All language subtitles for timedtext

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (SoranĂ®)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: WEBVTT Kind: captions Language: en 00:00:03.120 --> 00:00:11.770 align:start position:0% [Music] 00:00:11.770 --> 00:00:11.780 align:start position:0% [Music] 00:00:11.780 --> 00:00:24.130 align:start position:0% [Music] thank<00:00:12.780> you 00:00:24.130 --> 00:00:24.140 align:start position:0% 00:00:24.140 --> 00:00:27.830 align:start position:0% Network<00:00:25.140> fundamentals<00:00:26.539> basic<00:00:27.539> Network 00:00:27.830 --> 00:00:27.840 align:start position:0% Network fundamentals basic Network 00:00:27.840 --> 00:00:30.109 align:start position:0% Network fundamentals basic Network Theory<00:00:28.380> and<00:00:28.800> terminology 00:00:30.109 --> 00:00:30.119 align:start position:0% Theory and terminology 00:00:30.119 --> 00:00:32.450 align:start position:0% Theory and terminology Network<00:00:30.539> fundamentals<00:00:31.380> is<00:00:31.679> our<00:00:31.859> first<00:00:32.040> lesson 00:00:32.450 --> 00:00:32.460 align:start position:0% Network fundamentals is our first lesson 00:00:32.460 --> 00:00:35.030 align:start position:0% Network fundamentals is our first lesson since<00:00:32.880> before<00:00:33.120> we<00:00:33.420> can<00:00:33.540> get<00:00:33.780> into<00:00:34.040> discussing 00:00:35.030 --> 00:00:35.040 align:start position:0% since before we can get into discussing 00:00:35.040 --> 00:00:38.330 align:start position:0% since before we can get into discussing networking<00:00:35.899> and<00:00:36.899> its<00:00:37.200> complexity 00:00:38.330 --> 00:00:38.340 align:start position:0% networking and its complexity 00:00:38.340 --> 00:00:40.850 align:start position:0% networking and its complexity we<00:00:38.880> need<00:00:39.059> first<00:00:39.239> need<00:00:39.480> to<00:00:39.660> Define<00:00:40.020> some<00:00:40.500> of<00:00:40.620> the 00:00:40.850 --> 00:00:40.860 align:start position:0% we need first need to Define some of the 00:00:40.860 --> 00:00:43.130 align:start position:0% we need first need to Define some of the terms<00:00:41.219> some<00:00:41.700> of<00:00:41.820> the<00:00:41.879> theory<00:00:42.239> and<00:00:42.719> get<00:00:42.840> a<00:00:43.020> nice 00:00:43.130 --> 00:00:43.140 align:start position:0% terms some of the theory and get a nice 00:00:43.140 --> 00:00:44.450 align:start position:0% terms some of the theory and get a nice framework<00:00:43.620> for<00:00:43.860> where<00:00:44.040> we're<00:00:44.160> going<00:00:44.280> to<00:00:44.399> be 00:00:44.450 --> 00:00:44.460 align:start position:0% framework for where we're going to be 00:00:44.460 --> 00:00:45.410 align:start position:0% framework for where we're going to be going 00:00:45.410 --> 00:00:45.420 align:start position:0% going 00:00:45.420 --> 00:00:48.110 align:start position:0% going one<00:00:45.840> note<00:00:46.020> about<00:00:46.200> the<00:00:46.379> network<00:00:46.500> plus<00:00:46.860> exam<00:00:47.280> is 00:00:48.110 --> 00:00:48.120 align:start position:0% one note about the network plus exam is 00:00:48.120 --> 00:00:50.869 align:start position:0% one note about the network plus exam is that<00:00:48.360> they<00:00:48.780> assume<00:00:49.200> you<00:00:49.440> have<00:00:49.680> around<00:00:50.039> 18 00:00:50.869 --> 00:00:50.879 align:start position:0% that they assume you have around 18 00:00:50.879 --> 00:00:53.510 align:start position:0% that they assume you have around 18 months<00:00:51.480> experience<00:00:51.960> in<00:00:52.260> the<00:00:52.379> industry<00:00:52.739> if<00:00:53.399> you 00:00:53.510 --> 00:00:53.520 align:start position:0% months experience in the industry if you 00:00:53.520 --> 00:00:55.729 align:start position:0% months experience in the industry if you don't<00:00:53.700> that's<00:00:54.000> okay<00:00:54.300> but<00:00:54.960> I<00:00:55.140> am<00:00:55.260> assuming<00:00:55.620> that 00:00:55.729 --> 00:00:55.739 align:start position:0% don't that's okay but I am assuming that 00:00:55.739 --> 00:00:57.950 align:start position:0% don't that's okay but I am assuming that you<00:00:55.920> do<00:00:56.100> have<00:00:56.280> some<00:00:56.579> basic<00:00:57.000> knowledge<00:00:57.420> of 00:00:57.950 --> 00:00:57.960 align:start position:0% you do have some basic knowledge of 00:00:57.960 --> 00:01:00.470 align:start position:0% you do have some basic knowledge of computers<00:00:58.640> and<00:00:59.640> perhaps<00:01:00.120> some<00:01:00.300> working 00:01:00.470 --> 00:01:00.480 align:start position:0% computers and perhaps some working 00:01:00.480 --> 00:01:02.630 align:start position:0% computers and perhaps some working knowledge<00:01:00.899> of<00:01:01.079> networks<00:01:01.559> so<00:01:02.039> in<00:01:02.219> some<00:01:02.340> cases 00:01:02.630 --> 00:01:02.640 align:start position:0% knowledge of networks so in some cases 00:01:02.640 --> 00:01:06.530 align:start position:0% knowledge of networks so in some cases this<00:01:03.059> might<00:01:03.359> be<00:01:04.100> redundant<00:01:05.100> for<00:01:05.400> you<00:01:05.519> and<00:01:06.360> in 00:01:06.530 --> 00:01:06.540 align:start position:0% this might be redundant for you and in 00:01:06.540 --> 00:01:07.850 align:start position:0% this might be redundant for you and in other<00:01:06.659> cases<00:01:06.900> you<00:01:07.080> might<00:01:07.260> be<00:01:07.380> learning<00:01:07.680> some 00:01:07.850 --> 00:01:07.860 align:start position:0% other cases you might be learning some 00:01:07.860 --> 00:01:10.130 align:start position:0% other cases you might be learning some new<00:01:08.040> stuff<00:01:08.280> either<00:01:08.939> way<00:01:09.240> I'm<00:01:09.540> going<00:01:09.720> to<00:01:09.840> focus 00:01:10.130 --> 00:01:10.140 align:start position:0% new stuff either way I'm going to focus 00:01:10.140 --> 00:01:12.550 align:start position:0% new stuff either way I'm going to focus on<00:01:10.320> exactly<00:01:10.740> what<00:01:11.100> the<00:01:11.280> network<00:01:11.460> plus<00:01:11.760> exam 00:01:12.550 --> 00:01:12.560 align:start position:0% on exactly what the network plus exam 00:01:12.560 --> 00:01:15.469 align:start position:0% on exactly what the network plus exam wants<00:01:13.560> to<00:01:13.680> see<00:01:13.920> and 00:01:15.469 --> 00:01:15.479 align:start position:0% wants to see and 00:01:15.479 --> 00:01:18.469 align:start position:0% wants to see and what<00:01:16.020> you<00:01:16.200> need<00:01:16.320> to<00:01:16.439> know<00:01:16.560> to<00:01:16.920> pass 00:01:18.469 --> 00:01:18.479 align:start position:0% what you need to know to pass 00:01:18.479 --> 00:01:20.810 align:start position:0% what you need to know to pass so<00:01:19.020> in<00:01:19.320> this<00:01:19.439> module<00:01:19.860> we're<00:01:20.400> going<00:01:20.580> to<00:01:20.700> be 00:01:20.810 --> 00:01:20.820 align:start position:0% so in this module we're going to be 00:01:20.820 --> 00:01:23.390 align:start position:0% so in this module we're going to be introduced<00:01:21.299> to<00:01:21.659> networks<00:01:22.259> and<00:01:22.740> what<00:01:22.979> makes<00:01:23.159> up 00:01:23.390 --> 00:01:23.400 align:start position:0% introduced to networks and what makes up 00:01:23.400 --> 00:01:24.350 align:start position:0% introduced to networks and what makes up a<00:01:23.580> network 00:01:24.350 --> 00:01:24.360 align:start position:0% a network 00:01:24.360 --> 00:01:26.990 align:start position:0% a network the<00:01:24.900> terminology<00:01:25.380> that's<00:01:25.860> used<00:01:26.159> to<00:01:26.400> describe 00:01:26.990 --> 00:01:27.000 align:start position:0% the terminology that's used to describe 00:01:27.000 --> 00:01:29.810 align:start position:0% the terminology that's used to describe those<00:01:27.180> objects<00:01:27.659> it<00:01:28.080> becomes<00:01:28.560> flexible<00:01:29.040> after 00:01:29.810 --> 00:01:29.820 align:start position:0% those objects it becomes flexible after 00:01:29.820 --> 00:01:31.789 align:start position:0% those objects it becomes flexible after a<00:01:30.180> little<00:01:30.299> bit<00:01:30.420> of<00:01:30.659> time<00:01:30.960> and<00:01:31.259> experience 00:01:31.789 --> 00:01:31.799 align:start position:0% a little bit of time and experience 00:01:31.799 --> 00:01:33.890 align:start position:0% a little bit of time and experience spent<00:01:32.159> on<00:01:32.340> the<00:01:32.520> field<00:01:32.640> but<00:01:33.479> to<00:01:33.720> understand 00:01:33.890 --> 00:01:33.900 align:start position:0% spent on the field but to understand 00:01:33.900 --> 00:01:35.870 align:start position:0% spent on the field but to understand what<00:01:34.500> each<00:01:34.619> object<00:01:34.920> does<00:01:35.220> and<00:01:35.460> what<00:01:35.640> its 00:01:35.870 --> 00:01:35.880 align:start position:0% what each object does and what its 00:01:35.880 --> 00:01:38.090 align:start position:0% what each object does and what its functions<00:01:36.180> are<00:01:36.479> in<00:01:36.780> a<00:01:36.960> network<00:01:37.079> I<00:01:37.799> want<00:01:37.920> to 00:01:38.090 --> 00:01:38.100 align:start position:0% functions are in a network I want to 00:01:38.100 --> 00:01:39.649 align:start position:0% functions are in a network I want to break<00:01:38.220> down<00:01:38.460> some<00:01:38.759> of<00:01:38.880> the<00:01:39.000> jargon<00:01:39.360> or<00:01:39.540> the 00:01:39.649 --> 00:01:39.659 align:start position:0% break down some of the jargon or the 00:01:39.659 --> 00:01:42.170 align:start position:0% break down some of the jargon or the technical<00:01:39.960> speak<00:01:40.259> and<00:01:41.159> talk<00:01:41.400> about<00:01:41.640> what 00:01:42.170 --> 00:01:42.180 align:start position:0% technical speak and talk about what 00:01:42.180 --> 00:01:44.090 align:start position:0% technical speak and talk about what exactly<00:01:42.600> is<00:01:42.840> networking 00:01:44.090 --> 00:01:44.100 align:start position:0% exactly is networking 00:01:44.100 --> 00:01:46.429 align:start position:0% exactly is networking so<00:01:44.640> some<00:01:44.880> of<00:01:45.060> the<00:01:45.180> module<00:01:45.600> objectives<00:01:46.140> that 00:01:46.429 --> 00:01:46.439 align:start position:0% so some of the module objectives that 00:01:46.439 --> 00:01:48.649 align:start position:0% so some of the module objectives that we're<00:01:46.560> going<00:01:46.680> to<00:01:46.799> cover<00:01:46.939> are<00:01:47.939> first<00:01:48.119> to<00:01:48.420> Define 00:01:48.649 --> 00:01:48.659 align:start position:0% we're going to cover are first to Define 00:01:48.659 --> 00:01:51.530 align:start position:0% we're going to cover are first to Define and<00:01:48.960> describe<00:01:49.500> a<00:01:50.100> network<00:01:50.280> and<00:01:51.180> a<00:01:51.420> computer 00:01:51.530 --> 00:01:51.540 align:start position:0% and describe a network and a computer 00:01:51.540 --> 00:01:53.810 align:start position:0% and describe a network and a computer network<00:01:51.899> you've<00:01:52.619> heard<00:01:52.740> the<00:01:52.979> term<00:01:53.159> Network 00:01:53.810 --> 00:01:53.820 align:start position:0% network you've heard the term Network 00:01:53.820 --> 00:01:56.210 align:start position:0% network you've heard the term Network before<00:01:54.240> and<00:01:55.020> so<00:01:55.200> I<00:01:55.320> want<00:01:55.439> to<00:01:55.560> Define<00:01:55.740> what<00:01:56.040> that 00:01:56.210 --> 00:01:56.220 align:start position:0% before and so I want to Define what that 00:01:56.220 --> 00:01:57.770 align:start position:0% before and so I want to Define what that is<00:01:56.340> and<00:01:56.579> how<00:01:56.759> that<00:01:56.880> relates<00:01:57.240> to<00:01:57.479> a<00:01:57.600> computer 00:01:57.770 --> 00:01:57.780 align:start position:0% is and how that relates to a computer 00:01:57.780 --> 00:01:58.850 align:start position:0% is and how that relates to a computer network 00:01:58.850 --> 00:01:58.860 align:start position:0% network 00:01:58.860 --> 00:02:01.130 align:start position:0% network next<00:01:59.460> I<00:01:59.759> want<00:01:59.880> to<00:02:00.000> describe<00:02:00.299> the<00:02:00.600> components 00:02:01.130 --> 00:02:01.140 align:start position:0% next I want to describe the components 00:02:01.140 --> 00:02:03.050 align:start position:0% next I want to describe the components of<00:02:01.380> a<00:02:01.500> network<00:02:01.680> what<00:02:02.399> makes<00:02:02.700> a<00:02:02.939> computer 00:02:03.050 --> 00:02:03.060 align:start position:0% of a network what makes a computer 00:02:03.060 --> 00:02:04.490 align:start position:0% of a network what makes a computer network 00:02:04.490 --> 00:02:04.500 align:start position:0% network 00:02:04.500 --> 00:02:07.249 align:start position:0% network I<00:02:04.920> want<00:02:04.979> to<00:02:05.159> define<00:02:05.280> the<00:02:05.640> terms<00:02:06.119> node<00:02:06.780> and 00:02:07.249 --> 00:02:07.259 align:start position:0% I want to define the terms node and 00:02:07.259 --> 00:02:08.930 align:start position:0% I want to define the terms node and server<00:02:07.680> which<00:02:08.099> will<00:02:08.280> be<00:02:08.399> helpful<00:02:08.640> going 00:02:08.930 --> 00:02:08.940 align:start position:0% server which will be helpful going 00:02:08.940 --> 00:02:12.229 align:start position:0% server which will be helpful going forward<00:02:09.179> when<00:02:09.539> we<00:02:09.660> use<00:02:09.840> those<00:02:10.080> terms 00:02:12.229 --> 00:02:12.239 align:start position:0% forward when we use those terms 00:02:12.239 --> 00:02:15.050 align:start position:0% forward when we use those terms Define<00:02:12.720> and<00:02:13.080> describe<00:02:13.680> the<00:02:14.099> network<00:02:14.280> backbone 00:02:15.050 --> 00:02:15.060 align:start position:0% Define and describe the network backbone 00:02:15.060 --> 00:02:17.990 align:start position:0% Define and describe the network backbone and<00:02:15.599> the<00:02:15.780> various<00:02:16.220> variations<00:02:17.220> of<00:02:17.760> a<00:02:17.879> network 00:02:17.990 --> 00:02:18.000 align:start position:0% and the various variations of a network 00:02:18.000 --> 00:02:20.449 align:start position:0% and the various variations of a network backbone<00:02:18.660> and<00:02:19.560> finally 00:02:20.449 --> 00:02:20.459 align:start position:0% backbone and finally 00:02:20.459 --> 00:02:22.190 align:start position:0% backbone and finally I<00:02:20.879> want<00:02:20.940> to<00:02:21.120> define<00:02:21.239> the<00:02:21.660> difference<00:02:21.840> between 00:02:22.190 --> 00:02:22.200 align:start position:0% I want to define the difference between 00:02:22.200 --> 00:02:23.510 align:start position:0% I want to define the difference between a<00:02:22.560> terminal 00:02:23.510 --> 00:02:23.520 align:start position:0% a terminal 00:02:23.520 --> 00:02:26.510 align:start position:0% a terminal a<00:02:23.760> client<00:02:24.120> and<00:02:25.020> a<00:02:25.200> peer 00:02:26.510 --> 00:02:26.520 align:start position:0% a client and a peer 00:02:26.520 --> 00:02:28.670 align:start position:0% a client and a peer all<00:02:26.940> right<00:02:27.060> so<00:02:27.360> let's<00:02:27.540> get<00:02:27.780> started 00:02:28.670 --> 00:02:28.680 align:start position:0% all right so let's get started 00:02:28.680 --> 00:02:33.050 align:start position:0% all right so let's get started now<00:02:29.340> because<00:02:29.819> networking<00:02:30.720> is<00:02:31.319> ubiquitous<00:02:32.160> we 00:02:33.050 --> 00:02:33.060 align:start position:0% now because networking is ubiquitous we 00:02:33.060 --> 00:02:35.210 align:start position:0% now because networking is ubiquitous we need<00:02:33.180> to<00:02:33.300> define<00:02:33.480> a<00:02:33.900> few<00:02:34.080> specific<00:02:34.500> things<00:02:34.860> in 00:02:35.210 --> 00:02:35.220 align:start position:0% need to define a few specific things in 00:02:35.220 --> 00:02:36.770 align:start position:0% need to define a few specific things in order<00:02:35.340> to<00:02:35.520> keep<00:02:35.640> things<00:02:35.819> in<00:02:36.000> order 00:02:36.770 --> 00:02:36.780 align:start position:0% order to keep things in order 00:02:36.780 --> 00:02:39.589 align:start position:0% order to keep things in order so<00:02:37.319> first<00:02:37.620> Network 00:02:39.589 --> 00:02:39.599 align:start position:0% so first Network 00:02:39.599 --> 00:02:41.930 align:start position:0% so first Network this<00:02:40.140> is<00:02:40.260> an<00:02:40.560> interconnected<00:02:41.280> or 00:02:41.930 --> 00:02:41.940 align:start position:0% this is an interconnected or 00:02:41.940 --> 00:02:45.530 align:start position:0% this is an interconnected or interrelated<00:02:42.660> chain<00:02:43.260> group<00:02:43.860> or<00:02:44.640> system 00:02:45.530 --> 00:02:45.540 align:start position:0% interrelated chain group or system 00:02:45.540 --> 00:02:48.589 align:start position:0% interrelated chain group or system generally<00:02:46.200> based<00:02:46.739> on<00:02:47.040> a<00:02:47.280> purpose<00:02:47.640> so<00:02:48.360> for 00:02:48.589 --> 00:02:48.599 align:start position:0% generally based on a purpose so for 00:02:48.599 --> 00:02:50.690 align:start position:0% generally based on a purpose so for instance<00:02:48.840> if<00:02:49.140> we<00:02:49.260> say<00:02:49.500> that<00:02:49.680> you're<00:02:49.860> going<00:02:50.160> to 00:02:50.690 --> 00:02:50.700 align:start position:0% instance if we say that you're going to 00:02:50.700 --> 00:02:56.030 align:start position:0% instance if we say that you're going to Facebook<00:02:51.660> or<00:02:52.140> LinkedIn<00:02:52.620> are<00:02:53.280> social 00:02:56.030 --> 00:02:56.040 align:start position:0% 00:02:56.040 --> 00:02:59.089 align:start position:0% networks<00:02:56.819> because<00:02:57.480> the<00:02:58.200> purpose<00:02:58.500> is<00:02:58.680> to<00:02:58.980> be 00:02:59.089 --> 00:02:59.099 align:start position:0% networks because the purpose is to be 00:02:59.099 --> 00:02:59.990 align:start position:0% networks because the purpose is to be social 00:02:59.990 --> 00:03:00.000 align:start position:0% social 00:03:00.000 --> 00:03:01.970 align:start position:0% social and<00:03:00.300> to<00:03:00.540> connect<00:03:00.660> with<00:03:00.840> other<00:03:01.080> people<00:03:01.319> who 00:03:01.970 --> 00:03:01.980 align:start position:0% and to connect with other people who 00:03:01.980 --> 00:03:04.790 align:start position:0% and to connect with other people who have<00:03:02.099> similar<00:03:02.580> interests<00:03:03.180> likes<00:03:04.019> Etc 00:03:04.790 --> 00:03:04.800 align:start position:0% have similar interests likes Etc 00:03:04.800 --> 00:03:08.030 align:start position:0% have similar interests likes Etc in<00:03:05.340> the<00:03:05.459> same<00:03:05.640> way<00:03:05.819> you<00:03:06.239> are<00:03:06.420> interrelated<00:03:07.500> and 00:03:08.030 --> 00:03:08.040 align:start position:0% in the same way you are interrelated and 00:03:08.040 --> 00:03:11.030 align:start position:0% in the same way you are interrelated and you<00:03:08.220> form<00:03:08.400> a<00:03:08.700> group 00:03:11.030 --> 00:03:11.040 align:start position:0% 00:03:11.040 --> 00:03:14.089 align:start position:0% now<00:03:11.760> based<00:03:12.300> on<00:03:12.360> that<00:03:12.540> a<00:03:12.840> computer<00:03:12.959> network<00:03:13.319> is 00:03:14.089 --> 00:03:14.099 align:start position:0% now based on that a computer network is 00:03:14.099 --> 00:03:16.729 align:start position:0% now based on that a computer network is the<00:03:14.280> interconnecting<00:03:15.000> of<00:03:15.900> two<00:03:16.319> or<00:03:16.500> more 00:03:16.729 --> 00:03:16.739 align:start position:0% the interconnecting of two or more 00:03:16.739 --> 00:03:19.610 align:start position:0% the interconnecting of two or more computers<00:03:17.400> that<00:03:17.879> have<00:03:18.180> a<00:03:18.599> basic<00:03:18.900> core<00:03:19.140> purpose 00:03:19.610 --> 00:03:19.620 align:start position:0% computers that have a basic core purpose 00:03:19.620 --> 00:03:23.149 align:start position:0% computers that have a basic core purpose of<00:03:20.220> communicating<00:03:20.879> electronically 00:03:23.149 --> 00:03:23.159 align:start position:0% of communicating electronically 00:03:23.159 --> 00:03:26.210 align:start position:0% of communicating electronically so<00:03:23.760> the<00:03:24.420> network<00:03:24.599> of<00:03:24.959> social<00:03:25.140> network<00:03:25.500> is<00:03:25.860> to 00:03:26.210 --> 00:03:26.220 align:start position:0% so the network of social network is to 00:03:26.220 --> 00:03:28.430 align:start position:0% so the network of social network is to communicate<00:03:26.700> with<00:03:27.120> individuals<00:03:27.780> about<00:03:28.080> a 00:03:28.430 --> 00:03:28.440 align:start position:0% communicate with individuals about a 00:03:28.440 --> 00:03:30.949 align:start position:0% communicate with individuals about a specific<00:03:28.739> topic<00:03:29.280> on<00:03:29.879> a<00:03:30.060> computer<00:03:30.120> network<00:03:30.480> we 00:03:30.949 --> 00:03:30.959 align:start position:0% specific topic on a computer network we 00:03:30.959 --> 00:03:33.229 align:start position:0% specific topic on a computer network we need<00:03:31.080> to<00:03:31.319> communicate<00:03:31.800> data<00:03:32.519> electronically 00:03:33.229 --> 00:03:33.239 align:start position:0% need to communicate data electronically 00:03:33.239 --> 00:03:35.149 align:start position:0% need to communicate data electronically and<00:03:34.140> that's<00:03:34.319> the<00:03:34.500> thing<00:03:34.620> that<00:03:34.800> joins<00:03:35.040> us 00:03:35.149 --> 00:03:35.159 align:start position:0% and that's the thing that joins us 00:03:35.159 --> 00:03:35.990 align:start position:0% and that's the thing that joins us together 00:03:35.990 --> 00:03:36.000 align:start position:0% together 00:03:36.000 --> 00:03:38.809 align:start position:0% together the<00:03:36.599> internet<00:03:36.720> is<00:03:37.620> one<00:03:38.159> really<00:03:38.459> large 00:03:38.809 --> 00:03:38.819 align:start position:0% the internet is one really large 00:03:38.819 --> 00:03:41.990 align:start position:0% the internet is one really large computer<00:03:39.360> network<00:03:40.099> and<00:03:41.099> we<00:03:41.400> will<00:03:41.519> see<00:03:41.760> how 00:03:41.990 --> 00:03:42.000 align:start position:0% computer network and we will see how 00:03:42.000 --> 00:03:43.970 align:start position:0% computer network and we will see how that<00:03:42.180> comes<00:03:42.480> to<00:03:42.599> play<00:03:42.780> later<00:03:43.440> on<00:03:43.620> in<00:03:43.799> this 00:03:43.970 --> 00:03:43.980 align:start position:0% that comes to play later on in this 00:03:43.980 --> 00:03:46.390 align:start position:0% that comes to play later on in this course 00:03:46.390 --> 00:03:46.400 align:start position:0% 00:03:46.400 --> 00:03:49.250 align:start position:0% now<00:03:47.400> whether<00:03:47.760> your<00:03:48.060> network<00:03:48.239> is<00:03:48.599> comprised<00:03:49.080> of 00:03:49.250 --> 00:03:49.260 align:start position:0% now whether your network is comprised of 00:03:49.260 --> 00:03:51.350 align:start position:0% now whether your network is comprised of two<00:03:49.440> computers<00:03:49.980> or<00:03:50.340> two<00:03:50.519> thousand<00:03:50.940> computers 00:03:51.350 --> 00:03:51.360 align:start position:0% two computers or two thousand computers 00:03:51.360 --> 00:03:53.089 align:start position:0% two computers or two thousand computers or<00:03:51.780> like<00:03:52.080> the<00:03:52.200> internet<00:03:52.319> two<00:03:52.680> million 00:03:53.089 --> 00:03:53.099 align:start position:0% or like the internet two million 00:03:53.099 --> 00:03:55.430 align:start position:0% or like the internet two million computers<00:03:53.519> there<00:03:54.420> are<00:03:54.599> uh<00:03:55.080> some 00:03:55.430 --> 00:03:55.440 align:start position:0% computers there are uh some 00:03:55.440 --> 00:03:57.770 align:start position:0% computers there are uh some commonalities<00:03:56.159> in<00:03:56.879> networks<00:03:57.420> and 00:03:57.770 --> 00:03:57.780 align:start position:0% commonalities in networks and 00:03:57.780 --> 00:03:59.869 align:start position:0% commonalities in networks and requirements<00:03:58.319> for<00:03:58.560> what<00:03:58.680> makes<00:03:58.860> them<00:03:59.159> the 00:03:59.869 --> 00:03:59.879 align:start position:0% requirements for what makes them the 00:03:59.879 --> 00:04:01.250 align:start position:0% requirements for what makes them the first<00:04:00.000> thing<00:04:00.120> that<00:04:00.299> are<00:04:00.420> needed<00:04:00.720> obviously 00:04:01.250 --> 00:04:01.260 align:start position:0% first thing that are needed obviously 00:04:01.260 --> 00:04:04.070 align:start position:0% first thing that are needed obviously are<00:04:01.739> devices<00:04:02.299> these<00:04:03.299> are<00:04:03.480> the<00:04:03.780> actual 00:04:04.070 --> 00:04:04.080 align:start position:0% are devices these are the actual 00:04:04.080 --> 00:04:07.430 align:start position:0% are devices these are the actual computers<00:04:04.799> the<00:04:05.220> printers<00:04:05.760> the<00:04:06.659> switches<00:04:07.080> the 00:04:07.430 --> 00:04:07.440 align:start position:0% computers the printers the switches the 00:04:07.440 --> 00:04:09.890 align:start position:0% computers the printers the switches the routers<00:04:07.860> all<00:04:08.340> of<00:04:08.519> the<00:04:08.760> devices<00:04:09.180> that<00:04:09.780> are 00:04:09.890 --> 00:04:09.900 align:start position:0% routers all of the devices that are 00:04:09.900 --> 00:04:13.070 align:start position:0% routers all of the devices that are going<00:04:10.080> to<00:04:10.319> be<00:04:10.439> connected<00:04:10.920> together<00:04:11.280> by 00:04:13.070 --> 00:04:13.080 align:start position:0% going to be connected together by 00:04:13.080 --> 00:04:15.890 align:start position:0% going to be connected together by media<00:04:14.280> now<00:04:14.640> media<00:04:15.060> can<00:04:15.239> either<00:04:15.360> be<00:04:15.599> a<00:04:15.780> physical 00:04:15.890 --> 00:04:15.900 align:start position:0% media now media can either be a physical 00:04:15.900 --> 00:04:20.509 align:start position:0% media now media can either be a physical connection<00:04:16.260> such<00:04:16.979> as<00:04:17.299> copper<00:04:18.299> or<00:04:19.199> newer<00:04:20.040> forms 00:04:20.509 --> 00:04:20.519 align:start position:0% connection such as copper or newer forms 00:04:20.519 --> 00:04:23.210 align:start position:0% connection such as copper or newer forms such<00:04:20.820> as<00:04:21.139> fiber<00:04:22.139> optics 00:04:23.210 --> 00:04:23.220 align:start position:0% such as fiber optics 00:04:23.220 --> 00:04:25.370 align:start position:0% such as fiber optics or<00:04:23.759> it<00:04:23.880> can<00:04:24.000> be<00:04:24.120> something<00:04:24.300> Wireless<00:04:24.660> like 00:04:25.370 --> 00:04:25.380 align:start position:0% or it can be something Wireless like 00:04:25.380 --> 00:04:28.249 align:start position:0% or it can be something Wireless like Wi-Fi<00:04:25.979> or<00:04:26.580> a<00:04:26.699> radio<00:04:26.880> frequency<00:04:27.419> or<00:04:28.139> even 00:04:28.249 --> 00:04:28.259 align:start position:0% Wi-Fi or a radio frequency or even 00:04:28.259 --> 00:04:30.530 align:start position:0% Wi-Fi or a radio frequency or even cellular<00:04:28.860> Wi-Fi 00:04:30.530 --> 00:04:30.540 align:start position:0% cellular Wi-Fi 00:04:30.540 --> 00:04:33.710 align:start position:0% cellular Wi-Fi each<00:04:31.199> device<00:04:31.440> however<00:04:32.040> has<00:04:32.759> its<00:04:33.240> own<00:04:33.360> language 00:04:33.710 --> 00:04:33.720 align:start position:0% each device however has its own language 00:04:33.720 --> 00:04:36.409 align:start position:0% each device however has its own language when<00:04:34.380> networking<00:04:34.919> and<00:04:35.639> not<00:04:35.820> every<00:04:36.120> device 00:04:36.409 --> 00:04:36.419 align:start position:0% when networking and not every device 00:04:36.419 --> 00:04:38.450 align:start position:0% when networking and not every device knows<00:04:37.139> how<00:04:37.500> to<00:04:37.620> communicate<00:04:38.100> with<00:04:38.340> the 00:04:38.450 --> 00:04:38.460 align:start position:0% knows how to communicate with the 00:04:38.460 --> 00:04:40.370 align:start position:0% knows how to communicate with the language<00:04:38.580> of<00:04:38.940> these<00:04:39.240> other<00:04:39.419> devices<00:04:39.960> right 00:04:40.370 --> 00:04:40.380 align:start position:0% language of these other devices right 00:04:40.380 --> 00:04:42.170 align:start position:0% language of these other devices right because<00:04:41.040> obviously<00:04:41.699> a<00:04:42.000> computer 00:04:42.170 --> 00:04:42.180 align:start position:0% because obviously a computer 00:04:42.180 --> 00:04:44.749 align:start position:0% because obviously a computer communicates<00:04:42.960> slightly<00:04:43.320> differently<00:04:43.680> than<00:04:44.460> a 00:04:44.749 --> 00:04:44.759 align:start position:0% communicates slightly differently than a 00:04:44.759 --> 00:04:46.550 align:start position:0% communicates slightly differently than a printer<00:04:45.000> slightly<00:04:45.600> differently<00:04:45.900> than<00:04:46.199> a 00:04:46.550 --> 00:04:46.560 align:start position:0% printer slightly differently than a 00:04:46.560 --> 00:04:49.010 align:start position:0% printer slightly differently than a router<00:04:47.040> Etc<00:04:47.160> so<00:04:48.000> in<00:04:48.120> order<00:04:48.300> to<00:04:48.540> allow<00:04:48.840> all 00:04:49.010 --> 00:04:49.020 align:start position:0% router Etc so in order to allow all 00:04:49.020 --> 00:04:50.570 align:start position:0% router Etc so in order to allow all these<00:04:49.199> devices<00:04:49.440> to<00:04:49.740> communicate<00:04:50.160> with<00:04:50.400> the 00:04:50.570 --> 00:04:50.580 align:start position:0% these devices to communicate with the 00:04:50.580 --> 00:04:51.890 align:start position:0% these devices to communicate with the rest<00:04:50.639> of<00:04:50.820> the<00:04:50.940> network<00:04:51.060> we<00:04:51.479> have<00:04:51.660> something 00:04:51.890 --> 00:04:51.900 align:start position:0% rest of the network we have something 00:04:51.900 --> 00:04:54.409 align:start position:0% rest of the network we have something called<00:04:52.259> a<00:04:52.919> network<00:04:53.160> adapter<00:04:53.820> sometimes 00:04:54.409 --> 00:04:54.419 align:start position:0% called a network adapter sometimes 00:04:54.419 --> 00:04:55.909 align:start position:0% called a network adapter sometimes referred<00:04:54.840> to<00:04:54.900> as<00:04:55.080> a<00:04:55.259> network<00:04:55.380> interface 00:04:55.909 --> 00:04:55.919 align:start position:0% referred to as a network interface 00:04:55.919 --> 00:04:58.070 align:start position:0% referred to as a network interface controller<00:04:56.520> or<00:04:56.880> a<00:04:57.060> NIC 00:04:58.070 --> 00:04:58.080 align:start position:0% controller or a NIC 00:04:58.080 --> 00:05:01.370 align:start position:0% controller or a NIC specifically<00:04:58.860> in<00:04:59.100> the<00:04:59.220> term<00:04:59.340> of<00:04:59.759> computers 00:05:01.370 --> 00:05:01.380 align:start position:0% specifically in the term of computers 00:05:01.380 --> 00:05:04.730 align:start position:0% specifically in the term of computers and<00:05:02.100> it<00:05:02.400> serves<00:05:02.820> this<00:05:03.300> network<00:05:03.419> adapter<00:05:03.960> as<00:05:04.320> a 00:05:04.730 --> 00:05:04.740 align:start position:0% and it serves this network adapter as a 00:05:04.740 --> 00:05:07.010 align:start position:0% and it serves this network adapter as a translator<00:05:05.160> between<00:05:05.880> the<00:05:06.300> components<00:05:06.840> the 00:05:07.010 --> 00:05:07.020 align:start position:0% translator between the components the 00:05:07.020 --> 00:05:10.070 align:start position:0% translator between the components the devices<00:05:07.380> over<00:05:08.280> the<00:05:08.580> media<00:05:08.880> by<00:05:09.419> which<00:05:09.600> the<00:05:09.840> data 00:05:10.070 --> 00:05:10.080 align:start position:0% devices over the media by which the data 00:05:10.080 --> 00:05:11.150 align:start position:0% devices over the media by which the data is<00:05:10.199> sent 00:05:11.150 --> 00:05:11.160 align:start position:0% is sent 00:05:11.160 --> 00:05:14.450 align:start position:0% is sent so<00:05:11.639> finally<00:05:12.199> to<00:05:13.199> manage<00:05:13.500> and<00:05:13.740> govern<00:05:13.919> how 00:05:14.450 --> 00:05:14.460 align:start position:0% so finally to manage and govern how 00:05:14.460 --> 00:05:15.710 align:start position:0% so finally to manage and govern how everything<00:05:14.639> talks<00:05:15.180> with<00:05:15.300> everything<00:05:15.479> else 00:05:15.710 --> 00:05:15.720 align:start position:0% everything talks with everything else 00:05:15.720 --> 00:05:17.930 align:start position:0% everything talks with everything else the<00:05:16.080> network<00:05:16.259> needs<00:05:16.800> an<00:05:17.160> operating<00:05:17.580> system 00:05:17.930 --> 00:05:17.940 align:start position:0% the network needs an operating system 00:05:17.940 --> 00:05:20.450 align:start position:0% the network needs an operating system which<00:05:18.720> is<00:05:18.900> similar<00:05:19.199> to<00:05:19.380> like<00:05:19.560> the<00:05:19.860> ring<00:05:20.040> leader 00:05:20.450 --> 00:05:20.460 align:start position:0% which is similar to like the ring leader 00:05:20.460 --> 00:05:23.330 align:start position:0% which is similar to like the ring leader in<00:05:20.580> a<00:05:20.699> circus<00:05:21.000> if<00:05:21.300> we<00:05:21.479> can<00:05:21.600> use<00:05:21.840> a<00:05:22.199> a<00:05:22.740> metaphor 00:05:23.330 --> 00:05:23.340 align:start position:0% in a circus if we can use a a metaphor 00:05:23.340 --> 00:05:24.409 align:start position:0% in a circus if we can use a a metaphor there 00:05:24.409 --> 00:05:24.419 align:start position:0% there 00:05:24.419 --> 00:05:26.029 align:start position:0% there it<00:05:24.960> tells<00:05:25.139> the<00:05:25.259> network<00:05:25.380> how<00:05:25.740> to<00:05:25.860> work 00:05:26.029 --> 00:05:26.039 align:start position:0% it tells the network how to work 00:05:26.039 --> 00:05:28.189 align:start position:0% it tells the network how to work together<00:05:26.280> in<00:05:26.940> order<00:05:27.060> to<00:05:27.360> perform<00:05:27.600> as 00:05:28.189 --> 00:05:28.199 align:start position:0% together in order to perform as 00:05:28.199 --> 00:05:30.350 align:start position:0% together in order to perform as efficiently<00:05:28.680> as<00:05:28.919> possible<00:05:29.280> over<00:05:29.699> the<00:05:29.940> adapter 00:05:30.350 --> 00:05:30.360 align:start position:0% efficiently as possible over the adapter 00:05:30.360 --> 00:05:32.450 align:start position:0% efficiently as possible over the adapter over<00:05:30.660> the<00:05:30.900> media<00:05:31.259> and<00:05:31.680> with<00:05:31.919> each<00:05:32.160> of<00:05:32.280> the 00:05:32.450 --> 00:05:32.460 align:start position:0% over the media and with each of the 00:05:32.460 --> 00:05:34.550 align:start position:0% over the media and with each of the devices<00:05:32.759> without<00:05:33.600> the<00:05:33.960> operating<00:05:34.259> system 00:05:34.550 --> 00:05:34.560 align:start position:0% devices without the operating system 00:05:34.560 --> 00:05:36.890 align:start position:0% devices without the operating system there<00:05:34.979> wouldn't<00:05:35.160> be<00:05:35.340> any<00:05:35.639> order<00:05:36.000> or<00:05:36.660> Direction 00:05:36.890 --> 00:05:36.900 align:start position:0% there wouldn't be any order or Direction 00:05:36.900 --> 00:05:38.689 align:start position:0% there wouldn't be any order or Direction in<00:05:37.259> the<00:05:37.380> network<00:05:37.620> and<00:05:37.979> no<00:05:38.160> one<00:05:38.340> would<00:05:38.520> really 00:05:38.689 --> 00:05:38.699 align:start position:0% in the network and no one would really 00:05:38.699 --> 00:05:40.850 align:start position:0% in the network and no one would really know<00:05:38.940> what<00:05:39.180> they<00:05:39.300> were<00:05:39.479> doing<00:05:39.660> so<00:05:40.440> the<00:05:40.740> network 00:05:40.850 --> 00:05:40.860 align:start position:0% know what they were doing so the network 00:05:40.860 --> 00:05:43.430 align:start position:0% know what they were doing so the network operating<00:05:41.400> system<00:05:41.699> is<00:05:42.479> responsible<00:05:43.080> really 00:05:43.430 --> 00:05:43.440 align:start position:0% operating system is responsible really 00:05:43.440 --> 00:05:46.749 align:start position:0% operating system is responsible really for<00:05:44.060> allocating<00:05:45.060> resources 00:05:46.749 --> 00:05:46.759 align:start position:0% for allocating resources 00:05:46.759 --> 00:05:49.310 align:start position:0% for allocating resources monitoring<00:05:47.759> the<00:05:48.120> activities<00:05:48.479> of<00:05:48.780> devices<00:05:49.020> on 00:05:49.310 --> 00:05:49.320 align:start position:0% monitoring the activities of devices on 00:05:49.320 --> 00:05:51.610 align:start position:0% monitoring the activities of devices on the<00:05:49.380> network<00:05:49.500> over<00:05:49.979> the<00:05:50.280> media 00:05:51.610 --> 00:05:51.620 align:start position:0% the network over the media 00:05:51.620 --> 00:05:56.450 align:start position:0% the network over the media and<00:05:52.620> managing<00:05:53.160> files<00:05:53.759> and<00:05:54.060> data<00:05:54.539> Etc 00:05:56.450 --> 00:05:56.460 align:start position:0% and managing files and data Etc 00:05:56.460 --> 00:05:59.990 align:start position:0% and managing files and data Etc now<00:05:57.300> we<00:05:58.259> have<00:05:58.440> two<00:05:58.740> devices<00:05:59.160> that<00:05:59.580> I<00:05:59.759> want<00:05:59.880> to 00:05:59.990 --> 00:06:00.000 align:start position:0% now we have two devices that I want to 00:06:00.000 --> 00:06:03.890 align:start position:0% now we have two devices that I want to Define<00:06:00.800> one<00:06:01.800> is<00:06:01.979> a<00:06:02.280> node<00:06:02.460> and<00:06:03.000> a<00:06:03.120> node<00:06:03.360> is<00:06:03.539> any 00:06:03.890 --> 00:06:03.900 align:start position:0% Define one is a node and a node is any 00:06:03.900 --> 00:06:05.810 align:start position:0% Define one is a node and a node is any device<00:06:04.199> that<00:06:04.979> is<00:06:05.100> connected<00:06:05.460> to<00:06:05.639> a 00:06:05.810 --> 00:06:05.820 align:start position:0% device that is connected to a 00:06:05.820 --> 00:06:07.249 align:start position:0% device that is connected to a Communications<00:06:06.240> Network 00:06:07.249 --> 00:06:07.259 align:start position:0% Communications Network 00:06:07.259 --> 00:06:09.590 align:start position:0% Communications Network and<00:06:07.560> this<00:06:07.740> can<00:06:07.919> be<00:06:08.220> just<00:06:08.759> about<00:06:08.880> anything<00:06:09.120> so 00:06:09.590 --> 00:06:09.600 align:start position:0% and this can be just about anything so 00:06:09.600 --> 00:06:13.689 align:start position:0% and this can be just about anything so we<00:06:09.840> have<00:06:10.039> uh<00:06:11.039> clients<00:06:11.759> and<00:06:11.940> servers<00:06:12.539> our<00:06:13.020> nodes 00:06:13.689 --> 00:06:13.699 align:start position:0% we have uh clients and servers our nodes 00:06:13.699 --> 00:06:17.570 align:start position:0% we have uh clients and servers our nodes and<00:06:14.699> so<00:06:15.060> are<00:06:15.300> printers<00:06:16.259> and<00:06:16.800> network<00:06:16.979> attached 00:06:17.570 --> 00:06:17.580 align:start position:0% and so are printers and network attached 00:06:17.580 --> 00:06:20.749 align:start position:0% and so are printers and network attached storage<00:06:17.940> devices<00:06:18.800> and<00:06:19.800> these<00:06:20.100> are<00:06:20.220> all<00:06:20.460> what 00:06:20.749 --> 00:06:20.759 align:start position:0% storage devices and these are all what 00:06:20.759 --> 00:06:22.010 align:start position:0% storage devices and these are all what we<00:06:20.880> call 00:06:22.010 --> 00:06:22.020 align:start position:0% we call 00:06:22.020 --> 00:06:24.890 align:start position:0% we call endpoint<00:06:22.979> nodes<00:06:23.460> I'm<00:06:24.360> going<00:06:24.479> to<00:06:24.539> write<00:06:24.720> that 00:06:24.890 --> 00:06:24.900 align:start position:0% endpoint nodes I'm going to write that 00:06:24.900 --> 00:06:26.270 align:start position:0% endpoint nodes I'm going to write that up<00:06:25.020> here 00:06:26.270 --> 00:06:26.280 align:start position:0% up here 00:06:26.280 --> 00:06:30.770 align:start position:0% up here because<00:06:27.000> that's<00:06:27.780> where<00:06:28.020> the<00:06:28.199> data<00:06:28.620> ends 00:06:30.770 --> 00:06:30.780 align:start position:0% because that's where the data ends 00:06:30.780 --> 00:06:33.950 align:start position:0% because that's where the data ends whereas<00:06:31.560> something<00:06:32.039> like<00:06:32.460> a<00:06:32.819> router 00:06:33.950 --> 00:06:33.960 align:start position:0% whereas something like a router 00:06:33.960 --> 00:06:38.510 align:start position:0% whereas something like a router or<00:06:34.919> switch<00:06:35.600> or<00:06:36.600> previously<00:06:37.380> we<00:06:37.860> used<00:06:38.160> to<00:06:38.220> see<00:06:38.400> a 00:06:38.510 --> 00:06:38.520 align:start position:0% or switch or previously we used to see a 00:06:38.520 --> 00:06:44.270 align:start position:0% or switch or previously we used to see a lot<00:06:38.639> of<00:06:38.759> hubs<00:06:39.479> do<00:06:40.440> what's<00:06:40.680> called 00:06:44.270 --> 00:06:44.280 align:start position:0% 00:06:44.280 --> 00:06:45.830 align:start position:0% redistribute 00:06:45.830 --> 00:06:45.840 align:start position:0% redistribute 00:06:45.840 --> 00:06:47.990 align:start position:0% redistribute so<00:06:46.139> those<00:06:46.259> are<00:06:46.440> what<00:06:46.620> we<00:06:46.740> call<00:06:47.000> redistribution 00:06:47.990 --> 00:06:48.000 align:start position:0% so those are what we call redistribution 00:06:48.000 --> 00:06:51.170 align:start position:0% so those are what we call redistribution nodes<00:06:48.900> okay<00:06:49.560> so<00:06:50.460> it's<00:06:50.580> important<00:06:50.940> to 00:06:51.170 --> 00:06:51.180 align:start position:0% nodes okay so it's important to 00:06:51.180 --> 00:06:52.670 align:start position:0% nodes okay so it's important to understand<00:06:51.300> that<00:06:51.660> these<00:06:51.900> are<00:06:52.020> both<00:06:52.199> nodes 00:06:52.670 --> 00:06:52.680 align:start position:0% understand that these are both nodes 00:06:52.680 --> 00:06:55.189 align:start position:0% understand that these are both nodes anything<00:06:53.520> on<00:06:53.880> the<00:06:54.000> network<00:06:54.120> really<00:06:54.660> any<00:06:54.960> sort 00:06:55.189 --> 00:06:55.199 align:start position:0% anything on the network really any sort 00:06:55.199 --> 00:06:58.129 align:start position:0% anything on the network really any sort of<00:06:55.259> device<00:06:55.560> that's<00:06:56.520> communicating<00:06:57.180> is<00:06:57.780> a<00:06:57.960> node 00:06:58.129 --> 00:06:58.139 align:start position:0% of device that's communicating is a node 00:06:58.139 --> 00:07:00.230 align:start position:0% of device that's communicating is a node or<00:06:58.680> being<00:06:58.919> communicated<00:06:59.400> with 00:07:00.230 --> 00:07:00.240 align:start position:0% or being communicated with 00:07:00.240 --> 00:07:02.930 align:start position:0% or being communicated with the<00:07:00.720> endpoint<00:07:00.960> nodes<00:07:01.319> where<00:07:02.220> or<00:07:02.580> where<00:07:02.759> the 00:07:02.930 --> 00:07:02.940 align:start position:0% the endpoint nodes where or where the 00:07:02.940 --> 00:07:04.730 align:start position:0% the endpoint nodes where or where the information<00:07:03.060> sort<00:07:03.539> of<00:07:03.660> ends<00:07:04.020> up<00:07:04.139> or<00:07:04.440> is<00:07:04.560> going 00:07:04.730 --> 00:07:04.740 align:start position:0% information sort of ends up or is going 00:07:04.740 --> 00:07:07.550 align:start position:0% information sort of ends up or is going to<00:07:04.979> a<00:07:05.460> redistribution<00:07:06.180> node<00:07:06.660> its 00:07:07.550 --> 00:07:07.560 align:start position:0% to a redistribution node its 00:07:07.560 --> 00:07:11.210 align:start position:0% to a redistribution node its responsibilities<00:07:08.100> to<00:07:08.580> pass<00:07:08.880> the<00:07:09.720> data<00:07:10.080> on<00:07:10.740> to 00:07:11.210 --> 00:07:11.220 align:start position:0% responsibilities to pass the data on to 00:07:11.220 --> 00:07:13.850 align:start position:0% responsibilities to pass the data on to another<00:07:11.460> either<00:07:12.080> redistribution<00:07:13.080> node<00:07:13.440> or 00:07:13.850 --> 00:07:13.860 align:start position:0% another either redistribution node or 00:07:13.860 --> 00:07:17.689 align:start position:0% another either redistribution node or onto<00:07:14.340> the<00:07:14.520> endpoint<00:07:14.819> node 00:07:17.689 --> 00:07:17.699 align:start position:0% 00:07:17.699 --> 00:07:19.670 align:start position:0% now<00:07:18.060> a<00:07:18.539> server 00:07:19.670 --> 00:07:19.680 align:start position:0% now a server 00:07:19.680 --> 00:07:23.510 align:start position:0% now a server is<00:07:20.280> a<00:07:20.580> network<00:07:20.699> device<00:07:21.120> that's<00:07:22.020> responsible 00:07:23.510 --> 00:07:23.520 align:start position:0% is a network device that's responsible 00:07:23.520 --> 00:07:27.650 align:start position:0% is a network device that's responsible for<00:07:24.060> sharing<00:07:24.740> resources<00:07:26.000> and<00:07:27.000> managing 00:07:27.650 --> 00:07:27.660 align:start position:0% for sharing resources and managing 00:07:27.660 --> 00:07:28.990 align:start position:0% for sharing resources and managing certain<00:07:27.960> services 00:07:28.990 --> 00:07:29.000 align:start position:0% certain services 00:07:29.000 --> 00:07:31.610 align:start position:0% certain services like<00:07:30.000> addressing<00:07:30.720> and<00:07:31.080> we'll<00:07:31.259> talk<00:07:31.500> about 00:07:31.610 --> 00:07:31.620 align:start position:0% like addressing and we'll talk about 00:07:31.620 --> 00:07:34.070 align:start position:0% like addressing and we'll talk about this<00:07:31.979> which<00:07:32.220> is<00:07:32.340> called<00:07:32.520> an<00:07:32.759> IP<00:07:33.060> address<00:07:33.240> a 00:07:34.070 --> 00:07:34.080 align:start position:0% this which is called an IP address a 00:07:34.080 --> 00:07:36.830 align:start position:0% this which is called an IP address a little<00:07:34.199> later 00:07:36.830 --> 00:07:36.840 align:start position:0% 00:07:36.840 --> 00:07:40.070 align:start position:0% it's<00:07:37.500> also<00:07:37.919> uh<00:07:38.580> manages<00:07:39.180> devices<00:07:39.660> on<00:07:39.960> the 00:07:40.070 --> 00:07:40.080 align:start position:0% it's also uh manages devices on the 00:07:40.080 --> 00:07:42.110 align:start position:0% it's also uh manages devices on the network<00:07:40.199> and<00:07:40.560> controls<00:07:41.220> the<00:07:41.520> network-wide 00:07:42.110 --> 00:07:42.120 align:start position:0% network and controls the network-wide 00:07:42.120 --> 00:07:44.510 align:start position:0% network and controls the network-wide functions<00:07:42.780> like<00:07:43.080> permissions<00:07:43.680> so<00:07:44.160> not<00:07:44.340> only 00:07:44.510 --> 00:07:44.520 align:start position:0% functions like permissions so not only 00:07:44.520 --> 00:07:48.230 align:start position:0% functions like permissions so not only is<00:07:44.759> it<00:07:45.000> going<00:07:45.180> to<00:07:45.360> give<00:07:45.919> uh<00:07:46.919> all<00:07:47.699> our<00:07:47.940> clients 00:07:48.230 --> 00:07:48.240 align:start position:0% is it going to give uh all our clients 00:07:48.240 --> 00:07:50.270 align:start position:0% is it going to give uh all our clients all<00:07:48.419> the<00:07:48.539> other<00:07:48.660> nodes<00:07:49.020> addresses<00:07:49.800> that<00:07:49.979> allow 00:07:50.270 --> 00:07:50.280 align:start position:0% all the other nodes addresses that allow 00:07:50.280 --> 00:07:52.129 align:start position:0% all the other nodes addresses that allow it<00:07:50.400> to<00:07:50.580> communicate<00:07:51.000> it's<00:07:51.479> also<00:07:51.780> going<00:07:51.900> to 00:07:52.129 --> 00:07:52.139 align:start position:0% it to communicate it's also going to 00:07:52.139 --> 00:07:55.189 align:start position:0% it to communicate it's also going to manage<00:07:52.620> how<00:07:53.220> those<00:07:53.460> devices<00:07:53.819> communicate<00:07:54.599> and 00:07:55.189 --> 00:07:55.199 align:start position:0% manage how those devices communicate and 00:07:55.199 --> 00:07:57.110 align:start position:0% manage how those devices communicate and what<00:07:55.440> they're<00:07:55.620> allowed<00:07:55.979> to<00:07:56.099> do<00:07:56.340> which<00:07:56.819> is<00:07:56.940> what 00:07:57.110 --> 00:07:57.120 align:start position:0% what they're allowed to do which is what 00:07:57.120 --> 00:07:58.730 align:start position:0% what they're allowed to do which is what we<00:07:57.240> call<00:07:57.360> permissions 00:07:58.730 --> 00:07:58.740 align:start position:0% we call permissions 00:07:58.740 --> 00:08:02.150 align:start position:0% we call permissions all<00:07:59.099> right<00:07:59.280> now<00:07:59.940> this<00:08:00.599> is 00:08:02.150 --> 00:08:02.160 align:start position:0% all right now this is 00:08:02.160 --> 00:08:04.790 align:start position:0% all right now this is um<00:08:02.280> so<00:08:03.120> you<00:08:03.419> can<00:08:03.479> see<00:08:03.660> that<00:08:03.900> the<00:08:04.080> server<00:08:04.380> is<00:08:04.620> a 00:08:04.790 --> 00:08:04.800 align:start position:0% um so you can see that the server is a 00:08:04.800 --> 00:08:06.589 align:start position:0% um so you can see that the server is a type<00:08:04.919> of<00:08:05.099> node<00:08:05.400> but<00:08:05.819> I<00:08:05.940> just<00:08:06.060> want<00:08:06.180> to<00:08:06.300> describe 00:08:06.589 --> 00:08:06.599 align:start position:0% type of node but I just want to describe 00:08:06.599 --> 00:08:08.330 align:start position:0% type of node but I just want to describe server<00:08:06.840> we're<00:08:07.020> going<00:08:07.139> to<00:08:07.259> talk<00:08:07.380> about<00:08:07.560> some<00:08:08.220> of 00:08:08.330 --> 00:08:08.340 align:start position:0% server we're going to talk about some of 00:08:08.340 --> 00:08:09.350 align:start position:0% server we're going to talk about some of the<00:08:08.460> other 00:08:09.350 --> 00:08:09.360 align:start position:0% the other 00:08:09.360 --> 00:08:12.409 align:start position:0% the other um<00:08:09.500> devices<00:08:10.500> in<00:08:10.979> just<00:08:11.099> a<00:08:11.220> moment<00:08:11.460> before<00:08:12.000> we<00:08:12.240> do 00:08:12.409 --> 00:08:12.419 align:start position:0% um devices in just a moment before we do 00:08:12.419 --> 00:08:13.610 align:start position:0% um devices in just a moment before we do that 00:08:13.610 --> 00:08:13.620 align:start position:0% that 00:08:13.620 --> 00:08:15.890 align:start position:0% that let's<00:08:14.099> talk<00:08:14.280> about<00:08:14.460> the<00:08:15.000> network<00:08:15.120> backbone 00:08:15.890 --> 00:08:15.900 align:start position:0% let's talk about the network backbone 00:08:15.900 --> 00:08:19.189 align:start position:0% let's talk about the network backbone okay<00:08:16.560> the<00:08:17.460> network<00:08:17.580> backbone<00:08:18.300> is<00:08:18.660> responsible 00:08:19.189 --> 00:08:19.199 align:start position:0% okay the network backbone is responsible 00:08:19.199 --> 00:08:21.770 align:start position:0% okay the network backbone is responsible for<00:08:19.620> carrying<00:08:20.099> the<00:08:20.699> majority<00:08:21.180> of<00:08:21.539> network 00:08:21.770 --> 00:08:21.780 align:start position:0% for carrying the majority of network 00:08:21.780 --> 00:08:25.550 align:start position:0% for carrying the majority of network traffic<00:08:22.460> and<00:08:23.460> it<00:08:23.819> works<00:08:24.360> very<00:08:24.599> quickly<00:08:24.960> at<00:08:25.319> a 00:08:25.550 --> 00:08:25.560 align:start position:0% traffic and it works very quickly at a 00:08:25.560 --> 00:08:27.650 align:start position:0% traffic and it works very quickly at a very<00:08:25.740> very<00:08:25.979> very<00:08:26.160> high<00:08:26.759> speed 00:08:27.650 --> 00:08:27.660 align:start position:0% very very very high speed 00:08:27.660 --> 00:08:29.749 align:start position:0% very very very high speed now<00:08:28.199> it<00:08:28.500> might<00:08:28.680> use<00:08:28.860> different<00:08:29.160> technology 00:08:29.749 --> 00:08:29.759 align:start position:0% now it might use different technology 00:08:29.759 --> 00:08:33.889 align:start position:0% now it might use different technology throughout<00:08:30.539> this<00:08:31.680> um<00:08:31.880> on<00:08:32.880> the<00:08:33.120> backbone 00:08:33.889 --> 00:08:33.899 align:start position:0% throughout this um on the backbone 00:08:33.899 --> 00:08:35.149 align:start position:0% throughout this um on the backbone that's<00:08:34.140> different<00:08:34.380> from<00:08:34.680> the<00:08:34.800> rest<00:08:34.919> of<00:08:35.099> the 00:08:35.149 --> 00:08:35.159 align:start position:0% that's different from the rest of the 00:08:35.159 --> 00:08:38.329 align:start position:0% that's different from the rest of the network<00:08:35.339> because<00:08:36.000> it<00:08:36.659> basically<00:08:37.020> connects 00:08:38.329 --> 00:08:38.339 align:start position:0% network because it basically connects 00:08:38.339 --> 00:08:40.969 align:start position:0% network because it basically connects all<00:08:39.000> the<00:08:39.180> smaller<00:08:39.479> networks<00:08:39.899> together 00:08:40.969 --> 00:08:40.979 align:start position:0% all the smaller networks together 00:08:40.979 --> 00:08:43.310 align:start position:0% all the smaller networks together that's<00:08:41.459> why<00:08:41.640> it's<00:08:41.760> called<00:08:41.940> the<00:08:42.180> backbone<00:08:42.719> and 00:08:43.310 --> 00:08:43.320 align:start position:0% that's why it's called the backbone and 00:08:43.320 --> 00:08:47.449 align:start position:0% that's why it's called the backbone and it<00:08:43.500> needs<00:08:43.800> to<00:08:44.039> be<00:08:44.279> large<00:08:45.120> fast<00:08:45.899> and 00:08:47.449 --> 00:08:47.459 align:start position:0% it needs to be large fast and 00:08:47.459 --> 00:08:48.230 align:start position:0% it needs to be large fast and um 00:08:48.230 --> 00:08:48.240 align:start position:0% um 00:08:48.240 --> 00:08:51.110 align:start position:0% um capable<00:08:49.019> of<00:08:49.500> communicating<00:08:50.100> at<00:08:50.640> very<00:08:50.880> high 00:08:51.110 --> 00:08:51.120 align:start position:0% capable of communicating at very high 00:08:51.120 --> 00:08:52.970 align:start position:0% capable of communicating at very high speeds<00:08:51.480> because<00:08:51.899> all<00:08:52.140> of<00:08:52.260> these<00:08:52.500> computers 00:08:52.970 --> 00:08:52.980 align:start position:0% speeds because all of these computers 00:08:52.980 --> 00:08:54.769 align:start position:0% speeds because all of these computers all<00:08:53.339> these<00:08:53.640> smaller<00:08:53.940> networks<00:08:54.360> are 00:08:54.769 --> 00:08:54.779 align:start position:0% all these smaller networks are 00:08:54.779 --> 00:08:56.570 align:start position:0% all these smaller networks are communicating<00:08:55.200> we'll<00:08:55.500> talk<00:08:55.680> about<00:08:55.860> how<00:08:56.399> that 00:08:56.570 --> 00:08:56.580 align:start position:0% communicating we'll talk about how that 00:08:56.580 --> 00:08:58.850 align:start position:0% communicating we'll talk about how that all<00:08:56.760> works<00:08:57.060> in<00:08:57.180> a<00:08:57.300> bit<00:08:57.420> now<00:08:58.260> there<00:08:58.500> are<00:08:58.620> four 00:08:58.850 --> 00:08:58.860 align:start position:0% all works in a bit now there are four 00:08:58.860 --> 00:09:01.310 align:start position:0% all works in a bit now there are four different<00:08:59.160> types<00:08:59.760> of<00:09:00.000> network<00:09:00.180> backbones<00:09:00.899> and 00:09:01.310 --> 00:09:01.320 align:start position:0% different types of network backbones and 00:09:01.320 --> 00:09:02.570 align:start position:0% different types of network backbones and we're<00:09:01.440> gonna<00:09:01.560> I'm<00:09:01.800> just<00:09:01.980> gonna<00:09:02.100> give<00:09:02.279> you<00:09:02.399> a 00:09:02.570 --> 00:09:02.580 align:start position:0% we're gonna I'm just gonna give you a 00:09:02.580 --> 00:09:04.310 align:start position:0% we're gonna I'm just gonna give you a brief<00:09:02.820> definition<00:09:03.000> of<00:09:03.480> these<00:09:03.660> now<00:09:03.839> and<00:09:04.200> we 00:09:04.310 --> 00:09:04.320 align:start position:0% brief definition of these now and we 00:09:04.320 --> 00:09:05.990 align:start position:0% brief definition of these now and we will<00:09:04.440> come<00:09:04.680> back<00:09:04.920> and<00:09:05.160> talk<00:09:05.339> about<00:09:05.519> these<00:09:05.820> more 00:09:05.990 --> 00:09:06.000 align:start position:0% will come back and talk about these more 00:09:06.000 --> 00:09:07.970 align:start position:0% will come back and talk about these more in<00:09:06.180> depth<00:09:06.480> a<00:09:06.540> little<00:09:06.660> later<00:09:06.839> okay<00:09:07.380> the<00:09:07.860> first 00:09:07.970 --> 00:09:07.980 align:start position:0% in depth a little later okay the first 00:09:07.980 --> 00:09:10.130 align:start position:0% in depth a little later okay the first one<00:09:08.160> is<00:09:08.339> called<00:09:08.580> serial<00:09:09.120> that's<00:09:09.660> where<00:09:09.899> one 00:09:10.130 --> 00:09:10.140 align:start position:0% one is called serial that's where one 00:09:10.140 --> 00:09:11.990 align:start position:0% one is called serial that's where one backbone<00:09:10.620> cable 00:09:11.990 --> 00:09:12.000 align:start position:0% backbone cable 00:09:12.000 --> 00:09:13.970 align:start position:0% backbone cable connects 00:09:13.970 --> 00:09:13.980 align:start position:0% connects 00:09:13.980 --> 00:09:18.530 align:start position:0% connects to<00:09:14.459> another<00:09:14.779> one<00:09:15.779> after<00:09:16.019> the<00:09:16.320> other 00:09:18.530 --> 00:09:18.540 align:start position:0% 00:09:18.540 --> 00:09:19.910 align:start position:0% like<00:09:19.019> so 00:09:19.910 --> 00:09:19.920 align:start position:0% like so 00:09:19.920 --> 00:09:22.310 align:start position:0% like so all<00:09:20.459> right<00:09:20.640> so<00:09:21.000> there's<00:09:21.180> one<00:09:21.540> backbone<00:09:21.959> cable 00:09:22.310 --> 00:09:22.320 align:start position:0% all right so there's one backbone cable 00:09:22.320 --> 00:09:24.710 align:start position:0% all right so there's one backbone cable and<00:09:23.100> multiple<00:09:23.519> switches<00:09:23.940> are<00:09:24.180> connected<00:09:24.540> to 00:09:24.710 --> 00:09:24.720 align:start position:0% and multiple switches are connected to 00:09:24.720 --> 00:09:26.449 align:start position:0% and multiple switches are connected to that<00:09:24.959> cable 00:09:26.449 --> 00:09:26.459 align:start position:0% that cable 00:09:26.459 --> 00:09:30.470 align:start position:0% that cable which<00:09:27.000> allow<00:09:27.420> devices<00:09:28.080> to<00:09:28.680> connect<00:09:28.860> to<00:09:29.160> it 00:09:30.470 --> 00:09:30.480 align:start position:0% which allow devices to connect to it 00:09:30.480 --> 00:09:31.670 align:start position:0% which allow devices to connect to it there's<00:09:30.899> also<00:09:31.080> something<00:09:31.260> called<00:09:31.500> a 00:09:31.670 --> 00:09:31.680 align:start position:0% there's also something called a 00:09:31.680 --> 00:09:35.509 align:start position:0% there's also something called a hierarchical<00:09:32.220> or<00:09:32.580> distributed<00:09:33.360> uh 00:09:35.509 --> 00:09:35.519 align:start position:0% hierarchical or distributed uh 00:09:35.519 --> 00:09:38.210 align:start position:0% hierarchical or distributed uh um<00:09:35.640> backbone<00:09:36.420> which<00:09:36.839> like<00:09:37.080> a<00:09:37.320> family<00:09:37.500> tree<00:09:37.860> it 00:09:38.210 --> 00:09:38.220 align:start position:0% um backbone which like a family tree it 00:09:38.220 --> 00:09:40.310 align:start position:0% um backbone which like a family tree it has<00:09:38.519> more<00:09:38.700> of<00:09:38.820> a<00:09:38.940> family<00:09:39.120> tree<00:09:39.480> layout<00:09:39.899> if<00:09:40.140> you 00:09:40.310 --> 00:09:40.320 align:start position:0% has more of a family tree layout if you 00:09:40.320 --> 00:09:46.190 align:start position:0% has more of a family tree layout if you can<00:09:40.440> imagine<00:09:40.560> right 00:09:46.190 --> 00:09:46.200 align:start position:0% 00:09:46.200 --> 00:09:49.850 align:start position:0% okay<00:09:46.680> and<00:09:47.640> this<00:09:47.940> backbone<00:09:48.360> is<00:09:48.540> in<00:09:49.320> this<00:09:49.500> case 00:09:49.850 --> 00:09:49.860 align:start position:0% okay and this backbone is in this case 00:09:49.860 --> 00:09:52.730 align:start position:0% okay and this backbone is in this case it's<00:09:50.820> much<00:09:51.060> easier<00:09:51.420> to<00:09:51.660> manage<00:09:51.959> typical<00:09:52.500> for 00:09:52.730 --> 00:09:52.740 align:start position:0% it's much easier to manage typical for 00:09:52.740 --> 00:09:55.370 align:start position:0% it's much easier to manage typical for what<00:09:52.920> we'll<00:09:53.100> call<00:09:53.339> local<00:09:54.240> area<00:09:54.540> networks<00:09:55.019> or 00:09:55.370 --> 00:09:55.380 align:start position:0% what we'll call local area networks or 00:09:55.380 --> 00:09:58.550 align:start position:0% what we'll call local area networks or lands<00:09:56.279> it's<00:09:56.760> much<00:09:57.060> more<00:09:57.300> easily<00:09:57.720> scalable<00:09:58.200> as 00:09:58.550 --> 00:09:58.560 align:start position:0% lands it's much more easily scalable as 00:09:58.560 --> 00:10:00.290 align:start position:0% lands it's much more easily scalable as you<00:09:58.680> can<00:09:58.800> see<00:09:58.920> because<00:09:59.160> I<00:09:59.399> can<00:09:59.519> update<00:09:59.880> one 00:10:00.290 --> 00:10:00.300 align:start position:0% you can see because I can update one 00:10:00.300 --> 00:10:03.350 align:start position:0% you can see because I can update one part<00:10:00.540> a<00:10:00.899> lot<00:10:00.959> faster<00:10:01.320> and<00:10:02.220> in<00:10:02.459> this<00:10:02.580> case<00:10:02.820> the 00:10:03.350 --> 00:10:03.360 align:start position:0% part a lot faster and in this case the 00:10:03.360 --> 00:10:05.269 align:start position:0% part a lot faster and in this case the backbone<00:10:03.779> is<00:10:03.959> responsible<00:10:04.560> for<00:10:04.860> the<00:10:05.100> traffic 00:10:05.269 --> 00:10:05.279 align:start position:0% backbone is responsible for the traffic 00:10:05.279 --> 00:10:08.090 align:start position:0% backbone is responsible for the traffic of<00:10:05.700> the<00:10:05.880> nodes<00:10:06.060> on<00:10:06.420> each<00:10:06.720> branch<00:10:07.380> so<00:10:07.860> we<00:10:07.980> have 00:10:08.090 --> 00:10:08.100 align:start position:0% of the nodes on each branch so we have 00:10:08.100 --> 00:10:10.250 align:start position:0% of the nodes on each branch so we have different<00:10:08.279> branches<00:10:08.940> and<00:10:09.240> on<00:10:09.480> each<00:10:09.779> branch 00:10:10.250 --> 00:10:10.260 align:start position:0% different branches and on each branch 00:10:10.260 --> 00:10:12.530 align:start position:0% different branches and on each branch the<00:10:10.560> backbone<00:10:10.920> is<00:10:11.100> responsible<00:10:11.519> for<00:10:11.820> that<00:10:11.940> and 00:10:12.530 --> 00:10:12.540 align:start position:0% the backbone is responsible for that and 00:10:12.540 --> 00:10:14.690 align:start position:0% the backbone is responsible for that and that's<00:10:12.660> how<00:10:12.839> it<00:10:12.959> gets<00:10:13.200> a<00:10:13.260> little<00:10:13.320> easier<00:10:13.680> now<00:10:14.459> A 00:10:14.690 --> 00:10:14.700 align:start position:0% that's how it gets a little easier now A 00:10:14.700 --> 00:10:18.170 align:start position:0% that's how it gets a little easier now A collapsed<00:10:15.360> uh<00:10:16.320> backbone<00:10:16.920> uses<00:10:17.399> a<00:10:17.700> router<00:10:18.000> as 00:10:18.170 --> 00:10:18.180 align:start position:0% collapsed uh backbone uses a router as 00:10:18.180 --> 00:10:20.269 align:start position:0% collapsed uh backbone uses a router as the<00:10:18.300> Connecting<00:10:18.720> Point<00:10:18.959> all<00:10:19.680> right<00:10:19.860> and<00:10:20.160> we'll 00:10:20.269 --> 00:10:20.279 align:start position:0% the Connecting Point all right and we'll 00:10:20.279 --> 00:10:22.009 align:start position:0% the Connecting Point all right and we'll talk<00:10:20.519> more<00:10:20.760> about<00:10:20.940> how<00:10:21.240> that<00:10:21.420> works<00:10:21.779> a<00:10:21.899> little 00:10:22.009 --> 00:10:22.019 align:start position:0% talk more about how that works a little 00:10:22.019 --> 00:10:24.290 align:start position:0% talk more about how that works a little bit<00:10:22.200> later<00:10:22.380> and<00:10:22.980> what<00:10:23.160> exactly<00:10:23.519> a<00:10:23.700> router<00:10:24.120> does 00:10:24.290 --> 00:10:24.300 align:start position:0% bit later and what exactly a router does 00:10:24.300 --> 00:10:26.870 align:start position:0% bit later and what exactly a router does and<00:10:24.600> how<00:10:24.839> that's<00:10:25.019> different<00:10:25.339> from<00:10:26.339> a<00:10:26.700> switch 00:10:26.870 --> 00:10:26.880 align:start position:0% and how that's different from a switch 00:10:26.880 --> 00:10:29.750 align:start position:0% and how that's different from a switch and<00:10:27.480> that's<00:10:27.660> a<00:10:27.899> pretty<00:10:28.019> major<00:10:28.320> point 00:10:29.750 --> 00:10:29.760 align:start position:0% and that's a pretty major point 00:10:29.760 --> 00:10:31.970 align:start position:0% and that's a pretty major point finally<00:10:30.420> we<00:10:30.720> see<00:10:30.839> something<00:10:31.080> called<00:10:31.380> parallel 00:10:31.970 --> 00:10:31.980 align:start position:0% finally we see something called parallel 00:10:31.980 --> 00:10:34.910 align:start position:0% finally we see something called parallel which<00:10:32.519> is<00:10:32.640> just<00:10:32.880> like<00:10:33.060> a<00:10:33.360> collapsed<00:10:33.920> uh 00:10:34.910 --> 00:10:34.920 align:start position:0% which is just like a collapsed uh 00:10:34.920 --> 00:10:37.070 align:start position:0% which is just like a collapsed uh backbone<00:10:35.519> except<00:10:35.940> it<00:10:36.060> has<00:10:36.300> multiple<00:10:36.720> cable 00:10:37.070 --> 00:10:37.080 align:start position:0% backbone except it has multiple cable 00:10:37.080 --> 00:10:39.230 align:start position:0% backbone except it has multiple cable connections<00:10:37.920> and<00:10:38.399> that's<00:10:38.519> because<00:10:38.820> that 00:10:39.230 --> 00:10:39.240 align:start position:0% connections and that's because that 00:10:39.240 --> 00:10:41.509 align:start position:0% connections and that's because that allows<00:10:39.660> for<00:10:39.959> more<00:10:40.200> redundancy<00:10:40.860> remember<00:10:41.160> if 00:10:41.509 --> 00:10:41.519 align:start position:0% allows for more redundancy remember if 00:10:41.519 --> 00:10:43.130 align:start position:0% allows for more redundancy remember if you<00:10:41.640> took<00:10:41.820> the<00:10:41.940> A<00:10:42.060> Plus<00:10:42.240> Class<00:10:42.540> we<00:10:42.839> talked 00:10:43.130 --> 00:10:43.140 align:start position:0% you took the A Plus Class we talked 00:10:43.140 --> 00:10:45.530 align:start position:0% you took the A Plus Class we talked about<00:10:43.399> redundancy<00:10:44.399> and<00:10:44.640> how<00:10:44.820> we<00:10:45.060> want<00:10:45.240> to<00:10:45.360> make 00:10:45.530 --> 00:10:45.540 align:start position:0% about redundancy and how we want to make 00:10:45.540 --> 00:10:47.329 align:start position:0% about redundancy and how we want to make sure<00:10:45.779> uh<00:10:46.380> that<00:10:46.560> we<00:10:46.740> don't<00:10:46.800> have<00:10:46.920> what<00:10:47.220> are 00:10:47.329 --> 00:10:47.339 align:start position:0% sure uh that we don't have what are 00:10:47.339 --> 00:10:49.670 align:start position:0% sure uh that we don't have what are called<00:10:47.459> single<00:10:47.940> points<00:10:48.360> of<00:10:48.420> failures<00:10:48.839> so 00:10:49.670 --> 00:10:49.680 align:start position:0% called single points of failures so 00:10:49.680 --> 00:10:51.110 align:start position:0% called single points of failures so there's<00:10:49.980> more<00:10:50.279> than<00:10:50.399> one<00:10:50.640> cable<00:10:50.880> connection 00:10:51.110 --> 00:10:51.120 align:start position:0% there's more than one cable connection 00:10:51.120 --> 00:10:52.910 align:start position:0% there's more than one cable connection which<00:10:51.540> not<00:10:51.779> only<00:10:51.899> is<00:10:52.079> great<00:10:52.260> for<00:10:52.380> redundancy 00:10:52.910 --> 00:10:52.920 align:start position:0% which not only is great for redundancy 00:10:52.920 --> 00:10:55.009 align:start position:0% which not only is great for redundancy it<00:10:53.100> also<00:10:53.339> allows<00:10:53.700> for<00:10:54.240> what's<00:10:54.480> what<00:10:54.660> we<00:10:54.779> call 00:10:55.009 --> 00:10:55.019 align:start position:0% it also allows for what's what we call 00:10:55.019 --> 00:10:57.590 align:start position:0% it also allows for what's what we call load<00:10:55.500> balancing<00:10:55.980> and<00:10:56.880> also<00:10:57.180> a<00:10:57.360> faster 00:10:57.590 --> 00:10:57.600 align:start position:0% load balancing and also a faster 00:10:57.600 --> 00:10:59.810 align:start position:0% load balancing and also a faster throughput<00:10:58.079> because<00:10:58.500> the<00:10:59.100> computer<00:10:59.399> can 00:10:59.810 --> 00:10:59.820 align:start position:0% throughput because the computer can 00:10:59.820 --> 00:11:02.690 align:start position:0% throughput because the computer can decide<00:11:00.120> which<00:11:00.720> of<00:11:01.500> the<00:11:01.680> cable<00:11:01.860> connections<00:11:02.519> to 00:11:02.690 --> 00:11:02.700 align:start position:0% decide which of the cable connections to 00:11:02.700 --> 00:11:04.850 align:start position:0% decide which of the cable connections to use<00:11:02.880> all<00:11:03.480> right<00:11:03.660> so<00:11:04.019> these<00:11:04.260> are<00:11:04.320> again<00:11:04.440> we<00:11:04.740> have 00:11:04.850 --> 00:11:04.860 align:start position:0% use all right so these are again we have 00:11:04.860 --> 00:11:06.769 align:start position:0% use all right so these are again we have serial<00:11:05.279> hierarchical<00:11:05.940> or<00:11:06.180> distributed 00:11:06.769 --> 00:11:06.779 align:start position:0% serial hierarchical or distributed 00:11:06.779 --> 00:11:10.190 align:start position:0% serial hierarchical or distributed collapsed<00:11:07.500> in<00:11:07.620> parallel<00:11:08.300> as<00:11:09.300> we<00:11:09.600> talk<00:11:09.839> more 00:11:10.190 --> 00:11:10.200 align:start position:0% collapsed in parallel as we talk more 00:11:10.200 --> 00:11:12.530 align:start position:0% collapsed in parallel as we talk more about<00:11:10.440> networks<00:11:11.160> these<00:11:11.820> differences<00:11:12.300> will 00:11:12.530 --> 00:11:12.540 align:start position:0% about networks these differences will 00:11:12.540 --> 00:11:14.269 align:start position:0% about networks these differences will become<00:11:12.839> clearer<00:11:13.380> but<00:11:13.680> I<00:11:13.860> just<00:11:13.920> wanted<00:11:14.100> to 00:11:14.269 --> 00:11:14.279 align:start position:0% become clearer but I just wanted to 00:11:14.279 --> 00:11:16.069 align:start position:0% become clearer but I just wanted to cover<00:11:14.459> them<00:11:14.760> now<00:11:15.000> and<00:11:15.600> you<00:11:15.720> won't<00:11:15.839> probably 00:11:16.069 --> 00:11:16.079 align:start position:0% cover them now and you won't probably 00:11:16.079 --> 00:11:19.730 align:start position:0% cover them now and you won't probably see<00:11:16.440> these<00:11:16.800> specifically<00:11:17.399> on<00:11:17.880> the<00:11:18.240> exam<00:11:18.740> in 00:11:19.730 --> 00:11:19.740 align:start position:0% see these specifically on the exam in 00:11:19.740 --> 00:11:20.990 align:start position:0% see these specifically on the exam in this<00:11:19.920> format<00:11:20.220> you'll<00:11:20.459> see<00:11:20.579> them<00:11:20.700> in<00:11:20.820> other 00:11:20.990 --> 00:11:21.000 align:start position:0% this format you'll see them in other 00:11:21.000 --> 00:11:22.910 align:start position:0% this format you'll see them in other formats<00:11:21.540> and<00:11:21.839> but<00:11:22.200> I<00:11:22.320> want<00:11:22.440> to<00:11:22.560> lay<00:11:22.680> the 00:11:22.910 --> 00:11:22.920 align:start position:0% formats and but I want to lay the 00:11:22.920 --> 00:11:24.170 align:start position:0% formats and but I want to lay the framework<00:11:23.279> for<00:11:23.519> what<00:11:23.700> we're<00:11:23.820> going<00:11:23.940> to<00:11:24.060> be 00:11:24.170 --> 00:11:24.180 align:start position:0% framework for what we're going to be 00:11:24.180 --> 00:11:26.630 align:start position:0% framework for what we're going to be talking<00:11:24.360> about 00:11:26.630 --> 00:11:26.640 align:start position:0% 00:11:26.640 --> 00:11:29.630 align:start position:0% all<00:11:27.180> right<00:11:27.360> now<00:11:28.200> a<00:11:28.620> terminal 00:11:29.630 --> 00:11:29.640 align:start position:0% all right now a terminal 00:11:29.640 --> 00:11:32.530 align:start position:0% all right now a terminal terminal<00:11:30.300> is<00:11:30.720> a<00:11:31.140> network<00:11:31.440> Hardware<00:11:31.980> device 00:11:32.530 --> 00:11:32.540 align:start position:0% terminal is a network Hardware device 00:11:32.540 --> 00:11:36.110 align:start position:0% terminal is a network Hardware device that's<00:11:33.540> used<00:11:33.899> for<00:11:34.260> entering<00:11:34.680> date<00:11:35.040> data<00:11:35.700> into 00:11:36.110 --> 00:11:36.120 align:start position:0% that's used for entering date data into 00:11:36.120 --> 00:11:38.870 align:start position:0% that's used for entering date data into it<00:11:36.420> and<00:11:37.200> displaying<00:11:37.680> data<00:11:38.100> from<00:11:38.339> another 00:11:38.870 --> 00:11:38.880 align:start position:0% it and displaying data from another 00:11:38.880 --> 00:11:41.090 align:start position:0% it and displaying data from another computer<00:11:39.300> Computing<00:11:40.079> system 00:11:41.090 --> 00:11:41.100 align:start position:0% computer Computing system 00:11:41.100 --> 00:11:43.009 align:start position:0% computer Computing system it's<00:11:41.459> commonly<00:11:41.820> called<00:11:42.120> a<00:11:42.540> dummy<00:11:42.899> computer 00:11:43.009 --> 00:11:43.019 align:start position:0% it's commonly called a dummy computer 00:11:43.019 --> 00:11:44.810 align:start position:0% it's commonly called a dummy computer because<00:11:43.380> it<00:11:43.500> doesn't<00:11:43.680> have<00:11:43.920> any<00:11:44.220> processing 00:11:44.810 --> 00:11:44.820 align:start position:0% because it doesn't have any processing 00:11:44.820 --> 00:11:47.509 align:start position:0% because it doesn't have any processing capabilities<00:11:45.420> of<00:11:45.839> its<00:11:46.140> own<00:11:46.220> it<00:11:47.220> also<00:11:47.399> doesn't 00:11:47.509 --> 00:11:47.519 align:start position:0% capabilities of its own it also doesn't 00:11:47.519 --> 00:11:50.030 align:start position:0% capabilities of its own it also doesn't have<00:11:47.760> much<00:11:47.940> memory<00:11:48.480> or<00:11:49.200> anything<00:11:49.440> else<00:11:49.800> okay 00:11:50.030 --> 00:11:50.040 align:start position:0% have much memory or anything else okay 00:11:50.040 --> 00:11:51.889 align:start position:0% have much memory or anything else okay so<00:11:50.399> it<00:11:50.579> is<00:11:50.760> literally 00:11:51.889 --> 00:11:51.899 align:start position:0% so it is literally 00:11:51.899 --> 00:11:55.610 align:start position:0% so it is literally this<00:11:52.440> is<00:11:52.560> a<00:11:52.680> dummy<00:11:53.040> it's<00:11:53.640> basically<00:11:54.120> a<00:11:54.839> screen 00:11:55.610 --> 00:11:55.620 align:start position:0% this is a dummy it's basically a screen 00:11:55.620 --> 00:11:58.970 align:start position:0% this is a dummy it's basically a screen with<00:11:56.459> a<00:11:56.880> keyboard<00:11:57.660> a<00:11:58.260> mouse<00:11:58.380> some<00:11:58.680> sort<00:11:58.920> of 00:11:58.970 --> 00:11:58.980 align:start position:0% with a keyboard a mouse some sort of 00:11:58.980 --> 00:12:01.370 align:start position:0% with a keyboard a mouse some sort of input<00:11:59.399> tool<00:11:59.820> right<00:11:59.940> and<00:12:00.480> what<00:12:00.660> it's<00:12:00.779> doing<00:12:01.019> is 00:12:01.370 --> 00:12:01.380 align:start position:0% input tool right and what it's doing is 00:12:01.380 --> 00:12:04.850 align:start position:0% input tool right and what it's doing is simply<00:12:01.680> displaying<00:12:02.459> information<00:12:03.680> on<00:12:04.680> a 00:12:04.850 --> 00:12:04.860 align:start position:0% simply displaying information on a 00:12:04.860 --> 00:12:06.470 align:start position:0% simply displaying information on a bigger<00:12:05.100> better 00:12:06.470 --> 00:12:06.480 align:start position:0% bigger better 00:12:06.480 --> 00:12:09.829 align:start position:0% bigger better server<00:12:07.200> computer<00:12:07.440> someplace<00:12:08.220> else 00:12:09.829 --> 00:12:09.839 align:start position:0% server computer someplace else 00:12:09.839 --> 00:12:13.850 align:start position:0% server computer someplace else all<00:12:10.260> right 00:12:13.850 --> 00:12:13.860 align:start position:0% 00:12:13.860 --> 00:12:16.069 align:start position:0% we<00:12:14.399> also<00:12:14.640> need<00:12:14.820> something<00:12:15.060> called<00:12:15.360> a<00:12:15.660> terminal 00:12:16.069 --> 00:12:16.079 align:start position:0% we also need something called a terminal 00:12:16.079 --> 00:12:19.190 align:start position:0% we also need something called a terminal emulator<00:12:16.700> placed<00:12:17.700> onto<00:12:18.060> this<00:12:18.240> computer<00:12:18.480> so 00:12:19.190 --> 00:12:19.200 align:start position:0% emulator placed onto this computer so 00:12:19.200 --> 00:12:21.170 align:start position:0% emulator placed onto this computer so that<00:12:19.380> it<00:12:19.560> can<00:12:19.740> emulate<00:12:20.279> what's<00:12:20.579> going<00:12:20.820> on<00:12:20.940> on 00:12:21.170 --> 00:12:21.180 align:start position:0% that it can emulate what's going on on 00:12:21.180 --> 00:12:22.790 align:start position:0% that it can emulate what's going on on the<00:12:21.300> server<00:12:21.600> and<00:12:21.779> communicate<00:12:22.200> with<00:12:22.380> it<00:12:22.560> since 00:12:22.790 --> 00:12:22.800 align:start position:0% the server and communicate with it since 00:12:22.800 --> 00:12:24.590 align:start position:0% the server and communicate with it since it<00:12:22.980> doesn't<00:12:23.160> have<00:12:23.399> processing<00:12:24.060> capabilities 00:12:24.590 --> 00:12:24.600 align:start position:0% it doesn't have processing capabilities 00:12:24.600 --> 00:12:26.930 align:start position:0% it doesn't have processing capabilities or<00:12:24.959> memory<00:12:25.260> of<00:12:25.380> its<00:12:25.620> own<00:12:26.220> now<00:12:26.640> this<00:12:26.760> is 00:12:26.930 --> 00:12:26.940 align:start position:0% or memory of its own now this is 00:12:26.940 --> 00:12:30.050 align:start position:0% or memory of its own now this is different<00:12:27.120> from<00:12:27.540> what's<00:12:27.779> called<00:12:28.079> a<00:12:28.680> client 00:12:30.050 --> 00:12:30.060 align:start position:0% different from what's called a client 00:12:30.060 --> 00:12:33.050 align:start position:0% different from what's called a client a<00:12:30.600> client<00:12:30.839> has<00:12:31.200> its<00:12:31.560> own<00:12:31.620> processor<00:12:32.339> and 00:12:33.050 --> 00:12:33.060 align:start position:0% a client has its own processor and 00:12:33.060 --> 00:12:36.230 align:start position:0% a client has its own processor and memory<00:12:33.420> of<00:12:33.600> its<00:12:33.899> own<00:12:34.160> but<00:12:35.160> it<00:12:35.640> accesses 00:12:36.230 --> 00:12:36.240 align:start position:0% memory of its own but it accesses 00:12:36.240 --> 00:12:39.410 align:start position:0% memory of its own but it accesses network<00:12:36.660> resources<00:12:37.620> on<00:12:38.399> other<00:12:38.640> nodes<00:12:39.000> other 00:12:39.410 --> 00:12:39.420 align:start position:0% network resources on other nodes other 00:12:39.420 --> 00:12:41.449 align:start position:0% network resources on other nodes other servers<00:12:39.959> and<00:12:40.140> other<00:12:40.320> clients 00:12:41.449 --> 00:12:41.459 align:start position:0% servers and other clients 00:12:41.459 --> 00:12:44.690 align:start position:0% servers and other clients all<00:12:41.820> right<00:12:41.940> so<00:12:42.600> it<00:12:43.019> is<00:12:43.680> um<00:12:43.740> rather<00:12:44.040> than<00:12:44.220> a 00:12:44.690 --> 00:12:44.700 align:start position:0% all right so it is um rather than a 00:12:44.700 --> 00:12:47.810 align:start position:0% all right so it is um rather than a server<00:12:45.060> which<00:12:45.540> serves<00:12:46.019> up<00:12:46.320> information<00:12:46.820> the 00:12:47.810 --> 00:12:47.820 align:start position:0% server which serves up information the 00:12:47.820 --> 00:12:51.590 align:start position:0% server which serves up information the client<00:12:48.120> takes<00:12:48.660> the<00:12:48.899> information<00:12:49.079> and<00:12:49.560> uses<00:12:49.860> it 00:12:51.590 --> 00:12:51.600 align:start position:0% client takes the information and uses it 00:12:51.600 --> 00:12:53.629 align:start position:0% client takes the information and uses it now<00:12:52.139> appear 00:12:53.629 --> 00:12:53.639 align:start position:0% now appear 00:12:53.639 --> 00:12:56.150 align:start position:0% now appear is<00:12:54.120> a<00:12:54.300> network<00:12:54.420> computer<00:12:54.779> that<00:12:55.260> provides<00:12:55.740> its 00:12:56.150 --> 00:12:56.160 align:start position:0% is a network computer that provides its 00:12:56.160 --> 00:12:59.090 align:start position:0% is a network computer that provides its own<00:12:56.279> resources<00:12:57.000> and<00:12:57.480> services<00:12:57.720> and<00:12:58.680> computes 00:12:59.090 --> 00:12:59.100 align:start position:0% own resources and services and computes 00:12:59.100 --> 00:13:01.730 align:start position:0% own resources and services and computes on<00:12:59.399> its<00:12:59.639> own<00:12:59.700> the<00:13:00.660> best<00:13:00.779> thing<00:13:00.959> about<00:13:01.200> appear 00:13:01.730 --> 00:13:01.740 align:start position:0% on its own the best thing about appear 00:13:01.740 --> 00:13:04.670 align:start position:0% on its own the best thing about appear is<00:13:02.040> that<00:13:02.220> it<00:13:02.339> can<00:13:02.519> act<00:13:02.839> it<00:13:03.839> is<00:13:04.019> self-managed 00:13:04.670 --> 00:13:04.680 align:start position:0% is that it can act it is self-managed 00:13:04.680 --> 00:13:08.990 align:start position:0% is that it can act it is self-managed self-contained<00:13:05.519> and<00:13:06.240> it<00:13:06.720> is<00:13:06.839> both<00:13:07.079> a<00:13:07.440> server 00:13:08.990 --> 00:13:09.000 align:start position:0% self-contained and it is both a server 00:13:09.000 --> 00:13:11.870 align:start position:0% self-contained and it is both a server and<00:13:09.540> a<00:13:09.720> client 00:13:11.870 --> 00:13:11.880 align:start position:0% and a client 00:13:11.880 --> 00:13:15.170 align:start position:0% and a client okay 00:13:15.170 --> 00:13:15.180 align:start position:0% 00:13:15.180 --> 00:13:18.230 align:start position:0% so<00:13:15.600> you<00:13:15.660> can<00:13:15.779> see<00:13:15.959> how<00:13:16.139> this<00:13:16.320> works<00:13:16.740> this 00:13:18.230 --> 00:13:18.240 align:start position:0% so you can see how this works this 00:13:18.240 --> 00:13:20.870 align:start position:0% so you can see how this works this cloth<00:13:18.720> this<00:13:18.959> peer<00:13:19.260> computer<00:13:19.880> serves 00:13:20.870 --> 00:13:20.880 align:start position:0% cloth this peer computer serves 00:13:20.880 --> 00:13:23.389 align:start position:0% cloth this peer computer serves information<00:13:21.120> to<00:13:21.839> this<00:13:22.139> peer<00:13:22.740> computer<00:13:22.920> as<00:13:23.220> a 00:13:23.389 --> 00:13:23.399 align:start position:0% information to this peer computer as a 00:13:23.399 --> 00:13:26.389 align:start position:0% information to this peer computer as a client<00:13:23.660> this<00:13:24.660> computer<00:13:25.260> can<00:13:26.040> serve 00:13:26.389 --> 00:13:26.399 align:start position:0% client this computer can serve 00:13:26.399 --> 00:13:28.310 align:start position:0% client this computer can serve information<00:13:26.579> to<00:13:26.940> this<00:13:27.120> one<00:13:27.240> as<00:13:27.420> a<00:13:27.540> client<00:13:27.720> so 00:13:28.310 --> 00:13:28.320 align:start position:0% information to this one as a client so 00:13:28.320 --> 00:13:30.230 align:start position:0% information to this one as a client so this<00:13:28.680> is<00:13:28.800> what<00:13:28.920> we<00:13:29.040> call<00:13:29.240> peer-to-peer 00:13:30.230 --> 00:13:30.240 align:start position:0% this is what we call peer-to-peer 00:13:30.240 --> 00:13:32.990 align:start position:0% this is what we call peer-to-peer networking<00:13:31.079> it<00:13:31.860> manages<00:13:32.160> its<00:13:32.579> own<00:13:32.639> set<00:13:32.880> of 00:13:32.990 --> 00:13:33.000 align:start position:0% networking it manages its own set of 00:13:33.000 --> 00:13:35.030 align:start position:0% networking it manages its own set of local<00:13:33.240> policies<00:13:33.839> it<00:13:34.139> has<00:13:34.260> its<00:13:34.560> own<00:13:34.620> set<00:13:34.860> of 00:13:35.030 --> 00:13:35.040 align:start position:0% local policies it has its own set of 00:13:35.040 --> 00:13:37.670 align:start position:0% local policies it has its own set of users<00:13:35.459> it<00:13:36.360> is<00:13:36.480> completely<00:13:36.839> self-contained 00:13:37.670 --> 00:13:37.680 align:start position:0% users it is completely self-contained 00:13:37.680 --> 00:13:40.069 align:start position:0% users it is completely self-contained and<00:13:37.800> does<00:13:38.100> not<00:13:38.339> need<00:13:38.760> a<00:13:39.240> server<00:13:39.540> to<00:13:39.720> operate 00:13:40.069 --> 00:13:40.079 align:start position:0% and does not need a server to operate 00:13:40.079 --> 00:13:44.389 align:start position:0% and does not need a server to operate unlike<00:13:40.500> a<00:13:40.680> client<00:13:41.040> which<00:13:41.519> does 00:13:44.389 --> 00:13:44.399 align:start position:0% 00:13:44.399 --> 00:13:45.590 align:start position:0% all<00:13:44.880> right 00:13:45.590 --> 00:13:45.600 align:start position:0% all right 00:13:45.600 --> 00:13:47.150 align:start position:0% all right so 00:13:47.150 --> 00:13:47.160 align:start position:0% so 00:13:47.160 --> 00:13:49.790 align:start position:0% so just<00:13:47.700> to<00:13:47.880> recap<00:13:48.180> what<00:13:48.360> we've<00:13:48.540> talked<00:13:48.839> about<00:13:48.899> we 00:13:49.790 --> 00:13:49.800 align:start position:0% just to recap what we've talked about we 00:13:49.800 --> 00:13:52.610 align:start position:0% just to recap what we've talked about we were<00:13:49.980> we<00:13:50.279> we<00:13:50.399> defined<00:13:51.120> what<00:13:51.480> a<00:13:51.660> network<00:13:51.779> is<00:13:52.139> and 00:13:52.610 --> 00:13:52.620 align:start position:0% were we we defined what a network is and 00:13:52.620 --> 00:13:54.230 align:start position:0% were we we defined what a network is and how<00:13:52.800> that's<00:13:52.920> different<00:13:53.160> slightly<00:13:53.700> from<00:13:54.000> a 00:13:54.230 --> 00:13:54.240 align:start position:0% how that's different slightly from a 00:13:54.240 --> 00:13:56.449 align:start position:0% how that's different slightly from a computer<00:13:54.959> network<00:13:55.380> which<00:13:55.800> is<00:13:55.920> really<00:13:56.160> what 00:13:56.449 --> 00:13:56.459 align:start position:0% computer network which is really what 00:13:56.459 --> 00:13:58.670 align:start position:0% computer network which is really what the<00:13:56.639> network<00:13:56.700> plus<00:13:57.000> exam<00:13:57.420> covers 00:13:58.670 --> 00:13:58.680 align:start position:0% the network plus exam covers 00:13:58.680 --> 00:14:00.829 align:start position:0% the network plus exam covers we<00:13:59.040> describe<00:13:59.399> the<00:13:59.519> components<00:14:00.240> of<00:14:00.660> the 00:14:00.829 --> 00:14:00.839 align:start position:0% we describe the components of the 00:14:00.839 --> 00:14:02.750 align:start position:0% we describe the components of the network 00:14:02.750 --> 00:14:02.760 align:start position:0% network 00:14:02.760 --> 00:14:05.210 align:start position:0% network uh<00:14:03.540> the<00:14:03.839> adapter 00:14:05.210 --> 00:14:05.220 align:start position:0% uh the adapter 00:14:05.220 --> 00:14:07.910 align:start position:0% uh the adapter the<00:14:05.579> network<00:14:05.760> operating<00:14:06.240> system<00:14:06.660> the<00:14:07.620> devices 00:14:07.910 --> 00:14:07.920 align:start position:0% the network operating system the devices 00:14:07.920 --> 00:14:10.370 align:start position:0% the network operating system the devices the<00:14:08.880> media<00:14:09.240> let's<00:14:09.600> go<00:14:09.779> ahead<00:14:09.839> and<00:14:10.019> write<00:14:10.200> those 00:14:10.370 --> 00:14:10.380 align:start position:0% the media let's go ahead and write those 00:14:10.380 --> 00:14:11.990 align:start position:0% the media let's go ahead and write those we<00:14:10.680> had<00:14:10.800> media 00:14:11.990 --> 00:14:12.000 align:start position:0% we had media 00:14:12.000 --> 00:14:14.210 align:start position:0% we had media right<00:14:12.540> which<00:14:12.959> allowed<00:14:13.320> the<00:14:13.500> devices<00:14:13.740> to 00:14:14.210 --> 00:14:14.220 align:start position:0% right which allowed the devices to 00:14:14.220 --> 00:14:17.170 align:start position:0% right which allowed the devices to communicate 00:14:17.170 --> 00:14:17.180 align:start position:0% 00:14:17.180 --> 00:14:26.449 align:start position:0% using<00:14:18.180> a<00:14:19.019> network<00:14:19.500> adapter 00:14:26.449 --> 00:14:26.459 align:start position:0% 00:14:26.459 --> 00:14:29.210 align:start position:0% communicated<00:14:27.360> and<00:14:28.139> managed<00:14:28.440> by<00:14:28.620> an<00:14:28.860> operating 00:14:29.210 --> 00:14:29.220 align:start position:0% communicated and managed by an operating 00:14:29.220 --> 00:14:32.090 align:start position:0% communicated and managed by an operating system<00:14:29.519> we<00:14:30.480> also<00:14:30.720> defined<00:14:31.079> a<00:14:31.260> node<00:14:31.500> and<00:14:31.680> server 00:14:32.090 --> 00:14:32.100 align:start position:0% system we also defined a node and server 00:14:32.100 --> 00:14:35.930 align:start position:0% system we also defined a node and server right<00:14:32.760> the<00:14:33.120> node<00:14:33.420> is<00:14:34.019> really<00:14:34.260> any 00:14:35.930 --> 00:14:35.940 align:start position:0% right the node is really any 00:14:35.940 --> 00:14:36.829 align:start position:0% right the node is really any um 00:14:36.829 --> 00:14:36.839 align:start position:0% um 00:14:36.839 --> 00:14:39.410 align:start position:0% um sort<00:14:37.320> of<00:14:37.440> device<00:14:37.800> that's<00:14:38.100> on<00:14:38.279> we<00:14:38.700> have<00:14:38.820> the<00:14:39.180> end 00:14:39.410 --> 00:14:39.420 align:start position:0% sort of device that's on we have the end 00:14:39.420 --> 00:14:43.069 align:start position:0% sort of device that's on we have the end point 00:14:43.069 --> 00:14:43.079 align:start position:0% 00:14:43.079 --> 00:14:44.810 align:start position:0% and<00:14:43.500> we<00:14:43.620> also 00:14:44.810 --> 00:14:44.820 align:start position:0% and we also 00:14:44.820 --> 00:14:51.470 align:start position:0% and we also have<00:14:45.240> a<00:14:45.420> redistribution 00:14:51.470 --> 00:14:51.480 align:start position:0% 00:14:51.480 --> 00:14:53.150 align:start position:0% we<00:14:52.019> Define<00:14:52.199> and<00:14:52.440> describe<00:14:52.800> the<00:14:52.920> network 00:14:53.150 --> 00:14:53.160 align:start position:0% we Define and describe the network 00:14:53.160 --> 00:15:00.829 align:start position:0% we Define and describe the network backbone<00:14:54.000> remember<00:14:54.540> which<00:14:54.959> is<00:14:55.199> really<00:14:55.920> fast 00:15:00.829 --> 00:15:00.839 align:start position:0% 00:15:00.839 --> 00:15:03.949 align:start position:0% and<00:15:01.560> the<00:15:01.860> different<00:15:02.040> variations<00:15:02.579> of<00:15:02.880> it<00:15:03.540> which 00:15:03.949 --> 00:15:03.959 align:start position:0% and the different variations of it which 00:15:03.959 --> 00:15:06.470 align:start position:0% and the different variations of it which if<00:15:04.139> you<00:15:04.260> recall<00:15:04.680> included<00:15:05.519> cereal<00:15:06.180> which<00:15:06.360> is 00:15:06.470 --> 00:15:06.480 align:start position:0% if you recall included cereal which is 00:15:06.480 --> 00:15:08.750 align:start position:0% if you recall included cereal which is one<00:15:06.660> after<00:15:06.839> the<00:15:07.139> other 00:15:08.750 --> 00:15:08.760 align:start position:0% one after the other 00:15:08.760 --> 00:15:13.009 align:start position:0% one after the other hierarchical 00:15:13.009 --> 00:15:13.019 align:start position:0% 00:15:13.019 --> 00:15:20.150 align:start position:0% also<00:15:13.560> called<00:15:13.740> distributed 00:15:20.150 --> 00:15:20.160 align:start position:0% 00:15:20.160 --> 00:15:23.509 align:start position:0% then<00:15:20.459> we<00:15:20.639> looked<00:15:20.880> at<00:15:21.000> collapsed 00:15:23.509 --> 00:15:23.519 align:start position:0% then we looked at collapsed 00:15:23.519 --> 00:15:25.790 align:start position:0% then we looked at collapsed and<00:15:24.000> a<00:15:24.180> more<00:15:24.300> redundant<00:15:24.660> form 00:15:25.790 --> 00:15:25.800 align:start position:0% and a more redundant form 00:15:25.800 --> 00:15:27.710 align:start position:0% and a more redundant form parallel 00:15:27.710 --> 00:15:27.720 align:start position:0% parallel 00:15:27.720 --> 00:15:30.470 align:start position:0% parallel finally<00:15:28.380> we<00:15:28.560> defined<00:15:29.040> terminal<00:15:29.699> client<00:15:30.120> and 00:15:30.470 --> 00:15:30.480 align:start position:0% finally we defined terminal client and 00:15:30.480 --> 00:15:33.889 align:start position:0% finally we defined terminal client and appear<00:15:30.779> remember<00:15:31.260> the<00:15:31.620> terminal<00:15:31.980> is<00:15:32.459> a<00:15:32.760> dummy 00:15:33.889 --> 00:15:33.899 align:start position:0% appear remember the terminal is a dummy 00:15:33.899 --> 00:15:38.750 align:start position:0% appear remember the terminal is a dummy client<00:15:34.560> accesses<00:15:35.279> resources 00:15:38.750 --> 00:15:38.760 align:start position:0% 00:15:38.760 --> 00:15:40.670 align:start position:0% on<00:15:39.240> other<00:15:39.420> computers 00:15:40.670 --> 00:15:40.680 align:start position:0% on other computers 00:15:40.680 --> 00:15:44.870 align:start position:0% on other computers and<00:15:41.100> appear<00:15:41.459> both<00:15:42.240> serves 00:15:44.870 --> 00:15:44.880 align:start position:0% 00:15:44.880 --> 00:15:48.530 align:start position:0% and<00:15:45.360> accesses 00:15:48.530 --> 00:15:48.540 align:start position:0% 00:15:48.540 --> 00:15:50.449 align:start position:0% all<00:15:48.959> right<00:15:49.139> so<00:15:49.560> now<00:15:49.680> that<00:15:49.800> we've<00:15:49.980> covered<00:15:50.279> some 00:15:50.449 --> 00:15:50.459 align:start position:0% all right so now that we've covered some 00:15:50.459 --> 00:15:52.550 align:start position:0% all right so now that we've covered some of<00:15:50.579> this<00:15:50.699> basic<00:15:51.060> terminology<00:15:51.540> let's<00:15:52.260> continue 00:15:52.550 --> 00:15:52.560 align:start position:0% of this basic terminology let's continue 00:15:52.560 --> 00:15:54.769 align:start position:0% of this basic terminology let's continue on<00:15:52.980> talking<00:15:53.279> about<00:15:53.579> the<00:15:54.000> fundamentals<00:15:54.540> of<00:15:54.660> a 00:15:54.769 --> 00:15:54.779 align:start position:0% on talking about the fundamentals of a 00:15:54.779 --> 00:15:57.889 align:start position:0% on talking about the fundamentals of a network<00:15:54.959> And<00:15:55.800> discussing<00:15:56.399> more<00:15:56.760> of<00:15:57.180> what<00:15:57.779> we 00:15:57.889 --> 00:15:57.899 align:start position:0% network And discussing more of what we 00:15:57.899 --> 00:15:59.509 align:start position:0% network And discussing more of what we need<00:15:58.079> to<00:15:58.199> know<00:15:58.320> in<00:15:58.620> order<00:15:58.740> to<00:15:58.920> get<00:15:59.040> into<00:15:59.220> the 00:15:59.509 --> 00:15:59.519 align:start position:0% need to know in order to get into the 00:15:59.519 --> 00:16:01.910 align:start position:0% need to know in order to get into the majority<00:15:59.880> of<00:16:00.180> this<00:16:00.540> uh<00:16:00.959> information<00:16:01.380> on<00:16:01.800> the 00:16:01.910 --> 00:16:01.920 align:start position:0% majority of this uh information on the 00:16:01.920 --> 00:16:06.450 align:start position:0% majority of this uh information on the network<00:16:01.980> plus<00:16:02.279> exam 00:16:06.450 --> 00:16:06.460 align:start position:0% 00:16:06.460 --> 00:16:15.129 align:start position:0% [Music] 00:16:15.129 --> 00:16:15.139 align:start position:0% [Music] 00:16:15.139 --> 00:16:26.350 align:start position:0% [Music] thank<00:16:16.139> you 00:16:26.350 --> 00:16:26.360 align:start position:0% 00:16:26.360 --> 00:16:30.050 align:start position:0% Network<00:16:27.360> fundamentals<00:16:28.800> Network<00:16:29.339> categories 00:16:30.050 --> 00:16:30.060 align:start position:0% Network fundamentals Network categories 00:16:30.060 --> 00:16:31.910 align:start position:0% Network fundamentals Network categories and<00:16:30.600> models 00:16:31.910 --> 00:16:31.920 align:start position:0% and models 00:16:31.920 --> 00:16:33.769 align:start position:0% and models having<00:16:32.339> discussed<00:16:33.000> some<00:16:33.240> of<00:16:33.360> the<00:16:33.540> basic 00:16:33.769 --> 00:16:33.779 align:start position:0% having discussed some of the basic 00:16:33.779 --> 00:16:35.870 align:start position:0% having discussed some of the basic components<00:16:34.260> of<00:16:34.380> a<00:16:34.500> network<00:16:34.680> and<00:16:35.519> having 00:16:35.870 --> 00:16:35.880 align:start position:0% components of a network and having 00:16:35.880 --> 00:16:37.910 align:start position:0% components of a network and having established<00:16:36.540> sort<00:16:36.779> of<00:16:36.899> a<00:16:37.019> baseline<00:16:37.500> of<00:16:37.680> some 00:16:37.910 --> 00:16:37.920 align:start position:0% established sort of a baseline of some 00:16:37.920 --> 00:16:39.290 align:start position:0% established sort of a baseline of some terminology<00:16:38.399> that<00:16:38.699> we<00:16:38.880> all<00:16:38.940> need<00:16:39.120> to<00:16:39.180> be 00:16:39.290 --> 00:16:39.300 align:start position:0% terminology that we all need to be 00:16:39.300 --> 00:16:41.389 align:start position:0% terminology that we all need to be familiar<00:16:39.600> with<00:16:39.839> I<00:16:40.500> now<00:16:40.620> want<00:16:40.920> to<00:16:41.100> talk<00:16:41.220> about 00:16:41.389 --> 00:16:41.399 align:start position:0% familiar with I now want to talk about 00:16:41.399 --> 00:16:44.509 align:start position:0% familiar with I now want to talk about the<00:16:41.699> different<00:16:41.880> categories<00:16:42.839> of<00:16:43.259> networks<00:16:43.860> and 00:16:44.509 --> 00:16:44.519 align:start position:0% the different categories of networks and 00:16:44.519 --> 00:16:46.069 align:start position:0% the different categories of networks and as<00:16:44.699> we<00:16:44.880> begin<00:16:45.000> to<00:16:45.300> understand<00:16:45.480> the 00:16:46.069 --> 00:16:46.079 align:start position:0% as we begin to understand the 00:16:46.079 --> 00:16:47.749 align:start position:0% as we begin to understand the differences<00:16:46.440> between<00:16:46.860> these<00:16:47.279> categories 00:16:47.749 --> 00:16:47.759 align:start position:0% differences between these categories 00:16:47.759 --> 00:16:49.430 align:start position:0% differences between these categories we're<00:16:48.300> also<00:16:48.540> going<00:16:48.600> to<00:16:48.660> look<00:16:48.779> at<00:16:49.019> some<00:16:49.199> of<00:16:49.320> the 00:16:49.430 --> 00:16:49.440 align:start position:0% we're also going to look at some of the 00:16:49.440 --> 00:16:52.129 align:start position:0% we're also going to look at some of the basic<00:16:49.860> models<00:16:50.579> that<00:16:51.240> networks<00:16:51.660> are<00:16:51.779> placed 00:16:52.129 --> 00:16:52.139 align:start position:0% basic models that networks are placed 00:16:52.139 --> 00:16:53.569 align:start position:0% basic models that networks are placed into<00:16:52.380> depending<00:16:53.220> on<00:16:53.399> different 00:16:53.569 --> 00:16:53.579 align:start position:0% into depending on different 00:16:53.579 --> 00:16:55.910 align:start position:0% into depending on different configurations<00:16:54.420> and<00:16:54.839> layouts 00:16:55.910 --> 00:16:55.920 align:start position:0% configurations and layouts 00:16:55.920 --> 00:16:59.329 align:start position:0% configurations and layouts so<00:16:56.639> our<00:16:57.000> objectives<00:16:57.420> in<00:16:57.720> this<00:16:57.959> module<00:16:58.440> are 00:16:59.329 --> 00:16:59.339 align:start position:0% so our objectives in this module are 00:16:59.339 --> 00:17:02.030 align:start position:0% so our objectives in this module are first<00:16:59.639> to<00:17:00.000> describe<00:17:00.480> the<00:17:00.959> characteristics<00:17:01.680> of 00:17:02.030 --> 00:17:02.040 align:start position:0% first to describe the characteristics of 00:17:02.040 --> 00:17:06.530 align:start position:0% first to describe the characteristics of a<00:17:02.160> lan<00:17:02.519> or<00:17:03.180> what's<00:17:03.480> called<00:17:03.779> a<00:17:04.439> local 00:17:06.530 --> 00:17:06.540 align:start position:0% a lan or what's called a local 00:17:06.540 --> 00:17:10.130 align:start position:0% a lan or what's called a local area<00:17:07.199> network<00:17:08.120> now<00:17:09.120> this<00:17:09.299> is<00:17:09.419> different<00:17:09.660> from 00:17:10.130 --> 00:17:10.140 align:start position:0% area network now this is different from 00:17:10.140 --> 00:17:13.789 align:start position:0% area network now this is different from a<00:17:10.559> Wan<00:17:10.919> or<00:17:11.339> a<00:17:11.600> wide<00:17:12.600> area<00:17:12.900> network<00:17:13.319> you're 00:17:13.789 --> 00:17:13.799 align:start position:0% a Wan or a wide area network you're 00:17:13.799 --> 00:17:14.929 align:start position:0% a Wan or a wide area network you're going<00:17:13.919> to<00:17:13.980> need<00:17:14.100> to<00:17:14.160> be<00:17:14.220> familiar<00:17:14.520> with<00:17:14.640> both 00:17:14.929 --> 00:17:14.939 align:start position:0% going to need to be familiar with both 00:17:14.939 --> 00:17:16.250 align:start position:0% going to need to be familiar with both of<00:17:15.059> these<00:17:15.240> terms<00:17:15.540> and<00:17:15.720> actually<00:17:15.839> we're<00:17:16.140> going 00:17:16.250 --> 00:17:16.260 align:start position:0% of these terms and actually we're going 00:17:16.260 --> 00:17:19.210 align:start position:0% of these terms and actually we're going to<00:17:16.380> see<00:17:16.620> a<00:17:17.160> few<00:17:17.339> different<00:17:17.579> types<00:17:18.240> of<00:17:18.419> lands 00:17:19.210 --> 00:17:19.220 align:start position:0% to see a few different types of lands 00:17:19.220 --> 00:17:23.210 align:start position:0% to see a few different types of lands including<00:17:20.220> uh<00:17:21.000> man's 00:17:23.210 --> 00:17:23.220 align:start position:0% including uh man's 00:17:23.220 --> 00:17:26.870 align:start position:0% including uh man's pans 00:17:26.870 --> 00:17:26.880 align:start position:0% 00:17:26.880 --> 00:17:28.850 align:start position:0% cans 00:17:28.850 --> 00:17:28.860 align:start position:0% cans 00:17:28.860 --> 00:17:31.669 align:start position:0% cans and<00:17:29.700> uh<00:17:30.000> none<00:17:30.360> of<00:17:30.480> these<00:17:30.720> are<00:17:31.020> what<00:17:31.440> you<00:17:31.559> think 00:17:31.669 --> 00:17:31.679 align:start position:0% and uh none of these are what you think 00:17:31.679 --> 00:17:34.010 align:start position:0% and uh none of these are what you think these<00:17:31.980> are<00:17:32.100> all<00:17:32.220> acronyms<00:17:33.000> so<00:17:33.299> a<00:17:33.480> man<00:17:33.660> is<00:17:33.900> a 00:17:34.010 --> 00:17:34.020 align:start position:0% these are all acronyms so a man is a 00:17:34.020 --> 00:17:36.370 align:start position:0% these are all acronyms so a man is a metropolitan<00:17:34.799> or<00:17:35.280> a<00:17:35.400> municipal<00:17:35.820> area<00:17:36.059> network 00:17:36.370 --> 00:17:36.380 align:start position:0% metropolitan or a municipal area network 00:17:36.380 --> 00:17:39.289 align:start position:0% metropolitan or a municipal area network uh<00:17:37.380> pan<00:17:37.740> is<00:17:37.980> a<00:17:38.160> personal<00:17:38.280> area<00:17:38.580> network<00:17:38.880> can 00:17:39.289 --> 00:17:39.299 align:start position:0% uh pan is a personal area network can 00:17:39.299 --> 00:17:41.930 align:start position:0% uh pan is a personal area network can campus<00:17:39.840> area<00:17:40.020> network<00:17:40.620> etc<00:17:40.980> etc<00:17:41.160> and<00:17:41.700> as<00:17:41.820> you 00:17:41.930 --> 00:17:41.940 align:start position:0% campus area network etc etc and as you 00:17:41.940 --> 00:17:44.150 align:start position:0% campus area network etc etc and as you can<00:17:42.059> see<00:17:42.179> from<00:17:42.539> the<00:17:42.720> name<00:17:42.900> these<00:17:43.440> these<00:17:43.799> terms 00:17:44.150 --> 00:17:44.160 align:start position:0% can see from the name these these terms 00:17:44.160 --> 00:17:45.230 align:start position:0% can see from the name these these terms are<00:17:44.400> really 00:17:45.230 --> 00:17:45.240 align:start position:0% are really 00:17:45.240 --> 00:17:48.529 align:start position:0% are really um<00:17:45.780> amorphous<00:17:46.620> so<00:17:47.160> it<00:17:47.820> really<00:17:48.000> depends<00:17:48.360> on 00:17:48.529 --> 00:17:48.539 align:start position:0% um amorphous so it really depends on 00:17:48.539 --> 00:17:51.470 align:start position:0% um amorphous so it really depends on some<00:17:48.780> subjective<00:17:49.500> uh<00:17:50.400> opinions<00:17:50.820> as<00:17:51.059> to<00:17:51.240> what 00:17:51.470 --> 00:17:51.480 align:start position:0% some subjective uh opinions as to what 00:17:51.480 --> 00:17:52.490 align:start position:0% some subjective uh opinions as to what these 00:17:52.490 --> 00:17:52.500 align:start position:0% these 00:17:52.500 --> 00:17:55.130 align:start position:0% these types<00:17:53.220> of<00:17:53.700> networks<00:17:54.240> really<00:17:54.480> described<00:17:54.900> but 00:17:55.130 --> 00:17:55.140 align:start position:0% types of networks really described but 00:17:55.140 --> 00:17:56.570 align:start position:0% types of networks really described but anyway<00:17:55.260> we're<00:17:55.500> going<00:17:55.679> to<00:17:55.740> cover<00:17:55.919> all<00:17:56.340> of<00:17:56.460> those 00:17:56.570 --> 00:17:56.580 align:start position:0% anyway we're going to cover all of those 00:17:56.580 --> 00:17:58.310 align:start position:0% anyway we're going to cover all of those so<00:17:56.880> you'll<00:17:57.059> be<00:17:57.179> prepared<00:17:57.480> for<00:17:57.660> them<00:17:57.780> if<00:17:57.960> if<00:17:58.140> and 00:17:58.310 --> 00:17:58.320 align:start position:0% so you'll be prepared for them if if and 00:17:58.320 --> 00:17:59.810 align:start position:0% so you'll be prepared for them if if and when<00:17:58.500> you<00:17:58.620> see<00:17:58.799> them<00:17:58.980> out<00:17:59.160> in<00:17:59.280> the<00:17:59.340> field<00:17:59.460> or<00:17:59.640> on 00:17:59.810 --> 00:17:59.820 align:start position:0% when you see them out in the field or on 00:17:59.820 --> 00:18:01.669 align:start position:0% when you see them out in the field or on the<00:18:00.000> test<00:18:00.179> we're<00:18:00.900> also<00:18:01.140> going<00:18:01.200> to<00:18:01.260> define<00:18:01.440> the 00:18:01.669 --> 00:18:01.679 align:start position:0% the test we're also going to define the 00:18:01.679 --> 00:18:02.570 align:start position:0% the test we're also going to define the difference<00:18:01.799> between<00:18:01.980> the<00:18:02.340> internet 00:18:02.570 --> 00:18:02.580 align:start position:0% difference between the internet 00:18:02.580 --> 00:18:04.190 align:start position:0% difference between the internet something<00:18:03.179> that<00:18:03.360> I'm<00:18:03.480> sure<00:18:03.600> you<00:18:03.780> all<00:18:04.020> have 00:18:04.190 --> 00:18:04.200 align:start position:0% something that I'm sure you all have 00:18:04.200 --> 00:18:06.409 align:start position:0% something that I'm sure you all have heard<00:18:04.440> of<00:18:04.620> and<00:18:05.160> then<00:18:05.280> two<00:18:05.520> other<00:18:05.700> terms<00:18:06.120> the 00:18:06.409 --> 00:18:06.419 align:start position:0% heard of and then two other terms the 00:18:06.419 --> 00:18:10.370 align:start position:0% heard of and then two other terms the intranet<00:18:07.320> and<00:18:07.919> the<00:18:08.160> extranat<00:18:08.940> which<00:18:09.780> are<00:18:10.080> more 00:18:10.370 --> 00:18:10.380 align:start position:0% intranet and the extranat which are more 00:18:10.380 --> 00:18:14.029 align:start position:0% intranet and the extranat which are more uh<00:18:10.860> specific<00:18:11.280> towards<00:18:12.260> organizations<00:18:13.260> and 00:18:14.029 --> 00:18:14.039 align:start position:0% uh specific towards organizations and 00:18:14.039 --> 00:18:16.750 align:start position:0% uh specific towards organizations and sort<00:18:14.340> of<00:18:14.520> uh<00:18:14.880> uh<00:18:15.539> using<00:18:16.380> internet 00:18:16.750 --> 00:18:16.760 align:start position:0% sort of uh uh using internet 00:18:16.760 --> 00:18:19.250 align:start position:0% sort of uh uh using internet Technologies<00:18:17.760> uh<00:18:18.539> for<00:18:18.840> a<00:18:19.020> specific 00:18:19.250 --> 00:18:19.260 align:start position:0% Technologies uh for a specific 00:18:19.260 --> 00:18:21.770 align:start position:0% Technologies uh for a specific organization<00:18:19.919> we're<00:18:20.640> then<00:18:20.820> going<00:18:21.059> to<00:18:21.120> look<00:18:21.299> at 00:18:21.770 --> 00:18:21.780 align:start position:0% organization we're then going to look at 00:18:21.780 --> 00:18:24.650 align:start position:0% organization we're then going to look at uh<00:18:22.380> the<00:18:22.740> way<00:18:22.860> networks<00:18:23.520> basically<00:18:24.419> are 00:18:24.650 --> 00:18:24.660 align:start position:0% uh the way networks basically are 00:18:24.660 --> 00:18:26.029 align:start position:0% uh the way networks basically are organized<00:18:25.260> we're<00:18:25.620> going<00:18:25.740> to<00:18:25.860> look<00:18:25.919> at 00:18:26.029 --> 00:18:26.039 align:start position:0% organized we're going to look at 00:18:26.039 --> 00:18:28.010 align:start position:0% organized we're going to look at something<00:18:26.280> called<00:18:26.640> a<00:18:27.059> centralized<00:18:27.720> Network 00:18:28.010 --> 00:18:28.020 align:start position:0% something called a centralized Network 00:18:28.020 --> 00:18:31.250 align:start position:0% something called a centralized Network which<00:18:28.860> if<00:18:29.100> you<00:18:29.220> recall<00:18:29.580> from<00:18:29.820> the<00:18:30.059> previous<00:18:30.260> uh 00:18:31.250 --> 00:18:31.260 align:start position:0% which if you recall from the previous uh 00:18:31.260 --> 00:18:35.330 align:start position:0% which if you recall from the previous uh video<00:18:31.500> is<00:18:31.799> going<00:18:32.039> to<00:18:32.160> involve<00:18:32.640> a<00:18:33.059> terminal<00:18:33.419> and 00:18:35.330 --> 00:18:35.340 align:start position:0% video is going to involve a terminal and 00:18:35.340 --> 00:18:37.730 align:start position:0% video is going to involve a terminal and a<00:18:36.000> Mainframe<00:18:36.600> and<00:18:37.080> then<00:18:37.200> we're<00:18:37.380> going<00:18:37.500> to<00:18:37.620> look 00:18:37.730 --> 00:18:37.740 align:start position:0% a Mainframe and then we're going to look 00:18:37.740 --> 00:18:40.370 align:start position:0% a Mainframe and then we're going to look at<00:18:37.980> a<00:18:38.220> client<00:18:38.520> server<00:18:39.120> Network<00:18:39.299> which<00:18:39.960> sort<00:18:40.260> of 00:18:40.370 --> 00:18:40.380 align:start position:0% at a client server Network which sort of 00:18:40.380 --> 00:18:42.490 align:start position:0% at a client server Network which sort of takes<00:18:40.620> the<00:18:40.860> pressure<00:18:41.100> off<00:18:41.520> of<00:18:41.700> that<00:18:41.940> Central 00:18:42.490 --> 00:18:42.500 align:start position:0% takes the pressure off of that Central 00:18:42.500 --> 00:18:46.130 align:start position:0% takes the pressure off of that Central Mainframe<00:18:43.500> and<00:18:43.919> puts<00:18:44.160> it<00:18:44.220> onto<00:18:44.580> a<00:18:44.820> server<00:18:45.600> with 00:18:46.130 --> 00:18:46.140 align:start position:0% Mainframe and puts it onto a server with 00:18:46.140 --> 00:18:48.169 align:start position:0% Mainframe and puts it onto a server with a<00:18:46.380> client<00:18:46.740> and<00:18:47.400> then<00:18:47.520> finally<00:18:47.760> we're<00:18:47.940> going<00:18:48.059> to 00:18:48.169 --> 00:18:48.179 align:start position:0% a client and then finally we're going to 00:18:48.179 --> 00:18:49.970 align:start position:0% a client and then finally we're going to look<00:18:48.299> at<00:18:48.419> what<00:18:48.720> a<00:18:48.900> peer-to-peer<00:18:49.500> network<00:18:49.620> is 00:18:49.970 --> 00:18:49.980 align:start position:0% look at what a peer-to-peer network is 00:18:49.980 --> 00:18:52.549 align:start position:0% look at what a peer-to-peer network is and<00:18:50.580> again<00:18:50.760> that<00:18:51.240> is<00:18:51.360> like<00:18:51.600> where<00:18:51.840> we<00:18:52.020> have<00:18:52.200> all 00:18:52.549 --> 00:18:52.559 align:start position:0% and again that is like where we have all 00:18:52.559 --> 00:18:54.650 align:start position:0% and again that is like where we have all clients<00:18:53.039> no<00:18:53.340> servers<00:18:53.880> so<00:18:54.299> we're<00:18:54.419> really 00:18:54.650 --> 00:18:54.660 align:start position:0% clients no servers so we're really 00:18:54.660 --> 00:18:56.750 align:start position:0% clients no servers so we're really looking<00:18:54.840> at<00:18:55.140> a<00:18:55.320> descending<00:18:55.799> order<00:18:56.100> of 00:18:56.750 --> 00:18:56.760 align:start position:0% looking at a descending order of 00:18:56.760 --> 00:18:58.850 align:start position:0% looking at a descending order of centralization<00:18:57.539> but<00:18:58.140> at<00:18:58.320> the<00:18:58.440> same<00:18:58.620> time 00:18:58.850 --> 00:18:58.860 align:start position:0% centralization but at the same time 00:18:58.860 --> 00:19:01.250 align:start position:0% centralization but at the same time we're<00:18:59.160> putting<00:18:59.520> more<00:18:59.940> power<00:19:00.480> and<00:19:00.720> resources 00:19:01.250 --> 00:19:01.260 align:start position:0% we're putting more power and resources 00:19:01.260 --> 00:19:03.830 align:start position:0% we're putting more power and resources into<00:19:01.500> the<00:19:01.799> individual<00:19:02.220> computer<00:19:02.840> finally 00:19:03.830 --> 00:19:03.840 align:start position:0% into the individual computer finally 00:19:03.840 --> 00:19:06.230 align:start position:0% into the individual computer finally because<00:19:04.559> nothing<00:19:04.980> is<00:19:05.220> as<00:19:05.400> simple<00:19:05.580> as<00:19:05.760> it<00:19:05.940> seems 00:19:06.230 --> 00:19:06.240 align:start position:0% because nothing is as simple as it seems 00:19:06.240 --> 00:19:08.270 align:start position:0% because nothing is as simple as it seems we're<00:19:06.419> going<00:19:06.539> to<00:19:06.780> look<00:19:07.140> at<00:19:07.320> what's<00:19:07.620> called<00:19:07.919> a 00:19:08.270 --> 00:19:08.280 align:start position:0% we're going to look at what's called a 00:19:08.280 --> 00:19:10.070 align:start position:0% we're going to look at what's called a mixed<00:19:08.580> mode<00:19:08.760> Network<00:19:09.120> which<00:19:09.720> is<00:19:09.840> a 00:19:10.070 --> 00:19:10.080 align:start position:0% mixed mode Network which is a 00:19:10.080 --> 00:19:12.950 align:start position:0% mixed mode Network which is a combination<00:19:10.500> of<00:19:10.799> sort<00:19:11.039> of<00:19:11.160> all<00:19:11.700> of<00:19:11.820> these<00:19:12.179> and 00:19:12.950 --> 00:19:12.960 align:start position:0% combination of sort of all of these and 00:19:12.960 --> 00:19:15.409 align:start position:0% combination of sort of all of these and that'll<00:19:13.260> help<00:19:13.559> us<00:19:13.860> as<00:19:14.760> we<00:19:14.940> go<00:19:15.120> forward 00:19:15.409 --> 00:19:15.419 align:start position:0% that'll help us as we go forward 00:19:15.419 --> 00:19:18.470 align:start position:0% that'll help us as we go forward understand<00:19:16.220> how<00:19:17.220> an<00:19:17.520> administrator<00:19:18.059> of<00:19:18.360> a 00:19:18.470 --> 00:19:18.480 align:start position:0% understand how an administrator of a 00:19:18.480 --> 00:19:20.830 align:start position:0% understand how an administrator of a network<00:19:18.600> something<00:19:18.900> we'll<00:19:19.260> also<00:19:19.559> talk<00:19:19.740> about 00:19:20.830 --> 00:19:20.840 align:start position:0% network something we'll also talk about 00:19:20.840 --> 00:19:23.930 align:start position:0% network something we'll also talk about uh<00:19:21.840> deals<00:19:22.500> with<00:19:22.740> these<00:19:22.980> different<00:19:23.220> types<00:19:23.760> of 00:19:23.930 --> 00:19:23.940 align:start position:0% uh deals with these different types of 00:19:23.940 --> 00:19:27.650 align:start position:0% uh deals with these different types of needs<00:19:24.360> on<00:19:25.140> their<00:19:25.620> entire<00:19:25.919> network 00:19:27.650 --> 00:19:27.660 align:start position:0% needs on their entire network 00:19:27.660 --> 00:19:30.110 align:start position:0% needs on their entire network so<00:19:28.140> let's<00:19:28.500> first<00:19:28.679> start<00:19:28.980> talking<00:19:29.340> about<00:19:29.700> a 00:19:30.110 --> 00:19:30.120 align:start position:0% so let's first start talking about a 00:19:30.120 --> 00:19:33.289 align:start position:0% so let's first start talking about a local<00:19:30.299> area<00:19:30.660> network<00:19:31.200> a<00:19:32.160> lan<00:19:32.580> or<00:19:32.760> a<00:19:32.880> local<00:19:33.059> area 00:19:33.289 --> 00:19:33.299 align:start position:0% local area network a lan or a local area 00:19:33.299 --> 00:19:36.529 align:start position:0% local area network a lan or a local area network<00:19:33.660> is<00:19:34.140> a<00:19:34.320> network<00:19:34.620> that<00:19:35.160> spans<00:19:35.760> a<00:19:36.299> small 00:19:36.529 --> 00:19:36.539 align:start position:0% network is a network that spans a small 00:19:36.539 --> 00:19:39.890 align:start position:0% network is a network that spans a small area<00:19:37.160> typically<00:19:38.160> either<00:19:38.700> a<00:19:39.059> building<00:19:39.360> like 00:19:39.890 --> 00:19:39.900 align:start position:0% area typically either a building like 00:19:39.900 --> 00:19:43.130 align:start position:0% area typically either a building like your<00:19:40.200> home<00:19:40.440> or<00:19:40.860> office<00:19:41.299> or<00:19:42.299> a<00:19:42.419> floor<00:19:42.600> of<00:19:42.840> a<00:19:43.020> much 00:19:43.130 --> 00:19:43.140 align:start position:0% your home or office or a floor of a much 00:19:43.140 --> 00:19:46.190 align:start position:0% your home or office or a floor of a much larger<00:19:43.620> building<00:19:44.000> you<00:19:45.000> might<00:19:45.240> find<00:19:45.720> this<00:19:46.020> in 00:19:46.190 --> 00:19:46.200 align:start position:0% larger building you might find this in 00:19:46.200 --> 00:19:49.130 align:start position:0% larger building you might find this in like<00:19:46.440> a<00:19:47.039> skyscraper<00:19:47.940> so<00:19:48.480> take<00:19:48.720> the<00:19:48.900> Empire 00:19:49.130 --> 00:19:49.140 align:start position:0% like a skyscraper so take the Empire 00:19:49.140 --> 00:19:51.650 align:start position:0% like a skyscraper so take the Empire State<00:19:49.740> Building<00:19:50.100> for<00:19:50.640> instance<00:19:50.940> which<00:19:51.299> is<00:19:51.419> one 00:19:51.650 --> 00:19:51.660 align:start position:0% State Building for instance which is one 00:19:51.660 --> 00:19:54.470 align:start position:0% State Building for instance which is one of<00:19:51.780> the<00:19:51.900> largest<00:19:52.320> or<00:19:52.559> tallest<00:19:53.240> buildings<00:19:54.240> in 00:19:54.470 --> 00:19:54.480 align:start position:0% of the largest or tallest buildings in 00:19:54.480 --> 00:19:56.570 align:start position:0% of the largest or tallest buildings in New<00:19:54.600> York<00:19:54.780> or<00:19:55.080> it<00:19:55.260> used<00:19:55.440> to<00:19:55.559> be 00:19:56.570 --> 00:19:56.580 align:start position:0% New York or it used to be 00:19:56.580 --> 00:19:57.409 align:start position:0% New York or it used to be um 00:19:57.409 --> 00:19:57.419 align:start position:0% um 00:19:57.419 --> 00:20:01.370 align:start position:0% um every<00:19:58.260> floor<00:19:58.559> of<00:19:58.860> the<00:19:59.100> building<00:19:59.400> might<00:20:00.299> have<00:20:00.720> a 00:20:01.370 --> 00:20:01.380 align:start position:0% every floor of the building might have a 00:20:01.380 --> 00:20:03.950 align:start position:0% every floor of the building might have a different<00:20:01.500> company<00:20:01.980> using<00:20:02.520> it<00:20:02.700> so<00:20:03.299> each<00:20:03.720> one 00:20:03.950 --> 00:20:03.960 align:start position:0% different company using it so each one 00:20:03.960 --> 00:20:07.010 align:start position:0% different company using it so each one of<00:20:04.140> those<00:20:04.380> has<00:20:05.160> their<00:20:05.580> own<00:20:05.820> land<00:20:06.419> or<00:20:06.780> local 00:20:07.010 --> 00:20:07.020 align:start position:0% of those has their own land or local 00:20:07.020 --> 00:20:09.590 align:start position:0% of those has their own land or local area<00:20:07.320> network<00:20:07.740> to<00:20:08.400> keep<00:20:08.520> them<00:20:08.760> separated<00:20:09.299> from 00:20:09.590 --> 00:20:09.600 align:start position:0% area network to keep them separated from 00:20:09.600 --> 00:20:11.630 align:start position:0% area network to keep them separated from one<00:20:09.780> another<00:20:09.960> even<00:20:10.799> though<00:20:10.980> they<00:20:11.340> might<00:20:11.460> even 00:20:11.630 --> 00:20:11.640 align:start position:0% one another even though they might even 00:20:11.640 --> 00:20:13.850 align:start position:0% one another even though they might even be<00:20:11.940> using<00:20:12.299> some<00:20:12.539> of<00:20:12.660> the<00:20:12.900> same<00:20:13.080> infrastructure 00:20:13.850 --> 00:20:13.860 align:start position:0% be using some of the same infrastructure 00:20:13.860 --> 00:20:17.330 align:start position:0% be using some of the same infrastructure running<00:20:14.400> into<00:20:14.700> that<00:20:15.000> building<00:20:15.740> now<00:20:16.740> in<00:20:17.039> a<00:20:17.160> land 00:20:17.330 --> 00:20:17.340 align:start position:0% running into that building now in a land 00:20:17.340 --> 00:20:19.490 align:start position:0% running into that building now in a land the<00:20:17.580> most<00:20:17.760> commonly<00:20:18.299> implemented<00:20:19.080> technology 00:20:19.490 --> 00:20:19.500 align:start position:0% the most commonly implemented technology 00:20:19.500 --> 00:20:20.750 align:start position:0% the most commonly implemented technology and<00:20:19.799> something<00:20:19.980> you've<00:20:20.280> probably<00:20:20.400> heard<00:20:20.580> of 00:20:20.750 --> 00:20:20.760 align:start position:0% and something you've probably heard of 00:20:20.760 --> 00:20:23.270 align:start position:0% and something you've probably heard of is<00:20:20.940> something<00:20:21.179> called<00:20:21.539> ethernet<00:20:22.500> and<00:20:23.100> this 00:20:23.270 --> 00:20:23.280 align:start position:0% is something called ethernet and this 00:20:23.280 --> 00:20:25.250 align:start position:0% is something called ethernet and this means<00:20:23.640> that<00:20:23.880> the<00:20:24.059> communication<00:20:24.480> path<00:20:24.840> taken 00:20:25.250 --> 00:20:25.260 align:start position:0% means that the communication path taken 00:20:25.260 --> 00:20:28.430 align:start position:0% means that the communication path taken utilizes<00:20:25.919> uh<00:20:26.820> cabling<00:20:27.299> or<00:20:27.780> short<00:20:28.020> range 00:20:28.430 --> 00:20:28.440 align:start position:0% utilizes uh cabling or short range 00:20:28.440 --> 00:20:30.830 align:start position:0% utilizes uh cabling or short range Wireless<00:20:29.000> Technologies<00:20:30.000> we're<00:20:30.600> going<00:20:30.780> to 00:20:30.830 --> 00:20:30.840 align:start position:0% Wireless Technologies we're going to 00:20:30.840 --> 00:20:32.930 align:start position:0% Wireless Technologies we're going to talk<00:20:30.960> about<00:20:31.140> ethernet<00:20:31.860> and<00:20:32.160> and<00:20:32.400> really<00:20:32.700> what 00:20:32.930 --> 00:20:32.940 align:start position:0% talk about ethernet and and really what 00:20:32.940 --> 00:20:34.789 align:start position:0% talk about ethernet and and really what it<00:20:33.059> means<00:20:33.240> because<00:20:33.419> it's<00:20:33.660> it's<00:20:34.080> also<00:20:34.440> not<00:20:34.620> just 00:20:34.789 --> 00:20:34.799 align:start position:0% it means because it's it's also not just 00:20:34.799 --> 00:20:36.230 align:start position:0% it means because it's it's also not just the<00:20:35.100> hardware<00:20:35.280> it<00:20:35.580> really<00:20:35.760> has<00:20:35.880> to<00:20:36.059> do<00:20:36.120> with 00:20:36.230 --> 00:20:36.240 align:start position:0% the hardware it really has to do with 00:20:36.240 --> 00:20:38.810 align:start position:0% the hardware it really has to do with how<00:20:36.539> the<00:20:36.720> data<00:20:37.200> is<00:20:37.320> being<00:20:37.500> communicated<00:20:38.220> in 00:20:38.810 --> 00:20:38.820 align:start position:0% how the data is being communicated in 00:20:38.820 --> 00:20:41.390 align:start position:0% how the data is being communicated in Greater<00:20:39.120> detail<00:20:39.480> in<00:20:39.660> an<00:20:39.840> upcoming<00:20:40.320> module<00:20:40.799> now 00:20:41.390 --> 00:20:41.400 align:start position:0% Greater detail in an upcoming module now 00:20:41.400 --> 00:20:44.810 align:start position:0% Greater detail in an upcoming module now in<00:20:41.640> a<00:20:41.820> local<00:20:41.880> area<00:20:42.120> network<00:20:42.419> a<00:20:43.020> connection<00:20:43.820> uh 00:20:44.810 --> 00:20:44.820 align:start position:0% in a local area network a connection uh 00:20:44.820 --> 00:20:47.690 align:start position:0% in a local area network a connection uh is<00:20:45.360> leased<00:20:45.900> by<00:20:46.080> a<00:20:46.260> service<00:20:46.440> provider<00:20:47.220> but<00:20:47.580> it 00:20:47.690 --> 00:20:47.700 align:start position:0% is leased by a service provider but it 00:20:47.700 --> 00:20:49.430 align:start position:0% is leased by a service provider but it isn't<00:20:48.000> necessarily<00:20:48.480> for<00:20:48.840> the<00:20:48.960> land<00:20:49.140> to 00:20:49.430 --> 00:20:49.440 align:start position:0% isn't necessarily for the land to 00:20:49.440 --> 00:20:51.529 align:start position:0% isn't necessarily for the land to function<00:20:49.679> properly<00:20:50.160> so<00:20:50.640> this<00:20:50.820> means<00:20:51.120> I<00:20:51.360> don't 00:20:51.529 --> 00:20:51.539 align:start position:0% function properly so this means I don't 00:20:51.539 --> 00:20:54.950 align:start position:0% function properly so this means I don't need<00:20:52.400> an<00:20:53.400> outside<00:20:53.640> sort<00:20:54.179> of<00:20:54.240> connection<00:20:54.539> in 00:20:54.950 --> 00:20:54.960 align:start position:0% need an outside sort of connection in 00:20:54.960 --> 00:20:57.169 align:start position:0% need an outside sort of connection in order<00:20:55.080> for<00:20:55.320> my<00:20:55.500> land<00:20:55.740> to<00:20:56.100> work<00:20:56.280> the<00:20:56.940> reason<00:20:57.059> I 00:20:57.169 --> 00:20:57.179 align:start position:0% order for my land to work the reason I 00:20:57.179 --> 00:21:00.289 align:start position:0% order for my land to work the reason I might<00:20:57.360> need<00:20:58.080> a<00:20:58.919> connection<00:20:59.460> to<00:20:59.940> the<00:21:00.059> outside 00:21:00.289 --> 00:21:00.299 align:start position:0% might need a connection to the outside 00:21:00.299 --> 00:21:02.990 align:start position:0% might need a connection to the outside from<00:21:00.840> an<00:21:01.020> internet<00:21:01.200> service<00:21:01.679> provider<00:21:02.460> is 00:21:02.990 --> 00:21:03.000 align:start position:0% from an internet service provider is 00:21:03.000 --> 00:21:06.409 align:start position:0% from an internet service provider is going<00:21:03.240> to<00:21:03.360> be<00:21:03.419> thanks<00:21:03.660> to<00:21:04.080> a<00:21:04.799> Wan<00:21:05.160> or<00:21:05.820> a<00:21:06.059> wide 00:21:06.409 --> 00:21:06.419 align:start position:0% going to be thanks to a Wan or a wide 00:21:06.419 --> 00:21:08.090 align:start position:0% going to be thanks to a Wan or a wide area<00:21:06.600> network<00:21:06.900> but<00:21:07.559> let's<00:21:07.679> talk<00:21:07.860> really 00:21:08.090 --> 00:21:08.100 align:start position:0% area network but let's talk really 00:21:08.100 --> 00:21:10.610 align:start position:0% area network but let's talk really quickly<00:21:08.340> about<00:21:08.580> land<00:21:09.000> administrators<00:21:09.840> the 00:21:10.610 --> 00:21:10.620 align:start position:0% quickly about land administrators the 00:21:10.620 --> 00:21:12.110 align:start position:0% quickly about land administrators the people<00:21:10.799> who<00:21:11.100> are<00:21:11.160> running<00:21:11.340> these<00:21:11.640> lands<00:21:11.940> that 00:21:12.110 --> 00:21:12.120 align:start position:0% people who are running these lands that 00:21:12.120 --> 00:21:13.789 align:start position:0% people who are running these lands that might<00:21:12.240> help<00:21:12.480> us<00:21:12.660> understand<00:21:13.080> them<00:21:13.500> a<00:21:13.679> little 00:21:13.789 --> 00:21:13.799 align:start position:0% might help us understand them a little 00:21:13.799 --> 00:21:15.409 align:start position:0% might help us understand them a little clearer 00:21:15.409 --> 00:21:15.419 align:start position:0% clearer 00:21:15.419 --> 00:21:18.049 align:start position:0% clearer now<00:21:15.960> land<00:21:16.340> administrators<00:21:17.340> are<00:21:17.880> like 00:21:18.049 --> 00:21:18.059 align:start position:0% now land administrators are like 00:21:18.059 --> 00:21:20.270 align:start position:0% now land administrators are like jugglers<00:21:18.600> they<00:21:18.840> have<00:21:18.960> to<00:21:19.080> keep<00:21:19.260> their<00:21:19.559> eyes<00:21:19.799> on 00:21:20.270 --> 00:21:20.280 align:start position:0% jugglers they have to keep their eyes on 00:21:20.280 --> 00:21:21.950 align:start position:0% jugglers they have to keep their eyes on all<00:21:20.700> of<00:21:20.820> the<00:21:20.880> components<00:21:21.480> of<00:21:21.600> their<00:21:21.780> Network 00:21:21.950 --> 00:21:21.960 align:start position:0% all of the components of their Network 00:21:21.960 --> 00:21:25.070 align:start position:0% all of the components of their Network at<00:21:22.320> the<00:21:22.500> same<00:21:22.679> time<00:21:22.980> hence<00:21:23.760> the<00:21:24.000> little<00:21:24.419> GIF 00:21:25.070 --> 00:21:25.080 align:start position:0% at the same time hence the little GIF 00:21:25.080 --> 00:21:27.950 align:start position:0% at the same time hence the little GIF over<00:21:25.320> here<00:21:25.700> they<00:21:26.700> have<00:21:26.880> to<00:21:27.000> have<00:21:27.179> there<00:21:27.419> for<00:21:27.660> a 00:21:27.950 --> 00:21:27.960 align:start position:0% over here they have to have there for a 00:21:27.960 --> 00:21:30.830 align:start position:0% over here they have to have there for a broad<00:21:28.380> range<00:21:28.919> of<00:21:29.100> versatile<00:21:29.520> skills<00:21:30.120> that 00:21:30.830 --> 00:21:30.840 align:start position:0% broad range of versatile skills that 00:21:30.840 --> 00:21:32.990 align:start position:0% broad range of versatile skills that allow<00:21:31.080> them<00:21:31.260> to<00:21:31.559> manage<00:21:31.860> and<00:21:32.100> maintain<00:21:32.520> all 00:21:32.990 --> 00:21:33.000 align:start position:0% allow them to manage and maintain all 00:21:33.000 --> 00:21:35.930 align:start position:0% allow them to manage and maintain all the<00:21:33.120> different<00:21:33.299> parts<00:21:33.600> of<00:21:34.080> their<00:21:34.380> Network<00:21:34.940> now 00:21:35.930 --> 00:21:35.940 align:start position:0% the different parts of their Network now 00:21:35.940 --> 00:21:38.990 align:start position:0% the different parts of their Network now that's<00:21:36.360> only<00:21:36.840> within<00:21:37.440> their<00:21:37.860> domain<00:21:38.280> and<00:21:38.880> the 00:21:38.990 --> 00:21:39.000 align:start position:0% that's only within their domain and the 00:21:39.000 --> 00:21:41.570 align:start position:0% that's only within their domain and the juggler<00:21:39.360> also<00:21:39.780> has<00:21:39.960> to<00:21:40.140> be<00:21:40.320> mindful<00:21:40.919> of<00:21:41.340> each 00:21:41.570 --> 00:21:41.580 align:start position:0% juggler also has to be mindful of each 00:21:41.580 --> 00:21:43.070 align:start position:0% juggler also has to be mindful of each of<00:21:41.700> the<00:21:41.820> objects<00:21:42.240> in<00:21:42.360> the<00:21:42.480> air<00:21:42.600> at<00:21:42.780> the<00:21:42.900> same 00:21:43.070 --> 00:21:43.080 align:start position:0% of the objects in the air at the same 00:21:43.080 --> 00:21:45.470 align:start position:0% of the objects in the air at the same time<00:21:43.320> or<00:21:43.860> else<00:21:43.980> they<00:21:44.220> might<00:21:44.400> lose<00:21:44.700> track<00:21:45.179> of 00:21:45.470 --> 00:21:45.480 align:start position:0% time or else they might lose track of 00:21:45.480 --> 00:21:48.950 align:start position:0% time or else they might lose track of one<00:21:45.780> or<00:21:46.260> all<00:21:46.500> of<00:21:46.620> them<00:21:46.880> like<00:21:47.880> the<00:21:48.120> juggler<00:21:48.480> if 00:21:48.950 --> 00:21:48.960 align:start position:0% one or all of them like the juggler if 00:21:48.960 --> 00:21:51.350 align:start position:0% one or all of them like the juggler if the<00:21:49.140> land<00:21:49.320> administrator<00:21:49.919> loses<00:21:50.520> track<00:21:50.880> of 00:21:51.350 --> 00:21:51.360 align:start position:0% the land administrator loses track of 00:21:51.360 --> 00:21:54.110 align:start position:0% the land administrator loses track of one<00:21:51.720> part<00:21:51.960> of<00:21:52.200> their<00:21:52.440> job<00:21:52.740> it's<00:21:53.400> likely<00:21:53.760> the 00:21:54.110 --> 00:21:54.120 align:start position:0% one part of their job it's likely the 00:21:54.120 --> 00:21:56.390 align:start position:0% one part of their job it's likely the entire<00:21:54.600> network<00:21:54.960> of<00:21:55.380> moving<00:21:55.740> components 00:21:56.390 --> 00:21:56.400 align:start position:0% entire network of moving components 00:21:56.400 --> 00:21:59.029 align:start position:0% entire network of moving components could<00:21:56.700> come<00:21:57.000> quote<00:21:57.419> unquote<00:21:57.780> crashing<00:21:58.620> to<00:21:58.860> a 00:21:59.029 --> 00:21:59.039 align:start position:0% could come quote unquote crashing to a 00:21:59.039 --> 00:22:01.549 align:start position:0% could come quote unquote crashing to a halt<00:21:59.400> the<00:22:00.179> land<00:22:00.360> administrator<00:22:00.960> therefore 00:22:01.549 --> 00:22:01.559 align:start position:0% halt the land administrator therefore 00:22:01.559 --> 00:22:04.010 align:start position:0% halt the land administrator therefore has<00:22:01.980> to<00:22:02.159> have<00:22:02.400> a<00:22:02.820> strong<00:22:03.120> working<00:22:03.480> knowledge 00:22:04.010 --> 00:22:04.020 align:start position:0% has to have a strong working knowledge 00:22:04.020 --> 00:22:06.710 align:start position:0% has to have a strong working knowledge of<00:22:04.380> all<00:22:04.740> the<00:22:04.860> aspects<00:22:05.340> of<00:22:05.520> their<00:22:05.700> Network<00:22:05.940> now 00:22:06.710 --> 00:22:06.720 align:start position:0% of all the aspects of their Network now 00:22:06.720 --> 00:22:08.450 align:start position:0% of all the aspects of their Network now the<00:22:06.900> land<00:22:07.080> administrator<00:22:07.620> should<00:22:07.919> be<00:22:08.100> able<00:22:08.220> to 00:22:08.450 --> 00:22:08.460 align:start position:0% the land administrator should be able to 00:22:08.460 --> 00:22:11.270 align:start position:0% the land administrator should be able to handle<00:22:08.820> tasks<00:22:09.360> such<00:22:09.780> as<00:22:10.020> installation<00:22:10.980> of 00:22:11.270 --> 00:22:11.280 align:start position:0% handle tasks such as installation of 00:22:11.280 --> 00:22:13.270 align:start position:0% handle tasks such as installation of software<00:22:11.760> and<00:22:12.120> hardware 00:22:13.270 --> 00:22:13.280 align:start position:0% software and hardware 00:22:13.280 --> 00:22:15.770 align:start position:0% software and hardware troubleshooting<00:22:14.280> all<00:22:14.820> components<00:22:15.240> of<00:22:15.360> the 00:22:15.770 --> 00:22:15.780 align:start position:0% troubleshooting all components of the 00:22:15.780 --> 00:22:17.450 align:start position:0% troubleshooting all components of the network<00:22:15.960> including<00:22:16.559> the<00:22:16.799> servers<00:22:17.220> which 00:22:17.450 --> 00:22:17.460 align:start position:0% network including the servers which 00:22:17.460 --> 00:22:19.909 align:start position:0% network including the servers which we'll<00:22:17.640> talk<00:22:17.820> about<00:22:18.440> connectivity<00:22:19.440> devices 00:22:19.909 --> 00:22:19.919 align:start position:0% we'll talk about connectivity devices 00:22:19.919 --> 00:22:23.270 align:start position:0% we'll talk about connectivity devices and<00:22:20.880> media<00:22:21.240> and<00:22:21.419> so<00:22:21.600> on<00:22:21.720> and<00:22:21.900> so<00:22:22.080> forth<00:22:22.380> and<00:22:23.039> not 00:22:23.270 --> 00:22:23.280 align:start position:0% and media and so on and so forth and not 00:22:23.280 --> 00:22:26.570 align:start position:0% and media and so on and so forth and not to<00:22:23.460> mention<00:22:23.700> security<00:22:24.360> for<00:22:24.780> the<00:22:24.960> network<00:22:25.080> so 00:22:26.570 --> 00:22:26.580 align:start position:0% to mention security for the network so 00:22:26.580 --> 00:22:29.270 align:start position:0% to mention security for the network so if<00:22:27.120> that<00:22:27.299> isn't<00:22:27.659> enough<00:22:27.960> one<00:22:28.860> of<00:22:28.919> their<00:22:29.100> most 00:22:29.270 --> 00:22:29.280 align:start position:0% if that isn't enough one of their most 00:22:29.280 --> 00:22:31.669 align:start position:0% if that isn't enough one of their most difficult<00:22:29.900> tasking<00:22:30.900> duties<00:22:31.260> of<00:22:31.440> the<00:22:31.620> land 00:22:31.669 --> 00:22:31.679 align:start position:0% difficult tasking duties of the land 00:22:31.679 --> 00:22:33.710 align:start position:0% difficult tasking duties of the land administrator<00:22:32.220> is<00:22:32.460> being<00:22:32.700> responsible<00:22:33.299> for 00:22:33.710 --> 00:22:33.720 align:start position:0% administrator is being responsible for 00:22:33.720 --> 00:22:36.529 align:start position:0% administrator is being responsible for users<00:22:34.260> and<00:22:34.740> attending<00:22:35.159> to<00:22:35.400> their<00:22:35.760> requests 00:22:36.529 --> 00:22:36.539 align:start position:0% users and attending to their requests 00:22:36.539 --> 00:22:38.990 align:start position:0% users and attending to their requests and<00:22:36.720> their<00:22:36.960> requirements<00:22:37.620> so 00:22:38.990 --> 00:22:39.000 align:start position:0% and their requirements so 00:22:39.000 --> 00:22:41.270 align:start position:0% and their requirements so you<00:22:39.539> can<00:22:39.600> tell<00:22:39.780> that<00:22:40.140> the<00:22:40.440> land<00:22:40.620> administrator 00:22:41.270 --> 00:22:41.280 align:start position:0% you can tell that the land administrator 00:22:41.280 --> 00:22:44.029 align:start position:0% you can tell that the land administrator really<00:22:41.700> has<00:22:42.120> to<00:22:42.299> be<00:22:42.720> able<00:22:42.900> to<00:22:43.020> do<00:22:43.320> a<00:22:43.620> lot<00:22:43.740> and 00:22:44.029 --> 00:22:44.039 align:start position:0% really has to be able to do a lot and 00:22:44.039 --> 00:22:45.830 align:start position:0% really has to be able to do a lot and we're<00:22:44.159> gonna<00:22:44.340> as<00:22:44.940> we<00:22:45.120> go<00:22:45.240> through<00:22:45.419> this<00:22:45.659> course 00:22:45.830 --> 00:22:45.840 align:start position:0% we're gonna as we go through this course 00:22:45.840 --> 00:22:48.110 align:start position:0% we're gonna as we go through this course you'll<00:22:46.200> see<00:22:46.380> more<00:22:46.620> and<00:22:46.740> more<00:22:46.980> specifically<00:22:47.580> of 00:22:48.110 --> 00:22:48.120 align:start position:0% you'll see more and more specifically of 00:22:48.120 --> 00:22:49.909 align:start position:0% you'll see more and more specifically of what<00:22:48.360> they<00:22:48.539> have<00:22:48.720> to<00:22:48.840> do<00:22:49.020> but<00:22:49.559> let's<00:22:49.740> talk 00:22:49.909 --> 00:22:49.919 align:start position:0% what they have to do but let's talk 00:22:49.919 --> 00:22:54.289 align:start position:0% what they have to do but let's talk about<00:22:50.100> a<00:22:50.580> Wan<00:22:50.940> a<00:22:51.840> Wan<00:22:52.140> or<00:22:52.559> a<00:22:52.740> wide<00:22:53.100> area<00:22:53.280> network 00:22:54.289 --> 00:22:54.299 align:start position:0% about a Wan a Wan or a wide area network 00:22:54.299 --> 00:22:57.110 align:start position:0% about a Wan a Wan or a wide area network uh<00:22:54.960> is<00:22:55.140> a<00:22:55.380> network<00:22:55.500> that<00:22:55.919> spans<00:22:56.340> a<00:22:56.820> larger 00:22:57.110 --> 00:22:57.120 align:start position:0% uh is a network that spans a larger 00:22:57.120 --> 00:23:00.169 align:start position:0% uh is a network that spans a larger geographical<00:22:57.659> area<00:22:58.020> than<00:22:58.380> a<00:22:58.620> lan<00:22:59.000> in<00:23:00.000> most 00:23:00.169 --> 00:23:00.179 align:start position:0% geographical area than a lan in most 00:23:00.179 --> 00:23:04.130 align:start position:0% geographical area than a lan in most cases<00:23:00.980> uh<00:23:01.980> the<00:23:02.520> WAN<00:23:02.760> is<00:23:03.000> going<00:23:03.179> to<00:23:03.360> connect<00:23:03.600> as 00:23:04.130 --> 00:23:04.140 align:start position:0% cases uh the WAN is going to connect as 00:23:04.140 --> 00:23:07.010 align:start position:0% cases uh the WAN is going to connect as this<00:23:04.440> picture<00:23:04.679> demonstrates<00:23:05.600> multiple<00:23:06.600> lands 00:23:07.010 --> 00:23:07.020 align:start position:0% this picture demonstrates multiple lands 00:23:07.020 --> 00:23:09.370 align:start position:0% this picture demonstrates multiple lands together<00:23:07.260> and<00:23:08.039> it<00:23:08.220> might<00:23:08.400> even<00:23:08.580> utilize 00:23:09.370 --> 00:23:09.380 align:start position:0% together and it might even utilize 00:23:09.380 --> 00:23:11.750 align:start position:0% together and it might even utilize long-range<00:23:10.380> communication<00:23:11.039> such<00:23:11.520> as 00:23:11.750 --> 00:23:11.760 align:start position:0% long-range communication such as 00:23:11.760 --> 00:23:14.750 align:start position:0% long-range communication such as satellite<00:23:12.480> or<00:23:13.140> radio<00:23:13.620> frequency<00:23:14.220> otherwise 00:23:14.750 --> 00:23:14.760 align:start position:0% satellite or radio frequency otherwise 00:23:14.760 --> 00:23:21.350 align:start position:0% satellite or radio frequency otherwise known<00:23:15.000> as<00:23:15.299> RF 00:23:21.350 --> 00:23:21.360 align:start position:0% 00:23:21.360 --> 00:23:23.750 align:start position:0% now<00:23:21.780> one<00:23:22.200> main<00:23:22.440> factor<00:23:22.860> that<00:23:23.159> differentiates 00:23:23.750 --> 00:23:23.760 align:start position:0% now one main factor that differentiates 00:23:23.760 --> 00:23:26.810 align:start position:0% now one main factor that differentiates a<00:23:24.059> win<00:23:24.299> or<00:23:24.600> wide<00:23:24.840> area<00:23:25.020> network<00:23:25.320> from<00:23:25.799> a<00:23:25.980> lan<00:23:26.340> is 00:23:26.810 --> 00:23:26.820 align:start position:0% a win or wide area network from a lan is 00:23:26.820 --> 00:23:28.610 align:start position:0% a win or wide area network from a lan is that<00:23:26.940> it<00:23:27.059> can<00:23:27.240> enable<00:23:27.480> users<00:23:27.840> to<00:23:28.020> connect<00:23:28.200> to 00:23:28.610 --> 00:23:28.620 align:start position:0% that it can enable users to connect to 00:23:28.620 --> 00:23:30.350 align:start position:0% that it can enable users to connect to one<00:23:28.740> another<00:23:28.919> from<00:23:29.460> different<00:23:29.820> physical 00:23:30.350 --> 00:23:30.360 align:start position:0% one another from different physical 00:23:30.360 --> 00:23:32.990 align:start position:0% one another from different physical locations<00:23:31.200> so<00:23:31.740> whereas<00:23:32.159> these<00:23:32.640> are<00:23:32.760> each 00:23:32.990 --> 00:23:33.000 align:start position:0% locations so whereas these are each 00:23:33.000 --> 00:23:35.990 align:start position:0% locations so whereas these are each physically<00:23:33.539> sort<00:23:33.960> of<00:23:34.140> uh<00:23:34.919> isolated<00:23:35.460> in<00:23:35.880> some 00:23:35.990 --> 00:23:36.000 align:start position:0% physically sort of uh isolated in some 00:23:36.000 --> 00:23:39.049 align:start position:0% physically sort of uh isolated in some ways<00:23:36.240> you<00:23:36.419> can<00:23:36.539> tell<00:23:36.659> the<00:23:37.080> WAN<00:23:37.580> connects<00:23:38.580> all 00:23:39.049 --> 00:23:39.059 align:start position:0% ways you can tell the WAN connects all 00:23:39.059 --> 00:23:42.830 align:start position:0% ways you can tell the WAN connects all of<00:23:39.240> these<00:23:39.539> lands<00:23:40.020> together 00:23:42.830 --> 00:23:42.840 align:start position:0% 00:23:42.840 --> 00:23:46.789 align:start position:0% okay<00:23:43.700> now<00:23:44.700> a<00:23:45.000> Wan<00:23:45.299> can<00:23:45.539> be<00:23:45.780> private<00:23:46.320> where<00:23:46.620> an 00:23:46.789 --> 00:23:46.799 align:start position:0% okay now a Wan can be private where an 00:23:46.799 --> 00:23:49.370 align:start position:0% okay now a Wan can be private where an organization<00:23:47.280> has<00:23:47.700> complete<00:23:48.480> control<00:23:48.840> of 00:23:49.370 --> 00:23:49.380 align:start position:0% organization has complete control of 00:23:49.380 --> 00:23:52.789 align:start position:0% organization has complete control of access<00:23:49.919> to<00:23:50.460> it<00:23:50.640> resources<00:23:51.539> and<00:23:52.260> it's<00:23:52.440> solely 00:23:52.789 --> 00:23:52.799 align:start position:0% access to it resources and it's solely 00:23:52.799 --> 00:23:54.649 align:start position:0% access to it resources and it's solely responsible<00:23:53.400> for<00:23:53.760> everything<00:23:54.000> that<00:23:54.299> occurs 00:23:54.649 --> 00:23:54.659 align:start position:0% responsible for everything that occurs 00:23:54.659 --> 00:23:57.830 align:start position:0% responsible for everything that occurs on<00:23:54.900> that<00:23:55.140> Network<00:23:55.700> or<00:23:56.700> a<00:23:56.940> win<00:23:57.120> can<00:23:57.419> be<00:23:57.539> public 00:23:57.830 --> 00:23:57.840 align:start position:0% on that Network or a win can be public 00:23:57.840 --> 00:24:02.210 align:start position:0% on that Network or a win can be public and<00:23:58.559> of<00:23:58.740> course<00:23:58.860> the<00:23:59.340> world's<00:23:59.700> largest<00:24:00.419> Wan 00:24:02.210 --> 00:24:02.220 align:start position:0% and of course the world's largest Wan 00:24:02.220 --> 00:24:04.250 align:start position:0% and of course the world's largest Wan is<00:24:02.580> the<00:24:02.760> internet 00:24:04.250 --> 00:24:04.260 align:start position:0% is the internet 00:24:04.260 --> 00:24:05.570 align:start position:0% is the internet now<00:24:04.620> we're<00:24:04.740> going<00:24:04.860> to<00:24:04.919> talk<00:24:05.039> more<00:24:05.220> about<00:24:05.340> the 00:24:05.570 --> 00:24:05.580 align:start position:0% now we're going to talk more about the 00:24:05.580 --> 00:24:07.250 align:start position:0% now we're going to talk more about the internet<00:24:05.760> in<00:24:06.179> detail<00:24:06.480> shortly<00:24:06.840> but<00:24:07.020> I<00:24:07.140> just 00:24:07.250 --> 00:24:07.260 align:start position:0% internet in detail shortly but I just 00:24:07.260 --> 00:24:09.289 align:start position:0% internet in detail shortly but I just want<00:24:07.380> to<00:24:07.500> point<00:24:07.620> out<00:24:07.799> that<00:24:08.220> the<00:24:08.700> biggest<00:24:08.820> wide 00:24:09.289 --> 00:24:09.299 align:start position:0% want to point out that the biggest wide 00:24:09.299 --> 00:24:12.770 align:start position:0% want to point out that the biggest wide area<00:24:09.480> network<00:24:09.780> we<00:24:10.140> have<00:24:10.380> is<00:24:11.340> the<00:24:11.820> WAN<00:24:12.120> and 00:24:12.770 --> 00:24:12.780 align:start position:0% area network we have is the WAN and 00:24:12.780 --> 00:24:15.590 align:start position:0% area network we have is the WAN and unlike<00:24:13.260> the<00:24:13.919> land<00:24:14.100> which<00:24:14.520> is<00:24:14.700> geographically 00:24:15.590 --> 00:24:15.600 align:start position:0% unlike the land which is geographically 00:24:15.600 --> 00:24:19.010 align:start position:0% unlike the land which is geographically isolated<00:24:16.500> and<00:24:17.460> can<00:24:17.760> be<00:24:17.940> controlled<00:24:18.480> by<00:24:18.840> a 00:24:19.010 --> 00:24:19.020 align:start position:0% isolated and can be controlled by a 00:24:19.020 --> 00:24:21.409 align:start position:0% isolated and can be controlled by a relatively<00:24:19.500> few<00:24:19.679> number<00:24:19.860> of<00:24:20.039> people<00:24:20.280> the<00:24:21.120> WAN 00:24:21.409 --> 00:24:21.419 align:start position:0% relatively few number of people the WAN 00:24:21.419 --> 00:24:23.810 align:start position:0% relatively few number of people the WAN has<00:24:21.780> very<00:24:22.020> different<00:24:22.380> needs 00:24:23.810 --> 00:24:23.820 align:start position:0% has very different needs 00:24:23.820 --> 00:24:25.970 align:start position:0% has very different needs now<00:24:24.299> there<00:24:24.480> are<00:24:24.600> also<00:24:24.780> different<00:24:25.020> types<00:24:25.799> of 00:24:25.970 --> 00:24:25.980 align:start position:0% now there are also different types of 00:24:25.980 --> 00:24:27.470 align:start position:0% now there are also different types of lands<00:24:26.460> that<00:24:26.640> are<00:24:26.700> out<00:24:26.820> there<00:24:26.940> now<00:24:27.179> some<00:24:27.419> of 00:24:27.470 --> 00:24:27.480 align:start position:0% lands that are out there now some of 00:24:27.480 --> 00:24:29.450 align:start position:0% lands that are out there now some of these<00:24:27.659> classifications 00:24:29.450 --> 00:24:29.460 align:start position:0% these classifications 00:24:29.460 --> 00:24:32.090 align:start position:0% these classifications um<00:24:29.940> we<00:24:30.900> might<00:24:31.020> get<00:24:31.140> argument<00:24:31.500> from<00:24:31.860> certain 00:24:32.090 --> 00:24:32.100 align:start position:0% um we might get argument from certain 00:24:32.100 --> 00:24:35.270 align:start position:0% um we might get argument from certain individuals<00:24:32.760> just<00:24:33.120> because<00:24:33.919> this<00:24:34.919> is<00:24:35.039> sort<00:24:35.220> of 00:24:35.270 --> 00:24:35.280 align:start position:0% individuals just because this is sort of 00:24:35.280 --> 00:24:37.250 align:start position:0% individuals just because this is sort of open<00:24:35.460> to<00:24:35.700> some<00:24:35.880> subjectivity<00:24:36.539> but<00:24:36.960> these<00:24:37.140> are 00:24:37.250 --> 00:24:37.260 align:start position:0% open to some subjectivity but these are 00:24:37.260 --> 00:24:39.230 align:start position:0% open to some subjectivity but these are covered<00:24:37.559> on<00:24:37.799> the<00:24:38.039> examine<00:24:38.700> which<00:24:38.940> is<00:24:39.059> the 00:24:39.230 --> 00:24:39.240 align:start position:0% covered on the examine which is the 00:24:39.240 --> 00:24:41.029 align:start position:0% covered on the examine which is the reason<00:24:39.360> I<00:24:39.600> want<00:24:39.780> to<00:24:39.960> make<00:24:40.260> sure<00:24:40.380> we<00:24:40.559> cover<00:24:40.740> them 00:24:41.029 --> 00:24:41.039 align:start position:0% reason I want to make sure we cover them 00:24:41.039 --> 00:24:43.130 align:start position:0% reason I want to make sure we cover them the<00:24:41.580> first<00:24:41.700> one<00:24:41.940> that<00:24:42.120> we've<00:24:42.299> seen<00:24:42.539> a<00:24:42.840> few 00:24:43.130 --> 00:24:43.140 align:start position:0% the first one that we've seen a few 00:24:43.140 --> 00:24:44.990 align:start position:0% the first one that we've seen a few times<00:24:43.380> when<00:24:43.679> we<00:24:43.860> talked<00:24:44.159> if<00:24:44.400> you<00:24:44.580> were<00:24:44.700> here 00:24:44.990 --> 00:24:45.000 align:start position:0% times when we talked if you were here 00:24:45.000 --> 00:24:47.570 align:start position:0% times when we talked if you were here for<00:24:45.179> a<00:24:45.299> plus<00:24:45.539> is<00:24:45.960> called<00:24:46.200> a<00:24:46.440> pan<00:24:46.679> or<00:24:47.100> a<00:24:47.280> personal 00:24:47.570 --> 00:24:47.580 align:start position:0% for a plus is called a pan or a personal 00:24:47.580 --> 00:24:50.810 align:start position:0% for a plus is called a pan or a personal area<00:24:47.880> network<00:24:48.299> a<00:24:49.260> pan<00:24:49.559> is<00:24:50.159> two<00:24:50.460> to<00:24:50.640> three 00:24:50.810 --> 00:24:50.820 align:start position:0% area network a pan is two to three 00:24:50.820 --> 00:24:53.510 align:start position:0% area network a pan is two to three computers<00:24:51.299> connected<00:24:51.780> together<00:24:52.020> by<00:24:52.919> cables 00:24:53.510 --> 00:24:53.520 align:start position:0% computers connected together by cables 00:24:53.520 --> 00:24:58.130 align:start position:0% computers connected together by cables and<00:24:54.360> a<00:24:54.840> wireless<00:24:54.960> pan<00:24:55.440> or<00:24:55.740> wpn<00:24:56.640> is<00:24:57.480> going<00:24:57.720> to<00:24:57.960> be 00:24:58.130 --> 00:24:58.140 align:start position:0% and a wireless pan or wpn is going to be 00:24:58.140 --> 00:25:00.710 align:start position:0% and a wireless pan or wpn is going to be using<00:24:58.740> Bluetooth<00:24:59.159> or<00:24:59.580> infrared<00:25:00.120> Technologies 00:25:00.710 --> 00:25:00.720 align:start position:0% using Bluetooth or infrared Technologies 00:25:00.720 --> 00:25:03.289 align:start position:0% using Bluetooth or infrared Technologies generally<00:25:01.559> speaking<00:25:02.280> when<00:25:02.760> we<00:25:02.940> are<00:25:03.059> talking 00:25:03.289 --> 00:25:03.299 align:start position:0% generally speaking when we are talking 00:25:03.299 --> 00:25:06.409 align:start position:0% generally speaking when we are talking about<00:25:03.539> pans<00:25:04.080> uh<00:25:05.039> for<00:25:05.280> purposes<00:25:05.700> of<00:25:05.940> the<00:25:06.059> exam 00:25:06.409 --> 00:25:06.419 align:start position:0% about pans uh for purposes of the exam 00:25:06.419 --> 00:25:09.710 align:start position:0% about pans uh for purposes of the exam we're<00:25:06.960> really<00:25:07.260> talking<00:25:07.740> about<00:25:08.520> Bluetooth<00:25:09.059> now 00:25:09.710 --> 00:25:09.720 align:start position:0% we're really talking about Bluetooth now 00:25:09.720 --> 00:25:12.169 align:start position:0% we're really talking about Bluetooth now I<00:25:10.020> might<00:25:10.140> consider<00:25:10.620> pan<00:25:11.100> a<00:25:11.520> sort<00:25:11.640> of<00:25:11.820> local 00:25:12.169 --> 00:25:12.179 align:start position:0% I might consider pan a sort of local 00:25:12.179 --> 00:25:14.510 align:start position:0% I might consider pan a sort of local area<00:25:12.539> network<00:25:12.960> but 00:25:14.510 --> 00:25:14.520 align:start position:0% area network but 00:25:14.520 --> 00:25:16.909 align:start position:0% area network but for<00:25:15.179> our<00:25:15.419> sake<00:25:15.600> we're<00:25:15.900> just<00:25:16.080> gonna<00:25:16.200> group<00:25:16.679> this 00:25:16.909 --> 00:25:16.919 align:start position:0% for our sake we're just gonna group this 00:25:16.919 --> 00:25:18.770 align:start position:0% for our sake we're just gonna group this into<00:25:17.100> wands<00:25:17.640> right<00:25:17.820> now<00:25:17.940> but<00:25:18.179> this<00:25:18.419> could<00:25:18.539> be 00:25:18.770 --> 00:25:18.780 align:start position:0% into wands right now but this could be 00:25:18.780 --> 00:25:20.510 align:start position:0% into wands right now but this could be considered<00:25:19.260> something<00:25:19.919> a<00:25:20.159> little<00:25:20.280> different 00:25:20.510 --> 00:25:20.520 align:start position:0% considered something a little different 00:25:20.520 --> 00:25:22.310 align:start position:0% considered something a little different okay<00:25:20.940> so<00:25:21.299> I'm<00:25:21.419> just<00:25:21.600> gonna<00:25:21.780> sort<00:25:22.020> of<00:25:22.140> put 00:25:22.310 --> 00:25:22.320 align:start position:0% okay so I'm just gonna sort of put 00:25:22.320 --> 00:25:25.549 align:start position:0% okay so I'm just gonna sort of put brackets<00:25:22.860> around<00:25:23.100> that<00:25:23.460> and<00:25:24.120> a<00:25:24.240> w<00:25:24.480> pan<00:25:24.900> or<00:25:25.380> a 00:25:25.549 --> 00:25:25.559 align:start position:0% brackets around that and a w pan or a 00:25:25.559 --> 00:25:28.250 align:start position:0% brackets around that and a w pan or a wireless<00:25:25.799> pan<00:25:26.340> if<00:25:26.880> we<00:25:26.940> put<00:25:27.179> that<00:25:27.360> W<00:25:27.659> in<00:25:28.140> front 00:25:28.250 --> 00:25:28.260 align:start position:0% wireless pan if we put that W in front 00:25:28.260 --> 00:25:30.830 align:start position:0% wireless pan if we put that W in front of<00:25:28.380> it<00:25:28.559> uh<00:25:29.400> occurs<00:25:29.880> when<00:25:30.059> the<00:25:30.240> computers<00:25:30.600> are 00:25:30.830 --> 00:25:30.840 align:start position:0% of it uh occurs when the computers are 00:25:30.840 --> 00:25:33.649 align:start position:0% of it uh occurs when the computers are connected<00:25:31.200> together<00:25:31.440> wirelessly<00:25:32.400> but<00:25:33.360> not 00:25:33.649 --> 00:25:33.659 align:start position:0% connected together wirelessly but not 00:25:33.659 --> 00:25:36.769 align:start position:0% connected together wirelessly but not through<00:25:33.960> an<00:25:34.260> access<00:25:34.440> point<00:25:34.919> right<00:25:35.279> so<00:25:36.059> they're 00:25:36.769 --> 00:25:36.779 align:start position:0% through an access point right so they're 00:25:36.779 --> 00:25:39.850 align:start position:0% through an access point right so they're connected<00:25:37.320> literally<00:25:38.120> uh<00:25:39.120> to<00:25:39.360> one<00:25:39.659> another 00:25:39.850 --> 00:25:39.860 align:start position:0% connected literally uh to one another 00:25:39.860 --> 00:25:43.430 align:start position:0% connected literally uh to one another thanks<00:25:40.860> to<00:25:41.159> the<00:25:41.520> wireless<00:25:41.700> technology<00:25:42.600> but 00:25:43.430 --> 00:25:43.440 align:start position:0% thanks to the wireless technology but 00:25:43.440 --> 00:25:45.830 align:start position:0% thanks to the wireless technology but there<00:25:43.679> is<00:25:43.860> no<00:25:44.220> sort<00:25:44.460> of<00:25:44.580> Central<00:25:45.000> Access<00:25:45.480> Point 00:25:45.830 --> 00:25:45.840 align:start position:0% there is no sort of Central Access Point 00:25:45.840 --> 00:25:47.750 align:start position:0% there is no sort of Central Access Point that<00:25:46.080> they<00:25:46.200> all<00:25:46.380> connect<00:25:46.620> to 00:25:47.750 --> 00:25:47.760 align:start position:0% that they all connect to 00:25:47.760 --> 00:25:50.690 align:start position:0% that they all connect to now<00:25:48.299> the<00:25:48.539> next<00:25:48.720> type<00:25:48.960> is<00:25:49.200> a<00:25:49.440> can<00:25:49.620> or<00:25:50.100> a<00:25:50.279> campus 00:25:50.690 --> 00:25:50.700 align:start position:0% now the next type is a can or a campus 00:25:50.700 --> 00:25:53.350 align:start position:0% now the next type is a can or a campus area<00:25:50.940> network<00:25:51.360> and<00:25:51.960> I'm<00:25:52.080> assuming<00:25:52.500> from<00:25:52.860> the 00:25:53.350 --> 00:25:53.360 align:start position:0% area network and I'm assuming from the 00:25:53.360 --> 00:25:56.570 align:start position:0% area network and I'm assuming from the name<00:25:54.360> you<00:25:54.720> can<00:25:54.840> guess<00:25:55.020> that<00:25:55.380> this<00:25:55.799> is<00:25:55.980> a<00:25:56.279> Wan 00:25:56.570 --> 00:25:56.580 align:start position:0% name you can guess that this is a Wan 00:25:56.580 --> 00:25:58.490 align:start position:0% name you can guess that this is a Wan that<00:25:56.820> spans<00:25:57.120> the<00:25:57.360> geographical<00:25:58.020> area 00:25:58.490 --> 00:25:58.500 align:start position:0% that spans the geographical area 00:25:58.500 --> 00:26:02.930 align:start position:0% that spans the geographical area comparable<00:25:59.340> to<00:25:59.580> like<00:25:59.820> a<00:26:00.360> school<00:26:00.799> or<00:26:01.799> a<00:26:02.220> campus 00:26:02.930 --> 00:26:02.940 align:start position:0% comparable to like a school or a campus 00:26:02.940 --> 00:26:05.870 align:start position:0% comparable to like a school or a campus or<00:26:03.360> a<00:26:03.480> business<00:26:03.720> park<00:26:04.140> such<00:26:04.559> as<00:26:04.679> Yahoo<00:26:04.980> now 00:26:05.870 --> 00:26:05.880 align:start position:0% or a business park such as Yahoo now 00:26:05.880 --> 00:26:07.970 align:start position:0% or a business park such as Yahoo now again<00:26:06.120> some<00:26:06.720> people<00:26:06.840> might<00:26:07.140> consider<00:26:07.559> this<00:26:07.740> a 00:26:07.970 --> 00:26:07.980 align:start position:0% again some people might consider this a 00:26:07.980 --> 00:26:10.549 align:start position:0% again some people might consider this a land<00:26:08.100> some<00:26:08.400> might<00:26:08.580> consider<00:26:08.940> this<00:26:09.120> a<00:26:09.360> win<00:26:09.559> but 00:26:10.549 --> 00:26:10.559 align:start position:0% land some might consider this a win but 00:26:10.559 --> 00:26:13.190 align:start position:0% land some might consider this a win but for<00:26:11.039> our<00:26:11.279> sake<00:26:11.580> we're<00:26:11.880> just<00:26:12.059> going<00:26:12.240> to<00:26:12.419> assume 00:26:13.190 --> 00:26:13.200 align:start position:0% for our sake we're just going to assume 00:26:13.200 --> 00:26:15.110 align:start position:0% for our sake we're just going to assume that<00:26:13.380> this<00:26:13.620> is<00:26:13.860> dealing<00:26:14.400> with<00:26:14.580> some<00:26:14.820> sort<00:26:15.000> of 00:26:15.110 --> 00:26:15.120 align:start position:0% that this is dealing with some sort of 00:26:15.120 --> 00:26:17.810 align:start position:0% that this is dealing with some sort of Campus<00:26:15.539> some<00:26:15.900> sort<00:26:16.140> of<00:26:16.320> school<00:26:16.980> some<00:26:17.460> sort<00:26:17.700> of 00:26:17.810 --> 00:26:17.820 align:start position:0% Campus some sort of school some sort of 00:26:17.820 --> 00:26:20.930 align:start position:0% Campus some sort of school some sort of area<00:26:18.500> that<00:26:19.500> is<00:26:19.620> contained<00:26:20.039> all<00:26:20.340> by<00:26:20.580> one 00:26:20.930 --> 00:26:20.940 align:start position:0% area that is contained all by one 00:26:20.940 --> 00:26:24.169 align:start position:0% area that is contained all by one organization<00:26:21.720> so<00:26:22.080> for<00:26:22.380> instance<00:26:22.620> if<00:26:22.980> I<00:26:23.159> had<00:26:23.460> uh 00:26:24.169 --> 00:26:24.179 align:start position:0% organization so for instance if I had uh 00:26:24.179 --> 00:26:29.029 align:start position:0% organization so for instance if I had uh four<00:26:24.480> buildings<00:26:25.020> all<00:26:25.980> connected 00:26:29.029 --> 00:26:29.039 align:start position:0% 00:26:29.039 --> 00:26:32.210 align:start position:0% uh<00:26:29.940> and<00:26:30.120> each<00:26:30.360> of<00:26:30.480> them<00:26:30.600> has<00:26:31.080> let's<00:26:31.559> say<00:26:31.799> four 00:26:32.210 --> 00:26:32.220 align:start position:0% uh and each of them has let's say four 00:26:32.220 --> 00:26:34.250 align:start position:0% uh and each of them has let's say four floors 00:26:34.250 --> 00:26:34.260 align:start position:0% floors 00:26:34.260 --> 00:26:36.950 align:start position:0% floors right<00:26:34.740> there<00:26:35.039> might<00:26:35.220> be<00:26:35.340> a<00:26:35.700> lan<00:26:36.000> on<00:26:36.480> each<00:26:36.720> floor 00:26:36.950 --> 00:26:36.960 align:start position:0% right there might be a lan on each floor 00:26:36.960 --> 00:26:39.590 align:start position:0% right there might be a lan on each floor or<00:26:37.380> in<00:26:37.500> each<00:26:37.679> building<00:26:38.039> and<00:26:38.820> then<00:26:38.940> connecting 00:26:39.590 --> 00:26:39.600 align:start position:0% or in each building and then connecting 00:26:39.600 --> 00:26:41.570 align:start position:0% or in each building and then connecting each<00:26:39.960> land<00:26:40.260> together<00:26:40.559> is<00:26:40.980> going<00:26:41.100> to<00:26:41.220> be<00:26:41.340> this 00:26:41.570 --> 00:26:41.580 align:start position:0% each land together is going to be this 00:26:41.580 --> 00:26:43.549 align:start position:0% each land together is going to be this can<00:26:41.820> which<00:26:42.240> is<00:26:42.419> a<00:26:42.600> sort<00:26:42.720> of<00:26:42.840> wide<00:26:43.080> area<00:26:43.260> network 00:26:43.549 --> 00:26:43.559 align:start position:0% can which is a sort of wide area network 00:26:43.559 --> 00:26:45.830 align:start position:0% can which is a sort of wide area network but<00:26:44.159> because<00:26:44.340> the<00:26:44.700> wide<00:26:44.880> area<00:26:45.059> network<00:26:45.419> could 00:26:45.830 --> 00:26:45.840 align:start position:0% but because the wide area network could 00:26:45.840 --> 00:26:49.610 align:start position:0% but because the wide area network could denote<00:26:46.340> uh<00:26:47.340> the<00:26:47.640> internet<00:26:47.820> and<00:26:48.419> the<00:26:48.600> cloud<00:26:49.260> is 00:26:49.610 --> 00:26:49.620 align:start position:0% denote uh the internet and the cloud is 00:26:49.620 --> 00:26:52.610 align:start position:0% denote uh the internet and the cloud is sort<00:26:49.799> of<00:26:49.919> the<00:26:50.159> best<00:26:50.659> descriptor<00:26:51.659> of<00:26:51.840> that<00:26:52.020> we 00:26:52.610 --> 00:26:52.620 align:start position:0% sort of the best descriptor of that we 00:26:52.620 --> 00:26:53.810 align:start position:0% sort of the best descriptor of that we want<00:26:52.740> to<00:26:52.860> call<00:26:52.980> it<00:26:53.159> something<00:26:53.400> slightly 00:26:53.810 --> 00:26:53.820 align:start position:0% want to call it something slightly 00:26:53.820 --> 00:26:57.710 align:start position:0% want to call it something slightly different<00:26:54.140> now<00:26:55.140> a<00:26:55.620> man<00:26:55.740> is<00:26:56.100> a<00:26:56.340> metropolitan<00:26:57.179> or 00:26:57.710 --> 00:26:57.720 align:start position:0% different now a man is a metropolitan or 00:26:57.720 --> 00:27:01.549 align:start position:0% different now a man is a metropolitan or it<00:26:58.020> could<00:26:58.140> also<00:26:58.440> be<00:26:58.679> a<00:26:59.039> municipal 00:27:01.549 --> 00:27:01.559 align:start position:0% it could also be a municipal 00:27:01.559 --> 00:27:03.289 align:start position:0% it could also be a municipal area<00:27:02.159> network 00:27:03.289 --> 00:27:03.299 align:start position:0% area network 00:27:03.299 --> 00:27:06.350 align:start position:0% area network and<00:27:03.779> as<00:27:03.960> the<00:27:04.200> name<00:27:04.380> implies<00:27:05.039> It's<00:27:05.820> relatively 00:27:06.350 --> 00:27:06.360 align:start position:0% and as the name implies It's relatively 00:27:06.360 --> 00:27:09.529 align:start position:0% and as the name implies It's relatively the<00:27:06.600> size<00:27:06.779> of<00:27:07.080> a<00:27:07.320> city<00:27:07.559> or<00:27:08.400> a<00:27:08.580> town<00:27:08.820> or<00:27:09.360> a 00:27:09.529 --> 00:27:09.539 align:start position:0% the size of a city or a town or a 00:27:09.539 --> 00:27:11.630 align:start position:0% the size of a city or a town or a metropolitan<00:27:10.260> area<00:27:10.440> so<00:27:10.799> if<00:27:10.980> I<00:27:11.159> have<00:27:11.400> a 00:27:11.630 --> 00:27:11.640 align:start position:0% metropolitan area so if I have a 00:27:11.640 --> 00:27:14.510 align:start position:0% metropolitan area so if I have a business<00:27:11.820> that<00:27:12.539> like<00:27:12.720> the<00:27:12.960> cam<00:27:13.279> uh<00:27:14.279> has 00:27:14.510 --> 00:27:14.520 align:start position:0% business that like the cam uh has 00:27:14.520 --> 00:27:16.070 align:start position:0% business that like the cam uh has several<00:27:14.880> buildings<00:27:15.240> but<00:27:15.480> the<00:27:15.600> buildings<00:27:15.900> are 00:27:16.070 --> 00:27:16.080 align:start position:0% several buildings but the buildings are 00:27:16.080 --> 00:27:18.710 align:start position:0% several buildings but the buildings are now<00:27:16.520> separated<00:27:17.520> over<00:27:17.940> the<00:27:18.179> course<00:27:18.360> of<00:27:18.539> the 00:27:18.710 --> 00:27:18.720 align:start position:0% now separated over the course of the 00:27:18.720 --> 00:27:20.750 align:start position:0% now separated over the course of the city<00:27:18.840> as<00:27:19.080> opposed<00:27:19.440> to<00:27:19.440> some<00:27:19.740> in<00:27:20.100> my<00:27:20.279> own<00:27:20.400> campus 00:27:20.750 --> 00:27:20.760 align:start position:0% city as opposed to some in my own campus 00:27:20.760 --> 00:27:22.430 align:start position:0% city as opposed to some in my own campus then<00:27:21.179> I'm<00:27:21.360> probably<00:27:21.659> going<00:27:21.840> to<00:27:21.900> use<00:27:22.080> this 00:27:22.430 --> 00:27:22.440 align:start position:0% then I'm probably going to use this 00:27:22.440 --> 00:27:25.549 align:start position:0% then I'm probably going to use this terminology<00:27:23.120> again<00:27:24.120> or<00:27:24.600> a<00:27:24.840> global<00:27:25.320> area 00:27:25.549 --> 00:27:25.559 align:start position:0% terminology again or a global area 00:27:25.559 --> 00:27:27.470 align:start position:0% terminology again or a global area network<00:27:25.860> I<00:27:26.279> think<00:27:26.460> it's<00:27:26.580> sort<00:27:26.820> of<00:27:26.940> redundant 00:27:27.470 --> 00:27:27.480 align:start position:0% network I think it's sort of redundant 00:27:27.480 --> 00:27:30.590 align:start position:0% network I think it's sort of redundant but<00:27:28.260> these<00:27:28.980> are<00:27:29.039> networks<00:27:29.580> that<00:27:29.880> go<00:27:30.240> from 00:27:30.590 --> 00:27:30.600 align:start position:0% but these are networks that go from 00:27:30.600 --> 00:27:37.490 align:start position:0% but these are networks that go from country<00:27:30.900> to<00:27:31.260> country<00:27:31.559> or<00:27:32.039> around<00:27:32.400> uh 00:27:37.490 --> 00:27:37.500 align:start position:0% 00:27:37.500 --> 00:27:39.649 align:start position:0% these<00:27:38.100> are<00:27:38.220> networks<00:27:38.580> that<00:27:38.820> go<00:27:39.120> all<00:27:39.480> the<00:27:39.600> way 00:27:39.649 --> 00:27:39.659 align:start position:0% these are networks that go all the way 00:27:39.659 --> 00:27:41.330 align:start position:0% these are networks that go all the way from<00:27:40.200> country<00:27:40.440> to<00:27:40.679> country<00:27:40.919> all<00:27:41.159> the<00:27:41.340> way 00:27:41.330 --> 00:27:41.340 align:start position:0% from country to country all the way 00:27:41.340 --> 00:27:44.029 align:start position:0% from country to country all the way around<00:27:41.520> the<00:27:41.820> world<00:27:42.000> they<00:27:42.960> span<00:27:43.320> the<00:27:43.559> globe<00:27:43.919> and 00:27:44.029 --> 00:27:44.039 align:start position:0% around the world they span the globe and 00:27:44.039 --> 00:27:46.909 align:start position:0% around the world they span the globe and they're<00:27:44.220> going<00:27:44.340> to<00:27:44.520> utilize<00:27:44.940> Technologies<00:27:45.919> uh 00:27:46.909 --> 00:27:46.919 align:start position:0% they're going to utilize Technologies uh 00:27:46.919 --> 00:27:49.789 align:start position:0% they're going to utilize Technologies uh like<00:27:47.220> satellite<00:27:47.940> probably<00:27:48.500> and<00:27:49.500> the<00:27:49.679> reason 00:27:49.789 --> 00:27:49.799 align:start position:0% like satellite probably and the reason 00:27:49.799 --> 00:27:52.430 align:start position:0% like satellite probably and the reason we're<00:27:50.039> going<00:27:50.220> to<00:27:50.279> call<00:27:50.460> this<00:27:50.760> uh<00:27:51.299> again<00:27:51.600> is 00:27:52.430 --> 00:27:52.440 align:start position:0% we're going to call this uh again is 00:27:52.440 --> 00:27:54.470 align:start position:0% we're going to call this uh again is because<00:27:52.740> generally<00:27:53.340> speaking<00:27:53.820> the<00:27:54.059> global 00:27:54.470 --> 00:27:54.480 align:start position:0% because generally speaking the global 00:27:54.480 --> 00:27:57.470 align:start position:0% because generally speaking the global area<00:27:54.659> network<00:27:55.020> again<00:27:55.440> is<00:27:56.340> all<00:27:56.580> controlled<00:27:57.120> by 00:27:57.470 --> 00:27:57.480 align:start position:0% area network again is all controlled by 00:27:57.480 --> 00:28:07.430 align:start position:0% area network again is all controlled by one<00:27:58.020> sort<00:27:58.380> of<00:27:58.500> company 00:28:07.430 --> 00:28:07.440 align:start position:0% 00:28:07.440 --> 00:28:09.590 align:start position:0% as<00:28:07.860> opposed<00:28:08.159> to<00:28:08.159> a<00:28:08.520> Wan<00:28:08.760> which<00:28:09.059> as<00:28:09.179> we<00:28:09.419> just 00:28:09.590 --> 00:28:09.600 align:start position:0% as opposed to a Wan which as we just 00:28:09.600 --> 00:28:12.350 align:start position:0% as opposed to a Wan which as we just discussed<00:28:09.960> could<00:28:10.320> include<00:28:10.760> either<00:28:11.760> all<00:28:12.120> being 00:28:12.350 --> 00:28:12.360 align:start position:0% discussed could include either all being 00:28:12.360 --> 00:28:14.390 align:start position:0% discussed could include either all being controlled<00:28:12.659> by<00:28:12.779> one<00:28:12.960> company<00:28:13.200> or 00:28:14.390 --> 00:28:14.400 align:start position:0% controlled by one company or 00:28:14.400 --> 00:28:17.390 align:start position:0% controlled by one company or all<00:28:15.000> being<00:28:15.240> controlled<00:28:15.900> by<00:28:16.799> uh<00:28:17.159> you<00:28:17.340> know 00:28:17.390 --> 00:28:17.400 align:start position:0% all being controlled by uh you know 00:28:17.400 --> 00:28:19.149 align:start position:0% all being controlled by uh you know disparate<00:28:17.880> companies<00:28:18.240> such<00:28:18.480> as<00:28:18.600> the<00:28:18.840> internet 00:28:19.149 --> 00:28:19.159 align:start position:0% disparate companies such as the internet 00:28:19.159 --> 00:28:23.210 align:start position:0% disparate companies such as the internet finally<00:28:20.159> an<00:28:21.000> En<00:28:21.360> which<00:28:22.140> is<00:28:22.380> the<00:28:22.620> only<00:28:22.740> one<00:28:22.919> that 00:28:23.210 --> 00:28:23.220 align:start position:0% finally an En which is the only one that 00:28:23.220 --> 00:28:25.850 align:start position:0% finally an En which is the only one that breaks<00:28:23.580> from<00:28:23.760> this<00:28:24.000> convention<00:28:24.480> is<00:28:25.260> called<00:28:25.500> an 00:28:25.850 --> 00:28:25.860 align:start position:0% breaks from this convention is called an 00:28:25.860 --> 00:28:28.010 align:start position:0% breaks from this convention is called an Enterprise<00:28:26.159> Network<00:28:26.940> it's<00:28:27.360> a<00:28:27.600> network<00:28:27.720> that 00:28:28.010 --> 00:28:28.020 align:start position:0% Enterprise Network it's a network that 00:28:28.020 --> 00:28:30.890 align:start position:0% Enterprise Network it's a network that includes<00:28:28.380> usually<00:28:28.740> aspects<00:28:29.340> of<00:28:29.520> both<00:28:29.820> a<00:28:30.480> Wan 00:28:30.890 --> 00:28:30.900 align:start position:0% includes usually aspects of both a Wan 00:28:30.900 --> 00:28:33.649 align:start position:0% includes usually aspects of both a Wan and<00:28:31.620> a<00:28:31.799> lan<00:28:32.100> and<00:28:32.640> it's<00:28:32.760> typically<00:28:33.120> owned<00:28:33.539> and 00:28:33.649 --> 00:28:33.659 align:start position:0% and a lan and it's typically owned and 00:28:33.659 --> 00:28:35.810 align:start position:0% and a lan and it's typically owned and operated<00:28:34.020> by<00:28:34.440> a<00:28:34.740> single<00:28:35.039> entity<00:28:35.460> or 00:28:35.810 --> 00:28:35.820 align:start position:0% operated by a single entity or 00:28:35.820 --> 00:28:38.450 align:start position:0% operated by a single entity or organization<00:28:36.419> just<00:28:37.140> like<00:28:37.380> a<00:28:37.740> gan<00:28:38.039> might<00:28:38.279> be 00:28:38.450 --> 00:28:38.460 align:start position:0% organization just like a gan might be 00:28:38.460 --> 00:28:41.450 align:start position:0% organization just like a gan might be now<00:28:39.000> again<00:28:39.240> these<00:28:39.720> terms<00:28:40.200> are<00:28:40.679> very<00:28:40.860> fluid<00:28:41.340> and 00:28:41.450 --> 00:28:41.460 align:start position:0% now again these terms are very fluid and 00:28:41.460 --> 00:28:43.610 align:start position:0% now again these terms are very fluid and flexible<00:28:42.000> and<00:28:42.720> depending<00:28:43.020> on<00:28:43.140> who<00:28:43.320> you<00:28:43.500> talk 00:28:43.610 --> 00:28:43.620 align:start position:0% flexible and depending on who you talk 00:28:43.620 --> 00:28:45.169 align:start position:0% flexible and depending on who you talk to<00:28:43.740> they'll<00:28:44.159> call<00:28:44.279> it<00:28:44.460> different<00:28:44.640> things<00:28:44.940> so 00:28:45.169 --> 00:28:45.179 align:start position:0% to they'll call it different things so 00:28:45.179 --> 00:28:47.870 align:start position:0% to they'll call it different things so you<00:28:45.419> might<00:28:45.539> I<00:28:46.140> worked<00:28:46.440> for<00:28:46.620> a<00:28:46.860> an<00:28:47.279> organization 00:28:47.870 --> 00:28:47.880 align:start position:0% you might I worked for a an organization 00:28:47.880 --> 00:28:51.049 align:start position:0% you might I worked for a an organization we<00:28:48.480> never<00:28:48.659> used<00:28:49.140> the<00:28:49.740> word<00:28:49.860> man<00:28:50.220> we<00:28:50.580> always<00:28:50.760> use 00:28:51.049 --> 00:28:51.059 align:start position:0% we never used the word man we always use 00:28:51.059 --> 00:28:53.570 align:start position:0% we never used the word man we always use the<00:28:51.240> word<00:28:51.419> when<00:28:51.919> talking<00:28:52.919> about<00:28:53.100> the<00:28:53.400> network 00:28:53.570 --> 00:28:53.580 align:start position:0% the word when talking about the network 00:28:53.580 --> 00:28:55.730 align:start position:0% the word when talking about the network that<00:28:53.880> was<00:28:54.059> deployed<00:28:54.480> over<00:28:54.779> the<00:28:55.080> entire<00:28:55.440> city 00:28:55.730 --> 00:28:55.740 align:start position:0% that was deployed over the entire city 00:28:55.740 --> 00:28:57.890 align:start position:0% that was deployed over the entire city however<00:28:56.520> certain<00:28:56.940> individuals<00:28:57.600> certain 00:28:57.890 --> 00:28:57.900 align:start position:0% however certain individuals certain 00:28:57.900 --> 00:28:59.450 align:start position:0% however certain individuals certain organizations<00:28:58.440> will<00:28:58.799> call<00:28:58.980> these<00:28:59.340> different 00:28:59.450 --> 00:28:59.460 align:start position:0% organizations will call these different 00:28:59.460 --> 00:29:01.070 align:start position:0% organizations will call these different things<00:28:59.760> and<00:29:00.059> the<00:29:00.179> names<00:29:00.299> might<00:29:00.659> change<00:29:00.840> as 00:29:01.070 --> 00:29:01.080 align:start position:0% things and the names might change as 00:29:01.080 --> 00:29:03.950 align:start position:0% things and the names might change as well<00:29:01.260> but<00:29:01.740> it's<00:29:01.980> important<00:29:02.520> to<00:29:03.179> have<00:29:03.419> a<00:29:03.659> firm 00:29:03.950 --> 00:29:03.960 align:start position:0% well but it's important to have a firm 00:29:03.960 --> 00:29:07.610 align:start position:0% well but it's important to have a firm understanding<00:29:04.500> of<00:29:04.799> this<00:29:05.039> just<00:29:05.760> from<00:29:06.000> a<00:29:06.179> basic 00:29:07.610 --> 00:29:07.620 align:start position:0% understanding of this just from a basic 00:29:07.620 --> 00:29:10.250 align:start position:0% understanding of this just from a basic you<00:29:08.279> know<00:29:08.400> definition<00:29:08.940> standpoint<00:29:09.840> but<00:29:10.020> also 00:29:10.250 --> 00:29:10.260 align:start position:0% you know definition standpoint but also 00:29:10.260 --> 00:29:11.450 align:start position:0% you know definition standpoint but also so<00:29:10.380> that<00:29:10.559> if<00:29:10.679> you<00:29:10.799> go<00:29:10.860> out<00:29:10.980> in<00:29:11.100> the<00:29:11.159> fields<00:29:11.400> and 00:29:11.450 --> 00:29:11.460 align:start position:0% so that if you go out in the fields and 00:29:11.460 --> 00:29:12.649 align:start position:0% so that if you go out in the fields and you<00:29:11.640> hear<00:29:11.760> people<00:29:12.000> talking<00:29:12.240> these<00:29:12.539> different 00:29:12.649 --> 00:29:12.659 align:start position:0% you hear people talking these different 00:29:12.659 --> 00:29:17.390 align:start position:0% you hear people talking these different terms<00:29:13.020> you<00:29:13.500> can<00:29:13.559> talk<00:29:13.740> the<00:29:13.980> talk<00:29:14.159> as<00:29:14.400> well 00:29:17.390 --> 00:29:17.400 align:start position:0% 00:29:17.400 --> 00:29:20.149 align:start position:0% now<00:29:17.760> unlike<00:29:18.419> land<00:29:18.960> administrators<00:29:19.679> whose 00:29:20.149 --> 00:29:20.159 align:start position:0% now unlike land administrators whose 00:29:20.159 --> 00:29:22.430 align:start position:0% now unlike land administrators whose Duties<00:29:20.520> are<00:29:20.700> quite<00:29:21.059> varied<00:29:21.600> when 00:29:22.430 --> 00:29:22.440 align:start position:0% Duties are quite varied when 00:29:22.440 --> 00:29:24.830 align:start position:0% Duties are quite varied when administrators<00:29:23.159> are<00:29:23.520> typically<00:29:23.880> specialists 00:29:24.830 --> 00:29:24.840 align:start position:0% administrators are typically specialists 00:29:24.840 --> 00:29:26.990 align:start position:0% administrators are typically specialists in<00:29:25.200> their<00:29:25.380> respective<00:29:25.860> Fields<00:29:26.340> so<00:29:26.880> they're 00:29:26.990 --> 00:29:27.000 align:start position:0% in their respective Fields so they're 00:29:27.000 --> 00:29:28.549 align:start position:0% in their respective Fields so they're responsible<00:29:27.480> for<00:29:27.779> more<00:29:28.080> complex 00:29:28.549 --> 00:29:28.559 align:start position:0% responsible for more complex 00:29:28.559 --> 00:29:31.549 align:start position:0% responsible for more complex infrastructures<00:29:29.340> and<00:29:29.700> as<00:29:29.880> a<00:29:30.059> result<00:29:30.380> uh<00:29:31.380> they 00:29:31.549 --> 00:29:31.559 align:start position:0% infrastructures and as a result uh they 00:29:31.559 --> 00:29:33.529 align:start position:0% infrastructures and as a result uh they need<00:29:31.740> to<00:29:31.860> be<00:29:31.980> more<00:29:32.159> fluent<00:29:32.520> in<00:29:32.760> say<00:29:33.059> routing 00:29:33.529 --> 00:29:33.539 align:start position:0% need to be more fluent in say routing 00:29:33.539 --> 00:29:35.149 align:start position:0% need to be more fluent in say routing structures<00:29:34.020> and<00:29:34.320> troubleshooting<00:29:34.919> different 00:29:35.149 --> 00:29:35.159 align:start position:0% structures and troubleshooting different 00:29:35.159 --> 00:29:37.669 align:start position:0% structures and troubleshooting different difficult<00:29:36.000> or<00:29:36.299> different<00:29:36.539> network<00:29:36.960> issues 00:29:37.669 --> 00:29:37.679 align:start position:0% difficult or different network issues 00:29:37.679 --> 00:29:40.669 align:start position:0% difficult or different network issues they're<00:29:38.220> also<00:29:38.520> responsible<00:29:39.000> for<00:29:39.539> say<00:29:40.020> data 00:29:40.669 --> 00:29:40.679 align:start position:0% they're also responsible for say data 00:29:40.679 --> 00:29:43.250 align:start position:0% they're also responsible for say data versus<00:29:40.860> voice<00:29:41.520> systems<00:29:42.179> and<00:29:42.960> when 00:29:43.250 --> 00:29:43.260 align:start position:0% versus voice systems and when 00:29:43.260 --> 00:29:45.769 align:start position:0% versus voice systems and when administrators<00:29:44.220> concentrate<00:29:45.059> generally<00:29:45.480> on 00:29:45.769 --> 00:29:45.779 align:start position:0% administrators concentrate generally on 00:29:45.779 --> 00:29:48.529 align:start position:0% administrators concentrate generally on network<00:29:46.080> oriented<00:29:46.679> problems<00:29:47.100> and<00:29:47.820> not<00:29:48.120> user 00:29:48.529 --> 00:29:48.539 align:start position:0% network oriented problems and not user 00:29:48.539 --> 00:29:50.750 align:start position:0% network oriented problems and not user related<00:29:48.840> issues<00:29:49.380> like<00:29:49.679> a<00:29:49.919> land<00:29:50.100> administrator 00:29:50.750 --> 00:29:50.760 align:start position:0% related issues like a land administrator 00:29:50.760 --> 00:29:54.230 align:start position:0% related issues like a land administrator so<00:29:51.600> with<00:29:52.020> a<00:29:52.260> a<00:29:52.500> lan<00:29:53.159> we're<00:29:53.700> really<00:29:53.880> going<00:29:54.120> to 00:29:54.230 --> 00:29:54.240 align:start position:0% so with a a lan we're really going to 00:29:54.240 --> 00:29:56.570 align:start position:0% so with a a lan we're really going to get<00:29:54.299> these<00:29:54.860> user-oriented<00:29:55.860> tasks<00:29:56.340> right 00:29:56.570 --> 00:29:56.580 align:start position:0% get these user-oriented tasks right 00:29:56.580 --> 00:29:58.190 align:start position:0% get these user-oriented tasks right because<00:29:56.880> they're<00:29:57.240> dealing<00:29:57.539> with<00:29:57.659> the<00:29:57.779> user<00:29:58.020> on 00:29:58.190 --> 00:29:58.200 align:start position:0% because they're dealing with the user on 00:29:58.200 --> 00:30:00.590 align:start position:0% because they're dealing with the user on a<00:29:58.320> day-to-day<00:29:58.679> basic<00:29:59.100> a<00:29:59.820> Wan<00:30:00.120> administrator 00:30:00.590 --> 00:30:00.600 align:start position:0% a day-to-day basic a Wan administrator 00:30:00.600 --> 00:30:01.850 align:start position:0% a day-to-day basic a Wan administrator is<00:30:00.720> really<00:30:00.960> not<00:30:01.140> dealing<00:30:01.380> with<00:30:01.500> these<00:30:01.740> or 00:30:01.850 --> 00:30:01.860 align:start position:0% is really not dealing with these or 00:30:01.860 --> 00:30:02.990 align:start position:0% is really not dealing with these or they're<00:30:02.100> dealing<00:30:02.279> with<00:30:02.399> sometimes<00:30:02.700> what<00:30:02.880> we 00:30:02.990 --> 00:30:03.000 align:start position:0% they're dealing with sometimes what we 00:30:03.000 --> 00:30:06.350 align:start position:0% they're dealing with sometimes what we would<00:30:03.120> refer<00:30:03.419> to<00:30:03.600> as<00:30:04.039> the<00:30:05.039> back<00:30:05.279> end<00:30:05.580> and<00:30:06.179> in 00:30:06.350 --> 00:30:06.360 align:start position:0% would refer to as the back end and in 00:30:06.360 --> 00:30:08.690 align:start position:0% would refer to as the back end and in some<00:30:06.539> cases<00:30:06.899> as<00:30:07.260> well<00:30:07.440> they're<00:30:08.100> also<00:30:08.460> going<00:30:08.520> to 00:30:08.690 --> 00:30:08.700 align:start position:0% some cases as well they're also going to 00:30:08.700 --> 00:30:11.269 align:start position:0% some cases as well they're also going to be<00:30:08.820> a<00:30:09.000> little<00:30:09.120> more<00:30:09.419> specialized<00:30:10.380> in<00:30:11.039> what 00:30:11.269 --> 00:30:11.279 align:start position:0% be a little more specialized in what 00:30:11.279 --> 00:30:13.130 align:start position:0% be a little more specialized in what they<00:30:11.520> do<00:30:11.700> since<00:30:12.240> what<00:30:12.659> they're<00:30:12.779> dealing<00:30:13.020> with 00:30:13.130 --> 00:30:13.140 align:start position:0% they do since what they're dealing with 00:30:13.140 --> 00:30:14.990 align:start position:0% they do since what they're dealing with is<00:30:13.320> a<00:30:13.500> lot<00:30:13.559> more<00:30:13.679> complex<00:30:14.039> a<00:30:14.640> lan 00:30:14.990 --> 00:30:15.000 align:start position:0% is a lot more complex a lan 00:30:15.000 --> 00:30:16.970 align:start position:0% is a lot more complex a lan administrator<00:30:15.659> can<00:30:16.020> sort<00:30:16.260> of<00:30:16.320> be<00:30:16.500> a<00:30:16.679> jack<00:30:16.799> of 00:30:16.970 --> 00:30:16.980 align:start position:0% administrator can sort of be a jack of 00:30:16.980 --> 00:30:19.490 align:start position:0% administrator can sort of be a jack of all<00:30:17.100> trades<00:30:17.760> a<00:30:18.240> wand<00:30:18.539> administrator<00:30:19.020> we<00:30:19.320> want 00:30:19.490 --> 00:30:19.500 align:start position:0% all trades a wand administrator we want 00:30:19.500 --> 00:30:21.590 align:start position:0% all trades a wand administrator we want to<00:30:19.620> be<00:30:19.740> a<00:30:19.980> master<00:30:20.100> of<00:30:20.460> exactly<00:30:20.820> what<00:30:21.059> it<00:30:21.179> is<00:30:21.299> he 00:30:21.590 --> 00:30:21.600 align:start position:0% to be a master of exactly what it is he 00:30:21.600 --> 00:30:23.269 align:start position:0% to be a master of exactly what it is he or<00:30:21.779> she<00:30:21.960> is<00:30:22.080> dealing<00:30:22.440> with 00:30:23.269 --> 00:30:23.279 align:start position:0% or she is dealing with 00:30:23.279 --> 00:30:26.210 align:start position:0% or she is dealing with uh<00:30:23.940> one<00:30:24.120> of<00:30:24.240> the<00:30:24.360> other<00:30:24.539> main<00:30:24.960> duties<00:30:25.380> of<00:30:25.740> a<00:30:25.860> Wan 00:30:26.210 --> 00:30:26.220 align:start position:0% uh one of the other main duties of a Wan 00:30:26.220 --> 00:30:28.250 align:start position:0% uh one of the other main duties of a Wan administrator<00:30:26.820> is<00:30:27.179> the<00:30:27.480> development<00:30:28.020> and 00:30:28.250 --> 00:30:28.260 align:start position:0% administrator is the development and 00:30:28.260 --> 00:30:30.889 align:start position:0% administrator is the development and implementation<00:30:28.919> of<00:30:29.520> certain<00:30:29.760> scripts<00:30:30.360> that 00:30:30.889 --> 00:30:30.899 align:start position:0% implementation of certain scripts that 00:30:30.899 --> 00:30:32.570 align:start position:0% implementation of certain scripts that are<00:30:31.020> going<00:30:31.140> to<00:30:31.380> automate<00:30:31.919> certain<00:30:32.340> Network 00:30:32.570 --> 00:30:32.580 align:start position:0% are going to automate certain Network 00:30:32.580 --> 00:30:35.510 align:start position:0% are going to automate certain Network processes<00:30:33.480> and<00:30:34.440> they're<00:30:34.679> also<00:30:34.980> going<00:30:35.100> to<00:30:35.279> plan 00:30:35.510 --> 00:30:35.520 align:start position:0% processes and they're also going to plan 00:30:35.520 --> 00:30:38.149 align:start position:0% processes and they're also going to plan for<00:30:35.940> and<00:30:36.240> test<00:30:36.539> and<00:30:36.840> push<00:30:37.140> out<00:30:37.320> upgrades<00:30:37.919> and 00:30:38.149 --> 00:30:38.159 align:start position:0% for and test and push out upgrades and 00:30:38.159 --> 00:30:40.610 align:start position:0% for and test and push out upgrades and updates<00:30:38.580> to<00:30:39.179> the<00:30:39.539> infrastructure<00:30:40.320> of<00:30:40.500> the 00:30:40.610 --> 00:30:40.620 align:start position:0% updates to the infrastructure of the 00:30:40.620 --> 00:30:42.409 align:start position:0% updates to the infrastructure of the network<00:30:40.740> network<00:30:41.100> wide<00:30:41.640> whereas<00:30:42.179> a<00:30:42.360> land 00:30:42.409 --> 00:30:42.419 align:start position:0% network network wide whereas a land 00:30:42.419 --> 00:30:44.810 align:start position:0% network network wide whereas a land administrator<00:30:43.080> is<00:30:43.559> going<00:30:43.740> to<00:30:43.919> do<00:30:44.100> this<00:30:44.340> on<00:30:44.700> a 00:30:44.810 --> 00:30:44.820 align:start position:0% administrator is going to do this on a 00:30:44.820 --> 00:30:46.850 align:start position:0% administrator is going to do this on a sort<00:30:45.000> of<00:30:45.179> local<00:30:45.419> basis<00:30:46.020> perhaps<00:30:46.440> to<00:30:46.679> the 00:30:46.850 --> 00:30:46.860 align:start position:0% sort of local basis perhaps to the 00:30:46.860 --> 00:30:49.370 align:start position:0% sort of local basis perhaps to the computers<00:30:47.340> in<00:30:47.700> their<00:30:47.880> Network<00:30:48.059> so<00:30:48.779> we<00:30:48.960> can<00:30:49.140> see 00:30:49.370 --> 00:30:49.380 align:start position:0% computers in their Network so we can see 00:30:49.380 --> 00:30:50.950 align:start position:0% computers in their Network so we can see sort<00:30:49.679> of<00:30:49.799> how<00:30:50.220> these<00:30:50.700> are<00:30:50.760> getting 00:30:50.950 --> 00:30:50.960 align:start position:0% sort of how these are getting 00:30:50.960 --> 00:30:53.930 align:start position:0% sort of how these are getting differentiated<00:30:51.960> here<00:30:52.440> a<00:30:53.039> Wan<00:30:53.279> administrators 00:30:53.930 --> 00:30:53.940 align:start position:0% differentiated here a Wan administrators 00:30:53.940 --> 00:30:57.769 align:start position:0% differentiated here a Wan administrators a<00:30:54.299> lot<00:30:54.419> more<00:30:54.919> specialized<00:30:55.919> and<00:30:56.700> they're<00:30:57.539> not 00:30:57.769 --> 00:30:57.779 align:start position:0% a lot more specialized and they're not 00:30:57.779 --> 00:31:00.470 align:start position:0% a lot more specialized and they're not focused<00:30:58.260> on<00:30:58.620> user<00:30:59.159> oriented 00:31:00.470 --> 00:31:00.480 align:start position:0% focused on user oriented 00:31:00.480 --> 00:31:02.930 align:start position:0% focused on user oriented tasks<00:31:01.320> they're<00:31:01.559> looking<00:31:01.740> at<00:31:02.039> Network<00:31:02.460> stuff 00:31:02.930 --> 00:31:02.940 align:start position:0% tasks they're looking at Network stuff 00:31:02.940 --> 00:31:05.029 align:start position:0% tasks they're looking at Network stuff so<00:31:03.480> you<00:31:03.659> can<00:31:03.720> see<00:31:03.840> a<00:31:04.020> Wan<00:31:04.260> administrator<00:31:04.740> again 00:31:05.029 --> 00:31:05.039 align:start position:0% so you can see a Wan administrator again 00:31:05.039 --> 00:31:07.130 align:start position:0% so you can see a Wan administrator again dealing<00:31:05.700> with<00:31:05.820> the<00:31:06.000> back<00:31:06.179> end<00:31:06.360> much<00:31:06.899> more 00:31:07.130 --> 00:31:07.140 align:start position:0% dealing with the back end much more 00:31:07.140 --> 00:31:08.930 align:start position:0% dealing with the back end much more specifically<00:31:07.740> generally<00:31:08.220> more<00:31:08.580> Technical 00:31:08.930 --> 00:31:08.940 align:start position:0% specifically generally more Technical 00:31:08.940 --> 00:31:10.909 align:start position:0% specifically generally more Technical and<00:31:09.539> generally<00:31:09.840> also<00:31:10.260> a<00:31:10.440> little<00:31:10.559> bit<00:31:10.679> more 00:31:10.909 --> 00:31:10.919 align:start position:0% and generally also a little bit more 00:31:10.919 --> 00:31:14.389 align:start position:0% and generally also a little bit more training<00:31:11.399> than<00:31:11.940> a<00:31:12.179> land<00:31:12.299> administrator 00:31:14.389 --> 00:31:14.399 align:start position:0% training than a land administrator 00:31:14.399 --> 00:31:16.730 align:start position:0% training than a land administrator now<00:31:14.880> let's<00:31:15.059> talk<00:31:15.240> about<00:31:15.360> the<00:31:15.659> internet<00:31:15.840> or<00:31:16.440> the 00:31:16.730 --> 00:31:16.740 align:start position:0% now let's talk about the internet or the 00:31:16.740 --> 00:31:20.090 align:start position:0% now let's talk about the internet or the World<00:31:16.860> Wide<00:31:17.279> Web<00:31:17.520> which<00:31:18.120> is<00:31:18.480> a<00:31:18.960> public<00:31:19.200> wide 00:31:20.090 --> 00:31:20.100 align:start position:0% World Wide Web which is a public wide 00:31:20.100 --> 00:31:24.409 align:start position:0% World Wide Web which is a public wide area<00:31:20.340> network<00:31:20.880> right<00:31:21.659> it<00:31:21.960> is<00:31:22.260> the<00:31:23.100> largest<00:31:23.580> Wan 00:31:24.409 --> 00:31:24.419 align:start position:0% area network right it is the largest Wan 00:31:24.419 --> 00:31:27.049 align:start position:0% area network right it is the largest Wan that<00:31:24.779> we<00:31:25.020> have<00:31:25.260> and<00:31:25.860> it<00:31:26.039> essentially<00:31:26.399> connects 00:31:27.049 --> 00:31:27.059 align:start position:0% that we have and it essentially connects 00:31:27.059 --> 00:31:29.269 align:start position:0% that we have and it essentially connects every<00:31:27.419> country<00:31:27.720> on<00:31:28.080> the<00:31:28.260> planet<00:31:28.380> in<00:31:28.799> some<00:31:29.039> ways 00:31:29.269 --> 00:31:29.279 align:start position:0% every country on the planet in some ways 00:31:29.279 --> 00:31:31.730 align:start position:0% every country on the planet in some ways every<00:31:29.580> computer<00:31:29.820> on<00:31:30.240> the<00:31:30.360> planet<00:31:30.500> it's<00:31:31.500> used 00:31:31.730 --> 00:31:31.740 align:start position:0% every computer on the planet it's used 00:31:31.740 --> 00:31:33.710 align:start position:0% every computer on the planet it's used for<00:31:32.100> many<00:31:32.279> different<00:31:32.580> things<00:31:32.880> including<00:31:33.480> but 00:31:33.710 --> 00:31:33.720 align:start position:0% for many different things including but 00:31:33.720 --> 00:31:35.810 align:start position:0% for many different things including but certainly<00:31:34.080> not<00:31:34.320> limited<00:31:34.740> to<00:31:34.980> sending<00:31:35.700> and 00:31:35.810 --> 00:31:35.820 align:start position:0% certainly not limited to sending and 00:31:35.820 --> 00:31:38.389 align:start position:0% certainly not limited to sending and receiving<00:31:36.179> email<00:31:37.039> initiating<00:31:38.039> and 00:31:38.389 --> 00:31:38.399 align:start position:0% receiving email initiating and 00:31:38.399 --> 00:31:40.450 align:start position:0% receiving email initiating and completing<00:31:38.880> commercial<00:31:39.360> and<00:31:39.899> private 00:31:40.450 --> 00:31:40.460 align:start position:0% completing commercial and private 00:31:40.460 --> 00:31:44.029 align:start position:0% completing commercial and private transactions<00:31:41.460> uh<00:31:42.419> commute<00:31:43.039> communicating 00:31:44.029 --> 00:31:44.039 align:start position:0% transactions uh commute communicating 00:31:44.039 --> 00:31:46.490 align:start position:0% transactions uh commute communicating and<00:31:44.460> allowing<00:31:45.000> people<00:31:45.419> to<00:31:45.779> connect<00:31:45.960> to<00:31:46.380> one 00:31:46.490 --> 00:31:46.500 align:start position:0% and allowing people to connect to one 00:31:46.500 --> 00:31:48.350 align:start position:0% and allowing people to connect to one another<00:31:46.679> that<00:31:47.159> are<00:31:47.279> sitting<00:31:47.820> in<00:31:47.940> the<00:31:48.120> same 00:31:48.350 --> 00:31:48.360 align:start position:0% another that are sitting in the same 00:31:48.360 --> 00:31:50.389 align:start position:0% another that are sitting in the same room<00:31:48.720> or<00:31:49.200> perhaps<00:31:49.500> even<00:31:49.740> on<00:31:49.980> the<00:31:50.100> other<00:31:50.159> side 00:31:50.389 --> 00:31:50.399 align:start position:0% room or perhaps even on the other side 00:31:50.399 --> 00:31:52.370 align:start position:0% room or perhaps even on the other side of<00:31:50.580> the<00:31:50.700> world<00:31:50.880> the<00:31:51.539> internet<00:31:51.659> is<00:31:52.020> really<00:31:52.200> the 00:31:52.370 --> 00:31:52.380 align:start position:0% of the world the internet is really the 00:31:52.380 --> 00:31:53.870 align:start position:0% of the world the internet is really the method<00:31:52.620> by<00:31:52.799> which<00:31:53.039> everyone<00:31:53.340> in<00:31:53.580> the<00:31:53.700> world 00:31:53.870 --> 00:31:53.880 align:start position:0% method by which everyone in the world 00:31:53.880 --> 00:31:56.570 align:start position:0% method by which everyone in the world can<00:31:54.720> communicate<00:31:55.380> in<00:31:55.799> one<00:31:55.980> way<00:31:56.100> or<00:31:56.279> the<00:31:56.460> other 00:31:56.570 --> 00:31:56.580 align:start position:0% can communicate in one way or the other 00:31:56.580 --> 00:31:59.269 align:start position:0% can communicate in one way or the other and<00:31:56.880> in<00:31:57.120> some<00:31:57.299> ways<00:31:57.659> we<00:31:58.140> can<00:31:58.320> actually<00:31:58.559> use<00:31:59.100> it 00:31:59.269 --> 00:31:59.279 align:start position:0% and in some ways we can actually use it 00:31:59.279 --> 00:32:02.210 align:start position:0% and in some ways we can actually use it to<00:31:59.580> create<00:31:59.760> our<00:32:00.120> own<00:32:00.360> virtual<00:32:01.200> lands<00:32:01.799> that<00:32:02.039> are 00:32:02.210 --> 00:32:02.220 align:start position:0% to create our own virtual lands that are 00:32:02.220 --> 00:32:04.010 align:start position:0% to create our own virtual lands that are private<00:32:02.580> and<00:32:02.760> we'll<00:32:02.940> talk<00:32:03.179> more<00:32:03.419> about<00:32:03.659> that 00:32:04.010 --> 00:32:04.020 align:start position:0% private and we'll talk more about that 00:32:04.020 --> 00:32:05.810 align:start position:0% private and we'll talk more about that the<00:32:04.500> other<00:32:04.620> thing<00:32:04.799> that's<00:32:04.980> important<00:32:05.520> to<00:32:05.700> know 00:32:05.810 --> 00:32:05.820 align:start position:0% the other thing that's important to know 00:32:05.820 --> 00:32:09.230 align:start position:0% the other thing that's important to know is<00:32:06.179> every<00:32:06.659> bit<00:32:06.899> of<00:32:07.140> data<00:32:07.500> is<00:32:07.740> stored<00:32:08.240> somewhere 00:32:09.230 --> 00:32:09.240 align:start position:0% is every bit of data is stored somewhere 00:32:09.240 --> 00:32:11.810 align:start position:0% is every bit of data is stored somewhere on<00:32:10.080> a<00:32:10.260> server<00:32:10.500> typically<00:32:10.980> in<00:32:11.159> the<00:32:11.279> form<00:32:11.460> of<00:32:11.640> a 00:32:11.810 --> 00:32:11.820 align:start position:0% on a server typically in the form of a 00:32:11.820 --> 00:32:14.330 align:start position:0% on a server typically in the form of a web<00:32:12.000> page<00:32:12.360> and<00:32:13.020> in<00:32:13.200> order<00:32:13.380> to<00:32:13.620> access<00:32:13.799> the<00:32:14.100> data 00:32:14.330 --> 00:32:14.340 align:start position:0% web page and in order to access the data 00:32:14.340 --> 00:32:16.549 align:start position:0% web page and in order to access the data data<00:32:14.820> on<00:32:15.000> the<00:32:15.179> internet<00:32:15.299> you're<00:32:15.840> going<00:32:16.140> to 00:32:16.549 --> 00:32:16.559 align:start position:0% data on the internet you're going to 00:32:16.559 --> 00:32:19.010 align:start position:0% data on the internet you're going to have<00:32:17.460> several<00:32:17.880> different<00:32:18.059> considerations 00:32:19.010 --> 00:32:19.020 align:start position:0% have several different considerations 00:32:19.020 --> 00:32:21.169 align:start position:0% have several different considerations that<00:32:19.440> are<00:32:19.559> going<00:32:19.620> to<00:32:19.740> be<00:32:19.860> made<00:32:20.159> first<00:32:20.940> of<00:32:21.059> all 00:32:21.169 --> 00:32:21.179 align:start position:0% that are going to be made first of all 00:32:21.179 --> 00:32:24.230 align:start position:0% that are going to be made first of all you<00:32:21.779> need<00:32:21.899> to<00:32:22.140> have<00:32:22.380> a<00:32:22.860> web<00:32:23.279> browser<00:32:23.760> of<00:32:24.000> some 00:32:24.230 --> 00:32:24.240 align:start position:0% you need to have a web browser of some 00:32:24.240 --> 00:32:26.029 align:start position:0% you need to have a web browser of some sort 00:32:26.029 --> 00:32:26.039 align:start position:0% sort 00:32:26.039 --> 00:32:27.710 align:start position:0% sort or<00:32:26.520> you're<00:32:26.700> gonna<00:32:26.820> need<00:32:26.940> to<00:32:27.059> utilize<00:32:27.480> a 00:32:27.710 --> 00:32:27.720 align:start position:0% or you're gonna need to utilize a 00:32:27.720 --> 00:32:29.510 align:start position:0% or you're gonna need to utilize a certain<00:32:27.840> generic<00:32:28.380> protocol<00:32:28.799> and<00:32:29.340> have 00:32:29.510 --> 00:32:29.520 align:start position:0% certain generic protocol and have 00:32:29.520 --> 00:32:31.730 align:start position:0% certain generic protocol and have something<00:32:29.820> like<00:32:30.299> uh<00:32:31.020> so<00:32:31.200> if<00:32:31.320> we're<00:32:31.440> talking<00:32:31.559> a 00:32:31.730 --> 00:32:31.740 align:start position:0% something like uh so if we're talking a 00:32:31.740 --> 00:32:33.049 align:start position:0% something like uh so if we're talking a web<00:32:31.919> browser<00:32:32.279> we're<00:32:32.399> gonna<00:32:32.580> need<00:32:32.640> to<00:32:32.760> use<00:32:32.880> a 00:32:33.049 --> 00:32:33.059 align:start position:0% web browser we're gonna need to use a 00:32:33.059 --> 00:32:34.789 align:start position:0% web browser we're gonna need to use a safari<00:32:33.419> Internet<00:32:33.539> Explorer<00:32:34.140> Google<00:32:34.320> Chrome 00:32:34.789 --> 00:32:34.799 align:start position:0% safari Internet Explorer Google Chrome 00:32:34.799 --> 00:32:36.470 align:start position:0% safari Internet Explorer Google Chrome Firefox 00:32:36.470 --> 00:32:36.480 align:start position:0% Firefox 00:32:36.480 --> 00:32:40.250 align:start position:0% Firefox Etc<00:32:36.600> but<00:32:37.140> they're<00:32:37.440> all<00:32:37.740> using<00:32:38.600> HTTP<00:32:39.600> which<00:32:40.080> is 00:32:40.250 --> 00:32:40.260 align:start position:0% Etc but they're all using HTTP which is 00:32:40.260 --> 00:32:42.950 align:start position:0% Etc but they're all using HTTP which is a<00:32:40.500> specific<00:32:40.799> protocol<00:32:41.700> and<00:32:42.360> it<00:32:42.480> has<00:32:42.600> a<00:32:42.779> certain 00:32:42.950 --> 00:32:42.960 align:start position:0% a specific protocol and it has a certain 00:32:42.960 --> 00:32:44.389 align:start position:0% a specific protocol and it has a certain port 00:32:44.389 --> 00:32:44.399 align:start position:0% port 00:32:44.399 --> 00:32:46.610 align:start position:0% port which<00:32:45.000> by<00:32:45.179> the<00:32:45.299> way<00:32:45.360> is<00:32:45.480> 80.<00:32:46.080> we'll<00:32:46.260> talk<00:32:46.440> more 00:32:46.610 --> 00:32:46.620 align:start position:0% which by the way is 80. we'll talk more 00:32:46.620 --> 00:32:48.830 align:start position:0% which by the way is 80. we'll talk more about<00:32:46.740> those<00:32:47.039> later<00:32:47.279> in<00:32:47.880> order<00:32:48.059> to<00:32:48.480> allow 00:32:48.830 --> 00:32:48.840 align:start position:0% about those later in order to allow 00:32:48.840 --> 00:32:51.110 align:start position:0% about those later in order to allow communication<00:32:49.380> to<00:32:49.679> occur<00:32:50.039> and<00:32:50.580> this<00:32:50.760> might<00:32:51.000> be 00:32:51.110 --> 00:32:51.120 align:start position:0% communication to occur and this might be 00:32:51.120 --> 00:32:52.909 align:start position:0% communication to occur and this might be different<00:32:51.240> from<00:32:51.539> say<00:32:51.840> another<00:32:52.320> form<00:32:52.679> of 00:32:52.909 --> 00:32:52.919 align:start position:0% different from say another form of 00:32:52.919 --> 00:32:55.850 align:start position:0% different from say another form of communication<00:32:53.399> such<00:32:53.760> as<00:32:53.880> FTP<00:32:54.600> or<00:32:55.200> remoting<00:32:55.740> in 00:32:55.850 --> 00:32:55.860 align:start position:0% communication such as FTP or remoting in 00:32:55.860 --> 00:32:58.490 align:start position:0% communication such as FTP or remoting in and<00:32:56.100> so<00:32:56.340> on<00:32:56.520> and<00:32:57.120> secondly<00:32:57.480> all<00:32:57.779> devices<00:32:58.020> that 00:32:58.490 --> 00:32:58.500 align:start position:0% and so on and secondly all devices that 00:32:58.500 --> 00:33:00.889 align:start position:0% and so on and secondly all devices that want<00:32:58.679> to<00:32:58.860> connect<00:32:59.039> to<00:32:59.279> the<00:32:59.520> internet<00:32:59.720> must<00:33:00.720> be 00:33:00.889 --> 00:33:00.899 align:start position:0% want to connect to the internet must be 00:33:00.899 --> 00:33:04.430 align:start position:0% want to connect to the internet must be assigned<00:33:01.380> we<00:33:01.740> would<00:33:01.919> call<00:33:02.159> an<00:33:02.520> IP<00:33:02.820> address<00:33:03.440> all 00:33:04.430 --> 00:33:04.440 align:start position:0% assigned we would call an IP address all 00:33:04.440 --> 00:33:06.590 align:start position:0% assigned we would call an IP address all things<00:33:04.620> on<00:33:04.980> the<00:33:05.100> internet<00:33:05.279> due<00:33:06.059> to<00:33:06.179> the<00:33:06.299> way<00:33:06.419> it 00:33:06.590 --> 00:33:06.600 align:start position:0% things on the internet due to the way it 00:33:06.600 --> 00:33:09.409 align:start position:0% things on the internet due to the way it works<00:33:06.899> are<00:33:07.200> governed<00:33:07.679> by<00:33:07.980> this<00:33:08.279> IP<00:33:08.760> or<00:33:09.179> the 00:33:09.409 --> 00:33:09.419 align:start position:0% works are governed by this IP or the 00:33:09.419 --> 00:33:11.690 align:start position:0% works are governed by this IP or the Internet<00:33:09.659> Protocol<00:33:10.440> we're<00:33:11.100> going<00:33:11.279> to<00:33:11.340> revisit 00:33:11.690 --> 00:33:11.700 align:start position:0% Internet Protocol we're going to revisit 00:33:11.700 --> 00:33:16.210 align:start position:0% Internet Protocol we're going to revisit this<00:33:11.880> in<00:33:12.000> a<00:33:12.179> future<00:33:12.299> module<00:33:12.840> but<00:33:13.380> IP 00:33:16.210 --> 00:33:16.220 align:start position:0% this in a future module but IP 00:33:16.220 --> 00:33:19.370 align:start position:0% this in a future module but IP allows<00:33:17.220> all<00:33:17.580> of<00:33:17.700> this<00:33:18.059> to<00:33:18.360> happen<00:33:18.600> if<00:33:19.260> it 00:33:19.370 --> 00:33:19.380 align:start position:0% allows all of this to happen if it 00:33:19.380 --> 00:33:21.409 align:start position:0% allows all of this to happen if it wasn't<00:33:19.559> 4ip<00:33:20.100> we<00:33:20.580> wouldn't<00:33:20.760> have<00:33:21.059> an<00:33:21.299> internet 00:33:21.409 --> 00:33:21.419 align:start position:0% wasn't 4ip we wouldn't have an internet 00:33:21.419 --> 00:33:23.690 align:start position:0% wasn't 4ip we wouldn't have an internet at<00:33:21.779> least<00:33:21.899> in<00:33:22.080> the<00:33:22.200> way<00:33:22.320> we<00:33:22.500> know<00:33:22.620> it<00:33:22.860> so<00:33:23.519> again 00:33:23.690 --> 00:33:23.700 align:start position:0% at least in the way we know it so again 00:33:23.700 --> 00:33:27.710 align:start position:0% at least in the way we know it so again the<00:33:24.480> internet<00:33:24.659> is<00:33:25.260> this<00:33:25.679> largest<00:33:26.399> global<00:33:27.240> wide 00:33:27.710 --> 00:33:27.720 align:start position:0% the internet is this largest global wide 00:33:27.720 --> 00:33:29.990 align:start position:0% the internet is this largest global wide area<00:33:27.960> network<00:33:28.380> that<00:33:28.980> we<00:33:29.100> have<00:33:29.279> in<00:33:29.700> the<00:33:29.820> world 00:33:29.990 --> 00:33:30.000 align:start position:0% area network that we have in the world 00:33:30.000 --> 00:33:32.509 align:start position:0% area network that we have in the world and<00:33:30.600> it's<00:33:30.720> for<00:33:31.019> use<00:33:31.200> it's<00:33:31.500> public<00:33:31.860> and 00:33:32.509 --> 00:33:32.519 align:start position:0% and it's for use it's public and 00:33:32.519 --> 00:33:34.549 align:start position:0% and it's for use it's public and everyone<00:33:33.000> can<00:33:33.299> use<00:33:33.539> it<00:33:33.720> if<00:33:34.019> they<00:33:34.200> you<00:33:34.440> know 00:33:34.549 --> 00:33:34.559 align:start position:0% everyone can use it if they you know 00:33:34.559 --> 00:33:36.350 align:start position:0% everyone can use it if they you know have<00:33:34.860> a<00:33:35.039> provider<00:33:35.580> that<00:33:35.760> gives<00:33:35.940> them<00:33:36.120> access 00:33:36.350 --> 00:33:36.360 align:start position:0% have a provider that gives them access 00:33:36.360 --> 00:33:39.049 align:start position:0% have a provider that gives them access now<00:33:37.080> this<00:33:37.260> is<00:33:37.320> different<00:33:37.500> from<00:33:37.860> an<00:33:38.100> intranet 00:33:39.049 --> 00:33:39.059 align:start position:0% now this is different from an intranet 00:33:39.059 --> 00:33:42.409 align:start position:0% now this is different from an intranet an<00:33:39.720> intranet<00:33:40.500> is<00:33:40.919> a<00:33:41.100> company's<00:33:41.519> private 00:33:42.409 --> 00:33:42.419 align:start position:0% an intranet is a company's private 00:33:42.419 --> 00:33:45.049 align:start position:0% an intranet is a company's private version<00:33:42.720> of<00:33:43.320> the<00:33:43.500> Internet<00:33:43.640> it's<00:33:44.640> commonly 00:33:45.049 --> 00:33:45.059 align:start position:0% version of the Internet it's commonly 00:33:45.059 --> 00:33:47.149 align:start position:0% version of the Internet it's commonly connected<00:33:45.600> to<00:33:45.899> the<00:33:46.080> internet<00:33:46.200> so<00:33:46.799> that<00:33:46.980> people 00:33:47.149 --> 00:33:47.159 align:start position:0% connected to the internet so that people 00:33:47.159 --> 00:33:49.669 align:start position:0% connected to the internet so that people can<00:33:47.700> uh<00:33:48.240> connect<00:33:48.539> even<00:33:49.019> if<00:33:49.260> they're<00:33:49.440> not 00:33:49.669 --> 00:33:49.679 align:start position:0% can uh connect even if they're not 00:33:49.679 --> 00:33:52.430 align:start position:0% can uh connect even if they're not locally<00:33:50.340> at<00:33:50.640> the<00:33:51.059> same<00:33:51.240> place<00:33:51.419> physically<00:33:51.899> but 00:33:52.430 --> 00:33:52.440 align:start position:0% locally at the same place physically but 00:33:52.440 --> 00:33:54.409 align:start position:0% locally at the same place physically but the<00:33:52.679> purpose<00:33:53.039> of<00:33:53.399> an<00:33:53.519> intranet<00:33:53.940> is<00:33:54.059> to<00:33:54.240> keep 00:33:54.409 --> 00:33:54.419 align:start position:0% the purpose of an intranet is to keep 00:33:54.419 --> 00:33:56.570 align:start position:0% the purpose of an intranet is to keep your<00:33:54.720> network<00:33:54.960> or<00:33:55.620> portions<00:33:56.039> of<00:33:56.220> your<00:33:56.399> network 00:33:56.570 --> 00:33:56.580 align:start position:0% your network or portions of your network 00:33:56.580 --> 00:33:59.450 align:start position:0% your network or portions of your network segregated<00:33:57.360> from<00:33:58.140> the<00:33:58.320> unsecure<00:33:58.919> and 00:33:59.450 --> 00:33:59.460 align:start position:0% segregated from the unsecure and 00:33:59.460 --> 00:34:02.090 align:start position:0% segregated from the unsecure and possibly<00:34:00.000> even<00:34:00.299> dangerous<00:34:00.960> internet<00:34:01.260> so<00:34:01.919> a 00:34:02.090 --> 00:34:02.100 align:start position:0% possibly even dangerous internet so a 00:34:02.100 --> 00:34:04.070 align:start position:0% possibly even dangerous internet so a company<00:34:02.220> might<00:34:02.640> use<00:34:03.000> an<00:34:03.299> intranet<00:34:03.779> for 00:34:04.070 --> 00:34:04.080 align:start position:0% company might use an intranet for 00:34:04.080 --> 00:34:07.850 align:start position:0% company might use an intranet for security<00:34:04.380> purposes<00:34:05.240> or<00:34:06.240> for<00:34:06.899> confidentiality 00:34:07.850 --> 00:34:07.860 align:start position:0% security purposes or for confidentiality 00:34:07.860 --> 00:34:09.710 align:start position:0% security purposes or for confidentiality if<00:34:08.159> they<00:34:08.339> have<00:34:08.520> certain<00:34:08.760> files<00:34:09.240> and<00:34:09.359> folders 00:34:09.710 --> 00:34:09.720 align:start position:0% if they have certain files and folders 00:34:09.720 --> 00:34:11.629 align:start position:0% if they have certain files and folders they<00:34:09.899> want<00:34:10.020> to<00:34:10.139> post<00:34:10.320> up<00:34:10.500> and<00:34:11.040> the<00:34:11.159> intranet 00:34:11.629 --> 00:34:11.639 align:start position:0% they want to post up and the intranet 00:34:11.639 --> 00:34:14.510 align:start position:0% they want to post up and the intranet uses<00:34:12.119> the<00:34:12.480> same<00:34:12.720> services<00:34:13.020> and<00:34:13.679> protocols<00:34:14.280> as 00:34:14.510 --> 00:34:14.520 align:start position:0% uses the same services and protocols as 00:34:14.520 --> 00:34:16.490 align:start position:0% uses the same services and protocols as the<00:34:14.760> internet<00:34:14.940> so<00:34:15.419> the<00:34:15.480> reason<00:34:15.599> it<00:34:15.780> shares 00:34:16.490 --> 00:34:16.500 align:start position:0% the internet so the reason it shares 00:34:16.500 --> 00:34:19.849 align:start position:0% the internet so the reason it shares this<00:34:16.679> name<00:34:16.919> is<00:34:17.580> intra<00:34:18.359> enter<00:34:19.080> to<00:34:19.740> the 00:34:19.849 --> 00:34:19.859 align:start position:0% this name is intra enter to the 00:34:19.859 --> 00:34:22.070 align:start position:0% this name is intra enter to the organization<00:34:20.520> but<00:34:21.179> it<00:34:21.359> shares<00:34:21.659> the<00:34:21.780> same<00:34:21.899> name 00:34:22.070 --> 00:34:22.080 align:start position:0% organization but it shares the same name 00:34:22.080 --> 00:34:23.930 align:start position:0% organization but it shares the same name because<00:34:22.320> it's<00:34:22.560> using<00:34:22.980> all<00:34:23.339> of<00:34:23.460> the<00:34:23.760> same 00:34:23.930 --> 00:34:23.940 align:start position:0% because it's using all of the same 00:34:23.940 --> 00:34:27.290 align:start position:0% because it's using all of the same services<00:34:24.540> in<00:34:25.020> other<00:34:25.139> words<00:34:25.260> IP<00:34:26.060> HTTP<00:34:27.060> you 00:34:27.290 --> 00:34:27.300 align:start position:0% services in other words IP HTTP you 00:34:27.300 --> 00:34:29.570 align:start position:0% services in other words IP HTTP you still<00:34:27.480> use<00:34:27.659> a<00:34:27.899> browser<00:34:28.320> so<00:34:28.619> on<00:34:28.859> and<00:34:29.040> so<00:34:29.220> forth 00:34:29.570 --> 00:34:29.580 align:start position:0% still use a browser so on and so forth 00:34:29.580 --> 00:34:32.450 align:start position:0% still use a browser so on and so forth so<00:34:30.119> it's<00:34:30.359> still<00:34:30.599> accessed<00:34:31.260> the<00:34:31.740> same<00:34:31.919> way<00:34:32.159> you 00:34:32.450 --> 00:34:32.460 align:start position:0% so it's still accessed the same way you 00:34:32.460 --> 00:34:34.430 align:start position:0% so it's still accessed the same way you would<00:34:32.580> the<00:34:32.940> internet<00:34:33.119> through<00:34:33.659> a<00:34:33.899> browser<00:34:34.260> and 00:34:34.430 --> 00:34:34.440 align:start position:0% would the internet through a browser and 00:34:34.440 --> 00:34:37.550 align:start position:0% would the internet through a browser and a<00:34:34.619> web<00:34:34.740> page<00:34:34.980> on<00:34:35.399> the<00:34:35.520> world<00:34:35.580> wide<00:34:35.940> web<00:34:36.200> now<00:34:37.200> all 00:34:37.550 --> 00:34:37.560 align:start position:0% a web page on the world wide web now all 00:34:37.560 --> 00:34:40.070 align:start position:0% a web page on the world wide web now all of<00:34:37.679> this<00:34:37.859> is<00:34:38.040> different<00:34:38.220> from<00:34:38.639> an<00:34:39.000> Extranet<00:34:39.659> as 00:34:40.070 --> 00:34:40.080 align:start position:0% of this is different from an Extranet as 00:34:40.080 --> 00:34:41.829 align:start position:0% of this is different from an Extranet as the<00:34:40.320> name<00:34:40.500> implies 00:34:41.829 --> 00:34:41.839 align:start position:0% the name implies 00:34:41.839 --> 00:34:44.450 align:start position:0% the name implies with<00:34:42.839> an<00:34:42.960> intranet<00:34:43.500> your<00:34:43.919> network<00:34:44.099> is 00:34:44.450 --> 00:34:44.460 align:start position:0% with an intranet your network is 00:34:44.460 --> 00:34:46.250 align:start position:0% with an intranet your network is completely<00:34:44.820> secure<00:34:45.240> from<00:34:45.720> the<00:34:46.139> internet 00:34:46.250 --> 00:34:46.260 align:start position:0% completely secure from the internet 00:34:46.260 --> 00:34:48.829 align:start position:0% completely secure from the internet right<00:34:46.679> you<00:34:46.980> control<00:34:47.339> who<00:34:47.820> has<00:34:48.000> access<00:34:48.300> to<00:34:48.659> your 00:34:48.829 --> 00:34:48.839 align:start position:0% right you control who has access to your 00:34:48.839 --> 00:34:50.570 align:start position:0% right you control who has access to your network<00:34:48.960> in<00:34:49.379> every<00:34:49.560> facet 00:34:50.570 --> 00:34:50.580 align:start position:0% network in every facet 00:34:50.580 --> 00:34:54.470 align:start position:0% network in every facet but<00:34:51.540> what<00:34:52.080> if<00:34:52.379> your<00:34:52.980> company<00:34:53.480> organization 00:34:54.470 --> 00:34:54.480 align:start position:0% but what if your company organization 00:34:54.480 --> 00:34:57.050 align:start position:0% but what if your company organization needs<00:34:55.379> to<00:34:55.500> allow<00:34:55.800> certain<00:34:56.099> individuals<00:34:56.760> to 00:34:57.050 --> 00:34:57.060 align:start position:0% needs to allow certain individuals to 00:34:57.060 --> 00:34:58.970 align:start position:0% needs to allow certain individuals to have<00:34:57.180> access<00:34:57.480> to<00:34:57.839> your<00:34:58.020> network<00:34:58.200> but<00:34:58.859> you 00:34:58.970 --> 00:34:58.980 align:start position:0% have access to your network but you 00:34:58.980 --> 00:35:01.250 align:start position:0% have access to your network but you don't<00:34:59.099> want<00:34:59.220> them<00:34:59.339> to<00:34:59.520> have<00:34:59.700> access<00:34:59.940> to<00:35:00.420> all<00:35:01.080> of 00:35:01.250 --> 00:35:01.260 align:start position:0% don't want them to have access to all of 00:35:01.260 --> 00:35:03.410 align:start position:0% don't want them to have access to all of your<00:35:01.380> network<00:35:02.040> in<00:35:02.640> this<00:35:02.700> case<00:35:02.880> we're<00:35:03.180> going<00:35:03.359> to 00:35:03.410 --> 00:35:03.420 align:start position:0% your network in this case we're going to 00:35:03.420 --> 00:35:05.510 align:start position:0% your network in this case we're going to use<00:35:03.540> something<00:35:03.780> called<00:35:04.080> an<00:35:04.380> Extranet<00:35:05.040> it 00:35:05.510 --> 00:35:05.520 align:start position:0% use something called an Extranet it 00:35:05.520 --> 00:35:08.690 align:start position:0% use something called an Extranet it gives<00:35:05.700> you<00:35:05.940> the<00:35:06.180> ability<00:35:06.420> to<00:35:06.900> Grant<00:35:07.500> uh<00:35:08.460> access 00:35:08.690 --> 00:35:08.700 align:start position:0% gives you the ability to Grant uh access 00:35:08.700 --> 00:35:11.750 align:start position:0% gives you the ability to Grant uh access to<00:35:09.180> specific<00:35:09.599> portions<00:35:10.320> of<00:35:10.740> your<00:35:10.920> network<00:35:11.160> and 00:35:11.750 --> 00:35:11.760 align:start position:0% to specific portions of your network and 00:35:11.760 --> 00:35:14.870 align:start position:0% to specific portions of your network and your<00:35:12.060> Extranet<00:35:12.720> so<00:35:13.260> you<00:35:13.440> can<00:35:13.560> give<00:35:13.800> access<00:35:14.460> to 00:35:14.870 --> 00:35:14.880 align:start position:0% your Extranet so you can give access to 00:35:14.880 --> 00:35:16.910 align:start position:0% your Extranet so you can give access to specific<00:35:15.180> people<00:35:15.540> typically<00:35:16.380> vendors 00:35:16.910 --> 00:35:16.920 align:start position:0% specific people typically vendors 00:35:16.920 --> 00:35:20.390 align:start position:0% specific people typically vendors suppliers<00:35:18.140> individuals<00:35:19.140> that<00:35:19.680> might<00:35:20.160> need 00:35:20.390 --> 00:35:20.400 align:start position:0% suppliers individuals that might need 00:35:20.400 --> 00:35:23.210 align:start position:0% suppliers individuals that might need minimal<00:35:20.880> or<00:35:21.119> temporary<00:35:21.660> access<00:35:22.020> at<00:35:22.859> the<00:35:23.040> same 00:35:23.210 --> 00:35:23.220 align:start position:0% minimal or temporary access at the same 00:35:23.220 --> 00:35:25.670 align:start position:0% minimal or temporary access at the same time<00:35:23.460> your<00:35:23.880> Extranet<00:35:24.480> is<00:35:24.780> restricting<00:35:25.380> them 00:35:25.670 --> 00:35:25.680 align:start position:0% time your Extranet is restricting them 00:35:25.680 --> 00:35:27.470 align:start position:0% time your Extranet is restricting them from<00:35:25.980> having<00:35:26.220> full<00:35:26.460> access<00:35:26.700> to<00:35:27.000> the<00:35:27.180> rest<00:35:27.300> of 00:35:27.470 --> 00:35:27.480 align:start position:0% from having full access to the rest of 00:35:27.480 --> 00:35:31.490 align:start position:0% from having full access to the rest of your<00:35:27.660> network<00:35:27.839> or<00:35:28.619> your<00:35:28.980> intranet<00:35:29.880> so<00:35:30.720> it's 00:35:31.490 --> 00:35:31.500 align:start position:0% your network or your intranet so it's 00:35:31.500 --> 00:35:35.329 align:start position:0% your network or your intranet so it's really<00:35:31.740> an<00:35:32.160> extension<00:35:32.820> of<00:35:33.359> your<00:35:33.599> intranet<00:35:34.339> but 00:35:35.329 --> 00:35:35.339 align:start position:0% really an extension of your intranet but 00:35:35.339 --> 00:35:37.849 align:start position:0% really an extension of your intranet but it's<00:35:35.520> the<00:35:35.760> part<00:35:35.940> that<00:35:36.300> is<00:35:36.480> exterior<00:35:37.260> look<00:35:37.680> at 00:35:37.849 --> 00:35:37.859 align:start position:0% it's the part that is exterior look at 00:35:37.859 --> 00:35:39.589 align:start position:0% it's the part that is exterior look at that<00:35:38.099> extra 00:35:39.589 --> 00:35:39.599 align:start position:0% that extra 00:35:39.599 --> 00:35:41.510 align:start position:0% that extra to<00:35:40.140> your<00:35:40.320> organization<00:35:40.800> so<00:35:41.040> again<00:35:41.220> the 00:35:41.510 --> 00:35:41.520 align:start position:0% to your organization so again the 00:35:41.520 --> 00:35:42.530 align:start position:0% to your organization so again the internet 00:35:42.530 --> 00:35:42.540 align:start position:0% internet 00:35:42.540 --> 00:35:45.770 align:start position:0% internet is<00:35:43.079> is<00:35:43.079> a<00:35:43.619> you<00:35:43.800> know<00:35:43.940> using<00:35:44.940> a<00:35:45.180> certain<00:35:45.359> degree 00:35:45.770 --> 00:35:45.780 align:start position:0% is is a you know using a certain degree 00:35:45.780 --> 00:35:49.490 align:start position:0% is is a you know using a certain degree of<00:35:45.900> protocols<00:35:46.619> and<00:35:47.579> uh<00:35:48.359> technologies<00:35:49.140> that 00:35:49.490 --> 00:35:49.500 align:start position:0% of protocols and uh technologies that 00:35:49.500 --> 00:35:50.870 align:start position:0% of protocols and uh technologies that allows<00:35:49.800> anyone<00:35:50.160> in<00:35:50.339> the<00:35:50.400> world<00:35:50.520> to<00:35:50.760> access 00:35:50.870 --> 00:35:50.880 align:start position:0% allows anyone in the world to access 00:35:50.880 --> 00:35:54.349 align:start position:0% allows anyone in the world to access information<00:35:51.320> the<00:35:52.320> intranet<00:35:53.220> is<00:35:53.700> sort<00:35:53.880> of<00:35:54.000> a 00:35:54.349 --> 00:35:54.359 align:start position:0% information the intranet is sort of a 00:35:54.359 --> 00:35:56.810 align:start position:0% information the intranet is sort of a private<00:35:54.780> internet<00:35:55.160> for<00:35:56.160> your<00:35:56.280> organization 00:35:56.810 --> 00:35:56.820 align:start position:0% private internet for your organization 00:35:56.820 --> 00:35:59.329 align:start position:0% private internet for your organization and<00:35:57.240> the<00:35:57.480> Extranet<00:35:58.020> is<00:35:58.500> the<00:35:58.680> part<00:35:58.859> of<00:35:59.040> that 00:35:59.329 --> 00:35:59.339 align:start position:0% and the Extranet is the part of that 00:35:59.339 --> 00:36:01.670 align:start position:0% and the Extranet is the part of that intranet<00:36:00.119> that<00:36:00.599> you're<00:36:00.720> going<00:36:00.900> to<00:36:01.079> let<00:36:01.380> other 00:36:01.670 --> 00:36:01.680 align:start position:0% intranet that you're going to let other 00:36:01.680 --> 00:36:03.829 align:start position:0% intranet that you're going to let other people<00:36:01.980> from<00:36:02.579> outside<00:36:02.880> of<00:36:03.180> your<00:36:03.300> organization 00:36:03.829 --> 00:36:03.839 align:start position:0% people from outside of your organization 00:36:03.839 --> 00:36:08.450 align:start position:0% people from outside of your organization have<00:36:04.380> access<00:36:04.680> to 00:36:08.450 --> 00:36:08.460 align:start position:0% 00:36:08.460 --> 00:36:11.450 align:start position:0% now<00:36:09.300> I<00:36:09.900> just<00:36:09.960> want<00:36:10.140> to<00:36:10.260> Define<00:36:10.380> what<00:36:10.920> a<00:36:11.099> segment 00:36:11.450 --> 00:36:11.460 align:start position:0% now I just want to Define what a segment 00:36:11.460 --> 00:36:14.089 align:start position:0% now I just want to Define what a segment is<00:36:11.820> since<00:36:12.599> we<00:36:12.839> might<00:36:12.960> see<00:36:13.140> this<00:36:13.440> term<00:36:13.560> come<00:36:13.920> up 00:36:14.089 --> 00:36:14.099 align:start position:0% is since we might see this term come up 00:36:14.099 --> 00:36:17.030 align:start position:0% is since we might see this term come up a<00:36:14.579> bit<00:36:14.880> in<00:36:15.119> the<00:36:15.240> future<00:36:15.359> a<00:36:16.079> segment<00:36:16.380> is<00:36:16.680> a 00:36:17.030 --> 00:36:17.040 align:start position:0% a bit in the future a segment is a 00:36:17.040 --> 00:36:19.490 align:start position:0% a bit in the future a segment is a portion<00:36:17.460> of<00:36:17.700> a<00:36:17.880> Network<00:36:18.060> that<00:36:18.900> has<00:36:19.020> linked 00:36:19.490 --> 00:36:19.500 align:start position:0% portion of a Network that has linked 00:36:19.500 --> 00:36:22.069 align:start position:0% portion of a Network that has linked devices<00:36:19.920> and<00:36:20.640> that<00:36:20.880> are<00:36:21.000> separated<00:36:21.480> by<00:36:21.839> a 00:36:22.069 --> 00:36:22.079 align:start position:0% devices and that are separated by a 00:36:22.079 --> 00:36:24.829 align:start position:0% devices and that are separated by a connectivity<00:36:22.619> device<00:36:22.859> such<00:36:23.220> as<00:36:23.339> a<00:36:23.579> switch<00:36:23.839> or 00:36:24.829 --> 00:36:24.839 align:start position:0% connectivity device such as a switch or 00:36:24.839 --> 00:36:26.089 align:start position:0% connectivity device such as a switch or a<00:36:24.960> router 00:36:26.089 --> 00:36:26.099 align:start position:0% a router 00:36:26.099 --> 00:36:27.890 align:start position:0% a router all<00:36:26.640> right<00:36:26.820> so<00:36:27.060> we<00:36:27.300> haven't<00:36:27.420> talked<00:36:27.780> about 00:36:27.890 --> 00:36:27.900 align:start position:0% all right so we haven't talked about 00:36:27.900 --> 00:36:29.870 align:start position:0% all right so we haven't talked about switches<00:36:28.320> and<00:36:28.500> routers<00:36:28.859> yet<00:36:29.040> but<00:36:29.520> we're<00:36:29.640> going 00:36:29.870 --> 00:36:29.880 align:start position:0% switches and routers yet but we're going 00:36:29.880 --> 00:36:32.270 align:start position:0% switches and routers yet but we're going to<00:36:30.060> and<00:36:30.300> so<00:36:30.480> what<00:36:30.599> I<00:36:30.720> mean<00:36:30.839> is<00:36:31.020> I<00:36:31.260> might<00:36:31.380> have<00:36:31.740> a 00:36:32.270 --> 00:36:32.280 align:start position:0% to and so what I mean is I might have a 00:36:32.280 --> 00:36:34.849 align:start position:0% to and so what I mean is I might have a lan 00:36:34.849 --> 00:36:34.859 align:start position:0% 00:36:34.859 --> 00:36:38.210 align:start position:0% okay<00:36:35.339> and 00:36:38.210 --> 00:36:38.220 align:start position:0% okay and 00:36:38.220 --> 00:36:41.089 align:start position:0% okay and let's<00:36:38.820> say<00:36:39.060> that<00:36:39.480> for<00:36:39.900> simplicity's<00:36:40.680> sake<00:36:40.800> My 00:36:41.089 --> 00:36:41.099 align:start position:0% let's say that for simplicity's sake My 00:36:41.099 --> 00:36:44.030 align:start position:0% let's say that for simplicity's sake My Lan<00:36:41.400> is<00:36:41.640> consisting<00:36:42.180> of<00:36:42.420> four<00:36:42.660> computers<00:36:43.260> all 00:36:44.030 --> 00:36:44.040 align:start position:0% Lan is consisting of four computers all 00:36:44.040 --> 00:36:48.349 align:start position:0% Lan is consisting of four computers all connected<00:36:44.460> through<00:36:44.760> a<00:36:45.180> central<00:36:45.359> device 00:36:48.349 --> 00:36:48.359 align:start position:0% 00:36:48.359 --> 00:36:52.730 align:start position:0% which<00:36:48.780> we're<00:36:48.960> going<00:36:49.140> to<00:36:49.260> call<00:36:49.500> a<00:36:49.920> switch 00:36:52.730 --> 00:36:52.740 align:start position:0% 00:36:52.740 --> 00:36:54.170 align:start position:0% now<00:36:53.099> remember<00:36:53.220> if<00:36:53.460> they<00:36:53.640> weren't<00:36:53.760> connecting 00:36:54.170 --> 00:36:54.180 align:start position:0% now remember if they weren't connecting 00:36:54.180 --> 00:36:55.550 align:start position:0% now remember if they weren't connecting through<00:36:54.359> that<00:36:54.540> Central<00:36:54.780> device<00:36:55.079> this<00:36:55.440> would 00:36:55.550 --> 00:36:55.560 align:start position:0% through that Central device this would 00:36:55.560 --> 00:36:57.829 align:start position:0% through that Central device this would be<00:36:55.680> called<00:36:55.859> a<00:36:56.220> pan<00:36:56.820> a<00:36:57.180> personal<00:36:57.300> area<00:36:57.660> network 00:36:57.829 --> 00:36:57.839 align:start position:0% be called a pan a personal area network 00:36:57.839 --> 00:36:59.450 align:start position:0% be called a pan a personal area network but<00:36:58.079> this<00:36:58.260> is<00:36:58.320> a<00:36:58.440> lan<00:36:58.680> has<00:36:58.859> a<00:36:59.040> central<00:36:59.160> device 00:36:59.450 --> 00:36:59.460 align:start position:0% but this is a lan has a central device 00:36:59.460 --> 00:37:02.510 align:start position:0% but this is a lan has a central device and<00:37:00.240> let's<00:37:00.359> say<00:37:00.599> this<00:37:00.960> Central<00:37:01.200> device 00:37:02.510 --> 00:37:02.520 align:start position:0% and let's say this Central device 00:37:02.520 --> 00:37:05.270 align:start position:0% and let's say this Central device and<00:37:03.180> this<00:37:03.540> I'm<00:37:03.780> really<00:37:04.020> simplifying<00:37:04.680> it<00:37:04.859> but 00:37:05.270 --> 00:37:05.280 align:start position:0% and this I'm really simplifying it but 00:37:05.280 --> 00:37:09.290 align:start position:0% and this I'm really simplifying it but let's<00:37:05.460> say<00:37:05.640> it<00:37:06.000> connects<00:37:06.900> to<00:37:07.440> another<00:37:07.680> switch 00:37:09.290 --> 00:37:09.300 align:start position:0% let's say it connects to another switch 00:37:09.300 --> 00:37:11.810 align:start position:0% let's say it connects to another switch and<00:37:09.839> that<00:37:10.020> other<00:37:10.260> switch 00:37:11.810 --> 00:37:11.820 align:start position:0% and that other switch 00:37:11.820 --> 00:37:15.109 align:start position:0% and that other switch has<00:37:12.480> four<00:37:12.900> computers<00:37:13.380> connected<00:37:13.800> to<00:37:13.980> it<00:37:14.099> now<00:37:14.820> I 00:37:15.109 --> 00:37:15.119 align:start position:0% has four computers connected to it now I 00:37:15.119 --> 00:37:18.190 align:start position:0% has four computers connected to it now I have<00:37:15.359> different<00:37:15.960> segments<00:37:16.920> of<00:37:17.400> my<00:37:17.640> network 00:37:18.190 --> 00:37:18.200 align:start position:0% have different segments of my network 00:37:18.200 --> 00:37:20.930 align:start position:0% have different segments of my network that<00:37:19.200> uh<00:37:19.500> I<00:37:19.800> can<00:37:19.920> join<00:37:20.280> together<00:37:20.400> in<00:37:20.760> certain 00:37:20.930 --> 00:37:20.940 align:start position:0% that uh I can join together in certain 00:37:20.940 --> 00:37:23.030 align:start position:0% that uh I can join together in certain information<00:37:21.180> but<00:37:21.599> I<00:37:21.720> can<00:37:21.839> also<00:37:22.140> exclude<00:37:22.619> them 00:37:23.030 --> 00:37:23.040 align:start position:0% information but I can also exclude them 00:37:23.040 --> 00:37:25.370 align:start position:0% information but I can also exclude them from<00:37:23.339> certain<00:37:23.520> information<00:37:23.900> in<00:37:24.900> order<00:37:25.079> to 00:37:25.370 --> 00:37:25.380 align:start position:0% from certain information in order to 00:37:25.380 --> 00:37:28.490 align:start position:0% from certain information in order to allow<00:37:25.619> for<00:37:25.920> performance<00:37:26.540> by<00:37:27.540> segmenting<00:37:28.260> we 00:37:28.490 --> 00:37:28.500 align:start position:0% allow for performance by segmenting we 00:37:28.500 --> 00:37:30.650 align:start position:0% allow for performance by segmenting we allow<00:37:28.800> communication<00:37:29.400> between<00:37:29.880> the<00:37:30.180> nodes<00:37:30.420> on 00:37:30.650 --> 00:37:30.660 align:start position:0% allow communication between the nodes on 00:37:30.660 --> 00:37:33.770 align:start position:0% allow communication between the nodes on each<00:37:30.900> segment<00:37:31.320> to<00:37:32.040> be<00:37:32.160> uninhibited<00:37:33.060> by<00:37:33.599> the 00:37:33.770 --> 00:37:33.780 align:start position:0% each segment to be uninhibited by the 00:37:33.780 --> 00:37:36.470 align:start position:0% each segment to be uninhibited by the traffic<00:37:33.960> on<00:37:34.320> other<00:37:34.560> segments<00:37:35.460> so<00:37:36.000> I'm<00:37:36.300> not 00:37:36.470 --> 00:37:36.480 align:start position:0% traffic on other segments so I'm not 00:37:36.480 --> 00:37:40.190 align:start position:0% traffic on other segments so I'm not worried<00:37:36.900> about<00:37:37.140> uh<00:37:37.920> if<00:37:38.160> if<00:37:38.300> computer<00:37:39.300> a<00:37:39.720> wants 00:37:40.190 --> 00:37:40.200 align:start position:0% worried about uh if if computer a wants 00:37:40.200 --> 00:37:42.530 align:start position:0% worried about uh if if computer a wants to<00:37:40.320> talk<00:37:40.440> to<00:37:40.680> computer<00:37:40.859> C<00:37:41.400> I<00:37:42.060> don't<00:37:42.180> need<00:37:42.359> to 00:37:42.530 --> 00:37:42.540 align:start position:0% to talk to computer C I don't need to 00:37:42.540 --> 00:37:45.230 align:start position:0% to talk to computer C I don't need to involve<00:37:43.200> all<00:37:43.619> of<00:37:43.740> these<00:37:44.040> guys<00:37:44.220> I<00:37:45.000> can<00:37:45.119> just 00:37:45.230 --> 00:37:45.240 align:start position:0% involve all of these guys I can just 00:37:45.240 --> 00:37:47.569 align:start position:0% involve all of these guys I can just allow<00:37:45.540> them<00:37:45.780> to<00:37:46.020> talk<00:37:46.200> directly<00:37:46.740> and<00:37:47.280> so<00:37:47.400> what 00:37:47.569 --> 00:37:47.579 align:start position:0% allow them to talk directly and so what 00:37:47.579 --> 00:37:48.950 align:start position:0% allow them to talk directly and so what it's<00:37:47.700> doing<00:37:47.940> is<00:37:48.119> it's<00:37:48.359> it's<00:37:48.540> basically 00:37:48.950 --> 00:37:48.960 align:start position:0% it's doing is it's it's basically 00:37:48.960 --> 00:37:50.750 align:start position:0% it's doing is it's it's basically keeping<00:37:49.260> a<00:37:49.380> lot<00:37:49.500> of<00:37:49.680> traffic<00:37:49.859> from<00:37:50.280> going<00:37:50.520> over 00:37:50.750 --> 00:37:50.760 align:start position:0% keeping a lot of traffic from going over 00:37:50.760 --> 00:37:52.010 align:start position:0% keeping a lot of traffic from going over this<00:37:51.119> line 00:37:52.010 --> 00:37:52.020 align:start position:0% this line 00:37:52.020 --> 00:37:54.170 align:start position:0% this line and<00:37:52.500> therefore<00:37:52.859> we're<00:37:53.339> increasing<00:37:53.880> speed 00:37:54.170 --> 00:37:54.180 align:start position:0% and therefore we're increasing speed 00:37:54.180 --> 00:37:58.130 align:start position:0% and therefore we're increasing speed we're<00:37:54.780> increasing<00:37:55.260> throughput 00:37:58.130 --> 00:37:58.140 align:start position:0% 00:37:58.140 --> 00:38:00.349 align:start position:0% and<00:37:58.680> we're<00:37:58.859> decreasing<00:37:59.520> the<00:37:59.760> amount<00:38:00.000> of<00:38:00.180> sort 00:38:00.349 --> 00:38:00.359 align:start position:0% and we're decreasing the amount of sort 00:38:00.359 --> 00:38:01.910 align:start position:0% and we're decreasing the amount of sort of<00:38:00.540> errors<00:38:01.020> that<00:38:01.260> can<00:38:01.380> occur<00:38:01.619> and<00:38:01.800> we're 00:38:01.910 --> 00:38:01.920 align:start position:0% of errors that can occur and we're 00:38:01.920 --> 00:38:03.410 align:start position:0% of errors that can occur and we're segmenting<00:38:02.520> everything<00:38:02.700> out<00:38:03.000> to<00:38:03.180> make<00:38:03.300> it 00:38:03.410 --> 00:38:03.420 align:start position:0% segmenting everything out to make it 00:38:03.420 --> 00:38:05.990 align:start position:0% segmenting everything out to make it easier<00:38:03.660> to<00:38:03.839> fix<00:38:03.960> in<00:38:04.140> the<00:38:04.320> future<00:38:04.380> as<00:38:04.680> well 00:38:05.990 --> 00:38:06.000 align:start position:0% easier to fix in the future as well 00:38:06.000 --> 00:38:08.450 align:start position:0% easier to fix in the future as well now<00:38:06.480> let's<00:38:06.599> talk<00:38:06.780> about<00:38:06.900> a<00:38:07.320> network<00:38:07.440> model 00:38:08.450 --> 00:38:08.460 align:start position:0% now let's talk about a network model 00:38:08.460 --> 00:38:10.450 align:start position:0% now let's talk about a network model we've<00:38:09.000> just<00:38:09.119> talked<00:38:09.359> about<00:38:09.420> some<00:38:09.900> Network 00:38:10.450 --> 00:38:10.460 align:start position:0% we've just talked about some Network 00:38:10.460 --> 00:38:12.470 align:start position:0% we've just talked about some Network categories<00:38:11.460> so<00:38:11.700> now<00:38:11.880> let's<00:38:12.000> talk<00:38:12.180> about<00:38:12.240> the 00:38:12.470 --> 00:38:12.480 align:start position:0% categories so now let's talk about the 00:38:12.480 --> 00:38:13.670 align:start position:0% categories so now let's talk about the different<00:38:12.599> models<00:38:13.020> that<00:38:13.140> these<00:38:13.380> are<00:38:13.500> going<00:38:13.619> to 00:38:13.670 --> 00:38:13.680 align:start position:0% different models that these are going to 00:38:13.680 --> 00:38:16.190 align:start position:0% different models that these are going to fit<00:38:13.859> into<00:38:14.040> a<00:38:14.760> network<00:38:14.880> model 00:38:16.190 --> 00:38:16.200 align:start position:0% fit into a network model 00:38:16.200 --> 00:38:19.550 align:start position:0% fit into a network model is<00:38:16.619> a<00:38:16.859> design<00:38:17.180> uh<00:38:18.180> specification<00:38:18.900> if<00:38:19.260> you<00:38:19.440> will 00:38:19.550 --> 00:38:19.560 align:start position:0% is a design uh specification if you will 00:38:19.560 --> 00:38:23.990 align:start position:0% is a design uh specification if you will that<00:38:20.420> identifies<00:38:21.420> the<00:38:21.900> transmission<00:38:22.320> path 00:38:23.990 --> 00:38:24.000 align:start position:0% that identifies the transmission path 00:38:24.000 --> 00:38:25.910 align:start position:0% that identifies the transmission path that<00:38:24.480> nodes<00:38:24.780> on<00:38:25.079> the<00:38:25.200> network<00:38:25.320> are<00:38:25.619> going<00:38:25.800> to 00:38:25.910 --> 00:38:25.920 align:start position:0% that nodes on the network are going to 00:38:25.920 --> 00:38:28.430 align:start position:0% that nodes on the network are going to use<00:38:26.040> in<00:38:26.339> order<00:38:26.520> to<00:38:26.820> communicate<00:38:27.359> it<00:38:27.599> basically 00:38:28.430 --> 00:38:28.440 align:start position:0% use in order to communicate it basically 00:38:28.440 --> 00:38:31.430 align:start position:0% use in order to communicate it basically determines<00:38:29.160> whether<00:38:29.940> the<00:38:30.240> communication<00:38:30.839> and 00:38:31.430 --> 00:38:31.440 align:start position:0% determines whether the communication and 00:38:31.440 --> 00:38:33.290 align:start position:0% determines whether the communication and the<00:38:31.680> processing 00:38:33.290 --> 00:38:33.300 align:start position:0% the processing 00:38:33.300 --> 00:38:36.890 align:start position:0% the processing is<00:38:33.900> centralized<00:38:34.740> or<00:38:35.640> distributed 00:38:36.890 --> 00:38:36.900 align:start position:0% is centralized or distributed 00:38:36.900 --> 00:38:40.670 align:start position:0% is centralized or distributed so<00:38:37.500> in<00:38:37.800> a<00:38:38.359> centralized<00:38:39.359> Network<00:38:39.839> this<00:38:40.560> is 00:38:40.670 --> 00:38:40.680 align:start position:0% so in a centralized Network this is 00:38:40.680 --> 00:38:47.030 align:start position:0% so in a centralized Network this is where<00:38:40.920> we<00:38:41.160> have<00:38:41.400> our<00:38:42.180> Mainframe 00:38:47.030 --> 00:38:47.040 align:start position:0% 00:38:47.040 --> 00:38:53.150 align:start position:0% in<00:38:47.579> our<00:38:47.820> terminals 00:38:53.150 --> 00:38:53.160 align:start position:0% 00:38:53.160 --> 00:38:56.210 align:start position:0% the<00:38:53.880> host<00:38:54.119> computer 00:38:56.210 --> 00:38:56.220 align:start position:0% the host computer 00:38:56.220 --> 00:38:59.450 align:start position:0% the host computer this<00:38:56.820> guy<00:38:56.940> the<00:38:57.180> Mainframe<00:38:58.200> provides<00:38:58.980> all<00:38:59.280> of 00:38:59.450 --> 00:38:59.460 align:start position:0% this guy the Mainframe provides all of 00:38:59.460 --> 00:39:01.550 align:start position:0% this guy the Mainframe provides all of the<00:38:59.579> processing<00:39:00.180> and<00:39:00.960> all<00:39:01.140> of<00:39:01.260> the<00:39:01.440> network 00:39:01.550 --> 00:39:01.560 align:start position:0% the processing and all of the network 00:39:01.560 --> 00:39:04.190 align:start position:0% the processing and all of the network communication<00:39:02.359> and<00:39:03.359> the<00:39:03.540> users<00:39:03.900> that 00:39:04.190 --> 00:39:04.200 align:start position:0% communication and the users that 00:39:04.200 --> 00:39:06.589 align:start position:0% communication and the users that interface<00:39:04.680> with<00:39:05.040> the<00:39:05.280> host<00:39:05.520> computer<00:39:05.880> do<00:39:06.420> so 00:39:06.589 --> 00:39:06.599 align:start position:0% interface with the host computer do so 00:39:06.599 --> 00:39:09.950 align:start position:0% interface with the host computer do so through<00:39:06.839> these<00:39:07.400> Terminals<00:39:08.400> and<00:39:08.880> by<00:39:09.119> using<00:39:09.540> a 00:39:09.950 --> 00:39:09.960 align:start position:0% through these Terminals and by using a 00:39:09.960 --> 00:39:13.849 align:start position:0% through these Terminals and by using a terminal<00:39:10.320> emulator<00:39:10.859> that's<00:39:11.339> on<00:39:11.820> the<00:39:12.000> screen 00:39:13.849 --> 00:39:13.859 align:start position:0% terminal emulator that's on the screen 00:39:13.859 --> 00:39:15.829 align:start position:0% terminal emulator that's on the screen centralized<00:39:14.640> networks<00:39:15.180> are<00:39:15.420> highly 00:39:15.829 --> 00:39:15.839 align:start position:0% centralized networks are highly 00:39:15.839 --> 00:39:18.530 align:start position:0% centralized networks are highly effective<00:39:16.339> but<00:39:17.339> the<00:39:17.640> problem<00:39:17.820> is<00:39:18.060> they<00:39:18.300> can<00:39:18.420> be 00:39:18.530 --> 00:39:18.540 align:start position:0% effective but the problem is they can be 00:39:18.540 --> 00:39:20.930 align:start position:0% effective but the problem is they can be a<00:39:18.720> little<00:39:18.839> costly<00:39:19.320> to<00:39:19.619> maintain<00:39:20.099> because<00:39:20.520> this 00:39:20.930 --> 00:39:20.940 align:start position:0% a little costly to maintain because this 00:39:20.940 --> 00:39:22.490 align:start position:0% a little costly to maintain because this sucker<00:39:21.300> right<00:39:21.480> here<00:39:21.660> needs<00:39:21.960> to<00:39:22.020> be<00:39:22.140> so 00:39:22.490 --> 00:39:22.500 align:start position:0% sucker right here needs to be so 00:39:22.500 --> 00:39:25.130 align:start position:0% sucker right here needs to be so powerful<00:39:22.920> that<00:39:23.400> what<00:39:23.579> if<00:39:23.760> I<00:39:23.940> have<00:39:24.119> instead<00:39:25.020> of 00:39:25.130 --> 00:39:25.140 align:start position:0% powerful that what if I have instead of 00:39:25.140 --> 00:39:26.390 align:start position:0% powerful that what if I have instead of just<00:39:25.200> three<00:39:25.380> computers<00:39:25.740> what<00:39:25.920> if<00:39:26.040> I<00:39:26.160> had<00:39:26.220> a 00:39:26.390 --> 00:39:26.400 align:start position:0% just three computers what if I had a 00:39:26.400 --> 00:39:29.030 align:start position:0% just three computers what if I had a thousand<00:39:26.760> computers<00:39:27.240> and<00:39:27.780> what<00:39:28.020> if<00:39:28.260> this<00:39:28.619> goes 00:39:29.030 --> 00:39:29.040 align:start position:0% thousand computers and what if this goes 00:39:29.040 --> 00:39:31.849 align:start position:0% thousand computers and what if this goes out<00:39:29.160> well<00:39:29.400> now<00:39:29.700> I'm<00:39:29.940> in<00:39:30.240> major<00:39:30.540> issue<00:39:31.079> I<00:39:31.500> have<00:39:31.740> a 00:39:31.849 --> 00:39:31.859 align:start position:0% out well now I'm in major issue I have a 00:39:31.859 --> 00:39:33.829 align:start position:0% out well now I'm in major issue I have a major<00:39:32.040> problem<00:39:32.460> so<00:39:33.119> this<00:39:33.180> is<00:39:33.300> why<00:39:33.480> a<00:39:33.660> lot<00:39:33.780> of 00:39:33.829 --> 00:39:33.839 align:start position:0% major problem so this is why a lot of 00:39:33.839 --> 00:39:35.450 align:start position:0% major problem so this is why a lot of times<00:39:33.960> we<00:39:34.200> use<00:39:34.320> what's<00:39:34.500> called<00:39:34.740> a<00:39:35.099> client 00:39:35.450 --> 00:39:35.460 align:start position:0% times we use what's called a client 00:39:35.460 --> 00:39:38.810 align:start position:0% times we use what's called a client server<00:39:36.300> model 00:39:38.810 --> 00:39:38.820 align:start position:0% server model 00:39:38.820 --> 00:39:41.870 align:start position:0% server model the<00:39:39.420> client<00:39:39.780> server<00:39:40.260> model<00:39:40.560> it 00:39:41.870 --> 00:39:41.880 align:start position:0% the client server model it 00:39:41.880 --> 00:39:44.329 align:start position:0% the client server model it in<00:39:42.540> the<00:39:42.660> client<00:39:42.900> server<00:39:43.320> model<00:39:43.440> the<00:39:43.859> server<00:39:44.099> is 00:39:44.329 --> 00:39:44.339 align:start position:0% in the client server model the server is 00:39:44.339 --> 00:39:46.190 align:start position:0% in the client server model the server is responsible 00:39:46.190 --> 00:39:46.200 align:start position:0% responsible 00:39:46.200 --> 00:39:48.589 align:start position:0% responsible the<00:39:46.680> server<00:39:46.980> right<00:39:47.160> here<00:39:47.339> is<00:39:47.460> responsible<00:39:48.000> for 00:39:48.589 --> 00:39:48.599 align:start position:0% the server right here is responsible for 00:39:48.599 --> 00:39:52.490 align:start position:0% the server right here is responsible for providing<00:39:49.560> services<00:39:49.920> like<00:39:50.520> file<00:39:51.060> sharing<00:39:51.780> and 00:39:52.490 --> 00:39:52.500 align:start position:0% providing services like file sharing and 00:39:52.500 --> 00:39:54.230 align:start position:0% providing services like file sharing and printer<00:39:52.859> sharing<00:39:53.280> and<00:39:53.520> authentication 00:39:54.230 --> 00:39:54.240 align:start position:0% printer sharing and authentication 00:39:54.240 --> 00:39:57.010 align:start position:0% printer sharing and authentication services<00:39:54.839> and<00:39:55.440> data<00:39:55.920> storage<00:39:56.099> and<00:39:56.700> management 00:39:57.010 --> 00:39:57.020 align:start position:0% services and data storage and management 00:39:57.020 --> 00:40:00.410 align:start position:0% services and data storage and management to<00:39:58.020> these<00:39:58.500> clients<00:39:59.220> the<00:39:59.940> main<00:40:00.060> difference 00:40:00.410 --> 00:40:00.420 align:start position:0% to these clients the main difference 00:40:00.420 --> 00:40:03.170 align:start position:0% to these clients the main difference between<00:40:01.020> the<00:40:01.859> centralized<00:40:02.460> and<00:40:02.700> the<00:40:02.880> client 00:40:03.170 --> 00:40:03.180 align:start position:0% between the centralized and the client 00:40:03.180 --> 00:40:05.690 align:start position:0% between the centralized and the client server<00:40:03.660> model<00:40:03.900> is<00:40:04.680> that<00:40:04.859> in<00:40:05.099> this<00:40:05.280> client 00:40:05.690 --> 00:40:05.700 align:start position:0% server model is that in this client 00:40:05.700 --> 00:40:08.810 align:start position:0% server model is that in this client server<00:40:06.240> Network<00:40:06.560> the<00:40:07.560> processing<00:40:08.220> and<00:40:08.640> the 00:40:08.810 --> 00:40:08.820 align:start position:0% server Network the processing and the 00:40:08.820 --> 00:40:11.630 align:start position:0% server Network the processing and the resources<00:40:09.359> can<00:40:09.960> be<00:40:10.140> allocated<00:40:10.619> wherever<00:40:11.280> they 00:40:11.630 --> 00:40:11.640 align:start position:0% resources can be allocated wherever they 00:40:11.640 --> 00:40:14.630 align:start position:0% resources can be allocated wherever they are<00:40:11.760> needed<00:40:12.200> including<00:40:13.200> on<00:40:13.560> the<00:40:13.740> client<00:40:14.040> and 00:40:14.630 --> 00:40:14.640 align:start position:0% are needed including on the client and 00:40:14.640 --> 00:40:16.310 align:start position:0% are needed including on the client and they<00:40:14.760> can<00:40:14.940> also<00:40:15.119> be<00:40:15.300> distributed<00:40:15.780> whenever 00:40:16.310 --> 00:40:16.320 align:start position:0% they can also be distributed whenever 00:40:16.320 --> 00:40:17.470 align:start position:0% they can also be distributed whenever necessary 00:40:17.470 --> 00:40:17.480 align:start position:0% necessary 00:40:17.480 --> 00:40:20.569 align:start position:0% necessary and<00:40:18.480> the<00:40:19.380> end 00:40:20.569 --> 00:40:20.579 align:start position:0% and the end 00:40:20.579 --> 00:40:24.470 align:start position:0% and the end nodes<00:40:21.480> These<00:40:22.079> Guys<00:40:22.200> these<00:40:23.099> clients<00:40:23.640> can<00:40:24.119> still 00:40:24.470 --> 00:40:24.480 align:start position:0% nodes These Guys these clients can still 00:40:24.480 --> 00:40:27.050 align:start position:0% nodes These Guys these clients can still perform<00:40:24.780> their<00:40:25.380> own<00:40:25.560> processing<00:40:26.160> and<00:40:26.880> end 00:40:27.050 --> 00:40:27.060 align:start position:0% perform their own processing and end 00:40:27.060 --> 00:40:29.030 align:start position:0% perform their own processing and end user<00:40:27.420> tasks<00:40:27.720> without<00:40:27.960> having<00:40:28.320> to<00:40:28.619> constantly 00:40:29.030 --> 00:40:29.040 align:start position:0% user tasks without having to constantly 00:40:29.040 --> 00:40:32.030 align:start position:0% user tasks without having to constantly talk<00:40:29.460> over<00:40:30.000> to<00:40:30.180> the<00:40:30.359> server<00:40:30.660> so<00:40:31.200> if<00:40:31.380> I<00:40:31.560> need<00:40:31.680> a 00:40:32.030 --> 00:40:32.040 align:start position:0% talk over to the server so if I need a 00:40:32.040 --> 00:40:34.790 align:start position:0% talk over to the server so if I need a file<00:40:32.280> for<00:40:32.700> instance<00:40:32.940> I<00:40:33.240> can<00:40:33.359> get<00:40:33.540> that<00:40:33.780> file<00:40:34.140> do 00:40:34.790 --> 00:40:34.800 align:start position:0% file for instance I can get that file do 00:40:34.800 --> 00:40:36.890 align:start position:0% file for instance I can get that file do the<00:40:34.980> work<00:40:35.160> on<00:40:35.400> my<00:40:35.640> computer<00:40:35.880> and<00:40:36.420> then<00:40:36.540> I<00:40:36.780> can 00:40:36.890 --> 00:40:36.900 align:start position:0% the work on my computer and then I can 00:40:36.900 --> 00:40:39.230 align:start position:0% the work on my computer and then I can save<00:40:37.140> it<00:40:37.320> back<00:40:37.500> to<00:40:37.680> the<00:40:37.859> server<00:40:38.099> whereas<00:40:38.940> here 00:40:39.230 --> 00:40:39.240 align:start position:0% save it back to the server whereas here 00:40:39.240 --> 00:40:41.329 align:start position:0% save it back to the server whereas here on<00:40:39.480> the<00:40:39.660> centralized<00:40:40.320> Mainframe<00:40:41.040> terminal 00:40:41.329 --> 00:40:41.339 align:start position:0% on the centralized Mainframe terminal 00:40:41.339 --> 00:40:44.450 align:start position:0% on the centralized Mainframe terminal setup<00:40:41.760> all<00:40:42.660> the<00:40:42.839> work<00:40:42.960> is<00:40:43.440> actually<00:40:43.680> done<00:40:43.980> on 00:40:44.450 --> 00:40:44.460 align:start position:0% setup all the work is actually done on 00:40:44.460 --> 00:40:47.630 align:start position:0% setup all the work is actually done on this<00:40:44.880> major<00:40:45.420> huge<00:40:45.900> computer<00:40:46.140> and<00:40:47.099> here<00:40:47.280> in<00:40:47.460> the 00:40:47.630 --> 00:40:47.640 align:start position:0% this major huge computer and here in the 00:40:47.640 --> 00:40:49.370 align:start position:0% this major huge computer and here in the terminal<00:40:48.000> we're<00:40:48.480> just<00:40:48.660> sort<00:40:48.780> of<00:40:48.900> having<00:40:49.079> a 00:40:49.370 --> 00:40:49.380 align:start position:0% terminal we're just sort of having a 00:40:49.380 --> 00:40:52.430 align:start position:0% terminal we're just sort of having a portal<00:40:49.740> to<00:40:50.040> see<00:40:50.339> what's<00:40:50.579> going<00:40:50.880> on<00:40:51.480> now<00:40:52.079> both 00:40:52.430 --> 00:40:52.440 align:start position:0% portal to see what's going on now both 00:40:52.440 --> 00:40:55.130 align:start position:0% portal to see what's going on now both of<00:40:52.619> these<00:40:53.000> are<00:40:54.000> different<00:40:54.359> from<00:40:54.720> what<00:40:54.839> we<00:40:54.960> call 00:40:55.130 --> 00:40:55.140 align:start position:0% of these are different from what we call 00:40:55.140 --> 00:40:57.589 align:start position:0% of these are different from what we call a<00:40:55.440> peer-to-peer<00:40:56.339> Network<00:40:56.640> we<00:40:57.240> talked<00:40:57.540> about 00:40:57.589 --> 00:40:57.599 align:start position:0% a peer-to-peer Network we talked about 00:40:57.599 --> 00:41:00.109 align:start position:0% a peer-to-peer Network we talked about appear<00:40:58.260> in<00:40:58.740> the<00:40:58.859> previous<00:40:58.980> module<00:40:59.640> but<00:40:59.940> a 00:41:00.109 --> 00:41:00.119 align:start position:0% appear in the previous module but a 00:41:00.119 --> 00:41:01.370 align:start position:0% appear in the previous module but a peer-to-peer<00:41:00.599> Network<00:41:00.720> which<00:41:01.020> you<00:41:01.200> might 00:41:01.370 --> 00:41:01.380 align:start position:0% peer-to-peer Network which you might 00:41:01.380 --> 00:41:07.609 align:start position:0% peer-to-peer Network which you might also<00:41:01.740> see<00:41:02.040> as<00:41:02.940> P2P<00:41:03.859> or<00:41:04.859> PTP 00:41:07.609 --> 00:41:07.619 align:start position:0% also see as P2P or PTP 00:41:07.619 --> 00:41:11.990 align:start position:0% also see as P2P or PTP uh<00:41:08.460> is<00:41:09.240> a<00:41:09.839> network<00:41:09.960> in<00:41:10.320> which<00:41:10.560> each<00:41:11.160> node<00:41:11.579> on 00:41:11.990 --> 00:41:12.000 align:start position:0% uh is a network in which each node on 00:41:12.000 --> 00:41:14.450 align:start position:0% uh is a network in which each node on the<00:41:12.119> network<00:41:12.300> is<00:41:13.079> responsible<00:41:13.619> for<00:41:13.980> its<00:41:14.400> own 00:41:14.450 --> 00:41:14.460 align:start position:0% the network is responsible for its own 00:41:14.460 --> 00:41:16.430 align:start position:0% the network is responsible for its own Computing<00:41:14.940> its<00:41:15.300> own<00:41:15.359> management<00:41:15.660> its<00:41:16.380> own 00:41:16.430 --> 00:41:16.440 align:start position:0% Computing its own management its own 00:41:16.440 --> 00:41:19.250 align:start position:0% Computing its own management its own security<00:41:16.740> its<00:41:17.400> own<00:41:17.520> storage<00:41:18.079> its<00:41:19.079> own 00:41:19.250 --> 00:41:19.260 align:start position:0% security its own storage its own 00:41:19.260 --> 00:41:22.010 align:start position:0% security its own storage its own resource<00:41:19.920> sharing<00:41:20.220> like<00:41:20.400> printers<00:41:21.020> it's 00:41:22.010 --> 00:41:22.020 align:start position:0% resource sharing like printers it's 00:41:22.020 --> 00:41:24.349 align:start position:0% resource sharing like printers it's completely<00:41:22.940> decentralized<00:41:23.940> and<00:41:24.240> it's 00:41:24.349 --> 00:41:24.359 align:start position:0% completely decentralized and it's 00:41:24.359 --> 00:41:27.470 align:start position:0% completely decentralized and it's commonly<00:41:24.720> referred<00:41:25.140> to<00:41:25.260> as<00:41:25.560> a<00:41:26.220> work<00:41:26.339> group 00:41:27.470 --> 00:41:27.480 align:start position:0% commonly referred to as a work group 00:41:27.480 --> 00:41:29.390 align:start position:0% commonly referred to as a work group now<00:41:28.079> this<00:41:28.380> is<00:41:28.500> sort<00:41:28.740> of<00:41:28.800> like<00:41:28.980> if<00:41:29.160> we<00:41:29.280> were 00:41:29.390 --> 00:41:29.400 align:start position:0% now this is sort of like if we were 00:41:29.400 --> 00:41:32.150 align:start position:0% now this is sort of like if we were going<00:41:29.520> to<00:41:29.579> make<00:41:29.760> a<00:41:30.000> reference<00:41:30.420> to<00:41:31.020> a<00:41:31.440> political 00:41:32.150 --> 00:41:32.160 align:start position:0% going to make a reference to a political 00:41:32.160 --> 00:41:35.089 align:start position:0% going to make a reference to a political metaphor<00:41:32.820> this<00:41:33.599> would<00:41:33.780> be<00:41:33.960> like<00:41:34.320> communism 00:41:35.089 --> 00:41:35.099 align:start position:0% metaphor this would be like communism 00:41:35.099 --> 00:41:38.510 align:start position:0% metaphor this would be like communism everyone<00:41:35.579> works<00:41:36.240> together<00:41:36.619> equally<00:41:37.619> and 00:41:38.510 --> 00:41:38.520 align:start position:0% everyone works together equally and 00:41:38.520 --> 00:41:41.089 align:start position:0% everyone works together equally and everyone<00:41:38.820> is<00:41:39.060> responsible<00:41:39.660> for<00:41:40.380> their<00:41:40.920> own 00:41:41.089 --> 00:41:41.099 align:start position:0% everyone is responsible for their own 00:41:41.099 --> 00:41:43.250 align:start position:0% everyone is responsible for their own thing<00:41:41.400> and<00:41:42.119> then<00:41:42.240> they<00:41:42.420> can<00:41:42.599> share<00:41:42.839> that<00:41:43.020> with 00:41:43.250 --> 00:41:43.260 align:start position:0% thing and then they can share that with 00:41:43.260 --> 00:41:46.670 align:start position:0% thing and then they can share that with everyone<00:41:43.560> else<00:41:43.859> whereas<00:41:44.460> in<00:41:44.880> a<00:41:45.119> client<00:41:45.839> server 00:41:46.670 --> 00:41:46.680 align:start position:0% everyone else whereas in a client server 00:41:46.680 --> 00:41:49.609 align:start position:0% everyone else whereas in a client server sort<00:41:47.099> of<00:41:47.220> uh 00:41:49.609 --> 00:41:49.619 align:start position:0% sort of uh 00:41:49.619 --> 00:41:53.630 align:start position:0% sort of uh model<00:41:50.220> we're<00:41:50.820> dealing<00:41:51.180> with<00:41:51.420> say<00:41:52.020> a<00:41:52.740> democracy 00:41:53.630 --> 00:41:53.640 align:start position:0% model we're dealing with say a democracy 00:41:53.640 --> 00:41:55.310 align:start position:0% model we're dealing with say a democracy in<00:41:53.760> which<00:41:53.940> you<00:41:54.060> have<00:41:54.240> a<00:41:54.420> president<00:41:54.599> or<00:41:55.020> prime 00:41:55.310 --> 00:41:55.320 align:start position:0% in which you have a president or prime 00:41:55.320 --> 00:41:57.290 align:start position:0% in which you have a president or prime minister<00:41:55.680> someone<00:41:56.460> who's<00:41:56.700> going<00:41:56.940> to<00:41:57.000> make<00:41:57.119> a 00:41:57.290 --> 00:41:57.300 align:start position:0% minister someone who's going to make a 00:41:57.300 --> 00:41:59.089 align:start position:0% minister someone who's going to make a lot<00:41:57.359> of<00:41:57.540> the<00:41:57.660> decisions<00:41:58.020> but<00:41:58.500> you<00:41:58.740> are<00:41:58.920> still 00:41:59.089 --> 00:41:59.099 align:start position:0% lot of the decisions but you are still 00:41:59.099 --> 00:42:01.250 align:start position:0% lot of the decisions but you are still at<00:41:59.280> Liberty<00:41:59.640> to<00:41:59.820> exercise<00:42:00.359> a<00:42:00.780> lot<00:42:00.900> of<00:42:01.020> your<00:42:01.079> own 00:42:01.250 --> 00:42:01.260 align:start position:0% at Liberty to exercise a lot of your own 00:42:01.260 --> 00:42:03.650 align:start position:0% at Liberty to exercise a lot of your own stuff<00:42:01.440> and<00:42:01.920> that's<00:42:02.099> very<00:42:02.339> different<00:42:02.520> from 00:42:03.650 --> 00:42:03.660 align:start position:0% stuff and that's very different from 00:42:03.660 --> 00:42:07.609 align:start position:0% stuff and that's very different from say<00:42:04.380> a<00:42:04.740> terminal<00:42:05.599> Mainframe<00:42:06.599> which<00:42:07.079> is<00:42:07.260> would 00:42:07.609 --> 00:42:07.619 align:start position:0% say a terminal Mainframe which is would 00:42:07.619 --> 00:42:09.349 align:start position:0% say a terminal Mainframe which is would be<00:42:07.740> equivalent<00:42:08.040> to<00:42:08.160> like<00:42:08.280> a<00:42:08.460> monarchy<00:42:09.000> a 00:42:09.349 --> 00:42:09.359 align:start position:0% be equivalent to like a monarchy a 00:42:09.359 --> 00:42:10.930 align:start position:0% be equivalent to like a monarchy a really<00:42:09.540> strict<00:42:09.839> here<00:42:10.079> I<00:42:10.440> should<00:42:10.560> say 00:42:10.930 --> 00:42:10.940 align:start position:0% really strict here I should say 00:42:10.940 --> 00:42:13.550 align:start position:0% really strict here I should say tyrannical<00:42:11.940> monarchy<00:42:12.599> in<00:42:13.020> which<00:42:13.260> everything 00:42:13.550 --> 00:42:13.560 align:start position:0% tyrannical monarchy in which everything 00:42:13.560 --> 00:42:15.829 align:start position:0% tyrannical monarchy in which everything is<00:42:13.920> decided<00:42:14.400> for<00:42:14.579> you<00:42:14.760> and<00:42:15.240> you<00:42:15.420> make<00:42:15.599> no 00:42:15.829 --> 00:42:15.839 align:start position:0% is decided for you and you make no 00:42:15.839 --> 00:42:19.010 align:start position:0% is decided for you and you make no decisions<00:42:16.320> on<00:42:16.680> your<00:42:16.920> own<00:42:17.520> so<00:42:18.240> one<00:42:18.780> of<00:42:18.900> the 00:42:19.010 --> 00:42:19.020 align:start position:0% decisions on your own so one of the 00:42:19.020 --> 00:42:22.490 align:start position:0% decisions on your own so one of the problem<00:42:19.440> with<00:42:19.859> work<00:42:20.160> groups<00:42:20.640> is<00:42:21.420> that<00:42:22.079> user 00:42:22.490 --> 00:42:22.500 align:start position:0% problem with work groups is that user 00:42:22.500 --> 00:42:24.589 align:start position:0% problem with work groups is that user accounts<00:42:22.920> need<00:42:23.099> to<00:42:23.220> be<00:42:23.339> replicated<00:42:23.880> onto<00:42:24.359> each 00:42:24.589 --> 00:42:24.599 align:start position:0% accounts need to be replicated onto each 00:42:24.599 --> 00:42:27.050 align:start position:0% accounts need to be replicated onto each node<00:42:25.020> so<00:42:25.320> that<00:42:25.500> if<00:42:25.680> I<00:42:25.859> want<00:42:25.980> to<00:42:26.099> get<00:42:26.160> access<00:42:26.339> to 00:42:27.050 --> 00:42:27.060 align:start position:0% node so that if I want to get access to 00:42:27.060 --> 00:42:29.150 align:start position:0% node so that if I want to get access to this<00:42:27.300> computer<00:42:27.480> and<00:42:27.900> I<00:42:28.079> usually<00:42:28.380> work<00:42:28.680> on 00:42:29.150 --> 00:42:29.160 align:start position:0% this computer and I usually work on 00:42:29.160 --> 00:42:31.970 align:start position:0% this computer and I usually work on computer<00:42:29.280> y<00:42:30.020> all<00:42:31.020> of<00:42:31.140> my<00:42:31.320> username<00:42:31.740> password 00:42:31.970 --> 00:42:31.980 align:start position:0% computer y all of my username password 00:42:31.980 --> 00:42:33.829 align:start position:0% computer y all of my username password everything<00:42:32.400> is<00:42:32.700> going<00:42:32.820> to<00:42:32.940> be<00:42:33.000> on<00:42:33.240> there<00:42:33.420> and 00:42:33.829 --> 00:42:33.839 align:start position:0% everything is going to be on there and 00:42:33.839 --> 00:42:36.170 align:start position:0% everything is going to be on there and if<00:42:34.020> it's<00:42:34.200> not<00:42:34.500> done<00:42:34.920> if<00:42:35.220> I<00:42:35.400> don't<00:42:35.460> sort<00:42:35.700> of<00:42:35.820> copy 00:42:36.170 --> 00:42:36.180 align:start position:0% if it's not done if I don't sort of copy 00:42:36.180 --> 00:42:37.310 align:start position:0% if it's not done if I don't sort of copy everything<00:42:36.300> over<00:42:36.599> there's<00:42:36.839> no<00:42:36.960> way<00:42:37.079> I<00:42:37.200> can 00:42:37.310 --> 00:42:37.320 align:start position:0% everything over there's no way I can 00:42:37.320 --> 00:42:39.589 align:start position:0% everything over there's no way I can gain<00:42:37.440> access<00:42:37.680> so<00:42:38.099> this<00:42:38.220> is<00:42:38.339> the<00:42:38.640> problem<00:42:38.880> with 00:42:39.589 --> 00:42:39.599 align:start position:0% gain access so this is the problem with 00:42:39.599 --> 00:42:41.270 align:start position:0% gain access so this is the problem with this<00:42:39.839> model<00:42:39.960> is<00:42:40.260> each<00:42:40.500> person's<00:42:40.920> their<00:42:41.099> own 00:42:41.270 --> 00:42:41.280 align:start position:0% this model is each person's their own 00:42:41.280 --> 00:42:44.589 align:start position:0% this model is each person's their own but<00:42:41.880> if<00:42:42.119> x<00:42:42.359> has<00:42:42.720> wheat<00:42:43.380> and<00:42:43.619> I<00:42:43.800> have<00:42:43.980> corn 00:42:44.589 --> 00:42:44.599 align:start position:0% but if x has wheat and I have corn 00:42:44.599 --> 00:42:46.910 align:start position:0% but if x has wheat and I have corn there's<00:42:45.599> sort<00:42:45.900> of<00:42:46.020> no<00:42:46.260> sharing<00:42:46.680> that's 00:42:46.910 --> 00:42:46.920 align:start position:0% there's sort of no sharing that's 00:42:46.920 --> 00:42:49.130 align:start position:0% there's sort of no sharing that's automatically<00:42:47.700> set<00:42:47.940> up<00:42:48.060> we<00:42:48.359> have<00:42:48.540> to<00:42:48.780> create 00:42:49.130 --> 00:42:49.140 align:start position:0% automatically set up we have to create 00:42:49.140 --> 00:42:50.690 align:start position:0% automatically set up we have to create our<00:42:49.500> own<00:42:49.680> sort<00:42:49.920> of<00:42:50.099> share<00:42:50.280> and<00:42:50.400> then<00:42:50.520> if 00:42:50.690 --> 00:42:50.700 align:start position:0% our own sort of share and then if 00:42:50.700 --> 00:42:51.890 align:start position:0% our own sort of share and then if someone<00:42:50.820> else<00:42:51.060> says<00:42:51.359> something<00:42:51.480> I<00:42:51.720> have<00:42:51.839> to 00:42:51.890 --> 00:42:51.900 align:start position:0% someone else says something I have to 00:42:51.900 --> 00:42:53.569 align:start position:0% someone else says something I have to share<00:42:52.079> with<00:42:52.200> them<00:42:52.380> and<00:42:52.619> so<00:42:52.740> on<00:42:52.859> and<00:42:53.040> so<00:42:53.220> forth 00:42:53.569 --> 00:42:53.579 align:start position:0% share with them and so on and so forth 00:42:53.579 --> 00:42:55.790 align:start position:0% share with them and so on and so forth now<00:42:54.300> we<00:42:54.599> might<00:42:54.780> sometimes<00:42:55.140> mix<00:42:55.500> these 00:42:55.790 --> 00:42:55.800 align:start position:0% now we might sometimes mix these 00:42:55.800 --> 00:42:57.650 align:start position:0% now we might sometimes mix these together<00:42:55.980> into<00:42:56.280> what's<00:42:56.460> called<00:42:56.640> a<00:42:56.880> mixed<00:42:57.300> mode 00:42:57.650 --> 00:42:57.660 align:start position:0% together into what's called a mixed mode 00:42:57.660 --> 00:42:59.870 align:start position:0% together into what's called a mixed mode Network<00:42:58.140> and<00:42:58.920> that's<00:42:59.040> just<00:42:59.280> like<00:42:59.460> it<00:42:59.700> sounds 00:42:59.870 --> 00:42:59.880 align:start position:0% Network and that's just like it sounds 00:42:59.880 --> 00:43:02.270 align:start position:0% Network and that's just like it sounds it<00:43:00.300> mixes<00:43:00.720> aspects<00:43:01.319> of<00:43:01.500> two<00:43:01.740> or<00:43:01.920> more<00:43:02.040> of<00:43:02.160> the 00:43:02.270 --> 00:43:02.280 align:start position:0% it mixes aspects of two or more of the 00:43:02.280 --> 00:43:04.910 align:start position:0% it mixes aspects of two or more of the different<00:43:02.460> network<00:43:02.819> models<00:43:03.480> an<00:43:04.440> example 00:43:04.910 --> 00:43:04.920 align:start position:0% different network models an example 00:43:04.920 --> 00:43:07.430 align:start position:0% different network models an example might<00:43:05.640> be<00:43:05.880> a<00:43:06.180> work<00:43:06.420> group<00:43:06.660> of<00:43:06.900> computers 00:43:07.430 --> 00:43:07.440 align:start position:0% might be a work group of computers 00:43:07.440 --> 00:43:09.589 align:start position:0% might be a work group of computers connected<00:43:08.339> together<00:43:08.579> via<00:43:09.119> some<00:43:09.359> sort<00:43:09.540> of 00:43:09.589 --> 00:43:09.599 align:start position:0% connected together via some sort of 00:43:09.599 --> 00:43:12.710 align:start position:0% connected together via some sort of short<00:43:09.900> range<00:43:10.319> Wireless<00:43:11.119> while<00:43:12.119> allowing 00:43:12.710 --> 00:43:12.720 align:start position:0% short range Wireless while allowing 00:43:12.720 --> 00:43:14.630 align:start position:0% short range Wireless while allowing those<00:43:13.020> computers<00:43:13.500> to<00:43:13.800> connect<00:43:13.980> to<00:43:14.400> a 00:43:14.630 --> 00:43:14.640 align:start position:0% those computers to connect to a 00:43:14.640 --> 00:43:16.849 align:start position:0% those computers to connect to a Mainframe<00:43:15.180> computer<00:43:15.359> and<00:43:16.079> using<00:43:16.440> terminal 00:43:16.849 --> 00:43:16.859 align:start position:0% Mainframe computer and using terminal 00:43:16.859 --> 00:43:17.930 align:start position:0% Mainframe computer and using terminal emulation 00:43:17.930 --> 00:43:17.940 align:start position:0% emulation 00:43:17.940 --> 00:43:20.510 align:start position:0% emulation so<00:43:18.720> alternative<00:43:19.680> we<00:43:19.859> might<00:43:20.040> have<00:43:20.220> a<00:43:20.400> work 00:43:20.510 --> 00:43:20.520 align:start position:0% so alternative we might have a work 00:43:20.520 --> 00:43:22.370 align:start position:0% so alternative we might have a work group<00:43:20.760> and<00:43:21.119> then<00:43:21.240> a<00:43:21.420> centralized<00:43:21.839> server<00:43:22.260> Etc 00:43:22.370 --> 00:43:22.380 align:start position:0% group and then a centralized server Etc 00:43:22.380 --> 00:43:24.890 align:start position:0% group and then a centralized server Etc so<00:43:22.740> we<00:43:23.040> see<00:43:23.220> we<00:43:23.520> can<00:43:23.640> see<00:43:23.880> mixed<00:43:24.300> mode<00:43:24.420> networks 00:43:24.890 --> 00:43:24.900 align:start position:0% so we see we can see mixed mode networks 00:43:24.900 --> 00:43:27.589 align:start position:0% so we see we can see mixed mode networks they're<00:43:25.079> usually<00:43:25.520> uh<00:43:26.520> not<00:43:26.880> as<00:43:27.060> popular<00:43:27.300> in 00:43:27.589 --> 00:43:27.599 align:start position:0% they're usually uh not as popular in 00:43:27.599 --> 00:43:29.450 align:start position:0% they're usually uh not as popular in huge<00:43:27.960> Enterprises<00:43:28.500> because<00:43:28.740> of<00:43:28.920> the<00:43:29.099> lack<00:43:29.339> of 00:43:29.450 --> 00:43:29.460 align:start position:0% huge Enterprises because of the lack of 00:43:29.460 --> 00:43:30.950 align:start position:0% huge Enterprises because of the lack of control 00:43:30.950 --> 00:43:30.960 align:start position:0% control 00:43:30.960 --> 00:43:33.109 align:start position:0% control um except<00:43:31.740> in<00:43:31.920> certain<00:43:32.220> specific<00:43:32.579> instances 00:43:33.109 --> 00:43:33.119 align:start position:0% um except in certain specific instances 00:43:33.119 --> 00:43:35.690 align:start position:0% um except in certain specific instances uh<00:43:33.900> but<00:43:34.200> we<00:43:34.500> do<00:43:34.619> see<00:43:34.800> them<00:43:34.980> and<00:43:35.220> it's<00:43:35.339> important 00:43:35.690 --> 00:43:35.700 align:start position:0% uh but we do see them and it's important 00:43:35.700 --> 00:43:37.609 align:start position:0% uh but we do see them and it's important to<00:43:35.880> know<00:43:36.000> that<00:43:36.240> just<00:43:36.599> like<00:43:36.780> in<00:43:36.960> anything<00:43:37.140> we 00:43:37.609 --> 00:43:37.619 align:start position:0% to know that just like in anything we 00:43:37.619 --> 00:43:39.589 align:start position:0% to know that just like in anything we can<00:43:37.800> mix<00:43:38.099> and<00:43:38.280> match 00:43:39.589 --> 00:43:39.599 align:start position:0% can mix and match 00:43:39.599 --> 00:43:41.630 align:start position:0% can mix and match to<00:43:40.020> however<00:43:40.260> we<00:43:40.500> want<00:43:40.680> the<00:43:40.859> the<00:43:41.040> network<00:43:41.280> to 00:43:41.630 --> 00:43:41.640 align:start position:0% to however we want the the network to 00:43:41.640 --> 00:43:44.089 align:start position:0% to however we want the the network to work<00:43:41.819> all<00:43:42.540> right<00:43:42.720> so<00:43:42.900> now<00:43:43.079> just<00:43:43.380> to<00:43:43.560> recap<00:43:43.859> what 00:43:44.089 --> 00:43:44.099 align:start position:0% work all right so now just to recap what 00:43:44.099 --> 00:43:46.730 align:start position:0% work all right so now just to recap what we've<00:43:44.280> talked<00:43:44.520> about<00:43:44.579> we<00:43:45.420> can<00:43:45.599> now<00:43:45.839> describe 00:43:46.730 --> 00:43:46.740 align:start position:0% we've talked about we can now describe 00:43:46.740 --> 00:43:49.250 align:start position:0% we've talked about we can now describe and<00:43:46.920> Define<00:43:47.220> the<00:43:47.940> characteristics<00:43:48.480> of<00:43:48.720> a<00:43:48.900> lan 00:43:49.250 --> 00:43:49.260 align:start position:0% and Define the characteristics of a lan 00:43:49.260 --> 00:43:52.670 align:start position:0% and Define the characteristics of a lan or<00:43:49.619> a<00:43:49.800> local<00:43:49.920> area<00:43:50.220> network<00:43:50.579> as<00:43:51.480> well<00:43:51.660> as<00:43:51.960> a<00:43:52.380> Wan 00:43:52.670 --> 00:43:52.680 align:start position:0% or a local area network as well as a Wan 00:43:52.680 --> 00:43:54.770 align:start position:0% or a local area network as well as a Wan or<00:43:52.920> a<00:43:53.099> wide<00:43:53.280> area<00:43:53.460> network<00:43:53.760> and<00:43:54.359> we<00:43:54.480> also 00:43:54.770 --> 00:43:54.780 align:start position:0% or a wide area network and we also 00:43:54.780 --> 00:43:57.890 align:start position:0% or a wide area network and we also talked<00:43:55.140> about<00:43:55.440> several<00:43:56.339> of<00:43:56.520> the<00:43:56.880> uh<00:43:57.300> different 00:43:57.890 --> 00:43:57.900 align:start position:0% talked about several of the uh different 00:43:57.900 --> 00:44:01.390 align:start position:0% talked about several of the uh different types<00:43:58.500> of<00:43:58.619> lands<00:43:59.160> or<00:43:59.280> in<00:43:59.579> some<00:43:59.760> cases<00:44:00.380> lands 00:44:01.390 --> 00:44:01.400 align:start position:0% types of lands or in some cases lands 00:44:01.400 --> 00:44:06.530 align:start position:0% types of lands or in some cases lands including<00:44:02.540> a<00:44:03.540> can<00:44:03.900> or<00:44:04.200> campus<00:44:04.680> area<00:44:04.980> network<00:44:05.540> a 00:44:06.530 --> 00:44:06.540 align:start position:0% including a can or campus area network a 00:44:06.540 --> 00:44:09.589 align:start position:0% including a can or campus area network a man<00:44:06.800> or<00:44:07.800> municipal<00:44:08.460> or<00:44:08.640> metropolitan<00:44:09.420> area 00:44:09.589 --> 00:44:09.599 align:start position:0% man or municipal or metropolitan area 00:44:09.599 --> 00:44:12.710 align:start position:0% man or municipal or metropolitan area network<00:44:09.980> a<00:44:10.980> pan<00:44:11.220> or<00:44:11.700> personal<00:44:12.000> area<00:44:12.359> network 00:44:12.710 --> 00:44:12.720 align:start position:0% network a pan or personal area network 00:44:12.720 --> 00:44:14.210 align:start position:0% network a pan or personal area network which<00:44:13.140> is<00:44:13.200> where<00:44:13.440> the<00:44:13.560> computers<00:44:13.920> connect 00:44:14.210 --> 00:44:14.220 align:start position:0% which is where the computers connect 00:44:14.220 --> 00:44:16.250 align:start position:0% which is where the computers connect directly<00:44:14.700> to<00:44:14.880> one<00:44:15.060> another<00:44:15.240> and<00:44:16.020> then<00:44:16.140> we 00:44:16.250 --> 00:44:16.260 align:start position:0% directly to one another and then we 00:44:16.260 --> 00:44:18.890 align:start position:0% directly to one another and then we looked<00:44:16.560> at<00:44:16.619> a<00:44:16.859> gan<00:44:17.160> or<00:44:17.520> a<00:44:17.700> global<00:44:18.300> area<00:44:18.540> network 00:44:18.890 --> 00:44:18.900 align:start position:0% looked at a gan or a global area network 00:44:18.900 --> 00:44:21.950 align:start position:0% looked at a gan or a global area network and<00:44:19.560> then<00:44:19.680> we<00:44:19.920> also<00:44:20.220> talked<00:44:20.640> about<00:44:20.760> en<00:44:21.359> or<00:44:21.780> an 00:44:21.950 --> 00:44:21.960 align:start position:0% and then we also talked about en or an 00:44:21.960 --> 00:44:25.069 align:start position:0% and then we also talked about en or an Enterprise<00:44:22.319> Network<00:44:23.099> okay<00:44:23.819> so<00:44:24.300> these<00:44:24.599> are<00:44:24.720> all 00:44:25.069 --> 00:44:25.079 align:start position:0% Enterprise Network okay so these are all 00:44:25.079 --> 00:44:27.849 align:start position:0% Enterprise Network okay so these are all uh<00:44:25.560> different 00:44:27.849 --> 00:44:27.859 align:start position:0% uh different 00:44:27.859 --> 00:44:30.170 align:start position:0% uh different acronyms<00:44:28.859> that<00:44:28.980> you<00:44:29.160> need<00:44:29.280> to<00:44:29.460> learn<00:44:29.640> for<00:44:30.000> the 00:44:30.170 --> 00:44:30.180 align:start position:0% acronyms that you need to learn for the 00:44:30.180 --> 00:44:33.790 align:start position:0% acronyms that you need to learn for the exam<00:44:30.480> we<00:44:31.260> also<00:44:31.500> talked<00:44:31.800> about<00:44:32.000> uh<00:44:33.000> an<00:44:33.480> internet 00:44:33.790 --> 00:44:33.800 align:start position:0% exam we also talked about uh an internet 00:44:33.800 --> 00:44:36.109 align:start position:0% exam we also talked about uh an internet intranet<00:44:34.800> an<00:44:35.099> Extranet<00:44:35.640> remember<00:44:35.819> the 00:44:36.109 --> 00:44:36.119 align:start position:0% intranet an Extranet remember the 00:44:36.119 --> 00:44:39.109 align:start position:0% intranet an Extranet remember the internet<00:44:36.300> is<00:44:37.140> that<00:44:37.440> World<00:44:37.800> Wide<00:44:38.220> Web<00:44:38.400> right 00:44:39.109 --> 00:44:39.119 align:start position:0% internet is that World Wide Web right 00:44:39.119 --> 00:44:42.530 align:start position:0% internet is that World Wide Web right the<00:44:39.420> cloud<00:44:39.720> the<00:44:40.560> intranet<00:44:41.280> is<00:44:41.640> sort<00:44:41.880> of<00:44:41.940> using 00:44:42.530 --> 00:44:42.540 align:start position:0% the cloud the intranet is sort of using 00:44:42.540 --> 00:44:45.710 align:start position:0% the cloud the intranet is sort of using this<00:44:43.020> Cloud<00:44:43.319> but<00:44:44.099> in<00:44:44.400> your<00:44:44.640> company 00:44:45.710 --> 00:44:45.720 align:start position:0% this Cloud but in your company 00:44:45.720 --> 00:44:47.690 align:start position:0% this Cloud but in your company and<00:44:46.140> keeping<00:44:46.440> it<00:44:46.619> private<00:44:47.040> that's<00:44:47.339> my<00:44:47.579> little 00:44:47.690 --> 00:44:47.700 align:start position:0% and keeping it private that's my little 00:44:47.700 --> 00:44:51.170 align:start position:0% and keeping it private that's my little building<00:44:47.940> and<00:44:48.780> the<00:44:49.079> Extranet<00:44:49.920> is<00:44:50.579> allowing 00:44:51.170 --> 00:44:51.180 align:start position:0% building and the Extranet is allowing 00:44:51.180 --> 00:44:53.089 align:start position:0% building and the Extranet is allowing access 00:44:53.089 --> 00:44:53.099 align:start position:0% access 00:44:53.099 --> 00:44:56.510 align:start position:0% access of<00:44:53.760> your<00:44:54.060> company<00:44:54.300> private<00:44:55.020> intranet<00:44:55.619> to 00:44:56.510 --> 00:44:56.520 align:start position:0% of your company private intranet to 00:44:56.520 --> 00:44:57.770 align:start position:0% of your company private intranet to perhaps 00:44:57.770 --> 00:44:57.780 align:start position:0% perhaps 00:44:57.780 --> 00:45:00.890 align:start position:0% perhaps certain<00:44:58.380> individuals<00:44:59.160> from<00:44:59.880> outside<00:45:00.240> so<00:45:00.720> it's 00:45:00.890 --> 00:45:00.900 align:start position:0% certain individuals from outside so it's 00:45:00.900 --> 00:45:02.510 align:start position:0% certain individuals from outside so it's just<00:45:01.079> a<00:45:01.260> little<00:45:01.380> bit<00:45:01.619> of<00:45:01.800> that 00:45:02.510 --> 00:45:02.520 align:start position:0% just a little bit of that 00:45:02.520 --> 00:45:04.370 align:start position:0% just a little bit of that we<00:45:02.880> also<00:45:03.119> talked<00:45:03.359> about<00:45:03.359> a<00:45:03.780> centralized 00:45:04.370 --> 00:45:04.380 align:start position:0% we also talked about a centralized 00:45:04.380 --> 00:45:07.210 align:start position:0% we also talked about a centralized Network<00:45:04.619> which<00:45:05.460> is<00:45:05.700> mostly 00:45:07.210 --> 00:45:07.220 align:start position:0% Network which is mostly 00:45:07.220 --> 00:45:09.710 align:start position:0% Network which is mostly what<00:45:08.220> we<00:45:08.339> talk<00:45:08.520> about<00:45:08.700> when<00:45:09.060> we<00:45:09.240> deal<00:45:09.480> with 00:45:09.710 --> 00:45:09.720 align:start position:0% what we talk about when we deal with 00:45:09.720 --> 00:45:11.329 align:start position:0% what we talk about when we deal with terminals 00:45:11.329 --> 00:45:11.339 align:start position:0% terminals 00:45:11.339 --> 00:45:13.970 align:start position:0% terminals and<00:45:11.819> mainframes 00:45:13.970 --> 00:45:13.980 align:start position:0% and mainframes 00:45:13.980 --> 00:45:16.010 align:start position:0% and mainframes and<00:45:14.520> we'll<00:45:14.819> sort<00:45:15.060> of<00:45:15.180> deal<00:45:15.480> with<00:45:15.660> this<00:45:15.900> a 00:45:16.010 --> 00:45:16.020 align:start position:0% and we'll sort of deal with this a 00:45:16.020 --> 00:45:18.710 align:start position:0% and we'll sort of deal with this a little<00:45:16.140> bit<00:45:16.260> too<00:45:16.500> when<00:45:16.740> we<00:45:16.920> get<00:45:17.040> into<00:45:17.720> uh 00:45:18.710 --> 00:45:18.720 align:start position:0% little bit too when we get into uh 00:45:18.720 --> 00:45:20.690 align:start position:0% little bit too when we get into uh virtualization<00:45:19.500> when<00:45:19.859> we<00:45:20.040> talked<00:45:20.280> about<00:45:20.339> Thin 00:45:20.690 --> 00:45:20.700 align:start position:0% virtualization when we talked about Thin 00:45:20.700 --> 00:45:22.550 align:start position:0% virtualization when we talked about Thin and<00:45:20.819> Thick<00:45:21.060> clients<00:45:21.480> this<00:45:21.720> is<00:45:21.839> the<00:45:21.960> idea<00:45:22.200> of<00:45:22.319> a 00:45:22.550 --> 00:45:22.560 align:start position:0% and Thick clients this is the idea of a 00:45:22.560 --> 00:45:25.730 align:start position:0% and Thick clients this is the idea of a thin<00:45:22.859> client<00:45:23.160> on<00:45:24.119> a<00:45:24.300> network<00:45:24.480> with<00:45:24.900> a 00:45:25.730 --> 00:45:25.740 align:start position:0% thin client on a network with a 00:45:25.740 --> 00:45:28.569 align:start position:0% thin client on a network with a a<00:45:26.460> server<00:45:26.940> of<00:45:27.119> some<00:45:27.359> sort<00:45:27.540> or<00:45:27.720> a 00:45:28.569 --> 00:45:28.579 align:start position:0% a server of some sort or a 00:45:28.579 --> 00:45:31.069 align:start position:0% a server of some sort or a Mainframe<00:45:29.579> I<00:45:29.760> should<00:45:29.940> say<00:45:30.119> that<00:45:30.720> is<00:45:30.839> going<00:45:30.960> to 00:45:31.069 --> 00:45:31.079 align:start position:0% Mainframe I should say that is going to 00:45:31.079 --> 00:45:33.170 align:start position:0% Mainframe I should say that is going to do<00:45:31.140> all<00:45:31.380> the<00:45:31.500> processing<00:45:31.980> for<00:45:32.280> it<00:45:32.460> we<00:45:32.940> also 00:45:33.170 --> 00:45:33.180 align:start position:0% do all the processing for it we also 00:45:33.180 --> 00:45:36.050 align:start position:0% do all the processing for it we also looked<00:45:33.480> at<00:45:33.599> a<00:45:33.900> client<00:45:34.619> server<00:45:35.160> Network<00:45:35.339> which 00:45:36.050 --> 00:45:36.060 align:start position:0% looked at a client server Network which 00:45:36.060 --> 00:45:37.849 align:start position:0% looked at a client server Network which is<00:45:36.180> the<00:45:36.420> majority<00:45:36.839> of<00:45:36.960> the<00:45:37.140> types<00:45:37.380> of<00:45:37.500> networks 00:45:37.849 --> 00:45:37.859 align:start position:0% is the majority of the types of networks 00:45:37.859 --> 00:45:40.069 align:start position:0% is the majority of the types of networks we<00:45:37.980> see<00:45:38.160> in<00:45:38.400> Enterprise<00:45:38.640> settings<00:45:39.060> and<00:45:39.900> a 00:45:40.069 --> 00:45:40.079 align:start position:0% we see in Enterprise settings and a 00:45:40.079 --> 00:45:42.650 align:start position:0% we see in Enterprise settings and a peer-to-peer<00:45:40.680> Network<00:45:40.920> which<00:45:41.760> we<00:45:42.119> also<00:45:42.420> call 00:45:42.650 --> 00:45:42.660 align:start position:0% peer-to-peer Network which we also call 00:45:42.660 --> 00:45:46.550 align:start position:0% peer-to-peer Network which we also call a<00:45:42.960> work<00:45:43.380> group<00:45:43.740> network<00:45:44.280> in<00:45:44.760> which<00:45:45.000> every<00:45:45.780> peer 00:45:46.550 --> 00:45:46.560 align:start position:0% a work group network in which every peer 00:45:46.560 --> 00:45:49.069 align:start position:0% a work group network in which every peer is<00:45:47.160> both<00:45:47.400> a<00:45:47.760> client<00:45:48.119> and<00:45:48.599> a<00:45:48.720> server 00:45:49.069 --> 00:45:49.079 align:start position:0% is both a client and a server 00:45:49.079 --> 00:45:51.890 align:start position:0% is both a client and a server responsible<00:45:49.980> for<00:45:50.339> its<00:45:50.819> own 00:45:51.890 --> 00:45:51.900 align:start position:0% responsible for its own 00:45:51.900 --> 00:45:52.670 align:start position:0% responsible for its own um 00:45:52.670 --> 00:45:52.680 align:start position:0% um 00:45:52.680 --> 00:45:55.190 align:start position:0% um its<00:45:53.220> own<00:45:53.339> resources<00:45:53.880> and<00:45:54.119> so<00:45:54.300> on<00:45:54.420> I<00:45:54.839> think<00:45:54.960> we 00:45:55.190 --> 00:45:55.200 align:start position:0% its own resources and so on I think we 00:45:55.200 --> 00:45:57.290 align:start position:0% its own resources and so on I think we use<00:45:55.319> the<00:45:55.500> metaphor<00:45:55.920> that<00:45:56.220> this<00:45:56.520> might<00:45:56.760> be<00:45:56.940> like 00:45:57.290 --> 00:45:57.300 align:start position:0% use the metaphor that this might be like 00:45:57.300 --> 00:45:59.270 align:start position:0% use the metaphor that this might be like uh 00:45:59.270 --> 00:45:59.280 align:start position:0% uh 00:45:59.280 --> 00:46:02.809 align:start position:0% uh communism<00:46:00.200> this<00:46:01.200> might<00:46:01.619> be<00:46:01.920> like<00:46:02.339> a<00:46:02.640> client 00:46:02.809 --> 00:46:02.819 align:start position:0% communism this might be like a client 00:46:02.819 --> 00:46:05.950 align:start position:0% communism this might be like a client server<00:46:03.240> might<00:46:03.540> be<00:46:03.720> like<00:46:04.079> sort<00:46:04.920> of<00:46:05.099> uh 00:46:05.950 --> 00:46:05.960 align:start position:0% server might be like sort of uh 00:46:05.960 --> 00:46:09.410 align:start position:0% server might be like sort of uh democracy<00:46:06.960> of<00:46:07.260> some<00:46:07.500> sort<00:46:07.740> or<00:46:08.520> a<00:46:08.700> republic<00:46:08.880> of 00:46:09.410 --> 00:46:09.420 align:start position:0% democracy of some sort or a republic of 00:46:09.420 --> 00:46:12.650 align:start position:0% democracy of some sort or a republic of some<00:46:09.660> sort<00:46:10.040> and<00:46:11.040> a<00:46:11.579> centralized<00:46:12.240> Network 00:46:12.650 --> 00:46:12.660 align:start position:0% some sort and a centralized Network 00:46:12.660 --> 00:46:16.190 align:start position:0% some sort and a centralized Network would<00:46:13.500> be<00:46:13.740> more<00:46:14.220> like<00:46:14.520> I<00:46:15.180> guess<00:46:15.599> I<00:46:15.780> should<00:46:15.960> say 00:46:16.190 --> 00:46:16.200 align:start position:0% would be more like I guess I should say 00:46:16.200 --> 00:46:19.970 align:start position:0% would be more like I guess I should say a<00:46:16.800> democracy<00:46:17.339> that<00:46:17.640> is<00:46:17.760> also<00:46:18.060> republic<00:46:18.300> since 00:46:19.970 --> 00:46:19.980 align:start position:0% a democracy that is also republic since 00:46:19.980 --> 00:46:22.190 align:start position:0% a democracy that is also republic since um<00:46:20.040> we<00:46:20.880> do<00:46:21.000> have<00:46:21.119> officials<00:46:21.839> and<00:46:22.020> there's 00:46:22.190 --> 00:46:22.200 align:start position:0% um we do have officials and there's 00:46:22.200 --> 00:46:24.470 align:start position:0% um we do have officials and there's someone<00:46:22.380> above<00:46:22.800> us<00:46:22.920> right<00:46:23.220> but<00:46:23.640> a<00:46:24.119> prime 00:46:24.470 --> 00:46:24.480 align:start position:0% someone above us right but a prime 00:46:24.480 --> 00:46:26.569 align:start position:0% someone above us right but a prime minister<00:46:24.839> a<00:46:25.319> president<00:46:25.560> sort<00:46:26.040> of<00:46:26.099> system<00:46:26.280> and 00:46:26.569 --> 00:46:26.579 align:start position:0% minister a president sort of system and 00:46:26.579 --> 00:46:28.250 align:start position:0% minister a president sort of system and then<00:46:26.760> a<00:46:26.880> centralized<00:46:27.359> Network<00:46:27.540> would<00:46:27.900> be<00:46:28.020> like 00:46:28.250 --> 00:46:28.260 align:start position:0% then a centralized Network would be like 00:46:28.260 --> 00:46:29.809 align:start position:0% then a centralized Network would be like a<00:46:28.440> tyranny 00:46:29.809 --> 00:46:29.819 align:start position:0% a tyranny 00:46:29.819 --> 00:46:33.050 align:start position:0% a tyranny or<00:46:30.480> a<00:46:30.720> tyrannical<00:46:31.380> Monarch<00:46:31.980> I<00:46:32.099> should<00:46:32.280> say<00:46:32.460> and 00:46:33.050 --> 00:46:33.060 align:start position:0% or a tyrannical Monarch I should say and 00:46:33.060 --> 00:46:34.790 align:start position:0% or a tyrannical Monarch I should say and then<00:46:33.119> we<00:46:33.300> have<00:46:33.480> a<00:46:33.720> mixed<00:46:33.960> mode<00:46:34.079> Network<00:46:34.440> which 00:46:34.790 --> 00:46:34.800 align:start position:0% then we have a mixed mode Network which 00:46:34.800 --> 00:46:38.569 align:start position:0% then we have a mixed mode Network which is<00:46:34.920> sort<00:46:35.160> of<00:46:35.280> a<00:46:35.579> combination<00:46:36.119> of<00:46:37.079> uh<00:46:37.380> the<00:46:37.619> above 00:46:38.569 --> 00:46:38.579 align:start position:0% is sort of a combination of uh the above 00:46:38.579 --> 00:46:40.069 align:start position:0% is sort of a combination of uh the above great 00:46:40.069 --> 00:46:40.079 align:start position:0% great 00:46:40.079 --> 00:46:43.309 align:start position:0% great so<00:46:40.680> we've<00:46:41.099> talked<00:46:41.400> now<00:46:41.579> about<00:46:41.880> uh<00:46:42.720> some<00:46:43.079> of<00:46:43.200> the 00:46:43.309 --> 00:46:43.319 align:start position:0% so we've talked now about uh some of the 00:46:43.319 --> 00:46:45.710 align:start position:0% so we've talked now about uh some of the basic<00:46:43.859> terminology<00:46:44.339> we've<00:46:45.060> talked<00:46:45.359> about<00:46:45.420> the 00:46:45.710 --> 00:46:45.720 align:start position:0% basic terminology we've talked about the 00:46:45.720 --> 00:46:48.109 align:start position:0% basic terminology we've talked about the models<00:46:46.140> we've<00:46:46.740> also<00:46:47.099> talked<00:46:47.400> about<00:46:47.640> the 00:46:48.109 --> 00:46:48.119 align:start position:0% models we've also talked about the 00:46:48.119 --> 00:46:51.109 align:start position:0% models we've also talked about the different<00:46:48.380> categories<00:46:49.380> so<00:46:50.280> let's<00:46:50.579> finish<00:46:50.760> up 00:46:51.109 --> 00:46:51.119 align:start position:0% different categories so let's finish up 00:46:51.119 --> 00:46:53.270 align:start position:0% different categories so let's finish up this<00:46:51.540> basic<00:46:51.960> Network<00:46:52.140> fundamentals<00:46:52.859> area<00:46:53.040> by 00:46:53.270 --> 00:46:53.280 align:start position:0% this basic Network fundamentals area by 00:46:53.280 --> 00:46:54.710 align:start position:0% this basic Network fundamentals area by talking<00:46:53.520> about<00:46:53.700> what<00:46:54.060> are<00:46:54.180> what<00:46:54.420> are<00:46:54.540> called 00:46:54.710 --> 00:46:54.720 align:start position:0% talking about what are what are called 00:46:54.720 --> 00:46:56.690 align:start position:0% talking about what are what are called topologies<00:46:55.619> how<00:46:56.099> the<00:46:56.220> networks<00:46:56.579> are 00:46:56.690 --> 00:46:56.700 align:start position:0% topologies how the networks are 00:46:56.700 --> 00:46:58.550 align:start position:0% topologies how the networks are physically<00:46:57.060> set<00:46:57.240> up<00:46:57.420> and<00:46:57.660> how<00:46:57.839> they<00:46:58.079> logically 00:46:58.550 --> 00:46:58.560 align:start position:0% physically set up and how they logically 00:46:58.560 --> 00:47:03.380 align:start position:0% physically set up and how they logically communicate<00:46:59.220> with<00:46:59.339> one<00:46:59.520> another 00:47:03.380 --> 00:47:03.390 align:start position:0% 00:47:03.390 --> 00:47:11.950 align:start position:0% [Music] 00:47:11.950 --> 00:47:11.960 align:start position:0% [Music] 00:47:11.960 --> 00:47:28.490 align:start position:0% [Music] thank<00:47:12.960> you 00:47:28.490 --> 00:47:28.500 align:start position:0% 00:47:28.500 --> 00:47:33.170 align:start position:0% Network<00:47:28.980> fundamentals<00:47:29.940> Network<00:47:30.780> topologies 00:47:33.170 --> 00:47:33.180 align:start position:0% Network fundamentals Network topologies 00:47:33.180 --> 00:47:35.230 align:start position:0% Network fundamentals Network topologies so<00:47:33.720> now<00:47:33.839> we're<00:47:34.020> going<00:47:34.200> to<00:47:34.260> explain<00:47:34.500> Network 00:47:35.230 --> 00:47:35.240 align:start position:0% so now we're going to explain Network 00:47:35.240 --> 00:47:39.349 align:start position:0% so now we're going to explain Network topologies<00:47:36.240> or<00:47:36.900> uh<00:47:37.740> the<00:47:38.099> network<00:47:38.280> layout<00:47:39.000> both 00:47:39.349 --> 00:47:39.359 align:start position:0% topologies or uh the network layout both 00:47:39.359 --> 00:47:42.050 align:start position:0% topologies or uh the network layout both physical<00:47:39.720> and<00:47:40.560> logical<00:47:40.980> physical<00:47:41.400> being<00:47:41.700> how 00:47:42.050 --> 00:47:42.060 align:start position:0% physical and logical physical being how 00:47:42.060 --> 00:47:44.210 align:start position:0% physical and logical physical being how it's<00:47:42.180> physically<00:47:42.540> connected<00:47:42.960> and<00:47:43.800> logical 00:47:44.210 --> 00:47:44.220 align:start position:0% it's physically connected and logical 00:47:44.220 --> 00:47:45.890 align:start position:0% it's physically connected and logical being<00:47:44.579> how<00:47:44.819> the<00:47:45.000> information<00:47:45.180> is 00:47:45.890 --> 00:47:45.900 align:start position:0% being how the information is 00:47:45.900 --> 00:47:47.569 align:start position:0% being how the information is communicated<00:47:46.440> over<00:47:46.800> that<00:47:47.040> physical<00:47:47.220> Network 00:47:47.569 --> 00:47:47.579 align:start position:0% communicated over that physical Network 00:47:47.579 --> 00:47:49.250 align:start position:0% communicated over that physical Network and<00:47:48.180> we're<00:47:48.300> going<00:47:48.420> to<00:47:48.480> define<00:47:48.599> the<00:47:48.960> different 00:47:49.250 --> 00:47:49.260 align:start position:0% and we're going to define the different 00:47:49.260 --> 00:47:51.410 align:start position:0% and we're going to define the different standard<00:47:49.800> topologies<00:47:50.460> that<00:47:50.700> are<00:47:50.819> in<00:47:51.000> use<00:47:51.119> for 00:47:51.410 --> 00:47:51.420 align:start position:0% standard topologies that are in use for 00:47:51.420 --> 00:47:52.370 align:start position:0% standard topologies that are in use for today 00:47:52.370 --> 00:47:52.380 align:start position:0% today 00:47:52.380 --> 00:47:54.650 align:start position:0% today so<00:47:53.099> uh<00:47:53.700> we're<00:47:54.000> first<00:47:54.180> going<00:47:54.359> to<00:47:54.480> Define 00:47:54.650 --> 00:47:54.660 align:start position:0% so uh we're first going to Define 00:47:54.660 --> 00:47:56.630 align:start position:0% so uh we're first going to Define topology<00:47:55.380> in<00:47:55.800> general 00:47:56.630 --> 00:47:56.640 align:start position:0% topology in general 00:47:56.640 --> 00:47:58.250 align:start position:0% topology in general then<00:47:57.000> we're<00:47:57.119> going<00:47:57.300> to<00:47:57.359> talk<00:47:57.540> about<00:47:57.720> physical 00:47:58.250 --> 00:47:58.260 align:start position:0% then we're going to talk about physical 00:47:58.260 --> 00:48:02.150 align:start position:0% then we're going to talk about physical topology<00:47:58.920> followed<00:47:59.880> by<00:48:00.060> logical<00:48:00.780> topology 00:48:02.150 --> 00:48:02.160 align:start position:0% topology followed by logical topology 00:48:02.160 --> 00:48:04.010 align:start position:0% topology followed by logical topology we're<00:48:02.579> then<00:48:02.760> going<00:48:02.940> to<00:48:03.060> explain<00:48:03.180> a<00:48:03.480> few<00:48:03.599> of<00:48:03.780> the 00:48:04.010 --> 00:48:04.020 align:start position:0% we're then going to explain a few of the 00:48:04.020 --> 00:48:05.510 align:start position:0% we're then going to explain a few of the different<00:48:04.200> types<00:48:04.619> of<00:48:04.740> topologies<00:48:05.280> you<00:48:05.400> need 00:48:05.510 --> 00:48:05.520 align:start position:0% different types of topologies you need 00:48:05.520 --> 00:48:06.890 align:start position:0% different types of topologies you need to<00:48:05.640> be<00:48:05.760> familiar<00:48:06.060> with<00:48:06.180> for<00:48:06.480> the<00:48:06.599> exam 00:48:06.890 --> 00:48:06.900 align:start position:0% to be familiar with for the exam 00:48:06.900 --> 00:48:09.829 align:start position:0% to be familiar with for the exam including<00:48:07.680> a<00:48:07.859> bus<00:48:08.099> topology 00:48:09.829 --> 00:48:09.839 align:start position:0% including a bus topology 00:48:09.839 --> 00:48:11.809 align:start position:0% including a bus topology star<00:48:10.500> topology 00:48:11.809 --> 00:48:11.819 align:start position:0% star topology 00:48:11.819 --> 00:48:14.270 align:start position:0% star topology a<00:48:12.480> ring<00:48:12.720> topology 00:48:14.270 --> 00:48:14.280 align:start position:0% a ring topology 00:48:14.280 --> 00:48:16.609 align:start position:0% a ring topology a<00:48:14.880> tree<00:48:15.000> topology 00:48:16.609 --> 00:48:16.619 align:start position:0% a tree topology 00:48:16.619 --> 00:48:19.190 align:start position:0% a tree topology and<00:48:17.040> a<00:48:17.160> mesh<00:48:17.460> topology<00:48:17.819> we're<00:48:18.660> also<00:48:18.960> going<00:48:19.020> to 00:48:19.190 --> 00:48:19.200 align:start position:0% and a mesh topology we're also going to 00:48:19.200 --> 00:48:21.170 align:start position:0% and a mesh topology we're also going to talk<00:48:19.319> about<00:48:19.619> a<00:48:20.099> mixture<00:48:20.460> of<00:48:20.700> all<00:48:20.940> of<00:48:21.000> these 00:48:21.170 --> 00:48:21.180 align:start position:0% talk about a mixture of all of these 00:48:21.180 --> 00:48:24.050 align:start position:0% talk about a mixture of all of these topologies<00:48:21.859> that<00:48:22.859> is<00:48:22.980> called 00:48:24.050 --> 00:48:24.060 align:start position:0% topologies that is called 00:48:24.060 --> 00:48:26.390 align:start position:0% topologies that is called a<00:48:24.540> hybrid<00:48:24.839> topology 00:48:26.390 --> 00:48:26.400 align:start position:0% a hybrid topology 00:48:26.400 --> 00:48:27.770 align:start position:0% a hybrid topology these<00:48:26.819> are<00:48:26.880> the<00:48:27.060> things<00:48:27.180> you<00:48:27.359> really<00:48:27.480> want<00:48:27.660> to 00:48:27.770 --> 00:48:27.780 align:start position:0% these are the things you really want to 00:48:27.780 --> 00:48:29.210 align:start position:0% these are the things you really want to pay<00:48:27.900> attention<00:48:28.140> to<00:48:28.380> these<00:48:28.800> different<00:48:28.920> names 00:48:29.210 --> 00:48:29.220 align:start position:0% pay attention to these different names 00:48:29.220 --> 00:48:32.270 align:start position:0% pay attention to these different names and<00:48:29.819> the<00:48:30.000> names<00:48:30.180> correspond<00:48:30.839> directly<00:48:31.319> to<00:48:32.040> how 00:48:32.270 --> 00:48:32.280 align:start position:0% and the names correspond directly to how 00:48:32.280 --> 00:48:33.650 align:start position:0% and the names correspond directly to how everything<00:48:32.520> is<00:48:32.760> set<00:48:32.940> up<00:48:33.060> so<00:48:33.300> I<00:48:33.480> don't<00:48:33.540> think 00:48:33.650 --> 00:48:33.660 align:start position:0% everything is set up so I don't think 00:48:33.660 --> 00:48:36.710 align:start position:0% everything is set up so I don't think it'll<00:48:33.900> be<00:48:34.020> too<00:48:34.140> hard<00:48:34.380> for<00:48:34.619> you<00:48:34.800> to<00:48:35.220> remember<00:48:36.180> or 00:48:36.710 --> 00:48:36.720 align:start position:0% it'll be too hard for you to remember or 00:48:36.720 --> 00:48:40.010 align:start position:0% it'll be too hard for you to remember or to<00:48:36.960> memorize 00:48:40.010 --> 00:48:40.020 align:start position:0% 00:48:40.020 --> 00:48:43.430 align:start position:0% so<00:48:40.680> as<00:48:41.040> administrators<00:48:41.940> regardless<00:48:42.839> of<00:48:43.200> the 00:48:43.430 --> 00:48:43.440 align:start position:0% so as administrators regardless of the 00:48:43.440 --> 00:48:45.410 align:start position:0% so as administrators regardless of the specific<00:48:43.680> role<00:48:44.099> we're<00:48:44.220> in<00:48:44.400> we<00:48:44.880> have<00:48:45.000> to<00:48:45.119> have<00:48:45.240> a 00:48:45.410 --> 00:48:45.420 align:start position:0% specific role we're in we have to have a 00:48:45.420 --> 00:48:47.569 align:start position:0% specific role we're in we have to have a complete<00:48:45.720> understanding<00:48:46.200> of<00:48:46.500> the<00:48:46.859> layout<00:48:47.220> or 00:48:47.569 --> 00:48:47.579 align:start position:0% complete understanding of the layout or 00:48:47.579 --> 00:48:50.089 align:start position:0% complete understanding of the layout or the<00:48:47.819> arrangement<00:48:48.480> of<00:48:48.900> the<00:48:49.079> network<00:48:49.260> this 00:48:50.089 --> 00:48:50.099 align:start position:0% the arrangement of the network this 00:48:50.099 --> 00:48:52.910 align:start position:0% the arrangement of the network this allows<00:48:50.460> us<00:48:50.579> to<00:48:51.000> effectively<00:48:51.660> design<00:48:52.079> manage 00:48:52.910 --> 00:48:52.920 align:start position:0% allows us to effectively design manage 00:48:52.920 --> 00:48:55.450 align:start position:0% allows us to effectively design manage and<00:48:53.640> troubleshoot<00:48:54.240> the<00:48:54.420> networks<00:48:54.839> for 00:48:55.450 --> 00:48:55.460 align:start position:0% and troubleshoot the networks for 00:48:55.460 --> 00:48:58.309 align:start position:0% and troubleshoot the networks for performance<00:48:56.460> and<00:48:57.000> scalability<00:48:57.599> a 00:48:58.309 --> 00:48:58.319 align:start position:0% performance and scalability a 00:48:58.319 --> 00:49:00.650 align:start position:0% performance and scalability a scalability<00:48:58.920> by<00:48:59.280> the<00:48:59.460> way<00:48:59.579> I'm<00:49:00.300> just<00:49:00.480> going<00:49:00.599> to 00:49:00.650 --> 00:49:00.660 align:start position:0% scalability by the way I'm just going to 00:49:00.660 --> 00:49:02.569 align:start position:0% scalability by the way I'm just going to write<00:49:00.780> that<00:49:01.020> out<00:49:01.200> here 00:49:02.569 --> 00:49:02.579 align:start position:0% write that out here 00:49:02.579 --> 00:49:04.370 align:start position:0% write that out here because<00:49:03.000> it<00:49:03.240> is<00:49:03.359> a<00:49:03.480> term<00:49:03.599> we'll<00:49:03.780> see<00:49:03.960> come<00:49:04.200> up 00:49:04.370 --> 00:49:04.380 align:start position:0% because it is a term we'll see come up 00:49:04.380 --> 00:49:07.190 align:start position:0% because it is a term we'll see come up over<00:49:04.619> and<00:49:04.800> over<00:49:04.980> again<00:49:05.160> is 00:49:07.190 --> 00:49:07.200 align:start position:0% over and over again is 00:49:07.200 --> 00:49:08.329 align:start position:0% over and over again is um 00:49:08.329 --> 00:49:08.339 align:start position:0% um 00:49:08.339 --> 00:49:10.550 align:start position:0% um how<00:49:08.940> you<00:49:09.180> can<00:49:09.359> either<00:49:09.960> make<00:49:10.200> the<00:49:10.380> network 00:49:10.550 --> 00:49:10.560 align:start position:0% how you can either make the network 00:49:10.560 --> 00:49:14.089 align:start position:0% how you can either make the network larger<00:49:11.220> or<00:49:11.579> smaller<00:49:11.880> depending<00:49:12.300> on<00:49:12.480> needs 00:49:14.089 --> 00:49:14.099 align:start position:0% larger or smaller depending on needs 00:49:14.099 --> 00:49:17.089 align:start position:0% larger or smaller depending on needs certain<00:49:14.520> topologies<00:49:15.420> have<00:49:16.099> characteristics 00:49:17.089 --> 00:49:17.099 align:start position:0% certain topologies have characteristics 00:49:17.099 --> 00:49:19.490 align:start position:0% certain topologies have characteristics that<00:49:17.940> allow<00:49:18.240> us<00:49:18.359> to<00:49:18.599> have<00:49:18.780> more<00:49:19.079> efficient 00:49:19.490 --> 00:49:19.500 align:start position:0% that allow us to have more efficient 00:49:19.500 --> 00:49:21.650 align:start position:0% that allow us to have more efficient communication<00:49:20.160> while<00:49:20.760> other<00:49:20.940> topologies 00:49:21.650 --> 00:49:21.660 align:start position:0% communication while other topologies 00:49:21.660 --> 00:49:23.930 align:start position:0% communication while other topologies focus<00:49:22.200> more<00:49:22.380> on<00:49:22.619> immediate<00:49:23.339> or<00:49:23.700> faster 00:49:23.930 --> 00:49:23.940 align:start position:0% focus more on immediate or faster 00:49:23.940 --> 00:49:27.109 align:start position:0% focus more on immediate or faster communication<00:49:24.660> between<00:49:25.260> certain<00:49:25.680> devices<00:49:26.119> so 00:49:27.109 --> 00:49:27.119 align:start position:0% communication between certain devices so 00:49:27.119 --> 00:49:29.750 align:start position:0% communication between certain devices so understanding<00:49:27.839> the<00:49:28.079> topology<00:49:28.619> of<00:49:29.579> the 00:49:29.750 --> 00:49:29.760 align:start position:0% understanding the topology of the 00:49:29.760 --> 00:49:32.450 align:start position:0% understanding the topology of the network<00:49:29.940> allows<00:49:30.839> us<00:49:31.200> administrators<00:49:32.040> to 00:49:32.450 --> 00:49:32.460 align:start position:0% network allows us administrators to 00:49:32.460 --> 00:49:34.309 align:start position:0% network allows us administrators to troubleshoot<00:49:33.119> the<00:49:33.480> problems<00:49:33.839> we're<00:49:34.079> having 00:49:34.309 --> 00:49:34.319 align:start position:0% troubleshoot the problems we're having 00:49:34.319 --> 00:49:37.970 align:start position:0% troubleshoot the problems we're having and<00:49:35.099> then<00:49:35.220> Implement<00:49:35.700> Solutions<00:49:36.500> easier<00:49:37.500> and 00:49:37.970 --> 00:49:37.980 align:start position:0% and then Implement Solutions easier and 00:49:37.980 --> 00:49:39.770 align:start position:0% and then Implement Solutions easier and more<00:49:38.460> efficiently 00:49:39.770 --> 00:49:39.780 align:start position:0% more efficiently 00:49:39.780 --> 00:49:43.130 align:start position:0% more efficiently so<00:49:40.319> there<00:49:40.619> are<00:49:40.800> two<00:49:41.160> types<00:49:41.640> of<00:49:41.819> topologies<00:49:42.660> in 00:49:43.130 --> 00:49:43.140 align:start position:0% so there are two types of topologies in 00:49:43.140 --> 00:49:44.750 align:start position:0% so there are two types of topologies in general<00:49:43.319> and<00:49:43.920> then<00:49:44.099> there<00:49:44.280> are<00:49:44.460> specific 00:49:44.750 --> 00:49:44.760 align:start position:0% general and then there are specific 00:49:44.760 --> 00:49:46.550 align:start position:0% general and then there are specific names<00:49:45.060> for<00:49:45.300> each<00:49:45.420> of<00:49:45.540> those<00:49:45.599> topologies<00:49:46.200> but 00:49:46.550 --> 00:49:46.560 align:start position:0% names for each of those topologies but 00:49:46.560 --> 00:49:48.829 align:start position:0% names for each of those topologies but the<00:49:46.680> two<00:49:46.800> types<00:49:47.160> are<00:49:47.460> physical<00:49:47.700> and<00:49:48.480> logical 00:49:48.829 --> 00:49:48.839 align:start position:0% the two types are physical and logical 00:49:48.839 --> 00:49:50.990 align:start position:0% the two types are physical and logical so<00:49:49.560> uh<00:49:49.740> let's<00:49:49.980> take<00:49:50.160> a<00:49:50.339> look<00:49:50.460> at<00:49:50.819> the 00:49:50.990 --> 00:49:51.000 align:start position:0% so uh let's take a look at the 00:49:51.000 --> 00:49:52.790 align:start position:0% so uh let's take a look at the characteristics<00:49:51.599> that<00:49:52.020> define<00:49:52.200> a<00:49:52.680> physical 00:49:52.790 --> 00:49:52.800 align:start position:0% characteristics that define a physical 00:49:52.800 --> 00:49:58.190 align:start position:0% characteristics that define a physical topology<00:49:53.339> and<00:49:53.880> a<00:49:54.000> logical<00:49:54.300> topology 00:49:58.190 --> 00:49:58.200 align:start position:0% 00:49:58.200 --> 00:50:00.770 align:start position:0% Google<00:49:58.380> topology<00:49:58.980> is<00:49:59.400> the<00:49:59.760> actual<00:50:00.240> physical 00:50:00.770 --> 00:50:00.780 align:start position:0% Google topology is the actual physical 00:50:00.780 --> 00:50:04.550 align:start position:0% Google topology is the actual physical layout<00:50:01.500> of<00:50:02.160> the<00:50:02.280> devices<00:50:02.599> so<00:50:03.599> this<00:50:03.839> is<00:50:04.140> like 00:50:04.550 --> 00:50:04.560 align:start position:0% layout of the devices so this is like 00:50:04.560 --> 00:50:06.890 align:start position:0% layout of the devices so this is like looking<00:50:04.800> at<00:50:05.099> the<00:50:05.400> blueprint<00:50:05.940> of<00:50:06.540> our<00:50:06.660> Network 00:50:06.890 --> 00:50:06.900 align:start position:0% looking at the blueprint of our Network 00:50:06.900 --> 00:50:09.290 align:start position:0% looking at the blueprint of our Network this<00:50:07.619> tells<00:50:07.920> us<00:50:07.980> how<00:50:08.220> the<00:50:08.400> devices<00:50:08.760> are 00:50:09.290 --> 00:50:09.300 align:start position:0% this tells us how the devices are 00:50:09.300 --> 00:50:11.930 align:start position:0% this tells us how the devices are actually<00:50:09.599> physically<00:50:10.579> connected<00:50:11.579> to<00:50:11.760> one 00:50:11.930 --> 00:50:11.940 align:start position:0% actually physically connected to one 00:50:11.940 --> 00:50:14.089 align:start position:0% actually physically connected to one another<00:50:12.119> it's<00:50:12.900> also<00:50:13.200> the<00:50:13.440> shape<00:50:13.740> of<00:50:13.920> the 00:50:14.089 --> 00:50:14.099 align:start position:0% another it's also the shape of the 00:50:14.099 --> 00:50:15.470 align:start position:0% another it's also the shape of the network<00:50:14.220> and<00:50:14.579> it<00:50:14.700> gives<00:50:14.819> us<00:50:14.940> a<00:50:15.180> sort<00:50:15.359> of 00:50:15.470 --> 00:50:15.480 align:start position:0% network and it gives us a sort of 00:50:15.480 --> 00:50:19.010 align:start position:0% network and it gives us a sort of picture<00:50:16.319> to<00:50:16.740> represent<00:50:17.099> the<00:50:17.460> layout<00:50:17.819> or<00:50:18.599> the 00:50:19.010 --> 00:50:19.020 align:start position:0% picture to represent the layout or the 00:50:19.020 --> 00:50:22.910 align:start position:0% picture to represent the layout or the blueprint<00:50:19.819> the<00:50:20.819> physical<00:50:21.000> topology<00:50:21.920> ensures 00:50:22.910 --> 00:50:22.920 align:start position:0% blueprint the physical topology ensures 00:50:22.920 --> 00:50:25.130 align:start position:0% blueprint the physical topology ensures that<00:50:23.280> we<00:50:23.460> administrators<00:50:24.300> know<00:50:24.900> and 00:50:25.130 --> 00:50:25.140 align:start position:0% that we administrators know and 00:50:25.140 --> 00:50:27.770 align:start position:0% that we administrators know and understand<00:50:25.380> how<00:50:26.040> the<00:50:26.220> physical<00:50:26.400> media<00:50:27.180> like 00:50:27.770 --> 00:50:27.780 align:start position:0% understand how the physical media like 00:50:27.780 --> 00:50:30.170 align:start position:0% understand how the physical media like cables<00:50:28.380> connect<00:50:28.980> the<00:50:29.339> devices<00:50:29.640> to<00:50:30.000> one 00:50:30.170 --> 00:50:30.180 align:start position:0% cables connect the devices to one 00:50:30.180 --> 00:50:31.309 align:start position:0% cables connect the devices to one another 00:50:31.309 --> 00:50:31.319 align:start position:0% another 00:50:31.319 --> 00:50:34.670 align:start position:0% another so<00:50:32.099> a<00:50:32.880> logical<00:50:33.359> topology<00:50:33.839> on<00:50:34.260> the<00:50:34.380> other<00:50:34.500> hand 00:50:34.670 --> 00:50:34.680 align:start position:0% so a logical topology on the other hand 00:50:34.680 --> 00:50:37.790 align:start position:0% so a logical topology on the other hand describes<00:50:35.520> the<00:50:36.300> how<00:50:36.480> in<00:50:37.079> other<00:50:37.140> words<00:50:37.319> it's 00:50:37.790 --> 00:50:37.800 align:start position:0% describes the how in other words it's 00:50:37.800 --> 00:50:40.790 align:start position:0% describes the how in other words it's the<00:50:38.099> pathway<00:50:38.579> that<00:50:39.359> data<00:50:39.839> takes<00:50:40.079> regardless 00:50:40.790 --> 00:50:40.800 align:start position:0% the pathway that data takes regardless 00:50:40.800 --> 00:50:43.309 align:start position:0% the pathway that data takes regardless of<00:50:41.099> how<00:50:41.339> the<00:50:41.579> network<00:50:41.940> is<00:50:42.480> physically<00:50:42.960> laid 00:50:43.309 --> 00:50:43.319 align:start position:0% of how the network is physically laid 00:50:43.319 --> 00:50:46.190 align:start position:0% of how the network is physically laid out<00:50:43.440> this<00:50:44.040> is<00:50:44.099> how<00:50:44.400> the<00:50:44.880> data<00:50:45.599> is<00:50:45.900> actually 00:50:46.190 --> 00:50:46.200 align:start position:0% out this is how the data is actually 00:50:46.200 --> 00:50:49.069 align:start position:0% out this is how the data is actually communicated<00:50:47.099> over<00:50:47.700> the<00:50:48.059> physical 00:50:49.069 --> 00:50:49.079 align:start position:0% communicated over the physical 00:50:49.079 --> 00:50:51.170 align:start position:0% communicated over the physical so<00:50:49.559> the<00:50:49.859> logical<00:50:50.220> topology<00:50:50.700> allows 00:50:51.170 --> 00:50:51.180 align:start position:0% so the logical topology allows 00:50:51.180 --> 00:50:54.710 align:start position:0% so the logical topology allows administrators<00:50:51.839> to<00:50:52.260> troubleshoot<00:50:53.040> and 00:50:54.710 --> 00:50:54.720 align:start position:0% administrators to troubleshoot and 00:50:54.720 --> 00:50:57.109 align:start position:0% administrators to troubleshoot and fix<00:50:55.200> the<00:50:55.680> problems<00:50:56.160> we're<00:50:56.339> having<00:50:56.579> with 00:50:57.109 --> 00:50:57.119 align:start position:0% fix the problems we're having with 00:50:57.119 --> 00:51:00.170 align:start position:0% fix the problems we're having with communication<00:50:57.780> between<00:50:58.319> devices<00:50:59.180> by 00:51:00.170 --> 00:51:00.180 align:start position:0% communication between devices by 00:51:00.180 --> 00:51:03.349 align:start position:0% communication between devices by understanding<00:51:01.020> the<00:51:01.920> path<00:51:02.160> that<00:51:02.579> the<00:51:02.760> data<00:51:03.059> is 00:51:03.349 --> 00:51:03.359 align:start position:0% understanding the path that the data is 00:51:03.359 --> 00:51:05.390 align:start position:0% understanding the path that the data is actually<00:51:03.660> taking<00:51:04.079> and<00:51:04.619> we'll<00:51:04.980> see<00:51:05.280> some 00:51:05.390 --> 00:51:05.400 align:start position:0% actually taking and we'll see some 00:51:05.400 --> 00:51:07.010 align:start position:0% actually taking and we'll see some pictures<00:51:05.579> of<00:51:05.880> this<00:51:06.000> in<00:51:06.240> just<00:51:06.359> a<00:51:06.480> second<00:51:06.660> so 00:51:07.010 --> 00:51:07.020 align:start position:0% pictures of this in just a second so 00:51:07.020 --> 00:51:09.430 align:start position:0% pictures of this in just a second so that<00:51:07.260> will<00:51:07.440> make<00:51:08.339> this<00:51:08.520> all<00:51:08.760> a<00:51:08.880> lot<00:51:09.000> more<00:51:09.180> clear 00:51:09.430 --> 00:51:09.440 align:start position:0% that will make this all a lot more clear 00:51:09.440 --> 00:51:13.849 align:start position:0% that will make this all a lot more clear in<00:51:10.440> a<00:51:10.559> lot<00:51:10.619> of<00:51:10.800> cases<00:51:11.160> the<00:51:11.760> logical<00:51:12.300> topology 00:51:13.849 --> 00:51:13.859 align:start position:0% in a lot of cases the logical topology 00:51:13.859 --> 00:51:15.650 align:start position:0% in a lot of cases the logical topology could<00:51:14.460> be<00:51:14.640> very<00:51:14.880> different<00:51:15.180> from<00:51:15.540> the 00:51:15.650 --> 00:51:15.660 align:start position:0% could be very different from the 00:51:15.660 --> 00:51:17.089 align:start position:0% could be very different from the physical<00:51:15.839> topology 00:51:17.089 --> 00:51:17.099 align:start position:0% physical topology 00:51:17.099 --> 00:51:19.549 align:start position:0% physical topology so<00:51:17.700> only<00:51:18.000> because<00:51:18.240> one<00:51:18.599> logical<00:51:18.900> topology<00:51:19.260> is 00:51:19.549 --> 00:51:19.559 align:start position:0% so only because one logical topology is 00:51:19.559 --> 00:51:21.109 align:start position:0% so only because one logical topology is for<00:51:19.740> instance<00:51:19.920> the<00:51:20.160> star<00:51:20.400> doesn't<00:51:20.700> mean<00:51:20.940> the 00:51:21.109 --> 00:51:21.119 align:start position:0% for instance the star doesn't mean the 00:51:21.119 --> 00:51:22.670 align:start position:0% for instance the star doesn't mean the physical<00:51:21.300> topology<00:51:21.839> is<00:51:22.020> also<00:51:22.319> going<00:51:22.380> to<00:51:22.440> be<00:51:22.559> a 00:51:22.670 --> 00:51:22.680 align:start position:0% physical topology is also going to be a 00:51:22.680 --> 00:51:25.730 align:start position:0% physical topology is also going to be a star<00:51:22.800> you<00:51:23.339> can<00:51:23.520> have<00:51:23.640> a<00:51:23.819> physical<00:51:24.000> star<00:51:24.540> and<00:51:25.440> a 00:51:25.730 --> 00:51:25.740 align:start position:0% star you can have a physical star and a 00:51:25.740 --> 00:51:27.770 align:start position:0% star you can have a physical star and a logical<00:51:26.099> bus<00:51:26.460> so<00:51:27.000> that's<00:51:27.119> why<00:51:27.359> it's<00:51:27.480> important 00:51:27.770 --> 00:51:27.780 align:start position:0% logical bus so that's why it's important 00:51:27.780 --> 00:51:29.270 align:start position:0% logical bus so that's why it's important we<00:51:27.900> understand<00:51:28.140> but<00:51:28.559> the<00:51:28.800> difference<00:51:28.980> between 00:51:29.270 --> 00:51:29.280 align:start position:0% we understand but the difference between 00:51:29.280 --> 00:51:30.770 align:start position:0% we understand but the difference between logical<00:51:29.760> and<00:51:30.000> physical 00:51:30.770 --> 00:51:30.780 align:start position:0% logical and physical 00:51:30.780 --> 00:51:32.390 align:start position:0% logical and physical so<00:51:31.200> now<00:51:31.380> that<00:51:31.559> we've<00:51:31.740> defined<00:51:32.099> the<00:51:32.280> difference 00:51:32.390 --> 00:51:32.400 align:start position:0% so now that we've defined the difference 00:51:32.400 --> 00:51:34.849 align:start position:0% so now that we've defined the difference in<00:51:32.640> a<00:51:32.880> physical<00:51:33.000> and<00:51:33.359> a<00:51:33.540> logical<00:51:33.839> topology<00:51:34.319> I 00:51:34.849 --> 00:51:34.859 align:start position:0% in a physical and a logical topology I 00:51:34.859 --> 00:51:36.109 align:start position:0% in a physical and a logical topology I want<00:51:34.980> to<00:51:35.099> look<00:51:35.160> at<00:51:35.280> some<00:51:35.520> of<00:51:35.640> the<00:51:35.880> different 00:51:36.109 --> 00:51:36.119 align:start position:0% want to look at some of the different 00:51:36.119 --> 00:51:38.569 align:start position:0% want to look at some of the different connection<00:51:36.480> methods<00:51:37.200> that<00:51:37.680> we<00:51:37.859> use<00:51:38.040> in<00:51:38.339> these 00:51:38.569 --> 00:51:38.579 align:start position:0% connection methods that we use in these 00:51:38.579 --> 00:51:40.730 align:start position:0% connection methods that we use in these topologies<00:51:39.119> in<00:51:39.300> the<00:51:39.480> specific<00:51:39.720> layouts<00:51:40.380> both 00:51:40.730 --> 00:51:40.740 align:start position:0% topologies in the specific layouts both 00:51:40.740 --> 00:51:43.549 align:start position:0% topologies in the specific layouts both for<00:51:41.040> physical<00:51:41.220> and<00:51:41.640> logical<00:51:42.200> uh<00:51:43.200> but<00:51:43.440> first 00:51:43.549 --> 00:51:43.559 align:start position:0% for physical and logical uh but first 00:51:43.559 --> 00:51:45.170 align:start position:0% for physical and logical uh but first let's<00:51:43.800> talk<00:51:44.040> about<00:51:44.220> how<00:51:44.700> these<00:51:45.059> things 00:51:45.170 --> 00:51:45.180 align:start position:0% let's talk about how these things 00:51:45.180 --> 00:51:46.730 align:start position:0% let's talk about how these things connect<00:51:45.420> because<00:51:46.020> that's<00:51:46.260> going<00:51:46.440> to<00:51:46.619> keep 00:51:46.730 --> 00:51:46.740 align:start position:0% connect because that's going to keep 00:51:46.740 --> 00:51:48.650 align:start position:0% connect because that's going to keep coming<00:51:46.980> back<00:51:47.280> up 00:51:48.650 --> 00:51:48.660 align:start position:0% coming back up 00:51:48.660 --> 00:51:51.290 align:start position:0% coming back up so<00:51:49.319> the<00:51:49.740> first<00:51:49.920> type<00:51:50.280> we<00:51:50.520> have<00:51:50.640> is<00:51:50.819> called<00:51:51.000> a 00:51:51.290 --> 00:51:51.300 align:start position:0% so the first type we have is called a 00:51:51.300 --> 00:51:54.410 align:start position:0% so the first type we have is called a point-to-point<00:51:51.960> connection<00:51:52.640> this<00:51:53.640> is<00:51:53.940> a 00:51:54.410 --> 00:51:54.420 align:start position:0% point-to-point connection this is a 00:51:54.420 --> 00:51:57.349 align:start position:0% point-to-point connection this is a direct<00:51:54.599> connection<00:51:55.079> between<00:51:56.040> two<00:51:56.700> nodes<00:51:57.059> on 00:51:57.349 --> 00:51:57.359 align:start position:0% direct connection between two nodes on 00:51:57.359 --> 00:51:58.849 align:start position:0% direct connection between two nodes on the<00:51:57.480> network<00:51:57.599> and<00:51:58.200> remember<00:51:58.319> when<00:51:58.680> we're 00:51:58.849 --> 00:51:58.859 align:start position:0% the network and remember when we're 00:51:58.859 --> 00:52:01.309 align:start position:0% the network and remember when we're talking<00:51:59.099> nodes<00:52:00.059> that<00:52:00.359> could<00:52:00.599> be<00:52:00.839> two 00:52:01.309 --> 00:52:01.319 align:start position:0% talking nodes that could be two 00:52:01.319 --> 00:52:02.950 align:start position:0% talking nodes that could be two computers 00:52:02.950 --> 00:52:02.960 align:start position:0% computers 00:52:02.960 --> 00:52:08.870 align:start position:0% computers uh<00:52:03.960> printers 00:52:08.870 --> 00:52:08.880 align:start position:0% 00:52:08.880 --> 00:52:11.089 align:start position:0% Etc<00:52:09.059> and<00:52:09.359> remember<00:52:09.480> we<00:52:09.900> had<00:52:10.079> endpoint<00:52:10.680> nodes 00:52:11.089 --> 00:52:11.099 align:start position:0% Etc and remember we had endpoint nodes 00:52:11.099 --> 00:52:14.390 align:start position:0% Etc and remember we had endpoint nodes and<00:52:11.640> then<00:52:11.700> we<00:52:12.000> had<00:52:12.260> redistribution<00:52:13.260> nodes 00:52:14.390 --> 00:52:14.400 align:start position:0% and then we had redistribution nodes 00:52:14.400 --> 00:52:17.030 align:start position:0% and then we had redistribution nodes so<00:52:14.940> this<00:52:15.300> these<00:52:15.780> can<00:52:15.900> either<00:52:16.079> by<00:52:16.380> the<00:52:16.559> way<00:52:16.619> be 00:52:17.030 --> 00:52:17.040 align:start position:0% so this these can either by the way be 00:52:17.040 --> 00:52:20.089 align:start position:0% so this these can either by the way be wired<00:52:17.520> or<00:52:17.760> Wireless<00:52:18.020> so<00:52:19.020> an<00:52:19.140> example<00:52:19.500> of<00:52:19.800> a 00:52:20.089 --> 00:52:20.099 align:start position:0% wired or Wireless so an example of a 00:52:20.099 --> 00:52:21.710 align:start position:0% wired or Wireless so an example of a wireless<00:52:20.280> point-to-point<00:52:21.000> connection<00:52:21.300> would 00:52:21.710 --> 00:52:21.720 align:start position:0% wireless point-to-point connection would 00:52:21.720 --> 00:52:24.349 align:start position:0% wireless point-to-point connection would be<00:52:21.839> for<00:52:22.200> instance<00:52:22.500> two<00:52:23.460> nodes<00:52:23.760> using<00:52:24.119> an 00:52:24.349 --> 00:52:24.359 align:start position:0% be for instance two nodes using an 00:52:24.359 --> 00:52:26.809 align:start position:0% be for instance two nodes using an infrared<00:52:24.920> connection<00:52:25.920> to<00:52:26.280> communicate<00:52:26.640> with 00:52:26.809 --> 00:52:26.819 align:start position:0% infrared connection to communicate with 00:52:26.819 --> 00:52:28.790 align:start position:0% infrared connection to communicate with one<00:52:27.000> another<00:52:27.119> like<00:52:27.540> your<00:52:27.780> TV<00:52:28.140> and<00:52:28.440> your<00:52:28.619> remote 00:52:28.790 --> 00:52:28.800 align:start position:0% one another like your TV and your remote 00:52:28.800 --> 00:52:31.370 align:start position:0% one another like your TV and your remote control<00:52:29.300> a<00:52:30.300> wired<00:52:30.720> point-to-point 00:52:31.370 --> 00:52:31.380 align:start position:0% control a wired point-to-point 00:52:31.380 --> 00:52:33.470 align:start position:0% control a wired point-to-point connection<00:52:31.680> on<00:52:32.099> the<00:52:32.160> other<00:52:32.220> hand<00:52:32.460> would<00:52:33.180> be 00:52:33.470 --> 00:52:33.480 align:start position:0% connection on the other hand would be 00:52:33.480 --> 00:52:36.290 align:start position:0% connection on the other hand would be two<00:52:33.839> computers<00:52:34.500> with<00:52:35.400> network<00:52:35.700> interface 00:52:36.290 --> 00:52:36.300 align:start position:0% two computers with network interface 00:52:36.300 --> 00:52:39.470 align:start position:0% two computers with network interface cards<00:52:36.720> or<00:52:37.079> nics<00:52:37.920> remember<00:52:38.280> that<00:52:38.700> term 00:52:39.470 --> 00:52:39.480 align:start position:0% cards or nics remember that term 00:52:39.480 --> 00:52:42.290 align:start position:0% cards or nics remember that term okay<00:52:40.079> connected<00:52:40.859> directly<00:52:41.280> together<00:52:41.460> with 00:52:42.290 --> 00:52:42.300 align:start position:0% okay connected directly together with 00:52:42.300 --> 00:52:45.230 align:start position:0% okay connected directly together with what's<00:52:42.540> called<00:52:42.839> a<00:52:43.380> crossover<00:52:43.980> cable<00:52:44.460> so 00:52:45.230 --> 00:52:45.240 align:start position:0% what's called a crossover cable so 00:52:45.240 --> 00:52:46.609 align:start position:0% what's called a crossover cable so there's<00:52:45.420> nothing<00:52:45.660> in<00:52:45.960> between<00:52:46.079> them<00:52:46.380> right 00:52:46.609 --> 00:52:46.619 align:start position:0% there's nothing in between them right 00:52:46.619 --> 00:52:47.930 align:start position:0% there's nothing in between them right they're<00:52:46.859> connected<00:52:47.280> directly<00:52:47.579> to<00:52:47.760> one 00:52:47.930 --> 00:52:47.940 align:start position:0% they're connected directly to one 00:52:47.940 --> 00:52:50.450 align:start position:0% they're connected directly to one another<00:52:48.059> using<00:52:48.839> cables<00:52:49.740> this<00:52:49.980> might<00:52:50.160> also<00:52:50.339> be 00:52:50.450 --> 00:52:50.460 align:start position:0% another using cables this might also be 00:52:50.460 --> 00:52:51.890 align:start position:0% another using cables this might also be the<00:52:50.640> same<00:52:50.760> thing<00:52:50.880> we<00:52:51.059> do<00:52:51.119> if<00:52:51.300> we<00:52:51.420> connected<00:52:51.780> two 00:52:51.890 --> 00:52:51.900 align:start position:0% the same thing we do if we connected two 00:52:51.900 --> 00:52:55.730 align:start position:0% the same thing we do if we connected two computers<00:52:52.319> together<00:52:52.500> somehow<00:52:53.099> using<00:52:53.700> USB<00:52:54.740> uh 00:52:55.730 --> 00:52:55.740 align:start position:0% computers together somehow using USB uh 00:52:55.740 --> 00:52:57.530 align:start position:0% computers together somehow using USB uh cables<00:52:56.280> although<00:52:56.700> that's<00:52:56.880> not<00:52:57.180> really<00:52:57.359> going 00:52:57.530 --> 00:52:57.540 align:start position:0% cables although that's not really going 00:52:57.540 --> 00:52:59.030 align:start position:0% cables although that's not really going to<00:52:57.660> happen<00:52:57.780> very<00:52:58.140> often<00:52:58.440> in<00:52:58.680> a<00:52:58.920> network 00:52:59.030 --> 00:52:59.040 align:start position:0% to happen very often in a network 00:52:59.040 --> 00:53:01.190 align:start position:0% to happen very often in a network setting<00:52:59.579> the<00:53:00.180> next<00:53:00.300> type<00:53:00.480> we<00:53:00.660> have<00:53:00.780> is<00:53:00.900> called 00:53:01.190 --> 00:53:01.200 align:start position:0% setting the next type we have is called 00:53:01.200 --> 00:53:03.470 align:start position:0% setting the next type we have is called a<00:53:01.680> multi-point<00:53:02.220> connection<00:53:02.520> now<00:53:02.940> as<00:53:03.119> the<00:53:03.300> name 00:53:03.470 --> 00:53:03.480 align:start position:0% a multi-point connection now as the name 00:53:03.480 --> 00:53:05.870 align:start position:0% a multi-point connection now as the name implies<00:53:03.960> we<00:53:04.260> had<00:53:04.440> point<00:53:04.920> to<00:53:05.160> point<00:53:05.339> that's 00:53:05.870 --> 00:53:05.880 align:start position:0% implies we had point to point that's 00:53:05.880 --> 00:53:08.270 align:start position:0% implies we had point to point that's like<00:53:06.119> one<00:53:06.359> to<00:53:06.599> one 00:53:08.270 --> 00:53:08.280 align:start position:0% like one to one 00:53:08.280 --> 00:53:12.650 align:start position:0% like one to one and<00:53:09.000> then<00:53:09.119> we<00:53:09.359> have<00:53:09.680> multi-point<00:53:10.680> connections 00:53:12.650 --> 00:53:12.660 align:start position:0% and then we have multi-point connections 00:53:12.660 --> 00:53:14.569 align:start position:0% and then we have multi-point connections which<00:53:13.200> means<00:53:13.500> that<00:53:13.680> there<00:53:13.920> are<00:53:14.040> connections 00:53:14.569 --> 00:53:14.579 align:start position:0% which means that there are connections 00:53:14.579 --> 00:53:17.450 align:start position:0% which means that there are connections between<00:53:14.880> multiple<00:53:15.540> nodes<00:53:15.960> so<00:53:16.740> there<00:53:17.099> are<00:53:17.220> two 00:53:17.450 --> 00:53:17.460 align:start position:0% between multiple nodes so there are two 00:53:17.460 --> 00:53:20.930 align:start position:0% between multiple nodes so there are two or<00:53:17.640> more<00:53:17.819> endpoints<00:53:18.680> connected<00:53:19.680> together<00:53:20.040> by 00:53:20.930 --> 00:53:20.940 align:start position:0% or more endpoints connected together by 00:53:20.940 --> 00:53:23.030 align:start position:0% or more endpoints connected together by each<00:53:21.300> multi-point<00:53:21.960> Connection<00:53:22.260> in<00:53:22.920> other 00:53:23.030 --> 00:53:23.040 align:start position:0% each multi-point Connection in other 00:53:23.040 --> 00:53:24.890 align:start position:0% each multi-point Connection in other words<00:53:23.160> all<00:53:23.460> transmissions<00:53:24.000> are<00:53:24.240> not<00:53:24.420> private 00:53:24.890 --> 00:53:24.900 align:start position:0% words all transmissions are not private 00:53:24.900 --> 00:53:27.230 align:start position:0% words all transmissions are not private because<00:53:25.260> every<00:53:25.980> node<00:53:26.280> on<00:53:26.460> the<00:53:26.640> network<00:53:26.760> can 00:53:27.230 --> 00:53:27.240 align:start position:0% because every node on the network can 00:53:27.240 --> 00:53:29.450 align:start position:0% because every node on the network can detect<00:53:27.540> the<00:53:27.780> signal<00:53:28.020> being<00:53:28.260> transmitted 00:53:29.450 --> 00:53:29.460 align:start position:0% detect the signal being transmitted 00:53:29.460 --> 00:53:31.430 align:start position:0% detect the signal being transmitted now<00:53:29.880> there's<00:53:30.119> also<00:53:30.420> something<00:53:30.599> called<00:53:31.020> a 00:53:31.430 --> 00:53:31.440 align:start position:0% now there's also something called a 00:53:31.440 --> 00:53:33.710 align:start position:0% now there's also something called a radiated<00:53:31.859> connection<00:53:32.220> and<00:53:33.119> as<00:53:33.359> the<00:53:33.540> name 00:53:33.710 --> 00:53:33.720 align:start position:0% radiated connection and as the name 00:53:33.720 --> 00:53:37.069 align:start position:0% radiated connection and as the name implies<00:53:34.200> radiated<00:53:35.099> this<00:53:35.760> is<00:53:35.940> specifically<00:53:36.420> a 00:53:37.069 --> 00:53:37.079 align:start position:0% implies radiated this is specifically a 00:53:37.079 --> 00:53:40.190 align:start position:0% implies radiated this is specifically a wireless<00:53:37.460> connection<00:53:38.660> so<00:53:39.660> data<00:53:40.079> is 00:53:40.190 --> 00:53:40.200 align:start position:0% wireless connection so data is 00:53:40.200 --> 00:53:42.349 align:start position:0% wireless connection so data is transmitted<00:53:40.740> wirelessly<00:53:41.460> between<00:53:41.819> devices 00:53:42.349 --> 00:53:42.359 align:start position:0% transmitted wirelessly between devices 00:53:42.359 --> 00:53:48.349 align:start position:0% transmitted wirelessly between devices it's<00:53:43.200> also<00:53:43.440> by<00:53:43.619> the<00:53:43.740> way<00:53:43.859> called<00:53:44.339> a<00:53:45.059> broadcast 00:53:48.349 --> 00:53:48.359 align:start position:0% 00:53:48.359 --> 00:53:51.349 align:start position:0% connection<00:53:49.280> uh<00:53:50.280> although<00:53:50.520> broadcast<00:53:50.760> also 00:53:51.349 --> 00:53:51.359 align:start position:0% connection uh although broadcast also 00:53:51.359 --> 00:53:52.849 align:start position:0% connection uh although broadcast also means<00:53:51.599> something<00:53:51.780> different<00:53:52.079> as<00:53:52.380> we<00:53:52.559> will<00:53:52.740> see 00:53:52.849 --> 00:53:52.859 align:start position:0% means something different as we will see 00:53:52.859 --> 00:53:54.049 align:start position:0% means something different as we will see in<00:53:52.980> just<00:53:53.160> a<00:53:53.339> minute 00:53:54.049 --> 00:53:54.059 align:start position:0% in just a minute 00:53:54.059 --> 00:53:56.630 align:start position:0% in just a minute so<00:53:54.599> some<00:53:55.020> radiated<00:53:55.440> connections<00:53:56.040> would<00:53:56.460> be 00:53:56.630 --> 00:53:56.640 align:start position:0% so some radiated connections would be 00:53:56.640 --> 00:54:00.049 align:start position:0% so some radiated connections would be like<00:53:56.819> Wi-Fi<00:53:57.380> or<00:53:58.380> wireless<00:53:58.740> LAN<00:53:59.339> and<00:53:59.700> in<00:53:59.880> some 00:54:00.049 --> 00:54:00.059 align:start position:0% like Wi-Fi or wireless LAN and in some 00:54:00.059 --> 00:54:03.230 align:start position:0% like Wi-Fi or wireless LAN and in some cases<00:54:00.420> even<00:54:00.839> an<00:54:01.200> infrared<00:54:01.740> like<00:54:02.280> your<00:54:02.819> um<00:54:02.880> a 00:54:03.230 --> 00:54:03.240 align:start position:0% cases even an infrared like your um a 00:54:03.240 --> 00:54:04.549 align:start position:0% cases even an infrared like your um a remote<00:54:03.420> control<00:54:03.720> but<00:54:04.079> the<00:54:04.200> reason<00:54:04.319> that 00:54:04.549 --> 00:54:04.559 align:start position:0% remote control but the reason that 00:54:04.559 --> 00:54:06.530 align:start position:0% remote control but the reason that that's<00:54:04.740> a<00:54:04.920> point<00:54:05.040> to<00:54:05.220> point<00:54:05.460> is<00:54:06.000> it<00:54:06.180> uh 00:54:06.530 --> 00:54:06.540 align:start position:0% that's a point to point is it uh 00:54:06.540 --> 00:54:13.309 align:start position:0% that's a point to point is it uh infrared<00:54:07.020> requires<00:54:07.859> direct<00:54:08.700> line<00:54:09.059> of<00:54:09.300> sight 00:54:13.309 --> 00:54:13.319 align:start position:0% 00:54:13.319 --> 00:54:16.250 align:start position:0% whereas<00:54:14.099> radiated<00:54:15.000> connections<00:54:15.599> that<00:54:15.839> can<00:54:16.020> be 00:54:16.250 --> 00:54:16.260 align:start position:0% whereas radiated connections that can be 00:54:16.260 --> 00:54:20.390 align:start position:0% whereas radiated connections that can be either<00:54:17.040> point<00:54:17.760> to<00:54:17.940> point<00:54:18.180> or<00:54:19.020> multi-point<00:54:19.740> so 00:54:20.390 --> 00:54:20.400 align:start position:0% either point to point or multi-point so 00:54:20.400 --> 00:54:23.450 align:start position:0% either point to point or multi-point so it<00:54:20.579> sort<00:54:20.760> of<00:54:20.880> is<00:54:21.059> uh<00:54:21.900> it<00:54:22.440> sort<00:54:22.619> of<00:54:22.740> involves<00:54:23.099> all 00:54:23.450 --> 00:54:23.460 align:start position:0% it sort of is uh it sort of involves all 00:54:23.460 --> 00:54:26.329 align:start position:0% it sort of is uh it sort of involves all of<00:54:23.579> these<00:54:23.760> different<00:54:23.940> ones 00:54:26.329 --> 00:54:26.339 align:start position:0% 00:54:26.339 --> 00:54:27.950 align:start position:0% all<00:54:26.760> right<00:54:26.940> now<00:54:27.059> let's<00:54:27.180> talk<00:54:27.359> some<00:54:27.540> about<00:54:27.720> some 00:54:27.950 --> 00:54:27.960 align:start position:0% all right now let's talk some about some 00:54:27.960 --> 00:54:30.349 align:start position:0% all right now let's talk some about some of<00:54:28.079> the<00:54:28.200> specific<00:54:28.619> uh<00:54:29.520> topologies<00:54:30.059> the<00:54:30.240> first 00:54:30.349 --> 00:54:30.359 align:start position:0% of the specific uh topologies the first 00:54:30.359 --> 00:54:31.609 align:start position:0% of the specific uh topologies the first one<00:54:30.480> I<00:54:30.599> want<00:54:30.720> to<00:54:30.780> talk<00:54:30.839> about<00:54:30.960> is<00:54:31.200> a<00:54:31.440> physical 00:54:31.609 --> 00:54:31.619 align:start position:0% one I want to talk about is a physical 00:54:31.619 --> 00:54:35.150 align:start position:0% one I want to talk about is a physical bus<00:54:32.220> topology<00:54:32.760> not<00:54:33.660> a<00:54:34.079> logical<00:54:34.440> bust<00:54:34.740> apology 00:54:35.150 --> 00:54:35.160 align:start position:0% bus topology not a logical bust apology 00:54:35.160 --> 00:54:37.010 align:start position:0% bus topology not a logical bust apology okay<00:54:35.520> so<00:54:35.819> again<00:54:35.940> this<00:54:36.240> is<00:54:36.359> the<00:54:36.540> physical<00:54:36.720> how 00:54:37.010 --> 00:54:37.020 align:start position:0% okay so again this is the physical how 00:54:37.020 --> 00:54:39.589 align:start position:0% okay so again this is the physical how things<00:54:37.319> are<00:54:37.740> physically<00:54:38.339> connected<00:54:38.940> and<00:54:39.420> what 00:54:39.589 --> 00:54:39.599 align:start position:0% things are physically connected and what 00:54:39.599 --> 00:54:42.049 align:start position:0% things are physically connected and what this<00:54:39.720> means<00:54:40.020> is<00:54:40.200> each<00:54:40.559> node<00:54:40.920> is<00:54:41.220> arranged<00:54:41.760> as 00:54:42.049 --> 00:54:42.059 align:start position:0% this means is each node is arranged as 00:54:42.059 --> 00:54:44.870 align:start position:0% this means is each node is arranged as you<00:54:42.180> can<00:54:42.300> tell<00:54:42.480> in<00:54:43.319> a<00:54:43.500> line<00:54:43.680> so<00:54:44.460> this<00:54:44.579> is<00:54:44.700> like 00:54:44.870 --> 00:54:44.880 align:start position:0% you can tell in a line so this is like 00:54:44.880 --> 00:54:47.569 align:start position:0% you can tell in a line so this is like seats<00:54:45.420> on<00:54:45.599> a<00:54:45.720> school<00:54:45.839> bus<00:54:46.079> everyone<00:54:47.040> on<00:54:47.400> the 00:54:47.569 --> 00:54:47.579 align:start position:0% seats on a school bus everyone on the 00:54:47.579 --> 00:54:50.270 align:start position:0% seats on a school bus everyone on the bus<00:54:47.700> can<00:54:48.420> hear<00:54:48.660> the<00:54:49.020> transmission<00:54:49.260> but<00:54:50.099> the 00:54:50.270 --> 00:54:50.280 align:start position:0% bus can hear the transmission but the 00:54:50.280 --> 00:54:53.329 align:start position:0% bus can hear the transmission but the message<00:54:50.460> is<00:54:50.819> only<00:54:51.000> received<00:54:51.780> by<00:54:52.559> one<00:54:52.980> specific 00:54:53.329 --> 00:54:53.339 align:start position:0% message is only received by one specific 00:54:53.339 --> 00:54:56.690 align:start position:0% message is only received by one specific recipient<00:54:54.140> so<00:54:55.140> a<00:54:55.559> bust<00:54:55.740> topology<00:54:56.280> is<00:54:56.579> an 00:54:56.690 --> 00:54:56.700 align:start position:0% recipient so a bust topology is an 00:54:56.700 --> 00:54:58.549 align:start position:0% recipient so a bust topology is an example<00:54:56.940> of<00:54:57.359> a<00:54:57.660> multi-point<00:54:58.260> connection 00:54:58.549 --> 00:54:58.559 align:start position:0% example of a multi-point connection 00:54:58.559 --> 00:55:02.470 align:start position:0% example of a multi-point connection right<00:54:59.040> because<00:54:59.760> we<00:55:00.119> have 00:55:02.470 --> 00:55:02.480 align:start position:0% 00:55:02.480 --> 00:55:04.849 align:start position:0% it<00:55:03.480> goes<00:55:03.839> to<00:55:03.900> all<00:55:04.079> these<00:55:04.260> different<00:55:04.440> points 00:55:04.849 --> 00:55:04.859 align:start position:0% it goes to all these different points 00:55:04.859 --> 00:55:07.069 align:start position:0% it goes to all these different points there<00:55:05.160> are<00:55:05.280> many<00:55:05.400> points<00:55:05.760> connected<00:55:06.119> to<00:55:06.300> it<00:55:06.480> if 00:55:07.069 --> 00:55:07.079 align:start position:0% there are many points connected to it if 00:55:07.079 --> 00:55:09.650 align:start position:0% there are many points connected to it if the<00:55:07.260> message<00:55:07.440> is<00:55:07.740> for<00:55:08.040> everyone<00:55:08.280> on<00:55:08.700> the<00:55:08.819> bus 00:55:09.650 --> 00:55:09.660 align:start position:0% the message is for everyone on the bus 00:55:09.660 --> 00:55:11.569 align:start position:0% the message is for everyone on the bus so<00:55:10.020> I'm<00:55:10.140> meaning<00:55:10.319> I<00:55:10.619> want<00:55:10.800> to<00:55:10.920> send<00:55:11.220> this 00:55:11.569 --> 00:55:11.579 align:start position:0% so I'm meaning I want to send this 00:55:11.579 --> 00:55:13.549 align:start position:0% so I'm meaning I want to send this message<00:55:11.819> out<00:55:12.240> to<00:55:12.420> everyone<00:55:12.599> that<00:55:13.260> would<00:55:13.440> be 00:55:13.549 --> 00:55:13.559 align:start position:0% message out to everyone that would be 00:55:13.559 --> 00:55:16.069 align:start position:0% message out to everyone that would be called<00:55:13.800> a<00:55:14.339> broadcast<00:55:14.640> connection<00:55:15.359> broadcast 00:55:16.069 --> 00:55:16.079 align:start position:0% called a broadcast connection broadcast 00:55:16.079 --> 00:55:20.030 align:start position:0% called a broadcast connection broadcast meaning<00:55:16.740> it<00:55:17.339> is<00:55:17.520> intended<00:55:18.059> and<00:55:18.720> sent<00:55:19.319> to<00:55:19.740> every 00:55:20.030 --> 00:55:20.040 align:start position:0% meaning it is intended and sent to every 00:55:20.040 --> 00:55:22.609 align:start position:0% meaning it is intended and sent to every single<00:55:20.400> person<00:55:20.640> on<00:55:21.480> the<00:55:21.540> bus<00:55:21.720> or<00:55:22.079> every<00:55:22.319> node 00:55:22.609 --> 00:55:22.619 align:start position:0% single person on the bus or every node 00:55:22.619 --> 00:55:24.650 align:start position:0% single person on the bus or every node uh<00:55:23.520> on<00:55:23.700> the<00:55:23.819> network 00:55:24.650 --> 00:55:24.660 align:start position:0% uh on the network 00:55:24.660 --> 00:55:26.270 align:start position:0% uh on the network If<00:55:25.140> the<00:55:25.260> message<00:55:25.440> on<00:55:25.680> the<00:55:25.800> other<00:55:25.859> hand<00:55:25.980> is 00:55:26.270 --> 00:55:26.280 align:start position:0% If the message on the other hand is 00:55:26.280 --> 00:55:28.970 align:start position:0% If the message on the other hand is meant<00:55:26.520> to<00:55:26.640> just<00:55:26.760> go<00:55:27.000> to<00:55:27.359> one<00:55:28.020> person<00:55:28.200> or<00:55:28.740> one 00:55:28.970 --> 00:55:28.980 align:start position:0% meant to just go to one person or one 00:55:28.980 --> 00:55:32.710 align:start position:0% meant to just go to one person or one node<00:55:29.339> we're<00:55:30.059> going<00:55:30.180> to<00:55:30.240> call<00:55:30.420> that<00:55:30.720> unicast 00:55:32.710 --> 00:55:32.720 align:start position:0% node we're going to call that unicast 00:55:32.720 --> 00:55:35.750 align:start position:0% node we're going to call that unicast uh<00:55:33.720> finally<00:55:34.380> if<00:55:34.859> it's<00:55:34.980> intended<00:55:35.400> to<00:55:35.460> go<00:55:35.640> to 00:55:35.750 --> 00:55:35.760 align:start position:0% uh finally if it's intended to go to 00:55:35.760 --> 00:55:37.430 align:start position:0% uh finally if it's intended to go to more<00:55:35.940> than<00:55:36.119> one<00:55:36.240> recipient<00:55:36.780> but<00:55:37.020> not<00:55:37.140> all<00:55:37.319> of 00:55:37.430 --> 00:55:37.440 align:start position:0% more than one recipient but not all of 00:55:37.440 --> 00:55:39.230 align:start position:0% more than one recipient but not all of them<00:55:37.559> then<00:55:37.800> we're<00:55:38.040> looking<00:55:38.220> at<00:55:38.460> a<00:55:38.760> multicast 00:55:39.230 --> 00:55:39.240 align:start position:0% them then we're looking at a multicast 00:55:39.240 --> 00:55:43.130 align:start position:0% them then we're looking at a multicast Okay<00:55:39.900> so<00:55:40.380> unicast 00:55:43.130 --> 00:55:43.140 align:start position:0% Okay so unicast 00:55:43.140 --> 00:55:45.349 align:start position:0% Okay so unicast as<00:55:43.559> the<00:55:43.740> name<00:55:43.859> implies 00:55:45.349 --> 00:55:45.359 align:start position:0% as the name implies 00:55:45.359 --> 00:55:48.589 align:start position:0% as the name implies means 00:55:48.589 --> 00:55:48.599 align:start position:0% 00:55:48.599 --> 00:55:51.770 align:start position:0% one<00:55:49.079> recipient 00:55:51.770 --> 00:55:51.780 align:start position:0% 00:55:51.780 --> 00:55:56.450 align:start position:0% multicast 00:55:56.450 --> 00:55:56.460 align:start position:0% 00:55:56.460 --> 00:56:00.170 align:start position:0% is<00:55:57.119> two 00:56:00.170 --> 00:56:00.180 align:start position:0% 00:56:00.180 --> 00:56:04.069 align:start position:0% or<00:56:00.720> more 00:56:04.069 --> 00:56:04.079 align:start position:0% 00:56:04.079 --> 00:56:05.930 align:start position:0% recipients 00:56:05.930 --> 00:56:05.940 align:start position:0% recipients 00:56:05.940 --> 00:56:08.089 align:start position:0% recipients and<00:56:06.660> then<00:56:06.839> I'm<00:56:07.319> just<00:56:07.500> going<00:56:07.619> to<00:56:07.619> write<00:56:07.800> this<00:56:07.920> up 00:56:08.089 --> 00:56:08.099 align:start position:0% and then I'm just going to write this up 00:56:08.099 --> 00:56:11.210 align:start position:0% and then I'm just going to write this up here<00:56:08.280> broadcast<00:56:09.319> as<00:56:10.319> the<00:56:10.500> name<00:56:10.559> implies<00:56:10.980> like 00:56:11.210 --> 00:56:11.220 align:start position:0% here broadcast as the name implies like 00:56:11.220 --> 00:56:14.630 align:start position:0% here broadcast as the name implies like a<00:56:11.460> television<00:56:11.819> broadcast<00:56:12.180> it<00:56:13.140> goes<00:56:13.500> to<00:56:13.680> all 00:56:14.630 --> 00:56:14.640 align:start position:0% a television broadcast it goes to all 00:56:14.640 --> 00:56:16.849 align:start position:0% a television broadcast it goes to all recipients<00:56:15.240> on<00:56:15.480> the<00:56:15.599> network 00:56:16.849 --> 00:56:16.859 align:start position:0% recipients on the network 00:56:16.859 --> 00:56:18.290 align:start position:0% recipients on the network it's<00:56:17.160> important<00:56:17.579> to<00:56:17.819> understand<00:56:17.940> the 00:56:18.290 --> 00:56:18.300 align:start position:0% it's important to understand the 00:56:18.300 --> 00:56:20.270 align:start position:0% it's important to understand the difference<00:56:18.420> in<00:56:18.720> these<00:56:18.960> types<00:56:19.200> of<00:56:19.319> messages<00:56:19.559> we 00:56:20.270 --> 00:56:20.280 align:start position:0% difference in these types of messages we 00:56:20.280 --> 00:56:21.710 align:start position:0% difference in these types of messages we have<00:56:20.460> broadcast<00:56:20.640> messages<00:56:21.119> go<00:56:21.420> out<00:56:21.540> to 00:56:21.710 --> 00:56:21.720 align:start position:0% have broadcast messages go out to 00:56:21.720 --> 00:56:24.049 align:start position:0% have broadcast messages go out to everyone<00:56:22.040> unicast<00:56:23.040> messages<00:56:23.280> go<00:56:23.640> out<00:56:23.760> to<00:56:23.880> one 00:56:24.049 --> 00:56:24.059 align:start position:0% everyone unicast messages go out to one 00:56:24.059 --> 00:56:26.690 align:start position:0% everyone unicast messages go out to one recipient<00:56:24.480> multicast<00:56:25.319> to<00:56:25.559> two<00:56:25.740> or<00:56:25.920> more<00:56:26.099> but 00:56:26.690 --> 00:56:26.700 align:start position:0% recipient multicast to two or more but 00:56:26.700 --> 00:56:28.130 align:start position:0% recipient multicast to two or more but different<00:56:27.000> from<00:56:27.300> broadcast<00:56:27.480> because<00:56:27.900> it's 00:56:28.130 --> 00:56:28.140 align:start position:0% different from broadcast because it's 00:56:28.140 --> 00:56:31.790 align:start position:0% different from broadcast because it's not<00:56:28.319> going<00:56:28.619> to<00:56:29.280> everyone<00:56:29.579> or<00:56:30.300> all<00:56:30.660> of<00:56:30.839> them<00:56:31.079> the 00:56:31.790 --> 00:56:31.800 align:start position:0% not going to everyone or all of them the 00:56:31.800 --> 00:56:36.109 align:start position:0% not going to everyone or all of them the way<00:56:31.920> multicast<00:56:32.640> works<00:56:33.240> is<00:56:33.660> that<00:56:34.099> only<00:56:35.099> uh<00:56:35.940> the 00:56:36.109 --> 00:56:36.119 align:start position:0% way multicast works is that only uh the 00:56:36.119 --> 00:56:37.670 align:start position:0% way multicast works is that only uh the stations<00:56:36.540> or<00:56:36.660> the<00:56:36.839> nodes<00:56:37.079> that<00:56:37.440> have 00:56:37.670 --> 00:56:37.680 align:start position:0% stations or the nodes that have 00:56:37.680 --> 00:56:39.950 align:start position:0% stations or the nodes that have subscribed<00:56:38.579> to<00:56:38.880> a<00:56:39.000> message<00:56:39.119> will<00:56:39.480> receive<00:56:39.839> it 00:56:39.950 --> 00:56:39.960 align:start position:0% subscribed to a message will receive it 00:56:39.960 --> 00:56:42.410 align:start position:0% subscribed to a message will receive it so<00:56:40.559> we<00:56:40.859> could<00:56:41.040> if<00:56:41.280> we're<00:56:41.400> using<00:56:41.640> a<00:56:41.819> TV<00:56:42.059> sort<00:56:42.300> of 00:56:42.410 --> 00:56:42.420 align:start position:0% so we could if we're using a TV sort of 00:56:42.420 --> 00:56:44.329 align:start position:0% so we could if we're using a TV sort of example<00:56:42.720> unicast<00:56:43.500> would<00:56:43.740> be<00:56:43.859> like<00:56:43.980> if<00:56:44.160> you 00:56:44.329 --> 00:56:44.339 align:start position:0% example unicast would be like if you 00:56:44.339 --> 00:56:46.970 align:start position:0% example unicast would be like if you have<00:56:44.460> a<00:56:44.760> direct<00:56:44.880> line<00:56:45.780> to<00:56:46.140> your<00:56:46.680> sort<00:56:46.859> of 00:56:46.970 --> 00:56:46.980 align:start position:0% have a direct line to your sort of 00:56:46.980 --> 00:56:48.950 align:start position:0% have a direct line to your sort of television<00:56:47.339> provider<00:56:47.819> multicast<00:56:48.540> would<00:56:48.839> be 00:56:48.950 --> 00:56:48.960 align:start position:0% television provider multicast would be 00:56:48.960 --> 00:56:51.770 align:start position:0% television provider multicast would be like<00:56:49.079> HP<00:56:49.440> only<00:56:49.680> those<00:56:49.859> subscribing<00:56:50.640> to<00:56:51.480> the 00:56:51.770 --> 00:56:51.780 align:start position:0% like HP only those subscribing to the 00:56:51.780 --> 00:56:55.130 align:start position:0% like HP only those subscribing to the specific<00:56:52.079> uh<00:56:52.980> cable<00:56:53.700> network<00:56:54.180> get<00:56:54.540> access<00:56:54.780> to 00:56:55.130 --> 00:56:55.140 align:start position:0% specific uh cable network get access to 00:56:55.140 --> 00:56:57.290 align:start position:0% specific uh cable network get access to it<00:56:55.260> broadcast<00:56:55.800> is<00:56:56.280> sort<00:56:56.520> of<00:56:56.579> any<00:56:56.760> it's<00:56:57.000> in<00:56:57.180> the 00:56:57.290 --> 00:56:57.300 align:start position:0% it broadcast is sort of any it's in the 00:56:57.300 --> 00:57:00.230 align:start position:0% it broadcast is sort of any it's in the air<00:56:57.420> anyone<00:56:57.900> can<00:56:58.079> get<00:56:58.260> it<00:56:58.380> right<00:56:58.619> so<00:56:59.400> on<00:56:59.760> a<00:57:00.000> bust 00:57:00.230 --> 00:57:00.240 align:start position:0% air anyone can get it right so on a bust 00:57:00.240 --> 00:57:02.150 align:start position:0% air anyone can get it right so on a bust apology<00:57:00.720> like<00:57:01.200> we're<00:57:01.380> looking<00:57:01.559> at<00:57:01.680> right<00:57:01.980> now 00:57:02.150 --> 00:57:02.160 align:start position:0% apology like we're looking at right now 00:57:02.160 --> 00:57:05.329 align:start position:0% apology like we're looking at right now when<00:57:02.700> the<00:57:02.880> data<00:57:03.180> is<00:57:03.359> transmitted<00:57:04.079> the<00:57:04.980> signal 00:57:05.329 --> 00:57:05.339 align:start position:0% when the data is transmitted the signal 00:57:05.339 --> 00:57:08.089 align:start position:0% when the data is transmitted the signal will<00:57:05.760> bounce<00:57:06.119> or<00:57:06.420> reflect<00:57:06.839> off<00:57:07.260> of 00:57:08.089 --> 00:57:08.099 align:start position:0% will bounce or reflect off of 00:57:08.099 --> 00:57:11.270 align:start position:0% will bounce or reflect off of the<00:57:08.760> ends<00:57:09.119> and<00:57:09.900> so<00:57:10.020> it's<00:57:10.200> important 00:57:11.270 --> 00:57:11.280 align:start position:0% the ends and so it's important 00:57:11.280 --> 00:57:14.210 align:start position:0% the ends and so it's important uh<00:57:11.940> that<00:57:12.180> when<00:57:12.480> the<00:57:12.720> signal<00:57:12.960> bounces<00:57:13.500> it's 00:57:14.210 --> 00:57:14.220 align:start position:0% uh that when the signal bounces it's 00:57:14.220 --> 00:57:16.250 align:start position:0% uh that when the signal bounces it's gonna<00:57:14.400> interrupt<00:57:15.059> the<00:57:15.240> transmission<00:57:15.540> if 00:57:16.250 --> 00:57:16.260 align:start position:0% gonna interrupt the transmission if 00:57:16.260 --> 00:57:17.510 align:start position:0% gonna interrupt the transmission if there's<00:57:16.380> nothing<00:57:16.619> there<00:57:16.859> to<00:57:17.099> stop<00:57:17.280> that 00:57:17.510 --> 00:57:17.520 align:start position:0% there's nothing there to stop that 00:57:17.520 --> 00:57:19.549 align:start position:0% there's nothing there to stop that bounce<00:57:17.819> from<00:57:18.059> occurring<00:57:18.480> so<00:57:19.079> to<00:57:19.260> keep<00:57:19.380> this 00:57:19.549 --> 00:57:19.559 align:start position:0% bounce from occurring so to keep this 00:57:19.559 --> 00:57:20.930 align:start position:0% bounce from occurring so to keep this from<00:57:19.740> happening<00:57:20.099> we<00:57:20.400> generally<00:57:20.640> have 00:57:20.930 --> 00:57:20.940 align:start position:0% from happening we generally have 00:57:20.940 --> 00:57:23.089 align:start position:0% from happening we generally have something<00:57:21.180> called<00:57:21.480> a<00:57:21.780> terminator<00:57:22.260> and<00:57:22.920> it's 00:57:23.089 --> 00:57:23.099 align:start position:0% something called a terminator and it's 00:57:23.099 --> 00:57:25.010 align:start position:0% something called a terminator and it's generally<00:57:23.520> around<00:57:23.760> 50<00:57:24.180> ohms<00:57:24.720> I<00:57:24.900> would 00:57:25.010 --> 00:57:25.020 align:start position:0% generally around 50 ohms I would 00:57:25.020 --> 00:57:26.809 align:start position:0% generally around 50 ohms I would remember<00:57:25.200> that<00:57:25.559> for<00:57:25.800> the<00:57:25.980> exam<00:57:26.280> because<00:57:26.520> I<00:57:26.700> do 00:57:26.809 --> 00:57:26.819 align:start position:0% remember that for the exam because I do 00:57:26.819 --> 00:57:29.210 align:start position:0% remember that for the exam because I do see<00:57:27.000> that<00:57:27.180> pop<00:57:27.359> up<00:57:27.599> and<00:57:28.380> what<00:57:28.500> this<00:57:28.680> does<00:57:28.800> is<00:57:28.980> it 00:57:29.210 --> 00:57:29.220 align:start position:0% see that pop up and what this does is it 00:57:29.220 --> 00:57:32.089 align:start position:0% see that pop up and what this does is it really<00:57:29.400> grounds<00:57:30.240> the<00:57:30.780> bus<00:57:31.200> transmission<00:57:31.559> or 00:57:32.089 --> 00:57:32.099 align:start position:0% really grounds the bus transmission or 00:57:32.099 --> 00:57:35.390 align:start position:0% really grounds the bus transmission or the<00:57:32.220> bus<00:57:32.400> connections<00:57:33.240> to<00:57:33.599> reduce<00:57:33.980> uh<00:57:34.980> and<00:57:35.220> it 00:57:35.390 --> 00:57:35.400 align:start position:0% the bus connections to reduce uh and it 00:57:35.400 --> 00:57:37.849 align:start position:0% the bus connections to reduce uh and it reduces<00:57:35.760> static<00:57:36.180> electricity<00:57:36.599> to<00:57:37.140> keep<00:57:37.619> this 00:57:37.849 --> 00:57:37.859 align:start position:0% reduces static electricity to keep this 00:57:37.859 --> 00:57:39.950 align:start position:0% reduces static electricity to keep this Bounce<00:57:38.040> from<00:57:38.400> occurring<00:57:38.819> that<00:57:39.240> bounce<00:57:39.540> occurs 00:57:39.950 --> 00:57:39.960 align:start position:0% Bounce from occurring that bounce occurs 00:57:39.960 --> 00:57:41.990 align:start position:0% Bounce from occurring that bounce occurs then<00:57:40.140> we're<00:57:40.380> having<00:57:40.619> all<00:57:41.339> sorts<00:57:41.640> of<00:57:41.640> problems 00:57:41.990 --> 00:57:42.000 align:start position:0% then we're having all sorts of problems 00:57:42.000 --> 00:57:45.410 align:start position:0% then we're having all sorts of problems start<00:57:42.119> to<00:57:42.300> occur<00:57:42.540> in<00:57:42.599> our<00:57:42.780> Network<00:57:43.040> now<00:57:44.040> uh<00:57:44.700> if 00:57:45.410 --> 00:57:45.420 align:start position:0% start to occur in our Network now uh if 00:57:45.420 --> 00:57:47.150 align:start position:0% start to occur in our Network now uh if the<00:57:45.839> way<00:57:45.960> that<00:57:46.140> these<00:57:46.319> nodes<00:57:46.500> are<00:57:46.740> connected 00:57:47.150 --> 00:57:47.160 align:start position:0% the way that these nodes are connected 00:57:47.160 --> 00:57:49.910 align:start position:0% the way that these nodes are connected as<00:57:47.460> you<00:57:47.640> can<00:57:47.760> see<00:57:48.059> are<00:57:48.359> by<00:57:48.599> these<00:57:48.960> T<00:57:49.500> connectors 00:57:49.910 --> 00:57:49.920 align:start position:0% as you can see are by these T connectors 00:57:49.920 --> 00:57:50.870 align:start position:0% as you can see are by these T connectors and<00:57:50.099> the<00:57:50.220> reason<00:57:50.339> they're<00:57:50.520> called<00:57:50.700> T 00:57:50.870 --> 00:57:50.880 align:start position:0% and the reason they're called T 00:57:50.880 --> 00:57:52.309 align:start position:0% and the reason they're called T connectors<00:57:51.359> is<00:57:51.480> because<00:57:51.660> they<00:57:51.900> look<00:57:52.020> like<00:57:52.200> an 00:57:52.309 --> 00:57:52.319 align:start position:0% connectors is because they look like an 00:57:52.319 --> 00:57:54.049 align:start position:0% connectors is because they look like an upside<00:57:52.619> down<00:57:52.859> t 00:57:54.049 --> 00:57:54.059 align:start position:0% upside down t 00:57:54.059 --> 00:57:56.569 align:start position:0% upside down t now<00:57:54.780> the<00:57:55.380> downside<00:57:55.800> to<00:57:56.099> using<00:57:56.339> a<00:57:56.460> bus 00:57:56.569 --> 00:57:56.579 align:start position:0% now the downside to using a bus 00:57:56.579 --> 00:57:57.710 align:start position:0% now the downside to using a bus connection<00:57:56.819> are<00:57:57.180> obviously<00:57:57.480> these 00:57:57.710 --> 00:57:57.720 align:start position:0% connection are obviously these 00:57:57.720 --> 00:57:58.970 align:start position:0% connection are obviously these terminators 00:57:58.970 --> 00:57:58.980 align:start position:0% terminators 00:57:58.980 --> 00:58:02.450 align:start position:0% terminators and<00:57:59.819> uh<00:58:00.480> it's<00:58:00.780> a<00:58:01.079> little<00:58:01.200> frustrating<00:58:01.980> to<00:58:02.339> sort 00:58:02.450 --> 00:58:02.460 align:start position:0% and uh it's a little frustrating to sort 00:58:02.460 --> 00:58:04.790 align:start position:0% and uh it's a little frustrating to sort of<00:58:02.520> connect<00:58:02.700> these<00:58:03.059> up<00:58:03.240> but<00:58:03.660> the<00:58:03.900> upside<00:58:04.319> to 00:58:04.790 --> 00:58:04.800 align:start position:0% of connect these up but the upside to 00:58:04.800 --> 00:58:07.250 align:start position:0% of connect these up but the upside to using<00:58:05.040> a<00:58:05.160> bus<00:58:05.280> technology<00:58:05.880> uh<00:58:06.540> topology 00:58:07.250 --> 00:58:07.260 align:start position:0% using a bus technology uh topology 00:58:07.260 --> 00:58:09.589 align:start position:0% using a bus technology uh topology rather<00:58:07.680> is<00:58:08.220> that<00:58:08.339> it's<00:58:08.579> inexpensive<00:58:09.180> and<00:58:09.420> it's 00:58:09.589 --> 00:58:09.599 align:start position:0% rather is that it's inexpensive and it's 00:58:09.599 --> 00:58:13.670 align:start position:0% rather is that it's inexpensive and it's relatively<00:58:10.440> easy<00:58:10.740> to<00:58:11.160> implement 00:58:13.670 --> 00:58:13.680 align:start position:0% relatively easy to implement 00:58:13.680 --> 00:58:15.109 align:start position:0% relatively easy to implement now<00:58:13.980> this<00:58:14.160> is<00:58:14.220> different<00:58:14.400> from<00:58:14.700> a<00:58:14.880> physical 00:58:15.109 --> 00:58:15.119 align:start position:0% now this is different from a physical 00:58:15.119 --> 00:58:17.450 align:start position:0% now this is different from a physical star<00:58:15.720> topology<00:58:16.260> as<00:58:16.500> you<00:58:16.619> can<00:58:16.740> see<00:58:16.859> now<00:58:17.160> instead 00:58:17.450 --> 00:58:17.460 align:start position:0% star topology as you can see now instead 00:58:17.460 --> 00:58:19.430 align:start position:0% star topology as you can see now instead of<00:58:17.579> a<00:58:17.760> line<00:58:17.940> everything<00:58:18.599> is<00:58:18.900> connected<00:58:19.260> to 00:58:19.430 --> 00:58:19.440 align:start position:0% of a line everything is connected to 00:58:19.440 --> 00:58:21.530 align:start position:0% of a line everything is connected to every<00:58:19.680> other<00:58:19.859> device<00:58:20.160> using<00:58:20.760> a<00:58:21.180> central 00:58:21.530 --> 00:58:21.540 align:start position:0% every other device using a central 00:58:21.540 --> 00:58:25.970 align:start position:0% every other device using a central connection<00:58:21.960> device<00:58:22.500> such<00:58:23.160> as<00:58:23.339> a<00:58:23.819> switch 00:58:25.970 --> 00:58:25.980 align:start position:0% connection device such as a switch 00:58:25.980 --> 00:58:28.370 align:start position:0% connection device such as a switch or<00:58:26.880> a<00:58:27.059> hub 00:58:28.370 --> 00:58:28.380 align:start position:0% or a hub 00:58:28.380 --> 00:58:30.950 align:start position:0% or a hub in<00:58:28.920> a<00:58:29.099> physical<00:58:29.220> start<00:58:29.640> topology<00:58:30.240> where<00:58:30.599> a 00:58:30.950 --> 00:58:30.960 align:start position:0% in a physical start topology where a 00:58:30.960 --> 00:58:33.950 align:start position:0% in a physical start topology where a switch<00:58:31.500> is<00:58:31.800> used<00:58:32.040> what<00:58:32.819> happens 00:58:33.950 --> 00:58:33.960 align:start position:0% switch is used what happens 00:58:33.960 --> 00:58:36.230 align:start position:0% switch is used what happens is<00:58:34.440> the<00:58:34.619> node<00:58:34.800> that's<00:58:35.099> transmitting<00:58:35.819> the<00:58:35.940> data 00:58:36.230 --> 00:58:36.240 align:start position:0% is the node that's transmitting the data 00:58:36.240 --> 00:58:38.930 align:start position:0% is the node that's transmitting the data to<00:58:36.359> another<00:58:36.599> node<00:58:37.160> uh<00:58:38.160> the<00:58:38.339> switch<00:58:38.520> actually 00:58:38.930 --> 00:58:38.940 align:start position:0% to another node uh the switch actually 00:58:38.940 --> 00:58:40.549 align:start position:0% to another node uh the switch actually will 00:58:40.549 --> 00:58:40.559 align:start position:0% will 00:58:40.559 --> 00:58:42.770 align:start position:0% will determine<00:58:41.280> where<00:58:41.819> that<00:58:42.059> information<00:58:42.240> needs 00:58:42.770 --> 00:58:42.780 align:start position:0% determine where that information needs 00:58:42.780 --> 00:58:46.250 align:start position:0% determine where that information needs to go<00:58:42.900> and<00:58:43.079> send<00:58:43.260> it<00:58:43.500> only<00:58:43.859> to<00:58:44.819> the 00:58:46.250 --> 00:58:46.260 align:start position:0% to go and send it only to the 00:58:46.260 --> 00:58:49.130 align:start position:0% to go and send it only to the node<00:58:46.920> that<00:58:47.339> is<00:58:47.460> the<00:58:47.640> intended<00:58:48.000> recipient<00:58:48.540> like 00:58:49.130 --> 00:58:49.140 align:start position:0% node that is the intended recipient like 00:58:49.140 --> 00:58:51.950 align:start position:0% node that is the intended recipient like a<00:58:49.440> unicast<00:58:49.980> right 00:58:51.950 --> 00:58:51.960 align:start position:0% a unicast right 00:58:51.960 --> 00:58:54.890 align:start position:0% a unicast right on<00:58:52.680> the<00:58:52.799> other<00:58:52.859> hand<00:58:53.040> a<00:58:53.640> hub 00:58:54.890 --> 00:58:54.900 align:start position:0% on the other hand a hub 00:58:54.900 --> 00:58:57.829 align:start position:0% on the other hand a hub is<00:58:55.500> going<00:58:55.680> to<00:58:55.859> send<00:58:56.099> the<00:58:56.280> data<00:58:56.520> out 00:58:57.829 --> 00:58:57.839 align:start position:0% is going to send the data out 00:58:57.839 --> 00:59:00.470 align:start position:0% is going to send the data out to<00:58:58.440> everyone<00:58:58.619> and<00:58:59.400> what's<00:58:59.579> more<00:58:59.819> like<00:59:00.119> a 00:59:00.470 --> 00:59:00.480 align:start position:0% to everyone and what's more like a 00:59:00.480 --> 00:59:02.210 align:start position:0% to everyone and what's more like a broadcast<00:59:00.900> connection 00:59:02.210 --> 00:59:02.220 align:start position:0% broadcast connection 00:59:02.220 --> 00:59:05.150 align:start position:0% broadcast connection now<00:59:02.819> the<00:59:03.180> uh<00:59:03.540> and<00:59:04.319> we'll<00:59:04.500> talk<00:59:04.680> more<00:59:04.920> about 00:59:05.150 --> 00:59:05.160 align:start position:0% now the uh and we'll talk more about 00:59:05.160 --> 00:59:06.950 align:start position:0% now the uh and we'll talk more about hubs<00:59:06.059> and<00:59:06.119> switches<00:59:06.480> a<00:59:06.660> little<00:59:06.720> bit<00:59:06.839> later 00:59:06.950 --> 00:59:06.960 align:start position:0% hubs and switches a little bit later 00:59:06.960 --> 00:59:09.710 align:start position:0% hubs and switches a little bit later when<00:59:07.200> we<00:59:07.380> get<00:59:07.440> to<00:59:07.619> devices 00:59:09.710 --> 00:59:09.720 align:start position:0% when we get to devices 00:59:09.720 --> 00:59:12.289 align:start position:0% when we get to devices the<00:59:10.260> physical<00:59:10.440> start<00:59:10.859> topology<00:59:11.400> it's<00:59:11.819> very 00:59:12.289 --> 00:59:12.299 align:start position:0% the physical start topology it's very 00:59:12.299 --> 00:59:15.650 align:start position:0% the physical start topology it's very common<00:59:12.599> today<00:59:13.040> and<00:59:14.040> it's<00:59:14.819> uh<00:59:15.180> easy<00:59:15.420> to 00:59:15.650 --> 00:59:15.660 align:start position:0% common today and it's uh easy to 00:59:15.660 --> 00:59:17.870 align:start position:0% common today and it's uh easy to implement<00:59:16.020> and<00:59:16.380> maintain<00:59:16.859> and<00:59:17.280> it's<00:59:17.640> much 00:59:17.870 --> 00:59:17.880 align:start position:0% implement and maintain and it's much 00:59:17.880 --> 00:59:19.490 align:start position:0% implement and maintain and it's much more<00:59:18.059> reliable<00:59:18.420> than<00:59:18.660> bust<00:59:18.900> apologies 00:59:19.490 --> 00:59:19.500 align:start position:0% more reliable than bust apologies 00:59:19.500 --> 00:59:23.150 align:start position:0% more reliable than bust apologies because<00:59:20.099> if<00:59:20.760> one<00:59:21.000> node<00:59:21.299> fails<00:59:21.839> or<00:59:22.799> one 00:59:23.150 --> 00:59:23.160 align:start position:0% because if one node fails or one 00:59:23.160 --> 00:59:25.430 align:start position:0% because if one node fails or one connection<00:59:23.400> to<00:59:23.760> a<00:59:23.940> node<00:59:24.119> fails<00:59:24.599> uh<00:59:25.260> for 00:59:25.430 --> 00:59:25.440 align:start position:0% connection to a node fails uh for 00:59:25.440 --> 00:59:26.750 align:start position:0% connection to a node fails uh for instance<00:59:25.680> this<00:59:26.099> one 00:59:26.750 --> 00:59:26.760 align:start position:0% instance this one 00:59:26.760 --> 00:59:28.309 align:start position:0% instance this one then<00:59:27.240> the<00:59:27.480> rest<00:59:27.540> of<00:59:27.660> the<00:59:27.720> network<00:59:27.900> isn't 00:59:28.309 --> 00:59:28.319 align:start position:0% then the rest of the network isn't 00:59:28.319 --> 00:59:30.950 align:start position:0% then the rest of the network isn't affected<00:59:28.740> and<00:59:29.579> a<00:59:29.760> sort<00:59:29.940> of<00:59:30.059> client<00:59:30.420> server 00:59:30.950 --> 00:59:30.960 align:start position:0% affected and a sort of client server 00:59:30.960 --> 00:59:34.910 align:start position:0% affected and a sort of client server Arrangement<00:59:31.640> each<00:59:32.640> node<00:59:33.059> is<00:59:33.720> inherently<00:59:34.440> not 00:59:34.910 --> 00:59:34.920 align:start position:0% Arrangement each node is inherently not 00:59:34.920 --> 00:59:36.770 align:start position:0% Arrangement each node is inherently not aware<00:59:35.339> of<00:59:35.760> all<00:59:35.880> the<00:59:36.059> other<00:59:36.180> nodes<00:59:36.480> on<00:59:36.660> the 00:59:36.770 --> 00:59:36.780 align:start position:0% aware of all the other nodes on the 00:59:36.780 --> 00:59:39.710 align:start position:0% aware of all the other nodes on the network<00:59:36.960> because<00:59:37.760> the<00:59:38.760> node<00:59:39.000> only<00:59:39.299> has<00:59:39.540> a 00:59:39.710 --> 00:59:39.720 align:start position:0% network because the node only has a 00:59:39.720 --> 00:59:42.170 align:start position:0% network because the node only has a connection 00:59:42.170 --> 00:59:42.180 align:start position:0% 00:59:42.180 --> 00:59:44.809 align:start position:0% to<00:59:42.780> this<00:59:42.960> Central<00:59:43.140> sort<00:59:43.500> of<00:59:43.619> host<00:59:43.799> now<00:59:44.640> the 00:59:44.809 --> 00:59:44.819 align:start position:0% to this Central sort of host now the 00:59:44.819 --> 00:59:46.370 align:start position:0% to this Central sort of host now the negative<00:59:45.059> aspect<00:59:45.480> of<00:59:45.660> this<00:59:45.839> physical<00:59:46.020> start 00:59:46.370 --> 00:59:46.380 align:start position:0% negative aspect of this physical start 00:59:46.380 --> 00:59:48.770 align:start position:0% negative aspect of this physical start topology<00:59:46.859> is<00:59:47.460> we<00:59:47.640> have<00:59:47.760> what's<00:59:48.059> called<00:59:48.359> a 00:59:48.770 --> 00:59:48.780 align:start position:0% topology is we have what's called a 00:59:48.780 --> 00:59:51.049 align:start position:0% topology is we have what's called a single<00:59:49.440> point<00:59:49.619> of<00:59:49.859> failure<00:59:50.280> here<00:59:50.520> in<00:59:50.880> this 00:59:51.049 --> 00:59:51.059 align:start position:0% single point of failure here in this 00:59:51.059 --> 00:59:53.150 align:start position:0% single point of failure here in this connectivity<00:59:51.540> device<00:59:51.839> and<00:59:52.319> if<00:59:52.500> that<00:59:52.740> fails 00:59:53.150 --> 00:59:53.160 align:start position:0% connectivity device and if that fails 00:59:53.160 --> 00:59:55.190 align:start position:0% connectivity device and if that fails all<00:59:53.579> of<00:59:53.760> the<00:59:53.940> other<00:59:54.119> devices<00:59:54.599> won't<00:59:54.900> be<00:59:55.079> able 00:59:55.190 --> 00:59:55.200 align:start position:0% all of the other devices won't be able 00:59:55.200 --> 00:59:57.589 align:start position:0% all of the other devices won't be able to<00:59:55.319> communicate<00:59:55.859> so<00:59:56.400> the<00:59:56.579> benefit<00:59:56.700> is<00:59:57.059> now<00:59:57.359> not 00:59:57.589 --> 00:59:57.599 align:start position:0% to communicate so the benefit is now not 00:59:57.599 --> 00:59:59.630 align:start position:0% to communicate so the benefit is now not everyone<00:59:57.780> has<00:59:58.079> to<00:59:58.260> get<00:59:58.380> the<00:59:58.559> message<00:59:58.740> and<00:59:59.460> it's 00:59:59.630 --> 00:59:59.640 align:start position:0% everyone has to get the message and it's 00:59:59.640 --> 01:00:01.670 align:start position:0% everyone has to get the message and it's easier<01:00:00.000> to<01:00:00.420> uh<01:00:00.900> it's<01:00:01.079> sort<01:00:01.260> of<01:00:01.319> really<01:00:01.500> cheap 01:00:01.670 --> 01:00:01.680 align:start position:0% easier to uh it's sort of really cheap 01:00:01.680 --> 01:00:03.170 align:start position:0% easier to uh it's sort of really cheap and<01:00:01.859> easy<01:00:02.040> to<01:00:02.220> implement<01:00:02.460> it's<01:00:02.640> also<01:00:02.940> the<01:00:03.059> most 01:00:03.170 --> 01:00:03.180 align:start position:0% and easy to implement it's also the most 01:00:03.180 --> 01:00:05.030 align:start position:0% and easy to implement it's also the most popular<01:00:03.480> because<01:00:04.140> of<01:00:04.380> any<01:00:04.619> of<01:00:04.799> these 01:00:05.030 --> 01:00:05.040 align:start position:0% popular because of any of these 01:00:05.040 --> 01:00:06.230 align:start position:0% popular because of any of these connections<01:00:05.460> go<01:00:05.640> down<01:00:05.819> I<01:00:06.000> don't<01:00:06.119> lose 01:00:06.230 --> 01:00:06.240 align:start position:0% connections go down I don't lose 01:00:06.240 --> 01:00:08.210 align:start position:0% connections go down I don't lose connection<01:00:06.480> to<01:00:06.720> the<01:00:06.900> whole<01:00:07.020> thing<01:00:07.260> unlike<01:00:08.040> the 01:00:08.210 --> 01:00:08.220 align:start position:0% connection to the whole thing unlike the 01:00:08.220 --> 01:00:09.470 align:start position:0% connection to the whole thing unlike the bus<01:00:08.339> where<01:00:08.640> if<01:00:08.819> one<01:00:08.940> of<01:00:09.059> those<01:00:09.119> connections 01:00:09.470 --> 01:00:09.480 align:start position:0% bus where if one of those connections 01:00:09.480 --> 01:00:11.569 align:start position:0% bus where if one of those connections goes<01:00:09.780> down<01:00:09.960> obviously<01:00:10.740> the<01:00:10.980> connection<01:00:11.160> can't 01:00:11.569 --> 01:00:11.579 align:start position:0% goes down obviously the connection can't 01:00:11.579 --> 01:00:14.150 align:start position:0% goes down obviously the connection can't continue<01:00:11.940> but<01:00:12.780> the<01:00:13.079> downside<01:00:13.380> is<01:00:13.619> that<01:00:13.859> I<01:00:14.040> now 01:00:14.150 --> 01:00:14.160 align:start position:0% continue but the downside is that I now 01:00:14.160 --> 01:00:15.530 align:start position:0% continue but the downside is that I now have<01:00:14.339> a<01:00:14.460> single<01:00:14.700> point<01:00:14.760> of<01:00:14.940> failure<01:00:15.240> in<01:00:15.359> this 01:00:15.530 --> 01:00:15.540 align:start position:0% have a single point of failure in this 01:00:15.540 --> 01:00:19.309 align:start position:0% have a single point of failure in this Central<01:00:15.780> device 01:00:19.309 --> 01:00:19.319 align:start position:0% 01:00:19.319 --> 01:00:22.789 align:start position:0% now<01:00:19.859> in<01:00:20.040> a<01:00:20.280> physical<01:00:20.400> ring<01:00:21.359> topology<01:00:21.799> each 01:00:22.789 --> 01:00:22.799 align:start position:0% now in a physical ring topology each 01:00:22.799 --> 01:00:24.710 align:start position:0% now in a physical ring topology each node<01:00:23.099> is<01:00:23.280> connected<01:00:23.640> directly<01:00:24.059> to<01:00:24.299> its 01:00:24.710 --> 01:00:24.720 align:start position:0% node is connected directly to its 01:00:24.720 --> 01:00:28.309 align:start position:0% node is connected directly to its upstream<01:00:25.319> and<01:00:25.619> its<01:00:26.099> Downstream<01:00:26.819> neighbors<01:00:27.660> so 01:00:28.309 --> 01:00:28.319 align:start position:0% upstream and its Downstream neighbors so 01:00:28.319 --> 01:00:29.750 align:start position:0% upstream and its Downstream neighbors so if<01:00:28.500> we're<01:00:28.619> looking<01:00:28.799> at<01:00:29.040> this<01:00:29.280> device<01:00:29.460> we'll 01:00:29.750 --> 01:00:29.760 align:start position:0% if we're looking at this device we'll 01:00:29.760 --> 01:00:31.910 align:start position:0% if we're looking at this device we'll call<01:00:29.940> it<01:00:30.119> a<01:00:30.359> those<01:00:30.839> are<01:00:31.020> the<01:00:31.140> upstream<01:00:31.680> and 01:00:31.910 --> 01:00:31.920 align:start position:0% call it a those are the upstream and 01:00:31.920 --> 01:00:33.530 align:start position:0% call it a those are the upstream and downstream<01:00:32.460> neighbors<01:00:32.819> it's<01:00:33.119> much<01:00:33.359> like 01:00:33.530 --> 01:00:33.540 align:start position:0% downstream neighbors it's much like 01:00:33.540 --> 01:00:36.049 align:start position:0% downstream neighbors it's much like water<01:00:33.900> in<01:00:34.260> an<01:00:34.500> actual<01:00:34.859> uh<01:00:35.280> like<01:00:35.520> River<01:00:35.760> or 01:00:36.049 --> 01:00:36.059 align:start position:0% water in an actual uh like River or 01:00:36.059 --> 01:00:38.870 align:start position:0% water in an actual uh like River or stream<01:00:36.299> the<01:00:37.140> flow<01:00:37.500> of<01:00:37.859> data<01:00:38.280> in<01:00:38.579> the<01:00:38.760> physical 01:00:38.870 --> 01:00:38.880 align:start position:0% stream the flow of data in the physical 01:00:38.880 --> 01:00:42.109 align:start position:0% stream the flow of data in the physical ring<01:00:39.299> topology<01:00:39.780> is<01:00:40.380> unidirectional<01:00:41.280> meaning 01:00:42.109 --> 01:00:42.119 align:start position:0% ring topology is unidirectional meaning 01:00:42.119 --> 01:00:45.470 align:start position:0% ring topology is unidirectional meaning it<01:00:42.480> only<01:00:42.660> goes<01:00:43.079> in<01:00:43.500> One<01:00:43.859> Direction 01:00:45.470 --> 01:00:45.480 align:start position:0% it only goes in One Direction 01:00:45.480 --> 01:00:49.250 align:start position:0% it only goes in One Direction so<01:00:46.079> the<01:00:46.380> terms<01:00:46.799> upstream<01:00:47.520> and<01:00:47.640> downstream<01:00:48.359> are 01:00:49.250 --> 01:00:49.260 align:start position:0% so the terms upstream and downstream are 01:00:49.260 --> 01:00:52.549 align:start position:0% so the terms upstream and downstream are only<01:00:49.500> used<01:00:49.920> in<01:00:50.460> the<01:00:50.819> ring<01:00:51.059> topology 01:00:52.549 --> 01:00:52.559 align:start position:0% only used in the ring topology 01:00:52.559 --> 01:00:54.289 align:start position:0% only used in the ring topology now<01:00:53.040> here's<01:00:53.400> the<01:00:53.520> positive<01:00:53.819> in<01:00:54.000> using<01:00:54.240> the 01:00:54.289 --> 01:00:54.299 align:start position:0% now here's the positive in using the 01:00:54.299 --> 01:00:57.049 align:start position:0% now here's the positive in using the ring<01:00:54.480> topology<01:00:54.900> because<01:00:55.680> data<01:00:56.339> is<01:00:56.579> received 01:00:57.049 --> 01:00:57.059 align:start position:0% ring topology because data is received 01:00:57.059 --> 01:01:00.770 align:start position:0% ring topology because data is received and<01:00:57.359> then<01:00:57.540> re-transmitted 01:01:00.770 --> 01:01:00.780 align:start position:0% 01:01:00.780 --> 01:01:03.829 align:start position:0% from<01:01:01.380> node<01:01:01.740> to<01:01:01.920> node<01:01:02.220> the<01:01:02.880> transmission<01:01:03.180> is 01:01:03.829 --> 01:01:03.839 align:start position:0% from node to node the transmission is 01:01:03.839 --> 01:01:05.270 align:start position:0% from node to node the transmission is guaranteed<01:01:04.380> to<01:01:04.559> be<01:01:04.680> strong<01:01:04.920> and<01:01:05.099> clear 01:01:05.270 --> 01:01:05.280 align:start position:0% guaranteed to be strong and clear 01:01:05.280 --> 01:01:07.670 align:start position:0% guaranteed to be strong and clear because<01:01:05.640> each<01:01:06.119> node<01:01:06.480> is<01:01:06.900> acting<01:01:07.200> as<01:01:07.319> a<01:01:07.500> sort<01:01:07.619> of 01:01:07.670 --> 01:01:07.680 align:start position:0% because each node is acting as a sort of 01:01:07.680 --> 01:01:10.730 align:start position:0% because each node is acting as a sort of like<01:01:07.859> booster<01:01:08.400> for<01:01:08.819> the<01:01:08.940> signal<01:01:09.319> uh<01:01:10.319> also 01:01:10.730 --> 01:01:10.740 align:start position:0% like booster for the signal uh also 01:01:10.740 --> 01:01:13.370 align:start position:0% like booster for the signal uh also because<01:01:10.980> the<01:01:11.339> data<01:01:11.640> can<01:01:11.940> only<01:01:12.119> be<01:01:12.420> transmitted 01:01:13.370 --> 01:01:13.380 align:start position:0% because the data can only be transmitted 01:01:13.380 --> 01:01:15.170 align:start position:0% because the data can only be transmitted unidirectionally<01:01:14.280> in<01:01:14.700> One<01:01:15.000> Direction 01:01:15.170 --> 01:01:15.180 align:start position:0% unidirectionally in One Direction 01:01:15.180 --> 01:01:17.270 align:start position:0% unidirectionally in One Direction there's<01:01:15.960> no<01:01:16.200> collisions<01:01:16.740> that<01:01:16.920> are<01:01:17.040> going<01:01:17.160> to 01:01:17.270 --> 01:01:17.280 align:start position:0% there's no collisions that are going to 01:01:17.280 --> 01:01:19.789 align:start position:0% there's no collisions that are going to happen<01:01:17.400> on<01:01:17.700> the<01:01:17.760> network<01:01:17.880> in<01:01:18.540> other<01:01:18.660> words<01:01:18.900> uh 01:01:19.789 --> 01:01:19.799 align:start position:0% happen on the network in other words uh 01:01:19.799 --> 01:01:22.549 align:start position:0% happen on the network in other words uh if<01:01:20.099> this<01:01:20.579> guy<01:01:20.760> can't<01:01:21.000> send<01:01:21.359> data<01:01:22.079> that<01:01:22.260> way<01:01:22.440> and 01:01:22.549 --> 01:01:22.559 align:start position:0% if this guy can't send data that way and 01:01:22.559 --> 01:01:23.870 align:start position:0% if this guy can't send data that way and then<01:01:22.740> this<01:01:22.920> guy's<01:01:23.099> sending<01:01:23.400> this<01:01:23.520> data<01:01:23.760> that 01:01:23.870 --> 01:01:23.880 align:start position:0% then this guy's sending this data that 01:01:23.880 --> 01:01:25.190 align:start position:0% then this guy's sending this data that way<01:01:24.000> and<01:01:24.180> then<01:01:24.299> they<01:01:24.540> sort<01:01:24.660> of<01:01:24.780> cancel<01:01:24.900> each 01:01:25.190 --> 01:01:25.200 align:start position:0% way and then they sort of cancel each 01:01:25.200 --> 01:01:27.170 align:start position:0% way and then they sort of cancel each other<01:01:25.380> out 01:01:27.170 --> 01:01:27.180 align:start position:0% other out 01:01:27.180 --> 01:01:31.069 align:start position:0% other out so<01:01:27.720> we're<01:01:27.839> going<01:01:28.020> to<01:01:28.079> eliminate<01:01:29.240> uh<01:01:30.240> you<01:01:30.960> know 01:01:31.069 --> 01:01:31.079 align:start position:0% so we're going to eliminate uh you know 01:01:31.079 --> 01:01:33.230 align:start position:0% so we're going to eliminate uh you know where<01:01:31.920> problems<01:01:32.460> can<01:01:32.640> occur<01:01:32.940> and<01:01:33.119> that's 01:01:33.230 --> 01:01:33.240 align:start position:0% where problems can occur and that's 01:01:33.240 --> 01:01:35.329 align:start position:0% where problems can occur and that's going<01:01:33.420> to<01:01:33.480> help<01:01:33.799> administrators<01:01:34.799> determine 01:01:35.329 --> 01:01:35.339 align:start position:0% going to help administrators determine 01:01:35.339 --> 01:01:37.190 align:start position:0% going to help administrators determine where<01:01:35.760> an<01:01:36.000> issue<01:01:36.299> is<01:01:36.480> occurring<01:01:36.839> if<01:01:37.079> they're 01:01:37.190 --> 01:01:37.200 align:start position:0% where an issue is occurring if they're 01:01:37.200 --> 01:01:39.049 align:start position:0% where an issue is occurring if they're having<01:01:37.380> an<01:01:37.559> issue<01:01:37.799> with<01:01:37.920> the<01:01:38.040> network<01:01:38.220> now 01:01:39.049 --> 01:01:39.059 align:start position:0% having an issue with the network now 01:01:39.059 --> 01:01:41.990 align:start position:0% having an issue with the network now negatively<01:01:39.660> if<01:01:40.319> one<01:01:40.559> of<01:01:40.680> these<01:01:40.920> nodes<01:01:41.280> goes 01:01:41.990 --> 01:01:42.000 align:start position:0% negatively if one of these nodes goes 01:01:42.000 --> 01:01:43.970 align:start position:0% negatively if one of these nodes goes down<01:01:42.180> on<01:01:42.599> the<01:01:42.720> network<01:01:42.839> the<01:01:43.500> entire<01:01:43.740> network 01:01:43.970 --> 01:01:43.980 align:start position:0% down on the network the entire network 01:01:43.980 --> 01:01:46.490 align:start position:0% down on the network the entire network potentially<01:01:44.579> goes<01:01:44.880> down<01:01:45.000> as<01:01:45.299> well<01:01:45.480> and<01:01:46.260> also 01:01:46.490 --> 01:01:46.500 align:start position:0% potentially goes down as well and also 01:01:46.500 --> 01:01:48.650 align:start position:0% potentially goes down as well and also because<01:01:46.680> data<01:01:47.220> can<01:01:47.339> only<01:01:47.460> transmit<01:01:48.119> in<01:01:48.480> One 01:01:48.650 --> 01:01:48.660 align:start position:0% because data can only transmit in One 01:01:48.660 --> 01:01:50.930 align:start position:0% because data can only transmit in One Direction<01:01:48.900> there's<01:01:49.799> a<01:01:50.099> high<01:01:50.280> potential<01:01:50.700> for 01:01:50.930 --> 01:01:50.940 align:start position:0% Direction there's a high potential for 01:01:50.940 --> 01:01:53.569 align:start position:0% Direction there's a high potential for data<01:01:51.299> to<01:01:51.480> take<01:01:51.660> a<01:01:52.020> longer<01:01:52.319> time<01:01:52.559> to<01:01:52.980> reach<01:01:53.280> its 01:01:53.569 --> 01:01:53.579 align:start position:0% data to take a longer time to reach its 01:01:53.579 --> 01:01:55.789 align:start position:0% data to take a longer time to reach its destination<01:01:54.000> because<01:01:54.660> obviously<01:01:55.200> if<01:01:55.500> I<01:01:55.680> want 01:01:55.789 --> 01:01:55.799 align:start position:0% destination because obviously if I want 01:01:55.799 --> 01:01:58.430 align:start position:0% destination because obviously if I want to<01:01:55.980> send<01:01:56.220> data 01:01:58.430 --> 01:01:58.440 align:start position:0% to send data 01:01:58.440 --> 01:02:00.770 align:start position:0% to send data to<01:01:58.980> this<01:01:59.160> guy<01:01:59.339> but<01:01:59.700> I'm<01:01:59.819> unidirectional<01:02:00.540> I 01:02:00.770 --> 01:02:00.780 align:start position:0% to this guy but I'm unidirectional I 01:02:00.780 --> 01:02:03.770 align:start position:0% to this guy but I'm unidirectional I actually<01:02:00.960> have<01:02:01.140> to<01:02:01.319> go<01:02:01.500> here<01:02:01.799> then<01:02:02.700> here<01:02:03.059> then 01:02:03.770 --> 01:02:03.780 align:start position:0% actually have to go here then here then 01:02:03.780 --> 01:02:05.870 align:start position:0% actually have to go here then here then here<01:02:04.140> whereas<01:02:04.799> if<01:02:04.980> I<01:02:05.099> was<01:02:05.220> using<01:02:05.520> a<01:02:05.700> star 01:02:05.870 --> 01:02:05.880 align:start position:0% here whereas if I was using a star 01:02:05.880 --> 01:02:09.349 align:start position:0% here whereas if I was using a star topology<01:02:06.359> I<01:02:06.900> could<01:02:07.020> reduce<01:02:07.319> that<01:02:07.740> by<01:02:08.040> one<01:02:08.760> A 01:02:09.349 --> 01:02:09.359 align:start position:0% topology I could reduce that by one A 01:02:09.359 --> 01:02:10.849 align:start position:0% topology I could reduce that by one A variation<01:02:09.720> by<01:02:10.079> the<01:02:10.200> way<01:02:10.319> of<01:02:10.500> this<01:02:10.680> physical 01:02:10.849 --> 01:02:10.859 align:start position:0% variation by the way of this physical 01:02:10.859 --> 01:02:13.490 align:start position:0% variation by the way of this physical ring<01:02:11.339> topology<01:02:11.700> that<01:02:12.420> attempts<01:02:12.900> to<01:02:13.020> correct 01:02:13.490 --> 01:02:13.500 align:start position:0% ring topology that attempts to correct 01:02:13.500 --> 01:02:15.589 align:start position:0% ring topology that attempts to correct some<01:02:13.740> of<01:02:13.859> the<01:02:14.040> limitations<01:02:14.460> is<01:02:15.059> what's<01:02:15.299> called 01:02:15.589 --> 01:02:15.599 align:start position:0% some of the limitations is what's called 01:02:15.599 --> 01:02:17.990 align:start position:0% some of the limitations is what's called a<01:02:16.079> dual<01:02:16.260> ring<01:02:16.559> topology 01:02:17.990 --> 01:02:18.000 align:start position:0% a dual ring topology 01:02:18.000 --> 01:02:21.710 align:start position:0% a dual ring topology I'm<01:02:18.359> just<01:02:18.540> drawing<01:02:18.900> that<01:02:19.079> out 01:02:21.710 --> 01:02:21.720 align:start position:0% 01:02:21.720 --> 01:02:23.990 align:start position:0% and<01:02:22.260> a<01:02:22.440> dual<01:02:22.619> ranked<01:02:23.040> apology<01:02:23.339> gives<01:02:23.640> a<01:02:23.819> sort 01:02:23.990 --> 01:02:24.000 align:start position:0% and a dual ranked apology gives a sort 01:02:24.000 --> 01:02:26.750 align:start position:0% and a dual ranked apology gives a sort of<01:02:24.119> redundancy<01:02:24.839> uh<01:02:25.740> to<01:02:25.920> the<01:02:26.099> network<01:02:26.280> by 01:02:26.750 --> 01:02:26.760 align:start position:0% of redundancy uh to the network by 01:02:26.760 --> 01:02:28.430 align:start position:0% of redundancy uh to the network by having<01:02:27.000> a<01:02:27.299> second<01:02:27.420> ring<01:02:27.839> either<01:02:28.020> on<01:02:28.319> the 01:02:28.430 --> 01:02:28.440 align:start position:0% having a second ring either on the 01:02:28.440 --> 01:02:30.410 align:start position:0% having a second ring either on the inside<01:02:28.559> or<01:02:29.040> the<01:02:29.220> outside<01:02:29.400> of<01:02:29.760> the<01:02:29.880> first<01:02:30.000> ring 01:02:30.410 --> 01:02:30.420 align:start position:0% inside or the outside of the first ring 01:02:30.420 --> 01:02:33.650 align:start position:0% inside or the outside of the first ring and<01:02:30.900> it<01:02:31.020> allows<01:02:31.380> data<01:02:31.799> to<01:02:32.579> flow<01:02:33.000> in<01:02:33.540> the 01:02:33.650 --> 01:02:33.660 align:start position:0% and it allows data to flow in the 01:02:33.660 --> 01:02:39.710 align:start position:0% and it allows data to flow in the opposite<01:02:34.140> direction 01:02:39.710 --> 01:02:39.720 align:start position:0% 01:02:39.720 --> 01:02:41.630 align:start position:0% so<01:02:40.319> this<01:02:40.500> can<01:02:40.680> double<01:02:40.859> the<01:02:41.160> speed<01:02:41.280> of<01:02:41.520> the 01:02:41.630 --> 01:02:41.640 align:start position:0% so this can double the speed of the 01:02:41.640 --> 01:02:43.490 align:start position:0% so this can double the speed of the network<01:02:41.760> by<01:02:42.240> sending<01:02:42.660> data<01:02:42.960> through<01:02:43.140> the<01:02:43.319> path 01:02:43.490 --> 01:02:43.500 align:start position:0% network by sending data through the path 01:02:43.500 --> 01:02:44.750 align:start position:0% network by sending data through the path that's<01:02:43.799> going<01:02:43.980> to<01:02:44.040> be<01:02:44.099> the<01:02:44.280> shortest<01:02:44.579> between 01:02:44.750 --> 01:02:44.760 align:start position:0% that's going to be the shortest between 01:02:44.760 --> 01:02:49.490 align:start position:0% that's going to be the shortest between nodes<01:02:45.180> so<01:02:46.079> if<01:02:46.740> a<01:02:46.920> wants<01:02:47.400> to<01:02:47.460> talk<01:02:47.700> to<01:02:48.119> C 01:02:49.490 --> 01:02:49.500 align:start position:0% nodes so if a wants to talk to C 01:02:49.500 --> 01:02:51.109 align:start position:0% nodes so if a wants to talk to C or<01:02:49.859> actually<01:02:50.099> we'll<01:02:50.280> call<01:02:50.400> that<01:02:50.579> b<01:02:50.760> just 01:02:51.109 --> 01:02:51.119 align:start position:0% or actually we'll call that b just 01:02:51.119 --> 01:02:52.309 align:start position:0% or actually we'll call that b just because<01:02:51.240> of<01:02:51.480> where<01:02:51.599> it<01:02:51.780> is<01:02:51.900> and<01:02:52.020> we'll<01:02:52.200> call 01:02:52.309 --> 01:02:52.319 align:start position:0% because of where it is and we'll call 01:02:52.319 --> 01:02:53.510 align:start position:0% because of where it is and we'll call this<01:02:52.500> one<01:02:52.619> c 01:02:53.510 --> 01:02:53.520 align:start position:0% this one c 01:02:53.520 --> 01:02:56.270 align:start position:0% this one c um<01:02:53.579> if<01:02:53.760> a<01:02:53.940> wants<01:02:54.299> to<01:02:54.420> talk<01:02:54.599> to<01:02:54.780> B<01:02:55.020> it<01:02:55.859> knows<01:02:56.160> to 01:02:56.270 --> 01:02:56.280 align:start position:0% um if a wants to talk to B it knows to 01:02:56.280 --> 01:02:58.970 align:start position:0% um if a wants to talk to B it knows to take<01:02:56.460> the<01:02:56.700> blue<01:02:57.000> line<01:02:57.299> as<01:02:57.720> opposed<01:02:58.079> to<01:02:58.140> the<01:02:58.799> red 01:02:58.970 --> 01:02:58.980 align:start position:0% take the blue line as opposed to the red 01:02:58.980 --> 01:03:00.890 align:start position:0% take the blue line as opposed to the red line<01:02:59.280> because<01:02:59.940> the<01:03:00.240> blue<01:03:00.299> line<01:03:00.540> is<01:03:00.720> going<01:03:00.839> to 01:03:00.890 --> 01:03:00.900 align:start position:0% line because the blue line is going to 01:03:00.900 --> 01:03:02.569 align:start position:0% line because the blue line is going to get<01:03:01.020> it<01:03:01.140> there<01:03:01.260> faster 01:03:02.569 --> 01:03:02.579 align:start position:0% get it there faster 01:03:02.579 --> 01:03:05.270 align:start position:0% get it there faster so<01:03:02.940> dual<01:03:03.240> Rings<01:03:03.599> also<01:03:04.200> allow<01:03:04.500> the<01:03:04.680> network<01:03:04.859> to 01:03:05.270 --> 01:03:05.280 align:start position:0% so dual Rings also allow the network to 01:03:05.280 --> 01:03:07.730 align:start position:0% so dual Rings also allow the network to continue<01:03:05.520> to<01:03:05.880> operate<01:03:06.240> if<01:03:06.900> one<01:03:07.140> of<01:03:07.200> these<01:03:07.380> goes 01:03:07.730 --> 01:03:07.740 align:start position:0% continue to operate if one of these goes 01:03:07.740 --> 01:03:09.470 align:start position:0% continue to operate if one of these goes down<01:03:07.920> which<01:03:08.520> I<01:03:08.760> think<01:03:08.940> you<01:03:09.180> could<01:03:09.299> probably 01:03:09.470 --> 01:03:09.480 align:start position:0% down which I think you could probably 01:03:09.480 --> 01:03:11.870 align:start position:0% down which I think you could probably see<01:03:09.720> from<01:03:10.020> this<01:03:10.200> so<01:03:10.680> if<01:03:10.859> the<01:03:11.040> outside<01:03:11.280> ring 01:03:11.870 --> 01:03:11.880 align:start position:0% see from this so if the outside ring 01:03:11.880 --> 01:03:13.730 align:start position:0% see from this so if the outside ring fails<01:03:12.299> and<01:03:12.480> the<01:03:12.660> inside<01:03:12.720> ring<01:03:13.200> can<01:03:13.500> actually 01:03:13.730 --> 01:03:13.740 align:start position:0% fails and the inside ring can actually 01:03:13.740 --> 01:03:17.510 align:start position:0% fails and the inside ring can actually pick<01:03:14.280> up<01:03:14.460> the<01:03:14.700> slack<01:03:15.000> for<01:03:15.180> the<01:03:15.299> outside<01:03:15.420> ring 01:03:17.510 --> 01:03:17.520 align:start position:0% pick up the slack for the outside ring 01:03:17.520 --> 01:03:20.450 align:start position:0% pick up the slack for the outside ring a<01:03:18.180> physical<01:03:18.359> tree<01:03:18.900> topology<01:03:19.500> it's<01:03:20.099> much<01:03:20.280> like 01:03:20.450 --> 01:03:20.460 align:start position:0% a physical tree topology it's much like 01:03:20.460 --> 01:03:22.190 align:start position:0% a physical tree topology it's much like its<01:03:20.700> namesake<01:03:21.059> as<01:03:21.299> as<01:03:21.480> you<01:03:21.660> can<01:03:21.720> see<01:03:21.839> it's<01:03:22.020> a 01:03:22.190 --> 01:03:22.200 align:start position:0% its namesake as as you can see it's a 01:03:22.200 --> 01:03:28.670 align:start position:0% its namesake as as you can see it's a tree<01:03:22.319> each<01:03:22.980> branch<01:03:23.400> of<01:03:23.700> the<01:03:23.940> tree 01:03:28.670 --> 01:03:28.680 align:start position:0% 01:03:28.680 --> 01:03:32.690 align:start position:0% can<01:03:29.099> only<01:03:29.280> receive<01:03:29.700> its<01:03:30.059> signal<01:03:30.359> for<01:03:31.079> from<01:03:31.700> its 01:03:32.690 --> 01:03:32.700 align:start position:0% can only receive its signal for from its 01:03:32.700 --> 01:03:35.450 align:start position:0% can only receive its signal for from its parent<01:03:32.819> node<01:03:33.299> or<01:03:33.780> its<01:03:34.079> linked<01:03:34.380> branch 01:03:35.450 --> 01:03:35.460 align:start position:0% parent node or its linked branch 01:03:35.460 --> 01:03:39.230 align:start position:0% parent node or its linked branch right<01:03:35.940> so<01:03:36.359> all<01:03:36.720> of<01:03:36.839> these<01:03:37.260> can<01:03:37.740> only<01:03:38.040> receive<01:03:38.760> a 01:03:39.230 --> 01:03:39.240 align:start position:0% right so all of these can only receive a 01:03:39.240 --> 01:03:41.329 align:start position:0% right so all of these can only receive a signal<01:03:39.599> from 01:03:41.329 --> 01:03:41.339 align:start position:0% signal from 01:03:41.339 --> 01:03:44.329 align:start position:0% signal from this<01:03:41.819> guy<01:03:42.079> the<01:03:43.079> root<01:03:43.200> node<01:03:43.680> is<01:03:43.920> what<01:03:44.040> we<01:03:44.220> call 01:03:44.329 --> 01:03:44.339 align:start position:0% this guy the root node is what we call 01:03:44.339 --> 01:03:47.450 align:start position:0% this guy the root node is what we call the<01:03:44.700> top<01:03:44.880> portion<01:03:45.540> of<01:03:46.440> the<01:03:46.619> network<01:03:46.740> and<01:03:47.280> it 01:03:47.450 --> 01:03:47.460 align:start position:0% the top portion of the network and it 01:03:47.460 --> 01:03:49.910 align:start position:0% the top portion of the network and it does<01:03:47.640> not<01:03:47.819> have<01:03:48.119> a<01:03:48.299> parent<01:03:48.480> so<01:03:48.780> it<01:03:48.960> is<01:03:49.140> the<01:03:49.440> root 01:03:49.910 --> 01:03:49.920 align:start position:0% does not have a parent so it is the root 01:03:49.920 --> 01:03:52.309 align:start position:0% does not have a parent so it is the root just<01:03:50.220> like<01:03:50.400> a<01:03:50.579> tree<01:03:50.760> it's<01:03:51.119> the<01:03:51.299> roots<01:03:51.599> it's 01:03:52.309 --> 01:03:52.319 align:start position:0% just like a tree it's the roots it's 01:03:52.319 --> 01:03:54.410 align:start position:0% just like a tree it's the roots it's directly<01:03:52.740> connected<01:03:53.220> to<01:03:53.520> each<01:03:53.700> of<01:03:53.880> the<01:03:54.059> child 01:03:54.410 --> 01:03:54.420 align:start position:0% directly connected to each of the child 01:03:54.420 --> 01:03:58.190 align:start position:0% directly connected to each of the child nodes<01:03:54.960> that's<01:03:55.200> what<01:03:55.380> these<01:03:55.619> would<01:03:55.740> be<01:03:55.859> called 01:03:58.190 --> 01:03:58.200 align:start position:0% 01:03:58.200 --> 01:04:00.950 align:start position:0% by<01:03:58.859> a<01:03:59.099> point-to-point<01:03:59.700> connection 01:04:00.950 --> 01:04:00.960 align:start position:0% by a point-to-point connection 01:04:00.960 --> 01:04:02.809 align:start position:0% by a point-to-point connection now<01:04:01.380> depending<01:04:01.680> on<01:04:01.799> how<01:04:01.980> many<01:04:02.099> levels<01:04:02.579> you 01:04:02.809 --> 01:04:02.819 align:start position:0% now depending on how many levels you 01:04:02.819 --> 01:04:04.789 align:start position:0% now depending on how many levels you have<01:04:02.940> here<01:04:03.180> and<01:04:03.420> we<01:04:03.540> can<01:04:03.660> see<01:04:03.780> we<01:04:04.020> have<01:04:04.200> three 01:04:04.789 --> 01:04:04.799 align:start position:0% have here and we can see we have three 01:04:04.799 --> 01:04:08.150 align:start position:0% have here and we can see we have three levels<01:04:05.280> here<01:04:05.900> uh<01:04:06.900> your<01:04:07.200> tree<01:04:07.380> topology<01:04:07.859> is 01:04:08.150 --> 01:04:08.160 align:start position:0% levels here uh your tree topology is 01:04:08.160 --> 01:04:11.030 align:start position:0% levels here uh your tree topology is gonna<01:04:08.280> have<01:04:08.520> is<01:04:08.760> gonna<01:04:09.260> dictate<01:04:10.260> what<01:04:10.859> the 01:04:11.030 --> 01:04:11.040 align:start position:0% gonna have is gonna dictate what the 01:04:11.040 --> 01:04:13.609 align:start position:0% gonna have is gonna dictate what the what<01:04:11.280> we<01:04:11.400> call<01:04:11.579> the<01:04:11.819> branching<01:04:12.480> factor<01:04:13.200> is<01:04:13.380> and 01:04:13.609 --> 01:04:13.619 align:start position:0% what we call the branching factor is and 01:04:13.619 --> 01:04:15.530 align:start position:0% what we call the branching factor is and this<01:04:13.799> might<01:04:13.980> be<01:04:14.160> a<01:04:14.460> little<01:04:14.579> beyond<01:04:15.059> the<01:04:15.299> scope 01:04:15.530 --> 01:04:15.540 align:start position:0% this might be a little beyond the scope 01:04:15.540 --> 01:04:17.089 align:start position:0% this might be a little beyond the scope of<01:04:15.720> the<01:04:15.900> exam<01:04:16.200> but<01:04:16.380> I'm<01:04:16.500> going<01:04:16.619> to<01:04:16.740> cover<01:04:16.859> it 01:04:17.089 --> 01:04:17.099 align:start position:0% of the exam but I'm going to cover it 01:04:17.099 --> 01:04:19.430 align:start position:0% of the exam but I'm going to cover it here<01:04:17.280> anyway<01:04:17.520> the<01:04:18.480> higher<01:04:18.839> the<01:04:18.960> branching 01:04:19.430 --> 01:04:19.440 align:start position:0% here anyway the higher the branching 01:04:19.440 --> 01:04:21.589 align:start position:0% here anyway the higher the branching Factor<01:04:19.920> the<01:04:20.760> longer<01:04:21.000> it's<01:04:21.180> going<01:04:21.359> to<01:04:21.480> take 01:04:21.589 --> 01:04:21.599 align:start position:0% Factor the longer it's going to take 01:04:21.599 --> 01:04:23.270 align:start position:0% Factor the longer it's going to take from<01:04:21.839> data<01:04:22.200> to<01:04:22.260> go<01:04:22.440> from<01:04:22.619> one<01:04:22.859> node<01:04:23.099> through 01:04:23.270 --> 01:04:23.280 align:start position:0% from data to go from one node through 01:04:23.280 --> 01:04:24.530 align:start position:0% from data to go from one node through the<01:04:23.460> network<01:04:23.520> to<01:04:23.819> the<01:04:24.000> other<01:04:24.059> because 01:04:24.530 --> 01:04:24.540 align:start position:0% the network to the other because 01:04:24.540 --> 01:04:26.630 align:start position:0% the network to the other because obviously<01:04:25.079> if<01:04:25.319> this<01:04:25.559> needs<01:04:25.859> to<01:04:25.980> talk<01:04:26.160> to<01:04:26.400> this 01:04:26.630 --> 01:04:26.640 align:start position:0% obviously if this needs to talk to this 01:04:26.640 --> 01:04:30.289 align:start position:0% obviously if this needs to talk to this then<01:04:27.420> right<01:04:28.140> we're<01:04:28.440> going<01:04:28.559> to<01:04:28.680> have 01:04:30.289 --> 01:04:30.299 align:start position:0% then right we're going to have 01:04:30.299 --> 01:04:32.450 align:start position:0% then right we're going to have quite<01:04:30.960> a<01:04:31.079> bit<01:04:31.200> of<01:04:31.319> data<01:04:31.619> that<01:04:31.799> it<01:04:31.920> has<01:04:32.099> to<01:04:32.220> go 01:04:32.450 --> 01:04:32.460 align:start position:0% quite a bit of data that it has to go 01:04:32.460 --> 01:04:34.370 align:start position:0% quite a bit of data that it has to go through 01:04:34.370 --> 01:04:34.380 align:start position:0% through 01:04:34.380 --> 01:04:36.470 align:start position:0% through a<01:04:35.040> positive<01:04:35.400> aspect<01:04:35.760> of<01:04:36.000> this<01:04:36.240> entire 01:04:36.470 --> 01:04:36.480 align:start position:0% a positive aspect of this entire 01:04:36.480 --> 01:04:38.690 align:start position:0% a positive aspect of this entire topology<01:04:36.960> by<01:04:37.260> the<01:04:37.380> way<01:04:37.440> is<01:04:37.980> that<01:04:38.099> because<01:04:38.280> each 01:04:38.690 --> 01:04:38.700 align:start position:0% topology by the way is that because each 01:04:38.700 --> 01:04:41.510 align:start position:0% topology by the way is that because each level<01:04:38.940> is<01:04:39.359> connected<01:04:39.839> only<01:04:40.380> to<01:04:41.040> its<01:04:41.400> parent 01:04:41.510 --> 01:04:41.520 align:start position:0% level is connected only to its parent 01:04:41.520 --> 01:04:44.510 align:start position:0% level is connected only to its parent and<01:04:41.940> its<01:04:42.240> child<01:04:42.420> nodes 01:04:44.510 --> 01:04:44.520 align:start position:0% and its child nodes 01:04:44.520 --> 01:04:46.670 align:start position:0% and its child nodes it's<01:04:44.940> very<01:04:45.180> easy<01:04:45.420> to<01:04:45.720> troubleshoot<01:04:46.260> where<01:04:46.500> the 01:04:46.670 --> 01:04:46.680 align:start position:0% it's very easy to troubleshoot where the 01:04:46.680 --> 01:04:49.130 align:start position:0% it's very easy to troubleshoot where the problems<01:04:47.099> in<01:04:47.520> the<01:04:47.700> network<01:04:47.760> occur<01:04:48.359> because 01:04:49.130 --> 01:04:49.140 align:start position:0% problems in the network occur because 01:04:49.140 --> 01:04:51.430 align:start position:0% problems in the network occur because obviously<01:04:50.099> if<01:04:50.460> you're<01:04:50.579> having<01:04:50.819> a<01:04:51.119> problem 01:04:51.430 --> 01:04:51.440 align:start position:0% obviously if you're having a problem 01:04:51.440 --> 01:04:54.230 align:start position:0% obviously if you're having a problem with<01:04:52.440> you<01:04:52.859> know<01:04:52.980> this<01:04:53.579> connection<01:04:53.760> over<01:04:54.059> here 01:04:54.230 --> 01:04:54.240 align:start position:0% with you know this connection over here 01:04:54.240 --> 01:04:55.970 align:start position:0% with you know this connection over here you<01:04:54.660> know<01:04:54.839> that<01:04:55.079> none<01:04:55.380> of<01:04:55.500> these<01:04:55.740> have 01:04:55.970 --> 01:04:55.980 align:start position:0% you know that none of these have 01:04:55.980 --> 01:05:00.829 align:start position:0% you know that none of these have anything<01:04:56.160> to<01:04:56.460> do<01:04:56.579> with<01:04:56.819> it 01:05:00.829 --> 01:05:00.839 align:start position:0% 01:05:00.839 --> 01:05:02.990 align:start position:0% it's<01:05:01.500> also<01:05:01.799> the<01:05:02.040> other<01:05:02.160> benefit<01:05:02.400> is<01:05:02.760> it's 01:05:02.990 --> 01:05:03.000 align:start position:0% it's also the other benefit is it's 01:05:03.000 --> 01:05:04.309 align:start position:0% it's also the other benefit is it's really<01:05:03.299> scalable 01:05:04.309 --> 01:05:04.319 align:start position:0% really scalable 01:05:04.319 --> 01:05:06.770 align:start position:0% really scalable remember<01:05:04.740> that<01:05:05.099> word<01:05:05.339> because<01:05:05.880> obviously<01:05:06.540> if 01:05:06.770 --> 01:05:06.780 align:start position:0% remember that word because obviously if 01:05:06.780 --> 01:05:09.170 align:start position:0% remember that word because obviously if I<01:05:06.960> want<01:05:07.079> to<01:05:07.200> add<01:05:07.500> another<01:05:08.040> Network<01:05:08.339> I<01:05:08.819> can<01:05:09.000> just 01:05:09.170 --> 01:05:09.180 align:start position:0% I want to add another Network I can just 01:05:09.180 --> 01:05:11.569 align:start position:0% I want to add another Network I can just add<01:05:09.420> it<01:05:09.599> either<01:05:09.839> here<01:05:10.619> or<01:05:10.920> I<01:05:11.099> can<01:05:11.160> add<01:05:11.339> another 01:05:11.569 --> 01:05:11.579 align:start position:0% add it either here or I can add another 01:05:11.579 --> 01:05:13.789 align:start position:0% add it either here or I can add another child<01:05:11.940> here<01:05:12.420> and<01:05:12.900> then<01:05:13.020> just<01:05:13.200> sort<01:05:13.380> of<01:05:13.500> Branch 01:05:13.789 --> 01:05:13.799 align:start position:0% child here and then just sort of Branch 01:05:13.799 --> 01:05:16.970 align:start position:0% child here and then just sort of Branch off<01:05:14.099> there<01:05:14.940> now<01:05:15.240> negatively<01:05:15.960> if<01:05:16.799> the 01:05:16.970 --> 01:05:16.980 align:start position:0% off there now negatively if the 01:05:16.980 --> 01:05:19.069 align:start position:0% off there now negatively if the connection<01:05:17.160> should<01:05:17.579> be<01:05:17.700> interrupted<01:05:18.240> or<01:05:18.420> if<01:05:18.780> a 01:05:19.069 --> 01:05:19.079 align:start position:0% connection should be interrupted or if a 01:05:19.079 --> 01:05:21.289 align:start position:0% connection should be interrupted or if a node<01:05:19.380> that's<01:05:19.920> sort<01:05:20.099> of<01:05:20.280> a<01:05:20.460> higher<01:05:20.819> level<01:05:21.000> and 01:05:21.289 --> 01:05:21.299 align:start position:0% node that's sort of a higher level and 01:05:21.299 --> 01:05:23.450 align:start position:0% node that's sort of a higher level and the<01:05:21.480> change<01:05:21.599> should<01:05:21.960> go<01:05:22.140> down<01:05:22.380> then<01:05:22.920> all<01:05:23.160> these 01:05:23.450 --> 01:05:23.460 align:start position:0% the change should go down then all these 01:05:23.460 --> 01:05:25.370 align:start position:0% the change should go down then all these subordinate<01:05:24.000> nodes<01:05:24.240> would<01:05:24.480> suffer<01:05:24.839> so<01:05:25.020> if<01:05:25.200> the 01:05:25.370 --> 01:05:25.380 align:start position:0% subordinate nodes would suffer so if the 01:05:25.380 --> 01:05:26.630 align:start position:0% subordinate nodes would suffer so if the connection<01:05:25.500> between<01:05:25.799> the<01:05:26.040> root<01:05:26.339> and<01:05:26.460> their 01:05:26.630 --> 01:05:26.640 align:start position:0% connection between the root and their 01:05:26.640 --> 01:05:28.789 align:start position:0% connection between the root and their children<01:05:27.180> goes<01:05:27.960> down<01:05:28.079> we're<01:05:28.319> going<01:05:28.440> to<01:05:28.619> be<01:05:28.680> in 01:05:28.789 --> 01:05:28.799 align:start position:0% children goes down we're going to be in 01:05:28.799 --> 01:05:30.470 align:start position:0% children goes down we're going to be in major<01:05:29.040> issue<01:05:29.400> because<01:05:29.579> now<01:05:29.819> none<01:05:30.180> of<01:05:30.299> these 01:05:30.470 --> 01:05:30.480 align:start position:0% major issue because now none of these 01:05:30.480 --> 01:05:33.049 align:start position:0% major issue because now none of these can<01:05:30.660> talk<01:05:30.859> obviously<01:05:31.859> if<01:05:32.099> this<01:05:32.339> computer<01:05:32.520> goes 01:05:33.049 --> 01:05:33.059 align:start position:0% can talk obviously if this computer goes 01:05:33.059 --> 01:05:34.010 align:start position:0% can talk obviously if this computer goes down 01:05:34.010 --> 01:05:34.020 align:start position:0% down 01:05:34.020 --> 01:05:35.930 align:start position:0% down then<01:05:34.619> none<01:05:34.920> of<01:05:34.980> these<01:05:35.220> will<01:05:35.339> be<01:05:35.520> able<01:05:35.640> to<01:05:35.760> talk 01:05:35.930 --> 01:05:35.940 align:start position:0% then none of these will be able to talk 01:05:35.940 --> 01:05:37.849 align:start position:0% then none of these will be able to talk to<01:05:36.119> the<01:05:36.299> rest<01:05:36.359> of<01:05:36.540> the<01:05:36.599> network<01:05:36.780> either<01:05:37.200> so 01:05:37.849 --> 01:05:37.859 align:start position:0% to the rest of the network either so 01:05:37.859 --> 01:05:41.390 align:start position:0% to the rest of the network either so this<01:05:38.099> is<01:05:38.280> a<01:05:38.640> a<01:05:39.000> problem<01:05:39.960> with<01:05:40.319> it<01:05:40.500> it<01:05:40.920> is<01:05:41.160> a 01:05:41.390 --> 01:05:41.400 align:start position:0% this is a a problem with it it is a 01:05:41.400 --> 01:05:44.569 align:start position:0% this is a a problem with it it is a variation<01:05:41.819> by<01:05:42.240> the<01:05:42.359> way<01:05:42.480> of<01:05:43.319> the<01:05:43.680> bus<01:05:43.980> topology 01:05:44.569 --> 01:05:44.579 align:start position:0% variation by the way of the bus topology 01:05:44.579 --> 01:05:47.809 align:start position:0% variation by the way of the bus topology so<01:05:45.119> again<01:05:45.420> if<01:05:46.200> the<01:05:46.440> backbone<01:05:46.980> fails<01:05:47.520> then 01:05:47.809 --> 01:05:47.819 align:start position:0% so again if the backbone fails then 01:05:47.819 --> 01:05:49.670 align:start position:0% so again if the backbone fails then nothing<01:05:48.180> else<01:05:48.420> is<01:05:48.599> going<01:05:48.780> to<01:05:48.960> work 01:05:49.670 --> 01:05:49.680 align:start position:0% nothing else is going to work 01:05:49.680 --> 01:05:52.789 align:start position:0% nothing else is going to work now<01:05:50.220> with<01:05:50.460> a<01:05:50.700> physical<01:05:50.880> mesh<01:05:51.480> topology<01:05:51.900> each 01:05:52.789 --> 01:05:52.799 align:start position:0% now with a physical mesh topology each 01:05:52.799 --> 01:05:54.650 align:start position:0% now with a physical mesh topology each node<01:05:53.040> in<01:05:53.220> the<01:05:53.400> network<01:05:53.579> is<01:05:54.240> directly 01:05:54.650 --> 01:05:54.660 align:start position:0% node in the network is directly 01:05:54.660 --> 01:05:56.569 align:start position:0% node in the network is directly connected<01:05:55.140> to<01:05:55.380> every<01:05:55.619> other<01:05:55.740> node<01:05:56.160> on<01:05:56.460> the 01:05:56.569 --> 01:05:56.579 align:start position:0% connected to every other node on the 01:05:56.579 --> 01:05:59.630 align:start position:0% connected to every other node on the network<01:05:56.839> so<01:05:57.839> if<01:05:58.140> we<01:05:58.319> call<01:05:58.500> this<01:05:58.740> computer<01:05:58.980> a 01:05:59.630 --> 01:05:59.640 align:start position:0% network so if we call this computer a 01:05:59.640 --> 01:06:03.349 align:start position:0% network so if we call this computer a you<01:06:00.359> can<01:06:00.540> see<01:06:00.799> it's<01:06:01.799> connected<01:06:02.220> to 01:06:03.349 --> 01:06:03.359 align:start position:0% you can see it's connected to 01:06:03.359 --> 01:06:06.410 align:start position:0% you can see it's connected to B<01:06:03.839> it's<01:06:04.500> connected<01:06:04.980> directly<01:06:05.400> to 01:06:06.410 --> 01:06:06.420 align:start position:0% B it's connected directly to 01:06:06.420 --> 01:06:09.530 align:start position:0% B it's connected directly to C<01:06:06.960> and<01:06:07.859> it's<01:06:08.040> also<01:06:08.339> connected<01:06:08.700> directly<01:06:09.059> to<01:06:09.299> D 01:06:09.530 --> 01:06:09.540 align:start position:0% C and it's also connected directly to D 01:06:09.540 --> 01:06:11.930 align:start position:0% C and it's also connected directly to D so<01:06:10.319> for<01:06:10.740> every<01:06:10.980> computer<01:06:11.339> on<01:06:11.700> the<01:06:11.819> network 01:06:11.930 --> 01:06:11.940 align:start position:0% so for every computer on the network 01:06:11.940 --> 01:06:13.250 align:start position:0% so for every computer on the network it's<01:06:12.359> for<01:06:12.540> every<01:06:12.720> node<01:06:12.960> on<01:06:13.079> the<01:06:13.200> network 01:06:13.250 --> 01:06:13.260 align:start position:0% it's for every node on the network 01:06:13.260 --> 01:06:14.809 align:start position:0% it's for every node on the network rather<01:06:13.559> it's<01:06:13.740> connected<01:06:14.160> to<01:06:14.400> every<01:06:14.640> other 01:06:14.809 --> 01:06:14.819 align:start position:0% rather it's connected to every other 01:06:14.819 --> 01:06:16.849 align:start position:0% rather it's connected to every other node 01:06:16.849 --> 01:06:16.859 align:start position:0% node 01:06:16.859 --> 01:06:20.750 align:start position:0% node as<01:06:17.520> a<01:06:17.760> result<01:06:17.940> because<01:06:18.480> each<01:06:19.020> connection<01:06:19.760> is 01:06:20.750 --> 01:06:20.760 align:start position:0% as a result because each connection is 01:06:20.760 --> 01:06:22.809 align:start position:0% as a result because each connection is similar<01:06:21.180> to<01:06:21.420> like<01:06:21.599> a<01:06:21.780> point-to-point<01:06:22.260> network 01:06:22.809 --> 01:06:22.819 align:start position:0% similar to like a point-to-point network 01:06:22.819 --> 01:06:25.910 align:start position:0% similar to like a point-to-point network uh<01:06:23.819> communication<01:06:24.599> between<01:06:25.020> multiple<01:06:25.619> nodes 01:06:25.910 --> 01:06:25.920 align:start position:0% uh communication between multiple nodes 01:06:25.920 --> 01:06:28.430 align:start position:0% uh communication between multiple nodes can<01:06:26.220> happen<01:06:26.400> at<01:06:26.700> the<01:06:26.819> same<01:06:27.000> time<01:06:27.299> and<01:06:27.960> so<01:06:28.140> it's 01:06:28.430 --> 01:06:28.440 align:start position:0% can happen at the same time and so it's 01:06:28.440 --> 01:06:31.549 align:start position:0% can happen at the same time and so it's very<01:06:29.099> efficient<01:06:29.880> highly<01:06:30.720> reliable<01:06:31.140> and<01:06:31.380> has 01:06:31.549 --> 01:06:31.559 align:start position:0% very efficient highly reliable and has 01:06:31.559 --> 01:06:34.069 align:start position:0% very efficient highly reliable and has minimal<01:06:31.980> data<01:06:32.400> congestion<01:06:32.880> because<01:06:33.359> B<01:06:33.720> and<01:06:33.900> D 01:06:34.069 --> 01:06:34.079 align:start position:0% minimal data congestion because B and D 01:06:34.079 --> 01:06:36.589 align:start position:0% minimal data congestion because B and D can<01:06:34.260> talk<01:06:34.440> at<01:06:34.619> the<01:06:34.799> same<01:06:34.920> time<01:06:35.099> as<01:06:35.339> a<01:06:35.579> and<01:06:35.760> C<01:06:36.000> now 01:06:36.589 --> 01:06:36.599 align:start position:0% can talk at the same time as a and C now 01:06:36.599 --> 01:06:38.569 align:start position:0% can talk at the same time as a and C now for<01:06:36.839> the<01:06:36.960> same<01:06:37.140> reason<01:06:37.440> these<01:06:38.280> types<01:06:38.460> of 01:06:38.569 --> 01:06:38.579 align:start position:0% for the same reason these types of 01:06:38.579 --> 01:06:40.490 align:start position:0% for the same reason these types of topologies<01:06:39.119> the<01:06:39.299> mesh<01:06:39.539> topologies<01:06:40.079> are<01:06:40.319> very 01:06:40.490 --> 01:06:40.500 align:start position:0% topologies the mesh topologies are very 01:06:40.500 --> 01:06:42.710 align:start position:0% topologies the mesh topologies are very difficult<01:06:40.799> to<01:06:41.160> manage<01:06:41.460> and<01:06:42.119> to<01:06:42.359> maintain 01:06:42.710 --> 01:06:42.720 align:start position:0% difficult to manage and to maintain 01:06:42.720 --> 01:06:44.870 align:start position:0% difficult to manage and to maintain because<01:06:43.140> each<01:06:43.740> additional<01:06:44.220> node<01:06:44.640> that's 01:06:44.870 --> 01:06:44.880 align:start position:0% because each additional node that's 01:06:44.880 --> 01:06:50.270 align:start position:0% because each additional node that's added<01:06:45.859> uh<01:06:47.000> requires<01:06:48.000> you<01:06:48.240> to<01:06:48.720> connect<01:06:49.280> other 01:06:50.270 --> 01:06:50.280 align:start position:0% added uh requires you to connect other 01:06:50.280 --> 01:06:52.250 align:start position:0% added uh requires you to connect other you<01:06:50.760> know<01:06:50.819> every<01:06:51.059> single<01:06:51.359> other<01:06:51.539> node<01:06:51.900> to<01:06:52.140> it 01:06:52.250 --> 01:06:52.260 align:start position:0% you know every single other node to it 01:06:52.260 --> 01:06:54.829 align:start position:0% you know every single other node to it so<01:06:52.559> if<01:06:52.740> I<01:06:52.859> wanted<01:06:53.039> to<01:06:53.280> add<01:06:53.579> an<01:06:54.000> e<01:06:54.240> for<01:06:54.539> instance 01:06:54.829 --> 01:06:54.839 align:start position:0% so if I wanted to add an e for instance 01:06:54.839 --> 01:06:58.910 align:start position:0% so if I wanted to add an e for instance look<01:06:55.500> at<01:06:55.619> all<01:06:55.859> of<01:06:55.980> the<01:06:56.220> connections<01:06:56.760> I<01:06:57.299> now 01:06:58.910 --> 01:06:58.920 align:start position:0% look at all of the connections I now 01:06:58.920 --> 01:07:01.970 align:start position:0% look at all of the connections I now have<01:06:59.700> to<01:06:59.940> add<01:07:00.359> to<01:07:00.900> this<01:07:01.200> already<01:07:01.380> existing 01:07:01.970 --> 01:07:01.980 align:start position:0% have to add to this already existing 01:07:01.980 --> 01:07:04.190 align:start position:0% have to add to this already existing Network<01:07:02.220> so<01:07:03.180> to<01:07:03.299> alleviate<01:07:03.780> some<01:07:03.900> of<01:07:04.020> the 01:07:04.190 --> 01:07:04.200 align:start position:0% Network so to alleviate some of the 01:07:04.200 --> 01:07:06.829 align:start position:0% Network so to alleviate some of the negatives<01:07:04.559> of<01:07:04.799> this<01:07:05.039> type<01:07:05.160> of<01:07:05.339> network 01:07:06.829 --> 01:07:06.839 align:start position:0% negatives of this type of network 01:07:06.839 --> 01:07:08.450 align:start position:0% negatives of this type of network um<01:07:06.900> it's<01:07:07.319> uh 01:07:08.450 --> 01:07:08.460 align:start position:0% um it's uh 01:07:08.460 --> 01:07:09.950 align:start position:0% um it's uh we<01:07:08.819> sometimes<01:07:09.059> have<01:07:09.299> what's<01:07:09.420> called<01:07:09.660> a 01:07:09.950 --> 01:07:09.960 align:start position:0% we sometimes have what's called a 01:07:09.960 --> 01:07:12.589 align:start position:0% we sometimes have what's called a partial<01:07:10.319> mesh<01:07:10.740> the<01:07:11.220> partial<01:07:11.579> mesh<01:07:12.000> basically 01:07:12.589 --> 01:07:12.599 align:start position:0% partial mesh the partial mesh basically 01:07:12.599 --> 01:07:14.750 align:start position:0% partial mesh the partial mesh basically means<01:07:12.960> only<01:07:13.319> specific<01:07:13.920> nodes<01:07:14.280> on<01:07:14.460> the<01:07:14.579> network 01:07:14.750 --> 01:07:14.760 align:start position:0% means only specific nodes on the network 01:07:14.760 --> 01:07:17.270 align:start position:0% means only specific nodes on the network have<01:07:15.180> to<01:07:15.299> have<01:07:15.480> direct<01:07:15.720> links<01:07:16.200> and<01:07:16.920> this<01:07:17.220> is 01:07:17.270 --> 01:07:17.280 align:start position:0% have to have direct links and this is 01:07:17.280 --> 01:07:18.289 align:start position:0% have to have direct links and this is sort<01:07:17.460> of<01:07:17.579> where<01:07:17.700> we're<01:07:17.819> going<01:07:17.940> to<01:07:18.000> go<01:07:18.059> when<01:07:18.180> we 01:07:18.289 --> 01:07:18.299 align:start position:0% sort of where we're going to go when we 01:07:18.299 --> 01:07:20.210 align:start position:0% sort of where we're going to go when we get<01:07:18.420> into<01:07:18.480> hybrid<01:07:18.960> topologies 01:07:20.210 --> 01:07:20.220 align:start position:0% get into hybrid topologies 01:07:20.220 --> 01:07:21.910 align:start position:0% get into hybrid topologies it's<01:07:20.460> going<01:07:20.700> to<01:07:20.700> limit<01:07:20.880> the<01:07:21.240> number<01:07:21.420> of 01:07:21.910 --> 01:07:21.920 align:start position:0% it's going to limit the number of 01:07:21.920 --> 01:07:24.109 align:start position:0% it's going to limit the number of connections<01:07:22.920> that<01:07:23.520> are<01:07:23.640> necessary 01:07:24.109 --> 01:07:24.119 align:start position:0% connections that are necessary 01:07:24.119 --> 01:07:26.690 align:start position:0% connections that are necessary throughout<01:07:24.599> the<01:07:24.780> network<01:07:24.960> so<01:07:25.740> a<01:07:25.980> partial<01:07:26.280> mesh 01:07:26.690 --> 01:07:26.700 align:start position:0% throughout the network so a partial mesh 01:07:26.700 --> 01:07:28.309 align:start position:0% throughout the network so a partial mesh topology<01:07:27.119> would<01:07:27.420> be<01:07:27.539> useful<01:07:27.780> if<01:07:27.960> your<01:07:28.140> network 01:07:28.309 --> 01:07:28.319 align:start position:0% topology would be useful if your network 01:07:28.319 --> 01:07:31.670 align:start position:0% topology would be useful if your network is<01:07:28.980> comprised<01:07:29.640> of<01:07:29.819> say<01:07:30.059> like<01:07:30.299> end<01:07:30.660> nodes<01:07:31.020> that 01:07:31.670 --> 01:07:31.680 align:start position:0% is comprised of say like end nodes that 01:07:31.680 --> 01:07:33.589 align:start position:0% is comprised of say like end nodes that don't<01:07:31.859> need<01:07:32.280> a<01:07:32.700> connection<01:07:32.880> to<01:07:33.240> all<01:07:33.420> the<01:07:33.480> other 01:07:33.589 --> 01:07:33.599 align:start position:0% don't need a connection to all the other 01:07:33.599 --> 01:07:35.930 align:start position:0% don't need a connection to all the other nodes<01:07:33.839> on<01:07:34.020> the<01:07:34.140> network<01:07:34.319> but<01:07:35.160> it<01:07:35.400> still<01:07:35.579> allows 01:07:35.930 --> 01:07:35.940 align:start position:0% nodes on the network but it still allows 01:07:35.940 --> 01:07:39.289 align:start position:0% nodes on the network but it still allows high<01:07:36.599> end<01:07:37.079> devices<01:07:37.740> to<01:07:38.160> maintain<01:07:38.520> the<01:07:38.880> maximum 01:07:39.289 --> 01:07:39.299 align:start position:0% high end devices to maintain the maximum 01:07:39.299 --> 01:07:40.910 align:start position:0% high end devices to maintain the maximum transfer<01:07:39.720> rates<01:07:39.960> and<01:07:40.260> the<01:07:40.380> maximum<01:07:40.619> amount<01:07:40.740> of 01:07:40.910 --> 01:07:40.920 align:start position:0% transfer rates and the maximum amount of 01:07:40.920 --> 01:07:43.010 align:start position:0% transfer rates and the maximum amount of efficiency<01:07:41.339> and<01:07:41.520> reliability<01:07:42.059> the 01:07:43.010 --> 01:07:43.020 align:start position:0% efficiency and reliability the 01:07:43.020 --> 01:07:44.930 align:start position:0% efficiency and reliability the internet's<01:07:43.440> major<01:07:43.619> divisions<01:07:44.220> are<01:07:44.640> connected 01:07:44.930 --> 01:07:44.940 align:start position:0% internet's major divisions are connected 01:07:44.940 --> 01:07:47.150 align:start position:0% internet's major divisions are connected to<01:07:45.119> one<01:07:45.240> another<01:07:45.359> by<01:07:45.660> a<01:07:45.839> mesh<01:07:46.020> topology<01:07:46.380> so 01:07:47.150 --> 01:07:47.160 align:start position:0% to one another by a mesh topology so 01:07:47.160 --> 01:07:49.130 align:start position:0% to one another by a mesh topology so we're<01:07:47.880> really<01:07:48.059> going<01:07:48.180> to<01:07:48.299> see<01:07:48.420> this<01:07:48.660> in<01:07:48.900> sort 01:07:49.130 --> 01:07:49.140 align:start position:0% we're really going to see this in sort 01:07:49.140 --> 01:07:51.730 align:start position:0% we're really going to see this in sort of<01:07:49.339> large<01:07:50.339> scale 01:07:51.730 --> 01:07:51.740 align:start position:0% of large scale 01:07:51.740 --> 01:07:56.089 align:start position:0% of large scale implementations<01:07:53.059> that<01:07:54.059> need 01:07:56.089 --> 01:07:56.099 align:start position:0% implementations that need 01:07:56.099 --> 01:08:01.370 align:start position:0% implementations that need High<01:07:56.579> redundancy 01:08:01.370 --> 01:08:01.380 align:start position:0% 01:08:01.380 --> 01:08:03.650 align:start position:0% and<01:08:01.980> efficiency<01:08:02.400> I<01:08:02.700> should<01:08:02.880> add 01:08:03.650 --> 01:08:03.660 align:start position:0% and efficiency I should add 01:08:03.660 --> 01:08:06.349 align:start position:0% and efficiency I should add now<01:08:04.200> a<01:08:04.559> hybrid<01:08:04.799> topology<01:08:05.220> as<01:08:05.520> we<01:08:05.700> have<01:08:06.000> we<01:08:06.180> as 01:08:06.349 --> 01:08:06.359 align:start position:0% now a hybrid topology as we have we as 01:08:06.359 --> 01:08:09.770 align:start position:0% now a hybrid topology as we have we as we've<01:08:06.599> discussed<01:08:06.900> utilizes<01:08:07.799> uh<01:08:08.220> aspects<01:08:08.700> of 01:08:09.770 --> 01:08:09.780 align:start position:0% we've discussed utilizes uh aspects of 01:08:09.780 --> 01:08:11.990 align:start position:0% we've discussed utilizes uh aspects of more<01:08:10.380> than<01:08:10.500> one<01:08:10.859> type<01:08:11.099> of<01:08:11.339> individual 01:08:11.990 --> 01:08:12.000 align:start position:0% more than one type of individual 01:08:12.000 --> 01:08:14.809 align:start position:0% more than one type of individual topology<01:08:12.599> so<01:08:13.140> hybrid<01:08:13.500> topologies<01:08:14.160> are 01:08:14.809 --> 01:08:14.819 align:start position:0% topology so hybrid topologies are 01:08:14.819 --> 01:08:17.150 align:start position:0% topology so hybrid topologies are usually<01:08:15.299> not<01:08:15.599> created<01:08:15.960> on<01:08:16.259> purpose<01:08:16.620> they're 01:08:17.150 --> 01:08:17.160 align:start position:0% usually not created on purpose they're 01:08:17.160 --> 01:08:18.349 align:start position:0% usually not created on purpose they're usually<01:08:17.400> actually<01:08:17.580> created<01:08:17.940> out<01:08:18.179> of 01:08:18.349 --> 01:08:18.359 align:start position:0% usually actually created out of 01:08:18.359 --> 01:08:20.870 align:start position:0% usually actually created out of necessity<01:08:18.900> so<01:08:19.560> topologies<01:08:20.219> like<01:08:20.460> this<01:08:20.640> can 01:08:20.870 --> 01:08:20.880 align:start position:0% necessity so topologies like this can 01:08:20.880 --> 01:08:23.689 align:start position:0% necessity so topologies like this can maintain<01:08:21.359> uh<01:08:22.319> are<01:08:22.620> difficult<01:08:23.040> rather<01:08:23.460> to 01:08:23.689 --> 01:08:23.699 align:start position:0% maintain uh are difficult rather to 01:08:23.699 --> 01:08:25.669 align:start position:0% maintain uh are difficult rather to maintain<01:08:24.120> and<01:08:24.480> to<01:08:24.660> manage<01:08:24.960> because<01:08:25.380> each 01:08:25.669 --> 01:08:25.679 align:start position:0% maintain and to manage because each 01:08:25.679 --> 01:08:27.829 align:start position:0% maintain and to manage because each segment<01:08:26.040> in<01:08:26.279> the<01:08:26.400> hybrid<01:08:26.640> topology<01:08:27.480> might 01:08:27.829 --> 01:08:27.839 align:start position:0% segment in the hybrid topology might 01:08:27.839 --> 01:08:29.570 align:start position:0% segment in the hybrid topology might have<01:08:28.020> its<01:08:28.380> own<01:08:28.440> set<01:08:28.679> of<01:08:28.799> rules<01:08:29.040> it<01:08:29.219> needs<01:08:29.460> to 01:08:29.570 --> 01:08:29.580 align:start position:0% have its own set of rules it needs to 01:08:29.580 --> 01:08:31.430 align:start position:0% have its own set of rules it needs to Follows<01:08:30.060> the<01:08:30.660> technology<01:08:30.960> is<01:08:31.140> on<01:08:31.319> the 01:08:31.430 --> 01:08:31.440 align:start position:0% Follows the technology is on the 01:08:31.440 --> 01:08:33.349 align:start position:0% Follows the technology is on the different<01:08:31.560> segments<01:08:32.339> might<01:08:32.640> not<01:08:32.759> be<01:08:33.000> the<01:08:33.239> same 01:08:33.349 --> 01:08:33.359 align:start position:0% different segments might not be the same 01:08:33.359 --> 01:08:35.329 align:start position:0% different segments might not be the same either<01:08:33.719> so<01:08:34.140> I<01:08:34.259> might<01:08:34.440> have<01:08:34.560> a<01:08:34.739> different<01:08:34.859> type 01:08:35.329 --> 01:08:35.339 align:start position:0% either so I might have a different type 01:08:35.339 --> 01:08:38.030 align:start position:0% either so I might have a different type type<01:08:35.940> of<01:08:36.239> Technology<01:08:36.660> on<01:08:36.960> this<01:08:37.140> segment<01:08:37.500> than 01:08:38.030 --> 01:08:38.040 align:start position:0% type of Technology on this segment than 01:08:38.040 --> 01:08:39.950 align:start position:0% type of Technology on this segment than I<01:08:38.219> do<01:08:38.339> on<01:08:38.580> this<01:08:38.759> segment<01:08:39.120> and<01:08:39.420> I<01:08:39.540> might<01:08:39.660> and 01:08:39.950 --> 01:08:39.960 align:start position:0% I do on this segment and I might and 01:08:39.960 --> 01:08:41.209 align:start position:0% I do on this segment and I might and then<01:08:40.140> I<01:08:40.440> have<01:08:40.500> a<01:08:40.739> different<01:08:40.799> type<01:08:41.100> of 01:08:41.209 --> 01:08:41.219 align:start position:0% then I have a different type of 01:08:41.219 --> 01:08:43.849 align:start position:0% then I have a different type of Technology<01:08:41.640> on<01:08:42.420> this<01:08:42.600> segment<01:08:42.900> right<01:08:43.140> here<01:08:43.319> so 01:08:43.849 --> 01:08:43.859 align:start position:0% Technology on this segment right here so 01:08:43.859 --> 01:08:46.970 align:start position:0% Technology on this segment right here so there<01:08:44.100> are<01:08:44.279> a<01:08:44.460> few<01:08:45.000> common<01:08:45.420> types<01:08:46.020> of<01:08:46.440> star<01:08:46.679> of 01:08:46.970 --> 01:08:46.980 align:start position:0% there are a few common types of star of 01:08:46.980 --> 01:08:49.309 align:start position:0% there are a few common types of star of topologies<01:08:47.759> that<01:08:48.239> are<01:08:48.299> in<01:08:48.420> a<01:08:48.600> hybrid<01:08:48.839> sort<01:08:49.259> of 01:08:49.309 --> 01:08:49.319 align:start position:0% topologies that are in a hybrid sort of 01:08:49.319 --> 01:08:51.470 align:start position:0% topologies that are in a hybrid sort of breed<01:08:49.980> that<01:08:50.160> we<01:08:50.279> come<01:08:50.460> across<01:08:50.819> this<01:08:51.239> one's 01:08:51.470 --> 01:08:51.480 align:start position:0% breed that we come across this one's 01:08:51.480 --> 01:08:53.450 align:start position:0% breed that we come across this one's called<01:08:51.600> a<01:08:51.839> star<01:08:52.020> bus<01:08:52.319> obviously<01:08:52.920> because<01:08:53.160> we 01:08:53.450 --> 01:08:53.460 align:start position:0% called a star bus obviously because we 01:08:53.460 --> 01:08:56.150 align:start position:0% called a star bus obviously because we have<01:08:53.640> stars<01:08:54.540> here<01:08:54.839> and<01:08:55.380> then<01:08:55.500> the<01:08:55.679> stars<01:08:55.980> are 01:08:56.150 --> 01:08:56.160 align:start position:0% have stars here and then the stars are 01:08:56.160 --> 01:08:59.329 align:start position:0% have stars here and then the stars are connected<01:08:56.779> by<01:08:57.779> a<01:08:58.140> bus<01:08:58.380> connection<01:08:58.679> notice 01:08:59.329 --> 01:08:59.339 align:start position:0% connected by a bus connection notice 01:08:59.339 --> 01:09:02.749 align:start position:0% connected by a bus connection notice again<01:08:59.580> the<01:09:00.239> Terminators<01:09:00.839> on<01:09:01.380> either<01:09:01.620> side 01:09:02.749 --> 01:09:02.759 align:start position:0% again the Terminators on either side 01:09:02.759 --> 01:09:05.930 align:start position:0% again the Terminators on either side we<01:09:03.299> also<01:09:03.540> have<01:09:03.719> what's<01:09:04.020> called<01:09:04.259> a<01:09:05.040> a<01:09:05.339> star<01:09:05.640> of 01:09:05.930 --> 01:09:05.940 align:start position:0% we also have what's called a a star of 01:09:05.940 --> 01:09:08.450 align:start position:0% we also have what's called a a star of stars<01:09:06.540> hybrid<01:09:06.960> you<01:09:07.440> can<01:09:07.560> see<01:09:07.679> that<01:09:07.920> each<01:09:08.219> star 01:09:08.450 --> 01:09:08.460 align:start position:0% stars hybrid you can see that each star 01:09:08.460 --> 01:09:11.749 align:start position:0% stars hybrid you can see that each star is<01:09:08.819> connected<01:09:09.239> by<01:09:09.960> another<01:09:10.259> star<01:09:10.620> so<01:09:11.100> it's<01:09:11.460> not 01:09:11.749 --> 01:09:11.759 align:start position:0% is connected by another star so it's not 01:09:11.759 --> 01:09:13.910 align:start position:0% is connected by another star so it's not only<01:09:12.060> different<01:09:12.719> topologies<01:09:13.380> but<01:09:13.560> when<01:09:13.739> we 01:09:13.910 --> 01:09:13.920 align:start position:0% only different topologies but when we 01:09:13.920 --> 01:09:16.189 align:start position:0% only different topologies but when we connect<01:09:14.040> the<01:09:14.279> topologies<01:09:14.819> together<01:09:15.120> uh<01:09:15.960> sort 01:09:16.189 --> 01:09:16.199 align:start position:0% connect the topologies together uh sort 01:09:16.199 --> 01:09:18.229 align:start position:0% connect the topologies together uh sort of<01:09:16.319> in<01:09:16.560> different<01:09:16.739> ways<01:09:17.160> that<01:09:17.520> can<01:09:17.699> be<01:09:17.880> a 01:09:18.229 --> 01:09:18.239 align:start position:0% of in different ways that can be a 01:09:18.239 --> 01:09:20.570 align:start position:0% of in different ways that can be a different<01:09:18.359> hyper<01:09:18.900> topology<01:09:19.380> as<01:09:19.679> well<01:09:19.799> and 01:09:20.570 --> 01:09:20.580 align:start position:0% different hyper topology as well and 01:09:20.580 --> 01:09:22.370 align:start position:0% different hyper topology as well and then<01:09:20.699> another<01:09:21.000> popular<01:09:21.299> one<01:09:21.660> is<01:09:21.839> the<01:09:22.140> star 01:09:22.370 --> 01:09:22.380 align:start position:0% then another popular one is the star 01:09:22.380 --> 01:09:25.490 align:start position:0% then another popular one is the star ring<01:09:22.920> topology<01:09:23.339> so<01:09:24.060> similar<01:09:24.719> to<01:09:24.900> bus<01:09:25.080> except 01:09:25.490 --> 01:09:25.500 align:start position:0% ring topology so similar to bus except 01:09:25.500 --> 01:09:26.689 align:start position:0% ring topology so similar to bus except there's<01:09:25.620> no<01:09:25.859> Terminators<01:09:26.339> on<01:09:26.520> the<01:09:26.580> end 01:09:26.689 --> 01:09:26.699 align:start position:0% there's no Terminators on the end 01:09:26.699 --> 01:09:28.550 align:start position:0% there's no Terminators on the end because<01:09:26.880> everything<01:09:27.299> connects<01:09:27.839> together<01:09:28.020> you 01:09:28.550 --> 01:09:28.560 align:start position:0% because everything connects together you 01:09:28.560 --> 01:09:29.870 align:start position:0% because everything connects together you might<01:09:28.679> also<01:09:28.920> have<01:09:28.980> a<01:09:29.100> star<01:09:29.219> dual<01:09:29.580> ring 01:09:29.870 --> 01:09:29.880 align:start position:0% might also have a star dual ring 01:09:29.880 --> 01:09:32.510 align:start position:0% might also have a star dual ring topology<01:09:30.239> which<01:09:30.600> I<01:09:30.719> have<01:09:30.839> seen<01:09:31.140> uh<01:09:31.980> all<01:09:32.279> the 01:09:32.510 --> 01:09:32.520 align:start position:0% topology which I have seen uh all the 01:09:32.520 --> 01:09:35.209 align:start position:0% topology which I have seen uh all the very<01:09:33.120> infrequently<01:09:33.960> by<01:09:34.380> the<01:09:34.560> way<01:09:34.620> this<01:09:34.920> one<01:09:35.040> is 01:09:35.209 --> 01:09:35.219 align:start position:0% very infrequently by the way this one is 01:09:35.219 --> 01:09:36.769 align:start position:0% very infrequently by the way this one is also<01:09:35.460> called<01:09:35.699> although<01:09:36.120> I<01:09:36.239> doubt<01:09:36.480> you'll<01:09:36.600> see 01:09:36.769 --> 01:09:36.779 align:start position:0% also called although I doubt you'll see 01:09:36.779 --> 01:09:37.930 align:start position:0% also called although I doubt you'll see this 01:09:37.930 --> 01:09:37.940 align:start position:0% this 01:09:37.940 --> 01:09:40.729 align:start position:0% this snowflake<01:09:38.940> topology 01:09:40.729 --> 01:09:40.739 align:start position:0% snowflake topology 01:09:40.739 --> 01:09:42.610 align:start position:0% snowflake topology now<01:09:41.339> Network 01:09:42.610 --> 01:09:42.620 align:start position:0% now Network 01:09:42.620 --> 01:09:45.829 align:start position:0% now Network Protocols<01:09:43.620> are<01:09:44.339> the<01:09:44.580> controlling<01:09:45.239> factor<01:09:45.660> and 01:09:45.829 --> 01:09:45.839 align:start position:0% Protocols are the controlling factor and 01:09:45.839 --> 01:09:47.510 align:start position:0% Protocols are the controlling factor and how<01:09:46.080> all<01:09:46.259> these<01:09:46.500> topologies<01:09:46.920> are<01:09:47.100> going<01:09:47.279> to 01:09:47.510 --> 01:09:47.520 align:start position:0% how all these topologies are going to 01:09:47.520 --> 01:09:51.410 align:start position:0% how all these topologies are going to transmit<01:09:48.420> data<01:09:49.460> and<01:09:50.460> depending<01:09:51.060> on<01:09:51.239> the 01:09:51.410 --> 01:09:51.420 align:start position:0% transmit data and depending on the 01:09:51.420 --> 01:09:52.789 align:start position:0% transmit data and depending on the protocol<01:09:51.719> data<01:09:52.199> it<01:09:52.259> might<01:09:52.440> need<01:09:52.620> to<01:09:52.739> be 01:09:52.789 --> 01:09:52.799 align:start position:0% protocol data it might need to be 01:09:52.799 --> 01:09:54.410 align:start position:0% protocol data it might need to be transmitted<01:09:53.400> to<01:09:53.580> all<01:09:53.759> the<01:09:53.880> nodes<01:09:54.060> on<01:09:54.299> the 01:09:54.410 --> 01:09:54.420 align:start position:0% transmitted to all the nodes on the 01:09:54.420 --> 01:09:55.970 align:start position:0% transmitted to all the nodes on the network<01:09:54.540> regardless<01:09:55.440> of<01:09:55.679> the<01:09:55.800> physical 01:09:55.970 --> 01:09:55.980 align:start position:0% network regardless of the physical 01:09:55.980 --> 01:09:58.430 align:start position:0% network regardless of the physical connection<01:09:56.400> so<01:09:57.239> this<01:09:57.420> is<01:09:57.480> why<01:09:57.719> having<01:09:58.020> a 01:09:58.430 --> 01:09:58.440 align:start position:0% connection so this is why having a 01:09:58.440 --> 01:10:00.530 align:start position:0% connection so this is why having a logical<01:09:58.860> topology<01:09:59.520> is<01:09:59.820> different<01:10:00.000> from<01:10:00.360> a 01:10:00.530 --> 01:10:00.540 align:start position:0% logical topology is different from a 01:10:00.540 --> 01:10:03.410 align:start position:0% logical topology is different from a physical<01:10:00.780> topology<01:10:01.320> in<01:10:01.980> other<01:10:02.100> words<01:10:02.340> the<01:10:03.300> way 01:10:03.410 --> 01:10:03.420 align:start position:0% physical topology in other words the way 01:10:03.420 --> 01:10:05.689 align:start position:0% physical topology in other words the way the<01:10:03.600> data<01:10:03.960> is<01:10:04.199> transferred<01:10:04.920> over<01:10:05.280> the<01:10:05.520> network 01:10:05.689 --> 01:10:05.699 align:start position:0% the data is transferred over the network 01:10:05.699 --> 01:10:08.270 align:start position:0% the data is transferred over the network might<01:10:06.239> be<01:10:06.420> different<01:10:06.660> than<01:10:07.020> the<01:10:07.260> way<01:10:07.440> the 01:10:08.270 --> 01:10:08.280 align:start position:0% might be different than the way the 01:10:08.280 --> 01:10:10.130 align:start position:0% might be different than the way the physical<01:10:08.460> network<01:10:08.820> is<01:10:09.239> actually 01:10:10.130 --> 01:10:10.140 align:start position:0% physical network is actually 01:10:10.140 --> 01:10:12.229 align:start position:0% physical network is actually connected<01:10:10.860> so<01:10:11.040> let<01:10:11.160> me<01:10:11.280> give<01:10:11.400> an<01:10:11.460> example<01:10:11.760> with 01:10:12.229 --> 01:10:12.239 align:start position:0% connected so let me give an example with 01:10:12.239 --> 01:10:15.410 align:start position:0% connected so let me give an example with this<01:10:12.540> logical<01:10:12.900> bus<01:10:13.260> topology 01:10:15.410 --> 01:10:15.420 align:start position:0% this logical bus topology 01:10:15.420 --> 01:10:18.610 align:start position:0% this logical bus topology okay<01:10:15.840> data<01:10:16.679> is<01:10:16.860> received<01:10:17.400> by<01:10:17.699> all<01:10:18.060> nodes 01:10:18.610 --> 01:10:18.620 align:start position:0% okay data is received by all nodes 01:10:18.620 --> 01:10:22.070 align:start position:0% okay data is received by all nodes simultaneously<01:10:19.620> even<01:10:20.400> when<01:10:20.699> the<01:10:20.880> physical 01:10:22.070 --> 01:10:22.080 align:start position:0% simultaneously even when the physical 01:10:22.080 --> 01:10:24.530 align:start position:0% simultaneously even when the physical setup<01:10:22.679> is<01:10:22.860> different<01:10:23.100> so<01:10:23.820> for<01:10:24.000> example<01:10:24.300> we're 01:10:24.530 --> 01:10:24.540 align:start position:0% setup is different so for example we're 01:10:24.540 --> 01:10:27.350 align:start position:0% setup is different so for example we're using<01:10:24.840> a<01:10:25.080> logical<01:10:25.440> bus<01:10:25.739> topology<01:10:26.280> with<01:10:27.060> this 01:10:27.350 --> 01:10:27.360 align:start position:0% using a logical bus topology with this 01:10:27.360 --> 01:10:31.189 align:start position:0% using a logical bus topology with this physical<01:10:27.780> star<01:10:28.620> so<01:10:29.340> the<01:10:29.640> central<01:10:29.880> device<01:10:30.300> is 01:10:31.189 --> 01:10:31.199 align:start position:0% physical star so the central device is 01:10:31.199 --> 01:10:33.470 align:start position:0% physical star so the central device is receiving<01:10:31.500> the<01:10:31.800> transmission<01:10:32.239> from<01:10:33.239> let's 01:10:33.470 --> 01:10:33.480 align:start position:0% receiving the transmission from let's 01:10:33.480 --> 01:10:35.990 align:start position:0% receiving the transmission from let's say<01:10:33.659> the<01:10:34.260> sending<01:10:34.620> node<01:10:34.920> which<01:10:35.460> is<01:10:35.580> this<01:10:35.820> one 01:10:35.990 --> 01:10:36.000 align:start position:0% say the sending node which is this one 01:10:36.000 --> 01:10:38.270 align:start position:0% say the sending node which is this one so<01:10:36.239> let's<01:10:36.360> say<01:10:36.540> a<01:10:36.719> is<01:10:36.900> sending<01:10:37.260> it<01:10:37.320> out 01:10:38.270 --> 01:10:38.280 align:start position:0% so let's say a is sending it out 01:10:38.280 --> 01:10:40.790 align:start position:0% so let's say a is sending it out and<01:10:38.940> then<01:10:39.120> it's<01:10:39.300> passing<01:10:39.780> it<01:10:39.900> to<01:10:40.080> each<01:10:40.260> node<01:10:40.560> in 01:10:40.790 --> 01:10:40.800 align:start position:0% and then it's passing it to each node in 01:10:40.800 --> 01:10:42.950 align:start position:0% and then it's passing it to each node in succession<01:10:41.159> in<01:10:41.520> a<01:10:41.699> continuous<01:10:42.060> stream<01:10:42.300> in 01:10:42.950 --> 01:10:42.960 align:start position:0% succession in a continuous stream in 01:10:42.960 --> 01:10:44.990 align:start position:0% succession in a continuous stream in other<01:10:43.020> words<01:10:43.140> it's<01:10:43.500> doing<01:10:43.739> this 01:10:44.990 --> 01:10:45.000 align:start position:0% other words it's doing this 01:10:45.000 --> 01:10:47.149 align:start position:0% other words it's doing this it's<01:10:45.360> going<01:10:45.540> down<01:10:45.780> there<01:10:46.080> and<01:10:46.800> then<01:10:46.980> it's 01:10:47.149 --> 01:10:47.159 align:start position:0% it's going down there and then it's 01:10:47.159 --> 01:10:49.430 align:start position:0% it's going down there and then it's sending<01:10:47.580> it<01:10:47.699> here<01:10:47.940> and<01:10:48.659> then<01:10:48.780> it's<01:10:48.960> sending<01:10:49.320> it 01:10:49.430 --> 01:10:49.440 align:start position:0% sending it here and then it's sending it 01:10:49.440 --> 01:10:51.770 align:start position:0% sending it here and then it's sending it there<01:10:49.679> and<01:10:50.280> then<01:10:50.400> it's<01:10:50.580> sending<01:10:50.940> it<01:10:51.060> there<01:10:51.300> and 01:10:51.770 --> 01:10:51.780 align:start position:0% there and then it's sending it there and 01:10:51.780 --> 01:10:53.689 align:start position:0% there and then it's sending it there and then<01:10:51.900> it's<01:10:52.080> sending<01:10:52.440> it<01:10:52.560> there<01:10:52.739> so<01:10:53.460> you<01:10:53.580> can 01:10:53.689 --> 01:10:53.699 align:start position:0% then it's sending it there so you can 01:10:53.699 --> 01:10:55.010 align:start position:0% then it's sending it there so you can see<01:10:53.820> what<01:10:54.000> it's<01:10:54.120> doing<01:10:54.360> is<01:10:54.600> although<01:10:54.840> it's 01:10:55.010 --> 01:10:55.020 align:start position:0% see what it's doing is although it's 01:10:55.020 --> 01:10:57.709 align:start position:0% see what it's doing is although it's connected<01:10:55.440> in<01:10:55.679> a<01:10:55.860> star<01:10:56.100> physically<01:10:56.820> the<01:10:57.480> nodes 01:10:57.709 --> 01:10:57.719 align:start position:0% connected in a star physically the nodes 01:10:57.719 --> 01:10:58.970 align:start position:0% connected in a star physically the nodes are<01:10:57.900> talking<01:10:58.080> to<01:10:58.320> one<01:10:58.440> another<01:10:58.560> as<01:10:58.860> though 01:10:58.970 --> 01:10:58.980 align:start position:0% are talking to one another as though 01:10:58.980 --> 01:11:00.530 align:start position:0% are talking to one another as though they<01:10:59.219> are<01:10:59.340> logical 01:11:00.530 --> 01:11:00.540 align:start position:0% they are logical 01:11:00.540 --> 01:11:04.550 align:start position:0% they are logical now<01:11:00.960> with<01:11:01.140> a<01:11:01.320> logical<01:11:01.760> ring<01:11:02.760> topology<01:11:03.380> uh<01:11:04.380> just 01:11:04.550 --> 01:11:04.560 align:start position:0% now with a logical ring topology uh just 01:11:04.560 --> 01:11:06.590 align:start position:0% now with a logical ring topology uh just like<01:11:04.679> with<01:11:04.920> a<01:11:05.040> physical<01:11:05.219> ring<01:11:05.760> the<01:11:06.239> data<01:11:06.480> is 01:11:06.590 --> 01:11:06.600 align:start position:0% like with a physical ring the data is 01:11:06.600 --> 01:11:08.510 align:start position:0% like with a physical ring the data is only<01:11:06.780> transmitted<01:11:07.500> between<01:11:07.679> its<01:11:08.100> upstream 01:11:08.510 --> 01:11:08.520 align:start position:0% only transmitted between its upstream 01:11:08.520 --> 01:11:10.729 align:start position:0% only transmitted between its upstream and<01:11:08.640> its<01:11:08.880> Downstream<01:11:09.360> neighbors<01:11:09.719> so<01:11:10.380> even 01:11:10.729 --> 01:11:10.739 align:start position:0% and its Downstream neighbors so even 01:11:10.739 --> 01:11:12.950 align:start position:0% and its Downstream neighbors so even though<01:11:10.980> the<01:11:11.280> star<01:11:11.460> layout<01:11:12.000> is<01:11:12.600> physically 01:11:12.950 --> 01:11:12.960 align:start position:0% though the star layout is physically 01:11:12.960 --> 01:11:16.010 align:start position:0% though the star layout is physically laid<01:11:13.320> out<01:11:13.440> in<01:11:13.620> a<01:11:13.739> certain<01:11:13.860> way<01:11:14.300> the<01:11:15.300> data<01:11:15.780> from 01:11:16.010 --> 01:11:16.020 align:start position:0% laid out in a certain way the data from 01:11:16.020 --> 01:11:19.370 align:start position:0% laid out in a certain way the data from the<01:11:16.260> transmitting<01:11:16.920> devices<01:11:17.219> is<01:11:17.580> sent 01:11:19.370 --> 01:11:19.380 align:start position:0% the transmitting devices is sent 01:11:19.380 --> 01:11:22.010 align:start position:0% the transmitting devices is sent in<01:11:20.219> specific<01:11:20.520> order 01:11:22.010 --> 01:11:22.020 align:start position:0% in specific order 01:11:22.020 --> 01:11:25.669 align:start position:0% in specific order one<01:11:22.620> to<01:11:22.800> the<01:11:22.920> next 01:11:25.669 --> 01:11:25.679 align:start position:0% 01:11:25.679 --> 01:11:30.110 align:start position:0% now<01:11:26.280> actually<01:11:26.580> most<01:11:27.060> ring 01:11:30.110 --> 01:11:30.120 align:start position:0% 01:11:30.120 --> 01:11:33.890 align:start position:0% networks<01:11:30.960> are<01:11:31.199> physical<01:11:31.560> Stars 01:11:33.890 --> 01:11:33.900 align:start position:0% networks are physical Stars 01:11:33.900 --> 01:11:36.709 align:start position:0% networks are physical Stars right<01:11:34.320> so<01:11:34.679> every<01:11:34.920> time<01:11:35.100> the<01:11:35.340> data<01:11:35.580> is<01:11:35.760> sent<01:11:36.000> it 01:11:36.709 --> 01:11:36.719 align:start position:0% right so every time the data is sent it 01:11:36.719 --> 01:11:38.570 align:start position:0% right so every time the data is sent it has<01:11:36.840> to<01:11:37.020> be<01:11:37.140> sent<01:11:37.320> to<01:11:37.500> its<01:11:37.800> up<01:11:37.980> Downstream 01:11:38.570 --> 01:11:38.580 align:start position:0% has to be sent to its up Downstream 01:11:38.580 --> 01:11:40.850 align:start position:0% has to be sent to its up Downstream neighbor 01:11:40.850 --> 01:11:40.860 align:start position:0% 01:11:40.860 --> 01:11:43.070 align:start position:0% in<01:11:41.159> succession<01:11:41.520> like<01:11:41.880> so 01:11:43.070 --> 01:11:43.080 align:start position:0% in succession like so 01:11:43.080 --> 01:11:47.510 align:start position:0% in succession like so so<01:11:43.260> it<01:11:43.500> just<01:11:43.620> goes<01:11:43.860> in<01:11:43.980> a<01:11:44.159> circular<01:11:44.580> route 01:11:47.510 --> 01:11:47.520 align:start position:0% 01:11:47.520 --> 01:11:50.030 align:start position:0% we<01:11:47.940> also<01:11:48.179> have<01:11:48.420> of<01:11:48.719> course<01:11:48.840> The<01:11:49.080> Logical<01:11:49.440> star 01:11:50.030 --> 01:11:50.040 align:start position:0% we also have of course The Logical star 01:11:50.040 --> 01:11:52.310 align:start position:0% we also have of course The Logical star topology<01:11:50.640> which<01:11:51.239> can<01:11:51.420> utilize<01:11:51.840> a<01:11:52.080> central 01:11:52.310 --> 01:11:52.320 align:start position:0% topology which can utilize a central 01:11:52.320 --> 01:11:54.169 align:start position:0% topology which can utilize a central device 01:11:54.169 --> 01:11:54.179 align:start position:0% device 01:11:54.179 --> 01:11:56.330 align:start position:0% device and<01:11:54.659> it's<01:11:54.780> going<01:11:55.020> to<01:11:55.140> pull<01:11:55.380> each<01:11:55.739> node<01:11:55.980> to<01:11:56.219> see 01:11:56.330 --> 01:11:56.340 align:start position:0% and it's going to pull each node to see 01:11:56.340 --> 01:11:59.209 align:start position:0% and it's going to pull each node to see if<01:11:56.520> it<01:11:56.699> has<01:11:56.940> the<01:11:57.540> data<01:11:57.900> to<01:11:58.080> be<01:11:58.260> transmitted<01:11:58.920> so 01:11:59.209 --> 01:11:59.219 align:start position:0% if it has the data to be transmitted so 01:11:59.219 --> 01:12:01.910 align:start position:0% if it has the data to be transmitted so basically<01:11:59.520> it<01:11:59.640> says<01:11:59.940> hey<01:12:00.140> uh<01:12:01.140> do<01:12:01.440> you<01:12:01.620> have<01:12:01.739> any 01:12:01.910 --> 01:12:01.920 align:start position:0% basically it says hey uh do you have any 01:12:01.920 --> 01:12:03.830 align:start position:0% basically it says hey uh do you have any data<01:12:02.219> you<01:12:02.280> want<01:12:02.460> to<01:12:02.580> transmit<01:12:02.940> okay<01:12:03.300> do<01:12:03.659> you 01:12:03.830 --> 01:12:03.840 align:start position:0% data you want to transmit okay do you 01:12:03.840 --> 01:12:05.209 align:start position:0% data you want to transmit okay do you have<01:12:03.900> any<01:12:04.020> data<01:12:04.260> you<01:12:04.380> want<01:12:04.500> to<01:12:04.620> transmit<01:12:04.980> all 01:12:05.209 --> 01:12:05.219 align:start position:0% have any data you want to transmit all 01:12:05.219 --> 01:12:06.590 align:start position:0% have any data you want to transmit all right<01:12:05.340> do<01:12:05.520> you<01:12:05.640> have<01:12:05.699> any<01:12:05.820> data<01:12:06.120> oh<01:12:06.179> you<01:12:06.420> do 01:12:06.590 --> 01:12:06.600 align:start position:0% right do you have any data oh you do 01:12:06.600 --> 01:12:08.870 align:start position:0% right do you have any data oh you do great<01:12:06.900> then<01:12:07.320> it'll<01:12:07.620> transmit<01:12:08.159> that<01:12:08.400> data<01:12:08.699> and 01:12:08.870 --> 01:12:08.880 align:start position:0% great then it'll transmit that data and 01:12:08.880 --> 01:12:11.149 align:start position:0% great then it'll transmit that data and then<01:12:09.000> come<01:12:09.300> back<01:12:09.540> around<01:12:09.840> so<01:12:10.739> the<01:12:10.980> device 01:12:11.149 --> 01:12:11.159 align:start position:0% then come back around so the device 01:12:11.159 --> 01:12:13.370 align:start position:0% then come back around so the device ensures<01:12:12.000> that<01:12:12.360> each<01:12:12.600> node<01:12:12.900> has<01:12:13.140> an 01:12:13.370 --> 01:12:13.380 align:start position:0% ensures that each node has an 01:12:13.380 --> 01:12:15.470 align:start position:0% ensures that each node has an opportunity<01:12:13.800> to<01:12:14.280> transmit<01:12:14.760> but<01:12:15.179> it<01:12:15.300> also 01:12:15.470 --> 01:12:15.480 align:start position:0% opportunity to transmit but it also 01:12:15.480 --> 01:12:16.729 align:start position:0% opportunity to transmit but it also governs<01:12:15.840> how<01:12:16.020> long<01:12:16.140> that's<01:12:16.320> going<01:12:16.560> to<01:12:16.620> happen 01:12:16.729 --> 01:12:16.739 align:start position:0% governs how long that's going to happen 01:12:16.739 --> 01:12:18.830 align:start position:0% governs how long that's going to happen for<01:12:17.100> and<01:12:17.640> it's<01:12:17.760> going<01:12:17.940> to<01:12:18.060> make<01:12:18.239> sure<01:12:18.480> that 01:12:18.830 --> 01:12:18.840 align:start position:0% for and it's going to make sure that 01:12:18.840 --> 01:12:20.750 align:start position:0% for and it's going to make sure that there's<01:12:19.140> not<01:12:19.380> any 01:12:20.750 --> 01:12:20.760 align:start position:0% there's not any 01:12:20.760 --> 01:12:24.050 align:start position:0% there's not any sort<01:12:21.360> of<01:12:21.480> problems<01:12:22.080> or<01:12:22.560> uh 01:12:24.050 --> 01:12:24.060 align:start position:0% sort of problems or uh 01:12:24.060 --> 01:12:26.689 align:start position:0% sort of problems or uh collisions<01:12:24.960> with<01:12:25.320> the<01:12:25.440> data 01:12:26.689 --> 01:12:26.699 align:start position:0% collisions with the data 01:12:26.699 --> 01:12:29.030 align:start position:0% collisions with the data so<01:12:27.239> just<01:12:27.480> to<01:12:27.659> recap<01:12:28.020> what<01:12:28.320> we<01:12:28.500> just<01:12:28.620> talked 01:12:29.030 --> 01:12:29.040 align:start position:0% so just to recap what we just talked 01:12:29.040 --> 01:12:33.050 align:start position:0% so just to recap what we just talked about<01:12:29.159> albeit<01:12:30.120> a<01:12:30.719> a<01:12:30.900> 5<01:12:31.860> 000<01:12:31.980> foot<01:12:32.219> overview<01:12:32.880> of 01:12:33.050 --> 01:12:33.060 align:start position:0% about albeit a a 5 000 foot overview of 01:12:33.060 --> 01:12:35.630 align:start position:0% about albeit a a 5 000 foot overview of it<01:12:33.239> we<01:12:33.659> talked<01:12:33.900> about<01:12:34.020> topology<01:12:34.679> which<01:12:35.400> again 01:12:35.630 --> 01:12:35.640 align:start position:0% it we talked about topology which again 01:12:35.640 --> 01:12:39.050 align:start position:0% it we talked about topology which again is<01:12:36.420> like<01:12:36.780> how<01:12:37.260> the<01:12:37.500> network<01:12:37.620> is<01:12:37.980> arranged<01:12:38.520> that 01:12:39.050 --> 01:12:39.060 align:start position:0% is like how the network is arranged that 01:12:39.060 --> 01:12:40.850 align:start position:0% is like how the network is arranged that Arrangement<01:12:39.540> can<01:12:39.780> either<01:12:39.960> be<01:12:40.320> physical 01:12:40.850 --> 01:12:40.860 align:start position:0% Arrangement can either be physical 01:12:40.860 --> 01:12:42.830 align:start position:0% Arrangement can either be physical meaning<01:12:41.520> how<01:12:41.820> it<01:12:41.940> is<01:12:42.060> physically<01:12:42.360> connected 01:12:42.830 --> 01:12:42.840 align:start position:0% meaning how it is physically connected 01:12:42.840 --> 01:12:45.470 align:start position:0% meaning how it is physically connected or<01:12:43.679> logical 01:12:45.470 --> 01:12:45.480 align:start position:0% or logical 01:12:45.480 --> 01:12:48.290 align:start position:0% or logical we<01:12:45.900> then<01:12:46.020> talked<01:12:46.320> about<01:12:46.380> a<01:12:46.800> bus<01:12:46.980> topology<01:12:47.580> the 01:12:48.290 --> 01:12:48.300 align:start position:0% we then talked about a bus topology the 01:12:48.300 --> 01:12:52.729 align:start position:0% we then talked about a bus topology the bus<01:12:48.480> topology<01:12:49.020> meaning<01:12:49.800> that<01:12:50.159> it<01:12:50.340> is 01:12:52.729 --> 01:12:52.739 align:start position:0% 01:12:52.739 --> 01:12:55.550 align:start position:0% connected<01:12:53.520> to<01:12:53.699> each<01:12:53.880> device<01:12:54.060> one<01:12:54.420> in<01:12:54.659> sequence 01:12:55.550 --> 01:12:55.560 align:start position:0% connected to each device one in sequence 01:12:55.560 --> 01:12:57.709 align:start position:0% connected to each device one in sequence we<01:12:56.040> also<01:12:56.280> need<01:12:56.400> to<01:12:56.520> terminate<01:12:56.940> these<01:12:57.239> with<01:12:57.600> a 01:12:57.709 --> 01:12:57.719 align:start position:0% we also need to terminate these with a 01:12:57.719 --> 01:12:59.030 align:start position:0% we also need to terminate these with a 50<01:12:57.900> ohm 01:12:59.030 --> 01:12:59.040 align:start position:0% 50 ohm 01:12:59.040 --> 01:13:01.189 align:start position:0% 50 ohm Terminator<01:12:59.760> on<01:13:00.060> either<01:13:00.239> side<01:13:00.480> and<01:13:01.080> remember 01:13:01.189 --> 01:13:01.199 align:start position:0% Terminator on either side and remember 01:13:01.199 --> 01:13:03.050 align:start position:0% Terminator on either side and remember we<01:13:01.500> have<01:13:01.679> a<01:13:01.920> t<01:13:01.980> connector<01:13:02.460> that's<01:13:02.640> connecting 01:13:03.050 --> 01:13:03.060 align:start position:0% we have a t connector that's connecting 01:13:03.060 --> 01:13:03.709 align:start position:0% we have a t connector that's connecting them 01:13:03.709 --> 01:13:03.719 align:start position:0% them 01:13:03.719 --> 01:13:08.209 align:start position:0% them we<01:13:04.080> looked<01:13:04.320> at<01:13:04.380> a<01:13:04.679> star<01:13:04.980> topology 01:13:08.209 --> 01:13:08.219 align:start position:0% 01:13:08.219 --> 01:13:09.530 align:start position:0% which<01:13:08.460> means<01:13:08.640> that<01:13:08.760> these<01:13:08.940> are<01:13:09.060> all<01:13:09.179> connected 01:13:09.530 --> 01:13:09.540 align:start position:0% which means that these are all connected 01:13:09.540 --> 01:13:15.709 align:start position:0% which means that these are all connected through<01:13:09.719> a<01:13:10.020> central<01:13:10.199> device<01:13:10.880> a<01:13:11.880> ring 01:13:15.709 --> 01:13:15.719 align:start position:0% 01:13:15.719 --> 01:13:18.110 align:start position:0% topology 01:13:18.110 --> 01:13:18.120 align:start position:0% topology 01:13:18.120 --> 01:13:20.450 align:start position:0% topology tree<01:13:18.540> topology 01:13:20.450 --> 01:13:20.460 align:start position:0% tree topology 01:13:20.460 --> 01:13:22.669 align:start position:0% tree topology which<01:13:20.880> has<01:13:21.060> branches 01:13:22.669 --> 01:13:22.679 align:start position:0% which has branches 01:13:22.679 --> 01:13:24.350 align:start position:0% which has branches this<01:13:23.100> might<01:13:23.219> also<01:13:23.460> be<01:13:23.580> called<01:13:23.699> by<01:13:23.940> the<01:13:24.060> way<01:13:24.060> a 01:13:24.350 --> 01:13:24.360 align:start position:0% this might also be called by the way a 01:13:24.360 --> 01:13:25.550 align:start position:0% this might also be called by the way a hierarchical 01:13:25.550 --> 01:13:25.560 align:start position:0% hierarchical 01:13:25.560 --> 01:13:28.610 align:start position:0% hierarchical hierarchical 01:13:28.610 --> 01:13:28.620 align:start position:0% 01:13:28.620 --> 01:13:31.490 align:start position:0% topology<01:13:29.400> and<01:13:29.880> so<01:13:30.060> on<01:13:30.179> and<01:13:30.840> then<01:13:30.960> a<01:13:31.140> mesh 01:13:31.490 --> 01:13:31.500 align:start position:0% topology and so on and then a mesh 01:13:31.500 --> 01:13:33.709 align:start position:0% topology and so on and then a mesh topology 01:13:33.709 --> 01:13:33.719 align:start position:0% topology 01:13:33.719 --> 01:13:36.229 align:start position:0% topology which<01:13:34.380> would<01:13:34.620> be<01:13:34.739> every<01:13:35.040> device<01:13:35.280> connected<01:13:35.940> to 01:13:36.229 --> 01:13:36.239 align:start position:0% which would be every device connected to 01:13:36.239 --> 01:13:40.610 align:start position:0% which would be every device connected to every<01:13:37.020> other<01:13:37.199> device 01:13:40.610 --> 01:13:40.620 align:start position:0% 01:13:40.620 --> 01:13:45.350 align:start position:0% and<01:13:41.159> then<01:13:41.219> we<01:13:41.400> also<01:13:41.640> looked<01:13:41.940> at<01:13:42.000> a<01:13:42.360> hybrid 01:13:45.350 --> 01:13:45.360 align:start position:0% 01:13:45.360 --> 01:13:49.310 align:start position:0% of<01:13:45.780> these 01:13:49.310 --> 01:13:49.320 align:start position:0% 01:13:49.320 --> 01:13:52.310 align:start position:0% most<01:13:50.040> commonly<01:13:50.580> we're<01:13:51.239> going<01:13:51.480> to<01:13:51.719> see<01:13:51.900> a 01:13:52.310 --> 01:13:52.320 align:start position:0% most commonly we're going to see a 01:13:52.320 --> 01:13:53.689 align:start position:0% most commonly we're going to see a physical<01:13:52.500> star 01:13:53.689 --> 01:13:53.699 align:start position:0% physical star 01:13:53.699 --> 01:13:56.750 align:start position:0% physical star with<01:13:54.120> a<01:13:54.239> logical<01:13:54.600> ring 01:13:56.750 --> 01:13:56.760 align:start position:0% with a logical ring 01:13:56.760 --> 01:14:00.530 align:start position:0% with a logical ring so<01:13:57.239> it's<01:13:57.659> important<01:13:58.199> that<01:13:59.159> as<01:13:59.820> administrators 01:14:00.530 --> 01:14:00.540 align:start position:0% so it's important that as administrators 01:14:00.540 --> 01:14:02.510 align:start position:0% so it's important that as administrators we<01:14:00.840> have<01:14:01.020> an<01:14:01.320> understanding<01:14:01.980> of<01:14:02.219> how<01:14:02.400> the 01:14:02.510 --> 01:14:02.520 align:start position:0% we have an understanding of how the 01:14:02.520 --> 01:14:04.910 align:start position:0% we have an understanding of how the network<01:14:02.699> is<01:14:03.000> designed<01:14:03.360> both<01:14:03.659> physically<01:14:04.260> and 01:14:04.910 --> 01:14:04.920 align:start position:0% network is designed both physically and 01:14:04.920 --> 01:14:06.530 align:start position:0% network is designed both physically and logically<01:14:05.340> in<01:14:05.520> other<01:14:05.699> words<01:14:05.820> how<01:14:06.060> the<01:14:06.239> data 01:14:06.530 --> 01:14:06.540 align:start position:0% logically in other words how the data 01:14:06.540 --> 01:14:11.650 align:start position:0% logically in other words how the data transmits<01:14:06.960> over<01:14:07.140> that<01:14:07.380> physical<01:14:07.560> stuff 01:14:11.650 --> 01:14:11.660 align:start position:0% 01:14:11.660 --> 01:14:20.229 align:start position:0% [Music] 01:14:20.229 --> 01:14:20.239 align:start position:0% [Music] 01:14:20.239 --> 01:14:31.490 align:start position:0% [Music] thank<01:14:21.239> you 01:14:31.490 --> 01:14:31.500 align:start position:0% 01:14:31.500 --> 01:14:34.910 align:start position:0% Network<01:14:32.159> hardware<01:14:32.699> and<01:14:33.179> media<01:14:33.920> bounded 01:14:34.910 --> 01:14:34.920 align:start position:0% Network hardware and media bounded 01:14:34.920 --> 01:14:37.490 align:start position:0% Network hardware and media bounded Network<01:14:35.219> media 01:14:37.490 --> 01:14:37.500 align:start position:0% Network media 01:14:37.500 --> 01:14:40.669 align:start position:0% Network media having<01:14:37.920> discussed<01:14:38.580> some<01:14:38.940> of<01:14:39.120> the<01:14:39.679> basic 01:14:40.669 --> 01:14:40.679 align:start position:0% having discussed some of the basic 01:14:40.679 --> 01:14:43.130 align:start position:0% having discussed some of the basic terminology<01:14:41.480> and<01:14:42.480> some<01:14:42.719> of<01:14:42.780> the<01:14:42.900> basic 01:14:43.130 --> 01:14:43.140 align:start position:0% terminology and some of the basic 01:14:43.140 --> 01:14:45.410 align:start position:0% terminology and some of the basic Network<01:14:43.320> setups<01:14:43.980> I<01:14:44.460> want<01:14:44.580> to<01:14:44.699> get<01:14:44.820> into<01:14:45.000> now 01:14:45.410 --> 01:14:45.420 align:start position:0% Network setups I want to get into now 01:14:45.420 --> 01:14:48.470 align:start position:0% Network setups I want to get into now the<01:14:45.780> hardware<01:14:46.080> the<01:14:46.560> media<01:14:47.040> how<01:14:48.000> this<01:14:48.239> stuff 01:14:48.470 --> 01:14:48.480 align:start position:0% the hardware the media how this stuff 01:14:48.480 --> 01:14:50.750 align:start position:0% the hardware the media how this stuff actually<01:14:48.960> physically<01:14:49.679> connects<01:14:50.340> to<01:14:50.640> one 01:14:50.750 --> 01:14:50.760 align:start position:0% actually physically connects to one 01:14:50.760 --> 01:14:51.590 align:start position:0% actually physically connects to one another 01:14:51.590 --> 01:14:51.600 align:start position:0% another 01:14:51.600 --> 01:14:53.270 align:start position:0% another so<01:14:52.140> we're<01:14:52.320> going<01:14:52.500> to<01:14:52.620> discuss<01:14:52.860> the<01:14:53.159> different 01:14:53.270 --> 01:14:53.280 align:start position:0% so we're going to discuss the different 01:14:53.280 --> 01:14:55.910 align:start position:0% so we're going to discuss the different network<01:14:53.580> hardware<01:14:53.940> and<01:14:54.420> media<01:14:54.780> types<01:14:55.199> in<01:14:55.679> this 01:14:55.910 --> 01:14:55.920 align:start position:0% network hardware and media types in this 01:14:55.920 --> 01:14:57.169 align:start position:0% network hardware and media types in this module 01:14:57.169 --> 01:14:57.179 align:start position:0% module 01:14:57.179 --> 01:14:58.610 align:start position:0% module so<01:14:57.600> the<01:14:57.719> objectives<01:14:58.080> that<01:14:58.260> we're<01:14:58.380> going<01:14:58.500> to 01:14:58.610 --> 01:14:58.620 align:start position:0% so the objectives that we're going to 01:14:58.620 --> 01:15:01.610 align:start position:0% so the objectives that we're going to cover<01:14:58.739> are<01:14:59.699> first<01:14:59.940> defining<01:15:00.719> Network<01:15:01.020> media 01:15:01.610 --> 01:15:01.620 align:start position:0% cover are first defining Network media 01:15:01.620 --> 01:15:04.790 align:start position:0% cover are first defining Network media and<01:15:02.400> specifically<01:15:03.000> bounded<01:15:03.960> Network<01:15:04.260> media 01:15:04.790 --> 01:15:04.800 align:start position:0% and specifically bounded Network media 01:15:04.800 --> 01:15:06.890 align:start position:0% and specifically bounded Network media bounded<01:15:05.640> Network<01:15:05.820> media<01:15:06.300> meaning<01:15:06.480> the<01:15:06.719> stuff 01:15:06.890 --> 01:15:06.900 align:start position:0% bounded Network media meaning the stuff 01:15:06.900 --> 01:15:10.070 align:start position:0% bounded Network media meaning the stuff that<01:15:07.140> you<01:15:07.380> can<01:15:07.560> hold<01:15:07.920> bounded<01:15:08.900> contained<01:15:09.900> in 01:15:10.070 --> 01:15:10.080 align:start position:0% that you can hold bounded contained in 01:15:10.080 --> 01:15:13.189 align:start position:0% that you can hold bounded contained in chords<01:15:10.560> and<01:15:10.739> wires<01:15:11.219> unlike<01:15:11.820> unbounded<01:15:12.600> which 01:15:13.189 --> 01:15:13.199 align:start position:0% chords and wires unlike unbounded which 01:15:13.199 --> 01:15:15.590 align:start position:0% chords and wires unlike unbounded which is<01:15:13.380> Wireless<01:15:13.739> we're<01:15:14.699> then<01:15:14.880> going<01:15:15.060> to<01:15:15.179> describe 01:15:15.590 --> 01:15:15.600 align:start position:0% is Wireless we're then going to describe 01:15:15.600 --> 01:15:18.229 align:start position:0% is Wireless we're then going to describe the<01:15:15.840> different<01:15:15.960> types<01:15:16.500> of<01:15:16.739> copper<01:15:17.159> media<01:15:17.580> and 01:15:18.229 --> 01:15:18.239 align:start position:0% the different types of copper media and 01:15:18.239 --> 01:15:20.990 align:start position:0% the different types of copper media and also<01:15:18.540> explain<01:15:18.840> the<01:15:19.199> different<01:15:19.380> types<01:15:19.920> of<01:15:20.219> STP 01:15:20.990 --> 01:15:21.000 align:start position:0% also explain the different types of STP 01:15:21.000 --> 01:15:27.130 align:start position:0% also explain the different types of STP that's<01:15:21.920> shielded<01:15:22.920> twisted<01:15:23.460> pair<01:15:23.719> and<01:15:24.719> UTP 01:15:27.130 --> 01:15:27.140 align:start position:0% that's shielded twisted pair and UTP 01:15:27.140 --> 01:15:29.390 align:start position:0% that's shielded twisted pair and UTP unshielded<01:15:28.140> twisted<01:15:28.560> pair 01:15:29.390 --> 01:15:29.400 align:start position:0% unshielded twisted pair 01:15:29.400 --> 01:15:31.010 align:start position:0% unshielded twisted pair then<01:15:29.880> we'll<01:15:30.060> describe<01:15:30.420> the<01:15:30.540> different<01:15:30.719> types 01:15:31.010 --> 01:15:31.020 align:start position:0% then we'll describe the different types 01:15:31.020 --> 01:15:33.290 align:start position:0% then we'll describe the different types of<01:15:31.140> coaxial<01:15:31.860> cable<01:15:32.219> types<01:15:32.640> and<01:15:32.820> connectors 01:15:33.290 --> 01:15:33.300 align:start position:0% of coaxial cable types and connectors 01:15:33.300 --> 01:15:36.530 align:start position:0% of coaxial cable types and connectors and<01:15:34.080> finally<01:15:34.380> describe<01:15:35.280> fiber<01:15:35.880> optic<01:15:36.179> median 01:15:36.530 --> 01:15:36.540 align:start position:0% and finally describe fiber optic median 01:15:36.540 --> 01:15:38.930 align:start position:0% and finally describe fiber optic median connectors<01:15:37.020> fiber<01:15:37.679> optics<01:15:37.980> being<01:15:38.219> that<01:15:38.699> type 01:15:38.930 --> 01:15:38.940 align:start position:0% connectors fiber optics being that type 01:15:38.940 --> 01:15:39.790 align:start position:0% connectors fiber optics being that type of 01:15:39.790 --> 01:15:39.800 align:start position:0% of 01:15:39.800 --> 01:15:44.149 align:start position:0% of media<01:15:40.800> that<01:15:41.580> is<01:15:41.880> that<01:15:42.600> transmits<01:15:43.320> data<01:15:43.739> via 01:15:44.149 --> 01:15:44.159 align:start position:0% media that is that transmits data via 01:15:44.159 --> 01:15:47.030 align:start position:0% media that is that transmits data via light<01:15:45.060> and<01:15:45.600> photons<01:15:46.080> rather<01:15:46.860> than 01:15:47.030 --> 01:15:47.040 align:start position:0% light and photons rather than 01:15:47.040 --> 01:15:49.729 align:start position:0% light and photons rather than electricity<01:15:47.760> over<01:15:48.540> copper 01:15:49.729 --> 01:15:49.739 align:start position:0% electricity over copper 01:15:49.739 --> 01:15:53.209 align:start position:0% electricity over copper after<01:15:49.860> that<01:15:50.159> I<01:15:50.340> want<01:15:50.400> to<01:15:50.580> explain<01:15:50.760> the<01:15:51.540> 568<01:15:52.500> a<01:15:52.980> b 01:15:53.209 --> 01:15:53.219 align:start position:0% after that I want to explain the 568 a b 01:15:53.219 --> 01:15:56.390 align:start position:0% after that I want to explain the 568 a b and<01:15:53.400> c<01:15:53.699> standards<01:15:54.300> which<01:15:54.480> is<01:15:54.659> how<01:15:55.080> uh<01:15:55.860> standard 01:15:56.390 --> 01:15:56.400 align:start position:0% and c standards which is how uh standard 01:15:56.400 --> 01:16:00.410 align:start position:0% and c standards which is how uh standard UTP<01:15:57.000> and<01:15:57.120> STP<01:15:57.659> is<01:15:58.140> cabled<01:15:58.679> on<01:15:59.640> one<01:15:59.880> end<01:16:00.000> and<01:16:00.239> on 01:16:00.410 --> 01:16:00.420 align:start position:0% UTP and STP is cabled on one end and on 01:16:00.420 --> 01:16:02.570 align:start position:0% UTP and STP is cabled on one end and on the<01:16:00.540> other<01:16:00.659> so<01:16:00.960> we<01:16:01.260> can<01:16:01.320> plug<01:16:01.500> it<01:16:01.679> in<01:16:01.860> and 01:16:02.570 --> 01:16:02.580 align:start position:0% the other so we can plug it in and 01:16:02.580 --> 01:16:04.130 align:start position:0% the other so we can plug it in and finally<01:16:02.820> explain<01:16:03.060> something<01:16:03.420> called<01:16:03.719> premise 01:16:04.130 --> 01:16:04.140 align:start position:0% finally explain something called premise 01:16:04.140 --> 01:16:06.770 align:start position:0% finally explain something called premise wiring<01:16:04.620> and<01:16:05.280> structured<01:16:05.699> cabling 01:16:06.770 --> 01:16:06.780 align:start position:0% wiring and structured cabling 01:16:06.780 --> 01:16:10.550 align:start position:0% wiring and structured cabling so<01:16:07.380> Network<01:16:07.800> media<01:16:08.460> is<01:16:08.880> simply<01:16:09.179> the<01:16:09.600> method<01:16:10.080> or 01:16:10.550 --> 01:16:10.560 align:start position:0% so Network media is simply the method or 01:16:10.560 --> 01:16:14.169 align:start position:0% so Network media is simply the method or medium<01:16:11.040> by<01:16:11.699> which<01:16:12.000> data<01:16:12.540> will<01:16:12.780> be<01:16:13.140> transmitted 01:16:14.169 --> 01:16:14.179 align:start position:0% medium by which data will be transmitted 01:16:14.179 --> 01:16:17.390 align:start position:0% medium by which data will be transmitted it's<01:16:15.179> further<01:16:15.600> classified<01:16:16.199> based<01:16:16.980> on<01:16:17.100> the 01:16:17.390 --> 01:16:17.400 align:start position:0% it's further classified based on the 01:16:17.400 --> 01:16:20.270 align:start position:0% it's further classified based on the hardware<01:16:17.659> and<01:16:18.659> Associated<01:16:19.320> technology<01:16:19.860> of 01:16:20.270 --> 01:16:20.280 align:start position:0% hardware and Associated technology of 01:16:20.280 --> 01:16:22.610 align:start position:0% hardware and Associated technology of the<01:16:20.460> media<01:16:20.760> itself<01:16:21.239> now<01:16:22.080> there<01:16:22.260> are<01:16:22.440> both 01:16:22.610 --> 01:16:22.620 align:start position:0% the media itself now there are both 01:16:22.620 --> 01:16:25.390 align:start position:0% the media itself now there are both wired<01:16:23.280> and<01:16:23.640> wireless<01:16:24.020> Technologies 01:16:25.390 --> 01:16:25.400 align:start position:0% wired and wireless Technologies 01:16:25.400 --> 01:16:28.550 align:start position:0% wired and wireless Technologies associated<01:16:26.400> with<01:16:26.760> network<01:16:27.000> media<01:16:27.600> so<01:16:28.199> in<01:16:28.440> this 01:16:28.550 --> 01:16:28.560 align:start position:0% associated with network media so in this 01:16:28.560 --> 01:16:29.750 align:start position:0% associated with network media so in this one<01:16:28.679> we're<01:16:28.860> going<01:16:28.980> to<01:16:29.040> take<01:16:29.159> a<01:16:29.280> look<01:16:29.400> at<01:16:29.520> the 01:16:29.750 --> 01:16:29.760 align:start position:0% one we're going to take a look at the 01:16:29.760 --> 01:16:32.450 align:start position:0% one we're going to take a look at the first<01:16:29.880> one<01:16:30.199> wired<01:16:31.199> Network<01:16:31.440> media<01:16:31.980> which<01:16:32.340> is 01:16:32.450 --> 01:16:32.460 align:start position:0% first one wired Network media which is 01:16:32.460 --> 01:16:34.910 align:start position:0% first one wired Network media which is also<01:16:32.760> characterized<01:16:33.300> as<01:16:33.480> bounded<01:16:34.260> because<01:16:34.679> it 01:16:34.910 --> 01:16:34.920 align:start position:0% also characterized as bounded because it 01:16:34.920 --> 01:16:36.830 align:start position:0% also characterized as bounded because it is<01:16:35.040> bounded<01:16:35.460> by<01:16:35.699> a<01:16:35.880> chord 01:16:36.830 --> 01:16:36.840 align:start position:0% is bounded by a chord 01:16:36.840 --> 01:16:40.010 align:start position:0% is bounded by a chord so<01:16:37.380> bounded<01:16:37.920> media<01:16:38.460> is<01:16:39.060> media<01:16:39.420> that<01:16:39.600> can<01:16:39.780> be 01:16:40.010 --> 01:16:40.020 align:start position:0% so bounded media is media that can be 01:16:40.020 --> 01:16:42.290 align:start position:0% so bounded media is media that can be physically<01:16:40.380> held<01:16:40.920> there<01:16:41.580> are<01:16:41.699> a<01:16:41.760> few<01:16:41.880> types<01:16:42.179> of 01:16:42.290 --> 01:16:42.300 align:start position:0% physically held there are a few types of 01:16:42.300 --> 01:16:43.970 align:start position:0% physically held there are a few types of bound<01:16:42.480> media<01:16:42.960> that<01:16:43.140> we<01:16:43.260> need<01:16:43.380> to<01:16:43.500> be<01:16:43.620> familiar 01:16:43.970 --> 01:16:43.980 align:start position:0% bound media that we need to be familiar 01:16:43.980 --> 01:16:45.470 align:start position:0% bound media that we need to be familiar with<01:16:44.159> we're<01:16:44.760> going<01:16:44.880> to<01:16:45.000> look<01:16:45.060> at<01:16:45.239> either 01:16:45.470 --> 01:16:45.480 align:start position:0% with we're going to look at either 01:16:45.480 --> 01:16:48.830 align:start position:0% with we're going to look at either copper<01:16:46.260> or<01:16:46.860> Fiber<01:16:47.699> now<01:16:48.120> bounded<01:16:48.659> Network 01:16:48.830 --> 01:16:48.840 align:start position:0% copper or Fiber now bounded Network 01:16:48.840 --> 01:16:51.830 align:start position:0% copper or Fiber now bounded Network media<01:16:49.320> is<01:16:49.560> the<01:16:49.800> basic<01:16:50.280> and<01:16:50.640> original<01:16:51.120> form<01:16:51.600> of 01:16:51.830 --> 01:16:51.840 align:start position:0% media is the basic and original form of 01:16:51.840 --> 01:16:55.189 align:start position:0% media is the basic and original form of media<01:16:52.260> and<01:16:52.679> as<01:16:52.980> administrators<01:16:53.840> you're<01:16:54.840> very 01:16:55.189 --> 01:16:55.199 align:start position:0% media and as administrators you're very 01:16:55.199 --> 01:16:57.830 align:start position:0% media and as administrators you're very likely<01:16:55.620> if<01:16:55.800> not<01:16:56.040> guaranteed<01:16:57.000> at<01:16:57.480> some<01:16:57.659> point 01:16:57.830 --> 01:16:57.840 align:start position:0% likely if not guaranteed at some point 01:16:57.840 --> 01:16:59.689 align:start position:0% likely if not guaranteed at some point to<01:16:58.140> have<01:16:58.320> to<01:16:58.440> work<01:16:58.620> with<01:16:58.860> it<01:16:58.980> in<01:16:59.159> one<01:16:59.340> form<01:16:59.520> or 01:16:59.689 --> 01:16:59.699 align:start position:0% to have to work with it in one form or 01:16:59.699 --> 01:17:00.350 align:start position:0% to have to work with it in one form or another 01:17:00.350 --> 01:17:00.360 align:start position:0% another 01:17:00.360 --> 01:17:02.630 align:start position:0% another so<01:17:00.780> having<01:17:00.960> a<01:17:01.320> solid<01:17:01.620> understanding<01:17:02.159> of<01:17:02.460> the 01:17:02.630 --> 01:17:02.640 align:start position:0% so having a solid understanding of the 01:17:02.640 --> 01:17:05.030 align:start position:0% so having a solid understanding of the different<01:17:02.760> types<01:17:03.420> of<01:17:03.659> bounded<01:17:04.140> media<01:17:04.500> will 01:17:05.030 --> 01:17:05.040 align:start position:0% different types of bounded media will 01:17:05.040 --> 01:17:07.729 align:start position:0% different types of bounded media will help<01:17:05.340> you<01:17:05.460> succeed<01:17:05.940> in<01:17:06.239> managing<01:17:06.719> any<01:17:07.380> type<01:17:07.620> of 01:17:07.729 --> 01:17:07.739 align:start position:0% help you succeed in managing any type of 01:17:07.739 --> 01:17:10.010 align:start position:0% help you succeed in managing any type of network<01:17:07.920> whether<01:17:08.460> it's<01:17:08.640> at<01:17:08.880> your<01:17:09.120> home<01:17:09.360> a 01:17:10.010 --> 01:17:10.020 align:start position:0% network whether it's at your home a 01:17:10.020 --> 01:17:11.990 align:start position:0% network whether it's at your home a small<01:17:10.140> office<01:17:10.440> or<01:17:10.920> even<01:17:11.040> a<01:17:11.460> very<01:17:11.640> large 01:17:11.990 --> 01:17:12.000 align:start position:0% small office or even a very large 01:17:12.000 --> 01:17:14.990 align:start position:0% small office or even a very large corporate<01:17:12.600> win<01:17:12.960> or<01:17:13.260> wide<01:17:13.500> area<01:17:13.679> network<01:17:14.520> so 01:17:14.990 --> 01:17:15.000 align:start position:0% corporate win or wide area network so 01:17:15.000 --> 01:17:16.970 align:start position:0% corporate win or wide area network so the<01:17:15.179> first<01:17:15.300> type<01:17:15.600> of<01:17:15.780> bound<01:17:15.960> Network<01:17:16.380> media<01:17:16.860> I 01:17:16.970 --> 01:17:16.980 align:start position:0% the first type of bound Network media I 01:17:16.980 --> 01:17:19.910 align:start position:0% the first type of bound Network media I want<01:17:17.100> to<01:17:17.219> go<01:17:17.280> over<01:17:17.400> is<01:17:18.120> copper<01:17:18.659> media 01:17:19.910 --> 01:17:19.920 align:start position:0% want to go over is copper media 01:17:19.920 --> 01:17:22.850 align:start position:0% want to go over is copper media copper<01:17:20.640> media<01:17:21.000> is<01:17:21.540> the<01:17:21.780> term<01:17:21.960> used<01:17:22.380> to 01:17:22.850 --> 01:17:22.860 align:start position:0% copper media is the term used to 01:17:22.860 --> 01:17:25.669 align:start position:0% copper media is the term used to describe<01:17:23.340> any<01:17:23.880> media<01:17:24.300> that<01:17:24.600> uses<01:17:24.900> copper 01:17:25.669 --> 01:17:25.679 align:start position:0% describe any media that uses copper 01:17:25.679 --> 01:17:28.189 align:start position:0% describe any media that uses copper conductors<01:17:26.219> as<01:17:26.820> the<01:17:27.120> method<01:17:27.420> to<01:17:27.719> transmit 01:17:28.189 --> 01:17:28.199 align:start position:0% conductors as the method to transmit 01:17:28.199 --> 01:17:30.430 align:start position:0% conductors as the method to transmit data<01:17:28.739> in<01:17:29.340> the<01:17:29.460> form<01:17:29.580> of 01:17:30.430 --> 01:17:30.440 align:start position:0% data in the form of 01:17:30.440 --> 01:17:33.590 align:start position:0% data in the form of electromagnetic<01:17:31.440> energy<01:17:31.620> so<01:17:32.520> copper<01:17:33.120> media 01:17:33.590 --> 01:17:33.600 align:start position:0% electromagnetic energy so copper media 01:17:33.600 --> 01:17:36.290 align:start position:0% electromagnetic energy so copper media can<01:17:33.840> come<01:17:34.080> in<01:17:34.260> many<01:17:34.500> different<01:17:34.860> forms<01:17:35.460> there 01:17:36.290 --> 01:17:36.300 align:start position:0% can come in many different forms there 01:17:36.300 --> 01:17:38.209 align:start position:0% can come in many different forms there are<01:17:36.420> also<01:17:36.780> many<01:17:37.020> considerations<01:17:37.679> that<01:17:38.100> need 01:17:38.209 --> 01:17:38.219 align:start position:0% are also many considerations that need 01:17:38.219 --> 01:17:40.430 align:start position:0% are also many considerations that need to<01:17:38.340> be<01:17:38.460> taken<01:17:38.760> into<01:17:38.940> account<01:17:39.239> when<01:17:39.960> choosing 01:17:40.430 --> 01:17:40.440 align:start position:0% to be taken into account when choosing 01:17:40.440 --> 01:17:42.350 align:start position:0% to be taken into account when choosing between<01:17:40.620> these<01:17:40.980> different<01:17:41.219> types<01:17:41.820> of<01:17:41.940> forms 01:17:42.350 --> 01:17:42.360 align:start position:0% between these different types of forms 01:17:42.360 --> 01:17:45.290 align:start position:0% between these different types of forms such<01:17:42.960> as<01:17:43.199> a<01:17:43.560> distance<01:17:44.060> the<01:17:45.060> speed 01:17:45.290 --> 01:17:45.300 align:start position:0% such as a distance the speed 01:17:45.300 --> 01:17:47.510 align:start position:0% such as a distance the speed requirements<01:17:46.020> of<01:17:46.199> the<01:17:46.380> network<01:17:46.500> and<01:17:47.340> of 01:17:47.510 --> 01:17:47.520 align:start position:0% requirements of the network and of 01:17:47.520 --> 01:17:48.890 align:start position:0% requirements of the network and of course<01:17:47.640> the<01:17:48.000> cost 01:17:48.890 --> 01:17:48.900 align:start position:0% course the cost 01:17:48.900 --> 01:17:51.890 align:start position:0% course the cost a<01:17:49.440> lot<01:17:49.560> of<01:17:49.679> the<01:17:49.800> time<01:17:50.040> uh<01:17:50.760> copper<01:17:51.179> media<01:17:51.540> was 01:17:51.890 --> 01:17:51.900 align:start position:0% a lot of the time uh copper media was 01:17:51.900 --> 01:17:53.570 align:start position:0% a lot of the time uh copper media was going<01:17:52.199> to<01:17:52.260> be<01:17:52.380> fitted<01:17:52.739> with<01:17:53.040> some<01:17:53.280> sort<01:17:53.460> of 01:17:53.570 --> 01:17:53.580 align:start position:0% going to be fitted with some sort of 01:17:53.580 --> 01:17:56.030 align:start position:0% going to be fitted with some sort of shielding<01:17:54.179> which<01:17:54.719> also<01:17:55.020> looks<01:17:55.260> like<01:17:55.380> braided 01:17:56.030 --> 01:17:56.040 align:start position:0% shielding which also looks like braided 01:17:56.040 --> 01:17:57.950 align:start position:0% shielding which also looks like braided metal<01:17:56.280> wires<01:17:56.820> or<01:17:57.060> sometimes<01:17:57.360> it<01:17:57.540> looks<01:17:57.719> like<01:17:57.780> a 01:17:57.950 --> 01:17:57.960 align:start position:0% metal wires or sometimes it looks like a 01:17:57.960 --> 01:17:59.689 align:start position:0% metal wires or sometimes it looks like a metallic<01:17:58.380> foil<01:17:58.800> like<01:17:59.159> you<01:17:59.280> buy<01:17:59.460> at<01:17:59.580> the 01:17:59.689 --> 01:17:59.699 align:start position:0% metallic foil like you buy at the 01:17:59.699 --> 01:18:01.130 align:start position:0% metallic foil like you buy at the grocery<01:17:59.820> store<01:18:00.179> but<01:18:00.420> it<01:18:00.600> is<01:18:00.900> a<01:18:01.080> little 01:18:01.130 --> 01:18:01.140 align:start position:0% grocery store but it is a little 01:18:01.140 --> 01:18:03.110 align:start position:0% grocery store but it is a little different<01:18:01.440> the<01:18:02.280> shielding<01:18:02.699> on<01:18:02.880> the<01:18:03.000> outside 01:18:03.110 --> 01:18:03.120 align:start position:0% different the shielding on the outside 01:18:03.120 --> 01:18:07.729 align:start position:0% different the shielding on the outside helps<01:18:03.980> the<01:18:04.980> cable<01:18:05.280> prevent<01:18:06.000> or<01:18:06.360> helps<01:18:06.780> prevent 01:18:07.729 --> 01:18:07.739 align:start position:0% helps the cable prevent or helps prevent 01:18:07.739 --> 01:18:11.149 align:start position:0% helps the cable prevent or helps prevent the<01:18:08.100> cable<01:18:08.340> from<01:18:08.940> being<01:18:09.540> uh<01:18:10.440> subjected<01:18:10.980> to 01:18:11.149 --> 01:18:11.159 align:start position:0% the cable from being uh subjected to 01:18:11.159 --> 01:18:12.709 align:start position:0% the cable from being uh subjected to what's<01:18:11.340> called<01:18:11.719> electromagnetic 01:18:12.709 --> 01:18:12.719 align:start position:0% what's called electromagnetic 01:18:12.719 --> 01:18:17.510 align:start position:0% what's called electromagnetic interference<01:18:13.440> or<01:18:14.340> Emi<01:18:15.620> and<01:18:16.620> of<01:18:16.860> course<01:18:16.980> if<01:18:17.340> I 01:18:17.510 --> 01:18:17.520 align:start position:0% interference or Emi and of course if I 01:18:17.520 --> 01:18:19.250 align:start position:0% interference or Emi and of course if I allow<01:18:17.940> Emi<01:18:18.420> or<01:18:18.540> electromagnetic 01:18:19.250 --> 01:18:19.260 align:start position:0% allow Emi or electromagnetic 01:18:19.260 --> 01:18:21.410 align:start position:0% allow Emi or electromagnetic interference<01:18:19.920> to<01:18:20.159> get<01:18:20.340> into<01:18:20.699> the<01:18:21.060> copper 01:18:21.410 --> 01:18:21.420 align:start position:0% interference to get into the copper 01:18:21.420 --> 01:18:23.209 align:start position:0% interference to get into the copper within<01:18:21.840> the<01:18:21.960> cable<01:18:22.199> then<01:18:22.679> that's<01:18:22.920> going<01:18:23.100> to 01:18:23.209 --> 01:18:23.219 align:start position:0% within the cable then that's going to 01:18:23.219 --> 01:18:25.010 align:start position:0% within the cable then that's going to disrupt<01:18:23.699> the<01:18:23.880> sort<01:18:24.060> of<01:18:24.179> data<01:18:24.480> that's<01:18:24.659> going<01:18:24.840> on 01:18:25.010 --> 01:18:25.020 align:start position:0% disrupt the sort of data that's going on 01:18:25.020 --> 01:18:28.250 align:start position:0% disrupt the sort of data that's going on inside<01:18:25.260> of<01:18:25.500> it<01:18:26.040> now<01:18:26.520> there<01:18:26.880> are<01:18:27.000> two<01:18:27.600> uh 01:18:28.250 --> 01:18:28.260 align:start position:0% inside of it now there are two uh 01:18:28.260 --> 01:18:30.590 align:start position:0% inside of it now there are two uh different<01:18:28.739> types<01:18:29.340> of<01:18:29.520> very<01:18:29.760> common<01:18:30.060> copper 01:18:30.590 --> 01:18:30.600 align:start position:0% different types of very common copper 01:18:30.600 --> 01:18:32.870 align:start position:0% different types of very common copper media<01:18:30.900> that<01:18:31.080> I<01:18:31.140> want<01:18:31.199> to<01:18:31.320> go<01:18:31.440> off<01:18:31.820> uh<01:18:32.820> uh 01:18:32.870 --> 01:18:32.880 align:start position:0% media that I want to go off uh uh 01:18:32.880 --> 01:18:37.010 align:start position:0% media that I want to go off uh uh specifically<01:18:33.719> of<01:18:33.960> coaxial<01:18:34.739> or<01:18:35.460> coax<01:18:35.840> as<01:18:36.840> shown 01:18:37.010 --> 01:18:37.020 align:start position:0% specifically of coaxial or coax as shown 01:18:37.020 --> 01:18:39.590 align:start position:0% specifically of coaxial or coax as shown here<01:18:37.380> and<01:18:38.159> twisted<01:18:38.580> pair 01:18:39.590 --> 01:18:39.600 align:start position:0% here and twisted pair 01:18:39.600 --> 01:18:42.830 align:start position:0% here and twisted pair now<01:18:40.020> twisted<01:18:40.440> pair<01:18:40.679> table<01:18:41.340> is<01:18:41.940> one<01:18:42.600> of<01:18:42.659> the 01:18:42.830 --> 01:18:42.840 align:start position:0% now twisted pair table is one of the 01:18:42.840 --> 01:18:44.689 align:start position:0% now twisted pair table is one of the most<01:18:42.960> common<01:18:43.320> cable<01:18:43.679> types<01:18:44.100> that<01:18:44.219> you<01:18:44.460> need<01:18:44.580> to 01:18:44.689 --> 01:18:44.699 align:start position:0% most common cable types that you need to 01:18:44.699 --> 01:18:46.790 align:start position:0% most common cable types that you need to be<01:18:44.820> familiar<01:18:45.179> with<01:18:45.380> depending<01:18:46.380> on<01:18:46.620> the 01:18:46.790 --> 01:18:46.800 align:start position:0% be familiar with depending on the 01:18:46.800 --> 01:18:48.770 align:start position:0% be familiar with depending on the specification<01:18:47.460> of<01:18:47.820> the<01:18:47.940> cable<01:18:48.120> and<01:18:48.360> the<01:18:48.600> type 01:18:48.770 --> 01:18:48.780 align:start position:0% specification of the cable and the type 01:18:48.780 --> 01:18:51.229 align:start position:0% specification of the cable and the type of<01:18:48.960> twisted<01:18:49.380> pair<01:18:49.560> cable<01:18:50.100> being<01:18:50.400> used<01:18:50.699> there's 01:18:51.229 --> 01:18:51.239 align:start position:0% of twisted pair cable being used there's 01:18:51.239 --> 01:18:53.450 align:start position:0% of twisted pair cable being used there's going<01:18:51.420> to<01:18:51.480> be<01:18:51.540> anywhere<01:18:51.840> from<01:18:52.199> two<01:18:52.679> to<01:18:53.159> a 01:18:53.450 --> 01:18:53.460 align:start position:0% going to be anywhere from two to a 01:18:53.460 --> 01:18:55.729 align:start position:0% going to be anywhere from two to a hundred<01:18:53.699> pairs<01:18:54.300> or<01:18:54.719> more 01:18:55.729 --> 01:18:55.739 align:start position:0% hundred pairs or more 01:18:55.739 --> 01:18:58.669 align:start position:0% hundred pairs or more now<01:18:56.280> the<01:18:56.520> pairs<01:18:56.940> are<01:18:57.239> color<01:18:57.420> coded<01:18:57.900> so<01:18:58.440> the 01:18:58.669 --> 01:18:58.679 align:start position:0% now the pairs are color coded so the 01:18:58.679 --> 01:19:01.310 align:start position:0% now the pairs are color coded so the technicians<01:18:59.280> know<01:18:59.580> how<01:18:59.940> to<01:19:00.060> recable<01:19:00.540> the 01:19:01.310 --> 01:19:01.320 align:start position:0% technicians know how to recable the 01:19:01.320 --> 01:19:03.649 align:start position:0% technicians know how to recable the cables<01:19:01.679> on<01:19:01.800> either<01:19:01.980> end<01:19:02.219> and<01:19:02.940> it<01:19:03.120> ensures<01:19:03.420> that 01:19:03.649 --> 01:19:03.659 align:start position:0% cables on either end and it ensures that 01:19:03.659 --> 01:19:05.930 align:start position:0% cables on either end and it ensures that certain<01:19:03.900> wiring<01:19:04.560> standards<01:19:05.219> and<01:19:05.400> schemes<01:19:05.820> are 01:19:05.930 --> 01:19:05.940 align:start position:0% certain wiring standards and schemes are 01:19:05.940 --> 01:19:07.550 align:start position:0% certain wiring standards and schemes are maintained<01:19:06.300> in<01:19:06.540> case<01:19:06.719> another<01:19:07.020> technician 01:19:07.550 --> 01:19:07.560 align:start position:0% maintained in case another technician 01:19:07.560 --> 01:19:09.290 align:start position:0% maintained in case another technician was<01:19:07.739> to<01:19:07.920> come<01:19:08.100> in<01:19:08.219> and<01:19:08.400> start<01:19:08.699> or<01:19:08.880> end<01:19:09.060> the<01:19:09.179> work 01:19:09.290 --> 01:19:09.300 align:start position:0% was to come in and start or end the work 01:19:09.300 --> 01:19:10.790 align:start position:0% was to come in and start or end the work that<01:19:09.540> you've<01:19:09.719> already<01:19:09.840> begun 01:19:10.790 --> 01:19:10.800 align:start position:0% that you've already begun 01:19:10.800 --> 01:19:13.370 align:start position:0% that you've already begun now<01:19:11.460> all<01:19:11.760> twisted<01:19:12.179> pair<01:19:12.360> cables<01:19:12.900> are 01:19:13.370 --> 01:19:13.380 align:start position:0% now all twisted pair cables are 01:19:13.380 --> 01:19:16.070 align:start position:0% now all twisted pair cables are basically<01:19:13.739> the<01:19:14.040> same<01:19:14.219> however<01:19:14.760> it's<01:19:15.540> how<01:19:15.780> they 01:19:16.070 --> 01:19:16.080 align:start position:0% basically the same however it's how they 01:19:16.080 --> 01:19:17.630 align:start position:0% basically the same however it's how they are<01:19:16.260> terminated<01:19:16.679> that<01:19:17.040> makes<01:19:17.219> the<01:19:17.460> biggest 01:19:17.630 --> 01:19:17.640 align:start position:0% are terminated that makes the biggest 01:19:17.640 --> 01:19:20.630 align:start position:0% are terminated that makes the biggest difference<01:19:18.120> meaning<01:19:18.960> how<01:19:19.440> the<01:19:19.860> end<01:19:20.040> points<01:19:20.520> so 01:19:20.630 --> 01:19:20.640 align:start position:0% difference meaning how the end points so 01:19:20.640 --> 01:19:22.729 align:start position:0% difference meaning how the end points so what<01:19:20.940> happens<01:19:21.000> at<01:19:21.300> the<01:19:21.420> end<01:19:21.480> points<01:19:21.960> now<01:19:22.500> there 01:19:22.729 --> 01:19:22.739 align:start position:0% what happens at the end points now there 01:19:22.739 --> 01:19:25.130 align:start position:0% what happens at the end points now there are<01:19:22.980> two<01:19:23.460> typical<01:19:24.000> types<01:19:24.480> of<01:19:24.540> standards<01:19:24.960> that 01:19:25.130 --> 01:19:25.140 align:start position:0% are two typical types of standards that 01:19:25.140 --> 01:19:28.149 align:start position:0% are two typical types of standards that we<01:19:25.199> need<01:19:25.320> to<01:19:25.440> be<01:19:25.500> aware<01:19:25.800> of<01:19:25.980> these<01:19:26.820> are<01:19:26.940> uh 01:19:28.149 --> 01:19:28.159 align:start position:0% we need to be aware of these are uh 01:19:28.159 --> 01:19:33.530 align:start position:0% we need to be aware of these are uh t568<01:19:29.159> a<01:19:29.880> and<01:19:30.679> t568b<01:19:31.940> so<01:19:32.940> we're<01:19:33.239> going<01:19:33.360> to<01:19:33.420> take 01:19:33.530 --> 01:19:33.540 align:start position:0% t568 a and t568b so we're going to take 01:19:33.540 --> 01:19:35.630 align:start position:0% t568 a and t568b so we're going to take a<01:19:33.659> look<01:19:33.780> at<01:19:33.960> these<01:19:34.199> right<01:19:34.500> now 01:19:35.630 --> 01:19:35.640 align:start position:0% a look at these right now 01:19:35.640 --> 01:19:40.070 align:start position:0% a look at these right now now<01:19:36.140> 568a<01:19:37.280> it's<01:19:38.280> less<01:19:38.580> common<01:19:38.880> than<01:19:39.239> 568b 01:19:40.070 --> 01:19:40.080 align:start position:0% now 568a it's less common than 568b 01:19:40.080 --> 01:19:42.350 align:start position:0% now 568a it's less common than 568b today<01:19:40.440> in<01:19:40.739> today's<01:19:40.920> networks<01:19:41.520> but<01:19:41.940> it's<01:19:42.120> still 01:19:42.350 --> 01:19:42.360 align:start position:0% today in today's networks but it's still 01:19:42.360 --> 01:19:43.970 align:start position:0% today in today's networks but it's still necessary<01:19:42.780> for<01:19:43.080> you<01:19:43.199> to<01:19:43.380> know<01:19:43.500> and<01:19:43.739> you<01:19:43.860> need 01:19:43.970 --> 01:19:43.980 align:start position:0% necessary for you to know and you need 01:19:43.980 --> 01:19:45.470 align:start position:0% necessary for you to know and you need to<01:19:44.100> understand<01:19:44.280> the<01:19:44.699> difference<01:19:44.820> between<01:19:45.179> the 01:19:45.470 --> 01:19:45.480 align:start position:0% to understand the difference between the 01:19:45.480 --> 01:19:48.830 align:start position:0% to understand the difference between the two<01:19:45.600> of<01:19:45.780> these<01:19:46.020> uh<01:19:46.860> and<01:19:47.360> it'll<01:19:48.360> also<01:19:48.600> help<01:19:48.719> you 01:19:48.830 --> 01:19:48.840 align:start position:0% two of these uh and it'll also help you 01:19:48.840 --> 01:19:50.030 align:start position:0% two of these uh and it'll also help you in<01:19:48.900> case<01:19:49.080> you<01:19:49.199> ever<01:19:49.320> wanted<01:19:49.500> to<01:19:49.620> make<01:19:49.739> a<01:19:49.860> cable 01:19:50.030 --> 01:19:50.040 align:start position:0% in case you ever wanted to make a cable 01:19:50.040 --> 01:19:51.310 align:start position:0% in case you ever wanted to make a cable at<01:19:50.280> home 01:19:51.310 --> 01:19:51.320 align:start position:0% at home 01:19:51.320 --> 01:19:55.790 align:start position:0% at home 568<01:19:52.320> a<01:19:52.800> is<01:19:53.460> wired<01:19:53.880> in<01:19:54.060> this<01:19:54.239> way<01:19:54.360> green<01:19:55.020> white 01:19:55.790 --> 01:19:55.800 align:start position:0% 568 a is wired in this way green white 01:19:55.800 --> 01:19:57.110 align:start position:0% 568 a is wired in this way green white green 01:19:57.110 --> 01:19:57.120 align:start position:0% green 01:19:57.120 --> 01:19:58.669 align:start position:0% green orange<01:19:57.659> white 01:19:58.669 --> 01:19:58.679 align:start position:0% orange white 01:19:58.679 --> 01:19:59.990 align:start position:0% orange white blue 01:19:59.990 --> 01:20:00.000 align:start position:0% blue 01:20:00.000 --> 01:20:01.430 align:start position:0% blue White 01:20:01.430 --> 01:20:01.440 align:start position:0% White 01:20:01.440 --> 01:20:02.930 align:start position:0% White Orange 01:20:02.930 --> 01:20:02.940 align:start position:0% Orange 01:20:02.940 --> 01:20:05.330 align:start position:0% Orange brown<01:20:03.420> white<01:20:03.659> brown 01:20:05.330 --> 01:20:05.340 align:start position:0% brown white brown 01:20:05.340 --> 01:20:08.570 align:start position:0% brown white brown now<01:20:05.760> the<01:20:06.000> only<01:20:06.120> difference<01:20:06.540> between<01:20:07.500> the<01:20:07.920> 568 01:20:08.570 --> 01:20:08.580 align:start position:0% now the only difference between the 568 01:20:08.580 --> 01:20:13.010 align:start position:0% now the only difference between the 568 a<01:20:09.179> cabling<01:20:09.780> standard<01:20:10.679> and<01:20:11.040> 568b<01:20:11.940> is<01:20:12.540> that<01:20:12.719> the 01:20:13.010 --> 01:20:13.020 align:start position:0% a cabling standard and 568b is that the 01:20:13.020 --> 01:20:16.070 align:start position:0% a cabling standard and 568b is that the first<01:20:13.260> two<01:20:13.620> pins<01:20:13.980> one<01:20:14.340> and<01:20:14.580> two<01:20:14.760> are<01:20:15.540> swapped 01:20:16.070 --> 01:20:16.080 align:start position:0% first two pins one and two are swapped 01:20:16.080 --> 01:20:19.550 align:start position:0% first two pins one and two are swapped with<01:20:16.560> pins<01:20:16.920> three<01:20:17.400> and<01:20:17.699> six<01:20:17.960> that<01:20:18.960> means<01:20:19.260> that 01:20:19.550 --> 01:20:19.560 align:start position:0% with pins three and six that means that 01:20:19.560 --> 01:20:22.189 align:start position:0% with pins three and six that means that the<01:20:19.980> orange<01:20:20.460> colored<01:20:21.120> wires<01:20:21.540> are<01:20:21.840> swapped 01:20:22.189 --> 01:20:22.199 align:start position:0% the orange colored wires are swapped 01:20:22.199 --> 01:20:24.830 align:start position:0% the orange colored wires are swapped with<01:20:22.320> the<01:20:22.560> green<01:20:22.739> colored<01:20:23.219> wires<01:20:23.580> so<01:20:24.300> then<01:20:24.540> in 01:20:24.830 --> 01:20:24.840 align:start position:0% with the green colored wires so then in 01:20:24.840 --> 01:20:28.030 align:start position:0% with the green colored wires so then in 568b<01:20:25.800> we<01:20:26.460> see<01:20:26.640> a<01:20:26.820> wiring<01:20:27.120> of<01:20:27.300> orange<01:20:27.600> white 01:20:28.030 --> 01:20:28.040 align:start position:0% 568b we see a wiring of orange white 01:20:28.040 --> 01:20:32.390 align:start position:0% 568b we see a wiring of orange white orange<01:20:29.239> green<01:20:30.239> white<01:20:30.600> blue 01:20:32.390 --> 01:20:32.400 align:start position:0% orange green white blue 01:20:32.400 --> 01:20:34.970 align:start position:0% orange green white blue blue<01:20:33.179> white<01:20:33.480> green 01:20:34.970 --> 01:20:34.980 align:start position:0% blue white green 01:20:34.980 --> 01:20:38.689 align:start position:0% blue white green brown<01:20:35.760> white<01:20:36.000> and<01:20:36.900> brown 01:20:38.689 --> 01:20:38.699 align:start position:0% brown white and brown 01:20:38.699 --> 01:20:40.070 align:start position:0% brown white and brown now 01:20:40.070 --> 01:20:40.080 align:start position:0% now 01:20:40.080 --> 01:20:41.930 align:start position:0% now the<01:20:40.860> reason<01:20:40.920> you<01:20:41.219> need<01:20:41.340> to<01:20:41.460> know<01:20:41.580> both<01:20:41.760> of 01:20:41.930 --> 01:20:41.940 align:start position:0% the reason you need to know both of 01:20:41.940 --> 01:20:43.370 align:start position:0% the reason you need to know both of those<01:20:42.060> is<01:20:42.360> because<01:20:42.480> of<01:20:42.719> something<01:20:43.020> called 01:20:43.370 --> 01:20:43.380 align:start position:0% those is because of something called 01:20:43.380 --> 01:20:45.169 align:start position:0% those is because of something called crossover<01:20:43.920> cables<01:20:44.400> which<01:20:44.640> we'll<01:20:44.760> talk<01:20:45.000> about 01:20:45.169 --> 01:20:45.179 align:start position:0% crossover cables which we'll talk about 01:20:45.179 --> 01:20:48.350 align:start position:0% crossover cables which we'll talk about by<01:20:45.840> switching<01:20:46.320> those<01:20:46.739> uh<01:20:47.159> pins<01:20:47.520> around<01:20:48.000> it 01:20:48.350 --> 01:20:48.360 align:start position:0% by switching those uh pins around it 01:20:48.360 --> 01:20:50.570 align:start position:0% by switching those uh pins around it switches<01:20:48.960> the<01:20:49.140> data<01:20:49.440> and<01:20:49.560> how<01:20:49.739> it's<01:20:49.920> sent<01:20:50.159> and 01:20:50.570 --> 01:20:50.580 align:start position:0% switches the data and how it's sent and 01:20:50.580 --> 01:20:52.610 align:start position:0% switches the data and how it's sent and we'll<01:20:50.640> talk<01:20:50.880> about<01:20:51.000> the<01:20:51.600> purpose<01:20:51.900> of<01:20:52.080> that<01:20:52.260> a 01:20:52.610 --> 01:20:52.620 align:start position:0% we'll talk about the purpose of that a 01:20:52.620 --> 01:20:54.110 align:start position:0% we'll talk about the purpose of that a little<01:20:52.800> bit<01:20:52.920> later<01:20:53.100> on 01:20:54.110 --> 01:20:54.120 align:start position:0% little bit later on 01:20:54.120 --> 01:20:55.669 align:start position:0% little bit later on but<01:20:54.540> for<01:20:54.840> now<01:20:54.960> let's<01:20:55.080> talk<01:20:55.320> about<01:20:55.440> something 01:20:55.669 --> 01:20:55.679 align:start position:0% but for now let's talk about something 01:20:55.679 --> 01:20:59.209 align:start position:0% but for now let's talk about something called<01:20:56.000> STP<01:20:57.000> or<01:20:57.960> shielded<01:20:58.620> twisted<01:20:59.040> pair 01:20:59.209 --> 01:20:59.219 align:start position:0% called STP or shielded twisted pair 01:20:59.219 --> 01:21:01.910 align:start position:0% called STP or shielded twisted pair cabling<01:20:59.699> which<01:21:00.300> is<01:21:00.540> a<01:21:00.719> cable<01:21:00.900> type<01:21:01.199> that 01:21:01.910 --> 01:21:01.920 align:start position:0% cabling which is a cable type that 01:21:01.920 --> 01:21:04.430 align:start position:0% cabling which is a cable type that contains<01:21:02.460> pairs<01:21:02.940> of<01:21:03.060> copper<01:21:03.480> strands<01:21:03.960> like<01:21:04.320> we 01:21:04.430 --> 01:21:04.440 align:start position:0% contains pairs of copper strands like we 01:21:04.440 --> 01:21:06.110 align:start position:0% contains pairs of copper strands like we just<01:21:04.620> looked<01:21:04.800> at<01:21:04.920> orange<01:21:05.280> white<01:21:05.580> and<01:21:05.940> orange 01:21:06.110 --> 01:21:06.120 align:start position:0% just looked at orange white and orange 01:21:06.120 --> 01:21:08.570 align:start position:0% just looked at orange white and orange for<01:21:06.480> instance<01:21:06.659> being<01:21:06.960> a<01:21:07.199> pair<01:21:07.340> that<01:21:08.340> are 01:21:08.570 --> 01:21:08.580 align:start position:0% for instance being a pair that are 01:21:08.580 --> 01:21:10.970 align:start position:0% for instance being a pair that are twisted<01:21:09.000> together<01:21:09.239> and<01:21:10.080> wrapped<01:21:10.500> with<01:21:10.739> a 01:21:10.970 --> 01:21:10.980 align:start position:0% twisted together and wrapped with a 01:21:10.980 --> 01:21:14.390 align:start position:0% twisted together and wrapped with a metal<01:21:11.219> sheath<01:21:11.880> or<01:21:12.600> a<01:21:12.840> kind<01:21:13.140> of<01:21:13.320> foil<01:21:13.860> that 01:21:14.390 --> 01:21:14.400 align:start position:0% metal sheath or a kind of foil that 01:21:14.400 --> 01:21:16.370 align:start position:0% metal sheath or a kind of foil that decreases<01:21:14.880> the<01:21:15.120> cable<01:21:15.300> susceptibility<01:21:16.080> as 01:21:16.370 --> 01:21:16.380 align:start position:0% decreases the cable susceptibility as 01:21:16.380 --> 01:21:18.649 align:start position:0% decreases the cable susceptibility as we've<01:21:16.560> already<01:21:16.679> mentioned<01:21:17.100> to<01:21:17.340> Emi<01:21:17.880> now 01:21:18.649 --> 01:21:18.659 align:start position:0% we've already mentioned to Emi now 01:21:18.659 --> 01:21:20.870 align:start position:0% we've already mentioned to Emi now because<01:21:19.020> it's<01:21:19.320> wrapped<01:21:19.679> in<01:21:19.800> its<01:21:20.100> metal<01:21:20.219> it 01:21:20.870 --> 01:21:20.880 align:start position:0% because it's wrapped in its metal it 01:21:20.880 --> 01:21:23.570 align:start position:0% because it's wrapped in its metal it makes<01:21:21.060> the<01:21:21.300> cable<01:21:21.480> much<01:21:22.380> more<01:21:22.620> expensive<01:21:23.219> than 01:21:23.570 --> 01:21:23.580 align:start position:0% makes the cable much more expensive than 01:21:23.580 --> 01:21:27.110 align:start position:0% makes the cable much more expensive than its<01:21:24.000> counterpart<01:21:24.739> UTP<01:21:25.739> or<01:21:26.460> unshielded 01:21:27.110 --> 01:21:27.120 align:start position:0% its counterpart UTP or unshielded 01:21:27.120 --> 01:21:29.030 align:start position:0% its counterpart UTP or unshielded twisted<01:21:27.480> pair<01:21:27.659> and<01:21:28.260> it<01:21:28.440> can<01:21:28.560> make<01:21:28.679> it<01:21:28.860> more 01:21:29.030 --> 01:21:29.040 align:start position:0% twisted pair and it can make it more 01:21:29.040 --> 01:21:30.890 align:start position:0% twisted pair and it can make it more difficult<01:21:29.400> therefore<01:21:30.000> to<01:21:30.239> manage<01:21:30.540> or<01:21:30.659> work 01:21:30.890 --> 01:21:30.900 align:start position:0% difficult therefore to manage or work 01:21:30.900 --> 01:21:33.290 align:start position:0% difficult therefore to manage or work with<01:21:31.080> now<01:21:31.920> although<01:21:32.219> it<01:21:32.460> has<01:21:32.640> the<01:21:32.880> shielding 01:21:33.290 --> 01:21:33.300 align:start position:0% with now although it has the shielding 01:21:33.300 --> 01:21:35.630 align:start position:0% with now although it has the shielding to<01:21:33.480> prevent<01:21:33.780> it<01:21:33.900> from<01:21:34.140> Emi<01:21:34.620> it<01:21:35.280> doesn't<01:21:35.400> mean 01:21:35.630 --> 01:21:35.640 align:start position:0% to prevent it from Emi it doesn't mean 01:21:35.640 --> 01:21:38.750 align:start position:0% to prevent it from Emi it doesn't mean the<01:21:35.940> cable<01:21:36.179> is<01:21:36.480> prevented<01:21:37.020> completely<01:21:37.980> from 01:21:38.750 --> 01:21:38.760 align:start position:0% the cable is prevented completely from 01:21:38.760 --> 01:21:40.669 align:start position:0% the cable is prevented completely from any<01:21:39.000> sort<01:21:39.179> of<01:21:39.300> susceptibility<01:21:39.900> it<01:21:40.500> just 01:21:40.669 --> 01:21:40.679 align:start position:0% any sort of susceptibility it just 01:21:40.679 --> 01:21:42.830 align:start position:0% any sort of susceptibility it just reduces<01:21:41.159> it<01:21:41.340> I<01:21:41.880> also<01:21:42.120> want<01:21:42.239> to<01:21:42.360> mention<01:21:42.480> the 01:21:42.830 --> 01:21:42.840 align:start position:0% reduces it I also want to mention the 01:21:42.840 --> 01:21:45.430 align:start position:0% reduces it I also want to mention the reason<01:21:42.960> that<01:21:43.260> we<01:21:43.500> have<01:21:43.679> that<01:21:44.040> twisted<01:21:44.580> pair 01:21:45.430 --> 01:21:45.440 align:start position:0% reason that we have that twisted pair 01:21:45.440 --> 01:21:48.229 align:start position:0% reason that we have that twisted pair each<01:21:46.440> pair<01:21:46.739> of<01:21:47.040> cables<01:21:47.580> for<01:21:47.699> instance<01:21:47.880> orange 01:21:48.229 --> 01:21:48.239 align:start position:0% each pair of cables for instance orange 01:21:48.239 --> 01:21:51.410 align:start position:0% each pair of cables for instance orange and<01:21:49.140> white<01:21:50.100> orange<01:21:50.340> are<01:21:50.640> twisted<01:21:51.000> together<01:21:51.120> is 01:21:51.410 --> 01:21:51.420 align:start position:0% and white orange are twisted together is 01:21:51.420 --> 01:21:54.050 align:start position:0% and white orange are twisted together is to<01:21:51.540> reduce<01:21:51.719> what<01:21:51.960> we<01:21:52.080> call<01:21:52.340> crosstalk<01:21:53.340> meaning 01:21:54.050 --> 01:21:54.060 align:start position:0% to reduce what we call crosstalk meaning 01:21:54.060 --> 01:21:56.689 align:start position:0% to reduce what we call crosstalk meaning that<01:21:54.840> so<01:21:55.500> that<01:21:55.679> the<01:21:55.860> data<01:21:56.219> doesn't<01:21:56.340> sort<01:21:56.580> of 01:21:56.689 --> 01:21:56.699 align:start position:0% that so that the data doesn't sort of 01:21:56.699 --> 01:21:58.550 align:start position:0% that so that the data doesn't sort of jump<01:21:56.880> between<01:21:57.179> the<01:21:57.480> two<01:21:57.600> cables<01:21:58.080> this<01:21:58.440> was 01:21:58.550 --> 01:21:58.560 align:start position:0% jump between the two cables this was 01:21:58.560 --> 01:21:59.750 align:start position:0% jump between the two cables this was something<01:21:58.739> that<01:21:58.920> was<01:21:59.040> actually<01:21:59.219> discovered 01:21:59.750 --> 01:21:59.760 align:start position:0% something that was actually discovered 01:21:59.760 --> 01:22:01.790 align:start position:0% something that was actually discovered way<01:22:00.300> back<01:22:00.480> when<01:22:00.659> when<01:22:00.900> Edison<01:22:01.320> was<01:22:01.560> dealing 01:22:01.790 --> 01:22:01.800 align:start position:0% way back when when Edison was dealing 01:22:01.800 --> 01:22:04.850 align:start position:0% way back when when Edison was dealing with<01:22:01.920> electricity<01:22:02.460> now<01:22:03.300> UTP<01:22:04.020> or<01:22:04.260> unshielded 01:22:04.850 --> 01:22:04.860 align:start position:0% with electricity now UTP or unshielded 01:22:04.860 --> 01:22:06.830 align:start position:0% with electricity now UTP or unshielded twisted<01:22:05.219> pair<01:22:05.400> cabling<01:22:05.880> does<01:22:06.300> not<01:22:06.480> have<01:22:06.600> that 01:22:06.830 --> 01:22:06.840 align:start position:0% twisted pair cabling does not have that 01:22:06.840 --> 01:22:08.570 align:start position:0% twisted pair cabling does not have that metal<01:22:07.020> shielding<01:22:07.500> around<01:22:07.679> the<01:22:07.920> Twisted<01:22:08.280> pairs 01:22:08.570 --> 01:22:08.580 align:start position:0% metal shielding around the Twisted pairs 01:22:08.580 --> 01:22:10.669 align:start position:0% metal shielding around the Twisted pairs this<01:22:08.760> is<01:22:08.880> the<01:22:09.060> only<01:22:09.300> difference<01:22:09.600> now<01:22:10.380> this 01:22:10.669 --> 01:22:10.679 align:start position:0% this is the only difference now this 01:22:10.679 --> 01:22:12.470 align:start position:0% this is the only difference now this makes<01:22:10.860> the<01:22:11.040> cable<01:22:11.280> much<01:22:11.580> more<01:22:11.760> susceptible<01:22:12.239> to 01:22:12.470 --> 01:22:12.480 align:start position:0% makes the cable much more susceptible to 01:22:12.480 --> 01:22:15.229 align:start position:0% makes the cable much more susceptible to Emi<01:22:12.900> than<01:22:13.080> sdp<01:22:13.620> however<01:22:14.219> it's<01:22:14.400> so<01:22:14.640> inexpensive 01:22:15.229 --> 01:22:15.239 align:start position:0% Emi than sdp however it's so inexpensive 01:22:15.239 --> 01:22:18.229 align:start position:0% Emi than sdp however it's so inexpensive and<01:22:15.659> so<01:22:15.840> much<01:22:16.020> easier<01:22:16.500> to<01:22:17.340> install<01:22:17.699> and 01:22:18.229 --> 01:22:18.239 align:start position:0% and so much easier to install and 01:22:18.239 --> 01:22:20.930 align:start position:0% and so much easier to install and maneuver<01:22:18.600> with<01:22:18.840> and<01:22:19.440> in<01:22:19.739> most<01:22:19.860> instances<01:22:20.460> a 01:22:20.930 --> 01:22:20.940 align:start position:0% maneuver with and in most instances a 01:22:20.940 --> 01:22:23.030 align:start position:0% maneuver with and in most instances a lot<01:22:21.179> of<01:22:21.300> folks<01:22:21.540> don't<01:22:21.840> need<01:22:22.080> the<01:22:22.320> extra<01:22:22.440> Emi 01:22:23.030 --> 01:22:23.040 align:start position:0% lot of folks don't need the extra Emi 01:22:23.040 --> 01:22:24.709 align:start position:0% lot of folks don't need the extra Emi protection<01:22:23.340> so<01:22:23.640> it's<01:22:23.880> why<01:22:24.120> it's<01:22:24.300> one<01:22:24.540> of<01:22:24.659> the 01:22:24.709 --> 01:22:24.719 align:start position:0% protection so it's why it's one of the 01:22:24.719 --> 01:22:25.850 align:start position:0% protection so it's why it's one of the most<01:22:24.840> common 01:22:25.850 --> 01:22:25.860 align:start position:0% most common 01:22:25.860 --> 01:22:27.770 align:start position:0% most common now<01:22:26.400> there<01:22:26.640> are<01:22:26.760> several<01:22:27.179> specific 01:22:27.770 --> 01:22:27.780 align:start position:0% now there are several specific 01:22:27.780 --> 01:22:30.950 align:start position:0% now there are several specific implementations<01:22:28.679> of<01:22:29.040> sdp<01:22:29.580> and<01:22:29.820> UDP<01:22:30.179> and<01:22:30.840> each 01:22:30.950 --> 01:22:30.960 align:start position:0% implementations of sdp and UDP and each 01:22:30.960 --> 01:22:33.050 align:start position:0% implementations of sdp and UDP and each one<01:22:31.140> has<01:22:31.320> different<01:22:31.560> standards<01:22:32.340> uh<01:22:32.880> and 01:22:33.050 --> 01:22:33.060 align:start position:0% one has different standards uh and 01:22:33.060 --> 01:22:35.330 align:start position:0% one has different standards uh and characteristics<01:22:33.780> and<01:22:34.260> speeds<01:22:34.679> and<01:22:34.860> so<01:22:34.980> on<01:22:35.100> so 01:22:35.330 --> 01:22:35.340 align:start position:0% characteristics and speeds and so on so 01:22:35.340 --> 01:22:37.250 align:start position:0% characteristics and speeds and so on so let's<01:22:35.820> take<01:22:36.060> a<01:22:36.179> look<01:22:36.360> at<01:22:36.540> those<01:22:36.719> in<01:22:37.080> a<01:22:37.140> little 01:22:37.250 --> 01:22:37.260 align:start position:0% let's take a look at those in a little 01:22:37.260 --> 01:22:38.950 align:start position:0% let's take a look at those in a little more<01:22:37.380> depth<01:22:37.679> right<01:22:37.860> now 01:22:38.950 --> 01:22:38.960 align:start position:0% more depth right now 01:22:38.960 --> 01:22:42.470 align:start position:0% more depth right now you<01:22:39.960> may<01:22:40.080> have<01:22:40.199> heard<01:22:40.560> of<01:22:40.980> the<01:22:41.159> or<01:22:41.460> seen<01:22:42.239> the 01:22:42.470 --> 01:22:42.480 align:start position:0% you may have heard of the or seen the 01:22:42.480 --> 01:22:46.430 align:start position:0% you may have heard of the or seen the terms<01:22:42.840> CAT5<01:22:43.620> or<01:22:44.400> category<01:22:44.880> five<01:22:45.120> or<01:22:45.600> Cat6<01:22:46.080> or 01:22:46.430 --> 01:22:46.440 align:start position:0% terms CAT5 or category five or Cat6 or 01:22:46.440 --> 01:22:48.590 align:start position:0% terms CAT5 or category five or Cat6 or something<01:22:46.620> similar<01:22:47.100> to<01:22:47.280> this<01:22:47.460> before<01:22:47.640> let's 01:22:48.590 --> 01:22:48.600 align:start position:0% something similar to this before let's 01:22:48.600 --> 01:22:50.510 align:start position:0% something similar to this before let's take<01:22:48.780> a<01:22:48.900> look<01:22:48.960> at<01:22:49.080> what<01:22:49.320> these<01:22:49.560> terms<01:22:49.920> mean<01:22:50.100> and 01:22:50.510 --> 01:22:50.520 align:start position:0% take a look at what these terms mean and 01:22:50.520 --> 01:22:52.430 align:start position:0% take a look at what these terms mean and what<01:22:50.820> the<01:22:51.000> specifications<01:22:51.659> are<01:22:52.020> regarding 01:22:52.430 --> 01:22:52.440 align:start position:0% what the specifications are regarding 01:22:52.440 --> 01:22:53.689 align:start position:0% what the specifications are regarding them<01:22:52.620> because<01:22:52.920> you'll<01:22:53.159> need<01:22:53.280> to<01:22:53.400> know<01:22:53.520> that 01:22:53.689 --> 01:22:53.699 align:start position:0% them because you'll need to know that 01:22:53.699 --> 01:22:55.070 align:start position:0% them because you'll need to know that for<01:22:53.880> the<01:22:54.000> exam 01:22:55.070 --> 01:22:55.080 align:start position:0% for the exam 01:22:55.080 --> 01:22:59.630 align:start position:0% for the exam cat<01:22:55.920> simply<01:22:56.699> stands<01:22:57.179> for<01:22:57.480> category<01:22:58.679> there<01:22:59.400> are 01:22:59.630 --> 01:22:59.640 align:start position:0% cat simply stands for category there are 01:22:59.640 --> 01:23:02.750 align:start position:0% cat simply stands for category there are both<01:22:59.820> STP<01:23:00.600> and<01:23:00.900> UTP<01:23:01.560> versions<01:23:01.980> of<01:23:02.340> these 01:23:02.750 --> 01:23:02.760 align:start position:0% both STP and UTP versions of these 01:23:02.760 --> 01:23:05.630 align:start position:0% both STP and UTP versions of these category<01:23:03.300> cables<01:23:03.840> that<01:23:04.440> stand<01:23:04.679> if<01:23:05.219> you<01:23:05.340> recall 01:23:05.630 --> 01:23:05.640 align:start position:0% category cables that stand if you recall 01:23:05.640 --> 01:23:08.330 align:start position:0% category cables that stand if you recall that's<01:23:05.820> shielded<01:23:06.360> and<01:23:06.659> unshielded<01:23:07.380> and<01:23:08.040> the 01:23:08.330 --> 01:23:08.340 align:start position:0% that's shielded and unshielded and the 01:23:08.340 --> 01:23:10.610 align:start position:0% that's shielded and unshielded and the first<01:23:08.520> category<01:23:09.179> of<01:23:09.420> cable<01:23:09.719> is<01:23:10.080> as<01:23:10.380> you'd 01:23:10.610 --> 01:23:10.620 align:start position:0% first category of cable is as you'd 01:23:10.620 --> 01:23:13.490 align:start position:0% first category of cable is as you'd imagine<01:23:10.739> category<01:23:11.460> one<01:23:11.699> cable<01:23:12.060> now<01:23:12.960> we<01:23:13.380> don't 01:23:13.490 --> 01:23:13.500 align:start position:0% imagine category one cable now we don't 01:23:13.500 --> 01:23:14.810 align:start position:0% imagine category one cable now we don't really<01:23:13.679> see<01:23:13.980> this<01:23:14.159> in<01:23:14.340> the<01:23:14.460> field<01:23:14.580> anymore 01:23:14.810 --> 01:23:14.820 align:start position:0% really see this in the field anymore 01:23:14.820 --> 01:23:18.050 align:start position:0% really see this in the field anymore it's<01:23:15.179> been<01:23:15.560> superseded<01:23:16.560> by<01:23:17.100> the<01:23:17.580> following 01:23:18.050 --> 01:23:18.060 align:start position:0% it's been superseded by the following 01:23:18.060 --> 01:23:19.970 align:start position:0% it's been superseded by the following categories<01:23:18.600> cabling<01:23:19.080> and<01:23:19.320> but<01:23:19.560> its<01:23:19.860> original 01:23:19.970 --> 01:23:19.980 align:start position:0% categories cabling and but its original 01:23:19.980 --> 01:23:22.370 align:start position:0% categories cabling and but its original purpose<01:23:20.520> was<01:23:20.699> for<01:23:20.940> voice<01:23:21.179> I<01:23:22.020> wouldn't<01:23:22.140> worry 01:23:22.370 --> 01:23:22.380 align:start position:0% purpose was for voice I wouldn't worry 01:23:22.380 --> 01:23:24.169 align:start position:0% purpose was for voice I wouldn't worry about<01:23:22.560> memorizing<01:23:23.280> that<01:23:23.460> one 01:23:24.169 --> 01:23:24.179 align:start position:0% about memorizing that one 01:23:24.179 --> 01:23:27.830 align:start position:0% about memorizing that one type<01:23:25.020> 2<01:23:25.440> or<01:23:25.739> Category<01:23:26.219> 2<01:23:26.400> is<01:23:27.179> rarely<01:23:27.540> used 01:23:27.830 --> 01:23:27.840 align:start position:0% type 2 or Category 2 is rarely used 01:23:27.840 --> 01:23:31.850 align:start position:0% type 2 or Category 2 is rarely used today<01:23:28.100> uh<01:23:29.100> only<01:23:29.699> in<01:23:30.600> something<01:23:30.840> called<01:23:31.199> token 01:23:31.850 --> 01:23:31.860 align:start position:0% today uh only in something called token 01:23:31.860 --> 01:23:33.290 align:start position:0% today uh only in something called token based<01:23:32.219> networks<01:23:32.520> which<01:23:32.699> we'll<01:23:32.940> talk<01:23:33.120> more 01:23:33.290 --> 01:23:33.300 align:start position:0% based networks which we'll talk more 01:23:33.300 --> 01:23:35.209 align:start position:0% based networks which we'll talk more about<01:23:33.480> in<01:23:33.780> the<01:23:33.900> future<01:23:34.020> but<01:23:34.620> again<01:23:34.739> it's<01:23:34.980> not 01:23:35.209 --> 01:23:35.219 align:start position:0% about in the future but again it's not 01:23:35.219 --> 01:23:36.649 align:start position:0% about in the future but again it's not very<01:23:35.400> common<01:23:35.640> you're<01:23:35.940> not<01:23:36.179> really<01:23:36.300> going<01:23:36.540> to 01:23:36.649 --> 01:23:36.659 align:start position:0% very common you're not really going to 01:23:36.659 --> 01:23:39.110 align:start position:0% very common you're not really going to see<01:23:36.840> it<01:23:37.080> uh<01:23:37.620> very<01:23:38.159> much<01:23:38.280> at<01:23:38.460> all 01:23:39.110 --> 01:23:39.120 align:start position:0% see it uh very much at all 01:23:39.120 --> 01:23:42.649 align:start position:0% see it uh very much at all now<01:23:39.600> Category<01:23:40.080> 3<01:23:40.380> or<01:23:40.920> ethernet<01:23:41.640> which<01:23:42.360> is 01:23:42.649 --> 01:23:42.659 align:start position:0% now Category 3 or ethernet which is 01:23:42.659 --> 01:23:44.030 align:start position:0% now Category 3 or ethernet which is different<01:23:42.780> from<01:23:43.080> the<01:23:43.260> current<01:23:43.320> ethernet<01:23:43.800> but 01:23:44.030 --> 01:23:44.040 align:start position:0% different from the current ethernet but 01:23:44.040 --> 01:23:46.010 align:start position:0% different from the current ethernet but this<01:23:44.159> was<01:23:44.340> the<01:23:44.640> first<01:23:44.820> category<01:23:45.420> established 01:23:46.010 --> 01:23:46.020 align:start position:0% this was the first category established 01:23:46.020 --> 01:23:50.450 align:start position:0% this was the first category established by<01:23:46.860> an<01:23:47.159> organization<01:23:47.760> called<01:23:48.360> Tia<01:23:49.260> eia<01:23:49.860> this 01:23:50.450 --> 01:23:50.460 align:start position:0% by an organization called Tia eia this 01:23:50.460 --> 01:23:52.370 align:start position:0% by an organization called Tia eia this is<01:23:50.580> the<01:23:50.820> Telecommunications<01:23:51.659> industry 01:23:52.370 --> 01:23:52.380 align:start position:0% is the Telecommunications industry 01:23:52.380 --> 01:23:54.110 align:start position:0% is the Telecommunications industry Association<01:23:52.860> Electronics<01:23:53.699> Industries 01:23:54.110 --> 01:23:54.120 align:start position:0% Association Electronics Industries 01:23:54.120 --> 01:23:56.149 align:start position:0% Association Electronics Industries Alliance<01:23:54.840> don't<01:23:55.260> worry<01:23:55.440> about<01:23:55.560> memorizing 01:23:56.149 --> 01:23:56.159 align:start position:0% Alliance don't worry about memorizing 01:23:56.159 --> 01:23:58.970 align:start position:0% Alliance don't worry about memorizing that<01:23:56.340> but<01:23:57.060> in<01:23:57.420> today's<01:23:57.600> networks<01:23:58.440> category 01:23:58.970 --> 01:23:58.980 align:start position:0% that but in today's networks category 01:23:58.980 --> 01:24:01.790 align:start position:0% that but in today's networks category three<01:23:59.159> or<01:23:59.460> cat<01:23:59.699> 3<01:24:00.000> is<01:24:00.719> used<01:24:00.960> almost<01:24:01.260> completely 01:24:01.790 --> 01:24:01.800 align:start position:0% three or cat 3 is used almost completely 01:24:01.800 --> 01:24:04.490 align:start position:0% three or cat 3 is used almost completely for<01:24:02.100> voice<01:24:02.400> Transmissions<01:24:03.179> because<01:24:03.780> it<01:24:04.080> has<01:24:04.260> a 01:24:04.490 --> 01:24:04.500 align:start position:0% for voice Transmissions because it has a 01:24:04.500 --> 01:24:07.010 align:start position:0% for voice Transmissions because it has a limited<01:24:04.800> transfer<01:24:05.280> speed<01:24:05.520> of<01:24:05.940> 10<01:24:06.239> megabits 01:24:07.010 --> 01:24:07.020 align:start position:0% limited transfer speed of 10 megabits 01:24:07.020 --> 01:24:09.830 align:start position:0% limited transfer speed of 10 megabits per<01:24:07.260> second<01:24:07.500> and<01:24:08.219> a<01:24:08.340> 16<01:24:08.580> megahertz<01:24:09.120> bandwidth 01:24:09.830 --> 01:24:09.840 align:start position:0% per second and a 16 megahertz bandwidth 01:24:09.840 --> 01:24:11.750 align:start position:0% per second and a 16 megahertz bandwidth so<01:24:10.440> a<01:24:10.800> lot<01:24:10.920> of 01:24:11.750 --> 01:24:11.760 align:start position:0% so a lot of 01:24:11.760 --> 01:24:14.990 align:start position:0% so a lot of telephone<01:24:12.420> K<01:24:13.020> old<01:24:13.440> telephone<01:24:14.219> cableing<01:24:14.880> is 01:24:14.990 --> 01:24:15.000 align:start position:0% telephone K old telephone cableing is 01:24:15.000 --> 01:24:19.970 align:start position:0% telephone K old telephone cableing is cat<01:24:15.179> 3.<01:24:16.080> cat4<01:24:16.800> uh<01:24:17.900> just<01:24:18.900> like<01:24:19.080> cat<01:24:19.260> 2<01:24:19.500> it's<01:24:19.800> not 01:24:19.970 --> 01:24:19.980 align:start position:0% cat 3. cat4 uh just like cat 2 it's not 01:24:19.980 --> 01:24:22.070 align:start position:0% cat 3. cat4 uh just like cat 2 it's not used<01:24:20.159> anymore<01:24:20.400> not<01:24:21.000> even<01:24:21.179> worth<01:24:21.540> really 01:24:22.070 --> 01:24:22.080 align:start position:0% used anymore not even worth really 01:24:22.080 --> 01:24:24.709 align:start position:0% used anymore not even worth really spending<01:24:22.620> time<01:24:22.739> in<01:24:22.980> now<01:24:23.760> when<01:24:23.940> we<01:24:24.060> get<01:24:24.179> to<01:24:24.300> CAT5 01:24:24.709 --> 01:24:24.719 align:start position:0% spending time in now when we get to CAT5 01:24:24.719 --> 01:24:26.630 align:start position:0% spending time in now when we get to CAT5 this<01:24:25.199> is<01:24:25.380> sort<01:24:25.560> of<01:24:25.620> where<01:24:26.100> we<01:24:26.219> start<01:24:26.400> really 01:24:26.630 --> 01:24:26.640 align:start position:0% this is sort of where we start really 01:24:26.640 --> 01:24:29.149 align:start position:0% this is sort of where we start really getting<01:24:26.880> to<01:24:27.300> Modern<01:24:27.600> Day<01:24:27.900> stuff<01:24:28.260> Cat<01:24:28.920> 5 01:24:29.149 --> 01:24:29.159 align:start position:0% getting to Modern Day stuff Cat 5 01:24:29.159 --> 01:24:30.890 align:start position:0% getting to Modern Day stuff Cat 5 cabling<01:24:29.699> which<01:24:30.000> is<01:24:30.120> also<01:24:30.300> called<01:24:30.480> Fast 01:24:30.890 --> 01:24:30.900 align:start position:0% cabling which is also called Fast 01:24:30.900 --> 01:24:33.649 align:start position:0% cabling which is also called Fast ethernet<01:24:31.560> provides<01:24:32.400> performance<01:24:32.880> of<01:24:33.120> signals 01:24:33.649 --> 01:24:33.659 align:start position:0% ethernet provides performance of signals 01:24:33.659 --> 01:24:37.610 align:start position:0% ethernet provides performance of signals up<01:24:34.080> to<01:24:34.260> around<01:24:34.560> 100<01:24:35.219> megabits<01:24:36.060> per<01:24:36.239> second 01:24:37.610 --> 01:24:37.620 align:start position:0% up to around 100 megabits per second 01:24:37.620 --> 01:24:39.709 align:start position:0% up to around 100 megabits per second important<01:24:38.159> that<01:24:38.340> you<01:24:38.520> know<01:24:38.640> this<01:24:38.820> the<01:24:39.300> maximum 01:24:39.709 --> 01:24:39.719 align:start position:0% important that you know this the maximum 01:24:39.719 --> 01:24:43.189 align:start position:0% important that you know this the maximum distance<01:24:39.960> for<01:24:40.320> CAT5<01:24:40.739> cabling<01:24:41.280> is<01:24:42.060> 100<01:24:42.480> meters 01:24:43.189 --> 01:24:43.199 align:start position:0% distance for CAT5 cabling is 100 meters 01:24:43.199 --> 01:24:45.709 align:start position:0% distance for CAT5 cabling is 100 meters or<01:24:43.739> 328<01:24:44.640> feet 01:24:45.709 --> 01:24:45.719 align:start position:0% or 328 feet 01:24:45.719 --> 01:24:49.430 align:start position:0% or 328 feet now<01:24:46.260> CAT5<01:24:46.800> e<01:24:47.580> is<01:24:48.239> the<01:24:48.480> specification<01:24:49.080> that 01:24:49.430 --> 01:24:49.440 align:start position:0% now CAT5 e is the specification that 01:24:49.440 --> 01:24:52.130 align:start position:0% now CAT5 e is the specification that superseded<01:24:50.040> CAT5<01:24:50.699> and<01:24:51.360> it<01:24:51.480> addressed<01:24:51.900> some<01:24:52.020> of 01:24:52.130 --> 01:24:52.140 align:start position:0% superseded CAT5 and it addressed some of 01:24:52.140 --> 01:24:54.830 align:start position:0% superseded CAT5 and it addressed some of the<01:24:52.260> weaknesses<01:24:52.800> including<01:24:53.520> uh<01:24:54.420> crosstalk 01:24:54.830 --> 01:24:54.840 align:start position:0% the weaknesses including uh crosstalk 01:24:54.840 --> 01:24:57.890 align:start position:0% the weaknesses including uh crosstalk prevent<01:24:55.620> prevention<01:24:56.540> uh<01:24:57.540> and<01:24:57.780> other 01:24:57.890 --> 01:24:57.900 align:start position:0% prevent prevention uh and other 01:24:57.900 --> 01:25:01.669 align:start position:0% prevent prevention uh and other specifications<01:24:58.560> in<01:24:59.040> the<01:24:59.219> like<01:24:59.360> like<01:25:00.360> CAT5<01:25:01.080> the 01:25:01.669 --> 01:25:01.679 align:start position:0% specifications in the like like CAT5 the 01:25:01.679 --> 01:25:04.669 align:start position:0% specifications in the like like CAT5 the maximum<01:25:02.100> cable<01:25:02.400> length<01:25:02.820> of<01:25:03.060> Cat5e<01:25:03.900> is<01:25:04.380> also 01:25:04.669 --> 01:25:04.679 align:start position:0% maximum cable length of Cat5e is also 01:25:04.679 --> 01:25:07.610 align:start position:0% maximum cable length of Cat5e is also 100<01:25:04.980> meters<01:25:05.640> the<01:25:06.360> bandwidth<01:25:06.960> is<01:25:07.199> also<01:25:07.440> the 01:25:07.610 --> 01:25:07.620 align:start position:0% 100 meters the bandwidth is also the 01:25:07.620 --> 01:25:10.850 align:start position:0% 100 meters the bandwidth is also the same<01:25:07.800> at<01:25:08.040> 100<01:25:08.340> megahertz<01:25:09.060> but<01:25:09.960> it's<01:25:10.320> said<01:25:10.560> that 01:25:10.850 --> 01:25:10.860 align:start position:0% same at 100 megahertz but it's said that 01:25:10.860 --> 01:25:14.090 align:start position:0% same at 100 megahertz but it's said that data<01:25:11.460> data<01:25:12.060> rates<01:25:12.239> can<01:25:12.480> get<01:25:12.659> up<01:25:12.840> to<01:25:13.020> about<01:25:13.260> 350 01:25:14.090 --> 01:25:14.100 align:start position:0% data data rates can get up to about 350 01:25:14.100 --> 01:25:16.910 align:start position:0% data data rates can get up to about 350 megabits<01:25:14.820> per<01:25:15.060> second<01:25:15.560> uh<01:25:16.560> although 01:25:16.910 --> 01:25:16.920 align:start position:0% megabits per second uh although 01:25:16.920 --> 01:25:18.649 align:start position:0% megabits per second uh although sometimes<01:25:17.280> an<01:25:17.520> application<01:25:17.940> that's<01:25:18.360> not 01:25:18.649 --> 01:25:18.659 align:start position:0% sometimes an application that's not 01:25:18.659 --> 01:25:20.709 align:start position:0% sometimes an application that's not exactly<01:25:19.020> what<01:25:19.260> we<01:25:19.440> see 01:25:20.709 --> 01:25:20.719 align:start position:0% exactly what we see 01:25:20.719 --> 01:25:25.430 align:start position:0% exactly what we see Cat6<01:25:21.719> is<01:25:22.440> a<01:25:22.800> standard<01:25:23.159> uh<01:25:24.000> that<01:25:24.420> increased<01:25:25.140> the 01:25:25.430 --> 01:25:25.440 align:start position:0% Cat6 is a standard uh that increased the 01:25:25.440 --> 01:25:28.430 align:start position:0% Cat6 is a standard uh that increased the transmission<01:25:25.679> speeds<01:25:26.580> quite<01:25:27.120> a<01:25:27.239> bit<01:25:27.440> it's 01:25:28.430 --> 01:25:28.440 align:start position:0% transmission speeds quite a bit it's 01:25:28.440 --> 01:25:30.530 align:start position:0% transmission speeds quite a bit it's what's<01:25:28.739> called<01:25:29.040> gigabit<01:25:29.699> Ethernet<01:25:30.300> because 01:25:30.530 --> 01:25:30.540 align:start position:0% what's called gigabit Ethernet because 01:25:30.540 --> 01:25:32.750 align:start position:0% what's called gigabit Ethernet because it's<01:25:30.840> rated<01:25:31.199> for<01:25:31.440> data<01:25:31.800> rates<01:25:32.040> of<01:25:32.159> about<01:25:32.340> one 01:25:32.750 --> 01:25:32.760 align:start position:0% it's rated for data rates of about one 01:25:32.760 --> 01:25:35.450 align:start position:0% it's rated for data rates of about one gigabit<01:25:33.360> per<01:25:33.900> second<01:25:34.140> so<01:25:34.739> we're<01:25:34.920> going<01:25:35.100> from 01:25:35.450 --> 01:25:35.460 align:start position:0% gigabit per second so we're going from 01:25:35.460 --> 01:25:40.630 align:start position:0% gigabit per second so we're going from again<01:25:35.820> with<01:25:36.120> 10<01:25:36.440> cat<01:25:37.440> 3<01:25:37.739> from<01:25:38.159> 10<01:25:38.400> Cat<01:25:39.300> 5<01:25:39.540> 100 01:25:40.630 --> 01:25:40.640 align:start position:0% again with 10 cat 3 from 10 Cat 5 100 01:25:40.640 --> 01:25:43.910 align:start position:0% again with 10 cat 3 from 10 Cat 5 100 Cat5e<01:25:41.640> 350<01:25:42.300> theoretical<01:25:43.020> and<01:25:43.380> now<01:25:43.560> we're<01:25:43.739> at 01:25:43.910 --> 01:25:43.920 align:start position:0% Cat5e 350 theoretical and now we're at 01:25:43.920 --> 01:25:46.070 align:start position:0% Cat5e 350 theoretical and now we're at 1000<01:25:44.520> megabits<01:25:45.000> per<01:25:45.120> second<01:25:45.239> or<01:25:45.480> one<01:25:45.719> gigabit 01:25:46.070 --> 01:25:46.080 align:start position:0% 1000 megabits per second or one gigabit 01:25:46.080 --> 01:25:47.030 align:start position:0% 1000 megabits per second or one gigabit per<01:25:46.260> second 01:25:47.030 --> 01:25:47.040 align:start position:0% per second 01:25:47.040 --> 01:25:50.090 align:start position:0% per second the<01:25:47.580> signal<01:25:47.880> limb<01:25:48.179> rate<01:25:48.300> also<01:25:48.719> of<01:25:48.960> CAT5<01:25:49.440> Cat6 01:25:50.090 --> 01:25:50.100 align:start position:0% the signal limb rate also of CAT5 Cat6 01:25:50.100 --> 01:25:53.930 align:start position:0% the signal limb rate also of CAT5 Cat6 rather<01:25:50.520> is<01:25:50.820> tested<01:25:51.360> at<01:25:51.840> 250<01:25:52.500> megahertz<01:25:53.100> uh<01:25:53.760> but 01:25:53.930 --> 01:25:53.940 align:start position:0% rather is tested at 250 megahertz uh but 01:25:53.940 --> 01:25:56.990 align:start position:0% rather is tested at 250 megahertz uh but it's<01:25:54.120> guaranteed<01:25:54.719> at<01:25:54.960> a<01:25:55.380> 200. 01:25:56.990 --> 01:25:57.000 align:start position:0% it's guaranteed at a 200. 01:25:57.000 --> 01:25:58.729 align:start position:0% it's guaranteed at a 200. there<01:25:57.480> was<01:25:57.600> also<01:25:57.780> another<01:25:58.020> one<01:25:58.260> after<01:25:58.500> this 01:25:58.729 --> 01:25:58.739 align:start position:0% there was also another one after this 01:25:58.739 --> 01:26:02.090 align:start position:0% there was also another one after this called<01:25:59.300> cat6a<01:26:00.320> which<01:26:01.320> was<01:26:01.440> also<01:26:01.679> known<01:26:01.860> as 01:26:02.090 --> 01:26:02.100 align:start position:0% called cat6a which was also known as 01:26:02.100 --> 01:26:05.090 align:start position:0% called cat6a which was also known as augmented<01:26:02.880> category<01:26:03.360> six<01:26:03.600> and<01:26:04.139> it<01:26:04.500> had<01:26:04.920> a 01:26:05.090 --> 01:26:05.100 align:start position:0% augmented category six and it had a 01:26:05.100 --> 01:26:06.950 align:start position:0% augmented category six and it had a rating<01:26:05.340> of<01:26:05.520> a<01:26:05.639> little<01:26:05.760> bit<01:26:05.880> more<01:26:06.060> than<01:26:06.239> a<01:26:06.480> one 01:26:06.950 --> 01:26:06.960 align:start position:0% rating of a little bit more than a one 01:26:06.960 --> 01:26:09.830 align:start position:0% rating of a little bit more than a one gigabit<01:26:07.440> but<01:26:08.280> uh<01:26:08.880> many<01:26:09.179> people<01:26:09.480> said<01:26:09.719> that 01:26:09.830 --> 01:26:09.840 align:start position:0% gigabit but uh many people said that 01:26:09.840 --> 01:26:11.870 align:start position:0% gigabit but uh many people said that they<01:26:09.960> can<01:26:10.080> actually<01:26:10.260> get<01:26:10.440> to<01:26:10.560> 10<01:26:10.800> gigabits<01:26:11.400> and 01:26:11.870 --> 01:26:11.880 align:start position:0% they can actually get to 10 gigabits and 01:26:11.880 --> 01:26:14.570 align:start position:0% they can actually get to 10 gigabits and uh<01:26:12.480> uh<01:26:12.840> it's<01:26:13.260> megahertz<01:26:13.800> or<01:26:13.980> frequency<01:26:14.280> was 01:26:14.570 --> 01:26:14.580 align:start position:0% uh uh it's megahertz or frequency was 01:26:14.580 --> 01:26:16.430 align:start position:0% uh uh it's megahertz or frequency was also<01:26:14.940> Higher<01:26:15.360> by<01:26:15.659> the<01:26:15.780> way<01:26:15.840> I<01:26:16.139> wouldn't<01:26:16.199> worry 01:26:16.430 --> 01:26:16.440 align:start position:0% also Higher by the way I wouldn't worry 01:26:16.440 --> 01:26:17.810 align:start position:0% also Higher by the way I wouldn't worry about<01:26:16.620> any<01:26:16.800> of<01:26:16.980> the<01:26:17.040> frequencies<01:26:17.400> I'm<01:26:17.639> just 01:26:17.810 --> 01:26:17.820 align:start position:0% about any of the frequencies I'm just 01:26:17.820 --> 01:26:19.430 align:start position:0% about any of the frequencies I'm just throwing<01:26:18.060> those<01:26:18.239> in<01:26:18.420> there<01:26:18.600> so<01:26:18.780> that<01:26:19.020> you<01:26:19.260> know 01:26:19.430 --> 01:26:19.440 align:start position:0% throwing those in there so that you know 01:26:19.440 --> 01:26:20.689 align:start position:0% throwing those in there so that you know them<01:26:19.620> what<01:26:20.040> you<01:26:20.159> really<01:26:20.280> want<01:26:20.400> to<01:26:20.520> worry<01:26:20.639> about 01:26:20.689 --> 01:26:20.699 align:start position:0% them what you really want to worry about 01:26:20.699 --> 01:26:22.790 align:start position:0% them what you really want to worry about is<01:26:20.940> the<01:26:21.120> data<01:26:21.480> transfer<01:26:21.960> speed 01:26:22.790 --> 01:26:22.800 align:start position:0% is the data transfer speed 01:26:22.800 --> 01:26:25.430 align:start position:0% is the data transfer speed a<01:26:23.340> cat<01:26:23.580> 7<01:26:23.880> which<01:26:24.600> is<01:26:24.719> one<01:26:24.960> of<01:26:25.080> the<01:26:25.139> newest 01:26:25.430 --> 01:26:25.440 align:start position:0% a cat 7 which is one of the newest 01:26:25.440 --> 01:26:28.070 align:start position:0% a cat 7 which is one of the newest implementations<01:26:26.100> uh<01:26:26.820> it's<01:26:27.239> not<01:26:27.420> even<01:26:27.600> fully 01:26:28.070 --> 01:26:28.080 align:start position:0% implementations uh it's not even fully 01:26:28.080 --> 01:26:31.729 align:start position:0% implementations uh it's not even fully recognized<01:26:28.620> yet<01:26:28.800> by<01:26:29.100> Tia<01:26:29.520> eia<01:26:30.179> it's 01:26:31.729 --> 01:26:31.739 align:start position:0% recognized yet by Tia eia it's 01:26:31.739 --> 01:26:34.070 align:start position:0% recognized yet by Tia eia it's um<01:26:31.800> also<01:26:32.460> gigabit<01:26:33.000> Ethernet<01:26:33.540> and<01:26:33.900> it 01:26:34.070 --> 01:26:34.080 align:start position:0% um also gigabit Ethernet and it 01:26:34.080 --> 01:26:35.930 align:start position:0% um also gigabit Ethernet and it supposedly<01:26:34.560> supports<01:26:35.040> a<01:26:35.219> signaling<01:26:35.580> rate<01:26:35.760> of 01:26:35.930 --> 01:26:35.940 align:start position:0% supposedly supports a signaling rate of 01:26:35.940 --> 01:26:38.689 align:start position:0% supposedly supports a signaling rate of one<01:26:36.239> gigahertz<01:26:36.840> and<01:26:37.500> has<01:26:37.679> a<01:26:37.860> potential<01:26:38.280> for 01:26:38.689 --> 01:26:38.699 align:start position:0% one gigahertz and has a potential for 01:26:38.699 --> 01:26:41.030 align:start position:0% one gigahertz and has a potential for over<01:26:38.940> 10<01:26:39.360> gigabits<01:26:39.900> per<01:26:40.080> second<01:26:40.320> so<01:26:40.800> you<01:26:40.920> can 01:26:41.030 --> 01:26:41.040 align:start position:0% over 10 gigabits per second so you can 01:26:41.040 --> 01:26:43.250 align:start position:0% over 10 gigabits per second so you can see<01:26:41.159> where<01:26:41.460> we're<01:26:41.699> we<01:26:42.420> want<01:26:42.600> to<01:26:42.719> go<01:26:42.840> there<01:26:43.020> but 01:26:43.250 --> 01:26:43.260 align:start position:0% see where we're we want to go there but 01:26:43.260 --> 01:26:45.229 align:start position:0% see where we're we want to go there but at<01:26:43.440> the<01:26:43.560> same<01:26:43.739> time<01:26:43.980> Wireless<01:26:44.340> technology<01:26:44.940> or 01:26:45.229 --> 01:26:45.239 align:start position:0% at the same time Wireless technology or 01:26:45.239 --> 01:26:47.570 align:start position:0% at the same time Wireless technology or unbounded<01:26:45.840> technology<01:26:46.199> has<01:26:46.860> taken<01:26:47.219> us<01:26:47.280> to<01:26:47.460> a 01:26:47.570 --> 01:26:47.580 align:start position:0% unbounded technology has taken us to a 01:26:47.580 --> 01:26:49.189 align:start position:0% unbounded technology has taken us to a point<01:26:47.699> where<01:26:47.940> we<01:26:48.120> might<01:26:48.300> not<01:26:48.480> need<01:26:48.719> to<01:26:48.960> spend 01:26:49.189 --> 01:26:49.199 align:start position:0% point where we might not need to spend 01:26:49.199 --> 01:26:51.649 align:start position:0% point where we might not need to spend as<01:26:49.320> much<01:26:49.500> time<01:26:49.800> on<01:26:50.699> some<01:26:51.060> of<01:26:51.179> the<01:26:51.239> bounded 01:26:51.649 --> 01:26:51.659 align:start position:0% as much time on some of the bounded 01:26:51.659 --> 01:26:52.550 align:start position:0% as much time on some of the bounded media 01:26:52.550 --> 01:26:52.560 align:start position:0% media 01:26:52.560 --> 01:26:55.010 align:start position:0% media so 01:26:55.010 --> 01:26:55.020 align:start position:0% so 01:26:55.020 --> 01:26:56.450 align:start position:0% so now<01:26:55.500> that<01:26:55.620> we've<01:26:55.800> seen<01:26:55.980> all<01:26:56.159> of<01:26:56.280> these 01:26:56.450 --> 01:26:56.460 align:start position:0% now that we've seen all of these 01:26:56.460 --> 01:26:57.590 align:start position:0% now that we've seen all of these individually 01:26:57.590 --> 01:26:57.600 align:start position:0% individually 01:26:57.600 --> 01:27:00.470 align:start position:0% individually let's<01:26:58.320> take<01:26:58.500> a<01:26:58.679> look<01:26:59.159> at<01:26:59.520> an<01:26:59.699> easier<01:27:00.000> breakdown 01:27:00.470 --> 01:27:00.480 align:start position:0% let's take a look at an easier breakdown 01:27:00.480 --> 01:27:03.290 align:start position:0% let's take a look at an easier breakdown of<01:27:00.719> the<01:27:00.900> specifics<01:27:01.440> of<01:27:01.560> all<01:27:01.800> of<01:27:01.860> these 01:27:03.290 --> 01:27:03.300 align:start position:0% of the specifics of all of these 01:27:03.300 --> 01:27:05.990 align:start position:0% of the specifics of all of these so<01:27:03.840> as<01:27:04.260> we<01:27:04.440> can<01:27:04.620> see<01:27:04.739> here<01:27:05.100> each<01:27:05.580> of<01:27:05.699> these<01:27:05.820> cat 01:27:05.990 --> 01:27:06.000 align:start position:0% so as we can see here each of these cat 01:27:06.000 --> 01:27:08.629 align:start position:0% so as we can see here each of these cat standards<01:27:06.540> has<01:27:06.780> a<01:27:07.080> maximum<01:27:07.500> cable<01:27:07.800> length<01:27:08.219> of 01:27:08.629 --> 01:27:08.639 align:start position:0% standards has a maximum cable length of 01:27:08.639 --> 01:27:11.270 align:start position:0% standards has a maximum cable length of 100<01:27:08.820> meters<01:27:09.420> for<01:27:09.719> standard<01:27:10.080> use<01:27:10.320> and<01:27:11.100> the 01:27:11.270 --> 01:27:11.280 align:start position:0% 100 meters for standard use and the 01:27:11.280 --> 01:27:13.370 align:start position:0% 100 meters for standard use and the frequencies<01:27:11.760> and<01:27:12.060> maximum<01:27:12.420> data<01:27:12.780> ranges<01:27:13.139> go 01:27:13.370 --> 01:27:13.380 align:start position:0% frequencies and maximum data ranges go 01:27:13.380 --> 01:27:16.129 align:start position:0% frequencies and maximum data ranges go up<01:27:13.560> with<01:27:14.100> each<01:27:14.280> of<01:27:14.400> the<01:27:14.520> standards<01:27:14.940> as<01:27:15.060> well<01:27:15.239> in 01:27:16.129 --> 01:27:16.139 align:start position:0% up with each of the standards as well in 01:27:16.139 --> 01:27:17.629 align:start position:0% up with each of the standards as well in most<01:27:16.260> cases<01:27:16.620> when<01:27:16.860> you're<01:27:16.980> looking<01:27:17.159> at<01:27:17.460> the 01:27:17.629 --> 01:27:17.639 align:start position:0% most cases when you're looking at the 01:27:17.639 --> 01:27:20.930 align:start position:0% most cases when you're looking at the physical<01:27:17.880> cable<01:27:18.620> the<01:27:19.620> exact<01:27:20.100> specification 01:27:20.930 --> 01:27:20.940 align:start position:0% physical cable the exact specification 01:27:20.940 --> 01:27:23.709 align:start position:0% physical cable the exact specification is<01:27:21.540> typically<01:27:22.020> printed<01:27:22.560> on<01:27:22.800> the<01:27:22.920> cable<01:27:23.159> itself 01:27:23.709 --> 01:27:23.719 align:start position:0% is typically printed on the cable itself 01:27:23.719 --> 01:27:26.390 align:start position:0% is typically printed on the cable itself helping<01:27:24.719> technicians<01:27:25.320> ensure<01:27:25.739> that<01:27:25.980> the<01:27:26.159> same 01:27:26.390 --> 01:27:26.400 align:start position:0% helping technicians ensure that the same 01:27:26.400 --> 01:27:28.370 align:start position:0% helping technicians ensure that the same standard<01:27:27.000> is<01:27:27.480> going<01:27:27.659> to<01:27:27.780> be<01:27:27.840> used<01:27:28.020> throughout 01:27:28.370 --> 01:27:28.380 align:start position:0% standard is going to be used throughout 01:27:28.380 --> 01:27:29.689 align:start position:0% standard is going to be used throughout the<01:27:28.560> organization 01:27:29.689 --> 01:27:29.699 align:start position:0% the organization 01:27:29.699 --> 01:27:33.470 align:start position:0% the organization now<01:27:30.239> while<01:27:30.540> Cat<01:27:30.900> 5<01:27:31.260> through<01:27:31.980> 7<01:27:32.460> cables<01:27:33.120> are 01:27:33.470 --> 01:27:33.480 align:start position:0% now while Cat 5 through 7 cables are 01:27:33.480 --> 01:27:36.169 align:start position:0% now while Cat 5 through 7 cables are very<01:27:33.780> similar<01:27:34.199> because<01:27:35.040> they<01:27:35.340> all<01:27:35.520> use<01:27:35.760> the 01:27:36.169 --> 01:27:36.179 align:start position:0% very similar because they all use the 01:27:36.179 --> 01:27:38.570 align:start position:0% very similar because they all use the RJ45<01:27:36.960> connector<01:27:37.560> which<01:27:37.739> is<01:27:37.800> the<01:27:38.040> connector<01:27:38.400> at 01:27:38.570 --> 01:27:38.580 align:start position:0% RJ45 connector which is the connector at 01:27:38.580 --> 01:27:39.830 align:start position:0% RJ45 connector which is the connector at the<01:27:38.699> end<01:27:38.760> that<01:27:39.060> plugs<01:27:39.300> into<01:27:39.420> your<01:27:39.659> network 01:27:39.830 --> 01:27:39.840 align:start position:0% the end that plugs into your network 01:27:39.840 --> 01:27:43.129 align:start position:0% the end that plugs into your network card<01:27:40.199> or<01:27:40.739> into<01:27:40.920> a<01:27:41.219> port<01:27:41.480> uh<01:27:42.480> should<01:27:42.840> a 01:27:43.129 --> 01:27:43.139 align:start position:0% card or into a port uh should a 01:27:43.139 --> 01:27:46.669 align:start position:0% card or into a port uh should a technician<01:27:44.040> install<01:27:44.280> a<01:27:44.580> Cat5e<01:27:45.360> cable<01:27:45.780> and<01:27:46.440> a 01:27:46.669 --> 01:27:46.679 align:start position:0% technician install a Cat5e cable and a 01:27:46.679 --> 01:27:49.430 align:start position:0% technician install a Cat5e cable and a cat<01:27:46.800> 6<01:27:47.219> or<01:27:47.580> higher<01:27:48.000> Network<01:27:48.179> the<01:27:48.840> Network's 01:27:49.430 --> 01:27:49.440 align:start position:0% cat 6 or higher Network the Network's 01:27:49.440 --> 01:27:51.169 align:start position:0% cat 6 or higher Network the Network's still<01:27:49.920> probably<01:27:50.400> going<01:27:50.699> to<01:27:50.880> function 01:27:51.169 --> 01:27:51.179 align:start position:0% still probably going to function 01:27:51.179 --> 01:27:53.330 align:start position:0% still probably going to function correctly<01:27:51.719> but<01:27:52.320> the<01:27:52.560> Network's<01:27:52.920> only<01:27:53.100> going 01:27:53.330 --> 01:27:53.340 align:start position:0% correctly but the Network's only going 01:27:53.340 --> 01:27:55.070 align:start position:0% correctly but the Network's only going to<01:27:53.580> operate 01:27:55.070 --> 01:27:55.080 align:start position:0% to operate 01:27:55.080 --> 01:27:58.610 align:start position:0% to operate at<01:27:55.800> the<01:27:56.040> uh<01:27:56.480> maximum<01:27:57.480> speed<01:27:57.719> of<01:27:58.139> the<01:27:58.320> lowest 01:27:58.610 --> 01:27:58.620 align:start position:0% at the uh maximum speed of the lowest 01:27:58.620 --> 01:28:00.530 align:start position:0% at the uh maximum speed of the lowest standard<01:27:58.980> so<01:27:59.340> if<01:27:59.760> everyone<01:28:00.000> else<01:28:00.239> in<01:28:00.420> the 01:28:00.530 --> 01:28:00.540 align:start position:0% standard so if everyone else in the 01:28:00.540 --> 01:28:03.709 align:start position:0% standard so if everyone else in the network<01:28:00.719> has<01:28:01.139> Cat6<01:28:01.739> and<01:28:02.340> you<01:28:02.520> install<01:28:02.699> a<01:28:02.940> Cat5e 01:28:03.709 --> 01:28:03.719 align:start position:0% network has Cat6 and you install a Cat5e 01:28:03.719 --> 01:28:05.330 align:start position:0% network has Cat6 and you install a Cat5e cable<01:28:04.020> then<01:28:04.320> you're<01:28:04.500> limited<01:28:04.860> now<01:28:04.980> to<01:28:05.219> the 01:28:05.330 --> 01:28:05.340 align:start position:0% cable then you're limited now to the 01:28:05.340 --> 01:28:07.070 align:start position:0% cable then you're limited now to the Cat5e 01:28:07.070 --> 01:28:07.080 align:start position:0% Cat5e 01:28:07.080 --> 01:28:08.870 align:start position:0% Cat5e um<01:28:07.199> specifications 01:28:08.870 --> 01:28:08.880 align:start position:0% um specifications 01:28:08.880 --> 01:28:11.209 align:start position:0% um specifications now<01:28:09.360> here's<01:28:09.659> a<01:28:09.780> picture<01:28:09.960> of<01:28:10.260> an<01:28:10.500> RJ45 01:28:11.209 --> 01:28:11.219 align:start position:0% now here's a picture of an RJ45 01:28:11.219 --> 01:28:13.370 align:start position:0% now here's a picture of an RJ45 connector<01:28:11.880> I<01:28:12.300> want<01:28:12.420> you<01:28:12.540> to<01:28:12.659> note<01:28:12.780> there<01:28:13.199> are 01:28:13.370 --> 01:28:13.380 align:start position:0% connector I want you to note there are 01:28:13.380 --> 01:28:16.610 align:start position:0% connector I want you to note there are eight<01:28:13.560> pins<01:28:13.920> which<01:28:14.280> means<01:28:14.580> there<01:28:15.000> are<01:28:15.300> uh<01:28:16.139> four 01:28:16.610 --> 01:28:16.620 align:start position:0% eight pins which means there are uh four 01:28:16.620 --> 01:28:19.129 align:start position:0% eight pins which means there are uh four Twisted<01:28:17.159> Pairs<01:28:17.580> and<01:28:18.360> next<01:28:18.540> here's<01:28:18.900> a<01:28:19.020> picture 01:28:19.129 --> 01:28:19.139 align:start position:0% Twisted Pairs and next here's a picture 01:28:19.139 --> 01:28:21.830 align:start position:0% Twisted Pairs and next here's a picture of<01:28:19.320> an<01:28:19.440> rj11<01:28:20.100> which<01:28:20.460> is<01:28:20.580> used<01:28:20.760> for<01:28:21.000> phone<01:28:21.540> lines 01:28:21.830 --> 01:28:21.840 align:start position:0% of an rj11 which is used for phone lines 01:28:21.840 --> 01:28:24.410 align:start position:0% of an rj11 which is used for phone lines and<01:28:22.440> notice<01:28:22.679> that<01:28:22.860> this<01:28:23.040> one<01:28:23.219> has<01:28:23.639> four<01:28:24.060> pins 01:28:24.410 --> 01:28:24.420 align:start position:0% and notice that this one has four pins 01:28:24.420 --> 01:28:26.990 align:start position:0% and notice that this one has four pins so<01:28:25.020> that's<01:28:25.139> two<01:28:25.440> Twisted<01:28:25.920> Pairs<01:28:26.340> and<01:28:26.760> it's 01:28:26.990 --> 01:28:27.000 align:start position:0% so that's two Twisted Pairs and it's 01:28:27.000 --> 01:28:29.390 align:start position:0% so that's two Twisted Pairs and it's also<01:28:27.360> much<01:28:27.659> smaller<01:28:28.080> than<01:28:28.260> RJ45<01:28:28.980> this<01:28:29.280> is 01:28:29.390 --> 01:28:29.400 align:start position:0% also much smaller than RJ45 this is 01:28:29.400 --> 01:28:32.330 align:start position:0% also much smaller than RJ45 this is what's<01:28:29.520> used<01:28:29.760> in<01:28:29.940> what's<01:28:30.120> called<01:28:30.420> pots<01:28:31.679> plain 01:28:32.330 --> 01:28:32.340 align:start position:0% what's used in what's called pots plain 01:28:32.340 --> 01:28:36.470 align:start position:0% what's used in what's called pots plain old<01:28:32.580> telephone<01:28:33.199> system<01:28:34.199> or<01:28:34.980> pstn<01:28:35.699> the<01:28:36.300> public 01:28:36.470 --> 01:28:36.480 align:start position:0% old telephone system or pstn the public 01:28:36.480 --> 01:28:39.470 align:start position:0% old telephone system or pstn the public switched<01:28:37.080> telephone<01:28:37.440> Network 01:28:39.470 --> 01:28:39.480 align:start position:0% switched telephone Network 01:28:39.480 --> 01:28:42.890 align:start position:0% switched telephone Network all<01:28:39.960> right<01:28:40.139> now<01:28:40.560> moving<01:28:40.920> on<01:28:41.040> uh<01:28:41.460> past<01:28:41.760> cats<01:28:42.360> uh 01:28:42.890 --> 01:28:42.900 align:start position:0% all right now moving on uh past cats uh 01:28:42.900 --> 01:28:45.050 align:start position:0% all right now moving on uh past cats uh and<01:28:43.139> and<01:28:43.380> twisted<01:28:44.100> pair<01:28:44.280> let's<01:28:44.760> talk<01:28:44.940> about 01:28:45.050 --> 01:28:45.060 align:start position:0% and and twisted pair let's talk about 01:28:45.060 --> 01:28:48.770 align:start position:0% and and twisted pair let's talk about coaxial<01:28:45.840> cabling<01:28:46.280> uh<01:28:47.280> it<01:28:47.880> gets<01:28:48.120> its<01:28:48.420> name<01:28:48.540> by 01:28:48.770 --> 01:28:48.780 align:start position:0% coaxial cabling uh it gets its name by 01:28:48.780 --> 01:28:51.110 align:start position:0% coaxial cabling uh it gets its name by the<01:28:48.900> way<01:28:49.020> from<01:28:49.560> uh<01:28:50.100> this<01:28:50.400> is<01:28:50.520> sort<01:28:50.699> of<01:28:50.820> a<01:28:50.940> fun 01:28:51.110 --> 01:28:51.120 align:start position:0% the way from uh this is sort of a fun 01:28:51.120 --> 01:28:54.649 align:start position:0% the way from uh this is sort of a fun fact<01:28:51.360> common<01:28:52.260> geometric<01:28:53.159> access<01:28:53.580> or<01:28:54.300> common 01:28:54.649 --> 01:28:54.659 align:start position:0% fact common geometric access or common 01:28:54.659 --> 01:28:57.110 align:start position:0% fact common geometric access or common core<01:28:55.139> because<01:28:55.860> the<01:28:56.280> shielding<01:28:56.699> and<01:28:56.940> the 01:28:57.110 --> 01:28:57.120 align:start position:0% core because the shielding and the 01:28:57.120 --> 01:28:59.990 align:start position:0% core because the shielding and the conductor<01:28:57.480> share<01:28:58.320> the<01:28:58.560> same<01:28:58.739> Center 01:28:59.990 --> 01:29:00.000 align:start position:0% conductor share the same Center 01:29:00.000 --> 01:29:03.410 align:start position:0% conductor share the same Center or<01:29:00.719> axis<01:29:01.260> as<01:29:01.679> the<01:29:01.920> name<01:29:02.100> implies<01:29:02.820> in<01:29:03.179> common 01:29:03.410 --> 01:29:03.420 align:start position:0% or axis as the name implies in common 01:29:03.420 --> 01:29:06.590 align:start position:0% or axis as the name implies in common geometric<01:29:04.199> access<01:29:04.520> or<01:29:05.520> axis 01:29:06.590 --> 01:29:06.600 align:start position:0% geometric access or axis 01:29:06.600 --> 01:29:09.709 align:start position:0% geometric access or axis surrounding<01:29:07.560> the<01:29:07.860> single<01:29:08.159> copper<01:29:08.639> core<01:29:08.820> is<01:29:09.480> a 01:29:09.709 --> 01:29:09.719 align:start position:0% surrounding the single copper core is a 01:29:09.719 --> 01:29:12.169 align:start position:0% surrounding the single copper core is a non-conducive<01:29:10.560> meaning<01:29:11.460> that<01:29:11.699> it's<01:29:11.880> not 01:29:12.169 --> 01:29:12.179 align:start position:0% non-conducive meaning that it's not 01:29:12.179 --> 01:29:14.990 align:start position:0% non-conducive meaning that it's not going<01:29:12.480> to<01:29:12.900> conduct<01:29:13.199> electricity<01:29:14.000> insulated 01:29:14.990 --> 01:29:15.000 align:start position:0% going to conduct electricity insulated 01:29:15.000 --> 01:29:18.470 align:start position:0% going to conduct electricity insulated coating<01:29:15.540> which<01:29:16.260> is<01:29:16.440> typically<01:29:17.000> uh<01:29:18.000> some<01:29:18.300> sort 01:29:18.470 --> 01:29:18.480 align:start position:0% coating which is typically uh some sort 01:29:18.480 --> 01:29:22.010 align:start position:0% coating which is typically uh some sort of<01:29:18.600> dielectric<01:29:19.500> insulator<01:29:20.300> separating<01:29:21.300> the 01:29:22.010 --> 01:29:22.020 align:start position:0% of dielectric insulator separating the 01:29:22.020 --> 01:29:24.350 align:start position:0% of dielectric insulator separating the core<01:29:22.440> from<01:29:23.159> the<01:29:23.340> shielding 01:29:24.350 --> 01:29:24.360 align:start position:0% core from the shielding 01:29:24.360 --> 01:29:26.330 align:start position:0% core from the shielding the<01:29:24.840> next<01:29:24.960> layer<01:29:25.260> after<01:29:25.380> that<01:29:25.620> is<01:29:25.860> braided 01:29:26.330 --> 01:29:26.340 align:start position:0% the next layer after that is braided 01:29:26.340 --> 01:29:28.790 align:start position:0% the next layer after that is braided metal<01:29:26.639> shielding<01:29:27.300> and<01:29:27.960> this<01:29:28.139> could<01:29:28.320> be<01:29:28.500> either 01:29:28.790 --> 01:29:28.800 align:start position:0% metal shielding and this could be either 01:29:28.800 --> 01:29:31.550 align:start position:0% metal shielding and this could be either copper<01:29:29.460> or<01:29:29.940> steel<01:29:30.239> sometimes<01:29:30.840> it's<01:29:31.020> a<01:29:31.199> mesh<01:29:31.440> of 01:29:31.550 --> 01:29:31.560 align:start position:0% copper or steel sometimes it's a mesh of 01:29:31.560 --> 01:29:33.110 align:start position:0% copper or steel sometimes it's a mesh of multiple<01:29:31.920> Metals<01:29:32.340> depends<01:29:32.880> on<01:29:33.000> the 01:29:33.110 --> 01:29:33.120 align:start position:0% multiple Metals depends on the 01:29:33.120 --> 01:29:35.270 align:start position:0% multiple Metals depends on the manufacturer<01:29:33.780> the<01:29:34.739> purpose<01:29:34.980> of<01:29:35.159> this 01:29:35.270 --> 01:29:35.280 align:start position:0% manufacturer the purpose of this 01:29:35.280 --> 01:29:36.709 align:start position:0% manufacturer the purpose of this shielding<01:29:35.639> just<01:29:35.820> as<01:29:35.940> it<01:29:36.120> was<01:29:36.239> with<01:29:36.540> the 01:29:36.709 --> 01:29:36.719 align:start position:0% shielding just as it was with the 01:29:36.719 --> 01:29:38.689 align:start position:0% shielding just as it was with the twisted<01:29:37.020> pair<01:29:37.199> is<01:29:37.620> to<01:29:37.920> protect<01:29:38.340> the<01:29:38.520> cable 01:29:38.689 --> 01:29:38.699 align:start position:0% twisted pair is to protect the cable 01:29:38.699 --> 01:29:41.090 align:start position:0% twisted pair is to protect the cable from<01:29:38.940> Emi<01:29:39.420> or<01:29:39.600> electromagnetic<01:29:40.500> interference 01:29:41.090 --> 01:29:41.100 align:start position:0% from Emi or electromagnetic interference 01:29:41.100 --> 01:29:44.330 align:start position:0% from Emi or electromagnetic interference it<01:29:41.820> also<01:29:42.179> allows<01:29:43.080> the<01:29:43.260> cable<01:29:43.440> to<01:29:43.679> be<01:29:43.800> grounded 01:29:44.330 --> 01:29:44.340 align:start position:0% it also allows the cable to be grounded 01:29:44.340 --> 01:29:47.330 align:start position:0% it also allows the cable to be grounded and<01:29:45.239> acts<01:29:45.600> as<01:29:45.719> sort<01:29:45.900> of<01:29:46.020> a<01:29:46.199> drain<01:29:46.560> when<01:29:47.159> there 01:29:47.330 --> 01:29:47.340 align:start position:0% and acts as sort of a drain when there 01:29:47.340 --> 01:29:49.430 align:start position:0% and acts as sort of a drain when there is<01:29:47.460> noise<01:29:47.699> on<01:29:48.060> the<01:29:48.239> line<01:29:48.360> we'll<01:29:49.080> talk<01:29:49.260> about 01:29:49.430 --> 01:29:49.440 align:start position:0% is noise on the line we'll talk about 01:29:49.440 --> 01:29:52.250 align:start position:0% is noise on the line we'll talk about noise<01:29:49.739> in<01:29:50.280> just<01:29:50.580> a<01:29:50.880> few<01:29:51.060> minutes<01:29:51.300> and<01:29:52.020> also 01:29:52.250 --> 01:29:52.260 align:start position:0% noise in just a few minutes and also 01:29:52.260 --> 01:29:53.810 align:start position:0% noise in just a few minutes and also ways<01:29:52.620> to<01:29:52.679> prevent<01:29:52.980> it 01:29:53.810 --> 01:29:53.820 align:start position:0% ways to prevent it 01:29:53.820 --> 01:29:56.090 align:start position:0% ways to prevent it the<01:29:54.480> final<01:29:54.659> layer<01:29:55.020> on<01:29:55.139> the<01:29:55.260> coaxial<01:29:55.679> cable<01:29:55.860> as 01:29:56.090 --> 01:29:56.100 align:start position:0% the final layer on the coaxial cable as 01:29:56.100 --> 01:29:58.310 align:start position:0% the final layer on the coaxial cable as you<01:29:56.219> can<01:29:56.280> see<01:29:56.340> is<01:29:56.520> this<01:29:56.760> outer<01:29:57.120> sheathing<01:29:57.540> or<01:29:58.080> a 01:29:58.310 --> 01:29:58.320 align:start position:0% you can see is this outer sheathing or a 01:29:58.320 --> 01:30:00.410 align:start position:0% you can see is this outer sheathing or a plastic<01:29:58.620> insulating<01:29:59.340> jacket 01:30:00.410 --> 01:30:00.420 align:start position:0% plastic insulating jacket 01:30:00.420 --> 01:30:02.110 align:start position:0% plastic insulating jacket which<01:30:00.840> just<01:30:01.139> sort<01:30:01.260> of<01:30:01.380> keeps<01:30:01.679> everything 01:30:02.110 --> 01:30:02.120 align:start position:0% which just sort of keeps everything 01:30:02.120 --> 01:30:04.610 align:start position:0% which just sort of keeps everything protected<01:30:03.120> from<01:30:03.300> the<01:30:03.420> elements 01:30:04.610 --> 01:30:04.620 align:start position:0% protected from the elements 01:30:04.620 --> 01:30:06.770 align:start position:0% protected from the elements now<01:30:04.980> there<01:30:05.159> have<01:30:05.340> been<01:30:05.520> several<01:30:06.000> types<01:30:06.480> of 01:30:06.770 --> 01:30:06.780 align:start position:0% now there have been several types of 01:30:06.780 --> 01:30:09.350 align:start position:0% now there have been several types of coaxial<01:30:07.500> cables<01:30:07.980> used<01:30:08.340> in<01:30:08.580> networks<01:30:09.000> over<01:30:09.120> the 01:30:09.350 --> 01:30:09.360 align:start position:0% coaxial cables used in networks over the 01:30:09.360 --> 01:30:11.629 align:start position:0% coaxial cables used in networks over the past<01:30:09.480> few<01:30:09.719> years<01:30:09.900> uh<01:30:10.620> here's<01:30:10.860> a<01:30:10.980> breakdown<01:30:11.280> of 01:30:11.629 --> 01:30:11.639 align:start position:0% past few years uh here's a breakdown of 01:30:11.639 --> 01:30:13.910 align:start position:0% past few years uh here's a breakdown of what<01:30:11.940> you<01:30:12.179> should<01:30:12.360> be<01:30:12.480> familiar<01:30:12.840> with<01:30:13.020> the 01:30:13.910 --> 01:30:13.920 align:start position:0% what you should be familiar with the 01:30:13.920 --> 01:30:15.729 align:start position:0% what you should be familiar with the first<01:30:14.040> is<01:30:14.400> what's<01:30:14.580> called<01:30:14.820> an 01:30:15.729 --> 01:30:15.739 align:start position:0% first is what's called an 01:30:15.739 --> 01:30:18.709 align:start position:0% first is what's called an rg58u<01:30:16.739> it<01:30:17.460> was<01:30:17.580> used<01:30:17.760> for<01:30:18.060> ethernet 01:30:18.709 --> 01:30:18.719 align:start position:0% rg58u it was used for ethernet 01:30:18.719 --> 01:30:20.209 align:start position:0% rg58u it was used for ethernet networking<01:30:19.199> actually<01:30:19.320> if<01:30:19.560> you<01:30:19.739> see<01:30:19.920> old 01:30:20.209 --> 01:30:20.219 align:start position:0% networking actually if you see old 01:30:20.219 --> 01:30:22.790 align:start position:0% networking actually if you see old network<01:30:20.639> cards<01:30:21.120> you'll<01:30:21.300> actually<01:30:21.480> see<01:30:21.840> a<01:30:22.199> a 01:30:22.790 --> 01:30:22.800 align:start position:0% network cards you'll actually see a a 01:30:22.800 --> 01:30:25.910 align:start position:0% network cards you'll actually see a a coaxial<01:30:23.520> cable<01:30:23.880> on<01:30:24.179> them<01:30:24.360> and<01:30:24.780> it<01:30:24.960> has<01:30:25.139> a<01:30:25.560> solid 01:30:25.910 --> 01:30:25.920 align:start position:0% coaxial cable on them and it has a solid 01:30:25.920 --> 01:30:29.570 align:start position:0% coaxial cable on them and it has a solid core<01:30:26.280> and<01:30:26.699> requires<01:30:27.179> a<01:30:27.540> 50<01:30:27.659> Ohm<01:30:28.199> resistor<01:30:29.100> it's 01:30:29.570 --> 01:30:29.580 align:start position:0% core and requires a 50 Ohm resistor it's 01:30:29.580 --> 01:30:31.189 align:start position:0% core and requires a 50 Ohm resistor it's about<01:30:29.820> five<01:30:30.120> millimeters<01:30:30.659> thick<01:30:30.900> this<01:30:31.139> is 01:30:31.189 --> 01:30:31.199 align:start position:0% about five millimeters thick this is 01:30:31.199 --> 01:30:32.570 align:start position:0% about five millimeters thick this is different<01:30:31.440> from<01:30:31.739> the<01:30:31.860> stuff<01:30:32.040> that<01:30:32.280> brings 01:30:32.570 --> 01:30:32.580 align:start position:0% different from the stuff that brings 01:30:32.580 --> 01:30:35.689 align:start position:0% different from the stuff that brings cable<01:30:33.239> into<01:30:33.480> your<01:30:33.780> home<01:30:34.440> and<01:30:35.219> if<01:30:35.400> you<01:30:35.520> remember 01:30:35.689 --> 01:30:35.699 align:start position:0% cable into your home and if you remember 01:30:35.699 --> 01:30:39.290 align:start position:0% cable into your home and if you remember 50<01:30:36.420> ohm<01:30:36.900> resistor<01:30:37.320> that<01:30:37.800> is<01:30:37.920> what<01:30:38.159> was<01:30:38.280> used<01:30:38.580> on 01:30:39.290 --> 01:30:39.300 align:start position:0% 50 ohm resistor that is what was used on 01:30:39.300 --> 01:30:43.790 align:start position:0% 50 ohm resistor that is what was used on a<01:30:40.080> bust<01:30:40.980> apology<01:30:41.400> and<01:30:42.239> that's<01:30:42.420> why<01:30:42.719> where<01:30:43.560> we 01:30:43.790 --> 01:30:43.800 align:start position:0% a bust apology and that's why where we 01:30:43.800 --> 01:30:45.890 align:start position:0% a bust apology and that's why where we actually<01:30:43.920> used<01:30:44.280> most<01:30:44.760> of<01:30:44.940> these<01:30:45.179> was<01:30:45.420> on<01:30:45.659> a<01:30:45.780> bus 01:30:45.890 --> 01:30:45.900 align:start position:0% actually used most of these was on a bus 01:30:45.900 --> 01:30:48.370 align:start position:0% actually used most of these was on a bus topology<01:30:46.440> now<01:30:47.340> the 01:30:48.370 --> 01:30:48.380 align:start position:0% topology now the 01:30:48.380 --> 01:30:51.410 align:start position:0% topology now the rg58au<01:30:49.380> is<01:30:50.040> slightly<01:30:50.340> different<01:30:50.580> in<01:30:51.239> that 01:30:51.410 --> 01:30:51.420 align:start position:0% rg58au is slightly different in that 01:30:51.420 --> 01:30:53.209 align:start position:0% rg58au is slightly different in that instead<01:30:51.719> of<01:30:51.780> having<01:30:51.960> a<01:30:52.260> solid<01:30:52.560> cord<01:30:52.800> it<01:30:53.040> has 01:30:53.209 --> 01:30:53.219 align:start position:0% instead of having a solid cord it has 01:30:53.219 --> 01:30:55.070 align:start position:0% instead of having a solid cord it has what's<01:30:53.400> called<01:30:53.639> a<01:30:53.880> stranded<01:30:54.300> core<01:30:54.540> which 01:30:55.070 --> 01:30:55.080 align:start position:0% what's called a stranded core which 01:30:55.080 --> 01:30:57.530 align:start position:0% what's called a stranded core which means<01:30:55.320> there<01:30:55.620> are<01:30:55.800> multiple<01:30:56.219> strands<01:30:56.880> or 01:30:57.530 --> 01:30:57.540 align:start position:0% means there are multiple strands or 01:30:57.540 --> 01:30:59.750 align:start position:0% means there are multiple strands or cores<01:30:58.080> at<01:30:58.380> its<01:30:58.679> Center<01:30:58.800> as<01:30:59.159> opposed<01:30:59.400> to<01:30:59.460> one 01:30:59.750 --> 01:30:59.760 align:start position:0% cores at its Center as opposed to one 01:30:59.760 --> 01:31:01.129 align:start position:0% cores at its Center as opposed to one solid<01:31:00.120> one 01:31:01.129 --> 01:31:01.139 align:start position:0% solid one 01:31:01.139 --> 01:31:03.770 align:start position:0% solid one next<01:31:01.800> and<01:31:01.980> this<01:31:02.159> one<01:31:02.219> might<01:31:02.400> be<01:31:02.520> a<01:31:02.699> little<01:31:02.940> more 01:31:03.770 --> 01:31:03.780 align:start position:0% next and this one might be a little more 01:31:03.780 --> 01:31:05.090 align:start position:0% next and this one might be a little more we're<01:31:04.139> going<01:31:04.320> to<01:31:04.380> get<01:31:04.500> a<01:31:04.620> little<01:31:04.739> more<01:31:04.920> into 01:31:05.090 --> 01:31:05.100 align:start position:0% we're going to get a little more into 01:31:05.100 --> 01:31:06.890 align:start position:0% we're going to get a little more into sums<01:31:05.460> that<01:31:05.580> you've<01:31:05.760> probably<01:31:05.880> seen<01:31:06.239> is<01:31:06.659> What's 01:31:06.890 --> 01:31:06.900 align:start position:0% sums that you've probably seen is What's 01:31:06.900 --> 01:31:09.950 align:start position:0% sums that you've probably seen is What's called<01:31:07.080> the<01:31:07.380> rg8<01:31:08.219> standard<01:31:08.880> it<01:31:09.420> was<01:31:09.540> also<01:31:09.780> used 01:31:09.950 --> 01:31:09.960 align:start position:0% called the rg8 standard it was also used 01:31:09.960 --> 01:31:11.810 align:start position:0% called the rg8 standard it was also used for<01:31:10.199> ethernet<01:31:10.679> networking<01:31:11.219> but<01:31:11.460> it's<01:31:11.580> not 01:31:11.810 --> 01:31:11.820 align:start position:0% for ethernet networking but it's not 01:31:11.820 --> 01:31:14.450 align:start position:0% for ethernet networking but it's not seen<01:31:12.060> very<01:31:12.360> frequently<01:31:12.719> today 01:31:14.450 --> 01:31:14.460 align:start position:0% seen very frequently today 01:31:14.460 --> 01:31:16.550 align:start position:0% seen very frequently today um<01:31:14.520> because<01:31:15.000> it's<01:31:15.300> typically<01:31:15.719> was<01:31:15.960> used<01:31:16.199> for 01:31:16.550 --> 01:31:16.560 align:start position:0% um because it's typically was used for 01:31:16.560 --> 01:31:19.610 align:start position:0% um because it's typically was used for backbone<01:31:17.219> wiring<01:31:17.699> and<01:31:18.659> it's<01:31:18.900> been<01:31:19.020> which<01:31:19.440> has 01:31:19.610 --> 01:31:19.620 align:start position:0% backbone wiring and it's been which has 01:31:19.620 --> 01:31:22.729 align:start position:0% backbone wiring and it's been which has largely<01:31:20.040> been<01:31:20.340> sort<01:31:20.760> of<01:31:20.900> superseded<01:31:21.900> by<01:31:22.260> fiber 01:31:22.729 --> 01:31:22.739 align:start position:0% largely been sort of superseded by fiber 01:31:22.739 --> 01:31:23.870 align:start position:0% largely been sort of superseded by fiber optics 01:31:23.870 --> 01:31:23.880 align:start position:0% optics 01:31:23.880 --> 01:31:27.410 align:start position:0% optics finally<01:31:24.300> we<01:31:24.480> have<01:31:24.679> rg9<01:31:25.679> uh<01:31:26.520> coaxial<01:31:27.060> cables 01:31:27.410 --> 01:31:27.420 align:start position:0% finally we have rg9 uh coaxial cables 01:31:27.420 --> 01:31:30.050 align:start position:0% finally we have rg9 uh coaxial cables which<01:31:27.600> are<01:31:27.780> used<01:31:27.960> with<01:31:28.320> cable<01:31:28.739> TV<01:31:29.159> cable<01:31:29.639> modem 01:31:30.050 --> 01:31:30.060 align:start position:0% which are used with cable TV cable modem 01:31:30.060 --> 01:31:32.930 align:start position:0% which are used with cable TV cable modem installations<01:31:30.540> and<01:31:30.960> so<01:31:31.139> on<01:31:31.320> it's<01:31:32.219> about<01:31:32.460> 10 01:31:32.930 --> 01:31:32.940 align:start position:0% installations and so on it's about 10 01:31:32.940 --> 01:31:35.030 align:start position:0% installations and so on it's about 10 millimeters<01:31:33.480> thick<01:31:33.780> which<01:31:34.080> is<01:31:34.260> twice<01:31:34.860> the 01:31:35.030 --> 01:31:35.040 align:start position:0% millimeters thick which is twice the 01:31:35.040 --> 01:31:38.030 align:start position:0% millimeters thick which is twice the thickness<01:31:35.400> of<01:31:35.820> the<01:31:36.000> original<01:31:36.120> RG58 01:31:38.030 --> 01:31:38.040 align:start position:0% thickness of the original RG58 01:31:38.040 --> 01:31:39.530 align:start position:0% thickness of the original RG58 now<01:31:38.460> we're<01:31:38.639> getting<01:31:38.760> into<01:31:38.880> some<01:31:39.120> others<01:31:39.420> here 01:31:39.530 --> 01:31:39.540 align:start position:0% now we're getting into some others here 01:31:39.540 --> 01:31:42.709 align:start position:0% now we're getting into some others here that<01:31:39.719> I<01:31:39.960> wouldn't<01:31:40.080> worry<01:31:40.440> too<01:31:40.739> much<01:31:40.860> about<01:31:41.100> for 01:31:42.709 --> 01:31:42.719 align:start position:0% that I wouldn't worry too much about for 01:31:42.719 --> 01:31:44.330 align:start position:0% that I wouldn't worry too much about for um<01:31:42.780> the<01:31:43.199> test<01:31:43.380> but<01:31:43.620> I<01:31:43.800> just<01:31:43.860> want<01:31:43.980> to<01:31:44.100> go<01:31:44.219> over 01:31:44.330 --> 01:31:44.340 align:start position:0% um the test but I just want to go over 01:31:44.340 --> 01:31:45.649 align:start position:0% um the test but I just want to go over them<01:31:44.580> since<01:31:44.760> we're<01:31:45.000> covering<01:31:45.300> these<01:31:45.480> anyway 01:31:45.649 --> 01:31:45.659 align:start position:0% them since we're covering these anyway 01:31:45.659 --> 01:31:48.470 align:start position:0% them since we're covering these anyway we<01:31:46.320> have<01:31:46.440> something<01:31:46.560> called<01:31:46.940> rg62<01:31:47.940> cabling 01:31:48.470 --> 01:31:48.480 align:start position:0% we have something called rg62 cabling 01:31:48.480 --> 01:31:50.330 align:start position:0% we have something called rg62 cabling which<01:31:49.020> is<01:31:49.139> utilized<01:31:49.620> for<01:31:49.920> uh<01:31:50.159> something 01:31:50.330 --> 01:31:50.340 align:start position:0% which is utilized for uh something 01:31:50.340 --> 01:31:53.030 align:start position:0% which is utilized for uh something called<01:31:50.580> an<01:31:50.820> arcnet<01:31:51.420> protocol<01:31:51.960> uh<01:31:52.560> networking 01:31:53.030 --> 01:31:53.040 align:start position:0% called an arcnet protocol uh networking 01:31:53.040 --> 01:31:56.149 align:start position:0% called an arcnet protocol uh networking it<01:31:53.520> was<01:31:53.639> a<01:31:53.820> lan<01:31:54.120> protocol<01:31:54.620> uh<01:31:55.620> commonly<01:31:55.980> used 01:31:56.149 --> 01:31:56.159 align:start position:0% it was a lan protocol uh commonly used 01:31:56.159 --> 01:31:59.209 align:start position:0% it was a lan protocol uh commonly used in<01:31:56.400> what<01:31:56.580> was<01:31:56.699> called<01:31:57.080> microprocessing<01:31:58.219> and 01:31:59.209 --> 01:31:59.219 align:start position:0% in what was called microprocessing and 01:31:59.219 --> 01:32:01.970 align:start position:0% in what was called microprocessing and then<01:31:59.280> we<01:31:59.460> have<01:31:59.580> an<01:31:59.780> rg59<01:32:00.780> cable<01:32:01.260> which<01:32:01.860> was 01:32:01.970 --> 01:32:01.980 align:start position:0% then we have an rg59 cable which was 01:32:01.980 --> 01:32:04.250 align:start position:0% then we have an rg59 cable which was used<01:32:02.219> with<01:32:02.520> low<01:32:02.880> power<01:32:03.120> which<01:32:03.600> is<01:32:03.719> used<01:32:03.900> rather 01:32:04.250 --> 01:32:04.260 align:start position:0% used with low power which is used rather 01:32:04.260 --> 01:32:06.830 align:start position:0% used with low power which is used rather with<01:32:04.500> low<01:32:04.679> power<01:32:04.920> video<01:32:05.280> and<01:32:05.520> receivers<01:32:06.120> uh 01:32:06.830 --> 01:32:06.840 align:start position:0% with low power video and receivers uh 01:32:06.840 --> 01:32:08.930 align:start position:0% with low power video and receivers uh and<01:32:07.080> it<01:32:07.199> had<01:32:07.380> also<01:32:07.679> resistors<01:32:08.340> and<01:32:08.639> it<01:32:08.760> was 01:32:08.930 --> 01:32:08.940 align:start position:0% and it had also resistors and it was 01:32:08.940 --> 01:32:12.350 align:start position:0% and it had also resistors and it was about<01:32:09.120> six<01:32:09.480> millimeters<01:32:10.080> thick<01:32:10.440> the<01:32:11.400> RG6 01:32:12.350 --> 01:32:12.360 align:start position:0% about six millimeters thick the RG6 01:32:12.360 --> 01:32:14.510 align:start position:0% about six millimeters thick the RG6 cabling<01:32:12.960> which<01:32:13.620> is<01:32:13.739> greatly<01:32:14.040> preferred<01:32:14.400> by 01:32:14.510 --> 01:32:14.520 align:start position:0% cabling which is greatly preferred by 01:32:14.520 --> 01:32:17.090 align:start position:0% cabling which is greatly preferred by the<01:32:14.639> way<01:32:14.699> over<01:32:14.880> rg59 01:32:17.090 --> 01:32:17.100 align:start position:0% the way over rg59 01:32:17.100 --> 01:32:20.570 align:start position:0% the way over rg59 uh<01:32:17.639> because<01:32:17.820> it's<01:32:18.239> more<01:32:18.600> common<01:32:18.860> is<01:32:19.860> utilized 01:32:20.570 --> 01:32:20.580 align:start position:0% uh because it's more common is utilized 01:32:20.580 --> 01:32:22.910 align:start position:0% uh because it's more common is utilized for<01:32:20.940> cable<01:32:21.300> television<01:32:21.780> signal<01:32:22.260> routing<01:32:22.620> and 01:32:22.910 --> 01:32:22.920 align:start position:0% for cable television signal routing and 01:32:22.920 --> 01:32:24.410 align:start position:0% for cable television signal routing and also<01:32:23.219> requires 01:32:24.410 --> 01:32:24.420 align:start position:0% also requires 01:32:24.420 --> 01:32:28.490 align:start position:0% also requires uh<01:32:24.719> 75<01:32:25.500> ohm<01:32:25.980> resistors 01:32:28.490 --> 01:32:28.500 align:start position:0% uh 75 ohm resistors 01:32:28.500 --> 01:32:31.669 align:start position:0% uh 75 ohm resistors the<01:32:28.980> term<01:32:29.159> by<01:32:29.340> the<01:32:29.520> way<01:32:29.580> thin<01:32:30.000> net<01:32:30.320> is<01:32:31.320> in 01:32:31.669 --> 01:32:31.679 align:start position:0% the term by the way thin net is in 01:32:31.679 --> 01:32:34.550 align:start position:0% the term by the way thin net is in reference<01:32:32.040> to<01:32:32.460> ethernet<01:32:33.060> networking<01:32:33.719> that 01:32:34.550 --> 01:32:34.560 align:start position:0% reference to ethernet networking that 01:32:34.560 --> 01:32:38.750 align:start position:0% reference to ethernet networking that uses<01:32:34.920> the<01:32:35.239> rg58u<01:32:36.239> or<01:32:36.480> Au<01:32:36.960> cabling<01:32:37.580> these<01:32:38.580> thin 01:32:38.750 --> 01:32:38.760 align:start position:0% uses the rg58u or Au cabling these thin 01:32:38.760 --> 01:32:40.970 align:start position:0% uses the rg58u or Au cabling these thin net<01:32:38.940> cables<01:32:39.540> coaxial<01:32:40.320> and<01:32:40.739> the<01:32:40.860> reason 01:32:40.970 --> 01:32:40.980 align:start position:0% net cables coaxial and the reason 01:32:40.980 --> 01:32:42.649 align:start position:0% net cables coaxial and the reason they're<01:32:41.159> called<01:32:41.280> thin<01:32:41.520> is<01:32:41.699> because<01:32:41.880> that<01:32:42.179> thin 01:32:42.649 --> 01:32:42.659 align:start position:0% they're called thin is because that thin 01:32:42.659 --> 01:32:44.209 align:start position:0% they're called thin is because that thin five<01:32:42.900> millimeter 01:32:44.209 --> 01:32:44.219 align:start position:0% five millimeter 01:32:44.219 --> 01:32:48.590 align:start position:0% five millimeter uh<01:32:44.880> coaxial<01:32:45.360> cable<01:32:45.600> can<01:32:46.560> be<01:32:46.679> up<01:32:46.860> to<01:32:47.120> 185<01:32:48.120> meters 01:32:48.590 --> 01:32:48.600 align:start position:0% uh coaxial cable can be up to 185 meters 01:32:48.600 --> 01:32:50.090 align:start position:0% uh coaxial cable can be up to 185 meters in<01:32:48.719> length<01:32:49.020> which<01:32:49.260> is<01:32:49.380> quite<01:32:49.560> different<01:32:49.739> from 01:32:50.090 --> 01:32:50.100 align:start position:0% in length which is quite different from 01:32:50.100 --> 01:32:52.490 align:start position:0% in length which is quite different from the<01:32:50.219> 100<01:32:50.400> meters<01:32:50.820> we<01:32:51.000> got<01:32:51.120> with<01:32:51.300> ethernet<01:32:51.840> uh 01:32:52.490 --> 01:32:52.500 align:start position:0% the 100 meters we got with ethernet uh 01:32:52.500 --> 01:32:54.110 align:start position:0% the 100 meters we got with ethernet uh Twisted<01:32:52.980> fare 01:32:54.110 --> 01:32:54.120 align:start position:0% Twisted fare 01:32:54.120 --> 01:32:56.870 align:start position:0% Twisted fare Network<01:32:54.840> segments<01:32:55.620> that<01:32:55.800> utilized<01:32:56.340> coaxial 01:32:56.870 --> 01:32:56.880 align:start position:0% Network segments that utilized coaxial 01:32:56.880 --> 01:32:59.209 align:start position:0% Network segments that utilized coaxial cabling<01:32:57.300> have<01:32:57.900> to<01:32:58.080> be<01:32:58.199> terminated<01:32:58.739> at<01:32:59.040> the 01:32:59.209 --> 01:32:59.219 align:start position:0% cabling have to be terminated at the 01:32:59.219 --> 01:33:01.129 align:start position:0% cabling have to be terminated at the ends<01:32:59.400> like<01:32:59.639> we've<01:32:59.880> talked<01:33:00.179> about<01:33:00.239> to<01:33:00.840> provide 01:33:01.129 --> 01:33:01.139 align:start position:0% ends like we've talked about to provide 01:33:01.139 --> 01:33:02.629 align:start position:0% ends like we've talked about to provide that<01:33:01.320> signal<01:33:01.679> Bounce<01:33:01.980> from<01:33:02.159> occurring 01:33:02.629 --> 01:33:02.639 align:start position:0% that signal Bounce from occurring 01:33:02.639 --> 01:33:04.490 align:start position:0% that signal Bounce from occurring they're<01:33:03.239> terminated<01:33:03.659> by<01:33:03.960> installing<01:33:04.320> that 01:33:04.490 --> 01:33:04.500 align:start position:0% they're terminated by installing that 01:33:04.500 --> 01:33:07.490 align:start position:0% they're terminated by installing that resistor<01:33:05.040> that<01:33:05.340> matches<01:33:05.760> impedance<01:33:06.420> uh<01:33:07.199> that 01:33:07.490 --> 01:33:07.500 align:start position:0% resistor that matches impedance uh that 01:33:07.500 --> 01:33:09.169 align:start position:0% resistor that matches impedance uh that matches<01:33:07.920> the<01:33:08.100> impedance<01:33:08.460> of<01:33:08.639> the<01:33:08.760> cable<01:33:08.940> on 01:33:09.169 --> 01:33:09.179 align:start position:0% matches the impedance of the cable on 01:33:09.179 --> 01:33:11.209 align:start position:0% matches the impedance of the cable on the<01:33:09.360> ends<01:33:09.600> so<01:33:10.139> as<01:33:10.380> we've<01:33:10.620> mentioned<01:33:10.920> some<01:33:11.100> of 01:33:11.209 --> 01:33:11.219 align:start position:0% the ends so as we've mentioned some of 01:33:11.219 --> 01:33:14.450 align:start position:0% the ends so as we've mentioned some of these<01:33:11.340> are<01:33:11.460> 50<01:33:11.639> ohms<01:33:12.120> 60<01:33:12.239> Ohms<01:33:12.659> on<01:33:13.139> a 01:33:14.450 --> 01:33:14.460 align:start position:0% these are 50 ohms 60 Ohms on a 01:33:14.460 --> 01:33:17.810 align:start position:0% these are 50 ohms 60 Ohms on a a<01:33:14.520> typical<01:33:15.500> bus<01:33:16.500> topology<01:33:17.100> Network<01:33:17.460> we're 01:33:17.810 --> 01:33:17.820 align:start position:0% a typical bus topology Network we're 01:33:17.820 --> 01:33:21.770 align:start position:0% a typical bus topology Network we're looking<01:33:18.060> at<01:33:18.540> 50<01:33:19.080> ohms 01:33:21.770 --> 01:33:21.780 align:start position:0% 01:33:21.780 --> 01:33:23.990 align:start position:0% now<01:33:22.260> here's<01:33:22.679> a<01:33:22.800> visual<01:33:23.040> of<01:33:23.219> what<01:33:23.520> the<01:33:23.820> most 01:33:23.990 --> 01:33:24.000 align:start position:0% now here's a visual of what the most 01:33:24.000 --> 01:33:26.930 align:start position:0% now here's a visual of what the most common<01:33:24.360> coaxial<01:33:25.199> connectors<01:33:25.860> are<01:33:26.100> first<01:33:26.760> we 01:33:26.930 --> 01:33:26.940 align:start position:0% common coaxial connectors are first we 01:33:26.940 --> 01:33:29.810 align:start position:0% common coaxial connectors are first we have<01:33:27.060> a<01:33:27.239> picture<01:33:27.360> of<01:33:27.780> a<01:33:28.020> BNC<01:33:28.739> connector<01:33:29.340> with 01:33:29.810 --> 01:33:29.820 align:start position:0% have a picture of a BNC connector with 01:33:29.820 --> 01:33:31.850 align:start position:0% have a picture of a BNC connector with different<01:33:29.940> types<01:33:30.300> of<01:33:30.420> resistors<01:33:30.900> attached<01:33:31.380> if 01:33:31.850 --> 01:33:31.860 align:start position:0% different types of resistors attached if 01:33:31.860 --> 01:33:34.129 align:start position:0% different types of resistors attached if we<01:33:31.980> look<01:33:32.100> closely<01:33:32.520> at<01:33:32.699> the<01:33:32.880> top<01:33:33.060> connector<01:33:33.600> you 01:33:34.129 --> 01:33:34.139 align:start position:0% we look closely at the top connector you 01:33:34.139 --> 01:33:36.129 align:start position:0% we look closely at the top connector you can<01:33:34.260> see<01:33:34.440> the<01:33:34.800> small<01:33:35.159> needle<01:33:35.520> at<01:33:35.699> the<01:33:35.880> center 01:33:36.129 --> 01:33:36.139 align:start position:0% can see the small needle at the center 01:33:36.139 --> 01:33:39.530 align:start position:0% can see the small needle at the center is<01:33:37.139> just<01:33:37.739> slightly<01:33:38.159> bigger<01:33:38.520> than<01:33:38.699> the<01:33:38.940> 50<01:33:39.120> ohm 01:33:39.530 --> 01:33:39.540 align:start position:0% is just slightly bigger than the 50 ohm 01:33:39.540 --> 01:33:42.290 align:start position:0% is just slightly bigger than the 50 ohm on<01:33:39.719> the<01:33:39.840> bottom<01:33:40.080> this<01:33:40.860> is<01:33:40.980> important<01:33:41.340> uh<01:33:42.060> in 01:33:42.290 --> 01:33:42.300 align:start position:0% on the bottom this is important uh in 01:33:42.300 --> 01:33:44.510 align:start position:0% on the bottom this is important uh in case<01:33:42.420> you<01:33:42.659> have<01:33:42.780> a<01:33:43.080> 75<01:33:43.560> ohm<01:33:44.040> which<01:33:44.219> is<01:33:44.280> plugged 01:33:44.510 --> 01:33:44.520 align:start position:0% case you have a 75 ohm which is plugged 01:33:44.520 --> 01:33:45.950 align:start position:0% case you have a 75 ohm which is plugged into<01:33:44.639> a<01:33:44.880> 50<01:33:45.000> ohm<01:33:45.360> because<01:33:45.540> there's<01:33:45.719> going<01:33:45.840> to 01:33:45.950 --> 01:33:45.960 align:start position:0% into a 50 ohm because there's going to 01:33:45.960 --> 01:33:49.669 align:start position:0% into a 50 ohm because there's going to be<01:33:46.020> a<01:33:46.620> potential<01:33:47.460> of<01:33:48.060> damaging<01:33:48.600> the<01:33:49.080> connector 01:33:49.669 --> 01:33:49.679 align:start position:0% be a potential of damaging the connector 01:33:49.679 --> 01:33:51.410 align:start position:0% be a potential of damaging the connector that's<01:33:49.920> being<01:33:50.159> received 01:33:51.410 --> 01:33:51.420 align:start position:0% that's being received 01:33:51.420 --> 01:33:53.330 align:start position:0% that's being received now<01:33:51.840> this<01:33:52.020> next<01:33:52.199> picture<01:33:52.380> is<01:33:52.620> a<01:33:52.739> shot<01:33:52.860> of<01:33:53.040> a<01:33:53.159> t 01:33:53.330 --> 01:33:53.340 align:start position:0% now this next picture is a shot of a t 01:33:53.340 --> 01:33:55.189 align:start position:0% now this next picture is a shot of a t connector<01:33:53.820> and<01:33:54.239> a<01:33:54.420> Terminator<01:33:54.780> remember<01:33:54.960> we 01:33:55.189 --> 01:33:55.199 align:start position:0% connector and a Terminator remember we 01:33:55.199 --> 01:33:56.390 align:start position:0% connector and a Terminator remember we talked<01:33:55.500> about<01:33:55.560> these<01:33:55.800> when<01:33:56.040> we<01:33:56.159> were<01:33:56.280> talking 01:33:56.390 --> 01:33:56.400 align:start position:0% talked about these when we were talking 01:33:56.400 --> 01:33:58.729 align:start position:0% talked about these when we were talking about<01:33:56.580> bust<01:33:56.880> apologies<01:33:57.600> and<01:33:58.080> when<01:33:58.260> purchasing 01:33:58.729 --> 01:33:58.739 align:start position:0% about bust apologies and when purchasing 01:33:58.739 --> 01:34:00.110 align:start position:0% about bust apologies and when purchasing these<01:33:58.860> you<01:33:59.040> want<01:33:59.159> to<01:33:59.280> make<01:33:59.400> sure<01:33:59.639> you<01:33:59.940> check 01:34:00.110 --> 01:34:00.120 align:start position:0% these you want to make sure you check 01:34:00.120 --> 01:34:02.030 align:start position:0% these you want to make sure you check that<01:34:00.360> they're<01:34:00.600> properly<01:34:00.900> rated 01:34:02.030 --> 01:34:02.040 align:start position:0% that they're properly rated 01:34:02.040 --> 01:34:05.030 align:start position:0% that they're properly rated because<01:34:02.580> uh<01:34:03.480> you<01:34:03.719> know<01:34:03.840> every<01:34:04.440> manufacturer 01:34:05.030 --> 01:34:05.040 align:start position:0% because uh you know every manufacturer 01:34:05.040 --> 01:34:07.550 align:start position:0% because uh you know every manufacturer has<01:34:05.280> different<01:34:05.580> color<01:34:06.300> schemes<01:34:06.900> and 01:34:07.550 --> 01:34:07.560 align:start position:0% has different color schemes and 01:34:07.560 --> 01:34:10.010 align:start position:0% has different color schemes and different<01:34:07.800> types<01:34:08.280> of<01:34:08.460> uh<01:34:09.000> ways<01:34:09.960> of 01:34:10.010 --> 01:34:10.020 align:start position:0% different types of uh ways of 01:34:10.020 --> 01:34:12.830 align:start position:0% different types of uh ways of categorizing<01:34:10.679> their<01:34:10.860> terminators 01:34:12.830 --> 01:34:12.840 align:start position:0% categorizing their terminators 01:34:12.840 --> 01:34:15.169 align:start position:0% categorizing their terminators now<01:34:13.440> moving<01:34:13.800> away<01:34:13.980> from 01:34:15.169 --> 01:34:15.179 align:start position:0% now moving away from 01:34:15.179 --> 01:34:17.570 align:start position:0% now moving away from copper<01:34:15.900> cabling<01:34:16.320> which<01:34:16.860> is<01:34:16.980> what<01:34:17.219> twisted 01:34:17.570 --> 01:34:17.580 align:start position:0% copper cabling which is what twisted 01:34:17.580 --> 01:34:20.689 align:start position:0% copper cabling which is what twisted pair<01:34:17.820> and<01:34:18.360> coaxial<01:34:18.960> is<01:34:19.199> let's<01:34:19.860> look<01:34:20.040> at<01:34:20.159> fiber 01:34:20.689 --> 01:34:20.699 align:start position:0% pair and coaxial is let's look at fiber 01:34:20.699 --> 01:34:23.530 align:start position:0% pair and coaxial is let's look at fiber optic<01:34:21.060> cabling<01:34:21.480> which<01:34:21.960> is<01:34:22.080> cable<01:34:22.620> that<01:34:22.860> uses 01:34:23.530 --> 01:34:23.540 align:start position:0% optic cabling which is cable that uses 01:34:23.540 --> 01:34:26.870 align:start position:0% optic cabling which is cable that uses pulses<01:34:24.540> of<01:34:24.780> light<01:34:25.080> sent<01:34:25.860> down<01:34:26.100> glass<01:34:26.460> or 01:34:26.870 --> 01:34:26.880 align:start position:0% pulses of light sent down glass or 01:34:26.880 --> 01:34:28.310 align:start position:0% pulses of light sent down glass or plastic<01:34:27.239> core 01:34:28.310 --> 01:34:28.320 align:start position:0% plastic core 01:34:28.320 --> 01:34:30.530 align:start position:0% plastic core the<01:34:28.860> components<01:34:29.460> in<01:34:29.580> fiber<01:34:29.880> optic<01:34:30.120> cables 01:34:30.530 --> 01:34:30.540 align:start position:0% the components in fiber optic cables 01:34:30.540 --> 01:34:32.990 align:start position:0% the components in fiber optic cables start<01:34:30.780> out<01:34:31.020> from<01:34:31.739> the<01:34:32.159> center<01:34:32.340> working<01:34:32.760> their 01:34:32.990 --> 01:34:33.000 align:start position:0% start out from the center working their 01:34:33.000 --> 01:34:35.750 align:start position:0% start out from the center working their way<01:34:33.179> out<01:34:33.420> so<01:34:34.199> the<01:34:34.800> inner<01:34:35.100> strengthening<01:34:35.580> Rod 01:34:35.750 --> 01:34:35.760 align:start position:0% way out so the inner strengthening Rod 01:34:35.760 --> 01:34:38.930 align:start position:0% way out so the inner strengthening Rod gives<01:34:36.300> the<01:34:36.540> cable<01:34:36.719> its<01:34:37.440> most<01:34:37.620> most<01:34:38.460> of<01:34:38.699> its 01:34:38.930 --> 01:34:38.940 align:start position:0% gives the cable its most most of its 01:34:38.940 --> 01:34:40.790 align:start position:0% gives the cable its most most of its rigidity<01:34:39.360> otherwise<01:34:40.080> we<01:34:40.260> would<01:34:40.380> just<01:34:40.560> sort<01:34:40.679> of 01:34:40.790 --> 01:34:40.800 align:start position:0% rigidity otherwise we would just sort of 01:34:40.800 --> 01:34:42.410 align:start position:0% rigidity otherwise we would just sort of crack<01:34:40.980> this<01:34:41.280> stuff<01:34:41.460> because<01:34:41.639> it's<01:34:41.820> very<01:34:42.060> thin 01:34:42.410 --> 01:34:42.420 align:start position:0% crack this stuff because it's very thin 01:34:42.420 --> 01:34:43.850 align:start position:0% crack this stuff because it's very thin so<01:34:42.780> we<01:34:42.900> have<01:34:43.080> something<01:34:43.260> that's<01:34:43.500> going<01:34:43.739> to 01:34:43.850 --> 01:34:43.860 align:start position:0% so we have something that's going to 01:34:43.860 --> 01:34:46.550 align:start position:0% so we have something that's going to strengthen<01:34:44.520> the<01:34:44.699> rod<01:34:44.880> and<01:34:45.719> then<01:34:45.840> the<01:34:46.199> outside 01:34:46.550 --> 01:34:46.560 align:start position:0% strengthen the rod and then the outside 01:34:46.560 --> 01:34:48.290 align:start position:0% strengthen the rod and then the outside of<01:34:46.920> the<01:34:47.040> inner<01:34:47.280> strengthening<01:34:47.639> Rod<01:34:47.760> there<01:34:48.060> is 01:34:48.290 --> 01:34:48.300 align:start position:0% of the inner strengthening Rod there is 01:34:48.300 --> 01:34:51.050 align:start position:0% of the inner strengthening Rod there is filler<01:34:48.719> compound<01:34:49.320> in<01:34:50.159> between<01:34:50.280> the<01:34:50.699> strands 01:34:51.050 --> 01:34:51.060 align:start position:0% filler compound in between the strands 01:34:51.060 --> 01:34:52.129 align:start position:0% filler compound in between the strands of<01:34:51.179> cable 01:34:52.129 --> 01:34:52.139 align:start position:0% of cable 01:34:52.139 --> 01:34:53.810 align:start position:0% of cable at<01:34:52.620> the<01:34:52.739> center<01:34:52.920> of<01:34:53.219> these<01:34:53.400> individual 01:34:53.810 --> 01:34:53.820 align:start position:0% at the center of these individual 01:34:53.820 --> 01:34:56.390 align:start position:0% at the center of these individual strands<01:34:54.300> is<01:34:54.540> the<01:34:54.780> fiber<01:34:55.260> core<01:34:55.500> which<01:34:56.219> is 01:34:56.390 --> 01:34:56.400 align:start position:0% strands is the fiber core which is 01:34:56.400 --> 01:34:59.990 align:start position:0% strands is the fiber core which is between<01:34:56.880> 5<01:34:57.360> and<01:34:57.540> 100<01:34:57.920> microns<01:34:58.920> in<01:34:59.219> a<01:34:59.580> diameter 01:34:59.990 --> 01:35:00.000 align:start position:0% between 5 and 100 microns in a diameter 01:35:00.000 --> 01:35:01.550 align:start position:0% between 5 and 100 microns in a diameter and<01:35:00.120> I<01:35:00.300> don't<01:35:00.360> know<01:35:00.480> if<01:35:00.659> you<01:35:00.840> are<01:35:01.199> familiar 01:35:01.550 --> 01:35:01.560 align:start position:0% and I don't know if you are familiar 01:35:01.560 --> 01:35:03.770 align:start position:0% and I don't know if you are familiar with<01:35:01.679> that<01:35:01.860> term<01:35:02.040> Micron<01:35:02.400> but<01:35:02.699> that<01:35:02.880> is<01:35:03.179> very 01:35:03.770 --> 01:35:03.780 align:start position:0% with that term Micron but that is very 01:35:03.780 --> 01:35:06.530 align:start position:0% with that term Micron but that is very small<01:35:04.139> that's<01:35:04.920> roughly 01:35:06.530 --> 01:35:06.540 align:start position:0% small that's roughly 01:35:06.540 --> 01:35:08.570 align:start position:0% small that's roughly um<01:35:06.600> slightly<01:35:07.320> larger<01:35:07.679> than<01:35:07.920> like<01:35:08.100> I<01:35:08.219> think<01:35:08.340> a 01:35:08.570 --> 01:35:08.580 align:start position:0% um slightly larger than like I think a 01:35:08.580 --> 01:35:11.750 align:start position:0% um slightly larger than like I think a human<01:35:08.760> hair<01:35:09.179> so<01:35:10.020> just<01:35:10.380> to<01:35:10.500> give<01:35:10.620> you<01:35:10.739> a<01:35:10.980> context 01:35:11.750 --> 01:35:11.760 align:start position:0% human hair so just to give you a context 01:35:11.760 --> 01:35:12.790 align:start position:0% human hair so just to give you a context there 01:35:12.790 --> 01:35:12.800 align:start position:0% there 01:35:12.800 --> 01:35:16.370 align:start position:0% there surrounding<01:35:13.800> the<01:35:14.340> glass<01:35:14.580> or<01:35:15.000> the<01:35:15.120> core<01:35:15.380> which 01:35:16.370 --> 01:35:16.380 align:start position:0% surrounding the glass or the core which 01:35:16.380 --> 01:35:18.770 align:start position:0% surrounding the glass or the core which might<01:35:16.500> be<01:35:16.620> made<01:35:16.739> of<01:35:16.920> plastic<01:35:17.159> as<01:35:17.460> well<01:35:17.639> is<01:35:18.360> what 01:35:18.770 --> 01:35:18.780 align:start position:0% might be made of plastic as well is what 01:35:18.780 --> 01:35:20.330 align:start position:0% might be made of plastic as well is what we<01:35:18.900> call<01:35:19.080> Core<01:35:19.380> cladding<01:35:19.980> which<01:35:20.219> is 01:35:20.330 --> 01:35:20.340 align:start position:0% we call Core cladding which is 01:35:20.340 --> 01:35:22.490 align:start position:0% we call Core cladding which is responsible<01:35:20.880> for<01:35:21.239> trapping<01:35:21.719> the<01:35:21.960> light<01:35:22.139> in 01:35:22.490 --> 01:35:22.500 align:start position:0% responsible for trapping the light in 01:35:22.500 --> 01:35:24.410 align:start position:0% responsible for trapping the light in the<01:35:22.620> core<01:35:22.800> and<01:35:23.400> reflecting<01:35:23.880> it<01:35:24.060> in<01:35:24.239> a 01:35:24.410 --> 01:35:24.420 align:start position:0% the core and reflecting it in a 01:35:24.420 --> 01:35:26.510 align:start position:0% the core and reflecting it in a particular<01:35:24.719> way<01:35:24.960> depending<01:35:25.800> on<01:35:25.980> the<01:35:26.159> cable 01:35:26.510 --> 01:35:26.520 align:start position:0% particular way depending on the cable 01:35:26.520 --> 01:35:28.610 align:start position:0% particular way depending on the cable mode<01:35:26.820> and<01:35:27.600> on<01:35:27.780> the<01:35:27.900> outside<01:35:28.080> of<01:35:28.380> the<01:35:28.500> course 01:35:28.610 --> 01:35:28.620 align:start position:0% mode and on the outside of the course 01:35:28.620 --> 01:35:31.129 align:start position:0% mode and on the outside of the course cladding<01:35:29.219> there's<01:35:29.400> a<01:35:29.639> buffer<01:35:30.000> that<01:35:30.719> is<01:35:30.840> color 01:35:31.129 --> 01:35:31.139 align:start position:0% cladding there's a buffer that is color 01:35:31.139 --> 01:35:33.830 align:start position:0% cladding there's a buffer that is color coded<01:35:31.679> so<01:35:31.920> a<01:35:32.100> technician<01:35:32.580> knows<01:35:33.060> which<01:35:33.480> strand 01:35:33.830 --> 01:35:33.840 align:start position:0% coded so a technician knows which strand 01:35:33.840 --> 01:35:35.629 align:start position:0% coded so a technician knows which strand they're<01:35:34.199> working<01:35:34.380> on 01:35:35.629 --> 01:35:35.639 align:start position:0% they're working on 01:35:35.639 --> 01:35:37.970 align:start position:0% they're working on next<01:35:36.179> we<01:35:36.420> have<01:35:36.600> strengthening<01:35:37.320> fibers<01:35:37.739> that 01:35:37.970 --> 01:35:37.980 align:start position:0% next we have strengthening fibers that 01:35:37.980 --> 01:35:39.830 align:start position:0% next we have strengthening fibers that are<01:35:38.100> typically<01:35:38.340> made<01:35:38.639> from<01:35:39.120> very<01:35:39.540> strong 01:35:39.830 --> 01:35:39.840 align:start position:0% are typically made from very strong 01:35:39.840 --> 01:35:42.530 align:start position:0% are typically made from very strong material<01:35:40.440> and<01:35:41.280> finally<01:35:41.580> on<01:35:41.820> the<01:35:41.940> outside<01:35:42.120> is 01:35:42.530 --> 01:35:42.540 align:start position:0% material and finally on the outside is 01:35:42.540 --> 01:35:44.689 align:start position:0% material and finally on the outside is an<01:35:42.780> outer<01:35:43.080> protective<01:35:43.560> layer<01:35:43.920> called<01:35:44.280> the 01:35:44.689 --> 01:35:44.699 align:start position:0% an outer protective layer called the 01:35:44.699 --> 01:35:48.310 align:start position:0% an outer protective layer called the jacket<01:35:45.060> the<01:35:46.020> transmission<01:35:46.320> method<01:35:47.159> again 01:35:48.310 --> 01:35:48.320 align:start position:0% jacket the transmission method again 01:35:48.320 --> 01:35:50.990 align:start position:0% jacket the transmission method again utilizes<01:35:49.320> pulses<01:35:49.860> of<01:35:50.100> light 01:35:50.990 --> 01:35:51.000 align:start position:0% utilizes pulses of light 01:35:51.000 --> 01:35:54.470 align:start position:0% utilizes pulses of light these<01:35:51.780> lights<01:35:51.960> can<01:35:52.560> come<01:35:52.800> from<01:35:53.219> LEDs<01:35:54.060> or<01:35:54.239> light 01:35:54.470 --> 01:35:54.480 align:start position:0% these lights can come from LEDs or light 01:35:54.480 --> 01:35:56.990 align:start position:0% these lights can come from LEDs or light emitting<01:35:54.960> diodes<01:35:55.320> in<01:35:55.920> cases<01:35:56.280> where<01:35:56.580> there<01:35:56.820> is 01:35:56.990 --> 01:35:57.000 align:start position:0% emitting diodes in cases where there is 01:35:57.000 --> 01:35:59.810 align:start position:0% emitting diodes in cases where there is a<01:35:57.179> slower<01:35:57.420> Network<01:35:57.860> or<01:35:58.860> in<01:35:59.100> network<01:35:59.280> with<01:35:59.580> a 01:35:59.810 --> 01:35:59.820 align:start position:0% a slower Network or in network with a 01:35:59.820 --> 01:36:01.310 align:start position:0% a slower Network or in network with a much<01:35:59.940> faster<01:36:00.420> connection<01:36:00.659> we<01:36:01.020> might<01:36:01.199> even 01:36:01.310 --> 01:36:01.320 align:start position:0% much faster connection we might even 01:36:01.320 --> 01:36:03.290 align:start position:0% much faster connection we might even have<01:36:01.620> a<01:36:01.980> laser 01:36:03.290 --> 01:36:03.300 align:start position:0% have a laser 01:36:03.300 --> 01:36:05.450 align:start position:0% have a laser now<01:36:03.659> there<01:36:03.960> are<01:36:04.080> different<01:36:04.320> types<01:36:04.920> of<01:36:05.040> fiber 01:36:05.450 --> 01:36:05.460 align:start position:0% now there are different types of fiber 01:36:05.460 --> 01:36:07.790 align:start position:0% now there are different types of fiber modes<01:36:05.880> and<01:36:06.120> as<01:36:06.300> an<01:36:06.480> as<01:36:06.960> a<01:36:07.199> network<01:36:07.440> plus 01:36:07.790 --> 01:36:07.800 align:start position:0% modes and as an as a network plus 01:36:07.800 --> 01:36:09.770 align:start position:0% modes and as an as a network plus administrator<01:36:08.639> you<01:36:09.060> need<01:36:09.179> to<01:36:09.300> be<01:36:09.420> familiar 01:36:09.770 --> 01:36:09.780 align:start position:0% administrator you need to be familiar 01:36:09.780 --> 01:36:11.990 align:start position:0% administrator you need to be familiar with<01:36:10.139> the<01:36:10.500> different<01:36:10.800> methods<01:36:11.460> of 01:36:11.990 --> 01:36:12.000 align:start position:0% with the different methods of 01:36:12.000 --> 01:36:13.790 align:start position:0% with the different methods of transmission<01:36:12.239> for<01:36:12.780> each 01:36:13.790 --> 01:36:13.800 align:start position:0% transmission for each 01:36:13.800 --> 01:36:17.209 align:start position:0% transmission for each in<01:36:14.400> single<01:36:14.760> mode<01:36:14.880> fiber<01:36:15.480> only<01:36:16.440> one<01:36:16.860> single 01:36:17.209 --> 01:36:17.219 align:start position:0% in single mode fiber only one single 01:36:17.219 --> 01:36:19.070 align:start position:0% in single mode fiber only one single beam<01:36:17.520> of<01:36:17.639> light<01:36:17.820> passes<01:36:18.540> through<01:36:18.719> the<01:36:18.960> core 01:36:19.070 --> 01:36:19.080 align:start position:0% beam of light passes through the core 01:36:19.080 --> 01:36:21.470 align:start position:0% beam of light passes through the core now<01:36:20.040> a<01:36:20.159> bandwidth<01:36:20.639> of<01:36:20.760> up<01:36:20.940> to<01:36:21.060> about<01:36:21.239> 30 01:36:21.470 --> 01:36:21.480 align:start position:0% now a bandwidth of up to about 30 01:36:21.480 --> 01:36:24.350 align:start position:0% now a bandwidth of up to about 30 megahertz<01:36:22.080> megahertz<01:36:22.860> can<01:36:23.400> be<01:36:23.639> reached<01:36:24.060> and 01:36:24.350 --> 01:36:24.360 align:start position:0% megahertz megahertz can be reached and 01:36:24.360 --> 01:36:28.430 align:start position:0% megahertz megahertz can be reached and the<01:36:24.480> signal<01:36:24.840> is<01:36:25.500> modulated<01:36:26.280> by<01:36:27.239> intensity<01:36:27.780> to 01:36:28.430 --> 01:36:28.440 align:start position:0% the signal is modulated by intensity to 01:36:28.440 --> 01:36:30.290 align:start position:0% the signal is modulated by intensity to transmit<01:36:28.980> data<01:36:29.340> so<01:36:29.699> the<01:36:29.880> intensity 01:36:30.290 --> 01:36:30.300 align:start position:0% transmit data so the intensity 01:36:30.300 --> 01:36:31.910 align:start position:0% transmit data so the intensity determines<01:36:30.840> the<01:36:31.080> data 01:36:31.910 --> 01:36:31.920 align:start position:0% determines the data 01:36:31.920 --> 01:36:34.610 align:start position:0% determines the data with<01:36:32.760> the<01:36:33.179> next<01:36:33.239> thing<01:36:33.360> we<01:36:33.540> look<01:36:33.719> at<01:36:33.840> is<01:36:34.139> Step 01:36:34.610 --> 01:36:34.620 align:start position:0% with the next thing we look at is Step 01:36:34.620 --> 01:36:37.790 align:start position:0% with the next thing we look at is Step index<01:36:35.219> multi-mode<01:36:36.120> fiber<01:36:36.659> the<01:36:37.320> core<01:36:37.440> of<01:36:37.679> the 01:36:37.790 --> 01:36:37.800 align:start position:0% index multi-mode fiber the core of the 01:36:37.800 --> 01:36:39.770 align:start position:0% index multi-mode fiber the core of the fiber<01:36:38.159> and<01:36:38.460> the<01:36:38.580> clouding<01:36:38.940> surrounded<01:36:39.600> it 01:36:39.770 --> 01:36:39.780 align:start position:0% fiber and the clouding surrounded it 01:36:39.780 --> 01:36:41.750 align:start position:0% fiber and the clouding surrounded it surrounding<01:36:40.500> it<01:36:40.679> rather<01:36:40.920> have<01:36:41.460> different 01:36:41.750 --> 01:36:41.760 align:start position:0% surrounding it rather have different 01:36:41.760 --> 01:36:43.669 align:start position:0% surrounding it rather have different indices<01:36:42.540> by<01:36:43.199> the<01:36:43.320> way<01:36:43.380> if<01:36:43.500> you're<01:36:43.620> not 01:36:43.669 --> 01:36:43.679 align:start position:0% indices by the way if you're not 01:36:43.679 --> 01:36:44.750 align:start position:0% indices by the way if you're not familiar<01:36:43.920> with<01:36:44.040> that<01:36:44.219> word<01:36:44.340> that's<01:36:44.520> the 01:36:44.750 --> 01:36:44.760 align:start position:0% familiar with that word that's the 01:36:44.760 --> 01:36:48.229 align:start position:0% familiar with that word that's the plural<01:36:45.120> for<01:36:45.360> index<01:36:46.020> of<01:36:46.620> refraction<01:36:47.100> if<01:36:48.060> that's 01:36:48.229 --> 01:36:48.239 align:start position:0% plural for index of refraction if that's 01:36:48.239 --> 01:36:50.510 align:start position:0% plural for index of refraction if that's a<01:36:48.480> little<01:36:48.540> confusing<01:36:49.020> that<01:36:49.380> means<01:36:49.860> that<01:36:50.340> they 01:36:50.510 --> 01:36:50.520 align:start position:0% a little confusing that means that they 01:36:50.520 --> 01:36:53.330 align:start position:0% a little confusing that means that they have<01:36:50.699> different<01:36:50.940> densities<01:36:51.679> which<01:36:52.679> changes 01:36:53.330 --> 01:36:53.340 align:start position:0% have different densities which changes 01:36:53.340 --> 01:36:55.490 align:start position:0% have different densities which changes the<01:36:53.639> speed<01:36:53.820> and<01:36:54.060> velocity<01:36:54.540> of<01:36:54.840> the<01:36:55.020> light<01:36:55.139> that 01:36:55.490 --> 01:36:55.500 align:start position:0% the speed and velocity of the light that 01:36:55.500 --> 01:36:57.410 align:start position:0% the speed and velocity of the light that travels<01:36:55.800> through<01:36:55.980> the<01:36:56.159> medium<01:36:56.460> so<01:36:57.120> when<01:36:57.300> the 01:36:57.410 --> 01:36:57.420 align:start position:0% travels through the medium so when the 01:36:57.420 --> 01:36:59.990 align:start position:0% travels through the medium so when the velocity<01:36:57.840> changes<01:36:58.440> it's<01:36:58.800> called<01:36:59.159> the<01:36:59.760> step 01:36:59.990 --> 01:37:00.000 align:start position:0% velocity changes it's called the step 01:37:00.000 --> 01:37:03.649 align:start position:0% velocity changes it's called the step down<01:37:00.360> this<01:37:00.960> is<01:37:01.080> why<01:37:01.260> we<01:37:01.440> have<01:37:01.679> step<01:37:02.280> index 01:37:03.649 --> 01:37:03.659 align:start position:0% down this is why we have step index 01:37:03.659 --> 01:37:06.050 align:start position:0% down this is why we have step index finally<01:37:04.440> we<01:37:04.739> have<01:37:04.920> something<01:37:05.040> called<01:37:05.340> graded 01:37:06.050 --> 01:37:06.060 align:start position:0% finally we have something called graded 01:37:06.060 --> 01:37:08.990 align:start position:0% finally we have something called graded index<01:37:06.480> multi-mode<01:37:07.080> fiber<01:37:07.500> this<01:37:08.340> has<01:37:08.580> a<01:37:08.820> core 01:37:08.990 --> 01:37:09.000 align:start position:0% index multi-mode fiber this has a core 01:37:09.000 --> 01:37:12.050 align:start position:0% index multi-mode fiber this has a core glass<01:37:09.360> a<01:37:10.020> glass<01:37:10.440> core<01:37:10.679> rather<01:37:11.040> that<01:37:11.699> itself 01:37:12.050 --> 01:37:12.060 align:start position:0% glass a glass core rather that itself 01:37:12.060 --> 01:37:14.270 align:start position:0% glass a glass core rather that itself has<01:37:12.659> differences<01:37:13.080> in<01:37:13.320> variations<01:37:13.739> in<01:37:14.159> the 01:37:14.270 --> 01:37:14.280 align:start position:0% has differences in variations in the 01:37:14.280 --> 01:37:16.490 align:start position:0% has differences in variations in the form<01:37:14.460> and<01:37:15.120> that<01:37:15.239> allows<01:37:15.600> for<01:37:15.840> a<01:37:16.020> large<01:37:16.199> amount 01:37:16.490 --> 01:37:16.500 align:start position:0% form and that allows for a large amount 01:37:16.500 --> 01:37:18.290 align:start position:0% form and that allows for a large amount of<01:37:16.620> bandwidth<01:37:17.219> that<01:37:17.580> reaches<01:37:17.940> up<01:37:18.060> to<01:37:18.179> about 01:37:18.290 --> 01:37:18.300 align:start position:0% of bandwidth that reaches up to about 01:37:18.300 --> 01:37:20.570 align:start position:0% of bandwidth that reaches up to about two<01:37:18.719> gigahertz 01:37:20.570 --> 01:37:20.580 align:start position:0% two gigahertz 01:37:20.580 --> 01:37:21.770 align:start position:0% two gigahertz now<01:37:20.880> the<01:37:21.060> thing<01:37:21.179> I<01:37:21.300> want<01:37:21.420> you<01:37:21.540> to<01:37:21.659> remember 01:37:21.770 --> 01:37:21.780 align:start position:0% now the thing I want you to remember 01:37:21.780 --> 01:37:24.110 align:start position:0% now the thing I want you to remember most<01:37:22.260> about<01:37:22.560> single<01:37:23.040> mode<01:37:23.159> versus<01:37:23.400> multi-mode 01:37:24.110 --> 01:37:24.120 align:start position:0% most about single mode versus multi-mode 01:37:24.120 --> 01:37:25.970 align:start position:0% most about single mode versus multi-mode I<01:37:24.840> wouldn't<01:37:24.960> worry<01:37:25.199> so<01:37:25.440> much<01:37:25.560> about<01:37:25.739> the 01:37:25.970 --> 01:37:25.980 align:start position:0% I wouldn't worry so much about the 01:37:25.980 --> 01:37:27.890 align:start position:0% I wouldn't worry so much about the graded<01:37:26.400> index<01:37:26.639> and<01:37:26.880> step<01:37:27.060> index<01:37:27.420> but<01:37:27.600> what<01:37:27.719> you 01:37:27.890 --> 01:37:27.900 align:start position:0% graded index and step index but what you 01:37:27.900 --> 01:37:29.870 align:start position:0% graded index and step index but what you do<01:37:28.020> want<01:37:28.139> to<01:37:28.320> remember<01:37:28.440> is<01:37:29.100> that<01:37:29.280> single<01:37:29.699> mode 01:37:29.870 --> 01:37:29.880 align:start position:0% do want to remember is that single mode 01:37:29.880 --> 01:37:33.649 align:start position:0% do want to remember is that single mode is<01:37:30.659> good<01:37:30.960> for<01:37:31.440> longer<01:37:32.100> distances<01:37:32.639> but<01:37:33.300> not<01:37:33.480> as 01:37:33.649 --> 01:37:33.659 align:start position:0% is good for longer distances but not as 01:37:33.659 --> 01:37:35.870 align:start position:0% is good for longer distances but not as high<01:37:33.840> transfer<01:37:34.320> speeds<01:37:34.739> multi-mode<01:37:35.580> is<01:37:35.760> good 01:37:35.870 --> 01:37:35.880 align:start position:0% high transfer speeds multi-mode is good 01:37:35.880 --> 01:37:39.350 align:start position:0% high transfer speeds multi-mode is good for<01:37:36.060> short<01:37:36.300> distances<01:37:36.980> and<01:37:37.980> uh<01:37:38.760> higher 01:37:39.350 --> 01:37:39.360 align:start position:0% for short distances and uh higher 01:37:39.360 --> 01:37:40.910 align:start position:0% for short distances and uh higher transfer<01:37:39.719> speeds<01:37:40.020> think<01:37:40.199> about<01:37:40.380> it<01:37:40.560> this<01:37:40.739> way 01:37:40.910 --> 01:37:40.920 align:start position:0% transfer speeds think about it this way 01:37:40.920 --> 01:37:44.689 align:start position:0% transfer speeds think about it this way if<01:37:41.520> I<01:37:41.699> have<01:37:41.940> a<01:37:42.360> very<01:37:42.420> large<01:37:42.719> bus<01:37:43.460> I'm<01:37:44.460> going<01:37:44.580> to 01:37:44.689 --> 01:37:44.699 align:start position:0% if I have a very large bus I'm going to 01:37:44.699 --> 01:37:48.410 align:start position:0% if I have a very large bus I'm going to be<01:37:44.760> able<01:37:44.880> to<01:37:45.000> carry<01:37:45.360> more<01:37:45.719> people<01:37:46.280> uh<01:37:47.280> in<01:37:47.520> a<01:37:47.760> in 01:37:48.410 --> 01:37:48.420 align:start position:0% be able to carry more people uh in a in 01:37:48.420 --> 01:37:50.990 align:start position:0% be able to carry more people uh in a in a<01:37:48.540> shorter<01:37:48.840> distance<01:37:49.080> if<01:37:49.860> I<01:37:50.040> have<01:37:50.280> a<01:37:50.820> sports 01:37:50.990 --> 01:37:51.000 align:start position:0% a shorter distance if I have a sports 01:37:51.000 --> 01:37:53.090 align:start position:0% a shorter distance if I have a sports car<01:37:51.360> I<01:37:51.840> might<01:37:51.960> be<01:37:52.080> able<01:37:52.199> to<01:37:52.260> carry<01:37:52.560> one<01:37:52.920> person 01:37:53.090 --> 01:37:53.100 align:start position:0% car I might be able to carry one person 01:37:53.100 --> 01:37:55.209 align:start position:0% car I might be able to carry one person or<01:37:53.460> two<01:37:53.580> people<01:37:53.940> but<01:37:54.179> we'll<01:37:54.360> go<01:37:54.540> a<01:37:54.719> lot<01:37:54.840> faster 01:37:55.209 --> 01:37:55.219 align:start position:0% or two people but we'll go a lot faster 01:37:55.219 --> 01:37:58.669 align:start position:0% or two people but we'll go a lot faster so<01:37:56.219> you<01:37:56.580> can<01:37:56.699> think<01:37:56.820> about<01:37:56.940> it<01:37:57.179> that<01:37:57.360> way 01:37:58.669 --> 01:37:58.679 align:start position:0% so you can think about it that way 01:37:58.679 --> 01:38:02.030 align:start position:0% so you can think about it that way now<01:37:59.460> St<01:37:59.940> connectors<01:38:00.659> or<01:38:01.139> straight<01:38:01.560> tip 01:38:02.030 --> 01:38:02.040 align:start position:0% now St connectors or straight tip 01:38:02.040 --> 01:38:03.830 align:start position:0% now St connectors or straight tip connectors<01:38:02.460> are<01:38:02.940> one<01:38:03.120> of<01:38:03.239> the<01:38:03.360> most<01:38:03.480> common 01:38:03.830 --> 01:38:03.840 align:start position:0% connectors are one of the most common 01:38:03.840 --> 01:38:06.050 align:start position:0% connectors are one of the most common you're<01:38:04.139> going<01:38:04.320> to<01:38:04.380> see<01:38:04.500> today<01:38:04.739> they<01:38:05.520> look<01:38:05.699> very 01:38:06.050 --> 01:38:06.060 align:start position:0% you're going to see today they look very 01:38:06.060 --> 01:38:09.590 align:start position:0% you're going to see today they look very similar<01:38:06.540> to<01:38:06.840> the<01:38:07.020> coaxial<01:38:07.560> BNC<01:38:08.219> connector<01:38:08.760> and 01:38:09.590 --> 01:38:09.600 align:start position:0% similar to the coaxial BNC connector and 01:38:09.600 --> 01:38:11.629 align:start position:0% similar to the coaxial BNC connector and uh<01:38:10.080> one<01:38:10.620> way<01:38:10.739> you<01:38:10.860> can<01:38:10.980> remember<01:38:11.100> it<01:38:11.340> is<01:38:11.460> you 01:38:11.629 --> 01:38:11.639 align:start position:0% uh one way you can remember it is you 01:38:11.639 --> 01:38:13.490 align:start position:0% uh one way you can remember it is you have<01:38:11.760> to<01:38:11.880> twist<01:38:12.420> them<01:38:12.719> on<01:38:12.900> and<01:38:13.139> I<01:38:13.260> think<01:38:13.380> about 01:38:13.490 --> 01:38:13.500 align:start position:0% have to twist them on and I think about 01:38:13.500 --> 01:38:16.970 align:start position:0% have to twist them on and I think about that<01:38:13.860> t<01:38:14.159> for<01:38:14.460> Twist<01:38:14.940> the<01:38:15.900> SC<01:38:16.139> or<01:38:16.620> otherwise 01:38:16.970 --> 01:38:16.980 align:start position:0% that t for Twist the SC or otherwise 01:38:16.980 --> 01:38:19.370 align:start position:0% that t for Twist the SC or otherwise known<01:38:17.219> as<01:38:17.340> a<01:38:17.520> subscriber<01:38:18.120> connector<01:38:18.600> is<01:38:19.080> also 01:38:19.370 --> 01:38:19.380 align:start position:0% known as a subscriber connector is also 01:38:19.380 --> 01:38:21.110 align:start position:0% known as a subscriber connector is also one<01:38:19.560> of<01:38:19.620> the<01:38:19.739> most<01:38:19.860> common<01:38:20.100> connectors<01:38:20.699> so<01:38:20.940> you 01:38:21.110 --> 01:38:21.120 align:start position:0% one of the most common connectors so you 01:38:21.120 --> 01:38:23.209 align:start position:0% one of the most common connectors so you want<01:38:21.300> to<01:38:21.480> recognize<01:38:21.840> that<01:38:22.139> one<01:38:22.260> as<01:38:22.440> well 01:38:23.209 --> 01:38:23.219 align:start position:0% want to recognize that one as well 01:38:23.219 --> 01:38:25.010 align:start position:0% want to recognize that one as well we<01:38:23.699> also<01:38:23.880> have<01:38:24.000> something<01:38:24.120> called<01:38:24.420> the<01:38:24.659> LC 01:38:25.010 --> 01:38:25.020 align:start position:0% we also have something called the LC 01:38:25.020 --> 01:38:27.410 align:start position:0% we also have something called the LC connector<01:38:25.560> which<01:38:26.280> looks<01:38:26.880> almost<01:38:27.000> like<01:38:27.239> an 01:38:27.410 --> 01:38:27.420 align:start position:0% connector which looks almost like an 01:38:27.420 --> 01:38:30.229 align:start position:0% connector which looks almost like an RJ45<01:38:28.199> type<01:38:28.500> connector<01:38:28.980> and<01:38:29.280> it<01:38:29.460> snaps<01:38:30.000> in 01:38:30.229 --> 01:38:30.239 align:start position:0% RJ45 type connector and it snaps in 01:38:30.239 --> 01:38:32.330 align:start position:0% RJ45 type connector and it snaps in place<01:38:30.420> it's<01:38:30.960> also<01:38:31.260> about<01:38:31.380> half<01:38:31.739> the<01:38:31.980> size<01:38:32.159> of 01:38:32.330 --> 01:38:32.340 align:start position:0% place it's also about half the size of 01:38:32.340 --> 01:38:34.490 align:start position:0% place it's also about half the size of an<01:38:32.520> st<01:38:32.699> and<01:38:33.060> SC<01:38:33.239> connector 01:38:34.490 --> 01:38:34.500 align:start position:0% an st and SC connector 01:38:34.500 --> 01:38:36.169 align:start position:0% an st and SC connector I<01:38:35.100> also<01:38:35.460> want<01:38:35.580> to<01:38:35.699> show<01:38:35.760> you<01:38:35.820> some<01:38:36.000> of<01:38:36.120> the 01:38:36.169 --> 01:38:36.179 align:start position:0% I also want to show you some of the 01:38:36.179 --> 01:38:37.490 align:start position:0% I also want to show you some of the other<01:38:36.300> connectors<01:38:36.719> that<01:38:36.900> are<01:38:37.020> listed<01:38:37.260> on<01:38:37.380> the 01:38:37.490 --> 01:38:37.500 align:start position:0% other connectors that are listed on the 01:38:37.500 --> 01:38:38.810 align:start position:0% other connectors that are listed on the outline<01:38:37.739> although<01:38:38.040> I<01:38:38.159> don't<01:38:38.280> see<01:38:38.460> them<01:38:38.639> much 01:38:38.810 --> 01:38:38.820 align:start position:0% outline although I don't see them much 01:38:38.820 --> 01:38:42.050 align:start position:0% outline although I don't see them much on<01:38:39.000> the<01:38:39.120> exam<01:38:39.420> uh<01:38:40.320> an<01:38:40.560> mtrj<01:38:41.219> or<01:38:41.520> mechanical 01:38:42.050 --> 01:38:42.060 align:start position:0% on the exam uh an mtrj or mechanical 01:38:42.060 --> 01:38:44.870 align:start position:0% on the exam uh an mtrj or mechanical transfer<01:38:42.900> register<01:38:43.320> Jack<01:38:43.679> which<01:38:44.520> is<01:38:44.639> also 01:38:44.870 --> 01:38:44.880 align:start position:0% transfer register Jack which is also 01:38:44.880 --> 01:38:47.990 align:start position:0% transfer register Jack which is also called<01:38:45.120> a<01:38:45.480> fiber<01:38:45.840> Jack<01:38:45.960> it's<01:38:46.620> it's<01:38:46.920> again<01:38:47.639> just 01:38:47.990 --> 01:38:48.000 align:start position:0% called a fiber Jack it's it's again just 01:38:48.000 --> 01:38:50.510 align:start position:0% called a fiber Jack it's it's again just like<01:38:48.120> the<01:38:48.360> same<01:38:48.480> size<01:38:48.719> as<01:38:48.900> an<01:38:49.020> RJ45<01:38:49.739> and<01:38:50.340> it's 01:38:50.510 --> 01:38:50.520 align:start position:0% like the same size as an RJ45 and it's 01:38:50.520 --> 01:38:52.669 align:start position:0% like the same size as an RJ45 and it's usually<01:38:50.940> used<01:38:51.179> to<01:38:51.480> connect<01:38:51.659> two<01:38:52.080> strands<01:38:52.500> of 01:38:52.669 --> 01:38:52.679 align:start position:0% usually used to connect two strands of 01:38:52.679 --> 01:38:54.169 align:start position:0% usually used to connect two strands of fiber<01:38:53.100> together 01:38:54.169 --> 01:38:54.179 align:start position:0% fiber together 01:38:54.179 --> 01:38:57.110 align:start position:0% fiber together there's<01:38:54.659> also<01:38:54.960> a<01:38:55.080> few<01:38:55.199> other<01:38:55.380> connectors<01:38:56.120> uh 01:38:57.110 --> 01:38:57.120 align:start position:0% there's also a few other connectors uh 01:38:57.120 --> 01:39:00.709 align:start position:0% there's also a few other connectors uh FC<01:38:57.900> which<01:38:58.260> is<01:38:58.380> face<01:38:58.620> contact<01:38:59.060> uh<01:39:00.060> it's<01:39:00.239> used<01:39:00.480> in 01:39:00.709 --> 01:39:00.719 align:start position:0% FC which is face contact uh it's used in 01:39:00.719 --> 01:39:04.070 align:start position:0% FC which is face contact uh it's used in industrial<01:39:01.199> environments<01:39:01.980> uh<01:39:02.820> it<01:39:03.120> has<01:39:03.360> a 01:39:04.070 --> 01:39:04.080 align:start position:0% industrial environments uh it has a 01:39:04.080 --> 01:39:05.990 align:start position:0% industrial environments uh it has a different<01:39:04.560> Center<01:39:04.980> that<01:39:05.460> sort<01:39:05.639> of<01:39:05.699> gives<01:39:05.880> it 01:39:05.990 --> 01:39:06.000 align:start position:0% different Center that sort of gives it 01:39:06.000 --> 01:39:08.030 align:start position:0% different Center that sort of gives it more<01:39:06.300> strength<01:39:06.780> there's<01:39:07.320> also<01:39:07.560> something<01:39:07.800> in 01:39:08.030 --> 01:39:08.040 align:start position:0% more strength there's also something in 01:39:08.040 --> 01:39:10.070 align:start position:0% more strength there's also something in this<01:39:08.219> this<01:39:08.400> you<01:39:08.639> will<01:39:08.820> see<01:39:09.000> is<01:39:09.239> called<01:39:09.480> fuddy 01:39:10.070 --> 01:39:10.080 align:start position:0% this this you will see is called fuddy 01:39:10.080 --> 01:39:12.590 align:start position:0% this this you will see is called fuddy or<01:39:10.620> Fiber<01:39:11.100> distributed<01:39:11.639> data<01:39:12.120> interface 01:39:12.590 --> 01:39:12.600 align:start position:0% or Fiber distributed data interface 01:39:12.600 --> 01:39:16.310 align:start position:0% or Fiber distributed data interface which<01:39:13.199> can<01:39:13.320> also<01:39:13.560> be<01:39:13.679> called<01:39:13.920> uh<01:39:14.400> mic<01:39:15.179> or<01:39:15.480> SMA 01:39:16.310 --> 01:39:16.320 align:start position:0% which can also be called uh mic or SMA 01:39:16.320 --> 01:39:18.350 align:start position:0% which can also be called uh mic or SMA or<01:39:16.620> sub<01:39:16.920> miniature<01:39:17.520> assembly<01:39:17.880> all<01:39:18.239> these 01:39:18.350 --> 01:39:18.360 align:start position:0% or sub miniature assembly all these 01:39:18.360 --> 01:39:20.570 align:start position:0% or sub miniature assembly all these different<01:39:18.540> names<01:39:18.840> it's<01:39:19.560> an<01:39:19.739> older<01:39:20.100> connector 01:39:20.570 --> 01:39:20.580 align:start position:0% different names it's an older connector 01:39:20.580 --> 01:39:23.149 align:start position:0% different names it's an older connector and<01:39:21.239> it's<01:39:21.480> uh<01:39:21.719> one<01:39:22.080> of<01:39:22.199> the<01:39:22.560> original 01:39:23.149 --> 01:39:23.159 align:start position:0% and it's uh one of the original 01:39:23.159 --> 01:39:26.390 align:start position:0% and it's uh one of the original connectors<01:39:24.000> that<01:39:24.659> was<01:39:24.840> used 01:39:26.390 --> 01:39:26.400 align:start position:0% connectors that was used 01:39:26.400 --> 01:39:27.950 align:start position:0% connectors that was used now<01:39:27.179> because<01:39:27.420> of<01:39:27.659> the<01:39:27.840> different 01:39:27.950 --> 01:39:27.960 align:start position:0% now because of the different 01:39:27.960 --> 01:39:29.629 align:start position:0% now because of the different technologies<01:39:28.679> that<01:39:28.980> are<01:39:29.100> available<01:39:29.159> for 01:39:29.629 --> 01:39:29.639 align:start position:0% technologies that are available for 01:39:29.639 --> 01:39:32.570 align:start position:0% technologies that are available for networks<01:39:30.000> today<01:39:30.500> it<01:39:31.500> may<01:39:31.739> become<01:39:32.159> necessary 01:39:32.570 --> 01:39:32.580 align:start position:0% networks today it may become necessary 01:39:32.580 --> 01:39:34.250 align:start position:0% networks today it may become necessary to<01:39:32.820> go<01:39:32.940> from<01:39:33.120> one<01:39:33.360> type<01:39:33.480> of<01:39:33.600> medium<01:39:33.900> to<01:39:34.139> the 01:39:34.250 --> 01:39:34.260 align:start position:0% to go from one type of medium to the 01:39:34.260 --> 01:39:36.410 align:start position:0% to go from one type of medium to the other<01:39:34.380> in<01:39:35.159> some<01:39:35.280> of<01:39:35.400> these<01:39:35.580> cases<01:39:35.880> we<01:39:36.179> have<01:39:36.300> to 01:39:36.410 --> 01:39:36.420 align:start position:0% other in some of these cases we have to 01:39:36.420 --> 01:39:38.629 align:start position:0% other in some of these cases we have to utilize<01:39:36.960> what's<01:39:37.440> called<01:39:37.679> a<01:39:37.860> media<01:39:38.219> converter 01:39:38.629 --> 01:39:38.639 align:start position:0% utilize what's called a media converter 01:39:38.639 --> 01:39:40.490 align:start position:0% utilize what's called a media converter here<01:39:39.420> are<01:39:39.600> a<01:39:39.659> couple<01:39:39.780> common<01:39:40.080> media 01:39:40.490 --> 01:39:40.500 align:start position:0% here are a couple common media 01:39:40.500 --> 01:39:42.050 align:start position:0% here are a couple common media converters<01:39:40.860> you<01:39:41.040> may<01:39:41.159> have<01:39:41.280> come<01:39:41.460> across<01:39:41.820> in 01:39:42.050 --> 01:39:42.060 align:start position:0% converters you may have come across in 01:39:42.060 --> 01:39:43.970 align:start position:0% converters you may have come across in certain<01:39:42.239> networking<01:39:42.719> environments 01:39:43.970 --> 01:39:43.980 align:start position:0% certain networking environments 01:39:43.980 --> 01:39:45.890 align:start position:0% certain networking environments now<01:39:44.340> there<01:39:44.580> are<01:39:44.699> media<01:39:45.120> converters<01:39:45.600> that 01:39:45.890 --> 01:39:45.900 align:start position:0% now there are media converters that 01:39:45.900 --> 01:39:48.350 align:start position:0% now there are media converters that convert<01:39:46.260> signals<01:39:46.800> on<01:39:47.100> fiber<01:39:47.520> to<01:39:47.760> coaxial 01:39:48.350 --> 01:39:48.360 align:start position:0% convert signals on fiber to coaxial 01:39:48.360 --> 01:39:50.750 align:start position:0% convert signals on fiber to coaxial cable<01:39:48.719> when<01:39:49.139> you're<01:39:49.320> converting 01:39:50.750 --> 01:39:50.760 align:start position:0% cable when you're converting 01:39:50.760 --> 01:39:52.270 align:start position:0% cable when you're converting um 01:39:52.270 --> 01:39:52.280 align:start position:0% um 01:39:52.280 --> 01:39:55.550 align:start position:0% um multi-mode<01:39:53.280> fiber<01:39:53.820> into<01:39:54.239> ethernet<01:39:55.080> in<01:39:55.440> order 01:39:55.550 --> 01:39:55.560 align:start position:0% multi-mode fiber into ethernet in order 01:39:55.560 --> 01:39:57.770 align:start position:0% multi-mode fiber into ethernet in order to<01:39:55.739> extend<01:39:56.100> the<01:39:56.280> ethernet<01:39:56.760> network<01:39:57.000> over<01:39:57.480> a 01:39:57.770 --> 01:39:57.780 align:start position:0% to extend the ethernet network over a 01:39:57.780 --> 01:40:01.070 align:start position:0% to extend the ethernet network over a fiber<01:39:58.260> backbone<01:39:58.800> we<01:39:59.699> also<01:39:59.940> have<01:40:00.120> similar<01:40:00.900> to 01:40:01.070 --> 01:40:01.080 align:start position:0% fiber backbone we also have similar to 01:40:01.080 --> 01:40:03.350 align:start position:0% fiber backbone we also have similar to multi-mode<01:40:01.679> fiber<01:40:02.280> there<01:40:03.060> are<01:40:03.179> also 01:40:03.350 --> 01:40:03.360 align:start position:0% multi-mode fiber there are also 01:40:03.360 --> 01:40:04.970 align:start position:0% multi-mode fiber there are also converters<01:40:03.840> that<01:40:04.139> go<01:40:04.380> from<01:40:04.620> single<01:40:04.920> mode 01:40:04.970 --> 01:40:04.980 align:start position:0% converters that go from single mode 01:40:04.980 --> 01:40:07.430 align:start position:0% converters that go from single mode fiber<01:40:05.400> to<01:40:05.520> ethernet<01:40:06.000> as<01:40:06.600> well<01:40:06.780> which<01:40:07.080> is<01:40:07.260> for 01:40:07.430 --> 01:40:07.440 align:start position:0% fiber to ethernet as well which is for 01:40:07.440 --> 01:40:09.110 align:start position:0% fiber to ethernet as well which is for the<01:40:07.620> same<01:40:07.739> purpose<01:40:08.159> generally<01:40:08.880> speaking 01:40:09.110 --> 01:40:09.120 align:start position:0% the same purpose generally speaking 01:40:09.120 --> 01:40:10.669 align:start position:0% the same purpose generally speaking we're<01:40:09.300> going<01:40:09.420> to<01:40:09.480> see<01:40:09.600> more<01:40:09.780> multi-mode<01:40:10.380> in 01:40:10.669 --> 01:40:10.679 align:start position:0% we're going to see more multi-mode in 01:40:10.679 --> 01:40:11.990 align:start position:0% we're going to see more multi-mode in the<01:40:10.800> backbone<01:40:11.100> environment<01:40:11.520> because<01:40:11.699> it's<01:40:11.880> a 01:40:11.990 --> 01:40:12.000 align:start position:0% the backbone environment because it's a 01:40:12.000 --> 01:40:15.250 align:start position:0% the backbone environment because it's a shorter<01:40:12.300> distance<01:40:12.540> high<01:40:13.699> high<01:40:14.699> throughput 01:40:15.250 --> 01:40:15.260 align:start position:0% shorter distance high high throughput 01:40:15.260 --> 01:40:17.629 align:start position:0% shorter distance high high throughput lastly<01:40:16.260> there's<01:40:16.500> also<01:40:16.739> something<01:40:16.980> a<01:40:17.280> single 01:40:17.629 --> 01:40:17.639 align:start position:0% lastly there's also something a single 01:40:17.639 --> 01:40:20.209 align:start position:0% lastly there's also something a single mode<01:40:17.820> which<01:40:18.540> converts<01:40:18.900> to<01:40:19.139> multi-mode<01:40:19.679> fiber 01:40:20.209 --> 01:40:20.219 align:start position:0% mode which converts to multi-mode fiber 01:40:20.219 --> 01:40:22.810 align:start position:0% mode which converts to multi-mode fiber these<01:40:20.820> connectors<01:40:21.179> are<01:40:21.659> generally<01:40:22.139> used<01:40:22.440> to 01:40:22.810 --> 01:40:22.820 align:start position:0% these connectors are generally used to 01:40:22.820 --> 01:40:26.870 align:start position:0% these connectors are generally used to extend<01:40:23.820> the<01:40:24.060> range<01:40:24.360> of<01:40:24.600> multi-mode<01:40:25.139> signals 01:40:26.870 --> 01:40:26.880 align:start position:0% extend the range of multi-mode signals 01:40:26.880 --> 01:40:29.390 align:start position:0% extend the range of multi-mode signals now<01:40:27.360> the<01:40:27.600> Tia<01:40:27.960> eia<01:40:28.500> which<01:40:29.040> we've<01:40:29.280> already 01:40:29.390 --> 01:40:29.400 align:start position:0% now the Tia eia which we've already 01:40:29.400 --> 01:40:31.030 align:start position:0% now the Tia eia which we've already mentioned<01:40:29.880> the<01:40:30.179> organization 01:40:31.030 --> 01:40:31.040 align:start position:0% mentioned the organization 01:40:31.040 --> 01:40:33.050 align:start position:0% mentioned the organization telecommunications<01:40:32.040> industry<01:40:32.520> Association 01:40:33.050 --> 01:40:33.060 align:start position:0% telecommunications industry Association 01:40:33.060 --> 01:40:35.810 align:start position:0% telecommunications industry Association electronic<01:40:33.960> Industries<01:40:34.380> Association<01:40:34.920> uh 01:40:35.810 --> 01:40:35.820 align:start position:0% electronic Industries Association uh 01:40:35.820 --> 01:40:39.350 align:start position:0% electronic Industries Association uh created<01:40:36.239> standards<01:40:36.960> for<01:40:37.380> all<01:40:37.880> this<01:40:38.880> cabling 01:40:39.350 --> 01:40:39.360 align:start position:0% created standards for all this cabling 01:40:39.360 --> 01:40:42.229 align:start position:0% created standards for all this cabling that<01:40:40.320> covers<01:40:40.739> the<01:40:41.100> proper<01:40:41.520> implementation 01:40:42.229 --> 01:40:42.239 align:start position:0% that covers the proper implementation 01:40:42.239 --> 01:40:45.229 align:start position:0% that covers the proper implementation design<01:40:43.199> and<01:40:43.739> maintenance<01:40:44.159> to<01:40:44.760> ensure<01:40:45.060> that 01:40:45.229 --> 01:40:45.239 align:start position:0% design and maintenance to ensure that 01:40:45.239 --> 01:40:46.610 align:start position:0% design and maintenance to ensure that there's<01:40:45.420> a<01:40:45.540> certain<01:40:45.719> level<01:40:45.960> of<01:40:46.260> performance 01:40:46.610 --> 01:40:46.620 align:start position:0% there's a certain level of performance 01:40:46.620 --> 01:40:49.310 align:start position:0% there's a certain level of performance that's<01:40:46.920> met<01:40:47.219> and<01:40:48.120> that's<01:40:48.420> also<01:40:48.840> going<01:40:49.080> to 01:40:49.310 --> 01:40:49.320 align:start position:0% that's met and that's also going to 01:40:49.320 --> 01:40:50.930 align:start position:0% that's met and that's also going to ensure<01:40:49.620> that<01:40:49.860> if<01:40:50.040> someone<01:40:50.219> else<01:40:50.460> comes<01:40:50.820> into 01:40:50.930 --> 01:40:50.940 align:start position:0% ensure that if someone else comes into 01:40:50.940 --> 01:40:52.430 align:start position:0% ensure that if someone else comes into your<01:40:51.239> environment<01:40:51.600> they<01:40:51.900> know<01:40:52.080> what<01:40:52.320> they're 01:40:52.430 --> 01:40:52.440 align:start position:0% your environment they know what they're 01:40:52.440 --> 01:40:55.370 align:start position:0% your environment they know what they're getting<01:40:52.620> themselves<01:40:52.980> into<01:40:53.239> now<01:40:54.239> there's<01:40:54.600> six 01:40:55.370 --> 01:40:55.380 align:start position:0% getting themselves into now there's six 01:40:55.380 --> 01:40:57.830 align:start position:0% getting themselves into now there's six uh<01:40:55.920> the<01:40:56.639> standard<01:40:56.880> is<01:40:57.000> comprised<01:40:57.420> into<01:40:57.540> six 01:40:57.830 --> 01:40:57.840 align:start position:0% uh the standard is comprised into six 01:40:57.840 --> 01:40:59.870 align:start position:0% uh the standard is comprised into six different<01:40:58.080> categories<01:40:58.860> and<01:40:59.400> it's<01:40:59.520> important 01:40:59.870 --> 01:40:59.880 align:start position:0% different categories and it's important 01:40:59.880 --> 01:41:01.310 align:start position:0% different categories and it's important that<01:41:00.120> you<01:41:00.300> actually<01:41:00.420> know<01:41:00.659> these<01:41:00.960> for<01:41:01.199> the 01:41:01.310 --> 01:41:01.320 align:start position:0% that you actually know these for the 01:41:01.320 --> 01:41:03.229 align:start position:0% that you actually know these for the exam<01:41:01.679> this<01:41:02.400> by<01:41:02.580> the<01:41:02.699> way<01:41:02.760> is<01:41:02.940> called 01:41:03.229 --> 01:41:03.239 align:start position:0% exam this by the way is called 01:41:03.239 --> 01:41:05.629 align:start position:0% exam this by the way is called structured<01:41:04.199> cabling 01:41:05.629 --> 01:41:05.639 align:start position:0% structured cabling 01:41:05.639 --> 01:41:06.830 align:start position:0% structured cabling so<01:41:06.000> first<01:41:06.179> we<01:41:06.360> have<01:41:06.480> something<01:41:06.600> called 01:41:06.830 --> 01:41:06.840 align:start position:0% so first we have something called 01:41:06.840 --> 01:41:09.110 align:start position:0% so first we have something called entrance<01:41:07.320> facilities<01:41:07.800> and<01:41:08.280> this<01:41:08.400> covers<01:41:08.820> the 01:41:09.110 --> 01:41:09.120 align:start position:0% entrance facilities and this covers the 01:41:09.120 --> 01:41:10.970 align:start position:0% entrance facilities and this covers the entrance<01:41:09.540> of<01:41:09.840> the<01:41:10.080> Communication<01:41:10.560> Service 01:41:10.970 --> 01:41:10.980 align:start position:0% entrance of the Communication Service 01:41:10.980 --> 01:41:13.790 align:start position:0% entrance of the Communication Service into<01:41:11.880> the<01:41:12.179> building<01:41:12.420> and<01:41:13.320> this<01:41:13.440> includes 01:41:13.790 --> 01:41:13.800 align:start position:0% into the building and this includes 01:41:13.800 --> 01:41:16.189 align:start position:0% into the building and this includes What's<01:41:13.980> called<01:41:14.159> the<01:41:14.460> demarcation<01:41:15.120> point 01:41:16.189 --> 01:41:16.199 align:start position:0% What's called the demarcation point 01:41:16.199 --> 01:41:19.310 align:start position:0% What's called the demarcation point the<01:41:16.679> demarcation<01:41:17.340> point<01:41:17.639> is<01:41:17.940> that<01:41:18.179> point<01:41:18.480> at 01:41:19.310 --> 01:41:19.320 align:start position:0% the demarcation point is that point at 01:41:19.320 --> 01:41:21.250 align:start position:0% the demarcation point is that point at which<01:41:19.560> the<01:41:19.920> responsibility<01:41:20.460> of<01:41:20.699> the<01:41:20.880> network 01:41:21.250 --> 01:41:21.260 align:start position:0% which the responsibility of the network 01:41:21.260 --> 01:41:24.770 align:start position:0% which the responsibility of the network changes<01:41:22.260> from<01:41:22.679> you<01:41:23.100> to<01:41:23.280> your<01:41:23.460> ISP<01:41:24.000> or<01:41:24.600> from 01:41:24.770 --> 01:41:24.780 align:start position:0% changes from you to your ISP or from 01:41:24.780 --> 01:41:27.290 align:start position:0% changes from you to your ISP or from your<01:41:24.900> isptu<01:41:25.739> or<01:41:25.860> your<01:41:26.040> company<01:41:26.219> it<01:41:27.060> also 01:41:27.290 --> 01:41:27.300 align:start position:0% your isptu or your company it also 01:41:27.300 --> 01:41:29.030 align:start position:0% your isptu or your company it also contains<01:41:27.659> the<01:41:27.900> backbone<01:41:28.380> connections<01:41:28.860> as 01:41:29.030 --> 01:41:29.040 align:start position:0% contains the backbone connections as 01:41:29.040 --> 01:41:30.410 align:start position:0% contains the backbone connections as well 01:41:30.410 --> 01:41:30.420 align:start position:0% well 01:41:30.420 --> 01:41:33.950 align:start position:0% well next<01:41:31.139> we<01:41:31.500> have<01:41:31.679> the<01:41:32.040> backbone<01:41:32.580> wiring<01:41:33.360> which 01:41:33.950 --> 01:41:33.960 align:start position:0% next we have the backbone wiring which 01:41:33.960 --> 01:41:35.689 align:start position:0% next we have the backbone wiring which is<01:41:34.080> the<01:41:34.380> wiring<01:41:34.739> connection<01:41:34.980> that<01:41:35.340> goes<01:41:35.580> from 01:41:35.689 --> 01:41:35.699 align:start position:0% is the wiring connection that goes from 01:41:35.699 --> 01:41:37.310 align:start position:0% is the wiring connection that goes from the<01:41:35.880> communications<01:41:36.300> closet<01:41:36.960> to<01:41:37.199> the 01:41:37.310 --> 01:41:37.320 align:start position:0% the communications closet to the 01:41:37.320 --> 01:41:40.370 align:start position:0% the communications closet to the equipment<01:41:37.619> rooms<01:41:38.219> so<01:41:39.119> the<01:41:39.420> characteristic<01:41:40.139> of 01:41:40.370 --> 01:41:40.380 align:start position:0% equipment rooms so the characteristic of 01:41:40.380 --> 01:41:42.590 align:start position:0% equipment rooms so the characteristic of this<01:41:40.619> wiring<01:41:41.280> is<01:41:41.580> going<01:41:41.699> to<01:41:41.880> depend<01:41:42.239> on<01:41:42.420> the 01:41:42.590 --> 01:41:42.600 align:start position:0% this wiring is going to depend on the 01:41:42.600 --> 01:41:45.350 align:start position:0% this wiring is going to depend on the type<01:41:42.719> of<01:41:42.960> media<01:41:43.320> chosen<01:41:43.800> such<01:41:44.460> as<01:41:44.699> copper<01:41:45.239> or 01:41:45.350 --> 01:41:45.360 align:start position:0% type of media chosen such as copper or 01:41:45.360 --> 01:41:47.149 align:start position:0% type of media chosen such as copper or Fiber<01:41:45.840> but<01:41:46.199> nonetheless<01:41:46.560> we<01:41:46.800> need<01:41:46.920> to<01:41:47.040> make 01:41:47.149 --> 01:41:47.159 align:start position:0% Fiber but nonetheless we need to make 01:41:47.159 --> 01:41:50.570 align:start position:0% Fiber but nonetheless we need to make sure<01:41:47.340> it's<01:41:47.580> it's<01:41:47.960> very<01:41:48.960> sturdy<01:41:49.500> and<01:41:50.100> also<01:41:50.340> very 01:41:50.570 --> 01:41:50.580 align:start position:0% sure it's it's very sturdy and also very 01:41:50.580 --> 01:41:51.649 align:start position:0% sure it's it's very sturdy and also very fast 01:41:51.649 --> 01:41:51.659 align:start position:0% fast 01:41:51.659 --> 01:41:54.830 align:start position:0% fast the<01:41:52.320> equipment<01:41:52.619> room<01:41:52.920> now<01:41:53.820> uh<01:41:54.360> so<01:41:54.480> we've<01:41:54.659> gone 01:41:54.830 --> 01:41:54.840 align:start position:0% the equipment room now uh so we've gone 01:41:54.840 --> 01:41:58.609 align:start position:0% the equipment room now uh so we've gone from<01:41:55.199> uh<01:41:55.560> dmarc<01:41:56.219> to<01:41:56.639> Backbone<01:41:57.300> or<01:41:57.780> uh<01:41:58.199> we've 01:41:58.609 --> 01:41:58.619 align:start position:0% from uh dmarc to Backbone or uh we've 01:41:58.619 --> 01:42:00.890 align:start position:0% from uh dmarc to Backbone or uh we've gone<01:41:58.679> from<01:41:58.920> entrance<01:41:59.340> facility<01:41:59.639> or<01:41:59.940> dmarc<01:42:00.540> to 01:42:00.890 --> 01:42:00.900 align:start position:0% gone from entrance facility or dmarc to 01:42:00.900 --> 01:42:03.470 align:start position:0% gone from entrance facility or dmarc to Backbone<01:42:01.500> to<01:42:01.800> equipment<01:42:02.159> the<01:42:02.880> equipment<01:42:03.179> room 01:42:03.470 --> 01:42:03.480 align:start position:0% Backbone to equipment the equipment room 01:42:03.480 --> 01:42:05.390 align:start position:0% Backbone to equipment the equipment room is<01:42:03.840> the<01:42:04.020> point<01:42:04.199> of<01:42:04.380> termination<01:42:04.920> for<01:42:05.280> the 01:42:05.390 --> 01:42:05.400 align:start position:0% is the point of termination for the 01:42:05.400 --> 01:42:07.430 align:start position:0% is the point of termination for the backbone<01:42:05.820> wiring<01:42:06.179> it's<01:42:06.659> also<01:42:06.900> called<01:42:07.080> the<01:42:07.320> MCC 01:42:07.430 --> 01:42:07.440 align:start position:0% backbone wiring it's also called the MCC 01:42:07.440 --> 01:42:10.490 align:start position:0% backbone wiring it's also called the MCC or<01:42:08.040> the<01:42:08.280> main<01:42:08.520> cross<01:42:08.940> contact<01:42:09.300> and<01:42:10.199> this<01:42:10.380> can 01:42:10.490 --> 01:42:10.500 align:start position:0% or the main cross contact and this can 01:42:10.500 --> 01:42:12.649 align:start position:0% or the main cross contact and this can also<01:42:10.739> be<01:42:10.920> considered<01:42:11.520> what<01:42:12.060> I've<01:42:12.239> seen<01:42:12.480> it 01:42:12.649 --> 01:42:12.659 align:start position:0% also be considered what I've seen it 01:42:12.659 --> 01:42:14.270 align:start position:0% also be considered what I've seen it more<01:42:12.840> considered<01:42:13.320> on<01:42:13.440> the<01:42:13.500> network<01:42:13.619> plus<01:42:13.860> exam 01:42:14.270 --> 01:42:14.280 align:start position:0% more considered on the network plus exam 01:42:14.280 --> 01:42:17.750 align:start position:0% more considered on the network plus exam the<01:42:14.940> MDF<01:42:15.480> or<01:42:16.080> the<01:42:16.380> main<01:42:16.619> distribution<01:42:17.219> frame 01:42:17.750 --> 01:42:17.760 align:start position:0% the MDF or the main distribution frame 01:42:17.760 --> 01:42:19.310 align:start position:0% the MDF or the main distribution frame we're<01:42:18.239> going<01:42:18.420> to<01:42:18.480> talk<01:42:18.600> more<01:42:18.780> about<01:42:19.020> this 01:42:19.310 --> 01:42:19.320 align:start position:0% we're going to talk more about this 01:42:19.320 --> 01:42:21.290 align:start position:0% we're going to talk more about this shortly 01:42:21.290 --> 01:42:21.300 align:start position:0% shortly 01:42:21.300 --> 01:42:23.330 align:start position:0% shortly the<01:42:21.960> next<01:42:22.139> portion<01:42:22.500> of<01:42:22.619> structured<01:42:23.040> cabling 01:42:23.330 --> 01:42:23.340 align:start position:0% the next portion of structured cabling 01:42:23.340 --> 01:42:25.430 align:start position:0% the next portion of structured cabling are<01:42:23.639> the<01:42:23.820> Telecommunications<01:42:24.540> closets<01:42:25.199> so 01:42:25.430 --> 01:42:25.440 align:start position:0% are the Telecommunications closets so 01:42:25.440 --> 01:42:26.870 align:start position:0% are the Telecommunications closets so these<01:42:25.800> are<01:42:26.100> contain<01:42:26.520> the<01:42:26.699> connection 01:42:26.870 --> 01:42:26.880 align:start position:0% these are contain the connection 01:42:26.880 --> 01:42:28.790 align:start position:0% these are contain the connection equipment<01:42:27.600> for<01:42:27.960> any<01:42:28.139> of<01:42:28.320> the<01:42:28.500> nearby 01:42:28.790 --> 01:42:28.800 align:start position:0% equipment for any of the nearby 01:42:28.800 --> 01:42:31.189 align:start position:0% equipment for any of the nearby workstations<01:42:29.400> as<01:42:30.119> well<01:42:30.300> as<01:42:30.480> the<01:42:30.719> connections 01:42:31.189 --> 01:42:31.199 align:start position:0% workstations as well as the connections 01:42:31.199 --> 01:42:33.350 align:start position:0% workstations as well as the connections between<01:42:31.739> any<01:42:32.280> Communications<01:42:32.820> that 01:42:33.350 --> 01:42:33.360 align:start position:0% between any Communications that 01:42:33.360 --> 01:42:34.609 align:start position:0% between any Communications that cross-connect 01:42:34.609 --> 01:42:34.619 align:start position:0% cross-connect 01:42:34.619 --> 01:42:36.470 align:start position:0% cross-connect we<01:42:35.100> also<01:42:35.280> have<01:42:35.340> something<01:42:35.460> called<01:42:35.699> horizontal 01:42:36.470 --> 01:42:36.480 align:start position:0% we also have something called horizontal 01:42:36.480 --> 01:42:38.450 align:start position:0% we also have something called horizontal wiring<01:42:36.900> which<01:42:37.380> is<01:42:37.500> the<01:42:37.679> cable<01:42:37.800> and<01:42:38.100> that<01:42:38.280> goes 01:42:38.450 --> 01:42:38.460 align:start position:0% wiring which is the cable and that goes 01:42:38.460 --> 01:42:39.890 align:start position:0% wiring which is the cable and that goes between<01:42:38.699> workstations<01:42:39.480> and<01:42:39.780> the 01:42:39.890 --> 01:42:39.900 align:start position:0% between workstations and the 01:42:39.900 --> 01:42:41.930 align:start position:0% between workstations and the Telecommunications<01:42:40.560> closet<01:42:41.159> and<01:42:41.639> this<01:42:41.820> is 01:42:41.930 --> 01:42:41.940 align:start position:0% Telecommunications closet and this is 01:42:41.940 --> 01:42:45.169 align:start position:0% Telecommunications closet and this is typically<01:42:42.300> in<01:42:43.080> the<01:42:43.619> wall<01:42:43.739> in<01:42:43.980> the<01:42:44.100> ceiling 01:42:45.169 --> 01:42:45.179 align:start position:0% typically in the wall in the ceiling 01:42:45.179 --> 01:42:46.609 align:start position:0% typically in the wall in the ceiling finally 01:42:46.609 --> 01:42:46.619 align:start position:0% finally 01:42:46.619 --> 01:42:48.350 align:start position:0% finally we<01:42:46.920> have<01:42:47.100> the<01:42:47.219> work<01:42:47.340> area<01:42:47.639> which<01:42:48.179> is 01:42:48.350 --> 01:42:48.360 align:start position:0% we have the work area which is 01:42:48.360 --> 01:42:49.970 align:start position:0% we have the work area which is everything<01:42:48.659> coming<01:42:49.020> from<01:42:49.380> the<01:42:49.560> wall<01:42:49.739> outlet 01:42:49.970 --> 01:42:49.980 align:start position:0% everything coming from the wall outlet 01:42:49.980 --> 01:42:52.310 align:start position:0% everything coming from the wall outlet to<01:42:50.460> the<01:42:50.580> workstation<01:42:51.119> so<01:42:51.719> this<01:42:51.900> is<01:42:51.960> the<01:42:52.139> face 01:42:52.310 --> 01:42:52.320 align:start position:0% to the workstation so this is the face 01:42:52.320 --> 01:42:55.310 align:start position:0% to the workstation so this is the face plate<01:42:52.739> connectors<01:42:53.460> wiring<01:42:54.119> and<01:42:54.360> so<01:42:54.540> on<01:42:54.719> so<01:42:55.199> you 01:42:55.310 --> 01:42:55.320 align:start position:0% plate connectors wiring and so on so you 01:42:55.320 --> 01:42:58.430 align:start position:0% plate connectors wiring and so on so you can<01:42:55.440> see<01:42:55.560> that<01:42:55.739> we're<01:42:56.040> going<01:42:56.280> from<01:42:57.260> the<01:42:58.260> sort 01:42:58.430 --> 01:42:58.440 align:start position:0% can see that we're going from the sort 01:42:58.440 --> 01:42:59.689 align:start position:0% can see that we're going from the sort of<01:42:58.560> main<01:42:58.800> point<01:42:58.980> in<01:42:59.159> our<01:42:59.280> building<01:42:59.400> that 01:42:59.689 --> 01:42:59.699 align:start position:0% of main point in our building that 01:42:59.699 --> 01:43:01.790 align:start position:0% of main point in our building that entrance<01:43:00.119> where<01:43:00.480> the<01:43:00.659> D<01:43:00.780> mark<01:43:01.020> happens<01:43:01.320> where 01:43:01.790 --> 01:43:01.800 align:start position:0% entrance where the D mark happens where 01:43:01.800 --> 01:43:03.649 align:start position:0% entrance where the D mark happens where the<01:43:02.040> ISP<01:43:02.639> the<01:43:02.820> internet<01:43:03.000> comes<01:43:03.360> into<01:43:03.420> our 01:43:03.649 --> 01:43:03.659 align:start position:0% the ISP the internet comes into our 01:43:03.659 --> 01:43:05.510 align:start position:0% the ISP the internet comes into our building<01:43:03.900> all<01:43:04.619> the<01:43:04.739> way<01:43:04.800> down<01:43:05.159> to<01:43:05.400> the 01:43:05.510 --> 01:43:05.520 align:start position:0% building all the way down to the 01:43:05.520 --> 01:43:07.790 align:start position:0% building all the way down to the workstation<01:43:06.000> or<01:43:06.239> the<01:43:06.360> user 01:43:07.790 --> 01:43:07.800 align:start position:0% workstation or the user 01:43:07.800 --> 01:43:10.490 align:start position:0% workstation or the user the<01:43:08.340> Tia<01:43:08.699> eia<01:43:09.300> has<01:43:09.719> also<01:43:09.960> set<01:43:10.139> out<01:43:10.320> a 01:43:10.490 --> 01:43:10.500 align:start position:0% the Tia eia has also set out a 01:43:10.500 --> 01:43:12.830 align:start position:0% the Tia eia has also set out a specification<01:43:11.040> of<01:43:11.280> standards<01:43:11.760> that<01:43:12.360> line<01:43:12.540> out 01:43:12.830 --> 01:43:12.840 align:start position:0% specification of standards that line out 01:43:12.840 --> 01:43:14.930 align:start position:0% specification of standards that line out minimum<01:43:13.380> performance<01:43:13.980> levels<01:43:14.400> for<01:43:14.760> Network 01:43:14.930 --> 01:43:14.940 align:start position:0% minimum performance levels for Network 01:43:14.940 --> 01:43:18.229 align:start position:0% minimum performance levels for Network media<01:43:15.480> in<01:43:16.320> uh<01:43:16.619> commercial<01:43:16.860> environments<01:43:17.699> now 01:43:18.229 --> 01:43:18.239 align:start position:0% media in uh commercial environments now 01:43:18.239 --> 01:43:21.950 align:start position:0% media in uh commercial environments now these<01:43:18.600> standards<01:43:19.139> are<01:43:19.560> 568<01:43:20.219> a<01:43:20.520> b<01:43:20.760> and<01:43:20.940> c<01:43:21.119> we<01:43:21.780> saw 01:43:21.950 --> 01:43:21.960 align:start position:0% these standards are 568 a b and c we saw 01:43:21.960 --> 01:43:24.950 align:start position:0% these standards are 568 a b and c we saw earlier<01:43:22.320> the<01:43:22.739> t568<01:43:23.699> A<01:43:24.000> and<01:43:24.179> B<01:43:24.360> which<01:43:24.659> were<01:43:24.780> the 01:43:24.950 --> 01:43:24.960 align:start position:0% earlier the t568 A and B which were the 01:43:24.960 --> 01:43:29.090 align:start position:0% earlier the t568 A and B which were the standards<01:43:25.320> for<01:43:25.619> uh<01:43:26.460> cabling<01:43:27.619> colored<01:43:28.619> Twisted 01:43:29.090 --> 01:43:29.100 align:start position:0% standards for uh cabling colored Twisted 01:43:29.100 --> 01:43:30.830 align:start position:0% standards for uh cabling colored Twisted Pairs<01:43:29.520> and<01:43:29.639> how<01:43:29.820> they<01:43:30.000> should<01:43:30.119> be<01:43:30.300> arranged 01:43:30.830 --> 01:43:30.840 align:start position:0% Pairs and how they should be arranged 01:43:30.840 --> 01:43:33.050 align:start position:0% Pairs and how they should be arranged and<01:43:30.960> terminated<01:43:31.440> but<01:43:31.980> there<01:43:32.219> are<01:43:32.340> also<01:43:32.580> some 01:43:33.050 --> 01:43:33.060 align:start position:0% and terminated but there are also some 01:43:33.060 --> 01:43:35.629 align:start position:0% and terminated but there are also some other<01:43:33.600> specific<01:43:34.139> attributes<01:43:34.860> that<01:43:35.400> you<01:43:35.520> need 01:43:35.629 --> 01:43:35.639 align:start position:0% other specific attributes that you need 01:43:35.639 --> 01:43:36.830 align:start position:0% other specific attributes that you need to<01:43:35.760> be<01:43:35.880> aware<01:43:36.119> of 01:43:36.830 --> 01:43:36.840 align:start position:0% to be aware of 01:43:36.840 --> 01:43:39.649 align:start position:0% to be aware of the<01:43:37.260> 568a<01:43:38.159> specification<01:43:38.820> is<01:43:39.119> an<01:43:39.360> older 01:43:39.649 --> 01:43:39.659 align:start position:0% the 568a specification is an older 01:43:39.659 --> 01:43:42.229 align:start position:0% the 568a specification is an older standard<01:43:40.020> it's<01:43:40.380> governed<01:43:40.920> uh<01:43:41.760> it<01:43:41.880> governed 01:43:42.229 --> 01:43:42.239 align:start position:0% standard it's governed uh it governed 01:43:42.239 --> 01:43:44.390 align:start position:0% standard it's governed uh it governed data<01:43:42.659> voice<01:43:43.080> video<01:43:43.739> and<01:43:44.159> commercial 01:43:44.390 --> 01:43:44.400 align:start position:0% data voice video and commercial 01:43:44.400 --> 01:43:46.729 align:start position:0% data voice video and commercial buildings<01:43:45.300> and<01:43:45.900> it's<01:43:46.139> basically<01:43:46.500> been 01:43:46.729 --> 01:43:46.739 align:start position:0% buildings and it's basically been 01:43:46.739 --> 01:43:49.910 align:start position:0% buildings and it's basically been outdated<01:43:47.219> and<01:43:47.520> superseded<01:43:48.119> nowadays<01:43:48.659> by<01:43:48.960> 568a 01:43:49.910 --> 01:43:49.920 align:start position:0% outdated and superseded nowadays by 568a 01:43:49.920 --> 01:43:52.970 align:start position:0% outdated and superseded nowadays by 568a sorry<01:43:50.400> B<01:43:50.699> and<01:43:50.880> C<01:43:51.119> standards<01:43:51.800> the<01:43:52.800> B 01:43:52.970 --> 01:43:52.980 align:start position:0% sorry B and C standards the B 01:43:52.980 --> 01:43:55.310 align:start position:0% sorry B and C standards the B specification<01:43:53.760> now<01:43:54.060> is<01:43:54.300> an<01:43:54.480> earlier<01:43:54.840> standard 01:43:55.310 --> 01:43:55.320 align:start position:0% specification now is an earlier standard 01:43:55.320 --> 01:43:57.649 align:start position:0% specification now is an earlier standard still<01:43:56.100> in<01:43:56.280> use<01:43:56.460> quite<01:43:56.880> frequently<01:43:57.300> that 01:43:57.649 --> 01:43:57.659 align:start position:0% still in use quite frequently that 01:43:57.659 --> 01:44:00.169 align:start position:0% still in use quite frequently that defines<01:43:58.260> minimum<01:43:58.980> performance<01:43:59.460> levels<01:43:59.880> for 01:44:00.169 --> 01:44:00.179 align:start position:0% defines minimum performance levels for 01:44:00.179 --> 01:44:02.209 align:start position:0% defines minimum performance levels for cabling<01:44:00.600> including<01:44:01.560> twisted<01:44:02.040> pair 01:44:02.209 --> 01:44:02.219 align:start position:0% cabling including twisted pair 01:44:02.219 --> 01:44:05.629 align:start position:0% cabling including twisted pair performance<01:44:02.820> minimums<01:44:03.540> uh<01:44:04.199> shielded<01:44:04.739> Twisted 01:44:05.629 --> 01:44:05.639 align:start position:0% performance minimums uh shielded Twisted 01:44:05.639 --> 01:44:09.470 align:start position:0% performance minimums uh shielded Twisted paramums<01:44:06.360> fiber<01:44:06.960> optic<01:44:07.320> standards<01:44:07.800> and<01:44:08.639> Etc 01:44:09.470 --> 01:44:09.480 align:start position:0% paramums fiber optic standards and Etc 01:44:09.480 --> 01:44:11.810 align:start position:0% paramums fiber optic standards and Etc portions<01:44:10.199> of<01:44:10.380> this<01:44:10.560> are<01:44:10.800> now<01:44:11.040> Obsolete<01:44:11.699> and 01:44:11.810 --> 01:44:11.820 align:start position:0% portions of this are now Obsolete and 01:44:11.820 --> 01:44:16.189 align:start position:0% portions of this are now Obsolete and have<01:44:12.000> been<01:44:12.179> replaced<01:44:12.719> by<01:44:13.219> 568c<01:44:14.239> the<01:44:15.239> 568c 01:44:16.189 --> 01:44:16.199 align:start position:0% have been replaced by 568c the 568c 01:44:16.199 --> 01:44:17.450 align:start position:0% have been replaced by 568c the 568c standard 01:44:17.450 --> 01:44:17.460 align:start position:0% standard 01:44:17.460 --> 01:44:19.070 align:start position:0% standard which<01:44:17.880> is<01:44:18.000> the<01:44:18.239> current<01:44:18.360> specification 01:44:19.070 --> 01:44:19.080 align:start position:0% which is the current specification 01:44:19.080 --> 01:44:21.649 align:start position:0% which is the current specification that's<01:44:19.380> set<01:44:19.560> out<01:44:19.739> designates<01:44:20.639> minimums<01:44:21.480> for 01:44:21.649 --> 01:44:21.659 align:start position:0% that's set out designates minimums for 01:44:21.659 --> 01:44:24.229 align:start position:0% that's set out designates minimums for optimizing<01:44:22.199> Network<01:44:22.380> media<01:44:22.920> performance<01:44:23.460> in 01:44:24.229 --> 01:44:24.239 align:start position:0% optimizing Network media performance in 01:44:24.239 --> 01:44:26.629 align:start position:0% optimizing Network media performance in commercial<01:44:24.540> buildings<01:44:25.280> currently<01:44:26.280> it 01:44:26.629 --> 01:44:26.639 align:start position:0% commercial buildings currently it 01:44:26.639 --> 01:44:29.750 align:start position:0% commercial buildings currently it specifies<01:44:27.060> cat<01:44:27.540> 6A<01:44:28.260> as<01:44:28.679> the<01:44:28.860> media<01:44:29.219> type<01:44:29.400> that 01:44:29.750 --> 01:44:29.760 align:start position:0% specifies cat 6A as the media type that 01:44:29.760 --> 01:44:33.169 align:start position:0% specifies cat 6A as the media type that is<01:44:29.940> recommended<01:44:30.600> so<01:44:31.380> again<01:44:31.860> the<01:44:32.159> 568<01:44:32.639> A<01:44:32.880> and<01:44:33.060> B 01:44:33.169 --> 01:44:33.179 align:start position:0% is recommended so again the 568 A and B 01:44:33.179 --> 01:44:35.330 align:start position:0% is recommended so again the 568 A and B the<01:44:33.480> T5<01:44:33.840> to<01:44:34.080> 68<01:44:34.380> A<01:44:34.560> and<01:44:34.679> B<01:44:34.800> that<01:44:34.920> we<01:44:35.040> saw<01:44:35.100> earlier 01:44:35.330 --> 01:44:35.340 align:start position:0% the T5 to 68 A and B that we saw earlier 01:44:35.340 --> 01:44:37.729 align:start position:0% the T5 to 68 A and B that we saw earlier those<01:44:35.580> are<01:44:35.760> how<01:44:36.000> everything<01:44:36.540> is<01:44:36.780> cabled<01:44:37.320> those 01:44:37.729 --> 01:44:37.739 align:start position:0% those are how everything is cabled those 01:44:37.739 --> 01:44:39.890 align:start position:0% those are how everything is cabled those fall<01:44:37.980> under<01:44:38.280> the<01:44:38.699> umbrella<01:44:39.060> of<01:44:39.540> the<01:44:39.719> more 01:44:39.890 --> 01:44:39.900 align:start position:0% fall under the umbrella of the more 01:44:39.900 --> 01:44:43.430 align:start position:0% fall under the umbrella of the more General<01:44:40.139> 568<01:44:40.980> a<01:44:41.280> b<01:44:41.460> and<01:44:41.639> c<01:44:41.820> standards<01:44:42.780> which 01:44:43.430 --> 01:44:43.440 align:start position:0% General 568 a b and c standards which 01:44:43.440 --> 01:44:45.649 align:start position:0% General 568 a b and c standards which speak<01:44:43.920> more<01:44:44.100> to<01:44:44.340> Performance 01:44:45.649 --> 01:44:45.659 align:start position:0% speak more to Performance 01:44:45.659 --> 01:44:47.810 align:start position:0% speak more to Performance now<01:44:46.139> while<01:44:46.380> the<01:44:46.560> Tia<01:44:46.800> and<01:44:47.100> the<01:44:47.219> eia<01:44:47.400> have 01:44:47.810 --> 01:44:47.820 align:start position:0% now while the Tia and the eia have 01:44:47.820 --> 01:44:50.510 align:start position:0% now while the Tia and the eia have established<01:44:48.540> uh<01:44:48.960> standards<01:44:49.500> for<01:44:49.980> structured 01:44:50.510 --> 01:44:50.520 align:start position:0% established uh standards for structured 01:44:50.520 --> 01:44:51.590 align:start position:0% established uh standards for structured cabling 01:44:51.590 --> 01:44:51.600 align:start position:0% cabling 01:44:51.600 --> 01:44:54.590 align:start position:0% cabling premise<01:44:52.320> wiring<01:44:52.920> uh 01:44:54.590 --> 01:44:54.600 align:start position:0% premise wiring uh 01:44:54.600 --> 01:44:56.570 align:start position:0% premise wiring uh the<01:44:55.320> terms<01:44:55.560> that<01:44:55.739> we're<01:44:55.800> going<01:44:55.980> to<01:44:56.100> use<01:44:56.219> are 01:44:56.570 --> 01:44:56.580 align:start position:0% the terms that we're going to use are 01:44:56.580 --> 01:45:00.290 align:start position:0% the terms that we're going to use are industry-wide<01:44:57.560> so<01:44:58.760> although<01:44:59.760> there<01:45:00.000> might<01:45:00.179> be 01:45:00.290 --> 01:45:00.300 align:start position:0% industry-wide so although there might be 01:45:00.300 --> 01:45:02.990 align:start position:0% industry-wide so although there might be these<01:45:00.600> standards<01:45:01.260> the<01:45:02.219> terms<01:45:02.580> you're<01:45:02.880> going 01:45:02.990 --> 01:45:03.000 align:start position:0% these standards the terms you're going 01:45:03.000 --> 01:45:05.330 align:start position:0% these standards the terms you're going to<01:45:03.119> see<01:45:03.179> over<01:45:03.360> and<01:45:03.480> over<01:45:03.659> again 01:45:05.330 --> 01:45:05.340 align:start position:0% to see over and over again 01:45:05.340 --> 01:45:08.750 align:start position:0% to see over and over again hierarchical<01:45:06.239> cabling<01:45:06.780> is<01:45:07.500> recognized<01:45:08.340> and 01:45:08.750 --> 01:45:08.760 align:start position:0% hierarchical cabling is recognized and 01:45:08.760 --> 01:45:10.850 align:start position:0% hierarchical cabling is recognized and used<01:45:09.080> which<01:45:10.080> is<01:45:10.260> what<01:45:10.440> we're<01:45:10.560> talking<01:45:10.739> about 01:45:10.850 --> 01:45:10.860 align:start position:0% used which is what we're talking about 01:45:10.860 --> 01:45:12.410 align:start position:0% used which is what we're talking about when<01:45:11.040> we<01:45:11.159> talk<01:45:11.280> about<01:45:11.400> premise<01:45:11.940> wiring 01:45:12.410 --> 01:45:12.420 align:start position:0% when we talk about premise wiring 01:45:12.420 --> 01:45:14.870 align:start position:0% when we talk about premise wiring everywhere 01:45:14.870 --> 01:45:14.880 align:start position:0% everywhere 01:45:14.880 --> 01:45:17.750 align:start position:0% everywhere it's<01:45:15.960> a<01:45:16.500> telecommunications<01:45:17.280> design 01:45:17.750 --> 01:45:17.760 align:start position:0% it's a telecommunications design 01:45:17.760 --> 01:45:20.990 align:start position:0% it's a telecommunications design tradition<01:45:18.480> that<01:45:19.440> basically<01:45:19.860> allows<01:45:20.280> for<01:45:20.580> main 01:45:20.990 --> 01:45:21.000 align:start position:0% tradition that basically allows for main 01:45:21.000 --> 01:45:23.689 align:start position:0% tradition that basically allows for main cross<01:45:21.300> connects<01:45:21.840> or<01:45:21.960> MCCS<01:45:22.679> to<01:45:23.280> be<01:45:23.400> connected 01:45:23.689 --> 01:45:23.699 align:start position:0% cross connects or MCCS to be connected 01:45:23.699 --> 01:45:26.330 align:start position:0% cross connects or MCCS to be connected to<01:45:23.880> what<01:45:24.119> are<01:45:24.239> called<01:45:24.560> iccs<01:45:25.560> or<01:45:25.739> intermediate 01:45:26.330 --> 01:45:26.340 align:start position:0% to what are called iccs or intermediate 01:45:26.340 --> 01:45:29.990 align:start position:0% to what are called iccs or intermediate cross<01:45:26.580> connects<01:45:27.179> in<01:45:28.080> a<01:45:28.320> star<01:45:28.560> topology<01:45:29.100> with 01:45:29.990 --> 01:45:30.000 align:start position:0% cross connects in a star topology with 01:45:30.000 --> 01:45:33.050 align:start position:0% cross connects in a star topology with horizontal<01:45:30.600> cross<01:45:30.840> connects<01:45:31.980> in<01:45:32.580> most<01:45:32.699> cases 01:45:33.050 --> 01:45:33.060 align:start position:0% horizontal cross connects in most cases 01:45:33.060 --> 01:45:34.609 align:start position:0% horizontal cross connects in most cases you're<01:45:33.360> probably<01:45:33.540> going<01:45:33.719> to<01:45:33.840> see<01:45:33.960> the<01:45:34.260> terms 01:45:34.609 --> 01:45:34.619 align:start position:0% you're probably going to see the terms 01:45:34.619 --> 01:45:38.510 align:start position:0% you're probably going to see the terms wiring<01:45:35.520> closet<01:45:36.320> MDF<01:45:37.320> or<01:45:37.739> main<01:45:37.980> distribution 01:45:38.510 --> 01:45:38.520 align:start position:0% wiring closet MDF or main distribution 01:45:38.520 --> 01:45:41.629 align:start position:0% wiring closet MDF or main distribution frame<01:45:39.000> and<01:45:39.659> IDF<01:45:40.199> or<01:45:40.920> intermediate 01:45:41.629 --> 01:45:41.639 align:start position:0% frame and IDF or intermediate 01:45:41.639 --> 01:45:44.209 align:start position:0% frame and IDF or intermediate distribution<01:45:42.060> frame<01:45:42.540> instead<01:45:43.320> of<01:45:43.440> MCC<01:45:43.739> and 01:45:44.209 --> 01:45:44.219 align:start position:0% distribution frame instead of MCC and 01:45:44.219 --> 01:45:46.669 align:start position:0% distribution frame instead of MCC and ICC<01:45:44.639> however<01:45:45.540> they're<01:45:46.080> both<01:45:46.440> used 01:45:46.669 --> 01:45:46.679 align:start position:0% ICC however they're both used 01:45:46.679 --> 01:45:48.950 align:start position:0% ICC however they're both used interchangeably<01:45:47.580> so<01:45:48.239> I<01:45:48.360> just<01:45:48.480> want<01:45:48.600> to<01:45:48.719> take<01:45:48.840> a 01:45:48.950 --> 01:45:48.960 align:start position:0% interchangeably so I just want to take a 01:45:48.960 --> 01:45:50.629 align:start position:0% interchangeably so I just want to take a look<01:45:49.020> at<01:45:49.260> some<01:45:49.380> of<01:45:49.500> the<01:45:49.619> components<01:45:50.219> that<01:45:50.460> make 01:45:50.629 --> 01:45:50.639 align:start position:0% look at some of the components that make 01:45:50.639 --> 01:45:53.750 align:start position:0% look at some of the components that make up<01:45:50.820> this<01:45:51.119> premise<01:45:51.480> wiring<01:45:51.960> right<01:45:52.619> now 01:45:53.750 --> 01:45:53.760 align:start position:0% up this premise wiring right now 01:45:53.760 --> 01:45:56.390 align:start position:0% up this premise wiring right now the<01:45:54.480> patch<01:45:54.840> panel<01:45:55.199> is<01:45:55.440> the<01:45:55.739> connection<01:45:55.860> point 01:45:56.390 --> 01:45:56.400 align:start position:0% the patch panel is the connection point 01:45:56.400 --> 01:45:59.629 align:start position:0% the patch panel is the connection point for<01:45:56.940> drop<01:45:57.239> cables<01:45:57.840> and<01:45:58.260> patch<01:45:58.619> cables<01:45:58.980> they're 01:45:59.629 --> 01:45:59.639 align:start position:0% for drop cables and patch cables they're 01:45:59.639 --> 01:46:02.090 align:start position:0% for drop cables and patch cables they're connected<01:46:00.000> to<01:46:00.179> the<01:46:00.360> patch<01:46:00.780> panel<01:46:01.199> via<01:46:01.920> the 01:46:02.090 --> 01:46:02.100 align:start position:0% connected to the patch panel via the 01:46:02.100 --> 01:46:04.430 align:start position:0% connected to the patch panel via the RJ45<01:46:02.880> connectors<01:46:03.420> that<01:46:03.600> we<01:46:03.780> saw<01:46:03.900> with<01:46:04.080> twisted 01:46:04.430 --> 01:46:04.440 align:start position:0% RJ45 connectors that we saw with twisted 01:46:04.440 --> 01:46:06.830 align:start position:0% RJ45 connectors that we saw with twisted pair<01:46:04.619> now<01:46:05.280> you<01:46:05.460> might<01:46:05.580> find<01:46:05.880> a<01:46:06.239> patch<01:46:06.540> cable 01:46:06.830 --> 01:46:06.840 align:start position:0% pair now you might find a patch cable 01:46:06.840 --> 01:46:09.770 align:start position:0% pair now you might find a patch cable with<01:46:07.199> a<01:46:07.500> single<01:46:07.800> row<01:46:08.100> of<01:46:08.219> connections<01:46:08.820> or<01:46:09.480> one 01:46:09.770 --> 01:46:09.780 align:start position:0% with a single row of connections or one 01:46:09.780 --> 01:46:12.290 align:start position:0% with a single row of connections or one with<01:46:09.960> a<01:46:10.080> dozen<01:46:10.440> or<01:46:10.560> more<01:46:10.739> rows<01:46:11.100> now<01:46:11.880> a<01:46:12.119> drop 01:46:12.290 --> 01:46:12.300 align:start position:0% with a dozen or more rows now a drop 01:46:12.300 --> 01:46:14.209 align:start position:0% with a dozen or more rows now a drop cable<01:46:12.600> what<01:46:12.840> I<01:46:13.020> just<01:46:13.139> mentioned<01:46:13.500> is<01:46:13.800> the<01:46:14.040> cable 01:46:14.209 --> 01:46:14.219 align:start position:0% cable what I just mentioned is the cable 01:46:14.219 --> 01:46:16.430 align:start position:0% cable what I just mentioned is the cable that<01:46:14.460> goes<01:46:14.820> from<01:46:15.000> the<01:46:15.119> workstation<01:46:15.659> and<01:46:16.260> the 01:46:16.430 --> 01:46:16.440 align:start position:0% that goes from the workstation and the 01:46:16.440 --> 01:46:18.770 align:start position:0% that goes from the workstation and the network<01:46:16.619> devices<01:46:17.159> to<01:46:17.699> the<01:46:17.880> wall 01:46:18.770 --> 01:46:18.780 align:start position:0% network devices to the wall 01:46:18.780 --> 01:46:21.649 align:start position:0% network devices to the wall a<01:46:19.619> patch<01:46:19.980> cable<01:46:20.280> is<01:46:20.880> a<01:46:21.000> cable<01:46:21.239> that<01:46:21.480> is 01:46:21.649 --> 01:46:21.659 align:start position:0% a patch cable is a cable that is 01:46:21.659 --> 01:46:23.689 align:start position:0% a patch cable is a cable that is connected<01:46:22.080> to<01:46:22.500> the<01:46:22.739> patch<01:46:23.100> panel<01:46:23.400> and 01:46:23.689 --> 01:46:23.699 align:start position:0% connected to the patch panel and 01:46:23.699 --> 01:46:26.629 align:start position:0% connected to the patch panel and connects<01:46:24.179> two<01:46:24.600> drop<01:46:24.960> cables<01:46:25.560> this<01:46:26.340> cable 01:46:26.629 --> 01:46:26.639 align:start position:0% connects two drop cables this cable 01:46:26.639 --> 01:46:28.669 align:start position:0% connects two drop cables this cable might<01:46:27.000> be<01:46:27.179> either<01:46:27.480> a<01:46:27.960> normal<01:46:28.199> straight 01:46:28.669 --> 01:46:28.679 align:start position:0% might be either a normal straight 01:46:28.679 --> 01:46:31.310 align:start position:0% might be either a normal straight through<01:46:28.860> cable<01:46:29.219> or<01:46:29.940> a<01:46:30.179> crossover<01:46:30.540> cable<01:46:31.020> which 01:46:31.310 --> 01:46:31.320 align:start position:0% through cable or a crossover cable which 01:46:31.320 --> 01:46:32.990 align:start position:0% through cable or a crossover cable which is<01:46:31.440> something<01:46:31.619> I<01:46:31.800> mentioned<01:46:32.100> earlier<01:46:32.460> that 01:46:32.990 --> 01:46:33.000 align:start position:0% is something I mentioned earlier that 01:46:33.000 --> 01:46:35.410 align:start position:0% is something I mentioned earlier that crossover<01:46:33.360> cable<01:46:33.780> has<01:46:34.320> one<01:46:34.560> end<01:46:34.739> that<01:46:35.040> has<01:46:35.159> the 01:46:35.410 --> 01:46:35.420 align:start position:0% crossover cable has one end that has the 01:46:35.420 --> 01:46:37.729 align:start position:0% crossover cable has one end that has the 568a<01:46:36.420> wiring<01:46:36.840> and<01:46:37.080> the<01:46:37.199> other<01:46:37.260> end<01:46:37.440> that<01:46:37.619> has 01:46:37.729 --> 01:46:37.739 align:start position:0% 568a wiring and the other end that has 01:46:37.739 --> 01:46:41.149 align:start position:0% 568a wiring and the other end that has 568<01:46:38.340> B<01:46:38.880> wiring<01:46:39.420> this<01:46:40.139> is<01:46:40.260> in<01:46:40.440> order<01:46:40.619> to<01:46:40.920> connect 01:46:41.149 --> 01:46:41.159 align:start position:0% 568 B wiring this is in order to connect 01:46:41.159 --> 01:46:44.629 align:start position:0% 568 B wiring this is in order to connect two<01:46:41.760> like<01:46:42.060> devices<01:46:42.540> such<01:46:42.960> as<01:46:43.400> computers<01:46:44.400> or 01:46:44.629 --> 01:46:44.639 align:start position:0% two like devices such as computers or 01:46:44.639 --> 01:46:46.970 align:start position:0% two like devices such as computers or switches<01:46:45.060> directly<01:46:45.600> to<01:46:45.840> each<01:46:46.080> other<01:46:46.199> remember 01:46:46.970 --> 01:46:46.980 align:start position:0% switches directly to each other remember 01:46:46.980 --> 01:46:48.530 align:start position:0% switches directly to each other remember the<01:46:47.400> pin<01:46:47.580> out<01:46:47.699> on<01:46:47.940> these<01:46:48.179> is<01:46:48.360> different 01:46:48.530 --> 01:46:48.540 align:start position:0% the pin out on these is different 01:46:48.540 --> 01:46:50.629 align:start position:0% the pin out on these is different because<01:46:49.139> the<01:46:49.619> one<01:46:49.800> and<01:46:49.980> two<01:46:50.159> pins<01:46:50.400> are 01:46:50.629 --> 01:46:50.639 align:start position:0% because the one and two pins are 01:46:50.639 --> 01:46:52.729 align:start position:0% because the one and two pins are switched<01:46:51.060> on<01:46:51.239> one<01:46:51.420> end<01:46:51.540> with<01:46:52.320> the<01:46:52.440> three<01:46:52.560> and 01:46:52.729 --> 01:46:52.739 align:start position:0% switched on one end with the three and 01:46:52.739 --> 01:46:54.770 align:start position:0% switched on one end with the three and six<01:46:52.920> pins<01:46:53.219> so<01:46:53.639> this<01:46:53.760> allows<01:46:54.119> data<01:46:54.480> to<01:46:54.600> go 01:46:54.770 --> 01:46:54.780 align:start position:0% six pins so this allows data to go 01:46:54.780 --> 01:46:57.530 align:start position:0% six pins so this allows data to go directly<01:46:55.139> between<01:46:55.440> two<01:46:55.739> devices<01:46:56.300> a<01:46:57.300> lot<01:46:57.360> of 01:46:57.530 --> 01:46:57.540 align:start position:0% directly between two devices a lot of 01:46:57.540 --> 01:46:59.510 align:start position:0% directly between two devices a lot of devices<01:46:58.020> nowadays<01:46:58.619> however<01:46:58.920> don't<01:46:59.219> require 01:46:59.510 --> 01:46:59.520 align:start position:0% devices nowadays however don't require 01:46:59.520 --> 01:47:02.149 align:start position:0% devices nowadays however don't require the<01:46:59.940> crossover<01:47:00.239> cable<01:47:01.139> uh<01:47:01.619> because<01:47:01.860> they<01:47:02.040> have 01:47:02.149 --> 01:47:02.159 align:start position:0% the crossover cable uh because they have 01:47:02.159 --> 01:47:03.950 align:start position:0% the crossover cable uh because they have an<01:47:02.340> auto<01:47:02.460> sort<01:47:02.760> of<01:47:02.940> sensing<01:47:03.300> feature<01:47:03.659> within 01:47:03.950 --> 01:47:03.960 align:start position:0% an auto sort of sensing feature within 01:47:03.960 --> 01:47:06.830 align:start position:0% an auto sort of sensing feature within them<01:47:04.560> now<01:47:05.040> a<01:47:05.280> patch<01:47:05.580> panel<01:47:05.880> and<01:47:06.060> patch<01:47:06.420> cables 01:47:06.830 --> 01:47:06.840 align:start position:0% them now a patch panel and patch cables 01:47:06.840 --> 01:47:10.430 align:start position:0% them now a patch panel and patch cables are<01:47:07.199> located<01:47:07.440> in<01:47:08.100> wiring<01:47:08.520> closets 01:47:10.430 --> 01:47:10.440 align:start position:0% are located in wiring closets 01:47:10.440 --> 01:47:13.609 align:start position:0% are located in wiring closets the<01:47:11.100> IDF<01:47:11.639> is<01:47:12.300> the<01:47:12.480> communications<01:47:13.080> connection 01:47:13.609 --> 01:47:13.619 align:start position:0% the IDF is the communications connection 01:47:13.619 --> 01:47:16.250 align:start position:0% the IDF is the communications connection point<01:47:14.040> or<01:47:14.460> cable<01:47:14.820> rack<01:47:15.239> that<01:47:15.659> connects<01:47:16.020> all 01:47:16.250 --> 01:47:16.260 align:start position:0% point or cable rack that connects all 01:47:16.260 --> 01:47:19.970 align:start position:0% point or cable rack that connects all the<01:47:16.440> workstations<01:47:17.179> to<01:47:18.179> the<01:47:18.540> MDF<01:47:19.139> or<01:47:19.440> the<01:47:19.739> main 01:47:19.970 --> 01:47:19.980 align:start position:0% the workstations to the MDF or the main 01:47:19.980 --> 01:47:22.790 align:start position:0% the workstations to the MDF or the main distribution<01:47:20.580> frame<01:47:21.080> the<01:47:22.080> main<01:47:22.260> distribution 01:47:22.790 --> 01:47:22.800 align:start position:0% distribution frame the main distribution 01:47:22.800 --> 01:47:25.729 align:start position:0% distribution frame the main distribution frame<01:47:23.280> MDF<01:47:23.940> is<01:47:24.540> the<01:47:24.840> main<01:47:25.020> connection<01:47:25.320> point 01:47:25.729 --> 01:47:25.739 align:start position:0% frame MDF is the main connection point 01:47:25.739 --> 01:47:28.310 align:start position:0% frame MDF is the main connection point or<01:47:26.100> cable<01:47:26.460> rack<01:47:26.820> that<01:47:27.300> distributes<01:47:27.840> cables 01:47:28.310 --> 01:47:28.320 align:start position:0% or cable rack that distributes cables 01:47:28.320 --> 01:47:31.609 align:start position:0% or cable rack that distributes cables from<01:47:28.560> itself<01:47:28.980> to<01:47:29.639> all<01:47:29.940> the<01:47:30.060> other<01:47:30.179> idfs<01:47:30.960> now 01:47:31.609 --> 01:47:31.619 align:start position:0% from itself to all the other idfs now 01:47:31.619 --> 01:47:33.830 align:start position:0% from itself to all the other idfs now there's<01:47:31.800> only<01:47:31.980> going<01:47:32.100> to<01:47:32.280> be<01:47:32.340> one<01:47:32.699> MDF<01:47:33.300> but 01:47:33.830 --> 01:47:33.840 align:start position:0% there's only going to be one MDF but 01:47:33.840 --> 01:47:37.010 align:start position:0% there's only going to be one MDF but there<01:47:33.960> can<01:47:34.080> be<01:47:34.260> many<01:47:34.500> idfs<01:47:35.639> the<01:47:36.239> wiring<01:47:36.540> closet 01:47:37.010 --> 01:47:37.020 align:start position:0% there can be many idfs the wiring closet 01:47:37.020 --> 01:47:39.410 align:start position:0% there can be many idfs the wiring closet is<01:47:37.440> a<01:47:37.679> room<01:47:37.860> where<01:47:38.280> the<01:47:38.460> patch<01:47:38.760> panels<01:47:39.119> are 01:47:39.410 --> 01:47:39.420 align:start position:0% is a room where the patch panels are 01:47:39.420 --> 01:47:41.510 align:start position:0% is a room where the patch panels are installed<01:47:39.840> and<01:47:40.080> the<01:47:40.199> wiring<01:47:40.500> runs<01:47:40.920> through<01:47:41.280> it 01:47:41.510 --> 01:47:41.520 align:start position:0% installed and the wiring runs through it 01:47:41.520 --> 01:47:42.470 align:start position:0% installed and the wiring runs through it too 01:47:42.470 --> 01:47:42.480 align:start position:0% too 01:47:42.480 --> 01:47:43.970 align:start position:0% too so<01:47:42.719> here<01:47:42.960> we<01:47:43.080> have<01:47:43.199> a<01:47:43.320> building<01:47:43.440> where<01:47:43.739> we<01:47:43.860> have 01:47:43.970 --> 01:47:43.980 align:start position:0% so here we have a building where we have 01:47:43.980 --> 01:47:46.850 align:start position:0% so here we have a building where we have an<01:47:44.159> MDF<01:47:44.639> on<01:47:44.820> the<01:47:44.940> bottom<01:47:45.119> floor<01:47:45.300> and<01:47:45.840> an<01:47:46.020> IDF<01:47:46.500> on 01:47:46.850 --> 01:47:46.860 align:start position:0% an MDF on the bottom floor and an IDF on 01:47:46.860 --> 01:47:49.189 align:start position:0% an MDF on the bottom floor and an IDF on each<01:47:47.040> of<01:47:47.159> the<01:47:47.280> floors<01:47:47.520> above<01:47:47.880> the<01:47:48.600> connections 01:47:49.189 --> 01:47:49.199 align:start position:0% each of the floors above the connections 01:47:49.199 --> 01:47:51.890 align:start position:0% each of the floors above the connections going<01:47:49.440> from<01:47:49.739> the<01:47:49.980> idfs<01:47:50.699> through<01:47:51.000> the<01:47:51.300> walls<01:47:51.659> go 01:47:51.890 --> 01:47:51.900 align:start position:0% going from the idfs through the walls go 01:47:51.900 --> 01:47:54.470 align:start position:0% going from the idfs through the walls go to<01:47:52.020> the<01:47:52.139> workstations<01:47:52.760> then<01:47:53.760> there<01:47:54.239> is<01:47:54.360> a 01:47:54.470 --> 01:47:54.480 align:start position:0% to the workstations then there is a 01:47:54.480 --> 01:47:56.149 align:start position:0% to the workstations then there is a connection<01:47:54.659> that's<01:47:55.020> typically<01:47:55.380> much<01:47:55.860> faster 01:47:56.149 --> 01:47:56.159 align:start position:0% connection that's typically much faster 01:47:56.159 --> 01:47:57.649 align:start position:0% connection that's typically much faster than<01:47:56.340> the<01:47:56.520> rest<01:47:56.639> of<01:47:56.820> the<01:47:56.820> network<01:47:57.000> that<01:47:57.420> goes 01:47:57.649 --> 01:47:57.659 align:start position:0% than the rest of the network that goes 01:47:57.659 --> 01:48:00.290 align:start position:0% than the rest of the network that goes between<01:47:57.840> the<01:47:58.199> idfs<01:47:58.860> and<01:47:59.100> the<01:47:59.219> MDF 01:48:00.290 --> 01:48:00.300 align:start position:0% between the idfs and the MDF 01:48:00.300 --> 01:48:02.689 align:start position:0% between the idfs and the MDF when<01:48:01.020> installing<01:48:01.679> Cable<01:48:02.040> in<01:48:02.340> a<01:48:02.520> building 01:48:02.689 --> 01:48:02.699 align:start position:0% when installing Cable in a building 01:48:02.699 --> 01:48:05.090 align:start position:0% when installing Cable in a building there<01:48:03.480> are<01:48:03.600> fire<01:48:03.900> code<01:48:04.199> requirements<01:48:04.920> that 01:48:05.090 --> 01:48:05.100 align:start position:0% there are fire code requirements that 01:48:05.100 --> 01:48:06.229 align:start position:0% there are fire code requirements that have<01:48:05.280> to<01:48:05.400> be<01:48:05.520> met 01:48:06.229 --> 01:48:06.239 align:start position:0% have to be met 01:48:06.239 --> 01:48:08.450 align:start position:0% have to be met specifically<01:48:07.080> when<01:48:07.679> you're<01:48:07.860> running<01:48:08.040> cable 01:48:08.450 --> 01:48:08.460 align:start position:0% specifically when you're running cable 01:48:08.460 --> 01:48:10.729 align:start position:0% specifically when you're running cable and<01:48:08.820> air<01:48:09.060> handling<01:48:09.540> spaces<01:48:10.080> which<01:48:10.380> are<01:48:10.500> like 01:48:10.729 --> 01:48:10.739 align:start position:0% and air handling spaces which are like 01:48:10.739 --> 01:48:14.209 align:start position:0% and air handling spaces which are like under<01:48:11.100> floors<01:48:11.940> and<01:48:12.480> in<01:48:12.780> walls<01:48:13.320> most<01:48:13.920> of<01:48:14.100> the 01:48:14.209 --> 01:48:14.219 align:start position:0% under floors and in walls most of the 01:48:14.219 --> 01:48:17.209 align:start position:0% under floors and in walls most of the fire<01:48:14.460> codes<01:48:14.760> require<01:48:15.239> a<01:48:15.780> specific<01:48:16.080> cable 01:48:17.209 --> 01:48:17.219 align:start position:0% fire codes require a specific cable 01:48:17.219 --> 01:48:19.370 align:start position:0% fire codes require a specific cable PVC<01:48:17.940> cabling<01:48:18.420> which<01:48:18.719> is<01:48:18.840> the<01:48:19.080> typically 01:48:19.370 --> 01:48:19.380 align:start position:0% PVC cabling which is the typically 01:48:19.380 --> 01:48:21.950 align:start position:0% PVC cabling which is the typically standard<01:48:20.040> network<01:48:20.520> cable<01:48:20.880> that's<01:48:21.600> fairly 01:48:21.950 --> 01:48:21.960 align:start position:0% standard network cable that's fairly 01:48:21.960 --> 01:48:24.609 align:start position:0% standard network cable that's fairly inexpensive<01:48:22.440> and<01:48:22.619> easy<01:48:22.860> to<01:48:23.100> work<01:48:23.219> with<01:48:23.540> allows 01:48:24.609 --> 01:48:24.619 align:start position:0% inexpensive and easy to work with allows 01:48:24.619 --> 01:48:26.990 align:start position:0% inexpensive and easy to work with allows allows<01:48:25.619> fire<01:48:25.860> to<01:48:26.159> travel<01:48:26.340> through<01:48:26.639> the<01:48:26.820> cable 01:48:26.990 --> 01:48:27.000 align:start position:0% allows fire to travel through the cable 01:48:27.000 --> 01:48:30.290 align:start position:0% allows fire to travel through the cable if<01:48:27.239> it<01:48:27.420> berms<01:48:27.900> and<01:48:28.500> then<01:48:28.619> it<01:48:28.860> releases<01:48:29.400> these 01:48:30.290 --> 01:48:30.300 align:start position:0% if it berms and then it releases these 01:48:30.300 --> 01:48:33.649 align:start position:0% if it berms and then it releases these poisonous<01:48:31.020> and<01:48:31.320> noxious<01:48:31.739> fumes<01:48:32.400> so<01:48:33.119> as<01:48:33.480> a 01:48:33.649 --> 01:48:33.659 align:start position:0% poisonous and noxious fumes so as a 01:48:33.659 --> 01:48:37.189 align:start position:0% poisonous and noxious fumes so as a result<01:48:33.860> plenum<01:48:34.860> grade<01:48:35.100> cabling<01:48:35.580> which<01:48:36.540> is 01:48:37.189 --> 01:48:37.199 align:start position:0% result plenum grade cabling which is 01:48:37.199 --> 01:48:40.729 align:start position:0% result plenum grade cabling which is part<01:48:37.619> of<01:48:37.800> the<01:48:38.219> uh<01:48:38.639> plenum<01:48:39.239> or<01:48:39.840> a<01:48:40.020> plenum<01:48:40.440> space 01:48:40.729 --> 01:48:40.739 align:start position:0% part of the uh plenum or a plenum space 01:48:40.739 --> 01:48:43.070 align:start position:0% part of the uh plenum or a plenum space is<01:48:41.219> part<01:48:41.460> of<01:48:41.580> a<01:48:41.820> building<01:48:42.060> that<01:48:42.600> is<01:48:42.719> used<01:48:42.900> for 01:48:43.070 --> 01:48:43.080 align:start position:0% is part of a building that is used for 01:48:43.080 --> 01:48:45.770 align:start position:0% is part of a building that is used for air<01:48:43.320> circulation<01:48:43.920> and<01:48:44.460> HVAC<01:48:45.000> systems<01:48:45.480> and<01:48:45.659> so 01:48:45.770 --> 01:48:45.780 align:start position:0% air circulation and HVAC systems and so 01:48:45.780 --> 01:48:48.350 align:start position:0% air circulation and HVAC systems and so on<01:48:45.900> by<01:48:46.440> providing<01:48:46.860> Pathways<01:48:47.639> either<01:48:47.880> that<01:48:48.179> are 01:48:48.350 --> 01:48:48.360 align:start position:0% on by providing Pathways either that are 01:48:48.360 --> 01:48:51.050 align:start position:0% on by providing Pathways either that are heated<01:48:48.739> conditioned<01:48:49.739> or<01:48:50.280> have<01:48:50.760> return 01:48:51.050 --> 01:48:51.060 align:start position:0% heated conditioned or have return 01:48:51.060 --> 01:48:52.310 align:start position:0% heated conditioned or have return airflows 01:48:52.310 --> 01:48:52.320 align:start position:0% airflows 01:48:52.320 --> 01:48:54.350 align:start position:0% airflows space<01:48:52.920> between<01:48:53.219> the<01:48:53.639> structural<01:48:53.940> floor<01:48:54.179> and 01:48:54.350 --> 01:48:54.360 align:start position:0% space between the structural floor and 01:48:54.360 --> 01:48:56.330 align:start position:0% space between the structural floor and the<01:48:54.480> dropped<01:48:54.780> ceiling<01:48:55.139> or<01:48:55.440> under<01:48:55.679> a<01:48:55.980> raised 01:48:56.330 --> 01:48:56.340 align:start position:0% the dropped ceiling or under a raised 01:48:56.340 --> 01:48:59.330 align:start position:0% the dropped ceiling or under a raised floor<01:48:56.580> is<01:48:56.820> what's<01:48:57.119> called<01:48:57.300> plenum<01:48:58.199> so<01:48:58.800> we<01:48:59.219> have 01:48:59.330 --> 01:48:59.340 align:start position:0% floor is what's called plenum so we have 01:48:59.340 --> 01:49:01.310 align:start position:0% floor is what's called plenum so we have some<01:48:59.699> special<01:48:59.940> cabling<01:49:00.480> called<01:49:00.719> plenum 01:49:01.310 --> 01:49:01.320 align:start position:0% some special cabling called plenum 01:49:01.320 --> 01:49:03.470 align:start position:0% some special cabling called plenum cabling<01:49:01.739> this<01:49:02.219> is<01:49:02.400> jacketing<01:49:02.940> that's<01:49:03.060> wrapped 01:49:03.470 --> 01:49:03.480 align:start position:0% cabling this is jacketing that's wrapped 01:49:03.480 --> 01:49:05.570 align:start position:0% cabling this is jacketing that's wrapped around<01:49:03.659> the<01:49:03.960> wires<01:49:04.320> very<01:49:04.560> tightly<01:49:04.920> and<01:49:05.400> it 01:49:05.570 --> 01:49:05.580 align:start position:0% around the wires very tightly and it 01:49:05.580 --> 01:49:07.010 align:start position:0% around the wires very tightly and it prevents<01:49:05.940> fire<01:49:06.119> from<01:49:06.420> moving<01:49:06.659> through<01:49:06.900> it 01:49:07.010 --> 01:49:07.020 align:start position:0% prevents fire from moving through it 01:49:07.020 --> 01:49:09.470 align:start position:0% prevents fire from moving through it therefore<01:49:07.920> it's<01:49:08.340> not<01:49:08.580> going<01:49:08.820> to<01:49:09.000> put<01:49:09.239> off 01:49:09.470 --> 01:49:09.480 align:start position:0% therefore it's not going to put off 01:49:09.480 --> 01:49:12.050 align:start position:0% therefore it's not going to put off those<01:49:09.900> noxious<01:49:10.320> and<01:49:10.500> poisonous<01:49:10.980> fumes<01:49:11.400> it 01:49:12.050 --> 01:49:12.060 align:start position:0% those noxious and poisonous fumes it 01:49:12.060 --> 01:49:13.310 align:start position:0% those noxious and poisonous fumes it also<01:49:12.300> makes<01:49:12.420> the<01:49:12.659> cable<01:49:12.840> a<01:49:13.020> lot<01:49:13.139> more 01:49:13.310 --> 01:49:13.320 align:start position:0% also makes the cable a lot more 01:49:13.320 --> 01:49:15.530 align:start position:0% also makes the cable a lot more expensive<01:49:13.860> and<01:49:14.580> it<01:49:14.760> can<01:49:14.880> be<01:49:14.940> a<01:49:15.060> lot<01:49:15.179> difficult 01:49:15.530 --> 01:49:15.540 align:start position:0% expensive and it can be a lot difficult 01:49:15.540 --> 01:49:17.330 align:start position:0% expensive and it can be a lot difficult a<01:49:16.020> lot<01:49:16.139> more<01:49:16.380> difficult<01:49:16.679> to<01:49:16.860> work<01:49:16.980> with<01:49:17.159> at 01:49:17.330 --> 01:49:17.340 align:start position:0% a lot more difficult to work with at 01:49:17.340 --> 01:49:19.550 align:start position:0% a lot more difficult to work with at times<01:49:17.580> however<01:49:18.060> it<01:49:18.360> is<01:49:18.540> required<01:49:19.139> by<01:49:19.320> fire 01:49:19.550 --> 01:49:19.560 align:start position:0% times however it is required by fire 01:49:19.560 --> 01:49:21.109 align:start position:0% times however it is required by fire code<01:49:19.800> that<01:49:20.040> if<01:49:20.219> you're<01:49:20.280> running<01:49:20.460> cabling<01:49:20.880> in 01:49:21.109 --> 01:49:21.119 align:start position:0% code that if you're running cabling in 01:49:21.119 --> 01:49:23.270 align:start position:0% code that if you're running cabling in between<01:49:21.239> these<01:49:21.600> spaces<01:49:21.960> where<01:49:22.260> there<01:49:22.500> is<01:49:22.679> no 01:49:23.270 --> 01:49:23.280 align:start position:0% between these spaces where there is no 01:49:23.280 --> 01:49:25.310 align:start position:0% between these spaces where there is no sort<01:49:24.179> of 01:49:25.310 --> 01:49:25.320 align:start position:0% sort of 01:49:25.320 --> 01:49:27.290 align:start position:0% sort of sprinkler<01:49:26.100> system<01:49:26.340> to<01:49:26.699> put<01:49:26.820> out<01:49:26.940> the<01:49:27.119> fire 01:49:27.290 --> 01:49:27.300 align:start position:0% sprinkler system to put out the fire 01:49:27.300 --> 01:49:29.510 align:start position:0% sprinkler system to put out the fire that<01:49:27.780> you<01:49:27.900> use<01:49:28.080> plenum<01:49:28.619> grade<01:49:28.800> cabling<01:49:29.280> that's 01:49:29.510 --> 01:49:29.520 align:start position:0% that you use plenum grade cabling that's 01:49:29.520 --> 01:49:31.490 align:start position:0% that you use plenum grade cabling that's important<01:49:29.940> all<01:49:30.659> right<01:49:30.840> so<01:49:30.960> now<01:49:31.080> let's<01:49:31.260> go<01:49:31.380> over 01:49:31.490 --> 01:49:31.500 align:start position:0% important all right so now let's go over 01:49:31.500 --> 01:49:33.950 align:start position:0% important all right so now let's go over what<01:49:31.739> we<01:49:31.860> learned<01:49:32.159> first<01:49:33.000> we<01:49:33.179> defined<01:49:33.600> Network 01:49:33.950 --> 01:49:33.960 align:start position:0% what we learned first we defined Network 01:49:33.960 --> 01:49:37.490 align:start position:0% what we learned first we defined Network media<01:49:34.619> as<01:49:35.400> well<01:49:35.580> as<01:49:35.760> what<01:49:36.300> bounded<01:49:36.900> media<01:49:37.320> is 01:49:37.490 --> 01:49:37.500 align:start position:0% media as well as what bounded media is 01:49:37.500 --> 01:49:38.870 align:start position:0% media as well as what bounded media is we're<01:49:37.800> going<01:49:37.920> to<01:49:37.980> talk<01:49:38.100> about<01:49:38.219> unbounded 01:49:38.870 --> 01:49:38.880 align:start position:0% we're going to talk about unbounded 01:49:38.880 --> 01:49:40.669 align:start position:0% we're going to talk about unbounded media<01:49:39.179> a<01:49:39.300> little<01:49:39.360> bit<01:49:39.480> later<01:49:39.659> we<01:49:40.440> also 01:49:40.669 --> 01:49:40.679 align:start position:0% media a little bit later we also 01:49:40.679 --> 01:49:42.290 align:start position:0% media a little bit later we also describe<01:49:41.100> the<01:49:41.219> different<01:49:41.400> types<01:49:41.820> of<01:49:41.940> copper 01:49:42.290 --> 01:49:42.300 align:start position:0% describe the different types of copper 01:49:42.300 --> 01:49:44.629 align:start position:0% describe the different types of copper media<01:49:42.659> including<01:49:43.440> the<01:49:43.619> different<01:49:43.739> types<01:49:44.219> of 01:49:44.629 --> 01:49:44.639 align:start position:0% media including the different types of 01:49:44.639 --> 01:49:47.390 align:start position:0% media including the different types of Stan<01:49:45.540> shielded<01:49:46.199> twisted<01:49:46.679> pair<01:49:46.860> and 01:49:47.390 --> 01:49:47.400 align:start position:0% Stan shielded twisted pair and 01:49:47.400 --> 01:49:49.310 align:start position:0% Stan shielded twisted pair and unshielded<01:49:48.000> twisted<01:49:48.360> pair<01:49:48.540> and<01:49:49.139> the 01:49:49.310 --> 01:49:49.320 align:start position:0% unshielded twisted pair and the 01:49:49.320 --> 01:49:50.330 align:start position:0% unshielded twisted pair and the difference<01:49:49.440> between<01:49:49.739> those<01:49:50.040> remember 01:49:50.330 --> 01:49:50.340 align:start position:0% difference between those remember 01:49:50.340 --> 01:49:53.510 align:start position:0% difference between those remember shielded<01:49:51.060> it<01:49:51.600> protects<01:49:51.960> from<01:49:52.139> Emi<01:49:52.679> unshielded 01:49:53.510 --> 01:49:53.520 align:start position:0% shielded it protects from Emi unshielded 01:49:53.520 --> 01:49:55.310 align:start position:0% shielded it protects from Emi unshielded does<01:49:53.699> not<01:49:53.880> and<01:49:54.360> we<01:49:54.480> discussed<01:49:54.840> a<01:49:54.960> few<01:49:55.080> of<01:49:55.199> the 01:49:55.310 --> 01:49:55.320 align:start position:0% does not and we discussed a few of the 01:49:55.320 --> 01:49:57.490 align:start position:0% does not and we discussed a few of the standards<01:49:55.739> that<01:49:55.920> are<01:49:56.040> set<01:49:56.219> by<01:49:56.400> the<01:49:56.580> Tia<01:49:56.880> eia 01:49:57.490 --> 01:49:57.500 align:start position:0% standards that are set by the Tia eia 01:49:57.500 --> 01:50:01.189 align:start position:0% standards that are set by the Tia eia including<01:49:58.500> 568<01:49:59.100> a<01:49:59.520> b<01:49:59.940> and<01:50:00.179> c<01:50:00.420> and<01:50:01.020> remember 01:50:01.189 --> 01:50:01.199 align:start position:0% including 568 a b and c and remember 01:50:01.199 --> 01:50:04.149 align:start position:0% including 568 a b and c and remember that's<01:50:01.619> we<01:50:01.920> also<01:50:02.159> have<01:50:02.280> the<01:50:02.699> 568<01:50:03.300> A<01:50:03.540> and<01:50:03.780> B 01:50:04.149 --> 01:50:04.159 align:start position:0% that's we also have the 568 A and B 01:50:04.159 --> 01:50:06.350 align:start position:0% that's we also have the 568 A and B wiring<01:50:05.159> requirements<01:50:05.699> which<01:50:05.880> fall<01:50:06.119> under 01:50:06.350 --> 01:50:06.360 align:start position:0% wiring requirements which fall under 01:50:06.360 --> 01:50:08.270 align:start position:0% wiring requirements which fall under these<01:50:07.139> we<01:50:07.619> also<01:50:07.800> looked<01:50:07.980> at<01:50:07.980> the<01:50:08.100> different 01:50:08.270 --> 01:50:08.280 align:start position:0% these we also looked at the different 01:50:08.280 --> 01:50:10.729 align:start position:0% these we also looked at the different connector<01:50:08.760> types<01:50:09.119> not<01:50:09.600> only<01:50:09.719> for<01:50:10.080> the<01:50:10.380> twisted 01:50:10.729 --> 01:50:10.739 align:start position:0% connector types not only for the twisted 01:50:10.739 --> 01:50:13.609 align:start position:0% connector types not only for the twisted pair<01:50:10.920> which<01:50:11.159> is<01:50:11.280> that<01:50:11.340> RJ45<01:50:12.119> but<01:50:12.780> for<01:50:12.960> coaxial 01:50:13.609 --> 01:50:13.619 align:start position:0% pair which is that RJ45 but for coaxial 01:50:13.619 --> 01:50:16.970 align:start position:0% pair which is that RJ45 but for coaxial like<01:50:13.980> the<01:50:14.100> BNC<01:50:14.580> and<01:50:15.179> fiber<01:50:15.659> such<01:50:16.020> as<01:50:16.199> St<01:50:16.440> or<01:50:16.800> SC 01:50:16.970 --> 01:50:16.980 align:start position:0% like the BNC and fiber such as St or SC 01:50:16.980 --> 01:50:20.390 align:start position:0% like the BNC and fiber such as St or SC and<01:50:17.699> we<01:50:17.820> looked<01:50:18.179> at<01:50:18.500> structured<01:50:19.500> cabling<01:50:19.860> and 01:50:20.390 --> 01:50:20.400 align:start position:0% and we looked at structured cabling and 01:50:20.400 --> 01:50:22.370 align:start position:0% and we looked at structured cabling and premise<01:50:20.820> wiring<01:50:21.300> where<01:50:21.719> we<01:50:21.900> also<01:50:22.139> talked 01:50:22.370 --> 01:50:22.380 align:start position:0% premise wiring where we also talked 01:50:22.380 --> 01:50:23.810 align:start position:0% premise wiring where we also talked about<01:50:22.500> the<01:50:22.800> differences<01:50:23.159> and<01:50:23.520> this<01:50:23.699> is 01:50:23.810 --> 01:50:23.820 align:start position:0% about the differences and this is 01:50:23.820 --> 01:50:26.390 align:start position:0% about the differences and this is important<01:50:24.179> between<01:50:24.540> PVC<01:50:25.260> cabling 01:50:26.390 --> 01:50:26.400 align:start position:0% important between PVC cabling 01:50:26.400 --> 01:50:31.180 align:start position:0% important between PVC cabling and<01:50:26.580> plenum<01:50:27.000> grade<01:50:27.179> cabling 01:50:31.180 --> 01:50:31.190 align:start position:0% 01:50:31.190 --> 01:50:47.510 align:start position:0% [Music] 01:50:47.510 --> 01:50:47.520 align:start position:0% 01:50:47.520 --> 01:50:50.689 align:start position:0% welcome<01:50:48.060> to<01:50:48.300> module<01:50:48.659> 2<01:50:48.780> lesson<01:50:49.380> 1A<01:50:49.800> straight 01:50:50.689 --> 01:50:50.699 align:start position:0% welcome to module 2 lesson 1A straight 01:50:50.699 --> 01:50:53.030 align:start position:0% welcome to module 2 lesson 1A straight through<01:50:50.940> crossover<01:50:51.540> and<01:50:51.900> rollover<01:50:52.440> cables 01:50:53.030 --> 01:50:53.040 align:start position:0% through crossover and rollover cables 01:50:53.040 --> 01:50:55.250 align:start position:0% through crossover and rollover cables we've<01:50:53.760> actually<01:50:53.940> covered<01:50:54.719> some<01:50:54.960> of<01:50:55.080> this 01:50:55.250 --> 01:50:55.260 align:start position:0% we've actually covered some of this 01:50:55.260 --> 01:50:58.129 align:start position:0% we've actually covered some of this already<01:50:55.679> in<01:50:56.280> earlier<01:50:56.639> lessons<01:50:57.060> but<01:50:57.420> what<01:50:57.900> I've 01:50:58.129 --> 01:50:58.139 align:start position:0% already in earlier lessons but what I've 01:50:58.139 --> 01:51:01.250 align:start position:0% already in earlier lessons but what I've done<01:50:58.440> is<01:50:58.739> added<01:50:59.219> upgrades<01:50:59.760> for<01:51:00.060> the<01:51:00.360> new<01:51:00.960> exam 01:51:01.250 --> 01:51:01.260 align:start position:0% done is added upgrades for the new exam 01:51:01.260 --> 01:51:03.649 align:start position:0% done is added upgrades for the new exam syllabus<01:51:01.739> so<01:51:02.460> consider<01:51:02.940> some<01:51:03.300> of<01:51:03.420> it<01:51:03.540> a 01:51:03.649 --> 01:51:03.659 align:start position:0% syllabus so consider some of it a 01:51:03.659 --> 01:51:06.290 align:start position:0% syllabus so consider some of it a refresher<01:51:04.199> and<01:51:05.639> um<01:51:05.639> some<01:51:05.940> of<01:51:06.060> the<01:51:06.179> new 01:51:06.290 --> 01:51:06.300 align:start position:0% refresher and um some of the new 01:51:06.300 --> 01:51:07.430 align:start position:0% refresher and um some of the new material 01:51:07.430 --> 01:51:07.440 align:start position:0% material 01:51:07.440 --> 01:51:09.290 align:start position:0% material so<01:51:07.860> we're<01:51:08.100> still<01:51:08.280> under<01:51:08.460> Network<01:51:08.880> Hardware 01:51:09.290 --> 01:51:09.300 align:start position:0% so we're still under Network Hardware 01:51:09.300 --> 01:51:12.709 align:start position:0% so we're still under Network Hardware media<01:51:09.960> bounded<01:51:10.619> Network<01:51:11.040> media 01:51:12.709 --> 01:51:12.719 align:start position:0% media bounded Network media 01:51:12.719 --> 01:51:14.870 align:start position:0% media bounded Network media a<01:51:13.139> few<01:51:13.260> of<01:51:13.440> the<01:51:13.500> objectives 01:51:14.870 --> 01:51:14.880 align:start position:0% a few of the objectives 01:51:14.880 --> 01:51:18.490 align:start position:0% a few of the objectives looking<01:51:15.360> at<01:51:15.540> modular<01:51:15.900> connectors<01:51:16.500> the 01:51:18.490 --> 01:51:18.500 align:start position:0% looking at modular connectors the 01:51:18.500 --> 01:51:23.470 align:start position:0% looking at modular connectors the t568a<01:51:19.500> and<01:51:19.800> B<01:51:20.040> wiring<01:51:20.580> schemes<01:51:21.440> MDI<01:51:22.440> and<01:51:22.739> mdix 01:51:23.470 --> 01:51:23.480 align:start position:0% t568a and B wiring schemes MDI and mdix 01:51:23.480 --> 01:51:26.149 align:start position:0% t568a and B wiring schemes MDI and mdix straight<01:51:24.480> through<01:51:24.719> cables 01:51:26.149 --> 01:51:26.159 align:start position:0% straight through cables 01:51:26.159 --> 01:51:29.450 align:start position:0% straight through cables crossover<01:51:26.639> cable<01:51:27.119> and<01:51:28.020> then<01:51:28.199> Auto 01:51:29.450 --> 01:51:29.460 align:start position:0% crossover cable and then Auto 01:51:29.460 --> 01:51:33.350 align:start position:0% crossover cable and then Auto mdix<01:51:30.360> which<01:51:31.320> is<01:51:31.440> a<01:51:31.560> bit<01:51:31.679> of<01:51:31.860> a<01:51:31.920> mouthful 01:51:33.350 --> 01:51:33.360 align:start position:0% mdix which is a bit of a mouthful 01:51:33.360 --> 01:51:35.930 align:start position:0% mdix which is a bit of a mouthful and<01:51:33.960> uh<01:51:34.260> another<01:51:34.800> cable<01:51:35.280> you'll<01:51:35.580> be<01:51:35.699> using 01:51:35.930 --> 01:51:35.940 align:start position:0% and uh another cable you'll be using 01:51:35.940 --> 01:51:37.910 align:start position:0% and uh another cable you'll be using regularly<01:51:36.360> as<01:51:36.600> a<01:51:36.719> network<01:51:36.840> engineer<01:51:37.440> which<01:51:37.739> is 01:51:37.910 --> 01:51:37.920 align:start position:0% regularly as a network engineer which is 01:51:37.920 --> 01:51:39.890 align:start position:0% regularly as a network engineer which is a<01:51:38.159> rollover<01:51:38.760> cable 01:51:39.890 --> 01:51:39.900 align:start position:0% a rollover cable 01:51:39.900 --> 01:51:41.270 align:start position:0% a rollover cable they've<01:51:40.380> got<01:51:40.500> different<01:51:40.679> names<01:51:40.920> actually 01:51:41.270 --> 01:51:41.280 align:start position:0% they've got different names actually 01:51:41.280 --> 01:51:43.609 align:start position:0% they've got different names actually they<01:51:41.580> can<01:51:41.760> be<01:51:41.880> called<01:51:42.119> console<01:51:42.780> cables<01:51:43.320> if 01:51:43.609 --> 01:51:43.619 align:start position:0% they can be called console cables if 01:51:43.619 --> 01:51:46.729 align:start position:0% they can be called console cables if you're<01:51:43.800> working<01:51:44.520> in<01:51:44.760> the<01:51:44.880> Cisco<01:51:45.560> side<01:51:46.560> of 01:51:46.729 --> 01:51:46.739 align:start position:0% you're working in the Cisco side of 01:51:46.739 --> 01:51:48.649 align:start position:0% you're working in the Cisco side of things<01:51:46.920> we<01:51:47.460> tend<01:51:47.699> to<01:51:47.760> call<01:51:47.880> them<01:51:48.060> rollover 01:51:48.649 --> 01:51:48.659 align:start position:0% things we tend to call them rollover 01:51:48.659 --> 01:51:51.229 align:start position:0% things we tend to call them rollover cables<01:51:49.080> or<01:51:49.199> flat<01:51:49.560> cables 01:51:51.229 --> 01:51:51.239 align:start position:0% cables or flat cables 01:51:51.239 --> 01:51:52.970 align:start position:0% cables or flat cables but<01:51:51.719> I'm<01:51:51.900> sure<01:51:52.080> you'll<01:51:52.199> find<01:51:52.380> out<01:51:52.560> wherever 01:51:52.970 --> 01:51:52.980 align:start position:0% but I'm sure you'll find out wherever 01:51:52.980 --> 01:51:56.510 align:start position:0% but I'm sure you'll find out wherever you<01:51:53.159> end<01:51:53.520> up<01:51:53.639> working<01:51:53.880> what<01:51:54.480> uh 01:51:56.510 --> 01:51:56.520 align:start position:0% you end up working what uh 01:51:56.520 --> 01:51:58.550 align:start position:0% you end up working what uh what<01:51:57.060> they're<01:51:57.179> called<01:51:57.360> so<01:51:58.139> modular 01:51:58.550 --> 01:51:58.560 align:start position:0% what they're called so modular 01:51:58.560 --> 01:51:59.689 align:start position:0% what they're called so modular connectors 01:51:59.689 --> 01:51:59.699 align:start position:0% connectors 01:51:59.699 --> 01:52:02.090 align:start position:0% connectors a<01:52:00.239> type<01:52:00.540> of<01:52:00.659> electrical<01:52:01.139> Electric<01:52:01.739> electrical 01:52:02.090 --> 01:52:02.100 align:start position:0% a type of electrical Electric electrical 01:52:02.100 --> 01:52:04.189 align:start position:0% a type of electrical Electric electrical connector<01:52:02.460> that's<01:52:02.699> commonly<01:52:03.119> used<01:52:03.600> in<01:52:03.960> the 01:52:04.189 --> 01:52:04.199 align:start position:0% connector that's commonly used in the 01:52:04.199 --> 01:52:07.490 align:start position:0% connector that's commonly used in the following<01:52:04.860> systems<01:52:05.400> we'll<01:52:06.360> see<01:52:06.659> these<01:52:06.960> in<01:52:07.320> a 01:52:07.490 --> 01:52:07.500 align:start position:0% following systems we'll see these in a 01:52:07.500 --> 01:52:10.189 align:start position:0% following systems we'll see these in a telephone<01:52:07.699> systems<01:52:08.699> data<01:52:09.480> networks<01:52:09.840> which<01:52:10.080> is 01:52:10.189 --> 01:52:10.199 align:start position:0% telephone systems data networks which is 01:52:10.199 --> 01:52:11.689 align:start position:0% telephone systems data networks which is what<01:52:10.440> we're<01:52:10.560> more<01:52:10.800> interested<01:52:11.159> in<01:52:11.280> as<01:52:11.460> Network 01:52:11.689 --> 01:52:11.699 align:start position:0% what we're more interested in as Network 01:52:11.699 --> 01:52:13.189 align:start position:0% what we're more interested in as Network engineers 01:52:13.189 --> 01:52:13.199 align:start position:0% engineers 01:52:13.199 --> 01:52:15.470 align:start position:0% engineers low<01:52:13.560> speed<01:52:13.800> serial<01:52:14.219> connections<01:52:14.820> can<01:52:15.119> also 01:52:15.470 --> 01:52:15.480 align:start position:0% low speed serial connections can also 01:52:15.480 --> 01:52:16.729 align:start position:0% low speed serial connections can also use<01:52:15.659> them 01:52:16.729 --> 01:52:16.739 align:start position:0% use them 01:52:16.739 --> 01:52:19.550 align:start position:0% use them and<01:52:17.219> now<01:52:17.460> by<01:52:17.639> the<01:52:17.820> following<01:52:18.060> names<01:52:18.360> RJ<01:52:19.080> which 01:52:19.550 --> 01:52:19.560 align:start position:0% and now by the following names RJ which 01:52:19.560 --> 01:52:22.550 align:start position:0% and now by the following names RJ which is<01:52:19.679> short<01:52:19.920> for<01:52:20.100> registered<01:52:20.820> Jack 01:52:22.550 --> 01:52:22.560 align:start position:0% is short for registered Jack 01:52:22.560 --> 01:52:25.910 align:start position:0% is short for registered Jack modular<01:52:23.400> phone<01:52:23.760> jack<01:52:24.480> stroke<01:52:24.960> plug 01:52:25.910 --> 01:52:25.920 align:start position:0% modular phone jack stroke plug 01:52:25.920 --> 01:52:29.810 align:start position:0% modular phone jack stroke plug uh<01:52:26.580> Western<01:52:26.880> Jack<01:52:27.300> stroke<01:52:27.780> plug 01:52:29.810 --> 01:52:29.820 align:start position:0% uh Western Jack stroke plug 01:52:29.820 --> 01:52:32.169 align:start position:0% uh Western Jack stroke plug just<01:52:30.239> go<01:52:30.480> back<01:52:30.659> there<01:52:30.840> you<01:52:31.020> can<01:52:31.139> see<01:52:31.320> the<01:52:31.619> port 01:52:32.169 --> 01:52:32.179 align:start position:0% just go back there you can see the port 01:52:32.179 --> 01:52:35.570 align:start position:0% just go back there you can see the port which<01:52:33.179> is<01:52:33.360> the<01:52:33.780> interface<01:52:34.440> that<01:52:34.739> the<01:52:34.980> module 01:52:35.570 --> 01:52:35.580 align:start position:0% which is the interface that the module 01:52:35.580 --> 01:52:38.270 align:start position:0% which is the interface that the module modular<01:52:36.000> connector<01:52:36.480> goes<01:52:36.840> into<01:52:36.960> and<01:52:37.920> then<01:52:38.100> the 01:52:38.270 --> 01:52:38.280 align:start position:0% modular connector goes into and then the 01:52:38.280 --> 01:52:40.550 align:start position:0% modular connector goes into and then the physical<01:52:38.460> layer<01:52:39.000> which<01:52:39.179> will<01:52:39.360> specify<01:52:40.320> um<01:52:40.320> a 01:52:40.550 --> 01:52:40.560 align:start position:0% physical layer which will specify um a 01:52:40.560 --> 01:52:42.470 align:start position:0% physical layer which will specify um a whole<01:52:40.679> bunch<01:52:40.860> of<01:52:40.980> things<01:52:41.159> like<01:52:41.400> the<01:52:41.699> voltage 01:52:42.470 --> 01:52:42.480 align:start position:0% whole bunch of things like the voltage 01:52:42.480 --> 01:52:45.109 align:start position:0% whole bunch of things like the voltage on<01:52:42.719> the<01:52:42.840> wire<01:52:42.960> and<01:52:43.199> how<01:52:43.980> many<01:52:44.100> wires<01:52:44.520> and<01:52:44.639> or 01:52:45.109 --> 01:52:45.119 align:start position:0% on the wire and how many wires and or 01:52:45.119 --> 01:52:47.689 align:start position:0% on the wire and how many wires and or teach<01:52:45.420> wire<01:52:45.719> is<01:52:46.380> used<01:52:46.619> for<01:52:46.860> some<01:52:47.400> of<01:52:47.520> them<01:52:47.639> are 01:52:47.689 --> 01:52:47.699 align:start position:0% teach wire is used for some of them are 01:52:47.699 --> 01:52:50.930 align:start position:0% teach wire is used for some of them are unused<01:52:48.420> and<01:52:49.080> um<01:52:49.080> as<01:52:49.619> the<01:52:49.800> connections<01:52:50.219> get<01:52:50.460> uh 01:52:50.930 --> 01:52:50.940 align:start position:0% unused and um as the connections get uh 01:52:50.940 --> 01:52:52.010 align:start position:0% unused and um as the connections get uh quicker 01:52:52.010 --> 01:52:52.020 align:start position:0% quicker 01:52:52.020 --> 01:52:53.990 align:start position:0% quicker and<01:52:52.500> the<01:52:52.619> engine<01:52:52.739> is<01:52:52.980> worked<01:52:53.340> out<01:52:53.400> how<01:52:53.639> to<01:52:53.760> use 01:52:53.990 --> 01:52:54.000 align:start position:0% and the engine is worked out how to use 01:52:54.000 --> 01:52:57.109 align:start position:0% and the engine is worked out how to use spare<01:52:54.659> air<01:52:55.260> wires<01:52:55.679> to<01:52:55.800> increase<01:52:55.980> speed<01:52:56.400> which 01:52:57.109 --> 01:52:57.119 align:start position:0% spare air wires to increase speed which 01:52:57.119 --> 01:52:59.330 align:start position:0% spare air wires to increase speed which you'll<01:52:57.300> see<01:52:57.420> in<01:52:57.540> a<01:52:57.659> bit<01:52:57.840> the<01:52:58.739> male<01:52:58.980> modular 01:52:59.330 --> 01:52:59.340 align:start position:0% you'll see in a bit the male modular 01:52:59.340 --> 01:53:02.149 align:start position:0% you'll see in a bit the male modular connector<01:52:59.880> is<01:53:00.239> known<01:53:00.420> as<01:53:00.659> a<01:53:00.900> plug 01:53:02.149 --> 01:53:02.159 align:start position:0% connector is known as a plug 01:53:02.159 --> 01:53:04.850 align:start position:0% connector is known as a plug uh<01:53:03.000> basically<01:53:03.420> the<01:53:03.719> cable 01:53:04.850 --> 01:53:04.860 align:start position:0% uh basically the cable 01:53:04.860 --> 01:53:07.430 align:start position:0% uh basically the cable um<01:53:04.920> is<01:53:05.219> terminated<01:53:05.699> inside<01:53:06.060> here<01:53:06.540> normally 01:53:07.430 --> 01:53:07.440 align:start position:0% um is terminated inside here normally 01:53:07.440 --> 01:53:09.709 align:start position:0% um is terminated inside here normally you<01:53:07.679> do<01:53:07.800> buy<01:53:08.159> these<01:53:08.520> however 01:53:09.709 --> 01:53:09.719 align:start position:0% you do buy these however 01:53:09.719 --> 01:53:12.649 align:start position:0% you do buy these however um if<01:53:09.960> you<01:53:10.080> become<01:53:10.380> a<01:53:10.739> cabling<01:53:11.219> engineer 01:53:12.649 --> 01:53:12.659 align:start position:0% um if you become a cabling engineer 01:53:12.659 --> 01:53:15.229 align:start position:0% um if you become a cabling engineer you<01:53:13.440> can<01:53:13.560> have<01:53:13.800> your<01:53:14.040> own<01:53:14.159> tools<01:53:14.520> to<01:53:14.760> make<01:53:14.940> your 01:53:15.229 --> 01:53:15.239 align:start position:0% you can have your own tools to make your 01:53:15.239 --> 01:53:17.030 align:start position:0% you can have your own tools to make your own<01:53:15.360> network<01:53:15.600> cables<01:53:16.199> I<01:53:16.500> did<01:53:16.679> it<01:53:16.800> for<01:53:16.920> a<01:53:16.980> while 01:53:17.030 --> 01:53:17.040 align:start position:0% own network cables I did it for a while 01:53:17.040 --> 01:53:19.550 align:start position:0% own network cables I did it for a while I<01:53:17.280> can't<01:53:17.400> say<01:53:17.639> it<01:53:17.760> was<01:53:17.940> particularly 01:53:19.550 --> 01:53:19.560 align:start position:0% I can't say it was particularly 01:53:19.560 --> 01:53:21.050 align:start position:0% I can't say it was particularly um a<01:53:19.800> lot<01:53:19.920> of<01:53:20.040> fun 01:53:21.050 --> 01:53:21.060 align:start position:0% um a lot of fun 01:53:21.060 --> 01:53:22.910 align:start position:0% um a lot of fun but<01:53:21.540> it<01:53:21.659> did<01:53:21.780> pay<01:53:21.960> pretty<01:53:22.199> well 01:53:22.910 --> 01:53:22.920 align:start position:0% but it did pay pretty well 01:53:22.920 --> 01:53:25.910 align:start position:0% but it did pay pretty well a<01:53:23.400> female<01:53:23.699> modular<01:53:24.239> connector<01:53:24.960> is<01:53:25.199> known<01:53:25.440> as<01:53:25.679> a 01:53:25.910 --> 01:53:25.920 align:start position:0% a female modular connector is known as a 01:53:25.920 --> 01:53:28.310 align:start position:0% a female modular connector is known as a Jack<01:53:26.159> or<01:53:26.580> socket 01:53:28.310 --> 01:53:28.320 align:start position:0% Jack or socket 01:53:28.320 --> 01:53:31.310 align:start position:0% Jack or socket used<01:53:28.860> on<01:53:29.159> fixed<01:53:29.520> locations 01:53:31.310 --> 01:53:31.320 align:start position:0% used on fixed locations 01:53:31.320 --> 01:53:34.450 align:start position:0% used on fixed locations um<01:53:31.380> such<01:53:31.679> as<01:53:31.860> on<01:53:32.100> equipment 01:53:34.450 --> 01:53:34.460 align:start position:0% um such as on equipment 01:53:34.460 --> 01:53:36.950 align:start position:0% um such as on equipment uh<01:53:35.460> example<01:53:35.940> of<01:53:36.060> the<01:53:36.239> module<01:53:36.540> modular 01:53:36.950 --> 01:53:36.960 align:start position:0% uh example of the module modular 01:53:36.960 --> 01:53:40.729 align:start position:0% uh example of the module modular connector<01:53:37.440> is<01:53:37.560> the<01:53:37.800> 8<01:53:38.280> p8c<01:53:39.119> connector<01:53:39.719> uh<01:53:40.560> I 01:53:40.729 --> 01:53:40.739 align:start position:0% connector is the 8 p8c connector uh I 01:53:40.739 --> 01:53:42.229 align:start position:0% connector is the 8 p8c connector uh I think<01:53:40.860> Josh<01:53:41.280> may<01:53:41.460> have<01:53:41.639> referred<01:53:42.000> to<01:53:42.060> that 01:53:42.229 --> 01:53:42.239 align:start position:0% think Josh may have referred to that 01:53:42.239 --> 01:53:44.390 align:start position:0% think Josh may have referred to that elsewhere 01:53:44.390 --> 01:53:44.400 align:start position:0% elsewhere 01:53:44.400 --> 01:53:47.810 align:start position:0% elsewhere but<01:53:45.179> here<01:53:45.360> we<01:53:45.540> go<01:53:45.659> here's<01:53:46.260> a<01:53:46.380> an<01:53:46.619> image<01:53:46.920> of<01:53:47.100> one 01:53:47.810 --> 01:53:47.820 align:start position:0% but here we go here's a an image of one 01:53:47.820 --> 01:53:50.330 align:start position:0% but here we go here's a an image of one uh<01:53:48.360> using<01:53:48.659> ethernet<01:53:48.900> computer<01:53:49.320> network<01:53:49.679> that 01:53:50.330 --> 01:53:50.340 align:start position:0% uh using ethernet computer network that 01:53:50.340 --> 01:53:53.510 align:start position:0% uh using ethernet computer network that uses<01:53:50.940> the<01:53:51.239> twisted<01:53:51.719> pair<01:53:52.400> cables<01:53:53.400> for 01:53:53.510 --> 01:53:53.520 align:start position:0% uses the twisted pair cables for 01:53:53.520 --> 01:53:54.950 align:start position:0% uses the twisted pair cables for connection<01:53:53.760> which<01:53:54.300> is<01:53:54.420> pretty<01:53:54.600> much<01:53:54.719> every 01:53:54.950 --> 01:53:54.960 align:start position:0% connection which is pretty much every 01:53:54.960 --> 01:53:57.290 align:start position:0% connection which is pretty much every Network<01:53:55.260> now<01:53:55.619> unless<01:53:55.920> you<01:53:56.219> went<01:53:56.880> into<01:53:57.060> some 01:53:57.290 --> 01:53:57.300 align:start position:0% Network now unless you went into some 01:53:57.300 --> 01:53:58.790 align:start position:0% Network now unless you went into some old<01:53:57.540> basement 01:53:58.790 --> 01:53:58.800 align:start position:0% old basement 01:53:58.800 --> 01:54:02.090 align:start position:0% old basement um<01:53:58.920> or<01:53:59.159> some<01:53:59.340> odd<01:53:59.639> unit<01:53:59.820> somewhere 01:54:02.090 --> 01:54:02.100 align:start position:0% um or some odd unit somewhere 01:54:02.100 --> 01:54:04.910 align:start position:0% um or some odd unit somewhere commonly<01:54:02.760> referred<01:54:03.000> to<01:54:03.119> as<01:54:03.239> RJ45<01:54:04.139> it 01:54:04.910 --> 01:54:04.920 align:start position:0% commonly referred to as RJ45 it 01:54:04.920 --> 01:54:07.609 align:start position:0% commonly referred to as RJ45 it resembles<01:54:05.460> the<01:54:06.060> connectors<01:54:06.719> you'd<01:54:07.020> have<01:54:07.199> on 01:54:07.609 --> 01:54:07.619 align:start position:0% resembles the connectors you'd have on 01:54:07.619 --> 01:54:09.890 align:start position:0% resembles the connectors you'd have on many<01:54:07.860> phones<01:54:08.639> we<01:54:08.760> have<01:54:08.940> at<01:54:09.119> home<01:54:09.239> which<01:54:09.600> uses 01:54:09.890 --> 01:54:09.900 align:start position:0% many phones we have at home which uses 01:54:09.900 --> 01:54:11.830 align:start position:0% many phones we have at home which uses an<01:54:10.139> RJ<01:54:10.500> 11 01:54:11.830 --> 01:54:11.840 align:start position:0% an RJ 11 01:54:11.840 --> 01:54:15.050 align:start position:0% an RJ 11 telephone<01:54:12.840> cables<01:54:13.679> But<01:54:14.159> as<01:54:14.340> time<01:54:14.580> goes<01:54:14.940> on 01:54:15.050 --> 01:54:15.060 align:start position:0% telephone cables But as time goes on 01:54:15.060 --> 01:54:16.609 align:start position:0% telephone cables But as time goes on these<01:54:15.300> will<01:54:15.420> all<01:54:15.600> be<01:54:15.719> changing<01:54:16.080> and<01:54:16.199> I<01:54:16.380> think<01:54:16.500> a 01:54:16.609 --> 01:54:16.619 align:start position:0% these will all be changing and I think a 01:54:16.619 --> 01:54:18.530 align:start position:0% these will all be changing and I think a lot<01:54:16.679> of<01:54:16.800> people<01:54:16.860> don't<01:54:17.100> really<01:54:17.400> even<01:54:18.300> use 01:54:18.530 --> 01:54:18.540 align:start position:0% lot of people don't really even use 01:54:18.540 --> 01:54:21.350 align:start position:0% lot of people don't really even use their<01:54:18.780> home<01:54:19.020> phones<01:54:19.440> much<01:54:19.980> anymore 01:54:21.350 --> 01:54:21.360 align:start position:0% their home phones much anymore 01:54:21.360 --> 01:54:23.510 align:start position:0% their home phones much anymore uh<01:54:22.260> has<01:54:22.500> nothing<01:54:22.679> to<01:54:22.980> do<01:54:23.100> with<01:54:23.219> the<01:54:23.340> actual 01:54:23.510 --> 01:54:23.520 align:start position:0% uh has nothing to do with the actual 01:54:23.520 --> 01:54:26.629 align:start position:0% uh has nothing to do with the actual RJ45<01:54:24.480> standard 01:54:26.629 --> 01:54:26.639 align:start position:0% RJ45 standard 01:54:26.639 --> 01:54:30.830 align:start position:0% RJ45 standard looking<01:54:27.179> at<01:54:27.480> the<01:54:28.260> um<01:54:28.639> t568<01:54:29.639> A<01:54:29.940> and<01:54:30.179> B<01:54:30.300> wiring 01:54:30.830 --> 01:54:30.840 align:start position:0% looking at the um t568 A and B wiring 01:54:30.840 --> 01:54:32.090 align:start position:0% looking at the um t568 A and B wiring schemes 01:54:32.090 --> 01:54:32.100 align:start position:0% schemes 01:54:32.100 --> 01:54:34.729 align:start position:0% schemes these<01:54:33.000> are<01:54:33.119> the<01:54:33.600> specifications<01:54:34.139> in<01:54:34.560> more 01:54:34.729 --> 01:54:34.739 align:start position:0% these are the specifications in more 01:54:34.739 --> 01:54:37.910 align:start position:0% these are the specifications in more detail<01:54:35.100> it's<01:54:35.460> a<01:54:35.639> four<01:54:35.820> pair<01:54:36.179> 100<01:54:36.840> ohm<01:54:37.440> and 01:54:37.910 --> 01:54:37.920 align:start position:0% detail it's a four pair 100 ohm and 01:54:37.920 --> 01:54:40.129 align:start position:0% detail it's a four pair 100 ohm and shielded<01:54:38.400> twisted<01:54:38.760> their<01:54:39.000> cable 01:54:40.129 --> 01:54:40.139 align:start position:0% shielded twisted their cable 01:54:40.139 --> 01:54:41.390 align:start position:0% shielded twisted their cable and 01:54:41.390 --> 01:54:41.400 align:start position:0% and 01:54:41.400 --> 01:54:43.790 align:start position:0% and usually<01:54:42.060> terminated<01:54:42.659> into<01:54:43.080> an<01:54:43.440> a<01:54:43.560> position 01:54:43.790 --> 01:54:43.800 align:start position:0% usually terminated into an a position 01:54:43.800 --> 01:54:45.890 align:start position:0% usually terminated into an a position modular<01:54:44.460> Jack 01:54:45.890 --> 01:54:45.900 align:start position:0% modular Jack 01:54:45.900 --> 01:54:48.470 align:start position:0% modular Jack now<01:54:46.320> there's<01:54:46.500> two<01:54:46.679> wiring<01:54:47.040> schemes<01:54:47.520> five<01:54:48.239> six 01:54:48.470 --> 01:54:48.480 align:start position:0% now there's two wiring schemes five six 01:54:48.480 --> 01:54:50.810 align:start position:0% now there's two wiring schemes five six eight<01:54:48.659> a<01:54:48.960> five<01:54:49.320> six<01:54:49.560> eight<01:54:49.739> B 01:54:50.810 --> 01:54:50.820 align:start position:0% eight a five six eight B 01:54:50.820 --> 01:54:52.729 align:start position:0% eight a five six eight B this<01:54:51.300> defines<01:54:51.719> the<01:54:51.840> pin<01:54:52.080> out<01:54:52.260> and<01:54:52.500> the<01:54:52.679> Order 01:54:52.729 --> 01:54:52.739 align:start position:0% this defines the pin out and the Order 01:54:52.739 --> 01:54:54.709 align:start position:0% this defines the pin out and the Order of<01:54:52.980> the<01:54:53.100> connections<01:54:53.699> and<01:54:54.239> this<01:54:54.420> is<01:54:54.480> very 01:54:54.709 --> 01:54:54.719 align:start position:0% of the connections and this is very 01:54:54.719 --> 01:54:56.510 align:start position:0% of the connections and this is very important<01:54:55.080> we<01:54:55.320> can't<01:54:55.500> just<01:54:55.739> connect<01:54:55.920> any 01:54:56.510 --> 01:54:56.520 align:start position:0% important we can't just connect any 01:54:56.520 --> 01:54:58.850 align:start position:0% important we can't just connect any color<01:54:56.820> cable 01:54:58.850 --> 01:54:58.860 align:start position:0% color cable 01:54:58.860 --> 01:55:01.070 align:start position:0% color cable um<01:54:58.980> inside<01:54:59.280> and<01:54:59.820> attach<01:55:00.060> them<01:55:00.179> to<01:55:00.420> any<01:55:00.600> of<01:55:00.960> the 01:55:01.070 --> 01:55:01.080 align:start position:0% um inside and attach them to any of the 01:55:01.080 --> 01:55:04.010 align:start position:0% um inside and attach them to any of the pins<01:55:01.520> on<01:55:02.520> them<01:55:02.699> on<01:55:03.000> the<01:55:03.179> end<01:55:03.300> there<01:55:03.659> has<01:55:03.840> to<01:55:03.900> be 01:55:04.010 --> 01:55:04.020 align:start position:0% pins on them on the end there has to be 01:55:04.020 --> 01:55:06.830 align:start position:0% pins on them on the end there has to be a<01:55:04.260> specific<01:55:04.820> order<01:55:05.820> depending<01:55:06.480> on<01:55:06.600> what<01:55:06.719> we're 01:55:06.830 --> 01:55:06.840 align:start position:0% a specific order depending on what we're 01:55:06.840 --> 01:55:08.030 align:start position:0% a specific order depending on what we're trying<01:55:06.960> to<01:55:07.139> achieve 01:55:08.030 --> 01:55:08.040 align:start position:0% trying to achieve 01:55:08.040 --> 01:55:10.910 align:start position:0% trying to achieve you<01:55:08.699> can<01:55:08.880> obviously<01:55:09.360> buy<01:55:09.600> the<01:55:09.840> cable<01:55:10.139> it<01:55:10.560> comes 01:55:10.910 --> 01:55:10.920 align:start position:0% you can obviously buy the cable it comes 01:55:10.920 --> 01:55:14.390 align:start position:0% you can obviously buy the cable it comes off<01:55:11.520> um<01:55:11.520> big<01:55:12.020> rolls<01:55:13.020> it<01:55:13.920> could<01:55:14.100> be<01:55:14.219> a<01:55:14.280> few 01:55:14.390 --> 01:55:14.400 align:start position:0% off um big rolls it could be a few 01:55:14.400 --> 01:55:16.910 align:start position:0% off um big rolls it could be a few hundred<01:55:14.580> meters<01:55:14.940> long<01:55:15.239> and<01:55:16.199> it's<01:55:16.380> twisted 01:55:16.910 --> 01:55:16.920 align:start position:0% hundred meters long and it's twisted 01:55:16.920 --> 01:55:20.629 align:start position:0% hundred meters long and it's twisted into<01:55:17.400> one<01:55:18.119> two<01:55:18.360> three<01:55:18.780> four<01:55:19.260> pairs<01:55:19.679> there 01:55:20.629 --> 01:55:20.639 align:start position:0% into one two three four pairs there 01:55:20.639 --> 01:55:23.090 align:start position:0% into one two three four pairs there and<01:55:21.239> they<01:55:21.780> can<01:55:21.900> be<01:55:22.020> just<01:55:22.199> untwisted<01:55:22.739> slightly 01:55:23.090 --> 01:55:23.100 align:start position:0% and they can be just untwisted slightly 01:55:23.100 --> 01:55:25.010 align:start position:0% and they can be just untwisted slightly at<01:55:23.280> the<01:55:23.400> end<01:55:23.520> and<01:55:24.060> then<01:55:24.179> the<01:55:24.420> you<01:55:24.659> can<01:55:24.719> see<01:55:24.840> the 01:55:25.010 --> 01:55:25.020 align:start position:0% at the end and then the you can see the 01:55:25.020 --> 01:55:27.169 align:start position:0% at the end and then the you can see the blue<01:55:25.260> shielding<01:55:25.860> there<01:55:26.100> is<01:55:26.820> normally 01:55:27.169 --> 01:55:27.179 align:start position:0% blue shielding there is normally 01:55:27.179 --> 01:55:30.649 align:start position:0% blue shielding there is normally inserted<01:55:27.780> just<01:55:28.560> enough<01:55:28.800> so<01:55:29.219> it<01:55:29.940> um<01:55:29.940> catches 01:55:30.649 --> 01:55:30.659 align:start position:0% inserted just enough so it um catches 01:55:30.659 --> 01:55:32.149 align:start position:0% inserted just enough so it um catches inside<01:55:30.900> the<01:55:31.199> Jack<01:55:31.380> and<01:55:31.619> then<01:55:31.739> you've<01:55:31.920> got<01:55:31.980> a 01:55:32.149 --> 01:55:32.159 align:start position:0% inside the Jack and then you've got a 01:55:32.159 --> 01:55:34.850 align:start position:0% inside the Jack and then you've got a crimping<01:55:32.580> tool<01:55:33.000> which<01:55:33.719> squeezes<01:55:34.260> it<01:55:34.440> onto<01:55:34.679> the 01:55:34.850 --> 01:55:34.860 align:start position:0% crimping tool which squeezes it onto the 01:55:34.860 --> 01:55:38.689 align:start position:0% crimping tool which squeezes it onto the plastic<01:55:35.580> connector<01:55:36.540> on<01:55:36.659> the<01:55:36.780> end 01:55:38.689 --> 01:55:38.699 align:start position:0% plastic connector on the end 01:55:38.699 --> 01:55:41.030 align:start position:0% plastic connector on the end now<01:55:39.179> we<01:55:39.420> as<01:55:39.840> I<01:55:40.020> said<01:55:40.139> we<01:55:40.320> need<01:55:40.440> to<01:55:40.500> know<01:55:40.679> which 01:55:41.030 --> 01:55:41.040 align:start position:0% now we as I said we need to know which 01:55:41.040 --> 01:55:42.890 align:start position:0% now we as I said we need to know which wire<01:55:41.280> of<01:55:41.520> the<01:55:41.639> cable<01:55:41.820> connects<01:55:42.300> to<01:55:42.360> which<01:55:42.540> pin 01:55:42.890 --> 01:55:42.900 align:start position:0% wire of the cable connects to which pin 01:55:42.900 --> 01:55:46.450 align:start position:0% wire of the cable connects to which pin and<01:55:43.380> which<01:55:43.619> wiring<01:55:44.040> standards<01:55:44.580> we<01:55:44.880> use<01:55:45.119> the<01:55:46.440> um 01:55:46.450 --> 01:55:46.460 align:start position:0% and which wiring standards we use the um 01:55:46.460 --> 01:55:49.609 align:start position:0% and which wiring standards we use the um t568<01:55:47.460> A<01:55:47.699> and<01:55:47.820> B<01:55:48.000> standards<01:55:48.600> govern<01:55:49.320> the 01:55:49.609 --> 01:55:49.619 align:start position:0% t568 A and B standards govern the 01:55:49.619 --> 01:55:51.169 align:start position:0% t568 A and B standards govern the assignments<01:55:50.159> of<01:55:50.219> the<01:55:50.400> wires<01:55:50.699> so<01:55:50.880> it<01:55:51.000> says 01:55:51.169 --> 01:55:51.179 align:start position:0% assignments of the wires so it says 01:55:51.179 --> 01:55:53.390 align:start position:0% assignments of the wires so it says which<01:55:51.360> wires<01:55:51.780> go<01:55:52.020> where 01:55:53.390 --> 01:55:53.400 align:start position:0% which wires go where 01:55:53.400 --> 01:55:57.109 align:start position:0% which wires go where now<01:55:54.060> here's<01:55:54.600> a<01:55:54.780> graphic<01:55:55.500> you<01:55:55.920> can<01:55:56.040> see<01:55:56.400> and<01:55:56.880> the 01:55:57.109 --> 01:55:57.119 align:start position:0% now here's a graphic you can see and the 01:55:57.119 --> 01:55:59.629 align:start position:0% now here's a graphic you can see and the pairs<01:55:57.540> are<01:55:57.780> put<01:55:57.960> together<01:55:58.280> with<01:55:59.280> similar 01:55:59.629 --> 01:55:59.639 align:start position:0% pairs are put together with similar 01:55:59.639 --> 01:56:02.390 align:start position:0% pairs are put together with similar colors<01:56:00.060> and<01:56:00.840> then<01:56:01.020> the<01:56:01.260> specific<01:56:01.679> colors 01:56:02.390 --> 01:56:02.400 align:start position:0% colors and then the specific colors 01:56:02.400 --> 01:56:05.270 align:start position:0% colors and then the specific colors allocated<01:56:02.940> for<01:56:03.300> each<01:56:03.540> pin<01:56:03.900> going<01:56:04.619> from<01:56:04.860> one<01:56:05.100> to 01:56:05.270 --> 01:56:05.280 align:start position:0% allocated for each pin going from one to 01:56:05.280 --> 01:56:07.010 align:start position:0% allocated for each pin going from one to eight<01:56:05.520> so 01:56:07.010 --> 01:56:07.020 align:start position:0% eight so 01:56:07.020 --> 01:56:08.750 align:start position:0% eight so um<01:56:07.080> white<01:56:07.380> and<01:56:07.560> green<01:56:07.739> green<01:56:08.100> white<01:56:08.520> and 01:56:08.750 --> 01:56:08.760 align:start position:0% um white and green green white and 01:56:08.760 --> 01:56:10.430 align:start position:0% um white and green green white and orange 01:56:10.430 --> 01:56:10.440 align:start position:0% orange 01:56:10.440 --> 01:56:14.510 align:start position:0% orange and<01:56:11.040> blue<01:56:11.659> white<01:56:12.659> and<01:56:12.900> blue<01:56:13.139> orange 01:56:14.510 --> 01:56:14.520 align:start position:0% and blue white and blue orange 01:56:14.520 --> 01:56:17.870 align:start position:0% and blue white and blue orange white<01:56:15.000> and<01:56:15.179> brown<01:56:15.360> and<01:56:15.659> then<01:56:15.780> Brown 01:56:17.870 --> 01:56:17.880 align:start position:0% white and brown and then Brown 01:56:17.880 --> 01:56:19.490 align:start position:0% white and brown and then Brown you<01:56:18.239> can<01:56:18.360> see<01:56:18.480> different<01:56:18.659> pins<01:56:18.960> on<01:56:19.260> the<01:56:19.380> right 01:56:19.490 --> 01:56:19.500 align:start position:0% you can see different pins on the right 01:56:19.500 --> 01:56:21.470 align:start position:0% you can see different pins on the right because<01:56:19.980> we've<01:56:20.219> got<01:56:20.400> a<01:56:20.639> different<01:56:20.880> standard 01:56:21.470 --> 01:56:21.480 align:start position:0% because we've got a different standard 01:56:21.480 --> 01:56:23.810 align:start position:0% because we've got a different standard yes<01:56:21.780> and<01:56:22.020> I've<01:56:22.260> put<01:56:22.800> on<01:56:23.040> here<01:56:23.219> which<01:56:23.460> one's 01:56:23.810 --> 01:56:23.820 align:start position:0% yes and I've put on here which one's 01:56:23.820 --> 01:56:24.830 align:start position:0% yes and I've put on here which one's which 01:56:24.830 --> 01:56:24.840 align:start position:0% which 01:56:24.840 --> 01:56:26.870 align:start position:0% which so<01:56:25.260> there's<01:56:25.440> an<01:56:25.619> interchange<01:56:26.040> of<01:56:26.340> green<01:56:26.639> and 01:56:26.870 --> 01:56:26.880 align:start position:0% so there's an interchange of green and 01:56:26.880 --> 01:56:28.910 align:start position:0% so there's an interchange of green and orange<01:56:27.119> wire<01:56:27.600> pairs<01:56:28.199> between<01:56:28.560> the<01:56:28.800> two 01:56:28.910 --> 01:56:28.920 align:start position:0% orange wire pairs between the two 01:56:28.920 --> 01:56:32.629 align:start position:0% orange wire pairs between the two different<01:56:29.159> standards 01:56:32.629 --> 01:56:32.639 align:start position:0% 01:56:32.639 --> 01:56:35.330 align:start position:0% now<01:56:33.420> I'll<01:56:33.840> come<01:56:34.020> to<01:56:34.139> horizontal<01:56:34.619> cables<01:56:35.040> in<01:56:35.219> a 01:56:35.330 --> 01:56:35.340 align:start position:0% now I'll come to horizontal cables in a 01:56:35.340 --> 01:56:36.030 align:start position:0% now I'll come to horizontal cables in a minute<01:56:35.460> because 01:56:36.030 --> 01:56:36.040 align:start position:0% minute because 01:56:36.040 --> 01:56:36.410 align:start position:0% minute because [Music] 01:56:36.410 --> 01:56:36.420 align:start position:0% [Music] 01:56:36.420 --> 01:56:37.189 align:start position:0% [Music] um 01:56:37.189 --> 01:56:37.199 align:start position:0% um 01:56:37.199 --> 01:56:40.850 align:start position:0% um you<01:56:38.100> don't<01:56:38.219> actually<01:56:38.600> hear<01:56:39.600> this 01:56:40.850 --> 01:56:40.860 align:start position:0% you don't actually hear this 01:56:40.860 --> 01:56:43.550 align:start position:0% you don't actually hear this um<01:56:40.920> term<01:56:41.340> very<01:56:41.639> often<01:56:42.000> in<01:56:42.900> Internet<01:56:43.199> working 01:56:43.550 --> 01:56:43.560 align:start position:0% um term very often in Internet working 01:56:43.560 --> 01:56:46.729 align:start position:0% um term very often in Internet working and<01:56:43.920> I<01:56:44.100> hadn't<01:56:44.400> heard<01:56:44.580> of<01:56:44.760> it<01:56:44.880> for<01:56:45.840> um<01:56:45.840> until<01:56:46.500> I 01:56:46.729 --> 01:56:46.739 align:start position:0% and I hadn't heard of it for um until I 01:56:46.739 --> 01:56:48.649 align:start position:0% and I hadn't heard of it for um until I come<01:56:46.860> to<01:56:46.980> put<01:56:47.159> all<01:56:47.280> the<01:56:47.400> information<01:56:47.580> together 01:56:48.649 --> 01:56:48.659 align:start position:0% come to put all the information together 01:56:48.659 --> 01:56:51.350 align:start position:0% come to put all the information together for<01:56:49.199> the<01:56:49.380> presentation<01:56:50.100> but<01:56:51.000> it's<01:56:51.179> a 01:56:51.350 --> 01:56:51.360 align:start position:0% for the presentation but it's a 01:56:51.360 --> 01:56:53.030 align:start position:0% for the presentation but it's a recognized<01:56:52.020> name<01:56:52.199> even<01:56:52.440> though<01:56:52.619> it<01:56:52.739> isn't 01:56:53.030 --> 01:56:53.040 align:start position:0% recognized name even though it isn't 01:56:53.040 --> 01:56:55.189 align:start position:0% recognized name even though it isn't used<01:56:53.280> very<01:56:53.639> often 01:56:55.189 --> 01:56:55.199 align:start position:0% used very often 01:56:55.199 --> 01:56:58.970 align:start position:0% used very often so<01:56:55.920> the<01:56:56.880> um<01:56:56.880> 568b<01:56:57.780> pin<01:56:58.080> app<01:56:58.199> became<01:56:58.500> model<01:56:58.679> used 01:56:58.970 --> 01:56:58.980 align:start position:0% so the um 568b pin app became model used 01:56:58.980 --> 01:57:01.669 align:start position:0% so the um 568b pin app became model used because<01:56:59.280> it<01:56:59.520> matched<01:56:59.880> the<01:57:00.000> older<01:57:00.360> at<01:57:00.659> T<01:57:01.139> their 01:57:01.669 --> 01:57:01.679 align:start position:0% because it matched the older at T their 01:57:01.679 --> 01:57:03.229 align:start position:0% because it matched the older at T their pin<01:57:02.040> outs<01:57:02.280> and<01:57:02.400> you<01:57:02.520> can<01:57:02.580> see<01:57:02.699> the<01:57:02.880> standard 01:57:03.229 --> 01:57:03.239 align:start position:0% pin outs and you can see the standard 01:57:03.239 --> 01:57:06.470 align:start position:0% pin outs and you can see the standard there<01:57:04.020> widely<01:57:04.800> used<01:57:04.920> a<01:57:05.100> new<01:57:05.219> TP<01:57:05.580> Cable<01:57:05.940> in<01:57:06.179> at 01:57:06.470 --> 01:57:06.480 align:start position:0% there widely used a new TP Cable in at 01:57:06.480 --> 01:57:09.310 align:start position:0% there widely used a new TP Cable in at the<01:57:06.659> time<01:57:06.900> and<01:57:07.380> the<01:57:08.119> infrastructure 01:57:09.310 --> 01:57:09.320 align:start position:0% the time and the infrastructure 01:57:09.320 --> 01:57:13.370 align:start position:0% the time and the infrastructure regulations<01:57:10.320> and<01:57:10.860> numbers<01:57:11.040> were<01:57:11.460> published 01:57:13.370 --> 01:57:13.380 align:start position:0% regulations and numbers were published 01:57:13.380 --> 01:57:15.050 align:start position:0% regulations and numbers were published just<01:57:13.800> for<01:57:13.980> your<01:57:14.159> information<01:57:14.280> you<01:57:14.940> can 01:57:15.050 --> 01:57:15.060 align:start position:0% just for your information you can 01:57:15.060 --> 01:57:16.729 align:start position:0% just for your information you can research<01:57:15.540> in<01:57:15.719> your<01:57:15.900> own<01:57:16.020> time<01:57:16.139> if<01:57:16.440> you<01:57:16.560> want 01:57:16.729 --> 01:57:16.739 align:start position:0% research in your own time if you want 01:57:16.739 --> 01:57:19.070 align:start position:0% research in your own time if you want but<01:57:17.280> you<01:57:17.400> can<01:57:17.520> see<01:57:17.639> a<01:57:17.820> horizontal<01:57:18.300> cabling<01:57:18.780> in 01:57:19.070 --> 01:57:19.080 align:start position:0% but you can see a horizontal cabling in 01:57:19.080 --> 01:57:21.410 align:start position:0% but you can see a horizontal cabling in action<01:57:19.260> here<01:57:19.560> generally<01:57:20.400> it's<01:57:20.699> the<01:57:21.000> cabling 01:57:21.410 --> 01:57:21.420 align:start position:0% action here generally it's the cabling 01:57:21.420 --> 01:57:23.390 align:start position:0% action here generally it's the cabling that<01:57:21.719> runs<01:57:22.020> between<01:57:22.320> all<01:57:22.679> the<01:57:22.860> user<01:57:23.159> devices 01:57:23.390 --> 01:57:23.400 align:start position:0% that runs between all the user devices 01:57:23.400 --> 01:57:25.430 align:start position:0% that runs between all the user devices the<01:57:23.820> patch<01:57:24.179> panels<01:57:24.480> and<01:57:25.139> the<01:57:25.320> network 01:57:25.430 --> 01:57:25.440 align:start position:0% the patch panels and the network 01:57:25.440 --> 01:57:27.770 align:start position:0% the patch panels and the network switches<01:57:26.159> now<01:57:27.060> however<01:57:27.360> you've<01:57:27.540> got<01:57:27.659> your 01:57:27.770 --> 01:57:27.780 align:start position:0% switches now however you've got your 01:57:27.780 --> 01:57:29.209 align:start position:0% switches now however you've got your network<01:57:27.960> designs<01:57:28.560> you'll<01:57:28.800> normally<01:57:28.980> group 01:57:29.209 --> 01:57:29.219 align:start position:0% network designs you'll normally group 01:57:29.219 --> 01:57:30.890 align:start position:0% network designs you'll normally group the<01:57:29.460> switches<01:57:29.820> together<01:57:30.060> with<01:57:30.480> what's<01:57:30.719> known 01:57:30.890 --> 01:57:30.900 align:start position:0% the switches together with what's known 01:57:30.900 --> 01:57:33.070 align:start position:0% the switches together with what's known as<01:57:31.139> backbone<01:57:31.560> cabling 01:57:33.070 --> 01:57:33.080 align:start position:0% as backbone cabling 01:57:33.080 --> 01:57:37.550 align:start position:0% as backbone cabling so<01:57:34.080> that's<01:57:34.560> it<01:57:34.800> in<01:57:35.400> um<01:57:35.420> image<01:57:36.420> format<01:57:36.960> there's 01:57:37.550 --> 01:57:37.560 align:start position:0% so that's it in um image format there's 01:57:37.560 --> 01:57:40.669 align:start position:0% so that's it in um image format there's a<01:57:37.739> definition<01:57:37.920> which<01:57:38.520> I<01:57:38.760> got<01:57:39.179> from<01:57:39.420> Wikipedia 01:57:40.669 --> 01:57:40.679 align:start position:0% a definition which I got from Wikipedia 01:57:40.679 --> 01:57:43.370 align:start position:0% a definition which I got from Wikipedia it<01:57:41.219> can<01:57:41.400> be<01:57:41.520> the<01:57:41.820> inside<01:57:42.119> wiring<01:57:42.780> or<01:57:43.020> plenum 01:57:43.370 --> 01:57:43.380 align:start position:0% it can be the inside wiring or plenum 01:57:43.380 --> 01:57:45.649 align:start position:0% it can be the inside wiring or plenum Cable<01:57:43.739> in<01:57:44.040> connects<01:57:44.639> your<01:57:44.699> telecoms<01:57:45.239> rooms<01:57:45.540> to 01:57:45.649 --> 01:57:45.659 align:start position:0% Cable in connects your telecoms rooms to 01:57:45.659 --> 01:57:47.689 align:start position:0% Cable in connects your telecoms rooms to individual<01:57:46.199> Outlets<01:57:46.679> or<01:57:46.800> work<01:57:47.040> areas<01:57:47.400> on<01:57:47.580> the 01:57:47.689 --> 01:57:47.699 align:start position:0% individual Outlets or work areas on the 01:57:47.699 --> 01:57:50.149 align:start position:0% individual Outlets or work areas on the floor<01:57:47.820> usually<01:57:48.540> Through<01:57:48.719> the<01:57:48.900> Wire<01:57:49.080> ways<01:57:49.619> so 01:57:50.149 --> 01:57:50.159 align:start position:0% floor usually Through the Wire ways so 01:57:50.159 --> 01:57:52.250 align:start position:0% floor usually Through the Wire ways so this<01:57:50.400> is<01:57:50.520> the<01:57:50.760> part<01:57:51.000> of<01:57:51.179> the<01:57:51.360> cabling<01:57:51.840> that<01:57:52.139> you 01:57:52.250 --> 01:57:52.260 align:start position:0% this is the part of the cabling that you 01:57:52.260 --> 01:57:53.510 align:start position:0% this is the part of the cabling that you would<01:57:52.440> normally 01:57:53.510 --> 01:57:53.520 align:start position:0% would normally 01:57:53.520 --> 01:57:54.709 align:start position:0% would normally um be<01:57:53.760> concerned<01:57:54.119> with<01:57:54.179> as<01:57:54.420> a<01:57:54.599> network 01:57:54.709 --> 01:57:54.719 align:start position:0% um be concerned with as a network 01:57:54.719 --> 01:57:57.649 align:start position:0% um be concerned with as a network engineer<01:57:55.320> and<01:57:56.159> then<01:57:56.760> um<01:57:56.760> the<01:57:57.000> core<01:57:57.119> Cable<01:57:57.480> in 01:57:57.649 --> 01:57:57.659 align:start position:0% engineer and then um the core Cable in 01:57:57.659 --> 01:58:00.649 align:start position:0% engineer and then um the core Cable in the<01:57:57.840> backbone<01:57:58.139> cabling<01:57:58.560> May<01:57:59.099> well<01:57:59.280> be<01:57:59.520> done<01:57:59.760> by 01:58:00.649 --> 01:58:00.659 align:start position:0% the backbone cabling May well be done by 01:58:00.659 --> 01:58:02.750 align:start position:0% the backbone cabling May well be done by a<01:58:00.840> cabling<01:58:01.320> company<01:58:01.679> it's<01:58:02.280> not<01:58:02.520> something 01:58:02.750 --> 01:58:02.760 align:start position:0% a cabling company it's not something 01:58:02.760 --> 01:58:04.729 align:start position:0% a cabling company it's not something that<01:58:03.179> you<01:58:03.420> would<01:58:03.719> normally<01:58:04.020> get<01:58:04.260> involved<01:58:04.619> in 01:58:04.729 --> 01:58:04.739 align:start position:0% that you would normally get involved in 01:58:04.739 --> 01:58:07.370 align:start position:0% that you would normally get involved in again<01:58:05.159> it<01:58:05.460> depends<01:58:05.820> every<01:58:05.940> networks<01:58:06.540> a<01:58:07.199> bit 01:58:07.370 --> 01:58:07.380 align:start position:0% again it depends every networks a bit 01:58:07.380 --> 01:58:08.510 align:start position:0% again it depends every networks a bit different 01:58:08.510 --> 01:58:08.520 align:start position:0% different 01:58:08.520 --> 01:58:12.350 align:start position:0% different and<01:58:09.000> moving<01:58:09.360> on<01:58:09.540> to<01:58:09.719> MDI<01:58:10.380> and<01:58:10.560> MDI<01:58:11.400> X 01:58:12.350 --> 01:58:12.360 align:start position:0% and moving on to MDI and MDI X 01:58:12.360 --> 01:58:13.850 align:start position:0% and moving on to MDI and MDI X and 01:58:13.850 --> 01:58:13.860 align:start position:0% and 01:58:13.860 --> 01:58:16.189 align:start position:0% and devices<01:58:14.520> on<01:58:14.820> ethernet<01:58:15.119> networks<01:58:15.659> use<01:58:15.900> two 01:58:16.189 --> 01:58:16.199 align:start position:0% devices on ethernet networks use two 01:58:16.199 --> 01:58:18.830 align:start position:0% devices on ethernet networks use two types<01:58:16.500> of<01:58:16.619> Hardware<01:58:16.860> interfaces<01:58:17.820> which<01:58:18.719> I've 01:58:18.830 --> 01:58:18.840 align:start position:0% types of Hardware interfaces which I've 01:58:18.840 --> 01:58:21.470 align:start position:0% types of Hardware interfaces which I've already<01:58:19.020> mentioned<01:58:19.380> here<01:58:19.560> the<01:58:19.739> MDI<01:58:20.219> it<01:58:21.119> all 01:58:21.470 --> 01:58:21.480 align:start position:0% already mentioned here the MDI it all 01:58:21.480 --> 01:58:23.390 align:start position:0% already mentioned here the MDI it all stands<01:58:21.780> for<01:58:21.900> media<01:58:22.320> and<01:58:22.500> medium<01:58:22.920> dependent 01:58:23.390 --> 01:58:23.400 align:start position:0% stands for media and medium dependent 01:58:23.400 --> 01:58:24.589 align:start position:0% stands for media and medium dependent interface 01:58:24.589 --> 01:58:24.599 align:start position:0% interface 01:58:24.599 --> 01:58:26.510 align:start position:0% interface so<01:58:24.900> Hardware<01:58:25.199> interface<01:58:25.679> that<01:58:25.920> establishes 01:58:26.510 --> 01:58:26.520 align:start position:0% so Hardware interface that establishes 01:58:26.520 --> 01:58:28.790 align:start position:0% so Hardware interface that establishes the<01:58:27.000> direct<01:58:27.179> physical<01:58:27.599> and<01:58:28.199> electrical 01:58:28.790 --> 01:58:28.800 align:start position:0% the direct physical and electrical 01:58:28.800 --> 01:58:32.450 align:start position:0% the direct physical and electrical connection<01:58:29.040> with<01:58:29.580> a<01:58:29.880> UTP<01:58:30.780> cable<01:58:31.159> this<01:58:32.159> is<01:58:32.280> the 01:58:32.450 --> 01:58:32.460 align:start position:0% connection with a UTP cable this is the 01:58:32.460 --> 01:58:33.830 align:start position:0% connection with a UTP cable this is the traditional<01:58:32.820> port<01:58:33.000> on<01:58:33.300> the<01:58:33.420> back<01:58:33.480> of<01:58:33.659> a 01:58:33.830 --> 01:58:33.840 align:start position:0% traditional port on the back of a 01:58:33.840 --> 01:58:39.169 align:start position:0% traditional port on the back of a computer's<01:58:35.000> network<01:58:36.380> interface<01:58:37.380> card 01:58:39.169 --> 01:58:39.179 align:start position:0% computer's network interface card 01:58:39.179 --> 01:58:41.990 align:start position:0% computer's network interface card an<01:58:39.599> MDR<01:58:40.080> device<01:58:40.260> is<01:58:40.679> a<01:58:40.920> device<01:58:41.099> with<01:58:41.400> an<01:58:41.580> MDI 01:58:41.990 --> 01:58:42.000 align:start position:0% an MDR device is a device with an MDI 01:58:42.000 --> 01:58:44.209 align:start position:0% an MDR device is a device with an MDI Port<01:58:42.179> which<01:58:42.599> kind<01:58:42.960> of<01:58:43.080> goes<01:58:43.560> without<01:58:43.679> saying<01:58:44.099> I 01:58:44.209 --> 01:58:44.219 align:start position:0% Port which kind of goes without saying I 01:58:44.219 --> 01:58:47.629 align:start position:0% Port which kind of goes without saying I guess<01:58:44.400> a<01:58:45.300> computer<01:58:45.480> or<01:58:45.900> laptop 01:58:47.629 --> 01:58:47.639 align:start position:0% guess a computer or laptop 01:58:47.639 --> 01:58:49.010 align:start position:0% guess a computer or laptop um and<01:58:47.940> this<01:58:48.179> is<01:58:48.300> a<01:58:48.480> reference<01:58:48.780> for 01:58:49.010 --> 01:58:49.020 align:start position:0% um and this is a reference for 01:58:49.020 --> 01:58:51.229 align:start position:0% um and this is a reference for specifications<01:58:49.679> really<01:58:50.159> I<01:58:50.520> mean<01:58:50.639> in<01:58:50.880> all<01:58:51.060> the 01:58:51.229 --> 01:58:51.239 align:start position:0% specifications really I mean in all the 01:58:51.239 --> 01:58:52.790 align:start position:0% specifications really I mean in all the years<01:58:51.360> of<01:58:51.599> networking<01:58:51.960> I've<01:58:52.199> never<01:58:52.440> referred 01:58:52.790 --> 01:58:52.800 align:start position:0% years of networking I've never referred 01:58:52.800 --> 01:58:55.729 align:start position:0% years of networking I've never referred to<01:58:52.920> a<01:58:53.099> device<01:58:53.340> as<01:58:54.119> an<01:58:54.239> MDI<01:58:54.719> device 01:58:55.729 --> 01:58:55.739 align:start position:0% to a device as an MDI device 01:58:55.739 --> 01:58:58.189 align:start position:0% to a device as an MDI device and<01:58:56.219> tend<01:58:56.520> to<01:58:56.639> discuss<01:58:57.060> it<01:58:57.300> more<01:58:57.540> when<01:58:57.840> we<01:58:58.080> were 01:58:58.189 --> 01:58:58.199 align:start position:0% and tend to discuss it more when we were 01:58:58.199 --> 01:59:00.649 align:start position:0% and tend to discuss it more when we were using<01:58:58.619> Hobs 01:59:00.649 --> 01:59:00.659 align:start position:0% using Hobs 01:59:00.659 --> 01:59:03.410 align:start position:0% using Hobs um<01:59:00.780> in<01:59:01.260> the<01:59:01.380> earlier<01:59:01.619> days<01:59:01.800> of<01:59:02.040> networking<01:59:02.639> the 01:59:03.410 --> 01:59:03.420 align:start position:0% um in the earlier days of networking the 01:59:03.420 --> 01:59:06.709 align:start position:0% um in the earlier days of networking the mdix<01:59:03.900> stands<01:59:04.739> for<01:59:05.400> um<01:59:05.400> the<01:59:05.699> MDI<01:59:06.119> but<01:59:06.360> with<01:59:06.540> a 01:59:06.709 --> 01:59:06.719 align:start position:0% mdix stands for um the MDI but with a 01:59:06.719 --> 01:59:07.970 align:start position:0% mdix stands for um the MDI but with a crossover 01:59:07.970 --> 01:59:07.980 align:start position:0% crossover 01:59:07.980 --> 01:59:10.490 align:start position:0% crossover this<01:59:08.580> is<01:59:08.699> a<01:59:08.940> crossover<01:59:09.300> of<01:59:09.659> the 01:59:10.490 --> 01:59:10.500 align:start position:0% this is a crossover of the 01:59:10.500 --> 01:59:12.649 align:start position:0% this is a crossover of the um medium<01:59:10.980> dependent<01:59:11.460> interface<01:59:12.000> I'll<01:59:12.480> show 01:59:12.649 --> 01:59:12.659 align:start position:0% um medium dependent interface I'll show 01:59:12.659 --> 01:59:15.350 align:start position:0% um medium dependent interface I'll show it<01:59:12.900> up<01:59:13.020> an<01:59:13.500> image<01:59:13.800> actually<01:59:13.980> in<01:59:14.219> a<01:59:14.400> moment<01:59:14.580> the 01:59:15.350 --> 01:59:15.360 align:start position:0% it up an image actually in a moment the 01:59:15.360 --> 01:59:16.910 align:start position:0% it up an image actually in a moment the thoughts<01:59:15.719> of<01:59:15.780> the<01:59:15.900> devices<01:59:16.199> that<01:59:16.560> provide 01:59:16.910 --> 01:59:16.920 align:start position:0% thoughts of the devices that provide 01:59:16.920 --> 01:59:18.950 align:start position:0% thoughts of the devices that provide connectivity<01:59:17.580> such<01:59:18.060> as<01:59:18.179> a<01:59:18.300> switcher<01:59:18.659> hover 01:59:18.950 --> 01:59:18.960 align:start position:0% connectivity such as a switcher hover 01:59:18.960 --> 01:59:25.070 align:start position:0% connectivity such as a switcher hover setup<01:59:19.380> as<01:59:20.280> a<01:59:20.520> MDI<01:59:21.119> with<01:59:21.480> the<01:59:21.659> crossover 01:59:25.070 --> 01:59:25.080 align:start position:0% 01:59:25.080 --> 01:59:26.209 align:start position:0% foreign 01:59:26.209 --> 01:59:26.219 align:start position:0% foreign 01:59:26.219 --> 01:59:29.570 align:start position:0% foreign so<01:59:26.820> examples<01:59:27.179> of<01:59:27.360> the<01:59:27.540> devices<01:59:27.780> are<01:59:28.739> switches 01:59:29.570 --> 01:59:29.580 align:start position:0% so examples of the devices are switches 01:59:29.580 --> 01:59:32.689 align:start position:0% so examples of the devices are switches or<01:59:29.820> routers<01:59:30.360> and<01:59:31.139> I'll<01:59:31.739> put<01:59:31.920> in<01:59:32.040> an<01:59:32.219> image<01:59:32.520> here 01:59:32.689 --> 01:59:32.699 align:start position:0% or routers and I'll put in an image here 01:59:32.699 --> 01:59:35.270 align:start position:0% or routers and I'll put in an image here to<01:59:33.119> give<01:59:33.420> you<01:59:33.540> more 01:59:35.270 --> 01:59:35.280 align:start position:0% to give you more 01:59:35.280 --> 01:59:36.709 align:start position:0% to give you more um 01:59:36.709 --> 01:59:36.719 align:start position:0% um 01:59:36.719 --> 01:59:39.169 align:start position:0% um a<01:59:37.320> frame<01:59:37.800> of<01:59:37.920> reference<01:59:38.219> you<01:59:38.520> can<01:59:38.639> see<01:59:38.880> here 01:59:39.169 --> 01:59:39.179 align:start position:0% a frame of reference you can see here 01:59:39.179 --> 01:59:42.109 align:start position:0% a frame of reference you can see here it's<01:59:39.780> the<01:59:39.960> front<01:59:40.080> of<01:59:40.320> an<01:59:40.500> old<01:59:41.119> fashioned 01:59:42.109 --> 01:59:42.119 align:start position:0% it's the front of an old fashioned 01:59:42.119 --> 01:59:43.910 align:start position:0% it's the front of an old fashioned Netgear<01:59:42.780> maybe<01:59:42.960> they<01:59:43.260> don't<01:59:43.440> even<01:59:43.560> sell<01:59:43.739> him 01:59:43.910 --> 01:59:43.920 align:start position:0% Netgear maybe they don't even sell him 01:59:43.920 --> 01:59:45.589 align:start position:0% Netgear maybe they don't even sell him anymore 01:59:45.589 --> 01:59:45.599 align:start position:0% anymore 01:59:45.599 --> 01:59:47.750 align:start position:0% anymore um<01:59:45.719> Hub<01:59:46.380> and<01:59:46.980> you<01:59:47.040> can<01:59:47.159> see<01:59:47.280> to<01:59:47.520> the<01:59:47.699> right 01:59:47.750 --> 01:59:47.760 align:start position:0% um Hub and you can see to the right 01:59:47.760 --> 01:59:49.550 align:start position:0% um Hub and you can see to the right there's<01:59:48.000> a<01:59:48.179> little<01:59:48.300> black<01:59:48.540> switch<01:59:48.900> with<01:59:49.380> a 01:59:49.550 --> 01:59:49.560 align:start position:0% there's a little black switch with a 01:59:49.560 --> 01:59:51.169 align:start position:0% there's a little black switch with a little<01:59:49.739> line<01:59:49.980> that<01:59:50.219> connects<01:59:50.520> to<01:59:50.699> the<01:59:50.940> number 01:59:51.169 --> 01:59:51.179 align:start position:0% little line that connects to the number 01:59:51.179 --> 01:59:52.370 align:start position:0% little line that connects to the number four 01:59:52.370 --> 01:59:52.380 align:start position:0% four 01:59:52.380 --> 01:59:54.709 align:start position:0% four now<01:59:52.860> however<01:59:53.400> you<01:59:53.580> press<01:59:53.760> that<01:59:54.000> button<01:59:54.360> it 01:59:54.709 --> 01:59:54.719 align:start position:0% now however you press that button it 01:59:54.719 --> 01:59:58.910 align:start position:0% now however you press that button it will<01:59:54.840> act<01:59:55.199> as<01:59:55.440> an<01:59:55.619> MDI<01:59:56.520> or<01:59:57.239> an<01:59:57.360> mdix<01:59:57.960> interface 01:59:58.910 --> 01:59:58.920 align:start position:0% will act as an MDI or an mdix interface 01:59:58.920 --> 02:00:01.850 align:start position:0% will act as an MDI or an mdix interface now<01:59:59.580> if<01:59:59.820> you<01:59:59.940> wanted<02:00:00.060> to<02:00:00.300> connect<02:00:00.540> that<02:00:01.139> number 02:00:01.850 --> 02:00:01.860 align:start position:0% now if you wanted to connect that number 02:00:01.860 --> 02:00:03.890 align:start position:0% now if you wanted to connect that number four<02:00:02.099> port<02:00:02.400> to<02:00:02.699> a<02:00:02.940> PC 02:00:03.890 --> 02:00:03.900 align:start position:0% four port to a PC 02:00:03.900 --> 02:00:07.370 align:start position:0% four port to a PC you<02:00:04.440> would<02:00:04.560> leave<02:00:04.739> it<02:00:05.000> running<02:00:06.000> in<02:00:06.360> normal 02:00:07.370 --> 02:00:07.380 align:start position:0% you would leave it running in normal 02:00:07.380 --> 02:00:09.109 align:start position:0% you would leave it running in normal um mode<02:00:07.739> you<02:00:08.280> might<02:00:08.400> be<02:00:08.520> able<02:00:08.639> to<02:00:08.760> see<02:00:08.880> the 02:00:09.109 --> 02:00:09.119 align:start position:0% um mode you might be able to see the 02:00:09.119 --> 02:00:10.609 align:start position:0% um mode you might be able to see the actual<02:00:09.300> word<02:00:09.480> normal<02:00:09.719> it's<02:00:10.020> a<02:00:10.139> bit<02:00:10.260> blurry 02:00:10.609 --> 02:00:10.619 align:start position:0% actual word normal it's a bit blurry 02:00:10.619 --> 02:00:13.910 align:start position:0% actual word normal it's a bit blurry this<02:00:10.860> image<02:00:11.639> so<02:00:12.060> this<02:00:12.239> is<02:00:12.420> MDI<02:00:13.139> and<02:00:13.679> they're 02:00:13.910 --> 02:00:13.920 align:start position:0% this image so this is MDI and they're 02:00:13.920 --> 02:00:15.709 align:start position:0% this image so this is MDI and they're put<02:00:14.099> normal<02:00:14.340> because<02:00:15.179> um<02:00:15.179> You<02:00:15.659> probably 02:00:15.709 --> 02:00:15.719 align:start position:0% put normal because um You probably 02:00:15.719 --> 02:00:17.330 align:start position:0% put normal because um You probably wouldn't<02:00:15.900> be<02:00:16.080> a<02:00:16.199> network<02:00:16.320> engineer<02:00:16.800> using<02:00:17.219> it 02:00:17.330 --> 02:00:17.340 align:start position:0% wouldn't be a network engineer using it 02:00:17.340 --> 02:00:20.450 align:start position:0% wouldn't be a network engineer using it at<02:00:17.580> home<02:00:17.760> or<02:00:18.000> small<02:00:18.300> office 02:00:20.450 --> 02:00:20.460 align:start position:0% at home or small office 02:00:20.460 --> 02:00:23.870 align:start position:0% at home or small office um<02:00:20.580> the<02:00:20.880> mdix<02:00:21.420> they've<02:00:22.400> designated<02:00:23.400> as<02:00:23.699> an 02:00:23.870 --> 02:00:23.880 align:start position:0% um the mdix they've designated as an 02:00:23.880 --> 02:00:25.550 align:start position:0% um the mdix they've designated as an Uplink<02:00:24.360> that<02:00:24.599> means<02:00:24.840> you<02:00:24.960> would<02:00:25.080> connect<02:00:25.320> it 02:00:25.550 --> 02:00:25.560 align:start position:0% Uplink that means you would connect it 02:00:25.560 --> 02:00:26.930 align:start position:0% Uplink that means you would connect it to<02:00:25.739> another<02:00:25.920> hub 02:00:26.930 --> 02:00:26.940 align:start position:0% to another hub 02:00:26.940 --> 02:00:29.510 align:start position:0% to another hub and<02:00:27.480> so<02:00:27.960> the<02:00:28.199> it<02:00:28.619> would<02:00:28.800> change<02:00:28.980> the<02:00:29.219> way<02:00:29.400> it 02:00:29.510 --> 02:00:29.520 align:start position:0% and so the it would change the way it 02:00:29.520 --> 02:00:31.669 align:start position:0% and so the it would change the way it connect<02:00:29.699> and<02:00:30.239> communicates<02:00:30.960> using<02:00:31.500> the 02:00:31.669 --> 02:00:31.679 align:start position:0% connect and communicates using the 02:00:31.679 --> 02:00:34.129 align:start position:0% connect and communicates using the different<02:00:31.800> pin<02:00:32.159> outs<02:00:32.580> and<02:00:33.360> it<02:00:33.540> would<02:00:33.719> act<02:00:33.960> as 02:00:34.129 --> 02:00:34.139 align:start position:0% different pin outs and it would act as 02:00:34.139 --> 02:00:36.470 align:start position:0% different pin outs and it would act as if<02:00:34.679> um<02:00:34.679> you<02:00:34.980> you're<02:00:35.280> using<02:00:35.580> a<02:00:35.760> crossover<02:00:36.000> cable 02:00:36.470 --> 02:00:36.480 align:start position:0% if um you you're using a crossover cable 02:00:36.480 --> 02:00:42.830 align:start position:0% if um you you're using a crossover cable which<02:00:36.840> we'll<02:00:37.020> come<02:00:37.260> to<02:00:37.440> later 02:00:42.830 --> 02:00:42.840 align:start position:0% 02:00:42.840 --> 02:00:44.750 align:start position:0% so<02:00:43.440> this<02:00:43.619> is<02:00:43.739> basically<02:00:43.980> what<02:00:44.219> I've<02:00:44.340> said<02:00:44.520> it's 02:00:44.750 --> 02:00:44.760 align:start position:0% so this is basically what I've said it's 02:00:44.760 --> 02:00:47.870 align:start position:0% so this is basically what I've said it's going<02:00:45.000> to<02:00:45.480> um<02:00:45.480> using<02:00:46.020> the<02:00:46.199> button<02:00:46.619> you<02:00:47.280> would 02:00:47.870 --> 02:00:47.880 align:start position:0% going to um using the button you would 02:00:47.880 --> 02:00:49.189 align:start position:0% going to um using the button you would um designate<02:00:48.540> whether<02:00:48.659> it's<02:00:48.840> going<02:00:48.960> to<02:00:49.020> act 02:00:49.189 --> 02:00:49.199 align:start position:0% um designate whether it's going to act 02:00:49.199 --> 02:00:54.890 align:start position:0% um designate whether it's going to act as<02:00:49.380> an<02:00:49.500> MDI<02:00:49.980> or<02:00:50.400> an<02:00:50.580> MDI<02:00:51.119> X<02:00:51.599> interface 02:00:54.890 --> 02:00:54.900 align:start position:0% 02:00:54.900 --> 02:00:56.990 align:start position:0% um<02:00:54.960> this<02:00:55.440> all<02:00:55.619> basically<02:00:55.920> changes<02:00:56.400> how<02:00:56.639> we<02:00:56.820> use 02:00:56.990 --> 02:00:57.000 align:start position:0% um this all basically changes how we use 02:00:57.000 --> 02:00:59.649 align:start position:0% um this all basically changes how we use our<02:00:57.239> transmit<02:00:57.780> which<02:00:58.080> is<02:00:58.260> designated<02:00:58.739> as<02:00:58.980> TX 02:00:59.649 --> 02:00:59.659 align:start position:0% our transmit which is designated as TX 02:00:59.659 --> 02:01:02.390 align:start position:0% our transmit which is designated as TX and<02:01:00.659> I'll<02:01:00.840> receive<02:01:01.260> which<02:01:01.500> is<02:01:01.679> designated<02:01:02.159> as 02:01:02.390 --> 02:01:02.400 align:start position:0% and I'll receive which is designated as 02:01:02.400 --> 02:01:04.910 align:start position:0% and I'll receive which is designated as RX<02:01:02.940> on<02:01:03.659> the<02:01:03.780> different<02:01:03.960> wires<02:01:04.500> and<02:01:04.739> that's 02:01:04.910 --> 02:01:04.920 align:start position:0% RX on the different wires and that's 02:01:04.920 --> 02:01:07.370 align:start position:0% RX on the different wires and that's saying<02:01:05.280> what<02:01:05.580> that<02:01:05.760> setting<02:01:06.179> would<02:01:06.360> do 02:01:07.370 --> 02:01:07.380 align:start position:0% saying what that setting would do 02:01:07.380 --> 02:01:09.350 align:start position:0% saying what that setting would do straight<02:01:07.920> through<02:01:08.159> cable<02:01:08.520> the<02:01:08.940> easiest<02:01:09.179> way 02:01:09.350 --> 02:01:09.360 align:start position:0% straight through cable the easiest way 02:01:09.360 --> 02:01:12.290 align:start position:0% straight through cable the easiest way to<02:01:09.540> think<02:01:09.659> about<02:01:09.780> straight<02:01:10.139> through<02:01:10.320> cable<02:01:10.800> is 02:01:12.290 --> 02:01:12.300 align:start position:0% to think about straight through cable is 02:01:12.300 --> 02:01:14.390 align:start position:0% to think about straight through cable is um using<02:01:12.780> dissimilar<02:01:13.380> devices<02:01:13.679> for<02:01:14.099> example 02:01:14.390 --> 02:01:14.400 align:start position:0% um using dissimilar devices for example 02:01:14.400 --> 02:01:19.310 align:start position:0% um using dissimilar devices for example a<02:01:15.780> um<02:01:15.840> computer<02:01:16.739> to<02:01:17.400> a<02:01:17.880> switch<02:01:18.119> port<02:01:18.420> a<02:01:18.900> router 02:01:19.310 --> 02:01:19.320 align:start position:0% a um computer to a switch port a router 02:01:19.320 --> 02:01:23.089 align:start position:0% a um computer to a switch port a router to<02:01:19.560> a<02:01:19.860> switch 02:01:23.089 --> 02:01:23.099 align:start position:0% 02:01:23.099 --> 02:01:25.430 align:start position:0% and<02:01:23.760> here's<02:01:24.119> some<02:01:24.239> examples<02:01:24.540> also<02:01:24.960> known<02:01:25.080> as<02:01:25.320> a 02:01:25.430 --> 02:01:25.440 align:start position:0% and here's some examples also known as a 02:01:25.440 --> 02:01:27.530 align:start position:0% and here's some examples also known as a patch<02:01:25.800> cable<02:01:26.040> in<02:01:26.340> case<02:01:26.460> anyone<02:01:26.820> asks<02:01:27.179> you<02:01:27.239> to 02:01:27.530 --> 02:01:27.540 align:start position:0% patch cable in case anyone asks you to 02:01:27.540 --> 02:01:30.229 align:start position:0% patch cable in case anyone asks you to check<02:01:28.080> a<02:01:28.260> patch<02:01:28.619> cable<02:01:28.860> or<02:01:29.159> get<02:01:29.340> get<02:01:29.820> them<02:01:30.060> a 02:01:30.229 --> 02:01:30.239 align:start position:0% check a patch cable or get get them a 02:01:30.239 --> 02:01:32.209 align:start position:0% check a patch cable or get get them a patch<02:01:30.599> cable 02:01:32.209 --> 02:01:32.219 align:start position:0% patch cable 02:01:32.219 --> 02:01:35.149 align:start position:0% patch cable I've<02:01:32.820> mentioned<02:01:33.179> UTP<02:01:33.840> UTP<02:01:34.560> cables<02:01:35.040> they're 02:01:35.149 --> 02:01:35.159 align:start position:0% I've mentioned UTP UTP cables they're 02:01:35.159 --> 02:01:37.910 align:start position:0% I've mentioned UTP UTP cables they're used<02:01:35.400> in<02:01:35.520> the<02:01:35.639> modern<02:01:35.760> ethernet<02:01:36.179> Networks 02:01:37.910 --> 02:01:37.920 align:start position:0% used in the modern ethernet Networks 02:01:37.920 --> 02:01:40.370 align:start position:0% used in the modern ethernet Networks and<02:01:38.340> you<02:01:38.639> can't<02:01:38.760> directly<02:01:39.239> connect<02:01:39.599> unless 02:01:40.370 --> 02:01:40.380 align:start position:0% and you can't directly connect unless 02:01:40.380 --> 02:01:41.689 align:start position:0% and you can't directly connect unless you<02:01:40.500> stay<02:01:40.679> in<02:01:40.860> the<02:01:40.920> obvious<02:01:41.099> I<02:01:41.340> think<02:01:41.460> you 02:01:41.689 --> 02:01:41.699 align:start position:0% you stay in the obvious I think you 02:01:41.699 --> 02:01:43.370 align:start position:0% you stay in the obvious I think you can't<02:01:41.880> directly<02:01:42.239> connect<02:01:42.420> these<02:01:42.719> wires<02:01:43.020> to<02:01:43.199> a 02:01:43.370 --> 02:01:43.380 align:start position:0% can't directly connect these wires to a 02:01:43.380 --> 02:01:46.910 align:start position:0% can't directly connect these wires to a computer's<02:01:44.040> network<02:01:44.880> interface<02:01:45.420> card 02:01:46.910 --> 02:01:46.920 align:start position:0% computer's network interface card 02:01:46.920 --> 02:01:48.649 align:start position:0% computer's network interface card um<02:01:47.040> if<02:01:47.340> you<02:01:47.460> want<02:01:47.580> to<02:01:47.699> be<02:01:47.760> picky<02:01:48.060> I<02:01:48.239> suppose<02:01:48.420> you 02:01:48.649 --> 02:01:48.659 align:start position:0% um if you want to be picky I suppose you 02:01:48.659 --> 02:01:50.990 align:start position:0% um if you want to be picky I suppose you could<02:01:48.840> if<02:01:49.199> you<02:01:49.320> had<02:01:49.500> a<02:01:49.619> soldering<02:01:50.159> iron<02:01:50.340> and 02:01:50.990 --> 02:01:51.000 align:start position:0% could if you had a soldering iron and 02:01:51.000 --> 02:01:53.270 align:start position:0% could if you had a soldering iron and individually<02:01:51.480> sold<02:01:51.780> at<02:01:52.080> each<02:01:52.199> wire<02:01:52.500> but<02:01:53.099> that 02:01:53.270 --> 02:01:53.280 align:start position:0% individually sold at each wire but that 02:01:53.280 --> 02:01:55.030 align:start position:0% individually sold at each wire but that would<02:01:53.460> just<02:01:53.639> be<02:01:53.760> a<02:01:53.940> little<02:01:54.060> bit<02:01:54.179> of<02:01:54.360> a 02:01:55.030 --> 02:01:55.040 align:start position:0% would just be a little bit of a 02:01:55.040 --> 02:01:57.530 align:start position:0% would just be a little bit of a desperation<02:01:56.040> not<02:01:56.580> somebody<02:01:56.820> that<02:01:57.179> doesn't 02:01:57.530 --> 02:01:57.540 align:start position:0% desperation not somebody that doesn't 02:01:57.540 --> 02:01:59.870 align:start position:0% desperation not somebody that doesn't really<02:01:57.719> need<02:01:57.960> to<02:01:58.139> unplug 02:01:59.870 --> 02:01:59.880 align:start position:0% really need to unplug 02:01:59.880 --> 02:02:01.790 align:start position:0% really need to unplug so<02:02:00.360> both<02:02:00.599> ends<02:02:00.960> are<02:02:00.960> terminated<02:02:01.440> with<02:02:01.679> the 02:02:01.790 --> 02:02:01.800 align:start position:0% so both ends are terminated with the 02:02:01.800 --> 02:02:04.370 align:start position:0% so both ends are terminated with the 8phc<02:02:02.639> connectors 02:02:04.370 --> 02:02:04.380 align:start position:0% 8phc connectors 02:02:04.380 --> 02:02:06.229 align:start position:0% 8phc connectors and<02:02:04.860> you<02:02:04.920> can<02:02:05.040> see<02:02:05.159> the<02:02:05.340> two<02:02:05.460> wiring<02:02:05.880> types 02:02:06.229 --> 02:02:06.239 align:start position:0% and you can see the two wiring types 02:02:06.239 --> 02:02:08.930 align:start position:0% and you can see the two wiring types here<02:02:06.420> using<02:02:06.840> that<02:02:07.020> AP<02:02:07.199> AC<02:02:07.560> connectors 02:02:08.930 --> 02:02:08.940 align:start position:0% here using that AP AC connectors 02:02:08.940 --> 02:02:10.790 align:start position:0% here using that AP AC connectors now<02:02:09.360> the<02:02:09.540> pins<02:02:09.719> and<02:02:09.960> the<02:02:10.080> wire<02:02:10.139> assignments 02:02:10.790 --> 02:02:10.800 align:start position:0% now the pins and the wire assignments 02:02:10.800 --> 02:02:13.189 align:start position:0% now the pins and the wire assignments are<02:02:10.980> the<02:02:11.219> same<02:02:11.460> on<02:02:12.239> both<02:02:12.420> ends<02:02:12.780> so<02:02:12.960> we<02:02:13.080> know 02:02:13.189 --> 02:02:13.199 align:start position:0% are the same on both ends so we know 02:02:13.199 --> 02:02:14.930 align:start position:0% are the same on both ends so we know this<02:02:13.440> is<02:02:13.560> a<02:02:13.739> straight<02:02:13.920> through<02:02:14.159> cable<02:02:14.520> or<02:02:14.820> a 02:02:14.930 --> 02:02:14.940 align:start position:0% this is a straight through cable or a 02:02:14.940 --> 02:02:18.830 align:start position:0% this is a straight through cable or a patch<02:02:15.300> cable<02:02:15.739> the<02:02:16.739> numbers<02:02:17.219> match 02:02:18.830 --> 02:02:18.840 align:start position:0% patch cable the numbers match 02:02:18.840 --> 02:02:21.350 align:start position:0% patch cable the numbers match and<02:02:19.679> well<02:02:20.099> that's<02:02:20.340> just<02:02:20.520> a<02:02:20.639> number<02:02:20.940> into<02:02:21.179> the 02:02:21.350 --> 02:02:21.360 align:start position:0% and well that's just a number into the 02:02:21.360 --> 02:02:24.290 align:start position:0% and well that's just a number into the pins<02:02:21.599> the<02:02:21.960> colors<02:02:22.860> of<02:02:23.040> the<02:02:23.219> different<02:02:23.880> wires 02:02:24.290 --> 02:02:24.300 align:start position:0% pins the colors of the different wires 02:02:24.300 --> 02:02:26.570 align:start position:0% pins the colors of the different wires inside<02:02:24.480> match<02:02:25.380> and<02:02:25.860> that's<02:02:26.040> you<02:02:26.280> could<02:02:26.460> tell 02:02:26.570 --> 02:02:26.580 align:start position:0% inside match and that's you could tell 02:02:26.580 --> 02:02:29.030 align:start position:0% inside match and that's you could tell you<02:02:26.760> would<02:02:26.880> hold<02:02:27.119> the<02:02:27.480> cable<02:02:28.199> together<02:02:28.440> if<02:02:28.860> you 02:02:29.030 --> 02:02:29.040 align:start position:0% you would hold the cable together if you 02:02:29.040 --> 02:02:30.649 align:start position:0% you would hold the cable together if you didn't<02:02:29.159> know<02:02:29.460> if<02:02:29.940> you<02:02:30.000> wanted<02:02:30.119> to<02:02:30.360> see<02:02:30.480> if<02:02:30.540> it 02:02:30.649 --> 02:02:30.659 align:start position:0% didn't know if you wanted to see if it 02:02:30.659 --> 02:02:32.330 align:start position:0% didn't know if you wanted to see if it was<02:02:30.780> the<02:02:30.840> right<02:02:30.960> kind<02:02:31.199> of<02:02:31.320> cable<02:02:31.500> hold<02:02:32.040> it<02:02:32.219> up 02:02:32.330 --> 02:02:32.340 align:start position:0% was the right kind of cable hold it up 02:02:32.340 --> 02:02:34.310 align:start position:0% was the right kind of cable hold it up look<02:02:32.580> at<02:02:32.760> it<02:02:32.880> and<02:02:33.119> check<02:02:33.420> that<02:02:33.840> all<02:02:34.020> the<02:02:34.199> wire 02:02:34.310 --> 02:02:34.320 align:start position:0% look at it and check that all the wire 02:02:34.320 --> 02:02:37.189 align:start position:0% look at it and check that all the wire colors<02:02:34.800> match 02:02:37.189 --> 02:02:37.199 align:start position:0% 02:02:37.199 --> 02:02:40.270 align:start position:0% now<02:02:37.679> the<02:02:37.860> worrying<02:02:38.219> standards<02:02:38.699> for<02:02:39.000> the<02:02:39.119> RJ45 02:02:40.270 --> 02:02:40.280 align:start position:0% now the worrying standards for the RJ45 02:02:40.280 --> 02:02:44.930 align:start position:0% now the worrying standards for the RJ45 is<02:02:41.280> the<02:02:41.880> um<02:02:41.880> 568<02:02:42.719> amb<02:02:43.320> they<02:02:44.099> specify<02:02:44.520> how<02:02:44.760> to 02:02:44.930 --> 02:02:44.940 align:start position:0% is the um 568 amb they specify how to 02:02:44.940 --> 02:02:46.490 align:start position:0% is the um 568 amb they specify how to wire<02:02:45.060> the<02:02:45.360> actual<02:02:45.599> connector<02:02:46.020> over<02:02:46.260> an 02:02:46.490 --> 02:02:46.500 align:start position:0% wire the actual connector over an 02:02:46.500 --> 02:02:48.770 align:start position:0% wire the actual connector over an Ethernet<02:02:46.679> Network<02:02:47.300> technically<02:02:48.300> you<02:02:48.659> could 02:02:48.770 --> 02:02:48.780 align:start position:0% Ethernet Network technically you could 02:02:48.780 --> 02:02:51.709 align:start position:0% Ethernet Network technically you could choose<02:02:49.139> any<02:02:49.500> order<02:02:49.860> of<02:02:50.639> colors<02:02:51.060> you<02:02:51.239> like<02:02:51.420> if 02:02:51.709 --> 02:02:51.719 align:start position:0% choose any order of colors you like if 02:02:51.719 --> 02:02:53.810 align:start position:0% choose any order of colors you like if you<02:02:51.840> were<02:02:51.900> making<02:02:52.080> your<02:02:52.380> own<02:02:52.500> cables 02:02:53.810 --> 02:02:53.820 align:start position:0% you were making your own cables 02:02:53.820 --> 02:02:56.270 align:start position:0% you were making your own cables and<02:02:54.540> as<02:02:55.020> long<02:02:55.199> as<02:02:55.260> it<02:02:55.440> matched<02:02:55.800> the<02:02:55.920> other<02:02:56.099> side 02:02:56.270 --> 02:02:56.280 align:start position:0% and as long as it matched the other side 02:02:56.280 --> 02:02:58.250 align:start position:0% and as long as it matched the other side then<02:02:56.520> it<02:02:56.699> would<02:02:56.820> all<02:02:57.000> work<02:02:57.300> because<02:02:57.960> the 02:02:58.250 --> 02:02:58.260 align:start position:0% then it would all work because the 02:02:58.260 --> 02:03:00.770 align:start position:0% then it would all work because the cables<02:02:58.739> inside<02:02:58.980> the<02:02:59.340> the<02:02:59.760> eight<02:03:00.000> little<02:03:00.179> wires 02:03:00.770 --> 02:03:00.780 align:start position:0% cables inside the the eight little wires 02:03:00.780 --> 02:03:02.930 align:start position:0% cables inside the the eight little wires are<02:03:01.320> all<02:03:01.560> exactly<02:03:01.980> the<02:03:02.219> same 02:03:02.930 --> 02:03:02.940 align:start position:0% are all exactly the same 02:03:02.940 --> 02:03:04.490 align:start position:0% are all exactly the same but<02:03:03.719> um<02:03:03.719> you<02:03:03.960> wouldn't<02:03:04.020> obviously<02:03:04.380> be 02:03:04.490 --> 02:03:04.500 align:start position:0% but um you wouldn't obviously be 02:03:04.500 --> 02:03:06.530 align:start position:0% but um you wouldn't obviously be following<02:03:04.860> the<02:03:05.040> standards<02:03:05.580> so<02:03:06.179> maybe<02:03:06.360> you 02:03:06.530 --> 02:03:06.540 align:start position:0% following the standards so maybe you 02:03:06.540 --> 02:03:07.910 align:start position:0% following the standards so maybe you could<02:03:06.659> do<02:03:06.780> it<02:03:06.900> for<02:03:07.020> your<02:03:07.139> home<02:03:07.320> network<02:03:07.500> if<02:03:07.800> you 02:03:07.910 --> 02:03:07.920 align:start position:0% could do it for your home network if you 02:03:07.920 --> 02:03:09.410 align:start position:0% could do it for your home network if you wanted<02:03:08.040> to<02:03:08.219> make<02:03:08.400> your<02:03:08.520> own<02:03:08.639> cables<02:03:09.119> but 02:03:09.410 --> 02:03:09.420 align:start position:0% wanted to make your own cables but 02:03:09.420 --> 02:03:11.689 align:start position:0% wanted to make your own cables but certainly<02:03:10.380> not<02:03:10.560> recommended<02:03:11.159> for<02:03:11.400> commercial 02:03:11.689 --> 02:03:11.699 align:start position:0% certainly not recommended for commercial 02:03:11.699 --> 02:03:13.669 align:start position:0% certainly not recommended for commercial Networks 02:03:13.669 --> 02:03:13.679 align:start position:0% Networks 02:03:13.679 --> 02:03:15.470 align:start position:0% Networks so<02:03:14.219> only<02:03:14.400> one<02:03:14.639> of<02:03:14.699> the<02:03:14.820> following<02:03:15.060> standards 02:03:15.470 --> 02:03:15.480 align:start position:0% so only one of the following standards 02:03:15.480 --> 02:03:18.470 align:start position:0% so only one of the following standards used<02:03:15.719> for<02:03:15.900> terminating<02:03:16.320> ends<02:03:16.739> of<02:03:16.860> the<02:03:16.980> UTP<02:03:17.520> you 02:03:18.470 --> 02:03:18.480 align:start position:0% used for terminating ends of the UTP you 02:03:18.480 --> 02:03:21.410 align:start position:0% used for terminating ends of the UTP you could<02:03:18.540> choose<02:03:18.900> either 02:03:21.410 --> 02:03:21.420 align:start position:0% 02:03:21.420 --> 02:03:23.270 align:start position:0% and<02:03:21.960> but<02:03:22.080> I<02:03:22.260> think<02:03:22.380> I<02:03:22.500> mentioned<02:03:22.800> earlier<02:03:23.099> the 02:03:23.270 --> 02:03:23.280 align:start position:0% and but I think I mentioned earlier the 02:03:23.280 --> 02:03:24.890 align:start position:0% and but I think I mentioned earlier the recommendations<02:03:23.820> for<02:03:24.179> the<02:03:24.360> horizontal 02:03:24.890 --> 02:03:24.900 align:start position:0% recommendations for the horizontal 02:03:24.900 --> 02:03:26.270 align:start position:0% recommendations for the horizontal cables 02:03:26.270 --> 02:03:26.280 align:start position:0% cables 02:03:26.280 --> 02:03:27.649 align:start position:0% cables so<02:03:26.639> the<02:03:26.760> example<02:03:27.060> of<02:03:27.179> a<02:03:27.300> straight<02:03:27.420> through 02:03:27.649 --> 02:03:27.659 align:start position:0% so the example of a straight through 02:03:27.659 --> 02:03:31.129 align:start position:0% so the example of a straight through cable<02:03:28.020> is<02:03:28.260> computer<02:03:28.679> or<02:03:29.639> a<02:03:29.940> server<02:03:30.599> connecting 02:03:31.129 --> 02:03:31.139 align:start position:0% cable is computer or a server connecting 02:03:31.139 --> 02:03:33.770 align:start position:0% cable is computer or a server connecting into<02:03:31.320> a<02:03:31.619> switch<02:03:31.920> port 02:03:33.770 --> 02:03:33.780 align:start position:0% into a switch port 02:03:33.780 --> 02:03:35.089 align:start position:0% into a switch port I've<02:03:34.080> already<02:03:34.260> mentioned<02:03:34.619> that<02:03:34.800> you<02:03:34.980> wouldn't 02:03:35.089 --> 02:03:35.099 align:start position:0% I've already mentioned that you wouldn't 02:03:35.099 --> 02:03:41.870 align:start position:0% I've already mentioned that you wouldn't use<02:03:35.340> both<02:03:35.699> standards<02:03:36.480> on<02:03:37.199> them<02:03:37.440> on<02:03:37.739> your<02:03:37.980> cable 02:03:41.870 --> 02:03:41.880 align:start position:0% 02:03:41.880 --> 02:03:43.070 align:start position:0% straight<02:03:42.239> through<02:03:42.420> cables<02:03:42.719> are<02:03:42.840> used<02:03:42.960> when 02:03:43.070 --> 02:03:43.080 align:start position:0% straight through cables are used when 02:03:43.080 --> 02:03:45.950 align:start position:0% straight through cables are used when connecting<02:03:43.440> to<02:03:43.560> an<02:03:43.739> MDR<02:03:44.099> device<02:03:44.400> or<02:03:45.360> an<02:03:45.540> ndi 02:03:45.950 --> 02:03:45.960 align:start position:0% connecting to an MDR device or an ndi 02:03:45.960 --> 02:03:49.970 align:start position:0% connecting to an MDR device or an ndi device<02:03:46.199> to<02:03:46.440> an<02:03:46.560> mdix<02:03:47.099> device 02:03:49.970 --> 02:03:49.980 align:start position:0% 02:03:49.980 --> 02:03:51.890 align:start position:0% and<02:03:50.520> again<02:03:50.639> we've<02:03:50.940> seen<02:03:51.119> this<02:03:51.360> this<02:03:51.540> is<02:03:51.719> just 02:03:51.890 --> 02:03:51.900 align:start position:0% and again we've seen this this is just 02:03:51.900 --> 02:03:54.109 align:start position:0% and again we've seen this this is just zoomed<02:03:52.320> in<02:03:52.440> and<02:03:52.619> giving<02:03:52.800> you<02:03:53.040> a<02:03:53.280> better<02:03:53.400> and 02:03:54.109 --> 02:03:54.119 align:start position:0% zoomed in and giving you a better and 02:03:54.119 --> 02:03:57.229 align:start position:0% zoomed in and giving you a better and detailed<02:03:54.599> image<02:03:54.900> of<02:03:55.199> the<02:03:55.440> cable<02:03:55.800> type<02:03:56.159> here 02:03:57.229 --> 02:03:57.239 align:start position:0% detailed image of the cable type here 02:03:57.239 --> 02:03:58.910 align:start position:0% detailed image of the cable type here if<02:03:57.540> it's<02:03:57.719> straight<02:03:57.840> through<02:03:58.020> UTB<02:03:58.440> cable<02:03:58.739> is 02:03:58.910 --> 02:03:58.920 align:start position:0% if it's straight through UTB cable is 02:03:58.920 --> 02:04:00.830 align:start position:0% if it's straight through UTB cable is terminated<02:03:59.340> on<02:03:59.580> both<02:03:59.760> sides<02:04:00.060> using<02:04:00.420> the<02:04:00.659> type 02:04:00.830 --> 02:04:00.840 align:start position:0% terminated on both sides using the type 02:04:00.840 --> 02:04:02.270 align:start position:0% terminated on both sides using the type a<02:04:01.139> wiring 02:04:02.270 --> 02:04:02.280 align:start position:0% a wiring 02:04:02.280 --> 02:04:07.010 align:start position:0% a wiring then<02:04:02.699> the<02:04:03.060> a<02:04:03.360> color<02:04:03.780> scheme<02:04:04.320> and<02:04:04.800> should<02:04:05.340> be 02:04:07.010 --> 02:04:07.020 align:start position:0% then the a color scheme and should be 02:04:07.020 --> 02:04:08.629 align:start position:0% then the a color scheme and should be so<02:04:07.260> I'll<02:04:07.500> say<02:04:07.619> that<02:04:07.739> again<02:04:07.860> then<02:04:08.280> the<02:04:08.460> color 02:04:08.629 --> 02:04:08.639 align:start position:0% so I'll say that again then the color 02:04:08.639 --> 02:04:10.070 align:start position:0% so I'll say that again then the color scheme<02:04:09.060> and<02:04:09.119> the<02:04:09.239> pin<02:04:09.420> out<02:04:09.480> the<02:04:09.659> order<02:04:09.780> of<02:04:09.960> the 02:04:10.070 --> 02:04:10.080 align:start position:0% scheme and the pin out the order of the 02:04:10.080 --> 02:04:11.990 align:start position:0% scheme and the pin out the order of the connections<02:04:10.560> will<02:04:11.040> be<02:04:11.159> shown<02:04:11.340> in<02:04:11.520> the<02:04:11.699> diagram 02:04:11.990 --> 02:04:12.000 align:start position:0% connections will be shown in the diagram 02:04:12.000 --> 02:04:15.290 align:start position:0% connections will be shown in the diagram so<02:04:12.540> this<02:04:12.719> is<02:04:12.840> the<02:04:13.199> a<02:04:13.380> standard<02:04:13.860> and<02:04:14.639> you<02:04:15.000> do<02:04:15.179> it 02:04:15.290 --> 02:04:15.300 align:start position:0% so this is the a standard and you do it 02:04:15.300 --> 02:04:17.930 align:start position:0% so this is the a standard and you do it a<02:04:15.480> few<02:04:15.599> times 02:04:17.930 --> 02:04:17.940 align:start position:0% a few times 02:04:17.940 --> 02:04:19.550 align:start position:0% a few times um<02:04:18.000> for<02:04:18.239> a<02:04:18.360> few<02:04:18.480> days<02:04:18.659> and<02:04:18.960> then<02:04:19.080> you<02:04:19.380> probably 02:04:19.550 --> 02:04:19.560 align:start position:0% um for a few days and then you probably 02:04:19.560 --> 02:04:21.830 align:start position:0% um for a few days and then you probably have<02:04:19.980> it<02:04:20.159> in<02:04:20.280> your<02:04:20.400> memory<02:04:20.699> of<02:04:20.940> what<02:04:21.239> all<02:04:21.540> data 02:04:21.830 --> 02:04:21.840 align:start position:0% have it in your memory of what all data 02:04:21.840 --> 02:04:24.589 align:start position:0% have it in your memory of what all data put<02:04:22.020> the<02:04:22.199> wires<02:04:22.500> in<02:04:22.679> again<02:04:23.400> if<02:04:24.179> it<02:04:24.300> was<02:04:24.420> you 02:04:24.589 --> 02:04:24.599 align:start position:0% put the wires in again if it was you 02:04:24.599 --> 02:04:27.290 align:start position:0% put the wires in again if it was you making<02:04:24.840> the<02:04:25.139> cables<02:04:25.619> which<02:04:26.760> um 02:04:27.290 --> 02:04:27.300 align:start position:0% making the cables which um 02:04:27.300 --> 02:04:29.930 align:start position:0% making the cables which um wouldn't<02:04:28.139> only<02:04:28.380> really<02:04:28.679> happen<02:04:28.920> if<02:04:29.219> you<02:04:29.460> were 02:04:29.930 --> 02:04:29.940 align:start position:0% wouldn't only really happen if you were 02:04:29.940 --> 02:04:30.589 align:start position:0% wouldn't only really happen if you were um 02:04:30.589 --> 02:04:30.599 align:start position:0% um 02:04:30.599 --> 02:04:32.510 align:start position:0% um a<02:04:31.080> cabling<02:04:31.440> engineer<02:04:31.920> for<02:04:32.099> a<02:04:32.280> very<02:04:32.340> large 02:04:32.510 --> 02:04:32.520 align:start position:0% a cabling engineer for a very large 02:04:32.520 --> 02:04:33.830 align:start position:0% a cabling engineer for a very large Network 02:04:33.830 --> 02:04:33.840 align:start position:0% Network 02:04:33.840 --> 02:04:36.709 align:start position:0% Network and<02:04:34.440> there's<02:04:34.679> the<02:04:35.040> pin<02:04:35.400> outs<02:04:35.880> and<02:04:36.239> the<02:04:36.360> colors 02:04:36.709 --> 02:04:36.719 align:start position:0% and there's the pin outs and the colors 02:04:36.719 --> 02:04:38.510 align:start position:0% and there's the pin outs and the colors in<02:04:37.020> more<02:04:37.199> detail<02:04:37.560> you<02:04:37.800> can<02:04:37.980> see<02:04:38.040> the<02:04:38.280> tip 02:04:38.510 --> 02:04:38.520 align:start position:0% in more detail you can see the tip 02:04:38.520 --> 02:04:42.649 align:start position:0% in more detail you can see the tip transmit<02:04:39.080> and<02:04:40.080> the<02:04:40.560> um<02:04:40.560> receive<02:04:41.659> indications 02:04:42.649 --> 02:04:42.659 align:start position:0% transmit and the um receive indications 02:04:42.659 --> 02:04:45.410 align:start position:0% transmit and the um receive indications on<02:04:43.020> either<02:04:43.139> end<02:04:43.440> there 02:04:45.410 --> 02:04:45.420 align:start position:0% on either end there 02:04:45.420 --> 02:04:48.109 align:start position:0% on either end there so<02:04:45.780> when<02:04:45.960> a<02:04:46.199> computer<02:04:46.320> uses<02:04:46.860> pins<02:04:47.280> one<02:04:47.580> and<02:04:47.820> two 02:04:48.109 --> 02:04:48.119 align:start position:0% so when a computer uses pins one and two 02:04:48.119 --> 02:04:51.050 align:start position:0% so when a computer uses pins one and two I<02:04:48.719> have<02:04:48.960> a<02:04:49.080> pair<02:04:49.199> of<02:04:49.380> wise<02:04:49.619> to<02:04:49.860> transmit<02:04:50.760> the 02:04:51.050 --> 02:04:51.060 align:start position:0% I have a pair of wise to transmit the 02:04:51.060 --> 02:04:52.790 align:start position:0% I have a pair of wise to transmit the switch<02:04:51.239> will<02:04:51.540> receive<02:04:51.840> those<02:04:52.080> data<02:04:52.500> on<02:04:52.679> the 02:04:52.790 --> 02:04:52.800 align:start position:0% switch will receive those data on the 02:04:52.800 --> 02:04:54.470 align:start position:0% switch will receive those data on the same<02:04:52.920> pins 02:04:54.470 --> 02:04:54.480 align:start position:0% same pins 02:04:54.480 --> 02:04:56.990 align:start position:0% same pins when<02:04:54.960> I<02:04:55.199> sit<02:04:55.320> when<02:04:55.679> a<02:04:55.860> switch<02:04:56.040> transmits<02:04:56.820> the 02:04:56.990 --> 02:04:57.000 align:start position:0% when I sit when a switch transmits the 02:04:57.000 --> 02:04:58.910 align:start position:0% when I sit when a switch transmits the data<02:04:57.300> using<02:04:57.599> pins<02:04:57.840> three<02:04:58.080> and<02:04:58.320> six<02:04:58.500> on<02:04:58.739> a 02:04:58.910 --> 02:04:58.920 align:start position:0% data using pins three and six on a 02:04:58.920 --> 02:05:00.649 align:start position:0% data using pins three and six on a different<02:04:59.040> pair<02:04:59.280> of<02:04:59.520> wires<02:04:59.820> the<02:05:00.480> computer 02:05:00.649 --> 02:05:00.659 align:start position:0% different pair of wires the computer 02:05:00.659 --> 02:05:03.530 align:start position:0% different pair of wires the computer will<02:05:01.080> receive<02:05:01.800> those<02:05:02.099> so<02:05:03.000> you<02:05:03.179> can<02:05:03.300> see<02:05:03.420> here 02:05:03.530 --> 02:05:03.540 align:start position:0% will receive those so you can see here 02:05:03.540 --> 02:05:11.990 align:start position:0% will receive those so you can see here TX<02:05:03.960> is<02:05:04.139> going<02:05:04.320> to<02:05:04.500> an<02:05:04.679> RX<02:05:05.040> and<02:05:05.760> vice<02:05:06.000> versa 02:05:11.990 --> 02:05:12.000 align:start position:0% 02:05:12.000 --> 02:05:14.209 align:start position:0% um in<02:05:12.300> the<02:05:12.480> internet<02:05:12.599> Network<02:05:13.080> such<02:05:13.679> as<02:05:13.860> a<02:05:14.040> 10 02:05:14.209 --> 02:05:14.219 align:start position:0% um in the internet Network such as a 10 02:05:14.219 --> 02:05:17.030 align:start position:0% um in the internet Network such as a 10 base<02:05:14.400> t<02:05:14.639> or<02:05:14.880> 100<02:05:15.000> Base<02:05:15.360> TX<02:05:15.780> pins<02:05:16.560> four<02:05:16.739> and<02:05:16.860> five 02:05:17.030 --> 02:05:17.040 align:start position:0% base t or 100 Base TX pins four and five 02:05:17.040 --> 02:05:19.250 align:start position:0% base t or 100 Base TX pins four and five of<02:05:17.280> the<02:05:17.400> blue<02:05:17.639> pad<02:05:18.000> and<02:05:18.540> pin<02:05:18.780> seven<02:05:18.900> and<02:05:19.139> eight 02:05:19.250 --> 02:05:19.260 align:start position:0% of the blue pad and pin seven and eight 02:05:19.260 --> 02:05:21.709 align:start position:0% of the blue pad and pin seven and eight of<02:05:19.440> the<02:05:19.500> brown<02:05:19.679> pair<02:05:19.920> are<02:05:20.280> not<02:05:20.520> used 02:05:21.709 --> 02:05:21.719 align:start position:0% of the brown pair are not used 02:05:21.719 --> 02:05:23.330 align:start position:0% of the brown pair are not used so<02:05:22.199> technically<02:05:22.500> you<02:05:22.739> could<02:05:22.860> have<02:05:22.980> a<02:05:23.159> cable 02:05:23.330 --> 02:05:23.340 align:start position:0% so technically you could have a cable 02:05:23.340 --> 02:05:25.189 align:start position:0% so technically you could have a cable that<02:05:24.300> um<02:05:24.300> doesn't 02:05:25.189 --> 02:05:25.199 align:start position:0% that um doesn't 02:05:25.199 --> 02:05:28.189 align:start position:0% that um doesn't um<02:05:25.320> have<02:05:25.560> connections<02:05:26.040> on<02:05:26.219> those<02:05:26.400> pins<02:05:26.760> there 02:05:28.189 --> 02:05:28.199 align:start position:0% um have connections on those pins there 02:05:28.199 --> 02:05:30.830 align:start position:0% um have connections on those pins there now<02:05:28.679> you're<02:05:29.400> more<02:05:29.639> likely<02:05:29.940> to<02:05:30.060> be<02:05:30.179> using<02:05:30.540> a 02:05:30.830 --> 02:05:30.840 align:start position:0% now you're more likely to be using a 02:05:30.840 --> 02:05:33.109 align:start position:0% now you're more likely to be using a faster<02:05:31.020> and<02:05:31.619> connection<02:05:31.980> type<02:05:32.400> if<02:05:32.760> possible 02:05:33.109 --> 02:05:33.119 align:start position:0% faster and connection type if possible 02:05:33.119 --> 02:05:35.930 align:start position:0% faster and connection type if possible so<02:05:33.900> on<02:05:34.199> the<02:05:34.320> thousand<02:05:34.619> base<02:05:34.920> T<02:05:35.219> ethernet<02:05:35.639> cable 02:05:35.930 --> 02:05:35.940 align:start position:0% so on the thousand base T ethernet cable 02:05:35.940 --> 02:05:39.470 align:start position:0% so on the thousand base T ethernet cable such<02:05:36.840> as<02:05:37.020> cat5v<02:05:37.800> all<02:05:38.400> four<02:05:38.580> pairs<02:05:39.000> of<02:05:39.060> wires 02:05:39.470 --> 02:05:39.480 align:start position:0% such as cat5v all four pairs of wires 02:05:39.480 --> 02:05:41.089 align:start position:0% such as cat5v all four pairs of wires will<02:05:39.599> be<02:05:39.780> used<02:05:39.960> and<02:05:40.139> that's<02:05:40.260> how<02:05:40.500> they<02:05:40.679> get<02:05:40.860> the 02:05:41.089 --> 02:05:41.099 align:start position:0% will be used and that's how they get the 02:05:41.099 --> 02:05:44.030 align:start position:0% will be used and that's how they get the faster<02:05:41.760> speed<02:05:42.119> but<02:05:43.020> using<02:05:43.380> the<02:05:43.560> same<02:05:43.679> cable 02:05:44.030 --> 02:05:44.040 align:start position:0% faster speed but using the same cable 02:05:44.040 --> 02:05:45.830 align:start position:0% faster speed but using the same cable types 02:05:45.830 --> 02:05:45.840 align:start position:0% types 02:05:45.840 --> 02:05:48.050 align:start position:0% types now<02:05:46.320> the<02:05:46.440> crossover<02:05:46.800> cable<02:05:47.219> you<02:05:47.520> can<02:05:47.639> see<02:05:47.760> here 02:05:48.050 --> 02:05:48.060 align:start position:0% now the crossover cable you can see here 02:05:48.060 --> 02:05:51.169 align:start position:0% now the crossover cable you can see here is<02:05:48.420> used<02:05:48.599> to<02:05:48.840> connect<02:05:49.020> like<02:05:49.920> to<02:05:50.219> like<02:05:50.460> so<02:05:51.000> if 02:05:51.169 --> 02:05:51.179 align:start position:0% is used to connect like to like so if 02:05:51.179 --> 02:05:53.149 align:start position:0% is used to connect like to like so if you<02:05:51.300> have<02:05:51.420> two<02:05:51.659> switches<02:05:52.199> then<02:05:52.860> you<02:05:53.099> could 02:05:53.149 --> 02:05:53.159 align:start position:0% you have two switches then you could 02:05:53.159 --> 02:05:55.550 align:start position:0% you have two switches then you could connect<02:05:53.340> them<02:05:53.580> using<02:05:53.820> a<02:05:53.940> crossover<02:05:54.179> cable<02:05:54.719> two 02:05:55.550 --> 02:05:55.560 align:start position:0% connect them using a crossover cable two 02:05:55.560 --> 02:05:57.589 align:start position:0% connect them using a crossover cable two router<02:05:56.040> ethernet<02:05:56.580> ports<02:05:57.000> you<02:05:57.179> could<02:05:57.239> use<02:05:57.420> a 02:05:57.589 --> 02:05:57.599 align:start position:0% router ethernet ports you could use a 02:05:57.599 --> 02:06:00.350 align:start position:0% router ethernet ports you could use a crossover<02:05:57.900> cable<02:05:58.380> or<02:05:59.040> if<02:05:59.159> you<02:05:59.280> had<02:05:59.400> two<02:05:59.639> PCS<02:06:00.179> at 02:06:00.350 --> 02:06:00.360 align:start position:0% crossover cable or if you had two PCS at 02:06:00.360 --> 02:06:02.570 align:start position:0% crossover cable or if you had two PCS at home<02:06:00.619> and<02:06:01.619> you<02:06:01.679> didn't<02:06:01.860> want<02:06:02.040> to<02:06:02.159> pay<02:06:02.280> for<02:06:02.460> a 02:06:02.570 --> 02:06:02.580 align:start position:0% home and you didn't want to pay for a 02:06:02.580 --> 02:06:04.010 align:start position:0% home and you didn't want to pay for a switch<02:06:02.699> you<02:06:03.179> could<02:06:03.239> also<02:06:03.480> use<02:06:03.599> a<02:06:03.780> crossover 02:06:04.010 --> 02:06:04.020 align:start position:0% switch you could also use a crossover 02:06:04.020 --> 02:06:06.589 align:start position:0% switch you could also use a crossover cable 02:06:06.589 --> 02:06:06.599 align:start position:0% 02:06:06.599 --> 02:06:08.870 align:start position:0% used<02:06:06.960> to<02:06:07.199> connect<02:06:07.320> the<02:06:07.560> following<02:06:07.920> MDI<02:06:08.520> device 02:06:08.870 --> 02:06:08.880 align:start position:0% used to connect the following MDI device 02:06:08.880 --> 02:06:11.450 align:start position:0% used to connect the following MDI device to<02:06:09.239> an<02:06:09.360> MDI<02:06:09.780> device 02:06:11.450 --> 02:06:11.460 align:start position:0% to an MDI device 02:06:11.460 --> 02:06:14.270 align:start position:0% to an MDI device you<02:06:11.880> could<02:06:12.000> also<02:06:12.239> connect<02:06:12.480> to<02:06:13.619> um 02:06:14.270 --> 02:06:14.280 align:start position:0% you could also connect to um 02:06:14.280 --> 02:06:16.250 align:start position:0% you could also connect to um switches<02:06:15.000> together<02:06:15.239> as<02:06:15.480> we<02:06:15.659> have<02:06:15.780> here<02:06:15.960> in<02:06:16.139> the 02:06:16.250 --> 02:06:16.260 align:start position:0% switches together as we have here in the 02:06:16.260 --> 02:06:20.089 align:start position:0% switches together as we have here in the diagram<02:06:16.500> the<02:06:16.800> MDI<02:06:17.219> X<02:06:17.460> device 02:06:20.089 --> 02:06:20.099 align:start position:0% 02:06:20.099 --> 02:06:22.729 align:start position:0% okay<02:06:20.639> wiring<02:06:21.179> for<02:06:21.360> UTP<02:06:21.840> crossover<02:06:22.260> cable 02:06:22.729 --> 02:06:22.739 align:start position:0% okay wiring for UTP crossover cable 02:06:22.739 --> 02:06:24.589 align:start position:0% okay wiring for UTP crossover cable easiest<02:06:23.159> way<02:06:23.340> to<02:06:23.580> remember<02:06:23.699> is<02:06:24.000> one<02:06:24.239> goes<02:06:24.540> to 02:06:24.589 --> 02:06:24.599 align:start position:0% easiest way to remember is one goes to 02:06:24.599 --> 02:06:26.570 align:start position:0% easiest way to remember is one goes to three<02:06:24.780> and<02:06:25.020> two<02:06:25.199> goes<02:06:25.500> to<02:06:25.560> six<02:06:25.800> everything 02:06:26.570 --> 02:06:26.580 align:start position:0% three and two goes to six everything 02:06:26.580 --> 02:06:29.089 align:start position:0% three and two goes to six everything else<02:06:26.940> stays<02:06:27.360> the<02:06:27.480> same<02:06:27.719> you<02:06:28.380> can<02:06:28.560> see<02:06:28.679> that 02:06:29.089 --> 02:06:29.099 align:start position:0% else stays the same you can see that 02:06:29.099 --> 02:06:31.609 align:start position:0% else stays the same you can see that rule<02:06:29.639> applies<02:06:29.940> for<02:06:30.119> both<02:06:30.360> sides<02:06:30.780> so<02:06:31.139> left<02:06:31.440> to 02:06:31.609 --> 02:06:31.619 align:start position:0% rule applies for both sides so left to 02:06:31.619 --> 02:06:34.910 align:start position:0% rule applies for both sides so left to right<02:06:31.800> and<02:06:32.099> right<02:06:32.400> to<02:06:32.580> left 02:06:34.910 --> 02:06:34.920 align:start position:0% 02:06:34.920 --> 02:06:37.550 align:start position:0% a<02:06:35.280> crossover<02:06:35.699> UTP<02:06:36.239> cable<02:06:36.540> has<02:06:36.900> an<02:06:37.139> eight<02:06:37.260> pin 02:06:37.550 --> 02:06:37.560 align:start position:0% a crossover UTP cable has an eight pin 02:06:37.560 --> 02:06:39.770 align:start position:0% a crossover UTP cable has an eight pin modular<02:06:37.860> connectors<02:06:38.400> each<02:06:39.060> end<02:06:39.599> is 02:06:39.770 --> 02:06:39.780 align:start position:0% modular connectors each end is 02:06:39.780 --> 02:06:46.310 align:start position:0% modular connectors each end is terminated<02:06:40.260> in<02:06:40.739> the<02:06:40.920> below<02:06:41.340> manner 02:06:46.310 --> 02:06:46.320 align:start position:0% 02:06:46.320 --> 02:06:47.930 align:start position:0% okay<02:06:46.739> so<02:06:46.980> these<02:06:47.280> devices<02:06:47.520> will<02:06:47.820> be 02:06:47.930 --> 02:06:47.940 align:start position:0% okay so these devices will be 02:06:47.940 --> 02:06:50.089 align:start position:0% okay so these devices will be transmitted<02:06:48.480> on<02:06:48.599> the<02:06:48.840> same<02:06:49.020> pins<02:06:49.320> one<02:06:49.679> and<02:06:49.920> two 02:06:50.089 --> 02:06:50.099 align:start position:0% transmitted on the same pins one and two 02:06:50.099 --> 02:06:52.129 align:start position:0% transmitted on the same pins one and two these<02:06:50.760> devices<02:06:50.940> will<02:06:51.239> also<02:06:51.480> be<02:06:51.599> receiving<02:06:51.900> on 02:06:52.129 --> 02:06:52.139 align:start position:0% these devices will also be receiving on 02:06:52.139 --> 02:06:54.830 align:start position:0% these devices will also be receiving on the<02:06:52.260> same<02:06:52.380> pins<02:06:52.739> three<02:06:53.340> and<02:06:53.639> six<02:06:53.940> might<02:06:54.659> be 02:06:54.830 --> 02:06:54.840 align:start position:0% the same pins three and six might be 02:06:54.840 --> 02:06:56.689 align:start position:0% the same pins three and six might be worth<02:06:55.020> remembering<02:06:55.440> that<02:06:55.739> case<02:06:55.980> that<02:06:56.280> pops<02:06:56.580> up 02:06:56.689 --> 02:06:56.699 align:start position:0% worth remembering that case that pops up 02:06:56.699 --> 02:06:58.850 align:start position:0% worth remembering that case that pops up in<02:06:56.880> the<02:06:57.000> exam<02:06:57.239> which<02:06:57.420> ones<02:06:57.780> are<02:06:58.020> receiving<02:06:58.619> and 02:06:58.850 --> 02:06:58.860 align:start position:0% in the exam which ones are receiving and 02:06:58.860 --> 02:07:01.129 align:start position:0% in the exam which ones are receiving and which<02:06:58.980> ones<02:06:59.280> are<02:06:59.460> transmitting 02:07:01.129 --> 02:07:01.139 align:start position:0% which ones are transmitting 02:07:01.139 --> 02:07:05.109 align:start position:0% which ones are transmitting foreign 02:07:05.109 --> 02:07:05.119 align:start position:0% 02:07:05.119 --> 02:07:07.669 align:start position:0% on<02:07:06.119> one<02:07:06.239> side<02:07:06.420> is<02:07:06.780> connected<02:07:07.139> to<02:07:07.199> pin<02:07:07.500> three 02:07:07.669 --> 02:07:07.679 align:start position:0% on one side is connected to pin three 02:07:07.679 --> 02:07:10.850 align:start position:0% on one side is connected to pin three that's<02:07:07.920> what<02:07:08.159> I<02:07:08.280> said<02:07:08.460> and<02:07:09.000> two<02:07:09.179> to<02:07:09.420> six 02:07:10.850 --> 02:07:10.860 align:start position:0% that's what I said and two to six 02:07:10.860 --> 02:07:13.189 align:start position:0% that's what I said and two to six terminating<02:07:11.520> the<02:07:11.820> crossover 02:07:13.189 --> 02:07:13.199 align:start position:0% terminating the crossover 02:07:13.199 --> 02:07:16.250 align:start position:0% terminating the crossover you<02:07:13.619> would<02:07:13.800> terminate<02:07:14.219> by<02:07:14.580> using<02:07:14.940> the<02:07:15.599> um<02:07:15.599> 568 02:07:16.250 --> 02:07:16.260 align:start position:0% you would terminate by using the um 568 02:07:16.260 --> 02:07:19.310 align:start position:0% you would terminate by using the um 568 a<02:07:16.500> wiring<02:07:16.980> on<02:07:17.219> one<02:07:17.400> side<02:07:17.639> and<02:07:18.420> the<02:07:18.540> B<02:07:18.719> wiring<02:07:19.139> on 02:07:19.310 --> 02:07:19.320 align:start position:0% a wiring on one side and the B wiring on 02:07:19.320 --> 02:07:20.930 align:start position:0% a wiring on one side and the B wiring on the<02:07:19.500> other<02:07:19.619> so<02:07:20.219> using<02:07:20.580> two<02:07:20.760> different 02:07:20.930 --> 02:07:20.940 align:start position:0% the other so using two different 02:07:20.940 --> 02:07:26.810 align:start position:0% the other so using two different standards<02:07:21.599> for<02:07:22.020> either<02:07:22.380> end 02:07:26.810 --> 02:07:26.820 align:start position:0% 02:07:26.820 --> 02:07:28.850 align:start position:0% um if<02:07:27.000> we're<02:07:27.179> on<02:07:27.300> an<02:07:27.420> end<02:07:27.540> of<02:07:27.719> the<02:07:28.260> um<02:07:28.260> cabling 02:07:28.850 --> 02:07:28.860 align:start position:0% um if we're on an end of the um cabling 02:07:28.860 --> 02:07:31.490 align:start position:0% um if we're on an end of the um cabling uses<02:07:29.460> the<02:07:29.699> a<02:07:29.880> standard<02:07:30.360> the<02:07:30.659> other<02:07:30.780> has<02:07:31.139> to<02:07:31.320> use 02:07:31.490 --> 02:07:31.500 align:start position:0% uses the a standard the other has to use 02:07:31.500 --> 02:07:33.229 align:start position:0% uses the a standard the other has to use the<02:07:31.739> B<02:07:31.980> that's<02:07:32.520> if<02:07:32.760> you're<02:07:32.880> making<02:07:33.000> the 02:07:33.229 --> 02:07:33.239 align:start position:0% the B that's if you're making the 02:07:33.239 --> 02:07:35.149 align:start position:0% the B that's if you're making the crossover<02:07:33.599> cable 02:07:35.149 --> 02:07:35.159 align:start position:0% crossover cable 02:07:35.159 --> 02:07:37.970 align:start position:0% crossover cable Auto<02:07:36.000> mdix 02:07:37.970 --> 02:07:37.980 align:start position:0% Auto mdix 02:07:37.980 --> 02:07:40.010 align:start position:0% Auto mdix it's<02:07:38.639> Auto<02:07:38.880> sensing<02:07:39.480> so<02:07:39.659> do<02:07:39.840> you<02:07:39.960> remember 02:07:40.010 --> 02:07:40.020 align:start position:0% it's Auto sensing so do you remember 02:07:40.020 --> 02:07:43.070 align:start position:0% it's Auto sensing so do you remember earlier<02:07:40.500> we<02:07:40.679> had<02:07:40.860> this<02:07:41.219> picture<02:07:41.460> of<02:07:41.820> a<02:07:42.000> hub<02:07:42.239> and 02:07:43.070 --> 02:07:43.080 align:start position:0% earlier we had this picture of a hub and 02:07:43.080 --> 02:07:44.750 align:start position:0% earlier we had this picture of a hub and you<02:07:43.199> had<02:07:43.380> to<02:07:43.560> press<02:07:43.739> this<02:07:44.460> um<02:07:44.460> the<02:07:44.699> little 02:07:44.750 --> 02:07:44.760 align:start position:0% you had to press this um the little 02:07:44.760 --> 02:07:48.169 align:start position:0% you had to press this um the little switch<02:07:45.000> on<02:07:45.300> there<02:07:45.540> while<02:07:46.320> modern<02:07:46.739> devices<02:07:47.639> can 02:07:48.169 --> 02:07:48.179 align:start position:0% switch on there while modern devices can 02:07:48.179 --> 02:07:50.570 align:start position:0% switch on there while modern devices can actually<02:07:48.360> Auto<02:07:48.840> sense<02:07:49.320> what<02:07:49.860> type<02:07:50.040> of<02:07:50.159> cables 02:07:50.570 --> 02:07:50.580 align:start position:0% actually Auto sense what type of cables 02:07:50.580 --> 02:07:53.510 align:start position:0% actually Auto sense what type of cables attached<02:07:51.239> and<02:07:51.780> then<02:07:51.960> change<02:07:52.260> the<02:07:52.679> designation 02:07:53.510 --> 02:07:53.520 align:start position:0% attached and then change the designation 02:07:53.520 --> 02:07:56.930 align:start position:0% attached and then change the designation for<02:07:53.880> how<02:07:54.540> it<02:07:54.659> uses<02:07:54.960> which<02:07:55.260> wires<02:07:55.860> on<02:07:56.280> the<02:07:56.520> eight 02:07:56.930 --> 02:07:56.940 align:start position:0% for how it uses which wires on the eight 02:07:56.940 --> 02:08:00.589 align:start position:0% for how it uses which wires on the eight pins<02:07:57.300> on<02:07:57.540> the<02:07:57.659> inside 02:08:00.589 --> 02:08:00.599 align:start position:0% 02:08:00.599 --> 02:08:03.109 align:start position:0% and<02:08:01.020> most<02:08:01.320> modern<02:08:01.500> ethernet<02:08:02.219> devices<02:08:02.639> for 02:08:03.109 --> 02:08:03.119 align:start position:0% and most modern ethernet devices for 02:08:03.119 --> 02:08:05.930 align:start position:0% and most modern ethernet devices for example<02:08:03.360> switches<02:08:04.020> use<02:08:04.260> the<02:08:04.500> auto<02:08:04.739> MDI<02:08:05.400> XV 02:08:05.930 --> 02:08:05.940 align:start position:0% example switches use the auto MDI XV 02:08:05.940 --> 02:08:08.030 align:start position:0% example switches use the auto MDI XV channel<02:08:06.239> so<02:08:06.480> it's<02:08:06.719> pretty<02:08:06.900> handy 02:08:08.030 --> 02:08:08.040 align:start position:0% channel so it's pretty handy 02:08:08.040 --> 02:08:10.070 align:start position:0% channel so it's pretty handy this<02:08:08.580> is<02:08:08.699> why<02:08:08.880> sometimes<02:08:09.300> you<02:08:09.540> can<02:08:09.659> plug<02:08:09.840> the 02:08:10.070 --> 02:08:10.080 align:start position:0% this is why sometimes you can plug the 02:08:10.080 --> 02:08:12.770 align:start position:0% this is why sometimes you can plug the wrong<02:08:10.199> cable<02:08:10.500> into<02:08:10.739> a<02:08:11.040> switch<02:08:11.420> and<02:08:12.420> it<02:08:12.599> all 02:08:12.770 --> 02:08:12.780 align:start position:0% wrong cable into a switch and it all 02:08:12.780 --> 02:08:14.330 align:start position:0% wrong cable into a switch and it all still<02:08:12.960> works<02:08:13.320> because<02:08:13.619> it's<02:08:13.860> got<02:08:14.099> this 02:08:14.330 --> 02:08:14.340 align:start position:0% still works because it's got this 02:08:14.340 --> 02:08:16.189 align:start position:0% still works because it's got this automatic<02:08:15.179> feature 02:08:16.189 --> 02:08:16.199 align:start position:0% automatic feature 02:08:16.199 --> 02:08:17.870 align:start position:0% automatic feature rollover<02:08:16.800> cable<02:08:17.159> is<02:08:17.340> something<02:08:17.520> you<02:08:17.760> will 02:08:17.870 --> 02:08:17.880 align:start position:0% rollover cable is something you will 02:08:17.880 --> 02:08:19.609 align:start position:0% rollover cable is something you will have<02:08:18.000> with<02:08:18.239> you<02:08:18.420> normally<02:08:18.719> at<02:08:18.900> all<02:08:19.020> times<02:08:19.199> as<02:08:19.440> a 02:08:19.609 --> 02:08:19.619 align:start position:0% have with you normally at all times as a 02:08:19.619 --> 02:08:22.129 align:start position:0% have with you normally at all times as a network<02:08:19.739> engineer<02:08:20.400> in<02:08:20.699> your<02:08:20.880> briefcase 02:08:22.129 --> 02:08:22.139 align:start position:0% network engineer in your briefcase 02:08:22.139 --> 02:08:25.790 align:start position:0% network engineer in your briefcase and<02:08:22.619> normally<02:08:23.040> used<02:08:23.460> to<02:08:24.000> connect<02:08:24.239> your<02:08:24.840> PC<02:08:25.440> or 02:08:25.790 --> 02:08:25.800 align:start position:0% and normally used to connect your PC or 02:08:25.800 --> 02:08:29.870 align:start position:0% and normally used to connect your PC or laptop<02:08:26.239> to<02:08:27.239> the<02:08:27.599> console<02:08:27.960> port<02:08:28.219> on<02:08:29.219> a<02:08:29.460> router 02:08:29.870 --> 02:08:29.880 align:start position:0% laptop to the console port on a router 02:08:29.880 --> 02:08:31.790 align:start position:0% laptop to the console port on a router or<02:08:30.119> switch<02:08:30.300> and<02:08:30.599> it<02:08:30.780> lets<02:08:31.139> you 02:08:31.790 --> 02:08:31.800 align:start position:0% or switch and it lets you 02:08:31.800 --> 02:08:33.770 align:start position:0% or switch and it lets you configure<02:08:32.460> the<02:08:32.580> device<02:08:32.760> when<02:08:33.119> you<02:08:33.239> first<02:08:33.420> buy 02:08:33.770 --> 02:08:33.780 align:start position:0% configure the device when you first buy 02:08:33.780 --> 02:08:36.229 align:start position:0% configure the device when you first buy it<02:08:33.960> and<02:08:34.260> it's<02:08:34.440> blank<02:08:34.860> or<02:08:35.159> do<02:08:35.400> emergency 02:08:36.229 --> 02:08:36.239 align:start position:0% it and it's blank or do emergency 02:08:36.239 --> 02:08:38.629 align:start position:0% it and it's blank or do emergency recovery<02:08:37.080> for<02:08:37.679> example<02:08:37.860> if<02:08:38.099> you've<02:08:38.219> forgotten 02:08:38.629 --> 02:08:38.639 align:start position:0% recovery for example if you've forgotten 02:08:38.639 --> 02:08:40.790 align:start position:0% recovery for example if you've forgotten a<02:08:38.760> password<02:08:38.940> to<02:08:39.719> configure<02:08:40.139> the<02:08:40.320> router<02:08:40.619> or 02:08:40.790 --> 02:08:40.800 align:start position:0% a password to configure the router or 02:08:40.800 --> 02:08:43.490 align:start position:0% a password to configure the router or switch 02:08:43.490 --> 02:08:43.500 align:start position:0% 02:08:43.500 --> 02:08:47.570 align:start position:0% so<02:08:44.159> it<02:08:44.340> has<02:08:44.460> a<02:08:44.699> 8p<02:08:45.179> AC<02:08:45.420> connector<02:08:46.099> rs232<02:08:47.099> based 02:08:47.570 --> 02:08:47.580 align:start position:0% so it has a 8p AC connector rs232 based 02:08:47.580 --> 02:08:49.669 align:start position:0% so it has a 8p AC connector rs232 based connector<02:08:47.940> such<02:08:48.179> as<02:08:48.360> a<02:08:48.540> DB9 02:08:49.669 --> 02:08:49.679 align:start position:0% connector such as a DB9 02:08:49.679 --> 02:08:51.770 align:start position:0% connector such as a DB9 this<02:08:50.280> has<02:08:50.400> actually<02:08:50.639> changed<02:08:51.239> now<02:08:51.360> so<02:08:51.540> you<02:08:51.659> can 02:08:51.770 --> 02:08:51.780 align:start position:0% this has actually changed now so you can 02:08:51.780 --> 02:08:54.530 align:start position:0% this has actually changed now so you can see<02:08:51.840> the<02:08:52.020> DB9<02:08:52.560> connector<02:08:53.159> your<02:08:53.760> laptops<02:08:54.360> don't 02:08:54.530 --> 02:08:54.540 align:start position:0% see the DB9 connector your laptops don't 02:08:54.540 --> 02:08:56.209 align:start position:0% see the DB9 connector your laptops don't actually<02:08:54.780> come<02:08:55.020> with<02:08:55.199> DB9<02:08:55.739> connectors 02:08:56.209 --> 02:08:56.219 align:start position:0% actually come with DB9 connectors 02:08:56.219 --> 02:08:58.189 align:start position:0% actually come with DB9 connectors anymore<02:08:56.460> it's<02:08:56.760> pretty<02:08:56.940> old-fashioned<02:08:57.599> so 02:08:58.189 --> 02:08:58.199 align:start position:0% anymore it's pretty old-fashioned so 02:08:58.199 --> 02:09:00.709 align:start position:0% anymore it's pretty old-fashioned so what<02:08:58.380> you'll<02:08:58.560> do<02:08:58.739> is<02:08:58.800> you'll<02:08:59.040> have<02:08:59.159> a<02:08:59.280> db92<02:09:00.060> USB 02:09:00.709 --> 02:09:00.719 align:start position:0% what you'll do is you'll have a db92 USB 02:09:00.719 --> 02:09:02.930 align:start position:0% what you'll do is you'll have a db92 USB connector 02:09:02.930 --> 02:09:02.940 align:start position:0% connector 02:09:02.940 --> 02:09:06.169 align:start position:0% connector um<02:09:03.000> and<02:09:03.420> you'll<02:09:03.780> use<02:09:03.960> one<02:09:04.199> of<02:09:04.380> your<02:09:04.619> free 02:09:06.169 --> 02:09:06.179 align:start position:0% um and you'll use one of your free 02:09:06.179 --> 02:09:08.149 align:start position:0% um and you'll use one of your free um common<02:09:06.900> connections<02:09:07.619> using<02:09:07.980> device 02:09:08.149 --> 02:09:08.159 align:start position:0% um common connections using device 02:09:08.159 --> 02:09:14.209 align:start position:0% um common connections using device manager<02:09:08.880> to<02:09:09.659> see<02:09:10.020> which<02:09:10.199> port<02:09:10.440> to<02:09:10.739> connect<02:09:10.920> on 02:09:14.209 --> 02:09:14.219 align:start position:0% 02:09:14.219 --> 02:09:16.790 align:start position:0% so<02:09:14.699> I<02:09:14.880> mentioned<02:09:15.119> Cisco<02:09:15.540> console<02:09:15.960> cables<02:09:16.560> and 02:09:16.790 --> 02:09:16.800 align:start position:0% so I mentioned Cisco console cables and 02:09:16.800 --> 02:09:18.830 align:start position:0% so I mentioned Cisco console cables and recovering<02:09:17.219> your<02:09:17.400> Cisco<02:09:17.760> router 02:09:18.830 --> 02:09:18.840 align:start position:0% recovering your Cisco router 02:09:18.840 --> 02:09:21.410 align:start position:0% recovering your Cisco router in<02:09:19.619> order<02:09:19.739> to<02:09:19.920> you<02:09:20.280> can<02:09:20.880> make<02:09:21.060> your<02:09:21.300> own 02:09:21.410 --> 02:09:21.420 align:start position:0% in order to you can make your own 02:09:21.420 --> 02:09:24.229 align:start position:0% in order to you can make your own rollover<02:09:21.960> cable<02:09:22.380> roll<02:09:22.860> over<02:09:23.099> flat<02:09:23.639> console 02:09:24.229 --> 02:09:24.239 align:start position:0% rollover cable roll over flat console 02:09:24.239 --> 02:09:26.030 align:start position:0% rollover cable roll over flat console same<02:09:24.659> thing<02:09:24.900> cable 02:09:26.030 --> 02:09:26.040 align:start position:0% same thing cable 02:09:26.040 --> 02:09:28.550 align:start position:0% same thing cable and<02:09:26.639> the<02:09:26.820> wires<02:09:27.179> are<02:09:27.300> basically<02:09:27.599> reversed<02:09:28.199> so 02:09:28.550 --> 02:09:28.560 align:start position:0% and the wires are basically reversed so 02:09:28.560 --> 02:09:31.550 align:start position:0% and the wires are basically reversed so every<02:09:28.920> yr<02:09:29.400> goes<02:09:29.760> to<02:09:29.820> the<02:09:30.000> opposite<02:09:30.360> number<02:09:30.599> one 02:09:31.550 --> 02:09:31.560 align:start position:0% every yr goes to the opposite number one 02:09:31.560 --> 02:09:33.709 align:start position:0% every yr goes to the opposite number one goes<02:09:31.920> to<02:09:31.980> a<02:09:32.159> two<02:09:32.460> goes<02:09:32.760> to<02:09:32.820> seven<02:09:33.000> three<02:09:33.300> goes 02:09:33.709 --> 02:09:33.719 align:start position:0% goes to a two goes to seven three goes 02:09:33.719 --> 02:09:36.950 align:start position:0% goes to a two goes to seven three goes to<02:09:33.780> six<02:09:34.139> and<02:09:35.400> um<02:09:35.400> carry<02:09:36.000> on<02:09:36.119> with<02:09:36.599> that<02:09:36.780> number 02:09:36.950 --> 02:09:36.960 align:start position:0% to six and um carry on with that number 02:09:36.960 --> 02:09:38.629 align:start position:0% to six and um carry on with that number in<02:09:37.320> so<02:09:37.860> basically<02:09:38.099> the<02:09:38.280> whole<02:09:38.400> thing's 02:09:38.629 --> 02:09:38.639 align:start position:0% in so basically the whole thing's 02:09:38.639 --> 02:09:42.109 align:start position:0% in so basically the whole thing's Twisted<02:09:39.000> somewhere<02:09:39.420> in<02:09:39.599> the<02:09:39.719> middle 02:09:42.109 --> 02:09:42.119 align:start position:0% 02:09:42.119 --> 02:09:43.910 align:start position:0% all<02:09:42.659> right<02:09:42.780> so<02:09:43.080> we've<02:09:43.260> covered<02:09:43.560> modular 02:09:43.910 --> 02:09:43.920 align:start position:0% all right so we've covered modular 02:09:43.920 --> 02:09:46.750 align:start position:0% all right so we've covered modular connectors<02:09:44.520> the<02:09:44.940> A<02:09:45.119> and<02:09:45.300> B<02:09:45.420> wiring<02:09:45.900> schemes 02:09:46.750 --> 02:09:46.760 align:start position:0% connectors the A and B wiring schemes 02:09:46.760 --> 02:09:51.530 align:start position:0% connectors the A and B wiring schemes MDI<02:09:47.760> and<02:09:48.239> mdix<02:09:49.099> straight<02:09:50.099> through 02:09:51.530 --> 02:09:51.540 align:start position:0% MDI and mdix straight through 02:09:51.540 --> 02:09:55.609 align:start position:0% MDI and mdix straight through and<02:09:52.320> crossover<02:09:52.920> cable 02:09:55.609 --> 02:09:55.619 align:start position:0% 02:09:55.619 --> 02:09:58.669 align:start position:0% Auto<02:09:56.159> mdix<02:09:56.820> and<02:09:57.300> brown<02:09:57.599> leather<02:09:57.840> cables<02:09:58.380> so 02:09:58.669 --> 02:09:58.679 align:start position:0% Auto mdix and brown leather cables so 02:09:58.679 --> 02:10:00.470 align:start position:0% Auto mdix and brown leather cables so that's<02:09:58.980> all<02:09:59.280> we<02:09:59.460> need<02:09:59.639> to<02:09:59.760> look<02:09:59.880> at<02:10:00.060> for<02:10:00.300> now 02:10:00.470 --> 02:10:00.480 align:start position:0% that's all we need to look at for now 02:10:00.480 --> 02:10:09.300 align:start position:0% that's all we need to look at for now thanks<02:10:01.260> for<02:10:01.440> watching 02:10:09.300 --> 02:10:09.310 align:start position:0% 02:10:09.310 --> 02:10:26.270 align:start position:0% [Music] 02:10:26.270 --> 02:10:26.280 align:start position:0% 02:10:26.280 --> 02:10:29.930 align:start position:0% welcome<02:10:26.820> to<02:10:27.060> module<02:10:27.540> 2<02:10:27.719> lesson<02:10:28.199> 1B<02:10:28.639> some<02:10:29.639> more 02:10:29.930 --> 02:10:29.940 align:start position:0% welcome to module 2 lesson 1B some more 02:10:29.940 --> 02:10:32.149 align:start position:0% welcome to module 2 lesson 1B some more cables<02:10:30.480> connectors<02:10:30.960> and<02:10:31.199> transceivers<02:10:31.920> this 02:10:32.149 --> 02:10:32.159 align:start position:0% cables connectors and transceivers this 02:10:32.159 --> 02:10:34.250 align:start position:0% cables connectors and transceivers this is<02:10:32.280> all<02:10:32.580> new<02:10:32.760> stuff<02:10:33.060> that's<02:10:33.239> landed<02:10:33.719> into<02:10:33.960> the 02:10:34.250 --> 02:10:34.260 align:start position:0% is all new stuff that's landed into the 02:10:34.260 --> 02:10:36.109 align:start position:0% is all new stuff that's landed into the network<02:10:34.560> plus<02:10:34.860> syllabus 02:10:36.109 --> 02:10:36.119 align:start position:0% network plus syllabus 02:10:36.119 --> 02:10:38.209 align:start position:0% network plus syllabus uh<02:10:36.719> some<02:10:36.840> of<02:10:37.020> it's<02:10:37.139> a<02:10:37.320> little<02:10:37.440> bit<02:10:37.619> strange<02:10:37.980> in 02:10:38.209 --> 02:10:38.219 align:start position:0% uh some of it's a little bit strange in 02:10:38.219 --> 02:10:41.149 align:start position:0% uh some of it's a little bit strange in as<02:10:38.460> much<02:10:38.580> as<02:10:38.760> it's<02:10:39.060> almost<02:10:39.480> redundant<02:10:40.199> and<02:10:40.980> I'm 02:10:41.149 --> 02:10:41.159 align:start position:0% as much as it's almost redundant and I'm 02:10:41.159 --> 02:10:42.530 align:start position:0% as much as it's almost redundant and I'm guessing<02:10:41.400> they<02:10:41.580> want<02:10:41.760> you<02:10:41.940> to<02:10:42.119> know<02:10:42.239> this 02:10:42.530 --> 02:10:42.540 align:start position:0% guessing they want you to know this 02:10:42.540 --> 02:10:45.229 align:start position:0% guessing they want you to know this stuff<02:10:42.780> in<02:10:43.139> case<02:10:43.320> you<02:10:43.500> come<02:10:43.679> across<02:10:44.040> it<02:10:44.219> in<02:10:45.060> an 02:10:45.229 --> 02:10:45.239 align:start position:0% stuff in case you come across it in an 02:10:45.239 --> 02:10:47.390 align:start position:0% stuff in case you come across it in an environment<02:10:45.599> for<02:10:45.780> whatever<02:10:45.960> reason 02:10:47.390 --> 02:10:47.400 align:start position:0% environment for whatever reason 02:10:47.400 --> 02:10:50.149 align:start position:0% environment for whatever reason all<02:10:47.760> right<02:10:47.880> so<02:10:48.060> Network<02:10:48.360> Hardware<02:10:48.780> media<02:10:49.619> and 02:10:50.149 --> 02:10:50.159 align:start position:0% all right so Network Hardware media and 02:10:50.159 --> 02:10:52.250 align:start position:0% all right so Network Hardware media and bound<02:10:50.460> in<02:10:50.639> network<02:10:50.880> media<02:10:51.480> a<02:10:51.900> few<02:10:52.080> things 02:10:52.250 --> 02:10:52.260 align:start position:0% bound in network media a few things 02:10:52.260 --> 02:10:54.050 align:start position:0% bound in network media a few things we'll<02:10:52.500> be<02:10:52.679> looking<02:10:52.800> at 02:10:54.050 --> 02:10:54.060 align:start position:0% we'll be looking at 02:10:54.060 --> 02:10:56.870 align:start position:0% we'll be looking at copper<02:10:54.840> connectors<02:10:55.380> uh<02:10:56.219> the<02:10:56.520> stuff<02:10:56.699> we 02:10:56.870 --> 02:10:56.880 align:start position:0% copper connectors uh the stuff we 02:10:56.880 --> 02:10:58.970 align:start position:0% copper connectors uh the stuff we haven't<02:10:57.060> already<02:10:57.360> looked<02:10:58.199> at<02:10:58.260> earlier<02:10:58.619> by<02:10:58.800> the 02:10:58.970 --> 02:10:58.980 align:start position:0% haven't already looked at earlier by the 02:10:58.980 --> 02:11:01.790 align:start position:0% haven't already looked at earlier by the way<02:10:59.040> uh<02:10:59.940> transceivers 02:11:01.790 --> 02:11:01.800 align:start position:0% way uh transceivers 02:11:01.800 --> 02:11:04.310 align:start position:0% way uh transceivers some<02:11:02.400> termination<02:11:03.000> points<02:11:03.599> copper<02:11:04.139> cable 02:11:04.310 --> 02:11:04.320 align:start position:0% some termination points copper cable 02:11:04.320 --> 02:11:05.570 align:start position:0% some termination points copper cable standards 02:11:05.570 --> 02:11:05.580 align:start position:0% standards 02:11:05.580 --> 02:11:09.350 align:start position:0% standards and<02:11:06.119> network<02:11:06.420> storage<02:11:06.840> connection<02:11:07.260> types 02:11:09.350 --> 02:11:09.360 align:start position:0% and network storage connection types 02:11:09.360 --> 02:11:12.229 align:start position:0% and network storage connection types so<02:11:10.080> this<02:11:10.380> is<02:11:10.500> a<02:11:10.739> used<02:11:10.980> to<02:11:11.159> be<02:11:11.219> called<02:11:11.520> uh<02:11:11.760> d<02:11:12.000> sub 02:11:12.229 --> 02:11:12.239 align:start position:0% so this is a used to be called uh d sub 02:11:12.239 --> 02:11:13.669 align:start position:0% so this is a used to be called uh d sub actually<02:11:12.540> but<02:11:12.900> it<02:11:13.020> seems<02:11:13.380> to<02:11:13.440> have<02:11:13.500> been 02:11:13.669 --> 02:11:13.679 align:start position:0% actually but it seems to have been 02:11:13.679 --> 02:11:16.609 align:start position:0% actually but it seems to have been hijacked<02:11:14.219> into<02:11:14.340> DB<02:11:14.820> connectors<02:11:15.420> but<02:11:16.320> you<02:11:16.500> can 02:11:16.609 --> 02:11:16.619 align:start position:0% hijacked into DB connectors but you can 02:11:16.619 --> 02:11:18.830 align:start position:0% hijacked into DB connectors but you can see<02:11:16.800> the<02:11:17.460> um<02:11:17.460> the<02:11:17.940> shape<02:11:18.119> of<02:11:18.300> the<02:11:18.420> connector 02:11:18.830 --> 02:11:18.840 align:start position:0% see the um the shape of the connector 02:11:18.840 --> 02:11:21.290 align:start position:0% see the um the shape of the connector here<02:11:19.080> is<02:11:19.860> like<02:11:20.099> the<02:11:20.280> letter<02:11:20.460> D<02:11:20.760> really<02:11:21.060> leave 02:11:21.290 --> 02:11:21.300 align:start position:0% here is like the letter D really leave 02:11:21.300 --> 02:11:23.570 align:start position:0% here is like the letter D really leave it<02:11:21.480> on<02:11:21.599> its<02:11:21.960> side 02:11:23.570 --> 02:11:23.580 align:start position:0% it on its side 02:11:23.580 --> 02:11:27.530 align:start position:0% it on its side I<02:11:24.060> like<02:11:24.540> that<02:11:24.840> so<02:11:25.080> the<02:11:25.320> theory<02:11:25.739> is<02:11:25.920> you<02:11:26.340> can't 02:11:27.530 --> 02:11:27.540 align:start position:0% I like that so the theory is you can't 02:11:27.540 --> 02:11:30.589 align:start position:0% I like that so the theory is you can't uh<02:11:28.020> plug<02:11:28.199> it<02:11:28.380> in<02:11:28.560> the<02:11:29.219> wrong<02:11:29.340> way<02:11:29.580> I<02:11:30.239> say<02:11:30.420> in 02:11:30.589 --> 02:11:30.599 align:start position:0% uh plug it in the wrong way I say in 02:11:30.599 --> 02:11:31.970 align:start position:0% uh plug it in the wrong way I say in theory<02:11:30.900> because<02:11:31.080> when<02:11:31.320> I've<02:11:31.500> run<02:11:31.679> computer 02:11:31.970 --> 02:11:31.980 align:start position:0% theory because when I've run computer 02:11:31.980 --> 02:11:34.430 align:start position:0% theory because when I've run computer courses<02:11:32.639> it<02:11:33.179> might<02:11:33.360> just<02:11:33.480> be<02:11:33.659> a<02:11:33.780> Cisco<02:11:34.199> thing 02:11:34.430 --> 02:11:34.440 align:start position:0% courses it might just be a Cisco thing 02:11:34.440 --> 02:11:37.370 align:start position:0% courses it might just be a Cisco thing because<02:11:34.800> this<02:11:35.400> looks<02:11:36.300> a<02:11:36.480> little<02:11:36.599> bit<02:11:36.780> thicker 02:11:37.370 --> 02:11:37.380 align:start position:0% because this looks a little bit thicker 02:11:37.380 --> 02:11:40.609 align:start position:0% because this looks a little bit thicker but<02:11:37.920> the<02:11:38.159> uh<02:11:38.340> the<02:11:38.699> Cisco<02:11:39.480> um 02:11:40.609 --> 02:11:40.619 align:start position:0% but the uh the Cisco um 02:11:40.619 --> 02:11:43.129 align:start position:0% but the uh the Cisco um housing<02:11:41.580> here<02:11:41.820> I<02:11:42.000> was<02:11:42.179> so<02:11:42.360> thin<02:11:42.659> that<02:11:42.840> the 02:11:43.129 --> 02:11:43.139 align:start position:0% housing here I was so thin that the 02:11:43.139 --> 02:11:45.050 align:start position:0% housing here I was so thin that the students<02:11:43.500> would<02:11:43.800> come<02:11:44.040> and<02:11:44.340> somehow<02:11:44.699> managed 02:11:45.050 --> 02:11:45.060 align:start position:0% students would come and somehow managed 02:11:45.060 --> 02:11:47.810 align:start position:0% students would come and somehow managed to<02:11:45.179> plug<02:11:45.360> in<02:11:45.599> the<02:11:46.320> d-connector 02:11:47.810 --> 02:11:47.820 align:start position:0% to plug in the d-connector 02:11:47.820 --> 02:11:51.470 align:start position:0% to plug in the d-connector for<02:11:48.659> the<02:11:48.900> serial<02:11:49.260> cables<02:11:49.800> upside<02:11:50.400> down<02:11:50.639> now 02:11:51.470 --> 02:11:51.480 align:start position:0% for the serial cables upside down now 02:11:51.480 --> 02:11:54.050 align:start position:0% for the serial cables upside down now this<02:11:51.659> did<02:11:51.840> a<02:11:52.020> couple<02:11:52.139> of<02:11:52.260> things<02:11:52.560> it<02:11:53.580> um<02:11:53.580> a 02:11:54.050 --> 02:11:54.060 align:start position:0% this did a couple of things it um a 02:11:54.060 --> 02:11:55.550 align:start position:0% this did a couple of things it um a things<02:11:54.420> don't<02:11:54.659> work<02:11:54.900> when<02:11:55.139> they're<02:11:55.260> upside 02:11:55.550 --> 02:11:55.560 align:start position:0% things don't work when they're upside 02:11:55.560 --> 02:11:57.649 align:start position:0% things don't work when they're upside down<02:11:55.739> obviously<02:11:56.219> with<02:11:56.880> these<02:11:57.179> tiny<02:11:57.480> little 02:11:57.649 --> 02:11:57.659 align:start position:0% down obviously with these tiny little 02:11:57.659 --> 02:12:00.229 align:start position:0% down obviously with these tiny little pins<02:11:58.139> they're<02:11:59.099> much<02:11:59.520> smaller<02:11:59.820> than<02:11:59.880> the<02:12:00.060> ones 02:12:00.229 --> 02:12:00.239 align:start position:0% pins they're much smaller than the ones 02:12:00.239 --> 02:12:03.649 align:start position:0% pins they're much smaller than the ones you<02:12:00.360> see<02:12:00.540> here<02:12:01.040> they<02:12:02.040> actually<02:12:02.340> got<02:12:03.000> forced<02:12:03.599> in 02:12:03.649 --> 02:12:03.659 align:start position:0% you see here they actually got forced in 02:12:03.659 --> 02:12:05.510 align:start position:0% you see here they actually got forced in the<02:12:03.840> wrong<02:12:03.960> way<02:12:04.080> and<02:12:04.260> all<02:12:04.440> got<02:12:04.619> bent<02:12:05.040> like<02:12:05.340> that 02:12:05.510 --> 02:12:05.520 align:start position:0% the wrong way and all got bent like that 02:12:05.520 --> 02:12:07.010 align:start position:0% the wrong way and all got bent like that so<02:12:05.699> that<02:12:05.880> actually<02:12:06.060> cost<02:12:06.420> me<02:12:06.599> a<02:12:06.719> lot<02:12:06.840> of<02:12:06.900> money 02:12:07.010 --> 02:12:07.020 align:start position:0% so that actually cost me a lot of money 02:12:07.020 --> 02:12:09.290 align:start position:0% so that actually cost me a lot of money it<02:12:07.260> was<02:12:07.440> quite<02:12:07.619> a<02:12:07.920> distressing<02:12:08.760> when<02:12:09.060> I 02:12:09.290 --> 02:12:09.300 align:start position:0% it was quite a distressing when I 02:12:09.300 --> 02:12:11.089 align:start position:0% it was quite a distressing when I started<02:12:09.719> up<02:12:09.840> my<02:12:10.020> business 02:12:11.089 --> 02:12:11.099 align:start position:0% started up my business 02:12:11.099 --> 02:12:13.729 align:start position:0% started up my business so<02:12:12.000> this<02:12:12.540> is<02:12:12.599> the<02:12:12.780> theory<02:12:13.020> behind<02:12:13.380> the<02:12:13.500> shape 02:12:13.729 --> 02:12:13.739 align:start position:0% so this is the theory behind the shape 02:12:13.739 --> 02:12:16.310 align:start position:0% so this is the theory behind the shape anyway<02:12:13.980> I<02:12:14.940> actually<02:12:15.239> I<02:12:15.480> don't<02:12:15.540> know<02:12:15.659> why<02:12:15.900> I<02:12:16.139> put 02:12:16.310 --> 02:12:16.320 align:start position:0% anyway I actually I don't know why I put 02:12:16.320 --> 02:12:19.970 align:start position:0% anyway I actually I don't know why I put into<02:12:16.619> male<02:12:17.280> and<02:12:18.179> connectors<02:12:18.780> here<02:12:19.080> I<02:12:19.380> want<02:12:19.800> to 02:12:19.970 --> 02:12:19.980 align:start position:0% into male and connectors here I want to 02:12:19.980 --> 02:12:22.010 align:start position:0% into male and connectors here I want to do<02:12:20.099> have<02:12:20.400> one<02:12:20.639> female<02:12:20.880> but<02:12:21.179> I<02:12:21.360> put<02:12:21.480> into<02:12:21.599> male 02:12:22.010 --> 02:12:22.020 align:start position:0% do have one female but I put into male 02:12:22.020 --> 02:12:24.649 align:start position:0% do have one female but I put into male used<02:12:22.560> to<02:12:22.739> see<02:12:22.860> these<02:12:23.219> on<02:12:23.460> the<02:12:23.580> back<02:12:23.699> of<02:12:24.000> an<02:12:24.300> old 02:12:24.649 --> 02:12:24.659 align:start position:0% used to see these on the back of an old 02:12:24.659 --> 02:12:28.850 align:start position:0% used to see these on the back of an old style<02:12:24.900> PCS<02:12:25.800> and<02:12:27.239> um<02:12:27.239> their<02:12:28.080> laptops<02:12:28.619> as<02:12:28.739> well 02:12:28.850 --> 02:12:28.860 align:start position:0% style PCS and um their laptops as well 02:12:28.860 --> 02:12:29.870 align:start position:0% style PCS and um their laptops as well you<02:12:29.040> don't<02:12:29.219> really<02:12:29.340> see<02:12:29.520> them<02:12:29.699> anymore 02:12:29.870 --> 02:12:29.880 align:start position:0% you don't really see them anymore 02:12:29.880 --> 02:12:32.810 align:start position:0% you don't really see them anymore because<02:12:30.300> USBS<02:12:31.139> have<02:12:31.920> replaced<02:12:32.340> all<02:12:32.460> of<02:12:32.580> it<02:12:32.699> so 02:12:32.810 --> 02:12:32.820 align:start position:0% because USBS have replaced all of it so 02:12:32.820 --> 02:12:34.910 align:start position:0% because USBS have replaced all of it so you'd<02:12:33.000> have<02:12:33.119> to<02:12:33.239> be<02:12:33.420> looking<02:12:33.659> at<02:12:33.840> a<02:12:34.080> fairly<02:12:34.380> old 02:12:34.910 --> 02:12:34.920 align:start position:0% you'd have to be looking at a fairly old 02:12:34.920 --> 02:12:36.410 align:start position:0% you'd have to be looking at a fairly old machine 02:12:36.410 --> 02:12:36.420 align:start position:0% machine 02:12:36.420 --> 02:12:38.689 align:start position:0% machine they<02:12:36.900> were<02:12:37.020> created<02:12:37.320> a<02:12:37.619> long<02:12:37.800> long<02:12:37.980> time<02:12:38.400> ago 02:12:38.689 --> 02:12:38.699 align:start position:0% they were created a long long time ago 02:12:38.699 --> 02:12:42.109 align:start position:0% they were created a long long time ago before<02:12:39.320> I<02:12:40.320> was<02:12:40.440> born<02:12:40.619> when<02:12:41.520> my<02:12:41.699> dad<02:12:41.820> was<02:12:42.000> a 02:12:42.109 --> 02:12:42.119 align:start position:0% before I was born when my dad was a 02:12:42.119 --> 02:12:44.890 align:start position:0% before I was born when my dad was a young<02:12:42.239> man<02:12:42.420> as<02:12:42.599> he<02:12:42.780> used<02:12:42.900> to<02:12:43.020> say<02:12:43.520> 1952 02:12:44.890 --> 02:12:44.900 align:start position:0% young man as he used to say 1952 02:12:44.900 --> 02:12:47.330 align:start position:0% young man as he used to say 1952 exclusively<02:12:45.900> by<02:12:46.139> Canon<02:12:46.619> and<02:12:46.860> it<02:12:46.980> looks<02:12:47.280> like 02:12:47.330 --> 02:12:47.340 align:start position:0% exclusively by Canon and it looks like 02:12:47.340 --> 02:12:49.069 align:start position:0% exclusively by Canon and it looks like they've<02:12:47.699> probably<02:12:47.880> released<02:12:48.480> a<02:12:48.599> license<02:12:48.780> so 02:12:49.069 --> 02:12:49.079 align:start position:0% they've probably released a license so 02:12:49.079 --> 02:12:51.229 align:start position:0% they've probably released a license so that<02:12:49.320> people<02:12:49.500> could<02:12:49.739> use<02:12:49.920> them<02:12:50.579> they<02:12:51.060> were 02:12:51.229 --> 02:12:51.239 align:start position:0% that people could use them they were 02:12:51.239 --> 02:12:53.149 align:start position:0% that people could use them they were used<02:12:51.360> in<02:12:51.480> toker<02:12:51.960> ring<02:12:52.199> networks<02:12:52.739> I<02:12:52.980> do 02:12:53.149 --> 02:12:53.159 align:start position:0% used in toker ring networks I do 02:12:53.159 --> 02:12:55.069 align:start position:0% used in toker ring networks I do remember<02:12:53.400> those<02:12:54.000> support<02:12:54.540> I<02:12:54.960> actually 02:12:55.069 --> 02:12:55.079 align:start position:0% remember those support I actually 02:12:55.079 --> 02:12:57.169 align:start position:0% remember those support I actually supported<02:12:55.619> those<02:12:55.860> for<02:12:56.400> a<02:12:56.520> while<02:12:56.579> at<02:12:56.820> Cisco 02:12:57.169 --> 02:12:57.179 align:start position:0% supported those for a while at Cisco 02:12:57.179 --> 02:12:58.970 align:start position:0% supported those for a while at Cisco although<02:12:57.420> there<02:12:57.540> was<02:12:57.659> hardly<02:12:57.900> any<02:12:58.079> left 02:12:58.970 --> 02:12:58.980 align:start position:0% although there was hardly any left 02:12:58.980 --> 02:13:00.890 align:start position:0% although there was hardly any left it<02:12:59.400> was<02:12:59.520> pretty<02:12:59.699> scary<02:13:00.119> when<02:13:00.420> somebody<02:13:00.599> called 02:13:00.890 --> 02:13:00.900 align:start position:0% it was pretty scary when somebody called 02:13:00.900 --> 02:13:03.830 align:start position:0% it was pretty scary when somebody called in<02:13:01.079> with<02:13:01.260> a<02:13:01.380> token<02:13:01.739> ring<02:13:02.040> issue<02:13:02.880> external 02:13:03.830 --> 02:13:03.840 align:start position:0% in with a token ring issue external 02:13:03.840 --> 02:13:06.169 align:start position:0% in with a token ring issue external floppy<02:13:04.320> drives<02:13:04.619> if<02:13:04.860> you<02:13:04.980> remember<02:13:05.159> those<02:13:05.579> and 02:13:06.169 --> 02:13:06.179 align:start position:0% floppy drives if you remember those and 02:13:06.179 --> 02:13:07.669 align:start position:0% floppy drives if you remember those and you'd<02:13:06.480> buy<02:13:06.599> an<02:13:06.780> old<02:13:06.960> real<02:13:07.139> old<02:13:07.380> probably 02:13:07.669 --> 02:13:07.679 align:start position:0% you'd buy an old real old probably 02:13:07.679 --> 02:13:10.550 align:start position:0% you'd buy an old real old probably wasn't<02:13:07.920> even<02:13:08.099> a<02:13:08.340> PC<02:13:08.579> then<02:13:08.880> it<02:13:09.119> was<02:13:09.300> a<02:13:09.599> an<02:13:10.020> Amiga 02:13:10.550 --> 02:13:10.560 align:start position:0% wasn't even a PC then it was a an Amiga 02:13:10.560 --> 02:13:12.950 align:start position:0% wasn't even a PC then it was a an Amiga or<02:13:10.739> Commodore<02:13:11.280> 64<02:13:11.639> or<02:13:11.880> something<02:13:12.060> and<02:13:12.840> you 02:13:12.950 --> 02:13:12.960 align:start position:0% or Commodore 64 or something and you 02:13:12.960 --> 02:13:15.169 align:start position:0% or Commodore 64 or something and you could<02:13:13.079> invest<02:13:13.560> extra<02:13:13.920> money<02:13:14.579> to<02:13:14.820> put<02:13:15.000> these 02:13:15.169 --> 02:13:15.179 align:start position:0% could invest extra money to put these 02:13:15.179 --> 02:13:17.270 align:start position:0% could invest extra money to put these floppy<02:13:15.480> drives<02:13:15.840> in<02:13:16.020> and<02:13:16.679> if<02:13:16.860> you<02:13:16.980> wanted<02:13:17.099> to 02:13:17.270 --> 02:13:17.280 align:start position:0% floppy drives in and if you wanted to 02:13:17.280 --> 02:13:18.589 align:start position:0% floppy drives in and if you wanted to load<02:13:17.460> a<02:13:17.639> game<02:13:17.760> you<02:13:18.000> probably<02:13:18.179> have<02:13:18.420> to 02:13:18.589 --> 02:13:18.599 align:start position:0% load a game you probably have to 02:13:18.599 --> 02:13:21.470 align:start position:0% load a game you probably have to individually<02:13:19.139> insert<02:13:20.000> uh<02:13:21.000> I<02:13:21.179> think<02:13:21.300> it<02:13:21.360> was 02:13:21.470 --> 02:13:21.480 align:start position:0% individually insert uh I think it was 02:13:21.480 --> 02:13:23.990 align:start position:0% individually insert uh I think it was around<02:13:21.659> 10<02:13:22.020> floppy<02:13:22.860> drives<02:13:23.159> to<02:13:23.400> upload<02:13:23.760> each 02:13:23.990 --> 02:13:24.000 align:start position:0% around 10 floppy drives to upload each 02:13:24.000 --> 02:13:26.089 align:start position:0% around 10 floppy drives to upload each part<02:13:24.179> of<02:13:24.360> the<02:13:24.480> program<02:13:24.719> and<02:13:25.619> I<02:13:25.739> think<02:13:25.860> I<02:13:25.980> did 02:13:26.089 --> 02:13:26.099 align:start position:0% part of the program and I think I did 02:13:26.099 --> 02:13:27.709 align:start position:0% part of the program and I think I did have<02:13:26.280> to<02:13:26.400> do<02:13:26.520> that<02:13:26.639> for<02:13:26.820> early<02:13:26.940> versions<02:13:27.420> of 02:13:27.709 --> 02:13:27.719 align:start position:0% have to do that for early versions of 02:13:27.719 --> 02:13:30.890 align:start position:0% have to do that for early versions of Microsoft<02:13:28.500> Word<02:13:28.679> or<02:13:29.400> the<02:13:29.520> equivalent<02:13:30.000> I<02:13:30.719> used 02:13:30.890 --> 02:13:30.900 align:start position:0% Microsoft Word or the equivalent I used 02:13:30.900 --> 02:13:32.930 align:start position:0% Microsoft Word or the equivalent I used in<02:13:31.079> Mouse<02:13:31.260> connectors<02:13:31.800> also 02:13:32.930 --> 02:13:32.940 align:start position:0% in Mouse connectors also 02:13:32.940 --> 02:13:35.569 align:start position:0% in Mouse connectors also as<02:13:33.480> I<02:13:33.659> said<02:13:33.780> eventually<02:13:34.260> replaced<02:13:34.920> by<02:13:35.040> USB 02:13:35.569 --> 02:13:35.579 align:start position:0% as I said eventually replaced by USB 02:13:35.579 --> 02:13:37.370 align:start position:0% as I said eventually replaced by USB thank<02:13:36.060> goodness 02:13:37.370 --> 02:13:37.380 align:start position:0% thank goodness 02:13:37.380 --> 02:13:40.310 align:start position:0% thank goodness the<02:13:38.159> D<02:13:38.280> shape<02:13:38.699> so<02:13:39.420> I've<02:13:39.659> covered<02:13:39.960> this<02:13:40.079> already 02:13:40.310 --> 02:13:40.320 align:start position:0% the D shape so I've covered this already 02:13:40.320 --> 02:13:43.250 align:start position:0% the D shape so I've covered this already the<02:13:40.739> theory<02:13:41.099> is<02:13:41.280> in<02:13:42.179> fact<02:13:42.360> I'm<02:13:42.540> sure<02:13:42.719> it<02:13:42.900> works 02:13:43.250 --> 02:13:43.260 align:start position:0% the theory is in fact I'm sure it works 02:13:43.260 --> 02:13:44.569 align:start position:0% the theory is in fact I'm sure it works for<02:13:43.380> most<02:13:43.560> people<02:13:43.739> I'll<02:13:44.040> just<02:13:44.219> give<02:13:44.340> you<02:13:44.400> a 02:13:44.569 --> 02:13:44.579 align:start position:0% for most people I'll just give you a 02:13:44.579 --> 02:13:46.970 align:start position:0% for most people I'll just give you a heads<02:13:44.820> up<02:13:44.880> there<02:13:45.119> when<02:13:45.599> I<02:13:45.719> run<02:13:45.900> Cisco<02:13:46.380> it 02:13:46.970 --> 02:13:46.980 align:start position:0% heads up there when I run Cisco it 02:13:46.980 --> 02:13:48.950 align:start position:0% heads up there when I run Cisco it didn't<02:13:47.099> work<02:13:47.340> that<02:13:47.579> way 02:13:48.950 --> 02:13:48.960 align:start position:0% didn't work that way 02:13:48.960 --> 02:13:50.750 align:start position:0% didn't work that way um<02:13:49.079> I<02:13:49.619> wanted<02:13:49.739> the<02:13:49.980> students<02:13:50.219> to<02:13:50.400> plug<02:13:50.520> their 02:13:50.750 --> 02:13:50.760 align:start position:0% um I wanted the students to plug their 02:13:50.760 --> 02:13:53.030 align:start position:0% um I wanted the students to plug their own<02:13:50.880> cables<02:13:51.360> in<02:13:51.540> to<02:13:52.260> have<02:13:52.440> their<02:13:52.679> confidence 02:13:53.030 --> 02:13:53.040 align:start position:0% own cables in to have their confidence 02:13:53.040 --> 02:13:55.189 align:start position:0% own cables in to have their confidence but<02:13:53.460> it<02:13:53.639> kind<02:13:53.820> of<02:13:53.880> backfired<02:13:54.360> a<02:13:54.480> bit 02:13:55.189 --> 02:13:55.199 align:start position:0% but it kind of backfired a bit 02:13:55.199 --> 02:13:58.850 align:start position:0% but it kind of backfired a bit I<02:13:55.560> designed<02:13:55.980> to<02:13:56.040> work<02:13:56.219> with<02:13:56.400> the<02:13:56.639> eia<02:13:57.860> tia232 02:13:58.850 --> 02:13:58.860 align:start position:0% I designed to work with the eia tia232 02:13:58.860 --> 02:14:01.189 align:start position:0% I designed to work with the eia tia232 serial<02:13:59.280> interface<02:13:59.699> standard<02:14:00.179> I<02:14:00.900> guess<02:14:01.020> you 02:14:01.189 --> 02:14:01.199 align:start position:0% serial interface standard I guess you 02:14:01.199 --> 02:14:03.890 align:start position:0% serial interface standard I guess you should<02:14:01.380> make<02:14:01.500> it<02:14:01.679> out<02:14:01.800> of<02:14:01.980> that<02:14:02.099> for<02:14:02.280> the<02:14:02.520> exam 02:14:03.890 --> 02:14:03.900 align:start position:0% should make it out of that for the exam 02:14:03.900 --> 02:14:05.810 align:start position:0% should make it out of that for the exam sort<02:14:04.500> of<02:14:04.619> silly<02:14:04.920> question<02:14:05.040> would<02:14:05.400> be<02:14:05.579> asked 02:14:05.810 --> 02:14:05.820 align:start position:0% sort of silly question would be asked 02:14:05.820 --> 02:14:08.629 align:start position:0% sort of silly question would be asked the<02:14:06.480> number<02:14:06.719> DB<02:14:07.380> whatever 02:14:08.629 --> 02:14:08.639 align:start position:0% the number DB whatever 02:14:08.639 --> 02:14:12.350 align:start position:0% the number DB whatever so<02:14:09.239> uh<02:14:09.480> what<02:14:09.659> would<02:14:09.900> DB9<02:14:10.500> or<02:14:10.860> db25<02:14:11.639> this<02:14:12.239> is 02:14:12.350 --> 02:14:12.360 align:start position:0% so uh what would DB9 or db25 this is 02:14:12.360 --> 02:14:14.450 align:start position:0% so uh what would DB9 or db25 this is supposed<02:14:12.480> to<02:14:12.719> refer<02:14:13.139> to<02:14:13.380> the<02:14:13.679> amount<02:14:13.980> of<02:14:14.099> pins 02:14:14.450 --> 02:14:14.460 align:start position:0% supposed to refer to the amount of pins 02:14:14.460 --> 02:14:18.709 align:start position:0% supposed to refer to the amount of pins that<02:14:15.360> are<02:14:15.480> in<02:14:15.659> the<02:14:15.780> male<02:14:16.199> and<02:14:16.500> female<02:14:16.800> part<02:14:17.219> so 02:14:18.709 --> 02:14:18.719 align:start position:0% that are in the male and female part so 02:14:18.719 --> 02:14:20.209 align:start position:0% that are in the male and female part so it could<02:14:19.020> be<02:14:19.199> pretty<02:14:19.320> hard<02:14:19.500> to<02:14:19.679> mix<02:14:19.800> them<02:14:19.980> up 02:14:20.209 --> 02:14:20.219 align:start position:0% it could be pretty hard to mix them up 02:14:20.219 --> 02:14:22.490 align:start position:0% it could be pretty hard to mix them up actually<02:14:20.460> looking<02:14:21.119> at<02:14:21.420> them<02:14:21.599> you<02:14:22.079> more<02:14:22.320> like 02:14:22.490 --> 02:14:22.500 align:start position:0% actually looking at them you more like 02:14:22.500 --> 02:14:25.910 align:start position:0% actually looking at them you more like to<02:14:22.679> see<02:14:22.800> the<02:14:23.360> db25<02:14:24.360> on<02:14:24.840> uh<02:14:25.139> like<02:14:25.440> a<02:14:25.619> printer 02:14:25.910 --> 02:14:25.920 align:start position:0% to see the db25 on uh like a printer 02:14:25.920 --> 02:14:28.069 align:start position:0% to see the db25 on uh like a printer cable<02:14:26.159> or<02:14:26.340> something<02:14:26.520> like<02:14:26.820> that<02:14:27.000> again<02:14:27.840> if 02:14:28.069 --> 02:14:28.079 align:start position:0% cable or something like that again if 02:14:28.079 --> 02:14:29.569 align:start position:0% cable or something like that again if you<02:14:28.199> see<02:14:28.320> it<02:14:28.500> at<02:14:28.679> all 02:14:29.569 --> 02:14:29.579 align:start position:0% you see it at all 02:14:29.579 --> 02:14:32.450 align:start position:0% you see it at all now<02:14:30.179> the<02:14:30.420> F<02:14:30.719> connector<02:14:31.500> F-Type<02:14:32.159> has<02:14:32.280> been 02:14:32.450 --> 02:14:32.460 align:start position:0% now the F connector F-Type has been 02:14:32.460 --> 02:14:34.729 align:start position:0% now the F connector F-Type has been added<02:14:32.699> to<02:14:32.880> the<02:14:33.060> syllabus<02:14:33.480> not<02:14:34.020> to<02:14:34.199> be<02:14:34.320> confused 02:14:34.729 --> 02:14:34.739 align:start position:0% added to the syllabus not to be confused 02:14:34.739 --> 02:14:39.290 align:start position:0% added to the syllabus not to be confused with<02:14:34.980> fiber<02:14:35.520> cables<02:14:36.060> such<02:14:36.360> as<02:14:36.560> stlc<02:14:37.560> SC<02:14:38.300> which 02:14:39.290 --> 02:14:39.300 align:start position:0% with fiber cables such as stlc SC which 02:14:39.300 --> 02:14:41.689 align:start position:0% with fiber cables such as stlc SC which are<02:14:39.420> covered<02:14:39.719> elsewhere<02:14:40.020> in<02:14:40.500> the<02:14:41.040> in<02:14:41.579> the 02:14:41.689 --> 02:14:41.699 align:start position:0% are covered elsewhere in the in the 02:14:41.699 --> 02:14:43.790 align:start position:0% are covered elsewhere in the in the course<02:14:41.820> here 02:14:43.790 --> 02:14:43.800 align:start position:0% course here 02:14:43.800 --> 02:14:47.410 align:start position:0% course here so<02:14:44.520> it's<02:14:44.699> a<02:14:44.880> coaxial<02:14:45.420> RF<02:14:45.900> connector<02:14:46.500> type 02:14:47.410 --> 02:14:47.420 align:start position:0% so it's a coaxial RF connector type 02:14:47.420 --> 02:14:51.229 align:start position:0% so it's a coaxial RF connector type used<02:14:48.420> more<02:14:49.199> commonly<02:14:49.619> for<02:14:50.040> cable<02:14:50.639> satellite 02:14:51.229 --> 02:14:51.239 align:start position:0% used more commonly for cable satellite 02:14:51.239 --> 02:14:54.350 align:start position:0% used more commonly for cable satellite TV<02:14:51.719> if<02:14:52.320> you've<02:14:52.440> got<02:14:52.560> the<02:14:52.679> back<02:14:52.860> of<02:14:53.040> a<02:14:53.219> box<02:14:53.400> you 02:14:54.350 --> 02:14:54.360 align:start position:0% TV if you've got the back of a box you 02:14:54.360 --> 02:14:56.689 align:start position:0% TV if you've got the back of a box you can<02:14:54.480> see<02:14:54.659> here<02:14:54.960> there's<02:14:55.199> a<02:14:55.500> thread<02:14:55.920> on<02:14:56.579> the 02:14:56.689 --> 02:14:56.699 align:start position:0% can see here there's a thread on the 02:14:56.699 --> 02:14:58.189 align:start position:0% can see here there's a thread on the inside<02:14:56.760> of<02:14:57.060> the<02:14:57.179> cable<02:14:57.420> here<02:14:57.659> and<02:14:57.840> you'd<02:14:58.079> have 02:14:58.189 --> 02:14:58.199 align:start position:0% inside of the cable here and you'd have 02:14:58.199 --> 02:15:02.089 align:start position:0% inside of the cable here and you'd have to<02:14:58.380> turn<02:14:59.040> it<02:14:59.219> round<02:14:59.659> and<02:15:00.659> it'd<02:15:01.500> lock<02:15:01.679> in<02:15:01.860> with 02:15:02.089 --> 02:15:02.099 align:start position:0% to turn it round and it'd lock in with 02:15:02.099 --> 02:15:04.910 align:start position:0% to turn it round and it'd lock in with the<02:15:02.340> TR<02:15:03.179> so<02:15:03.480> you'd<02:15:03.659> have<02:15:03.780> to<02:15:03.960> hopefully<02:15:04.679> with 02:15:04.910 --> 02:15:04.920 align:start position:0% the TR so you'd have to hopefully with 02:15:04.920 --> 02:15:07.069 align:start position:0% the TR so you'd have to hopefully with enough<02:15:05.159> finger<02:15:05.639> pressure<02:15:05.760> be<02:15:06.420> able<02:15:06.599> to<02:15:06.719> secure 02:15:07.069 --> 02:15:07.079 align:start position:0% enough finger pressure be able to secure 02:15:07.079 --> 02:15:10.189 align:start position:0% enough finger pressure be able to secure it<02:15:07.199> into<02:15:07.380> place<02:15:07.679> and<02:15:08.579> then<02:15:08.780> unscrew<02:15:09.780> it<02:15:09.900> those 02:15:10.189 --> 02:15:10.199 align:start position:0% it into place and then unscrew it those 02:15:10.199 --> 02:15:11.569 align:start position:0% it into place and then unscrew it those are<02:15:10.380> when<02:15:10.500> you<02:15:10.619> need<02:15:10.739> to 02:15:11.569 --> 02:15:11.579 align:start position:0% are when you need to 02:15:11.579 --> 02:15:14.930 align:start position:0% are when you need to TV<02:15:12.300> antennas<02:15:12.900> for<02:15:13.440> those<02:15:13.560> user<02:15:13.980> on<02:15:14.159> on<02:15:14.400> using 02:15:14.930 --> 02:15:14.940 align:start position:0% TV antennas for those user on on using 02:15:14.940 --> 02:15:17.569 align:start position:0% TV antennas for those user on on using them<02:15:15.119> your<02:15:16.020> Broadband<02:15:16.860> or<02:15:17.099> Ethernet<02:15:17.340> or 02:15:17.569 --> 02:15:17.579 align:start position:0% them your Broadband or Ethernet or 02:15:17.579 --> 02:15:18.890 align:start position:0% them your Broadband or Ethernet or whatever 02:15:18.890 --> 02:15:18.900 align:start position:0% whatever 02:15:18.900 --> 02:15:20.390 align:start position:0% whatever bandwidth<02:15:19.619> could<02:15:19.739> go<02:15:19.860> up<02:15:19.980> to<02:15:20.099> several 02:15:20.390 --> 02:15:20.400 align:start position:0% bandwidth could go up to several 02:15:20.400 --> 02:15:22.550 align:start position:0% bandwidth could go up to several gigahertz 02:15:22.550 --> 02:15:22.560 align:start position:0% gigahertz 02:15:22.560 --> 02:15:25.370 align:start position:0% gigahertz uh<02:15:22.920> punch<02:15:23.219> down<02:15:23.460> blocks<02:15:24.000> this<02:15:24.840> is<02:15:24.960> a<02:15:25.199> pretty 02:15:25.370 --> 02:15:25.380 align:start position:0% uh punch down blocks this is a pretty 02:15:25.380 --> 02:15:27.350 align:start position:0% uh punch down blocks this is a pretty tricky<02:15:25.800> skill<02:15:26.159> really<02:15:26.340> and<02:15:26.699> one<02:15:26.820> that<02:15:26.940> takes<02:15:27.179> a 02:15:27.350 --> 02:15:27.360 align:start position:0% tricky skill really and one that takes a 02:15:27.360 --> 02:15:30.350 align:start position:0% tricky skill really and one that takes a bit<02:15:27.480> of<02:15:27.599> time<02:15:27.780> but<02:15:28.440> you<02:15:28.619> can<02:15:28.739> see<02:15:28.920> here<02:15:29.360> the 02:15:30.350 --> 02:15:30.360 align:start position:0% bit of time but you can see here the 02:15:30.360 --> 02:15:32.990 align:start position:0% bit of time but you can see here the cable<02:15:30.960> has<02:15:31.739> just<02:15:31.920> been<02:15:32.159> placed<02:15:32.639> in<02:15:32.760> between 02:15:32.990 --> 02:15:33.000 align:start position:0% cable has just been placed in between 02:15:33.000 --> 02:15:35.870 align:start position:0% cable has just been placed in between the<02:15:33.360> runners<02:15:33.840> and<02:15:34.560> then<02:15:34.679> the<02:15:34.860> punch<02:15:35.099> down<02:15:35.340> tool 02:15:35.870 --> 02:15:35.880 align:start position:0% the runners and then the punch down tool 02:15:35.880 --> 02:15:38.629 align:start position:0% the runners and then the punch down tool has<02:15:36.420> kind<02:15:36.659> of<02:15:36.719> got<02:15:36.840> this<02:15:37.139> shape<02:15:37.560> as<02:15:38.340> you<02:15:38.520> can 02:15:38.629 --> 02:15:38.639 align:start position:0% has kind of got this shape as you can 02:15:38.639 --> 02:15:40.069 align:start position:0% has kind of got this shape as you can see<02:15:38.940> here 02:15:40.069 --> 02:15:40.079 align:start position:0% see here 02:15:40.079 --> 02:15:42.890 align:start position:0% see here and<02:15:40.860> this<02:15:41.280> would<02:15:41.460> force<02:15:41.820> the<02:15:41.940> cable<02:15:42.179> in<02:15:42.420> and 02:15:42.890 --> 02:15:42.900 align:start position:0% and this would force the cable in and 02:15:42.900 --> 02:15:45.589 align:start position:0% and this would force the cable in and the<02:15:43.079> theory<02:15:43.320> is<02:15:43.500> it<02:15:43.800> would<02:15:43.980> strip<02:15:44.400> back<02:15:45.360> some 02:15:45.589 --> 02:15:45.599 align:start position:0% the theory is it would strip back some 02:15:45.599 --> 02:15:48.229 align:start position:0% the theory is it would strip back some of<02:15:45.780> this<02:15:46.020> uh<02:15:46.380> coating<02:15:46.739> for<02:15:46.980> the<02:15:47.219> wire<02:15:47.400> and 02:15:48.229 --> 02:15:48.239 align:start position:0% of this uh coating for the wire and 02:15:48.239 --> 02:15:50.629 align:start position:0% of this uh coating for the wire and create<02:15:48.420> a<02:15:48.719> contact<02:15:48.960> inside<02:15:49.920> the<02:15:50.219> punch<02:15:50.340> down 02:15:50.629 --> 02:15:50.639 align:start position:0% create a contact inside the punch down 02:15:50.639 --> 02:15:53.450 align:start position:0% create a contact inside the punch down block<02:15:50.940> takes<02:15:51.780> a<02:15:51.900> bit<02:15:52.020> of<02:15:52.199> skill<02:15:52.440> and<02:15:53.280> it's 02:15:53.450 --> 02:15:53.460 align:start position:0% block takes a bit of skill and it's 02:15:53.460 --> 02:15:54.830 align:start position:0% block takes a bit of skill and it's quite<02:15:53.639> frustrating<02:15:54.060> if<02:15:54.300> you<02:15:54.420> don't<02:15:54.540> do<02:15:54.719> it 02:15:54.830 --> 02:15:54.840 align:start position:0% quite frustrating if you don't do it 02:15:54.840 --> 02:15:56.330 align:start position:0% quite frustrating if you don't do it right<02:15:55.020> or<02:15:55.320> if<02:15:55.500> someone<02:15:55.619> hasn't<02:15:56.040> used<02:15:56.159> the 02:15:56.330 --> 02:15:56.340 align:start position:0% right or if someone hasn't used the 02:15:56.340 --> 02:15:58.550 align:start position:0% right or if someone hasn't used the correct<02:15:56.520> tool<02:15:56.940> it<02:15:57.540> leads<02:15:57.780> to<02:15:57.840> this<02:15:58.079> nightmare 02:15:58.550 --> 02:15:58.560 align:start position:0% correct tool it leads to this nightmare 02:15:58.560 --> 02:16:01.490 align:start position:0% correct tool it leads to this nightmare of<02:15:58.920> intermittent<02:15:59.639> connectivity<02:16:00.599> that<02:16:01.139> you'll 02:16:01.490 --> 02:16:01.500 align:start position:0% of intermittent connectivity that you'll 02:16:01.500 --> 02:16:03.830 align:start position:0% of intermittent connectivity that you'll have<02:16:01.679> to<02:16:01.739> go<02:16:01.860> and<02:16:01.980> troubleshoot 02:16:03.830 --> 02:16:03.840 align:start position:0% have to go and troubleshoot 02:16:03.840 --> 02:16:06.709 align:start position:0% have to go and troubleshoot you'll<02:16:04.380> typically<02:16:04.679> see<02:16:04.920> this<02:16:05.159> in<02:16:05.400> inside<02:16:05.820> a 02:16:06.709 --> 02:16:06.719 align:start position:0% you'll typically see this in inside a 02:16:06.719 --> 02:16:08.450 align:start position:0% you'll typically see this in inside a telephone<02:16:07.020> switch 02:16:08.450 --> 02:16:08.460 align:start position:0% telephone switch 02:16:08.460 --> 02:16:09.410 align:start position:0% telephone switch um 02:16:09.410 --> 02:16:09.420 align:start position:0% um 02:16:09.420 --> 02:16:12.649 align:start position:0% um as<02:16:10.020> switch<02:16:10.460> mechanisms<02:16:11.460> a<02:16:12.179> couple<02:16:12.300> wires 02:16:12.649 --> 02:16:12.659 align:start position:0% as switch mechanisms a couple wires 02:16:12.659 --> 02:16:14.510 align:start position:0% as switch mechanisms a couple wires punched<02:16:13.079> down<02:16:13.199> as<02:16:13.380> I<02:16:13.560> said 02:16:14.510 --> 02:16:14.520 align:start position:0% punched down as I said 02:16:14.520 --> 02:16:17.930 align:start position:0% punched down as I said the<02:16:15.360> numbers<02:16:15.659> are<02:16:16.320> for<02:16:17.040> these<02:16:17.340> models<02:16:17.760> are 02:16:17.930 --> 02:16:17.940 align:start position:0% the numbers are for these models are 02:16:17.940 --> 02:16:21.410 align:start position:0% the numbers are for these models are given<02:16:18.360> uh<02:16:18.960> 66<02:16:19.739> Block<02:16:20.159> it's<02:16:20.520> a<02:16:20.699> model<02:16:20.820> number<02:16:21.119> so 02:16:21.410 --> 02:16:21.420 align:start position:0% given uh 66 Block it's a model number so 02:16:21.420 --> 02:16:23.870 align:start position:0% given uh 66 Block it's a model number so it<02:16:21.540> doesn't<02:16:21.659> mean<02:16:21.840> the<02:16:22.020> 66<02:16:22.500> connectors 02:16:23.870 --> 02:16:23.880 align:start position:0% it doesn't mean the 66 connectors 02:16:23.880 --> 02:16:27.350 align:start position:0% it doesn't mean the 66 connectors that<02:16:24.420> particular<02:16:24.719> one<02:16:24.960> has<02:16:25.139> 55<02:16:25.800> rows<02:16:26.340> it<02:16:27.239> was 02:16:27.350 --> 02:16:27.360 align:start position:0% that particular one has 55 rows it was 02:16:27.360 --> 02:16:29.629 align:start position:0% that particular one has 55 rows it was subject<02:16:27.719> to<02:16:27.900> crosstalk<02:16:28.320> which<02:16:28.739> is<02:16:28.860> known<02:16:29.099> uh 02:16:29.629 --> 02:16:29.639 align:start position:0% subject to crosstalk which is known uh 02:16:29.639 --> 02:16:32.270 align:start position:0% subject to crosstalk which is known uh quite<02:16:30.000> known<02:16:30.360> quite<02:16:30.599> well<02:16:30.719> in<02:16:30.900> the<02:16:31.020> industry 02:16:32.270 --> 02:16:32.280 align:start position:0% quite known quite well in the industry 02:16:32.280 --> 02:16:34.969 align:start position:0% quite known quite well in the industry had<02:16:32.880> a<02:16:33.059> reputation<02:16:33.719> for<02:16:33.960> that<02:16:34.139> not<02:16:34.620> suitable 02:16:34.969 --> 02:16:34.979 align:start position:0% had a reputation for that not suitable 02:16:34.979 --> 02:16:39.349 align:start position:0% had a reputation for that not suitable for<02:16:35.280> high<02:16:35.519> speed<02:16:35.760> connections<02:16:36.359> of<02:16:36.660> 100<02:16:36.840> Meg<02:16:37.439> or 02:16:39.349 --> 02:16:39.359 align:start position:0% for high speed connections of 100 Meg or 02:16:39.359 --> 02:16:41.150 align:start position:0% for high speed connections of 100 Meg or um<02:16:39.420> or<02:16:40.139> hayab 02:16:41.150 --> 02:16:41.160 align:start position:0% um or hayab 02:16:41.160 --> 02:16:44.450 align:start position:0% um or hayab now<02:16:41.760> the<02:16:42.000> 100<02:16:42.240> block<02:16:42.719> replaced<02:16:43.559> the<02:16:43.679> 66<02:16:44.160> block 02:16:44.450 --> 02:16:44.460 align:start position:0% now the 100 block replaced the 66 block 02:16:44.460 --> 02:16:48.169 align:start position:0% now the 100 block replaced the 66 block so<02:16:45.120> just<02:16:45.359> remember<02:16:45.599> the<02:16:46.019> numbers<02:16:46.679> here<02:16:47.519> the<02:16:47.760> 66 02:16:48.169 --> 02:16:48.179 align:start position:0% so just remember the numbers here the 66 02:16:48.179 --> 02:16:50.330 align:start position:0% so just remember the numbers here the 66 block<02:16:48.540> hopefully<02:16:49.500> they<02:16:49.620> won't<02:16:49.740> try<02:16:49.920> and<02:16:50.040> catch 02:16:50.330 --> 02:16:50.340 align:start position:0% block hopefully they won't try and catch 02:16:50.340 --> 02:16:52.610 align:start position:0% block hopefully they won't try and catch you<02:16:50.399> out<02:16:50.580> with<02:16:50.700> the<02:16:51.179> um<02:16:51.179> question<02:16:51.599> saying<02:16:52.139> it's 02:16:52.610 --> 02:16:52.620 align:start position:0% you out with the um question saying it's 02:16:52.620 --> 02:16:54.530 align:start position:0% you out with the um question saying it's got<02:16:52.800> 66<02:16:53.340> Connections<02:16:53.880> in<02:16:54.000> it's<02:16:54.240> a<02:16:54.359> model 02:16:54.530 --> 02:16:54.540 align:start position:0% got 66 Connections in it's a model 02:16:54.540 --> 02:16:56.870 align:start position:0% got 66 Connections in it's a model number<02:16:54.840> just<02:16:55.500> to<02:16:55.679> confuse<02:16:56.040> you 02:16:56.870 --> 02:16:56.880 align:start position:0% number just to confuse you 02:16:56.880 --> 02:16:59.990 align:start position:0% number just to confuse you often<02:16:57.599> used<02:16:57.780> the<02:16:58.200> 100<02:16:58.380> is<02:16:58.800> to<02:16:59.160> terminate<02:16:59.760> cable 02:16:59.990 --> 02:17:00.000 align:start position:0% often used the 100 is to terminate cable 02:17:00.000 --> 02:17:01.849 align:start position:0% often used the 100 is to terminate cable runs 02:17:01.849 --> 02:17:01.859 align:start position:0% runs 02:17:01.859 --> 02:17:04.190 align:start position:0% runs the<02:17:02.099> fiber<02:17:02.519> distribution<02:17:03.000> plan<02:17:03.359> and<02:17:03.719> panel 02:17:04.190 --> 02:17:04.200 align:start position:0% the fiber distribution plan and panel 02:17:04.200 --> 02:17:06.110 align:start position:0% the fiber distribution plan and panel how<02:17:04.439> to<02:17:04.559> get<02:17:04.679> images<02:17:04.920> of<02:17:05.280> this<02:17:05.460> but<02:17:05.700> I've<02:17:05.939> I've 02:17:06.110 --> 02:17:06.120 align:start position:0% how to get images of this but I've I've 02:17:06.120 --> 02:17:08.150 align:start position:0% how to get images of this but I've I've got<02:17:06.359> one<02:17:06.540> that<02:17:06.719> you<02:17:06.840> can<02:17:06.960> actually<02:17:07.200> uh<02:17:07.800> buy 02:17:08.150 --> 02:17:08.160 align:start position:0% got one that you can actually uh buy 02:17:08.160 --> 02:17:10.429 align:start position:0% got one that you can actually uh buy from<02:17:08.460> the<02:17:08.580> manufacturer<02:17:09.359> this<02:17:09.960> one<02:17:10.080> obviously 02:17:10.429 --> 02:17:10.439 align:start position:0% from the manufacturer this one obviously 02:17:10.439 --> 02:17:12.650 align:start position:0% from the manufacturer this one obviously hasn't<02:17:10.800> been<02:17:11.040> set<02:17:11.460> up<02:17:11.580> at<02:17:11.820> all<02:17:11.939> it's<02:17:12.179> a<02:17:12.359> bare 02:17:12.650 --> 02:17:12.660 align:start position:0% hasn't been set up at all it's a bare 02:17:12.660 --> 02:17:15.110 align:start position:0% hasn't been set up at all it's a bare bone<02:17:12.899> system<02:17:13.139> that<02:17:13.859> you<02:17:14.099> would<02:17:14.219> run<02:17:14.460> all<02:17:15.000> of 02:17:15.110 --> 02:17:15.120 align:start position:0% bone system that you would run all of 02:17:15.120 --> 02:17:18.169 align:start position:0% bone system that you would run all of the<02:17:15.240> cables<02:17:15.719> through<02:17:16.019> here<02:17:16.639> and<02:17:17.639> then 02:17:18.169 --> 02:17:18.179 align:start position:0% the cables through here and then 02:17:18.179 --> 02:17:19.310 align:start position:0% the cables through here and then terminate 02:17:19.310 --> 02:17:19.320 align:start position:0% terminate 02:17:19.320 --> 02:17:21.469 align:start position:0% terminate so<02:17:20.040> this<02:17:20.280> is<02:17:20.399> also<02:17:20.580> known<02:17:20.760> as<02:17:20.939> the<02:17:21.120> fiber 02:17:21.469 --> 02:17:21.479 align:start position:0% so this is also known as the fiber 02:17:21.479 --> 02:17:23.690 align:start position:0% so this is also known as the fiber Distribution<02:17:22.080> Hub<02:17:22.620> if<02:17:22.979> you're<02:17:23.099> searching<02:17:23.580> for 02:17:23.690 --> 02:17:23.700 align:start position:0% Distribution Hub if you're searching for 02:17:23.700 --> 02:17:25.669 align:start position:0% Distribution Hub if you're searching for one<02:17:23.880> to<02:17:24.059> buy<02:17:24.240> I<02:17:24.840> think<02:17:25.139> they<02:17:25.380> give<02:17:25.559> you 02:17:25.669 --> 02:17:25.679 align:start position:0% one to buy I think they give you 02:17:25.679 --> 02:17:27.230 align:start position:0% one to buy I think they give you different<02:17:25.920> terms<02:17:26.340> depending<02:17:26.700> on<02:17:26.820> which<02:17:27.059> part 02:17:27.230 --> 02:17:27.240 align:start position:0% different terms depending on which part 02:17:27.240 --> 02:17:28.969 align:start position:0% different terms depending on which part of<02:17:27.359> the<02:17:27.420> country<02:17:27.599> you're<02:17:27.840> in<02:17:28.080> or<02:17:28.800> which 02:17:28.969 --> 02:17:28.979 align:start position:0% of the country you're in or which 02:17:28.979 --> 02:17:31.129 align:start position:0% of the country you're in or which country<02:17:29.280> and<02:17:30.000> at<02:17:30.120> the<02:17:30.300> bottom<02:17:30.479> here<02:17:30.719> I've<02:17:30.899> got 02:17:31.129 --> 02:17:31.139 align:start position:0% country and at the bottom here I've got 02:17:31.139 --> 02:17:34.250 align:start position:0% country and at the bottom here I've got a<02:17:31.439> URL<02:17:32.099> for<02:17:32.880> a<02:17:33.059> particular<02:17:33.540> company<02:17:33.840> that 02:17:34.250 --> 02:17:34.260 align:start position:0% a URL for a particular company that 02:17:34.260 --> 02:17:35.389 align:start position:0% a URL for a particular company that sells<02:17:34.740> them 02:17:35.389 --> 02:17:35.399 align:start position:0% sells them 02:17:35.399 --> 02:17:37.310 align:start position:0% sells them obviously<02:17:35.939> speak<02:17:36.120> to<02:17:36.300> the<02:17:36.479> sales<02:17:36.599> advisor<02:17:37.200> and 02:17:37.310 --> 02:17:37.320 align:start position:0% obviously speak to the sales advisor and 02:17:37.320 --> 02:17:39.110 align:start position:0% obviously speak to the sales advisor and find<02:17:37.500> out<02:17:37.679> what<02:17:37.920> you<02:17:38.040> need 02:17:39.110 --> 02:17:39.120 align:start position:0% find out what you need 02:17:39.120 --> 02:17:41.690 align:start position:0% find out what you need saves<02:17:39.780> you<02:17:40.260> um<02:17:40.260> making<02:17:40.679> expensive<02:17:41.280> mistakes 02:17:41.690 --> 02:17:41.700 align:start position:0% saves you um making expensive mistakes 02:17:41.700 --> 02:17:43.910 align:start position:0% saves you um making expensive mistakes this<02:17:42.660> is<02:17:42.780> the<02:17:42.899> patch<02:17:43.260> panel<02:17:43.559> used<02:17:43.740> to 02:17:43.910 --> 02:17:43.920 align:start position:0% this is the patch panel used to 02:17:43.920 --> 02:17:46.610 align:start position:0% this is the patch panel used to terminate<02:17:44.399> fiber<02:17:45.059> optic<02:17:45.359> cables 02:17:46.610 --> 02:17:46.620 align:start position:0% terminate fiber optic cables 02:17:46.620 --> 02:17:49.849 align:start position:0% terminate fiber optic cables access<02:17:47.160> to<02:17:47.460> the<02:17:47.639> cables<02:17:48.320> individual<02:17:49.320> strands 02:17:49.849 --> 02:17:49.859 align:start position:0% access to the cables individual strands 02:17:49.859 --> 02:17:53.089 align:start position:0% access to the cables individual strands the<02:17:50.099> so<02:17:50.280> the<02:17:50.519> strands<02:17:51.120> inside<02:17:51.300> the<02:17:51.780> cable<02:17:52.260> for 02:17:53.089 --> 02:17:53.099 align:start position:0% the so the strands inside the cable for 02:17:53.099 --> 02:17:54.770 align:start position:0% the so the strands inside the cable for cross<02:17:53.340> connection 02:17:54.770 --> 02:17:54.780 align:start position:0% cross connection 02:17:54.780 --> 02:17:58.610 align:start position:0% cross connection now<02:17:55.439> I<02:17:55.679> do<02:17:55.800> apologize<02:17:56.280> for<02:17:56.639> this<02:17:56.820> however 02:17:58.610 --> 02:17:58.620 align:start position:0% now I do apologize for this however 02:17:58.620 --> 02:17:59.450 align:start position:0% now I do apologize for this however um 02:17:59.450 --> 02:17:59.460 align:start position:0% um 02:17:59.460 --> 02:18:01.549 align:start position:0% um it's<02:17:59.939> in<02:18:00.120> the<02:18:00.240> syllabus<02:18:00.599> now<02:18:00.840> for<02:18:01.200> some<02:18:01.320> crazy 02:18:01.549 --> 02:18:01.559 align:start position:0% it's in the syllabus now for some crazy 02:18:01.559 --> 02:18:05.209 align:start position:0% it's in the syllabus now for some crazy reason<02:18:02.120> previously<02:18:03.120> we<02:18:03.660> had<02:18:04.380> um<02:18:04.380> other<02:18:04.679> RG 02:18:05.209 --> 02:18:05.219 align:start position:0% reason previously we had um other RG 02:18:05.219 --> 02:18:07.270 align:start position:0% reason previously we had um other RG standards<02:18:05.760> I<02:18:05.880> think<02:18:06.000> it<02:18:06.179> was 02:18:07.270 --> 02:18:07.280 align:start position:0% standards I think it was 02:18:07.280 --> 02:18:11.870 align:start position:0% standards I think it was rg9<02:18:08.280> or<02:18:09.179> and<02:18:09.800> RG58<02:18:10.800> I'll<02:18:11.160> have<02:18:11.340> to<02:18:11.460> check<02:18:11.580> you 02:18:11.870 --> 02:18:11.880 align:start position:0% rg9 or and RG58 I'll have to check you 02:18:11.880 --> 02:18:13.910 align:start position:0% rg9 or and RG58 I'll have to check you you<02:18:12.059> can<02:18:12.179> see<02:18:12.300> it<02:18:12.420> in<02:18:12.479> earlier<02:18:12.920> presentations 02:18:13.910 --> 02:18:13.920 align:start position:0% you can see it in earlier presentations 02:18:13.920 --> 02:18:17.030 align:start position:0% you can see it in earlier presentations anyway<02:18:14.420> however<02:18:15.420> now<02:18:15.660> they've<02:18:15.960> asked<02:18:16.200> for<02:18:16.320> RG6 02:18:17.030 --> 02:18:17.040 align:start position:0% anyway however now they've asked for RG6 02:18:17.040 --> 02:18:18.129 align:start position:0% anyway however now they've asked for RG6 and 02:18:18.129 --> 02:18:18.139 align:start position:0% and 02:18:18.139 --> 02:18:20.929 align:start position:0% and rg59<02:18:19.139> so<02:18:19.439> I've<02:18:19.920> highlighted<02:18:20.460> what<02:18:20.639> you<02:18:20.820> need 02:18:20.929 --> 02:18:20.939 align:start position:0% rg59 so I've highlighted what you need 02:18:20.939 --> 02:18:24.110 align:start position:0% rg59 so I've highlighted what you need to<02:18:21.059> do<02:18:21.240> I<02:18:22.019> suggest<02:18:22.320> you<02:18:22.500> make<02:18:22.679> some<02:18:22.979> notes 02:18:24.110 --> 02:18:24.120 align:start position:0% to do I suggest you make some notes 02:18:24.120 --> 02:18:26.990 align:start position:0% to do I suggest you make some notes as<02:18:24.840> to<02:18:25.439> um<02:18:25.439> impedance<02:18:26.099> which<02:18:26.399> is<02:18:26.519> all<02:18:26.700> the<02:18:26.880> same 02:18:26.990 --> 02:18:27.000 align:start position:0% as to um impedance which is all the same 02:18:27.000 --> 02:18:30.290 align:start position:0% as to um impedance which is all the same actually<02:18:27.300> so<02:18:27.719> it<02:18:27.840> shouldn't<02:18:28.200> be<02:18:28.260> too<02:18:28.439> easy 02:18:30.290 --> 02:18:30.300 align:start position:0% actually so it shouldn't be too easy 02:18:30.300 --> 02:18:30.969 align:start position:0% actually so it shouldn't be too easy um 02:18:30.969 --> 02:18:30.979 align:start position:0% um 02:18:30.979 --> 02:18:34.250 align:start position:0% um shielding<02:18:31.979> here<02:18:32.399> and<02:18:33.000> then<02:18:33.179> just<02:18:33.420> make<02:18:33.899> a<02:18:34.080> note 02:18:34.250 --> 02:18:34.260 align:start position:0% shielding here and then just make a note 02:18:34.260 --> 02:18:36.230 align:start position:0% shielding here and then just make a note of<02:18:34.559> what<02:18:34.859> they've<02:18:35.160> what<02:18:35.580> they've<02:18:35.760> said<02:18:35.939> here 02:18:36.230 --> 02:18:36.240 align:start position:0% of what they've what they've said here 02:18:36.240 --> 02:18:38.030 align:start position:0% of what they've what they've said here so 02:18:38.030 --> 02:18:38.040 align:start position:0% so 02:18:38.040 --> 02:18:38.650 align:start position:0% so um 02:18:38.650 --> 02:18:38.660 align:start position:0% um 02:18:38.660 --> 02:18:40.250 align:start position:0% um RG6 02:18:40.250 --> 02:18:40.260 align:start position:0% RG6 02:18:40.260 --> 02:18:45.290 align:start position:0% RG6 uh<02:18:41.040> Slash<02:18:41.760> U<02:18:42.000> what<02:18:42.540> is<02:18:42.719> used<02:18:42.960> for<02:18:43.260> the<02:18:44.040> uq 02:18:45.290 --> 02:18:45.300 align:start position:0% uh Slash U what is used for the uq 02:18:45.300 --> 02:18:47.509 align:start position:0% uh Slash U what is used for the uq again<02:18:45.780> this<02:18:46.139> is<02:18:46.260> just<02:18:46.439> such<02:18:46.679> a<02:18:46.859> pain<02:18:47.099> and<02:18:47.399> it's 02:18:47.509 --> 02:18:47.519 align:start position:0% again this is just such a pain and it's 02:18:47.519 --> 02:18:49.490 align:start position:0% again this is just such a pain and it's silly<02:18:47.880> because<02:18:48.059> you'd<02:18:48.479> if<02:18:48.960> you're<02:18:49.139> having 02:18:49.490 --> 02:18:49.500 align:start position:0% silly because you'd if you're having 02:18:49.500 --> 02:18:51.709 align:start position:0% silly because you'd if you're having anything<02:18:49.740> to<02:18:49.920> do<02:18:50.099> with<02:18:50.219> this<02:18:50.340> you<02:18:50.580> just<02:18:51.240> check 02:18:51.709 --> 02:18:51.719 align:start position:0% anything to do with this you just check 02:18:51.719 --> 02:18:53.990 align:start position:0% anything to do with this you just check the<02:18:51.899> documentation<02:18:52.439> before<02:18:52.800> you<02:18:53.160> went<02:18:53.340> on 02:18:53.990 --> 02:18:54.000 align:start position:0% the documentation before you went on 02:18:54.000 --> 02:18:56.330 align:start position:0% the documentation before you went on site<02:18:54.240> it's<02:18:54.840> very<02:18:55.080> unlikely<02:18:55.559> most<02:18:55.740> Engineers 02:18:56.330 --> 02:18:56.340 align:start position:0% site it's very unlikely most Engineers 02:18:56.340 --> 02:18:59.030 align:start position:0% site it's very unlikely most Engineers if<02:18:56.700> you<02:18:56.820> asked<02:18:57.120> most<02:18:57.300> Network<02:18:57.540> engineers<02:18:58.200> and 02:18:59.030 --> 02:18:59.040 align:start position:0% if you asked most Network engineers and 02:18:59.040 --> 02:19:01.849 align:start position:0% if you asked most Network engineers and what<02:18:59.280> can<02:18:59.399> you<02:18:59.519> tell<02:18:59.700> me<02:18:59.820> about<02:19:00.139> rg59<02:19:01.139> Slash<02:19:01.620> U 02:19:01.849 --> 02:19:01.859 align:start position:0% what can you tell me about rg59 Slash U 02:19:01.859 --> 02:19:03.650 align:start position:0% what can you tell me about rg59 Slash U there's<02:19:02.639> probably<02:19:02.820> not<02:19:03.059> a<02:19:03.240> lot<02:19:03.300> they<02:19:03.479> could 02:19:03.650 --> 02:19:03.660 align:start position:0% there's probably not a lot they could 02:19:03.660 --> 02:19:06.169 align:start position:0% there's probably not a lot they could say<02:19:03.840> however<02:19:04.559> I<02:19:05.280> don't<02:19:05.399> make<02:19:05.580> the<02:19:05.700> rules<02:19:05.880> it's 02:19:06.169 --> 02:19:06.179 align:start position:0% say however I don't make the rules it's 02:19:06.179 --> 02:19:08.929 align:start position:0% say however I don't make the rules it's in<02:19:06.359> the<02:19:06.479> syllabus<02:19:06.840> so<02:19:07.080> just<02:19:07.439> take<02:19:07.620> notes<02:19:08.099> and 02:19:08.929 --> 02:19:08.939 align:start position:0% in the syllabus so just take notes and 02:19:08.939 --> 02:19:11.089 align:start position:0% in the syllabus so just take notes and just<02:19:09.599> chop<02:19:10.200> that<02:19:10.320> up<02:19:10.500> to<02:19:10.620> something<02:19:10.859> you're 02:19:11.089 --> 02:19:11.099 align:start position:0% just chop that up to something you're 02:19:11.099 --> 02:19:12.230 align:start position:0% just chop that up to something you're gonna<02:19:11.219> have<02:19:11.399> to<02:19:11.519> learn 02:19:12.230 --> 02:19:12.240 align:start position:0% gonna have to learn 02:19:12.240 --> 02:19:14.270 align:start position:0% gonna have to learn uh<02:19:12.840> transceivers<02:19:13.620> I've<02:19:13.800> got<02:19:13.920> some<02:19:14.040> images 02:19:14.270 --> 02:19:14.280 align:start position:0% uh transceivers I've got some images 02:19:14.280 --> 02:19:17.629 align:start position:0% uh transceivers I've got some images here<02:19:14.760> these<02:19:15.240> are<02:19:15.359> for<02:19:15.960> um<02:19:15.960> the<02:19:16.260> SPF<02:19:16.800> SPF<02:19:17.460> plus 02:19:17.629 --> 02:19:17.639 align:start position:0% here these are for um the SPF SPF plus 02:19:17.639 --> 02:19:21.709 align:start position:0% here these are for um the SPF SPF plus and<02:19:18.359> gbic<02:19:19.019> which<02:19:19.859> are<02:19:20.099> connectors<02:19:20.880> for<02:19:21.240> Cisco 02:19:21.709 --> 02:19:21.719 align:start position:0% and gbic which are connectors for Cisco 02:19:21.719 --> 02:19:24.169 align:start position:0% and gbic which are connectors for Cisco equipment<02:19:22.200> these 02:19:24.169 --> 02:19:24.179 align:start position:0% equipment these 02:19:24.179 --> 02:19:25.429 align:start position:0% equipment these um 02:19:25.429 --> 02:19:25.439 align:start position:0% um 02:19:25.439 --> 02:19:27.530 align:start position:0% um these<02:19:26.040> would<02:19:26.160> stand<02:19:26.340> proud<02:19:26.820> from<02:19:27.120> the<02:19:27.300> switch 02:19:27.530 --> 02:19:27.540 align:start position:0% these would stand proud from the switch 02:19:27.540 --> 02:19:29.929 align:start position:0% these would stand proud from the switch chassis<02:19:28.080> and<02:19:28.679> then<02:19:28.740> this<02:19:28.979> would<02:19:29.099> be<02:19:29.280> inserted 02:19:29.929 --> 02:19:29.939 align:start position:0% chassis and then this would be inserted 02:19:29.939 --> 02:19:31.910 align:start position:0% chassis and then this would be inserted in<02:19:30.120> and<02:19:30.599> make<02:19:30.780> contact<02:19:31.019> to<02:19:31.380> the<02:19:31.500> back<02:19:31.620> of<02:19:31.800> the 02:19:31.910 --> 02:19:31.920 align:start position:0% in and make contact to the back of the 02:19:31.920 --> 02:19:33.830 align:start position:0% in and make contact to the back of the chassis<02:19:32.340> so<02:19:32.639> here's<02:19:33.179> the<02:19:33.300> front<02:19:33.479> of<02:19:33.660> the 02:19:33.830 --> 02:19:33.840 align:start position:0% chassis so here's the front of the 02:19:33.840 --> 02:19:36.230 align:start position:0% chassis so here's the front of the chassis<02:19:34.559> here<02:19:34.859> here<02:19:35.399> and<02:19:35.939> you<02:19:36.059> wouldn't 02:19:36.230 --> 02:19:36.240 align:start position:0% chassis here here and you wouldn't 02:19:36.240 --> 02:19:38.089 align:start position:0% chassis here here and you wouldn't actually<02:19:36.420> see<02:19:36.719> the<02:19:36.899> back<02:19:37.139> and<02:19:37.679> there's<02:19:37.859> this 02:19:38.089 --> 02:19:38.099 align:start position:0% actually see the back and there's this 02:19:38.099 --> 02:19:41.150 align:start position:0% actually see the back and there's this has<02:19:38.219> got<02:19:38.399> a<02:19:38.580> nice<02:19:38.760> thin<02:19:39.179> slot<02:19:39.840> that<02:19:40.800> you<02:19:41.040> would 02:19:41.150 --> 02:19:41.160 align:start position:0% has got a nice thin slot that you would 02:19:41.160 --> 02:19:43.370 align:start position:0% has got a nice thin slot that you would insert<02:19:41.760> to 02:19:43.370 --> 02:19:43.380 align:start position:0% insert to 02:19:43.380 --> 02:19:44.929 align:start position:0% insert to yeah 02:19:44.929 --> 02:19:44.939 align:start position:0% yeah 02:19:44.939 --> 02:19:48.290 align:start position:0% yeah do<02:19:45.479> the<02:19:45.660> 3D<02:19:45.960> version<02:19:46.460> so<02:19:47.460> transceiver<02:19:48.059> is 02:19:48.290 --> 02:19:48.300 align:start position:0% do the 3D version so transceiver is 02:19:48.300 --> 02:19:50.090 align:start position:0% do the 3D version so transceiver is short<02:19:48.479> for<02:19:48.660> transmitter<02:19:49.020> receiver<02:19:49.560> as<02:19:49.920> we 02:19:50.090 --> 02:19:50.100 align:start position:0% short for transmitter receiver as we 02:19:50.100 --> 02:19:51.830 align:start position:0% short for transmitter receiver as we mentioned<02:19:50.399> earlier<02:19:50.700> it<02:19:51.359> converts<02:19:51.720> the 02:19:51.830 --> 02:19:51.840 align:start position:0% mentioned earlier it converts the 02:19:51.840 --> 02:19:53.750 align:start position:0% mentioned earlier it converts the electrical<02:19:52.260> signals<02:19:52.740> from<02:19:52.920> one<02:19:53.160> type<02:19:53.399> to 02:19:53.750 --> 02:19:53.760 align:start position:0% electrical signals from one type to 02:19:53.760 --> 02:19:55.969 align:start position:0% electrical signals from one type to another<02:19:54.000> type<02:19:54.359> so<02:19:54.899> serial<02:19:55.439> to<02:19:55.620> Optical 02:19:55.969 --> 02:19:55.979 align:start position:0% another type so serial to Optical 02:19:55.979 --> 02:19:59.150 align:start position:0% another type so serial to Optical signals<02:19:56.580> and<02:19:57.120> vice<02:19:57.359> versa 02:19:59.150 --> 02:19:59.160 align:start position:0% signals and vice versa 02:19:59.160 --> 02:20:02.270 align:start position:0% signals and vice versa The<02:19:59.880> Cisco<02:20:00.540> gigabit<02:20:01.140> internet<02:20:01.560> interface 02:20:02.270 --> 02:20:02.280 align:start position:0% The Cisco gigabit internet interface 02:20:02.280 --> 02:20:04.790 align:start position:0% The Cisco gigabit internet interface converter<02:20:02.700> we<02:20:03.000> call<02:20:03.180> them<02:20:03.300> gbx<02:20:03.840> it's<02:20:04.560> hot 02:20:04.790 --> 02:20:04.800 align:start position:0% converter we call them gbx it's hot 02:20:04.800 --> 02:20:06.889 align:start position:0% converter we call them gbx it's hot swappable<02:20:05.280> so<02:20:05.760> you<02:20:05.939> pull<02:20:06.120> it<02:20:06.300> out<02:20:06.420> push<02:20:06.720> it 02:20:06.889 --> 02:20:06.899 align:start position:0% swappable so you pull it out push it 02:20:06.899 --> 02:20:09.950 align:start position:0% swappable so you pull it out push it back<02:20:07.080> in<02:20:07.200> again<02:20:07.439> hot<02:20:07.979> swappable<02:20:08.520> here 02:20:09.950 --> 02:20:09.960 align:start position:0% back in again hot swappable here 02:20:09.960 --> 02:20:12.349 align:start position:0% back in again hot swappable here is<02:20:10.560> very<02:20:10.859> handy<02:20:11.160> and<02:20:11.280> I<02:20:11.460> think<02:20:11.520> we'll<02:20:11.760> come<02:20:12.240> to 02:20:12.349 --> 02:20:12.359 align:start position:0% is very handy and I think we'll come to 02:20:12.359 --> 02:20:15.770 align:start position:0% is very handy and I think we'll come to this<02:20:12.540> later<02:20:12.780> actually<02:20:13.140> to<02:20:13.560> find<02:20:13.979> my<02:20:14.359> cursor<02:20:15.359> it 02:20:15.770 --> 02:20:15.780 align:start position:0% this later actually to find my cursor it 02:20:15.780 --> 02:20:17.450 align:start position:0% this later actually to find my cursor it means<02:20:15.960> you<02:20:16.020> don't<02:20:16.200> have<02:20:16.320> to<02:20:16.560> power<02:20:16.740> down<02:20:17.040> your 02:20:17.450 --> 02:20:17.460 align:start position:0% means you don't have to power down your 02:20:17.460 --> 02:20:20.330 align:start position:0% means you don't have to power down your unit<02:20:17.640> which<02:20:18.120> is<02:20:18.240> just<02:20:18.600> absolute<02:20:19.320> gold<02:20:19.680> if 02:20:20.330 --> 02:20:20.340 align:start position:0% unit which is just absolute gold if 02:20:20.340 --> 02:20:21.590 align:start position:0% unit which is just absolute gold if you're<02:20:20.460> working<02:20:20.640> in<02:20:20.939> a<02:20:21.060> production<02:20:21.300> Network 02:20:21.590 --> 02:20:21.600 align:start position:0% you're working in a production Network 02:20:21.600 --> 02:20:23.990 align:start position:0% you're working in a production Network because<02:20:21.960> it's<02:20:22.260> just<02:20:22.500> horrible<02:20:22.880> especially<02:20:23.880> if 02:20:23.990 --> 02:20:24.000 align:start position:0% because it's just horrible especially if 02:20:24.000 --> 02:20:26.630 align:start position:0% because it's just horrible especially if you've<02:20:24.479> got<02:20:24.600> paying<02:20:25.020> customers<02:20:25.560> that<02:20:26.460> are 02:20:26.630 --> 02:20:26.640 align:start position:0% you've got paying customers that are 02:20:26.640 --> 02:20:27.849 align:start position:0% you've got paying customers that are paying<02:20:26.939> for 02:20:27.849 --> 02:20:27.859 align:start position:0% paying for 02:20:27.859 --> 02:20:31.190 align:start position:0% paying for 99.999<02:20:28.859> recurring<02:20:29.760> up<02:20:30.000> time<02:20:30.300> and<02:20:30.960> then<02:20:31.020> you 02:20:31.190 --> 02:20:31.200 align:start position:0% 99.999 recurring up time and then you 02:20:31.200 --> 02:20:32.929 align:start position:0% 99.999 recurring up time and then you tell<02:20:31.320> them<02:20:31.439> you've<02:20:31.620> got<02:20:31.740> a<02:20:31.920> power<02:20:32.040> down<02:20:32.340> the 02:20:32.929 --> 02:20:32.939 align:start position:0% tell them you've got a power down the 02:20:32.939 --> 02:20:35.210 align:start position:0% tell them you've got a power down the device<02:20:33.180> they're<02:20:33.479> connected<02:20:33.899> to<02:20:34.140> and<02:20:34.800> just<02:20:35.040> to 02:20:35.210 --> 02:20:35.220 align:start position:0% device they're connected to and just to 02:20:35.220 --> 02:20:37.670 align:start position:0% device they're connected to and just to swap<02:20:35.399> out<02:20:35.580> something<02:20:35.820> so<02:20:36.240> very<02:20:36.479> handy<02:20:36.840> plugs 02:20:37.670 --> 02:20:37.680 align:start position:0% swap out something so very handy plugs 02:20:37.680 --> 02:20:41.710 align:start position:0% swap out something so very handy plugs into<02:20:37.740> the<02:20:37.979> gigabit<02:20:38.340> Ethernet<02:20:38.819> port<02:20:39.120> or<02:20:39.420> slot 02:20:41.710 --> 02:20:41.720 align:start position:0% into the gigabit Ethernet port or slot 02:20:41.720 --> 02:20:45.349 align:start position:0% into the gigabit Ethernet port or slot SPF<02:20:42.720> stands<02:20:43.439> for<02:20:43.680> small<02:20:44.340> form<02:20:44.819> factor 02:20:45.349 --> 02:20:45.359 align:start position:0% SPF stands for small form factor 02:20:45.359 --> 02:20:47.450 align:start position:0% SPF stands for small form factor pluggable<02:20:45.780> I<02:20:46.380> guess<02:20:46.560> a<02:20:46.740> gigabit<02:20:47.100> interface 02:20:47.450 --> 02:20:47.460 align:start position:0% pluggable I guess a gigabit interface 02:20:47.460 --> 02:20:50.450 align:start position:0% pluggable I guess a gigabit interface converter<02:20:48.420> that<02:20:48.720> too<02:20:48.840> is<02:20:49.020> hot<02:20:49.200> swappable<02:20:49.620> bear 02:20:50.450 --> 02:20:50.460 align:start position:0% converter that too is hot swappable bear 02:20:50.460 --> 02:20:52.550 align:start position:0% converter that too is hot swappable bear in<02:20:50.700> mind<02:20:50.880> what<02:20:51.300> you've<02:20:51.479> got<02:20:51.600> to<02:20:51.720> do<02:20:51.840> is<02:20:52.200> check 02:20:52.550 --> 02:20:52.560 align:start position:0% in mind what you've got to do is check 02:20:52.560 --> 02:20:55.670 align:start position:0% in mind what you've got to do is check for 02:20:55.670 --> 02:20:55.680 align:start position:0% 02:20:55.680 --> 02:20:59.210 align:start position:0% bugs<02:20:56.600> so<02:20:57.600> if<02:20:57.780> say<02:20:58.020> for<02:20:58.200> example<02:20:58.560> you've<02:20:58.920> got<02:20:59.040> a 02:20:59.210 --> 02:20:59.220 align:start position:0% bugs so if say for example you've got a 02:20:59.220 --> 02:21:01.670 align:start position:0% bugs so if say for example you've got a Cisco<02:20:59.580> device<02:21:00.140> and<02:21:01.140> you've<02:21:01.439> read<02:21:01.560> the 02:21:01.670 --> 02:21:01.680 align:start position:0% Cisco device and you've read the 02:21:01.680 --> 02:21:03.550 align:start position:0% Cisco device and you've read the documentation<02:21:02.220> and<02:21:02.460> it<02:21:02.700> says<02:21:02.880> hot<02:21:03.000> swappable 02:21:03.550 --> 02:21:03.560 align:start position:0% documentation and it says hot swappable 02:21:03.560 --> 02:21:06.349 align:start position:0% documentation and it says hot swappable you<02:21:04.560> ask<02:21:04.800> them<02:21:05.040> to<02:21:05.399> do<02:21:05.520> if<02:21:05.819> you've<02:21:06.060> got<02:21:06.120> a 02:21:06.349 --> 02:21:06.359 align:start position:0% you ask them to do if you've got a 02:21:06.359 --> 02:21:10.330 align:start position:0% you ask them to do if you've got a contract<02:21:07.100> a<02:21:08.100> bug 02:21:10.330 --> 02:21:10.340 align:start position:0% contract a bug 02:21:10.340 --> 02:21:12.889 align:start position:0% contract a bug sweep<02:21:11.340> for<02:21:11.939> the 02:21:12.889 --> 02:21:12.899 align:start position:0% sweep for the 02:21:12.899 --> 02:21:16.790 align:start position:0% sweep for the say<02:21:13.680> for<02:21:13.859> example<02:21:14.160> this<02:21:15.000> with<02:21:15.660> the<02:21:15.899> model<02:21:16.140> so 02:21:16.790 --> 02:21:16.800 align:start position:0% say for example this with the model so 02:21:16.800 --> 02:21:19.630 align:start position:0% say for example this with the model so say<02:21:17.660> WC 02:21:19.630 --> 02:21:19.640 align:start position:0% say WC 02:21:19.640 --> 02:21:23.270 align:start position:0% say WC 36<02:21:20.640> whatever<02:21:21.120> the<02:21:21.720> model<02:21:21.899> is<02:21:22.200> you<02:21:22.979> say<02:21:23.100> I've 02:21:23.270 --> 02:21:23.280 align:start position:0% 36 whatever the model is you say I've 02:21:23.280 --> 02:21:25.670 align:start position:0% 36 whatever the model is you say I've got<02:21:23.399> this<02:21:23.580> switch<02:21:23.819> this<02:21:24.300> model<02:21:24.479> uh<02:21:25.319> it<02:21:25.500> says 02:21:25.670 --> 02:21:25.680 align:start position:0% got this switch this model uh it says 02:21:25.680 --> 02:21:28.490 align:start position:0% got this switch this model uh it says it's<02:21:25.800> hot<02:21:25.979> swappable<02:21:26.460> and<02:21:27.359> just<02:21:27.660> do<02:21:27.899> a<02:21:28.260> bug 02:21:28.490 --> 02:21:28.500 align:start position:0% it's hot swappable and just do a bug 02:21:28.500 --> 02:21:30.830 align:start position:0% it's hot swappable and just do a bug sweep<02:21:28.920> this<02:21:29.640> is<02:21:29.760> I<02:21:30.180> only<02:21:30.359> tell<02:21:30.540> you<02:21:30.660> this 02:21:30.830 --> 02:21:30.840 align:start position:0% sweep this is I only tell you this 02:21:30.840 --> 02:21:32.510 align:start position:0% sweep this is I only tell you this because<02:21:31.020> and<02:21:31.439> this<02:21:31.680> is<02:21:31.740> the<02:21:31.920> advantage<02:21:32.340> of 02:21:32.510 --> 02:21:32.520 align:start position:0% because and this is the advantage of 02:21:32.520 --> 02:21:35.030 align:start position:0% because and this is the advantage of having<02:21:32.760> someone<02:21:33.660> like<02:21:33.960> myself<02:21:34.200> not<02:21:34.680> that<02:21:34.859> I'm 02:21:35.030 --> 02:21:35.040 align:start position:0% having someone like myself not that I'm 02:21:35.040 --> 02:21:37.370 align:start position:0% having someone like myself not that I'm boasting<02:21:35.520> but<02:21:35.760> I<02:21:35.939> worked<02:21:36.240> at<02:21:36.359> Cisco 02:21:37.370 --> 02:21:37.380 align:start position:0% boasting but I worked at Cisco 02:21:37.380 --> 02:21:41.090 align:start position:0% boasting but I worked at Cisco and<02:21:37.979> we<02:21:38.160> had<02:21:38.340> a<02:21:38.520> customer<02:21:38.720> who<02:21:39.800> asked<02:21:40.800> one<02:21:40.979> of 02:21:41.090 --> 02:21:41.100 align:start position:0% and we had a customer who asked one of 02:21:41.100 --> 02:21:43.070 align:start position:0% and we had a customer who asked one of our<02:21:41.220> Engineers<02:21:41.760> if<02:21:42.540> something<02:21:42.720> was<02:21:42.960> hot 02:21:43.070 --> 02:21:43.080 align:start position:0% our Engineers if something was hot 02:21:43.080 --> 02:21:45.650 align:start position:0% our Engineers if something was hot swappable<02:21:43.560> the<02:21:44.220> documentation<02:21:44.760> said<02:21:45.060> it<02:21:45.359> was 02:21:45.650 --> 02:21:45.660 align:start position:0% swappable the documentation said it was 02:21:45.660 --> 02:21:47.630 align:start position:0% swappable the documentation said it was however 02:21:47.630 --> 02:21:47.640 align:start position:0% however 02:21:47.640 --> 02:21:49.250 align:start position:0% however um<02:21:47.700> not<02:21:47.939> that<02:21:48.060> it<02:21:48.180> was<02:21:48.359> his<02:21:48.479> fault<02:21:48.720> there<02:21:48.960> was<02:21:49.080> a 02:21:49.250 --> 02:21:49.260 align:start position:0% um not that it was his fault there was a 02:21:49.260 --> 02:21:52.550 align:start position:0% um not that it was his fault there was a bug<02:21:49.640> which<02:21:50.640> he<02:21:50.819> didn't<02:21:51.000> know<02:21:51.240> about<02:21:51.420> and<02:21:52.200> the 02:21:52.550 --> 02:21:52.560 align:start position:0% bug which he didn't know about and the 02:21:52.560 --> 02:21:55.010 align:start position:0% bug which he didn't know about and the customer<02:21:52.740> hot<02:21:53.160> swapped<02:21:53.580> it<02:21:53.760> brought<02:21:54.359> down<02:21:54.660> a 02:21:55.010 --> 02:21:55.020 align:start position:0% customer hot swapped it brought down a 02:21:55.020 --> 02:21:57.530 align:start position:0% customer hot swapped it brought down a core<02:21:55.319> switch<02:21:55.620> it<02:21:56.580> caused<02:21:56.939> a<02:21:57.000> massive<02:21:57.300> amount 02:21:57.530 --> 02:21:57.540 align:start position:0% core switch it caused a massive amount 02:21:57.540 --> 02:21:59.510 align:start position:0% core switch it caused a massive amount of<02:21:57.660> problems<02:21:58.080> there<02:21:58.319> was<02:21:58.500> I<02:21:58.680> think<02:21:58.800> some<02:21:59.160> legal 02:21:59.510 --> 02:21:59.520 align:start position:0% of problems there was I think some legal 02:21:59.520 --> 02:22:01.790 align:start position:0% of problems there was I think some legal claims<02:22:00.000> or<02:22:00.180> whatever<02:22:00.300> it's<02:22:01.080> just<02:22:01.260> headaches 02:22:01.790 --> 02:22:01.800 align:start position:0% claims or whatever it's just headaches 02:22:01.800 --> 02:22:04.370 align:start position:0% claims or whatever it's just headaches you<02:22:01.979> don't<02:22:02.160> need<02:22:02.460> so<02:22:03.420> if<02:22:03.899> you've<02:22:04.020> got<02:22:04.140> the 02:22:04.370 --> 02:22:04.380 align:start position:0% you don't need so if you've got the 02:22:04.380 --> 02:22:05.510 align:start position:0% you don't need so if you've got the contract 02:22:05.510 --> 02:22:05.520 align:start position:0% contract 02:22:05.520 --> 02:22:07.429 align:start position:0% contract and<02:22:06.120> just<02:22:06.300> because<02:22:06.479> it<02:22:06.660> says<02:22:06.780> hot<02:22:06.960> swappable 02:22:07.429 --> 02:22:07.439 align:start position:0% and just because it says hot swappable 02:22:07.439 --> 02:22:10.010 align:start position:0% and just because it says hot swappable don't<02:22:08.399> necessarily<02:22:09.300> take<02:22:09.479> that<02:22:09.660> on<02:22:09.840> face 02:22:10.010 --> 02:22:10.020 align:start position:0% don't necessarily take that on face 02:22:10.020 --> 02:22:12.349 align:start position:0% don't necessarily take that on face value<02:22:10.260> and<02:22:10.500> if<02:22:10.680> you<02:22:10.859> if<02:22:11.100> you<02:22:11.340> can<02:22:11.460> log<02:22:11.880> a<02:22:12.180> ticket 02:22:12.349 --> 02:22:12.359 align:start position:0% value and if you if you can log a ticket 02:22:12.359 --> 02:22:15.110 align:start position:0% value and if you if you can log a ticket or<02:22:12.899> do<02:22:13.080> a<02:22:13.200> search 02:22:15.110 --> 02:22:15.120 align:start position:0% or do a search 02:22:15.120 --> 02:22:17.570 align:start position:0% or do a search SPF<02:22:15.840> plus<02:22:16.020> is<02:22:16.260> in<02:22:16.500> the<02:22:16.620> hearts<02:22:16.979> version<02:22:17.160> the 02:22:17.570 --> 02:22:17.580 align:start position:0% SPF plus is in the hearts version the 02:22:17.580 --> 02:22:19.849 align:start position:0% SPF plus is in the hearts version the hint<02:22:17.760> is<02:22:17.880> in<02:22:18.060> the<02:22:18.180> plus<02:22:18.359> that<02:22:19.020> supports<02:22:19.439> higher 02:22:19.849 --> 02:22:19.859 align:start position:0% hint is in the plus that supports higher 02:22:19.859 --> 02:22:22.670 align:start position:0% hint is in the plus that supports higher data<02:22:20.280> rates<02:22:20.819> and<02:22:21.420> this<02:22:21.720> time<02:22:21.840> up<02:22:22.080> to<02:22:22.319> 16 02:22:22.670 --> 02:22:22.680 align:start position:0% data rates and this time up to 16 02:22:22.680 --> 02:22:25.309 align:start position:0% data rates and this time up to 16 gigabits<02:22:23.399> per<02:22:23.520> second 02:22:25.309 --> 02:22:25.319 align:start position:0% gigabits per second 02:22:25.319 --> 02:22:26.929 align:start position:0% gigabits per second and<02:22:25.800> then<02:22:25.920> finally<02:22:26.220> I<02:22:26.399> don't<02:22:26.520> have<02:22:26.640> a<02:22:26.760> picture 02:22:26.929 --> 02:22:26.939 align:start position:0% and then finally I don't have a picture 02:22:26.939 --> 02:22:30.410 align:start position:0% and then finally I don't have a picture here<02:22:27.240> a<02:22:27.660> quad<02:22:28.020> small<02:22:28.319> form<02:22:28.620> factable<02:22:29.280> a<02:22:29.939> factor 02:22:30.410 --> 02:22:30.420 align:start position:0% here a quad small form factable a factor 02:22:30.420 --> 02:22:33.590 align:start position:0% here a quad small form factable a factor plugable<02:22:30.840> and<02:22:31.740> you've<02:22:31.979> got<02:22:32.100> different<02:22:32.600> speeds 02:22:33.590 --> 02:22:33.600 align:start position:0% plugable and you've got different speeds 02:22:33.600 --> 02:22:36.349 align:start position:0% plugable and you've got different speeds just<02:22:33.840> check<02:22:34.020> the<02:22:34.200> documentation<02:22:34.800> on<02:22:35.640> that<02:22:35.819> I 02:22:36.349 --> 02:22:36.359 align:start position:0% just check the documentation on that I 02:22:36.359 --> 02:22:39.170 align:start position:0% just check the documentation on that I just<02:22:36.479> wanted<02:22:36.720> to<02:22:37.740> um<02:22:37.740> flag<02:22:38.460> it<02:22:38.700> up<02:22:38.819> I<02:22:39.120> think 02:22:39.170 --> 02:22:39.180 align:start position:0% just wanted to um flag it up I think 02:22:39.180 --> 02:22:41.469 align:start position:0% just wanted to um flag it up I think it's<02:22:39.359> actually<02:22:39.540> in<02:22:39.780> the<02:22:39.899> syllabus<02:22:40.260> also 02:22:41.469 --> 02:22:41.479 align:start position:0% it's actually in the syllabus also 02:22:41.479 --> 02:22:45.170 align:start position:0% it's actually in the syllabus also uh<02:22:42.479> so<02:22:43.140> we've<02:22:43.380> just<02:22:43.620> got<02:22:43.859> the<02:22:44.220> ghibit<02:22:44.819> module 02:22:45.170 --> 02:22:45.180 align:start position:0% uh so we've just got the ghibit module 02:22:45.180 --> 02:22:47.809 align:start position:0% uh so we've just got the ghibit module here<02:22:45.359> and<02:22:45.540> you<02:22:45.780> can<02:22:45.899> see<02:22:46.140> the<02:22:46.979> uh<02:22:47.160> the<02:22:47.399> chassis 02:22:47.809 --> 02:22:47.819 align:start position:0% here and you can see the uh the chassis 02:22:47.819 --> 02:22:49.250 align:start position:0% here and you can see the uh the chassis would<02:22:48.060> actually<02:22:48.180> be<02:22:48.479> here<02:22:48.720> so<02:22:48.960> you<02:22:49.140> wouldn't 02:22:49.250 --> 02:22:49.260 align:start position:0% would actually be here so you wouldn't 02:22:49.260 --> 02:22:51.710 align:start position:0% would actually be here so you wouldn't see<02:22:49.680> all<02:22:49.920> this<02:22:50.040> typically<02:22:50.520> and<02:22:51.359> then<02:22:51.479> you'd 02:22:51.710 --> 02:22:51.720 align:start position:0% see all this typically and then you'd 02:22:51.720 --> 02:22:53.690 align:start position:0% see all this typically and then you'd have<02:22:51.899> obviously<02:22:52.260> the<02:22:52.500> slot<02:22:52.859> here<02:22:53.100> and<02:22:53.520> I 02:22:53.690 --> 02:22:53.700 align:start position:0% have obviously the slot here and I 02:22:53.700 --> 02:22:56.210 align:start position:0% have obviously the slot here and I mentioned<02:22:54.000> that<02:22:54.180> only<02:22:54.479> the<02:22:55.319> the<02:22:55.380> end<02:22:55.979> bit 02:22:56.210 --> 02:22:56.220 align:start position:0% mentioned that only the the end bit 02:22:56.220 --> 02:22:59.210 align:start position:0% mentioned that only the the end bit would<02:22:56.460> be<02:22:56.580> proud<02:22:57.000> and<02:22:57.540> you've<02:22:57.720> got<02:22:57.899> two<02:22:58.500> fiber 02:22:59.210 --> 02:22:59.220 align:start position:0% would be proud and you've got two fiber 02:22:59.220 --> 02:23:01.130 align:start position:0% would be proud and you've got two fiber cables<02:22:59.700> in<02:22:59.819> here<02:23:00.000> I'm<02:23:00.479> not<02:23:00.660> sure<02:23:00.780> what<02:23:00.960> this 02:23:01.130 --> 02:23:01.140 align:start position:0% cables in here I'm not sure what this 02:23:01.140 --> 02:23:03.290 align:start position:0% cables in here I'm not sure what this model<02:23:01.380> of<02:23:01.620> the<02:23:01.920> model<02:23:02.580> is<02:23:02.819> that<02:23:02.939> it's<02:23:03.120> actually 02:23:03.290 --> 02:23:03.300 align:start position:0% model of the model is that it's actually 02:23:03.300 --> 02:23:05.690 align:start position:0% model of the model is that it's actually plugging<02:23:03.720> into<02:23:03.899> we're<02:23:04.620> just<02:23:04.800> having<02:23:05.040> a<02:23:05.280> sneaky 02:23:05.690 --> 02:23:05.700 align:start position:0% plugging into we're just having a sneaky 02:23:05.700 --> 02:23:10.010 align:start position:0% plugging into we're just having a sneaky look<02:23:05.939> here<02:23:06.720> at<02:23:07.380> the<02:23:08.040> um<02:23:08.040> circuit<02:23:08.580> board<02:23:08.700> is<02:23:09.359> SPF 02:23:10.010 --> 02:23:10.020 align:start position:0% look here at the um circuit board is SPF 02:23:10.020 --> 02:23:12.530 align:start position:0% look here at the um circuit board is SPF plus<02:23:10.260> and 02:23:12.530 --> 02:23:12.540 align:start position:0% plus and 02:23:12.540 --> 02:23:14.809 align:start position:0% plus and um<02:23:12.600> yeah<02:23:13.080> so<02:23:13.439> just<02:23:13.800> so<02:23:13.979> you<02:23:14.160> can<02:23:14.280> see<02:23:14.460> it 02:23:14.809 --> 02:23:14.819 align:start position:0% um yeah so just so you can see it 02:23:14.819 --> 02:23:17.690 align:start position:0% um yeah so just so you can see it working<02:23:15.060> in<02:23:15.359> an<02:23:15.540> actual<02:23:15.840> device<02:23:16.280> and<02:23:17.280> however 02:23:17.690 --> 02:23:17.700 align:start position:0% working in an actual device and however 02:23:17.700 --> 02:23:19.190 align:start position:0% working in an actual device and however you<02:23:17.880> would<02:23:18.000> set<02:23:18.120> this<02:23:18.359> up<02:23:18.479> I'm<02:23:18.780> not<02:23:18.899> sure<02:23:19.020> if 02:23:19.190 --> 02:23:19.200 align:start position:0% you would set this up I'm not sure if 02:23:19.200 --> 02:23:21.230 align:start position:0% you would set this up I'm not sure if this<02:23:19.439> is<02:23:20.040> um<02:23:20.160> these<02:23:20.760> have<02:23:20.819> been<02:23:20.939> linked 02:23:21.230 --> 02:23:21.240 align:start position:0% this is um these have been linked 02:23:21.240 --> 02:23:23.270 align:start position:0% this is um these have been linked together<02:23:21.420> all<02:23:22.080> the<02:23:22.260> ones<02:23:22.560> operating<02:23:22.920> as<02:23:23.160> a 02:23:23.270 --> 02:23:23.280 align:start position:0% together all the ones operating as a 02:23:23.280 --> 02:23:25.370 align:start position:0% together all the ones operating as a backup<02:23:23.520> to<02:23:23.640> the<02:23:23.880> other<02:23:24.420> so<02:23:24.840> you<02:23:25.020> can<02:23:25.140> see<02:23:25.260> what 02:23:25.370 --> 02:23:25.380 align:start position:0% backup to the other so you can see what 02:23:25.380 --> 02:23:28.429 align:start position:0% backup to the other so you can see what it<02:23:25.560> would<02:23:25.680> look<02:23:25.859> like<02:23:26.040> on<02:23:26.399> a<02:23:26.520> live<02:23:26.700> environment 02:23:28.429 --> 02:23:28.439 align:start position:0% it would look like on a live environment 02:23:28.439 --> 02:23:30.950 align:start position:0% it would look like on a live environment and<02:23:28.920> network<02:23:29.220> storage<02:23:29.520> fiber<02:23:30.060> channel<02:23:30.300> fiber 02:23:30.950 --> 02:23:30.960 align:start position:0% and network storage fiber channel fiber 02:23:30.960 --> 02:23:32.990 align:start position:0% and network storage fiber channel fiber channel<02:23:31.140> ever<02:23:31.380> ethernet<02:23:31.920> it<02:23:32.760> basically 02:23:32.990 --> 02:23:33.000 align:start position:0% channel ever ethernet it basically 02:23:33.000 --> 02:23:35.150 align:start position:0% channel ever ethernet it basically encapsulates<02:23:33.600> fiber<02:23:34.319> channel<02:23:34.500> frames<02:23:34.920> over 02:23:35.150 --> 02:23:35.160 align:start position:0% encapsulates fiber channel frames over 02:23:35.160 --> 02:23:37.429 align:start position:0% encapsulates fiber channel frames over ethernet<02:23:35.700> it's<02:23:36.180> a<02:23:36.359> protocol<02:23:36.660> in<02:23:37.140> its<02:23:37.380> own 02:23:37.429 --> 02:23:37.439 align:start position:0% ethernet it's a protocol in its own 02:23:37.439 --> 02:23:39.290 align:start position:0% ethernet it's a protocol in its own right<02:23:37.680> and<02:23:38.340> it<02:23:38.460> was<02:23:38.640> developed<02:23:39.000> just 02:23:39.290 --> 02:23:39.300 align:start position:0% right and it was developed just 02:23:39.300 --> 02:23:41.570 align:start position:0% right and it was developed just specifically<02:23:39.660> for<02:23:39.899> this<02:23:40.140> environment<02:23:40.680> and 02:23:41.570 --> 02:23:41.580 align:start position:0% specifically for this environment and 02:23:41.580 --> 02:23:43.730 align:start position:0% specifically for this environment and you<02:23:41.700> can<02:23:41.819> see<02:23:42.060> the<02:23:42.720> um<02:23:42.720> fiber<02:23:43.260> channel<02:23:43.439> over 02:23:43.730 --> 02:23:43.740 align:start position:0% you can see the um fiber channel over 02:23:43.740 --> 02:23:46.910 align:start position:0% you can see the um fiber channel over ethernet<02:23:44.340> is<02:23:44.880> working<02:23:45.180> in<02:23:46.080> this<02:23:46.260> part<02:23:46.500> of<02:23:46.740> the 02:23:46.910 --> 02:23:46.920 align:start position:0% ethernet is working in this part of the 02:23:46.920 --> 02:23:49.250 align:start position:0% ethernet is working in this part of the connection<02:23:47.399> here 02:23:49.250 --> 02:23:49.260 align:start position:0% connection here 02:23:49.260 --> 02:23:50.990 align:start position:0% connection here and<02:23:49.800> then<02:23:49.920> it<02:23:50.040> looks<02:23:50.340> like<02:23:50.399> we've<02:23:50.580> got<02:23:50.640> ether 02:23:50.990 --> 02:23:51.000 align:start position:0% and then it looks like we've got ether 02:23:51.000 --> 02:23:53.990 align:start position:0% and then it looks like we've got ether channel<02:23:51.240> here<02:23:51.720> which<02:23:52.740> um<02:23:53.220> I<02:23:53.700> don't<02:23:53.819> think 02:23:53.990 --> 02:23:54.000 align:start position:0% channel here which um I don't think 02:23:54.000 --> 02:23:55.730 align:start position:0% channel here which um I don't think ether<02:23:54.359> channel<02:23:54.600> is<02:23:54.899> specifically<02:23:55.380> covered 02:23:55.730 --> 02:23:55.740 align:start position:0% ether channel is specifically covered 02:23:55.740 --> 02:23:56.870 align:start position:0% ether channel is specifically covered but<02:23:55.920> we<02:23:56.160> do 02:23:56.870 --> 02:23:56.880 align:start position:0% but we do 02:23:56.880 --> 02:23:59.510 align:start position:0% but we do um<02:23:57.000> there's<02:23:57.840> a<02:23:58.020> part<02:23:58.200> of<02:23:58.319> the<02:23:58.439> syllabus<02:23:58.859> that 02:23:59.510 --> 02:23:59.520 align:start position:0% um there's a part of the syllabus that 02:23:59.520 --> 02:24:02.389 align:start position:0% um there's a part of the syllabus that covers<02:24:00.300> um<02:24:00.380> increase<02:24:01.380> in<02:24:01.620> Europe<02:24:01.859> time<02:24:02.220> I 02:24:02.389 --> 02:24:02.399 align:start position:0% covers um increase in Europe time I 02:24:02.399 --> 02:24:04.010 align:start position:0% covers um increase in Europe time I can't<02:24:02.520> remember<02:24:02.700> what<02:24:02.880> it's<02:24:03.060> called<02:24:03.240> now 02:24:04.010 --> 02:24:04.020 align:start position:0% can't remember what it's called now 02:24:04.020 --> 02:24:06.050 align:start position:0% can't remember what it's called now let's<02:24:04.500> say<02:24:04.680> there's<02:24:04.859> redundancy<02:24:05.460> we<02:24:05.700> do<02:24:05.819> talk 02:24:06.050 --> 02:24:06.060 align:start position:0% let's say there's redundancy we do talk 02:24:06.060 --> 02:24:07.370 align:start position:0% let's say there's redundancy we do talk about<02:24:06.240> later 02:24:07.370 --> 02:24:07.380 align:start position:0% about later 02:24:07.380 --> 02:24:09.410 align:start position:0% about later so<02:24:07.920> uh<02:24:08.100> it's<02:24:08.340> a<02:24:08.520> non-routable<02:24:09.120> network 02:24:09.410 --> 02:24:09.420 align:start position:0% so uh it's a non-routable network 02:24:09.420 --> 02:24:12.050 align:start position:0% so uh it's a non-routable network protocol<02:24:10.020> so<02:24:10.439> it<02:24:10.859> won't<02:24:11.040> go 02:24:12.050 --> 02:24:12.060 align:start position:0% protocol so it won't go 02:24:12.060 --> 02:24:14.570 align:start position:0% protocol so it won't go whatever<02:24:12.899> your<02:24:13.260> connection<02:24:13.439> is<02:24:13.859> it<02:24:14.399> wouldn't 02:24:14.570 --> 02:24:14.580 align:start position:0% whatever your connection is it wouldn't 02:24:14.580 --> 02:24:15.710 align:start position:0% whatever your connection is it wouldn't be 02:24:15.710 --> 02:24:15.720 align:start position:0% be 02:24:15.720 --> 02:24:18.290 align:start position:0% be carried<02:24:16.319> out<02:24:16.439> here<02:24:16.800> to<02:24:17.580> um 02:24:18.290 --> 02:24:18.300 align:start position:0% carried out here to um 02:24:18.300 --> 02:24:20.929 align:start position:0% carried out here to um to<02:24:18.780> the<02:24:18.899> internet 02:24:20.929 --> 02:24:20.939 align:start position:0% to the internet 02:24:20.939 --> 02:24:23.330 align:start position:0% to the internet it<02:24:21.300> wouldn't<02:24:21.479> work<02:24:21.960> it'd<02:24:22.680> be<02:24:22.740> converted 02:24:23.330 --> 02:24:23.340 align:start position:0% it wouldn't work it'd be converted 02:24:23.340 --> 02:24:25.730 align:start position:0% it wouldn't work it'd be converted something<02:24:24.000> would<02:24:24.300> be<02:24:24.479> converted<02:24:24.840> to<02:24:24.960> bgp<02:24:25.560> or 02:24:25.730 --> 02:24:25.740 align:start position:0% something would be converted to bgp or 02:24:25.740 --> 02:24:28.670 align:start position:0% something would be converted to bgp or whatever<02:24:25.859> you're<02:24:26.100> using<02:24:26.460> out<02:24:26.580> here 02:24:28.670 --> 02:24:28.680 align:start position:0% whatever you're using out here 02:24:28.680 --> 02:24:30.530 align:start position:0% whatever you're using out here differs<02:24:29.160> from<02:24:29.340> Isco<02:24:29.700> Z<02:24:29.939> which<02:24:30.180> runs<02:24:30.420> over 02:24:30.530 --> 02:24:30.540 align:start position:0% differs from Isco Z which runs over 02:24:30.540 --> 02:24:32.809 align:start position:0% differs from Isco Z which runs over tcpip 02:24:32.809 --> 02:24:32.819 align:start position:0% tcpip 02:24:32.819 --> 02:24:34.730 align:start position:0% tcpip okay<02:24:33.120> this<02:24:33.420> is<02:24:33.540> non-routable<02:24:34.080> so<02:24:34.319> that<02:24:34.500> very 02:24:34.730 --> 02:24:34.740 align:start position:0% okay this is non-routable so that very 02:24:34.740 --> 02:24:35.870 align:start position:0% okay this is non-routable so that very much<02:24:34.859> whether<02:24:35.040> it<02:24:35.280> would<02:24:35.399> be<02:24:35.520> working<02:24:35.640> over 02:24:35.870 --> 02:24:35.880 align:start position:0% much whether it would be working over 02:24:35.880 --> 02:24:39.230 align:start position:0% much whether it would be working over tcpip<02:24:36.800> and<02:24:37.800> then<02:24:37.920> just<02:24:38.280> to<02:24:38.460> tick<02:24:38.760> the<02:24:38.939> Box 02:24:39.230 --> 02:24:39.240 align:start position:0% tcpip and then just to tick the Box 02:24:39.240 --> 02:24:42.590 align:start position:0% tcpip and then just to tick the Box Infinity<02:24:39.720> band<02:24:40.140> it's<02:24:40.439> added<02:24:40.740> in<02:24:40.859> the<02:24:40.979> syllabus 02:24:42.590 --> 02:24:42.600 align:start position:0% Infinity band it's added in the syllabus 02:24:42.600 --> 02:24:44.750 align:start position:0% Infinity band it's added in the syllabus um there's<02:24:42.899> a<02:24:43.140> diagram<02:24:43.680> here<02:24:43.979> I<02:24:44.220> got<02:24:44.399> from 02:24:44.750 --> 02:24:44.760 align:start position:0% um there's a diagram here I got from 02:24:44.760 --> 02:24:48.650 align:start position:0% um there's a diagram here I got from melanox<02:24:45.660> whoever<02:24:46.080> they<02:24:46.319> are<02:24:46.500> just<02:24:47.100> you<02:24:47.399> could 02:24:48.650 --> 02:24:48.660 align:start position:0% melanox whoever they are just you could 02:24:48.660 --> 02:24:52.309 align:start position:0% melanox whoever they are just you could um<02:24:48.859> see<02:24:49.859> a<02:24:50.040> topology<02:24:50.520> of<02:24:50.760> it<02:24:50.939> working<02:24:51.120> used<02:24:52.080> in 02:24:52.309 --> 02:24:52.319 align:start position:0% um see a topology of it working used in 02:24:52.319 --> 02:24:54.290 align:start position:0% um see a topology of it working used in high<02:24:52.500> performance<02:24:52.979> Computing<02:24:53.580> just<02:24:54.000> think<02:24:54.180> of 02:24:54.290 --> 02:24:54.300 align:start position:0% high performance Computing just think of 02:24:54.300 --> 02:24:56.809 align:start position:0% high performance Computing just think of exam<02:24:54.660> questions<02:24:54.899> basically<02:24:55.620> why<02:24:56.280> is<02:24:56.460> it<02:24:56.580> used 02:24:56.809 --> 02:24:56.819 align:start position:0% exam questions basically why is it used 02:24:56.819 --> 02:25:00.230 align:start position:0% exam questions basically why is it used it's<02:24:57.359> high<02:24:57.600> performance<02:24:58.020> low<02:24:58.319> latency<02:24:58.800> so<02:24:59.760> if 02:25:00.230 --> 02:25:00.240 align:start position:0% it's high performance low latency so if 02:25:00.240 --> 02:25:02.030 align:start position:0% it's high performance low latency so if it<02:25:00.420> if<02:25:00.780> it<02:25:00.899> meets<02:25:01.200> your<02:25:01.260> requirements<02:25:01.800> you'd 02:25:02.030 --> 02:25:02.040 align:start position:0% it if it meets your requirements you'd 02:25:02.040 --> 02:25:03.830 align:start position:0% it if it meets your requirements you'd consider<02:25:02.399> using<02:25:02.819> it 02:25:03.830 --> 02:25:03.840 align:start position:0% consider using it 02:25:03.840 --> 02:25:05.510 align:start position:0% consider using it uh<02:25:04.439> direct<02:25:04.680> or<02:25:04.979> switched<02:25:05.340> internet 02:25:05.510 --> 02:25:05.520 align:start position:0% uh direct or switched internet 02:25:05.520 --> 02:25:08.510 align:start position:0% uh direct or switched internet connection<02:25:05.939> between<02:25:06.479> servers<02:25:07.260> or<02:25:07.680> storage<02:25:08.040> so 02:25:08.510 --> 02:25:08.520 align:start position:0% connection between servers or storage so 02:25:08.520 --> 02:25:10.370 align:start position:0% connection between servers or storage so it<02:25:08.640> can<02:25:08.760> be<02:25:08.880> server<02:25:09.180> to<02:25:09.359> serve<02:25:09.660> our<02:25:09.840> server<02:25:10.200> to 02:25:10.370 --> 02:25:10.380 align:start position:0% it can be server to serve our server to 02:25:10.380 --> 02:25:12.050 align:start position:0% it can be server to serve our server to storage 02:25:12.050 --> 02:25:12.060 align:start position:0% storage 02:25:12.060 --> 02:25:14.030 align:start position:0% storage all<02:25:12.479> right<02:25:12.600> so<02:25:12.780> we<02:25:12.960> covered<02:25:13.319> a<02:25:13.560> lot<02:25:13.740> of<02:25:13.920> ground 02:25:14.030 --> 02:25:14.040 align:start position:0% all right so we covered a lot of ground 02:25:14.040 --> 02:25:16.730 align:start position:0% all right so we covered a lot of ground but<02:25:14.340> we're<02:25:14.520> just<02:25:14.760> topping<02:25:15.300> up<02:25:15.420> on<02:25:15.780> what<02:25:16.080> we<02:25:16.380> uh 02:25:16.730 --> 02:25:16.740 align:start position:0% but we're just topping up on what we uh 02:25:16.740 --> 02:25:18.650 align:start position:0% but we're just topping up on what we uh already<02:25:16.979> learned<02:25:17.399> earlier<02:25:17.700> you<02:25:18.240> learn<02:25:18.479> about 02:25:18.650 --> 02:25:18.660 align:start position:0% already learned earlier you learn about 02:25:18.660 --> 02:25:21.830 align:start position:0% already learned earlier you learn about some<02:25:18.840> copper<02:25:19.140> connector<02:25:19.560> types<02:25:19.920> transceivers 02:25:21.830 --> 02:25:21.840 align:start position:0% some copper connector types transceivers 02:25:21.840 --> 02:25:25.670 align:start position:0% some copper connector types transceivers so<02:25:22.620> it'll<02:25:22.859> convert<02:25:23.460> one<02:25:24.060> type<02:25:24.420> of<02:25:24.660> another<02:25:24.840> one 02:25:25.670 --> 02:25:25.680 align:start position:0% so it'll convert one type of another one 02:25:25.680 --> 02:25:27.830 align:start position:0% so it'll convert one type of another one type<02:25:25.859> of<02:25:26.040> connection<02:25:26.160> to<02:25:26.460> another<02:25:26.640> we<02:25:27.540> talked 02:25:27.830 --> 02:25:27.840 align:start position:0% type of connection to another we talked 02:25:27.840 --> 02:25:33.710 align:start position:0% type of connection to another we talked about<02:25:27.960> the<02:25:28.380> the<02:25:28.680> DB<02:25:29.520> oops<02:25:30.180> the<02:25:30.359> DB<02:25:31.280> M9<02:25:32.600> uh<02:25:33.600> I 02:25:33.710 --> 02:25:33.720 align:start position:0% about the the DB oops the DB M9 uh I 02:25:33.720 --> 02:25:35.389 align:start position:0% about the the DB oops the DB M9 uh I think<02:25:33.840> the<02:25:33.960> other<02:25:34.080> one<02:25:34.140> was<02:25:34.319> 25<02:25:34.740> the<02:25:35.220> D 02:25:35.389 --> 02:25:35.399 align:start position:0% think the other one was 25 the D 02:25:35.399 --> 02:25:37.610 align:start position:0% think the other one was 25 the D connector<02:25:36.000> and<02:25:36.540> basically<02:25:36.899> the<02:25:37.080> shape<02:25:37.380> is 02:25:37.610 --> 02:25:37.620 align:start position:0% connector and basically the shape is 02:25:37.620 --> 02:25:38.570 align:start position:0% connector and basically the shape is there 02:25:38.570 --> 02:25:38.580 align:start position:0% there 02:25:38.580 --> 02:25:41.030 align:start position:0% there hopefully<02:25:39.540> so<02:25:39.899> nobody<02:25:40.260> plugs<02:25:40.620> things<02:25:40.740> in<02:25:40.920> the 02:25:41.030 --> 02:25:41.040 align:start position:0% hopefully so nobody plugs things in the 02:25:41.040 --> 02:25:42.950 align:start position:0% hopefully so nobody plugs things in the wrong<02:25:41.220> way<02:25:41.340> that's<02:25:41.580> any<02:25:41.760> reason 02:25:42.950 --> 02:25:42.960 align:start position:0% wrong way that's any reason 02:25:42.960 --> 02:25:45.830 align:start position:0% wrong way that's any reason uh<02:25:43.439> termination<02:25:43.979> points<02:25:44.640> copper<02:25:45.600> cable 02:25:45.830 --> 02:25:45.840 align:start position:0% uh termination points copper cable 02:25:45.840 --> 02:25:48.830 align:start position:0% uh termination points copper cable standards<02:25:46.620> which<02:25:47.340> is<02:25:47.460> the<02:25:47.880> F<02:25:48.240> standard<02:25:48.660> I 02:25:48.830 --> 02:25:48.840 align:start position:0% standards which is the F standard I 02:25:48.840 --> 02:25:53.389 align:start position:0% standards which is the F standard I think<02:25:48.960> we<02:25:49.200> talked<02:25:49.439> about<02:25:49.560> which<02:25:49.979> isn't<02:25:50.399> fiber 02:25:53.389 --> 02:25:53.399 align:start position:0% 02:25:53.399 --> 02:25:56.450 align:start position:0% it<02:25:53.640> could<02:25:53.760> be<02:25:53.939> fiber<02:25:54.859> fibre<02:25:55.859> depending<02:25:56.399> on 02:25:56.450 --> 02:25:56.460 align:start position:0% it could be fiber fibre depending on 02:25:56.460 --> 02:25:57.650 align:start position:0% it could be fiber fibre depending on where<02:25:56.700> you<02:25:56.819> are 02:25:57.650 --> 02:25:57.660 align:start position:0% where you are 02:25:57.660 --> 02:25:59.330 align:start position:0% where you are and<02:25:57.960> then<02:25:58.140> the<02:25:58.319> network<02:25:58.439> storage<02:25:58.800> connection 02:25:59.330 --> 02:25:59.340 align:start position:0% and then the network storage connection 02:25:59.340 --> 02:26:00.710 align:start position:0% and then the network storage connection type 02:26:00.710 --> 02:26:00.720 align:start position:0% type 02:26:00.720 --> 02:26:02.690 align:start position:0% type all<02:26:01.080> right<02:26:01.260> so<02:26:01.439> that's<02:26:01.620> all<02:26:01.859> for<02:26:02.100> now<02:26:02.280> I'll 02:26:02.690 --> 02:26:02.700 align:start position:0% all right so that's all for now I'll 02:26:02.700 --> 02:26:03.830 align:start position:0% all right so that's all for now I'll look<02:26:02.939> forward<02:26:03.060> to<02:26:03.240> seeing<02:26:03.479> you<02:26:03.540> on<02:26:03.660> the<02:26:03.780> next 02:26:03.830 --> 02:26:03.840 align:start position:0% look forward to seeing you on the next 02:26:03.840 --> 02:26:09.280 align:start position:0% look forward to seeing you on the next presentation 02:26:09.280 --> 02:26:09.290 align:start position:0% 02:26:09.290 --> 02:26:17.630 align:start position:0% [Music] 02:26:17.630 --> 02:26:17.640 align:start position:0% [Music] 02:26:17.640 --> 02:26:29.270 align:start position:0% [Music] foreign 02:26:29.270 --> 02:26:29.280 align:start position:0% 02:26:29.280 --> 02:26:32.570 align:start position:0% Network<02:26:30.000> hardware<02:26:30.359> and<02:26:30.720> media<02:26:31.580> unbounded 02:26:32.570 --> 02:26:32.580 align:start position:0% Network hardware and media unbounded 02:26:32.580 --> 02:26:34.070 align:start position:0% Network hardware and media unbounded Network<02:26:32.880> media 02:26:34.070 --> 02:26:34.080 align:start position:0% Network media 02:26:34.080 --> 02:26:36.650 align:start position:0% Network media as<02:26:34.439> we<02:26:34.620> just<02:26:34.740> discussed<02:26:35.100> bounded<02:26:35.939> media<02:26:36.300> is 02:26:36.650 --> 02:26:36.660 align:start position:0% as we just discussed bounded media is 02:26:36.660 --> 02:26:38.929 align:start position:0% as we just discussed bounded media is that<02:26:36.899> media<02:26:37.380> error<02:26:37.620> cabling<02:26:37.979> that<02:26:38.280> is<02:26:38.460> bounded 02:26:38.929 --> 02:26:38.939 align:start position:0% that media error cabling that is bounded 02:26:38.939 --> 02:26:42.290 align:start position:0% that media error cabling that is bounded in<02:26:39.479> the<02:26:40.080> limits<02:26:40.500> of<02:26:40.920> a<02:26:41.160> cable<02:26:41.399> something<02:26:42.120> you 02:26:42.290 --> 02:26:42.300 align:start position:0% in the limits of a cable something you 02:26:42.300 --> 02:26:45.469 align:start position:0% in the limits of a cable something you can<02:26:42.479> hold<02:26:42.740> unbounded<02:26:43.740> media<02:26:44.160> as<02:26:44.760> the<02:26:45.240> image 02:26:45.469 --> 02:26:45.479 align:start position:0% can hold unbounded media as the image 02:26:45.479 --> 02:26:47.510 align:start position:0% can hold unbounded media as the image here<02:26:45.660> describes<02:26:46.260> and<02:26:46.740> the<02:26:46.920> image<02:26:47.160> right<02:26:47.340> here 02:26:47.510 --> 02:26:47.520 align:start position:0% here describes and the image right here 02:26:47.520 --> 02:26:50.750 align:start position:0% here describes and the image right here describes<02:26:47.939> is<02:26:48.500> uh<02:26:49.500> Wireless<02:26:49.979> in<02:26:50.399> nature 02:26:50.750 --> 02:26:50.760 align:start position:0% describes is uh Wireless in nature 02:26:50.760 --> 02:26:52.730 align:start position:0% describes is uh Wireless in nature meaning<02:26:51.000> that<02:26:51.300> there<02:26:51.540> isn't<02:26:51.899> any<02:26:52.380> sort<02:26:52.620> of 02:26:52.730 --> 02:26:52.740 align:start position:0% meaning that there isn't any sort of 02:26:52.740 --> 02:26:55.190 align:start position:0% meaning that there isn't any sort of chord<02:26:53.160> that<02:26:53.580> you<02:26:53.700> have<02:26:53.819> to<02:26:54.060> rely<02:26:54.359> on<02:26:54.540> and 02:26:55.190 --> 02:26:55.200 align:start position:0% chord that you have to rely on and 02:26:55.200 --> 02:26:57.349 align:start position:0% chord that you have to rely on and therefore<02:26:55.560> it<02:26:56.220> allows<02:26:56.520> for<02:26:56.939> certain 02:26:57.349 --> 02:26:57.359 align:start position:0% therefore it allows for certain 02:26:57.359 --> 02:26:58.910 align:start position:0% therefore it allows for certain advantages<02:26:57.960> and<02:26:58.500> also<02:26:58.680> certain 02:26:58.910 --> 02:26:58.920 align:start position:0% advantages and also certain 02:26:58.920 --> 02:27:00.830 align:start position:0% advantages and also certain disadvantages<02:26:59.580> so<02:27:00.180> we're<02:27:00.300> going<02:27:00.420> to<02:27:00.540> look<02:27:00.660> at 02:27:00.830 --> 02:27:00.840 align:start position:0% disadvantages so we're going to look at 02:27:00.840 --> 02:27:03.309 align:start position:0% disadvantages so we're going to look at the<02:27:01.080> hardware<02:27:01.260> and<02:27:01.680> unbounded<02:27:02.280> media<02:27:02.700> types 02:27:03.309 --> 02:27:03.319 align:start position:0% the hardware and unbounded media types 02:27:03.319 --> 02:27:06.230 align:start position:0% the hardware and unbounded media types involved<02:27:04.319> in<02:27:04.439> these<02:27:04.680> sort<02:27:04.800> of<02:27:04.920> connections 02:27:06.230 --> 02:27:06.240 align:start position:0% involved in these sort of connections 02:27:06.240 --> 02:27:09.469 align:start position:0% involved in these sort of connections so<02:27:07.140> are<02:27:07.380> the<02:27:07.500> objectives<02:27:07.979> for<02:27:08.520> this<02:27:09.060> module 02:27:09.469 --> 02:27:09.479 align:start position:0% so are the objectives for this module 02:27:09.479 --> 02:27:12.410 align:start position:0% so are the objectives for this module are<02:27:10.380> to<02:27:10.680> Define<02:27:10.880> unbounded<02:27:11.880> as<02:27:12.060> opposed<02:27:12.359> to 02:27:12.410 --> 02:27:12.420 align:start position:0% are to Define unbounded as opposed to 02:27:12.420 --> 02:27:15.050 align:start position:0% are to Define unbounded as opposed to bounded<02:27:12.960> Network<02:27:13.319> media<02:27:14.280> we're<02:27:14.700> also<02:27:14.939> going 02:27:15.050 --> 02:27:15.060 align:start position:0% bounded Network media we're also going 02:27:15.060 --> 02:27:16.610 align:start position:0% bounded Network media we're also going to<02:27:15.180> define<02:27:15.300> the<02:27:15.780> difference<02:27:15.899> in<02:27:16.140> radio 02:27:16.610 --> 02:27:16.620 align:start position:0% to define the difference in radio 02:27:16.620 --> 02:27:19.969 align:start position:0% to define the difference in radio networking<02:27:17.399> and<02:27:17.880> broadcast<02:27:18.300> radio 02:27:19.969 --> 02:27:19.979 align:start position:0% networking and broadcast radio 02:27:19.979 --> 02:27:23.090 align:start position:0% networking and broadcast radio look<02:27:20.880> at<02:27:21.060> something<02:27:21.240> called<02:27:21.600> spread<02:27:22.439> Spectrum 02:27:23.090 --> 02:27:23.100 align:start position:0% look at something called spread Spectrum 02:27:23.100 --> 02:27:27.230 align:start position:0% look at something called spread Spectrum which<02:27:23.819> was<02:27:24.180> created<02:27:24.899> in<02:27:25.200> order<02:27:25.380> to<02:27:26.240> help 02:27:27.230 --> 02:27:27.240 align:start position:0% which was created in order to help 02:27:27.240 --> 02:27:29.630 align:start position:0% which was created in order to help Wireless<02:27:27.840> Technologies<02:27:28.620> work<02:27:29.040> more 02:27:29.630 --> 02:27:29.640 align:start position:0% Wireless Technologies work more 02:27:29.640 --> 02:27:31.730 align:start position:0% Wireless Technologies work more efficiently<02:27:30.000> and<02:27:30.180> effectively<02:27:30.720> we're<02:27:31.500> also 02:27:31.730 --> 02:27:31.740 align:start position:0% efficiently and effectively we're also 02:27:31.740 --> 02:27:33.650 align:start position:0% efficiently and effectively we're also going<02:27:31.800> to<02:27:31.859> look<02:27:31.979> at<02:27:32.100> IR<02:27:32.460> or<02:27:32.880> infrared<02:27:33.479> or 02:27:33.650 --> 02:27:33.660 align:start position:0% going to look at IR or infrared or 02:27:33.660 --> 02:27:35.570 align:start position:0% going to look at IR or infrared or infrared<02:27:34.140> connections<02:27:34.859> Bluetooth 02:27:35.570 --> 02:27:35.580 align:start position:0% infrared connections Bluetooth 02:27:35.580 --> 02:27:38.450 align:start position:0% infrared connections Bluetooth connections<02:27:36.420> and<02:27:37.080> microwave<02:27:37.740> connections 02:27:38.450 --> 02:27:38.460 align:start position:0% connections and microwave connections 02:27:38.460 --> 02:27:39.950 align:start position:0% connections and microwave connections all<02:27:38.819> of<02:27:38.939> these<02:27:39.180> different<02:27:39.420> types<02:27:39.840> of 02:27:39.950 --> 02:27:39.960 align:start position:0% all of these different types of 02:27:39.960 --> 02:27:42.530 align:start position:0% all of these different types of unbounded<02:27:40.740> media<02:27:41.160> and<02:27:41.460> devices 02:27:42.530 --> 02:27:42.540 align:start position:0% unbounded media and devices 02:27:42.540 --> 02:27:43.550 align:start position:0% unbounded media and devices and<02:27:42.960> then<02:27:43.080> we're<02:27:43.200> going<02:27:43.319> to<02:27:43.319> look<02:27:43.439> at 02:27:43.550 --> 02:27:43.560 align:start position:0% and then we're going to look at 02:27:43.560 --> 02:27:44.929 align:start position:0% and then we're going to look at something<02:27:43.740> that<02:27:44.040> most<02:27:44.280> of<02:27:44.399> you<02:27:44.520> are<02:27:44.700> probably 02:27:44.929 --> 02:27:44.939 align:start position:0% something that most of you are probably 02:27:44.939 --> 02:27:46.849 align:start position:0% something that most of you are probably more<02:27:45.300> familiar<02:27:45.660> with<02:27:45.840> a<02:27:46.140> wireless<02:27:46.380> access 02:27:46.849 --> 02:27:46.859 align:start position:0% more familiar with a wireless access 02:27:46.859 --> 02:27:50.450 align:start position:0% more familiar with a wireless access point<02:27:47.359> also<02:27:48.359> a<02:27:48.720> WAP 02:27:50.450 --> 02:27:50.460 align:start position:0% point also a WAP 02:27:50.460 --> 02:27:51.469 align:start position:0% point also a WAP then<02:27:50.760> we're<02:27:50.880> going<02:27:51.000> to<02:27:51.060> describe<02:27:51.359> the 02:27:51.469 --> 02:27:51.479 align:start position:0% then we're going to describe the 02:27:51.479 --> 02:27:54.830 align:start position:0% then we're going to describe the characteristics<02:27:52.200> of<02:27:52.620> an<02:27:52.859> SSID<02:27:53.399> which<02:27:54.359> many<02:27:54.600> of 02:27:54.830 --> 02:27:54.840 align:start position:0% characteristics of an SSID which many of 02:27:54.840 --> 02:27:57.290 align:start position:0% characteristics of an SSID which many of you<02:27:55.020> uh<02:27:55.800> might<02:27:56.100> know<02:27:56.220> as<02:27:56.460> the<02:27:56.760> name<02:27:56.939> of<02:27:57.180> a 02:27:57.290 --> 02:27:57.300 align:start position:0% you uh might know as the name of a 02:27:57.300 --> 02:27:59.030 align:start position:0% you uh might know as the name of a network<02:27:57.540> also<02:27:58.020> called<02:27:58.200> the<02:27:58.439> service<02:27:58.740> set 02:27:59.030 --> 02:27:59.040 align:start position:0% network also called the service set 02:27:59.040 --> 02:28:00.590 align:start position:0% network also called the service set identifier 02:28:00.590 --> 02:28:00.600 align:start position:0% identifier 02:28:00.600 --> 02:28:03.050 align:start position:0% identifier and<02:28:01.020> finally<02:28:01.200> we're<02:28:01.439> going<02:28:01.560> to<02:28:01.620> look<02:28:01.800> at<02:28:01.979> the 02:28:03.050 --> 02:28:03.060 align:start position:0% and finally we're going to look at the 02:28:03.060 --> 02:28:04.610 align:start position:0% and finally we're going to look at the basic<02:28:03.540> uh 02:28:04.610 --> 02:28:04.620 align:start position:0% basic uh 02:28:04.620 --> 02:28:06.889 align:start position:0% basic uh ways<02:28:05.460> of<02:28:05.640> properly<02:28:06.000> installing<02:28:06.540> an<02:28:06.720> access 02:28:06.889 --> 02:28:06.899 align:start position:0% ways of properly installing an access 02:28:06.899 --> 02:28:09.230 align:start position:0% ways of properly installing an access point<02:28:07.260> and<02:28:07.979> by<02:28:08.280> properly<02:28:08.640> installing<02:28:09.060> an 02:28:09.230 --> 02:28:09.240 align:start position:0% point and by properly installing an 02:28:09.240 --> 02:28:11.690 align:start position:0% point and by properly installing an access<02:28:09.420> point<02:28:09.840> of<02:28:10.740> course<02:28:10.859> we're<02:28:11.220> referring 02:28:11.690 --> 02:28:11.700 align:start position:0% access point of course we're referring 02:28:11.700 --> 02:28:14.990 align:start position:0% access point of course we're referring to<02:28:11.939> the<02:28:12.240> network<02:28:12.540> plus<02:28:13.140> methodology<02:28:14.000> of 02:28:14.990 --> 02:28:15.000 align:start position:0% to the network plus methodology of 02:28:15.000 --> 02:28:16.670 align:start position:0% to the network plus methodology of installing<02:28:15.420> an<02:28:15.600> access<02:28:15.720> point 02:28:16.670 --> 02:28:16.680 align:start position:0% installing an access point 02:28:16.680 --> 02:28:19.130 align:start position:0% installing an access point all<02:28:17.160> right 02:28:19.130 --> 02:28:19.140 align:start position:0% all right 02:28:19.140 --> 02:28:22.190 align:start position:0% all right so<02:28:19.800> unbounded<02:28:20.460> Network<02:28:20.700> media<02:28:21.300> is<02:28:21.960> any 02:28:22.190 --> 02:28:22.200 align:start position:0% so unbounded Network media is any 02:28:22.200 --> 02:28:24.950 align:start position:0% so unbounded Network media is any network<02:28:22.439> media<02:28:22.979> that's<02:28:23.220> not<02:28:23.640> bound<02:28:24.180> by<02:28:24.720> a 02:28:24.950 --> 02:28:24.960 align:start position:0% network media that's not bound by a 02:28:24.960 --> 02:28:27.170 align:start position:0% network media that's not bound by a physical<02:28:25.140> connection<02:28:25.560> such<02:28:26.160> as<02:28:26.340> copper<02:28:26.939> or 02:28:27.170 --> 02:28:27.180 align:start position:0% physical connection such as copper or 02:28:27.180 --> 02:28:30.410 align:start position:0% physical connection such as copper or wire<02:28:27.359> a<02:28:28.080> fiber<02:28:28.560> that<02:28:28.800> we've<02:28:29.040> just<02:28:29.220> seen 02:28:30.410 --> 02:28:30.420 align:start position:0% wire a fiber that we've just seen 02:28:30.420 --> 02:28:33.290 align:start position:0% wire a fiber that we've just seen the<02:28:31.140> unbounded<02:28:31.800> simply<02:28:32.220> means<02:28:32.640> it's<02:28:32.939> wireless 02:28:33.290 --> 02:28:33.300 align:start position:0% the unbounded simply means it's wireless 02:28:33.300 --> 02:28:35.870 align:start position:0% the unbounded simply means it's wireless or<02:28:34.080> it's<02:28:34.260> using<02:28:34.740> a<02:28:35.040> sort<02:28:35.220> of<02:28:35.399> Wireless 02:28:35.870 --> 02:28:35.880 align:start position:0% or it's using a sort of Wireless 02:28:35.880 --> 02:28:39.830 align:start position:0% or it's using a sort of Wireless technology<02:28:36.920> Now<02:28:37.920> using<02:28:38.399> unbounded<02:28:39.060> media<02:28:39.479> has 02:28:39.830 --> 02:28:39.840 align:start position:0% technology Now using unbounded media has 02:28:39.840 --> 02:28:42.710 align:start position:0% technology Now using unbounded media has some<02:28:40.260> specific<02:28:40.979> advantages<02:28:41.580> such<02:28:42.060> as<02:28:42.180> it's 02:28:42.710 --> 02:28:42.720 align:start position:0% some specific advantages such as it's 02:28:42.720 --> 02:28:45.110 align:start position:0% some specific advantages such as it's easier<02:28:43.020> to<02:28:43.260> install<02:28:43.500> and<02:28:43.979> manage<02:28:44.399> over<02:28:44.760> its 02:28:45.110 --> 02:28:45.120 align:start position:0% easier to install and manage over its 02:28:45.120 --> 02:28:46.670 align:start position:0% easier to install and manage over its bounded<02:28:45.479> counterparts<02:28:46.080> because<02:28:46.260> you<02:28:46.560> don't 02:28:46.670 --> 02:28:46.680 align:start position:0% bounded counterparts because you don't 02:28:46.680 --> 02:28:49.550 align:start position:0% bounded counterparts because you don't have<02:28:46.920> as<02:28:47.160> much<02:28:47.340> stuff<02:28:48.120> to<02:28:48.479> deal<02:28:48.660> with<02:28:48.840> in<02:28:49.439> the 02:28:49.550 --> 02:28:49.560 align:start position:0% have as much stuff to deal with in the 02:28:49.560 --> 02:28:51.530 align:start position:0% have as much stuff to deal with in the same<02:28:49.680> regard<02:28:49.979> however<02:28:50.460> unbounded<02:28:51.300> Network 02:28:51.530 --> 02:28:51.540 align:start position:0% same regard however unbounded Network 02:28:51.540 --> 02:28:53.690 align:start position:0% same regard however unbounded Network media<02:28:52.080> has<02:28:52.680> the<02:28:52.859> potential<02:28:53.100> to<02:28:53.280> be<02:28:53.399> less 02:28:53.690 --> 02:28:53.700 align:start position:0% media has the potential to be less 02:28:53.700 --> 02:28:57.590 align:start position:0% media has the potential to be less secure<02:28:54.359> than<02:28:55.140> bounded<02:28:55.680> and<02:28:56.640> actually<02:28:56.819> a<02:28:57.420> lot 02:28:57.590 --> 02:28:57.600 align:start position:0% secure than bounded and actually a lot 02:28:57.600 --> 02:28:59.510 align:start position:0% secure than bounded and actually a lot of<02:28:57.720> folks<02:28:58.020> will<02:28:58.200> say<02:28:58.439> that<02:28:58.680> there<02:28:58.920> is<02:28:59.100> no<02:28:59.340> way 02:28:59.510 --> 02:28:59.520 align:start position:0% of folks will say that there is no way 02:28:59.520 --> 02:29:01.790 align:start position:0% of folks will say that there is no way to<02:28:59.760> have<02:28:59.939> a<02:29:00.300> secure<02:29:00.660> Wireless 02:29:01.790 --> 02:29:01.800 align:start position:0% to have a secure Wireless 02:29:01.800 --> 02:29:05.809 align:start position:0% to have a secure Wireless or<02:29:02.340> unbounded<02:29:03.000> network<02:29:03.359> because 02:29:05.809 --> 02:29:05.819 align:start position:0% or unbounded network because 02:29:05.819 --> 02:29:07.910 align:start position:0% or unbounded network because traffic<02:29:06.479> across<02:29:07.020> the<02:29:07.140> network<02:29:07.319> can<02:29:07.680> be 02:29:07.910 --> 02:29:07.920 align:start position:0% traffic across the network can be 02:29:07.920 --> 02:29:10.309 align:start position:0% traffic across the network can be intercepted<02:29:08.520> a<02:29:08.700> lot<02:29:08.819> easier<02:29:09.240> when<02:29:10.140> it's 02:29:10.309 --> 02:29:10.319 align:start position:0% intercepted a lot easier when it's 02:29:10.319 --> 02:29:11.990 align:start position:0% intercepted a lot easier when it's wireless<02:29:10.439> and<02:29:10.800> anyone<02:29:11.100> can<02:29:11.280> just<02:29:11.399> sort<02:29:11.580> of<02:29:11.700> tap 02:29:11.990 --> 02:29:12.000 align:start position:0% wireless and anyone can just sort of tap 02:29:12.000 --> 02:29:15.290 align:start position:0% wireless and anyone can just sort of tap in<02:29:12.260> in<02:29:13.260> radio<02:29:13.620> networking<02:29:14.399> data<02:29:15.180> is 02:29:15.290 --> 02:29:15.300 align:start position:0% in in radio networking data is 02:29:15.300 --> 02:29:19.969 align:start position:0% in in radio networking data is transmitted<02:29:16.020> as<02:29:16.740> RF<02:29:17.640> or<02:29:18.240> radio<02:29:18.600> frequency<02:29:19.380> so 02:29:19.969 --> 02:29:19.979 align:start position:0% transmitted as RF or radio frequency so 02:29:19.979 --> 02:29:22.510 align:start position:0% transmitted as RF or radio frequency so one<02:29:20.220> of<02:29:20.340> the<02:29:20.460> first<02:29:20.640> forms<02:29:21.120> of<02:29:21.240> communications 02:29:22.510 --> 02:29:22.520 align:start position:0% one of the first forms of communications 02:29:22.520 --> 02:29:26.929 align:start position:0% one of the first forms of communications this<02:29:23.520> these<02:29:23.939> signals<02:29:24.359> of<02:29:24.740> RF<02:29:25.740> waves<02:29:26.399> were 02:29:26.929 --> 02:29:26.939 align:start position:0% this these signals of RF waves were 02:29:26.939 --> 02:29:33.130 align:start position:0% this these signals of RF waves were transmitted<02:29:27.600> in<02:29:27.780> the<02:29:28.020> 10<02:29:28.260> kilohertz<02:29:28.979> to 02:29:33.130 --> 02:29:33.140 align:start position:0% 02:29:33.140 --> 02:29:37.030 align:start position:0% uh<02:29:34.140> one<02:29:34.380> gigahertz<02:29:34.920> range 02:29:37.030 --> 02:29:37.040 align:start position:0% uh one gigahertz range 02:29:37.040 --> 02:29:40.070 align:start position:0% uh one gigahertz range and<02:29:38.040> in<02:29:38.220> the<02:29:38.399> U.S<02:29:38.760> the<02:29:39.000> FCC<02:29:39.359> or<02:29:39.780> the<02:29:39.899> Federal 02:29:40.070 --> 02:29:40.080 align:start position:0% and in the U.S the FCC or the Federal 02:29:40.080 --> 02:29:42.410 align:start position:0% and in the U.S the FCC or the Federal Communications<02:29:40.800> Commission<02:29:41.460> regulates 02:29:42.410 --> 02:29:42.420 align:start position:0% Communications Commission regulates 02:29:42.420 --> 02:29:45.110 align:start position:0% Communications Commission regulates these<02:29:42.899> radio<02:29:43.020> Transmissions<02:29:43.859> this<02:29:44.819> kind<02:29:45.000> of 02:29:45.110 --> 02:29:45.120 align:start position:0% these radio Transmissions this kind of 02:29:45.120 --> 02:29:46.610 align:start position:0% these radio Transmissions this kind of networking<02:29:45.600> is<02:29:45.899> unfortunately<02:29:46.260> very 02:29:46.610 --> 02:29:46.620 align:start position:0% networking is unfortunately very 02:29:46.620 --> 02:29:50.210 align:start position:0% networking is unfortunately very susceptible<02:29:47.160> to<02:29:47.760> uh<02:29:48.420> Emi 02:29:50.210 --> 02:29:50.220 align:start position:0% susceptible to uh Emi 02:29:50.220 --> 02:29:52.370 align:start position:0% susceptible to uh Emi or<02:29:50.760> electromagnetic<02:29:51.660> interference<02:29:52.200> which 02:29:52.370 --> 02:29:52.380 align:start position:0% or electromagnetic interference which 02:29:52.380 --> 02:29:54.770 align:start position:0% or electromagnetic interference which we've<02:29:52.620> seen<02:29:52.920> previously<02:29:53.880> especially<02:29:54.479> from 02:29:54.770 --> 02:29:54.780 align:start position:0% we've seen previously especially from 02:29:54.780 --> 02:29:57.349 align:start position:0% we've seen previously especially from stuff<02:29:55.020> like<02:29:55.260> power<02:29:55.620> lines<02:29:56.359> metallic 02:29:57.349 --> 02:29:57.359 align:start position:0% stuff like power lines metallic 02:29:57.359 --> 02:30:00.050 align:start position:0% stuff like power lines metallic obstacles<02:29:57.960> even<02:29:58.520> atmospheric<02:29:59.520> conditions 02:30:00.050 --> 02:30:00.060 align:start position:0% obstacles even atmospheric conditions 02:30:00.060 --> 02:30:01.849 align:start position:0% obstacles even atmospheric conditions some<02:30:00.420> people<02:30:00.600> tell<02:30:00.840> me<02:30:00.960> that<02:30:01.260> they<02:30:01.560> lose 02:30:01.849 --> 02:30:01.859 align:start position:0% some people tell me that they lose 02:30:01.859 --> 02:30:05.150 align:start position:0% some people tell me that they lose connectivity<02:30:02.780> when<02:30:03.780> a<02:30:04.140> plane<02:30:04.439> flies<02:30:04.800> overhead 02:30:05.150 --> 02:30:05.160 align:start position:0% connectivity when a plane flies overhead 02:30:05.160 --> 02:30:08.690 align:start position:0% connectivity when a plane flies overhead a<02:30:06.000> radio<02:30:06.180> networking<02:30:06.780> can<02:30:07.020> also<02:30:07.319> be<02:30:07.680> very<02:30:08.100> long 02:30:08.690 --> 02:30:08.700 align:start position:0% a radio networking can also be very long 02:30:08.700 --> 02:30:11.030 align:start position:0% a radio networking can also be very long range<02:30:09.120> depending<02:30:09.660> on<02:30:09.899> the<02:30:10.439> method<02:30:10.740> of 02:30:11.030 --> 02:30:11.040 align:start position:0% range depending on the method of 02:30:11.040 --> 02:30:13.309 align:start position:0% range depending on the method of transmission<02:30:11.399> the<02:30:12.240> amount<02:30:12.479> of<02:30:12.660> power<02:30:12.840> behind 02:30:13.309 --> 02:30:13.319 align:start position:0% transmission the amount of power behind 02:30:13.319 --> 02:30:15.710 align:start position:0% transmission the amount of power behind the<02:30:13.500> signal<02:30:13.859> the<02:30:14.819> kind<02:30:14.939> of<02:30:15.060> antenna<02:30:15.540> being 02:30:15.710 --> 02:30:15.720 align:start position:0% the signal the kind of antenna being 02:30:15.720 --> 02:30:18.230 align:start position:0% the signal the kind of antenna being used<02:30:16.080> the<02:30:16.859> portion<02:30:17.280> of<02:30:17.580> the<02:30:17.819> frequency 02:30:18.230 --> 02:30:18.240 align:start position:0% used the portion of the frequency 02:30:18.240 --> 02:30:21.770 align:start position:0% used the portion of the frequency spectrum<02:30:18.960> which<02:30:19.800> is<02:30:19.979> located<02:30:20.340> in<02:30:20.819> here<02:30:21.060> that's 02:30:21.770 --> 02:30:21.780 align:start position:0% spectrum which is located in here that's 02:30:21.780 --> 02:30:24.950 align:start position:0% spectrum which is located in here that's being<02:30:22.080> used<02:30:22.319> now<02:30:23.040> with<02:30:23.280> broadcast<02:30:23.580> radio 02:30:24.950 --> 02:30:24.960 align:start position:0% being used now with broadcast radio 02:30:24.960 --> 02:30:27.050 align:start position:0% being used now with broadcast radio which<02:30:25.560> is<02:30:25.800> also<02:30:26.040> considered<02:30:26.520> a<02:30:26.939> broadcast 02:30:27.050 --> 02:30:27.060 align:start position:0% which is also considered a broadcast 02:30:27.060 --> 02:30:29.690 align:start position:0% which is also considered a broadcast network<02:30:27.780> the<02:30:28.560> signal<02:30:28.859> is<02:30:28.979> sent<02:30:29.160> out<02:30:29.280> in<02:30:29.460> all 02:30:29.690 --> 02:30:29.700 align:start position:0% network the signal is sent out in all 02:30:29.700 --> 02:30:31.790 align:start position:0% network the signal is sent out in all directions<02:30:29.880> and<02:30:30.420> utilizes<02:30:31.080> a<02:30:31.560> single 02:30:31.790 --> 02:30:31.800 align:start position:0% directions and utilizes a single 02:30:31.800 --> 02:30:34.130 align:start position:0% directions and utilizes a single frequency<02:30:32.220> for<02:30:32.640> transmission<02:30:32.939> so<02:30:33.840> there's 02:30:34.130 --> 02:30:34.140 align:start position:0% frequency for transmission so there's 02:30:34.140 --> 02:30:36.530 align:start position:0% frequency for transmission so there's low<02:30:34.859> power<02:30:35.100> transmission<02:30:35.580> for<02:30:36.180> shorter 02:30:36.530 --> 02:30:36.540 align:start position:0% low power transmission for shorter 02:30:36.540 --> 02:30:39.410 align:start position:0% low power transmission for shorter distances<02:30:37.020> is<02:30:37.319> more<02:30:37.560> common<02:30:37.740> and<02:30:38.640> is<02:30:38.880> easy<02:30:39.180> to 02:30:39.410 --> 02:30:39.420 align:start position:0% distances is more common and is easy to 02:30:39.420 --> 02:30:41.450 align:start position:0% distances is more common and is easy to install<02:30:39.540> but<02:30:40.260> there's<02:30:40.439> also 02:30:41.450 --> 02:30:41.460 align:start position:0% install but there's also 02:30:41.460 --> 02:30:44.270 align:start position:0% install but there's also high<02:30:42.000> power<02:30:42.180> Transmissions<02:30:42.960> which<02:30:43.560> are<02:30:43.859> used 02:30:44.270 --> 02:30:44.280 align:start position:0% high power Transmissions which are used 02:30:44.280 --> 02:30:45.770 align:start position:0% high power Transmissions which are used for<02:30:44.520> further<02:30:44.819> distances<02:30:45.240> as<02:30:45.479> you<02:30:45.660> would 02:30:45.770 --> 02:30:45.780 align:start position:0% for further distances as you would 02:30:45.780 --> 02:30:48.230 align:start position:0% for further distances as you would imagine<02:30:45.960> and<02:30:46.800> it's<02:30:46.979> difficult<02:30:47.460> typically<02:30:48.060> a 02:30:48.230 --> 02:30:48.240 align:start position:0% imagine and it's difficult typically a 02:30:48.240 --> 02:30:49.670 align:start position:0% imagine and it's difficult typically a little<02:30:48.359> more<02:30:48.540> difficult<02:30:48.840> to<02:30:49.140> install<02:30:49.260> because 02:30:49.670 --> 02:30:49.680 align:start position:0% little more difficult to install because 02:30:49.680 --> 02:30:52.190 align:start position:0% little more difficult to install because it<02:30:49.920> requires<02:30:50.399> really<02:30:51.300> specially<02:30:51.780> trained 02:30:52.190 --> 02:30:52.200 align:start position:0% it requires really specially trained 02:30:52.200 --> 02:30:54.050 align:start position:0% it requires really specially trained technicians<02:30:52.800> proper<02:30:53.460> installation<02:30:53.880> and 02:30:54.050 --> 02:30:54.060 align:start position:0% technicians proper installation and 02:30:54.060 --> 02:30:56.570 align:start position:0% technicians proper installation and maintenance<02:30:54.420> techniques<02:30:54.899> and<02:30:55.020> so<02:30:55.200> on<02:30:55.859> with 02:30:56.570 --> 02:30:56.580 align:start position:0% maintenance techniques and so on with 02:30:56.580 --> 02:30:59.450 align:start position:0% maintenance techniques and so on with radio<02:30:56.819> networking<02:30:57.600> line<02:30:57.840> of<02:30:58.080> sight<02:30:58.380> is<02:30:59.220> not 02:30:59.450 --> 02:30:59.460 align:start position:0% radio networking line of sight is not 02:30:59.460 --> 02:31:00.590 align:start position:0% radio networking line of sight is not necessary 02:31:00.590 --> 02:31:00.600 align:start position:0% necessary 02:31:00.600 --> 02:31:02.450 align:start position:0% necessary which<02:31:00.960> means<02:31:01.260> that<02:31:01.560> the 02:31:02.450 --> 02:31:02.460 align:start position:0% which means that the 02:31:02.460 --> 02:31:05.150 align:start position:0% which means that the uh<02:31:03.240> this<02:31:03.660> the<02:31:03.899> device<02:31:04.200> sending<02:31:04.740> the<02:31:04.800> signal<02:31:04.979> in 02:31:05.150 --> 02:31:05.160 align:start position:0% uh this the device sending the signal in 02:31:05.160 --> 02:31:06.530 align:start position:0% uh this the device sending the signal in the<02:31:05.280> device<02:31:05.340> receiving<02:31:05.880> the<02:31:06.060> signal<02:31:06.300> don't 02:31:06.530 --> 02:31:06.540 align:start position:0% the device receiving the signal don't 02:31:06.540 --> 02:31:08.630 align:start position:0% the device receiving the signal don't need<02:31:06.660> to<02:31:06.780> literally<02:31:07.260> be<02:31:07.800> able<02:31:07.979> to<02:31:08.100> see<02:31:08.399> one 02:31:08.630 --> 02:31:08.640 align:start position:0% need to literally be able to see one 02:31:08.640 --> 02:31:11.570 align:start position:0% need to literally be able to see one another<02:31:08.819> now<02:31:09.479> because<02:31:10.020> radio<02:31:10.439> networking<02:31:11.100> is 02:31:11.570 --> 02:31:11.580 align:start position:0% another now because radio networking is 02:31:11.580 --> 02:31:14.570 align:start position:0% another now because radio networking is sent<02:31:11.880> over<02:31:12.180> the<02:31:12.600> airwaves<02:31:13.260> uh<02:31:13.979> the<02:31:14.100> signal<02:31:14.399> can 02:31:14.570 --> 02:31:14.580 align:start position:0% sent over the airwaves uh the signal can 02:31:14.580 --> 02:31:16.849 align:start position:0% sent over the airwaves uh the signal can be<02:31:14.700> intercepted<02:31:15.359> really<02:31:15.780> easily<02:31:16.200> and<02:31:16.560> so<02:31:16.740> in 02:31:16.849 --> 02:31:16.859 align:start position:0% be intercepted really easily and so in 02:31:16.859 --> 02:31:19.309 align:start position:0% be intercepted really easily and so in order<02:31:17.040> to<02:31:17.399> utilize<02:31:18.240> the<02:31:18.540> technology<02:31:18.899> for 02:31:19.309 --> 02:31:19.319 align:start position:0% order to utilize the technology for 02:31:19.319 --> 02:31:21.070 align:start position:0% order to utilize the technology for day-to-day<02:31:19.920> transmission<02:31:20.280> of<02:31:20.760> information 02:31:21.070 --> 02:31:21.080 align:start position:0% day-to-day transmission of information 02:31:21.080 --> 02:31:23.330 align:start position:0% day-to-day transmission of information we<02:31:22.080> need<02:31:22.200> to<02:31:22.319> make<02:31:22.500> sure<02:31:22.620> that<02:31:22.859> it's<02:31:22.979> kept 02:31:23.330 --> 02:31:23.340 align:start position:0% we need to make sure that it's kept 02:31:23.340 --> 02:31:26.030 align:start position:0% we need to make sure that it's kept confidential<02:31:23.939> and<02:31:24.600> so<02:31:24.780> a<02:31:25.200> new<02:31:25.380> form<02:31:25.620> of<02:31:25.859> radio 02:31:26.030 --> 02:31:26.040 align:start position:0% confidential and so a new form of radio 02:31:26.040 --> 02:31:28.610 align:start position:0% confidential and so a new form of radio transmission<02:31:26.520> was<02:31:27.479> developed<02:31:28.020> this<02:31:28.500> is 02:31:28.610 --> 02:31:28.620 align:start position:0% transmission was developed this is 02:31:28.620 --> 02:31:31.490 align:start position:0% transmission was developed this is called<02:31:28.859> spread<02:31:29.819> Spectrum 02:31:31.490 --> 02:31:31.500 align:start position:0% called spread Spectrum 02:31:31.500 --> 02:31:33.889 align:start position:0% called spread Spectrum a<02:31:32.100> spread<02:31:32.460> Spectrum<02:31:32.939> was<02:31:33.180> introduced<02:31:33.600> to 02:31:33.889 --> 02:31:33.899 align:start position:0% a spread Spectrum was introduced to 02:31:33.899 --> 02:31:36.110 align:start position:0% a spread Spectrum was introduced to address<02:31:34.080> some<02:31:34.560> of<02:31:34.680> the<02:31:34.979> concerns<02:31:35.819> that<02:31:36.000> I've 02:31:36.110 --> 02:31:36.120 align:start position:0% address some of the concerns that I've 02:31:36.120 --> 02:31:38.570 align:start position:0% address some of the concerns that I've just<02:31:36.300> mentioned<02:31:36.660> uh<02:31:37.560> it<02:31:37.800> takes<02:31:37.920> the<02:31:38.340> radio 02:31:38.570 --> 02:31:38.580 align:start position:0% just mentioned uh it takes the radio 02:31:38.580 --> 02:31:41.570 align:start position:0% just mentioned uh it takes the radio signal<02:31:39.240> to<02:31:39.780> be<02:31:39.899> transmitted<02:31:40.500> and<02:31:41.040> it<02:31:41.160> sends<02:31:41.520> it 02:31:41.570 --> 02:31:41.580 align:start position:0% signal to be transmitted and it sends it 02:31:41.580 --> 02:31:44.270 align:start position:0% signal to be transmitted and it sends it over<02:31:41.760> more<02:31:42.180> than<02:31:42.420> one<02:31:42.899> frequency<02:31:43.439> so<02:31:44.100> this 02:31:44.270 --> 02:31:44.280 align:start position:0% over more than one frequency so this 02:31:44.280 --> 02:31:46.429 align:start position:0% over more than one frequency so this makes<02:31:44.520> it<02:31:44.700> more<02:31:44.939> difficult<02:31:45.300> to<02:31:45.780> intercept<02:31:46.140> the 02:31:46.429 --> 02:31:46.439 align:start position:0% makes it more difficult to intercept the 02:31:46.439 --> 02:31:48.230 align:start position:0% makes it more difficult to intercept the data<02:31:46.680> in<02:31:46.920> transit<02:31:47.399> now<02:31:47.819> there<02:31:48.000> are<02:31:48.180> two 02:31:48.230 --> 02:31:48.240 align:start position:0% data in transit now there are two 02:31:48.240 --> 02:31:50.270 align:start position:0% data in transit now there are two different<02:31:48.420> types<02:31:48.960> of<02:31:49.080> spread<02:31:49.560> spectrums 02:31:50.270 --> 02:31:50.280 align:start position:0% different types of spread spectrums 02:31:50.280 --> 02:31:53.870 align:start position:0% different types of spread spectrums first<02:31:51.000> is<02:31:51.240> DSS<02:31:51.780> or<02:31:52.140> direct<02:31:52.439> sequence<02:31:53.280> spread 02:31:53.870 --> 02:31:53.880 align:start position:0% first is DSS or direct sequence spread 02:31:53.880 --> 02:31:57.190 align:start position:0% first is DSS or direct sequence spread Spectrum<02:31:54.479> the<02:31:55.260> direct<02:31:55.380> sequence 02:31:57.190 --> 02:31:57.200 align:start position:0% Spectrum the direct sequence 02:31:57.200 --> 02:31:59.950 align:start position:0% Spectrum the direct sequence spread<02:31:58.200> Spectrum<02:31:58.800> that's<02:31:59.220> a<02:31:59.460> mouthful 02:31:59.950 --> 02:31:59.960 align:start position:0% spread Spectrum that's a mouthful 02:31:59.960 --> 02:32:03.469 align:start position:0% spread Spectrum that's a mouthful utilizes<02:32:00.960> multiple<02:32:01.500> channels<02:32:02.040> to<02:32:02.760> transmit 02:32:03.469 --> 02:32:03.479 align:start position:0% utilizes multiple channels to transmit 02:32:03.479 --> 02:32:06.290 align:start position:0% utilizes multiple channels to transmit the<02:32:03.780> message<02:32:04.020> simultaneously 02:32:06.290 --> 02:32:06.300 align:start position:0% the message simultaneously 02:32:06.300 --> 02:32:09.950 align:start position:0% the message simultaneously so<02:32:06.960> it's<02:32:07.200> going<02:32:07.380> to<02:32:07.500> use<02:32:07.560> multiple<02:32:08.100> channels 02:32:09.950 --> 02:32:09.960 align:start position:0% so it's going to use multiple channels 02:32:09.960 --> 02:32:12.710 align:start position:0% so it's going to use multiple channels and<02:32:10.439> it's<02:32:10.560> going<02:32:10.740> to<02:32:10.920> send<02:32:11.220> that<02:32:11.460> message 02:32:12.710 --> 02:32:12.720 align:start position:0% and it's going to send that message 02:32:12.720 --> 02:32:16.250 align:start position:0% and it's going to send that message all<02:32:13.260> at<02:32:13.380> the<02:32:13.560> same<02:32:13.740> time 02:32:16.250 --> 02:32:16.260 align:start position:0% 02:32:16.260 --> 02:32:18.770 align:start position:0% with<02:32:16.800> DSS<02:32:17.280> there's<02:32:17.580> also<02:32:17.819> a<02:32:17.939> method<02:32:18.180> of<02:32:18.359> error 02:32:18.770 --> 02:32:18.780 align:start position:0% with DSS there's also a method of error 02:32:18.780 --> 02:32:21.710 align:start position:0% with DSS there's also a method of error checking<02:32:19.080> and<02:32:19.200> it's<02:32:19.380> called<02:32:19.680> edac 02:32:21.710 --> 02:32:21.720 align:start position:0% checking and it's called edac 02:32:21.720 --> 02:32:22.969 align:start position:0% checking and it's called edac which<02:32:22.080> I<02:32:22.200> don't<02:32:22.260> think<02:32:22.380> you'll<02:32:22.560> see<02:32:22.740> on<02:32:22.859> the 02:32:22.969 --> 02:32:22.979 align:start position:0% which I don't think you'll see on the 02:32:22.979 --> 02:32:24.889 align:start position:0% which I don't think you'll see on the test<02:32:23.160> which<02:32:23.760> is<02:32:23.880> error<02:32:24.359> detection<02:32:24.660> and 02:32:24.889 --> 02:32:24.899 align:start position:0% test which is error detection and 02:32:24.899 --> 02:32:26.770 align:start position:0% test which is error detection and correction<02:32:25.200> and<02:32:25.439> this<02:32:25.620> allows<02:32:25.979> for<02:32:26.280> a<02:32:26.460> certain 02:32:26.770 --> 02:32:26.780 align:start position:0% correction and this allows for a certain 02:32:26.780 --> 02:32:29.809 align:start position:0% correction and this allows for a certain degree<02:32:27.780> of<02:32:28.260> signal<02:32:28.680> loss<02:32:28.979> while<02:32:29.399> still<02:32:29.700> being 02:32:29.809 --> 02:32:29.819 align:start position:0% degree of signal loss while still being 02:32:29.819 --> 02:32:31.490 align:start position:0% degree of signal loss while still being able<02:32:30.060> to<02:32:30.180> put<02:32:30.359> the<02:32:30.540> original<02:32:30.720> signal<02:32:31.260> back 02:32:31.490 --> 02:32:31.500 align:start position:0% able to put the original signal back 02:32:31.500 --> 02:32:36.410 align:start position:0% able to put the original signal back together<02:32:31.740> on<02:32:32.460> the<02:32:32.640> receiving<02:32:32.880> end 02:32:36.410 --> 02:32:36.420 align:start position:0% 02:32:36.420 --> 02:32:37.910 align:start position:0% on<02:32:37.080> the<02:32:37.140> other<02:32:37.200> hand<02:32:37.319> we<02:32:37.500> also<02:32:37.680> have<02:32:37.740> something 02:32:37.910 --> 02:32:37.920 align:start position:0% on the other hand we also have something 02:32:37.920 --> 02:32:41.870 align:start position:0% on the other hand we also have something called<02:32:38.540> fhss<02:32:39.540> or<02:32:39.899> frequency<02:32:40.380> hopping<02:32:41.340> spread 02:32:41.870 --> 02:32:41.880 align:start position:0% called fhss or frequency hopping spread 02:32:41.880 --> 02:32:45.050 align:start position:0% called fhss or frequency hopping spread Spectrum<02:32:42.420> in<02:32:43.200> this<02:32:43.319> method<02:32:43.680> uh<02:32:44.280> it<02:32:44.640> sends<02:32:44.939> the 02:32:45.050 --> 02:32:45.060 align:start position:0% Spectrum in this method uh it sends the 02:32:45.060 --> 02:32:50.090 align:start position:0% Spectrum in this method uh it sends the signal<02:32:45.300> across<02:32:45.720> one<02:32:46.020> channel<02:32:46.260> at<02:32:46.740> a<02:32:46.859> time 02:32:50.090 --> 02:32:50.100 align:start position:0% 02:32:50.100 --> 02:32:53.210 align:start position:0% and<02:32:50.880> hops<02:32:51.359> to<02:32:51.479> the<02:32:51.600> channel<02:32:51.780> uh<02:32:52.560> each<02:32:53.040> Channel 02:32:53.210 --> 02:32:53.220 align:start position:0% and hops to the channel uh each Channel 02:32:53.220 --> 02:32:55.370 align:start position:0% and hops to the channel uh each Channel just<02:32:53.580> just<02:32:53.760> sort<02:32:54.000> of<02:32:54.060> hops<02:32:54.420> to<02:32:54.540> another<02:32:54.720> one<02:32:54.960> at 02:32:55.370 --> 02:32:55.380 align:start position:0% just just sort of hops to another one at 02:32:55.380 --> 02:32:59.210 align:start position:0% just just sort of hops to another one at a<02:32:55.620> predetermined<02:32:56.220> interval 02:32:59.210 --> 02:32:59.220 align:start position:0% 02:32:59.220 --> 02:33:01.130 align:start position:0% this<02:32:59.700> method<02:32:59.939> can<02:33:00.120> hop<02:33:00.300> from<02:33:00.540> frequency<02:33:00.899> to 02:33:01.130 --> 02:33:01.140 align:start position:0% this method can hop from frequency to 02:33:01.140 --> 02:33:04.309 align:start position:0% this method can hop from frequency to frequency<02:33:01.560> anywhere<02:33:02.160> from<02:33:02.700> 50<02:33:03.420> to<02:33:03.720> a<02:33:03.899> several 02:33:04.309 --> 02:33:04.319 align:start position:0% frequency anywhere from 50 to a several 02:33:04.319 --> 02:33:13.309 align:start position:0% frequency anywhere from 50 to a several hundred<02:33:05.040> uh<02:33:05.640> different<02:33:05.939> frequencies 02:33:13.309 --> 02:33:13.319 align:start position:0% 02:33:13.319 --> 02:33:14.750 align:start position:0% per<02:33:13.859> second 02:33:14.750 --> 02:33:14.760 align:start position:0% per second 02:33:14.760 --> 02:33:16.190 align:start position:0% per second the<02:33:15.120> sender<02:33:15.420> and<02:33:15.540> receiver<02:33:15.780> as<02:33:15.960> you<02:33:16.080> can 02:33:16.190 --> 02:33:16.200 align:start position:0% the sender and receiver as you can 02:33:16.200 --> 02:33:17.750 align:start position:0% the sender and receiver as you can imagine<02:33:16.260> need<02:33:16.680> to<02:33:16.800> be<02:33:16.920> synchronized<02:33:17.399> with<02:33:17.580> one 02:33:17.750 --> 02:33:17.760 align:start position:0% imagine need to be synchronized with one 02:33:17.760 --> 02:33:19.070 align:start position:0% imagine need to be synchronized with one another<02:33:17.880> and<02:33:18.240> they<02:33:18.300> also<02:33:18.540> have<02:33:18.600> to<02:33:18.720> have<02:33:18.899> the 02:33:19.070 --> 02:33:19.080 align:start position:0% another and they also have to have the 02:33:19.080 --> 02:33:22.849 align:start position:0% another and they also have to have the same<02:33:19.760> uh<02:33:20.760> set<02:33:21.300> of<02:33:21.660> frequencies<02:33:22.140> to<02:33:22.439> hop<02:33:22.560> to 02:33:22.849 --> 02:33:22.859 align:start position:0% same uh set of frequencies to hop to 02:33:22.859 --> 02:33:26.650 align:start position:0% same uh set of frequencies to hop to which<02:33:23.100> which<02:33:23.280> is<02:33:23.520> called<02:33:23.760> a<02:33:24.000> hop<02:33:24.420> set 02:33:26.650 --> 02:33:26.660 align:start position:0% which which is called a hop set 02:33:26.660 --> 02:33:29.150 align:start position:0% which which is called a hop set this<02:33:27.660> method<02:33:27.899> of<02:33:28.140> radio<02:33:28.319> communication<02:33:28.920> by 02:33:29.150 --> 02:33:29.160 align:start position:0% this method of radio communication by 02:33:29.160 --> 02:33:31.490 align:start position:0% this method of radio communication by the<02:33:29.280> way<02:33:29.340> is<02:33:29.520> it's<02:33:29.819> commonly<02:33:30.359> used<02:33:30.660> in<02:33:31.380> the 02:33:31.490 --> 02:33:31.500 align:start position:0% the way is it's commonly used in the 02:33:31.500 --> 02:33:35.929 align:start position:0% the way is it's commonly used in the military<02:33:31.680> because<02:33:32.460> it<02:33:32.700> has<02:33:32.939> a<02:33:33.359> fairly 02:33:35.929 --> 02:33:35.939 align:start position:0% military because it has a fairly 02:33:35.939 --> 02:33:40.809 align:start position:0% military because it has a fairly strong<02:33:36.600> sense<02:33:37.020> of<02:33:37.140> security<02:33:37.439> about<02:33:37.859> it 02:33:40.809 --> 02:33:40.819 align:start position:0% 02:33:40.819 --> 02:33:44.030 align:start position:0% infrared<02:33:41.819> or<02:33:42.120> infrared<02:33:42.840> which<02:33:43.740> you<02:33:43.920> might 02:33:44.030 --> 02:33:44.040 align:start position:0% infrared or infrared which you might 02:33:44.040 --> 02:33:47.809 align:start position:0% infrared or infrared which you might have<02:33:44.160> heard<02:33:44.340> of<02:33:44.520> uh 02:33:47.809 --> 02:33:47.819 align:start position:0% 02:33:47.819 --> 02:33:49.429 align:start position:0% Transmissions 02:33:49.429 --> 02:33:49.439 align:start position:0% Transmissions 02:33:49.439 --> 02:33:51.410 align:start position:0% Transmissions are<02:33:50.160> also<02:33:50.399> unbounded<02:33:50.880> forms<02:33:51.240> of 02:33:51.410 --> 02:33:51.420 align:start position:0% are also unbounded forms of 02:33:51.420 --> 02:33:53.870 align:start position:0% are also unbounded forms of communication<02:33:52.020> and<02:33:52.800> the<02:33:52.920> and<02:33:53.340> the<02:33:53.460> data<02:33:53.760> is 02:33:53.870 --> 02:33:53.880 align:start position:0% communication and the and the data is 02:33:53.880 --> 02:33:57.410 align:start position:0% communication and the and the data is sent<02:33:54.120> via<02:33:54.720> pulses<02:33:55.260> of<02:33:55.680> infrared<02:33:56.340> light 02:33:57.410 --> 02:33:57.420 align:start position:0% sent via pulses of infrared light 02:33:57.420 --> 02:34:01.250 align:start position:0% sent via pulses of infrared light hence<02:33:58.140> the<02:33:58.500> name<02:33:58.800> infrared<02:33:59.460> this<02:34:00.420> light<02:34:00.600> is<02:34:00.840> ah 02:34:01.250 --> 02:34:01.260 align:start position:0% hence the name infrared this light is ah 02:34:01.260 --> 02:34:04.910 align:start position:0% hence the name infrared this light is ah between<02:34:01.560> 300<02:34:02.340> gigahertz<02:34:02.939> and<02:34:03.780> 300<02:34:04.800> 000 02:34:04.910 --> 02:34:04.920 align:start position:0% between 300 gigahertz and 300 000 02:34:04.920 --> 02:34:07.610 align:start position:0% between 300 gigahertz and 300 000 gigahertz<02:34:05.460> range<02:34:06.000> and<02:34:06.840> in<02:34:07.140> the<02:34:07.260> in<02:34:07.439> the 02:34:07.610 --> 02:34:07.620 align:start position:0% gigahertz range and in the in the 02:34:07.620 --> 02:34:10.010 align:start position:0% gigahertz range and in the in the electromagnetic<02:34:08.399> spectrum<02:34:08.819> of<02:34:09.359> ranges<02:34:09.840> and 02:34:10.010 --> 02:34:10.020 align:start position:0% electromagnetic spectrum of ranges and 02:34:10.020 --> 02:34:11.870 align:start position:0% electromagnetic spectrum of ranges and frequencies<02:34:10.560> there<02:34:11.220> are<02:34:11.340> also<02:34:11.460> a<02:34:11.580> few<02:34:11.640> types 02:34:11.870 --> 02:34:11.880 align:start position:0% frequencies there are also a few types 02:34:11.880 --> 02:34:14.090 align:start position:0% frequencies there are also a few types of<02:34:12.000> ir<02:34:12.180> that<02:34:12.660> can<02:34:12.840> be<02:34:13.020> used 02:34:14.090 --> 02:34:14.100 align:start position:0% of ir that can be used 02:34:14.100 --> 02:34:15.790 align:start position:0% of ir that can be used um<02:34:14.160> all<02:34:14.340> of<02:34:14.520> which<02:34:14.640> need<02:34:15.000> an<02:34:15.300> absolutely 02:34:15.790 --> 02:34:15.800 align:start position:0% um all of which need an absolutely 02:34:15.800 --> 02:34:18.650 align:start position:0% um all of which need an absolutely unobstructed<02:34:16.800> view<02:34:17.040> between<02:34:17.460> devices<02:34:18.000> this 02:34:18.650 --> 02:34:18.660 align:start position:0% unobstructed view between devices this 02:34:18.660 --> 02:34:21.290 align:start position:0% unobstructed view between devices this means<02:34:19.020> that<02:34:19.319> they<02:34:19.740> are<02:34:19.859> what<02:34:20.040> we<02:34:20.220> call<02:34:20.460> line<02:34:21.060> of 02:34:21.290 --> 02:34:21.300 align:start position:0% means that they are what we call line of 02:34:21.300 --> 02:34:23.690 align:start position:0% means that they are what we call line of sight 02:34:23.690 --> 02:34:23.700 align:start position:0% 02:34:23.700 --> 02:34:32.809 align:start position:0% or<02:34:24.240> loss 02:34:32.809 --> 02:34:32.819 align:start position:0% 02:34:32.819 --> 02:34:34.969 align:start position:0% because<02:34:33.120> of<02:34:33.479> this<02:34:33.600> it<02:34:33.780> nearly<02:34:34.140> guarantees 02:34:34.969 --> 02:34:34.979 align:start position:0% because of this it nearly guarantees 02:34:34.979 --> 02:34:36.469 align:start position:0% because of this it nearly guarantees that<02:34:35.220> there's<02:34:35.399> a<02:34:35.520> secure<02:34:35.819> connection<02:34:36.060> between 02:34:36.469 --> 02:34:36.479 align:start position:0% that there's a secure connection between 02:34:36.479 --> 02:34:38.270 align:start position:0% that there's a secure connection between the<02:34:36.780> devices<02:34:37.020> because<02:34:37.560> they<02:34:37.740> have<02:34:37.859> to<02:34:37.920> be<02:34:38.040> so 02:34:38.270 --> 02:34:38.280 align:start position:0% the devices because they have to be so 02:34:38.280 --> 02:34:39.710 align:start position:0% the devices because they have to be so close<02:34:38.520> to<02:34:38.700> one<02:34:38.880> another 02:34:39.710 --> 02:34:39.720 align:start position:0% close to one another 02:34:39.720 --> 02:34:41.690 align:start position:0% close to one another another<02:34:40.200> example<02:34:40.620> of<02:34:40.800> infrared<02:34:41.220> being<02:34:41.460> used 02:34:41.690 --> 02:34:41.700 align:start position:0% another example of infrared being used 02:34:41.700 --> 02:34:45.050 align:start position:0% another example of infrared being used by<02:34:42.240> the<02:34:42.359> way<02:34:42.420> is<02:34:42.660> your<02:34:43.200> remote<02:34:43.920> control<02:34:44.460> which 02:34:45.050 --> 02:34:45.060 align:start position:0% by the way is your remote control which 02:34:45.060 --> 02:34:46.190 align:start position:0% by the way is your remote control which is<02:34:45.180> the<02:34:45.300> reason<02:34:45.420> that<02:34:45.660> we<02:34:45.780> probably<02:34:45.899> found 02:34:46.190 --> 02:34:46.200 align:start position:0% is the reason that we probably found 02:34:46.200 --> 02:34:48.349 align:start position:0% is the reason that we probably found them<02:34:46.380> on<02:34:46.500> a<02:34:46.680> lot<02:34:46.740> of<02:34:46.859> laptops<02:34:47.460> now<02:34:48.060> there<02:34:48.240> are 02:34:48.349 --> 02:34:48.359 align:start position:0% them on a lot of laptops now there are 02:34:48.359 --> 02:34:50.570 align:start position:0% them on a lot of laptops now there are different<02:34:48.479> types<02:34:49.080> of<02:34:49.319> infrared<02:34:49.920> connections 02:34:50.570 --> 02:34:50.580 align:start position:0% different types of infrared connections 02:34:50.580 --> 02:34:53.389 align:start position:0% different types of infrared connections uh<02:34:51.240> they're<02:34:51.600> serial<02:34:52.200> infrared<02:34:52.859> which<02:34:53.160> means 02:34:53.389 --> 02:34:53.399 align:start position:0% uh they're serial infrared which means 02:34:53.399 --> 02:34:55.490 align:start position:0% uh they're serial infrared which means that<02:34:53.640> the<02:34:53.880> data<02:34:54.420> is<02:34:54.540> sent<02:34:54.780> in<02:34:55.080> a<02:34:55.200> Serial 02:34:55.490 --> 02:34:55.500 align:start position:0% that the data is sent in a Serial 02:34:55.500 --> 02:34:58.130 align:start position:0% that the data is sent in a Serial fashion<02:34:56.040> uh<02:34:56.880> in<02:34:57.120> this<02:34:57.240> case<02:34:57.420> you're<02:34:57.840> looking 02:34:58.130 --> 02:34:58.140 align:start position:0% fashion uh in this case you're looking 02:34:58.140 --> 02:35:01.730 align:start position:0% fashion uh in this case you're looking at<02:34:58.380> probably<02:34:58.740> around<02:34:58.979> 115 02:35:01.730 --> 02:35:01.740 align:start position:0% at probably around 115 02:35:01.740 --> 02:35:04.490 align:start position:0% at probably around 115 kilobits<02:35:02.580> per<02:35:02.760> second<02:35:03.000> then<02:35:03.720> we<02:35:03.960> also<02:35:04.260> have 02:35:04.490 --> 02:35:04.500 align:start position:0% kilobits per second then we also have 02:35:04.500 --> 02:35:07.370 align:start position:0% kilobits per second then we also have fast<02:35:05.160> infrared<02:35:05.880> which<02:35:06.420> goes<02:35:06.720> up<02:35:06.840> to<02:35:07.020> four 02:35:07.370 --> 02:35:07.380 align:start position:0% fast infrared which goes up to four 02:35:07.380 --> 02:35:10.730 align:start position:0% fast infrared which goes up to four megabits<02:35:08.160> per<02:35:08.520> second<02:35:08.760> and<02:35:09.660> finally<02:35:10.020> very 02:35:10.730 --> 02:35:10.740 align:start position:0% megabits per second and finally very 02:35:10.740 --> 02:35:13.370 align:start position:0% megabits per second and finally very fast<02:35:11.040> infrared<02:35:11.819> which<02:35:12.780> gives<02:35:13.020> you<02:35:13.140> up<02:35:13.260> to 02:35:13.370 --> 02:35:13.380 align:start position:0% fast infrared which gives you up to 02:35:13.380 --> 02:35:16.130 align:start position:0% fast infrared which gives you up to about<02:35:13.560> 16<02:35:13.979> megabits<02:35:14.760> per<02:35:14.939> second<02:35:15.180> so<02:35:15.899> you<02:35:16.020> can 02:35:16.130 --> 02:35:16.140 align:start position:0% about 16 megabits per second so you can 02:35:16.140 --> 02:35:18.590 align:start position:0% about 16 megabits per second so you can see<02:35:16.260> that<02:35:16.500> there<02:35:16.680> is<02:35:16.920> a<02:35:17.220> uh<02:35:18.000> the<02:35:18.300> technology 02:35:18.590 --> 02:35:18.600 align:start position:0% see that there is a uh the technology 02:35:18.600 --> 02:35:21.230 align:start position:0% see that there is a uh the technology has<02:35:19.080> changed<02:35:19.500> quite<02:35:19.740> a<02:35:19.920> bit<02:35:20.040> that<02:35:20.760> being<02:35:20.939> said 02:35:21.230 --> 02:35:21.240 align:start position:0% has changed quite a bit that being said 02:35:21.240 --> 02:35:23.750 align:start position:0% has changed quite a bit that being said we<02:35:21.840> don't<02:35:21.960> see<02:35:22.140> this<02:35:22.380> a<02:35:22.560> lot<02:35:22.680> in<02:35:22.920> sort<02:35:23.160> of<02:35:23.700> um 02:35:23.750 --> 02:35:23.760 align:start position:0% we don't see this a lot in sort of um 02:35:23.760 --> 02:35:27.410 align:start position:0% we don't see this a lot in sort of um consumer<02:35:24.540> markets<02:35:25.020> just<02:35:25.200> because<02:35:25.500> it<02:35:26.399> is<02:35:26.580> uh 02:35:27.410 --> 02:35:27.420 align:start position:0% consumer markets just because it is uh 02:35:27.420 --> 02:35:29.690 align:start position:0% consumer markets just because it is uh because<02:35:28.140> of<02:35:28.380> the<02:35:28.500> line<02:35:28.620> of<02:35:28.800> sight<02:35:28.979> necessity 02:35:29.690 --> 02:35:29.700 align:start position:0% because of the line of sight necessity 02:35:29.700 --> 02:35:30.590 align:start position:0% because of the line of sight necessity of<02:35:29.880> it 02:35:30.590 --> 02:35:30.600 align:start position:0% of it 02:35:30.600 --> 02:35:32.990 align:start position:0% of it now<02:35:31.140> there's<02:35:31.439> also<02:35:31.800> Bluetooth<02:35:32.160> Transmissions 02:35:32.990 --> 02:35:33.000 align:start position:0% now there's also Bluetooth Transmissions 02:35:33.000 --> 02:35:35.690 align:start position:0% now there's also Bluetooth Transmissions which<02:35:33.300> is<02:35:33.479> another<02:35:33.720> form<02:35:34.200> of<02:35:34.920> short<02:35:35.220> range 02:35:35.690 --> 02:35:35.700 align:start position:0% which is another form of short range 02:35:35.700 --> 02:35:38.090 align:start position:0% which is another form of short range wireless<02:35:36.180> communication<02:35:36.960> it's<02:35:37.500> increasingly 02:35:38.090 --> 02:35:38.100 align:start position:0% wireless communication it's increasingly 02:35:38.100 --> 02:35:40.070 align:start position:0% wireless communication it's increasingly popular<02:35:38.399> you've<02:35:39.240> probably<02:35:39.359> seen<02:35:39.600> it<02:35:39.780> with 02:35:40.070 --> 02:35:40.080 align:start position:0% popular you've probably seen it with 02:35:40.080 --> 02:35:43.190 align:start position:0% popular you've probably seen it with these<02:35:40.380> sort<02:35:40.500> of<02:35:40.620> headsets<02:35:41.160> and<02:35:41.819> it<02:35:41.939> uses<02:35:42.240> a<02:35:42.600> 2.4 02:35:43.190 --> 02:35:43.200 align:start position:0% these sort of headsets and it uses a 2.4 02:35:43.200 --> 02:35:46.250 align:start position:0% these sort of headsets and it uses a 2.4 gigahertz<02:35:43.920> frequency<02:35:44.460> which<02:35:45.120> by<02:35:45.359> the<02:35:45.540> way<02:35:45.660> is 02:35:46.250 --> 02:35:46.260 align:start position:0% gigahertz frequency which by the way is 02:35:46.260 --> 02:35:48.410 align:start position:0% gigahertz frequency which by the way is the<02:35:46.439> same<02:35:46.560> we're<02:35:46.740> going<02:35:46.920> to<02:35:47.040> see<02:35:47.220> with<02:35:47.880> Wi-Fi 02:35:48.410 --> 02:35:48.420 align:start position:0% the same we're going to see with Wi-Fi 02:35:48.420 --> 02:35:51.290 align:start position:0% the same we're going to see with Wi-Fi and<02:35:49.020> so<02:35:49.200> that<02:35:49.439> this<02:35:49.680> can<02:35:49.859> actually<02:35:49.979> cause<02:35:50.460> uh 02:35:51.290 --> 02:35:51.300 align:start position:0% and so that this can actually cause uh 02:35:51.300 --> 02:35:53.750 align:start position:0% and so that this can actually cause uh some<02:35:51.660> interference<02:35:52.620> with<02:35:52.979> your<02:35:53.220> at-home 02:35:53.750 --> 02:35:53.760 align:start position:0% some interference with your at-home 02:35:53.760 --> 02:35:56.150 align:start position:0% some interference with your at-home Wi-Fi<02:35:54.300> network<02:35:54.600> now<02:35:55.319> today<02:35:55.560> Bluetooth<02:35:55.800> is 02:35:56.150 --> 02:35:56.160 align:start position:0% Wi-Fi network now today Bluetooth is 02:35:56.160 --> 02:35:58.010 align:start position:0% Wi-Fi network now today Bluetooth is used<02:35:56.340> to<02:35:56.520> connect<02:35:56.640> devices<02:35:57.060> like<02:35:57.420> headsets 02:35:58.010 --> 02:35:58.020 align:start position:0% used to connect devices like headsets 02:35:58.020 --> 02:36:01.490 align:start position:0% used to connect devices like headsets cell<02:35:58.560> phones<02:35:59.000> uh<02:36:00.000> laptops<02:36:00.660> mice<02:36:01.020> gaming 02:36:01.490 --> 02:36:01.500 align:start position:0% cell phones uh laptops mice gaming 02:36:01.500 --> 02:36:03.050 align:start position:0% cell phones uh laptops mice gaming consoles 02:36:03.050 --> 02:36:03.060 align:start position:0% consoles 02:36:03.060 --> 02:36:05.030 align:start position:0% consoles um so<02:36:03.600> on<02:36:03.720> and<02:36:03.899> so<02:36:04.080> forth 02:36:05.030 --> 02:36:05.040 align:start position:0% um so on and so forth 02:36:05.040 --> 02:36:08.590 align:start position:0% um so on and so forth the<02:36:05.700> accepted<02:36:06.560> maximum<02:36:07.560> range<02:36:07.979> of<02:36:08.160> Bluetooth 02:36:08.590 --> 02:36:08.600 align:start position:0% the accepted maximum range of Bluetooth 02:36:08.600 --> 02:36:12.650 align:start position:0% the accepted maximum range of Bluetooth communication<02:36:09.600> is<02:36:09.899> about<02:36:10.020> 30<02:36:10.500> feet<02:36:11.060> uh<02:36:12.060> which 02:36:12.650 --> 02:36:12.660 align:start position:0% communication is about 30 feet uh which 02:36:12.660 --> 02:36:16.130 align:start position:0% communication is about 30 feet uh which is<02:36:12.840> equivalent<02:36:13.500> to<02:36:13.859> around<02:36:14.340> 10<02:36:15.060> meters 02:36:16.130 --> 02:36:16.140 align:start position:0% is equivalent to around 10 meters 02:36:16.140 --> 02:36:18.050 align:start position:0% is equivalent to around 10 meters but<02:36:16.680> the<02:36:16.859> newest<02:36:17.160> implementation<02:36:17.700> Bluetooth 02:36:18.050 --> 02:36:18.060 align:start position:0% but the newest implementation Bluetooth 02:36:18.060 --> 02:36:21.590 align:start position:0% but the newest implementation Bluetooth 2.0<02:36:18.899> is<02:36:19.680> said<02:36:20.040> to<02:36:20.160> reach<02:36:20.340> up<02:36:20.520> to<02:36:20.700> 30<02:36:20.939> meters<02:36:21.359> or 02:36:21.590 --> 02:36:21.600 align:start position:0% 2.0 is said to reach up to 30 meters or 02:36:21.600 --> 02:36:24.050 align:start position:0% 2.0 is said to reach up to 30 meters or a<02:36:21.780> hundred<02:36:22.020> feet<02:36:22.319> uh<02:36:23.160> but<02:36:23.399> it's<02:36:23.880> not 02:36:24.050 --> 02:36:24.060 align:start position:0% a hundred feet uh but it's not 02:36:24.060 --> 02:36:26.630 align:start position:0% a hundred feet uh but it's not guaranteed<02:36:24.540> to<02:36:24.720> run<02:36:24.840> that<02:36:25.020> distance<02:36:25.260> and 02:36:26.630 --> 02:36:26.640 align:start position:0% guaranteed to run that distance and 02:36:26.640 --> 02:36:28.429 align:start position:0% guaranteed to run that distance and um<02:36:26.760> in<02:36:27.120> application<02:36:27.600> it<02:36:27.899> might<02:36:28.080> not<02:36:28.200> actually 02:36:28.429 --> 02:36:28.439 align:start position:0% um in application it might not actually 02:36:28.439 --> 02:36:30.410 align:start position:0% um in application it might not actually get<02:36:28.680> there<02:36:28.920> now<02:36:29.580> when<02:36:29.760> you're<02:36:29.939> connecting 02:36:30.410 --> 02:36:30.420 align:start position:0% get there now when you're connecting 02:36:30.420 --> 02:36:33.410 align:start position:0% get there now when you're connecting devices<02:36:30.840> by<02:36:31.260> bluetooth<02:36:31.560> we<02:36:32.399> call<02:36:32.640> it<02:36:32.880> pairing 02:36:33.410 --> 02:36:33.420 align:start position:0% devices by bluetooth we call it pairing 02:36:33.420 --> 02:36:36.110 align:start position:0% devices by bluetooth we call it pairing devices<02:36:33.800> uh<02:36:34.800> and<02:36:35.040> if<02:36:35.340> you've<02:36:35.520> never<02:36:35.700> done<02:36:35.939> this 02:36:36.110 --> 02:36:36.120 align:start position:0% devices uh and if you've never done this 02:36:36.120 --> 02:36:37.849 align:start position:0% devices uh and if you've never done this before<02:36:36.300> generally<02:36:36.720> there's<02:36:37.020> a<02:36:37.319> pin<02:36:37.680> code 02:36:37.849 --> 02:36:37.859 align:start position:0% before generally there's a pin code 02:36:37.859 --> 02:36:39.830 align:start position:0% before generally there's a pin code that's<02:36:38.819> used 02:36:39.830 --> 02:36:39.840 align:start position:0% that's used 02:36:39.840 --> 02:36:42.590 align:start position:0% that's used to<02:36:40.740> pin<02:36:41.460> these<02:36:41.760> a<02:36:41.939> pair<02:36:42.120> these<02:36:42.420> devices 02:36:42.590 --> 02:36:42.600 align:start position:0% to pin these a pair these devices 02:36:42.600 --> 02:36:43.910 align:start position:0% to pin these a pair these devices together<02:36:42.899> to<02:36:43.200> make<02:36:43.319> sure<02:36:43.439> that<02:36:43.620> they<02:36:43.800> are 02:36:43.910 --> 02:36:43.920 align:start position:0% together to make sure that they are 02:36:43.920 --> 02:36:45.230 align:start position:0% together to make sure that they are secure<02:36:44.160> and<02:36:44.340> you're<02:36:44.460> not<02:36:44.580> connecting<02:36:44.939> to<02:36:45.060> a 02:36:45.230 --> 02:36:45.240 align:start position:0% secure and you're not connecting to a 02:36:45.240 --> 02:36:47.690 align:start position:0% secure and you're not connecting to a different<02:36:45.300> device<02:36:45.600> the<02:36:46.439> next<02:36:46.560> type<02:36:46.859> of<02:36:47.040> uh 02:36:47.690 --> 02:36:47.700 align:start position:0% different device the next type of uh 02:36:47.700 --> 02:36:49.610 align:start position:0% different device the next type of uh Wireless<02:36:48.240> transmission<02:36:48.780> I<02:36:49.260> want<02:36:49.380> to<02:36:49.500> talk 02:36:49.610 --> 02:36:49.620 align:start position:0% Wireless transmission I want to talk 02:36:49.620 --> 02:36:52.010 align:start position:0% Wireless transmission I want to talk about<02:36:49.740> is<02:36:50.160> microwave<02:36:50.880> transmission<02:36:51.240> is<02:36:51.780> the 02:36:52.010 --> 02:36:52.020 align:start position:0% about is microwave transmission is the 02:36:52.020 --> 02:36:52.730 align:start position:0% about is microwave transmission is the same 02:36:52.730 --> 02:36:52.740 align:start position:0% same 02:36:52.740 --> 02:36:55.429 align:start position:0% same term<02:36:53.220> for<02:36:53.520> that<02:36:53.700> thing<02:36:53.880> in<02:36:54.120> your<02:36:54.300> house<02:36:54.540> the 02:36:55.429 --> 02:36:55.439 align:start position:0% term for that thing in your house the 02:36:55.439 --> 02:36:57.710 align:start position:0% term for that thing in your house the microwave<02:36:55.800> operates<02:36:56.280> in<02:36:56.580> one<02:36:56.819> one<02:36:57.240> gigahertz 02:36:57.710 --> 02:36:57.720 align:start position:0% microwave operates in one one gigahertz 02:36:57.720 --> 02:37:02.090 align:start position:0% microwave operates in one one gigahertz to<02:36:57.960> 300<02:36:58.560> gigahertz<02:36:59.100> frequency<02:36:59.640> range<02:37:00.260> and<02:37:01.260> for 02:37:02.090 --> 02:37:02.100 align:start position:0% to 300 gigahertz frequency range and for 02:37:02.100 --> 02:37:04.130 align:start position:0% to 300 gigahertz frequency range and for the<02:37:02.280> microwave<02:37:02.760> transmission<02:37:03.420> to<02:37:03.899> be 02:37:04.130 --> 02:37:04.140 align:start position:0% the microwave transmission to be 02:37:04.140 --> 02:37:06.290 align:start position:0% the microwave transmission to be received<02:37:04.859> successfully<02:37:05.220> there<02:37:05.460> has<02:37:05.640> to<02:37:05.819> be<02:37:05.939> an 02:37:06.290 --> 02:37:06.300 align:start position:0% received successfully there has to be an 02:37:06.300 --> 02:37:09.530 align:start position:0% received successfully there has to be an unobstructed<02:37:07.080> view<02:37:07.380> or<02:37:08.340> point-to-point<02:37:09.180> line 02:37:09.530 --> 02:37:09.540 align:start position:0% unobstructed view or point-to-point line 02:37:09.540 --> 02:37:10.870 align:start position:0% unobstructed view or point-to-point line of 02:37:10.870 --> 02:37:10.880 align:start position:0% of 02:37:10.880 --> 02:37:15.170 align:start position:0% of communication<02:37:11.960> so<02:37:13.439> just<02:37:14.100> imagine<02:37:14.340> that<02:37:14.760> the 02:37:15.170 --> 02:37:15.180 align:start position:0% communication so just imagine that the 02:37:15.180 --> 02:37:17.510 align:start position:0% communication so just imagine that the satellite<02:37:15.660> uh<02:37:16.260> for<02:37:16.620> your<02:37:16.800> television<02:37:17.160> for 02:37:17.510 --> 02:37:17.520 align:start position:0% satellite uh for your television for 02:37:17.520 --> 02:37:19.610 align:start position:0% satellite uh for your television for instance<02:37:17.760> if<02:37:18.359> our<02:37:18.600> satellite<02:37:18.960> dish<02:37:19.200> at<02:37:19.439> home 02:37:19.610 --> 02:37:19.620 align:start position:0% instance if our satellite dish at home 02:37:19.620 --> 02:37:21.170 align:start position:0% instance if our satellite dish at home doesn't<02:37:19.920> have<02:37:20.160> a<02:37:20.340> clear<02:37:20.399> line<02:37:20.700> to<02:37:21.000> the 02:37:21.170 --> 02:37:21.180 align:start position:0% doesn't have a clear line to the 02:37:21.180 --> 02:37:23.389 align:start position:0% doesn't have a clear line to the satellite<02:37:21.479> in<02:37:21.780> the<02:37:21.899> sky<02:37:22.080> we<02:37:22.920> see<02:37:23.100> that<02:37:23.280> it's 02:37:23.389 --> 02:37:23.399 align:start position:0% satellite in the sky we see that it's 02:37:23.399 --> 02:37:26.030 align:start position:0% satellite in the sky we see that it's signal<02:37:23.700> to<02:37:23.880> grade<02:37:24.180> or<02:37:25.020> drop<02:37:25.319> off<02:37:25.500> altogether 02:37:26.030 --> 02:37:26.040 align:start position:0% signal to grade or drop off altogether 02:37:26.040 --> 02:37:28.910 align:start position:0% signal to grade or drop off altogether so<02:37:26.460> obstructions<02:37:27.120> such<02:37:27.300> as<02:37:27.540> buildings<02:37:28.439> uh 02:37:28.910 --> 02:37:28.920 align:start position:0% so obstructions such as buildings uh 02:37:28.920 --> 02:37:31.610 align:start position:0% so obstructions such as buildings uh trees<02:37:29.399> even<02:37:30.060> atmospheric<02:37:30.899> conditions<02:37:31.380> like 02:37:31.610 --> 02:37:31.620 align:start position:0% trees even atmospheric conditions like 02:37:31.620 --> 02:37:34.490 align:start position:0% trees even atmospheric conditions like rain<02:37:32.280> Etc<02:37:32.399> can<02:37:33.060> all<02:37:33.300> play<02:37:33.479> a<02:37:33.780> major<02:37:33.960> factor<02:37:34.380> in 02:37:34.490 --> 02:37:34.500 align:start position:0% rain Etc can all play a major factor in 02:37:34.500 --> 02:37:36.650 align:start position:0% rain Etc can all play a major factor in microwave<02:37:34.979> Transmissions<02:37:35.640> one<02:37:36.479> of<02:37:36.600> the 02:37:36.650 --> 02:37:36.660 align:start position:0% microwave Transmissions one of the 02:37:36.660 --> 02:37:38.570 align:start position:0% microwave Transmissions one of the greatest<02:37:36.840> benefits<02:37:37.680> of<02:37:38.160> microwave 02:37:38.570 --> 02:37:38.580 align:start position:0% greatest benefits of microwave 02:37:38.580 --> 02:37:40.790 align:start position:0% greatest benefits of microwave Transmissions<02:37:39.120> is<02:37:39.300> it<02:37:39.540> has<02:37:39.720> a<02:37:40.260> really<02:37:40.439> long 02:37:40.790 --> 02:37:40.800 align:start position:0% Transmissions is it has a really long 02:37:40.800 --> 02:37:42.590 align:start position:0% Transmissions is it has a really long range<02:37:41.220> of<02:37:41.340> communication<02:37:41.880> as<02:37:42.420> you<02:37:42.540> can 02:37:42.590 --> 02:37:42.600 align:start position:0% range of communication as you can 02:37:42.600 --> 02:37:43.670 align:start position:0% range of communication as you can imagine 02:37:43.670 --> 02:37:43.680 align:start position:0% imagine 02:37:43.680 --> 02:37:47.690 align:start position:0% imagine uh<02:37:44.520> uh<02:37:45.180> your<02:37:46.020> satellite<02:37:46.620> at<02:37:46.920> home<02:37:47.100> can<02:37:47.399> reach 02:37:47.690 --> 02:37:47.700 align:start position:0% uh uh your satellite at home can reach 02:37:47.700 --> 02:37:49.429 align:start position:0% uh uh your satellite at home can reach all<02:37:47.819> the<02:37:47.939> way<02:37:48.000> up<02:37:48.120> to<02:37:48.300> the<02:37:48.420> sky<02:37:48.540> and<02:37:48.840> hit<02:37:49.080> that 02:37:49.429 --> 02:37:49.439 align:start position:0% all the way up to the sky and hit that 02:37:49.439 --> 02:37:51.830 align:start position:0% all the way up to the sky and hit that uh<02:37:49.920> satellite<02:37:50.340> in<02:37:50.520> the<02:37:50.700> sky<02:37:50.819> or<02:37:51.120> rather<02:37:51.420> your 02:37:51.830 --> 02:37:51.840 align:start position:0% uh satellite in the sky or rather your 02:37:51.840 --> 02:37:53.330 align:start position:0% uh satellite in the sky or rather your receiver<02:37:52.319> at<02:37:52.560> home<02:37:52.680> or<02:37:52.800> your<02:37:52.920> dish<02:37:53.100> at<02:37:53.280> home 02:37:53.330 --> 02:37:53.340 align:start position:0% receiver at home or your dish at home 02:37:53.340 --> 02:37:55.610 align:start position:0% receiver at home or your dish at home can<02:37:53.640> reach<02:37:53.939> that<02:37:54.120> satellite<02:37:54.479> in<02:37:54.720> the<02:37:54.840> sky<02:37:55.020> and 02:37:55.610 --> 02:37:55.620 align:start position:0% can reach that satellite in the sky and 02:37:55.620 --> 02:37:57.530 align:start position:0% can reach that satellite in the sky and so<02:37:55.740> there's<02:37:55.920> a<02:37:56.220> real<02:37:56.340> strong<02:37:56.580> benefit<02:37:56.880> to<02:37:57.359> the 02:37:57.530 --> 02:37:57.540 align:start position:0% so there's a real strong benefit to the 02:37:57.540 --> 02:38:00.170 align:start position:0% so there's a real strong benefit to the satellite<02:37:58.020> microwave<02:37:58.620> Transmissions 02:38:00.170 --> 02:38:00.180 align:start position:0% satellite microwave Transmissions 02:38:00.180 --> 02:38:02.090 align:start position:0% satellite microwave Transmissions now<02:38:00.960> the<02:38:01.319> one<02:38:01.439> you're<02:38:01.680> probably<02:38:01.859> most 02:38:02.090 --> 02:38:02.100 align:start position:0% now the one you're probably most 02:38:02.100 --> 02:38:03.830 align:start position:0% now the one you're probably most familiar<02:38:02.460> with<02:38:02.580> here<02:38:02.819> is<02:38:03.000> a<02:38:03.180> wireless<02:38:03.359> access 02:38:03.830 --> 02:38:03.840 align:start position:0% familiar with here is a wireless access 02:38:03.840 --> 02:38:07.190 align:start position:0% familiar with here is a wireless access point<02:38:04.260> which<02:38:04.560> is<02:38:04.680> a<02:38:05.100> radio<02:38:05.460> uh<02:38:06.359> a<02:38:06.660> type<02:38:07.080> of 02:38:07.190 --> 02:38:07.200 align:start position:0% point which is a radio uh a type of 02:38:07.200 --> 02:38:09.830 align:start position:0% point which is a radio uh a type of radio<02:38:07.439> frequency<02:38:08.100> device<02:38:08.880> it<02:38:09.540> allows 02:38:09.830 --> 02:38:09.840 align:start position:0% radio frequency device it allows 02:38:09.840 --> 02:38:10.809 align:start position:0% radio frequency device it allows wireless 02:38:10.809 --> 02:38:10.819 align:start position:0% wireless 02:38:10.819 --> 02:38:15.530 align:start position:0% wireless devices<02:38:11.819> to<02:38:12.780> connect<02:38:13.080> to<02:38:13.620> a<02:38:13.979> network<02:38:14.160> it<02:38:15.060> has<02:38:15.240> a 02:38:15.530 --> 02:38:15.540 align:start position:0% devices to connect to a network it has a 02:38:15.540 --> 02:38:17.150 align:start position:0% devices to connect to a network it has a network<02:38:15.780> interface<02:38:16.319> that<02:38:16.620> allows<02:38:16.859> it<02:38:16.979> to 02:38:17.150 --> 02:38:17.160 align:start position:0% network interface that allows it to 02:38:17.160 --> 02:38:19.849 align:start position:0% network interface that allows it to connect<02:38:17.340> to<02:38:17.640> a<02:38:18.120> wired<02:38:18.540> Network<02:38:18.720> as<02:38:19.140> well<02:38:19.260> so 02:38:19.849 --> 02:38:19.859 align:start position:0% connect to a wired Network as well so 02:38:19.859 --> 02:38:22.849 align:start position:0% connect to a wired Network as well so generally<02:38:20.280> speaking<02:38:20.819> this<02:38:21.600> would<02:38:21.899> go<02:38:22.080> off<02:38:22.319> to 02:38:22.849 --> 02:38:22.859 align:start position:0% generally speaking this would go off to 02:38:22.859 --> 02:38:25.429 align:start position:0% generally speaking this would go off to say<02:38:23.399> a<02:38:23.520> switch<02:38:23.700> or<02:38:23.939> a<02:38:24.120> router<02:38:24.479> now<02:38:24.960> how<02:38:25.140> do<02:38:25.260> we 02:38:25.429 --> 02:38:25.439 align:start position:0% say a switch or a router now how do we 02:38:25.439 --> 02:38:27.230 align:start position:0% say a switch or a router now how do we know<02:38:25.620> which<02:38:26.160> wireless<02:38:26.340> access<02:38:26.640> point<02:38:26.939> we<02:38:27.120> want 02:38:27.230 --> 02:38:27.240 align:start position:0% know which wireless access point we want 02:38:27.240 --> 02:38:29.510 align:start position:0% know which wireless access point we want to<02:38:27.359> connect<02:38:27.479> to<02:38:27.780> this<02:38:28.380> is<02:38:28.500> something<02:38:28.740> this<02:38:29.399> is 02:38:29.510 --> 02:38:29.520 align:start position:0% to connect to this is something this is 02:38:29.520 --> 02:38:30.830 align:start position:0% to connect to this is something this is where<02:38:29.700> we<02:38:29.819> get<02:38:29.939> into<02:38:30.060> something<02:38:30.300> called<02:38:30.600> an 02:38:30.830 --> 02:38:30.840 align:start position:0% where we get into something called an 02:38:30.840 --> 02:38:33.950 align:start position:0% where we get into something called an SSID<02:38:32.060> and<02:38:33.060> there<02:38:33.240> are<02:38:33.359> also<02:38:33.540> other<02:38:33.660> settings 02:38:33.950 --> 02:38:33.960 align:start position:0% SSID and there are also other settings 02:38:33.960 --> 02:38:35.990 align:start position:0% SSID and there are also other settings that<02:38:34.319> we<02:38:34.500> need<02:38:34.620> to<02:38:34.859> take<02:38:35.100> care<02:38:35.460> of<02:38:35.580> when<02:38:35.819> we're 02:38:35.990 --> 02:38:36.000 align:start position:0% that we need to take care of when we're 02:38:36.000 --> 02:38:37.730 align:start position:0% that we need to take care of when we're setting<02:38:36.300> one<02:38:36.420> of<02:38:36.540> these<02:38:36.720> up<02:38:36.899> so<02:38:37.439> first<02:38:37.560> let's 02:38:37.730 --> 02:38:37.740 align:start position:0% setting one of these up so first let's 02:38:37.740 --> 02:38:40.250 align:start position:0% setting one of these up so first let's talk<02:38:37.920> about<02:38:38.040> the<02:38:38.340> SSID<02:38:38.819> or<02:38:39.300> service<02:38:39.720> set 02:38:40.250 --> 02:38:40.260 align:start position:0% talk about the SSID or service set 02:38:40.260 --> 02:38:43.630 align:start position:0% talk about the SSID or service set identifier<02:38:41.160> which<02:38:41.460> is<02:38:41.640> a<02:38:41.939> up<02:38:42.300> to<02:38:42.479> a<02:38:42.720> 32-bit 02:38:43.630 --> 02:38:43.640 align:start position:0% identifier which is a up to a 32-bit 02:38:43.640 --> 02:38:47.330 align:start position:0% identifier which is a up to a 32-bit alphanumeric<02:38:44.640> string<02:38:45.140> and<02:38:46.140> it<02:38:46.680> identifies 02:38:47.330 --> 02:38:47.340 align:start position:0% alphanumeric string and it identifies 02:38:47.340 --> 02:38:50.630 align:start position:0% alphanumeric string and it identifies the<02:38:48.120> name<02:38:48.420> of<02:38:48.899> your<02:38:49.200> wireless<02:38:49.439> access<02:38:50.040> point 02:38:50.630 --> 02:38:50.640 align:start position:0% the name of your wireless access point 02:38:50.640 --> 02:38:53.389 align:start position:0% the name of your wireless access point so<02:38:51.420> in<02:38:51.720> some<02:38:51.840> ways<02:38:52.140> we<02:38:52.319> might<02:38:52.439> call<02:38:52.680> this<02:38:52.920> the 02:38:53.389 --> 02:38:53.399 align:start position:0% so in some ways we might call this the 02:38:53.399 --> 02:38:55.550 align:start position:0% so in some ways we might call this the name<02:38:53.580> of<02:38:53.819> your<02:38:54.000> network<02:38:54.240> right<02:38:55.140> out<02:38:55.319> of<02:38:55.439> the 02:38:55.550 --> 02:38:55.560 align:start position:0% name of your network right out of the 02:38:55.560 --> 02:38:56.389 align:start position:0% name of your network right out of the box 02:38:56.389 --> 02:38:56.399 align:start position:0% box 02:38:56.399 --> 02:38:59.330 align:start position:0% box when<02:38:56.939> you<02:38:57.120> just<02:38:57.300> set<02:38:57.540> it<02:38:57.720> up<02:38:57.899> the<02:38:58.680> access<02:38:58.920> point 02:38:59.330 --> 02:38:59.340 align:start position:0% when you just set it up the access point 02:38:59.340 --> 02:39:01.030 align:start position:0% when you just set it up the access point is<02:38:59.580> going<02:38:59.760> to<02:38:59.880> do<02:39:00.000> what<02:39:00.120> we<02:39:00.300> call<02:39:00.420> broadcast 02:39:01.030 --> 02:39:01.040 align:start position:0% is going to do what we call broadcast 02:39:01.040 --> 02:39:04.130 align:start position:0% is going to do what we call broadcast your<02:39:02.040> SSID<02:39:02.640> this<02:39:03.540> means<02:39:03.780> that<02:39:03.899> it's 02:39:04.130 --> 02:39:04.140 align:start position:0% your SSID this means that it's 02:39:04.140 --> 02:39:06.650 align:start position:0% your SSID this means that it's transmitting<02:39:04.800> the<02:39:05.040> name<02:39:05.160> of<02:39:05.340> the<02:39:05.520> network<02:39:05.660> uh 02:39:06.650 --> 02:39:06.660 align:start position:0% transmitting the name of the network uh 02:39:06.660 --> 02:39:08.870 align:start position:0% transmitting the name of the network uh into<02:39:06.960> clear<02:39:07.380> text<02:39:07.680> so<02:39:08.040> that<02:39:08.160> anyone<02:39:08.580> who's 02:39:08.870 --> 02:39:08.880 align:start position:0% into clear text so that anyone who's 02:39:08.880 --> 02:39:11.330 align:start position:0% into clear text so that anyone who's within<02:39:09.300> range<02:39:09.600> can<02:39:09.899> see<02:39:10.140> it<02:39:10.260> if<02:39:10.740> you<02:39:10.859> live<02:39:10.979> in<02:39:11.160> a 02:39:11.330 --> 02:39:11.340 align:start position:0% within range can see it if you live in a 02:39:11.340 --> 02:39:13.010 align:start position:0% within range can see it if you live in a building<02:39:11.520> or<02:39:11.939> if<02:39:12.180> you're<02:39:12.359> in<02:39:12.479> an<02:39:12.600> office<02:39:12.720> space 02:39:13.010 --> 02:39:13.020 align:start position:0% building or if you're in an office space 02:39:13.020 --> 02:39:14.990 align:start position:0% building or if you're in an office space you've<02:39:13.380> probably<02:39:13.500> seen<02:39:13.740> this<02:39:14.040> so<02:39:14.760> This 02:39:14.990 --> 02:39:15.000 align:start position:0% you've probably seen this so This 02:39:15.000 --> 02:39:16.730 align:start position:0% you've probably seen this so This creates<02:39:15.300> a<02:39:15.540> vulnerability<02:39:16.200> on<02:39:16.500> the<02:39:16.620> network 02:39:16.730 --> 02:39:16.740 align:start position:0% creates a vulnerability on the network 02:39:16.740 --> 02:39:18.290 align:start position:0% creates a vulnerability on the network especially<02:39:17.340> if<02:39:17.520> you<02:39:17.640> want<02:39:17.760> to<02:39:17.880> limit<02:39:18.060> the 02:39:18.290 --> 02:39:18.300 align:start position:0% especially if you want to limit the 02:39:18.300 --> 02:39:20.510 align:start position:0% especially if you want to limit the number<02:39:18.479> of<02:39:18.660> users<02:39:19.200> that<02:39:19.979> are<02:39:20.160> trying<02:39:20.399> to 02:39:20.510 --> 02:39:20.520 align:start position:0% number of users that are trying to 02:39:20.520 --> 02:39:22.490 align:start position:0% number of users that are trying to access<02:39:20.760> your<02:39:21.120> network<02:39:21.300> so<02:39:22.020> with<02:39:22.319> your 02:39:22.490 --> 02:39:22.500 align:start position:0% access your network so with your 02:39:22.500 --> 02:39:24.650 align:start position:0% access your network so with your wireless<02:39:22.740> access<02:39:23.220> point<02:39:23.700> there<02:39:24.359> are<02:39:24.479> a<02:39:24.540> few 02:39:24.650 --> 02:39:24.660 align:start position:0% wireless access point there are a few 02:39:24.660 --> 02:39:27.650 align:start position:0% wireless access point there are a few steps<02:39:25.080> to<02:39:25.260> make<02:39:25.500> to<02:39:25.979> ensure<02:39:26.580> that<02:39:27.359> we're<02:39:27.540> going 02:39:27.650 --> 02:39:27.660 align:start position:0% steps to make to ensure that we're going 02:39:27.660 --> 02:39:29.990 align:start position:0% steps to make to ensure that we're going to<02:39:27.780> install<02:39:27.899> this<02:39:28.319> correctly<02:39:28.740> uh<02:39:29.340> safely<02:39:29.760> and 02:39:29.990 --> 02:39:30.000 align:start position:0% to install this correctly uh safely and 02:39:30.000 --> 02:39:32.090 align:start position:0% to install this correctly uh safely and efficiently<02:39:30.540> so<02:39:31.200> the<02:39:31.439> first<02:39:31.560> thing<02:39:31.800> we<02:39:31.979> want 02:39:32.090 --> 02:39:32.100 align:start position:0% efficiently so the first thing we want 02:39:32.100 --> 02:39:34.969 align:start position:0% efficiently so the first thing we want to<02:39:32.280> do<02:39:32.460> is<02:39:33.000> to<02:39:33.180> choose<02:39:33.420> the<02:39:33.720> proper<02:39:34.080> device<02:39:34.380> for 02:39:34.969 --> 02:39:34.979 align:start position:0% to do is to choose the proper device for 02:39:34.979 --> 02:39:37.250 align:start position:0% to do is to choose the proper device for your<02:39:35.160> needs<02:39:35.460> obviously<02:39:36.180> there<02:39:36.840> are<02:39:37.020> different 02:39:37.250 --> 02:39:37.260 align:start position:0% your needs obviously there are different 02:39:37.260 --> 02:39:39.110 align:start position:0% your needs obviously there are different types<02:39:37.740> of<02:39:37.800> access<02:39:38.040> points<02:39:38.640> if<02:39:38.880> you<02:39:39.000> were 02:39:39.110 --> 02:39:39.120 align:start position:0% types of access points if you were 02:39:39.120 --> 02:39:41.090 align:start position:0% types of access points if you were around<02:39:39.240> for<02:39:39.479> a<02:39:39.660> plus<02:39:39.899> we<02:39:40.439> talked<02:39:40.740> about<02:39:40.800> what 02:39:41.090 --> 02:39:41.100 align:start position:0% around for a plus we talked about what 02:39:41.100 --> 02:39:43.670 align:start position:0% around for a plus we talked about what are<02:39:41.220> called<02:39:41.399> Soho<02:39:42.359> routers<02:39:42.840> or<02:39:43.080> Soho<02:39:43.500> access 02:39:43.670 --> 02:39:43.680 align:start position:0% are called Soho routers or Soho access 02:39:43.680 --> 02:39:45.650 align:start position:0% are called Soho routers or Soho access points<02:39:44.100> which<02:39:44.220> also<02:39:44.520> have<02:39:44.700> routers<02:39:45.240> in<02:39:45.479> them 02:39:45.650 --> 02:39:45.660 align:start position:0% points which also have routers in them 02:39:45.660 --> 02:39:47.630 align:start position:0% points which also have routers in them but<02:39:46.140> an<02:39:46.260> access<02:39:46.439> point<02:39:46.740> simply<02:39:47.160> is<02:39:47.340> the<02:39:47.520> device 02:39:47.630 --> 02:39:47.640 align:start position:0% but an access point simply is the device 02:39:47.640 --> 02:39:50.330 align:start position:0% but an access point simply is the device that's<02:39:48.000> connecting<02:39:48.479> you<02:39:48.720> wirelessly<02:39:49.380> to<02:39:50.100> your 02:39:50.330 --> 02:39:50.340 align:start position:0% that's connecting you wirelessly to your 02:39:50.340 --> 02:39:51.770 align:start position:0% that's connecting you wirelessly to your network<02:39:50.520> now<02:39:51.000> if<02:39:51.060> you<02:39:51.180> have<02:39:51.300> a<02:39:51.479> corporate 02:39:51.770 --> 02:39:51.780 align:start position:0% network now if you have a corporate 02:39:51.780 --> 02:39:53.270 align:start position:0% network now if you have a corporate environment<02:39:52.140> or<02:39:52.439> a<02:39:52.560> home<02:39:52.680> office<02:39:52.920> Network 02:39:53.270 --> 02:39:53.280 align:start position:0% environment or a home office Network 02:39:53.280 --> 02:39:55.730 align:start position:0% environment or a home office Network you're<02:39:53.819> going<02:39:54.000> to<02:39:54.120> need<02:39:54.300> different<02:39:54.600> things<02:39:55.020> so 02:39:55.730 --> 02:39:55.740 align:start position:0% you're going to need different things so 02:39:55.740 --> 02:39:57.290 align:start position:0% you're going to need different things so the<02:39:55.920> next<02:39:55.979> thing<02:39:56.160> one<02:39:56.340> once<02:39:56.819> you've<02:39:56.939> decided 02:39:57.290 --> 02:39:57.300 align:start position:0% the next thing one once you've decided 02:39:57.300 --> 02:39:59.030 align:start position:0% the next thing one once you've decided which<02:39:57.540> device<02:39:57.840> you<02:39:58.200> want<02:39:58.319> we<02:39:58.560> then<02:39:58.740> have<02:39:58.920> to 02:39:59.030 --> 02:39:59.040 align:start position:0% which device you want we then have to 02:39:59.040 --> 02:40:01.849 align:start position:0% which device you want we then have to talk<02:39:59.220> about<02:39:59.399> where<02:39:59.939> we<02:40:00.120> want<02:40:00.240> to<02:40:00.420> place<02:40:00.660> it<02:40:00.899> and 02:40:01.849 --> 02:40:01.859 align:start position:0% talk about where we want to place it and 02:40:01.859 --> 02:40:03.770 align:start position:0% talk about where we want to place it and specifically<02:40:02.340> we<02:40:02.580> need<02:40:02.700> to<02:40:02.880> ensure<02:40:03.180> that<02:40:03.540> our 02:40:03.770 --> 02:40:03.780 align:start position:0% specifically we need to ensure that our 02:40:03.780 --> 02:40:06.230 align:start position:0% specifically we need to ensure that our users<02:40:04.140> can<02:40:04.560> access<02:40:04.920> the<02:40:05.399> network<02:40:05.580> from<02:40:06.000> all 02:40:06.230 --> 02:40:06.240 align:start position:0% users can access the network from all 02:40:06.240 --> 02:40:08.330 align:start position:0% users can access the network from all the<02:40:06.420> places<02:40:06.600> they<02:40:06.960> need<02:40:07.140> to<02:40:07.319> which<02:40:07.859> is<02:40:08.040> just<02:40:08.160> as 02:40:08.330 --> 02:40:08.340 align:start position:0% the places they need to which is just as 02:40:08.340 --> 02:40:10.130 align:start position:0% the places they need to which is just as important<02:40:08.640> as<02:40:08.819> considering<02:40:09.180> which<02:40:09.420> users<02:40:09.960> we 02:40:10.130 --> 02:40:10.140 align:start position:0% important as considering which users we 02:40:10.140 --> 02:40:11.750 align:start position:0% important as considering which users we don't<02:40:10.319> want<02:40:10.439> to<02:40:10.560> be<02:40:10.680> able<02:40:10.800> to<02:40:10.920> connect<02:40:11.040> so<02:40:11.580> we 02:40:11.750 --> 02:40:11.760 align:start position:0% don't want to be able to connect so we 02:40:11.760 --> 02:40:13.010 align:start position:0% don't want to be able to connect so we want<02:40:11.880> to<02:40:12.000> be<02:40:12.060> able<02:40:12.180> to<02:40:12.300> place<02:40:12.420> it<02:40:12.660> in<02:40:12.780> a<02:40:12.899> place 02:40:13.010 --> 02:40:13.020 align:start position:0% want to be able to place it in a place 02:40:13.020 --> 02:40:16.610 align:start position:0% want to be able to place it in a place that<02:40:13.319> is<02:40:13.500> of<02:40:13.979> course<02:40:14.100> Central<02:40:14.520> but<02:40:15.420> also<02:40:15.899> is 02:40:16.610 --> 02:40:16.620 align:start position:0% that is of course Central but also is 02:40:16.620 --> 02:40:19.010 align:start position:0% that is of course Central but also is limiting<02:40:17.340> or<02:40:17.939> Limited<02:40:18.479> in<02:40:18.600> the<02:40:18.780> amount<02:40:18.960> of 02:40:19.010 --> 02:40:19.020 align:start position:0% limiting or Limited in the amount of 02:40:19.020 --> 02:40:20.330 align:start position:0% limiting or Limited in the amount of people<02:40:19.140> who<02:40:19.380> are<02:40:19.439> going<02:40:19.560> to<02:40:19.680> connect<02:40:19.800> to<02:40:20.040> it<02:40:20.160> if 02:40:20.330 --> 02:40:20.340 align:start position:0% people who are going to connect to it if 02:40:20.340 --> 02:40:21.410 align:start position:0% people who are going to connect to it if you<02:40:20.460> put<02:40:20.580> it<02:40:20.640> near<02:40:20.760> a<02:40:20.939> window<02:40:21.060> for<02:40:21.300> instance 02:40:21.410 --> 02:40:21.420 align:start position:0% you put it near a window for instance 02:40:21.420 --> 02:40:22.910 align:start position:0% you put it near a window for instance our<02:40:21.660> next<02:40:21.840> door<02:40:21.960> neighbor<02:40:22.200> might<02:40:22.560> be<02:40:22.620> able<02:40:22.800> to 02:40:22.910 --> 02:40:22.920 align:start position:0% our next door neighbor might be able to 02:40:22.920 --> 02:40:24.710 align:start position:0% our next door neighbor might be able to connect<02:40:23.399> now<02:40:23.819> almost<02:40:24.000> immediately<02:40:24.540> after 02:40:24.710 --> 02:40:24.720 align:start position:0% connect now almost immediately after 02:40:24.720 --> 02:40:27.770 align:start position:0% connect now almost immediately after bringing<02:40:25.200> the<02:40:25.700> whapper<02:40:26.700> the<02:40:27.000> wireless<02:40:27.420> access 02:40:27.770 --> 02:40:27.780 align:start position:0% bringing the whapper the wireless access 02:40:27.780 --> 02:40:29.929 align:start position:0% bringing the whapper the wireless access point<02:40:28.200> out<02:40:28.380> of<02:40:28.500> the<02:40:28.620> box<02:40:28.740> we<02:40:29.520> want<02:40:29.640> to<02:40:29.819> change 02:40:29.929 --> 02:40:29.939 align:start position:0% point out of the box we want to change 02:40:29.939 --> 02:40:32.510 align:start position:0% point out of the box we want to change the<02:40:30.240> administrative<02:40:30.840> default<02:40:31.439> password 02:40:32.510 --> 02:40:32.520 align:start position:0% the administrative default password 02:40:32.520 --> 02:40:34.969 align:start position:0% the administrative default password so<02:40:33.180> and<02:40:33.479> disable<02:40:33.840> any<02:40:34.080> guest<02:40:34.380> accounts<02:40:34.800> this 02:40:34.969 --> 02:40:34.979 align:start position:0% so and disable any guest accounts this 02:40:34.979 --> 02:40:36.469 align:start position:0% so and disable any guest accounts this means<02:40:35.280> that<02:40:35.399> all<02:40:35.580> these<02:40:35.760> settings<02:40:35.939> that<02:40:36.359> we're 02:40:36.469 --> 02:40:36.479 align:start position:0% means that all these settings that we're 02:40:36.479 --> 02:40:39.410 align:start position:0% means that all these settings that we're talking<02:40:36.720> about<02:40:37.100> uh<02:40:38.100> you<02:40:38.520> need<02:40:38.640> a<02:40:38.819> password<02:40:39.120> to 02:40:39.410 --> 02:40:39.420 align:start position:0% talking about uh you need a password to 02:40:39.420 --> 02:40:40.730 align:start position:0% talking about uh you need a password to be<02:40:39.479> able<02:40:39.600> to<02:40:39.720> get<02:40:39.780> in<02:40:39.899> and<02:40:40.020> change<02:40:40.260> them<02:40:40.439> so<02:40:40.620> we 02:40:40.730 --> 02:40:40.740 align:start position:0% be able to get in and change them so we 02:40:40.740 --> 02:40:43.550 align:start position:0% be able to get in and change them so we want<02:40:40.920> to<02:40:41.040> change<02:40:41.340> that<02:40:41.819> or<02:40:42.420> disable<02:40:42.899> the<02:40:43.380> guest 02:40:43.550 --> 02:40:43.560 align:start position:0% want to change that or disable the guest 02:40:43.560 --> 02:40:46.010 align:start position:0% want to change that or disable the guest account<02:40:43.800> change<02:40:44.340> that<02:40:44.700> and<02:40:45.180> we<02:40:45.600> also<02:40:45.780> want<02:40:45.899> to 02:40:46.010 --> 02:40:46.020 align:start position:0% account change that and we also want to 02:40:46.020 --> 02:40:47.570 align:start position:0% account change that and we also want to make<02:40:46.080> sure<02:40:46.200> there<02:40:46.380> are<02:40:46.560> no<02:40:46.620> other<02:40:46.800> backdoor 02:40:47.570 --> 02:40:47.580 align:start position:0% make sure there are no other backdoor 02:40:47.580 --> 02:40:48.830 align:start position:0% make sure there are no other backdoor accounts 02:40:48.830 --> 02:40:48.840 align:start position:0% accounts 02:40:48.840 --> 02:40:50.210 align:start position:0% accounts um<02:40:48.899> you<02:40:49.140> can<02:40:49.260> generally<02:40:49.500> check<02:40:49.740> in<02:40:49.979> your 02:40:50.210 --> 02:40:50.220 align:start position:0% um you can generally check in your 02:40:50.220 --> 02:40:53.030 align:start position:0% um you can generally check in your administrative<02:40:50.880> sort<02:40:51.660> of<02:40:52.080> um<02:40:52.080> manual<02:40:52.680> to<02:40:52.920> see 02:40:53.030 --> 02:40:53.040 align:start position:0% administrative sort of um manual to see 02:40:53.040 --> 02:40:54.830 align:start position:0% administrative sort of um manual to see if<02:40:53.160> there's<02:40:53.280> anything<02:40:53.460> like<02:40:53.939> that<02:40:54.180> so<02:40:54.660> that 02:40:54.830 --> 02:40:54.840 align:start position:0% if there's anything like that so that 02:40:54.840 --> 02:40:56.210 align:start position:0% if there's anything like that so that way<02:40:54.960> we<02:40:55.080> don't<02:40:55.200> have<02:40:55.380> any<02:40:55.500> unauthorized 02:40:56.210 --> 02:40:56.220 align:start position:0% way we don't have any unauthorized 02:40:56.220 --> 02:40:58.190 align:start position:0% way we don't have any unauthorized access<02:40:56.580> to<02:40:57.000> the<02:40:57.120> account 02:40:58.190 --> 02:40:58.200 align:start position:0% access to the account 02:40:58.200 --> 02:41:00.349 align:start position:0% access to the account next<02:40:59.100> thing<02:40:59.220> we<02:40:59.399> want<02:40:59.520> to<02:40:59.640> do<02:40:59.700> is<02:40:59.880> configure 02:41:00.349 --> 02:41:00.359 align:start position:0% next thing we want to do is configure 02:41:00.359 --> 02:41:02.870 align:start position:0% next thing we want to do is configure these<02:41:00.899> wireless<02:41:01.500> access<02:41:02.040> point<02:41:02.520> settings 02:41:02.870 --> 02:41:02.880 align:start position:0% these wireless access point settings 02:41:02.880 --> 02:41:05.389 align:start position:0% these wireless access point settings including<02:41:03.600> the<02:41:03.780> SSID<02:41:04.319> what<02:41:04.859> encryption<02:41:05.220> we're 02:41:05.389 --> 02:41:05.399 align:start position:0% including the SSID what encryption we're 02:41:05.399 --> 02:41:08.750 align:start position:0% including the SSID what encryption we're using<02:41:05.760> power<02:41:06.359> and<02:41:06.660> so<02:41:06.899> on 02:41:08.750 --> 02:41:08.760 align:start position:0% using power and so on 02:41:08.760 --> 02:41:11.270 align:start position:0% using power and so on we'll<02:41:09.240> talk<02:41:09.420> about<02:41:09.600> encryption<02:41:10.319> and<02:41:10.800> in 02:41:11.270 --> 02:41:11.280 align:start position:0% we'll talk about encryption and in 02:41:11.280 --> 02:41:14.990 align:start position:0% we'll talk about encryption and in further<02:41:11.640> detail<02:41:12.140> in<02:41:13.140> later<02:41:13.439> uh<02:41:13.920> lessons<02:41:14.460> so 02:41:14.990 --> 02:41:15.000 align:start position:0% further detail in later uh lessons so 02:41:15.000 --> 02:41:19.370 align:start position:0% further detail in later uh lessons so don't<02:41:15.120> worry<02:41:15.420> about<02:41:15.660> that<02:41:15.899> so<02:41:16.080> much<02:41:16.260> right<02:41:16.439> now 02:41:19.370 --> 02:41:19.380 align:start position:0% 02:41:19.380 --> 02:41:21.650 align:start position:0% figurations<02:41:19.979> have<02:41:20.340> been<02:41:20.520> set<02:41:20.760> we<02:41:21.180> also<02:41:21.420> want 02:41:21.650 --> 02:41:21.660 align:start position:0% figurations have been set we also want 02:41:21.660 --> 02:41:24.050 align:start position:0% figurations have been set we also want to<02:41:21.960> disable<02:41:22.500> as<02:41:22.800> we've<02:41:22.979> mentioned<02:41:23.340> the<02:41:23.520> SSID 02:41:24.050 --> 02:41:24.060 align:start position:0% to disable as we've mentioned the SSID 02:41:24.060 --> 02:41:25.429 align:start position:0% to disable as we've mentioned the SSID this<02:41:24.600> doesn't<02:41:24.720> mean<02:41:24.899> that<02:41:25.020> users<02:41:25.319> aren't 02:41:25.429 --> 02:41:25.439 align:start position:0% this doesn't mean that users aren't 02:41:25.439 --> 02:41:26.870 align:start position:0% this doesn't mean that users aren't going<02:41:25.620> to<02:41:25.680> be<02:41:25.800> able<02:41:25.859> to<02:41:26.040> connect<02:41:26.340> to<02:41:26.760> the 02:41:26.870 --> 02:41:26.880 align:start position:0% going to be able to connect to the 02:41:26.880 --> 02:41:29.150 align:start position:0% going to be able to connect to the network<02:41:27.000> by<02:41:27.359> the<02:41:27.479> way<02:41:27.540> it<02:41:27.840> just<02:41:28.140> means<02:41:28.439> that<02:41:28.620> if 02:41:29.150 --> 02:41:29.160 align:start position:0% network by the way it just means that if 02:41:29.160 --> 02:41:31.610 align:start position:0% network by the way it just means that if you're<02:41:29.399> looking<02:41:29.700> for<02:41:30.660> available<02:41:31.080> wireless 02:41:31.610 --> 02:41:31.620 align:start position:0% you're looking for available wireless 02:41:31.620 --> 02:41:34.490 align:start position:0% you're looking for available wireless networks<02:41:32.220> it's<02:41:32.520> not<02:41:32.819> going<02:41:33.060> to<02:41:33.359> be<02:41:33.780> uh 02:41:34.490 --> 02:41:34.500 align:start position:0% networks it's not going to be uh 02:41:34.500 --> 02:41:36.290 align:start position:0% networks it's not going to be uh broadcast<02:41:34.800> out<02:41:35.460> there<02:41:35.580> so<02:41:36.000> in<02:41:36.060> other<02:41:36.180> words 02:41:36.290 --> 02:41:36.300 align:start position:0% broadcast out there so in other words 02:41:36.300 --> 02:41:38.030 align:start position:0% broadcast out there so in other words you<02:41:36.660> need<02:41:36.780> to<02:41:36.960> know<02:41:37.080> the<02:41:37.380> name<02:41:37.500> in<02:41:37.680> order<02:41:37.800> to 02:41:38.030 --> 02:41:38.040 align:start position:0% you need to know the name in order to 02:41:38.040 --> 02:41:39.770 align:start position:0% you need to know the name in order to find<02:41:38.160> it<02:41:38.280> it's<02:41:38.520> sort<02:41:38.760> of<02:41:38.880> like<02:41:39.060> a<02:41:39.359> door<02:41:39.479> that's 02:41:39.770 --> 02:41:39.780 align:start position:0% find it it's sort of like a door that's 02:41:39.780 --> 02:41:41.750 align:start position:0% find it it's sort of like a door that's hidden<02:41:40.140> in<02:41:40.319> the<02:41:40.439> wall<02:41:40.620> if<02:41:41.280> you<02:41:41.340> know<02:41:41.460> where<02:41:41.640> the 02:41:41.750 --> 02:41:41.760 align:start position:0% hidden in the wall if you know where the 02:41:41.760 --> 02:41:43.730 align:start position:0% hidden in the wall if you know where the door<02:41:41.939> is<02:41:42.180> you<02:41:42.420> can<02:41:42.540> find<02:41:42.780> it<02:41:42.960> if<02:41:43.200> not<02:41:43.380> it<02:41:43.560> Just 02:41:43.730 --> 02:41:43.740 align:start position:0% door is you can find it if not it Just 02:41:43.740 --> 02:41:45.230 align:start position:0% door is you can find it if not it Just Blends<02:41:44.100> into<02:41:44.220> the<02:41:44.520> wall 02:41:45.230 --> 02:41:45.240 align:start position:0% Blends into the wall 02:41:45.240 --> 02:41:46.910 align:start position:0% Blends into the wall finally<02:41:45.899> after<02:41:46.080> we've<02:41:46.380> set<02:41:46.500> everything<02:41:46.680> up 02:41:46.910 --> 02:41:46.920 align:start position:0% finally after we've set everything up 02:41:46.920 --> 02:41:48.349 align:start position:0% finally after we've set everything up the<02:41:47.100> last<02:41:47.220> thing<02:41:47.340> we<02:41:47.460> want<02:41:47.580> to<02:41:47.700> do<02:41:47.760> is<02:41:47.880> test<02:41:48.120> for 02:41:48.349 --> 02:41:48.359 align:start position:0% the last thing we want to do is test for 02:41:48.359 --> 02:41:50.150 align:start position:0% the last thing we want to do is test for functionality<02:41:49.020> make<02:41:49.560> sure<02:41:49.740> that<02:41:49.920> all<02:41:50.040> the 02:41:50.150 --> 02:41:50.160 align:start position:0% functionality make sure that all the 02:41:50.160 --> 02:41:52.670 align:start position:0% functionality make sure that all the users<02:41:50.399> can<02:41:50.640> connect<02:41:51.140> make<02:41:52.140> sure<02:41:52.319> that<02:41:52.500> they 02:41:52.670 --> 02:41:52.680 align:start position:0% users can connect make sure that they 02:41:52.680 --> 02:41:54.170 align:start position:0% users can connect make sure that they can<02:41:52.740> get<02:41:52.920> in<02:41:53.040> from<02:41:53.220> the<02:41:53.399> locations<02:41:53.819> they<02:41:54.060> need 02:41:54.170 --> 02:41:54.180 align:start position:0% can get in from the locations they need 02:41:54.180 --> 02:41:56.210 align:start position:0% can get in from the locations they need to<02:41:54.359> and<02:41:55.020> also<02:41:55.260> make<02:41:55.439> sure<02:41:55.560> that<02:41:55.740> people<02:41:55.979> who 02:41:56.210 --> 02:41:56.220 align:start position:0% to and also make sure that people who 02:41:56.220 --> 02:41:57.410 align:start position:0% to and also make sure that people who can't<02:41:56.399> who<02:41:56.640> shouldn't<02:41:56.939> be<02:41:57.060> able<02:41:57.180> to<02:41:57.300> connect 02:41:57.410 --> 02:41:57.420 align:start position:0% can't who shouldn't be able to connect 02:41:57.420 --> 02:41:58.969 align:start position:0% can't who shouldn't be able to connect can't 02:41:58.969 --> 02:41:58.979 align:start position:0% can't 02:41:58.979 --> 02:42:01.010 align:start position:0% can't all<02:41:59.399> right<02:41:59.580> so<02:42:00.060> now<02:42:00.180> we've<02:42:00.420> talked<02:42:00.720> about<02:42:00.840> a 02:42:01.010 --> 02:42:01.020 align:start position:0% all right so now we've talked about a 02:42:01.020 --> 02:42:02.510 align:start position:0% all right so now we've talked about a couple<02:42:01.140> different<02:42:01.439> things<02:42:01.680> first<02:42:01.979> we<02:42:02.220> talked 02:42:02.510 --> 02:42:02.520 align:start position:0% couple different things first we talked 02:42:02.520 --> 02:42:05.630 align:start position:0% couple different things first we talked about<02:42:02.840> unbounded<02:42:03.840> Network<02:42:04.260> media<02:42:04.859> which 02:42:05.630 --> 02:42:05.640 align:start position:0% about unbounded Network media which 02:42:05.640 --> 02:42:08.570 align:start position:0% about unbounded Network media which again<02:42:05.880> is<02:42:06.180> sort<02:42:06.420> of<02:42:06.540> Wireless 02:42:08.570 --> 02:42:08.580 align:start position:0% again is sort of Wireless 02:42:08.580 --> 02:42:11.570 align:start position:0% again is sort of Wireless in<02:42:09.120> scope<02:42:09.420> it<02:42:09.660> means<02:42:09.899> there's<02:42:10.140> no<02:42:10.560> chord<02:42:10.920> we 02:42:11.570 --> 02:42:11.580 align:start position:0% in scope it means there's no chord we 02:42:11.580 --> 02:42:14.090 align:start position:0% in scope it means there's no chord we looked<02:42:11.880> at<02:42:12.000> Radio<02:42:12.359> networking<02:42:13.140> and<02:42:13.680> broadcast 02:42:14.090 --> 02:42:14.100 align:start position:0% looked at Radio networking and broadcast 02:42:14.100 --> 02:42:18.110 align:start position:0% looked at Radio networking and broadcast radio<02:42:15.080> we<02:42:16.080> also<02:42:16.260> looked<02:42:16.560> at<02:42:16.620> the<02:42:16.979> sped<02:42:17.399> spread 02:42:18.110 --> 02:42:18.120 align:start position:0% radio we also looked at the sped spread 02:42:18.120 --> 02:42:20.630 align:start position:0% radio we also looked at the sped spread spectrum<02:42:18.780> and<02:42:19.439> if<02:42:19.560> you<02:42:19.680> remember<02:42:19.859> that's<02:42:20.220> we 02:42:20.630 --> 02:42:20.640 align:start position:0% spectrum and if you remember that's we 02:42:20.640 --> 02:42:22.370 align:start position:0% spectrum and if you remember that's we have<02:42:20.760> two<02:42:20.939> different<02:42:21.120> types<02:42:21.600> one<02:42:21.899> which<02:42:22.200> is 02:42:22.370 --> 02:42:22.380 align:start position:0% have two different types one which is 02:42:22.380 --> 02:42:26.210 align:start position:0% have two different types one which is going<02:42:22.680> to<02:42:23.100> broadcast<02:42:23.880> on<02:42:24.479> several<02:42:24.840> different 02:42:26.210 --> 02:42:26.220 align:start position:0% going to broadcast on several different 02:42:26.220 --> 02:42:29.090 align:start position:0% going to broadcast on several different channels<02:42:27.060> on<02:42:27.300> the<02:42:27.420> Spectrum<02:42:27.780> at<02:42:27.960> once<02:42:28.260> and<02:42:28.859> one 02:42:29.090 --> 02:42:29.100 align:start position:0% channels on the Spectrum at once and one 02:42:29.100 --> 02:42:32.210 align:start position:0% channels on the Spectrum at once and one which<02:42:29.280> hops<02:42:29.939> around<02:42:30.840> at<02:42:31.439> certain<02:42:31.620> intervals 02:42:32.210 --> 02:42:32.220 align:start position:0% which hops around at certain intervals 02:42:32.220 --> 02:42:35.090 align:start position:0% which hops around at certain intervals we<02:42:32.880> also<02:42:33.120> looked<02:42:33.359> at<02:42:33.479> infrared<02:42:34.080> Bluetooth<02:42:34.560> and 02:42:35.090 --> 02:42:35.100 align:start position:0% we also looked at infrared Bluetooth and 02:42:35.100 --> 02:42:37.730 align:start position:0% we also looked at infrared Bluetooth and microwave<02:42:35.520> connections<02:42:36.180> these<02:42:37.140> two<02:42:37.260> much 02:42:37.730 --> 02:42:37.740 align:start position:0% microwave connections these two much 02:42:37.740 --> 02:42:41.090 align:start position:0% microwave connections these two much more<02:42:38.040> uh<02:42:38.700> shorter<02:42:39.300> distances<02:42:39.920> microwave<02:42:40.920> a 02:42:41.090 --> 02:42:41.100 align:start position:0% more uh shorter distances microwave a 02:42:41.100 --> 02:42:43.670 align:start position:0% more uh shorter distances microwave a much<02:42:41.280> longer<02:42:41.700> distance<02:42:41.960> this<02:42:42.960> requires<02:42:43.439> a 02:42:43.670 --> 02:42:43.680 align:start position:0% much longer distance this requires a 02:42:43.680 --> 02:42:45.770 align:start position:0% much longer distance this requires a line<02:42:43.800> of<02:42:43.979> sight<02:42:44.220> so<02:42:44.640> does 02:42:45.770 --> 02:42:45.780 align:start position:0% line of sight so does 02:42:45.780 --> 02:42:48.830 align:start position:0% line of sight so does IR<02:42:46.380> Bluetooth<02:42:47.100> does<02:42:47.580> not<02:42:47.819> but<02:42:48.180> does<02:42:48.420> have<02:42:48.600> a 02:42:48.830 --> 02:42:48.840 align:start position:0% IR Bluetooth does not but does have a 02:42:48.840 --> 02:42:52.130 align:start position:0% IR Bluetooth does not but does have a very<02:42:49.020> limited<02:42:49.560> degree<02:42:50.460> of<02:42:51.120> um<02:42:51.180> distance<02:42:51.780> that 02:42:52.130 --> 02:42:52.140 align:start position:0% very limited degree of um distance that 02:42:52.140 --> 02:42:54.230 align:start position:0% very limited degree of um distance that it'll<02:42:52.380> work<02:42:52.560> we<02:42:53.160> also<02:42:53.340> looked<02:42:53.640> at<02:42:53.700> a<02:42:54.000> wireless 02:42:54.230 --> 02:42:54.240 align:start position:0% it'll work we also looked at a wireless 02:42:54.240 --> 02:42:58.910 align:start position:0% it'll work we also looked at a wireless access<02:42:54.720> point<02:42:55.140> or<02:42:55.680> a<02:42:56.479> WAP<02:42:57.680> by<02:42:58.680> the<02:42:58.800> way 02:42:58.910 --> 02:42:58.920 align:start position:0% access point or a WAP by the way 02:42:58.920 --> 02:43:00.889 align:start position:0% access point or a WAP by the way wireless<02:42:59.220> access<02:42:59.580> point<02:43:00.000> is<02:43:00.359> also<02:43:00.600> going<02:43:00.780> to 02:43:00.889 --> 02:43:00.899 align:start position:0% wireless access point is also going to 02:43:00.899 --> 02:43:02.570 align:start position:0% wireless access point is also going to be<02:43:01.020> built<02:43:01.319> into<02:43:01.380> what's<02:43:01.740> called<02:43:01.920> a<02:43:02.160> Soho 02:43:02.570 --> 02:43:02.580 align:start position:0% be built into what's called a Soho 02:43:02.580 --> 02:43:03.889 align:start position:0% be built into what's called a Soho router<02:43:02.880> those<02:43:03.060> are<02:43:03.180> those<02:43:03.300> Linksys<02:43:03.720> or 02:43:03.889 --> 02:43:03.899 align:start position:0% router those are those Linksys or 02:43:03.899 --> 02:43:05.210 align:start position:0% router those are those Linksys or Netgear<02:43:04.319> routers<02:43:04.620> that<02:43:04.740> you<02:43:04.859> buy<02:43:04.920> at<02:43:05.100> the 02:43:05.210 --> 02:43:05.220 align:start position:0% Netgear routers that you buy at the 02:43:05.220 --> 02:43:07.010 align:start position:0% Netgear routers that you buy at the store<02:43:05.399> and<02:43:06.060> finally<02:43:06.300> we<02:43:06.479> described<02:43:06.840> the 02:43:07.010 --> 02:43:07.020 align:start position:0% store and finally we described the 02:43:07.020 --> 02:43:09.590 align:start position:0% store and finally we described the characteristics<02:43:07.560> of<02:43:07.740> an<02:43:07.920> SSID<02:43:08.600> specifically 02:43:09.590 --> 02:43:09.600 align:start position:0% characteristics of an SSID specifically 02:43:09.600 --> 02:43:11.510 align:start position:0% characteristics of an SSID specifically the<02:43:09.840> fact<02:43:10.020> that<02:43:10.260> we<02:43:10.439> want<02:43:10.560> to<02:43:10.740> disable<02:43:11.100> their 02:43:11.510 --> 02:43:11.520 align:start position:0% the fact that we want to disable their 02:43:11.520 --> 02:43:16.849 align:start position:0% the fact that we want to disable their broadcasting 02:43:16.849 --> 02:43:16.859 align:start position:0% 02:43:16.859 --> 02:43:19.010 align:start position:0% so<02:43:17.580> we've<02:43:17.760> talked<02:43:18.000> about<02:43:18.060> the<02:43:18.540> bounded<02:43:18.960> and 02:43:19.010 --> 02:43:19.020 align:start position:0% so we've talked about the bounded and 02:43:19.020 --> 02:43:20.510 align:start position:0% so we've talked about the bounded and Unbound<02:43:19.380> media<02:43:19.740> let's<02:43:19.859> talk<02:43:20.040> about<02:43:20.160> some<02:43:20.399> of 02:43:20.510 --> 02:43:20.520 align:start position:0% Unbound media let's talk about some of 02:43:20.520 --> 02:43:21.950 align:start position:0% Unbound media let's talk about some of the<02:43:20.640> devices<02:43:20.880> this<02:43:21.300> media<02:43:21.600> is<02:43:21.720> going<02:43:21.840> to 02:43:21.950 --> 02:43:21.960 align:start position:0% the devices this media is going to 02:43:21.960 --> 02:43:25.550 align:start position:0% the devices this media is going to connect<02:43:22.080> to 02:43:25.550 --> 02:43:25.560 align:start position:0% 02:43:25.560 --> 02:43:45.550 align:start position:0% [Music] 02:43:45.550 --> 02:43:45.560 align:start position:0% 02:43:45.560 --> 02:43:49.010 align:start position:0% Network<02:43:46.560> hardware<02:43:46.920> and<02:43:47.340> media<02:43:48.240> network 02:43:49.010 --> 02:43:49.020 align:start position:0% Network hardware and media network 02:43:49.020 --> 02:43:52.429 align:start position:0% Network hardware and media network connectivity<02:43:49.920> devices 02:43:52.429 --> 02:43:52.439 align:start position:0% connectivity devices 02:43:52.439 --> 02:43:55.309 align:start position:0% connectivity devices so<02:43:52.979> having<02:43:53.160> discussed<02:43:53.939> the<02:43:54.540> way<02:43:54.660> that<02:43:54.960> devices 02:43:55.309 --> 02:43:55.319 align:start position:0% so having discussed the way that devices 02:43:55.319 --> 02:43:58.010 align:start position:0% so having discussed the way that devices connect<02:43:55.800> either<02:43:56.340> using<02:43:56.760> unbounded<02:43:57.540> or 02:43:58.010 --> 02:43:58.020 align:start position:0% connect either using unbounded or 02:43:58.020 --> 02:44:00.590 align:start position:0% connect either using unbounded or bounded<02:43:58.500> media<02:43:58.979> let's<02:43:59.520> now<02:43:59.760> talk<02:44:00.000> about<02:44:00.180> the 02:44:00.590 --> 02:44:00.600 align:start position:0% bounded media let's now talk about the 02:44:00.600 --> 02:44:03.410 align:start position:0% bounded media let's now talk about the connectivity<02:44:01.140> devices<02:44:01.500> themselves 02:44:03.410 --> 02:44:03.420 align:start position:0% connectivity devices themselves 02:44:03.420 --> 02:44:05.690 align:start position:0% connectivity devices themselves so<02:44:03.780> the<02:44:03.899> objectives<02:44:04.260> of<02:44:04.500> this<02:44:04.740> module<02:44:05.220> are 02:44:05.690 --> 02:44:05.700 align:start position:0% so the objectives of this module are 02:44:05.700 --> 02:44:08.090 align:start position:0% so the objectives of this module are first<02:44:05.939> to<02:44:06.300> Define<02:44:06.600> and<02:44:07.080> describe<02:44:07.560> a<02:44:07.920> Nick 02:44:08.090 --> 02:44:08.100 align:start position:0% first to Define and describe a Nick 02:44:08.100 --> 02:44:10.630 align:start position:0% first to Define and describe a Nick which<02:44:08.819> also<02:44:09.120> stands<02:44:09.479> for<02:44:09.720> a<02:44:10.319> network 02:44:10.630 --> 02:44:10.640 align:start position:0% which also stands for a network 02:44:10.640 --> 02:44:13.849 align:start position:0% which also stands for a network interface<02:44:11.640> card 02:44:13.849 --> 02:44:13.859 align:start position:0% interface card 02:44:13.859 --> 02:44:16.309 align:start position:0% interface card this<02:44:14.340> is<02:44:14.520> the<02:44:14.760> main<02:44:14.939> way<02:44:15.300> in<02:44:15.479> which<02:44:15.720> devices 02:44:16.309 --> 02:44:16.319 align:start position:0% this is the main way in which devices 02:44:16.319 --> 02:44:24.410 align:start position:0% this is the main way in which devices connect<02:44:16.859> to<02:44:17.460> a<02:44:17.760> network 02:44:24.410 --> 02:44:24.420 align:start position:0% 02:44:24.420 --> 02:44:26.570 align:start position:0% we're<02:44:25.140> also<02:44:25.439> going<02:44:25.500> to<02:44:25.620> talk<02:44:25.800> about<02:44:26.100> a 02:44:26.570 --> 02:44:26.580 align:start position:0% we're also going to talk about a 02:44:26.580 --> 02:44:28.790 align:start position:0% we're also going to talk about a transceiver<02:44:27.060> a<02:44:27.660> chip<02:44:27.780> that<02:44:28.080> is<02:44:28.260> on<02:44:28.500> the<02:44:28.620> Nick 02:44:28.790 --> 02:44:28.800 align:start position:0% transceiver a chip that is on the Nick 02:44:28.800 --> 02:44:31.910 align:start position:0% transceiver a chip that is on the Nick and<02:44:29.340> basically<02:44:29.760> allows<02:44:30.180> it<02:44:30.300> to<02:44:30.479> communicate 02:44:31.910 --> 02:44:31.920 align:start position:0% and basically allows it to communicate 02:44:31.920 --> 02:44:34.550 align:start position:0% and basically allows it to communicate we're<02:44:32.399> also<02:44:32.700> going<02:44:32.880> to<02:44:33.200> identify<02:44:34.200> the 02:44:34.550 --> 02:44:34.560 align:start position:0% we're also going to identify the 02:44:34.560 --> 02:44:37.190 align:start position:0% we're also going to identify the characteristics<02:44:35.220> that<02:44:35.520> make<02:44:35.760> a<02:44:36.300> switch<02:44:36.479> one 02:44:37.190 --> 02:44:37.200 align:start position:0% characteristics that make a switch one 02:44:37.200 --> 02:44:39.830 align:start position:0% characteristics that make a switch one of<02:44:37.319> the<02:44:37.620> main<02:44:37.979> Central<02:44:38.340> devices<02:44:38.939> in<02:44:39.479> our<02:44:39.660> start 02:44:39.830 --> 02:44:39.840 align:start position:0% of the main Central devices in our start 02:44:39.840 --> 02:44:43.070 align:start position:0% of the main Central devices in our start apology<02:44:40.439> that<02:44:41.040> allows<02:44:41.399> for<02:44:41.580> communication<02:44:42.120> on 02:44:43.070 --> 02:44:43.080 align:start position:0% apology that allows for communication on 02:44:43.080 --> 02:44:45.410 align:start position:0% apology that allows for communication on a<02:44:43.380> local<02:44:43.620> area<02:44:43.979> network<02:44:44.340> and<02:44:45.120> then<02:44:45.240> we're 02:44:45.410 --> 02:44:45.420 align:start position:0% a local area network and then we're 02:44:45.420 --> 02:44:48.410 align:start position:0% a local area network and then we're going<02:44:45.540> to<02:44:45.660> identify<02:44:46.260> some<02:44:46.979> of<02:44:47.100> the<02:44:47.460> qualities 02:44:48.410 --> 02:44:48.420 align:start position:0% going to identify some of the qualities 02:44:48.420 --> 02:44:50.929 align:start position:0% going to identify some of the qualities and<02:44:49.080> some<02:44:49.319> of<02:44:49.439> the<02:44:49.740> characteristics<02:44:50.460> that<02:44:50.819> we 02:44:50.929 --> 02:44:50.939 align:start position:0% and some of the characteristics that we 02:44:50.939 --> 02:44:53.090 align:start position:0% and some of the characteristics that we can<02:44:51.060> put<02:44:51.300> into<02:44:51.600> a<02:44:51.840> switch<02:44:52.020> including<02:44:52.560> trunking 02:44:53.090 --> 02:44:53.100 align:start position:0% can put into a switch including trunking 02:44:53.100 --> 02:44:56.150 align:start position:0% can put into a switch including trunking Port<02:44:53.640> mirroring<02:44:54.180> and<02:44:54.780> channel<02:44:54.960> bonding<02:44:55.620> all 02:44:56.150 --> 02:44:56.160 align:start position:0% Port mirroring and channel bonding all 02:44:56.160 --> 02:44:57.889 align:start position:0% Port mirroring and channel bonding all of<02:44:56.220> these<02:44:56.460> do<02:44:56.700> come<02:44:56.880> up<02:44:57.000> on<02:44:57.180> the<02:44:57.300> exam<02:44:57.600> and<02:44:57.720> so 02:44:57.889 --> 02:44:57.899 align:start position:0% of these do come up on the exam and so 02:44:57.899 --> 02:44:59.990 align:start position:0% of these do come up on the exam and so they<02:44:58.140> are<02:44:58.319> pretty<02:44:58.620> important<02:44:58.979> to<02:44:59.220> cover 02:44:59.990 --> 02:45:00.000 align:start position:0% they are pretty important to cover 02:45:00.000 --> 02:45:01.849 align:start position:0% they are pretty important to cover then<02:45:00.479> we're<02:45:00.660> going<02:45:00.780> to<02:45:00.840> talk<02:45:01.020> about<02:45:01.140> a<02:45:01.500> router 02:45:01.849 --> 02:45:01.859 align:start position:0% then we're going to talk about a router 02:45:01.859 --> 02:45:04.550 align:start position:0% then we're going to talk about a router and<02:45:02.100> a<02:45:02.280> Gateway<02:45:02.640> these<02:45:03.420> two<02:45:03.540> devices<02:45:03.899> allow<02:45:04.439> us 02:45:04.550 --> 02:45:04.560 align:start position:0% and a Gateway these two devices allow us 02:45:04.560 --> 02:45:06.410 align:start position:0% and a Gateway these two devices allow us to<02:45:05.040> communicate<02:45:05.399> outside<02:45:05.760> of<02:45:06.060> our<02:45:06.240> local 02:45:06.410 --> 02:45:06.420 align:start position:0% to communicate outside of our local 02:45:06.420 --> 02:45:08.990 align:start position:0% to communicate outside of our local networks<02:45:07.020> onto<02:45:07.380> a<02:45:07.859> wide<02:45:07.979> area<02:45:08.160> network<02:45:08.460> or<02:45:08.819> a 02:45:08.990 --> 02:45:09.000 align:start position:0% networks onto a wide area network or a 02:45:09.000 --> 02:45:10.070 align:start position:0% networks onto a wide area network or a Wan 02:45:10.070 --> 02:45:10.080 align:start position:0% Wan 02:45:10.080 --> 02:45:13.309 align:start position:0% Wan now<02:45:10.500> as<02:45:10.680> with<02:45:10.859> anything<02:45:11.300> we<02:45:12.300> have<02:45:12.479> noise<02:45:12.899> that 02:45:13.309 --> 02:45:13.319 align:start position:0% now as with anything we have noise that 02:45:13.319 --> 02:45:15.170 align:start position:0% now as with anything we have noise that interrupts<02:45:13.800> the<02:45:13.979> signal<02:45:14.340> and<02:45:14.760> so<02:45:14.880> we're<02:45:15.060> going 02:45:15.170 --> 02:45:15.180 align:start position:0% interrupts the signal and so we're going 02:45:15.180 --> 02:45:17.809 align:start position:0% interrupts the signal and so we're going to<02:45:15.300> talk<02:45:15.479> about<02:45:15.720> what<02:45:16.380> that<02:45:16.560> noise<02:45:16.740> is<02:45:17.100> and<02:45:17.700> the 02:45:17.809 --> 02:45:17.819 align:start position:0% to talk about what that noise is and the 02:45:17.819 --> 02:45:19.870 align:start position:0% to talk about what that noise is and the sources<02:45:18.240> of<02:45:18.420> that<02:45:18.600> noise<02:45:18.780> so<02:45:19.140> we<02:45:19.319> can<02:45:19.439> better 02:45:19.870 --> 02:45:19.880 align:start position:0% sources of that noise so we can better 02:45:19.880 --> 02:45:23.450 align:start position:0% sources of that noise so we can better uh<02:45:20.880> alleviate<02:45:21.840> and<02:45:22.140> avoid<02:45:22.439> it 02:45:23.450 --> 02:45:23.460 align:start position:0% uh alleviate and avoid it 02:45:23.460 --> 02:45:25.309 align:start position:0% uh alleviate and avoid it finally<02:45:24.060> we're<02:45:24.359> going<02:45:24.540> to<02:45:24.660> talk<02:45:24.780> about<02:45:25.020> that 02:45:25.309 --> 02:45:25.319 align:start position:0% finally we're going to talk about that 02:45:25.319 --> 02:45:27.710 align:start position:0% finally we're going to talk about that alleviation<02:45:25.979> and<02:45:26.580> avoidance<02:45:27.180> by<02:45:27.540> talking 02:45:27.710 --> 02:45:27.720 align:start position:0% alleviation and avoidance by talking 02:45:27.720 --> 02:45:29.929 align:start position:0% alleviation and avoidance by talking about<02:45:27.960> noise<02:45:28.439> control<02:45:28.800> and<02:45:29.580> reduction 02:45:29.929 --> 02:45:29.939 align:start position:0% about noise control and reduction 02:45:29.939 --> 02:45:33.469 align:start position:0% about noise control and reduction techniques<02:45:30.660> sometimes<02:45:31.560> getting<02:45:31.859> into<02:45:32.479> these 02:45:33.469 --> 02:45:33.479 align:start position:0% techniques sometimes getting into these 02:45:33.479 --> 02:45:35.870 align:start position:0% techniques sometimes getting into these specifics<02:45:33.960> of<02:45:34.140> how<02:45:34.380> this<02:45:34.560> works<02:45:34.979> now<02:45:35.460> some<02:45:35.760> of 02:45:35.870 --> 02:45:35.880 align:start position:0% specifics of how this works now some of 02:45:35.880 --> 02:45:37.849 align:start position:0% specifics of how this works now some of this<02:45:36.000> might<02:45:36.180> be<02:45:36.359> a<02:45:36.540> little<02:45:36.660> too<02:45:36.960> complex<02:45:37.319> for 02:45:37.849 --> 02:45:37.859 align:start position:0% this might be a little too complex for 02:45:37.859 --> 02:45:41.030 align:start position:0% this might be a little too complex for the<02:45:38.640> network<02:45:38.880> plus<02:45:39.240> exam<02:45:39.720> but<02:45:40.560> it's<02:45:40.740> good<02:45:40.920> to 02:45:41.030 --> 02:45:41.040 align:start position:0% the network plus exam but it's good to 02:45:41.040 --> 02:45:42.830 align:start position:0% the network plus exam but it's good to go<02:45:41.160> over<02:45:41.280> anyway<02:45:41.520> so<02:45:41.760> you<02:45:41.939> have<02:45:42.060> a<02:45:42.240> firm<02:45:42.540> basis 02:45:42.830 --> 02:45:42.840 align:start position:0% go over anyway so you have a firm basis 02:45:42.840 --> 02:45:44.510 align:start position:0% go over anyway so you have a firm basis in<02:45:43.020> the<02:45:43.200> theory<02:45:43.439> behind<02:45:43.800> it 02:45:44.510 --> 02:45:44.520 align:start position:0% in the theory behind it 02:45:44.520 --> 02:45:48.290 align:start position:0% in the theory behind it so<02:45:45.300> the<02:45:45.899> Nick<02:45:46.080> or<02:45:46.800> the<02:45:47.160> network<02:45:47.460> interface 02:45:48.290 --> 02:45:48.300 align:start position:0% so the Nick or the network interface 02:45:48.300 --> 02:45:51.410 align:start position:0% so the Nick or the network interface card<02:45:48.899> is<02:45:49.620> a<02:45:49.920> physical<02:45:50.100> connectivity<02:45:51.000> device 02:45:51.410 --> 02:45:51.420 align:start position:0% card is a physical connectivity device 02:45:51.420 --> 02:45:56.330 align:start position:0% card is a physical connectivity device that<02:45:52.080> can<02:45:52.319> be<02:45:52.560> either<02:45:52.939> wired<02:45:53.939> or<02:45:54.780> Wireless<02:45:55.340> for 02:45:56.330 --> 02:45:56.340 align:start position:0% that can be either wired or Wireless for 02:45:56.340 --> 02:45:59.210 align:start position:0% that can be either wired or Wireless for Wired<02:45:56.760> networks<02:45:57.359> the<02:45:57.720> Nix<02:45:57.960> gonna<02:45:58.319> have<02:45:58.560> an 02:45:59.210 --> 02:45:59.220 align:start position:0% Wired networks the Nix gonna have an 02:45:59.220 --> 02:46:02.389 align:start position:0% Wired networks the Nix gonna have an ethernet<02:45:59.760> port<02:46:00.120> which<02:46:00.660> is<02:46:00.780> right<02:46:01.080> here<02:46:01.399> that 02:46:02.389 --> 02:46:02.399 align:start position:0% ethernet port which is right here that 02:46:02.399 --> 02:46:05.450 align:start position:0% ethernet port which is right here that allows<02:46:02.819> you<02:46:02.939> to<02:46:03.300> connect<02:46:03.420> to<02:46:03.840> an<02:46:04.080> RJ45<02:46:04.979> cable 02:46:05.450 --> 02:46:05.460 align:start position:0% allows you to connect to an RJ45 cable 02:46:05.460 --> 02:46:09.050 align:start position:0% allows you to connect to an RJ45 cable if<02:46:05.700> you<02:46:05.819> recall<02:46:06.180> the<02:46:06.420> RJ45<02:46:07.380> cable<02:46:07.920> is<02:46:08.520> the<02:46:08.819> ones 02:46:09.050 --> 02:46:09.060 align:start position:0% if you recall the RJ45 cable is the ones 02:46:09.060 --> 02:46:12.070 align:start position:0% if you recall the RJ45 cable is the ones used<02:46:09.359> with<02:46:09.840> most<02:46:10.439> uh<02:46:10.979> twisted<02:46:11.460> pair 02:46:12.070 --> 02:46:12.080 align:start position:0% used with most uh twisted pair 02:46:12.080 --> 02:46:14.870 align:start position:0% used with most uh twisted pair installations<02:46:13.080> you<02:46:13.979> can<02:46:14.040> either<02:46:14.220> connect<02:46:14.520> it 02:46:14.870 --> 02:46:14.880 align:start position:0% installations you can either connect it 02:46:14.880 --> 02:46:19.190 align:start position:0% installations you can either connect it directly<02:46:15.479> to<02:46:16.200> the<02:46:16.380> motherboard<02:46:17.060> or<02:46:18.060> it<02:46:18.840> can<02:46:19.020> be 02:46:19.190 --> 02:46:19.200 align:start position:0% directly to the motherboard or it can be 02:46:19.200 --> 02:46:20.990 align:start position:0% directly to the motherboard or it can be connected<02:46:19.560> through<02:46:19.800> another<02:46:20.100> card<02:46:20.520> or<02:46:20.819> a 02:46:20.990 --> 02:46:21.000 align:start position:0% connected through another card or a 02:46:21.000 --> 02:46:23.270 align:start position:0% connected through another card or a riser<02:46:21.420> card<02:46:21.540> or<02:46:21.840> an<02:46:22.020> expansion<02:46:22.500> bus<02:46:22.680> as<02:46:22.979> this 02:46:23.270 --> 02:46:23.280 align:start position:0% riser card or an expansion bus as this 02:46:23.280 --> 02:46:25.490 align:start position:0% riser card or an expansion bus as this one<02:46:23.399> would<02:46:23.640> be<02:46:24.240> now<02:46:24.780> there<02:46:24.960> are<02:46:25.140> typically 02:46:25.490 --> 02:46:25.500 align:start position:0% one would be now there are typically 02:46:25.500 --> 02:46:28.910 align:start position:0% one would be now there are typically connectivity<02:46:26.340> lights<02:46:26.899> uh<02:46:27.899> on<02:46:28.200> the<02:46:28.380> outside<02:46:28.500> of 02:46:28.910 --> 02:46:28.920 align:start position:0% connectivity lights uh on the outside of 02:46:28.920 --> 02:46:31.190 align:start position:0% connectivity lights uh on the outside of the<02:46:29.040> Nic<02:46:29.280> that<02:46:29.580> allow<02:46:29.880> administrators<02:46:30.600> to<02:46:30.960> get 02:46:31.190 --> 02:46:31.200 align:start position:0% the Nic that allow administrators to get 02:46:31.200 --> 02:46:33.290 align:start position:0% the Nic that allow administrators to get a<02:46:31.500> a<02:46:31.979> quick<02:46:32.280> status<02:46:32.640> of<02:46:33.000> the<02:46:33.120> network 02:46:33.290 --> 02:46:33.300 align:start position:0% a a quick status of the network 02:46:33.300 --> 02:46:35.809 align:start position:0% a a quick status of the network connection<02:46:33.740> the<02:46:34.740> connectivity<02:46:35.220> lights<02:46:35.460> can 02:46:35.809 --> 02:46:35.819 align:start position:0% connection the connectivity lights can 02:46:35.819 --> 02:46:37.730 align:start position:0% connection the connectivity lights can mean<02:46:36.000> different<02:46:36.359> things<02:46:36.720> depending<02:46:37.319> on<02:46:37.560> the 02:46:37.730 --> 02:46:37.740 align:start position:0% mean different things depending on the 02:46:37.740 --> 02:46:39.830 align:start position:0% mean different things depending on the manufacture<02:46:38.280> of<02:46:38.460> the<02:46:38.640> Nick<02:46:38.760> however<02:46:39.540> most 02:46:39.830 --> 02:46:39.840 align:start position:0% manufacture of the Nick however most 02:46:39.840 --> 02:46:41.270 align:start position:0% manufacture of the Nick however most commonly<02:46:40.319> there<02:46:40.560> are<02:46:40.680> going<02:46:40.800> to<02:46:40.859> be<02:46:40.920> at<02:46:41.160> least 02:46:41.270 --> 02:46:41.280 align:start position:0% commonly there are going to be at least 02:46:41.280 --> 02:46:44.030 align:start position:0% commonly there are going to be at least two<02:46:41.640> and<02:46:42.000> possibly<02:46:42.420> even<02:46:42.660> three<02:46:43.020> and<02:46:43.680> each<02:46:43.920> of 02:46:44.030 --> 02:46:44.040 align:start position:0% two and possibly even three and each of 02:46:44.040 --> 02:46:45.050 align:start position:0% two and possibly even three and each of those<02:46:44.160> lights<02:46:44.340> are<02:46:44.580> going<02:46:44.640> to<02:46:44.760> be<02:46:44.880> different 02:46:45.050 --> 02:46:45.060 align:start position:0% those lights are going to be different 02:46:45.060 --> 02:46:46.849 align:start position:0% those lights are going to be different colors<02:46:45.479> you<02:46:45.720> can<02:46:45.840> see<02:46:45.960> on<02:46:46.080> this<02:46:46.260> one<02:46:46.439> we<02:46:46.680> have 02:46:46.849 --> 02:46:46.859 align:start position:0% colors you can see on this one we have 02:46:46.859 --> 02:46:48.950 align:start position:0% colors you can see on this one we have three<02:46:47.460> different<02:46:47.880> lights 02:46:48.950 --> 02:46:48.960 align:start position:0% three different lights 02:46:48.960 --> 02:46:51.370 align:start position:0% three different lights there<02:46:49.500> should<02:46:49.680> be<02:46:49.859> one<02:46:50.100> light<02:46:50.280> that<02:46:50.700> is<02:46:50.819> on<02:46:51.120> to 02:46:51.370 --> 02:46:51.380 align:start position:0% there should be one light that is on to 02:46:51.380 --> 02:46:54.349 align:start position:0% there should be one light that is on to dictate<02:46:52.380> that<02:46:52.800> there<02:46:53.100> is<02:46:53.280> a<02:46:53.520> connection 02:46:54.349 --> 02:46:54.359 align:start position:0% dictate that there is a connection 02:46:54.359 --> 02:46:57.170 align:start position:0% dictate that there is a connection that<02:46:55.020> would<02:46:55.140> be<02:46:55.319> a<02:46:55.800> solid<02:46:56.160> green<02:46:56.520> light<02:46:56.819> most 02:46:57.170 --> 02:46:57.180 align:start position:0% that would be a solid green light most 02:46:57.180 --> 02:46:59.270 align:start position:0% that would be a solid green light most of<02:46:57.359> the<02:46:57.479> time<02:46:57.600> and<02:46:58.140> it's<02:46:58.260> going<02:46:58.500> to<02:46:58.680> stay<02:46:58.920> lit 02:46:59.270 --> 02:46:59.280 align:start position:0% of the time and it's going to stay lit 02:46:59.280 --> 02:47:01.010 align:start position:0% of the time and it's going to stay lit when<02:46:59.520> connection<02:46:59.819> and<02:47:00.600> there's<02:47:00.720> also<02:47:00.960> going 02:47:01.010 --> 02:47:01.020 align:start position:0% when connection and there's also going 02:47:01.020 --> 02:47:02.570 align:start position:0% when connection and there's also going to<02:47:01.080> be<02:47:01.200> another<02:47:01.380> light<02:47:01.680> that's<02:47:02.040> sort<02:47:02.280> of<02:47:02.399> going 02:47:02.570 --> 02:47:02.580 align:start position:0% to be another light that's sort of going 02:47:02.580 --> 02:47:05.030 align:start position:0% to be another light that's sort of going to<02:47:02.760> flicker<02:47:03.180> the<02:47:03.899> flicker<02:47:04.319> is<02:47:04.680> letting<02:47:04.979> you 02:47:05.030 --> 02:47:05.040 align:start position:0% to flicker the flicker is letting you 02:47:05.040 --> 02:47:06.710 align:start position:0% to flicker the flicker is letting you know<02:47:05.220> that<02:47:05.399> there<02:47:05.580> is<02:47:05.700> activity<02:47:06.180> or<02:47:06.479> that 02:47:06.710 --> 02:47:06.720 align:start position:0% know that there is activity or that 02:47:06.720 --> 02:47:08.929 align:start position:0% know that there is activity or that traffic<02:47:07.020> is<02:47:07.319> being<02:47:07.560> sent<02:47:07.859> across<02:47:08.580> the<02:47:08.760> neck 02:47:08.929 --> 02:47:08.939 align:start position:0% traffic is being sent across the neck 02:47:08.939 --> 02:47:11.990 align:start position:0% traffic is being sent across the neck the<02:47:09.899> faster<02:47:10.200> the<02:47:10.439> flicker<02:47:10.920> uh<02:47:11.340> typically<02:47:11.700> this 02:47:11.990 --> 02:47:12.000 align:start position:0% the faster the flicker uh typically this 02:47:12.000 --> 02:47:14.330 align:start position:0% the faster the flicker uh typically this means<02:47:12.359> that<02:47:12.720> the<02:47:13.200> higher<02:47:13.560> the<02:47:13.740> network<02:47:13.979> speed 02:47:14.330 --> 02:47:14.340 align:start position:0% means that the higher the network speed 02:47:14.340 --> 02:47:16.210 align:start position:0% means that the higher the network speed or<02:47:14.700> the<02:47:14.880> more<02:47:15.000> data<02:47:15.359> that's<02:47:15.540> going<02:47:15.840> over 02:47:16.210 --> 02:47:16.220 align:start position:0% or the more data that's going over 02:47:16.220 --> 02:47:18.349 align:start position:0% or the more data that's going over occasionally<02:47:17.220> you<02:47:17.399> might<02:47:17.580> see<02:47:17.819> one<02:47:18.060> with 02:47:18.349 --> 02:47:18.359 align:start position:0% occasionally you might see one with 02:47:18.359 --> 02:47:20.270 align:start position:0% occasionally you might see one with different<02:47:18.540> colored<02:47:19.080> lights<02:47:19.260> the<02:47:20.160> different 02:47:20.270 --> 02:47:20.280 align:start position:0% different colored lights the different 02:47:20.280 --> 02:47:22.550 align:start position:0% different colored lights the different colors<02:47:20.760> might<02:47:21.000> dictate<02:47:21.479> for<02:47:21.899> instance<02:47:22.080> the 02:47:22.550 --> 02:47:22.560 align:start position:0% colors might dictate for instance the 02:47:22.560 --> 02:47:24.770 align:start position:0% colors might dictate for instance the speed<02:47:22.800> of<02:47:22.979> the<02:47:23.160> connection<02:47:23.340> for<02:47:24.180> instance<02:47:24.420> a 02:47:24.770 --> 02:47:24.780 align:start position:0% speed of the connection for instance a 02:47:24.780 --> 02:47:27.830 align:start position:0% speed of the connection for instance a green<02:47:25.080> for<02:47:25.680> gigabit<02:47:26.160> speeds<02:47:26.700> which<02:47:27.540> would<02:47:27.720> be 02:47:27.830 --> 02:47:27.840 align:start position:0% green for gigabit speeds which would be 02:47:27.840 --> 02:47:30.590 align:start position:0% green for gigabit speeds which would be a<02:47:27.960> thousand<02:47:28.200> megabits<02:47:28.740> per<02:47:28.859> second<02:47:29.100> and<02:47:30.060> Amber 02:47:30.590 --> 02:47:30.600 align:start position:0% a thousand megabits per second and Amber 02:47:30.600 --> 02:47:33.710 align:start position:0% a thousand megabits per second and Amber for<02:47:30.899> instance<02:47:31.200> for<02:47:31.859> uh<02:47:32.399> 100<02:47:32.760> megabit<02:47:33.420> speed 02:47:33.710 --> 02:47:33.720 align:start position:0% for instance for uh 100 megabit speed 02:47:33.720 --> 02:47:35.570 align:start position:0% for instance for uh 100 megabit speed across<02:47:34.200> the<02:47:34.319> network<02:47:34.500> okay<02:47:35.220> and<02:47:35.399> this<02:47:35.520> is 02:47:35.570 --> 02:47:35.580 align:start position:0% across the network okay and this is 02:47:35.580 --> 02:47:38.090 align:start position:0% across the network okay and this is going<02:47:35.819> to<02:47:35.939> really<02:47:36.120> vary<02:47:36.720> depending<02:47:37.260> on<02:47:37.740> the 02:47:38.090 --> 02:47:38.100 align:start position:0% going to really vary depending on the 02:47:38.100 --> 02:47:40.130 align:start position:0% going to really vary depending on the Nick<02:47:38.280> it's<02:47:39.060> also<02:47:39.359> important<02:47:39.600> to<02:47:39.780> know<02:47:39.899> that 02:47:40.130 --> 02:47:40.140 align:start position:0% Nick it's also important to know that 02:47:40.140 --> 02:47:42.950 align:start position:0% Nick it's also important to know that the<02:47:40.500> MAC<02:47:40.979> address<02:47:41.280> which<02:47:42.060> might<02:47:42.300> be<02:47:42.540> written 02:47:42.950 --> 02:47:42.960 align:start position:0% the MAC address which might be written 02:47:42.960 --> 02:47:46.370 align:start position:0% the MAC address which might be written out<02:47:43.140> here<02:47:43.500> is<02:47:44.040> actually<02:47:44.660> hardwired<02:47:45.660> or<02:47:46.080> hard 02:47:46.370 --> 02:47:46.380 align:start position:0% out here is actually hardwired or hard 02:47:46.380 --> 02:47:49.610 align:start position:0% out here is actually hardwired or hard uh<02:47:47.280> coded<02:47:47.819> into<02:47:48.359> the<02:47:48.660> neck<02:47:48.780> so<02:47:49.319> it's<02:47:49.439> something 02:47:49.610 --> 02:47:49.620 align:start position:0% uh coded into the neck so it's something 02:47:49.620 --> 02:47:52.429 align:start position:0% uh coded into the neck so it's something that<02:47:49.979> comes<02:47:50.280> with<02:47:50.460> the<02:47:50.640> Nick<02:47:50.819> itself<02:47:51.240> now<02:47:52.020> a 02:47:52.429 --> 02:47:52.439 align:start position:0% that comes with the Nick itself now a 02:47:52.439 --> 02:47:55.370 align:start position:0% that comes with the Nick itself now a transceiver<02:47:53.040> is<02:47:53.880> a<02:47:54.000> Connect<02:47:54.479> every<02:47:54.899> device 02:47:55.370 --> 02:47:55.380 align:start position:0% transceiver is a Connect every device 02:47:55.380 --> 02:47:59.210 align:start position:0% transceiver is a Connect every device that<02:47:55.979> has<02:47:56.220> the<02:47:56.580> ability<02:47:56.880> to<02:47:57.780> send<02:47:58.080> transmit<02:47:58.859> or 02:47:59.210 --> 02:47:59.220 align:start position:0% that has the ability to send transmit or 02:47:59.220 --> 02:48:02.570 align:start position:0% that has the ability to send transmit or receive<02:47:59.700> traffic<02:48:00.560> simultaneously<02:48:01.580> the 02:48:02.570 --> 02:48:02.580 align:start position:0% receive traffic simultaneously the 02:48:02.580 --> 02:48:05.630 align:start position:0% receive traffic simultaneously the ability<02:48:03.000> that<02:48:03.840> this<02:48:04.080> has<02:48:04.380> is<02:48:04.800> special<02:48:05.160> is<02:48:05.460> due 02:48:05.630 --> 02:48:05.640 align:start position:0% ability that this has is special is due 02:48:05.640 --> 02:48:08.210 align:start position:0% ability that this has is special is due to<02:48:05.880> a<02:48:06.120> specialized<02:48:06.720> chip<02:48:07.020> that's<02:48:07.620> right<02:48:07.920> here 02:48:08.210 --> 02:48:08.220 align:start position:0% to a specialized chip that's right here 02:48:08.220 --> 02:48:11.330 align:start position:0% to a specialized chip that's right here and<02:48:09.060> this<02:48:09.620> assists<02:48:10.620> the<02:48:10.800> Nick<02:48:10.979> in 02:48:11.330 --> 02:48:11.340 align:start position:0% and this assists the Nick in 02:48:11.340 --> 02:48:14.150 align:start position:0% and this assists the Nick in transmitting<02:48:11.880> traffic<02:48:12.180> across<02:48:13.020> the<02:48:13.200> medium 02:48:14.150 --> 02:48:14.160 align:start position:0% transmitting traffic across the medium 02:48:14.160 --> 02:48:16.969 align:start position:0% transmitting traffic across the medium almost<02:48:14.760> every<02:48:15.300> modern<02:48:15.600> Nic<02:48:16.140> has<02:48:16.740> a 02:48:16.969 --> 02:48:16.979 align:start position:0% almost every modern Nic has a 02:48:16.979 --> 02:48:19.969 align:start position:0% almost every modern Nic has a transceiver<02:48:17.460> built<02:48:18.300> directly<02:48:18.899> on<02:48:19.319> to<02:48:19.680> the 02:48:19.969 --> 02:48:19.979 align:start position:0% transceiver built directly on to the 02:48:19.979 --> 02:48:22.130 align:start position:0% transceiver built directly on to the device<02:48:20.160> now<02:48:20.939> a<02:48:21.120> great<02:48:21.240> example<02:48:21.660> of<02:48:21.899> a 02:48:22.130 --> 02:48:22.140 align:start position:0% device now a great example of a 02:48:22.140 --> 02:48:23.929 align:start position:0% device now a great example of a transceiver<02:48:22.620> at<02:48:22.859> work<02:48:23.040> is<02:48:23.280> something<02:48:23.520> called 02:48:23.929 --> 02:48:23.939 align:start position:0% transceiver at work is something called 02:48:23.939 --> 02:48:28.690 align:start position:0% transceiver at work is something called the<02:48:24.660> gbic<02:48:25.439> or<02:48:26.280> gigabit<02:48:26.819> interface<02:48:27.479> converter 02:48:28.690 --> 02:48:28.700 align:start position:0% the gbic or gigabit interface converter 02:48:28.700 --> 02:48:31.910 align:start position:0% the gbic or gigabit interface converter this<02:48:29.700> is<02:48:30.000> something<02:48:30.240> that<02:48:30.600> allows<02:48:31.140> the 02:48:31.910 --> 02:48:31.920 align:start position:0% this is something that allows the 02:48:31.920 --> 02:48:40.090 align:start position:0% this is something that allows the conversion<02:48:32.460> of<02:48:33.080> electrical<02:48:34.080> signals 02:48:40.090 --> 02:48:40.100 align:start position:0% 02:48:40.100 --> 02:48:46.429 align:start position:0% into<02:48:41.100> Optical<02:48:42.000> signals 02:48:46.429 --> 02:48:46.439 align:start position:0% 02:48:46.439 --> 02:48:49.610 align:start position:0% and<02:48:46.979> then<02:48:47.100> back<02:48:47.399> again 02:48:49.610 --> 02:48:49.620 align:start position:0% 02:48:49.620 --> 02:48:51.889 align:start position:0% the<02:48:50.280> gbit<02:48:50.700> can<02:48:50.880> also<02:48:51.060> be<02:48:51.240> used<02:48:51.420> to<02:48:51.600> convert 02:48:51.889 --> 02:48:51.899 align:start position:0% the gbit can also be used to convert 02:48:51.899 --> 02:48:53.929 align:start position:0% the gbit can also be used to convert different<02:48:52.200> Optical<02:48:52.620> Technologies<02:48:53.340> from<02:48:53.700> one 02:48:53.929 --> 02:48:53.939 align:start position:0% different Optical Technologies from one 02:48:53.939 --> 02:48:56.090 align:start position:0% different Optical Technologies from one to<02:48:54.120> the<02:48:54.240> other<02:48:54.420> and<02:48:55.140> this<02:48:55.380> the<02:48:55.680> benefit<02:48:55.859> of 02:48:56.090 --> 02:48:56.100 align:start position:0% to the other and this the benefit of 02:48:56.100 --> 02:48:57.530 align:start position:0% to the other and this the benefit of this<02:48:56.220> is<02:48:56.399> it<02:48:56.520> allows<02:48:56.819> a<02:48:56.939> network<02:48:57.060> to<02:48:57.359> be 02:48:57.530 --> 02:48:57.540 align:start position:0% this is it allows a network to be 02:48:57.540 --> 02:48:59.330 align:start position:0% this is it allows a network to be upgraded<02:48:58.080> without<02:48:58.620> actually<02:48:58.920> having<02:48:59.100> to 02:48:59.330 --> 02:48:59.340 align:start position:0% upgraded without actually having to 02:48:59.340 --> 02:49:01.490 align:start position:0% upgraded without actually having to upgrade<02:48:59.700> all<02:49:00.000> of<02:49:00.120> the<02:49:00.300> components<02:49:00.840> so<02:49:01.380> if 02:49:01.490 --> 02:49:01.500 align:start position:0% upgrade all of the components so if 02:49:01.500 --> 02:49:03.530 align:start position:0% upgrade all of the components so if we're<02:49:01.680> going<02:49:01.859> to<02:49:02.040> be<02:49:02.100> using<02:49:02.580> for<02:49:03.240> instance 02:49:03.530 --> 02:49:03.540 align:start position:0% we're going to be using for instance 02:49:03.540 --> 02:49:06.410 align:start position:0% we're going to be using for instance fiber<02:49:04.380> optics<02:49:04.740> and<02:49:05.399> copper<02:49:05.939> on<02:49:06.180> the<02:49:06.300> same 02:49:06.410 --> 02:49:06.420 align:start position:0% fiber optics and copper on the same 02:49:06.420 --> 02:49:07.910 align:start position:0% fiber optics and copper on the same network<02:49:06.720> this<02:49:07.380> is<02:49:07.439> something<02:49:07.680> that<02:49:07.859> we're 02:49:07.910 --> 02:49:07.920 align:start position:0% network this is something that we're 02:49:07.920 --> 02:49:09.590 align:start position:0% network this is something that we're really<02:49:08.100> going<02:49:08.280> to<02:49:08.460> want<02:49:08.580> I<02:49:09.240> wouldn't<02:49:09.359> worry 02:49:09.590 --> 02:49:09.600 align:start position:0% really going to want I wouldn't worry 02:49:09.600 --> 02:49:11.510 align:start position:0% really going to want I wouldn't worry too<02:49:09.840> much<02:49:10.020> about<02:49:10.200> transceivers<02:49:11.100> for<02:49:11.280> the 02:49:11.510 --> 02:49:11.520 align:start position:0% too much about transceivers for the 02:49:11.520 --> 02:49:13.010 align:start position:0% too much about transceivers for the network<02:49:11.640> plus<02:49:11.880> exam<02:49:12.240> but<02:49:12.479> I<02:49:12.600> did<02:49:12.720> want<02:49:12.840> to 02:49:13.010 --> 02:49:13.020 align:start position:0% network plus exam but I did want to 02:49:13.020 --> 02:49:14.990 align:start position:0% network plus exam but I did want to cover<02:49:13.080> them<02:49:13.319> because<02:49:13.500> they<02:49:13.740> are<02:49:13.859> listed<02:49:14.220> on 02:49:14.990 --> 02:49:15.000 align:start position:0% cover them because they are listed on 02:49:15.000 --> 02:49:16.370 align:start position:0% cover them because they are listed on the<02:49:15.780> um 02:49:16.370 --> 02:49:16.380 align:start position:0% the um 02:49:16.380 --> 02:49:19.190 align:start position:0% the um uh<02:49:17.040> on<02:49:17.220> the<02:49:17.399> outline<02:49:17.700> and<02:49:18.420> as<02:49:18.660> I<02:49:18.899> mentioned 02:49:19.190 --> 02:49:19.200 align:start position:0% uh on the outline and as I mentioned 02:49:19.200 --> 02:49:21.349 align:start position:0% uh on the outline and as I mentioned they're<02:49:19.500> really<02:49:19.680> built<02:49:20.160> onto<02:49:20.520> a<02:49:20.700> Nick<02:49:20.880> so<02:49:21.180> it's 02:49:21.349 --> 02:49:21.359 align:start position:0% they're really built onto a Nick so it's 02:49:21.359 --> 02:49:23.270 align:start position:0% they're really built onto a Nick so it's sort<02:49:21.540> of<02:49:21.660> a<02:49:21.899> subset<02:49:22.380> of<02:49:22.680> a<02:49:22.800> Nick<02:49:22.979> something 02:49:23.270 --> 02:49:23.280 align:start position:0% sort of a subset of a Nick something 02:49:23.280 --> 02:49:25.250 align:start position:0% sort of a subset of a Nick something that<02:49:23.580> is<02:49:23.700> on<02:49:24.060> the<02:49:24.180> Nick<02:49:24.300> that<02:49:24.600> allows<02:49:24.960> it<02:49:25.080> to 02:49:25.250 --> 02:49:25.260 align:start position:0% that is on the Nick that allows it to 02:49:25.260 --> 02:49:27.889 align:start position:0% that is on the Nick that allows it to transmit<02:49:25.680> and<02:49:25.979> receive<02:49:26.280> that<02:49:26.580> data<02:49:26.880> and<02:49:27.479> also 02:49:27.889 --> 02:49:27.899 align:start position:0% transmit and receive that data and also 02:49:27.899 --> 02:49:30.170 align:start position:0% transmit and receive that data and also allows<02:49:28.800> it<02:49:28.920> to<02:49:29.100> convert<02:49:29.460> sometimes<02:49:29.939> those 02:49:30.170 --> 02:49:30.180 align:start position:0% allows it to convert sometimes those 02:49:30.180 --> 02:49:32.150 align:start position:0% allows it to convert sometimes those signals<02:49:30.600> from<02:49:30.720> one<02:49:30.899> into<02:49:31.080> the<02:49:31.319> other<02:49:31.439> so<02:49:31.979> this 02:49:32.150 --> 02:49:32.160 align:start position:0% signals from one into the other so this 02:49:32.160 --> 02:49:33.469 align:start position:0% signals from one into the other so this is<02:49:32.220> how<02:49:32.399> a<02:49:32.580> computer<02:49:32.760> is<02:49:33.120> going<02:49:33.240> to<02:49:33.359> connect 02:49:33.469 --> 02:49:33.479 align:start position:0% is how a computer is going to connect 02:49:33.479 --> 02:49:36.530 align:start position:0% is how a computer is going to connect let's<02:49:33.840> talk<02:49:34.080> about<02:49:34.260> switches<02:49:34.979> a<02:49:35.760> switch<02:49:36.000> is<02:49:36.359> a 02:49:36.530 --> 02:49:36.540 align:start position:0% let's talk about switches a switch is a 02:49:36.540 --> 02:49:38.690 align:start position:0% let's talk about switches a switch is a connectivity<02:49:37.020> device<02:49:37.319> that<02:49:38.160> connects 02:49:38.690 --> 02:49:38.700 align:start position:0% connectivity device that connects 02:49:38.700 --> 02:49:41.929 align:start position:0% connectivity device that connects multiple<02:49:39.240> nodes<02:49:39.600> together<02:49:40.100> acting<02:49:41.100> as<02:49:41.340> the 02:49:41.929 --> 02:49:41.939 align:start position:0% multiple nodes together acting as the 02:49:41.939 --> 02:49:43.910 align:start position:0% multiple nodes together acting as the common<02:49:42.180> Connecting<02:49:42.899> Point<02:49:43.200> if<02:49:43.680> you<02:49:43.800> think 02:49:43.910 --> 02:49:43.920 align:start position:0% common Connecting Point if you think 02:49:43.920 --> 02:49:46.490 align:start position:0% common Connecting Point if you think back<02:49:44.220> to<02:49:44.460> our<02:49:44.760> start<02:49:44.939> topology<02:49:45.479> we<02:49:46.020> have<02:49:46.200> all 02:49:46.490 --> 02:49:46.500 align:start position:0% back to our start topology we have all 02:49:46.500 --> 02:49:49.429 align:start position:0% back to our start topology we have all the<02:49:46.740> nodes<02:49:47.040> connected<02:49:47.760> in<02:49:48.000> this<02:49:48.180> way<02:49:48.420> now<02:49:49.200> the 02:49:49.429 --> 02:49:49.439 align:start position:0% the nodes connected in this way now the 02:49:49.439 --> 02:49:52.490 align:start position:0% the nodes connected in this way now the switch<02:49:49.680> looks<02:49:50.340> at<02:49:50.460> something<02:49:50.819> called<02:49:51.720> the<02:49:52.260> MAC 02:49:52.490 --> 02:49:52.500 align:start position:0% switch looks at something called the MAC 02:49:52.500 --> 02:49:55.250 align:start position:0% switch looks at something called the MAC address<02:49:52.859> or<02:49:53.760> that<02:49:54.060> physical<02:49:54.359> address<02:49:54.780> that's 02:49:55.250 --> 02:49:55.260 align:start position:0% address or that physical address that's 02:49:55.260 --> 02:50:01.969 align:start position:0% address or that physical address that's burned<02:49:55.740> onto<02:49:56.600> the<02:49:57.600> uh<02:49:58.140> uh<02:49:58.680> Nick<02:49:59.520> it's<02:50:00.240> a<02:50:00.479> 48 02:50:01.969 --> 02:50:01.979 align:start position:0% burned onto the uh uh Nick it's a 48 02:50:01.979 --> 02:50:03.790 align:start position:0% burned onto the uh uh Nick it's a 48 bit 02:50:03.790 --> 02:50:03.800 align:start position:0% bit 02:50:03.800 --> 02:50:06.590 align:start position:0% bit hexadecimal<02:50:04.800> address<02:50:05.060> and<02:50:06.060> we<02:50:06.180> will<02:50:06.359> talk 02:50:06.590 --> 02:50:06.600 align:start position:0% hexadecimal address and we will talk 02:50:06.600 --> 02:50:08.690 align:start position:0% hexadecimal address and we will talk more<02:50:06.840> about<02:50:07.080> it<02:50:07.319> later 02:50:08.690 --> 02:50:08.700 align:start position:0% more about it later 02:50:08.700 --> 02:50:11.030 align:start position:0% more about it later and<02:50:09.479> what<02:50:09.840> it<02:50:09.960> does<02:50:10.080> is<02:50:10.260> it<02:50:10.380> looks<02:50:10.680> at<02:50:10.800> the<02:50:10.920> MAC 02:50:11.030 --> 02:50:11.040 align:start position:0% and what it does is it looks at the MAC 02:50:11.040 --> 02:50:13.849 align:start position:0% and what it does is it looks at the MAC address<02:50:11.280> of<02:50:12.120> each<02:50:12.359> packet<02:50:12.780> of<02:50:12.960> data<02:50:13.319> to<02:50:13.560> ensure 02:50:13.849 --> 02:50:13.859 align:start position:0% address of each packet of data to ensure 02:50:13.859 --> 02:50:16.429 align:start position:0% address of each packet of data to ensure the<02:50:14.160> data<02:50:14.520> goes<02:50:14.880> to<02:50:15.120> the<02:50:15.359> proper<02:50:15.840> destination 02:50:16.429 --> 02:50:16.439 align:start position:0% the data goes to the proper destination 02:50:16.439 --> 02:50:20.150 align:start position:0% the data goes to the proper destination or<02:50:17.220> to<02:50:17.460> the<02:50:17.819> node<02:50:18.300> for<02:50:18.479> which<02:50:18.660> it<02:50:18.899> is<02:50:19.080> meant<02:50:19.439> now 02:50:20.150 --> 02:50:20.160 align:start position:0% or to the node for which it is meant now 02:50:20.160 --> 02:50:23.210 align:start position:0% or to the node for which it is meant now because<02:50:20.700> of<02:50:21.180> this<02:50:21.359> because<02:50:21.780> the<02:50:22.260> switch<02:50:22.439> looks 02:50:23.210 --> 02:50:23.220 align:start position:0% because of this because the switch looks 02:50:23.220 --> 02:50:25.910 align:start position:0% because of this because the switch looks at<02:50:23.460> the<02:50:23.640> MAC<02:50:23.760> address<02:50:24.000> of<02:50:24.420> each<02:50:24.660> packet<02:50:25.200> it 02:50:25.910 --> 02:50:25.920 align:start position:0% at the MAC address of each packet it 02:50:25.920 --> 02:50:28.370 align:start position:0% at the MAC address of each packet it ensures<02:50:26.220> that<02:50:26.580> traffic<02:50:26.939> is<02:50:27.420> only<02:50:27.720> going<02:50:28.080> to 02:50:28.370 --> 02:50:28.380 align:start position:0% ensures that traffic is only going to 02:50:28.380 --> 02:50:32.990 align:start position:0% ensures that traffic is only going to the<02:50:28.620> intended<02:50:29.100> recipient<02:50:29.960> a<02:50:30.960> managed<02:50:31.439> switch 02:50:32.990 --> 02:50:33.000 align:start position:0% the intended recipient a managed switch 02:50:33.000 --> 02:50:35.570 align:start position:0% the intended recipient a managed switch just<02:50:33.359> going<02:50:33.540> to<02:50:33.660> write<02:50:33.780> that<02:50:34.020> in<02:50:34.200> here 02:50:35.570 --> 02:50:35.580 align:start position:0% just going to write that in here 02:50:35.580 --> 02:50:37.910 align:start position:0% just going to write that in here is<02:50:36.000> a<02:50:36.240> switch<02:50:36.359> that<02:50:36.600> allows<02:50:36.960> an<02:50:37.200> administrator 02:50:37.910 --> 02:50:37.920 align:start position:0% is a switch that allows an administrator 02:50:37.920 --> 02:50:41.809 align:start position:0% is a switch that allows an administrator access<02:50:38.819> to<02:50:39.420> its<02:50:39.780> configuration<02:50:40.380> and<02:50:41.340> is<02:50:41.460> able 02:50:41.809 --> 02:50:41.819 align:start position:0% access to its configuration and is able 02:50:41.819 --> 02:50:44.090 align:start position:0% access to its configuration and is able to<02:50:41.939> be<02:50:42.180> monitored<02:50:42.660> now<02:50:43.319> the<02:50:43.500> way<02:50:43.680> that<02:50:43.859> this 02:50:44.090 --> 02:50:44.100 align:start position:0% to be monitored now the way that this 02:50:44.100 --> 02:50:45.770 align:start position:0% to be monitored now the way that this works<02:50:44.580> is<02:50:44.760> that<02:50:45.000> there's<02:50:45.300> generally 02:50:45.770 --> 02:50:45.780 align:start position:0% works is that there's generally 02:50:45.780 --> 02:50:49.010 align:start position:0% works is that there's generally something<02:50:46.200> called<02:50:46.680> a<02:50:47.520> console<02:50:48.000> port<02:50:48.300> on<02:50:48.899> the 02:50:49.010 --> 02:50:49.020 align:start position:0% something called a console port on the 02:50:49.020 --> 02:50:50.990 align:start position:0% something called a console port on the back<02:50:49.140> of<02:50:49.380> the<02:50:49.560> device<02:50:49.740> and<02:50:50.340> you<02:50:50.520> use<02:50:50.700> something 02:50:50.990 --> 02:50:51.000 align:start position:0% back of the device and you use something 02:50:51.000 --> 02:50:54.290 align:start position:0% back of the device and you use something called<02:50:51.420> a<02:50:52.200> console<02:50:52.620> cable<02:50:53.160> in<02:50:53.819> order<02:50:53.939> to 02:50:54.290 --> 02:50:54.300 align:start position:0% called a console cable in order to 02:50:54.300 --> 02:50:57.110 align:start position:0% called a console cable in order to access<02:50:54.600> this<02:50:55.340> depending<02:50:56.340> on<02:50:56.520> the<02:50:56.640> manufacture 02:50:57.110 --> 02:50:57.120 align:start position:0% access this depending on the manufacture 02:50:57.120 --> 02:50:59.510 align:start position:0% access this depending on the manufacture of<02:50:57.300> the<02:50:57.479> switch<02:50:57.660> this<02:50:58.080> might<02:50:58.319> be<02:50:58.620> light<02:50:59.220> blue 02:50:59.510 --> 02:50:59.520 align:start position:0% of the switch this might be light blue 02:50:59.520 --> 02:51:02.090 align:start position:0% of the switch this might be light blue for<02:51:00.180> instance<02:51:00.359> in<02:51:00.660> Cisco<02:51:01.020> switches<02:51:01.500> which<02:51:01.920> is 02:51:02.090 --> 02:51:02.100 align:start position:0% for instance in Cisco switches which is 02:51:02.100 --> 02:51:04.309 align:start position:0% for instance in Cisco switches which is generally<02:51:02.460> the<02:51:02.880> most<02:51:03.060> common<02:51:03.479> and<02:51:04.020> sometimes 02:51:04.309 --> 02:51:04.319 align:start position:0% generally the most common and sometimes 02:51:04.319 --> 02:51:05.809 align:start position:0% generally the most common and sometimes you<02:51:04.439> might<02:51:04.560> have<02:51:04.680> light<02:51:04.979> yellow<02:51:05.280> or<02:51:05.640> orange 02:51:05.809 --> 02:51:05.819 align:start position:0% you might have light yellow or orange 02:51:05.819 --> 02:51:08.750 align:start position:0% you might have light yellow or orange for<02:51:06.180> others<02:51:06.540> now<02:51:07.140> switch<02:51:07.439> is<02:51:07.740> forward<02:51:08.220> traffic 02:51:08.750 --> 02:51:08.760 align:start position:0% for others now switch is forward traffic 02:51:08.760 --> 02:51:12.889 align:start position:0% for others now switch is forward traffic to<02:51:09.600> destination<02:51:10.260> nodes<02:51:10.920> via<02:51:11.819> these<02:51:12.180> ports<02:51:12.660> on 02:51:12.889 --> 02:51:12.899 align:start position:0% to destination nodes via these ports on 02:51:12.899 --> 02:51:16.010 align:start position:0% to destination nodes via these ports on the<02:51:13.020> switch 02:51:16.010 --> 02:51:16.020 align:start position:0% 02:51:16.020 --> 02:51:18.290 align:start position:0% and<02:51:16.500> there<02:51:16.680> might<02:51:16.859> be<02:51:16.979> as<02:51:17.160> little<02:51:17.399> as<02:51:17.700> uh<02:51:18.120> you 02:51:18.290 --> 02:51:18.300 align:start position:0% and there might be as little as uh you 02:51:18.300 --> 02:51:21.050 align:start position:0% and there might be as little as uh you know<02:51:18.420> a<02:51:18.540> few<02:51:18.660> ports<02:51:19.140> maybe<02:51:19.439> eight<02:51:19.920> four<02:51:20.280> or 02:51:21.050 --> 02:51:21.060 align:start position:0% know a few ports maybe eight four or 02:51:21.060 --> 02:51:24.050 align:start position:0% know a few ports maybe eight four or even<02:51:21.240> up<02:51:21.540> to<02:51:21.859> 168<02:51:22.859> or<02:51:23.100> more<02:51:23.280> now 02:51:24.050 --> 02:51:24.060 align:start position:0% even up to 168 or more now 02:51:24.060 --> 02:51:25.969 align:start position:0% even up to 168 or more now administrators<02:51:24.840> have<02:51:25.080> the<02:51:25.200> ability<02:51:25.380> to<02:51:25.680> do<02:51:25.800> a 02:51:25.969 --> 02:51:25.979 align:start position:0% administrators have the ability to do a 02:51:25.979 --> 02:51:27.290 align:start position:0% administrators have the ability to do a couple<02:51:26.100> different<02:51:26.340> things<02:51:26.640> the<02:51:27.000> first<02:51:27.120> thing 02:51:27.290 --> 02:51:27.300 align:start position:0% couple different things the first thing 02:51:27.300 --> 02:51:29.210 align:start position:0% couple different things the first thing they<02:51:27.420> can<02:51:27.540> do<02:51:27.660> is<02:51:27.780> do<02:51:27.960> something<02:51:28.140> called<02:51:28.439> Port 02:51:29.210 --> 02:51:29.220 align:start position:0% they can do is do something called Port 02:51:29.220 --> 02:51:30.469 align:start position:0% they can do is do something called Port mirroring 02:51:30.469 --> 02:51:30.479 align:start position:0% mirroring 02:51:30.479 --> 02:51:33.469 align:start position:0% mirroring Port<02:51:30.899> mirroring<02:51:31.680> effectively 02:51:33.469 --> 02:51:33.479 align:start position:0% Port mirroring effectively 02:51:33.479 --> 02:51:37.309 align:start position:0% Port mirroring effectively as<02:51:34.020> the<02:51:34.200> name<02:51:34.319> implies 02:51:37.309 --> 02:51:37.319 align:start position:0% 02:51:37.319 --> 02:51:39.710 align:start position:0% takes<02:51:37.920> all<02:51:38.280> the<02:51:38.520> traffic<02:51:38.760> on<02:51:39.240> a<02:51:39.420> specified 02:51:39.710 --> 02:51:39.720 align:start position:0% takes all the traffic on a specified 02:51:39.720 --> 02:51:43.010 align:start position:0% takes all the traffic on a specified port<02:51:40.080> and<02:51:40.439> replicates<02:51:40.979> it<02:51:41.220> or<02:51:41.819> copies<02:51:42.300> it<02:51:42.479> to 02:51:43.010 --> 02:51:43.020 align:start position:0% port and replicates it or copies it to 02:51:43.020 --> 02:51:49.250 align:start position:0% port and replicates it or copies it to another<02:51:43.260> port 02:51:49.250 --> 02:51:49.260 align:start position:0% 02:51:49.260 --> 02:51:52.370 align:start position:0% now<02:51:49.800> this<02:51:50.040> is<02:51:50.160> used<02:51:50.460> for<02:51:51.000> monitoring<02:51:51.720> for 02:51:52.370 --> 02:51:52.380 align:start position:0% now this is used for monitoring for 02:51:52.380 --> 02:51:53.809 align:start position:0% now this is used for monitoring for instance<02:51:52.560> if<02:51:52.740> I<02:51:52.920> want<02:51:53.100> to<02:51:53.279> see<02:51:53.399> what's<02:51:53.640> going 02:51:53.809 --> 02:51:53.819 align:start position:0% instance if I want to see what's going 02:51:53.819 --> 02:51:55.370 align:start position:0% instance if I want to see what's going on<02:51:54.000> in<02:51:54.180> a<02:51:54.300> port<02:51:54.420> but<02:51:54.660> I<02:51:54.779> don't<02:51:54.899> want<02:51:55.020> to<02:51:55.200> stop 02:51:55.370 --> 02:51:55.380 align:start position:0% on in a port but I don't want to stop 02:51:55.380 --> 02:51:57.590 align:start position:0% on in a port but I don't want to stop the<02:51:55.620> traffic<02:51:55.800> I<02:51:56.279> can<02:51:56.460> monitor<02:51:57.120> this<02:51:57.359> traffic 02:51:57.590 --> 02:51:57.600 align:start position:0% the traffic I can monitor this traffic 02:51:57.600 --> 02:51:59.990 align:start position:0% the traffic I can monitor this traffic for<02:51:58.080> analysis<02:51:58.680> and<02:51:58.920> diagnostic<02:51:59.520> purposes 02:51:59.990 --> 02:52:00.000 align:start position:0% for analysis and diagnostic purposes 02:52:00.000 --> 02:52:02.090 align:start position:0% for analysis and diagnostic purposes it's<02:52:00.660> also<02:52:00.899> going<02:52:01.020> to<02:52:01.140> allow<02:52:01.380> administrators 02:52:02.090 --> 02:52:02.100 align:start position:0% it's also going to allow administrators 02:52:02.100 --> 02:52:04.550 align:start position:0% it's also going to allow administrators to<02:52:02.460> diagnose<02:52:03.120> whether<02:52:03.479> traffic<02:52:03.840> across<02:52:04.439> the 02:52:04.550 --> 02:52:04.560 align:start position:0% to diagnose whether traffic across the 02:52:04.560 --> 02:52:06.590 align:start position:0% to diagnose whether traffic across the port<02:52:04.740> is<02:52:05.040> being<02:52:05.220> interfered<02:52:05.819> with<02:52:05.939> by<02:52:06.300> a 02:52:06.590 --> 02:52:06.600 align:start position:0% port is being interfered with by a 02:52:06.600 --> 02:52:08.630 align:start position:0% port is being interfered with by a nefarious<02:52:07.140> individual<02:52:07.859> or<02:52:08.100> someone<02:52:08.340> who's 02:52:08.630 --> 02:52:08.640 align:start position:0% nefarious individual or someone who's 02:52:08.640 --> 02:52:11.450 align:start position:0% nefarious individual or someone who's has<02:52:09.060> a<02:52:09.300> malicious<02:52:09.600> intent<02:52:10.020> such<02:52:10.319> as<02:52:10.439> a<02:52:10.620> hacker 02:52:11.450 --> 02:52:11.460 align:start position:0% has a malicious intent such as a hacker 02:52:11.460 --> 02:52:14.570 align:start position:0% has a malicious intent such as a hacker now<02:52:12.000> if<02:52:12.479> administrators<02:52:13.319> want<02:52:13.800> to<02:52:13.979> combine 02:52:14.570 --> 02:52:14.580 align:start position:0% now if administrators want to combine 02:52:14.580 --> 02:52:18.830 align:start position:0% now if administrators want to combine two<02:52:15.359> or<02:52:15.540> more<02:52:15.720> network<02:52:16.020> connections 02:52:18.830 --> 02:52:18.840 align:start position:0% two or more network connections 02:52:18.840 --> 02:52:27.070 align:start position:0% two or more network connections it's<02:52:19.740> called<02:52:20.040> link<02:52:20.520> aggregation 02:52:27.070 --> 02:52:27.080 align:start position:0% 02:52:27.080 --> 02:52:31.550 align:start position:0% or<02:52:28.080> Port<02:52:28.560> teaming 02:52:31.550 --> 02:52:31.560 align:start position:0% 02:52:31.560 --> 02:52:34.190 align:start position:0% and<02:52:32.340> there<02:52:32.460> are<02:52:32.640> other<02:52:32.700> names<02:52:33.000> as<02:52:33.300> well<02:52:33.479> what 02:52:34.190 --> 02:52:34.200 align:start position:0% and there are other names as well what 02:52:34.200 --> 02:52:36.530 align:start position:0% and there are other names as well what this<02:52:34.380> does<02:52:34.620> is<02:52:34.859> this<02:52:35.160> serves<02:52:35.520> to<02:52:35.819> increase<02:52:36.120> or 02:52:36.530 --> 02:52:36.540 align:start position:0% this does is this serves to increase or 02:52:36.540 --> 02:52:39.290 align:start position:0% this does is this serves to increase or effectively<02:52:37.020> double<02:52:37.319> the<02:52:37.560> bandwidth<02:52:38.160> uh<02:52:39.120> as 02:52:39.290 --> 02:52:39.300 align:start position:0% effectively double the bandwidth uh as 02:52:39.300 --> 02:52:41.030 align:start position:0% effectively double the bandwidth uh as well<02:52:39.420> as<02:52:39.600> allow<02:52:39.960> for<02:52:40.140> some<02:52:40.380> redundancy 02:52:41.030 --> 02:52:41.040 align:start position:0% well as allow for some redundancy 02:52:41.040 --> 02:52:44.389 align:start position:0% well as allow for some redundancy obviously<02:52:41.580> or<02:52:42.479> a<02:52:42.720> backup<02:52:43.140> connection<02:52:43.399> or 02:52:44.389 --> 02:52:44.399 align:start position:0% obviously or a backup connection or 02:52:44.399 --> 02:52:46.070 align:start position:0% obviously or a backup connection or something<02:52:44.640> else<02:52:44.880> another 02:52:46.070 --> 02:52:46.080 align:start position:0% something else another 02:52:46.080 --> 02:52:48.710 align:start position:0% something else another name<02:52:46.560> you<02:52:46.800> might<02:52:46.979> see<02:52:47.160> this<02:52:47.399> as<02:52:47.760> by<02:52:48.060> the<02:52:48.180> way<02:52:48.300> is 02:52:48.710 --> 02:52:48.720 align:start position:0% name you might see this as by the way is 02:52:48.720 --> 02:52:50.090 align:start position:0% name you might see this as by the way is trunking 02:52:50.090 --> 02:52:50.100 align:start position:0% trunking 02:52:50.100 --> 02:52:53.990 align:start position:0% trunking so<02:52:50.580> that's<02:52:50.700> the<02:52:50.880> one<02:52:51.000> I<02:52:51.120> most<02:52:51.300> see<02:52:51.479> on<02:52:51.720> the<02:52:51.899> exam 02:52:53.990 --> 02:52:54.000 align:start position:0% so that's the one I most see on the exam 02:52:54.000 --> 02:52:56.630 align:start position:0% so that's the one I most see on the exam so<02:52:54.479> that's<02:52:54.779> again<02:52:55.319> taking<02:52:55.680> two<02:52:56.040> and<02:52:56.340> sort<02:52:56.520> of 02:52:56.630 --> 02:52:56.640 align:start position:0% so that's again taking two and sort of 02:52:56.640 --> 02:52:58.070 align:start position:0% so that's again taking two and sort of treating<02:52:56.880> them<02:52:57.000> as<02:52:57.180> one 02:52:58.070 --> 02:52:58.080 align:start position:0% treating them as one 02:52:58.080 --> 02:53:00.530 align:start position:0% treating them as one finally<02:52:58.680> we<02:52:58.859> have<02:52:59.040> something<02:52:59.340> called<02:52:59.760> Channel 02:53:00.530 --> 02:53:00.540 align:start position:0% finally we have something called Channel 02:53:00.540 --> 02:53:07.550 align:start position:0% finally we have something called Channel bonding 02:53:07.550 --> 02:53:07.560 align:start position:0% 02:53:07.560 --> 02:53:10.070 align:start position:0% which<02:53:08.100> is<02:53:08.340> the<02:53:08.520> process<02:53:08.760> of<02:53:09.000> adding<02:53:09.420> multiple 02:53:10.070 --> 02:53:10.080 align:start position:0% which is the process of adding multiple 02:53:10.080 --> 02:53:11.630 align:start position:0% which is the process of adding multiple Nicks 02:53:11.630 --> 02:53:11.640 align:start position:0% Nicks 02:53:11.640 --> 02:53:17.630 align:start position:0% Nicks to<02:53:11.880> one 02:53:17.630 --> 02:53:17.640 align:start position:0% 02:53:17.640 --> 02:53:20.389 align:start position:0% Mac<02:53:18.120> address 02:53:20.389 --> 02:53:20.399 align:start position:0% 02:53:20.399 --> 02:53:22.550 align:start position:0% this<02:53:20.760> is<02:53:20.880> also<02:53:21.120> called<02:53:21.300> Nick<02:53:21.600> bonding<02:53:22.200> and 02:53:22.550 --> 02:53:22.560 align:start position:0% this is also called Nick bonding and 02:53:22.560 --> 02:53:24.110 align:start position:0% this is also called Nick bonding and we'll<02:53:22.740> discuss<02:53:23.040> it<02:53:23.220> in<02:53:23.340> Greater<02:53:23.640> detail<02:53:23.939> when 02:53:24.110 --> 02:53:24.120 align:start position:0% we'll discuss it in Greater detail when 02:53:24.120 --> 02:53:26.389 align:start position:0% we'll discuss it in Greater detail when we're<02:53:24.300> talking<02:53:24.479> about<02:53:24.779> IP<02:53:25.560> addresses<02:53:26.100> and 02:53:26.389 --> 02:53:26.399 align:start position:0% we're talking about IP addresses and 02:53:26.399 --> 02:53:29.570 align:start position:0% we're talking about IP addresses and some<02:53:26.580> of<02:53:26.640> the<02:53:26.760> other<02:53:26.880> protocols 02:53:29.570 --> 02:53:29.580 align:start position:0% some of the other protocols 02:53:29.580 --> 02:53:32.150 align:start position:0% some of the other protocols as<02:53:30.120> opposed<02:53:30.479> to<02:53:30.540> a<02:53:30.779> switch<02:53:30.960> a<02:53:31.560> router<02:53:31.920> is<02:53:32.040> a 02:53:32.150 --> 02:53:32.160 align:start position:0% as opposed to a switch a router is a 02:53:32.160 --> 02:53:34.130 align:start position:0% as opposed to a switch a router is a connectivity<02:53:32.640> device<02:53:32.880> that<02:53:33.720> typically 02:53:34.130 --> 02:53:34.140 align:start position:0% connectivity device that typically 02:53:34.140 --> 02:53:36.410 align:start position:0% connectivity device that typically connects<02:53:35.040> multiple<02:53:35.640> networks<02:53:36.060> or<02:53:36.240> network 02:53:36.410 --> 02:53:36.420 align:start position:0% connects multiple networks or network 02:53:36.420 --> 02:53:39.290 align:start position:0% connects multiple networks or network segments<02:53:37.080> and<02:53:37.800> unlike<02:53:38.160> the<02:53:38.399> switch<02:53:38.580> it<02:53:39.060> looks 02:53:39.290 --> 02:53:39.300 align:start position:0% segments and unlike the switch it looks 02:53:39.300 --> 02:53:42.110 align:start position:0% segments and unlike the switch it looks at<02:53:39.420> the<02:53:39.660> IP<02:53:40.080> address<02:53:40.319> of<02:53:40.979> each<02:53:41.160> packet<02:53:41.580> of<02:53:41.760> data 02:53:42.110 --> 02:53:42.120 align:start position:0% at the IP address of each packet of data 02:53:42.120 --> 02:53:45.230 align:start position:0% at the IP address of each packet of data to<02:53:42.779> forward<02:53:43.020> the<02:53:43.439> to<02:53:43.740> the<02:53:44.100> destination<02:53:44.760> node 02:53:45.230 --> 02:53:45.240 align:start position:0% to forward the to the destination node 02:53:45.240 --> 02:53:48.050 align:start position:0% to forward the to the destination node so<02:53:45.479> instead<02:53:45.840> of<02:53:45.899> the<02:53:46.080> MAC<02:53:46.260> address<02:53:46.819> uh<02:53:47.819> we're 02:53:48.050 --> 02:53:48.060 align:start position:0% so instead of the MAC address uh we're 02:53:48.060 --> 02:53:51.650 align:start position:0% so instead of the MAC address uh we're looking<02:53:48.300> at<02:53:48.720> the<02:53:49.080> IP<02:53:50.040> address<02:53:50.279> now<02:53:51.060> a<02:53:51.300> router 02:53:51.650 --> 02:53:51.660 align:start position:0% looking at the IP address now a router 02:53:51.660 --> 02:53:53.210 align:start position:0% looking at the IP address now a router is<02:53:51.779> usually<02:53:51.960> used<02:53:52.140> to<02:53:52.319> connect<02:53:52.439> networks<02:53:53.040> that 02:53:53.210 --> 02:53:53.220 align:start position:0% is usually used to connect networks that 02:53:53.220 --> 02:53:56.630 align:start position:0% is usually used to connect networks that use<02:53:53.460> the<02:53:53.939> same<02:53:54.180> routable<02:53:55.140> protocols<02:53:56.040> so<02:53:56.460> a 02:53:56.630 --> 02:53:56.640 align:start position:0% use the same routable protocols so a 02:53:56.640 --> 02:53:59.450 align:start position:0% use the same routable protocols so a routable<02:53:56.939> protocol<02:53:57.380> is<02:53:58.380> any<02:53:58.740> protocol<02:53:59.040> that 02:53:59.450 --> 02:53:59.460 align:start position:0% routable protocol is any protocol that 02:53:59.460 --> 02:54:04.670 align:start position:0% routable protocol is any protocol that identifies<02:54:00.380> the<02:54:01.380> node 02:54:04.670 --> 02:54:04.680 align:start position:0% 02:54:04.680 --> 02:54:06.830 align:start position:0% versus 02:54:06.830 --> 02:54:06.840 align:start position:0% versus 02:54:06.840 --> 02:54:11.630 align:start position:0% versus the<02:54:07.500> network 02:54:11.630 --> 02:54:11.640 align:start position:0% 02:54:11.640 --> 02:54:13.730 align:start position:0% using 02:54:13.730 --> 02:54:13.740 align:start position:0% using 02:54:13.740 --> 02:54:16.370 align:start position:0% using addressing 02:54:16.370 --> 02:54:16.380 align:start position:0% addressing 02:54:16.380 --> 02:54:20.030 align:start position:0% addressing I.E<02:54:17.160> the<02:54:17.520> IP<02:54:17.819> address<02:54:18.140> now<02:54:19.140> a<02:54:19.380> router<02:54:19.680> can<02:54:19.859> be 02:54:20.030 --> 02:54:20.040 align:start position:0% I.E the IP address now a router can be 02:54:20.040 --> 02:54:22.730 align:start position:0% I.E the IP address now a router can be installed<02:54:20.520> as<02:54:20.640> a<02:54:20.880> hardware<02:54:21.000> device<02:54:21.560> as<02:54:22.560> a 02:54:22.730 --> 02:54:22.740 align:start position:0% installed as a hardware device as a 02:54:22.740 --> 02:54:24.830 align:start position:0% installed as a hardware device as a function<02:54:22.979> of<02:54:23.220> a<02:54:23.399> multi-function<02:54:24.000> device<02:54:24.300> like 02:54:24.830 --> 02:54:24.840 align:start position:0% function of a multi-function device like 02:54:24.840 --> 02:54:28.510 align:start position:0% function of a multi-function device like a<02:54:25.279> Soho<02:54:26.279> router 02:54:28.510 --> 02:54:28.520 align:start position:0% a Soho router 02:54:28.520 --> 02:54:32.030 align:start position:0% a Soho router and<02:54:29.520> uh<02:54:30.120> it's<02:54:30.600> also<02:54:31.080> can<02:54:31.200> be<02:54:31.380> installed<02:54:31.859> as 02:54:32.030 --> 02:54:32.040 align:start position:0% and uh it's also can be installed as 02:54:32.040 --> 02:54:34.010 align:start position:0% and uh it's also can be installed as software<02:54:32.580> in<02:54:32.760> another<02:54:32.939> device<02:54:33.240> in<02:54:33.600> a<02:54:33.720> virtual 02:54:34.010 --> 02:54:34.020 align:start position:0% software in another device in a virtual 02:54:34.020 --> 02:54:36.410 align:start position:0% software in another device in a virtual environment<02:54:34.500> for<02:54:34.859> instance<02:54:35.040> on<02:54:35.340> a<02:54:35.460> server<02:54:35.760> in 02:54:36.410 --> 02:54:36.420 align:start position:0% environment for instance on a server in 02:54:36.420 --> 02:54:38.330 align:start position:0% environment for instance on a server in the<02:54:36.600> case<02:54:36.720> of<02:54:36.899> a<02:54:37.140> router<02:54:37.500> being<02:54:37.680> installed<02:54:38.220> as 02:54:38.330 --> 02:54:38.340 align:start position:0% the case of a router being installed as 02:54:38.340 --> 02:54:41.090 align:start position:0% the case of a router being installed as software<02:54:38.760> in<02:54:38.939> a<02:54:39.120> virtual<02:54:39.840> environment<02:54:40.319> the 02:54:41.090 --> 02:54:41.100 align:start position:0% software in a virtual environment the 02:54:41.100 --> 02:54:43.670 align:start position:0% software in a virtual environment the device<02:54:41.340> or<02:54:41.760> node<02:54:42.060> has<02:54:42.420> to<02:54:42.600> have 02:54:43.670 --> 02:54:43.680 align:start position:0% device or node has to have 02:54:43.680 --> 02:54:45.950 align:start position:0% device or node has to have two<02:54:44.279> Nicks<02:54:44.700> one<02:54:44.939> Nick<02:54:45.120> for<02:54:45.300> the<02:54:45.420> note<02:54:45.540> itself 02:54:45.950 --> 02:54:45.960 align:start position:0% two Nicks one Nick for the note itself 02:54:45.960 --> 02:54:47.570 align:start position:0% two Nicks one Nick for the note itself and<02:54:46.500> then<02:54:46.560> one<02:54:46.800> Nick<02:54:46.920> for<02:54:47.220> the<02:54:47.340> routing 02:54:47.570 --> 02:54:47.580 align:start position:0% and then one Nick for the routing 02:54:47.580 --> 02:54:49.309 align:start position:0% and then one Nick for the routing functions<02:54:48.060> sort<02:54:48.300> of<02:54:48.359> like<02:54:48.479> one<02:54:48.660> to<02:54:48.899> go<02:54:49.020> in<02:54:49.140> and 02:54:49.309 --> 02:54:49.319 align:start position:0% functions sort of like one to go in and 02:54:49.319 --> 02:54:52.250 align:start position:0% functions sort of like one to go in and one<02:54:49.500> to<02:54:49.680> go<02:54:49.800> out<02:54:50.000> a<02:54:51.000> Gateway<02:54:51.420> is<02:54:52.080> a 02:54:52.250 --> 02:54:52.260 align:start position:0% one to go out a Gateway is a 02:54:52.260 --> 02:54:53.990 align:start position:0% one to go out a Gateway is a connectivity<02:54:52.680> device<02:54:52.920> that's<02:54:53.340> very<02:54:53.819> much 02:54:53.990 --> 02:54:54.000 align:start position:0% connectivity device that's very much 02:54:54.000 --> 02:54:55.730 align:start position:0% connectivity device that's very much like<02:54:54.300> a<02:54:54.540> router<02:54:54.779> in<02:54:54.899> the<02:54:55.020> way<02:54:55.140> it<02:54:55.260> functions 02:54:55.730 --> 02:54:55.740 align:start position:0% like a router in the way it functions 02:54:55.740 --> 02:54:58.070 align:start position:0% like a router in the way it functions and<02:54:56.340> it<02:54:56.580> routes<02:54:56.939> traffic<02:54:57.180> in<02:54:57.540> much<02:54:57.720> the<02:54:57.899> same 02:54:58.070 --> 02:54:58.080 align:start position:0% and it routes traffic in much the same 02:54:58.080 --> 02:55:00.170 align:start position:0% and it routes traffic in much the same way<02:54:58.260> but<02:54:59.040> the<02:54:59.160> difference<02:54:59.279> between<02:54:59.580> a<02:54:59.880> Gateway 02:55:00.170 --> 02:55:00.180 align:start position:0% way but the difference between a Gateway 02:55:00.180 --> 02:55:02.210 align:start position:0% way but the difference between a Gateway and<02:55:00.359> a<02:55:00.479> router<02:55:00.779> is<02:55:01.020> that<02:55:01.140> a<02:55:01.319> Gateway<02:55:01.680> connects 02:55:02.210 --> 02:55:02.220 align:start position:0% and a router is that a Gateway connects 02:55:02.220 --> 02:55:04.790 align:start position:0% and a router is that a Gateway connects networks<02:55:02.580> that<02:55:02.760> have<02:55:03.060> different<02:55:03.899> protocols 02:55:04.790 --> 02:55:04.800 align:start position:0% networks that have different protocols 02:55:04.800 --> 02:55:07.070 align:start position:0% networks that have different protocols or<02:55:05.160> dissimilar<02:55:05.939> protocols<02:55:06.660> that<02:55:06.899> to 02:55:07.070 --> 02:55:07.080 align:start position:0% or dissimilar protocols that to 02:55:07.080 --> 02:55:09.469 align:start position:0% or dissimilar protocols that to communicate<02:55:07.620> so<02:55:08.220> the<02:55:08.399> Gateway<02:55:08.700> performs<02:55:09.300> the 02:55:09.469 --> 02:55:09.479 align:start position:0% communicate so the Gateway performs the 02:55:09.479 --> 02:55:11.590 align:start position:0% communicate so the Gateway performs the translation<02:55:10.080> between 02:55:11.590 --> 02:55:11.600 align:start position:0% translation between 02:55:11.600 --> 02:55:14.630 align:start position:0% translation between incompatible<02:55:12.600> networks<02:55:13.260> uh<02:55:14.220> I'm<02:55:14.399> just<02:55:14.520> going 02:55:14.630 --> 02:55:14.640 align:start position:0% incompatible networks uh I'm just going 02:55:14.640 --> 02:55:16.490 align:start position:0% incompatible networks uh I'm just going to<02:55:14.760> put<02:55:14.880> translation<02:55:15.540> here<02:55:15.899> since<02:55:16.140> I<02:55:16.319> think 02:55:16.490 --> 02:55:16.500 align:start position:0% to put translation here since I think 02:55:16.500 --> 02:55:21.070 align:start position:0% to put translation here since I think that's<02:55:16.740> pretty<02:55:17.160> important 02:55:21.070 --> 02:55:21.080 align:start position:0% 02:55:21.080 --> 02:55:22.730 align:start position:0% or 02:55:22.730 --> 02:55:22.740 align:start position:0% or 02:55:22.740 --> 02:55:26.150 align:start position:0% or even<02:55:23.399> different<02:55:23.760> uh<02:55:24.359> email<02:55:24.720> systems<02:55:25.500> or 02:55:26.150 --> 02:55:26.160 align:start position:0% even different uh email systems or 02:55:26.160 --> 02:55:28.490 align:start position:0% even different uh email systems or operating<02:55:26.580> systems<02:55:27.180> now<02:55:27.660> although<02:55:27.960> it<02:55:28.200> can<02:55:28.319> be 02:55:28.490 --> 02:55:28.500 align:start position:0% operating systems now although it can be 02:55:28.500 --> 02:55:31.610 align:start position:0% operating systems now although it can be easy<02:55:28.859> to<02:55:29.279> confuse<02:55:29.760> a<02:55:30.180> Gateway<02:55:30.540> with<02:55:31.080> the 02:55:31.610 --> 02:55:31.620 align:start position:0% easy to confuse a Gateway with the 02:55:31.620 --> 02:55:33.710 align:start position:0% easy to confuse a Gateway with the default<02:55:32.279> gateway<02:55:32.700> that<02:55:32.939> we<02:55:33.060> see<02:55:33.240> when<02:55:33.420> we<02:55:33.540> do 02:55:33.710 --> 02:55:33.720 align:start position:0% default gateway that we see when we do 02:55:33.720 --> 02:55:44.150 align:start position:0% default gateway that we see when we do an<02:55:34.080> ipconfig<02:55:35.040> it's<02:55:35.640> not<02:55:36.000> the<02:55:36.420> same<02:55:36.600> thing 02:55:44.150 --> 02:55:44.160 align:start position:0% 02:55:44.160 --> 02:55:46.730 align:start position:0% a<02:55:44.700> Gateway<02:55:45.060> is<02:55:45.479> a<02:55:45.660> device<02:55:45.840> on<02:55:46.140> the<02:55:46.260> edge<02:55:46.380> of<02:55:46.620> the 02:55:46.730 --> 02:55:46.740 align:start position:0% a Gateway is a device on the edge of the 02:55:46.740 --> 02:55:49.309 align:start position:0% a Gateway is a device on the edge of the network<02:55:46.920> that's<02:55:47.819> used<02:55:48.300> to<02:55:48.540> convert<02:55:49.020> traffic 02:55:49.309 --> 02:55:49.319 align:start position:0% network that's used to convert traffic 02:55:49.319 --> 02:55:51.710 align:start position:0% network that's used to convert traffic between<02:55:49.740> different<02:55:50.100> systems<02:55:50.580> while<02:55:50.819> as<02:55:51.060> this 02:55:51.710 --> 02:55:51.720 align:start position:0% between different systems while as this 02:55:51.720 --> 02:55:54.889 align:start position:0% between different systems while as this default<02:55:52.200> gateway<02:55:52.680> is<02:55:53.640> simply<02:55:54.060> forwards<02:55:54.540> data 02:55:54.889 --> 02:55:54.899 align:start position:0% default gateway is simply forwards data 02:55:54.899 --> 02:55:57.410 align:start position:0% default gateway is simply forwards data packets<02:55:55.260> in<02:55:55.680> TCP<02:55:56.220> so<02:55:56.760> we're<02:55:56.939> going<02:55:57.060> to<02:55:57.180> discuss 02:55:57.410 --> 02:55:57.420 align:start position:0% packets in TCP so we're going to discuss 02:55:57.420 --> 02:55:59.210 align:start position:0% packets in TCP so we're going to discuss that<02:55:57.720> in<02:55:58.080> more<02:55:58.260> detail<02:55:58.560> later<02:55:58.800> but<02:55:59.040> I<02:55:59.160> just 02:55:59.210 --> 02:55:59.220 align:start position:0% that in more detail later but I just 02:55:59.220 --> 02:56:00.530 align:start position:0% that in more detail later but I just want<02:55:59.340> to<02:55:59.460> point<02:55:59.580> out<02:55:59.700> this<02:55:59.939> is<02:56:00.060> not<02:56:00.240> the 02:56:00.530 --> 02:56:00.540 align:start position:0% want to point out this is not the 02:56:00.540 --> 02:56:04.010 align:start position:0% want to point out this is not the default<02:56:01.260> gateway<02:56:01.800> and<02:56:02.520> just<02:56:02.939> like<02:56:03.300> a<02:56:03.600> router 02:56:04.010 --> 02:56:04.020 align:start position:0% default gateway and just like a router 02:56:04.020 --> 02:56:05.929 align:start position:0% default gateway and just like a router by<02:56:04.200> the<02:56:04.319> way<02:56:04.439> it<02:56:04.740> can<02:56:04.920> be<02:56:05.100> a<02:56:05.340> hardware<02:56:05.460> device 02:56:05.929 --> 02:56:05.939 align:start position:0% by the way it can be a hardware device 02:56:05.939 --> 02:56:08.630 align:start position:0% by the way it can be a hardware device or<02:56:06.899> software<02:56:07.380> within<02:56:07.800> a<02:56:07.979> router<02:56:08.279> or<02:56:08.460> on 02:56:08.630 --> 02:56:08.640 align:start position:0% or software within a router or on 02:56:08.640 --> 02:56:11.090 align:start position:0% or software within a router or on another<02:56:08.760> virtual<02:56:09.240> device<02:56:09.560> and<02:56:10.560> it<02:56:10.800> uses 02:56:11.090 --> 02:56:11.100 align:start position:0% another virtual device and it uses 02:56:11.100 --> 02:56:13.370 align:start position:0% another virtual device and it uses radical<02:56:11.580> protocols<02:56:12.060> that<02:56:12.240> are<02:56:12.420> similar<02:56:12.840> to<02:56:13.200> a 02:56:13.370 --> 02:56:13.380 align:start position:0% radical protocols that are similar to a 02:56:13.380 --> 02:56:15.349 align:start position:0% radical protocols that are similar to a router<02:56:13.800> but<02:56:14.340> again<02:56:14.520> it<02:56:14.819> allows<02:56:15.180> the 02:56:15.349 --> 02:56:15.359 align:start position:0% router but again it allows the 02:56:15.359 --> 02:56:17.389 align:start position:0% router but again it allows the translation<02:56:15.960> between<02:56:16.380> different<02:56:16.800> types<02:56:17.279> of 02:56:17.389 --> 02:56:17.399 align:start position:0% translation between different types of 02:56:17.399 --> 02:56:23.870 align:start position:0% translation between different types of protocols 02:56:23.870 --> 02:56:23.880 align:start position:0% 02:56:23.880 --> 02:56:26.330 align:start position:0% now<02:56:24.720> let's<02:56:24.840> look<02:56:24.960> at<02:56:25.140> virtualization<02:56:25.920> a<02:56:26.160> bit 02:56:26.330 --> 02:56:26.340 align:start position:0% now let's look at virtualization a bit 02:56:26.340 --> 02:56:28.309 align:start position:0% now let's look at virtualization a bit since<02:56:26.520> this<02:56:26.760> is<02:56:26.880> really<02:56:27.060> the<02:56:27.479> the<02:56:27.720> big<02:56:28.080> thing 02:56:28.309 --> 02:56:28.319 align:start position:0% since this is really the the big thing 02:56:28.319 --> 02:56:31.250 align:start position:0% since this is really the the big thing in<02:56:28.560> Computing<02:56:28.979> nowadays<02:56:29.580> a<02:56:30.540> virtual<02:56:30.840> switch 02:56:31.250 --> 02:56:31.260 align:start position:0% in Computing nowadays a virtual switch 02:56:31.260 --> 02:56:34.130 align:start position:0% in Computing nowadays a virtual switch for<02:56:31.979> instance<02:56:32.240> functions<02:56:33.240> just<02:56:33.660> like<02:56:33.899> a 02:56:34.130 --> 02:56:34.140 align:start position:0% for instance functions just like a 02:56:34.140 --> 02:56:36.290 align:start position:0% for instance functions just like a physical<02:56:34.260> switch<02:56:34.680> you<02:56:35.340> cannot<02:56:35.700> however 02:56:36.290 --> 02:56:36.300 align:start position:0% physical switch you cannot however 02:56:36.300 --> 02:56:39.110 align:start position:0% physical switch you cannot however directly<02:56:37.260> communicate<02:56:37.740> between<02:56:38.040> two<02:56:38.700> virtual 02:56:39.110 --> 02:56:39.120 align:start position:0% directly communicate between two virtual 02:56:39.120 --> 02:56:41.150 align:start position:0% directly communicate between two virtual switches<02:56:39.660> if<02:56:40.200> you<02:56:40.319> want<02:56:40.439> to<02:56:40.560> do<02:56:40.680> that<02:56:40.800> you<02:56:41.040> need 02:56:41.150 --> 02:56:41.160 align:start position:0% switches if you want to do that you need 02:56:41.160 --> 02:56:43.610 align:start position:0% switches if you want to do that you need a<02:56:41.460> virtual<02:56:41.760> router<02:56:42.180> or<02:56:42.359> a<02:56:42.420> router<02:56:42.840> now<02:56:43.380> a 02:56:43.610 --> 02:56:43.620 align:start position:0% a virtual router or a router now a 02:56:43.620 --> 02:56:46.309 align:start position:0% a virtual router or a router now a Virtual<02:56:43.979> Router<02:56:44.520> is<02:56:45.300> the<02:56:45.600> software<02:56:45.960> that<02:56:46.200> can 02:56:46.309 --> 02:56:46.319 align:start position:0% Virtual Router is the software that can 02:56:46.319 --> 02:56:48.410 align:start position:0% Virtual Router is the software that can be<02:56:46.439> installed<02:56:46.859> on<02:56:46.979> a<02:56:47.160> device<02:56:47.279> with<02:56:47.819> two<02:56:48.060> nics 02:56:48.410 --> 02:56:48.420 align:start position:0% be installed on a device with two nics 02:56:48.420 --> 02:56:51.650 align:start position:0% be installed on a device with two nics for<02:56:48.660> routing<02:56:49.080> traffic<02:56:49.380> a<02:56:50.340> virtual<02:56:50.700> server<02:56:51.180> is 02:56:51.650 --> 02:56:51.660 align:start position:0% for routing traffic a virtual server is 02:56:51.660 --> 02:56:53.929 align:start position:0% for routing traffic a virtual server is a<02:56:51.840> server<02:56:52.140> that<02:56:52.319> operates<02:56:52.740> independently<02:56:53.640> of 02:56:53.929 --> 02:56:53.939 align:start position:0% a server that operates independently of 02:56:53.939 --> 02:56:57.110 align:start position:0% a server that operates independently of its<02:56:54.180> host<02:56:54.359> machine<02:56:54.899> meaning<02:56:55.859> that<02:56:56.220> it's<02:56:56.760> all 02:56:57.110 --> 02:56:57.120 align:start position:0% its host machine meaning that it's all 02:56:57.120 --> 02:57:00.110 align:start position:0% its host machine meaning that it's all software<02:56:57.600> based<02:56:58.080> CPU<02:56:58.620> Ram<02:56:59.100> Etc<02:56:59.279> can<02:56:59.880> be 02:57:00.110 --> 02:57:00.120 align:start position:0% software based CPU Ram Etc can be 02:57:00.120 --> 02:57:02.690 align:start position:0% software based CPU Ram Etc can be independent<02:57:00.660> of<02:57:00.960> its<02:57:01.260> host<02:57:01.439> machine<02:57:02.220> whatever 02:57:02.690 --> 02:57:02.700 align:start position:0% independent of its host machine whatever 02:57:02.700 --> 02:57:04.969 align:start position:0% independent of its host machine whatever that<02:57:03.120> might<02:57:03.300> be 02:57:04.969 --> 02:57:04.979 align:start position:0% that might be 02:57:04.979 --> 02:57:09.050 align:start position:0% that might be now<02:57:05.580> virtual<02:57:06.060> machines<02:57:06.979> uh<02:57:07.979> are<02:57:08.279> similar<02:57:08.700> to<02:57:08.939> a 02:57:09.050 --> 02:57:09.060 align:start position:0% now virtual machines uh are similar to a 02:57:09.060 --> 02:57:11.269 align:start position:0% now virtual machines uh are similar to a virtual<02:57:09.359> server<02:57:09.840> in<02:57:10.380> that<02:57:10.560> it<02:57:10.680> has<02:57:10.920> its<02:57:11.220> own 02:57:11.269 --> 02:57:11.279 align:start position:0% virtual server in that it has its own 02:57:11.279 --> 02:57:14.090 align:start position:0% virtual server in that it has its own software<02:57:11.819> like<02:57:12.420> uh<02:57:12.899> CPA<02:57:13.439> based<02:57:13.979> sorry 02:57:14.090 --> 02:57:14.100 align:start position:0% software like uh CPA based sorry 02:57:14.100 --> 02:57:16.790 align:start position:0% software like uh CPA based sorry software<02:57:14.640> based<02:57:15.060> CPU<02:57:15.420> Ram<02:57:15.660> Nic<02:57:16.200> hard<02:57:16.380> drive 02:57:16.790 --> 02:57:16.800 align:start position:0% software based CPU Ram Nic hard drive 02:57:16.800 --> 02:57:18.830 align:start position:0% software based CPU Ram Nic hard drive Etc<02:57:16.979> but<02:57:17.700> it's<02:57:17.819> a<02:57:18.000> software<02:57:18.300> implementation 02:57:18.830 --> 02:57:18.840 align:start position:0% Etc but it's a software implementation 02:57:18.840 --> 02:57:20.990 align:start position:0% Etc but it's a software implementation of<02:57:19.260> a<02:57:19.439> machine<02:57:19.560> that<02:57:20.100> performs<02:57:20.580> specific 02:57:20.990 --> 02:57:21.000 align:start position:0% of a machine that performs specific 02:57:21.000 --> 02:57:24.110 align:start position:0% of a machine that performs specific tasks<02:57:21.600> and<02:57:22.080> executes<02:57:22.560> specific<02:57:22.979> commands<02:57:23.640> but 02:57:24.110 --> 02:57:24.120 align:start position:0% tasks and executes specific commands but 02:57:24.120 --> 02:57:26.929 align:start position:0% tasks and executes specific commands but it's<02:57:24.300> not<02:57:24.660> a<02:57:25.140> server<02:57:25.740> per<02:57:26.100> se<02:57:26.279> all<02:57:26.760> right 02:57:26.929 --> 02:57:26.939 align:start position:0% it's not a server per se all right 02:57:26.939 --> 02:57:28.190 align:start position:0% it's not a server per se all right remember<02:57:27.120> a<02:57:27.479> server<02:57:27.720> or<02:57:27.899> something<02:57:28.020> that's 02:57:28.190 --> 02:57:28.200 align:start position:0% remember a server or something that's 02:57:28.200 --> 02:57:30.469 align:start position:0% remember a server or something that's serving<02:57:28.500> up<02:57:28.680> information<02:57:28.920> to<02:57:29.460> a<02:57:29.640> client 02:57:30.469 --> 02:57:30.479 align:start position:0% serving up information to a client 02:57:30.479 --> 02:57:32.030 align:start position:0% serving up information to a client and<02:57:30.960> then<02:57:31.080> finally<02:57:31.319> we<02:57:31.500> have<02:57:31.620> a<02:57:31.740> virtual 02:57:32.030 --> 02:57:32.040 align:start position:0% and then finally we have a virtual 02:57:32.040 --> 02:57:35.690 align:start position:0% and then finally we have a virtual desktop<02:57:32.640> which<02:57:33.359> in<02:57:33.600> Windows<02:57:34.279> systems<02:57:35.279> is<02:57:35.460> a 02:57:35.690 --> 02:57:35.700 align:start position:0% desktop which in Windows systems is a 02:57:35.700 --> 02:57:38.510 align:start position:0% desktop which in Windows systems is a single<02:57:35.939> desktop 02:57:38.510 --> 02:57:38.520 align:start position:0% 02:57:38.520 --> 02:57:40.730 align:start position:0% which<02:57:39.120> in<02:57:39.300> Windows<02:57:39.660> systems<02:57:40.080> a<02:57:40.439> single 02:57:40.730 --> 02:57:40.740 align:start position:0% which in Windows systems a single 02:57:40.740 --> 02:57:42.290 align:start position:0% which in Windows systems a single desktop 02:57:42.290 --> 02:57:42.300 align:start position:0% desktop 02:57:42.300 --> 02:57:45.110 align:start position:0% desktop is<02:57:42.779> the<02:57:43.020> default<02:57:43.439> that<02:57:44.040> can<02:57:44.220> be<02:57:44.399> open<02:57:44.520> but<02:57:44.880> a 02:57:45.110 --> 02:57:45.120 align:start position:0% is the default that can be open but a 02:57:45.120 --> 02:57:47.030 align:start position:0% is the default that can be open but a virtual<02:57:45.420> desktop<02:57:45.899> allows<02:57:46.439> you<02:57:46.740> to<02:57:46.920> open 02:57:47.030 --> 02:57:47.040 align:start position:0% virtual desktop allows you to open 02:57:47.040 --> 02:57:49.130 align:start position:0% virtual desktop allows you to open multiple<02:57:47.640> different<02:57:47.939> desktops<02:57:48.720> at<02:57:48.840> the<02:57:48.960> same 02:57:49.130 --> 02:57:49.140 align:start position:0% multiple different desktops at the same 02:57:49.140 --> 02:57:51.950 align:start position:0% multiple different desktops at the same time<02:57:49.580> Linux<02:57:50.580> also<02:57:50.880> supports<02:57:51.300> this<02:57:51.479> by<02:57:51.660> the<02:57:51.840> way 02:57:51.950 --> 02:57:51.960 align:start position:0% time Linux also supports this by the way 02:57:51.960 --> 02:57:55.070 align:start position:0% time Linux also supports this by the way but<02:57:52.439> Microsoft<02:57:53.040> requires<02:57:53.880> extra<02:57:54.420> software 02:57:55.070 --> 02:57:55.080 align:start position:0% but Microsoft requires extra software 02:57:55.080 --> 02:57:57.530 align:start position:0% but Microsoft requires extra software that<02:57:55.740> you<02:57:55.979> install<02:57:56.160> for<02:57:56.700> this<02:57:56.880> to<02:57:57.000> be<02:57:57.180> changed 02:57:57.530 --> 02:57:57.540 align:start position:0% that you install for this to be changed 02:57:57.540 --> 02:58:00.410 align:start position:0% that you install for this to be changed for<02:57:57.840> instance<02:57:58.080> uh<02:57:58.560> virtual<02:57:59.100> PC 02:58:00.410 --> 02:58:00.420 align:start position:0% for instance uh virtual PC 02:58:00.420 --> 02:58:03.469 align:start position:0% for instance uh virtual PC we've<02:58:00.840> seen<02:58:01.020> this<02:58:01.319> if<02:58:01.740> you<02:58:01.859> remember<02:58:02.040> with 02:58:03.469 --> 02:58:03.479 align:start position:0% we've seen this if you remember with 02:58:03.479 --> 02:58:06.889 align:start position:0% we've seen this if you remember with um an<02:58:03.779> A<02:58:03.960> plus<02:58:04.140> with<02:58:04.680> XP<02:58:05.279> Mode<02:58:05.700> now<02:58:06.420> continuing 02:58:06.889 --> 02:58:06.899 align:start position:0% um an A plus with XP Mode now continuing 02:58:06.899 --> 02:58:09.469 align:start position:0% um an A plus with XP Mode now continuing to<02:58:07.200> talk<02:58:07.380> about<02:58:07.740> virtualization<02:58:08.640> if<02:58:09.300> an 02:58:09.469 --> 02:58:09.479 align:start position:0% to talk about virtualization if an 02:58:09.479 --> 02:58:11.870 align:start position:0% to talk about virtualization if an organization<02:58:10.080> or<02:58:10.680> a<02:58:10.859> company<02:58:11.040> builds<02:58:11.640> their 02:58:11.870 --> 02:58:11.880 align:start position:0% organization or a company builds their 02:58:11.880 --> 02:58:14.690 align:start position:0% organization or a company builds their Network<02:58:12.240> infrastructure<02:58:13.200> and<02:58:13.920> chooses<02:58:14.399> not 02:58:14.690 --> 02:58:14.700 align:start position:0% Network infrastructure and chooses not 02:58:14.700 --> 02:58:17.030 align:start position:0% Network infrastructure and chooses not to<02:58:14.880> use<02:58:15.060> it<02:58:15.240> they<02:58:15.960> can<02:58:16.080> lease<02:58:16.439> it<02:58:16.620> out<02:58:16.740> to 02:58:17.030 --> 02:58:17.040 align:start position:0% to use it they can lease it out to 02:58:17.040 --> 02:58:19.849 align:start position:0% to use it they can lease it out to others<02:58:17.399> so<02:58:18.120> for<02:58:18.359> instance<02:58:18.600> Amazon<02:58:19.080> would<02:58:19.500> be<02:58:19.620> a 02:58:19.849 --> 02:58:19.859 align:start position:0% others so for instance Amazon would be a 02:58:19.859 --> 02:58:21.650 align:start position:0% others so for instance Amazon would be a great<02:58:19.979> example<02:58:20.340> of<02:58:20.520> this<02:58:20.640> they<02:58:20.880> have<02:58:21.060> a<02:58:21.300> huge 02:58:21.650 --> 02:58:21.660 align:start position:0% great example of this they have a huge 02:58:21.660 --> 02:58:23.330 align:start position:0% great example of this they have a huge infrastructure<02:58:22.319> but<02:58:22.560> they<02:58:22.680> don't<02:58:22.859> use<02:58:23.040> all<02:58:23.279> of 02:58:23.330 --> 02:58:23.340 align:start position:0% infrastructure but they don't use all of 02:58:23.340 --> 02:58:24.650 align:start position:0% infrastructure but they don't use all of it<02:58:23.460> so<02:58:23.580> what<02:58:23.760> do<02:58:23.880> they<02:58:23.939> do<02:58:24.060> they<02:58:24.180> lease<02:58:24.420> it<02:58:24.540> out 02:58:24.650 --> 02:58:24.660 align:start position:0% it so what do they do they lease it out 02:58:24.660 --> 02:58:26.870 align:start position:0% it so what do they do they lease it out to<02:58:24.840> others<02:58:25.140> this<02:58:25.620> is<02:58:25.740> a<02:58:25.920> very<02:58:26.100> common<02:58:26.340> practice 02:58:26.870 --> 02:58:26.880 align:start position:0% to others this is a very common practice 02:58:26.880 --> 02:58:35.830 align:start position:0% to others this is a very common practice and<02:58:27.540> what<02:58:27.720> it's<02:58:27.840> labeled<02:58:28.260> as<02:58:29.220> is<02:58:29.700> networking 02:58:35.830 --> 02:58:35.840 align:start position:0% 02:58:35.840 --> 02:58:40.969 align:start position:0% as<02:58:36.840> a<02:58:37.319> service 02:58:40.969 --> 02:58:40.979 align:start position:0% 02:58:40.979 --> 02:58:44.990 align:start position:0% now<02:58:41.939> an<02:58:42.840> area<02:58:43.020> of<02:58:43.439> network<02:58:43.740> as<02:58:44.160> a<02:58:44.340> service<02:58:44.580> or 02:58:44.990 --> 02:58:45.000 align:start position:0% now an area of network as a service or 02:58:45.000 --> 02:58:47.269 align:start position:0% now an area of network as a service or Naas<02:58:45.540> depending<02:58:46.200> on<02:58:46.319> what<02:58:46.560> is<02:58:46.680> being<02:58:46.859> leased 02:58:47.269 --> 02:58:47.279 align:start position:0% Naas depending on what is being leased 02:58:47.279 --> 02:58:49.250 align:start position:0% Naas depending on what is being leased might<02:58:47.819> be<02:58:48.000> considered<02:58:48.479> one<02:58:48.840> of<02:58:48.960> several 02:58:49.250 --> 02:58:49.260 align:start position:0% might be considered one of several 02:58:49.260 --> 02:58:51.170 align:start position:0% might be considered one of several different<02:58:49.439> things<02:58:49.800> it<02:58:50.460> might<02:58:50.580> be<02:58:50.700> considered 02:58:51.170 --> 02:58:51.180 align:start position:0% different things it might be considered 02:58:51.180 --> 02:58:55.670 align:start position:0% different things it might be considered IAS<02:58:52.020> or<02:58:52.939> infrastructure<02:58:53.939> as<02:58:54.300> a<02:58:54.479> service 02:58:55.670 --> 02:58:55.680 align:start position:0% IAS or infrastructure as a service 02:58:55.680 --> 02:58:58.490 align:start position:0% IAS or infrastructure as a service meaning<02:58:56.279> like<02:58:56.819> the<02:58:57.180> hardware 02:58:58.490 --> 02:58:58.500 align:start position:0% meaning like the hardware 02:58:58.500 --> 02:59:00.349 align:start position:0% meaning like the hardware I<02:58:58.920> provide<02:58:59.220> you<02:58:59.340> the<02:58:59.520> hardware<02:58:59.700> provide<02:59:00.240> you 02:59:00.349 --> 02:59:00.359 align:start position:0% I provide you the hardware provide you 02:59:00.359 --> 02:59:02.929 align:start position:0% I provide you the hardware provide you the<02:59:00.479> infrastructure<02:59:01.080> it<02:59:01.800> could<02:59:01.979> be<02:59:02.160> software 02:59:02.929 --> 02:59:02.939 align:start position:0% the infrastructure it could be software 02:59:02.939 --> 02:59:08.389 align:start position:0% the infrastructure it could be software as<02:59:03.359> a<02:59:03.540> service<02:59:03.720> much<02:59:04.140> like<02:59:04.380> Gmail 02:59:08.389 --> 02:59:08.399 align:start position:0% 02:59:08.399 --> 02:59:10.250 align:start position:0% which<02:59:09.180> simply<02:59:09.479> provides<02:59:09.840> you<02:59:09.960> certain 02:59:10.250 --> 02:59:10.260 align:start position:0% which simply provides you certain 02:59:10.260 --> 02:59:11.809 align:start position:0% which simply provides you certain software<02:59:10.680> and<02:59:10.859> just<02:59:11.040> like<02:59:11.160> infrastructure 02:59:11.809 --> 02:59:11.819 align:start position:0% software and just like infrastructure 02:59:11.819 --> 02:59:14.750 align:start position:0% software and just like infrastructure would<02:59:12.000> be<02:59:12.120> like<02:59:12.300> Amazon's<02:59:13.020> uh 02:59:14.750 --> 02:59:14.760 align:start position:0% would be like Amazon's uh 02:59:14.760 --> 02:59:19.370 align:start position:0% would be like Amazon's uh ec2<02:59:15.660> or<02:59:16.020> elastic<02:59:16.859> cloud<02:59:17.279> and<02:59:18.180> then<02:59:18.359> the<02:59:19.319> last 02:59:19.370 --> 02:59:19.380 align:start position:0% ec2 or elastic cloud and then the last 02:59:19.380 --> 02:59:21.950 align:start position:0% ec2 or elastic cloud and then the last one<02:59:19.620> is<02:59:19.859> platform<02:59:20.460> as<02:59:20.760> a<02:59:21.000> service 02:59:21.950 --> 02:59:21.960 align:start position:0% one is platform as a service 02:59:21.960 --> 02:59:24.410 align:start position:0% one is platform as a service which<02:59:22.380> would<02:59:22.560> be<02:59:22.680> like<02:59:22.979> a<02:59:23.340> an<02:59:23.880> application 02:59:24.410 --> 02:59:24.420 align:start position:0% which would be like a an application 02:59:24.420 --> 02:59:27.849 align:start position:0% which would be like a an application sort<02:59:24.779> of<02:59:24.899> engine<02:59:25.220> or<02:59:26.220> uh<02:59:26.760> allowing<02:59:27.240> you<02:59:27.359> to 02:59:27.849 --> 02:59:27.859 align:start position:0% sort of engine or uh allowing you to 02:59:27.859 --> 02:59:29.870 align:start position:0% sort of engine or uh allowing you to deploy<02:59:28.859> certain 02:59:29.870 --> 02:59:29.880 align:start position:0% deploy certain 02:59:29.880 --> 02:59:32.330 align:start position:0% deploy certain development<02:59:30.840> tools<02:59:31.380> most<02:59:31.920> of<02:59:32.100> the<02:59:32.160> time 02:59:32.330 --> 02:59:32.340 align:start position:0% development tools most of the time 02:59:32.340 --> 02:59:34.490 align:start position:0% development tools most of the time you're<02:59:32.640> gonna<02:59:32.819> see<02:59:33.120> most<02:59:33.420> of<02:59:33.660> these<02:59:33.960> in<02:59:34.319> the 02:59:34.490 --> 02:59:34.500 align:start position:0% you're gonna see most of these in the 02:59:34.500 --> 02:59:37.309 align:start position:0% you're gonna see most of these in the field<02:59:34.680> this<02:59:35.580> one<02:59:35.700> is<02:59:35.939> really<02:59:36.240> more<02:59:36.600> for 02:59:37.309 --> 02:59:37.319 align:start position:0% field this one is really more for 02:59:37.319 --> 02:59:43.550 align:start position:0% field this one is really more for Developers 02:59:43.550 --> 02:59:43.560 align:start position:0% 02:59:43.560 --> 02:59:46.730 align:start position:0% so<02:59:44.160> the<02:59:44.340> term<02:59:44.520> Legacy<02:59:45.240> indicates<02:59:46.140> that<02:59:46.500> this 02:59:46.730 --> 02:59:46.740 align:start position:0% so the term Legacy indicates that this 02:59:46.740 --> 02:59:49.550 align:start position:0% so the term Legacy indicates that this is<02:59:46.979> a<02:59:47.279> an<02:59:47.819> older<02:59:48.240> device<02:59:48.420> one<02:59:49.020> that's<02:59:49.260> not 02:59:49.550 --> 02:59:49.560 align:start position:0% is a an older device one that's not 02:59:49.560 --> 02:59:51.950 align:start position:0% is a an older device one that's not really<02:59:49.859> in<02:59:50.340> use<02:59:50.520> in<02:59:50.760> today's<02:59:51.000> networks<02:59:51.660> or 02:59:51.950 --> 02:59:51.960 align:start position:0% really in use in today's networks or 02:59:51.960 --> 02:59:54.650 align:start position:0% really in use in today's networks or that<02:59:52.319> have<02:59:52.500> been<02:59:52.680> replaced<02:59:53.340> by<02:59:53.700> a<02:59:53.939> newer<02:59:54.420> or 02:59:54.650 --> 02:59:54.660 align:start position:0% that have been replaced by a newer or 02:59:54.660 --> 02:59:56.870 align:start position:0% that have been replaced by a newer or higher<02:59:54.960> functioning<02:59:55.380> devices<02:59:55.740> so<02:59:56.520> some<02:59:56.760> of 02:59:56.870 --> 02:59:56.880 align:start position:0% higher functioning devices so some of 02:59:56.880 --> 02:59:58.490 align:start position:0% higher functioning devices so some of the<02:59:56.939> things<02:59:57.120> we're<02:59:57.720> going<02:59:57.840> to<02:59:57.960> talk<02:59:58.080> about<02:59:58.260> in 02:59:58.490 --> 02:59:58.500 align:start position:0% the things we're going to talk about in 02:59:58.500 --> 03:00:00.349 align:start position:0% the things we're going to talk about in this<02:59:58.740> one<02:59:58.859> might<02:59:59.279> appear<02:59:59.520> on<02:59:59.700> the<02:59:59.819> exam<03:00:00.120> and 03:00:00.349 --> 03:00:00.359 align:start position:0% this one might appear on the exam and 03:00:00.359 --> 03:00:02.269 align:start position:0% this one might appear on the exam and the<03:00:00.540> reason<03:00:00.720> the<03:00:01.380> reason<03:00:01.560> for<03:00:01.859> that<03:00:02.040> is 03:00:02.269 --> 03:00:02.279 align:start position:0% the reason the reason for that is 03:00:02.279 --> 03:00:04.150 align:start position:0% the reason the reason for that is because<03:00:02.520> they<03:00:03.240> might<03:00:03.420> appear<03:00:03.660> in<03:00:03.840> the<03:00:03.960> field 03:00:04.150 --> 03:00:04.160 align:start position:0% because they might appear in the field 03:00:04.160 --> 03:00:05.929 align:start position:0% because they might appear in the field uh<03:00:05.160> just<03:00:05.340> because<03:00:05.520> they<03:00:05.640> haven't<03:00:05.760> been 03:00:05.929 --> 03:00:05.939 align:start position:0% uh just because they haven't been 03:00:05.939 --> 03:00:08.090 align:start position:0% uh just because they haven't been replaced<03:00:06.420> yet<03:00:06.540> by<03:00:06.840> perhaps<03:00:07.260> due<03:00:07.620> to<03:00:07.740> expense 03:00:08.090 --> 03:00:08.100 align:start position:0% replaced yet by perhaps due to expense 03:00:08.100 --> 03:00:10.910 align:start position:0% replaced yet by perhaps due to expense or<03:00:08.340> something<03:00:08.899> however<03:00:09.899> these<03:00:10.620> have<03:00:10.740> probably 03:00:10.910 --> 03:00:10.920 align:start position:0% or something however these have probably 03:00:10.920 --> 03:00:13.190 align:start position:0% or something however these have probably been<03:00:11.160> replaced<03:00:11.760> by<03:00:12.060> switches<03:00:12.540> routers<03:00:13.020> and 03:00:13.190 --> 03:00:13.200 align:start position:0% been replaced by switches routers and 03:00:13.200 --> 03:00:14.929 align:start position:0% been replaced by switches routers and gateways<03:00:13.800> but<03:00:14.100> it's<03:00:14.220> still<03:00:14.399> good<03:00:14.580> to<03:00:14.700> go<03:00:14.819> over 03:00:14.929 --> 03:00:14.939 align:start position:0% gateways but it's still good to go over 03:00:14.939 --> 03:00:18.410 align:start position:0% gateways but it's still good to go over them<03:00:15.180> anyway<03:00:15.359> so<03:00:16.260> a<03:00:16.859> repeater<03:00:17.220> is<03:00:17.880> a<03:00:18.240> simple 03:00:18.410 --> 03:00:18.420 align:start position:0% them anyway so a repeater is a simple 03:00:18.420 --> 03:00:20.929 align:start position:0% them anyway so a repeater is a simple device<03:00:18.779> that<03:00:19.380> does<03:00:19.800> not<03:00:19.979> look<03:00:20.279> at<03:00:20.580> the<03:00:20.819> traffic 03:00:20.929 --> 03:00:20.939 align:start position:0% device that does not look at the traffic 03:00:20.939 --> 03:00:23.450 align:start position:0% device that does not look at the traffic at<03:00:21.300> all<03:00:21.420> all<03:00:21.660> it<03:00:21.840> does<03:00:22.080> is<03:00:22.439> it<03:00:22.620> simply<03:00:22.920> boosts 03:00:23.450 --> 03:00:23.460 align:start position:0% at all all it does is it simply boosts 03:00:23.460 --> 03:00:25.490 align:start position:0% at all all it does is it simply boosts the<03:00:23.760> signal<03:00:24.060> after<03:00:24.300> it<03:00:24.479> receives<03:00:24.840> it<03:00:25.020> and 03:00:25.490 --> 03:00:25.500 align:start position:0% the signal after it receives it and 03:00:25.500 --> 03:00:28.070 align:start position:0% the signal after it receives it and transmits<03:00:26.160> it<03:00:26.279> out<03:00:26.460> so<03:00:27.060> it<03:00:27.180> just<03:00:27.359> repeats<03:00:27.899> the 03:00:28.070 --> 03:00:28.080 align:start position:0% transmits it out so it just repeats the 03:00:28.080 --> 03:00:31.070 align:start position:0% transmits it out so it just repeats the signal<03:00:28.439> as<03:00:29.220> the<03:00:29.399> name<03:00:29.580> implies<03:00:30.120> just<03:00:30.600> boosting 03:00:31.070 --> 03:00:31.080 align:start position:0% signal as the name implies just boosting 03:00:31.080 --> 03:00:32.630 align:start position:0% signal as the name implies just boosting that<03:00:31.319> signal<03:00:31.620> we<03:00:32.160> also<03:00:32.399> have<03:00:32.460> something 03:00:32.630 --> 03:00:32.640 align:start position:0% that signal we also have something 03:00:32.640 --> 03:00:34.550 align:start position:0% that signal we also have something called<03:00:32.819> a<03:00:33.060> hub<03:00:33.240> which<03:00:33.779> you<03:00:34.080> might<03:00:34.200> have<03:00:34.380> heard 03:00:34.550 --> 03:00:34.560 align:start position:0% called a hub which you might have heard 03:00:34.560 --> 03:00:37.309 align:start position:0% called a hub which you might have heard of<03:00:34.680> and<03:00:34.859> this<03:00:35.040> is<03:00:35.160> similar<03:00:35.520> to<03:00:35.700> a<03:00:35.880> repeater<03:00:36.600> in 03:00:37.309 --> 03:00:37.319 align:start position:0% of and this is similar to a repeater in 03:00:37.319 --> 03:00:40.010 align:start position:0% of and this is similar to a repeater in that<03:00:37.560> it<03:00:38.100> only<03:00:38.460> it<03:00:38.819> doesn't<03:00:39.000> look<03:00:39.300> at<03:00:39.479> the<03:00:39.720> data 03:00:40.010 --> 03:00:40.020 align:start position:0% that it only it doesn't look at the data 03:00:40.020 --> 03:00:42.769 align:start position:0% that it only it doesn't look at the data it<03:00:40.319> just<03:00:40.620> retransmits<03:00:41.520> it<03:00:41.640> but<03:00:42.300> the<03:00:42.660> thing 03:00:42.769 --> 03:00:42.779 align:start position:0% it just retransmits it but the thing 03:00:42.779 --> 03:00:44.870 align:start position:0% it just retransmits it but the thing that<03:00:42.960> a<03:00:43.380> Hub<03:00:43.740> does<03:00:44.040> is<03:00:44.160> it<03:00:44.279> receives<03:00:44.580> traffic 03:00:44.870 --> 03:00:44.880 align:start position:0% that a Hub does is it receives traffic 03:00:44.880 --> 03:00:47.570 align:start position:0% that a Hub does is it receives traffic from<03:00:45.479> one<03:00:46.020> port<03:00:46.200> and<03:00:46.500> sends<03:00:46.800> it<03:00:46.859> out<03:00:46.979> to<03:00:47.279> all 03:00:47.570 --> 03:00:47.580 align:start position:0% from one port and sends it out to all 03:00:47.580 --> 03:00:49.490 align:start position:0% from one port and sends it out to all the<03:00:47.700> ports<03:00:48.060> without<03:00:48.420> looking<03:00:48.779> at<03:00:49.020> the<03:00:49.200> data 03:00:49.490 --> 03:00:49.500 align:start position:0% the ports without looking at the data 03:00:49.500 --> 03:00:53.410 align:start position:0% the ports without looking at the data traffic<03:00:49.680> now<03:00:50.340> it's<03:00:50.700> vastly<03:00:51.120> been<03:00:51.300> replaced<03:00:51.899> by 03:00:53.410 --> 03:00:53.420 align:start position:0% traffic now it's vastly been replaced by 03:00:53.420 --> 03:00:56.690 align:start position:0% traffic now it's vastly been replaced by switches<03:00:54.420> because<03:00:54.899> as<03:00:55.260> you<03:00:55.380> can<03:00:55.500> imagine<03:00:55.740> if<03:00:56.399> I 03:00:56.690 --> 03:00:56.700 align:start position:0% switches because as you can imagine if I 03:00:56.700 --> 03:01:00.050 align:start position:0% switches because as you can imagine if I wanted<03:00:56.819> to<03:00:57.120> send<03:00:57.359> data<03:00:57.779> to<03:00:58.020> only<03:00:58.500> one<03:00:58.859> node<03:00:59.160> The 03:01:00.050 --> 03:01:00.060 align:start position:0% wanted to send data to only one node The 03:01:00.060 --> 03:01:01.429 align:start position:0% wanted to send data to only one node The Hub<03:01:00.120> doesn't<03:01:00.359> allow<03:01:00.660> me<03:01:00.720> to<03:01:00.840> do<03:01:00.960> that<03:01:01.020> it<03:01:01.200> makes 03:01:01.429 --> 03:01:01.439 align:start position:0% Hub doesn't allow me to do that it makes 03:01:01.439 --> 03:01:03.889 align:start position:0% Hub doesn't allow me to do that it makes me<03:01:01.680> send<03:01:01.979> it<03:01:02.160> to<03:01:02.399> all<03:01:02.880> of<03:01:03.240> the<03:01:03.359> nodes<03:01:03.600> and<03:01:03.779> so 03:01:03.889 --> 03:01:03.899 align:start position:0% me send it to all of the nodes and so 03:01:03.899 --> 03:01:05.269 align:start position:0% me send it to all of the nodes and so this<03:01:04.020> is<03:01:04.140> going<03:01:04.260> to<03:01:04.380> cause<03:01:04.500> quite<03:01:04.859> a<03:01:04.979> bit<03:01:05.100> of 03:01:05.269 --> 03:01:05.279 align:start position:0% this is going to cause quite a bit of 03:01:05.279 --> 03:01:08.269 align:start position:0% this is going to cause quite a bit of extra<03:01:05.720> traffic<03:01:06.720> on<03:01:07.080> my<03:01:07.200> network<03:01:07.380> finally 03:01:08.269 --> 03:01:08.279 align:start position:0% extra traffic on my network finally 03:01:08.279 --> 03:01:10.910 align:start position:0% extra traffic on my network finally there's<03:01:08.520> something<03:01:08.760> called<03:01:09.180> a<03:01:09.660> bridge<03:01:10.080> which 03:01:10.910 --> 03:01:10.920 align:start position:0% there's something called a bridge which 03:01:10.920 --> 03:01:14.090 align:start position:0% there's something called a bridge which was<03:01:11.880> the<03:01:12.300> purpose<03:01:12.600> was<03:01:12.840> to<03:01:13.080> divide<03:01:13.500> logical 03:01:14.090 --> 03:01:14.100 align:start position:0% was the purpose was to divide logical 03:01:14.100 --> 03:01:16.370 align:start position:0% was the purpose was to divide logical bus<03:01:14.460> networks<03:01:15.000> into<03:01:15.180> segments<03:01:15.779> and<03:01:16.140> it<03:01:16.260> did 03:01:16.370 --> 03:01:16.380 align:start position:0% bus networks into segments and it did 03:01:16.380 --> 03:01:18.410 align:start position:0% bus networks into segments and it did this<03:01:16.560> by<03:01:16.800> looking<03:01:16.979> at<03:01:17.220> the<03:01:17.460> MAC<03:01:17.580> address<03:01:17.819> so<03:01:18.240> it 03:01:18.410 --> 03:01:18.420 align:start position:0% this by looking at the MAC address so it 03:01:18.420 --> 03:01:20.570 align:start position:0% this by looking at the MAC address so it is<03:01:18.960> operating<03:01:19.380> it's<03:01:19.680> sort<03:01:19.920> of<03:01:19.979> the<03:01:20.160> same<03:01:20.340> level 03:01:20.570 --> 03:01:20.580 align:start position:0% is operating it's sort of the same level 03:01:20.580 --> 03:01:23.269 align:start position:0% is operating it's sort of the same level as<03:01:21.000> a<03:01:21.240> as<03:01:21.660> a<03:01:21.899> switch<03:01:22.080> and<03:01:22.800> it<03:01:22.920> would<03:01:23.040> look<03:01:23.160> at 03:01:23.269 --> 03:01:23.279 align:start position:0% as a as a switch and it would look at 03:01:23.279 --> 03:01:24.650 align:start position:0% as a as a switch and it would look at the<03:01:23.340> MAC<03:01:23.460> address<03:01:23.580> of<03:01:23.880> the<03:01:24.000> packet<03:01:24.300> and 03:01:24.650 --> 03:01:24.660 align:start position:0% the MAC address of the packet and 03:01:24.660 --> 03:01:26.929 align:start position:0% the MAC address of the packet and transmitted<03:01:25.200> the<03:01:25.380> data<03:01:25.680> accordingly<03:01:26.220> now<03:01:26.819> if 03:01:26.929 --> 03:01:26.939 align:start position:0% transmitted the data accordingly now if 03:01:26.939 --> 03:01:28.969 align:start position:0% transmitted the data accordingly now if the<03:01:27.060> MAC<03:01:27.180> address<03:01:27.420> was<03:01:27.840> on<03:01:28.140> another<03:01:28.380> segment 03:01:28.969 --> 03:01:28.979 align:start position:0% the MAC address was on another segment 03:01:28.979 --> 03:01:31.010 align:start position:0% the MAC address was on another segment it<03:01:29.340> forwarded<03:01:29.819> it<03:01:30.000> out<03:01:30.180> and<03:01:30.660> if<03:01:30.840> the 03:01:31.010 --> 03:01:31.020 align:start position:0% it forwarded it out and if the 03:01:31.020 --> 03:01:32.870 align:start position:0% it forwarded it out and if the destination<03:01:31.439> was<03:01:31.680> on<03:01:31.859> the<03:01:32.040> same<03:01:32.220> segment<03:01:32.580> then 03:01:32.870 --> 03:01:32.880 align:start position:0% destination was on the same segment then 03:01:32.880 --> 03:01:35.210 align:start position:0% destination was on the same segment then it<03:01:33.060> didn't<03:01:33.180> forward<03:01:33.479> it<03:01:33.720> so<03:01:34.380> in<03:01:34.920> older 03:01:35.210 --> 03:01:35.220 align:start position:0% it didn't forward it so in older 03:01:35.220 --> 03:01:37.969 align:start position:0% it didn't forward it so in older networks<03:01:35.760> this<03:01:36.359> implementation<03:01:37.140> was<03:01:37.500> logical 03:01:37.969 --> 03:01:37.979 align:start position:0% networks this implementation was logical 03:01:37.979 --> 03:01:40.250 align:start position:0% networks this implementation was logical and<03:01:38.700> it<03:01:38.880> was<03:01:39.000> handy<03:01:39.359> because<03:01:39.479> it<03:01:39.779> reduced 03:01:40.250 --> 03:01:40.260 align:start position:0% and it was handy because it reduced 03:01:40.260 --> 03:01:42.410 align:start position:0% and it was handy because it reduced traffic<03:01:40.680> congestion<03:01:41.399> and<03:01:42.000> improved 03:01:42.410 --> 03:01:42.420 align:start position:0% traffic congestion and improved 03:01:42.420 --> 03:01:44.030 align:start position:0% traffic congestion and improved performance<03:01:42.840> obviously<03:01:43.319> because<03:01:43.620> it<03:01:43.920> wasn't 03:01:44.030 --> 03:01:44.040 align:start position:0% performance obviously because it wasn't 03:01:44.040 --> 03:01:46.190 align:start position:0% performance obviously because it wasn't forwarding<03:01:44.640> data<03:01:45.000> that<03:01:45.479> didn't<03:01:45.660> need<03:01:45.899> to<03:01:46.080> be 03:01:46.190 --> 03:01:46.200 align:start position:0% forwarding data that didn't need to be 03:01:46.200 --> 03:01:47.690 align:start position:0% forwarding data that didn't need to be forwarded<03:01:46.620> on 03:01:47.690 --> 03:01:47.700 align:start position:0% forwarded on 03:01:47.700 --> 03:01:49.389 align:start position:0% forwarded on all<03:01:48.060> right<03:01:48.240> now<03:01:48.479> let's<03:01:48.600> talk<03:01:48.779> about<03:01:48.899> noise 03:01:49.389 --> 03:01:49.399 align:start position:0% all right now let's talk about noise 03:01:49.399 --> 03:01:52.309 align:start position:0% all right now let's talk about noise noise<03:01:50.399> or<03:01:50.760> electrical<03:01:51.300> noise<03:01:51.479> and<03:01:51.779> networking 03:01:52.309 --> 03:01:52.319 align:start position:0% noise or electrical noise and networking 03:01:52.319 --> 03:01:56.990 align:start position:0% noise or electrical noise and networking it's<03:01:52.920> the<03:01:53.160> term<03:01:53.460> that<03:01:54.200> interferes<03:01:55.200> with<03:01:56.000> uh 03:01:56.990 --> 03:01:57.000 align:start position:0% it's the term that interferes with uh 03:01:57.000 --> 03:02:00.710 align:start position:0% it's the term that interferes with uh implies<03:01:57.899> rather<03:01:58.260> interfering<03:01:59.100> with<03:01:59.520> data<03:02:00.240> uh 03:02:00.710 --> 03:02:00.720 align:start position:0% implies rather interfering with data uh 03:02:00.720 --> 03:02:04.370 align:start position:0% implies rather interfering with data uh and<03:02:01.020> normal<03:02:01.439> data<03:02:01.979> traffic<03:02:02.180> it<03:02:03.180> can<03:02:03.420> come<03:02:04.080> from 03:02:04.370 --> 03:02:04.380 align:start position:0% and normal data traffic it can come from 03:02:04.380 --> 03:02:05.809 align:start position:0% and normal data traffic it can come from many<03:02:04.680> sources<03:02:05.220> and<03:02:05.460> as<03:02:05.640> Network 03:02:05.809 --> 03:02:05.819 align:start position:0% many sources and as Network 03:02:05.819 --> 03:02:07.429 align:start position:0% many sources and as Network administrators<03:02:06.540> it's<03:02:06.779> really<03:02:06.960> important 03:02:07.429 --> 03:02:07.439 align:start position:0% administrators it's really important 03:02:07.439 --> 03:02:10.010 align:start position:0% administrators it's really important that<03:02:07.979> we<03:02:08.279> know<03:02:09.060> where<03:02:09.300> all<03:02:09.479> this<03:02:09.600> noise<03:02:09.720> is 03:02:10.010 --> 03:02:10.020 align:start position:0% that we know where all this noise is 03:02:10.020 --> 03:02:11.929 align:start position:0% that we know where all this noise is coming<03:02:10.260> from<03:02:10.500> and<03:02:10.800> how<03:02:11.100> to<03:02:11.220> prevent<03:02:11.520> it<03:02:11.700> as 03:02:11.929 --> 03:02:11.939 align:start position:0% coming from and how to prevent it as 03:02:11.939 --> 03:02:14.150 align:start position:0% coming from and how to prevent it as well<03:02:12.180> so<03:02:12.779> not<03:02:12.960> only<03:02:13.080> can<03:02:13.319> noise<03:02:13.500> affect<03:02:13.920> our 03:02:14.150 --> 03:02:14.160 align:start position:0% well so not only can noise affect our 03:02:14.160 --> 03:02:16.849 align:start position:0% well so not only can noise affect our network<03:02:14.540> uh<03:02:15.540> performance<03:02:16.020> but<03:02:16.380> it<03:02:16.500> can<03:02:16.620> also 03:02:16.849 --> 03:02:16.859 align:start position:0% network uh performance but it can also 03:02:16.859 --> 03:02:19.250 align:start position:0% network uh performance but it can also affect<03:02:17.220> data<03:02:18.000> transmission<03:02:18.260> electrical 03:02:19.250 --> 03:02:19.260 align:start position:0% affect data transmission electrical 03:02:19.260 --> 03:02:21.230 align:start position:0% affect data transmission electrical current<03:02:19.500> as<03:02:19.859> well<03:02:20.040> now<03:02:20.580> if<03:02:20.700> electrical 03:02:21.230 --> 03:02:21.240 align:start position:0% current as well now if electrical 03:02:21.240 --> 03:02:23.150 align:start position:0% current as well now if electrical current<03:02:21.420> is<03:02:21.720> interrupted<03:02:22.260> or<03:02:22.560> interfered 03:02:23.150 --> 03:02:23.160 align:start position:0% current is interrupted or interfered 03:02:23.160 --> 03:02:26.210 align:start position:0% current is interrupted or interfered with<03:02:23.279> then<03:02:24.240> that<03:02:24.840> can<03:02:25.020> affect<03:02:25.319> our<03:02:25.740> electrical 03:02:26.210 --> 03:02:26.220 align:start position:0% with then that can affect our electrical 03:02:26.220 --> 03:02:28.550 align:start position:0% with then that can affect our electrical devices<03:02:26.580> so<03:02:27.060> for<03:02:27.300> instance<03:02:27.540> if<03:02:27.899> there<03:02:28.080> is<03:02:28.200> a 03:02:28.550 --> 03:02:28.560 align:start position:0% devices so for instance if there is a 03:02:28.560 --> 03:02:30.830 align:start position:0% devices so for instance if there is a surge<03:02:29.220> in<03:02:29.340> the<03:02:29.580> current<03:02:29.700> that<03:02:30.300> means<03:02:30.540> a<03:02:30.660> lot<03:02:30.779> of 03:02:30.830 --> 03:02:30.840 align:start position:0% surge in the current that means a lot of 03:02:30.840 --> 03:02:32.510 align:start position:0% surge in the current that means a lot of extraneous<03:02:31.380> noise<03:02:31.680> in<03:02:31.920> the<03:02:31.979> electrical<03:02:32.340> line 03:02:32.510 --> 03:02:32.520 align:start position:0% extraneous noise in the electrical line 03:02:32.520 --> 03:02:34.730 align:start position:0% extraneous noise in the electrical line goes<03:02:33.000> to<03:02:33.120> our<03:02:33.300> devices<03:02:33.600> and<03:02:34.260> then<03:02:34.380> damages 03:02:34.730 --> 03:02:34.740 align:start position:0% goes to our devices and then damages 03:02:34.740 --> 03:02:37.190 align:start position:0% goes to our devices and then damages them<03:02:35.100> so<03:02:35.640> sources<03:02:36.060> of<03:02:36.180> noise<03:02:36.359> are<03:02:36.660> found<03:02:36.899> in 03:02:37.190 --> 03:02:37.200 align:start position:0% them so sources of noise are found in 03:02:37.200 --> 03:02:39.469 align:start position:0% them so sources of noise are found in many<03:02:37.439> places<03:02:37.800> as<03:02:38.399> you<03:02:38.580> see<03:02:38.700> here<03:02:38.880> is<03:02:39.060> a<03:02:39.300> power 03:02:39.469 --> 03:02:39.479 align:start position:0% many places as you see here is a power 03:02:39.479 --> 03:02:42.590 align:start position:0% many places as you see here is a power line<03:02:39.720> electric<03:02:40.140> motors<03:02:40.920> used<03:02:41.700> in<03:02:41.939> HVAC 03:02:42.590 --> 03:02:42.600 align:start position:0% line electric motors used in HVAC 03:02:42.600 --> 03:02:45.830 align:start position:0% line electric motors used in HVAC systems<03:02:43.640> elevators<03:02:44.640> refrigerators<03:02:45.540> just 03:02:45.830 --> 03:02:45.840 align:start position:0% systems elevators refrigerators just 03:02:45.840 --> 03:02:47.990 align:start position:0% systems elevators refrigerators just about<03:02:46.020> anything<03:02:46.319> that<03:02:46.680> draws<03:02:46.979> power<03:02:47.220> to<03:02:47.460> run 03:02:47.990 --> 03:02:48.000 align:start position:0% about anything that draws power to run 03:02:48.000 --> 03:02:50.809 align:start position:0% about anything that draws power to run fluorescent<03:02:48.840> lights<03:02:49.220> neon<03:02:50.220> or<03:02:50.640> height 03:02:50.809 --> 03:02:50.819 align:start position:0% fluorescent lights neon or height 03:02:50.819 --> 03:02:53.389 align:start position:0% fluorescent lights neon or height intensity<03:02:51.540> discharge<03:02:52.260> lights<03:02:52.439> or<03:02:52.800> what<03:02:53.279> are 03:02:53.389 --> 03:02:53.399 align:start position:0% intensity discharge lights or what are 03:02:53.399 --> 03:02:57.050 align:start position:0% intensity discharge lights or what are called<03:02:53.720> HID<03:02:54.720> lights<03:02:55.460> uh<03:02:56.460> also<03:02:56.760> cause 03:02:57.050 --> 03:02:57.060 align:start position:0% called HID lights uh also cause 03:02:57.060 --> 03:02:59.389 align:start position:0% called HID lights uh also cause significant<03:02:57.660> amounts<03:02:58.080> of<03:02:58.439> noise<03:02:58.979> that 03:02:59.389 --> 03:02:59.399 align:start position:0% significant amounts of noise that 03:02:59.399 --> 03:03:01.550 align:start position:0% significant amounts of noise that interfere<03:02:59.880> with<03:03:00.120> networking<03:03:00.840> over<03:03:01.260> both 03:03:01.550 --> 03:03:01.560 align:start position:0% interfere with networking over both 03:03:01.560 --> 03:03:04.610 align:start position:0% interfere with networking over both bounded<03:03:02.040> and<03:03:02.279> unbounded<03:03:03.120> media<03:03:03.600> this<03:03:04.439> is 03:03:04.610 --> 03:03:04.620 align:start position:0% bounded and unbounded media this is 03:03:04.620 --> 03:03:06.230 align:start position:0% bounded and unbounded media this is especially<03:03:05.160> important<03:03:05.520> to<03:03:05.640> be<03:03:05.760> mindful<03:03:06.060> of 03:03:06.230 --> 03:03:06.240 align:start position:0% especially important to be mindful of 03:03:06.240 --> 03:03:07.910 align:start position:0% especially important to be mindful of when<03:03:06.420> you're<03:03:06.600> running<03:03:06.779> or<03:03:07.140> installing<03:03:07.680> your 03:03:07.910 --> 03:03:07.920 align:start position:0% when you're running or installing your 03:03:07.920 --> 03:03:09.950 align:start position:0% when you're running or installing your cables<03:03:08.340> or<03:03:08.760> placing<03:03:09.300> your<03:03:09.479> wireless<03:03:09.600> access 03:03:09.950 --> 03:03:09.960 align:start position:0% cables or placing your wireless access 03:03:09.960 --> 03:03:12.110 align:start position:0% cables or placing your wireless access points<03:03:10.500> you<03:03:10.920> want<03:03:10.979> to<03:03:11.160> really<03:03:11.340> avoid<03:03:11.760> running 03:03:12.110 --> 03:03:12.120 align:start position:0% points you want to really avoid running 03:03:12.120 --> 03:03:15.170 align:start position:0% points you want to really avoid running data<03:03:12.660> cable<03:03:12.840> parallel<03:03:13.740> to<03:03:13.920> those<03:03:14.100> lights<03:03:14.340> as 03:03:15.170 --> 03:03:15.180 align:start position:0% data cable parallel to those lights as 03:03:15.180 --> 03:03:18.050 align:start position:0% data cable parallel to those lights as well<03:03:15.359> as<03:03:15.479> any<03:03:16.140> cables<03:03:16.560> used<03:03:16.740> for<03:03:16.979> power<03:03:17.220> it<03:03:18.000> can 03:03:18.050 --> 03:03:18.060 align:start position:0% well as any cables used for power it can 03:03:18.060 --> 03:03:19.910 align:start position:0% well as any cables used for power it can also<03:03:18.300> come<03:03:18.479> from<03:03:18.840> devices<03:03:19.319> that<03:03:19.560> give<03:03:19.740> off 03:03:19.910 --> 03:03:19.920 align:start position:0% also come from devices that give off 03:03:19.920 --> 03:03:22.490 align:start position:0% also come from devices that give off heat<03:03:20.220> like<03:03:20.819> personal<03:03:21.060> heating<03:03:21.479> devices<03:03:21.840> and 03:03:22.490 --> 03:03:22.500 align:start position:0% heat like personal heating devices and 03:03:22.500 --> 03:03:23.870 align:start position:0% heat like personal heating devices and while<03:03:22.620> that<03:03:22.859> might<03:03:23.040> sound<03:03:23.279> a<03:03:23.460> little<03:03:23.520> strange 03:03:23.870 --> 03:03:23.880 align:start position:0% while that might sound a little strange 03:03:23.880 --> 03:03:25.309 align:start position:0% while that might sound a little strange it's<03:03:24.180> due<03:03:24.300> to<03:03:24.479> the<03:03:24.600> amount<03:03:24.779> of<03:03:24.899> power<03:03:25.080> that 03:03:25.309 --> 03:03:25.319 align:start position:0% it's due to the amount of power that 03:03:25.319 --> 03:03:27.889 align:start position:0% it's due to the amount of power that those<03:03:25.560> devices<03:03:25.920> consume<03:03:26.640> when<03:03:26.819> in<03:03:27.060> use<03:03:27.240> the 03:03:27.889 --> 03:03:27.899 align:start position:0% those devices consume when in use the 03:03:27.899 --> 03:03:29.750 align:start position:0% those devices consume when in use the power<03:03:28.140> or<03:03:28.439> the<03:03:28.560> electricity<03:03:29.040> it<03:03:29.399> has<03:03:29.580> the 03:03:29.750 --> 03:03:29.760 align:start position:0% power or the electricity it has the 03:03:29.760 --> 03:03:31.130 align:start position:0% power or the electricity it has the potential<03:03:30.000> to<03:03:30.120> give<03:03:30.300> off<03:03:30.420> a<03:03:30.660> lot<03:03:30.720> of<03:03:30.899> noise 03:03:31.130 --> 03:03:31.140 align:start position:0% potential to give off a lot of noise 03:03:31.140 --> 03:03:33.710 align:start position:0% potential to give off a lot of noise which<03:03:31.560> makes<03:03:31.740> sense<03:03:32.100> now<03:03:32.880> lastly<03:03:33.240> normal 03:03:33.710 --> 03:03:33.720 align:start position:0% which makes sense now lastly normal 03:03:33.720 --> 03:03:36.230 align:start position:0% which makes sense now lastly normal ambient<03:03:34.319> noise<03:03:34.680> also<03:03:35.399> called<03:03:35.580> background 03:03:36.230 --> 03:03:36.240 align:start position:0% ambient noise also called background 03:03:36.240 --> 03:03:39.110 align:start position:0% ambient noise also called background noise<03:03:36.720> or<03:03:37.560> the<03:03:37.740> noise<03:03:37.920> that's<03:03:38.340> present<03:03:38.760> due<03:03:39.000> to 03:03:39.110 --> 03:03:39.120 align:start position:0% noise or the noise that's present due to 03:03:39.120 --> 03:03:41.150 align:start position:0% noise or the noise that's present due to atmospheric<03:03:39.779> conditions<03:03:40.319> like<03:03:40.680> solar 03:03:41.150 --> 03:03:41.160 align:start position:0% atmospheric conditions like solar 03:03:41.160 --> 03:03:43.490 align:start position:0% atmospheric conditions like solar disturbances<03:03:41.819> radio<03:03:42.300> broadcasting<03:03:43.140> towers 03:03:43.490 --> 03:03:43.500 align:start position:0% disturbances radio broadcasting towers 03:03:43.500 --> 03:03:46.190 align:start position:0% disturbances radio broadcasting towers that<03:03:43.859> are<03:03:43.979> nearby<03:03:44.640> Etc<03:03:44.840> the<03:03:45.840> main<03:03:45.899> thing<03:03:46.020> to 03:03:46.190 --> 03:03:46.200 align:start position:0% that are nearby Etc the main thing to 03:03:46.200 --> 03:03:47.510 align:start position:0% that are nearby Etc the main thing to consider<03:03:46.439> with<03:03:46.620> ambient<03:03:46.979> noise<03:03:47.160> is<03:03:47.399> the 03:03:47.510 --> 03:03:47.520 align:start position:0% consider with ambient noise is the 03:03:47.520 --> 03:03:49.490 align:start position:0% consider with ambient noise is the distance<03:03:47.640> or<03:03:47.880> the<03:03:47.939> the<03:03:48.479> length<03:03:48.779> of<03:03:48.899> your<03:03:49.080> media 03:03:49.490 --> 03:03:49.500 align:start position:0% distance or the the length of your media 03:03:49.500 --> 03:03:52.250 align:start position:0% distance or the the length of your media the<03:03:50.160> longer<03:03:50.399> your<03:03:50.520> media<03:03:50.819> run<03:03:51.060> is<03:03:51.359> the<03:03:51.899> closer 03:03:52.250 --> 03:03:52.260 align:start position:0% the longer your media run is the closer 03:03:52.260 --> 03:03:54.710 align:start position:0% the longer your media run is the closer to<03:03:52.439> its<03:03:52.859> maximum<03:03:53.220> rated<03:03:53.580> length<03:03:54.060> then<03:03:54.540> the 03:03:54.710 --> 03:03:54.720 align:start position:0% to its maximum rated length then the 03:03:54.720 --> 03:03:57.469 align:start position:0% to its maximum rated length then the more<03:03:54.840> susceptible<03:03:55.819> your<03:03:56.819> signal<03:03:57.120> is<03:03:57.240> going<03:03:57.359> to 03:03:57.469 --> 03:03:57.479 align:start position:0% more susceptible your signal is going to 03:03:57.479 --> 03:04:00.410 align:start position:0% more susceptible your signal is going to be<03:03:57.540> so<03:03:58.380> to<03:03:58.680> combat<03:03:59.040> this<03:03:59.279> we<03:03:59.760> one<03:04:00.060> thing<03:04:00.180> we<03:04:00.359> can 03:04:00.410 --> 03:04:00.420 align:start position:0% be so to combat this we one thing we can 03:04:00.420 --> 03:04:03.170 align:start position:0% be so to combat this we one thing we can do<03:04:00.540> is<03:04:00.720> called<03:04:00.960> grounding<03:04:01.620> which<03:04:02.580> is<03:04:02.700> a<03:04:02.880> method 03:04:03.170 --> 03:04:03.180 align:start position:0% do is called grounding which is a method 03:04:03.180 --> 03:04:06.230 align:start position:0% do is called grounding which is a method of<03:04:03.479> taking<03:04:03.779> the<03:04:04.200> shielding<03:04:04.740> or<03:04:05.580> a<03:04:05.880> conductor 03:04:06.230 --> 03:04:06.240 align:start position:0% of taking the shielding or a conductor 03:04:06.240 --> 03:04:08.570 align:start position:0% of taking the shielding or a conductor and<03:04:06.899> connecting<03:04:07.500> it<03:04:07.620> to<03:04:07.800> an<03:04:08.100> electrical 03:04:08.570 --> 03:04:08.580 align:start position:0% and connecting it to an electrical 03:04:08.580 --> 03:04:11.269 align:start position:0% and connecting it to an electrical ground<03:04:09.300> point<03:04:09.720> that<03:04:10.319> is<03:04:10.500> directly<03:04:10.859> in<03:04:10.979> content 03:04:11.269 --> 03:04:11.279 align:start position:0% ground point that is directly in content 03:04:11.279 --> 03:04:13.429 align:start position:0% ground point that is directly in content with<03:04:11.460> literally<03:04:11.880> the<03:04:12.180> Earth's<03:04:12.540> ground<03:04:12.720> now 03:04:13.429 --> 03:04:13.439 align:start position:0% with literally the Earth's ground now 03:04:13.439 --> 03:04:15.889 align:start position:0% with literally the Earth's ground now when<03:04:13.620> we<03:04:13.800> connect<03:04:13.979> a<03:04:14.279> network<03:04:14.520> segment<03:04:15.060> at<03:04:15.660> one 03:04:15.889 --> 03:04:15.899 align:start position:0% when we connect a network segment at one 03:04:15.899 --> 03:04:18.950 align:start position:0% when we connect a network segment at one point<03:04:16.140> to<03:04:16.439> a<03:04:16.680> ground<03:04:16.859> this<03:04:17.819> basically<03:04:18.300> shunts 03:04:18.950 --> 03:04:18.960 align:start position:0% point to a ground this basically shunts 03:04:18.960 --> 03:04:22.150 align:start position:0% point to a ground this basically shunts or<03:04:19.080> drains<03:04:19.620> the<03:04:19.979> extraneous<03:04:20.939> noise 03:04:22.150 --> 03:04:22.160 align:start position:0% or drains the extraneous noise 03:04:22.160 --> 03:04:27.349 align:start position:0% or drains the extraneous noise only<03:04:23.160> leaving<03:04:23.580> the<03:04:24.300> data<03:04:24.660> signal<03:04:25.460> so<03:04:26.460> at<03:04:27.240> the 03:04:27.349 --> 03:04:27.359 align:start position:0% only leaving the data signal so at the 03:04:27.359 --> 03:04:29.630 align:start position:0% only leaving the data signal so at the same<03:04:27.540> time<03:04:27.899> if<03:04:28.500> more<03:04:28.740> than<03:04:28.920> one<03:04:29.220> point<03:04:29.399> is 03:04:29.630 --> 03:04:29.640 align:start position:0% same time if more than one point is 03:04:29.640 --> 03:04:31.969 align:start position:0% same time if more than one point is grounded<03:04:30.060> this<03:04:30.359> can<03:04:30.600> introduce<03:04:31.380> even<03:04:31.620> more 03:04:31.969 --> 03:04:31.979 align:start position:0% grounded this can introduce even more 03:04:31.979 --> 03:04:33.769 align:start position:0% grounded this can introduce even more noise<03:04:32.220> which<03:04:32.880> is<03:04:32.939> going<03:04:33.120> to<03:04:33.240> greatly<03:04:33.540> reduce 03:04:33.769 --> 03:04:33.779 align:start position:0% noise which is going to greatly reduce 03:04:33.779 --> 03:04:35.929 align:start position:0% noise which is going to greatly reduce the<03:04:34.200> quality<03:04:34.500> of<03:04:34.680> the<03:04:34.859> signal<03:04:35.100> if<03:04:35.640> not<03:04:35.819> even 03:04:35.929 --> 03:04:35.939 align:start position:0% the quality of the signal if not even 03:04:35.939 --> 03:04:38.389 align:start position:0% the quality of the signal if not even completely<03:04:36.479> get<03:04:36.960> rid<03:04:37.140> of<03:04:37.260> it<03:04:37.439> so<03:04:37.859> we<03:04:38.160> can<03:04:38.279> only 03:04:38.389 --> 03:04:38.399 align:start position:0% completely get rid of it so we can only 03:04:38.399 --> 03:04:41.870 align:start position:0% completely get rid of it so we can only we<03:04:38.700> only<03:04:38.880> want<03:04:39.060> to<03:04:39.300> uh<03:04:39.660> ground<03:04:40.080> the<03:04:40.500> point<03:04:40.880> uh 03:04:41.870 --> 03:04:41.880 align:start position:0% we only want to uh ground the point uh 03:04:41.880 --> 03:04:44.030 align:start position:0% we only want to uh ground the point uh once<03:04:42.359> which<03:04:42.660> is<03:04:42.840> important<03:04:43.200> if<03:04:43.500> we<03:04:43.560> do<03:04:43.740> it<03:04:43.859> more 03:04:44.030 --> 03:04:44.040 align:start position:0% once which is important if we do it more 03:04:44.040 --> 03:04:45.230 align:start position:0% once which is important if we do it more than<03:04:44.160> once<03:04:44.399> we're<03:04:44.580> going<03:04:44.760> to<03:04:44.819> be<03:04:44.880> in<03:04:45.060> major 03:04:45.230 --> 03:04:45.240 align:start position:0% than once we're going to be in major 03:04:45.240 --> 03:04:46.969 align:start position:0% than once we're going to be in major trouble<03:04:45.540> not<03:04:46.140> only<03:04:46.260> do<03:04:46.380> we<03:04:46.560> ground<03:04:46.740> for 03:04:46.969 --> 03:04:46.979 align:start position:0% trouble not only do we ground for 03:04:46.979 --> 03:04:49.130 align:start position:0% trouble not only do we ground for Network<03:04:47.160> for<03:04:47.460> a<03:04:47.640> performer<03:04:47.880> but<03:04:48.540> we<03:04:48.720> also<03:04:48.960> do 03:04:49.130 --> 03:04:49.140 align:start position:0% Network for a performer but we also do 03:04:49.140 --> 03:04:51.830 align:start position:0% Network for a performer but we also do it<03:04:49.319> for<03:04:49.620> safety<03:04:50.580> because<03:04:51.060> most<03:04:51.359> electrical 03:04:51.830 --> 03:04:51.840 align:start position:0% it for safety because most electrical 03:04:51.840 --> 03:04:53.450 align:start position:0% it for safety because most electrical devices<03:04:52.140> have<03:04:52.500> to<03:04:52.620> be<03:04:52.740> grounded<03:04:53.040> in<03:04:53.100> one<03:04:53.340> way 03:04:53.450 --> 03:04:53.460 align:start position:0% devices have to be grounded in one way 03:04:53.460 --> 03:04:56.150 align:start position:0% devices have to be grounded in one way or<03:04:53.580> the<03:04:53.760> other<03:04:53.819> otherwise<03:04:54.300> you<03:04:54.840> know<03:04:55.020> we<03:04:55.740> just 03:04:56.150 --> 03:04:56.160 align:start position:0% or the other otherwise you know we just 03:04:56.160 --> 03:04:58.370 align:start position:0% or the other otherwise you know we just like<03:04:56.340> we<03:04:56.460> saw<03:04:56.640> with<03:04:56.880> a<03:04:57.180> plus<03:04:57.359> and<03:04:57.899> touching 03:04:58.370 --> 03:04:58.380 align:start position:0% like we saw with a plus and touching 03:04:58.380 --> 03:05:00.590 align:start position:0% like we saw with a plus and touching devices<03:04:58.740> if<03:04:59.340> we<03:04:59.460> don't<03:04:59.580> ground<03:04:59.819> something<03:05:00.180> we 03:05:00.590 --> 03:05:00.600 align:start position:0% devices if we don't ground something we 03:05:00.600 --> 03:05:03.290 align:start position:0% devices if we don't ground something we could<03:05:00.840> possibly<03:05:01.439> damage<03:05:01.859> it<03:05:02.040> this<03:05:02.760> is<03:05:02.880> mostly 03:05:03.290 --> 03:05:03.300 align:start position:0% could possibly damage it this is mostly 03:05:03.300 --> 03:05:07.490 align:start position:0% could possibly damage it this is mostly to<03:05:03.600> redirect<03:05:04.040> uh<03:05:05.040> High<03:05:05.279> voltages 03:05:07.490 --> 03:05:07.500 align:start position:0% to redirect uh High voltages 03:05:07.500 --> 03:05:09.170 align:start position:0% to redirect uh High voltages into<03:05:07.979> the<03:05:08.220> ground<03:05:08.340> where<03:05:08.640> they're<03:05:08.819> not<03:05:08.939> going 03:05:09.170 --> 03:05:09.180 align:start position:0% into the ground where they're not going 03:05:09.180 --> 03:05:11.809 align:start position:0% into the ground where they're not going to<03:05:09.359> harm<03:05:09.600> your<03:05:09.840> equipment<03:05:10.260> now<03:05:11.100> electricians 03:05:11.809 --> 03:05:11.819 align:start position:0% to harm your equipment now electricians 03:05:11.819 --> 03:05:14.030 align:start position:0% to harm your equipment now electricians have<03:05:12.000> special<03:05:12.240> ground<03:05:12.600> points<03:05:13.200> or<03:05:13.500> dedicated 03:05:14.030 --> 03:05:14.040 align:start position:0% have special ground points or dedicated 03:05:14.040 --> 03:05:15.730 align:start position:0% have special ground points or dedicated ground<03:05:14.399> points<03:05:14.880> that<03:05:15.060> are<03:05:15.180> designed 03:05:15.730 --> 03:05:15.740 align:start position:0% ground points that are designed 03:05:15.740 --> 03:05:18.290 align:start position:0% ground points that are designed specifically<03:05:16.740> for<03:05:17.399> sensitive<03:05:17.819> electrical 03:05:18.290 --> 03:05:18.300 align:start position:0% specifically for sensitive electrical 03:05:18.300 --> 03:05:21.050 align:start position:0% specifically for sensitive electrical equipment<03:05:18.720> these<03:05:19.620> isolated<03:05:19.979> grounds<03:05:20.580> they're 03:05:21.050 --> 03:05:21.060 align:start position:0% equipment these isolated grounds they're 03:05:21.060 --> 03:05:22.790 align:start position:0% equipment these isolated grounds they're def<03:05:21.300> they're<03:05:21.840> usually<03:05:22.080> going<03:05:22.200> to<03:05:22.319> be<03:05:22.380> colored 03:05:22.790 --> 03:05:22.800 align:start position:0% def they're usually going to be colored 03:05:22.800 --> 03:05:24.950 align:start position:0% def they're usually going to be colored orange<03:05:23.040> which<03:05:23.760> helps<03:05:24.060> differentiate<03:05:24.720> them 03:05:24.950 --> 03:05:24.960 align:start position:0% orange which helps differentiate them 03:05:24.960 --> 03:05:27.469 align:start position:0% orange which helps differentiate them from<03:05:25.560> normal<03:05:25.800> plugs<03:05:26.399> so<03:05:26.880> if<03:05:27.000> you<03:05:27.120> see<03:05:27.300> an 03:05:27.469 --> 03:05:27.479 align:start position:0% from normal plugs so if you see an 03:05:27.479 --> 03:05:30.950 align:start position:0% from normal plugs so if you see an orange<03:05:27.720> looking<03:05:28.140> plug<03:05:28.560> that<03:05:29.100> is<03:05:29.340> a<03:05:29.700> special<03:05:29.960> uh 03:05:30.950 --> 03:05:30.960 align:start position:0% orange looking plug that is a special uh 03:05:30.960 --> 03:05:32.690 align:start position:0% orange looking plug that is a special uh isolated<03:05:31.620> ground 03:05:32.690 --> 03:05:32.700 align:start position:0% isolated ground 03:05:32.700 --> 03:05:35.030 align:start position:0% isolated ground now<03:05:33.240> the<03:05:33.540> shielding<03:05:33.960> around<03:05:34.080> a<03:05:34.439> cable<03:05:34.680> as<03:05:34.920> you 03:05:35.030 --> 03:05:35.040 align:start position:0% now the shielding around a cable as you 03:05:35.040 --> 03:05:37.790 align:start position:0% now the shielding around a cable as you can<03:05:35.160> see<03:05:35.279> here<03:05:35.580> on<03:05:35.760> this<03:05:35.939> coaxial<03:05:36.600> cable 03:05:37.790 --> 03:05:37.800 align:start position:0% can see here on this coaxial cable 03:05:37.800 --> 03:05:40.429 align:start position:0% can see here on this coaxial cable um<03:05:37.859> is<03:05:38.100> a<03:05:38.399> noise<03:05:38.520> prevention<03:05:39.120> measure<03:05:39.840> that 03:05:40.429 --> 03:05:40.439 align:start position:0% um is a noise prevention measure that 03:05:40.439 --> 03:05:42.469 align:start position:0% um is a noise prevention measure that takes<03:05:40.680> the<03:05:40.920> noise<03:05:41.040> and<03:05:41.520> drains<03:05:41.939> it<03:05:42.120> through 03:05:42.469 --> 03:05:42.479 align:start position:0% takes the noise and drains it through 03:05:42.479 --> 03:05:45.050 align:start position:0% takes the noise and drains it through the<03:05:42.720> shielding<03:05:43.200> away<03:05:43.979> from<03:05:44.340> the<03:05:44.520> conductor<03:05:44.760> in 03:05:45.050 --> 03:05:45.060 align:start position:0% the shielding away from the conductor in 03:05:45.060 --> 03:05:47.150 align:start position:0% the shielding away from the conductor in the<03:05:45.240> center<03:05:45.420> that<03:05:45.840> is<03:05:45.960> carrying<03:05:46.560> the<03:05:46.740> draining 03:05:47.150 --> 03:05:47.160 align:start position:0% the center that is carrying the draining 03:05:47.160 --> 03:05:49.910 align:start position:0% the center that is carrying the draining the<03:05:47.580> the<03:05:47.700> data<03:05:48.060> traffic<03:05:48.319> now<03:05:49.319> the<03:05:49.500> shielding 03:05:49.910 --> 03:05:49.920 align:start position:0% the the data traffic now the shielding 03:05:49.920 --> 03:05:52.070 align:start position:0% the the data traffic now the shielding is<03:05:50.100> then<03:05:50.279> connected<03:05:50.880> to<03:05:51.240> a<03:05:51.420> single<03:05:51.779> ground 03:05:52.070 --> 03:05:52.080 align:start position:0% is then connected to a single ground 03:05:52.080 --> 03:05:55.070 align:start position:0% is then connected to a single ground Point<03:05:52.460> flushing<03:05:53.460> the<03:05:53.640> noise<03:05:53.760> away<03:05:54.180> the 03:05:55.070 --> 03:05:55.080 align:start position:0% Point flushing the noise away the 03:05:55.080 --> 03:05:56.809 align:start position:0% Point flushing the noise away the connection<03:05:55.500> between<03:05:55.920> the<03:05:56.220> shield<03:05:56.340> and<03:05:56.640> the 03:05:56.809 --> 03:05:56.819 align:start position:0% connection between the shield and the 03:05:56.819 --> 03:05:59.269 align:start position:0% connection between the shield and the ground<03:05:57.000> point<03:05:57.240> is<03:05:57.720> also<03:05:58.020> called<03:05:58.380> the<03:05:58.920> drain 03:05:59.269 --> 03:05:59.279 align:start position:0% ground point is also called the drain 03:05:59.279 --> 03:06:02.269 align:start position:0% ground point is also called the drain which<03:05:59.880> is<03:06:00.000> why<03:06:00.180> we<03:06:00.359> say<03:06:00.540> it's<03:06:00.720> grain<03:06:01.140> drain<03:06:01.859> and 03:06:02.269 --> 03:06:02.279 align:start position:0% which is why we say it's grain drain and 03:06:02.279 --> 03:06:03.590 align:start position:0% which is why we say it's grain drain and this<03:06:02.460> same<03:06:02.640> thing<03:06:02.819> doesn't<03:06:03.060> just<03:06:03.300> go<03:06:03.420> for 03:06:03.590 --> 03:06:03.600 align:start position:0% this same thing doesn't just go for 03:06:03.600 --> 03:06:06.769 align:start position:0% this same thing doesn't just go for coaxial<03:06:04.200> it<03:06:04.380> also<03:06:04.680> goes<03:06:04.979> for<03:06:05.520> STP<03:06:06.120> or<03:06:06.359> shielded 03:06:06.769 --> 03:06:06.779 align:start position:0% coaxial it also goes for STP or shielded 03:06:06.779 --> 03:06:09.170 align:start position:0% coaxial it also goes for STP or shielded twisted<03:06:07.200> pair<03:06:07.380> as<03:06:07.680> well<03:06:07.800> now<03:06:08.520> because<03:06:08.819> the 03:06:09.170 --> 03:06:09.180 align:start position:0% twisted pair as well now because the 03:06:09.180 --> 03:06:12.349 align:start position:0% twisted pair as well now because the noise<03:06:09.359> is<03:06:09.720> often<03:06:10.319> going<03:06:10.800> to<03:06:11.040> be<03:06:11.279> constant<03:06:11.819> the 03:06:12.349 --> 03:06:12.359 align:start position:0% noise is often going to be constant the 03:06:12.359 --> 03:06:15.349 align:start position:0% noise is often going to be constant the method<03:06:12.660> of<03:06:12.960> differential<03:06:13.680> signaling<03:06:14.460> takes 03:06:15.349 --> 03:06:15.359 align:start position:0% method of differential signaling takes 03:06:15.359 --> 03:06:17.210 align:start position:0% method of differential signaling takes two<03:06:15.660> received<03:06:16.140> signals 03:06:17.210 --> 03:06:17.220 align:start position:0% two received signals 03:06:17.220 --> 03:06:21.349 align:start position:0% two received signals and<03:06:18.060> subtracts<03:06:18.899> the<03:06:19.680> equal<03:06:19.920> signals 03:06:21.349 --> 03:06:21.359 align:start position:0% and subtracts the equal signals 03:06:21.359 --> 03:06:22.849 align:start position:0% and subtracts the equal signals which<03:06:21.840> is<03:06:22.020> typically<03:06:22.260> going<03:06:22.439> to<03:06:22.560> be<03:06:22.620> the<03:06:22.740> noise 03:06:22.849 --> 03:06:22.859 align:start position:0% which is typically going to be the noise 03:06:22.859 --> 03:06:25.130 align:start position:0% which is typically going to be the noise of<03:06:23.100> the<03:06:23.220> noise<03:06:23.399> floor<03:06:23.760> and<03:06:24.540> that's<03:06:24.660> going<03:06:24.899> to 03:06:25.130 --> 03:06:25.140 align:start position:0% of the noise floor and that's going to 03:06:25.140 --> 03:06:28.309 align:start position:0% of the noise floor and that's going to give<03:06:25.500> us<03:06:25.620> an<03:06:25.920> end<03:06:26.100> result<03:06:26.399> of<03:06:27.120> Simply<03:06:27.540> the 03:06:28.309 --> 03:06:28.319 align:start position:0% give us an end result of Simply the 03:06:28.319 --> 03:06:30.410 align:start position:0% give us an end result of Simply the noise<03:06:28.500> so<03:06:28.979> basically<03:06:29.279> it<03:06:29.580> takes<03:06:29.819> this<03:06:30.060> signal 03:06:30.410 --> 03:06:30.420 align:start position:0% noise so basically it takes this signal 03:06:30.420 --> 03:06:32.269 align:start position:0% noise so basically it takes this signal input<03:06:30.720> which<03:06:30.960> is<03:06:31.140> a<03:06:31.319> digital<03:06:31.500> input<03:06:31.859> signal 03:06:32.269 --> 03:06:32.279 align:start position:0% input which is a digital input signal 03:06:32.279 --> 03:06:34.070 align:start position:0% input which is a digital input signal and 03:06:34.070 --> 03:06:34.080 align:start position:0% and 03:06:34.080 --> 03:06:37.550 align:start position:0% and it<03:06:34.200> takes<03:06:34.680> that<03:06:35.100> subtracts<03:06:35.939> this 03:06:37.550 --> 03:06:37.560 align:start position:0% it takes that subtracts this 03:06:37.560 --> 03:06:39.730 align:start position:0% it takes that subtracts this and<03:06:38.100> then<03:06:38.220> we<03:06:38.520> can<03:06:38.640> get 03:06:39.730 --> 03:06:39.740 align:start position:0% and then we can get 03:06:39.740 --> 03:06:43.490 align:start position:0% and then we can get a<03:06:40.740> a<03:06:40.979> signal<03:06:41.880> without<03:06:42.060> any<03:06:42.540> noise<03:06:42.779> in<03:06:43.140> it<03:06:43.260> as 03:06:43.490 --> 03:06:43.500 align:start position:0% a a signal without any noise in it as 03:06:43.500 --> 03:06:46.670 align:start position:0% a a signal without any noise in it as you<03:06:43.620> can<03:06:43.740> see 03:06:46.670 --> 03:06:46.680 align:start position:0% 03:06:46.680 --> 03:06:49.010 align:start position:0% now<03:06:47.399> besides<03:06:47.819> differential<03:06:48.300> signaling<03:06:48.779> there 03:06:49.010 --> 03:06:49.020 align:start position:0% now besides differential signaling there 03:06:49.020 --> 03:06:50.150 align:start position:0% now besides differential signaling there are<03:06:49.140> also<03:06:49.260> a<03:06:49.380> few<03:06:49.439> other<03:06:49.560> noise<03:06:49.800> control 03:06:50.150 --> 03:06:50.160 align:start position:0% are also a few other noise control 03:06:50.160 --> 03:06:52.490 align:start position:0% are also a few other noise control considerations<03:06:50.880> we<03:06:51.720> talked<03:06:52.020> about<03:06:52.080> earlier 03:06:52.490 --> 03:06:52.500 align:start position:0% considerations we talked about earlier 03:06:52.500 --> 03:06:54.290 align:start position:0% considerations we talked about earlier something<03:06:52.859> called<03:06:53.220> termination<03:06:53.819> which<03:06:54.180> is 03:06:54.290 --> 03:06:54.300 align:start position:0% something called termination which is 03:06:54.300 --> 03:06:56.630 align:start position:0% something called termination which is really<03:06:54.660> important<03:06:55.020> in<03:06:55.140> networking<03:06:55.640> some 03:06:56.630 --> 03:06:56.640 align:start position:0% really important in networking some 03:06:56.640 --> 03:06:59.030 align:start position:0% really important in networking some cables<03:06:57.180> require<03:06:57.540> termination<03:06:58.380> to<03:06:58.979> be 03:06:59.030 --> 03:06:59.040 align:start position:0% cables require termination to be 03:06:59.040 --> 03:07:03.170 align:start position:0% cables require termination to be installed<03:06:59.460> at<03:06:59.640> the<03:06:59.880> end<03:07:00.060> of<03:07:00.479> either<03:07:00.840> uh 03:07:03.170 --> 03:07:03.180 align:start position:0% installed at the end of either uh 03:07:03.180 --> 03:07:04.790 align:start position:0% installed at the end of either uh the<03:07:03.660> end<03:07:03.779> of<03:07:03.960> either 03:07:04.790 --> 03:07:04.800 align:start position:0% the end of either 03:07:04.800 --> 03:07:07.250 align:start position:0% the end of either connection<03:07:05.420> right<03:07:06.420> if<03:07:06.660> you<03:07:06.779> remember<03:07:06.960> that 03:07:07.250 --> 03:07:07.260 align:start position:0% connection right if you remember that 03:07:07.260 --> 03:07:09.830 align:start position:0% connection right if you remember that from<03:07:07.500> our<03:07:07.680> bus<03:07:07.920> and<03:07:08.819> it<03:07:09.000> has<03:07:09.240> to<03:07:09.420> have<03:07:09.540> the 03:07:09.830 --> 03:07:09.840 align:start position:0% from our bus and it has to have the 03:07:09.840 --> 03:07:13.790 align:start position:0% from our bus and it has to have the appropriate<03:07:10.500> ohm<03:07:11.100> rating 03:07:13.790 --> 03:07:13.800 align:start position:0% 03:07:13.800 --> 03:07:16.370 align:start position:0% if<03:07:14.340> you<03:07:14.580> install<03:07:14.819> the<03:07:15.180> Terminator<03:07:15.660> and<03:07:16.200> it 03:07:16.370 --> 03:07:16.380 align:start position:0% if you install the Terminator and it 03:07:16.380 --> 03:07:18.469 align:start position:0% if you install the Terminator and it doesn't<03:07:16.500> have<03:07:16.800> that<03:07:17.100> proper<03:07:17.399> ohm<03:07:17.819> rating<03:07:18.060> then 03:07:18.469 --> 03:07:18.479 align:start position:0% doesn't have that proper ohm rating then 03:07:18.479 --> 03:07:20.269 align:start position:0% doesn't have that proper ohm rating then it's<03:07:18.720> probably<03:07:18.960> going<03:07:19.260> to 03:07:20.269 --> 03:07:20.279 align:start position:0% it's probably going to 03:07:20.279 --> 03:07:22.670 align:start position:0% it's probably going to um<03:07:20.340> uh<03:07:21.060> actually 03:07:22.670 --> 03:07:22.680 align:start position:0% um uh actually 03:07:22.680 --> 03:07:25.070 align:start position:0% um uh actually it<03:07:22.979> won't<03:07:23.460> work<03:07:23.700> effectively<03:07:24.300> now<03:07:24.720> luckily 03:07:25.070 --> 03:07:25.080 align:start position:0% it won't work effectively now luckily 03:07:25.080 --> 03:07:27.290 align:start position:0% it won't work effectively now luckily for<03:07:25.319> us<03:07:25.439> in<03:07:25.920> most<03:07:26.100> cases<03:07:26.399> the<03:07:26.640> Terminators<03:07:27.120> are 03:07:27.290 --> 03:07:27.300 align:start position:0% for us in most cases the Terminators are 03:07:27.300 --> 03:07:29.030 align:start position:0% for us in most cases the Terminators are installed<03:07:27.660> in<03:07:27.899> these<03:07:28.080> network<03:07:28.260> devices<03:07:28.680> by 03:07:29.030 --> 03:07:29.040 align:start position:0% installed in these network devices by 03:07:29.040 --> 03:07:31.550 align:start position:0% installed in these network devices by default<03:07:29.460> but<03:07:30.120> not<03:07:30.359> too<03:07:30.720> long<03:07:30.840> ago<03:07:31.020> you<03:07:31.260> had<03:07:31.439> to 03:07:31.550 --> 03:07:31.560 align:start position:0% default but not too long ago you had to 03:07:31.560 --> 03:07:32.990 align:start position:0% default but not too long ago you had to install<03:07:31.680> them<03:07:32.040> manually<03:07:32.399> and<03:07:32.700> you<03:07:32.760> had<03:07:32.880> to 03:07:32.990 --> 03:07:33.000 align:start position:0% install them manually and you had to 03:07:33.000 --> 03:07:34.670 align:start position:0% install them manually and you had to make<03:07:33.180> sure<03:07:33.300> the<03:07:33.540> impedance<03:07:34.020> or<03:07:34.200> the<03:07:34.380> amount<03:07:34.560> of 03:07:34.670 --> 03:07:34.680 align:start position:0% make sure the impedance or the amount of 03:07:34.680 --> 03:07:37.550 align:start position:0% make sure the impedance or the amount of ohms<03:07:35.040> was<03:07:35.939> matched<03:07:36.420> it<03:07:36.779> was<03:07:36.899> a<03:07:37.080> fairly<03:07:37.319> simple 03:07:37.550 --> 03:07:37.560 align:start position:0% ohms was matched it was a fairly simple 03:07:37.560 --> 03:07:41.750 align:start position:0% ohms was matched it was a fairly simple task<03:07:38.300> but<03:07:39.300> the<03:07:40.260> specific<03:07:40.500> impedance<03:07:41.160> could 03:07:41.750 --> 03:07:41.760 align:start position:0% task but the specific impedance could 03:07:41.760 --> 03:07:44.750 align:start position:0% task but the specific impedance could have<03:07:41.880> been<03:07:42.000> marked<03:07:42.300> on<03:07:42.420> a<03:07:42.540> cable<03:07:42.779> jacket<03:07:43.399> or<03:07:44.399> if 03:07:44.750 --> 03:07:44.760 align:start position:0% have been marked on a cable jacket or if 03:07:44.760 --> 03:07:46.730 align:start position:0% have been marked on a cable jacket or if a<03:07:44.939> large<03:07:45.120> amount<03:07:45.420> of<03:07:45.600> cable<03:07:45.779> was<03:07:46.020> installed<03:07:46.500> it 03:07:46.730 --> 03:07:46.740 align:start position:0% a large amount of cable was installed it 03:07:46.740 --> 03:07:49.010 align:start position:0% a large amount of cable was installed it just<03:07:47.040> added<03:07:47.399> another<03:07:47.640> step<03:07:48.240> to<03:07:48.540> the<03:07:48.660> process 03:07:49.010 --> 03:07:49.020 align:start position:0% just added another step to the process 03:07:49.020 --> 03:07:50.809 align:start position:0% just added another step to the process now<03:07:49.680> something<03:07:49.859> else<03:07:50.040> to<03:07:50.160> keep<03:07:50.340> in<03:07:50.460> mind<03:07:50.580> is 03:07:50.809 --> 03:07:50.819 align:start position:0% now something else to keep in mind is 03:07:50.819 --> 03:07:53.090 align:start position:0% now something else to keep in mind is how<03:07:51.120> you<03:07:51.240> run<03:07:51.420> the<03:07:51.600> cable<03:07:51.840> your<03:07:52.140> cable<03:07:52.380> run<03:07:52.620> you 03:07:53.090 --> 03:07:53.100 align:start position:0% how you run the cable your cable run you 03:07:53.100 --> 03:07:54.349 align:start position:0% how you run the cable your cable run you don't<03:07:53.220> want<03:07:53.340> to<03:07:53.460> run<03:07:53.640> data<03:07:54.060> cable<03:07:54.180> and 03:07:54.349 --> 03:07:54.359 align:start position:0% don't want to run data cable and 03:07:54.359 --> 03:07:56.510 align:start position:0% don't want to run data cable and electrical<03:07:54.779> cable<03:07:54.960> in<03:07:55.200> the<03:07:55.319> same<03:07:55.439> tray<03:07:55.859> and 03:07:56.510 --> 03:07:56.520 align:start position:0% electrical cable in the same tray and 03:07:56.520 --> 03:07:58.130 align:start position:0% electrical cable in the same tray and you<03:07:56.700> should<03:07:56.819> try<03:07:57.000> to<03:07:57.240> avoid<03:07:57.540> running<03:07:57.840> your 03:07:58.130 --> 03:07:58.140 align:start position:0% you should try to avoid running your 03:07:58.140 --> 03:08:00.110 align:start position:0% you should try to avoid running your data<03:07:58.500> cable<03:07:58.680> parallel<03:07:59.279> to<03:07:59.520> any<03:07:59.700> electrical 03:08:00.110 --> 03:08:00.120 align:start position:0% data cable parallel to any electrical 03:08:00.120 --> 03:08:02.330 align:start position:0% data cable parallel to any electrical cables<03:08:00.540> or<03:08:00.899> any<03:08:01.080> other<03:08:01.260> data<03:08:01.620> cables<03:08:01.979> in<03:08:02.220> order 03:08:02.330 --> 03:08:02.340 align:start position:0% cables or any other data cables in order 03:08:02.340 --> 03:08:04.969 align:start position:0% cables or any other data cables in order to<03:08:02.640> reduce<03:08:02.819> what's<03:08:03.240> called<03:08:03.540> a<03:08:04.319> crosstalk 03:08:04.969 --> 03:08:04.979 align:start position:0% to reduce what's called a crosstalk 03:08:04.979 --> 03:08:07.010 align:start position:0% to reduce what's called a crosstalk which<03:08:05.340> basically<03:08:05.760> means<03:08:06.120> the<03:08:06.359> signal<03:08:06.720> sort<03:08:06.899> of 03:08:07.010 --> 03:08:07.020 align:start position:0% which basically means the signal sort of 03:08:07.020 --> 03:08:08.690 align:start position:0% which basically means the signal sort of jumps<03:08:07.260> from<03:08:07.500> one<03:08:07.680> to<03:08:07.859> the<03:08:08.040> other 03:08:08.690 --> 03:08:08.700 align:start position:0% jumps from one to the other 03:08:08.700 --> 03:08:10.790 align:start position:0% jumps from one to the other now<03:08:09.180> if<03:08:09.359> you<03:08:09.479> keep<03:08:09.600> data<03:08:10.020> cables<03:08:10.319> away<03:08:10.500> from 03:08:10.790 --> 03:08:10.800 align:start position:0% now if you keep data cables away from 03:08:10.800 --> 03:08:13.130 align:start position:0% now if you keep data cables away from Motors<03:08:11.279> fluorescent<03:08:12.180> lighting<03:08:12.600> high<03:08:12.960> power 03:08:13.130 --> 03:08:13.140 align:start position:0% Motors fluorescent lighting high power 03:08:13.140 --> 03:08:15.889 align:start position:0% Motors fluorescent lighting high power devices<03:08:13.620> like<03:08:13.979> we<03:08:14.160> saw<03:08:14.399> you<03:08:15.120> owe<03:08:15.300> and<03:08:15.600> you 03:08:15.889 --> 03:08:15.899 align:start position:0% devices like we saw you owe and you 03:08:15.899 --> 03:08:17.450 align:start position:0% devices like we saw you owe and you always<03:08:16.020> ground<03:08:16.380> your<03:08:16.680> electrical<03:08:17.160> equipment 03:08:17.450 --> 03:08:17.460 align:start position:0% always ground your electrical equipment 03:08:17.460 --> 03:08:19.670 align:start position:0% always ground your electrical equipment and<03:08:17.700> electrical<03:08:18.120> circuits<03:08:18.479> according<03:08:18.899> to<03:08:19.140> the 03:08:19.670 --> 03:08:19.680 align:start position:0% and electrical circuits according to the 03:08:19.680 --> 03:08:23.030 align:start position:0% and electrical circuits according to the manufacturer<03:08:20.520> and<03:08:21.060> you<03:08:21.420> allow<03:08:21.779> for<03:08:22.380> uh<03:08:22.800> all 03:08:23.030 --> 03:08:23.040 align:start position:0% manufacturer and you allow for uh all 03:08:23.040 --> 03:08:24.050 align:start position:0% manufacturer and you allow for uh all the<03:08:23.100> recommended<03:08:23.580> installation 03:08:24.050 --> 03:08:24.060 align:start position:0% the recommended installation 03:08:24.060 --> 03:08:25.849 align:start position:0% the recommended installation requirements<03:08:24.720> and<03:08:24.899> grounding<03:08:25.319> requirements 03:08:25.849 --> 03:08:25.859 align:start position:0% requirements and grounding requirements 03:08:25.859 --> 03:08:27.710 align:start position:0% requirements and grounding requirements that<03:08:26.160> they<03:08:26.399> provide<03:08:26.760> then<03:08:27.180> you<03:08:27.420> should<03:08:27.540> be 03:08:27.710 --> 03:08:27.720 align:start position:0% that they provide then you should be 03:08:27.720 --> 03:08:29.090 align:start position:0% that they provide then you should be good<03:08:27.899> to<03:08:28.080> go<03:08:28.200> when<03:08:28.439> you're<03:08:28.560> connecting<03:08:28.979> your 03:08:29.090 --> 03:08:29.100 align:start position:0% good to go when you're connecting your 03:08:29.100 --> 03:08:31.670 align:start position:0% good to go when you're connecting your cables<03:08:29.520> together<03:08:30.180> and<03:08:30.720> when<03:08:30.960> you're<03:08:31.680> um 03:08:31.670 --> 03:08:31.680 align:start position:0% cables together and when you're um 03:08:31.680 --> 03:08:34.670 align:start position:0% cables together and when you're um running<03:08:32.399> your<03:08:32.700> cables<03:08:33.060> as<03:08:33.180> well<03:08:33.359> so<03:08:34.200> just<03:08:34.500> to 03:08:34.670 --> 03:08:34.680 align:start position:0% running your cables as well so just to 03:08:34.680 --> 03:08:36.410 align:start position:0% running your cables as well so just to recap<03:08:34.979> what<03:08:35.220> we've<03:08:35.460> talked<03:08:35.700> about<03:08:35.760> here<03:08:36.120> first 03:08:36.410 --> 03:08:36.420 align:start position:0% recap what we've talked about here first 03:08:36.420 --> 03:08:39.650 align:start position:0% recap what we've talked about here first we<03:08:36.779> looked<03:08:37.080> at<03:08:37.140> a<03:08:37.439> Nick<03:08:37.680> and<03:08:38.399> a<03:08:38.700> network<03:08:38.819> or<03:08:39.359> a 03:08:39.650 --> 03:08:39.660 align:start position:0% we looked at a Nick and a network or a 03:08:39.660 --> 03:08:48.230 align:start position:0% we looked at a Nick and a network or a network<03:08:39.840> interface<03:08:40.620> card 03:08:48.230 --> 03:08:48.240 align:start position:0% 03:08:48.240 --> 03:08:48.950 align:start position:0% foreign 03:08:48.950 --> 03:08:48.960 align:start position:0% foreign 03:08:48.960 --> 03:08:51.110 align:start position:0% foreign we<03:08:49.740> describe<03:08:50.100> the<03:08:50.160> transceiver<03:08:50.760> something 03:08:51.110 --> 03:08:51.120 align:start position:0% we describe the transceiver something 03:08:51.120 --> 03:08:53.389 align:start position:0% we describe the transceiver something that<03:08:51.479> goes<03:08:51.840> on<03:08:52.500> the<03:08:52.620> card<03:08:52.800> and<03:08:53.040> how<03:08:53.220> it 03:08:53.389 --> 03:08:53.399 align:start position:0% that goes on the card and how it 03:08:53.399 --> 03:08:56.150 align:start position:0% that goes on the card and how it functions<03:08:53.939> we<03:08:54.779> also<03:08:55.020> looked<03:08:55.319> at<03:08:55.380> identifying 03:08:56.150 --> 03:08:56.160 align:start position:0% functions we also looked at identifying 03:08:56.160 --> 03:08:58.429 align:start position:0% functions we also looked at identifying the<03:08:56.340> characteristics<03:08:56.880> of<03:08:57.120> a<03:08:57.359> switch<03:08:57.540> which<03:08:58.260> if 03:08:58.429 --> 03:08:58.439 align:start position:0% the characteristics of a switch which if 03:08:58.439 --> 03:09:01.070 align:start position:0% the characteristics of a switch which if you<03:08:58.620> remember<03:08:58.800> use<03:08:59.340> Mac<03:08:59.880> addressing<03:09:00.479> we 03:09:01.070 --> 03:09:01.080 align:start position:0% you remember use Mac addressing we 03:09:01.080 --> 03:09:03.290 align:start position:0% you remember use Mac addressing we defined<03:09:01.500> trunking<03:09:02.160> Port<03:09:02.520> mirroring<03:09:03.060> and 03:09:03.290 --> 03:09:03.300 align:start position:0% defined trunking Port mirroring and 03:09:03.300 --> 03:09:05.510 align:start position:0% defined trunking Port mirroring and channel<03:09:03.540> bonding<03:09:04.080> remember<03:09:04.319> trunking<03:09:05.100> was 03:09:05.510 --> 03:09:05.520 align:start position:0% channel bonding remember trunking was 03:09:05.520 --> 03:09:07.730 align:start position:0% channel bonding remember trunking was using<03:09:05.939> two<03:09:06.180> or<03:09:06.359> more<03:09:06.479> ports<03:09:06.899> as<03:09:07.200> though<03:09:07.380> they 03:09:07.730 --> 03:09:07.740 align:start position:0% using two or more ports as though they 03:09:07.740 --> 03:09:10.250 align:start position:0% using two or more ports as though they were<03:09:07.979> one<03:09:08.700> port<03:09:09.120> mirroring<03:09:09.660> usually<03:09:09.960> going<03:09:10.140> to 03:09:10.250 --> 03:09:10.260 align:start position:0% were one port mirroring usually going to 03:09:10.260 --> 03:09:13.130 align:start position:0% were one port mirroring usually going to use<03:09:10.380> for<03:09:10.680> Diagnostic<03:09:11.520> purposes<03:09:12.060> and<03:09:13.020> then 03:09:13.130 --> 03:09:13.140 align:start position:0% use for Diagnostic purposes and then 03:09:13.140 --> 03:09:15.349 align:start position:0% use for Diagnostic purposes and then Channel<03:09:13.439> bonding<03:09:14.160> which<03:09:14.640> is<03:09:14.819> uh<03:09:15.060> sort<03:09:15.300> of 03:09:15.349 --> 03:09:15.359 align:start position:0% Channel bonding which is uh sort of 03:09:15.359 --> 03:09:17.450 align:start position:0% Channel bonding which is uh sort of bonding<03:09:15.720> those<03:09:15.840> Nicks<03:09:16.260> together<03:09:16.439> we<03:09:17.220> also 03:09:17.450 --> 03:09:17.460 align:start position:0% bonding those Nicks together we also 03:09:17.460 --> 03:09:19.610 align:start position:0% bonding those Nicks together we also described<03:09:17.939> a<03:09:18.240> router<03:09:18.600> and<03:09:18.779> a<03:09:18.899> Gateway<03:09:19.260> which 03:09:19.610 --> 03:09:19.620 align:start position:0% described a router and a Gateway which 03:09:19.620 --> 03:09:22.010 align:start position:0% described a router and a Gateway which again<03:09:19.800> operate<03:09:20.399> with<03:09:20.700> IP<03:09:21.120> addresses<03:09:21.600> instead 03:09:22.010 --> 03:09:22.020 align:start position:0% again operate with IP addresses instead 03:09:22.020 --> 03:09:24.230 align:start position:0% again operate with IP addresses instead of<03:09:22.080> Max<03:09:22.319> and<03:09:22.620> they<03:09:22.800> allow<03:09:23.160> us<03:09:23.279> whereas 03:09:24.230 --> 03:09:24.240 align:start position:0% of Max and they allow us whereas 03:09:24.240 --> 03:09:26.750 align:start position:0% of Max and they allow us whereas switches<03:09:24.840> allow<03:09:25.140> us<03:09:25.260> to<03:09:25.560> work<03:09:25.740> within<03:09:26.220> a<03:09:26.399> lan 03:09:26.750 --> 03:09:26.760 align:start position:0% switches allow us to work within a lan 03:09:26.760 --> 03:09:29.389 align:start position:0% switches allow us to work within a lan IP<03:09:27.420> addresses<03:09:27.840> or<03:09:28.319> rather<03:09:28.500> routers<03:09:28.979> allow<03:09:29.279> us 03:09:29.389 --> 03:09:29.399 align:start position:0% IP addresses or rather routers allow us 03:09:29.399 --> 03:09:31.790 align:start position:0% IP addresses or rather routers allow us and<03:09:29.640> gateways<03:09:30.180> to<03:09:30.420> operate<03:09:30.840> within<03:09:31.200> a<03:09:31.380> Wan<03:09:31.620> or 03:09:31.790 --> 03:09:31.800 align:start position:0% and gateways to operate within a Wan or 03:09:31.800 --> 03:09:34.010 align:start position:0% and gateways to operate within a Wan or a<03:09:31.920> wide<03:09:32.100> area<03:09:32.279> network<03:09:32.580> finally<03:09:33.479> we<03:09:33.720> looked<03:09:33.960> at 03:09:34.010 --> 03:09:34.020 align:start position:0% a wide area network finally we looked at 03:09:34.020 --> 03:09:37.250 align:start position:0% a wide area network finally we looked at some<03:09:34.140> Legacy<03:09:34.560> devices<03:09:35.240> and<03:09:36.240> we<03:09:36.420> defined<03:09:36.899> noise 03:09:37.250 --> 03:09:37.260 align:start position:0% some Legacy devices and we defined noise 03:09:37.260 --> 03:09:39.769 align:start position:0% some Legacy devices and we defined noise and<03:09:37.680> the<03:09:37.859> sources<03:09:38.279> of<03:09:38.460> noise<03:09:38.700> including<03:09:39.600> any 03:09:39.769 --> 03:09:39.779 align:start position:0% and the sources of noise including any 03:09:39.779 --> 03:09:41.809 align:start position:0% and the sources of noise including any of<03:09:39.960> those<03:09:40.080> high<03:09:40.319> power<03:09:40.500> devices<03:09:41.040> and<03:09:41.640> then<03:09:41.700> we 03:09:41.809 --> 03:09:41.819 align:start position:0% of those high power devices and then we 03:09:41.819 --> 03:09:43.130 align:start position:0% of those high power devices and then we looked<03:09:42.060> at<03:09:42.180> some<03:09:42.359> noise<03:09:42.540> control<03:09:42.840> and 03:09:43.130 --> 03:09:43.140 align:start position:0% looked at some noise control and 03:09:43.140 --> 03:09:45.290 align:start position:0% looked at some noise control and reduction<03:09:43.500> techniques<03:09:44.100> including<03:09:44.819> proper 03:09:45.290 --> 03:09:45.300 align:start position:0% reduction techniques including proper 03:09:45.300 --> 03:09:47.929 align:start position:0% reduction techniques including proper grounding<03:09:45.840> and 03:09:47.929 --> 03:09:47.939 align:start position:0% grounding and 03:09:47.939 --> 03:09:54.960 align:start position:0% grounding and shielding 03:09:54.960 --> 03:09:54.970 align:start position:0% 03:09:54.970 --> 03:10:11.809 align:start position:0% [Music] 03:10:11.809 --> 03:10:11.819 align:start position:0% 03:10:11.819 --> 03:10:15.290 align:start position:0% so<03:10:12.359> welcome<03:10:12.720> to<03:10:13.020> module<03:10:13.620> 2<03:10:13.740> lesson<03:10:14.220> 4<03:10:14.460> new 03:10:15.290 --> 03:10:15.300 align:start position:0% so welcome to module 2 lesson 4 new 03:10:15.300 --> 03:10:20.150 align:start position:0% so welcome to module 2 lesson 4 new topic<03:10:15.720> added<03:10:16.200> to<03:10:16.439> the<03:10:16.939> CompTIA<03:10:17.939> syllabus<03:10:18.479> the 03:10:20.150 --> 03:10:20.160 align:start position:0% topic added to the CompTIA syllabus the 03:10:20.160 --> 03:10:22.490 align:start position:0% topic added to the CompTIA syllabus the um what<03:10:20.640> is<03:10:20.819> the<03:10:20.939> syllabus<03:10:21.300> number<03:10:21.540> the<03:10:22.080> below 03:10:22.490 --> 03:10:22.500 align:start position:0% um what is the syllabus number the below 03:10:22.500 --> 03:10:25.550 align:start position:0% um what is the syllabus number the below seven 03:10:25.550 --> 03:10:25.560 align:start position:0% 03:10:25.560 --> 03:10:27.410 align:start position:0% um Advanced<03:10:26.220> networking<03:10:26.700> devices<03:10:26.939> so<03:10:27.240> this 03:10:27.410 --> 03:10:27.420 align:start position:0% um Advanced networking devices so this 03:10:27.420 --> 03:10:29.269 align:start position:0% um Advanced networking devices so this is<03:10:27.540> stuff<03:10:27.779> that<03:10:28.020> we<03:10:28.140> need<03:10:28.319> to<03:10:28.439> be<03:10:28.620> aware<03:10:29.100> of 03:10:29.269 --> 03:10:29.279 align:start position:0% is stuff that we need to be aware of 03:10:29.279 --> 03:10:31.790 align:start position:0% is stuff that we need to be aware of because<03:10:29.640> it<03:10:30.180> becomes<03:10:30.779> a<03:10:30.899> prominence<03:10:31.319> may<03:10:31.620> have 03:10:31.790 --> 03:10:31.800 align:start position:0% because it becomes a prominence may have 03:10:31.800 --> 03:10:35.389 align:start position:0% because it becomes a prominence may have been<03:10:31.859> in<03:10:32.760> the<03:10:32.939> industry<03:10:33.180> a<03:10:33.359> while<03:10:33.600> but 03:10:35.389 --> 03:10:35.399 align:start position:0% been in the industry a while but 03:10:35.399 --> 03:10:38.870 align:start position:0% been in the industry a while but um now<03:10:35.880> in<03:10:36.180> regular<03:10:36.600> use<03:10:36.840> or<03:10:37.560> big<03:10:38.040> ubiquitous 03:10:38.870 --> 03:10:38.880 align:start position:0% um now in regular use or big ubiquitous 03:10:38.880 --> 03:10:40.550 align:start position:0% um now in regular use or big ubiquitous as<03:10:39.180> they<03:10:39.359> say 03:10:40.550 --> 03:10:40.560 align:start position:0% as they say 03:10:40.560 --> 03:10:42.590 align:start position:0% as they say so<03:10:40.859> Advanced<03:10:41.460> networking<03:10:41.880> devices<03:10:42.120> Network 03:10:42.590 --> 03:10:42.600 align:start position:0% so Advanced networking devices Network 03:10:42.600 --> 03:10:44.269 align:start position:0% so Advanced networking devices Network Hardware<03:10:42.899> media<03:10:43.560> I'm<03:10:43.800> going<03:10:43.979> to<03:10:44.100> look<03:10:44.160> at 03:10:44.269 --> 03:10:44.279 align:start position:0% Hardware media I'm going to look at 03:10:44.279 --> 03:10:46.070 align:start position:0% Hardware media I'm going to look at multi-layer<03:10:44.880> switches 03:10:46.070 --> 03:10:46.080 align:start position:0% multi-layer switches 03:10:46.080 --> 03:10:49.490 align:start position:0% multi-layer switches wireless<03:10:46.620> controllers<03:10:47.399> a<03:10:47.939> load<03:10:48.240> balancer 03:10:49.490 --> 03:10:49.500 align:start position:0% wireless controllers a load balancer 03:10:49.500 --> 03:10:52.969 align:start position:0% wireless controllers a load balancer IDs<03:10:50.399> and<03:10:50.520> IPS 03:10:52.969 --> 03:10:52.979 align:start position:0% 03:10:52.979 --> 03:10:55.190 align:start position:0% we're<03:10:53.760> going<03:10:53.939> to<03:10:54.000> look<03:10:54.120> at<03:10:54.300> AAA<03:10:54.660> and<03:10:55.020> radio 03:10:55.190 --> 03:10:55.200 align:start position:0% we're going to look at AAA and radio 03:10:55.200 --> 03:10:57.410 align:start position:0% we're going to look at AAA and radio server<03:10:55.740> I<03:10:55.920> think<03:10:56.040> that's<03:10:56.399> dotted<03:10:56.939> throughout 03:10:57.410 --> 03:10:57.420 align:start position:0% server I think that's dotted throughout 03:10:57.420 --> 03:11:01.190 align:start position:0% server I think that's dotted throughout the<03:10:58.100> syllabus<03:10:59.100> so<03:10:59.279> we<03:10:59.399> pick<03:10:59.640> it<03:10:59.819> up<03:11:00.000> as<03:11:00.600> a 03:11:01.190 --> 03:11:01.200 align:start position:0% the syllabus so we pick it up as a 03:11:01.200 --> 03:11:03.110 align:start position:0% the syllabus so we pick it up as a security<03:11:01.500> subject<03:11:02.100> and<03:11:02.340> also<03:11:02.580> an<03:11:02.760> advanced 03:11:03.110 --> 03:11:03.120 align:start position:0% security subject and also an advanced 03:11:03.120 --> 03:11:05.150 align:start position:0% security subject and also an advanced networking<03:11:03.660> device 03:11:05.150 --> 03:11:05.160 align:start position:0% networking device 03:11:05.160 --> 03:11:10.309 align:start position:0% networking device uh<03:11:05.880> UTM<03:11:06.620> Next<03:11:07.620> Generation<03:11:08.100> firewalls<03:11:09.420> Veep 03:11:10.309 --> 03:11:10.319 align:start position:0% uh UTM Next Generation firewalls Veep 03:11:10.319 --> 03:11:14.330 align:start position:0% uh UTM Next Generation firewalls Veep Gateway<03:11:11.060> and<03:11:12.060> in<03:11:12.240> terms<03:11:12.479> of<03:11:12.540> PBX<03:11:13.020> that<03:11:13.260> is<03:11:13.439> uh 03:11:14.330 --> 03:11:14.340 align:start position:0% Gateway and in terms of PBX that is uh 03:11:14.340 --> 03:11:17.690 align:start position:0% Gateway and in terms of PBX that is uh content<03:11:14.700> filter<03:11:15.140> so<03:11:16.140> this<03:11:16.500> is<03:11:16.979> one<03:11:17.220> of<03:11:17.399> the<03:11:17.460> I 03:11:17.690 --> 03:11:17.700 align:start position:0% content filter so this is one of the I 03:11:17.700 --> 03:11:18.889 align:start position:0% content filter so this is one of the I think<03:11:17.819> it's<03:11:17.939> the<03:11:18.120> first<03:11:18.300> device<03:11:18.600> actually 03:11:18.889 --> 03:11:18.899 align:start position:0% think it's the first device actually 03:11:18.899 --> 03:11:20.870 align:start position:0% think it's the first device actually that<03:11:19.260> Cisco<03:11:19.680> ever 03:11:20.870 --> 03:11:20.880 align:start position:0% that Cisco ever 03:11:20.880 --> 03:11:24.290 align:start position:0% that Cisco ever um<03:11:20.939> brought<03:11:21.180> to<03:11:21.420> Market<03:11:21.800> is<03:11:22.800> known<03:11:22.979> as<03:11:23.220> the 03:11:24.290 --> 03:11:24.300 align:start position:0% um brought to Market is known as the 03:11:24.300 --> 03:11:26.809 align:start position:0% um brought to Market is known as the um<03:11:24.359> the<03:11:24.779> Cisco<03:11:25.140> pretty<03:11:25.500> hard<03:11:25.800> to<03:11:26.040> see<03:11:26.160> there<03:11:26.399> it 03:11:26.809 --> 03:11:26.819 align:start position:0% um the Cisco pretty hard to see there it 03:11:26.819 --> 03:11:30.590 align:start position:0% um the Cisco pretty hard to see there it was<03:11:27.000> the<03:11:27.240> AGS<03:11:28.040> uh<03:11:29.040> husband<03:11:29.220> and<03:11:29.520> wife<03:11:29.760> uh<03:11:30.359> first 03:11:30.590 --> 03:11:30.600 align:start position:0% was the AGS uh husband and wife uh first 03:11:30.600 --> 03:11:32.030 align:start position:0% was the AGS uh husband and wife uh first artist<03:11:30.899> Cisco<03:11:31.319> and<03:11:31.439> I<03:11:31.560> think<03:11:31.680> they<03:11:31.740> had<03:11:31.920> a 03:11:32.030 --> 03:11:32.040 align:start position:0% artist Cisco and I think they had a 03:11:32.040 --> 03:11:33.889 align:start position:0% artist Cisco and I think they had a colleague<03:11:32.340> that<03:11:33.000> they<03:11:33.180> used<03:11:33.300> to<03:11:33.479> work<03:11:33.660> with 03:11:33.889 --> 03:11:33.899 align:start position:0% colleague that they used to work with 03:11:33.899 --> 03:11:35.450 align:start position:0% colleague that they used to work with and 03:11:35.450 --> 03:11:35.460 align:start position:0% and 03:11:35.460 --> 03:11:36.650 align:start position:0% and um 03:11:36.650 --> 03:11:36.660 align:start position:0% um 03:11:36.660 --> 03:11:38.929 align:start position:0% um they<03:11:37.439> actually<03:11:37.620> bought 03:11:38.929 --> 03:11:38.939 align:start position:0% they actually bought 03:11:38.939 --> 03:11:40.969 align:start position:0% they actually bought um<03:11:39.000> the<03:11:39.240> first<03:11:39.359> Cisco<03:11:39.960> switch<03:11:40.439> was<03:11:40.740> actually 03:11:40.969 --> 03:11:40.979 align:start position:0% um the first Cisco switch was actually 03:11:40.979 --> 03:11:44.269 align:start position:0% um the first Cisco switch was actually created<03:11:41.399> by<03:11:41.700> a<03:11:41.819> company<03:11:41.939> called<03:11:42.300> a<03:11:43.260> kaplana<03:11:43.979> or 03:11:44.269 --> 03:11:44.279 align:start position:0% created by a company called a kaplana or 03:11:44.279 --> 03:11:47.090 align:start position:0% created by a company called a kaplana or kalpana<03:11:44.880> if<03:11:45.479> you<03:11:45.660> pronounce<03:11:46.020> it<03:11:46.260> this<03:11:46.920> was 03:11:47.090 --> 03:11:47.100 align:start position:0% kalpana if you pronounce it this was 03:11:47.100 --> 03:11:49.309 align:start position:0% kalpana if you pronounce it this was their<03:11:47.279> very<03:11:47.520> first<03:11:47.700> ever<03:11:47.880> switch<03:11:48.300> and<03:11:49.319> um 03:11:49.309 --> 03:11:49.319 align:start position:0% their very first ever switch and um 03:11:49.319 --> 03:11:52.849 align:start position:0% their very first ever switch and um switches<03:11:49.920> used<03:11:50.100> to<03:11:50.279> run<03:11:50.399> some<03:11:50.819> old<03:11:51.260> uh<03:11:52.260> code<03:11:52.500> I 03:11:52.849 --> 03:11:52.859 align:start position:0% switches used to run some old uh code I 03:11:52.859 --> 03:11:54.889 align:start position:0% switches used to run some old uh code I think<03:11:53.160> something<03:11:53.399> like<03:11:54.120> um 03:11:54.889 --> 03:11:54.899 align:start position:0% think something like um 03:11:54.899 --> 03:11:57.170 align:start position:0% think something like um I<03:11:55.140> think<03:11:55.200> we<03:11:55.380> used<03:11:55.500> to<03:11:55.620> call<03:11:55.800> it 03:11:57.170 --> 03:11:57.180 align:start position:0% I think we used to call it 03:11:57.180 --> 03:12:01.130 align:start position:0% I think we used to call it katos<03:11:58.020> and<03:11:58.920> then<03:11:59.040> the<03:11:59.340> routers<03:11:59.960> well<03:12:00.960> there 03:12:01.130 --> 03:12:01.140 align:start position:0% katos and then the routers well there 03:12:01.140 --> 03:12:02.330 align:start position:0% katos and then the routers well there was<03:12:01.260> no<03:12:01.439> code 03:12:02.330 --> 03:12:02.340 align:start position:0% was no code 03:12:02.340 --> 03:12:03.950 align:start position:0% was no code um<03:12:02.460> that<03:12:02.760> they<03:12:03.000> because<03:12:03.180> they<03:12:03.479> created<03:12:03.779> it 03:12:03.950 --> 03:12:03.960 align:start position:0% um that they because they created it 03:12:03.960 --> 03:12:06.050 align:start position:0% um that they because they created it they<03:12:04.140> created<03:12:04.439> their<03:12:04.680> own<03:12:04.800> code 03:12:06.050 --> 03:12:06.060 align:start position:0% they created their own code 03:12:06.060 --> 03:12:08.450 align:start position:0% they created their own code and<03:12:06.899> that's<03:12:07.380> called<03:12:07.620> the<03:12:07.859> internet<03:12:07.979> work 03:12:08.450 --> 03:12:08.460 align:start position:0% and that's called the internet work 03:12:08.460 --> 03:12:10.730 align:start position:0% and that's called the internet work operating<03:12:09.000> system<03:12:09.300> Cisco<03:12:10.140> brought<03:12:10.500> the<03:12:10.620> whole 03:12:10.730 --> 03:12:10.740 align:start position:0% operating system Cisco brought the whole 03:12:10.740 --> 03:12:12.230 align:start position:0% operating system Cisco brought the whole thing<03:12:10.920> together<03:12:11.100> now<03:12:11.399> so<03:12:11.640> there's<03:12:11.819> this<03:12:12.000> you 03:12:12.230 --> 03:12:12.240 align:start position:0% thing together now so there's this you 03:12:12.240 --> 03:12:14.570 align:start position:0% thing together now so there's this you don't<03:12:12.300> have<03:12:12.420> to<03:12:12.540> use<03:12:12.660> the<03:12:12.960> old<03:12:13.460> command<03:12:14.460> line 03:12:14.570 --> 03:12:14.580 align:start position:0% don't have to use the old command line 03:12:14.580 --> 03:12:16.670 align:start position:0% don't have to use the old command line that<03:12:14.880> work<03:12:15.300> for<03:12:15.479> katos<03:12:15.840> but<03:12:16.080> they<03:12:16.260> they<03:12:16.380> just 03:12:16.670 --> 03:12:16.680 align:start position:0% that work for katos but they they just 03:12:16.680 --> 03:12:18.590 align:start position:0% that work for katos but they they just weren't<03:12:16.920> compatible<03:12:17.460> at<03:12:17.760> all 03:12:18.590 --> 03:12:18.600 align:start position:0% weren't compatible at all 03:12:18.600 --> 03:12:20.210 align:start position:0% weren't compatible at all so<03:12:19.140> you<03:12:19.319> had<03:12:19.439> to<03:12:19.560> kind<03:12:19.680> of<03:12:19.800> learn<03:12:19.920> how<03:12:20.100> to 03:12:20.210 --> 03:12:20.220 align:start position:0% so you had to kind of learn how to 03:12:20.220 --> 03:12:22.670 align:start position:0% so you had to kind of learn how to program<03:12:20.399> two<03:12:20.880> different<03:12:21.060> type<03:12:21.359> of<03:12:21.540> devices 03:12:22.670 --> 03:12:22.680 align:start position:0% program two different type of devices 03:12:22.680 --> 03:12:24.889 align:start position:0% program two different type of devices so<03:12:23.160> this<03:12:23.340> was<03:12:23.520> the<03:12:23.880> early<03:12:24.120> I<03:12:24.540> think<03:12:24.660> this<03:12:24.779> is 03:12:24.889 --> 03:12:24.899 align:start position:0% so this was the early I think this is 03:12:24.899 --> 03:12:28.010 align:start position:0% so this was the early I think this is from<03:12:25.080> The<03:12:25.200> Cisco<03:12:25.560> Museum<03:12:25.859> actually<03:12:26.399> and 03:12:28.010 --> 03:12:28.020 align:start position:0% from The Cisco Museum actually and 03:12:28.020 --> 03:12:30.590 align:start position:0% from The Cisco Museum actually and um you<03:12:28.319> can<03:12:28.500> see<03:12:28.800> the<03:12:29.340> Cabana<03:12:29.819> switch<03:12:30.120> up<03:12:30.359> here 03:12:30.590 --> 03:12:30.600 align:start position:0% um you can see the Cabana switch up here 03:12:30.600 --> 03:12:35.030 align:start position:0% um you can see the Cabana switch up here so<03:12:31.319> a<03:12:31.500> real<03:12:31.680> old-fashioned<03:12:32.340> connectors<03:12:32.880> uh 03:12:35.030 --> 03:12:35.040 align:start position:0% so a real old-fashioned connectors uh 03:12:35.040 --> 03:12:37.670 align:start position:0% so a real old-fashioned connectors uh maybe<03:12:35.399> the<03:12:35.660> db25s<03:12:36.660> you<03:12:36.899> can<03:12:37.080> see<03:12:37.200> there's<03:12:37.439> no 03:12:37.670 --> 03:12:37.680 align:start position:0% maybe the db25s you can see there's no 03:12:37.680 --> 03:12:39.950 align:start position:0% maybe the db25s you can see there's no high<03:12:37.979> speed<03:12:38.220> connections<03:12:38.819> here<03:12:39.060> massive 03:12:39.950 --> 03:12:39.960 align:start position:0% high speed connections here massive 03:12:39.960 --> 03:12:42.650 align:start position:0% high speed connections here massive switch<03:12:40.260> and<03:12:41.040> then<03:12:41.220> your<03:12:41.520> power<03:12:42.060> connector 03:12:42.650 --> 03:12:42.660 align:start position:0% switch and then your power connector 03:12:42.660 --> 03:12:45.410 align:start position:0% switch and then your power connector yeah<03:12:43.040> so<03:12:44.040> I'm<03:12:44.340> sure<03:12:44.520> this<03:12:44.700> is<03:12:44.819> Cutting<03:12:45.240> Edge 03:12:45.410 --> 03:12:45.420 align:start position:0% yeah so I'm sure this is Cutting Edge 03:12:45.420 --> 03:12:48.170 align:start position:0% yeah so I'm sure this is Cutting Edge when<03:12:45.660> it<03:12:45.840> first<03:12:46.020> came<03:12:46.260> out<03:12:46.500> huge<03:12:47.220> thing<03:12:47.460> in<03:12:48.120> the 03:12:48.170 --> 03:12:48.180 align:start position:0% when it first came out huge thing in the 03:12:48.180 --> 03:12:51.290 align:start position:0% when it first came out huge thing in the 1990s<03:12:49.080> but<03:12:49.920> when<03:12:50.160> you're<03:12:50.300> supporting 03:12:51.290 --> 03:12:51.300 align:start position:0% 1990s but when you're supporting 03:12:51.300 --> 03:12:53.630 align:start position:0% 1990s but when you're supporting networks<03:12:51.840> back<03:12:52.140> then 03:12:53.630 --> 03:12:53.640 align:start position:0% networks back then 03:12:53.640 --> 03:12:55.910 align:start position:0% networks back then really<03:12:54.779> um<03:12:54.779> there<03:12:55.020> wasn't<03:12:55.140> an<03:12:55.380> awful<03:12:55.620> lot<03:12:55.740> to 03:12:55.910 --> 03:12:55.920 align:start position:0% really um there wasn't an awful lot to 03:12:55.920 --> 03:12:59.630 align:start position:0% really um there wasn't an awful lot to it<03:12:56.160> a<03:12:56.700> server<03:12:57.120> router<03:12:57.859> a<03:12:58.859> hub<03:12:59.160> there<03:12:59.460> wasn't 03:12:59.630 --> 03:12:59.640 align:start position:0% it a server router a hub there wasn't 03:12:59.640 --> 03:13:01.130 align:start position:0% it a server router a hub there wasn't that<03:12:59.819> much<03:13:00.000> traffic<03:13:00.300> because<03:13:00.840> people 03:13:01.130 --> 03:13:01.140 align:start position:0% that much traffic because people 03:13:01.140 --> 03:13:03.410 align:start position:0% that much traffic because people couldn't<03:13:01.260> afford<03:13:01.560> the<03:13:01.740> kit<03:13:01.920> anyway 03:13:03.410 --> 03:13:03.420 align:start position:0% couldn't afford the kit anyway 03:13:03.420 --> 03:13:06.469 align:start position:0% couldn't afford the kit anyway um early<03:13:03.720> 90s<03:13:04.200> the<03:13:04.500> web<03:13:04.680> was<03:13:05.240> invented<03:13:06.240> I'm 03:13:06.469 --> 03:13:06.479 align:start position:0% um early 90s the web was invented I'm 03:13:06.479 --> 03:13:07.969 align:start position:0% um early 90s the web was invented I'm sure<03:13:06.660> most<03:13:06.840> people<03:13:07.020> weren't<03:13:07.319> really<03:13:07.439> using<03:13:07.859> it 03:13:07.969 --> 03:13:07.979 align:start position:0% sure most people weren't really using it 03:13:07.979 --> 03:13:10.550 align:start position:0% sure most people weren't really using it ethernet<03:13:08.939> was<03:13:09.300> running<03:13:09.420> at<03:13:09.720> 10<03:13:09.960> Meg<03:13:10.319> half 03:13:10.550 --> 03:13:10.560 align:start position:0% ethernet was running at 10 Meg half 03:13:10.560 --> 03:13:12.469 align:start position:0% ethernet was running at 10 Meg half duplex 03:13:12.469 --> 03:13:12.479 align:start position:0% duplex 03:13:12.479 --> 03:13:16.849 align:start position:0% duplex a<03:13:12.899> Cisco<03:13:13.439> the<03:13:14.279> early<03:13:14.460> 90s<03:13:15.060> had<03:13:15.420> 251<03:13:16.260> employees 03:13:16.849 --> 03:13:16.859 align:start position:0% a Cisco the early 90s had 251 employees 03:13:16.859 --> 03:13:18.650 align:start position:0% a Cisco the early 90s had 251 employees obviously<03:13:17.340> there<03:13:17.580> were<03:13:17.700> just<03:13:17.880> I<03:13:18.300> think<03:13:18.359> three 03:13:18.650 --> 03:13:18.660 align:start position:0% obviously there were just I think three 03:13:18.660 --> 03:13:22.790 align:start position:0% obviously there were just I think three people<03:13:18.899> to<03:13:19.200> start<03:13:19.500> and<03:13:20.220> they<03:13:20.460> grew<03:13:20.939> to<03:13:21.060> 251. 03:13:22.790 --> 03:13:22.800 align:start position:0% people to start and they grew to 251. 03:13:22.800 --> 03:13:25.929 align:start position:0% people to start and they grew to 251. and<03:13:23.460> then<03:13:23.640> scroll<03:13:24.120> forwards<03:13:24.720> to<03:13:24.899> the<03:13:25.260> current 03:13:25.929 --> 03:13:25.939 align:start position:0% and then scroll forwards to the current 03:13:25.939 --> 03:13:28.790 align:start position:0% and then scroll forwards to the current ERA<03:13:26.939> and<03:13:27.120> you<03:13:27.300> can<03:13:27.420> see<03:13:27.600> obviously<03:13:28.080> things<03:13:28.380> are 03:13:28.790 --> 03:13:28.800 align:start position:0% ERA and you can see obviously things are 03:13:28.800 --> 03:13:31.370 align:start position:0% ERA and you can see obviously things are a<03:13:29.279> lot<03:13:29.399> more<03:13:29.580> complicated 03:13:31.370 --> 03:13:31.380 align:start position:0% a lot more complicated 03:13:31.380 --> 03:13:34.490 align:start position:0% a lot more complicated we<03:13:31.920> have<03:13:32.220> a<03:13:32.460> multi-lay<03:13:33.180> devices<03:13:33.660> working<03:13:34.080> at 03:13:34.490 --> 03:13:34.500 align:start position:0% we have a multi-lay devices working at 03:13:34.500 --> 03:13:37.250 align:start position:0% we have a multi-lay devices working at seven<03:13:34.920> different<03:13:35.220> layers<03:13:35.640> of<03:13:35.819> the<03:13:35.880> OSI<03:13:36.359> model 03:13:37.250 --> 03:13:37.260 align:start position:0% seven different layers of the OSI model 03:13:37.260 --> 03:13:40.730 align:start position:0% seven different layers of the OSI model incorporate<03:13:38.160> Wireless<03:13:38.399> into<03:13:38.819> our<03:13:39.120> Networks 03:13:40.730 --> 03:13:40.740 align:start position:0% incorporate Wireless into our Networks 03:13:40.740 --> 03:13:42.889 align:start position:0% incorporate Wireless into our Networks recover<03:13:41.340> Wireless<03:13:41.640> later 03:13:42.889 --> 03:13:42.899 align:start position:0% recover Wireless later 03:13:42.899 --> 03:13:44.750 align:start position:0% recover Wireless later there<03:13:43.439> isn't<03:13:43.740> anywhere<03:13:44.100> you<03:13:44.220> go<03:13:44.399> now<03:13:44.520> really 03:13:44.750 --> 03:13:44.760 align:start position:0% there isn't anywhere you go now really 03:13:44.760 --> 03:13:46.130 align:start position:0% there isn't anywhere you go now really where<03:13:44.939> there<03:13:45.060> isn't<03:13:45.300> somebody<03:13:45.420> offering<03:13:45.960> some 03:13:46.130 --> 03:13:46.140 align:start position:0% where there isn't somebody offering some 03:13:46.140 --> 03:13:48.349 align:start position:0% where there isn't somebody offering some sort<03:13:46.319> of<03:13:46.380> wireless<03:13:46.500> connection 03:13:48.349 --> 03:13:48.359 align:start position:0% sort of wireless connection 03:13:48.359 --> 03:13:50.929 align:start position:0% sort of wireless connection virtualization<03:13:49.260> is<03:13:49.560> a<03:13:49.740> Hot<03:13:49.920> Topic 03:13:50.929 --> 03:13:50.939 align:start position:0% virtualization is a Hot Topic 03:13:50.939 --> 03:13:53.269 align:start position:0% virtualization is a Hot Topic and<03:13:51.359> it's<03:13:51.540> obviously<03:13:51.899> used<03:13:52.319> by<03:13:52.740> pretty<03:13:53.160> much 03:13:53.269 --> 03:13:53.279 align:start position:0% and it's obviously used by pretty much 03:13:53.279 --> 03:13:56.650 align:start position:0% and it's obviously used by pretty much all<03:13:53.460> of<03:13:53.640> the<03:13:53.760> cloud<03:13:54.380> providers<03:13:55.380> Amazon<03:13:55.800> Google 03:13:56.650 --> 03:13:56.660 align:start position:0% all of the cloud providers Amazon Google 03:13:56.660 --> 03:14:00.170 align:start position:0% all of the cloud providers Amazon Google and<03:13:57.660> Microsoft<03:13:58.439> to 03:14:00.170 --> 03:14:00.180 align:start position:0% and Microsoft to 03:14:00.180 --> 03:14:03.290 align:start position:0% and Microsoft to um<03:14:00.240> cut<03:14:00.600> costs<03:14:01.020> and<03:14:01.140> improve<03:14:01.439> performance 03:14:03.290 --> 03:14:03.300 align:start position:0% um cut costs and improve performance 03:14:03.300 --> 03:14:05.870 align:start position:0% um cut costs and improve performance cloud<03:14:03.840> computing<03:14:04.439> is<03:14:04.740> a<03:14:04.920> red<03:14:05.040> hot<03:14:05.220> topic<03:14:05.640> that 03:14:05.870 --> 03:14:05.880 align:start position:0% cloud computing is a red hot topic that 03:14:05.880 --> 03:14:08.090 align:start position:0% cloud computing is a red hot topic that I<03:14:06.060> encourage<03:14:06.300> everyone<03:14:06.479> to<03:14:06.840> learn<03:14:07.100> video 03:14:08.090 --> 03:14:08.100 align:start position:0% I encourage everyone to learn video 03:14:08.100 --> 03:14:11.510 align:start position:0% I encourage everyone to learn video voice<03:14:08.520> over<03:14:08.819> IP<03:14:09.359> and<03:14:09.720> quality<03:14:10.020> of<03:14:10.260> service<03:14:10.520> you 03:14:11.510 --> 03:14:11.520 align:start position:0% voice over IP and quality of service you 03:14:11.520 --> 03:14:13.130 align:start position:0% voice over IP and quality of service you need<03:14:11.640> to<03:14:11.760> be<03:14:12.120> aware<03:14:12.420> of<03:14:12.540> advanced<03:14:13.020> security 03:14:13.130 --> 03:14:13.140 align:start position:0% need to be aware of advanced security 03:14:13.140 --> 03:14:15.590 align:start position:0% need to be aware of advanced security threats<03:14:13.800> and<03:14:13.979> obviously<03:14:14.399> the<03:14:15.180> larger<03:14:15.479> the 03:14:15.590 --> 03:14:15.600 align:start position:0% threats and obviously the larger the 03:14:15.600 --> 03:14:16.849 align:start position:0% threats and obviously the larger the network<03:14:15.779> now<03:14:16.080> they'll<03:14:16.380> have<03:14:16.560> their<03:14:16.740> own 03:14:16.849 --> 03:14:16.859 align:start position:0% network now they'll have their own 03:14:16.859 --> 03:14:19.550 align:start position:0% network now they'll have their own dedicated<03:14:17.340> security<03:14:17.700> team<03:14:18.260> for<03:14:19.260> Hardware 03:14:19.550 --> 03:14:19.560 align:start position:0% dedicated security team for Hardware 03:14:19.560 --> 03:14:21.530 align:start position:0% dedicated security team for Hardware software<03:14:20.279> and 03:14:21.530 --> 03:14:21.540 align:start position:0% software and 03:14:21.540 --> 03:14:22.750 align:start position:0% software and um 03:14:22.750 --> 03:14:22.760 align:start position:0% um 03:14:22.760 --> 03:14:25.190 align:start position:0% um protecting<03:14:23.760> from<03:14:24.000> employees<03:14:24.540> and<03:14:24.899> that<03:14:25.020> kind 03:14:25.190 --> 03:14:25.200 align:start position:0% protecting from employees and that kind 03:14:25.200 --> 03:14:29.090 align:start position:0% protecting from employees and that kind of<03:14:25.319> thing<03:14:25.819> Cisco<03:14:26.819> currently<03:14:27.779> has<03:14:28.080> 72<03:14:28.979> 000 03:14:29.090 --> 03:14:29.100 align:start position:0% of thing Cisco currently has 72 000 03:14:29.100 --> 03:14:31.610 align:start position:0% of thing Cisco currently has 72 000 employees<03:14:29.640> I<03:14:30.540> know<03:14:30.720> when<03:14:30.899> I<03:14:31.080> worked<03:14:31.500> there 03:14:31.610 --> 03:14:31.620 align:start position:0% employees I know when I worked there 03:14:31.620 --> 03:14:34.010 align:start position:0% employees I know when I worked there when<03:14:32.460> was<03:14:32.640> it<03:14:32.760> the<03:14:32.880> early<03:14:33.000> 90s<03:14:33.479> they<03:14:33.840> were 03:14:34.010 --> 03:14:34.020 align:start position:0% when was it the early 90s they were 03:14:34.020 --> 03:14:36.530 align:start position:0% when was it the early 90s they were getting<03:14:34.920> rid<03:14:35.160> of<03:14:35.340> slaves<03:14:36.060> of<03:14:36.300> different 03:14:36.530 --> 03:14:36.540 align:start position:0% getting rid of slaves of different 03:14:36.540 --> 03:14:38.510 align:start position:0% getting rid of slaves of different employees<03:14:37.080> from<03:14:37.439> the<03:14:37.560> legal<03:14:37.920> team<03:14:38.160> and 03:14:38.510 --> 03:14:38.520 align:start position:0% employees from the legal team and 03:14:38.520 --> 03:14:40.370 align:start position:0% employees from the legal team and marketing<03:14:39.000> teams<03:14:39.359> and<03:14:39.540> some<03:14:39.720> Engineers<03:14:40.140> as 03:14:40.370 --> 03:14:40.380 align:start position:0% marketing teams and some Engineers as 03:14:40.380 --> 03:14:42.050 align:start position:0% marketing teams and some Engineers as well<03:14:40.560> so<03:14:41.220> I'm<03:14:41.279> not<03:14:41.460> sure<03:14:41.580> if<03:14:41.640> it<03:14:41.819> was<03:14:41.880> ever 03:14:42.050 --> 03:14:42.060 align:start position:0% well so I'm not sure if it was ever 03:14:42.060 --> 03:14:44.929 align:start position:0% well so I'm not sure if it was ever higher<03:14:42.420> than<03:14:42.600> that<03:14:42.779> but<03:14:43.740> as<03:14:44.220> stated<03:14:44.520> on<03:14:44.760> the 03:14:44.929 --> 03:14:44.939 align:start position:0% higher than that but as stated on the 03:14:44.939 --> 03:14:47.809 align:start position:0% higher than that but as stated on the interweb<03:14:45.540> it's<03:14:45.779> 72<03:14:46.740> 000.<03:14:47.040> this<03:14:47.340> is<03:14:47.460> quite<03:14:47.700> a 03:14:47.809 --> 03:14:47.819 align:start position:0% interweb it's 72 000. this is quite a 03:14:47.819 --> 03:14:49.429 align:start position:0% interweb it's 72 000. this is quite a lot 03:14:49.429 --> 03:14:49.439 align:start position:0% lot 03:14:49.439 --> 03:14:52.550 align:start position:0% lot so<03:14:49.979> what<03:14:50.160> are<03:14:50.340> the<03:14:50.460> devices<03:14:51.140> that's<03:14:52.140> mentioned 03:14:52.550 --> 03:14:52.560 align:start position:0% so what are the devices that's mentioned 03:14:52.560 --> 03:14:54.110 align:start position:0% so what are the devices that's mentioned now<03:14:52.740> brought<03:14:53.040> into<03:14:53.160> the<03:14:53.399> syllabus<03:14:53.819> is<03:14:54.000> the 03:14:54.110 --> 03:14:54.120 align:start position:0% now brought into the syllabus is the 03:14:54.120 --> 03:14:55.450 align:start position:0% now brought into the syllabus is the multi-layer<03:14:54.660> switch 03:14:55.450 --> 03:14:55.460 align:start position:0% multi-layer switch 03:14:55.460 --> 03:14:58.429 align:start position:0% multi-layer switch switch<03:14:56.460> is<03:14:56.819> generally<03:14:57.240> a<03:14:57.779> layer<03:14:58.080> two<03:14:58.200> switch 03:14:58.429 --> 03:14:58.439 align:start position:0% switch is generally a layer two switch 03:14:58.439 --> 03:15:00.230 align:start position:0% switch is generally a layer two switch is<03:14:58.680> which<03:14:58.920> is<03:14:59.040> the<03:14:59.220> cheaper<03:14:59.520> models<03:14:59.939> will 03:15:00.230 --> 03:15:00.240 align:start position:0% is which is the cheaper models will 03:15:00.240 --> 03:15:03.410 align:start position:0% is which is the cheaper models will switch<03:15:00.840> frames<03:15:01.380> at<03:15:02.040> Layer<03:15:02.460> Two<03:15:02.640> and<03:15:03.180> they'll 03:15:03.410 --> 03:15:03.420 align:start position:0% switch frames at Layer Two and they'll 03:15:03.420 --> 03:15:05.570 align:start position:0% switch frames at Layer Two and they'll lay<03:15:03.600> they'll<03:15:03.960> use<03:15:04.080> hardware<03:15:04.319> for<03:15:04.800> this 03:15:05.570 --> 03:15:05.580 align:start position:0% lay they'll use hardware for this 03:15:05.580 --> 03:15:08.809 align:start position:0% lay they'll use hardware for this multi-layer<03:15:06.359> switches<03:15:06.779> operate<03:15:07.340> layers<03:15:08.340> two 03:15:08.809 --> 03:15:08.819 align:start position:0% multi-layer switches operate layers two 03:15:08.819 --> 03:15:10.309 align:start position:0% multi-layer switches operate layers two to<03:15:09.000> seven<03:15:09.180> you<03:15:09.359> can<03:15:09.479> buy<03:15:09.600> a<03:15:09.720> switch<03:15:09.899> operates 03:15:10.309 --> 03:15:10.319 align:start position:0% to seven you can buy a switch operates 03:15:10.319 --> 03:15:12.290 align:start position:0% to seven you can buy a switch operates at<03:15:10.500> layers<03:15:10.800> two<03:15:10.979> three<03:15:11.220> four<03:15:11.460> or<03:15:12.060> another 03:15:12.290 --> 03:15:12.300 align:start position:0% at layers two three four or another 03:15:12.300 --> 03:15:14.929 align:start position:0% at layers two three four or another switch<03:15:12.660> and<03:15:13.319> you<03:15:13.439> can<03:15:13.560> see<03:15:13.740> here 03:15:14.929 --> 03:15:14.939 align:start position:0% switch and you can see here 03:15:14.939 --> 03:15:17.389 align:start position:0% switch and you can see here I<03:15:15.420> might<03:15:15.600> be<03:15:15.840> clear<03:15:16.080> but<03:15:16.439> the<03:15:16.740> this<03:15:17.160> is 03:15:17.389 --> 03:15:17.399 align:start position:0% I might be clear but the this is 03:15:17.399 --> 03:15:20.210 align:start position:0% I might be clear but the this is actually<03:15:17.640> uh<03:15:18.540> a<03:15:18.899> connection<03:15:19.080> bracket<03:15:20.040> here 03:15:20.210 --> 03:15:20.220 align:start position:0% actually uh a connection bracket here 03:15:20.220 --> 03:15:22.969 align:start position:0% actually uh a connection bracket here and<03:15:21.120> what<03:15:21.300> happens<03:15:21.479> is<03:15:21.779> this<03:15:22.140> is<03:15:22.260> a<03:15:22.500> switch<03:15:22.680> in 03:15:22.969 --> 03:15:22.979 align:start position:0% and what happens is this is a switch in 03:15:22.979 --> 03:15:24.170 align:start position:0% and what happens is this is a switch in module 03:15:24.170 --> 03:15:24.180 align:start position:0% module 03:15:24.180 --> 03:15:27.230 align:start position:0% module that<03:15:24.899> you<03:15:25.200> can<03:15:25.380> buy<03:15:26.040> and<03:15:26.460> Slot<03:15:26.760> into<03:15:27.000> the 03:15:27.230 --> 03:15:27.240 align:start position:0% that you can buy and Slot into the 03:15:27.240 --> 03:15:29.570 align:start position:0% that you can buy and Slot into the chassis<03:15:27.660> so<03:15:28.500> what<03:15:28.680> you<03:15:28.800> could<03:15:28.979> have<03:15:29.160> there 03:15:29.570 --> 03:15:29.580 align:start position:0% chassis so what you could have there 03:15:29.580 --> 03:15:33.950 align:start position:0% chassis so what you could have there instead<03:15:30.439> is<03:15:31.439> uh<03:15:31.979> there's<03:15:32.399> two 03:15:33.950 --> 03:15:33.960 align:start position:0% instead is uh there's two 03:15:33.960 --> 03:15:36.290 align:start position:0% instead is uh there's two um modules<03:15:34.560> here<03:15:34.859> and<03:15:35.640> depending<03:15:36.000> on<03:15:36.060> what 03:15:36.290 --> 03:15:36.300 align:start position:0% um modules here and depending on what 03:15:36.300 --> 03:15:37.849 align:start position:0% um modules here and depending on what you<03:15:36.420> buy<03:15:36.660> you<03:15:36.960> could<03:15:37.020> have<03:15:37.200> one<03:15:37.380> here<03:15:37.620> for 03:15:37.849 --> 03:15:37.859 align:start position:0% you buy you could have one here for 03:15:37.859 --> 03:15:39.889 align:start position:0% you buy you could have one here for voice<03:15:38.100> one<03:15:38.460> here<03:15:38.640> for<03:15:38.819> remote<03:15:39.060> connections 03:15:39.889 --> 03:15:39.899 align:start position:0% voice one here for remote connections 03:15:39.899 --> 03:15:42.050 align:start position:0% voice one here for remote connections you<03:15:40.500> could<03:15:40.560> have<03:15:40.740> a<03:15:40.920> mini<03:15:41.040> switching<03:15:41.580> module 03:15:42.050 --> 03:15:42.060 align:start position:0% you could have a mini switching module 03:15:42.060 --> 03:15:44.450 align:start position:0% you could have a mini switching module here<03:15:42.359> or<03:15:43.020> one<03:15:43.200> that's<03:15:43.380> only<03:15:43.620> dedicated<03:15:44.160> for 03:15:44.450 --> 03:15:44.460 align:start position:0% here or one that's only dedicated for 03:15:44.460 --> 03:15:46.969 align:start position:0% here or one that's only dedicated for voice<03:15:44.819> connections<03:15:45.540> you<03:15:46.439> can<03:15:46.560> see<03:15:46.740> actually 03:15:46.969 --> 03:15:46.979 align:start position:0% voice connections you can see actually 03:15:46.979 --> 03:15:49.190 align:start position:0% voice connections you can see actually these<03:15:47.460> are<03:15:47.580> exactly<03:15:47.939> the<03:15:48.120> same<03:15:48.359> and<03:15:48.899> it<03:15:49.020> looks 03:15:49.190 --> 03:15:49.200 align:start position:0% these are exactly the same and it looks 03:15:49.200 --> 03:15:51.230 align:start position:0% these are exactly the same and it looks like<03:15:49.319> there's<03:15:49.500> USB<03:15:49.979> there<03:15:50.220> if<03:15:50.399> you<03:15:51.000> um<03:15:51.000> connect 03:15:51.230 --> 03:15:51.240 align:start position:0% like there's USB there if you um connect 03:15:51.240 --> 03:15:54.349 align:start position:0% like there's USB there if you um connect in<03:15:51.660> management<03:15:52.340> interfaces<03:15:53.340> a<03:15:54.000> console 03:15:54.349 --> 03:15:54.359 align:start position:0% in management interfaces a console 03:15:54.359 --> 03:15:55.610 align:start position:0% in management interfaces a console connection 03:15:55.610 --> 03:15:55.620 align:start position:0% connection 03:15:55.620 --> 03:15:59.809 align:start position:0% connection and<03:15:56.580> there's<03:15:56.819> what<03:15:57.060> there's<03:15:57.420> one<03:15:57.840> two<03:15:58.819> three 03:15:59.809 --> 03:15:59.819 align:start position:0% and there's what there's one two three 03:15:59.819 --> 03:16:02.510 align:start position:0% and there's what there's one two three four<03:16:00.180> switching<03:16:00.720> modules<03:16:01.080> here<03:16:01.439> and<03:16:02.100> it<03:16:02.279> looks 03:16:02.510 --> 03:16:02.520 align:start position:0% four switching modules here and it looks 03:16:02.520 --> 03:16:05.990 align:start position:0% four switching modules here and it looks like<03:16:02.640> it's<03:16:02.819> got<03:16:03.060> Quad<03:16:03.600> Power<03:16:04.260> as<03:16:04.800> well<03:16:04.979> so<03:16:05.640> if 03:16:05.990 --> 03:16:06.000 align:start position:0% like it's got Quad Power as well so if 03:16:06.000 --> 03:16:08.269 align:start position:0% like it's got Quad Power as well so if anything<03:16:06.180> goes<03:16:06.720> wrong<03:16:07.080> with<03:16:07.859> the<03:16:08.100> power 03:16:08.269 --> 03:16:08.279 align:start position:0% anything goes wrong with the power 03:16:08.279 --> 03:16:10.730 align:start position:0% anything goes wrong with the power supplies<03:16:08.819> you've<03:16:09.600> got 03:16:10.730 --> 03:16:10.740 align:start position:0% supplies you've got 03:16:10.740 --> 03:16:12.130 align:start position:0% supplies you've got three 03:16:12.130 --> 03:16:12.140 align:start position:0% three 03:16:12.140 --> 03:16:15.650 align:start position:0% three uh<03:16:13.140> possible<03:16:13.859> power<03:16:14.100> supplies<03:16:14.520> I'm<03:16:14.760> not<03:16:14.880> sure 03:16:15.650 --> 03:16:15.660 align:start position:0% uh possible power supplies I'm not sure 03:16:15.660 --> 03:16:16.790 align:start position:0% uh possible power supplies I'm not sure they're<03:16:16.140> probably<03:16:16.260> going<03:16:16.439> to<03:16:16.560> be<03:16:16.680> hot 03:16:16.790 --> 03:16:16.800 align:start position:0% they're probably going to be hot 03:16:16.800 --> 03:16:18.410 align:start position:0% they're probably going to be hot swappable<03:16:17.279> and<03:16:17.580> I'm<03:16:17.760> not<03:16:17.880> sure<03:16:18.060> if<03:16:18.240> they're 03:16:18.410 --> 03:16:18.420 align:start position:0% swappable and I'm not sure if they're 03:16:18.420 --> 03:16:19.429 align:start position:0% swappable and I'm not sure if they're working 03:16:19.429 --> 03:16:19.439 align:start position:0% working 03:16:19.439 --> 03:16:22.849 align:start position:0% working uh<03:16:20.279> there's<03:16:20.460> one's<03:16:20.880> a<03:16:21.000> backup<03:16:21.359> four<03:16:21.720> two<03:16:22.080> and 03:16:22.849 --> 03:16:22.859 align:start position:0% uh there's one's a backup four two and 03:16:22.859 --> 03:16:24.590 align:start position:0% uh there's one's a backup four two and um fours<03:16:23.399> are<03:16:23.520> back<03:16:23.580> up<03:16:23.760> for<03:16:23.939> three<03:16:24.120> and<03:16:24.359> vice 03:16:24.590 --> 03:16:24.600 align:start position:0% um fours are back up for three and vice 03:16:24.600 --> 03:16:26.030 align:start position:0% um fours are back up for three and vice versa<03:16:25.020> you<03:16:25.500> have<03:16:25.620> to<03:16:25.680> check<03:16:25.859> the 03:16:26.030 --> 03:16:26.040 align:start position:0% versa you have to check the 03:16:26.040 --> 03:16:28.490 align:start position:0% versa you have to check the documentation<03:16:26.580> but<03:16:27.479> this<03:16:27.660> whole<03:16:27.840> chassis 03:16:28.490 --> 03:16:28.500 align:start position:0% documentation but this whole chassis 03:16:28.500 --> 03:16:31.070 align:start position:0% documentation but this whole chassis would<03:16:28.680> obviously<03:16:28.920> be<03:16:29.040> connected<03:16:29.460> into<03:16:29.760> the 03:16:31.070 --> 03:16:31.080 align:start position:0% would obviously be connected into the 03:16:31.080 --> 03:16:33.650 align:start position:0% would obviously be connected into the cabinet<03:16:31.979> here<03:16:32.160> and<03:16:32.399> you<03:16:32.520> can<03:16:32.640> probably<03:16:32.880> have 03:16:33.650 --> 03:16:33.660 align:start position:0% cabinet here and you can probably have 03:16:33.660 --> 03:16:36.290 align:start position:0% cabinet here and you can probably have um one<03:16:34.319> major<03:16:34.560> switch<03:16:34.920> here<03:16:35.220> and<03:16:35.460> then<03:16:35.640> a 03:16:36.290 --> 03:16:36.300 align:start position:0% um one major switch here and then a 03:16:36.300 --> 03:16:39.170 align:start position:0% um one major switch here and then a second<03:16:36.600> one<03:16:36.840> to<03:16:37.020> take<03:16:37.200> up<03:16:37.620> um<03:16:37.620> the<03:16:38.040> whole<03:16:38.160> rack 03:16:39.170 --> 03:16:39.180 align:start position:0% second one to take up um the whole rack 03:16:39.180 --> 03:16:42.370 align:start position:0% second one to take up um the whole rack so<03:16:39.779> multi-layer<03:16:40.620> switches<03:16:41.040> operate 03:16:42.370 --> 03:16:42.380 align:start position:0% so multi-layer switches operate 03:16:42.380 --> 03:16:45.230 align:start position:0% so multi-layer switches operate multiple<03:16:43.380> layers<03:16:43.680> from<03:16:43.979> two<03:16:44.160> to<03:16:44.399> seven 03:16:45.230 --> 03:16:45.240 align:start position:0% multiple layers from two to seven 03:16:45.240 --> 03:16:48.410 align:start position:0% multiple layers from two to seven bandwidth<03:16:45.899> can<03:16:46.080> be<03:16:46.200> up<03:16:46.319> to<03:16:46.439> several<03:16:46.740> gigahertz 03:16:48.410 --> 03:16:48.420 align:start position:0% bandwidth can be up to several gigahertz 03:16:48.420 --> 03:16:50.570 align:start position:0% bandwidth can be up to several gigahertz and<03:16:48.779> you<03:16:48.899> can<03:16:49.020> stack<03:16:49.260> Cisco<03:16:49.740> switches<03:16:50.220> so<03:16:50.460> they 03:16:50.570 --> 03:16:50.580 align:start position:0% and you can stack Cisco switches so they 03:16:50.580 --> 03:16:52.190 align:start position:0% and you can stack Cisco switches so they all<03:16:50.760> become<03:16:51.060> one<03:16:51.300> you<03:16:51.660> could<03:16:51.779> have<03:16:51.899> two<03:16:52.080> or 03:16:52.190 --> 03:16:52.200 align:start position:0% all become one you could have two or 03:16:52.200 --> 03:16:54.469 align:start position:0% all become one you could have two or three<03:16:52.380> switches<03:16:52.800> or<03:16:53.100> becoming<03:16:53.580> one<03:16:54.060> logical 03:16:54.469 --> 03:16:54.479 align:start position:0% three switches or becoming one logical 03:16:54.479 --> 03:16:55.730 align:start position:0% three switches or becoming one logical switch 03:16:55.730 --> 03:16:55.740 align:start position:0% switch 03:16:55.740 --> 03:16:58.190 align:start position:0% switch and<03:16:56.279> ports<03:16:56.760> can<03:16:56.939> be<03:16:57.060> switched<03:16:57.600> which<03:16:57.840> is<03:16:57.960> Mac 03:16:58.190 --> 03:16:58.200 align:start position:0% and ports can be switched which is Mac 03:16:58.200 --> 03:17:00.769 align:start position:0% and ports can be switched which is Mac address<03:16:58.439> a<03:16:59.160> MAC<03:16:59.399> address<03:16:59.520> in<03:16:59.939> or<03:17:00.479> you<03:17:00.600> can 03:17:00.769 --> 03:17:00.779 align:start position:0% address a MAC address in or you can 03:17:00.779 --> 03:17:04.370 align:start position:0% address a MAC address in or you can configure<03:17:01.200> them<03:17:01.439> to<03:17:01.920> be<03:17:02.340> a<03:17:02.580> layer<03:17:02.880> 3<03:17:03.060> port<03:17:03.479> and 03:17:04.370 --> 03:17:04.380 align:start position:0% configure them to be a layer 3 port and 03:17:04.380 --> 03:17:06.650 align:start position:0% configure them to be a layer 3 port and Route<03:17:04.680> IP<03:17:05.460> addresses 03:17:06.650 --> 03:17:06.660 align:start position:0% Route IP addresses 03:17:06.660 --> 03:17:08.570 align:start position:0% Route IP addresses and<03:17:07.260> I<03:17:07.500> think<03:17:07.620> that's<03:17:07.740> outside<03:17:07.920> the<03:17:08.220> syllabus 03:17:08.570 --> 03:17:08.580 align:start position:0% and I think that's outside the syllabus 03:17:08.580 --> 03:17:11.809 align:start position:0% and I think that's outside the syllabus how<03:17:08.760> to<03:17:08.880> actually<03:17:09.060> configure<03:17:09.540> it 03:17:11.809 --> 03:17:11.819 align:start position:0% 03:17:11.819 --> 03:17:13.730 align:start position:0% um<03:17:11.939> so<03:17:12.240> this<03:17:12.420> would<03:17:12.540> be<03:17:12.720> your<03:17:12.960> typical<03:17:13.200> layer<03:17:13.620> 2 03:17:13.730 --> 03:17:13.740 align:start position:0% um so this would be your typical layer 2 03:17:13.740 --> 03:17:17.030 align:start position:0% um so this would be your typical layer 2 switch<03:17:14.040> now<03:17:14.340> if<03:17:14.580> you<03:17:14.760> wanted<03:17:15.060> to<03:17:15.660> uh<03:17:16.500> route<03:17:16.740> so 03:17:17.030 --> 03:17:17.040 align:start position:0% switch now if you wanted to uh route so 03:17:17.040 --> 03:17:20.090 align:start position:0% switch now if you wanted to uh route so if<03:17:17.279> these<03:17:17.520> devices<03:17:18.140> down<03:17:19.140> here<03:17:19.319> on<03:17:19.500> VLAN<03:17:19.920> 20 03:17:20.090 --> 03:17:20.100 align:start position:0% if these devices down here on VLAN 20 03:17:20.100 --> 03:17:22.090 align:start position:0% if these devices down here on VLAN 20 you<03:17:20.340> can<03:17:20.460> see<03:17:20.520> they're<03:17:20.700> on 03:17:22.090 --> 03:17:22.100 align:start position:0% you can see they're on 03:17:22.100 --> 03:17:25.210 align:start position:0% you can see they're on 192.168.20<03:17:23.100> well<03:17:24.060> that's<03:17:24.240> not<03:17:24.420> a<03:17:24.660> different 03:17:25.210 --> 03:17:25.220 align:start position:0% 192.168.20 well that's not a different 03:17:25.220 --> 03:17:28.610 align:start position:0% 192.168.20 well that's not a different subnet<03:17:26.220> to<03:17:26.939> one<03:17:27.420> on<03:17:27.600> two<03:17:27.720> one<03:17:27.840> six<03:17:28.080> eight<03:17:28.260> ten 03:17:28.610 --> 03:17:28.620 align:start position:0% subnet to one on two one six eight ten 03:17:28.620 --> 03:17:32.389 align:start position:0% subnet to one on two one six eight ten so<03:17:29.279> this<03:17:29.520> would<03:17:29.640> be<03:17:29.819> host<03:17:30.120> uh<03:17:30.720> one<03:17:31.140> and<03:17:31.859> two<03:17:32.100> for 03:17:32.389 --> 03:17:32.399 align:start position:0% so this would be host uh one and two for 03:17:32.399 --> 03:17:34.610 align:start position:0% so this would be host uh one and two for example<03:17:32.640> on<03:17:33.060> that<03:17:33.180> subnet<03:17:33.660> and<03:17:34.200> this<03:17:34.380> would<03:17:34.500> be 03:17:34.610 --> 03:17:34.620 align:start position:0% example on that subnet and this would be 03:17:34.620 --> 03:17:39.170 align:start position:0% example on that subnet and this would be host<03:17:35.120> one<03:17:36.200> and<03:17:37.200> two<03:17:37.500> on<03:17:37.800> that<03:17:38.040> subnet<03:17:38.460> well<03:17:38.939> the 03:17:39.170 --> 03:17:39.180 align:start position:0% host one and two on that subnet well the 03:17:39.180 --> 03:17:40.849 align:start position:0% host one and two on that subnet well the only<03:17:39.300> way<03:17:39.540> because<03:17:39.840> this<03:17:40.140> is<03:17:40.260> working<03:17:40.500> at 03:17:40.849 --> 03:17:40.859 align:start position:0% only way because this is working at 03:17:40.859 --> 03:17:44.269 align:start position:0% only way because this is working at Layer<03:17:41.279> Two<03:17:41.520> the<03:17:42.479> only<03:17:42.600> way<03:17:42.960> to<03:17:43.260> Route<03:17:43.500> because 03:17:44.269 --> 03:17:44.279 align:start position:0% Layer Two the only way to Route because 03:17:44.279 --> 03:17:47.269 align:start position:0% Layer Two the only way to Route because we're<03:17:44.640> we're<03:17:44.939> dealing<03:17:45.660> with<03:17:45.840> layer<03:17:46.140> two<03:17:46.380> layer 03:17:47.269 --> 03:17:47.279 align:start position:0% we're we're dealing with layer two layer 03:17:47.279 --> 03:17:50.990 align:start position:0% we're we're dealing with layer two layer 3<03:17:47.460> here<03:17:47.840> and<03:17:48.840> so<03:17:49.140> all<03:17:49.380> layer<03:17:49.680> 2<03:17:49.859> traffic<03:17:50.160> this 03:17:50.990 --> 03:17:51.000 align:start position:0% 3 here and so all layer 2 traffic this 03:17:51.000 --> 03:17:53.269 align:start position:0% 3 here and so all layer 2 traffic this switch<03:17:51.240> would<03:17:51.540> take<03:17:51.720> care<03:17:51.960> of<03:17:52.080> in<03:17:52.439> its<03:17:52.859> Mac 03:17:53.269 --> 03:17:53.279 align:start position:0% switch would take care of in its Mac 03:17:53.279 --> 03:17:55.730 align:start position:0% switch would take care of in its Mac table<03:17:53.580> which<03:17:54.000> we've<03:17:54.240> covered<03:17:54.479> earlier<03:17:54.840> now<03:17:55.560> if 03:17:55.730 --> 03:17:55.740 align:start position:0% table which we've covered earlier now if 03:17:55.740 --> 03:17:58.190 align:start position:0% table which we've covered earlier now if you<03:17:55.920> wanted<03:17:56.100> a<03:17:56.460> route<03:17:56.640> then 03:17:58.190 --> 03:17:58.200 align:start position:0% you wanted a route then 03:17:58.200 --> 03:18:00.769 align:start position:0% you wanted a route then um<03:17:58.399> traditionally<03:17:59.399> you<03:18:00.060> would<03:18:00.180> have<03:18:00.359> to<03:18:00.479> send 03:18:00.769 --> 03:18:00.779 align:start position:0% um traditionally you would have to send 03:18:00.779 --> 03:18:04.610 align:start position:0% um traditionally you would have to send out<03:18:01.020> the<03:18:01.460> packet<03:18:02.460> to<03:18:03.120> the<03:18:03.359> router<03:18:03.779> the<03:18:04.319> router 03:18:04.610 --> 03:18:04.620 align:start position:0% out the packet to the router the router 03:18:04.620 --> 03:18:07.550 align:start position:0% out the packet to the router the router has<03:18:04.800> a<03:18:04.979> directory<03:18:05.460> of<03:18:05.640> all<03:18:05.760> the<03:18:05.939> networks<03:18:06.560> 10 03:18:07.550 --> 03:18:07.560 align:start position:0% has a directory of all the networks 10 03:18:07.560 --> 03:18:10.790 align:start position:0% has a directory of all the networks 10 20.<03:18:08.340> this<03:18:08.819> network<03:18:09.180> 30<03:18:09.600> will<03:18:10.080> probably<03:18:10.319> be<03:18:10.500> for 03:18:10.790 --> 03:18:10.800 align:start position:0% 20. this network 30 will probably be for 03:18:10.800 --> 03:18:13.870 align:start position:0% 20. this network 30 will probably be for foreign 03:18:13.870 --> 03:18:13.880 align:start position:0% 03:18:13.880 --> 03:18:16.309 align:start position:0% management<03:18:14.880> traffic<03:18:15.600> or<03:18:16.020> it<03:18:16.140> could<03:18:16.260> be 03:18:16.309 --> 03:18:16.319 align:start position:0% management traffic or it could be 03:18:16.319 --> 03:18:17.510 align:start position:0% management traffic or it could be whatever<03:18:16.500> you<03:18:16.800> want 03:18:17.510 --> 03:18:17.520 align:start position:0% whatever you want 03:18:17.520 --> 03:18:20.030 align:start position:0% whatever you want and<03:18:18.120> then<03:18:18.300> it<03:18:19.020> would<03:18:19.140> route<03:18:19.319> and<03:18:19.740> then<03:18:19.859> it 03:18:20.030 --> 03:18:20.040 align:start position:0% and then it would route and then it 03:18:20.040 --> 03:18:22.070 align:start position:0% and then it would route and then it would<03:18:20.220> decide<03:18:20.520> that<03:18:20.760> it<03:18:20.939> needs<03:18:21.240> to<03:18:21.300> send<03:18:21.899> that 03:18:22.070 --> 03:18:22.080 align:start position:0% would decide that it needs to send that 03:18:22.080 --> 03:18:24.110 align:start position:0% would decide that it needs to send that traffic<03:18:22.319> out<03:18:22.740> it<03:18:23.160> could<03:18:23.279> be<03:18:23.399> an<03:18:23.520> interface<03:18:23.880> or 03:18:24.110 --> 03:18:24.120 align:start position:0% traffic out it could be an interface or 03:18:24.120 --> 03:18:25.730 align:start position:0% traffic out it could be an interface or a<03:18:24.240> sub<03:18:24.359> interface 03:18:25.730 --> 03:18:25.740 align:start position:0% a sub interface 03:18:25.740 --> 03:18:28.570 align:start position:0% a sub interface this<03:18:26.279> is<03:18:26.399> uh<03:18:26.640> what's<03:18:26.939> known<03:18:27.240> as<03:18:27.540> a 03:18:28.570 --> 03:18:28.580 align:start position:0% this is uh what's known as a 03:18:28.580 --> 03:18:34.450 align:start position:0% this is uh what's known as a router<03:18:29.960> on<03:18:30.960> a 03:18:34.450 --> 03:18:34.460 align:start position:0% 03:18:34.460 --> 03:18:37.730 align:start position:0% stick<03:18:35.460> one<03:18:36.120> armed<03:18:36.540> router<03:18:36.899> or<03:18:37.080> router<03:18:37.439> on<03:18:37.560> a 03:18:37.730 --> 03:18:37.740 align:start position:0% stick one armed router or router on a 03:18:37.740 --> 03:18:39.349 align:start position:0% stick one armed router or router on a stick<03:18:37.920> and<03:18:38.399> unfortunately<03:18:38.819> they<03:18:39.060> have<03:18:39.180> the 03:18:39.349 --> 03:18:39.359 align:start position:0% stick and unfortunately they have the 03:18:39.359 --> 03:18:40.990 align:start position:0% stick and unfortunately they have the physical<03:18:39.420> cable 03:18:40.990 --> 03:18:41.000 align:start position:0% physical cable 03:18:41.000 --> 03:18:43.730 align:start position:0% physical cable uh<03:18:42.000> will<03:18:42.240> carry<03:18:42.540> all<03:18:42.660> the<03:18:42.779> traffic<03:18:42.960> coming<03:18:43.380> in 03:18:43.730 --> 03:18:43.740 align:start position:0% uh will carry all the traffic coming in 03:18:43.740 --> 03:18:46.010 align:start position:0% uh will carry all the traffic coming in and<03:18:43.859> out<03:18:44.040> not<03:18:44.700> a<03:18:44.880> great<03:18:45.000> way<03:18:45.359> to<03:18:45.600> run<03:18:45.779> your 03:18:46.010 --> 03:18:46.020 align:start position:0% and out not a great way to run your 03:18:46.020 --> 03:18:48.050 align:start position:0% and out not a great way to run your network<03:18:46.260> I<03:18:46.680> mean<03:18:46.800> it's<03:18:46.920> okay<03:18:47.279> if<03:18:47.520> you're<03:18:47.640> in<03:18:47.819> a 03:18:48.050 --> 03:18:48.060 align:start position:0% network I mean it's okay if you're in a 03:18:48.060 --> 03:18:49.670 align:start position:0% network I mean it's okay if you're in a small<03:18:48.240> business<03:18:48.420> and<03:18:48.779> nobody<03:18:49.080> would<03:18:49.319> notice 03:18:49.670 --> 03:18:49.680 align:start position:0% small business and nobody would notice 03:18:49.680 --> 03:18:51.950 align:start position:0% small business and nobody would notice but<03:18:50.520> this<03:18:50.760> is<03:18:50.819> carrying<03:18:51.240> all<03:18:51.359> your<03:18:51.540> bandwidth 03:18:51.950 --> 03:18:51.960 align:start position:0% but this is carrying all your bandwidth 03:18:51.960 --> 03:18:55.670 align:start position:0% but this is carrying all your bandwidth and<03:18:52.080> obviously<03:18:52.439> this<03:18:53.340> is<03:18:53.580> a<03:18:54.300> um<03:18:54.300> single<03:18:55.080> point 03:18:55.670 --> 03:18:55.680 align:start position:0% and obviously this is a um single point 03:18:55.680 --> 03:18:58.670 align:start position:0% and obviously this is a um single point of<03:18:56.040> failure<03:18:56.880> here<03:18:57.060> this<03:18:57.540> cable<03:18:57.840> breaks<03:18:58.319> all 03:18:58.670 --> 03:18:58.680 align:start position:0% of failure here this cable breaks all 03:18:58.680 --> 03:19:00.170 align:start position:0% of failure here this cable breaks all this<03:18:58.979> interface 03:19:00.170 --> 03:19:00.180 align:start position:0% this interface 03:19:00.180 --> 03:19:03.469 align:start position:0% this interface or<03:19:01.080> this<03:19:01.500> interface<03:19:01.979> then<03:19:02.640> you<03:19:03.000> can't<03:19:03.120> Route 03:19:03.469 --> 03:19:03.479 align:start position:0% or this interface then you can't Route 03:19:03.479 --> 03:19:06.349 align:start position:0% or this interface then you can't Route traffic<03:19:03.779> the<03:19:04.680> only<03:19:04.800> traffic<03:19:05.040> that<03:19:05.340> would<03:19:05.520> then 03:19:06.349 --> 03:19:06.359 align:start position:0% traffic the only traffic that would then 03:19:06.359 --> 03:19:08.330 align:start position:0% traffic the only traffic that would then pass<03:19:06.720> would<03:19:07.080> be 03:19:08.330 --> 03:19:08.340 align:start position:0% pass would be 03:19:08.340 --> 03:19:11.570 align:start position:0% pass would be um<03:19:08.399> with<03:19:09.000> it<03:19:09.180> within<03:19:09.540> the<03:19:10.020> um<03:19:10.020> VLAN<03:19:10.680> sorry 03:19:11.570 --> 03:19:11.580 align:start position:0% um with it within the um VLAN sorry 03:19:11.580 --> 03:19:13.250 align:start position:0% um with it within the um VLAN sorry uh<03:19:12.120> he<03:19:12.300> couldn't<03:19:12.420> be<03:19:12.600> couldn't<03:19:12.840> pass<03:19:13.020> this 03:19:13.250 --> 03:19:13.260 align:start position:0% uh he couldn't be couldn't pass this 03:19:13.260 --> 03:19:14.210 align:start position:0% uh he couldn't be couldn't pass this traffic 03:19:14.210 --> 03:19:14.220 align:start position:0% traffic 03:19:14.220 --> 03:19:18.230 align:start position:0% traffic so<03:19:14.760> this<03:19:15.120> is<03:19:15.420> a<03:19:15.859> multi-layer<03:19:16.859> switch 03:19:18.230 --> 03:19:18.240 align:start position:0% so this is a multi-layer switch 03:19:18.240 --> 03:19:19.849 align:start position:0% so this is a multi-layer switch so<03:19:18.600> call<03:19:18.899> it 03:19:19.849 --> 03:19:19.859 align:start position:0% so call it 03:19:19.859 --> 03:19:22.790 align:start position:0% so call it um<03:19:19.920> say<03:19:20.340> layer<03:19:20.700> 3<03:19:20.880> switch 03:19:22.790 --> 03:19:22.800 align:start position:0% um say layer 3 switch 03:19:22.800 --> 03:19:24.769 align:start position:0% um say layer 3 switch and<03:19:22.920> what<03:19:23.220> happens<03:19:23.399> is<03:19:23.760> as<03:19:24.359> you've<03:19:24.600> seen 03:19:24.769 --> 03:19:24.779 align:start position:0% and what happens is as you've seen 03:19:24.779 --> 03:19:26.630 align:start position:0% and what happens is as you've seen you've<03:19:25.080> got<03:19:25.200> the<03:19:25.500> modules<03:19:25.920> that<03:19:26.160> are<03:19:26.279> slotted 03:19:26.630 --> 03:19:26.640 align:start position:0% you've got the modules that are slotted 03:19:26.640 --> 03:19:28.910 align:start position:0% you've got the modules that are slotted in<03:19:26.819> here<03:19:27.120> the<03:19:27.899> more<03:19:28.080> you<03:19:28.319> pay<03:19:28.500> the<03:19:28.740> more 03:19:28.910 --> 03:19:28.920 align:start position:0% in here the more you pay the more 03:19:28.920 --> 03:19:31.190 align:start position:0% in here the more you pay the more options<03:19:29.279> you<03:19:29.460> have<03:19:29.640> obviously<03:19:30.060> and<03:19:30.899> this 03:19:31.190 --> 03:19:31.200 align:start position:0% options you have obviously and this 03:19:31.200 --> 03:19:33.650 align:start position:0% options you have obviously and this module 03:19:33.650 --> 03:19:33.660 align:start position:0% module 03:19:33.660 --> 03:19:36.769 align:start position:0% module here<03:19:34.500> is<03:19:35.040> for<03:19:35.399> switching<03:19:36.120> so<03:19:36.359> you've<03:19:36.540> got<03:19:36.660> all 03:19:36.769 --> 03:19:36.779 align:start position:0% here is for switching so you've got all 03:19:36.779 --> 03:19:39.170 align:start position:0% here is for switching so you've got all your<03:19:37.020> ethernet<03:19:37.560> connections<03:19:38.220> and<03:19:38.819> this<03:19:39.000> could 03:19:39.170 --> 03:19:39.180 align:start position:0% your ethernet connections and this could 03:19:39.180 --> 03:19:42.110 align:start position:0% your ethernet connections and this could be<03:19:39.300> your<03:19:39.600> routing<03:19:40.080> module<03:19:40.859> and<03:19:41.640> so<03:19:41.819> all 03:19:42.110 --> 03:19:42.120 align:start position:0% be your routing module and so all 03:19:42.120 --> 03:19:44.450 align:start position:0% be your routing module and so all contained<03:19:42.600> within<03:19:42.840> the<03:19:42.899> same<03:19:43.140> chassis<03:19:43.680> and 03:19:44.450 --> 03:19:44.460 align:start position:0% contained within the same chassis and 03:19:44.460 --> 03:19:46.190 align:start position:0% contained within the same chassis and the<03:19:44.640> technology<03:19:45.000> isn't<03:19:45.660> really<03:19:45.779> covered<03:19:46.080> in 03:19:46.190 --> 03:19:46.200 align:start position:0% the technology isn't really covered in 03:19:46.200 --> 03:19:48.830 align:start position:0% the technology isn't really covered in the<03:19:46.319> syllabus<03:19:46.740> but<03:19:47.340> it<03:19:47.520> would<03:19:47.700> switch<03:19:47.880> the<03:19:48.420> uh 03:19:48.830 --> 03:19:48.840 align:start position:0% the syllabus but it would switch the uh 03:19:48.840 --> 03:19:51.710 align:start position:0% the syllabus but it would switch the uh traffic<03:19:49.080> depending<03:19:49.740> if<03:19:49.859> it's<03:19:50.040> Layer<03:19:50.399> Two<03:19:50.720> or 03:19:51.710 --> 03:19:51.720 align:start position:0% traffic depending if it's Layer Two or 03:19:51.720 --> 03:19:54.410 align:start position:0% traffic depending if it's Layer Two or layer<03:19:52.200> 3<03:19:52.319> within<03:19:52.979> the<03:19:53.160> same<03:19:53.340> unit<03:19:53.700> so 03:19:54.410 --> 03:19:54.420 align:start position:0% layer 3 within the same unit so 03:19:54.420 --> 03:19:57.050 align:start position:0% layer 3 within the same unit so basically<03:19:54.840> what<03:19:55.140> you<03:19:55.380> don't<03:19:55.859> have<03:19:56.040> to<03:19:56.220> have<03:19:56.460> is 03:19:57.050 --> 03:19:57.060 align:start position:0% basically what you don't have to have is 03:19:57.060 --> 03:19:59.809 align:start position:0% basically what you don't have to have is this<03:19:58.020> device<03:19:58.200> here<03:19:58.680> and<03:19:59.160> this<03:19:59.340> device<03:19:59.520> here 03:19:59.809 --> 03:19:59.819 align:start position:0% this device here and this device here 03:19:59.819 --> 03:20:02.150 align:start position:0% this device here and this device here it's<03:20:00.000> all<03:20:00.240> within<03:20:01.200> the<03:20:01.260> same<03:20:01.380> unit<03:20:01.680> and 03:20:02.150 --> 03:20:02.160 align:start position:0% it's all within the same unit and 03:20:02.160 --> 03:20:03.710 align:start position:0% it's all within the same unit and depending<03:20:02.520> on<03:20:02.580> what<03:20:02.760> you<03:20:02.880> spend<03:20:03.180> this<03:20:03.600> could 03:20:03.710 --> 03:20:03.720 align:start position:0% depending on what you spend this could 03:20:03.720 --> 03:20:04.550 align:start position:0% depending on what you spend this could be 03:20:04.550 --> 03:20:04.560 align:start position:0% be 03:20:04.560 --> 03:20:07.190 align:start position:0% be um doing<03:20:05.100> access<03:20:05.340> lists<03:20:06.000> on<03:20:06.479> also<03:20:06.840> your 03:20:07.190 --> 03:20:07.200 align:start position:0% um doing access lists on also your 03:20:07.200 --> 03:20:09.590 align:start position:0% um doing access lists on also your connection<03:20:07.380> out<03:20:07.800> to<03:20:08.040> the<03:20:08.220> internet<03:20:08.600> depending 03:20:09.590 --> 03:20:09.600 align:start position:0% connection out to the internet depending 03:20:09.600 --> 03:20:11.630 align:start position:0% connection out to the internet depending on<03:20:09.720> how<03:20:10.080> how<03:20:10.620> much<03:20:10.800> money<03:20:10.979> you<03:20:11.160> have<03:20:11.340> and<03:20:11.460> what 03:20:11.630 --> 03:20:11.640 align:start position:0% on how how much money you have and what 03:20:11.640 --> 03:20:14.389 align:start position:0% on how how much money you have and what your<03:20:11.760> requirements<03:20:12.359> are 03:20:14.389 --> 03:20:14.399 align:start position:0% your requirements are 03:20:14.399 --> 03:20:17.210 align:start position:0% your requirements are uh<03:20:15.120> next<03:20:15.359> device<03:20:15.660> is<03:20:15.960> a<03:20:16.200> wireless<03:20:16.380> controller 03:20:17.210 --> 03:20:17.220 align:start position:0% uh next device is a wireless controller 03:20:17.220 --> 03:20:19.849 align:start position:0% uh next device is a wireless controller this<03:20:17.580> is<03:20:17.700> a<03:20:17.880> Cisco<03:20:18.240> 2500<03:20:19.020> Cisco<03:20:19.620> wireless 03:20:19.849 --> 03:20:19.859 align:start position:0% this is a Cisco 2500 Cisco wireless 03:20:19.859 --> 03:20:21.469 align:start position:0% this is a Cisco 2500 Cisco wireless controller 03:20:21.469 --> 03:20:21.479 align:start position:0% controller 03:20:21.479 --> 03:20:23.990 align:start position:0% controller has<03:20:22.020> the<03:20:22.380> cheaper<03:20:22.800> devices<03:20:23.160> you've<03:20:23.880> probably 03:20:23.990 --> 03:20:24.000 align:start position:0% has the cheaper devices you've probably 03:20:24.000 --> 03:20:26.330 align:start position:0% has the cheaper devices you've probably seen<03:20:24.420> you<03:20:24.600> probably<03:20:24.779> got<03:20:25.500> one<03:20:25.680> at<03:20:25.859> home<03:20:25.979> here 03:20:26.330 --> 03:20:26.340 align:start position:0% seen you probably got one at home here 03:20:26.340 --> 03:20:29.990 align:start position:0% seen you probably got one at home here is<03:20:27.240> your<03:20:27.540> wireless<03:20:27.960> access<03:20:28.319> points<03:20:29.520> and<03:20:29.819> what 03:20:29.990 --> 03:20:30.000 align:start position:0% is your wireless access points and what 03:20:30.000 --> 03:20:32.510 align:start position:0% is your wireless access points and what happens<03:20:30.180> is<03:20:30.479> you've<03:20:30.840> got<03:20:30.960> a<03:20:31.500> few<03:20:32.040> um<03:20:32.100> wireless 03:20:32.510 --> 03:20:32.520 align:start position:0% happens is you've got a few um wireless 03:20:32.520 --> 03:20:35.269 align:start position:0% happens is you've got a few um wireless access<03:20:32.880> points<03:20:33.540> probably<03:20:33.840> say<03:20:34.560> this<03:20:34.859> is<03:20:34.979> your 03:20:35.269 --> 03:20:35.279 align:start position:0% access points probably say this is your 03:20:35.279 --> 03:20:37.969 align:start position:0% access points probably say this is your office 03:20:37.969 --> 03:20:37.979 align:start position:0% 03:20:37.979 --> 03:20:39.889 align:start position:0% and<03:20:38.460> normally<03:20:38.819> these<03:20:39.120> would<03:20:39.300> take<03:20:39.540> care<03:20:39.720> of 03:20:39.889 --> 03:20:39.899 align:start position:0% and normally these would take care of 03:20:39.899 --> 03:20:42.290 align:start position:0% and normally these would take care of all<03:20:40.080> of<03:20:40.260> the<03:20:40.380> connections<03:20:41.340> what<03:20:41.819> happens<03:20:42.060> is 03:20:42.290 --> 03:20:42.300 align:start position:0% all of the connections what happens is 03:20:42.300 --> 03:20:45.469 align:start position:0% all of the connections what happens is these<03:20:42.660> become<03:20:43.040> lightweight<03:20:44.040> access<03:20:44.819> points 03:20:45.469 --> 03:20:45.479 align:start position:0% these become lightweight access points 03:20:45.479 --> 03:20:48.170 align:start position:0% these become lightweight access points in<03:20:46.020> as<03:20:46.260> much<03:20:46.439> as<03:20:46.680> all<03:20:47.460> they're<03:20:47.640> doing<03:20:47.880> is 03:20:48.170 --> 03:20:48.180 align:start position:0% in as much as all they're doing is 03:20:48.180 --> 03:20:51.110 align:start position:0% in as much as all they're doing is taking<03:20:48.420> in<03:20:48.779> all<03:20:49.140> of<03:20:49.260> the<03:20:49.500> signals<03:20:50.220> and<03:20:50.939> then 03:20:51.110 --> 03:20:51.120 align:start position:0% taking in all of the signals and then 03:20:51.120 --> 03:20:54.349 align:start position:0% taking in all of the signals and then passing<03:20:51.479> it<03:20:51.660> over<03:20:51.779> to<03:20:52.080> this<03:20:52.380> master<03:20:52.979> device 03:20:54.349 --> 03:20:54.359 align:start position:0% passing it over to this master device 03:20:54.359 --> 03:20:57.290 align:start position:0% passing it over to this master device obviously<03:20:55.080> it<03:20:55.200> costs<03:20:55.439> a<03:20:55.560> bit<03:20:55.680> more<03:20:56.340> and<03:20:57.060> so 03:20:57.290 --> 03:20:57.300 align:start position:0% obviously it costs a bit more and so 03:20:57.300 --> 03:20:58.790 align:start position:0% obviously it costs a bit more and so these<03:20:57.540> are<03:20:57.600> lightwork<03:20:57.899> access<03:20:58.140> points<03:20:58.680> and 03:20:58.790 --> 03:20:58.800 align:start position:0% these are lightwork access points and 03:20:58.800 --> 03:21:01.490 align:start position:0% these are lightwork access points and this<03:20:58.979> is<03:20:59.160> your<03:20:59.580> wireless<03:21:00.300> LAN<03:21:00.779> controller 03:21:01.490 --> 03:21:01.500 align:start position:0% this is your wireless LAN controller 03:21:01.500 --> 03:21:06.050 align:start position:0% this is your wireless LAN controller which<03:21:02.160> some<03:21:02.340> people<03:21:02.460> refer<03:21:02.939> to<03:21:03.000> as<03:21:03.180> wlc 03:21:06.050 --> 03:21:06.060 align:start position:0% 03:21:06.060 --> 03:21:08.690 align:start position:0% so<03:21:06.600> it<03:21:06.779> allows<03:21:07.200> your<03:21:07.439> wireless<03:21:07.680> devices<03:21:08.220> to 03:21:08.690 --> 03:21:08.700 align:start position:0% so it allows your wireless devices to 03:21:08.700 --> 03:21:10.130 align:start position:0% so it allows your wireless devices to communicate<03:21:09.120> and<03:21:09.359> you<03:21:09.479> can<03:21:09.720> see<03:21:09.840> you've<03:21:10.020> got 03:21:10.130 --> 03:21:10.140 align:start position:0% communicate and you can see you've got 03:21:10.140 --> 03:21:12.830 align:start position:0% communicate and you can see you've got some<03:21:10.500> wired<03:21:10.979> connections<03:21:11.640> there<03:21:11.819> as<03:21:12.000> well 03:21:12.830 --> 03:21:12.840 align:start position:0% some wired connections there as well 03:21:12.840 --> 03:21:15.530 align:start position:0% some wired connections there as well takes<03:21:13.260> over<03:21:13.500> from<03:21:13.979> the<03:21:14.399> access<03:21:14.939> points 03:21:15.530 --> 03:21:15.540 align:start position:0% takes over from the access points 03:21:15.540 --> 03:21:18.110 align:start position:0% takes over from the access points becoming<03:21:15.899> lightweight<03:21:16.500> forwarders<03:21:16.979> so<03:21:17.880> you'd 03:21:18.110 --> 03:21:18.120 align:start position:0% becoming lightweight forwarders so you'd 03:21:18.120 --> 03:21:20.510 align:start position:0% becoming lightweight forwarders so you'd have<03:21:18.240> to<03:21:18.420> throw<03:21:18.479> them<03:21:18.720> away<03:21:18.899> which<03:21:19.200> is<03:21:19.319> Handy 03:21:20.510 --> 03:21:20.520 align:start position:0% have to throw them away which is Handy 03:21:20.520 --> 03:21:23.690 align:start position:0% have to throw them away which is Handy the<03:21:21.479> wireless<03:21:21.840> access<03:21:22.200> controller<03:21:23.040> has<03:21:23.340> your 03:21:23.690 --> 03:21:23.700 align:start position:0% the wireless access controller has your 03:21:23.700 --> 03:21:26.210 align:start position:0% the wireless access controller has your service<03:21:24.420> set<03:21:24.720> ID<03:21:25.020> it<03:21:25.620> can<03:21:25.740> have<03:21:25.859> logical 03:21:26.210 --> 03:21:26.220 align:start position:0% service set ID it can have logical 03:21:26.220 --> 03:21:28.790 align:start position:0% service set ID it can have logical interfaces<03:21:27.000> and<03:21:27.660> as<03:21:27.779> you<03:21:27.960> can<03:21:28.080> see<03:21:28.200> down<03:21:28.500> here 03:21:28.790 --> 03:21:28.800 align:start position:0% interfaces and as you can see down here 03:21:28.800 --> 03:21:30.830 align:start position:0% interfaces and as you can see down here you've<03:21:29.340> got<03:21:29.460> physical<03:21:29.640> pause<03:21:30.060> for<03:21:30.359> ethernet 03:21:30.830 --> 03:21:30.840 align:start position:0% you've got physical pause for ethernet 03:21:30.840 --> 03:21:34.210 align:start position:0% you've got physical pause for ethernet and<03:21:31.319> when<03:21:31.560> you<03:21:31.740> first<03:21:32.120> buy<03:21:33.120> it<03:21:33.300> if<03:21:33.600> you<03:21:33.779> want<03:21:34.020> to 03:21:34.210 --> 03:21:34.220 align:start position:0% and when you first buy it if you want to 03:21:34.220 --> 03:21:37.370 align:start position:0% and when you first buy it if you want to you<03:21:35.220> can<03:21:35.340> connect<03:21:36.000> to<03:21:36.240> the<03:21:36.420> console<03:21:36.779> Port<03:21:36.960> here 03:21:37.370 --> 03:21:37.380 align:start position:0% you can connect to the console Port here 03:21:37.380 --> 03:21:41.090 align:start position:0% you can connect to the console Port here and<03:21:38.100> then<03:21:38.279> use<03:21:38.580> your<03:21:38.939> PC<03:21:39.899> to<03:21:40.140> set<03:21:40.319> it<03:21:40.439> up<03:21:40.620> to 03:21:41.090 --> 03:21:41.100 align:start position:0% and then use your PC to set it up to 03:21:41.100 --> 03:21:41.929 align:start position:0% and then use your PC to set it up to whatever 03:21:41.929 --> 03:21:41.939 align:start position:0% whatever 03:21:41.939 --> 03:21:43.910 align:start position:0% whatever um parameters<03:21:42.600> you<03:21:42.840> want<03:21:42.960> and<03:21:43.439> also<03:21:43.680> you<03:21:43.800> can 03:21:43.910 --> 03:21:43.920 align:start position:0% um parameters you want and also you can 03:21:43.920 --> 03:21:46.490 align:start position:0% um parameters you want and also you can use<03:21:44.040> this<03:21:44.220> port<03:21:44.460> here<03:21:44.700> for<03:21:45.000> Disaster<03:21:45.420> Recovery 03:21:46.490 --> 03:21:46.500 align:start position:0% use this port here for Disaster Recovery 03:21:46.500 --> 03:21:48.170 align:start position:0% use this port here for Disaster Recovery you<03:21:47.040> obviously<03:21:47.340> have<03:21:47.460> to<03:21:47.640> be<03:21:47.760> physically 03:21:48.170 --> 03:21:48.180 align:start position:0% you obviously have to be physically 03:21:48.180 --> 03:21:52.429 align:start position:0% you obviously have to be physically present<03:21:48.660> unless<03:21:49.319> you<03:21:49.500> connect<03:21:49.740> a<03:21:50.399> Cisco 03:21:52.429 --> 03:21:52.439 align:start position:0% present unless you connect a Cisco 03:21:52.439 --> 03:21:54.650 align:start position:0% present unless you connect a Cisco access<03:21:53.040> server<03:21:53.700> which<03:21:53.939> we'll<03:21:54.120> cover<03:21:54.300> later 03:21:54.650 --> 03:21:54.660 align:start position:0% access server which we'll cover later 03:21:54.660 --> 03:21:56.389 align:start position:0% access server which we'll cover later which<03:21:55.560> um<03:21:55.560> that<03:21:55.859> would<03:21:55.979> have<03:21:56.100> an<03:21:56.279> internet 03:21:56.389 --> 03:21:56.399 align:start position:0% which um that would have an internet 03:21:56.399 --> 03:21:59.269 align:start position:0% which um that would have an internet connection<03:21:56.819> out<03:21:57.300> here<03:21:57.540> so<03:21:58.020> you<03:21:58.200> could 03:21:59.269 --> 03:21:59.279 align:start position:0% connection out here so you could 03:21:59.279 --> 03:22:00.650 align:start position:0% connection out here so you could um<03:21:59.340> and<03:21:59.520> if<03:21:59.700> you<03:21:59.819> said<03:21:59.939> tile<03:22:00.180> Nets<03:22:00.540> probably 03:22:00.650 --> 03:22:00.660 align:start position:0% um and if you said tile Nets probably 03:22:00.660 --> 03:22:03.769 align:start position:0% um and if you said tile Nets probably ssh<03:22:01.200> in<03:22:01.800> through 03:22:03.769 --> 03:22:03.779 align:start position:0% ssh in through 03:22:03.779 --> 03:22:06.349 align:start position:0% ssh in through um<03:22:03.899> here<03:22:04.260> and<03:22:04.740> then<03:22:04.859> you<03:22:05.100> could<03:22:05.220> from<03:22:05.819> the<03:22:06.000> from 03:22:06.349 --> 03:22:06.359 align:start position:0% um here and then you could from the from 03:22:06.359 --> 03:22:07.429 align:start position:0% um here and then you could from the from this<03:22:06.899> um 03:22:07.429 --> 03:22:07.439 align:start position:0% this um 03:22:07.439 --> 03:22:09.950 align:start position:0% this um Cisco<03:22:08.220> access<03:22:08.399> over<03:22:08.939> here 03:22:09.950 --> 03:22:09.960 align:start position:0% Cisco access over here 03:22:09.960 --> 03:22:11.389 align:start position:0% Cisco access over here you<03:22:10.380> would<03:22:10.500> have<03:22:10.620> a<03:22:10.740> connection<03:22:10.859> going<03:22:11.220> into 03:22:11.389 --> 03:22:11.399 align:start position:0% you would have a connection going into 03:22:11.399 --> 03:22:13.250 align:start position:0% you would have a connection going into your<03:22:11.580> console<03:22:11.939> Port<03:22:12.180> but<03:22:12.660> we'll<03:22:12.840> cover<03:22:13.020> that 03:22:13.250 --> 03:22:13.260 align:start position:0% your console Port but we'll cover that 03:22:13.260 --> 03:22:14.389 align:start position:0% your console Port but we'll cover that later 03:22:14.389 --> 03:22:14.399 align:start position:0% later 03:22:14.399 --> 03:22:17.210 align:start position:0% later uh<03:22:14.939> ports<03:22:15.300> can<03:22:15.420> be<03:22:15.600> switched<03:22:16.080> uh<03:22:16.800> so<03:22:16.979> they're 03:22:17.210 --> 03:22:17.220 align:start position:0% uh ports can be switched uh so they're 03:22:17.220 --> 03:22:18.889 align:start position:0% uh ports can be switched uh so they're just<03:22:17.399> dealing<03:22:17.700> with<03:22:17.760> Mac<03:22:17.939> addresses<03:22:18.359> or<03:22:18.660> they 03:22:18.889 --> 03:22:18.899 align:start position:0% just dealing with Mac addresses or they 03:22:18.899 --> 03:22:20.990 align:start position:0% just dealing with Mac addresses or they can<03:22:19.080> be<03:22:19.380> configured<03:22:19.859> to<03:22:19.979> route 03:22:20.990 --> 03:22:21.000 align:start position:0% can be configured to route 03:22:21.000 --> 03:22:22.849 align:start position:0% can be configured to route depending<03:22:21.600> on<03:22:21.660> what<03:22:21.960> you<03:22:22.080> need 03:22:22.849 --> 03:22:22.859 align:start position:0% depending on what you need 03:22:22.859 --> 03:22:25.490 align:start position:0% depending on what you need so<03:22:23.460> your<03:22:23.700> wireless<03:22:23.819> controllers<03:22:24.600> these<03:22:25.260> your 03:22:25.490 --> 03:22:25.500 align:start position:0% so your wireless controllers these your 03:22:25.500 --> 03:22:27.290 align:start position:0% so your wireless controllers these your wireless<03:22:25.620> LAN<03:22:25.920> controllers<03:22:26.460> permit<03:22:27.060> mobile 03:22:27.290 --> 03:22:27.300 align:start position:0% wireless LAN controllers permit mobile 03:22:27.300 --> 03:22:31.190 align:start position:0% wireless LAN controllers permit mobile devices<03:22:27.840> to<03:22:28.500> Rome<03:22:29.300> roaming<03:22:30.300> means<03:22:30.600> keeping 03:22:31.190 --> 03:22:31.200 align:start position:0% devices to Rome roaming means keeping 03:22:31.200 --> 03:22:33.830 align:start position:0% devices to Rome roaming means keeping the<03:22:31.380> same<03:22:31.500> IP<03:22:31.979> address 03:22:33.830 --> 03:22:33.840 align:start position:0% the same IP address 03:22:33.840 --> 03:22:35.690 align:start position:0% the same IP address now<03:22:34.200> you<03:22:34.380> can<03:22:34.500> have<03:22:34.620> intra<03:22:35.040> controller 03:22:35.690 --> 03:22:35.700 align:start position:0% now you can have intra controller 03:22:35.700 --> 03:22:37.550 align:start position:0% now you can have intra controller roaming<03:22:36.540> so<03:22:36.779> you've<03:22:36.960> just<03:22:37.080> got<03:22:37.260> one 03:22:37.550 --> 03:22:37.560 align:start position:0% roaming so you've just got one 03:22:37.560 --> 03:22:39.769 align:start position:0% roaming so you've just got one controller<03:22:38.040> or<03:22:38.640> you<03:22:38.760> can<03:22:38.880> have<03:22:39.060> inter<03:22:39.420> control 03:22:39.769 --> 03:22:39.779 align:start position:0% controller or you can have inter control 03:22:39.779 --> 03:22:41.269 align:start position:0% controller or you can have inter control around<03:22:40.140> me<03:22:40.439> which<03:22:40.620> is<03:22:40.740> a<03:22:40.859> little<03:22:40.920> bit<03:22:41.040> more 03:22:41.269 --> 03:22:41.279 align:start position:0% around me which is a little bit more 03:22:41.279 --> 03:22:43.790 align:start position:0% around me which is a little bit more difficult<03:22:41.640> but<03:22:42.420> as<03:22:42.660> you're<03:22:42.899> walking<03:22:43.200> through 03:22:43.790 --> 03:22:43.800 align:start position:0% difficult but as you're walking through 03:22:43.800 --> 03:22:47.450 align:start position:0% difficult but as you're walking through your<03:22:44.760> say<03:22:45.660> you're<03:22:45.840> in<03:22:46.020> a<03:22:46.140> coffee<03:22:46.260> shop 03:22:47.450 --> 03:22:47.460 align:start position:0% your say you're in a coffee shop 03:22:47.460 --> 03:22:49.969 align:start position:0% your say you're in a coffee shop and<03:22:48.420> you've<03:22:49.200> got 03:22:49.969 --> 03:22:49.979 align:start position:0% and you've got 03:22:49.979 --> 03:22:52.429 align:start position:0% and you've got ground<03:22:50.640> floor<03:22:51.000> here<03:22:51.359> and<03:22:51.840> say<03:22:52.020> there's<03:22:52.260> a 03:22:52.429 --> 03:22:52.439 align:start position:0% ground floor here and say there's a 03:22:52.439 --> 03:22:54.769 align:start position:0% ground floor here and say there's a concrete<03:22:52.979> which<03:22:53.520> normally<03:22:53.819> is<03:22:54.000> as<03:22:54.300> a<03:22:54.479> concrete 03:22:54.769 --> 03:22:54.779 align:start position:0% concrete which normally is as a concrete 03:22:54.779 --> 03:22:57.650 align:start position:0% concrete which normally is as a concrete floor<03:22:55.020> and<03:22:55.680> you<03:22:55.800> go<03:22:55.979> up<03:22:56.160> the<03:22:56.399> stairs<03:22:56.880> look<03:22:57.420> at 03:22:57.650 --> 03:22:57.660 align:start position:0% floor and you go up the stairs look at 03:22:57.660 --> 03:23:01.010 align:start position:0% floor and you go up the stairs look at my<03:22:57.899> amazing<03:22:58.439> stairs<03:22:58.979> there<03:22:59.160> and 03:23:01.010 --> 03:23:01.020 align:start position:0% my amazing stairs there and 03:23:01.020 --> 03:23:04.969 align:start position:0% my amazing stairs there and you're<03:23:01.920> in<03:23:02.340> the<03:23:02.580> uh<03:23:02.939> first<03:23:03.359> floor<03:23:03.779> I<03:23:04.560> know<03:23:04.740> you 03:23:04.969 --> 03:23:04.979 align:start position:0% you're in the uh first floor I know you 03:23:04.979 --> 03:23:06.590 align:start position:0% you're in the uh first floor I know you I<03:23:05.220> think<03:23:05.399> you<03:23:05.580> don't<03:23:05.700> have<03:23:05.880> a<03:23:06.000> ground<03:23:06.120> floor<03:23:06.359> in 03:23:06.590 --> 03:23:06.600 align:start position:0% I think you don't have a ground floor in 03:23:06.600 --> 03:23:08.150 align:start position:0% I think you don't have a ground floor in America<03:23:06.779> maybe<03:23:07.080> the<03:23:07.380> first<03:23:07.560> floor<03:23:07.800> it's 03:23:08.150 --> 03:23:08.160 align:start position:0% America maybe the first floor it's 03:23:08.160 --> 03:23:09.889 align:start position:0% America maybe the first floor it's called<03:23:08.340> the<03:23:08.460> first<03:23:08.700> floor<03:23:08.939> but<03:23:09.479> on<03:23:09.660> the<03:23:09.779> ground 03:23:09.889 --> 03:23:09.899 align:start position:0% called the first floor but on the ground 03:23:09.899 --> 03:23:11.570 align:start position:0% called the first floor but on the ground in<03:23:10.140> the<03:23:10.260> UK<03:23:10.500> we<03:23:10.680> call<03:23:10.800> it<03:23:10.920> ground<03:23:11.100> floor<03:23:11.340> and 03:23:11.570 --> 03:23:11.580 align:start position:0% in the UK we call it ground floor and 03:23:11.580 --> 03:23:13.729 align:start position:0% in the UK we call it ground floor and then<03:23:11.700> first<03:23:11.880> and<03:23:12.120> so<03:23:12.300> on<03:23:12.420> what<03:23:13.260> you<03:23:13.439> don't<03:23:13.560> want 03:23:13.729 --> 03:23:13.739 align:start position:0% then first and so on what you don't want 03:23:13.739 --> 03:23:16.910 align:start position:0% then first and so on what you don't want to<03:23:13.859> have<03:23:13.979> to<03:23:14.100> do<03:23:14.340> is<03:23:14.819> reassociate<03:23:15.720> with<03:23:16.319> a<03:23:16.620> new 03:23:16.910 --> 03:23:16.920 align:start position:0% to have to do is reassociate with a new 03:23:16.920 --> 03:23:19.610 align:start position:0% to have to do is reassociate with a new uh<03:23:17.760> controller<03:23:18.239> so<03:23:18.540> basically<03:23:18.899> you'd<03:23:19.200> have<03:23:19.380> to 03:23:19.610 --> 03:23:19.620 align:start position:0% uh controller so basically you'd have to 03:23:19.620 --> 03:23:21.650 align:start position:0% uh controller so basically you'd have to connect<03:23:20.460> to 03:23:21.650 --> 03:23:21.660 align:start position:0% connect to 03:23:21.660 --> 03:23:22.729 align:start position:0% connect to um 03:23:22.729 --> 03:23:22.739 align:start position:0% um 03:23:22.739 --> 03:23:25.370 align:start position:0% um wireless<03:23:23.700> network<03:23:24.180> one<03:23:24.779> and<03:23:25.140> wireless 03:23:25.370 --> 03:23:25.380 align:start position:0% wireless network one and wireless 03:23:25.380 --> 03:23:27.469 align:start position:0% wireless network one and wireless network<03:23:25.800> too<03:23:26.220> you<03:23:26.700> don't<03:23:26.819> really<03:23:26.939> want<03:23:27.239> that 03:23:27.469 --> 03:23:27.479 align:start position:0% network too you don't really want that 03:23:27.479 --> 03:23:29.210 align:start position:0% network too you don't really want that you<03:23:27.899> want<03:23:28.020> to<03:23:28.200> go<03:23:28.319> in 03:23:29.210 --> 03:23:29.220 align:start position:0% you want to go in 03:23:29.220 --> 03:23:32.090 align:start position:0% you want to go in connect<03:23:30.000> to<03:23:30.239> their<03:23:30.420> free<03:23:30.660> wireless<03:23:30.960> and<03:23:31.920> then 03:23:32.090 --> 03:23:32.100 align:start position:0% connect to their free wireless and then 03:23:32.100 --> 03:23:33.070 align:start position:0% connect to their free wireless and then keep 03:23:33.070 --> 03:23:33.080 align:start position:0% keep 03:23:33.080 --> 03:23:39.070 align:start position:0% keep your<03:23:34.080> IP<03:23:34.439> address<03:23:34.620> so 03:23:39.070 --> 03:23:39.080 align:start position:0% 03:23:39.080 --> 03:23:41.750 align:start position:0% 172.168.1.1<03:23:40.080> so<03:23:40.620> keep<03:23:40.859> it<03:23:41.040> as<03:23:41.160> you're<03:23:41.340> roaming 03:23:41.750 --> 03:23:41.760 align:start position:0% 172.168.1.1 so keep it as you're roaming 03:23:41.760 --> 03:23:43.010 align:start position:0% 172.168.1.1 so keep it as you're roaming around<03:23:41.939> the<03:23:42.239> building 03:23:43.010 --> 03:23:43.020 align:start position:0% around the building 03:23:43.020 --> 03:23:44.690 align:start position:0% around the building if<03:23:43.560> you're<03:23:43.680> just<03:23:43.920> using<03:23:44.100> lightweight<03:23:44.460> access 03:23:44.690 --> 03:23:44.700 align:start position:0% if you're just using lightweight access 03:23:44.700 --> 03:23:47.090 align:start position:0% if you're just using lightweight access points<03:23:45.359> then<03:23:46.020> you<03:23:46.439> would<03:23:46.560> have<03:23:46.680> to<03:23:46.800> just<03:23:46.920> keep 03:23:47.090 --> 03:23:47.100 align:start position:0% points then you would have to just keep 03:23:47.100 --> 03:23:49.610 align:start position:0% points then you would have to just keep reassociating<03:23:47.880> which<03:23:48.660> in<03:23:48.960> this<03:23:49.140> day<03:23:49.319> and<03:23:49.439> age 03:23:49.610 --> 03:23:49.620 align:start position:0% reassociating which in this day and age 03:23:49.620 --> 03:23:51.769 align:start position:0% reassociating which in this day and age is<03:23:49.800> obviously<03:23:50.160> a<03:23:50.340> pain<03:23:50.520> because<03:23:50.819> we're<03:23:51.300> so 03:23:51.769 --> 03:23:51.779 align:start position:0% is obviously a pain because we're so 03:23:51.779 --> 03:23:54.349 align:start position:0% is obviously a pain because we're so lazy<03:23:52.620> so<03:23:52.979> I've<03:23:53.100> mentioned<03:23:53.460> intra<03:23:53.819> controller 03:23:54.349 --> 03:23:54.359 align:start position:0% lazy so I've mentioned intra controller 03:23:54.359 --> 03:23:56.210 align:start position:0% lazy so I've mentioned intra controller and<03:23:54.540> Inter<03:23:54.840> controller<03:23:55.560> you<03:23:55.739> can<03:23:55.859> see<03:23:55.920> in<03:23:56.040> the 03:23:56.210 --> 03:23:56.220 align:start position:0% and Inter controller you can see in the 03:23:56.220 --> 03:23:58.790 align:start position:0% and Inter controller you can see in the diagrams<03:23:56.640> there 03:23:58.790 --> 03:23:58.800 align:start position:0% diagrams there 03:23:58.800 --> 03:24:01.610 align:start position:0% diagrams there the<03:23:59.520> load<03:23:59.880> balancer 03:24:01.610 --> 03:24:01.620 align:start position:0% the load balancer 03:24:01.620 --> 03:24:04.250 align:start position:0% the load balancer so<03:24:02.040> this<03:24:02.340> distributes<03:24:03.120> incoming<03:24:03.720> requests 03:24:04.250 --> 03:24:04.260 align:start position:0% so this distributes incoming requests 03:24:04.260 --> 03:24:07.370 align:start position:0% so this distributes incoming requests between<03:24:04.560> two<03:24:05.100> or<03:24:05.279> more<03:24:05.460> devices<03:24:05.880> so<03:24:06.779> your<03:24:07.080> this 03:24:07.370 --> 03:24:07.380 align:start position:0% between two or more devices so your this 03:24:07.380 --> 03:24:14.750 align:start position:0% between two or more devices so your this is<03:24:07.560> trans<03:24:07.920> this<03:24:08.520> will<03:24:08.700> be<03:24:08.819> transparent 03:24:14.750 --> 03:24:14.760 align:start position:0% 03:24:14.760 --> 03:24:19.490 align:start position:0% so<03:24:15.420> what<03:24:15.720> your<03:24:15.960> clients<03:24:16.439> think<03:24:16.739> is<03:24:17.040> happening 03:24:19.490 --> 03:24:19.500 align:start position:0% so what your clients think is happening 03:24:19.500 --> 03:24:24.290 align:start position:0% so what your clients think is happening is<03:24:20.880> basically<03:24:21.660> it<03:24:22.200> thinks<03:24:22.979> this<03:24:23.760> is<03:24:23.939> happening 03:24:24.290 --> 03:24:24.300 align:start position:0% is basically it thinks this is happening 03:24:24.300 --> 03:24:26.269 align:start position:0% is basically it thinks this is happening it<03:24:24.720> doesn't<03:24:24.840> realize<03:24:25.260> that<03:24:25.560> this<03:24:25.739> device<03:24:25.920> is 03:24:26.269 --> 03:24:26.279 align:start position:0% it doesn't realize that this device is 03:24:26.279 --> 03:24:28.670 align:start position:0% it doesn't realize that this device is here<03:24:26.580> which<03:24:27.420> is<03:24:27.600> fine<03:24:27.779> by<03:24:28.020> us<03:24:28.200> as<03:24:28.439> Network 03:24:28.670 --> 03:24:28.680 align:start position:0% here which is fine by us as Network 03:24:28.680 --> 03:24:31.130 align:start position:0% here which is fine by us as Network Engineers<03:24:29.220> will<03:24:29.520> will<03:24:29.760> take<03:24:30.000> care<03:24:30.180> of<03:24:30.300> that 03:24:31.130 --> 03:24:31.140 align:start position:0% Engineers will will take care of that 03:24:31.140 --> 03:24:33.290 align:start position:0% Engineers will will take care of that and<03:24:31.500> what<03:24:31.620> it<03:24:31.800> will<03:24:31.920> do<03:24:32.100> is<03:24:32.340> balance<03:24:32.819> so<03:24:33.060> it 03:24:33.290 --> 03:24:33.300 align:start position:0% and what it will do is balance so it 03:24:33.300 --> 03:24:35.450 align:start position:0% and what it will do is balance so it will<03:24:33.420> take<03:24:33.779> uh<03:24:34.319> the<03:24:34.560> say<03:24:35.100> the<03:24:35.340> first 03:24:35.450 --> 03:24:35.460 align:start position:0% will take uh the say the first 03:24:35.460 --> 03:24:38.030 align:start position:0% will take uh the say the first connection<03:24:35.700> here 03:24:38.030 --> 03:24:38.040 align:start position:0% connection here 03:24:38.040 --> 03:24:40.250 align:start position:0% connection here and<03:24:38.700> then<03:24:38.880> oh<03:24:39.300> no<03:24:39.540> this<03:24:39.779> is<03:24:39.840> getting<03:24:40.020> really 03:24:40.250 --> 03:24:40.260 align:start position:0% and then oh no this is getting really 03:24:40.260 --> 03:24:41.510 align:start position:0% and then oh no this is getting really bad<03:24:40.439> now 03:24:41.510 --> 03:24:41.520 align:start position:0% bad now 03:24:41.520 --> 03:24:45.590 align:start position:0% bad now it<03:24:42.060> will<03:24:42.180> log<03:24:42.540> internally<03:24:43.580> here<03:24:44.580> and<03:24:45.420> then 03:24:45.590 --> 03:24:45.600 align:start position:0% it will log internally here and then 03:24:45.600 --> 03:24:46.849 align:start position:0% it will log internally here and then this<03:24:45.960> could<03:24:46.140> be 03:24:46.849 --> 03:24:46.859 align:start position:0% this could be 03:24:46.859 --> 03:24:50.389 align:start position:0% this could be a<03:24:47.460> network<03:24:47.700> or<03:24:48.060> just<03:24:48.239> the<03:24:48.420> device 03:24:50.389 --> 03:24:50.399 align:start position:0% a network or just the device 03:24:50.399 --> 03:24:52.130 align:start position:0% a network or just the device third<03:24:50.939> connection<03:24:51.239> here<03:24:51.660> and<03:24:51.840> it<03:24:52.020> will 03:24:52.130 --> 03:24:52.140 align:start position:0% third connection here and it will 03:24:52.140 --> 03:24:53.809 align:start position:0% third connection here and it will balance 03:24:53.809 --> 03:24:53.819 align:start position:0% balance 03:24:53.819 --> 03:24:55.729 align:start position:0% balance and<03:24:54.420> you<03:24:54.660> don't<03:24:54.720> have<03:24:54.899> a<03:24:55.140> single<03:24:55.380> point<03:24:55.500> of 03:24:55.729 --> 03:24:55.739 align:start position:0% and you don't have a single point of 03:24:55.739 --> 03:24:57.710 align:start position:0% and you don't have a single point of failure<03:24:56.220> so<03:24:56.520> your<03:24:56.880> third<03:24:57.000> connection<03:24:57.180> goes 03:24:57.710 --> 03:24:57.720 align:start position:0% failure so your third connection goes 03:24:57.720 --> 03:25:03.410 align:start position:0% failure so your third connection goes here<03:24:57.899> this<03:24:58.739> load<03:24:59.279> hits<03:25:00.239> uh<03:25:01.200> say<03:25:01.439> 90<03:25:01.859> percent 03:25:03.410 --> 03:25:03.420 align:start position:0% here this load hits uh say 90 percent 03:25:03.420 --> 03:25:05.570 align:start position:0% here this load hits uh say 90 percent but<03:25:04.020> this<03:25:04.260> server<03:25:04.680> it<03:25:04.979> could<03:25:05.100> be<03:25:05.220> a<03:25:05.340> higher 03:25:05.570 --> 03:25:05.580 align:start position:0% but this server it could be a higher 03:25:05.580 --> 03:25:07.250 align:start position:0% but this server it could be a higher powered<03:25:05.939> server<03:25:06.239> it<03:25:06.600> doesn't<03:25:06.720> have<03:25:06.899> to<03:25:07.020> be<03:25:07.140> the 03:25:07.250 --> 03:25:07.260 align:start position:0% powered server it doesn't have to be the 03:25:07.260 --> 03:25:09.410 align:start position:0% powered server it doesn't have to be the same<03:25:07.439> this<03:25:08.160> is<03:25:08.279> only<03:25:08.460> sitting<03:25:08.880> at<03:25:09.060> twenty 03:25:09.410 --> 03:25:09.420 align:start position:0% same this is only sitting at twenty 03:25:09.420 --> 03:25:10.309 align:start position:0% same this is only sitting at twenty percent 03:25:10.309 --> 03:25:10.319 align:start position:0% percent 03:25:10.319 --> 03:25:12.410 align:start position:0% percent then<03:25:10.739> it<03:25:10.920> will<03:25:11.100> route<03:25:11.340> more<03:25:11.880> of<03:25:12.060> the<03:25:12.239> traffic 03:25:12.410 --> 03:25:12.420 align:start position:0% then it will route more of the traffic 03:25:12.420 --> 03:25:14.870 align:start position:0% then it will route more of the traffic to<03:25:12.779> here<03:25:13.020> if<03:25:13.800> this<03:25:13.979> goes<03:25:14.279> down<03:25:14.460> for<03:25:14.700> whatever 03:25:14.870 --> 03:25:14.880 align:start position:0% to here if this goes down for whatever 03:25:14.880 --> 03:25:17.389 align:start position:0% to here if this goes down for whatever reason<03:25:15.319> transparent<03:25:16.319> to<03:25:16.500> all<03:25:16.620> the<03:25:16.800> end<03:25:16.920> hosts 03:25:17.389 --> 03:25:17.399 align:start position:0% reason transparent to all the end hosts 03:25:17.399 --> 03:25:20.870 align:start position:0% reason transparent to all the end hosts it<03:25:17.880> will<03:25:18.000> load<03:25:18.300> balance<03:25:18.600> between<03:25:18.899> these<03:25:19.380> two 03:25:20.870 --> 03:25:20.880 align:start position:0% it will load balance between these two 03:25:20.880 --> 03:25:24.290 align:start position:0% it will load balance between these two and<03:25:21.540> you<03:25:22.020> can<03:25:22.439> um<03:25:22.439> you<03:25:22.859> could<03:25:22.979> be<03:25:23.640> routing 03:25:24.290 --> 03:25:24.300 align:start position:0% and you can um you could be routing 03:25:24.300 --> 03:25:25.610 align:start position:0% and you can um you could be routing between<03:25:24.479> different<03:25:24.779> devices<03:25:25.200> it<03:25:25.500> doesn't 03:25:25.610 --> 03:25:25.620 align:start position:0% between different devices it doesn't 03:25:25.620 --> 03:25:28.729 align:start position:0% between different devices it doesn't have<03:25:25.800> to<03:25:25.920> be<03:25:26.040> servers 03:25:28.729 --> 03:25:28.739 align:start position:0% have to be servers 03:25:28.739 --> 03:25:31.010 align:start position:0% have to be servers so<03:25:29.279> you<03:25:29.580> can<03:25:29.700> balance<03:25:29.939> web<03:25:30.180> traffic<03:25:30.420> streaming 03:25:31.010 --> 03:25:31.020 align:start position:0% so you can balance web traffic streaming 03:25:31.020 --> 03:25:33.650 align:start position:0% so you can balance web traffic streaming videos<03:25:31.399> databases<03:25:32.399> whatever<03:25:32.700> you<03:25:33.060> so<03:25:33.359> wish 03:25:33.650 --> 03:25:33.660 align:start position:0% videos databases whatever you so wish 03:25:33.660 --> 03:25:37.190 align:start position:0% videos databases whatever you so wish now<03:25:34.560> the<03:25:34.920> IP<03:25:35.220> address<03:25:35.479> is<03:25:36.479> actually<03:25:36.660> sitting 03:25:37.190 --> 03:25:37.200 align:start position:0% now the IP address is actually sitting 03:25:37.200 --> 03:25:38.510 align:start position:0% now the IP address is actually sitting on<03:25:37.620> here 03:25:38.510 --> 03:25:38.520 align:start position:0% on here 03:25:38.520 --> 03:25:43.370 align:start position:0% on here so<03:25:38.939> say<03:25:39.359> uh<03:25:40.140> 12.1.1.1 03:25:43.370 --> 03:25:43.380 align:start position:0% 03:25:43.380 --> 03:25:46.010 align:start position:0% and<03:25:44.160> then<03:25:44.640> these<03:25:44.939> will<03:25:45.120> have<03:25:45.359> probably<03:25:45.720> have 03:25:46.010 --> 03:25:46.020 align:start position:0% and then these will have probably have 03:25:46.020 --> 03:25:50.269 align:start position:0% and then these will have probably have non-routable<03:25:46.800> addresses<03:25:47.399> so<03:25:48.020> RFC<03:25:49.279> 1918 03:25:50.269 --> 03:25:50.279 align:start position:0% non-routable addresses so RFC 1918 03:25:50.279 --> 03:25:53.110 align:start position:0% non-routable addresses so RFC 1918 addresses<03:25:51.000> which<03:25:51.239> is 03:25:53.110 --> 03:25:53.120 align:start position:0% addresses which is 03:25:53.120 --> 03:25:56.030 align:start position:0% addresses which is whatever<03:25:54.120> you<03:25:54.479> know<03:25:54.600> the<03:25:54.779> the 03:25:56.030 --> 03:25:56.040 align:start position:0% whatever you know the the 03:25:56.040 --> 03:25:58.370 align:start position:0% whatever you know the the private<03:25:56.580> IP<03:25:56.939> address<03:25:57.120> is 03:25:58.370 --> 03:25:58.380 align:start position:0% private IP address is 03:25:58.380 --> 03:25:59.990 align:start position:0% private IP address is but<03:25:58.859> we<03:25:59.100> won't<03:25:59.220> care<03:25:59.399> about<03:25:59.580> that<03:25:59.819> as 03:25:59.990 --> 03:26:00.000 align:start position:0% but we won't care about that as 03:26:00.000 --> 03:26:04.550 align:start position:0% but we won't care about that as customers<03:26:00.620> moving<03:26:01.620> on<03:26:01.880> IDs<03:26:02.880> and<03:26:03.060> IPS 03:26:04.550 --> 03:26:04.560 align:start position:0% customers moving on IDs and IPS 03:26:04.560 --> 03:26:06.950 align:start position:0% customers moving on IDs and IPS uh<03:26:05.040> Cisco<03:26:05.399> Market<03:26:05.640> leaders<03:26:06.180> in<03:26:06.420> this<03:26:06.720> type<03:26:06.840> of 03:26:06.950 --> 03:26:06.960 align:start position:0% uh Cisco Market leaders in this type of 03:26:06.960 --> 03:26:08.510 align:start position:0% uh Cisco Market leaders in this type of equipment 03:26:08.510 --> 03:26:08.520 align:start position:0% equipment 03:26:08.520 --> 03:26:10.929 align:start position:0% equipment uh<03:26:09.060> I<03:26:09.120> can't<03:26:09.239> see<03:26:09.420> what<03:26:09.540> the<03:26:09.660> model<03:26:09.779> number<03:26:10.020> is 03:26:10.929 --> 03:26:10.939 align:start position:0% uh I can't see what the model number is 03:26:10.939 --> 03:26:14.330 align:start position:0% uh I can't see what the model number is 4240.<03:26:11.939> always<03:26:12.420> great<03:26:12.779> to<03:26:13.020> serve<03:26:13.859> the<03:26:14.040> sales 03:26:14.330 --> 03:26:14.340 align:start position:0% 4240. always great to serve the sales 03:26:14.340 --> 03:26:17.389 align:start position:0% 4240. always great to serve the sales pages<03:26:15.000> for<03:26:15.359> all<03:26:15.600> of<03:26:15.720> these<03:26:16.020> vendors 03:26:17.389 --> 03:26:17.399 align:start position:0% pages for all of these vendors 03:26:17.399 --> 03:26:20.690 align:start position:0% pages for all of these vendors uh<03:26:18.239> Cisco<03:26:18.779> and<03:26:19.080> Juniper<03:26:19.859> and<03:26:20.040> whoever<03:26:20.340> because 03:26:20.690 --> 03:26:20.700 align:start position:0% uh Cisco and Juniper and whoever because 03:26:20.700 --> 03:26:22.070 align:start position:0% uh Cisco and Juniper and whoever because it<03:26:20.880> gives<03:26:21.000> you<03:26:21.120> lots<03:26:21.420> of<03:26:21.540> useful 03:26:22.070 --> 03:26:22.080 align:start position:0% it gives you lots of useful 03:26:22.080 --> 03:26:23.510 align:start position:0% it gives you lots of useful documentation<03:26:22.680> you<03:26:23.100> can<03:26:23.220> see<03:26:23.340> what's 03:26:23.510 --> 03:26:23.520 align:start position:0% documentation you can see what's 03:26:23.520 --> 03:26:24.530 align:start position:0% documentation you can see what's available 03:26:24.530 --> 03:26:24.540 align:start position:0% available 03:26:24.540 --> 03:26:26.570 align:start position:0% available now<03:26:25.080> both<03:26:25.260> of<03:26:25.439> these<03:26:25.620> do<03:26:25.800> the<03:26:25.979> same<03:26:26.100> job<03:26:26.340> they 03:26:26.570 --> 03:26:26.580 align:start position:0% now both of these do the same job they 03:26:26.580 --> 03:26:29.210 align:start position:0% now both of these do the same job they inspect<03:26:26.880> traffic<03:26:27.180> to<03:26:28.020> detect<03:26:28.319> unauthorized 03:26:29.210 --> 03:26:29.220 align:start position:0% inspect traffic to detect unauthorized 03:26:29.220 --> 03:26:30.349 align:start position:0% inspect traffic to detect unauthorized access 03:26:30.349 --> 03:26:30.359 align:start position:0% access 03:26:30.359 --> 03:26:32.210 align:start position:0% access and<03:26:30.779> monitors<03:26:31.140> the<03:26:31.319> network<03:26:31.500> for<03:26:31.800> intrusions 03:26:32.210 --> 03:26:32.220 align:start position:0% and monitors the network for intrusions 03:26:32.220 --> 03:26:34.849 align:start position:0% and monitors the network for intrusions or<03:26:32.460> malicious<03:26:32.819> activities<03:26:33.300> now<03:26:34.260> what<03:26:34.560> it<03:26:34.739> can 03:26:34.849 --> 03:26:34.859 align:start position:0% or malicious activities now what it can 03:26:34.859 --> 03:26:38.389 align:start position:0% or malicious activities now what it can do<03:26:35.040> is<03:26:35.520> send<03:26:36.180> an<03:26:36.359> alert<03:26:36.779> which<03:26:37.620> is 03:26:38.389 --> 03:26:38.399 align:start position:0% do is send an alert which is 03:26:38.399 --> 03:26:41.630 align:start position:0% do is send an alert which is um<03:26:38.460> oh<03:26:38.760> no<03:26:39.000> I'm<03:26:39.420> gonna<03:26:39.540> have<03:26:39.660> to<03:26:39.779> draw<03:26:40.020> a 03:26:41.630 --> 03:26:41.640 align:start position:0% um oh no I'm gonna have to draw a 03:26:41.640 --> 03:26:44.570 align:start position:0% um oh no I'm gonna have to draw a this<03:26:42.120> is<03:26:42.239> actually<03:26:42.420> a<03:26:43.200> a<03:26:43.500> telephone<03:26:43.739> I<03:26:44.220> hope 03:26:44.570 --> 03:26:44.580 align:start position:0% this is actually a a telephone I hope 03:26:44.580 --> 03:26:46.250 align:start position:0% this is actually a a telephone I hope you<03:26:44.700> impress<03:26:45.140> old-fashioned<03:26:46.140> telephone 03:26:46.250 --> 03:26:46.260 align:start position:0% you impress old-fashioned telephone 03:26:46.260 --> 03:26:48.650 align:start position:0% you impress old-fashioned telephone there<03:26:46.739> if<03:26:47.040> you<03:26:47.160> recognize<03:26:47.520> that<03:26:47.760> then<03:26:48.060> you're 03:26:48.650 --> 03:26:48.660 align:start position:0% there if you recognize that then you're 03:26:48.660 --> 03:26:51.650 align:start position:0% there if you recognize that then you're officially<03:26:49.020> old<03:26:49.340> so<03:26:50.340> you<03:26:50.520> could<03:26:50.700> send<03:26:51.420> a 03:26:51.650 --> 03:26:51.660 align:start position:0% officially old so you could send a 03:26:51.660 --> 03:26:55.510 align:start position:0% officially old so you could send a message<03:26:52.380> to<03:26:52.680> your<03:26:52.859> mobile<03:26:53.220> phone<03:26:53.640> it<03:26:54.600> can<03:26:54.840> send 03:26:55.510 --> 03:26:55.520 align:start position:0% message to your mobile phone it can send 03:26:55.520 --> 03:26:59.450 align:start position:0% message to your mobile phone it can send SMS<03:26:56.520> log<03:26:57.479> messages<03:26:57.899> whatever<03:26:58.560> you<03:26:58.800> so<03:26:58.979> wish<03:26:59.220> or 03:26:59.450 --> 03:26:59.460 align:start position:0% SMS log messages whatever you so wish or 03:26:59.460 --> 03:27:02.389 align:start position:0% SMS log messages whatever you so wish or an<03:26:59.580> SNMP<03:27:00.180> trap<03:27:00.600> and<03:27:01.380> that<03:27:01.620> will 03:27:02.389 --> 03:27:02.399 align:start position:0% an SNMP trap and that will 03:27:02.399 --> 03:27:04.010 align:start position:0% an SNMP trap and that will um<03:27:02.460> it<03:27:02.760> could<03:27:02.880> shut<03:27:03.060> down<03:27:03.239> a<03:27:03.479> port<03:27:03.660> or<03:27:03.899> whatever 03:27:04.010 --> 03:27:04.020 align:start position:0% um it could shut down a port or whatever 03:27:04.020 --> 03:27:06.530 align:start position:0% um it could shut down a port or whatever you<03:27:04.260> instruct<03:27:04.560> it<03:27:04.859> to<03:27:05.040> do 03:27:06.530 --> 03:27:06.540 align:start position:0% you instruct it to do 03:27:06.540 --> 03:27:09.410 align:start position:0% you instruct it to do now<03:27:07.080> IPS<03:27:07.500> Works<03:27:08.160> in<03:27:08.460> line<03:27:08.640> so<03:27:08.880> it's<03:27:09.060> placed<03:27:09.359> in 03:27:09.410 --> 03:27:09.420 align:start position:0% now IPS Works in line so it's placed in 03:27:09.420 --> 03:27:12.729 align:start position:0% now IPS Works in line so it's placed in the<03:27:09.540> traffic<03:27:09.720> flow<03:27:10.140> so<03:27:10.319> you've<03:27:10.560> got<03:27:10.739> internet 03:27:12.729 --> 03:27:12.739 align:start position:0% the traffic flow so you've got internet 03:27:12.739 --> 03:27:16.610 align:start position:0% the traffic flow so you've got internet and<03:27:13.739> I'll<03:27:14.220> stick<03:27:14.580> it<03:27:14.700> here<03:27:14.880> actually 03:27:16.610 --> 03:27:16.620 align:start position:0% and I'll stick it here actually 03:27:16.620 --> 03:27:20.210 align:start position:0% and I'll stick it here actually your<03:27:17.279> IPS<03:27:18.080> and<03:27:19.080> then<03:27:19.200> that<03:27:19.380> will<03:27:19.500> go<03:27:19.680> off<03:27:19.859> to 03:27:20.210 --> 03:27:20.220 align:start position:0% your IPS and then that will go off to 03:27:20.220 --> 03:27:21.530 align:start position:0% your IPS and then that will go off to your 03:27:21.530 --> 03:27:21.540 align:start position:0% your 03:27:21.540 --> 03:27:23.410 align:start position:0% your router 03:27:23.410 --> 03:27:23.420 align:start position:0% router 03:27:23.420 --> 03:27:27.769 align:start position:0% router switch<03:27:24.620> and<03:27:25.620> then<03:27:25.800> your<03:27:26.279> your<03:27:26.760> hosts<03:27:27.420> here 03:27:27.769 --> 03:27:27.779 align:start position:0% switch and then your your hosts here 03:27:27.779 --> 03:27:31.429 align:start position:0% switch and then your your hosts here however<03:27:28.439> many<03:27:28.620> hosts<03:27:29.040> you've<03:27:29.220> got 03:27:31.429 --> 03:27:31.439 align:start position:0% 03:27:31.439 --> 03:27:33.590 align:start position:0% and<03:27:31.739> I<03:27:31.979> don't<03:27:32.100> give<03:27:32.220> up<03:27:32.340> your<03:27:32.520> day<03:27:32.640> job<03:27:32.880> so<03:27:33.359> this 03:27:33.590 --> 03:27:33.600 align:start position:0% and I don't give up your day job so this 03:27:33.600 --> 03:27:35.210 align:start position:0% and I don't give up your day job so this is<03:27:33.720> in<03:27:34.020> line<03:27:34.200> your<03:27:34.560> traffic<03:27:34.739> will<03:27:35.040> come 03:27:35.210 --> 03:27:35.220 align:start position:0% is in line your traffic will come 03:27:35.220 --> 03:27:37.670 align:start position:0% is in line your traffic will come through<03:27:35.399> here<03:27:35.640> it'll<03:27:36.000> be<03:27:36.120> inspected<03:27:36.720> and<03:27:37.560> then 03:27:37.670 --> 03:27:37.680 align:start position:0% through here it'll be inspected and then 03:27:37.680 --> 03:27:42.889 align:start position:0% through here it'll be inspected and then go<03:27:37.979> to<03:27:38.100> your<03:27:38.279> end<03:27:38.460> device<03:27:38.960> the<03:27:40.040> IDS<03:27:41.180> is<03:27:42.180> not<03:27:42.600> in 03:27:42.889 --> 03:27:42.899 align:start position:0% go to your end device the IDS is not in 03:27:42.899 --> 03:27:44.030 align:start position:0% go to your end device the IDS is not in line 03:27:44.030 --> 03:27:44.040 align:start position:0% line 03:27:44.040 --> 03:27:48.650 align:start position:0% line so<03:27:44.640> what<03:27:44.819> will<03:27:44.939> happen<03:27:45.180> is<03:27:45.540> router 03:27:48.650 --> 03:27:48.660 align:start position:0% 03:27:48.660 --> 03:27:53.389 align:start position:0% switch 03:27:53.389 --> 03:27:53.399 align:start position:0% 03:27:53.399 --> 03:27:56.570 align:start position:0% host<03:27:54.060> and<03:27:54.660> it<03:27:54.840> can<03:27:54.960> be<03:27:55.080> put<03:27:55.260> here<03:27:55.620> or<03:27:56.040> here<03:27:56.340> I'll 03:27:56.570 --> 03:27:56.580 align:start position:0% host and it can be put here or here I'll 03:27:56.580 --> 03:27:59.929 align:start position:0% host and it can be put here or here I'll say<03:27:56.760> there's<03:27:56.939> an<03:27:57.060> ethernet<03:27:57.359> connection<03:27:57.660> here 03:27:59.929 --> 03:27:59.939 align:start position:0% say there's an ethernet connection here 03:27:59.939 --> 03:28:03.170 align:start position:0% say there's an ethernet connection here now<03:28:00.479> your<03:28:00.720> IDs<03:28:01.439> receives<03:28:02.340> a<03:28:02.520> copy<03:28:02.819> of<03:28:03.000> the 03:28:03.170 --> 03:28:03.180 align:start position:0% now your IDs receives a copy of the 03:28:03.180 --> 03:28:07.309 align:start position:0% now your IDs receives a copy of the frame<03:28:03.479> so<03:28:04.080> the<03:28:04.319> frame<03:28:04.680> I'll<03:28:05.520> call<03:28:05.700> it<03:28:05.880> frame 03:28:07.309 --> 03:28:07.319 align:start position:0% frame so the frame I'll call it frame 03:28:07.319 --> 03:28:09.590 align:start position:0% frame so the frame I'll call it frame um<03:28:07.439> frame<03:28:08.100> y 03:28:09.590 --> 03:28:09.600 align:start position:0% um frame y 03:28:09.600 --> 03:28:10.910 align:start position:0% um frame y and<03:28:10.140> then 03:28:10.910 --> 03:28:10.920 align:start position:0% and then 03:28:10.920 --> 03:28:13.969 align:start position:0% and then that<03:28:11.399> is<03:28:11.520> just<03:28:11.700> a<03:28:11.819> copy<03:28:12.120> because<03:28:12.359> frame<03:28:12.960> Y<03:28:13.260> is 03:28:13.969 --> 03:28:13.979 align:start position:0% that is just a copy because frame Y is 03:28:13.979 --> 03:28:16.849 align:start position:0% that is just a copy because frame Y is actually<03:28:14.220> being<03:28:14.580> passed<03:28:15.180> through<03:28:15.779> to<03:28:16.500> your 03:28:16.849 --> 03:28:16.859 align:start position:0% actually being passed through to your 03:28:16.859 --> 03:28:18.650 align:start position:0% actually being passed through to your switch<03:28:17.100> obviously<03:28:17.880> you<03:28:18.000> can<03:28:18.120> see<03:28:18.239> the<03:28:18.479> problem 03:28:18.650 --> 03:28:18.660 align:start position:0% switch obviously you can see the problem 03:28:18.660 --> 03:28:21.229 align:start position:0% switch obviously you can see the problem here<03:28:19.080> is<03:28:19.439> receiving<03:28:19.800> a<03:28:20.040> copy<03:28:20.399> but<03:28:21.060> this 03:28:21.229 --> 03:28:21.239 align:start position:0% here is receiving a copy but this 03:28:21.239 --> 03:28:23.269 align:start position:0% here is receiving a copy but this traffic<03:28:21.420> is<03:28:21.779> actually<03:28:21.960> going<03:28:22.319> through<03:28:22.620> your 03:28:23.269 --> 03:28:23.279 align:start position:0% traffic is actually going through your 03:28:23.279 --> 03:28:24.950 align:start position:0% traffic is actually going through your network<03:28:23.460> so 03:28:24.950 --> 03:28:24.960 align:start position:0% network so 03:28:24.960 --> 03:28:29.030 align:start position:0% network so these<03:28:25.859> are<03:28:25.979> less<03:28:26.100> common<03:28:26.340> now<03:28:26.580> the<03:28:26.760> RDS<03:28:27.180> is 03:28:29.030 --> 03:28:29.040 align:start position:0% these are less common now the RDS is 03:28:29.040 --> 03:28:31.790 align:start position:0% these are less common now the RDS is I'm<03:28:29.520> going<03:28:29.819> to<03:28:29.880> talk<03:28:30.000> about<03:28:30.180> these<03:28:30.660> later<03:28:31.200> in 03:28:31.790 --> 03:28:31.800 align:start position:0% I'm going to talk about these later in 03:28:31.800 --> 03:28:35.690 align:start position:0% I'm going to talk about these later in the<03:28:31.979> security<03:28:32.100> sections<03:28:32.760> AAA<03:28:33.420> or<03:28:33.899> radius<03:28:34.700> and 03:28:35.690 --> 03:28:35.700 align:start position:0% the security sections AAA or radius and 03:28:35.700 --> 03:28:38.450 align:start position:0% the security sections AAA or radius and used<03:28:36.300> for<03:28:36.479> authentication<03:28:37.080> to<03:28:37.439> validate<03:28:38.279> the 03:28:38.450 --> 03:28:38.460 align:start position:0% used for authentication to validate the 03:28:38.460 --> 03:28:40.670 align:start position:0% used for authentication to validate the identity<03:28:38.880> does<03:28:39.239> a<03:28:39.420> few<03:28:39.540> things<03:28:39.660> actually<03:28:39.960> and 03:28:40.670 --> 03:28:40.680 align:start position:0% identity does a few things actually and 03:28:40.680 --> 03:28:42.410 align:start position:0% identity does a few things actually and um Josh<03:28:40.920> talked<03:28:41.340> about<03:28:41.460> the<03:28:42.239> different 03:28:42.410 --> 03:28:42.420 align:start position:0% um Josh talked about the different 03:28:42.420 --> 03:28:45.710 align:start position:0% um Josh talked about the different aspects<03:28:42.840> of<03:28:42.960> AAA<03:28:43.500> earlier<03:28:44.720> authorization 03:28:45.710 --> 03:28:45.720 align:start position:0% aspects of AAA earlier authorization 03:28:45.720 --> 03:28:48.170 align:start position:0% aspects of AAA earlier authorization determines<03:28:46.380> what<03:28:46.800> you<03:28:46.920> can<03:28:47.100> do<03:28:47.340> and 03:28:48.170 --> 03:28:48.180 align:start position:0% determines what you can do and 03:28:48.180 --> 03:28:50.510 align:start position:0% determines what you can do and accounting<03:28:48.660> is<03:28:48.840> for<03:28:49.020> the<03:28:49.200> audit<03:28:49.620> Trail<03:28:49.859> so 03:28:50.510 --> 03:28:50.520 align:start position:0% accounting is for the audit Trail so 03:28:50.520 --> 03:28:52.370 align:start position:0% accounting is for the audit Trail so this<03:28:51.060> um<03:28:51.120> the<03:28:51.359> accountant<03:28:51.720> will<03:28:51.899> normally<03:28:52.140> go 03:28:52.370 --> 03:28:52.380 align:start position:0% this um the accountant will normally go 03:28:52.380 --> 03:28:54.349 align:start position:0% this um the accountant will normally go off<03:28:52.500> to<03:28:52.800> a<03:28:53.220> server<03:28:53.640> where<03:28:54.120> you<03:28:54.300> can 03:28:54.349 --> 03:28:54.359 align:start position:0% off to a server where you can 03:28:54.359 --> 03:28:57.590 align:start position:0% off to a server where you can interrogate<03:28:55.080> the<03:28:55.800> server<03:28:56.100> logs<03:28:56.600> and 03:28:57.590 --> 03:28:57.600 align:start position:0% interrogate the server logs and 03:28:57.600 --> 03:28:59.630 align:start position:0% interrogate the server logs and sometimes<03:28:57.899> you<03:28:58.080> need<03:28:58.260> to<03:28:58.380> do<03:28:58.560> it<03:28:58.739> for 03:28:59.630 --> 03:28:59.640 align:start position:0% sometimes you need to do it for 03:28:59.640 --> 03:29:04.150 align:start position:0% sometimes you need to do it for um<03:28:59.700> compliance 03:29:04.150 --> 03:29:04.160 align:start position:0% 03:29:04.160 --> 03:29:06.710 align:start position:0% or<03:29:05.520> um 03:29:06.710 --> 03:29:06.720 align:start position:0% or um 03:29:06.720 --> 03:29:08.809 align:start position:0% or um if<03:29:07.200> you're<03:29:07.319> going<03:29:07.500> to<03:29:07.560> legally 03:29:08.809 --> 03:29:08.819 align:start position:0% if you're going to legally 03:29:08.819 --> 03:29:11.690 align:start position:0% if you're going to legally take<03:29:09.359> a<03:29:09.540> case<03:29:09.720> against<03:29:09.960> somebody 03:29:11.690 --> 03:29:11.700 align:start position:0% take a case against somebody 03:29:11.700 --> 03:29:14.030 align:start position:0% take a case against somebody so<03:29:12.239> it's<03:29:12.420> a<03:29:12.600> modular<03:29:12.840> and<03:29:13.080> scalable<03:29:13.439> model<03:29:13.739> for 03:29:14.030 --> 03:29:14.040 align:start position:0% so it's a modular and scalable model for 03:29:14.040 --> 03:29:16.370 align:start position:0% so it's a modular and scalable model for network<03:29:14.279> and<03:29:14.640> device<03:29:14.819> access<03:29:15.180> you<03:29:15.899> can<03:29:16.020> run<03:29:16.200> it 03:29:16.370 --> 03:29:16.380 align:start position:0% network and device access you can run it 03:29:16.380 --> 03:29:19.190 align:start position:0% network and device access you can run it on<03:29:16.560> its<03:29:16.859> own<03:29:16.920> server<03:29:17.540> or<03:29:18.540> certainly<03:29:18.899> in<03:29:19.020> the 03:29:19.190 --> 03:29:19.200 align:start position:0% on its own server or certainly in the 03:29:19.200 --> 03:29:21.950 align:start position:0% on its own server or certainly in the terms<03:29:19.439> of<03:29:19.560> Cisco<03:29:19.979> you<03:29:20.880> can<03:29:21.000> have<03:29:21.300> the<03:29:21.660> server 03:29:21.950 --> 03:29:21.960 align:start position:0% terms of Cisco you can have the server 03:29:21.960 --> 03:29:23.389 align:start position:0% terms of Cisco you can have the server software<03:29:22.260> running<03:29:22.500> on<03:29:22.739> your<03:29:22.920> router<03:29:23.279> and 03:29:23.389 --> 03:29:23.399 align:start position:0% software running on your router and 03:29:23.399 --> 03:29:25.729 align:start position:0% software running on your router and switch<03:29:23.600> probably<03:29:24.600> not<03:29:24.779> recommended<03:29:25.380> because 03:29:25.729 --> 03:29:25.739 align:start position:0% switch probably not recommended because 03:29:25.739 --> 03:29:28.070 align:start position:0% switch probably not recommended because routers<03:29:26.700> are<03:29:26.880> designed<03:29:27.300> specifically<03:29:27.899> to 03:29:28.070 --> 03:29:28.080 align:start position:0% routers are designed specifically to 03:29:28.080 --> 03:29:30.530 align:start position:0% routers are designed specifically to Route<03:29:28.260> traffic 03:29:30.530 --> 03:29:30.540 align:start position:0% Route traffic 03:29:30.540 --> 03:29:33.769 align:start position:0% Route traffic uses<03:29:31.319> radius<03:29:31.680> attack<03:29:31.920> ax<03:29:32.399> plus<03:29:32.640> and<03:29:33.000> curb<03:29:33.420> Ross 03:29:33.769 --> 03:29:33.779 align:start position:0% uses radius attack ax plus and curb Ross 03:29:33.779 --> 03:29:35.750 align:start position:0% uses radius attack ax plus and curb Ross as<03:29:33.899> authentication<03:29:34.439> methods<03:29:35.040> don't<03:29:35.279> I<03:29:35.640> don't 03:29:35.750 --> 03:29:35.760 align:start position:0% as authentication methods don't I don't 03:29:35.760 --> 03:29:37.070 align:start position:0% as authentication methods don't I don't think<03:29:35.880> airbrush<03:29:36.420> is<03:29:36.600> actually<03:29:36.720> in<03:29:36.960> the 03:29:37.070 --> 03:29:37.080 align:start position:0% think airbrush is actually in the 03:29:37.080 --> 03:29:40.670 align:start position:0% think airbrush is actually in the syllabus<03:29:37.500> but<03:29:38.279> I<03:29:38.460> know<03:29:38.640> a<03:29:39.060> radius<03:29:40.020> attack<03:29:40.260> ax 03:29:40.670 --> 03:29:40.680 align:start position:0% syllabus but I know a radius attack ax 03:29:40.680 --> 03:29:43.429 align:start position:0% syllabus but I know a radius attack ax is<03:29:41.340> certainly<03:29:42.060> worth<03:29:42.359> looking<03:29:42.960> at<03:29:43.260> the 03:29:43.429 --> 03:29:43.439 align:start position:0% is certainly worth looking at the 03:29:43.439 --> 03:29:46.190 align:start position:0% is certainly worth looking at the CompTIA<03:29:43.979> Security<03:29:44.220> Plus<03:29:44.640> which<03:29:45.359> we<03:29:45.600> go<03:29:45.960> into<03:29:46.020> a 03:29:46.190 --> 03:29:46.200 align:start position:0% CompTIA Security Plus which we go into a 03:29:46.200 --> 03:29:48.110 align:start position:0% CompTIA Security Plus which we go into a lot<03:29:46.260> more<03:29:46.380> detail<03:29:46.739> in<03:29:46.859> this<03:29:47.040> stuff 03:29:48.110 --> 03:29:48.120 align:start position:0% lot more detail in this stuff 03:29:48.120 --> 03:29:50.510 align:start position:0% lot more detail in this stuff I've<03:29:48.420> already<03:29:48.540> mentioned<03:29:49.020> using<03:29:49.380> the<03:29:49.500> service 03:29:50.510 --> 03:29:50.520 align:start position:0% I've already mentioned using the service 03:29:50.520 --> 03:29:53.570 align:start position:0% I've already mentioned using the service uh<03:29:51.060> UTM<03:29:51.660> is<03:29:51.960> an<03:29:52.140> appliance 03:29:53.570 --> 03:29:53.580 align:start position:0% uh UTM is an appliance 03:29:53.580 --> 03:29:55.790 align:start position:0% uh UTM is an appliance integrates<03:29:54.420> a<03:29:54.720> range<03:29:55.020> of<03:29:55.080> security<03:29:55.319> features 03:29:55.790 --> 03:29:55.800 align:start position:0% integrates a range of security features 03:29:55.800 --> 03:29:58.250 align:start position:0% integrates a range of security features but<03:29:56.040> it<03:29:56.160> does<03:29:56.340> it<03:29:56.460> into<03:29:56.640> a<03:29:57.000> single<03:29:57.239> Appliance<03:29:57.720> a 03:29:58.250 --> 03:29:58.260 align:start position:0% but it does it into a single Appliance a 03:29:58.260 --> 03:30:00.610 align:start position:0% but it does it into a single Appliance a while<03:29:58.439> ago<03:29:58.739> actually<03:29:58.920> I<03:29:59.220> was<03:29:59.340> when<03:29:59.819> I<03:30:00.000> was 03:30:00.610 --> 03:30:00.620 align:start position:0% while ago actually I was when I was 03:30:00.620 --> 03:30:03.250 align:start position:0% while ago actually I was when I was Consulting<03:30:01.620> in<03:30:01.920> the<03:30:02.040> early 03:30:03.250 --> 03:30:03.260 align:start position:0% Consulting in the early 03:30:03.260 --> 03:30:06.889 align:start position:0% Consulting in the early 2003<03:30:04.460> there<03:30:05.460> was<03:30:05.640> one<03:30:06.120> company<03:30:06.300> in<03:30:06.600> particular 03:30:06.889 --> 03:30:06.899 align:start position:0% 2003 there was one company in particular 03:30:06.899 --> 03:30:09.349 align:start position:0% 2003 there was one company in particular brought<03:30:07.439> out<03:30:07.620> everything<03:30:08.100> in<03:30:08.399> a<03:30:08.580> box<03:30:08.760> bearing 03:30:09.349 --> 03:30:09.359 align:start position:0% brought out everything in a box bearing 03:30:09.359 --> 03:30:11.030 align:start position:0% brought out everything in a box bearing in<03:30:09.420> mind<03:30:09.600> the<03:30:09.779> needs<03:30:10.080> weren't<03:30:10.319> as<03:30:10.500> complicated 03:30:11.030 --> 03:30:11.040 align:start position:0% in mind the needs weren't as complicated 03:30:11.040 --> 03:30:14.269 align:start position:0% in mind the needs weren't as complicated back<03:30:11.340> then<03:30:11.580> so<03:30:12.359> this<03:30:12.660> box 03:30:14.269 --> 03:30:14.279 align:start position:0% back then so this box 03:30:14.279 --> 03:30:18.710 align:start position:0% back then so this box let's<03:30:14.819> say<03:30:15.120> boxer<03:30:15.540> server<03:30:15.899> we<03:30:16.500> do<03:30:16.800> your<03:30:17.700> um 03:30:18.710 --> 03:30:18.720 align:start position:0% let's say boxer server we do your um 03:30:18.720 --> 03:30:22.130 align:start position:0% let's say boxer server we do your um email<03:30:19.560> it<03:30:20.100> would<03:30:20.279> do<03:30:20.520> your<03:30:21.060> web 03:30:22.130 --> 03:30:22.140 align:start position:0% email it would do your web 03:30:22.140 --> 03:30:26.510 align:start position:0% email it would do your web it<03:30:22.920> would<03:30:23.160> get<03:30:23.880> you<03:30:24.060> out<03:30:24.420> to<03:30:24.720> the<03:30:25.080> internet<03:30:26.040> as 03:30:26.510 --> 03:30:26.520 align:start position:0% it would get you out to the internet as 03:30:26.520 --> 03:30:29.450 align:start position:0% it would get you out to the internet as well<03:30:26.720> and<03:30:27.720> then<03:30:28.020> it<03:30:28.859> would<03:30:28.979> obviously<03:30:29.279> connect 03:30:29.450 --> 03:30:29.460 align:start position:0% well and then it would obviously connect 03:30:29.460 --> 03:30:30.830 align:start position:0% well and then it would obviously connect off<03:30:29.819> to<03:30:30.060> your 03:30:30.830 --> 03:30:30.840 align:start position:0% off to your 03:30:30.840 --> 03:30:36.130 align:start position:0% off to your switch<03:30:31.939> and<03:30:32.939> I<03:30:33.120> think<03:30:33.359> it<03:30:33.720> also<03:30:34.140> had<03:30:34.880> your 03:30:36.130 --> 03:30:36.140 align:start position:0% switch and I think it also had your 03:30:36.140 --> 03:30:38.929 align:start position:0% switch and I think it also had your firewall<03:30:37.140> there's<03:30:37.439> a<03:30:37.620> few<03:30:37.739> things<03:30:37.979> it<03:30:38.220> did<03:30:38.460> but 03:30:38.929 --> 03:30:38.939 align:start position:0% firewall there's a few things it did but 03:30:38.939 --> 03:30:40.429 align:start position:0% firewall there's a few things it did but basically<03:30:39.300> this<03:30:39.479> was<03:30:39.600> everything<03:30:39.840> in<03:30:40.140> a<03:30:40.319> box 03:30:40.429 --> 03:30:40.439 align:start position:0% basically this was everything in a box 03:30:40.439 --> 03:30:42.889 align:start position:0% basically this was everything in a box that<03:30:40.680> a<03:30:40.859> small<03:30:40.920> business<03:30:41.160> would<03:30:41.520> need 03:30:42.889 --> 03:30:42.899 align:start position:0% that a small business would need 03:30:42.899 --> 03:30:45.650 align:start position:0% that a small business would need so<03:30:43.680> it<03:30:44.040> does<03:30:44.279> several<03:30:45.060> things<03:30:45.239> and<03:30:45.479> it's 03:30:45.650 --> 03:30:45.660 align:start position:0% so it does several things and it's 03:30:45.660 --> 03:30:47.330 align:start position:0% so it does several things and it's designed<03:30:45.960> to<03:30:46.020> do<03:30:46.200> them<03:30:46.319> all<03:30:46.500> pretty<03:30:46.739> well<03:30:46.979> your 03:30:47.330 --> 03:30:47.340 align:start position:0% designed to do them all pretty well your 03:30:47.340 --> 03:30:50.210 align:start position:0% designed to do them all pretty well your firewall<03:30:47.760> your<03:30:48.000> antivirus<03:30:48.660> your<03:30:49.380> IDs<03:30:49.739> or<03:30:49.920> IPS 03:30:50.210 --> 03:30:50.220 align:start position:0% firewall your antivirus your IDs or IPS 03:30:50.220 --> 03:30:53.170 align:start position:0% firewall your antivirus your IDs or IPS you<03:30:50.760> can<03:30:50.819> it<03:30:51.479> has<03:30:51.660> VPN<03:30:52.080> software<03:30:52.500> built<03:30:52.920> in 03:30:53.170 --> 03:30:53.180 align:start position:0% you can it has VPN software built in 03:30:53.180 --> 03:30:55.429 align:start position:0% you can it has VPN software built in brands<03:30:54.180> that<03:30:54.300> you<03:30:54.420> want<03:30:54.600> to<03:30:54.779> check<03:30:54.899> out<03:30:55.080> that 03:30:55.429 --> 03:30:55.439 align:start position:0% brands that you want to check out that 03:30:55.439 --> 03:30:57.170 align:start position:0% brands that you want to check out that are<03:30:55.560> Market<03:30:55.680> leaders<03:30:56.100> at<03:30:56.279> the<03:30:56.399> moment<03:30:56.520> are<03:30:56.880> so 03:30:57.170 --> 03:30:57.180 align:start position:0% are Market leaders at the moment are so 03:30:57.180 --> 03:31:00.290 align:start position:0% are Market leaders at the moment are so fast<03:30:57.439> which<03:30:58.439> this<03:30:58.859> is<03:30:59.040> a<03:30:59.340> copyright<03:31:00.000> from 03:31:00.290 --> 03:31:00.300 align:start position:0% fast which this is a copyright from 03:31:00.300 --> 03:31:01.969 align:start position:0% fast which this is a copyright from their<03:31:00.540> page 03:31:01.969 --> 03:31:01.979 align:start position:0% their page 03:31:01.979 --> 03:31:04.130 align:start position:0% their page and<03:31:02.640> why<03:31:03.120> jungle 03:31:04.130 --> 03:31:04.140 align:start position:0% and why jungle 03:31:04.140 --> 03:31:06.950 align:start position:0% and why jungle a<03:31:04.680> lot<03:31:04.800> easier<03:31:05.100> for<03:31:05.340> you<03:31:05.520> to<03:31:05.939> install<03:31:06.540> and 03:31:06.950 --> 03:31:06.960 align:start position:0% a lot easier for you to install and 03:31:06.960 --> 03:31:08.870 align:start position:0% a lot easier for you to install and manage<03:31:07.319> most<03:31:07.620> of<03:31:07.800> it<03:31:07.920> will<03:31:08.040> be<03:31:08.279> running<03:31:08.460> off 03:31:08.870 --> 03:31:08.880 align:start position:0% manage most of it will be running off 03:31:08.880 --> 03:31:11.570 align:start position:0% manage most of it will be running off the<03:31:09.120> graphical<03:31:09.540> user<03:31:10.020> interface<03:31:10.560> so<03:31:11.340> rather 03:31:11.570 --> 03:31:11.580 align:start position:0% the graphical user interface so rather 03:31:11.580 --> 03:31:13.429 align:start position:0% the graphical user interface so rather than<03:31:11.819> have<03:31:12.120> to<03:31:12.239> configure<03:31:12.600> a<03:31:12.779> Cisco<03:31:13.140> device 03:31:13.429 --> 03:31:13.439 align:start position:0% than have to configure a Cisco device 03:31:13.439 --> 03:31:15.950 align:start position:0% than have to configure a Cisco device which<03:31:13.920> is<03:31:14.460> frankly<03:31:15.000> quite<03:31:15.180> a<03:31:15.359> nightmare<03:31:15.720> for 03:31:15.950 --> 03:31:15.960 align:start position:0% which is frankly quite a nightmare for 03:31:15.960 --> 03:31:17.570 align:start position:0% which is frankly quite a nightmare for most<03:31:16.080> people<03:31:16.319> unless<03:31:17.100> you<03:31:17.279> know<03:31:17.340> what<03:31:17.460> you're 03:31:17.570 --> 03:31:17.580 align:start position:0% most people unless you know what you're 03:31:17.580 --> 03:31:19.849 align:start position:0% most people unless you know what you're doing 03:31:19.849 --> 03:31:19.859 align:start position:0% 03:31:19.859 --> 03:31:21.830 align:start position:0% uh<03:31:20.580> it<03:31:20.819> just<03:31:20.939> makes<03:31:21.120> it<03:31:21.300> a<03:31:21.420> lot<03:31:21.479> easier 03:31:21.830 --> 03:31:21.840 align:start position:0% uh it just makes it a lot easier 03:31:21.840 --> 03:31:23.990 align:start position:0% uh it just makes it a lot easier probably<03:31:22.620> I'm<03:31:23.040> I'm<03:31:23.279> saying<03:31:23.640> it's<03:31:23.760> more 03:31:23.990 --> 03:31:24.000 align:start position:0% probably I'm I'm saying it's more 03:31:24.000 --> 03:31:26.030 align:start position:0% probably I'm I'm saying it's more suitable<03:31:24.420> for<03:31:24.840> the<03:31:25.020> check<03:31:25.500> the<03:31:25.739> software 03:31:26.030 --> 03:31:26.040 align:start position:0% suitable for the check the software 03:31:26.040 --> 03:31:28.190 align:start position:0% suitable for the check the software because<03:31:26.220> they<03:31:26.460> may<03:31:26.640> say<03:31:26.880> different<03:31:27.180> the<03:31:27.960> small 03:31:28.190 --> 03:31:28.200 align:start position:0% because they may say different the small 03:31:28.200 --> 03:31:31.010 align:start position:0% because they may say different the small business<03:31:28.700> the<03:31:29.700> small<03:31:30.120> to<03:31:30.300> medium-sized 03:31:31.010 --> 03:31:31.020 align:start position:0% business the small to medium-sized 03:31:31.020 --> 03:31:32.630 align:start position:0% business the small to medium-sized Enterprise<03:31:31.200> where<03:31:31.920> you<03:31:32.100> don't<03:31:32.160> have<03:31:32.279> a<03:31:32.460> lot<03:31:32.520> of 03:31:32.630 --> 03:31:32.640 align:start position:0% Enterprise where you don't have a lot of 03:31:32.640 --> 03:31:34.670 align:start position:0% Enterprise where you don't have a lot of employees<03:31:33.180> and<03:31:33.840> you<03:31:33.960> may<03:31:34.140> just<03:31:34.319> have<03:31:34.439> one 03:31:34.670 --> 03:31:34.680 align:start position:0% employees and you may just have one 03:31:34.680 --> 03:31:36.650 align:start position:0% employees and you may just have one support<03:31:34.920> person<03:31:35.340> or<03:31:35.700> somebody<03:31:35.880> that<03:31:36.180> comes<03:31:36.540> in 03:31:36.650 --> 03:31:36.660 align:start position:0% support person or somebody that comes in 03:31:36.660 --> 03:31:40.429 align:start position:0% support person or somebody that comes in just<03:31:37.439> to<03:31:37.800> do<03:31:38.040> patches<03:31:38.760> and<03:31:38.939> maintenance 03:31:40.429 --> 03:31:40.439 align:start position:0% just to do patches and maintenance 03:31:40.439 --> 03:31:43.849 align:start position:0% just to do patches and maintenance obviously<03:31:41.279> saves<03:31:41.760> time<03:31:41.939> and<03:31:42.120> money<03:31:42.359> so<03:31:43.080> a<03:31:43.439> big 03:31:43.849 --> 03:31:43.859 align:start position:0% obviously saves time and money so a big 03:31:43.859 --> 03:31:46.610 align:start position:0% obviously saves time and money so a big pull<03:31:44.100> for<03:31:44.399> any<03:31:44.580> small<03:31:44.760> businesses 03:31:46.610 --> 03:31:46.620 align:start position:0% pull for any small businesses 03:31:46.620 --> 03:31:48.590 align:start position:0% pull for any small businesses the<03:31:47.160> only<03:31:47.340> problem<03:31:47.580> is<03:31:47.819> if<03:31:48.180> you're<03:31:48.359> running 03:31:48.590 --> 03:31:48.600 align:start position:0% the only problem is if you're running 03:31:48.600 --> 03:31:50.630 align:start position:0% the only problem is if you're running everything<03:31:48.899> off<03:31:49.319> this<03:31:49.560> I<03:31:49.800> guess<03:31:49.920> it's<03:31:50.100> running 03:31:50.630 --> 03:31:50.640 align:start position:0% everything off this I guess it's running 03:31:50.640 --> 03:31:53.210 align:start position:0% everything off this I guess it's running off<03:31:50.939> a<03:31:51.060> server<03:31:51.359> of<03:31:51.540> some<03:31:51.779> sort<03:31:52.080> because<03:31:52.979> it's 03:31:53.210 --> 03:31:53.220 align:start position:0% off a server of some sort because it's 03:31:53.220 --> 03:31:55.250 align:start position:0% off a server of some sort because it's software<03:31:53.580> based<03:31:54.120> then<03:31:54.600> you've<03:31:54.840> got<03:31:54.899> a<03:31:55.080> single 03:31:55.250 --> 03:31:55.260 align:start position:0% software based then you've got a single 03:31:55.260 --> 03:31:56.750 align:start position:0% software based then you've got a single point<03:31:55.439> of<03:31:55.620> failure<03:31:55.979> so<03:31:56.100> you've<03:31:56.279> got<03:31:56.399> to<03:31:56.520> take 03:31:56.750 --> 03:31:56.760 align:start position:0% point of failure so you've got to take 03:31:56.760 --> 03:31:57.830 align:start position:0% point of failure so you've got to take this 03:31:57.830 --> 03:31:57.840 align:start position:0% this 03:31:57.840 --> 03:31:59.510 align:start position:0% this um<03:31:57.899> into<03:31:58.500> account<03:31:58.800> with<03:31:59.100> your<03:31:59.340> business 03:31:59.510 --> 03:31:59.520 align:start position:0% um into account with your business 03:31:59.520 --> 03:32:01.370 align:start position:0% um into account with your business continuity<03:32:00.300> planning<03:32:00.779> what<03:32:00.960> you're<03:32:01.080> going<03:32:01.200> to 03:32:01.370 --> 03:32:01.380 align:start position:0% continuity planning what you're going to 03:32:01.380 --> 03:32:04.070 align:start position:0% continuity planning what you're going to do<03:32:01.500> if<03:32:02.340> it<03:32:02.640> part<03:32:02.939> of<03:32:03.120> it<03:32:03.300> breaks<03:32:03.540> all<03:32:03.720> of<03:32:03.899> it 03:32:04.070 --> 03:32:04.080 align:start position:0% do if it part of it breaks all of it 03:32:04.080 --> 03:32:05.150 align:start position:0% do if it part of it breaks all of it breaks 03:32:05.150 --> 03:32:05.160 align:start position:0% breaks 03:32:05.160 --> 03:32:06.490 align:start position:0% breaks Etc 03:32:06.490 --> 03:32:06.500 align:start position:0% Etc 03:32:06.500 --> 03:32:09.950 align:start position:0% Etc ngfw<03:32:07.500> Next<03:32:07.920> Generation<03:32:08.399> firewalls<03:32:09.300> so<03:32:09.720> the 03:32:09.950 --> 03:32:09.960 align:start position:0% ngfw Next Generation firewalls so the 03:32:09.960 --> 03:32:11.929 align:start position:0% ngfw Next Generation firewalls so the hackers<03:32:10.319> as<03:32:10.560> you<03:32:10.800> know<03:32:10.979> are<03:32:11.160> getting<03:32:11.399> smarter 03:32:11.929 --> 03:32:11.939 align:start position:0% hackers as you know are getting smarter 03:32:11.939 --> 03:32:14.990 align:start position:0% hackers as you know are getting smarter and<03:32:12.060> smarter<03:32:12.479> and<03:32:12.600> smarter<03:32:13.080> and<03:32:13.739> whereas<03:32:14.279> and 03:32:14.990 --> 03:32:15.000 align:start position:0% and smarter and smarter and whereas and 03:32:15.000 --> 03:32:17.870 align:start position:0% and smarter and smarter and whereas and we'd<03:32:15.540> have<03:32:15.660> to<03:32:15.779> be<03:32:15.899> checking<03:32:16.260> the<03:32:16.439> IP<03:32:16.739> headers 03:32:17.870 --> 03:32:17.880 align:start position:0% we'd have to be checking the IP headers 03:32:17.880 --> 03:32:20.990 align:start position:0% we'd have to be checking the IP headers or<03:32:18.359> the<03:32:18.600> TCP<03:32:19.080> headers<03:32:19.500> to<03:32:19.739> find<03:32:20.040> any<03:32:20.460> malicious 03:32:20.990 --> 03:32:21.000 align:start position:0% or the TCP headers to find any malicious 03:32:21.000 --> 03:32:24.229 align:start position:0% or the TCP headers to find any malicious code<03:32:21.960> it's<03:32:22.920> actually<03:32:23.160> now<03:32:23.580> being<03:32:23.819> buried 03:32:24.229 --> 03:32:24.239 align:start position:0% code it's actually now being buried 03:32:24.239 --> 03:32:26.929 align:start position:0% code it's actually now being buried inside<03:32:24.540> the<03:32:24.840> application<03:32:25.260> data<03:32:25.979> and 03:32:26.929 --> 03:32:26.939 align:start position:0% inside the application data and 03:32:26.939 --> 03:32:29.269 align:start position:0% inside the application data and traditionally<03:32:27.420> your<03:32:28.200> firewalls<03:32:28.859> May<03:32:29.040> well 03:32:29.269 --> 03:32:29.279 align:start position:0% traditionally your firewalls May well 03:32:29.279 --> 03:32:31.550 align:start position:0% traditionally your firewalls May well have<03:32:29.520> been<03:32:29.700> just<03:32:29.880> checking<03:32:30.420> these<03:32:31.260> particular 03:32:31.550 --> 03:32:31.560 align:start position:0% have been just checking these particular 03:32:31.560 --> 03:32:34.849 align:start position:0% have been just checking these particular Fields<03:32:32.100> headers<03:32:32.880> Footers<03:32:33.300> trailers<03:32:33.779> whatever 03:32:34.849 --> 03:32:34.859 align:start position:0% Fields headers Footers trailers whatever 03:32:34.859 --> 03:32:37.969 align:start position:0% Fields headers Footers trailers whatever so<03:32:35.279> I<03:32:35.580> just<03:32:35.760> got<03:32:35.880> this<03:32:36.060> image<03:32:36.359> off<03:32:36.960> um<03:32:36.960> this<03:32:37.560> URL 03:32:37.969 --> 03:32:37.979 align:start position:0% so I just got this image off um this URL 03:32:37.979 --> 03:32:40.070 align:start position:0% so I just got this image off um this URL here<03:32:38.220> so<03:32:39.000> these<03:32:39.300> are<03:32:39.420> known<03:32:39.540> as<03:32:39.779> third 03:32:40.070 --> 03:32:40.080 align:start position:0% here so these are known as third 03:32:40.080 --> 03:32:43.190 align:start position:0% here so these are known as third generation<03:32:40.680> firewalls 03:32:43.190 --> 03:32:43.200 align:start position:0% generation firewalls 03:32:43.200 --> 03:32:45.530 align:start position:0% generation firewalls this<03:32:43.800> combines<03:32:44.160> your<03:32:44.399> firewall<03:32:44.880> with<03:32:45.359> your 03:32:45.530 --> 03:32:45.540 align:start position:0% this combines your firewall with your 03:32:45.540 --> 03:32:47.809 align:start position:0% this combines your firewall with your other<03:32:45.660> filtering<03:32:46.319> looking<03:32:47.040> at<03:32:47.340> application 03:32:47.809 --> 03:32:47.819 align:start position:0% other filtering looking at application 03:32:47.819 --> 03:32:50.809 align:start position:0% other filtering looking at application and<03:32:48.600> this<03:32:48.779> is<03:32:48.960> where<03:32:49.260> the<03:32:49.680> crypto<03:32:50.220> lockers<03:32:50.580> are 03:32:50.809 --> 03:32:50.819 align:start position:0% and this is where the crypto lockers are 03:32:50.819 --> 03:32:53.929 align:start position:0% and this is where the crypto lockers are hiding<03:32:51.120> which<03:32:51.779> we<03:32:51.960> cover<03:32:52.140> later 03:32:53.929 --> 03:32:53.939 align:start position:0% hiding which we cover later 03:32:53.939 --> 03:32:56.389 align:start position:0% hiding which we cover later and<03:32:54.420> it<03:32:54.600> can<03:32:54.779> include<03:32:55.080> antivirus<03:32:55.979> ID 03:32:56.389 --> 03:32:56.399 align:start position:0% and it can include antivirus ID 03:32:56.399 --> 03:32:58.610 align:start position:0% and it can include antivirus ID management<03:32:56.819> your<03:32:57.600> transport<03:32:58.020> layer<03:32:58.380> security 03:32:58.610 --> 03:32:58.620 align:start position:0% management your transport layer security 03:32:58.620 --> 03:33:02.809 align:start position:0% management your transport layer security which<03:32:59.340> is<03:32:59.660> the<03:33:00.660> latest<03:33:00.840> version<03:33:01.380> so<03:33:02.040> secure 03:33:02.809 --> 03:33:02.819 align:start position:0% which is the latest version so secure 03:33:02.819 --> 03:33:04.849 align:start position:0% which is the latest version so secure sockets<03:33:03.300> layer<03:33:03.660> quality<03:33:04.260> of<03:33:04.380> service<03:33:04.560> if 03:33:04.849 --> 03:33:04.859 align:start position:0% sockets layer quality of service if 03:33:04.859 --> 03:33:06.590 align:start position:0% sockets layer quality of service if you're<03:33:04.920> running<03:33:05.040> it<03:33:05.220> on<03:33:05.399> your<03:33:05.520> network<03:33:05.700> so<03:33:06.420> if 03:33:06.590 --> 03:33:06.600 align:start position:0% you're running it on your network so if 03:33:06.600 --> 03:33:09.830 align:start position:0% you're running it on your network so if you're<03:33:06.840> trying<03:33:07.200> to<03:33:07.439> prioritize<03:33:08.279> Voice<03:33:08.840> or 03:33:09.830 --> 03:33:09.840 align:start position:0% you're trying to prioritize Voice or 03:33:09.840 --> 03:33:11.750 align:start position:0% you're trying to prioritize Voice or video<03:33:10.140> conferencing<03:33:10.920> whatever<03:33:11.160> you<03:33:11.460> want<03:33:11.580> to 03:33:11.750 --> 03:33:11.760 align:start position:0% video conferencing whatever you want to 03:33:11.760 --> 03:33:14.269 align:start position:0% video conferencing whatever you want to run<03:33:12.239> at<03:33:12.660> your<03:33:12.899> work 03:33:14.269 --> 03:33:14.279 align:start position:0% run at your work 03:33:14.279 --> 03:33:16.809 align:start position:0% run at your work uh<03:33:14.700> command<03:33:15.060> firewall<03:33:15.479> antivirus<03:33:16.080> Gateway 03:33:16.809 --> 03:33:16.819 align:start position:0% uh command firewall antivirus Gateway 03:33:16.819 --> 03:33:21.590 align:start position:0% uh command firewall antivirus Gateway IDs<03:33:17.819> IPS<03:33:18.680> VPN<03:33:19.680> software 03:33:21.590 --> 03:33:21.600 align:start position:0% IDs IPS VPN software 03:33:21.600 --> 03:33:24.469 align:start position:0% IDs IPS VPN software now<03:33:22.200> eighty<03:33:22.739> percent<03:33:22.800> of<03:33:23.100> the<03:33:23.279> malware<03:33:23.700> now 03:33:24.469 --> 03:33:24.479 align:start position:0% now eighty percent of the malware now 03:33:24.479 --> 03:33:28.130 align:start position:0% now eighty percent of the malware now targets<03:33:25.200> your<03:33:26.040> application<03:33:26.460> so<03:33:26.819> this<03:33:27.120> is 03:33:28.130 --> 03:33:28.140 align:start position:0% targets your application so this is 03:33:28.140 --> 03:33:31.010 align:start position:0% targets your application so this is this<03:33:28.859> is<03:33:28.979> the<03:33:29.279> software<03:33:29.640> stuff<03:33:30.060> and<03:33:30.660> normally 03:33:31.010 --> 03:33:31.020 align:start position:0% this is the software stuff and normally 03:33:31.020 --> 03:33:32.950 align:start position:0% this is the software stuff and normally we<03:33:31.500> wouldn't<03:33:31.620> have<03:33:31.859> been<03:33:32.040> inspecting<03:33:32.640> inside 03:33:32.950 --> 03:33:32.960 align:start position:0% we wouldn't have been inspecting inside 03:33:32.960 --> 03:33:35.630 align:start position:0% we wouldn't have been inspecting inside this<03:33:33.960> part<03:33:34.080> of<03:33:34.200> the<03:33:34.319> packet<03:33:34.680> but<03:33:35.279> this<03:33:35.520> is 03:33:35.630 --> 03:33:35.640 align:start position:0% this part of the packet but this is 03:33:35.640 --> 03:33:37.610 align:start position:0% this part of the packet but this is where<03:33:35.880> they're<03:33:36.000> hiding<03:33:36.420> it<03:33:36.540> now<03:33:36.720> and<03:33:37.080> so<03:33:37.439> you 03:33:37.610 --> 03:33:37.620 align:start position:0% where they're hiding it now and so you 03:33:37.620 --> 03:33:39.290 align:start position:0% where they're hiding it now and so you might<03:33:37.800> things<03:33:38.340> that<03:33:38.520> have<03:33:38.640> been<03:33:38.760> downloaded 03:33:39.290 --> 03:33:39.300 align:start position:0% might things that have been downloaded 03:33:39.300 --> 03:33:41.750 align:start position:0% might things that have been downloaded off<03:33:39.479> the<03:33:39.800> websites<03:33:40.800> or<03:33:41.040> in<03:33:41.220> hidden<03:33:41.580> inside 03:33:41.750 --> 03:33:41.760 align:start position:0% off the websites or in hidden inside 03:33:41.760 --> 03:33:44.150 align:start position:0% off the websites or in hidden inside emails<03:33:42.420> so<03:33:42.899> this<03:33:43.080> is<03:33:43.140> why<03:33:43.319> we<03:33:43.560> need<03:33:43.680> this<03:33:43.920> third 03:33:44.150 --> 03:33:44.160 align:start position:0% emails so this is why we need this third 03:33:44.160 --> 03:33:47.570 align:start position:0% emails so this is why we need this third generation<03:33:44.640> of<03:33:45.479> firewall 03:33:47.570 --> 03:33:47.580 align:start position:0% generation of firewall 03:33:47.580 --> 03:33:50.450 align:start position:0% generation of firewall so<03:33:48.300> blocking<03:33:49.020> ports<03:33:49.439> and<03:33:49.560> filtering<03:33:50.040> is<03:33:50.220> no 03:33:50.450 --> 03:33:50.460 align:start position:0% so blocking ports and filtering is no 03:33:50.460 --> 03:33:52.610 align:start position:0% so blocking ports and filtering is no longer<03:33:50.700> enough<03:33:50.880> unfortunately<03:33:51.600> so<03:33:52.260> I<03:33:52.439> mean 03:33:52.610 --> 03:33:52.620 align:start position:0% longer enough unfortunately so I mean 03:33:52.620 --> 03:33:54.590 align:start position:0% longer enough unfortunately so I mean just<03:33:53.160> um<03:33:53.160> Gathering<03:33:53.640> more<03:33:53.880> data<03:33:54.180> spending 03:33:54.590 --> 03:33:54.600 align:start position:0% just um Gathering more data spending 03:33:54.600 --> 03:33:56.389 align:start position:0% just um Gathering more data spending more<03:33:54.779> cash<03:33:55.020> and<03:33:55.500> having<03:33:55.680> more<03:33:55.920> stuff<03:33:56.160> to 03:33:56.389 --> 03:33:56.399 align:start position:0% more cash and having more stuff to 03:33:56.399 --> 03:33:59.030 align:start position:0% more cash and having more stuff to support<03:33:56.660> what<03:33:57.660> this<03:33:57.840> is<03:33:58.020> known<03:33:58.260> as<03:33:58.439> here<03:33:58.739> is 03:33:59.030 --> 03:33:59.040 align:start position:0% support what this is known as here is 03:33:59.040 --> 03:34:02.090 align:start position:0% support what this is known as here is deep<03:33:59.279> packet<03:33:59.939> inspection<03:34:00.500> DPI<03:34:01.500> so<03:34:01.979> we're 03:34:02.090 --> 03:34:02.100 align:start position:0% deep packet inspection DPI so we're 03:34:02.100 --> 03:34:04.550 align:start position:0% deep packet inspection DPI so we're looking<03:34:02.220> deep<03:34:02.580> inside<03:34:02.760> the<03:34:03.060> IP<03:34:03.359> pack<03:34:03.600> here<03:34:03.899> to 03:34:04.550 --> 03:34:04.560 align:start position:0% looking deep inside the IP pack here to 03:34:04.560 --> 03:34:06.170 align:start position:0% looking deep inside the IP pack here to see<03:34:04.680> if<03:34:04.800> there's<03:34:04.920> anything<03:34:05.100> nefarious<03:34:05.880> in 03:34:06.170 --> 03:34:06.180 align:start position:0% see if there's anything nefarious in 03:34:06.180 --> 03:34:08.269 align:start position:0% see if there's anything nefarious in there 03:34:08.269 --> 03:34:08.279 align:start position:0% there 03:34:08.279 --> 03:34:10.790 align:start position:0% there the<03:34:08.819> Deepak<03:34:09.300> inspection<03:34:09.779> you<03:34:10.380> can<03:34:10.439> see<03:34:10.560> things 03:34:10.790 --> 03:34:10.800 align:start position:0% the Deepak inspection you can see things 03:34:10.800 --> 03:34:12.050 align:start position:0% the Deepak inspection you can see things that<03:34:11.040> you<03:34:11.160> wouldn't<03:34:11.279> normally<03:34:11.580> see<03:34:11.760> looking 03:34:12.050 --> 03:34:12.060 align:start position:0% that you wouldn't normally see looking 03:34:12.060 --> 03:34:15.170 align:start position:0% that you wouldn't normally see looking at<03:34:12.359> the<03:34:12.899> headers<03:34:13.739> and<03:34:13.979> Footers<03:34:14.460> and<03:34:14.700> trailers 03:34:15.170 --> 03:34:15.180 align:start position:0% at the headers and Footers and trailers 03:34:15.180 --> 03:34:18.590 align:start position:0% at the headers and Footers and trailers worms<03:34:16.140> viruses<03:34:16.800> and<03:34:17.340> it<03:34:17.460> can<03:34:17.580> also<03:34:17.819> do<03:34:18.060> so<03:34:18.239> most 03:34:18.590 --> 03:34:18.600 align:start position:0% worms viruses and it can also do so most 03:34:18.600 --> 03:34:21.710 align:start position:0% worms viruses and it can also do so most importantly<03:34:19.080> at<03:34:19.739> wire<03:34:19.979> speeds<03:34:20.640> so<03:34:21.359> the<03:34:21.600> thing 03:34:21.710 --> 03:34:21.720 align:start position:0% importantly at wire speeds so the thing 03:34:21.720 --> 03:34:25.910 align:start position:0% importantly at wire speeds so the thing that<03:34:22.020> we<03:34:22.260> all<03:34:22.439> hate<03:34:22.739> in<03:34:23.040> networks<03:34:23.700> is 03:34:25.910 --> 03:34:25.920 align:start position:0% that we all hate in networks is 03:34:25.920 --> 03:34:29.330 align:start position:0% that we all hate in networks is latency<03:34:26.700> I.E<03:34:27.660> slowing<03:34:28.140> stuff<03:34:28.380> down<03:34:28.620> it's 03:34:29.330 --> 03:34:29.340 align:start position:0% latency I.E slowing stuff down it's 03:34:29.340 --> 03:34:30.710 align:start position:0% latency I.E slowing stuff down it's really<03:34:29.520> bad<03:34:29.700> news<03:34:29.880> for<03:34:30.120> us<03:34:30.180> and<03:34:30.359> it<03:34:30.479> obviously 03:34:30.710 --> 03:34:30.720 align:start position:0% really bad news for us and it obviously 03:34:30.720 --> 03:34:32.570 align:start position:0% really bad news for us and it obviously frustrates<03:34:31.200> the<03:34:31.380> users<03:34:31.800> especially<03:34:32.520> if 03:34:32.570 --> 03:34:32.580 align:start position:0% frustrates the users especially if 03:34:32.580 --> 03:34:33.530 align:start position:0% frustrates the users especially if you're<03:34:32.700> doing<03:34:32.819> voice<03:34:33.120> and<03:34:33.359> video 03:34:33.530 --> 03:34:33.540 align:start position:0% you're doing voice and video 03:34:33.540 --> 03:34:37.490 align:start position:0% you're doing voice and video conferencing<03:34:34.200> it<03:34:34.439> would<03:34:34.560> be<03:34:34.739> a<03:34:35.520> nightmare 03:34:37.490 --> 03:34:37.500 align:start position:0% conferencing it would be a nightmare 03:34:37.500 --> 03:34:40.429 align:start position:0% conferencing it would be a nightmare they've<03:34:38.040> added<03:34:38.399> a<03:34:38.700> voiceover<03:34:39.180> voice<03:34:39.720> over<03:34:39.899> IP 03:34:40.429 --> 03:34:40.439 align:start position:0% they've added a voiceover voice over IP 03:34:40.439 --> 03:34:45.889 align:start position:0% they've added a voiceover voice over IP PBX<03:34:41.359> into<03:34:42.359> the<03:34:42.779> syllabus 03:34:45.889 --> 03:34:45.899 align:start position:0% 03:34:45.899 --> 03:34:47.929 align:start position:0% and<03:34:46.500> you<03:34:46.680> can<03:34:46.800> see<03:34:46.979> we've<03:34:47.279> got<03:34:47.399> the<03:34:47.700> voice 03:34:47.929 --> 03:34:47.939 align:start position:0% and you can see we've got the voice 03:34:47.939 --> 03:34:49.849 align:start position:0% and you can see we've got the voice Gateway<03:34:48.660> router<03:34:49.080> here<03:34:49.200> I've<03:34:49.380> got<03:34:49.500> this<03:34:49.680> from 03:34:49.849 --> 03:34:49.859 align:start position:0% Gateway router here I've got this from 03:34:49.859 --> 03:34:52.429 align:start position:0% Gateway router here I've got this from this<03:34:50.100> website<03:34:50.399> here<03:34:50.640> easytalks.com<03:34:51.600> so 03:34:52.429 --> 03:34:52.439 align:start position:0% this website here easytalks.com so 03:34:52.439 --> 03:34:54.469 align:start position:0% this website here easytalks.com so you've<03:34:52.739> got<03:34:52.920> your<03:34:53.340> uh<03:34:53.819> public<03:34:54.180> switch 03:34:54.469 --> 03:34:54.479 align:start position:0% you've got your uh public switch 03:34:54.479 --> 03:34:56.450 align:start position:0% you've got your uh public switch telephone<03:34:54.899> Network<03:34:55.380> which<03:34:55.859> Josh<03:34:56.100> talked 03:34:56.450 --> 03:34:56.460 align:start position:0% telephone Network which Josh talked 03:34:56.460 --> 03:34:59.150 align:start position:0% telephone Network which Josh talked about<03:34:56.580> which<03:34:57.300> is<03:34:57.479> your<03:34:57.660> voice<03:34:57.840> stuff<03:34:58.200> and<03:34:59.040> then 03:34:59.150 --> 03:34:59.160 align:start position:0% about which is your voice stuff and then 03:34:59.160 --> 03:35:01.790 align:start position:0% about which is your voice stuff and then we've<03:34:59.399> got<03:34:59.640> our<03:35:00.180> traditional<03:35:00.720> phones<03:35:01.319> uh 03:35:01.790 --> 03:35:01.800 align:start position:0% we've got our traditional phones uh 03:35:01.800 --> 03:35:04.010 align:start position:0% we've got our traditional phones uh we've<03:35:01.979> got<03:35:02.040> our<03:35:02.220> IP<03:35:02.580> phones<03:35:03.060> been<03:35:03.600> managed 03:35:04.010 --> 03:35:04.020 align:start position:0% we've got our IP phones been managed 03:35:04.020 --> 03:35:05.690 align:start position:0% we've got our IP phones been managed here<03:35:04.140> so<03:35:04.380> we<03:35:04.560> can<03:35:04.680> all<03:35:04.859> communicate<03:35:05.340> within 03:35:05.690 --> 03:35:05.700 align:start position:0% here so we can all communicate within 03:35:05.700 --> 03:35:09.530 align:start position:0% here so we can all communicate within each<03:35:05.880> other<03:35:06.060> and<03:35:06.779> then<03:35:06.899> your<03:35:07.200> voice<03:35:07.640> PBX<03:35:08.640> if 03:35:09.530 --> 03:35:09.540 align:start position:0% each other and then your voice PBX if 03:35:09.540 --> 03:35:11.090 align:start position:0% each other and then your voice PBX if you<03:35:09.600> need<03:35:09.779> to<03:35:09.899> make<03:35:10.020> calls<03:35:10.500> to<03:35:10.620> traditional 03:35:11.090 --> 03:35:11.100 align:start position:0% you need to make calls to traditional 03:35:11.100 --> 03:35:13.429 align:start position:0% you need to make calls to traditional landlines<03:35:11.819> that<03:35:12.359> can<03:35:12.479> go<03:35:12.660> out<03:35:12.779> through<03:35:12.960> the 03:35:13.429 --> 03:35:13.439 align:start position:0% landlines that can go out through the 03:35:13.439 --> 03:35:17.389 align:start position:0% landlines that can go out through the traditional<03:35:14.160> public<03:35:14.520> switch<03:35:14.880> Network 03:35:17.389 --> 03:35:17.399 align:start position:0% 03:35:17.399 --> 03:35:19.969 align:start position:0% so<03:35:18.000> IP<03:35:18.359> private<03:35:18.779> Branch<03:35:18.960> exchange<03:35:19.380> is<03:35:19.680> a<03:35:19.859> phone 03:35:19.969 --> 03:35:19.979 align:start position:0% so IP private Branch exchange is a phone 03:35:19.979 --> 03:35:22.190 align:start position:0% so IP private Branch exchange is a phone system<03:35:20.279> and<03:35:20.760> it<03:35:20.880> but<03:35:21.300> it<03:35:21.420> also<03:35:21.600> offers<03:35:21.840> IP 03:35:22.190 --> 03:35:22.200 align:start position:0% system and it but it also offers IP 03:35:22.200 --> 03:35:24.410 align:start position:0% system and it but it also offers IP connectivity<03:35:22.739> you<03:35:23.399> get<03:35:23.520> your<03:35:23.939> traditional 03:35:24.410 --> 03:35:24.420 align:start position:0% connectivity you get your traditional 03:35:24.420 --> 03:35:26.630 align:start position:0% connectivity you get your traditional extensions<03:35:25.140> connecting<03:35:25.800> through<03:35:26.100> your<03:35:26.340> Lan 03:35:26.630 --> 03:35:26.640 align:start position:0% extensions connecting through your Lan 03:35:26.640 --> 03:35:28.849 align:start position:0% extensions connecting through your Lan and<03:35:27.120> obviously<03:35:27.420> you<03:35:27.600> can<03:35:27.720> go<03:35:27.899> through 03:35:28.849 --> 03:35:28.859 align:start position:0% and obviously you can go through 03:35:28.859 --> 03:35:31.330 align:start position:0% and obviously you can go through the<03:35:29.460> internet<03:35:29.700> if<03:35:30.300> you've<03:35:30.479> got<03:35:30.660> your 03:35:31.330 --> 03:35:31.340 align:start position:0% the internet if you've got your 03:35:31.340 --> 03:35:34.010 align:start position:0% the internet if you've got your traditional<03:35:32.340> IP<03:35:32.760> phone<03:35:33.060> and<03:35:33.600> you<03:35:33.720> want<03:35:33.840> to 03:35:34.010 --> 03:35:34.020 align:start position:0% traditional IP phone and you want to 03:35:34.020 --> 03:35:36.110 align:start position:0% traditional IP phone and you want to call<03:35:34.140> somebody<03:35:34.439> in<03:35:35.100> the<03:35:35.220> remote<03:35:35.399> office<03:35:35.760> with 03:35:36.110 --> 03:35:36.120 align:start position:0% call somebody in the remote office with 03:35:36.120 --> 03:35:38.030 align:start position:0% call somebody in the remote office with another<03:35:36.300> IP<03:35:36.840> phone 03:35:38.030 --> 03:35:38.040 align:start position:0% another IP phone 03:35:38.040 --> 03:35:40.790 align:start position:0% another IP phone and<03:35:38.520> you<03:35:38.700> can<03:35:38.819> do<03:35:39.000> that<03:35:39.180> okay<03:35:39.500> otherwise<03:35:40.500> it 03:35:40.790 --> 03:35:40.800 align:start position:0% and you can do that okay otherwise it 03:35:40.800 --> 03:35:41.929 align:start position:0% and you can do that okay otherwise it would<03:35:40.979> have<03:35:41.100> to<03:35:41.160> go<03:35:41.279> through<03:35:41.460> to<03:35:41.640> the<03:35:41.819> public 03:35:41.929 --> 03:35:41.939 align:start position:0% would have to go through to the public 03:35:41.939 --> 03:35:44.150 align:start position:0% would have to go through to the public switch<03:35:42.239> telephone<03:35:42.540> Network 03:35:44.150 --> 03:35:44.160 align:start position:0% switch telephone Network 03:35:44.160 --> 03:35:46.370 align:start position:0% switch telephone Network you<03:35:44.760> can<03:35:44.939> buy<03:35:45.120> actually<03:35:45.359> software<03:35:45.899> so<03:35:46.140> it'll 03:35:46.370 --> 03:35:46.380 align:start position:0% you can buy actually software so it'll 03:35:46.380 --> 03:35:48.410 align:start position:0% you can buy actually software so it'll run<03:35:46.560> off<03:35:46.739> a<03:35:46.859> server<03:35:47.160> if<03:35:47.340> you<03:35:47.460> so<03:35:47.580> wish<03:35:47.880> or<03:35:48.300> you 03:35:48.410 --> 03:35:48.420 align:start position:0% run off a server if you so wish or you 03:35:48.420 --> 03:35:49.969 align:start position:0% run off a server if you so wish or you can<03:35:48.540> have<03:35:48.660> a<03:35:48.779> hardware<03:35:48.899> where<03:35:49.380> you<03:35:49.560> have<03:35:49.859> to 03:35:49.969 --> 03:35:49.979 align:start position:0% can have a hardware where you have to 03:35:49.979 --> 03:35:51.710 align:start position:0% can have a hardware where you have to wire<03:35:50.160> it<03:35:50.340> up<03:35:50.460> yourself 03:35:51.710 --> 03:35:51.720 align:start position:0% wire it up yourself 03:35:51.720 --> 03:35:53.570 align:start position:0% wire it up yourself mentioned<03:35:52.439> it<03:35:52.560> connects<03:35:52.920> to<03:35:53.040> the<03:35:53.220> phone 03:35:53.570 --> 03:35:53.580 align:start position:0% mentioned it connects to the phone 03:35:53.580 --> 03:35:56.450 align:start position:0% mentioned it connects to the phone network<03:35:53.899> and<03:35:54.899> obviously<03:35:55.439> use<03:35:55.680> it<03:35:55.859> if<03:35:56.040> invoice 03:35:56.450 --> 03:35:56.460 align:start position:0% network and obviously use it if invoice 03:35:56.460 --> 03:35:59.570 align:start position:0% network and obviously use it if invoice is<03:35:56.640> enabled<03:35:57.060> on<03:35:57.180> your<03:35:57.359> network 03:35:59.570 --> 03:35:59.580 align:start position:0% is enabled on your network 03:35:59.580 --> 03:36:02.450 align:start position:0% is enabled on your network content<03:36:00.540> filters 03:36:02.450 --> 03:36:02.460 align:start position:0% content filters 03:36:02.460 --> 03:36:06.530 align:start position:0% content filters uh<03:36:03.060> what<03:36:03.420> you<03:36:03.960> can<03:36:04.200> and<03:36:04.439> can't<03:36:04.739> uh<03:36:05.580> Surf<03:36:06.420> and 03:36:06.530 --> 03:36:06.540 align:start position:0% uh what you can and can't uh Surf and 03:36:06.540 --> 03:36:08.150 align:start position:0% uh what you can and can't uh Surf and I've<03:36:06.660> got<03:36:07.020> something<03:36:07.200> similar<03:36:07.680> on<03:36:07.859> my<03:36:07.979> home 03:36:08.150 --> 03:36:08.160 align:start position:0% I've got something similar on my home 03:36:08.160 --> 03:36:10.429 align:start position:0% I've got something similar on my home router<03:36:08.700> although<03:36:09.239> the<03:36:09.479> Fairly<03:36:09.779> rudimental 03:36:10.429 --> 03:36:10.439 align:start position:0% router although the Fairly rudimental 03:36:10.439 --> 03:36:13.010 align:start position:0% router although the Fairly rudimental level<03:36:11.100> where<03:36:11.700> I<03:36:11.880> can<03:36:12.000> block<03:36:12.180> stuff<03:36:12.479> that<03:36:12.720> and 03:36:13.010 --> 03:36:13.020 align:start position:0% level where I can block stuff that and 03:36:13.020 --> 03:36:15.290 align:start position:0% level where I can block stuff that and the<03:36:13.260> kids<03:36:13.380> shouldn't<03:36:13.680> be<03:36:13.800> watching<03:36:14.300> also 03:36:15.290 --> 03:36:15.300 align:start position:0% the kids shouldn't be watching also 03:36:15.300 --> 03:36:17.990 align:start position:0% the kids shouldn't be watching also referred<03:36:15.720> to<03:36:15.840> as<03:36:16.080> information<03:36:16.500> filtering 03:36:17.990 --> 03:36:18.000 align:start position:0% referred to as information filtering 03:36:18.000 --> 03:36:19.910 align:start position:0% referred to as information filtering depending<03:36:18.540> on<03:36:18.660> where<03:36:18.779> you<03:36:18.960> are<03:36:19.140> usually 03:36:19.910 --> 03:36:19.920 align:start position:0% depending on where you are usually 03:36:19.920 --> 03:36:23.330 align:start position:0% depending on where you are usually software<03:36:20.460> based<03:36:21.080> and<03:36:22.080> it's<03:36:22.500> it's<03:36:22.800> very<03:36:23.100> simply 03:36:23.330 --> 03:36:23.340 align:start position:0% software based and it's it's very simply 03:36:23.340 --> 03:36:26.150 align:start position:0% software based and it's it's very simply blocks<03:36:23.819> harmful<03:36:24.120> websites<03:36:24.779> or<03:36:25.439> files<03:36:25.859> such<03:36:25.979> as 03:36:26.150 --> 03:36:26.160 align:start position:0% blocks harmful websites or files such as 03:36:26.160 --> 03:36:27.650 align:start position:0% blocks harmful websites or files such as Dot<03:36:26.580> xees 03:36:27.650 --> 03:36:27.660 align:start position:0% Dot xees 03:36:27.660 --> 03:36:30.290 align:start position:0% Dot xees it<03:36:28.200> would<03:36:28.439> probably<03:36:28.620> uh<03:36:29.100> block 03:36:30.290 --> 03:36:30.300 align:start position:0% it would probably uh block 03:36:30.300 --> 03:36:34.790 align:start position:0% it would probably uh block um<03:36:30.420> Facebook 03:36:34.790 --> 03:36:34.800 align:start position:0% 03:36:34.800 --> 03:36:36.650 align:start position:0% Instagram<03:36:35.399> stuff<03:36:35.939> you<03:36:36.180> don't<03:36:36.300> want<03:36:36.479> people 03:36:36.650 --> 03:36:36.660 align:start position:0% Instagram stuff you don't want people 03:36:36.660 --> 03:36:39.830 align:start position:0% Instagram stuff you don't want people surfing<03:36:37.200> while<03:36:37.439> they're<03:36:37.620> at<03:36:37.739> work<03:36:37.859> also 03:36:39.830 --> 03:36:39.840 align:start position:0% surfing while they're at work also 03:36:39.840 --> 03:36:45.050 align:start position:0% surfing while they're at work also you<03:36:40.560> can<03:36:40.739> work<03:36:40.979> your<03:36:41.640> local<03:36:41.819> network<03:36:42.180> so<03:36:43.020> your 03:36:45.050 --> 03:36:45.060 align:start position:0% you can work your local network so your 03:36:45.060 --> 03:36:45.650 align:start position:0% you can work your local network so your um 03:36:45.650 --> 03:36:45.660 align:start position:0% um 03:36:45.660 --> 03:36:48.410 align:start position:0% um office<03:36:45.960> here<03:36:46.580> you<03:36:47.580> could<03:36:47.700> actually<03:36:47.880> have<03:36:48.239> it 03:36:48.410 --> 03:36:48.420 align:start position:0% office here you could actually have it 03:36:48.420 --> 03:36:52.269 align:start position:0% office here you could actually have it working<03:36:48.779> for<03:36:49.560> your<03:36:49.859> core<03:36:50.040> Network 03:36:52.269 --> 03:36:52.279 align:start position:0% working for your core Network 03:36:52.279 --> 03:36:55.490 align:start position:0% working for your core Network or<03:36:53.279> you<03:36:53.460> could<03:36:53.580> let<03:36:53.700> your<03:36:53.880> ISP<03:36:54.420> take<03:36:54.899> care<03:36:55.080> take 03:36:55.490 --> 03:36:55.500 align:start position:0% or you could let your ISP take care take 03:36:55.500 --> 03:36:57.469 align:start position:0% or you could let your ISP take care take care<03:36:55.680> of<03:36:55.800> it<03:36:55.920> sometimes<03:36:56.880> they're<03:36:57.239> actually 03:36:57.469 --> 03:36:57.479 align:start position:0% care of it sometimes they're actually 03:36:57.479 --> 03:36:59.450 align:start position:0% care of it sometimes they're actually automatically<03:36:58.319> block 03:36:59.450 --> 03:36:59.460 align:start position:0% automatically block 03:36:59.460 --> 03:37:01.849 align:start position:0% automatically block and<03:37:00.060> certain<03:37:00.359> content<03:37:00.779> and<03:37:00.960> certain<03:37:01.200> websites 03:37:01.849 --> 03:37:01.859 align:start position:0% and certain content and certain websites 03:37:01.859 --> 03:37:04.250 align:start position:0% and certain content and certain websites especially<03:37:02.640> in<03:37:03.000> some<03:37:03.180> countries<03:37:03.600> where<03:37:04.020> they 03:37:04.250 --> 03:37:04.260 align:start position:0% especially in some countries where they 03:37:04.260 --> 03:37:06.590 align:start position:0% especially in some countries where they they<03:37:04.500> control<03:37:04.880> politically<03:37:05.880> what<03:37:06.239> you<03:37:06.420> can 03:37:06.590 --> 03:37:06.600 align:start position:0% they control politically what you can 03:37:06.600 --> 03:37:10.190 align:start position:0% they control politically what you can and<03:37:06.840> can't<03:37:07.080> say<03:37:07.380> I<03:37:08.220> think<03:37:08.819> um 03:37:10.190 --> 03:37:10.200 align:start position:0% and can't say I think um 03:37:10.200 --> 03:37:12.650 align:start position:0% and can't say I think um Egypt<03:37:10.920> and<03:37:11.220> some<03:37:11.460> other<03:37:11.640> countries<03:37:12.359> where 03:37:12.650 --> 03:37:12.660 align:start position:0% Egypt and some other countries where 03:37:12.660 --> 03:37:14.330 align:start position:0% Egypt and some other countries where they<03:37:13.380> don't<03:37:13.500> want<03:37:13.620> you<03:37:13.739> to<03:37:13.859> see<03:37:14.040> certain 03:37:14.330 --> 03:37:14.340 align:start position:0% they don't want you to see certain 03:37:14.340 --> 03:37:15.650 align:start position:0% they don't want you to see certain things 03:37:15.650 --> 03:37:15.660 align:start position:0% things 03:37:15.660 --> 03:37:19.070 align:start position:0% things which<03:37:15.899> I<03:37:16.140> won't<03:37:16.260> go<03:37:16.439> into<03:37:16.560> that<03:37:16.859> uh<03:37:17.819> so<03:37:18.720> your 03:37:19.070 --> 03:37:19.080 align:start position:0% which I won't go into that uh so your 03:37:19.080 --> 03:37:21.110 align:start position:0% which I won't go into that uh so your voice<03:37:19.319> is<03:37:19.500> enabled<03:37:19.920> sorry<03:37:20.100> that's<03:37:20.460> uh<03:37:20.819> but 03:37:21.110 --> 03:37:21.120 align:start position:0% voice is enabled sorry that's uh but 03:37:21.120 --> 03:37:23.389 align:start position:0% voice is enabled sorry that's uh but they're<03:37:21.300> in<03:37:21.479> error<03:37:21.720> from<03:37:21.840> another<03:37:21.960> slide 03:37:23.389 --> 03:37:23.399 align:start position:0% they're in error from another slide 03:37:23.399 --> 03:37:25.429 align:start position:0% they're in error from another slide so<03:37:23.819> multi-layer<03:37:24.540> switch<03:37:24.660> we've<03:37:24.960> talked<03:37:25.260> about 03:37:25.429 --> 03:37:25.439 align:start position:0% so multi-layer switch we've talked about 03:37:25.439 --> 03:37:29.090 align:start position:0% so multi-layer switch we've talked about your<03:37:26.340> wireless<03:37:26.580> controllers<03:37:27.680> turning<03:37:28.680> your 03:37:29.090 --> 03:37:29.100 align:start position:0% your wireless controllers turning your 03:37:29.100 --> 03:37:32.809 align:start position:0% your wireless controllers turning your access<03:37:29.479> points<03:37:30.479> into<03:37:31.460> lightweight<03:37:32.460> access 03:37:32.809 --> 03:37:32.819 align:start position:0% access points into lightweight access 03:37:32.819 --> 03:37:35.870 align:start position:0% access points into lightweight access points<03:37:33.359> so<03:37:33.660> they<03:37:33.840> just<03:37:34.020> forward<03:37:34.200> traffic<03:37:34.880> and 03:37:35.870 --> 03:37:35.880 align:start position:0% points so they just forward traffic and 03:37:35.880 --> 03:37:37.849 align:start position:0% points so they just forward traffic and your<03:37:36.239> wireless<03:37:36.479> LAN<03:37:36.840> controller<03:37:37.380> takes<03:37:37.620> care 03:37:37.849 --> 03:37:37.859 align:start position:0% your wireless LAN controller takes care 03:37:37.859 --> 03:37:40.809 align:start position:0% your wireless LAN controller takes care of<03:37:38.220> all<03:37:38.399> of<03:37:38.580> the<03:37:39.200> routing<03:37:40.200> security 03:37:40.809 --> 03:37:40.819 align:start position:0% of all of the routing security 03:37:40.819 --> 03:37:43.150 align:start position:0% of all of the routing security associations 03:37:43.150 --> 03:37:43.160 align:start position:0% associations 03:37:43.160 --> 03:37:46.010 align:start position:0% associations ssids<03:37:44.160> that<03:37:44.460> kind<03:37:44.580> of<03:37:44.700> stuff 03:37:46.010 --> 03:37:46.020 align:start position:0% ssids that kind of stuff 03:37:46.020 --> 03:37:49.010 align:start position:0% ssids that kind of stuff load<03:37:46.859> balancer<03:37:47.279> where<03:37:47.880> it's<03:37:48.120> sending<03:37:48.840> your 03:37:49.010 --> 03:37:49.020 align:start position:0% load balancer where it's sending your 03:37:49.020 --> 03:37:53.210 align:start position:0% load balancer where it's sending your traffic<03:37:49.880> transparently<03:37:51.140> to<03:37:52.140> two<03:37:52.859> or<03:37:53.040> more 03:37:53.210 --> 03:37:53.220 align:start position:0% traffic transparently to two or more 03:37:53.220 --> 03:37:56.570 align:start position:0% traffic transparently to two or more servers<03:37:53.819> and<03:37:54.060> obviously<03:37:54.479> it's<03:37:54.960> got<03:37:55.260> your 03:37:56.570 --> 03:37:56.580 align:start position:0% servers and obviously it's got your 03:37:56.580 --> 03:37:57.410 align:start position:0% servers and obviously it's got your um 03:37:57.410 --> 03:37:57.420 align:start position:0% um 03:37:57.420 --> 03:37:59.630 align:start position:0% um the<03:37:57.960> capability<03:37:58.380> of<03:37:58.739> if<03:37:58.920> there's<03:37:59.100> a<03:37:59.279> one<03:37:59.460> of 03:37:59.630 --> 03:37:59.640 align:start position:0% the capability of if there's a one of 03:37:59.640 --> 03:38:01.010 align:start position:0% the capability of if there's a one of your<03:37:59.700> servers<03:38:00.000> goes<03:38:00.239> down<03:38:00.359> it<03:38:00.600> can<03:38:00.720> balance 03:38:01.010 --> 03:38:01.020 align:start position:0% your servers goes down it can balance 03:38:01.020 --> 03:38:04.670 align:start position:0% your servers goes down it can balance between<03:38:01.260> what<03:38:02.220> uh<03:38:02.460> or<03:38:02.640> others<03:38:03.060> are<03:38:03.180> left 03:38:04.670 --> 03:38:04.680 align:start position:0% between what uh or others are left 03:38:04.680 --> 03:38:07.610 align:start position:0% between what uh or others are left RDS<03:38:05.399> on<03:38:05.580> IPS<03:38:06.000> uh<03:38:06.840> you've<03:38:07.020> got<03:38:07.020> to<03:38:07.140> bear<03:38:07.260> in<03:38:07.439> mind 03:38:07.610 --> 03:38:07.620 align:start position:0% RDS on IPS uh you've got to bear in mind 03:38:07.620 --> 03:38:11.330 align:start position:0% RDS on IPS uh you've got to bear in mind what's<03:38:07.979> in<03:38:08.580> line<03:38:08.760> and<03:38:09.720> then<03:38:09.960> what<03:38:10.680> is<03:38:10.859> out<03:38:11.220> of 03:38:11.330 --> 03:38:11.340 align:start position:0% what's in line and then what is out of 03:38:11.340 --> 03:38:13.250 align:start position:0% what's in line and then what is out of line<03:38:11.520> and<03:38:11.819> just<03:38:12.000> receives<03:38:12.300> a<03:38:12.540> copy<03:38:12.899> because 03:38:13.250 --> 03:38:13.260 align:start position:0% line and just receives a copy because 03:38:13.260 --> 03:38:17.870 align:start position:0% line and just receives a copy because that's<03:38:13.500> your<03:38:13.739> typical<03:38:14.420> exam<03:38:15.420> question 03:38:17.870 --> 03:38:17.880 align:start position:0% 03:38:17.880 --> 03:38:20.030 align:start position:0% AAA<03:38:18.779> server<03:38:19.140> which<03:38:19.319> I'll<03:38:19.500> talk<03:38:19.680> more<03:38:19.859> about 03:38:20.030 --> 03:38:20.040 align:start position:0% AAA server which I'll talk more about 03:38:20.040 --> 03:38:24.950 align:start position:0% AAA server which I'll talk more about later<03:38:20.460> uh<03:38:21.180> UTM<03:38:21.779> again<03:38:22.319> probably<03:38:22.800> small 03:38:24.950 --> 03:38:24.960 align:start position:0% later uh UTM again probably small 03:38:24.960 --> 03:38:27.650 align:start position:0% later uh UTM again probably small to<03:38:25.439> medium-sized<03:38:26.279> Enterprise<03:38:26.580> but<03:38:27.180> do<03:38:27.420> check 03:38:27.650 --> 03:38:27.660 align:start position:0% to medium-sized Enterprise but do check 03:38:27.660 --> 03:38:29.870 align:start position:0% to medium-sized Enterprise but do check the<03:38:28.380> marketing<03:38:28.859> spiel 03:38:29.870 --> 03:38:29.880 align:start position:0% the marketing spiel 03:38:29.880 --> 03:38:33.950 align:start position:0% the marketing spiel Next<03:38:30.359> Generation<03:38:30.720> firewall<03:38:31.380> which<03:38:31.920> is<03:38:32.160> deep 03:38:33.950 --> 03:38:33.960 align:start position:0% Next Generation firewall which is deep 03:38:33.960 --> 03:38:37.309 align:start position:0% Next Generation firewall which is deep packet<03:38:34.560> inspections<03:38:35.340> voice 03:38:37.309 --> 03:38:37.319 align:start position:0% packet inspections voice 03:38:37.319 --> 03:38:40.309 align:start position:0% packet inspections voice again<03:38:37.859> if<03:38:38.160> you're<03:38:38.279> going<03:38:38.460> out<03:38:38.700> to<03:38:39.000> the 03:38:40.309 --> 03:38:40.319 align:start position:0% again if you're going out to the 03:38:40.319 --> 03:38:42.830 align:start position:0% again if you're going out to the public<03:38:40.739> switch<03:38:41.160> telephone<03:38:41.760> Network<03:38:42.239> you'll 03:38:42.830 --> 03:38:42.840 align:start position:0% public switch telephone Network you'll 03:38:42.840 --> 03:38:45.410 align:start position:0% public switch telephone Network you'll need<03:38:43.020> the<03:38:43.140> voice<03:38:43.260> Gateway<03:38:43.739> contact<03:38:44.460> content 03:38:45.410 --> 03:38:45.420 align:start position:0% need the voice Gateway contact content 03:38:45.420 --> 03:38:49.130 align:start position:0% need the voice Gateway contact content filter<03:38:45.800> is<03:38:46.800> blocking<03:38:47.479> sites<03:38:48.479> or<03:38:48.660> content 03:38:49.130 --> 03:38:49.140 align:start position:0% filter is blocking sites or content 03:38:49.140 --> 03:38:52.750 align:start position:0% filter is blocking sites or content definitely<03:38:49.979> dot<03:38:50.340> XC<03:38:50.700> files 03:38:52.750 --> 03:38:52.760 align:start position:0% definitely dot XC files 03:38:52.760 --> 03:38:58.070 align:start position:0% definitely dot XC files and<03:38:54.060> um<03:38:54.060> even<03:38:54.779> even<03:38:55.200> my<03:38:55.880> online<03:38:56.880> file<03:38:57.479> that<03:38:57.779> I 03:38:58.070 --> 03:38:58.080 align:start position:0% and um even even my online file that I 03:38:58.080 --> 03:39:00.590 align:start position:0% and um even even my online file that I share<03:38:58.859> with<03:38:59.040> my<03:38:59.399> providers<03:39:00.000> some<03:39:00.359> of<03:39:00.479> my 03:39:00.590 --> 03:39:00.600 align:start position:0% share with my providers some of my 03:39:00.600 --> 03:39:02.750 align:start position:0% share with my providers some of my Freelancers<03:39:01.200> that<03:39:01.380> work<03:39:01.560> for<03:39:01.739> me<03:39:01.920> they<03:39:02.640> can't 03:39:02.750 --> 03:39:02.760 align:start position:0% Freelancers that work for me they can't 03:39:02.760 --> 03:39:05.990 align:start position:0% Freelancers that work for me they can't reach<03:39:03.120> this<03:39:03.239> on<03:39:03.479> them<03:39:03.660> from<03:39:04.160> their<03:39:05.160> corporate 03:39:05.990 --> 03:39:06.000 align:start position:0% reach this on them from their corporate 03:39:06.000 --> 03:39:08.090 align:start position:0% reach this on them from their corporate Network<03:39:06.239> either<03:39:06.540> they're<03:39:06.779> often<03:39:07.140> blocked 03:39:08.090 --> 03:39:08.100 align:start position:0% Network either they're often blocked 03:39:08.100 --> 03:39:09.830 align:start position:0% Network either they're often blocked all<03:39:08.460> right<03:39:08.580> so<03:39:08.700> that's<03:39:08.880> all<03:39:09.120> for<03:39:09.300> now<03:39:09.479> thank 03:39:09.830 --> 03:39:09.840 align:start position:0% all right so that's all for now thank 03:39:09.840 --> 03:39:14.020 align:start position:0% all right so that's all for now thank you<03:39:09.960> very<03:39:10.020> much<03:39:10.200> for<03:39:10.439> listening 03:39:14.020 --> 03:39:14.030 align:start position:0% 03:39:14.030 --> 03:39:33.710 align:start position:0% [Music] 03:39:33.710 --> 03:39:33.720 align:start position:0% 03:39:33.720 --> 03:39:37.550 align:start position:0% foreign<03:39:34.620> network<03:39:35.460> communications<03:39:36.560> data 03:39:37.550 --> 03:39:37.560 align:start position:0% foreign network communications data 03:39:37.560 --> 03:39:39.889 align:start position:0% foreign network communications data transmission 03:39:39.889 --> 03:39:39.899 align:start position:0% 03:39:39.899 --> 03:39:44.990 align:start position:0% as<03:39:40.319> you<03:39:40.439> may<03:39:40.560> know<03:39:41.060> computers<03:39:42.060> talk<03:39:42.479> in<03:39:42.899> bits 03:39:44.990 --> 03:39:45.000 align:start position:0% as you may know computers talk in bits 03:39:45.000 --> 03:39:48.530 align:start position:0% as you may know computers talk in bits ones<03:39:45.960> and<03:39:46.140> zeros<03:39:46.560> ons<03:39:47.220> and<03:39:47.460> offs<03:39:47.819> and<03:39:48.239> this<03:39:48.420> is 03:39:48.530 --> 03:39:48.540 align:start position:0% ones and zeros ons and offs and this is 03:39:48.540 --> 03:39:51.110 align:start position:0% ones and zeros ons and offs and this is how<03:39:48.840> all<03:39:49.260> of<03:39:49.380> the<03:39:49.620> data<03:39:49.979> that<03:39:50.520> we<03:39:50.640> deal<03:39:50.760> with<03:39:50.939> in 03:39:51.110 --> 03:39:51.120 align:start position:0% how all of the data that we deal with in 03:39:51.120 --> 03:39:53.809 align:start position:0% how all of the data that we deal with in computers<03:39:51.600> is<03:39:52.439> transferred<03:39:53.100> from<03:39:53.399> one 03:39:53.809 --> 03:39:53.819 align:start position:0% computers is transferred from one 03:39:53.819 --> 03:39:56.570 align:start position:0% computers is transferred from one computer<03:39:54.180> to<03:39:54.779> the<03:39:55.020> next<03:39:55.140> or<03:39:55.500> one<03:39:55.739> node<03:39:56.040> to<03:39:56.399> the 03:39:56.570 --> 03:39:56.580 align:start position:0% computer to the next or one node to the 03:39:56.580 --> 03:39:59.090 align:start position:0% computer to the next or one node to the next<03:39:56.760> over<03:39:57.300> the<03:39:57.660> media<03:39:58.020> as<03:39:58.439> we've<03:39:58.680> discussed 03:39:59.090 --> 03:39:59.100 align:start position:0% next over the media as we've discussed 03:39:59.100 --> 03:40:02.090 align:start position:0% next over the media as we've discussed but<03:39:59.640> we<03:39:59.760> want<03:39:59.880> to<03:40:00.060> talk<03:40:00.180> exactly<03:40:00.779> about<03:40:01.100> how 03:40:02.090 --> 03:40:02.100 align:start position:0% but we want to talk exactly about how 03:40:02.100 --> 03:40:05.030 align:start position:0% but we want to talk exactly about how these<03:40:02.460> bits<03:40:02.819> these<03:40:03.120> ones<03:40:03.359> and<03:40:03.479> zeros<03:40:03.840> get<03:40:04.680> from 03:40:05.030 --> 03:40:05.040 align:start position:0% these bits these ones and zeros get from 03:40:05.040 --> 03:40:09.590 align:start position:0% these bits these ones and zeros get from point<03:40:05.340> A<03:40:05.700> to<03:40:06.479> point<03:40:06.720> B<03:40:07.020> and<03:40:07.920> so<03:40:08.160> in<03:40:08.640> this<03:40:09.000> uh 03:40:09.590 --> 03:40:09.600 align:start position:0% point A to point B and so in this uh 03:40:09.600 --> 03:40:12.050 align:start position:0% point A to point B and so in this uh module<03:40:10.140> we're<03:40:10.560> going<03:40:10.680> to<03:40:10.859> talk<03:40:11.040> about<03:40:11.340> data 03:40:12.050 --> 03:40:12.060 align:start position:0% module we're going to talk about data 03:40:12.060 --> 03:40:13.190 align:start position:0% module we're going to talk about data transmission 03:40:13.190 --> 03:40:13.200 align:start position:0% transmission 03:40:13.200 --> 03:40:16.910 align:start position:0% transmission or<03:40:14.100> how<03:40:14.580> data<03:40:15.120> makes<03:40:15.479> it<03:40:15.660> from<03:40:16.020> one<03:40:16.380> point<03:40:16.620> to 03:40:16.910 --> 03:40:16.920 align:start position:0% or how data makes it from one point to 03:40:16.920 --> 03:40:18.170 align:start position:0% or how data makes it from one point to the<03:40:17.160> other 03:40:18.170 --> 03:40:18.180 align:start position:0% the other 03:40:18.180 --> 03:40:20.330 align:start position:0% the other so<03:40:18.720> we're<03:40:19.020> going<03:40:19.140> to<03:40:19.260> start<03:40:19.439> by<03:40:19.739> talking<03:40:20.040> about 03:40:20.330 --> 03:40:20.340 align:start position:0% so we're going to start by talking about 03:40:20.340 --> 03:40:22.429 align:start position:0% so we're going to start by talking about data<03:40:20.939> transmission<03:40:21.120> methods<03:40:21.899> and<03:40:22.020> defining 03:40:22.429 --> 03:40:22.439 align:start position:0% data transmission methods and defining 03:40:22.439 --> 03:40:25.729 align:start position:0% data transmission methods and defining exactly<03:40:22.920> what<03:40:23.700> data<03:40:24.180> transmission<03:40:24.359> is 03:40:25.729 --> 03:40:25.739 align:start position:0% exactly what data transmission is 03:40:25.739 --> 03:40:27.490 align:start position:0% exactly what data transmission is we're<03:40:26.160> also<03:40:26.340> going<03:40:26.460> to<03:40:26.580> talk<03:40:26.700> about 03:40:27.490 --> 03:40:27.500 align:start position:0% we're also going to talk about 03:40:27.500 --> 03:40:31.010 align:start position:0% we're also going to talk about instantaneous<03:40:28.500> data<03:40:29.100> transfer<03:40:29.660> and<03:40:30.660> what 03:40:31.010 --> 03:40:31.020 align:start position:0% instantaneous data transfer and what 03:40:31.020 --> 03:40:33.229 align:start position:0% instantaneous data transfer and what might<03:40:31.200> require<03:40:31.500> it<03:40:31.859> the<03:40:32.220> word<03:40:32.340> instantaneous 03:40:33.229 --> 03:40:33.239 align:start position:0% might require it the word instantaneous 03:40:33.239 --> 03:40:35.690 align:start position:0% might require it the word instantaneous meaning<03:40:33.479> the<03:40:33.779> data<03:40:34.080> is<03:40:34.319> sent<03:40:34.700> instantaneously 03:40:35.690 --> 03:40:35.700 align:start position:0% meaning the data is sent instantaneously 03:40:35.700 --> 03:40:38.809 align:start position:0% meaning the data is sent instantaneously the<03:40:36.000> minute<03:40:36.180> that<03:40:36.960> it<03:40:37.140> is<03:40:37.319> created<03:40:37.800> in<03:40:38.640> some 03:40:38.809 --> 03:40:38.819 align:start position:0% the minute that it is created in some 03:40:38.819 --> 03:40:41.870 align:start position:0% the minute that it is created in some instances<03:40:39.239> data<03:40:39.899> is<03:40:40.140> first<03:40:40.500> stored<03:40:41.100> and<03:40:41.640> then 03:40:41.870 --> 03:40:41.880 align:start position:0% instances data is first stored and then 03:40:41.880 --> 03:40:44.269 align:start position:0% instances data is first stored and then converted<03:40:42.660> and<03:40:42.899> then<03:40:43.140> transferred<03:40:43.739> in<03:40:44.160> this 03:40:44.269 --> 03:40:44.279 align:start position:0% converted and then transferred in this 03:40:44.279 --> 03:40:46.130 align:start position:0% converted and then transferred in this case<03:40:44.420> instantaneously<03:40:45.420> the<03:40:45.720> data<03:40:46.020> is 03:40:46.130 --> 03:40:46.140 align:start position:0% case instantaneously the data is 03:40:46.140 --> 03:40:48.410 align:start position:0% case instantaneously the data is transferred<03:40:46.620> over<03:40:46.739> the<03:40:47.040> media<03:40:47.700> we're<03:40:48.180> also 03:40:48.410 --> 03:40:48.420 align:start position:0% transferred over the media we're also 03:40:48.420 --> 03:40:50.690 align:start position:0% transferred over the media we're also going<03:40:48.540> to<03:40:48.660> discuss<03:40:48.960> which<03:40:49.500> we've<03:40:49.739> seen<03:40:50.040> in<03:40:50.460> a 03:40:50.690 --> 03:40:50.700 align:start position:0% going to discuss which we've seen in a 03:40:50.700 --> 03:40:53.570 align:start position:0% going to discuss which we've seen in a plus<03:40:50.960> serial<03:40:51.960> data<03:40:52.500> transmission<03:40:52.680> meaning 03:40:53.570 --> 03:40:53.580 align:start position:0% plus serial data transmission meaning 03:40:53.580 --> 03:40:57.349 align:start position:0% plus serial data transmission meaning that<03:40:53.939> one<03:40:54.420> bit<03:40:54.660> is<03:40:55.080> sent<03:40:55.380> at<03:40:56.160> a<03:40:56.279> time<03:40:56.460> one<03:40:57.120> after 03:40:57.349 --> 03:40:57.359 align:start position:0% that one bit is sent at a time one after 03:40:57.359 --> 03:41:00.469 align:start position:0% that one bit is sent at a time one after the<03:40:57.720> other<03:40:57.840> and<03:40:58.560> remember<03:40:58.800> just<03:40:59.340> as<03:40:59.580> uh<03:40:59.939> you 03:41:00.469 --> 03:41:00.479 align:start position:0% the other and remember just as uh you 03:41:00.479 --> 03:41:03.170 align:start position:0% the other and remember just as uh you can<03:41:00.540> recall<03:41:00.960> one<03:41:01.859> byte 03:41:03.170 --> 03:41:03.180 align:start position:0% can recall one byte 03:41:03.180 --> 03:41:04.610 align:start position:0% can recall one byte equals 03:41:04.610 --> 03:41:04.620 align:start position:0% equals 03:41:04.620 --> 03:41:06.590 align:start position:0% equals eight<03:41:05.220> bits 03:41:06.590 --> 03:41:06.600 align:start position:0% eight bits 03:41:06.600 --> 03:41:08.929 align:start position:0% eight bits byte<03:41:07.260> being<03:41:07.439> represented<03:41:08.040> by<03:41:08.220> that<03:41:08.399> uppercase 03:41:08.929 --> 03:41:08.939 align:start position:0% byte being represented by that uppercase 03:41:08.939 --> 03:41:12.769 align:start position:0% byte being represented by that uppercase b<03:41:09.239> and<03:41:10.200> a<03:41:10.920> bit<03:41:11.520> being<03:41:11.819> represented<03:41:12.420> by<03:41:12.600> the 03:41:12.769 --> 03:41:12.779 align:start position:0% b and a bit being represented by the 03:41:12.779 --> 03:41:14.750 align:start position:0% b and a bit being represented by the lowercase<03:41:13.319> b 03:41:14.750 --> 03:41:14.760 align:start position:0% lowercase b 03:41:14.760 --> 03:41:16.729 align:start position:0% lowercase b we're<03:41:15.300> also<03:41:15.540> going<03:41:15.660> to<03:41:15.840> talk<03:41:15.960> about<03:41:16.200> two 03:41:16.729 --> 03:41:16.739 align:start position:0% we're also going to talk about two 03:41:16.739 --> 03:41:18.830 align:start position:0% we're also going to talk about two different<03:41:16.920> communication<03:41:17.580> methods<03:41:18.239> in 03:41:18.830 --> 03:41:18.840 align:start position:0% different communication methods in 03:41:18.840 --> 03:41:21.110 align:start position:0% different communication methods in serial<03:41:19.200> data<03:41:19.560> transmission<03:41:20.120> asynchronous 03:41:21.110 --> 03:41:21.120 align:start position:0% serial data transmission asynchronous 03:41:21.120 --> 03:41:23.389 align:start position:0% serial data transmission asynchronous and<03:41:21.540> synchronous<03:41:22.020> Communications<03:41:22.560> with 03:41:23.389 --> 03:41:23.399 align:start position:0% and synchronous Communications with 03:41:23.399 --> 03:41:26.870 align:start position:0% and synchronous Communications with which<03:41:23.700> have<03:41:23.939> to<03:41:24.120> do<03:41:24.300> with<03:41:24.720> uh<03:41:25.500> how<03:41:25.979> the<03:41:26.279> data<03:41:26.580> is 03:41:26.870 --> 03:41:26.880 align:start position:0% which have to do with uh how the data is 03:41:26.880 --> 03:41:30.170 align:start position:0% which have to do with uh how the data is synced<03:41:27.420> up<03:41:27.540> to<03:41:28.319> a<03:41:28.560> clock<03:41:28.739> cycle<03:41:29.160> with<03:41:29.580> the<03:41:29.700> CPU 03:41:30.170 --> 03:41:30.180 align:start position:0% synced up to a clock cycle with the CPU 03:41:30.180 --> 03:41:32.150 align:start position:0% synced up to a clock cycle with the CPU and<03:41:30.600> therefore<03:41:30.840> how<03:41:31.080> it's<03:41:31.260> sent 03:41:32.150 --> 03:41:32.160 align:start position:0% and therefore how it's sent 03:41:32.160 --> 03:41:34.429 align:start position:0% and therefore how it's sent then<03:41:32.819> we're<03:41:33.000> gonna<03:41:33.120> have<03:41:33.300> to<03:41:33.359> find<03:41:33.660> parallel 03:41:34.429 --> 03:41:34.439 align:start position:0% then we're gonna have to find parallel 03:41:34.439 --> 03:41:36.769 align:start position:0% then we're gonna have to find parallel data<03:41:34.800> transmission<03:41:34.979> meaning<03:41:35.939> that<03:41:36.180> the<03:41:36.420> data 03:41:36.769 --> 03:41:36.779 align:start position:0% data transmission meaning that the data 03:41:36.779 --> 03:41:38.450 align:start position:0% data transmission meaning that the data instead<03:41:37.439> of<03:41:37.500> being<03:41:37.620> sent<03:41:37.800> one<03:41:38.040> after<03:41:38.160> the 03:41:38.450 --> 03:41:38.460 align:start position:0% instead of being sent one after the 03:41:38.460 --> 03:41:40.790 align:start position:0% instead of being sent one after the other<03:41:38.580> you<03:41:39.300> may<03:41:39.479> have<03:41:39.720> eight<03:41:40.020> bits<03:41:40.380> of<03:41:40.500> data 03:41:40.790 --> 03:41:40.800 align:start position:0% other you may have eight bits of data 03:41:40.800 --> 03:41:43.550 align:start position:0% other you may have eight bits of data all<03:41:41.040> sent<03:41:41.279> at<03:41:42.000> Once<03:41:42.180> In<03:41:42.600> Parallel<03:41:43.020> with<03:41:43.380> the 03:41:43.550 --> 03:41:43.560 align:start position:0% all sent at Once In Parallel with the 03:41:43.560 --> 03:41:44.330 align:start position:0% all sent at Once In Parallel with the other 03:41:44.330 --> 03:41:44.340 align:start position:0% other 03:41:44.340 --> 03:41:46.670 align:start position:0% other finally<03:41:44.880> we're<03:41:45.060> going<03:41:45.180> to<03:41:45.239> discuss<03:41:45.680> baseband 03:41:46.670 --> 03:41:46.680 align:start position:0% finally we're going to discuss baseband 03:41:46.680 --> 03:41:48.830 align:start position:0% finally we're going to discuss baseband transmission<03:41:47.340> a<03:41:48.239> digital<03:41:48.540> transmission 03:41:48.830 --> 03:41:48.840 align:start position:0% transmission a digital transmission 03:41:48.840 --> 03:41:52.070 align:start position:0% transmission a digital transmission method<03:41:49.500> and<03:41:50.100> Broadband<03:41:50.640> transmission<03:41:51.120> or 03:41:52.070 --> 03:41:52.080 align:start position:0% method and Broadband transmission or 03:41:52.080 --> 03:41:54.410 align:start position:0% method and Broadband transmission or analog<03:41:52.620> transmission<03:41:52.920> method<03:41:53.580> these<03:41:54.239> are 03:41:54.410 --> 03:41:54.420 align:start position:0% analog transmission method these are 03:41:54.420 --> 03:41:56.269 align:start position:0% analog transmission method these are specifically<03:41:55.080> called<03:41:55.439> out<03:41:55.680> in<03:41:56.040> the<03:41:56.160> network 03:41:56.269 --> 03:41:56.279 align:start position:0% specifically called out in the network 03:41:56.279 --> 03:41:58.610 align:start position:0% specifically called out in the network plus<03:41:56.700> exam<03:41:57.180> and<03:41:57.660> so<03:41:57.840> it's<03:41:57.960> important<03:41:58.260> that<03:41:58.439> we 03:41:58.610 --> 03:41:58.620 align:start position:0% plus exam and so it's important that we 03:41:58.620 --> 03:42:01.610 align:start position:0% plus exam and so it's important that we pay<03:41:58.859> a<03:41:59.160> special<03:41:59.640> attention<03:42:00.060> to<03:42:00.359> those<03:42:00.620> now 03:42:01.610 --> 03:42:01.620 align:start position:0% pay a special attention to those now 03:42:01.620 --> 03:42:03.889 align:start position:0% pay a special attention to those now when<03:42:02.160> we<03:42:02.340> talk<03:42:02.580> about<03:42:02.819> data<03:42:03.720> transmission 03:42:03.889 --> 03:42:03.899 align:start position:0% when we talk about data transmission 03:42:03.899 --> 03:42:05.630 align:start position:0% when we talk about data transmission it's<03:42:04.620> important<03:42:04.920> that<03:42:05.160> we<03:42:05.340> have<03:42:05.460> to 03:42:05.630 --> 03:42:05.640 align:start position:0% it's important that we have to 03:42:05.640 --> 03:42:08.210 align:start position:0% it's important that we have to understand<03:42:05.880> there<03:42:06.479> are<03:42:06.660> many<03:42:06.840> ways<03:42:07.439> that<03:42:07.859> data 03:42:08.210 --> 03:42:08.220 align:start position:0% understand there are many ways that data 03:42:08.220 --> 03:42:11.330 align:start position:0% understand there are many ways that data can<03:42:08.340> be<03:42:08.520> sent<03:42:08.700> and<03:42:09.060> received<03:42:09.600> in<03:42:10.380> essence<03:42:10.680> data 03:42:11.330 --> 03:42:11.340 align:start position:0% can be sent and received in essence data 03:42:11.340 --> 03:42:14.330 align:start position:0% can be sent and received in essence data transmission<03:42:11.899> is<03:42:12.899> the<03:42:13.260> exchange<03:42:13.680> of<03:42:13.979> data 03:42:14.330 --> 03:42:14.340 align:start position:0% transmission is the exchange of data 03:42:14.340 --> 03:42:17.389 align:start position:0% transmission is the exchange of data between<03:42:14.760> devices<03:42:15.300> on<03:42:15.899> network<03:42:16.140> by<03:42:16.680> one<03:42:16.979> method 03:42:17.389 --> 03:42:17.399 align:start position:0% between devices on network by one method 03:42:17.399 --> 03:42:20.210 align:start position:0% between devices on network by one method or<03:42:17.880> another<03:42:18.140> the<03:42:19.140> main<03:42:19.500> thing<03:42:19.859> that 03:42:20.210 --> 03:42:20.220 align:start position:0% or another the main thing that 03:42:20.220 --> 03:42:23.690 align:start position:0% or another the main thing that differentiates<03:42:21.260> data<03:42:22.260> transmission<03:42:22.700> from 03:42:23.690 --> 03:42:23.700 align:start position:0% differentiates data transmission from 03:42:23.700 --> 03:42:28.550 align:start position:0% differentiates data transmission from say<03:42:24.260> Voice<03:42:25.260> or<03:42:26.040> telephony<03:42:26.580> transition<03:42:27.560> is 03:42:28.550 --> 03:42:28.560 align:start position:0% say Voice or telephony transition is 03:42:28.560 --> 03:42:31.729 align:start position:0% say Voice or telephony transition is that<03:42:28.859> we're<03:42:29.479> transmitting<03:42:30.500> many<03:42:31.500> different 03:42:31.729 --> 03:42:31.739 align:start position:0% that we're transmitting many different 03:42:31.739 --> 03:42:35.510 align:start position:0% that we're transmitting many different things<03:42:32.100> including<03:42:33.000> text<03:42:33.380> video<03:42:34.380> and<03:42:35.100> Graphics 03:42:35.510 --> 03:42:35.520 align:start position:0% things including text video and Graphics 03:42:35.520 --> 03:42:38.630 align:start position:0% things including text video and Graphics all<03:42:36.000> over<03:42:36.239> the<03:42:36.660> medium<03:42:36.960> whereas<03:42:37.560> telephony<03:42:38.100> is 03:42:38.630 --> 03:42:38.640 align:start position:0% all over the medium whereas telephony is 03:42:38.640 --> 03:42:40.969 align:start position:0% all over the medium whereas telephony is only<03:42:38.880> dealing<03:42:39.300> with<03:42:39.540> voice<03:42:39.899> this<03:42:40.859> is 03:42:40.969 --> 03:42:40.979 align:start position:0% only dealing with voice this is 03:42:40.979 --> 03:42:44.210 align:start position:0% only dealing with voice this is different<03:42:41.160> from<03:42:41.760> our<03:42:42.359> telephones<03:42:42.899> which<03:42:43.680> are 03:42:44.210 --> 03:42:44.220 align:start position:0% different from our telephones which are 03:42:44.220 --> 03:42:46.969 align:start position:0% different from our telephones which are are<03:42:44.700> also<03:42:45.060> transferring<03:42:45.600> a<03:42:45.779> sort<03:42:45.960> of<03:42:46.140> data<03:42:46.500> but 03:42:46.969 --> 03:42:46.979 align:start position:0% are also transferring a sort of data but 03:42:46.979 --> 03:42:48.769 align:start position:0% are also transferring a sort of data but that<03:42:47.160> data<03:42:47.460> doesn't<03:42:47.580> include<03:42:48.060> as<03:42:48.479> many 03:42:48.769 --> 03:42:48.779 align:start position:0% that data doesn't include as many 03:42:48.779 --> 03:42:50.750 align:start position:0% that data doesn't include as many different<03:42:49.500> things 03:42:50.750 --> 03:42:50.760 align:start position:0% different things 03:42:50.760 --> 03:42:53.050 align:start position:0% different things now<03:42:51.180> when<03:42:51.359> you<03:42:51.540> might<03:42:51.720> hear<03:42:51.960> the<03:42:52.260> term 03:42:53.050 --> 03:42:53.060 align:start position:0% now when you might hear the term 03:42:53.060 --> 03:42:56.090 align:start position:0% now when you might hear the term computer<03:42:54.060> network<03:42:54.600> I<03:42:55.439> just<03:42:55.560> want<03:42:55.739> to<03:42:55.859> be<03:42:55.920> clear 03:42:56.090 --> 03:42:56.100 align:start position:0% computer network I just want to be clear 03:42:56.100 --> 03:42:58.969 align:start position:0% computer network I just want to be clear that<03:42:56.399> computer<03:42:56.700> network<03:42:57.060> is<03:42:57.479> the<03:42:57.779> same<03:42:57.960> as<03:42:58.680> a 03:42:58.969 --> 03:42:58.979 align:start position:0% that computer network is the same as a 03:42:58.979 --> 03:43:01.010 align:start position:0% that computer network is the same as a Data<03:42:59.340> Network<03:42:59.460> and<03:43:00.000> so<03:43:00.239> we<03:43:00.420> might<03:43:00.540> be<03:43:00.720> using 03:43:01.010 --> 03:43:01.020 align:start position:0% Data Network and so we might be using 03:43:01.020 --> 03:43:02.929 align:start position:0% Data Network and so we might be using those<03:43:01.200> terms<03:43:01.620> interchangeably<03:43:02.520> but<03:43:02.760> when 03:43:02.929 --> 03:43:02.939 align:start position:0% those terms interchangeably but when 03:43:02.939 --> 03:43:04.330 align:start position:0% those terms interchangeably but when we're<03:43:03.120> talking<03:43:03.300> about<03:43:03.540> data<03:43:04.080> transmission 03:43:04.330 --> 03:43:04.340 align:start position:0% we're talking about data transmission 03:43:04.340 --> 03:43:07.910 align:start position:0% we're talking about data transmission sometimes<03:43:05.340> the<03:43:05.580> term<03:43:05.840> computer<03:43:06.840> network<03:43:07.319> as 03:43:07.910 --> 03:43:07.920 align:start position:0% sometimes the term computer network as 03:43:07.920 --> 03:43:09.590 align:start position:0% sometimes the term computer network as opposed<03:43:08.160> to<03:43:08.279> Data<03:43:08.700> Network<03:43:08.819> comes<03:43:09.300> up<03:43:09.359> but 03:43:09.590 --> 03:43:09.600 align:start position:0% opposed to Data Network comes up but 03:43:09.600 --> 03:43:11.269 align:start position:0% opposed to Data Network comes up but they<03:43:09.779> are<03:43:10.020> interchangeable 03:43:11.269 --> 03:43:11.279 align:start position:0% they are interchangeable 03:43:11.279 --> 03:43:14.750 align:start position:0% they are interchangeable now<03:43:11.880> in<03:43:12.300> most<03:43:12.479> cases<03:43:13.160> when<03:43:14.160> we're<03:43:14.460> dealing 03:43:14.750 --> 03:43:14.760 align:start position:0% now in most cases when we're dealing 03:43:14.760 --> 03:43:17.389 align:start position:0% now in most cases when we're dealing with<03:43:15.000> networking<03:43:15.660> the<03:43:16.380> data<03:43:16.739> is<03:43:16.979> stored 03:43:17.389 --> 03:43:17.399 align:start position:0% with networking the data is stored 03:43:17.399 --> 03:43:20.690 align:start position:0% with networking the data is stored somewhere<03:43:18.000> at<03:43:18.899> some<03:43:19.140> point<03:43:19.380> this<03:43:20.160> also<03:43:20.460> goes 03:43:20.690 --> 03:43:20.700 align:start position:0% somewhere at some point this also goes 03:43:20.700 --> 03:43:22.849 align:start position:0% somewhere at some point this also goes for<03:43:20.880> data<03:43:21.300> that's<03:43:21.540> ready<03:43:21.840> to<03:43:22.080> be<03:43:22.200> transmitted 03:43:22.849 --> 03:43:22.859 align:start position:0% for data that's ready to be transmitted 03:43:22.859 --> 03:43:25.610 align:start position:0% for data that's ready to be transmitted right<03:43:23.640> we<03:43:24.060> store<03:43:24.239> it<03:43:24.479> and<03:43:24.899> then<03:43:25.020> we<03:43:25.200> send<03:43:25.439> it 03:43:25.610 --> 03:43:25.620 align:start position:0% right we store it and then we send it 03:43:25.620 --> 03:43:27.830 align:start position:0% right we store it and then we send it however<03:43:26.160> there<03:43:26.520> are<03:43:26.640> some<03:43:26.819> instances<03:43:27.359> when 03:43:27.830 --> 03:43:27.840 align:start position:0% however there are some instances when 03:43:27.840 --> 03:43:30.349 align:start position:0% however there are some instances when data<03:43:28.260> needs<03:43:28.560> to<03:43:28.680> reach<03:43:29.040> its<03:43:29.340> destination<03:43:29.760> as 03:43:30.349 --> 03:43:30.359 align:start position:0% data needs to reach its destination as 03:43:30.359 --> 03:43:32.269 align:start position:0% data needs to reach its destination as soon<03:43:30.540> as<03:43:30.660> it's<03:43:30.840> been<03:43:31.080> generated<03:43:31.560> or<03:43:31.920> created 03:43:32.269 --> 03:43:32.279 align:start position:0% soon as it's been generated or created 03:43:32.279 --> 03:43:34.849 align:start position:0% soon as it's been generated or created and<03:43:33.000> we<03:43:33.180> don't<03:43:33.359> want<03:43:33.600> to<03:43:33.779> wait<03:43:34.200> for<03:43:34.439> it<03:43:34.560> to<03:43:34.739> be 03:43:34.849 --> 03:43:34.859 align:start position:0% and we don't want to wait for it to be 03:43:34.859 --> 03:43:36.769 align:start position:0% and we don't want to wait for it to be written<03:43:35.279> to<03:43:35.460> memory<03:43:35.760> or<03:43:35.939> written<03:43:36.239> to<03:43:36.420> a<03:43:36.600> hard 03:43:36.769 --> 03:43:36.779 align:start position:0% written to memory or written to a hard 03:43:36.779 --> 03:43:40.910 align:start position:0% written to memory or written to a hard drive<03:43:36.960> in<03:43:37.920> these<03:43:38.160> cases<03:43:38.580> instantaneous 03:43:40.910 --> 03:43:40.920 align:start position:0% drive in these cases instantaneous 03:43:40.920 --> 03:43:43.670 align:start position:0% drive in these cases instantaneous as<03:43:41.460> the<03:43:41.640> name<03:43:41.760> implies<03:43:42.239> being<03:43:42.660> instant<03:43:43.260> to<03:43:43.560> the 03:43:43.670 --> 03:43:43.680 align:start position:0% as the name implies being instant to the 03:43:43.680 --> 03:43:46.910 align:start position:0% as the name implies being instant to the moment<03:43:44.000> data<03:43:45.000> transfer<03:43:45.359> occurs<03:43:45.960> some 03:43:46.910 --> 03:43:46.920 align:start position:0% moment data transfer occurs some 03:43:46.920 --> 03:43:50.030 align:start position:0% moment data transfer occurs some programs<03:43:47.399> and<03:43:47.520> applications<03:43:48.060> such<03:43:49.020> as<03:43:49.439> online 03:43:50.030 --> 03:43:50.040 align:start position:0% programs and applications such as online 03:43:50.040 --> 03:43:53.090 align:start position:0% programs and applications such as online chat<03:43:50.760> uh<03:43:51.540> video<03:43:51.779> conferencing<03:43:52.560> and<03:43:52.859> voice 03:43:53.090 --> 03:43:53.100 align:start position:0% chat uh video conferencing and voice 03:43:53.100 --> 03:43:55.070 align:start position:0% chat uh video conferencing and voice conferencing<03:43:53.760> programs<03:43:54.300> all<03:43:54.600> via<03:43:54.899> the 03:43:55.070 --> 03:43:55.080 align:start position:0% conferencing programs all via the 03:43:55.080 --> 03:43:58.190 align:start position:0% conferencing programs all via the Internet<03:43:55.200> require<03:43:56.100> such<03:43:56.700> a<03:43:56.880> transfer<03:43:57.359> the 03:43:58.190 --> 03:43:58.200 align:start position:0% Internet require such a transfer the 03:43:58.200 --> 03:44:00.650 align:start position:0% Internet require such a transfer the this<03:43:58.560> method<03:43:59.100> of<03:43:59.399> data<03:43:59.880> transfer<03:44:00.359> doesn't 03:44:00.650 --> 03:44:00.660 align:start position:0% this method of data transfer doesn't 03:44:00.660 --> 03:44:03.229 align:start position:0% this method of data transfer doesn't store<03:44:01.080> the<03:44:01.380> data<03:44:01.739> at<03:44:02.399> any<03:44:02.580> point<03:44:02.880> before 03:44:03.229 --> 03:44:03.239 align:start position:0% store the data at any point before 03:44:03.239 --> 03:44:05.570 align:start position:0% store the data at any point before transmitting<03:44:04.080> it<03:44:04.260> to<03:44:04.680> memory 03:44:05.570 --> 03:44:05.580 align:start position:0% transmitting it to memory 03:44:05.580 --> 03:44:08.510 align:start position:0% transmitting it to memory instead<03:44:06.540> it<03:44:06.840> immediately<03:44:07.439> converts<03:44:08.220> that 03:44:08.510 --> 03:44:08.520 align:start position:0% instead it immediately converts that 03:44:08.520 --> 03:44:11.710 align:start position:0% instead it immediately converts that data<03:44:08.939> into<03:44:09.540> a<03:44:09.960> network<03:44:10.200> compatible<03:44:11.100> format 03:44:11.710 --> 03:44:11.720 align:start position:0% data into a network compatible format 03:44:11.720 --> 03:44:14.809 align:start position:0% data into a network compatible format and<03:44:12.720> as<03:44:12.960> it's<03:44:13.200> being<03:44:13.439> generated<03:44:13.979> and<03:44:14.520> then<03:44:14.640> it 03:44:14.809 --> 03:44:14.819 align:start position:0% and as it's being generated and then it 03:44:14.819 --> 03:44:17.090 align:start position:0% and as it's being generated and then it instantaneously<03:44:15.600> transmits<03:44:16.319> it<03:44:16.439> now<03:44:16.739> you<03:44:16.979> can 03:44:17.090 --> 03:44:17.100 align:start position:0% instantaneously transmits it now you can 03:44:17.100 --> 03:44:19.130 align:start position:0% instantaneously transmits it now you can understand<03:44:17.279> why<03:44:18.120> we<03:44:18.359> would<03:44:18.479> want<03:44:18.660> to<03:44:18.779> use<03:44:18.899> that 03:44:19.130 --> 03:44:19.140 align:start position:0% understand why we would want to use that 03:44:19.140 --> 03:44:21.349 align:start position:0% understand why we would want to use that in<03:44:19.319> these<03:44:19.620> specific<03:44:19.859> instances<03:44:20.399> I<03:44:21.060> don't<03:44:21.180> want 03:44:21.349 --> 03:44:21.359 align:start position:0% in these specific instances I don't want 03:44:21.359 --> 03:44:23.389 align:start position:0% in these specific instances I don't want to<03:44:21.540> store<03:44:21.840> my<03:44:22.200> chat<03:44:22.380> stuff<03:44:22.680> to<03:44:22.920> memory<03:44:23.220> and 03:44:23.389 --> 03:44:23.399 align:start position:0% to store my chat stuff to memory and 03:44:23.399 --> 03:44:25.309 align:start position:0% to store my chat stuff to memory and then<03:44:23.580> send<03:44:23.819> it<03:44:24.000> I<03:44:24.479> want<03:44:24.600> to<03:44:24.779> chat<03:44:25.020> and<03:44:25.200> then 03:44:25.309 --> 03:44:25.319 align:start position:0% then send it I want to chat and then 03:44:25.319 --> 03:44:26.690 align:start position:0% then send it I want to chat and then have<03:44:25.560> it<03:44:25.680> sent<03:44:25.920> same<03:44:26.340> with<03:44:26.520> video 03:44:26.690 --> 03:44:26.700 align:start position:0% have it sent same with video 03:44:26.700 --> 03:44:28.490 align:start position:0% have it sent same with video conferencing<03:44:27.180> or<03:44:27.359> voice<03:44:27.540> conferencing<03:44:28.140> I 03:44:28.490 --> 03:44:28.500 align:start position:0% conferencing or voice conferencing I 03:44:28.500 --> 03:44:30.050 align:start position:0% conferencing or voice conferencing I don't<03:44:28.560> want<03:44:28.739> the<03:44:28.920> lag<03:44:29.160> that's<03:44:29.399> going<03:44:29.580> to<03:44:29.700> occur 03:44:30.050 --> 03:44:30.060 align:start position:0% don't want the lag that's going to occur 03:44:30.060 --> 03:44:32.750 align:start position:0% don't want the lag that's going to occur due<03:44:30.899> to<03:44:31.020> having<03:44:31.500> to<03:44:31.680> save<03:44:31.859> it<03:44:32.040> to<03:44:32.160> memory<03:44:32.460> and 03:44:32.750 --> 03:44:32.760 align:start position:0% due to having to save it to memory and 03:44:32.760 --> 03:44:34.729 align:start position:0% due to having to save it to memory and then<03:44:32.880> save<03:44:33.120> it<03:44:33.359> and<03:44:33.720> then<03:44:33.840> send<03:44:34.080> it<03:44:34.260> which<03:44:34.620> is 03:44:34.729 --> 03:44:34.739 align:start position:0% then save it and then send it which is 03:44:34.739 --> 03:44:37.070 align:start position:0% then save it and then send it which is why<03:44:34.920> we<03:44:35.100> want<03:44:35.220> this<03:44:35.520> instantaneous<03:44:36.420> data 03:44:37.070 --> 03:44:37.080 align:start position:0% why we want this instantaneous data 03:44:37.080 --> 03:44:38.990 align:start position:0% why we want this instantaneous data transfer 03:44:38.990 --> 03:44:39.000 align:start position:0% transfer 03:44:39.000 --> 03:44:42.050 align:start position:0% transfer serial<03:44:39.840> data<03:44:40.319> transmission<03:44:40.640> is<03:44:41.640> a 03:44:42.050 --> 03:44:42.060 align:start position:0% serial data transmission is a 03:44:42.060 --> 03:44:45.410 align:start position:0% serial data transmission is a transmission<03:44:42.239> method<03:44:43.020> that<03:44:43.739> transmits<03:44:44.520> bits 03:44:45.410 --> 03:44:45.420 align:start position:0% transmission method that transmits bits 03:44:45.420 --> 03:44:48.650 align:start position:0% transmission method that transmits bits once<03:44:46.380> per<03:44:46.620> clock<03:44:46.979> cycle<03:44:47.399> now<03:44:48.000> this<03:44:48.359> clock 03:44:48.650 --> 03:44:48.660 align:start position:0% once per clock cycle now this clock 03:44:48.660 --> 03:44:52.550 align:start position:0% once per clock cycle now this clock cycle<03:44:49.160> refers<03:44:50.160> to<03:44:50.660> the<03:44:51.660> CPU<03:44:52.200> or<03:44:52.380> central 03:44:52.550 --> 03:44:52.560 align:start position:0% cycle refers to the CPU or central 03:44:52.560 --> 03:44:55.190 align:start position:0% cycle refers to the CPU or central processing<03:44:53.279> unit<03:44:53.460> of<03:44:53.700> the<03:44:53.819> computer<03:44:54.060> and<03:44:54.960> how 03:44:55.190 --> 03:44:55.200 align:start position:0% processing unit of the computer and how 03:44:55.200 --> 03:44:57.710 align:start position:0% processing unit of the computer and how that's<03:44:55.439> processing<03:44:56.100> information<03:44:56.479> and<03:44:57.479> as<03:44:57.600> you 03:44:57.710 --> 03:44:57.720 align:start position:0% that's processing information and as you 03:44:57.720 --> 03:44:59.510 align:start position:0% that's processing information and as you can<03:44:57.840> see<03:44:57.960> from<03:44:58.200> this<03:44:58.380> illustration<03:44:58.859> basically 03:44:59.510 --> 03:44:59.520 align:start position:0% can see from this illustration basically 03:44:59.520 --> 03:45:01.849 align:start position:0% can see from this illustration basically what<03:44:59.819> happens<03:45:00.000> is<03:45:00.300> we're<03:45:00.540> sending<03:45:01.020> one<03:45:01.680> of 03:45:01.849 --> 03:45:01.859 align:start position:0% what happens is we're sending one of 03:45:01.859 --> 03:45:03.530 align:start position:0% what happens is we're sending one of these<03:45:02.160> bits 03:45:03.530 --> 03:45:03.540 align:start position:0% these bits 03:45:03.540 --> 03:45:05.210 align:start position:0% these bits at<03:45:04.140> a<03:45:04.260> time 03:45:05.210 --> 03:45:05.220 align:start position:0% at a time 03:45:05.220 --> 03:45:07.370 align:start position:0% at a time and<03:45:05.640> if<03:45:05.819> you<03:45:05.939> recall 03:45:07.370 --> 03:45:07.380 align:start position:0% and if you recall 03:45:07.380 --> 03:45:11.090 align:start position:0% and if you recall one<03:45:08.340> byte<03:45:08.819> equals<03:45:09.479> eight<03:45:09.899> serial<03:45:10.439> bits<03:45:10.979> and 03:45:11.090 --> 03:45:11.100 align:start position:0% one byte equals eight serial bits and 03:45:11.100 --> 03:45:12.170 align:start position:0% one byte equals eight serial bits and that's<03:45:11.220> what<03:45:11.399> we're<03:45:11.520> going<03:45:11.640> to<03:45:11.760> call<03:45:11.880> eight 03:45:12.170 --> 03:45:12.180 align:start position:0% that's what we're going to call eight 03:45:12.180 --> 03:45:14.450 align:start position:0% that's what we're going to call eight serial<03:45:12.600> bits<03:45:12.960> one<03:45:13.200> byte<03:45:13.680> now<03:45:14.220> a<03:45:14.340> couple 03:45:14.450 --> 03:45:14.460 align:start position:0% serial bits one byte now a couple 03:45:14.460 --> 03:45:17.450 align:start position:0% serial bits one byte now a couple examples<03:45:15.120> of<03:45:15.420> what's<03:45:15.840> uh<03:45:16.439> of<03:45:16.800> what<03:45:17.040> uses 03:45:17.450 --> 03:45:17.460 align:start position:0% examples of what's uh of what uses 03:45:17.460 --> 03:45:19.670 align:start position:0% examples of what's uh of what uses serial<03:45:17.819> data<03:45:18.180> transmission<03:45:18.680> includes 03:45:19.670 --> 03:45:19.680 align:start position:0% serial data transmission includes 03:45:19.680 --> 03:45:22.670 align:start position:0% serial data transmission includes ethernet<03:45:20.460> as<03:45:21.300> well<03:45:21.479> as<03:45:21.779> some<03:45:22.200> peripheral 03:45:22.670 --> 03:45:22.680 align:start position:0% ethernet as well as some peripheral 03:45:22.680 --> 03:45:24.110 align:start position:0% ethernet as well as some peripheral devices<03:45:23.040> that<03:45:23.399> connect<03:45:23.520> to<03:45:23.760> our<03:45:23.939> computer 03:45:24.110 --> 03:45:24.120 align:start position:0% devices that connect to our computer 03:45:24.120 --> 03:45:27.769 align:start position:0% devices that connect to our computer like<03:45:24.540> mice<03:45:25.439> and<03:45:25.739> keyboards<03:45:26.460> now<03:45:27.120> with<03:45:27.359> serial 03:45:27.769 --> 03:45:27.779 align:start position:0% like mice and keyboards now with serial 03:45:27.779 --> 03:45:29.630 align:start position:0% like mice and keyboards now with serial data<03:45:28.200> Transmissions<03:45:28.800> there<03:45:29.220> are<03:45:29.340> different 03:45:29.630 --> 03:45:29.640 align:start position:0% data Transmissions there are different 03:45:29.640 --> 03:45:32.929 align:start position:0% data Transmissions there are different methods<03:45:30.359> that<03:45:30.899> can<03:45:31.080> be<03:45:31.319> used<03:45:31.620> to<03:45:32.279> delineate 03:45:32.929 --> 03:45:32.939 align:start position:0% methods that can be used to delineate 03:45:32.939 --> 03:45:36.050 align:start position:0% methods that can be used to delineate between<03:45:33.420> the<03:45:34.380> start<03:45:34.560> bit<03:45:34.859> and<03:45:35.460> the<03:45:35.640> stop<03:45:35.819> bit 03:45:36.050 --> 03:45:36.060 align:start position:0% between the start bit and the stop bit 03:45:36.060 --> 03:45:38.690 align:start position:0% between the start bit and the stop bit basically<03:45:36.660> how<03:45:37.080> they<03:45:37.319> know 03:45:38.690 --> 03:45:38.700 align:start position:0% basically how they know 03:45:38.700 --> 03:45:42.530 align:start position:0% basically how they know uh<03:45:39.540> what<03:45:39.960> where<03:45:40.380> the<03:45:40.680> data<03:45:41.040> begins<03:45:41.399> and<03:45:42.120> ends 03:45:42.530 --> 03:45:42.540 align:start position:0% uh what where the data begins and ends 03:45:42.540 --> 03:45:44.750 align:start position:0% uh what where the data begins and ends and<03:45:43.020> also<03:45:43.260> error<03:45:43.739> checking<03:45:44.100> or<03:45:44.279> correcting 03:45:44.750 --> 03:45:44.760 align:start position:0% and also error checking or correcting 03:45:44.760 --> 03:45:47.990 align:start position:0% and also error checking or correcting bits<03:45:45.120> that<03:45:45.239> allow<03:45:45.540> the<03:45:45.779> data<03:45:46.200> to<03:45:46.739> be<03:45:47.100> uh<03:45:47.580> fixed 03:45:47.990 --> 03:45:48.000 align:start position:0% bits that allow the data to be uh fixed 03:45:48.000 --> 03:45:50.809 align:start position:0% bits that allow the data to be uh fixed in<03:45:48.180> case<03:45:48.359> it<03:45:48.540> arrives<03:45:48.899> incorrectly<03:45:49.800> and<03:45:50.580> the 03:45:50.809 --> 03:45:50.819 align:start position:0% in case it arrives incorrectly and the 03:45:50.819 --> 03:45:53.210 align:start position:0% in case it arrives incorrectly and the data<03:45:51.120> itself<03:45:51.540> so<03:45:52.319> let's<03:45:52.439> take<03:45:52.620> a<03:45:52.739> look<03:45:52.859> at<03:45:53.100> the 03:45:53.210 --> 03:45:53.220 align:start position:0% data itself so let's take a look at the 03:45:53.220 --> 03:45:56.450 align:start position:0% data itself so let's take a look at the difference<03:45:53.399> between<03:45:54.439> synchronous<03:45:55.439> and<03:45:56.220> the 03:45:56.450 --> 03:45:56.460 align:start position:0% difference between synchronous and the 03:45:56.460 --> 03:45:59.030 align:start position:0% difference between synchronous and the asynchronous<03:45:57.120> methods<03:45:57.600> of<03:45:57.840> data<03:45:58.260> serial<03:45:58.620> data 03:45:59.030 --> 03:45:59.040 align:start position:0% asynchronous methods of data serial data 03:45:59.040 --> 03:46:00.410 align:start position:0% asynchronous methods of data serial data transmission 03:46:00.410 --> 03:46:00.420 align:start position:0% transmission 03:46:00.420 --> 03:46:03.550 align:start position:0% transmission synchronous<03:46:01.260> data<03:46:02.160> transmission 03:46:03.550 --> 03:46:03.560 align:start position:0% synchronous data transmission 03:46:03.560 --> 03:46:07.190 align:start position:0% synchronous data transmission utilizes<03:46:04.939> standardized<03:46:05.939> time<03:46:06.540> intervals 03:46:07.190 --> 03:46:07.200 align:start position:0% utilizes standardized time intervals 03:46:07.200 --> 03:46:09.950 align:start position:0% utilizes standardized time intervals when<03:46:07.800> transmitting<03:46:08.520> each<03:46:08.760> bit<03:46:08.939> now<03:46:09.720> the 03:46:09.950 --> 03:46:09.960 align:start position:0% when transmitting each bit now the 03:46:09.960 --> 03:46:12.710 align:start position:0% when transmitting each bit now the assumption<03:46:10.380> that<03:46:10.620> is<03:46:10.800> made<03:46:11.100> is<03:46:11.640> that<03:46:11.880> one<03:46:12.239> byte 03:46:12.710 --> 03:46:12.720 align:start position:0% assumption that is made is that one byte 03:46:12.720 --> 03:46:15.349 align:start position:0% assumption that is made is that one byte is<03:46:13.200> sent<03:46:13.439> every<03:46:13.859> interval<03:46:14.399> so<03:46:15.000> the<03:46:15.180> two 03:46:15.349 --> 03:46:15.359 align:start position:0% is sent every interval so the two 03:46:15.359 --> 03:46:17.269 align:start position:0% is sent every interval so the two devices<03:46:15.720> have<03:46:16.080> to<03:46:16.260> be<03:46:16.439> in<03:46:16.680> sync<03:46:16.979> with<03:46:17.100> each 03:46:17.269 --> 03:46:17.279 align:start position:0% devices have to be in sync with each 03:46:17.279 --> 03:46:19.130 align:start position:0% devices have to be in sync with each other<03:46:17.399> each<03:46:17.700> other<03:46:17.880> in<03:46:18.359> regards<03:46:18.779> to<03:46:18.960> their 03:46:19.130 --> 03:46:19.140 align:start position:0% other each other in regards to their 03:46:19.140 --> 03:46:22.210 align:start position:0% other each other in regards to their timing<03:46:19.560> a<03:46:20.340> clock<03:46:20.460> chip<03:46:20.819> therefore 03:46:22.210 --> 03:46:22.220 align:start position:0% timing a clock chip therefore 03:46:22.220 --> 03:46:25.309 align:start position:0% timing a clock chip therefore not<03:46:23.220> a<03:46:23.460> great<03:46:23.580> picture<03:46:23.819> of<03:46:24.120> it<03:46:24.239> but<03:46:24.660> imagine 03:46:25.309 --> 03:46:25.319 align:start position:0% not a great picture of it but imagine 03:46:25.319 --> 03:46:28.130 align:start position:0% not a great picture of it but imagine that<03:46:25.680> this<03:46:25.859> is<03:46:26.040> a<03:46:26.220> chip<03:46:26.399> is<03:46:27.239> needed<03:46:27.540> to<03:46:27.779> ensure 03:46:28.130 --> 03:46:28.140 align:start position:0% that this is a chip is needed to ensure 03:46:28.140 --> 03:46:29.990 align:start position:0% that this is a chip is needed to ensure that<03:46:28.380> the<03:46:28.560> devices<03:46:28.800> are<03:46:29.220> in<03:46:29.399> sync<03:46:29.700> with<03:46:29.819> one 03:46:29.990 --> 03:46:30.000 align:start position:0% that the devices are in sync with one 03:46:30.000 --> 03:46:32.750 align:start position:0% that the devices are in sync with one another<03:46:30.120> now<03:46:31.080> a<03:46:31.319> special<03:46:31.500> bit<03:46:31.859> pattern<03:46:32.340> is 03:46:32.750 --> 03:46:32.760 align:start position:0% another now a special bit pattern is 03:46:32.760 --> 03:46:35.210 align:start position:0% another now a special bit pattern is inserted<03:46:33.359> during<03:46:34.020> a<03:46:34.439> specified<03:46:34.800> time 03:46:35.210 --> 03:46:35.220 align:start position:0% inserted during a specified time 03:46:35.220 --> 03:46:37.370 align:start position:0% inserted during a specified time interval<03:46:35.760> to<03:46:36.479> maintain<03:46:36.899> this 03:46:37.370 --> 03:46:37.380 align:start position:0% interval to maintain this 03:46:37.380 --> 03:46:39.070 align:start position:0% interval to maintain this synchronization 03:46:39.070 --> 03:46:39.080 align:start position:0% synchronization 03:46:39.080 --> 03:46:41.990 align:start position:0% synchronization asynchronous<03:46:40.080> on<03:46:40.620> the<03:46:40.680> other<03:46:40.800> hand<03:46:41.040> uses 03:46:41.990 --> 03:46:42.000 align:start position:0% asynchronous on the other hand uses 03:46:42.000 --> 03:46:45.290 align:start position:0% asynchronous on the other hand uses special<03:46:42.359> start<03:46:42.840> and<03:46:43.140> stop<03:46:43.439> patterns<03:46:44.300> to 03:46:45.290 --> 03:46:45.300 align:start position:0% special start and stop patterns to 03:46:45.300 --> 03:46:47.389 align:start position:0% special start and stop patterns to differentiate<03:46:45.899> between<03:46:46.319> the<03:46:46.680> bytes<03:46:47.040> in<03:46:47.220> the 03:46:47.389 --> 03:46:47.399 align:start position:0% differentiate between the bytes in the 03:46:47.399 --> 03:46:50.030 align:start position:0% differentiate between the bytes in the data<03:46:47.700> Stream<03:46:47.819> So<03:46:48.720> the<03:46:48.960> receiver<03:46:49.260> just<03:46:49.620> has<03:46:49.800> to 03:46:50.030 --> 03:46:50.040 align:start position:0% data Stream So the receiver just has to 03:46:50.040 --> 03:46:52.250 align:start position:0% data Stream So the receiver just has to look<03:46:50.220> for<03:46:50.580> these<03:46:50.819> special<03:46:51.000> patterns<03:46:51.660> and<03:46:52.080> then 03:46:52.250 --> 03:46:52.260 align:start position:0% look for these special patterns and then 03:46:52.260 --> 03:46:54.110 align:start position:0% look for these special patterns and then can<03:46:52.500> easily<03:46:52.920> keep<03:46:53.160> track<03:46:53.460> of<03:46:53.700> whether<03:46:53.880> the 03:46:54.110 --> 03:46:54.120 align:start position:0% can easily keep track of whether the 03:46:54.120 --> 03:46:56.750 align:start position:0% can easily keep track of whether the data<03:46:54.420> has<03:46:54.600> been<03:46:54.779> successfully<03:46:55.500> received<03:46:56.100> so 03:46:56.750 --> 03:46:56.760 align:start position:0% data has been successfully received so 03:46:56.760 --> 03:46:58.610 align:start position:0% data has been successfully received so for<03:46:57.000> instance<03:46:57.239> the<03:46:57.540> pattern<03:46:57.840> might<03:46:58.080> be<03:46:58.260> one 03:46:58.610 --> 03:46:58.620 align:start position:0% for instance the pattern might be one 03:46:58.620 --> 03:47:02.510 align:start position:0% for instance the pattern might be one zero<03:46:58.979> one<03:46:59.160> zero<03:46:59.700> and<03:47:00.600> then<03:47:00.899> uh<03:47:01.800> or<03:47:01.979> one<03:47:02.220> zero 03:47:02.510 --> 03:47:02.520 align:start position:0% zero one zero and then uh or one zero 03:47:02.520 --> 03:47:04.610 align:start position:0% zero one zero and then uh or one zero one<03:47:02.580> zero<03:47:02.880> one<03:47:02.939> zero<03:47:03.239> one<03:47:03.359> zero<03:47:03.779> and<03:47:04.080> then<03:47:04.260> the 03:47:04.610 --> 03:47:04.620 align:start position:0% one zero one zero one zero and then the 03:47:04.620 --> 03:47:06.950 align:start position:0% one zero one zero one zero and then the device<03:47:04.859> knows<03:47:05.760> that<03:47:06.239> that<03:47:06.420> is<03:47:06.600> the<03:47:06.779> beginning 03:47:06.950 --> 03:47:06.960 align:start position:0% device knows that that is the beginning 03:47:06.960 --> 03:47:11.269 align:start position:0% device knows that that is the beginning or<03:47:07.380> the<03:47:07.560> end<03:47:07.800> of<03:47:08.640> a<03:47:08.939> pattern<03:47:09.420> of<03:47:09.720> bytes<03:47:10.260> of<03:47:10.380> data 03:47:11.269 --> 03:47:11.279 align:start position:0% or the end of a pattern of bytes of data 03:47:11.279 --> 03:47:13.370 align:start position:0% or the end of a pattern of bytes of data the<03:47:11.760> benefit<03:47:11.880> of<03:47:12.239> course<03:47:12.359> is<03:47:12.600> we<03:47:12.899> don't<03:47:13.020> need 03:47:13.370 --> 03:47:13.380 align:start position:0% the benefit of course is we don't need 03:47:13.380 --> 03:47:16.250 align:start position:0% the benefit of course is we don't need this<03:47:13.800> chip<03:47:14.040> because<03:47:14.760> the<03:47:15.600> start<03:47:15.840> and<03:47:16.020> stop 03:47:16.250 --> 03:47:16.260 align:start position:0% this chip because the start and stop 03:47:16.260 --> 03:47:18.710 align:start position:0% this chip because the start and stop times<03:47:16.500> are<03:47:16.979> built<03:47:17.340> automatically<03:47:18.000> into<03:47:18.359> the 03:47:18.710 --> 03:47:18.720 align:start position:0% times are built automatically into the 03:47:18.720 --> 03:47:20.269 align:start position:0% times are built automatically into the data<03:47:19.020> itself 03:47:20.269 --> 03:47:20.279 align:start position:0% data itself 03:47:20.279 --> 03:47:22.370 align:start position:0% data itself now<03:47:20.700> stepping<03:47:21.120> away<03:47:21.180> from<03:47:21.540> serial<03:47:21.960> data 03:47:22.370 --> 03:47:22.380 align:start position:0% now stepping away from serial data 03:47:22.380 --> 03:47:23.290 align:start position:0% now stepping away from serial data transmission 03:47:23.290 --> 03:47:23.300 align:start position:0% transmission 03:47:23.300 --> 03:47:26.690 align:start position:0% transmission parallel<03:47:24.300> data<03:47:24.779> transmission<03:47:25.020> is<03:47:25.920> a<03:47:26.160> transmit 03:47:26.690 --> 03:47:26.700 align:start position:0% parallel data transmission is a transmit 03:47:26.700 --> 03:47:29.690 align:start position:0% parallel data transmission is a transmit Mission<03:47:27.180> method<03:47:27.720> that<03:47:28.140> uses<03:47:28.739> multiple 03:47:29.690 --> 03:47:29.700 align:start position:0% Mission method that uses multiple 03:47:29.700 --> 03:47:33.170 align:start position:0% Mission method that uses multiple transmission<03:47:30.239> lines<03:47:31.279> wires<03:47:32.279> or<03:47:32.640> cables 03:47:33.170 --> 03:47:33.180 align:start position:0% transmission lines wires or cables 03:47:33.180 --> 03:47:35.510 align:start position:0% transmission lines wires or cables simultaneously<03:47:34.140> unlike<03:47:35.100> serial 03:47:35.510 --> 03:47:35.520 align:start position:0% simultaneously unlike serial 03:47:35.520 --> 03:47:37.790 align:start position:0% simultaneously unlike serial transmission<03:47:35.760> that<03:47:36.420> sends<03:47:36.840> start<03:47:37.140> and<03:47:37.500> stop 03:47:37.790 --> 03:47:37.800 align:start position:0% transmission that sends start and stop 03:47:37.800 --> 03:47:40.670 align:start position:0% transmission that sends start and stop and<03:47:38.399> synchronization<03:47:39.180> bits<03:47:39.720> along<03:47:40.080> with<03:47:40.439> the 03:47:40.670 --> 03:47:40.680 align:start position:0% and synchronization bits along with the 03:47:40.680 --> 03:47:43.070 align:start position:0% and synchronization bits along with the data<03:47:40.979> parallel<03:47:41.819> does<03:47:42.060> not<03:47:42.239> and<03:47:42.600> doesn't<03:47:42.779> have 03:47:43.070 --> 03:47:43.080 align:start position:0% data parallel does not and doesn't have 03:47:43.080 --> 03:47:46.670 align:start position:0% data parallel does not and doesn't have to<03:47:43.260> those<03:47:44.160> bits<03:47:44.580> are<03:47:44.939> sent<03:47:45.180> separately<03:47:45.840> via 03:47:46.670 --> 03:47:46.680 align:start position:0% to those bits are sent separately via 03:47:46.680 --> 03:47:49.849 align:start position:0% to those bits are sent separately via one<03:47:46.920> of<03:47:47.040> these<03:47:47.399> multiple<03:47:48.060> other<03:47:48.859> different 03:47:49.849 --> 03:47:49.859 align:start position:0% one of these multiple other different 03:47:49.859 --> 03:47:52.429 align:start position:0% one of these multiple other different transmission<03:47:50.460> lines<03:47:51.239> other<03:47:51.660> than<03:47:51.899> the<03:47:52.080> data 03:47:52.429 --> 03:47:52.439 align:start position:0% transmission lines other than the data 03:47:52.439 --> 03:47:55.130 align:start position:0% transmission lines other than the data because<03:47:53.220> of<03:47:53.520> this<03:47:53.700> throughput<03:47:54.300> is<03:47:54.779> generally 03:47:55.130 --> 03:47:55.140 align:start position:0% because of this throughput is generally 03:47:55.140 --> 03:47:57.910 align:start position:0% because of this throughput is generally better<03:47:55.560> than<03:47:56.100> standard<03:47:56.760> serial<03:47:57.239> transmission 03:47:57.910 --> 03:47:57.920 align:start position:0% better than standard serial transmission 03:47:57.920 --> 03:48:02.150 align:start position:0% better than standard serial transmission and<03:47:58.920> these<03:47:59.600> eight<03:48:00.600> of<03:48:00.899> these<03:48:01.260> parallel<03:48:01.800> bits 03:48:02.150 --> 03:48:02.160 align:start position:0% and these eight of these parallel bits 03:48:02.160 --> 03:48:04.790 align:start position:0% and these eight of these parallel bits are<03:48:02.640> referred<03:48:03.060> to<03:48:03.120> as<03:48:03.479> a<03:48:03.899> character<03:48:04.200> as 03:48:04.790 --> 03:48:04.800 align:start position:0% are referred to as a character as 03:48:04.800 --> 03:48:07.849 align:start position:0% are referred to as a character as opposed<03:48:05.220> to<03:48:05.279> a<03:48:05.760> byte<03:48:06.120> now<03:48:06.720> some<03:48:06.960> examples<03:48:07.439> that 03:48:07.849 --> 03:48:07.859 align:start position:0% opposed to a byte now some examples that 03:48:07.859 --> 03:48:11.050 align:start position:0% opposed to a byte now some examples that use<03:48:08.160> parallel<03:48:09.060> transmission<03:48:09.779> are<03:48:10.439> scuzzy 03:48:11.050 --> 03:48:11.060 align:start position:0% use parallel transmission are scuzzy 03:48:11.060 --> 03:48:15.190 align:start position:0% use parallel transmission are scuzzy parallel<03:48:12.060> ports<03:48:12.600> PC<03:48:13.319> card<03:48:13.620> or 03:48:15.190 --> 03:48:15.200 align:start position:0% parallel ports PC card or 03:48:15.200 --> 03:48:18.530 align:start position:0% parallel ports PC card or pcmcia<03:48:16.200> remember<03:48:17.040> piece<03:48:17.700> parallel<03:48:18.180> ports 03:48:18.530 --> 03:48:18.540 align:start position:0% pcmcia remember piece parallel ports 03:48:18.540 --> 03:48:20.870 align:start position:0% pcmcia remember piece parallel ports those<03:48:18.720> are<03:48:18.840> those<03:48:19.020> printer<03:48:19.439> ports 03:48:20.870 --> 03:48:20.880 align:start position:0% those are those printer ports 03:48:20.880 --> 03:48:23.090 align:start position:0% those are those printer ports and<03:48:21.540> may<03:48:21.720> all<03:48:21.960> use<03:48:22.200> parallel<03:48:22.739> data 03:48:23.090 --> 03:48:23.100 align:start position:0% and may all use parallel data 03:48:23.100 --> 03:48:26.330 align:start position:0% and may all use parallel data transmission<03:48:23.300> it's<03:48:24.300> not<03:48:24.720> as<03:48:25.200> used<03:48:25.620> or<03:48:25.979> widely 03:48:26.330 --> 03:48:26.340 align:start position:0% transmission it's not as used or widely 03:48:26.340 --> 03:48:29.450 align:start position:0% transmission it's not as used or widely used<03:48:26.520> as<03:48:27.120> a<03:48:27.779> serial<03:48:28.200> data<03:48:28.620> transmission<03:48:28.800> is 03:48:29.450 --> 03:48:29.460 align:start position:0% used as a serial data transmission is 03:48:29.460 --> 03:48:32.150 align:start position:0% used as a serial data transmission is now<03:48:30.359> that<03:48:30.540> deals<03:48:30.840> with<03:48:31.020> how<03:48:31.380> the<03:48:31.560> data<03:48:31.859> is<03:48:31.979> sent 03:48:32.150 --> 03:48:32.160 align:start position:0% now that deals with how the data is sent 03:48:32.160 --> 03:48:35.389 align:start position:0% now that deals with how the data is sent let's<03:48:32.399> deal<03:48:32.700> with<03:48:32.880> the<03:48:33.120> type<03:48:33.359> of<03:48:34.399> signal 03:48:35.389 --> 03:48:35.399 align:start position:0% let's deal with the type of signal 03:48:35.399 --> 03:48:36.889 align:start position:0% let's deal with the type of signal that's<03:48:35.640> sent 03:48:36.889 --> 03:48:36.899 align:start position:0% that's sent 03:48:36.899 --> 03:48:40.250 align:start position:0% that's sent in<03:48:37.500> baseband's<03:48:38.279> transmission<03:48:38.700> this<03:48:39.479> utilizes 03:48:40.250 --> 03:48:40.260 align:start position:0% in baseband's transmission this utilizes 03:48:40.260 --> 03:48:43.309 align:start position:0% in baseband's transmission this utilizes digital<03:48:40.859> signals<03:48:41.520> sent<03:48:42.239> via<03:48:42.720> a<03:48:43.140> direct 03:48:43.309 --> 03:48:43.319 align:start position:0% digital signals sent via a direct 03:48:43.319 --> 03:48:45.229 align:start position:0% digital signals sent via a direct current<03:48:43.859> pulse<03:48:44.460> and<03:48:44.640> remember<03:48:44.760> we're<03:48:45.060> talking 03:48:45.229 --> 03:48:45.239 align:start position:0% current pulse and remember we're talking 03:48:45.239 --> 03:48:47.210 align:start position:0% current pulse and remember we're talking about<03:48:45.420> direct<03:48:45.779> current<03:48:46.140> versus<03:48:46.439> alternating 03:48:47.210 --> 03:48:47.220 align:start position:0% about direct current versus alternating 03:48:47.220 --> 03:48:50.030 align:start position:0% about direct current versus alternating current<03:48:47.479> with<03:48:48.479> base<03:48:48.779> bands<03:48:49.319> all<03:48:49.620> the<03:48:49.739> devices 03:48:50.030 --> 03:48:50.040 align:start position:0% current with base bands all the devices 03:48:50.040 --> 03:48:53.570 align:start position:0% current with base bands all the devices share<03:48:50.640> the<03:48:50.880> same<03:48:51.120> medium<03:48:51.720> or<03:48:52.500> Channel<03:48:52.739> and 03:48:53.570 --> 03:48:53.580 align:start position:0% share the same medium or Channel and 03:48:53.580 --> 03:48:55.330 align:start position:0% share the same medium or Channel and can't<03:48:53.880> transmit<03:48:54.660> and<03:48:55.020> receive 03:48:55.330 --> 03:48:55.340 align:start position:0% can't transmit and receive 03:48:55.340 --> 03:48:59.269 align:start position:0% can't transmit and receive simultaneously<03:48:56.479> however<03:48:57.680> multiple<03:48:58.680> baseband 03:48:59.269 --> 03:48:59.279 align:start position:0% simultaneously however multiple baseband 03:48:59.279 --> 03:49:02.630 align:start position:0% simultaneously however multiple baseband channels<03:48:59.819> can<03:49:00.180> be<03:49:00.359> combined<03:49:01.080> over<03:49:01.680> one<03:49:02.100> medium 03:49:02.630 --> 03:49:02.640 align:start position:0% channels can be combined over one medium 03:49:02.640 --> 03:49:06.530 align:start position:0% channels can be combined over one medium to<03:49:03.479> use<03:49:03.720> a<03:49:04.080> channel<03:49:04.200> separated<03:49:04.939> with<03:49:05.939> specific 03:49:06.530 --> 03:49:06.540 align:start position:0% to use a channel separated with specific 03:49:06.540 --> 03:49:08.870 align:start position:0% to use a channel separated with specific time<03:49:07.080> slots<03:49:07.560> and<03:49:08.160> that's<03:49:08.340> how<03:49:08.580> we<03:49:08.700> can 03:49:08.870 --> 03:49:08.880 align:start position:0% time slots and that's how we can 03:49:08.880 --> 03:49:10.969 align:start position:0% time slots and that's how we can determine<03:49:09.359> when<03:49:09.720> it's<03:49:09.840> being<03:49:10.080> sent<03:49:10.380> and<03:49:10.800> when 03:49:10.969 --> 03:49:10.979 align:start position:0% determine when it's being sent and when 03:49:10.979 --> 03:49:12.950 align:start position:0% determine when it's being sent and when it's<03:49:11.100> being<03:49:11.279> received<03:49:11.819> one<03:49:12.300> thing<03:49:12.479> to<03:49:12.600> notice 03:49:12.950 --> 03:49:12.960 align:start position:0% it's being received one thing to notice 03:49:12.960 --> 03:49:15.530 align:start position:0% it's being received one thing to notice in<03:49:13.319> a<03:49:13.439> digital<03:49:13.680> signal<03:49:14.100> as<03:49:14.279> well<03:49:14.520> is<03:49:15.239> that 03:49:15.530 --> 03:49:15.540 align:start position:0% in a digital signal as well is that 03:49:15.540 --> 03:49:18.530 align:start position:0% in a digital signal as well is that we're<03:49:15.960> only<03:49:16.200> dealing<03:49:16.560> with<03:49:16.739> ones<03:49:17.279> or<03:49:17.580> zeros<03:49:18.000> on 03:49:18.530 --> 03:49:18.540 align:start position:0% we're only dealing with ones or zeros on 03:49:18.540 --> 03:49:23.630 align:start position:0% we're only dealing with ones or zeros on and<03:49:18.840> off<03:49:19.020> and<03:49:19.800> so<03:49:20.040> the<03:49:20.819> signal<03:49:21.120> is<03:49:21.239> either<03:49:21.479> on 03:49:23.630 --> 03:49:23.640 align:start position:0% and off and so the signal is either on 03:49:23.640 --> 03:49:27.349 align:start position:0% and off and so the signal is either on or<03:49:24.239> off<03:49:24.540> there's<03:49:25.500> no<03:49:25.859> sort<03:49:26.100> of<03:49:26.279> wave<03:49:27.000> that 03:49:27.349 --> 03:49:27.359 align:start position:0% or off there's no sort of wave that 03:49:27.359 --> 03:49:29.090 align:start position:0% or off there's no sort of wave that we're<03:49:27.420> gonna<03:49:27.540> get<03:49:27.779> with<03:49:28.140> the<03:49:28.319> analog<03:49:28.739> signal 03:49:29.090 --> 03:49:29.100 align:start position:0% we're gonna get with the analog signal 03:49:29.100 --> 03:49:32.090 align:start position:0% we're gonna get with the analog signal which<03:49:29.220> we'll<03:49:29.399> see<03:49:29.580> right<03:49:29.880> now 03:49:32.090 --> 03:49:32.100 align:start position:0% 03:49:32.100 --> 03:49:35.030 align:start position:0% so<03:49:32.700> where<03:49:33.000> baseband<03:49:33.779> used<03:49:34.260> those<03:49:34.680> digital 03:49:35.030 --> 03:49:35.040 align:start position:0% so where baseband used those digital 03:49:35.040 --> 03:49:37.429 align:start position:0% so where baseband used those digital signals<03:49:35.520> to<03:49:35.700> transmit<03:49:36.120> data<03:49:36.479> broadband's 03:49:37.429 --> 03:49:37.439 align:start position:0% signals to transmit data broadband's 03:49:37.439 --> 03:49:39.530 align:start position:0% signals to transmit data broadband's going<03:49:37.620> to<03:49:37.739> use<03:49:37.920> analog<03:49:38.640> signals<03:49:39.120> and<03:49:39.239> you<03:49:39.420> can 03:49:39.530 --> 03:49:39.540 align:start position:0% going to use analog signals and you can 03:49:39.540 --> 03:49:42.530 align:start position:0% going to use analog signals and you can see<03:49:39.720> that<03:49:39.960> represented<03:49:40.620> in<03:49:40.920> this<03:49:41.100> wave<03:49:41.540> also 03:49:42.530 --> 03:49:42.540 align:start position:0% see that represented in this wave also 03:49:42.540 --> 03:49:45.710 align:start position:0% see that represented in this wave also unlike<03:49:42.960> baseband<03:49:43.739> Broadband<03:49:44.640> utilizes<03:49:45.359> the 03:49:45.710 --> 03:49:45.720 align:start position:0% unlike baseband Broadband utilizes the 03:49:45.720 --> 03:49:48.530 align:start position:0% unlike baseband Broadband utilizes the entire<03:49:46.200> bandwidth<03:49:47.100> available<03:49:47.399> and<03:49:48.239> it's<03:49:48.359> only 03:49:48.530 --> 03:49:48.540 align:start position:0% entire bandwidth available and it's only 03:49:48.540 --> 03:49:50.990 align:start position:0% entire bandwidth available and it's only going<03:49:48.779> to<03:49:48.899> travel<03:49:49.080> in<03:49:49.620> one<03:49:49.859> direction<03:49:50.040> or 03:49:50.990 --> 03:49:51.000 align:start position:0% going to travel in one direction or 03:49:51.000 --> 03:49:53.450 align:start position:0% going to travel in one direction or unidirectionally<03:49:51.960> because<03:49:52.500> devices<03:49:53.100> can't 03:49:53.450 --> 03:49:53.460 align:start position:0% unidirectionally because devices can't 03:49:53.460 --> 03:49:55.309 align:start position:0% unidirectionally because devices can't send<03:49:53.760> and<03:49:54.000> receive<03:49:54.300> over<03:49:54.600> the<03:49:54.899> same<03:49:55.080> channel 03:49:55.309 --> 03:49:55.319 align:start position:0% send and receive over the same channel 03:49:55.319 --> 03:49:58.790 align:start position:0% send and receive over the same channel now<03:49:56.220> if<03:49:56.460> more<03:49:56.700> throughput<03:49:57.239> is<03:49:57.720> needed<03:49:58.140> that's 03:49:58.790 --> 03:49:58.800 align:start position:0% now if more throughput is needed that's 03:49:58.800 --> 03:50:01.969 align:start position:0% now if more throughput is needed that's fine<03:49:59.100> we<03:49:59.880> can<03:50:00.060> combine<03:50:00.779> and<03:50:01.260> send<03:50:01.500> across 03:50:01.969 --> 03:50:01.979 align:start position:0% fine we can combine and send across 03:50:01.979 --> 03:50:05.150 align:start position:0% fine we can combine and send across multiple<03:50:02.460> frequencies<03:50:03.239> channels<03:50:04.080> or<03:50:04.739> we<03:50:05.040> can 03:50:05.150 --> 03:50:05.160 align:start position:0% multiple frequencies channels or we can 03:50:05.160 --> 03:50:07.370 align:start position:0% multiple frequencies channels or we can use<03:50:05.399> over<03:50:05.760> just<03:50:06.060> one<03:50:06.300> medium 03:50:07.370 --> 03:50:07.380 align:start position:0% use over just one medium 03:50:07.380 --> 03:50:09.830 align:start position:0% use over just one medium generally<03:50:08.220> speaking<03:50:08.819> we're<03:50:09.239> going<03:50:09.420> to<03:50:09.540> see<03:50:09.660> a 03:50:09.830 --> 03:50:09.840 align:start position:0% generally speaking we're going to see a 03:50:09.840 --> 03:50:13.250 align:start position:0% generally speaking we're going to see a lot<03:50:09.960> of<03:50:10.140> broadband<03:50:10.920> in<03:50:11.279> the<03:50:11.399> field<03:50:11.580> because<03:50:12.260> a 03:50:13.250 --> 03:50:13.260 align:start position:0% lot of broadband in the field because a 03:50:13.260 --> 03:50:15.830 align:start position:0% lot of broadband in the field because a lot<03:50:13.439> of<03:50:13.620> our<03:50:13.920> current<03:50:14.340> infrastructure<03:50:15.180> was 03:50:15.830 --> 03:50:15.840 align:start position:0% lot of our current infrastructure was 03:50:15.840 --> 03:50:19.370 align:start position:0% lot of our current infrastructure was created<03:50:16.200> for<03:50:16.680> analog<03:50:17.640> signals<03:50:18.420> as<03:50:18.960> opposed<03:50:19.380> to 03:50:19.370 --> 03:50:19.380 align:start position:0% created for analog signals as opposed to 03:50:19.380 --> 03:50:22.910 align:start position:0% created for analog signals as opposed to digital<03:50:20.340> or<03:50:20.580> baseband<03:50:21.180> signals<03:50:22.319> now 03:50:22.910 --> 03:50:22.920 align:start position:0% digital or baseband signals now 03:50:22.920 --> 03:50:27.889 align:start position:0% digital or baseband signals now Broadband<03:50:23.760> over<03:50:24.239> power<03:50:24.779> lines<03:50:25.200> or<03:50:26.040> BPL<03:50:26.700> is<03:50:27.660> an 03:50:27.889 --> 03:50:27.899 align:start position:0% Broadband over power lines or BPL is an 03:50:27.899 --> 03:50:31.190 align:start position:0% Broadband over power lines or BPL is an emerging<03:50:28.380> technology<03:50:28.920> that<03:50:29.520> still<03:50:29.939> mostly<03:50:30.660> in 03:50:31.190 --> 03:50:31.200 align:start position:0% emerging technology that still mostly in 03:50:31.200 --> 03:50:34.429 align:start position:0% emerging technology that still mostly in the<03:50:31.439> testing<03:50:31.800> phases<03:50:32.220> in<03:50:32.520> the<03:50:32.640> US<03:50:33.080> the<03:50:34.080> premise 03:50:34.429 --> 03:50:34.439 align:start position:0% the testing phases in the US the premise 03:50:34.439 --> 03:50:37.370 align:start position:0% the testing phases in the US the premise of<03:50:34.680> it<03:50:34.800> is<03:50:35.160> that<03:50:35.399> we<03:50:36.000> can<03:50:36.180> essentially<03:50:36.720> bring 03:50:37.370 --> 03:50:37.380 align:start position:0% of it is that we can essentially bring 03:50:37.380 --> 03:50:39.429 align:start position:0% of it is that we can essentially bring high-speed<03:50:38.160> internet 03:50:39.429 --> 03:50:39.439 align:start position:0% high-speed internet 03:50:39.439 --> 03:50:43.550 align:start position:0% high-speed internet two<03:50:40.439> power<03:50:40.800> outlets<03:50:41.420> using<03:50:42.420> the<03:50:42.840> power<03:50:43.140> lines 03:50:43.550 --> 03:50:43.560 align:start position:0% two power outlets using the power lines 03:50:43.560 --> 03:50:45.050 align:start position:0% two power outlets using the power lines and<03:50:43.859> the<03:50:44.040> infrastructure<03:50:44.520> that's<03:50:44.819> already 03:50:45.050 --> 03:50:45.060 align:start position:0% and the infrastructure that's already 03:50:45.060 --> 03:50:47.929 align:start position:0% and the infrastructure that's already been<03:50:45.359> built<03:50:45.859> once<03:50:46.859> this<03:50:47.040> technology<03:50:47.340> is<03:50:47.640> fully 03:50:47.929 --> 03:50:47.939 align:start position:0% been built once this technology is fully 03:50:47.939 --> 03:50:50.389 align:start position:0% been built once this technology is fully developed<03:50:48.300> you<03:50:48.600> would<03:50:48.779> be<03:50:48.960> able<03:50:49.200> to<03:50:49.380> plug<03:50:50.160> your 03:50:50.389 --> 03:50:50.399 align:start position:0% developed you would be able to plug your 03:50:50.399 --> 03:50:52.130 align:start position:0% developed you would be able to plug your computer<03:50:50.580> into<03:50:50.939> a<03:50:51.239> power<03:50:51.359> outlet<03:50:51.600> in<03:50:51.960> your 03:50:52.130 --> 03:50:52.140 align:start position:0% computer into a power outlet in your 03:50:52.140 --> 03:50:54.530 align:start position:0% computer into a power outlet in your home<03:50:52.319> and<03:50:52.859> you<03:50:52.979> can<03:50:53.040> get<03:50:53.279> decently<03:50:53.880> fast 03:50:54.530 --> 03:50:54.540 align:start position:0% home and you can get decently fast 03:50:54.540 --> 03:50:57.050 align:start position:0% home and you can get decently fast internet<03:50:54.960> between<03:50:55.500> 500<03:50:56.100> kilobits<03:50:56.760> per<03:50:56.880> second 03:50:57.050 --> 03:50:57.060 align:start position:0% internet between 500 kilobits per second 03:50:57.060 --> 03:50:59.450 align:start position:0% internet between 500 kilobits per second and<03:50:57.420> three<03:50:57.660> megabits<03:50:58.319> per<03:50:58.439> second<03:50:58.680> which<03:50:59.279> are 03:50:59.450 --> 03:50:59.460 align:start position:0% and three megabits per second which are 03:50:59.460 --> 03:51:02.750 align:start position:0% and three megabits per second which are about<03:50:59.700> equivalent<03:51:00.479> to<03:51:00.739> DSL<03:51:01.739> or<03:51:01.979> cable<03:51:02.220> speeds 03:51:02.750 --> 03:51:02.760 align:start position:0% about equivalent to DSL or cable speeds 03:51:02.760 --> 03:51:05.150 align:start position:0% about equivalent to DSL or cable speeds now<03:51:03.479> of<03:51:03.660> course<03:51:03.779> the<03:51:04.200> main<03:51:04.380> concern<03:51:04.739> with<03:51:04.979> this 03:51:05.150 --> 03:51:05.160 align:start position:0% now of course the main concern with this 03:51:05.160 --> 03:51:07.729 align:start position:0% now of course the main concern with this type<03:51:05.279> of<03:51:05.399> transmission<03:51:05.779> is<03:51:06.779> a<03:51:07.260> the<03:51:07.560> effect 03:51:07.729 --> 03:51:07.739 align:start position:0% type of transmission is a the effect 03:51:07.739 --> 03:51:09.830 align:start position:0% type of transmission is a the effect that<03:51:08.340> the<03:51:08.819> uh<03:51:09.060> since<03:51:09.300> we're<03:51:09.420> dealing<03:51:09.720> with 03:51:09.830 --> 03:51:09.840 align:start position:0% that the uh since we're dealing with 03:51:09.840 --> 03:51:11.809 align:start position:0% that the uh since we're dealing with electrical<03:51:10.439> interest<03:51:10.680> infrastructure<03:51:11.520> the 03:51:11.809 --> 03:51:11.819 align:start position:0% electrical interest infrastructure the 03:51:11.819 --> 03:51:13.550 align:start position:0% electrical interest infrastructure the effect<03:51:12.000> that<03:51:12.239> the<03:51:12.479> electricity<03:51:13.020> is<03:51:13.260> going<03:51:13.439> to 03:51:13.550 --> 03:51:13.560 align:start position:0% effect that the electricity is going to 03:51:13.560 --> 03:51:16.010 align:start position:0% effect that the electricity is going to cause<03:51:13.939> uh<03:51:14.939> on 03:51:16.010 --> 03:51:16.020 align:start position:0% cause uh on 03:51:16.020 --> 03:51:19.250 align:start position:0% cause uh on uh<03:51:16.680> the<03:51:16.979> data<03:51:17.279> being<03:51:17.520> sent<03:51:17.819> remember<03:51:18.779> we<03:51:19.080> were 03:51:19.250 --> 03:51:19.260 align:start position:0% uh the data being sent remember we were 03:51:19.260 --> 03:51:21.710 align:start position:0% uh the data being sent remember we were talking<03:51:19.439> about<03:51:19.680> Emi<03:51:20.399> and<03:51:20.640> crosstalk<03:51:21.120> and<03:51:21.479> the 03:51:21.710 --> 03:51:21.720 align:start position:0% talking about Emi and crosstalk and the 03:51:21.720 --> 03:51:25.309 align:start position:0% talking about Emi and crosstalk and the noise<03:51:22.020> issue<03:51:22.979> previously<03:51:23.580> and<03:51:24.300> also<03:51:24.660> security 03:51:25.309 --> 03:51:25.319 align:start position:0% noise issue previously and also security 03:51:25.319 --> 03:51:27.349 align:start position:0% noise issue previously and also security since<03:51:25.800> if<03:51:26.040> we're<03:51:26.220> using<03:51:26.700> something<03:51:27.120> that 03:51:27.349 --> 03:51:27.359 align:start position:0% since if we're using something that 03:51:27.359 --> 03:51:29.450 align:start position:0% since if we're using something that everyone<03:51:27.540> has<03:51:27.779> access<03:51:28.020> to<03:51:28.439> we're<03:51:29.040> also<03:51:29.340> going 03:51:29.450 --> 03:51:29.460 align:start position:0% everyone has access to we're also going 03:51:29.460 --> 03:51:32.630 align:start position:0% everyone has access to we're also going to<03:51:29.700> be<03:51:29.880> opening<03:51:30.840> our<03:51:31.020> data<03:51:31.380> up<03:51:31.560> to<03:51:31.920> some<03:51:32.160> issues 03:51:32.630 --> 03:51:32.640 align:start position:0% to be opening our data up to some issues 03:51:32.640 --> 03:51:35.150 align:start position:0% to be opening our data up to some issues so<03:51:33.239> for<03:51:33.420> these<03:51:33.720> reasons<03:51:34.200> we<03:51:34.560> might<03:51:34.739> not<03:51:34.920> ever 03:51:35.150 --> 03:51:35.160 align:start position:0% so for these reasons we might not ever 03:51:35.160 --> 03:51:37.849 align:start position:0% so for these reasons we might not ever see<03:51:35.460> BPL<03:51:35.939> or<03:51:36.420> Broadband<03:51:36.899> over<03:51:37.200> power<03:51:37.560> lines 03:51:37.849 --> 03:51:37.859 align:start position:0% see BPL or Broadband over power lines 03:51:37.859 --> 03:51:40.370 align:start position:0% see BPL or Broadband over power lines really<03:51:38.220> come<03:51:38.520> to<03:51:38.700> full<03:51:38.880> fruition<03:51:39.380> especially 03:51:40.370 --> 03:51:40.380 align:start position:0% really come to full fruition especially 03:51:40.380 --> 03:51:42.650 align:start position:0% really come to full fruition especially with<03:51:40.680> the<03:51:40.859> prevalence<03:51:41.340> of<03:51:42.120> Wi-Fi 03:51:42.650 --> 03:51:42.660 align:start position:0% with the prevalence of Wi-Fi 03:51:42.660 --> 03:51:46.190 align:start position:0% with the prevalence of Wi-Fi technologies<03:51:43.439> that<03:51:44.279> are<03:51:44.520> now<03:51:44.880> becoming<03:51:45.540> uh 03:51:46.190 --> 03:51:46.200 align:start position:0% technologies that are now becoming uh 03:51:46.200 --> 03:51:48.290 align:start position:0% technologies that are now becoming uh installed<03:51:46.920> all<03:51:47.100> over<03:51:47.220> the<03:51:47.460> place<03:51:47.640> and<03:51:48.120> might 03:51:48.290 --> 03:51:48.300 align:start position:0% installed all over the place and might 03:51:48.300 --> 03:51:51.469 align:start position:0% installed all over the place and might make<03:51:48.540> BPL<03:51:49.040> extinct<03:51:50.040> before<03:51:50.279> it<03:51:50.520> even<03:51:50.640> has<03:51:50.939> a 03:51:51.469 --> 03:51:51.479 align:start position:0% make BPL extinct before it even has a 03:51:51.479 --> 03:51:53.870 align:start position:0% make BPL extinct before it even has a chance<03:51:51.720> to<03:51:51.960> flourish 03:51:53.870 --> 03:51:53.880 align:start position:0% chance to flourish 03:51:53.880 --> 03:51:55.969 align:start position:0% chance to flourish so<03:51:54.359> just<03:51:54.540> to<03:51:54.720> cover<03:51:54.899> what<03:51:55.140> we've<03:51:55.439> talked<03:51:55.859> about 03:51:55.969 --> 03:51:55.979 align:start position:0% so just to cover what we've talked about 03:51:55.979 --> 03:51:59.330 align:start position:0% so just to cover what we've talked about we<03:51:56.819> talked<03:51:57.060> about<03:51:57.120> data<03:51:57.960> transmission<03:51:58.340> uh 03:51:59.330 --> 03:51:59.340 align:start position:0% we talked about data transmission uh 03:51:59.340 --> 03:52:01.849 align:start position:0% we talked about data transmission uh meaning<03:51:59.580> that<03:51:59.939> we're<03:52:00.300> transferring<03:52:01.200> data 03:52:01.849 --> 03:52:01.859 align:start position:0% meaning that we're transferring data 03:52:01.859 --> 03:52:04.729 align:start position:0% meaning that we're transferring data over<03:52:02.100> a<03:52:02.460> computer<03:52:02.640> or<03:52:03.060> a<03:52:03.180> Data<03:52:03.540> Network<03:52:03.739> we 03:52:04.729 --> 03:52:04.739 align:start position:0% over a computer or a Data Network we 03:52:04.739 --> 03:52:07.309 align:start position:0% over a computer or a Data Network we looked<03:52:05.040> at<03:52:05.180> instantaneous<03:52:06.180> data<03:52:06.840> transfer 03:52:07.309 --> 03:52:07.319 align:start position:0% looked at instantaneous data transfer 03:52:07.319 --> 03:52:10.790 align:start position:0% looked at instantaneous data transfer which<03:52:07.979> means<03:52:08.520> that<03:52:09.060> the<03:52:09.239> data<03:52:09.600> is<03:52:09.960> not<03:52:10.380> stored 03:52:10.790 --> 03:52:10.800 align:start position:0% which means that the data is not stored 03:52:10.800 --> 03:52:16.790 align:start position:0% which means that the data is not stored to<03:52:10.979> memory 03:52:16.790 --> 03:52:16.800 align:start position:0% 03:52:16.800 --> 03:52:19.130 align:start position:0% we<03:52:17.279> also<03:52:17.520> talked<03:52:17.880> about<03:52:17.939> serial<03:52:18.720> data 03:52:19.130 --> 03:52:19.140 align:start position:0% we also talked about serial data 03:52:19.140 --> 03:52:23.150 align:start position:0% we also talked about serial data transmission<03:52:19.399> in<03:52:20.399> which<03:52:20.640> one<03:52:21.359> bit<03:52:21.720> is<03:52:22.500> sent<03:52:22.739> at 03:52:23.150 --> 03:52:23.160 align:start position:0% transmission in which one bit is sent at 03:52:23.160 --> 03:52:25.010 align:start position:0% transmission in which one bit is sent at a<03:52:23.279> time 03:52:25.010 --> 03:52:25.020 align:start position:0% a time 03:52:25.020 --> 03:52:28.670 align:start position:0% a time and<03:52:25.620> remember<03:52:25.800> we<03:52:26.279> have<03:52:26.580> eight<03:52:27.300> bits 03:52:28.670 --> 03:52:28.680 align:start position:0% and remember we have eight bits 03:52:28.680 --> 03:52:31.670 align:start position:0% and remember we have eight bits in<03:52:29.279> a<03:52:29.399> byte 03:52:31.670 --> 03:52:31.680 align:start position:0% in a byte 03:52:31.680 --> 03:52:34.370 align:start position:0% in a byte we<03:52:32.100> looked<03:52:32.399> at<03:52:32.899> asynchronous<03:52:33.899> versus 03:52:34.370 --> 03:52:34.380 align:start position:0% we looked at asynchronous versus 03:52:34.380 --> 03:52:36.969 align:start position:0% we looked at asynchronous versus synchronous<03:52:35.100> communication<03:52:35.720> synchronous 03:52:36.969 --> 03:52:36.979 align:start position:0% synchronous communication synchronous 03:52:36.979 --> 03:52:40.190 align:start position:0% synchronous communication synchronous requires<03:52:37.979> some<03:52:38.220> sort<03:52:38.399> of<03:52:38.520> clock<03:52:38.880> chip<03:52:39.300> whereas 03:52:40.190 --> 03:52:40.200 align:start position:0% requires some sort of clock chip whereas 03:52:40.200 --> 03:52:44.030 align:start position:0% requires some sort of clock chip whereas asynchronous<03:52:41.040> embeds 03:52:44.030 --> 03:52:44.040 align:start position:0% 03:52:44.040 --> 03:52:47.690 align:start position:0% start<03:52:44.460> and<03:52:44.760> stop 03:52:47.690 --> 03:52:47.700 align:start position:0% 03:52:47.700 --> 03:52:54.469 align:start position:0% into<03:52:48.180> the<03:52:48.479> transfer 03:52:54.469 --> 03:52:54.479 align:start position:0% 03:52:54.479 --> 03:52:56.630 align:start position:0% we<03:52:54.899> also<03:52:55.140> looked<03:52:55.380> at<03:52:55.500> parallel<03:52:56.279> data 03:52:56.630 --> 03:52:56.640 align:start position:0% we also looked at parallel data 03:52:56.640 --> 03:53:00.410 align:start position:0% we also looked at parallel data transmission<03:52:57.319> having<03:52:58.460> bits<03:52:59.460> sent<03:52:59.819> all 03:53:00.410 --> 03:53:00.420 align:start position:0% transmission having bits sent all 03:53:00.420 --> 03:53:04.610 align:start position:0% transmission having bits sent all concurrently<03:53:01.020> at<03:53:01.380> the<03:53:01.560> same<03:53:01.800> time<03:53:02.100> not<03:53:03.060> as<03:53:03.620> not 03:53:04.610 --> 03:53:04.620 align:start position:0% concurrently at the same time not as not 03:53:04.620 --> 03:53:07.250 align:start position:0% concurrently at the same time not as not as<03:53:04.859> widely<03:53:05.279> used<03:53:05.580> and<03:53:06.300> remember<03:53:06.479> although<03:53:07.140> I 03:53:07.250 --> 03:53:07.260 align:start position:0% as widely used and remember although I 03:53:07.260 --> 03:53:09.110 align:start position:0% as widely used and remember although I don't<03:53:07.380> think<03:53:07.500> you'll<03:53:07.739> see<03:53:07.920> this 03:53:09.110 --> 03:53:09.120 align:start position:0% don't think you'll see this 03:53:09.120 --> 03:53:13.550 align:start position:0% don't think you'll see this on<03:53:09.840> the<03:53:09.960> exam<03:53:10.319> eight<03:53:11.220> parallel<03:53:12.000> bits 03:53:13.550 --> 03:53:13.560 align:start position:0% on the exam eight parallel bits 03:53:13.560 --> 03:53:17.809 align:start position:0% on the exam eight parallel bits equal<03:53:14.220> one<03:53:14.640> what<03:53:15.120> we<03:53:15.239> call<03:53:15.420> a<03:53:15.840> character 03:53:17.809 --> 03:53:17.819 align:start position:0% equal one what we call a character 03:53:17.819 --> 03:53:20.090 align:start position:0% equal one what we call a character we<03:53:18.300> also<03:53:18.479> looked<03:53:18.779> at<03:53:18.899> baseband<03:53:19.620> transmission 03:53:20.090 --> 03:53:20.100 align:start position:0% we also looked at baseband transmission 03:53:20.100 --> 03:53:22.370 align:start position:0% we also looked at baseband transmission the<03:53:20.700> important<03:53:21.000> thing<03:53:21.180> to<03:53:21.359> remember<03:53:21.479> there<03:53:21.840> is 03:53:22.370 --> 03:53:22.380 align:start position:0% the important thing to remember there is 03:53:22.380 --> 03:53:24.650 align:start position:0% the important thing to remember there is that<03:53:22.560> it<03:53:22.680> is<03:53:22.859> digital<03:53:23.340> and<03:53:24.120> Broadband 03:53:24.650 --> 03:53:24.660 align:start position:0% that it is digital and Broadband 03:53:24.660 --> 03:53:28.370 align:start position:0% that it is digital and Broadband transmission<03:53:25.340> which<03:53:26.340> is<03:53:26.520> analog 03:53:28.370 --> 03:53:28.380 align:start position:0% transmission which is analog 03:53:28.380 --> 03:53:33.889 align:start position:0% transmission which is analog finally<03:53:29.040> we<03:53:29.340> talked<03:53:29.580> about<03:53:29.700> BPL<03:53:30.680> or<03:53:31.680> broadband 03:53:33.889 --> 03:53:33.899 align:start position:0% finally we talked about BPL or broadband 03:53:33.899 --> 03:53:36.710 align:start position:0% finally we talked about BPL or broadband over<03:53:34.439> power<03:53:34.920> lines<03:53:35.279> which<03:53:36.000> is<03:53:36.120> a<03:53:36.359> technology 03:53:36.710 --> 03:53:36.720 align:start position:0% over power lines which is a technology 03:53:36.720 --> 03:53:39.530 align:start position:0% over power lines which is a technology that<03:53:37.020> would<03:53:37.200> bring<03:53:37.439> Broadband<03:53:38.220> speeds<03:53:38.939> over 03:53:39.530 --> 03:53:39.540 align:start position:0% that would bring Broadband speeds over 03:53:39.540 --> 03:53:41.450 align:start position:0% that would bring Broadband speeds over the<03:53:39.840> power<03:53:40.020> lines<03:53:40.319> that<03:53:40.620> are<03:53:40.800> already<03:53:41.040> in 03:53:41.450 --> 03:53:41.460 align:start position:0% the power lines that are already in 03:53:41.460 --> 03:53:45.880 align:start position:0% the power lines that are already in place 03:53:45.880 --> 03:53:45.890 align:start position:0% 03:53:45.890 --> 03:53:54.490 align:start position:0% [Music] 03:53:54.490 --> 03:53:54.500 align:start position:0% [Music] 03:53:54.500 --> 03:54:05.830 align:start position:0% [Music] thank<03:53:55.500> you 03:54:05.830 --> 03:54:05.840 align:start position:0% 03:54:05.840 --> 03:54:09.349 align:start position:0% network<03:54:06.840> communications<03:54:08.120> media<03:54:09.120> access 03:54:09.349 --> 03:54:09.359 align:start position:0% network communications media access 03:54:09.359 --> 03:54:11.630 align:start position:0% network communications media access methods 03:54:11.630 --> 03:54:11.640 align:start position:0% methods 03:54:11.640 --> 03:54:14.570 align:start position:0% methods so<03:54:12.180> we've<03:54:12.720> discussed<03:54:13.380> and<03:54:13.620> explained<03:54:14.279> the 03:54:14.570 --> 03:54:14.580 align:start position:0% so we've discussed and explained the 03:54:14.580 --> 03:54:16.010 align:start position:0% so we've discussed and explained the different<03:54:14.760> media<03:54:15.239> and<03:54:15.720> the<03:54:15.840> different 03:54:16.010 --> 03:54:16.020 align:start position:0% different media and the different 03:54:16.020 --> 03:54:18.710 align:start position:0% different media and the different devices<03:54:16.500> that<03:54:16.920> exist<03:54:17.279> on<03:54:17.700> different<03:54:18.060> types<03:54:18.600> of 03:54:18.710 --> 03:54:18.720 align:start position:0% devices that exist on different types of 03:54:18.720 --> 03:54:21.229 align:start position:0% devices that exist on different types of networks<03:54:19.260> and<03:54:19.979> we<03:54:20.279> even<03:54:20.460> just<03:54:20.819> talked<03:54:21.180> about 03:54:21.229 --> 03:54:21.239 align:start position:0% networks and we even just talked about 03:54:21.239 --> 03:54:23.510 align:start position:0% networks and we even just talked about how<03:54:21.899> that<03:54:22.080> data<03:54:22.500> is<03:54:22.620> transferred<03:54:23.160> from<03:54:23.340> point 03:54:23.510 --> 03:54:23.520 align:start position:0% how that data is transferred from point 03:54:23.520 --> 03:54:25.729 align:start position:0% how that data is transferred from point A<03:54:23.699> to<03:54:23.880> point<03:54:24.000> B<03:54:24.239> but<03:54:25.080> we<03:54:25.199> have<03:54:25.319> a<03:54:25.500> lot<03:54:25.620> of 03:54:25.729 --> 03:54:25.739 align:start position:0% A to point B but we have a lot of 03:54:25.739 --> 03:54:27.950 align:start position:0% A to point B but we have a lot of different<03:54:26.040> devices<03:54:26.580> of<03:54:26.880> buying<03:54:27.420> for<03:54:27.660> access 03:54:27.950 --> 03:54:27.960 align:start position:0% different devices of buying for access 03:54:27.960 --> 03:54:30.290 align:start position:0% different devices of buying for access to<03:54:28.500> this<03:54:28.680> media<03:54:28.979> in<03:54:29.160> order<03:54:29.340> to<03:54:29.460> send<03:54:29.699> its<03:54:30.000> data 03:54:30.290 --> 03:54:30.300 align:start position:0% to this media in order to send its data 03:54:30.300 --> 03:54:32.570 align:start position:0% to this media in order to send its data and<03:54:30.840> so<03:54:31.020> we<03:54:31.319> need<03:54:31.439> to<03:54:31.560> create<03:54:31.680> certain<03:54:32.100> rules 03:54:32.570 --> 03:54:32.580 align:start position:0% and so we need to create certain rules 03:54:32.580 --> 03:54:35.510 align:start position:0% and so we need to create certain rules that<03:54:32.880> provide<03:54:33.300> access<03:54:33.779> to<03:54:34.319> the<03:54:34.560> media<03:54:34.859> and<03:54:35.399> so 03:54:35.510 --> 03:54:35.520 align:start position:0% that provide access to the media and so 03:54:35.520 --> 03:54:37.070 align:start position:0% that provide access to the media and so what<03:54:35.699> we're<03:54:35.819> going<03:54:35.939> to<03:54:36.060> talk<03:54:36.239> about<03:54:36.359> in<03:54:36.899> this 03:54:37.070 --> 03:54:37.080 align:start position:0% what we're going to talk about in this 03:54:37.080 --> 03:54:41.450 align:start position:0% what we're going to talk about in this module<03:54:37.500> is<03:54:38.100> first<03:54:38.340> what<03:54:39.239> media<03:54:39.779> access<03:54:40.020> is<03:54:40.500> and 03:54:41.450 --> 03:54:41.460 align:start position:0% module is first what media access is and 03:54:41.460 --> 03:54:42.950 align:start position:0% module is first what media access is and why<03:54:41.640> we<03:54:41.880> need<03:54:42.000> it<03:54:42.180> and<03:54:42.300> why<03:54:42.479> we<03:54:42.660> need<03:54:42.779> to 03:54:42.950 --> 03:54:42.960 align:start position:0% why we need it and why we need to 03:54:42.960 --> 03:54:45.229 align:start position:0% why we need it and why we need to understand<03:54:43.199> it<03:54:43.680> for<03:54:44.340> the<03:54:44.460> network<03:54:44.520> plus<03:54:44.819> exam 03:54:45.229 --> 03:54:45.239 align:start position:0% understand it for the network plus exam 03:54:45.239 --> 03:54:47.750 align:start position:0% understand it for the network plus exam and<03:54:45.600> as<03:54:45.840> administrators<03:54:46.620> we're<03:54:47.399> also<03:54:47.640> going 03:54:47.750 --> 03:54:47.760 align:start position:0% and as administrators we're also going 03:54:47.760 --> 03:54:51.349 align:start position:0% and as administrators we're also going to<03:54:47.880> describe<03:54:48.500> two<03:54:49.500> different<03:54:49.859> barrage 03:54:51.349 --> 03:54:51.359 align:start position:0% to describe two different barrage 03:54:51.359 --> 03:54:54.050 align:start position:0% to describe two different barrage areas<03:54:52.260> of<03:54:52.560> media<03:54:52.920> access<03:54:53.100> including 03:54:54.050 --> 03:54:54.060 align:start position:0% areas of media access including 03:54:54.060 --> 03:54:57.849 align:start position:0% areas of media access including contention<03:54:54.840> based<03:54:55.800> media<03:54:56.399> access<03:54:56.660> versus 03:54:57.849 --> 03:54:57.859 align:start position:0% contention based media access versus 03:54:57.859 --> 03:55:01.130 align:start position:0% contention based media access versus controlled<03:54:58.859> media<03:54:59.279> access<03:54:59.420> one<03:55:00.420> in<03:55:00.720> which<03:55:00.840> we 03:55:01.130 --> 03:55:01.140 align:start position:0% controlled media access one in which we 03:55:01.140 --> 03:55:03.950 align:start position:0% controlled media access one in which we sort<03:55:01.319> of<03:55:01.439> fight<03:55:01.800> for<03:55:02.220> access<03:55:02.460> to<03:55:02.760> the<03:55:02.939> media<03:55:03.239> uh 03:55:03.950 --> 03:55:03.960 align:start position:0% sort of fight for access to the media uh 03:55:03.960 --> 03:55:05.929 align:start position:0% sort of fight for access to the media uh contend<03:55:04.380> for<03:55:04.620> it<03:55:04.800> if<03:55:04.979> you<03:55:05.100> will<03:55:05.220> and<03:55:05.760> the<03:55:05.880> other 03:55:05.929 --> 03:55:05.939 align:start position:0% contend for it if you will and the other 03:55:05.939 --> 03:55:08.210 align:start position:0% contend for it if you will and the other in<03:55:06.180> which<03:55:06.300> it<03:55:06.479> is<03:55:06.660> controlled<03:55:07.260> generally<03:55:07.800> by 03:55:08.210 --> 03:55:08.220 align:start position:0% in which it is controlled generally by 03:55:08.220 --> 03:55:10.910 align:start position:0% in which it is controlled generally by some<03:55:08.580> sort<03:55:08.819> of<03:55:08.939> central<03:55:09.600> device 03:55:10.910 --> 03:55:10.920 align:start position:0% some sort of central device 03:55:10.920 --> 03:55:13.429 align:start position:0% some sort of central device and<03:55:11.460> then<03:55:11.520> we're<03:55:11.699> going<03:55:11.880> to<03:55:12.000> Define<03:55:12.439> uh 03:55:13.429 --> 03:55:13.439 align:start position:0% and then we're going to Define uh 03:55:13.439 --> 03:55:15.710 align:start position:0% and then we're going to Define uh multiplexing<03:55:14.340> which<03:55:14.760> allows<03:55:15.120> us<03:55:15.239> to<03:55:15.540> send 03:55:15.710 --> 03:55:15.720 align:start position:0% multiplexing which allows us to send 03:55:15.720 --> 03:55:17.990 align:start position:0% multiplexing which allows us to send multiple<03:55:16.260> signals<03:55:16.800> over<03:55:17.040> a<03:55:17.340> single<03:55:17.640> medium 03:55:17.990 --> 03:55:18.000 align:start position:0% multiple signals over a single medium 03:55:18.000 --> 03:55:19.969 align:start position:0% multiple signals over a single medium and<03:55:18.540> we're<03:55:18.660> going<03:55:18.840> to<03:55:18.960> talk<03:55:19.140> about<03:55:19.319> two 03:55:19.969 --> 03:55:19.979 align:start position:0% and we're going to talk about two 03:55:19.979 --> 03:55:22.729 align:start position:0% and we're going to talk about two different<03:55:20.220> types<03:55:20.760> of<03:55:20.939> multiplexing<03:55:21.779> time 03:55:22.729 --> 03:55:22.739 align:start position:0% different types of multiplexing time 03:55:22.739 --> 03:55:25.809 align:start position:0% different types of multiplexing time division<03:55:23.399> multiplexing 03:55:25.809 --> 03:55:25.819 align:start position:0% division multiplexing 03:55:25.819 --> 03:55:32.990 align:start position:0% division multiplexing and<03:55:26.819> frequency<03:55:27.540> division<03:55:28.500> multiplexing 03:55:32.990 --> 03:55:33.000 align:start position:0% 03:55:33.000 --> 03:55:35.750 align:start position:0% and<03:55:33.420> we'll<03:55:33.540> discuss<03:55:33.840> how<03:55:34.319> those<03:55:34.560> work<03:55:34.920> and<03:55:35.520> why 03:55:35.750 --> 03:55:35.760 align:start position:0% and we'll discuss how those work and why 03:55:35.760 --> 03:55:37.670 align:start position:0% and we'll discuss how those work and why we<03:55:35.939> need<03:55:36.060> two<03:55:36.239> different<03:55:36.420> ones 03:55:37.670 --> 03:55:37.680 align:start position:0% we need two different ones 03:55:37.680 --> 03:55:40.130 align:start position:0% we need two different ones then<03:55:38.160> we're<03:55:38.340> going<03:55:38.460> to<03:55:38.520> discuss<03:55:39.140> polling 03:55:40.130 --> 03:55:40.140 align:start position:0% then we're going to discuss polling 03:55:40.140 --> 03:55:43.010 align:start position:0% then we're going to discuss polling which<03:55:40.979> is<03:55:41.100> how<03:55:41.399> we<03:55:41.760> check<03:55:42.180> to<03:55:42.479> see<03:55:42.720> which 03:55:43.010 --> 03:55:43.020 align:start position:0% which is how we check to see which 03:55:43.020 --> 03:55:45.110 align:start position:0% which is how we check to see which devices<03:55:43.380> need<03:55:43.739> to<03:55:43.920> send 03:55:45.110 --> 03:55:45.120 align:start position:0% devices need to send 03:55:45.120 --> 03:55:46.790 align:start position:0% devices need to send um 03:55:46.790 --> 03:55:46.800 align:start position:0% um 03:55:46.800 --> 03:55:48.650 align:start position:0% um data 03:55:48.650 --> 03:55:48.660 align:start position:0% data 03:55:48.660 --> 03:55:51.309 align:start position:0% data and<03:55:49.020> we're<03:55:49.140> going<03:55:49.260> to<03:55:49.319> differentiate<03:55:50.040> between 03:55:51.309 --> 03:55:51.319 align:start position:0% and we're going to differentiate between 03:55:51.319 --> 03:55:56.330 align:start position:0% and we're going to differentiate between csma<03:55:52.319> CD<03:55:53.100> and<03:55:53.699> CA<03:55:54.239> now<03:55:54.720> csma<03:55:55.500> you<03:55:56.040> don't<03:55:56.220> really 03:55:56.330 --> 03:55:56.340 align:start position:0% csma CD and CA now csma you don't really 03:55:56.340 --> 03:55:58.070 align:start position:0% csma CD and CA now csma you don't really need<03:55:56.580> to<03:55:56.640> worry<03:55:57.000> about<03:55:57.239> that<03:55:57.479> but<03:55:57.779> it<03:55:57.960> does 03:55:58.070 --> 03:55:58.080 align:start position:0% need to worry about that but it does 03:55:58.080 --> 03:56:00.650 align:start position:0% need to worry about that but it does stand<03:55:58.319> for<03:55:58.680> carrier 03:56:00.650 --> 03:56:00.660 align:start position:0% stand for carrier 03:56:00.660 --> 03:56:02.750 align:start position:0% stand for carrier sense 03:56:02.750 --> 03:56:02.760 align:start position:0% sense 03:56:02.760 --> 03:56:07.070 align:start position:0% sense multiple<03:56:03.660> access 03:56:07.070 --> 03:56:07.080 align:start position:0% 03:56:07.080 --> 03:56:09.050 align:start position:0% but<03:56:07.560> the<03:56:07.739> real<03:56:07.859> important<03:56:08.279> thing<03:56:08.520> here<03:56:08.760> is<03:56:08.880> to 03:56:09.050 --> 03:56:09.060 align:start position:0% but the real important thing here is to 03:56:09.060 --> 03:56:10.670 align:start position:0% but the real important thing here is to know<03:56:09.180> the<03:56:09.359> difference<03:56:09.479> between<03:56:09.720> Collision 03:56:10.670 --> 03:56:10.680 align:start position:0% know the difference between Collision 03:56:10.680 --> 03:56:14.889 align:start position:0% know the difference between Collision detection 03:56:14.889 --> 03:56:14.899 align:start position:0% 03:56:14.899 --> 03:56:18.950 align:start position:0% and<03:56:15.899> collision<03:56:16.880> avoidance<03:56:17.880> and<03:56:18.600> these<03:56:18.840> are 03:56:18.950 --> 03:56:18.960 align:start position:0% and collision avoidance and these are 03:56:18.960 --> 03:56:20.889 align:start position:0% and collision avoidance and these are the<03:56:19.140> two<03:56:19.319> main<03:56:19.500> methods<03:56:19.920> we're<03:56:20.100> going<03:56:20.279> to<03:56:20.399> see 03:56:20.889 --> 03:56:20.899 align:start position:0% the two main methods we're going to see 03:56:20.899 --> 03:56:25.969 align:start position:0% the two main methods we're going to see uh<03:56:21.899> for<03:56:22.439> ethernet 03:56:25.969 --> 03:56:25.979 align:start position:0% 03:56:25.979 --> 03:56:28.729 align:start position:0% and<03:56:26.520> then<03:56:26.640> for<03:56:27.300> wireless<03:56:27.720> and<03:56:28.319> we'll<03:56:28.500> explain 03:56:28.729 --> 03:56:28.739 align:start position:0% and then for wireless and we'll explain 03:56:28.739 --> 03:56:33.010 align:start position:0% and then for wireless and we'll explain why<03:56:29.399> that<03:56:29.640> is<03:56:29.880> later<03:56:30.600> on 03:56:33.010 --> 03:56:33.020 align:start position:0% 03:56:33.020 --> 03:56:35.570 align:start position:0% finally<03:56:34.020> we<03:56:34.319> need<03:56:34.439> to<03:56:34.620> differentiate<03:56:35.220> between 03:56:35.570 --> 03:56:35.580 align:start position:0% finally we need to differentiate between 03:56:35.580 --> 03:56:38.929 align:start position:0% finally we need to differentiate between a<03:56:36.300> contention<03:56:36.720> contention<03:56:37.500> domain<03:56:38.160> and<03:56:38.760> a 03:56:38.929 --> 03:56:38.939 align:start position:0% a contention contention domain and a 03:56:38.939 --> 03:56:41.929 align:start position:0% a contention contention domain and a broadcast<03:56:39.120> domain<03:56:39.840> basically<03:56:40.680> uh<03:56:41.279> how<03:56:41.699> large 03:56:41.929 --> 03:56:41.939 align:start position:0% broadcast domain basically uh how large 03:56:41.939 --> 03:56:45.010 align:start position:0% broadcast domain basically uh how large or<03:56:42.239> how<03:56:42.479> many<03:56:42.600> other<03:56:42.960> devices<03:56:43.500> they<03:56:44.399> need<03:56:44.640> to 03:56:45.010 --> 03:56:45.020 align:start position:0% or how many other devices they need to 03:56:45.020 --> 03:56:47.689 align:start position:0% or how many other devices they need to contend<03:56:46.020> against<03:56:46.260> or<03:56:47.100> that<03:56:47.340> can<03:56:47.520> get 03:56:47.689 --> 03:56:47.699 align:start position:0% contend against or that can get 03:56:47.699 --> 03:56:50.090 align:start position:0% contend against or that can get broadcast<03:56:48.000> a<03:56:48.540> certain<03:56:48.720> message<03:56:49.080> and<03:56:49.800> these 03:56:50.090 --> 03:56:50.100 align:start position:0% broadcast a certain message and these 03:56:50.100 --> 03:56:51.950 align:start position:0% broadcast a certain message and these are<03:56:50.220> also<03:56:50.520> divided<03:56:51.060> by<03:56:51.300> those<03:56:51.600> two<03:56:51.779> different 03:56:51.950 --> 03:56:51.960 align:start position:0% are also divided by those two different 03:56:51.960 --> 03:56:55.189 align:start position:0% are also divided by those two different devices<03:56:52.319> that<03:56:52.680> keep<03:56:52.920> coming<03:56:53.160> up<03:56:53.399> switches<03:56:54.359> and 03:56:55.189 --> 03:56:55.199 align:start position:0% devices that keep coming up switches and 03:56:55.199 --> 03:56:56.750 align:start position:0% devices that keep coming up switches and routers 03:56:56.750 --> 03:56:56.760 align:start position:0% routers 03:56:56.760 --> 03:56:58.849 align:start position:0% routers so<03:56:57.120> if<03:56:57.239> that<03:56:57.420> seems<03:56:57.720> confusing<03:56:58.260> enough<03:56:58.500> to<03:56:58.739> you 03:56:58.849 --> 03:56:58.859 align:start position:0% so if that seems confusing enough to you 03:56:58.859 --> 03:57:00.950 align:start position:0% so if that seems confusing enough to you let's<03:56:59.279> delve<03:56:59.699> in<03:56:59.880> in<03:57:00.060> order<03:57:00.239> to<03:57:00.479> shed<03:57:00.779> some 03:57:00.950 --> 03:57:00.960 align:start position:0% let's delve in in order to shed some 03:57:00.960 --> 03:57:03.950 align:start position:0% let's delve in in order to shed some light<03:57:01.199> on<03:57:01.620> what<03:57:01.859> all<03:57:02.040> of<03:57:02.160> this<03:57:02.340> is<03:57:02.580> now<03:57:03.359> as 03:57:03.950 --> 03:57:03.960 align:start position:0% light on what all of this is now as 03:57:03.960 --> 03:57:05.570 align:start position:0% light on what all of this is now as administrators<03:57:04.620> it's<03:57:04.920> really<03:57:05.100> important 03:57:05.570 --> 03:57:05.580 align:start position:0% administrators it's really important 03:57:05.580 --> 03:57:08.269 align:start position:0% administrators it's really important that<03:57:05.939> we<03:57:06.300> understand<03:57:06.540> the<03:57:07.380> rules<03:57:07.739> that<03:57:07.979> are<03:57:08.160> in 03:57:08.269 --> 03:57:08.279 align:start position:0% that we understand the rules that are in 03:57:08.279 --> 03:57:10.790 align:start position:0% that we understand the rules that are in place<03:57:08.520> for<03:57:09.000> different<03:57:09.239> types<03:57:10.020> of<03:57:10.199> networks 03:57:10.790 --> 03:57:10.800 align:start position:0% place for different types of networks 03:57:10.800 --> 03:57:13.670 align:start position:0% place for different types of networks for<03:57:11.520> instance<03:57:11.760> if<03:57:12.420> I<03:57:12.660> were<03:57:12.779> in<03:57:12.960> a<03:57:13.140> crowded<03:57:13.500> room 03:57:13.670 --> 03:57:13.680 align:start position:0% for instance if I were in a crowded room 03:57:13.680 --> 03:57:16.849 align:start position:0% for instance if I were in a crowded room and<03:57:14.520> I<03:57:14.699> had<03:57:15.000> a<03:57:15.359> secret<03:57:15.540> message<03:57:16.020> that<03:57:16.439> I<03:57:16.620> needed 03:57:16.849 --> 03:57:16.859 align:start position:0% and I had a secret message that I needed 03:57:16.859 --> 03:57:19.010 align:start position:0% and I had a secret message that I needed to<03:57:17.040> get<03:57:17.399> across<03:57:17.880> to<03:57:18.060> someone<03:57:18.300> in<03:57:18.660> the<03:57:18.779> corner 03:57:19.010 --> 03:57:19.020 align:start position:0% to get across to someone in the corner 03:57:19.020 --> 03:57:21.050 align:start position:0% to get across to someone in the corner of<03:57:19.140> the<03:57:19.319> room<03:57:19.439> and<03:57:19.979> I<03:57:20.100> were<03:57:20.220> just<03:57:20.399> to<03:57:20.580> shout<03:57:20.819> out 03:57:21.050 --> 03:57:21.060 align:start position:0% of the room and I were just to shout out 03:57:21.060 --> 03:57:23.510 align:start position:0% of the room and I were just to shout out that<03:57:21.420> message<03:57:21.660> there's<03:57:22.500> no<03:57:22.739> rules<03:57:23.100> in<03:57:23.399> the 03:57:23.510 --> 03:57:23.520 align:start position:0% that message there's no rules in the 03:57:23.520 --> 03:57:25.550 align:start position:0% that message there's no rules in the world<03:57:23.640> that<03:57:24.000> say<03:57:24.180> everyone<03:57:24.420> else<03:57:24.720> has<03:57:25.140> to 03:57:25.550 --> 03:57:25.560 align:start position:0% world that say everyone else has to 03:57:25.560 --> 03:57:27.650 align:start position:0% world that say everyone else has to ignore<03:57:26.100> what<03:57:26.399> I'm<03:57:26.580> saying<03:57:26.939> and<03:57:27.359> they<03:57:27.540> could 03:57:27.650 --> 03:57:27.660 align:start position:0% ignore what I'm saying and they could 03:57:27.660 --> 03:57:30.110 align:start position:0% ignore what I'm saying and they could just<03:57:27.840> listen<03:57:28.100> or<03:57:29.100> or<03:57:29.279> there's<03:57:29.699> nothing<03:57:29.939> that 03:57:30.110 --> 03:57:30.120 align:start position:0% just listen or or there's nothing that 03:57:30.120 --> 03:57:31.910 align:start position:0% just listen or or there's nothing that says<03:57:30.420> that<03:57:30.540> everyone<03:57:30.779> else<03:57:31.020> couldn't<03:57:31.319> talk<03:57:31.620> at 03:57:31.910 --> 03:57:31.920 align:start position:0% says that everyone else couldn't talk at 03:57:31.920 --> 03:57:34.010 align:start position:0% says that everyone else couldn't talk at the<03:57:32.040> same<03:57:32.220> time<03:57:32.580> meaning<03:57:33.300> that<03:57:33.540> then<03:57:33.720> my 03:57:34.010 --> 03:57:34.020 align:start position:0% the same time meaning that then my 03:57:34.020 --> 03:57:36.469 align:start position:0% the same time meaning that then my message<03:57:34.199> wouldn't<03:57:34.560> make<03:57:34.859> it<03:57:35.520> now<03:57:36.060> that's 03:57:36.469 --> 03:57:36.479 align:start position:0% message wouldn't make it now that's 03:57:36.479 --> 03:57:39.410 align:start position:0% message wouldn't make it now that's means<03:57:37.380> there's<03:57:37.620> no<03:57:37.920> rules<03:57:38.340> for<03:57:38.880> communication 03:57:39.410 --> 03:57:39.420 align:start position:0% means there's no rules for communication 03:57:39.420 --> 03:57:42.290 align:start position:0% means there's no rules for communication in<03:57:39.960> real<03:57:40.199> life<03:57:40.439> but<03:57:40.859> in<03:57:41.699> networks<03:57:42.180> and 03:57:42.290 --> 03:57:42.300 align:start position:0% in real life but in networks and 03:57:42.300 --> 03:57:43.910 align:start position:0% in real life but in networks and computer<03:57:42.540> networks<03:57:43.080> and<03:57:43.199> data<03:57:43.500> networks 03:57:43.910 --> 03:57:43.920 align:start position:0% computer networks and data networks 03:57:43.920 --> 03:57:45.769 align:start position:0% computer networks and data networks there<03:57:44.340> are<03:57:44.460> many<03:57:44.640> different<03:57:44.939> types<03:57:45.300> of<03:57:45.420> rules 03:57:45.769 --> 03:57:45.779 align:start position:0% there are many different types of rules 03:57:45.779 --> 03:57:48.170 align:start position:0% there are many different types of rules and<03:57:46.680> here<03:57:46.920> we're<03:57:47.100> going<03:57:47.279> to<03:57:47.399> talk<03:57:47.580> about<03:57:47.760> some 03:57:48.170 --> 03:57:48.180 align:start position:0% and here we're going to talk about some 03:57:48.180 --> 03:57:50.630 align:start position:0% and here we're going to talk about some of<03:57:48.300> the<03:57:48.540> media<03:57:48.899> access<03:57:49.080> rules<03:57:49.800> or<03:57:50.040> the<03:57:50.220> rules 03:57:50.630 --> 03:57:50.640 align:start position:0% of the media access rules or the rules 03:57:50.640 --> 03:57:53.689 align:start position:0% of the media access rules or the rules that<03:57:51.000> govern<03:57:51.500> which<03:57:52.500> node<03:57:52.979> or<03:57:53.160> which<03:57:53.399> device 03:57:53.689 --> 03:57:53.699 align:start position:0% that govern which node or which device 03:57:53.699 --> 03:57:56.750 align:start position:0% that govern which node or which device has<03:57:54.359> access<03:57:54.720> and<03:57:55.380> the<03:57:55.560> ability<03:57:55.800> to<03:57:56.220> transmit 03:57:56.750 --> 03:57:56.760 align:start position:0% has access and the ability to transmit 03:57:56.760 --> 03:57:59.750 align:start position:0% has access and the ability to transmit on<03:57:57.180> the<03:57:57.300> media<03:57:57.660> at<03:57:58.080> any<03:57:58.199> one<03:57:58.439> time<03:57:58.680> and<03:57:59.520> when 03:57:59.750 --> 03:57:59.760 align:start position:0% on the media at any one time and when 03:57:59.760 --> 03:58:03.349 align:start position:0% on the media at any one time and when they're<03:58:00.000> allowed<03:58:00.420> to<03:58:01.140> send<03:58:01.680> and<03:58:02.399> receive<03:58:02.880> and 03:58:03.349 --> 03:58:03.359 align:start position:0% they're allowed to send and receive and 03:58:03.359 --> 03:58:06.590 align:start position:0% they're allowed to send and receive and for<03:58:03.600> how<03:58:03.840> long<03:58:04.020> now<03:58:04.920> these<03:58:05.220> rules<03:58:05.520> are<03:58:06.120> crucial 03:58:06.590 --> 03:58:06.600 align:start position:0% for how long now these rules are crucial 03:58:06.600 --> 03:58:09.410 align:start position:0% for how long now these rules are crucial they<03:58:07.199> ensure<03:58:07.500> that<03:58:07.800> data<03:58:08.340> delivery<03:58:08.939> and 03:58:09.410 --> 03:58:09.420 align:start position:0% they ensure that data delivery and 03:58:09.420 --> 03:58:11.750 align:start position:0% they ensure that data delivery and integrity<03:58:09.899> and<03:58:10.859> by<03:58:11.040> the<03:58:11.160> way<03:58:11.220> when<03:58:11.460> we<03:58:11.580> say 03:58:11.750 --> 03:58:11.760 align:start position:0% integrity and by the way when we say 03:58:11.760 --> 03:58:13.610 align:start position:0% integrity and by the way when we say Integrity<03:58:12.300> we<03:58:12.540> mean<03:58:12.660> that<03:58:12.840> the<03:58:13.020> data<03:58:13.319> we 03:58:13.610 --> 03:58:13.620 align:start position:0% Integrity we mean that the data we 03:58:13.620 --> 03:58:15.889 align:start position:0% Integrity we mean that the data we intended<03:58:14.220> to<03:58:14.399> send<03:58:14.640> is<03:58:15.060> actually<03:58:15.300> what<03:58:15.720> was 03:58:15.889 --> 03:58:15.899 align:start position:0% intended to send is actually what was 03:58:15.899 --> 03:58:18.889 align:start position:0% intended to send is actually what was sent<03:58:16.140> it<03:58:16.380> hasn't<03:58:16.620> been<03:58:16.800> tampered<03:58:17.279> with<03:58:17.600> uh<03:58:18.600> are 03:58:18.889 --> 03:58:18.899 align:start position:0% sent it hasn't been tampered with uh are 03:58:18.899 --> 03:58:21.410 align:start position:0% sent it hasn't been tampered with uh are maintained<03:58:19.920> now<03:58:20.460> there<03:58:20.760> are<03:58:20.939> two<03:58:21.120> general 03:58:21.410 --> 03:58:21.420 align:start position:0% maintained now there are two general 03:58:21.420 --> 03:58:23.830 align:start position:0% maintained now there are two general categories<03:58:22.380> for<03:58:22.739> types<03:58:23.100> of<03:58:23.160> media<03:58:23.520> access 03:58:23.830 --> 03:58:23.840 align:start position:0% categories for types of media access 03:58:23.840 --> 03:58:27.170 align:start position:0% categories for types of media access these<03:58:24.840> are<03:58:25.020> contention<03:58:25.800> based<03:58:26.520> and 03:58:27.170 --> 03:58:27.180 align:start position:0% these are contention based and 03:58:27.180 --> 03:58:29.689 align:start position:0% these are contention based and controlled<03:58:27.899> media<03:58:28.380> access<03:58:28.500> so<03:58:29.220> let's<03:58:29.340> take<03:58:29.520> a 03:58:29.689 --> 03:58:29.699 align:start position:0% controlled media access so let's take a 03:58:29.699 --> 03:58:31.250 align:start position:0% controlled media access so let's take a look<03:58:29.819> at<03:58:30.000> the<03:58:30.180> differences<03:58:30.540> between<03:58:30.840> those 03:58:31.250 --> 03:58:31.260 align:start position:0% look at the differences between those 03:58:31.260 --> 03:58:33.349 align:start position:0% look at the differences between those now<03:58:31.560> and<03:58:32.100> they'll<03:58:32.279> come<03:58:32.580> back<03:58:32.760> when<03:58:33.060> we<03:58:33.180> talk 03:58:33.349 --> 03:58:33.359 align:start position:0% now and they'll come back when we talk 03:58:33.359 --> 03:58:37.070 align:start position:0% now and they'll come back when we talk later<03:58:33.660> about<03:58:33.899> csma<03:58:34.760> CD<03:58:35.760> and<03:58:36.000> CA<03:58:36.420> not<03:58:36.960> to 03:58:37.070 --> 03:58:37.080 align:start position:0% later about csma CD and CA not to 03:58:37.080 --> 03:58:39.170 align:start position:0% later about csma CD and CA not to mention<03:58:37.319> contention<03:58:37.859> broadcast<03:58:38.340> domains 03:58:39.170 --> 03:58:39.180 align:start position:0% mention contention broadcast domains 03:58:39.180 --> 03:58:42.950 align:start position:0% mention contention broadcast domains with<03:58:40.160> contention-based<03:58:41.160> media<03:58:41.520> access<03:58:41.960> nodes 03:58:42.950 --> 03:58:42.960 align:start position:0% with contention-based media access nodes 03:58:42.960 --> 03:58:46.130 align:start position:0% with contention-based media access nodes on<03:58:43.140> the<03:58:43.260> network<03:58:43.439> are<03:58:44.100> competing<03:58:44.960> with<03:58:45.960> one 03:58:46.130 --> 03:58:46.140 align:start position:0% on the network are competing with one 03:58:46.140 --> 03:58:49.429 align:start position:0% on the network are competing with one another<03:58:46.319> for<03:58:47.160> media<03:58:47.580> access<03:58:47.880> time<03:58:48.840> and 03:58:49.429 --> 03:58:49.439 align:start position:0% another for media access time and 03:58:49.439 --> 03:58:52.250 align:start position:0% another for media access time and utilization<03:58:50.359> another<03:58:51.359> term<03:58:51.660> for<03:58:51.960> this<03:58:52.080> kind 03:58:52.250 --> 03:58:52.260 align:start position:0% utilization another term for this kind 03:58:52.260 --> 03:58:54.889 align:start position:0% utilization another term for this kind of<03:58:52.380> media<03:58:52.739> is<03:58:53.160> competitive<03:58:53.939> or<03:58:54.420> Collision 03:58:54.889 --> 03:58:54.899 align:start position:0% of media is competitive or Collision 03:58:54.899 --> 03:58:57.349 align:start position:0% of media is competitive or Collision based<03:58:55.500> and<03:58:55.979> yes<03:58:56.160> that<03:58:56.640> means<03:58:56.939> that<03:58:57.180> they're 03:58:57.349 --> 03:58:57.359 align:start position:0% based and yes that means that they're 03:58:57.359 --> 03:58:59.570 align:start position:0% based and yes that means that they're actually<03:58:57.540> the<03:58:58.080> data<03:58:58.380> packets<03:58:58.680> are<03:58:59.040> colliding 03:58:59.570 --> 03:58:59.580 align:start position:0% actually the data packets are colliding 03:58:59.580 --> 03:59:02.990 align:start position:0% actually the data packets are colliding and<03:59:00.060> that's<03:59:00.239> how<03:59:00.479> we<03:59:00.660> determine<03:59:01.220> which<03:59:02.220> can<03:59:02.580> go 03:59:02.990 --> 03:59:03.000 align:start position:0% and that's how we determine which can go 03:59:03.000 --> 03:59:05.570 align:start position:0% and that's how we determine which can go right<03:59:03.600> which<03:59:03.899> is<03:59:04.020> allowed<03:59:04.319> to<03:59:04.380> be<03:59:04.560> sent<03:59:04.739> now 03:59:05.570 --> 03:59:05.580 align:start position:0% right which is allowed to be sent now 03:59:05.580 --> 03:59:07.070 align:start position:0% right which is allowed to be sent now these<03:59:05.880> are<03:59:06.000> pretty<03:59:06.180> easy<03:59:06.420> to<03:59:06.720> implement 03:59:07.070 --> 03:59:07.080 align:start position:0% these are pretty easy to implement 03:59:07.080 --> 03:59:10.130 align:start position:0% these are pretty easy to implement however<03:59:07.819> data<03:59:08.819> can<03:59:08.939> be<03:59:09.120> delayed<03:59:09.600> for<03:59:09.840> nodes 03:59:10.130 --> 03:59:10.140 align:start position:0% however data can be delayed for nodes 03:59:10.140 --> 03:59:12.050 align:start position:0% however data can be delayed for nodes that<03:59:10.439> need<03:59:10.680> immediate<03:59:11.460> access<03:59:11.640> to<03:59:11.939> the 03:59:12.050 --> 03:59:12.060 align:start position:0% that need immediate access to the 03:59:12.060 --> 03:59:14.870 align:start position:0% that need immediate access to the network<03:59:12.239> media<03:59:12.779> because<03:59:13.699> collisions<03:59:14.699> are 03:59:14.870 --> 03:59:14.880 align:start position:0% network media because collisions are 03:59:14.880 --> 03:59:17.269 align:start position:0% network media because collisions are going<03:59:15.000> to<03:59:15.180> occur<03:59:15.540> as<03:59:15.840> the<03:59:16.020> name<03:59:16.140> implies<03:59:16.739> and 03:59:17.269 --> 03:59:17.279 align:start position:0% going to occur as the name implies and 03:59:17.279 --> 03:59:19.070 align:start position:0% going to occur as the name implies and that's<03:59:17.399> going<03:59:17.699> to<03:59:17.880> delay<03:59:18.239> Network<03:59:18.660> traffic 03:59:19.070 --> 03:59:19.080 align:start position:0% that's going to delay Network traffic 03:59:19.080 --> 03:59:21.710 align:start position:0% that's going to delay Network traffic now<03:59:19.680> as<03:59:19.800> a<03:59:19.859> opposed<03:59:20.580> to<03:59:20.720> contention-based 03:59:21.710 --> 03:59:21.720 align:start position:0% now as a opposed to contention-based 03:59:21.720 --> 03:59:24.469 align:start position:0% now as a opposed to contention-based Media<03:59:22.020> access<03:59:22.199> we<03:59:22.859> also<03:59:23.040> have<03:59:23.479> controlled 03:59:24.469 --> 03:59:24.479 align:start position:0% Media access we also have controlled 03:59:24.479 --> 03:59:27.830 align:start position:0% Media access we also have controlled media<03:59:24.960> access<03:59:25.399> so<03:59:26.399> instead<03:59:26.880> of<03:59:27.000> me<03:59:27.239> fighting 03:59:27.830 --> 03:59:27.840 align:start position:0% media access so instead of me fighting 03:59:27.840 --> 03:59:30.410 align:start position:0% media access so instead of me fighting for<03:59:28.080> access<03:59:28.260> to<03:59:28.620> the<03:59:28.800> media<03:59:29.100> I'm<03:59:29.819> granted 03:59:30.410 --> 03:59:30.420 align:start position:0% for access to the media I'm granted 03:59:30.420 --> 03:59:32.150 align:start position:0% for access to the media I'm granted access<03:59:30.660> to<03:59:30.960> the<03:59:31.140> media<03:59:31.439> and<03:59:31.739> the<03:59:31.859> way<03:59:31.979> this 03:59:32.150 --> 03:59:32.160 align:start position:0% access to the media and the way this 03:59:32.160 --> 03:59:35.809 align:start position:0% access to the media and the way this works<03:59:32.460> is<03:59:32.640> we<03:59:33.000> use<03:59:33.199> a<03:59:34.199> central<03:59:34.560> device<03:59:35.340> that's 03:59:35.809 --> 03:59:35.819 align:start position:0% works is we use a central device that's 03:59:35.819 --> 03:59:39.110 align:start position:0% works is we use a central device that's put<03:59:36.180> in<03:59:36.359> place<03:59:36.660> to<03:59:37.500> ensure<03:59:37.979> that<03:59:38.640> access<03:59:38.819> to 03:59:39.110 --> 03:59:39.120 align:start position:0% put in place to ensure that access to 03:59:39.120 --> 03:59:41.389 align:start position:0% put in place to ensure that access to the<03:59:39.239> media<03:59:39.540> is<03:59:39.779> guaranteed<03:59:40.380> for<03:59:40.620> devices<03:59:40.979> that 03:59:41.389 --> 03:59:41.399 align:start position:0% the media is guaranteed for devices that 03:59:41.399 --> 03:59:43.969 align:start position:0% the media is guaranteed for devices that have<03:59:41.580> certain<03:59:41.939> time<03:59:42.239> sensitive<03:59:42.840> data<03:59:43.319> and 03:59:43.969 --> 03:59:43.979 align:start position:0% have certain time sensitive data and 03:59:43.979 --> 03:59:45.849 align:start position:0% have certain time sensitive data and they<03:59:44.279> can<03:59:44.460> transmit<03:59:44.939> it<03:59:45.120> when<03:59:45.359> necessary 03:59:45.849 --> 03:59:45.859 align:start position:0% they can transmit it when necessary 03:59:45.859 --> 03:59:48.530 align:start position:0% they can transmit it when necessary because<03:59:46.859> of<03:59:47.160> the<03:59:47.340> because<03:59:47.699> of<03:59:47.939> this<03:59:48.120> and<03:59:48.300> these 03:59:48.530 --> 03:59:48.540 align:start position:0% because of the because of this and these 03:59:48.540 --> 03:59:50.330 align:start position:0% because of the because of this and these devices<03:59:48.840> that<03:59:49.199> need<03:59:49.380> to<03:59:49.500> be<03:59:49.620> added<03:59:49.920> these<03:59:50.220> are 03:59:50.330 --> 03:59:50.340 align:start position:0% devices that need to be added these are 03:59:50.340 --> 03:59:52.429 align:start position:0% devices that need to be added these are much<03:59:50.580> more<03:59:50.819> difficult<03:59:51.180> to<03:59:51.420> implement<03:59:52.080> and 03:59:52.429 --> 03:59:52.439 align:start position:0% much more difficult to implement and 03:59:52.439 --> 03:59:55.309 align:start position:0% much more difficult to implement and maintain<03:59:52.859> but<03:59:53.640> they're<03:59:54.180> highly<03:59:54.600> reliable<03:59:55.080> as 03:59:55.309 --> 03:59:55.319 align:start position:0% maintain but they're highly reliable as 03:59:55.319 --> 03:59:57.229 align:start position:0% maintain but they're highly reliable as you<03:59:55.439> can<03:59:55.560> imagine<03:59:55.800> and<03:59:56.520> also<03:59:56.699> make<03:59:56.880> sure<03:59:57.000> that 03:59:57.229 --> 03:59:57.239 align:start position:0% you can imagine and also make sure that 03:59:57.239 --> 03:59:58.849 align:start position:0% you can imagine and also make sure that no<03:59:57.420> device<03:59:57.660> has<03:59:58.020> more<03:59:58.199> access<03:59:58.380> than<03:59:58.739> another 03:59:58.849 --> 03:59:58.859 align:start position:0% no device has more access than another 03:59:58.859 --> 04:00:02.210 align:start position:0% no device has more access than another when<03:59:59.279> it<03:59:59.399> comes<03:59:59.699> to<03:59:59.939> access<04:00:00.359> time<04:00:00.840> so<04:00:01.739> take<04:00:01.979> for 04:00:02.210 --> 04:00:02.220 align:start position:0% when it comes to access time so take for 04:00:02.220 --> 04:00:04.729 align:start position:0% when it comes to access time so take for instance<04:00:02.580> a<04:00:03.120> device<04:00:03.359> that<04:00:03.779> has<04:00:04.020> a<04:00:04.380> safety 04:00:04.729 --> 04:00:04.739 align:start position:0% instance a device that has a safety 04:00:04.739 --> 04:00:06.889 align:start position:0% instance a device that has a safety function<04:00:05.100> that<04:00:05.640> when<04:00:05.880> an<04:00:06.060> emergency<04:00:06.300> event 04:00:06.889 --> 04:00:06.899 align:start position:0% function that when an emergency event 04:00:06.899 --> 04:00:09.290 align:start position:0% function that when an emergency event occurs<04:00:07.739> right<04:00:08.040> it<04:00:08.460> has<04:00:08.580> to<04:00:08.760> have<04:00:08.880> immediate 04:00:09.290 --> 04:00:09.300 align:start position:0% occurs right it has to have immediate 04:00:09.300 --> 04:00:11.090 align:start position:0% occurs right it has to have immediate access<04:00:09.479> to<04:00:09.840> the<04:00:09.960> network<04:00:10.080> and<04:00:10.680> to<04:00:10.859> the<04:00:10.979> network 04:00:11.090 --> 04:00:11.100 align:start position:0% access to the network and to the network 04:00:11.100 --> 04:00:14.330 align:start position:0% access to the network and to the network resources<04:00:11.880> so<04:00:12.180> it<04:00:12.359> can<04:00:12.600> send<04:00:12.979> instructions<04:00:13.979> to 04:00:14.330 --> 04:00:14.340 align:start position:0% resources so it can send instructions to 04:00:14.340 --> 04:00:16.729 align:start position:0% resources so it can send instructions to say<04:00:14.580> heavy<04:00:15.060> machinery<04:00:15.540> that<04:00:16.080> needs<04:00:16.380> to<04:00:16.500> shut 04:00:16.729 --> 04:00:16.739 align:start position:0% say heavy machinery that needs to shut 04:00:16.739 --> 04:00:18.950 align:start position:0% say heavy machinery that needs to shut down<04:00:16.920> in<04:00:17.220> case<04:00:17.399> an<04:00:17.640> emergency<04:00:17.880> in<04:00:18.720> that<04:00:18.840> case 04:00:18.950 --> 04:00:18.960 align:start position:0% down in case an emergency in that case 04:00:18.960 --> 04:00:20.689 align:start position:0% down in case an emergency in that case we<04:00:19.199> don't<04:00:19.260> want<04:00:19.380> it<04:00:19.439> to<04:00:19.560> be<04:00:19.800> intending<04:00:20.580> for 04:00:20.689 --> 04:00:20.699 align:start position:0% we don't want it to be intending for 04:00:20.699 --> 04:00:22.309 align:start position:0% we don't want it to be intending for Access<04:00:20.880> we<04:00:21.239> want<04:00:21.359> it<04:00:21.540> to<04:00:21.660> be<04:00:21.779> granted 04:00:22.309 --> 04:00:22.319 align:start position:0% Access we want it to be granted 04:00:22.319 --> 04:00:24.410 align:start position:0% Access we want it to be granted immediate<04:00:22.859> access<04:00:23.100> and<04:00:23.699> so<04:00:23.880> this<04:00:24.060> is<04:00:24.239> where 04:00:24.410 --> 04:00:24.420 align:start position:0% immediate access and so this is where 04:00:24.420 --> 04:00:26.210 align:start position:0% immediate access and so this is where controlled<04:00:24.899> media<04:00:25.199> access<04:00:25.319> can<04:00:25.739> really<04:00:25.979> come 04:00:26.210 --> 04:00:26.220 align:start position:0% controlled media access can really come 04:00:26.220 --> 04:00:27.290 align:start position:0% controlled media access can really come in<04:00:26.399> handy 04:00:27.290 --> 04:00:27.300 align:start position:0% in handy 04:00:27.300 --> 04:00:29.630 align:start position:0% in handy so<04:00:27.720> while<04:00:27.960> we're<04:00:28.140> talking<04:00:28.380> about<04:00:28.739> controlled 04:00:29.630 --> 04:00:29.640 align:start position:0% so while we're talking about controlled 04:00:29.640 --> 04:00:32.229 align:start position:0% so while we're talking about controlled media<04:00:30.060> access<04:00:30.439> and<04:00:31.439> we've<04:00:31.739> just<04:00:31.859> talked<04:00:32.160> about 04:00:32.229 --> 04:00:32.239 align:start position:0% media access and we've just talked about 04:00:32.239 --> 04:00:36.290 align:start position:0% media access and we've just talked about controlled<04:00:33.239> and<04:00:34.199> contention<04:00:34.920> based<04:00:35.880> media 04:00:36.290 --> 04:00:36.300 align:start position:0% controlled and contention based media 04:00:36.300 --> 04:00:38.150 align:start position:0% controlled and contention based media access<04:00:36.540> let's<04:00:37.260> keep<04:00:37.500> talking<04:00:37.680> about<04:00:37.920> control 04:00:38.150 --> 04:00:38.160 align:start position:0% access let's keep talking about control 04:00:38.160 --> 04:00:40.090 align:start position:0% access let's keep talking about control based<04:00:38.699> media<04:00:38.939> access<04:00:39.000> more<04:00:39.479> specifically 04:00:40.090 --> 04:00:40.100 align:start position:0% based media access more specifically 04:00:40.100 --> 04:00:43.070 align:start position:0% based media access more specifically discussing<04:00:41.100> a<04:00:41.340> few<04:00:41.520> different<04:00:42.080> controlled 04:00:43.070 --> 04:00:43.080 align:start position:0% discussing a few different controlled 04:00:43.080 --> 04:00:45.950 align:start position:0% discussing a few different controlled based<04:00:43.560> uh<04:00:44.399> or<04:00:44.580> controlled<04:00:45.359> media<04:00:45.779> access 04:00:45.950 --> 04:00:45.960 align:start position:0% based uh or controlled media access 04:00:45.960 --> 04:00:47.990 align:start position:0% based uh or controlled media access methods<04:00:46.800> the<04:00:47.220> first<04:00:47.399> I<04:00:47.520> want<04:00:47.640> to<04:00:47.760> talk<04:00:47.880> about 04:00:47.990 --> 04:00:48.000 align:start position:0% methods the first I want to talk about 04:00:48.000 --> 04:00:50.990 align:start position:0% methods the first I want to talk about is<04:00:48.300> called<04:00:48.680> multiplexing<04:00:49.680> and<04:00:50.279> multiplexing 04:00:50.990 --> 04:00:51.000 align:start position:0% is called multiplexing and multiplexing 04:00:51.000 --> 04:00:54.229 align:start position:0% is called multiplexing and multiplexing is<04:00:51.359> a<04:00:51.660> controlled<04:00:52.260> media<04:00:52.920> access<04:00:53.100> method<04:00:53.819> I'm 04:00:54.229 --> 04:00:54.239 align:start position:0% is a controlled media access method I'm 04:00:54.239 --> 04:00:56.030 align:start position:0% is a controlled media access method I'm just<04:00:54.420> going<04:00:54.540> to<04:00:54.600> add<04:00:54.840> control<04:00:55.199> there<04:00:55.560> so<04:00:55.859> that 04:00:56.030 --> 04:00:56.040 align:start position:0% just going to add control there so that 04:00:56.040 --> 04:00:59.710 align:start position:0% just going to add control there so that we<04:00:56.220> remember<04:00:56.399> that<04:00:56.939> this<04:00:57.660> is<04:00:58.020> related<04:00:58.560> to 04:00:59.710 --> 04:00:59.720 align:start position:0% we remember that this is related to 04:00:59.720 --> 04:01:04.189 align:start position:0% we remember that this is related to controlled<04:01:00.720> not<04:01:01.500> contention<04:01:02.040> based<04:01:02.819> it<04:01:03.720> takes 04:01:04.189 --> 04:01:04.199 align:start position:0% controlled not contention based it takes 04:01:04.199 --> 04:01:07.309 align:start position:0% controlled not contention based it takes multiple<04:01:04.800> signals<04:01:05.520> and<04:01:06.120> combines<04:01:06.540> them<04:01:06.840> over 04:01:07.309 --> 04:01:07.319 align:start position:0% multiple signals and combines them over 04:01:07.319 --> 04:01:10.670 align:start position:0% multiple signals and combines them over one<04:01:07.859> single<04:01:08.279> Network<04:01:08.460> medium<04:01:09.060> now<04:01:09.960> data<04:01:10.560> can 04:01:10.670 --> 04:01:10.680 align:start position:0% one single Network medium now data can 04:01:10.680 --> 04:01:13.070 align:start position:0% one single Network medium now data can actually<04:01:10.859> be<04:01:11.220> multiplexed<04:01:12.060> using<04:01:12.540> two 04:01:13.070 --> 04:01:13.080 align:start position:0% actually be multiplexed using two 04:01:13.080 --> 04:01:15.229 align:start position:0% actually be multiplexed using two different<04:01:13.260> methods<04:01:13.859> time<04:01:14.819> Division 04:01:15.229 --> 04:01:15.239 align:start position:0% different methods time Division 04:01:15.239 --> 04:01:17.990 align:start position:0% different methods time Division multiplexing<04:01:16.080> and<04:01:16.979> frequency<04:01:17.460> division 04:01:17.990 --> 04:01:18.000 align:start position:0% multiplexing and frequency division 04:01:18.000 --> 04:01:21.229 align:start position:0% multiplexing and frequency division multiplexing<04:01:18.779> so<04:01:19.020> let's<04:01:19.199> first<04:01:19.500> look<04:01:19.859> at<04:01:20.239> time 04:01:21.229 --> 04:01:21.239 align:start position:0% multiplexing so let's first look at time 04:01:21.239 --> 04:01:23.929 align:start position:0% multiplexing so let's first look at time division<04:01:21.779> multiplexing<04:01:22.620> this<04:01:23.399> is<04:01:23.520> where 04:01:23.929 --> 04:01:23.939 align:start position:0% division multiplexing this is where 04:01:23.939 --> 04:01:27.650 align:start position:0% division multiplexing this is where channels<04:01:24.899> are<04:01:25.140> divided<04:01:25.620> into<04:01:25.979> time<04:01:26.399> slots<04:01:26.880> and 04:01:27.650 --> 04:01:27.660 align:start position:0% channels are divided into time slots and 04:01:27.660 --> 04:01:30.170 align:start position:0% channels are divided into time slots and each<04:01:27.899> node<04:01:28.140> on<04:01:28.319> the<04:01:28.500> network<04:01:28.620> is<04:01:29.160> assigned<04:01:29.760> a 04:01:30.170 --> 04:01:30.180 align:start position:0% each node on the network is assigned a 04:01:30.180 --> 04:01:33.889 align:start position:0% each node on the network is assigned a specific<04:01:30.600> time<04:01:31.260> slot 04:01:33.889 --> 04:01:33.899 align:start position:0% 04:01:33.899 --> 04:01:36.410 align:start position:0% during<04:01:34.560> that<04:01:34.979> time<04:01:35.160> slot<04:01:35.520> the<04:01:35.880> node<04:01:36.120> has 04:01:36.410 --> 04:01:36.420 align:start position:0% during that time slot the node has 04:01:36.420 --> 04:01:39.650 align:start position:0% during that time slot the node has dedicated<04:01:37.460> sole<04:01:38.460> access<04:01:38.640> to<04:01:39.300> the<04:01:39.479> network 04:01:39.650 --> 04:01:39.660 align:start position:0% dedicated sole access to the network 04:01:39.660 --> 04:01:42.050 align:start position:0% dedicated sole access to the network until<04:01:40.500> that<04:01:40.859> time<04:01:40.979> has<04:01:41.220> ended<04:01:41.520> and<04:01:41.699> then<04:01:41.880> the 04:01:42.050 --> 04:01:42.060 align:start position:0% until that time has ended and then the 04:01:42.060 --> 04:01:44.750 align:start position:0% until that time has ended and then the next<04:01:42.239> node<04:01:42.600> is<04:01:42.720> allowed<04:01:43.080> to<04:01:43.199> transmit<04:01:44.340> now 04:01:44.750 --> 04:01:44.760 align:start position:0% next node is allowed to transmit now 04:01:44.760 --> 04:01:46.010 align:start position:0% next node is allowed to transmit now there's<04:01:44.939> a<04:01:45.180> device<04:01:45.300> that<04:01:45.720> we're<04:01:45.779> going<04:01:45.899> to 04:01:46.010 --> 04:01:46.020 align:start position:0% there's a device that we're going to 04:01:46.020 --> 04:01:47.330 align:start position:0% there's a device that we're going to talk<04:01:46.140> about<04:01:46.260> in<04:01:46.439> just<04:01:46.560> a<04:01:46.739> minute<04:01:46.859> called<04:01:47.100> the 04:01:47.330 --> 04:01:47.340 align:start position:0% talk about in just a minute called the 04:01:47.340 --> 04:01:50.210 align:start position:0% talk about in just a minute called the Mox<04:01:47.699> and<04:01:48.239> this<04:01:48.479> MOX<04:01:48.899> takes<04:01:49.380> the<04:01:49.560> signals<04:01:50.040> from 04:01:50.210 --> 04:01:50.220 align:start position:0% Mox and this MOX takes the signals from 04:01:50.220 --> 04:01:52.429 align:start position:0% Mox and this MOX takes the signals from each<04:01:50.399> of<04:01:50.520> the<04:01:50.699> nodes<04:01:50.939> and<04:01:51.540> sends<04:01:51.899> it<04:01:52.020> across 04:01:52.429 --> 04:01:52.439 align:start position:0% each of the nodes and sends it across 04:01:52.439 --> 04:01:53.389 align:start position:0% each of the nodes and sends it across the<04:01:52.560> network 04:01:53.389 --> 04:01:53.399 align:start position:0% the network 04:01:53.399 --> 04:01:56.090 align:start position:0% the network now<04:01:53.760> with<04:01:54.000> TDM<04:01:54.600> multiple 04:01:56.090 --> 04:01:56.100 align:start position:0% now with TDM multiple 04:01:56.100 --> 04:01:59.570 align:start position:0% now with TDM multiple base<04:01:56.640> band<04:01:56.939> signals<04:01:57.720> and<04:01:58.319> remember<04:01:58.580> baseband 04:01:59.570 --> 04:01:59.580 align:start position:0% base band signals and remember baseband 04:01:59.580 --> 04:02:01.189 align:start position:0% base band signals and remember baseband is 04:02:01.189 --> 04:02:01.199 align:start position:0% is 04:02:01.199 --> 04:02:03.229 align:start position:0% is digital 04:02:03.229 --> 04:02:03.239 align:start position:0% digital 04:02:03.239 --> 04:02:06.550 align:start position:0% digital again<04:02:03.779> represented<04:02:04.500> here<04:02:04.800> by<04:02:05.520> that<04:02:05.880> Digital 04:02:06.550 --> 04:02:06.560 align:start position:0% again represented here by that Digital 04:02:06.560 --> 04:02:10.070 align:start position:0% again represented here by that Digital Signal<04:02:07.560> because<04:02:08.279> there<04:02:08.819> is<04:02:09.000> no<04:02:09.300> curve<04:02:09.779> in<04:02:09.899> the 04:02:10.070 --> 04:02:10.080 align:start position:0% Signal because there is no curve in the 04:02:10.080 --> 04:02:12.229 align:start position:0% Signal because there is no curve in the wave<04:02:10.319> which<04:02:11.100> would<04:02:11.220> be<04:02:11.340> analog<04:02:11.760> and<04:02:11.939> we'll<04:02:12.060> see 04:02:12.229 --> 04:02:12.239 align:start position:0% wave which would be analog and we'll see 04:02:12.239 --> 04:02:13.490 align:start position:0% wave which would be analog and we'll see that<04:02:12.359> in<04:02:12.479> just<04:02:12.600> a<04:02:12.779> second 04:02:13.490 --> 04:02:13.500 align:start position:0% that in just a second 04:02:13.500 --> 04:02:16.070 align:start position:0% that in just a second it<04:02:13.920> allows<04:02:14.279> these<04:02:14.699> digital<04:02:15.180> signals<04:02:15.720> these 04:02:16.070 --> 04:02:16.080 align:start position:0% it allows these digital signals these 04:02:16.080 --> 04:02:18.050 align:start position:0% it allows these digital signals these baseband<04:02:16.560> channels<04:02:17.100> to<04:02:17.279> be<04:02:17.460> combined<04:02:17.939> and 04:02:18.050 --> 04:02:18.060 align:start position:0% baseband channels to be combined and 04:02:18.060 --> 04:02:20.750 align:start position:0% baseband channels to be combined and sent<04:02:18.300> over<04:02:18.600> one<04:02:19.080> network<04:02:19.560> medium 04:02:20.750 --> 04:02:20.760 align:start position:0% sent over one network medium 04:02:20.760 --> 04:02:22.490 align:start position:0% sent over one network medium on<04:02:21.180> the<04:02:21.300> other<04:02:21.359> hand<04:02:21.540> we<04:02:21.840> also<04:02:22.080> have<04:02:22.199> something 04:02:22.490 --> 04:02:22.500 align:start position:0% on the other hand we also have something 04:02:22.500 --> 04:02:25.070 align:start position:0% on the other hand we also have something called<04:02:22.920> frequency<04:02:23.819> division<04:02:24.300> multiplexing 04:02:25.070 --> 04:02:25.080 align:start position:0% called frequency division multiplexing 04:02:25.080 --> 04:02:27.590 align:start position:0% called frequency division multiplexing this<04:02:25.920> is<04:02:26.040> where<04:02:26.279> data<04:02:26.699> from<04:02:26.880> multiple<04:02:27.239> nodes 04:02:27.590 --> 04:02:27.600 align:start position:0% this is where data from multiple nodes 04:02:27.600 --> 04:02:30.229 align:start position:0% this is where data from multiple nodes is<04:02:28.080> sent<04:02:28.319> over<04:02:28.500> many<04:02:28.920> different<04:02:29.279> frequencies 04:02:30.229 --> 04:02:30.239 align:start position:0% is sent over many different frequencies 04:02:30.239 --> 04:02:33.410 align:start position:0% is sent over many different frequencies as<04:02:30.899> opposed<04:02:31.199> to<04:02:31.260> given<04:02:31.620> a<04:02:31.739> specific<04:02:32.040> time<04:02:32.420> each 04:02:33.410 --> 04:02:33.420 align:start position:0% as opposed to given a specific time each 04:02:33.420 --> 04:02:35.510 align:start position:0% as opposed to given a specific time each node<04:02:33.720> has<04:02:34.020> complete<04:02:34.560> access<04:02:34.739> to<04:02:35.220> its 04:02:35.510 --> 04:02:35.520 align:start position:0% node has complete access to its 04:02:35.520 --> 04:02:38.450 align:start position:0% node has complete access to its frequency<04:02:36.080> and<04:02:37.080> dedicated<04:02:37.680> communication 04:02:38.450 --> 04:02:38.460 align:start position:0% frequency and dedicated communication 04:02:38.460 --> 04:02:41.210 align:start position:0% frequency and dedicated communication with<04:02:38.880> the<04:02:39.300> MOX<04:02:39.660> that<04:02:39.960> device<04:02:40.199> that<04:02:40.859> is 04:02:41.210 --> 04:02:41.220 align:start position:0% with the MOX that device that is 04:02:41.220 --> 04:02:43.250 align:start position:0% with the MOX that device that is basically<04:02:41.580> controlling<04:02:42.239> all<04:02:42.420> of<04:02:42.600> this 04:02:43.250 --> 04:02:43.260 align:start position:0% basically controlling all of this 04:02:43.260 --> 04:02:46.429 align:start position:0% basically controlling all of this the<04:02:43.859> mux<04:02:44.220> combines<04:02:44.819> the<04:02:45.479> received<04:02:45.960> signals 04:02:46.429 --> 04:02:46.439 align:start position:0% the mux combines the received signals 04:02:46.439 --> 04:02:48.170 align:start position:0% the mux combines the received signals from<04:02:46.680> the<04:02:46.859> nodes<04:02:47.040> and<04:02:47.460> then<04:02:47.580> transmitted 04:02:48.170 --> 04:02:48.180 align:start position:0% from the nodes and then transmitted 04:02:48.180 --> 04:02:49.910 align:start position:0% from the nodes and then transmitted across<04:02:48.600> the<04:02:48.720> medium<04:02:49.020> the<04:02:49.500> important<04:02:49.800> thing 04:02:49.910 --> 04:02:49.920 align:start position:0% across the medium the important thing 04:02:49.920 --> 04:02:51.950 align:start position:0% across the medium the important thing you're<04:02:50.160> here<04:02:50.399> to<04:02:50.699> know<04:02:50.819> is<04:02:51.359> that<04:02:51.540> this<04:02:51.779> we're 04:02:51.950 --> 04:02:51.960 align:start position:0% you're here to know is that this we're 04:02:51.960 --> 04:02:56.330 align:start position:0% you're here to know is that this we're dealing<04:02:52.260> with<04:02:52.380> Broadband<04:02:53.160> or<04:02:53.939> analog<04:02:54.420> signals 04:02:56.330 --> 04:02:56.340 align:start position:0% dealing with Broadband or analog signals 04:02:56.340 --> 04:02:59.630 align:start position:0% dealing with Broadband or analog signals now<04:02:56.939> we've<04:02:57.420> been<04:02:57.660> talking<04:02:57.960> about 04:02:59.630 --> 04:02:59.640 align:start position:0% now we've been talking about 04:02:59.640 --> 04:03:02.210 align:start position:0% now we've been talking about uh<04:03:00.420> the<04:03:00.720> mux<04:03:01.020> so<04:03:01.260> let's<04:03:01.380> just<04:03:01.500> talk<04:03:01.680> about<04:03:01.859> that 04:03:02.210 --> 04:03:02.220 align:start position:0% uh the mux so let's just talk about that 04:03:02.220 --> 04:03:05.630 align:start position:0% uh the mux so let's just talk about that really<04:03:02.520> briefly<04:03:03.000> the<04:03:03.960> MOX<04:03:04.380> is<04:03:05.160> the<04:03:05.460> central 04:03:05.630 --> 04:03:05.640 align:start position:0% really briefly the MOX is the central 04:03:05.640 --> 04:03:09.170 align:start position:0% really briefly the MOX is the central device<04:03:06.380> that<04:03:07.380> or<04:03:07.739> which<04:03:08.160> is<04:03:08.279> also<04:03:08.580> called<04:03:08.760> a 04:03:09.170 --> 04:03:09.180 align:start position:0% device that or which is also called a 04:03:09.180 --> 04:03:10.670 align:start position:0% device that or which is also called a multiplexer 04:03:10.670 --> 04:03:10.680 align:start position:0% multiplexer 04:03:10.680 --> 04:03:13.070 align:start position:0% multiplexer that<04:03:11.340> combines<04:03:11.699> the<04:03:11.939> signals<04:03:12.359> and<04:03:12.540> transmits 04:03:13.070 --> 04:03:13.080 align:start position:0% that combines the signals and transmits 04:03:13.080 --> 04:03:15.349 align:start position:0% that combines the signals and transmits them<04:03:13.199> to<04:03:13.439> the<04:03:13.560> receiving<04:03:13.800> end<04:03:14.100> or<04:03:14.460> a<04:03:14.699> demux<04:03:15.180> or 04:03:15.349 --> 04:03:15.359 align:start position:0% them to the receiving end or a demux or 04:03:15.359 --> 04:03:17.750 align:start position:0% them to the receiving end or a demux or a<04:03:15.479> d<04:03:15.600> multiplexer<04:03:16.380> separates<04:03:17.160> the<04:03:17.340> signals 04:03:17.750 --> 04:03:17.760 align:start position:0% a d multiplexer separates the signals 04:03:17.760 --> 04:03:19.990 align:start position:0% a d multiplexer separates the signals out<04:03:17.880> again<04:03:18.060> now<04:03:18.779> remember<04:03:19.020> this<04:03:19.500> is<04:03:19.620> all 04:03:19.990 --> 04:03:20.000 align:start position:0% out again now remember this is all 04:03:20.000 --> 04:03:23.570 align:start position:0% out again now remember this is all controlled<04:03:21.000> access<04:03:21.199> and<04:03:22.199> this<04:03:22.500> mux<04:03:22.979> is<04:03:23.279> that 04:03:23.570 --> 04:03:23.580 align:start position:0% controlled access and this mux is that 04:03:23.580 --> 04:03:25.910 align:start position:0% controlled access and this mux is that device<04:03:23.880> we<04:03:24.239> were<04:03:24.420> talking<04:03:24.660> about<04:03:24.960> that<04:03:25.739> is 04:03:25.910 --> 04:03:25.920 align:start position:0% device we were talking about that is 04:03:25.920 --> 04:03:28.610 align:start position:0% device we were talking about that is doing<04:03:26.220> the<04:03:26.939> controlling<04:03:27.479> now<04:03:28.080> a<04:03:28.439> different 04:03:28.610 --> 04:03:28.620 align:start position:0% doing the controlling now a different 04:03:28.620 --> 04:03:31.309 align:start position:0% doing the controlling now a different type<04:03:29.040> of<04:03:29.279> controlled<04:03:30.000> media<04:03:30.479> access<04:03:30.660> method 04:03:31.309 --> 04:03:31.319 align:start position:0% type of controlled media access method 04:03:31.319 --> 04:03:33.590 align:start position:0% type of controlled media access method is<04:03:31.920> called<04:03:32.160> polling<04:03:32.760> and<04:03:33.120> as<04:03:33.300> the<04:03:33.479> name 04:03:33.590 --> 04:03:33.600 align:start position:0% is called polling and as the name 04:03:33.600 --> 04:03:35.929 align:start position:0% is called polling and as the name implies<04:03:34.020> we<04:03:34.380> have<04:03:34.500> a<04:03:34.800> central<04:03:34.920> device<04:03:35.340> as<04:03:35.819> well 04:03:35.929 --> 04:03:35.939 align:start position:0% implies we have a central device as well 04:03:35.939 --> 04:03:38.269 align:start position:0% implies we have a central device as well that<04:03:36.300> goes<04:03:36.600> to<04:03:36.720> each<04:03:36.960> node<04:03:37.199> in<04:03:37.380> the<04:03:37.500> network<04:03:37.680> in 04:03:38.269 --> 04:03:38.279 align:start position:0% that goes to each node in the network in 04:03:38.279 --> 04:03:41.090 align:start position:0% that goes to each node in the network in turn<04:03:38.460> and<04:03:39.239> C's<04:03:39.660> and<04:03:39.899> queries<04:03:40.260> them<04:03:40.500> do<04:03:40.979> you 04:03:41.090 --> 04:03:41.100 align:start position:0% turn and C's and queries them do you 04:03:41.100 --> 04:03:43.729 align:start position:0% turn and C's and queries them do you have<04:03:41.220> any<04:03:41.460> data<04:03:41.819> to<04:03:42.000> transmit<04:03:42.479> with<04:03:43.319> polling 04:03:43.729 --> 04:03:43.739 align:start position:0% have any data to transmit with polling 04:03:43.739 --> 04:03:46.130 align:start position:0% have any data to transmit with polling then<04:03:43.979> there<04:03:44.279> is<04:03:44.520> guaranteed<04:03:45.300> access<04:03:45.600> because 04:03:46.130 --> 04:03:46.140 align:start position:0% then there is guaranteed access because 04:03:46.140 --> 04:03:48.170 align:start position:0% then there is guaranteed access because the<04:03:46.500> process<04:03:46.800> is<04:03:47.100> constantly<04:03:47.640> repeating 04:03:48.170 --> 04:03:48.180 align:start position:0% the process is constantly repeating 04:03:48.180 --> 04:03:50.210 align:start position:0% the process is constantly repeating basically<04:03:48.899> it's<04:03:49.199> just<04:03:49.380> constantly<04:03:49.859> if<04:03:50.040> we 04:03:50.210 --> 04:03:50.220 align:start position:0% basically it's just constantly if we 04:03:50.220 --> 04:03:52.849 align:start position:0% basically it's just constantly if we have<04:03:50.399> this<04:03:50.640> middle<04:03:50.939> mux<04:03:51.479> sort<04:03:51.720> of<04:03:51.779> device<04:03:52.020> it's 04:03:52.849 --> 04:03:52.859 align:start position:0% have this middle mux sort of device it's 04:03:52.859 --> 04:03:54.469 align:start position:0% have this middle mux sort of device it's constantly<04:03:53.340> going 04:03:54.469 --> 04:03:54.479 align:start position:0% constantly going 04:03:54.479 --> 04:03:59.929 align:start position:0% constantly going to<04:03:55.140> each 04:03:59.929 --> 04:03:59.939 align:start position:0% 04:03:59.939 --> 04:04:02.330 align:start position:0% device<04:04:00.600> and<04:04:00.960> saying<04:04:01.319> hey<04:04:01.439> are<04:04:01.739> you<04:04:01.920> ready<04:04:02.100> to 04:04:02.330 --> 04:04:02.340 align:start position:0% device and saying hey are you ready to 04:04:02.340 --> 04:04:03.969 align:start position:0% device and saying hey are you ready to send<04:04:02.460> something<04:04:02.760> you<04:04:03.120> now<04:04:03.300> have<04:04:03.600> access 04:04:03.969 --> 04:04:03.979 align:start position:0% send something you now have access 04:04:03.979 --> 04:04:06.769 align:start position:0% send something you now have access although<04:04:04.979> this<04:04:05.279> guaranteed<04:04:05.819> access<04:04:06.180> in<04:04:06.600> this 04:04:06.769 --> 04:04:06.779 align:start position:0% although this guaranteed access in this 04:04:06.779 --> 04:04:09.530 align:start position:0% although this guaranteed access in this method<04:04:07.140> is<04:04:07.620> reliable<04:04:08.160> it<04:04:08.880> might<04:04:09.000> not<04:04:09.120> be<04:04:09.300> as 04:04:09.530 --> 04:04:09.540 align:start position:0% method is reliable it might not be as 04:04:09.540 --> 04:04:13.790 align:start position:0% method is reliable it might not be as effective<04:04:10.080> in<04:04:10.500> time<04:04:10.739> sensitive<04:04:11.279> Networks 04:04:13.790 --> 04:04:13.800 align:start position:0% 04:04:13.800 --> 04:04:15.889 align:start position:0% and<04:04:14.340> time<04:04:14.580> can<04:04:14.939> affect<04:04:15.239> sometimes 04:04:15.889 --> 04:04:15.899 align:start position:0% and time can affect sometimes 04:04:15.899 --> 04:04:18.290 align:start position:0% and time can affect sometimes potentially<04:04:16.439> be<04:04:16.800> wasted 04:04:18.290 --> 04:04:18.300 align:start position:0% potentially be wasted 04:04:18.300 --> 04:04:21.370 align:start position:0% potentially be wasted in<04:04:18.840> this<04:04:18.960> querying<04:04:19.560> in<04:04:19.979> this<04:04:20.220> polling<04:04:20.699> because 04:04:21.370 --> 04:04:21.380 align:start position:0% in this querying in this polling because 04:04:21.380 --> 04:04:23.809 align:start position:0% in this querying in this polling because sometimes<04:04:22.380> I'm<04:04:22.560> having<04:04:22.739> to<04:04:22.979> ask<04:04:23.100> devices<04:04:23.520> that 04:04:23.809 --> 04:04:23.819 align:start position:0% sometimes I'm having to ask devices that 04:04:23.819 --> 04:04:25.910 align:start position:0% sometimes I'm having to ask devices that don't<04:04:23.939> need<04:04:24.180> to<04:04:24.359> transmit<04:04:24.899> anything<04:04:25.140> to<04:04:25.620> if 04:04:25.910 --> 04:04:25.920 align:start position:0% don't need to transmit anything to if 04:04:25.920 --> 04:04:27.950 align:start position:0% don't need to transmit anything to if they<04:04:26.040> need<04:04:26.220> to<04:04:26.340> transmit<04:04:26.760> so<04:04:27.060> this<04:04:27.479> basically 04:04:27.950 --> 04:04:27.960 align:start position:0% they need to transmit so this basically 04:04:27.960 --> 04:04:31.189 align:start position:0% they need to transmit so this basically wastes<04:04:28.560> time<04:04:29.060> another<04:04:30.060> example<04:04:30.540> of<04:04:30.779> this<04:04:31.020> by 04:04:31.189 --> 04:04:31.199 align:start position:0% wastes time another example of this by 04:04:31.199 --> 04:04:34.309 align:start position:0% wastes time another example of this by the<04:04:31.319> way<04:04:31.380> is<04:04:31.500> if<04:04:31.920> for<04:04:32.399> instance<04:04:32.640> node<04:04:33.180> a<04:04:33.540> at<04:04:34.020> one 04:04:34.309 --> 04:04:34.319 align:start position:0% the way is if for instance node a at one 04:04:34.319 --> 04:04:35.750 align:start position:0% the way is if for instance node a at one point 04:04:35.750 --> 04:04:35.760 align:start position:0% point 04:04:35.760 --> 04:04:39.410 align:start position:0% point finds<04:04:36.479> it<04:04:36.600> as<04:04:36.779> data<04:04:37.140> to<04:04:37.260> transmit<04:04:38.000> node<04:04:39.000> a<04:04:39.180> has 04:04:39.410 --> 04:04:39.420 align:start position:0% finds it as data to transmit node a has 04:04:39.420 --> 04:04:41.570 align:start position:0% finds it as data to transmit node a has to<04:04:39.600> wait<04:04:39.779> until<04:04:40.140> basically<04:04:40.800> the<04:04:41.220> polling 04:04:41.570 --> 04:04:41.580 align:start position:0% to wait until basically the polling 04:04:41.580 --> 04:04:43.969 align:start position:0% to wait until basically the polling device<04:04:41.819> comes<04:04:42.720> all<04:04:42.899> the<04:04:43.020> way<04:04:43.140> around<04:04:43.380> to<04:04:43.800> it 04:04:43.969 --> 04:04:43.979 align:start position:0% device comes all the way around to it 04:04:43.979 --> 04:04:46.370 align:start position:0% device comes all the way around to it before<04:04:44.699> it's<04:04:45.000> allowed<04:04:45.359> to<04:04:45.420> transmit<04:04:45.899> the<04:04:46.080> data 04:04:46.370 --> 04:04:46.380 align:start position:0% before it's allowed to transmit the data 04:04:46.380 --> 04:04:48.290 align:start position:0% before it's allowed to transmit the data now<04:04:46.739> this<04:04:46.979> can<04:04:47.160> take<04:04:47.279> a<04:04:47.520> lot<04:04:47.580> longer<04:04:48.060> than 04:04:48.290 --> 04:04:48.300 align:start position:0% now this can take a lot longer than 04:04:48.300 --> 04:04:51.290 align:start position:0% now this can take a lot longer than simply<04:04:48.660> just<04:04:49.020> asking<04:04:49.800> if<04:04:50.040> it<04:04:50.220> can<04:04:50.399> then<04:04:50.880> just 04:04:51.290 --> 04:04:51.300 align:start position:0% simply just asking if it can then just 04:04:51.300 --> 04:04:53.389 align:start position:0% simply just asking if it can then just send<04:04:51.840> the<04:04:52.020> data<04:04:52.439> along 04:04:53.389 --> 04:04:53.399 align:start position:0% send the data along 04:04:53.399 --> 04:04:55.610 align:start position:0% send the data along now<04:04:53.699> because<04:04:54.060> of<04:04:54.359> these<04:04:54.660> negatives<04:04:54.960> there's<04:04:55.319> a 04:04:55.610 --> 04:04:55.620 align:start position:0% now because of these negatives there's a 04:04:55.620 --> 04:04:57.769 align:start position:0% now because of these negatives there's a variation<04:04:56.100> of<04:04:56.399> this<04:04:56.520> polling<04:04:57.000> which<04:04:57.540> is 04:04:57.769 --> 04:04:57.779 align:start position:0% variation of this polling which is 04:04:57.779 --> 04:05:01.969 align:start position:0% variation of this polling which is called<04:04:58.279> demand<04:04:59.279> priority<04:04:59.960> where<04:05:00.960> each<04:05:01.500> node 04:05:01.969 --> 04:05:01.979 align:start position:0% called demand priority where each node 04:05:01.979 --> 04:05:05.150 align:start position:0% called demand priority where each node signals<04:05:02.760> when<04:05:03.180> it<04:05:03.420> has<04:05:03.660> to<04:05:03.960> transmit<04:05:04.680> or<04:05:04.979> not 04:05:05.150 --> 04:05:05.160 align:start position:0% signals when it has to transmit or not 04:05:05.160 --> 04:05:07.910 align:start position:0% signals when it has to transmit or not transmit<04:05:05.760> this<04:05:06.600> method<04:05:06.899> contains<04:05:07.439> within<04:05:07.739> it 04:05:07.910 --> 04:05:07.920 align:start position:0% transmit this method contains within it 04:05:07.920 --> 04:05:10.790 align:start position:0% transmit this method contains within it measures<04:05:08.340> to<04:05:08.699> Grant<04:05:09.120> priority<04:05:09.660> to<04:05:09.960> nodes<04:05:10.260> that 04:05:10.790 --> 04:05:10.800 align:start position:0% measures to Grant priority to nodes that 04:05:10.800 --> 04:05:12.830 align:start position:0% measures to Grant priority to nodes that have<04:05:11.040> immediate<04:05:11.699> data<04:05:12.120> that<04:05:12.359> it<04:05:12.479> needs<04:05:12.720> to 04:05:12.830 --> 04:05:12.840 align:start position:0% have immediate data that it needs to 04:05:12.840 --> 04:05:15.530 align:start position:0% have immediate data that it needs to transmit<04:05:13.380> it<04:05:13.920> also<04:05:14.220> contains<04:05:14.640> measures<04:05:15.120> and 04:05:15.530 --> 04:05:15.540 align:start position:0% transmit it also contains measures and 04:05:15.540 --> 04:05:18.050 align:start position:0% transmit it also contains measures and controls<04:05:16.020> to<04:05:16.260> ensure<04:05:16.500> that<04:05:16.800> nodes<04:05:17.160> can't 04:05:18.050 --> 04:05:18.060 align:start position:0% controls to ensure that nodes can't 04:05:18.060 --> 04:05:20.210 align:start position:0% controls to ensure that nodes can't constantly<04:05:18.720> signal<04:05:19.140> they<04:05:19.380> have<04:05:19.560> priority 04:05:20.210 --> 04:05:20.220 align:start position:0% constantly signal they have priority 04:05:20.220 --> 04:05:22.910 align:start position:0% constantly signal they have priority data<04:05:20.760> because<04:05:21.540> then<04:05:21.779> you<04:05:22.020> would<04:05:22.140> have<04:05:22.319> one 04:05:22.910 --> 04:05:22.920 align:start position:0% data because then you would have one 04:05:22.920 --> 04:05:25.189 align:start position:0% data because then you would have one device<04:05:23.220> that's<04:05:23.760> constantly<04:05:24.300> sort<04:05:24.540> of<04:05:24.720> hogging 04:05:25.189 --> 04:05:25.199 align:start position:0% device that's constantly sort of hogging 04:05:25.199 --> 04:05:27.769 align:start position:0% device that's constantly sort of hogging your<04:05:25.439> network<04:05:25.620> so<04:05:26.399> those<04:05:26.699> are<04:05:26.880> our<04:05:27.060> controlled 04:05:27.769 --> 04:05:27.779 align:start position:0% your network so those are our controlled 04:05:27.779 --> 04:05:30.830 align:start position:0% your network so those are our controlled based<04:05:28.080> media<04:05:28.439> access<04:05:28.620> let's<04:05:29.520> and<04:05:29.880> and<04:05:30.120> really 04:05:30.830 --> 04:05:30.840 align:start position:0% based media access let's and and really 04:05:30.840 --> 04:05:32.929 align:start position:0% based media access let's and and really we<04:05:31.080> we<04:05:31.140> see<04:05:31.620> these<04:05:31.920> employed<04:05:32.520> in<04:05:32.760> certain 04:05:32.929 --> 04:05:32.939 align:start position:0% we we see these employed in certain 04:05:32.939 --> 04:05:35.269 align:start position:0% we we see these employed in certain circumstances<04:05:33.600> but<04:05:34.020> you're<04:05:34.380> going<04:05:34.620> to<04:05:34.979> more 04:05:35.269 --> 04:05:35.279 align:start position:0% circumstances but you're going to more 04:05:35.279 --> 04:05:36.910 align:start position:0% circumstances but you're going to more encounter 04:05:36.910 --> 04:05:36.920 align:start position:0% encounter 04:05:36.920 --> 04:05:39.349 align:start position:0% encounter contention-based<04:05:37.920> media<04:05:38.340> access<04:05:38.460> and<04:05:39.180> in 04:05:39.349 --> 04:05:39.359 align:start position:0% contention-based media access and in 04:05:39.359 --> 04:05:40.969 align:start position:0% contention-based media access and in contention-based<04:05:40.199> media<04:05:40.380> access<04:05:40.500> there<04:05:40.859> are 04:05:40.969 --> 04:05:40.979 align:start position:0% contention-based media access there are 04:05:40.979 --> 04:05:42.170 align:start position:0% contention-based media access there are two<04:05:41.100> different<04:05:41.220> types<04:05:41.520> I<04:05:41.640> want<04:05:41.760> to<04:05:41.939> talk<04:05:42.000> about 04:05:42.170 --> 04:05:42.180 align:start position:0% two different types I want to talk about 04:05:42.180 --> 04:05:44.889 align:start position:0% two different types I want to talk about Collision<04:05:43.140> detection<04:05:43.680> is<04:05:44.460> a 04:05:44.889 --> 04:05:44.899 align:start position:0% Collision detection is a 04:05:44.899 --> 04:05:47.630 align:start position:0% Collision detection is a contention-based<04:05:45.899> media<04:05:46.620> access<04:05:46.920> method 04:05:47.630 --> 04:05:47.640 align:start position:0% contention-based media access method 04:05:47.640 --> 04:05:51.670 align:start position:0% contention-based media access method that<04:05:48.300> attempts<04:05:49.020> to<04:05:49.680> provide<04:05:50.340> Collision<04:05:51.120> free 04:05:51.670 --> 04:05:51.680 align:start position:0% that attempts to provide Collision free 04:05:51.680 --> 04:05:54.710 align:start position:0% that attempts to provide Collision free data<04:05:52.680> transfer<04:05:53.160> in<04:05:53.699> Ethernet<04:05:54.120> local<04:05:54.359> area 04:05:54.710 --> 04:05:54.720 align:start position:0% data transfer in Ethernet local area 04:05:54.720 --> 04:05:57.710 align:start position:0% data transfer in Ethernet local area Networks<04:05:55.620> so<04:05:56.100> the<04:05:56.340> key<04:05:56.520> here<04:05:56.760> is<04:05:56.939> this<04:05:57.239> is<04:05:57.420> what 04:05:57.710 --> 04:05:57.720 align:start position:0% Networks so the key here is this is what 04:05:57.720 --> 04:06:01.490 align:start position:0% Networks so the key here is this is what ethernet<04:05:58.319> uses<04:05:58.819> with<04:05:59.819> csma<04:06:00.359> CD<04:06:00.960> or<04:06:01.199> Collision 04:06:01.490 --> 04:06:01.500 align:start position:0% ethernet uses with csma CD or Collision 04:06:01.500 --> 04:06:04.189 align:start position:0% ethernet uses with csma CD or Collision detection<04:06:02.000> nodes<04:06:03.000> transmit<04:06:03.660> when<04:06:03.840> they<04:06:04.020> have 04:06:04.189 --> 04:06:04.199 align:start position:0% detection nodes transmit when they have 04:06:04.199 --> 04:06:06.710 align:start position:0% detection nodes transmit when they have data<04:06:04.620> to<04:06:04.739> send<04:06:04.920> and<04:06:05.760> then<04:06:05.939> when<04:06:06.239> a<04:06:06.420> collision 04:06:06.710 --> 04:06:06.720 align:start position:0% data to send and then when a collision 04:06:06.720 --> 04:06:09.429 align:start position:0% data to send and then when a collision occurs<04:06:07.500> they're<04:06:08.100> basically<04:06:08.460> detected 04:06:09.429 --> 04:06:09.439 align:start position:0% occurs they're basically detected 04:06:09.439 --> 04:06:12.830 align:start position:0% occurs they're basically detected managed<04:06:10.439> and<04:06:10.920> then<04:06:11.040> the<04:06:11.279> data<04:06:11.580> is<04:06:11.880> resent<04:06:12.540> or 04:06:12.830 --> 04:06:12.840 align:start position:0% managed and then the data is resent or 04:06:12.840 --> 04:06:14.990 align:start position:0% managed and then the data is resent or retransmitted<04:06:13.680> appropriately<04:06:14.220> to<04:06:14.760> get<04:06:14.880> a 04:06:14.990 --> 04:06:15.000 align:start position:0% retransmitted appropriately to get a 04:06:15.000 --> 04:06:16.370 align:start position:0% retransmitted appropriately to get a better<04:06:15.120> sense<04:06:15.359> of<04:06:15.600> this<04:06:15.720> and<04:06:15.960> because<04:06:16.140> it's 04:06:16.370 --> 04:06:16.380 align:start position:0% better sense of this and because it's 04:06:16.380 --> 04:06:17.870 align:start position:0% better sense of this and because it's one<04:06:16.560> that<04:06:16.800> we<04:06:17.220> really<04:06:17.340> need<04:06:17.580> to<04:06:17.699> understand 04:06:17.870 --> 04:06:17.880 align:start position:0% one that we really need to understand 04:06:17.880 --> 04:06:19.910 align:start position:0% one that we really need to understand let's<04:06:18.779> take<04:06:19.020> a<04:06:19.140> look 04:06:19.910 --> 04:06:19.920 align:start position:0% let's take a look 04:06:19.920 --> 04:06:24.769 align:start position:0% let's take a look at<04:06:21.239> um<04:06:21.300> an<04:06:21.840> image<04:06:22.140> to<04:06:22.380> give<04:06:22.500> us<04:06:22.620> an<04:06:22.859> idea 04:06:24.769 --> 04:06:24.779 align:start position:0% at um an image to give us an idea 04:06:24.779 --> 04:06:28.370 align:start position:0% at um an image to give us an idea so<04:06:25.439> there<04:06:26.040> are<04:06:26.220> five<04:06:26.520> steps<04:06:27.060> in<04:06:27.660> Collision<04:06:28.020> in 04:06:28.370 --> 04:06:28.380 align:start position:0% so there are five steps in Collision in 04:06:28.380 --> 04:06:30.050 align:start position:0% so there are five steps in Collision in this<04:06:28.500> Collision<04:06:28.800> detection<04:06:29.279> which<04:06:29.640> again<04:06:29.819> I'm 04:06:30.050 --> 04:06:30.060 align:start position:0% this Collision detection which again I'm 04:06:30.060 --> 04:06:32.150 align:start position:0% this Collision detection which again I'm just<04:06:30.180> going<04:06:30.300> to<04:06:30.359> throw<04:06:30.479> this<04:06:30.720> up<04:06:30.899> there<04:06:31.140> is<04:06:31.800> a 04:06:32.150 --> 04:06:32.160 align:start position:0% just going to throw this up there is a 04:06:32.160 --> 04:06:33.189 align:start position:0% just going to throw this up there is a contention 04:06:33.189 --> 04:06:33.199 align:start position:0% contention 04:06:33.199 --> 04:06:36.349 align:start position:0% contention based<04:06:34.199> media<04:06:34.800> access<04:06:34.979> method 04:06:36.349 --> 04:06:36.359 align:start position:0% based media access method 04:06:36.359 --> 04:06:39.590 align:start position:0% based media access method in<04:06:36.840> step<04:06:37.020> one<04:06:37.380> we<04:06:38.100> just<04:06:38.340> say<04:06:38.580> that<04:06:38.880> the<04:06:39.239> node 04:06:39.590 --> 04:06:39.600 align:start position:0% in step one we just say that the node 04:06:39.600 --> 04:06:43.429 align:start position:0% in step one we just say that the node itself<04:06:40.020> wants<04:06:40.859> to<04:06:40.979> uh<04:06:41.880> transmit<04:06:42.420> data<04:06:42.840> so<04:06:43.319> what 04:06:43.429 --> 04:06:43.439 align:start position:0% itself wants to uh transmit data so what 04:06:43.439 --> 04:06:45.410 align:start position:0% itself wants to uh transmit data so what it<04:06:43.620> then<04:06:43.739> does<04:06:43.979> in<04:06:44.220> step<04:06:44.399> two<04:06:44.580> is<04:06:44.819> it<04:06:45.060> basically 04:06:45.410 --> 04:06:45.420 align:start position:0% it then does in step two is it basically 04:06:45.420 --> 04:06:48.110 align:start position:0% it then does in step two is it basically checks<04:06:45.960> the<04:06:46.080> network<04:06:46.260> for<04:06:46.680> availability 04:06:48.110 --> 04:06:48.120 align:start position:0% checks the network for availability 04:06:48.120 --> 04:06:50.630 align:start position:0% checks the network for availability now<04:06:48.600> in<04:06:48.779> step<04:06:48.960> three<04:06:49.140> the<04:06:49.500> node<04:06:49.800> transmits 04:06:50.630 --> 04:06:50.640 align:start position:0% now in step three the node transmits 04:06:50.640 --> 04:06:52.309 align:start position:0% now in step three the node transmits that<04:06:50.819> data<04:06:51.180> and<04:06:51.600> waits<04:06:52.020> for<04:06:52.140> an 04:06:52.309 --> 04:06:52.319 align:start position:0% that data and waits for an 04:06:52.319 --> 04:06:54.469 align:start position:0% that data and waits for an acknowledgment<04:06:52.800> from<04:06:53.340> the<04:06:53.640> receiver<04:06:54.000> that<04:06:54.359> it 04:06:54.469 --> 04:06:54.479 align:start position:0% acknowledgment from the receiver that it 04:06:54.479 --> 04:06:57.769 align:start position:0% acknowledgment from the receiver that it got<04:06:54.660> there<04:06:54.899> which<04:06:55.560> is<04:06:55.739> called<04:06:55.920> an<04:06:56.220> ack 04:06:57.769 --> 04:06:57.779 align:start position:0% got there which is called an ack 04:06:57.779 --> 04:07:01.550 align:start position:0% got there which is called an ack packet<04:06:58.680> an<04:06:59.160> acknowledgment<04:06:59.760> packet<04:07:00.720> in<04:07:01.319> step 04:07:01.550 --> 04:07:01.560 align:start position:0% packet an acknowledgment packet in step 04:07:01.560 --> 04:07:03.130 align:start position:0% packet an acknowledgment packet in step four<04:07:01.739> this<04:07:02.100> is<04:07:02.160> where<04:07:02.340> stuff<04:07:02.520> really<04:07:02.760> happens 04:07:03.130 --> 04:07:03.140 align:start position:0% four this is where stuff really happens 04:07:03.140 --> 04:07:06.950 align:start position:0% four this is where stuff really happens uh<04:07:04.140> if<04:07:04.439> there<04:07:04.680> is<04:07:04.859> a<04:07:05.160> collision<04:07:05.640> the<04:07:06.540> packet 04:07:06.950 --> 04:07:06.960 align:start position:0% uh if there is a collision the packet 04:07:06.960 --> 04:07:09.110 align:start position:0% uh if there is a collision the packet size<04:07:07.260> will<04:07:07.680> identify<04:07:08.220> if<04:07:08.460> one<04:07:08.640> occurred 04:07:09.110 --> 04:07:09.120 align:start position:0% size will identify if one occurred 04:07:09.120 --> 04:07:11.389 align:start position:0% size will identify if one occurred because<04:07:09.540> what<04:07:09.899> happens<04:07:10.080> is<04:07:10.439> boom<04:07:10.859> I<04:07:11.040> have<04:07:11.220> this 04:07:11.389 --> 04:07:11.399 align:start position:0% because what happens is boom I have this 04:07:11.399 --> 04:07:13.729 align:start position:0% because what happens is boom I have this collision<04:07:11.699> and<04:07:11.880> now<04:07:12.060> my<04:07:12.239> packet<04:07:12.600> size<04:07:12.840> changes 04:07:13.729 --> 04:07:13.739 align:start position:0% collision and now my packet size changes 04:07:13.739 --> 04:07:16.130 align:start position:0% collision and now my packet size changes so<04:07:14.520> in<04:07:14.699> step<04:07:14.880> five<04:07:15.180> if<04:07:15.660> that<04:07:15.840> Collision 04:07:16.130 --> 04:07:16.140 align:start position:0% so in step five if that Collision 04:07:16.140 --> 04:07:18.590 align:start position:0% so in step five if that Collision occurred<04:07:16.680> both<04:07:17.399> transmitting<04:07:18.060> nodes<04:07:18.300> and<04:07:18.479> by 04:07:18.590 --> 04:07:18.600 align:start position:0% occurred both transmitting nodes and by 04:07:18.600 --> 04:07:20.750 align:start position:0% occurred both transmitting nodes and by the<04:07:18.720> way<04:07:18.779> the<04:07:19.080> reason<04:07:19.199> a<04:07:19.620> a<04:07:19.979> collision<04:07:20.580> is 04:07:20.750 --> 04:07:20.760 align:start position:0% the way the reason a a collision is 04:07:20.760 --> 04:07:22.250 align:start position:0% the way the reason a a collision is going<04:07:20.880> to<04:07:20.939> occur<04:07:21.180> is<04:07:21.300> because<04:07:21.479> another<04:07:21.840> device 04:07:22.250 --> 04:07:22.260 align:start position:0% going to occur is because another device 04:07:22.260 --> 04:07:25.490 align:start position:0% going to occur is because another device is<04:07:23.100> also<04:07:23.460> trying<04:07:23.760> to<04:07:24.180> transmit<04:07:25.020> at<04:07:25.199> the<04:07:25.380> same 04:07:25.490 --> 04:07:25.500 align:start position:0% is also trying to transmit at the same 04:07:25.500 --> 04:07:28.010 align:start position:0% is also trying to transmit at the same time<04:07:25.739> so<04:07:26.460> in<04:07:26.699> step<04:07:26.939> five<04:07:27.239> if<04:07:27.600> the<04:07:27.720> Collision 04:07:28.010 --> 04:07:28.020 align:start position:0% time so in step five if the Collision 04:07:28.020 --> 04:07:30.950 align:start position:0% time so in step five if the Collision occurred<04:07:28.560> I<04:07:28.979> wait<04:07:29.160> a<04:07:29.520> set<04:07:29.640> period<04:07:30.060> of<04:07:30.239> time<04:07:30.479> and 04:07:30.950 --> 04:07:30.960 align:start position:0% occurred I wait a set period of time and 04:07:30.960 --> 04:07:33.889 align:start position:0% occurred I wait a set period of time and then<04:07:31.080> I<04:07:31.380> try<04:07:31.620> to<04:07:31.800> retransmit<04:07:32.580> again<04:07:32.760> now<04:07:33.540> this 04:07:33.889 --> 04:07:33.899 align:start position:0% then I try to retransmit again now this 04:07:33.899 --> 04:07:35.210 align:start position:0% then I try to retransmit again now this might<04:07:34.080> seem<04:07:34.380> like<04:07:34.560> it's<04:07:34.739> not<04:07:34.979> a<04:07:35.160> very 04:07:35.210 --> 04:07:35.220 align:start position:0% might seem like it's not a very 04:07:35.220 --> 04:07:37.670 align:start position:0% might seem like it's not a very effective<04:07:35.699> way<04:07:36.000> of<04:07:36.359> transmitting<04:07:36.899> data<04:07:37.260> but 04:07:37.670 --> 04:07:37.680 align:start position:0% effective way of transmitting data but 04:07:37.680 --> 04:07:39.650 align:start position:0% effective way of transmitting data but it<04:07:37.859> happens<04:07:37.979> at<04:07:38.340> such<04:07:38.520> a<04:07:38.760> fast<04:07:38.939> speed<04:07:39.300> that 04:07:39.650 --> 04:07:39.660 align:start position:0% it happens at such a fast speed that 04:07:39.660 --> 04:07:42.229 align:start position:0% it happens at such a fast speed that actually<04:07:39.899> it<04:07:40.199> works<04:07:40.500> quite<04:07:40.800> well<04:07:41.040> as<04:07:41.939> long<04:07:42.120> as 04:07:42.229 --> 04:07:42.239 align:start position:0% actually it works quite well as long as 04:07:42.239 --> 04:07:44.389 align:start position:0% actually it works quite well as long as we<04:07:42.420> don't<04:07:42.540> have<04:07:42.660> too<04:07:42.960> many<04:07:43.140> devices<04:07:43.620> in<04:07:44.220> the 04:07:44.389 --> 04:07:44.399 align:start position:0% we don't have too many devices in the 04:07:44.399 --> 04:07:47.090 align:start position:0% we don't have too many devices in the same<04:07:44.640> network<04:07:45.300> contending<04:07:46.199> for<04:07:46.500> Access<04:07:46.680> which 04:07:47.090 --> 04:07:47.100 align:start position:0% same network contending for Access which 04:07:47.100 --> 04:07:49.189 align:start position:0% same network contending for Access which we'll<04:07:47.220> talk<04:07:47.460> about<04:07:47.580> in<04:07:47.939> just<04:07:48.060> a<04:07:48.239> bit<04:07:48.359> now<04:07:49.080> you 04:07:49.189 --> 04:07:49.199 align:start position:0% we'll talk about in just a bit now you 04:07:49.199 --> 04:07:50.570 align:start position:0% we'll talk about in just a bit now you can<04:07:49.319> understand<04:07:49.439> why<04:07:49.859> this<04:07:50.040> works<04:07:50.340> really 04:07:50.570 --> 04:07:50.580 align:start position:0% can understand why this works really 04:07:50.580 --> 04:07:54.769 align:start position:0% can understand why this works really well<04:07:50.880> in<04:07:51.239> Ethernet<04:07:51.720> networks<04:07:52.199> wired<04:07:52.859> Networks 04:07:54.769 --> 04:07:54.779 align:start position:0% well in Ethernet networks wired Networks 04:07:54.779 --> 04:07:58.130 align:start position:0% well in Ethernet networks wired Networks because<04:07:55.620> I<04:07:56.340> can<04:07:56.520> continue<04:07:56.760> to<04:07:57.420> collide<04:07:57.840> and 04:07:58.130 --> 04:07:58.140 align:start position:0% because I can continue to collide and 04:07:58.140 --> 04:07:59.809 align:start position:0% because I can continue to collide and then<04:07:58.260> send<04:07:58.560> something<04:07:58.800> out<04:07:59.100> again<04:07:59.279> and<04:07:59.640> many 04:07:59.809 --> 04:07:59.819 align:start position:0% then send something out again and many 04:07:59.819 --> 04:08:01.429 align:start position:0% then send something out again and many times<04:08:00.000> as<04:08:00.180> I<04:08:00.359> need<04:08:00.479> until<04:08:00.660> the<04:08:00.899> data<04:08:01.199> gets 04:08:01.429 --> 04:08:01.439 align:start position:0% times as I need until the data gets 04:08:01.439 --> 04:08:04.429 align:start position:0% times as I need until the data gets there<04:08:01.560> but<04:08:02.520> in<04:08:02.939> wireless<04:08:03.180> settings<04:08:03.779> this 04:08:04.429 --> 04:08:04.439 align:start position:0% there but in wireless settings this 04:08:04.439 --> 04:08:05.870 align:start position:0% there but in wireless settings this isn't<04:08:04.680> really<04:08:04.859> going<04:08:05.040> to<04:08:05.160> work<04:08:05.279> so<04:08:05.520> well<04:08:05.699> for 04:08:05.870 --> 04:08:05.880 align:start position:0% isn't really going to work so well for 04:08:05.880 --> 04:08:07.490 align:start position:0% isn't really going to work so well for us<04:08:06.060> in<04:08:06.660> this<04:08:06.779> case<04:08:06.899> we're<04:08:07.140> going<04:08:07.260> to<04:08:07.380> use 04:08:07.490 --> 04:08:07.500 align:start position:0% us in this case we're going to use 04:08:07.500 --> 04:08:09.830 align:start position:0% us in this case we're going to use carrier<04:08:08.100> sense<04:08:08.399> multiple<04:08:08.819> axis<04:08:09.180> collision 04:08:09.830 --> 04:08:09.840 align:start position:0% carrier sense multiple axis collision 04:08:09.840 --> 04:08:12.650 align:start position:0% carrier sense multiple axis collision avoidance<04:08:10.680> meaning<04:08:11.220> we<04:08:11.640> don't<04:08:11.939> want<04:08:12.359> a 04:08:12.650 --> 04:08:12.660 align:start position:0% avoidance meaning we don't want a 04:08:12.660 --> 04:08:14.269 align:start position:0% avoidance meaning we don't want a collision<04:08:12.960> to<04:08:13.199> occur 04:08:14.269 --> 04:08:14.279 align:start position:0% collision to occur 04:08:14.279 --> 04:08:16.610 align:start position:0% collision to occur in<04:08:14.939> this<04:08:15.140> contention-based<04:08:16.140> media<04:08:16.500> access 04:08:16.610 --> 04:08:16.620 align:start position:0% in this contention-based media access 04:08:16.620 --> 04:08:19.630 align:start position:0% in this contention-based media access method<04:08:17.279> there<04:08:18.060> are<04:08:18.180> six<04:08:18.479> steps<04:08:18.899> that<04:08:19.140> provide 04:08:19.630 --> 04:08:19.640 align:start position:0% method there are six steps that provide 04:08:19.640 --> 04:08:23.030 align:start position:0% method there are six steps that provide Collision<04:08:20.640> free<04:08:21.300> Communication<04:08:21.960> in<04:08:22.800> Wireless 04:08:23.030 --> 04:08:23.040 align:start position:0% Collision free Communication in Wireless 04:08:23.040 --> 04:08:26.750 align:start position:0% Collision free Communication in Wireless Lanes<04:08:23.760> specifically<04:08:24.359> now<04:08:25.319> similar<04:08:25.680> to<04:08:25.859> csma 04:08:26.750 --> 04:08:26.760 align:start position:0% Lanes specifically now similar to csma 04:08:26.760 --> 04:08:30.229 align:start position:0% Lanes specifically now similar to csma CD<04:08:27.680> nodes<04:08:28.680> transmit<04:08:29.220> when<04:08:29.399> they<04:08:29.640> have<04:08:29.760> data<04:08:30.120> to 04:08:30.229 --> 04:08:30.239 align:start position:0% CD nodes transmit when they have data to 04:08:30.239 --> 04:08:33.170 align:start position:0% CD nodes transmit when they have data to send<04:08:30.479> however<04:08:31.260> the<04:08:31.979> node<04:08:32.160> takes<04:08:32.520> preventative 04:08:33.170 --> 04:08:33.180 align:start position:0% send however the node takes preventative 04:08:33.180 --> 04:08:35.450 align:start position:0% send however the node takes preventative measures<04:08:33.720> basically<04:08:34.319> by<04:08:34.620> sending<04:08:34.979> out<04:08:35.160> a 04:08:35.450 --> 04:08:35.460 align:start position:0% measures basically by sending out a 04:08:35.460 --> 04:08:37.370 align:start position:0% measures basically by sending out a jamming<04:08:35.880> signal<04:08:36.300> or<04:08:36.600> a<04:08:36.720> signal<04:08:36.960> to<04:08:37.080> all<04:08:37.260> the 04:08:37.370 --> 04:08:37.380 align:start position:0% jamming signal or a signal to all the 04:08:37.380 --> 04:08:39.590 align:start position:0% jamming signal or a signal to all the other<04:08:37.500> computers<04:08:38.160> that<04:08:38.880> tell<04:08:39.120> all<04:08:39.359> the<04:08:39.479> other 04:08:39.590 --> 04:08:39.600 align:start position:0% other computers that tell all the other 04:08:39.600 --> 04:08:42.050 align:start position:0% other computers that tell all the other computers<04:08:40.140> that<04:08:40.800> there<04:08:41.040> is<04:08:41.220> uh<04:08:41.520> something<04:08:41.760> to 04:08:42.050 --> 04:08:42.060 align:start position:0% computers that there is uh something to 04:08:42.060 --> 04:08:43.130 align:start position:0% computers that there is uh something to be<04:08:42.180> sent 04:08:43.130 --> 04:08:43.140 align:start position:0% be sent 04:08:43.140 --> 04:08:45.110 align:start position:0% be sent and<04:08:43.739> therefore<04:08:44.100> no<04:08:44.460> one<04:08:44.580> else<04:08:44.699> is<04:08:44.880> going<04:08:45.060> to 04:08:45.110 --> 04:08:45.120 align:start position:0% and therefore no one else is going to 04:08:45.120 --> 04:08:46.969 align:start position:0% and therefore no one else is going to send<04:08:45.300> anything<04:08:45.540> for<04:08:45.960> a<04:08:46.080> set<04:08:46.260> period<04:08:46.620> of<04:08:46.739> time 04:08:46.969 --> 04:08:46.979 align:start position:0% send anything for a set period of time 04:08:46.979 --> 04:08:49.550 align:start position:0% send anything for a set period of time so<04:08:47.399> let's<04:08:47.580> take<04:08:47.760> a<04:08:47.880> look<04:08:48.000> at<04:08:48.239> this<04:08:48.479> in<04:08:49.140> a<04:08:49.260> visual 04:08:49.550 --> 04:08:49.560 align:start position:0% so let's take a look at this in a visual 04:08:49.560 --> 04:08:50.990 align:start position:0% so let's take a look at this in a visual way 04:08:50.990 --> 04:08:51.000 align:start position:0% way 04:08:51.000 --> 04:08:53.450 align:start position:0% way so<04:08:51.540> the<04:08:52.020> first<04:08:52.199> step<04:08:52.380> in<04:08:52.560> here<04:08:52.680> like<04:08:53.040> with<04:08:53.279> the 04:08:53.450 --> 04:08:53.460 align:start position:0% so the first step in here like with the 04:08:53.460 --> 04:08:56.389 align:start position:0% so the first step in here like with the CD<04:08:53.760> or<04:08:54.239> like<04:08:54.540> with<04:08:54.660> CD<04:08:55.020> as<04:08:55.199> opposed<04:08:55.500> to<04:08:55.500> ca<04:08:55.979> is 04:08:56.389 --> 04:08:56.399 align:start position:0% CD or like with CD as opposed to ca is 04:08:56.399 --> 04:08:59.330 align:start position:0% CD or like with CD as opposed to ca is that<04:08:56.580> the<04:08:56.819> transmitting<04:08:57.560> node<04:08:58.560> has<04:08:58.920> data 04:08:59.330 --> 04:08:59.340 align:start position:0% that the transmitting node has data 04:08:59.340 --> 04:09:01.790 align:start position:0% that the transmitting node has data descend<04:08:59.760> now<04:09:00.420> the<04:09:00.720> node<04:09:00.960> checks<04:09:01.500> the<04:09:01.620> network 04:09:01.790 --> 04:09:01.800 align:start position:0% descend now the node checks the network 04:09:01.800 --> 04:09:04.910 align:start position:0% descend now the node checks the network for<04:09:02.520> any<04:09:02.699> Jam<04:09:03.000> signals<04:09:03.660> being<04:09:04.140> transmitted<04:09:04.739> by 04:09:04.910 --> 04:09:04.920 align:start position:0% for any Jam signals being transmitted by 04:09:04.920 --> 04:09:07.010 align:start position:0% for any Jam signals being transmitted by other<04:09:05.040> nodes<04:09:05.340> basically<04:09:05.880> uh<04:09:06.600> has<04:09:06.779> another 04:09:07.010 --> 04:09:07.020 align:start position:0% other nodes basically uh has another 04:09:07.020 --> 04:09:09.050 align:start position:0% other nodes basically uh has another node<04:09:07.439> already<04:09:07.739> sort<04:09:08.100> of<04:09:08.220> said<04:09:08.340> hey<04:09:08.580> I<04:09:08.819> need<04:09:08.939> to 04:09:09.050 --> 04:09:09.060 align:start position:0% node already sort of said hey I need to 04:09:09.060 --> 04:09:11.809 align:start position:0% node already sort of said hey I need to send<04:09:09.239> something<04:09:09.540> if<04:09:10.319> not<04:09:10.560> the<04:09:11.220> transmitting 04:09:11.809 --> 04:09:11.819 align:start position:0% send something if not the transmitting 04:09:11.819 --> 04:09:12.610 align:start position:0% send something if not the transmitting node 04:09:12.610 --> 04:09:12.620 align:start position:0% node 04:09:12.620 --> 04:09:17.990 align:start position:0% node sends<04:09:13.620> uh<04:09:14.220> its<04:09:14.699> own<04:09:14.819> Jam<04:09:15.300> signal 04:09:17.990 --> 04:09:18.000 align:start position:0% 04:09:18.000 --> 04:09:21.290 align:start position:0% saying<04:09:18.899> hey<04:09:19.199> no<04:09:19.680> one<04:09:19.859> else<04:09:20.520> send<04:09:21.060> anything 04:09:21.290 --> 04:09:21.300 align:start position:0% saying hey no one else send anything 04:09:21.300 --> 04:09:22.910 align:start position:0% saying hey no one else send anything because<04:09:21.600> I'm<04:09:21.899> gonna<04:09:22.080> send<04:09:22.380> something<04:09:22.620> right 04:09:22.910 --> 04:09:22.920 align:start position:0% because I'm gonna send something right 04:09:22.920 --> 04:09:23.630 align:start position:0% because I'm gonna send something right now 04:09:23.630 --> 04:09:23.640 align:start position:0% now 04:09:23.640 --> 04:09:26.630 align:start position:0% now then<04:09:24.239> it<04:09:24.660> waits<04:09:25.080> a<04:09:25.260> set<04:09:25.439> period<04:09:25.800> of<04:09:25.920> time<04:09:26.100> to 04:09:26.630 --> 04:09:26.640 align:start position:0% then it waits a set period of time to 04:09:26.640 --> 04:09:28.790 align:start position:0% then it waits a set period of time to allow<04:09:26.939> all<04:09:27.239> the<04:09:27.359> other<04:09:27.479> devices<04:09:27.899> to<04:09:28.439> receive 04:09:28.790 --> 04:09:28.800 align:start position:0% allow all the other devices to receive 04:09:28.800 --> 04:09:31.550 align:start position:0% allow all the other devices to receive this<04:09:29.100> Jam<04:09:29.279> signal<04:09:29.760> and<04:09:30.420> then<04:09:30.600> it<04:09:30.899> transmits 04:09:31.550 --> 04:09:31.560 align:start position:0% this Jam signal and then it transmits 04:09:31.560 --> 04:09:32.570 align:start position:0% this Jam signal and then it transmits the<04:09:31.739> data 04:09:32.570 --> 04:09:32.580 align:start position:0% the data 04:09:32.580 --> 04:09:35.150 align:start position:0% the data now<04:09:33.000> in<04:09:33.239> Step<04:09:33.479> six<04:09:33.779> which<04:09:34.140> is<04:09:34.260> the<04:09:34.560> last<04:09:34.739> step 04:09:35.150 --> 04:09:35.160 align:start position:0% now in Step six which is the last step 04:09:35.160 --> 04:09:37.309 align:start position:0% now in Step six which is the last step the<04:09:35.699> node<04:09:35.939> monitors<04:09:36.359> the<04:09:36.660> network<04:09:36.779> for<04:09:37.140> any 04:09:37.309 --> 04:09:37.319 align:start position:0% the node monitors the network for any 04:09:37.319 --> 04:09:39.769 align:start position:0% the node monitors the network for any other<04:09:37.500> Jam<04:09:37.800> signals<04:09:38.340> from<04:09:38.460> other<04:09:38.640> nodes<04:09:39.060> and 04:09:39.769 --> 04:09:39.779 align:start position:0% other Jam signals from other nodes and 04:09:39.779 --> 04:09:41.870 align:start position:0% other Jam signals from other nodes and if<04:09:40.020> a<04:09:40.140> signal<04:09:40.380> is<04:09:40.560> detected<04:09:40.979> it<04:09:41.279> halts<04:09:41.640> its 04:09:41.870 --> 04:09:41.880 align:start position:0% if a signal is detected it halts its 04:09:41.880 --> 04:09:44.269 align:start position:0% if a signal is detected it halts its transmission<04:09:42.140> Waits<04:09:43.140> a<04:09:43.260> delay<04:09:43.560> and<04:09:44.100> then 04:09:44.269 --> 04:09:44.279 align:start position:0% transmission Waits a delay and then 04:09:44.279 --> 04:09:47.330 align:start position:0% transmission Waits a delay and then tries<04:09:44.699> to<04:09:45.060> transmit<04:09:45.660> again 04:09:47.330 --> 04:09:47.340 align:start position:0% tries to transmit again 04:09:47.340 --> 04:09:50.330 align:start position:0% tries to transmit again this<04:09:48.180> process<04:09:48.540> as<04:09:48.899> you<04:09:49.080> can<04:09:49.199> tell<04:09:49.439> allows 04:09:50.330 --> 04:09:50.340 align:start position:0% this process as you can tell allows 04:09:50.340 --> 04:09:52.790 align:start position:0% this process as you can tell allows wireless<04:09:50.819> devices<04:09:51.540> to<04:09:52.319> communicate 04:09:52.790 --> 04:09:52.800 align:start position:0% wireless devices to communicate 04:09:52.800 --> 04:09:54.950 align:start position:0% wireless devices to communicate efficiently<04:09:53.399> in<04:09:53.699> a<04:09:53.960> contention-based 04:09:54.950 --> 04:09:54.960 align:start position:0% efficiently in a contention-based 04:09:54.960 --> 04:09:57.530 align:start position:0% efficiently in a contention-based network<04:09:55.140> one<04:09:55.500> in<04:09:55.680> which<04:09:55.859> it's<04:09:55.979> contending<04:09:56.580> for 04:09:57.530 --> 04:09:57.540 align:start position:0% network one in which it's contending for 04:09:57.540 --> 04:10:00.110 align:start position:0% network one in which it's contending for the<04:09:58.080> right<04:09:58.199> to<04:09:58.500> send<04:09:58.680> and<04:09:58.859> receive<04:09:59.160> data<04:09:59.580> so 04:10:00.110 --> 04:10:00.120 align:start position:0% the right to send and receive data so 04:10:00.120 --> 04:10:02.269 align:start position:0% the right to send and receive data so this<04:10:00.239> allows<04:10:00.660> all<04:10:00.899> nodes<04:10:01.260> to<04:10:01.439> have<04:10:01.620> relatively 04:10:02.269 --> 04:10:02.279 align:start position:0% this allows all nodes to have relatively 04:10:02.279 --> 04:10:04.849 align:start position:0% this allows all nodes to have relatively equal<04:10:02.640> access<04:10:03.060> to<04:10:03.540> the<04:10:03.660> media 04:10:04.849 --> 04:10:04.859 align:start position:0% equal access to the media 04:10:04.859 --> 04:10:08.269 align:start position:0% equal access to the media now<04:10:05.460> we<04:10:05.939> need<04:10:06.060> to<04:10:06.239> have<04:10:06.479> a<04:10:06.960> an<04:10:07.319> area<04:10:07.620> in<04:10:08.040> which 04:10:08.269 --> 04:10:08.279 align:start position:0% now we need to have a an area in which 04:10:08.279 --> 04:10:10.010 align:start position:0% now we need to have a an area in which all<04:10:08.640> of<04:10:08.760> these<04:10:08.939> are<04:10:09.060> going<04:10:09.239> to<04:10:09.359> contend<04:10:09.720> for 04:10:10.010 --> 04:10:10.020 align:start position:0% all of these are going to contend for 04:10:10.020 --> 04:10:13.010 align:start position:0% all of these are going to contend for Access<04:10:10.260> and<04:10:10.979> in<04:10:11.160> a<04:10:11.399> contention<04:10:11.760> domain<04:10:12.420> nodes 04:10:13.010 --> 04:10:13.020 align:start position:0% Access and in a contention domain nodes 04:10:13.020 --> 04:10:14.450 align:start position:0% Access and in a contention domain nodes on<04:10:13.199> the<04:10:13.319> network<04:10:13.439> are<04:10:13.739> allowed<04:10:14.040> to<04:10:14.160> compete 04:10:14.450 --> 04:10:14.460 align:start position:0% on the network are allowed to compete 04:10:14.460 --> 04:10:16.550 align:start position:0% on the network are allowed to compete with<04:10:14.580> each<04:10:14.760> other<04:10:14.880> for<04:10:15.239> media<04:10:15.600> access<04:10:15.720> and 04:10:16.550 --> 04:10:16.560 align:start position:0% with each other for media access and 04:10:16.560 --> 04:10:18.769 align:start position:0% with each other for media access and then<04:10:16.680> the<04:10:16.920> collisions<04:10:17.340> might<04:10:18.000> occur<04:10:18.359> as<04:10:18.600> a 04:10:18.769 --> 04:10:18.779 align:start position:0% then the collisions might occur as a 04:10:18.779 --> 04:10:20.929 align:start position:0% then the collisions might occur as a result<04:10:18.899> but<04:10:19.859> this<04:10:20.100> is<04:10:20.220> why<04:10:20.460> a<04:10:20.580> contention 04:10:20.929 --> 04:10:20.939 align:start position:0% result but this is why a contention 04:10:20.939 --> 04:10:22.910 align:start position:0% result but this is why a contention domain<04:10:21.420> is<04:10:21.660> also<04:10:21.960> considered<04:10:22.380> a<04:10:22.620> collision 04:10:22.910 --> 04:10:22.920 align:start position:0% domain is also considered a collision 04:10:22.920 --> 04:10:24.769 align:start position:0% domain is also considered a collision domain<04:10:23.399> because<04:10:23.760> this<04:10:24.120> is<04:10:24.239> where<04:10:24.420> these 04:10:24.769 --> 04:10:24.779 align:start position:0% domain because this is where these 04:10:24.779 --> 04:10:27.229 align:start position:0% domain because this is where these collisions<04:10:25.380> are<04:10:25.560> going<04:10:25.680> to<04:10:25.800> occur<04:10:26.160> now<04:10:26.880> in<04:10:27.060> a 04:10:27.229 --> 04:10:27.239 align:start position:0% collisions are going to occur now in a 04:10:27.239 --> 04:10:30.050 align:start position:0% collisions are going to occur now in a contention<04:10:27.540> domain<04:10:28.340> switches<04:10:29.340> control<04:10:29.640> the 04:10:30.050 --> 04:10:30.060 align:start position:0% contention domain switches control the 04:10:30.060 --> 04:10:32.330 align:start position:0% contention domain switches control the size<04:10:30.239> of<04:10:30.479> this<04:10:30.660> domain<04:10:31.080> and<04:10:31.800> in<04:10:31.979> larger 04:10:32.330 --> 04:10:32.340 align:start position:0% size of this domain and in larger 04:10:32.340 --> 04:10:34.429 align:start position:0% size of this domain and in larger networks<04:10:32.880> we<04:10:33.120> want<04:10:33.180> to<04:10:33.300> make<04:10:33.420> sure<04:10:33.600> to<04:10:33.779> vot<04:10:34.080> to 04:10:34.429 --> 04:10:34.439 align:start position:0% networks we want to make sure to vot to 04:10:34.439 --> 04:10:36.229 align:start position:0% networks we want to make sure to vot to divide<04:10:34.739> these<04:10:35.040> into<04:10:35.279> smaller<04:10:35.760> networks<04:10:36.120> so 04:10:36.229 --> 04:10:36.239 align:start position:0% divide these into smaller networks so 04:10:36.239 --> 04:10:37.670 align:start position:0% divide these into smaller networks so that<04:10:36.359> way<04:10:36.540> we're<04:10:36.660> not<04:10:36.779> having<04:10:36.960> to<04:10:37.140> contend 04:10:37.670 --> 04:10:37.680 align:start position:0% that way we're not having to contend 04:10:37.680 --> 04:10:41.450 align:start position:0% that way we're not having to contend with<04:10:38.220> as<04:10:38.399> many<04:10:38.640> devices<04:10:39.060> at<04:10:39.420> the<04:10:39.540> same<04:10:39.720> time 04:10:41.450 --> 04:10:41.460 align:start position:0% with as many devices at the same time 04:10:41.460 --> 04:10:42.830 align:start position:0% with as many devices at the same time so 04:10:42.830 --> 04:10:42.840 align:start position:0% so 04:10:42.840 --> 04:10:46.250 align:start position:0% so on<04:10:43.319> the<04:10:43.500> other<04:10:43.560> hand<04:10:43.859> a<04:10:44.819> broadcast<04:10:45.060> domain<04:10:45.720> is 04:10:46.250 --> 04:10:46.260 align:start position:0% on the other hand a broadcast domain is 04:10:46.260 --> 04:10:48.170 align:start position:0% on the other hand a broadcast domain is simply<04:10:46.500> a<04:10:46.800> logical<04:10:47.160> area<04:10:47.460> of<04:10:47.819> the<04:10:48.000> network 04:10:48.170 --> 04:10:48.180 align:start position:0% simply a logical area of the network 04:10:48.180 --> 04:10:50.269 align:start position:0% simply a logical area of the network where<04:10:48.840> all<04:10:49.080> the<04:10:49.199> nodes<04:10:49.380> can<04:10:49.620> communicate<04:10:50.040> with 04:10:50.269 --> 04:10:50.279 align:start position:0% where all the nodes can communicate with 04:10:50.279 --> 04:10:52.010 align:start position:0% where all the nodes can communicate with all<04:10:50.460> the<04:10:50.580> other<04:10:50.699> nodes<04:10:50.939> without<04:10:51.239> having<04:10:51.600> to<04:10:51.779> go 04:10:52.010 --> 04:10:52.020 align:start position:0% all the other nodes without having to go 04:10:52.020 --> 04:10:54.590 align:start position:0% all the other nodes without having to go through<04:10:52.319> a<04:10:52.620> centralized<04:10:53.040> device<04:10:53.399> because<04:10:54.359> of 04:10:54.590 --> 04:10:54.600 align:start position:0% through a centralized device because of 04:10:54.600 --> 04:10:56.210 align:start position:0% through a centralized device because of this<04:10:54.779> the<04:10:55.140> device<04:10:55.260> we're<04:10:55.560> going<04:10:55.680> to<04:10:55.800> use<04:10:55.920> is 04:10:56.210 --> 04:10:56.220 align:start position:0% this the device we're going to use is 04:10:56.220 --> 04:10:57.889 align:start position:0% this the device we're going to use is actually<04:10:56.460> a<04:10:56.939> router<04:10:57.359> which<04:10:57.540> is<04:10:57.660> going<04:10:57.779> to 04:10:57.889 --> 04:10:57.899 align:start position:0% actually a router which is going to 04:10:57.899 --> 04:10:59.570 align:start position:0% actually a router which is going to control<04:10:58.020> the<04:10:58.439> size<04:10:58.620> of<04:10:58.920> the<04:10:59.160> contention 04:10:59.570 --> 04:10:59.580 align:start position:0% control the size of the contention 04:10:59.580 --> 04:11:02.450 align:start position:0% control the size of the contention domain<04:11:00.060> in<04:11:00.479> a<04:11:00.660> broadcast<04:11:00.840> domain<04:11:01.500> now<04:11:02.160> the 04:11:02.450 --> 04:11:02.460 align:start position:0% domain in a broadcast domain now the 04:11:02.460 --> 04:11:04.910 align:start position:0% domain in a broadcast domain now the broadcast<04:11:02.640> domain<04:11:03.300> refers<04:11:03.720> to<04:11:04.080> the<04:11:04.439> set<04:11:04.620> of 04:11:04.910 --> 04:11:04.920 align:start position:0% broadcast domain refers to the set of 04:11:04.920 --> 04:11:06.830 align:start position:0% broadcast domain refers to the set of devices<04:11:05.460> that<04:11:06.120> are<04:11:06.239> going<04:11:06.359> to<04:11:06.479> receive 04:11:06.830 --> 04:11:06.840 align:start position:0% devices that are going to receive 04:11:06.840 --> 04:11:09.050 align:start position:0% devices that are going to receive broadcast<04:11:07.199> data<04:11:07.979> Transmissions<04:11:08.460> from<04:11:08.819> any 04:11:09.050 --> 04:11:09.060 align:start position:0% broadcast data Transmissions from any 04:11:09.060 --> 04:11:11.090 align:start position:0% broadcast data Transmissions from any node<04:11:09.359> on<04:11:09.899> that<04:11:10.140> portion<04:11:10.560> of<04:11:10.800> the<04:11:10.920> network 04:11:11.090 --> 04:11:11.100 align:start position:0% node on that portion of the network 04:11:11.100 --> 04:11:12.670 align:start position:0% node on that portion of the network which<04:11:11.460> is<04:11:11.580> also<04:11:11.880> called<04:11:12.060> a<04:11:12.300> segment 04:11:12.670 --> 04:11:12.680 align:start position:0% which is also called a segment 04:11:12.680 --> 04:11:16.010 align:start position:0% which is also called a segment essentially<04:11:13.680> if<04:11:14.279> a<04:11:14.399> node<04:11:14.640> were<04:11:14.819> to<04:11:15.000> transmit<04:11:15.600> a 04:11:16.010 --> 04:11:16.020 align:start position:0% essentially if a node were to transmit a 04:11:16.020 --> 04:11:18.590 align:start position:0% essentially if a node were to transmit a broadcast<04:11:16.319> message<04:11:17.040> the<04:11:17.760> broadcast<04:11:17.939> domain 04:11:18.590 --> 04:11:18.600 align:start position:0% broadcast message the broadcast domain 04:11:18.600 --> 04:11:20.450 align:start position:0% broadcast message the broadcast domain dictates<04:11:19.140> where<04:11:19.620> the<04:11:19.800> message<04:11:19.920> is<04:11:20.160> going<04:11:20.340> to 04:11:20.450 --> 04:11:20.460 align:start position:0% dictates where the message is going to 04:11:20.460 --> 04:11:21.170 align:start position:0% dictates where the message is going to go 04:11:21.170 --> 04:11:21.180 align:start position:0% go 04:11:21.180 --> 04:11:24.349 align:start position:0% go now<04:11:21.720> in<04:11:21.960> a<04:11:22.140> contention<04:11:22.439> domain<04:11:23.040> if<04:11:23.939> a 04:11:24.349 --> 04:11:24.359 align:start position:0% now in a contention domain if a 04:11:24.359 --> 04:11:26.630 align:start position:0% now in a contention domain if a broadcast<04:11:24.600> message<04:11:25.199> were<04:11:25.560> to<04:11:25.739> be<04:11:25.920> transmitted 04:11:26.630 --> 04:11:26.640 align:start position:0% broadcast message were to be transmitted 04:11:26.640 --> 04:11:28.250 align:start position:0% broadcast message were to be transmitted there's<04:11:27.060> going<04:11:27.239> to<04:11:27.239> be<04:11:27.359> a<04:11:27.600> greater<04:11:27.899> number<04:11:28.080> of 04:11:28.250 --> 04:11:28.260 align:start position:0% there's going to be a greater number of 04:11:28.260 --> 04:11:31.010 align:start position:0% there's going to be a greater number of collisions<04:11:28.920> as<04:11:29.580> a<04:11:29.819> result<04:11:30.060> of<04:11:30.600> the<04:11:30.779> traffic 04:11:31.010 --> 04:11:31.020 align:start position:0% collisions as a result of the traffic 04:11:31.020 --> 04:11:33.889 align:start position:0% collisions as a result of the traffic you<04:11:31.800> can<04:11:31.920> have<04:11:32.040> multiple<04:11:32.580> contention<04:11:33.120> domains 04:11:33.889 --> 04:11:33.899 align:start position:0% you can have multiple contention domains 04:11:33.899 --> 04:11:37.370 align:start position:0% you can have multiple contention domains that<04:11:34.500> make<04:11:34.800> up<04:11:35.420> broadcasts<04:11:36.420> that<04:11:36.720> make<04:11:36.960> up<04:11:37.140> a 04:11:37.370 --> 04:11:37.380 align:start position:0% that make up broadcasts that make up a 04:11:37.380 --> 04:11:40.130 align:start position:0% that make up broadcasts that make up a broadcast<04:11:37.500> domain<04:11:38.279> so<04:11:38.880> I<04:11:39.060> can<04:11:39.180> have<04:11:39.479> again 04:11:40.130 --> 04:11:40.140 align:start position:0% broadcast domain so I can have again 04:11:40.140 --> 04:11:42.410 align:start position:0% broadcast domain so I can have again divided<04:11:40.800> by<04:11:40.979> switches<04:11:41.520> two<04:11:42.180> different 04:11:42.410 --> 04:11:42.420 align:start position:0% divided by switches two different 04:11:42.420 --> 04:11:47.510 align:start position:0% divided by switches two different contention<04:11:43.199> domains 04:11:47.510 --> 04:11:47.520 align:start position:0% 04:11:47.520 --> 04:11:50.210 align:start position:0% and<04:11:48.060> multiple<04:11:48.420> ones<04:11:48.779> of<04:11:48.899> these<04:11:49.080> can<04:11:49.319> make<04:11:49.560> up<04:11:49.739> a 04:11:50.210 --> 04:11:50.220 align:start position:0% and multiple ones of these can make up a 04:11:50.220 --> 04:11:55.309 align:start position:0% and multiple ones of these can make up a larger<04:11:50.580> broadcast<04:11:51.479> domain<04:11:52.380> and 04:11:55.309 --> 04:11:55.319 align:start position:0% larger broadcast domain and 04:11:55.319 --> 04:11:57.650 align:start position:0% larger broadcast domain and because<04:11:55.979> these<04:11:56.460> switches<04:11:56.819> are<04:11:57.120> all<04:11:57.300> connected 04:11:57.650 --> 04:11:57.660 align:start position:0% because these switches are all connected 04:11:57.660 --> 04:12:00.410 align:start position:0% because these switches are all connected by<04:11:58.080> one<04:11:58.380> Central<04:11:58.620> router<04:11:59.220> when<04:11:59.939> one<04:12:00.180> of<04:12:00.300> the 04:12:00.410 --> 04:12:00.420 align:start position:0% by one Central router when one of the 04:12:00.420 --> 04:12:02.090 align:start position:0% by one Central router when one of the nodes<04:12:00.660> branching<04:12:01.319> off<04:12:01.500> of<04:12:01.680> one<04:12:01.859> of<04:12:01.979> the 04:12:02.090 --> 04:12:02.100 align:start position:0% nodes branching off of one of the 04:12:02.100 --> 04:12:05.809 align:start position:0% nodes branching off of one of the switches<04:12:02.460> sends<04:12:03.420> a<04:12:03.600> broadcast<04:12:03.840> message 04:12:05.809 --> 04:12:05.819 align:start position:0% switches sends a broadcast message 04:12:05.819 --> 04:12:08.150 align:start position:0% switches sends a broadcast message the<04:12:06.420> router<04:12:06.779> dictates<04:12:07.199> that<04:12:07.620> only<04:12:07.859> the 04:12:08.150 --> 04:12:08.160 align:start position:0% the router dictates that only the 04:12:08.160 --> 04:12:09.950 align:start position:0% the router dictates that only the connected<04:12:08.520> switch<04:12:08.760> and<04:12:09.120> its<04:12:09.420> devices<04:12:09.660> are 04:12:09.950 --> 04:12:09.960 align:start position:0% connected switch and its devices are 04:12:09.960 --> 04:12:11.269 align:start position:0% connected switch and its devices are going<04:12:10.080> to<04:12:10.260> receive<04:12:10.620> that<04:12:10.979> broadcast 04:12:11.269 --> 04:12:11.279 align:start position:0% going to receive that broadcast 04:12:11.279 --> 04:12:13.250 align:start position:0% going to receive that broadcast transmission 04:12:13.250 --> 04:12:13.260 align:start position:0% transmission 04:12:13.260 --> 04:12:16.490 align:start position:0% transmission so<04:12:13.739> we<04:12:14.100> first<04:12:14.460> talked<04:12:14.939> about<04:12:15.060> defining<04:12:16.020> media 04:12:16.490 --> 04:12:16.500 align:start position:0% so we first talked about defining media 04:12:16.500 --> 04:12:19.729 align:start position:0% so we first talked about defining media access<04:12:17.120> basically<04:12:18.120> the<04:12:18.899> rules<04:12:19.199> by<04:12:19.439> which 04:12:19.729 --> 04:12:19.739 align:start position:0% access basically the rules by which 04:12:19.739 --> 04:12:22.610 align:start position:0% access basically the rules by which devices<04:12:20.340> are<04:12:20.760> allowed<04:12:21.120> to<04:12:21.420> communicate<04:12:22.020> on 04:12:22.610 --> 04:12:22.620 align:start position:0% devices are allowed to communicate on 04:12:22.620 --> 04:12:24.889 align:start position:0% devices are allowed to communicate on the<04:12:22.739> network<04:12:22.920> we<04:12:23.819> then<04:12:24.000> looked<04:12:24.300> at<04:12:24.359> the<04:12:24.600> two 04:12:24.889 --> 04:12:24.899 align:start position:0% the network we then looked at the two 04:12:24.899 --> 04:12:28.189 align:start position:0% the network we then looked at the two broad<04:12:25.260> categories<04:12:26.220> of<04:12:27.000> access<04:12:27.359> or<04:12:27.840> media 04:12:28.189 --> 04:12:28.199 align:start position:0% broad categories of access or media 04:12:28.199 --> 04:12:29.889 align:start position:0% broad categories of access or media access<04:12:28.380> that<04:12:28.859> we<04:12:28.979> deal<04:12:29.100> with 04:12:29.889 --> 04:12:29.899 align:start position:0% access that we deal with 04:12:29.899 --> 04:12:31.790 align:start position:0% access that we deal with contention-based<04:12:30.899> media<04:12:31.199> access<04:12:31.319> meaning 04:12:31.790 --> 04:12:31.800 align:start position:0% contention-based media access meaning 04:12:31.800 --> 04:12:35.450 align:start position:0% contention-based media access meaning we're<04:12:32.160> basically<04:12:32.640> fighting 04:12:35.450 --> 04:12:35.460 align:start position:0% we're basically fighting 04:12:35.460 --> 04:12:39.650 align:start position:0% we're basically fighting for<04:12:36.300> the<04:12:36.540> right<04:12:36.779> to<04:12:37.560> access<04:12:37.859> the<04:12:38.399> media<04:12:39.000> or 04:12:39.650 --> 04:12:39.660 align:start position:0% for the right to access the media or 04:12:39.660 --> 04:12:42.229 align:start position:0% for the right to access the media or controlled<04:12:40.260> media<04:12:40.620> access<04:12:40.800> in<04:12:41.520> which<04:12:41.699> we<04:12:42.000> have 04:12:42.229 --> 04:12:42.239 align:start position:0% controlled media access in which we have 04:12:42.239 --> 04:12:45.650 align:start position:0% controlled media access in which we have a<04:12:42.600> central<04:12:42.779> device<04:12:43.260> that<04:12:44.100> decides<04:12:44.580> for<04:12:44.819> us 04:12:45.650 --> 04:12:45.660 align:start position:0% a central device that decides for us 04:12:45.660 --> 04:12:47.929 align:start position:0% a central device that decides for us we<04:12:46.199> looked<04:12:46.500> at<04:12:46.560> then<04:12:46.920> a<04:12:47.520> couple<04:12:47.640> different 04:12:47.929 --> 04:12:47.939 align:start position:0% we looked at then a couple different 04:12:47.939 --> 04:12:51.830 align:start position:0% we looked at then a couple different types<04:12:48.540> of<04:12:48.840> controlled<04:12:49.800> media<04:12:50.279> access<04:12:50.840> these 04:12:51.830 --> 04:12:51.840 align:start position:0% types of controlled media access these 04:12:51.840 --> 04:12:55.689 align:start position:0% types of controlled media access these are<04:12:51.960> all<04:12:52.199> controlled<04:12:52.859> media<04:12:53.220> access<04:12:53.340> types 04:12:55.689 --> 04:12:55.699 align:start position:0% are all controlled media access types 04:12:55.699 --> 04:12:58.790 align:start position:0% are all controlled media access types multiplexing<04:12:56.699> which<04:12:57.479> allows<04:12:58.080> us<04:12:58.260> to<04:12:58.620> send 04:12:58.790 --> 04:12:58.800 align:start position:0% multiplexing which allows us to send 04:12:58.800 --> 04:13:01.250 align:start position:0% multiplexing which allows us to send multiple<04:12:59.279> signals<04:12:59.760> over<04:12:59.880> one<04:13:00.180> media<04:13:00.660> and<04:13:01.140> we 04:13:01.250 --> 04:13:01.260 align:start position:0% multiple signals over one media and we 04:13:01.260 --> 04:13:04.910 align:start position:0% multiple signals over one media and we looked<04:13:01.560> at<04:13:01.680> TDM<04:13:02.640> or<04:13:03.420> time<04:13:04.020> division<04:13:04.560> which 04:13:04.910 --> 04:13:04.920 align:start position:0% looked at TDM or time division which 04:13:04.920 --> 04:13:06.830 align:start position:0% looked at TDM or time division which divides<04:13:05.340> It<04:13:05.399> Up<04:13:05.520> by<04:13:05.760> time<04:13:05.939> and<04:13:06.300> remember<04:13:06.420> this 04:13:06.830 --> 04:13:06.840 align:start position:0% divides It Up by time and remember this 04:13:06.840 --> 04:13:09.769 align:start position:0% divides It Up by time and remember this is<04:13:07.020> for<04:13:07.380> digital<04:13:08.160> signals<04:13:08.760> and<04:13:09.479> then<04:13:09.600> we 04:13:09.769 --> 04:13:09.779 align:start position:0% is for digital signals and then we 04:13:09.779 --> 04:13:14.269 align:start position:0% is for digital signals and then we looked<04:13:10.080> at<04:13:10.199> frequency 04:13:14.269 --> 04:13:14.279 align:start position:0% 04:13:14.279 --> 04:13:17.809 align:start position:0% division<04:13:15.060> which<04:13:15.779> allows<04:13:16.260> us<04:13:16.380> to<04:13:16.680> use<04:13:16.920> analog 04:13:17.809 --> 04:13:17.819 align:start position:0% division which allows us to use analog 04:13:17.819 --> 04:13:20.630 align:start position:0% division which allows us to use analog signals<04:13:18.420> or<04:13:18.899> Multiplex<04:13:19.500> analog<04:13:20.220> signals 04:13:20.630 --> 04:13:20.640 align:start position:0% signals or Multiplex analog signals 04:13:20.640 --> 04:13:24.050 align:start position:0% signals or Multiplex analog signals remember<04:13:21.239> both<04:13:21.840> of<04:13:22.020> these<04:13:22.319> use<04:13:22.859> a<04:13:23.160> device<04:13:23.279> a 04:13:24.050 --> 04:13:24.060 align:start position:0% remember both of these use a device a 04:13:24.060 --> 04:13:26.750 align:start position:0% remember both of these use a device a controlling<04:13:24.540> device<04:13:24.779> called<04:13:25.380> a<04:13:25.800> Mox 04:13:26.750 --> 04:13:26.760 align:start position:0% controlling device called a Mox 04:13:26.760 --> 04:13:30.590 align:start position:0% controlling device called a Mox or<04:13:27.180> a<04:13:27.359> multiplexer<04:13:28.080> and<04:13:28.800> a<04:13:29.100> d-mox<04:13:29.640> or<04:13:30.000> D 04:13:30.590 --> 04:13:30.600 align:start position:0% or a multiplexer and a d-mox or D 04:13:30.600 --> 04:13:32.269 align:start position:0% or a multiplexer and a d-mox or D multiplexer 04:13:32.269 --> 04:13:32.279 align:start position:0% multiplexer 04:13:32.279 --> 04:13:35.210 align:start position:0% multiplexer we<04:13:32.819> also<04:13:33.120> described<04:13:33.660> polling<04:13:34.319> in<04:13:34.739> which<04:13:34.859> we 04:13:35.210 --> 04:13:35.220 align:start position:0% we also described polling in which we 04:13:35.220 --> 04:13:37.550 align:start position:0% we also described polling in which we ask<04:13:35.460> are<04:13:35.699> there<04:13:35.819> any<04:13:36.000> devices<04:13:36.479> on<04:13:37.260> this 04:13:37.550 --> 04:13:37.560 align:start position:0% ask are there any devices on this 04:13:37.560 --> 04:13:40.010 align:start position:0% ask are there any devices on this network<04:13:37.739> that<04:13:38.220> want<04:13:38.460> to<04:13:38.580> send<04:13:38.819> data<04:13:39.300> but<04:13:39.779> we 04:13:40.010 --> 04:13:40.020 align:start position:0% network that want to send data but we 04:13:40.020 --> 04:13:41.689 align:start position:0% network that want to send data but we talked<04:13:40.319> about<04:13:40.439> the<04:13:40.800> fact<04:13:40.920> that<04:13:41.220> this<04:13:41.460> can 04:13:41.689 --> 04:13:41.699 align:start position:0% talked about the fact that this can 04:13:41.699 --> 04:13:44.630 align:start position:0% talked about the fact that this can actually<04:13:42.000> add<04:13:42.540> more<04:13:43.260> time<04:13:43.560> to<04:13:44.100> the<04:13:44.279> process 04:13:44.630 --> 04:13:44.640 align:start position:0% actually add more time to the process 04:13:44.640 --> 04:13:47.030 align:start position:0% actually add more time to the process since<04:13:45.060> I<04:13:45.300> have<04:13:45.420> to<04:13:45.600> ask<04:13:45.899> every<04:13:46.319> device<04:13:46.560> before 04:13:47.030 --> 04:13:47.040 align:start position:0% since I have to ask every device before 04:13:47.040 --> 04:13:48.710 align:start position:0% since I have to ask every device before I<04:13:47.279> get<04:13:47.399> back<04:13:47.580> to<04:13:47.699> the<04:13:47.760> device<04:13:47.939> that's<04:13:48.239> ready<04:13:48.479> to 04:13:48.710 --> 04:13:48.720 align:start position:0% I get back to the device that's ready to 04:13:48.720 --> 04:13:49.429 align:start position:0% I get back to the device that's ready to send 04:13:49.429 --> 04:13:49.439 align:start position:0% send 04:13:49.439 --> 04:13:52.030 align:start position:0% send we<04:13:50.040> then<04:13:50.220> looked<04:13:50.640> at<04:13:51.180> two 04:13:52.030 --> 04:13:52.040 align:start position:0% we then looked at two 04:13:52.040 --> 04:13:59.689 align:start position:0% we then looked at two contention<04:13:53.120> based<04:13:54.120> media<04:13:54.479> access<04:13:54.660> methods 04:13:59.689 --> 04:13:59.699 align:start position:0% 04:13:59.699 --> 04:14:03.189 align:start position:0% carrier<04:14:00.540> sense<04:14:00.960> multiple<04:14:01.859> access<04:14:02.120> Collision 04:14:03.189 --> 04:14:03.199 align:start position:0% carrier sense multiple access Collision 04:14:03.199 --> 04:14:07.070 align:start position:0% carrier sense multiple access Collision detection<04:14:04.220> and<04:14:05.220> collision<04:14:05.640> avoidance<04:14:06.479> and 04:14:07.070 --> 04:14:07.080 align:start position:0% detection and collision avoidance and 04:14:07.080 --> 04:14:08.330 align:start position:0% detection and collision avoidance and remember<04:14:07.199> the<04:14:07.620> important<04:14:07.920> thing<04:14:08.040> to<04:14:08.220> know 04:14:08.330 --> 04:14:08.340 align:start position:0% remember the important thing to know 04:14:08.340 --> 04:14:11.510 align:start position:0% remember the important thing to know here<04:14:08.580> is<04:14:08.760> Collision<04:14:09.180> detection<04:14:09.960> simply<04:14:10.920> has<04:14:11.279> a 04:14:11.510 --> 04:14:11.520 align:start position:0% here is Collision detection simply has a 04:14:11.520 --> 04:14:14.150 align:start position:0% here is Collision detection simply has a collision<04:14:12.239> occurs<04:14:12.840> and<04:14:13.439> then<04:14:13.560> I<04:14:13.800> just<04:14:13.979> wait 04:14:14.150 --> 04:14:14.160 align:start position:0% collision occurs and then I just wait 04:14:14.160 --> 04:14:16.729 align:start position:0% collision occurs and then I just wait and<04:14:14.399> I<04:14:14.580> try<04:14:14.760> sending<04:14:15.239> again<04:14:15.420> and<04:14:16.080> this<04:14:16.260> is<04:14:16.439> what 04:14:16.729 --> 04:14:16.739 align:start position:0% and I try sending again and this is what 04:14:16.739 --> 04:14:19.309 align:start position:0% and I try sending again and this is what ethernet<04:14:17.399> really<04:14:17.760> is<04:14:18.000> going<04:14:18.180> to<04:14:18.359> use<04:14:18.600> as 04:14:19.309 --> 04:14:19.319 align:start position:0% ethernet really is going to use as 04:14:19.319 --> 04:14:23.990 align:start position:0% ethernet really is going to use as opposed<04:14:19.620> to<04:14:19.680> collision<04:14:20.340> avoidance 04:14:23.990 --> 04:14:24.000 align:start position:0% 04:14:24.000 --> 04:14:27.290 align:start position:0% which<04:14:24.600> is<04:14:24.779> going<04:14:24.960> to<04:14:25.080> be<04:14:25.199> used<04:14:25.439> mostly 04:14:27.290 --> 04:14:27.300 align:start position:0% which is going to be used mostly 04:14:27.300 --> 04:14:30.229 align:start position:0% which is going to be used mostly in<04:14:28.080> Wireless<04:14:28.260> situations<04:14:29.040> because<04:14:29.760> I<04:14:30.120> send 04:14:30.229 --> 04:14:30.239 align:start position:0% in Wireless situations because I send 04:14:30.239 --> 04:14:34.490 align:start position:0% in Wireless situations because I send out<04:14:30.420> a<04:14:30.720> jamming<04:14:31.140> signal<04:14:31.500> first 04:14:34.490 --> 04:14:34.500 align:start position:0% 04:14:34.500 --> 04:14:36.189 align:start position:0% we<04:14:34.920> then<04:14:35.040> looked<04:14:35.340> at<04:14:35.460> the<04:14:35.580> difference<04:14:35.699> in<04:14:36.000> a 04:14:36.189 --> 04:14:36.199 align:start position:0% we then looked at the difference in a 04:14:36.199 --> 04:14:38.570 align:start position:0% we then looked at the difference in a contention-based<04:14:37.199> domain 04:14:38.570 --> 04:14:38.580 align:start position:0% contention-based domain 04:14:38.580 --> 04:14:41.150 align:start position:0% contention-based domain or<04:14:39.120> where<04:14:39.420> we're<04:14:39.660> contending<04:14:40.140> for<04:14:40.319> Access<04:14:40.560> and 04:14:41.150 --> 04:14:41.160 align:start position:0% or where we're contending for Access and 04:14:41.160 --> 04:14:43.130 align:start position:0% or where we're contending for Access and remember<04:14:41.340> that's<04:14:41.699> defined<04:14:42.300> by<04:14:42.720> a<04:14:42.899> switch 04:14:43.130 --> 04:14:43.140 align:start position:0% remember that's defined by a switch 04:14:43.140 --> 04:14:46.250 align:start position:0% remember that's defined by a switch because<04:14:43.979> a<04:14:44.460> switch<04:14:44.640> uh<04:14:45.420> everything<04:14:45.660> connected 04:14:46.250 --> 04:14:46.260 align:start position:0% because a switch uh everything connected 04:14:46.260 --> 04:14:48.290 align:start position:0% because a switch uh everything connected to<04:14:46.439> the<04:14:46.560> switch<04:14:46.739> can<04:14:47.160> contend<04:14:47.520> for<04:14:47.819> Access<04:14:48.000> and 04:14:48.290 --> 04:14:48.300 align:start position:0% to the switch can contend for Access and 04:14:48.300 --> 04:14:50.210 align:start position:0% to the switch can contend for Access and can<04:14:48.479> have<04:14:48.660> a<04:14:48.779> collision<04:14:49.080> and<04:14:49.800> a<04:14:50.040> broadcast 04:14:50.210 --> 04:14:50.220 align:start position:0% can have a collision and a broadcast 04:14:50.220 --> 04:14:52.189 align:start position:0% can have a collision and a broadcast domain<04:14:50.880> which<04:14:51.420> is 04:14:52.189 --> 04:14:52.199 align:start position:0% domain which is 04:14:52.199 --> 04:14:54.950 align:start position:0% domain which is created<04:14:52.859> by<04:14:53.100> the<04:14:53.279> router<04:14:53.699> and<04:14:54.300> is<04:14:54.420> simply<04:14:54.720> a 04:14:54.950 --> 04:14:54.960 align:start position:0% created by the router and is simply a 04:14:54.960 --> 04:14:57.410 align:start position:0% created by the router and is simply a logical<04:14:55.260> division<04:14:55.680> of<04:14:56.040> all<04:14:56.220> the<04:14:56.399> devices<04:14:56.699> that 04:14:57.410 --> 04:14:57.420 align:start position:0% logical division of all the devices that 04:14:57.420 --> 04:15:04.420 align:start position:0% logical division of all the devices that uh<04:14:58.080> one<04:14:58.859> device<04:14:59.220> can<04:14:59.760> contact 04:15:04.420 --> 04:15:04.430 align:start position:0% 04:15:04.430 --> 04:15:13.330 align:start position:0% [Music] 04:15:13.330 --> 04:15:13.340 align:start position:0% 04:15:13.340 --> 04:15:24.170 align:start position:0% thank<04:15:14.340> you 04:15:24.170 --> 04:15:24.180 align:start position:0% 04:15:24.180 --> 04:15:29.510 align:start position:0% network<04:15:24.960> communications<04:15:26.300> signaling<04:15:27.300> methods 04:15:29.510 --> 04:15:29.520 align:start position:0% network communications signaling methods 04:15:29.520 --> 04:15:33.550 align:start position:0% network communications signaling methods we've<04:15:30.000> talked<04:15:30.359> about<04:15:30.620> digital<04:15:31.640> and<04:15:32.640> analog 04:15:33.550 --> 04:15:33.560 align:start position:0% we've talked about digital and analog 04:15:33.560 --> 04:15:35.990 align:start position:0% we've talked about digital and analog signaling<04:15:34.560> quite<04:15:34.979> a<04:15:35.160> bit<04:15:35.279> but<04:15:35.760> we<04:15:35.880> haven't 04:15:35.990 --> 04:15:36.000 align:start position:0% signaling quite a bit but we haven't 04:15:36.000 --> 04:15:38.210 align:start position:0% signaling quite a bit but we haven't really<04:15:36.239> gone<04:15:36.540> into<04:15:36.779> what<04:15:37.140> that<04:15:37.380> exactly<04:15:37.800> means 04:15:38.210 --> 04:15:38.220 align:start position:0% really gone into what that exactly means 04:15:38.220 --> 04:15:42.290 align:start position:0% really gone into what that exactly means at<04:15:38.819> a<04:15:39.000> waveform<04:15:39.420> level<04:15:39.779> at<04:15:40.319> a<04:15:40.620> basic<04:15:41.220> level<04:15:41.460> and 04:15:42.290 --> 04:15:42.300 align:start position:0% at a waveform level at a basic level and 04:15:42.300 --> 04:15:44.210 align:start position:0% at a waveform level at a basic level and so<04:15:42.479> in<04:15:42.779> this<04:15:42.960> module<04:15:43.319> I<04:15:43.560> want<04:15:43.620> to<04:15:43.739> cover<04:15:43.920> some 04:15:44.210 --> 04:15:44.220 align:start position:0% so in this module I want to cover some 04:15:44.220 --> 04:15:45.769 align:start position:0% so in this module I want to cover some of<04:15:44.399> the<04:15:44.460> background<04:15:44.819> information<04:15:45.180> about 04:15:45.769 --> 04:15:45.779 align:start position:0% of the background information about 04:15:45.779 --> 04:15:48.170 align:start position:0% of the background information about these<04:15:46.199> and<04:15:46.800> outline<04:15:47.100> some<04:15:47.340> of<04:15:47.460> the<04:15:47.580> attributes 04:15:48.170 --> 04:15:48.180 align:start position:0% these and outline some of the attributes 04:15:48.180 --> 04:15:49.729 align:start position:0% these and outline some of the attributes that<04:15:48.359> go<04:15:48.540> along<04:15:48.660> with<04:15:48.899> them 04:15:49.729 --> 04:15:49.739 align:start position:0% that go along with them 04:15:49.739 --> 04:15:51.650 align:start position:0% that go along with them now<04:15:50.340> this<04:15:50.580> information<04:15:50.760> might<04:15:51.420> not 04:15:51.650 --> 04:15:51.660 align:start position:0% now this information might not 04:15:51.660 --> 04:15:54.889 align:start position:0% now this information might not specifically<04:15:52.319> be<04:15:52.739> on<04:15:53.460> the<04:15:53.580> exam<04:15:53.939> but<04:15:54.540> I<04:15:54.779> think 04:15:54.889 --> 04:15:54.899 align:start position:0% specifically be on the exam but I think 04:15:54.899 --> 04:15:56.090 align:start position:0% specifically be on the exam but I think it's<04:15:55.020> still<04:15:55.260> good<04:15:55.439> background<04:15:55.800> information 04:15:56.090 --> 04:15:56.100 align:start position:0% it's still good background information 04:15:56.100 --> 04:15:58.189 align:start position:0% it's still good background information to<04:15:56.580> understand<04:15:56.699> anyway 04:15:58.189 --> 04:15:58.199 align:start position:0% to understand anyway 04:15:58.199 --> 04:16:00.830 align:start position:0% to understand anyway so<04:15:58.800> uh<04:15:59.160> in<04:15:59.340> this<04:15:59.580> module<04:16:00.000> we're<04:16:00.479> first<04:16:00.660> going 04:16:00.830 --> 04:16:00.840 align:start position:0% so uh in this module we're first going 04:16:00.840 --> 04:16:03.710 align:start position:0% so uh in this module we're first going to<04:16:01.020> Define<04:16:01.199> what<04:16:02.160> a<04:16:02.279> signal<04:16:02.580> is<04:16:02.760> and<04:16:03.479> what 04:16:03.710 --> 04:16:03.720 align:start position:0% to Define what a signal is and what 04:16:03.720 --> 04:16:05.269 align:start position:0% to Define what a signal is and what analog<04:16:04.319> is 04:16:05.269 --> 04:16:05.279 align:start position:0% analog is 04:16:05.279 --> 04:16:07.189 align:start position:0% analog is we're<04:16:05.640> then<04:16:05.760> going<04:16:06.000> to<04:16:06.060> talk<04:16:06.359> about<04:16:06.720> the 04:16:07.189 --> 04:16:07.199 align:start position:0% we're then going to talk about the 04:16:07.199 --> 04:16:11.630 align:start position:0% we're then going to talk about the attributes<04:16:07.739> of<04:16:08.399> an<04:16:08.699> analog<04:16:09.239> signal 04:16:11.630 --> 04:16:11.640 align:start position:0% attributes of an analog signal 04:16:11.640 --> 04:16:14.510 align:start position:0% attributes of an analog signal well<04:16:12.060> then<04:16:12.300> take<04:16:12.960> this<04:16:13.199> and<04:16:13.439> talk<04:16:13.680> about<04:16:13.859> a 04:16:14.510 --> 04:16:14.520 align:start position:0% well then take this and talk about a 04:16:14.520 --> 04:16:17.929 align:start position:0% well then take this and talk about a digital<04:16:14.819> signal<04:16:15.239> different<04:16:15.899> from<04:16:16.380> analog<04:16:16.979> and 04:16:17.929 --> 04:16:17.939 align:start position:0% digital signal different from analog and 04:16:17.939 --> 04:16:20.630 align:start position:0% digital signal different from analog and a<04:16:18.239> digital<04:16:18.479> data<04:16:18.960> transmission<04:16:19.140> or<04:16:20.100> how<04:16:20.340> this 04:16:20.630 --> 04:16:20.640 align:start position:0% a digital data transmission or how this 04:16:20.640 --> 04:16:22.910 align:start position:0% a digital data transmission or how this digital<04:16:20.939> Signa<04:16:21.420> is<04:16:21.600> transmitted 04:16:22.910 --> 04:16:22.920 align:start position:0% digital Signa is transmitted 04:16:22.920 --> 04:16:25.910 align:start position:0% digital Signa is transmitted we're<04:16:23.399> also<04:16:23.640> going<04:16:23.760> to<04:16:23.880> Define<04:16:24.060> modulation 04:16:25.910 --> 04:16:25.920 align:start position:0% we're also going to Define modulation 04:16:25.920 --> 04:16:29.330 align:start position:0% we're also going to Define modulation and<04:16:26.640> outline<04:16:27.060> the<04:16:27.720> Way<04:16:27.840> digital<04:16:28.319> signals<04:16:28.920> are 04:16:29.330 --> 04:16:29.340 align:start position:0% and outline the Way digital signals are 04:16:29.340 --> 04:16:31.969 align:start position:0% and outline the Way digital signals are modulated<04:16:29.939> and<04:16:30.540> modulation<04:16:31.080> really<04:16:31.500> has<04:16:31.800> to 04:16:31.969 --> 04:16:31.979 align:start position:0% modulated and modulation really has to 04:16:31.979 --> 04:16:35.330 align:start position:0% modulated and modulation really has to do<04:16:32.160> with<04:16:32.520> uh<04:16:33.300> length<04:16:33.899> or<04:16:34.319> making<04:16:34.620> sure<04:16:34.920> that<04:16:35.220> a 04:16:35.330 --> 04:16:35.340 align:start position:0% do with uh length or making sure that a 04:16:35.340 --> 04:16:39.229 align:start position:0% do with uh length or making sure that a signal<04:16:35.699> can<04:16:36.479> be<04:16:36.720> broadcast<04:16:37.100> or<04:16:38.100> sent<04:16:38.460> over<04:16:38.880> a 04:16:39.229 --> 04:16:39.239 align:start position:0% signal can be broadcast or sent over a 04:16:39.239 --> 04:16:41.269 align:start position:0% signal can be broadcast or sent over a very<04:16:39.420> long<04:16:39.840> or<04:16:40.260> large 04:16:41.269 --> 04:16:41.279 align:start position:0% very long or large 04:16:41.279 --> 04:16:42.590 align:start position:0% very long or large area 04:16:42.590 --> 04:16:42.600 align:start position:0% area 04:16:42.600 --> 04:16:44.750 align:start position:0% area or<04:16:43.020> distance 04:16:44.750 --> 04:16:44.760 align:start position:0% or distance 04:16:44.760 --> 04:16:47.030 align:start position:0% or distance finally<04:16:45.359> we'll<04:16:45.779> look<04:16:46.080> at<04:16:46.199> Digital<04:16:46.560> Signal 04:16:47.030 --> 04:16:47.040 align:start position:0% finally we'll look at Digital Signal 04:16:47.040 --> 04:16:50.450 align:start position:0% finally we'll look at Digital Signal reference<04:16:47.819> methods<04:16:48.660> how<04:16:49.260> we<04:16:49.500> know<04:16:49.739> when<04:16:50.220> the 04:16:50.450 --> 04:16:50.460 align:start position:0% reference methods how we know when the 04:16:50.460 --> 04:16:53.030 align:start position:0% reference methods how we know when the message<04:16:50.699> begins<04:16:51.300> and<04:16:51.479> when<04:16:51.660> it<04:16:51.840> ends<04:16:52.199> and 04:16:53.030 --> 04:16:53.040 align:start position:0% message begins and when it ends and 04:16:53.040 --> 04:16:55.490 align:start position:0% message begins and when it ends and finally<04:16:53.340> wind<04:16:54.300> up<04:16:54.540> talking<04:16:54.840> about<04:16:55.080> Digital 04:16:55.490 --> 04:16:55.500 align:start position:0% finally wind up talking about Digital 04:16:55.500 --> 04:16:58.010 align:start position:0% finally wind up talking about Digital Data<04:16:55.979> units<04:16:56.460> or<04:16:56.819> the<04:16:56.939> unit<04:16:57.120> of<04:16:57.359> measurements 04:16:58.010 --> 04:16:58.020 align:start position:0% Data units or the unit of measurements 04:16:58.020 --> 04:16:59.809 align:start position:0% Data units or the unit of measurements that<04:16:58.260> we<04:16:58.439> hear<04:16:58.620> often<04:16:59.040> when<04:16:59.220> we're<04:16:59.399> referring 04:16:59.809 --> 04:16:59.819 align:start position:0% that we hear often when we're referring 04:16:59.819 --> 04:17:02.389 align:start position:0% that we hear often when we're referring to<04:17:00.239> Digital<04:17:00.600> Data<04:17:01.080> such<04:17:01.439> as<04:17:01.560> kilobytes<04:17:02.220> and 04:17:02.389 --> 04:17:02.399 align:start position:0% to Digital Data such as kilobytes and 04:17:02.399 --> 04:17:06.229 align:start position:0% to Digital Data such as kilobytes and megabytes<04:17:03.359> so<04:17:03.899> at<04:17:04.140> its<04:17:04.439> most<04:17:04.560> basic<04:17:05.040> level<04:17:05.239> a 04:17:06.229 --> 04:17:06.239 align:start position:0% megabytes so at its most basic level a 04:17:06.239 --> 04:17:08.750 align:start position:0% megabytes so at its most basic level a signal<04:17:06.540> is<04:17:07.380> simply<04:17:07.739> data<04:17:08.279> or<04:17:08.460> information 04:17:08.750 --> 04:17:08.760 align:start position:0% signal is simply data or information 04:17:08.760 --> 04:17:12.370 align:start position:0% signal is simply data or information that<04:17:09.720> is<04:17:09.899> translated<04:17:10.560> into<04:17:11.340> measurable 04:17:12.370 --> 04:17:12.380 align:start position:0% that is translated into measurable 04:17:12.380 --> 04:17:16.429 align:start position:0% that is translated into measurable transmittable<04:17:13.380> and<04:17:14.340> receivable<04:17:15.439> formats 04:17:16.429 --> 04:17:16.439 align:start position:0% transmittable and receivable formats 04:17:16.439 --> 04:17:19.370 align:start position:0% transmittable and receivable formats meaning<04:17:17.399> that<04:17:17.819> it<04:17:18.060> is<04:17:18.239> what<04:17:18.479> allows<04:17:18.840> us<04:17:18.960> to 04:17:19.370 --> 04:17:19.380 align:start position:0% meaning that it is what allows us to 04:17:19.380 --> 04:17:21.469 align:start position:0% meaning that it is what allows us to transmit<04:17:19.920> and<04:17:20.100> receive<04:17:20.460> data 04:17:21.469 --> 04:17:21.479 align:start position:0% transmit and receive data 04:17:21.479 --> 04:17:24.410 align:start position:0% transmit and receive data now<04:17:22.020> an<04:17:22.500> analog<04:17:22.920> signal<04:17:23.340> is<04:17:23.760> a<04:17:23.880> signal<04:17:24.180> that 04:17:24.410 --> 04:17:24.420 align:start position:0% now an analog signal is a signal that 04:17:24.420 --> 04:17:28.550 align:start position:0% now an analog signal is a signal that carries<04:17:24.779> data<04:17:25.260> in<04:17:25.680> a<04:17:25.920> continuous<04:17:26.520> stream<04:17:27.020> or<04:17:28.020> a 04:17:28.550 --> 04:17:28.560 align:start position:0% carries data in a continuous stream or a 04:17:28.560 --> 04:17:32.150 align:start position:0% carries data in a continuous stream or a waveform<04:17:29.120> via<04:17:30.120> either<04:17:30.739> electromagnetic<04:17:31.739> or 04:17:32.150 --> 04:17:32.160 align:start position:0% waveform via either electromagnetic or 04:17:32.160 --> 04:17:34.790 align:start position:0% waveform via either electromagnetic or Optical<04:17:32.580> energy<04:17:32.880> and<04:17:33.720> this<04:17:34.020> energy<04:17:34.199> can<04:17:34.560> come 04:17:34.790 --> 04:17:34.800 align:start position:0% Optical energy and this energy can come 04:17:34.800 --> 04:17:38.150 align:start position:0% Optical energy and this energy can come from<04:17:35.100> many<04:17:35.399> different<04:17:35.760> sources<04:17:36.479> uh 04:17:38.150 --> 04:17:38.160 align:start position:0% from many different sources uh 04:17:38.160 --> 04:17:40.969 align:start position:0% from many different sources uh such<04:17:38.819> as<04:17:39.000> a<04:17:39.540> electric<04:17:39.840> current 04:17:40.969 --> 04:17:40.979 align:start position:0% such as a electric current 04:17:40.979 --> 04:17:43.670 align:start position:0% such as a electric current and<04:17:41.399> the<04:17:41.520> analog<04:17:41.939> waveforms<04:17:42.680> characteristics 04:17:43.670 --> 04:17:43.680 align:start position:0% and the analog waveforms characteristics 04:17:43.680 --> 04:17:45.950 align:start position:0% and the analog waveforms characteristics determine<04:17:44.520> the<04:17:44.760> information<04:17:45.060> that<04:17:45.779> it 04:17:45.950 --> 04:17:45.960 align:start position:0% determine the information that it 04:17:45.960 --> 04:17:48.590 align:start position:0% determine the information that it contains<04:17:46.500> because<04:17:47.040> the<04:17:47.399> analog<04:17:47.819> signal<04:17:48.300> will 04:17:48.590 --> 04:17:48.600 align:start position:0% contains because the analog signal will 04:17:48.600 --> 04:17:52.550 align:start position:0% contains because the analog signal will oscillate<04:17:49.199> between<04:17:50.000> minimum<04:17:51.000> and<04:17:51.899> maximum 04:17:52.550 --> 04:17:52.560 align:start position:0% oscillate between minimum and maximum 04:17:52.560 --> 04:17:55.130 align:start position:0% oscillate between minimum and maximum values<04:17:53.160> over<04:17:53.939> time 04:17:55.130 --> 04:17:55.140 align:start position:0% values over time 04:17:55.140 --> 04:17:58.130 align:start position:0% values over time basically<04:17:55.859> the<04:17:56.460> analog<04:17:56.880> signal<04:17:57.420> has<04:17:57.779> many 04:17:58.130 --> 04:17:58.140 align:start position:0% basically the analog signal has many 04:17:58.140 --> 04:18:00.170 align:start position:0% basically the analog signal has many attributes<04:17:58.800> to<04:17:58.979> it<04:17:59.100> and<04:17:59.279> it<04:17:59.460> can<04:17:59.520> be<04:17:59.699> read<04:17:59.880> in 04:18:00.170 --> 04:18:00.180 align:start position:0% attributes to it and it can be read in 04:18:00.180 --> 04:18:03.710 align:start position:0% attributes to it and it can be read in many<04:18:00.479> different<04:18:00.840> ways<04:18:02.000> depending<04:18:03.000> on<04:18:03.479> the 04:18:03.710 --> 04:18:03.720 align:start position:0% many different ways depending on the 04:18:03.720 --> 04:18:05.389 align:start position:0% many different ways depending on the values<04:18:04.080> and<04:18:04.199> the<04:18:04.380> information<04:18:04.560> in<04:18:05.279> the 04:18:05.389 --> 04:18:05.399 align:start position:0% values and the information in the 04:18:05.399 --> 04:18:08.110 align:start position:0% values and the information in the signals<04:18:05.760> given 04:18:08.110 --> 04:18:08.120 align:start position:0% signals given 04:18:08.120 --> 04:18:11.090 align:start position:0% signals given now<04:18:09.120> this<04:18:09.540> analog<04:18:09.960> signal<04:18:10.439> as<04:18:10.800> I<04:18:10.979> just 04:18:11.090 --> 04:18:11.100 align:start position:0% now this analog signal as I just 04:18:11.100 --> 04:18:12.650 align:start position:0% now this analog signal as I just mentioned<04:18:11.340> is<04:18:11.640> many<04:18:11.819> different<04:18:12.120> possible 04:18:12.650 --> 04:18:12.660 align:start position:0% mentioned is many different possible 04:18:12.660 --> 04:18:14.990 align:start position:0% mentioned is many different possible values<04:18:13.199> depending<04:18:14.040> on<04:18:14.160> the<04:18:14.340> characteristics 04:18:14.990 --> 04:18:15.000 align:start position:0% values depending on the characteristics 04:18:15.000 --> 04:18:17.330 align:start position:0% values depending on the characteristics and<04:18:15.239> how<04:18:15.479> that<04:18:15.660> signal<04:18:15.960> is<04:18:16.080> being<04:18:16.319> read<04:18:16.560> now 04:18:17.330 --> 04:18:17.340 align:start position:0% and how that signal is being read now 04:18:17.340 --> 04:18:19.250 align:start position:0% and how that signal is being read now the<04:18:17.520> characteristics<04:18:18.120> of<04:18:18.479> an<04:18:18.779> analog 04:18:19.250 --> 04:18:19.260 align:start position:0% the characteristics of an analog 04:18:19.260 --> 04:18:21.889 align:start position:0% the characteristics of an analog waveform<04:18:19.979> can<04:18:20.460> be<04:18:20.640> described<04:18:21.120> using<04:18:21.600> the 04:18:21.889 --> 04:18:21.899 align:start position:0% waveform can be described using the 04:18:21.899 --> 04:18:24.349 align:start position:0% waveform can be described using the following<04:18:22.260> terms<04:18:22.739> these<04:18:23.640> won't<04:18:23.819> necessarily 04:18:24.349 --> 04:18:24.359 align:start position:0% following terms these won't necessarily 04:18:24.359 --> 04:18:25.790 align:start position:0% following terms these won't necessarily appear<04:18:24.720> on<04:18:24.840> the<04:18:24.960> exam<04:18:25.260> but<04:18:25.439> they're<04:18:25.620> good 04:18:25.790 --> 04:18:25.800 align:start position:0% appear on the exam but they're good 04:18:25.800 --> 04:18:27.229 align:start position:0% appear on the exam but they're good background<04:18:26.160> information<04:18:26.460> for<04:18:26.880> you<04:18:27.060> anyway 04:18:27.229 --> 04:18:27.239 align:start position:0% background information for you anyway 04:18:27.239 --> 04:18:30.229 align:start position:0% background information for you anyway first<04:18:28.140> we<04:18:28.380> have<04:18:28.560> the<04:18:28.859> crest<04:18:29.220> or<04:18:29.520> the<04:18:29.699> peak<04:18:30.000> of 04:18:30.229 --> 04:18:30.239 align:start position:0% first we have the crest or the peak of 04:18:30.239 --> 04:18:32.929 align:start position:0% first we have the crest or the peak of the<04:18:30.420> signal<04:18:30.720> this<04:18:31.319> is<04:18:31.439> the<04:18:31.680> distance<04:18:31.859> from<04:18:32.699> the 04:18:32.929 --> 04:18:32.939 align:start position:0% the signal this is the distance from the 04:18:32.939 --> 04:18:35.750 align:start position:0% the signal this is the distance from the midpoint<04:18:33.359> to<04:18:34.020> the<04:18:34.260> topmost<04:18:34.680> part<04:18:35.040> of<04:18:35.279> the<04:18:35.520> wave 04:18:35.750 --> 04:18:35.760 align:start position:0% midpoint to the topmost part of the wave 04:18:35.760 --> 04:18:37.550 align:start position:0% midpoint to the topmost part of the wave and<04:18:36.180> when<04:18:36.300> we<04:18:36.420> talk<04:18:36.540> about<04:18:36.660> the<04:18:36.960> midpoint<04:18:37.260> we 04:18:37.550 --> 04:18:37.560 align:start position:0% and when we talk about the midpoint we 04:18:37.560 --> 04:18:39.170 align:start position:0% and when we talk about the midpoint we talk<04:18:37.739> about<04:18:37.859> this<04:18:38.279> line<04:18:38.460> that's<04:18:38.819> sort<04:18:39.060> of 04:18:39.170 --> 04:18:39.180 align:start position:0% talk about this line that's sort of 04:18:39.180 --> 04:18:40.269 align:start position:0% talk about this line that's sort of going<04:18:39.300> through 04:18:40.269 --> 04:18:40.279 align:start position:0% going through 04:18:40.279 --> 04:18:43.250 align:start position:0% going through inversely<04:18:41.279> the<04:18:42.000> trough<04:18:42.300> is<04:18:42.899> the<04:18:43.080> distance 04:18:43.250 --> 04:18:43.260 align:start position:0% inversely the trough is the distance 04:18:43.260 --> 04:18:45.290 align:start position:0% inversely the trough is the distance from<04:18:43.620> the<04:18:43.800> midpoint<04:18:44.160> to<04:18:44.640> the<04:18:44.819> bottom<04:18:45.120> most 04:18:45.290 --> 04:18:45.300 align:start position:0% from the midpoint to the bottom most 04:18:45.300 --> 04:18:46.729 align:start position:0% from the midpoint to the bottom most portion<04:18:45.720> of<04:18:45.840> the<04:18:46.020> wave 04:18:46.729 --> 04:18:46.739 align:start position:0% portion of the wave 04:18:46.739 --> 04:18:48.110 align:start position:0% portion of the wave now<04:18:47.100> the<04:18:47.279> next<04:18:47.340> term<04:18:47.460> I<04:18:47.699> want<04:18:47.760> to<04:18:47.880> talk<04:18:48.000> about 04:18:48.110 --> 04:18:48.120 align:start position:0% now the next term I want to talk about 04:18:48.120 --> 04:18:51.950 align:start position:0% now the next term I want to talk about is<04:18:48.420> amplitude<04:18:49.460> amplitude<04:18:50.460> is<04:18:50.699> exactly<04:18:51.239> one 04:18:51.950 --> 04:18:51.960 align:start position:0% is amplitude amplitude is exactly one 04:18:51.960 --> 04:18:54.830 align:start position:0% is amplitude amplitude is exactly one half<04:18:52.199> the<04:18:52.500> distance<04:18:52.739> between<04:18:53.340> the<04:18:53.939> crest<04:18:54.300> and 04:18:54.830 --> 04:18:54.840 align:start position:0% half the distance between the crest and 04:18:54.840 --> 04:18:57.349 align:start position:0% half the distance between the crest and the<04:18:55.020> trough<04:18:55.319> of<04:18:55.680> the<04:18:55.859> wave<04:18:56.100> so<04:18:57.000> it<04:18:57.239> would 04:18:57.349 --> 04:18:57.359 align:start position:0% the trough of the wave so it would 04:18:57.359 --> 04:18:59.990 align:start position:0% the trough of the wave so it would either<04:18:57.540> be<04:18:57.899> this<04:18:58.739> could<04:18:58.979> be<04:18:59.100> the<04:18:59.340> what<04:18:59.880> it's 04:18:59.990 --> 04:19:00.000 align:start position:0% either be this could be the what it's 04:19:00.000 --> 04:19:01.010 align:start position:0% either be this could be the what it's measured<04:19:00.300> it<04:19:00.420> could<04:19:00.479> be<04:19:00.600> the<04:19:00.660> amplitude 04:19:01.010 --> 04:19:01.020 align:start position:0% measured it could be the amplitude 04:19:01.020 --> 04:19:02.510 align:start position:0% measured it could be the amplitude alternatively 04:19:02.510 --> 04:19:02.520 align:start position:0% alternatively 04:19:02.520 --> 04:19:04.550 align:start position:0% alternatively this<04:19:02.939> could<04:19:03.060> be<04:19:03.180> the<04:19:03.359> amplitude 04:19:04.550 --> 04:19:04.560 align:start position:0% this could be the amplitude 04:19:04.560 --> 04:19:06.830 align:start position:0% this could be the amplitude and<04:19:04.979> the<04:19:05.160> cycle<04:19:05.520> is<04:19:05.819> one<04:19:06.239> complete 04:19:06.830 --> 04:19:06.840 align:start position:0% and the cycle is one complete 04:19:06.840 --> 04:19:09.469 align:start position:0% and the cycle is one complete oscillation<04:19:07.560> of<04:19:07.979> the<04:19:08.160> wave<04:19:08.340> from<04:19:08.760> start<04:19:09.120> to 04:19:09.469 --> 04:19:09.479 align:start position:0% oscillation of the wave from start to 04:19:09.479 --> 04:19:11.750 align:start position:0% oscillation of the wave from start to finish<04:19:09.840> changing<04:19:10.800> from<04:19:11.100> one<04:19:11.279> state<04:19:11.520> to 04:19:11.750 --> 04:19:11.760 align:start position:0% finish changing from one state to 04:19:11.760 --> 04:19:14.030 align:start position:0% finish changing from one state to another<04:19:11.939> and<04:19:12.239> Back<04:19:12.420> Again<04:19:12.680> basically<04:19:13.680> from 04:19:14.030 --> 04:19:14.040 align:start position:0% another and Back Again basically from 04:19:14.040 --> 04:19:16.929 align:start position:0% another and Back Again basically from the<04:19:14.220> midpoint<04:19:14.640> going<04:19:15.180> up<04:19:15.479> until<04:19:16.140> we<04:19:16.560> get<04:19:16.680> to 04:19:16.929 --> 04:19:16.939 align:start position:0% the midpoint going up until we get to 04:19:16.939 --> 04:19:19.849 align:start position:0% the midpoint going up until we get to the<04:19:17.939> next<04:19:18.060> midpoint 04:19:19.849 --> 04:19:19.859 align:start position:0% the next midpoint 04:19:19.859 --> 04:19:22.010 align:start position:0% the next midpoint after<04:19:20.279> it<04:19:20.520> goes<04:19:20.819> down 04:19:22.010 --> 04:19:22.020 align:start position:0% after it goes down 04:19:22.020 --> 04:19:25.070 align:start position:0% after it goes down now<04:19:22.500> the<04:19:22.920> wavelength<04:19:23.699> is<04:19:24.000> determined<04:19:24.540> by<04:19:24.779> the 04:19:25.070 --> 04:19:25.080 align:start position:0% now the wavelength is determined by the 04:19:25.080 --> 04:19:28.429 align:start position:0% now the wavelength is determined by the distance<04:19:25.520> between<04:19:26.520> two<04:19:27.180> consecutive<04:19:27.779> troughs 04:19:28.429 --> 04:19:28.439 align:start position:0% distance between two consecutive troughs 04:19:28.439 --> 04:19:30.830 align:start position:0% distance between two consecutive troughs or<04:19:28.920> Peaks<04:19:29.399> so<04:19:29.939> here<04:19:30.120> we're<04:19:30.300> measuring<04:19:30.720> the 04:19:30.830 --> 04:19:30.840 align:start position:0% or Peaks so here we're measuring the 04:19:30.840 --> 04:19:33.229 align:start position:0% or Peaks so here we're measuring the wavelength<04:19:31.319> between<04:19:31.620> two<04:19:31.920> troughs<04:19:32.460> we<04:19:33.120> could 04:19:33.229 --> 04:19:33.239 align:start position:0% wavelength between two troughs we could 04:19:33.239 --> 04:19:36.170 align:start position:0% wavelength between two troughs we could also<04:19:33.540> measure<04:19:33.899> it<04:19:34.020> between<04:19:34.620> two<04:19:34.979> peaks<04:19:35.460> like 04:19:36.170 --> 04:19:36.180 align:start position:0% also measure it between two peaks like 04:19:36.180 --> 04:19:37.250 align:start position:0% also measure it between two peaks like so 04:19:37.250 --> 04:19:37.260 align:start position:0% so 04:19:37.260 --> 04:19:40.309 align:start position:0% so now<04:19:37.620> the<04:19:37.920> frequency<04:19:38.340> also<04:19:39.060> called<04:19:39.300> the<04:19:39.960> period 04:19:40.309 --> 04:19:40.319 align:start position:0% now the frequency also called the period 04:19:40.319 --> 04:19:42.889 align:start position:0% now the frequency also called the period of<04:19:40.680> the<04:19:40.859> wave<04:19:41.100> is<04:19:41.580> the<04:19:41.819> number<04:19:42.000> of<04:19:42.359> complete 04:19:42.889 --> 04:19:42.899 align:start position:0% of the wave is the number of complete 04:19:42.899 --> 04:19:46.370 align:start position:0% of the wave is the number of complete cycles<04:19:43.380> per<04:19:43.979> second<04:19:44.279> in<04:19:45.180> a<04:19:45.359> wave<04:19:45.600> this<04:19:46.199> is 04:19:46.370 --> 04:19:46.380 align:start position:0% cycles per second in a wave this is 04:19:46.380 --> 04:19:47.750 align:start position:0% cycles per second in a wave this is generally<04:19:46.680> measured 04:19:47.750 --> 04:19:47.760 align:start position:0% generally measured 04:19:47.760 --> 04:19:51.110 align:start position:0% generally measured in<04:19:48.300> hertz<04:19:48.720> such<04:19:49.260> as<04:19:49.439> gigahertz<04:19:50.040> or<04:19:50.580> megahertz 04:19:51.110 --> 04:19:51.120 align:start position:0% in hertz such as gigahertz or megahertz 04:19:51.120 --> 04:19:54.290 align:start position:0% in hertz such as gigahertz or megahertz now<04:19:52.080> the<04:19:52.260> last<04:19:52.439> term<04:19:52.620> is<04:19:53.040> the<04:19:53.580> phase<04:19:53.819> of<04:19:54.120> the 04:19:54.290 --> 04:19:54.300 align:start position:0% now the last term is the phase of the 04:19:54.300 --> 04:19:55.130 align:start position:0% now the last term is the phase of the wave 04:19:55.130 --> 04:19:55.140 align:start position:0% wave 04:19:55.140 --> 04:19:58.429 align:start position:0% wave the<04:19:56.100> phase<04:19:56.399> is<04:19:57.060> the<04:19:57.300> relationship<04:19:57.840> of<04:19:58.260> the 04:19:58.429 --> 04:19:58.439 align:start position:0% the phase is the relationship of the 04:19:58.439 --> 04:20:01.490 align:start position:0% the phase is the relationship of the Cycles<04:19:58.859> beginning<04:19:59.479> to<04:20:00.479> a<04:20:00.660> fixed<04:20:01.020> point<04:20:01.260> in 04:20:01.490 --> 04:20:01.500 align:start position:0% Cycles beginning to a fixed point in 04:20:01.500 --> 04:20:04.849 align:start position:0% Cycles beginning to a fixed point in time<04:20:01.819> meaning<04:20:02.819> if<04:20:03.479> two<04:20:03.779> waves<04:20:04.199> with<04:20:04.500> the<04:20:04.680> same 04:20:04.849 --> 04:20:04.859 align:start position:0% time meaning if two waves with the same 04:20:04.859 --> 04:20:07.910 align:start position:0% time meaning if two waves with the same frequency<04:20:05.340> are<04:20:06.239> transmitted<04:20:06.960> at<04:20:07.500> the<04:20:07.680> same 04:20:07.910 --> 04:20:07.920 align:start position:0% frequency are transmitted at the same 04:20:07.920 --> 04:20:09.110 align:start position:0% frequency are transmitted at the same time 04:20:09.110 --> 04:20:09.120 align:start position:0% time 04:20:09.120 --> 04:20:12.050 align:start position:0% time they<04:20:09.600> are<04:20:09.720> said<04:20:09.899> to<04:20:10.080> be<04:20:10.199> in<04:20:10.620> phase<04:20:10.979> and<04:20:11.880> two 04:20:12.050 --> 04:20:12.060 align:start position:0% they are said to be in phase and two 04:20:12.060 --> 04:20:13.969 align:start position:0% they are said to be in phase and two that<04:20:12.300> are<04:20:12.479> purposely<04:20:12.899> offset<04:20:13.560> from<04:20:13.800> each 04:20:13.969 --> 04:20:13.979 align:start position:0% that are purposely offset from each 04:20:13.979 --> 04:20:16.010 align:start position:0% that are purposely offset from each other<04:20:14.120> or<04:20:15.120> if<04:20:15.359> they<04:20:15.540> have<04:20:15.720> different 04:20:16.010 --> 04:20:16.020 align:start position:0% other or if they have different 04:20:16.020 --> 04:20:19.670 align:start position:0% other or if they have different frequencies<04:20:16.739> like<04:20:17.520> these<04:20:17.880> do<04:20:18.060> they<04:20:18.660> will<04:20:18.899> be 04:20:19.670 --> 04:20:19.680 align:start position:0% frequencies like these do they will be 04:20:19.680 --> 04:20:21.349 align:start position:0% frequencies like these do they will be out<04:20:20.340> of<04:20:20.460> phase 04:20:21.349 --> 04:20:21.359 align:start position:0% out of phase 04:20:21.359 --> 04:20:24.110 align:start position:0% out of phase the<04:20:21.899> device<04:20:22.199> that<04:20:22.680> plots<04:20:23.040> the<04:20:23.399> amplitude<04:20:23.880> of 04:20:24.110 --> 04:20:24.120 align:start position:0% the device that plots the amplitude of 04:20:24.120 --> 04:20:26.450 align:start position:0% the device that plots the amplitude of an<04:20:24.359> analog<04:20:24.779> signal<04:20:25.260> what<04:20:25.859> would<04:20:26.040> show<04:20:26.279> you 04:20:26.450 --> 04:20:26.460 align:start position:0% an analog signal what would show you 04:20:26.460 --> 04:20:30.229 align:start position:0% an analog signal what would show you this<04:20:26.760> wave<04:20:27.120> is<04:20:27.840> called<04:20:28.199> an<04:20:28.979> oscilloscope 04:20:30.229 --> 04:20:30.239 align:start position:0% this wave is called an oscilloscope 04:20:30.239 --> 04:20:33.170 align:start position:0% this wave is called an oscilloscope and<04:20:30.779> you<04:20:30.899> may<04:20:31.080> have<04:20:31.260> seen<04:20:31.500> this<04:20:31.800> perhaps<04:20:32.460> at<04:20:33.000> a 04:20:33.170 --> 04:20:33.180 align:start position:0% and you may have seen this perhaps at a 04:20:33.180 --> 04:20:36.349 align:start position:0% and you may have seen this perhaps at a store<04:20:33.359> or<04:20:34.319> even<04:20:34.500> on<04:20:35.040> TV<04:20:35.340> and<04:20:35.819> we<04:20:36.000> can<04:20:36.120> measure 04:20:36.349 --> 04:20:36.359 align:start position:0% store or even on TV and we can measure 04:20:36.359 --> 04:20:38.030 align:start position:0% store or even on TV and we can measure waves<04:20:36.720> of<04:20:36.899> all<04:20:37.020> sorts<04:20:37.319> of<04:20:37.380> things<04:20:37.560> for 04:20:38.030 --> 04:20:38.040 align:start position:0% waves of all sorts of things for 04:20:38.040 --> 04:20:40.010 align:start position:0% waves of all sorts of things for instance<04:20:38.279> sound<04:20:38.819> might<04:20:39.180> be<04:20:39.359> a<04:20:39.600> wave<04:20:39.840> that 04:20:40.010 --> 04:20:40.020 align:start position:0% instance sound might be a wave that 04:20:40.020 --> 04:20:41.990 align:start position:0% instance sound might be a wave that you've<04:20:40.319> seen<04:20:40.500> when<04:20:41.100> you're<04:20:41.279> running<04:20:41.520> a 04:20:41.990 --> 04:20:42.000 align:start position:0% you've seen when you're running a 04:20:42.000 --> 04:20:44.450 align:start position:0% you've seen when you're running a program<04:20:42.479> on<04:20:42.840> your<04:20:43.020> computer<04:20:43.199> this<04:20:44.100> gives<04:20:44.340> you 04:20:44.450 --> 04:20:44.460 align:start position:0% program on your computer this gives you 04:20:44.460 --> 04:20:47.269 align:start position:0% program on your computer this gives you a<04:20:44.640> real-time<04:20:45.000> view<04:20:45.300> of<04:20:45.600> the<04:20:45.840> analog<04:20:46.279> waveforms 04:20:47.269 --> 04:20:47.279 align:start position:0% a real-time view of the analog waveforms 04:20:47.279 --> 04:20:49.790 align:start position:0% a real-time view of the analog waveforms and<04:20:47.760> its<04:20:48.060> shape<04:20:48.300> if<04:20:48.660> we've<04:20:48.960> just<04:20:49.080> as<04:20:49.500> we've 04:20:49.790 --> 04:20:49.800 align:start position:0% and its shape if we've just as we've 04:20:49.800 --> 04:20:53.269 align:start position:0% and its shape if we've just as we've just<04:20:49.920> described<04:20:50.399> now<04:20:51.120> unlike<04:20:51.660> analog<04:20:52.620> signals 04:20:53.269 --> 04:20:53.279 align:start position:0% just described now unlike analog signals 04:20:53.279 --> 04:20:55.010 align:start position:0% just described now unlike analog signals which<04:20:53.520> can<04:20:53.640> have<04:20:53.880> many<04:20:54.180> different<04:20:54.420> values 04:20:55.010 --> 04:20:55.020 align:start position:0% which can have many different values 04:20:55.020 --> 04:20:57.530 align:start position:0% which can have many different values assigned<04:20:55.439> to<04:20:55.560> them<04:20:55.880> Digital<04:20:56.880> Data 04:20:57.530 --> 04:20:57.540 align:start position:0% assigned to them Digital Data 04:20:57.540 --> 04:21:00.050 align:start position:0% assigned to them Digital Data Transmissions<04:20:58.460> utilize<04:20:59.460> voltage 04:21:00.050 --> 04:21:00.060 align:start position:0% Transmissions utilize voltage 04:21:00.060 --> 04:21:02.809 align:start position:0% Transmissions utilize voltage differences<04:21:00.800> represented<04:21:01.800> either<04:21:02.040> by<04:21:02.340> ones 04:21:02.809 --> 04:21:02.819 align:start position:0% differences represented either by ones 04:21:02.819 --> 04:21:06.650 align:start position:0% differences represented either by ones and<04:21:03.420> zeros<04:21:03.859> these<04:21:04.859> ones<04:21:05.279> and<04:21:05.520> zeros<04:21:06.000> are<04:21:06.479> what 04:21:06.650 --> 04:21:06.660 align:start position:0% and zeros these ones and zeros are what 04:21:06.660 --> 04:21:09.469 align:start position:0% and zeros these ones and zeros are what make<04:21:07.020> up<04:21:07.319> all<04:21:07.680> of<04:21:07.859> the<04:21:08.100> information 04:21:09.469 --> 04:21:09.479 align:start position:0% make up all of the information 04:21:09.479 --> 04:21:12.710 align:start position:0% make up all of the information when<04:21:10.199> there<04:21:10.439> is<04:21:10.680> a<04:21:10.859> presence<04:21:11.220> of<04:21:11.399> a<04:21:11.580> signal<04:21:11.880> or 04:21:12.710 --> 04:21:12.720 align:start position:0% when there is a presence of a signal or 04:21:12.720 --> 04:21:15.170 align:start position:0% when there is a presence of a signal or voltage<04:21:13.199> meaning<04:21:13.739> that<04:21:14.040> it<04:21:14.160> is<04:21:14.340> on<04:21:14.580> it 04:21:15.170 --> 04:21:15.180 align:start position:0% voltage meaning that it is on it 04:21:15.180 --> 04:21:17.090 align:start position:0% voltage meaning that it is on it translates<04:21:15.660> to<04:21:16.080> one 04:21:17.090 --> 04:21:17.100 align:start position:0% translates to one 04:21:17.100 --> 04:21:19.670 align:start position:0% translates to one and<04:21:17.819> a<04:21:18.060> lack<04:21:18.239> of<04:21:18.420> voltage<04:21:18.720> or<04:21:18.960> an<04:21:19.140> absence<04:21:19.500> of 04:21:19.670 --> 04:21:19.680 align:start position:0% and a lack of voltage or an absence of 04:21:19.680 --> 04:21:23.150 align:start position:0% and a lack of voltage or an absence of this<04:21:19.859> signal<04:21:20.220> translates<04:21:20.939> to<04:21:21.300> zero<04:21:22.020> now<04:21:22.620> in 04:21:23.150 --> 04:21:23.160 align:start position:0% this signal translates to zero now in 04:21:23.160 --> 04:21:25.849 align:start position:0% this signal translates to zero now in computer<04:21:23.460> networks<04:21:24.239> digital<04:21:24.840> waveforms<04:21:25.560> can 04:21:25.849 --> 04:21:25.859 align:start position:0% computer networks digital waveforms can 04:21:25.859 --> 04:21:27.769 align:start position:0% computer networks digital waveforms can switch<04:21:26.040> between<04:21:26.460> two<04:21:26.939> voltage<04:21:27.300> levels 04:21:27.769 --> 04:21:27.779 align:start position:0% switch between two voltage levels 04:21:27.779 --> 04:21:30.889 align:start position:0% switch between two voltage levels depending<04:21:28.500> on<04:21:28.739> its<04:21:28.979> relation<04:21:29.279> to<04:21:30.120> the<04:21:30.720> ground 04:21:30.889 --> 04:21:30.899 align:start position:0% depending on its relation to the ground 04:21:30.899 --> 04:21:33.050 align:start position:0% depending on its relation to the ground if<04:21:31.319> you<04:21:31.500> recall<04:21:31.739> what<04:21:31.920> that<04:21:32.100> is 04:21:33.050 --> 04:21:33.060 align:start position:0% if you recall what that is 04:21:33.060 --> 04:21:35.689 align:start position:0% if you recall what that is now<04:21:33.540> because<04:21:33.720> digital<04:21:34.500> signals<04:21:35.100> utilize 04:21:35.689 --> 04:21:35.699 align:start position:0% now because digital signals utilize 04:21:35.699 --> 04:21:38.269 align:start position:0% now because digital signals utilize voltage<04:21:36.359> to<04:21:36.660> represent<04:21:37.080> its<04:21:37.500> values<04:21:37.739> of<04:21:37.920> ones 04:21:38.269 --> 04:21:38.279 align:start position:0% voltage to represent its values of ones 04:21:38.279 --> 04:21:41.030 align:start position:0% voltage to represent its values of ones and<04:21:38.460> zeros<04:21:38.819> this<04:21:39.420> is<04:21:39.540> also<04:21:39.840> called<04:21:40.199> The 04:21:41.030 --> 04:21:41.040 align:start position:0% and zeros this is also called The 04:21:41.040 --> 04:21:45.530 align:start position:0% and zeros this is also called The Logical<04:21:41.640> state<04:21:42.420> of<04:21:43.199> the<04:21:43.380> data 04:21:45.530 --> 04:21:45.540 align:start position:0% Logical state of the data 04:21:45.540 --> 04:21:50.210 align:start position:0% Logical state of the data each<04:21:46.439> bit<04:21:46.800> or<04:21:47.580> binary<04:21:48.120> digit<04:21:49.140> takes<04:21:49.800> a 04:21:50.210 --> 04:21:50.220 align:start position:0% each bit or binary digit takes a 04:21:50.220 --> 04:21:53.809 align:start position:0% each bit or binary digit takes a predetermined<04:21:51.000> period<04:21:51.960> of<04:21:52.260> time<04:21:52.560> to<04:21:53.220> transmit 04:21:53.809 --> 04:21:53.819 align:start position:0% predetermined period of time to transmit 04:21:53.819 --> 04:21:57.290 align:start position:0% predetermined period of time to transmit and<04:21:54.600> bit<04:21:54.840> patterns<04:21:55.680> are<04:21:56.220> used<04:21:56.460> to<04:21:56.819> establish 04:21:57.290 --> 04:21:57.300 align:start position:0% and bit patterns are used to establish 04:21:57.300 --> 04:21:59.570 align:start position:0% and bit patterns are used to establish the<04:21:57.660> start<04:21:57.899> and<04:21:58.560> the<04:21:58.680> stop<04:21:58.859> of<04:21:59.100> the<04:21:59.220> sequence 04:21:59.570 --> 04:21:59.580 align:start position:0% the start and the stop of the sequence 04:21:59.580 --> 04:22:03.349 align:start position:0% the start and the stop of the sequence and<04:22:00.239> the<04:22:00.420> sink<04:22:00.720> clocks<04:22:01.500> which<04:22:02.340> allows<04:22:02.819> the 04:22:03.349 --> 04:22:03.359 align:start position:0% and the sink clocks which allows the 04:22:03.359 --> 04:22:05.389 align:start position:0% and the sink clocks which allows the receiver<04:22:03.840> and<04:22:04.439> the<04:22:04.560> sender<04:22:04.859> to<04:22:05.100> be<04:22:05.220> on 04:22:05.389 --> 04:22:05.399 align:start position:0% receiver and the sender to be on 04:22:05.399 --> 04:22:08.090 align:start position:0% receiver and the sender to be on basically<04:22:05.880> the<04:22:06.120> same<04:22:06.300> page<04:22:06.720> the<04:22:07.680> sender<04:22:08.040> and 04:22:08.090 --> 04:22:08.100 align:start position:0% basically the same page the sender and 04:22:08.100 --> 04:22:10.010 align:start position:0% basically the same page the sender and the<04:22:08.279> receiver<04:22:08.520> have<04:22:08.880> to<04:22:09.120> then<04:22:09.359> synchronize 04:22:10.010 --> 04:22:10.020 align:start position:0% the receiver have to then synchronize 04:22:10.020 --> 04:22:12.650 align:start position:0% the receiver have to then synchronize these<04:22:10.380> clocks<04:22:10.739> to<04:22:11.040> ensure<04:22:11.399> proper<04:22:12.000> reception 04:22:12.650 --> 04:22:12.660 align:start position:0% these clocks to ensure proper reception 04:22:12.660 --> 04:22:15.889 align:start position:0% these clocks to ensure proper reception or<04:22:13.140> receipt<04:22:13.560> of<04:22:13.979> the<04:22:14.160> data<04:22:14.939> now<04:22:15.420> there<04:22:15.660> are<04:22:15.840> a 04:22:15.889 --> 04:22:15.899 align:start position:0% or receipt of the data now there are a 04:22:15.899 --> 04:22:18.769 align:start position:0% or receipt of the data now there are a couple<04:22:16.020> different<04:22:16.260> ways<04:22:16.979> that<04:22:17.279> we<04:22:17.580> encode<04:22:18.120> in 04:22:18.769 --> 04:22:18.779 align:start position:0% couple different ways that we encode in 04:22:18.779 --> 04:22:21.290 align:start position:0% couple different ways that we encode in order<04:22:18.899> to<04:22:19.260> allow<04:22:19.560> devices<04:22:20.040> to<04:22:20.520> tell<04:22:20.699> which<04:22:21.060> bit 04:22:21.290 --> 04:22:21.300 align:start position:0% order to allow devices to tell which bit 04:22:21.300 --> 04:22:24.170 align:start position:0% order to allow devices to tell which bit is<04:22:21.660> what<04:22:21.899> in<04:22:22.439> other<04:22:22.560> words<04:22:22.739> to<04:22:23.220> tell<04:22:23.399> it<04:22:23.580> when 04:22:24.170 --> 04:22:24.180 align:start position:0% is what in other words to tell it when 04:22:24.180 --> 04:22:26.450 align:start position:0% is what in other words to tell it when it<04:22:24.359> starts<04:22:24.720> and<04:22:24.840> when<04:22:25.080> it<04:22:25.260> ends 04:22:26.450 --> 04:22:26.460 align:start position:0% it starts and when it ends 04:22:26.460 --> 04:22:28.010 align:start position:0% it starts and when it ends the<04:22:26.760> first<04:22:26.880> method<04:22:27.239> I<04:22:27.359> want<04:22:27.479> to<04:22:27.600> look<04:22:27.660> at<04:22:27.840> is 04:22:28.010 --> 04:22:28.020 align:start position:0% the first method I want to look at is 04:22:28.020 --> 04:22:31.610 align:start position:0% the first method I want to look at is called<04:22:28.319> on<04:22:28.859> off<04:22:29.100> keying<04:22:29.720> this<04:22:30.720> looks<04:22:31.199> at<04:22:31.319> the 04:22:31.610 --> 04:22:31.620 align:start position:0% called on off keying this looks at the 04:22:31.620 --> 04:22:33.110 align:start position:0% called on off keying this looks at the voltage<04:22:32.100> change 04:22:33.110 --> 04:22:33.120 align:start position:0% voltage change 04:22:33.120 --> 04:22:39.530 align:start position:0% voltage change from<04:22:33.720> one<04:22:34.020> state<04:22:34.380> to<04:22:35.220> the<04:22:35.520> other 04:22:39.530 --> 04:22:39.540 align:start position:0% 04:22:39.540 --> 04:22:50.030 align:start position:0% within<04:22:40.260> a<04:22:40.800> pre-specified<04:22:41.760> interval 04:22:50.030 --> 04:22:50.040 align:start position:0% 04:22:50.040 --> 04:22:52.550 align:start position:0% which<04:22:50.580> is<04:22:50.760> represented<04:22:51.300> by<04:22:51.540> the<04:22:51.720> binary<04:22:52.080> digit 04:22:52.550 --> 04:22:52.560 align:start position:0% which is represented by the binary digit 04:22:52.560 --> 04:22:55.729 align:start position:0% which is represented by the binary digit one<04:22:53.340> and<04:22:54.060> the<04:22:54.359> lack<04:22:54.540> of<04:22:54.720> voltage<04:22:55.080> or<04:22:55.500> no 04:22:55.729 --> 04:22:55.739 align:start position:0% one and the lack of voltage or no 04:22:55.739 --> 04:22:57.769 align:start position:0% one and the lack of voltage or no voltage<04:22:56.100> is<04:22:56.279> represented<04:22:56.880> by<04:22:57.060> zero<04:22:57.479> as<04:22:57.600> we 04:22:57.769 --> 04:22:57.779 align:start position:0% voltage is represented by zero as we 04:22:57.779 --> 04:23:00.170 align:start position:0% voltage is represented by zero as we just<04:22:57.960> saw<04:22:58.199> now<04:22:58.979> the<04:22:59.160> synchronization<04:22:59.760> between 04:23:00.170 --> 04:23:00.180 align:start position:0% just saw now the synchronization between 04:23:00.180 --> 04:23:02.750 align:start position:0% just saw now the synchronization between the<04:23:00.540> sender<04:23:00.899> and<04:23:01.080> the<04:23:01.199> receiver<04:23:01.520> occurs<04:23:02.520> with 04:23:02.750 --> 04:23:02.760 align:start position:0% the sender and the receiver occurs with 04:23:02.760 --> 04:23:05.870 align:start position:0% the sender and the receiver occurs with the<04:23:03.000> receiver<04:23:03.359> waiting<04:23:04.319> for<04:23:04.620> a<04:23:04.979> series<04:23:05.220> of 04:23:05.870 --> 04:23:05.880 align:start position:0% the receiver waiting for a series of 04:23:05.880 --> 04:23:09.830 align:start position:0% the receiver waiting for a series of ones 04:23:09.830 --> 04:23:09.840 align:start position:0% 04:23:09.840 --> 04:23:12.110 align:start position:0% because<04:23:10.380> of<04:23:10.620> this<04:23:10.859> there<04:23:11.160> is<04:23:11.340> a<04:23:11.460> potential<04:23:11.880> for 04:23:12.110 --> 04:23:12.120 align:start position:0% because of this there is a potential for 04:23:12.120 --> 04:23:14.389 align:start position:0% because of this there is a potential for problems<04:23:12.600> to<04:23:12.779> arise<04:23:13.199> especially<04:23:14.040> when<04:23:14.220> the 04:23:14.389 --> 04:23:14.399 align:start position:0% problems to arise especially when the 04:23:14.399 --> 04:23:17.090 align:start position:0% problems to arise especially when the sender<04:23:14.819> has<04:23:15.060> a<04:23:15.300> long<04:23:15.479> series<04:23:15.899> of<04:23:16.380> ones<04:23:16.800> to 04:23:17.090 --> 04:23:17.100 align:start position:0% sender has a long series of ones to 04:23:17.100 --> 04:23:20.030 align:start position:0% sender has a long series of ones to transmit<04:23:17.580> within<04:23:18.180> the<04:23:18.359> data<04:23:18.720> this<04:23:19.439> means<04:23:19.739> that 04:23:20.030 --> 04:23:20.040 align:start position:0% transmit within the data this means that 04:23:20.040 --> 04:23:22.429 align:start position:0% transmit within the data this means that it<04:23:20.399> could<04:23:20.580> take<04:23:20.939> a<04:23:21.359> long<04:23:21.540> while<04:23:21.840> for<04:23:22.260> the 04:23:22.429 --> 04:23:22.439 align:start position:0% it could take a long while for the 04:23:22.439 --> 04:23:24.469 align:start position:0% it could take a long while for the sender<04:23:22.800> and<04:23:22.920> the<04:23:23.100> receiver<04:23:23.399> to<04:23:24.060> synchronize 04:23:24.469 --> 04:23:24.479 align:start position:0% sender and the receiver to synchronize 04:23:24.479 --> 04:23:25.969 align:start position:0% sender and the receiver to synchronize their<04:23:24.779> clocks<04:23:25.140> together 04:23:25.969 --> 04:23:25.979 align:start position:0% their clocks together 04:23:25.979 --> 04:23:27.650 align:start position:0% their clocks together in<04:23:26.460> the<04:23:26.640> event<04:23:26.699> that<04:23:26.939> the<04:23:27.060> clocks<04:23:27.359> are<04:23:27.479> not 04:23:27.650 --> 04:23:27.660 align:start position:0% in the event that the clocks are not 04:23:27.660 --> 04:23:29.990 align:start position:0% in the event that the clocks are not sync<04:23:28.080> then<04:23:28.260> there's<04:23:28.439> a<04:23:28.739> high<04:23:28.859> probability<04:23:29.399> for 04:23:29.990 --> 04:23:30.000 align:start position:0% sync then there's a high probability for 04:23:30.000 --> 04:23:34.550 align:start position:0% sync then there's a high probability for data<04:23:30.960> corruption<04:23:31.439> as<04:23:32.100> the<04:23:32.819> receiver<04:23:33.560> can't 04:23:34.550 --> 04:23:34.560 align:start position:0% data corruption as the receiver can't 04:23:34.560 --> 04:23:37.309 align:start position:0% data corruption as the receiver can't determine<04:23:35.100> how<04:23:35.760> many<04:23:35.880> ones<04:23:36.359> and<04:23:36.540> zeros<04:23:36.960> have 04:23:37.309 --> 04:23:37.319 align:start position:0% determine how many ones and zeros have 04:23:37.319 --> 04:23:39.349 align:start position:0% determine how many ones and zeros have to<04:23:37.439> be<04:23:37.620> transmitted<04:23:38.279> now<04:23:38.939> there<04:23:39.120> are<04:23:39.239> two 04:23:39.349 --> 04:23:39.359 align:start position:0% to be transmitted now there are two 04:23:39.359 --> 04:23:41.870 align:start position:0% to be transmitted now there are two variations<04:23:39.899> of<04:23:40.620> on<04:23:40.859> and<04:23:41.040> off<04:23:41.160> keying<04:23:41.580> I<04:23:41.760> have 04:23:41.870 --> 04:23:41.880 align:start position:0% variations of on and off keying I have 04:23:41.880 --> 04:23:42.889 align:start position:0% variations of on and off keying I have listed<04:23:42.239> here 04:23:42.889 --> 04:23:42.899 align:start position:0% listed here 04:23:42.899 --> 04:23:45.290 align:start position:0% listed here one<04:23:43.319> is<04:23:43.500> called<04:23:43.739> the<04:23:44.100> non-return<04:23:44.760> to<04:23:44.939> zero 04:23:45.290 --> 04:23:45.300 align:start position:0% one is called the non-return to zero 04:23:45.300 --> 04:23:47.630 align:start position:0% one is called the non-return to zero variation<04:23:45.779> and<04:23:46.439> the<04:23:46.680> other<04:23:46.800> is<04:23:47.460> the 04:23:47.630 --> 04:23:47.640 align:start position:0% variation and the other is the 04:23:47.640 --> 04:23:49.969 align:start position:0% variation and the other is the non-return<04:23:48.180> to<04:23:48.300> zero<04:23:48.660> inverted 04:23:49.969 --> 04:23:49.979 align:start position:0% non-return to zero inverted 04:23:49.979 --> 04:23:52.729 align:start position:0% non-return to zero inverted this<04:23:50.699> type<04:23:51.000> of<04:23:51.180> data<04:23:51.540> encoding<04:23:52.020> scheme<04:23:52.500> is 04:23:52.729 --> 04:23:52.739 align:start position:0% this type of data encoding scheme is 04:23:52.739 --> 04:23:55.969 align:start position:0% this type of data encoding scheme is typically<04:23:53.100> used<04:23:53.699> over<04:23:54.479> serial<04:23:55.199> ports<04:23:55.680> and 04:23:55.969 --> 04:23:55.979 align:start position:0% typically used over serial ports and 04:23:55.979 --> 04:23:58.370 align:start position:0% typically used over serial ports and fairly<04:23:56.460> slow<04:23:57.060> connections 04:23:58.370 --> 04:23:58.380 align:start position:0% fairly slow connections 04:23:58.380 --> 04:24:01.729 align:start position:0% fairly slow connections I'm<04:23:59.100> mentioning<04:23:59.580> these<04:23:59.880> because<04:24:00.380> uh<04:24:01.380> they're 04:24:01.729 --> 04:24:01.739 align:start position:0% I'm mentioning these because uh they're 04:24:01.739 --> 04:24:04.429 align:start position:0% I'm mentioning these because uh they're good<04:24:01.979> to<04:24:02.160> know<04:24:02.399> but<04:24:03.300> you<04:24:03.660> won't<04:24:03.779> have<04:24:04.020> to<04:24:04.199> worry 04:24:04.429 --> 04:24:04.439 align:start position:0% good to know but you won't have to worry 04:24:04.439 --> 04:24:07.490 align:start position:0% good to know but you won't have to worry about<04:24:04.680> these<04:24:05.040> for<04:24:05.520> the<04:24:05.640> exam 04:24:07.490 --> 04:24:07.500 align:start position:0% about these for the exam 04:24:07.500 --> 04:24:09.830 align:start position:0% about these for the exam now<04:24:07.979> the<04:24:08.399> next<04:24:08.520> encoding<04:24:09.060> scheme<04:24:09.420> a<04:24:09.660> little 04:24:09.830 --> 04:24:09.840 align:start position:0% now the next encoding scheme a little 04:24:09.840 --> 04:24:11.389 align:start position:0% now the next encoding scheme a little more<04:24:10.020> popular<04:24:10.260> perhaps<04:24:10.859> is<04:24:11.160> called 04:24:11.389 --> 04:24:11.399 align:start position:0% more popular perhaps is called 04:24:11.399 --> 04:24:13.969 align:start position:0% more popular perhaps is called Manchester<04:24:12.120> encoding<04:24:12.899> this<04:24:13.560> scheme<04:24:13.859> was 04:24:13.969 --> 04:24:13.979 align:start position:0% Manchester encoding this scheme was 04:24:13.979 --> 04:24:15.710 align:start position:0% Manchester encoding this scheme was developed<04:24:14.460> in<04:24:14.640> order<04:24:14.760> to<04:24:15.000> address<04:24:15.180> some<04:24:15.600> of 04:24:15.710 --> 04:24:15.720 align:start position:0% developed in order to address some of 04:24:15.720 --> 04:24:18.469 align:start position:0% developed in order to address some of the<04:24:15.960> downfalls<04:24:16.739> that<04:24:17.399> we<04:24:17.520> saw<04:24:17.760> with<04:24:18.060> on<04:24:18.300> and 04:24:18.469 --> 04:24:18.479 align:start position:0% the downfalls that we saw with on and 04:24:18.479 --> 04:24:21.769 align:start position:0% the downfalls that we saw with on and off<04:24:18.660> keying<04:24:19.620> firstly<04:24:20.279> Manchester<04:24:21.120> encoding 04:24:21.769 --> 04:24:21.779 align:start position:0% off keying firstly Manchester encoding 04:24:21.779 --> 04:24:24.410 align:start position:0% off keying firstly Manchester encoding uses<04:24:22.080> voltage<04:24:22.560> differences<04:24:23.279> to<04:24:24.000> represent 04:24:24.410 --> 04:24:24.420 align:start position:0% uses voltage differences to represent 04:24:24.420 --> 04:24:27.410 align:start position:0% uses voltage differences to represent both<04:24:25.080> binary<04:24:25.680> digits<04:24:26.279> so<04:24:26.819> instead<04:24:27.120> of<04:24:27.239> just 04:24:27.410 --> 04:24:27.420 align:start position:0% both binary digits so instead of just 04:24:27.420 --> 04:24:30.710 align:start position:0% both binary digits so instead of just having<04:24:27.800> one<04:24:28.800> which<04:24:29.580> is<04:24:29.699> represented<04:24:30.239> by<04:24:30.479> a 04:24:30.710 --> 04:24:30.720 align:start position:0% having one which is represented by a 04:24:30.720 --> 04:24:32.570 align:start position:0% having one which is represented by a voltage<04:24:31.140> and<04:24:31.500> then<04:24:31.620> zero<04:24:32.040> which<04:24:32.160> has<04:24:32.340> no 04:24:32.570 --> 04:24:32.580 align:start position:0% voltage and then zero which has no 04:24:32.580 --> 04:24:36.050 align:start position:0% voltage and then zero which has no voltage<04:24:33.060> both<04:24:33.960> zero<04:24:34.620> and<04:24:34.800> one<04:24:34.979> have<04:24:35.640> voltages 04:24:36.050 --> 04:24:36.060 align:start position:0% voltage both zero and one have voltages 04:24:36.060 --> 04:24:39.110 align:start position:0% voltage both zero and one have voltages the<04:24:36.960> way<04:24:37.140> it<04:24:37.319> does<04:24:37.620> this<04:24:37.859> is<04:24:38.340> it<04:24:38.520> works<04:24:38.819> by 04:24:39.110 --> 04:24:39.120 align:start position:0% the way it does this is it works by 04:24:39.120 --> 04:24:41.269 align:start position:0% the way it does this is it works by assigning<04:24:39.720> the<04:24:40.020> voltage<04:24:40.380> change<04:24:40.739> from 04:24:41.269 --> 04:24:41.279 align:start position:0% assigning the voltage change from 04:24:41.279 --> 04:24:44.870 align:start position:0% assigning the voltage change from positive<04:24:41.880> to<04:24:42.840> ground 04:24:44.870 --> 04:24:44.880 align:start position:0% positive to ground 04:24:44.880 --> 04:24:48.769 align:start position:0% positive to ground or<04:24:45.540> the<04:24:45.779> binary<04:24:46.140> digit<04:24:46.620> 0<04:24:46.939> and<04:24:47.939> a<04:24:48.180> negative<04:24:48.479> to 04:24:48.769 --> 04:24:48.779 align:start position:0% or the binary digit 0 and a negative to 04:24:48.779 --> 04:24:51.950 align:start position:0% or the binary digit 0 and a negative to positive<04:24:49.199> change<04:24:49.560> equals<04:24:50.279> the<04:24:50.460> binary<04:24:50.960> digit 04:24:51.950 --> 04:24:51.960 align:start position:0% positive change equals the binary digit 04:24:51.960 --> 04:24:53.929 align:start position:0% positive change equals the binary digit one<04:24:52.319> so 04:24:53.929 --> 04:24:53.939 align:start position:0% one so 04:24:53.939 --> 04:24:57.290 align:start position:0% one so positive<04:24:54.660> to<04:24:54.840> Ground<04:24:55.020> Zero 04:24:57.290 --> 04:24:57.300 align:start position:0% positive to Ground Zero 04:24:57.300 --> 04:25:02.330 align:start position:0% positive to Ground Zero negative<04:24:58.199> or<04:24:58.920> ground<04:24:59.359> to<04:25:00.359> positive 04:25:02.330 --> 04:25:02.340 align:start position:0% negative or ground to positive 04:25:02.340 --> 04:25:04.849 align:start position:0% negative or ground to positive equals<04:25:03.000> one 04:25:04.849 --> 04:25:04.859 align:start position:0% equals one 04:25:04.859 --> 04:25:08.389 align:start position:0% equals one this<04:25:05.580> effectively<04:25:06.680> eliminates<04:25:07.680> the<04:25:07.920> issue<04:25:08.220> of 04:25:08.389 --> 04:25:08.399 align:start position:0% this effectively eliminates the issue of 04:25:08.399 --> 04:25:11.689 align:start position:0% this effectively eliminates the issue of too<04:25:08.699> many<04:25:08.939> one<04:25:09.660> bits<04:25:10.199> being<04:25:10.800> transmitted<04:25:11.520> and 04:25:11.689 --> 04:25:11.699 align:start position:0% too many one bits being transmitted and 04:25:11.699 --> 04:25:13.910 align:start position:0% too many one bits being transmitted and throwing<04:25:12.060> off<04:25:12.180> the<04:25:12.420> synchronization<04:25:13.020> as<04:25:13.800> we 04:25:13.910 --> 04:25:13.920 align:start position:0% throwing off the synchronization as we 04:25:13.920 --> 04:25:16.070 align:start position:0% throwing off the synchronization as we saw<04:25:14.160> with<04:25:14.399> on<04:25:14.640> and<04:25:14.819> off<04:25:14.939> King<04:25:15.239> which<04:25:15.540> relies<04:25:15.899> on 04:25:16.070 --> 04:25:16.080 align:start position:0% saw with on and off King which relies on 04:25:16.080 --> 04:25:17.689 align:start position:0% saw with on and off King which relies on those<04:25:16.199> one<04:25:16.380> bits<04:25:16.739> in<04:25:16.859> order<04:25:16.979> to<04:25:17.100> sync<04:25:17.399> up<04:25:17.460> the 04:25:17.689 --> 04:25:17.699 align:start position:0% those one bits in order to sync up the 04:25:17.699 --> 04:25:18.830 align:start position:0% those one bits in order to sync up the clocks 04:25:18.830 --> 04:25:18.840 align:start position:0% clocks 04:25:18.840 --> 04:25:23.510 align:start position:0% clocks okay<04:25:19.760> so<04:25:20.760> modulation<04:25:21.720> is<04:25:22.560> the<04:25:22.800> process<04:25:23.100> of 04:25:23.510 --> 04:25:23.520 align:start position:0% okay so modulation is the process of 04:25:23.520 --> 04:25:26.809 align:start position:0% okay so modulation is the process of taking<04:25:23.699> a<04:25:24.239> weaker<04:25:24.660> lower<04:25:25.439> frequency<04:25:25.979> analog 04:25:26.809 --> 04:25:26.819 align:start position:0% taking a weaker lower frequency analog 04:25:26.819 --> 04:25:29.269 align:start position:0% taking a weaker lower frequency analog signal<04:25:27.239> that<04:25:27.779> can't<04:25:28.020> travel<04:25:28.319> large<04:25:28.739> distances 04:25:29.269 --> 04:25:29.279 align:start position:0% signal that can't travel large distances 04:25:29.279 --> 04:25:32.450 align:start position:0% signal that can't travel large distances and<04:25:30.180> superimposing<04:25:31.080> the<04:25:31.260> signal<04:25:31.620> over<04:25:31.979> a 04:25:32.450 --> 04:25:32.460 align:start position:0% and superimposing the signal over a 04:25:32.460 --> 04:25:35.870 align:start position:0% and superimposing the signal over a stronger<04:25:32.880> higher<04:25:33.660> frequency<04:25:34.020> called<04:25:34.979> a 04:25:35.870 --> 04:25:35.880 align:start position:0% stronger higher frequency called a 04:25:35.880 --> 04:25:37.910 align:start position:0% stronger higher frequency called a carrier<04:25:36.300> signal 04:25:37.910 --> 04:25:37.920 align:start position:0% carrier signal 04:25:37.920 --> 04:25:41.510 align:start position:0% carrier signal the<04:25:38.520> carrier<04:25:38.939> signal<04:25:39.420> being<04:25:39.960> constant<04:25:40.680> takes 04:25:41.510 --> 04:25:41.520 align:start position:0% the carrier signal being constant takes 04:25:41.520 --> 04:25:44.990 align:start position:0% the carrier signal being constant takes on<04:25:41.939> the<04:25:42.239> attributes<04:25:42.960> of<04:25:43.739> the<04:25:44.100> analog<04:25:44.580> signal 04:25:44.990 --> 04:25:45.000 align:start position:0% on the attributes of the analog signal 04:25:45.000 --> 04:25:47.090 align:start position:0% on the attributes of the analog signal and<04:25:45.479> it's<04:25:45.659> shaped<04:25:46.080> by<04:25:46.199> either<04:25:46.380> the<04:25:46.800> phase 04:25:47.090 --> 04:25:47.100 align:start position:0% and it's shaped by either the phase 04:25:47.100 --> 04:25:50.990 align:start position:0% and it's shaped by either the phase amplitude<04:25:48.000> or<04:25:48.720> the<04:25:48.960> frequency<04:25:49.580> the<04:25:50.580> resulting 04:25:50.990 --> 04:25:51.000 align:start position:0% amplitude or the frequency the resulting 04:25:51.000 --> 04:25:54.410 align:start position:0% amplitude or the frequency the resulting signal<04:25:51.479> then<04:25:51.720> has<04:25:52.260> characteristics<04:25:53.220> of<04:25:54.120> both 04:25:54.410 --> 04:25:54.420 align:start position:0% signal then has characteristics of both 04:25:54.420 --> 04:25:56.990 align:start position:0% signal then has characteristics of both the<04:25:55.020> original<04:25:55.199> signal<04:25:55.859> and<04:25:56.399> the<04:25:56.580> carrier 04:25:56.990 --> 04:25:57.000 align:start position:0% the original signal and the carrier 04:25:57.000 --> 04:26:01.090 align:start position:0% the original signal and the carrier signal<04:25:57.359> that<04:25:58.319> process<04:25:58.800> this<04:25:59.760> is<04:26:00.180> called 04:26:01.090 --> 04:26:01.100 align:start position:0% signal that process this is called 04:26:01.100 --> 04:26:04.490 align:start position:0% signal that process this is called modulation<04:26:02.100> and<04:26:02.819> when<04:26:03.120> receiving<04:26:03.720> and<04:26:04.319> when 04:26:04.490 --> 04:26:04.500 align:start position:0% modulation and when receiving and when 04:26:04.500 --> 04:26:08.030 align:start position:0% modulation and when receiving and when the<04:26:04.680> receiving<04:26:04.920> end<04:26:05.779> decodes<04:26:06.779> the<04:26:07.020> signal<04:26:07.380> by 04:26:08.030 --> 04:26:08.040 align:start position:0% the receiving end decodes the signal by 04:26:08.040 --> 04:26:11.570 align:start position:0% the receiving end decodes the signal by separating<04:26:08.580> these<04:26:09.300> two<04:26:09.600> signals<04:26:10.680> the<04:26:11.220> carrier 04:26:11.570 --> 04:26:11.580 align:start position:0% separating these two signals the carrier 04:26:11.580 --> 04:26:14.870 align:start position:0% separating these two signals the carrier and<04:26:11.819> the<04:26:12.000> data 04:26:14.870 --> 04:26:14.880 align:start position:0% 04:26:14.880 --> 04:26:16.969 align:start position:0% the<04:26:15.479> process<04:26:15.779> is<04:26:16.080> called 04:26:16.969 --> 04:26:16.979 align:start position:0% the process is called 04:26:16.979 --> 04:26:19.550 align:start position:0% the process is called demodulation 04:26:19.550 --> 04:26:19.560 align:start position:0% demodulation 04:26:19.560 --> 04:26:25.070 align:start position:0% demodulation so<04:26:20.040> again<04:26:20.340> we<04:26:20.819> have<04:26:21.000> demodulation 04:26:25.070 --> 04:26:25.080 align:start position:0% 04:26:25.080 --> 04:26:27.290 align:start position:0% which<04:26:25.620> would<04:26:25.859> basically 04:26:27.290 --> 04:26:27.300 align:start position:0% which would basically 04:26:27.300 --> 04:26:29.809 align:start position:0% which would basically take<04:26:27.720> these<04:26:28.020> away<04:26:28.199> from<04:26:28.439> one<04:26:28.620> another<04:26:28.819> and 04:26:29.809 --> 04:26:29.819 align:start position:0% take these away from one another and 04:26:29.819 --> 04:26:35.450 align:start position:0% take these away from one another and modulation<04:26:30.420> which<04:26:31.319> puts<04:26:31.739> them<04:26:31.859> together 04:26:35.450 --> 04:26:35.460 align:start position:0% 04:26:35.460 --> 04:26:37.849 align:start position:0% devices<04:26:36.239> that<04:26:36.659> perform<04:26:36.960> this<04:26:37.380> operation 04:26:37.849 --> 04:26:37.859 align:start position:0% devices that perform this operation 04:26:37.859 --> 04:26:40.189 align:start position:0% devices that perform this operation you've<04:26:38.460> probably<04:26:38.640> heard<04:26:38.880> of<04:26:39.060> before<04:26:39.300> they're 04:26:40.189 --> 04:26:40.199 align:start position:0% you've probably heard of before they're 04:26:40.199 --> 04:26:42.590 align:start position:0% you've probably heard of before they're called<04:26:40.500> modems 04:26:42.590 --> 04:26:42.600 align:start position:0% called modems 04:26:42.600 --> 04:26:46.330 align:start position:0% called modems and<04:26:43.260> a<04:26:43.439> modem<04:26:43.800> is<04:26:44.340> known<04:26:44.580> for<04:26:44.880> its<04:26:45.120> ability<04:26:45.359> to 04:26:46.330 --> 04:26:46.340 align:start position:0% and a modem is known for its ability to 04:26:46.340 --> 04:26:51.349 align:start position:0% and a modem is known for its ability to modulate<04:26:47.359> and<04:26:48.739> demodulate<04:26:49.739> hence<04:26:50.340> the<04:26:50.520> name 04:26:51.349 --> 04:26:51.359 align:start position:0% modulate and demodulate hence the name 04:26:51.359 --> 04:26:54.290 align:start position:0% modulate and demodulate hence the name a<04:26:51.840> modem<04:26:52.140> is<04:26:52.319> in<04:26:52.500> effect<04:26:52.680> a<04:26:53.220> type<04:26:53.399> of<04:26:53.580> codec 04:26:54.290 --> 04:26:54.300 align:start position:0% a modem is in effect a type of codec 04:26:54.300 --> 04:26:57.550 align:start position:0% a modem is in effect a type of codec which<04:26:55.199> is<04:26:55.439> a<04:26:55.859> software<04:26:56.220> or<04:26:56.520> Hardware<04:26:56.760> that 04:26:57.550 --> 04:26:57.560 align:start position:0% which is a software or Hardware that 04:26:57.560 --> 04:27:04.010 align:start position:0% which is a software or Hardware that translates<04:26:58.560> digital 04:27:04.010 --> 04:27:04.020 align:start position:0% 04:27:04.020 --> 04:27:08.689 align:start position:0% to<04:27:04.460> analog<04:27:05.460> formats<04:27:06.659> and<04:27:07.080> back<04:27:07.399> this<04:27:08.399> is<04:27:08.520> an 04:27:08.689 --> 04:27:08.699 align:start position:0% to analog formats and back this is an 04:27:08.699 --> 04:27:11.710 align:start position:0% to analog formats and back this is an important<04:27:09.000> thing<04:27:09.180> to<04:27:09.359> know<04:27:09.479> for<04:27:09.659> the<04:27:09.840> exam<04:27:10.680> a 04:27:11.710 --> 04:27:11.720 align:start position:0% important thing to know for the exam a 04:27:11.720 --> 04:27:13.490 align:start position:0% important thing to know for the exam a DAC 04:27:13.490 --> 04:27:13.500 align:start position:0% DAC 04:27:13.500 --> 04:27:17.090 align:start position:0% DAC is<04:27:14.220> a<04:27:14.640> digital<04:27:15.000> to<04:27:15.239> analog<04:27:15.720> codec 04:27:17.090 --> 04:27:17.100 align:start position:0% is a digital to analog codec 04:27:17.100 --> 04:27:18.729 align:start position:0% is a digital to analog codec and<04:27:17.819> in 04:27:18.729 --> 04:27:18.739 align:start position:0% and in 04:27:18.739 --> 04:27:22.729 align:start position:0% and in ADC<04:27:19.739> as<04:27:20.699> you<04:27:20.819> guessed<04:27:21.120> it<04:27:21.180> is<04:27:21.540> an<04:27:21.779> analog<04:27:22.260> to 04:27:22.729 --> 04:27:22.739 align:start position:0% ADC as you guessed it is an analog to 04:27:22.739 --> 04:27:25.910 align:start position:0% ADC as you guessed it is an analog to digital<04:27:23.100> codec 04:27:25.910 --> 04:27:25.920 align:start position:0% 04:27:25.920 --> 04:27:29.149 align:start position:0% both<04:27:26.460> of<04:27:26.699> these<04:27:27.000> exist<04:27:27.540> in<04:27:28.140> a<04:27:28.319> modem 04:27:29.149 --> 04:27:29.159 align:start position:0% both of these exist in a modem 04:27:29.159 --> 04:27:31.969 align:start position:0% both of these exist in a modem now<04:27:29.520> this<04:27:29.760> is<04:27:29.880> it<04:27:30.060> in<04:27:30.300> analog<04:27:30.899> terms<04:27:31.380> but 04:27:31.969 --> 04:27:31.979 align:start position:0% now this is it in analog terms but 04:27:31.979 --> 04:27:35.330 align:start position:0% now this is it in analog terms but digital<04:27:32.939> modulation<04:27:33.600> is<04:27:34.439> also<04:27:34.800> required 04:27:35.330 --> 04:27:35.340 align:start position:0% digital modulation is also required 04:27:35.340 --> 04:27:38.030 align:start position:0% digital modulation is also required which<04:27:35.939> allows<04:27:36.359> the<04:27:36.540> digital<04:27:36.899> signal<04:27:37.500> to 04:27:38.030 --> 04:27:38.040 align:start position:0% which allows the digital signal to 04:27:38.040 --> 04:27:41.210 align:start position:0% which allows the digital signal to travel<04:27:38.279> along<04:27:38.699> distances<04:27:39.359> and<04:27:40.319> demodulation 04:27:41.210 --> 04:27:41.220 align:start position:0% travel along distances and demodulation 04:27:41.220 --> 04:27:44.870 align:start position:0% travel along distances and demodulation is<04:27:41.880> the<04:27:42.060> representation<04:27:42.600> of<04:27:43.080> Digital<04:27:43.500> Data<04:27:44.220> in 04:27:44.870 --> 04:27:44.880 align:start position:0% is the representation of Digital Data in 04:27:44.880 --> 04:27:47.570 align:start position:0% is the representation of Digital Data in an<04:27:45.120> analog<04:27:45.600> format<04:27:46.140> for<04:27:46.500> transmission<04:27:46.859> over 04:27:47.570 --> 04:27:47.580 align:start position:0% an analog format for transmission over 04:27:47.580 --> 04:27:50.269 align:start position:0% an analog format for transmission over those<04:27:47.880> longer<04:27:48.300> distances<04:27:48.779> so<04:27:49.560> the<04:27:49.800> analog 04:27:50.269 --> 04:27:50.279 align:start position:0% those longer distances so the analog 04:27:50.279 --> 04:27:53.750 align:start position:0% those longer distances so the analog signal<04:27:50.699> has<04:27:51.239> a<04:27:51.479> characteristic<04:27:52.399> changed<04:27:53.399> to 04:27:53.750 --> 04:27:53.760 align:start position:0% signal has a characteristic changed to 04:27:53.760 --> 04:27:56.570 align:start position:0% signal has a characteristic changed to signify<04:27:54.300> the<04:27:54.659> difference<04:27:54.920> between<04:27:55.920> logical 04:27:56.570 --> 04:27:56.580 align:start position:0% signify the difference between logical 04:27:56.580 --> 04:27:59.689 align:start position:0% signify the difference between logical states<04:27:56.880> of<04:27:57.359> the<04:27:57.659> digital<04:27:58.020> signal<04:27:58.500> this<04:27:59.279> is<04:27:59.399> a 04:27:59.689 --> 04:27:59.699 align:start position:0% states of the digital signal this is a 04:27:59.699 --> 04:28:02.269 align:start position:0% states of the digital signal this is a fairly<04:28:00.060> simple<04:28:00.300> as<04:28:00.659> digital<04:28:01.199> signals<04:28:01.920> again 04:28:02.269 --> 04:28:02.279 align:start position:0% fairly simple as digital signals again 04:28:02.279 --> 04:28:06.229 align:start position:0% fairly simple as digital signals again only<04:28:02.699> have<04:28:03.000> two<04:28:03.300> states<04:28:03.600> one<04:28:04.560> and<04:28:05.100> zero<04:28:05.580> and<04:28:06.000> so 04:28:06.229 --> 04:28:06.239 align:start position:0% only have two states one and zero and so 04:28:06.239 --> 04:28:09.410 align:start position:0% only have two states one and zero and so the<04:28:06.600> analog<04:28:07.080> waveform<04:28:07.800> needs<04:28:08.760> only<04:28:09.000> be 04:28:09.410 --> 04:28:09.420 align:start position:0% the analog waveform needs only be 04:28:09.420 --> 04:28:13.670 align:start position:0% the analog waveform needs only be changed<04:28:10.080> or<04:28:10.439> modulated<04:28:11.100> in<04:28:11.880> one<04:28:12.120> way<04:28:12.500> such<04:28:13.500> as 04:28:13.670 --> 04:28:13.680 align:start position:0% changed or modulated in one way such as 04:28:13.680 --> 04:28:15.889 align:start position:0% changed or modulated in one way such as the<04:28:13.979> graphic<04:28:14.340> here<04:28:14.640> the<04:28:15.239> frequency<04:28:15.600> is 04:28:15.889 --> 04:28:15.899 align:start position:0% the graphic here the frequency is 04:28:15.899 --> 04:28:17.570 align:start position:0% the graphic here the frequency is changed<04:28:16.439> where<04:28:16.680> the<04:28:16.920> higher<04:28:17.220> frequency 04:28:17.570 --> 04:28:17.580 align:start position:0% changed where the higher frequency 04:28:17.580 --> 04:28:20.450 align:start position:0% changed where the higher frequency represents<04:28:18.420> one<04:28:19.020> bits<04:28:19.500> and<04:28:20.159> the<04:28:20.340> lower 04:28:20.450 --> 04:28:20.460 align:start position:0% represents one bits and the lower 04:28:20.460 --> 04:28:24.110 align:start position:0% represents one bits and the lower frequency<04:28:21.140> represents<04:28:22.140> zero<04:28:22.920> bits<04:28:23.279> in<04:28:23.939> this 04:28:24.110 --> 04:28:24.120 align:start position:0% frequency represents zero bits in this 04:28:24.120 --> 04:28:27.649 align:start position:0% frequency represents zero bits in this way<04:28:24.359> I<04:28:24.960> can<04:28:25.080> convert<04:28:25.620> this<04:28:26.520> Digital<04:28:27.120> Signal 04:28:27.649 --> 04:28:27.659 align:start position:0% way I can convert this Digital Signal 04:28:27.659 --> 04:28:30.530 align:start position:0% way I can convert this Digital Signal into<04:28:28.319> an<04:28:28.620> analog<04:28:28.920> one<04:28:29.100> 1<04:28:29.520> in<04:28:30.060> order<04:28:30.239> to 04:28:30.530 --> 04:28:30.540 align:start position:0% into an analog one 1 in order to 04:28:30.540 --> 04:28:33.349 align:start position:0% into an analog one 1 in order to transfer<04:28:31.080> transfer<04:28:31.739> transmit<04:28:32.340> it<04:28:32.460> over<04:28:32.640> a 04:28:33.349 --> 04:28:33.359 align:start position:0% transfer transfer transmit it over a 04:28:33.359 --> 04:28:35.510 align:start position:0% transfer transfer transmit it over a long<04:28:33.540> distance<04:28:33.779> now<04:28:34.560> there<04:28:34.979> are<04:28:35.159> various 04:28:35.510 --> 04:28:35.520 align:start position:0% long distance now there are various 04:28:35.520 --> 04:28:38.510 align:start position:0% long distance now there are various methods<04:28:36.180> to<04:28:36.659> modulate<04:28:37.199> the<04:28:37.739> digital<04:28:38.100> signal 04:28:38.510 --> 04:28:38.520 align:start position:0% methods to modulate the digital signal 04:28:38.520 --> 04:28:40.849 align:start position:0% methods to modulate the digital signal depending<04:28:39.000> on<04:28:39.239> what<04:28:39.659> part<04:28:39.960> of<04:28:40.260> the<04:28:40.439> analog 04:28:40.849 --> 04:28:40.859 align:start position:0% depending on what part of the analog 04:28:40.859 --> 04:28:43.849 align:start position:0% depending on what part of the analog waveform<04:28:41.520> is<04:28:42.180> being<04:28:42.420> changed<04:28:42.960> the<04:28:43.500> first<04:28:43.620> one 04:28:43.849 --> 04:28:43.859 align:start position:0% waveform is being changed the first one 04:28:43.859 --> 04:28:47.809 align:start position:0% waveform is being changed the first one is<04:28:44.040> called<04:28:44.279> ask<04:28:44.960> or<04:28:45.960> amplitude<04:28:46.620> shift<04:28:47.279> key 04:28:47.809 --> 04:28:47.819 align:start position:0% is called ask or amplitude shift key 04:28:47.819 --> 04:28:51.590 align:start position:0% is called ask or amplitude shift key modulation<04:28:48.800> here<04:28:49.800> only<04:28:50.399> the<04:28:50.880> amplitude<04:28:51.479> of 04:28:51.590 --> 04:28:51.600 align:start position:0% modulation here only the amplitude of 04:28:51.600 --> 04:28:54.229 align:start position:0% modulation here only the amplitude of the<04:28:51.779> wave<04:28:51.960> is<04:28:52.199> modulated<04:28:52.739> and<04:28:53.640> remember<04:28:53.760> the 04:28:54.229 --> 04:28:54.239 align:start position:0% the wave is modulated and remember the 04:28:54.239 --> 04:28:59.090 align:start position:0% the wave is modulated and remember the amplitude<04:28:54.779> is<04:28:55.620> the<04:28:55.859> distance 04:28:59.090 --> 04:28:59.100 align:start position:0% 04:28:59.100 --> 04:29:01.790 align:start position:0% between<04:28:59.760> a<04:29:00.359> peak<04:29:00.659> or<04:29:00.840> a<04:29:01.020> trough<04:29:01.260> in<04:29:01.620> the 04:29:01.790 --> 04:29:01.800 align:start position:0% between a peak or a trough in the 04:29:01.800 --> 04:29:05.269 align:start position:0% between a peak or a trough in the midpoint 04:29:05.269 --> 04:29:05.279 align:start position:0% 04:29:05.279 --> 04:29:07.729 align:start position:0% and<04:29:05.880> the<04:29:06.000> result<04:29:06.180> of<04:29:06.420> this<04:29:06.600> can<04:29:06.840> only<04:29:07.020> be<04:29:07.319> one 04:29:07.729 --> 04:29:07.739 align:start position:0% and the result of this can only be one 04:29:07.739 --> 04:29:10.849 align:start position:0% and the result of this can only be one or<04:29:08.520> zero<04:29:09.359> the<04:29:09.960> next<04:29:10.020> method<04:29:10.439> is<04:29:10.620> called 04:29:10.849 --> 04:29:10.859 align:start position:0% or zero the next method is called 04:29:10.859 --> 04:29:13.969 align:start position:0% or zero the next method is called frequency<04:29:11.520> shift<04:29:12.120> key<04:29:12.300> here<04:29:13.199> the<04:29:13.560> frequency 04:29:13.969 --> 04:29:13.979 align:start position:0% frequency shift key here the frequency 04:29:13.979 --> 04:29:17.149 align:start position:0% frequency shift key here the frequency is<04:29:14.279> modulated<04:29:14.819> to<04:29:15.420> only<04:29:15.600> represent<04:29:16.140> one<04:29:16.739> or 04:29:17.149 --> 04:29:17.159 align:start position:0% is modulated to only represent one or 04:29:17.159 --> 04:29:19.490 align:start position:0% is modulated to only represent one or zero<04:29:17.580> as<04:29:17.880> opposed<04:29:18.180> to<04:29:18.239> the<04:29:18.479> amplitude<04:29:19.080> and 04:29:19.490 --> 04:29:19.500 align:start position:0% zero as opposed to the amplitude and 04:29:19.500 --> 04:29:22.670 align:start position:0% zero as opposed to the amplitude and remember<04:29:19.680> the<04:29:19.979> frequency<04:29:20.460> is<04:29:21.239> the<04:29:21.540> amount 04:29:22.670 --> 04:29:22.680 align:start position:0% remember the frequency is the amount 04:29:22.680 --> 04:29:25.429 align:start position:0% remember the frequency is the amount times<04:29:23.100> we<04:29:23.460> have<04:29:23.580> this<04:29:23.819> wave<04:29:24.180> over<04:29:24.840> a<04:29:25.260> certain 04:29:25.429 --> 04:29:25.439 align:start position:0% times we have this wave over a certain 04:29:25.439 --> 04:29:28.189 align:start position:0% times we have this wave over a certain period<04:29:25.920> of<04:29:26.220> time 04:29:28.189 --> 04:29:28.199 align:start position:0% period of time 04:29:28.199 --> 04:29:30.110 align:start position:0% period of time we<04:29:28.620> also<04:29:28.800> have<04:29:28.920> something<04:29:29.100> called<04:29:29.399> binary 04:29:30.110 --> 04:29:30.120 align:start position:0% we also have something called binary 04:29:30.120 --> 04:29:33.950 align:start position:0% we also have something called binary phase<04:29:30.659> shift<04:29:31.199> key<04:29:31.439> in<04:29:32.159> which<04:29:32.340> case<04:29:32.760> the<04:29:33.600> phase 04:29:33.950 --> 04:29:33.960 align:start position:0% phase shift key in which case the phase 04:29:33.960 --> 04:29:36.349 align:start position:0% phase shift key in which case the phase of<04:29:34.199> the<04:29:34.380> wave<04:29:34.560> is<04:29:34.859> changed<04:29:35.340> and<04:29:35.760> remember<04:29:35.939> the 04:29:36.349 --> 04:29:36.359 align:start position:0% of the wave is changed and remember the 04:29:36.359 --> 04:29:38.990 align:start position:0% of the wave is changed and remember the phase<04:29:36.659> would<04:29:37.319> be<04:29:37.439> if<04:29:37.620> I<04:29:37.800> have<04:29:38.040> 2<04:29:38.340> next<04:29:38.640> to<04:29:38.819> each 04:29:38.990 --> 04:29:39.000 align:start position:0% phase would be if I have 2 next to each 04:29:39.000 --> 04:29:41.389 align:start position:0% phase would be if I have 2 next to each other<04:29:39.120> the<04:29:39.779> difference<04:29:39.960> between<04:29:40.439> those 04:29:41.389 --> 04:29:41.399 align:start position:0% other the difference between those 04:29:41.399 --> 04:29:44.269 align:start position:0% other the difference between those and<04:29:41.880> then<04:29:42.000> I<04:29:42.180> have<04:29:42.420> quadrature<04:29:43.380> phase<04:29:43.680> shift 04:29:44.269 --> 04:29:44.279 align:start position:0% and then I have quadrature phase shift 04:29:44.279 --> 04:29:47.090 align:start position:0% and then I have quadrature phase shift keying<04:29:45.000> here<04:29:45.600> the<04:29:45.960> phase<04:29:46.140> is<04:29:46.380> changed<04:29:46.739> as<04:29:46.920> well 04:29:47.090 --> 04:29:47.100 align:start position:0% keying here the phase is changed as well 04:29:47.100 --> 04:29:49.849 align:start position:0% keying here the phase is changed as well but<04:29:47.640> we<04:29:47.880> can<04:29:48.000> actually<04:29:48.180> have<04:29:48.779> two<04:29:49.439> logical 04:29:49.849 --> 04:29:49.859 align:start position:0% but we can actually have two logical 04:29:49.859 --> 04:29:51.410 align:start position:0% but we can actually have two logical States<04:29:50.100> at<04:29:50.399> a<04:29:50.580> time 04:29:51.410 --> 04:29:51.420 align:start position:0% States at a time 04:29:51.420 --> 04:29:55.130 align:start position:0% States at a time for<04:29:51.960> instance<04:29:52.199> zero<04:29:52.920> zero<04:29:53.279> zero<04:29:54.000> one<04:29:54.239> one<04:29:54.600> zero 04:29:55.130 --> 04:29:55.140 align:start position:0% for instance zero zero zero one one zero 04:29:55.140 --> 04:29:57.830 align:start position:0% for instance zero zero zero one one zero or<04:29:55.439> one<04:29:55.620> one<04:29:55.859> this<04:29:56.819> method<04:29:57.180> actually<04:29:57.420> allows 04:29:57.830 --> 04:29:57.840 align:start position:0% or one one this method actually allows 04:29:57.840 --> 04:30:02.149 align:start position:0% or one one this method actually allows for<04:29:58.080> data<04:29:58.560> uh<04:29:59.460> to<04:30:00.000> be<04:30:00.300> more<04:30:00.720> secure<04:30:01.380> when<04:30:01.979> it's 04:30:02.149 --> 04:30:02.159 align:start position:0% for data uh to be more secure when it's 04:30:02.159 --> 04:30:04.429 align:start position:0% for data uh to be more secure when it's transmitted<04:30:02.880> so<04:30:03.300> this<04:30:03.479> is<04:30:03.659> a<04:30:03.899> more<04:30:04.020> secure 04:30:04.429 --> 04:30:04.439 align:start position:0% transmitted so this is a more secure 04:30:04.439 --> 04:30:06.530 align:start position:0% transmitted so this is a more secure method 04:30:06.530 --> 04:30:06.540 align:start position:0% method 04:30:06.540 --> 04:30:08.170 align:start position:0% method finally<04:30:07.140> there's<04:30:07.380> something<04:30:07.620> called 04:30:08.170 --> 04:30:08.180 align:start position:0% finally there's something called 04:30:08.180 --> 04:30:12.290 align:start position:0% finally there's something called quadrature<04:30:09.439> amplitude<04:30:10.439> modulation<04:30:11.100> and<04:30:12.060> in 04:30:12.290 --> 04:30:12.300 align:start position:0% quadrature amplitude modulation and in 04:30:12.300 --> 04:30:14.630 align:start position:0% quadrature amplitude modulation and in this<04:30:12.420> case<04:30:12.600> I<04:30:12.960> can<04:30:13.080> also<04:30:13.380> have<04:30:13.620> more<04:30:14.159> than<04:30:14.340> two 04:30:14.630 --> 04:30:14.640 align:start position:0% this case I can also have more than two 04:30:14.640 --> 04:30:17.269 align:start position:0% this case I can also have more than two states<04:30:14.939> at<04:30:15.359> a<04:30:15.479> time<04:30:15.659> but<04:30:16.439> what<04:30:16.620> I'm<04:30:16.800> shifting 04:30:17.269 --> 04:30:17.279 align:start position:0% states at a time but what I'm shifting 04:30:17.279 --> 04:30:20.210 align:start position:0% states at a time but what I'm shifting here<04:30:17.520> instead<04:30:18.000> of<04:30:18.180> the<04:30:18.659> phase<04:30:19.020> only<04:30:19.380> is<04:30:19.979> I'm 04:30:20.210 --> 04:30:20.220 align:start position:0% here instead of the phase only is I'm 04:30:20.220 --> 04:30:23.570 align:start position:0% here instead of the phase only is I'm also<04:30:20.640> Shifting<04:30:21.180> the<04:30:21.720> amplitude<04:30:22.380> and<04:30:23.159> so<04:30:23.279> these 04:30:23.570 --> 04:30:23.580 align:start position:0% also Shifting the amplitude and so these 04:30:23.580 --> 04:30:25.670 align:start position:0% also Shifting the amplitude and so these are<04:30:23.699> both<04:30:23.939> combined<04:30:24.659> into<04:30:25.020> one<04:30:25.380> different 04:30:25.670 --> 04:30:25.680 align:start position:0% are both combined into one different 04:30:25.680 --> 04:30:28.330 align:start position:0% are both combined into one different modulating<04:30:26.340> wave<04:30:26.760> now<04:30:27.479> in<04:30:27.659> order<04:30:27.840> to 04:30:28.330 --> 04:30:28.340 align:start position:0% modulating wave now in order to 04:30:28.340 --> 04:30:30.769 align:start position:0% modulating wave now in order to demodulate<04:30:29.340> these<04:30:29.640> once<04:30:30.060> I've<04:30:30.180> modulated 04:30:30.769 --> 04:30:30.779 align:start position:0% demodulate these once I've modulated 04:30:30.779 --> 04:30:31.670 align:start position:0% demodulate these once I've modulated them 04:30:31.670 --> 04:30:31.680 align:start position:0% them 04:30:31.680 --> 04:30:33.889 align:start position:0% them there<04:30:32.460> must<04:30:32.699> be<04:30:32.880> a<04:30:33.180> reference<04:30:33.540> to 04:30:33.889 --> 04:30:33.899 align:start position:0% there must be a reference to 04:30:33.899 --> 04:30:35.750 align:start position:0% there must be a reference to differentiate<04:30:34.560> the<04:30:34.800> data<04:30:35.100> from<04:30:35.279> the<04:30:35.460> rest<04:30:35.580> of 04:30:35.750 --> 04:30:35.760 align:start position:0% differentiate the data from the rest of 04:30:35.760 --> 04:30:38.389 align:start position:0% differentiate the data from the rest of the<04:30:35.880> signal<04:30:36.659> now<04:30:37.140> there<04:30:37.439> are<04:30:37.620> two<04:30:37.979> digital 04:30:38.389 --> 04:30:38.399 align:start position:0% the signal now there are two digital 04:30:38.399 --> 04:30:40.550 align:start position:0% the signal now there are two digital signal<04:30:39.060> reference<04:30:39.479> methods<04:30:40.020> that<04:30:40.260> can<04:30:40.380> be 04:30:40.550 --> 04:30:40.560 align:start position:0% signal reference methods that can be 04:30:40.560 --> 04:30:42.830 align:start position:0% signal reference methods that can be used<04:30:40.859> the<04:30:41.699> first<04:30:41.880> reference<04:30:42.239> method<04:30:42.659> is 04:30:42.830 --> 04:30:42.840 align:start position:0% used the first reference method is 04:30:42.840 --> 04:30:45.830 align:start position:0% used the first reference method is called<04:30:43.279> differential<04:30:44.279> demodulation 04:30:45.830 --> 04:30:45.840 align:start position:0% called differential demodulation 04:30:45.840 --> 04:30:48.950 align:start position:0% called differential demodulation this<04:30:46.380> takes<04:30:46.680> the<04:30:47.159> modulated<04:30:47.819> and<04:30:48.779> the 04:30:48.950 --> 04:30:48.960 align:start position:0% this takes the modulated and the 04:30:48.960 --> 04:30:51.110 align:start position:0% this takes the modulated and the demodulated<04:30:49.739> signals 04:30:51.110 --> 04:30:51.120 align:start position:0% demodulated signals 04:30:51.120 --> 04:30:54.110 align:start position:0% demodulated signals and<04:30:51.659> Compares<04:30:52.199> them<04:30:52.859> the<04:30:53.399> output<04:30:53.760> then 04:30:54.110 --> 04:30:54.120 align:start position:0% and Compares them the output then 04:30:54.120 --> 04:30:57.769 align:start position:0% and Compares them the output then becomes<04:30:54.800> one<04:30:55.800> mod<04:30:56.279> one<04:30:56.699> signal<04:30:57.120> which<04:30:57.359> is<04:30:57.540> the 04:30:57.769 --> 04:30:57.779 align:start position:0% becomes one mod one signal which is the 04:30:57.779 --> 04:30:58.849 align:start position:0% becomes one mod one signal which is the data 04:30:58.849 --> 04:30:58.859 align:start position:0% data 04:30:58.859 --> 04:31:01.130 align:start position:0% data there's<04:30:59.520> also<04:30:59.880> something<04:31:00.180> called<04:31:00.600> a 04:31:01.130 --> 04:31:01.140 align:start position:0% there's also something called a 04:31:01.140 --> 04:31:03.590 align:start position:0% there's also something called a single-ended<04:31:01.920> this<04:31:02.699> method<04:31:03.060> instead<04:31:03.479> of 04:31:03.590 --> 04:31:03.600 align:start position:0% single-ended this method instead of 04:31:03.600 --> 04:31:06.649 align:start position:0% single-ended this method instead of using<04:31:04.100> two<04:31:05.100> different<04:31:05.340> the<04:31:05.819> modulated<04:31:06.479> and 04:31:06.649 --> 04:31:06.659 align:start position:0% using two different the modulated and 04:31:06.659 --> 04:31:09.830 align:start position:0% using two different the modulated and the<04:31:06.840> demodulated<04:31:07.439> singles<04:31:07.920> signals<04:31:08.819> uses<04:31:09.540> the 04:31:09.830 --> 04:31:09.840 align:start position:0% the demodulated singles signals uses the 04:31:09.840 --> 04:31:12.229 align:start position:0% the demodulated singles signals uses the ground<04:31:10.080> as<04:31:10.560> a<04:31:10.800> reference<04:31:11.100> point<04:31:11.340> and<04:31:12.060> the 04:31:12.229 --> 04:31:12.239 align:start position:0% ground as a reference point and the 04:31:12.239 --> 04:31:14.510 align:start position:0% ground as a reference point and the resultant<04:31:12.659> information<04:31:13.020> then<04:31:13.739> becomes<04:31:14.340> the 04:31:14.510 --> 04:31:14.520 align:start position:0% resultant information then becomes the 04:31:14.520 --> 04:31:16.490 align:start position:0% resultant information then becomes the data<04:31:14.880> now<04:31:15.479> again<04:31:15.659> if<04:31:15.899> this<04:31:16.080> is<04:31:16.199> a<04:31:16.380> little 04:31:16.490 --> 04:31:16.500 align:start position:0% data now again if this is a little 04:31:16.500 --> 04:31:18.469 align:start position:0% data now again if this is a little confusing<04:31:17.040> don't<04:31:17.460> worry<04:31:17.640> about<04:31:17.880> it<04:31:18.060> it's<04:31:18.180> not 04:31:18.469 --> 04:31:18.479 align:start position:0% confusing don't worry about it it's not 04:31:18.479 --> 04:31:20.929 align:start position:0% confusing don't worry about it it's not going<04:31:18.659> to<04:31:18.779> come<04:31:18.899> up<04:31:19.020> on<04:31:19.260> the<04:31:19.439> exam<04:31:19.800> I<04:31:20.640> just<04:31:20.760> want 04:31:20.929 --> 04:31:20.939 align:start position:0% going to come up on the exam I just want 04:31:20.939 --> 04:31:23.090 align:start position:0% going to come up on the exam I just want to<04:31:21.060> cover<04:31:21.239> this<04:31:21.540> to<04:31:21.720> give<04:31:21.899> you<04:31:22.020> a<04:31:22.319> broad<04:31:22.500> basis 04:31:23.090 --> 04:31:23.100 align:start position:0% to cover this to give you a broad basis 04:31:23.100 --> 04:31:26.570 align:start position:0% to cover this to give you a broad basis outline<04:31:23.580> of<04:31:24.060> what<04:31:24.239> we're<04:31:24.420> talking<04:31:24.600> about<04:31:24.899> here 04:31:26.570 --> 04:31:26.580 align:start position:0% outline of what we're talking about here 04:31:26.580 --> 04:31:28.790 align:start position:0% outline of what we're talking about here now<04:31:27.120> while<04:31:27.359> there<04:31:27.600> is<04:31:27.779> very<04:31:28.020> good<04:31:28.260> possibility 04:31:28.790 --> 04:31:28.800 align:start position:0% now while there is very good possibility 04:31:28.800 --> 04:31:30.050 align:start position:0% now while there is very good possibility that<04:31:29.040> you've<04:31:29.159> probably<04:31:29.340> heard<04:31:29.580> of<04:31:29.760> some<04:31:29.939> of 04:31:30.050 --> 04:31:30.060 align:start position:0% that you've probably heard of some of 04:31:30.060 --> 04:31:31.729 align:start position:0% that you've probably heard of some of these<04:31:30.239> data<04:31:30.600> units<04:31:30.840> I'm<04:31:31.020> about<04:31:31.140> to<04:31:31.319> mention<04:31:31.439> at 04:31:31.729 --> 04:31:31.739 align:start position:0% these data units I'm about to mention at 04:31:31.739 --> 04:31:33.349 align:start position:0% these data units I'm about to mention at one<04:31:31.979> time<04:31:32.100> or<04:31:32.220> another<04:31:32.399> it's<04:31:33.120> really 04:31:33.349 --> 04:31:33.359 align:start position:0% one time or another it's really 04:31:33.359 --> 04:31:34.610 align:start position:0% one time or another it's really important<04:31:33.720> that<04:31:33.960> you<04:31:34.199> really<04:31:34.319> understand 04:31:34.610 --> 04:31:34.620 align:start position:0% important that you really understand 04:31:34.620 --> 04:31:37.490 align:start position:0% important that you really understand them<04:31:35.100> in<04:31:35.460> their<04:31:35.699> actual<04:31:36.060> quantities<04:31:36.659> now 04:31:37.490 --> 04:31:37.500 align:start position:0% them in their actual quantities now 04:31:37.500 --> 04:31:39.410 align:start position:0% them in their actual quantities now originally<04:31:37.920> before<04:31:38.279> computers<04:31:39.060> became 04:31:39.410 --> 04:31:39.420 align:start position:0% originally before computers became 04:31:39.420 --> 04:31:41.750 align:start position:0% originally before computers became household<04:31:39.899> items<04:31:40.500> and<04:31:41.100> now<04:31:41.340> nearly 04:31:41.750 --> 04:31:41.760 align:start position:0% household items and now nearly 04:31:41.760 --> 04:31:44.149 align:start position:0% household items and now nearly ubiquitous<04:31:42.420> computer<04:31:43.080> Engineers<04:31:43.620> came<04:31:43.979> up 04:31:44.149 --> 04:31:44.159 align:start position:0% ubiquitous computer Engineers came up 04:31:44.159 --> 04:31:46.429 align:start position:0% ubiquitous computer Engineers came up with<04:31:44.460> these<04:31:44.819> measurements<04:31:45.239> of<04:31:45.420> data<04:31:45.779> and<04:31:46.260> it 04:31:46.429 --> 04:31:46.439 align:start position:0% with these measurements of data and it 04:31:46.439 --> 04:31:48.530 align:start position:0% with these measurements of data and it was<04:31:46.620> pretty<04:31:46.979> straightforward<04:31:47.819> as<04:31:48.359> we've 04:31:48.530 --> 04:31:48.540 align:start position:0% was pretty straightforward as we've 04:31:48.540 --> 04:31:50.210 align:start position:0% was pretty straightforward as we've mentioned<04:31:48.779> before<04:31:48.960> in<04:31:49.319> computer<04:31:49.500> systems<04:31:50.100> and 04:31:50.210 --> 04:31:50.220 align:start position:0% mentioned before in computer systems and 04:31:50.220 --> 04:31:53.269 align:start position:0% mentioned before in computer systems and networking<04:31:50.779> data<04:31:51.779> is<04:31:51.899> stored<04:31:52.319> in<04:31:52.800> binary 04:31:53.269 --> 04:31:53.279 align:start position:0% networking data is stored in binary 04:31:53.279 --> 04:31:56.809 align:start position:0% networking data is stored in binary digits<04:31:53.880> or<04:31:54.359> bits<04:31:54.840> and<04:31:55.560> a<04:31:55.680> single<04:31:55.979> bit<04:31:56.159> is 04:31:56.809 --> 04:31:56.819 align:start position:0% digits or bits and a single bit is 04:31:56.819 --> 04:32:00.110 align:start position:0% digits or bits and a single bit is either<04:31:57.060> a<04:31:57.300> zero<04:31:57.840> or<04:31:58.500> a<04:31:58.680> one<04:31:58.859> this<04:31:59.640> is<04:31:59.760> the<04:32:00.000> most 04:32:00.110 --> 04:32:00.120 align:start position:0% either a zero or a one this is the most 04:32:00.120 --> 04:32:02.929 align:start position:0% either a zero or a one this is the most basic<04:32:00.600> form<04:32:00.779> of<04:32:01.020> measurement<04:32:01.439> zero<04:32:02.340> one<04:32:02.520> being 04:32:02.929 --> 04:32:02.939 align:start position:0% basic form of measurement zero one being 04:32:02.939 --> 04:32:05.510 align:start position:0% basic form of measurement zero one being no<04:32:03.659> power 04:32:05.510 --> 04:32:05.520 align:start position:0% no power 04:32:05.520 --> 04:32:09.830 align:start position:0% no power or<04:32:06.420> power 04:32:09.830 --> 04:32:09.840 align:start position:0% 04:32:09.840 --> 04:32:12.229 align:start position:0% a<04:32:10.620> lesser-known<04:32:11.040> term<04:32:11.340> but<04:32:11.819> still<04:32:12.000> cool 04:32:12.229 --> 04:32:12.239 align:start position:0% a lesser-known term but still cool 04:32:12.239 --> 04:32:14.570 align:start position:0% a lesser-known term but still cool nonetheless<04:32:12.779> is<04:32:13.560> that<04:32:13.800> two<04:32:14.040> bits<04:32:14.399> together 04:32:14.570 --> 04:32:14.580 align:start position:0% nonetheless is that two bits together 04:32:14.580 --> 04:32:16.790 align:start position:0% nonetheless is that two bits together form<04:32:15.120> a<04:32:15.659> crumb 04:32:16.790 --> 04:32:16.800 align:start position:0% form a crumb 04:32:16.800 --> 04:32:20.630 align:start position:0% form a crumb bits<04:32:17.760> contain<04:32:18.239> a<04:32:18.779> nibble<04:32:19.560> and<04:32:20.100> a<04:32:20.279> bits 04:32:20.630 --> 04:32:20.640 align:start position:0% bits contain a nibble and a bits 04:32:20.640 --> 04:32:23.210 align:start position:0% bits contain a nibble and a bits together<04:32:20.819> a<04:32:21.600> byte<04:32:21.960> that's<04:32:22.439> how<04:32:22.680> we<04:32:22.800> got<04:32:22.979> there 04:32:23.210 --> 04:32:23.220 align:start position:0% together a byte that's how we got there 04:32:23.220 --> 04:32:26.809 align:start position:0% together a byte that's how we got there bits<04:32:24.120> crumbs<04:32:24.540> nibbles<04:32:25.020> bites<04:32:25.680> now<04:32:26.399> depending 04:32:26.809 --> 04:32:26.819 align:start position:0% bits crumbs nibbles bites now depending 04:32:26.819 --> 04:32:28.729 align:start position:0% bits crumbs nibbles bites now depending on<04:32:27.060> the<04:32:27.239> processor<04:32:27.720> you<04:32:28.020> have 04:32:28.729 --> 04:32:28.739 align:start position:0% on the processor you have 04:32:28.739 --> 04:32:34.370 align:start position:0% on the processor you have a<04:32:29.580> word<04:32:29.699> would<04:32:30.300> either<04:32:30.420> be<04:32:30.779> 16<04:32:31.819> 32<04:32:32.819> or<04:32:33.359> 64<04:32:33.899> bits 04:32:34.370 --> 04:32:34.380 align:start position:0% a word would either be 16 32 or 64 bits 04:32:34.380 --> 04:32:37.010 align:start position:0% a word would either be 16 32 or 64 bits we<04:32:35.100> generally<04:32:35.340> don't<04:32:35.580> see<04:32:35.760> 16-bit<04:32:36.420> processors 04:32:37.010 --> 04:32:37.020 align:start position:0% we generally don't see 16-bit processors 04:32:37.020 --> 04:32:40.070 align:start position:0% we generally don't see 16-bit processors anymore<04:32:37.260> so<04:32:38.040> generally<04:32:38.399> speaking<04:32:38.880> a<04:32:39.359> word<04:32:39.540> is 04:32:40.070 --> 04:32:40.080 align:start position:0% anymore so generally speaking a word is 04:32:40.080 --> 04:32:42.530 align:start position:0% anymore so generally speaking a word is either<04:32:40.199> going<04:32:40.439> to<04:32:40.560> be<04:32:40.620> 32<04:32:41.100> bits<04:32:41.460> or<04:32:41.640> 64<04:32:42.120> bits 04:32:42.530 --> 04:32:42.540 align:start position:0% either going to be 32 bits or 64 bits 04:32:42.540 --> 04:32:44.630 align:start position:0% either going to be 32 bits or 64 bits this<04:32:43.020> doesn't<04:32:43.199> mean<04:32:43.500> a<04:32:43.920> word<04:32:44.100> that<04:32:44.399> you've 04:32:44.630 --> 04:32:44.640 align:start position:0% this doesn't mean a word that you've 04:32:44.640 --> 04:32:47.389 align:start position:0% this doesn't mean a word that you've written<04:32:45.060> on<04:32:45.239> your<04:32:45.479> word<04:32:45.659> processor<04:32:46.380> but<04:32:47.040> a 04:32:47.389 --> 04:32:47.399 align:start position:0% written on your word processor but a 04:32:47.399 --> 04:32:50.330 align:start position:0% written on your word processor but a unit<04:32:47.520> of<04:32:47.760> measurement<04:32:48.180> just<04:32:49.020> like<04:32:49.140> byte<04:32:49.680> is 04:32:50.330 --> 04:32:50.340 align:start position:0% unit of measurement just like byte is 04:32:50.340 --> 04:32:52.790 align:start position:0% unit of measurement just like byte is now<04:32:50.880> in<04:32:51.180> most<04:32:51.420> places 04:32:52.790 --> 04:32:52.800 align:start position:0% now in most places 04:32:52.800 --> 04:32:57.250 align:start position:0% now in most places Hilo<04:32:53.939> is<04:32:54.659> a<04:32:54.960> thousand<04:32:55.260> such<04:32:55.800> as<04:32:56.060> kilometers 04:32:57.250 --> 04:32:57.260 align:start position:0% Hilo is a thousand such as kilometers 04:32:57.260 --> 04:33:00.830 align:start position:0% Hilo is a thousand such as kilometers and<04:32:58.260> uh<04:32:58.739> in<04:32:59.220> one<04:32:59.819> thousand<04:33:00.180> such<04:33:00.659> as 04:33:00.830 --> 04:33:00.840 align:start position:0% and uh in one thousand such as 04:33:00.840 --> 04:33:03.349 align:start position:0% and uh in one thousand such as kilometers<04:33:01.380> means<04:33:01.739> one<04:33:02.100> thousand<04:33:02.460> meters 04:33:03.349 --> 04:33:03.359 align:start position:0% kilometers means one thousand meters 04:33:03.359 --> 04:33:05.390 align:start position:0% kilometers means one thousand meters while<04:33:03.720> this<04:33:03.960> is<04:33:04.141> true<04:33:04.439> in<04:33:04.680> networking<04:33:05.160> it 04:33:05.390 --> 04:33:05.400 align:start position:0% while this is true in networking it 04:33:05.400 --> 04:33:07.551 align:start position:0% while this is true in networking it becomes<04:33:05.820> slightly<04:33:06.600> more<04:33:06.959> complicated 04:33:07.551 --> 04:33:07.561 align:start position:0% becomes slightly more complicated 04:33:07.561 --> 04:33:10.849 align:start position:0% becomes slightly more complicated because<04:33:08.340> some<04:33:08.879> sources<04:33:09.420> Define<04:33:09.779> a<04:33:10.320> key<04:33:10.500> a 04:33:10.849 --> 04:33:10.859 align:start position:0% because some sources Define a key a 04:33:10.859 --> 04:33:13.269 align:start position:0% because some sources Define a key a kilobit<04:33:11.400> as 04:33:13.269 --> 04:33:13.279 align:start position:0% kilobit as 04:33:13.279 --> 04:33:16.429 align:start position:0% kilobit as 1024<04:33:14.279> bits<04:33:14.939> While<04:33:15.299> others<04:33:15.660> might<04:33:15.840> Define<04:33:16.020> a 04:33:16.429 --> 04:33:16.439 align:start position:0% 1024 bits While others might Define a 04:33:16.439 --> 04:33:20.150 align:start position:0% 1024 bits While others might Define a kilobit<04:33:16.920> as<04:33:17.480> 1024<04:33:18.480> bytes 04:33:20.150 --> 04:33:20.160 align:start position:0% kilobit as 1024 bytes 04:33:20.160 --> 04:33:23.869 align:start position:0% kilobit as 1024 bytes one<04:33:20.699> of<04:33:20.820> the<04:33:20.939> reasons<04:33:21.359> for<04:33:21.600> this<04:33:21.900> confusion<04:33:23.100> is 04:33:23.869 --> 04:33:23.879 align:start position:0% one of the reasons for this confusion is 04:33:23.879 --> 04:33:25.670 align:start position:0% one of the reasons for this confusion is and<04:33:24.180> you<04:33:24.299> can<04:33:24.420> see<04:33:24.539> right<04:33:24.840> here<04:33:25.020> how<04:33:25.320> we<04:33:25.500> get 04:33:25.670 --> 04:33:25.680 align:start position:0% and you can see right here how we get 04:33:25.680 --> 04:33:27.590 align:start position:0% and you can see right here how we get that<04:33:25.920> 1024 04:33:27.590 --> 04:33:27.600 align:start position:0% that 1024 04:33:27.600 --> 04:33:30.410 align:start position:0% that 1024 2<04:33:28.141> to<04:33:28.379> the<04:33:28.500> 10th<04:33:28.859> bytes<04:33:29.340> and<04:33:29.939> one<04:33:30.119> of<04:33:30.240> the 04:33:30.410 --> 04:33:30.420 align:start position:0% 2 to the 10th bytes and one of the 04:33:30.420 --> 04:33:32.090 align:start position:0% 2 to the 10th bytes and one of the confusion<04:33:30.900> the<04:33:31.199> reason<04:33:31.320> for<04:33:31.561> this<04:33:31.680> confusion 04:33:32.090 --> 04:33:32.100 align:start position:0% confusion the reason for this confusion 04:33:32.100 --> 04:33:35.449 align:start position:0% confusion the reason for this confusion of<04:33:32.340> bits<04:33:32.939> versus<04:33:33.180> bytes<04:33:33.840> is<04:33:34.500> because<04:33:34.740> of<04:33:35.279> the 04:33:35.449 --> 04:33:35.459 align:start position:0% of bits versus bytes is because of the 04:33:35.459 --> 04:33:38.750 align:start position:0% of bits versus bytes is because of the little<04:33:35.580> B<04:33:35.820> versus<04:33:36.480> the<04:33:36.900> Big<04:33:37.020> B<04:33:37.260> so<04:33:37.980> here<04:33:38.219> is<04:33:38.400> a 04:33:38.750 --> 04:33:38.760 align:start position:0% little B versus the Big B so here is a 04:33:38.760 --> 04:33:41.810 align:start position:0% little B versus the Big B so here is a fairly<04:33:39.119> easy<04:33:39.600> breakdown 04:33:41.810 --> 04:33:41.820 align:start position:0% fairly easy breakdown 04:33:41.820 --> 04:33:43.670 align:start position:0% fairly easy breakdown that<04:33:42.359> nearly<04:33:42.660> anywhere<04:33:42.959> you<04:33:43.141> go<04:33:43.260> and<04:33:43.500> more 04:33:43.670 --> 04:33:43.680 align:start position:0% that nearly anywhere you go and more 04:33:43.680 --> 04:33:45.769 align:start position:0% that nearly anywhere you go and more importantly<04:33:43.980> on<04:33:44.219> the<04:33:44.340> exam<04:33:44.641> is<04:33:45.420> going<04:33:45.719> to 04:33:45.769 --> 04:33:45.779 align:start position:0% importantly on the exam is going to 04:33:45.779 --> 04:33:46.609 align:start position:0% importantly on the exam is going to allow<04:33:45.959> you<04:33:46.020> to<04:33:46.141> have<04:33:46.260> a<04:33:46.500> perfect 04:33:46.609 --> 04:33:46.619 align:start position:0% allow you to have a perfect 04:33:46.619 --> 04:33:48.410 align:start position:0% allow you to have a perfect understanding<04:33:47.340> of<04:33:47.520> how<04:33:47.820> much<04:33:47.939> data<04:33:48.299> we're 04:33:48.410 --> 04:33:48.420 align:start position:0% understanding of how much data we're 04:33:48.420 --> 04:33:49.670 align:start position:0% understanding of how much data we're actually<04:33:48.600> talking<04:33:48.900> about 04:33:49.670 --> 04:33:49.680 align:start position:0% actually talking about 04:33:49.680 --> 04:33:52.730 align:start position:0% actually talking about this<04:33:50.459> chart<04:33:50.760> specifies<04:33:51.660> how<04:33:52.199> the<04:33:52.379> breakdown 04:33:52.730 --> 04:33:52.740 align:start position:0% this chart specifies how the breakdown 04:33:52.740 --> 04:33:55.429 align:start position:0% this chart specifies how the breakdown of<04:33:53.219> binary<04:33:53.699> data<04:33:54.180> is<04:33:54.719> mathematically 04:33:55.429 --> 04:33:55.439 align:start position:0% of binary data is mathematically 04:33:55.439 --> 04:33:58.970 align:start position:0% of binary data is mathematically calculated<04:33:56.580> and<04:33:57.061> this<04:33:57.240> binary<04:33:57.660> is<04:33:58.080> a<04:33:58.379> base<04:33:58.561> 2 04:33:58.970 --> 04:33:58.980 align:start position:0% calculated and this binary is a base 2 04:33:58.980 --> 04:34:01.730 align:start position:0% calculated and this binary is a base 2 system 04:34:01.730 --> 04:34:01.740 align:start position:0% 04:34:01.740 --> 04:34:03.470 align:start position:0% and<04:34:02.219> we'll<04:34:02.340> talk<04:34:02.520> more<04:34:02.760> about<04:34:02.939> that<04:34:03.119> when<04:34:03.359> we 04:34:03.470 --> 04:34:03.480 align:start position:0% and we'll talk more about that when we 04:34:03.480 --> 04:34:06.709 align:start position:0% and we'll talk more about that when we get<04:34:03.600> into<04:34:03.859> binary<04:34:04.859> and<04:34:05.219> creating<04:34:05.520> binary 04:34:06.709 --> 04:34:06.719 align:start position:0% get into binary and creating binary 04:34:06.719 --> 04:34:07.369 align:start position:0% get into binary and creating binary um 04:34:07.369 --> 04:34:07.379 align:start position:0% um 04:34:07.379 --> 04:34:11.929 align:start position:0% um uh<04:34:08.219> numbers<04:34:08.939> like<04:34:09.420> IP<04:34:09.840> addresses<04:34:10.379> and<04:34:11.279> why<04:34:11.820> is 04:34:11.929 --> 04:34:11.939 align:start position:0% uh numbers like IP addresses and why is 04:34:11.939 --> 04:34:13.369 align:start position:0% uh numbers like IP addresses and why is it<04:34:12.119> base<04:34:12.240> two<04:34:12.480> because<04:34:12.719> we<04:34:12.900> only<04:34:13.020> have<04:34:13.260> two 04:34:13.369 --> 04:34:13.379 align:start position:0% it base two because we only have two 04:34:13.379 --> 04:34:17.029 align:start position:0% it base two because we only have two options<04:34:13.740> a<04:34:14.100> one<04:34:14.340> and<04:34:14.699> a<04:34:14.879> zero 04:34:17.029 --> 04:34:17.039 align:start position:0% options a one and a zero 04:34:17.039 --> 04:34:19.609 align:start position:0% options a one and a zero which<04:34:17.520> is<04:34:17.641> a<04:34:17.939> bit<04:34:18.061> and<04:34:18.539> remember<04:34:18.719> eight<04:34:19.141> bits 04:34:19.609 --> 04:34:19.619 align:start position:0% which is a bit and remember eight bits 04:34:19.619 --> 04:34:22.131 align:start position:0% which is a bit and remember eight bits go<04:34:19.799> into<04:34:19.980> a<04:34:20.520> byte<04:34:21.180> so<04:34:21.420> this<04:34:21.600> chart<04:34:21.779> mainly 04:34:22.131 --> 04:34:22.141 align:start position:0% go into a byte so this chart mainly 04:34:22.141 --> 04:34:23.750 align:start position:0% go into a byte so this chart mainly demonstrates<04:34:22.561> how<04:34:22.859> that<04:34:23.100> numbering<04:34:23.520> system 04:34:23.750 --> 04:34:23.760 align:start position:0% demonstrates how that numbering system 04:34:23.760 --> 04:34:25.970 align:start position:0% demonstrates how that numbering system works<04:34:24.299> the<04:34:24.779> magic<04:34:24.959> number<04:34:25.260> I<04:34:25.561> really<04:34:25.680> want<04:34:25.859> you 04:34:25.970 --> 04:34:25.980 align:start position:0% works the magic number I really want you 04:34:25.980 --> 04:34:29.090 align:start position:0% works the magic number I really want you to<04:34:26.100> pay<04:34:26.279> attention<04:34:26.580> to<04:34:26.820> is<04:34:27.180> 10<04:34:27.480> 24.<04:34:28.320> that's<04:34:28.799> the 04:34:29.090 --> 04:34:29.100 align:start position:0% to pay attention to is 10 24. that's the 04:34:29.100 --> 04:34:31.310 align:start position:0% to pay attention to is 10 24. that's the number<04:34:29.219> of<04:34:29.459> bytes<04:34:29.939> in<04:34:30.180> a<04:34:30.359> kilobyte<04:34:30.840> the<04:34:31.141> number 04:34:31.310 --> 04:34:31.320 align:start position:0% number of bytes in a kilobyte the number 04:34:31.320 --> 04:34:33.410 align:start position:0% number of bytes in a kilobyte the number of<04:34:31.439> kilobytes<04:34:32.039> in<04:34:32.219> a<04:34:32.340> megabyte<04:34:32.820> the<04:34:33.119> number<04:34:33.299> of 04:34:33.410 --> 04:34:33.420 align:start position:0% of kilobytes in a megabyte the number of 04:34:33.420 --> 04:34:35.570 align:start position:0% of kilobytes in a megabyte the number of megabytes<04:34:34.080> in<04:34:34.439> a<04:34:34.619> gigabyte<04:34:35.100> the<04:34:35.279> number 04:34:35.570 --> 04:34:35.580 align:start position:0% megabytes in a gigabyte the number 04:34:35.580 --> 04:34:38.689 align:start position:0% megabytes in a gigabyte the number gigabytes<04:34:36.480> in<04:34:36.840> a<04:34:37.020> terabyte<04:34:37.740> so<04:34:38.100> on<04:34:38.340> and<04:34:38.520> so 04:34:38.689 --> 04:34:38.699 align:start position:0% gigabytes in a terabyte so on and so 04:34:38.699 --> 04:34:40.551 align:start position:0% gigabytes in a terabyte so on and so forth<04:34:39.061> now<04:34:39.539> you're<04:34:39.779> not<04:34:39.900> going<04:34:40.020> to<04:34:40.141> be<04:34:40.199> asked 04:34:40.551 --> 04:34:40.561 align:start position:0% forth now you're not going to be asked 04:34:40.561 --> 04:34:43.189 align:start position:0% forth now you're not going to be asked to<04:34:40.619> calculate<04:34:41.340> this<04:34:41.641> necessarily<04:34:42.359> but<04:34:43.080> it's 04:34:43.189 --> 04:34:43.199 align:start position:0% to calculate this necessarily but it's 04:34:43.199 --> 04:34:45.769 align:start position:0% to calculate this necessarily but it's good<04:34:43.439> to<04:34:43.619> know<04:34:43.799> nonetheless 04:34:45.769 --> 04:34:45.779 align:start position:0% good to know nonetheless 04:34:45.779 --> 04:34:47.869 align:start position:0% good to know nonetheless all<04:34:46.260> right 04:34:47.869 --> 04:34:47.879 align:start position:0% all right 04:34:47.879 --> 04:34:50.810 align:start position:0% all right so<04:34:48.420> we<04:34:48.779> just<04:34:48.959> talked<04:34:49.320> about<04:34:49.379> a<04:34:49.740> signal<04:34:50.100> and 04:34:50.810 --> 04:34:50.820 align:start position:0% so we just talked about a signal and 04:34:50.820 --> 04:34:53.869 align:start position:0% so we just talked about a signal and what<04:34:51.119> analog<04:34:51.840> means<04:34:52.260> the<04:34:52.980> signal<04:34:53.279> being<04:34:53.459> how 04:34:53.869 --> 04:34:53.879 align:start position:0% what analog means the signal being how 04:34:53.879 --> 04:34:57.590 align:start position:0% what analog means the signal being how that<04:34:54.119> data<04:34:54.600> is<04:34:55.260> sent<04:34:55.561> modified<04:34:56.459> and<04:34:57.119> received 04:34:57.590 --> 04:34:57.600 align:start position:0% that data is sent modified and received 04:34:57.600 --> 04:35:00.410 align:start position:0% that data is sent modified and received and<04:34:58.141> then<04:34:58.260> analog<04:34:58.799> being<04:34:59.219> that<04:34:59.820> it<04:35:00.061> can<04:35:00.240> have 04:35:00.410 --> 04:35:00.420 align:start position:0% and then analog being that it can have 04:35:00.420 --> 04:35:02.330 align:start position:0% and then analog being that it can have many<04:35:00.719> different<04:35:00.959> values 04:35:02.330 --> 04:35:02.340 align:start position:0% many different values 04:35:02.340 --> 04:35:05.150 align:start position:0% many different values we<04:35:02.879> looked<04:35:03.119> at<04:35:03.180> the<04:35:03.420> attributes<04:35:03.900> of<04:35:04.260> a<04:35:04.500> analog 04:35:05.150 --> 04:35:05.160 align:start position:0% we looked at the attributes of a analog 04:35:05.160 --> 04:35:10.209 align:start position:0% we looked at the attributes of a analog signal<04:35:05.580> including<04:35:06.420> amplitude 04:35:10.209 --> 04:35:10.219 align:start position:0% 04:35:10.219 --> 04:35:15.470 align:start position:0% Peak<04:35:11.520> a<04:35:12.240> trough 04:35:15.470 --> 04:35:15.480 align:start position:0% 04:35:15.480 --> 04:35:18.470 align:start position:0% frequency<04:35:16.379> and<04:35:17.340> so<04:35:17.459> on 04:35:18.470 --> 04:35:18.480 align:start position:0% frequency and so on 04:35:18.480 --> 04:35:20.929 align:start position:0% frequency and so on we<04:35:18.959> also<04:35:19.199> looked<04:35:19.439> at<04:35:19.561> a<04:35:19.740> digital<04:35:20.100> signal<04:35:20.520> and 04:35:20.929 --> 04:35:20.939 align:start position:0% we also looked at a digital signal and 04:35:20.939 --> 04:35:23.510 align:start position:0% we also looked at a digital signal and Digital<04:35:21.299> Data<04:35:21.840> Transmissions<04:35:22.520> remembering 04:35:23.510 --> 04:35:23.520 align:start position:0% Digital Data Transmissions remembering 04:35:23.520 --> 04:35:25.849 align:start position:0% Digital Data Transmissions remembering that<04:35:23.760> a<04:35:23.939> digital<04:35:24.180> signal<04:35:24.660> can<04:35:25.320> only<04:35:25.500> have 04:35:25.849 --> 04:35:25.859 align:start position:0% that a digital signal can only have 04:35:25.859 --> 04:35:30.410 align:start position:0% that a digital signal can only have generally<04:35:26.699> two<04:35:27.119> values<04:35:27.660> a<04:35:28.439> one<04:35:28.680> and<04:35:29.459> a<04:35:29.641> zero 04:35:30.410 --> 04:35:30.420 align:start position:0% generally two values a one and a zero 04:35:30.420 --> 04:35:32.390 align:start position:0% generally two values a one and a zero and<04:35:30.900> depending<04:35:31.199> on<04:35:31.379> whether<04:35:31.561> we're<04:35:31.859> comparing 04:35:32.390 --> 04:35:32.400 align:start position:0% and depending on whether we're comparing 04:35:32.400 --> 04:35:35.269 align:start position:0% and depending on whether we're comparing it<04:35:32.580> to<04:35:32.760> each<04:35:32.939> its<04:35:33.420> own<04:35:33.480> or<04:35:34.141> to<04:35:34.320> the<04:35:34.561> ground<04:35:34.680> we 04:35:35.269 --> 04:35:35.279 align:start position:0% it to each its own or to the ground we 04:35:35.279 --> 04:35:36.949 align:start position:0% it to each its own or to the ground we have<04:35:35.400> different<04:35:35.641> digital<04:35:36.180> data<04:35:36.719> transmission 04:35:36.949 --> 04:35:36.959 align:start position:0% have different digital data transmission 04:35:36.959 --> 04:35:40.010 align:start position:0% have different digital data transmission methods<04:35:37.799> we<04:35:38.641> also<04:35:38.879> looked<04:35:39.180> at<04:35:39.240> modulating 04:35:40.010 --> 04:35:40.020 align:start position:0% methods we also looked at modulating 04:35:40.020 --> 04:35:43.849 align:start position:0% methods we also looked at modulating which<04:35:40.619> allows<04:35:41.100> us<04:35:41.219> to<04:35:41.699> send<04:35:42.000> a<04:35:42.359> signal<04:35:42.779> over<04:35:43.439> a 04:35:43.849 --> 04:35:43.859 align:start position:0% which allows us to send a signal over a 04:35:43.859 --> 04:35:47.330 align:start position:0% which allows us to send a signal over a more<04:35:43.980> powerful<04:35:44.480> carrier<04:35:45.480> signal 04:35:47.330 --> 04:35:47.340 align:start position:0% more powerful carrier signal 04:35:47.340 --> 04:35:50.150 align:start position:0% more powerful carrier signal in<04:35:47.939> order<04:35:48.119> to<04:35:48.359> allow<04:35:48.660> it<04:35:48.779> to<04:35:49.080> travel<04:35:49.379> long 04:35:50.150 --> 04:35:50.160 align:start position:0% in order to allow it to travel long 04:35:50.160 --> 04:35:52.670 align:start position:0% in order to allow it to travel long distances 04:35:52.670 --> 04:35:52.680 align:start position:0% distances 04:35:52.680 --> 04:35:55.551 align:start position:0% distances we<04:35:53.160> looked<04:35:53.459> at<04:35:53.580> Digital<04:35:54.240> Signal<04:35:54.719> modulation 04:35:55.551 --> 04:35:55.561 align:start position:0% we looked at Digital Signal modulation 04:35:55.561 --> 04:35:58.070 align:start position:0% we looked at Digital Signal modulation techniques<04:35:56.279> perhaps<04:35:57.000> we<04:35:57.180> got<04:35:57.299> a<04:35:57.539> little<04:35:57.660> too 04:35:58.070 --> 04:35:58.080 align:start position:0% techniques perhaps we got a little too 04:35:58.080 --> 04:35:59.390 align:start position:0% techniques perhaps we got a little too involved<04:35:58.561> in<04:35:58.680> it 04:35:59.390 --> 04:35:59.400 align:start position:0% involved in it 04:35:59.400 --> 04:36:02.510 align:start position:0% involved in it and<04:36:00.000> we<04:36:00.299> talked<04:36:00.660> about<04:36:00.779> how<04:36:01.680> then<04:36:01.980> we<04:36:02.400> can 04:36:02.510 --> 04:36:02.520 align:start position:0% and we talked about how then we can 04:36:02.520 --> 04:36:06.051 align:start position:0% and we talked about how then we can convert<04:36:02.939> these<04:36:03.359> Digital<04:36:03.600> Signal<04:36:04.141> into<04:36:05.061> a 04:36:06.051 --> 04:36:06.061 align:start position:0% convert these Digital Signal into a 04:36:06.061 --> 04:36:09.590 align:start position:0% convert these Digital Signal into a analog<04:36:06.719> signal<04:36:07.141> for<04:36:07.799> sending<04:36:08.400> over<04:36:08.520> data<04:36:09.240> and 04:36:09.590 --> 04:36:09.600 align:start position:0% analog signal for sending over data and 04:36:09.600 --> 04:36:12.230 align:start position:0% analog signal for sending over data and then<04:36:09.719> how<04:36:10.020> we<04:36:10.279> demodulate<04:36:11.279> it<04:36:11.459> back<04:36:11.641> and<04:36:12.061> we 04:36:12.230 --> 04:36:12.240 align:start position:0% then how we demodulate it back and we 04:36:12.240 --> 04:36:14.029 align:start position:0% then how we demodulate it back and we talked<04:36:12.539> about<04:36:12.600> the<04:36:12.900> device<04:36:13.080> doing<04:36:13.500> this<04:36:13.799> is 04:36:14.029 --> 04:36:14.039 align:start position:0% talked about the device doing this is 04:36:14.039 --> 04:36:17.029 align:start position:0% talked about the device doing this is called<04:36:14.279> a<04:36:14.641> modem<04:36:15.000> which<04:36:15.480> modulates<04:36:16.080> and 04:36:17.029 --> 04:36:17.039 align:start position:0% called a modem which modulates and 04:36:17.039 --> 04:36:18.349 align:start position:0% called a modem which modulates and demodulates 04:36:18.349 --> 04:36:18.359 align:start position:0% demodulates 04:36:18.359 --> 04:36:20.689 align:start position:0% demodulates we<04:36:18.900> also<04:36:19.199> described<04:36:19.680> Digital<04:36:20.160> Signal 04:36:20.689 --> 04:36:20.699 align:start position:0% we also described Digital Signal 04:36:20.699 --> 04:36:23.150 align:start position:0% we also described Digital Signal referencing<04:36:21.480> methods<04:36:21.959> in<04:36:22.500> other<04:36:22.561> words<04:36:22.740> how 04:36:23.150 --> 04:36:23.160 align:start position:0% referencing methods in other words how 04:36:23.160 --> 04:36:26.090 align:start position:0% referencing methods in other words how it<04:36:23.340> knows<04:36:23.699> where<04:36:24.359> the<04:36:24.539> signal<04:36:24.840> begins<04:36:25.379> and 04:36:26.090 --> 04:36:26.100 align:start position:0% it knows where the signal begins and 04:36:26.100 --> 04:36:31.429 align:start position:0% it knows where the signal begins and where<04:36:26.340> it<04:36:26.520> ends 04:36:31.429 --> 04:36:31.439 align:start position:0% 04:36:31.439 --> 04:36:33.949 align:start position:0% finally<04:36:32.160> we<04:36:32.520> described<04:36:32.879> the<04:36:33.119> Digital<04:36:33.420> Data 04:36:33.949 --> 04:36:33.959 align:start position:0% finally we described the Digital Data 04:36:33.959 --> 04:36:36.289 align:start position:0% finally we described the Digital Data units<04:36:34.400> specifically<04:36:35.400> I<04:36:35.580> wanted<04:36:35.760> you<04:36:36.000> to<04:36:36.119> pay 04:36:36.289 --> 04:36:36.299 align:start position:0% units specifically I wanted you to pay 04:36:36.299 --> 04:36:39.289 align:start position:0% units specifically I wanted you to pay attention<04:36:36.600> to<04:36:36.959> the<04:36:37.680> fact<04:36:37.859> that<04:36:38.039> one<04:36:38.400> bit 04:36:39.289 --> 04:36:39.299 align:start position:0% attention to the fact that one bit 04:36:39.299 --> 04:36:43.849 align:start position:0% attention to the fact that one bit equals<04:36:40.141> the<04:36:40.799> fact<04:36:40.920> that<04:36:41.219> 8<04:36:41.820> Bits<04:36:42.359> equal<04:36:43.020> one 04:36:43.849 --> 04:36:43.859 align:start position:0% equals the fact that 8 Bits equal one 04:36:43.859 --> 04:36:45.769 align:start position:0% equals the fact that 8 Bits equal one byte 04:36:45.769 --> 04:36:45.779 align:start position:0% byte 04:36:45.779 --> 04:36:48.670 align:start position:0% byte and<04:36:46.199> the<04:36:46.439> fact<04:36:46.561> that<04:36:47.039> 10 04:36:48.670 --> 04:36:48.680 align:start position:0% and the fact that 10 04:36:48.680 --> 04:36:52.010 align:start position:0% and the fact that 10 1024<04:36:49.680> bits 04:36:52.010 --> 04:36:52.020 align:start position:0% 1024 bits 04:36:52.020 --> 04:36:55.910 align:start position:0% 1024 bits are<04:36:52.740> in<04:36:52.980> one 04:36:55.910 --> 04:36:55.920 align:start position:0% 04:36:55.920 --> 04:36:57.529 align:start position:0% kilobit 04:36:57.529 --> 04:36:57.539 align:start position:0% kilobit 04:36:57.539 --> 04:37:08.350 align:start position:0% kilobit or<04:36:58.199> 1024<04:36:59.039> bytes<04:36:59.760> are<04:37:00.420> in<04:37:00.660> one<04:37:01.199> kilobyte 04:37:08.350 --> 04:37:08.360 align:start position:0% 04:37:08.360 --> 04:37:28.490 align:start position:0% [Music] 04:37:28.490 --> 04:37:28.500 align:start position:0% 04:37:28.500 --> 04:37:31.670 align:start position:0% Network<04:37:29.160> protocols<04:37:30.061> and<04:37:30.299> services 04:37:31.670 --> 04:37:31.680 align:start position:0% Network protocols and services 04:37:31.680 --> 04:37:35.390 align:start position:0% Network protocols and services common<04:37:32.340> Network<04:37:32.699> ports<04:37:33.240> and<04:37:33.600> protocols 04:37:35.390 --> 04:37:35.400 align:start position:0% common Network ports and protocols 04:37:35.400 --> 04:37:37.369 align:start position:0% common Network ports and protocols all<04:37:35.760> right<04:37:35.939> now<04:37:36.119> we<04:37:36.240> start<04:37:36.420> getting<04:37:36.719> into<04:37:36.959> what 04:37:37.369 --> 04:37:37.379 align:start position:0% all right now we start getting into what 04:37:37.379 --> 04:37:39.650 align:start position:0% all right now we start getting into what I<04:37:37.500> think<04:37:37.680> is<04:37:37.859> the<04:37:38.100> fun<04:37:38.279> stuff<04:37:38.580> in<04:37:39.359> this<04:37:39.539> network 04:37:39.650 --> 04:37:39.660 align:start position:0% I think is the fun stuff in this network 04:37:39.660 --> 04:37:42.529 align:start position:0% I think is the fun stuff in this network plus<04:37:39.900> exam<04:37:40.320> in<04:37:40.859> some<04:37:41.039> ways<04:37:41.340> it's<04:37:41.580> also<04:37:41.879> where<04:37:42.299> a 04:37:42.529 --> 04:37:42.539 align:start position:0% plus exam in some ways it's also where a 04:37:42.539 --> 04:37:44.029 align:start position:0% plus exam in some ways it's also where a blue<04:37:42.840> bulk<04:37:43.199> of<04:37:43.260> the<04:37:43.379> questions<04:37:43.561> are<04:37:43.799> going<04:37:43.920> to 04:37:44.029 --> 04:37:44.039 align:start position:0% blue bulk of the questions are going to 04:37:44.039 --> 04:37:47.570 align:start position:0% blue bulk of the questions are going to come<04:37:44.100> from<04:37:44.340> by<04:37:45.299> the<04:37:45.480> end<04:37:45.840> of<04:37:46.439> this<04:37:47.039> module 04:37:47.570 --> 04:37:47.580 align:start position:0% come from by the end of this module 04:37:47.580 --> 04:37:49.730 align:start position:0% come from by the end of this module you're<04:37:48.061> going<04:37:48.240> to<04:37:48.299> be<04:37:48.420> able<04:37:48.539> to<04:37:48.660> say<04:37:48.959> what<04:37:49.439> each 04:37:49.730 --> 04:37:49.740 align:start position:0% you're going to be able to say what each 04:37:49.740 --> 04:37:52.369 align:start position:0% you're going to be able to say what each of<04:37:49.859> these<04:37:50.039> numbers<04:37:50.219> represents<04:37:51.119> in<04:37:51.779> terms<04:37:52.080> of 04:37:52.369 --> 04:37:52.379 align:start position:0% of these numbers represents in terms of 04:37:52.379 --> 04:37:54.650 align:start position:0% of these numbers represents in terms of a<04:37:52.500> protocol<04:37:52.799> now<04:37:53.459> if<04:37:53.699> you<04:37:53.879> took<04:37:54.240> the<04:37:54.359> a<04:37:54.480> plus 04:37:54.650 --> 04:37:54.660 align:start position:0% a protocol now if you took the a plus 04:37:54.660 --> 04:37:56.929 align:start position:0% a protocol now if you took the a plus exam<04:37:55.080> and<04:37:55.260> I<04:37:55.379> hope<04:37:55.500> you<04:37:55.619> did<04:37:55.859> you<04:37:56.760> probably 04:37:56.929 --> 04:37:56.939 align:start position:0% exam and I hope you did you probably 04:37:56.939 --> 04:37:59.150 align:start position:0% exam and I hope you did you probably recall<04:37:57.420> some<04:37:57.779> of<04:37:57.900> these<04:37:58.141> from<04:37:58.379> there<04:37:58.561> so<04:37:58.920> this 04:37:59.150 --> 04:37:59.160 align:start position:0% recall some of these from there so this 04:37:59.160 --> 04:38:01.670 align:start position:0% recall some of these from there so this might<04:37:59.459> be<04:37:59.641> a<04:38:00.119> bit<04:38:00.180> of<04:38:00.299> a<04:38:00.420> recap<04:38:00.779> for<04:38:01.080> you<04:38:01.199> but 04:38:01.670 --> 04:38:01.680 align:start position:0% might be a bit of a recap for you but 04:38:01.680 --> 04:38:03.051 align:start position:0% might be a bit of a recap for you but that's<04:38:01.799> okay<04:38:01.980> it<04:38:02.279> never<04:38:02.400> hurts<04:38:02.699> to<04:38:02.820> go<04:38:02.939> over 04:38:03.051 --> 04:38:03.061 align:start position:0% that's okay it never hurts to go over 04:38:03.061 --> 04:38:05.330 align:start position:0% that's okay it never hurts to go over this<04:38:03.299> stuff<04:38:03.480> again<04:38:03.719> especially<04:38:04.379> because<04:38:04.680> it 04:38:05.330 --> 04:38:05.340 align:start position:0% this stuff again especially because it 04:38:05.340 --> 04:38:07.429 align:start position:0% this stuff again especially because it just<04:38:05.520> always<04:38:05.760> pops<04:38:06.180> up<04:38:06.299> on<04:38:06.420> the<04:38:06.539> exam<04:38:06.840> and<04:38:07.260> as 04:38:07.429 --> 04:38:07.439 align:start position:0% just always pops up on the exam and as 04:38:07.439 --> 04:38:09.949 align:start position:0% just always pops up on the exam and as far<04:38:07.619> as<04:38:07.740> knowing<04:38:08.520> stuff<04:38:08.760> this<04:38:09.600> is<04:38:09.719> one<04:38:09.900> of 04:38:09.949 --> 04:38:09.959 align:start position:0% far as knowing stuff this is one of 04:38:09.959 --> 04:38:11.510 align:start position:0% far as knowing stuff this is one of those<04:38:10.080> things<04:38:10.260> that<04:38:10.439> you<04:38:10.680> just<04:38:10.799> have<04:38:11.219> to<04:38:11.400> know 04:38:11.510 --> 04:38:11.520 align:start position:0% those things that you just have to know 04:38:11.520 --> 04:38:13.131 align:start position:0% those things that you just have to know these<04:38:12.000> these<04:38:12.299> Protocols<04:38:12.719> are<04:38:12.840> what<04:38:12.959> you 04:38:13.131 --> 04:38:13.141 align:start position:0% these these Protocols are what you 04:38:13.141 --> 04:38:14.929 align:start position:0% these these Protocols are what you really<04:38:13.320> have<04:38:13.561> to<04:38:13.680> know<04:38:13.920> we're<04:38:14.580> going<04:38:14.760> to<04:38:14.820> talk 04:38:14.929 --> 04:38:14.939 align:start position:0% really have to know we're going to talk 04:38:14.939 --> 04:38:16.730 align:start position:0% really have to know we're going to talk about<04:38:15.119> the<04:38:15.420> protocols<04:38:15.900> in<04:38:16.080> more<04:38:16.199> depth<04:38:16.500> later 04:38:16.730 --> 04:38:16.740 align:start position:0% about the protocols in more depth later 04:38:16.740 --> 04:38:19.730 align:start position:0% about the protocols in more depth later too<04:38:17.039> when<04:38:17.219> we<04:38:17.400> talk<04:38:17.520> about<04:38:17.699> what<04:38:18.061> tcpip<04:38:18.959> is<04:38:19.379> but 04:38:19.730 --> 04:38:19.740 align:start position:0% too when we talk about what tcpip is but 04:38:19.740 --> 04:38:21.349 align:start position:0% too when we talk about what tcpip is but I<04:38:19.920> want<04:38:20.039> to<04:38:20.160> start<04:38:20.279> talking<04:38:20.580> about<04:38:20.760> these<04:38:21.119> now 04:38:21.349 --> 04:38:21.359 align:start position:0% I want to start talking about these now 04:38:21.359 --> 04:38:24.830 align:start position:0% I want to start talking about these now since<04:38:22.020> a<04:38:22.320> port<04:38:22.500> is<04:38:23.100> really<04:38:23.400> the<04:38:24.061> end<04:38:24.539> point 04:38:24.830 --> 04:38:24.840 align:start position:0% since a port is really the end point 04:38:24.840 --> 04:38:27.051 align:start position:0% since a port is really the end point logically<04:38:25.561> of<04:38:25.980> a<04:38:26.160> connection 04:38:27.051 --> 04:38:27.061 align:start position:0% logically of a connection 04:38:27.061 --> 04:38:29.209 align:start position:0% logically of a connection so<04:38:27.660> we're<04:38:27.900> going<04:38:28.080> to<04:38:28.199> start<04:38:28.379> by<04:38:28.680> talking<04:38:28.920> about 04:38:29.209 --> 04:38:29.219 align:start position:0% so we're going to start by talking about 04:38:29.219 --> 04:38:31.250 align:start position:0% so we're going to start by talking about what<04:38:29.580> a<04:38:29.699> port<04:38:29.820> is<04:38:30.119> in<04:38:30.299> a<04:38:30.480> little<04:38:30.539> more<04:38:30.719> detail 04:38:31.250 --> 04:38:31.260 align:start position:0% what a port is in a little more detail 04:38:31.260 --> 04:38:33.709 align:start position:0% what a port is in a little more detail and<04:38:31.920> outline<04:38:32.340> the<04:38:32.580> different<04:38:32.760> port<04:38:33.119> ranges 04:38:33.709 --> 04:38:33.719 align:start position:0% and outline the different port ranges 04:38:33.719 --> 04:38:36.070 align:start position:0% and outline the different port ranges there<04:38:34.080> are<04:38:34.199> three<04:38:34.379> of<04:38:34.561> them<04:38:34.740> well-known<04:38:35.520> ports 04:38:36.070 --> 04:38:36.080 align:start position:0% there are three of them well-known ports 04:38:36.080 --> 04:38:38.810 align:start position:0% there are three of them well-known ports registered<04:38:37.080> ports<04:38:37.500> and<04:38:37.920> then<04:38:38.039> the<04:38:38.219> last<04:38:38.340> range 04:38:38.810 --> 04:38:38.820 align:start position:0% registered ports and then the last range 04:38:38.820 --> 04:38:40.369 align:start position:0% registered ports and then the last range which<04:38:39.240> is 04:38:40.369 --> 04:38:40.379 align:start position:0% which is 04:38:40.379 --> 04:38:41.529 align:start position:0% which is um 04:38:41.529 --> 04:38:41.539 align:start position:0% um 04:38:41.539 --> 04:38:44.209 align:start position:0% um experimental<04:38:42.539> sort<04:38:42.900> of<04:38:43.020> ports<04:38:43.439> and<04:38:43.859> private 04:38:44.209 --> 04:38:44.219 align:start position:0% experimental sort of ports and private 04:38:44.219 --> 04:38:47.029 align:start position:0% experimental sort of ports and private ports<04:38:45.119> so<04:38:45.539> we're<04:38:45.719> going<04:38:45.900> to<04:38:46.080> outline<04:38:46.500> the<04:38:46.859> most 04:38:47.029 --> 04:38:47.039 align:start position:0% ports so we're going to outline the most 04:38:47.039 --> 04:38:50.689 align:start position:0% ports so we're going to outline the most common<04:38:47.480> well-known<04:38:48.480> default<04:38:49.260> ports<04:38:49.799> and<04:38:50.400> the 04:38:50.689 --> 04:38:50.699 align:start position:0% common well-known default ports and the 04:38:50.699 --> 04:38:52.490 align:start position:0% common well-known default ports and the protocols<04:38:51.119> that<04:38:51.299> go<04:38:51.480> along<04:38:51.600> with<04:38:51.900> them<04:38:52.080> I'm 04:38:52.490 --> 04:38:52.500 align:start position:0% protocols that go along with them I'm 04:38:52.500 --> 04:38:53.990 align:start position:0% protocols that go along with them I'm actually<04:38:52.680> going<04:38:52.859> to<04:38:52.920> give<04:38:53.039> you<04:38:53.160> a<04:38:53.520> huge<04:38:53.760> list 04:38:53.990 --> 04:38:54.000 align:start position:0% actually going to give you a huge list 04:38:54.000 --> 04:38:55.551 align:start position:0% actually going to give you a huge list of<04:38:54.299> all<04:38:54.420> the<04:38:54.539> protocols<04:38:55.020> you<04:38:55.141> need<04:38:55.260> to<04:38:55.379> know 04:38:55.551 --> 04:38:55.561 align:start position:0% of all the protocols you need to know 04:38:55.561 --> 04:38:57.051 align:start position:0% of all the protocols you need to know and<04:38:55.980> we're<04:38:56.100> going<04:38:56.219> to<04:38:56.279> talk<04:38:56.459> about<04:38:56.641> some<04:38:56.939> of 04:38:57.051 --> 04:38:57.061 align:start position:0% and we're going to talk about some of 04:38:57.061 --> 04:38:59.090 align:start position:0% and we're going to talk about some of those<04:38:57.180> in<04:38:57.420> depth<04:38:57.719> in<04:38:57.779> this<04:38:58.020> module<04:38:58.379> some<04:38:58.859> in 04:38:59.090 --> 04:38:59.100 align:start position:0% those in depth in this module some in 04:38:59.100 --> 04:39:01.429 align:start position:0% those in depth in this module some in the<04:38:59.279> next<04:38:59.400> module<04:38:59.939> and<04:39:00.539> then<04:39:00.660> some<04:39:00.959> later<04:39:01.260> on 04:39:01.429 --> 04:39:01.439 align:start position:0% the next module and then some later on 04:39:01.439 --> 04:39:03.051 align:start position:0% the next module and then some later on in<04:39:01.680> the<04:39:01.799> course<04:39:01.980> but<04:39:02.459> I'm<04:39:02.580> going<04:39:02.699> to<04:39:02.760> get<04:39:02.939> them 04:39:03.051 --> 04:39:03.061 align:start position:0% in the course but I'm going to get them 04:39:03.061 --> 04:39:06.289 align:start position:0% in the course but I'm going to get them all<04:39:03.180> out<04:39:03.359> onto<04:39:03.779> a<04:39:04.020> a<04:39:04.320> chart<04:39:04.680> for<04:39:05.039> you<04:39:05.160> right<04:39:05.459> now 04:39:06.289 --> 04:39:06.299 align:start position:0% all out onto a a chart for you right now 04:39:06.299 --> 04:39:08.631 align:start position:0% all out onto a a chart for you right now finally<04:39:07.080> I<04:39:07.500> wanted<04:39:07.619> to<04:39:07.799> find<04:39:07.980> and<04:39:08.160> describe 04:39:08.631 --> 04:39:08.641 align:start position:0% finally I wanted to find and describe 04:39:08.641 --> 04:39:11.090 align:start position:0% finally I wanted to find and describe the<04:39:09.119> common<04:39:09.359> ports<04:39:09.900> and<04:39:10.020> protocols<04:39:10.619> dealing 04:39:11.090 --> 04:39:11.100 align:start position:0% the common ports and protocols dealing 04:39:11.100 --> 04:39:14.470 align:start position:0% the common ports and protocols dealing with<04:39:11.219> FTP<04:39:12.180> or<04:39:12.719> the<04:39:12.900> file<04:39:13.199> transfer<04:39:13.740> protocol 04:39:14.470 --> 04:39:14.480 align:start position:0% with FTP or the file transfer protocol 04:39:14.480 --> 04:39:17.410 align:start position:0% with FTP or the file transfer protocol ntp<04:39:15.480> or<04:39:15.719> the<04:39:15.900> network<04:39:16.020> time<04:39:16.320> protocol 04:39:17.410 --> 04:39:17.420 align:start position:0% ntp or the network time protocol 04:39:17.420 --> 04:39:20.590 align:start position:0% ntp or the network time protocol SMTP<04:39:18.420> the<04:39:18.900> simple<04:39:19.080> mail<04:39:19.379> transfer<04:39:19.920> protocol 04:39:20.590 --> 04:39:20.600 align:start position:0% SMTP the simple mail transfer protocol 04:39:20.600 --> 04:39:25.070 align:start position:0% SMTP the simple mail transfer protocol POP3<04:39:21.600> or<04:39:22.020> the<04:39:22.320> post<04:39:22.799> office<04:39:23.039> protocol<04:39:23.779> the<04:39:24.779> uh 04:39:25.070 --> 04:39:25.080 align:start position:0% POP3 or the post office protocol the uh 04:39:25.080 --> 04:39:28.551 align:start position:0% POP3 or the post office protocol the uh used<04:39:25.561> to<04:39:26.039> receive<04:39:26.641> email<04:39:26.939> as<04:39:27.299> opposed<04:39:27.660> to<04:39:27.660> SMTP 04:39:28.551 --> 04:39:28.561 align:start position:0% used to receive email as opposed to SMTP 04:39:28.561 --> 04:39:31.849 align:start position:0% used to receive email as opposed to SMTP which<04:39:28.799> is<04:39:28.920> used<04:39:29.160> to<04:39:29.340> send<04:39:29.760> email<04:39:30.379> IMAP<04:39:31.379> which 04:39:31.849 --> 04:39:31.859 align:start position:0% which is used to send email IMAP which 04:39:31.859 --> 04:39:35.510 align:start position:0% which is used to send email IMAP which is<04:39:32.160> also<04:39:32.520> used<04:39:32.760> for<04:39:33.619> receiving<04:39:34.619> or<04:39:34.980> accessing 04:39:35.510 --> 04:39:35.520 align:start position:0% is also used for receiving or accessing 04:39:35.520 --> 04:39:37.131 align:start position:0% is also used for receiving or accessing email<04:39:35.820> which<04:39:36.420> stands<04:39:36.719> for<04:39:36.840> the<04:39:37.020> internet 04:39:37.131 --> 04:39:37.141 align:start position:0% email which stands for the internet 04:39:37.141 --> 04:39:40.570 align:start position:0% email which stands for the internet message<04:39:37.860> access<04:39:38.400> protocol 04:39:40.570 --> 04:39:40.580 align:start position:0% message access protocol 04:39:40.580 --> 04:39:44.810 align:start position:0% message access protocol nntp<04:39:41.580> or<04:39:42.360> the<04:39:42.718> network<04:39:43.320> news<04:39:44.040> transfer 04:39:44.810 --> 04:39:44.820 align:start position:0% nntp or the network news transfer 04:39:44.820 --> 04:39:47.630 align:start position:0% nntp or the network news transfer protocol<04:39:45.240> uh<04:39:46.140> something<04:39:46.440> you<04:39:46.980> may<04:39:47.340> have<04:39:47.458> used 04:39:47.630 --> 04:39:47.640 align:start position:0% protocol uh something you may have used 04:39:47.640 --> 04:39:51.708 align:start position:0% protocol uh something you may have used if<04:39:47.878> you've<04:39:48.120> ever<04:39:48.240> used<04:39:48.740> RSS<04:39:49.740> feeds<04:39:50.420> HTTP<04:39:51.420> or 04:39:51.708 --> 04:39:51.718 align:start position:0% if you've ever used RSS feeds HTTP or 04:39:51.718 --> 04:39:54.530 align:start position:0% if you've ever used RSS feeds HTTP or the<04:39:51.900> hypertext<04:39:52.680> transfer<04:39:53.218> protocol<04:39:53.640> and 04:39:54.530 --> 04:39:54.540 align:start position:0% the hypertext transfer protocol and 04:39:54.540 --> 04:39:57.830 align:start position:0% the hypertext transfer protocol and https<04:39:55.200> which<04:39:56.100> is<04:39:56.218> the<04:39:56.520> secure<04:39:56.820> version<04:39:57.060> these 04:39:57.830 --> 04:39:57.840 align:start position:0% https which is the secure version these 04:39:57.840 --> 04:39:59.750 align:start position:0% https which is the secure version these are<04:39:57.958> what<04:39:58.200> allow<04:39:58.620> you<04:39:58.740> to<04:39:58.980> browse<04:39:59.400> on<04:39:59.580> the 04:39:59.750 --> 04:39:59.760 align:start position:0% are what allow you to browse on the 04:39:59.760 --> 04:40:01.368 align:start position:0% are what allow you to browse on the internet<04:39:59.878> and<04:40:00.600> finally<04:40:00.840> we'll<04:40:01.020> talk<04:40:01.200> about 04:40:01.368 --> 04:40:01.378 align:start position:0% internet and finally we'll talk about 04:40:01.378 --> 04:40:05.750 align:start position:0% internet and finally we'll talk about RDP<04:40:02.218> or<04:40:03.120> the<04:40:03.480> remote<04:40:03.718> desktop<04:40:04.500> protocol<04:40:05.160> which 04:40:05.750 --> 04:40:05.760 align:start position:0% RDP or the remote desktop protocol which 04:40:05.760 --> 04:40:08.690 align:start position:0% RDP or the remote desktop protocol which allows<04:40:06.120> you<04:40:06.180> to<04:40:06.420> remote<04:40:06.660> in<04:40:07.080> to<04:40:07.680> a<04:40:08.100> Microsoft 04:40:08.690 --> 04:40:08.700 align:start position:0% allows you to remote in to a Microsoft 04:40:08.700 --> 04:40:11.750 align:start position:0% allows you to remote in to a Microsoft computer<04:40:09.060> all<04:40:10.020> right<04:40:10.200> so<04:40:10.920> let's<04:40:11.340> talk<04:40:11.580> about 04:40:11.750 --> 04:40:11.760 align:start position:0% computer all right so let's talk about 04:40:11.760 --> 04:40:15.288 align:start position:0% computer all right so let's talk about these<04:40:12.120> in<04:40:12.360> more<04:40:12.480> depth<04:40:13.260> first<04:40:13.860> off<04:40:14.100> we<04:40:15.060> have<04:40:15.180> to 04:40:15.288 --> 04:40:15.298 align:start position:0% these in more depth first off we have to 04:40:15.298 --> 04:40:18.110 align:start position:0% these in more depth first off we have to define<04:40:15.540> a<04:40:16.140> port<04:40:16.340> in<04:40:17.340> computers<04:40:17.878> and 04:40:18.110 --> 04:40:18.120 align:start position:0% define a port in computers and 04:40:18.120 --> 04:40:21.410 align:start position:0% define a port in computers and networking<04:40:18.600> a<04:40:19.080> port<04:40:19.320> is<04:40:19.860> a<04:40:20.218> process<04:40:20.640> specific 04:40:21.410 --> 04:40:21.420 align:start position:0% networking a port is a process specific 04:40:21.420 --> 04:40:25.010 align:start position:0% networking a port is a process specific or<04:40:21.840> application<04:40:22.560> specific<04:40:23.280> designation<04:40:24.120> that 04:40:25.010 --> 04:40:25.020 align:start position:0% or application specific designation that 04:40:25.020 --> 04:40:27.650 align:start position:0% or application specific designation that serves<04:40:25.378> as<04:40:25.620> a<04:40:25.920> communication<04:40:26.458> endpoint<04:40:27.360> in 04:40:27.650 --> 04:40:27.660 align:start position:0% serves as a communication endpoint in 04:40:27.660 --> 04:40:30.050 align:start position:0% serves as a communication endpoint in the<04:40:27.840> computer's<04:40:28.260> operating<04:40:28.680> system<04:40:29.060> meaning 04:40:30.050 --> 04:40:30.060 align:start position:0% the computer's operating system meaning 04:40:30.060 --> 04:40:32.810 align:start position:0% the computer's operating system meaning where<04:40:30.718> the<04:40:30.958> communication<04:40:31.500> logically<04:40:32.340> ends 04:40:32.810 --> 04:40:32.820 align:start position:0% where the communication logically ends 04:40:32.820 --> 04:40:35.090 align:start position:0% where the communication logically ends once<04:40:33.240> it<04:40:33.360> reaches<04:40:33.718> the<04:40:33.900> user<04:40:34.200> the<04:40:34.980> port 04:40:35.090 --> 04:40:35.100 align:start position:0% once it reaches the user the port 04:40:35.100 --> 04:40:38.270 align:start position:0% once it reaches the user the port identifies<04:40:36.060> specific<04:40:36.718> processes<04:40:37.620> and 04:40:38.270 --> 04:40:38.280 align:start position:0% identifies specific processes and 04:40:38.280 --> 04:40:42.350 align:start position:0% identifies specific processes and applications<04:40:39.020> and<04:40:40.020> denotes<04:40:40.620> the<04:40:41.340> path<04:40:41.878> that 04:40:42.350 --> 04:40:42.360 align:start position:0% applications and denotes the path that 04:40:42.360 --> 04:40:44.150 align:start position:0% applications and denotes the path that they<04:40:42.540> take<04:40:42.780> through<04:40:43.080> the<04:40:43.320> network 04:40:44.150 --> 04:40:44.160 align:start position:0% they take through the network 04:40:44.160 --> 04:40:46.368 align:start position:0% they take through the network now<04:40:44.760> the<04:40:45.000> internet<04:40:45.120> assigned<04:40:46.020> numbers 04:40:46.368 --> 04:40:46.378 align:start position:0% now the internet assigned numbers 04:40:46.378 --> 04:40:52.490 align:start position:0% now the internet assigned numbers Authority<04:40:47.160> or<04:40:48.000> the<04:40:48.420> i<04:40:49.200> a<04:40:49.560> n<04:40:50.218> a 04:40:52.490 --> 04:40:52.500 align:start position:0% 04:40:52.500 --> 04:40:54.948 align:start position:0% is<04:40:52.920> the<04:40:53.160> governing<04:40:53.520> entity<04:40:53.940> that<04:40:54.298> regulates 04:40:54.948 --> 04:40:54.958 align:start position:0% is the governing entity that regulates 04:40:54.958 --> 04:40:57.948 align:start position:0% is the governing entity that regulates all<04:40:55.440> of<04:40:55.560> these<04:40:55.920> Port<04:40:56.218> assignments<04:40:57.120> and<04:40:57.660> also 04:40:57.948 --> 04:40:57.958 align:start position:0% all of these Port assignments and also 04:40:57.958 --> 04:40:59.930 align:start position:0% all of these Port assignments and also defines<04:40:58.560> the<04:40:59.040> numbers<04:40:59.160> or<04:40:59.458> the<04:40:59.580> numbering 04:40:59.930 --> 04:40:59.940 align:start position:0% defines the numbers or the numbering 04:40:59.940 --> 04:41:02.090 align:start position:0% defines the numbers or the numbering convention<04:41:00.298> that<04:41:00.540> they're<04:41:00.660> given<04:41:01.440> now<04:41:01.798> these 04:41:02.090 --> 04:41:02.100 align:start position:0% convention that they're given now these 04:41:02.100 --> 04:41:07.010 align:start position:0% convention that they're given now these ports<04:41:02.520> range<04:41:03.240> from<04:41:03.600> 1<04:41:04.080> to<04:41:04.680> over<04:41:04.980> 65<04:41:06.240> 000.<04:41:06.600> Port 04:41:07.010 --> 04:41:07.020 align:start position:0% ports range from 1 to over 65 000. Port 04:41:07.020 --> 04:41:09.530 align:start position:0% ports range from 1 to over 65 000. Port 0<04:41:07.260> is<04:41:07.560> reserved<04:41:08.040> and<04:41:08.340> it's<04:41:08.520> never<04:41:08.760> used<04:41:09.060> so 04:41:09.530 --> 04:41:09.540 align:start position:0% 0 is reserved and it's never used so 04:41:09.540 --> 04:41:13.010 align:start position:0% 0 is reserved and it's never used so don't<04:41:10.140> really<04:41:10.378> worry<04:41:10.680> about<04:41:10.980> that<04:41:11.760> now<04:41:12.360> within 04:41:13.010 --> 04:41:13.020 align:start position:0% don't really worry about that now within 04:41:13.020 --> 04:41:14.868 align:start position:0% don't really worry about that now within this<04:41:13.378> range<04:41:13.680> we<04:41:14.040> actually<04:41:14.160> have<04:41:14.458> three 04:41:14.868 --> 04:41:14.878 align:start position:0% this range we actually have three 04:41:14.878 --> 04:41:17.570 align:start position:0% this range we actually have three different<04:41:15.180> subsets<04:41:15.900> of<04:41:16.260> ranges<04:41:16.740> and<04:41:17.400> as 04:41:17.570 --> 04:41:17.580 align:start position:0% different subsets of ranges and as 04:41:17.580 --> 04:41:19.910 align:start position:0% different subsets of ranges and as administrators<04:41:18.298> knowing<04:41:18.780> the<04:41:19.200> common<04:41:19.378> ports 04:41:19.910 --> 04:41:19.920 align:start position:0% administrators knowing the common ports 04:41:19.920 --> 04:41:22.550 align:start position:0% administrators knowing the common ports is<04:41:20.160> crucial<04:41:20.520> to<04:41:21.298> managing<04:41:21.958> a<04:41:22.200> successful 04:41:22.550 --> 04:41:22.560 align:start position:0% is crucial to managing a successful 04:41:22.560 --> 04:41:23.448 align:start position:0% is crucial to managing a successful Network 04:41:23.448 --> 04:41:23.458 align:start position:0% Network 04:41:23.458 --> 04:41:25.430 align:start position:0% Network the<04:41:24.120> common<04:41:24.240> ports<04:41:24.780> are<04:41:24.900> some<04:41:25.080> of<04:41:25.200> the 04:41:25.430 --> 04:41:25.440 align:start position:0% the common ports are some of the 04:41:25.440 --> 04:41:28.490 align:start position:0% the common ports are some of the guaranteed<04:41:25.980> few<04:41:26.540> questions<04:41:27.540> that<04:41:27.900> I<04:41:28.020> I<04:41:28.260> know 04:41:28.490 --> 04:41:28.500 align:start position:0% guaranteed few questions that I I know 04:41:28.500 --> 04:41:29.810 align:start position:0% guaranteed few questions that I I know you're<04:41:28.740> going<04:41:28.920> to<04:41:29.040> have<04:41:29.160> on<04:41:29.340> the<04:41:29.458> network<04:41:29.580> plus 04:41:29.810 --> 04:41:29.820 align:start position:0% you're going to have on the network plus 04:41:29.820 --> 04:41:32.208 align:start position:0% you're going to have on the network plus examination<04:41:30.540> and<04:41:31.260> nearly<04:41:31.620> every<04:41:31.980> other 04:41:32.208 --> 04:41:32.218 align:start position:0% examination and nearly every other 04:41:32.218 --> 04:41:34.670 align:start position:0% examination and nearly every other network<04:41:32.458> examination<04:41:33.240> as<04:41:33.480> well<04:41:33.660> so<04:41:34.260> covering 04:41:34.670 --> 04:41:34.680 align:start position:0% network examination as well so covering 04:41:34.680 --> 04:41:36.770 align:start position:0% network examination as well so covering these<04:41:35.040> and<04:41:35.340> committing<04:41:35.940> these<04:41:36.060> to<04:41:36.180> memory<04:41:36.480> is 04:41:36.770 --> 04:41:36.780 align:start position:0% these and committing these to memory is 04:41:36.780 --> 04:41:38.990 align:start position:0% these and committing these to memory is of<04:41:36.900> the<04:41:37.080> utmost<04:41:37.320> importance<04:41:37.860> now<04:41:38.458> within<04:41:38.820> that 04:41:38.990 --> 04:41:39.000 align:start position:0% of the utmost importance now within that 04:41:39.000 --> 04:41:42.230 align:start position:0% of the utmost importance now within that range<04:41:39.298> from<04:41:39.660> 1<04:41:39.840> to<04:41:40.020> over<04:41:40.260> 65<04:41:41.280> 000<04:41:41.400> there<04:41:42.060> are 04:41:42.230 --> 04:41:42.240 align:start position:0% range from 1 to over 65 000 there are 04:41:42.240 --> 04:41:44.990 align:start position:0% range from 1 to over 65 000 there are three<04:41:42.480> recognized<04:41:43.320> blocks<04:41:44.100> or<04:41:44.280> subsets<04:41:44.700> of 04:41:44.990 --> 04:41:45.000 align:start position:0% three recognized blocks or subsets of 04:41:45.000 --> 04:41:47.750 align:start position:0% three recognized blocks or subsets of ports<04:41:45.420> the<04:41:46.080> first<04:41:46.260> block<04:41:46.560> is<04:41:47.040> considered<04:41:47.458> the 04:41:47.750 --> 04:41:47.760 align:start position:0% ports the first block is considered the 04:41:47.760 --> 04:41:50.990 align:start position:0% ports the first block is considered the well-known<04:41:48.360> ports<04:41:48.900> these<04:41:49.798> ports<04:41:50.160> range<04:41:50.700> from 04:41:50.990 --> 04:41:51.000 align:start position:0% well-known ports these ports range from 04:41:51.000 --> 04:41:53.570 align:start position:0% well-known ports these ports range from one<04:41:51.240> to<04:41:51.480> one<04:41:51.718> thousand<04:41:52.080> twenty<04:41:52.440> three<04:41:52.560> this<04:41:53.458> is 04:41:53.570 --> 04:41:53.580 align:start position:0% one to one thousand twenty three this is 04:41:53.580 --> 04:41:55.010 align:start position:0% one to one thousand twenty three this is where<04:41:53.820> we're<04:41:54.000> mostly<04:41:54.298> going<04:41:54.480> to<04:41:54.600> look<04:41:54.718> at 04:41:55.010 --> 04:41:55.020 align:start position:0% where we're mostly going to look at 04:41:55.020 --> 04:41:57.230 align:start position:0% where we're mostly going to look at ports<04:41:55.500> uh<04:41:55.980> when<04:41:56.160> we<04:41:56.280> look<04:41:56.400> at<04:41:56.580> them<04:41:56.700> in<04:41:56.940> just<04:41:57.120> a 04:41:57.230 --> 04:41:57.240 align:start position:0% ports uh when we look at them in just a 04:41:57.240 --> 04:41:57.948 align:start position:0% ports uh when we look at them in just a minute 04:41:57.948 --> 04:41:57.958 align:start position:0% minute 04:41:57.958 --> 04:42:00.890 align:start position:0% minute these<04:41:58.560> are<04:41:58.680> used<04:41:58.860> by<04:41:59.280> Common<04:41:59.520> services<04:41:59.940> and 04:42:00.890 --> 04:42:00.900 align:start position:0% these are used by Common services and 04:42:00.900 --> 04:42:02.930 align:start position:0% these are used by Common services and are<04:42:01.260> pretty<04:42:01.620> much<04:42:01.740> known<04:42:02.340> by<04:42:02.638> just<04:42:02.820> about 04:42:02.930 --> 04:42:02.940 align:start position:0% are pretty much known by just about 04:42:02.940 --> 04:42:04.550 align:start position:0% are pretty much known by just about everyone<04:42:03.298> in<04:42:03.600> the<04:42:03.718> field 04:42:04.550 --> 04:42:04.560 align:start position:0% everyone in the field 04:42:04.560 --> 04:42:06.350 align:start position:0% everyone in the field now<04:42:04.980> the<04:42:05.218> next<04:42:05.340> range<04:42:05.638> of<04:42:05.760> ports<04:42:06.000> is<04:42:06.180> called 04:42:06.350 --> 04:42:06.360 align:start position:0% now the next range of ports is called 04:42:06.360 --> 04:42:08.690 align:start position:0% now the next range of ports is called the<04:42:06.660> registered<04:42:07.080> ports<04:42:07.500> range<04:42:07.798> these<04:42:08.458> span 04:42:08.690 --> 04:42:08.700 align:start position:0% the registered ports range these span 04:42:08.700 --> 04:42:11.770 align:start position:0% the registered ports range these span from<04:42:08.958> 1024<04:42:09.958> to<04:42:10.560> 49 04:42:11.770 --> 04:42:11.780 align:start position:0% from 1024 to 49 04:42:11.780 --> 04:42:15.230 align:start position:0% from 1024 to 49 151.<04:42:12.780> these<04:42:13.620> are<04:42:13.740> reserved<04:42:14.218> by<04:42:14.520> applications 04:42:15.230 --> 04:42:15.240 align:start position:0% 151. these are reserved by applications 04:42:15.240 --> 04:42:19.150 align:start position:0% 151. these are reserved by applications and<04:42:16.020> programs<04:42:16.740> that<04:42:17.040> register<04:42:17.458> with<04:42:17.820> the<04:42:18.060> Iana 04:42:19.150 --> 04:42:19.160 align:start position:0% and programs that register with the Iana 04:42:19.160 --> 04:42:22.730 align:start position:0% and programs that register with the Iana an<04:42:20.160> example<04:42:20.520> might<04:42:20.940> be<04:42:21.180> for<04:42:21.540> instance 04:42:22.730 --> 04:42:22.740 align:start position:0% an example might be for instance 04:42:22.740 --> 04:42:25.490 align:start position:0% an example might be for instance Skype 04:42:25.490 --> 04:42:25.500 align:start position:0% 04:42:25.500 --> 04:42:28.610 align:start position:0% which<04:42:26.160> registers<04:42:26.760> and<04:42:27.180> utilizes<04:42:27.780> Port<04:42:28.260> I 04:42:28.610 --> 04:42:28.620 align:start position:0% which registers and utilizes Port I 04:42:28.620 --> 04:42:30.128 align:start position:0% which registers and utilizes Port I think 04:42:30.128 --> 04:42:30.138 align:start position:0% think 04:42:30.138 --> 04:42:34.190 align:start position:0% think 23399<04:42:31.138> as<04:42:31.980> its<04:42:32.458> default<04:42:32.760> protocol<04:42:33.240> don't 04:42:34.190 --> 04:42:34.200 align:start position:0% 23399 as its default protocol don't 04:42:34.200 --> 04:42:35.930 align:start position:0% 23399 as its default protocol don't worry<04:42:34.500> about<04:42:34.798> that<04:42:35.040> but<04:42:35.340> if<04:42:35.520> you're<04:42:35.638> curious 04:42:35.930 --> 04:42:35.940 align:start position:0% worry about that but if you're curious 04:42:35.940 --> 04:42:38.090 align:start position:0% worry about that but if you're curious for<04:42:36.360> your<04:42:36.540> firewall's<04:42:37.320> sake<04:42:37.440> this<04:42:37.920> is<04:42:37.980> the 04:42:38.090 --> 04:42:38.100 align:start position:0% for your firewall's sake this is the 04:42:38.100 --> 04:42:40.070 align:start position:0% for your firewall's sake this is the port<04:42:38.218> I<04:42:38.520> believe<04:42:38.638> Skype<04:42:39.120> uses 04:42:40.070 --> 04:42:40.080 align:start position:0% port I believe Skype uses 04:42:40.080 --> 04:42:42.948 align:start position:0% port I believe Skype uses finally<04:42:40.860> we<04:42:41.340> have<04:42:41.458> the<04:42:41.760> dynamic<04:42:42.298> or<04:42:42.718> the 04:42:42.948 --> 04:42:42.958 align:start position:0% finally we have the dynamic or the 04:42:42.958 --> 04:42:45.230 align:start position:0% finally we have the dynamic or the private<04:42:43.440> Port<04:42:43.620> range<04:42:44.160> this<04:42:44.700> is<04:42:44.878> everything 04:42:45.230 --> 04:42:45.240 align:start position:0% private Port range this is everything 04:42:45.240 --> 04:42:51.110 align:start position:0% private Port range this is everything else<04:42:45.540> 49<04:42:46.218> 152<04:42:47.218> to<04:42:47.820> 65<04:42:48.860> 535.<04:42:49.860> these<04:42:50.520> are<04:42:50.638> used<04:42:50.820> by 04:42:51.110 --> 04:42:51.120 align:start position:0% else 49 152 to 65 535. these are used by 04:42:51.120 --> 04:42:54.230 align:start position:0% else 49 152 to 65 535. these are used by unregistered<04:42:51.840> services<04:42:52.340> in<04:42:53.340> uh<04:42:53.820> test 04:42:54.230 --> 04:42:54.240 align:start position:0% unregistered services in uh test 04:42:54.240 --> 04:42:56.150 align:start position:0% unregistered services in uh test settings<04:42:54.540> and<04:42:55.138> also<04:42:55.378> for<04:42:55.680> temporary 04:42:56.150 --> 04:42:56.160 align:start position:0% settings and also for temporary 04:42:56.160 --> 04:42:58.190 align:start position:0% settings and also for temporary connections<04:42:56.878> you<04:42:57.360> can't<04:42:57.480> register<04:42:57.900> these 04:42:58.190 --> 04:42:58.200 align:start position:0% connections you can't register these 04:42:58.200 --> 04:43:00.948 align:start position:0% connections you can't register these with<04:42:58.378> the<04:42:58.500> Ina<04:42:59.040> they're<04:42:59.580> just<04:42:59.760> left<04:43:00.060> open<04:43:00.360> for 04:43:00.948 --> 04:43:00.958 align:start position:0% with the Ina they're just left open for 04:43:00.958 --> 04:43:03.350 align:start position:0% with the Ina they're just left open for anyone<04:43:01.320> to<04:43:01.560> use<04:43:01.798> for<04:43:02.400> whatever<04:43:02.520> purposes<04:43:03.120> you 04:43:03.350 --> 04:43:03.360 align:start position:0% anyone to use for whatever purposes you 04:43:03.360 --> 04:43:04.430 align:start position:0% anyone to use for whatever purposes you may<04:43:03.480> need<04:43:03.660> them 04:43:04.430 --> 04:43:04.440 align:start position:0% may need them 04:43:04.440 --> 04:43:06.708 align:start position:0% may need them so<04:43:04.920> now<04:43:05.040> let's<04:43:05.218> talk<04:43:05.520> about<04:43:05.940> the<04:43:06.360> well-known 04:43:06.708 --> 04:43:06.718 align:start position:0% so now let's talk about the well-known 04:43:06.718 --> 04:43:08.510 align:start position:0% so now let's talk about the well-known default<04:43:07.200> ports<04:43:07.680> you<04:43:07.798> need<04:43:07.920> to<04:43:08.040> know<04:43:08.160> for<04:43:08.400> the 04:43:08.510 --> 04:43:08.520 align:start position:0% default ports you need to know for the 04:43:08.520 --> 04:43:11.030 align:start position:0% default ports you need to know for the exam<04:43:08.820> this<04:43:09.718> chart<04:43:09.958> is<04:43:10.378> really<04:43:10.560> what<04:43:10.860> you 04:43:11.030 --> 04:43:11.040 align:start position:0% exam this chart is really what you 04:43:11.040 --> 04:43:13.550 align:start position:0% exam this chart is really what you should<04:43:11.218> commit<04:43:11.580> to<04:43:11.760> memory<04:43:12.120> since<04:43:12.900> uh<04:43:13.440> and 04:43:13.550 --> 04:43:13.560 align:start position:0% should commit to memory since uh and 04:43:13.560 --> 04:43:15.590 align:start position:0% should commit to memory since uh and when<04:43:13.980> you<04:43:14.100> get<04:43:14.280> to<04:43:14.400> the<04:43:14.580> test<04:43:14.820> you<04:43:15.180> want<04:43:15.298> to<04:43:15.420> be 04:43:15.590 --> 04:43:15.600 align:start position:0% when you get to the test you want to be 04:43:15.600 --> 04:43:18.230 align:start position:0% when you get to the test you want to be able<04:43:15.840> to<04:43:16.260> basically<04:43:16.920> recreate<04:43:17.700> this<04:43:18.060> chart 04:43:18.230 --> 04:43:18.240 align:start position:0% able to basically recreate this chart 04:43:18.240 --> 04:43:19.910 align:start position:0% able to basically recreate this chart before<04:43:18.540> you<04:43:18.840> sit<04:43:18.958> down<04:43:19.138> and<04:43:19.378> take<04:43:19.560> the<04:43:19.740> test 04:43:19.910 --> 04:43:19.920 align:start position:0% before you sit down and take the test 04:43:19.920 --> 04:43:21.350 align:start position:0% before you sit down and take the test you'll<04:43:20.520> be<04:43:20.638> able<04:43:20.700> to<04:43:20.820> do<04:43:20.940> this<04:43:21.060> in<04:43:21.240> what's 04:43:21.350 --> 04:43:21.360 align:start position:0% you'll be able to do this in what's 04:43:21.360 --> 04:43:24.230 align:start position:0% you'll be able to do this in what's called<04:43:21.600> a<04:43:21.840> brain<04:43:22.138> dump<04:43:22.440> sheet<04:43:23.218> so<04:43:23.820> let's<04:43:24.000> talk 04:43:24.230 --> 04:43:24.240 align:start position:0% called a brain dump sheet so let's talk 04:43:24.240 --> 04:43:25.670 align:start position:0% called a brain dump sheet so let's talk about<04:43:24.360> the<04:43:24.600> first<04:43:24.780> portion<04:43:25.138> of<04:43:25.260> these<04:43:25.378> ports 04:43:25.670 --> 04:43:25.680 align:start position:0% about the first portion of these ports 04:43:25.680 --> 04:43:28.550 align:start position:0% about the first portion of these ports we<04:43:25.798> need<04:43:25.980> to<04:43:26.040> know<04:43:26.218> the<04:43:26.940> first<04:43:27.120> is<04:43:27.718> Port<04:43:27.958> 7. 04:43:28.550 --> 04:43:28.560 align:start position:0% we need to know the first is Port 7. 04:43:28.560 --> 04:43:31.970 align:start position:0% we need to know the first is Port 7. this<04:43:29.280> is<04:43:29.458> for<04:43:29.700> the<04:43:29.940> icmp<04:43:30.780> echo<04:43:31.260> request<04:43:31.560> or 04:43:31.970 --> 04:43:31.980 align:start position:0% this is for the icmp echo request or 04:43:31.980 --> 04:43:34.070 align:start position:0% this is for the icmp echo request or ping<04:43:32.340> if<04:43:32.760> you've<04:43:33.000> ever<04:43:33.180> pinged<04:43:33.840> something 04:43:34.070 --> 04:43:34.080 align:start position:0% ping if you've ever pinged something 04:43:34.080 --> 04:43:35.930 align:start position:0% ping if you've ever pinged something from<04:43:34.440> the<04:43:34.560> command<04:43:34.860> line<04:43:35.040> this<04:43:35.520> is<04:43:35.638> what<04:43:35.820> we're 04:43:35.930 --> 04:43:35.940 align:start position:0% from the command line this is what we're 04:43:35.940 --> 04:43:38.030 align:start position:0% from the command line this is what we're talking<04:43:36.120> about<04:43:36.360> we'll<04:43:37.080> talk<04:43:37.320> more<04:43:37.500> about<04:43:37.740> this 04:43:38.030 --> 04:43:38.040 align:start position:0% talking about we'll talk more about this 04:43:38.040 --> 04:43:39.470 align:start position:0% talking about we'll talk more about this a<04:43:38.280> little<04:43:38.340> bit<04:43:38.520> later 04:43:39.470 --> 04:43:39.480 align:start position:0% a little bit later 04:43:39.480 --> 04:43:43.910 align:start position:0% a little bit later next<04:43:40.138> we<04:43:40.560> have<04:43:40.740> Port<04:43:41.218> 20<04:43:41.580> and<04:43:42.120> 21.<04:43:42.900> these<04:43:43.740> are 04:43:43.910 --> 04:43:43.920 align:start position:0% next we have Port 20 and 21. these are 04:43:43.920 --> 04:43:46.610 align:start position:0% next we have Port 20 and 21. these are for<04:43:44.280> the<04:43:44.520> FTP<04:43:45.060> or<04:43:45.298> file<04:43:45.660> transfer<04:43:46.200> protocol 04:43:46.610 --> 04:43:46.620 align:start position:0% for the FTP or file transfer protocol 04:43:46.620 --> 04:43:49.670 align:start position:0% for the FTP or file transfer protocol which<04:43:47.400> allows<04:43:47.820> you<04:43:47.940> to<04:43:48.360> transfer<04:43:48.780> files<04:43:49.260> over 04:43:49.670 --> 04:43:49.680 align:start position:0% which allows you to transfer files over 04:43:49.680 --> 04:43:51.948 align:start position:0% which allows you to transfer files over a<04:43:49.980> network<04:43:50.160> we'll<04:43:50.820> talk<04:43:51.060> more<04:43:51.240> about<04:43:51.480> this<04:43:51.718> in 04:43:51.948 --> 04:43:51.958 align:start position:0% a network we'll talk more about this in 04:43:51.958 --> 04:43:53.150 align:start position:0% a network we'll talk more about this in just<04:43:52.080> a<04:43:52.260> minute 04:43:53.150 --> 04:43:53.160 align:start position:0% just a minute 04:43:53.160 --> 04:43:56.690 align:start position:0% just a minute Port<04:43:53.760> 22<04:43:54.420> is<04:43:54.900> for<04:43:55.138> the<04:43:55.378> secure<04:43:55.740> shell<04:43:56.100> or<04:43:56.340> SSH 04:43:56.690 --> 04:43:56.700 align:start position:0% Port 22 is for the secure shell or SSH 04:43:56.700 --> 04:44:00.288 align:start position:0% Port 22 is for the secure shell or SSH and<04:43:57.540> Port<04:43:57.718> 23<04:43:58.260> is<04:43:58.620> for<04:43:58.860> telnet<04:43:59.400> both<04:44:00.000> of<04:44:00.180> those 04:44:00.288 --> 04:44:00.298 align:start position:0% and Port 23 is for telnet both of those 04:44:00.298 --> 04:44:02.208 align:start position:0% and Port 23 is for telnet both of those we're<04:44:00.540> going<04:44:00.718> to<04:44:00.840> discuss<04:44:01.138> later<04:44:01.620> on<04:44:01.860> in<04:44:02.100> a 04:44:02.208 --> 04:44:02.218 align:start position:0% we're going to discuss later on in a 04:44:02.218 --> 04:44:04.010 align:start position:0% we're going to discuss later on in a different<04:44:02.340> module<04:44:02.940> but<04:44:03.360> they're<04:44:03.600> sort<04:44:03.900> of 04:44:04.010 --> 04:44:04.020 align:start position:0% different module but they're sort of 04:44:04.020 --> 04:44:06.590 align:start position:0% different module but they're sort of allowing<04:44:04.440> you<04:44:04.620> to<04:44:04.980> remote<04:44:05.340> in<04:44:05.700> and<04:44:06.060> control<04:44:06.298> a 04:44:06.590 --> 04:44:06.600 align:start position:0% allowing you to remote in and control a 04:44:06.600 --> 04:44:09.230 align:start position:0% allowing you to remote in and control a remote<04:44:06.780> computer<04:44:07.080> albeit<04:44:08.040> not<04:44:08.400> from<04:44:09.000> a 04:44:09.230 --> 04:44:09.240 align:start position:0% remote computer albeit not from a 04:44:09.240 --> 04:44:10.910 align:start position:0% remote computer albeit not from a graphical<04:44:09.600> standpoint 04:44:10.910 --> 04:44:10.920 align:start position:0% graphical standpoint 04:44:10.920 --> 04:44:14.570 align:start position:0% graphical standpoint Port<04:44:11.520> 25<04:44:11.940> is<04:44:12.660> the<04:44:12.900> SMTP<04:44:13.620> or<04:44:14.040> simple<04:44:14.280> mail 04:44:14.570 --> 04:44:14.580 align:start position:0% Port 25 is the SMTP or simple mail 04:44:14.580 --> 04:44:16.930 align:start position:0% Port 25 is the SMTP or simple mail transfer<04:44:15.120> protocol<04:44:15.480> which<04:44:16.020> allows<04:44:16.378> you<04:44:16.500> to 04:44:16.930 --> 04:44:16.940 align:start position:0% transfer protocol which allows you to 04:44:16.940 --> 04:44:21.530 align:start position:0% transfer protocol which allows you to receive<04:44:17.940> email<04:44:18.560> and<04:44:19.560> DNS<04:44:20.160> or<04:44:20.638> the<04:44:20.878> domain<04:44:21.298> name 04:44:21.530 --> 04:44:21.540 align:start position:0% receive email and DNS or the domain name 04:44:21.540 --> 04:44:24.650 align:start position:0% receive email and DNS or the domain name service<04:44:21.900> which<04:44:22.440> uses<04:44:22.740> Port<04:44:23.040> 53<04:44:23.760> is<04:44:24.420> what 04:44:24.650 --> 04:44:24.660 align:start position:0% service which uses Port 53 is what 04:44:24.660 --> 04:44:27.788 align:start position:0% service which uses Port 53 is what allows<04:44:25.080> you<04:44:25.260> to<04:44:25.620> transmit<04:44:26.340> or<04:44:27.180> to<04:44:27.360> translate 04:44:27.788 --> 04:44:27.798 align:start position:0% allows you to transmit or to translate 04:44:27.798 --> 04:44:31.850 align:start position:0% allows you to transmit or to translate say<04:44:28.798> google.com<04:44:29.520> into<04:44:30.298> its<04:44:30.780> IP<04:44:31.020> address<04:44:31.260> when 04:44:31.850 --> 04:44:31.860 align:start position:0% say google.com into its IP address when 04:44:31.860 --> 04:44:33.708 align:start position:0% say google.com into its IP address when you're<04:44:32.040> browsing<04:44:32.340> out<04:44:32.520> on<04:44:32.700> the<04:44:32.820> internet<04:44:32.940> this 04:44:33.708 --> 04:44:33.718 align:start position:0% you're browsing out on the internet this 04:44:33.718 --> 04:44:35.690 align:start position:0% you're browsing out on the internet this is<04:44:33.840> a<04:44:34.138> really<04:44:34.320> important<04:44:34.798> protocol<04:44:35.160> and<04:44:35.580> we'll 04:44:35.690 --> 04:44:35.700 align:start position:0% is a really important protocol and we'll 04:44:35.700 --> 04:44:37.970 align:start position:0% is a really important protocol and we'll talk<04:44:35.878> more<04:44:36.060> about<04:44:36.240> it<04:44:36.480> later<04:44:36.718> along<04:44:37.378> with<04:44:37.740> the 04:44:37.970 --> 04:44:37.980 align:start position:0% talk more about it later along with the 04:44:37.980 --> 04:44:40.550 align:start position:0% talk more about it later along with the the<04:44:38.280> DNS<04:44:38.760> sort<04:44:39.120> of<04:44:39.240> server 04:44:40.550 --> 04:44:40.560 align:start position:0% the DNS sort of server 04:44:40.560 --> 04:44:45.490 align:start position:0% the DNS sort of server Port<04:44:41.480> 67<04:44:42.480> and<04:44:43.260> 68<04:44:43.980> are<04:44:44.580> for<04:44:44.760> what<04:44:45.060> are<04:44:45.240> called 04:44:45.490 --> 04:44:45.500 align:start position:0% Port 67 and 68 are for what are called 04:44:45.500 --> 04:44:49.190 align:start position:0% Port 67 and 68 are for what are called DHCP<04:44:46.500> and<04:44:46.920> boot<04:44:47.280> P<04:44:47.458> or<04:44:47.820> the<04:44:48.060> bootstrap<04:44:48.840> service 04:44:49.190 --> 04:44:49.200 align:start position:0% DHCP and boot P or the bootstrap service 04:44:49.200 --> 04:44:51.830 align:start position:0% DHCP and boot P or the bootstrap service for<04:44:49.620> servers<04:44:50.040> and<04:44:50.280> client<04:44:50.520> respectively 04:44:51.830 --> 04:44:51.840 align:start position:0% for servers and client respectively 04:44:51.840 --> 04:44:56.570 align:start position:0% for servers and client respectively one<04:44:52.680> for<04:44:52.980> uh<04:44:53.760> servers<04:44:54.780> and<04:44:55.378> one<04:44:55.620> for<04:44:55.920> clients 04:44:56.570 --> 04:44:56.580 align:start position:0% one for uh servers and one for clients 04:44:56.580 --> 04:44:58.010 align:start position:0% one for uh servers and one for clients as<04:44:56.940> we<04:44:57.120> can<04:44:57.240> see 04:44:58.010 --> 04:44:58.020 align:start position:0% as we can see 04:44:58.020 --> 04:45:00.170 align:start position:0% as we can see right<04:44:58.500> here 04:45:00.170 --> 04:45:00.180 align:start position:0% right here 04:45:00.180 --> 04:45:01.788 align:start position:0% right here we're<04:45:00.540> going<04:45:00.718> to<04:45:00.780> Define<04:45:00.958> and<04:45:01.260> describe<04:45:01.680> those 04:45:01.788 --> 04:45:01.798 align:start position:0% we're going to Define and describe those 04:45:01.798 --> 04:45:04.430 align:start position:0% we're going to Define and describe those in<04:45:02.040> more<04:45:02.218> detail<04:45:02.520> in<04:45:02.878> the<04:45:03.000> next<04:45:03.240> lesson 04:45:04.430 --> 04:45:04.440 align:start position:0% in more detail in the next lesson 04:45:04.440 --> 04:45:08.090 align:start position:0% in more detail in the next lesson now<04:45:04.920> Port<04:45:05.340> 69<04:45:06.000> is<04:45:06.420> the<04:45:06.718> trivial<04:45:07.138> file<04:45:07.560> transfer 04:45:08.090 --> 04:45:08.100 align:start position:0% now Port 69 is the trivial file transfer 04:45:08.100 --> 04:45:10.850 align:start position:0% now Port 69 is the trivial file transfer protocol<04:45:08.458> this<04:45:09.298> is<04:45:09.420> related<04:45:09.840> to<04:45:10.500> the<04:45:10.680> file 04:45:10.850 --> 04:45:10.860 align:start position:0% protocol this is related to the file 04:45:10.860 --> 04:45:13.010 align:start position:0% protocol this is related to the file transfer<04:45:11.400> protocol<04:45:11.760> we<04:45:12.240> mentioned<04:45:12.540> up<04:45:12.780> here 04:45:13.010 --> 04:45:13.020 align:start position:0% transfer protocol we mentioned up here 04:45:13.020 --> 04:45:16.610 align:start position:0% transfer protocol we mentioned up here but<04:45:13.798> it<04:45:13.980> is<04:45:14.160> Trivial<04:45:14.638> meaning<04:45:15.298> that<04:45:15.660> it<04:45:15.900> is<04:45:16.080> not 04:45:16.610 --> 04:45:16.620 align:start position:0% but it is Trivial meaning that it is not 04:45:16.620 --> 04:45:19.910 align:start position:0% but it is Trivial meaning that it is not a<04:45:17.160> connection<04:45:17.458> oriented<04:45:18.360> and<04:45:18.958> doesn't<04:45:19.200> really 04:45:19.910 --> 04:45:19.920 align:start position:0% a connection oriented and doesn't really 04:45:19.920 --> 04:45:22.010 align:start position:0% a connection oriented and doesn't really guarantee<04:45:20.700> that<04:45:21.240> the<04:45:21.360> file<04:45:21.600> has<04:45:21.840> been 04:45:22.010 --> 04:45:22.020 align:start position:0% guarantee that the file has been 04:45:22.020 --> 04:45:23.330 align:start position:0% guarantee that the file has been transferred 04:45:23.330 --> 04:45:23.340 align:start position:0% transferred 04:45:23.340 --> 04:45:27.050 align:start position:0% transferred Port<04:45:24.060> 123<04:45:24.958> is<04:45:25.440> the<04:45:25.680> network<04:45:25.980> time<04:45:26.520> protocol 04:45:27.050 --> 04:45:27.060 align:start position:0% Port 123 is the network time protocol 04:45:27.060 --> 04:45:30.230 align:start position:0% Port 123 is the network time protocol which<04:45:27.540> keeps<04:45:27.958> the<04:45:28.378> clock<04:45:28.620> on<04:45:29.040> a<04:45:29.218> network<04:45:29.458> or<04:45:30.060> on 04:45:30.230 --> 04:45:30.240 align:start position:0% which keeps the clock on a network or on 04:45:30.240 --> 04:45:32.270 align:start position:0% which keeps the clock on a network or on computers<04:45:30.600> on<04:45:30.780> the<04:45:30.900> network<04:45:31.020> up<04:45:31.378> to<04:45:31.560> sync<04:45:31.920> a 04:45:32.270 --> 04:45:32.280 align:start position:0% computers on the network up to sync a 04:45:32.280 --> 04:45:33.830 align:start position:0% computers on the network up to sync a great<04:45:32.400> way<04:45:32.520> to<04:45:32.760> remember<04:45:32.878> this<04:45:33.180> is<04:45:33.420> that<04:45:33.600> time 04:45:33.830 --> 04:45:33.840 align:start position:0% great way to remember this is that time 04:45:33.840 --> 04:45:38.030 align:start position:0% great way to remember this is that time is<04:45:34.138> always<04:45:34.378> counting<04:45:34.980> one<04:45:35.820> two<04:45:36.360> three 04:45:38.030 --> 04:45:38.040 align:start position:0% is always counting one two three 04:45:38.040 --> 04:45:41.448 align:start position:0% is always counting one two three uh<04:45:38.820> Port<04:45:39.120> 110<04:45:39.840> is<04:45:40.200> for<04:45:40.440> the<04:45:40.620> pop<04:45:40.798> three<04:45:41.040> or<04:45:41.280> the 04:45:41.448 --> 04:45:41.458 align:start position:0% uh Port 110 is for the pop three or the 04:45:41.458 --> 04:45:43.550 align:start position:0% uh Port 110 is for the pop three or the post<04:45:41.638> office<04:45:41.878> protocol<04:45:42.420> which<04:45:43.020> is<04:45:43.138> how<04:45:43.378> many 04:45:43.550 --> 04:45:43.560 align:start position:0% post office protocol which is how many 04:45:43.560 --> 04:45:46.310 align:start position:0% post office protocol which is how many of<04:45:43.740> us<04:45:43.920> download<04:45:44.700> our<04:45:45.120> email<04:45:45.298> onto<04:45:45.840> our<04:45:46.080> local 04:45:46.310 --> 04:45:46.320 align:start position:0% of us download our email onto our local 04:45:46.320 --> 04:45:48.110 align:start position:0% of us download our email onto our local device 04:45:48.110 --> 04:45:48.120 align:start position:0% device 04:45:48.120 --> 04:45:51.948 align:start position:0% device and<04:45:48.600> then<04:45:48.718> Port<04:45:49.138> 137<04:45:50.040> is<04:45:50.580> the<04:45:50.760> net<04:45:50.940> bios<04:45:51.420> naming 04:45:51.948 --> 04:45:51.958 align:start position:0% and then Port 137 is the net bios naming 04:45:51.958 --> 04:45:56.090 align:start position:0% and then Port 137 is the net bios naming service<04:45:52.340> this<04:45:53.340> is<04:45:53.580> similar<04:45:54.120> to<04:45:54.540> DNS<04:45:55.260> but<04:45:55.920> is 04:45:56.090 --> 04:45:56.100 align:start position:0% service this is similar to DNS but is 04:45:56.100 --> 04:45:59.150 align:start position:0% service this is similar to DNS but is specific<04:45:56.520> to<04:45:57.000> Windows<04:45:57.780> operating<04:45:58.320> systems<04:45:58.860> or 04:45:59.150 --> 04:45:59.160 align:start position:0% specific to Windows operating systems or 04:45:59.160 --> 04:46:01.490 align:start position:0% specific to Windows operating systems or Microsoft<04:45:59.638> operating<04:46:00.180> systems 04:46:01.490 --> 04:46:01.500 align:start position:0% Microsoft operating systems 04:46:01.500 --> 04:46:05.390 align:start position:0% Microsoft operating systems related<04:46:02.218> to<04:46:02.520> pop<04:46:02.700> 3<04:46:03.000> is<04:46:03.600> Port<04:46:03.840> 143<04:46:04.740> which<04:46:05.280> is 04:46:05.390 --> 04:46:05.400 align:start position:0% related to pop 3 is Port 143 which is 04:46:05.400 --> 04:46:07.368 align:start position:0% related to pop 3 is Port 143 which is IMAP<04:46:05.940> the<04:46:06.240> internet<04:46:06.360> message<04:46:06.958> access 04:46:07.368 --> 04:46:07.378 align:start position:0% IMAP the internet message access 04:46:07.378 --> 04:46:09.650 align:start position:0% IMAP the internet message access protocol<04:46:07.980> this<04:46:08.878> is<04:46:09.000> another<04:46:09.180> way<04:46:09.480> of 04:46:09.650 --> 04:46:09.660 align:start position:0% protocol this is another way of 04:46:09.660 --> 04:46:13.550 align:start position:0% protocol this is another way of accessing<04:46:10.260> and<04:46:10.560> managing<04:46:11.240> your<04:46:12.240> email<04:46:12.600> let's 04:46:13.550 --> 04:46:13.560 align:start position:0% accessing and managing your email let's 04:46:13.560 --> 04:46:15.590 align:start position:0% accessing and managing your email let's continue<04:46:14.040> taking<04:46:14.520> a<04:46:14.700> look<04:46:14.820> at<04:46:15.000> a<04:46:15.180> few<04:46:15.298> more 04:46:15.590 --> 04:46:15.600 align:start position:0% continue taking a look at a few more 04:46:15.600 --> 04:46:19.670 align:start position:0% continue taking a look at a few more protocols<04:46:16.260> that<04:46:16.860> are<04:46:17.040> equally<04:46:17.400> important 04:46:19.670 --> 04:46:19.680 align:start position:0% protocols that are equally important 04:46:19.680 --> 04:46:21.470 align:start position:0% protocols that are equally important the<04:46:20.160> first<04:46:20.340> is<04:46:20.700> the<04:46:20.940> simple<04:46:21.120> Network 04:46:21.470 --> 04:46:21.480 align:start position:0% the first is the simple Network 04:46:21.480 --> 04:46:23.868 align:start position:0% the first is the simple Network management<04:46:22.020> protocol<04:46:22.680> which<04:46:23.218> allows<04:46:23.580> you<04:46:23.638> to 04:46:23.868 --> 04:46:23.878 align:start position:0% management protocol which allows you to 04:46:23.878 --> 04:46:26.990 align:start position:0% management protocol which allows you to manage<04:46:24.180> devices<04:46:24.540> on<04:46:24.900> network<04:46:25.138> Say<04:46:25.920> by<04:46:26.280> getting 04:46:26.990 --> 04:46:27.000 align:start position:0% manage devices on network Say by getting 04:46:27.000 --> 04:46:29.510 align:start position:0% manage devices on network Say by getting error<04:46:27.718> messages<04:46:27.840> from<04:46:28.440> your<04:46:28.680> printer<04:46:28.980> or<04:46:29.280> from 04:46:29.510 --> 04:46:29.520 align:start position:0% error messages from your printer or from 04:46:29.520 --> 04:46:32.690 align:start position:0% error messages from your printer or from a<04:46:29.700> router<04:46:30.060> this<04:46:30.600> uses<04:46:30.958> Port<04:46:31.580> 161.<04:46:32.580> we'll 04:46:32.690 --> 04:46:32.700 align:start position:0% a router this uses Port 161. we'll 04:46:32.700 --> 04:46:34.610 align:start position:0% a router this uses Port 161. we'll discuss<04:46:33.120> this<04:46:33.420> a<04:46:33.600> lot<04:46:33.718> more<04:46:33.900> in<04:46:34.138> detail<04:46:34.378> later 04:46:34.610 --> 04:46:34.620 align:start position:0% discuss this a lot more in detail later 04:46:34.620 --> 04:46:35.690 align:start position:0% discuss this a lot more in detail later as<04:46:34.860> well 04:46:35.690 --> 04:46:35.700 align:start position:0% as well 04:46:35.700 --> 04:46:39.410 align:start position:0% as well port<04:46:36.360> 389<04:46:37.080> is<04:46:37.500> the<04:46:37.860> lightweight<04:46:38.458> directory 04:46:39.410 --> 04:46:39.420 align:start position:0% port 389 is the lightweight directory 04:46:39.420 --> 04:46:42.230 align:start position:0% port 389 is the lightweight directory access<04:46:39.660> protocol<04:46:40.260> this<04:46:40.980> is<04:46:41.040> what<04:46:41.280> allows<04:46:41.760> a 04:46:42.230 --> 04:46:42.240 align:start position:0% access protocol this is what allows a 04:46:42.240 --> 04:46:45.708 align:start position:0% access protocol this is what allows a Windows<04:46:42.718> server<04:46:43.200> to<04:46:43.740> have<04:46:44.060> usernames<04:46:45.060> and 04:46:45.708 --> 04:46:45.718 align:start position:0% Windows server to have usernames and 04:46:45.718 --> 04:46:47.990 align:start position:0% Windows server to have usernames and passwords 04:46:47.990 --> 04:46:48.000 align:start position:0% passwords 04:46:48.000 --> 04:46:52.550 align:start position:0% passwords Port<04:46:48.540> 443<04:46:49.378> is<04:46:50.160> https<04:46:50.940> or<04:46:51.660> the<04:46:51.900> hypertext 04:46:52.550 --> 04:46:52.560 align:start position:0% Port 443 is https or the hypertext 04:46:52.560 --> 04:46:55.670 align:start position:0% Port 443 is https or the hypertext transfer<04:46:53.160> protocol<04:46:53.520> over<04:46:54.360> secure<04:46:55.138> socket 04:46:55.670 --> 04:46:55.680 align:start position:0% transfer protocol over secure socket 04:46:55.680 --> 04:46:58.970 align:start position:0% transfer protocol over secure socket layer<04:46:56.040> notice<04:46:56.878> the<04:46:57.120> S<04:46:57.420> here<04:46:57.680> this<04:46:58.680> is<04:46:58.798> what 04:46:58.970 --> 04:46:58.980 align:start position:0% layer notice the S here this is what 04:46:58.980 --> 04:47:02.030 align:start position:0% layer notice the S here this is what allows<04:46:59.638> us<04:46:59.760> to<04:47:00.240> browse<04:47:00.958> the<04:47:01.138> internet<04:47:01.320> but 04:47:02.030 --> 04:47:02.040 align:start position:0% allows us to browse the internet but 04:47:02.040 --> 04:47:03.590 align:start position:0% allows us to browse the internet but securely 04:47:03.590 --> 04:47:03.600 align:start position:0% securely 04:47:03.600 --> 04:47:07.788 align:start position:0% securely we<04:47:04.138> also<04:47:04.440> have<04:47:04.680> Port<04:47:05.100> 500<04:47:05.820> which<04:47:06.600> is<04:47:06.798> ipsec 04:47:07.788 --> 04:47:07.798 align:start position:0% we also have Port 500 which is ipsec 04:47:07.798 --> 04:47:09.830 align:start position:0% we also have Port 500 which is ipsec this<04:47:08.340> one<04:47:08.458> also<04:47:08.760> has<04:47:08.940> another<04:47:09.240> name<04:47:09.540> which 04:47:09.830 --> 04:47:09.840 align:start position:0% this one also has another name which 04:47:09.840 --> 04:47:11.930 align:start position:0% this one also has another name which stands<04:47:10.080> for<04:47:10.260> Internet<04:47:10.500> Security<04:47:10.940> Association 04:47:11.930 --> 04:47:11.940 align:start position:0% stands for Internet Security Association 04:47:11.940 --> 04:47:14.628 align:start position:0% stands for Internet Security Association and<04:47:12.360> Key<04:47:12.600> Management<04:47:12.840> protocol<04:47:13.638> basically 04:47:14.628 --> 04:47:14.638 align:start position:0% and Key Management protocol basically 04:47:14.638 --> 04:47:17.930 align:start position:0% and Key Management protocol basically ipsec<04:47:15.540> or<04:47:15.660> IP<04:47:16.020> security<04:47:16.378> is<04:47:17.218> what<04:47:17.458> allows<04:47:17.820> us 04:47:17.930 --> 04:47:17.940 align:start position:0% ipsec or IP security is what allows us 04:47:17.940 --> 04:47:22.310 align:start position:0% ipsec or IP security is what allows us to<04:47:18.180> have<04:47:18.420> secure<04:47:18.958> connections<04:47:19.740> over<04:47:20.340> IP 04:47:22.310 --> 04:47:22.320 align:start position:0% to have secure connections over IP 04:47:22.320 --> 04:47:25.310 align:start position:0% to have secure connections over IP finally<04:47:23.160> we're<04:47:23.638> going<04:47:23.878> into<04:47:24.180> RDP<04:47:24.958> or<04:47:25.200> the 04:47:25.310 --> 04:47:25.320 align:start position:0% finally we're going into RDP or the 04:47:25.320 --> 04:47:27.470 align:start position:0% finally we're going into RDP or the remote<04:47:25.500> desktop<04:47:26.100> protocol<04:47:26.580> which<04:47:27.120> allows<04:47:27.360> us 04:47:27.470 --> 04:47:27.480 align:start position:0% remote desktop protocol which allows us 04:47:27.480 --> 04:47:30.948 align:start position:0% remote desktop protocol which allows us to<04:47:27.718> remotely<04:47:28.080> access<04:47:28.500> a<04:47:29.160> computer<04:47:29.958> Windows 04:47:30.948 --> 04:47:30.958 align:start position:0% to remotely access a computer Windows 04:47:30.958 --> 04:47:32.868 align:start position:0% to remotely access a computer Windows based<04:47:31.378> specifically 04:47:32.868 --> 04:47:32.878 align:start position:0% based specifically 04:47:32.878 --> 04:47:37.010 align:start position:0% based specifically Port<04:47:33.480> 119<04:47:34.260> or<04:47:34.798> the<04:47:35.160> network<04:47:35.700> news<04:47:36.360> transfer 04:47:37.010 --> 04:47:37.020 align:start position:0% Port 119 or the network news transfer 04:47:37.020 --> 04:47:39.170 align:start position:0% Port 119 or the network news transfer protocol<04:47:37.378> which<04:47:38.100> is<04:47:38.280> not<04:47:38.400> only<04:47:38.580> used<04:47:38.820> with 04:47:39.170 --> 04:47:39.180 align:start position:0% protocol which is not only used with 04:47:39.180 --> 04:47:41.570 align:start position:0% protocol which is not only used with Usenet<04:47:39.900> a<04:47:40.440> sort<04:47:40.620> of<04:47:40.740> Message<04:47:41.100> Board<04:47:41.340> that's 04:47:41.570 --> 04:47:41.580 align:start position:0% Usenet a sort of Message Board that's 04:47:41.580 --> 04:47:43.610 align:start position:0% Usenet a sort of Message Board that's been<04:47:41.760> around<04:47:41.878> for<04:47:42.240> a<04:47:42.360> very<04:47:42.480> long<04:47:42.660> time<04:47:42.958> but 04:47:43.610 --> 04:47:43.620 align:start position:0% been around for a very long time but 04:47:43.620 --> 04:47:45.770 align:start position:0% been around for a very long time but also<04:47:43.920> RSS<04:47:44.400> feeds<04:47:44.878> which<04:47:45.060> you<04:47:45.240> might<04:47:45.480> be<04:47:45.600> more 04:47:45.770 --> 04:47:45.780 align:start position:0% also RSS feeds which you might be more 04:47:45.780 --> 04:47:48.948 align:start position:0% also RSS feeds which you might be more familiar<04:47:46.080> with<04:47:46.260> and<04:47:47.100> finally<04:47:47.400> Port<04:47:47.940> 80<04:47:48.240> is 04:47:48.948 --> 04:47:48.958 align:start position:0% familiar with and finally Port 80 is 04:47:48.958 --> 04:47:53.208 align:start position:0% familiar with and finally Port 80 is HTTP<04:47:49.920> or<04:47:50.700> hypertext<04:47:51.360> transfer<04:47:51.958> protocol<04:47:52.378> the 04:47:53.208 --> 04:47:53.218 align:start position:0% HTTP or hypertext transfer protocol the 04:47:53.218 --> 04:47:55.368 align:start position:0% HTTP or hypertext transfer protocol the other<04:47:53.280> thing<04:47:53.458> to<04:47:53.580> know<04:47:53.760> about<04:47:53.878> HTTP<04:47:54.718> is<04:47:55.080> it<04:47:55.260> has 04:47:55.368 --> 04:47:55.378 align:start position:0% other thing to know about HTTP is it has 04:47:55.378 --> 04:47:58.310 align:start position:0% other thing to know about HTTP is it has an<04:47:55.620> alternate<04:47:55.980> Port<04:47:56.218> of<04:47:56.638> 8080<04:47:57.240> so<04:47:57.900> you<04:47:58.138> might 04:47:58.310 --> 04:47:58.320 align:start position:0% an alternate Port of 8080 so you might 04:47:58.320 --> 04:48:01.010 align:start position:0% an alternate Port of 8080 so you might see<04:47:58.560> either<04:47:58.920> one<04:47:59.280> of<04:47:59.400> these<04:47:59.638> on<04:47:59.820> there 04:48:01.010 --> 04:48:01.020 align:start position:0% see either one of these on there 04:48:01.020 --> 04:48:03.110 align:start position:0% see either one of these on there all<04:48:01.620> right<04:48:01.798> now<04:48:02.160> I<04:48:02.280> know<04:48:02.400> that<04:48:02.580> was<04:48:02.700> a<04:48:02.878> lot<04:48:03.000> of 04:48:03.110 --> 04:48:03.120 align:start position:0% all right now I know that was a lot of 04:48:03.120 --> 04:48:05.150 align:start position:0% all right now I know that was a lot of information<04:48:03.298> I<04:48:03.840> just<04:48:03.958> threw<04:48:04.260> out<04:48:04.320> there<04:48:04.560> but 04:48:05.150 --> 04:48:05.160 align:start position:0% information I just threw out there but 04:48:05.160 --> 04:48:06.590 align:start position:0% information I just threw out there but we're<04:48:05.340> going<04:48:05.520> to<04:48:05.580> cover<04:48:05.760> these<04:48:06.060> all<04:48:06.240> in<04:48:06.360> a 04:48:06.590 --> 04:48:06.600 align:start position:0% we're going to cover these all in a 04:48:06.600 --> 04:48:08.090 align:start position:0% we're going to cover these all in a little<04:48:06.660> more<04:48:06.780> depth<04:48:07.138> as<04:48:07.320> we<04:48:07.500> go<04:48:07.620> through<04:48:07.860> here 04:48:08.090 --> 04:48:08.100 align:start position:0% little more depth as we go through here 04:48:08.100 --> 04:48:10.670 align:start position:0% little more depth as we go through here and<04:48:08.878> I<04:48:09.120> just<04:48:09.240> wanted<04:48:09.360> to<04:48:09.600> lay<04:48:09.780> them<04:48:09.958> out<04:48:10.138> in<04:48:10.500> a 04:48:10.670 --> 04:48:10.680 align:start position:0% and I just wanted to lay them out in a 04:48:10.680 --> 04:48:11.890 align:start position:0% and I just wanted to lay them out in a very<04:48:10.798> simple 04:48:11.890 --> 04:48:11.900 align:start position:0% very simple 04:48:11.900 --> 04:48:14.448 align:start position:0% very simple chart-based<04:48:12.900> way<04:48:13.080> so<04:48:13.620> that<04:48:13.740> you<04:48:13.920> could<04:48:14.100> commit 04:48:14.448 --> 04:48:14.458 align:start position:0% chart-based way so that you could commit 04:48:14.458 --> 04:48:15.770 align:start position:0% chart-based way so that you could commit them<04:48:14.638> to<04:48:14.820> Memory 04:48:15.770 --> 04:48:15.780 align:start position:0% them to Memory 04:48:15.780 --> 04:48:17.510 align:start position:0% them to Memory now<04:48:16.200> let's<04:48:16.378> talk<04:48:16.620> about<04:48:16.798> these<04:48:17.160> in<04:48:17.340> a<04:48:17.458> little 04:48:17.510 --> 04:48:17.520 align:start position:0% now let's talk about these in a little 04:48:17.520 --> 04:48:19.670 align:start position:0% now let's talk about these in a little more<04:48:17.700> depth<04:48:18.120> understand<04:48:18.660> how<04:48:19.200> they<04:48:19.320> function 04:48:19.670 --> 04:48:19.680 align:start position:0% more depth understand how they function 04:48:19.680 --> 04:48:23.390 align:start position:0% more depth understand how they function and<04:48:20.280> why<04:48:20.520> first<04:48:21.360> up<04:48:21.600> is<04:48:21.958> the<04:48:22.260> file<04:48:22.620> transfer 04:48:23.390 --> 04:48:23.400 align:start position:0% and why first up is the file transfer 04:48:23.400 --> 04:48:27.470 align:start position:0% and why first up is the file transfer protocol<04:48:23.878> or<04:48:24.540> FTP<04:48:25.340> this<04:48:26.340> protocol<04:48:26.638> enables 04:48:27.470 --> 04:48:27.480 align:start position:0% protocol or FTP this protocol enables 04:48:27.480 --> 04:48:30.590 align:start position:0% protocol or FTP this protocol enables the<04:48:27.840> transfer<04:48:28.378> of<04:48:28.560> files<04:48:29.100> between<04:48:29.700> a<04:48:30.180> user's 04:48:30.590 --> 04:48:30.600 align:start position:0% the transfer of files between a user's 04:48:30.600 --> 04:48:32.990 align:start position:0% the transfer of files between a user's computer<04:48:30.718> and<04:48:31.620> a<04:48:31.740> remote<04:48:31.920> host 04:48:32.990 --> 04:48:33.000 align:start position:0% computer and a remote host 04:48:33.000 --> 04:48:36.050 align:start position:0% computer and a remote host using<04:48:33.900> the<04:48:34.020> file<04:48:34.138> transfer<04:48:34.680> protocol<04:48:35.100> or<04:48:35.458> FTP 04:48:36.050 --> 04:48:36.060 align:start position:0% using the file transfer protocol or FTP 04:48:36.060 --> 04:48:41.208 align:start position:0% using the file transfer protocol or FTP you<04:48:36.958> can<04:48:37.138> view<04:48:37.920> change<04:48:38.820> search<04:48:39.718> for<04:48:40.080> upload<04:48:40.860> or 04:48:41.208 --> 04:48:41.218 align:start position:0% you can view change search for upload or 04:48:41.218 --> 04:48:43.550 align:start position:0% you can view change search for upload or download<04:48:41.520> files<04:48:42.240> now<04:48:42.840> where<04:48:43.080> while<04:48:43.320> this 04:48:43.550 --> 04:48:43.560 align:start position:0% download files now where while this 04:48:43.560 --> 04:48:45.948 align:start position:0% download files now where while this sounds<04:48:43.740> really<04:48:44.100> great<04:48:44.458> as<04:48:44.940> a<04:48:45.240> way<04:48:45.600> to<04:48:45.780> access 04:48:45.948 --> 04:48:45.958 align:start position:0% sounds really great as a way to access 04:48:45.958 --> 04:48:48.230 align:start position:0% sounds really great as a way to access files<04:48:46.500> remotely<04:48:46.860> it<04:48:47.700> has<04:48:47.878> a<04:48:48.120> few 04:48:48.230 --> 04:48:48.240 align:start position:0% files remotely it has a few 04:48:48.240 --> 04:48:49.970 align:start position:0% files remotely it has a few considerations<04:48:48.840> that<04:48:49.200> need<04:48:49.378> to<04:48:49.500> be<04:48:49.620> kept<04:48:49.860> in 04:48:49.970 --> 04:48:49.980 align:start position:0% considerations that need to be kept in 04:48:49.980 --> 04:48:53.868 align:start position:0% considerations that need to be kept in mind<04:48:50.160> the<04:48:50.940> first<04:48:51.120> is<04:48:51.360> that<04:48:51.840> FTP<04:48:52.440> by<04:48:52.740> itself<04:48:53.100> is 04:48:53.868 --> 04:48:53.878 align:start position:0% mind the first is that FTP by itself is 04:48:53.878 --> 04:48:59.448 align:start position:0% mind the first is that FTP by itself is very<04:48:54.180> unsecure<04:48:55.100> and<04:48:56.100> an<04:48:56.458> FTP<04:48:57.060> Daemon<04:48:58.378> which<04:48:59.100> is 04:48:59.448 --> 04:48:59.458 align:start position:0% very unsecure and an FTP Daemon which is 04:48:59.458 --> 04:49:03.890 align:start position:0% very unsecure and an FTP Daemon which is a<04:48:59.760> Unix<04:49:00.180> term<04:49:00.420> for<04:49:01.260> a<04:49:01.500> service 04:49:03.890 --> 04:49:03.900 align:start position:0% 04:49:03.900 --> 04:49:07.070 align:start position:0% has<04:49:04.500> to<04:49:04.740> be<04:49:04.860> running<04:49:05.160> on<04:49:06.060> the<04:49:06.420> remote<04:49:06.600> computer 04:49:07.070 --> 04:49:07.080 align:start position:0% has to be running on the remote computer 04:49:07.080 --> 04:49:10.070 align:start position:0% has to be running on the remote computer in<04:49:07.680> order<04:49:07.798> for<04:49:08.100> this<04:49:08.280> to<04:49:08.520> work<04:49:08.760> you<04:49:09.660> might<04:49:09.780> also 04:49:10.070 --> 04:49:10.080 align:start position:0% in order for this to work you might also 04:49:10.080 --> 04:49:13.430 align:start position:0% in order for this to work you might also have<04:49:10.260> to<04:49:10.440> have<04:49:10.680> an<04:49:11.160> FTP<04:49:11.700> utility<04:49:12.240> or<04:49:12.660> client<04:49:13.080> on 04:49:13.430 --> 04:49:13.440 align:start position:0% have to have an FTP utility or client on 04:49:13.440 --> 04:49:16.190 align:start position:0% have to have an FTP utility or client on the<04:49:13.560> client<04:49:13.860> computer<04:49:14.160> in<04:49:14.940> order<04:49:15.120> for<04:49:15.600> you<04:49:15.780> to 04:49:16.190 --> 04:49:16.200 align:start position:0% the client computer in order for you to 04:49:16.200 --> 04:49:18.470 align:start position:0% the client computer in order for you to have<04:49:16.620> this<04:49:16.860> protocol<04:49:17.160> operate<04:49:17.878> effectively 04:49:18.470 --> 04:49:18.480 align:start position:0% have this protocol operate effectively 04:49:18.480 --> 04:49:21.410 align:start position:0% have this protocol operate effectively and<04:49:19.020> for<04:49:19.138> you<04:49:19.260> to<04:49:19.440> be<04:49:19.500> able<04:49:19.680> to<04:49:19.798> use<04:49:19.980> it<04:49:20.638> now 04:49:21.410 --> 04:49:21.420 align:start position:0% and for you to be able to use it now 04:49:21.420 --> 04:49:25.128 align:start position:0% and for you to be able to use it now trivial<04:49:22.138> FTP<04:49:22.860> is<04:49:23.580> the<04:49:23.820> simple<04:49:24.060> version<04:49:24.360> of<04:49:24.660> FTP 04:49:25.128 --> 04:49:25.138 align:start position:0% trivial FTP is the simple version of FTP 04:49:25.138 --> 04:49:27.230 align:start position:0% trivial FTP is the simple version of FTP and<04:49:25.560> does<04:49:25.798> not<04:49:25.980> support<04:49:26.280> error<04:49:26.940> correction 04:49:27.230 --> 04:49:27.240 align:start position:0% and does not support error correction 04:49:27.240 --> 04:49:29.628 align:start position:0% and does not support error correction and<04:49:27.540> doesn't<04:49:27.718> guarantee<04:49:28.440> that<04:49:28.980> a<04:49:29.160> file<04:49:29.400> is 04:49:29.628 --> 04:49:29.638 align:start position:0% and doesn't guarantee that a file is 04:49:29.638 --> 04:49:31.550 align:start position:0% and doesn't guarantee that a file is actually<04:49:29.820> getting<04:49:30.060> where<04:49:30.360> it<04:49:30.480> needs<04:49:30.718> to<04:49:30.840> it's 04:49:31.550 --> 04:49:31.560 align:start position:0% actually getting where it needs to it's 04:49:31.560 --> 04:49:34.368 align:start position:0% actually getting where it needs to it's typically<04:49:31.980> not<04:49:32.400> really<04:49:32.638> used<04:49:33.060> in<04:49:33.660> many<04:49:33.900> actual 04:49:34.368 --> 04:49:34.378 align:start position:0% typically not really used in many actual 04:49:34.378 --> 04:49:37.010 align:start position:0% typically not really used in many actual file<04:49:34.620> transfer<04:49:35.218> settings<04:49:35.458> now<04:49:36.420> just<04:49:36.660> as<04:49:36.780> I 04:49:37.010 --> 04:49:37.020 align:start position:0% file transfer settings now just as I 04:49:37.020 --> 04:49:38.830 align:start position:0% file transfer settings now just as I just<04:49:37.138> mentioned<04:49:37.378> you<04:49:37.620> might<04:49:37.798> need<04:49:38.040> a<04:49:38.400> client 04:49:38.830 --> 04:49:38.840 align:start position:0% just mentioned you might need a client 04:49:38.840 --> 04:49:42.890 align:start position:0% just mentioned you might need a client FTP<04:49:39.840> uh<04:49:40.680> software<04:49:41.340> on<04:49:41.760> your<04:49:41.940> computer 04:49:42.890 --> 04:49:42.900 align:start position:0% FTP uh software on your computer 04:49:42.900 --> 04:49:44.930 align:start position:0% FTP uh software on your computer generally<04:49:43.500> speaking<04:49:43.920> there<04:49:44.160> is<04:49:44.340> a<04:49:44.580> command 04:49:44.930 --> 04:49:44.940 align:start position:0% generally speaking there is a command 04:49:44.940 --> 04:49:47.208 align:start position:0% generally speaking there is a command line<04:49:45.360> prompt<04:49:45.900> that<04:49:46.200> you<04:49:46.320> can<04:49:46.378> use 04:49:47.208 --> 04:49:47.218 align:start position:0% line prompt that you can use 04:49:47.218 --> 04:49:49.850 align:start position:0% line prompt that you can use it<04:49:47.580> goes<04:49:47.820> like<04:49:47.940> this<04:49:48.120> FTP 04:49:49.850 --> 04:49:49.860 align:start position:0% it goes like this FTP 04:49:49.860 --> 04:49:53.090 align:start position:0% it goes like this FTP space<04:49:50.520> the<04:49:51.420> fully<04:49:51.780> qualified<04:49:52.260> domain<04:49:52.920> name 04:49:53.090 --> 04:49:53.100 align:start position:0% space the fully qualified domain name 04:49:53.100 --> 04:49:56.810 align:start position:0% space the fully qualified domain name for<04:49:53.940> instance<04:49:54.180> google.com<04:49:55.340> FTP<04:49:56.340> which<04:49:56.700> I 04:49:56.810 --> 04:49:56.820 align:start position:0% for instance google.com FTP which I 04:49:56.820 --> 04:49:59.628 align:start position:0% for instance google.com FTP which I don't<04:49:56.940> think<04:49:57.060> is<04:49:57.180> the<04:49:57.420> actual<04:49:57.660> one<04:49:57.860> or<04:49:58.860> the<04:49:59.340> IP 04:49:59.628 --> 04:49:59.638 align:start position:0% don't think is the actual one or the IP 04:49:59.638 --> 04:50:02.390 align:start position:0% don't think is the actual one or the IP address<04:49:59.878> of<04:50:00.540> the<04:50:00.718> remote<04:50:00.900> host<04:50:01.320> you<04:50:02.100> only<04:50:02.160> need 04:50:02.390 --> 04:50:02.400 align:start position:0% address of the remote host you only need 04:50:02.400 --> 04:50:04.910 align:start position:0% address of the remote host you only need one<04:50:02.700> or<04:50:02.878> the<04:50:03.120> other<04:50:03.240> if<04:50:04.020> you<04:50:04.138> provide<04:50:04.440> the<04:50:04.620> IP 04:50:04.910 --> 04:50:04.920 align:start position:0% one or the other if you provide the IP 04:50:04.920 --> 04:50:06.350 align:start position:0% one or the other if you provide the IP address<04:50:05.100> you're<04:50:05.520> sort<04:50:05.760> of<04:50:05.820> using<04:50:06.060> the<04:50:06.240> direct 04:50:06.350 --> 04:50:06.360 align:start position:0% address you're sort of using the direct 04:50:06.360 --> 04:50:08.510 align:start position:0% address you're sort of using the direct route<04:50:06.660> if<04:50:07.260> you're<04:50:07.320> using<04:50:07.620> What's<04:50:07.860> called<04:50:08.100> the 04:50:08.510 --> 04:50:08.520 align:start position:0% route if you're using What's called the 04:50:08.520 --> 04:50:10.788 align:start position:0% route if you're using What's called the fully<04:50:09.060> qualified<04:50:09.480> domain<04:50:10.020> name<04:50:10.200> which<04:50:10.620> we'll 04:50:10.788 --> 04:50:10.798 align:start position:0% fully qualified domain name which we'll 04:50:10.798 --> 04:50:13.310 align:start position:0% fully qualified domain name which we'll talk<04:50:11.040> about<04:50:11.218> a<04:50:11.580> little<04:50:11.700> bit<04:50:11.820> later<04:50:12.120> then<04:50:13.020> you 04:50:13.310 --> 04:50:13.320 align:start position:0% talk about a little bit later then you 04:50:13.320 --> 04:50:15.708 align:start position:0% talk about a little bit later then you allow<04:50:13.620> something<04:50:13.920> called<04:50:14.280> DNS<04:50:14.878> or<04:50:15.120> the<04:50:15.298> domain 04:50:15.708 --> 04:50:15.718 align:start position:0% allow something called DNS or the domain 04:50:15.718 --> 04:50:17.448 align:start position:0% allow something called DNS or the domain name<04:50:16.200> service 04:50:17.448 --> 04:50:17.458 align:start position:0% name service 04:50:17.458 --> 04:50:22.430 align:start position:0% name service to<04:50:18.180> do<04:50:18.480> the<04:50:18.780> translation<04:50:19.320> into<04:50:20.480> uh<04:50:21.480> a<04:50:22.080> IP 04:50:22.430 --> 04:50:22.440 align:start position:0% to do the translation into uh a IP 04:50:22.440 --> 04:50:25.910 align:start position:0% to do the translation into uh a IP address<04:50:22.680> for<04:50:23.100> you<04:50:23.280> remember<04:50:24.180> again<04:50:24.660> that<04:50:25.260> FTP 04:50:25.910 --> 04:50:25.920 align:start position:0% address for you remember again that FTP 04:50:25.920 --> 04:50:28.310 align:start position:0% address for you remember again that FTP uses<04:50:26.700> ports<04:50:27.240> 20 04:50:28.310 --> 04:50:28.320 align:start position:0% uses ports 20 04:50:28.320 --> 04:50:33.530 align:start position:0% uses ports 20 and<04:50:29.040> 21<04:50:29.400> by<04:50:30.180> default 04:50:33.530 --> 04:50:33.540 align:start position:0% 04:50:33.540 --> 04:50:36.288 align:start position:0% next<04:50:34.138> is<04:50:34.320> the<04:50:34.680> simple<04:50:34.920> mail<04:50:35.520> transfer 04:50:36.288 --> 04:50:36.298 align:start position:0% next is the simple mail transfer 04:50:36.298 --> 04:50:39.830 align:start position:0% next is the simple mail transfer protocol<04:50:36.860> or<04:50:37.860> SMTP 04:50:39.830 --> 04:50:39.840 align:start position:0% protocol or SMTP 04:50:39.840 --> 04:50:42.350 align:start position:0% protocol or SMTP this<04:50:40.320> is<04:50:40.500> used<04:50:40.740> to<04:50:41.160> manage<04:50:41.458> the<04:50:41.760> formatting 04:50:42.350 --> 04:50:42.360 align:start position:0% this is used to manage the formatting 04:50:42.360 --> 04:50:45.610 align:start position:0% this is used to manage the formatting and<04:50:43.200> sending<04:50:44.040> of<04:50:44.520> email<04:50:44.760> messages 04:50:45.610 --> 04:50:45.620 align:start position:0% and sending of email messages 04:50:45.620 --> 04:50:47.690 align:start position:0% and sending of email messages specifically<04:50:46.620> we're<04:50:46.860> looking<04:50:47.100> here<04:50:47.400> at 04:50:47.690 --> 04:50:47.700 align:start position:0% specifically we're looking here at 04:50:47.700 --> 04:50:49.670 align:start position:0% specifically we're looking here at outgoing<04:50:48.600> email 04:50:49.670 --> 04:50:49.680 align:start position:0% outgoing email 04:50:49.680 --> 04:50:52.628 align:start position:0% outgoing email using<04:50:50.400> a<04:50:50.580> method<04:50:50.878> called<04:50:51.180> store<04:50:51.780> and<04:50:52.020> forward 04:50:52.628 --> 04:50:52.638 align:start position:0% using a method called store and forward 04:50:52.638 --> 04:50:56.628 align:start position:0% using a method called store and forward SMTP<04:50:53.638> can<04:50:54.060> hold<04:50:54.480> on<04:50:54.900> to<04:50:55.200> a<04:50:55.440> message<04:50:55.560> until<04:50:56.218> the 04:50:56.628 --> 04:50:56.638 align:start position:0% SMTP can hold on to a message until the 04:50:56.638 --> 04:50:59.628 align:start position:0% SMTP can hold on to a message until the recipient<04:50:57.120> comes<04:50:57.900> online<04:50:58.080> this<04:50:59.040> is<04:50:59.100> why<04:50:59.400> it's 04:50:59.628 --> 04:50:59.638 align:start position:0% recipient comes online this is why it's 04:50:59.638 --> 04:51:02.810 align:start position:0% recipient comes online this is why it's used<04:51:00.000> over<04:51:00.480> unreliable<04:51:01.440> wide<04:51:02.340> area<04:51:02.520> network 04:51:02.810 --> 04:51:02.820 align:start position:0% used over unreliable wide area network 04:51:02.820 --> 04:51:06.590 align:start position:0% used over unreliable wide area network links<04:51:03.420> once<04:51:04.320> the<04:51:04.440> device<04:51:04.680> comes<04:51:05.458> online<04:51:05.638> it 04:51:06.590 --> 04:51:06.600 align:start position:0% links once the device comes online it 04:51:06.600 --> 04:51:09.110 align:start position:0% links once the device comes online it hands<04:51:06.900> the<04:51:07.020> message<04:51:07.200> off<04:51:07.740> to<04:51:08.040> the<04:51:08.218> server<04:51:08.520> the 04:51:09.110 --> 04:51:09.120 align:start position:0% hands the message off to the server the 04:51:09.120 --> 04:51:11.590 align:start position:0% hands the message off to the server the SMTP<04:51:09.780> message<04:51:10.138> has<04:51:10.920> several<04:51:11.340> things 04:51:11.590 --> 04:51:11.600 align:start position:0% SMTP message has several things 04:51:11.600 --> 04:51:14.208 align:start position:0% SMTP message has several things including<04:51:12.600> a<04:51:12.958> header 04:51:14.208 --> 04:51:14.218 align:start position:0% including a header 04:51:14.218 --> 04:51:17.510 align:start position:0% including a header that<04:51:14.820> contains<04:51:15.360> Source<04:51:16.200> information<04:51:16.378> as<04:51:17.340> to 04:51:17.510 --> 04:51:17.520 align:start position:0% that contains Source information as to 04:51:17.520 --> 04:51:21.490 align:start position:0% that contains Source information as to where<04:51:17.820> it's<04:51:18.000> coming<04:51:18.240> from<04:51:18.798> and<04:51:19.798> it<04:51:20.280> also<04:51:20.520> has 04:51:21.490 --> 04:51:21.500 align:start position:0% where it's coming from and it also has 04:51:21.500 --> 04:51:24.350 align:start position:0% where it's coming from and it also has destination<04:51:22.500> information<04:51:22.860> as<04:51:23.820> to<04:51:24.000> where<04:51:24.240> it's 04:51:24.350 --> 04:51:24.360 align:start position:0% destination information as to where it's 04:51:24.360 --> 04:51:26.208 align:start position:0% destination information as to where it's going 04:51:26.208 --> 04:51:26.218 align:start position:0% going 04:51:26.218 --> 04:51:28.190 align:start position:0% going of<04:51:26.820> course<04:51:26.940> there's<04:51:27.360> also<04:51:27.718> content 04:51:28.190 --> 04:51:28.200 align:start position:0% of course there's also content 04:51:28.200 --> 04:51:30.708 align:start position:0% of course there's also content information<04:51:28.500> which<04:51:29.100> is<04:51:29.280> inside<04:51:29.700> of<04:51:30.480> the 04:51:30.708 --> 04:51:30.718 align:start position:0% information which is inside of the 04:51:30.718 --> 04:51:31.788 align:start position:0% information which is inside of the packet 04:51:31.788 --> 04:51:31.798 align:start position:0% packet 04:51:31.798 --> 04:51:35.830 align:start position:0% packet the<04:51:32.340> default<04:51:32.638> port<04:51:32.878> for<04:51:33.120> SMTP<04:51:33.840> is<04:51:34.740> Port<04:51:35.218> 25 04:51:35.830 --> 04:51:35.840 align:start position:0% the default port for SMTP is Port 25 04:51:35.840 --> 04:51:38.570 align:start position:0% the default port for SMTP is Port 25 although<04:51:36.840> sometimes<04:51:37.378> you<04:51:37.740> might<04:51:37.860> see<04:51:38.160> it<04:51:38.340> use 04:51:38.570 --> 04:51:38.580 align:start position:0% although sometimes you might see it use 04:51:38.580 --> 04:51:42.410 align:start position:0% although sometimes you might see it use port<04:51:39.020> 587<04:51:40.020> which<04:51:40.680> is<04:51:40.860> uh<04:51:41.218> by<04:51:41.458> relay<04:51:41.820> I<04:51:42.298> wouldn't 04:51:42.410 --> 04:51:42.420 align:start position:0% port 587 which is uh by relay I wouldn't 04:51:42.420 --> 04:51:44.330 align:start position:0% port 587 which is uh by relay I wouldn't worry<04:51:42.660> too<04:51:42.900> much<04:51:43.080> about<04:51:43.320> that<04:51:43.680> one<04:51:43.860> for<04:51:44.160> the 04:51:44.330 --> 04:51:44.340 align:start position:0% worry too much about that one for the 04:51:44.340 --> 04:51:48.050 align:start position:0% worry too much about that one for the exam<04:51:44.700> but<04:51:45.240> just<04:51:45.480> keep<04:51:45.718> in<04:51:45.900> mind<04:51:46.020> Port<04:51:46.560> 25.<04:51:47.400> now 04:51:48.050 --> 04:51:48.060 align:start position:0% exam but just keep in mind Port 25. now 04:51:48.060 --> 04:51:53.330 align:start position:0% exam but just keep in mind Port 25. now like<04:51:48.860> SMTP<04:51:50.180> POP3<04:51:51.180> is<04:51:51.840> a<04:51:52.020> protocol<04:51:52.320> that's<04:51:52.980> used 04:51:53.330 --> 04:51:53.340 align:start position:0% like SMTP POP3 is a protocol that's used 04:51:53.340 --> 04:51:56.570 align:start position:0% like SMTP POP3 is a protocol that's used in<04:51:53.760> handling<04:51:54.180> email<04:51:54.540> messages<04:51:54.980> and<04:51:55.980> POP3 04:51:56.570 --> 04:51:56.580 align:start position:0% in handling email messages and POP3 04:51:56.580 --> 04:51:58.628 align:start position:0% in handling email messages and POP3 stands<04:51:57.000> for<04:51:57.120> the<04:51:57.360> Post<04:51:57.718> Office<04:51:57.958> protocol 04:51:58.628 --> 04:51:58.638 align:start position:0% stands for the Post Office protocol 04:51:58.638 --> 04:52:01.670 align:start position:0% stands for the Post Office protocol version<04:51:59.638> 3<04:52:00.360> which<04:52:00.840> is<04:52:00.958> the<04:52:01.260> commonly<04:52:01.500> used 04:52:01.670 --> 04:52:01.680 align:start position:0% version 3 which is the commonly used 04:52:01.680 --> 04:52:03.050 align:start position:0% version 3 which is the commonly used version<04:52:02.040> now 04:52:03.050 --> 04:52:03.060 align:start position:0% version now 04:52:03.060 --> 04:52:05.570 align:start position:0% version now specifically<04:52:03.900> POP3<04:52:04.680> is<04:52:04.860> used<04:52:05.040> for<04:52:05.280> the 04:52:05.570 --> 04:52:05.580 align:start position:0% specifically POP3 is used for the 04:52:05.580 --> 04:52:09.288 align:start position:0% specifically POP3 is used for the receipt<04:52:06.000> of<04:52:06.298> email<04:52:06.540> or<04:52:07.200> incoming<04:52:07.798> email<04:52:08.298> and 04:52:09.288 --> 04:52:09.298 align:start position:0% receipt of email or incoming email and 04:52:09.298 --> 04:52:11.628 align:start position:0% receipt of email or incoming email and it<04:52:09.840> does<04:52:10.020> this<04:52:10.260> by<04:52:10.798> retrieving<04:52:11.340> email 04:52:11.628 --> 04:52:11.638 align:start position:0% it does this by retrieving email 04:52:11.638 --> 04:52:14.390 align:start position:0% it does this by retrieving email messages<04:52:12.000> from<04:52:12.718> a<04:52:12.900> mail<04:52:13.080> server<04:52:13.920> it's 04:52:14.390 --> 04:52:14.400 align:start position:0% messages from a mail server it's 04:52:14.400 --> 04:52:16.970 align:start position:0% messages from a mail server it's designed<04:52:14.760> to<04:52:15.060> pull<04:52:15.240> the<04:52:15.480> messages<04:52:15.660> down<04:52:16.260> and 04:52:16.970 --> 04:52:16.980 align:start position:0% designed to pull the messages down and 04:52:16.980 --> 04:52:19.070 align:start position:0% designed to pull the messages down and then<04:52:17.160> once<04:52:17.700> it<04:52:17.760> does<04:52:17.940> that<04:52:18.120> the<04:52:18.718> server 04:52:19.070 --> 04:52:19.080 align:start position:0% then once it does that the server 04:52:19.080 --> 04:52:23.270 align:start position:0% then once it does that the server deletes<04:52:19.920> the<04:52:20.218> message<04:52:20.580> on<04:52:21.540> the<04:52:22.500> server<04:52:22.860> Source 04:52:23.270 --> 04:52:23.280 align:start position:0% deletes the message on the server Source 04:52:23.280 --> 04:52:25.970 align:start position:0% deletes the message on the server Source by<04:52:23.820> default<04:52:24.240> although<04:52:24.840> you<04:52:25.200> can<04:52:25.320> change<04:52:25.680> that 04:52:25.970 --> 04:52:25.980 align:start position:0% by default although you can change that 04:52:25.980 --> 04:52:28.850 align:start position:0% by default although you can change that if<04:52:26.280> an<04:52:26.400> administrator<04:52:26.940> wants<04:52:27.480> to<04:52:27.600> this<04:52:28.560> makes 04:52:28.850 --> 04:52:28.860 align:start position:0% if an administrator wants to this makes 04:52:28.860 --> 04:52:33.050 align:start position:0% if an administrator wants to this makes POP3<04:52:29.580> not<04:52:30.360> as<04:52:30.540> desirable<04:52:31.138> and<04:52:32.040> weaker<04:52:32.580> than 04:52:33.050 --> 04:52:33.060 align:start position:0% POP3 not as desirable and weaker than 04:52:33.060 --> 04:52:34.610 align:start position:0% POP3 not as desirable and weaker than most<04:52:33.298> some<04:52:33.600> other<04:52:33.780> mail<04:52:34.020> protocols 04:52:34.610 --> 04:52:34.620 align:start position:0% most some other mail protocols 04:52:34.620 --> 04:52:36.170 align:start position:0% most some other mail protocols specifically<04:52:35.100> IMAP<04:52:35.580> which<04:52:35.760> we're<04:52:35.940> going<04:52:36.060> to 04:52:36.170 --> 04:52:36.180 align:start position:0% specifically IMAP which we're going to 04:52:36.180 --> 04:52:40.190 align:start position:0% specifically IMAP which we're going to see<04:52:36.298> because<04:52:37.040> it<04:52:38.040> puts<04:52:38.520> all<04:52:38.760> of<04:52:38.940> the<04:52:39.298> brunt<04:52:39.900> of 04:52:40.190 --> 04:52:40.200 align:start position:0% see because it puts all of the brunt of 04:52:40.200 --> 04:52:42.770 align:start position:0% see because it puts all of the brunt of the<04:52:40.378> responsibility<04:52:41.040> onto<04:52:41.940> the<04:52:42.120> client<04:52:42.360> for 04:52:42.770 --> 04:52:42.780 align:start position:0% the responsibility onto the client for 04:52:42.780 --> 04:52:45.050 align:start position:0% the responsibility onto the client for storing<04:52:43.138> and<04:52:43.320> managing<04:52:43.740> emails<04:52:44.218> and<04:52:44.638> deletes 04:52:45.050 --> 04:52:45.060 align:start position:0% storing and managing emails and deletes 04:52:45.060 --> 04:52:47.448 align:start position:0% storing and managing emails and deletes all<04:52:45.240> the<04:52:45.420> emails<04:52:45.900> at<04:52:46.200> the<04:52:46.320> source<04:52:46.740> so<04:52:47.280> if 04:52:47.448 --> 04:52:47.458 align:start position:0% all the emails at the source so if 04:52:47.458 --> 04:52:48.948 align:start position:0% all the emails at the source so if something<04:52:47.638> happens<04:52:47.940> to<04:52:48.298> your<04:52:48.480> computer<04:52:48.660> and 04:52:48.948 --> 04:52:48.958 align:start position:0% something happens to your computer and 04:52:48.958 --> 04:52:50.868 align:start position:0% something happens to your computer and you<04:52:49.080> don't<04:52:49.200> have<04:52:49.320> a<04:52:49.500> backup<04:52:49.740> you're<04:52:50.458> in<04:52:50.760> big 04:52:50.868 --> 04:52:50.878 align:start position:0% you don't have a backup you're in big 04:52:50.878 --> 04:52:51.708 align:start position:0% you don't have a backup you're in big trouble 04:52:51.708 --> 04:52:51.718 align:start position:0% trouble 04:52:51.718 --> 04:52:53.810 align:start position:0% trouble the<04:52:52.200> default<04:52:52.560> port<04:52:52.740> for<04:52:53.040> POP3<04:52:53.458> as<04:52:53.700> we 04:52:53.810 --> 04:52:53.820 align:start position:0% the default port for POP3 as we 04:52:53.820 --> 04:52:57.230 align:start position:0% the default port for POP3 as we mentioned<04:52:54.120> is<04:52:54.480> Port<04:52:54.980> 110.<04:52:55.980> so<04:52:56.340> remember<04:52:56.580> Port 04:52:57.230 --> 04:52:57.240 align:start position:0% mentioned is Port 110. so remember Port 04:52:57.240 --> 04:53:02.750 align:start position:0% mentioned is Port 110. so remember Port 110<04:52:57.900> is<04:52:58.020> POP3<04:52:58.500> and<04:52:59.100> Port<04:52:59.340> 25<04:52:59.760> is<04:53:00.420> SMTP<04:53:01.200> now<04:53:02.040> IMAP 04:53:02.750 --> 04:53:02.760 align:start position:0% 110 is POP3 and Port 25 is SMTP now IMAP 04:53:02.760 --> 04:53:06.050 align:start position:0% 110 is POP3 and Port 25 is SMTP now IMAP 4<04:53:03.080> usually<04:53:04.080> just<04:53:04.440> called<04:53:04.740> IMAP<04:53:05.400> is<04:53:05.820> the 04:53:06.050 --> 04:53:06.060 align:start position:0% 4 usually just called IMAP is the 04:53:06.060 --> 04:53:08.810 align:start position:0% 4 usually just called IMAP is the internet<04:53:06.240> message<04:53:06.840> access<04:53:07.378> protocol<04:53:08.100> and 04:53:08.810 --> 04:53:08.820 align:start position:0% internet message access protocol and 04:53:08.820 --> 04:53:10.730 align:start position:0% internet message access protocol and it's<04:53:08.940> similar<04:53:09.298> to<04:53:09.420> POP3<04:53:09.900> in<04:53:10.138> that<04:53:10.260> it's<04:53:10.440> also 04:53:10.730 --> 04:53:10.740 align:start position:0% it's similar to POP3 in that it's also 04:53:10.740 --> 04:53:13.368 align:start position:0% it's similar to POP3 in that it's also utilized<04:53:11.400> for<04:53:11.700> incoming<04:53:12.298> mail<04:53:12.718> or<04:53:13.020> mail 04:53:13.368 --> 04:53:13.378 align:start position:0% utilized for incoming mail or mail 04:53:13.378 --> 04:53:16.788 align:start position:0% utilized for incoming mail or mail retrieval<04:53:14.040> but<04:53:14.638> in<04:53:14.878> nearly<04:53:15.180> every<04:53:15.540> way<04:53:15.840> IMAP 04:53:16.788 --> 04:53:16.798 align:start position:0% retrieval but in nearly every way IMAP 04:53:16.798 --> 04:53:20.090 align:start position:0% retrieval but in nearly every way IMAP surpasses<04:53:17.580> POP3<04:53:18.180> it's<04:53:19.020> a<04:53:19.260> much<04:53:19.378> more<04:53:19.620> powerful 04:53:20.090 --> 04:53:20.100 align:start position:0% surpasses POP3 it's a much more powerful 04:53:20.100 --> 04:53:23.030 align:start position:0% surpasses POP3 it's a much more powerful protocol<04:53:20.638> because<04:53:21.240> it<04:53:21.540> offers<04:53:21.900> more<04:53:22.500> benefits 04:53:23.030 --> 04:53:23.040 align:start position:0% protocol because it offers more benefits 04:53:23.040 --> 04:53:26.390 align:start position:0% protocol because it offers more benefits like<04:53:23.580> easier<04:53:24.120> mailbox<04:53:24.600> management<04:53:25.400> more 04:53:26.390 --> 04:53:26.400 align:start position:0% like easier mailbox management more 04:53:26.400 --> 04:53:28.788 align:start position:0% like easier mailbox management more granular<04:53:26.940> search<04:53:27.298> capabilities<04:53:28.020> and<04:53:28.440> so<04:53:28.620> on 04:53:28.788 --> 04:53:28.798 align:start position:0% granular search capabilities and so on 04:53:28.798 --> 04:53:31.670 align:start position:0% granular search capabilities and so on with<04:53:29.700> IMAP<04:53:30.240> users<04:53:30.900> can<04:53:31.200> search<04:53:31.378> through 04:53:31.670 --> 04:53:31.680 align:start position:0% with IMAP users can search through 04:53:31.680 --> 04:53:34.070 align:start position:0% with IMAP users can search through messages<04:53:31.920> by<04:53:32.458> keywords<04:53:33.120> and<04:53:33.540> choose<04:53:33.840> which 04:53:34.070 --> 04:53:34.080 align:start position:0% messages by keywords and choose which 04:53:34.080 --> 04:53:36.110 align:start position:0% messages by keywords and choose which messages<04:53:34.320> they<04:53:34.740> want<04:53:34.860> to<04:53:35.040> download<04:53:35.218> they<04:53:35.940> can 04:53:36.110 --> 04:53:36.120 align:start position:0% messages they want to download they can 04:53:36.120 --> 04:53:38.690 align:start position:0% messages they want to download they can also<04:53:36.360> leave<04:53:36.600> IMAP<04:53:37.200> messages<04:53:37.440> on<04:53:38.218> the<04:53:38.340> server 04:53:38.690 --> 04:53:38.700 align:start position:0% also leave IMAP messages on the server 04:53:38.700 --> 04:53:40.970 align:start position:0% also leave IMAP messages on the server and<04:53:39.240> still<04:53:39.420> work<04:53:39.660> with<04:53:39.840> them<04:53:40.080> as<04:53:40.740> though 04:53:40.970 --> 04:53:40.980 align:start position:0% and still work with them as though 04:53:40.980 --> 04:53:42.948 align:start position:0% and still work with them as though they're<04:53:41.400> on<04:53:41.638> the<04:53:41.878> local<04:53:42.000> computer 04:53:42.948 --> 04:53:42.958 align:start position:0% they're on the local computer 04:53:42.958 --> 04:53:47.510 align:start position:0% they're on the local computer so<04:53:43.940> it<04:53:44.940> seems<04:53:45.360> that<04:53:46.138> the<04:53:46.620> two<04:53:46.740> are<04:53:47.160> synced 04:53:47.510 --> 04:53:47.520 align:start position:0% so it seems that the two are synced 04:53:47.520 --> 04:53:49.670 align:start position:0% so it seems that the two are synced together<04:53:47.760> perfectly<04:53:48.480> the<04:53:48.900> server<04:53:49.200> and<04:53:49.500> the 04:53:49.670 --> 04:53:49.680 align:start position:0% together perfectly the server and the 04:53:49.680 --> 04:53:50.628 align:start position:0% together perfectly the server and the client 04:53:50.628 --> 04:53:50.638 align:start position:0% client 04:53:50.638 --> 04:53:52.788 align:start position:0% client also<04:53:51.240> an<04:53:51.420> email<04:53:51.540> message<04:53:51.900> with<04:53:52.260> say<04:53:52.560> a 04:53:52.788 --> 04:53:52.798 align:start position:0% also an email message with say a 04:53:52.798 --> 04:53:55.010 align:start position:0% also an email message with say a multimedia<04:53:53.520> file<04:53:53.878> can<04:53:54.298> be<04:53:54.540> partially 04:53:55.010 --> 04:53:55.020 align:start position:0% multimedia file can be partially 04:53:55.020 --> 04:53:58.070 align:start position:0% multimedia file can be partially downloaded<04:53:55.740> to<04:53:56.340> save<04:53:56.520> bandwidth 04:53:58.070 --> 04:53:58.080 align:start position:0% downloaded to save bandwidth 04:53:58.080 --> 04:54:00.590 align:start position:0% downloaded to save bandwidth now<04:53:58.620> the<04:53:59.340> main<04:53:59.458> benefit<04:53:59.760> here<04:54:00.120> is<04:54:00.298> we're<04:54:00.480> going 04:54:00.590 --> 04:54:00.600 align:start position:0% now the main benefit here is we're going 04:54:00.600 --> 04:54:02.150 align:start position:0% now the main benefit here is we're going to<04:54:00.660> use<04:54:00.840> this<04:54:01.020> instead<04:54:01.378> of<04:54:01.500> first<04:54:01.680> say<04:54:01.980> a 04:54:02.150 --> 04:54:02.160 align:start position:0% to use this instead of first say a 04:54:02.160 --> 04:54:04.070 align:start position:0% to use this instead of first say a computer<04:54:02.280> let's<04:54:02.760> say<04:54:02.940> I<04:54:03.180> have<04:54:03.360> a<04:54:03.660> smartphone 04:54:04.070 --> 04:54:04.080 align:start position:0% computer let's say I have a smartphone 04:54:04.080 --> 04:54:07.250 align:start position:0% computer let's say I have a smartphone and<04:54:04.980> a<04:54:05.160> computer<04:54:05.540> now<04:54:06.540> it's<04:54:06.840> going<04:54:07.020> to<04:54:07.138> make 04:54:07.250 --> 04:54:07.260 align:start position:0% and a computer now it's going to make 04:54:07.260 --> 04:54:10.310 align:start position:0% and a computer now it's going to make sure<04:54:07.560> because<04:54:08.280> the<04:54:09.120> source<04:54:09.480> is<04:54:09.660> all<04:54:09.900> stored<04:54:10.200> at 04:54:10.310 --> 04:54:10.320 align:start position:0% sure because the source is all stored at 04:54:10.320 --> 04:54:11.690 align:start position:0% sure because the source is all stored at the<04:54:10.500> server 04:54:11.690 --> 04:54:11.700 align:start position:0% the server 04:54:11.700 --> 04:54:14.628 align:start position:0% the server that<04:54:12.420> if<04:54:12.718> I<04:54:12.900> delete<04:54:13.020> something<04:54:13.440> say<04:54:14.160> on<04:54:14.458> my 04:54:14.628 --> 04:54:14.638 align:start position:0% that if I delete something say on my 04:54:14.638 --> 04:54:17.990 align:start position:0% that if I delete something say on my computer<04:54:14.958> that<04:54:15.958> syncs<04:54:16.500> up<04:54:16.620> to<04:54:16.798> the<04:54:16.920> server<04:54:17.218> and 04:54:17.990 --> 04:54:18.000 align:start position:0% computer that syncs up to the server and 04:54:18.000 --> 04:54:19.310 align:start position:0% computer that syncs up to the server and then<04:54:18.120> the<04:54:18.298> server<04:54:18.540> will<04:54:18.718> have<04:54:18.840> that<04:54:18.958> sync<04:54:19.200> with 04:54:19.310 --> 04:54:19.320 align:start position:0% then the server will have that sync with 04:54:19.320 --> 04:54:21.708 align:start position:0% then the server will have that sync with this<04:54:19.440> my<04:54:19.620> smartphone<04:54:20.160> so<04:54:20.878> all<04:54:21.180> of<04:54:21.298> these<04:54:21.480> are 04:54:21.708 --> 04:54:21.718 align:start position:0% this my smartphone so all of these are 04:54:21.718 --> 04:54:24.230 align:start position:0% this my smartphone so all of these are in<04:54:21.900> perfect<04:54:22.080> synchronization<04:54:22.920> this<04:54:23.878> is<04:54:24.000> why 04:54:24.230 --> 04:54:24.240 align:start position:0% in perfect synchronization this is why 04:54:24.240 --> 04:54:26.930 align:start position:0% in perfect synchronization this is why it's<04:54:24.480> much<04:54:24.840> stronger<04:54:25.320> than<04:54:25.740> POP3<04:54:26.340> which 04:54:26.930 --> 04:54:26.940 align:start position:0% it's much stronger than POP3 which 04:54:26.940 --> 04:54:29.270 align:start position:0% it's much stronger than POP3 which simply<04:54:27.298> downloads<04:54:27.958> the<04:54:28.138> email<04:54:28.320> onto<04:54:29.100> your 04:54:29.270 --> 04:54:29.280 align:start position:0% simply downloads the email onto your 04:54:29.280 --> 04:54:30.650 align:start position:0% simply downloads the email onto your client<04:54:29.580> device 04:54:30.650 --> 04:54:30.660 align:start position:0% client device 04:54:30.660 --> 04:54:35.390 align:start position:0% client device by<04:54:31.378> default<04:54:31.740> IMAP<04:54:32.400> uses<04:54:32.820> Port<04:54:33.440> 143<04:54:34.440> which<04:54:35.280> is 04:54:35.390 --> 04:54:35.400 align:start position:0% by default IMAP uses Port 143 which is 04:54:35.400 --> 04:54:36.890 align:start position:0% by default IMAP uses Port 143 which is different<04:54:35.580> from<04:54:35.878> IMAP 04:54:36.890 --> 04:54:36.900 align:start position:0% different from IMAP 04:54:36.900 --> 04:54:41.030 align:start position:0% different from IMAP POP3<04:54:37.620> rather<04:54:38.160> which<04:54:38.638> uses<04:54:39.060> 110. 04:54:41.030 --> 04:54:41.040 align:start position:0% POP3 rather which uses 110. 04:54:41.040 --> 04:54:44.990 align:start position:0% POP3 rather which uses 110. now<04:54:41.940> ntp<04:54:42.540> or<04:54:42.718> the<04:54:42.900> network<04:54:43.020> time<04:54:43.740> protocol<04:54:44.340> is 04:54:44.990 --> 04:54:45.000 align:start position:0% now ntp or the network time protocol is 04:54:45.000 --> 04:54:47.030 align:start position:0% now ntp or the network time protocol is an<04:54:45.180> Internet<04:54:45.298> Protocol<04:54:45.780> that<04:54:46.200> synchronizes 04:54:47.030 --> 04:54:47.040 align:start position:0% an Internet Protocol that synchronizes 04:54:47.040 --> 04:54:50.570 align:start position:0% an Internet Protocol that synchronizes system<04:54:47.340> Clocks<04:54:48.000> by<04:54:48.600> exchanging<04:54:49.378> time<04:54:49.920> signals 04:54:50.570 --> 04:54:50.580 align:start position:0% system Clocks by exchanging time signals 04:54:50.580 --> 04:54:52.850 align:start position:0% system Clocks by exchanging time signals between<04:54:51.000> a<04:54:51.360> client<04:54:51.660> and<04:54:52.138> a<04:54:52.320> Master<04:54:52.500> Clock 04:54:52.850 --> 04:54:52.860 align:start position:0% between a client and a Master Clock 04:54:52.860 --> 04:54:55.490 align:start position:0% between a client and a Master Clock server<04:54:53.400> the<04:54:54.180> computers<04:54:54.600> are<04:54:55.020> constantly 04:54:55.490 --> 04:54:55.500 align:start position:0% server the computers are constantly 04:54:55.500 --> 04:54:57.530 align:start position:0% server the computers are constantly running<04:54:55.740> this<04:54:55.980> in<04:54:56.218> the<04:54:56.340> background<04:54:56.638> and<04:54:57.298> this 04:54:57.530 --> 04:54:57.540 align:start position:0% running this in the background and this 04:54:57.540 --> 04:55:00.050 align:start position:0% running this in the background and this protocol<04:54:57.958> will<04:54:58.440> send<04:54:58.740> requests<04:54:59.400> to<04:54:59.878> the 04:55:00.050 --> 04:55:00.060 align:start position:0% protocol will send requests to the 04:55:00.060 --> 04:55:03.110 align:start position:0% protocol will send requests to the server<04:55:00.360> to<04:55:00.900> obtain<04:55:01.260> accurate<04:55:02.040> time<04:55:02.520> updates 04:55:03.110 --> 04:55:03.120 align:start position:0% server to obtain accurate time updates 04:55:03.120 --> 04:55:06.288 align:start position:0% server to obtain accurate time updates up<04:55:03.540> to<04:55:03.718> the<04:55:03.840> millisecond<04:55:04.500> this<04:55:05.458> time<04:55:05.700> is 04:55:06.288 --> 04:55:06.298 align:start position:0% up to the millisecond this time is 04:55:06.298 --> 04:55:08.170 align:start position:0% up to the millisecond this time is checked<04:55:06.600> against<04:55:06.718> the<04:55:07.200> U.S<04:55:07.620> Naval 04:55:08.170 --> 04:55:08.180 align:start position:0% checked against the U.S Naval 04:55:08.180 --> 04:55:11.448 align:start position:0% checked against the U.S Naval Observatory<04:55:09.180> Master<04:55:09.840> Clock<04:55:10.260> or<04:55:10.680> atomic<04:55:11.218> clock 04:55:11.448 --> 04:55:11.458 align:start position:0% Observatory Master Clock or atomic clock 04:55:11.458 --> 04:55:14.330 align:start position:0% Observatory Master Clock or atomic clock so<04:55:12.420> the<04:55:12.780> timestamps<04:55:13.500> on<04:55:13.740> the<04:55:13.920> received 04:55:14.330 --> 04:55:14.340 align:start position:0% so the timestamps on the received 04:55:14.340 --> 04:55:17.810 align:start position:0% so the timestamps on the received updates<04:55:14.820> are<04:55:15.480> verified<04:55:15.900> with<04:55:16.620> this<04:55:17.218> Master 04:55:17.810 --> 04:55:17.820 align:start position:0% updates are verified with this Master 04:55:17.820 --> 04:55:20.570 align:start position:0% updates are verified with this Master Clock<04:55:18.120> server<04:55:18.718> which<04:55:19.378> is<04:55:19.680> again<04:55:19.860> that<04:55:20.218> US 04:55:20.570 --> 04:55:20.580 align:start position:0% Clock server which is again that US 04:55:20.580 --> 04:55:23.448 align:start position:0% Clock server which is again that US Naval<04:55:21.240> server 04:55:23.448 --> 04:55:23.458 align:start position:0% Naval server 04:55:23.458 --> 04:55:26.150 align:start position:0% Naval server and<04:55:24.298> the<04:55:24.540> computers<04:55:24.900> then<04:55:25.200> update<04:55:25.620> their<04:55:25.980> time 04:55:26.150 --> 04:55:26.160 align:start position:0% and the computers then update their time 04:55:26.160 --> 04:55:27.590 align:start position:0% and the computers then update their time accordingly 04:55:27.590 --> 04:55:27.600 align:start position:0% accordingly 04:55:27.600 --> 04:55:30.948 align:start position:0% accordingly the<04:55:27.840> port<04:55:28.080> this<04:55:28.320> uses<04:55:28.680> is<04:55:29.100> Port<04:55:29.458> 123<04:55:30.298> which<04:55:30.840> is 04:55:30.948 --> 04:55:30.958 align:start position:0% the port this uses is Port 123 which is 04:55:30.958 --> 04:55:34.250 align:start position:0% the port this uses is Port 123 which is as<04:55:31.200> easy<04:55:31.378> to<04:55:31.680> remember<04:55:31.860> as<04:55:32.520> time 04:55:34.250 --> 04:55:34.260 align:start position:0% as easy to remember as time 04:55:34.260 --> 04:55:38.810 align:start position:0% as easy to remember as time keeps<04:55:34.860> moving<04:55:35.160> up<04:55:35.400> one<04:55:36.378> two<04:55:37.378> three 04:55:38.810 --> 04:55:38.820 align:start position:0% keeps moving up one two three 04:55:38.820 --> 04:55:41.090 align:start position:0% keeps moving up one two three now<04:55:39.180> if<04:55:39.298> we<04:55:39.480> add<04:55:39.660> an<04:55:39.840> additional<04:55:40.320> n<04:55:40.620> to<04:55:40.860> the 04:55:41.090 --> 04:55:41.100 align:start position:0% now if we add an additional n to the 04:55:41.100 --> 04:55:43.010 align:start position:0% now if we add an additional n to the previous<04:55:41.218> one<04:55:41.638> we<04:55:42.120> get<04:55:42.240> What's<04:55:42.420> called<04:55:42.660> the 04:55:43.010 --> 04:55:43.020 align:start position:0% previous one we get What's called the 04:55:43.020 --> 04:55:46.128 align:start position:0% previous one we get What's called the network<04:55:43.200> news<04:55:43.980> transfer<04:55:44.700> protocol 04:55:46.128 --> 04:55:46.138 align:start position:0% network news transfer protocol 04:55:46.138 --> 04:55:47.868 align:start position:0% network news transfer protocol this<04:55:46.620> is<04:55:46.798> very<04:55:47.100> different<04:55:47.340> from<04:55:47.638> the<04:55:47.820> network 04:55:47.868 --> 04:55:47.878 align:start position:0% this is very different from the network 04:55:47.878 --> 04:55:50.330 align:start position:0% this is very different from the network time<04:55:48.298> protocol<04:55:48.840> it's<04:55:49.680> used<04:55:49.920> for<04:55:50.218> the 04:55:50.330 --> 04:55:50.340 align:start position:0% time protocol it's used for the 04:55:50.340 --> 04:55:53.030 align:start position:0% time protocol it's used for the retrieval<04:55:50.820> and<04:55:51.060> posting<04:55:51.540> of<04:55:52.260> news<04:55:52.680> group 04:55:53.030 --> 04:55:53.040 align:start position:0% retrieval and posting of news group 04:55:53.040 --> 04:55:56.750 align:start position:0% retrieval and posting of news group messages<04:55:53.520> or<04:55:54.480> bulletin<04:55:55.260> messages<04:55:55.520> to<04:55:56.520> the 04:55:56.750 --> 04:55:56.760 align:start position:0% messages or bulletin messages to the 04:55:56.760 --> 04:55:59.030 align:start position:0% messages or bulletin messages to the Usenet<04:55:57.298> which<04:55:57.540> is<04:55:57.660> a<04:55:58.020> worldwide<04:55:58.440> bulletin 04:55:59.030 --> 04:55:59.040 align:start position:0% Usenet which is a worldwide bulletin 04:55:59.040 --> 04:56:01.910 align:start position:0% Usenet which is a worldwide bulletin board<04:55:59.218> that's<04:55:59.520> been<04:55:59.760> around<04:55:59.940> since<04:56:00.540> the<04:56:00.958> 1980s 04:56:01.910 --> 04:56:01.920 align:start position:0% board that's been around since the 1980s 04:56:01.920 --> 04:56:04.490 align:start position:0% board that's been around since the 1980s really<04:56:02.580> since<04:56:03.000> the<04:56:03.298> internet<04:56:03.420> was<04:56:03.900> in<04:56:04.200> its 04:56:04.490 --> 04:56:04.500 align:start position:0% really since the internet was in its 04:56:04.500 --> 04:56:07.550 align:start position:0% really since the internet was in its nascent<04:56:04.920> stages<04:56:05.298> the<04:56:06.298> network<04:56:06.420> news<04:56:06.840> transfer 04:56:07.550 --> 04:56:07.560 align:start position:0% nascent stages the network news transfer 04:56:07.560 --> 04:56:11.090 align:start position:0% nascent stages the network news transfer protocol<04:56:07.980> is<04:56:08.820> also<04:56:09.120> the<04:56:09.240> protocol<04:56:09.600> that<04:56:10.260> RSS 04:56:11.090 --> 04:56:11.100 align:start position:0% protocol is also the protocol that RSS 04:56:11.100 --> 04:56:13.430 align:start position:0% protocol is also the protocol that RSS feeds<04:56:11.580> are<04:56:11.760> based<04:56:12.120> on<04:56:12.180> this<04:56:12.840> stands<04:56:13.320> for 04:56:13.430 --> 04:56:13.440 align:start position:0% feeds are based on this stands for 04:56:13.440 --> 04:56:15.230 align:start position:0% feeds are based on this stands for really 04:56:15.230 --> 04:56:15.240 align:start position:0% really 04:56:15.240 --> 04:56:17.628 align:start position:0% really simple 04:56:17.628 --> 04:56:17.638 align:start position:0% simple 04:56:17.638 --> 04:56:23.090 align:start position:0% simple syndication 04:56:23.090 --> 04:56:23.100 align:start position:0% 04:56:23.100 --> 04:56:25.730 align:start position:0% basically<04:56:23.940> this<04:56:24.660> is<04:56:24.780> where<04:56:25.020> a<04:56:25.260> user<04:56:25.500> can 04:56:25.730 --> 04:56:25.740 align:start position:0% basically this is where a user can 04:56:25.740 --> 04:56:29.570 align:start position:0% basically this is where a user can subscribe<04:56:26.280> to<04:56:26.638> an<04:56:26.878> article<04:56:27.360> web<04:56:27.780> page<04:56:28.138> blog<04:56:29.100> or 04:56:29.570 --> 04:56:29.580 align:start position:0% subscribe to an article web page blog or 04:56:29.580 --> 04:56:31.128 align:start position:0% subscribe to an article web page blog or something<04:56:29.820> similar<04:56:30.420> that<04:56:30.660> uses<04:56:30.958> this 04:56:31.128 --> 04:56:31.138 align:start position:0% something similar that uses this 04:56:31.138 --> 04:56:33.830 align:start position:0% something similar that uses this protocol<04:56:31.440> and<04:56:32.218> when<04:56:32.458> an<04:56:32.700> update<04:56:33.000> is<04:56:33.240> made<04:56:33.480> to 04:56:33.830 --> 04:56:33.840 align:start position:0% protocol and when an update is made to 04:56:33.840 --> 04:56:36.050 align:start position:0% protocol and when an update is made to that<04:56:34.080> page<04:56:34.440> or<04:56:34.680> to<04:56:34.798> that<04:56:34.980> article<04:56:35.458> the 04:56:36.050 --> 04:56:36.060 align:start position:0% that page or to that article the 04:56:36.060 --> 04:56:37.788 align:start position:0% that page or to that article the subscriber<04:56:36.540> is<04:56:36.718> updated 04:56:37.788 --> 04:56:37.798 align:start position:0% subscriber is updated 04:56:37.798 --> 04:56:41.390 align:start position:0% subscriber is updated so<04:56:38.400> in<04:56:38.700> this<04:56:38.878> way<04:56:39.120> you<04:56:40.020> can<04:56:40.138> get<04:56:40.560> updated 04:56:41.390 --> 04:56:41.400 align:start position:0% so in this way you can get updated 04:56:41.400 --> 04:56:43.190 align:start position:0% so in this way you can get updated articles<04:56:41.940> from<04:56:42.240> your<04:56:42.420> favorite<04:56:42.540> web<04:56:42.958> page 04:56:43.190 --> 04:56:43.200 align:start position:0% articles from your favorite web page 04:56:43.200 --> 04:56:45.830 align:start position:0% articles from your favorite web page just<04:56:43.740> like<04:56:43.860> you<04:56:44.100> would<04:56:44.280> new 04:56:45.830 --> 04:56:45.840 align:start position:0% just like you would new 04:56:45.840 --> 04:56:51.288 align:start position:0% just like you would new emails<04:56:47.218> with<04:56:47.940> nntp<04:56:48.660> however<04:56:49.280> only<04:56:50.298> postings 04:56:51.288 --> 04:56:51.298 align:start position:0% emails with nntp however only postings 04:56:51.298 --> 04:56:53.628 align:start position:0% emails with nntp however only postings and<04:56:51.540> articles<04:56:51.900> that<04:56:52.138> are<04:56:52.320> new<04:56:52.440> or<04:56:52.680> updated<04:56:53.100> are 04:56:53.628 --> 04:56:53.638 align:start position:0% and articles that are new or updated are 04:56:53.638 --> 04:56:55.430 align:start position:0% and articles that are new or updated are submitted<04:56:54.120> and<04:56:54.298> retrieved<04:56:54.780> from<04:56:55.020> the<04:56:55.138> server 04:56:55.430 --> 04:56:55.440 align:start position:0% submitted and retrieved from the server 04:56:55.440 --> 04:56:58.730 align:start position:0% submitted and retrieved from the server slightly<04:56:56.280> different<04:56:56.458> from<04:56:56.760> RSS<04:56:57.298> but<04:56:57.780> RSS<04:56:58.320> is 04:56:58.730 --> 04:56:58.740 align:start position:0% slightly different from RSS but RSS is 04:56:58.740 --> 04:57:02.270 align:start position:0% slightly different from RSS but RSS is based<04:56:59.218> on<04:56:59.458> nntp<04:57:00.260> the<04:57:01.260> default<04:57:01.560> port<04:57:01.798> for<04:57:02.100> this 04:57:02.270 --> 04:57:02.280 align:start position:0% based on nntp the default port for this 04:57:02.280 --> 04:57:05.150 align:start position:0% based on nntp the default port for this is<04:57:02.760> port<04:57:03.060> 119. 04:57:05.150 --> 04:57:05.160 align:start position:0% is port 119. 04:57:05.160 --> 04:57:06.830 align:start position:0% is port 119. so<04:57:05.580> we're<04:57:05.940> covering<04:57:06.240> a<04:57:06.420> lot<04:57:06.540> of<04:57:06.660> different 04:57:06.830 --> 04:57:06.840 align:start position:0% so we're covering a lot of different 04:57:06.840 --> 04:57:08.628 align:start position:0% so we're covering a lot of different numbers<04:57:07.138> here<04:57:07.500> it's<04:57:07.860> really<04:57:08.218> important 04:57:08.628 --> 04:57:08.638 align:start position:0% numbers here it's really important 04:57:08.638 --> 04:57:11.750 align:start position:0% numbers here it's really important perhaps<04:57:09.120> even<04:57:09.420> more<04:57:09.718> than<04:57:09.900> memorizing<04:57:10.798> uh 04:57:11.750 --> 04:57:11.760 align:start position:0% perhaps even more than memorizing uh 04:57:11.760 --> 04:57:14.208 align:start position:0% perhaps even more than memorizing uh specifically<04:57:12.540> what<04:57:13.080> each<04:57:13.378> protocol<04:57:13.860> does 04:57:14.208 --> 04:57:14.218 align:start position:0% specifically what each protocol does 04:57:14.218 --> 04:57:16.610 align:start position:0% specifically what each protocol does that<04:57:14.458> you<04:57:14.700> definitely<04:57:15.120> memorize<04:57:15.900> which<04:57:16.378> Port 04:57:16.610 --> 04:57:16.620 align:start position:0% that you definitely memorize which Port 04:57:16.620 --> 04:57:19.070 align:start position:0% that you definitely memorize which Port it's<04:57:16.920> a<04:57:17.100> part<04:57:17.218> of<04:57:17.400> if<04:57:17.940> you<04:57:18.180> can<04:57:18.240> memorize<04:57:18.718> by 04:57:19.070 --> 04:57:19.080 align:start position:0% it's a part of if you can memorize by 04:57:19.080 --> 04:57:20.750 align:start position:0% it's a part of if you can memorize by the<04:57:19.200> way<04:57:19.320> the<04:57:19.860> number 04:57:20.750 --> 04:57:20.760 align:start position:0% the way the number 04:57:20.760 --> 04:57:23.270 align:start position:0% the way the number and<04:57:21.240> what<04:57:21.420> the<04:57:21.540> acronym<04:57:21.958> means<04:57:22.378> you<04:57:22.920> should<04:57:23.100> be 04:57:23.270 --> 04:57:23.280 align:start position:0% and what the acronym means you should be 04:57:23.280 --> 04:57:25.850 align:start position:0% and what the acronym means you should be fine<04:57:23.520> now<04:57:24.120> a<04:57:24.298> protocol<04:57:24.600> you<04:57:24.900> use<04:57:25.080> every<04:57:25.620> day 04:57:25.850 --> 04:57:25.860 align:start position:0% fine now a protocol you use every day 04:57:25.860 --> 04:57:29.208 align:start position:0% fine now a protocol you use every day even<04:57:26.160> if<04:57:26.340> you<04:57:26.458> don't<04:57:26.580> realize<04:57:27.000> it<04:57:27.240> is<04:57:27.780> HTTP<04:57:28.620> or 04:57:29.208 --> 04:57:29.218 align:start position:0% even if you don't realize it is HTTP or 04:57:29.218 --> 04:57:32.510 align:start position:0% even if you don't realize it is HTTP or the<04:57:29.458> hypertext<04:57:30.120> transfer<04:57:31.020> protocol<04:57:31.560> this<04:57:32.340> is 04:57:32.510 --> 04:57:32.520 align:start position:0% the hypertext transfer protocol this is 04:57:32.520 --> 04:57:35.570 align:start position:0% the hypertext transfer protocol this is used<04:57:32.760> to<04:57:33.120> view<04:57:33.320> unsecure<04:57:34.320> web<04:57:34.740> pages<04:57:35.040> and 04:57:35.570 --> 04:57:35.580 align:start position:0% used to view unsecure web pages and 04:57:35.580 --> 04:57:38.208 align:start position:0% used to view unsecure web pages and allows<04:57:36.000> users<04:57:36.540> to<04:57:37.020> connect<04:57:37.378> to<04:57:37.798> and 04:57:38.208 --> 04:57:38.218 align:start position:0% allows users to connect to and 04:57:38.218 --> 04:57:41.030 align:start position:0% allows users to connect to and communicate<04:57:38.700> with<04:57:39.060> web<04:57:39.360> servers<04:57:40.040> although 04:57:41.030 --> 04:57:41.040 align:start position:0% communicate with web servers although 04:57:41.040 --> 04:57:44.530 align:start position:0% communicate with web servers although HTTP<04:57:41.820> is<04:57:42.120> going<04:57:42.298> to<04:57:42.600> define<04:57:43.160> the<04:57:44.160> transmission 04:57:44.530 --> 04:57:44.540 align:start position:0% HTTP is going to define the transmission 04:57:44.540 --> 04:57:47.510 align:start position:0% HTTP is going to define the transmission and<04:57:45.540> the<04:57:45.718> format<04:57:46.080> of<04:57:46.260> messages<04:57:46.500> and<04:57:47.340> the 04:57:47.510 --> 04:57:47.520 align:start position:0% and the format of messages and the 04:57:47.520 --> 04:57:50.150 align:start position:0% and the format of messages and the actions<04:57:47.940> taken<04:57:48.420> by<04:57:48.718> web<04:57:48.958> servers<04:57:49.500> when<04:57:49.798> users 04:57:50.150 --> 04:57:50.160 align:start position:0% actions taken by web servers when users 04:57:50.160 --> 04:57:54.288 align:start position:0% actions taken by web servers when users interact<04:57:50.580> with<04:57:50.878> it<04:57:51.320> HTTP<04:57:52.320> is<04:57:52.560> what<04:57:52.798> we<04:57:52.920> call<04:57:53.298> a 04:57:54.288 --> 04:57:54.298 align:start position:0% interact with it HTTP is what we call a 04:57:54.298 --> 04:57:57.770 align:start position:0% interact with it HTTP is what we call a stateless<04:57:55.020> protocol<04:57:56.180> meaning<04:57:57.180> that<04:57:57.480> it<04:57:57.600> may 04:57:57.770 --> 04:57:57.780 align:start position:0% stateless protocol meaning that it may 04:57:57.780 --> 04:58:01.010 align:start position:0% stateless protocol meaning that it may be<04:57:57.958> difficult<04:57:58.320> to<04:57:58.798> get<04:57:58.980> a<04:57:59.520> lot<04:57:59.940> of<04:58:00.180> intelligent 04:58:01.010 --> 04:58:01.020 align:start position:0% be difficult to get a lot of intelligent 04:58:01.020 --> 04:58:03.590 align:start position:0% be difficult to get a lot of intelligent interactive<04:58:01.860> responses<04:58:02.638> to<04:58:03.180> the<04:58:03.420> information 04:58:03.590 --> 04:58:03.600 align:start position:0% interactive responses to the information 04:58:03.600 --> 04:58:07.010 align:start position:0% interactive responses to the information if<04:58:04.560> you<04:58:04.740> remember<04:58:04.920> ever<04:58:05.340> making<04:58:05.700> very<04:58:06.480> basic 04:58:07.010 --> 04:58:07.020 align:start position:0% if you remember ever making very basic 04:58:07.020 --> 04:58:11.570 align:start position:0% if you remember ever making very basic web<04:58:07.320> pages<04:58:07.620> using<04:58:08.458> HTML<04:58:09.360> or<04:58:10.080> the<04:58:10.580> hypertext 04:58:11.570 --> 04:58:11.580 align:start position:0% web pages using HTML or the hypertext 04:58:11.580 --> 04:58:15.530 align:start position:0% web pages using HTML or the hypertext markup<04:58:12.480> language<04:58:13.218> the<04:58:14.218> language<04:58:14.520> that<04:58:14.878> HTTP 04:58:15.530 --> 04:58:15.540 align:start position:0% markup language the language that HTTP 04:58:15.540 --> 04:58:17.570 align:start position:0% markup language the language that HTTP is<04:58:15.840> reading<04:58:16.260> then<04:58:16.620> you<04:58:16.860> probably<04:58:17.040> know<04:58:17.340> this 04:58:17.570 --> 04:58:17.580 align:start position:0% is reading then you probably know this 04:58:17.580 --> 04:58:20.690 align:start position:0% is reading then you probably know this so<04:58:18.120> if<04:58:18.360> you<04:58:18.420> want<04:58:18.718> more<04:58:19.020> interactive<04:58:19.860> web<04:58:20.400> page 04:58:20.690 --> 04:58:20.700 align:start position:0% so if you want more interactive web page 04:58:20.700 --> 04:58:23.690 align:start position:0% so if you want more interactive web page Pages<04:58:21.000> or<04:58:21.420> interaction<04:58:21.900> with<04:58:22.440> web<04:58:22.680> pages<04:58:23.040> then 04:58:23.690 --> 04:58:23.700 align:start position:0% Pages or interaction with web pages then 04:58:23.700 --> 04:58:25.490 align:start position:0% Pages or interaction with web pages then you're<04:58:24.000> going<04:58:24.120> to<04:58:24.298> use<04:58:24.540> different<04:58:24.958> add-ons 04:58:25.490 --> 04:58:25.500 align:start position:0% you're going to use different add-ons 04:58:25.500 --> 04:58:27.948 align:start position:0% you're going to use different add-ons such<04:58:26.280> as<04:58:26.520> ActiveX<04:58:27.298> that<04:58:27.540> you<04:58:27.718> might<04:58:27.840> have 04:58:27.948 --> 04:58:27.958 align:start position:0% such as ActiveX that you might have 04:58:27.958 --> 04:58:29.890 align:start position:0% such as ActiveX that you might have heard<04:58:28.200> of 04:58:29.890 --> 04:58:29.900 align:start position:0% heard of 04:58:29.900 --> 04:58:34.070 align:start position:0% heard of HTTP<04:58:30.900> defaults<04:58:31.740> Port<04:58:31.980> is<04:58:32.580> Port<04:58:32.940> 80<04:58:33.240> and<04:58:33.900> a 04:58:34.070 --> 04:58:34.080 align:start position:0% HTTP defaults Port is Port 80 and a 04:58:34.080 --> 04:58:36.490 align:start position:0% HTTP defaults Port is Port 80 and a common<04:58:34.260> alternate<04:58:34.920> port<04:58:35.100> for<04:58:35.340> it<04:58:35.520> is<04:58:36.000> Port 04:58:36.490 --> 04:58:36.500 align:start position:0% common alternate port for it is Port 04:58:36.500 --> 04:58:41.590 align:start position:0% common alternate port for it is Port 8080.<04:58:37.500> now<04:58:37.798> similar<04:58:38.580> to<04:58:38.940> http<04:58:39.660> is<04:58:40.200> https 04:58:41.590 --> 04:58:41.600 align:start position:0% 8080. now similar to http is https 04:58:41.600 --> 04:58:46.190 align:start position:0% 8080. now similar to http is https or<04:58:42.600> hypertext<04:58:43.200> transfer<04:58:43.740> protocol<04:58:44.100> over<04:58:44.638> SSL 04:58:46.190 --> 04:58:46.200 align:start position:0% or hypertext transfer protocol over SSL 04:58:46.200 --> 04:58:50.868 align:start position:0% or hypertext transfer protocol over SSL which<04:58:46.798> is<04:58:46.980> the<04:58:47.638> secure<04:58:48.360> socket<04:58:49.200> layer<04:58:49.798> this<04:58:50.638> is 04:58:50.868 --> 04:58:50.878 align:start position:0% which is the secure socket layer this is 04:58:50.878 --> 04:58:54.230 align:start position:0% which is the secure socket layer this is a<04:58:51.298> secure<04:58:51.718> version<04:58:51.958> of<04:58:52.260> HTTP<04:58:52.980> so<04:58:53.820> if<04:58:53.940> you<04:58:54.060> ever 04:58:54.230 --> 04:58:54.240 align:start position:0% a secure version of HTTP so if you ever 04:58:54.240 --> 04:58:55.910 align:start position:0% a secure version of HTTP so if you ever see<04:58:54.420> an<04:58:54.660> s<04:58:54.780> on<04:58:55.020> the<04:58:55.200> end<04:58:55.260> of<04:58:55.440> just<04:58:55.560> about<04:58:55.680> any 04:58:55.910 --> 04:58:55.920 align:start position:0% see an s on the end of just about any 04:58:55.920 --> 04:58:58.550 align:start position:0% see an s on the end of just about any protocol<04:58:56.340> you<04:58:57.120> can<04:58:57.240> bet<04:58:57.600> that<04:58:57.900> that<04:58:58.080> has<04:58:58.260> to<04:58:58.440> do 04:58:58.550 --> 04:58:58.560 align:start position:0% protocol you can bet that that has to do 04:58:58.560 --> 04:59:01.250 align:start position:0% protocol you can bet that that has to do with<04:58:58.860> this<04:58:59.100> being<04:58:59.638> secure<04:59:00.120> and<04:59:00.660> it<04:59:00.840> creates 04:59:01.250 --> 04:59:01.260 align:start position:0% with this being secure and it creates 04:59:01.260 --> 04:59:03.948 align:start position:0% with this being secure and it creates secure<04:59:01.798> connections<04:59:02.458> between<04:59:03.060> your<04:59:03.540> browser 04:59:03.948 --> 04:59:03.958 align:start position:0% secure connections between your browser 04:59:03.958 --> 04:59:07.570 align:start position:0% secure connections between your browser and<04:59:04.378> the<04:59:04.560> web<04:59:04.680> server<04:59:05.458> it<04:59:06.120> does<04:59:06.298> this<04:59:06.540> using 04:59:07.570 --> 04:59:07.580 align:start position:0% and the web server it does this using 04:59:07.580 --> 04:59:11.570 align:start position:0% and the web server it does this using SSL<04:59:08.580> or<04:59:09.298> the<04:59:09.660> secure 04:59:11.570 --> 04:59:11.580 align:start position:0% SSL or the secure 04:59:11.580 --> 04:59:14.208 align:start position:0% SSL or the secure sockets 04:59:14.208 --> 04:59:14.218 align:start position:0% sockets 04:59:14.218 --> 04:59:16.070 align:start position:0% sockets layer 04:59:16.070 --> 04:59:16.080 align:start position:0% layer 04:59:16.080 --> 04:59:17.930 align:start position:0% layer we're<04:59:16.500> going<04:59:16.620> to<04:59:16.740> discuss<04:59:17.160> the<04:59:17.638> secure 04:59:17.930 --> 04:59:17.940 align:start position:0% we're going to discuss the secure 04:59:17.940 --> 04:59:20.390 align:start position:0% we're going to discuss the secure sockets<04:59:18.420> layer<04:59:18.840> when<04:59:19.138> we<04:59:19.320> discuss<04:59:19.680> encryption 04:59:20.390 --> 04:59:20.400 align:start position:0% sockets layer when we discuss encryption 04:59:20.400 --> 04:59:23.150 align:start position:0% sockets layer when we discuss encryption more<04:59:21.060> detail<04:59:21.540> in<04:59:21.718> a<04:59:21.900> future<04:59:22.020> lesson 04:59:23.150 --> 04:59:23.160 align:start position:0% more detail in a future lesson 04:59:23.160 --> 04:59:27.590 align:start position:0% more detail in a future lesson now<04:59:23.700> most<04:59:24.240> web<04:59:24.540> pages<04:59:24.780> support<04:59:25.440> https<04:59:26.600> and 04:59:27.590 --> 04:59:27.600 align:start position:0% now most web pages support https and 04:59:27.600 --> 04:59:29.448 align:start position:0% now most web pages support https and it's<04:59:27.900> recommended<04:59:28.500> that<04:59:28.680> you<04:59:28.920> use<04:59:29.100> it<04:59:29.280> over 04:59:29.448 --> 04:59:29.458 align:start position:0% it's recommended that you use it over 04:59:29.458 --> 04:59:31.910 align:start position:0% it's recommended that you use it over HTTP<04:59:30.298> almost<04:59:30.840> every<04:59:31.080> time<04:59:31.320> you're<04:59:31.560> able<04:59:31.798> to 04:59:31.910 --> 04:59:31.920 align:start position:0% HTTP almost every time you're able to 04:59:31.920 --> 04:59:35.570 align:start position:0% HTTP almost every time you're able to the<04:59:32.580> way<04:59:32.700> you<04:59:32.940> do<04:59:33.120> this<04:59:33.360> is<04:59:34.080> simply<04:59:34.500> by<04:59:35.160> using 04:59:35.570 --> 04:59:35.580 align:start position:0% the way you do this is simply by using 04:59:35.580 --> 04:59:39.190 align:start position:0% the way you do this is simply by using instead<04:59:36.540> of<04:59:36.660> HTTP<04:59:37.440> colon<04:59:38.100> slash<04:59:38.458> slash 04:59:39.190 --> 04:59:39.200 align:start position:0% instead of HTTP colon slash slash 04:59:39.200 --> 04:59:43.310 align:start position:0% instead of HTTP colon slash slash facebook.com<04:59:40.400> just<04:59:41.400> put<04:59:41.760> an<04:59:42.120> S<04:59:42.298> in<04:59:42.540> front 04:59:43.310 --> 04:59:43.320 align:start position:0% facebook.com just put an S in front 04:59:43.320 --> 04:59:45.890 align:start position:0% facebook.com just put an S in front yes<04:59:43.980> Facebook<04:59:44.400> supports<04:59:45.060> this<04:59:45.180> as<04:59:45.480> do<04:59:45.660> other 04:59:45.890 --> 04:59:45.900 align:start position:0% yes Facebook supports this as do other 04:59:45.900 --> 04:59:48.708 align:start position:0% yes Facebook supports this as do other social<04:59:46.200> media<04:59:46.620> sites<04:59:47.040> and<04:59:47.458> even<04:59:47.638> email<04:59:48.060> and 04:59:48.708 --> 04:59:48.718 align:start position:0% social media sites and even email and 04:59:48.718 --> 04:59:51.350 align:start position:0% social media sites and even email and even<04:59:48.840> Google<04:59:49.200> supports<04:59:49.798> https<04:59:50.340> why<04:59:51.120> would<04:59:51.240> you 04:59:51.350 --> 04:59:51.360 align:start position:0% even Google supports https why would you 04:59:51.360 --> 04:59:53.030 align:start position:0% even Google supports https why would you want<04:59:51.480> to<04:59:51.600> do<04:59:51.660> this<04:59:51.840> well<04:59:52.260> say<04:59:52.500> someone<04:59:52.798> is 04:59:53.030 --> 04:59:53.040 align:start position:0% want to do this well say someone is 04:59:53.040 --> 04:59:56.690 align:start position:0% want to do this well say someone is browsing<04:59:53.638> and<04:59:54.000> or<04:59:54.620> listening<04:59:55.620> in<04:59:55.860> to<04:59:56.458> your 04:59:56.690 --> 04:59:56.700 align:start position:0% browsing and or listening in to your 04:59:56.700 --> 04:59:58.310 align:start position:0% browsing and or listening in to your Google<04:59:56.940> searches<04:59:57.600> that<04:59:58.080> might<04:59:58.200> be 04:59:58.310 --> 04:59:58.320 align:start position:0% Google searches that might be 04:59:58.320 --> 04:59:59.690 align:start position:0% Google searches that might be information<04:59:58.500> you<04:59:58.980> don't<04:59:59.100> want<04:59:59.280> someone<04:59:59.520> else 04:59:59.690 --> 04:59:59.700 align:start position:0% information you don't want someone else 04:59:59.700 --> 05:00:00.708 align:start position:0% information you don't want someone else to<04:59:59.940> know 05:00:00.708 --> 05:00:00.718 align:start position:0% to know 05:00:00.718 --> 05:00:03.230 align:start position:0% to know just<05:00:01.200> as<05:00:01.378> a<05:00:01.620> recommendation<05:00:02.340> absolutely 05:00:03.230 --> 05:00:03.240 align:start position:0% just as a recommendation absolutely 05:00:03.240 --> 05:00:05.090 align:start position:0% just as a recommendation absolutely anytime<05:00:03.660> you<05:00:03.840> visit<05:00:04.020> any<05:00:04.320> website<05:00:04.680> but 05:00:05.090 --> 05:00:05.100 align:start position:0% anytime you visit any website but 05:00:05.100 --> 05:00:08.390 align:start position:0% anytime you visit any website but especially<05:00:05.840> Financial<05:00:06.840> uh<05:00:07.798> institutions 05:00:08.390 --> 05:00:08.400 align:start position:0% especially Financial uh institutions 05:00:08.400 --> 05:00:11.208 align:start position:0% especially Financial uh institutions such<05:00:08.760> as<05:00:08.878> your<05:00:09.240> bank<05:00:09.560> or<05:00:10.560> your<05:00:10.680> credit<05:00:10.920> union 05:00:11.208 --> 05:00:11.218 align:start position:0% such as your bank or your credit union 05:00:11.218 --> 05:00:13.490 align:start position:0% such as your bank or your credit union you<05:00:11.820> want<05:00:11.878> to<05:00:12.060> ensure<05:00:12.360> that<05:00:12.600> in<05:00:12.900> the<05:00:13.020> bar<05:00:13.200> it 05:00:13.490 --> 05:00:13.500 align:start position:0% you want to ensure that in the bar it 05:00:13.500 --> 05:00:17.390 align:start position:0% you want to ensure that in the bar it says<05:00:13.798> https<05:00:14.840> if<05:00:15.840> it's<05:00:16.020> not<05:00:16.320> then<05:00:16.860> opening 05:00:17.390 --> 05:00:17.400 align:start position:0% says https if it's not then opening 05:00:17.400 --> 05:00:19.128 align:start position:0% says https if it's not then opening anything<05:00:17.700> in<05:00:18.060> this<05:00:18.180> including<05:00:18.660> typing<05:00:18.958> in 05:00:19.128 --> 05:00:19.138 align:start position:0% anything in this including typing in 05:00:19.138 --> 05:00:20.930 align:start position:0% anything in this including typing in your<05:00:19.260> bank<05:00:19.440> password<05:00:19.740> could<05:00:20.400> be<05:00:20.638> really 05:00:20.930 --> 05:00:20.940 align:start position:0% your bank password could be really 05:00:20.940 --> 05:00:22.010 align:start position:0% your bank password could be really serious 05:00:22.010 --> 05:00:22.020 align:start position:0% serious 05:00:22.020 --> 05:00:23.750 align:start position:0% serious the<05:00:22.440> same<05:00:22.620> goes<05:00:22.980> for<05:00:23.160> anything<05:00:23.340> when<05:00:23.638> we're 05:00:23.750 --> 05:00:23.760 align:start position:0% the same goes for anything when we're 05:00:23.760 --> 05:00:25.730 align:start position:0% the same goes for anything when we're dealing<05:00:24.060> with<05:00:24.240> credit<05:00:24.718> cards<05:00:25.200> for<05:00:25.500> instance 05:00:25.730 --> 05:00:25.740 align:start position:0% dealing with credit cards for instance 05:00:25.740 --> 05:00:28.270 align:start position:0% dealing with credit cards for instance buying<05:00:26.280> something<05:00:26.520> make<05:00:27.120> sure<05:00:27.298> that<05:00:27.540> https 05:00:28.270 --> 05:00:28.280 align:start position:0% buying something make sure that https 05:00:28.280 --> 05:00:31.910 align:start position:0% buying something make sure that https appears<05:00:29.280> in<05:00:30.000> the<05:00:30.120> bar<05:00:30.298> or<05:00:30.780> in<05:00:30.958> your<05:00:31.138> url<05:00:31.500> bar<05:00:31.680> at 05:00:31.910 --> 05:00:31.920 align:start position:0% appears in the bar or in your url bar at 05:00:31.920 --> 05:00:34.010 align:start position:0% appears in the bar or in your url bar at the<05:00:32.100> top<05:00:32.218> as<05:00:32.940> we've<05:00:33.120> mentioned<05:00:33.420> before<05:00:33.600> too 05:00:34.010 --> 05:00:34.020 align:start position:0% the top as we've mentioned before too 05:00:34.020 --> 05:00:38.990 align:start position:0% the top as we've mentioned before too the<05:00:34.740> default<05:00:35.100> Port<05:00:35.458> is<05:00:36.420> Port<05:00:36.780> 443 05:00:38.990 --> 05:00:39.000 align:start position:0% the default Port is Port 443 05:00:39.000 --> 05:00:41.448 align:start position:0% the default Port is Port 443 now<05:00:39.420> the<05:00:39.600> last<05:00:39.718> port<05:00:39.958> I<05:00:40.200> want<05:00:40.320> to<05:00:40.440> discuss<05:00:40.798> is 05:00:41.448 --> 05:00:41.458 align:start position:0% now the last port I want to discuss is 05:00:41.458 --> 05:00:45.590 align:start position:0% now the last port I want to discuss is RDP<05:00:42.060> or<05:00:42.420> the<05:00:42.660> remote<05:00:42.900> desktop<05:00:43.740> protocol<05:00:44.600> RDP 05:00:45.590 --> 05:00:45.600 align:start position:0% RDP or the remote desktop protocol RDP 05:00:45.600 --> 05:00:47.990 align:start position:0% RDP or the remote desktop protocol RDP servers<05:00:46.080> are<05:00:46.440> built<05:00:46.860> into<05:00:47.160> the<05:00:47.580> Microsoft 05:00:47.990 --> 05:00:48.000 align:start position:0% servers are built into the Microsoft 05:00:48.000 --> 05:00:51.770 align:start position:0% servers are built into the Microsoft operating<05:00:48.600> system<05:00:48.900> such<05:00:49.740> as<05:00:50.060> Windows<05:00:51.060> by 05:00:51.770 --> 05:00:51.780 align:start position:0% operating system such as Windows by 05:00:51.780 --> 05:00:54.590 align:start position:0% operating system such as Windows by default<05:00:52.200> and<05:00:53.100> it<05:00:53.280> provides<05:00:53.638> users<05:00:54.000> with<05:00:54.360> a 05:00:54.590 --> 05:00:54.600 align:start position:0% default and it provides users with a 05:00:54.600 --> 05:00:59.510 align:start position:0% default and it provides users with a graphical<05:00:55.080> user<05:00:55.920> interface<05:00:56.400> or<05:00:57.298> a<05:00:57.780> GUI 05:00:59.510 --> 05:00:59.520 align:start position:0% graphical user interface or a GUI 05:00:59.520 --> 05:01:02.090 align:start position:0% graphical user interface or a GUI to<05:01:00.120> another<05:01:00.360> computer<05:01:00.840> over<05:01:01.680> a<05:01:01.920> network 05:01:02.090 --> 05:01:02.100 align:start position:0% to another computer over a network 05:01:02.100 --> 05:01:03.110 align:start position:0% to another computer over a network connection 05:01:03.110 --> 05:01:03.120 align:start position:0% connection 05:01:03.120 --> 05:01:05.448 align:start position:0% connection so<05:01:03.600> this<05:01:03.780> protocol<05:01:04.138> allows<05:01:04.740> users<05:01:05.160> to 05:01:05.448 --> 05:01:05.458 align:start position:0% so this protocol allows users to 05:01:05.458 --> 05:01:09.288 align:start position:0% so this protocol allows users to remotely<05:01:06.420> manage<05:01:07.320> administer<05:01:08.280> and<05:01:09.060> access 05:01:09.288 --> 05:01:09.298 align:start position:0% remotely manage administer and access 05:01:09.298 --> 05:01:11.830 align:start position:0% remotely manage administer and access network<05:01:09.780> resources<05:01:10.500> from<05:01:10.980> another<05:01:11.160> physical 05:01:11.830 --> 05:01:11.840 align:start position:0% network resources from another physical 05:01:11.840 --> 05:01:15.650 align:start position:0% network resources from another physical location<05:01:13.040> over<05:01:14.040> the<05:01:14.638> Internet<05:01:14.820> which<05:01:15.480> is 05:01:15.650 --> 05:01:15.660 align:start position:0% location over the Internet which is 05:01:15.660 --> 05:01:18.350 align:start position:0% location over the Internet which is represented<05:01:16.200> by<05:01:16.500> the<05:01:16.740> cloud<05:01:16.940> there<05:01:17.940> are<05:01:18.060> a<05:01:18.240> few 05:01:18.350 --> 05:01:18.360 align:start position:0% represented by the cloud there are a few 05:01:18.360 --> 05:01:21.470 align:start position:0% represented by the cloud there are a few security<05:01:18.718> concerns<05:01:19.620> that<05:01:20.040> come<05:01:20.280> with 05:01:21.470 --> 05:01:21.480 align:start position:0% security concerns that come with 05:01:21.480 --> 05:01:25.128 align:start position:0% security concerns that come with um<05:01:21.958> RDP<05:01:22.820> and<05:01:23.820> there<05:01:24.180> is<05:01:24.360> potential<05:01:24.840> for 05:01:25.128 --> 05:01:25.138 align:start position:0% um RDP and there is potential for 05:01:25.138 --> 05:01:27.590 align:start position:0% um RDP and there is potential for certain<05:01:25.320> sort<05:01:25.680> of<05:01:25.860> computer<05:01:26.458> attacks<05:01:27.180> so 05:01:27.590 --> 05:01:27.600 align:start position:0% certain sort of computer attacks so 05:01:27.600 --> 05:01:29.868 align:start position:0% certain sort of computer attacks so there<05:01:27.840> are<05:01:28.020> also<05:01:28.280> non-microsoft<05:01:29.280> variations 05:01:29.868 --> 05:01:29.878 align:start position:0% there are also non-microsoft variations 05:01:29.878 --> 05:01:33.288 align:start position:0% there are also non-microsoft variations available<05:01:30.440> such<05:01:31.440> as<05:01:31.680> something<05:01:31.980> called<05:01:32.458> our 05:01:33.288 --> 05:01:33.298 align:start position:0% available such as something called our 05:01:33.298 --> 05:01:35.930 align:start position:0% available such as something called our desktop 05:01:35.930 --> 05:01:35.940 align:start position:0% 05:01:35.940 --> 05:01:38.810 align:start position:0% for<05:01:36.540> Unix 05:01:38.810 --> 05:01:38.820 align:start position:0% for Unix 05:01:38.820 --> 05:01:41.150 align:start position:0% for Unix which<05:01:39.718> if<05:01:40.020> you<05:01:40.260> are<05:01:40.440> going<05:01:40.560> to<05:01:40.680> be<05:01:40.740> doing<05:01:40.920> a<05:01:41.100> lot 05:01:41.150 --> 05:01:41.160 align:start position:0% which if you are going to be doing a lot 05:01:41.160 --> 05:01:43.430 align:start position:0% which if you are going to be doing a lot of<05:01:41.280> remoting<05:01:41.760> you<05:01:42.000> might<05:01:42.120> want<05:01:42.298> to<05:01:42.540> look<05:01:42.600> into 05:01:43.430 --> 05:01:43.440 align:start position:0% of remoting you might want to look into 05:01:43.440 --> 05:01:47.170 align:start position:0% of remoting you might want to look into RDP<05:01:44.280> by<05:01:44.580> the<05:01:44.700> way<05:01:44.820> uses<05:01:45.600> default<05:01:46.080> Port 05:01:47.170 --> 05:01:47.180 align:start position:0% RDP by the way uses default Port 05:01:47.180 --> 05:01:50.448 align:start position:0% RDP by the way uses default Port 3389<05:01:48.180> although<05:01:48.718> you<05:01:48.900> can<05:01:49.138> change<05:01:49.500> that 05:01:50.448 --> 05:01:50.458 align:start position:0% 3389 although you can change that 05:01:50.458 --> 05:01:52.970 align:start position:0% 3389 although you can change that usually<05:01:51.120> as<05:01:51.420> well<05:01:51.600> when<05:01:52.020> we're<05:01:52.138> using<05:01:52.440> RDP 05:01:52.970 --> 05:01:52.980 align:start position:0% usually as well when we're using RDP 05:01:52.980 --> 05:01:54.708 align:start position:0% usually as well when we're using RDP we're<05:01:53.400> also<05:01:53.700> going<05:01:53.760> to<05:01:53.878> use<05:01:54.000> it<05:01:54.240> over<05:01:54.420> what's 05:01:54.708 --> 05:01:54.718 align:start position:0% we're also going to use it over what's 05:01:54.718 --> 05:01:57.350 align:start position:0% we're also going to use it over what's called<05:01:55.080> a<05:01:55.500> VPN<05:01:56.040> or<05:01:56.340> virtual<05:01:56.760> private<05:01:57.180> Network 05:01:57.350 --> 05:01:57.360 align:start position:0% called a VPN or virtual private Network 05:01:57.360 --> 05:02:01.430 align:start position:0% called a VPN or virtual private Network which<05:01:58.320> creates<05:01:58.860> a<05:01:59.458> tunnel 05:02:01.430 --> 05:02:01.440 align:start position:0% which creates a tunnel 05:02:01.440 --> 05:02:03.650 align:start position:0% which creates a tunnel through<05:02:01.980> which<05:02:02.280> your<05:02:02.760> connection<05:02:02.940> occurs 05:02:03.650 --> 05:02:03.660 align:start position:0% through which your connection occurs 05:02:03.660 --> 05:02:06.050 align:start position:0% through which your connection occurs this<05:02:04.320> improves<05:02:04.798> the<05:02:05.100> security<05:02:05.280> we<05:02:05.760> were<05:02:05.940> just 05:02:06.050 --> 05:02:06.060 align:start position:0% this improves the security we were just 05:02:06.060 --> 05:02:08.690 align:start position:0% this improves the security we were just talking<05:02:06.298> about<05:02:06.540> so<05:02:07.500> let's<05:02:07.798> review<05:02:08.040> what<05:02:08.458> we've 05:02:08.690 --> 05:02:08.700 align:start position:0% talking about so let's review what we've 05:02:08.700 --> 05:02:10.850 align:start position:0% talking about so let's review what we've just<05:02:08.878> talked<05:02:09.240> about<05:02:09.298> first<05:02:10.080> we<05:02:10.378> talked<05:02:10.740> about 05:02:10.850 --> 05:02:10.860 align:start position:0% just talked about first we talked about 05:02:10.860 --> 05:02:14.090 align:start position:0% just talked about first we talked about a<05:02:11.100> port<05:02:11.280> being<05:02:12.000> The<05:02:12.420> Logical<05:02:12.780> endpoint<05:02:13.500> of<05:02:13.860> a 05:02:14.090 --> 05:02:14.100 align:start position:0% a port being The Logical endpoint of a 05:02:14.100 --> 05:02:15.170 align:start position:0% a port being The Logical endpoint of a connection 05:02:15.170 --> 05:02:15.180 align:start position:0% connection 05:02:15.180 --> 05:02:19.368 align:start position:0% connection and<05:02:15.780> then<05:02:15.958> we<05:02:16.520> outlined<05:02:17.940> the<05:02:18.600> port<05:02:18.718> ranges 05:02:19.368 --> 05:02:19.378 align:start position:0% and then we outlined the port ranges 05:02:19.378 --> 05:02:24.770 align:start position:0% and then we outlined the port ranges remember<05:02:20.040> we<05:02:20.458> had<05:02:20.700> the<05:02:21.180> well-known<05:02:21.540> ports 05:02:24.770 --> 05:02:24.780 align:start position:0% 05:02:24.780 --> 05:02:27.890 align:start position:0% the<05:02:25.260> registered<05:02:25.740> ports 05:02:27.890 --> 05:02:27.900 align:start position:0% the registered ports 05:02:27.900 --> 05:02:31.490 align:start position:0% the registered ports and<05:02:28.378> then<05:02:28.500> the<05:02:28.798> dynamic 05:02:31.490 --> 05:02:31.500 align:start position:0% 05:02:31.500 --> 05:02:35.448 align:start position:0% or<05:02:32.040> private<05:02:32.580> or<05:02:33.298> experimental<05:02:34.138> ports<05:02:34.560> what<05:02:35.280> we 05:02:35.448 --> 05:02:35.458 align:start position:0% or private or experimental ports what we 05:02:35.458 --> 05:02:38.390 align:start position:0% or private or experimental ports what we really<05:02:35.638> want<05:02:36.000> to<05:02:36.180> uh<05:02:36.798> learn<05:02:37.798> for<05:02:38.040> ourselves 05:02:38.390 --> 05:02:38.400 align:start position:0% really want to uh learn for ourselves 05:02:38.400 --> 05:02:40.730 align:start position:0% really want to uh learn for ourselves are<05:02:38.878> the<05:02:39.060> well-known<05:02:39.540> ports 05:02:40.730 --> 05:02:40.740 align:start position:0% are the well-known ports 05:02:40.740 --> 05:02:42.830 align:start position:0% are the well-known ports I<05:02:41.218> then<05:02:41.400> outlined<05:02:42.060> the<05:02:42.360> most<05:02:42.480> common 05:02:42.830 --> 05:02:42.840 align:start position:0% I then outlined the most common 05:02:42.840 --> 05:02:44.750 align:start position:0% I then outlined the most common well-known<05:02:43.378> default<05:02:43.860> ports<05:02:44.340> and<05:02:44.580> their 05:02:44.750 --> 05:02:44.760 align:start position:0% well-known default ports and their 05:02:44.760 --> 05:02:48.230 align:start position:0% well-known default ports and their protocols<05:02:45.420> you<05:02:46.080> want<05:02:46.320> to<05:02:46.560> memorize<05:02:47.400> this 05:02:48.230 --> 05:02:48.240 align:start position:0% protocols you want to memorize this 05:02:48.240 --> 05:02:49.970 align:start position:0% protocols you want to memorize this table 05:02:49.970 --> 05:02:49.980 align:start position:0% table 05:02:49.980 --> 05:02:54.530 align:start position:0% table for<05:02:50.820> the<05:02:51.060> network<05:02:51.240> plus<05:02:51.540> exam 05:02:54.530 --> 05:02:54.540 align:start position:0% 05:02:54.540 --> 05:02:56.930 align:start position:0% I<05:02:55.138> guarantee<05:02:55.560> you<05:02:55.740> doing<05:02:55.980> that<05:02:56.218> will<05:02:56.580> get<05:02:56.760> you 05:02:56.930 --> 05:02:56.940 align:start position:0% I guarantee you doing that will get you 05:02:56.940 --> 05:02:59.510 align:start position:0% I guarantee you doing that will get you a<05:02:57.298> bunch<05:02:57.480> of<05:02:57.600> questions<05:02:57.900> on<05:02:58.320> the<05:02:58.440> exam 05:02:59.510 --> 05:02:59.520 align:start position:0% a bunch of questions on the exam 05:02:59.520 --> 05:03:01.788 align:start position:0% a bunch of questions on the exam finally<05:03:00.000> we<05:03:00.180> Define<05:03:00.420> to<05:03:00.780> describe<05:03:01.320> some<05:03:01.680> of 05:03:01.788 --> 05:03:01.798 align:start position:0% finally we Define to describe some of 05:03:01.798 --> 05:03:04.910 align:start position:0% finally we Define to describe some of the<05:03:01.980> specific<05:03:02.340> ports<05:03:02.940> and<05:03:03.780> not<05:03:04.080> only<05:03:04.260> and<05:03:04.560> we 05:03:04.910 --> 05:03:04.920 align:start position:0% the specific ports and not only and we 05:03:04.920 --> 05:03:08.150 align:start position:0% the specific ports and not only and we looked<05:03:05.218> not<05:03:05.400> only<05:03:05.520> at<05:03:05.760> the<05:03:05.878> protocol 05:03:08.150 --> 05:03:08.160 align:start position:0% looked not only at the protocol 05:03:08.160 --> 05:03:11.628 align:start position:0% looked not only at the protocol and<05:03:08.520> their<05:03:08.700> protocols<05:03:09.298> including<05:03:10.080> FTP<05:03:10.740> or<05:03:11.340> the 05:03:11.628 --> 05:03:11.638 align:start position:0% and their protocols including FTP or the 05:03:11.638 --> 05:03:15.708 align:start position:0% and their protocols including FTP or the file<05:03:12.440> transfer<05:03:13.440> protocol 05:03:15.708 --> 05:03:15.718 align:start position:0% file transfer protocol 05:03:15.718 --> 05:03:19.310 align:start position:0% file transfer protocol ntp<05:03:16.620> or<05:03:17.340> the<05:03:17.638> network 05:03:19.310 --> 05:03:19.320 align:start position:0% ntp or the network 05:03:19.320 --> 05:03:22.208 align:start position:0% ntp or the network time<05:03:19.980> protocol 05:03:22.208 --> 05:03:22.218 align:start position:0% time protocol 05:03:22.218 --> 05:03:27.650 align:start position:0% time protocol SMTP<05:03:23.218> or<05:03:23.940> the<05:03:24.298> simple<05:03:25.138> mail 05:03:27.650 --> 05:03:27.660 align:start position:0% SMTP or the simple mail 05:03:27.660 --> 05:03:29.868 align:start position:0% SMTP or the simple mail transfer 05:03:29.868 --> 05:03:29.878 align:start position:0% transfer 05:03:29.878 --> 05:03:31.610 align:start position:0% transfer protocol 05:03:31.610 --> 05:03:31.620 align:start position:0% protocol 05:03:31.620 --> 05:03:34.250 align:start position:0% protocol POP3<05:03:32.458> or<05:03:33.298> the 05:03:34.250 --> 05:03:34.260 align:start position:0% POP3 or the 05:03:34.260 --> 05:03:36.170 align:start position:0% POP3 or the post 05:03:36.170 --> 05:03:36.180 align:start position:0% post 05:03:36.180 --> 05:03:38.990 align:start position:0% post office<05:03:36.660> protocol 05:03:38.990 --> 05:03:39.000 align:start position:0% office protocol 05:03:39.000 --> 05:03:40.850 align:start position:0% office protocol we<05:03:39.420> also<05:03:39.660> looked<05:03:39.958> at 05:03:40.850 --> 05:03:40.860 align:start position:0% we also looked at 05:03:40.860 --> 05:03:46.128 align:start position:0% we also looked at IMAP<05:03:41.600> the<05:03:42.600> internet 05:03:46.128 --> 05:03:46.138 align:start position:0% 05:03:46.138 --> 05:03:49.970 align:start position:0% message<05:03:46.798> access<05:03:47.580> protocol<05:03:48.298> and<05:03:49.138> again<05:03:49.320> all 05:03:49.970 --> 05:03:49.980 align:start position:0% message access protocol and again all 05:03:49.980 --> 05:03:51.770 align:start position:0% message access protocol and again all three<05:03:50.218> of<05:03:50.458> these 05:03:51.770 --> 05:03:51.780 align:start position:0% three of these 05:03:51.780 --> 05:03:54.050 align:start position:0% three of these have<05:03:52.320> to<05:03:52.440> do<05:03:52.560> with<05:03:52.740> email 05:03:54.050 --> 05:03:54.060 align:start position:0% have to do with email 05:03:54.060 --> 05:03:57.948 align:start position:0% have to do with email we<05:03:54.600> also<05:03:54.780> looked<05:03:55.080> at<05:03:55.138> an<05:03:56.040> ntp<05:03:56.580> which<05:03:57.298> is<05:03:57.540> not 05:03:57.948 --> 05:03:57.958 align:start position:0% we also looked at an ntp which is not 05:03:57.958 --> 05:04:00.970 align:start position:0% we also looked at an ntp which is not Network<05:03:58.260> time<05:03:58.620> protocol<05:03:59.100> but<05:04:00.000> the<05:04:00.480> network 05:04:00.970 --> 05:04:00.980 align:start position:0% Network time protocol but the network 05:04:00.980 --> 05:04:05.330 align:start position:0% Network time protocol but the network news<05:04:01.980> transfer 05:04:05.330 --> 05:04:05.340 align:start position:0% 05:04:05.340 --> 05:04:06.830 align:start position:0% protocol 05:04:06.830 --> 05:04:06.840 align:start position:0% protocol 05:04:06.840 --> 05:04:08.390 align:start position:0% protocol we<05:04:07.200> looked<05:04:07.440> at<05:04:07.500> two<05:04:07.680> different<05:04:07.860> versions<05:04:08.160> of 05:04:08.390 --> 05:04:08.400 align:start position:0% we looked at two different versions of 05:04:08.400 --> 05:04:11.810 align:start position:0% we looked at two different versions of HTTP<05:04:09.000> one<05:04:09.840> that<05:04:10.020> is<05:04:10.200> secure<05:04:10.620> these<05:04:11.280> allow<05:04:11.580> for 05:04:11.810 --> 05:04:11.820 align:start position:0% HTTP one that is secure these allow for 05:04:11.820 --> 05:04:14.570 align:start position:0% HTTP one that is secure these allow for browsing 05:04:14.570 --> 05:04:14.580 align:start position:0% browsing 05:04:14.580 --> 05:04:16.690 align:start position:0% browsing and<05:04:15.000> it<05:04:15.120> stands<05:04:15.420> for<05:04:15.540> the<05:04:15.840> hyper<05:04:16.320> text 05:04:16.690 --> 05:04:16.700 align:start position:0% and it stands for the hyper text 05:04:16.700 --> 05:04:19.430 align:start position:0% and it stands for the hyper text transfer<05:04:17.700> protocol 05:04:19.430 --> 05:04:19.440 align:start position:0% transfer protocol 05:04:19.440 --> 05:04:22.490 align:start position:0% transfer protocol which<05:04:19.860> if<05:04:20.040> you<05:04:20.218> know<05:04:20.400> HTML<05:04:21.360> or<05:04:21.660> the<05:04:21.900> hypertext 05:04:22.490 --> 05:04:22.500 align:start position:0% which if you know HTML or the hypertext 05:04:22.500 --> 05:04:25.128 align:start position:0% which if you know HTML or the hypertext markup<05:04:23.340> language<05:04:23.878> then<05:04:24.600> that<05:04:24.840> might<05:04:24.958> be 05:04:25.128 --> 05:04:25.138 align:start position:0% markup language then that might be 05:04:25.138 --> 05:04:27.288 align:start position:0% markup language then that might be familiar<05:04:25.500> to<05:04:25.680> you<05:04:25.860> and<05:04:26.580> finally<05:04:26.820> looked<05:04:27.180> at 05:04:27.288 --> 05:04:27.298 align:start position:0% familiar to you and finally looked at 05:04:27.298 --> 05:04:31.670 align:start position:0% familiar to you and finally looked at RDP<05:04:27.780> or<05:04:28.138> the<05:04:28.440> remote<05:04:28.920> desktop<05:04:29.820> protocol 05:04:31.670 --> 05:04:31.680 align:start position:0% RDP or the remote desktop protocol 05:04:31.680 --> 05:04:34.128 align:start position:0% RDP or the remote desktop protocol I<05:04:32.218> know<05:04:32.340> this<05:04:32.520> seems<05:04:32.820> like<05:04:32.940> a<05:04:33.120> lot<05:04:33.298> but<05:04:33.900> I 05:04:34.128 --> 05:04:34.138 align:start position:0% I know this seems like a lot but I 05:04:34.138 --> 05:04:36.288 align:start position:0% I know this seems like a lot but I guarantee<05:04:34.560> memorizing<05:04:35.280> all<05:04:35.520> of<05:04:35.638> these<05:04:35.940> and 05:04:36.288 --> 05:04:36.298 align:start position:0% guarantee memorizing all of these and 05:04:36.298 --> 05:04:37.490 align:start position:0% guarantee memorizing all of these and all<05:04:36.420> of<05:04:36.540> the<05:04:36.718> numbers<05:04:36.900> that<05:04:37.320> they're 05:04:37.490 --> 05:04:37.500 align:start position:0% all of the numbers that they're 05:04:37.500 --> 05:04:40.250 align:start position:0% all of the numbers that they're associated<05:04:37.980> with<05:04:38.280> is<05:04:38.820> gonna<05:04:39.000> help<05:04:39.420> you<05:04:39.780> so 05:04:40.250 --> 05:04:40.260 align:start position:0% associated with is gonna help you so 05:04:40.260 --> 05:04:44.920 align:start position:0% associated with is gonna help you so much<05:04:40.560> on<05:04:40.980> the<05:04:41.160> exam 05:04:44.920 --> 05:04:44.930 align:start position:0% 05:04:44.930 --> 05:05:04.868 align:start position:0% [Music] 05:05:04.868 --> 05:05:04.878 align:start position:0% 05:05:04.878 --> 05:05:08.708 align:start position:0% Network<05:05:05.878> protocols<05:05:06.718> and<05:05:07.080> services 05:05:08.708 --> 05:05:08.718 align:start position:0% Network protocols and services 05:05:08.718 --> 05:05:11.750 align:start position:0% Network protocols and services interoperability<05:05:09.718> services 05:05:11.750 --> 05:05:11.760 align:start position:0% interoperability services 05:05:11.760 --> 05:05:14.208 align:start position:0% interoperability services this<05:05:12.360> word<05:05:12.620> interoperability<05:05:13.620> is<05:05:13.920> a<05:05:14.100> really 05:05:14.208 --> 05:05:14.218 align:start position:0% this word interoperability is a really 05:05:14.218 --> 05:05:15.788 align:start position:0% this word interoperability is a really long<05:05:14.458> one<05:05:14.638> but<05:05:14.820> it's<05:05:15.000> also<05:05:15.180> a<05:05:15.360> good<05:05:15.480> one 05:05:15.788 --> 05:05:15.798 align:start position:0% long one but it's also a good one 05:05:15.798 --> 05:05:18.830 align:start position:0% long one but it's also a good one basically<05:05:16.798> what<05:05:17.100> this<05:05:17.340> means<05:05:17.700> is<05:05:18.360> how 05:05:18.830 --> 05:05:18.840 align:start position:0% basically what this means is how 05:05:18.840 --> 05:05:21.470 align:start position:0% basically what this means is how different<05:05:19.260> types<05:05:20.218> of<05:05:20.458> operating<05:05:20.878> systems<05:05:21.298> and 05:05:21.470 --> 05:05:21.480 align:start position:0% different types of operating systems and 05:05:21.480 --> 05:05:23.628 align:start position:0% different types of operating systems and computers<05:05:21.900> can<05:05:22.440> communicate<05:05:22.980> with<05:05:23.400> one 05:05:23.628 --> 05:05:23.638 align:start position:0% computers can communicate with one 05:05:23.638 --> 05:05:26.628 align:start position:0% computers can communicate with one another<05:05:23.820> over<05:05:24.718> a<05:05:25.378> similar<05:05:25.680> Network<05:05:25.920> and 05:05:26.628 --> 05:05:26.638 align:start position:0% another over a similar Network and 05:05:26.638 --> 05:05:27.830 align:start position:0% another over a similar Network and that's<05:05:26.700> what<05:05:26.878> we're<05:05:27.000> going<05:05:27.180> to<05:05:27.240> be<05:05:27.360> discussing 05:05:27.830 --> 05:05:27.840 align:start position:0% that's what we're going to be discussing 05:05:27.840 --> 05:05:29.868 align:start position:0% that's what we're going to be discussing in<05:05:28.378> this<05:05:28.620> module 05:05:29.868 --> 05:05:29.878 align:start position:0% in this module 05:05:29.878 --> 05:05:32.690 align:start position:0% in this module so<05:05:30.360> we're<05:05:30.540> going<05:05:30.718> to<05:05:30.840> first<05:05:31.020> cover<05:05:31.700> what 05:05:32.690 --> 05:05:32.700 align:start position:0% so we're going to first cover what 05:05:32.700 --> 05:05:34.788 align:start position:0% so we're going to first cover what interoperability<05:05:33.660> services<05:05:34.020> are<05:05:34.440> in<05:05:34.620> a 05:05:34.788 --> 05:05:34.798 align:start position:0% interoperability services are in a 05:05:34.798 --> 05:05:36.590 align:start position:0% interoperability services are in a little<05:05:34.860> more<05:05:35.040> depth<05:05:35.458> then<05:05:36.120> we're<05:05:36.298> going<05:05:36.480> to 05:05:36.590 --> 05:05:36.600 align:start position:0% little more depth then we're going to 05:05:36.600 --> 05:05:39.288 align:start position:0% little more depth then we're going to Define<05:05:36.718> some<05:05:37.260> specific<05:05:37.680> services<05:05:38.400> that 05:05:39.288 --> 05:05:39.298 align:start position:0% Define some specific services that 05:05:39.298 --> 05:05:43.310 align:start position:0% Define some specific services that qualify<05:05:39.840> as<05:05:39.958> these<05:05:40.320> particularly<05:05:41.420> NFS<05:05:42.420> or<05:05:42.958> the 05:05:43.310 --> 05:05:43.320 align:start position:0% qualify as these particularly NFS or the 05:05:43.320 --> 05:05:45.190 align:start position:0% qualify as these particularly NFS or the network 05:05:45.190 --> 05:05:45.200 align:start position:0% network 05:05:45.200 --> 05:05:48.050 align:start position:0% network file<05:05:46.200> system<05:05:46.740> I'm<05:05:47.458> sure<05:05:47.638> you<05:05:47.760> can<05:05:47.940> imagine 05:05:48.050 --> 05:05:48.060 align:start position:0% file system I'm sure you can imagine 05:05:48.060 --> 05:05:50.690 align:start position:0% file system I'm sure you can imagine what<05:05:48.480> that<05:05:48.600> is<05:05:48.780> from<05:05:49.080> its<05:05:49.440> name<05:05:49.560> we're<05:05:50.400> also 05:05:50.690 --> 05:05:50.700 align:start position:0% what that is from its name we're also 05:05:50.700 --> 05:05:53.510 align:start position:0% what that is from its name we're also going<05:05:50.760> to<05:05:50.820> look<05:05:50.940> at<05:05:51.120> SSH<05:05:51.660> which<05:05:52.200> is<05:05:52.320> the<05:05:52.740> secure 05:05:53.510 --> 05:05:53.520 align:start position:0% going to look at SSH which is the secure 05:05:53.520 --> 05:05:54.770 align:start position:0% going to look at SSH which is the secure shell 05:05:54.770 --> 05:05:54.780 align:start position:0% shell 05:05:54.780 --> 05:05:58.670 align:start position:0% shell and<05:05:55.700> SCP<05:05:56.700> secure 05:05:58.670 --> 05:05:58.680 align:start position:0% and SCP secure 05:05:58.680 --> 05:06:01.788 align:start position:0% and SCP secure copy<05:05:59.520> protocol<05:06:00.060> remember<05:06:00.780> every<05:06:01.200> time<05:06:01.378> we<05:06:01.620> see 05:06:01.788 --> 05:06:01.798 align:start position:0% copy protocol remember every time we see 05:06:01.798 --> 05:06:05.150 align:start position:0% copy protocol remember every time we see that<05:06:01.980> s<05:06:02.280> we<05:06:02.820> want<05:06:03.120> to<05:06:03.298> think<05:06:03.620> uh<05:06:04.620> secure 05:06:05.150 --> 05:06:05.160 align:start position:0% that s we want to think uh secure 05:06:05.160 --> 05:06:07.128 align:start position:0% that s we want to think uh secure security<05:06:05.580> that's<05:06:06.000> a<05:06:06.240> great<05:06:06.360> tip<05:06:06.718> that'll<05:06:07.020> help 05:06:07.128 --> 05:06:07.138 align:start position:0% security that's a great tip that'll help 05:06:07.138 --> 05:06:09.110 align:start position:0% security that's a great tip that'll help you<05:06:07.260> out<05:06:07.378> on<05:06:07.560> the<05:06:07.680> test<05:06:07.860> by<05:06:08.458> the<05:06:08.580> way<05:06:08.638> secure 05:06:09.110 --> 05:06:09.120 align:start position:0% you out on the test by the way secure 05:06:09.120 --> 05:06:12.590 align:start position:0% you out on the test by the way secure copy<05:06:09.540> protocols<05:06:10.080> similar<05:06:10.560> to<05:06:11.100> SFTP<05:06:12.060> or<05:06:12.298> the 05:06:12.590 --> 05:06:12.600 align:start position:0% copy protocols similar to SFTP or the 05:06:12.600 --> 05:06:15.410 align:start position:0% copy protocols similar to SFTP or the secure<05:06:12.958> file<05:06:13.620> transfer<05:06:14.100> protocol 05:06:15.410 --> 05:06:15.420 align:start position:0% secure file transfer protocol 05:06:15.420 --> 05:06:17.448 align:start position:0% secure file transfer protocol we're<05:06:15.840> then<05:06:16.020> going<05:06:16.200> to<05:06:16.260> look<05:06:16.440> at<05:06:16.620> telnet<05:06:17.218> or 05:06:17.448 --> 05:06:17.458 align:start position:0% we're then going to look at telnet or 05:06:17.458 --> 05:06:20.330 align:start position:0% we're then going to look at telnet or the<05:06:17.580> Telecommunications<05:06:18.420> Network<05:06:18.780> and<05:06:19.740> SMB 05:06:20.330 --> 05:06:20.340 align:start position:0% the Telecommunications Network and SMB 05:06:20.340 --> 05:06:27.830 align:start position:0% the Telecommunications Network and SMB or<05:06:21.060> the<05:06:21.420> server<05:06:22.458> messenger<05:06:23.458> block 05:06:27.830 --> 05:06:27.840 align:start position:0% 05:06:27.840 --> 05:06:30.530 align:start position:0% which<05:06:28.378> is<05:06:28.500> what<05:06:28.680> allows<05:06:29.040> us<05:06:29.218> to<05:06:29.638> share<05:06:30.120> for 05:06:30.530 --> 05:06:30.540 align:start position:0% which is what allows us to share for 05:06:30.540 --> 05:06:32.990 align:start position:0% which is what allows us to share for instance<05:06:30.780> files<05:06:31.440> and<05:06:31.980> printers 05:06:32.990 --> 05:06:33.000 align:start position:0% instance files and printers 05:06:33.000 --> 05:06:35.330 align:start position:0% instance files and printers we're<05:06:33.360> also<05:06:33.600> going<05:06:33.660> to<05:06:33.780> look<05:06:33.900> at<05:06:34.080> ldap<05:06:34.740> or 05:06:35.330 --> 05:06:35.340 align:start position:0% we're also going to look at ldap or 05:06:35.340 --> 05:06:37.550 align:start position:0% we're also going to look at ldap or lightweight<05:06:35.940> directory<05:06:36.660> access<05:06:36.900> protocol 05:06:37.550 --> 05:06:37.560 align:start position:0% lightweight directory access protocol 05:06:37.560 --> 05:06:40.250 align:start position:0% lightweight directory access protocol and<05:06:38.218> that<05:06:38.400> word<05:06:38.638> directory<05:06:39.540> is<05:06:39.660> important<05:06:40.020> as 05:06:40.250 --> 05:06:40.260 align:start position:0% and that word directory is important as 05:06:40.260 --> 05:06:43.250 align:start position:0% and that word directory is important as it<05:06:40.378> allows<05:06:40.680> us<05:06:40.798> to<05:06:41.218> manage<05:06:42.000> users<05:06:42.718> in<05:06:43.138> our 05:06:43.250 --> 05:06:43.260 align:start position:0% it allows us to manage users in our 05:06:43.260 --> 05:06:44.448 align:start position:0% it allows us to manage users in our Network 05:06:44.448 --> 05:06:44.458 align:start position:0% Network 05:06:44.458 --> 05:06:48.350 align:start position:0% Network mm<05:06:45.360> zero<05:06:46.020> conf<05:06:46.260> in<05:06:46.680> networking<05:06:47.280> which<05:06:47.940> also 05:06:48.350 --> 05:06:48.360 align:start position:0% mm zero conf in networking which also 05:06:48.360 --> 05:06:50.810 align:start position:0% mm zero conf in networking which also stands<05:06:48.718> for<05:06:48.840> zero<05:06:49.440> configuration<05:06:50.100> networking 05:06:50.810 --> 05:06:50.820 align:start position:0% stands for zero configuration networking 05:06:50.820 --> 05:06:53.628 align:start position:0% stands for zero configuration networking a<05:06:51.660> set<05:06:51.958> of<05:06:52.138> protocols<05:06:52.798> that<05:06:53.040> allows<05:06:53.280> us<05:06:53.400> to 05:06:53.628 --> 05:06:53.638 align:start position:0% a set of protocols that allows us to 05:06:53.638 --> 05:06:56.750 align:start position:0% a set of protocols that allows us to sort<05:06:53.878> of<05:06:54.000> plug<05:06:54.240> in<05:06:54.480> and<05:06:55.138> go 05:06:56.750 --> 05:06:56.760 align:start position:0% sort of plug in and go 05:06:56.760 --> 05:06:58.970 align:start position:0% sort of plug in and go without<05:06:57.298> having<05:06:57.660> to<05:06:57.780> do<05:06:57.900> a<05:06:58.080> lot<05:06:58.200> of<05:06:58.378> advanced 05:06:58.970 --> 05:06:58.980 align:start position:0% without having to do a lot of advanced 05:06:58.980 --> 05:07:01.310 align:start position:0% without having to do a lot of advanced configuration<05:06:59.760> and<05:07:00.000> setup<05:07:00.360> this<05:07:00.958> is<05:07:01.138> what 05:07:01.310 --> 05:07:01.320 align:start position:0% configuration and setup this is what 05:07:01.320 --> 05:07:04.010 align:start position:0% configuration and setup this is what allows<05:07:01.740> us<05:07:01.920> to<05:07:02.280> have<05:07:02.520> very<05:07:02.940> easy<05:07:03.298> Plug<05:07:03.840> and 05:07:04.010 --> 05:07:04.020 align:start position:0% allows us to have very easy Plug and 05:07:04.020 --> 05:07:07.010 align:start position:0% allows us to have very easy Plug and Play<05:07:04.320> network<05:07:05.100> devices<05:07:05.700> such<05:07:06.120> as<05:07:06.240> our<05:07:06.540> Soho 05:07:07.010 --> 05:07:07.020 align:start position:0% Play network devices such as our Soho 05:07:07.020 --> 05:07:08.810 align:start position:0% Play network devices such as our Soho routers<05:07:07.560> which<05:07:08.040> is<05:07:08.160> a<05:07:08.280> good<05:07:08.340> way<05:07:08.520> to<05:07:08.700> think 05:07:08.810 --> 05:07:08.820 align:start position:0% routers which is a good way to think 05:07:08.820 --> 05:07:10.970 align:start position:0% routers which is a good way to think about<05:07:09.000> it<05:07:09.240> however<05:07:09.900> it's<05:07:10.200> also<05:07:10.440> deployed<05:07:10.798> in 05:07:10.970 --> 05:07:10.980 align:start position:0% about it however it's also deployed in 05:07:10.980 --> 05:07:13.250 align:start position:0% about it however it's also deployed in much<05:07:11.160> larger<05:07:11.580> operations<05:07:12.060> in<05:07:12.660> order<05:07:12.780> to<05:07:12.958> ease 05:07:13.250 --> 05:07:13.260 align:start position:0% much larger operations in order to ease 05:07:13.260 --> 05:07:15.350 align:start position:0% much larger operations in order to ease the<05:07:13.440> burden<05:07:13.740> on<05:07:14.218> administrators<05:07:14.940> and 05:07:15.350 --> 05:07:15.360 align:start position:0% the burden on administrators and 05:07:15.360 --> 05:07:17.930 align:start position:0% the burden on administrators and technicians 05:07:17.930 --> 05:07:17.940 align:start position:0% technicians 05:07:17.940 --> 05:07:20.990 align:start position:0% technicians so<05:07:18.540> in<05:07:19.080> the<05:07:19.200> previous<05:07:19.378> module<05:07:20.100> we<05:07:20.520> discussed 05:07:20.990 --> 05:07:21.000 align:start position:0% so in the previous module we discussed 05:07:21.000 --> 05:07:23.510 align:start position:0% so in the previous module we discussed several<05:07:21.540> different<05:07:21.798> protocols<05:07:22.798> that<05:07:23.340> were 05:07:23.510 --> 05:07:23.520 align:start position:0% several different protocols that were 05:07:23.520 --> 05:07:28.310 align:start position:0% several different protocols that were used<05:07:23.820> in<05:07:24.480> the<05:07:24.660> tcpip<05:07:25.700> protocol<05:07:26.700> suite<05:07:27.360> and 05:07:28.310 --> 05:07:28.320 align:start position:0% used in the tcpip protocol suite and 05:07:28.320 --> 05:07:30.350 align:start position:0% used in the tcpip protocol suite and these<05:07:28.920> allowed<05:07:29.280> us<05:07:29.400> to<05:07:29.580> do<05:07:29.820> a<05:07:30.060> lot<05:07:30.180> of 05:07:30.350 --> 05:07:30.360 align:start position:0% these allowed us to do a lot of 05:07:30.360 --> 05:07:33.470 align:start position:0% these allowed us to do a lot of different<05:07:30.480> things<05:07:30.780> by<05:07:31.378> the<05:07:31.500> way<05:07:31.700> tcpip<05:07:32.700> which 05:07:33.470 --> 05:07:33.480 align:start position:0% different things by the way tcpip which 05:07:33.480 --> 05:07:35.690 align:start position:0% different things by the way tcpip which is<05:07:33.600> what<05:07:33.958> basically<05:07:34.440> allows<05:07:34.980> us<05:07:35.160> to 05:07:35.690 --> 05:07:35.700 align:start position:0% is what basically allows us to 05:07:35.700 --> 05:07:37.850 align:start position:0% is what basically allows us to communicate<05:07:36.600> over<05:07:36.840> the<05:07:37.080> network<05:07:37.260> in<05:07:37.680> general 05:07:37.850 --> 05:07:37.860 align:start position:0% communicate over the network in general 05:07:37.860 --> 05:07:40.490 align:start position:0% communicate over the network in general is<05:07:38.400> going<05:07:38.638> to<05:07:38.820> be<05:07:38.940> discussed<05:07:39.480> in<05:07:39.718> more<05:07:39.958> detail 05:07:40.490 --> 05:07:40.500 align:start position:0% is going to be discussed in more detail 05:07:40.500 --> 05:07:43.128 align:start position:0% is going to be discussed in more detail in<05:07:40.740> depth<05:07:41.100> later<05:07:41.458> on<05:07:41.638> in<05:07:41.878> this<05:07:42.060> course 05:07:43.128 --> 05:07:43.138 align:start position:0% in depth later on in this course 05:07:43.138 --> 05:07:46.190 align:start position:0% in depth later on in this course now<05:07:43.920> because<05:07:44.218> not<05:07:44.638> all<05:07:44.878> computers<05:07:45.420> are<05:07:45.958> made 05:07:46.190 --> 05:07:46.200 align:start position:0% now because not all computers are made 05:07:46.200 --> 05:07:48.830 align:start position:0% now because not all computers are made the<05:07:46.440> same<05:07:46.560> or<05:07:47.400> by<05:07:47.700> the<05:07:48.000> same<05:07:48.180> people<05:07:48.540> or 05:07:48.830 --> 05:07:48.840 align:start position:0% the same or by the same people or 05:07:48.840 --> 05:07:52.128 align:start position:0% the same or by the same people or individuals<05:07:49.580> certain<05:07:50.580> protocols<05:07:51.480> and 05:07:52.128 --> 05:07:52.138 align:start position:0% individuals certain protocols and 05:07:52.138 --> 05:07:54.970 align:start position:0% individuals certain protocols and services<05:07:52.798> need<05:07:53.458> to<05:07:53.580> be<05:07:53.700> in<05:07:53.878> place<05:07:54.120> to<05:07:54.540> allow 05:07:54.970 --> 05:07:54.980 align:start position:0% services need to be in place to allow 05:07:54.980 --> 05:07:58.910 align:start position:0% services need to be in place to allow dissimilar<05:07:55.980> systems<05:07:56.458> such<05:07:57.000> as<05:07:57.240> PCS<05:07:58.138> and<05:07:58.440> Macs 05:07:58.910 --> 05:07:58.920 align:start position:0% dissimilar systems such as PCS and Macs 05:07:58.920 --> 05:08:01.448 align:start position:0% dissimilar systems such as PCS and Macs to<05:07:59.638> be<05:07:59.760> able<05:08:00.000> to<05:08:00.360> interact<05:08:00.780> with<05:08:01.080> one<05:08:01.260> another 05:08:01.448 --> 05:08:01.458 align:start position:0% to be able to interact with one another 05:08:01.458 --> 05:08:05.530 align:start position:0% to be able to interact with one another so<05:08:02.660> tcpip<05:08:03.660> also<05:08:04.500> contains<05:08:04.980> these 05:08:05.530 --> 05:08:05.540 align:start position:0% so tcpip also contains these 05:08:05.540 --> 05:08:08.410 align:start position:0% so tcpip also contains these interoperability<05:08:06.540> services<05:08:07.080> that<05:08:07.920> allow 05:08:08.410 --> 05:08:08.420 align:start position:0% interoperability services that allow 05:08:08.420 --> 05:08:12.110 align:start position:0% interoperability services that allow dissimilar<05:08:09.420> services<05:08:09.780> or<05:08:10.740> systems<05:08:11.280> to<05:08:11.820> share 05:08:12.110 --> 05:08:12.120 align:start position:0% dissimilar services or systems to share 05:08:12.120 --> 05:08:14.990 align:start position:0% dissimilar services or systems to share resources<05:08:12.900> and<05:08:13.620> communicate<05:08:14.160> efficiently 05:08:14.990 --> 05:08:15.000 align:start position:0% resources and communicate efficiently 05:08:15.000 --> 05:08:17.990 align:start position:0% resources and communicate efficiently and<05:08:15.900> securely<05:08:16.500> which<05:08:17.100> is<05:08:17.280> important<05:08:17.638> if<05:08:17.878> I 05:08:17.990 --> 05:08:18.000 align:start position:0% and securely which is important if I 05:08:18.000 --> 05:08:20.510 align:start position:0% and securely which is important if I want<05:08:18.120> to<05:08:18.240> make<05:08:18.480> sure<05:08:18.660> that<05:08:18.958> no<05:08:19.260> one<05:08:19.440> is<05:08:20.040> reading 05:08:20.510 --> 05:08:20.520 align:start position:0% want to make sure that no one is reading 05:08:20.520 --> 05:08:22.070 align:start position:0% want to make sure that no one is reading all<05:08:20.760> of<05:08:20.878> the<05:08:21.060> information<05:08:21.240> I'm<05:08:21.718> sending 05:08:22.070 --> 05:08:22.080 align:start position:0% all of the information I'm sending 05:08:22.080 --> 05:08:24.590 align:start position:0% all of the information I'm sending between<05:08:22.320> computers<05:08:23.040> so<05:08:23.700> these<05:08:24.000> Services<05:08:24.180> is 05:08:24.590 --> 05:08:24.600 align:start position:0% between computers so these Services is 05:08:24.600 --> 05:08:26.030 align:start position:0% between computers so these Services is what<05:08:24.780> we're<05:08:24.900> going<05:08:25.080> to<05:08:25.138> spend<05:08:25.500> the<05:08:25.740> rest<05:08:25.860> of 05:08:26.030 --> 05:08:26.040 align:start position:0% what we're going to spend the rest of 05:08:26.040 --> 05:08:27.890 align:start position:0% what we're going to spend the rest of this<05:08:26.160> module<05:08:26.580> discussing 05:08:27.890 --> 05:08:27.900 align:start position:0% this module discussing 05:08:27.900 --> 05:08:30.470 align:start position:0% this module discussing now<05:08:28.500> the<05:08:28.798> first<05:08:28.920> service<05:08:29.160> is<05:08:29.700> the<05:08:30.120> network 05:08:30.470 --> 05:08:30.480 align:start position:0% now the first service is the network 05:08:30.480 --> 05:08:32.390 align:start position:0% now the first service is the network file<05:08:31.260> system 05:08:32.390 --> 05:08:32.400 align:start position:0% file system 05:08:32.400 --> 05:08:35.750 align:start position:0% file system it's<05:08:32.878> an<05:08:33.120> application<05:08:33.660> that<05:08:34.378> allows<05:08:34.740> users<05:08:35.340> to 05:08:35.750 --> 05:08:35.760 align:start position:0% it's an application that allows users to 05:08:35.760 --> 05:08:40.310 align:start position:0% it's an application that allows users to remotely<05:08:36.298> access<05:08:36.860> resources<05:08:38.000> and<05:08:39.000> files<05:08:39.660> a 05:08:40.310 --> 05:08:40.320 align:start position:0% remotely access resources and files a 05:08:40.320 --> 05:08:43.250 align:start position:0% remotely access resources and files a resource<05:08:41.040> being<05:08:41.400> for<05:08:41.820> instance<05:08:42.180> a<05:08:42.780> printer 05:08:43.250 --> 05:08:43.260 align:start position:0% resource being for instance a printer 05:08:43.260 --> 05:08:46.788 align:start position:0% resource being for instance a printer and<05:08:43.798> a<05:08:43.980> file<05:08:44.280> being<05:08:44.760> like<05:08:45.060> a<05:08:45.298> Word<05:08:45.420> document<05:08:45.958> as 05:08:46.788 --> 05:08:46.798 align:start position:0% and a file being like a Word document as 05:08:46.798 --> 05:08:48.890 align:start position:0% and a file being like a Word document as though<05:08:46.980> they<05:08:47.280> were<05:08:47.458> located<05:08:47.820> on<05:08:48.540> a<05:08:48.718> local 05:08:48.890 --> 05:08:48.900 align:start position:0% though they were located on a local 05:08:48.900 --> 05:08:51.050 align:start position:0% though they were located on a local machine<05:08:49.320> even<05:08:50.100> though<05:08:50.340> they're<05:08:50.638> someplace 05:08:51.050 --> 05:08:51.060 align:start position:0% machine even though they're someplace 05:08:51.060 --> 05:08:52.010 align:start position:0% machine even though they're someplace else 05:08:52.010 --> 05:08:52.020 align:start position:0% else 05:08:52.020 --> 05:08:54.530 align:start position:0% else this<05:08:52.740> service<05:08:52.920> is<05:08:53.340> used<05:08:53.580> for<05:08:53.878> systems<05:08:54.298> that 05:08:54.530 --> 05:08:54.540 align:start position:0% this service is used for systems that 05:08:54.540 --> 05:08:57.948 align:start position:0% this service is used for systems that are<05:08:54.660> typically<05:08:55.020> not<05:08:55.740> the<05:08:56.040> same<05:08:56.160> such<05:08:56.940> as<05:08:57.180> Unix 05:08:57.948 --> 05:08:57.958 align:start position:0% are typically not the same such as Unix 05:08:57.958 --> 05:09:00.948 align:start position:0% are typically not the same such as Unix which<05:08:58.620> is<05:08:58.740> the<05:08:59.218> larger<05:08:59.940> version<05:09:00.180> or<05:09:00.660> the 05:09:00.948 --> 05:09:00.958 align:start position:0% which is the larger version or the 05:09:00.958 --> 05:09:04.128 align:start position:0% which is the larger version or the commercial<05:09:01.500> version<05:09:01.920> of<05:09:02.820> Linux<05:09:03.420> and 05:09:04.128 --> 05:09:04.138 align:start position:0% commercial version of Linux and 05:09:04.138 --> 05:09:07.750 align:start position:0% commercial version of Linux and Microsoft<05:09:04.680> systems<05:09:05.280> now<05:09:06.060> NFS<05:09:06.780> functions 05:09:07.750 --> 05:09:07.760 align:start position:0% Microsoft systems now NFS functions 05:09:07.760 --> 05:09:10.310 align:start position:0% Microsoft systems now NFS functions independently<05:09:08.760> of<05:09:09.360> the<05:09:09.600> operating<05:09:09.958> system 05:09:10.310 --> 05:09:10.320 align:start position:0% independently of the operating system 05:09:10.320 --> 05:09:13.070 align:start position:0% independently of the operating system the<05:09:11.100> computer<05:09:11.280> system<05:09:12.000> it's<05:09:12.420> installed<05:09:12.900> on 05:09:13.070 --> 05:09:13.080 align:start position:0% the computer system it's installed on 05:09:13.080 --> 05:09:16.490 align:start position:0% the computer system it's installed on and<05:09:13.798> the<05:09:14.100> network<05:09:14.280> architecture<05:09:15.180> this<05:09:16.080> means 05:09:16.490 --> 05:09:16.500 align:start position:0% and the network architecture this means 05:09:16.500 --> 05:09:18.708 align:start position:0% and the network architecture this means that<05:09:16.798> NFS<05:09:17.400> is<05:09:17.760> going<05:09:17.940> to<05:09:18.060> perform<05:09:18.180> its 05:09:18.708 --> 05:09:18.718 align:start position:0% that NFS is going to perform its 05:09:18.718 --> 05:09:20.510 align:start position:0% that NFS is going to perform its functions<05:09:19.080> regardless<05:09:19.740> of<05:09:20.040> where<05:09:20.280> it's 05:09:20.510 --> 05:09:20.520 align:start position:0% functions regardless of where it's 05:09:20.520 --> 05:09:23.628 align:start position:0% functions regardless of where it's installed<05:09:21.060> and<05:09:21.600> since<05:09:21.780> it's<05:09:21.958> what<05:09:22.200> we<05:09:22.378> call<05:09:22.638> an 05:09:23.628 --> 05:09:23.638 align:start position:0% installed and since it's what we call an 05:09:23.638 --> 05:09:26.150 align:start position:0% installed and since it's what we call an open<05:09:23.940> standard 05:09:26.150 --> 05:09:26.160 align:start position:0% open standard 05:09:26.160 --> 05:09:30.650 align:start position:0% open standard it<05:09:26.760> allows<05:09:27.240> anyone<05:09:27.840> to<05:09:28.200> implement<05:09:28.560> it 05:09:30.650 --> 05:09:30.660 align:start position:0% it allows anyone to implement it 05:09:30.660 --> 05:09:34.550 align:start position:0% it allows anyone to implement it it<05:09:31.200> also<05:09:31.560> listens<05:09:32.040> on<05:09:32.638> Port<05:09:32.878> 2049<05:09:33.840> by<05:09:34.200> default 05:09:34.550 --> 05:09:34.560 align:start position:0% it also listens on Port 2049 by default 05:09:34.560 --> 05:09:36.650 align:start position:0% it also listens on Port 2049 by default but<05:09:35.040> I<05:09:35.218> wouldn't<05:09:35.340> worry<05:09:35.700> about<05:09:35.940> memorizing 05:09:36.650 --> 05:09:36.660 align:start position:0% but I wouldn't worry about memorizing 05:09:36.660 --> 05:09:38.448 align:start position:0% but I wouldn't worry about memorizing that<05:09:36.900> for<05:09:37.138> the<05:09:37.320> test 05:09:38.448 --> 05:09:38.458 align:start position:0% that for the test 05:09:38.458 --> 05:09:43.070 align:start position:0% that for the test next<05:09:39.120> SSH<05:09:39.840> or<05:09:40.500> the<05:09:40.798> secure<05:09:41.700> shell<05:09:42.120> is<05:09:42.718> one<05:09:42.958> of 05:09:43.070 --> 05:09:43.080 align:start position:0% next SSH or the secure shell is one of 05:09:43.080 --> 05:09:45.770 align:start position:0% next SSH or the secure shell is one of the<05:09:43.378> preferred<05:09:43.920> session<05:09:44.878> initiating 05:09:45.770 --> 05:09:45.780 align:start position:0% the preferred session initiating 05:09:45.780 --> 05:09:49.368 align:start position:0% the preferred session initiating programs<05:09:46.560> that<05:09:47.160> allows<05:09:47.580> us<05:09:47.700> to<05:09:48.298> connect<05:09:48.480> to<05:09:49.260> a 05:09:49.368 --> 05:09:49.378 align:start position:0% programs that allows us to connect to a 05:09:49.378 --> 05:09:50.868 align:start position:0% programs that allows us to connect to a remote<05:09:49.560> computer 05:09:50.868 --> 05:09:50.878 align:start position:0% remote computer 05:09:50.878 --> 05:09:53.930 align:start position:0% remote computer it<05:09:51.420> creates<05:09:51.718> a<05:09:51.958> secure<05:09:52.378> Connection<05:09:52.740> by<05:09:53.520> using 05:09:53.930 --> 05:09:53.940 align:start position:0% it creates a secure Connection by using 05:09:53.940 --> 05:09:56.868 align:start position:0% it creates a secure Connection by using strong<05:09:54.360> authentication<05:09:55.320> mechanisms<05:09:56.160> and<05:09:56.700> it 05:09:56.868 --> 05:09:56.878 align:start position:0% strong authentication mechanisms and it 05:09:56.878 --> 05:09:59.510 align:start position:0% strong authentication mechanisms and it lets<05:09:57.240> users<05:09:57.718> log<05:09:58.138> on<05:09:58.378> to<05:09:58.560> remote<05:09:58.798> computers 05:09:59.510 --> 05:09:59.520 align:start position:0% lets users log on to remote computers 05:09:59.520 --> 05:10:02.208 align:start position:0% lets users log on to remote computers with<05:10:00.420> different<05:10:00.718> systems<05:10:01.378> independent<05:10:02.040> of 05:10:02.208 --> 05:10:02.218 align:start position:0% with different systems independent of 05:10:02.218 --> 05:10:04.430 align:start position:0% with different systems independent of the<05:10:02.400> type<05:10:02.580> of<05:10:02.760> system<05:10:02.940> you're<05:10:03.298> currently<05:10:03.660> on 05:10:04.430 --> 05:10:04.440 align:start position:0% the type of system you're currently on 05:10:04.440 --> 05:10:07.910 align:start position:0% the type of system you're currently on with<05:10:05.040> SSH<05:10:05.458> the<05:10:06.298> secure<05:10:06.600> shell<05:10:06.900> the<05:10:07.560> entire 05:10:07.910 --> 05:10:07.920 align:start position:0% with SSH the secure shell the entire 05:10:07.920 --> 05:10:10.850 align:start position:0% with SSH the secure shell the entire connection<05:10:08.280> is<05:10:09.000> encrypted<05:10:09.600> including<05:10:10.500> the 05:10:10.850 --> 05:10:10.860 align:start position:0% connection is encrypted including the 05:10:10.860 --> 05:10:13.550 align:start position:0% connection is encrypted including the password<05:10:11.060> and<05:10:12.060> the<05:10:12.298> login<05:10:12.420> session 05:10:13.550 --> 05:10:13.560 align:start position:0% password and the login session 05:10:13.560 --> 05:10:15.530 align:start position:0% password and the login session it's<05:10:14.100> all<05:10:14.340> compatible<05:10:14.820> with<05:10:15.180> a<05:10:15.360> lot<05:10:15.420> of 05:10:15.530 --> 05:10:15.540 align:start position:0% it's all compatible with a lot of 05:10:15.540 --> 05:10:18.770 align:start position:0% it's all compatible with a lot of different<05:10:15.718> systems<05:10:16.260> including<05:10:16.798> Linux<05:10:17.780> Macs 05:10:18.770 --> 05:10:18.780 align:start position:0% different systems including Linux Macs 05:10:18.780 --> 05:10:21.530 align:start position:0% different systems including Linux Macs and<05:10:19.020> PCs<05:10:19.680> and<05:10:19.920> so<05:10:20.040> on<05:10:20.280> now<05:10:21.000> there<05:10:21.240> are<05:10:21.420> actually 05:10:21.530 --> 05:10:21.540 align:start position:0% and PCs and so on now there are actually 05:10:21.540 --> 05:10:24.110 align:start position:0% and PCs and so on now there are actually two<05:10:22.320> different<05:10:22.560> versions<05:10:23.100> of<05:10:23.458> secure<05:10:23.878> show 05:10:24.110 --> 05:10:24.120 align:start position:0% two different versions of secure show 05:10:24.120 --> 05:10:26.930 align:start position:0% two different versions of secure show ssh1 05:10:26.930 --> 05:10:26.940 align:start position:0% ssh1 05:10:26.940 --> 05:10:31.490 align:start position:0% ssh1 and<05:10:27.480> ssh2 05:10:31.490 --> 05:10:31.500 align:start position:0% 05:10:31.500 --> 05:10:34.070 align:start position:0% these<05:10:32.160> two<05:10:32.280> versions<05:10:32.700> are<05:10:33.180> not<05:10:33.420> compatible 05:10:34.070 --> 05:10:34.080 align:start position:0% these two versions are not compatible 05:10:34.080 --> 05:10:36.830 align:start position:0% these two versions are not compatible with<05:10:34.680> one<05:10:34.920> another<05:10:35.100> which<05:10:36.000> is<05:10:36.180> important<05:10:36.600> to 05:10:36.830 --> 05:10:36.840 align:start position:0% with one another which is important to 05:10:36.840 --> 05:10:37.550 align:start position:0% with one another which is important to know 05:10:37.550 --> 05:10:37.560 align:start position:0% know 05:10:37.560 --> 05:10:39.948 align:start position:0% know because<05:10:37.980> they<05:10:38.400> each<05:10:38.638> encrypt<05:10:39.298> different 05:10:39.948 --> 05:10:39.958 align:start position:0% because they each encrypt different 05:10:39.958 --> 05:10:42.650 align:start position:0% because they each encrypt different parts<05:10:40.320> of<05:10:40.680> the<05:10:40.920> data<05:10:41.218> packet<05:10:41.580> and<05:10:42.180> they<05:10:42.420> employ 05:10:42.650 --> 05:10:42.660 align:start position:0% parts of the data packet and they employ 05:10:42.660 --> 05:10:45.170 align:start position:0% parts of the data packet and they employ different<05:10:43.320> types<05:10:43.980> of<05:10:44.218> encryption<05:10:44.700> methods 05:10:45.170 --> 05:10:45.180 align:start position:0% different types of encryption methods 05:10:45.180 --> 05:10:47.690 align:start position:0% different types of encryption methods which<05:10:45.600> we'll<05:10:45.780> talk<05:10:46.020> about<05:10:46.138> later<05:10:46.560> however<05:10:47.340> the 05:10:47.690 --> 05:10:47.700 align:start position:0% which we'll talk about later however the 05:10:47.700 --> 05:10:50.090 align:start position:0% which we'll talk about later however the most<05:10:47.878> important<05:10:48.298> thing<05:10:48.480> to<05:10:48.660> know<05:10:48.780> is<05:10:49.378> that<05:10:49.620> SSH 05:10:50.090 --> 05:10:50.100 align:start position:0% most important thing to know is that SSH 05:10:50.100 --> 05:10:55.430 align:start position:0% most important thing to know is that SSH 2<05:10:50.760> is<05:10:51.540> more<05:10:51.900> secure<05:10:52.378> than<05:10:53.240> ssh1<05:10:54.240> and<05:10:54.900> so<05:10:55.138> in 05:10:55.430 --> 05:10:55.440 align:start position:0% 2 is more secure than ssh1 and so in 05:10:55.440 --> 05:10:57.770 align:start position:0% 2 is more secure than ssh1 and so in most<05:10:55.620> cases<05:10:55.920> we<05:10:56.218> want<05:10:56.400> to<05:10:56.520> use<05:10:56.700> that<05:10:56.940> this<05:10:57.600> is 05:10:57.770 --> 05:10:57.780 align:start position:0% most cases we want to use that this is 05:10:57.780 --> 05:11:01.430 align:start position:0% most cases we want to use that this is because<05:10:58.080> it<05:10:58.980> does<05:10:59.160> not<05:10:59.400> use<05:10:59.760> server<05:11:00.298> Keys<05:11:00.660> ssh1 05:11:01.430 --> 05:11:01.440 align:start position:0% because it does not use server Keys ssh1 05:11:01.440 --> 05:11:05.270 align:start position:0% because it does not use server Keys ssh1 doesn't<05:11:01.798> which<05:11:02.458> are<05:11:02.878> keys<05:11:03.980> that<05:11:04.980> are 05:11:05.270 --> 05:11:05.280 align:start position:0% doesn't which are keys that are 05:11:05.280 --> 05:11:08.628 align:start position:0% doesn't which are keys that are temporary<05:11:05.940> and<05:11:06.540> protect<05:11:06.958> other<05:11:07.860> aspects<05:11:08.458> of 05:11:08.628 --> 05:11:08.638 align:start position:0% temporary and protect other aspects of 05:11:08.638 --> 05:11:10.610 align:start position:0% temporary and protect other aspects of the<05:11:08.820> encryption<05:11:09.240> process<05:11:09.718> it's<05:11:10.320> a<05:11:10.500> bit 05:11:10.610 --> 05:11:10.620 align:start position:0% the encryption process it's a bit 05:11:10.620 --> 05:11:13.310 align:start position:0% the encryption process it's a bit complex<05:11:10.980> and<05:11:11.280> over<05:11:11.520> the<05:11:11.760> course<05:11:11.940> of<05:11:12.180> and<05:11:13.080> over 05:11:13.310 --> 05:11:13.320 align:start position:0% complex and over the course of and over 05:11:13.320 --> 05:11:16.310 align:start position:0% complex and over the course of and over the<05:11:13.700> objectives<05:11:14.700> of<05:11:14.940> this<05:11:15.180> course<05:11:15.420> however 05:11:16.310 --> 05:11:16.320 align:start position:0% the objectives of this course however 05:11:16.320 --> 05:11:19.250 align:start position:0% the objectives of this course however SSH<05:11:16.860> 2<05:11:17.340> does<05:11:17.760> contain<05:11:18.240> another<05:11:18.660> protocol 05:11:19.250 --> 05:11:19.260 align:start position:0% SSH 2 does contain another protocol 05:11:19.260 --> 05:11:23.270 align:start position:0% SSH 2 does contain another protocol called<05:11:20.218> SFTP 05:11:23.270 --> 05:11:23.280 align:start position:0% 05:11:23.280 --> 05:11:27.288 align:start position:0% an<05:11:23.940> SFTP<05:11:24.600> or<05:11:25.080> the<05:11:25.378> secure<05:11:26.340> file<05:11:26.700> transfer 05:11:27.288 --> 05:11:27.298 align:start position:0% an SFTP or the secure file transfer 05:11:27.298 --> 05:11:28.730 align:start position:0% an SFTP or the secure file transfer protocol 05:11:28.730 --> 05:11:28.740 align:start position:0% protocol 05:11:28.740 --> 05:11:31.970 align:start position:0% protocol is<05:11:29.340> a<05:11:29.580> secure<05:11:29.940> replacement<05:11:30.240> for<05:11:31.080> the<05:11:31.378> unsecure 05:11:31.970 --> 05:11:31.980 align:start position:0% is a secure replacement for the unsecure 05:11:31.980 --> 05:11:35.390 align:start position:0% is a secure replacement for the unsecure version<05:11:32.280> of<05:11:32.878> plain<05:11:33.180> old<05:11:33.360> FTP<05:11:34.020> and<05:11:34.980> it<05:11:35.218> still 05:11:35.390 --> 05:11:35.400 align:start position:0% version of plain old FTP and it still 05:11:35.400 --> 05:11:39.770 align:start position:0% version of plain old FTP and it still uses<05:11:35.820> the<05:11:36.180> same<05:11:36.360> port<05:11:36.718> as<05:11:37.440> SSH<05:11:37.860> which<05:11:38.820> if<05:11:39.660> you 05:11:39.770 --> 05:11:39.780 align:start position:0% uses the same port as SSH which if you 05:11:39.780 --> 05:11:43.490 align:start position:0% uses the same port as SSH which if you recall<05:11:40.200> is<05:11:40.798> port<05:11:41.160> 22. 05:11:43.490 --> 05:11:43.500 align:start position:0% recall is port 22. 05:11:43.500 --> 05:11:46.128 align:start position:0% recall is port 22. so<05:11:44.100> it's<05:11:44.458> important<05:11:44.940> to<05:11:45.298> know<05:11:45.480> that<05:11:45.900> if<05:11:46.080> we're 05:11:46.128 --> 05:11:46.138 align:start position:0% so it's important to know that if we're 05:11:46.138 --> 05:11:49.788 align:start position:0% so it's important to know that if we're going<05:11:46.320> to<05:11:46.378> be<05:11:46.500> using<05:11:46.940> SFTP<05:11:47.940> remember<05:11:48.600> FTP<05:11:49.378> uses 05:11:49.788 --> 05:11:49.798 align:start position:0% going to be using SFTP remember FTP uses 05:11:49.798 --> 05:11:53.510 align:start position:0% going to be using SFTP remember FTP uses 20<05:11:50.160> and<05:11:50.878> 21<05:11:51.180> if<05:11:52.080> we're<05:11:52.200> using<05:11:52.560> SFTP<05:11:53.280> we're 05:11:53.510 --> 05:11:53.520 align:start position:0% 20 and 21 if we're using SFTP we're 05:11:53.520 --> 05:11:57.590 align:start position:0% 20 and 21 if we're using SFTP we're using<05:11:53.820> Port<05:11:54.060> 22.<05:11:54.958> now<05:11:55.320> similar<05:11:55.798> to<05:11:56.040> SFTP<05:11:56.940> is 05:11:57.590 --> 05:11:57.600 align:start position:0% using Port 22. now similar to SFTP is 05:11:57.600 --> 05:12:02.270 align:start position:0% using Port 22. now similar to SFTP is SCP<05:11:58.500> or<05:11:59.100> the<05:11:59.458> secure<05:12:00.240> copy<05:12:00.780> protocol<05:12:01.200> which<05:12:02.100> is 05:12:02.270 --> 05:12:02.280 align:start position:0% SCP or the secure copy protocol which is 05:12:02.280 --> 05:12:04.850 align:start position:0% SCP or the secure copy protocol which is a<05:12:02.580> secure<05:12:02.878> method<05:12:03.360> of<05:12:03.718> copying<05:12:04.200> files<05:12:04.560> between 05:12:04.850 --> 05:12:04.860 align:start position:0% a secure method of copying files between 05:12:04.860 --> 05:12:09.410 align:start position:0% a secure method of copying files between remote<05:12:05.218> devices<05:12:05.760> just<05:12:06.420> like<05:12:06.600> FTP<05:12:07.260> or<05:12:07.860> SFTP<05:12:08.580> it 05:12:09.410 --> 05:12:09.420 align:start position:0% remote devices just like FTP or SFTP it 05:12:09.420 --> 05:12:12.530 align:start position:0% remote devices just like FTP or SFTP it utilizes<05:12:09.958> the<05:12:10.260> same<05:12:10.378> Portis<05:12:10.920> SSH<05:12:11.400> just<05:12:12.298> like 05:12:12.530 --> 05:12:12.540 align:start position:0% utilizes the same Portis SSH just like 05:12:12.540 --> 05:12:15.288 align:start position:0% utilizes the same Portis SSH just like SFTP<05:12:13.320> and<05:12:13.980> it's<05:12:14.100> compatible<05:12:14.580> with<05:12:14.940> a<05:12:15.060> lot<05:12:15.180> of 05:12:15.288 --> 05:12:15.298 align:start position:0% SFTP and it's compatible with a lot of 05:12:15.298 --> 05:12:17.868 align:start position:0% SFTP and it's compatible with a lot of different<05:12:15.540> operating<05:12:16.080> systems<05:12:16.740> to<05:12:17.520> implement 05:12:17.868 --> 05:12:17.878 align:start position:0% different operating systems to implement 05:12:17.878 --> 05:12:21.170 align:start position:0% different operating systems to implement SCP<05:12:18.718> you<05:12:19.320> can<05:12:19.378> initiate<05:12:19.860> it<05:12:20.100> via<05:12:20.520> a<05:12:20.878> command 05:12:21.170 --> 05:12:21.180 align:start position:0% SCP you can initiate it via a command 05:12:21.180 --> 05:12:25.010 align:start position:0% SCP you can initiate it via a command line<05:12:21.360> utility<05:12:21.900> that<05:12:22.798> uses<05:12:23.218> either<05:12:23.760> SCP<05:12:24.718> or 05:12:25.010 --> 05:12:25.020 align:start position:0% line utility that uses either SCP or 05:12:25.020 --> 05:12:28.730 align:start position:0% line utility that uses either SCP or SFTP<05:12:25.798> to<05:12:26.340> perform<05:12:26.520> some<05:12:27.120> secure<05:12:27.480> copying<05:12:28.080> the 05:12:28.730 --> 05:12:28.740 align:start position:0% SFTP to perform some secure copying the 05:12:28.740 --> 05:12:30.350 align:start position:0% SFTP to perform some secure copying the important<05:12:29.100> thing<05:12:29.340> here<05:12:29.638> to<05:12:29.878> know<05:12:30.000> for<05:12:30.240> the 05:12:30.350 --> 05:12:30.360 align:start position:0% important thing here to know for the 05:12:30.360 --> 05:12:32.810 align:start position:0% important thing here to know for the network<05:12:30.480> plus<05:12:30.780> exam<05:12:31.260> is<05:12:31.920> not<05:12:32.160> when<05:12:32.458> you<05:12:32.638> would 05:12:32.810 --> 05:12:32.820 align:start position:0% network plus exam is not when you would 05:12:32.820 --> 05:12:36.230 align:start position:0% network plus exam is not when you would use<05:12:33.060> SCP<05:12:33.900> over<05:12:34.218> SFTP<05:12:35.218> which<05:12:35.700> is<05:12:35.820> a<05:12:36.000> little<05:12:36.120> bit 05:12:36.230 --> 05:12:36.240 align:start position:0% use SCP over SFTP which is a little bit 05:12:36.240 --> 05:12:39.350 align:start position:0% use SCP over SFTP which is a little bit more<05:12:36.540> complex<05:12:36.958> but<05:12:37.560> rather<05:12:37.860> to<05:12:38.100> realize<05:12:38.520> that 05:12:39.350 --> 05:12:39.360 align:start position:0% more complex but rather to realize that 05:12:39.360 --> 05:12:43.010 align:start position:0% more complex but rather to realize that SCP<05:12:40.260> is<05:12:40.620> a<05:12:40.860> secure<05:12:41.160> method<05:12:41.520> of<05:12:41.638> copying<05:12:42.120> as<05:12:42.780> is 05:12:43.010 --> 05:12:43.020 align:start position:0% SCP is a secure method of copying as is 05:12:43.020 --> 05:12:45.890 align:start position:0% SCP is a secure method of copying as is as<05:12:43.580> FTP<05:12:44.580> that's<05:12:45.240> how<05:12:45.420> you're<05:12:45.540> going<05:12:45.660> to<05:12:45.780> see 05:12:45.890 --> 05:12:45.900 align:start position:0% as FTP that's how you're going to see 05:12:45.900 --> 05:12:48.830 align:start position:0% as FTP that's how you're going to see this<05:12:46.138> pop<05:12:46.440> up<05:12:46.620> on<05:12:46.798> the<05:12:46.920> exam<05:12:47.700> now<05:12:48.240> in<05:12:48.480> contrast 05:12:48.830 --> 05:12:48.840 align:start position:0% this pop up on the exam now in contrast 05:12:48.840 --> 05:12:51.590 align:start position:0% this pop up on the exam now in contrast to<05:12:49.138> all<05:12:49.320> of<05:12:49.440> this<05:12:49.740> secure<05:12:50.280> Communications<05:12:50.878> I 05:12:51.590 --> 05:12:51.600 align:start position:0% to all of this secure Communications I 05:12:51.600 --> 05:12:53.868 align:start position:0% to all of this secure Communications I want<05:12:51.718> to<05:12:51.840> talk<05:12:52.020> about<05:12:52.218> telnet<05:12:53.218> or<05:12:53.638> the 05:12:53.868 --> 05:12:53.878 align:start position:0% want to talk about telnet or the 05:12:53.878 --> 05:12:56.750 align:start position:0% want to talk about telnet or the Telecommunications<05:12:54.660> Network<05:12:55.200> which<05:12:56.040> is<05:12:56.340> a 05:12:56.750 --> 05:12:56.760 align:start position:0% Telecommunications Network which is a 05:12:56.760 --> 05:12:59.750 align:start position:0% Telecommunications Network which is a terminal<05:12:57.120> emulations<05:12:58.080> protocol<05:12:58.740> what<05:12:59.580> this 05:12:59.750 --> 05:12:59.760 align:start position:0% terminal emulations protocol what this 05:12:59.760 --> 05:13:02.330 align:start position:0% terminal emulations protocol what this means<05:13:00.120> is<05:13:00.540> that<05:13:00.718> it's<05:13:00.958> only<05:13:01.200> simulating<05:13:01.980> a 05:13:02.330 --> 05:13:02.340 align:start position:0% means is that it's only simulating a 05:13:02.340 --> 05:13:04.490 align:start position:0% means is that it's only simulating a session<05:13:02.520> on<05:13:03.000> the<05:13:03.120> machine<05:13:03.360> it<05:13:04.080> is<05:13:04.200> being 05:13:04.490 --> 05:13:04.500 align:start position:0% session on the machine it is being 05:13:04.500 --> 05:13:06.770 align:start position:0% session on the machine it is being initiated<05:13:05.100> on<05:13:05.400> when<05:13:06.000> you<05:13:06.120> connect<05:13:06.298> to<05:13:06.600> a 05:13:06.770 --> 05:13:06.780 align:start position:0% initiated on when you connect to a 05:13:06.780 --> 05:13:10.310 align:start position:0% initiated on when you connect to a machine<05:13:06.958> via<05:13:07.920> a<05:13:08.280> terminal<05:13:08.580> by<05:13:09.298> using<05:13:09.660> telnet 05:13:10.310 --> 05:13:10.320 align:start position:0% machine via a terminal by using telnet 05:13:10.320 --> 05:13:12.288 align:start position:0% machine via a terminal by using telnet the<05:13:10.860> machine<05:13:10.980> is<05:13:11.280> translating<05:13:12.000> your 05:13:12.288 --> 05:13:12.298 align:start position:0% the machine is translating your 05:13:12.298 --> 05:13:14.810 align:start position:0% the machine is translating your keystrokes<05:13:12.958> into<05:13:13.200> instructions<05:13:14.100> that<05:13:14.580> the 05:13:14.810 --> 05:13:14.820 align:start position:0% keystrokes into instructions that the 05:13:14.820 --> 05:13:17.270 align:start position:0% keystrokes into instructions that the Remote<05:13:14.940> device<05:13:15.378> understands<05:13:16.378> and<05:13:17.040> it 05:13:17.270 --> 05:13:17.280 align:start position:0% Remote device understands and it 05:13:17.280 --> 05:13:20.208 align:start position:0% Remote device understands and it displays<05:13:18.000> those<05:13:18.298> instructions<05:13:19.040> and<05:13:20.040> the 05:13:20.208 --> 05:13:20.218 align:start position:0% displays those instructions and the 05:13:20.218 --> 05:13:22.970 align:start position:0% displays those instructions and the responses<05:13:20.700> back<05:13:21.000> to<05:13:21.180> you<05:13:21.360> in<05:13:21.900> a<05:13:22.080> graphical<05:13:22.500> or 05:13:22.970 --> 05:13:22.980 align:start position:0% responses back to you in a graphical or 05:13:22.980 --> 05:13:25.010 align:start position:0% responses back to you in a graphical or command<05:13:23.520> line<05:13:23.760> manner 05:13:25.010 --> 05:13:25.020 align:start position:0% command line manner 05:13:25.020 --> 05:13:28.070 align:start position:0% command line manner telnet<05:13:25.920> is<05:13:26.100> an<05:13:26.458> unsecure<05:13:27.120> protocol<05:13:27.540> which<05:13:27.958> is 05:13:28.070 --> 05:13:28.080 align:start position:0% telnet is an unsecure protocol which is 05:13:28.080 --> 05:13:30.050 align:start position:0% telnet is an unsecure protocol which is why<05:13:28.320> we<05:13:28.620> don't<05:13:28.860> use<05:13:29.040> it<05:13:29.160> as<05:13:29.340> much<05:13:29.458> as<05:13:29.638> SSH 05:13:30.050 --> 05:13:30.060 align:start position:0% why we don't use it as much as SSH 05:13:30.060 --> 05:13:32.628 align:start position:0% why we don't use it as much as SSH anymore<05:13:30.540> and<05:13:31.500> this<05:13:31.620> is<05:13:31.740> important<05:13:32.100> to<05:13:32.280> keep<05:13:32.458> in 05:13:32.628 --> 05:13:32.638 align:start position:0% anymore and this is important to keep in 05:13:32.638 --> 05:13:33.708 align:start position:0% anymore and this is important to keep in mind 05:13:33.708 --> 05:13:33.718 align:start position:0% mind 05:13:33.718 --> 05:13:35.868 align:start position:0% mind so<05:13:34.200> when<05:13:34.500> you<05:13:34.680> send<05:13:34.860> the<05:13:35.160> password<05:13:35.400> over 05:13:35.868 --> 05:13:35.878 align:start position:0% so when you send the password over 05:13:35.878 --> 05:13:38.090 align:start position:0% so when you send the password over telnet<05:13:36.540> it's<05:13:37.138> actually<05:13:37.320> in<05:13:37.500> what<05:13:37.740> we<05:13:37.860> call 05:13:38.090 --> 05:13:38.100 align:start position:0% telnet it's actually in what we call 05:13:38.100 --> 05:13:40.070 align:start position:0% telnet it's actually in what we call plain<05:13:38.940> text 05:13:40.070 --> 05:13:40.080 align:start position:0% plain text 05:13:40.080 --> 05:13:44.990 align:start position:0% plain text whereas<05:13:40.860> as<05:13:41.520> we<05:13:41.700> mentioned<05:13:42.180> with<05:13:42.600> SSH<05:13:44.000> it 05:13:44.990 --> 05:13:45.000 align:start position:0% whereas as we mentioned with SSH it 05:13:45.000 --> 05:13:47.510 align:start position:0% whereas as we mentioned with SSH it transmits<05:13:45.660> the<05:13:45.780> password<05:13:46.020> encrypted<05:13:46.920> so<05:13:47.340> if 05:13:47.510 --> 05:13:47.520 align:start position:0% transmits the password encrypted so if 05:13:47.520 --> 05:13:49.190 align:start position:0% transmits the password encrypted so if someone<05:13:47.700> is<05:13:47.940> reading<05:13:48.420> the<05:13:48.540> packets<05:13:48.900> that<05:13:49.080> are 05:13:49.190 --> 05:13:49.200 align:start position:0% someone is reading the packets that are 05:13:49.200 --> 05:13:50.868 align:start position:0% someone is reading the packets that are going<05:13:49.320> back<05:13:49.500> and<05:13:49.680> forth<05:13:49.980> they<05:13:50.400> won't<05:13:50.580> be<05:13:50.700> able 05:13:50.868 --> 05:13:50.878 align:start position:0% going back and forth they won't be able 05:13:50.878 --> 05:13:53.150 align:start position:0% going back and forth they won't be able to<05:13:51.000> hack<05:13:51.240> your<05:13:51.540> system<05:13:51.718> if<05:13:52.378> you're<05:13:52.500> using<05:13:52.798> SSH 05:13:53.150 --> 05:13:53.160 align:start position:0% to hack your system if you're using SSH 05:13:53.160 --> 05:13:54.948 align:start position:0% to hack your system if you're using SSH whereas<05:13:53.878> with<05:13:54.000> telnet<05:13:54.420> they'd<05:13:54.660> be<05:13:54.718> able<05:13:54.840> to 05:13:54.948 --> 05:13:54.958 align:start position:0% whereas with telnet they'd be able to 05:13:54.958 --> 05:13:57.830 align:start position:0% whereas with telnet they'd be able to read<05:13:55.200> your<05:13:55.440> password<05:13:55.620> now<05:13:56.580> telnet<05:13:57.180> uses<05:13:57.540> Port 05:13:57.830 --> 05:13:57.840 align:start position:0% read your password now telnet uses Port 05:13:57.840 --> 05:14:00.770 align:start position:0% read your password now telnet uses Port 23<05:13:58.440> by<05:13:58.680> default<05:13:59.160> which<05:13:59.700> is<05:13:59.940> important<05:14:00.360> to<05:14:00.660> know 05:14:00.770 --> 05:14:00.780 align:start position:0% 23 by default which is important to know 05:14:00.780 --> 05:14:03.110 align:start position:0% 23 by default which is important to know however<05:14:01.500> you<05:14:01.860> could<05:14:02.040> configure<05:14:02.638> it<05:14:02.820> to<05:14:03.000> use 05:14:03.110 --> 05:14:03.120 align:start position:0% however you could configure it to use 05:14:03.120 --> 05:14:04.970 align:start position:0% however you could configure it to use another<05:14:03.298> Port<05:14:03.660> as<05:14:04.200> long<05:14:04.378> as<05:14:04.500> the<05:14:04.740> remote 05:14:04.970 --> 05:14:04.980 align:start position:0% another Port as long as the remote 05:14:04.980 --> 05:14:07.250 align:start position:0% another Port as long as the remote machine<05:14:05.700> is<05:14:06.120> also<05:14:06.360> configured<05:14:06.780> to<05:14:06.900> use<05:14:07.020> that 05:14:07.250 --> 05:14:07.260 align:start position:0% machine is also configured to use that 05:14:07.260 --> 05:14:09.350 align:start position:0% machine is also configured to use that same<05:14:07.440> port<05:14:07.680> with<05:14:08.520> telnet<05:14:09.000> you<05:14:09.180> can<05:14:09.240> actually 05:14:09.350 --> 05:14:09.360 align:start position:0% same port with telnet you can actually 05:14:09.360 --> 05:14:11.448 align:start position:0% same port with telnet you can actually connect<05:14:09.660> to<05:14:10.020> any<05:14:10.260> host<05:14:10.560> that's<05:14:10.920> running<05:14:11.160> the 05:14:11.448 --> 05:14:11.458 align:start position:0% connect to any host that's running the 05:14:11.458 --> 05:14:14.690 align:start position:0% connect to any host that's running the telnet<05:14:11.940> service<05:14:12.180> or<05:14:12.840> Daemon<05:14:13.378> which<05:14:13.860> again<05:14:14.100> the 05:14:14.690 --> 05:14:14.700 align:start position:0% telnet service or Daemon which again the 05:14:14.700 --> 05:14:19.930 align:start position:0% telnet service or Daemon which again the word<05:14:14.878> Daemon<05:14:15.660> is<05:14:16.320> a<05:14:16.680> Unix<05:14:17.040> version<05:14:17.340> of<05:14:18.120> service 05:14:19.930 --> 05:14:19.940 align:start position:0% word Daemon is a Unix version of service 05:14:19.940 --> 05:14:23.570 align:start position:0% word Daemon is a Unix version of service SMB<05:14:20.940> or<05:14:21.420> the<05:14:21.718> server<05:14:22.080> message<05:14:22.320> block<05:14:22.740> which<05:14:23.400> by 05:14:23.570 --> 05:14:23.580 align:start position:0% SMB or the server message block which by 05:14:23.580 --> 05:14:27.350 align:start position:0% SMB or the server message block which by the<05:14:23.700> way<05:14:23.760> is<05:14:24.120> also<05:14:24.480> known<05:14:24.780> as<05:14:25.520> cifs<05:14:26.520> or<05:14:27.000> the 05:14:27.350 --> 05:14:27.360 align:start position:0% the way is also known as cifs or the 05:14:27.360 --> 05:14:29.930 align:start position:0% the way is also known as cifs or the common<05:14:27.540> internet<05:14:27.958> file<05:14:28.680> system<05:14:28.980> is<05:14:29.760> a 05:14:29.930 --> 05:14:29.940 align:start position:0% common internet file system is a 05:14:29.940 --> 05:14:32.030 align:start position:0% common internet file system is a protocol<05:14:30.180> that's<05:14:30.480> mainly<05:14:30.900> used<05:14:31.138> to<05:14:31.740> provide 05:14:32.030 --> 05:14:32.040 align:start position:0% protocol that's mainly used to provide 05:14:32.040 --> 05:14:35.628 align:start position:0% protocol that's mainly used to provide shared<05:14:32.878> access<05:14:33.240> to<05:14:34.138> files<05:14:34.860> peripheral 05:14:35.628 --> 05:14:35.638 align:start position:0% shared access to files peripheral 05:14:35.638 --> 05:14:38.868 align:start position:0% shared access to files peripheral devices<05:14:36.120> like<05:14:36.780> printers<05:14:37.620> most<05:14:38.040> most<05:14:38.520> of<05:14:38.760> the 05:14:38.868 --> 05:14:38.878 align:start position:0% devices like printers most most of the 05:14:38.878 --> 05:14:40.730 align:start position:0% devices like printers most most of the time 05:14:40.730 --> 05:14:40.740 align:start position:0% time 05:14:40.740 --> 05:14:43.970 align:start position:0% time and<05:14:41.400> also<05:14:41.700> access<05:14:42.120> to<05:14:42.600> serial<05:14:43.260> ports<05:14:43.680> and 05:14:43.970 --> 05:14:43.980 align:start position:0% and also access to serial ports and 05:14:43.980 --> 05:14:46.190 align:start position:0% and also access to serial ports and other<05:14:44.160> communication<05:14:44.878> between<05:14:45.360> nodes<05:14:45.840> on<05:14:46.020> a 05:14:46.190 --> 05:14:46.200 align:start position:0% other communication between nodes on a 05:14:46.200 --> 05:14:49.570 align:start position:0% other communication between nodes on a network<05:14:46.820> Windows<05:14:47.820> systems<05:14:48.298> used<05:14:48.660> SMB 05:14:49.570 --> 05:14:49.580 align:start position:0% network Windows systems used SMB 05:14:49.580 --> 05:14:51.890 align:start position:0% network Windows systems used SMB primarily<05:14:50.580> before<05:14:50.940> the<05:14:51.240> introduction<05:14:51.600> of 05:14:51.890 --> 05:14:51.900 align:start position:0% primarily before the introduction of 05:14:51.900 --> 05:14:55.730 align:start position:0% primarily before the introduction of something<05:14:52.200> called<05:14:52.740> uh<05:14:53.878> active<05:14:54.740> directories 05:14:55.730 --> 05:14:55.740 align:start position:0% something called uh active directories 05:14:55.740 --> 05:14:58.310 align:start position:0% something called uh active directories which<05:14:56.580> we'll<05:14:56.940> talk<05:14:57.180> more<05:14:57.360> about<05:14:57.660> a<05:14:58.080> little<05:14:58.200> bit 05:14:58.310 --> 05:14:58.320 align:start position:0% which we'll talk more about a little bit 05:14:58.320 --> 05:15:01.610 align:start position:0% which we'll talk more about a little bit later<05:14:58.560> this<05:14:59.160> is<05:14:59.400> currently<05:14:59.760> what's<05:15:00.180> used<05:15:00.620> in 05:15:01.610 --> 05:15:01.620 align:start position:0% later this is currently what's used in 05:15:01.620 --> 05:15:04.368 align:start position:0% later this is currently what's used in Microsoft<05:15:02.280> networks<05:15:03.060> now<05:15:03.718> Windows<05:15:04.200> services 05:15:04.368 --> 05:15:04.378 align:start position:0% Microsoft networks now Windows services 05:15:04.378 --> 05:15:07.550 align:start position:0% Microsoft networks now Windows services that<05:15:05.040> correspond<05:15:05.700> are<05:15:06.480> called<05:15:06.718> server 05:15:07.550 --> 05:15:07.560 align:start position:0% that correspond are called server 05:15:07.560 --> 05:15:10.430 align:start position:0% that correspond are called server services<05:15:07.860> for<05:15:08.700> the<05:15:08.820> server<05:15:09.120> component<05:15:09.600> and 05:15:10.430 --> 05:15:10.440 align:start position:0% services for the server component and 05:15:10.440 --> 05:15:13.250 align:start position:0% services for the server component and workstation<05:15:11.100> services<05:15:11.600> for<05:15:12.600> the<05:15:12.900> client 05:15:13.250 --> 05:15:13.260 align:start position:0% workstation services for the client 05:15:13.260 --> 05:15:14.570 align:start position:0% workstation services for the client component 05:15:14.570 --> 05:15:14.580 align:start position:0% component 05:15:14.580 --> 05:15:16.788 align:start position:0% component now<05:15:14.940> for<05:15:15.180> example<05:15:15.540> the<05:15:16.378> primary 05:15:16.788 --> 05:15:16.798 align:start position:0% now for example the primary 05:15:16.798 --> 05:15:20.448 align:start position:0% now for example the primary functionality<05:15:17.700> that<05:15:18.298> SMB<05:15:18.958> is<05:15:19.378> typically<05:15:19.920> most 05:15:20.448 --> 05:15:20.458 align:start position:0% functionality that SMB is typically most 05:15:20.458 --> 05:15:23.150 align:start position:0% functionality that SMB is typically most known<05:15:20.878> for<05:15:21.120> is<05:15:21.660> when<05:15:21.958> client<05:15:22.378> computers<05:15:22.860> want 05:15:23.150 --> 05:15:23.160 align:start position:0% known for is when client computers want 05:15:23.160 --> 05:15:26.570 align:start position:0% known for is when client computers want to<05:15:23.340> access<05:15:23.520> files<05:15:24.360> systems<05:15:24.900> or<05:15:25.378> printers<05:15:25.798> on<05:15:26.400> a 05:15:26.570 --> 05:15:26.580 align:start position:0% to access files systems or printers on a 05:15:26.580 --> 05:15:29.090 align:start position:0% to access files systems or printers on a shared<05:15:26.878> network<05:15:27.120> or<05:15:27.540> server<05:15:28.020> this<05:15:28.620> is<05:15:28.740> when 05:15:29.090 --> 05:15:29.100 align:start position:0% shared network or server this is when 05:15:29.100 --> 05:15:32.470 align:start position:0% shared network or server this is when SMB<05:15:29.940> is<05:15:30.420> most<05:15:30.718> often<05:15:31.200> used 05:15:32.470 --> 05:15:32.480 align:start position:0% SMB is most often used 05:15:32.480 --> 05:15:35.510 align:start position:0% SMB is most often used Samba<05:15:33.480> which<05:15:34.080> you<05:15:34.500> may<05:15:34.620> have<05:15:34.860> seen<05:15:35.040> if<05:15:35.340> you've 05:15:35.510 --> 05:15:35.520 align:start position:0% Samba which you may have seen if you've 05:15:35.520 --> 05:15:37.850 align:start position:0% Samba which you may have seen if you've ever<05:15:35.700> dealt<05:15:36.120> with<05:15:36.240> a<05:15:36.780> Mac<05:15:37.020> or<05:15:37.440> a<05:15:37.560> Linux 05:15:37.850 --> 05:15:37.860 align:start position:0% ever dealt with a Mac or a Linux 05:15:37.860 --> 05:15:40.610 align:start position:0% ever dealt with a Mac or a Linux computer<05:15:38.100> is<05:15:39.060> free<05:15:39.360> software<05:15:39.900> that's<05:15:40.260> a 05:15:40.610 --> 05:15:40.620 align:start position:0% computer is free software that's a 05:15:40.620 --> 05:15:44.270 align:start position:0% computer is free software that's a re-implementation<05:15:41.580> of<05:15:42.420> the<05:15:42.718> SMB<05:15:43.260> or<05:15:43.500> cifs 05:15:44.270 --> 05:15:44.280 align:start position:0% re-implementation of the SMB or cifs 05:15:44.280 --> 05:15:47.050 align:start position:0% re-implementation of the SMB or cifs networking<05:15:45.000> protocol<05:15:45.420> for<05:15:46.200> other<05:15:46.378> systems 05:15:47.050 --> 05:15:47.060 align:start position:0% networking protocol for other systems 05:15:47.060 --> 05:15:51.170 align:start position:0% networking protocol for other systems even<05:15:48.060> though<05:15:48.420> SMB<05:15:49.378> is<05:15:49.680> primarily<05:15:50.218> used<05:15:50.580> or<05:15:50.940> was 05:15:51.170 --> 05:15:51.180 align:start position:0% even though SMB is primarily used or was 05:15:51.180 --> 05:15:53.208 align:start position:0% even though SMB is primarily used or was primarily<05:15:51.780> used<05:15:51.958> with<05:15:52.200> Microsoft<05:15:52.680> systems 05:15:53.208 --> 05:15:53.218 align:start position:0% primarily used with Microsoft systems 05:15:53.218 --> 05:15:55.310 align:start position:0% primarily used with Microsoft systems there<05:15:53.820> are<05:15:53.940> still<05:15:54.120> other<05:15:54.360> products<05:15:54.900> that<05:15:55.138> use 05:15:55.310 --> 05:15:55.320 align:start position:0% there are still other products that use 05:15:55.320 --> 05:15:57.708 align:start position:0% there are still other products that use SMB<05:15:55.920> for<05:15:56.160> file<05:15:56.458> sharing<05:15:56.878> in<05:15:57.540> different 05:15:57.708 --> 05:15:57.718 align:start position:0% SMB for file sharing in different 05:15:57.718 --> 05:15:59.628 align:start position:0% SMB for file sharing in different operating<05:15:58.200> systems<05:15:58.740> which<05:15:59.160> is<05:15:59.218> why<05:15:59.458> it's 05:15:59.628 --> 05:15:59.638 align:start position:0% operating systems which is why it's 05:15:59.638 --> 05:16:01.250 align:start position:0% operating systems which is why it's important<05:16:00.000> that<05:16:00.298> we<05:16:00.420> still<05:16:00.660> familiarize 05:16:01.250 --> 05:16:01.260 align:start position:0% important that we still familiarize 05:16:01.260 --> 05:16:02.948 align:start position:0% important that we still familiarize ourselves<05:16:01.680> with<05:16:01.980> it 05:16:02.948 --> 05:16:02.958 align:start position:0% ourselves with it 05:16:02.958 --> 05:16:05.890 align:start position:0% ourselves with it ldap<05:16:03.958> stands<05:16:04.620> for<05:16:04.740> the<05:16:05.160> lightweight 05:16:05.890 --> 05:16:05.900 align:start position:0% ldap stands for the lightweight 05:16:05.900 --> 05:16:08.990 align:start position:0% ldap stands for the lightweight directory<05:16:06.900> access<05:16:07.200> protocol<05:16:07.980> and<05:16:08.760> this<05:16:08.940> is 05:16:08.990 --> 05:16:09.000 align:start position:0% directory access protocol and this is 05:16:09.000 --> 05:16:12.430 align:start position:0% directory access protocol and this is what<05:16:09.240> defines<05:16:09.718> how<05:16:10.138> a<05:16:10.320> user<05:16:10.680> can<05:16:11.160> access<05:16:11.458> files 05:16:12.430 --> 05:16:12.440 align:start position:0% what defines how a user can access files 05:16:12.440 --> 05:16:15.470 align:start position:0% what defines how a user can access files resources<05:16:13.440> or<05:16:13.980> share<05:16:14.218> directory<05:16:14.820> data<05:16:15.120> and 05:16:15.470 --> 05:16:15.480 align:start position:0% resources or share directory data and 05:16:15.480 --> 05:16:18.288 align:start position:0% resources or share directory data and perform<05:16:15.718> operations<05:16:16.620> on<05:16:17.160> a<05:16:17.280> server<05:16:17.580> in<05:16:18.120> a 05:16:18.288 --> 05:16:18.298 align:start position:0% perform operations on a server in a 05:16:18.298 --> 05:16:22.970 align:start position:0% perform operations on a server in a tcpip<05:16:19.138> network<05:16:19.820> now<05:16:20.820> this<05:16:21.420> is<05:16:21.660> not<05:16:22.020> how<05:16:22.798> they 05:16:22.970 --> 05:16:22.980 align:start position:0% tcpip network now this is not how they 05:16:22.980 --> 05:16:26.570 align:start position:0% tcpip network now this is not how they access<05:16:23.218> it<05:16:23.580> this<05:16:24.180> simply<05:16:24.480> defines<05:16:25.080> how<05:16:25.860> a<05:16:26.280> user 05:16:26.570 --> 05:16:26.580 align:start position:0% access it this simply defines how a user 05:16:26.580 --> 05:16:29.390 align:start position:0% access it this simply defines how a user can<05:16:26.878> access<05:16:27.180> it<05:16:27.600> meaning<05:16:28.378> that<05:16:28.920> we're<05:16:29.100> really 05:16:29.390 --> 05:16:29.400 align:start position:0% can access it meaning that we're really 05:16:29.400 --> 05:16:32.208 align:start position:0% can access it meaning that we're really talking<05:16:29.700> about<05:16:29.940> here<05:16:30.420> are<05:16:31.020> users 05:16:32.208 --> 05:16:32.218 align:start position:0% talking about here are users 05:16:32.218 --> 05:16:37.250 align:start position:0% talking about here are users and<05:16:32.878> permissions 05:16:37.250 --> 05:16:37.260 align:start position:0% 05:16:37.260 --> 05:16:40.670 align:start position:0% so<05:16:37.920> basically<05:16:38.400> ldap<05:16:39.298> is<05:16:39.540> the<05:16:39.660> protocol<05:16:40.020> that 05:16:40.670 --> 05:16:40.680 align:start position:0% so basically ldap is the protocol that 05:16:40.680 --> 05:16:43.730 align:start position:0% so basically ldap is the protocol that controls<05:16:41.100> how<05:16:41.520> users<05:16:42.020> manage<05:16:43.020> directory 05:16:43.730 --> 05:16:43.740 align:start position:0% controls how users manage directory 05:16:43.740 --> 05:16:47.170 align:start position:0% controls how users manage directory information<05:16:44.120> such<05:16:45.120> as<05:16:45.298> data<05:16:46.200> about<05:16:46.378> users 05:16:47.170 --> 05:16:47.180 align:start position:0% information such as data about users 05:16:47.180 --> 05:16:51.590 align:start position:0% information such as data about users devices<05:16:48.440> permissions<05:16:49.878> searching<05:16:50.878> and<05:16:51.360> other 05:16:51.590 --> 05:16:51.600 align:start position:0% devices permissions searching and other 05:16:51.600 --> 05:16:53.750 align:start position:0% devices permissions searching and other tasks<05:16:52.020> in<05:16:52.200> most<05:16:52.378> networks<05:16:52.980> we're<05:16:53.520> going<05:16:53.638> to 05:16:53.750 --> 05:16:53.760 align:start position:0% tasks in most networks we're going to 05:16:53.760 --> 05:16:55.368 align:start position:0% tasks in most networks we're going to deal<05:16:53.878> with<05:16:54.120> this<05:16:54.298> a<05:16:54.540> little<05:16:54.600> more<05:16:54.900> in<05:16:55.080> depth 05:16:55.368 --> 05:16:55.378 align:start position:0% deal with this a little more in depth 05:16:55.378 --> 05:16:58.070 align:start position:0% deal with this a little more in depth later<05:16:55.680> on<05:16:55.920> as<05:16:56.100> well<05:16:56.280> now<05:16:57.120> it<05:16:57.360> was<05:16:57.480> designed<05:16:57.900> to 05:16:58.070 --> 05:16:58.080 align:start position:0% later on as well now it was designed to 05:16:58.080 --> 05:17:00.530 align:start position:0% later on as well now it was designed to be<05:16:58.260> used<05:16:58.560> on<05:16:59.100> the<05:16:59.218> internet<05:16:59.400> and<05:17:00.060> it<05:17:00.180> relies 05:17:00.530 --> 05:17:00.540 align:start position:0% be used on the internet and it relies 05:17:00.540 --> 05:17:04.490 align:start position:0% be used on the internet and it relies heavily<05:17:01.260> on<05:17:02.160> DNS<05:17:02.878> the<05:17:03.240> domain<05:17:03.780> name<05:17:04.080> service 05:17:04.490 --> 05:17:04.500 align:start position:0% heavily on DNS the domain name service 05:17:04.500 --> 05:17:06.830 align:start position:0% heavily on DNS the domain name service which<05:17:05.218> we<05:17:05.520> talked<05:17:05.820> about<05:17:05.878> is<05:17:06.420> a<05:17:06.600> way<05:17:06.718> of 05:17:06.830 --> 05:17:06.840 align:start position:0% which we talked about is a way of 05:17:06.840 --> 05:17:10.788 align:start position:0% which we talked about is a way of converting<05:17:07.378> say<05:17:07.920> google.com<05:17:08.780> into<05:17:09.780> its<05:17:10.500> IP 05:17:10.788 --> 05:17:10.798 align:start position:0% converting say google.com into its IP 05:17:10.798 --> 05:17:13.368 align:start position:0% converting say google.com into its IP address<05:17:11.040> we're<05:17:11.878> going<05:17:12.060> to<05:17:12.180> discuss<05:17:12.480> DNS<05:17:13.138> in 05:17:13.368 --> 05:17:13.378 align:start position:0% address we're going to discuss DNS in 05:17:13.378 --> 05:17:16.070 align:start position:0% address we're going to discuss DNS in Greater<05:17:13.860> detail<05:17:14.160> in<05:17:14.458> another<05:17:14.638> module<05:17:15.240> now 05:17:16.070 --> 05:17:16.080 align:start position:0% Greater detail in another module now 05:17:16.080 --> 05:17:18.288 align:start position:0% Greater detail in another module now Microsoft's<05:17:16.980> active<05:17:17.458> directory<05:17:18.060> service 05:17:18.288 --> 05:17:18.298 align:start position:0% Microsoft's active directory service 05:17:18.298 --> 05:17:22.610 align:start position:0% Microsoft's active directory service which<05:17:18.840> we<05:17:19.020> just<05:17:19.260> mentioned<05:17:19.740> and<05:17:20.580> novell's<05:17:21.620> NDS 05:17:22.610 --> 05:17:22.620 align:start position:0% which we just mentioned and novell's NDS 05:17:22.620 --> 05:17:25.730 align:start position:0% which we just mentioned and novell's NDS and<05:17:23.160> e-directory<05:17:24.060> services<05:17:24.440> Novell<05:17:25.440> being 05:17:25.730 --> 05:17:25.740 align:start position:0% and e-directory services Novell being 05:17:25.740 --> 05:17:28.670 align:start position:0% and e-directory services Novell being another<05:17:26.280> networking<05:17:26.940> operating<05:17:27.480> system<05:17:27.840> as 05:17:28.670 --> 05:17:28.680 align:start position:0% another networking operating system as 05:17:28.680 --> 05:17:32.090 align:start position:0% another networking operating system as well<05:17:28.860> as<05:17:29.040> Apple's<05:17:29.700> open<05:17:29.940> directory<05:17:31.100> directory 05:17:32.090 --> 05:17:32.100 align:start position:0% well as Apple's open directory directory 05:17:32.100 --> 05:17:36.590 align:start position:0% well as Apple's open directory directory system<05:17:32.600> all<05:17:33.600> use<05:17:34.100> ldap<05:17:35.100> now<05:17:35.878> the<05:17:36.120> reason<05:17:36.298> it's 05:17:36.590 --> 05:17:36.600 align:start position:0% system all use ldap now the reason it's 05:17:36.600 --> 05:17:40.070 align:start position:0% system all use ldap now the reason it's called<05:17:36.840> like<05:17:37.200> lightweight<05:17:38.160> is<05:17:39.120> because<05:17:39.420> it 05:17:40.070 --> 05:17:40.080 align:start position:0% called like lightweight is because it 05:17:40.080 --> 05:17:42.708 align:start position:0% called like lightweight is because it was<05:17:40.200> not<05:17:40.500> as<05:17:40.798> Network<05:17:41.160> intensive<05:17:41.878> as<05:17:42.360> its 05:17:42.708 --> 05:17:42.718 align:start position:0% was not as Network intensive as its 05:17:42.718 --> 05:17:44.750 align:start position:0% was not as Network intensive as its predecessor<05:17:43.320> which<05:17:44.040> was<05:17:44.218> simply<05:17:44.520> the 05:17:44.750 --> 05:17:44.760 align:start position:0% predecessor which was simply the 05:17:44.760 --> 05:17:47.270 align:start position:0% predecessor which was simply the directory<05:17:45.298> access<05:17:45.480> Protocol<05:17:46.138> no<05:17:46.920> need<05:17:47.100> to 05:17:47.270 --> 05:17:47.280 align:start position:0% directory access Protocol no need to 05:17:47.280 --> 05:17:48.708 align:start position:0% directory access Protocol no need to know<05:17:47.400> that<05:17:47.520> but<05:17:47.700> I<05:17:47.878> just<05:17:48.000> wanted<05:17:48.180> to<05:17:48.420> explain 05:17:48.708 --> 05:17:48.718 align:start position:0% know that but I just wanted to explain 05:17:48.718 --> 05:17:51.470 align:start position:0% know that but I just wanted to explain the<05:17:49.680> reasoning<05:17:50.458> behind<05:17:50.820> that<05:17:51.060> light<05:17:51.240> weight 05:17:51.470 --> 05:17:51.480 align:start position:0% the reasoning behind that light weight 05:17:51.480 --> 05:17:52.490 align:start position:0% the reasoning behind that light weight in<05:17:51.780> there 05:17:52.490 --> 05:17:52.500 align:start position:0% in there 05:17:52.500 --> 05:17:54.708 align:start position:0% in there also<05:17:53.160> it's<05:17:53.340> important<05:17:53.760> to<05:17:53.940> know<05:17:54.060> that<05:17:54.420> port 05:17:54.708 --> 05:17:54.718 align:start position:0% also it's important to know that port 05:17:54.718 --> 05:17:58.368 align:start position:0% also it's important to know that port 389<05:17:55.560> is<05:17:56.040> used<05:17:56.280> by<05:17:56.878> default<05:17:57.360> for<05:17:57.958> all<05:17:58.200> the 05:17:58.368 --> 05:17:58.378 align:start position:0% 389 is used by default for all the 05:17:58.378 --> 05:18:00.650 align:start position:0% 389 is used by default for all the communication<05:17:58.980> of<05:17:59.458> the<05:17:59.638> requests<05:18:00.180> for 05:18:00.650 --> 05:18:00.660 align:start position:0% communication of the requests for 05:18:00.660 --> 05:18:04.190 align:start position:0% communication of the requests for information<05:18:00.900> and<05:18:01.440> objects<05:18:02.280> finally<05:18:03.200> zero 05:18:04.190 --> 05:18:04.200 align:start position:0% information and objects finally zero 05:18:04.200 --> 05:18:08.948 align:start position:0% information and objects finally zero conf<05:18:04.440> or<05:18:05.160> zero<05:18:06.000> configuration 05:18:08.948 --> 05:18:08.958 align:start position:0% conf or zero configuration 05:18:08.958 --> 05:18:12.170 align:start position:0% conf or zero configuration networking<05:18:09.958> is<05:18:10.680> a<05:18:10.798> set<05:18:10.920> of<05:18:11.100> standards<05:18:11.638> that 05:18:12.170 --> 05:18:12.180 align:start position:0% networking is a set of standards that 05:18:12.180 --> 05:18:14.208 align:start position:0% networking is a set of standards that was<05:18:12.360> established<05:18:12.840> to<05:18:13.020> allow<05:18:13.378> users<05:18:13.860> the 05:18:14.208 --> 05:18:14.218 align:start position:0% was established to allow users the 05:18:14.218 --> 05:18:17.810 align:start position:0% was established to allow users the ability<05:18:14.520> to<05:18:15.000> have<05:18:15.240> network<05:18:15.958> connectivity<05:18:16.920> out 05:18:17.810 --> 05:18:17.820 align:start position:0% ability to have network connectivity out 05:18:17.820 --> 05:18:21.590 align:start position:0% ability to have network connectivity out of<05:18:18.000> the<05:18:18.120> box<05:18:18.680> or<05:18:19.680> Plug<05:18:20.100> and<05:18:20.280> Play<05:18:20.458> or<05:18:21.180> without 05:18:21.590 --> 05:18:21.600 align:start position:0% of the box or Plug and Play or without 05:18:21.600 --> 05:18:24.288 align:start position:0% of the box or Plug and Play or without the<05:18:22.138> need<05:18:22.440> for<05:18:23.218> any<05:18:23.458> sort<05:18:23.700> of<05:18:23.878> technical 05:18:24.288 --> 05:18:24.298 align:start position:0% the need for any sort of technical 05:18:24.298 --> 05:18:28.190 align:start position:0% the need for any sort of technical change<05:18:24.900> or<05:18:25.378> configuration<05:18:26.360> zero<05:18:27.360> con<05:18:27.600> capable 05:18:28.190 --> 05:18:28.200 align:start position:0% change or configuration zero con capable 05:18:28.200 --> 05:18:30.830 align:start position:0% change or configuration zero con capable protocols<05:18:29.040> will<05:18:29.520> generally<05:18:29.878> use<05:18:30.240> Mac 05:18:30.830 --> 05:18:30.840 align:start position:0% protocols will generally use Mac 05:18:30.840 --> 05:18:33.708 align:start position:0% protocols will generally use Mac addresses<05:18:31.378> or<05:18:31.740> the<05:18:31.980> physical<05:18:32.218> addresses<05:18:33.120> as 05:18:33.708 --> 05:18:33.718 align:start position:0% addresses or the physical addresses as 05:18:33.718 --> 05:18:36.650 align:start position:0% addresses or the physical addresses as they<05:18:33.958> are<05:18:34.138> unique<05:18:34.440> to<05:18:34.860> each<05:18:35.100> device<05:18:35.360> with<05:18:36.360> a 05:18:36.650 --> 05:18:36.660 align:start position:0% they are unique to each device with a 05:18:36.660 --> 05:18:39.530 align:start position:0% they are unique to each device with a NIC<05:18:37.020> or<05:18:37.560> network<05:18:37.920> interface<05:18:38.638> card 05:18:39.530 --> 05:18:39.540 align:start position:0% NIC or network interface card 05:18:39.540 --> 05:18:41.830 align:start position:0% NIC or network interface card in<05:18:40.200> order<05:18:40.320> for<05:18:40.680> devices 05:18:41.830 --> 05:18:41.840 align:start position:0% in order for devices 05:18:41.840 --> 05:18:46.128 align:start position:0% in order for devices to<05:18:42.840> fit<05:18:43.260> into<05:18:43.560> a<05:18:44.040> zero<05:18:44.458> conf<05:18:44.700> standard<05:18:45.480> they 05:18:46.128 --> 05:18:46.138 align:start position:0% to fit into a zero conf standard they 05:18:46.138 --> 05:18:49.190 align:start position:0% to fit into a zero conf standard they have<05:18:46.320> to<05:18:46.560> fit<05:18:47.100> or<05:18:47.458> meet<05:18:47.700> four<05:18:48.420> qualifications 05:18:49.190 --> 05:18:49.200 align:start position:0% have to fit or meet four qualifications 05:18:49.200 --> 05:18:52.670 align:start position:0% have to fit or meet four qualifications or<05:18:49.680> functions<05:18:50.280> first<05:18:51.060> the<05:18:51.900> network<05:18:52.138> address 05:18:52.670 --> 05:18:52.680 align:start position:0% or functions first the network address 05:18:52.680 --> 05:18:55.788 align:start position:0% or functions first the network address assignment<05:18:53.638> must<05:18:54.060> be<05:18:54.298> automatic<05:18:54.958> if<05:18:55.680> you 05:18:55.788 --> 05:18:55.798 align:start position:0% assignment must be automatic if you 05:18:55.798 --> 05:18:57.350 align:start position:0% assignment must be automatic if you recall<05:18:56.160> from<05:18:56.340> a<05:18:56.580> plus<05:18:56.760> and<05:18:57.060> this<05:18:57.180> is<05:18:57.298> something 05:18:57.350 --> 05:18:57.360 align:start position:0% recall from a plus and this is something 05:18:57.360 --> 05:18:59.208 align:start position:0% recall from a plus and this is something we'll<05:18:57.540> talk<05:18:57.718> about<05:18:57.840> a<05:18:58.080> bit<05:18:58.260> later<05:18:58.500> this<05:18:59.160> is 05:18:59.208 --> 05:18:59.218 align:start position:0% we'll talk about a bit later this is 05:18:59.218 --> 05:19:03.288 align:start position:0% we'll talk about a bit later this is what<05:18:59.520> we<05:18:59.760> use<05:18:59.940> when<05:19:00.480> we're<05:19:00.660> using<05:19:01.020> DHCP 05:19:03.288 --> 05:19:03.298 align:start position:0% what we use when we're using DHCP 05:19:03.298 --> 05:19:06.910 align:start position:0% what we use when we're using DHCP second<05:19:04.218> automatic<05:19:05.218> multicast<05:19:06.180> address 05:19:06.910 --> 05:19:06.920 align:start position:0% second automatic multicast address 05:19:06.920 --> 05:19:10.730 align:start position:0% second automatic multicast address assignment<05:19:07.920> must<05:19:08.878> be<05:19:09.180> implemented<05:19:09.958> which<05:19:10.500> is 05:19:10.730 --> 05:19:10.740 align:start position:0% assignment must be implemented which is 05:19:10.740 --> 05:19:14.288 align:start position:0% assignment must be implemented which is also<05:19:11.040> related<05:19:11.280> to<05:19:11.520> the<05:19:11.700> DHCP<05:19:12.360> standard<05:19:12.840> third 05:19:14.288 --> 05:19:14.298 align:start position:0% also related to the DHCP standard third 05:19:14.298 --> 05:19:17.090 align:start position:0% also related to the DHCP standard third automatic<05:19:15.298> translation<05:19:16.020> between<05:19:16.500> Network 05:19:17.090 --> 05:19:17.100 align:start position:0% automatic translation between Network 05:19:17.100 --> 05:19:19.850 align:start position:0% automatic translation between Network names<05:19:17.400> and<05:19:17.820> addresses<05:19:18.360> must<05:19:18.718> exist<05:19:19.138> this<05:19:19.798> is 05:19:19.850 --> 05:19:19.860 align:start position:0% names and addresses must exist this is 05:19:19.860 --> 05:19:22.610 align:start position:0% names and addresses must exist this is what<05:19:20.040> we<05:19:20.218> talk<05:19:20.340> about<05:19:20.520> when<05:19:20.820> we<05:19:21.000> deal<05:19:21.120> with<05:19:21.420> DNS 05:19:22.610 --> 05:19:22.620 align:start position:0% what we talk about when we deal with DNS 05:19:22.620 --> 05:19:26.390 align:start position:0% what we talk about when we deal with DNS finally<05:19:23.660> discovery<05:19:24.660> of<05:19:24.900> Network<05:19:25.260> Services<05:19:25.740> or 05:19:26.390 --> 05:19:26.400 align:start position:0% finally discovery of Network Services or 05:19:26.400 --> 05:19:28.670 align:start position:0% finally discovery of Network Services or the<05:19:26.520> location<05:19:26.700> by<05:19:27.360> the<05:19:27.660> protocol<05:19:27.958> and<05:19:28.560> the 05:19:28.670 --> 05:19:28.680 align:start position:0% the location by the protocol and the 05:19:28.680 --> 05:19:31.910 align:start position:0% the location by the protocol and the name<05:19:28.920> is<05:19:29.700> required<05:19:30.298> meaning<05:19:31.020> that<05:19:31.378> it<05:19:31.500> must<05:19:31.680> be 05:19:31.910 --> 05:19:31.920 align:start position:0% name is required meaning that it must be 05:19:31.920 --> 05:19:34.190 align:start position:0% name is required meaning that it must be able<05:19:32.160> to<05:19:32.580> find<05:19:33.120> all<05:19:33.540> of<05:19:33.660> this<05:19:33.958> information 05:19:34.190 --> 05:19:34.200 align:start position:0% able to find all of this information 05:19:34.200 --> 05:19:36.170 align:start position:0% able to find all of this information when<05:19:35.160> it<05:19:35.340> goes<05:19:35.760> on<05:19:35.878> the<05:19:36.060> network 05:19:36.170 --> 05:19:36.180 align:start position:0% when it goes on the network 05:19:36.180 --> 05:19:39.170 align:start position:0% when it goes on the network automatically<05:19:37.440> this<05:19:37.920> is<05:19:38.040> what<05:19:38.280> allows<05:19:38.700> users 05:19:39.170 --> 05:19:39.180 align:start position:0% automatically this is what allows users 05:19:39.180 --> 05:19:41.690 align:start position:0% automatically this is what allows users to<05:19:39.360> be<05:19:39.480> able<05:19:39.600> to<05:19:39.780> purchase<05:19:40.138> a<05:19:40.440> router<05:19:40.740> from<05:19:41.458> the 05:19:41.690 --> 05:19:41.700 align:start position:0% to be able to purchase a router from the 05:19:41.700 --> 05:19:44.990 align:start position:0% to be able to purchase a router from the local<05:19:41.940> Best<05:19:42.718> Buy<05:19:42.900> or<05:19:43.200> electronics<05:19:43.798> store<05:19:44.100> take 05:19:44.990 --> 05:19:45.000 align:start position:0% local Best Buy or electronics store take 05:19:45.000 --> 05:19:47.868 align:start position:0% local Best Buy or electronics store take it<05:19:45.240> home<05:19:45.500> plug<05:19:46.500> it<05:19:46.620> into<05:19:46.798> their<05:19:47.100> ISB<05:19:47.638> or 05:19:47.868 --> 05:19:47.878 align:start position:0% it home plug it into their ISB or 05:19:47.878 --> 05:19:50.030 align:start position:0% it home plug it into their ISB or Internet<05:19:48.000> service<05:19:48.360> provider<05:19:48.958> connection<05:19:49.138> and 05:19:50.030 --> 05:19:50.040 align:start position:0% Internet service provider connection and 05:19:50.040 --> 05:19:51.948 align:start position:0% Internet service provider connection and automatically<05:19:50.520> have<05:19:50.820> it<05:19:51.000> work<05:19:51.298> automatically 05:19:51.948 --> 05:19:51.958 align:start position:0% automatically have it work automatically 05:19:51.958 --> 05:19:54.050 align:start position:0% automatically have it work automatically another<05:19:52.440> implementation<05:19:53.218> by<05:19:53.580> the<05:19:53.700> way<05:19:53.760> of 05:19:54.050 --> 05:19:54.060 align:start position:0% another implementation by the way of 05:19:54.060 --> 05:19:56.270 align:start position:0% another implementation by the way of this<05:19:54.298> is<05:19:54.840> a<05:19:55.020> configuration<05:19:55.500> and<05:19:55.798> networking 05:19:56.270 --> 05:19:56.280 align:start position:0% this is a configuration and networking 05:19:56.280 --> 05:19:57.368 align:start position:0% this is a configuration and networking called 05:19:57.368 --> 05:19:57.378 align:start position:0% called 05:19:57.378 --> 05:19:59.810 align:start position:0% called you<05:19:58.378> PNP 05:19:59.810 --> 05:19:59.820 align:start position:0% you PNP 05:19:59.820 --> 05:20:01.368 align:start position:0% you PNP or 05:20:01.368 --> 05:20:01.378 align:start position:0% or 05:20:01.378 --> 05:20:04.670 align:start position:0% or Universal 05:20:04.670 --> 05:20:04.680 align:start position:0% 05:20:04.680 --> 05:20:07.310 align:start position:0% plug 05:20:07.310 --> 05:20:07.320 align:start position:0% 05:20:07.320 --> 05:20:09.650 align:start position:0% and<05:20:07.798> play 05:20:09.650 --> 05:20:09.660 align:start position:0% and play 05:20:09.660 --> 05:20:11.868 align:start position:0% and play so<05:20:10.020> to<05:20:10.138> recap<05:20:10.440> what<05:20:10.680> we've<05:20:10.860> talked<05:20:11.100> about<05:20:11.218> we 05:20:11.868 --> 05:20:11.878 align:start position:0% so to recap what we've talked about we 05:20:11.878 --> 05:20:13.788 align:start position:0% so to recap what we've talked about we talked<05:20:12.180> about<05:20:12.320> interoperability<05:20:13.320> Services 05:20:13.788 --> 05:20:13.798 align:start position:0% talked about interoperability Services 05:20:13.798 --> 05:20:17.470 align:start position:0% talked about interoperability Services which<05:20:14.638> allows<05:20:15.060> for<05:20:15.360> instance<05:20:15.660> a<05:20:16.138> PC<05:20:16.440> and<05:20:17.100> a<05:20:17.280> Mac 05:20:17.470 --> 05:20:17.480 align:start position:0% which allows for instance a PC and a Mac 05:20:17.480 --> 05:20:20.330 align:start position:0% which allows for instance a PC and a Mac to<05:20:18.480> communicate<05:20:18.958> flawlessly<05:20:19.740> over<05:20:19.980> a<05:20:20.218> network 05:20:20.330 --> 05:20:20.340 align:start position:0% to communicate flawlessly over a network 05:20:20.340 --> 05:20:23.448 align:start position:0% to communicate flawlessly over a network we<05:20:21.298> then<05:20:21.480> talked<05:20:21.900> about<05:20:21.958> the<05:20:22.500> network<05:20:22.740> file 05:20:23.448 --> 05:20:23.458 align:start position:0% we then talked about the network file 05:20:23.458 --> 05:20:26.350 align:start position:0% we then talked about the network file service 05:20:26.350 --> 05:20:26.360 align:start position:0% 05:20:26.360 --> 05:20:34.250 align:start position:0% SSH<05:20:27.360> and<05:20:28.340> SCP<05:20:29.340> SSH<05:20:30.180> being<05:20:30.718> a<05:20:31.200> secure<05:20:32.160> shell 05:20:34.250 --> 05:20:34.260 align:start position:0% SSH and SCP SSH being a secure shell 05:20:34.260 --> 05:20:37.670 align:start position:0% SSH and SCP SSH being a secure shell working<05:20:35.040> on 05:20:37.670 --> 05:20:37.680 align:start position:0% 05:20:37.680 --> 05:20:39.890 align:start position:0% Port<05:20:38.400> 22 05:20:39.890 --> 05:20:39.900 align:start position:0% Port 22 05:20:39.900 --> 05:20:43.910 align:start position:0% Port 22 and<05:20:40.500> SCP<05:20:41.100> being<05:20:41.580> the<05:20:42.060> secure 05:20:43.910 --> 05:20:43.920 align:start position:0% and SCP being the secure 05:20:43.920 --> 05:20:45.830 align:start position:0% and SCP being the secure copy<05:20:44.700> protocol 05:20:45.830 --> 05:20:45.840 align:start position:0% copy protocol 05:20:45.840 --> 05:20:47.628 align:start position:0% copy protocol similar 05:20:47.628 --> 05:20:47.638 align:start position:0% similar 05:20:47.638 --> 05:20:48.430 align:start position:0% similar to 05:20:48.430 --> 05:20:48.440 align:start position:0% to 05:20:48.440 --> 05:20:51.350 align:start position:0% to SFTP<05:20:49.440> the<05:20:49.860> secure<05:20:50.160> file<05:20:50.520> transfer<05:20:51.000> protocol 05:20:51.350 --> 05:20:51.360 align:start position:0% SFTP the secure file transfer protocol 05:20:51.360 --> 05:20:54.650 align:start position:0% SFTP the secure file transfer protocol we<05:20:52.260> looked<05:20:52.500> at<05:20:52.620> telnet<05:20:53.280> which<05:20:53.820> is<05:20:53.940> sort<05:20:54.180> of<05:20:54.298> a 05:20:54.650 --> 05:20:54.660 align:start position:0% we looked at telnet which is sort of a 05:20:54.660 --> 05:20:58.128 align:start position:0% we looked at telnet which is sort of a plain<05:20:55.020> text<05:20:55.260> version<05:20:55.740> of<05:20:56.400> SSH<05:20:56.878> so<05:20:57.718> it's<05:20:57.900> been 05:20:58.128 --> 05:20:58.138 align:start position:0% plain text version of SSH so it's been 05:20:58.138 --> 05:21:01.430 align:start position:0% plain text version of SSH so it's been replaced<05:20:58.740> by<05:20:58.980> it<05:20:59.100> and<05:20:59.820> SMB<05:21:00.480> or<05:21:00.958> the<05:21:01.138> server 05:21:01.430 --> 05:21:01.440 align:start position:0% replaced by it and SMB or the server 05:21:01.440 --> 05:21:05.810 align:start position:0% replaced by it and SMB or the server message<05:21:01.680> block<05:21:02.100> allowing<05:21:03.060> us<05:21:03.240> to<05:21:04.218> share<05:21:05.218> files 05:21:05.810 --> 05:21:05.820 align:start position:0% message block allowing us to share files 05:21:05.820 --> 05:21:09.288 align:start position:0% message block allowing us to share files and<05:21:06.120> resources 05:21:09.288 --> 05:21:09.298 align:start position:0% 05:21:09.298 --> 05:21:12.350 align:start position:0% between<05:21:10.260> different<05:21:10.740> types<05:21:11.280> of<05:21:11.400> systems 05:21:12.350 --> 05:21:12.360 align:start position:0% between different types of systems 05:21:12.360 --> 05:21:15.948 align:start position:0% between different types of systems finally<05:21:13.138> we<05:21:13.860> described<05:21:14.400> and<05:21:14.580> defined<05:21:15.000> ldap<05:21:15.600> or 05:21:15.948 --> 05:21:15.958 align:start position:0% finally we described and defined ldap or 05:21:15.958 --> 05:21:18.050 align:start position:0% finally we described and defined ldap or the<05:21:16.200> lightweight<05:21:16.820> directory<05:21:17.820> access 05:21:18.050 --> 05:21:18.060 align:start position:0% the lightweight directory access 05:21:18.060 --> 05:21:22.010 align:start position:0% the lightweight directory access protocol<05:21:18.780> which<05:21:19.620> defines<05:21:20.280> users<05:21:21.120> and<05:21:21.780> their 05:21:22.010 --> 05:21:22.020 align:start position:0% protocol which defines users and their 05:21:22.020 --> 05:21:24.350 align:start position:0% protocol which defines users and their ability<05:21:22.378> to<05:21:22.860> access<05:21:23.100> all<05:21:23.580> this<05:21:23.760> stuff<05:21:23.940> on<05:21:24.180> the 05:21:24.350 --> 05:21:24.360 align:start position:0% ability to access all this stuff on the 05:21:24.360 --> 05:21:27.530 align:start position:0% ability to access all this stuff on the network<05:21:24.740> and<05:21:25.740> then<05:21:25.980> we<05:21:26.400> explained<05:21:26.878> zero<05:21:27.360> conf 05:21:27.530 --> 05:21:27.540 align:start position:0% network and then we explained zero conf 05:21:27.540 --> 05:21:31.190 align:start position:0% network and then we explained zero conf or<05:21:28.138> zero<05:21:28.798> configuration<05:21:29.600> in<05:21:30.600> networking 05:21:31.190 --> 05:21:31.200 align:start position:0% or zero configuration in networking 05:21:31.200 --> 05:21:34.670 align:start position:0% or zero configuration in networking which<05:21:31.920> allows<05:21:32.700> us<05:21:33.240> to<05:21:33.540> plug<05:21:33.718> up<05:21:33.900> a<05:21:34.138> device<05:21:34.260> and 05:21:34.670 --> 05:21:34.680 align:start position:0% which allows us to plug up a device and 05:21:34.680 --> 05:21:40.680 align:start position:0% which allows us to plug up a device and have<05:21:34.920> it<05:21:35.100> work<05:21:35.340> almost<05:21:35.760> instantaneously 05:21:40.680 --> 05:21:40.690 align:start position:0% 05:21:40.690 --> 05:21:49.690 align:start position:0% [Music] 05:21:49.690 --> 05:21:49.700 align:start position:0% 05:21:49.700 --> 05:21:57.110 align:start position:0% thank<05:21:50.700> you 05:21:57.110 --> 05:21:57.120 align:start position:0% 05:21:57.120 --> 05:21:59.990 align:start position:0% welcome<05:21:57.718> to<05:21:58.020> module<05:21:58.560> 5<05:21:58.680> lesson<05:21:59.340> 1<05:21:59.458> ethernet 05:21:59.990 --> 05:22:00.000 align:start position:0% welcome to module 5 lesson 1 ethernet 05:22:00.000 --> 05:22:03.410 align:start position:0% welcome to module 5 lesson 1 ethernet standards<05:22:00.660> pretty<05:22:01.440> meaty<05:22:02.160> subject<05:22:03.060> this 05:22:03.410 --> 05:22:03.420 align:start position:0% standards pretty meaty subject this 05:22:03.420 --> 05:22:05.150 align:start position:0% standards pretty meaty subject this because<05:22:03.780> it's<05:22:04.200> got<05:22:04.440> a<05:22:04.680> whole<05:22:04.798> bunch<05:22:04.980> of 05:22:05.150 --> 05:22:05.160 align:start position:0% because it's got a whole bunch of 05:22:05.160 --> 05:22:07.610 align:start position:0% because it's got a whole bunch of standards<05:22:05.878> and<05:22:06.180> information<05:22:06.840> as<05:22:07.378> well<05:22:07.500> as 05:22:07.610 --> 05:22:07.620 align:start position:0% standards and information as well as 05:22:07.620 --> 05:22:09.470 align:start position:0% standards and information as well as history<05:22:07.860> to<05:22:08.218> fit<05:22:08.458> in 05:22:09.470 --> 05:22:09.480 align:start position:0% history to fit in 05:22:09.480 --> 05:22:12.590 align:start position:0% history to fit in what<05:22:10.020> is<05:22:10.138> ethernet<05:22:10.620> the<05:22:10.920> history<05:22:11.360> why<05:22:12.360> the 05:22:12.590 --> 05:22:12.600 align:start position:0% what is ethernet the history why the 05:22:12.600 --> 05:22:14.810 align:start position:0% what is ethernet the history why the name<05:22:12.900> just<05:22:13.500> in<05:22:13.680> case<05:22:13.860> you<05:22:13.980> wanted<05:22:14.160> to<05:22:14.340> know<05:22:14.580> I 05:22:14.810 --> 05:22:14.820 align:start position:0% name just in case you wanted to know I 05:22:14.820 --> 05:22:15.708 align:start position:0% name just in case you wanted to know I guess 05:22:15.708 --> 05:22:15.718 align:start position:0% guess 05:22:15.718 --> 05:22:18.890 align:start position:0% guess introduction<05:22:16.378> of<05:22:16.620> ethernet<05:22:16.980> standards 05:22:18.890 --> 05:22:18.900 align:start position:0% introduction of ethernet standards 05:22:18.900 --> 05:22:21.708 align:start position:0% introduction of ethernet standards the<05:22:19.440> Archer<05:22:19.860> Police<05:22:20.040> standard<05:22:20.580> as<05:22:20.940> well<05:22:21.060> ATO 05:22:21.708 --> 05:22:21.718 align:start position:0% the Archer Police standard as well ATO 05:22:21.718 --> 05:22:23.330 align:start position:0% the Archer Police standard as well ATO 2.3<05:22:22.200> which<05:22:22.440> you'll<05:22:22.680> need<05:22:22.798> to<05:22:22.920> be<05:22:22.980> familiar 05:22:23.330 --> 05:22:23.340 align:start position:0% 2.3 which you'll need to be familiar 05:22:23.340 --> 05:22:25.550 align:start position:0% 2.3 which you'll need to be familiar with<05:22:23.520> which<05:22:24.000> defines<05:22:24.420> ethernet 05:22:25.550 --> 05:22:25.560 align:start position:0% with which defines ethernet 05:22:25.560 --> 05:22:28.970 align:start position:0% with which defines ethernet the<05:22:26.160> IEEE<05:22:26.820> as<05:22:27.000> well<05:22:27.180> what<05:22:27.420> they<05:22:27.600> do<05:22:27.780> and<05:22:28.260> their 05:22:28.970 --> 05:22:28.980 align:start position:0% the IEEE as well what they do and their 05:22:28.980 --> 05:22:32.330 align:start position:0% the IEEE as well what they do and their remit<05:22:29.458> per<05:22:30.000> view 05:22:32.330 --> 05:22:32.340 align:start position:0% 05:22:32.340 --> 05:22:34.910 align:start position:0% uh<05:22:33.060> based<05:22:33.360> on<05:22:33.420> a<05:22:33.660> Broadband<05:22:34.200> some<05:22:34.740> history 05:22:34.910 --> 05:22:34.920 align:start position:0% uh based on a Broadband some history 05:22:34.920 --> 05:22:37.310 align:start position:0% uh based on a Broadband some history really<05:22:35.280> of<05:22:35.520> the<05:22:35.700> early<05:22:35.820> days<05:22:36.120> of<05:22:36.480> ethernet 05:22:37.310 --> 05:22:37.320 align:start position:0% really of the early days of ethernet 05:22:37.320 --> 05:22:38.750 align:start position:0% really of the early days of ethernet networking 05:22:38.750 --> 05:22:38.760 align:start position:0% networking 05:22:38.760 --> 05:22:40.730 align:start position:0% networking which<05:22:39.240> are<05:22:39.420> depending<05:22:39.840> on<05:22:39.958> how<05:22:40.200> old<05:22:40.378> you<05:22:40.560> are 05:22:40.730 --> 05:22:40.740 align:start position:0% which are depending on how old you are 05:22:40.740 --> 05:22:42.708 align:start position:0% which are depending on how old you are you<05:22:40.980> may<05:22:41.100> be<05:22:41.340> familiar<05:22:41.760> with 05:22:42.708 --> 05:22:42.718 align:start position:0% you may be familiar with 05:22:42.718 --> 05:22:45.288 align:start position:0% you may be familiar with some<05:22:43.080> of<05:22:43.260> the<05:22:43.378> naming<05:22:43.680> conventions<05:22:44.520> uh<05:22:45.000> the 05:22:45.288 --> 05:22:45.298 align:start position:0% some of the naming conventions uh the 05:22:45.298 --> 05:22:47.150 align:start position:0% some of the naming conventions uh the early<05:22:45.480> days<05:22:45.780> the<05:22:46.138> early<05:22:46.320> specifications 05:22:47.150 --> 05:22:47.160 align:start position:0% early days the early specifications 05:22:47.160 --> 05:22:50.810 align:start position:0% early days the early specifications thick<05:22:47.940> nets<05:22:48.360> in<05:22:48.540> net 05:22:50.810 --> 05:22:50.820 align:start position:0% 05:22:50.820 --> 05:22:52.850 align:start position:0% and<05:22:51.660> some<05:22:51.840> of<05:22:52.020> the<05:22:52.138> standards<05:22:52.560> here<05:22:52.680> which 05:22:52.850 --> 05:22:52.860 align:start position:0% and some of the standards here which 05:22:52.860 --> 05:22:54.410 align:start position:0% and some of the standards here which we're<05:22:53.040> going<05:22:53.160> to<05:22:53.280> run<05:22:53.458> through<05:22:53.700> which<05:22:54.240> you'll 05:22:54.410 --> 05:22:54.420 align:start position:0% we're going to run through which you'll 05:22:54.420 --> 05:22:55.910 align:start position:0% we're going to run through which you'll need<05:22:54.600> to<05:22:54.660> be<05:22:54.780> familiar<05:22:55.138> with<05:22:55.320> because<05:22:55.680> you 05:22:55.910 --> 05:22:55.920 align:start position:0% need to be familiar with because you 05:22:55.920 --> 05:22:58.310 align:start position:0% need to be familiar with because you could<05:22:56.100> be<05:22:56.218> asked<05:22:56.520> a<05:22:56.580> question 05:22:58.310 --> 05:22:58.320 align:start position:0% could be asked a question 05:22:58.320 --> 05:23:01.910 align:start position:0% could be asked a question so<05:22:59.218> that's<05:22:59.400> a<05:22:59.580> good<05:22:59.700> reason<05:22:59.940> as<05:23:00.360> any<05:23:00.920> uh 05:23:01.910 --> 05:23:01.920 align:start position:0% so that's a good reason as any uh 05:23:01.920 --> 05:23:04.610 align:start position:0% so that's a good reason as any uh ethernet<05:23:02.218> it's<05:23:02.638> the<05:23:02.878> was<05:23:03.360> or<05:23:03.780> is<05:23:04.080> the<05:23:04.500> first 05:23:04.610 --> 05:23:04.620 align:start position:0% ethernet it's the was or is the first 05:23:04.620 --> 05:23:07.070 align:start position:0% ethernet it's the was or is the first high-speed<05:23:05.340> land<05:23:05.580> technology<05:23:06.060> that<05:23:06.718> in 05:23:07.070 --> 05:23:07.080 align:start position:0% high-speed land technology that in 05:23:07.080 --> 05:23:10.310 align:start position:0% high-speed land technology that in Connected<05:23:07.940> computers<05:23:08.940> high<05:23:09.360> speed<05:23:09.718> Laser 05:23:10.310 --> 05:23:10.320 align:start position:0% Connected computers high speed Laser 05:23:10.320 --> 05:23:12.410 align:start position:0% Connected computers high speed Laser Printers<05:23:10.820> obviously<05:23:11.820> in<05:23:11.940> the<05:23:12.060> early<05:23:12.180> days 05:23:12.410 --> 05:23:12.420 align:start position:0% Printers obviously in the early days 05:23:12.420 --> 05:23:14.930 align:start position:0% Printers obviously in the early days there<05:23:12.660> needed<05:23:12.958> to<05:23:13.080> be<05:23:13.200> some<05:23:13.560> agreed<05:23:14.458> format 05:23:14.930 --> 05:23:14.940 align:start position:0% there needed to be some agreed format 05:23:14.940 --> 05:23:17.690 align:start position:0% there needed to be some agreed format for<05:23:16.020> um<05:23:16.080> Internet<05:23:16.378> working<05:23:16.740> devices<05:23:17.280> to 05:23:17.690 --> 05:23:17.700 align:start position:0% for um Internet working devices to 05:23:17.700 --> 05:23:19.010 align:start position:0% for um Internet working devices to communicate 05:23:19.010 --> 05:23:19.020 align:start position:0% communicate 05:23:19.020 --> 05:23:20.990 align:start position:0% communicate actually<05:23:19.500> invented<05:23:20.040> by<05:23:20.160> a<05:23:20.280> guy<05:23:20.400> called<05:23:20.638> Bob 05:23:20.990 --> 05:23:21.000 align:start position:0% actually invented by a guy called Bob 05:23:21.000 --> 05:23:23.288 align:start position:0% actually invented by a guy called Bob Metcalfe<05:23:21.840> back<05:23:22.200> in 05:23:23.288 --> 05:23:23.298 align:start position:0% Metcalfe back in 05:23:23.298 --> 05:23:26.090 align:start position:0% Metcalfe back in 1973.<05:23:24.298> it<05:23:24.420> was<05:23:24.660> remarkable<05:23:25.138> in<05:23:25.500> as<05:23:25.680> much<05:23:25.860> that 05:23:26.090 --> 05:23:26.100 align:start position:0% 1973. it was remarkable in as much that 05:23:26.100 --> 05:23:28.550 align:start position:0% 1973. it was remarkable in as much that at<05:23:26.638> the<05:23:26.760> time<05:23:26.940> competing<05:23:27.600> was<05:23:27.780> dominated<05:23:28.200> by 05:23:28.550 --> 05:23:28.560 align:start position:0% at the time competing was dominated by 05:23:28.560 --> 05:23:32.150 align:start position:0% at the time competing was dominated by some<05:23:28.860> very<05:23:29.100> large<05:23:29.600> and<05:23:30.600> expensive<05:23:31.378> mainframe 05:23:32.150 --> 05:23:32.160 align:start position:0% some very large and expensive mainframe 05:23:32.160 --> 05:23:33.650 align:start position:0% some very large and expensive mainframe computers 05:23:33.650 --> 05:23:33.660 align:start position:0% computers 05:23:33.660 --> 05:23:36.410 align:start position:0% computers um<05:23:33.780> to<05:23:34.080> name<05:23:34.200> IBM<05:23:34.860> as<05:23:35.580> a<05:23:35.820> one<05:23:36.060> of<05:23:36.180> the<05:23:36.240> main 05:23:36.410 --> 05:23:36.420 align:start position:0% um to name IBM as a one of the main 05:23:36.420 --> 05:23:37.788 align:start position:0% um to name IBM as a one of the main players<05:23:36.780> at<05:23:36.958> the<05:23:37.138> time 05:23:37.788 --> 05:23:37.798 align:start position:0% players at the time 05:23:37.798 --> 05:23:39.230 align:start position:0% players at the time it's<05:23:38.218> only<05:23:38.400> a<05:23:38.580> few<05:23:38.700> people<05:23:38.878> could<05:23:39.120> actually 05:23:39.230 --> 05:23:39.240 align:start position:0% it's only a few people could actually 05:23:39.240 --> 05:23:41.930 align:start position:0% it's only a few people could actually afford<05:23:39.540> to<05:23:39.718> buy<05:23:39.900> the<05:23:40.080> mainframes<05:23:40.740> and<05:23:41.520> the 05:23:41.930 --> 05:23:41.940 align:start position:0% afford to buy the mainframes and the 05:23:41.940 --> 05:23:45.288 align:start position:0% afford to buy the mainframes and the information<05:23:42.500> required<05:23:43.500> in<05:23:43.798> order<05:23:43.920> to<05:23:44.458> use 05:23:45.288 --> 05:23:45.298 align:start position:0% information required in order to use 05:23:45.298 --> 05:23:47.510 align:start position:0% information required in order to use them<05:23:45.540> operate<05:23:46.020> support<05:23:46.378> and<05:23:46.680> maintain<05:23:47.100> was 05:23:47.510 --> 05:23:47.520 align:start position:0% them operate support and maintain was 05:23:47.520 --> 05:23:50.510 align:start position:0% them operate support and maintain was only<05:23:48.180> known<05:23:48.420> to<05:23:48.600> a<05:23:48.780> few<05:23:48.900> people<05:23:49.020> at<05:23:49.320> the<05:23:49.440> time 05:23:50.510 --> 05:23:50.520 align:start position:0% only known to a few people at the time 05:23:50.520 --> 05:23:52.610 align:start position:0% only known to a few people at the time so<05:23:51.000> Bob<05:23:51.180> actually<05:23:51.540> changed<05:23:52.080> the<05:23:52.200> name<05:23:52.320> of<05:23:52.440> his 05:23:52.610 --> 05:23:52.620 align:start position:0% so Bob actually changed the name of his 05:23:52.620 --> 05:23:55.910 align:start position:0% so Bob actually changed the name of his first<05:23:52.798> network<05:23:53.100> from<05:23:53.760> alto<05:23:54.480> Alor<05:23:55.020> Network<05:23:55.440> to 05:23:55.910 --> 05:23:55.920 align:start position:0% first network from alto Alor Network to 05:23:55.920 --> 05:23:58.490 align:start position:0% first network from alto Alor Network to ethernet<05:23:56.600> thankfully<05:23:57.600> otherwise<05:23:58.080> would<05:23:58.320> all 05:23:58.490 --> 05:23:58.500 align:start position:0% ethernet thankfully otherwise would all 05:23:58.500 --> 05:24:02.570 align:start position:0% ethernet thankfully otherwise would all be<05:23:58.620> referred<05:23:59.040> to<05:23:59.100> it<05:23:59.340> as<05:23:59.638> alto<05:24:00.600> Aloha<05:24:01.500> which<05:24:02.100> um 05:24:02.570 --> 05:24:02.580 align:start position:0% be referred to it as alto Aloha which um 05:24:02.580 --> 05:24:05.448 align:start position:0% be referred to it as alto Aloha which um be<05:24:03.120> a<05:24:03.240> bit<05:24:03.360> strange 05:24:05.448 --> 05:24:05.458 align:start position:0% be a bit strange 05:24:05.458 --> 05:24:09.350 align:start position:0% be a bit strange why<05:24:06.120> the<05:24:06.298> name<05:24:06.540> he<05:24:07.560> um<05:24:07.920> Bob's<05:24:08.760> experimental 05:24:09.350 --> 05:24:09.360 align:start position:0% why the name he um Bob's experimental 05:24:09.360 --> 05:24:11.208 align:start position:0% why the name he um Bob's experimental Network<05:24:09.480> the<05:24:09.840> physical<05:24:10.020> medium 05:24:11.208 --> 05:24:11.218 align:start position:0% Network the physical medium 05:24:11.218 --> 05:24:14.448 align:start position:0% Network the physical medium or<05:24:12.000> the<05:24:12.120> cable<05:24:12.360> to<05:24:13.020> carry<05:24:13.320> out<05:24:13.440> all<05:24:13.620> the<05:24:13.798> bits 05:24:14.448 --> 05:24:14.458 align:start position:0% or the cable to carry out all the bits 05:24:14.458 --> 05:24:16.430 align:start position:0% or the cable to carry out all the bits to<05:24:14.940> describe<05:24:15.240> the<05:24:15.420> important<05:24:15.780> feature<05:24:16.138> Bob 05:24:16.430 --> 05:24:16.440 align:start position:0% to describe the important feature Bob 05:24:16.440 --> 05:24:18.050 align:start position:0% to describe the important feature Bob named<05:24:16.860> the<05:24:16.920> network<05:24:17.160> based<05:24:17.700> on<05:24:17.820> the<05:24:17.940> word 05:24:18.050 --> 05:24:18.060 align:start position:0% named the network based on the word 05:24:18.060 --> 05:24:19.070 align:start position:0% named the network based on the word ether 05:24:19.070 --> 05:24:19.080 align:start position:0% ether 05:24:19.080 --> 05:24:22.910 align:start position:0% ether the<05:24:19.680> old<05:24:20.218> um<05:24:20.218> luminous<05:24:21.260> lumini<05:24:22.260> Ferrera 05:24:22.910 --> 05:24:22.920 align:start position:0% the old um luminous lumini Ferrera 05:24:22.920 --> 05:24:24.890 align:start position:0% the old um luminous lumini Ferrera Ferris<05:24:23.340> ether<05:24:23.940> was<05:24:24.180> once<05:24:24.420> considered<05:24:24.780> the 05:24:24.890 --> 05:24:24.900 align:start position:0% Ferris ether was once considered the 05:24:24.900 --> 05:24:27.550 align:start position:0% Ferris ether was once considered the medium<05:24:25.260> for<05:24:25.980> the<05:24:26.160> propagation<05:24:26.760> of 05:24:27.550 --> 05:24:27.560 align:start position:0% medium for the propagation of 05:24:27.560 --> 05:24:30.170 align:start position:0% medium for the propagation of electromagnetic<05:24:28.560> waves 05:24:30.170 --> 05:24:30.180 align:start position:0% electromagnetic waves 05:24:30.180 --> 05:24:33.110 align:start position:0% electromagnetic waves so<05:24:30.420> there<05:24:30.660> are<05:24:30.840> some<05:24:31.020> mythical<05:24:31.820> background<05:24:32.820> in 05:24:33.110 --> 05:24:33.120 align:start position:0% so there are some mythical background in 05:24:33.120 --> 05:24:34.850 align:start position:0% so there are some mythical background in it 05:24:34.850 --> 05:24:34.860 align:start position:0% it 05:24:34.860 --> 05:24:37.430 align:start position:0% it and<05:24:35.580> first<05:24:35.820> standardized<05:24:36.360> by<05:24:36.600> the<05:24:36.780> Consortium 05:24:37.430 --> 05:24:37.440 align:start position:0% and first standardized by the Consortium 05:24:37.440 --> 05:24:41.750 align:start position:0% and first standardized by the Consortium of<05:24:37.740> deck<05:24:38.160> Intel<05:24:38.700> Xerox<05:24:39.298> or<05:24:40.020> Dix 05:24:41.750 --> 05:24:41.760 align:start position:0% of deck Intel Xerox or Dix 05:24:41.760 --> 05:24:45.850 align:start position:0% of deck Intel Xerox or Dix later<05:24:42.360> actually<05:24:42.718> standardized<05:24:43.320> by<05:24:43.500> the<05:24:43.680> IEEE 05:24:45.850 --> 05:24:45.860 align:start position:0% later actually standardized by the IEEE 05:24:45.860 --> 05:24:48.050 align:start position:0% later actually standardized by the IEEE standards<05:24:46.860> defined<05:24:47.218> several<05:24:47.520> aspects<05:24:47.940> that 05:24:48.050 --> 05:24:48.060 align:start position:0% standards defined several aspects that 05:24:48.060 --> 05:24:50.270 align:start position:0% standards defined several aspects that make<05:24:48.240> data<05:24:48.718> transmission<05:24:49.020> possible<05:24:49.798> this<05:24:50.160> is 05:24:50.270 --> 05:24:50.280 align:start position:0% make data transmission possible this is 05:24:50.280 --> 05:24:51.830 align:start position:0% make data transmission possible this is their<05:24:50.520> job 05:24:51.830 --> 05:24:51.840 align:start position:0% their job 05:24:51.840 --> 05:24:54.050 align:start position:0% their job term<05:24:52.378> ethernet<05:24:52.740> is<05:24:53.040> used<05:24:53.160> to<05:24:53.280> refer<05:24:53.580> to<05:24:53.700> both 05:24:54.050 --> 05:24:54.060 align:start position:0% term ethernet is used to refer to both 05:24:54.060 --> 05:24:56.270 align:start position:0% term ethernet is used to refer to both the<05:24:54.360> original<05:24:54.480> Dix<05:24:55.138> ethernet<05:24:55.740> which<05:24:56.040> we'll 05:24:56.270 --> 05:24:56.280 align:start position:0% the original Dix ethernet which we'll 05:24:56.280 --> 05:24:58.610 align:start position:0% the original Dix ethernet which we'll rarely<05:24:56.580> talk<05:24:56.820> about<05:24:57.000> unless<05:24:57.420> we're<05:24:57.600> doing<05:24:57.780> and 05:24:58.610 --> 05:24:58.620 align:start position:0% rarely talk about unless we're doing and 05:24:58.620 --> 05:25:01.330 align:start position:0% rarely talk about unless we're doing and talking<05:24:58.798> in<05:24:59.100> the<05:24:59.280> context<05:24:59.520> of<05:24:59.760> exams<05:25:00.298> and<05:25:00.958> the 05:25:01.330 --> 05:25:01.340 align:start position:0% talking in the context of exams and the 05:25:01.340 --> 05:25:04.390 align:start position:0% talking in the context of exams and the 802.3<05:25:02.340> specification<05:25:03.240> which<05:25:03.660> specifies 05:25:04.390 --> 05:25:04.400 align:start position:0% 802.3 specification which specifies 05:25:04.400 --> 05:25:08.810 align:start position:0% 802.3 specification which specifies ethernet<05:25:05.400> old<05:25:06.000> and<05:25:06.360> new 05:25:08.810 --> 05:25:08.820 align:start position:0% 05:25:08.820 --> 05:25:11.270 align:start position:0% so<05:25:09.180> 802.3<05:25:10.138> is<05:25:10.320> an<05:25:10.500> international<05:25:10.620> standard 05:25:11.270 --> 05:25:11.280 align:start position:0% so 802.3 is an international standard 05:25:11.280 --> 05:25:13.670 align:start position:0% so 802.3 is an international standard for<05:25:11.520> local<05:25:11.700> area<05:25:11.940> networks<05:25:12.600> and<05:25:12.958> metropolitan 05:25:13.670 --> 05:25:13.680 align:start position:0% for local area networks and metropolitan 05:25:13.680 --> 05:25:16.190 align:start position:0% for local area networks and metropolitan area<05:25:13.798> networks<05:25:14.400> that<05:25:15.060> employs<05:25:15.420> the<05:25:15.840> carrier 05:25:16.190 --> 05:25:16.200 align:start position:0% area networks that employs the carrier 05:25:16.200 --> 05:25:18.350 align:start position:0% area networks that employs the carrier sensor<05:25:16.560> multiple<05:25:16.920> access<05:25:17.100> with<05:25:17.760> Collision 05:25:18.350 --> 05:25:18.360 align:start position:0% sensor multiple access with Collision 05:25:18.360 --> 05:25:20.030 align:start position:0% sensor multiple access with Collision detection 05:25:20.030 --> 05:25:20.040 align:start position:0% detection 05:25:20.040 --> 05:25:23.150 align:start position:0% detection the<05:25:20.638> ethernet<05:25:20.940> protocol<05:25:21.540> frame<05:25:22.080> format<05:25:22.560> for 05:25:23.150 --> 05:25:23.160 align:start position:0% the ethernet protocol frame format for 05:25:23.160 --> 05:25:24.830 align:start position:0% the ethernet protocol frame format for communication 05:25:24.830 --> 05:25:24.840 align:start position:0% communication 05:25:24.840 --> 05:25:27.288 align:start position:0% communication the<05:25:25.260> IEEE<05:25:25.920> is<05:25:26.100> the<05:25:26.218> institute<05:25:26.520> for<05:25:26.760> electrical 05:25:27.288 --> 05:25:27.298 align:start position:0% the IEEE is the institute for electrical 05:25:27.298 --> 05:25:29.990 align:start position:0% the IEEE is the institute for electrical and<05:25:27.600> electronic<05:25:28.320> engineers 05:25:29.990 --> 05:25:30.000 align:start position:0% and electronic engineers 05:25:30.000 --> 05:25:34.250 align:start position:0% and electronic engineers uh<05:25:30.660> largest<05:25:31.020> Professional<05:25:31.560> Association 05:25:34.250 --> 05:25:34.260 align:start position:0% uh largest Professional Association 05:25:34.260 --> 05:25:38.510 align:start position:0% uh largest Professional Association um<05:25:34.320> for<05:25:34.980> the<05:25:35.160> advancement<05:25:35.458> of<05:25:35.760> Technology 05:25:38.510 --> 05:25:38.520 align:start position:0% 05:25:38.520 --> 05:25:41.930 align:start position:0% it<05:25:39.000> has<05:25:39.180> more<05:25:39.480> than<05:25:39.718> uh<05:25:40.378> 400<05:25:41.340> 000<05:25:41.458> members 05:25:41.930 --> 05:25:41.940 align:start position:0% it has more than uh 400 000 members 05:25:41.940 --> 05:25:46.128 align:start position:0% it has more than uh 400 000 members spanning<05:25:42.660> 100<05:25:42.958> and<05:25:43.378> more<05:25:43.740> than<05:25:43.920> 160<05:25:44.520> countries 05:25:46.128 --> 05:25:46.138 align:start position:0% spanning 100 and more than 160 countries 05:25:46.138 --> 05:25:48.288 align:start position:0% spanning 100 and more than 160 countries so<05:25:46.620> what<05:25:46.740> do<05:25:46.920> they<05:25:47.040> do 05:25:48.288 --> 05:25:48.298 align:start position:0% so what do they do 05:25:48.298 --> 05:25:51.350 align:start position:0% so what do they do they<05:25:49.138> provide<05:25:49.500> Society<05:25:50.160> Publications<05:25:50.760> they 05:25:51.350 --> 05:25:51.360 align:start position:0% they provide Society Publications they 05:25:51.360 --> 05:25:53.750 align:start position:0% they provide Society Publications they develop<05:25:51.718> on<05:25:52.020> new<05:25:52.620> and<05:25:52.980> emerging<05:25:53.340> technology 05:25:53.750 --> 05:25:53.760 align:start position:0% develop on new and emerging technology 05:25:53.760 --> 05:25:55.850 align:start position:0% develop on new and emerging technology standards<05:25:54.420> they<05:25:54.958> also<05:25:55.200> have<05:25:55.260> conferences 05:25:55.850 --> 05:25:55.860 align:start position:0% standards they also have conferences 05:25:55.860 --> 05:25:57.650 align:start position:0% standards they also have conferences that<05:25:56.160> various<05:25:56.520> Network<05:25:56.760> Engineers<05:25:57.360> can 05:25:57.650 --> 05:25:57.660 align:start position:0% that various Network Engineers can 05:25:57.660 --> 05:26:01.550 align:start position:0% that various Network Engineers can attend<05:25:58.100> to<05:25:59.100> swap<05:25:59.700> ideas<05:25:59.958> and<05:26:00.958> Advance<05:26:01.138> the 05:26:01.550 --> 05:26:01.560 align:start position:0% attend to swap ideas and Advance the 05:26:01.560 --> 05:26:03.530 align:start position:0% attend to swap ideas and Advance the technology 05:26:03.530 --> 05:26:03.540 align:start position:0% technology 05:26:03.540 --> 05:26:06.230 align:start position:0% technology uh<05:26:04.320> fortunately<05:26:04.740> I'm<05:26:04.980> not<05:26:05.458> um<05:26:05.458> this<05:26:05.940> the 05:26:06.230 --> 05:26:06.240 align:start position:0% uh fortunately I'm not um this the 05:26:06.240 --> 05:26:08.570 align:start position:0% uh fortunately I'm not um this the points<05:26:07.138> aren't<05:26:07.378> sliding<05:26:07.860> in<05:26:07.980> as<05:26:08.218> they<05:26:08.400> should 05:26:08.570 --> 05:26:08.580 align:start position:0% points aren't sliding in as they should 05:26:08.580 --> 05:26:10.430 align:start position:0% points aren't sliding in as they should be<05:26:08.760> so<05:26:09.600> um<05:26:09.600> all<05:26:09.840> the<05:26:10.020> information<05:26:10.138> is 05:26:10.430 --> 05:26:10.440 align:start position:0% be so um all the information is 05:26:10.440 --> 05:26:12.530 align:start position:0% be so um all the information is appearing<05:26:10.860> at<05:26:11.040> the<05:26:11.160> same<05:26:11.280> time<05:26:11.400> sorry 05:26:12.530 --> 05:26:12.540 align:start position:0% appearing at the same time sorry 05:26:12.540 --> 05:26:14.628 align:start position:0% appearing at the same time sorry so<05:26:12.900> the<05:26:13.020> ieee's<05:26:13.740> leading<05:26:14.100> developer<05:26:14.458> of 05:26:14.628 --> 05:26:14.638 align:start position:0% so the ieee's leading developer of 05:26:14.638 --> 05:26:17.030 align:start position:0% so the ieee's leading developer of international<05:26:14.820> standards<05:26:15.718> they<05:26:16.500> include<05:26:16.798> the 05:26:17.030 --> 05:26:17.040 align:start position:0% international standards they include the 05:26:17.040 --> 05:26:19.670 align:start position:0% international standards they include the 802<05:26:17.700> standards<05:26:18.240> which<05:26:18.480> are<05:26:18.660> for<05:26:18.900> lands<05:26:19.560> and 05:26:19.670 --> 05:26:19.680 align:start position:0% 802 standards which are for lands and 05:26:19.680 --> 05:26:22.610 align:start position:0% 802 standards which are for lands and mans<05:26:20.160> and<05:26:21.120> wireless<05:26:21.420> local<05:26:21.780> area<05:26:22.080> networks 05:26:22.610 --> 05:26:22.620 align:start position:0% mans and wireless local area networks 05:26:22.620 --> 05:26:24.770 align:start position:0% mans and wireless local area networks also<05:26:22.980> which<05:26:23.520> will<05:26:23.700> refer<05:26:24.060> to<05:26:24.180> usually<05:26:24.600> as 05:26:24.770 --> 05:26:24.780 align:start position:0% also which will refer to usually as 05:26:24.780 --> 05:26:27.050 align:start position:0% also which will refer to usually as Wi-Fi<05:26:25.200> you'll<05:26:25.860> see<05:26:26.040> the<05:26:26.218> little<05:26:26.340> stickers<05:26:26.820> on 05:26:27.050 --> 05:26:27.060 align:start position:0% Wi-Fi you'll see the little stickers on 05:26:27.060 --> 05:26:30.110 align:start position:0% Wi-Fi you'll see the little stickers on Wi-Fi<05:26:27.360> devices<05:26:27.900> and<05:26:28.860> when<05:26:29.100> you<05:26:29.218> go<05:26:29.400> to<05:26:29.520> cafes 05:26:30.110 --> 05:26:30.120 align:start position:0% Wi-Fi devices and when you go to cafes 05:26:30.120 --> 05:26:32.628 align:start position:0% Wi-Fi devices and when you go to cafes they<05:26:30.360> may<05:26:30.540> well<05:26:30.718> have<05:26:30.900> a<05:26:31.138> Wi-Fi<05:26:31.440> sticker<05:26:31.980> to 05:26:32.628 --> 05:26:32.638 align:start position:0% they may well have a Wi-Fi sticker to 05:26:32.638 --> 05:26:36.170 align:start position:0% they may well have a Wi-Fi sticker to say<05:26:32.820> them<05:26:33.240> they<05:26:33.660> give<05:26:33.900> a<05:26:34.260> wireless<05:26:34.798> access 05:26:36.170 --> 05:26:36.180 align:start position:0% say them they give a wireless access 05:26:36.180 --> 05:26:38.890 align:start position:0% say them they give a wireless access and<05:26:37.020> so<05:26:37.260> ethernet's<05:26:37.920> the<05:26:38.040> most<05:26:38.160> popular<05:26:38.340> today 05:26:38.890 --> 05:26:38.900 align:start position:0% and so ethernet's the most popular today 05:26:38.900 --> 05:26:41.030 align:start position:0% and so ethernet's the most popular today it's<05:26:39.900> everywhere<05:26:40.378> basically<05:26:40.798> making 05:26:41.030 --> 05:26:41.040 align:start position:0% it's everywhere basically making 05:26:41.040 --> 05:26:43.490 align:start position:0% it's everywhere basically making communication<05:26:41.820> possible<05:26:42.540> for<05:26:43.080> pretty<05:26:43.378> much 05:26:43.490 --> 05:26:43.500 align:start position:0% communication possible for pretty much 05:26:43.500 --> 05:26:47.690 align:start position:0% communication possible for pretty much everyone<05:26:44.000> and<05:26:45.000> mainly<05:26:45.780> popular<05:26:46.200> because<05:26:46.680> of 05:26:47.690 --> 05:26:47.700 align:start position:0% everyone and mainly popular because of 05:26:47.700 --> 05:26:50.390 align:start position:0% everyone and mainly popular because of um the<05:26:48.060> fact<05:26:48.180> is<05:26:48.360> economical<05:26:48.900> to<05:26:49.138> use<05:26:49.378> it<05:26:50.100> uses 05:26:50.390 --> 05:26:50.400 align:start position:0% um the fact is economical to use it uses 05:26:50.400 --> 05:26:52.788 align:start position:0% um the fact is economical to use it uses high<05:26:50.638> speed<05:26:50.878> it's<05:26:51.180> reliable<05:26:51.718> and<05:26:52.440> it's<05:26:52.560> easy 05:26:52.788 --> 05:26:52.798 align:start position:0% high speed it's reliable and it's easy 05:26:52.798 --> 05:26:55.670 align:start position:0% high speed it's reliable and it's easy to<05:26:53.218> install<05:26:53.458> and<05:26:53.820> maintain<05:26:54.180> also<05:26:55.080> free<05:26:55.260> to<05:26:55.500> use 05:26:55.670 --> 05:26:55.680 align:start position:0% to install and maintain also free to use 05:26:55.680 --> 05:26:57.050 align:start position:0% to install and maintain also free to use the<05:26:55.920> standards 05:26:57.050 --> 05:26:57.060 align:start position:0% the standards 05:26:57.060 --> 05:27:01.368 align:start position:0% the standards um<05:26:57.120> like<05:26:57.420> TCP<05:26:58.218> if<05:26:59.218> you<05:26:59.400> used<05:26:59.638> a<05:27:00.420> custom 05:27:01.368 --> 05:27:01.378 align:start position:0% um like TCP if you used a custom 05:27:01.378 --> 05:27:04.730 align:start position:0% um like TCP if you used a custom Solution<05:27:02.100> by<05:27:02.638> another 05:27:04.730 --> 05:27:04.740 align:start position:0% Solution by another 05:27:04.740 --> 05:27:07.070 align:start position:0% Solution by another um Creator<05:27:05.638> then<05:27:06.298> you'd<05:27:06.480> obviously<05:27:06.780> have<05:27:06.900> to 05:27:07.070 --> 05:27:07.080 align:start position:0% um Creator then you'd obviously have to 05:27:07.080 --> 05:27:09.530 align:start position:0% um Creator then you'd obviously have to pay<05:27:07.440> to<05:27:07.680> use<05:27:07.920> all<05:27:08.218> of<05:27:08.400> their 05:27:09.530 --> 05:27:09.540 align:start position:0% pay to use all of their 05:27:09.540 --> 05:27:11.930 align:start position:0% pay to use all of their um specifications<05:27:10.440> and<05:27:10.860> standards 05:27:11.930 --> 05:27:11.940 align:start position:0% um specifications and standards 05:27:11.940 --> 05:27:14.150 align:start position:0% um specifications and standards so<05:27:12.480> the<05:27:12.660> early<05:27:12.780> ethernet<05:27:13.260> run<05:27:13.440> over<05:27:13.620> what<05:27:13.980> was 05:27:14.150 --> 05:27:14.160 align:start position:0% so the early ethernet run over what was 05:27:14.160 --> 05:27:16.910 align:start position:0% so the early ethernet run over what was known<05:27:14.340> as<05:27:14.520> coaxial<05:27:15.120> cables 05:27:16.910 --> 05:27:16.920 align:start position:0% known as coaxial cables 05:27:16.920 --> 05:27:18.830 align:start position:0% known as coaxial cables um<05:27:17.040> modern<05:27:17.400> ethernet<05:27:17.820> don't<05:27:18.298> do<05:27:18.480> that<05:27:18.660> anymore 05:27:18.830 --> 05:27:18.840 align:start position:0% um modern ethernet don't do that anymore 05:27:18.840 --> 05:27:20.930 align:start position:0% um modern ethernet don't do that anymore because<05:27:19.260> of<05:27:19.440> the<05:27:19.560> limitations<05:27:20.040> of<05:27:20.400> speed<05:27:20.700> and 05:27:20.930 --> 05:27:20.940 align:start position:0% because of the limitations of speed and 05:27:20.940 --> 05:27:23.330 align:start position:0% because of the limitations of speed and troubleshooting<05:27:21.718> they<05:27:22.620> use<05:27:22.798> a<05:27:22.920> mixture<05:27:23.218> of 05:27:23.330 --> 05:27:23.340 align:start position:0% troubleshooting they use a mixture of 05:27:23.340 --> 05:27:26.990 align:start position:0% troubleshooting they use a mixture of copper<05:27:23.700> and<05:27:24.000> fiber<05:27:24.540> depending<05:27:25.440> on<05:27:26.400> um<05:27:26.400> the 05:27:26.990 --> 05:27:27.000 align:start position:0% copper and fiber depending on um the 05:27:27.000 --> 05:27:29.868 align:start position:0% copper and fiber depending on um the location<05:27:27.180> and<05:27:27.840> how<05:27:28.138> much<05:27:28.340> what<05:27:29.340> the<05:27:29.458> budgets 05:27:29.868 --> 05:27:29.878 align:start position:0% location and how much what the budgets 05:27:29.878 --> 05:27:32.448 align:start position:0% location and how much what the budgets of<05:27:29.940> the<05:27:30.120> various<05:27:30.420> devices<05:27:30.840> or 05:27:32.448 --> 05:27:32.458 align:start position:0% of the various devices or 05:27:32.458 --> 05:27:35.570 align:start position:0% of the various devices or um<05:27:32.580> local<05:27:33.000> government<05:27:33.298> authorities<05:27:33.958> have 05:27:35.570 --> 05:27:35.580 align:start position:0% um local government authorities have 05:27:35.580 --> 05:27:38.150 align:start position:0% um local government authorities have based<05:27:36.240> on<05:27:36.298> broadband<05:27:37.080> is<05:27:37.620> the<05:27:38.040> term 05:27:38.150 --> 05:27:38.160 align:start position:0% based on broadband is the term 05:27:38.160 --> 05:27:41.208 align:start position:0% based on broadband is the term synonymous<05:27:38.878> with<05:27:39.360> ethernet<05:27:39.900> the<05:27:40.798> band<05:27:40.980> is 05:27:41.208 --> 05:27:41.218 align:start position:0% synonymous with ethernet the band is 05:27:41.218 --> 05:27:43.850 align:start position:0% synonymous with ethernet the band is actually<05:27:41.458> referred<05:27:41.940> to<05:27:42.060> the<05:27:42.360> bandwidth<05:27:43.020> in 05:27:43.850 --> 05:27:43.860 align:start position:0% actually referred to the bandwidth in 05:27:43.860 --> 05:27:47.050 align:start position:0% actually referred to the bandwidth in context<05:27:44.160> of<05:27:44.400> the<05:27:44.638> transmission 05:27:47.050 --> 05:27:47.060 align:start position:0% 05:27:47.060 --> 05:27:49.910 align:start position:0% uh<05:27:48.060> Broadband<05:27:48.600> is<05:27:48.900> a<05:27:49.080> broadband<05:27:49.440> system<05:27:49.620> a 05:27:49.910 --> 05:27:49.920 align:start position:0% uh Broadband is a broadband system a 05:27:49.920 --> 05:27:51.948 align:start position:0% uh Broadband is a broadband system a whole<05:27:50.100> band<05:27:50.280> of<05:27:50.520> transmission<05:27:50.820> medium<05:27:51.540> is 05:27:51.948 --> 05:27:51.958 align:start position:0% whole band of transmission medium is 05:27:51.958 --> 05:27:53.930 align:start position:0% whole band of transmission medium is shared<05:27:52.320> dividing<05:27:52.980> it<05:27:53.100> into<05:27:53.218> pieces<05:27:53.638> called 05:27:53.930 --> 05:27:53.940 align:start position:0% shared dividing it into pieces called 05:27:53.940 --> 05:27:55.368 align:start position:0% shared dividing it into pieces called channels 05:27:55.368 --> 05:27:55.378 align:start position:0% channels 05:27:55.378 --> 05:27:57.590 align:start position:0% channels each<05:27:55.980> channel<05:27:56.218> will<05:27:56.580> have<05:27:56.760> the<05:27:56.940> portion<05:27:57.360> of 05:27:57.590 --> 05:27:57.600 align:start position:0% each channel will have the portion of 05:27:57.600 --> 05:28:00.410 align:start position:0% each channel will have the portion of the<05:27:57.840> whole<05:27:58.080> band<05:27:58.820> multiple<05:27:59.820> channels<05:28:00.240> will 05:28:00.410 --> 05:28:00.420 align:start position:0% the whole band multiple channels will 05:28:00.420 --> 05:28:02.690 align:start position:0% the whole band multiple channels will serve<05:28:00.660> as<05:28:00.958> multiple<05:28:01.378> signal<05:28:01.680> carriers<05:28:02.160> each 05:28:02.690 --> 05:28:02.700 align:start position:0% serve as multiple signal carriers each 05:28:02.700 --> 05:28:04.368 align:start position:0% serve as multiple signal carriers each carrying<05:28:03.120> its<05:28:03.420> own<05:28:03.480> data<05:28:03.900> on<05:28:04.080> the<05:28:04.260> same 05:28:04.368 --> 05:28:04.378 align:start position:0% carrying its own data on the same 05:28:04.378 --> 05:28:06.530 align:start position:0% carrying its own data on the same transmission<05:28:04.680> medium<05:28:05.458> so<05:28:05.940> basically<05:28:06.240> we're 05:28:06.530 --> 05:28:06.540 align:start position:0% transmission medium so basically we're 05:28:06.540 --> 05:28:10.310 align:start position:0% transmission medium so basically we're all<05:28:06.900> sharing<05:28:07.440> the<05:28:08.160> same<05:28:08.280> medium<05:28:08.900> and<05:28:09.900> the 05:28:10.310 --> 05:28:10.320 align:start position:0% all sharing the same medium and the 05:28:10.320 --> 05:28:12.288 align:start position:0% all sharing the same medium and the local<05:28:10.500> ratio<05:28:11.100> I<05:28:11.280> think<05:28:11.458> for<05:28:11.638> my<05:28:11.878> Broadband 05:28:12.288 --> 05:28:12.298 align:start position:0% local ratio I think for my Broadband 05:28:12.298 --> 05:28:14.270 align:start position:0% local ratio I think for my Broadband here<05:28:12.660> is 05:28:14.270 --> 05:28:14.280 align:start position:0% here is 05:28:14.280 --> 05:28:17.628 align:start position:0% here is um<05:28:14.400> 30<05:28:15.060> to<05:28:15.360> 1<05:28:15.718> so<05:28:16.200> 30<05:28:16.500> users<05:28:16.980> will<05:28:17.218> use<05:28:17.400> one 05:28:17.628 --> 05:28:17.638 align:start position:0% um 30 to 1 so 30 users will use one 05:28:17.638 --> 05:28:20.270 align:start position:0% um 30 to 1 so 30 users will use one connection<05:28:17.940> to<05:28:18.420> the<05:28:18.718> local 05:28:20.270 --> 05:28:20.280 align:start position:0% connection to the local 05:28:20.280 --> 05:28:22.190 align:start position:0% connection to the local um switch<05:28:20.878> provided<05:28:21.718> by<05:28:21.900> the<05:28:22.020> telephone 05:28:22.190 --> 05:28:22.200 align:start position:0% um switch provided by the telephone 05:28:22.200 --> 05:28:23.868 align:start position:0% um switch provided by the telephone company 05:28:23.868 --> 05:28:23.878 align:start position:0% company 05:28:23.878 --> 05:28:26.030 align:start position:0% company base<05:28:24.480> band<05:28:24.780> in<05:28:25.020> the<05:28:25.200> baseband<05:28:25.500> system<05:28:25.740> the 05:28:26.030 --> 05:28:26.040 align:start position:0% base band in the baseband system the 05:28:26.040 --> 05:28:27.650 align:start position:0% base band in the baseband system the entire<05:28:26.218> band<05:28:26.400> of<05:28:26.700> the<05:28:26.820> transmission<05:28:27.000> medium 05:28:27.650 --> 05:28:27.660 align:start position:0% entire band of the transmission medium 05:28:27.660 --> 05:28:31.250 align:start position:0% entire band of the transmission medium will<05:28:27.958> be<05:28:28.138> used<05:28:28.440> as<05:28:28.680> a<05:28:28.920> signal<05:28:29.218> carrier 05:28:31.250 --> 05:28:31.260 align:start position:0% will be used as a signal carrier 05:28:31.260 --> 05:28:33.650 align:start position:0% will be used as a signal carrier naming<05:28:32.160> conventions<05:28:32.700> the<05:28:33.420> ethernet 05:28:33.650 --> 05:28:33.660 align:start position:0% naming conventions the ethernet 05:28:33.660 --> 05:28:35.448 align:start position:0% naming conventions the ethernet standards<05:28:34.200> username<05:28:34.560> and<05:28:34.798> Convention<05:28:35.100> that 05:28:35.448 --> 05:28:35.458 align:start position:0% standards username and Convention that 05:28:35.458 --> 05:28:38.208 align:start position:0% standards username and Convention that houses<05:28:35.700> determine<05:28:36.540> a<05:28:36.780> few<05:28:36.900> things<05:28:37.138> the<05:28:38.040> speed 05:28:38.208 --> 05:28:38.218 align:start position:0% houses determine a few things the speed 05:28:38.218 --> 05:28:40.128 align:start position:0% houses determine a few things the speed of<05:28:38.458> the<05:28:38.580> transmission<05:28:38.820> the<05:28:39.420> signaling<05:28:39.900> type 05:28:40.128 --> 05:28:40.138 align:start position:0% of the transmission the signaling type 05:28:40.138 --> 05:28:42.288 align:start position:0% of the transmission the signaling type and<05:28:40.560> the<05:28:40.680> length<05:28:40.980> of<05:28:41.100> the<05:28:41.218> cable 05:28:42.288 --> 05:28:42.298 align:start position:0% and the length of the cable 05:28:42.298 --> 05:28:45.170 align:start position:0% and the length of the cable uh<05:28:42.958> cable<05:28:43.260> type<05:28:43.500> used<05:28:43.798> as<05:28:44.040> well<05:28:44.218> for<05:28:44.940> example 05:28:45.170 --> 05:28:45.180 align:start position:0% uh cable type used as well for example 05:28:45.180 --> 05:28:49.368 align:start position:0% uh cable type used as well for example 10<05:28:45.420> base<05:28:45.718> 5<05:28:46.138> really<05:28:46.860> old<05:28:47.458> standard<05:28:48.000> this<05:28:48.378> it 05:28:49.368 --> 05:28:49.378 align:start position:0% 10 base 5 really old standard this it 05:28:49.378 --> 05:28:54.230 align:start position:0% 10 base 5 really old standard this it was<05:28:49.500> been<05:28:49.740> phased<05:28:50.218> out<05:28:50.400> in<05:28:51.180> the<05:28:51.920> well<05:28:52.920> late<05:28:53.458> 90s 05:28:54.230 --> 05:28:54.240 align:start position:0% was been phased out in the well late 90s 05:28:54.240 --> 05:28:55.910 align:start position:0% was been phased out in the well late 90s I<05:28:54.480> think<05:28:54.600> when<05:28:54.900> I<05:28:55.080> was 05:28:55.910 --> 05:28:55.920 align:start position:0% I think when I was 05:28:55.920 --> 05:28:58.310 align:start position:0% I think when I was um<05:28:55.980> just<05:28:56.280> getting<05:28:56.400> into<05:28:56.638> networking<05:28:57.240> really 05:28:58.310 --> 05:28:58.320 align:start position:0% um just getting into networking really 05:28:58.320 --> 05:29:01.430 align:start position:0% um just getting into networking really so<05:28:59.040> 10<05:28:59.340> base<05:28:59.638> 5<05:29:00.000> is<05:29:00.420> named<05:29:00.780> for<05:29:00.958> the<05:29:01.080> following 05:29:01.430 --> 05:29:01.440 align:start position:0% so 10 base 5 is named for the following 05:29:01.440 --> 05:29:03.948 align:start position:0% so 10 base 5 is named for the following 10<05:29:02.100> is<05:29:02.340> the<05:29:02.520> transmission<05:29:02.760> speed<05:29:03.298> which<05:29:03.660> is<05:29:03.718> 10 05:29:03.948 --> 05:29:03.958 align:start position:0% 10 is the transmission speed which is 10 05:29:03.958 --> 05:29:05.150 align:start position:0% 10 is the transmission speed which is 10 Meg 05:29:05.150 --> 05:29:05.160 align:start position:0% Meg 05:29:05.160 --> 05:29:07.730 align:start position:0% Meg base<05:29:05.700> means<05:29:06.120> the<05:29:06.298> type<05:29:06.660> of<05:29:06.958> signal<05:29:07.378> in<05:29:07.500> his 05:29:07.730 --> 05:29:07.740 align:start position:0% base means the type of signal in his 05:29:07.740 --> 05:29:10.368 align:start position:0% base means the type of signal in his baseband<05:29:08.218> and<05:29:09.180> five<05:29:09.360> indicates<05:29:09.900> to<05:29:10.080> the<05:29:10.260> track 05:29:10.368 --> 05:29:10.378 align:start position:0% baseband and five indicates to the track 05:29:10.378 --> 05:29:12.890 align:start position:0% baseband and five indicates to the track the<05:29:10.740> maximum<05:29:11.040> length<05:29:11.400> of<05:29:11.520> the<05:29:11.638> cable<05:29:11.878> can<05:29:12.718> be 05:29:12.890 --> 05:29:12.900 align:start position:0% the maximum length of the cable can be 05:29:12.900 --> 05:29:15.890 align:start position:0% the maximum length of the cable can be up<05:29:13.020> to<05:29:13.200> 500<05:29:13.620> meters 05:29:15.890 --> 05:29:15.900 align:start position:0% up to 500 meters 05:29:15.900 --> 05:29:17.990 align:start position:0% up to 500 meters this<05:29:16.378> is<05:29:16.500> for<05:29:16.740> the<05:29:16.920> segments<05:29:17.580> you<05:29:17.700> could<05:29:17.878> have 05:29:17.990 --> 05:29:18.000 align:start position:0% this is for the segments you could have 05:29:18.000 --> 05:29:20.690 align:start position:0% this is for the segments you could have another<05:29:18.180> segment<05:29:18.600> after<05:29:18.840> 500<05:29:19.440> meters 05:29:20.690 --> 05:29:20.700 align:start position:0% another segment after 500 meters 05:29:20.700 --> 05:29:23.150 align:start position:0% another segment after 500 meters and<05:29:21.298> the<05:29:21.480> signal<05:29:21.780> would<05:29:21.958> all<05:29:22.260> have<05:29:22.500> to<05:29:22.620> be<05:29:22.798> a 05:29:23.150 --> 05:29:23.160 align:start position:0% and the signal would all have to be a 05:29:23.160 --> 05:29:26.810 align:start position:0% and the signal would all have to be a replenished 05:29:26.810 --> 05:29:26.820 align:start position:0% 05:29:26.820 --> 05:29:29.390 align:start position:0% okay<05:29:27.360> so<05:29:27.660> a<05:29:27.840> thousand<05:29:28.080> Base<05:29:28.260> TX<05:29:28.740> the<05:29:29.040> following 05:29:29.390 --> 05:29:29.400 align:start position:0% okay so a thousand Base TX the following 05:29:29.400 --> 05:29:32.628 align:start position:0% okay so a thousand Base TX the following is<05:29:29.820> true<05:29:30.360> a<05:29:30.958> thousand<05:29:31.260> indicates<05:29:31.920> uh<05:29:32.458> sorry 05:29:32.628 --> 05:29:32.638 align:start position:0% is true a thousand indicates uh sorry 05:29:32.638 --> 05:29:36.110 align:start position:0% is true a thousand indicates uh sorry 100<05:29:33.260> htx<05:29:34.260> 100<05:29:34.798> is<05:29:35.160> the<05:29:35.340> speed<05:29:35.520> which<05:29:35.820> is<05:29:35.940> 100 05:29:36.110 --> 05:29:36.120 align:start position:0% 100 htx 100 is the speed which is 100 05:29:36.120 --> 05:29:37.250 align:start position:0% 100 htx 100 is the speed which is 100 mag 05:29:37.250 --> 05:29:37.260 align:start position:0% mag 05:29:37.260 --> 05:29:39.830 align:start position:0% mag base<05:29:37.920> stands<05:29:38.400> for<05:29:38.458> baseband<05:29:38.878> again<05:29:39.180> T 05:29:39.830 --> 05:29:39.840 align:start position:0% base stands for baseband again T 05:29:39.840 --> 05:29:42.050 align:start position:0% base stands for baseband again T indicates<05:29:40.378> that<05:29:40.620> the<05:29:40.920> standard<05:29:41.400> is<05:29:41.520> twisted 05:29:42.050 --> 05:29:42.060 align:start position:0% indicates that the standard is twisted 05:29:42.060 --> 05:29:43.310 align:start position:0% indicates that the standard is twisted pair 05:29:43.310 --> 05:29:43.320 align:start position:0% pair 05:29:43.320 --> 05:29:46.190 align:start position:0% pair X<05:29:43.798> at<05:29:44.040> the<05:29:44.218> end<05:29:44.360> indicates<05:29:45.360> that<05:29:45.540> the<05:29:45.718> K<05:29:45.840> the 05:29:46.190 --> 05:29:46.200 align:start position:0% X at the end indicates that the K the 05:29:46.200 --> 05:29:48.708 align:start position:0% X at the end indicates that the K the cable<05:29:46.378> is<05:29:46.760> capable<05:29:47.760> of<05:29:48.060> full<05:29:48.240> duplex 05:29:48.708 --> 05:29:48.718 align:start position:0% cable is capable of full duplex 05:29:48.718 --> 05:29:52.788 align:start position:0% cable is capable of full duplex communication 05:29:52.788 --> 05:29:52.798 align:start position:0% 05:29:52.798 --> 05:29:56.090 align:start position:0% 10<05:29:53.040> base<05:29:53.340> 5<05:29:53.700> real<05:29:54.000> old<05:29:54.240> standard<05:29:54.660> again 05:29:56.090 --> 05:29:56.100 align:start position:0% 10 base 5 real old standard again 05:29:56.100 --> 05:29:58.490 align:start position:0% 10 base 5 real old standard again um<05:29:56.160> based<05:29:56.700> on<05:29:56.760> 802.3 05:29:58.490 --> 05:29:58.500 align:start position:0% um based on 802.3 05:29:58.500 --> 05:30:01.070 align:start position:0% um based on 802.3 the<05:29:59.040> original<05:29:59.160> standard<05:29:59.878> uses<05:30:00.660> a<05:30:00.900> thick 05:30:01.070 --> 05:30:01.080 align:start position:0% the original standard uses a thick 05:30:01.080 --> 05:30:03.830 align:start position:0% the original standard uses a thick coaxial<05:30:01.740> cable<05:30:01.980> as<05:30:02.218> its<05:30:02.520> physical<05:30:02.580> medium<05:30:03.240> it 05:30:03.830 --> 05:30:03.840 align:start position:0% coaxial cable as its physical medium it 05:30:03.840 --> 05:30:06.050 align:start position:0% coaxial cable as its physical medium it was<05:30:03.958> actually<05:30:04.080> called<05:30:04.378> thick<05:30:04.680> net<05:30:04.920> for<05:30:05.218> short 05:30:06.050 --> 05:30:06.060 align:start position:0% was actually called thick net for short 05:30:06.060 --> 05:30:08.930 align:start position:0% was actually called thick net for short and<05:30:07.020> you<05:30:07.620> can<05:30:07.680> see<05:30:07.860> the<05:30:07.980> picture<05:30:08.218> of<05:30:08.458> it<05:30:08.638> there 05:30:08.930 --> 05:30:08.940 align:start position:0% and you can see the picture of it there 05:30:08.940 --> 05:30:10.910 align:start position:0% and you can see the picture of it there to<05:30:09.298> actually<05:30:09.540> connecting<05:30:10.020> to<05:30:10.260> the<05:30:10.378> cable<05:30:10.560> use 05:30:10.910 --> 05:30:10.920 align:start position:0% to actually connecting to the cable use 05:30:10.920 --> 05:30:15.230 align:start position:0% to actually connecting to the cable use these<05:30:11.400> big<05:30:11.718> plastic<05:30:12.718> devices<05:30:13.680> uh<05:30:14.400> called<05:30:15.180> um 05:30:15.230 --> 05:30:15.240 align:start position:0% these big plastic devices uh called um 05:30:15.240 --> 05:30:17.448 align:start position:0% these big plastic devices uh called um vampire<05:30:16.138> Taps<05:30:16.620> and<05:30:16.920> they're<05:30:17.100> physically 05:30:17.448 --> 05:30:17.458 align:start position:0% vampire Taps and they're physically 05:30:17.458 --> 05:30:20.270 align:start position:0% vampire Taps and they're physically screwed<05:30:18.120> in<05:30:18.298> to<05:30:18.958> the<05:30:19.138> cable<05:30:19.378> and<05:30:19.620> pierced<05:30:20.100> it 05:30:20.270 --> 05:30:20.280 align:start position:0% screwed in to the cable and pierced it 05:30:20.280 --> 05:30:22.610 align:start position:0% screwed in to the cable and pierced it very<05:30:20.940> awkward<05:30:21.240> to<05:30:21.480> use<05:30:21.660> and<05:30:21.958> hard<05:30:22.378> to 05:30:22.610 --> 05:30:22.620 align:start position:0% very awkward to use and hard to 05:30:22.620 --> 05:30:26.090 align:start position:0% very awkward to use and hard to troubleshoot<05:30:23.160> it<05:30:24.060> ran<05:30:24.298> at<05:30:24.420> 10<05:30:24.600> Meg 05:30:26.090 --> 05:30:26.100 align:start position:0% troubleshoot it ran at 10 Meg 05:30:26.100 --> 05:30:29.390 align:start position:0% troubleshoot it ran at 10 Meg and<05:30:26.760> either<05:30:27.000> RGA<05:30:27.480> or<05:30:27.780> rg11<05:30:28.378> it<05:30:28.798> had<05:30:29.040> a<05:30:29.280> little 05:30:29.390 --> 05:30:29.400 align:start position:0% and either RGA or rg11 it had a little 05:30:29.400 --> 05:30:31.190 align:start position:0% and either RGA or rg11 it had a little resistors<05:30:29.940> on<05:30:30.120> the<05:30:30.240> end<05:30:30.360> to<05:30:30.660> stop<05:30:30.780> the<05:30:30.958> signal 05:30:31.190 --> 05:30:31.200 align:start position:0% resistors on the end to stop the signal 05:30:31.200 --> 05:30:32.750 align:start position:0% resistors on the end to stop the signal bouncing<05:30:31.680> off<05:30:31.798> the<05:30:31.980> back<05:30:32.100> of<05:30:32.218> the<05:30:32.340> cable<05:30:32.520> and 05:30:32.750 --> 05:30:32.760 align:start position:0% bouncing off the back of the cable and 05:30:32.760 --> 05:30:36.590 align:start position:0% bouncing off the back of the cable and coming<05:30:32.940> back<05:30:33.240> and<05:30:33.900> they<05:30:34.080> ran<05:30:34.320> at<05:30:34.500> 50<05:30:34.798> ohm<05:30:35.760> RG 05:30:36.590 --> 05:30:36.600 align:start position:0% coming back and they ran at 50 ohm RG 05:30:36.600 --> 05:30:39.770 align:start position:0% coming back and they ran at 50 ohm RG stands<05:30:37.560> for<05:30:37.620> radio<05:30:37.980> government 05:30:39.770 --> 05:30:39.780 align:start position:0% stands for radio government 05:30:39.780 --> 05:30:42.410 align:start position:0% stands for radio government standard<05:30:40.680> determ<05:30:41.218> is<05:30:41.280> a<05:30:41.458> type<05:30:41.580> of<05:30:41.820> coaxial 05:30:42.410 --> 05:30:42.420 align:start position:0% standard determ is a type of coaxial 05:30:42.420 --> 05:30:46.550 align:start position:0% standard determ is a type of coaxial cables<05:30:43.020> the<05:30:43.320> distance<05:30:43.500> was<05:30:44.100> up<05:30:44.400> to<05:30:44.638> 500<05:30:45.180> meters 05:30:46.550 --> 05:30:46.560 align:start position:0% cables the distance was up to 500 meters 05:30:46.560 --> 05:30:48.830 align:start position:0% cables the distance was up to 500 meters there<05:30:47.100> were<05:30:47.160> a<05:30:47.340> few<05:30:47.458> pros<05:30:47.820> and<05:30:47.940> cons<05:30:48.120> to<05:30:48.420> using 05:30:48.830 --> 05:30:48.840 align:start position:0% there were a few pros and cons to using 05:30:48.840 --> 05:30:51.050 align:start position:0% there were a few pros and cons to using thick<05:30:49.138> net 05:30:51.050 --> 05:30:51.060 align:start position:0% thick net 05:30:51.060 --> 05:30:53.050 align:start position:0% thick net you<05:30:51.780> have<05:30:52.020> protection<05:30:52.260> against 05:30:53.050 --> 05:30:53.060 align:start position:0% you have protection against 05:30:53.060 --> 05:30:55.368 align:start position:0% you have protection against electromagnetic<05:30:54.060> interference<05:30:54.718> which<05:30:55.080> can 05:30:55.368 --> 05:30:55.378 align:start position:0% electromagnetic interference which can 05:30:55.378 --> 05:30:57.670 align:start position:0% electromagnetic interference which can seriously<05:30:55.798> degrade<05:30:56.218> your<05:30:56.400> signal 05:30:57.670 --> 05:30:57.680 align:start position:0% seriously degrade your signal 05:30:57.680 --> 05:30:59.570 align:start position:0% seriously degrade your signal disadvantage<05:30:58.680> there<05:30:58.920> was<05:30:59.040> loads<05:30:59.400> actually 05:30:59.570 --> 05:30:59.580 align:start position:0% disadvantage there was loads actually 05:30:59.580 --> 05:31:01.610 align:start position:0% disadvantage there was loads actually difficult<05:31:00.060> to<05:31:00.298> work<05:31:00.540> with<05:31:00.780> very<05:31:01.080> difficult<05:31:01.440> to 05:31:01.610 --> 05:31:01.620 align:start position:0% difficult to work with very difficult to 05:31:01.620 --> 05:31:04.490 align:start position:0% difficult to work with very difficult to troubleshoot<05:31:02.280> cable<05:31:03.000> was<05:31:03.298> very<05:31:03.600> thick<05:31:04.020> so 05:31:04.490 --> 05:31:04.500 align:start position:0% troubleshoot cable was very thick so 05:31:04.500 --> 05:31:06.530 align:start position:0% troubleshoot cable was very thick so trying<05:31:04.798> to<05:31:04.980> expand<05:31:05.700> it<05:31:05.878> around<05:31:06.060> an<05:31:06.360> office 05:31:06.530 --> 05:31:06.540 align:start position:0% trying to expand it around an office 05:31:06.540 --> 05:31:07.730 align:start position:0% trying to expand it around an office without 05:31:07.730 --> 05:31:07.740 align:start position:0% without 05:31:07.740 --> 05:31:09.770 align:start position:0% without and<05:31:08.280> people<05:31:08.458> tripping<05:31:09.000> over<05:31:09.120> or<05:31:09.360> hitting<05:31:09.600> the 05:31:09.770 --> 05:31:09.780 align:start position:0% and people tripping over or hitting the 05:31:09.780 --> 05:31:12.410 align:start position:0% and people tripping over or hitting the head<05:31:09.900> off<05:31:10.080> them<05:31:10.200> was<05:31:10.440> quite<05:31:10.620> awkward<05:31:10.980> as<05:31:11.280> well 05:31:12.410 --> 05:31:12.420 align:start position:0% head off them was quite awkward as well 05:31:12.420 --> 05:31:15.708 align:start position:0% head off them was quite awkward as well thin<05:31:13.020> net<05:31:13.200> is<05:31:14.100> based<05:31:14.580> on<05:31:14.820> the<05:31:15.000> 10<05:31:15.180> base<05:31:15.480> 2 05:31:15.708 --> 05:31:15.718 align:start position:0% thin net is based on the 10 base 2 05:31:15.718 --> 05:31:17.030 align:start position:0% thin net is based on the 10 base 2 standard 05:31:17.030 --> 05:31:17.040 align:start position:0% standard 05:31:17.040 --> 05:31:18.890 align:start position:0% standard so<05:31:17.458> 10<05:31:17.760> Meg 05:31:18.890 --> 05:31:18.900 align:start position:0% so 10 Meg 05:31:18.900 --> 05:31:20.030 align:start position:0% so 10 Meg um 05:31:20.030 --> 05:31:20.040 align:start position:0% um 05:31:20.040 --> 05:31:23.208 align:start position:0% um baseband<05:31:20.820> and<05:31:21.420> two<05:31:21.840> stands<05:31:22.320> for<05:31:22.440> how<05:31:22.680> long<05:31:22.860> the 05:31:23.208 --> 05:31:23.218 align:start position:0% baseband and two stands for how long the 05:31:23.218 --> 05:31:25.010 align:start position:0% baseband and two stands for how long the and<05:31:23.700> you<05:31:24.000> could<05:31:24.120> get<05:31:24.298> the<05:31:24.420> connection<05:31:24.600> which 05:31:25.010 --> 05:31:25.020 align:start position:0% and you could get the connection which 05:31:25.020 --> 05:31:29.330 align:start position:0% and you could get the connection which is<05:31:25.080> 200<05:31:25.500> meters 05:31:29.330 --> 05:31:29.340 align:start position:0% 05:31:29.340 --> 05:31:31.850 align:start position:0% was<05:31:29.820> actually<05:31:30.060> 185<05:31:30.718> was<05:31:30.958> recommended<05:31:31.440> but<05:31:31.680> you 05:31:31.850 --> 05:31:31.860 align:start position:0% was actually 185 was recommended but you 05:31:31.860 --> 05:31:34.310 align:start position:0% was actually 185 was recommended but you couldn't<05:31:31.980> you<05:31:32.700> couldn't<05:31:32.820> ensure<05:31:33.180> to<05:31:33.420> 185<05:31:34.020> so 05:31:34.310 --> 05:31:34.320 align:start position:0% couldn't you couldn't ensure to 185 so 05:31:34.320 --> 05:31:38.448 align:start position:0% couldn't you couldn't ensure to 185 so they<05:31:34.500> called<05:31:34.620> it<05:31:34.798> 10<05:31:34.980> base<05:31:35.218> 2. 05:31:38.448 --> 05:31:38.458 align:start position:0% 05:31:38.458 --> 05:31:40.610 align:start position:0% uh<05:31:39.240> being<05:31:39.480> cheaper<05:31:39.840> than<05:31:39.900> thick<05:31:40.138> Navy<05:31:40.378> was 05:31:40.610 --> 05:31:40.620 align:start position:0% uh being cheaper than thick Navy was 05:31:40.620 --> 05:31:42.170 align:start position:0% uh being cheaper than thick Navy was called<05:31:40.798> cheaper<05:31:41.458> net 05:31:42.170 --> 05:31:42.180 align:start position:0% called cheaper net 05:31:42.180 --> 05:31:44.810 align:start position:0% called cheaper net before<05:31:42.718> we<05:31:42.958> had<05:31:43.138> any<05:31:43.440> type<05:31:43.798> of<05:31:43.980> network<05:31:44.218> and<05:31:44.638> we 05:31:44.810 --> 05:31:44.820 align:start position:0% before we had any type of network and we 05:31:44.820 --> 05:31:47.030 align:start position:0% before we had any type of network and we used<05:31:44.940> to<05:31:45.060> use<05:31:45.298> floppy<05:31:46.020> disks 05:31:47.030 --> 05:31:47.040 align:start position:0% used to use floppy disks 05:31:47.040 --> 05:31:48.890 align:start position:0% used to use floppy disks big<05:31:47.520> thick<05:31:47.820> floppy<05:31:48.180> disks<05:31:48.480> not<05:31:48.600> even<05:31:48.718> the 05:31:48.890 --> 05:31:48.900 align:start position:0% big thick floppy disks not even the 05:31:48.900 --> 05:31:50.750 align:start position:0% big thick floppy disks not even the small<05:31:49.080> ones<05:31:49.440> that<05:31:49.560> you<05:31:49.740> might<05:31:49.860> remember<05:31:50.040> that 05:31:50.750 --> 05:31:50.760 align:start position:0% small ones that you might remember that 05:31:50.760 --> 05:31:54.288 align:start position:0% small ones that you might remember that was<05:31:50.878> called<05:31:51.060> sneakinet 05:31:54.288 --> 05:31:54.298 align:start position:0% 05:31:54.298 --> 05:31:56.330 align:start position:0% turnbass<05:31:54.900> tea<05:31:55.020> was<05:31:55.200> one<05:31:55.378> of<05:31:55.500> the<05:31:55.560> first<05:31:55.798> modern 05:31:56.330 --> 05:31:56.340 align:start position:0% turnbass tea was one of the first modern 05:31:56.340 --> 05:31:59.570 align:start position:0% turnbass tea was one of the first modern standards<05:31:57.060> introduced<05:31:57.480> in<05:31:57.660> 1990 05:31:59.570 --> 05:31:59.580 align:start position:0% standards introduced in 1990 05:31:59.580 --> 05:32:02.270 align:start position:0% standards introduced in 1990 it<05:32:00.060> ran<05:32:00.360> over<05:32:00.600> 10<05:32:00.900> Meg<05:32:01.320> over<05:32:01.500> two<05:32:01.798> pairs<05:32:02.160> of 05:32:02.270 --> 05:32:02.280 align:start position:0% it ran over 10 Meg over two pairs of 05:32:02.280 --> 05:32:05.510 align:start position:0% it ran over 10 Meg over two pairs of twisted<05:32:02.820> uh<05:32:03.600> paired<05:32:04.320> telephone<05:32:04.440> wire 05:32:05.510 --> 05:32:05.520 align:start position:0% twisted uh paired telephone wire 05:32:05.520 --> 05:32:07.490 align:start position:0% twisted uh paired telephone wire and<05:32:06.060> it<05:32:06.180> allowed<05:32:06.540> your<05:32:06.718> network<05:32:06.900> to<05:32:07.200> use<05:32:07.320> the 05:32:07.490 --> 05:32:07.500 align:start position:0% and it allowed your network to use the 05:32:07.500 --> 05:32:09.050 align:start position:0% and it allowed your network to use the existing<05:32:07.860> telephone<05:32:08.040> cabling<05:32:08.638> which<05:32:08.940> is 05:32:09.050 --> 05:32:09.060 align:start position:0% existing telephone cabling which is 05:32:09.060 --> 05:32:11.708 align:start position:0% existing telephone cabling which is pretty<05:32:09.298> handy<05:32:09.740> really<05:32:10.740> easy<05:32:10.920> to<05:32:11.280> install 05:32:11.708 --> 05:32:11.718 align:start position:0% pretty handy really easy to install 05:32:11.718 --> 05:32:14.750 align:start position:0% pretty handy really easy to install reduce<05:32:12.718> costs<05:32:13.378> the<05:32:13.798> cable<05:32:13.920> could<05:32:14.340> just<05:32:14.458> be<05:32:14.580> run 05:32:14.750 --> 05:32:14.760 align:start position:0% reduce costs the cable could just be run 05:32:14.760 --> 05:32:17.150 align:start position:0% reduce costs the cable could just be run off<05:32:14.940> and<05:32:15.180> you<05:32:15.360> could<05:32:15.540> cut<05:32:16.378> it<05:32:16.620> to<05:32:16.798> whichever 05:32:17.150 --> 05:32:17.160 align:start position:0% off and you could cut it to whichever 05:32:17.160 --> 05:32:18.948 align:start position:0% off and you could cut it to whichever length<05:32:17.580> you<05:32:17.700> required 05:32:18.948 --> 05:32:18.958 align:start position:0% length you required 05:32:18.958 --> 05:32:20.628 align:start position:0% length you required and<05:32:19.560> also<05:32:19.798> obviously<05:32:20.100> you<05:32:20.160> could<05:32:20.280> use<05:32:20.458> a 05:32:20.628 --> 05:32:20.638 align:start position:0% and also obviously you could use a 05:32:20.638 --> 05:32:23.030 align:start position:0% and also obviously you could use a network<05:32:20.760> switch<05:32:21.180> which<05:32:21.600> the<05:32:21.958> uh<05:32:22.320> thick<05:32:22.980> and 05:32:23.030 --> 05:32:23.040 align:start position:0% network switch which the uh thick and 05:32:23.040 --> 05:32:25.550 align:start position:0% network switch which the uh thick and thin<05:32:23.280> that<05:32:23.458> couldn't<05:32:23.580> use<05:32:23.820> a<05:32:24.060> switch<05:32:24.240> or<05:32:24.480> hub 05:32:25.550 --> 05:32:25.560 align:start position:0% thin that couldn't use a switch or hub 05:32:25.560 --> 05:32:28.910 align:start position:0% thin that couldn't use a switch or hub T<05:32:26.340> denotes<05:32:26.940> twisted<05:32:27.298> pair<05:32:27.480> wires 05:32:28.910 --> 05:32:28.920 align:start position:0% T denotes twisted pair wires 05:32:28.920 --> 05:32:31.610 align:start position:0% T denotes twisted pair wires 10<05:32:29.520> base<05:32:29.760> T<05:32:30.000> is<05:32:30.180> category<05:32:30.660> three<05:32:30.900> cable<05:32:31.320> we 05:32:31.610 --> 05:32:31.620 align:start position:0% 10 base T is category three cable we 05:32:31.620 --> 05:32:34.128 align:start position:0% 10 base T is category three cable we used<05:32:31.740> to<05:32:31.860> call<05:32:31.980> it<05:32:32.100> cat<05:32:32.340> 3<05:32:32.638> for<05:32:33.120> short<05:32:33.298> in<05:32:34.020> fact 05:32:34.128 --> 05:32:34.138 align:start position:0% used to call it cat 3 for short in fact 05:32:34.138 --> 05:32:37.910 align:start position:0% used to call it cat 3 for short in fact every<05:32:34.378> category<05:32:34.860> is<05:32:35.040> is<05:32:35.580> called<05:32:36.420> a<05:32:36.660> cat<05:32:36.840> for<05:32:37.920> um 05:32:37.910 --> 05:32:37.920 align:start position:0% every category is is called a cat for um 05:32:37.920 --> 05:32:40.010 align:start position:0% every category is is called a cat for um short 05:32:40.010 --> 05:32:40.020 align:start position:0% short 05:32:40.020 --> 05:32:42.170 align:start position:0% short High<05:32:40.440> category<05:32:40.920> cables<05:32:41.458> can<05:32:41.580> be<05:32:41.760> used<05:32:41.940> with 05:32:42.170 --> 05:32:42.180 align:start position:0% High category cables can be used with 05:32:42.180 --> 05:32:45.110 align:start position:0% High category cables can be used with the<05:32:42.480> 10<05:32:42.900> base<05:32:43.260> T<05:32:43.798> ethernet 05:32:45.110 --> 05:32:45.120 align:start position:0% the 10 base T ethernet 05:32:45.120 --> 05:32:49.788 align:start position:0% the 10 base T ethernet so<05:32:45.958> examples<05:32:46.378> are<05:32:46.560> CAT5<05:32:47.100> 5e<05:32:47.940> 6<05:32:48.298> 6A<05:32:48.958> and<05:32:49.440> so<05:32:49.620> on 05:32:49.788 --> 05:32:49.798 align:start position:0% so examples are CAT5 5e 6 6A and so on 05:32:49.798 --> 05:32:51.770 align:start position:0% so examples are CAT5 5e 6 6A and so on this<05:32:50.160> changes<05:32:50.520> every<05:32:50.820> few<05:32:51.000> months<05:32:51.298> as<05:32:51.480> a<05:32:51.660> new 05:32:51.770 --> 05:32:51.780 align:start position:0% this changes every few months as a new 05:32:51.780 --> 05:32:53.868 align:start position:0% this changes every few months as a new category<05:32:52.200> introduced 05:32:53.868 --> 05:32:53.878 align:start position:0% category introduced 05:32:53.878 --> 05:32:56.510 align:start position:0% category introduced High<05:32:54.480> categories<05:32:55.020> of<05:32:55.260> the<05:32:55.500> TP<05:32:55.860> cables<05:32:56.340> have 05:32:56.510 --> 05:32:56.520 align:start position:0% High categories of the TP cables have 05:32:56.520 --> 05:32:58.430 align:start position:0% High categories of the TP cables have higher<05:32:56.878> specifications<05:32:57.480> and<05:32:58.138> they<05:32:58.320> can 05:32:58.430 --> 05:32:58.440 align:start position:0% higher specifications and they can 05:32:58.440 --> 05:33:01.368 align:start position:0% higher specifications and they can handle<05:32:58.740> higher<05:32:59.100> data<05:32:59.400> transmission<05:32:59.580> speeds 05:33:01.368 --> 05:33:01.378 align:start position:0% handle higher data transmission speeds 05:33:01.378 --> 05:33:04.368 align:start position:0% handle higher data transmission speeds the<05:33:01.920> term<05:33:02.218> base<05:33:02.580> T<05:33:03.120> supports<05:33:03.718> the<05:33:03.958> maximum 05:33:04.368 --> 05:33:04.378 align:start position:0% the term base T supports the maximum 05:33:04.378 --> 05:33:08.448 align:start position:0% the term base T supports the maximum cable<05:33:04.680> length<05:33:05.100> of<05:33:05.218> 100<05:33:05.458> meters 05:33:08.448 --> 05:33:08.458 align:start position:0% 05:33:08.458 --> 05:33:11.090 align:start position:0% 100<05:33:08.638> Base<05:33:09.060> TX<05:33:09.480> I<05:33:09.718> mentioned<05:33:10.020> earlier 05:33:11.090 --> 05:33:11.100 align:start position:0% 100 Base TX I mentioned earlier 05:33:11.100 --> 05:33:14.270 align:start position:0% 100 Base TX I mentioned earlier 100<05:33:11.400> Meg<05:33:12.000> over<05:33:12.180> two<05:33:12.480> pairs<05:33:12.840> of<05:33:12.958> CAT5<05:33:13.440> twisted 05:33:14.270 --> 05:33:14.280 align:start position:0% 100 Meg over two pairs of CAT5 twisted 05:33:14.280 --> 05:33:16.730 align:start position:0% 100 Meg over two pairs of CAT5 twisted pair<05:33:14.458> cable<05:33:14.820> in<05:33:15.060> you<05:33:15.660> can<05:33:15.840> get<05:33:15.958> 100<05:33:16.138> meters 05:33:16.730 --> 05:33:16.740 align:start position:0% pair cable in you can get 100 meters 05:33:16.740 --> 05:33:19.368 align:start position:0% pair cable in you can get 100 meters before<05:33:17.040> you<05:33:17.280> have<05:33:17.400> to<05:33:17.520> terminate<05:33:18.060> the<05:33:18.240> cable 05:33:19.368 --> 05:33:19.378 align:start position:0% before you have to terminate the cable 05:33:19.378 --> 05:33:22.128 align:start position:0% before you have to terminate the cable we<05:33:19.680> normally<05:33:20.040> then<05:33:20.160> go<05:33:20.340> into<05:33:20.458> a<05:33:20.700> switch 05:33:22.128 --> 05:33:22.138 align:start position:0% we normally then go into a switch 05:33:22.138 --> 05:33:25.070 align:start position:0% we normally then go into a switch it's<05:33:22.920> called<05:33:23.280> Fast<05:33:23.638> ethernet 05:33:25.070 --> 05:33:25.080 align:start position:0% it's called Fast ethernet 05:33:25.080 --> 05:33:28.310 align:start position:0% it's called Fast ethernet so<05:33:25.560> 100<05:33:25.740> mag<05:33:26.420> obviously<05:33:27.420> 10<05:33:27.780> times<05:33:28.020> faster 05:33:28.310 --> 05:33:28.320 align:start position:0% so 100 mag obviously 10 times faster 05:33:28.320 --> 05:33:30.708 align:start position:0% so 100 mag obviously 10 times faster than<05:33:28.560> 10<05:33:28.740> base<05:33:28.980> t 05:33:30.708 --> 05:33:30.718 align:start position:0% than 10 base t 05:33:30.718 --> 05:33:33.590 align:start position:0% than 10 base t uh<05:33:31.440> became<05:33:31.920> widely<05:33:32.520> used<05:33:32.878> because<05:33:33.120> of<05:33:33.360> its 05:33:33.590 --> 05:33:33.600 align:start position:0% uh became widely used because of its 05:33:33.600 --> 05:33:35.690 align:start position:0% uh became widely used because of its compatibility<05:33:34.080> with<05:33:34.500> 10<05:33:34.680> base<05:33:34.920> T<05:33:35.218> so<05:33:35.458> imagine 05:33:35.690 --> 05:33:35.700 align:start position:0% compatibility with 10 base T so imagine 05:33:35.700 --> 05:33:39.650 align:start position:0% compatibility with 10 base T so imagine back<05:33:36.600> in<05:33:36.780> the<05:33:36.958> day<05:33:37.138> you<05:33:37.860> would<05:33:37.980> have<05:33:38.280> your<05:33:39.240> um 05:33:39.650 --> 05:33:39.660 align:start position:0% back in the day you would have your um 05:33:39.660 --> 05:33:42.110 align:start position:0% back in the day you would have your um the<05:33:40.138> core<05:33:40.260> of<05:33:40.500> your<05:33:40.680> network<05:33:40.920> running<05:33:41.580> at<05:33:41.940> 100 05:33:42.110 --> 05:33:42.120 align:start position:0% the core of your network running at 100 05:33:42.120 --> 05:33:45.350 align:start position:0% the core of your network running at 100 Meg<05:33:43.080> and<05:33:43.740> then<05:33:44.280> um<05:33:44.280> unless<05:33:44.638> if<05:33:45.120> you<05:33:45.180> didn't 05:33:45.350 --> 05:33:45.360 align:start position:0% Meg and then um unless if you didn't 05:33:45.360 --> 05:33:47.030 align:start position:0% Meg and then um unless if you didn't have<05:33:45.540> the<05:33:45.660> budget<05:33:45.958> you<05:33:46.560> would<05:33:46.680> have<05:33:46.860> your 05:33:47.030 --> 05:33:47.040 align:start position:0% have the budget you would have your 05:33:47.040 --> 05:33:49.970 align:start position:0% have the budget you would have your individual<05:33:47.580> PCS<05:33:48.240> connecting<05:33:48.660> at<05:33:48.900> 10<05:33:49.080> Meg<05:33:49.440> into 05:33:49.970 --> 05:33:49.980 align:start position:0% individual PCS connecting at 10 Meg into 05:33:49.980 --> 05:33:53.330 align:start position:0% individual PCS connecting at 10 Meg into the<05:33:50.340> network<05:33:50.520> switch<05:33:51.000> or<05:33:51.298> hub 05:33:53.330 --> 05:33:53.340 align:start position:0% the network switch or hub 05:33:53.340 --> 05:33:56.270 align:start position:0% the network switch or hub they<05:33:53.878> used<05:33:54.060> a<05:33:54.240> Cat5<05:33:54.718> cables<05:33:55.378> a<05:33:55.740> lot<05:33:55.860> easier<05:33:56.160> to 05:33:56.270 --> 05:33:56.280 align:start position:0% they used a Cat5 cables a lot easier to 05:33:56.280 --> 05:33:58.910 align:start position:0% they used a Cat5 cables a lot easier to upgrade<05:33:56.760> because<05:33:57.240> it<05:33:57.480> used<05:33:57.718> the<05:33:58.080> same<05:33:58.620> Cable 05:33:58.910 --> 05:33:58.920 align:start position:0% upgrade because it used the same Cable 05:33:58.920 --> 05:34:01.490 align:start position:0% upgrade because it used the same Cable in<05:33:59.218> principles<05:33:59.638> and<05:34:00.000> same<05:34:00.240> pin<05:34:00.600> outs 05:34:01.490 --> 05:34:01.500 align:start position:0% in principles and same pin outs 05:34:01.500 --> 05:34:04.128 align:start position:0% in principles and same pin outs and<05:34:02.160> determination 05:34:04.128 --> 05:34:04.138 align:start position:0% and determination 05:34:04.138 --> 05:34:07.730 align:start position:0% and determination 100<05:34:04.680> base<05:34:05.100> FX<05:34:05.820> f<05:34:06.360> is<05:34:06.600> usually<05:34:07.260> designates 05:34:07.730 --> 05:34:07.740 align:start position:0% 100 base FX f is usually designates 05:34:07.740 --> 05:34:09.970 align:start position:0% 100 base FX f is usually designates fiber<05:34:08.218> optic 05:34:09.970 --> 05:34:09.980 align:start position:0% fiber optic 05:34:09.980 --> 05:34:12.890 align:start position:0% fiber optic fiber<05:34:10.980> standard<05:34:11.340> for<05:34:11.580> 100<05:34:11.760> Meg<05:34:12.240> ethernet<05:34:12.600> is 05:34:12.890 --> 05:34:12.900 align:start position:0% fiber standard for 100 Meg ethernet is 05:34:12.900 --> 05:34:16.490 align:start position:0% fiber standard for 100 Meg ethernet is 100<05:34:13.080> base<05:34:13.440> FX 05:34:16.490 --> 05:34:16.500 align:start position:0% 05:34:16.500 --> 05:34:18.550 align:start position:0% so<05:34:17.040> this<05:34:17.280> is<05:34:17.520> a 05:34:18.550 --> 05:34:18.560 align:start position:0% so this is a 05:34:18.560 --> 05:34:22.310 align:start position:0% so this is a 802.3<05:34:19.560> u<05:34:20.160> specification 05:34:22.310 --> 05:34:22.320 align:start position:0% 802.3 u specification 05:34:22.320 --> 05:34:24.230 align:start position:0% 802.3 u specification it's<05:34:22.680> 100<05:34:22.920> Meg<05:34:23.340> ethernet<05:34:23.520> over<05:34:23.940> two 05:34:24.230 --> 05:34:24.240 align:start position:0% it's 100 Meg ethernet over two 05:34:24.240 --> 05:34:27.830 align:start position:0% it's 100 Meg ethernet over two multi-mode<05:34:24.980> Optical<05:34:25.980> fibers 05:34:27.830 --> 05:34:27.840 align:start position:0% multi-mode Optical fibers 05:34:27.840 --> 05:34:29.868 align:start position:0% multi-mode Optical fibers one's<05:34:28.378> used<05:34:28.500> for<05:34:28.680> the<05:34:28.798> transmission<05:34:29.040> and<05:34:29.580> ones 05:34:29.868 --> 05:34:29.878 align:start position:0% one's used for the transmission and ones 05:34:29.878 --> 05:34:32.208 align:start position:0% one's used for the transmission and ones used<05:34:30.060> for<05:34:30.240> the<05:34:30.360> receiver<05:34:30.718> as<05:34:31.138> and<05:34:31.620> designated 05:34:32.208 --> 05:34:32.218 align:start position:0% used for the receiver as and designated 05:34:32.218 --> 05:34:35.530 align:start position:0% used for the receiver as and designated in<05:34:32.580> the<05:34:32.820> diagram<05:34:33.780> there 05:34:35.530 --> 05:34:35.540 align:start position:0% in the diagram there 05:34:35.540 --> 05:34:38.270 align:start position:0% in the diagram there the<05:34:36.540> 100<05:34:36.660> base<05:34:37.020> FX<05:34:37.378> standard<05:34:37.740> supports<05:34:38.160> the 05:34:38.270 --> 05:34:38.280 align:start position:0% the 100 base FX standard supports the 05:34:38.280 --> 05:34:41.090 align:start position:0% the 100 base FX standard supports the maximum<05:34:38.638> cable<05:34:38.940> length<05:34:39.420> of<05:34:39.540> 400<05:34:40.020> meters<05:34:40.500> in 05:34:41.090 --> 05:34:41.100 align:start position:0% maximum cable length of 400 meters in 05:34:41.100 --> 05:34:43.070 align:start position:0% maximum cable length of 400 meters in half<05:34:41.280> duplex<05:34:41.760> mode 05:34:43.070 --> 05:34:43.080 align:start position:0% half duplex mode 05:34:43.080 --> 05:34:45.230 align:start position:0% half duplex mode half<05:34:43.440> duplex<05:34:43.860> is<05:34:44.100> pretty<05:34:44.340> old-fashioned<05:34:45.120> now 05:34:45.230 --> 05:34:45.240 align:start position:0% half duplex is pretty old-fashioned now 05:34:45.240 --> 05:34:46.730 align:start position:0% half duplex is pretty old-fashioned now to<05:34:45.420> be<05:34:45.540> honest 05:34:46.730 --> 05:34:46.740 align:start position:0% to be honest 05:34:46.740 --> 05:34:48.890 align:start position:0% to be honest or<05:34:47.040> in<05:34:47.218> full<05:34:47.400> duplex<05:34:47.820> mode 05:34:48.890 --> 05:34:48.900 align:start position:0% or in full duplex mode 05:34:48.900 --> 05:34:50.448 align:start position:0% or in full duplex mode which<05:34:49.200> means<05:34:49.440> you<05:34:49.560> can<05:34:49.680> send<05:34:49.798> and<05:34:49.980> receive<05:34:50.280> at 05:34:50.448 --> 05:34:50.458 align:start position:0% which means you can send and receive at 05:34:50.458 --> 05:34:54.470 align:start position:0% which means you can send and receive at the<05:34:50.580> same<05:34:50.700> time<05:34:51.138> then<05:34:52.138> up<05:34:52.378> to<05:34:52.560> two<05:34:52.860> kilometers 05:34:54.470 --> 05:34:54.480 align:start position:0% the same time then up to two kilometers 05:34:54.480 --> 05:34:56.868 align:start position:0% the same time then up to two kilometers half<05:34:54.840> duplex<05:34:55.260> mode<05:34:55.680> as<05:34:56.280> well<05:34:56.458> just<05:34:56.760> so 05:34:56.868 --> 05:34:56.878 align:start position:0% half duplex mode as well just so 05:34:56.878 --> 05:34:58.610 align:start position:0% half duplex mode as well just so basically<05:34:57.298> it's<05:34:57.600> like<05:34:57.840> a<05:34:57.958> walkie-talk<05:34:58.378> here 05:34:58.610 --> 05:34:58.620 align:start position:0% basically it's like a walkie-talk here 05:34:58.620 --> 05:35:00.590 align:start position:0% basically it's like a walkie-talk here device<05:34:58.798> can<05:34:59.100> either<05:34:59.218> send<05:34:59.458> or<05:34:59.700> receive<05:35:00.060> data 05:35:00.590 --> 05:35:00.600 align:start position:0% device can either send or receive data 05:35:00.600 --> 05:35:03.288 align:start position:0% device can either send or receive data at<05:35:01.080> a<05:35:01.260> given<05:35:01.500> time<05:35:01.620> but<05:35:01.798> it<05:35:01.920> can't<05:35:02.040> do<05:35:02.280> both 05:35:03.288 --> 05:35:03.298 align:start position:0% at a given time but it can't do both 05:35:03.298 --> 05:35:05.930 align:start position:0% at a given time but it can't do both full<05:35:03.780> duplexy<05:35:04.500> can<05:35:04.680> do<05:35:04.798> both<05:35:05.100> so<05:35:05.580> it's<05:35:05.760> like 05:35:05.930 --> 05:35:05.940 align:start position:0% full duplexy can do both so it's like 05:35:05.940 --> 05:35:08.208 align:start position:0% full duplexy can do both so it's like having<05:35:06.120> a<05:35:06.298> telephone<05:35:06.480> conversation 05:35:08.208 --> 05:35:08.218 align:start position:0% having a telephone conversation 05:35:08.218 --> 05:35:11.330 align:start position:0% having a telephone conversation a<05:35:08.878> thousand<05:35:09.180> base<05:35:09.420> T<05:35:09.718> now<05:35:10.080> we're<05:35:10.320> talking<05:35:10.500> 10 05:35:11.330 --> 05:35:11.340 align:start position:0% a thousand base T now we're talking 10 05:35:11.340 --> 05:35:13.788 align:start position:0% a thousand base T now we're talking 10 times<05:35:11.520> faster<05:35:11.878> than<05:35:12.120> a<05:35:12.360> hundred 05:35:13.788 --> 05:35:13.798 align:start position:0% times faster than a hundred 05:35:13.798 --> 05:35:19.850 align:start position:0% times faster than a hundred it's<05:35:14.458> a<05:35:14.638> IEEE<05:35:15.740> 802.3<05:35:16.740> a<05:35:17.100> b<05:35:17.718> specification<05:35:18.860> it's 05:35:19.850 --> 05:35:19.860 align:start position:0% it's a IEEE 802.3 a b specification it's 05:35:19.860 --> 05:35:21.948 align:start position:0% it's a IEEE 802.3 a b specification it's a<05:35:20.160> thousand<05:35:20.580> megabit<05:35:21.298> per<05:35:21.480> second<05:35:21.600> ethernet 05:35:21.948 --> 05:35:21.958 align:start position:0% a thousand megabit per second ethernet 05:35:21.958 --> 05:35:26.030 align:start position:0% a thousand megabit per second ethernet Network<05:35:22.378> uses<05:35:23.280> four<05:35:23.520> pairs<05:35:24.000> of<05:35:24.240> CAT5<05:35:24.780> cable<05:35:25.378> or 05:35:26.030 --> 05:35:26.040 align:start position:0% Network uses four pairs of CAT5 cable or 05:35:26.040 --> 05:35:26.868 align:start position:0% Network uses four pairs of CAT5 cable or better 05:35:26.868 --> 05:35:26.878 align:start position:0% better 05:35:26.878 --> 05:35:30.470 align:start position:0% better and<05:35:27.480> speak<05:35:27.780> to<05:35:28.020> your<05:35:28.440> cabling<05:35:28.860> provider<05:35:29.638> to<05:35:30.480> um 05:35:30.470 --> 05:35:30.480 align:start position:0% and speak to your cabling provider to um 05:35:30.480 --> 05:35:33.110 align:start position:0% and speak to your cabling provider to um find<05:35:30.718> out<05:35:30.900> what<05:35:31.080> cable<05:35:31.440> you<05:35:32.218> can<05:35:32.280> use<05:35:32.458> minimum 05:35:33.110 --> 05:35:33.120 align:start position:0% find out what cable you can use minimum 05:35:33.120 --> 05:35:35.090 align:start position:0% find out what cable you can use minimum standards 05:35:35.090 --> 05:35:35.100 align:start position:0% standards 05:35:35.100 --> 05:35:38.628 align:start position:0% standards 100<05:35:35.660> meter<05:35:36.660> length<05:35:37.020> of<05:35:37.080> cable 05:35:38.628 --> 05:35:38.638 align:start position:0% 100 meter length of cable 05:35:38.638 --> 05:35:41.690 align:start position:0% 100 meter length of cable it's<05:35:39.718> um<05:35:39.718> referred<05:35:40.138> to<05:35:40.260> as<05:35:40.500> gigabit<05:35:41.100> Ethernet 05:35:41.690 --> 05:35:41.700 align:start position:0% it's um referred to as gigabit Ethernet 05:35:41.700 --> 05:35:43.250 align:start position:0% it's um referred to as gigabit Ethernet 1000<05:35:42.298> bits 05:35:43.250 --> 05:35:43.260 align:start position:0% 1000 bits 05:35:43.260 --> 05:35:46.610 align:start position:0% 1000 bits that<05:35:43.740> easy<05:35:43.980> to<05:35:44.218> install<05:35:44.400> runs<05:35:45.000> on<05:35:45.120> CAT5 05:35:46.610 --> 05:35:46.620 align:start position:0% that easy to install runs on CAT5 05:35:46.620 --> 05:35:50.030 align:start position:0% that easy to install runs on CAT5 and<05:35:47.218> inexpensive<05:35:48.000> cables 05:35:50.030 --> 05:35:50.040 align:start position:0% and inexpensive cables 05:35:50.040 --> 05:35:52.610 align:start position:0% and inexpensive cables as<05:35:50.638> an<05:35:50.878> example<05:35:51.120> of<05:35:51.240> a<05:35:51.360> CAT5<05:35:51.718> cable<05:35:52.138> which<05:35:52.500> I'm 05:35:52.610 --> 05:35:52.620 align:start position:0% as an example of a CAT5 cable which I'm 05:35:52.620 --> 05:35:54.590 align:start position:0% as an example of a CAT5 cable which I'm sure<05:35:52.798> you've<05:35:53.040> seen<05:35:53.340> many<05:35:53.940> times<05:35:54.180> even<05:35:54.360> if 05:35:54.590 --> 05:35:54.600 align:start position:0% sure you've seen many times even if 05:35:54.600 --> 05:35:57.770 align:start position:0% sure you've seen many times even if you've<05:35:54.718> got<05:35:54.900> a<05:35:55.080> home<05:35:55.798> computer 05:35:57.770 --> 05:35:57.780 align:start position:0% you've got a home computer 05:35:57.780 --> 05:35:59.868 align:start position:0% you've got a home computer so<05:35:58.080> the<05:35:58.138> Cat5<05:35:58.500> cables<05:35:59.040> are<05:35:59.160> four<05:35:59.400> pairs<05:35:59.760> of 05:35:59.868 --> 05:35:59.878 align:start position:0% so the Cat5 cables are four pairs of 05:35:59.878 --> 05:36:02.270 align:start position:0% so the Cat5 cables are four pairs of twist<05:36:00.298> uh<05:36:00.780> four<05:36:01.020> pairs<05:36:01.378> of<05:36:01.440> Twisted<05:36:01.860> wire 05:36:02.270 --> 05:36:02.280 align:start position:0% twist uh four pairs of Twisted wire 05:36:02.280 --> 05:36:05.690 align:start position:0% twist uh four pairs of Twisted wire which<05:36:02.940> is<05:36:03.060> eight<05:36:03.298> individual<05:36:03.958> strands 05:36:05.690 --> 05:36:05.700 align:start position:0% which is eight individual strands 05:36:05.700 --> 05:36:08.750 align:start position:0% which is eight individual strands the<05:36:06.480> 10<05:36:06.900> and<05:36:07.080> 100<05:36:07.200> base<05:36:07.500> T<05:36:07.798> only<05:36:08.100> uses<05:36:08.520> two 05:36:08.750 --> 05:36:08.760 align:start position:0% the 10 and 100 base T only uses two 05:36:08.760 --> 05:36:09.948 align:start position:0% the 10 and 100 base T only uses two pairs 05:36:09.948 --> 05:36:09.958 align:start position:0% pairs 05:36:09.958 --> 05:36:12.410 align:start position:0% pairs all<05:36:10.740> four<05:36:10.980> pairs<05:36:11.400> are<05:36:11.458> used<05:36:11.638> by<05:36:11.940> the<05:36:12.060> EM 05:36:12.410 --> 05:36:12.420 align:start position:0% all four pairs are used by the EM 05:36:12.420 --> 05:36:15.230 align:start position:0% all four pairs are used by the EM thousand<05:36:13.020> base<05:36:13.200> t 05:36:15.230 --> 05:36:15.240 align:start position:0% thousand base t 05:36:15.240 --> 05:36:18.170 align:start position:0% thousand base t popular<05:36:15.780> gigabit<05:36:16.440> Ethernet<05:36:16.860> and<05:36:17.820> the 05:36:18.170 --> 05:36:18.180 align:start position:0% popular gigabit Ethernet and the 05:36:18.180 --> 05:36:19.970 align:start position:0% popular gigabit Ethernet and the Thousand<05:36:18.480> base<05:36:18.660> T<05:36:18.900> is<05:36:19.020> the<05:36:19.138> most<05:36:19.260> widely<05:36:19.740> used 05:36:19.970 --> 05:36:19.980 align:start position:0% Thousand base T is the most widely used 05:36:19.980 --> 05:36:21.650 align:start position:0% Thousand base T is the most widely used version 05:36:21.650 --> 05:36:21.660 align:start position:0% version 05:36:21.660 --> 05:36:23.810 align:start position:0% version you've<05:36:22.260> got<05:36:22.320> the<05:36:22.440> a223<05:36:23.280> standard<05:36:23.638> that 05:36:23.810 --> 05:36:23.820 align:start position:0% you've got the a223 standard that 05:36:23.820 --> 05:36:25.788 align:start position:0% you've got the a223 standard that specifies<05:36:24.360> other<05:36:24.718> versions<05:36:25.138> of<05:36:25.320> gigabit 05:36:25.788 --> 05:36:25.798 align:start position:0% specifies other versions of gigabit 05:36:25.798 --> 05:36:29.090 align:start position:0% specifies other versions of gigabit Ethernet<05:36:26.340> here<05:36:27.240> are<05:36:27.360> some<05:36:27.600> of<05:36:27.660> your<05:36:27.780> options 05:36:29.090 --> 05:36:29.100 align:start position:0% Ethernet here are some of your options 05:36:29.100 --> 05:36:32.930 align:start position:0% Ethernet here are some of your options um<05:36:29.160> thousand<05:36:30.120> Bay<05:36:30.298> CX<05:36:30.958> LS<05:36:31.680> LX 05:36:32.930 --> 05:36:32.940 align:start position:0% um thousand Bay CX LS LX 05:36:32.940 --> 05:36:35.208 align:start position:0% um thousand Bay CX LS LX SX 05:36:35.208 --> 05:36:35.218 align:start position:0% SX 05:36:35.218 --> 05:36:37.970 align:start position:0% SX uh<05:36:35.940> you<05:36:36.180> need<05:36:36.958> to<05:36:37.138> know<05:36:37.320> some<05:36:37.680> of<05:36:37.860> this 05:36:37.970 --> 05:36:37.980 align:start position:0% uh you need to know some of this 05:36:37.980 --> 05:36:39.590 align:start position:0% uh you need to know some of this information<05:36:38.280> but<05:36:38.878> I<05:36:39.060> think<05:36:39.180> one<05:36:39.420> of<05:36:39.540> the 05:36:39.590 --> 05:36:39.600 align:start position:0% information but I think one of the 05:36:39.600 --> 05:36:41.330 align:start position:0% information but I think one of the questions<05:36:39.780> they<05:36:40.080> could<05:36:40.200> ask<05:36:40.378> is<05:36:40.620> which<05:36:40.980> one<05:36:41.218> of 05:36:41.330 --> 05:36:41.340 align:start position:0% questions they could ask is which one of 05:36:41.340 --> 05:36:43.128 align:start position:0% questions they could ask is which one of them<05:36:41.520> is 05:36:43.128 --> 05:36:43.138 align:start position:0% them is 05:36:43.138 --> 05:36:46.670 align:start position:0% them is um fiber<05:36:43.680> optic<05:36:43.980> and<05:36:44.760> the<05:36:44.940> answer<05:36:45.180> is<05:36:45.540> LX<05:36:46.378> it's 05:36:46.670 --> 05:36:46.680 align:start position:0% um fiber optic and the answer is LX it's 05:36:46.680 --> 05:36:48.890 align:start position:0% um fiber optic and the answer is LX it's a<05:36:46.920> question<05:36:47.040> I've<05:36:47.340> seen<05:36:47.580> before<05:36:47.820> I<05:36:48.600> think<05:36:48.718> I 05:36:48.890 --> 05:36:48.900 align:start position:0% a question I've seen before I think I 05:36:48.900 --> 05:36:51.590 align:start position:0% a question I've seen before I think I was<05:36:49.020> actually<05:36:49.138> asked<05:36:49.440> in<05:36:49.500> a<05:36:49.680> Cisco<05:36:50.040> exam<05:36:50.400> not 05:36:51.590 --> 05:36:51.600 align:start position:0% was actually asked in a Cisco exam not 05:36:51.600 --> 05:36:54.708 align:start position:0% was actually asked in a Cisco exam not um<05:36:52.080> uh<05:36:52.680> CompTIA<05:36:53.218> Network<05:36:53.400> plus<05:36:53.820> but<05:36:54.120> good<05:36:54.540> to 05:36:54.708 --> 05:36:54.718 align:start position:0% um uh CompTIA Network plus but good to 05:36:54.718 --> 05:36:56.930 align:start position:0% um uh CompTIA Network plus but good to know<05:36:54.840> anyway 05:36:56.930 --> 05:36:56.940 align:start position:0% know anyway 05:36:56.940 --> 05:37:00.230 align:start position:0% know anyway so<05:36:57.660> five<05:36:58.080> kilometers<05:36:58.620> to<05:36:58.980> 550<05:36:59.760> meters 05:37:00.230 --> 05:37:00.240 align:start position:0% so five kilometers to 550 meters 05:37:00.240 --> 05:37:03.530 align:start position:0% so five kilometers to 550 meters depending<05:37:00.718> if<05:37:00.900> it's<05:37:01.020> single<05:37:01.440> or<05:37:01.620> multi-mode 05:37:03.530 --> 05:37:03.540 align:start position:0% depending if it's single or multi-mode 05:37:03.540 --> 05:37:06.110 align:start position:0% depending if it's single or multi-mode and<05:37:04.138> SX<05:37:04.560> is<05:37:04.860> implemented<05:37:05.280> over<05:37:05.458> multi-mode 05:37:06.110 --> 05:37:06.120 align:start position:0% and SX is implemented over multi-mode 05:37:06.120 --> 05:37:11.090 align:start position:0% and SX is implemented over multi-mode fiber<05:37:06.540> as<05:37:06.840> well<05:37:07.020> so<05:37:07.798> um<05:37:07.798> LX<05:37:08.218> and<05:37:08.520> SX 05:37:11.090 --> 05:37:11.100 align:start position:0% 05:37:11.100 --> 05:37:14.510 align:start position:0% 1000<05:37:11.458> Base<05:37:11.878> TX<05:37:12.540> is<05:37:12.958> gigabit<05:37:13.500> over<05:37:13.798> Cat6 05:37:14.510 --> 05:37:14.520 align:start position:0% 1000 Base TX is gigabit over Cat6 05:37:14.520 --> 05:37:16.490 align:start position:0% 1000 Base TX is gigabit over Cat6 cabling 05:37:16.490 --> 05:37:16.500 align:start position:0% cabling 05:37:16.500 --> 05:37:19.310 align:start position:0% cabling supports<05:37:17.340> a<05:37:17.580> maximum<05:37:17.940> cable<05:37:18.240> length<05:37:18.718> of<05:37:18.840> 100 05:37:19.310 --> 05:37:19.320 align:start position:0% supports a maximum cable length of 100 05:37:19.320 --> 05:37:21.010 align:start position:0% supports a maximum cable length of 100 meters 05:37:21.010 --> 05:37:21.020 align:start position:0% meters 05:37:21.020 --> 05:37:24.830 align:start position:0% meters uh<05:37:22.020> uses<05:37:22.320> only<05:37:22.500> two<05:37:22.798> pairs<05:37:23.280> of<05:37:24.000> wires<05:37:24.600> for<05:37:24.718> the 05:37:24.830 --> 05:37:24.840 align:start position:0% uh uses only two pairs of wires for the 05:37:24.840 --> 05:37:27.110 align:start position:0% uh uses only two pairs of wires for the data<05:37:25.200> transmission 05:37:27.110 --> 05:37:27.120 align:start position:0% data transmission 05:37:27.120 --> 05:37:29.150 align:start position:0% data transmission now<05:37:27.718> the<05:37:27.958> Thousand<05:37:28.260> Base<05:37:28.440> TX<05:37:28.798> you<05:37:28.980> don't 05:37:29.150 --> 05:37:29.160 align:start position:0% now the Thousand Base TX you don't 05:37:29.160 --> 05:37:30.770 align:start position:0% now the Thousand Base TX you don't really<05:37:29.280> see<05:37:29.400> much<05:37:29.638> anymore<05:37:29.820> is<05:37:30.180> a<05:37:30.360> bit<05:37:30.480> of<05:37:30.600> a 05:37:30.770 --> 05:37:30.780 align:start position:0% really see much anymore is a bit of a 05:37:30.780 --> 05:37:32.270 align:start position:0% really see much anymore is a bit of a commercial<05:37:30.958> failure 05:37:32.270 --> 05:37:32.280 align:start position:0% commercial failure 05:37:32.280 --> 05:37:34.610 align:start position:0% commercial failure mainly<05:37:33.060> because<05:37:33.240> of<05:37:33.480> the<05:37:33.780> Thousand<05:37:34.138> base<05:37:34.320> T 05:37:34.610 --> 05:37:34.620 align:start position:0% mainly because of the Thousand base T 05:37:34.620 --> 05:37:37.128 align:start position:0% mainly because of the Thousand base T the<05:37:34.860> cost<05:37:35.100> was<05:37:35.340> so<05:37:35.520> affordable<05:37:36.000> you<05:37:36.840> had<05:37:37.020> to 05:37:37.128 --> 05:37:37.138 align:start position:0% the cost was so affordable you had to 05:37:37.138 --> 05:37:39.890 align:start position:0% the cost was so affordable you had to upgrade<05:37:37.560> all<05:37:38.040> of<05:37:38.160> your<05:37:38.340> cables<05:37:38.760> from<05:37:39.000> CAT5<05:37:39.540> or 05:37:39.890 --> 05:37:39.900 align:start position:0% upgrade all of your cables from CAT5 or 05:37:39.900 --> 05:37:42.708 align:start position:0% upgrade all of your cables from CAT5 or Cat5e<05:37:40.680> to<05:37:40.860> Cat6<05:37:41.280> which<05:37:42.060> is<05:37:42.240> a<05:37:42.420> lot<05:37:42.600> of 05:37:42.708 --> 05:37:42.718 align:start position:0% Cat5e to Cat6 which is a lot of 05:37:42.718 --> 05:37:44.868 align:start position:0% Cat5e to Cat6 which is a lot of inconvenience<05:37:43.620> and<05:37:43.920> expensive<05:37:44.458> companies 05:37:44.868 --> 05:37:44.878 align:start position:0% inconvenience and expensive companies 05:37:44.878 --> 05:37:46.610 align:start position:0% inconvenience and expensive companies and<05:37:45.298> downtime 05:37:46.610 --> 05:37:46.620 align:start position:0% and downtime 05:37:46.620 --> 05:37:48.350 align:start position:0% and downtime because<05:37:47.040> of<05:37:47.280> your<05:37:47.400> all<05:37:47.580> your<05:37:47.760> core<05:37:47.940> devices 05:37:48.350 --> 05:37:48.360 align:start position:0% because of your all your core devices 05:37:48.360 --> 05:37:50.270 align:start position:0% because of your all your core devices would<05:37:48.718> need<05:37:48.900> the<05:37:49.320> connections<05:37:49.740> would<05:37:49.920> need<05:37:50.100> to 05:37:50.270 --> 05:37:50.280 align:start position:0% would need the connections would need to 05:37:50.280 --> 05:37:52.550 align:start position:0% would need the connections would need to be<05:37:50.700> um<05:37:50.700> changed<05:37:51.240> as<05:37:51.420> well<05:37:51.540> normally<05:37:52.260> have<05:37:52.440> to 05:37:52.550 --> 05:37:52.560 align:start position:0% be um changed as well normally have to 05:37:52.560 --> 05:37:55.190 align:start position:0% be um changed as well normally have to schedule<05:37:52.740> downtime 05:37:55.190 --> 05:37:55.200 align:start position:0% schedule downtime 05:37:55.200 --> 05:37:57.010 align:start position:0% schedule downtime um<05:37:55.320> for<05:37:55.560> this 05:37:57.010 --> 05:37:57.020 align:start position:0% um for this 05:37:57.020 --> 05:38:01.670 align:start position:0% um for this 10<05:37:58.020> gigabyte<05:37:58.920> 10g<05:37:59.580> base<05:37:59.820> t<05:38:00.180> 10<05:38:00.958> times<05:38:01.200> faster 05:38:01.670 --> 05:38:01.680 align:start position:0% 10 gigabyte 10g base t 10 times faster 05:38:01.680 --> 05:38:04.788 align:start position:0% 10 gigabyte 10g base t 10 times faster than<05:38:02.280> a<05:38:02.520> thousand<05:38:02.820> base<05:38:03.000> T<05:38:03.298> ethernet<05:38:03.798> operates 05:38:04.788 --> 05:38:04.798 align:start position:0% than a thousand base T ethernet operates 05:38:04.798 --> 05:38:06.470 align:start position:0% than a thousand base T ethernet operates at<05:38:05.040> 10<05:38:05.218> gig 05:38:06.470 --> 05:38:06.480 align:start position:0% at 10 gig 05:38:06.480 --> 05:38:11.270 align:start position:0% at 10 gig and<05:38:07.020> it's<05:38:07.200> an<05:38:07.400> 802.3<05:38:08.400> a<05:38:08.820> n<05:38:09.138> specification<05:38:10.280> four 05:38:11.270 --> 05:38:11.280 align:start position:0% and it's an 802.3 a n specification four 05:38:11.280 --> 05:38:14.990 align:start position:0% and it's an 802.3 a n specification four pairs<05:38:11.638> of<05:38:11.760> Cat6<05:38:12.360> a<05:38:12.900> cable<05:38:13.560> or<05:38:13.860> higher 05:38:14.990 --> 05:38:15.000 align:start position:0% pairs of Cat6 a cable or higher 05:38:15.000 --> 05:38:18.170 align:start position:0% pairs of Cat6 a cable or higher 100<05:38:15.660> meters<05:38:16.260> maximum 05:38:18.170 --> 05:38:18.180 align:start position:0% 100 meters maximum 05:38:18.180 --> 05:38:20.868 align:start position:0% 100 meters maximum it's<05:38:18.660> an<05:38:18.780> augmented<05:38:19.378> version<05:38:19.740> of<05:38:20.280> category 05:38:20.868 --> 05:38:20.878 align:start position:0% it's an augmented version of category 05:38:20.878 --> 05:38:24.288 align:start position:0% it's an augmented version of category six<05:38:21.360> which<05:38:21.958> you<05:38:22.138> can<05:38:22.320> see<05:38:22.440> 6A<05:38:23.100> isn't<05:38:24.000> the<05:38:24.120> same 05:38:24.288 --> 05:38:24.298 align:start position:0% six which you can see 6A isn't the same 05:38:24.298 --> 05:38:25.910 align:start position:0% six which you can see 6A isn't the same as<05:38:24.480> six 05:38:25.910 --> 05:38:25.920 align:start position:0% as six 05:38:25.920 --> 05:38:29.868 align:start position:0% as six and<05:38:26.400> frequency<05:38:26.940> is<05:38:27.480> at<05:38:27.660> 500<05:38:28.200> megahertz 05:38:29.868 --> 05:38:29.878 align:start position:0% and frequency is at 500 megahertz 05:38:29.878 --> 05:38:33.410 align:start position:0% and frequency is at 500 megahertz next<05:38:30.360> standard<05:38:30.718> is<05:38:30.958> 10gbase<05:38:31.920> Sr<05:38:32.458> this<05:38:33.360> is 05:38:33.410 --> 05:38:33.420 align:start position:0% next standard is 10gbase Sr this is 05:38:33.420 --> 05:38:35.868 align:start position:0% next standard is 10gbase Sr this is gigabit<05:38:33.900> Ethernet<05:38:34.138> over<05:38:34.500> Fiber<05:38:34.980> Optic<05:38:35.340> Cables 05:38:35.868 --> 05:38:35.878 align:start position:0% gigabit Ethernet over Fiber Optic Cables 05:38:35.878 --> 05:38:38.390 align:start position:0% gigabit Ethernet over Fiber Optic Cables I<05:38:36.480> don't<05:38:36.600> know<05:38:36.718> why<05:38:36.840> they<05:38:37.020> don't<05:38:37.138> just<05:38:37.320> put<05:38:37.560> a<05:38:37.740> f 05:38:38.390 --> 05:38:38.400 align:start position:0% I don't know why they don't just put a f 05:38:38.400 --> 05:38:40.850 align:start position:0% I don't know why they don't just put a f in<05:38:39.060> all<05:38:39.240> of<05:38:39.360> the<05:38:39.480> fiber<05:38:39.900> specifications<05:38:40.440> it's 05:38:40.850 --> 05:38:40.860 align:start position:0% in all of the fiber specifications it's 05:38:40.860 --> 05:38:43.390 align:start position:0% in all of the fiber specifications it's a<05:38:41.040> little<05:38:41.100> bit<05:38:41.280> annoying<05:38:41.638> to<05:38:41.820> be<05:38:42.000> honest 05:38:43.390 --> 05:38:43.400 align:start position:0% a little bit annoying to be honest 05:38:43.400 --> 05:38:46.368 align:start position:0% a little bit annoying to be honest 802.3<05:38:44.400> specification 05:38:46.368 --> 05:38:46.378 align:start position:0% 802.3 specification 05:38:46.378 --> 05:38:49.070 align:start position:0% 802.3 specification is<05:38:46.860> 10<05:38:47.100> gig<05:38:47.340> ethernet<05:38:47.700> over<05:38:48.000> multi-mode<05:38:48.600> fiber 05:38:49.070 --> 05:38:49.080 align:start position:0% is 10 gig ethernet over multi-mode fiber 05:38:49.080 --> 05:38:52.610 align:start position:0% is 10 gig ethernet over multi-mode fiber the<05:38:49.920> SR<05:38:50.218> stands<05:38:50.700> for<05:38:50.820> short<05:38:51.240> range 05:38:52.610 --> 05:38:52.620 align:start position:0% the SR stands for short range 05:38:52.620 --> 05:38:54.948 align:start position:0% the SR stands for short range at<05:38:52.980> the<05:38:53.100> cable<05:38:53.280> length<05:38:53.638> is<05:38:53.760> 300<05:38:54.240> meters<05:38:54.600> so<05:38:54.780> you 05:38:54.948 --> 05:38:54.958 align:start position:0% at the cable length is 300 meters so you 05:38:54.958 --> 05:38:56.750 align:start position:0% at the cable length is 300 meters so you only<05:38:55.080> need<05:38:55.260> to<05:38:55.378> make<05:38:55.500> a<05:38:55.680> note<05:38:55.798> of<05:38:56.040> all<05:38:56.218> of<05:38:56.520> these 05:38:56.750 --> 05:38:56.760 align:start position:0% only need to make a note of all of these 05:38:56.760 --> 05:38:58.070 align:start position:0% only need to make a note of all of these in<05:38:57.000> case<05:38:57.180> they 05:38:58.070 --> 05:38:58.080 align:start position:0% in case they 05:38:58.080 --> 05:39:00.170 align:start position:0% in case they for<05:38:58.500> some<05:38:58.620> reason<05:38:58.798> want<05:38:59.218> you<05:38:59.400> to 05:39:00.170 --> 05:39:00.180 align:start position:0% for some reason want you to 05:39:00.180 --> 05:39:02.330 align:start position:0% for some reason want you to um remember<05:39:00.540> this<05:39:01.020> generally<05:39:01.740> most<05:39:02.040> of<05:39:02.218> us 05:39:02.330 --> 05:39:02.340 align:start position:0% um remember this generally most of us 05:39:02.340 --> 05:39:03.890 align:start position:0% um remember this generally most of us will<05:39:02.520> just<05:39:02.700> look<05:39:02.940> speak<05:39:03.480> to<05:39:03.660> the<05:39:03.780> sales 05:39:03.890 --> 05:39:03.900 align:start position:0% will just look speak to the sales 05:39:03.900 --> 05:39:07.550 align:start position:0% will just look speak to the sales advisor<05:39:04.680> or<05:39:05.160> just<05:39:05.340> look<05:39:05.520> on<05:39:05.700> the<05:39:06.298> um<05:39:06.360> online<05:39:07.138> or 05:39:07.550 --> 05:39:07.560 align:start position:0% advisor or just look on the um online or 05:39:07.560 --> 05:39:09.708 align:start position:0% advisor or just look on the um online or some<05:39:07.740> documentation 05:39:09.708 --> 05:39:09.718 align:start position:0% some documentation 05:39:09.718 --> 05:39:14.830 align:start position:0% some documentation 10<05:39:10.560> gbase<05:39:11.400> er 05:39:14.830 --> 05:39:14.840 align:start position:0% 05:39:14.840 --> 05:39:18.890 align:start position:0% 802.3<05:39:15.840> AE<05:39:16.500> a<05:39:17.458> gigabit<05:39:18.000> over<05:39:18.298> single<05:39:18.780> mode 05:39:18.890 --> 05:39:18.900 align:start position:0% 802.3 AE a gigabit over single mode 05:39:18.900 --> 05:39:21.350 align:start position:0% 802.3 AE a gigabit over single mode fiber<05:39:19.500> optic<05:39:19.798> cabling<05:39:20.160> ER<05:39:20.760> stands<05:39:21.298> for 05:39:21.350 --> 05:39:21.360 align:start position:0% fiber optic cabling ER stands for 05:39:21.360 --> 05:39:24.470 align:start position:0% fiber optic cabling ER stands for extended<05:39:21.900> range<05:39:22.280> you<05:39:23.280> got<05:39:23.400> up<05:39:23.520> to<05:39:23.760> full<05:39:24.000> of<05:39:24.240> 40 05:39:24.470 --> 05:39:24.480 align:start position:0% extended range you got up to full of 40 05:39:24.480 --> 05:39:26.510 align:start position:0% extended range you got up to full of 40 kilometers<05:39:24.958> which<05:39:25.378> is<05:39:25.500> a<05:39:25.798> quite<05:39:26.160> a<05:39:26.280> nice 05:39:26.510 --> 05:39:26.520 align:start position:0% kilometers which is a quite a nice 05:39:26.520 --> 05:39:30.770 align:start position:0% kilometers which is a quite a nice distance<05:39:27.798> amazing<05:39:28.798> distance<05:39:28.980> in<05:39:29.400> fact 05:39:30.770 --> 05:39:30.780 align:start position:0% distance amazing distance in fact 05:39:30.780 --> 05:39:32.810 align:start position:0% distance amazing distance in fact uh<05:39:31.500> SW 05:39:32.810 --> 05:39:32.820 align:start position:0% uh SW 05:39:32.820 --> 05:39:34.970 align:start position:0% uh SW that<05:39:33.360> was<05:39:33.480> designed<05:39:33.900> for<05:39:34.200> use<05:39:34.378> over<05:39:34.620> a 05:39:34.970 --> 05:39:34.980 align:start position:0% that was designed for use over a 05:39:34.980 --> 05:39:38.030 align:start position:0% that was designed for use over a particular<05:39:35.218> type<05:39:35.580> of<05:39:35.820> Technology<05:39:36.680> sonnet<05:39:37.680> or 05:39:38.030 --> 05:39:38.040 align:start position:0% particular type of Technology sonnet or 05:39:38.040 --> 05:39:42.050 align:start position:0% particular type of Technology sonnet or sdh 05:39:42.050 --> 05:39:42.060 align:start position:0% 05:39:42.060 --> 05:39:45.650 align:start position:0% again<05:39:42.420> multi-mode<05:39:43.020> fiber<05:39:43.560> 300<05:39:44.100> meters<05:39:44.520> again 05:39:45.650 --> 05:39:45.660 align:start position:0% again multi-mode fiber 300 meters again 05:39:45.660 --> 05:39:47.810 align:start position:0% again multi-mode fiber 300 meters again all<05:39:46.080> right<05:39:46.200> so<05:39:46.500> we've<05:39:46.860> covered<05:39:47.218> a<05:39:47.458> few<05:39:47.580> of<05:39:47.760> the 05:39:47.810 --> 05:39:47.820 align:start position:0% all right so we've covered a few of the 05:39:47.820 --> 05:39:50.090 align:start position:0% all right so we've covered a few of the basics<05:39:48.120> of<05:39:48.240> ethernet<05:39:48.540> here<05:39:48.958> the<05:39:49.260> history<05:39:49.500> the 05:39:50.090 --> 05:39:50.100 align:start position:0% basics of ethernet here the history the 05:39:50.100 --> 05:39:54.470 align:start position:0% basics of ethernet here the history the name<05:39:50.340> the<05:39:51.240> standards<05:39:52.040> uh<05:39:53.040> the<05:39:53.280> oee<05:39:53.878> what<05:39:54.298> they 05:39:54.470 --> 05:39:54.480 align:start position:0% name the standards uh the oee what they 05:39:54.480 --> 05:39:55.970 align:start position:0% name the standards uh the oee what they do<05:39:54.600> in<05:39:55.080> brief 05:39:55.970 --> 05:39:55.980 align:start position:0% do in brief 05:39:55.980 --> 05:39:58.128 align:start position:0% do in brief I<05:39:56.400> recommend<05:39:57.240> you<05:39:57.360> have<05:39:57.480> a<05:39:57.600> look<05:39:57.660> in<05:39:57.840> your<05:39:57.958> own 05:39:58.128 --> 05:39:58.138 align:start position:0% I recommend you have a look in your own 05:39:58.138 --> 05:39:59.930 align:start position:0% I recommend you have a look in your own time<05:39:58.320> at<05:39:58.500> Wikipedia 05:39:59.930 --> 05:39:59.940 align:start position:0% time at Wikipedia 05:39:59.940 --> 05:40:01.910 align:start position:0% time at Wikipedia the<05:40:00.420> popularity<05:40:00.958> which<05:40:01.320> is<05:40:01.378> nearly<05:40:01.740> always 05:40:01.910 --> 05:40:01.920 align:start position:0% the popularity which is nearly always 05:40:01.920 --> 05:40:03.650 align:start position:0% the popularity which is nearly always the<05:40:02.218> fact<05:40:02.340> it's<05:40:02.580> the<05:40:02.820> standards<05:40:03.240> are<05:40:03.360> free<05:40:03.480> to 05:40:03.650 --> 05:40:03.660 align:start position:0% the fact it's the standards are free to 05:40:03.660 --> 05:40:05.810 align:start position:0% the fact it's the standards are free to use<05:40:03.840> and<05:40:04.080> it's<05:40:04.200> affordable<05:40:05.160> and<05:40:05.638> everyone 05:40:05.810 --> 05:40:05.820 align:start position:0% use and it's affordable and everyone 05:40:05.820 --> 05:40:08.030 align:start position:0% use and it's affordable and everyone else<05:40:06.060> is<05:40:06.180> using<05:40:06.540> the<05:40:06.660> same<05:40:06.780> standards 05:40:08.030 --> 05:40:08.040 align:start position:0% else is using the same standards 05:40:08.040 --> 05:40:10.368 align:start position:0% else is using the same standards baseband<05:40:08.820> the<05:40:09.000> Broadband<05:40:09.420> the<05:40:09.958> naming 05:40:10.368 --> 05:40:10.378 align:start position:0% baseband the Broadband the naming 05:40:10.378 --> 05:40:11.930 align:start position:0% baseband the Broadband the naming conventions<05:40:10.920> and<05:40:11.340> then<05:40:11.520> some<05:40:11.760> of<05:40:11.878> the 05:40:11.930 --> 05:40:11.940 align:start position:0% conventions and then some of the 05:40:11.940 --> 05:40:13.850 align:start position:0% conventions and then some of the different<05:40:12.120> standards<05:40:12.900> here 05:40:13.850 --> 05:40:13.860 align:start position:0% different standards here 05:40:13.860 --> 05:40:15.170 align:start position:0% different standards here you'll<05:40:14.520> need<05:40:14.638> to<05:40:14.700> know<05:40:14.820> the<05:40:15.000> different 05:40:15.170 --> 05:40:15.180 align:start position:0% you'll need to know the different 05:40:15.180 --> 05:40:17.330 align:start position:0% you'll need to know the different standards<05:40:15.780> which<05:40:16.080> uses<05:40:16.500> a<05:40:16.860> single<05:40:17.218> and 05:40:17.330 --> 05:40:17.340 align:start position:0% standards which uses a single and 05:40:17.340 --> 05:40:19.970 align:start position:0% standards which uses a single and multi-mode<05:40:17.878> how<05:40:18.780> long<05:40:19.378> um<05:40:19.378> you<05:40:19.620> can<05:40:19.740> have<05:40:19.860> a 05:40:19.970 --> 05:40:19.980 align:start position:0% multi-mode how long um you can have a 05:40:19.980 --> 05:40:21.650 align:start position:0% multi-mode how long um you can have a segment<05:40:20.280> that<05:40:20.458> lengths<05:40:21.120> and<05:40:21.180> that<05:40:21.360> kind<05:40:21.540> of 05:40:21.650 --> 05:40:21.660 align:start position:0% segment that lengths and that kind of 05:40:21.660 --> 05:40:22.368 align:start position:0% segment that lengths and that kind of thing 05:40:22.368 --> 05:40:22.378 align:start position:0% thing 05:40:22.378 --> 05:40:23.628 align:start position:0% thing all<05:40:22.740> right<05:40:22.920> so<05:40:23.040> that's<05:40:23.218> the<05:40:23.400> end<05:40:23.458> of<05:40:23.580> the 05:40:23.628 --> 05:40:23.638 align:start position:0% all right so that's the end of the 05:40:23.638 --> 05:40:30.420 align:start position:0% all right so that's the end of the presentation<05:40:24.060> thanks<05:40:24.540> for<05:40:24.718> watching 05:40:30.420 --> 05:40:30.430 align:start position:0% 05:40:30.430 --> 05:40:51.170 align:start position:0% [Music] 05:40:51.170 --> 05:40:51.180 align:start position:0% 05:40:51.180 --> 05:40:53.470 align:start position:0% Network<05:40:51.900> infrastructure<05:40:52.680> and<05:40:52.980> Design 05:40:53.470 --> 05:40:53.480 align:start position:0% Network infrastructure and Design 05:40:53.480 --> 05:40:57.230 align:start position:0% Network infrastructure and Design Network<05:40:54.480> models<05:40:55.260> the<05:40:55.740> OSI<05:40:56.160> model 05:40:57.230 --> 05:40:57.240 align:start position:0% Network models the OSI model 05:40:57.240 --> 05:40:58.788 align:start position:0% Network models the OSI model so<05:40:57.600> we're<05:40:57.660> going<05:40:57.840> to<05:40:57.958> discuss<05:40:58.260> two<05:40:58.620> different 05:40:58.788 --> 05:40:58.798 align:start position:0% so we're going to discuss two different 05:40:58.798 --> 05:41:00.530 align:start position:0% so we're going to discuss two different models<05:40:59.400> coming<05:40:59.638> up<05:40:59.878> here<05:41:00.060> and<05:41:00.240> the<05:41:00.420> first 05:41:00.530 --> 05:41:00.540 align:start position:0% models coming up here and the first 05:41:00.540 --> 05:41:02.628 align:start position:0% models coming up here and the first model<05:41:00.780> I<05:41:01.020> want<05:41:01.200> to<05:41:01.260> talk<05:41:01.378> about<05:41:01.560> is<05:41:02.040> the<05:41:02.218> OSI 05:41:02.628 --> 05:41:02.638 align:start position:0% model I want to talk about is the OSI 05:41:02.638 --> 05:41:04.970 align:start position:0% model I want to talk about is the OSI model<05:41:02.878> in<05:41:03.240> this<05:41:03.480> module<05:41:04.080> now<05:41:04.560> from<05:41:04.798> this 05:41:04.970 --> 05:41:04.980 align:start position:0% model in this module now from this 05:41:04.980 --> 05:41:06.470 align:start position:0% model in this module now from this lesson<05:41:05.280> you're<05:41:05.458> going<05:41:05.580> to<05:41:05.700> have<05:41:05.878> a<05:41:06.180> thorough 05:41:06.470 --> 05:41:06.480 align:start position:0% lesson you're going to have a thorough 05:41:06.480 --> 05:41:09.708 align:start position:0% lesson you're going to have a thorough understanding<05:41:07.138> of<05:41:07.798> each<05:41:08.100> of<05:41:08.280> the<05:41:08.520> layers<05:41:08.940> in 05:41:09.708 --> 05:41:09.718 align:start position:0% understanding of each of the layers in 05:41:09.718 --> 05:41:11.890 align:start position:0% understanding of each of the layers in this<05:41:09.900> module<05:41:10.260> and<05:41:10.440> there<05:41:10.680> are<05:41:10.860> seven<05:41:11.160> of<05:41:11.400> them 05:41:11.890 --> 05:41:11.900 align:start position:0% this module and there are seven of them 05:41:11.900 --> 05:41:14.330 align:start position:0% this module and there are seven of them and<05:41:12.900> we're<05:41:13.200> also<05:41:13.440> going<05:41:13.560> to<05:41:13.680> talk<05:41:13.798> about<05:41:13.980> how 05:41:14.330 --> 05:41:14.340 align:start position:0% and we're also going to talk about how 05:41:14.340 --> 05:41:16.610 align:start position:0% and we're also going to talk about how those<05:41:14.458> layers<05:41:14.820> communicate<05:41:15.480> some<05:41:16.320> of<05:41:16.500> the 05:41:16.610 --> 05:41:16.620 align:start position:0% those layers communicate some of the 05:41:16.620 --> 05:41:19.190 align:start position:0% those layers communicate some of the devices<05:41:16.980> that<05:41:17.520> operate<05:41:18.000> at<05:41:18.360> specific<05:41:18.718> layers 05:41:19.190 --> 05:41:19.200 align:start position:0% devices that operate at specific layers 05:41:19.200 --> 05:41:22.788 align:start position:0% devices that operate at specific layers specifically<05:41:20.160> layers<05:41:20.580> one<05:41:21.060> through<05:41:21.420> three 05:41:22.788 --> 05:41:22.798 align:start position:0% specifically layers one through three 05:41:22.798 --> 05:41:25.010 align:start position:0% specifically layers one through three and<05:41:23.458> some<05:41:23.700> of<05:41:23.760> the<05:41:23.878> protocols<05:41:24.420> that<05:41:24.660> operate 05:41:25.010 --> 05:41:25.020 align:start position:0% and some of the protocols that operate 05:41:25.020 --> 05:41:26.390 align:start position:0% and some of the protocols that operate on<05:41:25.320> some<05:41:25.500> of<05:41:25.620> these<05:41:25.740> layers<05:41:26.040> as<05:41:26.218> well 05:41:26.390 --> 05:41:26.400 align:start position:0% on some of these layers as well 05:41:26.400 --> 05:41:28.730 align:start position:0% on some of these layers as well specifically<05:41:27.120> the<05:41:27.420> upper<05:41:27.718> layers<05:41:28.020> we're<05:41:28.560> also 05:41:28.730 --> 05:41:28.740 align:start position:0% specifically the upper layers we're also 05:41:28.740 --> 05:41:29.690 align:start position:0% specifically the upper layers we're also going<05:41:28.860> to<05:41:28.860> have<05:41:28.980> a<05:41:29.040> better<05:41:29.160> understanding<05:41:29.520> of 05:41:29.690 --> 05:41:29.700 align:start position:0% going to have a better understanding of 05:41:29.700 --> 05:41:32.690 align:start position:0% going to have a better understanding of what<05:41:29.820> the<05:41:29.940> OSI<05:41:30.360> model<05:41:30.600> is<05:41:31.080> and<05:41:31.798> why<05:41:31.980> we<05:41:32.218> use<05:41:32.400> a 05:41:32.690 --> 05:41:32.700 align:start position:0% what the OSI model is and why we use a 05:41:32.700 --> 05:41:34.190 align:start position:0% what the OSI model is and why we use a layered<05:41:33.000> approach 05:41:34.190 --> 05:41:34.200 align:start position:0% layered approach 05:41:34.200 --> 05:41:36.288 align:start position:0% layered approach so<05:41:34.680> this<05:41:35.040> model<05:41:35.218> is<05:41:35.520> going<05:41:35.700> to<05:41:35.820> teach<05:41:36.060> us 05:41:36.288 --> 05:41:36.298 align:start position:0% so this model is going to teach us 05:41:36.298 --> 05:41:39.230 align:start position:0% so this model is going to teach us everything<05:41:36.840> we<05:41:37.138> need<05:41:37.320> to<05:41:37.440> know<05:41:37.620> about<05:41:38.218> the<05:41:38.760> OSI 05:41:39.230 --> 05:41:39.240 align:start position:0% everything we need to know about the OSI 05:41:39.240 --> 05:41:41.390 align:start position:0% everything we need to know about the OSI model<05:41:39.540> we're<05:41:40.320> going<05:41:40.440> to<05:41:40.500> begin<05:41:40.680> by<05:41:40.980> explaining 05:41:41.390 --> 05:41:41.400 align:start position:0% model we're going to begin by explaining 05:41:41.400 --> 05:41:44.030 align:start position:0% model we're going to begin by explaining exactly<05:41:41.878> what<05:41:42.240> the<05:41:42.540> OSI<05:41:42.958> model<05:41:43.260> is<05:41:43.500> and<05:41:43.798> what 05:41:44.030 --> 05:41:44.040 align:start position:0% exactly what the OSI model is and what 05:41:44.040 --> 05:41:46.490 align:start position:0% exactly what the OSI model is and what the<05:41:44.160> purpose<05:41:44.458> of<05:41:44.700> it<05:41:44.878> is<05:41:45.060> as<05:41:45.420> well<05:41:45.600> then<05:41:46.378> we're 05:41:46.490 --> 05:41:46.500 align:start position:0% the purpose of it is as well then we're 05:41:46.500 --> 05:41:47.810 align:start position:0% the purpose of it is as well then we're going<05:41:46.620> to<05:41:46.680> go<05:41:46.798> through<05:41:46.980> and<05:41:47.160> explain<05:41:47.340> each 05:41:47.810 --> 05:41:47.820 align:start position:0% going to go through and explain each 05:41:47.820 --> 05:41:51.288 align:start position:0% going to go through and explain each layer<05:41:48.180> from<05:41:48.718> layer<05:41:49.080> 1<05:41:49.320> the<05:41:49.798> physical<05:41:49.980> layer<05:41:50.520> to 05:41:51.288 --> 05:41:51.298 align:start position:0% layer from layer 1 the physical layer to 05:41:51.298 --> 05:41:54.410 align:start position:0% layer from layer 1 the physical layer to layer<05:41:51.780> 2<05:41:51.900> the<05:41:52.440> data<05:41:52.740> link<05:41:52.860> layer<05:41:53.280> later<05:41:54.000> three 05:41:54.410 --> 05:41:54.420 align:start position:0% layer 2 the data link layer later three 05:41:54.420 --> 05:41:57.830 align:start position:0% layer 2 the data link layer later three the<05:41:54.900> network<05:41:55.080> layer<05:41:55.638> layer<05:41:56.638> 4<05:41:56.940> transport 05:41:57.830 --> 05:41:57.840 align:start position:0% the network layer layer 4 transport 05:41:57.840 --> 05:42:02.090 align:start position:0% the network layer layer 4 transport layer<05:41:58.320> layer<05:41:59.100> 5<05:41:59.400> the<05:42:00.060> session<05:42:00.298> layer<05:42:01.138> layer<05:42:01.920> 6 05:42:02.090 --> 05:42:02.100 align:start position:0% layer layer 5 the session layer layer 6 05:42:02.100 --> 05:42:04.730 align:start position:0% layer layer 5 the session layer layer 6 the<05:42:02.400> presentation<05:42:02.940> layer<05:42:03.480> and<05:42:04.080> finally<05:42:04.320> layer 05:42:04.730 --> 05:42:04.740 align:start position:0% the presentation layer and finally layer 05:42:04.740 --> 05:42:07.610 align:start position:0% the presentation layer and finally layer 7<05:42:04.980> the<05:42:05.520> application<05:42:06.000> layer<05:42:06.900> we're<05:42:07.320> also<05:42:07.500> going 05:42:07.610 --> 05:42:07.620 align:start position:0% 7 the application layer we're also going 05:42:07.620 --> 05:42:09.650 align:start position:0% 7 the application layer we're also going to<05:42:07.680> discuss<05:42:07.980> some<05:42:08.280> of<05:42:08.400> the<05:42:08.580> protocols<05:42:09.360> and 05:42:09.650 --> 05:42:09.660 align:start position:0% to discuss some of the protocols and 05:42:09.660 --> 05:42:12.410 align:start position:0% to discuss some of the protocols and devices<05:42:10.020> that<05:42:10.500> operate<05:42:10.980> at<05:42:11.760> each<05:42:12.000> of<05:42:12.180> these 05:42:12.410 --> 05:42:12.420 align:start position:0% devices that operate at each of these 05:42:12.420 --> 05:42:14.628 align:start position:0% devices that operate at each of these layers<05:42:12.798> and<05:42:13.798> we're<05:42:14.100> also<05:42:14.400> going<05:42:14.458> to 05:42:14.628 --> 05:42:14.638 align:start position:0% layers and we're also going to 05:42:14.638 --> 05:42:17.570 align:start position:0% layers and we're also going to understand<05:42:14.760> how<05:42:15.360> communication<05:42:15.920> begins<05:42:16.920> and 05:42:17.570 --> 05:42:17.580 align:start position:0% understand how communication begins and 05:42:17.580 --> 05:42:21.770 align:start position:0% understand how communication begins and ends<05:42:18.000> through<05:42:18.900> these<05:42:19.260> layers<05:42:19.760> now<05:42:20.760> early<05:42:21.420> back 05:42:21.770 --> 05:42:21.780 align:start position:0% ends through these layers now early back 05:42:21.780 --> 05:42:24.948 align:start position:0% ends through these layers now early back in<05:42:22.260> the<05:42:22.378> 1980s<05:42:22.980> late<05:42:23.340> 70s<05:42:23.878> when<05:42:24.480> networking 05:42:24.948 --> 05:42:24.958 align:start position:0% in the 1980s late 70s when networking 05:42:24.958 --> 05:42:27.050 align:start position:0% in the 1980s late 70s when networking communication<05:42:25.740> between<05:42:26.160> devices<05:42:26.580> which<05:42:26.878> a 05:42:27.050 --> 05:42:27.060 align:start position:0% communication between devices which a 05:42:27.060 --> 05:42:28.730 align:start position:0% communication between devices which a lot<05:42:27.120> simpler<05:42:27.660> a<05:42:28.200> lot<05:42:28.320> of<05:42:28.440> brilliant 05:42:28.730 --> 05:42:28.740 align:start position:0% lot simpler a lot of brilliant 05:42:28.740 --> 05:42:31.190 align:start position:0% lot simpler a lot of brilliant individuals<05:42:29.280> from<05:42:29.638> the<05:42:29.820> iso<05:42:30.360> organization 05:42:31.190 --> 05:42:31.200 align:start position:0% individuals from the iso organization 05:42:31.200 --> 05:42:33.170 align:start position:0% individuals from the iso organization we've<05:42:31.560> seen<05:42:31.740> previously<05:42:32.400> or<05:42:32.940> the 05:42:33.170 --> 05:42:33.180 align:start position:0% we've seen previously or the 05:42:33.180 --> 05:42:34.730 align:start position:0% we've seen previously or the International<05:42:33.378> Organization<05:42:34.378> for 05:42:34.730 --> 05:42:34.740 align:start position:0% International Organization for 05:42:34.740 --> 05:42:36.890 align:start position:0% International Organization for standardization<05:42:35.458> came<05:42:36.180> together<05:42:36.360> and<05:42:36.780> they 05:42:36.890 --> 05:42:36.900 align:start position:0% standardization came together and they 05:42:36.900 --> 05:42:39.670 align:start position:0% standardization came together and they came<05:42:37.138> up<05:42:37.260> with<05:42:37.440> a<05:42:37.920> a<05:42:38.160> way<05:42:38.638> to<05:42:39.060> outline 05:42:39.670 --> 05:42:39.680 align:start position:0% came up with a a way to outline 05:42:39.680 --> 05:42:43.010 align:start position:0% came up with a a way to outline standardize<05:42:40.680> and<05:42:41.660> characterize<05:42:42.660> the 05:42:43.010 --> 05:42:43.020 align:start position:0% standardize and characterize the 05:42:43.020 --> 05:42:46.250 align:start position:0% standardize and characterize the functions<05:42:43.560> of<05:42:43.980> a<05:42:44.160> communication<05:42:44.638> system<05:42:45.260> or 05:42:46.250 --> 05:42:46.260 align:start position:0% functions of a communication system or 05:42:46.260 --> 05:42:48.470 align:start position:0% functions of a communication system or the<05:42:46.560> methods<05:42:47.040> by<05:42:47.280> which<05:42:47.520> computers<05:42:48.060> are<05:42:48.298> going 05:42:48.470 --> 05:42:48.480 align:start position:0% the methods by which computers are going 05:42:48.480 --> 05:42:50.868 align:start position:0% the methods by which computers are going to<05:42:48.660> communicate<05:42:49.320> in<05:42:49.980> a<05:42:50.100> network<05:42:50.280> environment 05:42:50.868 --> 05:42:50.878 align:start position:0% to communicate in a network environment 05:42:50.878 --> 05:42:53.690 align:start position:0% to communicate in a network environment so<05:42:51.420> they<05:42:51.600> came<05:42:51.780> up<05:42:51.900> with<05:42:52.320> this<05:42:52.560> OSI<05:42:53.160> model<05:42:53.458> and 05:42:53.690 --> 05:42:53.700 align:start position:0% so they came up with this OSI model and 05:42:53.700 --> 05:42:56.208 align:start position:0% so they came up with this OSI model and I<05:42:53.878> love<05:42:54.060> it<05:42:54.180> because<05:42:54.420> I<05:42:54.780> know<05:42:54.900> the<05:42:55.320> iso<05:42:55.980> made 05:42:56.208 --> 05:42:56.218 align:start position:0% I love it because I know the iso made 05:42:56.218 --> 05:42:59.090 align:start position:0% I love it because I know the iso made the<05:42:56.520> OSI<05:42:57.060> and<05:42:57.780> they<05:42:57.900> did<05:42:58.020> this<05:42:58.200> in<05:42:58.440> term<05:42:58.560> of 05:42:59.090 --> 05:42:59.100 align:start position:0% the OSI and they did this in term of 05:42:59.100 --> 05:43:02.628 align:start position:0% the OSI and they did this in term of abstract<05:42:59.760> layers<05:43:00.360> so<05:43:01.260> what<05:43:01.740> we<05:43:01.920> mean<05:43:02.040> by<05:43:02.340> these 05:43:02.628 --> 05:43:02.638 align:start position:0% abstract layers so what we mean by these 05:43:02.638 --> 05:43:04.490 align:start position:0% abstract layers so what we mean by these abstract<05:43:03.060> layers<05:43:03.420> and<05:43:03.600> here<05:43:03.780> they<05:43:03.958> are<05:43:04.138> again 05:43:04.490 --> 05:43:04.500 align:start position:0% abstract layers and here they are again 05:43:04.500 --> 05:43:06.830 align:start position:0% abstract layers and here they are again from<05:43:05.280> the<05:43:05.458> top<05:43:05.638> down<05:43:05.940> application<05:43:06.600> press 05:43:06.830 --> 05:43:06.840 align:start position:0% from the top down application press 05:43:06.840 --> 05:43:09.170 align:start position:0% from the top down application press presentation<05:43:07.560> session<05:43:08.100> transport<05:43:08.638> layer 05:43:09.170 --> 05:43:09.180 align:start position:0% presentation session transport layer 05:43:09.180 --> 05:43:11.150 align:start position:0% presentation session transport layer data<05:43:09.480> link<05:43:09.600> physical<05:43:09.900> and<05:43:10.560> just<05:43:10.740> so<05:43:10.860> we<05:43:11.040> don't 05:43:11.150 --> 05:43:11.160 align:start position:0% data link physical and just so we don't 05:43:11.160 --> 05:43:14.150 align:start position:0% data link physical and just so we don't get<05:43:11.340> confused<05:43:12.320> the<05:43:13.320> first<05:43:13.500> layer<05:43:13.798> is<05:43:13.980> actually 05:43:14.150 --> 05:43:14.160 align:start position:0% get confused the first layer is actually 05:43:14.160 --> 05:43:16.490 align:start position:0% get confused the first layer is actually here<05:43:14.400> at<05:43:14.580> the<05:43:14.700> bottom<05:43:15.000> and<05:43:15.540> the<05:43:15.718> last<05:43:15.900> layer<05:43:16.320> is 05:43:16.490 --> 05:43:16.500 align:start position:0% here at the bottom and the last layer is 05:43:16.500 --> 05:43:18.948 align:start position:0% here at the bottom and the last layer is here<05:43:16.980> at<05:43:17.160> the<05:43:17.280> top<05:43:17.400> and<05:43:17.700> that<05:43:17.878> and<05:43:18.360> viewing 05:43:18.948 --> 05:43:18.958 align:start position:0% here at the top and that and viewing 05:43:18.958 --> 05:43:21.590 align:start position:0% here at the top and that and viewing this<05:43:19.138> we<05:43:19.500> call<05:43:19.620> this<05:43:19.860> a<05:43:20.160> top 05:43:21.590 --> 05:43:21.600 align:start position:0% this we call this a top 05:43:21.600 --> 05:43:24.170 align:start position:0% this we call this a top down<05:43:22.080> approach<05:43:22.620> as<05:43:23.160> opposed<05:43:23.458> to<05:43:23.458> a<05:43:23.760> bottom-up 05:43:24.170 --> 05:43:24.180 align:start position:0% down approach as opposed to a bottom-up 05:43:24.180 --> 05:43:26.930 align:start position:0% down approach as opposed to a bottom-up approach 05:43:26.930 --> 05:43:26.940 align:start position:0% 05:43:26.940 --> 05:43:28.368 align:start position:0% and<05:43:27.420> these 05:43:28.368 --> 05:43:28.378 align:start position:0% and these 05:43:28.378 --> 05:43:31.430 align:start position:0% and these abstract<05:43:29.040> layers<05:43:29.580> outline<05:43:30.240> the<05:43:30.540> functions<05:43:31.138> of 05:43:31.430 --> 05:43:31.440 align:start position:0% abstract layers outline the functions of 05:43:31.440 --> 05:43:34.010 align:start position:0% abstract layers outline the functions of the<05:43:31.620> communications<05:43:31.980> process<05:43:32.580> but<05:43:33.420> they<05:43:33.780> hide 05:43:34.010 --> 05:43:34.020 align:start position:0% the communications process but they hide 05:43:34.020 --> 05:43:35.810 align:start position:0% the communications process but they hide exactly<05:43:34.620> specifically<05:43:35.280> how<05:43:35.638> they're 05:43:35.810 --> 05:43:35.820 align:start position:0% exactly specifically how they're 05:43:35.820 --> 05:43:38.208 align:start position:0% exactly specifically how they're implemented<05:43:36.480> in<05:43:36.840> each<05:43:37.020> layer<05:43:37.378> in<05:43:37.920> other<05:43:38.040> words 05:43:38.208 --> 05:43:38.218 align:start position:0% implemented in each layer in other words 05:43:38.218 --> 05:43:41.150 align:start position:0% implemented in each layer in other words this<05:43:39.060> really<05:43:39.240> attempts<05:43:39.718> to<05:43:39.900> simplify<05:43:40.620> and 05:43:41.150 --> 05:43:41.160 align:start position:0% this really attempts to simplify and 05:43:41.160 --> 05:43:43.368 align:start position:0% this really attempts to simplify and sometimes<05:43:41.540> oversimplify<05:43:42.540> exactly<05:43:43.080> how 05:43:43.368 --> 05:43:43.378 align:start position:0% sometimes oversimplify exactly how 05:43:43.378 --> 05:43:44.690 align:start position:0% sometimes oversimplify exactly how everything<05:43:43.740> in<05:43:44.040> the<05:43:44.218> network<05:43:44.340> is 05:43:44.690 --> 05:43:44.700 align:start position:0% everything in the network is 05:43:44.700 --> 05:43:47.930 align:start position:0% everything in the network is communicated<05:43:45.360> so<05:43:46.138> let's<05:43:46.798> say<05:43:47.040> that<05:43:47.340> we<05:43:47.638> want 05:43:47.930 --> 05:43:47.940 align:start position:0% communicated so let's say that we want 05:43:47.940 --> 05:43:50.690 align:start position:0% communicated so let's say that we want to<05:43:48.180> establish<05:43:48.660> a<05:43:49.020> highway<05:43:49.200> more<05:43:50.160> so<05:43:50.340> we<05:43:50.580> really 05:43:50.690 --> 05:43:50.700 align:start position:0% to establish a highway more so we really 05:43:50.700 --> 05:43:52.610 align:start position:0% to establish a highway more so we really want<05:43:50.940> to<05:43:51.058> build<05:43:51.240> a<05:43:51.718> brand<05:43:51.840> new<05:43:52.080> type<05:43:52.440> of 05:43:52.610 --> 05:43:52.620 align:start position:0% want to build a brand new type of 05:43:52.620 --> 05:43:54.830 align:start position:0% want to build a brand new type of vehicle<05:43:53.100> designed<05:43:53.940> specifically<05:43:54.480> to<05:43:54.660> be 05:43:54.830 --> 05:43:54.840 align:start position:0% vehicle designed specifically to be 05:43:54.840 --> 05:43:58.190 align:start position:0% vehicle designed specifically to be driven<05:43:55.200> on<05:43:55.620> this<05:43:56.040> very<05:43:56.340> specific<05:43:56.878> Highway<05:43:57.420> and 05:43:58.190 --> 05:43:58.200 align:start position:0% driven on this very specific Highway and 05:43:58.200 --> 05:43:59.628 align:start position:0% driven on this very specific Highway and we're<05:43:58.378> going<05:43:58.558> to<05:43:58.740> have<05:43:58.860> to<05:43:59.040> do<05:43:59.160> it<05:43:59.280> from<05:43:59.520> the 05:43:59.628 --> 05:43:59.638 align:start position:0% we're going to have to do it from the 05:43:59.638 --> 05:44:02.510 align:start position:0% we're going to have to do it from the ground<05:43:59.820> up<05:44:00.240> so<05:44:00.958> let's<05:44:01.200> call<05:44:01.378> this<05:44:01.558> vehicle<05:44:01.980> a 05:44:02.510 --> 05:44:02.520 align:start position:0% ground up so let's call this vehicle a 05:44:02.520 --> 05:44:03.410 align:start position:0% ground up so let's call this vehicle a bus 05:44:03.410 --> 05:44:03.420 align:start position:0% bus 05:44:03.420 --> 05:44:05.990 align:start position:0% bus not<05:44:04.080> only<05:44:04.200> do<05:44:04.440> we<05:44:04.680> want<05:44:04.980> this<05:44:05.340> bus<05:44:05.520> to<05:44:05.820> be<05:44:05.940> able 05:44:05.990 --> 05:44:06.000 align:start position:0% not only do we want this bus to be able 05:44:06.000 --> 05:44:08.208 align:start position:0% not only do we want this bus to be able to<05:44:06.180> run<05:44:06.360> on<05:44:06.718> any<05:44:06.958> of<05:44:07.138> the<05:44:07.260> existing<05:44:07.620> highways 05:44:08.208 --> 05:44:08.218 align:start position:0% to run on any of the existing highways 05:44:08.218 --> 05:44:10.190 align:start position:0% to run on any of the existing highways or<05:44:08.340> they're<05:44:08.520> out<05:44:08.760> there<05:44:08.940> but<05:44:09.540> we<05:44:09.780> also<05:44:10.020> want 05:44:10.190 --> 05:44:10.200 align:start position:0% or they're out there but we also want 05:44:10.200 --> 05:44:11.930 align:start position:0% or they're out there but we also want the<05:44:10.378> bus<05:44:10.500> to<05:44:10.740> be<05:44:10.860> able<05:44:10.980> to<05:44:11.160> use<05:44:11.340> the<05:44:11.760> already 05:44:11.930 --> 05:44:11.940 align:start position:0% the bus to be able to use the already 05:44:11.940 --> 05:44:14.750 align:start position:0% the bus to be able to use the already existing<05:44:12.540> bus<05:44:12.958> stations<05:44:13.558> as<05:44:13.798> well<05:44:13.980> so<05:44:14.638> in 05:44:14.750 --> 05:44:14.760 align:start position:0% existing bus stations as well so in 05:44:14.760 --> 05:44:16.670 align:start position:0% existing bus stations as well so in order<05:44:14.940> to<05:44:15.120> do<05:44:15.360> this<05:44:15.600> we<05:44:16.138> need<05:44:16.320> to<05:44:16.440> understand 05:44:16.670 --> 05:44:16.680 align:start position:0% order to do this we need to understand 05:44:16.680 --> 05:44:19.190 align:start position:0% order to do this we need to understand exactly<05:44:17.340> what<05:44:17.700> we<05:44:17.940> already<05:44:18.058> have<05:44:18.480> meaning 05:44:19.190 --> 05:44:19.200 align:start position:0% exactly what we already have meaning 05:44:19.200 --> 05:44:21.288 align:start position:0% exactly what we already have meaning what<05:44:19.620> the<05:44:19.798> standards<05:44:20.218> are<05:44:20.400> already<05:44:20.760> in<05:44:21.120> place 05:44:21.288 --> 05:44:21.298 align:start position:0% what the standards are already in place 05:44:21.298 --> 05:44:23.868 align:start position:0% what the standards are already in place for<05:44:21.958> a<05:44:22.320> highway<05:44:22.500> we<05:44:23.340> also<05:44:23.520> need<05:44:23.638> to<05:44:23.760> know 05:44:23.868 --> 05:44:23.878 align:start position:0% for a highway we also need to know 05:44:23.878 --> 05:44:26.208 align:start position:0% for a highway we also need to know everything<05:44:24.180> about<05:44:24.480> bus<05:44:24.780> stations<05:44:25.378> and 05:44:26.208 --> 05:44:26.218 align:start position:0% everything about bus stations and 05:44:26.218 --> 05:44:28.250 align:start position:0% everything about bus stations and everything<05:44:26.520> about<05:44:26.820> the<05:44:27.298> infrastructure<05:44:27.958> of 05:44:28.250 --> 05:44:28.260 align:start position:0% everything about the infrastructure of 05:44:28.260 --> 05:44:30.310 align:start position:0% everything about the infrastructure of the<05:44:28.440> highway<05:44:28.558> system<05:44:29.040> that<05:44:29.400> already<05:44:29.580> exists 05:44:30.310 --> 05:44:30.320 align:start position:0% the highway system that already exists 05:44:30.320 --> 05:44:33.048 align:start position:0% the highway system that already exists regardless<05:44:31.320> of<05:44:31.500> whether<05:44:31.680> we<05:44:32.040> actually<05:44:32.218> have 05:44:33.048 --> 05:44:33.058 align:start position:0% regardless of whether we actually have 05:44:33.058 --> 05:44:34.788 align:start position:0% regardless of whether we actually have to<05:44:33.360> build<05:44:33.660> the<05:44:33.958> highway 05:44:34.788 --> 05:44:34.798 align:start position:0% to build the highway 05:44:34.798 --> 05:44:36.948 align:start position:0% to build the highway we<05:44:35.400> still<05:44:35.580> need<05:44:35.760> to<05:44:35.940> understand<05:44:36.120> everything 05:44:36.948 --> 05:44:36.958 align:start position:0% we still need to understand everything 05:44:36.958 --> 05:44:38.930 align:start position:0% we still need to understand everything that<05:44:37.320> relates<05:44:37.680> to<05:44:37.920> highways<05:44:38.458> and<05:44:38.700> their 05:44:38.930 --> 05:44:38.940 align:start position:0% that relates to highways and their 05:44:38.940 --> 05:44:41.448 align:start position:0% that relates to highways and their designs<05:44:39.480> uh<05:44:40.200> to<05:44:40.440> the<05:44:40.620> materials<05:44:41.160> the 05:44:41.448 --> 05:44:41.458 align:start position:0% designs uh to the materials the 05:44:41.458 --> 05:44:44.390 align:start position:0% designs uh to the materials the limitations<05:44:41.878> and<05:44:42.360> so<05:44:42.480> on<05:44:42.660> so<05:44:43.558> this<05:44:43.920> way<05:44:44.100> when 05:44:44.390 --> 05:44:44.400 align:start position:0% limitations and so on so this way when 05:44:44.400 --> 05:44:46.670 align:start position:0% limitations and so on so this way when we're<05:44:44.580> designing<05:44:45.120> our<05:44:45.360> brand<05:44:45.480> new<05:44:45.660> bus<05:44:45.958> we<05:44:46.500> can 05:44:46.670 --> 05:44:46.680 align:start position:0% we're designing our brand new bus we can 05:44:46.680 --> 05:44:48.590 align:start position:0% we're designing our brand new bus we can ensure<05:44:46.980> that<05:44:47.280> it<05:44:47.458> still<05:44:47.638> can<05:44:47.940> drive<05:44:48.180> and 05:44:48.590 --> 05:44:48.600 align:start position:0% ensure that it still can drive and 05:44:48.600 --> 05:44:50.750 align:start position:0% ensure that it still can drive and operate<05:44:49.020> on<05:44:49.378> older<05:44:49.740> highways<05:44:50.218> not<05:44:50.400> to<05:44:50.580> mention 05:44:50.750 --> 05:44:50.760 align:start position:0% operate on older highways not to mention 05:44:50.760 --> 05:44:53.390 align:start position:0% operate on older highways not to mention new<05:44:51.180> highways<05:44:51.780> and<05:44:52.440> that<05:44:52.620> our<05:44:52.798> bus<05:44:52.980> is<05:44:53.160> going 05:44:53.390 --> 05:44:53.400 align:start position:0% new highways and that our bus is going 05:44:53.400 --> 05:44:56.090 align:start position:0% new highways and that our bus is going to<05:44:53.580> interact<05:44:54.420> uh<05:44:55.080> properly<05:44:55.500> with<05:44:55.798> the<05:44:55.980> other 05:44:56.090 --> 05:44:56.100 align:start position:0% to interact uh properly with the other 05:44:56.100 --> 05:44:58.310 align:start position:0% to interact uh properly with the other buses<05:44:56.580> and<05:44:56.760> other<05:44:57.000> vehicles<05:44:57.600> that<05:44:57.840> are<05:44:57.958> on<05:44:58.200> the 05:44:58.310 --> 05:44:58.320 align:start position:0% buses and other vehicles that are on the 05:44:58.320 --> 05:45:00.770 align:start position:0% buses and other vehicles that are on the road<05:44:58.440> the<05:44:58.860> other<05:44:58.980> benefit<05:44:59.280> here<05:44:59.760> is<05:45:00.298> if<05:45:00.600> I'm 05:45:00.770 --> 05:45:00.780 align:start position:0% road the other benefit here is if I'm 05:45:00.780 --> 05:45:02.750 align:start position:0% road the other benefit here is if I'm designing<05:45:01.260> this<05:45:01.500> bus<05:45:01.740> and<05:45:02.040> I<05:45:02.280> break<05:45:02.400> it<05:45:02.638> down 05:45:02.750 --> 05:45:02.760 align:start position:0% designing this bus and I break it down 05:45:02.760 --> 05:45:05.510 align:start position:0% designing this bus and I break it down into<05:45:03.058> different<05:45:03.360> layers<05:45:04.020> seven<05:45:04.440> of<05:45:04.740> them<05:45:04.860> I 05:45:05.510 --> 05:45:05.520 align:start position:0% into different layers seven of them I 05:45:05.520 --> 05:45:07.850 align:start position:0% into different layers seven of them I only<05:45:05.700> have<05:45:05.940> to<05:45:06.120> worry<05:45:06.298> about<05:45:06.540> one<05:45:06.900> part<05:45:07.138> for 05:45:07.850 --> 05:45:07.860 align:start position:0% only have to worry about one part for 05:45:07.860 --> 05:45:10.010 align:start position:0% only have to worry about one part for instance<05:45:08.040> there<05:45:08.340> might<05:45:08.458> be<05:45:08.580> someone<05:45:08.878> who<05:45:09.480> is 05:45:10.010 --> 05:45:10.020 align:start position:0% instance there might be someone who is 05:45:10.020 --> 05:45:12.708 align:start position:0% instance there might be someone who is responsible<05:45:10.620> for<05:45:11.218> say<05:45:11.520> the<05:45:11.760> wheels<05:45:12.180> and<05:45:12.540> there 05:45:12.708 --> 05:45:12.718 align:start position:0% responsible for say the wheels and there 05:45:12.718 --> 05:45:14.990 align:start position:0% responsible for say the wheels and there might<05:45:12.900> be<05:45:13.020> someone<05:45:13.260> else<05:45:13.620> who's<05:45:14.280> responsible 05:45:14.990 --> 05:45:15.000 align:start position:0% might be someone else who's responsible 05:45:15.000 --> 05:45:19.010 align:start position:0% might be someone else who's responsible for<05:45:15.600> uh<05:45:16.500> say<05:45:17.000> the<05:45:18.000> body<05:45:18.240> and<05:45:18.660> there<05:45:18.780> might<05:45:18.900> be 05:45:19.010 --> 05:45:19.020 align:start position:0% for uh say the body and there might be 05:45:19.020 --> 05:45:20.990 align:start position:0% for uh say the body and there might be someone<05:45:19.200> else<05:45:19.378> who's<05:45:19.740> responsible<05:45:20.340> for<05:45:20.760> the 05:45:20.990 --> 05:45:21.000 align:start position:0% someone else who's responsible for the 05:45:21.000 --> 05:45:22.250 align:start position:0% someone else who's responsible for the highway<05:45:21.240> and<05:45:21.600> someone<05:45:21.780> else<05:45:22.020> who's 05:45:22.250 --> 05:45:22.260 align:start position:0% highway and someone else who's 05:45:22.260 --> 05:45:25.010 align:start position:0% highway and someone else who's responsible<05:45:22.860> for<05:45:23.760> the<05:45:23.940> bus<05:45:24.120> stop<05:45:24.360> and<05:45:24.660> so<05:45:24.900> on 05:45:25.010 --> 05:45:25.020 align:start position:0% responsible for the bus stop and so on 05:45:25.020 --> 05:45:27.048 align:start position:0% responsible for the bus stop and so on and<05:45:25.200> so<05:45:25.378> forth<05:45:25.680> this<05:45:26.160> way<05:45:26.280> I<05:45:26.458> can<05:45:26.638> fragment 05:45:27.048 --> 05:45:27.058 align:start position:0% and so forth this way I can fragment 05:45:27.058 --> 05:45:28.490 align:start position:0% and so forth this way I can fragment everything<05:45:27.480> out<05:45:27.840> and<05:45:28.080> give<05:45:28.260> everyone 05:45:28.490 --> 05:45:28.500 align:start position:0% everything out and give everyone 05:45:28.500 --> 05:45:31.070 align:start position:0% everything out and give everyone specific<05:45:29.100> jobs<05:45:29.458> and<05:45:30.000> if<05:45:30.180> a<05:45:30.360> problem<05:45:30.600> occurs 05:45:31.070 --> 05:45:31.080 align:start position:0% specific jobs and if a problem occurs 05:45:31.080 --> 05:45:33.650 align:start position:0% specific jobs and if a problem occurs with<05:45:31.440> the<05:45:31.740> bus<05:45:31.920> then<05:45:32.760> I<05:45:33.058> can<05:45:33.180> go<05:45:33.360> to<05:45:33.480> the 05:45:33.650 --> 05:45:33.660 align:start position:0% with the bus then I can go to the 05:45:33.660 --> 05:45:36.530 align:start position:0% with the bus then I can go to the specific<05:45:33.958> person<05:45:34.378> who<05:45:34.740> with<05:45:35.340> whom<05:45:35.580> who<05:45:36.360> is 05:45:36.530 --> 05:45:36.540 align:start position:0% specific person who with whom who is 05:45:36.540 --> 05:45:38.510 align:start position:0% specific person who with whom who is most<05:45:36.780> familiar<05:45:37.080> with<05:45:37.378> that<05:45:37.620> section<05:45:37.980> or<05:45:38.340> that 05:45:38.510 --> 05:45:38.520 align:start position:0% most familiar with that section or that 05:45:38.520 --> 05:45:40.850 align:start position:0% most familiar with that section or that layer<05:45:38.940> this<05:45:39.420> is<05:45:39.480> the<05:45:39.660> benefit<05:45:39.840> to<05:45:40.260> a<05:45:40.500> layered 05:45:40.850 --> 05:45:40.860 align:start position:0% layer this is the benefit to a layered 05:45:40.860 --> 05:45:42.650 align:start position:0% layer this is the benefit to a layered approach<05:45:41.100> to<05:45:41.400> creating<05:45:41.700> something 05:45:42.650 --> 05:45:42.660 align:start position:0% approach to creating something 05:45:42.660 --> 05:45:44.750 align:start position:0% approach to creating something so<05:45:43.080> that<05:45:43.200> being<05:45:43.378> said<05:45:43.620> let's<05:45:44.100> talk<05:45:44.280> about<05:45:44.400> the 05:45:44.750 --> 05:45:44.760 align:start position:0% so that being said let's talk about the 05:45:44.760 --> 05:45:46.730 align:start position:0% so that being said let's talk about the very<05:45:45.000> first<05:45:45.240> layer<05:45:45.660> layer<05:45:46.020> one 05:45:46.730 --> 05:45:46.740 align:start position:0% very first layer layer one 05:45:46.740 --> 05:45:49.610 align:start position:0% very first layer layer one so<05:45:47.160> layer<05:45:47.458> one<05:45:47.580> is<05:45:47.940> the<05:45:48.298> physical<05:45:48.540> layer<05:45:49.080> the 05:45:49.610 --> 05:45:49.620 align:start position:0% so layer one is the physical layer the 05:45:49.620 --> 05:45:52.070 align:start position:0% so layer one is the physical layer the this<05:45:49.740> is<05:45:49.920> the<05:45:50.160> actual<05:45:50.638> physical<05:45:51.120> media<05:45:51.840> the 05:45:52.070 --> 05:45:52.080 align:start position:0% this is the actual physical media the 05:45:52.080 --> 05:45:54.770 align:start position:0% this is the actual physical media the cables<05:45:52.558> the<05:45:52.860> wires<05:45:53.340> this<05:45:54.000> is<05:45:54.120> the<05:45:54.298> means<05:45:54.600> by 05:45:54.770 --> 05:45:54.780 align:start position:0% cables the wires this is the means by 05:45:54.780 --> 05:45:57.830 align:start position:0% cables the wires this is the means by which<05:45:54.958> the<05:45:55.320> bits<05:45:55.740> go<05:45:56.280> from<05:45:56.638> one<05:45:57.000> point<05:45:57.298> to 05:45:57.830 --> 05:45:57.840 align:start position:0% which the bits go from one point to 05:45:57.840 --> 05:46:02.690 align:start position:0% which the bits go from one point to another<05:45:58.340> so<05:45:59.340> for<05:46:00.000> the<05:46:00.180> actual<05:46:00.540> cable<05:46:01.160> uh<05:46:02.160> the 05:46:02.690 --> 05:46:02.700 align:start position:0% another so for the actual cable uh the 05:46:02.700 --> 05:46:05.090 align:start position:0% another so for the actual cable uh the infrared<05:46:03.180> connection<05:46:03.600> the<05:46:04.200> radio<05:46:04.378> frequency 05:46:05.090 --> 05:46:05.100 align:start position:0% infrared connection the radio frequency 05:46:05.100 --> 05:46:08.510 align:start position:0% infrared connection the radio frequency even<05:46:05.940> Wi-Fi<05:46:06.540> all<05:46:07.378> of<05:46:07.500> these<05:46:07.740> reference<05:46:08.218> the 05:46:08.510 --> 05:46:08.520 align:start position:0% even Wi-Fi all of these reference the 05:46:08.520 --> 05:46:10.610 align:start position:0% even Wi-Fi all of these reference the layer<05:46:08.940> or<05:46:09.058> the<05:46:09.240> pathway<05:46:09.718> that<05:46:10.080> the<05:46:10.200> data<05:46:10.500> is 05:46:10.610 --> 05:46:10.620 align:start position:0% layer or the pathway that the data is 05:46:10.620 --> 05:46:12.708 align:start position:0% layer or the pathway that the data is going<05:46:10.798> to<05:46:10.980> take<05:46:11.100> so<05:46:11.940> to<05:46:12.058> take<05:46:12.180> a<05:46:12.298> look<05:46:12.420> in<05:46:12.600> this 05:46:12.708 --> 05:46:12.718 align:start position:0% going to take so to take a look in this 05:46:12.718 --> 05:46:14.090 align:start position:0% going to take so to take a look in this in<05:46:12.900> the<05:46:13.080> way<05:46:13.138> that<05:46:13.320> we<05:46:13.440> were<05:46:13.558> talking<05:46:13.740> about<05:46:13.860> it 05:46:14.090 --> 05:46:14.100 align:start position:0% in the way that we were talking about it 05:46:14.100 --> 05:46:16.910 align:start position:0% in the way that we were talking about it with<05:46:14.218> our<05:46:14.400> bus<05:46:14.580> and<05:46:15.298> our<05:46:15.480> Highway<05:46:15.660> setting<05:46:16.260> if 05:46:16.910 --> 05:46:16.920 align:start position:0% with our bus and our Highway setting if 05:46:16.920 --> 05:46:19.548 align:start position:0% with our bus and our Highway setting if our<05:46:17.160> main<05:46:17.400> concern<05:46:17.820> is<05:46:18.240> building<05:46:18.660> our<05:46:19.138> buses 05:46:19.548 --> 05:46:19.558 align:start position:0% our main concern is building our buses 05:46:19.558 --> 05:46:21.530 align:start position:0% our main concern is building our buses we<05:46:20.100> need<05:46:20.218> to<05:46:20.400> look<05:46:20.520> at<05:46:20.760> all<05:46:21.000> of<05:46:21.120> the<05:46:21.360> other 05:46:21.530 --> 05:46:21.540 align:start position:0% we need to look at all of the other 05:46:21.540 --> 05:46:23.510 align:start position:0% we need to look at all of the other vehicles<05:46:22.020> on<05:46:22.378> the<05:46:22.500> road<05:46:22.680> we<05:46:23.280> need<05:46:23.400> to 05:46:23.510 --> 05:46:23.520 align:start position:0% vehicles on the road we need to 05:46:23.520 --> 05:46:26.590 align:start position:0% vehicles on the road we need to understand<05:46:23.760> their<05:46:24.480> size<05:46:24.718> their<05:46:25.200> shape<05:46:25.520> other 05:46:26.590 --> 05:46:26.600 align:start position:0% understand their size their shape other 05:46:26.600 --> 05:46:29.810 align:start position:0% understand their size their shape other characteristics<05:46:27.600> and<05:46:28.080> so<05:46:28.260> on<05:46:28.440> so<05:46:29.100> that<05:46:29.340> way<05:46:29.458> we 05:46:29.810 --> 05:46:29.820 align:start position:0% characteristics and so on so that way we 05:46:29.820 --> 05:46:32.570 align:start position:0% characteristics and so on so that way we understand<05:46:30.200> how<05:46:31.200> our<05:46:31.378> bus<05:46:31.558> can<05:46:31.860> use<05:46:32.040> the<05:46:32.340> same 05:46:32.570 --> 05:46:32.580 align:start position:0% understand how our bus can use the same 05:46:32.580 --> 05:46:35.208 align:start position:0% understand how our bus can use the same tracks<05:46:33.058> the<05:46:33.360> other<05:46:33.540> vehicles<05:46:34.020> are<05:46:34.200> using<05:46:34.500> so 05:46:35.208 --> 05:46:35.218 align:start position:0% tracks the other vehicles are using so 05:46:35.218 --> 05:46:37.548 align:start position:0% tracks the other vehicles are using so here<05:46:35.400> on<05:46:35.580> layer<05:46:35.940> one<05:46:36.058> we<05:46:36.540> have<05:46:36.660> the<05:46:36.900> path<05:46:37.138> the 05:46:37.548 --> 05:46:37.558 align:start position:0% here on layer one we have the path the 05:46:37.558 --> 05:46:40.610 align:start position:0% here on layer one we have the path the road<05:46:37.860> used<05:46:38.280> for<05:46:38.700> communication<05:46:39.360> again<05:46:40.200> this 05:46:40.610 --> 05:46:40.620 align:start position:0% road used for communication again this 05:46:40.620 --> 05:46:44.270 align:start position:0% road used for communication again this is<05:46:40.798> the<05:46:41.280> wire<05:46:41.540> the<05:46:42.540> Bluetooth<05:46:42.840> fiber<05:46:43.680> copper 05:46:44.270 --> 05:46:44.280 align:start position:0% is the wire the Bluetooth fiber copper 05:46:44.280 --> 05:46:47.390 align:start position:0% is the wire the Bluetooth fiber copper the<05:46:44.820> Wi-Fi<05:46:45.240> whatever<05:46:46.020> means<05:46:46.620> there<05:46:46.798> is<05:46:46.980> that 05:46:47.390 --> 05:46:47.400 align:start position:0% the Wi-Fi whatever means there is that 05:46:47.400 --> 05:46:49.548 align:start position:0% the Wi-Fi whatever means there is that physically<05:46:47.878> the<05:46:48.298> bits<05:46:48.718> the<05:46:49.020> ones<05:46:49.200> and<05:46:49.320> zeros 05:46:49.548 --> 05:46:49.558 align:start position:0% physically the bits the ones and zeros 05:46:49.558 --> 05:46:54.230 align:start position:0% physically the bits the ones and zeros rows<05:46:50.218> are<05:46:50.700> going<05:46:51.000> over<05:46:51.740> this<05:46:52.740> media<05:46:53.638> so<05:46:54.058> the 05:46:54.230 --> 05:46:54.240 align:start position:0% rows are going over this media so the 05:46:54.240 --> 05:46:56.208 align:start position:0% rows are going over this media so the terminology<05:46:54.780> for<05:46:55.138> the<05:46:55.320> information<05:46:55.558> is 05:46:56.208 --> 05:46:56.218 align:start position:0% terminology for the information is 05:46:56.218 --> 05:46:58.250 align:start position:0% terminology for the information is considered<05:46:56.700> simply<05:46:57.058> the<05:46:57.298> bits<05:46:57.660> because<05:46:57.900> we're 05:46:58.250 --> 05:46:58.260 align:start position:0% considered simply the bits because we're 05:46:58.260 --> 05:47:00.048 align:start position:0% considered simply the bits because we're actually<05:46:58.500> transmitting<05:46:59.218> the<05:46:59.400> raw<05:46:59.638> one<05:46:59.820> and 05:47:00.048 --> 05:47:00.058 align:start position:0% actually transmitting the raw one and 05:47:00.058 --> 05:47:02.570 align:start position:0% actually transmitting the raw one and ones<05:47:00.420> and<05:47:00.540> zeros<05:47:00.840> we're<05:47:01.080> not<05:47:01.320> dealing<05:47:02.218> here 05:47:02.570 --> 05:47:02.580 align:start position:0% ones and zeros we're not dealing here 05:47:02.580 --> 05:47:04.850 align:start position:0% ones and zeros we're not dealing here with<05:47:03.240> what<05:47:03.600> the<05:47:03.780> information<05:47:03.958> is<05:47:04.558> we're 05:47:04.850 --> 05:47:04.860 align:start position:0% with what the information is we're 05:47:04.860 --> 05:47:07.090 align:start position:0% with what the information is we're dealing<05:47:05.160> with<05:47:05.280> it<05:47:05.400> at<05:47:05.638> the<05:47:05.878> most<05:47:06.120> Electrical 05:47:07.090 --> 05:47:07.100 align:start position:0% dealing with it at the most Electrical 05:47:07.100 --> 05:47:10.368 align:start position:0% dealing with it at the most Electrical uh<05:47:08.100> basic<05:47:08.760> sort<05:47:09.600> of 05:47:10.368 --> 05:47:10.378 align:start position:0% uh basic sort of 05:47:10.378 --> 05:47:13.250 align:start position:0% uh basic sort of standpoint<05:47:11.100> so<05:47:11.760> this<05:47:12.000> is<05:47:12.120> simply<05:47:12.420> the<05:47:12.660> mid<05:47:12.840> the 05:47:13.250 --> 05:47:13.260 align:start position:0% standpoint so this is simply the mid the 05:47:13.260 --> 05:47:15.470 align:start position:0% standpoint so this is simply the mid the median<05:47:13.500> this<05:47:13.740> is<05:47:13.860> called<05:47:14.040> physical<05:47:14.340> and<05:47:15.180> as 05:47:15.470 --> 05:47:15.480 align:start position:0% median this is called physical and as 05:47:15.480 --> 05:47:17.990 align:start position:0% median this is called physical and as you<05:47:15.900> can<05:47:15.958> imagine<05:47:16.320> this<05:47:17.040> is<05:47:17.160> also<05:47:17.458> the<05:47:17.760> very 05:47:17.990 --> 05:47:18.000 align:start position:0% you can imagine this is also the very 05:47:18.000 --> 05:47:20.330 align:start position:0% you can imagine this is also the very first<05:47:18.298> place<05:47:18.660> that<05:47:19.080> data<05:47:19.440> is<05:47:19.558> going<05:47:19.798> to<05:47:20.100> enter 05:47:20.330 --> 05:47:20.340 align:start position:0% first place that data is going to enter 05:47:20.340 --> 05:47:22.670 align:start position:0% first place that data is going to enter into<05:47:20.760> the<05:47:21.000> computer<05:47:21.120> right<05:47:21.540> it<05:47:21.718> goes<05:47:22.080> over<05:47:22.378> the 05:47:22.670 --> 05:47:22.680 align:start position:0% into the computer right it goes over the 05:47:22.680 --> 05:47:24.590 align:start position:0% into the computer right it goes over the chord<05:47:22.860> and<05:47:23.400> into<05:47:23.580> a<05:47:23.940> nick 05:47:24.590 --> 05:47:24.600 align:start position:0% chord and into a nick 05:47:24.600 --> 05:47:27.288 align:start position:0% chord and into a nick all<05:47:25.138> right<05:47:25.320> now<05:47:25.860> what<05:47:26.100> happens<05:47:26.340> then 05:47:27.288 --> 05:47:27.298 align:start position:0% all right now what happens then 05:47:27.298 --> 05:47:29.510 align:start position:0% all right now what happens then well<05:47:27.718> then<05:47:27.900> we<05:47:28.080> get<05:47:28.260> to<05:47:28.440> Layer<05:47:28.798> Two<05:47:28.980> which<05:47:29.340> is 05:47:29.510 --> 05:47:29.520 align:start position:0% well then we get to Layer Two which is 05:47:29.520 --> 05:47:32.030 align:start position:0% well then we get to Layer Two which is called<05:47:29.760> the<05:47:30.180> data<05:47:30.540> link<05:47:30.660> layer<05:47:31.080> an<05:47:31.620> easy<05:47:31.740> way 05:47:32.030 --> 05:47:32.040 align:start position:0% called the data link layer an easy way 05:47:32.040 --> 05:47:34.310 align:start position:0% called the data link layer an easy way to<05:47:32.280> remember<05:47:32.458> that<05:47:32.940> the<05:47:33.180> layer<05:47:33.480> 2<05:47:33.660> is<05:47:33.900> data 05:47:34.310 --> 05:47:34.320 align:start position:0% to remember that the layer 2 is data 05:47:34.320 --> 05:47:36.170 align:start position:0% to remember that the layer 2 is data link<05:47:34.440> is<05:47:34.798> because<05:47:34.980> it's<05:47:35.340> the<05:47:35.520> only<05:47:35.638> one<05:47:35.878> that 05:47:36.170 --> 05:47:36.180 align:start position:0% link is because it's the only one that 05:47:36.180 --> 05:47:39.890 align:start position:0% link is because it's the only one that has<05:47:36.420> two<05:47:37.260> words<05:47:37.620> it<05:47:38.458> also<05:47:38.700> has<05:47:39.000> and<05:47:39.540> this<05:47:39.780> is 05:47:39.890 --> 05:47:39.900 align:start position:0% has two words it also has and this is 05:47:39.900 --> 05:47:42.650 align:start position:0% has two words it also has and this is not<05:47:40.080> as<05:47:40.320> important<05:47:40.798> uh<05:47:41.580> for 05:47:42.650 --> 05:47:42.660 align:start position:0% not as important uh for 05:47:42.660 --> 05:47:45.170 align:start position:0% not as important uh for this<05:47:43.500> uh<05:47:43.920> for<05:47:44.218> the<05:47:44.280> network<05:47:44.400> plus<05:47:44.638> exam<05:47:45.000> but 05:47:45.170 --> 05:47:45.180 align:start position:0% this uh for the network plus exam but 05:47:45.180 --> 05:47:46.548 align:start position:0% this uh for the network plus exam but it's<05:47:45.240> still<05:47:45.420> good<05:47:45.600> to<05:47:45.718> know<05:47:45.900> there<05:47:46.320> are<05:47:46.440> two 05:47:46.548 --> 05:47:46.558 align:start position:0% it's still good to know there are two 05:47:46.558 --> 05:47:49.190 align:start position:0% it's still good to know there are two what<05:47:46.680> we<05:47:46.860> call<05:47:46.980> sub-layers<05:47:47.940> the<05:47:48.660> max<05:47:48.900> sub 05:47:49.190 --> 05:47:49.200 align:start position:0% what we call sub-layers the max sub 05:47:49.200 --> 05:47:52.190 align:start position:0% what we call sub-layers the max sub layer<05:47:49.680> and<05:47:50.040> the<05:47:50.218> LLC<05:47:50.760> sub<05:47:51.058> layer 05:47:52.190 --> 05:47:52.200 align:start position:0% layer and the LLC sub layer 05:47:52.200 --> 05:47:55.490 align:start position:0% layer and the LLC sub layer this<05:47:53.040> layer<05:47:53.458> in<05:47:54.240> total<05:47:54.540> and<05:47:54.718> so<05:47:54.900> these<05:47:55.320> two 05:47:55.490 --> 05:47:55.500 align:start position:0% this layer in total and so these two 05:47:55.500 --> 05:47:56.628 align:start position:0% this layer in total and so these two make<05:47:55.860> up 05:47:56.628 --> 05:47:56.638 align:start position:0% make up 05:47:56.638 --> 05:47:59.868 align:start position:0% make up this<05:47:57.540> data<05:47:57.840> link<05:47:57.958> layer<05:47:58.440> and<05:47:58.920> this<05:47:59.100> layer<05:47:59.400> as<05:47:59.700> a 05:47:59.868 --> 05:47:59.878 align:start position:0% this data link layer and this layer as a 05:47:59.878 --> 05:48:01.548 align:start position:0% this data link layer and this layer as a whole<05:48:00.000> is<05:48:00.240> responsible<05:48:00.780> for<05:48:01.138> allowing 05:48:01.548 --> 05:48:01.558 align:start position:0% whole is responsible for allowing 05:48:01.558 --> 05:48:04.970 align:start position:0% whole is responsible for allowing devices<05:48:01.980> to<05:48:02.580> share<05:48:02.878> the<05:48:03.360> same<05:48:03.540> medium<05:48:04.138> the 05:48:04.970 --> 05:48:04.980 align:start position:0% devices to share the same medium the 05:48:04.980 --> 05:48:07.788 align:start position:0% devices to share the same medium the medium<05:48:05.280> being<05:48:05.520> the<05:48:06.000> physical<05:48:06.180> layer<05:48:06.718> so<05:48:07.500> here 05:48:07.788 --> 05:48:07.798 align:start position:0% medium being the physical layer so here 05:48:07.798 --> 05:48:10.070 align:start position:0% medium being the physical layer so here we<05:48:07.980> see<05:48:08.100> a<05:48:08.218> few<05:48:08.400> things<05:48:08.520> happening<05:48:09.058> first<05:48:09.718> we 05:48:10.070 --> 05:48:10.080 align:start position:0% we see a few things happening first we 05:48:10.080 --> 05:48:13.670 align:start position:0% we see a few things happening first we see<05:48:10.260> a<05:48:10.500> certain<05:48:10.680> level<05:48:11.360> of<05:48:12.360> error<05:48:13.200> correction 05:48:13.670 --> 05:48:13.680 align:start position:0% see a certain level of error correction 05:48:13.680 --> 05:48:16.010 align:start position:0% see a certain level of error correction and<05:48:14.040> error<05:48:14.520> detection<05:48:14.878> on<05:48:15.718> the<05:48:15.900> physical 05:48:16.010 --> 05:48:16.020 align:start position:0% and error detection on the physical 05:48:16.020 --> 05:48:17.390 align:start position:0% and error detection on the physical layer<05:48:16.558> we're<05:48:16.680> going<05:48:16.860> to<05:48:16.920> see<05:48:17.040> this<05:48:17.160> a<05:48:17.340> little 05:48:17.390 --> 05:48:17.400 align:start position:0% layer we're going to see this a little 05:48:17.400 --> 05:48:19.250 align:start position:0% layer we're going to see this a little more<05:48:17.520> on<05:48:17.700> later<05:48:17.878> layers<05:48:18.298> as<05:48:18.540> well 05:48:19.250 --> 05:48:19.260 align:start position:0% more on later layers as well 05:48:19.260 --> 05:48:22.430 align:start position:0% more on later layers as well also<05:48:19.920> and<05:48:20.160> probably<05:48:20.458> more<05:48:21.000> important<05:48:21.480> we<05:48:22.138> see 05:48:22.430 --> 05:48:22.440 align:start position:0% also and probably more important we see 05:48:22.440 --> 05:48:25.670 align:start position:0% also and probably more important we see access<05:48:22.980> control<05:48:23.760> which<05:48:24.718> I've<05:48:24.840> denoted<05:48:25.378> here 05:48:25.670 --> 05:48:25.680 align:start position:0% access control which I've denoted here 05:48:25.680 --> 05:48:27.650 align:start position:0% access control which I've denoted here and<05:48:25.920> I'll<05:48:26.100> get<05:48:26.280> to<05:48:26.340> this<05:48:26.520> in<05:48:26.638> a<05:48:26.760> minute<05:48:26.878> by<05:48:27.480> the 05:48:27.650 --> 05:48:27.660 align:start position:0% and I'll get to this in a minute by the 05:48:27.660 --> 05:48:28.670 align:start position:0% and I'll get to this in a minute by the stop<05:48:27.840> light 05:48:28.670 --> 05:48:28.680 align:start position:0% stop light 05:48:28.680 --> 05:48:31.548 align:start position:0% stop light so<05:48:29.280> this<05:48:29.638> function<05:48:29.940> is<05:48:30.180> performed<05:48:30.780> by<05:48:31.200> this 05:48:31.548 --> 05:48:31.558 align:start position:0% so this function is performed by this 05:48:31.558 --> 05:48:33.410 align:start position:0% so this function is performed by this Max<05:48:31.798> sub<05:48:32.100> layer<05:48:32.458> again<05:48:32.580> I<05:48:32.878> wouldn't<05:48:33.000> worry<05:48:33.180> too 05:48:33.410 --> 05:48:33.420 align:start position:0% Max sub layer again I wouldn't worry too 05:48:33.420 --> 05:48:35.448 align:start position:0% Max sub layer again I wouldn't worry too much<05:48:33.540> about<05:48:33.718> that<05:48:34.020> but<05:48:34.680> the<05:48:34.920> most<05:48:35.040> important 05:48:35.448 --> 05:48:35.458 align:start position:0% much about that but the most important 05:48:35.458 --> 05:48:37.510 align:start position:0% much about that but the most important thing<05:48:35.700> here<05:48:35.940> is<05:48:36.360> that<05:48:36.540> we<05:48:36.780> have<05:48:37.020> physical 05:48:37.510 --> 05:48:37.520 align:start position:0% thing here is that we have physical 05:48:37.520 --> 05:48:40.610 align:start position:0% thing here is that we have physical addressing<05:48:38.520> or<05:48:39.120> the<05:48:39.298> MAC<05:48:39.480> address<05:48:39.780> so 05:48:40.610 --> 05:48:40.620 align:start position:0% addressing or the MAC address so 05:48:40.620 --> 05:48:43.730 align:start position:0% addressing or the MAC address so anything<05:48:40.920> that<05:48:41.340> looks<05:48:41.820> at<05:48:42.540> Mac<05:48:43.080> addressing 05:48:43.730 --> 05:48:43.740 align:start position:0% anything that looks at Mac addressing 05:48:43.740 --> 05:48:46.190 align:start position:0% anything that looks at Mac addressing and<05:48:44.400> by<05:48:44.520> the<05:48:44.638> way<05:48:44.700> Mac<05:48:45.000> addressing<05:48:45.600> is<05:48:45.840> oddly 05:48:46.190 --> 05:48:46.200 align:start position:0% and by the way Mac addressing is oddly 05:48:46.200 --> 05:48:47.990 align:start position:0% and by the way Mac addressing is oddly enough<05:48:46.378> performed 05:48:47.990 --> 05:48:48.000 align:start position:0% enough performed 05:48:48.000 --> 05:48:50.868 align:start position:0% enough performed by<05:48:48.718> the<05:48:49.200> LLC<05:48:49.740> layer 05:48:50.868 --> 05:48:50.878 align:start position:0% by the LLC layer 05:48:50.878 --> 05:48:52.788 align:start position:0% by the LLC layer allows<05:48:51.480> a<05:48:51.660> device<05:48:51.780> to<05:48:52.080> look<05:48:52.260> at<05:48:52.378> a<05:48:52.620> certain 05:48:52.788 --> 05:48:52.798 align:start position:0% allows a device to look at a certain 05:48:52.798 --> 05:48:57.530 align:start position:0% allows a device to look at a certain extra<05:48:53.958> layer<05:48:54.958> of<05:48:55.080> information<05:48:55.760> so<05:48:56.760> whereas 05:48:57.530 --> 05:48:57.540 align:start position:0% extra layer of information so whereas 05:48:57.540 --> 05:48:59.390 align:start position:0% extra layer of information so whereas with<05:48:57.900> layer<05:48:58.200> one<05:48:58.378> we<05:48:58.558> saw<05:48:58.740> physical<05:48:58.980> if<05:48:59.340> you 05:48:59.390 --> 05:48:59.400 align:start position:0% with layer one we saw physical if you 05:48:59.400 --> 05:49:01.788 align:start position:0% with layer one we saw physical if you remember<05:48:59.520> we<05:48:59.820> talked<05:49:00.120> about<05:49:00.240> hubs<05:49:01.020> hubs<05:49:01.620> just 05:49:01.788 --> 05:49:01.798 align:start position:0% remember we talked about hubs hubs just 05:49:01.798 --> 05:49:03.590 align:start position:0% remember we talked about hubs hubs just forward<05:49:02.040> bits<05:49:02.520> they<05:49:02.700> don't<05:49:02.820> look<05:49:03.000> at<05:49:03.120> the<05:49:03.298> bits 05:49:03.590 --> 05:49:03.600 align:start position:0% forward bits they don't look at the bits 05:49:03.600 --> 05:49:05.208 align:start position:0% forward bits they don't look at the bits so<05:49:03.780> they're<05:49:03.900> going<05:49:04.080> to<05:49:04.200> operate<05:49:04.500> at<05:49:04.680> layer<05:49:05.040> one 05:49:05.208 --> 05:49:05.218 align:start position:0% so they're going to operate at layer one 05:49:05.218 --> 05:49:07.670 align:start position:0% so they're going to operate at layer one here<05:49:05.820> at<05:49:06.058> Layer<05:49:06.360> Two<05:49:06.540> we<05:49:06.840> start<05:49:07.020> dealing<05:49:07.440> with 05:49:07.670 --> 05:49:07.680 align:start position:0% here at Layer Two we start dealing with 05:49:07.680 --> 05:49:10.670 align:start position:0% here at Layer Two we start dealing with Mac<05:49:08.040> addresses<05:49:08.580> as<05:49:09.298> a<05:49:09.480> result<05:49:09.660> this<05:49:10.260> is<05:49:10.378> where 05:49:10.670 --> 05:49:10.680 align:start position:0% Mac addresses as a result this is where 05:49:10.680 --> 05:49:14.690 align:start position:0% Mac addresses as a result this is where devices<05:49:11.100> like<05:49:11.840> switches<05:49:12.860> are<05:49:13.860> found<05:49:14.100> and 05:49:14.690 --> 05:49:14.700 align:start position:0% devices like switches are found and 05:49:14.700 --> 05:49:17.110 align:start position:0% devices like switches are found and that's<05:49:14.878> why<05:49:15.180> switches<05:49:15.718> are<05:49:15.958> often<05:49:16.378> called 05:49:17.110 --> 05:49:17.120 align:start position:0% that's why switches are often called 05:49:17.120 --> 05:49:19.850 align:start position:0% that's why switches are often called layer<05:49:18.120> 2<05:49:18.360> devices 05:49:19.850 --> 05:49:19.860 align:start position:0% layer 2 devices 05:49:19.860 --> 05:49:21.708 align:start position:0% layer 2 devices there<05:49:20.580> are<05:49:20.700> more<05:49:20.940> advanced<05:49:21.360> types<05:49:21.660> of 05:49:21.708 --> 05:49:21.718 align:start position:0% there are more advanced types of 05:49:21.718 --> 05:49:22.910 align:start position:0% there are more advanced types of switches<05:49:22.080> but<05:49:22.260> I<05:49:22.378> want<05:49:22.500> you<05:49:22.620> to<05:49:22.798> remember 05:49:22.910 --> 05:49:22.920 align:start position:0% switches but I want you to remember 05:49:22.920 --> 05:49:27.708 align:start position:0% switches but I want you to remember again<05:49:23.400> a<05:49:24.298> switch<05:49:24.420> is<05:49:24.780> a<05:49:25.020> layer<05:49:25.440> 2<05:49:26.218> device<05:49:26.760> now 05:49:27.708 --> 05:49:27.718 align:start position:0% again a switch is a layer 2 device now 05:49:27.718 --> 05:49:29.270 align:start position:0% again a switch is a layer 2 device now if<05:49:27.840> we<05:49:27.958> look<05:49:28.080> at<05:49:28.260> this<05:49:28.500> in<05:49:28.798> a<05:49:28.980> slightly 05:49:29.270 --> 05:49:29.280 align:start position:0% if we look at this in a slightly 05:49:29.280 --> 05:49:32.208 align:start position:0% if we look at this in a slightly different<05:49:29.700> way<05:49:30.138> here's<05:49:31.138> where<05:49:31.320> we<05:49:31.620> have<05:49:31.798> to<05:49:31.920> be 05:49:32.208 --> 05:49:32.218 align:start position:0% different way here's where we have to be 05:49:32.218 --> 05:49:33.948 align:start position:0% different way here's where we have to be able<05:49:32.400> to<05:49:32.520> have<05:49:32.700> access<05:49:33.058> control<05:49:33.480> on<05:49:33.780> our 05:49:33.948 --> 05:49:33.958 align:start position:0% able to have access control on our 05:49:33.958 --> 05:49:36.110 align:start position:0% able to have access control on our highway<05:49:34.200> so<05:49:35.100> this<05:49:35.280> is<05:49:35.400> where<05:49:35.580> we<05:49:35.760> have<05:49:35.878> to<05:49:36.000> be 05:49:36.110 --> 05:49:36.120 align:start position:0% highway so this is where we have to be 05:49:36.120 --> 05:49:39.288 align:start position:0% highway so this is where we have to be able<05:49:36.240> to<05:49:36.360> have<05:49:36.660> uh<05:49:37.500> proper<05:49:37.980> on-ramps<05:49:38.700> that<05:49:39.180> are 05:49:39.288 --> 05:49:39.298 align:start position:0% able to have uh proper on-ramps that are 05:49:39.298 --> 05:49:41.330 align:start position:0% able to have uh proper on-ramps that are only<05:49:39.480> going<05:49:39.660> to<05:49:39.718> allow<05:49:40.020> authorized<05:49:40.920> vehicles 05:49:41.330 --> 05:49:41.340 align:start position:0% only going to allow authorized vehicles 05:49:41.340 --> 05:49:43.730 align:start position:0% only going to allow authorized vehicles to<05:49:41.638> enter<05:49:41.820> onto<05:49:42.240> the<05:49:42.360> road<05:49:42.480> and<05:49:43.138> we<05:49:43.320> also<05:49:43.620> need 05:49:43.730 --> 05:49:43.740 align:start position:0% to enter onto the road and we also need 05:49:43.740 --> 05:49:45.708 align:start position:0% to enter onto the road and we also need to<05:49:43.860> establish<05:49:44.280> standards<05:49:44.878> for<05:49:45.180> how<05:49:45.420> the<05:49:45.600> road 05:49:45.708 --> 05:49:45.718 align:start position:0% to establish standards for how the road 05:49:45.718 --> 05:49:48.948 align:start position:0% to establish standards for how the road is<05:49:46.020> going<05:49:46.200> to<05:49:46.440> be<05:49:46.700> used<05:49:47.700> by<05:49:48.120> everyone<05:49:48.360> perhaps 05:49:48.948 --> 05:49:48.958 align:start position:0% is going to be used by everyone perhaps 05:49:48.958 --> 05:49:51.048 align:start position:0% is going to be used by everyone perhaps with<05:49:49.320> signs<05:49:49.860> and<05:49:50.340> here<05:49:50.458> we<05:49:50.638> also<05:49:50.820> remember 05:49:51.048 --> 05:49:51.058 align:start position:0% with signs and here we also remember 05:49:51.058 --> 05:49:52.610 align:start position:0% with signs and here we also remember this<05:49:51.420> is<05:49:51.540> where<05:49:51.718> we<05:49:51.900> establish<05:49:52.200> how<05:49:52.440> everyone 05:49:52.610 --> 05:49:52.620 align:start position:0% this is where we establish how everyone 05:49:52.620 --> 05:49:54.590 align:start position:0% this is where we establish how everyone is<05:49:52.860> going<05:49:53.040> to<05:49:53.218> share<05:49:53.400> the<05:49:53.638> road<05:49:53.760> who's<05:49:54.298> going 05:49:54.590 --> 05:49:54.600 align:start position:0% is going to share the road who's going 05:49:54.600 --> 05:49:57.708 align:start position:0% is going to share the road who's going to<05:49:54.660> access<05:49:54.840> the<05:49:55.138> road<05:49:55.580> and<05:49:56.580> a<05:49:57.000> certain<05:49:57.420> level 05:49:57.708 --> 05:49:57.718 align:start position:0% to access the road and a certain level 05:49:57.718 --> 05:49:59.628 align:start position:0% to access the road and a certain level of<05:49:58.020> checking<05:49:58.500> for<05:49:58.680> damage<05:49:59.040> on<05:49:59.340> the<05:49:59.458> highway 05:49:59.628 --> 05:49:59.638 align:start position:0% of checking for damage on the highway 05:49:59.638 --> 05:50:02.270 align:start position:0% of checking for damage on the highway and<05:50:00.420> vehicles<05:50:00.840> for<05:50:01.200> instance<05:50:01.440> people<05:50:01.740> sort<05:50:02.160> of 05:50:02.270 --> 05:50:02.280 align:start position:0% and vehicles for instance people sort of 05:50:02.280 --> 05:50:03.948 align:start position:0% and vehicles for instance people sort of going<05:50:02.760> on<05:50:02.940> and<05:50:03.120> making<05:50:03.298> sure<05:50:03.540> there<05:50:03.780> aren't 05:50:03.948 --> 05:50:03.958 align:start position:0% going on and making sure there aren't 05:50:03.958 --> 05:50:07.010 align:start position:0% going on and making sure there aren't potholes<05:50:05.100> in<05:50:05.638> this<05:50:05.760> layer<05:50:06.058> we<05:50:06.298> refer<05:50:06.600> to<05:50:06.718> the 05:50:07.010 --> 05:50:07.020 align:start position:0% potholes in this layer we refer to the 05:50:07.020 --> 05:50:10.250 align:start position:0% potholes in this layer we refer to the data<05:50:07.440> as<05:50:08.218> frames<05:50:09.058> of<05:50:09.420> data<05:50:09.780> because<05:50:09.958> they're 05:50:10.250 --> 05:50:10.260 align:start position:0% data as frames of data because they're 05:50:10.260 --> 05:50:12.110 align:start position:0% data as frames of data because they're beginning<05:50:10.500> to<05:50:10.798> get<05:50:10.980> framed<05:50:11.340> we're<05:50:11.580> no<05:50:11.878> longer 05:50:12.110 --> 05:50:12.120 align:start position:0% beginning to get framed we're no longer 05:50:12.120 --> 05:50:14.030 align:start position:0% beginning to get framed we're no longer just<05:50:12.298> dealing<05:50:12.660> with<05:50:13.138> the<05:50:13.320> ones<05:50:13.558> and<05:50:13.680> zeros 05:50:14.030 --> 05:50:14.040 align:start position:0% just dealing with the ones and zeros 05:50:14.040 --> 05:50:17.990 align:start position:0% just dealing with the ones and zeros we're<05:50:14.280> dealing<05:50:14.638> with<05:50:14.878> them<05:50:15.120> in<05:50:15.958> a<05:50:16.378> frame<05:50:16.798> or<05:50:17.580> in 05:50:17.990 --> 05:50:18.000 align:start position:0% we're dealing with them in a frame or in 05:50:18.000 --> 05:50:21.948 align:start position:0% we're dealing with them in a frame or in a<05:50:18.298> uh<05:50:18.660> sort<05:50:18.900> of<05:50:19.080> larger<05:50:19.980> context<05:50:20.638> now<05:50:21.480> the<05:50:21.780> next 05:50:21.948 --> 05:50:21.958 align:start position:0% a uh sort of larger context now the next 05:50:21.958 --> 05:50:24.830 align:start position:0% a uh sort of larger context now the next layer<05:50:22.378> is<05:50:22.920> layer<05:50:23.400> three<05:50:23.580> or<05:50:24.058> the<05:50:24.360> network 05:50:24.830 --> 05:50:24.840 align:start position:0% layer is layer three or the network 05:50:24.840 --> 05:50:27.170 align:start position:0% layer is layer three or the network layer<05:50:25.378> here's<05:50:26.100> where<05:50:26.280> a<05:50:26.580> really<05:50:26.760> a<05:50:27.000> lot<05:50:27.058> of 05:50:27.170 --> 05:50:27.180 align:start position:0% layer here's where a really a lot of 05:50:27.180 --> 05:50:30.170 align:start position:0% layer here's where a really a lot of exciting<05:50:27.600> stuff<05:50:27.840> happens<05:50:28.138> okay<05:50:28.740> first<05:50:29.520> the 05:50:30.170 --> 05:50:30.180 align:start position:0% exciting stuff happens okay first the 05:50:30.180 --> 05:50:31.910 align:start position:0% exciting stuff happens okay first the third<05:50:30.360> layer<05:50:30.780> is<05:50:30.958> different<05:50:31.138> from<05:50:31.500> the<05:50:31.680> second 05:50:31.910 --> 05:50:31.920 align:start position:0% third layer is different from the second 05:50:31.920 --> 05:50:34.810 align:start position:0% third layer is different from the second layer<05:50:32.400> in<05:50:33.000> that<05:50:33.240> the<05:50:33.600> data<05:50:34.020> link<05:50:34.138> layer 05:50:34.810 --> 05:50:34.820 align:start position:0% layer in that the data link layer 05:50:34.820 --> 05:50:37.670 align:start position:0% layer in that the data link layer transfers<05:50:35.820> data<05:50:36.240> between<05:50:36.600> devices<05:50:37.200> that<05:50:37.500> are 05:50:37.670 --> 05:50:37.680 align:start position:0% transfers data between devices that are 05:50:37.680 --> 05:50:40.850 align:start position:0% transfers data between devices that are within<05:50:38.100> the<05:50:38.340> same<05:50:38.638> network<05:50:39.000> okay<05:50:39.900> so<05:50:40.320> if<05:50:40.740> you 05:50:40.850 --> 05:50:40.860 align:start position:0% within the same network okay so if you 05:50:40.860 --> 05:50:42.288 align:start position:0% within the same network okay so if you remember<05:50:40.980> we<05:50:41.280> talked<05:50:41.580> with<05:50:41.760> dealing<05:50:42.180> with 05:50:42.288 --> 05:50:42.298 align:start position:0% remember we talked with dealing with 05:50:42.298 --> 05:50:44.270 align:start position:0% remember we talked with dealing with switches<05:50:42.718> switches<05:50:43.200> only<05:50:43.440> deal<05:50:43.620> with<05:50:43.860> devices 05:50:44.270 --> 05:50:44.280 align:start position:0% switches switches only deal with devices 05:50:44.280 --> 05:50:47.090 align:start position:0% switches switches only deal with devices on<05:50:44.760> the<05:50:44.940> same<05:50:45.120> network<05:50:45.420> but<05:50:46.200> here<05:50:46.440> on<05:50:46.740> layer 05:50:47.090 --> 05:50:47.100 align:start position:0% on the same network but here on layer 05:50:47.100 --> 05:50:49.970 align:start position:0% on the same network but here on layer three<05:50:47.280> the<05:50:48.058> network<05:50:48.240> layer<05:50:48.718> can<05:50:49.020> allow<05:50:49.320> us<05:50:49.558> to 05:50:49.970 --> 05:50:49.980 align:start position:0% three the network layer can allow us to 05:50:49.980 --> 05:50:52.610 align:start position:0% three the network layer can allow us to transfer<05:50:50.458> data<05:50:50.878> to<05:50:51.540> and<05:50:51.718> from<05:50:51.900> devices<05:50:52.260> that 05:50:52.610 --> 05:50:52.620 align:start position:0% transfer data to and from devices that 05:50:52.620 --> 05:50:55.310 align:start position:0% transfer data to and from devices that are<05:50:52.740> on<05:50:53.160> different<05:50:53.458> networks<05:50:54.120> it<05:50:54.780> does<05:50:54.958> this 05:50:55.310 --> 05:50:55.320 align:start position:0% are on different networks it does this 05:50:55.320 --> 05:50:58.310 align:start position:0% are on different networks it does this by<05:50:56.160> a<05:50:56.400> specific<05:50:56.878> kind<05:50:57.420> of<05:50:57.600> addressing 05:50:58.310 --> 05:50:58.320 align:start position:0% by a specific kind of addressing 05:50:58.320 --> 05:50:59.690 align:start position:0% by a specific kind of addressing specifically 05:50:59.690 --> 05:50:59.700 align:start position:0% specifically 05:50:59.700 --> 05:51:02.690 align:start position:0% specifically IP<05:51:00.480> addressing<05:51:01.020> and<05:51:01.500> when<05:51:01.620> we<05:51:01.798> deal<05:51:01.980> with<05:51:02.280> IP 05:51:02.690 --> 05:51:02.700 align:start position:0% IP addressing and when we deal with IP 05:51:02.700 --> 05:51:07.310 align:start position:0% IP addressing and when we deal with IP addressing<05:51:03.320> or<05:51:04.320> the<05:51:04.860> Internet<05:51:05.340> Protocol 05:51:07.310 --> 05:51:07.320 align:start position:0% addressing or the Internet Protocol 05:51:07.320 --> 05:51:10.310 align:start position:0% addressing or the Internet Protocol we<05:51:07.740> allow<05:51:07.980> what's<05:51:08.160> called<05:51:08.580> routing 05:51:10.310 --> 05:51:10.320 align:start position:0% we allow what's called routing 05:51:10.320 --> 05:51:12.890 align:start position:0% we allow what's called routing so<05:51:10.680> the<05:51:10.920> main<05:51:11.040> job<05:51:11.280> of<05:51:11.520> the<05:51:11.760> network<05:51:11.940> layer<05:51:12.480> is 05:51:12.890 --> 05:51:12.900 align:start position:0% so the main job of the network layer is 05:51:12.900 --> 05:51:14.930 align:start position:0% so the main job of the network layer is really<05:51:13.200> about<05:51:13.860> this<05:51:14.218> routing<05:51:14.580> it's<05:51:14.760> about 05:51:14.930 --> 05:51:14.940 align:start position:0% really about this routing it's about 05:51:14.940 --> 05:51:17.868 align:start position:0% really about this routing it's about routing<05:51:15.718> and<05:51:16.200> routers<05:51:16.680> so<05:51:17.160> knowing<05:51:17.580> this<05:51:17.700> and 05:51:17.868 --> 05:51:17.878 align:start position:0% routing and routers so knowing this and 05:51:17.878 --> 05:51:19.910 align:start position:0% routing and routers so knowing this and that<05:51:18.058> IP<05:51:18.420> addresses<05:51:18.958> are<05:51:19.138> used<05:51:19.320> for<05:51:19.558> routing 05:51:19.910 --> 05:51:19.920 align:start position:0% that IP addresses are used for routing 05:51:19.920 --> 05:51:22.310 align:start position:0% that IP addresses are used for routing we<05:51:20.458> come<05:51:20.638> to<05:51:20.820> the<05:51:20.940> conclusion<05:51:21.420> that<05:51:21.780> the<05:51:22.020> kinds 05:51:22.310 --> 05:51:22.320 align:start position:0% we come to the conclusion that the kinds 05:51:22.320 --> 05:51:23.810 align:start position:0% we come to the conclusion that the kinds of<05:51:22.440> devices<05:51:22.680> we're<05:51:23.100> really<05:51:23.280> going<05:51:23.458> to<05:51:23.520> find<05:51:23.638> in 05:51:23.810 --> 05:51:23.820 align:start position:0% of devices we're really going to find in 05:51:23.820 --> 05:51:24.948 align:start position:0% of devices we're really going to find in this<05:51:24.000> layer 05:51:24.948 --> 05:51:24.958 align:start position:0% this layer 05:51:24.958 --> 05:51:28.368 align:start position:0% this layer are<05:51:25.558> routers<05:51:26.040> so<05:51:26.638> routers<05:51:27.240> are<05:51:27.718> what<05:51:27.958> we<05:51:28.138> call 05:51:28.368 --> 05:51:28.378 align:start position:0% are routers so routers are what we call 05:51:28.378 --> 05:51:30.590 align:start position:0% are routers so routers are what we call layer<05:51:29.040> 3<05:51:29.280> devices<05:51:29.760> and<05:51:30.120> that's<05:51:30.240> you're<05:51:30.480> going 05:51:30.590 --> 05:51:30.600 align:start position:0% layer 3 devices and that's you're going 05:51:30.600 --> 05:51:32.930 align:start position:0% layer 3 devices and that's you're going to<05:51:30.718> see<05:51:30.780> on<05:51:31.020> the<05:51:31.200> test<05:51:31.378> now<05:51:32.218> for<05:51:32.580> the 05:51:32.930 --> 05:51:32.940 align:start position:0% to see on the test now for the 05:51:32.940 --> 05:51:35.868 align:start position:0% to see on the test now for the information<05:51:33.600> to<05:51:34.260> actually<05:51:34.558> reach<05:51:35.458> the 05:51:35.868 --> 05:51:35.878 align:start position:0% information to actually reach the 05:51:35.878 --> 05:51:38.810 align:start position:0% information to actually reach the destination<05:51:36.360> this<05:51:37.200> IP<05:51:37.620> address<05:51:37.798> has<05:51:38.458> to<05:51:38.638> be 05:51:38.810 --> 05:51:38.820 align:start position:0% destination this IP address has to be 05:51:38.820 --> 05:51:40.070 align:start position:0% destination this IP address has to be mapped 05:51:40.070 --> 05:51:40.080 align:start position:0% mapped 05:51:40.080 --> 05:51:44.208 align:start position:0% mapped to<05:51:40.860> a<05:51:41.160> physical<05:51:41.400> address<05:51:41.820> on<05:51:42.360> layer<05:51:42.718> 2. 05:51:44.208 --> 05:51:44.218 align:start position:0% to a physical address on layer 2. 05:51:44.218 --> 05:51:47.208 align:start position:0% to a physical address on layer 2. so<05:51:44.638> the<05:51:44.820> protocol<05:51:45.120> that<05:51:45.420> does<05:51:45.718> this<05:51:46.080> is<05:51:46.920> called 05:51:47.208 --> 05:51:47.218 align:start position:0% so the protocol that does this is called 05:51:47.218 --> 05:51:48.590 align:start position:0% so the protocol that does this is called arp 05:51:48.590 --> 05:51:48.600 align:start position:0% arp 05:51:48.600 --> 05:51:51.230 align:start position:0% arp what<05:51:49.260> ARP<05:51:49.620> does 05:51:51.230 --> 05:51:51.240 align:start position:0% what ARP does 05:51:51.240 --> 05:51:54.830 align:start position:0% what ARP does is<05:51:51.660> it<05:51:51.958> Maps 05:51:54.830 --> 05:51:54.840 align:start position:0% 05:51:54.840 --> 05:51:56.990 align:start position:0% for<05:51:55.378> better<05:51:55.558> for<05:51:55.980> a<05:51:56.100> lack<05:51:56.340> of<05:51:56.458> a<05:51:56.580> better<05:51:56.700> way<05:51:56.878> of 05:51:56.990 --> 05:51:57.000 align:start position:0% for better for a lack of a better way of 05:51:57.000 --> 05:52:01.128 align:start position:0% for better for a lack of a better way of describing<05:51:57.360> it<05:51:57.540> Maps<05:51:58.080> Mac<05:51:58.320> addresses 05:52:01.128 --> 05:52:01.138 align:start position:0% 05:52:01.138 --> 05:52:04.490 align:start position:0% to<05:52:01.440> IP<05:52:01.860> addresses<05:52:02.520> by<05:52:03.420> the<05:52:03.540> way<05:52:03.600> ARP<05:52:04.080> stands 05:52:04.490 --> 05:52:04.500 align:start position:0% to IP addresses by the way ARP stands 05:52:04.500 --> 05:52:12.170 align:start position:0% to IP addresses by the way ARP stands for<05:52:04.798> address 05:52:12.170 --> 05:52:12.180 align:start position:0% 05:52:12.180 --> 05:52:15.650 align:start position:0% resolution 05:52:15.650 --> 05:52:15.660 align:start position:0% 05:52:15.660 --> 05:52:19.850 align:start position:0% protocol 05:52:19.850 --> 05:52:19.860 align:start position:0% 05:52:19.860 --> 05:52:23.570 align:start position:0% this<05:52:20.820> protocol<05:52:21.240> actually<05:52:22.200> operates<05:52:23.160> slightly 05:52:23.570 --> 05:52:23.580 align:start position:0% this protocol actually operates slightly 05:52:23.580 --> 05:52:25.310 align:start position:0% this protocol actually operates slightly on<05:52:23.760> the<05:52:23.878> network<05:52:24.000> layer<05:52:24.480> and<05:52:24.718> slightly<05:52:25.020> on<05:52:25.200> the 05:52:25.310 --> 05:52:25.320 align:start position:0% on the network layer and slightly on the 05:52:25.320 --> 05:52:27.170 align:start position:0% on the network layer and slightly on the data<05:52:25.620> link<05:52:25.740> layer<05:52:26.100> because<05:52:26.458> obviously<05:52:27.000> it's 05:52:27.170 --> 05:52:27.180 align:start position:0% data link layer because obviously it's 05:52:27.180 --> 05:52:29.330 align:start position:0% data link layer because obviously it's dealing<05:52:27.480> with<05:52:27.600> Mac<05:52:27.840> addresses<05:52:28.440> and<05:52:28.920> IP 05:52:29.330 --> 05:52:29.340 align:start position:0% dealing with Mac addresses and IP 05:52:29.340 --> 05:52:33.890 align:start position:0% dealing with Mac addresses and IP addresses 05:52:33.890 --> 05:52:33.900 align:start position:0% 05:52:33.900 --> 05:52:35.390 align:start position:0% now<05:52:34.260> it's<05:52:34.378> important<05:52:34.680> that<05:52:34.798> you<05:52:34.980> consider 05:52:35.390 --> 05:52:35.400 align:start position:0% now it's important that you consider 05:52:35.400 --> 05:52:37.490 align:start position:0% now it's important that you consider that<05:52:35.700> remember<05:52:35.878> we<05:52:36.240> talked<05:52:36.600> about 05:52:37.490 --> 05:52:37.500 align:start position:0% that remember we talked about 05:52:37.500 --> 05:52:38.628 align:start position:0% that remember we talked about UDP 05:52:38.628 --> 05:52:38.638 align:start position:0% UDP 05:52:38.638 --> 05:52:41.628 align:start position:0% UDP versus<05:52:39.240> TCP 05:52:41.628 --> 05:52:41.638 align:start position:0% versus TCP 05:52:41.638 --> 05:52:44.990 align:start position:0% versus TCP UDP<05:52:42.058> being 05:52:44.990 --> 05:52:45.000 align:start position:0% 05:52:45.000 --> 05:52:51.850 align:start position:0% connection<05:52:45.540> less<05:52:46.378> and<05:52:47.160> TCP<05:52:47.820> being<05:52:48.360> connection 05:52:51.850 --> 05:52:51.860 align:start position:0% 05:52:51.860 --> 05:52:54.288 align:start position:0% oriented<05:52:53.218> that's<05:52:53.700> when<05:52:53.820> we're<05:52:53.940> dealing<05:52:54.240> with 05:52:54.288 --> 05:52:54.298 align:start position:0% oriented that's when we're dealing with 05:52:54.298 --> 05:52:55.970 align:start position:0% oriented that's when we're dealing with ports<05:52:54.660> and<05:52:54.840> we'll<05:52:54.958> talk<05:52:55.138> about<05:52:55.260> that<05:52:55.558> more<05:52:55.740> we 05:52:55.970 --> 05:52:55.980 align:start position:0% ports and we'll talk about that more we 05:52:55.980 --> 05:52:57.350 align:start position:0% ports and we'll talk about that more we talked<05:52:56.280> about<05:52:56.340> that<05:52:56.520> in<05:52:56.638> a<05:52:56.760> plus<05:52:56.940> and<05:52:57.180> we'll 05:52:57.350 --> 05:52:57.360 align:start position:0% talked about that in a plus and we'll 05:52:57.360 --> 05:52:59.390 align:start position:0% talked about that in a plus and we'll talk<05:52:57.540> about<05:52:57.660> that<05:52:57.958> a<05:52:58.138> little<05:52:58.200> more<05:52:58.378> later<05:52:58.620> well 05:52:59.390 --> 05:52:59.400 align:start position:0% talk about that a little more later well 05:52:59.400 --> 05:53:01.548 align:start position:0% talk about that a little more later well everything<05:52:59.760> in<05:53:00.298> the<05:53:00.480> network<05:53:00.660> layer<05:53:01.200> is 05:53:01.548 --> 05:53:01.558 align:start position:0% everything in the network layer is 05:53:01.558 --> 05:53:04.010 align:start position:0% everything in the network layer is connection<05:53:02.218> less 05:53:04.010 --> 05:53:04.020 align:start position:0% connection less 05:53:04.020 --> 05:53:07.250 align:start position:0% connection less this<05:53:04.440> means<05:53:04.798> that<05:53:05.040> it<05:53:05.340> manages<05:53:05.840> the<05:53:06.840> transfer 05:53:07.250 --> 05:53:07.260 align:start position:0% this means that it manages the transfer 05:53:07.260 --> 05:53:11.270 align:start position:0% this means that it manages the transfer of<05:53:07.440> data<05:53:07.740> in<05:53:08.040> a<05:53:08.218> connection<05:53:08.400> less<05:53:09.260> uh<05:53:10.260> mode<05:53:10.558> it 05:53:11.270 --> 05:53:11.280 align:start position:0% of data in a connection less uh mode it 05:53:11.280 --> 05:53:12.890 align:start position:0% of data in a connection less uh mode it just<05:53:11.400> sends<05:53:11.760> the<05:53:11.878> data<05:53:12.120> but<05:53:12.298> it's<05:53:12.420> not<05:53:12.718> going 05:53:12.890 --> 05:53:12.900 align:start position:0% just sends the data but it's not going 05:53:12.900 --> 05:53:15.110 align:start position:0% just sends the data but it's not going to<05:53:13.020> wait<05:53:13.320> for<05:53:13.558> a<05:53:13.680> reply<05:53:13.980> to<05:53:14.160> ensure<05:53:14.520> it<05:53:14.638> got<05:53:14.878> to 05:53:15.110 --> 05:53:15.120 align:start position:0% to wait for a reply to ensure it got to 05:53:15.120 --> 05:53:17.448 align:start position:0% to wait for a reply to ensure it got to its<05:53:15.420> destination<05:53:15.900> this<05:53:16.620> means<05:53:16.860> we're<05:53:17.100> sort<05:53:17.340> of 05:53:17.448 --> 05:53:17.458 align:start position:0% its destination this means we're sort of 05:53:17.458 --> 05:53:21.350 align:start position:0% its destination this means we're sort of using<05:53:17.940> a<05:53:18.780> best<05:53:19.020> effort<05:53:19.620> here<05:53:20.160> this<05:53:21.000> is<05:53:21.120> like 05:53:21.350 --> 05:53:21.360 align:start position:0% using a best effort here this is like 05:53:21.360 --> 05:53:23.150 align:start position:0% using a best effort here this is like dropping<05:53:21.900> something<05:53:22.138> in<05:53:22.440> the<05:53:22.558> mail<05:53:22.680> and<05:53:22.980> just 05:53:23.150 --> 05:53:23.160 align:start position:0% dropping something in the mail and just 05:53:23.160 --> 05:53:24.650 align:start position:0% dropping something in the mail and just hoping<05:53:23.458> it<05:53:23.580> gets<05:53:23.878> there<05:53:24.000> we're<05:53:24.180> not<05:53:24.298> using 05:53:24.650 --> 05:53:24.660 align:start position:0% hoping it gets there we're not using 05:53:24.660 --> 05:53:28.850 align:start position:0% hoping it gets there we're not using certified<05:53:25.200> mail<05:53:25.740> at<05:53:26.040> all<05:53:26.580> on<05:53:27.180> layer<05:53:27.540> 3<05:53:27.860> the 05:53:28.850 --> 05:53:28.860 align:start position:0% certified mail at all on layer 3 the 05:53:28.860 --> 05:53:30.890 align:start position:0% certified mail at all on layer 3 the information<05:53:29.160> remember<05:53:30.058> Layer<05:53:30.480> Two<05:53:30.600> we<05:53:30.718> had 05:53:30.890 --> 05:53:30.900 align:start position:0% information remember Layer Two we had 05:53:30.900 --> 05:53:32.990 align:start position:0% information remember Layer Two we had frames<05:53:31.260> well<05:53:31.500> now<05:53:31.680> we<05:53:31.860> have<05:53:32.040> something<05:53:32.458> called 05:53:32.990 --> 05:53:33.000 align:start position:0% frames well now we have something called 05:53:33.000 --> 05:53:35.930 align:start position:0% frames well now we have something called datagrams 05:53:35.930 --> 05:53:35.940 align:start position:0% datagrams 05:53:35.940 --> 05:53:38.750 align:start position:0% datagrams so<05:53:36.420> this<05:53:36.718> is<05:53:36.900> now<05:53:37.200> we're<05:53:37.320> moving<05:53:37.620> up<05:53:37.798> right<05:53:38.280> we 05:53:38.750 --> 05:53:38.760 align:start position:0% so this is now we're moving up right we 05:53:38.760 --> 05:53:40.490 align:start position:0% so this is now we're moving up right we had<05:53:38.878> frames<05:53:39.298> now<05:53:39.480> the<05:53:39.660> frames<05:53:39.958> are<05:53:40.138> packaged 05:53:40.490 --> 05:53:40.500 align:start position:0% had frames now the frames are packaged 05:53:40.500 --> 05:53:43.128 align:start position:0% had frames now the frames are packaged into<05:53:40.620> datagrams<05:53:41.760> so<05:53:42.180> if<05:53:42.480> we<05:53:42.660> keep<05:53:42.780> with<05:53:42.958> our 05:53:43.128 --> 05:53:43.138 align:start position:0% into datagrams so if we keep with our 05:53:43.138 --> 05:53:45.048 align:start position:0% into datagrams so if we keep with our method<05:53:43.500> of<05:53:43.620> talking<05:53:43.798> about<05:53:43.980> the<05:53:44.280> bus<05:53:44.458> metaphor 05:53:45.048 --> 05:53:45.058 align:start position:0% method of talking about the bus metaphor 05:53:45.058 --> 05:53:47.090 align:start position:0% method of talking about the bus metaphor okay 05:53:47.090 --> 05:53:47.100 align:start position:0% okay 05:53:47.100 --> 05:53:49.250 align:start position:0% okay from<05:53:47.580> the<05:53:47.760> third<05:53:47.940> layer<05:53:48.360> up<05:53:48.600> we're<05:53:48.900> going<05:53:49.080> to 05:53:49.250 --> 05:53:49.260 align:start position:0% from the third layer up we're going to 05:53:49.260 --> 05:53:51.890 align:start position:0% from the third layer up we're going to concentrate<05:53:49.860> on<05:53:50.218> the<05:53:50.458> bus<05:53:50.700> itself<05:53:51.298> so<05:53:51.660> we've 05:53:51.890 --> 05:53:51.900 align:start position:0% concentrate on the bus itself so we've 05:53:51.900 --> 05:53:54.048 align:start position:0% concentrate on the bus itself so we've been<05:53:52.080> talking<05:53:52.378> about<05:53:52.680> the<05:53:53.100> road<05:53:53.280> right<05:53:53.820> we 05:53:54.048 --> 05:53:54.058 align:start position:0% been talking about the road right we 05:53:54.058 --> 05:53:55.850 align:start position:0% been talking about the road right we talked<05:53:54.420> about<05:53:54.480> the<05:53:54.780> road<05:53:54.958> itself<05:53:55.558> the 05:53:55.850 --> 05:53:55.860 align:start position:0% talked about the road itself the 05:53:55.860 --> 05:53:57.048 align:start position:0% talked about the road itself the physical<05:53:56.040> layer<05:53:56.458> and<05:53:56.520> then<05:53:56.638> we<05:53:56.760> talked<05:53:57.000> about 05:53:57.048 --> 05:53:57.058 align:start position:0% physical layer and then we talked about 05:53:57.058 --> 05:53:58.788 align:start position:0% physical layer and then we talked about how<05:53:57.420> people<05:53:57.600> are<05:53:57.840> going<05:53:57.958> to<05:53:58.080> share<05:53:58.260> that<05:53:58.558> road 05:53:58.788 --> 05:53:58.798 align:start position:0% how people are going to share that road 05:53:58.798 --> 05:54:01.368 align:start position:0% how people are going to share that road which<05:53:59.520> is<05:53:59.700> Layer<05:54:00.360> Two 05:54:01.368 --> 05:54:01.378 align:start position:0% which is Layer Two 05:54:01.378 --> 05:54:04.010 align:start position:0% which is Layer Two data<05:54:02.160> link<05:54:02.218> layer<05:54:02.638> now<05:54:03.120> layer<05:54:03.480> 3<05:54:03.600> the<05:54:03.840> network 05:54:04.010 --> 05:54:04.020 align:start position:0% data link layer now layer 3 the network 05:54:04.020 --> 05:54:07.010 align:start position:0% data link layer now layer 3 the network layer<05:54:04.500> this<05:54:04.740> is<05:54:04.860> the<05:54:05.040> bus<05:54:05.218> itself<05:54:05.718> layer<05:54:06.718> 3 05:54:07.010 --> 05:54:07.020 align:start position:0% layer this is the bus itself layer 3 05:54:07.020 --> 05:54:09.770 align:start position:0% layer this is the bus itself layer 3 through<05:54:07.440> 7<05:54:07.798> concentrates<05:54:08.760> on<05:54:08.940> the<05:54:09.180> processes 05:54:09.770 --> 05:54:09.780 align:start position:0% through 7 concentrates on the processes 05:54:09.780 --> 05:54:13.010 align:start position:0% through 7 concentrates on the processes that<05:54:10.320> affect<05:54:10.680> this<05:54:11.160> container<05:54:11.940> in<05:54:12.600> our<05:54:12.780> case 05:54:13.010 --> 05:54:13.020 align:start position:0% that affect this container in our case 05:54:13.020 --> 05:54:15.770 align:start position:0% that affect this container in our case the<05:54:13.680> bus<05:54:13.920> since<05:54:14.700> we're<05:54:14.878> basically<05:54:15.240> designing 05:54:15.770 --> 05:54:15.780 align:start position:0% the bus since we're basically designing 05:54:15.780 --> 05:54:17.868 align:start position:0% the bus since we're basically designing our<05:54:15.900> bus<05:54:16.080> this<05:54:16.500> layer<05:54:16.798> is<05:54:16.980> determining<05:54:17.700> the 05:54:17.868 --> 05:54:17.878 align:start position:0% our bus this layer is determining the 05:54:17.878 --> 05:54:20.570 align:start position:0% our bus this layer is determining the best<05:54:18.120> path<05:54:18.660> that<05:54:19.260> our<05:54:19.440> data<05:54:19.798> is<05:54:19.980> going<05:54:20.160> to<05:54:20.340> take 05:54:20.570 --> 05:54:20.580 align:start position:0% best path that our data is going to take 05:54:20.580 --> 05:54:22.670 align:start position:0% best path that our data is going to take so<05:54:21.058> in<05:54:21.180> a<05:54:21.360> manner<05:54:21.540> of<05:54:21.660> speaking<05:54:21.958> this<05:54:22.200> is<05:54:22.378> like 05:54:22.670 --> 05:54:22.680 align:start position:0% so in a manner of speaking this is like 05:54:22.680 --> 05:54:25.548 align:start position:0% so in a manner of speaking this is like the<05:54:23.400> bus<05:54:23.580> driver<05:54:23.878> on<05:54:24.240> a<05:54:24.360> specific<05:54:24.600> route<05:54:24.958> who's 05:54:25.548 --> 05:54:25.558 align:start position:0% the bus driver on a specific route who's 05:54:25.558 --> 05:54:27.470 align:start position:0% the bus driver on a specific route who's going<05:54:25.798> to<05:54:25.920> constantly<05:54:26.458> updating<05:54:26.940> us<05:54:27.240> with 05:54:27.470 --> 05:54:27.480 align:start position:0% going to constantly updating us with 05:54:27.480 --> 05:54:29.628 align:start position:0% going to constantly updating us with routing<05:54:27.958> information<05:54:28.200> so<05:54:29.160> it's<05:54:29.280> saying 05:54:29.628 --> 05:54:29.638 align:start position:0% routing information so it's saying 05:54:29.638 --> 05:54:31.250 align:start position:0% routing information so it's saying here's<05:54:29.878> our<05:54:30.000> first<05:54:30.180> destination<05:54:30.660> here's<05:54:31.080> our 05:54:31.250 --> 05:54:31.260 align:start position:0% here's our first destination here's our 05:54:31.260 --> 05:54:32.810 align:start position:0% here's our first destination here's our second<05:54:31.440> destination<05:54:31.980> here's<05:54:32.520> our<05:54:32.700> third 05:54:32.810 --> 05:54:32.820 align:start position:0% second destination here's our third 05:54:32.820 --> 05:54:35.570 align:start position:0% second destination here's our third destination<05:54:33.360> just<05:54:34.260> in<05:54:34.500> case<05:54:34.740> a<05:54:35.160> route<05:54:35.340> is 05:54:35.570 --> 05:54:35.580 align:start position:0% destination just in case a route is 05:54:35.580 --> 05:54:37.310 align:start position:0% destination just in case a route is blocked<05:54:36.000> or<05:54:36.058> if<05:54:36.240> there's<05:54:36.360> a<05:54:36.600> faster<05:54:36.840> or<05:54:37.080> better 05:54:37.310 --> 05:54:37.320 align:start position:0% blocked or if there's a faster or better 05:54:37.320 --> 05:54:40.128 align:start position:0% blocked or if there's a faster or better route<05:54:37.558> available<05:54:38.058> layer<05:54:39.058> 3<05:54:39.240> is<05:54:39.718> where<05:54:39.958> those 05:54:40.128 --> 05:54:40.138 align:start position:0% route available layer 3 is where those 05:54:40.138 --> 05:54:42.170 align:start position:0% route available layer 3 is where those Protocols<05:54:40.798> are<05:54:40.920> going<05:54:41.040> to<05:54:41.218> operate<05:54:41.638> to<05:54:42.000> find 05:54:42.170 --> 05:54:42.180 align:start position:0% Protocols are going to operate to find 05:54:42.180 --> 05:54:44.930 align:start position:0% Protocols are going to operate to find the<05:54:42.540> shortest<05:54:42.900> and<05:54:43.138> most<05:54:43.320> reliable<05:54:43.980> path<05:54:44.400> to 05:54:44.930 --> 05:54:44.940 align:start position:0% the shortest and most reliable path to 05:54:44.940 --> 05:54:46.190 align:start position:0% the shortest and most reliable path to our<05:54:45.120> destination 05:54:46.190 --> 05:54:46.200 align:start position:0% our destination 05:54:46.200 --> 05:54:49.010 align:start position:0% our destination here<05:54:46.680> on<05:54:46.920> the<05:54:47.100> fourth<05:54:47.458> layer<05:54:47.820> also<05:54:48.480> called<05:54:48.600> the 05:54:49.010 --> 05:54:49.020 align:start position:0% here on the fourth layer also called the 05:54:49.020 --> 05:54:51.470 align:start position:0% here on the fourth layer also called the transport<05:54:49.500> layer<05:54:49.920> some<05:54:50.520> crucial<05:54:50.820> functions 05:54:51.470 --> 05:54:51.480 align:start position:0% transport layer some crucial functions 05:54:51.480 --> 05:54:53.510 align:start position:0% transport layer some crucial functions are<05:54:51.718> taking<05:54:51.900> place<05:54:52.260> now<05:54:52.980> one<05:54:53.218> of<05:54:53.340> these 05:54:53.510 --> 05:54:53.520 align:start position:0% are taking place now one of these 05:54:53.520 --> 05:54:56.750 align:start position:0% are taking place now one of these functions<05:54:54.058> is<05:54:54.540> reliability<05:54:55.500> it<05:54:56.280> can<05:54:56.400> be<05:54:56.520> said 05:54:56.750 --> 05:54:56.760 align:start position:0% functions is reliability it can be said 05:54:56.760 --> 05:55:00.350 align:start position:0% functions is reliability it can be said that<05:54:57.240> the<05:54:57.900> TCP<05:54:58.740> protocol<05:54:59.340> what<05:55:00.058> you<05:55:00.240> might 05:55:00.350 --> 05:55:00.360 align:start position:0% that the TCP protocol what you might 05:55:00.360 --> 05:55:05.208 align:start position:0% that the TCP protocol what you might have<05:55:00.540> heard<05:55:00.780> in<05:55:01.740> TCP<05:55:02.638> IP<05:55:03.298> if<05:55:03.600> IP<05:55:04.080> was<05:55:04.440> on<05:55:04.860> the 05:55:05.208 --> 05:55:05.218 align:start position:0% have heard in TCP IP if IP was on the 05:55:05.218 --> 05:55:09.350 align:start position:0% have heard in TCP IP if IP was on the layer<05:55:05.940> 3<05:55:06.180> perhaps<05:55:06.840> then<05:55:07.080> layer<05:55:07.558> four<05:55:07.740> is<05:55:08.360> TCP 05:55:09.350 --> 05:55:09.360 align:start position:0% layer 3 perhaps then layer four is TCP 05:55:09.360 --> 05:55:12.708 align:start position:0% layer 3 perhaps then layer four is TCP the<05:55:10.080> TCP<05:55:10.558> portion<05:55:11.040> operates<05:55:12.000> on<05:55:12.240> this<05:55:12.420> layer 05:55:12.708 --> 05:55:12.718 align:start position:0% the TCP portion operates on this layer 05:55:12.718 --> 05:55:14.330 align:start position:0% the TCP portion operates on this layer or<05:55:12.900> at<05:55:13.138> least<05:55:13.260> close<05:55:13.680> enough<05:55:13.920> to<05:55:14.160> the 05:55:14.330 --> 05:55:14.340 align:start position:0% or at least close enough to the 05:55:14.340 --> 05:55:16.310 align:start position:0% or at least close enough to the transport<05:55:14.700> layer<05:55:15.058> to<05:55:15.240> be<05:55:15.360> considered<05:55:15.780> a<05:55:15.958> layer 05:55:16.310 --> 05:55:16.320 align:start position:0% transport layer to be considered a layer 05:55:16.320 --> 05:55:17.890 align:start position:0% transport layer to be considered a layer 4<05:55:16.558> Protocol 05:55:17.890 --> 05:55:17.900 align:start position:0% 4 Protocol 05:55:17.900 --> 05:55:21.170 align:start position:0% 4 Protocol just<05:55:18.900> to<05:55:19.080> sort<05:55:19.260> of<05:55:19.458> secondary<05:55:20.458> side<05:55:20.760> note<05:55:21.000> and 05:55:21.170 --> 05:55:21.180 align:start position:0% just to sort of secondary side note and 05:55:21.180 --> 05:55:23.690 align:start position:0% just to sort of secondary side note and we'll<05:55:21.360> talk<05:55:21.540> about<05:55:21.718> TCP<05:55:22.680> and<05:55:22.920> IP<05:55:23.218> a<05:55:23.458> little<05:55:23.580> bit 05:55:23.690 --> 05:55:23.700 align:start position:0% we'll talk about TCP and IP a little bit 05:55:23.700 --> 05:55:25.548 align:start position:0% we'll talk about TCP and IP a little bit more<05:55:23.878> in<05:55:24.000> depth<05:55:24.298> in<05:55:24.360> the<05:55:24.540> next<05:55:24.660> module<05:55:25.138> they 05:55:25.548 --> 05:55:25.558 align:start position:0% more in depth in the next module they 05:55:25.558 --> 05:55:28.368 align:start position:0% more in depth in the next module they have<05:55:25.740> their<05:55:25.980> own<05:55:26.160> model<05:55:26.458> the<05:55:27.000> OSI<05:55:27.540> model<05:55:27.900> is 05:55:28.368 --> 05:55:28.378 align:start position:0% have their own model the OSI model is 05:55:28.378 --> 05:55:30.048 align:start position:0% have their own model the OSI model is sort<05:55:28.500> of<05:55:28.620> a<05:55:28.798> theoretical<05:55:29.280> model<05:55:29.520> it<05:55:29.700> was<05:55:29.820> never 05:55:30.048 --> 05:55:30.058 align:start position:0% sort of a theoretical model it was never 05:55:30.058 --> 05:55:32.690 align:start position:0% sort of a theoretical model it was never actually<05:55:30.540> implemented<05:55:31.320> as<05:55:31.920> it<05:55:32.100> was<05:55:32.280> created 05:55:32.690 --> 05:55:32.700 align:start position:0% actually implemented as it was created 05:55:32.700 --> 05:55:34.970 align:start position:0% actually implemented as it was created that<05:55:33.240> being<05:55:33.480> said<05:55:33.660> we<05:55:34.020> still<05:55:34.138> use<05:55:34.500> it<05:55:34.680> in 05:55:34.970 --> 05:55:34.980 align:start position:0% that being said we still use it in 05:55:34.980 --> 05:55:36.530 align:start position:0% that being said we still use it in discussing<05:55:35.400> a<05:55:35.580> lot<05:55:35.638> of<05:55:35.760> stuff<05:55:35.940> which<05:55:36.180> is<05:55:36.298> why 05:55:36.530 --> 05:55:36.540 align:start position:0% discussing a lot of stuff which is why 05:55:36.540 --> 05:55:39.048 align:start position:0% discussing a lot of stuff which is why we<05:55:36.718> need<05:55:36.840> to<05:55:36.958> talk<05:55:37.080> about<05:55:37.320> so<05:55:38.040> the<05:55:38.400> reliability 05:55:39.048 --> 05:55:39.058 align:start position:0% we need to talk about so the reliability 05:55:39.058 --> 05:55:43.070 align:start position:0% we need to talk about so the reliability is<05:55:39.660> guaranteed<05:55:40.500> by<05:55:41.340> in<05:55:41.940> here<05:55:42.120> the<05:55:42.540> connection 05:55:43.070 --> 05:55:43.080 align:start position:0% is guaranteed by in here the connection 05:55:43.080 --> 05:55:50.650 align:start position:0% is guaranteed by in here the connection oriented 05:55:50.650 --> 05:55:50.660 align:start position:0% 05:55:50.660 --> 05:55:53.390 align:start position:0% protocols<05:55:51.660> that<05:55:52.080> are<05:55:52.200> on<05:55:52.320> layer<05:55:52.620> four 05:55:53.390 --> 05:55:53.400 align:start position:0% protocols that are on layer four 05:55:53.400 --> 05:55:55.610 align:start position:0% protocols that are on layer four so<05:55:53.760> the<05:55:54.058> transport<05:55:54.420> layer<05:55:54.780> has<05:55:55.020> mechanisms 05:55:55.610 --> 05:55:55.620 align:start position:0% so the transport layer has mechanisms 05:55:55.620 --> 05:56:00.410 align:start position:0% so the transport layer has mechanisms that<05:55:55.980> keep<05:55:56.400> track<05:55:56.900> of<05:55:57.900> uh<05:55:58.440> these<05:55:58.980> segments<05:55:59.878> and 05:56:00.410 --> 05:56:00.420 align:start position:0% that keep track of uh these segments and 05:56:00.420 --> 05:56:02.868 align:start position:0% that keep track of uh these segments and when<05:56:00.660> segments<05:56:01.378> fail<05:56:01.620> the<05:56:02.040> transport<05:56:02.458> layer 05:56:02.868 --> 05:56:02.878 align:start position:0% when segments fail the transport layer 05:56:02.878 --> 05:56:04.910 align:start position:0% when segments fail the transport layer resends<05:56:03.660> them<05:56:03.780> there's<05:56:04.320> also<05:56:04.620> this 05:56:04.910 --> 05:56:04.920 align:start position:0% resends them there's also this 05:56:04.920 --> 05:56:08.208 align:start position:0% resends them there's also this acknowledgment<05:56:05.760> feature<05:56:06.360> such<05:56:07.020> as<05:56:07.378> a<05:56:07.798> like<05:56:08.040> a 05:56:08.208 --> 05:56:08.218 align:start position:0% acknowledgment feature such as a like a 05:56:08.218 --> 05:56:10.430 align:start position:0% acknowledgment feature such as a like a certified<05:56:08.580> letter<05:56:08.940> would<05:56:09.298> have<05:56:09.480> that<05:56:10.080> ensures 05:56:10.430 --> 05:56:10.440 align:start position:0% certified letter would have that ensures 05:56:10.440 --> 05:56:12.770 align:start position:0% certified letter would have that ensures that<05:56:10.740> when<05:56:10.980> a<05:56:11.280> message<05:56:11.458> is<05:56:11.820> received<05:56:12.360> by<05:56:12.600> the 05:56:12.770 --> 05:56:12.780 align:start position:0% that when a message is received by the 05:56:12.780 --> 05:56:15.170 align:start position:0% that when a message is received by the destination<05:56:13.260> the<05:56:14.040> transport<05:56:14.458> layer<05:56:14.878> is 05:56:15.170 --> 05:56:15.180 align:start position:0% destination the transport layer is 05:56:15.180 --> 05:56:17.570 align:start position:0% destination the transport layer is notified<05:56:15.600> for<05:56:16.440> instance<05:56:16.680> by<05:56:17.100> a<05:56:17.400> message 05:56:17.570 --> 05:56:17.580 align:start position:0% notified for instance by a message 05:56:17.580 --> 05:56:21.230 align:start position:0% notified for instance by a message received<05:56:18.240> successfully<05:56:18.900> what<05:56:19.440> we<05:56:19.620> call<05:56:19.860> a<05:56:20.520> ack 05:56:21.230 --> 05:56:21.240 align:start position:0% received successfully what we call a ack 05:56:21.240 --> 05:56:25.150 align:start position:0% received successfully what we call a ack packet<05:56:21.780> or<05:56:22.080> acknowledgment<05:56:22.798> packet 05:56:25.150 --> 05:56:25.160 align:start position:0% packet or acknowledgment packet 05:56:25.160 --> 05:56:28.128 align:start position:0% packet or acknowledgment packet besides<05:56:26.160> these<05:56:26.580> guaranteed<05:56:27.540> delivery 05:56:28.128 --> 05:56:28.138 align:start position:0% besides these guaranteed delivery 05:56:28.138 --> 05:56:30.770 align:start position:0% besides these guaranteed delivery features<05:56:28.558> we<05:56:29.100> also<05:56:29.340> have<05:56:29.520> what's<05:56:29.940> called<05:56:30.180> data 05:56:30.770 --> 05:56:30.780 align:start position:0% features we also have what's called data 05:56:30.780 --> 05:56:33.770 align:start position:0% features we also have what's called data flow<05:56:31.020> control<05:56:31.280> this<05:56:32.280> function<05:56:32.638> ensures<05:56:33.420> that 05:56:33.770 --> 05:56:33.780 align:start position:0% flow control this function ensures that 05:56:33.780 --> 05:56:36.170 align:start position:0% flow control this function ensures that during<05:56:34.080> the<05:56:34.378> data<05:56:34.740> transfer<05:56:35.218> the<05:56:35.878> receiving 05:56:36.170 --> 05:56:36.180 align:start position:0% during the data transfer the receiving 05:56:36.180 --> 05:56:38.030 align:start position:0% during the data transfer the receiving end<05:56:36.420> doesn't<05:56:36.718> get<05:56:36.958> flooded<05:56:37.440> with<05:56:37.680> too<05:56:37.860> much 05:56:38.030 --> 05:56:38.040 align:start position:0% end doesn't get flooded with too much 05:56:38.040 --> 05:56:40.910 align:start position:0% end doesn't get flooded with too much data<05:56:38.580> at<05:56:38.820> any<05:56:39.000> one<05:56:39.240> time<05:56:39.540> later<05:56:40.320> in<05:56:40.558> the<05:56:40.620> lesson 05:56:40.910 --> 05:56:40.920 align:start position:0% data at any one time later in the lesson 05:56:40.920 --> 05:56:42.890 align:start position:0% data at any one time later in the lesson we're<05:56:41.040> going<05:56:41.218> to<05:56:41.280> talk<05:56:41.400> about<05:56:41.580> different<05:56:42.058> data 05:56:42.890 --> 05:56:42.900 align:start position:0% we're going to talk about different data 05:56:42.900 --> 05:56:43.868 align:start position:0% we're going to talk about different data flow 05:56:43.868 --> 05:56:43.878 align:start position:0% flow 05:56:43.878 --> 05:56:46.250 align:start position:0% flow techniques<05:56:44.878> and<05:56:45.120> flow<05:56:45.420> control<05:56:45.600> techniques 05:56:46.250 --> 05:56:46.260 align:start position:0% techniques and flow control techniques 05:56:46.260 --> 05:56:48.530 align:start position:0% techniques and flow control techniques that<05:56:46.500> are<05:56:46.620> used<05:56:46.920> the<05:56:47.700> transport<05:56:48.120> layer<05:56:48.420> is 05:56:48.530 --> 05:56:48.540 align:start position:0% that are used the transport layer is 05:56:48.540 --> 05:56:50.510 align:start position:0% that are used the transport layer is where<05:56:48.780> something<05:56:49.138> else<05:56:49.320> called<05:56:49.620> sequencing 05:56:50.510 --> 05:56:50.520 align:start position:0% where something else called sequencing 05:56:50.520 --> 05:56:53.330 align:start position:0% where something else called sequencing of<05:56:50.760> data<05:56:51.120> occurs<05:56:51.660> basically<05:56:52.500> when<05:56:52.798> data<05:56:53.160> is 05:56:53.330 --> 05:56:53.340 align:start position:0% of data occurs basically when data is 05:56:53.340 --> 05:56:56.208 align:start position:0% of data occurs basically when data is transmitted<05:56:54.000> it's<05:56:54.718> either<05:56:54.958> broken<05:56:55.320> apart<05:56:55.798> or 05:56:56.208 --> 05:56:56.218 align:start position:0% transmitted it's either broken apart or 05:56:56.218 --> 05:56:58.310 align:start position:0% transmitted it's either broken apart or fragmented<05:56:56.940> to<05:56:57.180> be<05:56:57.298> able<05:56:57.420> to<05:56:57.540> send<05:56:57.718> it<05:56:57.900> across 05:56:58.310 --> 05:56:58.320 align:start position:0% fragmented to be able to send it across 05:56:58.320 --> 05:57:00.708 align:start position:0% fragmented to be able to send it across the<05:56:58.500> medium<05:56:58.860> and<05:56:59.280> when<05:56:59.520> it's<05:56:59.638> fragmented<05:57:00.420> each 05:57:00.708 --> 05:57:00.718 align:start position:0% the medium and when it's fragmented each 05:57:00.718 --> 05:57:03.350 align:start position:0% the medium and when it's fragmented each fragment<05:57:01.200> or<05:57:01.500> piece<05:57:01.920> is<05:57:02.160> labeled<05:57:02.580> with<05:57:03.120> a 05:57:03.350 --> 05:57:03.360 align:start position:0% fragment or piece is labeled with a 05:57:03.360 --> 05:57:05.208 align:start position:0% fragment or piece is labeled with a specific<05:57:03.718> number<05:57:04.080> so<05:57:04.740> that<05:57:04.860> when<05:57:05.100> the 05:57:05.208 --> 05:57:05.218 align:start position:0% specific number so that when the 05:57:05.218 --> 05:57:08.030 align:start position:0% specific number so that when the receiving<05:57:05.520> end<05:57:06.080> receives<05:57:07.080> uh<05:57:07.740> when<05:57:07.920> the 05:57:08.030 --> 05:57:08.040 align:start position:0% receiving end receives uh when the 05:57:08.040 --> 05:57:09.590 align:start position:0% receiving end receives uh when the receiving<05:57:08.280> end<05:57:08.458> of<05:57:08.638> the<05:57:08.820> transport<05:57:09.180> layer 05:57:09.590 --> 05:57:09.600 align:start position:0% receiving end of the transport layer 05:57:09.600 --> 05:57:12.590 align:start position:0% receiving end of the transport layer receives<05:57:10.440> this<05:57:10.920> data<05:57:11.340> it<05:57:11.638> can<05:57:11.820> be<05:57:11.940> reassembled 05:57:12.590 --> 05:57:12.600 align:start position:0% receives this data it can be reassembled 05:57:12.600 --> 05:57:14.390 align:start position:0% receives this data it can be reassembled and<05:57:12.900> put<05:57:13.080> back<05:57:13.378> together<05:57:13.620> in<05:57:13.980> the<05:57:14.100> proper 05:57:14.390 --> 05:57:14.400 align:start position:0% and put back together in the proper 05:57:14.400 --> 05:57:15.948 align:start position:0% and put back together in the proper order<05:57:14.520> this<05:57:15.240> is<05:57:15.360> really<05:57:15.540> important 05:57:15.948 --> 05:57:15.958 align:start position:0% order this is really important 05:57:15.958 --> 05:57:18.170 align:start position:0% order this is really important especially<05:57:16.440> when<05:57:16.920> data<05:57:17.218> is<05:57:17.340> received<05:57:17.760> out<05:57:18.058> of 05:57:18.170 --> 05:57:18.180 align:start position:0% especially when data is received out of 05:57:18.180 --> 05:57:20.990 align:start position:0% especially when data is received out of order<05:57:18.360> as<05:57:18.900> I<05:57:19.080> just<05:57:19.260> demonstrated<05:57:19.798> now<05:57:20.580> in 05:57:20.990 --> 05:57:21.000 align:start position:0% order as I just demonstrated now in 05:57:21.000 --> 05:57:23.868 align:start position:0% order as I just demonstrated now in essence<05:57:21.298> this<05:57:21.780> layer<05:57:22.080> is<05:57:22.440> much<05:57:22.798> like<05:57:23.218> the 05:57:23.868 --> 05:57:23.878 align:start position:0% essence this layer is much like the 05:57:23.878 --> 05:57:26.030 align:start position:0% essence this layer is much like the standards<05:57:24.360> and<05:57:24.480> the<05:57:24.600> laws<05:57:24.840> that<05:57:25.320> we<05:57:25.558> have<05:57:25.740> in 05:57:26.030 --> 05:57:26.040 align:start position:0% standards and the laws that we have in 05:57:26.040 --> 05:57:27.890 align:start position:0% standards and the laws that we have in place<05:57:26.218> on<05:57:26.458> our<05:57:26.638> highways<05:57:27.058> they<05:57:27.298> ensure<05:57:27.600> that 05:57:27.890 --> 05:57:27.900 align:start position:0% place on our highways they ensure that 05:57:27.900 --> 05:57:30.230 align:start position:0% place on our highways they ensure that Vehicles<05:57:28.320> get<05:57:28.920> us<05:57:29.100> to<05:57:29.340> where<05:57:29.520> we<05:57:29.700> need<05:57:29.878> to<05:57:30.058> be 05:57:30.230 --> 05:57:30.240 align:start position:0% Vehicles get us to where we need to be 05:57:30.240 --> 05:57:32.930 align:start position:0% Vehicles get us to where we need to be safely<05:57:30.958> and<05:57:31.500> on<05:57:31.740> time<05:57:31.920> now<05:57:32.520> some<05:57:32.638> of<05:57:32.760> the<05:57:32.820> other 05:57:32.930 --> 05:57:32.940 align:start position:0% safely and on time now some of the other 05:57:32.940 --> 05:57:34.610 align:start position:0% safely and on time now some of the other protocols<05:57:33.420> you<05:57:33.600> may<05:57:33.718> have<05:57:33.900> heard<05:57:34.138> of<05:57:34.320> that 05:57:34.610 --> 05:57:34.620 align:start position:0% protocols you may have heard of that 05:57:34.620 --> 05:57:39.110 align:start position:0% protocols you may have heard of that operate<05:57:34.980> on<05:57:35.160> this<05:57:35.340> layer<05:57:35.700> are<05:57:36.980> sctp<05:57:37.980> uh<05:57:38.940> some 05:57:39.110 --> 05:57:39.120 align:start position:0% operate on this layer are sctp uh some 05:57:39.120 --> 05:57:42.590 align:start position:0% operate on this layer are sctp uh some tunneling<05:57:39.660> protocols<05:57:40.378> and<05:57:41.040> uh<05:57:41.820> more 05:57:42.590 --> 05:57:42.600 align:start position:0% tunneling protocols and uh more 05:57:42.600 --> 05:57:45.048 align:start position:0% tunneling protocols and uh more importantly<05:57:43.020> here<05:57:43.378> when<05:57:43.680> data<05:57:44.160> is<05:57:44.520> sort<05:57:44.878> of 05:57:45.048 --> 05:57:45.058 align:start position:0% importantly here when data is sort of 05:57:45.058 --> 05:57:48.048 align:start position:0% importantly here when data is sort of partitioned<05:57:45.958> out<05:57:46.080> it's<05:57:46.500> called<05:57:46.740> a<05:57:47.100> segment<05:57:47.458> as 05:57:48.048 --> 05:57:48.058 align:start position:0% partitioned out it's called a segment as 05:57:48.058 --> 05:57:52.610 align:start position:0% partitioned out it's called a segment as opposed<05:57:48.480> to<05:57:48.540> a<05:57:49.500> datagram<05:57:50.040> or<05:57:51.000> a<05:57:51.180> frame<05:57:51.540> now<05:57:52.200> the 05:57:52.610 --> 05:57:52.620 align:start position:0% opposed to a datagram or a frame now the 05:57:52.620 --> 05:57:55.850 align:start position:0% opposed to a datagram or a frame now the next<05:57:52.798> layer<05:57:53.280> is<05:57:54.180> uh<05:57:54.780> I<05:57:55.200> think<05:57:55.260> it's<05:57:55.440> one<05:57:55.680> of<05:57:55.798> the 05:57:55.850 --> 05:57:55.860 align:start position:0% next layer is uh I think it's one of the 05:57:55.860 --> 05:57:58.070 align:start position:0% next layer is uh I think it's one of the easier<05:57:56.160> ones<05:57:56.458> to<05:57:56.580> memorize<05:57:56.940> it's<05:57:57.240> called<05:57:57.480> the 05:57:58.070 --> 05:57:58.080 align:start position:0% easier ones to memorize it's called the 05:57:58.080 --> 05:58:00.708 align:start position:0% easier ones to memorize it's called the session<05:57:58.320> layer<05:57:58.860> and<05:57:59.160> layer<05:57:59.638> five<05:57:59.878> and<05:58:00.540> it's 05:58:00.708 --> 05:58:00.718 align:start position:0% session layer and layer five and it's 05:58:00.718 --> 05:58:03.110 align:start position:0% session layer and layer five and it's pretty<05:58:01.020> simple<05:58:01.260> because<05:58:01.860> the<05:58:02.580> sole<05:58:02.878> purpose 05:58:03.110 --> 05:58:03.120 align:start position:0% pretty simple because the sole purpose 05:58:03.120 --> 05:58:05.570 align:start position:0% pretty simple because the sole purpose of<05:58:03.298> this<05:58:03.480> layer<05:58:03.780> is<05:58:03.900> to<05:58:04.200> establish<05:58:04.740> maintain 05:58:05.570 --> 05:58:05.580 align:start position:0% of this layer is to establish maintain 05:58:05.580 --> 05:58:08.510 align:start position:0% of this layer is to establish maintain when<05:58:05.940> it<05:58:06.058> comes<05:58:06.240> time<05:58:06.480> to<05:58:06.780> shut<05:58:06.958> down<05:58:07.520> or 05:58:08.510 --> 05:58:08.520 align:start position:0% when it comes time to shut down or 05:58:08.520 --> 05:58:11.690 align:start position:0% when it comes time to shut down or conclude<05:58:09.000> the<05:58:09.240> communication<05:58:10.040> session<05:58:11.040> now 05:58:11.690 --> 05:58:11.700 align:start position:0% conclude the communication session now 05:58:11.700 --> 05:58:13.730 align:start position:0% conclude the communication session now while<05:58:11.940> the<05:58:12.120> OSI<05:58:12.540> model<05:58:12.780> assigns<05:58:13.500> the 05:58:13.730 --> 05:58:13.740 align:start position:0% while the OSI model assigns the 05:58:13.740 --> 05:58:16.548 align:start position:0% while the OSI model assigns the responsibility<05:58:14.580> of<05:58:15.058> this<05:58:15.718> termination<05:58:16.200> of 05:58:16.548 --> 05:58:16.558 align:start position:0% responsibility of this termination of 05:58:16.558 --> 05:58:19.850 align:start position:0% responsibility of this termination of sessions<05:58:17.120> to<05:58:18.120> the<05:58:18.360> session<05:58:18.600> layer<05:58:19.260> some<05:58:19.680> other 05:58:19.850 --> 05:58:19.860 align:start position:0% sessions to the session layer some other 05:58:19.860 --> 05:58:21.470 align:start position:0% sessions to the session layer some other models<05:58:20.280> have<05:58:20.520> performed<05:58:20.940> this<05:58:21.058> on<05:58:21.360> a 05:58:21.470 --> 05:58:21.480 align:start position:0% models have performed this on a 05:58:21.480 --> 05:58:22.670 align:start position:0% models have performed this on a different<05:58:21.600> layer<05:58:22.020> and<05:58:22.080> we'll<05:58:22.320> talk<05:58:22.500> about 05:58:22.670 --> 05:58:22.680 align:start position:0% different layer and we'll talk about 05:58:22.680 --> 05:58:24.770 align:start position:0% different layer and we'll talk about that<05:58:23.040> a<05:58:23.400> little<05:58:23.638> bit<05:58:23.820> more<05:58:24.058> some<05:58:24.600> of<05:58:24.718> the 05:58:24.770 --> 05:58:24.780 align:start position:0% that a little bit more some of the 05:58:24.780 --> 05:58:27.708 align:start position:0% that a little bit more some of the protocols<05:58:25.680> you<05:58:25.860> might<05:58:26.040> see<05:58:26.218> on<05:58:26.458> here<05:58:26.700> are<05:58:27.420> for 05:58:27.708 --> 05:58:27.718 align:start position:0% protocols you might see on here are for 05:58:27.718 --> 05:58:30.470 align:start position:0% protocols you might see on here are for instance<05:58:28.280> RPC<05:58:29.280> which<05:58:29.820> stands<05:58:30.120> for<05:58:30.240> remote 05:58:30.470 --> 05:58:30.480 align:start position:0% instance RPC which stands for remote 05:58:30.480 --> 05:58:33.850 align:start position:0% instance RPC which stands for remote procedure<05:58:31.260> call<05:58:32.058> and 05:58:33.850 --> 05:58:33.860 align:start position:0% procedure call and 05:58:33.860 --> 05:58:38.690 align:start position:0% procedure call and TLS<05:58:34.860> and<05:58:35.638> SSL<05:58:36.420> as<05:58:37.378> well<05:58:37.500> so<05:58:38.100> this<05:58:38.280> layer 05:58:38.690 --> 05:58:38.700 align:start position:0% TLS and SSL as well so this layer 05:58:38.700 --> 05:58:41.990 align:start position:0% TLS and SSL as well so this layer manages<05:58:39.500> how<05:58:40.500> and<05:58:40.680> for<05:58:40.860> how<05:58:41.218> long<05:58:41.340> and<05:58:41.638> what 05:58:41.990 --> 05:58:42.000 align:start position:0% manages how and for how long and what 05:58:42.000 --> 05:58:46.070 align:start position:0% manages how and for how long and what way<05:58:42.298> a<05:58:43.020> device<05:58:43.260> is<05:58:43.620> going<05:58:43.920> to<05:58:44.600> establish<05:58:45.600> a 05:58:46.070 --> 05:58:46.080 align:start position:0% way a device is going to establish a 05:58:46.080 --> 05:58:47.628 align:start position:0% way a device is going to establish a connection<05:58:46.378> during<05:58:46.920> the<05:58:47.218> communications 05:58:47.628 --> 05:58:47.638 align:start position:0% connection during the communications 05:58:47.638 --> 05:58:49.670 align:start position:0% connection during the communications process<05:58:48.298> that<05:58:48.540> the<05:58:48.780> layer<05:58:49.020> is<05:58:49.138> not<05:58:49.378> yet 05:58:49.670 --> 05:58:49.680 align:start position:0% process that the layer is not yet 05:58:49.680 --> 05:58:51.708 align:start position:0% process that the layer is not yet completed<05:58:50.400> with<05:58:50.638> its<05:58:50.878> functions<05:58:51.240> the<05:58:51.480> rest<05:58:51.600> of 05:58:51.708 --> 05:58:51.718 align:start position:0% completed with its functions the rest of 05:58:51.718 --> 05:58:54.048 align:start position:0% completed with its functions the rest of the<05:58:51.840> network<05:58:51.958> just<05:58:52.320> has<05:58:52.500> to<05:58:52.680> wait 05:58:54.048 --> 05:58:54.058 align:start position:0% the network just has to wait 05:58:54.058 --> 05:58:56.448 align:start position:0% the network just has to wait so<05:58:54.600> in<05:58:54.840> keeping<05:58:55.200> with<05:58:55.320> the<05:58:55.500> analogy<05:58:55.980> of<05:58:56.280> the 05:58:56.448 --> 05:58:56.458 align:start position:0% so in keeping with the analogy of the 05:58:56.458 --> 05:58:58.128 align:start position:0% so in keeping with the analogy of the boss<05:58:56.638> in<05:58:57.058> order<05:58:57.298> to<05:58:57.480> understand<05:58:57.600> how<05:58:58.020> the 05:58:58.128 --> 05:58:58.138 align:start position:0% boss in order to understand how the 05:58:58.138 --> 05:58:59.990 align:start position:0% boss in order to understand how the session<05:58:58.260> layer<05:58:58.740> fits<05:58:59.040> in<05:58:59.160> let's<05:58:59.700> take<05:58:59.820> a<05:58:59.940> look 05:58:59.990 --> 05:59:00.000 align:start position:0% session layer fits in let's take a look 05:59:00.000 --> 05:59:03.590 align:start position:0% session layer fits in let's take a look at<05:59:00.180> exactly<05:59:00.740> why<05:59:01.740> we're<05:59:01.920> using<05:59:02.280> our<05:59:02.458> buses<05:59:02.940> is 05:59:03.590 --> 05:59:03.600 align:start position:0% at exactly why we're using our buses is 05:59:03.600 --> 05:59:05.990 align:start position:0% at exactly why we're using our buses is it<05:59:03.780> for<05:59:03.958> transporting<05:59:04.558> people<05:59:04.860> or<05:59:05.520> is<05:59:05.638> it<05:59:05.820> for 05:59:05.990 --> 05:59:06.000 align:start position:0% it for transporting people or is it for 05:59:06.000 --> 05:59:08.990 align:start position:0% it for transporting people or is it for transporting<05:59:06.660> top<05:59:07.500> secret<05:59:07.798> documents<05:59:08.580> from 05:59:08.990 --> 05:59:09.000 align:start position:0% transporting top secret documents from 05:59:09.000 --> 05:59:10.250 align:start position:0% transporting top secret documents from the<05:59:09.120> main<05:59:09.298> office<05:59:09.540> building<05:59:09.780> to<05:59:10.020> the<05:59:10.138> remote 05:59:10.250 --> 05:59:10.260 align:start position:0% the main office building to the remote 05:59:10.260 --> 05:59:13.128 align:start position:0% the main office building to the remote office<05:59:10.700> this<05:59:11.700> Y<05:59:11.940> is<05:59:12.240> going<05:59:12.420> to<05:59:12.540> determine 05:59:13.128 --> 05:59:13.138 align:start position:0% office this Y is going to determine 05:59:13.138 --> 05:59:15.350 align:start position:0% office this Y is going to determine several<05:59:13.920> things<05:59:14.100> for<05:59:14.400> this<05:59:14.580> layer<05:59:14.878> right<05:59:15.058> if 05:59:15.350 --> 05:59:15.360 align:start position:0% several things for this layer right if 05:59:15.360 --> 05:59:17.750 align:start position:0% several things for this layer right if it's<05:59:15.540> determined<05:59:16.080> that<05:59:16.260> we<05:59:16.558> need 05:59:17.750 --> 05:59:17.760 align:start position:0% it's determined that we need 05:59:17.760 --> 05:59:18.590 align:start position:0% it's determined that we need um 05:59:18.590 --> 05:59:18.600 align:start position:0% um 05:59:18.600 --> 05:59:22.250 align:start position:0% um several<05:59:19.320> connections<05:59:19.980> to<05:59:20.820> take<05:59:21.240> a<05:59:21.660> private 05:59:22.250 --> 05:59:22.260 align:start position:0% several connections to take a private 05:59:22.260 --> 05:59:24.048 align:start position:0% several connections to take a private Highway<05:59:22.740> for<05:59:23.400> instance<05:59:23.580> it<05:59:23.760> might<05:59:23.940> be 05:59:24.048 --> 05:59:24.058 align:start position:0% Highway for instance it might be 05:59:24.058 --> 05:59:26.990 align:start position:0% Highway for instance it might be determined<05:59:24.480> that<05:59:24.600> we<05:59:24.780> need<05:59:24.958> a<05:59:25.200> private<05:59:25.980> bus<05:59:26.280> to 05:59:26.990 --> 05:59:27.000 align:start position:0% determined that we need a private bus to 05:59:27.000 --> 05:59:27.770 align:start position:0% determined that we need a private bus to take 05:59:27.770 --> 05:59:27.780 align:start position:0% take 05:59:27.780 --> 05:59:28.548 align:start position:0% take um 05:59:28.548 --> 05:59:28.558 align:start position:0% um 05:59:28.558 --> 05:59:30.670 align:start position:0% um special<05:59:29.100> documents 05:59:30.670 --> 05:59:30.680 align:start position:0% special documents 05:59:30.680 --> 05:59:33.410 align:start position:0% special documents to<05:59:31.680> maintain<05:59:31.980> security<05:59:32.340> or<05:59:32.820> take<05:59:33.000> a<05:59:33.240> special 05:59:33.410 --> 05:59:33.420 align:start position:0% to maintain security or take a special 05:59:33.420 --> 05:59:35.448 align:start position:0% to maintain security or take a special Highway<05:59:33.780> for<05:59:34.320> instance<05:59:34.558> so<05:59:35.160> the<05:59:35.280> session 05:59:35.448 --> 05:59:35.458 align:start position:0% Highway for instance so the session 05:59:35.458 --> 05:59:37.690 align:start position:0% Highway for instance so the session layer<05:59:35.878> is<05:59:35.940> what's<05:59:36.180> responsible<05:59:36.780> for 05:59:37.690 --> 05:59:37.700 align:start position:0% layer is what's responsible for 05:59:37.700 --> 05:59:40.490 align:start position:0% layer is what's responsible for determining<05:59:38.700> what<05:59:39.180> type<05:59:39.420> of<05:59:39.540> data<05:59:39.840> and<05:59:39.958> how<05:59:40.260> we 05:59:40.490 --> 05:59:40.500 align:start position:0% determining what type of data and how we 05:59:40.500 --> 05:59:42.470 align:start position:0% determining what type of data and how we need<05:59:40.620> to<05:59:40.740> connect<05:59:40.860> this<05:59:41.458> session<05:59:41.820> continuing 05:59:42.470 --> 05:59:42.480 align:start position:0% need to connect this session continuing 05:59:42.480 --> 05:59:44.390 align:start position:0% need to connect this session continuing on<05:59:42.600> to<05:59:42.780> the<05:59:42.900> next<05:59:42.958> layer<05:59:43.260> is<05:59:43.500> the<05:59:43.860> presentation 05:59:44.390 --> 05:59:44.400 align:start position:0% on to the next layer is the presentation 05:59:44.400 --> 05:59:46.730 align:start position:0% on to the next layer is the presentation layer<05:59:44.878> or<05:59:45.058> layer<05:59:45.480> six<05:59:45.718> this<05:59:46.320> layer<05:59:46.620> is 05:59:46.730 --> 05:59:46.740 align:start position:0% layer or layer six this layer is 05:59:46.740 --> 05:59:48.770 align:start position:0% layer or layer six this layer is responsible<05:59:47.218> for<05:59:47.520> taking<05:59:47.760> the<05:59:48.058> data<05:59:48.360> from<05:59:48.600> the 05:59:48.770 --> 05:59:48.780 align:start position:0% responsible for taking the data from the 05:59:48.780 --> 05:59:50.330 align:start position:0% responsible for taking the data from the application<05:59:49.378> layer<05:59:49.798> which<05:59:49.980> is<05:59:50.040> the<05:59:50.218> next 05:59:50.330 --> 05:59:50.340 align:start position:0% application layer which is the next 05:59:50.340 --> 05:59:52.310 align:start position:0% application layer which is the next layer<05:59:50.638> we'll<05:59:50.760> talk<05:59:51.000> about<05:59:51.120> and<05:59:51.840> translating 05:59:52.310 --> 05:59:52.320 align:start position:0% layer we'll talk about and translating 05:59:52.320 --> 05:59:55.310 align:start position:0% layer we'll talk about and translating it<05:59:52.620> into<05:59:52.920> an<05:59:53.700> intermediary<05:59:54.420> language<05:59:54.958> that 05:59:55.310 --> 05:59:55.320 align:start position:0% it into an intermediary language that 05:59:55.320 --> 05:59:56.650 align:start position:0% it into an intermediary language that the<05:59:55.558> rest<05:59:55.620> of<05:59:55.740> the<05:59:55.860> network<05:59:55.980> can<05:59:56.340> understand 05:59:56.650 --> 05:59:56.660 align:start position:0% the rest of the network can understand 05:59:56.660 --> 05:59:59.030 align:start position:0% the rest of the network can understand and<05:59:57.660> it's<05:59:57.780> also<05:59:58.080> going<05:59:58.138> to<05:59:58.200> perform<05:59:58.320> it<05:59:58.680> in 05:59:59.030 --> 05:59:59.040 align:start position:0% and it's also going to perform it in 05:59:59.040 --> 06:00:01.368 align:start position:0% and it's also going to perform it in reverse<05:59:59.458> on<05:59:59.760> the<05:59:59.820> receiving<06:00:00.120> end<06:00:00.420> also<06:00:01.260> in 06:00:01.368 --> 06:00:01.378 align:start position:0% reverse on the receiving end also in 06:00:01.378 --> 06:00:03.170 align:start position:0% reverse on the receiving end also in this<06:00:01.500> layer<06:00:01.798> data<06:00:02.218> encryption<06:00:02.820> and 06:00:03.170 --> 06:00:03.180 align:start position:0% this layer data encryption and 06:00:03.180 --> 06:00:06.288 align:start position:0% this layer data encryption and compression<06:00:03.840> takes<06:00:04.558> place<06:00:04.940> sometimes<06:00:05.940> called 06:00:06.288 --> 06:00:06.298 align:start position:0% compression takes place sometimes called 06:00:06.298 --> 06:00:09.708 align:start position:0% compression takes place sometimes called the<06:00:06.780> syntax<06:00:07.320> layer<06:00:07.860> because<06:00:08.160> of<06:00:08.940> its<06:00:09.298> data 06:00:09.708 --> 06:00:09.718 align:start position:0% the syntax layer because of its data 06:00:09.718 --> 06:00:12.650 align:start position:0% the syntax layer because of its data encryption<06:00:10.558> abilities<06:00:11.400> as<06:00:11.820> well<06:00:12.000> as<06:00:12.120> its 06:00:12.650 --> 06:00:12.660 align:start position:0% encryption abilities as well as its 06:00:12.660 --> 06:00:15.530 align:start position:0% encryption abilities as well as its conversion<06:00:13.200> to<06:00:13.620> a<06:00:13.980> network<06:00:14.280> relatable<06:00:15.000> format 06:00:15.530 --> 06:00:15.540 align:start position:0% conversion to a network relatable format 06:00:15.540 --> 06:00:18.170 align:start position:0% conversion to a network relatable format or<06:00:15.780> a<06:00:16.020> format<06:00:16.378> that<06:00:16.740> applications<06:00:17.638> can 06:00:18.170 --> 06:00:18.180 align:start position:0% or a format that applications can 06:00:18.180 --> 06:00:21.650 align:start position:0% or a format that applications can understand<06:00:18.740> now<06:00:19.740> what<06:00:20.580> this<06:00:20.878> really<06:00:21.120> means<06:00:21.480> is 06:00:21.650 --> 06:00:21.660 align:start position:0% understand now what this really means is 06:00:21.660 --> 06:00:23.330 align:start position:0% understand now what this really means is because<06:00:21.900> the<06:00:22.260> applications<06:00:22.680> is<06:00:23.040> going<06:00:23.218> to 06:00:23.330 --> 06:00:23.340 align:start position:0% because the applications is going to 06:00:23.340 --> 06:00:26.448 align:start position:0% because the applications is going to have<06:00:23.520> its<06:00:23.940> own<06:00:24.058> syntax<06:00:24.780> or<06:00:25.080> its<06:00:25.440> own<06:00:25.558> language 06:00:26.448 --> 06:00:26.458 align:start position:0% have its own syntax or its own language 06:00:26.458 --> 06:00:28.368 align:start position:0% have its own syntax or its own language the<06:00:27.180> presentation<06:00:27.600> layer<06:00:28.020> is<06:00:28.138> going<06:00:28.260> to<06:00:28.260> try 06:00:28.368 --> 06:00:28.378 align:start position:0% the presentation layer is going to try 06:00:28.378 --> 06:00:31.128 align:start position:0% the presentation layer is going to try to<06:00:28.500> a<06:00:29.100> map<06:00:29.340> between<06:00:29.760> those<06:00:30.058> languages<06:00:30.420> now<06:00:30.958> if 06:00:31.128 --> 06:00:31.138 align:start position:0% to a map between those languages now if 06:00:31.138 --> 06:00:33.048 align:start position:0% to a map between those languages now if the<06:00:31.260> mapping<06:00:31.558> is<06:00:31.740> available 06:00:33.048 --> 06:00:33.058 align:start position:0% the mapping is available 06:00:33.058 --> 06:00:34.788 align:start position:0% the mapping is available then<06:00:33.480> the<06:00:33.660> presentation<06:00:34.080> layer<06:00:34.440> is<06:00:34.558> going<06:00:34.740> to 06:00:34.788 --> 06:00:34.798 align:start position:0% then the presentation layer is going to 06:00:34.798 --> 06:00:37.490 align:start position:0% then the presentation layer is going to convert<06:00:35.160> the<06:00:35.280> data<06:00:35.580> into<06:00:35.878> Data<06:00:36.420> units<06:00:36.900> for<06:00:37.320> the 06:00:37.490 --> 06:00:37.500 align:start position:0% convert the data into Data units for the 06:00:37.500 --> 06:00:39.048 align:start position:0% convert the data into Data units for the session<06:00:37.680> protocol<06:00:38.160> and<06:00:38.400> after<06:00:38.580> that<06:00:38.760> it's 06:00:39.048 --> 06:00:39.058 align:start position:0% session protocol and after that it's 06:00:39.058 --> 06:00:41.330 align:start position:0% session protocol and after that it's send<06:00:39.360> down<06:00:39.660> the<06:00:39.958> stack<06:00:40.200> down<06:00:40.740> the<06:00:40.980> rest<06:00:41.100> of<06:00:41.218> the 06:00:41.330 --> 06:00:41.340 align:start position:0% send down the stack down the rest of the 06:00:41.340 --> 06:00:43.368 align:start position:0% send down the stack down the rest of the layers<06:00:41.638> to<06:00:42.180> do<06:00:42.360> everything<06:00:42.660> else<06:00:42.900> it<06:00:43.080> needs<06:00:43.320> to 06:00:43.368 --> 06:00:43.378 align:start position:0% layers to do everything else it needs to 06:00:43.378 --> 06:00:45.530 align:start position:0% layers to do everything else it needs to do<06:00:43.500> some<06:00:44.160> of<06:00:44.340> the<06:00:44.400> protocols<06:00:44.940> that<06:00:45.120> operate 06:00:45.530 --> 06:00:45.540 align:start position:0% do some of the protocols that operate 06:00:45.540 --> 06:00:47.350 align:start position:0% do some of the protocols that operate this<06:00:45.780> layer<06:00:46.138> are 06:00:47.350 --> 06:00:47.360 align:start position:0% this layer are 06:00:47.360 --> 06:00:49.850 align:start position:0% this layer are anything<06:00:48.360> that's<06:00:48.660> dealing<06:00:48.958> with<06:00:49.138> compression 06:00:49.850 --> 06:00:49.860 align:start position:0% anything that's dealing with compression 06:00:49.860 --> 06:00:56.030 align:start position:0% anything that's dealing with compression for<06:00:50.280> instance<06:00:51.080> PNG<06:00:52.080> jpegs 06:00:56.030 --> 06:00:56.040 align:start position:0% 06:00:56.040 --> 06:01:01.368 align:start position:0% Tiff<06:00:57.000> a<06:00:57.298> lot<06:00:57.420> of<06:00:57.600> these<06:00:58.020> sort<06:00:58.740> of<06:00:58.920> picture 06:01:01.368 --> 06:01:01.378 align:start position:0% Tiff a lot of these sort of picture 06:01:01.378 --> 06:01:04.190 align:start position:0% Tiff a lot of these sort of picture file<06:01:02.218> extension<06:01:02.700> that<06:01:02.820> you've<06:01:03.058> seen<06:01:03.240> this 06:01:04.190 --> 06:01:04.200 align:start position:0% file extension that you've seen this 06:01:04.200 --> 06:01:06.048 align:start position:0% file extension that you've seen this layer<06:01:04.558> also<06:01:04.860> performs<06:01:05.280> code<06:01:05.520> conversions 06:01:06.048 --> 06:01:06.058 align:start position:0% layer also performs code conversions 06:01:06.058 --> 06:01:07.430 align:start position:0% layer also performs code conversions they're<06:01:06.240> going<06:01:06.360> to<06:01:06.420> take<06:01:06.600> raw<06:01:07.020> application 06:01:07.430 --> 06:01:07.440 align:start position:0% they're going to take raw application 06:01:07.440 --> 06:01:09.230 align:start position:0% they're going to take raw application data<06:01:07.920> and<06:01:07.980> compress<06:01:08.458> them<06:01:08.638> into<06:01:08.878> more 06:01:09.230 --> 06:01:09.240 align:start position:0% data and compress them into more 06:01:09.240 --> 06:01:12.110 align:start position:0% data and compress them into more manageable<06:01:10.138> forms<06:01:10.620> for<06:01:10.920> transmitting<06:01:11.638> now 06:01:12.110 --> 06:01:12.120 align:start position:0% manageable forms for transmitting now 06:01:12.120 --> 06:01:14.090 align:start position:0% manageable forms for transmitting now regarding<06:01:12.480> the<06:01:12.780> translation<06:01:13.378> capabilities 06:01:14.090 --> 06:01:14.100 align:start position:0% regarding the translation capabilities 06:01:14.100 --> 06:01:16.190 align:start position:0% regarding the translation capabilities of<06:01:14.400> this<06:01:14.580> layer<06:01:14.940> think<06:01:15.540> of<06:01:15.718> like<06:01:15.958> two 06:01:16.190 --> 06:01:16.200 align:start position:0% of this layer think of like two 06:01:16.200 --> 06:01:18.470 align:start position:0% of this layer think of like two different<06:01:16.378> systems<06:01:17.160> that<06:01:18.000> are<06:01:18.240> very 06:01:18.470 --> 06:01:18.480 align:start position:0% different systems that are very 06:01:18.480 --> 06:01:20.390 align:start position:0% different systems that are very different<06:01:18.718> from<06:01:19.080> each<06:01:19.260> other<06:01:19.440> one<06:01:19.980> perhaps 06:01:20.390 --> 06:01:20.400 align:start position:0% different from each other one perhaps 06:01:20.400 --> 06:01:22.910 align:start position:0% different from each other one perhaps using<06:01:20.820> TCP<06:01:21.420> which<06:01:21.900> we<06:01:22.080> know<06:01:22.200> another<06:01:22.440> using 06:01:22.910 --> 06:01:22.920 align:start position:0% using TCP which we know another using 06:01:22.920 --> 06:01:26.150 align:start position:0% using TCP which we know another using ipx<06:01:23.458> SPX<06:01:24.120> which<06:01:24.780> you<06:01:25.200> don't<06:01:25.440> worry<06:01:25.620> about<06:01:25.798> but 06:01:26.150 --> 06:01:26.160 align:start position:0% ipx SPX which you don't worry about but 06:01:26.160 --> 06:01:28.430 align:start position:0% ipx SPX which you don't worry about but it's<06:01:26.280> another<06:01:26.580> sort<06:01:26.940> of<06:01:27.058> protocol<06:01:27.420> Suite<06:01:27.900> this 06:01:28.430 --> 06:01:28.440 align:start position:0% it's another sort of protocol Suite this 06:01:28.440 --> 06:01:30.048 align:start position:0% it's another sort of protocol Suite this layer<06:01:28.680> is<06:01:28.798> what<06:01:29.040> makes<06:01:29.218> Communications 06:01:30.048 --> 06:01:30.058 align:start position:0% layer is what makes Communications 06:01:30.058 --> 06:01:33.048 align:start position:0% layer is what makes Communications available<06:01:30.920> because<06:01:31.920> of<06:01:32.160> this<06:01:32.340> we<06:01:32.638> also<06:01:32.878> know 06:01:33.048 --> 06:01:33.058 align:start position:0% available because of this we also know 06:01:33.058 --> 06:01:36.230 align:start position:0% available because of this we also know that<06:01:33.360> a<06:01:33.840> Gateway<06:01:34.740> device<06:01:35.100> if<06:01:35.520> you<06:01:35.638> recall<06:01:36.000> from 06:01:36.230 --> 06:01:36.240 align:start position:0% that a Gateway device if you recall from 06:01:36.240 --> 06:01:38.330 align:start position:0% that a Gateway device if you recall from the<06:01:36.420> devices<06:01:36.718> we've<06:01:37.200> talked<06:01:37.500> about 06:01:38.330 --> 06:01:38.340 align:start position:0% the devices we've talked about 06:01:38.340 --> 06:01:40.850 align:start position:0% the devices we've talked about is<06:01:38.820> a<06:01:38.940> device<06:01:39.058> that's<06:01:39.420> going<06:01:39.600> to<06:01:39.780> operate<06:01:40.320> on 06:01:40.850 --> 06:01:40.860 align:start position:0% is a device that's going to operate on 06:01:40.860 --> 06:01:42.110 align:start position:0% is a device that's going to operate on this<06:01:41.218> layer 06:01:42.110 --> 06:01:42.120 align:start position:0% this layer 06:01:42.120 --> 06:01:43.970 align:start position:0% this layer because<06:01:42.600> it's<06:01:42.840> converting<06:01:43.260> between<06:01:43.558> two 06:01:43.970 --> 06:01:43.980 align:start position:0% because it's converting between two 06:01:43.980 --> 06:01:46.310 align:start position:0% because it's converting between two different<06:01:44.160> types<06:01:44.580> of<06:01:44.700> Networks 06:01:46.310 --> 06:01:46.320 align:start position:0% different types of Networks 06:01:46.320 --> 06:01:48.890 align:start position:0% different types of Networks this<06:01:46.740> is<06:01:46.920> the<06:01:47.160> biggest<06:01:47.340> difference<06:01:47.820> between<06:01:48.298> a 06:01:48.890 --> 06:01:48.900 align:start position:0% this is the biggest difference between a 06:01:48.900 --> 06:01:50.628 align:start position:0% this is the biggest difference between a gateway 06:01:50.628 --> 06:01:50.638 align:start position:0% gateway 06:01:50.638 --> 06:01:53.170 align:start position:0% gateway and<06:01:51.000> a<06:01:51.120> router<06:01:51.540> which<06:01:52.138> as<06:01:52.440> you<06:01:52.620> recall 06:01:53.170 --> 06:01:53.180 align:start position:0% and a router which as you recall 06:01:53.180 --> 06:01:57.770 align:start position:0% and a router which as you recall operates<06:01:54.180> on<06:01:54.600> layer<06:01:55.020> 3. 06:01:57.770 --> 06:01:57.780 align:start position:0% operates on layer 3. 06:01:57.780 --> 06:02:00.170 align:start position:0% operates on layer 3. a<06:01:58.320> transceiver<06:01:58.798> by<06:01:59.580> the<06:01:59.760> way<06:01:59.820> and<06:02:00.058> you 06:02:00.170 --> 06:02:00.180 align:start position:0% a transceiver by the way and you 06:02:00.180 --> 06:02:02.868 align:start position:0% a transceiver by the way and you remember<06:02:00.360> a<06:02:00.780> transceiver<06:02:01.260> is<06:02:01.558> that<06:02:01.878> device 06:02:02.868 --> 06:02:02.878 align:start position:0% remember a transceiver is that device 06:02:02.878 --> 06:02:04.970 align:start position:0% remember a transceiver is that device that<06:02:03.360> is<06:02:03.540> on<06:02:04.020> a 06:02:04.970 --> 06:02:04.980 align:start position:0% that is on a 06:02:04.980 --> 06:02:07.310 align:start position:0% that is on a Nick<06:02:05.580> it's<06:02:05.878> going<06:02:06.058> to<06:02:06.120> allow<06:02:06.420> you<06:02:06.540> to<06:02:06.780> talk<06:02:07.020> for 06:02:07.310 --> 06:02:07.320 align:start position:0% Nick it's going to allow you to talk for 06:02:07.320 --> 06:02:09.230 align:start position:0% Nick it's going to allow you to talk for instance<06:02:07.558> between<06:02:07.920> a<06:02:08.280> copper<06:02:08.638> and<06:02:08.760> fiber 06:02:09.230 --> 06:02:09.240 align:start position:0% instance between a copper and fiber 06:02:09.240 --> 06:02:12.350 align:start position:0% instance between a copper and fiber Network<06:02:09.500> also<06:02:10.500> might<06:02:10.860> work<06:02:11.218> on<06:02:12.000> this 06:02:12.350 --> 06:02:12.360 align:start position:0% Network also might work on this 06:02:12.360 --> 06:02:14.628 align:start position:0% Network also might work on this presentation<06:02:12.840> layer<06:02:13.378> depending<06:02:14.040> on<06:02:14.218> how<06:02:14.458> we 06:02:14.628 --> 06:02:14.638 align:start position:0% presentation layer depending on how we 06:02:14.638 --> 06:02:16.250 align:start position:0% presentation layer depending on how we Define<06:02:14.820> it<06:02:15.120> other<06:02:15.420> people<06:02:15.660> might<06:02:16.020> actually 06:02:16.250 --> 06:02:16.260 align:start position:0% Define it other people might actually 06:02:16.260 --> 06:02:18.948 align:start position:0% Define it other people might actually say<06:02:16.558> it<06:02:16.740> works<06:02:17.040> on<06:02:17.218> a<06:02:17.458> physical<06:02:17.760> layer<06:02:18.298> now<06:02:18.718> to 06:02:18.948 --> 06:02:18.958 align:start position:0% say it works on a physical layer now to 06:02:18.958 --> 06:02:20.930 align:start position:0% say it works on a physical layer now to put<06:02:19.080> this<06:02:19.260> layer<06:02:19.558> in<06:02:19.920> perspective<06:02:20.400> the 06:02:20.930 --> 06:02:20.940 align:start position:0% put this layer in perspective the 06:02:20.940 --> 06:02:22.548 align:start position:0% put this layer in perspective the presentation<06:02:21.360> layer<06:02:21.780> is<06:02:21.840> like<06:02:22.020> having<06:02:22.200> a 06:02:22.548 --> 06:02:22.558 align:start position:0% presentation layer is like having a 06:02:22.558 --> 06:02:25.128 align:start position:0% presentation layer is like having a double<06:02:22.680> decker<06:02:23.280> bus<06:02:23.580> with<06:02:24.180> a<06:02:24.360> tour<06:02:24.480> guide<06:02:24.780> on<06:02:25.020> a 06:02:25.128 --> 06:02:25.138 align:start position:0% double decker bus with a tour guide on a 06:02:25.138 --> 06:02:26.690 align:start position:0% double decker bus with a tour guide on a microphone<06:02:25.558> who's<06:02:25.740> translating<06:02:26.280> everything 06:02:26.690 --> 06:02:26.700 align:start position:0% microphone who's translating everything 06:02:26.700 --> 06:02:29.330 align:start position:0% microphone who's translating everything that<06:02:27.120> can<06:02:27.240> be<06:02:27.420> seen<06:02:27.660> and<06:02:27.840> heard<06:02:28.138> to<06:02:28.920> the 06:02:29.330 --> 06:02:29.340 align:start position:0% that can be seen and heard to the 06:02:29.340 --> 06:02:31.430 align:start position:0% that can be seen and heard to the passengers<06:02:30.058> the<06:02:30.540> tour<06:02:30.718> guide<06:02:30.958> is<06:02:31.138> also<06:02:31.320> going 06:02:31.430 --> 06:02:31.440 align:start position:0% passengers the tour guide is also going 06:02:31.440 --> 06:02:33.708 align:start position:0% passengers the tour guide is also going to<06:02:31.558> help<06:02:31.740> repack<06:02:32.340> the<06:02:32.700> tourists<06:02:33.120> luggage<06:02:33.540> for 06:02:33.708 --> 06:02:33.718 align:start position:0% to help repack the tourists luggage for 06:02:33.718 --> 06:02:37.190 align:start position:0% to help repack the tourists luggage for them<06:02:33.900> which<06:02:34.500> is<06:02:34.680> like<06:02:35.040> a<06:02:35.820> compression 06:02:37.190 --> 06:02:37.200 align:start position:0% them which is like a compression 06:02:37.200 --> 06:02:39.110 align:start position:0% them which is like a compression and<06:02:37.860> it's<06:02:38.040> also<06:02:38.340> going<06:02:38.458> to<06:02:38.520> add<06:02:38.638> another<06:02:38.760> level 06:02:39.110 --> 06:02:39.120 align:start position:0% and it's also going to add another level 06:02:39.120 --> 06:02:44.030 align:start position:0% and it's also going to add another level of<06:02:39.480> security<06:02:39.980> for<06:02:40.980> VIP<06:02:41.760> passengers 06:02:44.030 --> 06:02:44.040 align:start position:0% of security for VIP passengers 06:02:44.040 --> 06:02:46.670 align:start position:0% of security for VIP passengers who<06:02:44.760> might<06:02:45.000> come<06:02:45.240> on<06:02:45.480> board<06:02:45.718> this<06:02:46.260> is<06:02:46.440> just 06:02:46.670 --> 06:02:46.680 align:start position:0% who might come on board this is just 06:02:46.680 --> 06:02:48.170 align:start position:0% who might come on board this is just like 06:02:48.170 --> 06:02:48.180 align:start position:0% like 06:02:48.180 --> 06:02:50.750 align:start position:0% like encryption 06:02:50.750 --> 06:02:50.760 align:start position:0% encryption 06:02:50.760 --> 06:02:53.448 align:start position:0% encryption here<06:02:51.298> the<06:02:51.660> formatting<06:02:52.320> is<06:02:52.860> simply<06:02:53.160> making 06:02:53.448 --> 06:02:53.458 align:start position:0% here the formatting is simply making 06:02:53.458 --> 06:02:56.030 align:start position:0% here the formatting is simply making sure<06:02:53.878> that<06:02:54.180> the<06:02:54.420> passengers<06:02:54.840> are<06:02:55.020> briefed<06:02:55.558> and 06:02:56.030 --> 06:02:56.040 align:start position:0% sure that the passengers are briefed and 06:02:56.040 --> 06:02:58.070 align:start position:0% sure that the passengers are briefed and ready<06:02:56.280> for<06:02:56.638> their<06:02:56.820> tour<06:02:57.058> and<06:02:57.600> making<06:02:57.780> sure 06:02:58.070 --> 06:02:58.080 align:start position:0% ready for their tour and making sure 06:02:58.080 --> 06:03:00.948 align:start position:0% ready for their tour and making sure that<06:02:58.378> they<06:02:58.798> or<06:02:58.980> the<06:02:59.280> data<06:02:59.700> is<06:03:00.120> ready<06:03:00.360> for<06:03:00.718> the 06:03:00.948 --> 06:03:00.958 align:start position:0% that they or the data is ready for the 06:03:00.958 --> 06:03:02.810 align:start position:0% that they or the data is ready for the application<06:03:01.500> so<06:03:02.100> again<06:03:02.280> we're<06:03:02.580> really 06:03:02.810 --> 06:03:02.820 align:start position:0% application so again we're really 06:03:02.820 --> 06:03:05.990 align:start position:0% application so again we're really packaging<06:03:03.480> this<06:03:03.718> up<06:03:03.900> for<06:03:04.260> presentation<06:03:05.000> to 06:03:05.990 --> 06:03:06.000 align:start position:0% packaging this up for presentation to 06:03:06.000 --> 06:03:08.030 align:start position:0% packaging this up for presentation to the<06:03:06.360> application<06:03:06.900> layer<06:03:07.378> and<06:03:07.860> the 06:03:08.030 --> 06:03:08.040 align:start position:0% the application layer and the 06:03:08.040 --> 06:03:10.730 align:start position:0% the application layer and the terminology<06:03:08.520> for<06:03:09.000> data<06:03:09.420> at<06:03:09.718> this<06:03:10.020> point<06:03:10.378> is 06:03:10.730 --> 06:03:10.740 align:start position:0% terminology for data at this point is 06:03:10.740 --> 06:03:12.770 align:start position:0% terminology for data at this point is going<06:03:10.860> to<06:03:10.980> be<06:03:11.100> actually<06:03:11.280> called<06:03:11.700> Data<06:03:12.420> so<06:03:12.600> this 06:03:12.770 --> 06:03:12.780 align:start position:0% going to be actually called Data so this 06:03:12.780 --> 06:03:14.448 align:start position:0% going to be actually called Data so this is<06:03:12.900> where<06:03:13.138> we're<06:03:13.378> moving<06:03:13.740> up<06:03:13.920> in<06:03:14.100> the<06:03:14.280> world 06:03:14.448 --> 06:03:14.458 align:start position:0% is where we're moving up in the world 06:03:14.458 --> 06:03:17.208 align:start position:0% is where we're moving up in the world we're<06:03:15.000> no<06:03:15.240> longer<06:03:15.420> talking<06:03:15.718> about<06:03:16.218> segments 06:03:17.208 --> 06:03:17.218 align:start position:0% we're no longer talking about segments 06:03:17.218 --> 06:03:19.610 align:start position:0% we're no longer talking about segments or<06:03:17.520> datagrams<06:03:18.240> or<06:03:18.480> frames<06:03:18.840> we're<06:03:19.200> here<06:03:19.440> now 06:03:19.610 --> 06:03:19.620 align:start position:0% or datagrams or frames we're here now 06:03:19.620 --> 06:03:21.770 align:start position:0% or datagrams or frames we're here now talking<06:03:19.980> about<06:03:20.218> data<06:03:20.760> it's<06:03:20.940> packaged<06:03:21.540> in<06:03:21.600> a 06:03:21.770 --> 06:03:21.780 align:start position:0% talking about data it's packaged in a 06:03:21.780 --> 06:03:23.810 align:start position:0% talking about data it's packaged in a way<06:03:21.900> that<06:03:22.378> an<06:03:22.558> application<06:03:23.040> can<06:03:23.400> read<06:03:23.638> it 06:03:23.810 --> 06:03:23.820 align:start position:0% way that an application can read it 06:03:23.820 --> 06:03:26.510 align:start position:0% way that an application can read it finally<06:03:24.480> at<06:03:24.780> the<06:03:24.900> topmost<06:03:25.260> layer<06:03:25.740> we<06:03:25.980> have<06:03:26.160> the 06:03:26.510 --> 06:03:26.520 align:start position:0% finally at the topmost layer we have the 06:03:26.520 --> 06:03:28.368 align:start position:0% finally at the topmost layer we have the application<06:03:27.058> layer<06:03:27.480> this<06:03:27.900> is<06:03:27.958> the<06:03:28.138> layer 06:03:28.368 --> 06:03:28.378 align:start position:0% application layer this is the layer 06:03:28.378 --> 06:03:31.788 align:start position:0% application layer this is the layer that's<06:03:28.558> closest<06:03:28.980> to 06:03:31.788 --> 06:03:31.798 align:start position:0% 06:03:31.798 --> 06:03:34.368 align:start position:0% the<06:03:32.580> user<06:03:32.878> and<06:03:33.120> it's<06:03:33.240> the<06:03:33.480> only<06:03:33.660> one<06:03:33.958> that<06:03:34.260> the 06:03:34.368 --> 06:03:34.378 align:start position:0% the user and it's the only one that the 06:03:34.378 --> 06:03:35.810 align:start position:0% the user and it's the only one that the typical<06:03:34.680> end<06:03:34.980> user<06:03:35.340> is<06:03:35.458> going<06:03:35.638> to<06:03:35.700> be 06:03:35.810 --> 06:03:35.820 align:start position:0% typical end user is going to be 06:03:35.820 --> 06:03:37.610 align:start position:0% typical end user is going to be interacting<06:03:36.298> with<06:03:36.480> now<06:03:37.020> even<06:03:37.200> though<06:03:37.378> it's 06:03:37.610 --> 06:03:37.620 align:start position:0% interacting with now even though it's 06:03:37.620 --> 06:03:40.128 align:start position:0% interacting with now even though it's called<06:03:37.860> the<06:03:38.280> application<06:03:39.000> layer<06:03:39.540> this 06:03:40.128 --> 06:03:40.138 align:start position:0% called the application layer this 06:03:40.138 --> 06:03:42.470 align:start position:0% called the application layer this doesn't<06:03:40.320> mean<06:03:40.620> that<06:03:40.980> the<06:03:41.280> application<06:03:41.940> itself 06:03:42.470 --> 06:03:42.480 align:start position:0% doesn't mean that the application itself 06:03:42.480 --> 06:03:45.110 align:start position:0% doesn't mean that the application itself is<06:03:42.780> on<06:03:43.020> this<06:03:43.200> layer<06:03:43.700> but<06:03:44.700> that<06:03:44.820> the 06:03:45.110 --> 06:03:45.120 align:start position:0% is on this layer but that the 06:03:45.120 --> 06:03:48.650 align:start position:0% is on this layer but that the application<06:03:45.718> layer<06:03:46.440> provides<06:03:47.100> utilities<06:03:47.760> and 06:03:48.650 --> 06:03:48.660 align:start position:0% application layer provides utilities and 06:03:48.660 --> 06:03:51.170 align:start position:0% application layer provides utilities and services<06:03:49.020> that<06:03:49.620> an<06:03:49.798> application<06:03:50.280> could<06:03:50.820> use 06:03:51.170 --> 06:03:51.180 align:start position:0% services that an application could use 06:03:51.180 --> 06:03:53.510 align:start position:0% services that an application could use for<06:03:51.718> accessing<06:03:52.260> network<06:03:52.500> resources<06:03:53.160> like 06:03:53.510 --> 06:03:53.520 align:start position:0% for accessing network resources like 06:03:53.520 --> 06:03:55.030 align:start position:0% for accessing network resources like some<06:03:53.700> of<06:03:53.820> these<06:03:54.000> that<06:03:54.120> we've<06:03:54.298> talked<06:03:54.660> about 06:03:55.030 --> 06:03:55.040 align:start position:0% some of these that we've talked about 06:03:55.040 --> 06:03:58.190 align:start position:0% some of these that we've talked about SMTP<06:03:56.040> which<06:03:56.580> allows<06:03:56.878> you<06:03:56.940> to<06:03:57.180> get<06:03:57.298> email<06:03:57.540> DNS 06:03:58.190 --> 06:03:58.200 align:start position:0% SMTP which allows you to get email DNS 06:03:58.200 --> 06:03:59.810 align:start position:0% SMTP which allows you to get email DNS which<06:03:58.378> is<06:03:58.500> going<06:03:58.680> to<06:03:58.740> translate<06:03:59.040> between<06:03:59.580> an 06:03:59.810 --> 06:03:59.820 align:start position:0% which is going to translate between an 06:03:59.820 --> 06:04:03.590 align:start position:0% which is going to translate between an IP<06:04:00.120> address<06:04:00.298> and<06:04:01.260> a<06:04:01.860> fully<06:04:02.638> qualified<06:04:03.000> domain 06:04:03.590 --> 06:04:03.600 align:start position:0% IP address and a fully qualified domain 06:04:03.600 --> 06:04:05.990 align:start position:0% IP address and a fully qualified domain name<06:04:03.798> FTP<06:04:04.798> which<06:04:05.100> is<06:04:05.218> going<06:04:05.400> to<06:04:05.458> allow<06:04:05.760> for 06:04:05.990 --> 06:04:06.000 align:start position:0% name FTP which is going to allow for 06:04:06.000 --> 06:04:08.570 align:start position:0% name FTP which is going to allow for file<06:04:06.298> transferring<06:04:06.900> ntp<06:04:07.558> Network<06:04:08.340> time 06:04:08.570 --> 06:04:08.580 align:start position:0% file transferring ntp Network time 06:04:08.580 --> 06:04:09.948 align:start position:0% file transferring ntp Network time protocol<06:04:09.058> which<06:04:09.298> is<06:04:09.360> going<06:04:09.480> to<06:04:09.540> keep<06:04:09.660> time<06:04:09.780> up 06:04:09.948 --> 06:04:09.958 align:start position:0% protocol which is going to keep time up 06:04:09.958 --> 06:04:11.810 align:start position:0% protocol which is going to keep time up to<06:04:10.080> date<06:04:10.200> and<06:04:10.378> HTTP<06:04:10.920> which<06:04:11.100> allows<06:04:11.400> us<06:04:11.520> to 06:04:11.810 --> 06:04:11.820 align:start position:0% to date and HTTP which allows us to 06:04:11.820 --> 06:04:13.910 align:start position:0% to date and HTTP which allows us to browse<06:04:12.298> so<06:04:12.958> for<06:04:13.138> example<06:04:13.378> let's<06:04:13.558> say<06:04:13.680> you<06:04:13.860> have 06:04:13.910 --> 06:04:13.920 align:start position:0% browse so for example let's say you have 06:04:13.920 --> 06:04:16.128 align:start position:0% browse so for example let's say you have a<06:04:14.100> file<06:04:14.280> that<06:04:14.580> you'd<06:04:14.878> like<06:04:15.240> to<06:04:15.420> transfer<06:04:15.840> to<06:04:16.020> a 06:04:16.128 --> 06:04:16.138 align:start position:0% a file that you'd like to transfer to a 06:04:16.138 --> 06:04:18.230 align:start position:0% a file that you'd like to transfer to a remote<06:04:16.260> computer<06:04:16.620> right<06:04:17.160> what<06:04:17.820> method<06:04:18.058> you're 06:04:18.230 --> 06:04:18.240 align:start position:0% remote computer right what method you're 06:04:18.240 --> 06:04:21.170 align:start position:0% remote computer right what method you're going<06:04:18.420> to<06:04:18.480> use<06:04:18.620> FTP<06:04:19.620> now<06:04:20.520> the<06:04:20.760> application 06:04:21.170 --> 06:04:21.180 align:start position:0% going to use FTP now the application 06:04:21.180 --> 06:04:24.530 align:start position:0% going to use FTP now the application layer<06:04:21.600> provides<06:04:22.138> the<06:04:22.378> FTP<06:04:22.860> services<06:04:23.280> to<06:04:24.240> the 06:04:24.530 --> 06:04:24.540 align:start position:0% layer provides the FTP services to the 06:04:24.540 --> 06:04:26.868 align:start position:0% layer provides the FTP services to the application<06:04:25.320> you<06:04:25.620> use<06:04:25.798> which<06:04:26.218> is<06:04:26.340> some<06:04:26.638> sort 06:04:26.868 --> 06:04:26.878 align:start position:0% application you use which is some sort 06:04:26.878 --> 06:04:30.890 align:start position:0% application you use which is some sort of<06:04:27.020> FTP<06:04:28.020> client<06:04:28.980> the<06:04:29.400> FTP<06:04:29.820> client<06:04:30.180> itself<06:04:30.540> does 06:04:30.890 --> 06:04:30.900 align:start position:0% of FTP client the FTP client itself does 06:04:30.900 --> 06:04:32.930 align:start position:0% of FTP client the FTP client itself does not<06:04:31.080> exist<06:04:31.378> on<06:04:31.558> the<06:04:31.680> app<06:04:31.860> application<06:04:32.458> layer 06:04:32.930 --> 06:04:32.940 align:start position:0% not exist on the app application layer 06:04:32.940 --> 06:04:36.650 align:start position:0% not exist on the app application layer simply<06:04:33.780> the<06:04:34.500> protocol<06:04:34.920> does<06:04:35.458> this<06:04:36.120> layer<06:04:36.420> is 06:04:36.650 --> 06:04:36.660 align:start position:0% simply the protocol does this layer is 06:04:36.660 --> 06:04:38.448 align:start position:0% simply the protocol does this layer is the<06:04:37.138> one<06:04:37.320> you've<06:04:37.620> probably<06:04:37.798> dealt<06:04:38.160> with<06:04:38.218> the 06:04:38.448 --> 06:04:38.458 align:start position:0% the one you've probably dealt with the 06:04:38.458 --> 06:04:40.548 align:start position:0% the one you've probably dealt with the most<06:04:38.580> and<06:04:38.878> you're<06:04:39.058> probably<06:04:39.378> likely<06:04:40.378> already 06:04:40.548 --> 06:04:40.558 align:start position:0% most and you're probably likely already 06:04:40.558 --> 06:04:42.350 align:start position:0% most and you're probably likely already familiar<06:04:40.980> with<06:04:41.160> without<06:04:41.340> even<06:04:41.700> realizing<06:04:42.240> it 06:04:42.350 --> 06:04:42.360 align:start position:0% familiar with without even realizing it 06:04:42.360 --> 06:04:44.510 align:start position:0% familiar with without even realizing it for<06:04:43.020> example<06:04:43.260> you<06:04:43.500> utilize<06:04:43.920> this<06:04:44.100> layer<06:04:44.400> every 06:04:44.510 --> 06:04:44.520 align:start position:0% for example you utilize this layer every 06:04:44.520 --> 06:04:47.270 align:start position:0% for example you utilize this layer every time<06:04:44.760> you<06:04:44.940> check<06:04:45.240> your<06:04:45.480> email<06:04:45.660> browse<06:04:46.798> Etc<06:04:46.980> and 06:04:47.270 --> 06:04:47.280 align:start position:0% time you check your email browse Etc and 06:04:47.280 --> 06:04:50.330 align:start position:0% time you check your email browse Etc and so<06:04:47.520> on<06:04:47.700> now<06:04:48.540> some<06:04:49.378> of<06:04:49.500> these<06:04:49.680> might<06:04:49.920> not<06:04:50.040> fit 06:04:50.330 --> 06:04:50.340 align:start position:0% so on now some of these might not fit 06:04:50.340 --> 06:04:52.250 align:start position:0% so on now some of these might not fit perfectly<06:04:50.878> into<06:04:51.180> the<06:04:51.420> application<06:04:51.780> layer<06:04:52.138> and 06:04:52.250 --> 06:04:52.260 align:start position:0% perfectly into the application layer and 06:04:52.260 --> 06:04:53.750 align:start position:0% perfectly into the application layer and that's<06:04:52.440> because<06:04:52.680> again<06:04:52.980> this<06:04:53.340> is<06:04:53.520> a 06:04:53.750 --> 06:04:53.760 align:start position:0% that's because again this is a 06:04:53.760 --> 06:04:55.610 align:start position:0% that's because again this is a theoretical<06:04:54.298> model<06:04:54.600> when<06:04:54.958> we<06:04:55.138> talk<06:04:55.260> about<06:04:55.378> the 06:04:55.610 --> 06:04:55.620 align:start position:0% theoretical model when we talk about the 06:04:55.620 --> 06:04:59.208 align:start position:0% theoretical model when we talk about the TCP<06:04:56.100> model<06:04:56.760> next<06:04:57.120> it<06:04:57.718> will<06:04:58.080> see<06:04:58.320> this<06:04:58.558> working 06:04:59.208 --> 06:04:59.218 align:start position:0% TCP model next it will see this working 06:04:59.218 --> 06:05:01.310 align:start position:0% TCP model next it will see this working in<06:04:59.638> a<06:04:59.760> lot<06:04:59.878> more<06:05:00.000> of<06:05:00.120> a<06:05:00.298> practical<06:05:00.600> way<06:05:00.840> now 06:05:01.310 --> 06:05:01.320 align:start position:0% in a lot more of a practical way now 06:05:01.320 --> 06:05:02.868 align:start position:0% in a lot more of a practical way now because<06:05:01.680> we<06:05:02.040> all<06:05:02.160> know<06:05:02.340> we<06:05:02.580> have<06:05:02.700> many 06:05:02.868 --> 06:05:02.878 align:start position:0% because we all know we have many 06:05:02.878 --> 06:05:04.430 align:start position:0% because we all know we have many different<06:05:03.058> applications<06:05:03.660> on<06:05:04.020> every<06:05:04.200> one<06:05:04.320> of 06:05:04.430 --> 06:05:04.440 align:start position:0% different applications on every one of 06:05:04.440 --> 06:05:06.530 align:start position:0% different applications on every one of our<06:05:04.558> computers<06:05:05.040> one<06:05:05.760> of<06:05:05.878> the<06:05:06.000> purpose<06:05:06.240> of<06:05:06.420> the 06:05:06.530 --> 06:05:06.540 align:start position:0% our computers one of the purpose of the 06:05:06.540 --> 06:05:08.448 align:start position:0% our computers one of the purpose of the application<06:05:06.900> layer<06:05:07.260> is<06:05:07.440> to<06:05:07.680> regulate<06:05:08.218> the 06:05:08.448 --> 06:05:08.458 align:start position:0% application layer is to regulate the 06:05:08.458 --> 06:05:10.070 align:start position:0% application layer is to regulate the communications<06:05:09.000> between<06:05:09.660> these 06:05:10.070 --> 06:05:10.080 align:start position:0% communications between these 06:05:10.080 --> 06:05:12.530 align:start position:0% communications between these applications<06:05:10.558> and<06:05:11.340> manage<06:05:11.760> when<06:05:12.298> they 06:05:12.530 --> 06:05:12.540 align:start position:0% applications and manage when they 06:05:12.540 --> 06:05:14.990 align:start position:0% applications and manage when they request<06:05:12.840> services<06:05:13.138> and<06:05:13.558> resources<06:05:14.160> so<06:05:14.820> while 06:05:14.990 --> 06:05:15.000 align:start position:0% request services and resources so while 06:05:15.000 --> 06:05:17.090 align:start position:0% request services and resources so while it<06:05:15.180> might<06:05:15.298> seem<06:05:15.600> easy<06:05:15.780> to<06:05:16.080> lump<06:05:16.680> all 06:05:17.090 --> 06:05:17.100 align:start position:0% it might seem easy to lump all 06:05:17.100 --> 06:05:19.010 align:start position:0% it might seem easy to lump all applications<06:05:17.638> together<06:05:18.058> when<06:05:18.540> talking<06:05:18.780> about 06:05:19.010 --> 06:05:19.020 align:start position:0% applications together when talking about 06:05:19.020 --> 06:05:21.288 align:start position:0% applications together when talking about this<06:05:19.260> layer<06:05:19.680> the<06:05:20.280> only<06:05:20.340> applications<06:05:20.878> that 06:05:21.288 --> 06:05:21.298 align:start position:0% this layer the only applications that 06:05:21.298 --> 06:05:22.730 align:start position:0% this layer the only applications that this<06:05:21.540> layer<06:05:21.840> is<06:05:21.958> actually<06:05:22.200> going<06:05:22.378> to<06:05:22.500> manage 06:05:22.730 --> 06:05:22.740 align:start position:0% this layer is actually going to manage 06:05:22.740 --> 06:05:25.730 align:start position:0% this layer is actually going to manage are<06:05:22.920> those<06:05:23.160> that<06:05:23.458> have<06:05:23.700> a<06:05:24.740> Communications 06:05:25.730 --> 06:05:25.740 align:start position:0% are those that have a Communications 06:05:25.740 --> 06:05:27.850 align:start position:0% are those that have a Communications component 06:05:27.850 --> 06:05:27.860 align:start position:0% component 06:05:27.860 --> 06:05:31.970 align:start position:0% component so<06:05:29.180> Solitaire<06:05:30.180> would<06:05:30.718> not<06:05:30.900> qualify<06:05:31.558> for<06:05:31.860> this 06:05:31.970 --> 06:05:31.980 align:start position:0% so Solitaire would not qualify for this 06:05:31.980 --> 06:05:34.610 align:start position:0% so Solitaire would not qualify for this right<06:05:32.218> but<06:05:32.638> Internet<06:05:33.058> Explorer<06:05:33.958> which<06:05:34.378> has 06:05:34.610 --> 06:05:34.620 align:start position:0% right but Internet Explorer which has 06:05:34.620 --> 06:05:38.690 align:start position:0% right but Internet Explorer which has all<06:05:34.798> those<06:05:35.040> browsing<06:05:35.638> and<06:05:35.940> protocols<06:05:36.480> FTP<06:05:37.320> DNS 06:05:38.690 --> 06:05:38.700 align:start position:0% all those browsing and protocols FTP DNS 06:05:38.700 --> 06:05:41.868 align:start position:0% all those browsing and protocols FTP DNS Etc<06:05:38.878> is<06:05:39.780> going<06:05:40.020> to<06:05:40.378> uh<06:05:40.620> deal<06:05:40.798> with<06:05:41.040> this<06:05:41.218> so 06:05:41.868 --> 06:05:41.878 align:start position:0% Etc is going to uh deal with this so 06:05:41.878 --> 06:05:43.850 align:start position:0% Etc is going to uh deal with this so this<06:05:42.058> layer<06:05:42.360> is<06:05:42.480> also<06:05:42.840> responsible<06:05:43.378> for 06:05:43.850 --> 06:05:43.860 align:start position:0% this layer is also responsible for 06:05:43.860 --> 06:05:46.910 align:start position:0% this layer is also responsible for network<06:05:44.160> access<06:05:44.700> a<06:05:45.298> certain<06:05:45.420> level<06:05:45.718> of<06:05:46.080> error 06:05:46.910 --> 06:05:46.920 align:start position:0% network access a certain level of error 06:05:46.920 --> 06:05:49.310 align:start position:0% network access a certain level of error recovery<06:05:47.520> and<06:05:48.360> it's<06:05:48.480> also<06:05:48.780> capable<06:05:49.020> of<06:05:49.080> some 06:05:49.310 --> 06:05:49.320 align:start position:0% recovery and it's also capable of some 06:05:49.320 --> 06:05:50.930 align:start position:0% recovery and it's also capable of some data<06:05:49.620> flow<06:05:49.798> measures<06:05:50.218> there's<06:05:50.458> a<06:05:50.760> lot<06:05:50.820> of 06:05:50.930 --> 06:05:50.940 align:start position:0% data flow measures there's a lot of 06:05:50.940 --> 06:05:53.570 align:start position:0% data flow measures there's a lot of redundancy<06:05:51.660> here<06:05:51.958> as<06:05:52.620> this<06:05:52.860> is<06:05:52.980> the<06:05:53.280> seventh 06:05:53.570 --> 06:05:53.580 align:start position:0% redundancy here as this is the seventh 06:05:53.580 --> 06:05:55.310 align:start position:0% redundancy here as this is the seventh and<06:05:53.760> the<06:05:53.940> final<06:05:54.120> layer<06:05:54.660> this<06:05:54.840> is<06:05:54.958> where<06:05:55.138> the 06:05:55.310 --> 06:05:55.320 align:start position:0% and the final layer this is where the 06:05:55.320 --> 06:06:00.850 align:start position:0% and the final layer this is where the information<06:05:55.500> or<06:05:56.040> process<06:05:56.458> either<06:05:57.240> starts 06:06:00.850 --> 06:06:00.860 align:start position:0% 06:06:00.860 --> 06:06:05.930 align:start position:0% or<06:06:01.860> finishes 06:06:05.930 --> 06:06:05.940 align:start position:0% 06:06:05.940 --> 06:06:07.788 align:start position:0% so<06:06:06.360> an<06:06:06.540> application<06:06:07.020> is<06:06:07.320> going<06:06:07.440> to<06:06:07.620> create 06:06:07.788 --> 06:06:07.798 align:start position:0% so an application is going to create 06:06:07.798 --> 06:06:09.530 align:start position:0% so an application is going to create what<06:06:08.040> it<06:06:08.218> needs<06:06:08.400> to<06:06:08.458> be<06:06:08.520> sent<06:06:08.760> here<06:06:09.058> and<06:06:09.420> then 06:06:09.530 --> 06:06:09.540 align:start position:0% what it needs to be sent here and then 06:06:09.540 --> 06:06:12.530 align:start position:0% what it needs to be sent here and then unwrap<06:06:10.080> the<06:06:10.260> data<06:06:10.558> once<06:06:11.100> it's<06:06:11.280> sent<06:06:11.520> uh<06:06:12.240> from 06:06:12.530 --> 06:06:12.540 align:start position:0% unwrap the data once it's sent uh from 06:06:12.540 --> 06:06:14.750 align:start position:0% unwrap the data once it's sent uh from one<06:06:12.718> computer<06:06:12.900> the<06:06:13.320> next<06:06:13.500> so<06:06:14.100> to<06:06:14.280> finish<06:06:14.458> off 06:06:14.750 --> 06:06:14.760 align:start position:0% one computer the next so to finish off 06:06:14.760 --> 06:06:17.208 align:start position:0% one computer the next so to finish off our<06:06:15.120> analogy<06:06:15.600> of<06:06:15.840> the<06:06:16.020> bus 06:06:17.208 --> 06:06:17.218 align:start position:0% our analogy of the bus 06:06:17.218 --> 06:06:19.070 align:start position:0% our analogy of the bus um this<06:06:17.520> is<06:06:17.638> sort<06:06:17.820> of<06:06:17.878> like<06:06:18.058> the<06:06:18.360> bus<06:06:18.480> station 06:06:19.070 --> 06:06:19.080 align:start position:0% um this is sort of like the bus station 06:06:19.080 --> 06:06:20.930 align:start position:0% um this is sort of like the bus station here's<06:06:19.860> where<06:06:19.980> all<06:06:20.100> the<06:06:20.280> people<06:06:20.340> wait<06:06:20.580> in<06:06:20.760> line 06:06:20.930 --> 06:06:20.940 align:start position:0% here's where all the people wait in line 06:06:20.940 --> 06:06:22.970 align:start position:0% here's where all the people wait in line to<06:06:21.120> get<06:06:21.240> tickets<06:06:21.420> to<06:06:21.718> use<06:06:21.900> the<06:06:22.080> bus<06:06:22.260> they're 06:06:22.970 --> 06:06:22.980 align:start position:0% to get tickets to use the bus they're 06:06:22.980 --> 06:06:24.650 align:start position:0% to get tickets to use the bus they're going<06:06:23.160> to<06:06:23.520> dictate<06:06:24.000> the<06:06:24.120> bus<06:06:24.298> station<06:06:24.480> is 06:06:24.650 --> 06:06:24.660 align:start position:0% going to dictate the bus station is 06:06:24.660 --> 06:06:26.570 align:start position:0% going to dictate the bus station is going<06:06:24.840> to<06:06:24.958> dictate<06:06:25.260> who<06:06:25.740> has<06:06:25.920> access<06:06:26.160> to<06:06:26.458> the 06:06:26.570 --> 06:06:26.580 align:start position:0% going to dictate who has access to the 06:06:26.580 --> 06:06:28.310 align:start position:0% going to dictate who has access to the resources<06:06:27.058> the<06:06:27.360> resources<06:06:27.780> being<06:06:28.020> these 06:06:28.310 --> 06:06:28.320 align:start position:0% resources the resources being these 06:06:28.320 --> 06:06:30.470 align:start position:0% resources the resources being these buses<06:06:28.680> and<06:06:29.160> it's<06:06:29.280> going<06:06:29.520> to<06:06:29.700> receive<06:06:30.120> all<06:06:30.298> the 06:06:30.470 --> 06:06:30.480 align:start position:0% buses and it's going to receive all the 06:06:30.480 --> 06:06:32.990 align:start position:0% buses and it's going to receive all the incoming<06:06:30.840> drop-offs<06:06:31.440> and<06:06:31.680> process<06:06:31.980> them<06:06:32.340> as 06:06:32.990 --> 06:06:33.000 align:start position:0% incoming drop-offs and process them as 06:06:33.000 --> 06:06:34.910 align:start position:0% incoming drop-offs and process them as well<06:06:33.240> as<06:06:33.420> control<06:06:33.718> the<06:06:34.020> flow<06:06:34.260> of<06:06:34.378> people<06:06:34.620> in 06:06:34.910 --> 06:06:34.920 align:start position:0% well as control the flow of people in 06:06:34.920 --> 06:06:36.590 align:start position:0% well as control the flow of people in and<06:06:35.100> out<06:06:35.218> of<06:06:35.340> the<06:06:35.458> station<06:06:35.700> and<06:06:36.240> it's<06:06:36.360> going<06:06:36.540> to 06:06:36.590 --> 06:06:36.600 align:start position:0% and out of the station and it's going to 06:06:36.600 --> 06:06:38.208 align:start position:0% and out of the station and it's going to notify<06:06:36.958> people<06:06:37.200> if<06:06:37.500> there<06:06:37.620> are<06:06:37.798> problems<06:06:38.040> on 06:06:38.208 --> 06:06:38.218 align:start position:0% notify people if there are problems on 06:06:38.218 --> 06:06:40.910 align:start position:0% notify people if there are problems on the<06:06:38.340> highways<06:06:38.820> and<06:06:39.000> so<06:06:39.180> on<06:06:39.360> just<06:06:40.080> as<06:06:40.320> users<06:06:40.740> are 06:06:40.910 --> 06:06:40.920 align:start position:0% the highways and so on just as users are 06:06:40.920 --> 06:06:43.010 align:start position:0% the highways and so on just as users are typically<06:06:41.340> mostly<06:06:41.878> going<06:06:42.000> to<06:06:42.240> interact<06:06:42.660> with 06:06:43.010 --> 06:06:43.020 align:start position:0% typically mostly going to interact with 06:06:43.020 --> 06:06:45.230 align:start position:0% typically mostly going to interact with the<06:06:43.200> application<06:06:43.620> layer<06:06:44.100> the<06:06:44.520> bus<06:06:44.700> riders<06:06:45.058> are 06:06:45.230 --> 06:06:45.240 align:start position:0% the application layer the bus riders are 06:06:45.240 --> 06:06:47.208 align:start position:0% the application layer the bus riders are really<06:06:45.420> only<06:06:45.600> going<06:06:45.840> to<06:06:45.958> interact<06:06:46.320> at<06:06:46.558> the<06:06:46.860> bus 06:06:47.208 --> 06:06:47.218 align:start position:0% really only going to interact at the bus 06:06:47.218 --> 06:06:48.948 align:start position:0% really only going to interact at the bus station<06:06:47.400> layer<06:06:47.940> right<06:06:48.360> they're<06:06:48.600> not<06:06:48.780> going<06:06:48.900> to 06:06:48.948 --> 06:06:48.958 align:start position:0% station layer right they're not going to 06:06:48.958 --> 06:06:50.270 align:start position:0% station layer right they're not going to be<06:06:49.020> interacting<06:06:49.440> with<06:06:49.558> mechanics<06:06:50.100> and 06:06:50.270 --> 06:06:50.280 align:start position:0% be interacting with mechanics and 06:06:50.280 --> 06:06:51.890 align:start position:0% be interacting with mechanics and building<06:06:50.458> the<06:06:50.700> bus<06:06:50.820> or<06:06:51.240> maintaining<06:06:51.660> the<06:06:51.780> bus 06:06:51.890 --> 06:06:51.900 align:start position:0% building the bus or maintaining the bus 06:06:51.900 --> 06:06:54.708 align:start position:0% building the bus or maintaining the bus or<06:06:52.138> dispatching<06:06:52.740> individuals<06:06:53.340> or<06:06:54.180> any<06:06:54.600> of 06:06:54.708 --> 06:06:54.718 align:start position:0% or dispatching individuals or any of 06:06:54.718 --> 06:06:56.270 align:start position:0% or dispatching individuals or any of that<06:06:54.900> stuff<06:06:55.080> in<06:06:55.378> most<06:06:55.558> cases<06:06:55.920> they're<06:06:56.100> not 06:06:56.270 --> 06:06:56.280 align:start position:0% that stuff in most cases they're not 06:06:56.280 --> 06:06:58.070 align:start position:0% that stuff in most cases they're not even<06:06:56.400> going<06:06:56.638> to<06:06:56.760> be<06:06:57.000> interacting<06:06:57.660> with<06:06:57.900> the 06:06:58.070 --> 06:06:58.080 align:start position:0% even going to be interacting with the 06:06:58.080 --> 06:07:00.170 align:start position:0% even going to be interacting with the individual<06:06:58.440> driving<06:06:58.920> the<06:06:59.280> bus<06:06:59.400> so<06:06:59.940> this<06:07:00.058> is 06:07:00.170 --> 06:07:00.180 align:start position:0% individual driving the bus so this is 06:07:00.180 --> 06:07:02.990 align:start position:0% individual driving the bus so this is really<06:07:00.420> where<06:07:00.840> users<06:07:01.500> are<06:07:02.218> going<06:07:02.400> to<06:07:02.638> be<06:07:02.760> doing 06:07:02.990 --> 06:07:03.000 align:start position:0% really where users are going to be doing 06:07:03.000 --> 06:07:05.030 align:start position:0% really where users are going to be doing most<06:07:03.420> of<06:07:03.600> their<06:07:03.780> interacting<06:07:04.378> now<06:07:04.798> after 06:07:05.030 --> 06:07:05.040 align:start position:0% most of their interacting now after 06:07:05.040 --> 06:07:07.368 align:start position:0% most of their interacting now after going<06:07:05.340> through<06:07:05.580> each<06:07:05.760> of<06:07:05.878> of<06:07:06.298> these<06:07:06.600> layers<06:07:06.958> we 06:07:07.368 --> 06:07:07.378 align:start position:0% going through each of of these layers we 06:07:07.378 --> 06:07:09.048 align:start position:0% going through each of of these layers we can<06:07:07.500> now<06:07:07.620> begin<06:07:07.798> to<06:07:08.040> have<06:07:08.218> an<06:07:08.458> understanding 06:07:09.048 --> 06:07:09.058 align:start position:0% can now begin to have an understanding 06:07:09.058 --> 06:07:10.970 align:start position:0% can now begin to have an understanding on<06:07:09.298> how<06:07:09.480> they're<06:07:09.660> grouped<06:07:10.020> together 06:07:10.970 --> 06:07:10.980 align:start position:0% on how they're grouped together 06:07:10.980 --> 06:07:15.110 align:start position:0% on how they're grouped together for<06:07:11.458> instance<06:07:11.700> layers<06:07:12.660> 5<06:07:13.260> 6<06:07:13.680> and<06:07:13.920> 7<06:07:14.160> are<06:07:14.940> what 06:07:15.110 --> 06:07:15.120 align:start position:0% for instance layers 5 6 and 7 are what 06:07:15.120 --> 06:07:18.110 align:start position:0% for instance layers 5 6 and 7 are what we<06:07:15.298> call<06:07:15.480> application<06:07:16.378> support<06:07:16.920> block<06:07:17.400> when 06:07:18.110 --> 06:07:18.120 align:start position:0% we call application support block when 06:07:18.120 --> 06:07:19.250 align:start position:0% we call application support block when we<06:07:18.240> look<06:07:18.360> at<06:07:18.540> each<06:07:18.718> of<06:07:18.840> these<06:07:18.958> layers 06:07:19.250 --> 06:07:19.260 align:start position:0% we look at each of these layers 06:07:19.260 --> 06:07:21.830 align:start position:0% we look at each of these layers individually<06:07:19.860> we<06:07:20.340> can<06:07:20.520> very<06:07:20.878> easily<06:07:21.360> see<06:07:21.660> that 06:07:21.830 --> 06:07:21.840 align:start position:0% individually we can very easily see that 06:07:21.840 --> 06:07:24.288 align:start position:0% individually we can very easily see that the<06:07:22.080> functions<06:07:22.558> of<06:07:22.798> each<06:07:23.160> play<06:07:23.820> a<06:07:24.058> very 06:07:24.288 --> 06:07:24.298 align:start position:0% the functions of each play a very 06:07:24.298 --> 06:07:26.628 align:start position:0% the functions of each play a very specific<06:07:24.958> role<06:07:25.558> in<06:07:25.860> the<06:07:26.040> application 06:07:26.628 --> 06:07:26.638 align:start position:0% specific role in the application 06:07:26.638 --> 06:07:29.510 align:start position:0% specific role in the application management<06:07:27.138> support<06:07:28.138> and<06:07:28.980> keeping<06:07:29.400> them 06:07:29.510 --> 06:07:29.520 align:start position:0% management support and keeping them 06:07:29.520 --> 06:07:32.030 align:start position:0% management support and keeping them consistent<06:07:30.180> the<06:07:31.020> remaining<06:07:31.440> four<06:07:31.620> layers 06:07:32.030 --> 06:07:32.040 align:start position:0% consistent the remaining four layers 06:07:32.040 --> 06:07:34.368 align:start position:0% consistent the remaining four layers from<06:07:32.400> the<06:07:32.580> transport<06:07:33.120> layer<06:07:33.600> down<06:07:33.900> to<06:07:34.260> the 06:07:34.368 --> 06:07:34.378 align:start position:0% from the transport layer down to the 06:07:34.378 --> 06:07:36.288 align:start position:0% from the transport layer down to the physical<06:07:34.558> layer<06:07:35.100> are<06:07:35.520> what<06:07:35.700> we<06:07:35.820> call<06:07:36.000> the 06:07:36.288 --> 06:07:36.298 align:start position:0% physical layer are what we call the 06:07:36.298 --> 06:07:39.350 align:start position:0% physical layer are what we call the network<06:07:36.660> support<06:07:37.200> block<06:07:37.760> these<06:07:38.760> layers<06:07:39.058> and 06:07:39.350 --> 06:07:39.360 align:start position:0% network support block these layers and 06:07:39.360 --> 06:07:41.330 align:start position:0% network support block these layers and the<06:07:39.480> protocols<06:07:40.080> and<06:07:40.260> devices<06:07:40.558> that<06:07:40.980> operate 06:07:41.330 --> 06:07:41.340 align:start position:0% the protocols and devices that operate 06:07:41.340 --> 06:07:44.750 align:start position:0% the protocols and devices that operate on<06:07:41.580> them<06:07:41.820> are<06:07:42.660> all<06:07:43.138> Network<06:07:43.620> related<06:07:44.160> whether 06:07:44.750 --> 06:07:44.760 align:start position:0% on them are all Network related whether 06:07:44.760 --> 06:07:46.610 align:start position:0% on them are all Network related whether it's<06:07:44.940> for<06:07:45.180> routing<06:07:45.600> or<06:07:45.958> switching<06:07:46.320> on<06:07:46.500> the 06:07:46.610 --> 06:07:46.620 align:start position:0% it's for routing or switching on the 06:07:46.620 --> 06:07:48.770 align:start position:0% it's for routing or switching on the network<06:07:46.798> or<06:07:47.280> ensuring<06:07:47.700> data<06:07:48.180> delivery<06:07:48.480> on<06:07:48.660> the 06:07:48.770 --> 06:07:48.780 align:start position:0% network or ensuring data delivery on the 06:07:48.780 --> 06:07:51.288 align:start position:0% network or ensuring data delivery on the network<06:07:48.900> and<06:07:49.320> so<06:07:49.558> on<06:07:49.820> perhaps<06:07:50.820> even<06:07:51.000> making 06:07:51.288 --> 06:07:51.298 align:start position:0% network and so on perhaps even making 06:07:51.298 --> 06:07:53.390 align:start position:0% network and so on perhaps even making sure<06:07:51.540> that<06:07:51.718> the<06:07:51.958> actual<06:07:52.200> bits<06:07:52.920> all<06:07:53.218> the<06:07:53.340> way 06:07:53.390 --> 06:07:53.400 align:start position:0% sure that the actual bits all the way 06:07:53.400 --> 06:07:55.190 align:start position:0% sure that the actual bits all the way down<06:07:53.638> to<06:07:53.760> those<06:07:53.940> bits<06:07:54.360> of<06:07:54.660> data<06:07:55.020> being 06:07:55.190 --> 06:07:55.200 align:start position:0% down to those bits of data being 06:07:55.200 --> 06:07:57.288 align:start position:0% down to those bits of data being communicated<06:07:55.798> now<06:07:56.400> as<06:07:56.580> technicians<06:07:57.180> and 06:07:57.288 --> 06:07:57.298 align:start position:0% communicated now as technicians and 06:07:57.298 --> 06:07:59.448 align:start position:0% communicated now as technicians and specifically<06:07:57.840> for<06:07:58.080> the<06:07:58.260> exam<06:07:58.558> you<06:07:59.280> really 06:07:59.448 --> 06:07:59.458 align:start position:0% specifically for the exam you really 06:07:59.458 --> 06:08:02.030 align:start position:0% specifically for the exam you really want<06:07:59.760> to<06:07:59.878> know<06:08:00.058> which<06:08:00.480> layer<06:08:01.020> relates<06:08:01.798> to 06:08:02.030 --> 06:08:02.040 align:start position:0% want to know which layer relates to 06:08:02.040 --> 06:08:04.310 align:start position:0% want to know which layer relates to which<06:08:02.218> support<06:08:02.520> blocks<06:08:03.180> and<06:08:03.840> also<06:08:04.080> this<06:08:04.200> is 06:08:04.310 --> 06:08:04.320 align:start position:0% which support blocks and also this is 06:08:04.320 --> 06:08:05.390 align:start position:0% which support blocks and also this is going<06:08:04.440> to<06:08:04.500> help<06:08:04.620> a<06:08:04.740> great<06:08:04.860> deal<06:08:05.040> when<06:08:05.280> we 06:08:05.390 --> 06:08:05.400 align:start position:0% going to help a great deal when we 06:08:05.400 --> 06:08:07.250 align:start position:0% going to help a great deal when we discuss<06:08:05.760> the<06:08:06.120> next<06:08:06.298> networking<06:08:06.840> model<06:08:06.958> which 06:08:07.250 --> 06:08:07.260 align:start position:0% discuss the next networking model which 06:08:07.260 --> 06:08:12.410 align:start position:0% discuss the next networking model which is<06:08:07.320> the<06:08:07.500> tcpip<06:08:08.360> layer<06:08:09.360> model<06:08:09.600> so<06:08:10.500> uh<06:08:10.920> just<06:08:11.820> to 06:08:12.410 --> 06:08:12.420 align:start position:0% is the tcpip layer model so uh just to 06:08:12.420 --> 06:08:14.990 align:start position:0% is the tcpip layer model so uh just to sort<06:08:12.958> of<06:08:13.080> go<06:08:13.500> through<06:08:13.680> this<06:08:13.920> again 06:08:14.990 --> 06:08:15.000 align:start position:0% sort of go through this again 06:08:15.000 --> 06:08:18.590 align:start position:0% sort of go through this again we<06:08:15.600> start<06:08:15.840> here<06:08:16.200> at<06:08:16.620> the<06:08:17.058> application<06:08:18.058> layer 06:08:18.590 --> 06:08:18.600 align:start position:0% we start here at the application layer 06:08:18.600 --> 06:08:21.770 align:start position:0% we start here at the application layer and<06:08:19.320> we<06:08:19.440> work<06:08:19.680> our<06:08:19.920> way<06:08:20.100> down<06:08:20.400> until<06:08:21.240> we<06:08:21.600> get 06:08:21.770 --> 06:08:21.780 align:start position:0% and we work our way down until we get 06:08:21.780 --> 06:08:23.868 align:start position:0% and we work our way down until we get down<06:08:22.080> to<06:08:22.378> the<06:08:22.500> physical<06:08:22.740> layer<06:08:23.280> which<06:08:23.760> is 06:08:23.868 --> 06:08:23.878 align:start position:0% down to the physical layer which is 06:08:23.878 --> 06:08:25.490 align:start position:0% down to the physical layer which is where<06:08:24.120> the<06:08:24.298> data<06:08:24.660> can<06:08:24.900> actually<06:08:25.200> be 06:08:25.490 --> 06:08:25.500 align:start position:0% where the data can actually be 06:08:25.500 --> 06:08:27.890 align:start position:0% where the data can actually be transmitted 06:08:27.890 --> 06:08:27.900 align:start position:0% transmitted 06:08:27.900 --> 06:08:30.650 align:start position:0% transmitted over<06:08:28.378> the<06:08:28.558> network<06:08:28.760> and<06:08:29.760> then<06:08:29.878> it<06:08:30.058> builds<06:08:30.360> its 06:08:30.650 --> 06:08:30.660 align:start position:0% over the network and then it builds its 06:08:30.660 --> 06:08:32.930 align:start position:0% over the network and then it builds its way<06:08:30.780> back<06:08:31.260> up<06:08:31.620> until<06:08:31.860> we<06:08:32.218> get<06:08:32.340> to<06:08:32.520> the<06:08:32.760> last 06:08:32.930 --> 06:08:32.940 align:start position:0% way back up until we get to the last 06:08:32.940 --> 06:08:36.110 align:start position:0% way back up until we get to the last application<06:08:33.540> so<06:08:34.138> if<06:08:34.260> I'm<06:08:34.440> browsing<06:08:35.160> uh<06:08:36.000> let's 06:08:36.110 --> 06:08:36.120 align:start position:0% application so if I'm browsing uh let's 06:08:36.120 --> 06:08:38.690 align:start position:0% application so if I'm browsing uh let's say<06:08:36.360> this<06:08:36.660> is<06:08:36.840> me 06:08:38.690 --> 06:08:38.700 align:start position:0% say this is me 06:08:38.700 --> 06:08:41.810 align:start position:0% say this is me right<06:08:39.298> and<06:08:39.660> this<06:08:39.840> is<06:08:40.080> a<06:08:40.558> web 06:08:41.810 --> 06:08:41.820 align:start position:0% right and this is a web 06:08:41.820 --> 06:08:44.750 align:start position:0% right and this is a web sort<06:08:42.420> of<06:08:42.600> server 06:08:44.750 --> 06:08:44.760 align:start position:0% sort of server 06:08:44.760 --> 06:08:49.310 align:start position:0% sort of server I<06:08:45.718> send<06:08:46.500> a<06:08:47.040> request<06:08:47.520> the<06:08:48.058> request<06:08:48.360> goes<06:08:48.840> down 06:08:49.310 --> 06:08:49.320 align:start position:0% I send a request the request goes down 06:08:49.320 --> 06:08:52.788 align:start position:0% I send a request the request goes down all<06:08:49.740> the<06:08:49.920> way<06:08:50.040> goes<06:08:51.000> over<06:08:51.420> the<06:08:51.718> network<06:08:51.900> it 06:08:52.788 --> 06:08:52.798 align:start position:0% all the way goes over the network it 06:08:52.798 --> 06:08:54.470 align:start position:0% all the way goes over the network it might<06:08:52.920> even<06:08:53.100> hit<06:08:53.340> a<06:08:53.580> couple<06:08:53.700> routers<06:08:54.240> along 06:08:54.470 --> 06:08:54.480 align:start position:0% might even hit a couple routers along 06:08:54.480 --> 06:08:56.390 align:start position:0% might even hit a couple routers along the<06:08:54.718> way 06:08:56.390 --> 06:08:56.400 align:start position:0% the way 06:08:56.400 --> 06:09:00.470 align:start position:0% the way or<06:08:56.940> switches<06:08:57.360> rather 06:09:00.470 --> 06:09:00.480 align:start position:0% 06:09:00.480 --> 06:09:01.850 align:start position:0% so<06:09:00.718> we're<06:09:00.780> hitting<06:09:01.020> some<06:09:01.138> switches<06:09:01.558> and<06:09:01.740> then 06:09:01.850 --> 06:09:01.860 align:start position:0% so we're hitting some switches and then 06:09:01.860 --> 06:09:03.410 align:start position:0% so we're hitting some switches and then we<06:09:01.980> hit<06:09:02.100> some<06:09:02.340> routers<06:09:02.760> then<06:09:03.000> we<06:09:03.120> had<06:09:03.240> some 06:09:03.410 --> 06:09:03.420 align:start position:0% we hit some routers then we had some 06:09:03.420 --> 06:09:06.048 align:start position:0% we hit some routers then we had some switches<06:09:03.958> and<06:09:04.740> then<06:09:04.860> it's<06:09:05.040> going<06:09:05.218> to<06:09:05.340> go<06:09:05.520> all 06:09:06.048 --> 06:09:06.058 align:start position:0% switches and then it's going to go all 06:09:06.058 --> 06:09:08.390 align:start position:0% switches and then it's going to go all the<06:09:06.240> way<06:09:06.298> up<06:09:06.540> again<06:09:06.660> to<06:09:07.020> the<06:09:07.138> web<06:09:07.260> server<06:09:07.740> and 06:09:08.390 --> 06:09:08.400 align:start position:0% the way up again to the web server and 06:09:08.400 --> 06:09:09.650 align:start position:0% the way up again to the web server and then<06:09:08.520> the<06:09:08.638> web<06:09:08.760> server<06:09:09.058> is<06:09:09.180> going<06:09:09.360> to<06:09:09.480> send 06:09:09.650 --> 06:09:09.660 align:start position:0% then the web server is going to send 06:09:09.660 --> 06:09:13.010 align:start position:0% then the web server is going to send that<06:09:10.020> data<06:09:10.378> back<06:09:11.040> Etc<06:09:11.218> and<06:09:12.000> so<06:09:12.180> we<06:09:12.420> go<06:09:12.600> this 06:09:13.010 --> 06:09:13.020 align:start position:0% that data back Etc and so we go this 06:09:13.020 --> 06:09:16.128 align:start position:0% that data back Etc and so we go this really<06:09:13.260> follows<06:09:13.860> on<06:09:14.160> each<06:09:14.458> end<06:09:14.760> how<06:09:15.480> data<06:09:15.958> is 06:09:16.128 --> 06:09:16.138 align:start position:0% really follows on each end how data is 06:09:16.138 --> 06:09:19.310 align:start position:0% really follows on each end how data is being<06:09:16.440> sent<06:09:16.980> and<06:09:17.340> received<06:09:18.298> so<06:09:18.780> before<06:09:18.958> we 06:09:19.310 --> 06:09:19.320 align:start position:0% being sent and received so before we 06:09:19.320 --> 06:09:21.530 align:start position:0% being sent and received so before we wrap<06:09:19.620> this<06:09:19.860> up<06:09:20.100> there's<06:09:20.580> a<06:09:20.940> couple<06:09:21.058> ways<06:09:21.420> to 06:09:21.530 --> 06:09:21.540 align:start position:0% wrap this up there's a couple ways to 06:09:21.540 --> 06:09:23.330 align:start position:0% wrap this up there's a couple ways to remember<06:09:21.718> these<06:09:22.138> and<06:09:22.320> I'd<06:09:22.500> really<06:09:22.740> highly 06:09:23.330 --> 06:09:23.340 align:start position:0% remember these and I'd really highly 06:09:23.340 --> 06:09:25.548 align:start position:0% remember these and I'd really highly recommend<06:09:23.820> committing<06:09:24.480> this<06:09:24.660> OSI<06:09:25.080> model<06:09:25.320> to 06:09:25.548 --> 06:09:25.558 align:start position:0% recommend committing this OSI model to 06:09:25.558 --> 06:09:27.530 align:start position:0% recommend committing this OSI model to memory<06:09:25.860> there's<06:09:26.458> two<06:09:26.638> ways<06:09:26.878> we<06:09:27.000> do<06:09:27.120> this<06:09:27.240> one 06:09:27.530 --> 06:09:27.540 align:start position:0% memory there's two ways we do this one 06:09:27.540 --> 06:09:31.208 align:start position:0% memory there's two ways we do this one is<06:09:27.718> called<06:09:28.020> the<06:09:28.860> top 06:09:31.208 --> 06:09:31.218 align:start position:0% 06:09:31.218 --> 06:09:35.208 align:start position:0% down<06:09:32.218> approach<06:09:33.080> this<06:09:34.080> starts<06:09:34.500> with<06:09:34.798> layer 06:09:35.208 --> 06:09:35.218 align:start position:0% down approach this starts with layer 06:09:35.218 --> 06:09:36.230 align:start position:0% down approach this starts with layer seven 06:09:36.230 --> 06:09:36.240 align:start position:0% seven 06:09:36.240 --> 06:09:38.570 align:start position:0% seven and<06:09:36.780> ends<06:09:37.020> with<06:09:37.138> layer<06:09:37.620> one<06:09:37.798> now<06:09:38.218> the<06:09:38.458> reason 06:09:38.570 --> 06:09:38.580 align:start position:0% and ends with layer one now the reason 06:09:38.580 --> 06:09:40.250 align:start position:0% and ends with layer one now the reason you<06:09:38.820> want<06:09:39.000> to<06:09:39.180> just<06:09:39.600> remember<06:09:39.780> whichever 06:09:40.250 --> 06:09:40.260 align:start position:0% you want to just remember whichever 06:09:40.260 --> 06:09:41.570 align:start position:0% you want to just remember whichever mnemonic<06:09:40.740> device<06:09:40.860> I'm<06:09:41.100> about<06:09:41.218> to<06:09:41.400> tell<06:09:41.458> you 06:09:41.570 --> 06:09:41.580 align:start position:0% mnemonic device I'm about to tell you 06:09:41.580 --> 06:09:42.530 align:start position:0% mnemonic device I'm about to tell you just<06:09:41.760> remember<06:09:41.878> which<06:09:42.180> one<06:09:42.360> you're 06:09:42.530 --> 06:09:42.540 align:start position:0% just remember which one you're 06:09:42.540 --> 06:09:43.850 align:start position:0% just remember which one you're remembering<06:09:42.958> so<06:09:43.138> that<06:09:43.260> way<06:09:43.378> you<06:09:43.440> know<06:09:43.558> how<06:09:43.740> to 06:09:43.850 --> 06:09:43.860 align:start position:0% remembering so that way you know how to 06:09:43.860 --> 06:09:44.990 align:start position:0% remembering so that way you know how to write<06:09:43.980> it 06:09:44.990 --> 06:09:45.000 align:start position:0% write it 06:09:45.000 --> 06:09:47.330 align:start position:0% write it a<06:09:45.660> great<06:09:45.780> way<06:09:45.958> to<06:09:46.080> remember<06:09:46.200> this<06:09:46.500> one<06:09:46.680> is<06:09:46.980> all 06:09:47.330 --> 06:09:47.340 align:start position:0% a great way to remember this one is all 06:09:47.340 --> 06:09:50.030 align:start position:0% a great way to remember this one is all people<06:09:47.580> seem<06:09:48.120> to<06:09:48.240> need<06:09:48.480> delicious<06:09:49.080> pizza 06:09:50.030 --> 06:09:50.040 align:start position:0% people seem to need delicious pizza 06:09:50.040 --> 06:09:53.330 align:start position:0% people seem to need delicious pizza uh<06:09:50.820> now<06:09:51.120> again<06:09:51.600> all<06:09:52.138> his<06:09:52.320> application<06:09:52.798> starts 06:09:53.330 --> 06:09:53.340 align:start position:0% uh now again all his application starts 06:09:53.340 --> 06:09:56.270 align:start position:0% uh now again all his application starts at<06:09:53.458> seven<06:09:53.760> so<06:09:54.420> we're<06:09:54.600> starting<06:09:54.780> with<06:09:55.138> the<06:09:55.440> user 06:09:56.270 --> 06:09:56.280 align:start position:0% at seven so we're starting with the user 06:09:56.280 --> 06:09:59.448 align:start position:0% at seven so we're starting with the user and<06:09:56.760> we're<06:09:56.878> going<06:09:57.240> down<06:09:57.600> to<06:09:58.260> physical<06:09:58.500> to<06:09:59.280> the 06:09:59.448 --> 06:09:59.458 align:start position:0% and we're going down to physical to the 06:09:59.458 --> 06:10:02.208 align:start position:0% and we're going down to physical to the hardware 06:10:02.208 --> 06:10:02.218 align:start position:0% 06:10:02.218 --> 06:10:03.830 align:start position:0% now<06:10:02.638> the<06:10:02.820> other<06:10:02.940> way<06:10:03.240> I<06:10:03.420> like<06:10:03.540> to<06:10:03.660> remember 06:10:03.830 --> 06:10:03.840 align:start position:0% now the other way I like to remember 06:10:03.840 --> 06:10:09.230 align:start position:0% now the other way I like to remember this<06:10:04.138> is<06:10:04.920> uh<06:10:05.820> please<06:10:06.420> do<06:10:07.080> not<06:10:07.378> throw<06:10:08.340> sausage 06:10:09.230 --> 06:10:09.240 align:start position:0% this is uh please do not throw sausage 06:10:09.240 --> 06:10:11.510 align:start position:0% this is uh please do not throw sausage pizza<06:10:09.600> away<06:10:10.080> that's<06:10:10.440> my<06:10:10.860> particular<06:10:11.160> favorite 06:10:11.510 --> 06:10:11.520 align:start position:0% pizza away that's my particular favorite 06:10:11.520 --> 06:10:16.910 align:start position:0% pizza away that's my particular favorite now<06:10:12.240> here<06:10:12.480> we're<06:10:12.718> taking<06:10:13.020> a<06:10:13.620> bottom 06:10:16.910 --> 06:10:16.920 align:start position:0% 06:10:16.920 --> 06:10:18.830 align:start position:0% up<06:10:17.218> approach<06:10:17.940> because<06:10:18.180> we're<06:10:18.360> going<06:10:18.540> from<06:10:18.718> the 06:10:18.830 --> 06:10:18.840 align:start position:0% up approach because we're going from the 06:10:18.840 --> 06:10:20.930 align:start position:0% up approach because we're going from the bottom<06:10:19.080> up<06:10:19.260> so<06:10:19.500> realize<06:10:19.920> that<06:10:20.218> this<06:10:20.638> you're 06:10:20.930 --> 06:10:20.940 align:start position:0% bottom up so realize that this you're 06:10:20.940 --> 06:10:23.510 align:start position:0% bottom up so realize that this you're starting<06:10:21.180> with<06:10:21.600> the<06:10:22.200> physical<06:10:22.378> layer 06:10:23.510 --> 06:10:23.520 align:start position:0% starting with the physical layer 06:10:23.520 --> 06:10:26.330 align:start position:0% starting with the physical layer and<06:10:24.058> going<06:10:24.298> up<06:10:24.480> to<06:10:24.660> the<06:10:24.840> application<06:10:25.260> layer<06:10:25.740> so 06:10:26.330 --> 06:10:26.340 align:start position:0% and going up to the application layer so 06:10:26.340 --> 06:10:28.128 align:start position:0% and going up to the application layer so however<06:10:26.638> which<06:10:26.940> one<06:10:27.120> of<06:10:27.240> one<06:10:27.718> of<06:10:27.780> these<06:10:27.900> you 06:10:28.128 --> 06:10:28.138 align:start position:0% however which one of one of these you 06:10:28.138 --> 06:10:30.890 align:start position:0% however which one of one of these you memorize<06:10:28.798> you<06:10:29.040> use<06:10:29.280> to<06:10:29.520> memorize<06:10:29.940> this<06:10:30.240> uh 06:10:30.890 --> 06:10:30.900 align:start position:0% memorize you use to memorize this uh 06:10:30.900 --> 06:10:32.810 align:start position:0% memorize you use to memorize this uh just<06:10:31.138> remember<06:10:31.378> to<06:10:31.620> commit<06:10:31.980> it<06:10:32.100> to<06:10:32.218> memory<06:10:32.520> and 06:10:32.810 --> 06:10:32.820 align:start position:0% just remember to commit it to memory and 06:10:32.820 --> 06:10:34.730 align:start position:0% just remember to commit it to memory and when<06:10:33.058> you<06:10:33.240> get<06:10:33.420> to<06:10:33.600> your<06:10:33.780> exam<06:10:34.020> write<06:10:34.378> it<06:10:34.500> down 06:10:34.730 --> 06:10:34.740 align:start position:0% when you get to your exam write it down 06:10:34.740 --> 06:10:36.590 align:start position:0% when you get to your exam write it down immediately<06:10:35.280> so<06:10:35.638> you<06:10:35.820> can<06:10:35.878> just<06:10:36.058> look<06:10:36.298> at<06:10:36.480> it 06:10:36.590 --> 06:10:36.600 align:start position:0% immediately so you can just look at it 06:10:36.600 --> 06:10:41.948 align:start position:0% immediately so you can just look at it and<06:10:37.020> remember<06:10:37.200> this<06:10:37.680> is<06:10:37.798> seven<06:10:38.420> six<06:10:39.680> five<06:10:40.700> four 06:10:41.948 --> 06:10:41.958 align:start position:0% and remember this is seven six five four 06:10:41.958 --> 06:10:46.970 align:start position:0% and remember this is seven six five four three<06:10:42.958> two<06:10:43.920> one<06:10:44.878> this<06:10:45.600> is<06:10:45.718> where<06:10:46.080> hubs<06:10:46.798> would 06:10:46.970 --> 06:10:46.980 align:start position:0% three two one this is where hubs would 06:10:46.980 --> 06:10:49.128 align:start position:0% three two one this is where hubs would function<06:10:47.340> again<06:10:48.058> uh<06:10:48.660> they're<06:10:48.958> just 06:10:49.128 --> 06:10:49.138 align:start position:0% function again uh they're just 06:10:49.138 --> 06:10:50.810 align:start position:0% function again uh they're just forwarding<06:10:49.620> the<06:10:49.798> same<06:10:49.980> information<06:10:50.218> just 06:10:50.810 --> 06:10:50.820 align:start position:0% forwarding the same information just 06:10:50.820 --> 06:10:52.548 align:start position:0% forwarding the same information just like<06:10:50.940> this<06:10:51.120> is<06:10:51.298> where<06:10:51.600> a<06:10:52.080> cable<06:10:52.320> would 06:10:52.548 --> 06:10:52.558 align:start position:0% like this is where a cable would 06:10:52.558 --> 06:10:55.070 align:start position:0% like this is where a cable would function<06:10:52.920> data<06:10:53.878> link<06:10:54.000> is<06:10:54.240> where<06:10:54.600> most 06:10:55.070 --> 06:10:55.080 align:start position:0% function data link is where most 06:10:55.080 --> 06:10:58.190 align:start position:0% function data link is where most switches<06:10:56.040> are<06:10:56.400> going<06:10:56.580> to<06:10:56.820> function<06:10:57.120> and<06:10:58.020> on 06:10:58.190 --> 06:10:58.200 align:start position:0% switches are going to function and on 06:10:58.200 --> 06:10:59.448 align:start position:0% switches are going to function and on the<06:10:58.320> network<06:10:58.500> layer<06:10:58.920> that's<06:10:59.100> where<06:10:59.280> we're 06:10:59.448 --> 06:10:59.458 align:start position:0% the network layer that's where we're 06:10:59.458 --> 06:11:01.910 align:start position:0% the network layer that's where we're going<06:10:59.580> to<06:10:59.700> see<06:10:59.820> routers<06:11:00.780> function<06:11:01.200> this<06:11:01.798> is 06:11:01.910 --> 06:11:01.920 align:start position:0% going to see routers function this is 06:11:01.920 --> 06:11:04.010 align:start position:0% going to see routers function this is the<06:11:02.160> most<06:11:02.340> information<06:11:02.638> that<06:11:03.240> I<06:11:03.420> see<06:11:03.600> on<06:11:03.900> the 06:11:04.010 --> 06:11:04.020 align:start position:0% the most information that I see on the 06:11:04.020 --> 06:11:05.628 align:start position:0% the most information that I see on the exam<06:11:04.260> and<06:11:04.440> so<06:11:04.620> if<06:11:04.680> you<06:11:04.798> Commit<06:11:05.040> This<06:11:05.280> to<06:11:05.400> Memory 06:11:05.628 --> 06:11:05.638 align:start position:0% exam and so if you Commit This to Memory 06:11:05.638 --> 06:11:07.788 align:start position:0% exam and so if you Commit This to Memory I<06:11:05.878> think<06:11:06.058> you'll<06:11:06.298> be<06:11:06.420> set 06:11:07.788 --> 06:11:07.798 align:start position:0% I think you'll be set 06:11:07.798 --> 06:11:10.730 align:start position:0% I think you'll be set okay<06:11:08.458> so<06:11:09.000> just<06:11:09.180> to<06:11:09.360> recap<06:11:09.718> one<06:11:10.138> last<06:11:10.260> time<06:11:10.500> and 06:11:10.730 --> 06:11:10.740 align:start position:0% okay so just to recap one last time and 06:11:10.740 --> 06:11:12.770 align:start position:0% okay so just to recap one last time and review<06:11:10.860> everything<06:11:11.340> we've<06:11:11.760> discussed<06:11:12.180> first 06:11:12.770 --> 06:11:12.780 align:start position:0% review everything we've discussed first 06:11:12.780 --> 06:11:15.288 align:start position:0% review everything we've discussed first we<06:11:13.138> explained<06:11:13.740> the<06:11:14.340> history<06:11:14.580> and<06:11:14.940> the<06:11:15.058> purpose 06:11:15.288 --> 06:11:15.298 align:start position:0% we explained the history and the purpose 06:11:15.298 --> 06:11:17.628 align:start position:0% we explained the history and the purpose of<06:11:15.480> the<06:11:15.600> OSI<06:11:16.080> model<06:11:16.320> remember<06:11:16.980> the<06:11:17.340> important 06:11:17.628 --> 06:11:17.638 align:start position:0% of the OSI model remember the important 06:11:17.638 --> 06:11:20.030 align:start position:0% of the OSI model remember the important thing<06:11:17.878> to<06:11:18.058> realize<06:11:18.360> here<06:11:18.718> is<06:11:19.200> that<06:11:19.440> it's<06:11:19.740> a 06:11:20.030 --> 06:11:20.040 align:start position:0% thing to realize here is that it's a 06:11:20.040 --> 06:11:21.650 align:start position:0% thing to realize here is that it's a layered<06:11:20.458> model<06:11:20.638> and<06:11:21.000> the<06:11:21.240> reason<06:11:21.360> it's 06:11:21.650 --> 06:11:21.660 align:start position:0% layered model and the reason it's 06:11:21.660 --> 06:11:25.030 align:start position:0% layered model and the reason it's layered<06:11:22.020> is<06:11:22.200> to<06:11:22.378> make<06:11:22.558> it<06:11:22.740> easier<06:11:23.218> not<06:11:23.940> only<06:11:24.120> to 06:11:25.030 --> 06:11:25.040 align:start position:0% layered is to make it easier not only to 06:11:25.040 --> 06:11:27.948 align:start position:0% layered is to make it easier not only to develop<06:11:26.040> things<06:11:26.340> for<06:11:26.700> each<06:11:27.000> layer<06:11:27.360> instead<06:11:27.840> of 06:11:27.948 --> 06:11:27.958 align:start position:0% develop things for each layer instead of 06:11:27.958 --> 06:11:29.390 align:start position:0% develop things for each layer instead of having<06:11:28.080> to<06:11:28.260> develop<06:11:28.620> something<06:11:28.860> for<06:11:29.160> the 06:11:29.390 --> 06:11:29.400 align:start position:0% having to develop something for the 06:11:29.400 --> 06:11:31.610 align:start position:0% having to develop something for the entire<06:11:29.878> system<06:11:30.298> I<06:11:30.600> can<06:11:30.718> just<06:11:30.900> develop<06:11:31.260> one 06:11:31.610 --> 06:11:31.620 align:start position:0% entire system I can just develop one 06:11:31.620 --> 06:11:34.850 align:start position:0% entire system I can just develop one little<06:11:31.798> device<06:11:32.218> such<06:11:33.058> as<06:11:33.240> a<06:11:33.600> router<06:11:34.020> or<06:11:34.680> a 06:11:34.850 --> 06:11:34.860 align:start position:0% little device such as a router or a 06:11:34.860 --> 06:11:37.128 align:start position:0% little device such as a router or a switch<06:11:35.040> and<06:11:35.820> also<06:11:36.058> it's<06:11:36.240> going<06:11:36.420> to<06:11:36.540> be<06:11:36.660> easier 06:11:37.128 --> 06:11:37.138 align:start position:0% switch and also it's going to be easier 06:11:37.138 --> 06:11:40.368 align:start position:0% switch and also it's going to be easier to<06:11:37.980> troubleshoot<06:11:38.760> and<06:11:39.240> fix<06:11:39.600> anything<06:11:40.080> that 06:11:40.368 --> 06:11:40.378 align:start position:0% to troubleshoot and fix anything that 06:11:40.378 --> 06:11:41.448 align:start position:0% to troubleshoot and fix anything that goes<06:11:40.740> wrong 06:11:41.448 --> 06:11:41.458 align:start position:0% goes wrong 06:11:41.458 --> 06:11:43.970 align:start position:0% goes wrong we<06:11:42.058> then<06:11:42.180> talked<06:11:42.540> about<06:11:42.660> layer<06:11:43.320> one<06:11:43.500> the 06:11:43.970 --> 06:11:43.980 align:start position:0% we then talked about layer one the 06:11:43.980 --> 06:11:46.788 align:start position:0% we then talked about layer one the physical<06:11:44.160> layer<06:11:44.700> right<06:11:45.420> and<06:11:45.900> this<06:11:46.138> is<06:11:46.378> uh 06:11:46.788 --> 06:11:46.798 align:start position:0% physical layer right and this is uh 06:11:46.798 --> 06:11:48.890 align:start position:0% physical layer right and this is uh where<06:11:47.280> chords 06:11:48.890 --> 06:11:48.900 align:start position:0% where chords 06:11:48.900 --> 06:11:53.150 align:start position:0% where chords for<06:11:49.440> instance<06:11:49.740> the<06:11:50.280> media<06:11:50.638> exists 06:11:53.150 --> 06:11:53.160 align:start position:0% for instance the media exists 06:11:53.160 --> 06:11:55.310 align:start position:0% for instance the media exists and<06:11:53.700> where<06:11:53.940> all<06:11:54.240> the<06:11:54.420> bits<06:11:54.780> are<06:11:54.900> going<06:11:55.080> to<06:11:55.200> go 06:11:55.310 --> 06:11:55.320 align:start position:0% and where all the bits are going to go 06:11:55.320 --> 06:11:57.350 align:start position:0% and where all the bits are going to go from<06:11:55.558> one<06:11:55.798> place<06:11:55.980> to<06:11:56.218> the<06:11:56.400> other<06:11:56.580> we're<06:11:57.120> really 06:11:57.350 --> 06:11:57.360 align:start position:0% from one place to the other we're really 06:11:57.360 --> 06:11:59.628 align:start position:0% from one place to the other we're really here<06:11:57.540> dealing<06:11:57.958> with<06:11:58.138> the<06:11:58.320> ones<06:11:58.620> and<06:11:58.860> zeros<06:11:59.280> the 06:11:59.628 --> 06:11:59.638 align:start position:0% here dealing with the ones and zeros the 06:11:59.638 --> 06:12:02.750 align:start position:0% here dealing with the ones and zeros the electrical<06:12:00.058> bits<06:12:00.480> also<06:12:01.200> remember<06:12:01.440> hubs<06:12:02.400> exist 06:12:02.750 --> 06:12:02.760 align:start position:0% electrical bits also remember hubs exist 06:12:02.760 --> 06:12:03.948 align:start position:0% electrical bits also remember hubs exist here<06:12:03.058> as<06:12:03.240> well 06:12:03.948 --> 06:12:03.958 align:start position:0% here as well 06:12:03.958 --> 06:12:06.948 align:start position:0% here as well we<06:12:04.440> then<06:12:04.620> talked<06:12:05.100> about<06:12:05.340> the<06:12:06.000> data<06:12:06.360> link<06:12:06.480> layer 06:12:06.948 --> 06:12:06.958 align:start position:0% we then talked about the data link layer 06:12:06.958 --> 06:12:10.970 align:start position:0% we then talked about the data link layer this<06:12:07.740> also<06:12:08.100> had<06:12:08.340> two<06:12:08.700> sub-layers<06:12:09.360> Mac 06:12:10.970 --> 06:12:10.980 align:start position:0% this also had two sub-layers Mac 06:12:10.980 --> 06:12:13.610 align:start position:0% this also had two sub-layers Mac and<06:12:11.700> LLC 06:12:13.610 --> 06:12:13.620 align:start position:0% and LLC 06:12:13.620 --> 06:12:17.030 align:start position:0% and LLC and<06:12:14.400> this<06:12:14.760> is<06:12:14.878> where<06:12:15.120> we<06:12:15.420> see<06:12:15.660> Mac<06:12:16.320> addressing 06:12:17.030 --> 06:12:17.040 align:start position:0% and this is where we see Mac addressing 06:12:17.040 --> 06:12:21.170 align:start position:0% and this is where we see Mac addressing or<06:12:17.760> physical<06:12:18.200> addresses<06:12:19.200> start<06:12:19.798> to<06:12:20.040> occur<06:12:20.458> and 06:12:21.170 --> 06:12:21.180 align:start position:0% or physical addresses start to occur and 06:12:21.180 --> 06:12:22.730 align:start position:0% or physical addresses start to occur and that<06:12:21.360> means<06:12:21.660> that<06:12:21.900> here<06:12:22.138> is<06:12:22.320> where<06:12:22.558> we're 06:12:22.730 --> 06:12:22.740 align:start position:0% that means that here is where we're 06:12:22.740 --> 06:12:24.048 align:start position:0% that means that here is where we're really<06:12:22.920> going<06:12:23.100> to<06:12:23.280> deal 06:12:24.048 --> 06:12:24.058 align:start position:0% really going to deal 06:12:24.058 --> 06:12:28.190 align:start position:0% really going to deal with<06:12:24.600> switches 06:12:28.190 --> 06:12:28.200 align:start position:0% 06:12:28.200 --> 06:12:30.890 align:start position:0% the<06:12:28.860> data<06:12:29.160> here<06:12:29.280> by<06:12:29.580> the<06:12:29.700> way<06:12:29.820> is<06:12:30.298> called<06:12:30.480> is 06:12:30.890 --> 06:12:30.900 align:start position:0% the data here by the way is called is 06:12:30.900 --> 06:12:33.230 align:start position:0% the data here by the way is called is put<06:12:31.260> into<06:12:31.440> what<06:12:31.798> we<06:12:31.980> call<06:12:32.218> frames<06:12:32.760> instead<06:12:33.120> of 06:12:33.230 --> 06:12:33.240 align:start position:0% put into what we call frames instead of 06:12:33.240 --> 06:12:36.170 align:start position:0% put into what we call frames instead of just<06:12:33.420> dealing<06:12:33.840> with<06:12:34.080> bits 06:12:36.170 --> 06:12:36.180 align:start position:0% just dealing with bits 06:12:36.180 --> 06:12:38.868 align:start position:0% just dealing with bits now<06:12:36.660> the<06:12:36.958> next<06:12:37.138> layer<06:12:37.500> is<06:12:37.680> the<06:12:38.040> network<06:12:38.280> layer 06:12:38.868 --> 06:12:38.878 align:start position:0% now the next layer is the network layer 06:12:38.878 --> 06:12:41.990 align:start position:0% now the next layer is the network layer and<06:12:39.600> this<06:12:40.020> is<06:12:40.200> where<06:12:40.558> we<06:12:41.340> start<06:12:41.580> to<06:12:41.760> see 06:12:41.990 --> 06:12:42.000 align:start position:0% and this is where we start to see 06:12:42.000 --> 06:12:44.868 align:start position:0% and this is where we start to see routing<06:12:42.900> and<06:12:43.500> this<06:12:43.680> is<06:12:43.860> thanks<06:12:44.160> to<06:12:44.520> a<06:12:44.700> new 06:12:44.868 --> 06:12:44.878 align:start position:0% routing and this is thanks to a new 06:12:44.878 --> 06:12:47.448 align:start position:0% routing and this is thanks to a new addressing<06:12:45.480> system<06:12:45.780> specifically<06:12:46.680> the<06:12:47.160> one 06:12:47.448 --> 06:12:47.458 align:start position:0% addressing system specifically the one 06:12:47.458 --> 06:12:49.128 align:start position:0% addressing system specifically the one we're<06:12:47.700> going<06:12:47.820> to<06:12:47.878> see<06:12:48.000> the<06:12:48.180> most<06:12:48.298> is<06:12:48.660> IP 06:12:49.128 --> 06:12:49.138 align:start position:0% we're going to see the most is IP 06:12:49.138 --> 06:12:51.288 align:start position:0% we're going to see the most is IP addressing<06:12:49.740> this<06:12:50.280> means<06:12:50.580> here<06:12:50.820> is<06:12:51.058> where 06:12:51.288 --> 06:12:51.298 align:start position:0% addressing this means here is where 06:12:51.298 --> 06:12:53.868 align:start position:0% addressing this means here is where we're<06:12:51.420> going<06:12:51.540> to<06:12:51.660> start<06:12:51.840> seeing<06:12:52.340> routers<06:12:53.340> and 06:12:53.868 --> 06:12:53.878 align:start position:0% we're going to start seeing routers and 06:12:53.878 --> 06:12:57.288 align:start position:0% we're going to start seeing routers and don't<06:12:54.058> forget<06:12:54.240> here<06:12:54.660> we<06:12:55.020> see<06:12:55.200> start<06:12:55.558> seeing<06:12:55.980> uh 06:12:57.288 --> 06:12:57.298 align:start position:0% don't forget here we see start seeing uh 06:12:57.298 --> 06:13:01.070 align:start position:0% don't forget here we see start seeing uh terminology<06:12:58.580> for<06:12:59.580> packets 06:13:01.070 --> 06:13:01.080 align:start position:0% terminology for packets 06:13:01.080 --> 06:13:05.170 align:start position:0% terminology for packets and<06:13:01.558> the<06:13:01.680> one<06:13:01.798> we<06:13:01.980> mentioned<06:13:02.400> too<06:13:02.638> was 06:13:05.170 --> 06:13:05.180 align:start position:0% 06:13:05.180 --> 06:13:08.270 align:start position:0% datagrams<06:13:06.180> we<06:13:06.900> also<06:13:07.200> mentioned<06:13:07.558> that<06:13:07.920> this<06:13:08.160> is 06:13:08.270 --> 06:13:08.280 align:start position:0% datagrams we also mentioned that this is 06:13:08.280 --> 06:13:14.270 align:start position:0% datagrams we also mentioned that this is where<06:13:08.520> we<06:13:08.820> see<06:13:09.200> connection<06:13:10.200> loss 06:13:14.270 --> 06:13:14.280 align:start position:0% 06:13:14.280 --> 06:13:16.970 align:start position:0% or<06:13:14.638> connections<06:13:15.058> that<06:13:15.298> don't<06:13:15.480> sort<06:13:15.718> of<06:13:15.840> have<06:13:16.138> a 06:13:16.970 --> 06:13:16.980 align:start position:0% or connections that don't sort of have a 06:13:16.980 --> 06:13:21.048 align:start position:0% or connections that don't sort of have a definite<06:13:17.700> got<06:13:18.540> sent<06:13:18.840> or<06:13:19.260> delivery<06:13:19.860> receipt<06:13:20.340> we 06:13:21.048 --> 06:13:21.058 align:start position:0% definite got sent or delivery receipt we 06:13:21.058 --> 06:13:23.750 align:start position:0% definite got sent or delivery receipt we then<06:13:21.180> looked<06:13:21.600> at<06:13:21.780> layer<06:13:22.558> four<06:13:22.798> which<06:13:23.458> is<06:13:23.580> where 06:13:23.750 --> 06:13:23.760 align:start position:0% then looked at layer four which is where 06:13:23.760 --> 06:13:27.948 align:start position:0% then looked at layer four which is where we<06:13:24.058> see<06:13:24.320> TCP<06:13:25.320> from<06:13:25.740> the<06:13:25.860> IP<06:13:26.280> Suite<06:13:26.760> right<06:13:27.540> and 06:13:27.948 --> 06:13:27.958 align:start position:0% we see TCP from the IP Suite right and 06:13:27.958 --> 06:13:29.150 align:start position:0% we see TCP from the IP Suite right and this<06:13:28.138> is<06:13:28.260> the<06:13:28.440> one<06:13:28.500> that's<06:13:28.740> going<06:13:28.920> to<06:13:29.040> start 06:13:29.150 --> 06:13:29.160 align:start position:0% this is the one that's going to start 06:13:29.160 --> 06:13:37.310 align:start position:0% this is the one that's going to start looking<06:13:29.400> at<06:13:29.780> guaranteeing<06:13:30.780> our<06:13:31.138> delivery 06:13:37.310 --> 06:13:37.320 align:start position:0% 06:13:37.320 --> 06:13:39.590 align:start position:0% layer<06:13:38.280> 4<06:13:38.400> is<06:13:38.638> also<06:13:38.878> where<06:13:39.058> we<06:13:39.240> ensure 06:13:39.590 --> 06:13:39.600 align:start position:0% layer 4 is also where we ensure 06:13:39.600 --> 06:13:42.650 align:start position:0% layer 4 is also where we ensure reliability 06:13:42.650 --> 06:13:42.660 align:start position:0% 06:13:42.660 --> 06:13:47.810 align:start position:0% and<06:13:43.260> flow<06:13:43.620> control 06:13:47.810 --> 06:13:47.820 align:start position:0% 06:13:47.820 --> 06:13:50.448 align:start position:0% here<06:13:48.480> information 06:13:50.448 --> 06:13:50.458 align:start position:0% here information 06:13:50.458 --> 06:13:52.970 align:start position:0% here information is<06:13:51.000> called<06:13:51.240> segments<06:13:51.958> when<06:13:52.320> we<06:13:52.440> get<06:13:52.558> to<06:13:52.680> layer 06:13:52.970 --> 06:13:52.980 align:start position:0% is called segments when we get to layer 06:13:52.980 --> 06:13:55.250 align:start position:0% is called segments when we get to layer 5<06:13:53.160> or<06:13:53.580> the<06:13:53.700> session<06:13:53.940> layer<06:13:54.420> we<06:13:54.780> see<06:13:54.900> that<06:13:55.138> we're 06:13:55.250 --> 06:13:55.260 align:start position:0% 5 or the session layer we see that we're 06:13:55.260 --> 06:13:57.590 align:start position:0% 5 or the session layer we see that we're really<06:13:55.500> establishing<06:13:56.218> and<06:13:56.458> maintaining<06:13:57.120> a 06:13:57.590 --> 06:13:57.600 align:start position:0% really establishing and maintaining a 06:13:57.600 --> 06:14:03.110 align:start position:0% really establishing and maintaining a session 06:14:03.110 --> 06:14:03.120 align:start position:0% 06:14:03.120 --> 06:14:04.970 align:start position:0% this<06:14:03.600> is<06:14:03.718> where<06:14:03.900> we're<06:14:04.080> going<06:14:04.200> to<06:14:04.320> start<06:14:04.558> and 06:14:04.970 --> 06:14:04.980 align:start position:0% this is where we're going to start and 06:14:04.980 --> 06:14:07.970 align:start position:0% this is where we're going to start and gracefully<06:14:05.520> end<06:14:05.878> our<06:14:06.360> Communications<06:14:06.980> such 06:14:07.970 --> 06:14:07.980 align:start position:0% gracefully end our Communications such 06:14:07.980 --> 06:14:11.090 align:start position:0% gracefully end our Communications such as<06:14:08.160> SSL<06:14:09.058> Communications<06:14:09.740> when<06:14:10.740> we<06:14:10.860> get<06:14:10.980> to 06:14:11.090 --> 06:14:11.100 align:start position:0% as SSL Communications when we get to 06:14:11.100 --> 06:14:16.190 align:start position:0% as SSL Communications when we get to layer<06:14:11.458> 6<06:14:11.700> this<06:14:12.360> is<06:14:12.480> where<06:14:12.780> encryption 06:14:16.190 --> 06:14:16.200 align:start position:0% 06:14:16.200 --> 06:14:22.730 align:start position:0% and<06:14:17.160> compression<06:14:17.760> occur 06:14:22.730 --> 06:14:22.740 align:start position:0% 06:14:22.740 --> 06:14:24.590 align:start position:0% this<06:14:23.100> is<06:14:23.280> also<06:14:23.520> where<06:14:23.638> we<06:14:23.820> start<06:14:24.000> seeing<06:14:24.360> the 06:14:24.590 --> 06:14:24.600 align:start position:0% this is also where we start seeing the 06:14:24.600 --> 06:14:25.430 align:start position:0% this is also where we start seeing the term 06:14:25.430 --> 06:14:25.440 align:start position:0% term 06:14:25.440 --> 06:14:27.350 align:start position:0% term data 06:14:27.350 --> 06:14:27.360 align:start position:0% data 06:14:27.360 --> 06:14:30.048 align:start position:0% data finally<06:14:28.320> we<06:14:28.680> talked<06:14:28.920> about<06:14:28.980> the<06:14:29.400> application 06:14:30.048 --> 06:14:30.058 align:start position:0% finally we talked about the application 06:14:30.058 --> 06:14:32.030 align:start position:0% finally we talked about the application layer 06:14:32.030 --> 06:14:32.040 align:start position:0% layer 06:14:32.040 --> 06:14:34.610 align:start position:0% layer or<06:14:32.458> layer<06:14:32.878> seven<06:14:33.058> this<06:14:33.840> is<06:14:33.958> the<06:14:34.138> layer<06:14:34.378> that's 06:14:34.610 --> 06:14:34.620 align:start position:0% or layer seven this is the layer that's 06:14:34.620 --> 06:14:38.090 align:start position:0% or layer seven this is the layer that's closest<06:14:35.160> to<06:14:35.760> the<06:14:36.240> user 06:14:38.090 --> 06:14:38.100 align:start position:0% closest to the user 06:14:38.100 --> 06:14:39.590 align:start position:0% closest to the user and<06:14:38.458> this<06:14:38.580> is<06:14:38.700> where<06:14:38.940> you're<06:14:39.120> really<06:14:39.298> going<06:14:39.480> to 06:14:39.590 --> 06:14:39.600 align:start position:0% and this is where you're really going to 06:14:39.600 --> 06:14:41.690 align:start position:0% and this is where you're really going to see<06:14:39.780> the<06:14:40.020> interaction<06:14:40.500> this<06:14:41.100> is<06:14:41.280> where<06:14:41.400> we<06:14:41.520> saw 06:14:41.690 --> 06:14:41.700 align:start position:0% see the interaction this is where we saw 06:14:41.700 --> 06:14:46.190 align:start position:0% see the interaction this is where we saw a<06:14:41.878> lot<06:14:42.000> of<06:14:42.120> the<06:14:42.240> stuff<06:14:42.680> such<06:14:43.680> as<06:14:43.920> SMTP 06:14:46.190 --> 06:14:46.200 align:start position:0% a lot of the stuff such as SMTP 06:14:46.200 --> 06:14:49.270 align:start position:0% a lot of the stuff such as SMTP FTP 06:14:49.270 --> 06:14:49.280 align:start position:0% 06:14:49.280 --> 06:14:51.530 align:start position:0% HTTP<06:14:50.280> and<06:14:50.580> so<06:14:50.820> on 06:14:51.530 --> 06:14:51.540 align:start position:0% HTTP and so on 06:14:51.540 --> 06:14:53.930 align:start position:0% HTTP and so on this<06:14:52.080> really<06:14:52.260> governs<06:14:52.740> everything<06:14:53.160> so<06:14:53.700> if<06:14:53.820> we 06:14:53.930 --> 06:14:53.940 align:start position:0% this really governs everything so if we 06:14:53.940 --> 06:14:55.310 align:start position:0% this really governs everything so if we go<06:14:54.058> back<06:14:54.180> through<06:14:54.420> this<06:14:54.600> with<06:14:54.840> our<06:14:54.958> metaphor 06:14:55.310 --> 06:14:55.320 align:start position:0% go back through this with our metaphor 06:14:55.320 --> 06:14:57.230 align:start position:0% go back through this with our metaphor remember<06:14:55.500> the<06:14:55.798> physical<06:14:55.980> layer<06:14:56.580> are<06:14:57.058> the 06:14:57.230 --> 06:14:57.240 align:start position:0% remember the physical layer are the 06:14:57.240 --> 06:15:00.288 align:start position:0% remember the physical layer are the highways 06:15:00.288 --> 06:15:00.298 align:start position:0% 06:15:00.298 --> 06:15:02.030 align:start position:0% the<06:15:00.660> date<06:15:00.780> of<06:15:00.958> the<06:15:01.080> link<06:15:01.260> layer<06:15:01.558> or<06:15:01.680> how<06:15:01.860> we're 06:15:02.030 --> 06:15:02.040 align:start position:0% the date of the link layer or how we're 06:15:02.040 --> 06:15:05.570 align:start position:0% the date of the link layer or how we're going<06:15:02.160> to<06:15:02.340> share<06:15:02.638> the<06:15:03.360> roads 06:15:05.570 --> 06:15:05.580 align:start position:0% going to share the roads 06:15:05.580 --> 06:15:09.110 align:start position:0% going to share the roads remember<06:15:05.878> we<06:15:06.240> thought<06:15:06.540> about<06:15:06.900> a<06:15:07.260> stop<06:15:07.620> light 06:15:09.110 --> 06:15:09.120 align:start position:0% remember we thought about a stop light 06:15:09.120 --> 06:15:11.270 align:start position:0% remember we thought about a stop light the<06:15:09.600> network<06:15:09.840> layer<06:15:10.378> is<06:15:10.860> where<06:15:10.980> we<06:15:11.160> start 06:15:11.270 --> 06:15:11.280 align:start position:0% the network layer is where we start 06:15:11.280 --> 06:15:13.610 align:start position:0% the network layer is where we start determining<06:15:11.878> the<06:15:12.298> best<06:15:12.480> route<06:15:12.840> to<06:15:13.260> get<06:15:13.320> from 06:15:13.610 --> 06:15:13.620 align:start position:0% determining the best route to get from 06:15:13.620 --> 06:15:15.890 align:start position:0% determining the best route to get from one<06:15:13.798> place<06:15:14.040> to<06:15:14.280> the<06:15:14.458> other 06:15:15.890 --> 06:15:15.900 align:start position:0% one place to the other 06:15:15.900 --> 06:15:17.930 align:start position:0% one place to the other the<06:15:16.320> transport<06:15:16.680> layer<06:15:17.100> tells<06:15:17.520> us<06:15:17.638> for 06:15:17.930 --> 06:15:17.940 align:start position:0% the transport layer tells us for 06:15:17.940 --> 06:15:22.128 align:start position:0% the transport layer tells us for instance<06:15:18.180> the<06:15:18.660> rules<06:15:19.020> of<06:15:19.200> the<06:15:19.440> road 06:15:22.128 --> 06:15:22.138 align:start position:0% 06:15:22.138 --> 06:15:24.830 align:start position:0% the<06:15:23.100> session<06:15:23.340> layer<06:15:23.820> is<06:15:24.298> what<06:15:24.540> type<06:15:24.718> of 06:15:24.830 --> 06:15:24.840 align:start position:0% the session layer is what type of 06:15:24.840 --> 06:15:28.548 align:start position:0% the session layer is what type of Highway<06:15:25.080> we<06:15:25.440> might<06:15:25.558> need<06:15:25.740> to<06:15:25.920> take 06:15:28.548 --> 06:15:28.558 align:start position:0% 06:15:28.558 --> 06:15:31.970 align:start position:0% for<06:15:29.040> instance<06:15:29.280> I<06:15:29.580> might<06:15:29.760> need<06:15:29.940> to<06:15:30.240> take<06:15:30.480> a 06:15:31.970 --> 06:15:31.980 align:start position:0% for instance I might need to take a 06:15:31.980 --> 06:15:34.788 align:start position:0% for instance I might need to take a um<06:15:32.040> a<06:15:32.638> special<06:15:33.360> private<06:15:33.900> Highway<06:15:34.080> if<06:15:34.440> I<06:15:34.620> have 06:15:34.788 --> 06:15:34.798 align:start position:0% um a special private Highway if I have 06:15:34.798 --> 06:15:37.250 align:start position:0% um a special private Highway if I have important<06:15:35.400> documents<06:15:36.000> the<06:15:36.718> presentation 06:15:37.250 --> 06:15:37.260 align:start position:0% important documents the presentation 06:15:37.260 --> 06:15:40.788 align:start position:0% important documents the presentation layer<06:15:37.740> is<06:15:38.340> like<06:15:38.638> the<06:15:39.000> bus<06:15:39.180> driver 06:15:40.788 --> 06:15:40.798 align:start position:0% layer is like the bus driver 06:15:40.798 --> 06:15:43.250 align:start position:0% layer is like the bus driver who<06:15:41.218> is<06:15:41.340> going<06:15:41.638> to<06:15:41.940> pack<06:15:42.120> up<06:15:42.360> our<06:15:42.600> bags<06:15:42.900> for<06:15:43.080> us 06:15:43.250 --> 06:15:43.260 align:start position:0% who is going to pack up our bags for us 06:15:43.260 --> 06:15:44.810 align:start position:0% who is going to pack up our bags for us and<06:15:43.440> also<06:15:43.740> communicate<06:15:44.280> and<06:15:44.458> make<06:15:44.638> sure<06:15:44.700> that 06:15:44.810 --> 06:15:44.820 align:start position:0% and also communicate and make sure that 06:15:44.820 --> 06:15:46.310 align:start position:0% and also communicate and make sure that we<06:15:45.000> know<06:15:45.058> where<06:15:45.240> we're<06:15:45.360> going<06:15:45.540> and<06:15:46.080> the 06:15:46.310 --> 06:15:46.320 align:start position:0% we know where we're going and the 06:15:46.320 --> 06:15:49.850 align:start position:0% we know where we're going and the application<06:15:46.680> layer<06:15:47.160> is<06:15:47.638> going<06:15:47.820> to<06:15:48.000> be<06:15:48.180> like 06:15:49.850 --> 06:15:49.860 align:start position:0% application layer is going to be like 06:15:49.860 --> 06:15:54.048 align:start position:0% application layer is going to be like the<06:15:50.520> bus<06:15:50.700> stop 06:15:54.048 --> 06:15:54.058 align:start position:0% 06:15:54.058 --> 06:15:57.288 align:start position:0% now<06:15:54.780> the<06:15:55.020> OSI<06:15:55.440> model<06:15:55.680> is<06:15:56.160> in<06:15:56.458> actuality<06:15:56.940> pretty 06:15:57.288 --> 06:15:57.298 align:start position:0% now the OSI model is in actuality pretty 06:15:57.298 --> 06:15:59.510 align:start position:0% now the OSI model is in actuality pretty obsolete<06:15:57.958> but<06:15:58.260> we<06:15:58.378> need<06:15:58.500> to<06:15:58.620> understand<06:15:58.860> the 06:15:59.510 --> 06:15:59.520 align:start position:0% obsolete but we need to understand the 06:15:59.520 --> 06:16:01.128 align:start position:0% obsolete but we need to understand the theory<06:15:59.820> behind<06:16:00.180> it<06:16:00.298> before<06:16:00.480> we<06:16:00.718> can<06:16:00.840> get<06:16:00.958> into 06:16:01.128 --> 06:16:01.138 align:start position:0% theory behind it before we can get into 06:16:01.138 --> 06:16:02.990 align:start position:0% theory behind it before we can get into something<06:16:01.378> that's<06:16:01.620> a<06:16:01.798> little<06:16:01.920> more 06:16:02.990 --> 06:16:03.000 align:start position:0% something that's a little more 06:16:03.000 --> 06:16:06.350 align:start position:0% something that's a little more um<06:16:03.120> uh<06:16:03.900> necessary<06:16:04.558> for<06:16:05.100> instance<06:16:05.280> the<06:16:05.520> tcpip 06:16:06.350 --> 06:16:06.360 align:start position:0% um uh necessary for instance the tcpip 06:16:06.360 --> 06:16:11.390 align:start position:0% um uh necessary for instance the tcpip layer<06:16:07.200> model 06:16:11.390 --> 06:16:11.400 align:start position:0% 06:16:11.400 --> 06:16:33.170 align:start position:0% [Music] 06:16:33.170 --> 06:16:33.180 align:start position:0% 06:16:33.180 --> 06:16:35.390 align:start position:0% Network<06:16:33.900> infrastructure<06:16:34.798> and<06:16:35.160> Design 06:16:35.390 --> 06:16:35.400 align:start position:0% Network infrastructure and Design 06:16:35.400 --> 06:16:39.708 align:start position:0% Network infrastructure and Design Network<06:16:36.360> models<06:16:37.020> the<06:16:37.440> TCP<06:16:37.920> model 06:16:39.708 --> 06:16:39.718 align:start position:0% Network models the TCP model 06:16:39.718 --> 06:16:41.868 align:start position:0% Network models the TCP model whereas<06:16:40.260> in<06:16:40.440> the<06:16:40.558> previous<06:16:40.680> module<06:16:41.400> we<06:16:41.638> talked 06:16:41.868 --> 06:16:41.878 align:start position:0% whereas in the previous module we talked 06:16:41.878 --> 06:16:44.628 align:start position:0% whereas in the previous module we talked about<06:16:41.940> the<06:16:42.240> OSI<06:16:42.660> model<06:16:42.958> A<06:16:43.558> mostly<06:16:43.920> theoretical 06:16:44.628 --> 06:16:44.638 align:start position:0% about the OSI model A mostly theoretical 06:16:44.638 --> 06:16:47.208 align:start position:0% about the OSI model A mostly theoretical model<06:16:44.940> that's<06:16:45.240> in<06:16:45.420> use<06:16:45.600> in<06:16:45.840> computer<06:16:46.020> networks 06:16:47.208 --> 06:16:47.218 align:start position:0% model that's in use in computer networks 06:16:47.218 --> 06:16:49.010 align:start position:0% model that's in use in computer networks in<06:16:47.638> this<06:16:47.700> module<06:16:48.058> we're<06:16:48.180> going<06:16:48.360> to<06:16:48.480> talk<06:16:48.718> about 06:16:49.010 --> 06:16:49.020 align:start position:0% in this module we're going to talk about 06:16:49.020 --> 06:16:50.750 align:start position:0% in this module we're going to talk about perhaps<06:16:49.440> what<06:16:49.740> is<06:16:49.860> considered<06:16:50.218> to<06:16:50.340> be<06:16:50.458> one<06:16:50.700> of 06:16:50.750 --> 06:16:50.760 align:start position:0% perhaps what is considered to be one of 06:16:50.760 --> 06:16:53.090 align:start position:0% perhaps what is considered to be one of the<06:16:50.940> most<06:16:51.120> common<06:16:51.420> or<06:16:52.020> at<06:16:52.558> least<06:16:52.740> the<06:16:52.920> most 06:16:53.090 --> 06:16:53.100 align:start position:0% the most common or at least the most 06:16:53.100 --> 06:16:55.970 align:start position:0% the most common or at least the most widely<06:16:53.458> used<06:16:53.638> model<06:16:53.878> the<06:16:54.180> TCP<06:16:54.660> model<06:16:55.200> now 06:16:55.970 --> 06:16:55.980 align:start position:0% widely used model the TCP model now 06:16:55.980 --> 06:16:57.830 align:start position:0% widely used model the TCP model now while<06:16:56.100> it's<06:16:56.218> important<06:16:56.580> that<06:16:56.820> we<06:16:57.120> memorize 06:16:57.830 --> 06:16:57.840 align:start position:0% while it's important that we memorize 06:16:57.840 --> 06:16:59.448 align:start position:0% while it's important that we memorize and<06:16:58.080> familiarize<06:16:58.500> ourselves<06:16:58.740> with<06:16:58.920> the<06:16:59.040> OSI 06:16:59.448 --> 06:16:59.458 align:start position:0% and familiarize ourselves with the OSI 06:16:59.458 --> 06:17:01.430 align:start position:0% and familiarize ourselves with the OSI model<06:16:59.700> it's<06:17:00.298> also<06:17:00.600> really<06:17:00.780> important<06:17:01.080> that<06:17:01.320> we 06:17:01.430 --> 06:17:01.440 align:start position:0% model it's also really important that we 06:17:01.440 --> 06:17:03.708 align:start position:0% model it's also really important that we understand<06:17:01.558> this<06:17:01.920> TCP<06:17:02.458> model<06:17:03.000> and<06:17:03.540> the 06:17:03.708 --> 06:17:03.718 align:start position:0% understand this TCP model and the 06:17:03.718 --> 06:17:07.190 align:start position:0% understand this TCP model and the differences<06:17:04.138> between<06:17:04.860> it<06:17:05.280> and<06:17:05.760> the<06:17:05.878> OSI<06:17:06.298> model 06:17:07.190 --> 06:17:07.200 align:start position:0% differences between it and the OSI model 06:17:07.200 --> 06:17:09.890 align:start position:0% differences between it and the OSI model as<06:17:07.740> technicians<06:17:08.458> and<06:17:08.638> administrators<06:17:09.360> it's 06:17:09.890 --> 06:17:09.900 align:start position:0% as technicians and administrators it's 06:17:09.900 --> 06:17:11.690 align:start position:0% as technicians and administrators it's really<06:17:10.260> important<06:17:10.740> that<06:17:11.280> we're<06:17:11.400> familiar 06:17:11.690 --> 06:17:11.700 align:start position:0% really important that we're familiar 06:17:11.700 --> 06:17:14.208 align:start position:0% really important that we're familiar with<06:17:11.820> each<06:17:12.058> layer<06:17:12.420> as<06:17:12.780> well<06:17:12.958> as<06:17:13.080> how<06:17:13.620> a<06:17:13.860> data 06:17:14.208 --> 06:17:14.218 align:start position:0% with each layer as well as how a data 06:17:14.218 --> 06:17:16.448 align:start position:0% with each layer as well as how a data transfers<06:17:14.638> between<06:17:15.120> all<06:17:15.840> of<06:17:15.958> these<06:17:16.138> layers 06:17:16.448 --> 06:17:16.458 align:start position:0% transfers between all of these layers 06:17:16.458 --> 06:17:19.070 align:start position:0% transfers between all of these layers and<06:17:17.458> how<06:17:17.700> all<06:17:17.878> the<06:17:18.058> protocols<06:17:18.600> that<06:17:18.840> are<06:17:18.958> used 06:17:19.070 --> 06:17:19.080 align:start position:0% and how all the protocols that are used 06:17:19.080 --> 06:17:22.070 align:start position:0% and how all the protocols that are used in<06:17:19.320> TCP<06:17:19.798> relate<06:17:20.340> to<06:17:20.458> one<06:17:20.638> another<06:17:20.820> and<06:17:21.718> in<06:17:21.900> the 06:17:22.070 --> 06:17:22.080 align:start position:0% in TCP relate to one another and in the 06:17:22.080 --> 06:17:23.150 align:start position:0% in TCP relate to one another and in the layers 06:17:23.150 --> 06:17:23.160 align:start position:0% layers 06:17:23.160 --> 06:17:24.288 align:start position:0% layers so 06:17:24.288 --> 06:17:24.298 align:start position:0% so 06:17:24.298 --> 06:17:26.570 align:start position:0% so the<06:17:24.718> objective<06:17:25.020> of<06:17:25.200> this<06:17:25.320> module<06:17:25.680> are<06:17:26.340> first 06:17:26.570 --> 06:17:26.580 align:start position:0% the objective of this module are first 06:17:26.580 --> 06:17:28.490 align:start position:0% the objective of this module are first to<06:17:26.820> explain<06:17:27.000> the<06:17:27.420> purpose<06:17:27.718> and<06:17:27.958> depth<06:17:28.260> of<06:17:28.378> the 06:17:28.490 --> 06:17:28.500 align:start position:0% to explain the purpose and depth of the 06:17:28.500 --> 06:17:31.910 align:start position:0% to explain the purpose and depth of the TCP<06:17:28.920> model<06:17:29.580> and<06:17:30.420> to<06:17:30.660> compare<06:17:31.080> it<06:17:31.260> in<06:17:31.558> some<06:17:31.680> ways 06:17:31.910 --> 06:17:31.920 align:start position:0% TCP model and to compare it in some ways 06:17:31.920 --> 06:17:34.190 align:start position:0% TCP model and to compare it in some ways with<06:17:32.100> the<06:17:32.218> OSI<06:17:32.638> model<06:17:32.940> we're<06:17:33.718> also<06:17:33.958> going<06:17:34.080> to 06:17:34.190 --> 06:17:34.200 align:start position:0% with the OSI model we're also going to 06:17:34.200 --> 06:17:36.770 align:start position:0% with the OSI model we're also going to talk<06:17:34.378> about<06:17:34.680> what<06:17:35.040> data<06:17:35.400> encapsulation<06:17:36.180> and 06:17:36.770 --> 06:17:36.780 align:start position:0% talk about what data encapsulation and 06:17:36.780 --> 06:17:38.868 align:start position:0% talk about what data encapsulation and fragmentation<06:17:37.378> are<06:17:37.680> these<06:17:38.280> are<06:17:38.400> really<06:17:38.638> key 06:17:38.868 --> 06:17:38.878 align:start position:0% fragmentation are these are really key 06:17:38.878 --> 06:17:41.690 align:start position:0% fragmentation are these are really key to<06:17:39.298> how<06:17:39.660> large<06:17:40.200> amounts<06:17:40.680> of<06:17:40.798> data<06:17:41.160> are<06:17:41.340> able<06:17:41.580> to 06:17:41.690 --> 06:17:41.700 align:start position:0% to how large amounts of data are able to 06:17:41.700 --> 06:17:44.270 align:start position:0% to how large amounts of data are able to be<06:17:42.020> transmitted<06:17:43.020> and<06:17:43.200> transferred<06:17:43.740> over<06:17:43.860> the 06:17:44.270 --> 06:17:44.280 align:start position:0% be transmitted and transferred over the 06:17:44.280 --> 06:17:46.610 align:start position:0% be transmitted and transferred over the Internet<06:17:44.480> the<06:17:45.480> largest<06:17:45.780> Network<06:17:46.080> in<06:17:46.500> the 06:17:46.610 --> 06:17:46.620 align:start position:0% Internet the largest Network in the 06:17:46.620 --> 06:17:47.330 align:start position:0% Internet the largest Network in the world 06:17:47.330 --> 06:17:47.340 align:start position:0% world 06:17:47.340 --> 06:17:49.010 align:start position:0% world and<06:17:47.760> then<06:17:47.878> we're<06:17:48.000> going<06:17:48.120> to<06:17:48.180> talk<06:17:48.420> about<06:17:48.718> the 06:17:49.010 --> 06:17:49.020 align:start position:0% and then we're going to talk about the 06:17:49.020 --> 06:17:51.530 align:start position:0% and then we're going to talk about the four<06:17:49.138> layers<06:17:49.500> of<06:17:49.680> the<06:17:49.860> tcpip<06:17:50.580> model<06:17:51.000> beginning 06:17:51.530 --> 06:17:51.540 align:start position:0% four layers of the tcpip model beginning 06:17:51.540 --> 06:17:53.448 align:start position:0% four layers of the tcpip model beginning with<06:17:51.900> the<06:17:52.080> fourth<06:17:52.320> one<06:17:52.440> and<06:17:52.980> then<06:17:53.040> the<06:17:53.280> third 06:17:53.448 --> 06:17:53.458 align:start position:0% with the fourth one and then the third 06:17:53.458 --> 06:17:56.090 align:start position:0% with the fourth one and then the third the<06:17:54.120> second<06:17:54.298> and<06:17:55.020> the<06:17:55.200> first 06:17:56.090 --> 06:17:56.100 align:start position:0% the second and the first 06:17:56.100 --> 06:17:57.830 align:start position:0% the second and the first finally<06:17:56.700> we're<06:17:57.058> going<06:17:57.240> to<06:17:57.360> talk<06:17:57.540> about 06:17:57.830 --> 06:17:57.840 align:start position:0% finally we're going to talk about 06:17:57.840 --> 06:18:00.708 align:start position:0% finally we're going to talk about protocol<06:17:58.558> binding<06:17:59.458> and<06:17:59.940> something<06:18:00.180> called<06:18:00.480> an 06:18:00.708 --> 06:18:00.718 align:start position:0% protocol binding and something called an 06:18:00.718 --> 06:18:03.410 align:start position:0% protocol binding and something called an MTU<06:18:01.260> black<06:18:01.620> hole<06:18:02.100> that<06:18:02.638> doesn't<06:18:02.820> really<06:18:03.120> occur 06:18:03.410 --> 06:18:03.420 align:start position:0% MTU black hole that doesn't really occur 06:18:03.420 --> 06:18:05.330 align:start position:0% MTU black hole that doesn't really occur much<06:18:03.600> anymore<06:18:03.780> but<06:18:04.200> that<06:18:04.378> Network<06:18:04.558> plus<06:18:04.860> wants 06:18:05.330 --> 06:18:05.340 align:start position:0% much anymore but that Network plus wants 06:18:05.340 --> 06:18:06.890 align:start position:0% much anymore but that Network plus wants you<06:18:05.400> to<06:18:05.520> be<06:18:05.638> familiar<06:18:06.058> with 06:18:06.890 --> 06:18:06.900 align:start position:0% you to be familiar with 06:18:06.900 --> 06:18:09.650 align:start position:0% you to be familiar with so<06:18:07.320> as<06:18:07.620> mentioned<06:18:07.920> before<06:18:08.100> the<06:18:08.580> tcpap<06:18:09.240> model 06:18:09.650 --> 06:18:09.660 align:start position:0% so as mentioned before the tcpap model 06:18:09.660 --> 06:18:12.350 align:start position:0% so as mentioned before the tcpap model is<06:18:09.958> perhaps<06:18:10.680> the<06:18:10.920> most<06:18:11.100> widely<06:18:11.520> known<06:18:11.820> or<06:18:12.120> used 06:18:12.350 --> 06:18:12.360 align:start position:0% is perhaps the most widely known or used 06:18:12.360 --> 06:18:14.868 align:start position:0% is perhaps the most widely known or used networking<06:18:13.020> model<06:18:13.260> it's<06:18:14.218> uh<06:18:14.580> another 06:18:14.868 --> 06:18:14.878 align:start position:0% networking model it's uh another 06:18:14.878 --> 06:18:17.150 align:start position:0% networking model it's uh another networking<06:18:15.718> model<06:18:15.958> that's<06:18:16.320> most<06:18:16.680> commonly 06:18:17.150 --> 06:18:17.160 align:start position:0% networking model that's most commonly 06:18:17.160 --> 06:18:20.330 align:start position:0% networking model that's most commonly defined<06:18:17.760> using<06:18:18.540> abstract<06:18:19.440> layers<06:18:19.860> just<06:18:20.160> like 06:18:20.330 --> 06:18:20.340 align:start position:0% defined using abstract layers just like 06:18:20.340 --> 06:18:22.610 align:start position:0% defined using abstract layers just like we<06:18:20.580> had<06:18:20.700> with<06:18:20.940> the<06:18:21.058> OSI<06:18:21.480> model<06:18:21.718> and<06:18:22.260> the<06:18:22.440> entire 06:18:22.610 --> 06:18:22.620 align:start position:0% we had with the OSI model and the entire 06:18:22.620 --> 06:18:24.430 align:start position:0% we had with the OSI model and the entire purpose<06:18:22.920> of<06:18:23.100> this<06:18:23.280> model<06:18:23.400> is<06:18:23.700> to<06:18:23.878> allow<06:18:24.120> for 06:18:24.430 --> 06:18:24.440 align:start position:0% purpose of this model is to allow for 06:18:24.440 --> 06:18:26.930 align:start position:0% purpose of this model is to allow for conceptualization<06:18:25.440> of<06:18:26.340> how<06:18:26.580> a<06:18:26.760> computer 06:18:26.930 --> 06:18:26.940 align:start position:0% conceptualization of how a computer 06:18:26.940 --> 06:18:29.390 align:start position:0% conceptualization of how a computer network<06:18:27.360> functions<06:18:28.200> in<06:18:28.860> maintaining 06:18:29.390 --> 06:18:29.400 align:start position:0% network functions in maintaining 06:18:29.400 --> 06:18:32.868 align:start position:0% network functions in maintaining hardware<06:18:29.878> and<06:18:30.660> protocol<06:18:31.020> interoperability 06:18:32.868 --> 06:18:32.878 align:start position:0% hardware and protocol interoperability 06:18:32.878 --> 06:18:38.150 align:start position:0% hardware and protocol interoperability also<06:18:33.718> it's<06:18:33.900> commonly<06:18:34.378> called<06:18:34.820> the<06:18:35.820> dod<06:18:36.600> model 06:18:38.150 --> 06:18:38.160 align:start position:0% also it's commonly called the dod model 06:18:38.160 --> 06:18:40.730 align:start position:0% also it's commonly called the dod model for<06:18:38.820> the<06:18:39.058> Department<06:18:39.420> of<06:18:39.840> Defense<06:18:40.260> which 06:18:40.730 --> 06:18:40.740 align:start position:0% for the Department of Defense which 06:18:40.740 --> 06:18:43.070 align:start position:0% for the Department of Defense which funded<06:18:41.280> much<06:18:42.000> of<06:18:42.180> the<06:18:42.360> research<06:18:42.718> that<06:18:42.900> went 06:18:43.070 --> 06:18:43.080 align:start position:0% funded much of the research that went 06:18:43.080 --> 06:18:47.350 align:start position:0% funded much of the research that went into<06:18:43.320> it<06:18:43.700> uh<06:18:44.700> TCP<06:18:45.240> was<06:18:45.780> permanently<06:18:46.440> uh 06:18:47.350 --> 06:18:47.360 align:start position:0% into it uh TCP was permanently uh 06:18:47.360 --> 06:18:51.788 align:start position:0% into it uh TCP was permanently uh activated<06:18:48.360> in<06:18:48.740> 1983<06:18:49.740> and<06:18:50.580> it's<06:18:50.760> been<06:18:51.000> in<06:18:51.240> use 06:18:51.788 --> 06:18:51.798 align:start position:0% activated in 1983 and it's been in use 06:18:51.798 --> 06:18:54.530 align:start position:0% activated in 1983 and it's been in use just<06:18:52.798> about<06:18:52.980> ever<06:18:53.280> since 06:18:54.530 --> 06:18:54.540 align:start position:0% just about ever since 06:18:54.540 --> 06:18:57.110 align:start position:0% just about ever since that<06:18:54.840> wasn't<06:18:55.080> until<06:18:55.260> 1985<06:18:56.100> this<06:18:56.638> model<06:18:56.878> was 06:18:57.110 --> 06:18:57.120 align:start position:0% that wasn't until 1985 this model was 06:18:57.120 --> 06:18:59.750 align:start position:0% that wasn't until 1985 this model was actually<06:18:57.360> commercially<06:18:57.900> marketed<06:18:58.558> but<06:18:59.458> it<06:18:59.638> is 06:18:59.750 --> 06:18:59.760 align:start position:0% actually commercially marketed but it is 06:18:59.760 --> 06:19:03.470 align:start position:0% actually commercially marketed but it is now<06:18:59.878> the<06:19:00.240> preferred<06:19:00.920> network<06:19:01.920> standard<06:19:02.760> for 06:19:03.470 --> 06:19:03.480 align:start position:0% now the preferred network standard for 06:19:03.480 --> 06:19:05.270 align:start position:0% now the preferred network standard for protocols<06:19:04.080> and<06:19:04.260> so<06:19:04.440> on 06:19:05.270 --> 06:19:05.280 align:start position:0% protocols and so on 06:19:05.280 --> 06:19:08.750 align:start position:0% protocols and so on now<06:19:05.940> this<06:19:06.900> means<06:19:07.320> that<06:19:07.680> using<06:19:08.100> these<06:19:08.520> four 06:19:08.750 --> 06:19:08.760 align:start position:0% now this means that using these four 06:19:08.760 --> 06:19:10.670 align:start position:0% now this means that using these four layers<06:19:09.120> on<06:19:09.298> this<06:19:09.480> model<06:19:09.660> the<06:19:10.260> bottom<06:19:10.500> being 06:19:10.670 --> 06:19:10.680 align:start position:0% layers on this model the bottom being 06:19:10.680 --> 06:19:12.890 align:start position:0% layers on this model the bottom being the<06:19:10.980> network<06:19:11.100> interface<06:19:11.638> layer<06:19:12.000> the<06:19:12.780> internet 06:19:12.890 --> 06:19:12.900 align:start position:0% the network interface layer the internet 06:19:12.900 --> 06:19:15.410 align:start position:0% the network interface layer the internet layer<06:19:13.440> the<06:19:14.218> transport<06:19:14.520> layer<06:19:14.940> and<06:19:15.298> then 06:19:15.410 --> 06:19:15.420 align:start position:0% layer the transport layer and then 06:19:15.420 --> 06:19:17.868 align:start position:0% layer the transport layer and then finally<06:19:15.718> the<06:19:15.900> application<06:19:16.320> layer<06:19:16.740> and<06:19:17.340> if<06:19:17.638> you 06:19:17.868 --> 06:19:17.878 align:start position:0% finally the application layer and if you 06:19:17.878 --> 06:19:19.788 align:start position:0% finally the application layer and if you know<06:19:18.240> or<06:19:18.480> remember<06:19:18.660> the<06:19:18.900> OSI<06:19:19.320> model<06:19:19.500> you'll 06:19:19.788 --> 06:19:19.798 align:start position:0% know or remember the OSI model you'll 06:19:19.798 --> 06:19:22.010 align:start position:0% know or remember the OSI model you'll see<06:19:19.920> that<06:19:20.100> there<06:19:20.280> is<06:19:20.400> some<06:19:20.638> resemblance<06:19:21.240> uh 06:19:22.010 --> 06:19:22.020 align:start position:0% see that there is some resemblance uh 06:19:22.020 --> 06:19:24.770 align:start position:0% see that there is some resemblance uh these<06:19:22.620> understanding<06:19:23.218> these<06:19:23.580> this<06:19:24.240> model<06:19:24.540> and 06:19:24.770 --> 06:19:24.780 align:start position:0% these understanding these this model and 06:19:24.780 --> 06:19:26.930 align:start position:0% these understanding these this model and understanding<06:19:25.260> how<06:19:25.558> data<06:19:25.920> flows<06:19:26.280> is<06:19:26.760> actually 06:19:26.930 --> 06:19:26.940 align:start position:0% understanding how data flows is actually 06:19:26.940 --> 06:19:29.390 align:start position:0% understanding how data flows is actually how<06:19:27.298> the<06:19:27.600> entire<06:19:28.020> world<06:19:28.500> is<06:19:28.920> allowed<06:19:29.280> to 06:19:29.390 --> 06:19:29.400 align:start position:0% how the entire world is allowed to 06:19:29.400 --> 06:19:30.948 align:start position:0% how the entire world is allowed to communicate<06:19:29.940> and<06:19:30.180> connect<06:19:30.420> to<06:19:30.660> the<06:19:30.840> network 06:19:30.948 --> 06:19:30.958 align:start position:0% communicate and connect to the network 06:19:30.958 --> 06:19:34.128 align:start position:0% communicate and connect to the network so<06:19:31.680> this<06:19:31.860> is<06:19:32.040> necessary<06:19:32.700> for<06:19:33.420> every<06:19:33.780> computer 06:19:34.128 --> 06:19:34.138 align:start position:0% so this is necessary for every computer 06:19:34.138 --> 06:19:36.650 align:start position:0% so this is necessary for every computer in<06:19:34.980> the<06:19:35.100> world<06:19:35.280> that<06:19:35.638> is<06:19:35.820> currently<06:19:36.120> using<06:19:36.480> the 06:19:36.650 --> 06:19:36.660 align:start position:0% in the world that is currently using the 06:19:36.660 --> 06:19:38.510 align:start position:0% in the world that is currently using the internet<06:19:36.840> and<06:19:37.440> for<06:19:37.558> the<06:19:37.680> most<06:19:37.798> part<06:19:37.980> that's<06:19:38.218> on 06:19:38.510 --> 06:19:38.520 align:start position:0% internet and for the most part that's on 06:19:38.520 --> 06:19:41.448 align:start position:0% internet and for the most part that's on any<06:19:38.760> network<06:19:39.000> we<06:19:39.718> might<06:19:39.900> find<06:19:40.138> other<06:19:40.620> smaller 06:19:41.448 --> 06:19:41.458 align:start position:0% any network we might find other smaller 06:19:41.458 --> 06:19:43.490 align:start position:0% any network we might find other smaller lesser<06:19:41.820> known<06:19:42.058> protocols<06:19:42.718> that<06:19:42.900> do<06:19:43.020> operate 06:19:43.490 --> 06:19:43.500 align:start position:0% lesser known protocols that do operate 06:19:43.500 --> 06:19:45.948 align:start position:0% lesser known protocols that do operate outside<06:19:44.100> of<06:19:44.400> this<06:19:44.520> but<06:19:45.120> I<06:19:45.480> think<06:19:45.540> you<06:19:45.660> would<06:19:45.840> be 06:19:45.948 --> 06:19:45.958 align:start position:0% outside of this but I think you would be 06:19:45.958 --> 06:19:47.930 align:start position:0% outside of this but I think you would be hard-pressed<06:19:46.680> in<06:19:46.920> today's<06:19:47.040> day<06:19:47.340> and<06:19:47.458> age<06:19:47.638> to 06:19:47.930 --> 06:19:47.940 align:start position:0% hard-pressed in today's day and age to 06:19:47.940 --> 06:19:48.890 align:start position:0% hard-pressed in today's day and age to see<06:19:48.058> that 06:19:48.890 --> 06:19:48.900 align:start position:0% see that 06:19:48.900 --> 06:19:51.770 align:start position:0% see that so<06:19:49.500> technicians<06:19:50.218> and<06:19:50.400> Engineers<06:19:50.878> will 06:19:51.770 --> 06:19:51.780 align:start position:0% so technicians and Engineers will 06:19:51.780 --> 06:19:53.628 align:start position:0% so technicians and Engineers will probably<06:19:51.958> sit<06:19:52.378> and<06:19:52.620> talk<06:19:52.798> about<06:19:53.040> Technology's 06:19:53.628 --> 06:19:53.638 align:start position:0% probably sit and talk about Technology's 06:19:53.638 --> 06:19:55.548 align:start position:0% probably sit and talk about Technology's implementation<06:19:54.360> of<06:19:54.660> these<06:19:54.840> two<06:19:54.958> models<06:19:55.320> for 06:19:55.548 --> 06:19:55.558 align:start position:0% implementation of these two models for 06:19:55.558 --> 06:19:57.770 align:start position:0% implementation of these two models for hours<06:19:55.798> on<06:19:56.160> end<06:19:56.340> and<06:19:57.120> the<06:19:57.240> reason<06:19:57.360> is<06:19:57.600> because 06:19:57.770 --> 06:19:57.780 align:start position:0% hours on end and the reason is because 06:19:57.780 --> 06:19:59.030 align:start position:0% hours on end and the reason is because there's<06:19:58.020> quite<06:19:58.200> a<06:19:58.320> bit<06:19:58.440> of<06:19:58.558> history<06:19:58.740> and 06:19:59.030 --> 06:19:59.040 align:start position:0% there's quite a bit of history and 06:19:59.040 --> 06:20:00.410 align:start position:0% there's quite a bit of history and Brilliant<06:19:59.400> thinking<06:19:59.700> that<06:19:59.878> went<06:20:00.000> into<06:20:00.180> the 06:20:00.410 --> 06:20:00.420 align:start position:0% Brilliant thinking that went into the 06:20:00.420 --> 06:20:03.410 align:start position:0% Brilliant thinking that went into the creation<06:20:00.718> of<06:20:00.958> both<06:20:01.080> of<06:20:01.260> them<06:20:01.440> the<06:20:02.340> tcpap<06:20:03.000> model 06:20:03.410 --> 06:20:03.420 align:start position:0% creation of both of them the tcpap model 06:20:03.420 --> 06:20:06.048 align:start position:0% creation of both of them the tcpap model was<06:20:03.840> in<06:20:04.138> fact<06:20:04.378> created<06:20:04.798> before<06:20:05.100> the<06:20:05.400> OSI<06:20:05.820> model 06:20:06.048 --> 06:20:06.058 align:start position:0% was in fact created before the OSI model 06:20:06.058 --> 06:20:08.150 align:start position:0% was in fact created before the OSI model and<06:20:06.958> it<06:20:07.138> still<06:20:07.260> makes<06:20:07.440> it<06:20:07.620> easier<06:20:07.920> to 06:20:08.150 --> 06:20:08.160 align:start position:0% and it still makes it easier to 06:20:08.160 --> 06:20:09.890 align:start position:0% and it still makes it easier to represent<06:20:08.520> how<06:20:08.820> communication<06:20:09.420> and<06:20:09.660> network 06:20:09.890 --> 06:20:09.900 align:start position:0% represent how communication and network 06:20:09.900 --> 06:20:12.470 align:start position:0% represent how communication and network related<06:20:10.740> Protocols<06:20:11.458> are<06:20:11.700> defined<06:20:12.058> and<06:20:12.180> relate 06:20:12.470 --> 06:20:12.480 align:start position:0% related Protocols are defined and relate 06:20:12.480 --> 06:20:14.868 align:start position:0% related Protocols are defined and relate to<06:20:12.600> one<06:20:12.780> another<06:20:12.920> however<06:20:13.920> it's<06:20:14.400> still<06:20:14.580> more 06:20:14.868 --> 06:20:14.878 align:start position:0% to one another however it's still more 06:20:14.878 --> 06:20:16.128 align:start position:0% to one another however it's still more common<06:20:15.058> to<06:20:15.298> hear<06:20:15.420> technicians<06:20:15.958> and 06:20:16.128 --> 06:20:16.138 align:start position:0% common to hear technicians and 06:20:16.138 --> 06:20:18.170 align:start position:0% common to hear technicians and administrators<06:20:16.680> use<06:20:16.920> the<06:20:17.218> OSI<06:20:17.700> model<06:20:17.940> when 06:20:18.170 --> 06:20:18.180 align:start position:0% administrators use the OSI model when 06:20:18.180 --> 06:20:19.730 align:start position:0% administrators use the OSI model when they're<06:20:18.360> troubleshooting<06:20:18.958> or<06:20:19.138> referencing 06:20:19.730 --> 06:20:19.740 align:start position:0% they're troubleshooting or referencing 06:20:19.740 --> 06:20:22.310 align:start position:0% they're troubleshooting or referencing networking<06:20:20.520> devices<06:20:20.878> and<06:20:21.718> there<06:20:21.958> are<06:20:22.138> many 06:20:22.310 --> 06:20:22.320 align:start position:0% networking devices and there are many 06:20:22.320 --> 06:20:25.310 align:start position:0% networking devices and there are many similarities<06:20:23.218> between<06:20:23.760> the<06:20:24.120> two<06:20:24.240> models<06:20:24.660> the 06:20:25.310 --> 06:20:25.320 align:start position:0% similarities between the two models the 06:20:25.320 --> 06:20:27.110 align:start position:0% similarities between the two models the first<06:20:25.440> similarity<06:20:25.980> is<06:20:26.100> the<06:20:26.340> obvious<06:20:26.580> use<06:20:26.820> of 06:20:27.110 --> 06:20:27.120 align:start position:0% first similarity is the obvious use of 06:20:27.120 --> 06:20:29.270 align:start position:0% first similarity is the obvious use of the<06:20:27.360> layers<06:20:27.718> to<06:20:28.260> describe<06:20:28.620> the<06:20:28.798> functions<06:20:29.160> of 06:20:29.270 --> 06:20:29.280 align:start position:0% the layers to describe the functions of 06:20:29.280 --> 06:20:31.250 align:start position:0% the layers to describe the functions of these<06:20:29.520> communication<06:20:30.058> systems<06:20:30.600> although<06:20:31.138> in 06:20:31.250 --> 06:20:31.260 align:start position:0% these communication systems although in 06:20:31.260 --> 06:20:34.490 align:start position:0% these communication systems although in tcpip<06:20:32.040> we<06:20:32.458> have<06:20:32.580> four<06:20:32.820> whereas<06:20:33.540> in<06:20:33.718> OSI<06:20:34.138> as<06:20:34.320> you 06:20:34.490 --> 06:20:34.500 align:start position:0% tcpip we have four whereas in OSI as you 06:20:34.500 --> 06:20:36.770 align:start position:0% tcpip we have four whereas in OSI as you recall<06:20:34.798> we<06:20:35.340> have<06:20:35.458> seven<06:20:35.760> some<06:20:36.420> of<06:20:36.540> them<06:20:36.600> even 06:20:36.770 --> 06:20:36.780 align:start position:0% recall we have seven some of them even 06:20:36.780 --> 06:20:40.910 align:start position:0% recall we have seven some of them even have<06:20:37.080> similar<06:20:37.558> names<06:20:37.860> as<06:20:38.580> you<06:20:38.760> can<06:20:38.878> see<06:20:39.120> uh 06:20:40.910 --> 06:20:40.920 align:start position:0% have similar names as you can see uh 06:20:40.920 --> 06:20:43.670 align:start position:0% have similar names as you can see uh from<06:20:41.638> application<06:20:42.240> and<06:20:42.660> transport<06:20:43.080> and<06:20:43.620> then 06:20:43.670 --> 06:20:43.680 align:start position:0% from application and transport and then 06:20:43.680 --> 06:20:46.070 align:start position:0% from application and transport and then we<06:20:43.860> see<06:20:43.980> network<06:20:44.280> or<06:20:44.760> Internet<06:20:45.058> and<06:20:45.840> network 06:20:46.070 --> 06:20:46.080 align:start position:0% we see network or Internet and network 06:20:46.080 --> 06:20:47.690 align:start position:0% we see network or Internet and network interface<06:20:46.620> which<06:20:46.920> is<06:20:47.040> very<06:20:47.280> much<06:20:47.458> like 06:20:47.690 --> 06:20:47.700 align:start position:0% interface which is very much like 06:20:47.700 --> 06:20:51.288 align:start position:0% interface which is very much like physical 06:20:51.288 --> 06:20:51.298 align:start position:0% 06:20:51.298 --> 06:20:53.150 align:start position:0% in<06:20:51.780> some<06:20:51.900> ways<06:20:52.138> some<06:20:52.378> people<06:20:52.558> consider<06:20:52.920> the 06:20:53.150 --> 06:20:53.160 align:start position:0% in some ways some people consider the 06:20:53.160 --> 06:20:56.150 align:start position:0% in some ways some people consider the TCP<06:20:53.638> model<06:20:54.120> to<06:20:54.420> be<06:20:54.600> a<06:20:55.138> smaller<06:20:55.440> version<06:20:55.680> of<06:20:56.040> The 06:20:56.150 --> 06:20:56.160 align:start position:0% TCP model to be a smaller version of The 06:20:56.160 --> 06:20:58.250 align:start position:0% TCP model to be a smaller version of The OSI<06:20:56.638> model<06:20:56.878> however<06:20:57.240> this<06:20:57.540> leads<06:20:58.020> to<06:20:58.080> some 06:20:58.250 --> 06:20:58.260 align:start position:0% OSI model however this leads to some 06:20:58.260 --> 06:21:00.650 align:start position:0% OSI model however this leads to some misconceptions<06:20:58.920> about<06:20:59.638> the<06:20:59.940> position<06:21:00.120> of 06:21:00.650 --> 06:21:00.660 align:start position:0% misconceptions about the position of 06:21:00.660 --> 06:21:02.208 align:start position:0% misconceptions about the position of relationships<06:21:01.260> of<06:21:01.440> certain<06:21:01.680> protocols 06:21:02.208 --> 06:21:02.218 align:start position:0% relationships of certain protocols 06:21:02.218 --> 06:21:04.368 align:start position:0% relationships of certain protocols within<06:21:02.580> the<06:21:02.700> OSI<06:21:03.058> model<06:21:03.298> because<06:21:03.958> these<06:21:04.260> are 06:21:04.368 --> 06:21:04.378 align:start position:0% within the OSI model because these are 06:21:04.378 --> 06:21:06.708 align:start position:0% within the OSI model because these are very<06:21:04.558> two<06:21:04.860> very<06:21:05.160> different<06:21:05.340> designs<06:21:06.058> and<06:21:06.540> they 06:21:06.708 --> 06:21:06.718 align:start position:0% very two very different designs and they 06:21:06.718 --> 06:21:09.170 align:start position:0% very two very different designs and they have<06:21:06.840> different<06:21:07.080> purposes<06:21:07.700> there<06:21:08.700> are<06:21:08.820> some 06:21:09.170 --> 06:21:09.180 align:start position:0% have different purposes there are some 06:21:09.180 --> 06:21:11.090 align:start position:0% have different purposes there are some recognizable<06:21:09.900> similarities<06:21:10.558> but<06:21:10.860> they're 06:21:11.090 --> 06:21:11.100 align:start position:0% recognizable similarities but they're 06:21:11.100 --> 06:21:13.490 align:start position:0% recognizable similarities but they're still<06:21:11.340> at<06:21:11.638> their<06:21:12.000> core<06:21:12.240> different<06:21:12.600> so<06:21:13.320> the 06:21:13.490 --> 06:21:13.500 align:start position:0% still at their core different so the 06:21:13.500 --> 06:21:15.708 align:start position:0% still at their core different so the purpose<06:21:13.740> of<06:21:13.980> this<06:21:14.100> OSI<06:21:14.520> model<06:21:14.760> was<06:21:15.120> an<06:21:15.420> attempt 06:21:15.708 --> 06:21:15.718 align:start position:0% purpose of this OSI model was an attempt 06:21:15.718 --> 06:21:19.090 align:start position:0% purpose of this OSI model was an attempt to<06:21:16.200> simplify<06:21:16.740> and<06:21:17.280> standardize<06:21:17.820> networking 06:21:19.090 --> 06:21:19.100 align:start position:0% to simplify and standardize networking 06:21:19.100 --> 06:21:21.470 align:start position:0% to simplify and standardize networking tcp's<06:21:20.100> original<06:21:20.400> purpose<06:21:20.878> as<06:21:21.058> opposed<06:21:21.360> to<06:21:21.360> the 06:21:21.470 --> 06:21:21.480 align:start position:0% tcp's original purpose as opposed to the 06:21:21.480 --> 06:21:25.010 align:start position:0% tcp's original purpose as opposed to the OSI<06:21:21.900> is<06:21:22.558> more<06:21:22.798> attempting<06:21:23.280> to<06:21:23.520> sort<06:21:23.700> of<06:21:24.020> uh 06:21:25.010 --> 06:21:25.020 align:start position:0% OSI is more attempting to sort of uh 06:21:25.020 --> 06:21:27.350 align:start position:0% OSI is more attempting to sort of uh sort<06:21:25.378> out<06:21:25.620> the<06:21:25.980> internet<06:21:26.160> protocols<06:21:27.058> into 06:21:27.350 --> 06:21:27.360 align:start position:0% sort out the internet protocols into 06:21:27.360 --> 06:21:29.628 align:start position:0% sort out the internet protocols into comprehensive<06:21:28.138> groups<06:21:28.740> according<06:21:29.400> to<06:21:29.520> their 06:21:29.628 --> 06:21:29.638 align:start position:0% comprehensive groups according to their 06:21:29.638 --> 06:21:32.090 align:start position:0% comprehensive groups according to their functions<06:21:30.120> of<06:21:30.360> the<06:21:30.660> scope<06:21:30.958> and<06:21:31.620> the<06:21:31.798> sort<06:21:31.920> of 06:21:32.090 --> 06:21:32.100 align:start position:0% functions of the scope and the sort of 06:21:32.100 --> 06:21:33.770 align:start position:0% functions of the scope and the sort of network<06:21:32.280> that's<06:21:32.700> involved 06:21:33.770 --> 06:21:33.780 align:start position:0% network that's involved 06:21:33.780 --> 06:21:36.230 align:start position:0% network that's involved now<06:21:34.378> one<06:21:34.680> of<06:21:34.798> the<06:21:34.920> similarities<06:21:35.520> between<06:21:35.940> the 06:21:36.230 --> 06:21:36.240 align:start position:0% now one of the similarities between the 06:21:36.240 --> 06:21:37.310 align:start position:0% now one of the similarities between the two<06:21:36.360> models<06:21:36.660> is<06:21:36.780> they<06:21:36.900> both<06:21:37.080> have 06:21:37.310 --> 06:21:37.320 align:start position:0% two models is they both have 06:21:37.320 --> 06:21:39.410 align:start position:0% two models is they both have interchangeable<06:21:38.218> Network<06:21:38.700> and<06:21:39.000> transport 06:21:39.410 --> 06:21:39.420 align:start position:0% interchangeable Network and transport 06:21:39.420 --> 06:21:40.430 align:start position:0% interchangeable Network and transport layers 06:21:40.430 --> 06:21:40.440 align:start position:0% layers 06:21:40.440 --> 06:21:42.410 align:start position:0% layers also<06:21:41.340> each<06:21:41.458> layer<06:21:41.700> of<06:21:41.760> the<06:21:41.878> OSI<06:21:42.240> model 06:21:42.410 --> 06:21:42.420 align:start position:0% also each layer of the OSI model 06:21:42.420 --> 06:21:44.930 align:start position:0% also each layer of the OSI model directly<06:21:43.020> correlates<06:21:43.620> with<06:21:43.920> the<06:21:44.040> TCP<06:21:44.400> model 06:21:44.930 --> 06:21:44.940 align:start position:0% directly correlates with the TCP model 06:21:44.940 --> 06:21:46.610 align:start position:0% directly correlates with the TCP model and<06:21:45.480> here<06:21:45.660> you<06:21:45.780> can<06:21:45.900> see<06:21:45.958> the<06:21:46.200> application 06:21:46.610 --> 06:21:46.620 align:start position:0% and here you can see the application 06:21:46.620 --> 06:21:49.010 align:start position:0% and here you can see the application layer<06:21:47.040> the<06:21:47.580> presentation<06:21:48.000> layer<06:21:48.420> and<06:21:48.840> the 06:21:49.010 --> 06:21:49.020 align:start position:0% layer the presentation layer and the 06:21:49.020 --> 06:21:50.628 align:start position:0% layer the presentation layer and the session<06:21:49.138> layer<06:21:49.558> of<06:21:49.680> the<06:21:49.798> OSI<06:21:50.218> model 06:21:50.628 --> 06:21:50.638 align:start position:0% session layer of the OSI model 06:21:50.638 --> 06:21:52.368 align:start position:0% session layer of the OSI model correspond<06:21:51.420> to<06:21:51.540> what<06:21:51.718> we<06:21:51.840> know<06:21:51.958> as<06:21:52.138> the 06:21:52.368 --> 06:21:52.378 align:start position:0% correspond to what we know as the 06:21:52.378 --> 06:21:55.310 align:start position:0% correspond to what we know as the application<06:21:52.798> layer<06:21:53.218> of<06:21:53.340> the<06:21:53.458> TCP<06:21:53.878> stack<06:21:54.660> this 06:21:55.310 --> 06:21:55.320 align:start position:0% application layer of the TCP stack this 06:21:55.320 --> 06:21:57.048 align:start position:0% application layer of the TCP stack this means<06:21:55.680> that<06:21:55.798> everything<06:21:55.980> in<06:21:56.280> the<06:21:56.400> OSI<06:21:56.760> model 06:21:57.048 --> 06:21:57.058 align:start position:0% means that everything in the OSI model 06:21:57.058 --> 06:21:59.090 align:start position:0% means that everything in the OSI model that<06:21:57.600> fell<06:21:57.780> into<06:21:57.958> application<06:21:58.500> presentation 06:21:59.090 --> 06:21:59.100 align:start position:0% that fell into application presentation 06:21:59.100 --> 06:22:01.910 align:start position:0% that fell into application presentation session<06:21:59.600> are<06:22:00.600> actually<06:22:00.780> done<06:22:01.138> in<06:22:01.740> the 06:22:01.910 --> 06:22:01.920 align:start position:0% session are actually done in the 06:22:01.920 --> 06:22:04.310 align:start position:0% session are actually done in the application<06:22:02.458> support<06:22:03.000> block 06:22:04.310 --> 06:22:04.320 align:start position:0% application support block 06:22:04.320 --> 06:22:06.890 align:start position:0% application support block next<06:22:04.980> the<06:22:05.340> transport<06:22:05.940> layer<06:22:06.360> of<06:22:06.480> the<06:22:06.540> OSI 06:22:06.890 --> 06:22:06.900 align:start position:0% next the transport layer of the OSI 06:22:06.900 --> 06:22:08.270 align:start position:0% next the transport layer of the OSI model<06:22:07.138> corresponds<06:22:07.680> directly<06:22:07.980> to<06:22:08.160> the 06:22:08.270 --> 06:22:08.280 align:start position:0% model corresponds directly to the 06:22:08.280 --> 06:22:10.730 align:start position:0% model corresponds directly to the transport<06:22:08.700> layer<06:22:09.000> of<06:22:09.120> the<06:22:09.180> TCP<06:22:09.600> model<06:22:10.080> the 06:22:10.730 --> 06:22:10.740 align:start position:0% transport layer of the TCP model the 06:22:10.740 --> 06:22:12.470 align:start position:0% transport layer of the TCP model the network<06:22:10.860> layer<06:22:11.280> of<06:22:11.400> OSI<06:22:11.820> with<06:22:12.120> the<06:22:12.298> internet 06:22:12.470 --> 06:22:12.480 align:start position:0% network layer of OSI with the internet 06:22:12.480 --> 06:22:15.708 align:start position:0% network layer of OSI with the internet layer<06:22:13.080> of<06:22:13.500> tcpip<06:22:14.160> and<06:22:14.820> that<06:22:15.058> is<06:22:15.298> easy<06:22:15.480> to 06:22:15.708 --> 06:22:15.718 align:start position:0% layer of tcpip and that is easy to 06:22:15.718 --> 06:22:18.048 align:start position:0% layer of tcpip and that is easy to remember<06:22:15.840> since<06:22:16.320> internet<06:22:16.680> is<06:22:17.400> really<06:22:17.878> short 06:22:18.048 --> 06:22:18.058 align:start position:0% remember since internet is really short 06:22:18.058 --> 06:22:20.208 align:start position:0% remember since internet is really short for<06:22:18.298> like<06:22:18.480> internet<06:22:18.718> working 06:22:20.208 --> 06:22:20.218 align:start position:0% for like internet working 06:22:20.218 --> 06:22:23.448 align:start position:0% for like internet working and<06:22:20.878> the<06:22:21.420> data<06:22:21.900> link<06:22:22.020> and<06:22:22.260> physical<06:22:22.500> layers<06:22:22.980> of 06:22:23.448 --> 06:22:23.458 align:start position:0% and the data link and physical layers of 06:22:23.458 --> 06:22:25.670 align:start position:0% and the data link and physical layers of the<06:22:23.638> OSI<06:22:24.000> model<06:22:24.240> correspond<06:22:24.780> directly<06:22:25.200> to<06:22:25.440> the 06:22:25.670 --> 06:22:25.680 align:start position:0% the OSI model correspond directly to the 06:22:25.680 --> 06:22:28.310 align:start position:0% the OSI model correspond directly to the network<06:22:25.860> interface<06:22:26.580> layer<06:22:26.940> of<06:22:27.000> the<06:22:27.120> TCP<06:22:27.480> now 06:22:28.310 --> 06:22:28.320 align:start position:0% network interface layer of the TCP now 06:22:28.320 --> 06:22:30.048 align:start position:0% network interface layer of the TCP now some<06:22:28.500> of<06:22:28.620> these<06:22:28.860> correlations<06:22:29.340> it<06:22:29.760> should<06:22:29.940> be 06:22:30.048 --> 06:22:30.058 align:start position:0% some of these correlations it should be 06:22:30.058 --> 06:22:32.330 align:start position:0% some of these correlations it should be mentioned<06:22:30.480> aren't<06:22:31.260> precise<06:22:31.798> and<06:22:31.980> exact 06:22:32.330 --> 06:22:32.340 align:start position:0% mentioned aren't precise and exact 06:22:32.340 --> 06:22:34.270 align:start position:0% mentioned aren't precise and exact they're<06:22:32.820> sort<06:22:33.120> of 06:22:34.270 --> 06:22:34.280 align:start position:0% they're sort of 06:22:34.280 --> 06:22:36.288 align:start position:0% they're sort of approximations<06:22:35.280> and<06:22:35.638> that's<06:22:35.760> because<06:22:36.000> they 06:22:36.288 --> 06:22:36.298 align:start position:0% approximations and that's because they 06:22:36.298 --> 06:22:38.208 align:start position:0% approximations and that's because they are<06:22:36.480> two<06:22:36.718> very<06:22:36.958> different<06:22:37.138> models<06:22:37.740> and 06:22:38.208 --> 06:22:38.218 align:start position:0% are two very different models and 06:22:38.218 --> 06:22:39.650 align:start position:0% are two very different models and therefore<06:22:38.580> they<06:22:38.820> were<06:22:38.940> created<06:22:39.240> differently 06:22:39.650 --> 06:22:39.660 align:start position:0% therefore they were created differently 06:22:39.660 --> 06:22:41.628 align:start position:0% therefore they were created differently and<06:22:40.200> weren't<06:22:40.440> necessarily<06:22:40.860> created<06:22:41.218> with<06:22:41.400> the 06:22:41.628 --> 06:22:41.638 align:start position:0% and weren't necessarily created with the 06:22:41.638 --> 06:22:43.490 align:start position:0% and weren't necessarily created with the one<06:22:41.878> or<06:22:42.000> the<06:22:42.180> other<06:22:42.240> in<06:22:42.480> mind<06:22:42.660> that<06:22:43.080> being<06:22:43.320> said 06:22:43.490 --> 06:22:43.500 align:start position:0% one or the other in mind that being said 06:22:43.500 --> 06:22:45.890 align:start position:0% one or the other in mind that being said tcpip<06:22:44.340> and<06:22:44.580> OSI<06:22:45.000> were<06:22:45.180> built<06:22:45.480> with<06:22:45.600> knowledge 06:22:45.890 --> 06:22:45.900 align:start position:0% tcpip and OSI were built with knowledge 06:22:45.900 --> 06:22:47.990 align:start position:0% tcpip and OSI were built with knowledge of<06:22:46.138> one<06:22:46.320> another<06:22:46.440> and<06:22:47.040> so<06:22:47.160> we<06:22:47.400> do<06:22:47.520> see<06:22:47.700> this 06:22:47.990 --> 06:22:48.000 align:start position:0% of one another and so we do see this 06:22:48.000 --> 06:22:51.708 align:start position:0% of one another and so we do see this overlap<06:22:48.420> now<06:22:49.260> the<06:22:49.740> TCP<06:22:50.280> model<06:22:50.940> outlines<06:22:51.480> and 06:22:51.708 --> 06:22:51.718 align:start position:0% overlap now the TCP model outlines and 06:22:51.718 --> 06:22:54.048 align:start position:0% overlap now the TCP model outlines and defines<06:22:52.260> the<06:22:52.860> methods<06:22:53.280> data<06:22:53.638> is<06:22:53.700> going<06:22:53.878> to 06:22:54.048 --> 06:22:54.058 align:start position:0% defines the methods data is going to 06:22:54.058 --> 06:22:55.490 align:start position:0% defines the methods data is going to flow<06:22:54.298> and<06:22:54.480> commute<06:22:54.780> in<06:22:54.958> a<06:22:55.080> communication 06:22:55.490 --> 06:22:55.500 align:start position:0% flow and commute in a communication 06:22:55.500 --> 06:22:58.190 align:start position:0% flow and commute in a communication system<06:22:55.798> it<06:22:56.638> does<06:22:56.760> this<06:22:56.940> by<06:22:57.180> assigning<06:22:57.780> each 06:22:58.190 --> 06:22:58.200 align:start position:0% system it does this by assigning each 06:22:58.200 --> 06:23:01.250 align:start position:0% system it does this by assigning each layer<06:22:58.680> in<06:22:58.980> the<06:22:59.160> stack<06:22:59.400> specific<06:23:00.240> functions<06:23:00.958> to 06:23:01.250 --> 06:23:01.260 align:start position:0% layer in the stack specific functions to 06:23:01.260 --> 06:23:03.948 align:start position:0% layer in the stack specific functions to perform<06:23:01.378> on<06:23:01.920> the<06:23:02.040> data<06:23:02.400> and<06:23:03.120> ultimately<06:23:03.540> each 06:23:03.948 --> 06:23:03.958 align:start position:0% perform on the data and ultimately each 06:23:03.958 --> 06:23:05.868 align:start position:0% perform on the data and ultimately each layer<06:23:04.260> is<06:23:04.500> completely<06:23:04.980> independent<06:23:05.580> of<06:23:05.760> all 06:23:05.868 --> 06:23:05.878 align:start position:0% layer is completely independent of all 06:23:05.878 --> 06:23:07.788 align:start position:0% layer is completely independent of all the<06:23:06.000> other<06:23:06.120> layers<06:23:06.540> and<06:23:06.900> more<06:23:07.138> or<06:23:07.320> less<06:23:07.378> is 06:23:07.788 --> 06:23:07.798 align:start position:0% the other layers and more or less is 06:23:07.798 --> 06:23:09.530 align:start position:0% the other layers and more or less is unaware<06:23:08.280> of<06:23:08.400> the<06:23:08.580> other<06:23:08.700> layers 06:23:09.530 --> 06:23:09.540 align:start position:0% unaware of the other layers 06:23:09.540 --> 06:23:11.510 align:start position:0% unaware of the other layers for<06:23:10.138> instance<06:23:10.378> the<06:23:10.740> topmost<06:23:11.040> layer<06:23:11.400> of<06:23:11.458> the 06:23:11.510 --> 06:23:11.520 align:start position:0% for instance the topmost layer of the 06:23:11.520 --> 06:23:13.490 align:start position:0% for instance the topmost layer of the application<06:23:12.058> layer<06:23:12.540> is<06:23:13.020> going<06:23:13.200> to<06:23:13.320> perform 06:23:13.490 --> 06:23:13.500 align:start position:0% application layer is going to perform 06:23:13.500 --> 06:23:16.310 align:start position:0% application layer is going to perform its<06:23:13.920> operations<06:23:14.218> if<06:23:14.580> the<06:23:14.878> processes<06:23:15.600> on<06:23:16.138> the 06:23:16.310 --> 06:23:16.320 align:start position:0% its operations if the processes on the 06:23:16.320 --> 06:23:18.650 align:start position:0% its operations if the processes on the communicating<06:23:16.860> systems<06:23:17.580> are<06:23:18.240> directly 06:23:18.650 --> 06:23:18.660 align:start position:0% communicating systems are directly 06:23:18.660 --> 06:23:20.570 align:start position:0% communicating systems are directly connected<06:23:19.080> to<06:23:19.320> each<06:23:19.500> other<06:23:19.620> by<06:23:19.980> some<06:23:20.218> sort<06:23:20.400> of 06:23:20.570 --> 06:23:20.580 align:start position:0% connected to each other by some sort of 06:23:20.580 --> 06:23:23.868 align:start position:0% connected to each other by some sort of information<06:23:21.120> pipe<06:23:22.620> the<06:23:23.160> operations<06:23:23.580> that 06:23:23.868 --> 06:23:23.878 align:start position:0% information pipe the operations that 06:23:23.878 --> 06:23:25.850 align:start position:0% information pipe the operations that allow<06:23:24.180> for<06:23:24.360> the<06:23:24.600> next<06:23:24.718> layer<06:23:25.138> the<06:23:25.378> transport 06:23:25.850 --> 06:23:25.860 align:start position:0% allow for the next layer the transport 06:23:25.860 --> 06:23:28.430 align:start position:0% allow for the next layer the transport layer<06:23:26.340> to<06:23:26.820> transmit<06:23:27.240> data<06:23:27.660> between<06:23:27.900> the<06:23:28.260> host 06:23:28.430 --> 06:23:28.440 align:start position:0% layer to transmit data between the host 06:23:28.440 --> 06:23:30.530 align:start position:0% layer to transmit data between the host computers<06:23:29.160> is<06:23:29.700> actually<06:23:29.878> found<06:23:30.180> in<06:23:30.360> the 06:23:30.530 --> 06:23:30.540 align:start position:0% computers is actually found in the 06:23:30.540 --> 06:23:33.948 align:start position:0% computers is actually found in the protocols<06:23:31.200> of<06:23:31.798> lower<06:23:32.100> layers<06:23:33.000> and<06:23:33.600> from<06:23:33.780> there 06:23:33.948 --> 06:23:33.958 align:start position:0% protocols of lower layers and from there 06:23:33.958 --> 06:23:37.310 align:start position:0% protocols of lower layers and from there on<06:23:34.200> each<06:23:34.740> data<06:23:35.458> layer<06:23:36.298> will<06:23:36.480> complete<06:23:36.900> its 06:23:37.310 --> 06:23:37.320 align:start position:0% on each data layer will complete its 06:23:37.320 --> 06:23:40.010 align:start position:0% on each data layer will complete its specified<06:23:37.680> actions<06:23:38.520> to<06:23:38.940> the<06:23:39.120> data<06:23:39.480> and<06:23:39.900> then 06:23:40.010 --> 06:23:40.020 align:start position:0% specified actions to the data and then 06:23:40.020 --> 06:23:41.990 align:start position:0% specified actions to the data and then encapsulate<06:23:40.680> the<06:23:40.860> data<06:23:41.218> where<06:23:41.580> it's<06:23:41.760> then 06:23:41.990 --> 06:23:42.000 align:start position:0% encapsulate the data where it's then 06:23:42.000 --> 06:23:45.230 align:start position:0% encapsulate the data where it's then passed<06:23:42.780> down<06:23:43.200> the<06:23:43.620> stack<06:23:43.798> in<06:23:44.700> the<06:23:44.878> opposite 06:23:45.230 --> 06:23:45.240 align:start position:0% passed down the stack in the opposite 06:23:45.240 --> 06:23:48.470 align:start position:0% passed down the stack in the opposite direction<06:23:45.420> when<06:23:46.260> data<06:23:46.680> is<06:23:46.860> traveling<06:23:47.340> back<06:23:47.638> up 06:23:48.470 --> 06:23:48.480 align:start position:0% direction when data is traveling back up 06:23:48.480 --> 06:23:50.208 align:start position:0% direction when data is traveling back up the<06:23:48.718> stack<06:23:48.900> and<06:23:49.200> we<06:23:49.378> saw<06:23:49.500> the<06:23:49.740> same<06:23:49.860> thing<06:23:50.040> with 06:23:50.208 --> 06:23:50.218 align:start position:0% the stack and we saw the same thing with 06:23:50.218 --> 06:23:52.868 align:start position:0% the stack and we saw the same thing with OSI<06:23:50.700> model<06:23:51.000> the<06:23:51.958> data<06:23:52.260> is<06:23:52.440> then 06:23:52.868 --> 06:23:52.878 align:start position:0% OSI model the data is then 06:23:52.878 --> 06:23:55.310 align:start position:0% OSI model the data is then de-encapsulated<06:23:53.878> so<06:23:54.540> when<06:23:54.660> it's<06:23:54.840> going<06:23:55.020> down 06:23:55.310 --> 06:23:55.320 align:start position:0% de-encapsulated so when it's going down 06:23:55.320 --> 06:23:57.350 align:start position:0% de-encapsulated so when it's going down we<06:23:55.680> call<06:23:55.860> that 06:23:57.350 --> 06:23:57.360 align:start position:0% we call that 06:23:57.360 --> 06:24:01.548 align:start position:0% we call that being<06:23:58.200> encapsulated 06:24:01.548 --> 06:24:01.558 align:start position:0% 06:24:01.558 --> 06:24:03.948 align:start position:0% and<06:24:01.980> when<06:24:02.100> it's<06:24:02.218> going<06:24:02.340> back<06:24:02.520> up<06:24:02.700> we<06:24:03.000> call<06:24:03.120> it 06:24:03.948 --> 06:24:03.958 align:start position:0% and when it's going back up we call it 06:24:03.958 --> 06:24:06.410 align:start position:0% and when it's going back up we call it D<06:24:04.440> encapsulated<06:24:05.218> so<06:24:05.820> we<06:24:05.940> really<06:24:06.120> need<06:24:06.298> to 06:24:06.410 --> 06:24:06.420 align:start position:0% D encapsulated so we really need to 06:24:06.420 --> 06:24:08.030 align:start position:0% D encapsulated so we really need to understand<06:24:06.600> how<06:24:07.200> all<06:24:07.440> of<06:24:07.558> this<06:24:07.740> works 06:24:08.030 --> 06:24:08.040 align:start position:0% understand how all of this works 06:24:08.040 --> 06:24:11.750 align:start position:0% understand how all of this works together<06:24:08.360> in<06:24:09.360> order<06:24:09.480> to<06:24:10.020> get<06:24:10.740> a<06:24:11.100> really<06:24:11.520> strong 06:24:11.750 --> 06:24:11.760 align:start position:0% together in order to get a really strong 06:24:11.760 --> 06:24:16.070 align:start position:0% together in order to get a really strong picture<06:24:12.200> of<06:24:13.200> uh<06:24:13.860> uh<06:24:14.340> TCP<06:24:15.240> and<06:24:15.660> be<06:24:15.780> able<06:24:15.958> to 06:24:16.070 --> 06:24:16.080 align:start position:0% picture of uh uh TCP and be able to 06:24:16.080 --> 06:24:19.368 align:start position:0% picture of uh uh TCP and be able to speak<06:24:16.500> about<06:24:16.680> the<06:24:17.040> layers<06:24:17.280> in<06:24:17.638> general 06:24:19.368 --> 06:24:19.378 align:start position:0% speak about the layers in general 06:24:19.378 --> 06:24:22.190 align:start position:0% speak about the layers in general so<06:24:19.740> let's<06:24:19.920> talk<06:24:20.100> about<06:24:20.218> encapsulation<06:24:21.200> each 06:24:22.190 --> 06:24:22.200 align:start position:0% so let's talk about encapsulation each 06:24:22.200 --> 06:24:24.708 align:start position:0% so let's talk about encapsulation each layer<06:24:22.558> is<06:24:22.740> responsible<06:24:23.340> for<06:24:23.940> only<06:24:24.240> the 06:24:24.708 --> 06:24:24.718 align:start position:0% layer is responsible for only the 06:24:24.718 --> 06:24:26.750 align:start position:0% layer is responsible for only the specific<06:24:25.080> data<06:24:25.558> defined<06:24:26.040> at<06:24:26.160> that<06:24:26.340> layer<06:24:26.580> as 06:24:26.750 --> 06:24:26.760 align:start position:0% specific data defined at that layer as 06:24:26.760 --> 06:24:29.030 align:start position:0% specific data defined at that layer as we've<06:24:27.000> said<06:24:27.180> now<06:24:27.840> these<06:24:28.080> layers<06:24:28.378> are<06:24:28.620> going<06:24:28.798> to 06:24:29.030 --> 06:24:29.040 align:start position:0% we've said now these layers are going to 06:24:29.040 --> 06:24:31.070 align:start position:0% we've said now these layers are going to receive<06:24:29.580> the<06:24:29.820> data<06:24:30.180> package<06:24:30.420> from<06:24:30.660> the<06:24:30.780> layer 06:24:31.070 --> 06:24:31.080 align:start position:0% receive the data package from the layer 06:24:31.080 --> 06:24:33.590 align:start position:0% receive the data package from the layer above<06:24:31.440> it<06:24:31.620> when<06:24:32.100> sending<06:24:32.638> and<06:24:33.180> the<06:24:33.298> layer 06:24:33.590 --> 06:24:33.600 align:start position:0% above it when sending and the layer 06:24:33.600 --> 06:24:36.288 align:start position:0% above it when sending and the layer below<06:24:34.138> it<06:24:34.320> when<06:24:34.740> receiving<06:24:35.218> this<06:24:35.940> makes<06:24:36.120> sense 06:24:36.288 --> 06:24:36.298 align:start position:0% below it when receiving this makes sense 06:24:36.298 --> 06:24:39.288 align:start position:0% below it when receiving this makes sense if<06:24:36.600> I'm<06:24:36.718> receiving<06:24:37.080> data<06:24:38.040> is<06:24:38.458> going<06:24:38.638> up<06:24:38.940> so<06:24:39.120> the 06:24:39.288 --> 06:24:39.298 align:start position:0% if I'm receiving data is going up so the 06:24:39.298 --> 06:24:41.390 align:start position:0% if I'm receiving data is going up so the data<06:24:39.540> is<06:24:39.600> coming<06:24:39.780> from<06:24:39.958> below<06:24:40.320> and<06:24:41.100> if<06:24:41.280> I'm 06:24:41.390 --> 06:24:41.400 align:start position:0% data is coming from below and if I'm 06:24:41.400 --> 06:24:43.070 align:start position:0% data is coming from below and if I'm sending<06:24:41.760> it's<06:24:41.878> going<06:24:42.120> down<06:24:42.420> from<06:24:42.900> the 06:24:43.070 --> 06:24:43.080 align:start position:0% sending it's going down from the 06:24:43.080 --> 06:24:44.750 align:start position:0% sending it's going down from the application<06:24:43.620> down<06:24:43.980> to<06:24:44.218> the<06:24:44.340> networking 06:24:44.750 --> 06:24:44.760 align:start position:0% application down to the networking 06:24:44.760 --> 06:24:46.070 align:start position:0% application down to the networking interface 06:24:46.070 --> 06:24:46.080 align:start position:0% interface 06:24:46.080 --> 06:24:48.708 align:start position:0% interface now<06:24:46.558> when<06:24:46.860> it<06:24:47.100> receives<06:24:47.520> this<06:24:48.000> package<06:24:48.360> each 06:24:48.708 --> 06:24:48.718 align:start position:0% now when it receives this package each 06:24:48.718 --> 06:24:50.750 align:start position:0% now when it receives this package each layer<06:24:49.020> is<06:24:49.138> going<06:24:49.320> to<06:24:49.440> add<06:24:49.680> its<06:24:50.040> own<06:24:50.160> packaging 06:24:50.750 --> 06:24:50.760 align:start position:0% layer is going to add its own packaging 06:24:50.760 --> 06:24:53.270 align:start position:0% layer is going to add its own packaging which<06:24:51.180> is<06:24:51.360> called<06:24:51.480> a<06:24:51.660> header<06:24:52.020> this<06:24:52.740> header<06:24:53.100> is 06:24:53.270 --> 06:24:53.280 align:start position:0% which is called a header this header is 06:24:53.280 --> 06:24:55.910 align:start position:0% which is called a header this header is used<06:24:53.458> by<06:24:53.820> the<06:24:54.120> corresponding<06:24:54.900> layer<06:24:55.320> at<06:24:55.740> the 06:24:55.910 --> 06:24:55.920 align:start position:0% used by the corresponding layer at the 06:24:55.920 --> 06:24:59.030 align:start position:0% used by the corresponding layer at the receiving<06:24:56.218> side<06:24:56.638> for<06:24:57.180> specific<06:24:57.718> purposes<06:24:58.320> the 06:24:59.030 --> 06:24:59.040 align:start position:0% receiving side for specific purposes the 06:24:59.040 --> 06:25:00.350 align:start position:0% receiving side for specific purposes the exact<06:24:59.340> purpose<06:24:59.580> is<06:24:59.760> really<06:24:59.878> going<06:25:00.058> to<06:25:00.120> depend 06:25:00.350 --> 06:25:00.360 align:start position:0% exact purpose is really going to depend 06:25:00.360 --> 06:25:02.510 align:start position:0% exact purpose is really going to depend on<06:25:00.480> the<06:25:00.600> layer<06:25:00.900> in<06:25:01.080> question<06:25:01.320> but<06:25:02.040> this<06:25:02.218> header 06:25:02.510 --> 06:25:02.520 align:start position:0% on the layer in question but this header 06:25:02.520 --> 06:25:04.310 align:start position:0% on the layer in question but this header is<06:25:02.638> going<06:25:02.760> to<06:25:02.820> be<06:25:02.940> added<06:25:03.240> to<06:25:03.360> the<06:25:03.540> beginning<06:25:03.840> of 06:25:04.310 --> 06:25:04.320 align:start position:0% is going to be added to the beginning of 06:25:04.320 --> 06:25:06.948 align:start position:0% is going to be added to the beginning of the<06:25:04.558> data<06:25:04.860> so<06:25:05.340> that<06:25:05.520> it<06:25:05.700> is<06:25:05.878> the<06:25:06.298> first<06:25:06.480> thing 06:25:06.948 --> 06:25:06.958 align:start position:0% the data so that it is the first thing 06:25:06.958 --> 06:25:10.010 align:start position:0% the data so that it is the first thing received<06:25:07.920> by<06:25:08.218> the<06:25:08.340> receiving<06:25:08.638> layer<06:25:09.180> that<06:25:09.840> way 06:25:10.010 --> 06:25:10.020 align:start position:0% received by the receiving layer that way 06:25:10.020 --> 06:25:12.110 align:start position:0% received by the receiving layer that way each<06:25:10.320> layer<06:25:10.558> on<06:25:10.680> the<06:25:10.798> receiving<06:25:11.040> end<06:25:11.340> can<06:25:11.940> then 06:25:12.110 --> 06:25:12.120 align:start position:0% each layer on the receiving end can then 06:25:12.120 --> 06:25:14.270 align:start position:0% each layer on the receiving end can then remove<06:25:12.420> that<06:25:12.780> header<06:25:13.200> perform<06:25:13.798> its 06:25:14.270 --> 06:25:14.280 align:start position:0% remove that header perform its 06:25:14.280 --> 06:25:15.890 align:start position:0% remove that header perform its operations<06:25:14.580> and<06:25:14.940> then<06:25:15.058> pass<06:25:15.298> the<06:25:15.480> remaining 06:25:15.890 --> 06:25:15.900 align:start position:0% operations and then pass the remaining 06:25:15.900 --> 06:25:19.128 align:start position:0% operations and then pass the remaining data<06:25:16.200> up<06:25:16.440> the<06:25:16.620> stack<06:25:16.860> up<06:25:17.160> the<06:25:17.340> TCP<06:25:17.760> model<06:25:18.360> on 06:25:19.128 --> 06:25:19.138 align:start position:0% data up the stack up the TCP model on 06:25:19.138 --> 06:25:21.830 align:start position:0% data up the stack up the TCP model on the<06:25:19.320> lowest<06:25:19.620> layer<06:25:20.400> a<06:25:21.000> footer<06:25:21.360> is<06:25:21.540> also<06:25:21.780> going 06:25:21.830 --> 06:25:21.840 align:start position:0% the lowest layer a footer is also going 06:25:21.840 --> 06:25:22.970 align:start position:0% the lowest layer a footer is also going to<06:25:22.020> be<06:25:22.080> added 06:25:22.970 --> 06:25:22.980 align:start position:0% to be added 06:25:22.980 --> 06:25:25.430 align:start position:0% to be added and<06:25:23.400> this<06:25:23.520> is<06:25:23.638> going<06:25:23.760> to<06:25:23.820> add<06:25:24.058> to<06:25:24.660> the<06:25:24.840> frame<06:25:25.080> by 06:25:25.430 --> 06:25:25.440 align:start position:0% and this is going to add to the frame by 06:25:25.440 --> 06:25:27.128 align:start position:0% and this is going to add to the frame by adding<06:25:25.740> more<06:25:25.980> supplemental<06:25:26.700> information 06:25:27.128 --> 06:25:27.138 align:start position:0% adding more supplemental information 06:25:27.138 --> 06:25:29.628 align:start position:0% adding more supplemental information this<06:25:28.138> extra<06:25:28.320> data 06:25:29.628 --> 06:25:29.638 align:start position:0% this extra data 06:25:29.638 --> 06:25:31.910 align:start position:0% this extra data at<06:25:30.180> the<06:25:30.360> end<06:25:30.540> of<06:25:30.840> the<06:25:30.958> data<06:25:31.260> package<06:25:31.558> is<06:25:31.740> going 06:25:31.910 --> 06:25:31.920 align:start position:0% at the end of the data package is going 06:25:31.920 --> 06:25:34.190 align:start position:0% at the end of the data package is going to<06:25:32.040> assist<06:25:32.218> the<06:25:32.700> receiving<06:25:33.000> end<06:25:33.240> on<06:25:33.600> ensuring 06:25:34.190 --> 06:25:34.200 align:start position:0% to assist the receiving end on ensuring 06:25:34.200 --> 06:25:36.708 align:start position:0% to assist the receiving end on ensuring that<06:25:34.920> the<06:25:35.218> data<06:25:35.520> was<06:25:35.760> received<06:25:36.240> completely 06:25:36.708 --> 06:25:36.718 align:start position:0% that the data was received completely 06:25:36.718 --> 06:25:39.530 align:start position:0% that the data was received completely and<06:25:37.260> undamaged<06:25:37.920> this<06:25:38.340> footer<06:25:38.878> is<06:25:39.058> also<06:25:39.298> what's 06:25:39.530 --> 06:25:39.540 align:start position:0% and undamaged this footer is also what's 06:25:39.540 --> 06:25:44.990 align:start position:0% and undamaged this footer is also what's called<06:25:39.780> an<06:25:40.160> FCS<06:25:41.160> or<06:25:42.120> a<06:25:42.540> frame 06:25:44.990 --> 06:25:45.000 align:start position:0% 06:25:45.000 --> 06:25:47.990 align:start position:0% check 06:25:47.990 --> 06:25:48.000 align:start position:0% 06:25:48.000 --> 06:25:50.628 align:start position:0% sequence 06:25:50.628 --> 06:25:50.638 align:start position:0% sequence 06:25:50.638 --> 06:25:53.270 align:start position:0% sequence and<06:25:51.058> as<06:25:51.240> the<06:25:51.420> name<06:25:51.540> implies<06:25:52.020> it<06:25:52.798> is<06:25:52.920> going<06:25:53.100> to 06:25:53.270 --> 06:25:53.280 align:start position:0% and as the name implies it is going to 06:25:53.280 --> 06:25:55.490 align:start position:0% and as the name implies it is going to check<06:25:53.580> to<06:25:53.878> make<06:25:54.000> sure<06:25:54.120> the<06:25:54.420> data<06:25:54.718> was<06:25:55.020> received 06:25:55.490 --> 06:25:55.500 align:start position:0% check to make sure the data was received 06:25:55.500 --> 06:25:57.948 align:start position:0% check to make sure the data was received correctly<06:25:55.920> now<06:25:56.638> on<06:25:56.940> the<06:25:57.000> receiving<06:25:57.298> end<06:25:57.540> this 06:25:57.948 --> 06:25:57.958 align:start position:0% correctly now on the receiving end this 06:25:57.958 --> 06:25:59.810 align:start position:0% correctly now on the receiving end this process<06:25:58.260> is<06:25:58.680> reversed<06:25:59.218> by<06:25:59.458> what's<06:25:59.638> called 06:25:59.810 --> 06:25:59.820 align:start position:0% process is reversed by what's called 06:25:59.820 --> 06:26:02.090 align:start position:0% process is reversed by what's called de-encapsulation<06:26:00.780> in<06:26:01.320> other<06:26:01.440> words<06:26:01.558> the<06:26:01.860> data 06:26:02.090 --> 06:26:02.100 align:start position:0% de-encapsulation in other words the data 06:26:02.100 --> 06:26:03.470 align:start position:0% de-encapsulation in other words the data is<06:26:02.218> received<06:26:02.638> at<06:26:02.760> each<06:26:02.878> layer<06:26:03.180> and<06:26:03.298> the 06:26:03.470 --> 06:26:03.480 align:start position:0% is received at each layer and the 06:26:03.480 --> 06:26:06.590 align:start position:0% is received at each layer and the headers<06:26:03.718> are<06:26:03.900> removed<06:26:04.378> to<06:26:04.920> allow<06:26:05.280> the<06:26:05.580> data<06:26:05.940> to 06:26:06.590 --> 06:26:06.600 align:start position:0% headers are removed to allow the data to 06:26:06.600 --> 06:26:08.628 align:start position:0% headers are removed to allow the data to perform<06:26:06.840> the<06:26:07.200> related<06:26:07.500> tasks<06:26:07.980> where<06:26:08.280> finally 06:26:08.628 --> 06:26:08.638 align:start position:0% perform the related tasks where finally 06:26:08.638 --> 06:26:11.390 align:start position:0% perform the related tasks where finally the<06:26:08.820> data<06:26:09.058> is<06:26:09.298> received<06:26:09.780> by<06:26:09.958> the<06:26:10.138> application 06:26:11.390 --> 06:26:11.400 align:start position:0% the data is received by the application 06:26:11.400 --> 06:26:13.730 align:start position:0% the data is received by the application uh<06:26:12.058> the<06:26:12.298> application<06:26:12.660> layer<06:26:13.080> and<06:26:13.500> then<06:26:13.620> the 06:26:13.730 --> 06:26:13.740 align:start position:0% uh the application layer and then the 06:26:13.740 --> 06:26:15.410 align:start position:0% uh the application layer and then the resulting<06:26:14.100> data<06:26:14.400> is<06:26:14.458> delivered<06:26:14.878> to<06:26:15.180> whatever 06:26:15.410 --> 06:26:15.420 align:start position:0% resulting data is delivered to whatever 06:26:15.420 --> 06:26:17.510 align:start position:0% resulting data is delivered to whatever the<06:26:15.660> requested<06:26:16.138> application<06:26:16.558> was<06:26:16.860> now<06:26:17.218> just 06:26:17.510 --> 06:26:17.520 align:start position:0% the requested application was now just 06:26:17.520 --> 06:26:19.430 align:start position:0% the requested application was now just like<06:26:17.700> with<06:26:17.940> the<06:26:18.240> OSI<06:26:18.600> model<06:26:18.780> we'll<06:26:19.200> talk<06:26:19.378> about 06:26:19.430 --> 06:26:19.440 align:start position:0% like with the OSI model we'll talk about 06:26:19.440 --> 06:26:20.810 align:start position:0% like with the OSI model we'll talk about later<06:26:19.680> this<06:26:19.980> application<06:26:20.340> layer<06:26:20.700> doesn't 06:26:20.810 --> 06:26:20.820 align:start position:0% later this application layer doesn't 06:26:20.820 --> 06:26:22.850 align:start position:0% later this application layer doesn't mean<06:26:21.000> the<06:26:21.298> actual<06:26:21.540> application<06:26:22.200> itself<06:26:22.558> it's 06:26:22.850 --> 06:26:22.860 align:start position:0% mean the actual application itself it's 06:26:22.860 --> 06:26:25.190 align:start position:0% mean the actual application itself it's simply<06:26:23.100> the<06:26:23.280> layer<06:26:23.638> that<06:26:24.180> provides<06:26:24.600> access<06:26:24.840> to 06:26:25.190 --> 06:26:25.200 align:start position:0% simply the layer that provides access to 06:26:25.200 --> 06:26:27.770 align:start position:0% simply the layer that provides access to the<06:26:25.378> information<06:26:25.558> from<06:26:26.458> an<06:26:26.760> application<06:26:27.180> now 06:26:27.770 --> 06:26:27.780 align:start position:0% the information from an application now 06:26:27.780 --> 06:26:29.448 align:start position:0% the information from an application now just<06:26:28.020> like<06:26:28.080> the<06:26:28.200> OSI<06:26:28.620> model<06:26:28.798> there<06:26:29.100> are<06:26:29.218> a<06:26:29.340> few 06:26:29.448 --> 06:26:29.458 align:start position:0% just like the OSI model there are a few 06:26:29.458 --> 06:26:31.610 align:start position:0% just like the OSI model there are a few mnemonic<06:26:30.298> devices<06:26:30.660> that<06:26:31.080> can<06:26:31.200> be<06:26:31.320> used<06:26:31.440> to 06:26:31.610 --> 06:26:31.620 align:start position:0% mnemonic devices that can be used to 06:26:31.620 --> 06:26:33.230 align:start position:0% mnemonic devices that can be used to help<06:26:31.740> in<06:26:31.980> Remembering<06:26:32.520> these<06:26:32.760> layers<06:26:33.000> in 06:26:33.230 --> 06:26:33.240 align:start position:0% help in Remembering these layers in 06:26:33.240 --> 06:26:35.030 align:start position:0% help in Remembering these layers in order<06:26:33.420> and<06:26:33.958> the<06:26:34.080> one<06:26:34.200> that<06:26:34.378> I<06:26:34.500> use<06:26:34.680> the<06:26:34.920> most 06:26:35.030 --> 06:26:35.040 align:start position:0% order and the one that I use the most 06:26:35.040 --> 06:26:37.970 align:start position:0% order and the one that I use the most going<06:26:35.638> from<06:26:35.878> the<06:26:36.058> top<06:26:36.180> down<06:26:36.480> is<06:26:37.200> called<06:26:37.440> All 06:26:37.970 --> 06:26:37.980 align:start position:0% going from the top down is called All 06:26:37.980 --> 06:26:40.310 align:start position:0% going from the top down is called All Things<06:26:38.218> in<06:26:38.760> networking<06:26:39.420> again<06:26:39.958> that's 06:26:40.310 --> 06:26:40.320 align:start position:0% Things in networking again that's 06:26:40.320 --> 06:26:42.770 align:start position:0% Things in networking again that's application<06:26:40.980> All<06:26:41.520> Transport<06:26:42.298> things 06:26:42.770 --> 06:26:42.780 align:start position:0% application All Transport things 06:26:42.780 --> 06:26:46.070 align:start position:0% application All Transport things internet<06:26:43.320> in<06:26:44.040> network<06:26:44.458> interface<06:26:45.180> networking 06:26:46.070 --> 06:26:46.080 align:start position:0% internet in network interface networking 06:26:46.080 --> 06:26:47.990 align:start position:0% internet in network interface networking so<06:26:46.680> now<06:26:46.798> we<06:26:46.920> have<06:26:47.040> a<06:26:47.160> better<06:26:47.280> understanding<06:26:47.760> of 06:26:47.990 --> 06:26:48.000 align:start position:0% so now we have a better understanding of 06:26:48.000 --> 06:26:49.850 align:start position:0% so now we have a better understanding of how<06:26:48.420> the<06:26:48.600> data<06:26:48.900> is<06:26:48.958> going<06:26:49.138> to<06:26:49.260> proceed<06:26:49.558> from 06:26:49.850 --> 06:26:49.860 align:start position:0% how the data is going to proceed from 06:26:49.860 --> 06:26:52.190 align:start position:0% how the data is going to proceed from layer<06:26:50.160> to<06:26:50.280> layer<06:26:50.638> through<06:26:51.420> encapsulation 06:26:52.190 --> 06:26:52.200 align:start position:0% layer to layer through encapsulation 06:26:52.200 --> 06:26:55.368 align:start position:0% layer to layer through encapsulation going<06:26:53.040> down<06:26:53.400> from<06:26:53.820> application<06:26:54.420> to<06:26:54.840> transport 06:26:55.368 --> 06:26:55.378 align:start position:0% going down from application to transport 06:26:55.378 --> 06:26:58.910 align:start position:0% going down from application to transport to<06:26:56.280> internet<06:26:56.580> to<06:26:57.298> network<06:26:57.480> interface<06:26:58.200> right 06:26:58.910 --> 06:26:58.920 align:start position:0% to internet to network interface right 06:26:58.920 --> 06:27:00.730 align:start position:0% to internet to network interface right and<06:26:59.580> then<06:26:59.638> through<06:26:59.940> D<06:27:00.180> inter 06:27:00.730 --> 06:27:00.740 align:start position:0% and then through D inter 06:27:00.740 --> 06:27:02.990 align:start position:0% and then through D inter de-encapsulation<06:27:01.740> which<06:27:02.040> goes<06:27:02.400> the<06:27:02.638> opposite 06:27:02.990 --> 06:27:03.000 align:start position:0% de-encapsulation which goes the opposite 06:27:03.000 --> 06:27:06.170 align:start position:0% de-encapsulation which goes the opposite way<06:27:03.200> let's<06:27:04.200> take<06:27:04.440> a<06:27:04.680> closer<06:27:04.980> look<06:27:05.218> at<06:27:05.940> these 06:27:06.170 --> 06:27:06.180 align:start position:0% way let's take a closer look at these 06:27:06.180 --> 06:27:08.090 align:start position:0% way let's take a closer look at these layers<06:27:06.480> starting<06:27:06.900> with<06:27:07.200> the<06:27:07.378> topmost<06:27:07.680> layer 06:27:08.090 --> 06:27:08.100 align:start position:0% layers starting with the topmost layer 06:27:08.100 --> 06:27:10.850 align:start position:0% layers starting with the topmost layer the<06:27:08.280> application<06:27:08.700> layer<06:27:09.480> so<06:27:10.138> here<06:27:10.440> on<06:27:10.740> the 06:27:10.850 --> 06:27:10.860 align:start position:0% the application layer so here on the 06:27:10.860 --> 06:27:12.650 align:start position:0% the application layer so here on the application<06:27:11.340> layer<06:27:11.700> much<06:27:12.000> like<06:27:12.240> the 06:27:12.650 --> 06:27:12.660 align:start position:0% application layer much like the 06:27:12.660 --> 06:27:14.990 align:start position:0% application layer much like the application<06:27:13.320> layer<06:27:13.680> of<06:27:13.740> the<06:27:13.798> OSI<06:27:14.280> model<06:27:14.520> we 06:27:14.990 --> 06:27:15.000 align:start position:0% application layer of the OSI model we 06:27:15.000 --> 06:27:16.910 align:start position:0% application layer of the OSI model we find<06:27:15.180> what's<06:27:15.420> considered<06:27:15.958> the<06:27:16.320> highest<06:27:16.740> level 06:27:16.910 --> 06:27:16.920 align:start position:0% find what's considered the highest level 06:27:16.920 --> 06:27:19.310 align:start position:0% find what's considered the highest level protocols<06:27:17.760> higher<06:27:18.480> level<06:27:18.600> meaning<06:27:18.900> these 06:27:19.310 --> 06:27:19.320 align:start position:0% protocols higher level meaning these 06:27:19.320 --> 06:27:23.030 align:start position:0% protocols higher level meaning these protocols<06:27:19.798> such<06:27:20.040> as<06:27:20.420> SMTP<06:27:21.420> FTP<06:27:22.320> and<06:27:22.680> so<06:27:22.860> on 06:27:23.030 --> 06:27:23.040 align:start position:0% protocols such as SMTP FTP and so on 06:27:23.040 --> 06:27:25.250 align:start position:0% protocols such as SMTP FTP and so on these<06:27:23.580> Protocols<06:27:24.058> are<06:27:24.240> not<06:27:24.420> necessarily 06:27:25.250 --> 06:27:25.260 align:start position:0% these Protocols are not necessarily 06:27:25.260 --> 06:27:27.948 align:start position:0% these Protocols are not necessarily concerned<06:27:26.160> with<06:27:26.760> the<06:27:27.058> method<06:27:27.420> by<06:27:27.600> which<06:27:27.780> the 06:27:27.948 --> 06:27:27.958 align:start position:0% concerned with the method by which the 06:27:27.958 --> 06:27:30.410 align:start position:0% concerned with the method by which the data<06:27:28.320> arrives<06:27:28.740> at<06:27:28.920> it<06:27:29.040> says<06:27:29.160> destination<06:27:29.820> but 06:27:30.410 --> 06:27:30.420 align:start position:0% data arrives at it says destination but 06:27:30.420 --> 06:27:32.990 align:start position:0% data arrives at it says destination but simply<06:27:30.718> that<06:27:30.900> it<06:27:31.080> just<06:27:31.378> arrives<06:27:31.798> period 06:27:32.990 --> 06:27:33.000 align:start position:0% simply that it just arrives period 06:27:33.000 --> 06:27:35.090 align:start position:0% simply that it just arrives period here<06:27:33.420> in<06:27:33.660> the<06:27:33.780> application<06:27:34.200> layer<06:27:34.620> we<06:27:34.860> also 06:27:35.090 --> 06:27:35.100 align:start position:0% here in the application layer we also 06:27:35.100 --> 06:27:37.610 align:start position:0% here in the application layer we also provide<06:27:35.458> the<06:27:35.700> functions<06:27:36.180> that<06:27:36.540> relate<06:27:37.020> to<06:27:37.500> the 06:27:37.610 --> 06:27:37.620 align:start position:0% provide the functions that relate to the 06:27:37.620 --> 06:27:40.310 align:start position:0% provide the functions that relate to the presentation<06:27:38.100> and<06:27:38.940> the<06:27:39.120> session<06:27:39.298> layers<06:27:39.840> of 06:27:40.310 --> 06:27:40.320 align:start position:0% presentation and the session layers of 06:27:40.320 --> 06:27:42.530 align:start position:0% presentation and the session layers of the<06:27:40.558> OSI<06:27:40.980> model<06:27:41.280> as<06:27:41.760> we've<06:27:41.940> already<06:27:42.058> pointed 06:27:42.530 --> 06:27:42.540 align:start position:0% the OSI model as we've already pointed 06:27:42.540 --> 06:27:44.628 align:start position:0% the OSI model as we've already pointed out<06:27:42.660> it<06:27:43.620> does<06:27:43.740> this<06:27:43.860> typically<06:27:44.218> through<06:27:44.520> the 06:27:44.628 --> 06:27:44.638 align:start position:0% out it does this typically through the 06:27:44.638 --> 06:27:49.010 align:start position:0% out it does this typically through the use<06:27:44.760> of<06:27:45.000> what<06:27:45.120> are<06:27:45.298> called<06:27:45.480> libraries 06:27:49.010 --> 06:27:49.020 align:start position:0% 06:27:49.020 --> 06:27:52.610 align:start position:0% which<06:27:49.740> are<06:27:49.980> collections<06:27:50.700> of<06:27:51.620> Behavioral 06:27:52.610 --> 06:27:52.620 align:start position:0% which are collections of Behavioral 06:27:52.620 --> 06:27:56.150 align:start position:0% which are collections of Behavioral implementations<06:27:53.520> that<06:27:54.360> can<06:27:54.540> be<06:27:54.718> utilized<06:27:55.500> and 06:27:56.150 --> 06:27:56.160 align:start position:0% implementations that can be utilized and 06:27:56.160 --> 06:27:58.368 align:start position:0% implementations that can be utilized and called<06:27:56.400> upon<06:27:56.820> by<06:27:57.298> services<06:27:57.660> that<06:27:58.200> are 06:27:58.368 --> 06:27:58.378 align:start position:0% called upon by services that are 06:27:58.378 --> 06:27:59.628 align:start position:0% called upon by services that are unrelated 06:27:59.628 --> 06:27:59.638 align:start position:0% unrelated 06:27:59.638 --> 06:28:02.868 align:start position:0% unrelated so<06:28:00.298> this<06:28:01.260> means<06:28:01.558> that<06:28:01.740> the<06:28:01.920> application<06:28:02.340> layer 06:28:02.868 --> 06:28:02.878 align:start position:0% so this means that the application layer 06:28:02.878 --> 06:28:05.090 align:start position:0% so this means that the application layer of<06:28:03.298> the<06:28:03.420> TCP<06:28:03.840> model 06:28:05.090 --> 06:28:05.100 align:start position:0% of the TCP model 06:28:05.100 --> 06:28:08.270 align:start position:0% of the TCP model encodes<06:28:06.000> the<06:28:06.360> data<06:28:06.660> and<06:28:07.558> performs<06:28:08.040> any 06:28:08.270 --> 06:28:08.280 align:start position:0% encodes the data and performs any 06:28:08.280 --> 06:28:10.190 align:start position:0% encodes the data and performs any encryption<06:28:08.878> and<06:28:09.420> compression<06:28:09.958> that's 06:28:10.190 --> 06:28:10.200 align:start position:0% encryption and compression that's 06:28:10.200 --> 06:28:11.510 align:start position:0% encryption and compression that's necessary 06:28:11.510 --> 06:28:11.520 align:start position:0% necessary 06:28:11.520 --> 06:28:15.410 align:start position:0% necessary as<06:28:11.940> well<06:28:12.058> as<06:28:12.240> initiating<06:28:13.080> and<06:28:13.980> maintaining 06:28:15.410 --> 06:28:15.420 align:start position:0% as well as initiating and maintaining 06:28:15.420 --> 06:28:18.230 align:start position:0% as well as initiating and maintaining the<06:28:16.138> connection<06:28:16.558> or<06:28:16.920> the<06:28:17.040> session<06:28:17.340> as<06:28:18.000> we<06:28:18.120> can 06:28:18.230 --> 06:28:18.240 align:start position:0% the connection or the session as we can 06:28:18.240 --> 06:28:20.330 align:start position:0% the connection or the session as we can see<06:28:18.360> here<06:28:18.600> these<06:28:19.020> are<06:28:19.080> just<06:28:19.320> some<06:28:19.740> of<06:28:20.160> the 06:28:20.330 --> 06:28:20.340 align:start position:0% see here these are just some of the 06:28:20.340 --> 06:28:22.610 align:start position:0% see here these are just some of the protocols<06:28:20.940> that<06:28:21.540> we<06:28:21.780> find<06:28:22.020> at<06:28:22.500> the 06:28:22.610 --> 06:28:22.620 align:start position:0% protocols that we find at the 06:28:22.620 --> 06:28:25.250 align:start position:0% protocols that we find at the application<06:28:23.100> layer<06:28:23.520> we<06:28:24.000> can<06:28:24.120> also<06:28:24.540> further 06:28:25.250 --> 06:28:25.260 align:start position:0% application layer we can also further 06:28:25.260 --> 06:28:27.110 align:start position:0% application layer we can also further group<06:28:25.500> some<06:28:25.798> of<06:28:25.920> these<06:28:26.100> applications<06:28:26.520> based 06:28:27.110 --> 06:28:27.120 align:start position:0% group some of these applications based 06:28:27.120 --> 06:28:29.090 align:start position:0% group some of these applications based on<06:28:27.298> the<06:28:27.540> specific<06:28:27.780> type<06:28:28.138> of<06:28:28.440> function<06:28:28.798> that 06:28:29.090 --> 06:28:29.100 align:start position:0% on the specific type of function that 06:28:29.100 --> 06:28:31.850 align:start position:0% on the specific type of function that they<06:28:29.280> provide<06:28:29.780> for<06:28:30.780> instance<06:28:31.080> if<06:28:31.740> we're 06:28:31.850 --> 06:28:31.860 align:start position:0% they provide for instance if we're 06:28:31.860 --> 06:28:34.090 align:start position:0% they provide for instance if we're looking<06:28:32.100> at<06:28:32.340> protocols<06:28:32.940> that<06:28:33.120> are<06:28:33.298> dedicated 06:28:34.090 --> 06:28:34.100 align:start position:0% looking at protocols that are dedicated 06:28:34.100 --> 06:28:38.990 align:start position:0% looking at protocols that are dedicated to<06:28:35.100> transferring<06:28:36.000> files<06:28:36.480> such<06:28:37.200> as<06:28:37.440> FTP<06:28:38.218> or 06:28:38.990 --> 06:28:39.000 align:start position:0% to transferring files such as FTP or 06:28:39.000 --> 06:28:41.810 align:start position:0% to transferring files such as FTP or tftp<06:28:39.660> which<06:28:39.900> of<06:28:40.080> your<06:28:40.200> call<06:28:40.440> is<06:28:40.620> the<06:28:41.040> trivial 06:28:41.810 --> 06:28:41.820 align:start position:0% tftp which of your call is the trivial 06:28:41.820 --> 06:28:45.048 align:start position:0% tftp which of your call is the trivial FTP<06:28:42.798> then<06:28:43.798> there<06:28:44.040> are<06:28:44.160> also<06:28:44.400> protocols<06:28:44.878> that 06:28:45.048 --> 06:28:45.058 align:start position:0% FTP then there are also protocols that 06:28:45.058 --> 06:28:46.670 align:start position:0% FTP then there are also protocols that can<06:28:45.180> be<06:28:45.298> categorized<06:28:45.840> by<06:28:46.138> supporting 06:28:46.670 --> 06:28:46.680 align:start position:0% can be categorized by supporting 06:28:46.680 --> 06:28:49.430 align:start position:0% can be categorized by supporting services<06:28:47.400> so<06:28:48.360> some<06:28:48.540> of<06:28:48.660> those<06:28:48.840> are<06:28:49.200> going<06:28:49.260> to 06:28:49.430 --> 06:28:49.440 align:start position:0% services so some of those are going to 06:28:49.440 --> 06:28:51.470 align:start position:0% services so some of those are going to be<06:28:49.500> for<06:28:49.860> instance<06:28:50.040> DNS<06:28:50.638> the<06:28:50.878> domain<06:28:51.240> name 06:28:51.470 --> 06:28:51.480 align:start position:0% be for instance DNS the domain name 06:28:51.480 --> 06:28:52.850 align:start position:0% be for instance DNS the domain name service 06:28:52.850 --> 06:28:52.860 align:start position:0% service 06:28:52.860 --> 06:28:55.310 align:start position:0% service and<06:28:53.580> SNMP<06:28:54.360> which<06:28:54.660> is<06:28:54.780> for<06:28:55.020> management 06:28:55.310 --> 06:28:55.320 align:start position:0% and SNMP which is for management 06:28:55.320 --> 06:28:57.970 align:start position:0% and SNMP which is for management purposes 06:28:57.970 --> 06:28:57.980 align:start position:0% purposes 06:28:57.980 --> 06:29:01.850 align:start position:0% purposes or<06:28:58.980> even<06:28:59.218> boot<06:28:59.700> P<06:28:59.878> or<06:29:00.180> the<06:29:00.360> bootstrap<06:29:01.200> protocol 06:29:01.850 --> 06:29:01.860 align:start position:0% or even boot P or the bootstrap protocol 06:29:01.860 --> 06:29:04.670 align:start position:0% or even boot P or the bootstrap protocol now<06:29:02.520> just<06:29:02.760> like<06:29:02.878> the<06:29:03.180> OSI<06:29:03.660> models<06:29:04.200> application 06:29:04.670 --> 06:29:04.680 align:start position:0% now just like the OSI models application 06:29:04.680 --> 06:29:07.548 align:start position:0% now just like the OSI models application layer<06:29:05.100> this<06:29:05.638> tcpip<06:29:06.360> application<06:29:06.958> layer<06:29:07.320> is 06:29:07.548 --> 06:29:07.558 align:start position:0% layer this tcpip application layer is 06:29:07.558 --> 06:29:11.208 align:start position:0% layer this tcpip application layer is responsible<06:29:08.040> for<06:29:08.520> process<06:29:09.480> to<06:29:09.840> process<06:29:10.320> level 06:29:11.208 --> 06:29:11.218 align:start position:0% responsible for process to process level 06:29:11.218 --> 06:29:14.390 align:start position:0% responsible for process to process level data<06:29:11.878> communication<06:29:12.360> this<06:29:13.320> means<06:29:13.740> that<06:29:14.218> the 06:29:14.390 --> 06:29:14.400 align:start position:0% data communication this means that the 06:29:14.400 --> 06:29:16.548 align:start position:0% data communication this means that the application<06:29:14.878> itself<06:29:15.360> doesn't<06:29:15.780> necessarily 06:29:16.548 --> 06:29:16.558 align:start position:0% application itself doesn't necessarily 06:29:16.558 --> 06:29:18.410 align:start position:0% application itself doesn't necessarily reside<06:29:17.040> on<06:29:17.340> this<06:29:17.458> layer 06:29:18.410 --> 06:29:18.420 align:start position:0% reside on this layer 06:29:18.420 --> 06:29:21.110 align:start position:0% reside on this layer what<06:29:19.080> more<06:29:19.378> means<06:29:19.740> is<06:29:19.860> that<06:29:20.040> it<06:29:20.160> defines<06:29:20.700> what 06:29:21.110 --> 06:29:21.120 align:start position:0% what more means is that it defines what 06:29:21.120 --> 06:29:22.548 align:start position:0% what more means is that it defines what the<06:29:21.360> application<06:29:21.780> or<06:29:22.080> what<06:29:22.260> type<06:29:22.378> of 06:29:22.548 --> 06:29:22.558 align:start position:0% the application or what type of 06:29:22.558 --> 06:29:26.030 align:start position:0% the application or what type of application<06:29:23.040> can<06:29:23.700> be<06:29:23.940> utilized<06:29:24.660> depending<06:29:25.620> on 06:29:26.030 --> 06:29:26.040 align:start position:0% application can be utilized depending on 06:29:26.040 --> 06:29:28.690 align:start position:0% application can be utilized depending on the<06:29:26.218> protocol<06:29:26.520> so<06:29:27.180> for<06:29:27.360> example<06:29:27.680> SMTP 06:29:28.690 --> 06:29:28.700 align:start position:0% the protocol so for example SMTP 06:29:28.700 --> 06:29:30.770 align:start position:0% the protocol so for example SMTP specifies<06:29:29.700> that<06:29:30.000> outgoing<06:29:30.540> mail 06:29:30.770 --> 06:29:30.780 align:start position:0% specifies that outgoing mail 06:29:30.780 --> 06:29:32.570 align:start position:0% specifies that outgoing mail communication<06:29:31.378> with<06:29:31.680> the<06:29:31.798> mail<06:29:31.980> or<06:29:32.218> exchange 06:29:32.570 --> 06:29:32.580 align:start position:0% communication with the mail or exchange 06:29:32.580 --> 06:29:35.750 align:start position:0% communication with the mail or exchange server<06:29:33.000> and<06:29:33.718> IMAP<06:29:34.260> specifies<06:29:34.860> the<06:29:35.280> incoming 06:29:35.750 --> 06:29:35.760 align:start position:0% server and IMAP specifies the incoming 06:29:35.760 --> 06:29:37.490 align:start position:0% server and IMAP specifies the incoming mail<06:29:35.940> communication<06:29:36.540> with<06:29:36.780> the<06:29:36.958> mail<06:29:37.080> server 06:29:37.490 --> 06:29:37.500 align:start position:0% mail communication with the mail server 06:29:37.500 --> 06:29:40.128 align:start position:0% mail communication with the mail server also<06:29:38.458> remember<06:29:39.000> that<06:29:39.420> only<06:29:39.780> those 06:29:40.128 --> 06:29:40.138 align:start position:0% also remember that only those 06:29:40.138 --> 06:29:42.530 align:start position:0% also remember that only those applications<06:29:40.798> that<06:29:41.340> are<06:29:41.520> network<06:29:41.820> relatable 06:29:42.530 --> 06:29:42.540 align:start position:0% applications that are network relatable 06:29:42.540 --> 06:29:45.410 align:start position:0% applications that are network relatable are<06:29:43.378> going<06:29:43.620> to<06:29:43.798> be<06:29:43.920> managed<06:29:44.280> this<06:29:44.580> layer<06:29:45.000> not 06:29:45.410 --> 06:29:45.420 align:start position:0% are going to be managed this layer not 06:29:45.420 --> 06:29:48.470 align:start position:0% are going to be managed this layer not necessarily<06:29:45.958> all<06:29:46.860> application<06:29:47.520> so<06:29:48.240> this 06:29:48.470 --> 06:29:48.480 align:start position:0% necessarily all application so this 06:29:48.480 --> 06:29:50.990 align:start position:0% necessarily all application so this layer's<06:29:49.020> role<06:29:49.260> is<06:29:49.378> more<06:29:49.620> towards<06:29:50.040> software 06:29:50.990 --> 06:29:51.000 align:start position:0% layer's role is more towards software 06:29:51.000 --> 06:29:52.910 align:start position:0% layer's role is more towards software applications<06:29:51.420> and<06:29:51.840> protocols<06:29:52.440> and<06:29:52.680> their 06:29:52.910 --> 06:29:52.920 align:start position:0% applications and protocols and their 06:29:52.920 --> 06:29:55.368 align:start position:0% applications and protocols and their interaction<06:29:53.340> with<06:29:53.700> the<06:29:53.940> user<06:29:54.298> it's<06:29:54.780> not<06:29:55.138> as 06:29:55.368 --> 06:29:55.378 align:start position:0% interaction with the user it's not as 06:29:55.378 --> 06:29:57.288 align:start position:0% interaction with the user it's not as concerned<06:29:55.920> with<06:29:56.218> the<06:29:56.458> formatting<06:29:57.000> or 06:29:57.288 --> 06:29:57.298 align:start position:0% concerned with the formatting or 06:29:57.298 --> 06:30:00.230 align:start position:0% concerned with the formatting or transmitting<06:29:58.020> the<06:29:58.200> data<06:29:58.558> across<06:29:59.218> the<06:29:59.458> media 06:30:00.230 --> 06:30:00.240 align:start position:0% transmitting the data across the media 06:30:00.240 --> 06:30:02.810 align:start position:0% transmitting the data across the media for<06:30:00.780> that<06:30:00.900> we<06:30:01.200> have<06:30:01.320> to<06:30:01.500> move<06:30:01.740> lower<06:30:02.280> down<06:30:02.580> into 06:30:02.810 --> 06:30:02.820 align:start position:0% for that we have to move lower down into 06:30:02.820 --> 06:30:06.350 align:start position:0% for that we have to move lower down into the<06:30:03.058> model<06:30:03.180> and<06:30:03.480> get<06:30:03.718> to<06:30:04.378> the<06:30:05.040> transport<06:30:05.400> layer 06:30:06.350 --> 06:30:06.360 align:start position:0% the model and get to the transport layer 06:30:06.360 --> 06:30:08.990 align:start position:0% the model and get to the transport layer now<06:30:06.718> on<06:30:06.958> the<06:30:07.138> transport<06:30:07.558> layer<06:30:08.040> of<06:30:08.218> the<06:30:08.340> tcpip 06:30:08.990 --> 06:30:09.000 align:start position:0% now on the transport layer of the tcpip 06:30:09.000 --> 06:30:11.628 align:start position:0% now on the transport layer of the tcpip model<06:30:09.360> we<06:30:09.900> have<06:30:10.020> two<06:30:10.440> main<06:30:10.798> protocols<06:30:11.400> that<06:30:11.520> we 06:30:11.628 --> 06:30:11.638 align:start position:0% model we have two main protocols that we 06:30:11.638 --> 06:30:14.090 align:start position:0% model we have two main protocols that we need<06:30:11.760> to<06:30:11.820> be<06:30:11.940> familiar<06:30:12.240> with<06:30:12.420> first<06:30:13.378> we<06:30:13.920> have 06:30:14.090 --> 06:30:14.100 align:start position:0% need to be familiar with first we have 06:30:14.100 --> 06:30:18.350 align:start position:0% need to be familiar with first we have the<06:30:14.580> transmission<06:30:15.020> control<06:30:16.020> protocol<06:30:16.680> or<06:30:17.638> TCP 06:30:18.350 --> 06:30:18.360 align:start position:0% the transmission control protocol or TCP 06:30:18.360 --> 06:30:20.930 align:start position:0% the transmission control protocol or TCP and<06:30:19.200> the<06:30:19.378> second<06:30:19.558> is<06:30:19.980> the<06:30:20.218> user<06:30:20.520> datagram 06:30:20.930 --> 06:30:20.940 align:start position:0% and the second is the user datagram 06:30:20.940 --> 06:30:23.868 align:start position:0% and the second is the user datagram protocol<06:30:21.540> or<06:30:22.320> UDP<06:30:22.680> let<06:30:23.160> me<06:30:23.280> just<06:30:23.458> write<06:30:23.638> those 06:30:23.868 --> 06:30:23.878 align:start position:0% protocol or UDP let me just write those 06:30:23.878 --> 06:30:26.390 align:start position:0% protocol or UDP let me just write those out<06:30:24.180> here<06:30:24.420> so<06:30:24.660> that<06:30:24.900> you<06:30:25.200> can<06:30:25.378> see<06:30:25.980> what<06:30:26.160> these 06:30:26.390 --> 06:30:26.400 align:start position:0% out here so that you can see what these 06:30:26.400 --> 06:30:41.570 align:start position:0% out here so that you can see what these stand<06:30:26.580> for<06:30:26.760> again 06:30:41.570 --> 06:30:41.580 align:start position:0% 06:30:41.580 --> 06:30:43.850 align:start position:0% now<06:30:42.120> on<06:30:42.360> this<06:30:42.660> layer<06:30:43.020> three<06:30:43.320> things<06:30:43.500> are<06:30:43.680> going 06:30:43.850 --> 06:30:43.860 align:start position:0% now on this layer three things are going 06:30:43.860 --> 06:30:44.690 align:start position:0% now on this layer three things are going on 06:30:44.690 --> 06:30:44.700 align:start position:0% on 06:30:44.700 --> 06:30:54.890 align:start position:0% on uh<06:30:45.480> data<06:30:45.958> verification 06:30:54.890 --> 06:30:54.900 align:start position:0% 06:30:54.900 --> 06:31:07.490 align:start position:0% error<06:30:55.620> checking 06:31:07.490 --> 06:31:07.500 align:start position:0% 06:31:07.500 --> 06:31:11.810 align:start position:0% and<06:31:08.160> flow<06:31:08.520> control 06:31:11.810 --> 06:31:11.820 align:start position:0% 06:31:11.820 --> 06:31:14.810 align:start position:0% now<06:31:12.298> our<06:31:12.480> two<06:31:12.780> heavy<06:31:13.138> hitting<06:31:13.500> Protocols<06:31:14.160> are 06:31:14.810 --> 06:31:14.820 align:start position:0% now our two heavy hitting Protocols are 06:31:14.820 --> 06:31:18.948 align:start position:0% now our two heavy hitting Protocols are done<06:31:15.120> in<06:31:15.660> very<06:31:15.840> different<06:31:16.080> ways<06:31:16.680> so<06:31:17.458> tcpap<06:31:18.420> as 06:31:18.948 --> 06:31:18.958 align:start position:0% done in very different ways so tcpap as 06:31:18.958 --> 06:31:20.448 align:start position:0% done in very different ways so tcpap as we've<06:31:19.200> talked<06:31:19.500> about<06:31:19.620> in<06:31:19.798> the<06:31:19.920> past<06:31:20.040> is<06:31:20.340> what 06:31:20.448 --> 06:31:20.458 align:start position:0% we've talked about in the past is what 06:31:20.458 --> 06:31:21.670 align:start position:0% we've talked about in the past is what we<06:31:20.580> call<06:31:20.700> connection 06:31:21.670 --> 06:31:21.680 align:start position:0% we call connection 06:31:21.680 --> 06:31:23.810 align:start position:0% we call connection oriented<06:31:22.680> which<06:31:23.218> means<06:31:23.458> there's<06:31:23.580> a 06:31:23.810 --> 06:31:23.820 align:start position:0% oriented which means there's a 06:31:23.820 --> 06:31:27.110 align:start position:0% oriented which means there's a guaranteed<06:31:24.420> delivery<06:31:24.900> whereas<06:31:25.860> UDP<06:31:26.280> is 06:31:27.110 --> 06:31:27.120 align:start position:0% guaranteed delivery whereas UDP is 06:31:27.120 --> 06:31:28.970 align:start position:0% guaranteed delivery whereas UDP is connection<06:31:27.298> last<06:31:27.718> which<06:31:28.020> means<06:31:28.320> it's<06:31:28.440> just<06:31:28.680> a 06:31:28.970 --> 06:31:28.980 align:start position:0% connection last which means it's just a 06:31:28.980 --> 06:31:31.190 align:start position:0% connection last which means it's just a best<06:31:29.218> effort<06:31:29.760> delivery 06:31:31.190 --> 06:31:31.200 align:start position:0% best effort delivery 06:31:31.200 --> 06:31:33.230 align:start position:0% best effort delivery UDP<06:31:31.558> doesn't<06:31:31.798> have<06:31:31.980> any<06:31:32.160> means<06:31:32.580> of<06:31:32.820> error 06:31:33.230 --> 06:31:33.240 align:start position:0% UDP doesn't have any means of error 06:31:33.240 --> 06:31:35.750 align:start position:0% UDP doesn't have any means of error checking<06:31:33.600> that's<06:31:33.780> one<06:31:34.080> of<06:31:34.280> tcp's<06:31:35.280> areas<06:31:35.580> of 06:31:35.750 --> 06:31:35.760 align:start position:0% checking that's one of tcp's areas of 06:31:35.760 --> 06:31:38.330 align:start position:0% checking that's one of tcp's areas of expertise<06:31:36.240> so<06:31:36.780> to<06:31:36.958> put<06:31:37.080> TCP<06:31:37.620> and<06:31:37.920> UDP<06:31:38.160> in 06:31:38.330 --> 06:31:38.340 align:start position:0% expertise so to put TCP and UDP in 06:31:38.340 --> 06:31:40.010 align:start position:0% expertise so to put TCP and UDP in perspective<06:31:38.700> I've<06:31:39.240> always<06:31:39.420> thought<06:31:39.660> about<06:31:39.780> it 06:31:40.010 --> 06:31:40.020 align:start position:0% perspective I've always thought about it 06:31:40.020 --> 06:31:42.350 align:start position:0% perspective I've always thought about it as<06:31:40.260> if<06:31:40.440> say<06:31:40.920> a<06:31:41.100> grade<06:31:41.400> school<06:31:41.638> teacher<06:31:42.120> needs 06:31:42.350 --> 06:31:42.360 align:start position:0% as if say a grade school teacher needs 06:31:42.360 --> 06:31:43.788 align:start position:0% as if say a grade school teacher needs to<06:31:42.480> send<06:31:42.660> a<06:31:42.840> note<06:31:42.958> to<06:31:43.138> a<06:31:43.320> student's<06:31:43.558> parent 06:31:43.788 --> 06:31:43.798 align:start position:0% to send a note to a student's parent 06:31:43.798 --> 06:31:45.890 align:start position:0% to send a note to a student's parent because<06:31:44.160> the<06:31:44.520> student<06:31:44.700> hadn't<06:31:45.540> turned<06:31:45.840> in 06:31:45.890 --> 06:31:45.900 align:start position:0% because the student hadn't turned in 06:31:45.900 --> 06:31:47.868 align:start position:0% because the student hadn't turned in their<06:31:46.020> homework<06:31:46.378> for<06:31:46.620> more<06:31:46.740> than<06:31:46.920> a<06:31:47.040> week<06:31:47.218> now 06:31:47.868 --> 06:31:47.878 align:start position:0% their homework for more than a week now 06:31:47.878 --> 06:31:49.670 align:start position:0% their homework for more than a week now the<06:31:48.180> teacher<06:31:48.420> can<06:31:48.540> send<06:31:48.780> the<06:31:48.900> note<06:31:49.080> one<06:31:49.320> of<06:31:49.500> two 06:31:49.670 --> 06:31:49.680 align:start position:0% the teacher can send the note one of two 06:31:49.680 --> 06:31:53.350 align:start position:0% the teacher can send the note one of two ways<06:31:49.980> the<06:31:50.280> first<06:31:50.458> is<06:31:51.180> through<06:31:51.600> UDP<06:31:51.900> or<06:31:52.558> the 06:31:53.350 --> 06:31:53.360 align:start position:0% ways the first is through UDP or the 06:31:53.360 --> 06:31:57.048 align:start position:0% ways the first is through UDP or the uninterested<06:31:54.360> doubtful<06:31:55.020> pre-teen<06:31:55.920> now<06:31:56.700> this 06:31:57.048 --> 06:31:57.058 align:start position:0% uninterested doubtful pre-teen now this 06:31:57.058 --> 06:31:58.730 align:start position:0% uninterested doubtful pre-teen now this UDP<06:31:57.420> is<06:31:57.600> certainly<06:31:57.900> going<06:31:58.080> to<06:31:58.260> make<06:31:58.440> it<06:31:58.558> home 06:31:58.730 --> 06:31:58.740 align:start position:0% UDP is certainly going to make it home 06:31:58.740 --> 06:32:00.890 align:start position:0% UDP is certainly going to make it home as<06:31:59.100> quickly<06:31:59.458> as<06:31:59.638> possible<06:32:00.058> but<06:32:00.540> whether<06:32:00.718> the 06:32:00.890 --> 06:32:00.900 align:start position:0% as quickly as possible but whether the 06:32:00.900 --> 06:32:02.510 align:start position:0% as quickly as possible but whether the message<06:32:01.080> gets<06:32:01.500> sent<06:32:01.620> to<06:32:01.798> the<06:32:01.920> parent<06:32:02.040> or<06:32:02.340> not 06:32:02.510 --> 06:32:02.520 align:start position:0% message gets sent to the parent or not 06:32:02.520 --> 06:32:04.788 align:start position:0% message gets sent to the parent or not it<06:32:02.878> really<06:32:03.058> isn't<06:32:03.660> udp's<06:32:04.138> biggest<06:32:04.260> concern 06:32:04.788 --> 06:32:04.798 align:start position:0% it really isn't udp's biggest concern 06:32:04.798 --> 06:32:08.150 align:start position:0% it really isn't udp's biggest concern getting<06:32:05.400> there<06:32:05.700> quickly<06:32:06.180> is<06:32:06.480> so<06:32:07.080> UDP<06:32:07.440> is<06:32:07.798> going 06:32:08.150 --> 06:32:08.160 align:start position:0% getting there quickly is so UDP is going 06:32:08.160 --> 06:32:09.830 align:start position:0% getting there quickly is so UDP is going to<06:32:08.218> have<06:32:08.340> you<06:32:08.458> that<06:32:08.760> quick 06:32:09.830 --> 06:32:09.840 align:start position:0% to have you that quick 06:32:09.840 --> 06:32:13.128 align:start position:0% to have you that quick but<06:32:10.620> not<06:32:10.920> necessarily<06:32:11.520> guaranteed<06:32:12.660> now 06:32:13.128 --> 06:32:13.138 align:start position:0% but not necessarily guaranteed now 06:32:13.138 --> 06:32:15.650 align:start position:0% but not necessarily guaranteed now meanwhile<06:32:13.500> the<06:32:13.680> other<06:32:13.798> method<06:32:14.160> TCP<06:32:14.820> or 06:32:15.650 --> 06:32:15.660 align:start position:0% meanwhile the other method TCP or 06:32:15.660 --> 06:32:18.708 align:start position:0% meanwhile the other method TCP or Teacher<06:32:16.260> Calls<06:32:16.798> parent<06:32:17.120> this<06:32:18.120> is<06:32:18.240> the<06:32:18.420> way<06:32:18.540> the 06:32:18.708 --> 06:32:18.718 align:start position:0% Teacher Calls parent this is the way the 06:32:18.718 --> 06:32:20.750 align:start position:0% Teacher Calls parent this is the way the teacher<06:32:19.020> has<06:32:19.260> a<06:32:19.500> guaranteed<06:32:20.040> delivery<06:32:20.520> of<06:32:20.638> the 06:32:20.750 --> 06:32:20.760 align:start position:0% teacher has a guaranteed delivery of the 06:32:20.760 --> 06:32:23.090 align:start position:0% teacher has a guaranteed delivery of the message<06:32:20.940> the<06:32:21.480> parents<06:32:21.900> aren't<06:32:22.020> home<06:32:22.378> the 06:32:23.090 --> 06:32:23.100 align:start position:0% message the parents aren't home the 06:32:23.100 --> 06:32:24.770 align:start position:0% message the parents aren't home the message<06:32:23.280> cannot<06:32:23.820> be<06:32:23.940> delivered<06:32:24.360> or<06:32:24.540> something 06:32:24.770 --> 06:32:24.780 align:start position:0% message cannot be delivered or something 06:32:24.780 --> 06:32:27.190 align:start position:0% message cannot be delivered or something happens<06:32:25.200> during<06:32:25.620> the<06:32:25.860> communication<06:32:26.340> process 06:32:27.190 --> 06:32:27.200 align:start position:0% happens during the communication process 06:32:27.200 --> 06:32:29.810 align:start position:0% happens during the communication process TCP<06:32:28.200> will<06:32:28.440> wait<06:32:28.680> and<06:32:29.100> attempt<06:32:29.400> to<06:32:29.520> send<06:32:29.700> the 06:32:29.810 --> 06:32:29.820 align:start position:0% TCP will wait and attempt to send the 06:32:29.820 --> 06:32:31.010 align:start position:0% TCP will wait and attempt to send the message<06:32:30.000> again 06:32:31.010 --> 06:32:31.020 align:start position:0% message again 06:32:31.020 --> 06:32:34.128 align:start position:0% message again so<06:32:31.740> whereas<06:32:32.700> TCP 06:32:34.128 --> 06:32:34.138 align:start position:0% so whereas TCP 06:32:34.138 --> 06:32:37.730 align:start position:0% so whereas TCP UDP<06:32:34.440> is<06:32:34.620> quick<06:32:34.798> TCP<06:32:35.458> is<06:32:35.638> guaranteed 06:32:37.730 --> 06:32:37.740 align:start position:0% UDP is quick TCP is guaranteed 06:32:37.740 --> 06:32:39.350 align:start position:0% UDP is quick TCP is guaranteed and<06:32:38.160> so<06:32:38.340> that's<06:32:38.458> sort<06:32:38.700> of<06:32:38.760> the<06:32:38.878> give<06:32:39.058> and<06:32:39.180> take 06:32:39.350 --> 06:32:39.360 align:start position:0% and so that's sort of the give and take 06:32:39.360 --> 06:32:40.368 align:start position:0% and so that's sort of the give and take there 06:32:40.368 --> 06:32:40.378 align:start position:0% there 06:32:40.378 --> 06:32:42.530 align:start position:0% there now<06:32:40.860> while<06:32:41.040> our<06:32:41.280> story<06:32:41.458> is<06:32:41.700> a<06:32:41.878> generalization 06:32:42.530 --> 06:32:42.540 align:start position:0% now while our story is a generalization 06:32:42.540 --> 06:32:44.448 align:start position:0% now while our story is a generalization it<06:32:42.780> really<06:32:42.958> touches<06:32:43.320> on<06:32:43.500> the<06:32:43.798> two<06:32:44.160> most 06:32:44.448 --> 06:32:44.458 align:start position:0% it really touches on the two most 06:32:44.458 --> 06:32:46.070 align:start position:0% it really touches on the two most important<06:32:44.878> characteristics<06:32:45.540> of<06:32:45.840> these 06:32:46.070 --> 06:32:46.080 align:start position:0% important characteristics of these 06:32:46.080 --> 06:32:49.490 align:start position:0% important characteristics of these protocols<06:32:46.680> now<06:32:47.280> there<06:32:47.638> are<06:32:47.760> a<06:32:48.000> few<06:32:48.180> other<06:32:48.540> uh 06:32:49.490 --> 06:32:49.500 align:start position:0% protocols now there are a few other uh 06:32:49.500 --> 06:32:52.010 align:start position:0% protocols now there are a few other uh specifics<06:32:50.100> about<06:32:50.280> TCP<06:32:51.120> that<06:32:51.480> are<06:32:51.600> are<06:32:51.780> really 06:32:52.010 --> 06:32:52.020 align:start position:0% specifics about TCP that are are really 06:32:52.020 --> 06:32:54.170 align:start position:0% specifics about TCP that are are really worth<06:32:52.260> mentioning<06:32:52.740> firstly<06:32:53.638> and<06:32:53.940> most 06:32:54.170 --> 06:32:54.180 align:start position:0% worth mentioning firstly and most 06:32:54.180 --> 06:32:57.170 align:start position:0% worth mentioning firstly and most importantly<06:32:54.660> we<06:32:55.320> have<06:32:55.500> reliability<06:32:56.340> like<06:32:56.940> we 06:32:57.170 --> 06:32:57.180 align:start position:0% importantly we have reliability like we 06:32:57.180 --> 06:32:59.090 align:start position:0% importantly we have reliability like we just<06:32:57.360> mentioned<06:32:57.780> how<06:32:58.200> it<06:32:58.378> accomplishes<06:32:58.920> this 06:32:59.090 --> 06:32:59.100 align:start position:0% just mentioned how it accomplishes this 06:32:59.100 --> 06:33:02.750 align:start position:0% just mentioned how it accomplishes this is<06:32:59.340> TCP<06:32:59.940> assigns<06:33:00.660> a<06:33:01.320> sequence<06:33:01.798> numbers<06:33:02.280> to 06:33:02.750 --> 06:33:02.760 align:start position:0% is TCP assigns a sequence numbers to 06:33:02.760 --> 06:33:04.490 align:start position:0% is TCP assigns a sequence numbers to each<06:33:03.000> segment<06:33:03.360> of<06:33:03.600> data<06:33:03.900> and<06:33:04.138> the<06:33:04.320> receiving 06:33:04.490 --> 06:33:04.500 align:start position:0% each segment of data and the receiving 06:33:04.500 --> 06:33:06.708 align:start position:0% each segment of data and the receiving end<06:33:04.740> looks<06:33:05.160> for<06:33:05.280> these<06:33:05.520> sequence<06:33:05.878> numbers<06:33:06.120> and 06:33:06.708 --> 06:33:06.718 align:start position:0% end looks for these sequence numbers and 06:33:06.718 --> 06:33:08.750 align:start position:0% end looks for these sequence numbers and sends<06:33:07.080> what's<06:33:07.320> called<06:33:07.798> an<06:33:08.280> ack<06:33:08.580> or 06:33:08.750 --> 06:33:08.760 align:start position:0% sends what's called an ack or 06:33:08.760 --> 06:33:10.548 align:start position:0% sends what's called an ack or acknowledgment<06:33:09.420> message 06:33:10.548 --> 06:33:10.558 align:start position:0% acknowledgment message 06:33:10.558 --> 06:33:12.530 align:start position:0% acknowledgment message which<06:33:11.040> is<06:33:11.160> something<06:33:11.580> important<06:33:12.000> that<06:33:12.240> you<06:33:12.420> do 06:33:12.530 --> 06:33:12.540 align:start position:0% which is something important that you do 06:33:12.540 --> 06:33:13.788 align:start position:0% which is something important that you do want<06:33:12.780> to 06:33:13.788 --> 06:33:13.798 align:start position:0% want to 06:33:13.798 --> 06:33:14.448 align:start position:0% want to um 06:33:14.448 --> 06:33:14.458 align:start position:0% um 06:33:14.458 --> 06:33:16.490 align:start position:0% um be<06:33:15.058> familiar<06:33:15.420> with<06:33:15.480> and<06:33:15.718> you<06:33:15.900> might<06:33:16.020> also<06:33:16.320> see 06:33:16.490 --> 06:33:16.500 align:start position:0% be familiar with and you might also see 06:33:16.500 --> 06:33:17.690 align:start position:0% be familiar with and you might also see that<06:33:16.740> as<06:33:16.920> a 06:33:17.690 --> 06:33:17.700 align:start position:0% that as a 06:33:17.700 --> 06:33:21.170 align:start position:0% that as a sin<06:33:18.540> act<06:33:18.780> which<06:33:19.320> is<06:33:19.440> the<06:33:19.558> synchronization<06:33:20.340> and 06:33:21.170 --> 06:33:21.180 align:start position:0% sin act which is the synchronization and 06:33:21.180 --> 06:33:22.910 align:start position:0% sin act which is the synchronization and that<06:33:21.298> act<06:33:21.480> message<06:33:21.780> is<06:33:22.020> sent<06:33:22.200> when<06:33:22.440> the<06:33:22.620> data 06:33:22.910 --> 06:33:22.920 align:start position:0% that act message is sent when the data 06:33:22.920 --> 06:33:25.250 align:start position:0% that act message is sent when the data is<06:33:23.040> successfully<06:33:23.638> received<06:33:24.240> now<06:33:24.660> the<06:33:24.840> sending 06:33:25.250 --> 06:33:25.260 align:start position:0% is successfully received now the sending 06:33:25.260 --> 06:33:27.350 align:start position:0% is successfully received now the sending transport<06:33:25.798> layer<06:33:26.280> doesn't<06:33:26.520> receive<06:33:27.058> the 06:33:27.350 --> 06:33:27.360 align:start position:0% transport layer doesn't receive the 06:33:27.360 --> 06:33:29.390 align:start position:0% transport layer doesn't receive the accurate<06:33:27.840> acknowledgment<06:33:28.378> message<06:33:28.798> then 06:33:29.390 --> 06:33:29.400 align:start position:0% accurate acknowledgment message then 06:33:29.400 --> 06:33:31.010 align:start position:0% accurate acknowledgment message then it's<06:33:29.580> going<06:33:29.760> to<06:33:29.878> re-transmit<06:33:30.600> the<06:33:30.840> Lost 06:33:31.010 --> 06:33:31.020 align:start position:0% it's going to re-transmit the Lost 06:33:31.020 --> 06:33:33.770 align:start position:0% it's going to re-transmit the Lost segment<06:33:31.580> secondly<06:33:32.580> we<06:33:32.940> have<06:33:33.058> data<06:33:33.540> flow 06:33:33.770 --> 06:33:33.780 align:start position:0% segment secondly we have data flow 06:33:33.780 --> 06:33:35.750 align:start position:0% segment secondly we have data flow control<06:33:34.080> which<06:33:34.620> is<06:33:34.740> we've<06:33:35.100> already<06:33:35.218> mentioned 06:33:35.750 --> 06:33:35.760 align:start position:0% control which is we've already mentioned 06:33:35.760 --> 06:33:38.150 align:start position:0% control which is we've already mentioned this<06:33:36.420> is<06:33:36.540> important<06:33:37.138> in<06:33:37.320> as<06:33:37.558> networking 06:33:38.150 --> 06:33:38.160 align:start position:0% this is important in as networking 06:33:38.160 --> 06:33:40.970 align:start position:0% this is important in as networking devices<06:33:38.458> are<06:33:38.820> not<06:33:39.180> always<06:33:39.660> going<06:33:40.440> to<06:33:40.620> operate 06:33:40.970 --> 06:33:40.980 align:start position:0% devices are not always going to operate 06:33:40.980 --> 06:33:43.070 align:start position:0% devices are not always going to operate at<06:33:41.160> the<06:33:41.280> same<06:33:41.458> speeds<06:33:42.000> and<06:33:42.420> without<06:33:42.540> flow 06:33:43.070 --> 06:33:43.080 align:start position:0% at the same speeds and without flow 06:33:43.080 --> 06:33:46.070 align:start position:0% at the same speeds and without flow control<06:33:43.320> slower<06:33:43.860> devices<06:33:44.280> might<06:33:44.700> overrun<06:33:45.420> by 06:33:46.070 --> 06:33:46.080 align:start position:0% control slower devices might overrun by 06:33:46.080 --> 06:33:48.590 align:start position:0% control slower devices might overrun by might<06:33:46.378> be<06:33:46.680> overrun<06:33:47.160> with<06:33:47.520> data<06:33:47.940> causing 06:33:48.590 --> 06:33:48.600 align:start position:0% might be overrun with data causing 06:33:48.600 --> 06:33:51.170 align:start position:0% might be overrun with data causing Network<06:33:49.020> downtime<06:33:49.740> thirdly<06:33:50.700> we<06:33:51.058> have 06:33:51.170 --> 06:33:51.180 align:start position:0% Network downtime thirdly we have 06:33:51.180 --> 06:33:53.390 align:start position:0% Network downtime thirdly we have something<06:33:51.360> called<06:33:51.718> segmentation<06:33:52.558> and 06:33:53.390 --> 06:33:53.400 align:start position:0% something called segmentation and 06:33:53.400 --> 06:33:55.670 align:start position:0% something called segmentation and segmentation<06:33:54.120> occurs<06:33:54.718> at<06:33:54.958> this<06:33:55.138> layer<06:33:55.440> taking 06:33:55.670 --> 06:33:55.680 align:start position:0% segmentation occurs at this layer taking 06:33:55.680 --> 06:33:58.190 align:start position:0% segmentation occurs at this layer taking the<06:33:56.160> tedious<06:33:56.638> task<06:33:56.940> away<06:33:57.540> from<06:33:57.958> the 06:33:58.190 --> 06:33:58.200 align:start position:0% the tedious task away from the 06:33:58.200 --> 06:34:00.530 align:start position:0% the tedious task away from the application<06:33:58.620> layer<06:33:59.100> of<06:33:59.638> sectioning<06:34:00.120> the<06:34:00.240> data 06:34:00.530 --> 06:34:00.540 align:start position:0% application layer of sectioning the data 06:34:00.540 --> 06:34:03.350 align:start position:0% application layer of sectioning the data into<06:34:00.780> pieces<06:34:01.320> or<06:34:01.680> segments<06:34:02.218> these<06:34:03.000> segments 06:34:03.350 --> 06:34:03.360 align:start position:0% into pieces or segments these segments 06:34:03.360 --> 06:34:05.330 align:start position:0% into pieces or segments these segments can<06:34:03.540> then<06:34:03.660> get<06:34:03.900> sent<06:34:04.200> to<06:34:04.680> the<06:34:04.798> next<06:34:04.980> layer 06:34:05.330 --> 06:34:05.340 align:start position:0% can then get sent to the next layer 06:34:05.340 --> 06:34:07.788 align:start position:0% can then get sent to the next layer below<06:34:05.760> to<06:34:06.000> be<06:34:06.180> prepared<06:34:06.718> for<06:34:07.080> transmittal 06:34:07.788 --> 06:34:07.798 align:start position:0% below to be prepared for transmittal 06:34:07.798 --> 06:34:10.368 align:start position:0% below to be prepared for transmittal across<06:34:08.458> the<06:34:08.760> media<06:34:09.600> so<06:34:10.020> the<06:34:10.260> final 06:34:10.368 --> 06:34:10.378 align:start position:0% across the media so the final 06:34:10.378 --> 06:34:13.310 align:start position:0% across the media so the final consideration<06:34:11.040> for<06:34:11.340> TCP<06:34:11.940> is<06:34:12.540> in<06:34:12.660> order<06:34:12.840> for<06:34:13.080> an 06:34:13.310 --> 06:34:13.320 align:start position:0% consideration for TCP is in order for an 06:34:13.320 --> 06:34:15.530 align:start position:0% consideration for TCP is in order for an application<06:34:13.740> to<06:34:14.100> be<06:34:14.160> able<06:34:14.400> to<06:34:14.580> utilize<06:34:15.240> this 06:34:15.530 --> 06:34:15.540 align:start position:0% application to be able to utilize this 06:34:15.540 --> 06:34:18.470 align:start position:0% application to be able to utilize this protocol<06:34:15.900> a<06:34:16.798> connection<06:34:16.980> between<06:34:17.520> port 06:34:18.470 --> 06:34:18.480 align:start position:0% protocol a connection between port 06:34:18.480 --> 06:34:20.750 align:start position:0% protocol a connection between port numbers<06:34:18.780> has<06:34:19.260> to<06:34:19.440> be<06:34:19.558> established<06:34:20.100> the 06:34:20.750 --> 06:34:20.760 align:start position:0% numbers has to be established the 06:34:20.760 --> 06:34:22.730 align:start position:0% numbers has to be established the devices<06:34:20.940> try<06:34:21.360> to<06:34:21.480> create<06:34:21.718> this<06:34:22.080> session<06:34:22.260> using 06:34:22.730 --> 06:34:22.740 align:start position:0% devices try to create this session using 06:34:22.740 --> 06:34:26.330 align:start position:0% devices try to create this session using a<06:34:22.980> combination<06:34:23.458> of<06:34:24.180> an<06:34:24.360> IP<06:34:24.660> address<06:34:25.040> and<06:34:26.040> a 06:34:26.330 --> 06:34:26.340 align:start position:0% a combination of an IP address and a 06:34:26.340 --> 06:34:28.610 align:start position:0% a combination of an IP address and a port<06:34:26.520> number<06:34:26.820> now<06:34:27.660> this<06:34:27.900> combination<06:34:28.320> is 06:34:28.610 --> 06:34:28.620 align:start position:0% port number now this combination is 06:34:28.620 --> 06:34:30.590 align:start position:0% port number now this combination is called<06:34:28.860> a<06:34:29.400> socket 06:34:30.590 --> 06:34:30.600 align:start position:0% called a socket 06:34:30.600 --> 06:34:32.270 align:start position:0% called a socket in<06:34:31.080> the<06:34:31.200> future<06:34:31.320> modules<06:34:31.798> we're<06:34:31.980> going<06:34:32.160> to 06:34:32.270 --> 06:34:32.280 align:start position:0% in the future modules we're going to 06:34:32.280 --> 06:34:35.150 align:start position:0% in the future modules we're going to look<06:34:32.400> at<06:34:32.638> at<06:34:32.940> referencing<06:34:33.660> TCP<06:34:34.320> and<06:34:34.680> UDP<06:34:34.980> as 06:34:35.150 --> 06:34:35.160 align:start position:0% look at at referencing TCP and UDP as 06:34:35.160 --> 06:34:36.770 align:start position:0% look at at referencing TCP and UDP as well<06:34:35.340> as<06:34:35.458> going<06:34:35.638> a<06:34:35.878> bit<06:34:36.000> more<06:34:36.298> further<06:34:36.600> into 06:34:36.770 --> 06:34:36.780 align:start position:0% well as going a bit more further into 06:34:36.780 --> 06:34:38.628 align:start position:0% well as going a bit more further into explaining<06:34:37.320> how<06:34:37.920> they<06:34:38.100> function<06:34:38.400> and 06:34:38.628 --> 06:34:38.638 align:start position:0% explaining how they function and 06:34:38.638 --> 06:34:40.548 align:start position:0% explaining how they function and interact<06:34:39.000> with<06:34:39.120> different<06:34:39.360> protocols<06:34:40.020> but 06:34:40.548 --> 06:34:40.558 align:start position:0% interact with different protocols but 06:34:40.558 --> 06:34:45.470 align:start position:0% interact with different protocols but what<06:34:40.680> you<06:34:40.860> see<06:34:41.040> here<06:34:41.340> is<06:34:42.058> the<06:34:42.540> IP<06:34:42.900> address 06:34:45.470 --> 06:34:45.480 align:start position:0% 06:34:45.480 --> 06:34:48.530 align:start position:0% on<06:34:46.200> a<06:34:46.440> specific<06:34:46.680> port<06:34:47.100> number<06:34:47.400> so<06:34:48.180> we<06:34:48.360> know 06:34:48.530 --> 06:34:48.540 align:start position:0% on a specific port number so we know 06:34:48.540 --> 06:34:51.890 align:start position:0% on a specific port number so we know based<06:34:48.958> on<06:34:49.080> this<06:34:49.260> port<06:34:49.440> number<06:34:49.760> what<06:34:50.760> the 06:34:51.890 --> 06:34:51.900 align:start position:0% based on this port number what the 06:34:51.900 --> 06:34:53.270 align:start position:0% based on this port number what the connection 06:34:53.270 --> 06:34:53.280 align:start position:0% connection 06:34:53.280 --> 06:34:55.430 align:start position:0% connection is<06:34:53.700> trying<06:34:53.878> to<06:34:54.058> attempt<06:34:54.420> and<06:34:55.020> whether<06:34:55.200> or<06:34:55.440> not 06:34:55.430 --> 06:34:55.440 align:start position:0% is trying to attempt and whether or not 06:34:55.440 --> 06:34:57.288 align:start position:0% is trying to attempt and whether or not it's<06:34:55.680> TCP<06:34:56.160> or<06:34:56.458> UDP<06:34:56.700> we<06:34:56.878> know<06:34:57.000> whether<06:34:57.120> it's 06:34:57.288 --> 06:34:57.298 align:start position:0% it's TCP or UDP we know whether it's 06:34:57.298 --> 06:35:00.010 align:start position:0% it's TCP or UDP we know whether it's connection<06:34:57.540> oriented<06:34:58.260> or<06:34:58.500> connection<06:34:58.740> less 06:35:00.010 --> 06:35:00.020 align:start position:0% connection oriented or connection less 06:35:00.020 --> 06:35:03.230 align:start position:0% connection oriented or connection less the<06:35:01.020> internet<06:35:01.138> layer<06:35:01.680> of<06:35:01.920> the<06:35:02.160> tcpip<06:35:02.878> model 06:35:03.230 --> 06:35:03.240 align:start position:0% the internet layer of the tcpip model 06:35:03.240 --> 06:35:05.690 align:start position:0% the internet layer of the tcpip model corresponds<06:35:04.200> directly<06:35:04.860> to<06:35:05.218> the<06:35:05.458> network 06:35:05.690 --> 06:35:05.700 align:start position:0% corresponds directly to the network 06:35:05.700 --> 06:35:08.810 align:start position:0% corresponds directly to the network layer<06:35:06.180> of<06:35:06.480> the<06:35:06.660> OSI<06:35:07.138> model<06:35:07.500> now<06:35:08.280> the<06:35:08.458> data 06:35:08.810 --> 06:35:08.820 align:start position:0% layer of the OSI model now the data 06:35:08.820 --> 06:35:11.150 align:start position:0% layer of the OSI model now the data terminology<06:35:09.240> on<06:35:09.600> this<06:35:09.780> layer<06:35:10.260> as<06:35:10.740> I<06:35:10.920> think<06:35:11.040> we 06:35:11.150 --> 06:35:11.160 align:start position:0% terminology on this layer as I think we 06:35:11.160 --> 06:35:12.770 align:start position:0% terminology on this layer as I think we discussed<06:35:11.458> when<06:35:11.638> we<06:35:11.820> talked<06:35:12.000> about<06:35:12.120> the<06:35:12.298> OSI 06:35:12.770 --> 06:35:12.780 align:start position:0% discussed when we talked about the OSI 06:35:12.780 --> 06:35:16.430 align:start position:0% discussed when we talked about the OSI model<06:35:13.020> is<06:35:13.920> a<06:35:14.280> datagram 06:35:16.430 --> 06:35:16.440 align:start position:0% model is a datagram 06:35:16.440 --> 06:35:18.830 align:start position:0% model is a datagram now<06:35:16.980> as<06:35:17.218> the<06:35:17.520> internet<06:35:17.638> layer<06:35:18.240> relates 06:35:18.830 --> 06:35:18.840 align:start position:0% now as the internet layer relates 06:35:18.840 --> 06:35:20.930 align:start position:0% now as the internet layer relates directly<06:35:19.260> to<06:35:19.558> the<06:35:19.740> network<06:35:19.860> layer<06:35:20.340> which<06:35:20.760> if 06:35:20.930 --> 06:35:20.940 align:start position:0% directly to the network layer which if 06:35:20.940 --> 06:35:21.948 align:start position:0% directly to the network layer which if you<06:35:21.058> recall 06:35:21.948 --> 06:35:21.958 align:start position:0% you recall 06:35:21.958 --> 06:35:24.948 align:start position:0% you recall was<06:35:22.740> layer<06:35:23.280> three<06:35:23.580> we<06:35:24.240> can<06:35:24.420> a<06:35:24.718> little<06:35:24.780> more 06:35:24.948 --> 06:35:24.958 align:start position:0% was layer three we can a little more 06:35:24.958 --> 06:35:26.690 align:start position:0% was layer three we can a little more easily<06:35:25.440> understand<06:35:25.680> a<06:35:26.100> few<06:35:26.218> things<06:35:26.400> that 06:35:26.690 --> 06:35:26.700 align:start position:0% easily understand a few things that 06:35:26.700 --> 06:35:29.150 align:start position:0% easily understand a few things that happen<06:35:26.940> on<06:35:27.240> this<06:35:27.360> layer<06:35:27.660> first<06:35:28.440> it<06:35:28.798> tells<06:35:29.040> us 06:35:29.150 --> 06:35:29.160 align:start position:0% happen on this layer first it tells us 06:35:29.160 --> 06:35:31.788 align:start position:0% happen on this layer first it tells us that<06:35:29.400> this<06:35:29.580> layer<06:35:29.940> is<06:35:30.240> responsible<06:35:30.900> for 06:35:31.788 --> 06:35:31.798 align:start position:0% that this layer is responsible for 06:35:31.798 --> 06:35:34.788 align:start position:0% that this layer is responsible for routing<06:35:32.280> if<06:35:32.878> you<06:35:33.058> recall<06:35:33.420> layer<06:35:33.900> 3<06:35:34.080> devices 06:35:34.788 --> 06:35:34.798 align:start position:0% routing if you recall layer 3 devices 06:35:34.798 --> 06:35:39.890 align:start position:0% routing if you recall layer 3 devices for<06:35:35.340> OSI<06:35:35.878> are<06:35:36.360> routers 06:35:39.890 --> 06:35:39.900 align:start position:0% 06:35:39.900 --> 06:35:43.310 align:start position:0% this<06:35:40.500> means<06:35:40.860> that<06:35:41.218> it<06:35:41.458> ensures<06:35:42.058> the<06:35:42.958> typically 06:35:43.310 --> 06:35:43.320 align:start position:0% this means that it ensures the typically 06:35:43.320 --> 06:35:47.090 align:start position:0% this means that it ensures the typically fastest<06:35:44.218> and<06:35:44.700> best<06:35:45.058> path<06:35:45.600> from<06:35:46.378> the<06:35:46.620> source<06:35:46.920> to 06:35:47.090 --> 06:35:47.100 align:start position:0% fastest and best path from the source to 06:35:47.100 --> 06:35:48.470 align:start position:0% fastest and best path from the source to the<06:35:47.218> destination 06:35:48.470 --> 06:35:48.480 align:start position:0% the destination 06:35:48.480 --> 06:35:50.990 align:start position:0% the destination this<06:35:48.840> layer<06:35:49.200> is<06:35:49.320> also<06:35:49.558> responsible<06:35:50.040> for<06:35:50.520> data 06:35:50.990 --> 06:35:51.000 align:start position:0% this layer is also responsible for data 06:35:51.000 --> 06:35:53.390 align:start position:0% this layer is also responsible for data addressing<06:35:51.718> and<06:35:52.200> if<06:35:52.378> you<06:35:52.500> recall<06:35:52.860> with<06:35:53.100> data 06:35:53.390 --> 06:35:53.400 align:start position:0% addressing and if you recall with data 06:35:53.400 --> 06:35:54.948 align:start position:0% addressing and if you recall with data addressing<06:35:53.878> we're<06:35:54.058> dealing<06:35:54.360> with<06:35:54.600> the<06:35:54.780> second 06:35:54.948 --> 06:35:54.958 align:start position:0% addressing we're dealing with the second 06:35:54.958 --> 06:36:01.548 align:start position:0% addressing we're dealing with the second part<06:35:55.260> of<06:35:55.500> TCP<06:35:56.360> IP<06:35:57.360> which<06:35:57.900> is<06:35:58.020> the<06:35:58.378> internet 06:36:01.548 --> 06:36:01.558 align:start position:0% 06:36:01.558 --> 06:36:04.850 align:start position:0% protocol<06:36:02.480> aptly<06:36:03.480> name<06:36:03.718> send<06:36:04.080> is<06:36:04.378> since<06:36:04.558> it<06:36:04.798> is 06:36:04.850 --> 06:36:04.860 align:start position:0% protocol aptly name send is since it is 06:36:04.860 --> 06:36:07.070 align:start position:0% protocol aptly name send is since it is on<06:36:05.040> the<06:36:05.280> internet<06:36:05.458> layer<06:36:06.298> and<06:36:06.780> the<06:36:07.020> Internet 06:36:07.070 --> 06:36:07.080 align:start position:0% on the internet layer and the Internet 06:36:07.080 --> 06:36:08.690 align:start position:0% on the internet layer and the Internet Protocol<06:36:07.558> is<06:36:07.740> responsible<06:36:08.160> for<06:36:08.400> a<06:36:08.580> couple 06:36:08.690 --> 06:36:08.700 align:start position:0% Protocol is responsible for a couple 06:36:08.700 --> 06:36:11.208 align:start position:0% Protocol is responsible for a couple main<06:36:09.000> functions<06:36:09.680> the<06:36:10.680> first<06:36:10.798> of<06:36:11.040> those 06:36:11.208 --> 06:36:11.218 align:start position:0% main functions the first of those 06:36:11.218 --> 06:36:13.910 align:start position:0% main functions the first of those functions<06:36:11.760> is<06:36:12.360> what<06:36:12.600> we<06:36:12.780> call<06:36:12.958> fragmentation 06:36:13.910 --> 06:36:13.920 align:start position:0% functions is what we call fragmentation 06:36:13.920 --> 06:36:16.670 align:start position:0% functions is what we call fragmentation it's<06:36:14.760> important<06:36:15.180> for<06:36:15.420> us<06:36:15.480> to<06:36:16.020> understand 06:36:16.670 --> 06:36:16.680 align:start position:0% it's important for us to understand 06:36:16.680 --> 06:36:21.708 align:start position:0% it's important for us to understand something<06:36:17.280> called<06:36:17.760> mtus<06:36:18.480> which<06:36:19.138> are<06:36:19.440> maximum 06:36:21.708 --> 06:36:21.718 align:start position:0% something called mtus which are maximum 06:36:21.718 --> 06:36:33.350 align:start position:0% something called mtus which are maximum transmission<06:36:22.620> units 06:36:33.350 --> 06:36:33.360 align:start position:0% 06:36:33.360 --> 06:36:35.810 align:start position:0% so<06:36:33.840> that<06:36:34.020> we<06:36:34.200> know<06:36:34.378> why<06:36:34.680> fragmentation<06:36:35.340> has<06:36:35.638> to 06:36:35.810 --> 06:36:35.820 align:start position:0% so that we know why fragmentation has to 06:36:35.820 --> 06:36:39.110 align:start position:0% so that we know why fragmentation has to occur<06:36:36.240> now<06:36:36.900> the<06:36:37.080> MTU<06:36:37.620> is<06:36:37.798> the<06:36:38.100> term<06:36:38.340> as<06:36:38.760> the 06:36:39.110 --> 06:36:39.120 align:start position:0% occur now the MTU is the term as the 06:36:39.120 --> 06:36:41.690 align:start position:0% occur now the MTU is the term as the name<06:36:39.298> implies<06:36:39.958> that's<06:36:40.620> used<06:36:40.798> to<06:36:40.980> define<06:36:41.160> the 06:36:41.690 --> 06:36:41.700 align:start position:0% name implies that's used to define the 06:36:41.700 --> 06:36:44.690 align:start position:0% name implies that's used to define the largest<06:36:42.058> size<06:36:42.600> of<06:36:43.378> increment<06:36:43.860> of<06:36:44.100> data<06:36:44.458> in 06:36:44.690 --> 06:36:44.700 align:start position:0% largest size of increment of data in 06:36:44.700 --> 06:36:46.850 align:start position:0% largest size of increment of data in bytes<06:36:45.120> that<06:36:45.360> can<06:36:45.480> pass<06:36:45.718> through<06:36:46.200> the<06:36:46.500> given 06:36:46.850 --> 06:36:46.860 align:start position:0% bytes that can pass through the given 06:36:46.860 --> 06:36:50.390 align:start position:0% bytes that can pass through the given Network<06:36:47.040> device<06:36:47.520> such<06:36:48.420> as<06:36:48.660> a<06:36:49.200> router<06:36:49.620> now 06:36:50.390 --> 06:36:50.400 align:start position:0% Network device such as a router now 06:36:50.400 --> 06:36:51.948 align:start position:0% Network device such as a router now often<06:36:50.760> data<06:36:51.058> is<06:36:51.120> going<06:36:51.298> to<06:36:51.420> need<06:36:51.600> to<06:36:51.780> pass 06:36:51.948 --> 06:36:51.958 align:start position:0% often data is going to need to pass 06:36:51.958 --> 06:36:55.490 align:start position:0% often data is going to need to pass through<06:36:52.200> networks<06:36:52.920> with<06:36:53.878> mtus<06:36:54.480> that<06:36:54.900> are<06:36:55.200> less 06:36:55.490 --> 06:36:55.500 align:start position:0% through networks with mtus that are less 06:36:55.500 --> 06:36:56.570 align:start position:0% through networks with mtus that are less than 06:36:56.570 --> 06:36:56.580 align:start position:0% than 06:36:56.580 --> 06:37:00.288 align:start position:0% than the<06:36:57.120> MTU<06:36:57.600> listed<06:36:58.020> on<06:36:58.920> that<06:36:59.040> device 06:37:00.288 --> 06:37:00.298 align:start position:0% the MTU listed on that device 06:37:00.298 --> 06:37:03.350 align:start position:0% the MTU listed on that device generally<06:37:01.200> even<06:37:01.500> uh<06:37:02.280> not<06:37:02.580> just<06:37:02.700> match<06:37:02.940> two<06:37:03.120> but 06:37:03.350 --> 06:37:03.360 align:start position:0% generally even uh not just match two but 06:37:03.360 --> 06:37:05.448 align:start position:0% generally even uh not just match two but the<06:37:03.540> lower<06:37:04.080> it<06:37:04.378> is<06:37:04.500> the<06:37:04.680> more<06:37:04.860> it's<06:37:05.040> preferred 06:37:05.448 --> 06:37:05.458 align:start position:0% the lower it is the more it's preferred 06:37:05.458 --> 06:37:07.070 align:start position:0% the lower it is the more it's preferred because<06:37:05.638> then<06:37:05.820> we<06:37:06.058> can<06:37:06.240> make<06:37:06.600> sure<06:37:06.780> that<06:37:06.958> it's 06:37:07.070 --> 06:37:07.080 align:start position:0% because then we can make sure that it's 06:37:07.080 --> 06:37:08.628 align:start position:0% because then we can make sure that it's not<06:37:07.260> going<06:37:07.378> to<06:37:07.500> have<06:37:07.620> a<06:37:07.740> problem<06:37:07.920> so<06:37:08.458> network 06:37:08.628 --> 06:37:08.638 align:start position:0% not going to have a problem so network 06:37:08.638 --> 06:37:10.610 align:start position:0% not going to have a problem so network devices<06:37:09.120> are<06:37:09.360> going<06:37:09.540> to<06:37:09.660> send<06:37:10.020> and<06:37:10.200> receive 06:37:10.610 --> 06:37:10.620 align:start position:0% devices are going to send and receive 06:37:10.620 --> 06:37:14.810 align:start position:0% devices are going to send and receive messages<06:37:11.058> or<06:37:12.058> responses<06:37:13.020> to<06:37:13.320> datagrams<06:37:13.980> that 06:37:14.810 --> 06:37:14.820 align:start position:0% messages or responses to datagrams that 06:37:14.820 --> 06:37:17.690 align:start position:0% messages or responses to datagrams that are<06:37:15.120> larger<06:37:15.600> than<06:37:15.840> the<06:37:16.020> device's<06:37:16.500> MTU 06:37:17.690 --> 06:37:17.700 align:start position:0% are larger than the device's MTU 06:37:17.700 --> 06:37:19.610 align:start position:0% are larger than the device's MTU in<06:37:18.298> these<06:37:18.480> instances<06:37:18.840> when<06:37:19.200> there<06:37:19.320> is<06:37:19.440> a 06:37:19.610 --> 06:37:19.620 align:start position:0% in these instances when there is a 06:37:19.620 --> 06:37:21.830 align:start position:0% in these instances when there is a datagram<06:37:19.920> that's<06:37:20.340> larger<06:37:20.820> than<06:37:20.940> the<06:37:21.120> MTU<06:37:21.600> of<06:37:21.660> a 06:37:21.830 --> 06:37:21.840 align:start position:0% datagram that's larger than the MTU of a 06:37:21.840 --> 06:37:25.628 align:start position:0% datagram that's larger than the MTU of a device<06:37:22.020> the<06:37:22.980> transmitting<06:37:23.760> internet<06:37:24.420> layer 06:37:25.628 --> 06:37:25.638 align:start position:0% device the transmitting internet layer 06:37:25.638 --> 06:37:29.270 align:start position:0% device the transmitting internet layer fragments<06:37:26.638> the<06:37:26.760> data<06:37:27.180> or<06:37:27.718> the<06:37:27.900> datagram<06:37:28.280> and 06:37:29.270 --> 06:37:29.280 align:start position:0% fragments the data or the datagram and 06:37:29.280 --> 06:37:32.690 align:start position:0% fragments the data or the datagram and then<06:37:29.520> tries<06:37:30.180> to<06:37:30.480> resend<06:37:31.320> it 06:37:32.690 --> 06:37:32.700 align:start position:0% then tries to resend it 06:37:32.700 --> 06:37:35.628 align:start position:0% then tries to resend it in<06:37:33.540> smaller<06:37:34.020> and<06:37:34.260> more<06:37:34.620> easily<06:37:35.100> manageable 06:37:35.628 --> 06:37:35.638 align:start position:0% in smaller and more easily manageable 06:37:35.638 --> 06:37:36.708 align:start position:0% in smaller and more easily manageable blocks 06:37:36.708 --> 06:37:36.718 align:start position:0% blocks 06:37:36.718 --> 06:37:39.170 align:start position:0% blocks so<06:37:37.138> once<06:37:37.378> the<06:37:37.440> data<06:37:37.740> is<06:37:37.860> fragmented<06:37:38.580> enough<06:37:38.820> to 06:37:39.170 --> 06:37:39.180 align:start position:0% so once the data is fragmented enough to 06:37:39.180 --> 06:37:41.690 align:start position:0% so once the data is fragmented enough to pass<06:37:39.360> through<06:37:39.660> the<06:37:39.958> remaining<06:37:40.440> devices<06:37:40.860> the 06:37:41.690 --> 06:37:41.700 align:start position:0% pass through the remaining devices the 06:37:41.700 --> 06:37:43.610 align:start position:0% pass through the remaining devices the receiving<06:37:42.000> ends<06:37:42.480> internet<06:37:42.660> layer<06:37:43.200> then 06:37:43.610 --> 06:37:43.620 align:start position:0% receiving ends internet layer then 06:37:43.620 --> 06:37:46.310 align:start position:0% receiving ends internet layer then pieces<06:37:44.100> together<06:37:44.340> those<06:37:44.760> fragments<06:37:45.480> during 06:37:46.310 --> 06:37:46.320 align:start position:0% pieces together those fragments during 06:37:46.320 --> 06:37:49.490 align:start position:0% pieces together those fragments during the<06:37:46.740> reassembly<06:37:47.340> process<06:37:47.820> now<06:37:48.780> in<06:37:49.020> the<06:37:49.200> header 06:37:49.490 --> 06:37:49.500 align:start position:0% the reassembly process now in the header 06:37:49.500 --> 06:37:51.410 align:start position:0% the reassembly process now in the header of<06:37:49.680> those<06:37:49.860> fragmented<06:37:50.458> datagrams<06:37:50.940> if<06:37:51.120> we<06:37:51.240> go 06:37:51.410 --> 06:37:51.420 align:start position:0% of those fragmented datagrams if we go 06:37:51.420 --> 06:37:53.690 align:start position:0% of those fragmented datagrams if we go back<06:37:51.660> just<06:37:52.020> a<06:37:52.138> bit<06:37:52.260> you'll<06:37:52.980> see<06:37:53.100> right<06:37:53.400> here 06:37:53.690 --> 06:37:53.700 align:start position:0% back just a bit you'll see right here 06:37:53.700 --> 06:37:55.850 align:start position:0% back just a bit you'll see right here the<06:37:54.298> header 06:37:55.850 --> 06:37:55.860 align:start position:0% the header 06:37:55.860 --> 06:37:57.350 align:start position:0% the header there<06:37:56.218> is<06:37:56.400> a<06:37:56.458> specific<06:37:56.700> field<06:37:56.940> that's<06:37:57.180> set 06:37:57.350 --> 06:37:57.360 align:start position:0% there is a specific field that's set 06:37:57.360 --> 06:38:03.230 align:start position:0% there is a specific field that's set aside<06:37:57.660> for<06:37:57.840> what<06:37:58.020> we<06:37:58.138> call<06:37:58.320> three<06:37:58.860> flag<06:37:59.638> bits 06:38:03.230 --> 06:38:03.240 align:start position:0% 06:38:03.240 --> 06:38:05.270 align:start position:0% the<06:38:03.840> first<06:38:03.958> flag<06:38:04.200> bit<06:38:04.500> is<06:38:04.740> reserved<06:38:05.160> and 06:38:05.270 --> 06:38:05.280 align:start position:0% the first flag bit is reserved and 06:38:05.280 --> 06:38:08.208 align:start position:0% the first flag bit is reserved and should<06:38:05.458> always<06:38:05.580> be<06:38:05.820> zero<06:38:06.540> the<06:38:07.138> second<06:38:07.320> is<06:38:08.040> the 06:38:08.208 --> 06:38:08.218 align:start position:0% should always be zero the second is the 06:38:08.218 --> 06:38:10.788 align:start position:0% should always be zero the second is the don't<06:38:08.340> fragment<06:38:08.940> or<06:38:09.298> the<06:38:09.420> DF<06:38:09.718> bit<06:38:09.958> now<06:38:10.620> either 06:38:10.788 --> 06:38:10.798 align:start position:0% don't fragment or the DF bit now either 06:38:10.798 --> 06:38:13.190 align:start position:0% don't fragment or the DF bit now either this<06:38:11.100> bit<06:38:11.218> is<06:38:11.520> off<06:38:11.820> or<06:38:12.180> zero<06:38:12.600> which<06:38:12.840> means 06:38:13.190 --> 06:38:13.200 align:start position:0% this bit is off or zero which means 06:38:13.200 --> 06:38:15.650 align:start position:0% this bit is off or zero which means fragment<06:38:13.920> this<06:38:14.160> datagram<06:38:14.520> or<06:38:15.058> on<06:38:15.298> meaning 06:38:15.650 --> 06:38:15.660 align:start position:0% fragment this datagram or on meaning 06:38:15.660 --> 06:38:18.110 align:start position:0% fragment this datagram or on meaning don't<06:38:15.958> fragment<06:38:16.500> this<06:38:16.740> datagram<06:38:17.100> the<06:38:17.940> third 06:38:18.110 --> 06:38:18.120 align:start position:0% don't fragment this datagram the third 06:38:18.120 --> 06:38:21.830 align:start position:0% don't fragment this datagram the third flag<06:38:18.298> bit<06:38:18.600> is<06:38:19.020> the<06:38:19.320> more<06:38:19.740> fragments<06:38:20.580> bit 06:38:21.830 --> 06:38:21.840 align:start position:0% flag bit is the more fragments bit 06:38:21.840 --> 06:38:23.570 align:start position:0% flag bit is the more fragments bit MF 06:38:23.570 --> 06:38:23.580 align:start position:0% MF 06:38:23.580 --> 06:38:25.788 align:start position:0% MF and<06:38:23.940> when<06:38:24.058> this<06:38:24.298> is<06:38:24.480> on<06:38:24.780> it<06:38:25.200> means<06:38:25.378> that<06:38:25.500> there 06:38:25.788 --> 06:38:25.798 align:start position:0% and when this is on it means that there 06:38:25.798 --> 06:38:27.890 align:start position:0% and when this is on it means that there are<06:38:25.920> more<06:38:26.100> fragments<06:38:26.700> on<06:38:26.820> the<06:38:27.000> way 06:38:27.890 --> 06:38:27.900 align:start position:0% are more fragments on the way 06:38:27.900 --> 06:38:29.810 align:start position:0% are more fragments on the way and<06:38:28.138> finally<06:38:28.378> when<06:38:28.558> the<06:38:28.680> MF<06:38:28.920> flag<06:38:29.100> is<06:38:29.340> off<06:38:29.580> it 06:38:29.810 --> 06:38:29.820 align:start position:0% and finally when the MF flag is off it 06:38:29.820 --> 06:38:31.610 align:start position:0% and finally when the MF flag is off it means<06:38:30.058> there<06:38:30.298> are<06:38:30.420> no<06:38:30.540> more<06:38:30.718> fragments<06:38:31.320> to<06:38:31.500> be 06:38:31.610 --> 06:38:31.620 align:start position:0% means there are no more fragments to be 06:38:31.620 --> 06:38:33.948 align:start position:0% means there are no more fragments to be sent<06:38:31.860> as<06:38:32.340> you<06:38:32.520> can<06:38:32.580> see<06:38:32.700> right<06:38:33.000> here 06:38:33.948 --> 06:38:33.958 align:start position:0% sent as you can see right here 06:38:33.958 --> 06:38:35.750 align:start position:0% sent as you can see right here and<06:38:34.320> that<06:38:34.500> there<06:38:34.680> were<06:38:34.860> never<06:38:34.980> any<06:38:35.160> fragments 06:38:35.750 --> 06:38:35.760 align:start position:0% and that there were never any fragments 06:38:35.760 --> 06:38:37.548 align:start position:0% and that there were never any fragments to<06:38:35.878> send<06:38:36.058> so<06:38:36.360> as<06:38:36.540> we<06:38:36.718> see<06:38:36.780> here<06:38:37.020> our<06:38:37.200> initial 06:38:37.548 --> 06:38:37.558 align:start position:0% to send so as we see here our initial 06:38:37.558 --> 06:38:41.930 align:start position:0% to send so as we see here our initial datagram<06:38:38.400> that<06:38:39.058> we<06:38:39.240> wanted<06:38:39.298> to<06:38:39.600> transmit 06:38:41.930 --> 06:38:41.940 align:start position:0% datagram that we wanted to transmit 06:38:41.940 --> 06:38:47.030 align:start position:0% datagram that we wanted to transmit had<06:38:42.840> an<06:38:43.320> MTU<06:38:43.878> that<06:38:44.878> was<06:38:45.240> too<06:38:45.840> large<06:38:46.080> to<06:38:46.378> send<06:38:46.558> it 06:38:47.030 --> 06:38:47.040 align:start position:0% had an MTU that was too large to send it 06:38:47.040 --> 06:38:47.830 align:start position:0% had an MTU that was too large to send it was 06:38:47.830 --> 06:38:47.840 align:start position:0% was 06:38:47.840 --> 06:38:50.750 align:start position:0% was 2500<06:38:48.840> and<06:38:49.500> it<06:38:49.620> was<06:38:49.740> too<06:38:49.920> large<06:38:50.100> therefore<06:38:50.580> to 06:38:50.750 --> 06:38:50.760 align:start position:0% 2500 and it was too large therefore to 06:38:50.760 --> 06:38:52.730 align:start position:0% 2500 and it was too large therefore to go<06:38:50.940> through<06:38:51.120> router<06:38:51.540> B<06:38:51.718> and<06:38:52.200> so<06:38:52.320> then<06:38:52.500> we 06:38:52.730 --> 06:38:52.740 align:start position:0% go through router B and so then we 06:38:52.740 --> 06:38:55.010 align:start position:0% go through router B and so then we fragmented<06:38:53.580> this<06:38:53.700> datagram<06:38:54.058> and<06:38:54.600> added<06:38:54.900> those 06:38:55.010 --> 06:38:55.020 align:start position:0% fragmented this datagram and added those 06:38:55.020 --> 06:38:57.590 align:start position:0% fragmented this datagram and added those bits<06:38:55.378> to<06:38:55.500> the<06:38:55.620> headers<06:38:55.980> of<06:38:56.280> the<06:38:56.458> fragments 06:38:57.590 --> 06:38:57.600 align:start position:0% bits to the headers of the fragments 06:38:57.600 --> 06:39:00.650 align:start position:0% bits to the headers of the fragments so<06:38:58.138> that's<06:38:59.100> how<06:38:59.458> this<06:38:59.760> all<06:38:59.940> works<06:39:00.360> and<06:39:00.540> that's 06:39:00.650 --> 06:39:00.660 align:start position:0% so that's how this all works and that's 06:39:00.660 --> 06:39:02.810 align:start position:0% so that's how this all works and that's why<06:39:00.900> fragmenting<06:39:01.500> is<06:39:01.680> so<06:39:01.798> important<06:39:02.160> now 06:39:02.810 --> 06:39:02.820 align:start position:0% why fragmenting is so important now 06:39:02.820 --> 06:39:04.250 align:start position:0% why fragmenting is so important now let's<06:39:02.940> take<06:39:03.180> a<06:39:03.298> look<06:39:03.420> at<06:39:03.718> a<06:39:03.840> networking 06:39:04.250 --> 06:39:04.260 align:start position:0% let's take a look at a networking 06:39:04.260 --> 06:39:05.868 align:start position:0% let's take a look at a networking problem<06:39:04.500> that<06:39:04.860> used<06:39:05.040> to<06:39:05.218> plague<06:39:05.520> Network 06:39:05.868 --> 06:39:05.878 align:start position:0% problem that used to plague Network 06:39:05.878 --> 06:39:07.910 align:start position:0% problem that used to plague Network engineers<06:39:06.420> and<06:39:06.718> technicians<06:39:07.320> that<06:39:07.558> has<06:39:07.680> to<06:39:07.860> do 06:39:07.910 --> 06:39:07.920 align:start position:0% engineers and technicians that has to do 06:39:07.920 --> 06:39:10.250 align:start position:0% engineers and technicians that has to do with<06:39:08.100> mtus<06:39:08.580> for<06:39:08.940> some<06:39:09.120> time<06:39:09.298> this<06:39:09.840> is<06:39:10.020> also 06:39:10.250 --> 06:39:10.260 align:start position:0% with mtus for some time this is also 06:39:10.260 --> 06:39:11.868 align:start position:0% with mtus for some time this is also something<06:39:10.440> that's<06:39:10.798> specifically<06:39:11.340> called<06:39:11.638> for 06:39:11.868 --> 06:39:11.878 align:start position:0% something that's specifically called for 06:39:11.878 --> 06:39:14.390 align:start position:0% something that's specifically called for on<06:39:12.058> the<06:39:12.180> network<06:39:12.298> plus<06:39:12.540> exam<06:39:12.958> now<06:39:13.680> a<06:39:14.160> black 06:39:14.390 --> 06:39:14.400 align:start position:0% on the network plus exam now a black 06:39:14.400 --> 06:39:16.610 align:start position:0% on the network plus exam now a black hole<06:39:14.878> router<06:39:15.298> is<06:39:15.718> the<06:39:15.840> name<06:39:15.958> given<06:39:16.320> to<06:39:16.440> a 06:39:16.610 --> 06:39:16.620 align:start position:0% hole router is the name given to a 06:39:16.620 --> 06:39:19.490 align:start position:0% hole router is the name given to a situation<06:39:17.040> where<06:39:17.400> a<06:39:17.638> datagram<06:39:17.940> is<06:39:18.360> sent<06:39:18.600> with 06:39:19.490 --> 06:39:19.500 align:start position:0% situation where a datagram is sent with 06:39:19.500 --> 06:39:22.548 align:start position:0% situation where a datagram is sent with an<06:39:19.680> MTU<06:39:20.160> that's<06:39:20.400> greater<06:39:21.058> than<06:39:21.420> the<06:39:21.660> MTU<06:39:22.200> of 06:39:22.548 --> 06:39:22.558 align:start position:0% an MTU that's greater than the MTU of 06:39:22.558 --> 06:39:26.030 align:start position:0% an MTU that's greater than the MTU of the<06:39:22.798> receiving<06:39:23.100> device<06:39:23.520> as<06:39:23.940> we<06:39:24.120> can<06:39:24.240> see<06:39:24.480> here 06:39:26.030 --> 06:39:26.040 align:start position:0% the receiving device as we can see here 06:39:26.040 --> 06:39:28.250 align:start position:0% the receiving device as we can see here now<06:39:26.520> when<06:39:26.760> the<06:39:26.940> destination<06:39:27.360> device<06:39:27.840> is 06:39:28.250 --> 06:39:28.260 align:start position:0% now when the destination device is 06:39:28.260 --> 06:39:31.190 align:start position:0% now when the destination device is unable<06:39:28.740> to<06:39:28.920> receive<06:39:29.458> the<06:39:29.760> IP<06:39:30.058> datagram 06:39:31.190 --> 06:39:31.200 align:start position:0% unable to receive the IP datagram 06:39:31.200 --> 06:39:34.610 align:start position:0% unable to receive the IP datagram it's<06:39:31.860> supposed<06:39:32.100> to<06:39:32.340> send<06:39:32.700> a<06:39:33.120> specific<06:39:33.620> icmp 06:39:34.610 --> 06:39:34.620 align:start position:0% it's supposed to send a specific icmp 06:39:34.620 --> 06:39:37.610 align:start position:0% it's supposed to send a specific icmp response<06:39:35.458> that<06:39:36.120> notifies<06:39:36.660> the<06:39:37.020> transmitting 06:39:37.610 --> 06:39:37.620 align:start position:0% response that notifies the transmitting 06:39:37.620 --> 06:39:40.788 align:start position:0% response that notifies the transmitting station<06:39:37.980> that<06:39:38.638> there's<06:39:38.878> an<06:39:39.298> MTU<06:39:39.958> mismatch 06:39:40.788 --> 06:39:40.798 align:start position:0% station that there's an MTU mismatch 06:39:40.798 --> 06:39:43.910 align:start position:0% station that there's an MTU mismatch this<06:39:41.760> can<06:39:41.878> be<06:39:42.000> due<06:39:42.180> to<06:39:42.360> a<06:39:42.600> variety<06:39:43.138> of<06:39:43.320> reasons 06:39:43.910 --> 06:39:43.920 align:start position:0% this can be due to a variety of reasons 06:39:43.920 --> 06:39:47.150 align:start position:0% this can be due to a variety of reasons one<06:39:44.520> of<06:39:44.638> which<06:39:44.820> could<06:39:45.180> be<06:39:45.420> as<06:39:46.138> simple<06:39:46.320> as<06:39:46.798> a 06:39:47.150 --> 06:39:47.160 align:start position:0% one of which could be as simple as a 06:39:47.160 --> 06:39:49.610 align:start position:0% one of which could be as simple as a firewall<06:39:47.878> that's<06:39:48.240> blocking<06:39:48.780> the<06:39:48.958> icmp 06:39:49.610 --> 06:39:49.620 align:start position:0% firewall that's blocking the icmp 06:39:49.620 --> 06:39:51.770 align:start position:0% firewall that's blocking the icmp response<06:39:50.160> and<06:39:50.280> by<06:39:50.520> the<06:39:50.638> way<06:39:50.760> when<06:39:51.420> we<06:39:51.600> talk 06:39:51.770 --> 06:39:51.780 align:start position:0% response and by the way when we talk 06:39:51.780 --> 06:39:54.470 align:start position:0% response and by the way when we talk about<06:39:51.958> icmp<06:39:52.920> we're<06:39:53.580> really<06:39:53.820> talking<06:39:54.120> about 06:39:54.470 --> 06:39:54.480 align:start position:0% about icmp we're really talking about 06:39:54.480 --> 06:39:57.410 align:start position:0% about icmp we're really talking about the<06:39:55.020> ping<06:39:55.320> utility<06:39:55.740> as<06:39:56.100> well<06:39:56.280> now<06:39:57.000> in<06:39:57.180> these 06:39:57.410 --> 06:39:57.420 align:start position:0% the ping utility as well now in these 06:39:57.420 --> 06:39:59.448 align:start position:0% the ping utility as well now in these cases<06:39:57.718> this<06:39:58.020> is<06:39:58.138> called<06:39:58.378> a<06:39:58.740> black<06:39:58.980> hole 06:39:59.448 --> 06:39:59.458 align:start position:0% cases this is called a black hole 06:39:59.458 --> 06:40:00.948 align:start position:0% cases this is called a black hole because<06:39:59.820> of<06:40:00.058> The<06:40:00.180> Disappearance<06:40:00.718> of 06:40:00.948 --> 06:40:00.958 align:start position:0% because of The Disappearance of 06:40:00.958 --> 06:40:03.350 align:start position:0% because of The Disappearance of datagrams<06:40:01.620> basically<06:40:02.458> as<06:40:02.700> you<06:40:02.820> can<06:40:02.940> see<06:40:03.058> I'm 06:40:03.350 --> 06:40:03.360 align:start position:0% datagrams basically as you can see I'm 06:40:03.360 --> 06:40:05.150 align:start position:0% datagrams basically as you can see I'm sending<06:40:03.718> the<06:40:03.840> data 06:40:05.150 --> 06:40:05.160 align:start position:0% sending the data 06:40:05.160 --> 06:40:07.730 align:start position:0% sending the data the<06:40:05.638> data<06:40:05.940> gets<06:40:06.240> here<06:40:06.360> the<06:40:06.958> device<06:40:07.080> the<06:40:07.440> router 06:40:07.730 --> 06:40:07.740 align:start position:0% the data gets here the device the router 06:40:07.740 --> 06:40:09.470 align:start position:0% the data gets here the device the router here<06:40:07.920> says<06:40:08.218> wait<06:40:08.340> a<06:40:08.520> minute<06:40:08.638> I<06:40:08.878> can't<06:40:09.000> fit<06:40:09.240> that 06:40:09.470 --> 06:40:09.480 align:start position:0% here says wait a minute I can't fit that 06:40:09.480 --> 06:40:12.650 align:start position:0% here says wait a minute I can't fit that 2500<06:40:10.138> MTU<06:40:10.680> through<06:40:10.860> my<06:40:11.040> 1500<06:40:11.638> sends<06:40:12.540> a 06:40:12.650 --> 06:40:12.660 align:start position:0% 2500 MTU through my 1500 sends a 06:40:12.660 --> 06:40:14.330 align:start position:0% 2500 MTU through my 1500 sends a response<06:40:13.138> but<06:40:13.378> for<06:40:13.620> some<06:40:13.740> reason<06:40:13.920> the 06:40:14.330 --> 06:40:14.340 align:start position:0% response but for some reason the 06:40:14.340 --> 06:40:15.708 align:start position:0% response but for some reason the response 06:40:15.708 --> 06:40:15.718 align:start position:0% response 06:40:15.718 --> 06:40:17.990 align:start position:0% response hits<06:40:16.260> this<06:40:16.620> firewall<06:40:17.040> and<06:40:17.400> doesn't<06:40:17.580> make<06:40:17.820> it 06:40:17.990 --> 06:40:18.000 align:start position:0% hits this firewall and doesn't make it 06:40:18.000 --> 06:40:20.510 align:start position:0% hits this firewall and doesn't make it back<06:40:18.180> to<06:40:18.360> the<06:40:18.480> router<06:40:18.780> and<06:40:19.200> so<06:40:19.440> the<06:40:19.980> data<06:40:20.280> is 06:40:20.510 --> 06:40:20.520 align:start position:0% back to the router and so the data is 06:40:20.520 --> 06:40:23.930 align:start position:0% back to the router and so the data is lost<06:40:20.878> into<06:40:21.360> this<06:40:21.718> black<06:40:22.200> hole<06:40:22.798> now<06:40:23.580> this<06:40:23.820> is 06:40:23.930 --> 06:40:23.940 align:start position:0% lost into this black hole now this is 06:40:23.940 --> 06:40:25.730 align:start position:0% lost into this black hole now this is called<06:40:24.180> a<06:40:24.480> black<06:40:24.600> hole<06:40:25.020> because<06:40:25.200> this 06:40:25.730 --> 06:40:25.740 align:start position:0% called a black hole because this 06:40:25.740 --> 06:40:29.090 align:start position:0% called a black hole because this datagram<06:40:26.420> disappears<06:40:27.420> as<06:40:28.138> if<06:40:28.378> it<06:40:28.680> were<06:40:28.798> sucked 06:40:29.090 --> 06:40:29.100 align:start position:0% datagram disappears as if it were sucked 06:40:29.100 --> 06:40:30.948 align:start position:0% datagram disappears as if it were sucked into<06:40:29.218> a<06:40:29.458> black<06:40:29.580> hole<06:40:30.000> now<06:40:30.540> there<06:40:30.718> are<06:40:30.840> some 06:40:30.948 --> 06:40:30.958 align:start position:0% into a black hole now there are some 06:40:30.958 --> 06:40:33.470 align:start position:0% into a black hole now there are some ways<06:40:31.320> to<06:40:31.500> detect<06:40:32.100> or<06:40:32.340> find<06:40:32.520> this<06:40:32.760> MTU<06:40:33.240> black 06:40:33.470 --> 06:40:33.480 align:start position:0% ways to detect or find this MTU black 06:40:33.480 --> 06:40:36.170 align:start position:0% ways to detect or find this MTU black hole<06:40:33.840> and<06:40:34.260> one<06:40:34.440> of<06:40:34.500> the<06:40:34.620> best<06:40:34.798> ways<06:40:35.218> is<06:40:35.700> to<06:40:36.000> use 06:40:36.170 --> 06:40:36.180 align:start position:0% hole and one of the best ways is to use 06:40:36.180 --> 06:40:39.788 align:start position:0% hole and one of the best ways is to use the<06:40:36.480> Ping<06:40:36.718> utility<06:40:37.280> and<06:40:38.280> specify<06:40:38.878> a<06:40:39.120> syntax 06:40:39.788 --> 06:40:39.798 align:start position:0% the Ping utility and specify a syntax 06:40:39.798 --> 06:40:43.850 align:start position:0% the Ping utility and specify a syntax that<06:40:40.798> sets<06:40:41.100> the<06:40:41.340> MTU<06:40:41.940> of<06:40:42.540> the<06:40:42.718> icmp<06:40:43.440> echo 06:40:43.850 --> 06:40:43.860 align:start position:0% that sets the MTU of the icmp echo 06:40:43.860 --> 06:40:46.310 align:start position:0% that sets the MTU of the icmp echo request<06:40:44.218> meaning<06:40:45.058> you<06:40:45.420> tell<06:40:45.600> it<06:40:45.718> I<06:40:46.020> want<06:40:46.200> to 06:40:46.310 --> 06:40:46.320 align:start position:0% request meaning you tell it I want to 06:40:46.320 --> 06:40:49.250 align:start position:0% request meaning you tell it I want to Ping<06:40:46.558> with<06:40:46.798> this<06:40:47.218> much<06:40:47.820> of<06:40:48.058> an<06:40:48.240> MTU<06:40:48.718> and<06:40:49.138> so 06:40:49.250 --> 06:40:49.260 align:start position:0% Ping with this much of an MTU and so 06:40:49.260 --> 06:40:50.990 align:start position:0% Ping with this much of an MTU and so then<06:40:49.440> we<06:40:49.620> can<06:40:49.740> see<06:40:49.980> if<06:40:50.218> the<06:40:50.340> Ping's<06:40:50.700> not<06:40:50.820> coming 06:40:50.990 --> 06:40:51.000 align:start position:0% then we can see if the Ping's not coming 06:40:51.000 --> 06:40:52.610 align:start position:0% then we can see if the Ping's not coming back<06:40:51.180> if<06:40:51.360> it's<06:40:51.540> coming<06:40:51.660> back<06:40:51.780> at<06:40:51.958> one<06:40:52.080> MTU<06:40:52.500> and 06:40:52.610 --> 06:40:52.620 align:start position:0% back if it's coming back at one MTU and 06:40:52.620 --> 06:40:54.708 align:start position:0% back if it's coming back at one MTU and not<06:40:52.740> another<06:40:52.920> then<06:40:53.580> we<06:40:53.878> know<06:40:54.000> oh<06:40:54.298> this<06:40:54.600> is 06:40:54.708 --> 06:40:54.718 align:start position:0% not another then we know oh this is 06:40:54.718 --> 06:40:56.570 align:start position:0% not another then we know oh this is what's<06:40:54.900> happening<06:40:55.260> right<06:40:55.620> here<06:40:55.798> and<06:40:56.218> we<06:40:56.400> can 06:40:56.570 --> 06:40:56.580 align:start position:0% what's happening right here and we can 06:40:56.580 --> 06:40:59.090 align:start position:0% what's happening right here and we can determine<06:40:57.120> uh<06:40:57.900> where<06:40:58.200> the<06:40:58.378> black<06:40:58.558> hole<06:40:58.980> is 06:40:59.090 --> 06:40:59.100 align:start position:0% determine uh where the black hole is 06:40:59.100 --> 06:41:01.010 align:start position:0% determine uh where the black hole is specifically<06:40:59.760> occurring 06:41:01.010 --> 06:41:01.020 align:start position:0% specifically occurring 06:41:01.020 --> 06:41:03.890 align:start position:0% specifically occurring now<06:41:01.558> on<06:41:01.798> the<06:41:01.920> bottom<06:41:02.160> of<06:41:02.340> the<06:41:02.458> tcpip<06:41:03.180> stack<06:41:03.660> is 06:41:03.890 --> 06:41:03.900 align:start position:0% now on the bottom of the tcpip stack is 06:41:03.900 --> 06:41:07.070 align:start position:0% now on the bottom of the tcpip stack is the<06:41:04.200> network<06:41:04.378> interface<06:41:05.218> layer<06:41:06.180> now<06:41:06.660> this 06:41:07.070 --> 06:41:07.080 align:start position:0% the network interface layer now this 06:41:07.080 --> 06:41:10.010 align:start position:0% the network interface layer now this layer<06:41:07.500> is<06:41:07.860> completely<06:41:08.340> dedicated<06:41:08.940> to<06:41:09.780> the 06:41:10.010 --> 06:41:10.020 align:start position:0% layer is completely dedicated to the 06:41:10.020 --> 06:41:12.530 align:start position:0% layer is completely dedicated to the actual<06:41:10.440> transfer<06:41:11.100> of<06:41:11.400> bits<06:41:11.878> across<06:41:12.420> the 06:41:12.530 --> 06:41:12.540 align:start position:0% actual transfer of bits across the 06:41:12.540 --> 06:41:14.990 align:start position:0% actual transfer of bits across the network<06:41:12.718> medium<06:41:13.320> the<06:41:14.160> network<06:41:14.340> interface 06:41:14.990 --> 06:41:15.000 align:start position:0% network medium the network interface 06:41:15.000 --> 06:41:17.868 align:start position:0% network medium the network interface layer<06:41:15.298> of<06:41:15.420> the<06:41:15.540> tcpip<06:41:16.260> model<06:41:16.878> directly 06:41:17.868 --> 06:41:17.878 align:start position:0% layer of the tcpip model directly 06:41:17.878 --> 06:41:22.490 align:start position:0% layer of the tcpip model directly correlates<06:41:18.600> to<06:41:19.500> the<06:41:19.860> physical 06:41:22.490 --> 06:41:22.500 align:start position:0% 06:41:22.500 --> 06:41:28.368 align:start position:0% and<06:41:23.218> the<06:41:23.638> data<06:41:24.000> link<06:41:24.120> layer 06:41:28.368 --> 06:41:28.378 align:start position:0% 06:41:28.378 --> 06:41:32.030 align:start position:0% of<06:41:28.860> the<06:41:29.040> OSI<06:41:29.520> model 06:41:32.030 --> 06:41:32.040 align:start position:0% 06:41:32.040 --> 06:41:33.708 align:start position:0% now<06:41:32.520> the<06:41:32.700> data<06:41:33.058> type<06:41:33.180> we're<06:41:33.420> going<06:41:33.540> to<06:41:33.660> be 06:41:33.708 --> 06:41:33.718 align:start position:0% now the data type we're going to be 06:41:33.718 --> 06:41:35.750 align:start position:0% now the data type we're going to be talking<06:41:33.900> about<06:41:34.080> on<06:41:34.378> this<06:41:34.558> layer<06:41:34.860> are<06:41:35.400> what<06:41:35.580> we 06:41:35.750 --> 06:41:35.760 align:start position:0% talking about on this layer are what we 06:41:35.760 --> 06:41:39.048 align:start position:0% talking about on this layer are what we call<06:41:35.878> frames<06:41:36.480> as<06:41:36.840> opposed<06:41:37.260> to<06:41:37.320> datagrams 06:41:39.048 --> 06:41:39.058 align:start position:0% call frames as opposed to datagrams 06:41:39.058 --> 06:41:40.670 align:start position:0% call frames as opposed to datagrams and<06:41:39.540> the<06:41:39.780> major<06:41:39.900> functions<06:41:40.378> that<06:41:40.558> are 06:41:40.670 --> 06:41:40.680 align:start position:0% and the major functions that are 06:41:40.680 --> 06:41:42.650 align:start position:0% and the major functions that are performed<06:41:41.040> on<06:41:41.218> this<06:41:41.400> layer<06:41:41.700> on<06:41:42.120> the<06:41:42.298> data<06:41:42.540> link 06:41:42.650 --> 06:41:42.660 align:start position:0% performed on this layer on the data link 06:41:42.660 --> 06:41:45.650 align:start position:0% performed on this layer on the data link of<06:41:43.020> the<06:41:43.320> OSI<06:41:43.740> model<06:41:44.040> are<06:41:44.760> also<06:41:45.058> occurring<06:41:45.420> at 06:41:45.650 --> 06:41:45.660 align:start position:0% of the OSI model are also occurring at 06:41:45.660 --> 06:41:50.208 align:start position:0% of the OSI model are also occurring at this<06:41:45.900> layer<06:41:46.260> so<06:41:46.700> we're<06:41:47.700> really<06:41:47.940> talking<06:41:48.240> about 06:41:50.208 --> 06:41:50.218 align:start position:0% this layer so we're really talking about 06:41:50.218 --> 06:41:52.730 align:start position:0% this layer so we're really talking about switching<06:41:51.058> operations<06:41:51.480> that<06:41:51.840> occur<06:41:52.138> on<06:41:52.320> Layer 06:41:52.730 --> 06:41:52.740 align:start position:0% switching operations that occur on Layer 06:41:52.740 --> 06:41:53.628 align:start position:0% switching operations that occur on Layer Two 06:41:53.628 --> 06:41:53.638 align:start position:0% Two 06:41:53.638 --> 06:41:58.070 align:start position:0% Two which<06:41:54.000> again<06:41:54.120> is<06:41:54.360> that<06:41:54.540> data<06:41:54.840> link<06:41:54.958> layer 06:41:58.070 --> 06:41:58.080 align:start position:0% 06:41:58.080 --> 06:42:00.048 align:start position:0% and<06:41:58.378> so<06:41:58.558> this<06:41:58.740> is<06:41:58.860> where<06:41:59.040> we<06:41:59.218> see<06:41:59.400> switches 06:42:00.048 --> 06:42:00.058 align:start position:0% and so this is where we see switches 06:42:00.058 --> 06:42:05.690 align:start position:0% and so this is where we see switches operating 06:42:05.690 --> 06:42:05.700 align:start position:0% 06:42:05.700 --> 06:42:07.970 align:start position:0% which<06:42:06.180> means<06:42:06.780> that<06:42:07.080> we're<06:42:07.260> really<06:42:07.500> dealing 06:42:07.970 --> 06:42:07.980 align:start position:0% which means that we're really dealing 06:42:07.980 --> 06:42:11.570 align:start position:0% which means that we're really dealing with<06:42:08.340> Mac<06:42:09.000> addresses<06:42:09.660> okay<06:42:10.378> now<06:42:11.040> a<06:42:11.400> MAC 06:42:11.570 --> 06:42:11.580 align:start position:0% with Mac addresses okay now a MAC 06:42:11.580 --> 06:42:16.310 align:start position:0% with Mac addresses okay now a MAC address<06:42:11.820> again<06:42:12.420> is<06:42:12.780> a<06:42:13.138> 48 06:42:16.310 --> 06:42:16.320 align:start position:0% 06:42:16.320 --> 06:42:20.570 align:start position:0% bit<06:42:17.600> hexadecimal<06:42:18.920> universally<06:42:19.920> unique 06:42:20.570 --> 06:42:20.580 align:start position:0% bit hexadecimal universally unique 06:42:20.580 --> 06:42:23.150 align:start position:0% bit hexadecimal universally unique identifier<06:42:21.298> that's<06:42:21.958> broken<06:42:22.260> up<06:42:22.500> into<06:42:22.680> several 06:42:23.150 --> 06:42:23.160 align:start position:0% identifier that's broken up into several 06:42:23.160 --> 06:42:24.170 align:start position:0% identifier that's broken up into several parts 06:42:24.170 --> 06:42:24.180 align:start position:0% parts 06:42:24.180 --> 06:42:28.070 align:start position:0% parts first<06:42:24.780> part<06:42:25.020> of<06:42:25.200> it<06:42:25.320> is<06:42:25.860> what<06:42:26.100> we<06:42:26.280> call<06:42:26.458> the<06:42:27.660> oui 06:42:28.070 --> 06:42:28.080 align:start position:0% first part of it is what we call the oui 06:42:28.080 --> 06:42:31.190 align:start position:0% first part of it is what we call the oui or<06:42:28.740> the<06:42:28.980> organizational 06:42:31.190 --> 06:42:31.200 align:start position:0% or the organizational 06:42:31.200 --> 06:42:33.470 align:start position:0% or the organizational unique<06:42:31.980> identifier 06:42:33.470 --> 06:42:33.480 align:start position:0% unique identifier 06:42:33.480 --> 06:42:35.868 align:start position:0% unique identifier this<06:42:33.958> basically<06:42:34.260> says<06:42:34.500> what<06:42:34.798> company 06:42:35.868 --> 06:42:35.878 align:start position:0% this basically says what company 06:42:35.878 --> 06:42:39.170 align:start position:0% this basically says what company is<06:42:36.660> uh<06:42:37.200> sending<06:42:37.620> out<06:42:37.798> this<06:42:38.040> device 06:42:39.170 --> 06:42:39.180 align:start position:0% is uh sending out this device 06:42:39.180 --> 06:42:42.288 align:start position:0% is uh sending out this device and<06:42:39.660> then<06:42:39.718> we<06:42:40.020> have<06:42:40.260> the<06:42:40.680> second<06:42:40.798> part<06:42:41.298> which 06:42:42.288 --> 06:42:42.298 align:start position:0% and then we have the second part which 06:42:42.298 --> 06:42:46.010 align:start position:0% and then we have the second part which is<06:42:42.480> the<06:42:42.900> Nic<06:42:43.500> specific 06:42:46.010 --> 06:42:46.020 align:start position:0% is the Nic specific 06:42:46.020 --> 06:42:48.288 align:start position:0% is the Nic specific and<06:42:46.500> then<06:42:46.620> we<06:42:46.740> have<06:42:46.920> the<06:42:47.160> second<06:42:47.280> part 06:42:48.288 --> 06:42:48.298 align:start position:0% and then we have the second part 06:42:48.298 --> 06:42:52.190 align:start position:0% and then we have the second part which<06:42:48.840> is<06:42:49.020> specific<06:42:49.378> to<06:42:49.680> that<06:42:49.980> device<06:42:50.218> itself 06:42:52.190 --> 06:42:52.200 align:start position:0% which is specific to that device itself 06:42:52.200 --> 06:42:56.270 align:start position:0% which is specific to that device itself so<06:42:52.620> this<06:42:52.798> is<06:42:52.980> the<06:42:53.280> manufacturer 06:42:56.270 --> 06:42:56.280 align:start position:0% 06:42:56.280 --> 06:42:58.070 align:start position:0% and<06:42:56.820> this<06:42:57.000> is<06:42:57.120> for<06:42:57.298> the<06:42:57.420> device<06:42:57.600> you<06:42:58.020> can 06:42:58.070 --> 06:42:58.080 align:start position:0% and this is for the device you can 06:42:58.080 --> 06:43:01.490 align:start position:0% and this is for the device you can literally<06:42:58.378> go<06:42:58.558> online<06:42:59.000> search<06:43:00.000> for<06:43:00.360> this<06:43:00.600> part 06:43:01.490 --> 06:43:01.500 align:start position:0% literally go online search for this part 06:43:01.500 --> 06:43:02.750 align:start position:0% literally go online search for this part of<06:43:01.620> the<06:43:01.740> MAC<06:43:01.860> address<06:43:02.040> and<06:43:02.280> it'll<06:43:02.520> tell<06:43:02.638> you 06:43:02.750 --> 06:43:02.760 align:start position:0% of the MAC address and it'll tell you 06:43:02.760 --> 06:43:07.610 align:start position:0% of the MAC address and it'll tell you what<06:43:03.058> company<06:43:03.680> is<06:43:04.680> creating<06:43:05.218> this<06:43:06.058> device 06:43:07.610 --> 06:43:07.620 align:start position:0% what company is creating this device 06:43:07.620 --> 06:43:09.830 align:start position:0% what company is creating this device now<06:43:08.100> the<06:43:08.580> easiest<06:43:08.878> way<06:43:09.120> to<06:43:09.298> find<06:43:09.480> the<06:43:09.660> MAC 06:43:09.830 --> 06:43:09.840 align:start position:0% now the easiest way to find the MAC 06:43:09.840 --> 06:43:12.110 align:start position:0% now the easiest way to find the MAC address<06:43:10.080> in<06:43:10.500> a<06:43:10.680> Windows<06:43:10.980> PC<06:43:11.340> is<06:43:11.520> by<06:43:11.760> opening<06:43:12.058> up 06:43:12.110 --> 06:43:12.120 align:start position:0% address in a Windows PC is by opening up 06:43:12.120 --> 06:43:14.930 align:start position:0% address in a Windows PC is by opening up the<06:43:12.298> command<06:43:12.600> prompt<06:43:12.958> and<06:43:13.500> using<06:43:13.940> ipconfig 06:43:14.930 --> 06:43:14.940 align:start position:0% the command prompt and using ipconfig 06:43:14.940 --> 06:43:17.990 align:start position:0% the command prompt and using ipconfig all<06:43:15.240> which<06:43:15.600> we've<06:43:15.840> talked<06:43:16.200> about<06:43:16.400> in<06:43:17.400> a<06:43:17.820> plus 06:43:17.990 --> 06:43:18.000 align:start position:0% all which we've talked about in a plus 06:43:18.000 --> 06:43:20.030 align:start position:0% all which we've talked about in a plus this<06:43:18.718> brings<06:43:18.900> up<06:43:19.080> the<06:43:19.378> Internet<06:43:19.500> Protocol 06:43:20.030 --> 06:43:20.040 align:start position:0% this brings up the Internet Protocol 06:43:20.040 --> 06:43:22.670 align:start position:0% this brings up the Internet Protocol information<06:43:20.400> the<06:43:20.940> IP<06:43:21.298> address<06:43:21.480> and<06:43:22.260> it<06:43:22.440> also 06:43:22.670 --> 06:43:22.680 align:start position:0% information the IP address and it also 06:43:22.680 --> 06:43:25.070 align:start position:0% information the IP address and it also brings<06:43:22.980> up<06:43:23.280> the<06:43:23.940> MAC<06:43:24.120> address<06:43:24.360> or<06:43:24.840> the 06:43:25.070 --> 06:43:25.080 align:start position:0% brings up the MAC address or the 06:43:25.080 --> 06:43:26.868 align:start position:0% brings up the MAC address or the physical<06:43:25.260> address<06:43:25.680> that's<06:43:26.160> assigned<06:43:26.638> to<06:43:26.700> your 06:43:26.868 --> 06:43:26.878 align:start position:0% physical address that's assigned to your 06:43:26.878 --> 06:43:28.190 align:start position:0% physical address that's assigned to your Nick 06:43:28.190 --> 06:43:28.200 align:start position:0% Nick 06:43:28.200 --> 06:43:29.750 align:start position:0% Nick so<06:43:28.620> now<06:43:28.740> that<06:43:28.920> we've<06:43:29.040> covered<06:43:29.400> the<06:43:29.638> MAC 06:43:29.750 --> 06:43:29.760 align:start position:0% so now that we've covered the MAC 06:43:29.760 --> 06:43:31.670 align:start position:0% so now that we've covered the MAC address<06:43:30.058> is<06:43:30.600> it's<06:43:30.958> really<06:43:31.138> important<06:43:31.500> to 06:43:31.670 --> 06:43:31.680 align:start position:0% address is it's really important to 06:43:31.680 --> 06:43:34.190 align:start position:0% address is it's really important to understand<06:43:31.860> the<06:43:32.580> parts<06:43:32.760> of<06:43:33.540> an<06:43:33.718> Ethernet 06:43:34.190 --> 06:43:34.200 align:start position:0% understand the parts of an Ethernet 06:43:34.200 --> 06:43:35.810 align:start position:0% understand the parts of an Ethernet frame<06:43:34.740> and<06:43:34.920> remember<06:43:35.100> we're<06:43:35.340> talking<06:43:35.580> about 06:43:35.810 --> 06:43:35.820 align:start position:0% frame and remember we're talking about 06:43:35.820 --> 06:43:39.650 align:start position:0% frame and remember we're talking about frames<06:43:36.600> at<06:43:37.378> this<06:43:37.620> juncture 06:43:39.650 --> 06:43:39.660 align:start position:0% frames at this juncture 06:43:39.660 --> 06:43:42.530 align:start position:0% frames at this juncture so<06:43:40.080> the<06:43:40.320> Preamble<06:43:40.798> of<06:43:41.040> an<06:43:41.160> Ethernet<06:43:41.580> frame<06:43:42.058> is 06:43:42.530 --> 06:43:42.540 align:start position:0% so the Preamble of an Ethernet frame is 06:43:42.540 --> 06:43:45.350 align:start position:0% so the Preamble of an Ethernet frame is made<06:43:42.718> up<06:43:42.840> of<06:43:43.080> seven<06:43:43.378> bytes<06:43:43.860> or<06:43:43.980> 56<06:43:44.458> bits<06:43:44.878> and 06:43:45.350 --> 06:43:45.360 align:start position:0% made up of seven bytes or 56 bits and 06:43:45.360 --> 06:43:50.510 align:start position:0% made up of seven bytes or 56 bits and this<06:43:45.480> serves<06:43:45.780> as<06:43:45.958> synchronization 06:43:50.510 --> 06:43:50.520 align:start position:0% 06:43:50.520 --> 06:43:52.970 align:start position:0% and<06:43:50.940> gives<06:43:51.180> the<06:43:51.540> receiving<06:43:51.958> station<06:43:52.378> a<06:43:52.680> heads 06:43:52.970 --> 06:43:52.980 align:start position:0% and gives the receiving station a heads 06:43:52.980 --> 06:43:55.010 align:start position:0% and gives the receiving station a heads up<06:43:53.040> to<06:43:53.340> standby<06:43:53.700> and<06:43:53.878> look<06:43:54.058> out<06:43:54.240> for<06:43:54.480> a<06:43:54.718> signal 06:43:55.010 --> 06:43:55.020 align:start position:0% up to standby and look out for a signal 06:43:55.020 --> 06:43:56.090 align:start position:0% up to standby and look out for a signal that's<06:43:55.200> coming 06:43:56.090 --> 06:43:56.100 align:start position:0% that's coming 06:43:56.100 --> 06:43:58.190 align:start position:0% that's coming the<06:43:56.638> next<06:43:56.760> part<06:43:57.000> is<06:43:57.240> what<06:43:57.420> we<06:43:57.540> call<06:43:57.660> the<06:43:57.958> start 06:43:58.190 --> 06:43:58.200 align:start position:0% the next part is what we call the start 06:43:58.200 --> 06:44:00.948 align:start position:0% the next part is what we call the start of<06:43:58.558> frame<06:43:58.920> delimiter<06:43:59.700> the<06:44:00.298> only<06:44:00.420> purpose<06:44:00.780> of 06:44:00.948 --> 06:44:00.958 align:start position:0% of frame delimiter the only purpose of 06:44:00.958 --> 06:44:03.650 align:start position:0% of frame delimiter the only purpose of this<06:44:01.080> is<06:44:01.260> to<06:44:01.440> indicate<06:44:01.740> the<06:44:01.980> start<06:44:02.100> of<06:44:02.400> data 06:44:03.650 --> 06:44:03.660 align:start position:0% this is to indicate the start of data 06:44:03.660 --> 06:44:05.690 align:start position:0% this is to indicate the start of data the<06:44:04.200> next<06:44:04.320> two<06:44:04.440> parts<06:44:04.680> are<06:44:04.920> the<06:44:05.100> source<06:44:05.520> and 06:44:05.690 --> 06:44:05.700 align:start position:0% the next two parts are the source and 06:44:05.700 --> 06:44:09.170 align:start position:0% the next two parts are the source and destination<06:44:06.298> Mac<06:44:07.080> addresses<06:44:07.680> so<06:44:08.638> the 06:44:09.170 --> 06:44:09.180 align:start position:0% destination Mac addresses so the 06:44:09.180 --> 06:44:11.390 align:start position:0% destination Mac addresses so the ethernet<06:44:09.600> frame<06:44:09.958> again<06:44:10.680> this<06:44:11.040> is<06:44:11.160> everything 06:44:11.390 --> 06:44:11.400 align:start position:0% ethernet frame again this is everything 06:44:11.400 --> 06:44:14.868 align:start position:0% ethernet frame again this is everything that's<06:44:11.638> going<06:44:11.940> over<06:44:12.360> this<06:44:12.600> ethernet<06:44:13.160> uh<06:44:14.160> over 06:44:14.868 --> 06:44:14.878 align:start position:0% that's going over this ethernet uh over 06:44:14.878 --> 06:44:17.270 align:start position:0% that's going over this ethernet uh over the<06:44:15.540> network<06:44:15.718> we<06:44:16.200> have<06:44:16.320> the<06:44:16.440> Preamble<06:44:16.860> it<06:44:16.980> says 06:44:17.270 --> 06:44:17.280 align:start position:0% the network we have the Preamble it says 06:44:17.280 --> 06:44:20.628 align:start position:0% the network we have the Preamble it says Hey<06:44:17.700> pay<06:44:18.360> attention<06:44:18.718> now<06:44:19.138> this<06:44:19.980> that<06:44:20.218> says<06:44:20.458> now 06:44:20.628 --> 06:44:20.638 align:start position:0% Hey pay attention now this that says now 06:44:20.638 --> 06:44:22.368 align:start position:0% Hey pay attention now this that says now I'm<06:44:20.820> giving<06:44:21.000> you<06:44:21.120> some<06:44:21.360> data<06:44:21.718> and<06:44:22.138> then<06:44:22.200> we 06:44:22.368 --> 06:44:22.378 align:start position:0% I'm giving you some data and then we 06:44:22.378 --> 06:44:24.530 align:start position:0% I'm giving you some data and then we have<06:44:22.558> the<06:44:22.798> destination<06:44:23.280> and<06:44:23.760> the<06:44:24.000> source<06:44:24.360> Mac 06:44:24.530 --> 06:44:24.540 align:start position:0% have the destination and the source Mac 06:44:24.540 --> 06:44:26.990 align:start position:0% have the destination and the source Mac addresses<06:44:25.020> so<06:44:25.260> that<06:44:25.440> way<06:44:25.620> we<06:44:26.160> know<06:44:26.340> where<06:44:26.820> it's 06:44:26.990 --> 06:44:27.000 align:start position:0% addresses so that way we know where it's 06:44:27.000 --> 06:44:29.570 align:start position:0% addresses so that way we know where it's coming<06:44:27.180> from<06:44:27.420> who<06:44:27.780> it's<06:44:27.958> going<06:44:28.260> to<06:44:28.558> and<06:44:29.400> this 06:44:29.570 --> 06:44:29.580 align:start position:0% coming from who it's going to and this 06:44:29.580 --> 06:44:35.090 align:start position:0% coming from who it's going to and this takes<06:44:29.878> up<06:44:30.138> 96<06:44:31.138> bits 06:44:35.090 --> 06:44:35.100 align:start position:0% 06:44:35.100 --> 06:44:38.810 align:start position:0% or<06:44:35.638> 12<06:44:35.878> bytes 06:44:38.810 --> 06:44:38.820 align:start position:0% 06:44:38.820 --> 06:44:41.090 align:start position:0% because<06:44:39.298> remember<06:44:39.540> this<06:44:39.958> is<06:44:40.138> 48<06:44:40.558> bits<06:44:40.920> right 06:44:41.090 --> 06:44:41.100 align:start position:0% because remember this is 48 bits right 06:44:41.100 --> 06:44:43.070 align:start position:0% because remember this is 48 bits right here<06:44:41.400> so<06:44:41.878> if<06:44:42.000> we<06:44:42.180> double<06:44:42.360> that<06:44:42.600> that's<06:44:42.900> going 06:44:43.070 --> 06:44:43.080 align:start position:0% here so if we double that that's going 06:44:43.080 --> 06:44:45.530 align:start position:0% here so if we double that that's going to<06:44:43.138> be<06:44:43.200> 96<06:44:43.798> and<06:44:44.580> then<06:44:44.760> the<06:44:44.940> next<06:44:45.120> type<06:44:45.360> is 06:44:45.530 --> 06:44:45.540 align:start position:0% to be 96 and then the next type is 06:44:45.540 --> 06:44:48.350 align:start position:0% to be 96 and then the next type is What's<06:44:45.718> called<06:44:45.958> the<06:44:46.200> frame<06:44:46.440> type<06:44:46.680> this<06:44:47.400> is<06:44:47.580> two 06:44:48.350 --> 06:44:48.360 align:start position:0% What's called the frame type this is two 06:44:48.360 --> 06:44:52.250 align:start position:0% What's called the frame type this is two uh<06:44:49.080> bytes<06:44:49.740> that<06:44:49.980> contain<06:44:50.400> either<06:44:51.180> the<06:44:51.840> client 06:44:52.250 --> 06:44:52.260 align:start position:0% uh bytes that contain either the client 06:44:52.260 --> 06:44:54.830 align:start position:0% uh bytes that contain either the client protocol<06:44:52.740> information<06:44:53.240> or<06:44:54.240> the<06:44:54.600> number<06:44:54.718> of 06:44:54.830 --> 06:44:54.840 align:start position:0% protocol information or the number of 06:44:54.840 --> 06:44:56.330 align:start position:0% protocol information or the number of bytes<06:44:55.260> that<06:44:55.378> are<06:44:55.500> found<06:44:55.620> in<06:44:55.740> the<06:44:55.860> data<06:44:56.218> field 06:44:56.330 --> 06:44:56.340 align:start position:0% bytes that are found in the data field 06:44:56.340 --> 06:44:58.070 align:start position:0% bytes that are found in the data field which<06:44:56.700> happen<06:44:56.878> to<06:44:57.058> be<06:44:57.180> the<06:44:57.360> next<06:44:57.540> part<06:44:57.780> of<06:44:57.958> the 06:44:58.070 --> 06:44:58.080 align:start position:0% which happen to be the next part of the 06:44:58.080 --> 06:44:59.150 align:start position:0% which happen to be the next part of the frame 06:44:59.150 --> 06:44:59.160 align:start position:0% frame 06:44:59.160 --> 06:45:01.910 align:start position:0% frame which<06:44:59.580> is<06:44:59.760> the<06:45:00.120> data<06:45:00.480> this<06:45:01.080> field<06:45:01.200> is<06:45:01.500> going<06:45:01.680> to 06:45:01.910 --> 06:45:01.920 align:start position:0% which is the data this field is going to 06:45:01.920 --> 06:45:04.368 align:start position:0% which is the data this field is going to be<06:45:02.100> a<06:45:02.700> certain<06:45:02.878> number<06:45:03.058> of<06:45:03.240> bytes<06:45:03.780> and<06:45:04.260> the 06:45:04.368 --> 06:45:04.378 align:start position:0% be a certain number of bytes and the 06:45:04.378 --> 06:45:06.110 align:start position:0% be a certain number of bytes and the amount<06:45:04.620> of<06:45:04.740> data<06:45:05.040> is<06:45:05.160> going<06:45:05.340> to<06:45:05.458> change<06:45:05.700> with 06:45:06.110 --> 06:45:06.120 align:start position:0% amount of data is going to change with 06:45:06.120 --> 06:45:08.570 align:start position:0% amount of data is going to change with any<06:45:06.298> given<06:45:06.660> transmission<06:45:07.218> the<06:45:08.218> maximum 06:45:08.570 --> 06:45:08.580 align:start position:0% any given transmission the maximum 06:45:08.580 --> 06:45:10.970 align:start position:0% any given transmission the maximum amount<06:45:08.700> of<06:45:08.878> data<06:45:09.180> allowed<06:45:09.480> in<06:45:09.600> this<06:45:09.780> field<06:45:10.020> is 06:45:10.970 --> 06:45:10.980 align:start position:0% amount of data allowed in this field is 06:45:10.980 --> 06:45:14.030 align:start position:0% amount of data allowed in this field is 1500<06:45:11.700> bytes<06:45:12.120> we<06:45:12.298> can't<06:45:12.420> have<06:45:12.600> more<06:45:12.900> than<06:45:13.080> that 06:45:14.030 --> 06:45:14.040 align:start position:0% 1500 bytes we can't have more than that 06:45:14.040 --> 06:45:16.788 align:start position:0% 1500 bytes we can't have more than that now<06:45:14.458> if<06:45:14.638> this<06:45:14.820> field<06:45:14.940> is<06:45:15.120> any<06:45:15.360> less<06:45:15.718> than<06:45:16.138> 46 06:45:16.788 --> 06:45:16.798 align:start position:0% now if this field is any less than 46 06:45:16.798 --> 06:45:19.070 align:start position:0% now if this field is any less than 46 bytes<06:45:17.820> then<06:45:18.180> we<06:45:18.360> have<06:45:18.480> to<06:45:18.660> actually<06:45:18.840> have 06:45:19.070 --> 06:45:19.080 align:start position:0% bytes then we have to actually have 06:45:19.080 --> 06:45:21.350 align:start position:0% bytes then we have to actually have something<06:45:19.320> called<06:45:19.620> a<06:45:19.980> pad<06:45:20.218> which<06:45:21.058> is<06:45:21.180> actually 06:45:21.350 --> 06:45:21.360 align:start position:0% something called a pad which is actually 06:45:21.360 --> 06:45:23.330 align:start position:0% something called a pad which is actually just<06:45:21.540> going<06:45:21.660> to<06:45:21.718> be<06:45:21.780> used<06:45:21.900> to<06:45:22.138> fill<06:45:22.440> in<06:45:22.620> the 06:45:23.330 --> 06:45:23.340 align:start position:0% just going to be used to fill in the 06:45:23.340 --> 06:45:24.708 align:start position:0% just going to be used to fill in the rest<06:45:23.400> of<06:45:23.580> the<06:45:23.820> data 06:45:24.708 --> 06:45:24.718 align:start position:0% rest of the data 06:45:24.718 --> 06:45:26.390 align:start position:0% rest of the data and<06:45:25.138> the<06:45:25.260> final<06:45:25.440> part<06:45:25.740> of<06:45:25.920> this<06:45:26.040> ethernet 06:45:26.390 --> 06:45:26.400 align:start position:0% and the final part of this ethernet 06:45:26.400 --> 06:45:34.128 align:start position:0% and the final part of this ethernet frame<06:45:26.700> is<06:45:26.820> called<06:45:27.000> the<06:45:27.298> FCS<06:45:28.020> or<06:45:28.860> the<06:45:29.100> frame 06:45:34.128 --> 06:45:34.138 align:start position:0% 06:45:34.138 --> 06:45:36.590 align:start position:0% check<06:45:34.558> sequence<06:45:35.100> and<06:45:35.760> this<06:45:35.940> is<06:45:36.120> used<06:45:36.298> for 06:45:36.590 --> 06:45:36.600 align:start position:0% check sequence and this is used for 06:45:36.600 --> 06:45:38.750 align:start position:0% check sequence and this is used for cyclic<06:45:37.080> redundancy<06:45:37.798> check<06:45:37.980> which<06:45:38.400> is<06:45:38.458> also 06:45:38.750 --> 06:45:38.760 align:start position:0% cyclic redundancy check which is also 06:45:38.760 --> 06:45:41.690 align:start position:0% cyclic redundancy check which is also called<06:45:38.940> CRC<06:45:39.660> this<06:45:40.558> basically<06:45:40.920> allows<06:45:41.340> us<06:45:41.458> to 06:45:41.690 --> 06:45:41.700 align:start position:0% called CRC this basically allows us to 06:45:41.700 --> 06:45:43.548 align:start position:0% called CRC this basically allows us to make<06:45:41.940> sure<06:45:42.180> that<06:45:42.480> there<06:45:42.660> are<06:45:42.780> no<06:45:42.900> errors<06:45:43.320> in 06:45:43.548 --> 06:45:43.558 align:start position:0% make sure that there are no errors in 06:45:43.558 --> 06:45:45.890 align:start position:0% make sure that there are no errors in the<06:45:43.680> data<06:45:44.040> now<06:45:44.700> similar<06:45:45.058> to<06:45:45.180> the<06:45:45.298> way<06:45:45.420> that<06:45:45.660> a 06:45:45.890 --> 06:45:45.900 align:start position:0% the data now similar to the way that a 06:45:45.900 --> 06:45:47.750 align:start position:0% the data now similar to the way that a an<06:45:46.260> algorithm<06:45:46.798> is<06:45:47.040> going<06:45:47.160> to<06:45:47.280> be<06:45:47.340> used<06:45:47.520> to 06:45:47.750 --> 06:45:47.760 align:start position:0% an algorithm is going to be used to 06:45:47.760 --> 06:45:50.628 align:start position:0% an algorithm is going to be used to ensure<06:45:48.058> Integrity<06:45:48.480> of<06:45:48.718> data<06:45:49.020> the<06:45:49.440> CRC<06:45:49.860> uses<06:45:50.280> a 06:45:50.628 --> 06:45:50.638 align:start position:0% ensure Integrity of data the CRC uses a 06:45:50.638 --> 06:45:53.090 align:start position:0% ensure Integrity of data the CRC uses a mathematical<06:45:51.360> algorithm<06:45:52.138> which<06:45:52.680> sometimes 06:45:53.090 --> 06:45:53.100 align:start position:0% mathematical algorithm which sometimes 06:45:53.100 --> 06:45:54.530 align:start position:0% mathematical algorithm which sometimes we're<06:45:53.218> going<06:45:53.340> to<06:45:53.400> refer<06:45:53.638> to<06:45:53.760> as<06:45:53.940> hashing<06:45:54.360> which 06:45:54.530 --> 06:45:54.540 align:start position:0% we're going to refer to as hashing which 06:45:54.540 --> 06:45:56.030 align:start position:0% we're going to refer to as hashing which we'll<06:45:54.718> talk<06:45:54.900> a<06:45:55.080> lot<06:45:55.200> more<06:45:55.320> about<06:45:55.500> when<06:45:55.740> we<06:45:55.920> get 06:45:56.030 --> 06:45:56.040 align:start position:0% we'll talk a lot more about when we get 06:45:56.040 --> 06:45:59.868 align:start position:0% we'll talk a lot more about when we get to<06:45:56.160> Security<06:45:56.400> Plus 06:45:59.868 --> 06:45:59.878 align:start position:0% 06:45:59.878 --> 06:46:03.288 align:start position:0% that's<06:46:00.600> made<06:46:00.840> before<06:46:01.260> the<06:46:01.798> data<06:46:02.160> is<06:46:02.340> sent<06:46:02.580> and 06:46:03.288 --> 06:46:03.298 align:start position:0% that's made before the data is sent and 06:46:03.298 --> 06:46:05.090 align:start position:0% that's made before the data is sent and then<06:46:03.480> it<06:46:03.840> is<06:46:03.958> checked<06:46:04.440> when<06:46:04.620> it<06:46:04.740> gets<06:46:04.980> there 06:46:05.090 --> 06:46:05.100 align:start position:0% then it is checked when it gets there 06:46:05.100 --> 06:46:07.010 align:start position:0% then it is checked when it gets there that<06:46:05.520> way<06:46:05.700> we<06:46:05.940> can<06:46:06.058> compare<06:46:06.420> the<06:46:06.660> two<06:46:06.780> results 06:46:07.010 --> 06:46:07.020 align:start position:0% that way we can compare the two results 06:46:07.020 --> 06:46:08.810 align:start position:0% that way we can compare the two results bit<06:46:07.320> for<06:46:07.500> bit<06:46:07.680> and<06:46:07.920> if<06:46:08.040> the<06:46:08.160> two<06:46:08.280> numbers<06:46:08.458> don't 06:46:08.810 --> 06:46:08.820 align:start position:0% bit for bit and if the two numbers don't 06:46:08.820 --> 06:46:10.490 align:start position:0% bit for bit and if the two numbers don't match<06:46:09.000> then<06:46:09.298> we<06:46:09.480> know<06:46:09.600> the<06:46:09.780> frame<06:46:10.020> needs<06:46:10.320> to<06:46:10.378> be 06:46:10.490 --> 06:46:10.500 align:start position:0% match then we know the frame needs to be 06:46:10.500 --> 06:46:12.230 align:start position:0% match then we know the frame needs to be discarded<06:46:11.040> we<06:46:11.458> assume<06:46:11.760> there's<06:46:11.878> been<06:46:12.058> a 06:46:12.230 --> 06:46:12.240 align:start position:0% discarded we assume there's been a 06:46:12.240 --> 06:46:14.150 align:start position:0% discarded we assume there's been a transmission<06:46:12.420> error<06:46:13.080> or<06:46:13.558> that<06:46:13.740> there<06:46:13.860> was<06:46:14.040> a 06:46:14.150 --> 06:46:14.160 align:start position:0% transmission error or that there was a 06:46:14.160 --> 06:46:16.250 align:start position:0% transmission error or that there was a data<06:46:14.520> Collision<06:46:14.760> of<06:46:15.000> some<06:46:15.240> sort<06:46:15.540> and<06:46:16.020> then<06:46:16.080> we 06:46:16.250 --> 06:46:16.260 align:start position:0% data Collision of some sort and then we 06:46:16.260 --> 06:46:18.230 align:start position:0% data Collision of some sort and then we ask<06:46:16.440> the<06:46:16.620> data<06:46:16.920> to<06:46:17.040> be<06:46:17.100> resent 06:46:18.230 --> 06:46:18.240 align:start position:0% ask the data to be resent 06:46:18.240 --> 06:46:19.850 align:start position:0% ask the data to be resent now<06:46:18.600> this<06:46:18.780> layer<06:46:19.138> by<06:46:19.320> the<06:46:19.440> way<06:46:19.500> this<06:46:19.680> network 06:46:19.850 --> 06:46:19.860 align:start position:0% now this layer by the way this network 06:46:19.860 --> 06:46:22.670 align:start position:0% now this layer by the way this network interface<06:46:20.458> layer<06:46:20.820> is<06:46:21.000> also<06:46:21.420> responsible<06:46:21.958> for 06:46:22.670 --> 06:46:22.680 align:start position:0% interface layer is also responsible for 06:46:22.680 --> 06:46:25.368 align:start position:0% interface layer is also responsible for the<06:46:22.978> network<06:46:23.218> access<06:46:23.580> control<06:46:24.180> and<06:46:25.138> some<06:46:25.260> of 06:46:25.368 --> 06:46:25.378 align:start position:0% the network access control and some of 06:46:25.378 --> 06:46:28.250 align:start position:0% the network access control and some of the<06:46:25.978> protocols<06:46:26.940> that<06:46:27.180> operate<06:46:27.540> on<06:46:27.718> this<06:46:27.900> are 06:46:28.250 --> 06:46:28.260 align:start position:0% the protocols that operate on this are 06:46:28.260 --> 06:46:31.690 align:start position:0% the protocols that operate on this are what<06:46:28.500> are<06:46:28.680> called<06:46:29.100> uh<06:46:29.878> point<06:46:30.240> to<06:46:30.478> point 06:46:31.690 --> 06:46:31.700 align:start position:0% what are called uh point to point 06:46:31.700 --> 06:46:35.208 align:start position:0% what are called uh point to point protocols<06:46:32.780> ISDN<06:46:33.780> which<06:46:34.080> is<06:46:34.260> a<06:46:34.558> which<06:46:34.978> we've 06:46:35.208 --> 06:46:35.218 align:start position:0% protocols ISDN which is a which we've 06:46:35.218 --> 06:46:37.430 align:start position:0% protocols ISDN which is a which we've talked<06:46:35.520> about<06:46:35.580> also<06:46:36.058> a<06:46:36.180> type<06:46:36.420> of 06:46:37.430 --> 06:46:37.440 align:start position:0% talked about also a type of 06:46:37.440 --> 06:46:38.090 align:start position:0% talked about also a type of um 06:46:38.090 --> 06:46:38.100 align:start position:0% um 06:46:38.100 --> 06:46:41.030 align:start position:0% um Network<06:46:38.760> and<06:46:39.180> also<06:46:39.420> DSL<06:46:40.138> so<06:46:40.620> these<06:46:40.798> are<06:46:40.860> some 06:46:41.030 --> 06:46:41.040 align:start position:0% Network and also DSL so these are some 06:46:41.040 --> 06:46:42.948 align:start position:0% Network and also DSL so these are some of<06:46:41.100> the<06:46:41.218> things<06:46:41.340> that<06:46:41.820> exist<06:46:42.360> at<06:46:42.600> this<06:46:42.780> and 06:46:42.948 --> 06:46:42.958 align:start position:0% of the things that exist at this and 06:46:42.958 --> 06:46:44.510 align:start position:0% of the things that exist at this and this<06:46:43.200> makes<06:46:43.320> sense<06:46:43.558> because<06:46:43.798> again<06:46:44.100> we're 06:46:44.510 --> 06:46:44.520 align:start position:0% this makes sense because again we're 06:46:44.520 --> 06:46:46.548 align:start position:0% this makes sense because again we're dealing<06:46:44.820> with<06:46:44.940> the<06:46:45.240> physical<06:46:45.360> bits<06:46:46.020> bytes<06:46:46.440> of 06:46:46.548 --> 06:46:46.558 align:start position:0% dealing with the physical bits bytes of 06:46:46.558 --> 06:46:47.690 align:start position:0% dealing with the physical bits bytes of data 06:46:47.690 --> 06:46:47.700 align:start position:0% data 06:46:47.700 --> 06:46:50.208 align:start position:0% data so<06:46:48.180> now<06:46:48.478> that<06:46:48.600> we've<06:46:48.780> taken<06:46:49.080> a<06:46:49.200> look<06:46:49.320> at<06:46:49.798> each 06:46:50.208 --> 06:46:50.218 align:start position:0% so now that we've taken a look at each 06:46:50.218 --> 06:46:52.368 align:start position:0% so now that we've taken a look at each of<06:46:50.340> the<06:46:50.458> layers<06:46:50.760> in<06:46:51.000> the<06:46:51.120> TCP<06:46:51.540> model<06:46:52.020> there's 06:46:52.368 --> 06:46:52.378 align:start position:0% of the layers in the TCP model there's 06:46:52.378 --> 06:46:53.930 align:start position:0% of the layers in the TCP model there's still<06:46:52.558> a<06:46:52.680> couple<06:46:52.798> things<06:46:53.100> that<06:46:53.340> we<06:46:53.520> still<06:46:53.700> need 06:46:53.930 --> 06:46:53.940 align:start position:0% still a couple things that we still need 06:46:53.940 --> 06:46:56.330 align:start position:0% still a couple things that we still need to<06:46:54.120> Define<06:46:54.298> now<06:46:55.138> we've<06:46:55.378> discussed<06:46:55.798> how<06:46:56.100> some 06:46:56.330 --> 06:46:56.340 align:start position:0% to Define now we've discussed how some 06:46:56.340 --> 06:46:58.968 align:start position:0% to Define now we've discussed how some of<06:46:56.458> the<06:46:56.580> protocols<06:46:57.240> that<06:46:57.478> we've<06:46:57.718> seen<06:46:57.978> relate 06:46:58.968 --> 06:46:58.978 align:start position:0% of the protocols that we've seen relate 06:46:58.978 --> 06:47:01.310 align:start position:0% of the protocols that we've seen relate to<06:46:59.100> the<06:46:59.218> OSI<06:46:59.760> model<06:47:00.000> as<06:47:00.298> well<06:47:00.478> as<06:47:00.600> the<06:47:00.780> tcpip 06:47:01.310 --> 06:47:01.320 align:start position:0% to the OSI model as well as the tcpip 06:47:01.320 --> 06:47:03.048 align:start position:0% to the OSI model as well as the tcpip model<06:47:01.740> and<06:47:02.218> we<06:47:02.340> found<06:47:02.520> that<06:47:02.700> some<06:47:02.878> of<06:47:03.000> the 06:47:03.048 --> 06:47:03.058 align:start position:0% model and we found that some of the 06:47:03.058 --> 06:47:04.850 align:start position:0% model and we found that some of the protocols<06:47:03.478> function<06:47:03.780> much<06:47:04.080> more<06:47:04.320> smoothly 06:47:04.850 --> 06:47:04.860 align:start position:0% protocols function much more smoothly 06:47:04.860 --> 06:47:06.890 align:start position:0% protocols function much more smoothly when<06:47:05.340> they're<06:47:05.458> put<06:47:05.638> into<06:47:05.820> the<06:47:06.058> context<06:47:06.420> of<06:47:06.718> an 06:47:06.890 --> 06:47:06.900 align:start position:0% when they're put into the context of an 06:47:06.900 --> 06:47:09.048 align:start position:0% when they're put into the context of an outline<06:47:07.260> of<06:47:07.440> one<06:47:07.620> of<06:47:07.740> these<06:47:07.920> models<06:47:08.400> so<06:47:08.878> the 06:47:09.048 --> 06:47:09.058 align:start position:0% outline of one of these models so the 06:47:09.058 --> 06:47:10.670 align:start position:0% outline of one of these models so the next<06:47:09.180> definition<06:47:09.420> I<06:47:09.900> want<06:47:10.020> to<06:47:10.138> make<06:47:10.320> sure<06:47:10.500> to 06:47:10.670 --> 06:47:10.680 align:start position:0% next definition I want to make sure to 06:47:10.680 --> 06:47:12.350 align:start position:0% next definition I want to make sure to cover<06:47:10.860> is<06:47:11.040> something<06:47:11.280> called<06:47:11.580> protocol 06:47:12.350 --> 06:47:12.360 align:start position:0% cover is something called protocol 06:47:12.360 --> 06:47:14.930 align:start position:0% cover is something called protocol binding<06:47:13.080> this<06:47:13.680> is<06:47:13.798> when<06:47:13.920> a<06:47:14.160> network<06:47:14.280> interface 06:47:14.930 --> 06:47:14.940 align:start position:0% binding this is when a network interface 06:47:14.940 --> 06:47:18.410 align:start position:0% binding this is when a network interface card<06:47:15.320> receives<06:47:16.320> an<06:47:16.680> assigned<06:47:17.218> protocol<06:47:17.580> it's 06:47:18.410 --> 06:47:18.420 align:start position:0% card receives an assigned protocol it's 06:47:18.420 --> 06:47:21.288 align:start position:0% card receives an assigned protocol it's considered<06:47:18.900> binding<06:47:19.558> that<06:47:20.160> protocol<06:47:20.580> to<06:47:21.120> that 06:47:21.288 --> 06:47:21.298 align:start position:0% considered binding that protocol to that 06:47:21.298 --> 06:47:23.628 align:start position:0% considered binding that protocol to that Nick<06:47:21.540> so<06:47:22.200> just<06:47:22.320> we<06:47:22.558> learned<06:47:22.798> how<06:47:22.978> the<06:47:23.218> data<06:47:23.520> is 06:47:23.628 --> 06:47:23.638 align:start position:0% Nick so just we learned how the data is 06:47:23.638 --> 06:47:25.430 align:start position:0% Nick so just we learned how the data is going<06:47:23.820> to<06:47:23.940> be<06:47:24.058> passed<06:47:24.478> down<06:47:24.600> from<06:47:24.900> one<06:47:25.138> layer 06:47:25.430 --> 06:47:25.440 align:start position:0% going to be passed down from one layer 06:47:25.440 --> 06:47:27.410 align:start position:0% going to be passed down from one layer to<06:47:25.620> the<06:47:25.798> next<06:47:25.920> it's<06:47:26.520> very<06:47:26.760> important<06:47:27.058> that<06:47:27.240> we 06:47:27.410 --> 06:47:27.420 align:start position:0% to the next it's very important that we 06:47:27.420 --> 06:47:29.628 align:start position:0% to the next it's very important that we have<06:47:27.540> these<06:47:27.840> protocols<06:47:28.500> bound<06:47:28.920> to<06:47:29.160> the<06:47:29.458> Nick 06:47:29.628 --> 06:47:29.638 align:start position:0% have these protocols bound to the Nick 06:47:29.638 --> 06:47:32.150 align:start position:0% have these protocols bound to the Nick we<06:47:30.420> can<06:47:30.478> have<06:47:30.660> multiple<06:47:31.020> protocols<06:47:31.798> actually 06:47:32.150 --> 06:47:32.160 align:start position:0% we can have multiple protocols actually 06:47:32.160 --> 06:47:35.510 align:start position:0% we can have multiple protocols actually bound<06:47:32.700> to<06:47:33.360> one<06:47:33.660> network<06:47:34.020> interface<06:47:34.680> card<06:47:34.920> now 06:47:35.510 --> 06:47:35.520 align:start position:0% bound to one network interface card now 06:47:35.520 --> 06:47:37.670 align:start position:0% bound to one network interface card now of<06:47:35.700> course<06:47:35.820> the<06:47:36.058> most<06:47:36.240> easily<06:47:36.600> recognized<06:47:37.260> we 06:47:37.670 --> 06:47:37.680 align:start position:0% of course the most easily recognized we 06:47:37.680 --> 06:47:39.170 align:start position:0% of course the most easily recognized we can<06:47:37.860> most<06:47:38.040> easily<06:47:38.340> recognize<06:47:38.760> these<06:47:39.000> when 06:47:39.170 --> 06:47:39.180 align:start position:0% can most easily recognize these when 06:47:39.180 --> 06:47:41.750 align:start position:0% can most easily recognize these when we're<06:47:39.360> looking<06:47:39.540> at<06:47:39.780> the<06:47:40.200> ipv4<06:47:40.860> and<06:47:41.100> IPv6 06:47:41.750 --> 06:47:41.760 align:start position:0% we're looking at the ipv4 and IPv6 06:47:41.760 --> 06:47:44.510 align:start position:0% we're looking at the ipv4 and IPv6 configurations<06:47:42.620> in<06:47:43.620> our<06:47:43.920> network<06:47:44.160> connection 06:47:44.510 --> 06:47:44.520 align:start position:0% configurations in our network connection 06:47:44.520 --> 06:47:46.968 align:start position:0% configurations in our network connection Properties<06:47:45.240> or<06:47:45.600> adapter<06:47:46.080> settings<06:47:46.320> in 06:47:46.968 --> 06:47:46.978 align:start position:0% Properties or adapter settings in 06:47:46.978 --> 06:47:49.010 align:start position:0% Properties or adapter settings in Windows<06:47:47.340> so<06:47:47.638> for<06:47:48.180> instance<06:47:48.420> you<06:47:48.600> use<06:47:48.780> a 06:47:49.010 --> 06:47:49.020 align:start position:0% Windows so for instance you use a 06:47:49.020 --> 06:47:51.288 align:start position:0% Windows so for instance you use a specific<06:47:49.320> protocol<06:47:49.798> more<06:47:50.160> than<06:47:50.340> others<06:47:50.700> and 06:47:51.288 --> 06:47:51.298 align:start position:0% specific protocol more than others and 06:47:51.298 --> 06:47:52.850 align:start position:0% specific protocol more than others and you're<06:47:51.478> confident<06:47:51.900> in<06:47:52.138> the<06:47:52.260> stability<06:47:52.558> of<06:47:52.740> the 06:47:52.850 --> 06:47:52.860 align:start position:0% you're confident in the stability of the 06:47:52.860 --> 06:47:55.070 align:start position:0% you're confident in the stability of the connection<06:47:53.040> you<06:47:53.878> can<06:47:53.940> change<06:47:54.180> the<06:47:54.540> order<06:47:54.718> of 06:47:55.070 --> 06:47:55.080 align:start position:0% connection you can change the order of 06:47:55.080 --> 06:47:56.150 align:start position:0% connection you can change the order of binding 06:47:56.150 --> 06:47:56.160 align:start position:0% binding 06:47:56.160 --> 06:47:58.250 align:start position:0% binding to<06:47:56.760> potentially<06:47:57.240> speed<06:47:57.600> up<06:47:57.840> your<06:47:58.080> network 06:47:58.250 --> 06:47:58.260 align:start position:0% to potentially speed up your network 06:47:58.260 --> 06:48:00.410 align:start position:0% to potentially speed up your network since<06:47:58.620> what<06:47:58.920> it<06:47:59.040> basically<06:47:59.400> does<06:47:59.700> is<06:48:00.240> it's 06:48:00.410 --> 06:48:00.420 align:start position:0% since what it basically does is it's 06:48:00.420 --> 06:48:03.468 align:start position:0% since what it basically does is it's going<06:48:00.600> to<06:48:00.660> give<06:48:00.780> a<06:48:01.080> list 06:48:03.468 --> 06:48:03.478 align:start position:0% 06:48:03.478 --> 06:48:05.750 align:start position:0% of<06:48:03.958> each<06:48:04.200> protocol<06:48:04.620> that<06:48:04.978> exists<06:48:05.400> and<06:48:05.638> it's 06:48:05.750 --> 06:48:05.760 align:start position:0% of each protocol that exists and it's 06:48:05.760 --> 06:48:07.610 align:start position:0% of each protocol that exists and it's going<06:48:06.000> to<06:48:06.120> hit<06:48:06.240> each<06:48:06.540> protocol<06:48:06.900> one<06:48:07.200> after<06:48:07.378> the 06:48:07.610 --> 06:48:07.620 align:start position:0% going to hit each protocol one after the 06:48:07.620 --> 06:48:08.810 align:start position:0% going to hit each protocol one after the other<06:48:07.740> so<06:48:07.978> if<06:48:08.100> there's<06:48:08.218> one<06:48:08.400> that<06:48:08.520> you<06:48:08.700> use 06:48:08.810 --> 06:48:08.820 align:start position:0% other so if there's one that you use 06:48:08.820 --> 06:48:10.850 align:start position:0% other so if there's one that you use more<06:48:09.058> you<06:48:09.360> can<06:48:09.420> set<06:48:09.600> that<06:48:09.780> at<06:48:09.958> the<06:48:10.138> top<06:48:10.260> so<06:48:10.740> it 06:48:10.850 --> 06:48:10.860 align:start position:0% more you can set that at the top so it 06:48:10.860 --> 06:48:13.128 align:start position:0% more you can set that at the top so it doesn't<06:48:11.040> have<06:48:11.280> as<06:48:11.458> far<06:48:11.700> to<06:48:11.878> go<06:48:12.058> so<06:48:12.718> as<06:48:12.840> we<06:48:13.020> can 06:48:13.128 --> 06:48:13.138 align:start position:0% doesn't have as far to go so as we can 06:48:13.138 --> 06:48:15.048 align:start position:0% doesn't have as far to go so as we can see<06:48:13.260> here<06:48:13.558> we<06:48:13.798> have<06:48:13.978> several<06:48:14.580> default 06:48:15.048 --> 06:48:15.058 align:start position:0% see here we have several default 06:48:15.058 --> 06:48:16.368 align:start position:0% see here we have several default protocols 06:48:16.368 --> 06:48:16.378 align:start position:0% protocols 06:48:16.378 --> 06:48:18.730 align:start position:0% protocols and<06:48:17.100> they're<06:48:17.280> going<06:48:17.400> to<06:48:17.520> be<06:48:17.638> tested<06:48:18.058> in<06:48:18.360> order 06:48:18.730 --> 06:48:18.740 align:start position:0% and they're going to be tested in order 06:48:18.740 --> 06:48:21.468 align:start position:0% and they're going to be tested in order for<06:48:19.740> that<06:48:19.978> available<06:48:20.160> connection 06:48:21.468 --> 06:48:21.478 align:start position:0% for that available connection 06:48:21.478 --> 06:48:23.390 align:start position:0% for that available connection and<06:48:21.900> the<06:48:22.138> first<06:48:22.260> protocol<06:48:22.620> that's<06:48:22.920> found<06:48:23.160> to 06:48:23.390 --> 06:48:23.400 align:start position:0% and the first protocol that's found to 06:48:23.400 --> 06:48:25.310 align:start position:0% and the first protocol that's found to have<06:48:23.580> a<06:48:23.820> matching<06:48:24.120> active<06:48:24.420> protocol<06:48:24.780> on<06:48:25.138> the 06:48:25.310 --> 06:48:25.320 align:start position:0% have a matching active protocol on the 06:48:25.320 --> 06:48:28.368 align:start position:0% have a matching active protocol on the receiving<06:48:25.680> end<06:48:26.180> is<06:48:27.180> going<06:48:27.420> to<06:48:27.718> be<06:48:27.900> the<06:48:28.080> one<06:48:28.200> we 06:48:28.368 --> 06:48:28.378 align:start position:0% receiving end is going to be the one we 06:48:28.378 --> 06:48:31.128 align:start position:0% receiving end is going to be the one we use<06:48:28.620> now<06:48:29.340> that<06:48:29.520> while<06:48:29.760> this<06:48:30.058> might<06:48:30.420> sound<06:48:30.718> like 06:48:31.128 --> 06:48:31.138 align:start position:0% use now that while this might sound like 06:48:31.138 --> 06:48:32.690 align:start position:0% use now that while this might sound like a<06:48:31.320> pretty<06:48:31.440> decent<06:48:31.740> method<06:48:32.040> of<06:48:32.218> doing<06:48:32.340> things 06:48:32.690 --> 06:48:32.700 align:start position:0% a pretty decent method of doing things 06:48:32.700 --> 06:48:35.030 align:start position:0% a pretty decent method of doing things it<06:48:33.298> also<06:48:33.780> opens<06:48:34.138> your<06:48:34.320> computer<06:48:34.558> up<06:48:34.860> to 06:48:35.030 --> 06:48:35.040 align:start position:0% it also opens your computer up to 06:48:35.040 --> 06:48:37.430 align:start position:0% it also opens your computer up to utilizing<06:48:35.580> a<06:48:35.878> lesser<06:48:36.240> protocol<06:48:36.600> which<06:48:37.320> is 06:48:37.430 --> 06:48:37.440 align:start position:0% utilizing a lesser protocol which is 06:48:37.440 --> 06:48:38.750 align:start position:0% utilizing a lesser protocol which is potentially<06:48:37.798> going<06:48:37.920> to<06:48:38.040> give<06:48:38.160> you<06:48:38.280> a<06:48:38.458> slower 06:48:38.750 --> 06:48:38.760 align:start position:0% potentially going to give you a slower 06:48:38.760 --> 06:48:39.770 align:start position:0% potentially going to give you a slower speed 06:48:39.770 --> 06:48:39.780 align:start position:0% speed 06:48:39.780 --> 06:48:42.288 align:start position:0% speed so<06:48:40.200> the<06:48:40.558> graphical<06:48:40.978> interface<06:48:41.580> or<06:48:41.820> properties 06:48:42.288 --> 06:48:42.298 align:start position:0% so the graphical interface or properties 06:48:42.298 --> 06:48:45.770 align:start position:0% so the graphical interface or properties menu<06:48:42.540> for<06:48:43.378> your<06:48:44.160> um<06:48:44.218> network<06:48:45.058> interface<06:48:45.540> card 06:48:45.770 --> 06:48:45.780 align:start position:0% menu for your um network interface card 06:48:45.780 --> 06:48:47.030 align:start position:0% menu for your um network interface card is<06:48:46.020> where<06:48:46.260> you're<06:48:46.440> going<06:48:46.558> to<06:48:46.680> be<06:48:46.798> able<06:48:46.860> to 06:48:47.030 --> 06:48:47.040 align:start position:0% is where you're going to be able to 06:48:47.040 --> 06:48:49.490 align:start position:0% is where you're going to be able to configure<06:48:47.580> all<06:48:48.240> of<06:48:48.360> this<06:48:48.478> stuff<06:48:48.780> stuff<06:48:49.138> such 06:48:49.490 --> 06:48:49.500 align:start position:0% configure all of this stuff stuff such 06:48:49.500 --> 06:48:52.390 align:start position:0% configure all of this stuff stuff such as<06:48:50.000> tcpip 06:48:52.390 --> 06:48:52.400 align:start position:0% as tcpip 06:48:52.400 --> 06:48:55.788 align:start position:0% as tcpip DNS<06:48:53.400> server<06:48:53.760> assignment<06:48:54.180> DHCP<06:48:55.020> and<06:48:55.378> so<06:48:55.500> on<06:48:55.680> and 06:48:55.788 --> 06:48:55.798 align:start position:0% DNS server assignment DHCP and so on and 06:48:55.798 --> 06:48:58.368 align:start position:0% DNS server assignment DHCP and so on and so<06:48:55.978> forth<06:48:56.700> so<06:48:57.240> after<06:48:57.478> all<06:48:57.780> of<06:48:57.900> this<06:48:58.080> it's 06:48:58.368 --> 06:48:58.378 align:start position:0% so forth so after all of this it's 06:48:58.378 --> 06:48:59.810 align:start position:0% so forth so after all of this it's really<06:48:58.558> important<06:48:58.920> to<06:48:59.040> understand<06:48:59.218> that<06:48:59.638> all 06:48:59.810 --> 06:48:59.820 align:start position:0% really important to understand that all 06:48:59.820 --> 06:49:02.330 align:start position:0% really important to understand that all this<06:49:00.058> organizing<06:49:00.740> categorizing<06:49:01.740> defining<06:49:02.218> of 06:49:02.330 --> 06:49:02.340 align:start position:0% this organizing categorizing defining of 06:49:02.340 --> 06:49:04.010 align:start position:0% this organizing categorizing defining of these<06:49:02.520> protocols<06:49:02.940> the<06:49:03.180> assigning<06:49:03.600> of<06:49:03.718> rules 06:49:04.010 --> 06:49:04.020 align:start position:0% these protocols the assigning of rules 06:49:04.020 --> 06:49:06.650 align:start position:0% these protocols the assigning of rules and<06:49:04.138> roles<06:49:04.500> all<06:49:05.100> of<06:49:05.280> this<06:49:05.458> the<06:49:05.940> the<06:49:06.298> internet 06:49:06.650 --> 06:49:06.660 align:start position:0% and roles all of this the the internet 06:49:06.660 --> 06:49:09.230 align:start position:0% and roles all of this the the internet didn't<06:49:07.620> just<06:49:07.860> happen<06:49:08.100> overnight<06:49:08.638> it's<06:49:09.058> not 06:49:09.230 --> 06:49:09.240 align:start position:0% didn't just happen overnight it's not 06:49:09.240 --> 06:49:10.968 align:start position:0% didn't just happen overnight it's not even<06:49:09.478> necessarily<06:49:10.080> the<06:49:10.260> way<06:49:10.378> we<06:49:10.500> did<06:49:10.680> it<06:49:10.798> on 06:49:10.968 --> 06:49:10.978 align:start position:0% even necessarily the way we did it on 06:49:10.978 --> 06:49:13.368 align:start position:0% even necessarily the way we did it on purpose<06:49:11.360> these<06:49:12.360> standards<06:49:12.718> and<06:49:12.840> these<06:49:13.080> models 06:49:13.368 --> 06:49:13.378 align:start position:0% purpose these standards and these models 06:49:13.378 --> 06:49:16.070 align:start position:0% purpose these standards and these models are<06:49:13.620> going<06:49:13.798> to<06:49:13.978> continue<06:49:14.458> to<06:49:15.000> expand<06:49:15.420> and 06:49:16.070 --> 06:49:16.080 align:start position:0% are going to continue to expand and 06:49:16.080 --> 06:49:19.190 align:start position:0% are going to continue to expand and change<06:49:16.458> and<06:49:17.458> eventually<06:49:18.120> might<06:49:18.420> even<06:49:18.540> have<06:49:18.840> a 06:49:19.190 --> 06:49:19.200 align:start position:0% change and eventually might even have a 06:49:19.200 --> 06:49:20.510 align:start position:0% change and eventually might even have a brand<06:49:19.320> new<06:49:19.500> model<06:49:19.798> that<06:49:20.100> we're<06:49:20.218> going<06:49:20.340> to<06:49:20.400> have 06:49:20.510 --> 06:49:20.520 align:start position:0% brand new model that we're going to have 06:49:20.520 --> 06:49:21.590 align:start position:0% brand new model that we're going to have to<06:49:20.700> learn<06:49:20.878> about 06:49:21.590 --> 06:49:21.600 align:start position:0% to learn about 06:49:21.600 --> 06:49:23.690 align:start position:0% to learn about but<06:49:22.080> in<06:49:22.260> the<06:49:22.378> meantime<06:49:22.740> these<06:49:23.280> models<06:49:23.580> are 06:49:23.690 --> 06:49:23.700 align:start position:0% but in the meantime these models are 06:49:23.700 --> 06:49:25.548 align:start position:0% but in the meantime these models are here<06:49:23.940> to<06:49:24.120> stay<06:49:24.298> and<06:49:24.840> they're<06:49:24.958> going<06:49:25.138> to<06:49:25.260> remain 06:49:25.548 --> 06:49:25.558 align:start position:0% here to stay and they're going to remain 06:49:25.558 --> 06:49:28.670 align:start position:0% here to stay and they're going to remain really<06:49:25.920> important<06:49:26.520> and<06:49:26.940> especially<06:49:27.378> uh<06:49:28.378> in 06:49:28.670 --> 06:49:28.680 align:start position:0% really important and especially uh in 06:49:28.680 --> 06:49:30.230 align:start position:0% really important and especially uh in the<06:49:28.740> future<06:49:28.920> you<06:49:29.340> have<06:49:29.520> to<06:49:29.638> understand<06:49:29.820> the 06:49:30.230 --> 06:49:30.240 align:start position:0% the future you have to understand the 06:49:30.240 --> 06:49:32.208 align:start position:0% the future you have to understand the historical<06:49:30.718> roots<06:49:31.138> of<06:49:31.320> the<06:49:31.440> network<06:49:31.620> so<06:49:32.100> you 06:49:32.208 --> 06:49:32.218 align:start position:0% historical roots of the network so you 06:49:32.218 --> 06:49:34.548 align:start position:0% historical roots of the network so you can<06:49:32.340> be<06:49:32.458> able<06:49:32.580> to<06:49:32.700> Define<06:49:32.940> not<06:49:33.840> only<06:49:33.958> how<06:49:34.320> to<06:49:34.378> go 06:49:34.548 --> 06:49:34.558 align:start position:0% can be able to Define not only how to go 06:49:34.558 --> 06:49:37.010 align:start position:0% can be able to Define not only how to go forward<06:49:34.920> in<06:49:35.160> the<06:49:35.340> future<06:49:35.520> but<06:49:36.298> also<06:49:36.540> how<06:49:36.840> to 06:49:37.010 --> 06:49:37.020 align:start position:0% forward in the future but also how to 06:49:37.020 --> 06:49:38.390 align:start position:0% forward in the future but also how to you<06:49:37.320> know<06:49:37.378> prepare<06:49:37.620> yourself<06:49:37.798> for<06:49:38.160> a<06:49:38.280> network 06:49:38.390 --> 06:49:38.400 align:start position:0% you know prepare yourself for a network 06:49:38.400 --> 06:49:40.670 align:start position:0% you know prepare yourself for a network plus<06:49:38.638> exam<06:49:39.058> so<06:49:39.780> let's<06:49:40.020> just<06:49:40.200> go<06:49:40.320> back<06:49:40.500> over 06:49:40.670 --> 06:49:40.680 align:start position:0% plus exam so let's just go back over 06:49:40.680 --> 06:49:42.110 align:start position:0% plus exam so let's just go back over everything<06:49:40.920> we've<06:49:41.280> talked<06:49:41.520> about<06:49:41.580> one<06:49:41.878> last 06:49:42.110 --> 06:49:42.120 align:start position:0% everything we've talked about one last 06:49:42.120 --> 06:49:44.690 align:start position:0% everything we've talked about one last time<06:49:42.420> we<06:49:43.020> covered<06:49:43.320> in<06:49:43.500> great<06:49:43.798> a<06:49:44.340> lot<06:49:44.400> of<06:49:44.580> stuff 06:49:44.690 --> 06:49:44.700 align:start position:0% time we covered in great a lot of stuff 06:49:44.700 --> 06:49:46.730 align:start position:0% time we covered in great a lot of stuff here<06:49:44.878> right<06:49:45.120> first<06:49:45.478> we<06:49:45.900> explain<06:49:46.080> the<06:49:46.440> purpose 06:49:46.730 --> 06:49:46.740 align:start position:0% here right first we explain the purpose 06:49:46.740 --> 06:49:50.150 align:start position:0% here right first we explain the purpose of<06:49:46.920> the<06:49:47.040> TCP<06:49:47.520> model<06:49:48.180> and<06:49:48.958> we<06:49:49.138> compared<06:49:49.798> the 06:49:50.150 --> 06:49:50.160 align:start position:0% of the TCP model and we compared the 06:49:50.160 --> 06:49:52.610 align:start position:0% of the TCP model and we compared the tcpip<06:49:51.000> model<06:49:51.420> with<06:49:51.718> the<06:49:51.840> OSI<06:49:52.320> model 06:49:52.610 --> 06:49:52.620 align:start position:0% tcpip model with the OSI model 06:49:52.620 --> 06:49:55.128 align:start position:0% tcpip model with the OSI model remembering<06:49:53.340> that<06:49:53.520> the<06:49:53.820> top<06:49:54.058> three<06:49:54.360> layers<06:49:54.900> if 06:49:55.128 --> 06:49:55.138 align:start position:0% remembering that the top three layers if 06:49:55.138 --> 06:49:57.230 align:start position:0% remembering that the top three layers if we<06:49:55.320> look<06:49:55.620> at<06:49:55.798> this 06:49:57.230 --> 06:49:57.240 align:start position:0% we look at this 06:49:57.240 --> 06:50:00.590 align:start position:0% we look at this if<06:49:57.600> we<06:49:57.780> do<06:49:58.020> the<06:49:58.320> three<06:49:58.978> two<06:49:59.340> one<06:49:59.760> and<06:50:00.298> then<06:50:00.478> we 06:50:00.590 --> 06:50:00.600 align:start position:0% if we do the three two one and then we 06:50:00.600 --> 06:50:05.270 align:start position:0% if we do the three two one and then we look<06:50:00.840> at<06:50:01.138> seven<06:50:01.740> six<06:50:02.340> five<06:50:03.120> four 06:50:05.270 --> 06:50:05.280 align:start position:0% look at seven six five four 06:50:05.280 --> 06:50:07.730 align:start position:0% look at seven six five four right<06:50:05.878> two<06:50:06.298> and<06:50:06.540> one<06:50:06.780> physical<06:50:07.138> and<06:50:07.378> data<06:50:07.680> link 06:50:07.730 --> 06:50:07.740 align:start position:0% right two and one physical and data link 06:50:07.740 --> 06:50:10.788 align:start position:0% right two and one physical and data link are<06:50:07.978> going<06:50:08.100> to<06:50:08.218> go<06:50:08.340> straight<06:50:08.580> over<06:50:08.878> here 06:50:10.788 --> 06:50:10.798 align:start position:0% are going to go straight over here 06:50:10.798 --> 06:50:13.850 align:start position:0% are going to go straight over here to<06:50:11.458> uh<06:50:11.760> that<06:50:12.058> physical<06:50:12.298> layer<06:50:13.200> one<06:50:13.378> of<06:50:13.740> the 06:50:13.850 --> 06:50:13.860 align:start position:0% to uh that physical layer one of the 06:50:13.860 --> 06:50:15.590 align:start position:0% to uh that physical layer one of the tcpip<06:50:14.520> model 06:50:15.590 --> 06:50:15.600 align:start position:0% tcpip model 06:50:15.600 --> 06:50:17.150 align:start position:0% tcpip model then 06:50:17.150 --> 06:50:17.160 align:start position:0% then 06:50:17.160 --> 06:50:19.910 align:start position:0% then the<06:50:17.700> network<06:50:17.820> layer<06:50:18.298> is<06:50:18.420> going<06:50:18.718> to 06:50:19.910 --> 06:50:19.920 align:start position:0% the network layer is going to 06:50:19.920 --> 06:50:21.590 align:start position:0% the network layer is going to correspond<06:50:20.638> directly<06:50:21.000> to<06:50:21.240> the<06:50:21.420> internet 06:50:21.590 --> 06:50:21.600 align:start position:0% correspond directly to the internet 06:50:21.600 --> 06:50:24.110 align:start position:0% correspond directly to the internet layer<06:50:22.080> the<06:50:22.920> transport<06:50:23.340> layers<06:50:23.700> are<06:50:23.878> going<06:50:24.000> to 06:50:24.110 --> 06:50:24.120 align:start position:0% layer the transport layers are going to 06:50:24.120 --> 06:50:27.048 align:start position:0% layer the transport layers are going to be<06:50:24.180> the<06:50:24.420> same 06:50:27.048 --> 06:50:27.058 align:start position:0% 06:50:27.058 --> 06:50:28.548 align:start position:0% and 06:50:28.548 --> 06:50:28.558 align:start position:0% and 06:50:28.558 --> 06:50:31.670 align:start position:0% and session<06:50:29.340> presentation<06:50:30.298> and<06:50:30.600> application<06:50:31.080> all 06:50:31.670 --> 06:50:31.680 align:start position:0% session presentation and application all 06:50:31.680 --> 06:50:35.990 align:start position:0% session presentation and application all go<06:50:31.978> over<06:50:32.160> to<06:50:32.520> the<06:50:32.878> presentation<06:50:33.540> layer<06:50:34.020> in<06:50:34.500> TCP 06:50:35.990 --> 06:50:36.000 align:start position:0% go over to the presentation layer in TCP 06:50:36.000 --> 06:50:38.270 align:start position:0% go over to the presentation layer in TCP we<06:50:36.478> also<06:50:36.718> talked<06:50:37.080> about<06:50:37.200> defining<06:50:37.860> data 06:50:38.270 --> 06:50:38.280 align:start position:0% we also talked about defining data 06:50:38.280 --> 06:50:40.610 align:start position:0% we also talked about defining data encapsulation<06:50:39.058> and<06:50:39.900> we<06:50:40.020> walk<06:50:40.138> through<06:50:40.320> how 06:50:40.610 --> 06:50:40.620 align:start position:0% encapsulation and we walk through how 06:50:40.620 --> 06:50:42.650 align:start position:0% encapsulation and we walk through how fragmentation<06:50:41.340> works<06:50:41.940> on<06:50:42.240> the<06:50:42.478> internet 06:50:42.650 --> 06:50:42.660 align:start position:0% fragmentation works on the internet 06:50:42.660 --> 06:50:46.910 align:start position:0% fragmentation works on the internet layer 06:50:46.910 --> 06:50:46.920 align:start position:0% 06:50:46.920 --> 06:50:48.590 align:start position:0% and<06:50:47.340> the<06:50:47.458> reason<06:50:47.580> we<06:50:47.820> need<06:50:47.940> to<06:50:48.058> do<06:50:48.240> that<06:50:48.360> is 06:50:48.590 --> 06:50:48.600 align:start position:0% and the reason we need to do that is 06:50:48.600 --> 06:50:52.070 align:start position:0% and the reason we need to do that is because<06:50:48.900> of<06:50:49.740> the<06:50:49.920> maximum<06:50:50.340> transmission<06:50:50.638> unit 06:50:52.070 --> 06:50:52.080 align:start position:0% because of the maximum transmission unit 06:50:52.080 --> 06:50:54.590 align:start position:0% because of the maximum transmission unit finally<06:50:52.680> we<06:50:52.978> talked<06:50:53.218> about<06:50:53.280> the<06:50:53.878> fourth<06:50:54.298> third 06:50:54.590 --> 06:50:54.600 align:start position:0% finally we talked about the fourth third 06:50:54.600 --> 06:50:57.530 align:start position:0% finally we talked about the fourth third second<06:50:55.138> and<06:50:55.500> first<06:50:55.740> layers<06:50:56.100> of<06:50:56.340> the<06:50:56.540> tcpip 06:50:57.530 --> 06:50:57.540 align:start position:0% second and first layers of the tcpip 06:50:57.540 --> 06:51:01.548 align:start position:0% second and first layers of the tcpip model<06:50:57.900> and<06:50:58.798> on<06:50:59.160> each<06:50:59.458> model<06:50:59.820> we<06:51:00.540> outlined<06:51:01.138> some 06:51:01.548 --> 06:51:01.558 align:start position:0% model and on each model we outlined some 06:51:01.558 --> 06:51:03.948 align:start position:0% model and on each model we outlined some of<06:51:01.740> the<06:51:01.978> important<06:51:02.340> aspects<06:51:02.760> of<06:51:02.940> each<06:51:03.180> layer 06:51:03.948 --> 06:51:03.958 align:start position:0% of the important aspects of each layer 06:51:03.958 --> 06:51:06.530 align:start position:0% of the important aspects of each layer such<06:51:04.620> as<06:51:04.878> the 06:51:06.530 --> 06:51:06.540 align:start position:0% such as the 06:51:06.540 --> 06:51:07.510 align:start position:0% such as the um 06:51:07.510 --> 06:51:07.520 align:start position:0% um 06:51:07.520 --> 06:51:09.468 align:start position:0% um application<06:51:08.520> layer 06:51:09.468 --> 06:51:09.478 align:start position:0% application layer 06:51:09.478 --> 06:51:11.810 align:start position:0% application layer which<06:51:10.020> again<06:51:10.138> is<06:51:10.680> the<06:51:11.160> way<06:51:11.400> that<06:51:11.638> the 06:51:11.810 --> 06:51:11.820 align:start position:0% which again is the way that the 06:51:11.820 --> 06:51:14.150 align:start position:0% which again is the way that the application<06:51:12.240> is<06:51:12.540> going<06:51:12.780> to<06:51:13.138> process<06:51:13.620> all<06:51:13.978> this 06:51:14.150 --> 06:51:14.160 align:start position:0% application is going to process all this 06:51:14.160 --> 06:51:18.590 align:start position:0% application is going to process all this information<06:51:14.540> the<06:51:15.540> Tran<06:51:15.958> sport<06:51:16.378> layer 06:51:18.590 --> 06:51:18.600 align:start position:0% information the Tran sport layer 06:51:18.600 --> 06:51:22.910 align:start position:0% information the Tran sport layer which<06:51:19.200> is<06:51:19.320> in<06:51:19.500> charge<06:51:19.620> of<06:51:19.860> reliability 06:51:22.910 --> 06:51:22.920 align:start position:0% 06:51:22.920 --> 06:51:26.090 align:start position:0% and<06:51:23.280> it<06:51:23.520> is<06:51:23.700> where<06:51:24.058> TCP<06:51:24.900> which<06:51:25.740> is<06:51:25.860> connection 06:51:26.090 --> 06:51:26.100 align:start position:0% and it is where TCP which is connection 06:51:26.100 --> 06:51:29.030 align:start position:0% and it is where TCP which is connection oriented<06:51:26.878> or<06:51:27.660> UDP<06:51:28.020> which<06:51:28.260> is<06:51:28.378> connection<06:51:28.558> less 06:51:29.030 --> 06:51:29.040 align:start position:0% oriented or UDP which is connection less 06:51:29.040 --> 06:51:31.850 align:start position:0% oriented or UDP which is connection less live<06:51:29.660> and<06:51:30.660> this<06:51:30.780> is<06:51:30.900> also<06:51:31.138> going<06:51:31.320> to<06:51:31.500> deal<06:51:31.558> with 06:51:31.850 --> 06:51:31.860 align:start position:0% live and this is also going to deal with 06:51:31.860 --> 06:51:35.330 align:start position:0% live and this is also going to deal with flow<06:51:32.700> control 06:51:35.330 --> 06:51:35.340 align:start position:0% 06:51:35.340 --> 06:51:43.730 align:start position:0% and<06:51:35.940> also<06:51:36.240> segmentation 06:51:43.730 --> 06:51:43.740 align:start position:0% 06:51:43.740 --> 06:51:47.750 align:start position:0% we<06:51:44.638> looked<06:51:44.940> at<06:51:45.000> uh<06:51:45.840> Layer<06:51:46.260> Two<06:51:46.500> as<06:51:46.978> well<06:51:47.100> which 06:51:47.750 --> 06:51:47.760 align:start position:0% we looked at uh Layer Two as well which 06:51:47.760 --> 06:51:50.150 align:start position:0% we looked at uh Layer Two as well which is<06:51:47.940> the<06:51:48.298> internet<06:51:48.420> layer 06:51:50.150 --> 06:51:50.160 align:start position:0% is the internet layer 06:51:50.160 --> 06:51:56.030 align:start position:0% is the internet layer and<06:51:50.700> the<06:51:50.878> fragmentation<06:51:51.478> that<06:51:51.780> happens<06:51:51.958> there 06:51:56.030 --> 06:51:56.040 align:start position:0% 06:51:56.040 --> 06:51:58.490 align:start position:0% and<06:51:56.458> network<06:51:56.700> one<06:51:57.120> the<06:51:57.600> network<06:51:57.780> interface 06:51:58.490 --> 06:51:58.500 align:start position:0% and network one the network interface 06:51:58.500 --> 06:52:04.368 align:start position:0% and network one the network interface layer 06:52:04.368 --> 06:52:04.378 align:start position:0% 06:52:04.378 --> 06:52:06.288 align:start position:0% which<06:52:04.798> is<06:52:04.978> equivalent<06:52:05.400> to<06:52:05.580> all<06:52:05.760> that<06:52:06.000> physical 06:52:06.288 --> 06:52:06.298 align:start position:0% which is equivalent to all that physical 06:52:06.298 --> 06:52:08.570 align:start position:0% which is equivalent to all that physical stuff<06:52:06.780> that<06:52:07.020> we've<06:52:07.200> talked<06:52:07.558> about<06:52:07.620> we<06:52:08.340> also 06:52:08.570 --> 06:52:08.580 align:start position:0% stuff that we've talked about we also 06:52:08.580 --> 06:52:10.850 align:start position:0% stuff that we've talked about we also looked<06:52:08.878> at<06:52:08.878> how<06:52:09.360> the<06:52:09.718> terminology<06:52:10.200> changes 06:52:10.850 --> 06:52:10.860 align:start position:0% looked at how the terminology changes 06:52:10.860 --> 06:52:13.430 align:start position:0% looked at how the terminology changes remember<06:52:11.458> on<06:52:11.820> layer<06:52:12.240> four<06:52:12.478> we're<06:52:13.200> talking 06:52:13.430 --> 06:52:13.440 align:start position:0% remember on layer four we're talking 06:52:13.440 --> 06:52:15.230 align:start position:0% remember on layer four we're talking about<06:52:13.740> data 06:52:15.230 --> 06:52:15.240 align:start position:0% about data 06:52:15.240 --> 06:52:17.750 align:start position:0% about data on<06:52:15.900> layer<06:52:16.260> three 06:52:17.750 --> 06:52:17.760 align:start position:0% on layer three 06:52:17.760 --> 06:52:20.930 align:start position:0% on layer three we're<06:52:18.240> dealing<06:52:18.540> with<06:52:18.718> segments 06:52:20.930 --> 06:52:20.940 align:start position:0% we're dealing with segments 06:52:20.940 --> 06:52:25.670 align:start position:0% we're dealing with segments on<06:52:21.478> Layer<06:52:21.840> Two 06:52:25.670 --> 06:52:25.680 align:start position:0% 06:52:25.680 --> 06:52:28.010 align:start position:0% we're<06:52:26.100> dealing<06:52:26.340> with<06:52:26.580> datagrams<06:52:27.360> also<06:52:27.780> called 06:52:28.010 --> 06:52:28.020 align:start position:0% we're dealing with datagrams also called 06:52:28.020 --> 06:52:32.270 align:start position:0% we're dealing with datagrams also called packets<06:52:28.760> and<06:52:29.760> we<06:52:30.298> broke<06:52:30.660> down<06:52:30.840> then<06:52:31.260> on<06:52:31.920> layer 06:52:32.270 --> 06:52:32.280 align:start position:0% packets and we broke down then on layer 06:52:32.280 --> 06:52:34.070 align:start position:0% packets and we broke down then on layer one 06:52:34.070 --> 06:52:34.080 align:start position:0% one 06:52:34.080 --> 06:52:36.948 align:start position:0% one frames<06:52:34.860> and<06:52:35.520> an<06:52:35.638> Ethernet<06:52:36.120> frame<06:52:36.478> and<06:52:36.660> all<06:52:36.780> the 06:52:36.948 --> 06:52:36.958 align:start position:0% frames and an Ethernet frame and all the 06:52:36.958 --> 06:52:40.310 align:start position:0% frames and an Ethernet frame and all the information<06:52:37.080> that<06:52:37.500> goes<06:52:37.740> into<06:52:37.860> that 06:52:40.310 --> 06:52:40.320 align:start position:0% 06:52:40.320 --> 06:52:43.250 align:start position:0% finally<06:52:40.978> we<06:52:41.280> Define<06:52:41.458> what<06:52:41.878> an<06:52:42.058> MTU<06:52:42.540> black<06:52:42.718> hole 06:52:43.250 --> 06:52:43.260 align:start position:0% finally we Define what an MTU black hole 06:52:43.260 --> 06:52:45.230 align:start position:0% finally we Define what an MTU black hole was<06:52:43.378> and<06:52:43.920> we<06:52:44.100> finished<06:52:44.340> off<06:52:44.638> everything<06:52:44.878> by 06:52:45.230 --> 06:52:45.240 align:start position:0% was and we finished off everything by 06:52:45.240 --> 06:52:47.750 align:start position:0% was and we finished off everything by talking<06:52:45.420> about<06:52:45.600> protocol<06:52:46.200> binding<06:52:46.860> which<06:52:47.580> is 06:52:47.750 --> 06:52:47.760 align:start position:0% talking about protocol binding which is 06:52:47.760 --> 06:52:49.730 align:start position:0% talking about protocol binding which is binding<06:52:48.240> certain<06:52:48.478> protocols<06:52:49.138> to<06:52:49.320> specific 06:52:49.730 --> 06:52:49.740 align:start position:0% binding certain protocols to specific 06:52:49.740 --> 06:52:57.020 align:start position:0% binding certain protocols to specific Nicks<06:52:50.340> and<06:52:50.700> in<06:52:50.878> a<06:52:51.360> in<06:52:51.958> a<06:52:52.138> delineated<06:52:52.558> order 06:52:57.020 --> 06:52:57.030 align:start position:0% 06:52:57.030 --> 06:53:17.208 align:start position:0% [Music] 06:53:17.208 --> 06:53:17.218 align:start position:0% 06:53:17.218 --> 06:53:19.750 align:start position:0% Network<06:53:17.878> infrastructure<06:53:18.840> and<06:53:19.138> design 06:53:19.750 --> 06:53:19.760 align:start position:0% Network infrastructure and design 06:53:19.760 --> 06:53:22.490 align:start position:0% Network infrastructure and design ethernet<06:53:20.760> and<06:53:21.360> implementing<06:53:21.900> a<06:53:22.320> wireless 06:53:22.490 --> 06:53:22.500 align:start position:0% ethernet and implementing a wireless 06:53:22.500 --> 06:53:24.948 align:start position:0% ethernet and implementing a wireless network 06:53:24.948 --> 06:53:24.958 align:start position:0% network 06:53:24.958 --> 06:53:27.890 align:start position:0% network so<06:53:25.798> in<06:53:26.340> the<06:53:26.520> previous<06:53:26.638> modules<06:53:27.240> we<06:53:27.718> were 06:53:27.890 --> 06:53:27.900 align:start position:0% so in the previous modules we were 06:53:27.900 --> 06:53:30.110 align:start position:0% so in the previous modules we were introduced<06:53:28.378> to<06:53:28.798> many<06:53:28.978> networking<06:53:29.520> standards 06:53:30.110 --> 06:53:30.120 align:start position:0% introduced to many networking standards 06:53:30.120 --> 06:53:33.770 align:start position:0% introduced to many networking standards models<06:53:30.840> and<06:53:31.558> Technologies<06:53:32.218> now<06:53:33.058> this<06:53:33.420> module 06:53:33.770 --> 06:53:33.780 align:start position:0% models and Technologies now this module 06:53:33.780 --> 06:53:35.930 align:start position:0% models and Technologies now this module is<06:53:34.020> going<06:53:34.200> into<06:53:34.620> ethernet<06:53:35.340> a<06:53:35.700> little<06:53:35.820> bit 06:53:35.930 --> 06:53:35.940 align:start position:0% is going into ethernet a little bit 06:53:35.940 --> 06:53:37.670 align:start position:0% is going into ethernet a little bit further<06:53:36.298> and<06:53:37.020> specifically<06:53:37.440> the 06:53:37.670 --> 06:53:37.680 align:start position:0% further and specifically the 06:53:37.680 --> 06:53:40.968 align:start position:0% further and specifically the implementation<06:53:38.280> of<06:53:39.058> a<06:53:39.240> wireless<06:53:39.478> network<06:53:39.978> so 06:53:40.968 --> 06:53:40.978 align:start position:0% implementation of a wireless network so 06:53:40.978 --> 06:53:43.190 align:start position:0% implementation of a wireless network so the<06:53:41.218> module<06:53:41.520> objectives<06:53:41.940> are<06:53:42.298> first<06:53:42.540> to 06:53:43.190 --> 06:53:43.200 align:start position:0% the module objectives are first to 06:53:43.200 --> 06:53:45.110 align:start position:0% the module objectives are first to outline<06:53:43.440> the<06:53:43.620> different<06:53:43.798> types<06:53:44.458> of<06:53:44.700> ethernet 06:53:45.110 --> 06:53:45.120 align:start position:0% outline the different types of ethernet 06:53:45.120 --> 06:53:47.510 align:start position:0% outline the different types of ethernet networks<06:53:45.840> that<06:53:46.080> exist<06:53:46.378> and<06:53:47.100> then<06:53:47.218> we're<06:53:47.340> going 06:53:47.510 --> 06:53:47.520 align:start position:0% networks that exist and then we're going 06:53:47.520 --> 06:53:50.628 align:start position:0% networks that exist and then we're going to<06:53:47.638> go<06:53:47.760> into<06:53:47.940> the<06:53:48.360> explanation<06:53:48.780> of<06:53:49.138> WLAN<06:53:49.920> or 06:53:50.628 --> 06:53:50.638 align:start position:0% to go into the explanation of WLAN or 06:53:50.638 --> 06:53:53.868 align:start position:0% to go into the explanation of WLAN or wireless<06:53:51.058> LAN<06:53:51.840> architecture 06:53:53.868 --> 06:53:53.878 align:start position:0% wireless LAN architecture 06:53:53.878 --> 06:53:56.868 align:start position:0% wireless LAN architecture then<06:53:54.540> we're<06:53:54.900> going<06:53:55.320> to<06:53:55.860> Define<06:53:56.100> and<06:53:56.458> describe 06:53:56.868 --> 06:53:56.878 align:start position:0% then we're going to Define and describe 06:53:56.878 --> 06:53:59.090 align:start position:0% then we're going to Define and describe the<06:53:57.180> characteristics<06:53:57.780> of<06:53:58.080> an<06:53:58.320> antenna<06:53:58.740> and 06:53:59.090 --> 06:53:59.100 align:start position:0% the characteristics of an antenna and 06:53:59.100 --> 06:54:00.830 align:start position:0% the characteristics of an antenna and have<06:53:59.280> different<06:53:59.458> types<06:53:59.940> of<06:54:00.058> antennas<06:54:00.540> which 06:54:00.830 --> 06:54:00.840 align:start position:0% have different types of antennas which 06:54:00.840 --> 06:54:02.628 align:start position:0% have different types of antennas which is<06:54:01.080> actually<06:54:01.320> pretty<06:54:01.920> important<06:54:02.340> for<06:54:02.520> the 06:54:02.628 --> 06:54:02.638 align:start position:0% is actually pretty important for the 06:54:02.638 --> 06:54:05.330 align:start position:0% is actually pretty important for the network<06:54:02.760> plus<06:54:03.058> exam<06:54:03.540> specifically 06:54:05.330 --> 06:54:05.340 align:start position:0% network plus exam specifically 06:54:05.340 --> 06:54:08.990 align:start position:0% network plus exam specifically wireless<06:54:06.000> antenna<06:54:06.780> performance<06:54:07.558> factors<06:54:08.040> and 06:54:08.990 --> 06:54:09.000 align:start position:0% wireless antenna performance factors and 06:54:09.000 --> 06:54:10.190 align:start position:0% wireless antenna performance factors and then<06:54:09.120> by<06:54:09.298> the<06:54:09.420> end<06:54:09.540> of<06:54:09.660> the<06:54:09.780> module<06:54:10.080> we're 06:54:10.190 --> 06:54:10.200 align:start position:0% then by the end of the module we're 06:54:10.200 --> 06:54:11.868 align:start position:0% then by the end of the module we're going<06:54:10.320> to<06:54:10.378> have<06:54:10.620> a<06:54:10.978> complete<06:54:11.280> understanding 06:54:11.868 --> 06:54:11.878 align:start position:0% going to have a complete understanding 06:54:11.878 --> 06:54:14.990 align:start position:0% going to have a complete understanding of<06:54:12.540> the<06:54:12.780> 802.11<06:54:13.680> standard<06:54:14.340> and<06:54:14.700> its 06:54:14.990 --> 06:54:15.000 align:start position:0% of the 802.11 standard and its 06:54:15.000 --> 06:54:18.170 align:start position:0% of the 802.11 standard and its Associated<06:54:15.620> modes<06:54:16.620> we're<06:54:17.100> going<06:54:17.340> to<06:54:17.700> talk 06:54:18.170 --> 06:54:18.180 align:start position:0% Associated modes we're going to talk 06:54:18.180 --> 06:54:21.948 align:start position:0% Associated modes we're going to talk about<06:54:18.478> uh<06:54:19.320> the<06:54:19.620> beacon<06:54:19.978> frame<06:54:20.360> and<06:54:21.360> we're<06:54:21.660> also 06:54:21.948 --> 06:54:21.958 align:start position:0% about uh the beacon frame and we're also 06:54:21.958 --> 06:54:25.250 align:start position:0% about uh the beacon frame and we're also going<06:54:22.200> to<06:54:22.620> talk<06:54:23.520> about<06:54:23.760> what<06:54:24.660> determines 06:54:25.250 --> 06:54:25.260 align:start position:0% going to talk about what determines 06:54:25.260 --> 06:54:27.770 align:start position:0% going to talk about what determines where<06:54:25.680> you<06:54:25.860> place<06:54:26.280> your<06:54:27.000> wireless<06:54:27.180> access 06:54:27.770 --> 06:54:27.780 align:start position:0% where you place your wireless access 06:54:27.780 --> 06:54:31.670 align:start position:0% where you place your wireless access point<06:54:28.320> or<06:54:29.218> your<06:54:29.580> WAP 06:54:31.670 --> 06:54:31.680 align:start position:0% point or your WAP 06:54:31.680 --> 06:54:34.310 align:start position:0% point or your WAP and<06:54:32.218> we'll<06:54:32.458> finish<06:54:32.760> by<06:54:33.180> talking<06:54:33.360> about<06:54:33.600> how<06:54:34.200> to 06:54:34.310 --> 06:54:34.320 align:start position:0% and we'll finish by talking about how to 06:54:34.320 --> 06:54:37.910 align:start position:0% and we'll finish by talking about how to properly<06:54:34.680> Implement<06:54:35.340> a<06:54:36.058> wireless<06:54:36.240> network 06:54:37.910 --> 06:54:37.920 align:start position:0% properly Implement a wireless network 06:54:37.920 --> 06:54:40.610 align:start position:0% properly Implement a wireless network so<06:54:38.580> an<06:54:38.820> Ethernet<06:54:39.180> network<06:54:39.420> is<06:54:39.840> perhaps<06:54:40.138> one<06:54:40.500> of 06:54:40.610 --> 06:54:40.620 align:start position:0% so an Ethernet network is perhaps one of 06:54:40.620 --> 06:54:42.410 align:start position:0% so an Ethernet network is perhaps one of the<06:54:40.860> easiest<06:54:41.218> networks<06:54:41.820> to<06:54:42.058> plan<06:54:42.240> and 06:54:42.410 --> 06:54:42.420 align:start position:0% the easiest networks to plan and 06:54:42.420 --> 06:54:44.330 align:start position:0% the easiest networks to plan and implement<06:54:43.200> depending<06:54:43.620> on<06:54:43.740> the<06:54:43.860> size<06:54:43.978> of<06:54:44.218> your 06:54:44.330 --> 06:54:44.340 align:start position:0% implement depending on the size of your 06:54:44.340 --> 06:54:45.708 align:start position:0% implement depending on the size of your network<06:54:44.520> and<06:54:44.820> the<06:54:44.940> equipment<06:54:45.180> being<06:54:45.478> used 06:54:45.708 --> 06:54:45.718 align:start position:0% network and the equipment being used 06:54:45.718 --> 06:54:47.750 align:start position:0% network and the equipment being used there<06:54:46.260> are<06:54:46.378> a<06:54:46.440> bunch<06:54:46.500> of<06:54:46.620> different<06:54:46.740> kinds<06:54:47.458> of 06:54:47.750 --> 06:54:47.760 align:start position:0% there are a bunch of different kinds of 06:54:47.760 --> 06:54:49.788 align:start position:0% there are a bunch of different kinds of small<06:54:48.240> ethernet<06:54:48.840> Network<06:54:49.080> implementations 06:54:49.788 --> 06:54:49.798 align:start position:0% small ethernet Network implementations 06:54:49.798 --> 06:54:51.948 align:start position:0% small ethernet Network implementations that<06:54:50.160> you<06:54:50.280> can<06:54:50.400> use<06:54:50.638> some<06:54:51.478> of<06:54:51.600> the<06:54:51.718> typical 06:54:51.948 --> 06:54:51.958 align:start position:0% that you can use some of the typical 06:54:51.958 --> 06:54:53.510 align:start position:0% that you can use some of the typical equipment<06:54:52.378> that<06:54:52.620> you're<06:54:52.740> going<06:54:52.860> to<06:54:52.978> find<06:54:53.160> in 06:54:53.510 --> 06:54:53.520 align:start position:0% equipment that you're going to find in 06:54:53.520 --> 06:54:56.330 align:start position:0% equipment that you're going to find in an<06:54:53.700> Ethernet<06:54:54.120> Network<06:54:54.360> might<06:54:55.020> be<06:54:55.200> a<06:54:55.378> hub 06:54:56.330 --> 06:54:56.340 align:start position:0% an Ethernet Network might be a hub 06:54:56.340 --> 06:54:58.788 align:start position:0% an Ethernet Network might be a hub an<06:54:56.700> ethernet<06:54:57.120> cable<06:54:57.478> which<06:54:58.138> can<06:54:58.378> either<06:54:58.558> be 06:54:58.788 --> 06:54:58.798 align:start position:0% an ethernet cable which can either be 06:54:58.798 --> 06:55:03.110 align:start position:0% an ethernet cable which can either be what<06:54:59.040> we<06:54:59.218> call<06:54:59.660> straight<06:55:00.660> through 06:55:03.110 --> 06:55:03.120 align:start position:0% 06:55:03.120 --> 06:55:05.448 align:start position:0% or<06:55:03.840> crossover 06:55:05.448 --> 06:55:05.458 align:start position:0% or crossover 06:55:05.458 --> 06:55:07.010 align:start position:0% or crossover and<06:55:05.878> we've<06:55:06.120> looked<06:55:06.420> at<06:55:06.478> that<06:55:06.600> a<06:55:06.780> little<06:55:06.900> bit 06:55:07.010 --> 06:55:07.020 align:start position:0% and we've looked at that a little bit 06:55:07.020 --> 06:55:08.810 align:start position:0% and we've looked at that a little bit more<06:55:07.200> in<06:55:07.320> depth<06:55:07.620> previously 06:55:08.810 --> 06:55:08.820 align:start position:0% more in depth previously 06:55:08.820 --> 06:55:10.670 align:start position:0% more in depth previously and<06:55:09.600> a<06:55:09.900> switch 06:55:10.670 --> 06:55:10.680 align:start position:0% and a switch 06:55:10.680 --> 06:55:14.628 align:start position:0% and a switch or<06:55:11.458> and<06:55:11.820> a<06:55:12.120> router<06:55:12.958> so<06:55:13.320> a<06:55:13.500> network<06:55:13.620> can<06:55:14.100> also 06:55:14.628 --> 06:55:14.638 align:start position:0% or and a router so a network can also 06:55:14.638 --> 06:55:17.510 align:start position:0% or and a router so a network can also contain<06:55:15.058> a<06:55:15.780> combination<06:55:16.320> of<06:55:16.558> these<06:55:16.740> or<06:55:17.040> all<06:55:17.340> of 06:55:17.510 --> 06:55:17.520 align:start position:0% contain a combination of these or all of 06:55:17.520 --> 06:55:19.968 align:start position:0% contain a combination of these or all of them<06:55:18.138> generally<06:55:19.138> so<06:55:19.320> much<06:55:19.500> we're<06:55:19.680> not<06:55:19.860> going 06:55:19.968 --> 06:55:19.978 align:start position:0% them generally so much we're not going 06:55:19.978 --> 06:55:22.788 align:start position:0% them generally so much we're not going to<06:55:20.160> see<06:55:20.280> hubs<06:55:20.820> a<06:55:21.058> lot<06:55:21.180> anymore<06:55:21.478> but<06:55:22.260> they're 06:55:22.788 --> 06:55:22.798 align:start position:0% to see hubs a lot anymore but they're 06:55:22.798 --> 06:55:24.530 align:start position:0% to see hubs a lot anymore but they're still<06:55:22.978> mentioned<06:55:23.400> on<06:55:23.520> the<06:55:23.700> exam 06:55:24.530 --> 06:55:24.540 align:start position:0% still mentioned on the exam 06:55:24.540 --> 06:55:27.288 align:start position:0% still mentioned on the exam so<06:55:25.020> a<06:55:25.440> very<06:55:25.558> simple<06:55:25.860> ethernet<06:55:26.520> Network<06:55:26.760> that 06:55:27.288 --> 06:55:27.298 align:start position:0% so a very simple ethernet Network that 06:55:27.298 --> 06:55:29.930 align:start position:0% so a very simple ethernet Network that involves<06:55:27.600> a<06:55:27.780> hub<06:55:27.900> is<06:55:28.558> called<06:55:28.860> a<06:55:29.340> Hub<06:55:29.520> Network 06:55:29.930 --> 06:55:29.940 align:start position:0% involves a hub is called a Hub Network 06:55:29.940 --> 06:55:32.150 align:start position:0% involves a hub is called a Hub Network Now<06:55:30.718> to<06:55:30.900> create<06:55:31.080> this<06:55:31.260> network<06:55:31.440> all<06:55:31.798> you<06:55:31.978> need 06:55:32.150 --> 06:55:32.160 align:start position:0% Now to create this network all you need 06:55:32.160 --> 06:55:34.490 align:start position:0% Now to create this network all you need is<06:55:32.700> two<06:55:32.878> devices 06:55:34.490 --> 06:55:34.500 align:start position:0% is two devices 06:55:34.500 --> 06:55:35.810 align:start position:0% is two devices a<06:55:34.978> hub 06:55:35.810 --> 06:55:35.820 align:start position:0% a hub 06:55:35.820 --> 06:55:38.150 align:start position:0% a hub and<06:55:36.478> an<06:55:36.600> ethernet<06:55:37.020> cable 06:55:38.150 --> 06:55:38.160 align:start position:0% and an ethernet cable 06:55:38.160 --> 06:55:40.490 align:start position:0% and an ethernet cable this<06:55:38.638> type<06:55:38.878> of<06:55:39.000> network<06:55:39.240> is<06:55:39.660> not<06:55:39.900> capable<06:55:40.260> of 06:55:40.490 --> 06:55:40.500 align:start position:0% this type of network is not capable of 06:55:40.500 --> 06:55:42.650 align:start position:0% this type of network is not capable of reaching<06:55:41.040> the<06:55:41.218> internet<06:55:41.400> and<06:55:42.180> it's<06:55:42.298> typically 06:55:42.650 --> 06:55:42.660 align:start position:0% reaching the internet and it's typically 06:55:42.660 --> 06:55:44.750 align:start position:0% reaching the internet and it's typically only<06:55:42.900> going<06:55:43.138> to<06:55:43.320> be<06:55:43.500> used<06:55:43.680> for<06:55:43.978> file<06:55:44.280> sharing 06:55:44.750 --> 06:55:44.760 align:start position:0% only going to be used for file sharing 06:55:44.760 --> 06:55:46.910 align:start position:0% only going to be used for file sharing or<06:55:44.940> printing<06:55:45.360> and<06:55:46.320> you're<06:55:46.440> not<06:55:46.620> going<06:55:46.740> to<06:55:46.860> want 06:55:46.910 --> 06:55:46.920 align:start position:0% or printing and you're not going to want 06:55:46.920 --> 06:55:48.590 align:start position:0% or printing and you're not going to want to<06:55:47.040> have<06:55:47.100> a<06:55:47.280> lot<06:55:47.400> of<06:55:47.520> devices<06:55:47.820> either<06:55:48.240> because 06:55:48.590 --> 06:55:48.600 align:start position:0% to have a lot of devices either because 06:55:48.600 --> 06:55:51.110 align:start position:0% to have a lot of devices either because it's<06:55:49.020> quickly<06:55:49.378> going<06:55:49.558> to<06:55:49.740> become<06:55:50.160> very<06:55:50.760> slow 06:55:51.110 --> 06:55:51.120 align:start position:0% it's quickly going to become very slow 06:55:51.120 --> 06:55:53.030 align:start position:0% it's quickly going to become very slow due<06:55:51.900> to<06:55:51.958> the<06:55:52.080> fact<06:55:52.260> that<06:55:52.440> hubs<06:55:52.798> as<06:55:52.920> you 06:55:53.030 --> 06:55:53.040 align:start position:0% due to the fact that hubs as you 06:55:53.040 --> 06:55:56.570 align:start position:0% due to the fact that hubs as you remember<06:55:53.218> operate<06:55:54.120> on<06:55:54.360> layer<06:55:55.138> one<06:55:55.320> of<06:55:55.920> the<06:55:56.100> OSI 06:55:56.570 --> 06:55:56.580 align:start position:0% remember operate on layer one of the OSI 06:55:56.580 --> 06:56:00.650 align:start position:0% remember operate on layer one of the OSI model<06:55:56.820> and<06:55:57.420> therefore<06:55:57.718> broadcast<06:55:58.260> every 06:56:00.650 --> 06:56:00.660 align:start position:0% model and therefore broadcast every 06:56:00.660 --> 06:56:05.030 align:start position:0% model and therefore broadcast every um<06:56:01.200> uh<06:56:02.100> input<06:56:02.638> data<06:56:03.000> out<06:56:03.240> to<06:56:03.540> everything<06:56:03.780> else 06:56:05.030 --> 06:56:05.040 align:start position:0% um uh input data out to everything else 06:56:05.040 --> 06:56:07.310 align:start position:0% um uh input data out to everything else now<06:56:05.458> the<06:56:05.638> next<06:56:05.760> type<06:56:05.940> is<06:56:06.180> also<06:56:06.478> very<06:56:06.718> easy<06:56:07.020> to 06:56:07.310 --> 06:56:07.320 align:start position:0% now the next type is also very easy to 06:56:07.320 --> 06:56:09.530 align:start position:0% now the next type is also very easy to implement<06:56:07.558> this<06:56:07.920> is<06:56:08.100> considered<06:56:08.580> a<06:56:09.240> crossover 06:56:09.530 --> 06:56:09.540 align:start position:0% implement this is considered a crossover 06:56:09.540 --> 06:56:13.368 align:start position:0% implement this is considered a crossover Network<06:56:09.900> or<06:56:10.740> a<06:56:11.040> peer 06:56:13.368 --> 06:56:13.378 align:start position:0% Network or a peer 06:56:13.378 --> 06:56:15.830 align:start position:0% Network or a peer to<06:56:13.680> peer<06:56:14.100> Network<06:56:14.340> and<06:56:15.298> the<06:56:15.420> reason<06:56:15.540> is 06:56:15.830 --> 06:56:15.840 align:start position:0% to peer Network and the reason is 06:56:15.840 --> 06:56:19.310 align:start position:0% to peer Network and the reason is because<06:56:16.138> there<06:56:16.740> is<06:56:16.978> no<06:56:17.580> device<06:56:18.420> sitting<06:56:19.200> in 06:56:19.310 --> 06:56:19.320 align:start position:0% because there is no device sitting in 06:56:19.320 --> 06:56:20.330 align:start position:0% because there is no device sitting in the<06:56:19.500> center 06:56:20.330 --> 06:56:20.340 align:start position:0% the center 06:56:20.340 --> 06:56:22.430 align:start position:0% the center a<06:56:20.760> crossover<06:56:21.000> Network<06:56:21.298> only<06:56:21.600> needs<06:56:22.080> the<06:56:22.260> two 06:56:22.430 --> 06:56:22.440 align:start position:0% a crossover Network only needs the two 06:56:22.440 --> 06:56:24.590 align:start position:0% a crossover Network only needs the two devices<06:56:22.680> in<06:56:23.100> the<06:56:23.280> crossover<06:56:23.638> cable<06:56:24.058> to 06:56:24.590 --> 06:56:24.600 align:start position:0% devices in the crossover cable to 06:56:24.600 --> 06:56:25.910 align:start position:0% devices in the crossover cable to connect<06:56:24.718> them<06:56:24.958> and<06:56:25.138> the<06:56:25.260> reason<06:56:25.378> we<06:56:25.620> must<06:56:25.798> use 06:56:25.910 --> 06:56:25.920 align:start position:0% connect them and the reason we must use 06:56:25.920 --> 06:56:27.410 align:start position:0% connect them and the reason we must use a<06:56:26.160> crossover<06:56:26.400> cable<06:56:26.760> is<06:56:26.940> because<06:56:27.180> we're 06:56:27.410 --> 06:56:27.420 align:start position:0% a crossover cable is because we're 06:56:27.420 --> 06:56:29.990 align:start position:0% a crossover cable is because we're switching<06:56:27.900> if<06:56:28.320> you<06:56:28.500> recall<06:56:28.860> the<06:56:29.520> one<06:56:29.760> two 06:56:29.990 --> 06:56:30.000 align:start position:0% switching if you recall the one two 06:56:30.000 --> 06:56:32.390 align:start position:0% switching if you recall the one two three<06:56:30.240> six<06:56:30.600> pins<06:56:30.958> we're<06:56:31.260> switching<06:56:31.740> these 06:56:32.390 --> 06:56:32.400 align:start position:0% three six pins we're switching these 06:56:32.400 --> 06:56:35.390 align:start position:0% three six pins we're switching these pins<06:56:32.700> so<06:56:33.298> that<06:56:33.540> way<06:56:33.780> on<06:56:34.260> one<06:56:34.500> side<06:56:34.680> the<06:56:35.040> data<06:56:35.340> is 06:56:35.390 --> 06:56:35.400 align:start position:0% pins so that way on one side the data is 06:56:35.400 --> 06:56:39.770 align:start position:0% pins so that way on one side the data is sent<06:56:35.580> on<06:56:35.760> the<06:56:35.940> other<06:56:36.000> side<06:56:36.240> it's<06:56:36.718> received 06:56:39.770 --> 06:56:39.780 align:start position:0% 06:56:39.780 --> 06:56:42.350 align:start position:0% of<06:56:40.378> course<06:56:40.558> newer<06:56:41.040> devices<06:56:41.400> might<06:56:42.000> not<06:56:42.180> always 06:56:42.350 --> 06:56:42.360 align:start position:0% of course newer devices might not always 06:56:42.360 --> 06:56:44.270 align:start position:0% of course newer devices might not always need<06:56:42.900> this<06:56:43.260> crossover<06:56:43.620> cable<06:56:44.040> anymore 06:56:44.270 --> 06:56:44.280 align:start position:0% need this crossover cable anymore 06:56:44.280 --> 06:56:47.628 align:start position:0% need this crossover cable anymore because<06:56:45.058> a<06:56:45.478> lot<06:56:45.600> of<06:56:45.780> modern<06:56:46.200> Nicks<06:56:46.920> have<06:56:47.340> Auto 06:56:47.628 --> 06:56:47.638 align:start position:0% because a lot of modern Nicks have Auto 06:56:47.638 --> 06:56:49.310 align:start position:0% because a lot of modern Nicks have Auto switching<06:56:48.180> capabilities<06:56:48.718> which<06:56:49.080> will 06:56:49.310 --> 06:56:49.320 align:start position:0% switching capabilities which will 06:56:49.320 --> 06:56:50.990 align:start position:0% switching capabilities which will automatically<06:56:49.798> determine<06:56:50.280> and<06:56:50.458> switch<06:56:50.700> these 06:56:50.990 --> 06:56:51.000 align:start position:0% automatically determine and switch these 06:56:51.000 --> 06:56:53.750 align:start position:0% automatically determine and switch these pins<06:56:51.240> for<06:56:51.540> you<06:56:52.200> now<06:56:52.860> another<06:56:53.340> ethernet 06:56:53.750 --> 06:56:53.760 align:start position:0% pins for you now another ethernet 06:56:53.760 --> 06:56:56.810 align:start position:0% pins for you now another ethernet network<06:56:54.240> is<06:56:55.020> one<06:56:55.200> that<06:56:55.378> uses<06:56:55.740> a<06:56:55.978> router<06:56:56.400> to 06:56:56.810 --> 06:56:56.820 align:start position:0% network is one that uses a router to 06:56:56.820 --> 06:56:59.330 align:start position:0% network is one that uses a router to connect<06:56:56.940> devices<06:56:57.420> to<06:56:57.840> the<06:56:58.080> outside<06:56:58.320> world<06:56:58.920> or 06:56:59.330 --> 06:56:59.340 align:start position:0% connect devices to the outside world or 06:56:59.340 --> 06:57:01.070 align:start position:0% connect devices to the outside world or to<06:56:59.520> the<06:57:00.180> internet 06:57:01.070 --> 06:57:01.080 align:start position:0% to the internet 06:57:01.080 --> 06:57:04.548 align:start position:0% to the internet and<06:57:01.798> a<06:57:02.458> switch<06:57:02.638> can<06:57:03.240> often<06:57:03.600> be<06:57:03.780> placed<06:57:04.260> in 06:57:04.548 --> 06:57:04.558 align:start position:0% and a switch can often be placed in 06:57:04.558 --> 06:57:06.770 align:start position:0% and a switch can often be placed in between<06:57:04.740> the<06:57:05.160> router<06:57:05.520> which<06:57:06.180> leads<06:57:06.478> out<06:57:06.600> to 06:57:06.770 --> 06:57:06.780 align:start position:0% between the router which leads out to 06:57:06.780 --> 06:57:08.448 align:start position:0% between the router which leads out to the<06:57:06.958> Wan 06:57:08.448 --> 06:57:08.458 align:start position:0% the Wan 06:57:08.458 --> 06:57:12.048 align:start position:0% the Wan in<06:57:09.000> the<06:57:09.180> internal<06:57:09.540> Network<06:57:09.718> or<06:57:10.138> the<06:57:10.680> LAN<06:57:11.400> in 06:57:12.048 --> 06:57:12.058 align:start position:0% in the internal Network or the LAN in 06:57:12.058 --> 06:57:14.208 align:start position:0% in the internal Network or the LAN in order<06:57:12.180> to<06:57:12.478> alleviate<06:57:13.080> Network<06:57:13.440> congestion 06:57:14.208 --> 06:57:14.218 align:start position:0% order to alleviate Network congestion 06:57:14.218 --> 06:57:16.430 align:start position:0% order to alleviate Network congestion and<06:57:14.760> to<06:57:14.940> allow<06:57:15.180> for<06:57:15.360> more<06:57:15.660> devices<06:57:15.958> to<06:57:16.320> be 06:57:16.430 --> 06:57:16.440 align:start position:0% and to allow for more devices to be 06:57:16.440 --> 06:57:17.390 align:start position:0% and to allow for more devices to be added 06:57:17.390 --> 06:57:17.400 align:start position:0% added 06:57:17.400 --> 06:57:19.368 align:start position:0% added now<06:57:17.820> just<06:57:18.000> so<06:57:18.120> we<06:57:18.240> remember<06:57:18.420> a<06:57:19.260> switch 06:57:19.368 --> 06:57:19.378 align:start position:0% now just so we remember a switch 06:57:19.378 --> 06:57:22.730 align:start position:0% now just so we remember a switch operates<06:57:20.120> on<06:57:21.120> Layer<06:57:21.600> Two<06:57:21.780> although<06:57:22.320> there<06:57:22.620> are 06:57:22.730 --> 06:57:22.740 align:start position:0% operates on Layer Two although there are 06:57:22.740 --> 06:57:24.410 align:start position:0% operates on Layer Two although there are switches<06:57:23.160> that<06:57:23.340> do<06:57:23.520> routing<06:57:23.878> and<06:57:24.000> those<06:57:24.180> are 06:57:24.410 --> 06:57:24.420 align:start position:0% switches that do routing and those are 06:57:24.420 --> 06:57:27.650 align:start position:0% switches that do routing and those are called<06:57:24.660> layer<06:57:25.620> 3<06:57:25.798> switches<06:57:26.340> and<06:57:27.298> then<06:57:27.420> the 06:57:27.650 --> 06:57:27.660 align:start position:0% called layer 3 switches and then the 06:57:27.660 --> 06:57:29.990 align:start position:0% called layer 3 switches and then the router<06:57:28.080> as<06:57:28.378> we<06:57:28.558> just<06:57:28.740> mentioned<06:57:29.100> operates<06:57:29.700> on 06:57:29.990 --> 06:57:30.000 align:start position:0% router as we just mentioned operates on 06:57:30.000 --> 06:57:33.170 align:start position:0% router as we just mentioned operates on layer<06:57:30.360> three<06:57:30.540> of<06:57:31.500> the<06:57:31.798> OSI<06:57:32.280> model 06:57:33.170 --> 06:57:33.180 align:start position:0% layer three of the OSI model 06:57:33.180 --> 06:57:35.150 align:start position:0% layer three of the OSI model now<06:57:33.780> another<06:57:34.080> point<06:57:34.378> about<06:57:34.620> ethernet 06:57:35.150 --> 06:57:35.160 align:start position:0% now another point about ethernet 06:57:35.160 --> 06:57:36.708 align:start position:0% now another point about ethernet networks<06:57:35.580> that<06:57:35.760> is<06:57:35.940> important<06:57:36.298> is<06:57:36.540> that 06:57:36.708 --> 06:57:36.718 align:start position:0% networks that is important is that 06:57:36.718 --> 06:57:39.708 align:start position:0% networks that is important is that ethernet<06:57:37.138> uses<06:57:37.638> destination<06:57:38.638> and<06:57:39.240> Source 06:57:39.708 --> 06:57:39.718 align:start position:0% ethernet uses destination and Source 06:57:39.718 --> 06:57:42.830 align:start position:0% ethernet uses destination and Source access<06:57:40.260> points<06:57:40.920> to<06:57:41.160> assist<06:57:41.340> in<06:57:41.878> keeping<06:57:42.298> tabs 06:57:42.830 --> 06:57:42.840 align:start position:0% access points to assist in keeping tabs 06:57:42.840 --> 06:57:44.868 align:start position:0% access points to assist in keeping tabs on<06:57:43.260> all<06:57:43.440> the<06:57:43.558> multiple<06:57:43.860> channels<06:57:44.400> that<06:57:44.700> are 06:57:44.868 --> 06:57:44.878 align:start position:0% on all the multiple channels that are 06:57:44.878 --> 06:57:47.868 align:start position:0% on all the multiple channels that are used<06:57:45.120> in<06:57:45.660> network<06:57:45.840> communications<06:57:46.760> these<06:57:47.760> are 06:57:47.868 --> 06:57:47.878 align:start position:0% used in network communications these are 06:57:47.878 --> 06:57:52.250 align:start position:0% used in network communications these are called<06:57:48.120> sap<06:57:49.020> or<06:57:49.798> service<06:57:50.218> access<06:57:50.760> points<06:57:51.540> and 06:57:52.250 --> 06:57:52.260 align:start position:0% called sap or service access points and 06:57:52.260 --> 06:57:53.990 align:start position:0% called sap or service access points and in<06:57:52.440> the<06:57:52.558> previous<06:57:52.680> modules<06:57:53.280> we<06:57:53.458> discussed<06:57:53.760> how 06:57:53.990 --> 06:57:54.000 align:start position:0% in the previous modules we discussed how 06:57:54.000 --> 06:57:56.150 align:start position:0% in the previous modules we discussed how data<06:57:54.420> flows<06:57:54.780> through<06:57:55.020> these<06:57:55.320> layers<06:57:55.680> in<06:57:55.978> the 06:57:56.150 --> 06:57:56.160 align:start position:0% data flows through these layers in the 06:57:56.160 --> 06:57:58.968 align:start position:0% data flows through these layers in the network<06:57:56.280> models<06:57:56.878> well<06:57:57.540> here<06:57:57.958> these<06:57:58.798> access 06:57:58.968 --> 06:57:58.978 align:start position:0% network models well here these access 06:57:58.978 --> 06:58:02.030 align:start position:0% network models well here these access points<06:57:59.580> are<06:58:00.058> used<06:58:00.298> to<06:58:00.718> map<06:58:00.840> the<06:58:01.200> network<06:58:01.440> layer 06:58:02.030 --> 06:58:02.040 align:start position:0% points are used to map the network layer 06:58:02.040 --> 06:58:05.390 align:start position:0% points are used to map the network layer communication<06:58:02.700> or<06:58:03.360> IP<06:58:03.860> through<06:58:04.860> the<06:58:05.218> physical 06:58:05.390 --> 06:58:05.400 align:start position:0% communication or IP through the physical 06:58:05.400 --> 06:58:08.750 align:start position:0% communication or IP through the physical layer<06:58:06.000> or<06:58:06.420> layer<06:58:06.840> 1.<06:58:07.500> now<06:58:07.920> the<06:58:08.160> access<06:58:08.280> points 06:58:08.750 --> 06:58:08.760 align:start position:0% layer or layer 1. now the access points 06:58:08.760 --> 06:58:11.570 align:start position:0% layer or layer 1. now the access points allow<06:58:09.120> a<06:58:09.600> single<06:58:09.900> physical<06:58:10.200> connection<06:58:10.620> to<06:58:11.458> be 06:58:11.570 --> 06:58:11.580 align:start position:0% allow a single physical connection to be 06:58:11.580 --> 06:58:14.208 align:start position:0% allow a single physical connection to be utilized<06:58:12.180> for<06:58:12.478> many<06:58:12.780> logical<06:58:13.320> connections 06:58:14.208 --> 06:58:14.218 align:start position:0% utilized for many logical connections 06:58:14.218 --> 06:58:17.150 align:start position:0% utilized for many logical connections for<06:58:14.638> tcpip<06:58:15.478> this<06:58:16.378> would<06:58:16.500> be<06:58:16.620> like<06:58:16.798> a<06:58:16.978> Nick 06:58:17.150 --> 06:58:17.160 align:start position:0% for tcpip this would be like a Nick 06:58:17.160 --> 06:58:19.190 align:start position:0% for tcpip this would be like a Nick because<06:58:17.878> these<06:58:18.240> access<06:58:18.360> points<06:58:18.840> are<06:58:18.958> going<06:58:19.080> to 06:58:19.190 --> 06:58:19.200 align:start position:0% because these access points are going to 06:58:19.200 --> 06:58:21.770 align:start position:0% because these access points are going to be<06:58:19.260> on<06:58:19.500> the<06:58:19.680> local<06:58:19.978> side<06:58:20.458> only<06:58:20.940> they're 06:58:21.770 --> 06:58:21.780 align:start position:0% be on the local side only they're 06:58:21.780 --> 06:58:24.890 align:start position:0% be on the local side only they're selected<06:58:22.378> by<06:58:22.860> the<06:58:23.160> server<06:58:23.580> managing<06:58:24.420> those 06:58:24.890 --> 06:58:24.900 align:start position:0% selected by the server managing those 06:58:24.900 --> 06:58:26.090 align:start position:0% selected by the server managing those services 06:58:26.090 --> 06:58:26.100 align:start position:0% services 06:58:26.100 --> 06:58:28.850 align:start position:0% services now<06:58:26.520> to<06:58:26.638> keep<06:58:26.760> what<06:58:26.878> TCP<06:58:27.298> as<06:58:27.718> an<06:58:27.900> example<06:58:28.138> when 06:58:28.850 --> 06:58:28.860 align:start position:0% now to keep what TCP as an example when 06:58:28.860 --> 06:58:30.590 align:start position:0% now to keep what TCP as an example when a<06:58:29.040> user<06:58:29.280> is<06:58:29.458> accessing<06:58:29.878> a<06:58:30.000> website<06:58:30.298> for 06:58:30.590 --> 06:58:30.600 align:start position:0% a user is accessing a website for 06:58:30.600 --> 06:58:31.368 align:start position:0% a user is accessing a website for example 06:58:31.368 --> 06:58:31.378 align:start position:0% example 06:58:31.378 --> 06:58:33.530 align:start position:0% example a<06:58:31.860> connection<06:58:31.978> is<06:58:32.400> made<06:58:32.580> with<06:58:32.820> the<06:58:33.000> web<06:58:33.120> server 06:58:33.530 --> 06:58:33.540 align:start position:0% a connection is made with the web server 06:58:33.540 --> 06:58:36.170 align:start position:0% a connection is made with the web server and<06:58:33.958> the<06:58:34.138> computer<06:58:34.340> downloads<06:58:35.340> that<06:58:35.638> website 06:58:36.170 --> 06:58:36.180 align:start position:0% and the computer downloads that website 06:58:36.180 --> 06:58:38.690 align:start position:0% and the computer downloads that website along<06:58:36.958> with<06:58:37.200> the<06:58:37.320> website<06:58:37.620> are<06:58:37.978> references<06:58:38.458> to 06:58:38.690 --> 06:58:38.700 align:start position:0% along with the website are references to 06:58:38.700 --> 06:58:40.670 align:start position:0% along with the website are references to parts<06:58:38.878> of<06:58:39.120> the<06:58:39.240> page<06:58:39.420> such<06:58:39.718> as<06:58:39.900> files<06:58:40.378> that<06:58:40.558> are 06:58:40.670 --> 06:58:40.680 align:start position:0% parts of the page such as files that are 06:58:40.680 --> 06:58:44.330 align:start position:0% parts of the page such as files that are associated<06:58:41.160> with<06:58:41.400> the<06:58:41.580> web<06:58:41.760> page<06:58:42.320> sound<06:58:43.340> image 06:58:44.330 --> 06:58:44.340 align:start position:0% associated with the web page sound image 06:58:44.340 --> 06:58:47.390 align:start position:0% associated with the web page sound image other<06:58:45.180> things<06:58:45.420> like<06:58:45.780> JavaScript<06:58:46.378> and<06:58:47.160> these 06:58:47.390 --> 06:58:47.400 align:start position:0% other things like JavaScript and these 06:58:47.400 --> 06:58:49.730 align:start position:0% other things like JavaScript and these files<06:58:47.760> are<06:58:47.878> stored<06:58:48.298> on<06:58:48.600> the<06:58:48.718> web<06:58:48.900> server<06:58:49.320> and 06:58:49.730 --> 06:58:49.740 align:start position:0% files are stored on the web server and 06:58:49.740 --> 06:58:51.350 align:start position:0% files are stored on the web server and when<06:58:49.920> the<06:58:49.978> user<06:58:50.218> interacts<06:58:50.638> with<06:58:50.820> the<06:58:51.000> website 06:58:51.350 --> 06:58:51.360 align:start position:0% when the user interacts with the website 06:58:51.360 --> 06:58:53.628 align:start position:0% when the user interacts with the website the<06:58:52.138> access<06:58:52.200> point<06:58:52.620> ensures<06:58:53.160> that<06:58:53.520> the 06:58:53.628 --> 06:58:53.638 align:start position:0% the access point ensures that the 06:58:53.638 --> 06:58:56.090 align:start position:0% the access point ensures that the computer<06:58:53.820> can<06:58:54.240> differentiate<06:58:55.020> between<06:58:55.740> the 06:58:56.090 --> 06:58:56.100 align:start position:0% computer can differentiate between the 06:58:56.100 --> 06:58:58.788 align:start position:0% computer can differentiate between the ethernet<06:58:56.520> frames<06:58:57.000> for<06:58:57.420> the<06:58:57.660> images<06:58:57.780> and<06:58:58.680> those 06:58:58.788 --> 06:58:58.798 align:start position:0% ethernet frames for the images and those 06:58:58.798 --> 06:59:00.650 align:start position:0% ethernet frames for the images and those for<06:58:59.040> sound<06:58:59.218> files<06:58:59.700> and<06:59:00.058> those<06:59:00.240> for<06:59:00.420> other 06:59:00.650 --> 06:59:00.660 align:start position:0% for sound files and those for other 06:59:00.660 --> 06:59:01.610 align:start position:0% for sound files and those for other types 06:59:01.610 --> 06:59:01.620 align:start position:0% types 06:59:01.620 --> 06:59:04.070 align:start position:0% types okay<06:59:02.218> so<06:59:02.760> in<06:59:03.000> a<06:59:03.180> lot<06:59:03.240> of<06:59:03.360> the<06:59:03.478> previous<06:59:03.600> lessons 06:59:04.070 --> 06:59:04.080 align:start position:0% okay so in a lot of the previous lessons 06:59:04.080 --> 06:59:05.868 align:start position:0% okay so in a lot of the previous lessons we've<06:59:04.320> been<06:59:04.500> talking<06:59:04.680> about<06:59:04.978> the<06:59:05.458> methods<06:59:05.760> of 06:59:05.868 --> 06:59:05.878 align:start position:0% we've been talking about the methods of 06:59:05.878 --> 06:59:07.610 align:start position:0% we've been talking about the methods of connecting<06:59:06.240> our<06:59:06.478> devices<06:59:06.780> mostly<06:59:07.320> through 06:59:07.610 --> 06:59:07.620 align:start position:0% connecting our devices mostly through 06:59:07.620 --> 06:59:10.368 align:start position:0% connecting our devices mostly through physical<06:59:07.920> means<06:59:08.458> and<06:59:08.940> we<06:59:09.120> defined<06:59:09.540> that<06:59:10.080> many 06:59:10.368 --> 06:59:10.378 align:start position:0% physical means and we defined that many 06:59:10.378 --> 06:59:12.948 align:start position:0% physical means and we defined that many Technologies<06:59:11.160> are<06:59:11.700> commonly<06:59:12.120> used<06:59:12.420> in<06:59:12.780> both 06:59:12.948 --> 06:59:12.958 align:start position:0% Technologies are commonly used in both 06:59:12.958 --> 06:59:16.190 align:start position:0% Technologies are commonly used in both wired<06:59:13.620> and<06:59:13.798> wireless<06:59:14.040> networks<06:59:15.200> otherwise 06:59:16.190 --> 06:59:16.200 align:start position:0% wired and wireless networks otherwise 06:59:16.200 --> 06:59:18.650 align:start position:0% wired and wireless networks otherwise known<06:59:16.440> as<06:59:16.680> bounded<06:59:17.218> and<06:59:17.638> unbounded<06:59:18.180> networks 06:59:18.650 --> 06:59:18.660 align:start position:0% known as bounded and unbounded networks 06:59:18.660 --> 06:59:19.910 align:start position:0% known as bounded and unbounded networks so<06:59:19.080> here<06:59:19.260> we're<06:59:19.440> going<06:59:19.558> to<06:59:19.620> discuss 06:59:19.910 --> 06:59:19.920 align:start position:0% so here we're going to discuss 06:59:19.920 --> 06:59:22.670 align:start position:0% so here we're going to discuss specifically<06:59:20.458> WLAN<06:59:21.360> or<06:59:21.600> Wireless<06:59:21.900> local<06:59:22.378> area 06:59:22.670 --> 06:59:22.680 align:start position:0% specifically WLAN or Wireless local area 06:59:22.680 --> 06:59:26.150 align:start position:0% specifically WLAN or Wireless local area networks<06:59:23.280> in<06:59:23.580> Greater<06:59:23.940> detail<06:59:24.360> starting<06:59:25.138> with 06:59:26.150 --> 06:59:26.160 align:start position:0% networks in Greater detail starting with 06:59:26.160 --> 06:59:28.368 align:start position:0% networks in Greater detail starting with the<06:59:26.700> architecture 06:59:28.368 --> 06:59:28.378 align:start position:0% the architecture 06:59:28.378 --> 06:59:30.650 align:start position:0% the architecture there<06:59:29.340> are<06:59:29.458> several<06:59:29.760> components<06:59:30.298> that<06:59:30.478> we 06:59:30.650 --> 06:59:30.660 align:start position:0% there are several components that we 06:59:30.660 --> 06:59:32.690 align:start position:0% there are several components that we really<06:59:30.780> need<06:59:31.020> to<06:59:31.138> Define 06:59:32.690 --> 06:59:32.700 align:start position:0% really need to Define 06:59:32.700 --> 06:59:34.910 align:start position:0% really need to Define the<06:59:33.420> first<06:59:33.600> component<06:59:34.080> is<06:59:34.260> what's<06:59:34.500> called<06:59:34.740> an 06:59:34.910 --> 06:59:34.920 align:start position:0% the first component is what's called an 06:59:34.920 --> 06:59:37.968 align:start position:0% the first component is what's called an sta<06:59:35.458> or<06:59:36.240> the<06:59:36.540> station 06:59:37.968 --> 06:59:37.978 align:start position:0% sta or the station 06:59:37.978 --> 06:59:40.968 align:start position:0% sta or the station the<06:59:38.580> wireless<06:59:38.760> sta<06:59:39.600> is<06:59:39.900> any<06:59:40.200> device<06:59:40.440> that<06:59:40.798> has 06:59:40.968 --> 06:59:40.978 align:start position:0% the wireless sta is any device that has 06:59:40.978 --> 06:59:44.208 align:start position:0% the wireless sta is any device that has a<06:59:41.340> network<06:59:41.520> adapter<06:59:42.240> card<06:59:42.540> or<06:59:43.200> Nick<06:59:43.558> that 06:59:44.208 --> 06:59:44.218 align:start position:0% a network adapter card or Nick that 06:59:44.218 --> 06:59:48.230 align:start position:0% a network adapter card or Nick that conforms<06:59:44.878> to<06:59:45.240> the<06:59:45.620> 802.11<06:59:46.620> standard 06:59:48.230 --> 06:59:48.240 align:start position:0% conforms to the 802.11 standard 06:59:48.240 --> 06:59:50.090 align:start position:0% conforms to the 802.11 standard and<06:59:48.540> you<06:59:48.718> remember<06:59:48.840> the<06:59:49.320> specific<06:59:49.620> standard 06:59:50.090 --> 06:59:50.100 align:start position:0% and you remember the specific standard 06:59:50.100 --> 06:59:52.788 align:start position:0% and you remember the specific standard for<06:59:50.340> wireless<06:59:50.520> is<06:59:51.138> 802.11<06:59:52.138> as<06:59:52.440> opposed<06:59:52.740> to 06:59:52.788 --> 06:59:52.798 align:start position:0% for wireless is 802.11 as opposed to 06:59:52.798 --> 06:59:55.548 align:start position:0% for wireless is 802.11 as opposed to 8023<06:59:53.458> which<06:59:53.700> is<06:59:53.820> ethernet<06:59:54.900> now<06:59:55.260> the<06:59:55.440> next 06:59:55.548 --> 06:59:55.558 align:start position:0% 8023 which is ethernet now the next 06:59:55.558 --> 06:59:58.010 align:start position:0% 8023 which is ethernet now the next device<06:59:55.740> is<06:59:56.040> called<06:59:56.280> an<06:59:56.580> AP<06:59:56.820> or<06:59:57.600> an<06:59:57.840> access 06:59:58.010 --> 06:59:58.020 align:start position:0% device is called an AP or an access 06:59:58.020 --> 07:00:00.770 align:start position:0% device is called an AP or an access point<06:59:58.378> look<06:59:58.860> familiar<06:59:59.280> now<06:59:59.940> this<07:00:00.180> is<07:00:00.360> very 07:00:00.770 --> 07:00:00.780 align:start position:0% point look familiar now this is very 07:00:00.780 --> 07:00:02.750 align:start position:0% point look familiar now this is very different<07:00:01.138> from<07:00:01.680> the<07:00:01.860> service<07:00:02.100> access<07:00:02.400> point 07:00:02.750 --> 07:00:02.760 align:start position:0% different from the service access point 07:00:02.760 --> 07:00:05.150 align:start position:0% different from the service access point I<07:00:03.058> just<07:00:03.180> talked<07:00:03.540> about<07:00:03.660> because<07:00:04.320> an<07:00:04.620> AP<07:00:04.798> in 07:00:05.150 --> 07:00:05.160 align:start position:0% I just talked about because an AP in 07:00:05.160 --> 07:00:08.270 align:start position:0% I just talked about because an AP in this<07:00:05.340> sense<07:00:05.580> it<07:00:06.420> is<07:00:06.540> a<07:00:06.780> device<07:00:07.020> or<07:00:07.798> a<07:00:07.920> software 07:00:08.270 --> 07:00:08.280 align:start position:0% this sense it is a device or a software 07:00:08.280 --> 07:00:10.368 align:start position:0% this sense it is a device or a software implementation<07:00:08.940> that<07:00:09.600> allows<07:00:09.958> wireless 07:00:10.368 --> 07:00:10.378 align:start position:0% implementation that allows wireless 07:00:10.378 --> 07:00:12.288 align:start position:0% implementation that allows wireless devices<07:00:10.978> to<07:00:11.340> communicate<07:00:11.760> with<07:00:12.000> each<07:00:12.180> other 07:00:12.288 --> 07:00:12.298 align:start position:0% devices to communicate with each other 07:00:12.298 --> 07:00:15.230 align:start position:0% devices to communicate with each other and<07:00:12.840> to<07:00:13.020> connect<07:00:13.138> to<07:00:13.500> a<07:00:13.680> wired<07:00:13.978> Network<07:00:14.240> an 07:00:15.230 --> 07:00:15.240 align:start position:0% and to connect to a wired Network an 07:00:15.240 --> 07:00:18.468 align:start position:0% and to connect to a wired Network an access<07:00:15.478> pointer<07:00:16.080> AP<07:00:16.638> also<07:00:17.638> sometimes<07:00:18.058> called 07:00:18.468 --> 07:00:18.478 align:start position:0% access pointer AP also sometimes called 07:00:18.478 --> 07:00:21.410 align:start position:0% access pointer AP also sometimes called wireless<07:00:19.020> access<07:00:19.500> point<07:00:20.120> offers<07:00:21.120> wireless 07:00:21.410 --> 07:00:21.420 align:start position:0% wireless access point offers wireless 07:00:21.420 --> 07:00:23.930 align:start position:0% wireless access point offers wireless devices<07:00:22.080> some<07:00:22.680> higher<07:00:23.100> levels<07:00:23.400> of<07:00:23.638> security 07:00:23.930 --> 07:00:23.940 align:start position:0% devices some higher levels of security 07:00:23.940 --> 07:00:27.230 align:start position:0% devices some higher levels of security as<07:00:24.660> well<07:00:24.840> and<07:00:25.440> can<07:00:25.740> act<07:00:26.040> as<07:00:26.218> the<07:00:26.580> bridging 07:00:27.230 --> 07:00:27.240 align:start position:0% as well and can act as the bridging 07:00:27.240 --> 07:00:28.368 align:start position:0% as well and can act as the bridging component 07:00:28.368 --> 07:00:28.378 align:start position:0% component 07:00:28.378 --> 07:00:30.890 align:start position:0% component between<07:00:28.798> the<07:00:29.218> STA 07:00:30.890 --> 07:00:30.900 align:start position:0% between the STA 07:00:30.900 --> 07:00:33.350 align:start position:0% between the STA and<07:00:31.558> the<07:00:31.860> backbone<07:00:32.340> of<07:00:32.638> the<07:00:32.820> network<07:00:32.940> for 07:00:33.350 --> 07:00:33.360 align:start position:0% and the backbone of the network for 07:00:33.360 --> 07:00:34.788 align:start position:0% and the backbone of the network for access 07:00:34.788 --> 07:00:34.798 align:start position:0% access 07:00:34.798 --> 07:00:37.730 align:start position:0% access so<07:00:35.340> the<07:00:35.820> next<07:00:36.058> component<07:00:36.900> that<07:00:37.200> we<07:00:37.320> need<07:00:37.440> to 07:00:37.730 --> 07:00:37.740 align:start position:0% so the next component that we need to 07:00:37.740 --> 07:00:41.930 align:start position:0% so the next component that we need to identify<07:00:38.638> is<07:00:39.540> the<07:00:39.840> WDS<07:00:40.620> or<07:00:41.458> the<07:00:41.700> wireless 07:00:41.930 --> 07:00:41.940 align:start position:0% identify is the WDS or the wireless 07:00:41.940 --> 07:00:45.350 align:start position:0% identify is the WDS or the wireless distribution<07:00:42.840> system<07:00:43.400> this<07:00:44.400> device<07:00:44.638> is<07:00:45.000> the 07:00:45.350 --> 07:00:45.360 align:start position:0% distribution system this device is the 07:00:45.360 --> 07:00:48.410 align:start position:0% distribution system this device is the authority<07:00:46.260> in<07:00:46.500> terms<07:00:46.798> of<07:00:46.920> Access<07:00:47.218> Control<07:00:47.878> to 07:00:48.410 --> 07:00:48.420 align:start position:0% authority in terms of Access Control to 07:00:48.420 --> 07:00:50.930 align:start position:0% authority in terms of Access Control to resources<07:00:49.138> and<07:00:49.740> ensures<07:00:50.100> that<07:00:50.400> devices<07:00:50.638> are 07:00:50.930 --> 07:00:50.940 align:start position:0% resources and ensures that devices are 07:00:50.940 --> 07:00:53.510 align:start position:0% resources and ensures that devices are mobile<07:00:51.180> this<07:00:52.080> allows<07:00:52.500> multiple<07:00:53.160> access 07:00:53.510 --> 07:00:53.520 align:start position:0% mobile this allows multiple access 07:00:53.520 --> 07:00:55.010 align:start position:0% mobile this allows multiple access points 07:00:55.010 --> 07:00:55.020 align:start position:0% points 07:00:55.020 --> 07:00:58.610 align:start position:0% points to<07:00:55.860> be<07:00:56.040> interconnected<07:00:56.820> wirelessly<07:00:57.620> which 07:00:58.610 --> 07:00:58.620 align:start position:0% to be interconnected wirelessly which 07:00:58.620 --> 07:01:01.190 align:start position:0% to be interconnected wirelessly which allows<07:00:59.100> you<07:00:59.218> which<07:00:59.580> allows<07:00:59.878> the<07:01:00.058> aps<07:01:00.600> to<07:01:01.080> be 07:01:01.190 --> 07:01:01.200 align:start position:0% allows you which allows the aps to be 07:01:01.200 --> 07:01:03.468 align:start position:0% allows you which allows the aps to be connected<07:01:01.620> and<07:01:02.160> extend<07:01:02.520> the<07:01:02.700> wireless<07:01:02.940> range 07:01:03.468 --> 07:01:03.478 align:start position:0% connected and extend the wireless range 07:01:03.478 --> 07:01:05.270 align:start position:0% connected and extend the wireless range of<07:01:03.660> the<07:01:03.780> network<07:01:03.958> without<07:01:04.620> having<07:01:04.978> to<07:01:05.160> connect 07:01:05.270 --> 07:01:05.280 align:start position:0% of the network without having to connect 07:01:05.280 --> 07:01:07.670 align:start position:0% of the network without having to connect the<07:01:05.580> wire<07:01:05.760> at<07:01:05.940> the<07:01:06.058> access<07:01:06.240> points<07:01:06.840> directly 07:01:07.670 --> 07:01:07.680 align:start position:0% the wire at the access points directly 07:01:07.680 --> 07:01:10.128 align:start position:0% the wire at the access points directly to<07:01:08.160> the<07:01:08.280> backbone<07:01:08.760> and<07:01:09.240> again<07:01:09.360> the<07:01:09.718> backbone 07:01:10.128 --> 07:01:10.138 align:start position:0% to the backbone and again the backbone 07:01:10.138 --> 07:01:13.128 align:start position:0% to the backbone and again the backbone would<07:01:10.378> be<07:01:10.500> the<07:01:10.860> internet 07:01:13.128 --> 07:01:13.138 align:start position:0% 07:01:13.138 --> 07:01:15.110 align:start position:0% or<07:01:13.740> the<07:01:13.978> rest<07:01:14.100> of<07:01:14.340> the<07:01:14.458> network<07:01:14.638> if<07:01:14.940> we're 07:01:15.110 --> 07:01:15.120 align:start position:0% or the rest of the network if we're 07:01:15.120 --> 07:01:17.390 align:start position:0% or the rest of the network if we're talking<07:01:15.298> about<07:01:15.478> a<07:01:15.780> lan<07:01:16.080> now<07:01:16.620> the<07:01:16.860> system<07:01:16.978> has 07:01:17.390 --> 07:01:17.400 align:start position:0% talking about a lan now the system has 07:01:17.400 --> 07:01:20.930 align:start position:0% talking about a lan now the system has three<07:01:17.760> types<07:01:18.298> of<07:01:18.840> AP<07:01:19.200> stations<07:01:20.458> we<07:01:20.878> have 07:01:20.930 --> 07:01:20.940 align:start position:0% three types of AP stations we have 07:01:20.940 --> 07:01:22.610 align:start position:0% three types of AP stations we have something<07:01:21.120> called<07:01:21.420> a<07:01:21.840> remote<07:01:21.958> base<07:01:22.320> station 07:01:22.610 --> 07:01:22.620 align:start position:0% something called a remote base station 07:01:22.620 --> 07:01:25.310 align:start position:0% something called a remote base station which<07:01:23.400> is<07:01:23.520> the<07:01:23.820> access<07:01:24.000> point<07:01:24.540> that<07:01:24.900> connects 07:01:25.310 --> 07:01:25.320 align:start position:0% which is the access point that connects 07:01:25.320 --> 07:01:27.170 align:start position:0% which is the access point that connects directly<07:01:25.798> to<07:01:26.040> the<07:01:26.218> wireless<07:01:26.400> clients<07:01:27.058> or 07:01:27.170 --> 07:01:27.180 align:start position:0% directly to the wireless clients or 07:01:27.180 --> 07:01:30.468 align:start position:0% directly to the wireless clients or devices<07:01:27.740> a<07:01:28.740> relay<07:01:29.040> based<07:01:29.520> station<07:01:29.700> just 07:01:30.468 --> 07:01:30.478 align:start position:0% devices a relay based station just 07:01:30.478 --> 07:01:32.090 align:start position:0% devices a relay based station just relays<07:01:31.080> or<07:01:31.260> repeats<07:01:31.740> the<07:01:31.978> information 07:01:32.090 --> 07:01:32.100 align:start position:0% relays or repeats the information 07:01:32.100 --> 07:01:35.330 align:start position:0% relays or repeats the information between<07:01:32.700> other<07:01:33.058> stations<07:01:33.540> or<07:01:33.660> devices<07:01:34.040> and<07:01:35.040> a 07:01:35.330 --> 07:01:35.340 align:start position:0% between other stations or devices and a 07:01:35.340 --> 07:01:36.830 align:start position:0% between other stations or devices and a main<07:01:35.520> base<07:01:35.760> station 07:01:36.830 --> 07:01:36.840 align:start position:0% main base station 07:01:36.840 --> 07:01:39.110 align:start position:0% main base station now<07:01:37.440> the<07:01:38.100> last<07:01:38.400> thing<07:01:38.580> I<07:01:38.700> want<07:01:38.820> to<07:01:38.940> talk<07:01:39.000> about 07:01:39.110 --> 07:01:39.120 align:start position:0% now the last thing I want to talk about 07:01:39.120 --> 07:01:41.990 align:start position:0% now the last thing I want to talk about is<07:01:39.478> the<07:01:39.718> main<07:01:39.840> base<07:01:40.138> station<07:01:40.440> which<07:01:41.400> is 07:01:41.990 --> 07:01:42.000 align:start position:0% is the main base station which is 07:01:42.000 --> 07:01:44.930 align:start position:0% is the main base station which is connected<07:01:42.600> to<07:01:42.900> the<07:01:43.200> wired<07:01:43.740> or<07:01:44.040> Ethernet<07:01:44.580> or 07:01:44.930 --> 07:01:44.940 align:start position:0% connected to the wired or Ethernet or 07:01:44.940 --> 07:01:47.150 align:start position:0% connected to the wired or Ethernet or backbone<07:01:45.718> Network 07:01:47.150 --> 07:01:47.160 align:start position:0% backbone Network 07:01:47.160 --> 07:01:49.310 align:start position:0% backbone Network using<07:01:48.000> these<07:01:48.360> components<07:01:48.900> there<07:01:49.138> are<07:01:49.260> a 07:01:49.310 --> 07:01:49.320 align:start position:0% using these components there are a 07:01:49.320 --> 07:01:50.690 align:start position:0% using these components there are a number<07:01:49.440> of<07:01:49.558> different<07:01:49.740> ways<07:01:50.160> we<07:01:50.400> can<07:01:50.520> actually 07:01:50.690 --> 07:01:50.700 align:start position:0% number of different ways we can actually 07:01:50.700 --> 07:01:54.468 align:start position:0% number of different ways we can actually configure<07:01:51.478> a<07:01:52.080> wireless<07:01:52.260> LAN<07:01:52.740> the<07:01:53.520> service<07:01:53.878> set 07:01:54.468 --> 07:01:54.478 align:start position:0% configure a wireless LAN the service set 07:01:54.478 --> 07:01:56.930 align:start position:0% configure a wireless LAN the service set is<07:01:55.260> what<07:01:55.500> defines<07:01:55.978> how<07:01:56.340> your<07:01:56.520> network<07:01:56.638> is 07:01:56.930 --> 07:01:56.940 align:start position:0% is what defines how your network is 07:01:56.940 --> 07:01:59.330 align:start position:0% is what defines how your network is configured<07:01:57.478> now<07:01:58.200> there<07:01:58.500> are<07:01:58.620> three<07:01:58.920> standard 07:01:59.330 --> 07:01:59.340 align:start position:0% configured now there are three standard 07:01:59.340 --> 07:02:02.750 align:start position:0% configured now there are three standard ways<07:01:59.820> that<07:02:00.360> W<07:02:00.600> lands<07:02:01.260> or<07:02:01.680> Wireless<07:02:01.920> Lans<07:02:02.458> can 07:02:02.750 --> 07:02:02.760 align:start position:0% ways that W lands or Wireless Lans can 07:02:02.760 --> 07:02:04.670 align:start position:0% ways that W lands or Wireless Lans can be<07:02:02.878> configured 07:02:04.670 --> 07:02:04.680 align:start position:0% be configured 07:02:04.680 --> 07:02:06.890 align:start position:0% be configured first<07:02:05.218> configuration<07:02:05.878> is<07:02:06.120> what's<07:02:06.298> called<07:02:06.478> a 07:02:06.890 --> 07:02:06.900 align:start position:0% first configuration is what's called a 07:02:06.900 --> 07:02:11.990 align:start position:0% first configuration is what's called a BSS<07:02:07.440> or<07:02:07.978> a<07:02:08.400> basic<07:02:09.000> service<07:02:09.660> set<07:02:10.260> the<07:02:11.100> BSS<07:02:11.580> in 07:02:11.990 --> 07:02:12.000 align:start position:0% BSS or a basic service set the BSS in 07:02:12.000 --> 07:02:14.868 align:start position:0% BSS or a basic service set the BSS in its<07:02:12.298> simplest<07:02:12.600> sense<07:02:12.840> is<07:02:13.558> comprised<07:02:14.100> of<07:02:14.458> an<07:02:14.638> AP 07:02:14.868 --> 07:02:14.878 align:start position:0% its simplest sense is comprised of an AP 07:02:14.878 --> 07:02:18.010 align:start position:0% its simplest sense is comprised of an AP an<07:02:15.478> access<07:02:15.660> point<07:02:16.020> and<07:02:16.500> an<07:02:16.680> sta<07:02:17.160> a<07:02:17.760> station 07:02:18.010 --> 07:02:18.020 align:start position:0% an access point and an sta a station 07:02:18.020 --> 07:02:20.890 align:start position:0% an access point and an sta a station although<07:02:19.020> many<07:02:19.260> stations<07:02:19.860> with<07:02:20.100> a<07:02:20.280> single<07:02:20.580> AP 07:02:20.890 --> 07:02:20.900 align:start position:0% although many stations with a single AP 07:02:20.900 --> 07:02:26.030 align:start position:0% although many stations with a single AP is<07:02:21.900> also<07:02:22.260> considered<07:02:23.280> a<07:02:23.820> BSS<07:02:24.360> so<07:02:25.200> I<07:02:25.558> only<07:02:25.620> need 07:02:26.030 --> 07:02:26.040 align:start position:0% is also considered a BSS so I only need 07:02:26.040 --> 07:02:28.368 align:start position:0% is also considered a BSS so I only need one<07:02:26.458> station<07:02:26.700> but<07:02:27.120> I<07:02:27.240> can<07:02:27.360> have<07:02:27.540> multiple<07:02:28.020> the 07:02:28.368 --> 07:02:28.378 align:start position:0% one station but I can have multiple the 07:02:28.378 --> 07:02:31.968 align:start position:0% one station but I can have multiple the trick<07:02:28.558> here<07:02:28.680> is<07:02:28.860> that<07:02:29.040> I<07:02:29.218> have<07:02:29.340> only<07:02:29.940> one<07:02:30.360> AP 07:02:31.968 --> 07:02:31.978 align:start position:0% trick here is that I have only one AP 07:02:31.978 --> 07:02:36.230 align:start position:0% trick here is that I have only one AP now<07:02:32.520> client<07:02:32.940> nodes<07:02:33.540> like<07:02:34.500> these<07:02:34.920> may<07:02:35.760> not<07:02:35.940> be 07:02:36.230 --> 07:02:36.240 align:start position:0% now client nodes like these may not be 07:02:36.240 --> 07:02:38.868 align:start position:0% now client nodes like these may not be necessarily<07:02:37.218> explicitly<07:02:38.218> aware<07:02:38.520> of<07:02:38.700> each 07:02:38.868 --> 07:02:38.878 align:start position:0% necessarily explicitly aware of each 07:02:38.878 --> 07:02:45.530 align:start position:0% necessarily explicitly aware of each other<07:02:39.138> using<07:02:40.138> a<07:02:40.320> BSS<07:02:40.740> we<07:02:41.040> are<07:02:41.280> easily 07:02:45.530 --> 07:02:45.540 align:start position:0% 07:02:45.540 --> 07:02:48.170 align:start position:0% able<07:02:46.080> to<07:02:46.138> extend<07:02:46.798> our<07:02:47.280> network<07:02:47.458> coverage<07:02:47.940> area 07:02:48.170 --> 07:02:48.180 align:start position:0% able to extend our network coverage area 07:02:48.180 --> 07:02:50.208 align:start position:0% able to extend our network coverage area and<07:02:48.660> the<07:02:48.840> distance<07:02:49.020> between<07:02:49.620> our<07:02:50.040> wireless 07:02:50.208 --> 07:02:50.218 align:start position:0% and the distance between our wireless 07:02:50.218 --> 07:02:52.910 align:start position:0% and the distance between our wireless devices<07:02:50.820> by<07:02:51.780> forwarding 07:02:52.910 --> 07:02:52.920 align:start position:0% devices by forwarding 07:02:52.920 --> 07:02:54.350 align:start position:0% devices by forwarding packets 07:02:54.350 --> 07:02:54.360 align:start position:0% packets 07:02:54.360 --> 07:02:56.868 align:start position:0% packets through<07:02:54.900> a<07:02:55.138> wireless<07:02:55.260> access<07:02:55.740> point 07:02:56.868 --> 07:02:56.878 align:start position:0% through a wireless access point 07:02:56.878 --> 07:02:58.730 align:start position:0% through a wireless access point so<07:02:57.240> that<07:02:57.360> we<07:02:57.478> can<07:02:57.600> gain<07:02:57.780> access<07:02:58.020> to<07:02:58.320> the<07:02:58.440> wired 07:02:58.730 --> 07:02:58.740 align:start position:0% so that we can gain access to the wired 07:02:58.740 --> 07:03:00.590 align:start position:0% so that we can gain access to the wired Network 07:03:00.590 --> 07:03:00.600 align:start position:0% Network 07:03:00.600 --> 07:03:03.230 align:start position:0% Network now<07:03:01.080> wlans<07:03:01.798> can<07:03:02.218> also<07:03:02.520> be<07:03:02.638> configured<07:03:03.120> in 07:03:03.230 --> 07:03:03.240 align:start position:0% now wlans can also be configured in 07:03:03.240 --> 07:03:05.390 align:start position:0% now wlans can also be configured in what's<07:03:03.420> called<07:03:03.660> an<07:03:03.900> ESS<07:03:04.080> or<07:03:04.740> an<07:03:04.920> extended 07:03:05.390 --> 07:03:05.400 align:start position:0% what's called an ESS or an extended 07:03:05.400 --> 07:03:08.868 align:start position:0% what's called an ESS or an extended service<07:03:05.638> set<07:03:06.478> an<07:03:07.080> ESS<07:03:07.320> is<07:03:08.040> comprised<07:03:08.520> of<07:03:08.580> two 07:03:08.868 --> 07:03:08.878 align:start position:0% service set an ESS is comprised of two 07:03:08.878 --> 07:03:12.770 align:start position:0% service set an ESS is comprised of two or<07:03:09.120> more<07:03:09.500> bss's<07:03:10.500> basic<07:03:10.978> service<07:03:11.280> sets<07:03:12.298> and<07:03:12.660> the 07:03:12.770 --> 07:03:12.780 align:start position:0% or more bss's basic service sets and the 07:03:12.780 --> 07:03:14.690 align:start position:0% or more bss's basic service sets and the purpose<07:03:13.020> of<07:03:13.200> an<07:03:13.320> ESS<07:03:13.500> is<07:03:13.978> to<07:03:14.100> allow<07:03:14.400> mobile 07:03:14.690 --> 07:03:14.700 align:start position:0% purpose of an ESS is to allow mobile 07:03:14.700 --> 07:03:17.090 align:start position:0% purpose of an ESS is to allow mobile devices<07:03:15.120> to<07:03:15.478> maintain<07:03:15.900> a<07:03:16.740> constant 07:03:17.090 --> 07:03:17.100 align:start position:0% devices to maintain a constant 07:03:17.100 --> 07:03:18.590 align:start position:0% devices to maintain a constant connection 07:03:18.590 --> 07:03:18.600 align:start position:0% connection 07:03:18.600 --> 07:03:20.990 align:start position:0% connection it's<07:03:18.840> the<07:03:19.080> network<07:03:19.320> while<07:03:19.798> you're<07:03:19.978> roaming<07:03:20.458> so 07:03:20.990 --> 07:03:21.000 align:start position:0% it's the network while you're roaming so 07:03:21.000 --> 07:03:24.048 align:start position:0% it's the network while you're roaming so each<07:03:21.240> BSS<07:03:21.900> in<07:03:22.440> an<07:03:22.620> ESS<07:03:22.798> or<07:03:23.520> an<07:03:23.638> extended 07:03:24.048 --> 07:03:24.058 align:start position:0% each BSS in an ESS or an extended 07:03:24.058 --> 07:03:26.690 align:start position:0% each BSS in an ESS or an extended service<07:03:24.478> set<07:03:24.840> is<07:03:25.440> going<07:03:25.620> to<07:03:25.740> have<07:03:25.978> the<07:03:26.458> same 07:03:26.690 --> 07:03:26.700 align:start position:0% service set is going to have the same 07:03:26.700 --> 07:03:29.510 align:start position:0% service set is going to have the same service<07:03:27.120> set<07:03:27.600> identifier<07:03:28.378> otherwise<07:03:29.218> known 07:03:29.510 --> 07:03:29.520 align:start position:0% service set identifier otherwise known 07:03:29.520 --> 07:03:32.090 align:start position:0% service set identifier otherwise known as<07:03:29.700> an<07:03:30.180> SSID 07:03:32.090 --> 07:03:32.100 align:start position:0% as an SSID 07:03:32.100 --> 07:03:36.288 align:start position:0% as an SSID this<07:03:32.820> makes<07:03:33.180> multiple<07:03:34.138> bsses<07:03:35.100> appear<07:03:35.940> as<07:03:36.120> if 07:03:36.288 --> 07:03:36.298 align:start position:0% this makes multiple bsses appear as if 07:03:36.298 --> 07:03:37.850 align:start position:0% this makes multiple bsses appear as if they're<07:03:36.478> only<07:03:36.718> one 07:03:37.850 --> 07:03:37.860 align:start position:0% they're only one 07:03:37.860 --> 07:03:40.430 align:start position:0% they're only one so<07:03:38.400> as<07:03:38.700> an<07:03:38.878> example<07:03:39.298> if<07:03:39.840> you<07:03:39.900> think<07:03:40.020> about<07:03:40.138> when 07:03:40.430 --> 07:03:40.440 align:start position:0% so as an example if you think about when 07:03:40.440 --> 07:03:42.770 align:start position:0% so as an example if you think about when you<07:03:40.558> walk<07:03:40.740> through<07:03:40.978> an<07:03:41.218> airport<07:03:41.478> pretty<07:03:42.478> much 07:03:42.770 --> 07:03:42.780 align:start position:0% you walk through an airport pretty much 07:03:42.780 --> 07:03:45.468 align:start position:0% you walk through an airport pretty much wherever<07:03:43.620> you<07:03:43.920> sit<07:03:44.160> we<07:03:44.638> have<07:03:44.820> a<07:03:45.120> decently 07:03:45.468 --> 07:03:45.478 align:start position:0% wherever you sit we have a decently 07:03:45.478 --> 07:03:48.170 align:start position:0% wherever you sit we have a decently strong<07:03:45.840> Wireless<07:03:46.260> signal<07:03:46.940> theoretically<07:03:47.940> of 07:03:48.170 --> 07:03:48.180 align:start position:0% strong Wireless signal theoretically of 07:03:48.180 --> 07:03:50.570 align:start position:0% strong Wireless signal theoretically of course<07:03:48.360> so<07:03:49.080> thinking<07:03:49.440> about<07:03:49.620> what's<07:03:50.160> that 07:03:50.570 --> 07:03:50.580 align:start position:0% course so thinking about what's that 07:03:50.580 --> 07:03:52.430 align:start position:0% course so thinking about what's that signal<07:03:51.000> they<07:03:51.240> wouldn't<07:03:51.420> be<07:03:51.660> easy<07:03:51.840> for<07:03:52.200> a 07:03:52.430 --> 07:03:52.440 align:start position:0% signal they wouldn't be easy for a 07:03:52.440 --> 07:03:54.708 align:start position:0% signal they wouldn't be easy for a single<07:03:52.740> access<07:03:52.920> point<07:03:53.340> to<07:03:53.820> provide<07:03:54.120> you<07:03:54.298> a 07:03:54.708 --> 07:03:54.718 align:start position:0% single access point to provide you a 07:03:54.718 --> 07:03:56.628 align:start position:0% single access point to provide you a signal<07:03:55.440> that's<07:03:55.620> that<07:03:55.860> strong<07:03:56.100> for<07:03:56.340> that<07:03:56.458> much 07:03:56.628 --> 07:03:56.638 align:start position:0% signal that's that strong for that much 07:03:56.638 --> 07:03:58.670 align:start position:0% signal that's that strong for that much space<07:03:56.940> in<07:03:57.600> fact<07:03:57.780> it's<07:03:58.080> pretty<07:03:58.558> much 07:03:58.670 --> 07:03:58.680 align:start position:0% space in fact it's pretty much 07:03:58.680 --> 07:04:01.310 align:start position:0% space in fact it's pretty much impossible<07:03:59.218> so<07:04:00.000> instead<07:04:00.360> there<07:04:00.958> are<07:04:01.080> many 07:04:01.310 --> 07:04:01.320 align:start position:0% impossible so instead there are many 07:04:01.320 --> 07:04:04.310 align:start position:0% impossible so instead there are many access<07:04:01.798> points<07:04:02.400> APS<07:04:03.058> arrange<07:04:03.600> strategically 07:04:04.310 --> 07:04:04.320 align:start position:0% access points APS arrange strategically 07:04:04.320 --> 07:04:06.890 align:start position:0% access points APS arrange strategically to<07:04:05.040> allow<07:04:05.340> full<07:04:05.638> coverage<07:04:06.058> throughout<07:04:06.718> the 07:04:06.890 --> 07:04:06.900 align:start position:0% to allow full coverage throughout the 07:04:06.900 --> 07:04:09.770 align:start position:0% to allow full coverage throughout the airport<07:04:07.080> and<07:04:07.920> combined<07:04:08.520> they<07:04:08.820> make<07:04:09.058> up<07:04:09.240> this 07:04:09.770 --> 07:04:09.780 align:start position:0% airport and combined they make up this 07:04:09.780 --> 07:04:12.468 align:start position:0% airport and combined they make up this ESS<07:04:10.080> or<07:04:10.620> extended<07:04:11.100> service<07:04:11.340> set<07:04:11.638> that's<07:04:12.298> why 07:04:12.468 --> 07:04:12.478 align:start position:0% ESS or extended service set that's why 07:04:12.478 --> 07:04:14.090 align:start position:0% ESS or extended service set that's why we<07:04:12.660> see<07:04:12.780> the<07:04:12.958> same<07:04:13.080> network<07:04:13.378> name<07:04:13.680> no<07:04:13.978> matter 07:04:14.090 --> 07:04:14.100 align:start position:0% we see the same network name no matter 07:04:14.100 --> 07:04:16.250 align:start position:0% we see the same network name no matter where<07:04:14.400> you<07:04:14.580> are<07:04:14.760> within<07:04:15.240> that<07:04:15.478> Network<07:04:15.718> range 07:04:16.250 --> 07:04:16.260 align:start position:0% where you are within that Network range 07:04:16.260 --> 07:04:19.788 align:start position:0% where you are within that Network range now<07:04:16.798> the<07:04:16.920> BSS<07:04:17.340> can<07:04:17.820> either<07:04:18.058> operate<07:04:18.840> on<07:04:19.620> the 07:04:19.788 --> 07:04:19.798 align:start position:0% now the BSS can either operate on the 07:04:19.798 --> 07:04:22.548 align:start position:0% now the BSS can either operate on the same<07:04:19.978> channel<07:04:20.218> or<07:04:21.058> on<07:04:21.420> separate<07:04:21.958> channels 07:04:22.548 --> 07:04:22.558 align:start position:0% same channel or on separate channels 07:04:22.558 --> 07:04:24.948 align:start position:0% same channel or on separate channels which<07:04:23.280> effectively<07:04:23.820> increases<07:04:24.660> the 07:04:24.948 --> 07:04:24.958 align:start position:0% which effectively increases the 07:04:24.958 --> 07:04:26.750 align:start position:0% which effectively increases the throughput<07:04:25.320> by<07:04:25.798> having<07:04:25.978> separate<07:04:26.400> channels 07:04:26.750 --> 07:04:26.760 align:start position:0% throughput by having separate channels 07:04:26.760 --> 07:04:28.610 align:start position:0% throughput by having separate channels that<07:04:27.000> they're<07:04:27.298> not<07:04:27.660> going<07:04:27.840> to<07:04:27.958> overlap<07:04:28.378> on 07:04:28.610 --> 07:04:28.620 align:start position:0% that they're not going to overlap on 07:04:28.620 --> 07:04:32.030 align:start position:0% that they're not going to overlap on finally<07:04:29.340> we<07:04:29.700> have<07:04:29.820> What's<07:04:30.058> called<07:04:30.298> the<07:04:31.040> ibss 07:04:32.030 --> 07:04:32.040 align:start position:0% finally we have What's called the ibss 07:04:32.040 --> 07:04:35.208 align:start position:0% finally we have What's called the ibss this<07:04:32.760> is<07:04:32.878> an<07:04:33.240> independent<07:04:33.900> basic<07:04:34.558> service<07:04:34.860> set 07:04:35.208 --> 07:04:35.218 align:start position:0% this is an independent basic service set 07:04:35.218 --> 07:04:37.730 align:start position:0% this is an independent basic service set and<07:04:36.000> ibss<07:04:36.660> is<07:04:36.900> created<07:04:37.200> when<07:04:37.378> there<07:04:37.558> is<07:04:37.680> a 07:04:37.730 --> 07:04:37.740 align:start position:0% and ibss is created when there is a 07:04:37.740 --> 07:04:40.310 align:start position:0% and ibss is created when there is a isn't<07:04:38.280> a<07:04:38.520> controlling<07:04:39.000> access<07:04:39.240> point<07:04:39.718> but 07:04:40.310 --> 07:04:40.320 align:start position:0% isn't a controlling access point but 07:04:40.320 --> 07:04:42.830 align:start position:0% isn't a controlling access point but instead<07:04:40.680> there's<07:04:41.160> what<07:04:41.340> we<07:04:41.520> call<07:04:41.700> an<07:04:42.058> ad<07:04:42.478> hoc 07:04:42.830 --> 07:04:42.840 align:start position:0% instead there's what we call an ad hoc 07:04:42.840 --> 07:04:46.128 align:start position:0% instead there's what we call an ad hoc network<07:04:43.558> and<07:04:44.100> as<07:04:44.280> the<07:04:44.458> name<07:04:44.638> implies 07:04:46.128 --> 07:04:46.138 align:start position:0% network and as the name implies 07:04:46.138 --> 07:04:49.610 align:start position:0% network and as the name implies this<07:04:46.620> means<07:04:46.920> that<07:04:47.280> uh<07:04:48.240> this<07:04:48.718> is<07:04:48.840> a<07:04:49.080> makeshift 07:04:49.610 --> 07:04:49.620 align:start position:0% this means that uh this is a makeshift 07:04:49.620 --> 07:04:52.670 align:start position:0% this means that uh this is a makeshift or<07:04:49.860> an<07:04:50.040> improvised<07:04:50.760> in<07:04:50.878> technical<07:04:51.240> terms<07:04:51.780> uh 07:04:52.670 --> 07:04:52.680 align:start position:0% or an improvised in technical terms uh 07:04:52.680 --> 07:04:55.310 align:start position:0% or an improvised in technical terms uh wireless<07:04:53.340> network<07:04:53.878> that<07:04:54.478> combines<07:04:54.958> Network 07:04:55.310 --> 07:04:55.320 align:start position:0% wireless network that combines Network 07:04:55.320 --> 07:04:57.530 align:start position:0% wireless network that combines Network elements<07:04:55.920> to<07:04:56.160> make<07:04:56.280> a<07:04:56.458> network<07:04:56.580> with<07:04:57.058> minimal 07:04:57.530 --> 07:04:57.540 align:start position:0% elements to make a network with minimal 07:04:57.540 --> 07:04:59.750 align:start position:0% elements to make a network with minimal planning<07:04:58.020> where<07:04:58.680> all<07:04:58.920> the<07:04:59.040> devices<07:04:59.280> on<07:04:59.638> the 07:04:59.750 --> 07:04:59.760 align:start position:0% planning where all the devices on the 07:04:59.760 --> 07:05:02.690 align:start position:0% planning where all the devices on the network<07:04:59.878> are<07:05:00.478> essentially<07:05:01.020> equal<07:05:01.378> in<07:05:01.680> status 07:05:02.690 --> 07:05:02.700 align:start position:0% network are essentially equal in status 07:05:02.700 --> 07:05:06.590 align:start position:0% network are essentially equal in status and<07:05:03.240> are<07:05:03.420> free<07:05:03.780> to<07:05:04.558> talk<07:05:05.400> with<07:05:05.940> any<07:05:06.120> other<07:05:06.360> ad 07:05:06.590 --> 07:05:06.600 align:start position:0% and are free to talk with any other ad 07:05:06.600 --> 07:05:09.048 align:start position:0% and are free to talk with any other ad hoc<07:05:06.780> devices<07:05:07.200> that<07:05:07.558> are<07:05:07.680> in<07:05:07.860> range<07:05:08.218> this<07:05:08.878> ad 07:05:09.048 --> 07:05:09.058 align:start position:0% hoc devices that are in range this ad 07:05:09.058 --> 07:05:10.910 align:start position:0% hoc devices that are in range this ad hoc<07:05:09.240> configuration<07:05:09.900> which<07:05:10.260> is<07:05:10.440> also<07:05:10.740> called 07:05:10.910 --> 07:05:10.920 align:start position:0% hoc configuration which is also called 07:05:10.920 --> 07:05:15.708 align:start position:0% hoc configuration which is also called by<07:05:11.218> the<07:05:11.340> way<07:05:11.458> a<07:05:12.120> peer-to-peer<07:05:12.840> configuration 07:05:15.708 --> 07:05:15.718 align:start position:0% 07:05:15.718 --> 07:05:19.010 align:start position:0% is<07:05:16.378> where<07:05:16.680> stas<07:05:17.400> are<07:05:17.940> performing<07:05:18.420> their<07:05:18.840> own 07:05:19.010 --> 07:05:19.020 align:start position:0% is where stas are performing their own 07:05:19.020 --> 07:05:22.310 align:start position:0% is where stas are performing their own AP<07:05:19.620> functions<07:05:20.400> as<07:05:21.058> well<07:05:21.240> as<07:05:21.420> their<07:05:21.718> own<07:05:21.900> client 07:05:22.310 --> 07:05:22.320 align:start position:0% AP functions as well as their own client 07:05:22.320 --> 07:05:24.890 align:start position:0% AP functions as well as their own client operations<07:05:23.180> independent<07:05:24.180> of<07:05:24.360> any<07:05:24.540> sort<07:05:24.780> of 07:05:24.890 --> 07:05:24.900 align:start position:0% operations independent of any sort of 07:05:24.900 --> 07:05:26.390 align:start position:0% operations independent of any sort of central<07:05:25.080> device 07:05:26.390 --> 07:05:26.400 align:start position:0% central device 07:05:26.400 --> 07:05:28.850 align:start position:0% central device so<07:05:27.000> if<07:05:27.360> you've<07:05:27.600> ever<07:05:27.780> connected<07:05:28.440> two 07:05:28.850 --> 07:05:28.860 align:start position:0% so if you've ever connected two 07:05:28.860 --> 07:05:30.708 align:start position:0% so if you've ever connected two computers<07:05:29.280> directly<07:05:29.700> together<07:05:29.878> in<07:05:30.298> order<07:05:30.478> to 07:05:30.708 --> 07:05:30.718 align:start position:0% computers directly together in order to 07:05:30.718 --> 07:05:31.670 align:start position:0% computers directly together in order to say 07:05:31.670 --> 07:05:31.680 align:start position:0% say 07:05:31.680 --> 07:05:33.830 align:start position:0% say transfer<07:05:32.340> files<07:05:32.820> or<07:05:33.298> perhaps<07:05:33.600> you've 07:05:33.830 --> 07:05:33.840 align:start position:0% transfer files or perhaps you've 07:05:33.840 --> 07:05:36.650 align:start position:0% transfer files or perhaps you've connected<07:05:34.260> your<07:05:34.878> smartphone<07:05:35.878> directly<07:05:36.420> to 07:05:36.650 --> 07:05:36.660 align:start position:0% connected your smartphone directly to 07:05:36.660 --> 07:05:38.570 align:start position:0% connected your smartphone directly to your<07:05:36.840> computer<07:05:37.020> in<07:05:37.440> order<07:05:37.558> to<07:05:37.798> transfer<07:05:38.160> files 07:05:38.570 --> 07:05:38.580 align:start position:0% your computer in order to transfer files 07:05:38.580 --> 07:05:40.250 align:start position:0% your computer in order to transfer files without<07:05:38.878> the<07:05:39.180> use<07:05:39.360> of<07:05:39.540> an<07:05:39.718> access<07:05:39.840> point 07:05:40.250 --> 07:05:40.260 align:start position:0% without the use of an access point 07:05:40.260 --> 07:05:43.310 align:start position:0% without the use of an access point you're<07:05:40.798> using<07:05:41.040> what's<07:05:41.218> called<07:05:41.458> an<07:05:41.760> ibss<07:05:42.660> or<07:05:43.138> an 07:05:43.310 --> 07:05:43.320 align:start position:0% you're using what's called an ibss or an 07:05:43.320 --> 07:05:46.910 align:start position:0% you're using what's called an ibss or an ad<07:05:43.558> hoc<07:05:43.740> wireless<07:05:44.160> network<07:05:44.780> many<07:05:45.780> aspects<07:05:46.500> of 07:05:46.910 --> 07:05:46.920 align:start position:0% ad hoc wireless network many aspects of 07:05:46.920 --> 07:05:49.250 align:start position:0% ad hoc wireless network many aspects of antennas<07:05:47.760> and<07:05:48.120> their<07:05:48.360> characteristics<07:05:48.958> that 07:05:49.250 --> 07:05:49.260 align:start position:0% antennas and their characteristics that 07:05:49.260 --> 07:05:50.810 align:start position:0% antennas and their characteristics that are<07:05:49.440> a<07:05:49.558> little<07:05:49.620> outside<07:05:49.920> of<07:05:50.218> the<07:05:50.340> scope<07:05:50.520> the 07:05:50.810 --> 07:05:50.820 align:start position:0% are a little outside of the scope the 07:05:50.820 --> 07:05:52.850 align:start position:0% are a little outside of the scope the network<07:05:51.000> plus<07:05:51.240> exam<07:05:51.660> but<07:05:52.320> there<07:05:52.500> are<07:05:52.620> still<07:05:52.680> a 07:05:52.850 --> 07:05:52.860 align:start position:0% network plus exam but there are still a 07:05:52.860 --> 07:05:54.830 align:start position:0% network plus exam but there are still a few<07:05:52.978> Basics<07:05:53.458> that<07:05:53.760> are<07:05:53.878> important 07:05:54.830 --> 07:05:54.840 align:start position:0% few Basics that are important 07:05:54.840 --> 07:05:57.530 align:start position:0% few Basics that are important the<07:05:55.440> first<07:05:55.620> of<07:05:55.798> which<07:05:55.920> is<07:05:56.100> to<07:05:56.340> Define<07:05:56.458> what<07:05:57.360> an 07:05:57.530 --> 07:05:57.540 align:start position:0% the first of which is to Define what an 07:05:57.540 --> 07:06:00.048 align:start position:0% the first of which is to Define what an antenna<07:05:58.020> actually<07:05:58.320> is<07:05:58.740> and<07:05:59.160> how<07:05:59.400> it<07:05:59.580> functions 07:06:00.048 --> 07:06:00.058 align:start position:0% antenna actually is and how it functions 07:06:00.058 --> 07:06:01.850 align:start position:0% antenna actually is and how it functions on<07:06:00.478> a<07:06:00.600> fundamental<07:06:01.080> level 07:06:01.850 --> 07:06:01.860 align:start position:0% on a fundamental level 07:06:01.860 --> 07:06:04.670 align:start position:0% on a fundamental level so<07:06:02.218> an<07:06:02.400> antenna<07:06:02.820> is<07:06:03.058> a<07:06:03.240> physical<07:06:03.360> device<07:06:03.840> that 07:06:04.670 --> 07:06:04.680 align:start position:0% so an antenna is a physical device that 07:06:04.680 --> 07:06:06.850 align:start position:0% so an antenna is a physical device that are<07:06:04.860> transmits<07:06:05.638> or<07:06:06.058> receives 07:06:06.850 --> 07:06:06.860 align:start position:0% are transmits or receives 07:06:06.860 --> 07:06:08.930 align:start position:0% are transmits or receives electromagnetic<07:06:07.860> waves<07:06:08.218> and<07:06:08.400> then<07:06:08.520> converts 07:06:08.930 --> 07:06:08.940 align:start position:0% electromagnetic waves and then converts 07:06:08.940 --> 07:06:11.990 align:start position:0% electromagnetic waves and then converts those<07:06:09.180> waves<07:06:09.718> to<07:06:10.440> and<07:06:10.680> from<07:06:10.920> high<07:06:11.520> frequency 07:06:11.990 --> 07:06:12.000 align:start position:0% those waves to and from high frequency 07:06:12.000 --> 07:06:14.288 align:start position:0% those waves to and from high frequency signal<07:06:12.540> now<07:06:13.260> the<07:06:13.440> antenna's<07:06:14.100> physical 07:06:14.288 --> 07:06:14.298 align:start position:0% signal now the antenna's physical 07:06:14.298 --> 07:06:16.548 align:start position:0% signal now the antenna's physical characteristics<07:06:15.298> and<07:06:15.540> dimensions<07:06:16.020> are<07:06:16.440> going 07:06:16.548 --> 07:06:16.558 align:start position:0% characteristics and dimensions are going 07:06:16.558 --> 07:06:18.650 align:start position:0% characteristics and dimensions are going to<07:06:16.740> dictate<07:06:17.100> these<07:06:17.520> frequencies<07:06:18.000> that<07:06:18.360> it<07:06:18.478> can 07:06:18.650 --> 07:06:18.660 align:start position:0% to dictate these frequencies that it can 07:06:18.660 --> 07:06:21.650 align:start position:0% to dictate these frequencies that it can transmit<07:06:19.260> or<07:06:19.860> receive<07:06:20.218> and<07:06:21.058> depending<07:06:21.360> on<07:06:21.478> the 07:06:21.650 --> 07:06:21.660 align:start position:0% transmit or receive and depending on the 07:06:21.660 --> 07:06:23.330 align:start position:0% transmit or receive and depending on the purpose<07:06:21.900> of<07:06:22.138> the<07:06:22.320> antenna 07:06:23.330 --> 07:06:23.340 align:start position:0% purpose of the antenna 07:06:23.340 --> 07:06:25.490 align:start position:0% purpose of the antenna there<07:06:24.000> are<07:06:24.180> different<07:06:24.420> types<07:06:24.958> that<07:06:25.200> can<07:06:25.320> be 07:06:25.490 --> 07:06:25.500 align:start position:0% there are different types that can be 07:06:25.500 --> 07:06:28.128 align:start position:0% there are different types that can be used<07:06:25.740> for<07:06:26.580> instance<07:06:26.760> the<07:06:27.120> radiation<07:06:27.540> pattern 07:06:28.128 --> 07:06:28.138 align:start position:0% used for instance the radiation pattern 07:06:28.138 --> 07:06:30.110 align:start position:0% used for instance the radiation pattern is<07:06:28.620> different<07:06:28.798> on<07:06:29.218> some<07:06:29.458> antennas<07:06:29.940> versus 07:06:30.110 --> 07:06:30.120 align:start position:0% is different on some antennas versus 07:06:30.120 --> 07:06:31.250 align:start position:0% is different on some antennas versus others 07:06:31.250 --> 07:06:31.260 align:start position:0% others 07:06:31.260 --> 07:06:32.750 align:start position:0% others now<07:06:31.740> another<07:06:31.860> term<07:06:32.160> we<07:06:32.340> really<07:06:32.520> need<07:06:32.700> to 07:06:32.750 --> 07:06:32.760 align:start position:0% now another term we really need to 07:06:32.760 --> 07:06:34.670 align:start position:0% now another term we really need to understand<07:06:32.940> is<07:06:33.298> the<07:06:33.478> term<07:06:33.600> gain<07:06:34.138> which 07:06:34.670 --> 07:06:34.680 align:start position:0% understand is the term gain which 07:06:34.680 --> 07:06:37.490 align:start position:0% understand is the term gain which describes<07:06:35.160> the<07:06:35.520> intensity<07:06:36.058> of<07:06:36.298> an<07:06:36.478> antenna<07:06:36.900> in 07:06:37.490 --> 07:06:37.500 align:start position:0% describes the intensity of an antenna in 07:06:37.500 --> 07:06:40.448 align:start position:0% describes the intensity of an antenna in a<07:06:37.620> specific<07:06:37.920> Direction<07:06:38.718> related<07:06:39.718> to<07:06:40.080> the 07:06:40.448 --> 07:06:40.458 align:start position:0% a specific Direction related to the 07:06:40.458 --> 07:06:43.490 align:start position:0% a specific Direction related to the hypothetical<07:06:41.458> intensity<07:06:42.360> of<07:06:43.020> a<07:06:43.200> given 07:06:43.490 --> 07:06:43.500 align:start position:0% hypothetical intensity of a given 07:06:43.500 --> 07:06:46.010 align:start position:0% hypothetical intensity of a given standard<07:06:43.860> which<07:06:44.160> is<07:06:44.280> the<07:06:44.520> ideal<07:06:45.478> in<07:06:45.900> other 07:06:46.010 --> 07:06:46.020 align:start position:0% standard which is the ideal in other 07:06:46.020 --> 07:06:51.708 align:start position:0% standard which is the ideal in other words<07:06:46.200> we<07:06:46.920> always<07:06:47.040> have<07:06:47.400> a<07:06:47.580> hypothetical 07:06:51.708 --> 07:06:51.718 align:start position:0% 07:06:51.718 --> 07:06:55.128 align:start position:0% versus 07:06:55.128 --> 07:06:55.138 align:start position:0% 07:06:55.138 --> 07:06:57.530 align:start position:0% the<07:06:55.620> reality 07:06:57.530 --> 07:06:57.540 align:start position:0% the reality 07:06:57.540 --> 07:06:59.330 align:start position:0% the reality now<07:06:57.900> this<07:06:58.020> is<07:06:58.138> achieved<07:06:58.558> by<07:06:58.740> focusing<07:06:59.160> on 07:06:59.330 --> 07:06:59.340 align:start position:0% now this is achieved by focusing on 07:06:59.340 --> 07:07:01.128 align:start position:0% now this is achieved by focusing on What's<07:06:59.520> called<07:06:59.820> the<07:07:00.120> RF<07:07:00.540> or<07:07:00.840> the<07:07:00.958> radio 07:07:01.128 --> 07:07:01.138 align:start position:0% What's called the RF or the radio 07:07:01.138 --> 07:07:02.690 align:start position:0% What's called the RF or the radio frequency 07:07:02.690 --> 07:07:02.700 align:start position:0% frequency 07:07:02.700 --> 07:07:05.090 align:start position:0% frequency in<07:07:03.240> a<07:07:03.478> more<07:07:03.600> manageable<07:07:04.138> or<07:07:04.500> concentrated 07:07:05.090 --> 07:07:05.100 align:start position:0% in a more manageable or concentrated 07:07:05.100 --> 07:07:08.208 align:start position:0% in a more manageable or concentrated plane<07:07:05.638> this<07:07:06.058> is<07:07:06.180> what<07:07:06.360> we<07:07:06.540> see<07:07:06.718> as<07:07:06.900> strength<07:07:07.740> on 07:07:08.208 --> 07:07:08.218 align:start position:0% plane this is what we see as strength on 07:07:08.218 --> 07:07:10.490 align:start position:0% plane this is what we see as strength on your<07:07:08.580> computer<07:07:09.000> right<07:07:09.660> if<07:07:09.900> you've<07:07:10.080> seen<07:07:10.260> this 07:07:10.490 --> 07:07:10.500 align:start position:0% your computer right if you've seen this 07:07:10.500 --> 07:07:12.890 align:start position:0% your computer right if you've seen this thing<07:07:10.620> and<07:07:10.798> you<07:07:10.978> have<07:07:11.160> different 07:07:12.890 --> 07:07:12.900 align:start position:0% thing and you have different 07:07:12.900 --> 07:07:15.110 align:start position:0% thing and you have different number<07:07:13.378> of<07:07:13.620> bars<07:07:14.100> that's<07:07:14.580> what<07:07:14.760> we're<07:07:14.940> really 07:07:15.110 --> 07:07:15.120 align:start position:0% number of bars that's what we're really 07:07:15.120 --> 07:07:17.270 align:start position:0% number of bars that's what we're really talking<07:07:15.360> about<07:07:15.540> here<07:07:15.840> is<07:07:16.138> the<07:07:16.320> gain 07:07:17.270 --> 07:07:17.280 align:start position:0% talking about here is the gain 07:07:17.280 --> 07:07:19.788 align:start position:0% talking about here is the gain in<07:07:17.878> most<07:07:18.000> cases<07:07:18.360> we<07:07:18.718> want<07:07:18.840> more<07:07:19.138> gain<07:07:19.378> which<07:07:19.680> is 07:07:19.788 --> 07:07:19.798 align:start position:0% in most cases we want more gain which is 07:07:19.798 --> 07:07:21.770 align:start position:0% in most cases we want more gain which is better<07:07:20.040> but<07:07:20.700> there<07:07:20.940> are<07:07:21.120> certain<07:07:21.360> legal 07:07:21.770 --> 07:07:21.780 align:start position:0% better but there are certain legal 07:07:21.780 --> 07:07:23.810 align:start position:0% better but there are certain legal limits<07:07:22.138> and<07:07:22.260> adding<07:07:22.620> power<07:07:22.860> can<07:07:23.400> potentially 07:07:23.810 --> 07:07:23.820 align:start position:0% limits and adding power can potentially 07:07:23.820 --> 07:07:26.750 align:start position:0% limits and adding power can potentially have<07:07:24.180> some<07:07:24.478> negative<07:07:24.718> ramifications<07:07:25.440> so<07:07:26.400> gain 07:07:26.750 --> 07:07:26.760 align:start position:0% have some negative ramifications so gain 07:07:26.760 --> 07:07:28.968 align:start position:0% have some negative ramifications so gain can<07:07:27.180> also<07:07:27.478> come<07:07:27.660> from<07:07:27.840> an<07:07:28.080> external<07:07:28.558> Source 07:07:28.968 --> 07:07:28.978 align:start position:0% can also come from an external Source 07:07:28.978 --> 07:07:32.750 align:start position:0% can also come from an external Source like<07:07:29.340> an<07:07:29.638> amplifier<07:07:30.378> which<07:07:31.378> means<07:07:32.218> that<07:07:32.458> it 07:07:32.750 --> 07:07:32.760 align:start position:0% like an amplifier which means that it 07:07:32.760 --> 07:07:35.510 align:start position:0% like an amplifier which means that it amplifies<07:07:33.360> the<07:07:33.660> signal<07:07:33.958> making<07:07:34.378> it<07:07:34.680> stronger 07:07:35.510 --> 07:07:35.520 align:start position:0% amplifies the signal making it stronger 07:07:35.520 --> 07:07:39.048 align:start position:0% amplifies the signal making it stronger and<07:07:36.478> it's<07:07:36.660> measured<07:07:37.138> in<07:07:37.558> decibels 07:07:39.048 --> 07:07:39.058 align:start position:0% and it's measured in decibels 07:07:39.058 --> 07:07:41.270 align:start position:0% and it's measured in decibels now<07:07:39.600> while<07:07:39.780> this<07:07:40.020> explanation<07:07:40.500> is<07:07:40.920> very 07:07:41.270 --> 07:07:41.280 align:start position:0% now while this explanation is very 07:07:41.280 --> 07:07:43.850 align:start position:0% now while this explanation is very simplified<07:07:41.760> the<07:07:42.420> antenna<07:07:42.840> gain<07:07:43.138> is<07:07:43.440> how<07:07:43.680> it's 07:07:43.850 --> 07:07:43.860 align:start position:0% simplified the antenna gain is how it's 07:07:43.860 --> 07:07:46.368 align:start position:0% simplified the antenna gain is how it's affected<07:07:44.340> by<07:07:44.638> things<07:07:44.940> such<07:07:45.298> as<07:07:45.478> the<07:07:45.840> size<07:07:46.020> and 07:07:46.368 --> 07:07:46.378 align:start position:0% affected by things such as the size and 07:07:46.378 --> 07:07:48.350 align:start position:0% affected by things such as the size and shape<07:07:46.620> of<07:07:46.798> the<07:07:46.978> antenna<07:07:47.400> and<07:07:47.878> the<07:07:48.000> amount<07:07:48.240> of 07:07:48.350 --> 07:07:48.360 align:start position:0% shape of the antenna and the amount of 07:07:48.360 --> 07:07:50.208 align:start position:0% shape of the antenna and the amount of electrical<07:07:48.780> power<07:07:49.020> that's<07:07:49.378> applied<07:07:49.860> to<07:07:50.100> the 07:07:50.208 --> 07:07:50.218 align:start position:0% electrical power that's applied to the 07:07:50.218 --> 07:07:52.490 align:start position:0% electrical power that's applied to the signal<07:07:50.580> and<07:07:51.240> it's<07:07:51.360> all<07:07:51.600> kind<07:07:51.840> of<07:07:51.958> complicated 07:07:52.490 --> 07:07:52.500 align:start position:0% signal and it's all kind of complicated 07:07:52.500 --> 07:07:54.170 align:start position:0% signal and it's all kind of complicated which<07:07:53.160> is<07:07:53.280> why<07:07:53.400> there<07:07:53.580> are<07:07:53.760> people<07:07:53.878> who 07:07:54.170 --> 07:07:54.180 align:start position:0% which is why there are people who 07:07:54.180 --> 07:07:56.270 align:start position:0% which is why there are people who specifically<07:07:54.660> are<07:07:54.958> RF<07:07:55.440> or<07:07:55.680> radio<07:07:55.798> frequency 07:07:56.270 --> 07:07:56.280 align:start position:0% specifically are RF or radio frequency 07:07:56.280 --> 07:07:57.590 align:start position:0% specifically are RF or radio frequency engineers 07:07:57.590 --> 07:07:57.600 align:start position:0% engineers 07:07:57.600 --> 07:07:59.030 align:start position:0% engineers so<07:07:58.020> what<07:07:58.320> you<07:07:58.500> really<07:07:58.620> need<07:07:58.798> to<07:07:58.920> remember 07:07:59.030 --> 07:07:59.040 align:start position:0% so what you really need to remember 07:07:59.040 --> 07:08:01.430 align:start position:0% so what you really need to remember about<07:07:59.280> all<07:07:59.580> this<07:07:59.760> is<07:08:00.600> first 07:08:01.430 --> 07:08:01.440 align:start position:0% about all this is first 07:08:01.440 --> 07:08:04.070 align:start position:0% about all this is first the<07:08:02.040> physical<07:08:02.420> characteristics<07:08:03.420> of<07:08:03.900> an 07:08:04.070 --> 07:08:04.080 align:start position:0% the physical characteristics of an 07:08:04.080 --> 07:08:06.468 align:start position:0% the physical characteristics of an antenna<07:08:04.558> affect<07:08:05.280> its<07:08:05.580> gain 07:08:06.468 --> 07:08:06.478 align:start position:0% antenna affect its gain 07:08:06.478 --> 07:08:09.590 align:start position:0% antenna affect its gain second<07:08:07.138> a<07:08:08.100> higher<07:08:08.340> gain<07:08:08.580> is<07:08:08.760> usually<07:08:09.000> good<07:08:09.298> but 07:08:09.590 --> 07:08:09.600 align:start position:0% second a higher gain is usually good but 07:08:09.600 --> 07:08:11.090 align:start position:0% second a higher gain is usually good but potentially<07:08:09.958> dangerous 07:08:11.090 --> 07:08:11.100 align:start position:0% potentially dangerous 07:08:11.100 --> 07:08:14.330 align:start position:0% potentially dangerous third<07:08:11.878> more<07:08:12.660> gain<07:08:12.958> can<07:08:13.260> be<07:08:13.378> achieved<07:08:13.798> by<07:08:14.040> using 07:08:14.330 --> 07:08:14.340 align:start position:0% third more gain can be achieved by using 07:08:14.340 --> 07:08:17.208 align:start position:0% third more gain can be achieved by using an<07:08:14.520> amplifier<07:08:15.138> and<07:08:16.138> fourth<07:08:16.500> we're<07:08:16.920> going<07:08:17.100> to 07:08:17.208 --> 07:08:17.218 align:start position:0% an amplifier and fourth we're going to 07:08:17.218 --> 07:08:19.730 align:start position:0% an amplifier and fourth we're going to measure<07:08:17.520> it<07:08:17.638> in<07:08:17.878> decibels 07:08:19.730 --> 07:08:19.740 align:start position:0% measure it in decibels 07:08:19.740 --> 07:08:21.468 align:start position:0% measure it in decibels so<07:08:19.978> now<07:08:20.218> that<07:08:20.340> we've<07:08:20.520> defined<07:08:21.058> some<07:08:21.240> of<07:08:21.360> this 07:08:21.468 --> 07:08:21.478 align:start position:0% so now that we've defined some of this 07:08:21.478 --> 07:08:23.208 align:start position:0% so now that we've defined some of this terminology<07:08:22.020> when<07:08:22.378> it<07:08:22.500> comes<07:08:22.620> to<07:08:22.740> antennas 07:08:23.208 --> 07:08:23.218 align:start position:0% terminology when it comes to antennas 07:08:23.218 --> 07:08:24.350 align:start position:0% terminology when it comes to antennas let's<07:08:23.580> take<07:08:23.760> a<07:08:23.820> look<07:08:23.940> at<07:08:24.000> some<07:08:24.180> of<07:08:24.298> the 07:08:24.350 --> 07:08:24.360 align:start position:0% let's take a look at some of the 07:08:24.360 --> 07:08:26.628 align:start position:0% let's take a look at some of the wireless<07:08:24.540> antenna<07:08:25.260> types 07:08:26.628 --> 07:08:26.638 align:start position:0% wireless antenna types 07:08:26.638 --> 07:08:28.968 align:start position:0% wireless antenna types now<07:08:27.000> Wireless<07:08:27.240> antennas<07:08:28.138> can<07:08:28.378> be<07:08:28.620> fairly 07:08:28.968 --> 07:08:28.978 align:start position:0% now Wireless antennas can be fairly 07:08:28.978 --> 07:08:31.368 align:start position:0% now Wireless antennas can be fairly organized<07:08:29.580> into<07:08:29.940> two<07:08:30.420> general<07:08:30.958> broad 07:08:31.368 --> 07:08:31.378 align:start position:0% organized into two general broad 07:08:31.378 --> 07:08:34.010 align:start position:0% organized into two general broad categories<07:08:32.100> the<07:08:33.058> first<07:08:33.240> category<07:08:33.840> is 07:08:34.010 --> 07:08:34.020 align:start position:0% categories the first category is 07:08:34.020 --> 07:08:37.310 align:start position:0% categories the first category is directional<07:08:35.000> directional<07:08:36.000> antennas<07:08:36.660> attempt 07:08:37.310 --> 07:08:37.320 align:start position:0% directional directional antennas attempt 07:08:37.320 --> 07:08:39.410 align:start position:0% directional directional antennas attempt to<07:08:37.500> focus<07:08:37.920> the<07:08:38.100> radio<07:08:38.280> waves<07:08:38.700> into<07:08:38.820> a<07:08:39.120> narrow 07:08:39.410 --> 07:08:39.420 align:start position:0% to focus the radio waves into a narrow 07:08:39.420 --> 07:08:41.288 align:start position:0% to focus the radio waves into a narrow beam<07:08:39.718> going<07:08:40.020> in<07:08:40.320> one<07:08:40.558> specific<07:08:40.860> Direction 07:08:41.288 --> 07:08:41.298 align:start position:0% beam going in one specific Direction 07:08:41.298 --> 07:08:44.448 align:start position:0% beam going in one specific Direction because<07:08:42.298> the<07:08:42.600> signal<07:08:42.958> is<07:08:43.080> being<07:08:43.320> focused<07:08:43.978> it 07:08:44.448 --> 07:08:44.458 align:start position:0% because the signal is being focused it 07:08:44.458 --> 07:08:45.890 align:start position:0% because the signal is being focused it typically<07:08:44.700> means<07:08:45.000> that<07:08:45.120> these<07:08:45.360> antennas<07:08:45.780> are 07:08:45.890 --> 07:08:45.900 align:start position:0% typically means that these antennas are 07:08:45.900 --> 07:08:47.930 align:start position:0% typically means that these antennas are going<07:08:46.020> to<07:08:46.138> have<07:08:46.320> a<07:08:46.680> higher<07:08:47.040> gain 07:08:47.930 --> 07:08:47.940 align:start position:0% going to have a higher gain 07:08:47.940 --> 07:08:50.230 align:start position:0% going to have a higher gain and<07:08:48.360> for<07:08:48.600> the<07:08:48.718> same<07:08:48.900> reason<07:08:49.138> a<07:08:49.558> relatively 07:08:50.230 --> 07:08:50.240 align:start position:0% and for the same reason a relatively 07:08:50.240 --> 07:08:52.968 align:start position:0% and for the same reason a relatively narrower<07:08:51.240> transmission<07:08:51.600> beam<07:08:52.260> versus<07:08:52.620> other 07:08:52.968 --> 07:08:52.978 align:start position:0% narrower transmission beam versus other 07:08:52.978 --> 07:08:54.708 align:start position:0% narrower transmission beam versus other types<07:08:53.340> as<07:08:53.638> you<07:08:53.820> can<07:08:53.940> see 07:08:54.708 --> 07:08:54.718 align:start position:0% types as you can see 07:08:54.718 --> 07:08:56.510 align:start position:0% types as you can see these<07:08:55.320> characteristics<07:08:55.798> allow<07:08:56.160> for<07:08:56.280> a<07:08:56.458> couple 07:08:56.510 --> 07:08:56.520 align:start position:0% these characteristics allow for a couple 07:08:56.520 --> 07:08:58.850 align:start position:0% these characteristics allow for a couple of<07:08:56.700> Bennetts<07:08:57.240> benefits<07:08:57.718> such<07:08:57.958> as<07:08:58.080> a<07:08:58.558> focus 07:08:58.850 --> 07:08:58.860 align:start position:0% of Bennetts benefits such as a focus 07:08:58.860 --> 07:09:01.010 align:start position:0% of Bennetts benefits such as a focus beam<07:08:59.218> which<07:08:59.458> ensures<07:08:59.820> a<07:09:00.360> better<07:09:00.478> signal 07:09:01.010 --> 07:09:01.020 align:start position:0% beam which ensures a better signal 07:09:01.020 --> 07:09:03.708 align:start position:0% beam which ensures a better signal quality<07:09:01.378> and<07:09:02.100> a<07:09:02.340> smaller<07:09:02.760> transmission<07:09:03.058> beam 07:09:03.708 --> 07:09:03.718 align:start position:0% quality and a smaller transmission beam 07:09:03.718 --> 07:09:05.690 align:start position:0% quality and a smaller transmission beam which<07:09:04.138> means<07:09:04.378> that<07:09:04.500> there's<07:09:04.740> less<07:09:05.100> area<07:09:05.400> of 07:09:05.690 --> 07:09:05.700 align:start position:0% which means that there's less area of 07:09:05.700 --> 07:09:07.190 align:start position:0% which means that there's less area of interference 07:09:07.190 --> 07:09:07.200 align:start position:0% interference 07:09:07.200 --> 07:09:09.110 align:start position:0% interference how<07:09:07.620> directional<07:09:08.100> antennas<07:09:08.700> are<07:09:08.940> really 07:09:09.110 --> 07:09:09.120 align:start position:0% how directional antennas are really 07:09:09.120 --> 07:09:11.628 align:start position:0% how directional antennas are really commonplace<07:09:09.718> in<07:09:10.020> implementations<07:09:10.680> of 07:09:11.628 --> 07:09:11.638 align:start position:0% commonplace in implementations of 07:09:11.638 --> 07:09:13.670 align:start position:0% commonplace in implementations of point-to-point<07:09:12.420> networks<07:09:13.080> which<07:09:13.500> makes 07:09:13.670 --> 07:09:13.680 align:start position:0% point-to-point networks which makes 07:09:13.680 --> 07:09:16.548 align:start position:0% point-to-point networks which makes sense<07:09:13.920> because<07:09:14.280> I<07:09:14.520> have<07:09:14.638> this<07:09:14.878> Limited<07:09:15.840> sort 07:09:16.548 --> 07:09:16.558 align:start position:0% sense because I have this Limited sort 07:09:16.558 --> 07:09:19.010 align:start position:0% sense because I have this Limited sort of<07:09:16.740> area<07:09:17.458> in<07:09:17.940> which<07:09:18.120> the<07:09:18.360> waves<07:09:18.718> are<07:09:18.780> going<07:09:18.900> to 07:09:19.010 --> 07:09:19.020 align:start position:0% of area in which the waves are going to 07:09:19.020 --> 07:09:21.590 align:start position:0% of area in which the waves are going to be<07:09:19.080> traveling<07:09:19.558> and<07:09:20.458> perhaps<07:09:20.820> most<07:09:21.240> commonly 07:09:21.590 --> 07:09:21.600 align:start position:0% be traveling and perhaps most commonly 07:09:21.600 --> 07:09:24.650 align:start position:0% be traveling and perhaps most commonly you've<07:09:21.840> seen<07:09:22.020> them<07:09:22.400> in<07:09:23.400> Dish<07:09:23.580> Networks<07:09:24.180> for 07:09:24.650 --> 07:09:24.660 align:start position:0% you've seen them in Dish Networks for 07:09:24.660 --> 07:09:26.868 align:start position:0% you've seen them in Dish Networks for satellite<07:09:25.138> TV<07:09:25.440> and<07:09:25.620> the<07:09:25.798> internet 07:09:26.868 --> 07:09:26.878 align:start position:0% satellite TV and the internet 07:09:26.878 --> 07:09:30.288 align:start position:0% satellite TV and the internet now<07:09:27.718> the<07:09:28.080> next<07:09:28.260> category<07:09:28.798> of<07:09:29.040> antenna<07:09:29.520> is<07:09:29.878> are 07:09:30.288 --> 07:09:30.298 align:start position:0% now the next category of antenna is are 07:09:30.298 --> 07:09:32.990 align:start position:0% now the next category of antenna is are called<07:09:30.740> omnidirectional<07:09:31.740> antennas<07:09:32.340> this 07:09:32.990 --> 07:09:33.000 align:start position:0% called omnidirectional antennas this 07:09:33.000 --> 07:09:35.150 align:start position:0% called omnidirectional antennas this type<07:09:33.058> of<07:09:33.240> antenna<07:09:33.660> emits<07:09:34.080> the<07:09:34.200> radio<07:09:34.320> waves<07:09:34.798> in 07:09:35.150 --> 07:09:35.160 align:start position:0% type of antenna emits the radio waves in 07:09:35.160 --> 07:09:38.270 align:start position:0% type of antenna emits the radio waves in all<07:09:35.400> directions<07:09:35.580> on<07:09:36.478> the<07:09:36.660> same<07:09:36.840> plane<07:09:37.320> equally 07:09:38.270 --> 07:09:38.280 align:start position:0% all directions on the same plane equally 07:09:38.280 --> 07:09:41.030 align:start position:0% all directions on the same plane equally in<07:09:39.058> some<07:09:39.180> ways<07:09:39.420> these<07:09:39.840> are<07:09:39.900> called<07:09:40.200> donuts 07:09:41.030 --> 07:09:41.040 align:start position:0% in some ways these are called donuts 07:09:41.040 --> 07:09:42.230 align:start position:0% in some ways these are called donuts because 07:09:42.230 --> 07:09:42.240 align:start position:0% because 07:09:42.240 --> 07:09:44.628 align:start position:0% because the<07:09:42.718> wave<07:09:42.900> comes<07:09:43.320> out<07:09:43.500> in<07:09:43.920> a<07:09:44.100> donut<07:09:44.280> looking 07:09:44.628 --> 07:09:44.638 align:start position:0% the wave comes out in a donut looking 07:09:44.638 --> 07:09:47.270 align:start position:0% the wave comes out in a donut looking shape<07:09:45.660> now<07:09:46.080> because<07:09:46.320> the<07:09:46.620> signal<07:09:46.920> is<07:09:47.040> being 07:09:47.270 --> 07:09:47.280 align:start position:0% shape now because the signal is being 07:09:47.280 --> 07:09:51.350 align:start position:0% shape now because the signal is being transmitted<07:09:47.878> in<07:09:48.420> any<07:09:48.600> direction<07:09:48.900> such<07:09:49.798> as<07:09:49.978> on 07:09:51.350 --> 07:09:51.360 align:start position:0% transmitted in any direction such as on 07:09:51.360 --> 07:09:53.510 align:start position:0% transmitted in any direction such as on a<07:09:52.020> wireless<07:09:52.138> router 07:09:53.510 --> 07:09:53.520 align:start position:0% a wireless router 07:09:53.520 --> 07:09:56.750 align:start position:0% a wireless router these<07:09:54.240> antennas<07:09:54.660> have<07:09:55.020> a<07:09:55.558> relatively<07:09:56.160> low 07:09:56.750 --> 07:09:56.760 align:start position:0% these antennas have a relatively low 07:09:56.760 --> 07:10:00.010 align:start position:0% these antennas have a relatively low gain<07:09:57.080> when<07:09:58.080> compared 07:10:00.010 --> 07:10:00.020 align:start position:0% gain when compared 07:10:00.020 --> 07:10:04.368 align:start position:0% gain when compared with<07:10:01.020> a<07:10:01.500> uh<07:10:01.978> directional<07:10:02.638> antenna<07:10:03.478> now<07:10:03.958> where 07:10:04.368 --> 07:10:04.378 align:start position:0% with a uh directional antenna now where 07:10:04.378 --> 07:10:06.110 align:start position:0% with a uh directional antenna now where these<07:10:04.680> antennas<07:10:05.040> lack<07:10:05.340> and<07:10:05.520> gain<07:10:05.760> they<07:10:06.000> make 07:10:06.110 --> 07:10:06.120 align:start position:0% these antennas lack and gain they make 07:10:06.120 --> 07:10:08.628 align:start position:0% these antennas lack and gain they make up<07:10:06.478> for<07:10:06.660> it<07:10:06.840> because<07:10:07.020> obviously<07:10:07.500> they<07:10:07.798> have<07:10:08.040> a 07:10:08.628 --> 07:10:08.638 align:start position:0% up for it because obviously they have a 07:10:08.638 --> 07:10:14.810 align:start position:0% up for it because obviously they have a greater<07:10:09.000> coverage<07:10:09.420> area 07:10:14.810 --> 07:10:14.820 align:start position:0% 07:10:14.820 --> 07:10:17.570 align:start position:0% as<07:10:15.360> the<07:10:15.660> donut<07:10:15.780> wave<07:10:16.320> implies 07:10:17.570 --> 07:10:17.580 align:start position:0% as the donut wave implies 07:10:17.580 --> 07:10:18.948 align:start position:0% as the donut wave implies the<07:10:17.878> good<07:10:18.000> part<07:10:18.180> about<07:10:18.360> this<07:10:18.600> greater 07:10:18.948 --> 07:10:18.958 align:start position:0% the good part about this greater 07:10:18.958 --> 07:10:21.288 align:start position:0% the good part about this greater coverage<07:10:19.320> area<07:10:19.558> is<07:10:20.400> that<07:10:20.580> transmitting<07:10:21.120> and 07:10:21.288 --> 07:10:21.298 align:start position:0% coverage area is that transmitting and 07:10:21.298 --> 07:10:23.990 align:start position:0% coverage area is that transmitting and receiving<07:10:21.600> Stations<07:10:22.320> don't<07:10:22.920> have<07:10:23.160> to<07:10:23.340> have<07:10:23.580> a 07:10:23.990 --> 07:10:24.000 align:start position:0% receiving Stations don't have to have a 07:10:24.000 --> 07:10:26.628 align:start position:0% receiving Stations don't have to have a specific<07:10:24.298> alignment<07:10:24.958> with<07:10:25.200> one<07:10:25.378> another 07:10:26.628 --> 07:10:26.638 align:start position:0% specific alignment with one another 07:10:26.638 --> 07:10:28.490 align:start position:0% specific alignment with one another they<07:10:27.000> can<07:10:27.120> be<07:10:27.240> in<07:10:27.420> any<07:10:27.540> direction<07:10:27.780> from<07:10:28.260> the 07:10:28.490 --> 07:10:28.500 align:start position:0% they can be in any direction from the 07:10:28.500 --> 07:10:30.830 align:start position:0% they can be in any direction from the antenna<07:10:29.400> these<07:10:30.000> antennas<07:10:30.360> are<07:10:30.540> really<07:10:30.660> going 07:10:30.830 --> 07:10:30.840 align:start position:0% antenna these antennas are really going 07:10:30.840 --> 07:10:33.110 align:start position:0% antenna these antennas are really going to<07:10:30.958> be<07:10:31.020> used<07:10:31.260> in<07:10:31.740> distributed<07:10:32.218> networks<07:10:32.820> and 07:10:33.110 --> 07:10:33.120 align:start position:0% to be used in distributed networks and 07:10:33.120 --> 07:10:35.090 align:start position:0% to be used in distributed networks and multi-point<07:10:33.600> networks<07:10:34.200> as<07:10:34.378> well<07:10:34.558> so 07:10:35.090 --> 07:10:35.100 align:start position:0% multi-point networks as well so 07:10:35.100 --> 07:10:37.190 align:start position:0% multi-point networks as well so omnidirectional<07:10:36.000> antennas<07:10:36.478> are<07:10:36.718> implemented 07:10:37.190 --> 07:10:37.200 align:start position:0% omnidirectional antennas are implemented 07:10:37.200 --> 07:10:40.010 align:start position:0% omnidirectional antennas are implemented everywhere<07:10:37.680> from<07:10:38.240> cell<07:10:39.240> phones<07:10:39.600> to<07:10:39.840> radio 07:10:40.010 --> 07:10:40.020 align:start position:0% everywhere from cell phones to radio 07:10:40.020 --> 07:10:42.650 align:start position:0% everywhere from cell phones to radio broadcasting<07:10:40.920> antennas<07:10:41.458> to<07:10:41.760> walkie-talkies 07:10:42.650 --> 07:10:42.660 align:start position:0% broadcasting antennas to walkie-talkies 07:10:42.660 --> 07:10:47.750 align:start position:0% broadcasting antennas to walkie-talkies to<07:10:43.260> GPS<07:10:43.798> to<07:10:44.780> mostly<07:10:45.780> our<07:10:46.680> wireless<07:10:46.920> networks 07:10:47.750 --> 07:10:47.760 align:start position:0% to GPS to mostly our wireless networks 07:10:47.760 --> 07:10:51.590 align:start position:0% to GPS to mostly our wireless networks at<07:10:47.940> home<07:10:48.120> and<07:10:48.780> in<07:10:49.080> a<07:10:49.260> lot<07:10:49.320> of<07:10:49.500> offices<07:10:50.760> Etc 07:10:51.590 --> 07:10:51.600 align:start position:0% at home and in a lot of offices Etc 07:10:51.600 --> 07:10:53.810 align:start position:0% at home and in a lot of offices Etc so<07:10:51.958> now<07:10:52.080> that<07:10:52.200> we've<07:10:52.378> talked<07:10:52.740> about<07:10:52.860> a<07:10:53.458> lot<07:10:53.700> of 07:10:53.810 --> 07:10:53.820 align:start position:0% so now that we've talked about a lot of 07:10:53.820 --> 07:10:55.490 align:start position:0% so now that we've talked about a lot of the<07:10:53.940> different<07:10:54.120> types<07:10:54.660> of<07:10:54.780> antennas<07:10:55.320> and 07:10:55.490 --> 07:10:55.500 align:start position:0% the different types of antennas and 07:10:55.500 --> 07:10:57.890 align:start position:0% the different types of antennas and their<07:10:55.680> characteristics<07:10:56.340> the<07:10:57.058> the<07:10:57.240> last<07:10:57.718> thing 07:10:57.890 --> 07:10:57.900 align:start position:0% their characteristics the the last thing 07:10:57.900 --> 07:10:59.990 align:start position:0% their characteristics the the last thing I'd<07:10:58.080> like<07:10:58.200> to<07:10:58.320> mention<07:10:58.440> about<07:10:58.740> gain<07:10:59.100> is<07:10:59.700> the 07:10:59.990 --> 07:11:00.000 align:start position:0% I'd like to mention about gain is the 07:11:00.000 --> 07:11:02.810 align:start position:0% I'd like to mention about gain is the more<07:11:00.180> gain<07:11:00.540> the<07:11:00.840> antenna<07:11:01.378> has<07:11:01.680> the<07:11:02.520> smaller 07:11:02.810 --> 07:11:02.820 align:start position:0% more gain the antenna has the smaller 07:11:02.820 --> 07:11:05.628 align:start position:0% more gain the antenna has the smaller the<07:11:03.000> effective<07:11:03.420> angle<07:11:03.900> of<07:11:04.020> use<07:11:04.200> needs<07:11:04.740> to<07:11:04.860> be 07:11:05.628 --> 07:11:05.638 align:start position:0% the effective angle of use needs to be 07:11:05.638 --> 07:11:07.670 align:start position:0% the effective angle of use needs to be so<07:11:06.240> the<07:11:06.540> next<07:11:06.660> thing<07:11:06.840> we<07:11:07.020> need<07:11:07.138> to<07:11:07.260> do<07:11:07.440> is 07:11:07.670 --> 07:11:07.680 align:start position:0% so the next thing we need to do is 07:11:07.680 --> 07:11:10.430 align:start position:0% so the next thing we need to do is outline<07:11:08.240> what's<07:11:09.240> going<07:11:09.478> to<07:11:09.718> affect<07:11:10.020> the 07:11:10.430 --> 07:11:10.440 align:start position:0% outline what's going to affect the 07:11:10.440 --> 07:11:12.890 align:start position:0% outline what's going to affect the performance<07:11:10.798> of<07:11:11.100> these<07:11:11.280> antennas 07:11:12.890 --> 07:11:12.900 align:start position:0% performance of these antennas 07:11:12.900 --> 07:11:15.110 align:start position:0% performance of these antennas so<07:11:13.320> the<07:11:13.500> physical<07:11:13.620> layer<07:11:14.100> of<07:11:14.218> the<07:11:14.400> network<07:11:14.580> the 07:11:15.110 --> 07:11:15.120 align:start position:0% so the physical layer of the network the 07:11:15.120 --> 07:11:16.910 align:start position:0% so the physical layer of the network the transmission<07:11:15.298> of<07:11:15.718> bits<07:11:16.138> from<07:11:16.378> one<07:11:16.558> point<07:11:16.740> to 07:11:16.910 --> 07:11:16.920 align:start position:0% transmission of bits from one point to 07:11:16.920 --> 07:11:18.770 align:start position:0% transmission of bits from one point to the<07:11:17.100> other<07:11:17.218> there<07:11:18.000> are<07:11:18.120> a<07:11:18.180> lot<07:11:18.240> of<07:11:18.360> things<07:11:18.478> that 07:11:18.770 --> 07:11:18.780 align:start position:0% the other there are a lot of things that 07:11:18.780 --> 07:11:20.570 align:start position:0% the other there are a lot of things that can<07:11:18.900> hinder<07:11:19.320> the<07:11:19.500> data<07:11:19.860> while<07:11:20.218> it's<07:11:20.400> in 07:11:20.570 --> 07:11:20.580 align:start position:0% can hinder the data while it's in 07:11:20.580 --> 07:11:23.270 align:start position:0% can hinder the data while it's in transit<07:11:21.478> these<07:11:22.138> things<07:11:22.378> that<07:11:22.860> are<07:11:23.040> going<07:11:23.160> to 07:11:23.270 --> 07:11:23.280 align:start position:0% transit these things that are going to 07:11:23.280 --> 07:11:25.490 align:start position:0% transit these things that are going to impede<07:11:23.700> our<07:11:23.820> signal<07:11:24.180> are<07:11:24.478> going<07:11:24.660> to<07:11:24.840> depend<07:11:25.200> on 07:11:25.490 --> 07:11:25.500 align:start position:0% impede our signal are going to depend on 07:11:25.500 --> 07:11:28.368 align:start position:0% impede our signal are going to depend on the<07:11:25.680> type<07:11:25.920> of<07:11:26.218> data<07:11:26.580> in<07:11:27.120> transmission 07:11:28.368 --> 07:11:28.378 align:start position:0% the type of data in transmission 07:11:28.378 --> 07:11:32.330 align:start position:0% the type of data in transmission so<07:11:28.740> for<07:11:28.978> infrared<07:11:29.780> data<07:11:30.780> Transmissions<07:11:31.378> the 07:11:32.330 --> 07:11:32.340 align:start position:0% so for infrared data Transmissions the 07:11:32.340 --> 07:11:34.548 align:start position:0% so for infrared data Transmissions the antennas<07:11:32.820> need<07:11:33.058> a<07:11:33.298> line<07:11:33.540> of<07:11:33.718> sight<07:11:34.020> or<07:11:34.200> Los 07:11:34.548 --> 07:11:34.558 align:start position:0% antennas need a line of sight or Los 07:11:34.558 --> 07:11:37.250 align:start position:0% antennas need a line of sight or Los just<07:11:35.218> like<07:11:35.400> your<07:11:35.580> remote<07:11:35.760> control<07:11:36.260> almost 07:11:37.250 --> 07:11:37.260 align:start position:0% just like your remote control almost 07:11:37.260 --> 07:11:39.468 align:start position:0% just like your remote control almost anything<07:11:37.620> that<07:11:38.040> obstructs<07:11:38.520> this<07:11:38.700> loss<07:11:39.240> is 07:11:39.468 --> 07:11:39.478 align:start position:0% anything that obstructs this loss is 07:11:39.478 --> 07:11:41.448 align:start position:0% anything that obstructs this loss is going<07:11:39.660> to<07:11:39.840> affect<07:11:40.200> the<07:11:40.440> signal<07:11:40.798> this<07:11:41.340> could 07:11:41.448 --> 07:11:41.458 align:start position:0% going to affect the signal this could 07:11:41.458 --> 07:11:45.430 align:start position:0% going to affect the signal this could include<07:11:41.760> stuff<07:11:42.058> like<07:11:42.298> smoke<07:11:42.660> smog<07:11:43.378> fog<07:11:44.340> dust 07:11:45.430 --> 07:11:45.440 align:start position:0% include stuff like smoke smog fog dust 07:11:45.440 --> 07:11:48.770 align:start position:0% include stuff like smoke smog fog dust even<07:11:46.440> pulses<07:11:47.040> of<07:11:47.280> light<07:11:47.520> and<07:11:48.000> bright<07:11:48.240> sunlight 07:11:48.770 --> 07:11:48.780 align:start position:0% even pulses of light and bright sunlight 07:11:48.780 --> 07:11:51.170 align:start position:0% even pulses of light and bright sunlight can<07:11:49.260> very<07:11:49.500> easily<07:11:49.978> change<07:11:50.458> the<07:11:50.820> maximum 07:11:51.170 --> 07:11:51.180 align:start position:0% can very easily change the maximum 07:11:51.180 --> 07:11:53.510 align:start position:0% can very easily change the maximum transmitting<07:11:51.840> distance<07:11:52.080> and<07:11:52.978> obviously<07:11:53.340> if 07:11:53.510 --> 07:11:53.520 align:start position:0% transmitting distance and obviously if 07:11:53.520 --> 07:11:55.070 align:start position:0% transmitting distance and obviously if anything 07:11:55.070 --> 07:11:55.080 align:start position:0% anything 07:11:55.080 --> 07:11:57.170 align:start position:0% anything standing<07:11:55.860> in<07:11:55.978> the<07:11:56.160> way<07:11:56.280> we're<07:11:56.638> going<07:11:56.820> to<07:11:56.878> be<07:11:57.000> in 07:11:57.170 --> 07:11:57.180 align:start position:0% standing in the way we're going to be in 07:11:57.180 --> 07:11:58.250 align:start position:0% standing in the way we're going to be in big<07:11:57.360> trouble 07:11:58.250 --> 07:11:58.260 align:start position:0% big trouble 07:11:58.260 --> 07:12:01.310 align:start position:0% big trouble now<07:11:58.798> for<07:11:59.040> microwave<07:11:59.580> Transmissions<07:12:00.420> the 07:12:01.310 --> 07:12:01.320 align:start position:0% now for microwave Transmissions the 07:12:01.320 --> 07:12:04.490 align:start position:0% now for microwave Transmissions the signals<07:12:01.860> also<07:12:02.218> considered<07:12:02.760> Los<07:12:03.180> or<07:12:04.020> line<07:12:04.320> of 07:12:04.490 --> 07:12:04.500 align:start position:0% signals also considered Los or line of 07:12:04.500 --> 07:12:06.590 align:start position:0% signals also considered Los or line of sight<07:12:04.740> this<07:12:05.520> typically<07:12:05.820> doesn't<07:12:06.058> mean<07:12:06.360> that 07:12:06.590 --> 07:12:06.600 align:start position:0% sight this typically doesn't mean that 07:12:06.600 --> 07:12:08.270 align:start position:0% sight this typically doesn't mean that we<07:12:06.780> need<07:12:06.900> to<07:12:07.020> be<07:12:07.138> able<07:12:07.320> to<07:12:07.558> see<07:12:07.798> the<07:12:08.040> receiving 07:12:08.270 --> 07:12:08.280 align:start position:0% we need to be able to see the receiving 07:12:08.280 --> 07:12:10.548 align:start position:0% we need to be able to see the receiving station<07:12:08.580> with<07:12:08.940> our<07:12:09.180> naked<07:12:09.540> eye<07:12:09.718> it<07:12:10.260> just<07:12:10.378> means 07:12:10.548 --> 07:12:10.558 align:start position:0% station with our naked eye it just means 07:12:10.558 --> 07:12:12.650 align:start position:0% station with our naked eye it just means that<07:12:10.740> the<07:12:10.860> signal<07:12:11.160> has<07:12:11.400> to<07:12:11.520> have<07:12:11.700> an<07:12:12.000> unimpeded 07:12:12.650 --> 07:12:12.660 align:start position:0% that the signal has to have an unimpeded 07:12:12.660 --> 07:12:14.390 align:start position:0% that the signal has to have an unimpeded path<07:12:12.900> from<07:12:13.260> the<07:12:13.378> source<07:12:13.740> of<07:12:13.798> the<07:12:13.978> destination 07:12:14.390 --> 07:12:14.400 align:start position:0% path from the source of the destination 07:12:14.400 --> 07:12:17.690 align:start position:0% path from the source of the destination most<07:12:15.240> commonly<07:12:15.740> satellite<07:12:16.740> the<07:12:17.520> ground 07:12:17.690 --> 07:12:17.700 align:start position:0% most commonly satellite the ground 07:12:17.700 --> 07:12:20.090 align:start position:0% most commonly satellite the ground station<07:12:18.120> has<07:12:18.600> to<07:12:18.718> be<07:12:18.840> within<07:12:19.260> the<07:12:19.558> footprint 07:12:20.090 --> 07:12:20.100 align:start position:0% station has to be within the footprint 07:12:20.100 --> 07:12:23.030 align:start position:0% station has to be within the footprint of<07:12:20.760> the<07:12:21.000> orbiting<07:12:21.540> satellite<07:12:22.138> generally 07:12:23.030 --> 07:12:23.040 align:start position:0% of the orbiting satellite generally 07:12:23.040 --> 07:12:24.230 align:start position:0% of the orbiting satellite generally speaking 07:12:24.230 --> 07:12:24.240 align:start position:0% speaking 07:12:24.240 --> 07:12:26.270 align:start position:0% speaking distance<07:12:24.840> is<07:12:25.200> the<07:12:25.378> performance<07:12:25.798> Factor 07:12:26.270 --> 07:12:26.280 align:start position:0% distance is the performance Factor 07:12:26.280 --> 07:12:28.128 align:start position:0% distance is the performance Factor that's<07:12:26.520> going<07:12:26.760> to<07:12:26.940> affect<07:12:27.298> these<07:12:27.780> microwave 07:12:28.128 --> 07:12:28.138 align:start position:0% that's going to affect these microwave 07:12:28.138 --> 07:12:29.930 align:start position:0% that's going to affect these microwave Transmissions<07:12:28.740> the<07:12:29.160> most 07:12:29.930 --> 07:12:29.940 align:start position:0% Transmissions the most 07:12:29.940 --> 07:12:32.150 align:start position:0% Transmissions the most now<07:12:30.360> the<07:12:30.540> factors<07:12:30.840> that<07:12:31.020> are<07:12:31.200> going<07:12:31.378> to<07:12:31.558> affect 07:12:32.150 --> 07:12:32.160 align:start position:0% now the factors that are going to affect 07:12:32.160 --> 07:12:34.490 align:start position:0% now the factors that are going to affect radio<07:12:33.000> Transmissions<07:12:33.780> which<07:12:34.080> are<07:12:34.200> the<07:12:34.320> ones 07:12:34.490 --> 07:12:34.500 align:start position:0% radio Transmissions which are the ones 07:12:34.500 --> 07:12:37.368 align:start position:0% radio Transmissions which are the ones we<07:12:34.680> use<07:12:34.798> in<07:12:35.160> Wi-Fi<07:12:35.580> settings<07:12:36.200> mostly<07:12:37.200> start 07:12:37.368 --> 07:12:37.378 align:start position:0% we use in Wi-Fi settings mostly start 07:12:37.378 --> 07:12:39.048 align:start position:0% we use in Wi-Fi settings mostly start with<07:12:37.620> the<07:12:37.798> antenna<07:12:38.160> itself 07:12:39.048 --> 07:12:39.058 align:start position:0% with the antenna itself 07:12:39.058 --> 07:12:41.030 align:start position:0% with the antenna itself so<07:12:39.420> the<07:12:39.600> signal<07:12:39.958> characteristics<07:12:40.680> of<07:12:40.860> an 07:12:41.030 --> 07:12:41.040 align:start position:0% so the signal characteristics of an 07:12:41.040 --> 07:12:42.708 align:start position:0% so the signal characteristics of an antenna<07:12:41.458> can<07:12:41.700> affect<07:12:42.000> the<07:12:42.298> maximum 07:12:42.708 --> 07:12:42.718 align:start position:0% antenna can affect the maximum 07:12:42.718 --> 07:12:45.288 align:start position:0% antenna can affect the maximum transmitting<07:12:43.378> distance<07:12:43.760> also<07:12:44.760> performance 07:12:45.288 --> 07:12:45.298 align:start position:0% transmitting distance also performance 07:12:45.298 --> 07:12:47.150 align:start position:0% transmitting distance also performance can<07:12:45.600> be<07:12:45.718> limited<07:12:46.080> if<07:12:46.260> there<07:12:46.378> are<07:12:46.500> any<07:12:46.620> objects 07:12:47.150 --> 07:12:47.160 align:start position:0% can be limited if there are any objects 07:12:47.160 --> 07:12:50.150 align:start position:0% can be limited if there are any objects that<07:12:47.458> are<07:12:47.580> very<07:12:47.760> electrical<07:12:48.600> or<07:12:49.440> give<07:12:49.740> off<07:12:49.920> a 07:12:50.150 --> 07:12:50.160 align:start position:0% that are very electrical or give off a 07:12:50.160 --> 07:12:53.448 align:start position:0% that are very electrical or give off a lot<07:12:50.280> of<07:12:50.400> magnet<07:12:51.020> magnetic<07:12:52.020> fields<07:12:52.440> near<07:12:53.218> or 07:12:53.448 --> 07:12:53.458 align:start position:0% lot of magnet magnetic fields near or 07:12:53.458 --> 07:12:55.128 align:start position:0% lot of magnet magnetic fields near or around<07:12:53.638> the<07:12:54.058> transmitting<07:12:54.600> or<07:12:54.780> receiving 07:12:55.128 --> 07:12:55.138 align:start position:0% around the transmitting or receiving 07:12:55.138 --> 07:12:56.810 align:start position:0% around the transmitting or receiving stations<07:12:55.920> and<07:12:56.100> this<07:12:56.280> is<07:12:56.340> going<07:12:56.520> to<07:12:56.638> cause 07:12:56.810 --> 07:12:56.820 align:start position:0% stations and this is going to cause 07:12:56.820 --> 07:12:58.368 align:start position:0% stations and this is going to cause problems<07:12:57.298> to<07:12:57.478> arise 07:12:58.368 --> 07:12:58.378 align:start position:0% problems to arise 07:12:58.378 --> 07:13:01.070 align:start position:0% problems to arise we<07:12:58.860> can<07:12:58.978> also<07:12:59.160> have<07:12:59.340> normal<07:12:59.700> ambient<07:13:00.240> noise<07:13:00.660> or 07:13:01.070 --> 07:13:01.080 align:start position:0% we can also have normal ambient noise or 07:13:01.080 --> 07:13:02.750 align:start position:0% we can also have normal ambient noise or environmental<07:13:01.798> conditions<07:13:02.280> which<07:13:02.520> can 07:13:02.750 --> 07:13:02.760 align:start position:0% environmental conditions which can 07:13:02.760 --> 07:13:04.670 align:start position:0% environmental conditions which can affect<07:13:03.058> the<07:13:03.360> distance<07:13:03.600> these<07:13:04.138> signals<07:13:04.500> can 07:13:04.670 --> 07:13:04.680 align:start position:0% affect the distance these signals can 07:13:04.680 --> 07:13:07.190 align:start position:0% affect the distance these signals can travel<07:13:04.940> finally<07:13:05.940> the<07:13:06.360> greatest<07:13:06.540> factor 07:13:07.190 --> 07:13:07.200 align:start position:0% travel finally the greatest factor 07:13:07.200 --> 07:13:08.628 align:start position:0% travel finally the greatest factor that's<07:13:07.558> going<07:13:07.740> to<07:13:07.798> affect<07:13:08.100> Bluetooth 07:13:08.628 --> 07:13:08.638 align:start position:0% that's going to affect Bluetooth 07:13:08.638 --> 07:13:10.968 align:start position:0% that's going to affect Bluetooth Transmissions<07:13:09.478> is<07:13:09.900> the<07:13:10.138> distance<07:13:10.378> between 07:13:10.968 --> 07:13:10.978 align:start position:0% Transmissions is the distance between 07:13:10.978 --> 07:13:14.750 align:start position:0% Transmissions is the distance between the<07:13:11.760> uh<07:13:12.240> the<07:13:12.900> devices<07:13:13.200> just<07:13:14.100> because<07:13:14.280> of<07:13:14.580> the 07:13:14.750 --> 07:13:14.760 align:start position:0% the uh the devices just because of the 07:13:14.760 --> 07:13:17.208 align:start position:0% the uh the devices just because of the technology<07:13:15.120> we're<07:13:15.478> using<07:13:15.840> as<07:13:16.558> most<07:13:16.860> Bluetooth 07:13:17.208 --> 07:13:17.218 align:start position:0% technology we're using as most Bluetooth 07:13:17.218 --> 07:13:21.650 align:start position:0% technology we're using as most Bluetooth devices<07:13:17.760> are<07:13:18.000> what<07:13:18.120> we<07:13:18.240> call<07:13:18.478> Class<07:13:19.260> 2<07:13:19.620> devices 07:13:21.650 --> 07:13:21.660 align:start position:0% devices are what we call Class 2 devices 07:13:21.660 --> 07:13:24.830 align:start position:0% devices are what we call Class 2 devices this<07:13:22.500> means<07:13:22.798> that<07:13:22.978> we<07:13:23.160> have<07:13:23.340> about<07:13:23.638> a<07:13:24.120> 10<07:13:24.360> meter 07:13:24.830 --> 07:13:24.840 align:start position:0% this means that we have about a 10 meter 07:13:24.840 --> 07:13:27.830 align:start position:0% this means that we have about a 10 meter which<07:13:25.260> is<07:13:25.378> equivalent<07:13:25.860> to<07:13:26.160> around<07:13:26.660> although<07:13:27.660> a 07:13:27.830 --> 07:13:27.840 align:start position:0% which is equivalent to around although a 07:13:27.840 --> 07:13:29.810 align:start position:0% which is equivalent to around although a little<07:13:28.020> more<07:13:28.200> than<07:13:28.378> 30<07:13:28.740> feet 07:13:29.810 --> 07:13:29.820 align:start position:0% little more than 30 feet 07:13:29.820 --> 07:13:33.650 align:start position:0% little more than 30 feet and<07:13:30.360> this<07:13:30.540> is<07:13:30.660> due<07:13:30.900> to<07:13:31.340> power<07:13:32.340> limitations<07:13:32.940> now 07:13:33.650 --> 07:13:33.660 align:start position:0% and this is due to power limitations now 07:13:33.660 --> 07:13:34.788 align:start position:0% and this is due to power limitations now depending<07:13:33.958> on<07:13:34.138> the<07:13:34.260> type<07:13:34.440> of<07:13:34.620> Bluetooth 07:13:34.788 --> 07:13:34.798 align:start position:0% depending on the type of Bluetooth 07:13:34.798 --> 07:13:37.190 align:start position:0% depending on the type of Bluetooth device<07:13:35.280> it<07:13:35.700> may<07:13:35.820> operate<07:13:36.120> on<07:13:36.360> the<07:13:36.478> 2.4 07:13:37.190 --> 07:13:37.200 align:start position:0% device it may operate on the 2.4 07:13:37.200 --> 07:13:39.288 align:start position:0% device it may operate on the 2.4 gigahertz 07:13:39.288 --> 07:13:39.298 align:start position:0% gigahertz 07:13:39.298 --> 07:13:41.330 align:start position:0% gigahertz frequency<07:13:39.900> which<07:13:40.320> by<07:13:40.558> the<07:13:40.680> way<07:13:40.740> is<07:13:40.978> the<07:13:41.218> same 07:13:41.330 --> 07:13:41.340 align:start position:0% frequency which by the way is the same 07:13:41.340 --> 07:13:43.548 align:start position:0% frequency which by the way is the same as<07:13:41.520> Wi-Fi<07:13:41.940> and<07:13:42.600> so<07:13:42.718> there<07:13:42.900> that's<07:13:43.200> why<07:13:43.378> we're 07:13:43.548 --> 07:13:43.558 align:start position:0% as Wi-Fi and so there that's why we're 07:13:43.558 --> 07:13:44.930 align:start position:0% as Wi-Fi and so there that's why we're going<07:13:43.680> to<07:13:43.740> have<07:13:43.860> a<07:13:44.040> problem<07:13:44.218> and<07:13:44.638> sometimes 07:13:44.930 --> 07:13:44.940 align:start position:0% going to have a problem and sometimes 07:13:44.940 --> 07:13:46.490 align:start position:0% going to have a problem and sometimes we're<07:13:45.120> also<07:13:45.360> going<07:13:45.420> to<07:13:45.420> see<07:13:45.540> it<07:13:45.600> on<07:13:45.780> the<07:13:45.900> 4.6 07:13:46.490 --> 07:13:46.500 align:start position:0% we're also going to see it on the 4.6 07:13:46.500 --> 07:13:48.650 align:start position:0% we're also going to see it on the 4.6 gigahertz<07:13:46.978> frequency 07:13:48.650 --> 07:13:48.660 align:start position:0% gigahertz frequency 07:13:48.660 --> 07:13:51.190 align:start position:0% gigahertz frequency and<07:13:49.020> for<07:13:49.200> those<07:13:49.378> that<07:13:49.620> operate<07:13:49.978> at<07:13:50.160> 2.4 07:13:51.190 --> 07:13:51.200 align:start position:0% and for those that operate at 2.4 07:13:51.200 --> 07:13:54.230 align:start position:0% and for those that operate at 2.4 obviously<07:13:52.200> not<07:13:52.680> only<07:13:52.860> does<07:13:53.218> radio<07:13:53.458> operate<07:13:54.058> at 07:13:54.230 --> 07:13:54.240 align:start position:0% obviously not only does radio operate at 07:13:54.240 --> 07:13:56.150 align:start position:0% obviously not only does radio operate at those<07:13:54.420> or<07:13:54.718> Wi-Fi<07:13:55.138> connections<07:13:55.620> but<07:13:55.860> also 07:13:56.150 --> 07:13:56.160 align:start position:0% those or Wi-Fi connections but also 07:13:56.160 --> 07:13:58.128 align:start position:0% those or Wi-Fi connections but also phones<07:13:56.820> and<07:13:57.058> so<07:13:57.180> on<07:13:57.298> so<07:13:57.540> there's<07:13:57.718> a<07:13:57.900> lot<07:13:58.020> of 07:13:58.128 --> 07:13:58.138 align:start position:0% phones and so on so there's a lot of 07:13:58.138 --> 07:14:00.530 align:start position:0% phones and so on so there's a lot of potential<07:13:58.620> for 07:14:00.530 --> 07:14:00.540 align:start position:0% potential for 07:14:00.540 --> 07:14:02.570 align:start position:0% potential for having<07:14:01.080> devices<07:14:01.500> on<07:14:01.860> the<07:14:01.978> same<07:14:02.100> frequency 07:14:02.570 --> 07:14:02.580 align:start position:0% having devices on the same frequency 07:14:02.580 --> 07:14:04.070 align:start position:0% having devices on the same frequency that<07:14:02.878> are<07:14:03.000> going<07:14:03.120> to<07:14:03.240> impede<07:14:03.718> its 07:14:04.070 --> 07:14:04.080 align:start position:0% that are going to impede its 07:14:04.080 --> 07:14:05.628 align:start position:0% that are going to impede its communication 07:14:05.628 --> 07:14:05.638 align:start position:0% communication 07:14:05.638 --> 07:14:07.368 align:start position:0% communication now<07:14:06.120> one<07:14:06.360> other<07:14:06.478> term<07:14:06.660> I<07:14:06.900> want<07:14:07.020> to<07:14:07.138> talk<07:14:07.260> about 07:14:07.368 --> 07:14:07.378 align:start position:0% now one other term I want to talk about 07:14:07.378 --> 07:14:10.670 align:start position:0% now one other term I want to talk about is<07:14:07.680> a<07:14:07.860> term<07:14:07.978> called<07:14:08.340> latency<07:14:09.080> this<07:14:10.080> is<07:14:10.260> we've 07:14:10.670 --> 07:14:10.680 align:start position:0% is a term called latency this is we've 07:14:10.680 --> 07:14:11.930 align:start position:0% is a term called latency this is we've mentioned<07:14:10.978> it<07:14:11.100> a<07:14:11.280> couple<07:14:11.340> times<07:14:11.520> in<07:14:11.760> previous 07:14:11.930 --> 07:14:11.940 align:start position:0% mentioned it a couple times in previous 07:14:11.940 --> 07:14:13.730 align:start position:0% mentioned it a couple times in previous modules<07:14:12.540> but<07:14:12.718> I<07:14:12.840> haven't<07:14:12.958> really<07:14:13.138> defined<07:14:13.558> it 07:14:13.730 --> 07:14:13.740 align:start position:0% modules but I haven't really defined it 07:14:13.740 --> 07:14:16.610 align:start position:0% modules but I haven't really defined it latency<07:14:14.580> is<07:14:14.940> basically<07:14:15.240> the<07:14:15.540> time<07:14:15.780> delay<07:14:16.260> in<07:14:16.440> a 07:14:16.610 --> 07:14:16.620 align:start position:0% latency is basically the time delay in a 07:14:16.620 --> 07:14:18.410 align:start position:0% latency is basically the time delay in a given<07:14:16.920> system<07:14:17.160> depending<07:14:18.058> on<07:14:18.120> what<07:14:18.240> system 07:14:18.410 --> 07:14:18.420 align:start position:0% given system depending on what system 07:14:18.420 --> 07:14:20.030 align:start position:0% given system depending on what system you're<07:14:18.718> measuring<07:14:19.080> it<07:14:19.260> might<07:14:19.440> mean<07:14:19.620> slightly 07:14:20.030 --> 07:14:20.040 align:start position:0% you're measuring it might mean slightly 07:14:20.040 --> 07:14:21.708 align:start position:0% you're measuring it might mean slightly different<07:14:20.160> things<07:14:20.520> so<07:14:21.120> the<07:14:21.298> system<07:14:21.420> we're 07:14:21.708 --> 07:14:21.718 align:start position:0% different things so the system we're 07:14:21.718 --> 07:14:23.090 align:start position:0% different things so the system we're most<07:14:21.958> concerned<07:14:22.320> with<07:14:22.440> is<07:14:22.680> the<07:14:22.920> network 07:14:23.090 --> 07:14:23.100 align:start position:0% most concerned with is the network 07:14:23.100 --> 07:14:25.310 align:start position:0% most concerned with is the network latency<07:14:23.700> which<07:14:24.360> can<07:14:24.478> be<07:14:24.660> measured<07:14:24.958> in<07:14:25.138> either 07:14:25.310 --> 07:14:25.320 align:start position:0% latency which can be measured in either 07:14:25.320 --> 07:14:28.850 align:start position:0% latency which can be measured in either one<07:14:25.798> way<07:14:26.040> or<07:14:26.638> round<07:14:27.000> trip<07:14:27.540> latency<07:14:28.440> and<07:14:28.680> I'm 07:14:28.850 --> 07:14:28.860 align:start position:0% one way or round trip latency and I'm 07:14:28.860 --> 07:14:30.170 align:start position:0% one way or round trip latency and I'm sure<07:14:29.040> that<07:14:29.280> you<07:14:29.400> can<07:14:29.520> understand<07:14:29.700> the 07:14:30.170 --> 07:14:30.180 align:start position:0% sure that you can understand the 07:14:30.180 --> 07:14:32.150 align:start position:0% sure that you can understand the difference<07:14:30.360> there 07:14:32.150 --> 07:14:32.160 align:start position:0% difference there 07:14:32.160 --> 07:14:34.190 align:start position:0% difference there the<07:14:32.820> latency<07:14:33.180> is<07:14:33.360> the<07:14:33.540> amount<07:14:33.718> of<07:14:33.840> time<07:14:33.958> it 07:14:34.190 --> 07:14:34.200 align:start position:0% the latency is the amount of time it 07:14:34.200 --> 07:14:35.990 align:start position:0% the latency is the amount of time it takes<07:14:34.320> for<07:14:34.500> data<07:14:34.860> to<07:14:35.040> go<07:14:35.218> from<07:14:35.458> a<07:14:35.580> source<07:14:35.878> to 07:14:35.990 --> 07:14:36.000 align:start position:0% takes for data to go from a source to 07:14:36.000 --> 07:14:38.150 align:start position:0% takes for data to go from a source to destination<07:14:36.540> and<07:14:37.378> we're<07:14:37.500> just<07:14:37.680> dealing<07:14:38.040> with 07:14:38.150 --> 07:14:38.160 align:start position:0% destination and we're just dealing with 07:14:38.160 --> 07:14:39.830 align:start position:0% destination and we're just dealing with bat<07:14:38.700> round<07:14:39.058> trip 07:14:39.830 --> 07:14:39.840 align:start position:0% bat round trip 07:14:39.840 --> 07:14:42.530 align:start position:0% bat round trip it<07:14:40.320> coming<07:14:40.500> back<07:14:40.798> as<07:14:41.100> well<07:14:41.280> so<07:14:42.058> the<07:14:42.180> round<07:14:42.298> trip 07:14:42.530 --> 07:14:42.540 align:start position:0% it coming back as well so the round trip 07:14:42.540 --> 07:14:45.830 align:start position:0% it coming back as well so the round trip adds<07:14:43.200> the<07:14:43.920> two<07:14:44.100> one-way<07:14:44.638> totals 07:14:45.830 --> 07:14:45.840 align:start position:0% adds the two one-way totals 07:14:45.840 --> 07:14:48.048 align:start position:0% adds the two one-way totals and<07:14:46.260> doesn't<07:14:46.440> include<07:14:46.920> the<07:14:47.280> processing<07:14:47.878> time 07:14:48.048 --> 07:14:48.058 align:start position:0% and doesn't include the processing time 07:14:48.058 --> 07:14:50.090 align:start position:0% and doesn't include the processing time of<07:14:48.298> the<07:14:48.420> packet<07:14:48.840> so<07:14:49.260> only<07:14:49.378> because<07:14:49.680> it's<07:14:49.920> sent 07:14:50.090 --> 07:14:50.100 align:start position:0% of the packet so only because it's sent 07:14:50.100 --> 07:14:51.410 align:start position:0% of the packet so only because it's sent and<07:14:50.340> then<07:14:50.458> takes<07:14:50.638> a<07:14:50.820> certain<07:14:50.940> amount<07:14:51.058> of<07:14:51.298> time 07:14:51.410 --> 07:14:51.420 align:start position:0% and then takes a certain amount of time 07:14:51.420 --> 07:14:53.270 align:start position:0% and then takes a certain amount of time to<07:14:51.900> come<07:14:52.020> back<07:14:52.138> doesn't<07:14:52.378> mean<07:14:52.620> that<07:14:52.740> is<07:14:53.040> all 07:14:53.270 --> 07:14:53.280 align:start position:0% to come back doesn't mean that is all 07:14:53.280 --> 07:14:55.368 align:start position:0% to come back doesn't mean that is all latency<07:14:53.700> because<07:14:54.180> some<07:14:54.478> of<07:14:54.600> that<07:14:54.718> is<07:14:55.020> how<07:14:55.260> much 07:14:55.368 --> 07:14:55.378 align:start position:0% latency because some of that is how much 07:14:55.378 --> 07:14:57.650 align:start position:0% latency because some of that is how much time<07:14:55.620> the<07:14:55.920> computer<07:14:56.100> is<07:14:56.458> spending<07:14:56.820> processing 07:14:57.650 --> 07:14:57.660 align:start position:0% time the computer is spending processing 07:14:57.660 --> 07:14:59.448 align:start position:0% time the computer is spending processing that<07:14:58.260> information 07:14:59.448 --> 07:14:59.458 align:start position:0% that information 07:14:59.458 --> 07:15:04.310 align:start position:0% that information obviously<07:15:00.298> we<07:15:00.600> want<07:15:00.840> lower<07:15:01.378> latency 07:15:04.310 --> 07:15:04.320 align:start position:0% 07:15:04.320 --> 07:15:06.770 align:start position:0% and<07:15:04.920> to<07:15:05.100> measure<07:15:05.340> it<07:15:05.458> we<07:15:05.700> can<07:15:05.878> generally<07:15:06.298> use 07:15:06.770 --> 07:15:06.780 align:start position:0% and to measure it we can generally use 07:15:06.780 --> 07:15:08.990 align:start position:0% and to measure it we can generally use the<07:15:07.558> Ping<07:15:07.798> utility<07:15:08.160> which<07:15:08.520> is<07:15:08.638> going<07:15:08.820> to<07:15:08.878> tell 07:15:08.990 --> 07:15:09.000 align:start position:0% the Ping utility which is going to tell 07:15:09.000 --> 07:15:12.170 align:start position:0% the Ping utility which is going to tell us<07:15:09.180> in<07:15:09.478> milliseconds<07:15:10.080> how<07:15:10.440> long<07:15:10.680> a<07:15:11.638> packet 07:15:12.170 --> 07:15:12.180 align:start position:0% us in milliseconds how long a packet 07:15:12.180 --> 07:15:14.270 align:start position:0% us in milliseconds how long a packet took<07:15:12.420> to<07:15:12.540> go<07:15:12.718> there<07:15:12.900> and<07:15:13.080> come<07:15:13.260> back 07:15:14.270 --> 07:15:14.280 align:start position:0% took to go there and come back 07:15:14.280 --> 07:15:16.430 align:start position:0% took to go there and come back now<07:15:14.638> let's<07:15:14.760> look<07:15:14.940> at<07:15:15.058> some<07:15:15.180> of<07:15:15.298> the<07:15:15.420> 802<07:15:16.020> 11 07:15:16.430 --> 07:15:16.440 align:start position:0% now let's look at some of the 802 11 07:15:16.440 --> 07:15:18.770 align:start position:0% now let's look at some of the 802 11 standards<07:15:17.100> and<07:15:17.400> see<07:15:17.580> which<07:15:17.940> specifications 07:15:18.770 --> 07:15:18.780 align:start position:0% standards and see which specifications 07:15:18.780 --> 07:15:21.048 align:start position:0% standards and see which specifications have<07:15:19.200> the<07:15:19.378> least<07:15:19.558> amount<07:15:19.920> of<07:15:20.040> latency<07:15:20.400> so 07:15:21.048 --> 07:15:21.058 align:start position:0% have the least amount of latency so 07:15:21.058 --> 07:15:24.110 align:start position:0% have the least amount of latency so these<07:15:21.360> 802<07:15:21.780> 11<07:15:21.958> standards<07:15:22.680> cover<07:15:23.218> the<07:15:23.638> proper 07:15:24.110 --> 07:15:24.120 align:start position:0% these 802 11 standards cover the proper 07:15:24.120 --> 07:15:26.330 align:start position:0% these 802 11 standards cover the proper implementation<07:15:24.780> setup<07:15:25.680> and<07:15:25.860> performance 07:15:26.330 --> 07:15:26.340 align:start position:0% implementation setup and performance 07:15:26.340 --> 07:15:29.390 align:start position:0% implementation setup and performance minimums<07:15:27.000> and<07:15:27.718> device<07:15:27.958> specifications<07:15:28.798> for 07:15:29.390 --> 07:15:29.400 align:start position:0% minimums and device specifications for 07:15:29.400 --> 07:15:32.270 align:start position:0% minimums and device specifications for wireless<07:15:30.120> local<07:15:30.540> area<07:15:30.840> networks<07:15:31.500> these<07:15:32.160> all 07:15:32.270 --> 07:15:32.280 align:start position:0% wireless local area networks these all 07:15:32.280 --> 07:15:34.910 align:start position:0% wireless local area networks these all fall<07:15:32.458> under<07:15:32.638> the<07:15:32.820> 802.11<07:15:33.478> specifications 07:15:34.910 --> 07:15:34.920 align:start position:0% fall under the 802.11 specifications 07:15:34.920 --> 07:15:38.270 align:start position:0% fall under the 802.11 specifications they<07:15:35.458> also<07:15:35.820> specify<07:15:36.620> the<07:15:37.620> method<07:15:37.920> for<07:15:38.100> which 07:15:38.270 --> 07:15:38.280 align:start position:0% they also specify the method for which 07:15:38.280 --> 07:15:41.990 align:start position:0% they also specify the method for which those<07:15:38.638> wireless<07:15:38.820> networks<07:15:40.138> as<07:15:40.978> carrier<07:15:41.638> sense 07:15:41.990 --> 07:15:42.000 align:start position:0% those wireless networks as carrier sense 07:15:42.000 --> 07:15:47.270 align:start position:0% those wireless networks as carrier sense multiple<07:15:42.840> access<07:15:43.080> with<07:15:43.798> collision<07:15:44.218> avoidance 07:15:47.270 --> 07:15:47.280 align:start position:0% 07:15:47.280 --> 07:15:51.170 align:start position:0% or<07:15:48.120> csma<07:15:48.780> CA<07:15:49.440> which<07:15:49.680> we've<07:15:49.920> talked<07:15:50.218> about 07:15:51.170 --> 07:15:51.180 align:start position:0% or csma CA which we've talked about 07:15:51.180 --> 07:15:53.270 align:start position:0% or csma CA which we've talked about are<07:15:51.600> going<07:15:51.718> to<07:15:51.900> operate 07:15:53.270 --> 07:15:53.280 align:start position:0% are going to operate 07:15:53.280 --> 07:15:56.208 align:start position:0% are going to operate and<07:15:53.820> it<07:15:54.000> also<07:15:54.240> designates<07:15:54.718> the<07:15:55.080> 2.4<07:15:55.740> gigahertz 07:15:56.208 --> 07:15:56.218 align:start position:0% and it also designates the 2.4 gigahertz 07:15:56.218 --> 07:15:58.010 align:start position:0% and it also designates the 2.4 gigahertz frequency 07:15:58.010 --> 07:15:58.020 align:start position:0% frequency 07:15:58.020 --> 07:16:00.830 align:start position:0% frequency as<07:15:58.500> the<07:15:58.798> band<07:15:58.978> for<07:15:59.400> the<07:15:59.638> sped<07:16:00.000> Spectrum 07:16:00.830 --> 07:16:00.840 align:start position:0% as the band for the sped Spectrum 07:16:00.840 --> 07:16:02.868 align:start position:0% as the band for the sped Spectrum devices<07:16:01.378> that<07:16:01.920> are<07:16:01.978> going<07:16:02.100> to<07:16:02.218> utilize<07:16:02.580> for 07:16:02.868 --> 07:16:02.878 align:start position:0% devices that are going to utilize for 07:16:02.878 --> 07:16:04.788 align:start position:0% devices that are going to utilize for reliability<07:16:03.478> now<07:16:04.260> over<07:16:04.378> the<07:16:04.558> years<07:16:04.620> there 07:16:04.788 --> 07:16:04.798 align:start position:0% reliability now over the years there 07:16:04.798 --> 07:16:06.170 align:start position:0% reliability now over the years there have<07:16:04.978> been<07:16:05.100> several<07:16:05.458> standards<07:16:05.878> in<07:16:06.000> this 07:16:06.170 --> 07:16:06.180 align:start position:0% have been several standards in this 07:16:06.180 --> 07:16:08.030 align:start position:0% have been several standards in this family<07:16:06.360> that<07:16:06.600> have<07:16:06.780> been<07:16:06.900> ratified<07:16:07.320> the 07:16:08.030 --> 07:16:08.040 align:start position:0% family that have been ratified the 07:16:08.040 --> 07:16:10.968 align:start position:0% family that have been ratified the original<07:16:08.160> was<07:16:08.580> 802.11<07:16:09.420> just<07:16:09.840> plain<07:16:10.200> old<07:16:10.378> it 07:16:10.968 --> 07:16:10.978 align:start position:0% original was 802.11 just plain old it 07:16:10.978 --> 07:16:14.570 align:start position:0% original was 802.11 just plain old it was<07:16:11.100> named<07:16:11.400> for<07:16:11.580> its<07:16:11.878> release<07:16:12.120> in<07:16:13.020> 1997<07:16:13.978> so<07:16:14.400> the 07:16:14.570 --> 07:16:14.580 align:start position:0% was named for its release in 1997 so the 07:16:14.580 --> 07:16:17.270 align:start position:0% was named for its release in 1997 so the 1997<07:16:15.180> is<07:16:15.478> part<07:16:15.780> of<07:16:15.958> that<07:16:16.200> and<07:16:17.040> it<07:16:17.160> was 07:16:17.270 --> 07:16:17.280 align:start position:0% 1997 is part of that and it was 07:16:17.280 --> 07:16:19.490 align:start position:0% 1997 is part of that and it was specified<07:16:17.638> to<07:16:17.940> operate<07:16:18.298> the<07:16:18.540> 2.4<07:16:19.080> gigahertz 07:16:19.490 --> 07:16:19.500 align:start position:0% specified to operate the 2.4 gigahertz 07:16:19.500 --> 07:16:21.948 align:start position:0% specified to operate the 2.4 gigahertz frequency<07:16:19.978> band<07:16:20.340> and<07:16:20.940> was<07:16:21.058> rated<07:16:21.360> for<07:16:21.600> data 07:16:21.948 --> 07:16:21.958 align:start position:0% frequency band and was rated for data 07:16:21.958 --> 07:16:23.990 align:start position:0% frequency band and was rated for data bits<07:16:22.260> at<07:16:22.440> about<07:16:22.620> 2<07:16:22.978> megabits<07:16:23.580> per<07:16:23.760> second 07:16:23.990 --> 07:16:24.000 align:start position:0% bits at about 2 megabits per second 07:16:24.000 --> 07:16:26.330 align:start position:0% bits at about 2 megabits per second which<07:16:24.660> as<07:16:24.780> you<07:16:24.958> imagine<07:16:25.138> would<07:16:25.860> not<07:16:25.978> be<07:16:26.160> very 07:16:26.330 --> 07:16:26.340 align:start position:0% which as you imagine would not be very 07:16:26.340 --> 07:16:28.310 align:start position:0% which as you imagine would not be very useful<07:16:26.638> for<07:16:26.878> us<07:16:27.000> now<07:16:27.298> and<07:16:27.660> therefore<07:16:27.900> it<07:16:28.138> is 07:16:28.310 --> 07:16:28.320 align:start position:0% useful for us now and therefore it is 07:16:28.320 --> 07:16:30.590 align:start position:0% useful for us now and therefore it is very<07:16:28.558> obsolete<07:16:29.340> at<07:16:29.458> this<07:16:29.580> point 07:16:30.590 --> 07:16:30.600 align:start position:0% very obsolete at this point 07:16:30.600 --> 07:16:33.708 align:start position:0% very obsolete at this point the<07:16:31.260> 802<07:16:31.920> a<07:16:32.520> standard<07:16:33.000> which<07:16:33.180> was<07:16:33.298> released 07:16:33.708 --> 07:16:33.718 align:start position:0% the 802 a standard which was released 07:16:33.718 --> 07:16:36.048 align:start position:0% the 802 a standard which was released two<07:16:33.958> years<07:16:34.200> later<07:16:34.500> was<07:16:35.218> designed<07:16:35.580> to<07:16:35.700> operate 07:16:36.048 --> 07:16:36.058 align:start position:0% two years later was designed to operate 07:16:36.058 --> 07:16:39.170 align:start position:0% two years later was designed to operate at<07:16:36.298> the<07:16:36.478> 5<07:16:36.660> gigahertz<07:16:37.200> band<07:16:37.500> and<07:16:38.340> it<07:16:38.458> had<07:16:38.638> a<07:16:38.820> 54 07:16:39.170 --> 07:16:39.180 align:start position:0% at the 5 gigahertz band and it had a 54 07:16:39.180 --> 07:16:41.330 align:start position:0% at the 5 gigahertz band and it had a 54 megabit<07:16:39.718> data<07:16:40.260> rate<07:16:40.378> now<07:16:40.920> while<07:16:41.040> it<07:16:41.218> would 07:16:41.330 --> 07:16:41.340 align:start position:0% megabit data rate now while it would 07:16:41.340 --> 07:16:42.708 align:start position:0% megabit data rate now while it would seem<07:16:41.520> that<07:16:41.700> this<07:16:41.940> standard<07:16:42.240> would<07:16:42.420> sort<07:16:42.600> of 07:16:42.708 --> 07:16:42.718 align:start position:0% seem that this standard would sort of 07:16:42.718 --> 07:16:44.810 align:start position:0% seem that this standard would sort of lead<07:16:42.900> the<07:16:43.200> charge<07:16:43.378> in<07:16:43.620> Wireless<07:16:43.798> standards<07:16:44.400> at 07:16:44.810 --> 07:16:44.820 align:start position:0% lead the charge in Wireless standards at 07:16:44.820 --> 07:16:47.030 align:start position:0% lead the charge in Wireless standards at the<07:16:45.000> same<07:16:45.120> time<07:16:45.360> that<07:16:45.600> 802a<07:16:46.440> was<07:16:46.740> released 07:16:47.030 --> 07:16:47.040 align:start position:0% the same time that 802a was released 07:16:47.040 --> 07:16:49.610 align:start position:0% the same time that 802a was released there<07:16:47.218> was<07:16:47.400> also<07:16:47.638> 802<07:16:48.240> B<07:16:48.660> which<07:16:49.020> was<07:16:49.200> released 07:16:49.610 --> 07:16:49.620 align:start position:0% there was also 802 B which was released 07:16:49.620 --> 07:16:53.030 align:start position:0% there was also 802 B which was released and<07:16:50.040> 802b<07:16:50.760> operates<07:16:51.298> at<07:16:51.600> the<07:16:51.780> 2.4<07:16:52.500> gigahertz 07:16:53.030 --> 07:16:53.040 align:start position:0% and 802b operates at the 2.4 gigahertz 07:16:53.040 --> 07:16:55.368 align:start position:0% and 802b operates at the 2.4 gigahertz band<07:16:53.340> and<07:16:54.298> essentially<07:16:54.660> was<07:16:54.958> a<07:16:55.260> direct 07:16:55.368 --> 07:16:55.378 align:start position:0% band and essentially was a direct 07:16:55.378 --> 07:16:57.670 align:start position:0% band and essentially was a direct extension<07:16:56.100> of<07:16:56.400> the<07:16:56.700> original 07:16:57.670 --> 07:16:57.680 align:start position:0% extension of the original 07:16:57.680 --> 07:17:01.610 align:start position:0% extension of the original 802.11<07:16:58.760> 1997<07:16:59.760> standard<07:17:00.420> now<07:17:01.138> even<07:17:01.320> though<07:17:01.440> the 07:17:01.610 --> 07:17:01.620 align:start position:0% 802.11 1997 standard now even though the 07:17:01.620 --> 07:17:04.490 align:start position:0% 802.11 1997 standard now even though the data<07:17:01.920> rate<07:17:01.978> was<07:17:02.218> faster<07:17:02.458> with<07:17:02.958> 802.11a<07:17:03.958> there 07:17:04.490 --> 07:17:04.500 align:start position:0% data rate was faster with 802.11a there 07:17:04.500 --> 07:17:06.230 align:start position:0% data rate was faster with 802.11a there were<07:17:04.620> some<07:17:04.798> initial<07:17:05.100> downsides<07:17:05.878> to<07:17:06.058> that 07:17:06.230 --> 07:17:06.240 align:start position:0% were some initial downsides to that 07:17:06.240 --> 07:17:07.610 align:start position:0% were some initial downsides to that standard<07:17:06.600> that<07:17:06.718> kept<07:17:06.958> it<07:17:07.080> from<07:17:07.200> being<07:17:07.378> the 07:17:07.610 --> 07:17:07.620 align:start position:0% standard that kept it from being the 07:17:07.620 --> 07:17:08.868 align:start position:0% standard that kept it from being the most<07:17:07.740> popular 07:17:08.868 --> 07:17:08.878 align:start position:0% most popular 07:17:08.878 --> 07:17:12.890 align:start position:0% most popular first<07:17:09.540> this<07:17:10.080> higher<07:17:10.558> frequency<07:17:11.240> uh<07:17:12.240> had<07:17:12.600> a 07:17:12.890 --> 07:17:12.900 align:start position:0% first this higher frequency uh had a 07:17:12.900 --> 07:17:15.350 align:start position:0% first this higher frequency uh had a lesser<07:17:13.860> range<07:17:14.218> and<07:17:14.520> so<07:17:14.700> you<07:17:14.878> could<07:17:15.000> travel 07:17:15.350 --> 07:17:15.360 align:start position:0% lesser range and so you could travel 07:17:15.360 --> 07:17:19.430 align:start position:0% lesser range and so you could travel travel<07:17:16.080> less<07:17:16.500> distance 07:17:19.430 --> 07:17:19.440 align:start position:0% 07:17:19.440 --> 07:17:22.968 align:start position:0% also<07:17:20.040> when<07:17:20.298> 802.11b<07:17:21.298> came<07:17:21.718> out<07:17:21.840> it<07:17:22.200> was<07:17:22.320> a<07:17:22.860> lot 07:17:22.968 --> 07:17:22.978 align:start position:0% also when 802.11b came out it was a lot 07:17:22.978 --> 07:17:24.530 align:start position:0% also when 802.11b came out it was a lot cheaper 07:17:24.530 --> 07:17:24.540 align:start position:0% cheaper 07:17:24.540 --> 07:17:28.548 align:start position:0% cheaper than<07:17:24.978> 802.11a<07:17:25.978> and<07:17:26.820> that<07:17:27.000> made<07:17:27.180> up<07:17:27.360> quickly<07:17:27.780> uh 07:17:28.548 --> 07:17:28.558 align:start position:0% than 802.11a and that made up quickly uh 07:17:28.558 --> 07:17:30.890 align:start position:0% than 802.11a and that made up quickly uh with<07:17:29.280> consumers<07:17:29.760> and<07:17:30.000> so<07:17:30.120> it<07:17:30.298> quickly<07:17:30.600> became 07:17:30.890 --> 07:17:30.900 align:start position:0% with consumers and so it quickly became 07:17:30.900 --> 07:17:33.410 align:start position:0% with consumers and so it quickly became the<07:17:31.200> de<07:17:31.320> facto<07:17:31.740> standard<07:17:32.218> now<07:17:32.638> it's<07:17:32.820> popularly 07:17:33.410 --> 07:17:33.420 align:start position:0% the de facto standard now it's popularly 07:17:33.420 --> 07:17:35.810 align:start position:0% the de facto standard now it's popularly grew<07:17:34.320> rapidly<07:17:34.740> and<07:17:35.040> though<07:17:35.218> it<07:17:35.340> operated<07:17:35.638> at 07:17:35.810 --> 07:17:35.820 align:start position:0% grew rapidly and though it operated at 07:17:35.820 --> 07:17:38.150 align:start position:0% grew rapidly and though it operated at 2.4<07:17:36.298> gigahertz<07:17:36.780> and<07:17:37.080> therefore<07:17:37.378> was<07:17:37.620> open<07:17:37.860> to 07:17:38.150 --> 07:17:38.160 align:start position:0% 2.4 gigahertz and therefore was open to 07:17:38.160 --> 07:17:41.330 align:start position:0% 2.4 gigahertz and therefore was open to uh<07:17:38.520> you<07:17:38.820> know<07:17:38.878> was<07:17:39.058> really<07:17:39.360> susceptible 07:17:41.330 --> 07:17:41.340 align:start position:0% uh you know was really susceptible 07:17:41.340 --> 07:17:44.930 align:start position:0% uh you know was really susceptible to<07:17:42.058> a<07:17:42.298> lot<07:17:42.420> of<07:17:42.540> interference<07:17:43.378> uh<07:17:44.280> it<07:17:44.520> still<07:17:44.760> was 07:17:44.930 --> 07:17:44.940 align:start position:0% to a lot of interference uh it still was 07:17:44.940 --> 07:17:47.868 align:start position:0% to a lot of interference uh it still was the<07:17:45.180> one<07:17:45.298> that<07:17:45.600> almost<07:17:45.840> everyone<07:17:46.260> used<07:17:46.740> uh<07:17:47.700> and 07:17:47.868 --> 07:17:47.878 align:start position:0% the one that almost everyone used uh and 07:17:47.878 --> 07:17:49.910 align:start position:0% the one that almost everyone used uh and so<07:17:48.120> that's<07:17:48.540> sort<07:17:48.958> of<07:17:49.020> where<07:17:49.260> it<07:17:49.378> went<07:17:49.558> because 07:17:49.910 --> 07:17:49.920 align:start position:0% so that's sort of where it went because 07:17:49.920 --> 07:17:52.010 align:start position:0% so that's sort of where it went because range 07:17:52.010 --> 07:17:52.020 align:start position:0% range 07:17:52.020 --> 07:17:54.650 align:start position:0% range was<07:17:52.500> such<07:17:52.680> a<07:17:52.798> big<07:17:52.920> deal<07:17:53.160> the<07:17:54.120> next<07:17:54.298> standard 07:17:54.650 --> 07:17:54.660 align:start position:0% was such a big deal the next standard 07:17:54.660 --> 07:17:57.590 align:start position:0% was such a big deal the next standard which<07:17:54.780> was<07:17:54.958> released<07:17:55.260> in<07:17:55.440> 2003<07:17:56.160> was<07:17:56.940> the<07:17:57.120> 802 07:17:57.590 --> 07:17:57.600 align:start position:0% which was released in 2003 was the 802 07:17:57.600 --> 07:18:00.530 align:start position:0% which was released in 2003 was the 802 11g<07:17:58.378> standard<07:17:58.920> and<07:17:59.400> this<07:17:59.580> specification<07:18:00.240> used 07:18:00.530 --> 07:18:00.540 align:start position:0% 11g standard and this specification used 07:18:00.540 --> 07:18:03.410 align:start position:0% 11g standard and this specification used the<07:18:00.840> 2.4<07:18:01.440> gigahertz<07:18:02.040> frequency<07:18:02.520> again 07:18:03.410 --> 07:18:03.420 align:start position:0% the 2.4 gigahertz frequency again 07:18:03.420 --> 07:18:05.570 align:start position:0% the 2.4 gigahertz frequency again but<07:18:03.840> the<07:18:03.958> data<07:18:04.260> rates<07:18:04.440> took<07:18:04.740> a<07:18:04.860> major<07:18:04.978> leap<07:18:05.340> up 07:18:05.570 --> 07:18:05.580 align:start position:0% but the data rates took a major leap up 07:18:05.580 --> 07:18:07.690 align:start position:0% but the data rates took a major leap up to<07:18:05.700> 54<07:18:06.120> megabits<07:18:06.660> per<07:18:06.840> second<07:18:07.020> just<07:18:07.378> like 07:18:07.690 --> 07:18:07.700 align:start position:0% to 54 megabits per second just like 07:18:07.700 --> 07:18:10.968 align:start position:0% to 54 megabits per second just like 802.11a<07:18:08.700> now<07:18:09.298> since<07:18:09.540> it<07:18:09.840> used<07:18:10.020> the<07:18:10.200> 2.4<07:18:10.740> band 07:18:10.968 --> 07:18:10.978 align:start position:0% 802.11a now since it used the 2.4 band 07:18:10.978 --> 07:18:13.390 align:start position:0% 802.11a now since it used the 2.4 band it<07:18:11.280> made<07:18:11.520> backwards<07:18:12.298> compatible<07:18:12.840> with 07:18:13.390 --> 07:18:13.400 align:start position:0% it made backwards compatible with 07:18:13.400 --> 07:18:16.910 align:start position:0% it made backwards compatible with 802.11b<07:18:14.400> so<07:18:14.760> it<07:18:14.878> was<07:18:15.000> very<07:18:15.360> easy<07:18:15.780> to<07:18:16.440> integrate 07:18:16.910 --> 07:18:16.920 align:start position:0% 802.11b so it was very easy to integrate 07:18:16.920 --> 07:18:18.830 align:start position:0% 802.11b so it was very easy to integrate and<07:18:17.458> it<07:18:17.638> therefore<07:18:17.940> became<07:18:18.240> the<07:18:18.420> preferred 07:18:18.830 --> 07:18:18.840 align:start position:0% and it therefore became the preferred 07:18:18.840 --> 07:18:21.830 align:start position:0% and it therefore became the preferred standard<07:18:19.260> now<07:18:19.860> after<07:18:20.120> 80211g<07:18:21.120> took<07:18:21.540> over<07:18:21.660> the 07:18:21.830 --> 07:18:21.840 align:start position:0% standard now after 80211g took over the 07:18:21.840 --> 07:18:24.288 align:start position:0% standard now after 80211g took over the market<07:18:22.020> it<07:18:22.320> wasn't<07:18:22.500> until<07:18:22.878> 2009<07:18:23.878> that<07:18:24.120> we 07:18:24.288 --> 07:18:24.298 align:start position:0% market it wasn't until 2009 that we 07:18:24.298 --> 07:18:27.590 align:start position:0% market it wasn't until 2009 that we finally<07:18:24.600> got<07:18:24.780> the<07:18:24.900> 802.11<07:18:25.798> N<07:18:26.340> standard<07:18:26.878> and<07:18:27.478> it 07:18:27.590 --> 07:18:27.600 align:start position:0% finally got the 802.11 N standard and it 07:18:27.600 --> 07:18:30.230 align:start position:0% finally got the 802.11 N standard and it was<07:18:27.780> released<07:18:28.260> with<07:18:28.860> something<07:18:29.100> called<07:18:29.580> a 07:18:30.230 --> 07:18:30.240 align:start position:0% was released with something called a 07:18:30.240 --> 07:18:31.788 align:start position:0% was released with something called a memo 07:18:31.788 --> 07:18:31.798 align:start position:0% memo 07:18:31.798 --> 07:18:33.948 align:start position:0% memo which<07:18:32.160> was<07:18:32.340> a<07:18:32.520> type<07:18:32.638> of<07:18:32.820> antenna 07:18:33.948 --> 07:18:33.958 align:start position:0% which was a type of antenna 07:18:33.958 --> 07:18:40.128 align:start position:0% which was a type of antenna or<07:18:34.798> multiple 07:18:40.128 --> 07:18:40.138 align:start position:0% 07:18:40.138 --> 07:18:44.750 align:start position:0% input 07:18:44.750 --> 07:18:44.760 align:start position:0% 07:18:44.760 --> 07:18:46.430 align:start position:0% multiple<07:18:45.540> output 07:18:46.430 --> 07:18:46.440 align:start position:0% multiple output 07:18:46.440 --> 07:18:48.590 align:start position:0% multiple output and<07:18:46.860> it<07:18:46.978> had<07:18:47.160> multiple<07:18:47.580> antennas<07:18:48.120> and<07:18:48.420> that 07:18:48.590 --> 07:18:48.600 align:start position:0% and it had multiple antennas and that 07:18:48.600 --> 07:18:50.530 align:start position:0% and it had multiple antennas and that greatly<07:18:48.958> improved<07:18:49.440> the<07:18:49.620> network<07:18:49.798> performance 07:18:50.530 --> 07:18:50.540 align:start position:0% greatly improved the network performance 07:18:50.540 --> 07:18:53.570 align:start position:0% greatly improved the network performance also<07:18:51.540> this<07:18:51.780> amendment<07:18:52.320> was<07:18:52.680> specified<07:18:53.100> for 07:18:53.570 --> 07:18:53.580 align:start position:0% also this amendment was specified for 07:18:53.580 --> 07:18:56.810 align:start position:0% also this amendment was specified for both<07:18:53.940> 2.4<07:18:54.660> gigahertz<07:18:55.138> and<07:18:55.558> 5<07:18:55.798> gigahertz<07:18:56.280> bands 07:18:56.810 --> 07:18:56.820 align:start position:0% both 2.4 gigahertz and 5 gigahertz bands 07:18:56.820 --> 07:18:58.730 align:start position:0% both 2.4 gigahertz and 5 gigahertz bands and<07:18:57.298> so<07:18:57.420> these<07:18:57.718> improvements<07:18:58.200> made<07:18:58.500> the 07:18:58.730 --> 07:18:58.740 align:start position:0% and so these improvements made the 07:18:58.740 --> 07:19:00.708 align:start position:0% and so these improvements made the standard<07:18:59.160> really<07:18:59.580> popular<07:18:59.878> especially 07:19:00.708 --> 07:19:00.718 align:start position:0% standard really popular especially 07:19:00.718 --> 07:19:02.930 align:start position:0% standard really popular especially because<07:19:00.840> it<07:19:01.080> was<07:19:01.200> backwards<07:19:01.740> compatible<07:19:02.218> not 07:19:02.930 --> 07:19:02.940 align:start position:0% because it was backwards compatible not 07:19:02.940 --> 07:19:07.788 align:start position:0% because it was backwards compatible not only<07:19:03.058> with<07:19:03.420> G<07:19:03.718> but<07:19:04.320> also<07:19:04.558> with<07:19:04.740> b<07:19:04.978> and<07:19:05.458> even<07:19:05.760> a 07:19:07.788 --> 07:19:07.798 align:start position:0% only with G but also with b and even a 07:19:07.798 --> 07:19:10.310 align:start position:0% only with G but also with b and even a and<07:19:08.520> it<07:19:08.638> was<07:19:08.760> rated<07:19:09.120> for<07:19:09.360> a<07:19:09.540> maximum<07:19:09.900> of<07:19:10.020> up<07:19:10.200> to 07:19:10.310 --> 07:19:10.320 align:start position:0% and it was rated for a maximum of up to 07:19:10.320 --> 07:19:13.968 align:start position:0% and it was rated for a maximum of up to 150<07:19:11.160> megabits<07:19:11.760> per<07:19:12.298> second<07:19:12.540> now<07:19:13.440> the<07:19:13.620> range<07:19:13.798> of 07:19:13.968 --> 07:19:13.978 align:start position:0% 150 megabits per second now the range of 07:19:13.978 --> 07:19:15.650 align:start position:0% 150 megabits per second now the range of these<07:19:14.218> Wireless<07:19:14.400> standards<07:19:15.058> is<07:19:15.298> also 07:19:15.650 --> 07:19:15.660 align:start position:0% these Wireless standards is also 07:19:15.660 --> 07:19:21.170 align:start position:0% these Wireless standards is also specified<07:19:16.080> the<07:19:16.860> original<07:19:17.040> 802<07:19:17.878> 11<07:19:18.860> 1997<07:19:19.878> and<07:19:20.878> a 07:19:21.170 --> 07:19:21.180 align:start position:0% specified the original 802 11 1997 and a 07:19:21.180 --> 07:19:24.170 align:start position:0% specified the original 802 11 1997 and a have<07:19:21.780> a<07:19:21.958> range<07:19:22.200> of<07:19:22.378> about 07:19:24.170 --> 07:19:24.180 align:start position:0% have a range of about 07:19:24.180 --> 07:19:28.968 align:start position:0% have a range of about 20<07:19:24.600> meters<07:19:25.280> B<07:19:26.280> and<07:19:26.520> G 07:19:28.968 --> 07:19:28.978 align:start position:0% 07:19:28.978 --> 07:19:31.490 align:start position:0% have<07:19:29.520> a<07:19:29.760> hundred<07:19:30.000> meters 07:19:31.490 --> 07:19:31.500 align:start position:0% have a hundred meters 07:19:31.500 --> 07:19:34.250 align:start position:0% have a hundred meters and<07:19:32.040> N<07:19:32.280> is<07:19:32.520> approximately<07:19:33.058> 70<07:19:33.478> meters<07:19:33.900> so<07:19:34.080> we 07:19:34.250 --> 07:19:34.260 align:start position:0% and N is approximately 70 meters so we 07:19:34.260 --> 07:19:36.350 align:start position:0% and N is approximately 70 meters so we lost<07:19:34.500> a<07:19:34.978> little<07:19:35.040> bit<07:19:35.218> of<07:19:35.400> distance<07:19:35.580> because<07:19:36.058> we 07:19:36.350 --> 07:19:36.360 align:start position:0% lost a little bit of distance because we 07:19:36.360 --> 07:19:39.288 align:start position:0% lost a little bit of distance because we added<07:19:36.600> that<07:19:36.718> five<07:19:36.900> gigahertz<07:19:37.320> band<07:19:37.680> in<07:19:37.978> but 07:19:39.288 --> 07:19:39.298 align:start position:0% added that five gigahertz band in but 07:19:39.298 --> 07:19:41.208 align:start position:0% added that five gigahertz band in but for<07:19:39.958> most<07:19:40.138> people<07:19:40.378> this<07:19:40.740> didn't<07:19:40.920> really 07:19:41.208 --> 07:19:41.218 align:start position:0% for most people this didn't really 07:19:41.218 --> 07:19:43.368 align:start position:0% for most people this didn't really matter<07:19:41.458> since<07:19:42.058> we<07:19:42.298> could<07:19:42.478> use<07:19:42.718> again<07:19:43.020> an 07:19:43.368 --> 07:19:43.378 align:start position:0% matter since we could use again an 07:19:43.378 --> 07:19:45.590 align:start position:0% matter since we could use again an extended<07:19:43.798> service<07:19:44.100> set<07:19:44.458> and<07:19:45.058> simply<07:19:45.298> add 07:19:45.590 --> 07:19:45.600 align:start position:0% extended service set and simply add 07:19:45.600 --> 07:19:47.868 align:start position:0% extended service set and simply add several<07:19:46.020> 80211<07:19:46.740> devices 07:19:47.868 --> 07:19:47.878 align:start position:0% several 80211 devices 07:19:47.878 --> 07:19:49.610 align:start position:0% several 80211 devices now<07:19:48.298> while<07:19:48.478> you<07:19:48.780> might<07:19:48.900> have<07:19:49.020> heard<07:19:49.200> of<07:19:49.440> some 07:19:49.610 --> 07:19:49.620 align:start position:0% now while you might have heard of some 07:19:49.620 --> 07:19:52.128 align:start position:0% now while you might have heard of some newer<07:19:50.040> standards<07:19:50.520> available<07:19:50.780> and<07:19:51.780> even<07:19:51.958> some 07:19:52.128 --> 07:19:52.138 align:start position:0% newer standards available and even some 07:19:52.138 --> 07:19:53.448 align:start position:0% newer standards available and even some that<07:19:52.320> are<07:19:52.500> just<07:19:52.620> coming<07:19:52.740> around<07:19:52.920> the<07:19:53.160> corner 07:19:53.448 --> 07:19:53.458 align:start position:0% that are just coming around the corner 07:19:53.458 --> 07:19:56.390 align:start position:0% that are just coming around the corner these<07:19:54.000> four<07:19:54.240> are<07:19:54.780> the<07:19:55.020> ones<07:19:55.260> you<07:19:55.920> really<07:19:56.100> need 07:19:56.390 --> 07:19:56.400 align:start position:0% these four are the ones you really need 07:19:56.400 --> 07:19:58.490 align:start position:0% these four are the ones you really need to<07:19:56.520> know<07:19:56.760> for<07:19:57.420> the<07:19:57.600> exam<07:19:57.900> and<07:19:58.080> so<07:19:58.200> those<07:19:58.320> are 07:19:58.490 --> 07:19:58.500 align:start position:0% to know for the exam and so those are 07:19:58.500 --> 07:20:02.930 align:start position:0% to know for the exam and so those are the<07:19:58.558> ones<07:19:58.680> I<07:19:58.798> really<07:19:58.920> want<07:19:59.160> to<07:19:59.280> concentrate<07:19:59.820> on 07:20:02.930 --> 07:20:02.940 align:start position:0% 07:20:02.940 --> 07:20:04.368 align:start position:0% so<07:20:03.180> if<07:20:03.360> we<07:20:03.420> look<07:20:03.540> at<07:20:03.660> these<07:20:03.840> in<07:20:03.958> a<07:20:04.138> little<07:20:04.260> more 07:20:04.368 --> 07:20:04.378 align:start position:0% so if we look at these in a little more 07:20:04.378 --> 07:20:06.650 align:start position:0% so if we look at these in a little more organized<07:20:04.920> Manner<07:20:05.340> and<07:20:05.700> we<07:20:05.878> can<07:20:06.000> recap<07:20:06.360> the 07:20:06.650 --> 07:20:06.660 align:start position:0% organized Manner and we can recap the 07:20:06.660 --> 07:20:10.250 align:start position:0% organized Manner and we can recap the important<07:20:07.020> parts<07:20:07.320> the<07:20:07.978> 802.11<07:20:08.760> standard<07:20:09.298> 1997 07:20:10.250 --> 07:20:10.260 align:start position:0% important parts the 802.11 standard 1997 07:20:10.260 --> 07:20:14.930 align:start position:0% important parts the 802.11 standard 1997 worked<07:20:11.040> on<07:20:11.160> a<07:20:11.340> 9<07:20:11.520> a<07:20:11.820> 2.4<07:20:12.860> frequency<07:20:13.860> had<07:20:14.760> a 07:20:14.930 --> 07:20:14.940 align:start position:0% worked on a 9 a 2.4 frequency had a 07:20:14.940 --> 07:20:16.968 align:start position:0% worked on a 9 a 2.4 frequency had a range<07:20:15.120> of<07:20:15.298> 20<07:20:15.660> meters 07:20:16.968 --> 07:20:16.978 align:start position:0% range of 20 meters 07:20:16.978 --> 07:20:19.310 align:start position:0% range of 20 meters and<07:20:17.400> had<07:20:17.638> a<07:20:17.820> two<07:20:17.878> megabit<07:20:18.360> per<07:20:18.600> second<07:20:18.780> data 07:20:19.310 --> 07:20:19.320 align:start position:0% and had a two megabit per second data 07:20:19.320 --> 07:20:20.030 align:start position:0% and had a two megabit per second data rate 07:20:20.030 --> 07:20:20.040 align:start position:0% rate 07:20:20.040 --> 07:20:23.990 align:start position:0% rate Ada<07:20:20.638> 211A<07:20:21.420> was<07:20:21.840> at<07:20:22.020> 5<07:20:22.200> gigahertz<07:20:22.680> 20<07:20:23.280> meters<07:20:23.760> in 07:20:23.990 --> 07:20:24.000 align:start position:0% Ada 211A was at 5 gigahertz 20 meters in 07:20:24.000 --> 07:20:27.730 align:start position:0% Ada 211A was at 5 gigahertz 20 meters in range<07:20:24.298> 54<07:20:25.138> megabits<07:20:25.740> it's<07:20:26.340> compatible<07:20:27.000> with 07:20:27.730 --> 07:20:27.740 align:start position:0% range 54 megabits it's compatible with 07:20:27.740 --> 07:20:32.030 align:start position:0% range 54 megabits it's compatible with 802.11n<07:20:29.180> 8211b<07:20:30.180> operated<07:20:30.780> at<07:20:30.958> 2.4<07:20:31.558> gigahertz 07:20:32.030 --> 07:20:32.040 align:start position:0% 802.11n 8211b operated at 2.4 gigahertz 07:20:32.040 --> 07:20:35.570 align:start position:0% 802.11n 8211b operated at 2.4 gigahertz had<07:20:32.760> a<07:20:32.940> 100<07:20:33.120> meter<07:20:33.660> range<07:20:34.080> 11<07:20:34.740> megabits<07:20:35.400> per 07:20:35.570 --> 07:20:35.580 align:start position:0% had a 100 meter range 11 megabits per 07:20:35.580 --> 07:20:38.570 align:start position:0% had a 100 meter range 11 megabits per second<07:20:35.760> and<07:20:36.478> is<07:20:36.660> compatible<07:20:37.080> with<07:20:37.260> G<07:20:37.558> and<07:20:37.798> n 07:20:38.570 --> 07:20:38.580 align:start position:0% second and is compatible with G and n 07:20:38.580 --> 07:20:42.170 align:start position:0% second and is compatible with G and n ative<07:20:39.000> to<07:20:39.240> 11g<07:20:39.780> also<07:20:40.378> 2.4<07:20:41.100> gigahertz<07:20:41.638> 100 07:20:42.170 --> 07:20:42.180 align:start position:0% ative to 11g also 2.4 gigahertz 100 07:20:42.180 --> 07:20:45.410 align:start position:0% ative to 11g also 2.4 gigahertz 100 meters<07:20:42.840> and<07:20:43.558> it<07:20:43.740> was<07:20:43.860> 54<07:20:44.520> megabits<07:20:45.120> per<07:20:45.240> second 07:20:45.410 --> 07:20:45.420 align:start position:0% meters and it was 54 megabits per second 07:20:45.420 --> 07:20:48.110 align:start position:0% meters and it was 54 megabits per second so<07:20:45.780> it's<07:20:45.900> increasing<07:20:46.320> the<07:20:46.500> top<07:20:46.680> the<07:20:46.920> speed 07:20:48.110 --> 07:20:48.120 align:start position:0% so it's increasing the top the speed 07:20:48.120 --> 07:20:50.990 align:start position:0% so it's increasing the top the speed and<07:20:48.718> was<07:20:49.020> compatible<07:20:49.500> with<07:20:49.978> the<07:20:50.280> previous<07:20:50.400> and 07:20:50.990 --> 07:20:51.000 align:start position:0% and was compatible with the previous and 07:20:51.000 --> 07:20:54.288 align:start position:0% and was compatible with the previous and the<07:20:51.180> next<07:20:51.360> one<07:20:51.600> which<07:20:52.260> is<07:20:52.520> 802.11n<07:20:53.520> which<07:20:54.120> not 07:20:54.288 --> 07:20:54.298 align:start position:0% the next one which is 802.11n which not 07:20:54.298 --> 07:20:57.170 align:start position:0% the next one which is 802.11n which not only<07:20:54.478> operates<07:20:54.900> at<07:20:55.138> 2.4<07:20:55.680> gigahertz<07:20:56.160> but<07:20:56.820> also 07:20:57.170 --> 07:20:57.180 align:start position:0% only operates at 2.4 gigahertz but also 07:20:57.180 --> 07:20:58.490 align:start position:0% only operates at 2.4 gigahertz but also five 07:20:58.490 --> 07:20:58.500 align:start position:0% five 07:20:58.500 --> 07:21:01.490 align:start position:0% five has<07:20:59.040> a<07:20:59.280> slightly<07:20:59.520> less<07:20:59.820> range<07:21:00.298> but<07:21:00.958> it<07:21:01.320> does 07:21:01.490 --> 07:21:01.500 align:start position:0% has a slightly less range but it does 07:21:01.500 --> 07:21:03.890 align:start position:0% has a slightly less range but it does have<07:21:01.680> a<07:21:01.860> higher<07:21:02.100> megabit<07:21:02.520> per<07:21:02.700> second<07:21:02.940> data 07:21:03.890 --> 07:21:03.900 align:start position:0% have a higher megabit per second data 07:21:03.900 --> 07:21:05.448 align:start position:0% have a higher megabit per second data rate<07:21:04.020> some<07:21:04.500> would<07:21:04.740> even<07:21:04.860> claim<07:21:05.218> that<07:21:05.340> this 07:21:05.448 --> 07:21:05.458 align:start position:0% rate some would even claim that this 07:21:05.458 --> 07:21:07.250 align:start position:0% rate some would even claim that this goes<07:21:05.760> up<07:21:05.820> to<07:21:06.058> 600<07:21:06.478> depending<07:21:06.958> on<07:21:07.080> your 07:21:07.250 --> 07:21:07.260 align:start position:0% goes up to 600 depending on your 07:21:07.260 --> 07:21:10.548 align:start position:0% goes up to 600 depending on your theoretical<07:21:07.760> and<07:21:08.760> it's<07:21:08.940> compatible<07:21:09.540> with<07:21:10.260> all 07:21:10.548 --> 07:21:10.558 align:start position:0% theoretical and it's compatible with all 07:21:10.558 --> 07:21:13.310 align:start position:0% theoretical and it's compatible with all of<07:21:10.680> the<07:21:10.860> previous<07:21:10.978> versions 07:21:13.310 --> 07:21:13.320 align:start position:0% of the previous versions 07:21:13.320 --> 07:21:15.830 align:start position:0% of the previous versions now<07:21:13.978> there<07:21:14.340> are<07:21:14.458> two<07:21:14.760> modes<07:21:15.298> that<07:21:15.718> are 07:21:15.830 --> 07:21:15.840 align:start position:0% now there are two modes that are 07:21:15.840 --> 07:21:18.048 align:start position:0% now there are two modes that are supported<07:21:16.200> by<07:21:16.378> the<07:21:16.558> Ada<07:21:16.798> 211<07:21:17.218> standard<07:21:17.638> the 07:21:18.048 --> 07:21:18.058 align:start position:0% supported by the Ada 211 standard the 07:21:18.058 --> 07:21:20.150 align:start position:0% supported by the Ada 211 standard the first<07:21:18.540> is<07:21:18.718> what<07:21:18.900> we<07:21:19.080> call<07:21:19.260> infrastructure 07:21:20.150 --> 07:21:20.160 align:start position:0% first is what we call infrastructure 07:21:20.160 --> 07:21:22.128 align:start position:0% first is what we call infrastructure mode<07:21:20.400> this<07:21:20.940> is<07:21:21.058> the<07:21:21.180> mode<07:21:21.360> that's<07:21:21.660> configured 07:21:22.128 --> 07:21:22.138 align:start position:0% mode this is the mode that's configured 07:21:22.138 --> 07:21:24.530 align:start position:0% mode this is the mode that's configured to<07:21:22.260> use<07:21:22.440> wireless<07:21:22.920> access<07:21:23.400> points<07:21:24.058> to<07:21:24.360> connect 07:21:24.530 --> 07:21:24.540 align:start position:0% to use wireless access points to connect 07:21:24.540 --> 07:21:27.530 align:start position:0% to use wireless access points to connect workstations<07:21:25.320> to<07:21:25.978> a<07:21:26.160> cable<07:21:26.340> backbone 07:21:27.530 --> 07:21:27.540 align:start position:0% workstations to a cable backbone 07:21:27.540 --> 07:21:30.110 align:start position:0% workstations to a cable backbone the<07:21:28.138> network<07:21:28.378> using<07:21:29.340> the<07:21:29.520> infrastructure 07:21:30.110 --> 07:21:30.120 align:start position:0% the network using the infrastructure 07:21:30.120 --> 07:21:32.750 align:start position:0% the network using the infrastructure mode<07:21:30.360> is<07:21:30.900> going<07:21:31.080> to<07:21:31.200> either<07:21:31.320> use<07:21:31.740> a<07:21:32.458> basic 07:21:32.750 --> 07:21:32.760 align:start position:0% mode is going to either use a basic 07:21:32.760 --> 07:21:36.350 align:start position:0% mode is going to either use a basic service<07:21:32.940> set<07:21:33.298> or<07:21:34.260> an<07:21:34.620> extended<07:21:35.100> service<07:21:35.340> set 07:21:36.350 --> 07:21:36.360 align:start position:0% service set or an extended service set 07:21:36.360 --> 07:21:37.788 align:start position:0% service set or an extended service set the<07:21:36.780> other<07:21:36.840> one<07:21:37.020> we<07:21:37.200> have<07:21:37.320> which<07:21:37.558> we<07:21:37.740> already 07:21:37.788 --> 07:21:37.798 align:start position:0% the other one we have which we already 07:21:37.798 --> 07:21:40.190 align:start position:0% the other one we have which we already mentioned<07:21:38.160> is<07:21:38.340> called<07:21:38.580> ad<07:21:39.000> hoc<07:21:39.240> mode<07:21:39.540> this<07:21:40.080> is 07:21:40.190 --> 07:21:40.200 align:start position:0% mentioned is called ad hoc mode this is 07:21:40.200 --> 07:21:42.890 align:start position:0% mentioned is called ad hoc mode this is for<07:21:40.378> those<07:21:40.558> peer-to-peer<07:21:41.340> configurations 07:21:42.890 --> 07:21:42.900 align:start position:0% for those peer-to-peer configurations 07:21:42.900 --> 07:21:45.110 align:start position:0% for those peer-to-peer configurations and<07:21:43.500> again<07:21:43.680> it's<07:21:44.040> referred<07:21:44.458> to<07:21:44.520> as<07:21:44.760> an 07:21:45.110 --> 07:21:45.120 align:start position:0% and again it's referred to as an 07:21:45.120 --> 07:21:49.070 align:start position:0% and again it's referred to as an independent<07:21:45.780> basic<07:21:46.320> service<07:21:46.620> set<07:21:46.920> or<07:21:47.760> an<07:21:48.080> ibss 07:21:49.070 --> 07:21:49.080 align:start position:0% independent basic service set or an ibss 07:21:49.080 --> 07:21:51.530 align:start position:0% independent basic service set or an ibss now<07:21:49.860> the<07:21:50.040> configuration<07:21:50.520> of<07:21:50.760> this<07:21:50.940> mode<07:21:51.120> is 07:21:51.530 --> 07:21:51.540 align:start position:0% now the configuration of this mode is 07:21:51.540 --> 07:21:53.690 align:start position:0% now the configuration of this mode is designed<07:21:52.020> with<07:21:52.320> each<07:21:52.620> Wireless<07:21:52.860> workstation 07:21:53.690 --> 07:21:53.700 align:start position:0% designed with each Wireless workstation 07:21:53.700 --> 07:21:56.330 align:start position:0% designed with each Wireless workstation able<07:21:54.540> to<07:21:54.660> communicate<07:21:55.320> directly<07:21:55.860> with<07:21:56.160> one 07:21:56.330 --> 07:21:56.340 align:start position:0% able to communicate directly with one 07:21:56.340 --> 07:21:58.190 align:start position:0% able to communicate directly with one another<07:21:56.520> without<07:21:57.120> having<07:21:57.478> to<07:21:57.660> go<07:21:57.780> through<07:21:58.020> a 07:21:58.190 --> 07:21:58.200 align:start position:0% another without having to go through a 07:21:58.200 --> 07:22:00.110 align:start position:0% another without having to go through a central<07:21:58.378> device 07:22:00.110 --> 07:22:00.120 align:start position:0% central device 07:22:00.120 --> 07:22:02.628 align:start position:0% central device now<07:22:00.718> earlier<07:22:01.138> in<07:22:01.378> this<07:22:01.558> module<07:22:01.978> we<07:22:02.280> talked 07:22:02.628 --> 07:22:02.638 align:start position:0% now earlier in this module we talked 07:22:02.638 --> 07:22:04.730 align:start position:0% now earlier in this module we talked about<07:22:02.820> the<07:22:03.240> service<07:22:03.420> sets<07:22:03.900> of<07:22:03.958> many<07:22:04.200> kinds<07:22:04.558> and 07:22:04.730 --> 07:22:04.740 align:start position:0% about the service sets of many kinds and 07:22:04.740 --> 07:22:06.830 align:start position:0% about the service sets of many kinds and we<07:22:04.860> talked<07:22:05.160> about<07:22:05.298> frames<07:22:06.298> in<07:22:06.660> previous 07:22:06.830 --> 07:22:06.840 align:start position:0% we talked about frames in previous 07:22:06.840 --> 07:22:09.048 align:start position:0% we talked about frames in previous modules<07:22:07.440> now<07:22:07.978> keeping<07:22:08.340> those<07:22:08.458> in<07:22:08.638> mind<07:22:08.820> it's 07:22:09.048 --> 07:22:09.058 align:start position:0% modules now keeping those in mind it's 07:22:09.058 --> 07:22:10.610 align:start position:0% modules now keeping those in mind it's important<07:22:09.360> to<07:22:09.540> understand<07:22:09.660> how<07:22:10.320> these 07:22:10.610 --> 07:22:10.620 align:start position:0% important to understand how these 07:22:10.620 --> 07:22:13.490 align:start position:0% important to understand how these devices<07:22:10.920> such<07:22:11.400> as<07:22:11.580> laptops<07:22:12.540> and<07:22:13.020> smartphones 07:22:13.490 --> 07:22:13.500 align:start position:0% devices such as laptops and smartphones 07:22:13.500 --> 07:22:15.830 align:start position:0% devices such as laptops and smartphones know<07:22:14.340> what<07:22:14.638> wireless<07:22:14.878> networks<07:22:15.600> are 07:22:15.830 --> 07:22:15.840 align:start position:0% know what wireless networks are 07:22:15.840 --> 07:22:18.350 align:start position:0% know what wireless networks are available<07:22:16.138> when<07:22:16.860> we<07:22:17.100> access<07:22:17.340> them 07:22:18.350 --> 07:22:18.360 align:start position:0% available when we access them 07:22:18.360 --> 07:22:20.270 align:start position:0% available when we access them now<07:22:18.718> this<07:22:19.138> comes<07:22:19.440> by<07:22:19.558> detecting<07:22:20.100> and 07:22:20.270 --> 07:22:20.280 align:start position:0% now this comes by detecting and 07:22:20.280 --> 07:22:22.128 align:start position:0% now this comes by detecting and receiving<07:22:20.580> what<07:22:20.878> are<07:22:21.000> called<07:22:21.180> Beacon<07:22:21.718> frames 07:22:22.128 --> 07:22:22.138 align:start position:0% receiving what are called Beacon frames 07:22:22.138 --> 07:22:24.948 align:start position:0% receiving what are called Beacon frames a<07:22:22.978> beacon<07:22:23.340> frame<07:22:23.638> is<07:22:23.820> a<07:22:24.180> management<07:22:24.360> frame 07:22:24.948 --> 07:22:24.958 align:start position:0% a beacon frame is a management frame 07:22:24.958 --> 07:22:27.708 align:start position:0% a beacon frame is a management frame that's<07:22:25.500> 50<07:22:25.860> bytes<07:22:26.340> long<07:22:26.580> and<07:22:27.180> it<07:22:27.298> contains 07:22:27.708 --> 07:22:27.718 align:start position:0% that's 50 bytes long and it contains 07:22:27.718 --> 07:22:29.270 align:start position:0% that's 50 bytes long and it contains information<07:22:27.900> about<07:22:28.680> the<07:22:29.100> transmission 07:22:29.270 --> 07:22:29.280 align:start position:0% information about the transmission 07:22:29.280 --> 07:22:33.590 align:start position:0% information about the transmission process<07:22:30.180> such<07:22:31.020> as<07:22:31.260> the<07:22:31.860> SSID<07:22:32.400> or<07:22:33.180> the<07:22:33.360> service 07:22:33.590 --> 07:22:33.600 align:start position:0% process such as the SSID or the service 07:22:33.600 --> 07:22:35.330 align:start position:0% process such as the SSID or the service set<07:22:33.958> identifier 07:22:35.330 --> 07:22:35.340 align:start position:0% set identifier 07:22:35.340 --> 07:22:39.170 align:start position:0% set identifier which<07:22:36.000> is<07:22:36.360> essentially<07:22:36.920> the<07:22:37.920> name<07:22:38.218> of<07:22:39.000> your 07:22:39.170 --> 07:22:39.180 align:start position:0% which is essentially the name of your 07:22:39.180 --> 07:22:41.030 align:start position:0% which is essentially the name of your network 07:22:41.030 --> 07:22:41.040 align:start position:0% network 07:22:41.040 --> 07:22:44.930 align:start position:0% network the<07:22:41.400> SSID<07:22:41.878> is<07:22:42.420> that<07:22:42.780> text<07:22:43.320> string<07:22:43.978> that 07:22:44.930 --> 07:22:44.940 align:start position:0% the SSID is that text string that 07:22:44.940 --> 07:22:47.390 align:start position:0% the SSID is that text string that identifies<07:22:45.478> the<07:22:45.660> network<07:22:45.840> it's<07:22:46.138> 32<07:22:46.620> bytes 07:22:47.390 --> 07:22:47.400 align:start position:0% identifies the network it's 32 bytes 07:22:47.400 --> 07:22:49.910 align:start position:0% identifies the network it's 32 bytes long<07:22:47.580> might<07:22:48.240> be<07:22:48.420> for<07:22:48.780> instance<07:22:49.080> Bill's 07:22:49.910 --> 07:22:49.920 align:start position:0% long might be for instance Bill's 07:22:49.920 --> 07:22:52.548 align:start position:0% long might be for instance Bill's Network<07:22:50.160> or<07:22:50.760> something<07:22:50.940> like<07:22:51.240> that<07:22:51.478> now<07:22:52.320> the 07:22:52.548 --> 07:22:52.558 align:start position:0% Network or something like that now the 07:22:52.558 --> 07:22:55.430 align:start position:0% Network or something like that now the beacon<07:22:52.978> frame<07:22:53.400> is<07:22:53.700> used<07:22:53.940> to<07:22:54.240> start<07:22:54.540> and 07:22:55.430 --> 07:22:55.440 align:start position:0% beacon frame is used to start and 07:22:55.440 --> 07:22:56.868 align:start position:0% beacon frame is used to start and maintain 07:22:56.868 --> 07:22:56.878 align:start position:0% maintain 07:22:56.878 --> 07:23:00.048 align:start position:0% maintain the<07:22:57.360> wireless<07:22:57.540> communication<07:22:58.440> session<07:22:59.058> and 07:23:00.048 --> 07:23:00.058 align:start position:0% the wireless communication session and 07:23:00.058 --> 07:23:02.330 align:start position:0% the wireless communication session and it's<07:23:00.240> sent<07:23:00.540> in<07:23:00.958> regular<07:23:01.260> intervals<07:23:01.860> from<07:23:02.160> the 07:23:02.330 --> 07:23:02.340 align:start position:0% it's sent in regular intervals from the 07:23:02.340 --> 07:23:04.490 align:start position:0% it's sent in regular intervals from the axis<07:23:02.760> point<07:23:03.000> and<07:23:03.600> those<07:23:03.780> intervals<07:23:04.200> can<07:23:04.320> be 07:23:04.490 --> 07:23:04.500 align:start position:0% axis point and those intervals can be 07:23:04.500 --> 07:23:06.170 align:start position:0% axis point and those intervals can be manually<07:23:04.798> changed<07:23:05.340> or<07:23:05.520> set<07:23:05.700> by<07:23:06.000> an 07:23:06.170 --> 07:23:06.180 align:start position:0% manually changed or set by an 07:23:06.180 --> 07:23:09.110 align:start position:0% manually changed or set by an administrator<07:23:06.958> and<07:23:07.500> we<07:23:07.620> can<07:23:07.798> even<07:23:07.978> turn<07:23:08.940> them 07:23:09.110 --> 07:23:09.120 align:start position:0% administrator and we can even turn them 07:23:09.120 --> 07:23:11.690 align:start position:0% administrator and we can even turn them off<07:23:09.420> so<07:23:09.718> that<07:23:10.020> way<07:23:10.260> or<07:23:10.798> hide<07:23:11.100> them<07:23:11.340> so<07:23:11.580> that's 07:23:11.690 --> 07:23:11.700 align:start position:0% off so that way or hide them so that's 07:23:11.700 --> 07:23:13.548 align:start position:0% off so that way or hide them so that's not<07:23:11.940> being<07:23:12.120> broadcast 07:23:13.548 --> 07:23:13.558 align:start position:0% not being broadcast 07:23:13.558 --> 07:23:16.128 align:start position:0% not being broadcast now<07:23:14.100> when<07:23:14.400> it<07:23:14.520> comes<07:23:14.878> to<07:23:15.120> installing<07:23:15.540> a<07:23:15.840> proper 07:23:16.128 --> 07:23:16.138 align:start position:0% now when it comes to installing a proper 07:23:16.138 --> 07:23:18.350 align:start position:0% now when it comes to installing a proper wireless<07:23:16.320> network<07:23:16.680> implementation<07:23:17.458> we<07:23:18.240> need 07:23:18.350 --> 07:23:18.360 align:start position:0% wireless network implementation we need 07:23:18.360 --> 07:23:20.270 align:start position:0% wireless network implementation we need to<07:23:18.478> be<07:23:18.600> familiar<07:23:18.958> with<07:23:19.260> the<07:23:19.440> typical<07:23:19.680> process 07:23:20.270 --> 07:23:20.280 align:start position:0% to be familiar with the typical process 07:23:20.280 --> 07:23:22.910 align:start position:0% to be familiar with the typical process and<07:23:20.760> the<07:23:20.878> steps<07:23:21.298> to<07:23:21.780> maintain<07:23:22.138> the<07:23:22.558> highest 07:23:22.910 --> 07:23:22.920 align:start position:0% and the steps to maintain the highest 07:23:22.920 --> 07:23:25.730 align:start position:0% and the steps to maintain the highest level<07:23:23.100> of<07:23:23.400> functionality<07:23:24.058> now<07:23:24.958> much<07:23:25.138> like<07:23:25.378> a 07:23:25.730 --> 07:23:25.740 align:start position:0% level of functionality now much like a 07:23:25.740 --> 07:23:27.350 align:start position:0% level of functionality now much like a lot<07:23:25.798> of<07:23:25.920> different<07:23:26.100> processes<07:23:26.700> the<07:23:27.058> basic 07:23:27.350 --> 07:23:27.360 align:start position:0% lot of different processes the basic 07:23:27.360 --> 07:23:29.390 align:start position:0% lot of different processes the basic steps<07:23:27.718> to<07:23:27.958> take<07:23:28.080> are<07:23:28.378> pretty<07:23:28.740> much<07:23:28.920> the<07:23:29.218> same 07:23:29.390 --> 07:23:29.400 align:start position:0% steps to take are pretty much the same 07:23:29.400 --> 07:23:32.090 align:start position:0% steps to take are pretty much the same they<07:23:30.058> begin<07:23:30.240> with<07:23:30.600> planning<07:23:31.080> so<07:23:31.740> there<07:23:31.920> are<07:23:32.040> a 07:23:32.090 --> 07:23:32.100 align:start position:0% they begin with planning so there are a 07:23:32.100 --> 07:23:33.590 align:start position:0% they begin with planning so there are a few<07:23:32.160> things<07:23:32.580> that<07:23:32.878> are<07:23:33.000> helpful<07:23:33.298> to<07:23:33.478> collect 07:23:33.590 --> 07:23:33.600 align:start position:0% few things that are helpful to collect 07:23:33.600 --> 07:23:35.930 align:start position:0% few things that are helpful to collect before<07:23:34.020> the<07:23:34.378> planning<07:23:34.920> process 07:23:35.930 --> 07:23:35.940 align:start position:0% before the planning process 07:23:35.940 --> 07:23:38.090 align:start position:0% before the planning process we<07:23:36.240> need<07:23:36.360> to<07:23:36.478> collect<07:23:36.660> information<07:23:37.020> about<07:23:37.860> the 07:23:38.090 --> 07:23:38.100 align:start position:0% we need to collect information about the 07:23:38.100 --> 07:23:40.070 align:start position:0% we need to collect information about the floor<07:23:38.280> plan<07:23:38.580> of<07:23:38.820> the<07:23:39.000> building<07:23:39.180> where<07:23:39.840> we<07:23:39.958> want 07:23:40.070 --> 07:23:40.080 align:start position:0% floor plan of the building where we want 07:23:40.080 --> 07:23:42.110 align:start position:0% floor plan of the building where we want to<07:23:40.200> install<07:23:40.440> and<07:23:40.978> so<07:23:41.160> we<07:23:41.340> can<07:23:41.458> design<07:23:41.700> a 07:23:42.110 --> 07:23:42.120 align:start position:0% to install and so we can design a 07:23:42.120 --> 07:23:43.610 align:start position:0% to install and so we can design a topology<07:23:42.540> and<07:23:42.780> figure<07:23:42.958> out<07:23:43.080> where<07:23:43.320> to<07:23:43.440> put 07:23:43.610 --> 07:23:43.620 align:start position:0% topology and figure out where to put 07:23:43.620 --> 07:23:46.070 align:start position:0% topology and figure out where to put access<07:23:43.860> points<07:23:44.458> we<07:23:45.298> need<07:23:45.420> to<07:23:45.600> establish 07:23:46.070 --> 07:23:46.080 align:start position:0% access points we need to establish 07:23:46.080 --> 07:23:48.170 align:start position:0% access points we need to establish requirements<07:23:46.920> for<07:23:47.160> how<07:23:47.400> many<07:23:47.520> devices<07:23:47.878> are 07:23:48.170 --> 07:23:48.180 align:start position:0% requirements for how many devices are 07:23:48.180 --> 07:23:50.868 align:start position:0% requirements for how many devices are going<07:23:48.360> to<07:23:48.540> connect<07:23:48.780> which<07:23:49.680> 802.11<07:23:50.400> standard 07:23:50.868 --> 07:23:50.878 align:start position:0% going to connect which 802.11 standard 07:23:50.878 --> 07:23:52.968 align:start position:0% going to connect which 802.11 standard we're<07:23:51.058> going<07:23:51.240> to<07:23:51.420> use<07:23:51.600> what<07:23:52.378> type<07:23:52.558> of<07:23:52.740> security 07:23:52.968 --> 07:23:52.978 align:start position:0% we're going to use what type of security 07:23:52.978 --> 07:23:55.730 align:start position:0% we're going to use what type of security is<07:23:53.340> going<07:23:53.520> to<07:23:53.638> be<07:23:53.700> required<07:23:54.180> and<07:23:54.360> so<07:23:54.540> on<07:23:55.200> now 07:23:55.730 --> 07:23:55.740 align:start position:0% is going to be required and so on now 07:23:55.740 --> 07:23:57.468 align:start position:0% is going to be required and so on now all<07:23:55.978> of<07:23:56.100> these<07:23:56.280> are<07:23:56.458> crucial<07:23:56.760> to<07:23:57.000> proper 07:23:57.468 --> 07:23:57.478 align:start position:0% all of these are crucial to proper 07:23:57.478 --> 07:23:59.270 align:start position:0% all of these are crucial to proper planning<07:23:57.900> without<07:23:58.260> this<07:23:58.558> information<07:23:58.740> it's 07:23:59.270 --> 07:23:59.280 align:start position:0% planning without this information it's 07:23:59.280 --> 07:24:00.350 align:start position:0% planning without this information it's just<07:23:59.400> going<07:23:59.520> to<07:23:59.520> be<07:23:59.638> easy<07:23:59.760> to<07:24:00.000> choose<07:24:00.180> the 07:24:00.350 --> 07:24:00.360 align:start position:0% just going to be easy to choose the 07:24:00.360 --> 07:24:03.250 align:start position:0% just going to be easy to choose the wrong<07:24:00.478> devices<07:24:00.900> or<07:24:01.620> the<07:24:02.218> wrong<07:24:02.458> Technologies 07:24:03.250 --> 07:24:03.260 align:start position:0% wrong devices or the wrong Technologies 07:24:03.260 --> 07:24:05.690 align:start position:0% wrong devices or the wrong Technologies also<07:24:04.260> if<07:24:04.558> the<07:24:04.740> research<07:24:05.160> isn't<07:24:05.520> done 07:24:05.690 --> 07:24:05.700 align:start position:0% also if the research isn't done 07:24:05.700 --> 07:24:07.490 align:start position:0% also if the research isn't done beforehand<07:24:06.420> you're<07:24:06.958> going<07:24:07.080> to<07:24:07.200> find<07:24:07.320> yourself 07:24:07.490 --> 07:24:07.500 align:start position:0% beforehand you're going to find yourself 07:24:07.500 --> 07:24:11.208 align:start position:0% beforehand you're going to find yourself performing<07:24:08.280> a<07:24:08.940> lot<07:24:09.058> of<07:24:09.240> rework<07:24:09.840> at<07:24:10.138> the<07:24:10.260> end 07:24:11.208 --> 07:24:11.218 align:start position:0% performing a lot of rework at the end 07:24:11.218 --> 07:24:13.310 align:start position:0% performing a lot of rework at the end now<07:24:11.580> once<07:24:11.820> this<07:24:11.940> information<07:24:12.120> is<07:24:12.718> designed 07:24:13.310 --> 07:24:13.320 align:start position:0% now once this information is designed 07:24:13.320 --> 07:24:14.750 align:start position:0% now once this information is designed and<07:24:13.680> gathered 07:24:14.750 --> 07:24:14.760 align:start position:0% and gathered 07:24:14.760 --> 07:24:16.788 align:start position:0% and gathered we<07:24:15.180> can<07:24:15.298> start<07:24:15.478> to<07:24:15.660> establish<07:24:16.080> the<07:24:16.378> type<07:24:16.558> of 07:24:16.788 --> 07:24:16.798 align:start position:0% we can start to establish the type of 07:24:16.798 --> 07:24:19.190 align:start position:0% we can start to establish the type of access<07:24:17.040> points<07:24:17.700> and<07:24:18.180> the<07:24:18.298> number<07:24:18.478> of<07:24:18.660> APs 07:24:19.190 --> 07:24:19.200 align:start position:0% access points and the number of APs 07:24:19.200 --> 07:24:21.350 align:start position:0% access points and the number of APs needed<07:24:19.558> knowing<07:24:20.458> the<07:24:20.580> number<07:24:20.700> of<07:24:20.820> users<07:24:21.180> on 07:24:21.350 --> 07:24:21.360 align:start position:0% needed knowing the number of users on 07:24:21.360 --> 07:24:22.548 align:start position:0% needed knowing the number of users on the<07:24:21.478> network<07:24:21.600> is<07:24:21.958> going<07:24:22.138> to<07:24:22.260> help<07:24:22.440> us 07:24:22.548 --> 07:24:22.558 align:start position:0% the network is going to help us 07:24:22.558 --> 07:24:24.770 align:start position:0% the network is going to help us determine<07:24:23.040> for<07:24:23.400> instance<07:24:23.638> how<07:24:24.420> many<07:24:24.540> access 07:24:24.770 --> 07:24:24.780 align:start position:0% determine for instance how many access 07:24:24.780 --> 07:24:27.048 align:start position:0% determine for instance how many access points<07:24:25.378> and<07:24:26.040> we<07:24:26.160> want<07:24:26.340> to<07:24:26.458> balance<07:24:26.700> the<07:24:26.878> number 07:24:27.048 --> 07:24:27.058 align:start position:0% points and we want to balance the number 07:24:27.058 --> 07:24:28.850 align:start position:0% points and we want to balance the number of<07:24:27.180> users<07:24:27.540> with<07:24:27.780> the<07:24:27.958> access<07:24:28.080> points<07:24:28.558> in<07:24:28.680> order 07:24:28.850 --> 07:24:28.860 align:start position:0% of users with the access points in order 07:24:28.860 --> 07:24:31.010 align:start position:0% of users with the access points in order to<07:24:29.040> make<07:24:29.218> sure<07:24:29.520> that<07:24:30.058> we<07:24:30.180> have<07:24:30.360> a<07:24:30.478> good<07:24:30.660> load 07:24:31.010 --> 07:24:31.020 align:start position:0% to make sure that we have a good load 07:24:31.020 --> 07:24:31.910 align:start position:0% to make sure that we have a good load balance 07:24:31.910 --> 07:24:31.920 align:start position:0% balance 07:24:31.920 --> 07:24:34.310 align:start position:0% balance the<07:24:32.458> next<07:24:32.638> step<07:24:32.820> is<07:24:33.000> to<07:24:33.298> assess<07:24:33.660> the<07:24:34.200> building 07:24:34.310 --> 07:24:34.320 align:start position:0% the next step is to assess the building 07:24:34.320 --> 07:24:36.410 align:start position:0% the next step is to assess the building to<07:24:34.680> see<07:24:34.798> if<07:24:34.978> anything<07:24:35.218> around<07:24:35.520> might<07:24:36.180> cause 07:24:36.410 --> 07:24:36.420 align:start position:0% to see if anything around might cause 07:24:36.420 --> 07:24:37.850 align:start position:0% to see if anything around might cause interference 07:24:37.850 --> 07:24:37.860 align:start position:0% interference 07:24:37.860 --> 07:24:39.708 align:start position:0% interference specifically<07:24:38.580> it's<07:24:39.000> important<07:24:39.360> to<07:24:39.600> install 07:24:39.708 --> 07:24:39.718 align:start position:0% specifically it's important to install 07:24:39.718 --> 07:24:41.810 align:start position:0% specifically it's important to install anything<07:24:40.138> that's<07:24:40.500> going<07:24:40.680> to<07:24:40.798> be<07:24:40.860> on<07:24:41.040> the<07:24:41.218> 2.4 07:24:41.810 --> 07:24:41.820 align:start position:0% anything that's going to be on the 2.4 07:24:41.820 --> 07:24:44.030 align:start position:0% anything that's going to be on the 2.4 gigahertz<07:24:42.240> band<07:24:42.600> now<07:24:43.080> remember<07:24:43.260> some<07:24:43.860> of<07:24:43.978> the 07:24:44.030 --> 07:24:44.040 align:start position:0% gigahertz band now remember some of the 07:24:44.040 --> 07:24:45.830 align:start position:0% gigahertz band now remember some of the things<07:24:44.218> that<07:24:44.400> can<07:24:44.580> cause<07:24:44.700> interference<07:24:45.420> are 07:24:45.830 --> 07:24:45.840 align:start position:0% things that can cause interference are 07:24:45.840 --> 07:24:47.510 align:start position:0% things that can cause interference are Bluetooth<07:24:46.080> devices<07:24:46.680> other<07:24:47.218> wireless 07:24:47.510 --> 07:24:47.520 align:start position:0% Bluetooth devices other wireless 07:24:47.520 --> 07:24:51.048 align:start position:0% Bluetooth devices other wireless networks<07:24:48.298> heavy<07:24:48.900> duty<07:24:49.138> machinery<07:24:49.620> and<07:24:49.920> so<07:24:50.100> on 07:24:51.048 --> 07:24:51.058 align:start position:0% networks heavy duty machinery and so on 07:24:51.058 --> 07:24:53.390 align:start position:0% networks heavy duty machinery and so on we<07:24:51.478> also<07:24:51.660> need<07:24:51.840> to<07:24:51.958> determine<07:24:52.440> the<07:24:53.040> exact 07:24:53.390 --> 07:24:53.400 align:start position:0% we also need to determine the exact 07:24:53.400 --> 07:24:55.610 align:start position:0% we also need to determine the exact placement<07:24:53.940> of<07:24:54.240> the<07:24:54.420> access<07:24:54.540> points<07:24:55.080> are<07:24:55.500> they 07:24:55.610 --> 07:24:55.620 align:start position:0% placement of the access points are they 07:24:55.620 --> 07:24:56.868 align:start position:0% placement of the access points are they going<07:24:55.740> to<07:24:55.740> be<07:24:55.860> placed<07:24:56.160> in<07:24:56.218> the<07:24:56.340> ceiling<07:24:56.700> or 07:24:56.868 --> 07:24:56.878 align:start position:0% going to be placed in the ceiling or 07:24:56.878 --> 07:24:59.090 align:start position:0% going to be placed in the ceiling or somewhere<07:24:57.180> visible<07:24:57.540> or<07:24:58.378> somewhere<07:24:58.680> like<07:24:58.860> a 07:24:59.090 --> 07:24:59.100 align:start position:0% somewhere visible or somewhere like a 07:24:59.100 --> 07:25:01.250 align:start position:0% somewhere visible or somewhere like a secure<07:24:59.400> room<07:24:59.638> and<07:25:00.360> when<07:25:00.540> we<07:25:00.660> determine<07:25:01.080> this 07:25:01.250 --> 07:25:01.260 align:start position:0% secure room and when we determine this 07:25:01.260 --> 07:25:03.110 align:start position:0% secure room and when we determine this we<07:25:01.440> need<07:25:01.558> to<07:25:01.680> make<07:25:01.798> sure<07:25:01.978> that<07:25:02.280> there's<07:25:02.700> we're 07:25:03.110 --> 07:25:03.120 align:start position:0% we need to make sure that there's we're 07:25:03.120 --> 07:25:04.788 align:start position:0% we need to make sure that there's we're looking<07:25:03.298> for<07:25:03.540> obstacles<07:25:04.080> that<07:25:04.440> are<07:25:04.558> going<07:25:04.740> to 07:25:04.788 --> 07:25:04.798 align:start position:0% looking for obstacles that are going to 07:25:04.798 --> 07:25:07.548 align:start position:0% looking for obstacles that are going to impede<07:25:05.280> like<07:25:05.580> thick<07:25:06.000> walls<07:25:06.478> doors<07:25:07.020> metal 07:25:07.548 --> 07:25:07.558 align:start position:0% impede like thick walls doors metal 07:25:07.558 --> 07:25:10.788 align:start position:0% impede like thick walls doors metal shelving<07:25:08.160> uh<07:25:08.940> proximity<07:25:09.540> to<07:25:10.138> large 07:25:10.788 --> 07:25:10.798 align:start position:0% shelving uh proximity to large 07:25:10.798 --> 07:25:12.890 align:start position:0% shelving uh proximity to large electrical<07:25:11.520> equipment<07:25:11.940> and<07:25:12.540> if<07:25:12.660> those 07:25:12.890 --> 07:25:12.900 align:start position:0% electrical equipment and if those 07:25:12.900 --> 07:25:14.750 align:start position:0% electrical equipment and if those obstacles<07:25:13.378> Can't<07:25:13.620> Be<07:25:13.798> Moved<07:25:14.160> we<07:25:14.400> might<07:25:14.580> want 07:25:14.750 --> 07:25:14.760 align:start position:0% obstacles Can't Be Moved we might want 07:25:14.760 --> 07:25:16.430 align:start position:0% obstacles Can't Be Moved we might want to<07:25:14.878> choose<07:25:15.180> a<07:25:15.360> different<07:25:15.478> location<07:25:15.780> for<07:25:16.260> our 07:25:16.430 --> 07:25:16.440 align:start position:0% to choose a different location for our 07:25:16.440 --> 07:25:17.570 align:start position:0% to choose a different location for our access<07:25:16.620> point 07:25:17.570 --> 07:25:17.580 align:start position:0% access point 07:25:17.580 --> 07:25:19.190 align:start position:0% access point so<07:25:17.940> now<07:25:18.120> that<07:25:18.240> we've<07:25:18.420> planned<07:25:18.718> the<07:25:18.840> next<07:25:19.020> part 07:25:19.190 --> 07:25:19.200 align:start position:0% so now that we've planned the next part 07:25:19.200 --> 07:25:21.708 align:start position:0% so now that we've planned the next part is<07:25:19.378> the<07:25:19.558> fun<07:25:19.680> part<07:25:20.340> the<07:25:20.940> actual<07:25:21.120> installation 07:25:21.708 --> 07:25:21.718 align:start position:0% is the fun part the actual installation 07:25:21.718 --> 07:25:24.890 align:start position:0% is the fun part the actual installation here<07:25:22.558> we<07:25:22.740> need<07:25:22.860> to<07:25:22.978> configure<07:25:23.580> the<07:25:23.878> device<07:25:24.058> to 07:25:24.890 --> 07:25:24.900 align:start position:0% here we need to configure the device to 07:25:24.900 --> 07:25:26.448 align:start position:0% here we need to configure the device to connect<07:25:25.080> it<07:25:25.320> to<07:25:25.500> the<07:25:25.620> network<07:25:25.798> and<07:25:26.218> some<07:25:26.340> of 07:25:26.448 --> 07:25:26.458 align:start position:0% connect it to the network and some of 07:25:26.458 --> 07:25:27.350 align:start position:0% connect it to the network and some of the<07:25:26.520> standard<07:25:26.760> things<07:25:26.940> we're<07:25:27.058> going<07:25:27.180> to<07:25:27.298> do 07:25:27.350 --> 07:25:27.360 align:start position:0% the standard things we're going to do 07:25:27.360 --> 07:25:29.270 align:start position:0% the standard things we're going to do are<07:25:27.600> connect<07:25:27.900> the<07:25:28.260> router 07:25:29.270 --> 07:25:29.280 align:start position:0% are connect the router 07:25:29.280 --> 07:25:31.850 align:start position:0% are connect the router change<07:25:29.940> the<07:25:30.298> administrator<07:25:31.080> default 07:25:31.850 --> 07:25:31.860 align:start position:0% change the administrator default 07:25:31.860 --> 07:25:34.670 align:start position:0% change the administrator default settings<07:25:32.100> that<07:25:32.520> the<07:25:32.700> device<07:25:32.878> came<07:25:33.360> with<07:25:34.080> and 07:25:34.670 --> 07:25:34.680 align:start position:0% settings that the device came with and 07:25:34.680 --> 07:25:37.430 align:start position:0% settings that the device came with and configure<07:25:35.160> DHCP<07:25:36.000> services<07:25:36.420> and<07:25:36.958> encryption 07:25:37.430 --> 07:25:37.440 align:start position:0% configure DHCP services and encryption 07:25:37.440 --> 07:25:39.590 align:start position:0% configure DHCP services and encryption levels<07:25:37.860> such<07:25:38.580> as<07:25:38.700> whether<07:25:39.120> we're<07:25:39.298> going<07:25:39.478> to 07:25:39.590 --> 07:25:39.600 align:start position:0% levels such as whether we're going to 07:25:39.600 --> 07:25:44.150 align:start position:0% levels such as whether we're going to use<07:25:39.840> WPA 07:25:44.150 --> 07:25:44.160 align:start position:0% 07:25:44.160 --> 07:25:48.170 align:start position:0% or<07:25:45.120> WEP<07:25:46.020> and<07:25:46.860> also<07:25:47.100> are<07:25:47.280> we<07:25:47.400> going<07:25:47.520> to<07:25:47.638> use<07:25:47.760> one 07:25:48.170 --> 07:25:48.180 align:start position:0% or WEP and also are we going to use one 07:25:48.180 --> 07:25:49.430 align:start position:0% or WEP and also are we going to use one of<07:25:48.298> the<07:25:48.478> three<07:25:48.660> channels<07:25:49.020> are<07:25:49.138> we<07:25:49.260> going<07:25:49.378> to 07:25:49.430 --> 07:25:49.440 align:start position:0% of the three channels are we going to 07:25:49.440 --> 07:25:51.830 align:start position:0% of the three channels are we going to have<07:25:49.500> them<07:25:49.680> auto<07:25:49.978> check<07:25:50.340> or<07:25:50.878> what<07:25:51.120> another 07:25:51.830 --> 07:25:51.840 align:start position:0% have them auto check or what another 07:25:51.840 --> 07:25:52.910 align:start position:0% have them auto check or what another thing<07:25:52.080> we<07:25:52.200> might<07:25:52.320> want<07:25:52.440> to<07:25:52.558> do<07:25:52.620> is<07:25:52.740> create 07:25:52.910 --> 07:25:52.920 align:start position:0% thing we might want to do is create 07:25:52.920 --> 07:25:54.948 align:start position:0% thing we might want to do is create what's<07:25:53.160> called<07:25:53.400> an<07:25:53.700> access<07:25:53.940> control<07:25:54.600> list 07:25:54.948 --> 07:25:54.958 align:start position:0% what's called an access control list 07:25:54.958 --> 07:25:58.730 align:start position:0% what's called an access control list which<07:25:55.740> means<07:25:56.160> we<07:25:56.638> can<07:25:56.820> allow<07:25:57.320> only<07:25:58.320> specific 07:25:58.730 --> 07:25:58.740 align:start position:0% which means we can allow only specific 07:25:58.740 --> 07:26:01.070 align:start position:0% which means we can allow only specific computers<07:25:59.280> to<07:25:59.580> get<07:25:59.700> access<07:25:59.940> to<07:26:00.298> our 07:26:01.070 --> 07:26:01.080 align:start position:0% computers to get access to our 07:26:01.080 --> 07:26:04.430 align:start position:0% computers to get access to our network<07:26:01.860> via<07:26:02.820> Mac<07:26:03.058> addresses<07:26:03.660> which<07:26:04.320> are 07:26:04.430 --> 07:26:04.440 align:start position:0% network via Mac addresses which are 07:26:04.440 --> 07:26:06.770 align:start position:0% network via Mac addresses which are again<07:26:04.680> the<07:26:05.520> physical<07:26:05.700> addresses<07:26:06.478> on<07:26:06.660> a 07:26:06.770 --> 07:26:06.780 align:start position:0% again the physical addresses on a 07:26:06.780 --> 07:26:07.788 align:start position:0% again the physical addresses on a computer 07:26:07.788 --> 07:26:07.798 align:start position:0% computer 07:26:07.798 --> 07:26:13.730 align:start position:0% computer or<07:26:08.218> on<07:26:08.400> a<07:26:08.520> network<07:26:08.638> card 07:26:13.730 --> 07:26:13.740 align:start position:0% 07:26:13.740 --> 07:26:15.948 align:start position:0% next<07:26:14.340> we<07:26:14.520> need<07:26:14.700> to<07:26:14.820> configure<07:26:15.360> the<07:26:15.660> client 07:26:15.948 --> 07:26:15.958 align:start position:0% next we need to configure the client 07:26:15.958 --> 07:26:18.230 align:start position:0% next we need to configure the client workstations<07:26:16.558> and<07:26:16.920> we<07:26:17.100> need<07:26:17.218> to<07:26:17.458> test<07:26:17.700> your 07:26:18.230 --> 07:26:18.240 align:start position:0% workstations and we need to test your 07:26:18.240 --> 07:26:20.570 align:start position:0% workstations and we need to test your functionality<07:26:18.900> now<07:26:19.680> it's<07:26:19.978> important<07:26:20.340> here 07:26:20.570 --> 07:26:20.580 align:start position:0% functionality now it's important here 07:26:20.580 --> 07:26:23.090 align:start position:0% functionality now it's important here because<07:26:20.820> not<07:26:21.360> all<07:26:21.660> operating<07:26:22.260> systems<07:26:22.798> can 07:26:23.090 --> 07:26:23.100 align:start position:0% because not all operating systems can 07:26:23.100 --> 07:26:24.530 align:start position:0% because not all operating systems can use<07:26:23.280> all<07:26:23.580> the<07:26:23.700> different<07:26:23.820> standards<07:26:24.298> they 07:26:24.530 --> 07:26:24.540 align:start position:0% use all the different standards they 07:26:24.540 --> 07:26:26.750 align:start position:0% use all the different standards they might<07:26:24.660> even<07:26:24.840> require<07:26:25.200> a<07:26:25.978> software<07:26:26.280> update<07:26:26.638> of 07:26:26.750 --> 07:26:26.760 align:start position:0% might even require a software update of 07:26:26.760 --> 07:26:28.250 align:start position:0% might even require a software update of some<07:26:27.058> sort 07:26:28.250 --> 07:26:28.260 align:start position:0% some sort 07:26:28.260 --> 07:26:30.948 align:start position:0% some sort you<07:26:28.978> might<07:26:29.100> want<07:26:29.218> to<07:26:29.400> make<07:26:29.638> sure<07:26:29.940> to<07:26:30.540> test<07:26:30.718> the 07:26:30.948 --> 07:26:30.958 align:start position:0% you might want to make sure to test the 07:26:30.958 --> 07:26:32.810 align:start position:0% you might want to make sure to test the wireless<07:26:31.138> device<07:26:31.500> by<07:26:31.920> walking<07:26:32.160> around<07:26:32.458> a 07:26:32.810 --> 07:26:32.820 align:start position:0% wireless device by walking around a 07:26:32.820 --> 07:26:34.670 align:start position:0% wireless device by walking around a building<07:26:33.058> and<07:26:33.840> make<07:26:34.020> sure<07:26:34.138> you<07:26:34.320> can<07:26:34.440> stay 07:26:34.670 --> 07:26:34.680 align:start position:0% building and make sure you can stay 07:26:34.680 --> 07:26:36.048 align:start position:0% building and make sure you can stay connected<07:26:35.160> and<07:26:35.340> that<07:26:35.458> you<07:26:35.580> can<07:26:35.700> connect<07:26:35.820> in 07:26:36.048 --> 07:26:36.058 align:start position:0% connected and that you can connect in 07:26:36.058 --> 07:26:38.330 align:start position:0% connected and that you can connect in the<07:26:36.240> first<07:26:36.360> place<07:26:36.620> anywhere<07:26:37.620> you<07:26:37.798> need<07:26:37.920> to<07:26:38.100> and 07:26:38.330 --> 07:26:38.340 align:start position:0% the first place anywhere you need to and 07:26:38.340 --> 07:26:39.830 align:start position:0% the first place anywhere you need to and then<07:26:38.638> you<07:26:38.878> also<07:26:39.058> need<07:26:39.180> to<07:26:39.360> take<07:26:39.478> the<07:26:39.718> device 07:26:39.830 --> 07:26:39.840 align:start position:0% then you also need to take the device 07:26:39.840 --> 07:26:42.110 align:start position:0% then you also need to take the device outside<07:26:40.260> and<07:26:40.680> make<07:26:40.860> sure<07:26:41.040> that<07:26:41.340> no<07:26:41.760> one<07:26:41.940> can 07:26:42.110 --> 07:26:42.120 align:start position:0% outside and make sure that no one can 07:26:42.120 --> 07:26:44.150 align:start position:0% outside and make sure that no one can get<07:26:42.360> in<07:26:42.478> from<07:26:42.718> the<07:26:42.900> outside<07:26:43.080> so<07:26:43.620> it's<07:26:43.860> actually 07:26:44.150 --> 07:26:44.160 align:start position:0% get in from the outside so it's actually 07:26:44.160 --> 07:26:46.128 align:start position:0% get in from the outside so it's actually quite<07:26:44.580> difficult<07:26:45.058> to<07:26:45.420> just<07:26:45.540> start<07:26:45.780> one<07:26:46.080> of 07:26:46.128 --> 07:26:46.138 align:start position:0% quite difficult to just start one of 07:26:46.138 --> 07:26:48.410 align:start position:0% quite difficult to just start one of these<07:26:46.320> from<07:26:46.500> scratch<07:26:46.798> the<07:26:47.760> last<07:26:47.878> step<07:26:48.058> in<07:26:48.298> the 07:26:48.410 --> 07:26:48.420 align:start position:0% these from scratch the last step in the 07:26:48.420 --> 07:26:50.868 align:start position:0% these from scratch the last step in the process<07:26:48.718> is<07:26:49.138> to<07:26:49.320> document<07:26:49.740> every<07:26:50.340> single<07:26:50.638> step 07:26:50.868 --> 07:26:50.878 align:start position:0% process is to document every single step 07:26:50.878 --> 07:26:52.670 align:start position:0% process is to document every single step that<07:26:51.180> was<07:26:51.298> made<07:26:51.600> and<07:26:52.138> it's<07:26:52.320> always<07:26:52.440> a<07:26:52.558> good 07:26:52.670 --> 07:26:52.680 align:start position:0% that was made and it's always a good 07:26:52.680 --> 07:26:54.948 align:start position:0% that was made and it's always a good idea<07:26:52.978> to<07:26:53.218> Baseline<07:26:53.820> for<07:26:54.058> future<07:26:54.240> testing<07:26:54.780> and 07:26:54.948 --> 07:26:54.958 align:start position:0% idea to Baseline for future testing and 07:26:54.958 --> 07:26:57.230 align:start position:0% idea to Baseline for future testing and implementations<07:26:55.558> now<07:26:56.520> being<07:26:56.760> able<07:26:57.000> to 07:26:57.230 --> 07:26:57.240 align:start position:0% implementations now being able to 07:26:57.240 --> 07:26:59.510 align:start position:0% implementations now being able to successfully<07:26:57.840> accomplish<07:26:58.620> the<07:26:58.920> two<07:26:59.160> phases 07:26:59.510 --> 07:26:59.520 align:start position:0% successfully accomplish the two phases 07:26:59.520 --> 07:27:01.850 align:start position:0% successfully accomplish the two phases the<07:27:00.058> planning<07:27:00.420> phase<07:27:00.600> and<07:27:01.200> the<07:27:01.378> installation 07:27:01.850 --> 07:27:01.860 align:start position:0% the planning phase and the installation 07:27:01.860 --> 07:27:03.948 align:start position:0% the planning phase and the installation phase<07:27:02.280> needs<07:27:02.940> to<07:27:03.000> be<07:27:03.120> a<07:27:03.240> part<07:27:03.360> of<07:27:03.540> your<07:27:03.718> skill 07:27:03.948 --> 07:27:03.958 align:start position:0% phase needs to be a part of your skill 07:27:03.958 --> 07:27:05.330 align:start position:0% phase needs to be a part of your skill set<07:27:04.138> needs<07:27:04.558> to<07:27:04.558> be<07:27:04.680> something<07:27:04.798> you<07:27:05.040> understand 07:27:05.330 --> 07:27:05.340 align:start position:0% set needs to be something you understand 07:27:05.340 --> 07:27:07.910 align:start position:0% set needs to be something you understand for<07:27:05.940> the<07:27:06.058> network<07:27:06.180> plus<07:27:06.478> exam<07:27:06.958> so<07:27:07.620> just<07:27:07.798> to 07:27:07.910 --> 07:27:07.920 align:start position:0% for the network plus exam so just to 07:27:07.920 --> 07:27:09.890 align:start position:0% for the network plus exam so just to recap<07:27:08.218> everything<07:27:08.458> we've<07:27:08.820> talked<07:27:09.120> about<07:27:09.180> the 07:27:09.890 --> 07:27:09.900 align:start position:0% recap everything we've talked about the 07:27:09.900 --> 07:27:11.208 align:start position:0% recap everything we've talked about the first<07:27:10.020> thing<07:27:10.138> we<07:27:10.260> did<07:27:10.378> is<07:27:10.558> we<07:27:10.740> outlined<07:27:11.160> the 07:27:11.208 --> 07:27:11.218 align:start position:0% first thing we did is we outlined the 07:27:11.218 --> 07:27:13.490 align:start position:0% first thing we did is we outlined the different<07:27:11.400> types<07:27:12.000> of<07:27:12.298> ethernet<07:27:12.840> networks 07:27:13.490 --> 07:27:13.500 align:start position:0% different types of ethernet networks 07:27:13.500 --> 07:27:17.510 align:start position:0% different types of ethernet networks whether<07:27:14.340> that<07:27:14.580> means<07:27:14.940> it's<07:27:15.718> a<07:27:16.080> Hub<07:27:16.320> Network 07:27:17.510 --> 07:27:17.520 align:start position:0% whether that means it's a Hub Network 07:27:17.520 --> 07:27:19.430 align:start position:0% whether that means it's a Hub Network a<07:27:18.120> router<07:27:18.478> Network 07:27:19.430 --> 07:27:19.440 align:start position:0% a router Network 07:27:19.440 --> 07:27:24.048 align:start position:0% a router Network or<07:27:19.978> a<07:27:20.100> peer-to-peer<07:27:20.700> Network 07:27:24.048 --> 07:27:24.058 align:start position:0% 07:27:24.058 --> 07:27:27.288 align:start position:0% we<07:27:24.660> also<07:27:24.958> explained<07:27:25.580> WLAN<07:27:26.580> architecture 07:27:27.288 --> 07:27:27.298 align:start position:0% we also explained WLAN architecture 07:27:27.298 --> 07:27:29.208 align:start position:0% we also explained WLAN architecture looking<07:27:28.020> at<07:27:28.260> the<07:27:28.440> difference<07:27:28.558> between<07:27:28.860> a 07:27:29.208 --> 07:27:29.218 align:start position:0% looking at the difference between a 07:27:29.218 --> 07:27:31.430 align:start position:0% looking at the difference between a basic<07:27:29.458> service<07:27:29.700> set<07:27:30.000> an<07:27:30.718> extended<07:27:31.138> service 07:27:31.430 --> 07:27:31.440 align:start position:0% basic service set an extended service 07:27:31.440 --> 07:27:35.270 align:start position:0% basic service set an extended service set<07:27:31.740> and<07:27:32.580> an<07:27:32.760> independent<07:27:33.298> basic<07:27:33.660> service<07:27:33.900> set 07:27:35.270 --> 07:27:35.280 align:start position:0% set and an independent basic service set 07:27:35.280 --> 07:27:36.770 align:start position:0% set and an independent basic service set we<07:27:35.638> defined<07:27:36.000> and<07:27:36.120> describe<07:27:36.600> the 07:27:36.770 --> 07:27:36.780 align:start position:0% we defined and describe the 07:27:36.780 --> 07:27:39.468 align:start position:0% we defined and describe the characteristics<07:27:37.440> of<07:27:37.798> antennas<07:27:38.280> looking<07:27:39.000> at 07:27:39.468 --> 07:27:39.478 align:start position:0% characteristics of antennas looking at 07:27:39.478 --> 07:27:40.850 align:start position:0% characteristics of antennas looking at gain 07:27:40.850 --> 07:27:40.860 align:start position:0% gain 07:27:40.860 --> 07:27:43.548 align:start position:0% gain and<07:27:41.340> the<07:27:41.520> types<07:27:41.878> of<07:27:42.180> impedances<07:27:42.958> that<07:27:43.440> could 07:27:43.548 --> 07:27:43.558 align:start position:0% and the types of impedances that could 07:27:43.558 --> 07:27:46.548 align:start position:0% and the types of impedances that could occur 07:27:46.548 --> 07:27:46.558 align:start position:0% 07:27:46.558 --> 07:27:49.810 align:start position:0% then<07:27:46.920> we<07:27:47.100> outline<07:27:47.400> the<07:27:47.580> Ada<07:27:47.940> to<07:27:48.120> 11<07:27:48.298> standard 07:27:49.810 --> 07:27:49.820 align:start position:0% then we outline the Ada to 11 standard 07:27:49.820 --> 07:27:54.948 align:start position:0% then we outline the Ada to 11 standard including<07:27:51.200> a<07:27:52.200> b<07:27:52.620> g<07:27:53.100> and<07:27:53.580> N<07:27:53.820> which<07:27:54.600> are<07:27:54.718> the 07:27:54.948 --> 07:27:54.958 align:start position:0% including a b g and N which are the 07:27:54.958 --> 07:27:56.868 align:start position:0% including a b g and N which are the different<07:27:55.080> modes 07:27:56.868 --> 07:27:56.878 align:start position:0% different modes 07:27:56.878 --> 07:27:59.390 align:start position:0% different modes we<07:27:57.360> also<07:27:57.600> talked<07:27:57.958> about<07:27:58.080> which<07:27:58.798> frequencies 07:27:59.390 --> 07:27:59.400 align:start position:0% we also talked about which frequencies 07:27:59.400 --> 07:28:03.650 align:start position:0% we also talked about which frequencies these<07:27:59.820> live<07:28:00.000> on<07:28:00.660> whether<07:28:01.200> 2.4<07:28:01.920> or<07:28:02.100> 5 07:28:03.650 --> 07:28:03.660 align:start position:0% these live on whether 2.4 or 5 07:28:03.660 --> 07:28:06.530 align:start position:0% these live on whether 2.4 or 5 and<07:28:04.320> how<07:28:04.860> fast<07:28:05.160> are<07:28:05.580> the<07:28:05.700> megabits<07:28:06.180> per<07:28:06.298> second 07:28:06.530 --> 07:28:06.540 align:start position:0% and how fast are the megabits per second 07:28:06.540 --> 07:28:08.990 align:start position:0% and how fast are the megabits per second that<07:28:06.840> each<07:28:07.020> one<07:28:07.200> provides<07:28:07.740> you<07:28:08.638> want<07:28:08.760> to<07:28:08.878> make 07:28:08.990 --> 07:28:09.000 align:start position:0% that each one provides you want to make 07:28:09.000 --> 07:28:10.850 align:start position:0% that each one provides you want to make sure<07:28:09.180> to<07:28:09.298> commit<07:28:09.540> to<07:28:09.718> memory<07:28:10.020> that<07:28:10.200> table<07:28:10.500> that 07:28:10.850 --> 07:28:10.860 align:start position:0% sure to commit to memory that table that 07:28:10.860 --> 07:28:14.030 align:start position:0% sure to commit to memory that table that we<07:28:10.978> displayed<07:28:11.520> on<07:28:11.638> an<07:28:11.820> earlier<07:28:12.120> frame 07:28:14.030 --> 07:28:14.040 align:start position:0% we displayed on an earlier frame 07:28:14.040 --> 07:28:16.190 align:start position:0% we displayed on an earlier frame we<07:28:14.520> also<07:28:14.760> talked<07:28:15.058> about<07:28:15.180> defining<07:28:15.718> Beacon 07:28:16.190 --> 07:28:16.200 align:start position:0% we also talked about defining Beacon 07:28:16.200 --> 07:28:20.090 align:start position:0% we also talked about defining Beacon frames<07:28:16.620> which<07:28:17.218> broadcast<07:28:17.580> the<07:28:18.120> SSID<07:28:18.920> and<07:28:19.920> tell 07:28:20.090 --> 07:28:20.100 align:start position:0% frames which broadcast the SSID and tell 07:28:20.100 --> 07:28:22.070 align:start position:0% frames which broadcast the SSID and tell computers<07:28:20.760> how<07:28:21.240> to<07:28:21.420> connect<07:28:21.540> to<07:28:21.840> the<07:28:21.958> wireless 07:28:22.070 --> 07:28:22.080 align:start position:0% computers how to connect to the wireless 07:28:22.080 --> 07:28:23.510 align:start position:0% computers how to connect to the wireless network 07:28:23.510 --> 07:28:23.520 align:start position:0% network 07:28:23.520 --> 07:28:26.270 align:start position:0% network finally<07:28:24.360> we<07:28:24.840> outlined<07:28:25.320> what<07:28:25.740> factors<07:28:26.100> are 07:28:26.270 --> 07:28:26.280 align:start position:0% finally we outlined what factors are 07:28:26.280 --> 07:28:28.310 align:start position:0% finally we outlined what factors are going<07:28:26.458> to<07:28:26.638> result<07:28:26.820> in<07:28:27.298> where<07:28:27.540> you<07:28:27.718> place<07:28:28.020> your 07:28:28.310 --> 07:28:28.320 align:start position:0% going to result in where you place your 07:28:28.320 --> 07:28:30.830 align:start position:0% going to result in where you place your access<07:28:28.500> point<07:28:28.940> and<07:28:29.940> how<07:28:30.180> to<07:28:30.360> properly 07:28:30.830 --> 07:28:30.840 align:start position:0% access point and how to properly 07:28:30.840 --> 07:28:33.410 align:start position:0% access point and how to properly Implement<07:28:31.740> a<07:28:31.978> wireless<07:28:32.100> network<07:28:32.458> point 07:28:33.410 --> 07:28:33.420 align:start position:0% Implement a wireless network point 07:28:33.420 --> 07:28:35.628 align:start position:0% Implement a wireless network point from<07:28:33.900> the<07:28:34.080> planning 07:28:35.628 --> 07:28:35.638 align:start position:0% from the planning 07:28:35.638 --> 07:28:43.650 align:start position:0% from the planning and<07:28:36.360> implementation<07:28:37.138> stages 07:28:43.650 --> 07:28:43.660 align:start position:0% 07:28:43.660 --> 07:28:58.548 align:start position:0% [Music] 07:28:58.548 --> 07:28:58.558 align:start position:0% 07:28:58.558 --> 07:29:01.330 align:start position:0% welcome<07:28:59.160> to<07:28:59.458> module<07:28:59.820> 5<07:29:00.000> lesson<07:29:00.540> five 07:29:01.330 --> 07:29:01.340 align:start position:0% welcome to module 5 lesson five 07:29:01.340 --> 07:29:05.750 align:start position:0% welcome to module 5 lesson five IEEE<07:29:02.600> 802.11<07:29:03.600> AC<07:29:04.280> actually<07:29:05.280> we're<07:29:05.520> going<07:29:05.638> to 07:29:05.750 --> 07:29:05.760 align:start position:0% IEEE 802.11 AC actually we're going to 07:29:05.760 --> 07:29:08.448 align:start position:0% IEEE 802.11 AC actually we're going to look<07:29:05.820> at<07:29:06.000> a<07:29:06.180> little<07:29:06.360> bit<07:29:06.478> more<07:29:06.780> than<07:29:07.080> that<07:29:07.458> the 07:29:08.448 --> 07:29:08.458 align:start position:0% look at a little bit more than that the 07:29:08.458 --> 07:29:11.510 align:start position:0% look at a little bit more than that the N<07:29:08.760> standard<07:29:09.360> 82.11n 07:29:11.510 --> 07:29:11.520 align:start position:0% N standard 82.11n 07:29:11.520 --> 07:29:15.350 align:start position:0% N standard 82.11n AC<07:29:12.180> Channel<07:29:13.138> bonding 07:29:15.350 --> 07:29:15.360 align:start position:0% AC Channel bonding 07:29:15.360 --> 07:29:19.190 align:start position:0% AC Channel bonding now<07:29:15.718> the<07:29:15.860> 802.11<07:29:16.860> it's<07:29:17.638> a<07:29:17.940> specification<07:29:18.600> for 07:29:19.190 --> 07:29:19.200 align:start position:0% now the 802.11 it's a specification for 07:29:19.200 --> 07:29:23.030 align:start position:0% now the 802.11 it's a specification for wireless<07:29:19.860> LAN<07:29:20.280> WLAN<07:29:21.000> communication<07:29:21.740> it<07:29:22.740> uses 07:29:23.030 --> 07:29:23.040 align:start position:0% wireless LAN WLAN communication it uses 07:29:23.040 --> 07:29:26.810 align:start position:0% wireless LAN WLAN communication it uses mimo<07:29:23.700> which<07:29:24.478> we<07:29:24.780> shorten<07:29:25.680> from<07:29:26.100> a<07:29:26.400> multiple 07:29:26.810 --> 07:29:26.820 align:start position:0% mimo which we shorten from a multiple 07:29:26.820 --> 07:29:29.628 align:start position:0% mimo which we shorten from a multiple input<07:29:27.298> multiple<07:29:27.958> outputs<07:29:28.500> I'm<07:29:29.218> sure<07:29:29.400> you<07:29:29.520> can 07:29:29.628 --> 07:29:29.638 align:start position:0% input multiple outputs I'm sure you can 07:29:29.638 --> 07:29:31.490 align:start position:0% input multiple outputs I'm sure you can see<07:29:29.820> why 07:29:31.490 --> 07:29:31.500 align:start position:0% see why 07:29:31.500 --> 07:29:34.128 align:start position:0% see why so<07:29:32.458> in<07:29:32.878> this<07:29:33.000> technology<07:29:33.360> the<07:29:33.780> transmitter 07:29:34.128 --> 07:29:34.138 align:start position:0% so in this technology the transmitter 07:29:34.138 --> 07:29:38.208 align:start position:0% so in this technology the transmitter and<07:29:34.440> receiver<07:29:34.798> use<07:29:35.100> multiple<07:29:35.580> antennas 07:29:38.208 --> 07:29:38.218 align:start position:0% and receiver use multiple antennas 07:29:38.218 --> 07:29:40.128 align:start position:0% and receiver use multiple antennas I've<07:29:38.638> put<07:29:38.820> a<07:29:38.940> little<07:29:39.058> diagram<07:29:39.420> on<07:29:39.718> the<07:29:39.900> bottom 07:29:40.128 --> 07:29:40.138 align:start position:0% I've put a little diagram on the bottom 07:29:40.138 --> 07:29:43.490 align:start position:0% I've put a little diagram on the bottom here<07:29:40.378> from<07:29:41.218> um<07:29:41.298> ieb<07:29:42.298> media 07:29:43.490 --> 07:29:43.500 align:start position:0% here from um ieb media 07:29:43.500 --> 07:29:45.770 align:start position:0% here from um ieb media that<07:29:43.920> it<07:29:44.100> will<07:29:44.218> demonstrate<07:29:44.820> at<07:29:45.478> the<07:29:45.600> bottom 07:29:45.770 --> 07:29:45.780 align:start position:0% that it will demonstrate at the bottom 07:29:45.780 --> 07:29:47.628 align:start position:0% that it will demonstrate at the bottom certainly<07:29:46.138> you<07:29:46.260> can<07:29:46.440> see<07:29:46.558> three<07:29:46.798> channels<07:29:47.280> in 07:29:47.628 --> 07:29:47.638 align:start position:0% certainly you can see three channels in 07:29:47.638 --> 07:29:51.048 align:start position:0% certainly you can see three channels in use<07:29:48.080> simultaneously<07:29:49.080> multiple<07:29:50.040> channels<07:29:50.520> on 07:29:51.048 --> 07:29:51.058 align:start position:0% use simultaneously multiple channels on 07:29:51.058 --> 07:29:54.288 align:start position:0% use simultaneously multiple channels on the<07:29:51.360> top<07:29:51.840> part<07:29:52.200> of<07:29:52.378> the<07:29:52.500> Fig<07:29:52.740> you<07:29:53.400> can<07:29:53.520> see<07:29:53.760> you 07:29:54.288 --> 07:29:54.298 align:start position:0% the top part of the Fig you can see you 07:29:54.298 --> 07:29:57.048 align:start position:0% the top part of the Fig you can see you can<07:29:54.478> select<07:29:54.718> from<07:29:54.900> but<07:29:55.080> it's<07:29:55.260> only<07:29:55.440> using<07:29:55.860> one 07:29:57.048 --> 07:29:57.058 align:start position:0% can select from but it's only using one 07:29:57.058 --> 07:29:59.330 align:start position:0% can select from but it's only using one so<07:29:57.780> in<07:29:58.080> this<07:29:58.260> standard<07:29:58.558> the<07:29:58.740> end<07:29:58.920> standard 07:29:59.330 --> 07:29:59.340 align:start position:0% so in this standard the end standard 07:29:59.340 --> 07:30:01.548 align:start position:0% so in this standard the end standard multiple<07:29:59.820> antennas<07:30:00.478> provide<07:30:00.900> independent 07:30:01.548 --> 07:30:01.558 align:start position:0% multiple antennas provide independent 07:30:01.558 --> 07:30:03.350 align:start position:0% multiple antennas provide independent paths<07:30:01.920> in<07:30:02.160> space<07:30:02.340> between<07:30:02.638> the<07:30:02.940> transmitter 07:30:03.350 --> 07:30:03.360 align:start position:0% paths in space between the transmitter 07:30:03.360 --> 07:30:05.030 align:start position:0% paths in space between the transmitter and<07:30:03.600> the<07:30:03.958> receiver 07:30:05.030 --> 07:30:05.040 align:start position:0% and the receiver 07:30:05.040 --> 07:30:07.670 align:start position:0% and the receiver to<07:30:05.638> send<07:30:05.820> or<07:30:06.120> receive<07:30:06.660> streams<07:30:07.620> of 07:30:07.670 --> 07:30:07.680 align:start position:0% to send or receive streams of 07:30:07.680 --> 07:30:09.948 align:start position:0% to send or receive streams of information<07:30:07.978> at<07:30:08.400> the<07:30:08.580> same<07:30:08.760> time<07:30:09.000> on<07:30:09.660> the<07:30:09.780> same 07:30:09.948 --> 07:30:09.958 align:start position:0% information at the same time on the same 07:30:09.958 --> 07:30:10.788 align:start position:0% information at the same time on the same band 07:30:10.788 --> 07:30:10.798 align:start position:0% band 07:30:10.798 --> 07:30:12.770 align:start position:0% band what<07:30:11.280> my<07:30:11.520> mode<07:30:11.700> does<07:30:11.940> is<07:30:12.120> increase<07:30:12.360> the<07:30:12.660> number 07:30:12.770 --> 07:30:12.780 align:start position:0% what my mode does is increase the number 07:30:12.780 --> 07:30:14.330 align:start position:0% what my mode does is increase the number of<07:30:12.958> data<07:30:13.320> streams<07:30:13.620> sent<07:30:13.860> from<07:30:14.040> an<07:30:14.218> access 07:30:14.330 --> 07:30:14.340 align:start position:0% of data streams sent from an access 07:30:14.340 --> 07:30:16.368 align:start position:0% of data streams sent from an access point<07:30:14.700> to<07:30:14.940> a<07:30:15.120> client<07:30:15.360> which<07:30:15.840> you<07:30:15.958> can<07:30:16.080> see<07:30:16.200> in 07:30:16.368 --> 07:30:16.378 align:start position:0% point to a client which you can see in 07:30:16.378 --> 07:30:18.590 align:start position:0% point to a client which you can see in the<07:30:16.500> bottom<07:30:16.740> part 07:30:18.590 --> 07:30:18.600 align:start position:0% the bottom part 07:30:18.600 --> 07:30:22.190 align:start position:0% the bottom part in<07:30:19.080> 802.11<07:30:20.040> mimo<07:30:20.760> four<07:30:21.058> spatial<07:30:21.540> streams<07:30:21.958> can 07:30:22.190 --> 07:30:22.200 align:start position:0% in 802.11 mimo four spatial streams can 07:30:22.200 --> 07:30:25.430 align:start position:0% in 802.11 mimo four spatial streams can be<07:30:22.378> sent<07:30:22.500> to<07:30:22.680> a<07:30:22.860> single<07:30:23.100> client<07:30:23.280> at<07:30:23.638> a<07:30:23.820> time 07:30:25.430 --> 07:30:25.440 align:start position:0% be sent to a single client at a time 07:30:25.440 --> 07:30:27.350 align:start position:0% be sent to a single client at a time again<07:30:25.740> if<07:30:26.100> you<07:30:26.280> want<07:30:26.400> to<07:30:26.520> read<07:30:26.638> further<07:30:27.180> you 07:30:27.350 --> 07:30:27.360 align:start position:0% again if you want to read further you 07:30:27.360 --> 07:30:28.850 align:start position:0% again if you want to read further you can<07:30:27.478> now<07:30:27.600> look<07:30:27.840> up<07:30:27.958> the<07:30:28.260> specifications 07:30:28.850 --> 07:30:28.860 align:start position:0% can now look up the specifications 07:30:28.860 --> 07:30:31.490 align:start position:0% can now look up the specifications there's<07:30:29.218> a<07:30:29.400> few<07:30:29.520> Wireless<07:30:30.080> specialty<07:30:31.080> books 07:30:31.490 --> 07:30:31.500 align:start position:0% there's a few Wireless specialty books 07:30:31.500 --> 07:30:33.110 align:start position:0% there's a few Wireless specialty books if<07:30:31.680> it's<07:30:31.860> something<07:30:32.040> you're<07:30:32.458> interested<07:30:33.000> in 07:30:33.110 --> 07:30:33.120 align:start position:0% if it's something you're interested in 07:30:33.120 --> 07:30:34.670 align:start position:0% if it's something you're interested in doing<07:30:33.298> it's<07:30:33.660> certainly<07:30:34.020> an<07:30:34.200> interesting 07:30:34.670 --> 07:30:34.680 align:start position:0% doing it's certainly an interesting 07:30:34.680 --> 07:30:36.288 align:start position:0% doing it's certainly an interesting field 07:30:36.288 --> 07:30:36.298 align:start position:0% field 07:30:36.298 --> 07:30:40.548 align:start position:0% field uh<07:30:37.020> the<07:30:37.378> 802.11<07:30:38.218> AC<07:30:38.520> is<07:30:38.940> an<07:30:39.120> enhancement<07:30:39.718> of<07:30:40.558> um 07:30:40.548 --> 07:30:40.558 align:start position:0% uh the 802.11 AC is an enhancement of um 07:30:40.558 --> 07:30:42.048 align:start position:0% uh the 802.11 AC is an enhancement of um 11n 07:30:42.048 --> 07:30:42.058 align:start position:0% 11n 07:30:42.058 --> 07:30:44.570 align:start position:0% 11n obviously<07:30:42.660> still<07:30:42.900> Wireless<07:30:43.138> networking<07:30:43.920> it's 07:30:44.570 --> 07:30:44.580 align:start position:0% obviously still Wireless networking it's 07:30:44.580 --> 07:30:46.910 align:start position:0% obviously still Wireless networking it's designed<07:30:45.058> for<07:30:45.180> high<07:30:45.360> throughput<07:30:45.920> our 07:30:46.910 --> 07:30:46.920 align:start position:0% designed for high throughput our 07:30:46.920 --> 07:30:49.730 align:start position:0% designed for high throughput our wireless<07:30:47.638> Lans<07:30:48.120> on<07:30:48.420> the<07:30:48.600> five<07:30:48.780> gigahertz<07:30:49.378> band 07:30:49.730 --> 07:30:49.740 align:start position:0% wireless Lans on the five gigahertz band 07:30:49.740 --> 07:30:53.270 align:start position:0% wireless Lans on the five gigahertz band there's<07:30:50.218> a<07:30:50.400> few<07:30:50.520> advantages<07:30:50.878> to<07:30:51.240> using<07:30:51.600> that 07:30:53.270 --> 07:30:53.280 align:start position:0% there's a few advantages to using that 07:30:53.280 --> 07:30:58.310 align:start position:0% there's a few advantages to using that it<07:30:53.700> uses<07:30:54.120> a<07:30:54.420> multi-user<07:30:55.020> form<07:30:55.200> of<07:30:55.440> Mimo 07:30:58.310 --> 07:30:58.320 align:start position:0% 07:30:58.320 --> 07:31:00.288 align:start position:0% in<07:30:58.860> their<07:30:58.978> mind<07:30:59.160> mode<07:30:59.400> the<07:30:59.580> access<07:30:59.638> points<07:31:00.120> has 07:31:00.288 --> 07:31:00.298 align:start position:0% in their mind mode the access points has 07:31:00.298 --> 07:31:02.330 align:start position:0% in their mind mode the access points has multiple<07:31:00.840> streams<07:31:01.260> of<07:31:01.440> data<07:31:01.740> at<07:31:02.100> the<07:31:02.218> same 07:31:02.330 --> 07:31:02.340 align:start position:0% multiple streams of data at the same 07:31:02.340 --> 07:31:04.610 align:start position:0% multiple streams of data at the same time<07:31:02.458> to<07:31:02.638> different<07:31:02.878> clients<07:31:03.478> over<07:31:04.138> the<07:31:04.440> same 07:31:04.610 --> 07:31:04.620 align:start position:0% time to different clients over the same 07:31:04.620 --> 07:31:06.410 align:start position:0% time to different clients over the same frequency<07:31:05.040> spectrum 07:31:06.410 --> 07:31:06.420 align:start position:0% frequency spectrum 07:31:06.420 --> 07:31:11.990 align:start position:0% frequency spectrum in<07:31:07.378> uh<07:31:08.240> 802.11<07:31:09.440> acmu<07:31:10.440> mimo<07:31:10.978> eight<07:31:11.760> special 07:31:11.990 --> 07:31:12.000 align:start position:0% in uh 802.11 acmu mimo eight special 07:31:12.000 --> 07:31:15.110 align:start position:0% in uh 802.11 acmu mimo eight special streams<07:31:12.600> can<07:31:12.780> be<07:31:12.958> divided<07:31:13.680> among<07:31:14.400> up<07:31:14.760> to<07:31:14.940> four 07:31:15.110 --> 07:31:15.120 align:start position:0% streams can be divided among up to four 07:31:15.120 --> 07:31:19.310 align:start position:0% streams can be divided among up to four clients<07:31:15.540> I<07:31:15.718> think<07:31:15.840> the<07:31:15.958> MU<07:31:16.260> is<07:31:16.500> multiple<07:31:16.860> user 07:31:19.310 --> 07:31:19.320 align:start position:0% clients I think the MU is multiple user 07:31:19.320 --> 07:31:21.650 align:start position:0% clients I think the MU is multiple user yeah<07:31:19.920> multi-user<07:31:20.638> mimo<07:31:21.000> at<07:31:21.180> the<07:31:21.298> bottom<07:31:21.478> and 07:31:21.650 --> 07:31:21.660 align:start position:0% yeah multi-user mimo at the bottom and 07:31:21.660 --> 07:31:24.288 align:start position:0% yeah multi-user mimo at the bottom and you<07:31:21.780> can<07:31:21.900> see<07:31:22.020> the<07:31:22.260> stream<07:31:22.500> can<07:31:23.040> be<07:31:23.340> broken<07:31:23.940> up 07:31:24.288 --> 07:31:24.298 align:start position:0% you can see the stream can be broken up 07:31:24.298 --> 07:31:26.750 align:start position:0% you can see the stream can be broken up you've<07:31:24.780> got<07:31:24.900> a<07:31:25.080> few<07:31:25.200> options<07:31:25.680> you<07:31:26.280> can<07:31:26.400> have<07:31:26.520> a 07:31:26.750 --> 07:31:26.760 align:start position:0% you've got a few options you can have a 07:31:26.760 --> 07:31:29.030 align:start position:0% you've got a few options you can have a higher<07:31:27.058> stream<07:31:27.240> to<07:31:27.478> one<07:31:27.718> client<07:31:28.080> and<07:31:28.860> then 07:31:29.030 --> 07:31:29.040 align:start position:0% higher stream to one client and then 07:31:29.040 --> 07:31:31.010 align:start position:0% higher stream to one client and then lower<07:31:29.420> bandwidth<07:31:30.420> stream<07:31:30.540> to<07:31:30.780> another 07:31:31.010 --> 07:31:31.020 align:start position:0% lower bandwidth stream to another 07:31:31.020 --> 07:31:34.610 align:start position:0% lower bandwidth stream to another clients 07:31:34.610 --> 07:31:34.620 align:start position:0% 07:31:34.620 --> 07:31:37.190 align:start position:0% supports<07:31:35.580> treatment<07:31:35.700> of<07:31:36.000> HD<07:31:36.360> videos<07:31:36.600> which<07:31:37.080> is 07:31:37.190 --> 07:31:37.200 align:start position:0% supports treatment of HD videos which is 07:31:37.200 --> 07:31:39.048 align:start position:0% supports treatment of HD videos which is really<07:31:37.378> handy<07:31:37.798> and<07:31:38.100> to<07:31:38.218> multiple<07:31:38.580> clients 07:31:39.048 --> 07:31:39.058 align:start position:0% really handy and to multiple clients 07:31:39.058 --> 07:31:41.150 align:start position:0% really handy and to multiple clients because<07:31:39.360> of<07:31:39.600> low<07:31:39.840> latency<07:31:40.260> high<07:31:40.680> throughput 07:31:41.150 --> 07:31:41.160 align:start position:0% because of low latency high throughput 07:31:41.160 --> 07:31:43.368 align:start position:0% because of low latency high throughput and<07:31:41.820> reliability 07:31:43.368 --> 07:31:43.378 align:start position:0% and reliability 07:31:43.378 --> 07:31:46.368 align:start position:0% and reliability it<07:31:43.860> operates<07:31:44.160> in<07:31:44.400> the<07:31:44.520> five<07:31:44.700> gigahertz<07:31:45.180> band<07:31:45.540> I 07:31:46.368 --> 07:31:46.378 align:start position:0% it operates in the five gigahertz band I 07:31:46.378 --> 07:31:48.468 align:start position:0% it operates in the five gigahertz band I already<07:31:46.558> mentioned<07:31:46.978> that<07:31:47.160> theoretical<07:31:48.120> data 07:31:48.468 --> 07:31:48.478 align:start position:0% already mentioned that theoretical data 07:31:48.478 --> 07:31:50.510 align:start position:0% already mentioned that theoretical data rate<07:31:48.600> of<07:31:48.780> 600<07:31:49.260> this<07:31:49.558> has<07:31:49.680> been<07:31:49.860> improved<07:31:50.340> on 07:31:50.510 --> 07:31:50.520 align:start position:0% rate of 600 this has been improved on 07:31:50.520 --> 07:31:53.930 align:start position:0% rate of 600 this has been improved on all<07:31:50.820> the<07:31:51.000> time<07:31:51.180> so<07:31:51.478> maybe<07:31:52.138> check<07:31:52.500> up<07:31:52.740> on<07:31:53.400> the<07:31:53.940> um 07:31:53.930 --> 07:31:53.940 align:start position:0% all the time so maybe check up on the um 07:31:53.940 --> 07:31:58.250 align:start position:0% all the time so maybe check up on the um standard<07:31:54.660> before<07:31:55.320> exam<07:31:56.100> day 07:31:58.250 --> 07:31:58.260 align:start position:0% standard before exam day 07:31:58.260 --> 07:32:00.590 align:start position:0% standard before exam day you've<07:31:58.620> got<07:31:58.740> less<07:31:58.978> interference<07:31:59.820> than<07:32:00.120> in<07:32:00.420> the 07:32:00.590 --> 07:32:00.600 align:start position:0% you've got less interference than in the 07:32:00.600 --> 07:32:03.350 align:start position:0% you've got less interference than in the 2.4<07:32:01.200> gigahertz<07:32:01.740> band<07:32:02.100> which<07:32:03.000> is<07:32:03.058> where<07:32:03.240> you 07:32:03.350 --> 07:32:03.360 align:start position:0% 2.4 gigahertz band which is where you 07:32:03.360 --> 07:32:05.390 align:start position:0% 2.4 gigahertz band which is where you get<07:32:03.478> the<07:32:03.660> increased<07:32:04.080> performance<07:32:04.500> more 07:32:05.390 --> 07:32:05.400 align:start position:0% get the increased performance more 07:32:05.400 --> 07:32:07.570 align:start position:0% get the increased performance more channels<07:32:05.878> available<07:32:06.240> for<07:32:06.660> data<07:32:07.080> transmission 07:32:07.570 --> 07:32:07.580 align:start position:0% channels available for data transmission 07:32:07.580 --> 07:32:10.010 align:start position:0% channels available for data transmission greater<07:32:08.580> number<07:32:08.760> of<07:32:09.020> non-overlapping 07:32:10.010 --> 07:32:10.020 align:start position:0% greater number of non-overlapping 07:32:10.020 --> 07:32:13.548 align:start position:0% greater number of non-overlapping channels<07:32:10.378> than<07:32:10.620> you<07:32:10.798> do<07:32:10.978> in<07:32:11.458> 2.4<07:32:12.180> megahertz<07:32:12.780> I 07:32:13.548 --> 07:32:13.558 align:start position:0% channels than you do in 2.4 megahertz I 07:32:13.558 --> 07:32:15.048 align:start position:0% channels than you do in 2.4 megahertz I think<07:32:13.680> there's<07:32:13.920> a<07:32:14.100> couple<07:32:14.280> of<07:32:14.458> disadvantages 07:32:15.048 --> 07:32:15.058 align:start position:0% think there's a couple of disadvantages 07:32:15.058 --> 07:32:16.850 align:start position:0% think there's a couple of disadvantages as<07:32:15.478> well<07:32:15.660> but<07:32:15.840> I'm<07:32:16.020> not<07:32:16.320> sure<07:32:16.440> I'll<07:32:16.558> put<07:32:16.740> them 07:32:16.850 --> 07:32:16.860 align:start position:0% as well but I'm not sure I'll put them 07:32:16.860 --> 07:32:18.590 align:start position:0% as well but I'm not sure I'll put them down<07:32:16.978> here<07:32:17.160> in<07:32:17.340> the<07:32:17.520> slide 07:32:18.590 --> 07:32:18.600 align:start position:0% down here in the slide 07:32:18.600 --> 07:32:21.730 align:start position:0% down here in the slide so<07:32:19.080> the<07:32:19.320> U.S<07:32:19.620> a<07:32:19.798> five<07:32:19.978> gigahertz<07:32:20.520> band<07:32:20.820> has<07:32:21.360> 25 07:32:21.730 --> 07:32:21.740 align:start position:0% so the U.S a five gigahertz band has 25 07:32:21.740 --> 07:32:24.530 align:start position:0% so the U.S a five gigahertz band has 25 non-overlapping<07:32:22.740> channels<07:32:23.218> whereas<07:32:23.940> 2.4 07:32:24.530 --> 07:32:24.540 align:start position:0% non-overlapping channels whereas 2.4 07:32:24.540 --> 07:32:29.750 align:start position:0% non-overlapping channels whereas 2.4 gigahertz<07:32:25.020> is<07:32:25.260> only<07:32:25.440> three 07:32:29.750 --> 07:32:29.760 align:start position:0% 07:32:29.760 --> 07:32:31.788 align:start position:0% uh<07:32:30.058> Channel<07:32:30.298> bandwidth<07:32:30.840> of<07:32:30.958> the<07:32:31.080> following<07:32:31.378> 80 07:32:31.788 --> 07:32:31.798 align:start position:0% uh Channel bandwidth of the following 80 07:32:31.798 --> 07:32:35.090 align:start position:0% uh Channel bandwidth of the following 80 160<07:32:32.700> 20<07:32:33.360> it's<07:32:33.718> worth<07:32:33.958> and<07:32:34.320> making<07:32:34.558> a<07:32:34.798> note<07:32:34.920> of 07:32:35.090 --> 07:32:35.100 align:start position:0% 160 20 it's worth and making a note of 07:32:35.100 --> 07:32:36.650 align:start position:0% 160 20 it's worth and making a note of all<07:32:35.218> of<07:32:35.340> these<07:32:35.520> in<07:32:35.760> case<07:32:35.878> it's<07:32:36.000> asked<07:32:36.420> in<07:32:36.478> the 07:32:36.650 --> 07:32:36.660 align:start position:0% all of these in case it's asked in the 07:32:36.660 --> 07:32:40.128 align:start position:0% all of these in case it's asked in the exam<07:32:36.900> and<07:32:37.320> 40. 07:32:40.128 --> 07:32:40.138 align:start position:0% exam and 40. 07:32:40.138 --> 07:32:42.650 align:start position:0% exam and 40. uh<07:32:40.860> obviously<07:32:41.160> needs<07:32:41.520> to<07:32:41.580> comply<07:32:42.298> with<07:32:42.478> the 07:32:42.650 --> 07:32:42.660 align:start position:0% uh obviously needs to comply with the 07:32:42.660 --> 07:32:43.968 align:start position:0% uh obviously needs to comply with the standard<07:32:42.958> you<07:32:43.138> can<07:32:43.260> see<07:32:43.440> this<07:32:43.740> particular 07:32:43.968 --> 07:32:43.978 align:start position:0% standard you can see this particular 07:32:43.978 --> 07:32:45.830 align:start position:0% standard you can see this particular adapter's<07:32:44.580> got<07:32:44.700> it<07:32:44.878> written<07:32:45.180> on<07:32:45.360> it<07:32:45.478> it's<07:32:45.600> got 07:32:45.830 --> 07:32:45.840 align:start position:0% adapter's got it written on it it's got 07:32:45.840 --> 07:32:48.770 align:start position:0% adapter's got it written on it it's got a<07:32:46.020> AC<07:32:46.320> standard<07:32:46.860> written<07:32:47.218> on<07:32:47.340> it 07:32:48.770 --> 07:32:48.780 align:start position:0% a AC standard written on it 07:32:48.780 --> 07:32:50.628 align:start position:0% a AC standard written on it to<07:32:49.200> comply<07:32:49.558> with<07:32:49.680> the<07:32:49.798> standard<07:32:50.100> as<07:32:50.400> to 07:32:50.628 --> 07:32:50.638 align:start position:0% to comply with the standard as to 07:32:50.638 --> 07:32:53.628 align:start position:0% to comply with the standard as to support<07:32:50.820> the<07:32:51.540> 2040<07:32:52.440> 80<07:32:52.680> megahertz<07:32:53.218> Channel 07:32:53.628 --> 07:32:53.638 align:start position:0% support the 2040 80 megahertz Channel 07:32:53.638 --> 07:32:56.810 align:start position:0% support the 2040 80 megahertz Channel bandwidth<07:32:54.360> in<07:32:54.478> the<07:32:54.660> 5<07:32:54.780> gigahertz<07:32:55.320> band 07:32:56.810 --> 07:32:56.820 align:start position:0% bandwidth in the 5 gigahertz band 07:32:56.820 --> 07:32:59.448 align:start position:0% bandwidth in the 5 gigahertz band the<07:32:57.478> 160<07:32:58.020> megahertz<07:32:58.440> Channel<07:32:58.740> bandwidth<07:32:59.340> is 07:32:59.448 --> 07:32:59.458 align:start position:0% the 160 megahertz Channel bandwidth is 07:32:59.458 --> 07:33:01.310 align:start position:0% the 160 megahertz Channel bandwidth is optional 07:33:01.310 --> 07:33:01.320 align:start position:0% optional 07:33:01.320 --> 07:33:03.230 align:start position:0% optional 80<07:33:01.798> megahertz<07:33:02.280> channels<07:33:02.700> are<07:33:02.820> formed<07:33:03.120> by 07:33:03.230 --> 07:33:03.240 align:start position:0% 80 megahertz channels are formed by 07:33:03.240 --> 07:33:04.548 align:start position:0% 80 megahertz channels are formed by combining<07:33:03.718> combining<07:33:04.138> the<07:33:04.260> following 07:33:04.548 --> 07:33:04.558 align:start position:0% combining combining the following 07:33:04.558 --> 07:33:07.490 align:start position:0% combining combining the following following<07:33:05.280> two<07:33:05.760> adjacent<07:33:06.360> none<07:33:06.900> overlapping 07:33:07.490 --> 07:33:07.500 align:start position:0% following two adjacent none overlapping 07:33:07.500 --> 07:33:10.010 align:start position:0% following two adjacent none overlapping 40<07:33:07.860> megahertz 07:33:10.010 --> 07:33:10.020 align:start position:0% 40 megahertz 07:33:10.020 --> 07:33:13.910 align:start position:0% 40 megahertz 160<07:33:10.798> megahertz<07:33:11.400> are<07:33:12.240> uh<07:33:12.660> combined<07:33:13.138> to<07:33:13.260> 80 07:33:13.910 --> 07:33:13.920 align:start position:0% 160 megahertz are uh combined to 80 07:33:13.920 --> 07:33:15.708 align:start position:0% 160 megahertz are uh combined to 80 megahertz<07:33:14.580> I<07:33:14.878> think<07:33:15.000> you<07:33:15.120> can<07:33:15.240> see<07:33:15.360> how<07:33:15.540> this 07:33:15.708 --> 07:33:15.718 align:start position:0% megahertz I think you can see how this 07:33:15.718 --> 07:33:17.750 align:start position:0% megahertz I think you can see how this works 07:33:17.750 --> 07:33:17.760 align:start position:0% works 07:33:17.760 --> 07:33:19.548 align:start position:0% works so<07:33:18.180> here<07:33:18.478> I've<07:33:18.718> put 07:33:19.548 --> 07:33:19.558 align:start position:0% so here I've put 07:33:19.558 --> 07:33:20.390 align:start position:0% so here I've put um 07:33:20.390 --> 07:33:20.400 align:start position:0% um 07:33:20.400 --> 07:33:24.530 align:start position:0% um a<07:33:20.458> slide<07:33:21.298> from<07:33:21.780> Wi-Fi<07:33:22.558> Jetty<07:33:23.100> website<07:33:23.580> they've 07:33:24.530 --> 07:33:24.540 align:start position:0% a slide from Wi-Fi Jetty website they've 07:33:24.540 --> 07:33:26.750 align:start position:0% a slide from Wi-Fi Jetty website they've combined<07:33:25.200> two<07:33:25.620> channels<07:33:26.100> here<07:33:26.280> to<07:33:26.520> 20 07:33:26.750 --> 07:33:26.760 align:start position:0% combined two channels here to 20 07:33:26.760 --> 07:33:28.910 align:start position:0% combined two channels here to 20 megahertz<07:33:27.240> channels<07:33:27.660> are<07:33:27.780> made<07:33:27.840> of<07:33:28.020> 40<07:33:28.200> for 07:33:28.910 --> 07:33:28.920 align:start position:0% megahertz channels are made of 40 for 07:33:28.920 --> 07:33:31.788 align:start position:0% megahertz channels are made of 40 for channel<07:33:29.160> bonding 07:33:31.788 --> 07:33:31.798 align:start position:0% 07:33:31.798 --> 07:33:34.010 align:start position:0% so<07:33:32.400> Channel<07:33:32.638> bonding<07:33:33.180> was<07:33:33.360> first<07:33:33.600> introduced 07:33:34.010 --> 07:33:34.020 align:start position:0% so Channel bonding was first introduced 07:33:34.020 --> 07:33:36.650 align:start position:0% so Channel bonding was first introduced with<07:33:34.260> 802.11n 07:33:36.650 --> 07:33:36.660 align:start position:0% with 802.11n 07:33:36.660 --> 07:33:38.628 align:start position:0% with 802.11n in<07:33:37.080> Channel<07:33:37.200> bonding<07:33:37.740> two<07:33:37.978> or<07:33:38.100> more<07:33:38.280> channels 07:33:38.628 --> 07:33:38.638 align:start position:0% in Channel bonding two or more channels 07:33:38.638 --> 07:33:40.730 align:start position:0% in Channel bonding two or more channels adjacent<07:33:39.298> to<07:33:39.420> each<07:33:39.600> other<07:33:39.780> are<07:33:40.200> combined<07:33:40.620> to 07:33:40.730 --> 07:33:40.740 align:start position:0% adjacent to each other are combined to 07:33:40.740 --> 07:33:42.468 align:start position:0% adjacent to each other are combined to increase<07:33:40.920> bandwidth<07:33:41.638> as<07:33:41.820> you<07:33:42.000> can<07:33:42.058> see<07:33:42.180> in<07:33:42.298> the 07:33:42.468 --> 07:33:42.478 align:start position:0% increase bandwidth as you can see in the 07:33:42.478 --> 07:33:44.628 align:start position:0% increase bandwidth as you can see in the figure<07:33:42.600> put<07:33:42.958> there 07:33:44.628 --> 07:33:44.638 align:start position:0% figure put there 07:33:44.638 --> 07:33:47.810 align:start position:0% figure put there benefits<07:33:45.500> 802.11<07:33:46.500> AC<07:33:46.740> benefits<07:33:47.458> because<07:33:47.638> it 07:33:47.810 --> 07:33:47.820 align:start position:0% benefits 802.11 AC benefits because it 07:33:47.820 --> 07:33:51.048 align:start position:0% benefits 802.11 AC benefits because it supports<07:33:48.120> the<07:33:48.298> following<07:33:48.600> channels<07:33:49.200> 2040 07:33:51.048 --> 07:33:51.058 align:start position:0% supports the following channels 2040 07:33:51.058 --> 07:33:54.010 align:start position:0% supports the following channels 2040 80<07:33:51.478> megahertz 07:33:54.010 --> 07:33:54.020 align:start position:0% 80 megahertz 07:33:54.020 --> 07:33:57.230 align:start position:0% 80 megahertz uh<07:33:55.020> although<07:33:55.378> 160<07:33:56.218> megahertz<07:33:56.700> channels<07:33:57.180> are 07:33:57.230 --> 07:33:57.240 align:start position:0% uh although 160 megahertz channels are 07:33:57.240 --> 07:33:59.150 align:start position:0% uh although 160 megahertz channels are supported<07:33:57.718> as<07:33:57.958> an<07:33:58.138> option<07:33:58.440> is<07:33:58.860> its 07:33:59.150 --> 07:33:59.160 align:start position:0% supported as an option is its 07:33:59.160 --> 07:34:01.250 align:start position:0% supported as an option is its availability<07:33:59.458> depends<07:34:00.058> on<07:34:00.298> your<07:34:00.600> geography 07:34:01.250 --> 07:34:01.260 align:start position:0% availability depends on your geography 07:34:01.260 --> 07:34:03.170 align:start position:0% availability depends on your geography Where<07:34:01.680> You<07:34:01.920> Are 07:34:03.170 --> 07:34:03.180 align:start position:0% Where You Are 07:34:03.180 --> 07:34:04.968 align:start position:0% Where You Are well<07:34:03.660> I<07:34:03.840> just<07:34:03.900> had<07:34:04.080> a<07:34:04.200> bandwidth<07:34:04.620> increases 07:34:04.968 --> 07:34:04.978 align:start position:0% well I just had a bandwidth increases 07:34:04.978 --> 07:34:07.368 align:start position:0% well I just had a bandwidth increases the<07:34:05.218> data<07:34:05.580> rates<07:34:05.760> so 07:34:07.368 --> 07:34:07.378 align:start position:0% the data rates so 07:34:07.378 --> 07:34:09.650 align:start position:0% the data rates so um 11ac<07:34:08.040> uses<07:34:08.520> eight<07:34:08.700> spatial<07:34:09.120> streams<07:34:09.478> and 07:34:09.650 --> 07:34:09.660 align:start position:0% um 11ac uses eight spatial streams and 07:34:09.660 --> 07:34:12.650 align:start position:0% um 11ac uses eight spatial streams and 160<07:34:10.500> megahertz<07:34:11.040> bandwidth 07:34:12.650 --> 07:34:12.660 align:start position:0% 160 megahertz bandwidth 07:34:12.660 --> 07:34:16.310 align:start position:0% 160 megahertz bandwidth to<07:34:13.080> achieve<07:34:13.378> a<07:34:13.500> maximum<07:34:13.860> data<07:34:14.280> rate<07:34:14.458> of<07:34:15.320> 6.933 07:34:16.310 --> 07:34:16.320 align:start position:0% to achieve a maximum data rate of 6.933 07:34:16.320 --> 07:34:18.350 align:start position:0% to achieve a maximum data rate of 6.933 gig 07:34:18.350 --> 07:34:18.360 align:start position:0% gig 07:34:18.360 --> 07:34:20.868 align:start position:0% gig uh<07:34:18.780> data<07:34:19.200> rates<07:34:19.440> vary<07:34:19.860> on<07:34:20.218> the<07:34:20.340> following<07:34:20.638> for 07:34:20.868 --> 07:34:20.878 align:start position:0% uh data rates vary on the following for 07:34:20.878 --> 07:34:23.390 align:start position:0% uh data rates vary on the following for 11ac<07:34:21.600> you're<07:34:22.200> given<07:34:22.500> bandwidth<07:34:23.100> and<07:34:23.218> the 07:34:23.390 --> 07:34:23.400 align:start position:0% 11ac you're given bandwidth and the 07:34:23.400 --> 07:34:26.510 align:start position:0% 11ac you're given bandwidth and the number<07:34:23.458> of<07:34:23.580> spatial<07:34:24.058> streams<07:34:24.478> used 07:34:26.510 --> 07:34:26.520 align:start position:0% number of spatial streams used 07:34:26.520 --> 07:34:29.570 align:start position:0% number of spatial streams used probably<07:34:27.000> worth<07:34:27.840> um<07:34:27.900> writing<07:34:28.440> out<07:34:28.558> this 07:34:29.570 --> 07:34:29.580 align:start position:0% probably worth um writing out this 07:34:29.580 --> 07:34:31.010 align:start position:0% probably worth um writing out this um 07:34:31.010 --> 07:34:31.020 align:start position:0% um 07:34:31.020 --> 07:34:33.590 align:start position:0% um table<07:34:31.558> here<07:34:31.978> if<07:34:32.638> you<07:34:32.760> want<07:34:33.180> the<07:34:33.360> information 07:34:33.590 --> 07:34:33.600 align:start position:0% table here if you want the information 07:34:33.600 --> 07:34:36.788 align:start position:0% table here if you want the information or<07:34:34.378> you<07:34:34.500> can<07:34:34.620> do<07:34:34.740> a<07:34:34.920> screen<07:34:35.040> capture 07:34:36.788 --> 07:34:36.798 align:start position:0% or you can do a screen capture 07:34:36.798 --> 07:34:39.830 align:start position:0% or you can do a screen capture 802.11<07:34:37.798> AC<07:34:38.280> with<07:34:38.700> one<07:34:38.878> spatial<07:34:39.298> stream<07:34:39.540> and 07:34:39.830 --> 07:34:39.840 align:start position:0% 802.11 AC with one spatial stream and 07:34:39.840 --> 07:34:41.510 align:start position:0% 802.11 AC with one spatial stream and for<07:34:39.958> a<07:34:40.080> bandwidth<07:34:40.440> of<07:34:40.558> 20<07:34:40.740> megahertz<07:34:41.218> can 07:34:41.510 --> 07:34:41.520 align:start position:0% for a bandwidth of 20 megahertz can 07:34:41.520 --> 07:34:43.628 align:start position:0% for a bandwidth of 20 megahertz can ensure<07:34:41.878> either<07:34:42.120> data<07:34:42.600> rate<07:34:42.660> of 07:34:43.628 --> 07:34:43.638 align:start position:0% ensure either data rate of 07:34:43.638 --> 07:34:47.270 align:start position:0% ensure either data rate of 86.7<07:34:44.638> megahertz<07:34:45.540> and<07:34:46.320> so<07:34:46.440> on<07:34:46.620> and<07:34:46.798> so<07:34:46.978> forth 07:34:47.270 --> 07:34:47.280 align:start position:0% 86.7 megahertz and so on and so forth 07:34:47.280 --> 07:34:49.910 align:start position:0% 86.7 megahertz and so on and so forth for<07:34:47.580> the<07:34:47.700> others<07:34:48.600> um<07:34:48.718> their<07:34:49.260> data<07:34:49.860> rate 07:34:49.910 --> 07:34:49.920 align:start position:0% for the others um their data rate 07:34:49.920 --> 07:34:51.948 align:start position:0% for the others um their data rate increases<07:34:50.400> both<07:34:50.700> vertically<07:34:51.240> and 07:34:51.948 --> 07:34:51.958 align:start position:0% increases both vertically and 07:34:51.958 --> 07:34:53.510 align:start position:0% increases both vertically and horizontally 07:34:53.510 --> 07:34:53.520 align:start position:0% horizontally 07:34:53.520 --> 07:34:56.090 align:start position:0% horizontally all<07:34:53.878> right<07:34:54.058> so<07:34:54.180> we've<07:34:54.360> covered<07:34:54.780> NAC<07:34:55.558> Channel 07:34:56.090 --> 07:34:56.100 align:start position:0% all right so we've covered NAC Channel 07:34:56.100 --> 07:34:58.548 align:start position:0% all right so we've covered NAC Channel bonding<07:34:56.760> that's<07:34:57.360> all<07:34:57.600> for<07:34:57.780> now<07:34:57.958> thanks<07:34:58.440> for 07:34:58.548 --> 07:34:58.558 align:start position:0% bonding that's all for now thanks for 07:34:58.558 --> 07:35:02.220 align:start position:0% bonding that's all for now thanks for listening 07:35:02.220 --> 07:35:02.230 align:start position:0% 07:35:02.230 --> 07:35:18.650 align:start position:0% [Music] 07:35:18.650 --> 07:35:18.660 align:start position:0% 07:35:18.660 --> 07:35:21.770 align:start position:0% plug<07:35:19.260> the<07:35:19.558> module<07:35:19.978> 5<07:35:20.340> lesson<07:35:20.820> 6<07:35:21.058> in<07:35:21.478> network 07:35:21.770 --> 07:35:21.780 align:start position:0% plug the module 5 lesson 6 in network 07:35:21.780 --> 07:35:24.708 align:start position:0% plug the module 5 lesson 6 in network segmentation 07:35:24.708 --> 07:35:24.718 align:start position:0% 07:35:24.718 --> 07:35:26.868 align:start position:0% quite<07:35:25.138> a<07:35:25.320> bit<07:35:25.440> to<07:35:25.558> cover<07:35:25.740> and<07:35:26.100> some<07:35:26.458> of<07:35:26.638> this<07:35:26.700> is 07:35:26.868 --> 07:35:26.878 align:start position:0% quite a bit to cover and some of this is 07:35:26.878 --> 07:35:29.990 align:start position:0% quite a bit to cover and some of this is a<07:35:27.058> little<07:35:27.180> bit<07:35:27.360> esoteric<07:35:28.320> to<07:35:28.500> be<07:35:28.680> honest<07:35:28.978> so<07:35:29.940> um 07:35:29.990 --> 07:35:30.000 align:start position:0% a little bit esoteric to be honest so um 07:35:30.000 --> 07:35:32.030 align:start position:0% a little bit esoteric to be honest so um it's<07:35:30.780> conceptual 07:35:32.030 --> 07:35:32.040 align:start position:0% it's conceptual 07:35:32.040 --> 07:35:33.770 align:start position:0% it's conceptual it<07:35:32.520> can<07:35:32.638> be<07:35:32.760> a<07:35:32.878> bit<07:35:32.940> hard<07:35:33.120> to<07:35:33.298> get<07:35:33.478> your<07:35:33.600> head 07:35:33.770 --> 07:35:33.780 align:start position:0% it can be a bit hard to get your head 07:35:33.780 --> 07:35:34.850 align:start position:0% it can be a bit hard to get your head around 07:35:34.850 --> 07:35:34.860 align:start position:0% around 07:35:34.860 --> 07:35:36.650 align:start position:0% around um<07:35:34.920> in<07:35:35.520> that<07:35:35.638> sense 07:35:36.650 --> 07:35:36.660 align:start position:0% um in that sense 07:35:36.660 --> 07:35:39.110 align:start position:0% um in that sense what<07:35:37.138> is<07:35:37.260> Network<07:35:37.500> segmentation<07:35:38.400> what<07:35:38.940> is 07:35:39.110 --> 07:35:39.120 align:start position:0% what is Network segmentation what is 07:35:39.120 --> 07:35:42.468 align:start position:0% what is Network segmentation what is physical<07:35:39.478> segmentation<07:35:40.440> logical 07:35:42.468 --> 07:35:42.478 align:start position:0% physical segmentation logical 07:35:42.478 --> 07:35:45.048 align:start position:0% physical segmentation logical uh<07:35:43.260> the<07:35:43.500> uses<07:35:43.798> why<07:35:44.160> bother 07:35:45.048 --> 07:35:45.058 align:start position:0% uh the uses why bother 07:35:45.058 --> 07:35:47.868 align:start position:0% uh the uses why bother and<07:35:45.840> critical<07:35:46.260> situations<07:35:46.978> so<07:35:47.400> we're<07:35:47.520> hitting 07:35:47.868 --> 07:35:47.878 align:start position:0% and critical situations so we're hitting 07:35:47.878 --> 07:35:51.708 align:start position:0% and critical situations so we're hitting a<07:35:48.540> few<07:35:48.780> the<07:35:49.020> syllabus<07:35:49.558> topics<07:35:50.100> here<07:35:50.520> in<07:35:51.360> the<07:35:51.718> um 07:35:51.708 --> 07:35:51.718 align:start position:0% a few the syllabus topics here in the um 07:35:51.718 --> 07:35:54.708 align:start position:0% a few the syllabus topics here in the um Network<07:35:52.020> plus<07:35:52.320> syllabus<07:35:52.860> so 07:35:54.708 --> 07:35:54.718 align:start position:0% Network plus syllabus so 07:35:54.718 --> 07:35:58.250 align:start position:0% Network plus syllabus so in<07:35:55.320> a<07:35:55.500> sense<07:35:55.680> Network<07:35:56.400> segmentation<07:35:57.298> concerns 07:35:58.250 --> 07:35:58.260 align:start position:0% in a sense Network segmentation concerns 07:35:58.260 --> 07:36:00.410 align:start position:0% in a sense Network segmentation concerns dividing<07:35:58.680> a<07:35:58.860> computer<07:35:59.040> into<07:35:59.400> Network<07:35:59.638> or<07:36:00.180> sub 07:36:00.410 --> 07:36:00.420 align:start position:0% dividing a computer into Network or sub 07:36:00.420 --> 07:36:03.170 align:start position:0% dividing a computer into Network or sub networks<07:36:01.080> not<07:36:01.860> in<07:36:02.040> the<07:36:02.160> sense<07:36:02.340> of 07:36:03.170 --> 07:36:03.180 align:start position:0% networks not in the sense of 07:36:03.180 --> 07:36:04.610 align:start position:0% networks not in the sense of um subnetting 07:36:04.610 --> 07:36:04.620 align:start position:0% um subnetting 07:36:04.620 --> 07:36:07.670 align:start position:0% um subnetting um<07:36:04.740> in<07:36:04.978> the<07:36:05.040> context<07:36:05.340> of<07:36:05.520> Ip<07:36:05.878> addressing<07:36:06.420> but 07:36:07.670 --> 07:36:07.680 align:start position:0% um in the context of Ip addressing but 07:36:07.680 --> 07:36:10.850 align:start position:0% um in the context of Ip addressing but um dividing<07:36:08.340> our<07:36:08.580> network<07:36:08.760> down 07:36:10.850 --> 07:36:10.860 align:start position:0% um dividing our network down 07:36:10.860 --> 07:36:14.448 align:start position:0% um dividing our network down so<07:36:11.700> each<07:36:12.540> portion<07:36:13.020> of<07:36:13.200> the<07:36:13.378> network<07:36:13.558> is<07:36:14.218> called 07:36:14.448 --> 07:36:14.458 align:start position:0% so each portion of the network is called 07:36:14.458 --> 07:36:16.190 align:start position:0% so each portion of the network is called a<07:36:14.638> network<07:36:14.878> segment 07:36:16.190 --> 07:36:16.200 align:start position:0% a network segment 07:36:16.200 --> 07:36:18.048 align:start position:0% a network segment it<07:36:16.680> can<07:36:16.860> be<07:36:16.978> characterized<07:36:17.580> by<07:36:17.760> a<07:36:17.878> physical 07:36:18.048 --> 07:36:18.058 align:start position:0% it can be characterized by a physical 07:36:18.058 --> 07:36:19.430 align:start position:0% it can be characterized by a physical boundary 07:36:19.430 --> 07:36:19.440 align:start position:0% boundary 07:36:19.440 --> 07:36:22.430 align:start position:0% boundary or<07:36:20.100> logical<07:36:20.520> So<07:36:21.000> Physical<07:36:21.240> something<07:36:21.660> you<07:36:22.200> can 07:36:22.430 --> 07:36:22.440 align:start position:0% or logical So Physical something you can 07:36:22.440 --> 07:36:24.770 align:start position:0% or logical So Physical something you can see<07:36:22.680> logical<07:36:23.580> something<07:36:24.000> that<07:36:24.360> the<07:36:24.540> network 07:36:24.770 --> 07:36:24.780 align:start position:0% see logical something that the network 07:36:24.780 --> 07:36:27.410 align:start position:0% see logical something that the network can<07:36:25.500> see<07:36:25.680> but<07:36:26.340> you<07:36:26.580> couldn't<07:36:26.700> see<07:36:26.940> physically 07:36:27.410 --> 07:36:27.420 align:start position:0% can see but you couldn't see physically 07:36:27.420 --> 07:36:29.270 align:start position:0% can see but you couldn't see physically you<07:36:27.660> would<07:36:27.840> then<07:36:28.020> have<07:36:28.500> to<07:36:28.680> log<07:36:28.798> in<07:36:28.978> and<07:36:29.160> check 07:36:29.270 --> 07:36:29.280 align:start position:0% you would then have to log in and check 07:36:29.280 --> 07:36:31.010 align:start position:0% you would then have to log in and check the<07:36:29.458> configurations 07:36:31.010 --> 07:36:31.020 align:start position:0% the configurations 07:36:31.020 --> 07:36:32.810 align:start position:0% the configurations so<07:36:31.378> physical<07:36:31.620> or<07:36:32.040> logical<07:36:32.340> boundary 07:36:32.810 --> 07:36:32.820 align:start position:0% so physical or logical boundary 07:36:32.820 --> 07:36:36.048 align:start position:0% so physical or logical boundary separates<07:36:33.360> various<07:36:34.020> Network<07:36:34.860> segments<07:36:35.638> from 07:36:36.048 --> 07:36:36.058 align:start position:0% separates various Network segments from 07:36:36.058 --> 07:36:38.330 align:start position:0% separates various Network segments from one<07:36:36.780> another 07:36:38.330 --> 07:36:38.340 align:start position:0% one another 07:36:38.340 --> 07:36:41.390 align:start position:0% one another physical<07:36:38.820> is<07:36:39.180> a<07:36:39.298> bit<07:36:39.420> easier<07:36:39.780> the<07:36:40.558> computer<07:36:40.798> is 07:36:41.390 --> 07:36:41.400 align:start position:0% physical is a bit easier the computer is 07:36:41.400 --> 07:36:43.430 align:start position:0% physical is a bit easier the computer is divided<07:36:41.820> into<07:36:41.940> segments<07:36:42.540> for<07:36:43.020> example<07:36:43.260> with 07:36:43.430 --> 07:36:43.440 align:start position:0% divided into segments for example with 07:36:43.440 --> 07:36:45.010 align:start position:0% divided into segments for example with switches 07:36:45.010 --> 07:36:45.020 align:start position:0% switches 07:36:45.020 --> 07:36:48.530 align:start position:0% switches routers<07:36:46.020> a<07:36:46.620> group<07:36:46.920> of<07:36:47.160> physical<07:36:47.520> access<07:36:47.878> and 07:36:48.530 --> 07:36:48.540 align:start position:0% routers a group of physical access and 07:36:48.540 --> 07:36:50.990 align:start position:0% routers a group of physical access and assets<07:36:49.020> is<07:36:49.680> part<07:36:49.860> of<07:36:50.040> a<07:36:50.280> specific<07:36:50.580> Network 07:36:50.990 --> 07:36:51.000 align:start position:0% assets is part of a specific Network 07:36:51.000 --> 07:36:52.310 align:start position:0% assets is part of a specific Network segment 07:36:52.310 --> 07:36:52.320 align:start position:0% segment 07:36:52.320 --> 07:36:54.948 align:start position:0% segment so<07:36:53.160> a<07:36:53.520> bit<07:36:53.700> harder<07:36:54.058> to<07:36:54.180> do<07:36:54.298> with<07:36:54.478> switches 07:36:54.948 --> 07:36:54.958 align:start position:0% so a bit harder to do with switches 07:36:54.958 --> 07:36:57.410 align:start position:0% so a bit harder to do with switches because<07:36:55.378> you<07:36:55.920> would<07:36:56.160> normally<07:36:56.760> needed<07:36:57.180> to<07:36:57.298> add 07:36:57.410 --> 07:36:57.420 align:start position:0% because you would normally needed to add 07:36:57.420 --> 07:36:59.150 align:start position:0% because you would normally needed to add a<07:36:57.660> configuration<07:36:58.138> because<07:36:58.378> switches<07:36:58.978> are 07:36:59.150 --> 07:36:59.160 align:start position:0% a configuration because switches are 07:36:59.160 --> 07:37:02.690 align:start position:0% a configuration because switches are designed<07:37:00.000> to<07:37:00.478> broadcast<07:37:00.740> to<07:37:01.740> other 07:37:02.690 --> 07:37:02.700 align:start position:0% designed to broadcast to other 07:37:02.700 --> 07:37:04.788 align:start position:0% designed to broadcast to other um<07:37:02.760> parts<07:37:03.058> of<07:37:03.240> the<07:37:03.360> network<07:37:03.600> if<07:37:04.500> it<07:37:04.620> doesn't 07:37:04.788 --> 07:37:04.798 align:start position:0% um parts of the network if it doesn't 07:37:04.798 --> 07:37:06.468 align:start position:0% um parts of the network if it doesn't know<07:37:05.100> where<07:37:05.458> that<07:37:05.638> part<07:37:05.820> of<07:37:05.940> the<07:37:06.058> network<07:37:06.180> is 07:37:06.468 --> 07:37:06.478 align:start position:0% know where that part of the network is 07:37:06.478 --> 07:37:08.448 align:start position:0% know where that part of the network is or<07:37:06.718> particularly<07:37:07.080> device 07:37:08.448 --> 07:37:08.458 align:start position:0% or particularly device 07:37:08.458 --> 07:37:11.150 align:start position:0% or particularly device whereas<07:37:08.940> routers<07:37:09.240> do<07:37:09.420> the<07:37:09.600> opposite 07:37:11.150 --> 07:37:11.160 align:start position:0% whereas routers do the opposite 07:37:11.160 --> 07:37:14.208 align:start position:0% whereas routers do the opposite computer<07:37:12.000> network<07:37:12.420> is<07:37:12.900> logically 07:37:14.208 --> 07:37:14.218 align:start position:0% computer network is logically 07:37:14.218 --> 07:37:14.930 align:start position:0% computer network is logically um 07:37:14.930 --> 07:37:14.940 align:start position:0% um 07:37:14.940 --> 07:37:17.208 align:start position:0% um virtually<07:37:15.900> divided<07:37:16.440> into<07:37:16.500> Network<07:37:16.740> segment 07:37:17.208 --> 07:37:17.218 align:start position:0% virtually divided into Network segment 07:37:17.218 --> 07:37:19.010 align:start position:0% virtually divided into Network segment so<07:37:17.520> this<07:37:17.700> is<07:37:17.820> uh<07:37:18.180> from<07:37:18.478> The<07:37:18.600> Logical 07:37:19.010 --> 07:37:19.020 align:start position:0% so this is uh from The Logical 07:37:19.020 --> 07:37:21.468 align:start position:0% so this is uh from The Logical standpoint<07:37:19.978> so<07:37:20.638> we<07:37:20.760> could<07:37:20.940> do<07:37:21.120> it<07:37:21.240> with 07:37:21.468 --> 07:37:21.478 align:start position:0% standpoint so we could do it with 07:37:21.478 --> 07:37:23.690 align:start position:0% standpoint so we could do it with virtual<07:37:21.900> lands<07:37:22.320> or<07:37:22.440> vlans 07:37:23.690 --> 07:37:23.700 align:start position:0% virtual lands or vlans 07:37:23.700 --> 07:37:25.850 align:start position:0% virtual lands or vlans virtual<07:37:24.540> segmentation<07:37:25.138> is<07:37:25.440> done<07:37:25.620> or 07:37:25.850 --> 07:37:25.860 align:start position:0% virtual segmentation is done or 07:37:25.860 --> 07:37:27.048 align:start position:0% virtual segmentation is done or different<07:37:26.100> connections<07:37:26.580> or<07:37:26.760> the<07:37:26.940> same 07:37:27.048 --> 07:37:27.058 align:start position:0% different connections or the same 07:37:27.058 --> 07:37:29.090 align:start position:0% different connections or the same physical<07:37:27.298> switch<07:37:27.780> so<07:37:28.440> you<07:37:28.620> can<07:37:28.680> have<07:37:28.860> 10 07:37:29.090 --> 07:37:29.100 align:start position:0% physical switch so you can have 10 07:37:29.100 --> 07:37:32.628 align:start position:0% physical switch so you can have 10 switch<07:37:29.520> ports<07:37:30.240> and<07:37:31.200> the<07:37:31.740> first<07:37:31.920> five<07:37:32.160> ports 07:37:32.628 --> 07:37:32.638 align:start position:0% switch ports and the first five ports 07:37:32.638 --> 07:37:34.430 align:start position:0% switch ports and the first five ports are<07:37:32.820> in<07:37:33.000> one<07:37:33.298> logical<07:37:33.840> part<07:37:34.080> of<07:37:34.200> the<07:37:34.320> network 07:37:34.430 --> 07:37:34.440 align:start position:0% are in one logical part of the network 07:37:34.440 --> 07:37:37.670 align:start position:0% are in one logical part of the network in<07:37:34.920> one<07:37:35.100> VLAN<07:37:35.580> VLAN<07:37:36.058> 10<07:37:36.240> for<07:37:36.478> example<07:37:36.780> and<07:37:37.500> the 07:37:37.670 --> 07:37:37.680 align:start position:0% in one VLAN VLAN 10 for example and the 07:37:37.680 --> 07:37:40.250 align:start position:0% in one VLAN VLAN 10 for example and the other<07:37:37.740> five<07:37:37.978> in<07:37:38.218> VLAN<07:37:38.638> 20.<07:37:39.780> and<07:37:40.020> you<07:37:40.138> could 07:37:40.250 --> 07:37:40.260 align:start position:0% other five in VLAN 20. and you could 07:37:40.260 --> 07:37:42.890 align:start position:0% other five in VLAN 20. and you could have<07:37:40.378> multiple<07:37:40.740> vlans<07:37:41.280> depending<07:37:41.820> on<07:37:42.120> your 07:37:42.890 --> 07:37:42.900 align:start position:0% have multiple vlans depending on your 07:37:42.900 --> 07:37:44.750 align:start position:0% have multiple vlans depending on your capabilities<07:37:43.500> or<07:37:43.860> whatever<07:37:44.040> switch<07:37:44.458> you're 07:37:44.750 --> 07:37:44.760 align:start position:0% capabilities or whatever switch you're 07:37:44.760 --> 07:37:46.368 align:start position:0% capabilities or whatever switch you're using 07:37:46.368 --> 07:37:46.378 align:start position:0% using 07:37:46.378 --> 07:37:48.830 align:start position:0% using through<07:37:47.040> through<07:37:47.700> Network<07:37:48.000> segments<07:37:48.660> are 07:37:48.830 --> 07:37:48.840 align:start position:0% through through Network segments are 07:37:48.840 --> 07:37:50.990 align:start position:0% through through Network segments are isolated<07:37:49.260> although<07:37:49.978> secure<07:37:50.400> communication 07:37:50.990 --> 07:37:51.000 align:start position:0% isolated although secure communication 07:37:51.000 --> 07:37:53.570 align:start position:0% isolated although secure communication can<07:37:51.420> be<07:37:51.600> established<07:37:52.020> between<07:37:52.378> them<07:37:53.160> to<07:37:53.340> share 07:37:53.570 --> 07:37:53.580 align:start position:0% can be established between them to share 07:37:53.580 --> 07:37:55.670 align:start position:0% can be established between them to share network<07:37:53.760> resources<07:37:54.478> we<07:37:54.958> cover<07:37:55.200> that<07:37:55.440> with 07:37:55.670 --> 07:37:55.680 align:start position:0% network resources we cover that with 07:37:55.680 --> 07:37:58.250 align:start position:0% network resources we cover that with security<07:37:55.920> and<07:37:56.760> elsewhere<07:37:57.298> you<07:37:57.958> can<07:37:58.138> actually 07:37:58.250 --> 07:37:58.260 align:start position:0% security and elsewhere you can actually 07:37:58.260 --> 07:38:00.948 align:start position:0% security and elsewhere you can actually have<07:37:58.680> an<07:37:59.100> internal<07:37:59.638> and<07:37:59.760> external<07:38:00.360> network 07:38:00.948 --> 07:38:00.958 align:start position:0% have an internal and external network 07:38:00.958 --> 07:38:03.890 align:start position:0% have an internal and external network security<07:38:01.440> it<07:38:02.280> isn't<07:38:02.520> just<07:38:02.638> for<07:38:02.878> example<07:38:03.120> vpns 07:38:03.890 --> 07:38:03.900 align:start position:0% security it isn't just for example vpns 07:38:03.900 --> 07:38:06.110 align:start position:0% security it isn't just for example vpns connecting<07:38:04.378> and<07:38:05.218> through<07:38:05.520> from<07:38:05.878> remote 07:38:06.110 --> 07:38:06.120 align:start position:0% connecting and through from remote 07:38:06.120 --> 07:38:07.548 align:start position:0% connecting and through from remote offices 07:38:07.548 --> 07:38:07.558 align:start position:0% offices 07:38:07.558 --> 07:38:11.208 align:start position:0% offices so<07:38:08.340> why<07:38:08.580> would<07:38:08.760> you<07:38:08.878> bother<07:38:09.500> in<07:38:10.500> a<07:38:10.860> sense<07:38:10.978> it 07:38:11.208 --> 07:38:11.218 align:start position:0% so why would you bother in a sense it 07:38:11.218 --> 07:38:13.850 align:start position:0% so why would you bother in a sense it enhances<07:38:11.760> the<07:38:11.940> security<07:38:12.180> of<07:38:12.540> the<07:38:12.660> network<07:38:12.860> you 07:38:13.850 --> 07:38:13.860 align:start position:0% enhances the security of the network you 07:38:13.860 --> 07:38:15.830 align:start position:0% enhances the security of the network you can<07:38:13.978> isolate<07:38:14.520> critical<07:38:15.058> parts<07:38:15.478> of<07:38:15.780> your 07:38:15.830 --> 07:38:15.840 align:start position:0% can isolate critical parts of your 07:38:15.840 --> 07:38:18.350 align:start position:0% can isolate critical parts of your infrastructure<07:38:16.558> from<07:38:17.400> an<07:38:17.638> authorized<07:38:18.120> access 07:38:18.350 --> 07:38:18.360 align:start position:0% infrastructure from an authorized access 07:38:18.360 --> 07:38:20.810 align:start position:0% infrastructure from an authorized access for<07:38:19.320> example<07:38:19.558> if<07:38:19.860> you've<07:38:20.040> got<07:38:20.218> a<07:38:20.580> special 07:38:20.810 --> 07:38:20.820 align:start position:0% for example if you've got a special 07:38:20.820 --> 07:38:23.448 align:start position:0% for example if you've got a special service<07:38:21.298> and<07:38:21.900> server<07:38:22.378> you<07:38:23.040> can<07:38:23.100> restrict 07:38:23.448 --> 07:38:23.458 align:start position:0% service and server you can restrict 07:38:23.458 --> 07:38:26.628 align:start position:0% service and server you can restrict access<07:38:23.760> to<07:38:24.120> the<07:38:24.660> um<07:38:24.660> users<07:38:25.200> don't<07:38:25.978> access<07:38:26.280> it 07:38:26.628 --> 07:38:26.638 align:start position:0% access to the um users don't access it 07:38:26.638 --> 07:38:28.910 align:start position:0% access to the um users don't access it and<07:38:27.000> they<07:38:27.180> don't<07:38:27.360> have<07:38:27.540> direct<07:38:27.780> access<07:38:28.200> so 07:38:28.910 --> 07:38:28.920 align:start position:0% and they don't have direct access so 07:38:28.920 --> 07:38:30.468 align:start position:0% and they don't have direct access so they'll<07:38:29.218> be<07:38:29.340> in<07:38:29.458> a<07:38:29.638> different<07:38:29.760> VLAN<07:38:30.298> for 07:38:30.468 --> 07:38:30.478 align:start position:0% they'll be in a different VLAN for 07:38:30.478 --> 07:38:32.628 align:start position:0% they'll be in a different VLAN for example<07:38:30.780> or<07:38:31.200> just<07:38:31.440> in<07:38:31.740> it<07:38:32.040> wouldn't<07:38:32.160> appear<07:38:32.458> on 07:38:32.628 --> 07:38:32.638 align:start position:0% example or just in it wouldn't appear on 07:38:32.638 --> 07:38:35.390 align:start position:0% example or just in it wouldn't appear on the<07:38:32.760> network<07:38:32.958> and<07:38:33.958> you<07:38:34.080> normally<07:38:34.440> or<07:38:34.860> may<07:38:35.160> well 07:38:35.390 --> 07:38:35.400 align:start position:0% the network and you normally or may well 07:38:35.400 --> 07:38:36.708 align:start position:0% the network and you normally or may well have<07:38:35.638> depending<07:38:36.058> on<07:38:36.120> the<07:38:36.298> size<07:38:36.420> of<07:38:36.600> your 07:38:36.708 --> 07:38:36.718 align:start position:0% have depending on the size of your 07:38:36.718 --> 07:38:38.990 align:start position:0% have depending on the size of your network<07:38:36.900> a<07:38:37.740> different<07:38:37.920> team<07:38:38.340> or<07:38:38.760> Department 07:38:38.990 --> 07:38:39.000 align:start position:0% network a different team or Department 07:38:39.000 --> 07:38:42.170 align:start position:0% network a different team or Department managing<07:38:39.780> that<07:38:40.260> part<07:38:40.558> of<07:38:40.680> the<07:38:40.798> network 07:38:42.170 --> 07:38:42.180 align:start position:0% managing that part of the network 07:38:42.180 --> 07:38:44.570 align:start position:0% managing that part of the network it<07:38:42.840> can<07:38:43.020> be<07:38:43.200> used<07:38:43.558> for<07:38:43.740> reducing<07:38:44.218> Network 07:38:44.570 --> 07:38:44.580 align:start position:0% it can be used for reducing Network 07:38:44.580 --> 07:38:46.730 align:start position:0% it can be used for reducing Network congestion<07:38:45.478> so<07:38:45.718> you're<07:38:45.958> dedicating<07:38:46.378> certain 07:38:46.730 --> 07:38:46.740 align:start position:0% congestion so you're dedicating certain 07:38:46.740 --> 07:38:49.070 align:start position:0% congestion so you're dedicating certain parts<07:38:47.040> of<07:38:47.218> bandwidth<07:38:47.878> for<07:38:48.420> certain<07:38:48.600> segments 07:38:49.070 --> 07:38:49.080 align:start position:0% parts of bandwidth for certain segments 07:38:49.080 --> 07:38:51.048 align:start position:0% parts of bandwidth for certain segments of<07:38:49.200> the<07:38:49.320> network<07:38:49.500> and<07:38:50.218> you<07:38:50.340> can<07:38:50.458> even<07:38:50.580> have<07:38:50.878> a 07:38:51.048 --> 07:38:51.058 align:start position:0% of the network and you can even have a 07:38:51.058 --> 07:38:54.110 align:start position:0% of the network and you can even have a high-speed<07:38:51.660> department<07:38:52.218> for<07:38:53.218> example 07:38:54.110 --> 07:38:54.120 align:start position:0% high-speed department for example 07:38:54.120 --> 07:38:55.610 align:start position:0% high-speed department for example um the<07:38:54.298> company<07:38:54.420> I<07:38:54.718> used<07:38:54.900> to<07:38:54.958> work<07:38:55.080> at<07:38:55.260> we<07:38:55.440> had 07:38:55.610 --> 07:38:55.620 align:start position:0% um the company I used to work at we had 07:38:55.620 --> 07:38:58.310 align:start position:0% um the company I used to work at we had a<07:38:55.798> design<07:38:55.978> team<07:38:56.400> who<07:38:57.058> all<07:38:57.240> used 07:38:58.310 --> 07:38:58.320 align:start position:0% a design team who all used 07:38:58.320 --> 07:39:02.030 align:start position:0% a design team who all used um<07:38:58.920> high<07:38:59.580> speed<07:38:59.878> high<07:39:00.600> resolution<07:39:01.020> files<07:39:01.798> and 07:39:02.030 --> 07:39:02.040 align:start position:0% um high speed high resolution files and 07:39:02.040 --> 07:39:05.270 align:start position:0% um high speed high resolution files and graphics<07:39:02.520> and<07:39:03.000> it<07:39:03.540> um<07:39:03.540> they<07:39:03.900> needed 07:39:05.270 --> 07:39:05.280 align:start position:0% graphics and it um they needed 07:39:05.280 --> 07:39:06.770 align:start position:0% graphics and it um they needed um a<07:39:05.520> fast<07:39:05.700> connection<07:39:05.940> so<07:39:06.298> they<07:39:06.478> had<07:39:06.600> their 07:39:06.770 --> 07:39:06.780 align:start position:0% um a fast connection so they had their 07:39:06.780 --> 07:39:09.230 align:start position:0% um a fast connection so they had their own<07:39:06.900> logical<07:39:07.260> segment 07:39:09.230 --> 07:39:09.240 align:start position:0% own logical segment 07:39:09.240 --> 07:39:11.628 align:start position:0% own logical segment and<07:39:09.900> you<07:39:10.080> could<07:39:10.200> also<07:39:10.440> limit<07:39:10.620> traffic<07:39:11.040> as<07:39:11.458> I 07:39:11.628 --> 07:39:11.638 align:start position:0% and you could also limit traffic as I 07:39:11.638 --> 07:39:13.610 align:start position:0% and you could also limit traffic as I said<07:39:11.760> faster<07:39:12.360> connection<07:39:12.660> for<07:39:13.020> some<07:39:13.200> slower 07:39:13.610 --> 07:39:13.620 align:start position:0% said faster connection for some slower 07:39:13.620 --> 07:39:15.830 align:start position:0% said faster connection for some slower for<07:39:13.860> others<07:39:14.218> and<07:39:14.700> the<07:39:14.820> available<07:39:14.940> bandwidth 07:39:15.830 --> 07:39:15.840 align:start position:0% for others and the available bandwidth 07:39:15.840 --> 07:39:19.788 align:start position:0% for others and the available bandwidth is<07:39:16.260> um<07:39:16.260> increased<07:39:16.798> or<07:39:16.978> reduced<07:39:17.458> accordingly 07:39:19.788 --> 07:39:19.798 align:start position:0% is um increased or reduced accordingly 07:39:19.798 --> 07:39:22.850 align:start position:0% is um increased or reduced accordingly uh<07:39:20.760> also<07:39:21.180> useful<07:39:21.478> for<07:39:21.780> load<07:39:22.080> balancing<07:39:22.500> you 07:39:22.850 --> 07:39:22.860 align:start position:0% uh also useful for load balancing you 07:39:22.860 --> 07:39:25.310 align:start position:0% uh also useful for load balancing you can<07:39:22.920> distribute<07:39:23.400> the<07:39:23.580> traffic<07:39:23.878> a<07:39:24.600> load<07:39:24.958> based 07:39:25.310 --> 07:39:25.320 align:start position:0% can distribute the traffic a load based 07:39:25.320 --> 07:39:26.270 align:start position:0% can distribute the traffic a load based on<07:39:25.558> the 07:39:26.270 --> 07:39:26.280 align:start position:0% on the 07:39:26.280 --> 07:39:29.628 align:start position:0% on the for<07:39:26.820> the<07:39:27.000> network<07:39:27.200> certain<07:39:28.200> devices<07:39:28.638> certain 07:39:29.628 --> 07:39:29.638 align:start position:0% for the network certain devices certain 07:39:29.638 --> 07:39:31.250 align:start position:0% for the network certain devices certain devices<07:39:30.000> can<07:39:30.478> be<07:39:30.600> placed<07:39:30.900> in<07:39:31.080> certain 07:39:31.250 --> 07:39:31.260 align:start position:0% devices can be placed in certain 07:39:31.260 --> 07:39:33.250 align:start position:0% devices can be placed in certain segments 07:39:33.250 --> 07:39:33.260 align:start position:0% segments 07:39:33.260 --> 07:39:35.990 align:start position:0% segments and<07:39:34.260> network<07:39:34.558> segmentation<07:39:35.280> is<07:39:35.520> also<07:39:35.820> done 07:39:35.990 --> 07:39:36.000 align:start position:0% and network segmentation is also done 07:39:36.000 --> 07:39:38.570 align:start position:0% and network segmentation is also done for<07:39:36.298> the<07:39:36.718> PCI<07:39:37.260> the<07:39:37.440> payment<07:39:37.680> card<07:39:37.978> industry 07:39:38.570 --> 07:39:38.580 align:start position:0% for the PCI the payment card industry 07:39:38.580 --> 07:39:40.910 align:start position:0% for the PCI the payment card industry that's<07:39:39.298> different<07:39:39.478> from<07:39:39.840> the<07:39:40.080> PCI<07:39:40.558> bus 07:39:40.910 --> 07:39:40.920 align:start position:0% that's different from the PCI bus 07:39:40.920 --> 07:39:43.730 align:start position:0% that's different from the PCI bus technology<07:39:41.520> which<07:39:41.878> we<07:39:42.058> discuss<07:39:42.420> elsewhere 07:39:43.730 --> 07:39:43.740 align:start position:0% technology which we discuss elsewhere 07:39:43.740 --> 07:39:45.770 align:start position:0% technology which we discuss elsewhere the<07:39:44.100> PCA<07:39:44.400> compliance<07:39:45.000> standards<07:39:45.540> were 07:39:45.770 --> 07:39:45.780 align:start position:0% the PCA compliance standards were 07:39:45.780 --> 07:39:48.468 align:start position:0% the PCA compliance standards were created<07:39:46.138> by<07:39:46.620> Major<07:39:46.920> card<07:39:47.218> issuers<07:39:47.820> and<07:39:48.360> you 07:39:48.468 --> 07:39:48.478 align:start position:0% created by Major card issuers and you 07:39:48.478 --> 07:39:50.390 align:start position:0% created by Major card issuers and you may<07:39:48.660> come<07:39:48.840> across<07:39:49.200> it<07:39:49.320> if<07:39:49.558> you<07:39:49.798> have<07:39:49.920> to<07:39:50.100> take 07:39:50.390 --> 07:39:50.400 align:start position:0% may come across it if you have to take 07:39:50.400 --> 07:39:53.690 align:start position:0% may come across it if you have to take online<07:39:51.180> payments 07:39:53.690 --> 07:39:53.700 align:start position:0% online payments 07:39:53.700 --> 07:39:55.490 align:start position:0% online payments um depending<07:39:54.240> on<07:39:54.420> the<07:39:54.600> processor<07:39:55.080> you<07:39:55.260> use 07:39:55.490 --> 07:39:55.500 align:start position:0% um depending on the processor you use 07:39:55.500 --> 07:39:57.830 align:start position:0% um depending on the processor you use even<07:39:55.798> if<07:39:55.978> you've<07:39:56.160> got<07:39:56.280> a<07:39:56.520> small 07:39:57.830 --> 07:39:57.840 align:start position:0% even if you've got a small 07:39:57.840 --> 07:40:01.490 align:start position:0% even if you've got a small um<07:39:57.900> Network<07:39:58.200> for<07:39:58.860> your<07:39:59.100> business<07:39:59.478> or<07:40:00.478> shop<07:40:00.718> you 07:40:01.490 --> 07:40:01.500 align:start position:0% um Network for your business or shop you 07:40:01.500 --> 07:40:03.288 align:start position:0% um Network for your business or shop you um may<07:40:01.740> have<07:40:01.978> to<07:40:02.100> or<07:40:02.340> you<07:40:02.700> will<07:40:02.820> be<07:40:02.940> affected 07:40:03.288 --> 07:40:03.298 align:start position:0% um may have to or you will be affected 07:40:03.298 --> 07:40:05.270 align:start position:0% um may have to or you will be affected by<07:40:03.540> PCR<07:40:03.900> compliance 07:40:05.270 --> 07:40:05.280 align:start position:0% by PCR compliance 07:40:05.280 --> 07:40:06.650 align:start position:0% by PCR compliance so<07:40:05.638> this<07:40:05.760> is<07:40:05.878> to<07:40:06.058> ensure<07:40:06.298> that<07:40:06.420> the<07:40:06.540> payment 07:40:06.650 --> 07:40:06.660 align:start position:0% so this is to ensure that the payment 07:40:06.660 --> 07:40:08.570 align:start position:0% so this is to ensure that the payment transactions<07:40:07.378> are<07:40:07.500> done<07:40:07.740> in<07:40:08.040> a<07:40:08.218> secure 07:40:08.570 --> 07:40:08.580 align:start position:0% transactions are done in a secure 07:40:08.580 --> 07:40:10.490 align:start position:0% transactions are done in a secure environment 07:40:10.490 --> 07:40:10.500 align:start position:0% environment 07:40:10.500 --> 07:40:13.010 align:start position:0% environment if<07:40:10.860> someone<07:40:11.040> processes<07:40:11.760> stores<07:40:12.120> or<07:40:12.420> transmits 07:40:13.010 --> 07:40:13.020 align:start position:0% if someone processes stores or transmits 07:40:13.020 --> 07:40:15.590 align:start position:0% if someone processes stores or transmits credit<07:40:13.138> card<07:40:13.378> information<07:40:14.218> it<07:40:15.120> must<07:40:15.298> comply 07:40:15.590 --> 07:40:15.600 align:start position:0% credit card information it must comply 07:40:15.600 --> 07:40:17.628 align:start position:0% credit card information it must comply with<07:40:15.718> the<07:40:15.958> PCI<07:40:16.378> Data<07:40:16.860> security<07:40:17.040> standard 07:40:17.628 --> 07:40:17.638 align:start position:0% with the PCI Data security standard 07:40:17.638 --> 07:40:20.810 align:start position:0% with the PCI Data security standard which<07:40:17.878> is<07:40:18.058> the<07:40:18.298> DSs 07:40:20.810 --> 07:40:20.820 align:start position:0% which is the DSs 07:40:20.820 --> 07:40:23.208 align:start position:0% which is the DSs this<07:40:21.420> is<07:40:21.540> mandated<07:40:21.958> by<07:40:22.260> Visa<07:40:22.740> Mastercard 07:40:23.208 --> 07:40:23.218 align:start position:0% this is mandated by Visa Mastercard 07:40:23.218 --> 07:40:25.430 align:start position:0% this is mandated by Visa Mastercard American<07:40:23.520> Express<07:40:23.940> discovering<07:40:24.840> JCB 07:40:25.430 --> 07:40:25.440 align:start position:0% American Express discovering JCB 07:40:25.440 --> 07:40:27.350 align:start position:0% American Express discovering JCB obviously<07:40:26.160> because<07:40:26.280> people<07:40:26.638> will<07:40:27.058> try<07:40:27.240> and 07:40:27.350 --> 07:40:27.360 align:start position:0% obviously because people will try and 07:40:27.360 --> 07:40:28.310 align:start position:0% obviously because people will try and capture 07:40:28.310 --> 07:40:28.320 align:start position:0% capture 07:40:28.320 --> 07:40:30.530 align:start position:0% capture and<07:40:28.920> credit<07:40:29.218> card<07:40:29.458> information<07:40:29.700> so<07:40:30.180> it<07:40:30.298> needs 07:40:30.530 --> 07:40:30.540 align:start position:0% and credit card information so it needs 07:40:30.540 --> 07:40:35.448 align:start position:0% and credit card information so it needs to<07:40:30.600> comply<07:40:30.958> with<07:40:31.138> the<07:40:31.378> standards 07:40:35.448 --> 07:40:35.458 align:start position:0% 07:40:35.458 --> 07:40:37.610 align:start position:0% um<07:40:35.520> Network<07:40:35.760> segmentation<07:40:36.600> is<07:40:37.080> actually<07:40:37.378> not 07:40:37.610 --> 07:40:37.620 align:start position:0% um Network segmentation is actually not 07:40:37.620 --> 07:40:40.010 align:start position:0% um Network segmentation is actually not a<07:40:37.860> PCI<07:40:38.340> DSS<07:40:38.700> requirement<07:40:39.298> it's<07:40:39.600> done<07:40:39.840> to 07:40:40.010 --> 07:40:40.020 align:start position:0% a PCI DSS requirement it's done to 07:40:40.020 --> 07:40:41.948 align:start position:0% a PCI DSS requirement it's done to isolate<07:40:40.440> the<07:40:40.558> traffic<07:40:40.740> that<07:40:41.160> stores 07:40:41.948 --> 07:40:41.958 align:start position:0% isolate the traffic that stores 07:40:41.958 --> 07:40:44.090 align:start position:0% isolate the traffic that stores processes<07:40:42.958> or<07:40:43.260> channels<07:40:43.500> emits<07:40:43.920> the<07:40:43.978> card 07:40:44.090 --> 07:40:44.100 align:start position:0% processes or channels emits the card 07:40:44.100 --> 07:40:45.650 align:start position:0% processes or channels emits the card holder<07:40:44.580> information<07:40:44.760> from<07:40:45.240> the<07:40:45.360> rest<07:40:45.420> of<07:40:45.600> the 07:40:45.650 --> 07:40:45.660 align:start position:0% holder information from the rest of the 07:40:45.660 --> 07:40:47.208 align:start position:0% holder information from the rest of the network 07:40:47.208 --> 07:40:47.218 align:start position:0% network 07:40:47.218 --> 07:40:49.070 align:start position:0% network and<07:40:47.700> reduces<07:40:48.240> the<07:40:48.420> scope<07:40:48.600> of<07:40:48.780> the<07:40:48.900> network 07:40:49.070 --> 07:40:49.080 align:start position:0% and reduces the scope of the network 07:40:49.080 --> 07:40:52.250 align:start position:0% and reduces the scope of the network environment<07:40:49.798> subject<07:40:50.340> to<07:40:50.520> PCI<07:40:51.058> compliance<07:40:51.600> if 07:40:52.250 --> 07:40:52.260 align:start position:0% environment subject to PCI compliance if 07:40:52.260 --> 07:40:54.468 align:start position:0% environment subject to PCI compliance if you<07:40:52.378> didn't<07:40:52.558> have<07:40:52.798> your<07:40:53.520> network<07:40:53.638> segmented 07:40:54.468 --> 07:40:54.478 align:start position:0% you didn't have your network segmented 07:40:54.478 --> 07:40:57.350 align:start position:0% you didn't have your network segmented then<07:40:55.138> your<07:40:55.378> entire<07:40:55.740> network<07:40:56.100> would<07:40:57.000> have<07:40:57.240> to 07:40:57.350 --> 07:40:57.360 align:start position:0% then your entire network would have to 07:40:57.360 --> 07:41:00.948 align:start position:0% then your entire network would have to comply<07:40:57.958> with<07:40:58.620> all<07:40:58.798> of<07:40:58.920> the<07:40:59.160> various<07:40:59.458> pcid<07:41:00.298> SS 07:41:00.948 --> 07:41:00.958 align:start position:0% comply with all of the various pcid SS 07:41:00.958 --> 07:41:03.530 align:start position:0% comply with all of the various pcid SS requirements<07:41:01.680> if<07:41:02.520> you<07:41:02.700> segment<07:41:03.000> the<07:41:03.298> card 07:41:03.530 --> 07:41:03.540 align:start position:0% requirements if you segment the card 07:41:03.540 --> 07:41:06.170 align:start position:0% requirements if you segment the card processing<07:41:04.200> and<07:41:04.740> part<07:41:04.860> of<07:41:05.040> your<07:41:05.160> network<07:41:05.400> then 07:41:06.170 --> 07:41:06.180 align:start position:0% processing and part of your network then 07:41:06.180 --> 07:41:07.910 align:start position:0% processing and part of your network then only<07:41:06.420> that<07:41:06.718> part<07:41:06.900> of<07:41:07.020> the<07:41:07.138> network<07:41:07.320> needs<07:41:07.798> to 07:41:07.910 --> 07:41:07.920 align:start position:0% only that part of the network needs to 07:41:07.920 --> 07:41:09.650 align:start position:0% only that part of the network needs to comply<07:41:08.340> so<07:41:08.700> it's<07:41:08.878> going<07:41:09.000> to<07:41:09.058> make<07:41:09.180> your<07:41:09.298> life<07:41:09.478> a 07:41:09.650 --> 07:41:09.660 align:start position:0% comply so it's going to make your life a 07:41:09.660 --> 07:41:11.570 align:start position:0% comply so it's going to make your life a lot<07:41:09.780> easier 07:41:11.570 --> 07:41:11.580 align:start position:0% lot easier 07:41:11.580 --> 07:41:13.490 align:start position:0% lot easier um uses<07:41:12.058> the<07:41:12.298> footprints<07:41:12.780> of<07:41:12.840> a<07:41:13.080> sensitive 07:41:13.490 --> 07:41:13.500 align:start position:0% um uses the footprints of a sensitive 07:41:13.500 --> 07:41:15.530 align:start position:0% um uses the footprints of a sensitive information<07:41:13.798> is<07:41:14.280> confined<07:41:14.820> and<07:41:15.058> this<07:41:15.180> is<07:41:15.298> what 07:41:15.530 --> 07:41:15.540 align:start position:0% information is confined and this is what 07:41:15.540 --> 07:41:17.690 align:start position:0% information is confined and this is what I<07:41:15.718> I<07:41:15.900> mentioned<07:41:16.200> a<07:41:16.378> moment<07:41:16.620> ago<07:41:16.978> and<07:41:17.458> you<07:41:17.580> can 07:41:17.690 --> 07:41:17.700 align:start position:0% I I mentioned a moment ago and you can 07:41:17.700 --> 07:41:19.968 align:start position:0% I I mentioned a moment ago and you can protect<07:41:18.000> it<07:41:18.180> using<07:41:18.600> firewall<07:41:19.080> or<07:41:19.740> your 07:41:19.968 --> 07:41:19.978 align:start position:0% protect it using firewall or your 07:41:19.978 --> 07:41:22.128 align:start position:0% protect it using firewall or your intrusion<07:41:20.520> detection<07:41:21.298> or<07:41:21.718> Protection 07:41:22.128 --> 07:41:22.138 align:start position:0% intrusion detection or Protection 07:41:22.138 --> 07:41:25.190 align:start position:0% intrusion detection or Protection Systems 07:41:25.190 --> 07:41:25.200 align:start position:0% 07:41:25.200 --> 07:41:27.890 align:start position:0% and<07:41:25.620> reduces<07:41:26.040> the<07:41:26.218> audit<07:41:26.580> cost<07:41:26.700> as<07:41:27.000> well 07:41:27.890 --> 07:41:27.900 align:start position:0% and reduces the audit cost as well 07:41:27.900 --> 07:41:29.628 align:start position:0% and reduces the audit cost as well the<07:41:28.260> audit<07:41:28.620> is<07:41:28.680> done<07:41:28.798> for<07:41:28.978> specific<07:41:29.340> Network 07:41:29.628 --> 07:41:29.638 align:start position:0% the audit is done for specific Network 07:41:29.638 --> 07:41:32.208 align:start position:0% the audit is done for specific Network segment<07:41:30.420> as<07:41:31.200> opposed<07:41:31.558> to<07:41:31.620> your<07:41:31.920> entire 07:41:32.208 --> 07:41:32.218 align:start position:0% segment as opposed to your entire 07:41:32.218 --> 07:41:34.310 align:start position:0% segment as opposed to your entire network<07:41:32.520> and<07:41:33.180> again<07:41:33.298> the<07:41:33.600> best<07:41:33.718> example<07:41:34.138> is 07:41:34.310 --> 07:41:34.320 align:start position:0% network and again the best example is 07:41:34.320 --> 07:41:36.048 align:start position:0% network and again the best example is when<07:41:34.680> you're<07:41:34.920> getting<07:41:35.218> audited<07:41:35.760> for<07:41:35.940> the 07:41:36.048 --> 07:41:36.058 align:start position:0% when you're getting audited for the 07:41:36.058 --> 07:41:40.570 align:start position:0% when you're getting audited for the purposes<07:41:36.420> of<07:41:36.718> of<07:41:37.378> PCI<07:41:37.978> compliance 07:41:40.570 --> 07:41:40.580 align:start position:0% purposes of of PCI compliance 07:41:40.580 --> 07:41:44.448 align:start position:0% purposes of of PCI compliance and<07:41:41.580> this<07:41:42.120> is<07:41:42.298> one<07:41:42.540> of<07:41:42.718> the<07:41:43.080> uh<07:41:43.860> topics<07:41:44.218> for 07:41:44.448 --> 07:41:44.458 align:start position:0% and this is one of the uh topics for 07:41:44.458 --> 07:41:46.190 align:start position:0% and this is one of the uh topics for these<07:41:44.638> syllabus<07:41:45.058> actually<07:41:45.240> Network<07:41:45.660> segment 07:41:46.190 --> 07:41:46.200 align:start position:0% these syllabus actually Network segment 07:41:46.200 --> 07:41:48.350 align:start position:0% these syllabus actually Network segment segmentations 07:41:48.350 --> 07:41:48.360 align:start position:0% segmentations 07:41:48.360 --> 07:41:51.048 align:start position:0% segmentations in<07:41:48.958> critical<07:41:49.378> situations<07:41:50.058> numerous 07:41:51.048 --> 07:41:51.058 align:start position:0% in critical situations numerous 07:41:51.058 --> 07:41:52.010 align:start position:0% in critical situations numerous situations<07:41:51.360> where<07:41:51.660> the<07:41:51.840> network 07:41:52.010 --> 07:41:52.020 align:start position:0% situations where the network 07:41:52.020 --> 07:41:54.410 align:start position:0% situations where the network segmentation<07:41:52.798> is<07:41:53.218> critical 07:41:54.410 --> 07:41:54.420 align:start position:0% segmentation is critical 07:41:54.420 --> 07:41:57.770 align:start position:0% segmentation is critical so<07:41:54.900> the<07:41:55.260> scada<07:41:55.920> the<07:41:56.580> supervisory<07:41:57.120> control<07:41:57.478> and 07:41:57.770 --> 07:41:57.780 align:start position:0% so the scada the supervisory control and 07:41:57.780 --> 07:42:01.850 align:start position:0% so the scada the supervisory control and data<07:41:58.580> acquisition<07:41:59.600> and<07:42:00.600> the<07:42:00.840> ICS<07:42:01.378> industrial 07:42:01.850 --> 07:42:01.860 align:start position:0% data acquisition and the ICS industrial 07:42:01.860 --> 07:42:03.948 align:start position:0% data acquisition and the ICS industrial Control<07:42:02.160> Systems<07:42:02.820> so<07:42:03.360> again<07:42:03.540> you'll<07:42:03.840> see 07:42:03.948 --> 07:42:03.958 align:start position:0% Control Systems so again you'll see 07:42:03.958 --> 07:42:05.448 align:start position:0% Control Systems so again you'll see you'll<07:42:04.138> see<07:42:04.260> this<07:42:04.378> on<07:42:04.558> the<07:42:04.680> syllabus<07:42:05.100> when<07:42:05.218> you 07:42:05.448 --> 07:42:05.458 align:start position:0% you'll see this on the syllabus when you 07:42:05.458 --> 07:42:08.150 align:start position:0% you'll see this on the syllabus when you look<07:42:05.638> the<07:42:06.420> ICS<07:42:06.958> refers<07:42:07.260> to<07:42:07.440> several<07:42:07.978> control 07:42:08.150 --> 07:42:08.160 align:start position:0% look the ICS refers to several control 07:42:08.160 --> 07:42:11.090 align:start position:0% look the ICS refers to several control systems<07:42:08.760> that<07:42:09.000> are<07:42:09.120> used<07:42:09.360> in<07:42:09.840> the<07:42:10.138> industry<07:42:10.740> in 07:42:11.090 --> 07:42:11.100 align:start position:0% systems that are used in the industry in 07:42:11.100 --> 07:42:13.610 align:start position:0% systems that are used in the industry in various<07:42:11.458> Industries<07:42:11.958> this<07:42:12.958> is<07:42:13.080> an<07:42:13.260> industrial 07:42:13.610 --> 07:42:13.620 align:start position:0% various Industries this is an industrial 07:42:13.620 --> 07:42:16.788 align:start position:0% various Industries this is an industrial control<07:42:13.860> system<07:42:14.340> so<07:42:15.360> you<07:42:16.200> may<07:42:16.320> not<07:42:16.440> have<07:42:16.620> heard 07:42:16.788 --> 07:42:16.798 align:start position:0% control system so you may not have heard 07:42:16.798 --> 07:42:19.548 align:start position:0% control system so you may not have heard of<07:42:16.978> this<07:42:17.100> or<07:42:17.400> may<07:42:17.580> never<07:42:17.760> come<07:42:18.000> to<07:42:18.180> deal<07:42:18.558> or 07:42:19.548 --> 07:42:19.558 align:start position:0% of this or may never come to deal or 07:42:19.558 --> 07:42:21.110 align:start position:0% of this or may never come to deal or support<07:42:19.798> or<07:42:20.100> manage<07:42:20.400> this<07:42:20.580> unless<07:42:20.940> you're 07:42:21.110 --> 07:42:21.120 align:start position:0% support or manage this unless you're 07:42:21.120 --> 07:42:23.510 align:start position:0% support or manage this unless you're part<07:42:21.360> of<07:42:21.540> the<07:42:21.840> industrial<07:42:22.680> Network 07:42:23.510 --> 07:42:23.520 align:start position:0% part of the industrial Network 07:42:23.520 --> 07:42:25.368 align:start position:0% part of the industrial Network infrastructure 07:42:25.368 --> 07:42:25.378 align:start position:0% infrastructure 07:42:25.378 --> 07:42:28.010 align:start position:0% infrastructure thank<07:42:25.558> you 07:42:28.010 --> 07:42:28.020 align:start position:0% 07:42:28.020 --> 07:42:30.170 align:start position:0% and<07:42:28.798> the<07:42:28.978> additional<07:42:29.340> facilities<07:42:29.760> are 07:42:30.170 --> 07:42:30.180 align:start position:0% and the additional facilities are 07:42:30.180 --> 07:42:32.270 align:start position:0% and the additional facilities are electrical<07:42:30.718> electrical<07:42:31.378> power<07:42:31.558> grids<07:42:32.040> water 07:42:32.270 --> 07:42:32.280 align:start position:0% electrical electrical power grids water 07:42:32.280 --> 07:42:35.030 align:start position:0% electrical electrical power grids water distribution<07:42:33.000> oil<07:42:33.478> natural<07:42:34.138> gas<07:42:34.440> pipeline 07:42:35.030 --> 07:42:35.040 align:start position:0% distribution oil natural gas pipeline 07:42:35.040 --> 07:42:36.350 align:start position:0% distribution oil natural gas pipeline systems 07:42:36.350 --> 07:42:36.360 align:start position:0% systems 07:42:36.360 --> 07:42:38.270 align:start position:0% systems and<07:42:36.900> they're<07:42:37.080> dependent<07:42:37.500> on<07:42:37.680> electrical 07:42:38.270 --> 07:42:38.280 align:start position:0% and they're dependent on electrical 07:42:38.280 --> 07:42:41.030 align:start position:0% and they're dependent on electrical hydraulic<07:42:38.940> and<07:42:39.240> mechanical<07:42:39.718> equipment 07:42:41.030 --> 07:42:41.040 align:start position:0% hydraulic and mechanical equipment 07:42:41.040 --> 07:42:42.830 align:start position:0% hydraulic and mechanical equipment this<07:42:41.520> equipment<07:42:41.820> is<07:42:42.058> all<07:42:42.298> monitored<07:42:42.660> by 07:42:42.830 --> 07:42:42.840 align:start position:0% this equipment is all monitored by 07:42:42.840 --> 07:42:44.810 align:start position:0% this equipment is all monitored by sensors<07:42:43.378> that<07:42:43.680> transform<07:42:44.218> the<07:42:44.580> physical 07:42:44.810 --> 07:42:44.820 align:start position:0% sensors that transform the physical 07:42:44.820 --> 07:42:47.090 align:start position:0% sensors that transform the physical stimulus<07:42:45.600> for<07:42:45.840> example<07:42:46.080> something's<07:42:46.798> broken 07:42:47.090 --> 07:42:47.100 align:start position:0% stimulus for example something's broken 07:42:47.100 --> 07:42:48.468 align:start position:0% stimulus for example something's broken or<07:42:47.520> stuck 07:42:48.468 --> 07:42:48.478 align:start position:0% or stuck 07:42:48.478 --> 07:42:51.410 align:start position:0% or stuck or<07:42:49.138> doing<07:42:49.920> too<07:42:50.218> much<07:42:50.458> or<07:42:50.700> too<07:42:50.878> little<07:42:51.000> of<07:42:51.298> what 07:42:51.410 --> 07:42:51.420 align:start position:0% or doing too much or too little of what 07:42:51.420 --> 07:42:53.690 align:start position:0% or doing too much or too little of what it<07:42:51.540> should<07:42:51.660> be<07:42:51.840> doing<07:42:51.958> and<07:42:52.680> this<07:42:52.860> is 07:42:53.690 --> 07:42:53.700 align:start position:0% it should be doing and this is 07:42:53.700 --> 07:42:57.770 align:start position:0% it should be doing and this is um<07:42:53.718> changed<07:42:54.718> into<07:42:54.900> electrical<07:42:55.558> signal 07:42:57.770 --> 07:42:57.780 align:start position:0% um changed into electrical signal 07:42:57.780 --> 07:43:00.830 align:start position:0% um changed into electrical signal and<07:42:58.500> in<07:42:58.680> a<07:42:58.860> basic<07:42:59.160> SC<07:42:59.458> Ada<07:43:00.120> system<07:43:00.360> when 07:43:00.830 --> 07:43:00.840 align:start position:0% and in a basic SC Ada system when 07:43:00.840 --> 07:43:02.690 align:start position:0% and in a basic SC Ada system when industrial<07:43:01.320> operations<07:43:01.798> are<07:43:02.100> performed<07:43:02.520> the 07:43:02.690 --> 07:43:02.700 align:start position:0% industrial operations are performed the 07:43:02.700 --> 07:43:05.390 align:start position:0% industrial operations are performed the information<07:43:02.878> from<07:43:03.540> the<07:43:03.780> sensors<07:43:04.138> is<07:43:04.920> sent<07:43:05.100> to 07:43:05.390 --> 07:43:05.400 align:start position:0% information from the sensors is sent to 07:43:05.400 --> 07:43:08.090 align:start position:0% information from the sensors is sent to a<07:43:05.940> a<07:43:06.840> controller<07:43:07.440> or<07:43:07.680> a<07:43:07.798> number<07:43:07.920> of 07:43:08.090 --> 07:43:08.100 align:start position:0% a a controller or a number of 07:43:08.100 --> 07:43:10.788 align:start position:0% a a controller or a number of controllers<07:43:08.638> the<07:43:09.360> controller<07:43:09.840> is<07:43:10.138> a<07:43:10.440> type<07:43:10.680> of 07:43:10.788 --> 07:43:10.798 align:start position:0% controllers the controller is a type of 07:43:10.798 --> 07:43:12.250 align:start position:0% controllers the controller is a type of computer<07:43:11.040> that<07:43:11.400> receives<07:43:11.760> the<07:43:12.058> information 07:43:12.250 --> 07:43:12.260 align:start position:0% computer that receives the information 07:43:12.260 --> 07:43:15.048 align:start position:0% computer that receives the information from<07:43:13.260> the<07:43:13.440> sensor 07:43:15.048 --> 07:43:15.058 align:start position:0% from the sensor 07:43:15.058 --> 07:43:16.548 align:start position:0% from the sensor now<07:43:15.420> what<07:43:15.600> happens<07:43:15.780> with<07:43:16.138> this<07:43:16.320> information 07:43:16.548 --> 07:43:16.558 align:start position:0% now what happens with this information 07:43:16.558 --> 07:43:18.590 align:start position:0% now what happens with this information just<07:43:17.100> depends<07:43:17.520> on<07:43:17.700> the<07:43:17.878> environment<07:43:18.240> and 07:43:18.590 --> 07:43:18.600 align:start position:0% just depends on the environment and 07:43:18.600 --> 07:43:20.990 align:start position:0% just depends on the environment and what's<07:43:18.718> required<07:43:19.200> and<07:43:19.378> the<07:43:19.558> sensor<07:43:19.920> type<07:43:20.100> it 07:43:20.990 --> 07:43:21.000 align:start position:0% what's required and the sensor type it 07:43:21.000 --> 07:43:22.730 align:start position:0% what's required and the sensor type it sends<07:43:21.298> the<07:43:21.360> information<07:43:21.478> to<07:43:21.958> computers<07:43:22.440> with 07:43:22.730 --> 07:43:22.740 align:start position:0% sends the information to computers with 07:43:22.740 --> 07:43:26.750 align:start position:0% sends the information to computers with the<07:43:22.978> seada<07:43:23.580> software 07:43:26.750 --> 07:43:26.760 align:start position:0% 07:43:26.760 --> 07:43:30.110 align:start position:0% so<07:43:27.298> this<07:43:27.478> helps<07:43:27.900> the<07:43:28.638> systems<07:43:29.638> monitor 07:43:30.110 --> 07:43:30.120 align:start position:0% so this helps the systems monitor 07:43:30.120 --> 07:43:32.270 align:start position:0% so this helps the systems monitor interact<07:43:30.718> and<07:43:31.138> control<07:43:31.440> a<07:43:31.798> variety<07:43:32.100> of 07:43:32.270 --> 07:43:32.280 align:start position:0% interact and control a variety of 07:43:32.280 --> 07:43:33.830 align:start position:0% interact and control a variety of equipment 07:43:33.830 --> 07:43:33.840 align:start position:0% equipment 07:43:33.840 --> 07:43:37.670 align:start position:0% equipment prevents<07:43:34.680> outside<07:43:34.860> attacks<07:43:35.638> the<07:43:36.660> um<07:43:36.680> seida 07:43:37.670 --> 07:43:37.680 align:start position:0% prevents outside attacks the um seida 07:43:37.680 --> 07:43:39.230 align:start position:0% prevents outside attacks the um seida systems<07:43:38.040> are<07:43:38.160> segmented<07:43:38.638> from<07:43:38.820> the<07:43:39.000> rest<07:43:39.058> of 07:43:39.230 --> 07:43:39.240 align:start position:0% systems are segmented from the rest of 07:43:39.240 --> 07:43:40.250 align:start position:0% systems are segmented from the rest of the<07:43:39.360> network 07:43:40.250 --> 07:43:40.260 align:start position:0% the network 07:43:40.260 --> 07:43:42.708 align:start position:0% the network and<07:43:40.860> in<07:43:41.218> addition<07:43:41.458> they<07:43:41.760> have<07:43:41.940> the<07:43:42.120> firewalls 07:43:42.708 --> 07:43:42.718 align:start position:0% and in addition they have the firewalls 07:43:42.718 --> 07:43:44.150 align:start position:0% and in addition they have the firewalls installed 07:43:44.150 --> 07:43:44.160 align:start position:0% installed 07:43:44.160 --> 07:43:46.128 align:start position:0% installed you'd<07:43:44.760> need<07:43:44.940> probably<07:43:45.298> help<07:43:45.660> from<07:43:45.958> a 07:43:46.128 --> 07:43:46.138 align:start position:0% you'd need probably help from a 07:43:46.138 --> 07:43:49.070 align:start position:0% you'd need probably help from a specialist<07:43:46.620> and<07:43:47.160> design<07:43:47.660> company<07:43:48.660> and 07:43:49.070 --> 07:43:49.080 align:start position:0% specialist and design company and 07:43:49.080 --> 07:43:50.510 align:start position:0% specialist and design company and probably<07:43:49.260> installation<07:43:49.920> as<07:43:50.160> well<07:43:50.340> because 07:43:50.510 --> 07:43:50.520 align:start position:0% probably installation as well because 07:43:50.520 --> 07:43:52.850 align:start position:0% probably installation as well because it's<07:43:50.700> kind<07:43:50.940> of<07:43:51.000> outside<07:43:51.180> the<07:43:51.660> purview<07:43:52.320> of<07:43:52.620> the 07:43:52.850 --> 07:43:52.860 align:start position:0% it's kind of outside the purview of the 07:43:52.860 --> 07:43:56.570 align:start position:0% it's kind of outside the purview of the normal<07:43:53.400> Network<07:43:53.700> Engineers<07:43:54.360> roles 07:43:56.570 --> 07:43:56.580 align:start position:0% normal Network Engineers roles 07:43:56.580 --> 07:43:58.430 align:start position:0% normal Network Engineers roles um<07:43:56.700> old<07:43:57.000> and<07:43:57.240> outdated<07:43:57.600> compute<07:43:58.080> systems 07:43:58.430 --> 07:43:58.440 align:start position:0% um old and outdated compute systems 07:43:58.440 --> 07:44:01.250 align:start position:0% um old and outdated compute systems often<07:43:58.798> referred<07:43:59.160> to<07:43:59.218> as<07:43:59.400> Legacy<07:44:00.138> these<07:44:01.138> May 07:44:01.250 --> 07:44:01.260 align:start position:0% often referred to as Legacy these May 07:44:01.260 --> 07:44:02.990 align:start position:0% often referred to as Legacy these May well<07:44:01.440> be<07:44:01.558> running<07:44:01.740> applications<07:44:02.340> and<07:44:02.760> you'll 07:44:02.990 --> 07:44:03.000 align:start position:0% well be running applications and you'll 07:44:03.000 --> 07:44:04.610 align:start position:0% well be running applications and you'll you<07:44:03.180> could<07:44:03.420> see<07:44:03.540> this<07:44:03.718> a<07:44:03.900> lot<07:44:03.958> if<07:44:04.138> you<07:44:04.260> do<07:44:04.378> a<07:44:04.500> new 07:44:04.610 --> 07:44:04.620 align:start position:0% you could see this a lot if you do a new 07:44:04.620 --> 07:44:06.590 align:start position:0% you could see this a lot if you do a new network<07:44:04.920> Consulting<07:44:05.580> you'll<07:44:06.360> go<07:44:06.478> to 07:44:06.590 --> 07:44:06.600 align:start position:0% network Consulting you'll go to 07:44:06.600 --> 07:44:08.090 align:start position:0% network Consulting you'll go to companies<07:44:06.958> that<07:44:07.200> are<07:44:07.320> just<07:44:07.440> running<07:44:07.620> in<07:44:07.860> Old 07:44:08.090 --> 07:44:08.100 align:start position:0% companies that are just running in Old 07:44:08.100 --> 07:44:10.128 align:start position:0% companies that are just running in Old software<07:44:08.580> and<07:44:09.360> they<07:44:09.478> want<07:44:09.718> to<07:44:09.840> keep<07:44:09.958> it 07:44:10.128 --> 07:44:10.138 align:start position:0% software and they want to keep it 07:44:10.138 --> 07:44:12.948 align:start position:0% software and they want to keep it because<07:44:10.378> it<07:44:10.740> still<07:44:10.920> works<07:44:11.400> and<07:44:12.180> it's<07:44:12.600> due<07:44:12.780> to 07:44:12.948 --> 07:44:12.958 align:start position:0% because it still works and it's due to 07:44:12.958 --> 07:44:14.448 align:start position:0% because it still works and it's due to the<07:44:13.080> cost<07:44:13.320> and<07:44:13.558> all<07:44:13.680> of<07:44:13.860> the<07:44:13.920> heartache<07:44:14.400> of 07:44:14.448 --> 07:44:14.458 align:start position:0% the cost and all of the heartache of 07:44:14.458 --> 07:44:17.330 align:start position:0% the cost and all of the heartache of having<07:44:14.700> to<07:44:15.020> upgrade<07:44:16.020> and<07:44:16.260> translate<07:44:16.500> all<07:44:16.920> of 07:44:17.330 --> 07:44:17.340 align:start position:0% having to upgrade and translate all of 07:44:17.340 --> 07:44:19.208 align:start position:0% having to upgrade and translate all of the<07:44:17.520> data 07:44:19.208 --> 07:44:19.218 align:start position:0% the data 07:44:19.218 --> 07:44:21.468 align:start position:0% the data these<07:44:20.218> systems<07:44:20.520> can't<07:44:20.700> be<07:44:20.820> taken<07:44:21.120> out<07:44:21.298> of 07:44:21.468 --> 07:44:21.478 align:start position:0% these systems can't be taken out of 07:44:21.478 --> 07:44:23.510 align:start position:0% these systems can't be taken out of service<07:44:21.660> usually<07:44:22.378> but<07:44:22.680> because<07:44:22.860> of<07:44:23.100> the<07:44:23.340> age 07:44:23.510 --> 07:44:23.520 align:start position:0% service usually but because of the age 07:44:23.520 --> 07:44:26.330 align:start position:0% service usually but because of the age they're<07:44:24.240> more<07:44:24.478> vulnerable<07:44:24.840> to<07:44:25.080> attacks<07:44:25.558> and 07:44:26.330 --> 07:44:26.340 align:start position:0% they're more vulnerable to attacks and 07:44:26.340 --> 07:44:28.128 align:start position:0% they're more vulnerable to attacks and because<07:44:26.580> of<07:44:26.820> the<07:44:26.940> lack<07:44:27.180> of<07:44:27.298> support<07:44:27.540> and<07:44:27.958> the 07:44:28.128 --> 07:44:28.138 align:start position:0% because of the lack of support and the 07:44:28.138 --> 07:44:29.930 align:start position:0% because of the lack of support and the support<07:44:28.320> means<07:44:28.740> there's<07:44:28.860> no<07:44:29.100> more<07:44:29.340> security 07:44:29.930 --> 07:44:29.940 align:start position:0% support means there's no more security 07:44:29.940 --> 07:44:32.448 align:start position:0% support means there's no more security patches 07:44:32.448 --> 07:44:32.458 align:start position:0% patches 07:44:32.458 --> 07:44:34.788 align:start position:0% patches so<07:44:33.120> basically<07:44:33.600> we'll<07:44:33.958> come<07:44:34.138> back<07:44:34.260> into<07:44:34.440> back 07:44:34.788 --> 07:44:34.798 align:start position:0% so basically we'll come back into back 07:44:34.798 --> 07:44:36.890 align:start position:0% so basically we'll come back into back to<07:44:34.978> segmentation<07:44:35.580> and<07:44:36.000> it's<07:44:36.180> important<07:44:36.718> to 07:44:36.890 --> 07:44:36.900 align:start position:0% to segmentation and it's important to 07:44:36.900 --> 07:44:38.208 align:start position:0% to segmentation and it's important to segment<07:44:37.200> these<07:44:37.440> from<07:44:37.680> the<07:44:37.798> rest<07:44:37.920> of<07:44:38.100> the 07:44:38.208 --> 07:44:38.218 align:start position:0% segment these from the rest of the 07:44:38.218 --> 07:44:40.150 align:start position:0% segment these from the rest of the network 07:44:40.150 --> 07:44:40.160 align:start position:0% network 07:44:40.160 --> 07:44:42.948 align:start position:0% network service<07:44:41.160> in<07:44:41.458> the<07:44:41.580> network<07:44:41.760> for<07:44:42.120> Public<07:44:42.360> Public 07:44:42.948 --> 07:44:42.958 align:start position:0% service in the network for Public Public 07:44:42.958 --> 07:44:44.930 align:start position:0% service in the network for Public Public Access<07:44:43.378> would<07:44:43.978> normally<07:44:44.280> restrict<07:44:44.700> access 07:44:44.930 --> 07:44:44.940 align:start position:0% Access would normally restrict access 07:44:44.940 --> 07:44:48.410 align:start position:0% Access would normally restrict access this<07:44:45.540> is<07:44:46.138> classic<07:44:46.740> example<07:44:47.340> is<07:44:47.520> at<07:44:48.058> a<07:44:48.180> public 07:44:48.410 --> 07:44:48.420 align:start position:0% this is classic example is at a public 07:44:48.420 --> 07:44:50.868 align:start position:0% this is classic example is at a public library<07:44:48.780> where<07:44:49.500> customers<07:44:49.978> come<07:44:50.218> in<07:44:50.400> and<07:44:50.638> want 07:44:50.868 --> 07:44:50.878 align:start position:0% library where customers come in and want 07:44:50.878 --> 07:44:52.850 align:start position:0% library where customers come in and want to<07:44:51.000> use<07:44:51.120> the<07:44:51.360> systems<07:44:51.780> but<07:44:52.080> obviously<07:44:52.680> you 07:44:52.850 --> 07:44:52.860 align:start position:0% to use the systems but obviously you 07:44:52.860 --> 07:44:54.590 align:start position:0% to use the systems but obviously you don't<07:44:52.978> want<07:44:53.160> them<07:44:53.280> to<07:44:53.458> have<07:44:53.580> visibility<07:44:54.058> to 07:44:54.590 --> 07:44:54.600 align:start position:0% don't want them to have visibility to 07:44:54.600 --> 07:44:57.230 align:start position:0% don't want them to have visibility to the<07:44:54.900> back<07:44:55.320> end<07:44:55.500> systems<07:44:55.978> where<07:44:56.400> customers 07:44:57.230 --> 07:44:57.240 align:start position:0% the back end systems where customers 07:44:57.240 --> 07:45:00.170 align:start position:0% the back end systems where customers data<07:44:57.600> is<07:44:57.718> kept<07:44:58.020> and<07:44:58.200> people<07:44:58.378> can<07:44:58.820> get<07:44:59.820> books 07:45:00.170 --> 07:45:00.180 align:start position:0% data is kept and people can get books 07:45:00.180 --> 07:45:02.090 align:start position:0% data is kept and people can get books and<07:45:00.360> make<07:45:00.478> payments<07:45:00.958> and<07:45:01.320> all<07:45:01.558> that<07:45:01.740> sort<07:45:01.978> of 07:45:02.090 --> 07:45:02.100 align:start position:0% and make payments and all that sort of 07:45:02.100 --> 07:45:03.350 align:start position:0% and make payments and all that sort of stuff 07:45:03.350 --> 07:45:03.360 align:start position:0% stuff 07:45:03.360 --> 07:45:05.930 align:start position:0% stuff so<07:45:04.260> you'd<07:45:04.798> segment<07:45:05.100> the<07:45:05.400> servers<07:45:05.820> and 07:45:05.930 --> 07:45:05.940 align:start position:0% so you'd segment the servers and 07:45:05.940 --> 07:45:08.090 align:start position:0% so you'd segment the servers and resources<07:45:06.360> used<07:45:06.600> by<07:45:06.840> employees<07:45:07.320> on<07:45:07.620> a<07:45:07.798> private 07:45:08.090 --> 07:45:08.100 align:start position:0% resources used by employees on a private 07:45:08.100 --> 07:45:13.610 align:start position:0% resources used by employees on a private Network<07:45:08.218> public<07:45:09.120> access<07:45:09.420> to<07:45:10.080> the<07:45:10.740> public 07:45:13.610 --> 07:45:13.620 align:start position:0% 07:45:13.620 --> 07:45:16.610 align:start position:0% and<07:45:14.218> net<07:45:14.458> Network<07:45:14.958> segmentations<07:45:15.958> critical 07:45:16.610 --> 07:45:16.620 align:start position:0% and net Network segmentations critical 07:45:16.620 --> 07:45:18.890 align:start position:0% and net Network segmentations critical situations<07:45:17.218> if<07:45:18.000> a<07:45:18.180> private<07:45:18.420> network<07:45:18.600> is 07:45:18.890 --> 07:45:18.900 align:start position:0% situations if a private network is 07:45:18.900 --> 07:45:21.410 align:start position:0% situations if a private network is restricted<07:45:19.378> only<07:45:19.558> to<07:45:19.860> employees<07:45:20.340> it's<07:45:21.120> less 07:45:21.410 --> 07:45:21.420 align:start position:0% restricted only to employees it's less 07:45:21.420 --> 07:45:23.090 align:start position:0% restricted only to employees it's less prone<07:45:21.718> to<07:45:21.900> outside<07:45:22.138> attacks<07:45:22.860> probably 07:45:23.090 --> 07:45:23.100 align:start position:0% prone to outside attacks probably 07:45:23.100 --> 07:45:25.190 align:start position:0% prone to outside attacks probably certainly<07:45:23.638> obvious<07:45:23.878> here<07:45:24.120> in<07:45:24.840> a<07:45:25.020> public 07:45:25.190 --> 07:45:25.200 align:start position:0% certainly obvious here in a public 07:45:25.200 --> 07:45:26.868 align:start position:0% certainly obvious here in a public network<07:45:25.500> even<07:45:26.160> if<07:45:26.340> the<07:45:26.520> server<07:45:26.760> is 07:45:26.868 --> 07:45:26.878 align:start position:0% network even if the server is 07:45:26.878 --> 07:45:29.030 align:start position:0% network even if the server is compromised<07:45:27.600> it<07:45:28.138> won't<07:45:28.320> actually<07:45:28.620> affect 07:45:29.030 --> 07:45:29.040 align:start position:0% compromised it won't actually affect 07:45:29.040 --> 07:45:31.610 align:start position:0% compromised it won't actually affect your<07:45:29.400> internal<07:45:30.000> private<07:45:30.420> Network<07:45:30.660> so<07:45:31.440> you 07:45:31.610 --> 07:45:31.620 align:start position:0% your internal private Network so you 07:45:31.620 --> 07:45:33.650 align:start position:0% your internal private Network so you could<07:45:31.740> do<07:45:31.860> your<07:45:32.100> troubleshooting<07:45:32.940> and 07:45:33.650 --> 07:45:33.660 align:start position:0% could do your troubleshooting and 07:45:33.660 --> 07:45:35.990 align:start position:0% could do your troubleshooting and resolution<07:45:34.080> without<07:45:34.798> worrying<07:45:35.280> about 07:45:35.990 --> 07:45:36.000 align:start position:0% resolution without worrying about 07:45:36.000 --> 07:45:37.610 align:start position:0% resolution without worrying about um affecting<07:45:36.600> your<07:45:36.958> critical<07:45:37.320> Business 07:45:37.610 --> 07:45:37.620 align:start position:0% um affecting your critical Business 07:45:37.620 --> 07:45:39.410 align:start position:0% um affecting your critical Business Systems 07:45:39.410 --> 07:45:39.420 align:start position:0% Systems 07:45:39.420 --> 07:45:41.990 align:start position:0% Systems uh<07:45:40.138> testing<07:45:40.620> patches<07:45:41.040> and<07:45:41.218> updates<07:45:41.580> for 07:45:41.990 --> 07:45:42.000 align:start position:0% uh testing patches and updates for 07:45:42.000 --> 07:45:43.610 align:start position:0% uh testing patches and updates for applications<07:45:42.478> should<07:45:42.780> be<07:45:42.900> carried<07:45:43.200> out<07:45:43.320> in<07:45:43.500> a 07:45:43.610 --> 07:45:43.620 align:start position:0% applications should be carried out in a 07:45:43.620 --> 07:45:45.830 align:start position:0% applications should be carried out in a test<07:45:43.798> the<07:45:43.978> environment<07:45:44.400> it's<07:45:45.240> often<07:45:45.540> called<07:45:45.660> a 07:45:45.830 --> 07:45:45.840 align:start position:0% test the environment it's often called a 07:45:45.840 --> 07:45:48.350 align:start position:0% test the environment it's often called a test<07:45:46.020> bed<07:45:46.200> where<07:45:46.500> you've<07:45:46.620> got<07:45:46.740> a<07:45:46.860> copy<07:45:47.160> of<07:45:47.400> your 07:45:48.350 --> 07:45:48.360 align:start position:0% test bed where you've got a copy of your 07:45:48.360 --> 07:45:49.730 align:start position:0% test bed where you've got a copy of your devices 07:45:49.730 --> 07:45:49.740 align:start position:0% devices 07:45:49.740 --> 07:45:51.350 align:start position:0% devices and<07:45:50.280> you<07:45:50.400> could<07:45:50.580> even<07:45:50.700> be<07:45:50.878> running<07:45:51.058> them 07:45:51.350 --> 07:45:51.360 align:start position:0% and you could even be running them 07:45:51.360 --> 07:45:53.208 align:start position:0% and you could even be running them virtually 07:45:53.208 --> 07:45:53.218 align:start position:0% virtually 07:45:53.218 --> 07:45:56.510 align:start position:0% virtually and<07:45:53.820> it's<07:45:54.180> all<07:45:54.420> done<07:45:54.660> in<07:45:55.260> order<07:45:55.378> to<07:45:55.620> prevent<07:45:56.040> or 07:45:56.510 --> 07:45:56.520 align:start position:0% and it's all done in order to prevent or 07:45:56.520 --> 07:46:02.810 align:start position:0% and it's all done in order to prevent or foresee<07:45:57.058> problems<07:45:57.420> on<07:45:57.600> your<07:45:57.718> live<07:45:57.900> equipment 07:46:02.810 --> 07:46:02.820 align:start position:0% 07:46:02.820 --> 07:46:06.128 align:start position:0% a<07:46:03.298> honey<07:46:03.540> pot<07:46:03.840> is<07:46:04.080> a<07:46:04.260> decoy<07:46:05.040> server<07:46:05.458> set<07:46:05.878> to 07:46:06.128 --> 07:46:06.138 align:start position:0% a honey pot is a decoy server set to 07:46:06.138 --> 07:46:09.230 align:start position:0% a honey pot is a decoy server set to lure<07:46:07.138> attackers<07:46:07.680> studies<07:46:08.520> there<07:46:08.940> and 07:46:09.230 --> 07:46:09.240 align:start position:0% lure attackers studies there and 07:46:09.240 --> 07:46:11.270 align:start position:0% lure attackers studies there and methodology<07:46:09.718> and<07:46:10.200> how<07:46:10.378> they<07:46:10.558> break<07:46:10.740> into<07:46:10.978> the 07:46:11.270 --> 07:46:11.280 align:start position:0% methodology and how they break into the 07:46:11.280 --> 07:46:13.788 align:start position:0% methodology and how they break into the systems<07:46:11.760> gathers<07:46:12.600> for<07:46:12.780> our<07:46:12.900> zinc<07:46:13.200> forensic 07:46:13.788 --> 07:46:13.798 align:start position:0% systems gathers for our zinc forensic 07:46:13.798 --> 07:46:16.070 align:start position:0% systems gathers for our zinc forensic information<07:46:14.040> and<07:46:14.940> it<07:46:15.120> can<07:46:15.240> be<07:46:15.360> used<07:46:15.600> in<07:46:15.900> the 07:46:16.070 --> 07:46:16.080 align:start position:0% information and it can be used in the 07:46:16.080 --> 07:46:17.570 align:start position:0% information and it can be used in the event<07:46:16.378> that<07:46:16.620> you<07:46:16.798> actually<07:46:16.920> prosecute 07:46:17.570 --> 07:46:17.580 align:start position:0% event that you actually prosecute 07:46:17.580 --> 07:46:18.948 align:start position:0% event that you actually prosecute somebody 07:46:18.948 --> 07:46:18.958 align:start position:0% somebody 07:46:18.958 --> 07:46:21.230 align:start position:0% somebody designed<07:46:19.740> to<07:46:19.798> be<07:46:19.978> a<07:46:20.340> little<07:46:20.458> bit<07:46:20.580> more<07:46:20.820> easily 07:46:21.230 --> 07:46:21.240 align:start position:0% designed to be a little bit more easily 07:46:21.240 --> 07:46:23.150 align:start position:0% designed to be a little bit more easily exploited<07:46:21.840> exploited<07:46:22.558> than<07:46:22.740> the<07:46:22.920> actual 07:46:23.150 --> 07:46:23.160 align:start position:0% exploited exploited than the actual 07:46:23.160 --> 07:46:25.490 align:start position:0% exploited exploited than the actual production<07:46:23.580> server<07:46:24.120> so<07:46:24.900> this<07:46:25.200> would<07:46:25.320> probably 07:46:25.490 --> 07:46:25.500 align:start position:0% production server so this would probably 07:46:25.500 --> 07:46:27.230 align:start position:0% production server so this would probably be<07:46:25.620> the<07:46:25.798> first<07:46:25.978> device<07:46:26.218> discovered<07:46:26.878> by<07:46:27.058> the 07:46:27.230 --> 07:46:27.240 align:start position:0% be the first device discovered by the 07:46:27.240 --> 07:46:28.430 align:start position:0% be the first device discovered by the attackers 07:46:28.430 --> 07:46:28.440 align:start position:0% attackers 07:46:28.440 --> 07:46:30.770 align:start position:0% attackers has<07:46:29.040> attackers<07:46:29.520> activities<07:46:29.940> logged<07:46:30.478> to<07:46:30.540> get 07:46:30.770 --> 07:46:30.780 align:start position:0% has attackers activities logged to get 07:46:30.780 --> 07:46:35.448 align:start position:0% has attackers activities logged to get insight<07:46:31.138> into<07:46:31.378> their<07:46:31.798> sneaky<07:46:32.340> little<07:46:32.520> methods 07:46:35.448 --> 07:46:35.458 align:start position:0% 07:46:35.458 --> 07:46:37.910 align:start position:0% okay<07:46:35.940> an<07:46:36.420> early<07:46:36.780> part<07:46:37.080> is<07:46:37.200> a<07:46:37.378> network<07:46:37.500> segment 07:46:37.910 --> 07:46:37.920 align:start position:0% okay an early part is a network segment 07:46:37.920 --> 07:46:40.070 align:start position:0% okay an early part is a network segment that<07:46:38.100> contains<07:46:38.520> more<07:46:38.878> than<07:46:39.058> one 07:46:40.070 --> 07:46:40.080 align:start position:0% that contains more than one 07:46:40.080 --> 07:46:42.948 align:start position:0% that contains more than one um honey<07:46:40.378> pot<07:46:40.740> or<07:46:41.040> only<07:46:41.218> net<07:46:41.580> sorry 07:46:42.948 --> 07:46:42.958 align:start position:0% um honey pot or only net sorry 07:46:42.958 --> 07:46:44.990 align:start position:0% um honey pot or only net sorry so<07:46:43.500> the<07:46:43.740> honey<07:46:43.920> net<07:46:44.280> would<07:46:44.520> normally<07:46:44.760> look 07:46:44.990 --> 07:46:45.000 align:start position:0% so the honey net would normally look 07:46:45.000 --> 07:46:46.850 align:start position:0% so the honey net would normally look like<07:46:45.240> a<07:46:45.420> normal<07:46:45.540> operational<07:46:46.020> Network<07:46:46.440> for 07:46:46.850 --> 07:46:46.860 align:start position:0% like a normal operational Network for 07:46:46.860 --> 07:46:48.110 align:start position:0% like a normal operational Network for the<07:46:47.040> attacker 07:46:48.110 --> 07:46:48.120 align:start position:0% the attacker 07:46:48.120 --> 07:46:50.810 align:start position:0% the attacker and<07:46:48.900> it'll<07:46:49.440> make<07:46:49.680> the<07:46:49.978> attacker<07:46:50.340> spend<07:46:50.638> more 07:46:50.810 --> 07:46:50.820 align:start position:0% and it'll make the attacker spend more 07:46:50.820 --> 07:46:52.368 align:start position:0% and it'll make the attacker spend more time<07:46:51.058> in<07:46:51.240> the<07:46:51.360> system<07:46:51.540> which<07:46:51.840> gives<07:46:52.020> you<07:46:52.138> more 07:46:52.368 --> 07:46:52.378 align:start position:0% time in the system which gives you more 07:46:52.378 --> 07:46:54.650 align:start position:0% time in the system which gives you more time<07:46:52.558> to<07:46:52.740> analyze<07:46:53.218> what<07:46:53.760> they're<07:46:53.940> doing<07:46:54.180> and 07:46:54.650 --> 07:46:54.660 align:start position:0% time to analyze what they're doing and 07:46:54.660 --> 07:46:57.230 align:start position:0% time to analyze what they're doing and where<07:46:54.900> they're<07:46:55.080> coming<07:46:55.260> from 07:46:57.230 --> 07:46:57.240 align:start position:0% where they're coming from 07:46:57.240 --> 07:46:59.350 align:start position:0% where they're coming from all<07:46:57.718> right<07:46:57.840> so<07:46:58.020> we've<07:46:58.200> covered<07:46:58.558> segmentation 07:46:59.350 --> 07:46:59.360 align:start position:0% all right so we've covered segmentation 07:46:59.360 --> 07:47:03.830 align:start position:0% all right so we've covered segmentation physically<07:47:00.360> logically<07:47:01.580> uses<07:47:02.580> of<07:47:02.820> it<07:47:03.000> and 07:47:03.830 --> 07:47:03.840 align:start position:0% physically logically uses of it and 07:47:03.840 --> 07:47:06.350 align:start position:0% physically logically uses of it and critical<07:47:04.260> situations<07:47:04.940> that's<07:47:05.940> the<07:47:06.120> end<07:47:06.240> of 07:47:06.350 --> 07:47:06.360 align:start position:0% critical situations that's the end of 07:47:06.360 --> 07:47:15.520 align:start position:0% critical situations that's the end of the<07:47:06.420> presentation<07:47:06.840> thanks<07:47:07.500> for<07:47:07.680> watching 07:47:15.520 --> 07:47:15.530 align:start position:0% 07:47:15.530 --> 07:47:33.830 align:start position:0% [Music] 07:47:33.830 --> 07:47:33.840 align:start position:0% 07:47:33.840 --> 07:47:37.788 align:start position:0% Network<07:47:34.620> routing<07:47:35.340> and<07:47:35.760> IP<07:47:36.120> addressing<07:47:36.798> IP 07:47:37.788 --> 07:47:37.798 align:start position:0% Network routing and IP addressing IP 07:47:37.798 --> 07:47:40.430 align:start position:0% Network routing and IP addressing IP addresses<07:47:38.340> and<07:47:38.760> conversion 07:47:40.430 --> 07:47:40.440 align:start position:0% addresses and conversion 07:47:40.440 --> 07:47:42.590 align:start position:0% addresses and conversion so<07:47:41.100> welcome<07:47:41.280> to<07:47:41.580> this<07:47:41.820> module<07:47:42.180> we're<07:47:42.360> going<07:47:42.540> to 07:47:42.590 --> 07:47:42.600 align:start position:0% so welcome to this module we're going to 07:47:42.600 --> 07:47:46.490 align:start position:0% so welcome to this module we're going to cover<07:47:42.780> IP<07:47:43.620> addresses<07:47:44.218> and<07:47:45.000> conversions<07:47:45.600> and 07:47:46.490 --> 07:47:46.500 align:start position:0% cover IP addresses and conversions and 07:47:46.500 --> 07:47:48.350 align:start position:0% cover IP addresses and conversions and in<07:47:46.680> some<07:47:46.860> of<07:47:46.978> the<07:47:47.160> previous<07:47:47.520> modules<07:47:48.120> we 07:47:48.350 --> 07:47:48.360 align:start position:0% in some of the previous modules we 07:47:48.360 --> 07:47:50.150 align:start position:0% in some of the previous modules we talked<07:47:48.780> about<07:47:48.900> a<07:47:49.200> lot<07:47:49.320> of<07:47:49.440> the<07:47:49.500> Technologies 07:47:50.150 --> 07:47:50.160 align:start position:0% talked about a lot of the Technologies 07:47:50.160 --> 07:47:53.090 align:start position:0% talked about a lot of the Technologies and<07:47:50.700> theories<07:47:51.120> and<07:47:51.840> protocols<07:47:52.378> that<07:47:52.620> make<07:47:52.798> up 07:47:53.090 --> 07:47:53.100 align:start position:0% and theories and protocols that make up 07:47:53.100 --> 07:47:55.010 align:start position:0% and theories and protocols that make up computer<07:47:53.340> networks<07:47:54.000> and<07:47:54.478> so<07:47:54.600> here<07:47:54.840> we're 07:47:55.010 --> 07:47:55.020 align:start position:0% computer networks and so here we're 07:47:55.020 --> 07:47:56.930 align:start position:0% computer networks and so here we're going<07:47:55.200> to<07:47:55.320> discuss<07:47:55.680> some<07:47:56.458> of<07:47:56.580> the<07:47:56.700> more 07:47:56.930 --> 07:47:56.940 align:start position:0% going to discuss some of the more 07:47:56.940 --> 07:47:59.390 align:start position:0% going to discuss some of the more important<07:47:57.600> aspects<07:47:58.320> of<07:47:58.860> networking 07:47:59.390 --> 07:47:59.400 align:start position:0% important aspects of networking 07:47:59.400 --> 07:48:03.350 align:start position:0% important aspects of networking specifically<07:48:00.240> the<07:48:01.138> IP<07:48:01.500> address<07:48:01.878> so<07:48:02.878> this 07:48:03.350 --> 07:48:03.360 align:start position:0% specifically the IP address so this 07:48:03.360 --> 07:48:05.448 align:start position:0% specifically the IP address so this module<07:48:03.718> is<07:48:03.840> going<07:48:04.020> to<07:48:04.138> begin<07:48:04.260> by<07:48:05.040> introducing 07:48:05.448 --> 07:48:05.458 align:start position:0% module is going to begin by introducing 07:48:05.458 --> 07:48:07.190 align:start position:0% module is going to begin by introducing us<07:48:05.580> to<07:48:05.820> some<07:48:06.000> of<07:48:06.120> the<07:48:06.180> specific<07:48:06.478> protocols 07:48:07.190 --> 07:48:07.200 align:start position:0% us to some of the specific protocols 07:48:07.200 --> 07:48:10.730 align:start position:0% us to some of the specific protocols that<07:48:07.440> are<07:48:07.558> found<07:48:07.798> within<07:48:08.458> the<07:48:08.878> tcpip<07:48:09.740> protocol 07:48:10.730 --> 07:48:10.740 align:start position:0% that are found within the tcpip protocol 07:48:10.740 --> 07:48:13.310 align:start position:0% that are found within the tcpip protocol Suite<07:48:11.340> that<07:48:12.240> you<07:48:12.360> need<07:48:12.478> to<07:48:12.600> know<07:48:12.718> about<07:48:12.958> for 07:48:13.310 --> 07:48:13.320 align:start position:0% Suite that you need to know about for 07:48:13.320 --> 07:48:16.610 align:start position:0% Suite that you need to know about for the<07:48:13.440> network<07:48:13.558> plus<07:48:13.860> exam<07:48:14.340> and<07:48:15.180> these<07:48:15.420> are<07:48:15.620> TCP 07:48:16.610 --> 07:48:16.620 align:start position:0% the network plus exam and these are TCP 07:48:16.620 --> 07:48:18.948 align:start position:0% the network plus exam and these are TCP and<07:48:17.040> IP<07:48:17.400> and<07:48:17.580> a<07:48:17.760> little<07:48:17.820> more<07:48:17.940> depth<07:48:18.420> we 07:48:18.948 --> 07:48:18.958 align:start position:0% and IP and a little more depth we 07:48:18.958 --> 07:48:20.930 align:start position:0% and IP and a little more depth we mentioned<07:48:19.500> them<07:48:19.680> briefly<07:48:20.160> when<07:48:20.520> we<07:48:20.700> talked 07:48:20.930 --> 07:48:20.940 align:start position:0% mentioned them briefly when we talked 07:48:20.940 --> 07:48:24.590 align:start position:0% mentioned them briefly when we talked about<07:48:21.000> the<07:48:21.360> TCP<07:48:22.280> model<07:48:23.280> and<07:48:24.120> then<07:48:24.240> we're<07:48:24.478> going 07:48:24.590 --> 07:48:24.600 align:start position:0% about the TCP model and then we're going 07:48:24.600 --> 07:48:27.310 align:start position:0% about the TCP model and then we're going to<07:48:24.718> describe<07:48:25.620> UDP<07:48:26.040> which<07:48:26.700> is<07:48:26.878> a<07:48:27.120> connection 07:48:27.310 --> 07:48:27.320 align:start position:0% to describe UDP which is a connection 07:48:27.320 --> 07:48:30.890 align:start position:0% to describe UDP which is a connection less<07:48:28.820> protocol<07:48:29.820> then<07:48:30.478> we're<07:48:30.600> going<07:48:30.718> to<07:48:30.780> look 07:48:30.890 --> 07:48:30.900 align:start position:0% less protocol then we're going to look 07:48:30.900 --> 07:48:33.770 align:start position:0% less protocol then we're going to look at<07:48:31.020> ARP<07:48:31.378> and<07:48:31.558> rarp<07:48:32.040> two<07:48:32.878> versions<07:48:33.240> that<07:48:33.478> allow 07:48:33.770 --> 07:48:33.780 align:start position:0% at ARP and rarp two versions that allow 07:48:33.780 --> 07:48:37.010 align:start position:0% at ARP and rarp two versions that allow us<07:48:33.900> to<07:48:34.378> basically<07:48:35.120> or<07:48:36.120> two<07:48:36.298> protocols<07:48:36.780> rather 07:48:37.010 --> 07:48:37.020 align:start position:0% us to basically or two protocols rather 07:48:37.020 --> 07:48:38.810 align:start position:0% us to basically or two protocols rather that<07:48:37.260> basically<07:48:37.620> allow<07:48:37.920> us<07:48:38.040> to<07:48:38.280> map<07:48:38.458> Mac 07:48:38.810 --> 07:48:38.820 align:start position:0% that basically allow us to map Mac 07:48:38.820 --> 07:48:42.048 align:start position:0% that basically allow us to map Mac addresses<07:48:39.420> to<07:48:39.840> IP<07:48:40.138> address<07:48:40.378> and<07:48:41.218> which<07:48:41.700> are 07:48:42.048 --> 07:48:42.058 align:start position:0% addresses to IP address and which are 07:48:42.058 --> 07:48:44.270 align:start position:0% addresses to IP address and which are basically<07:48:42.478> responsible<07:48:43.080> for<07:48:43.740> routing<07:48:44.160> in 07:48:44.270 --> 07:48:44.280 align:start position:0% basically responsible for routing in 07:48:44.280 --> 07:48:45.830 align:start position:0% basically responsible for routing in general<07:48:44.458> and<07:48:45.240> after<07:48:45.360> that<07:48:45.540> we're<07:48:45.660> going<07:48:45.780> to 07:48:45.830 --> 07:48:45.840 align:start position:0% general and after that we're going to 07:48:45.840 --> 07:48:47.930 align:start position:0% general and after that we're going to look<07:48:45.958> at<07:48:46.080> two<07:48:46.260> management<07:48:46.500> protocols<07:48:47.340> one 07:48:47.930 --> 07:48:47.940 align:start position:0% look at two management protocols one 07:48:47.940 --> 07:48:50.690 align:start position:0% look at two management protocols one called<07:48:48.240> icmp<07:48:49.138> which<07:48:49.320> I<07:48:49.500> introduced<07:48:49.860> to<07:48:50.040> you<07:48:50.160> in 07:48:50.690 --> 07:48:50.700 align:start position:0% called icmp which I introduced to you in 07:48:50.700 --> 07:48:52.010 align:start position:0% called icmp which I introduced to you in previous<07:48:50.878> modules<07:48:51.420> and<07:48:51.540> I<07:48:51.660> said<07:48:51.780> it<07:48:51.898> was 07:48:52.010 --> 07:48:52.020 align:start position:0% previous modules and I said it was 07:48:52.020 --> 07:48:54.650 align:start position:0% previous modules and I said it was related<07:48:52.260> to<07:48:52.500> the<07:48:53.218> Ping<07:48:53.520> a<07:48:53.940> utility<07:48:54.298> we're 07:48:54.650 --> 07:48:54.660 align:start position:0% related to the Ping a utility we're 07:48:54.660 --> 07:48:55.670 align:start position:0% related to the Ping a utility we're going<07:48:54.718> to<07:48:54.780> learn<07:48:54.898> a<07:48:55.020> little<07:48:55.080> more<07:48:55.260> about<07:48:55.378> that 07:48:55.670 --> 07:48:55.680 align:start position:0% going to learn a little more about that 07:48:55.680 --> 07:49:00.288 align:start position:0% going to learn a little more about that and<07:48:56.160> then<07:48:56.340> igmp<07:48:57.320> which<07:48:58.320> is<07:48:58.860> uh<07:48:59.700> slightly 07:49:00.288 --> 07:49:00.298 align:start position:0% and then igmp which is uh slightly 07:49:00.298 --> 07:49:01.548 align:start position:0% and then igmp which is uh slightly different<07:49:00.478> has<07:49:00.958> to<07:49:01.080> do<07:49:01.200> more<07:49:01.320> with 07:49:01.548 --> 07:49:01.558 align:start position:0% different has to do more with 07:49:01.558 --> 07:49:04.250 align:start position:0% different has to do more with multicasting<07:49:02.340> and<07:49:02.760> unicasting<07:49:03.540> and<07:49:04.138> then 07:49:04.250 --> 07:49:04.260 align:start position:0% multicasting and unicasting and then 07:49:04.260 --> 07:49:06.590 align:start position:0% multicasting and unicasting and then we're<07:49:04.440> going<07:49:04.558> to<07:49:04.620> continue<07:49:04.860> by<07:49:05.218> outlining<07:49:05.820> uh 07:49:06.590 --> 07:49:06.600 align:start position:0% we're going to continue by outlining uh 07:49:06.600 --> 07:49:10.128 align:start position:0% we're going to continue by outlining uh IP<07:49:07.020> packet<07:49:07.500> delivery<07:49:07.978> processes<07:49:08.898> and<07:49:09.898> we're 07:49:10.128 --> 07:49:10.138 align:start position:0% IP packet delivery processes and we're 07:49:10.138 --> 07:49:11.930 align:start position:0% IP packet delivery processes and we're going<07:49:10.320> to<07:49:10.378> finish<07:49:10.500> off<07:49:10.798> the<07:49:11.040> module<07:49:11.398> with<07:49:11.878> a 07:49:11.930 --> 07:49:11.940 align:start position:0% going to finish off the module with a 07:49:11.940 --> 07:49:15.770 align:start position:0% going to finish off the module with a bit<07:49:12.058> of<07:49:12.180> an<07:49:12.298> introduction<07:49:12.840> into<07:49:13.798> binary<07:49:14.780> and 07:49:15.770 --> 07:49:15.780 align:start position:0% bit of an introduction into binary and 07:49:15.780 --> 07:49:18.888 align:start position:0% bit of an introduction into binary and decimal<07:49:16.440> conversions<07:49:17.040> so<07:49:17.820> that<07:49:18.058> later<07:49:18.298> on<07:49:18.540> we 07:49:18.888 --> 07:49:18.898 align:start position:0% decimal conversions so that later on we 07:49:18.898 --> 07:49:20.750 align:start position:0% decimal conversions so that later on we can<07:49:19.020> talk<07:49:19.200> a<07:49:19.378> little<07:49:19.500> more<07:49:19.620> in<07:49:19.798> depth<07:49:20.040> about<07:49:20.218> IP 07:49:20.750 --> 07:49:20.760 align:start position:0% can talk a little more in depth about IP 07:49:20.760 --> 07:49:24.250 align:start position:0% can talk a little more in depth about IP addressing<07:49:21.298> and<07:49:22.520> how 07:49:24.250 --> 07:49:24.260 align:start position:0% addressing and how 07:49:24.260 --> 07:49:27.288 align:start position:0% addressing and how something<07:49:25.260> called<07:49:25.620> subnetting<07:49:26.458> Works<07:49:26.820> which 07:49:27.288 --> 07:49:27.298 align:start position:0% something called subnetting Works which 07:49:27.298 --> 07:49:29.208 align:start position:0% something called subnetting Works which is<07:49:27.420> going<07:49:27.600> to<07:49:27.780> require<07:49:27.958> us<07:49:28.260> to<07:49:28.500> understand<07:49:28.680> the 07:49:29.208 --> 07:49:29.218 align:start position:0% is going to require us to understand the 07:49:29.218 --> 07:49:30.948 align:start position:0% is going to require us to understand the difference<07:49:29.280> between<07:49:29.638> these<07:49:30.000> two<07:49:30.240> ways<07:49:30.840> of 07:49:30.948 --> 07:49:30.958 align:start position:0% difference between these two ways of 07:49:30.958 --> 07:49:34.250 align:start position:0% difference between these two ways of writing<07:49:31.320> our<07:49:31.580> numbers<07:49:32.580> and<07:49:33.360> after<07:49:33.540> we<07:49:33.898> have 07:49:34.250 --> 07:49:34.260 align:start position:0% writing our numbers and after we have 07:49:34.260 --> 07:49:35.510 align:start position:0% writing our numbers and after we have covered<07:49:34.620> all<07:49:34.798> these<07:49:34.978> topics<07:49:35.218> we're<07:49:35.398> gonna 07:49:35.510 --> 07:49:35.520 align:start position:0% covered all these topics we're gonna 07:49:35.520 --> 07:49:38.090 align:start position:0% covered all these topics we're gonna have<07:49:35.700> a<07:49:35.820> fundamental<07:49:36.240> understanding<07:49:37.020> of<07:49:37.680> Ip 07:49:38.090 --> 07:49:38.100 align:start position:0% have a fundamental understanding of Ip 07:49:38.100 --> 07:49:39.590 align:start position:0% have a fundamental understanding of Ip that's<07:49:38.580> going<07:49:38.760> to<07:49:38.820> prepare<07:49:39.000> us<07:49:39.120> for<07:49:39.298> some<07:49:39.420> of 07:49:39.590 --> 07:49:39.600 align:start position:0% that's going to prepare us for some of 07:49:39.600 --> 07:49:41.628 align:start position:0% that's going to prepare us for some of the<07:49:39.660> more<07:49:39.780> in-depth<07:49:40.320> topics<07:49:41.040> as<07:49:41.280> I<07:49:41.520> just 07:49:41.628 --> 07:49:41.638 align:start position:0% the more in-depth topics as I just 07:49:41.638 --> 07:49:44.270 align:start position:0% the more in-depth topics as I just mentioned<07:49:42.058> in<07:49:42.840> the<07:49:42.958> following<07:49:43.260> modules 07:49:44.270 --> 07:49:44.280 align:start position:0% mentioned in the following modules 07:49:44.280 --> 07:49:46.610 align:start position:0% mentioned in the following modules so<07:49:44.760> let's<07:49:45.120> begin<07:49:45.298> by<07:49:45.600> taking<07:49:45.840> a<07:49:46.080> look<07:49:46.200> at<07:49:46.440> two 07:49:46.610 --> 07:49:46.620 align:start position:0% so let's begin by taking a look at two 07:49:46.620 --> 07:49:48.708 align:start position:0% so let's begin by taking a look at two of<07:49:46.740> the<07:49:46.920> most<07:49:47.100> important<07:49:48.000> protocols<07:49:48.540> that 07:49:48.708 --> 07:49:48.718 align:start position:0% of the most important protocols that 07:49:48.718 --> 07:49:52.730 align:start position:0% of the most important protocols that make<07:49:48.898> up<07:49:49.080> the<07:49:49.320> suite<07:49:49.940> TCP<07:49:50.940> and<07:49:51.298> IP<07:49:51.660> now<07:49:52.440> in 07:49:52.730 --> 07:49:52.740 align:start position:0% make up the suite TCP and IP now in 07:49:52.740 --> 07:49:54.770 align:start position:0% make up the suite TCP and IP now in previous<07:49:52.860> chapters<07:49:53.398> we<07:49:53.820> briefly<07:49:54.240> described 07:49:54.770 --> 07:49:54.780 align:start position:0% previous chapters we briefly described 07:49:54.780 --> 07:49:57.288 align:start position:0% previous chapters we briefly described these<07:49:55.200> two<07:49:55.320> but<07:49:55.920> we<07:49:56.160> still<07:49:56.340> need<07:49:56.580> to<07:49:56.820> take<07:49:57.058> a 07:49:57.288 --> 07:49:57.298 align:start position:0% these two but we still need to take a 07:49:57.298 --> 07:49:59.510 align:start position:0% these two but we still need to take a closer<07:49:57.600> look<07:49:57.840> at<07:49:58.200> them<07:49:58.320> to<07:49:58.740> assure<07:49:59.100> that<07:49:59.398> we 07:49:59.510 --> 07:49:59.520 align:start position:0% closer look at them to assure that we 07:49:59.520 --> 07:50:02.030 align:start position:0% closer look at them to assure that we have<07:49:59.638> a<07:49:59.760> complete<07:50:00.120> understanding<07:50:00.840> of<07:50:01.798> the 07:50:02.030 --> 07:50:02.040 align:start position:0% have a complete understanding of the 07:50:02.040 --> 07:50:04.070 align:start position:0% have a complete understanding of the many<07:50:02.160> different<07:50:02.458> protocols<07:50:03.240> that<07:50:03.660> are<07:50:03.840> found 07:50:04.070 --> 07:50:04.080 align:start position:0% many different protocols that are found 07:50:04.080 --> 07:50:07.010 align:start position:0% many different protocols that are found in<07:50:04.440> our<07:50:04.680> protocol<07:50:04.978> Suite<07:50:05.458> so<07:50:06.240> first<07:50:06.478> for<07:50:06.840> those 07:50:07.010 --> 07:50:07.020 align:start position:0% in our protocol Suite so first for those 07:50:07.020 --> 07:50:09.468 align:start position:0% in our protocol Suite so first for those applications<07:50:07.620> and<07:50:08.040> instances<07:50:08.520> that<07:50:09.000> depend 07:50:09.468 --> 07:50:09.478 align:start position:0% applications and instances that depend 07:50:09.478 --> 07:50:12.468 align:start position:0% applications and instances that depend on<07:50:09.958> data<07:50:10.378> to<07:50:10.798> be<07:50:10.978> reliable<07:50:11.580> in<07:50:12.058> terms<07:50:12.298> of 07:50:12.468 --> 07:50:12.478 align:start position:0% on data to be reliable in terms of 07:50:12.478 --> 07:50:15.830 align:start position:0% on data to be reliable in terms of delivery<07:50:13.378> and<07:50:14.040> integrity<07:50:14.580> the<07:50:15.420> transmission 07:50:15.830 --> 07:50:15.840 align:start position:0% delivery and integrity the transmission 07:50:15.840 --> 07:50:20.330 align:start position:0% delivery and integrity the transmission control<07:50:16.740> protocol<07:50:17.458> or<07:50:18.420> TCP<07:50:19.320> and<07:50:20.040> I'm<07:50:20.160> just 07:50:20.330 --> 07:50:20.340 align:start position:0% control protocol or TCP and I'm just 07:50:20.340 --> 07:50:23.030 align:start position:0% control protocol or TCP and I'm just going<07:50:20.398> to<07:50:20.520> write<07:50:20.638> out 07:50:23.030 --> 07:50:23.040 align:start position:0% 07:50:23.040 --> 07:50:26.868 align:start position:0% transmission 07:50:26.868 --> 07:50:26.878 align:start position:0% 07:50:26.878 --> 07:50:28.610 align:start position:0% control 07:50:28.610 --> 07:50:28.620 align:start position:0% control 07:50:28.620 --> 07:50:32.090 align:start position:0% control protocol<07:50:29.280> is<07:50:30.240> a<07:50:30.600> really<07:50:30.718> Dependable<07:50:31.440> protocol 07:50:32.090 --> 07:50:32.100 align:start position:0% protocol is a really Dependable protocol 07:50:32.100 --> 07:50:35.150 align:start position:0% protocol is a really Dependable protocol and<07:50:32.700> provides<07:50:33.120> a<07:50:33.540> number<07:50:33.718> of<07:50:33.898> features<07:50:34.378> first 07:50:35.150 --> 07:50:35.160 align:start position:0% and provides a number of features first 07:50:35.160 --> 07:50:38.510 align:start position:0% and provides a number of features first it<07:50:35.638> guarantees<07:50:36.360> that<07:50:36.718> data<07:50:37.138> delivery<07:50:37.680> and 07:50:38.510 --> 07:50:38.520 align:start position:0% it guarantees that data delivery and 07:50:38.520 --> 07:50:39.948 align:start position:0% it guarantees that data delivery and besides 07:50:39.948 --> 07:50:39.958 align:start position:0% besides 07:50:39.958 --> 07:50:43.310 align:start position:0% besides um<07:50:40.280> guaranteeing<07:50:41.280> that<07:50:42.000> delivery<07:50:42.718> it<07:50:43.020> also 07:50:43.310 --> 07:50:43.320 align:start position:0% um guaranteeing that delivery it also 07:50:43.320 --> 07:50:46.310 align:start position:0% um guaranteeing that delivery it also has<07:50:43.680> a<07:50:43.860> certain<07:50:43.978> amount<07:50:44.340> of<07:50:44.478> reliability<07:50:45.478> it 07:50:46.310 --> 07:50:46.320 align:start position:0% has a certain amount of reliability it 07:50:46.320 --> 07:50:48.770 align:start position:0% has a certain amount of reliability it also<07:50:46.558> offers<07:50:47.040> flow<07:50:47.760> control<07:50:47.940> which<07:50:48.360> as<07:50:48.540> we've 07:50:48.770 --> 07:50:48.780 align:start position:0% also offers flow control which as we've 07:50:48.780 --> 07:50:51.530 align:start position:0% also offers flow control which as we've mentioned<07:50:49.020> in<07:50:49.200> the<07:50:49.320> past<07:50:49.458> assists<07:50:50.540> ascending 07:50:51.530 --> 07:50:51.540 align:start position:0% mentioned in the past assists ascending 07:50:51.540 --> 07:50:53.930 align:start position:0% mentioned in the past assists ascending station<07:50:51.958> in<07:50:52.740> making<07:50:52.978> sure<07:50:53.160> it<07:50:53.398> doesn't<07:50:53.580> send 07:50:53.930 --> 07:50:53.940 align:start position:0% station in making sure it doesn't send 07:50:53.940 --> 07:50:56.810 align:start position:0% station in making sure it doesn't send data<07:50:54.478> faster<07:50:54.958> then<07:50:55.500> the<07:50:55.740> receiver<07:50:56.100> can<07:50:56.398> handle 07:50:56.810 --> 07:50:56.820 align:start position:0% data faster then the receiver can handle 07:50:56.820 --> 07:50:59.628 align:start position:0% data faster then the receiver can handle this<07:50:57.600> function<07:50:57.958> also<07:50:58.378> is<07:50:58.500> going<07:50:58.680> to<07:50:58.798> assist<07:50:58.978> in 07:50:59.628 --> 07:50:59.638 align:start position:0% this function also is going to assist in 07:50:59.638 --> 07:51:01.968 align:start position:0% this function also is going to assist in the<07:51:00.000> reliability<07:51:00.600> of<07:51:00.958> data<07:51:01.320> because<07:51:01.680> it 07:51:01.968 --> 07:51:01.978 align:start position:0% the reliability of data because it 07:51:01.978 --> 07:51:04.368 align:start position:0% the reliability of data because it ensures<07:51:02.458> that<07:51:03.000> there<07:51:03.180> isn't<07:51:03.420> any<07:51:03.600> data<07:51:04.080> lost 07:51:04.368 --> 07:51:04.378 align:start position:0% ensures that there isn't any data lost 07:51:04.378 --> 07:51:07.310 align:start position:0% ensures that there isn't any data lost due<07:51:05.280> to<07:51:05.398> overloading 07:51:07.310 --> 07:51:07.320 align:start position:0% due to overloading 07:51:07.320 --> 07:51:08.270 align:start position:0% due to overloading um 07:51:08.270 --> 07:51:08.280 align:start position:0% um 07:51:08.280 --> 07:51:15.110 align:start position:0% um the<07:51:09.000> receiving<07:51:09.298> station 07:51:15.110 --> 07:51:15.120 align:start position:0% 07:51:15.120 --> 07:51:17.868 align:start position:0% now<07:51:15.600> TCP<07:51:16.200> also<07:51:16.558> contains<07:51:17.040> something<07:51:17.280> called<07:51:17.580> a 07:51:17.868 --> 07:51:17.878 align:start position:0% now TCP also contains something called a 07:51:17.878 --> 07:51:20.270 align:start position:0% now TCP also contains something called a checksum<07:51:18.540> mechanism<07:51:19.138> and<07:51:19.620> what<07:51:19.798> this<07:51:19.920> does<07:51:20.100> is 07:51:20.270 --> 07:51:20.280 align:start position:0% checksum mechanism and what this does is 07:51:20.280 --> 07:51:23.510 align:start position:0% checksum mechanism and what this does is it<07:51:20.458> assists<07:51:20.940> with<07:51:21.718> error<07:51:22.200> detection<07:51:22.558> the 07:51:23.510 --> 07:51:23.520 align:start position:0% it assists with error detection the 07:51:23.520 --> 07:51:25.548 align:start position:0% it assists with error detection the level<07:51:23.760> of<07:51:24.058> error<07:51:24.360> detection<07:51:24.600> isn't<07:51:25.138> as<07:51:25.320> strong 07:51:25.548 --> 07:51:25.558 align:start position:0% level of error detection isn't as strong 07:51:25.558 --> 07:51:28.070 align:start position:0% level of error detection isn't as strong as<07:51:25.798> that<07:51:26.040> of<07:51:26.458> some<07:51:26.638> of<07:51:26.760> the<07:51:26.940> lower<07:51:27.120> layers<07:51:27.840> and 07:51:28.070 --> 07:51:28.080 align:start position:0% as that of some of the lower layers and 07:51:28.080 --> 07:51:31.368 align:start position:0% as that of some of the lower layers and you<07:51:28.260> recall<07:51:28.620> that<07:51:29.458> this<07:51:29.940> is<07:51:30.540> in<07:51:30.718> the<07:51:30.898> transport 07:51:31.368 --> 07:51:31.378 align:start position:0% you recall that this is in the transport 07:51:31.378 --> 07:51:33.830 align:start position:0% you recall that this is in the transport layer<07:51:31.798> of<07:51:31.978> the<07:51:32.100> tcpip<07:51:32.760> stack 07:51:33.830 --> 07:51:33.840 align:start position:0% layer of the tcpip stack 07:51:33.840 --> 07:51:36.468 align:start position:0% layer of the tcpip stack but<07:51:34.320> it<07:51:34.680> does<07:51:34.920> catch<07:51:35.458> some<07:51:35.700> specific<07:51:36.000> errors 07:51:36.468 --> 07:51:36.478 align:start position:0% but it does catch some specific errors 07:51:36.478 --> 07:51:39.530 align:start position:0% but it does catch some specific errors that<07:51:36.660> may<07:51:36.780> go<07:51:36.958> unnoticed<07:51:37.558> by<07:51:37.860> other<07:51:38.540> layers 07:51:39.530 --> 07:51:39.540 align:start position:0% that may go unnoticed by other layers 07:51:39.540 --> 07:51:41.930 align:start position:0% that may go unnoticed by other layers and<07:51:39.718> and<07:51:39.958> by<07:51:40.260> the<07:51:40.378> way<07:51:40.500> this<07:51:41.398> checksum 07:51:41.930 --> 07:51:41.940 align:start position:0% and and by the way this checksum 07:51:41.940 --> 07:51:44.628 align:start position:0% and and by the way this checksum basically<07:51:42.360> it's<07:51:42.540> it<07:51:42.840> sort<07:51:43.080> of<07:51:43.260> has<07:51:44.040> a<07:51:44.340> number 07:51:44.628 --> 07:51:44.638 align:start position:0% basically it's it sort of has a number 07:51:44.638 --> 07:51:46.448 align:start position:0% basically it's it sort of has a number that<07:51:44.940> it<07:51:45.180> creates 07:51:46.448 --> 07:51:46.458 align:start position:0% that it creates 07:51:46.458 --> 07:51:49.190 align:start position:0% that it creates based<07:51:47.458> on<07:51:47.580> the<07:51:47.820> data<07:51:48.120> and<07:51:48.540> it<07:51:48.660> can<07:51:48.840> check<07:51:48.958> that 07:51:49.190 --> 07:51:49.200 align:start position:0% based on the data and it can check that 07:51:49.200 --> 07:51:50.628 align:start position:0% based on the data and it can check that number<07:51:49.440> at<07:51:49.740> the<07:51:49.860> beginning<07:51:49.978> and<07:51:50.280> at<07:51:50.458> the<07:51:50.580> end 07:51:50.628 --> 07:51:50.638 align:start position:0% number at the beginning and at the end 07:51:50.638 --> 07:51:53.510 align:start position:0% number at the beginning and at the end to<07:51:50.878> make<07:51:51.000> sure<07:51:51.120> we<07:51:51.240> haven't<07:51:51.360> lost<07:51:51.660> anything 07:51:53.510 --> 07:51:53.520 align:start position:0% to make sure we haven't lost anything 07:51:53.520 --> 07:51:56.770 align:start position:0% to make sure we haven't lost anything now<07:51:54.058> this<07:51:54.420> protocol<07:51:54.780> attempts<07:51:55.378> to<07:51:55.558> alleviate 07:51:56.770 --> 07:51:56.780 align:start position:0% now this protocol attempts to alleviate 07:51:56.780 --> 07:51:59.750 align:start position:0% now this protocol attempts to alleviate MTU<07:51:57.780> if<07:51:58.020> you<07:51:58.138> recall<07:51:58.558> uh<07:51:59.218> what<07:51:59.398> we<07:51:59.520> talked 07:51:59.750 --> 07:51:59.760 align:start position:0% MTU if you recall uh what we talked 07:51:59.760 --> 07:52:02.330 align:start position:0% MTU if you recall uh what we talked about<07:51:59.820> with<07:52:00.058> MTU<07:52:00.660> there<07:52:00.978> mismatches<07:52:01.978> on<07:52:02.280> the 07:52:02.330 --> 07:52:02.340 align:start position:0% about with MTU there mismatches on the 07:52:02.340 --> 07:52:05.330 align:start position:0% about with MTU there mismatches on the data<07:52:02.700> link<07:52:02.820> layer<07:52:03.240> by<07:52:03.840> establishing<07:52:04.558> maximum 07:52:05.330 --> 07:52:05.340 align:start position:0% data link layer by establishing maximum 07:52:05.340 --> 07:52:07.670 align:start position:0% data link layer by establishing maximum segment<07:52:05.700> sizes<07:52:06.180> that<07:52:06.478> can<07:52:06.600> be<07:52:06.780> accepted<07:52:07.320> by 07:52:07.670 --> 07:52:07.680 align:start position:0% segment sizes that can be accepted by 07:52:07.680 --> 07:52:10.368 align:start position:0% segment sizes that can be accepted by TCP<07:52:08.340> this<07:52:09.058> is<07:52:09.180> also<07:52:09.420> going<07:52:09.540> to<07:52:09.660> reduce<07:52:09.840> what<07:52:10.260> we 07:52:10.368 --> 07:52:10.378 align:start position:0% TCP this is also going to reduce what we 07:52:10.378 --> 07:52:13.968 align:start position:0% TCP this is also going to reduce what we talked<07:52:10.740> about<07:52:10.798> earlier<07:52:11.218> that<07:52:11.760> MTU<07:52:12.440> black<07:52:13.440> hole 07:52:13.968 --> 07:52:13.978 align:start position:0% talked about earlier that MTU black hole 07:52:13.978 --> 07:52:17.150 align:start position:0% talked about earlier that MTU black hole now<07:52:14.520> further<07:52:14.940> examining<07:52:15.540> IP<07:52:16.138> or<07:52:16.500> the<07:52:16.798> Internet 07:52:17.150 --> 07:52:17.160 align:start position:0% now further examining IP or the Internet 07:52:17.160 --> 07:52:18.830 align:start position:0% now further examining IP or the Internet Protocol 07:52:18.830 --> 07:52:18.840 align:start position:0% Protocol 07:52:18.840 --> 07:52:22.010 align:start position:0% Protocol which<07:52:19.378> is<07:52:19.500> aptly<07:52:19.920> name<07:52:20.160> and<07:52:20.878> exists<07:52:21.360> at<07:52:21.718> the 07:52:22.010 --> 07:52:22.020 align:start position:0% which is aptly name and exists at the 07:52:22.020 --> 07:52:23.750 align:start position:0% which is aptly name and exists at the internet 07:52:23.750 --> 07:52:23.760 align:start position:0% internet 07:52:23.760 --> 07:52:28.310 align:start position:0% internet layer<07:52:24.420> unlike<07:52:25.378> TCP<07:52:26.218> IP<07:52:27.120> is<07:52:27.298> characterized<07:52:28.020> as 07:52:28.310 --> 07:52:28.320 align:start position:0% layer unlike TCP IP is characterized as 07:52:28.320 --> 07:52:30.948 align:start position:0% layer unlike TCP IP is characterized as being<07:52:28.920> connectionless<07:52:29.700> or<07:52:30.120> a<07:52:30.298> best<07:52:30.540> effort 07:52:30.948 --> 07:52:30.958 align:start position:0% being connectionless or a best effort 07:52:30.958 --> 07:52:32.690 align:start position:0% being connectionless or a best effort delivery<07:52:31.378> which<07:52:31.620> is<07:52:31.740> also<07:52:31.978> like<07:52:32.280> UDP<07:52:32.520> which 07:52:32.690 --> 07:52:32.700 align:start position:0% delivery which is also like UDP which 07:52:32.700 --> 07:52:35.208 align:start position:0% delivery which is also like UDP which we'll<07:52:32.820> see<07:52:32.940> in<07:52:33.058> a<07:52:33.180> second<07:52:33.298> it<07:52:34.260> outlines<07:52:34.740> the 07:52:35.208 --> 07:52:35.218 align:start position:0% we'll see in a second it outlines the 07:52:35.218 --> 07:52:38.868 align:start position:0% we'll see in a second it outlines the structure<07:52:35.700> then<07:52:35.940> of<07:52:36.840> information<07:52:37.580> which<07:52:38.580> is 07:52:38.868 --> 07:52:38.878 align:start position:0% structure then of information which is 07:52:38.878 --> 07:52:43.968 align:start position:0% structure then of information which is called<07:52:39.200> datagrams<07:52:40.200> or<07:52:41.040> packets 07:52:43.968 --> 07:52:43.978 align:start position:0% 07:52:43.978 --> 07:52:46.368 align:start position:0% and<07:52:44.580> how<07:52:44.940> we're<07:52:45.478> going<07:52:45.600> to<07:52:45.780> package<07:52:46.080> this 07:52:46.368 --> 07:52:46.378 align:start position:0% and how we're going to package this 07:52:46.378 --> 07:52:48.948 align:start position:0% and how we're going to package this stuff<07:52:46.620> to<07:52:47.100> send<07:52:47.280> it<07:52:47.458> over<07:52:47.580> the<07:52:47.820> network<07:52:48.000> this 07:52:48.948 --> 07:52:48.958 align:start position:0% stuff to send it over the network this 07:52:48.958 --> 07:52:51.170 align:start position:0% stuff to send it over the network this protocol<07:52:49.260> is<07:52:49.558> more<07:52:49.740> concerned<07:52:50.340> with<07:52:50.760> source 07:52:51.170 --> 07:52:51.180 align:start position:0% protocol is more concerned with source 07:52:51.180 --> 07:52:55.070 align:start position:0% protocol is more concerned with source to<07:52:51.360> destination<07:52:52.100> navigation<07:52:53.120> or<07:52:54.120> planning<07:52:54.718> or 07:52:55.070 --> 07:52:55.080 align:start position:0% to destination navigation or planning or 07:52:55.080 --> 07:52:57.888 align:start position:0% to destination navigation or planning or routing<07:52:55.620> as<07:52:56.280> well<07:52:56.458> as<07:52:56.700> host<07:52:57.240> identification 07:52:57.888 --> 07:52:57.898 align:start position:0% routing as well as host identification 07:52:57.898 --> 07:53:01.730 align:start position:0% routing as well as host identification and<07:52:58.378> data<07:52:58.740> delivery<07:52:59.120> solely<07:53:00.120> by<07:53:00.420> using<07:53:00.840> the<07:53:01.378> IP 07:53:01.730 --> 07:53:01.740 align:start position:0% and data delivery solely by using the IP 07:53:01.740 --> 07:53:03.288 align:start position:0% and data delivery solely by using the IP address<07:53:01.920> so<07:53:02.580> this<07:53:02.760> is<07:53:02.820> slightly<07:53:03.120> different 07:53:03.288 --> 07:53:03.298 align:start position:0% address so this is slightly different 07:53:03.298 --> 07:53:05.990 align:start position:0% address so this is slightly different from<07:53:03.780> TCP<07:53:04.440> which<07:53:04.920> is<07:53:05.040> doing<07:53:05.218> stuff<07:53:05.458> in<07:53:05.700> a<07:53:05.820> much 07:53:05.990 --> 07:53:06.000 align:start position:0% from TCP which is doing stuff in a much 07:53:06.000 --> 07:53:08.448 align:start position:0% from TCP which is doing stuff in a much more<07:53:06.180> different<07:53:06.360> way<07:53:06.718> now<07:53:07.260> IP<07:53:07.620> is<07:53:07.860> used<07:53:08.160> for 07:53:08.448 --> 07:53:08.458 align:start position:0% more different way now IP is used for 07:53:08.458 --> 07:53:11.270 align:start position:0% more different way now IP is used for communications<07:53:08.940> between<07:53:09.540> one<07:53:09.958> or<07:53:10.138> many<07:53:10.440> IP 07:53:11.270 --> 07:53:11.280 align:start position:0% communications between one or many IP 07:53:11.280 --> 07:53:13.968 align:start position:0% communications between one or many IP based<07:53:11.940> networks<07:53:12.298> and<07:53:12.840> because<07:53:13.020> of<07:53:13.500> its<07:53:13.798> design 07:53:13.968 --> 07:53:13.978 align:start position:0% based networks and because of its design 07:53:13.978 --> 07:53:16.910 align:start position:0% based networks and because of its design it<07:53:14.940> makes<07:53:15.058> it<07:53:15.360> the<07:53:15.718> principal<07:53:16.200> protocol<07:53:16.620> of 07:53:16.910 --> 07:53:16.920 align:start position:0% it makes it the principal protocol of 07:53:16.920 --> 07:53:19.788 align:start position:0% it makes it the principal protocol of the<07:53:17.100> internet<07:53:17.240> and<07:53:18.240> it's<07:53:18.600> essential<07:53:19.138> to 07:53:19.788 --> 07:53:19.798 align:start position:0% the internet and it's essential to 07:53:19.798 --> 07:53:23.270 align:start position:0% the internet and it's essential to connect<07:53:19.920> to<07:53:20.340> it<07:53:20.520> so<07:53:21.360> unless<07:53:22.020> we<07:53:22.260> are<07:53:22.440> using<07:53:22.860> IP 07:53:23.270 --> 07:53:23.280 align:start position:0% connect to it so unless we are using IP 07:53:23.280 --> 07:53:25.490 align:start position:0% connect to it so unless we are using IP address<07:53:23.458> in<07:53:23.820> today's<07:53:24.000> day<07:53:24.240> and<07:53:24.420> age<07:53:24.600> we<07:53:25.260> will 07:53:25.490 --> 07:53:25.500 align:start position:0% address in today's day and age we will 07:53:25.500 --> 07:53:27.590 align:start position:0% address in today's day and age we will not<07:53:25.740> be<07:53:25.978> able<07:53:26.100> to<07:53:26.340> connect<07:53:26.520> to<07:53:26.820> this<07:53:27.120> big<07:53:27.298> thing 07:53:27.590 --> 07:53:27.600 align:start position:0% not be able to connect to this big thing 07:53:27.600 --> 07:53:30.468 align:start position:0% not be able to connect to this big thing called<07:53:28.080> the<07:53:28.620> internet<07:53:28.760> now<07:53:29.760> the<07:53:30.120> terms 07:53:30.468 --> 07:53:30.478 align:start position:0% called the internet now the terms 07:53:30.478 --> 07:53:34.788 align:start position:0% called the internet now the terms connection<07:53:31.080> less<07:53:31.620> and<07:53:32.040> connection<07:53:32.218> oriented 07:53:34.788 --> 07:53:34.798 align:start position:0% connection less and connection oriented 07:53:34.798 --> 07:53:37.010 align:start position:0% connection less and connection oriented relate<07:53:35.580> to<07:53:35.700> the<07:53:35.940> steps<07:53:36.298> that<07:53:36.478> are<07:53:36.600> taken 07:53:37.010 --> 07:53:37.020 align:start position:0% relate to the steps that are taken 07:53:37.020 --> 07:53:39.650 align:start position:0% relate to the steps that are taken before<07:53:37.558> the<07:53:37.920> data<07:53:38.280> is<07:53:38.520> transmitted<07:53:39.180> by<07:53:39.420> a 07:53:39.650 --> 07:53:39.660 align:start position:0% before the data is transmitted by a 07:53:39.660 --> 07:53:41.090 align:start position:0% before the data is transmitted by a given<07:53:39.898> protocol<07:53:40.200> whatever<07:53:40.500> that<07:53:40.860> protocol 07:53:41.090 --> 07:53:41.100 align:start position:0% given protocol whatever that protocol 07:53:41.100 --> 07:53:43.610 align:start position:0% given protocol whatever that protocol might<07:53:41.458> be<07:53:41.638> with<07:53:42.420> TCP<07:53:42.958> we're<07:53:43.138> looking<07:53:43.320> at 07:53:43.610 --> 07:53:43.620 align:start position:0% might be with TCP we're looking at 07:53:43.620 --> 07:53:46.310 align:start position:0% might be with TCP we're looking at connection<07:53:44.100> oriented<07:53:45.058> and<07:53:45.780> of<07:53:46.020> course<07:53:46.080> with 07:53:46.310 --> 07:53:46.320 align:start position:0% connection oriented and of course with 07:53:46.320 --> 07:53:49.310 align:start position:0% connection oriented and of course with IP<07:53:46.620> we're<07:53:46.860> looking<07:53:46.978> at<07:53:47.218> connection<07:53:47.520> less 07:53:49.310 --> 07:53:49.320 align:start position:0% IP we're looking at connection less 07:53:49.320 --> 07:53:52.250 align:start position:0% IP we're looking at connection less and<07:53:49.978> for<07:53:50.160> instance<07:53:50.458> the<07:53:51.000> connection<07:53:51.360> oriented 07:53:52.250 --> 07:53:52.260 align:start position:0% and for instance the connection oriented 07:53:52.260 --> 07:53:55.010 align:start position:0% and for instance the connection oriented protocol<07:53:52.680> is<07:53:53.520> going<07:53:53.638> to<07:53:53.820> ensure<07:53:54.298> a<07:53:54.840> connection 07:53:55.010 --> 07:53:55.020 align:start position:0% protocol is going to ensure a connection 07:53:55.020 --> 07:53:57.708 align:start position:0% protocol is going to ensure a connection is<07:53:55.680> established<07:53:56.398> before<07:53:56.940> the<07:53:57.240> sending<07:53:57.600> of 07:53:57.708 --> 07:53:57.718 align:start position:0% is established before the sending of 07:53:57.718 --> 07:54:00.468 align:start position:0% is established before the sending of data<07:53:58.138> meaning<07:53:58.860> it<07:53:59.160> is<07:53:59.340> oriented<07:53:59.878> towards<07:54:00.298> a 07:54:00.468 --> 07:54:00.478 align:start position:0% data meaning it is oriented towards a 07:54:00.478 --> 07:54:02.510 align:start position:0% data meaning it is oriented towards a connection<07:54:00.620> whereas<07:54:01.620> a<07:54:01.860> connection<07:54:02.040> less 07:54:02.510 --> 07:54:02.520 align:start position:0% connection whereas a connection less 07:54:02.520 --> 07:54:04.730 align:start position:0% connection whereas a connection less isn't<07:54:03.120> going<07:54:03.298> to<07:54:03.478> doesn't<07:54:03.958> matter<07:54:04.320> if<07:54:04.558> there 07:54:04.730 --> 07:54:04.740 align:start position:0% isn't going to doesn't matter if there 07:54:04.740 --> 07:54:06.708 align:start position:0% isn't going to doesn't matter if there is<07:54:04.860> a<07:54:04.978> connection<07:54:05.040> established<07:54:05.760> already 07:54:06.708 --> 07:54:06.718 align:start position:0% is a connection established already 07:54:06.718 --> 07:54:09.350 align:start position:0% is a connection established already so<07:54:07.378> the<07:54:07.798> next<07:54:08.040> protocol<07:54:08.580> which<07:54:09.000> is<07:54:09.120> also 07:54:09.350 --> 07:54:09.360 align:start position:0% so the next protocol which is also 07:54:09.360 --> 07:54:10.850 align:start position:0% so the next protocol which is also connection<07:54:09.600> last<07:54:10.020> that<07:54:10.320> we<07:54:10.500> want<07:54:10.558> to<07:54:10.680> talk 07:54:10.850 --> 07:54:10.860 align:start position:0% connection last that we want to talk 07:54:10.860 --> 07:54:14.208 align:start position:0% connection last that we want to talk about<07:54:10.978> is<07:54:11.458> something<07:54:11.700> called<07:54:12.420> UDP<07:54:12.840> now<07:54:13.798> since 07:54:14.208 --> 07:54:14.218 align:start position:0% about is something called UDP now since 07:54:14.218 --> 07:54:16.910 align:start position:0% about is something called UDP now since we<07:54:14.638> have<07:54:14.940> many<07:54:15.718> applications<07:54:16.378> and<07:54:16.740> their 07:54:16.910 --> 07:54:16.920 align:start position:0% we have many applications and their 07:54:16.920 --> 07:54:19.610 align:start position:0% we have many applications and their functions<07:54:17.280> depend<07:54:17.638> on<07:54:17.820> data<07:54:18.240> being<07:54:18.420> sent<07:54:18.718> in<07:54:19.440> a 07:54:19.610 --> 07:54:19.620 align:start position:0% functions depend on data being sent in a 07:54:19.620 --> 07:54:22.070 align:start position:0% functions depend on data being sent in a timely<07:54:19.920> manner<07:54:20.638> TCP<07:54:21.360> and<07:54:21.540> its<07:54:21.840> connection 07:54:22.070 --> 07:54:22.080 align:start position:0% timely manner TCP and its connection 07:54:22.080 --> 07:54:24.468 align:start position:0% timely manner TCP and its connection oriented<07:54:22.978> properties<07:54:23.458> hinder<07:54:24.298> their 07:54:24.468 --> 07:54:24.478 align:start position:0% oriented properties hinder their 07:54:24.478 --> 07:54:27.048 align:start position:0% oriented properties hinder their performance<07:54:25.020> in<07:54:25.860> these<07:54:26.100> cases<07:54:26.398> we're<07:54:26.638> able<07:54:26.940> to 07:54:27.048 --> 07:54:27.058 align:start position:0% performance in these cases we're able to 07:54:27.058 --> 07:54:28.548 align:start position:0% performance in these cases we're able to use<07:54:27.240> something<07:54:27.478> called 07:54:28.548 --> 07:54:28.558 align:start position:0% use something called 07:54:28.558 --> 07:54:34.150 align:start position:0% use something called UDP<07:54:28.978> again<07:54:29.878> the<07:54:30.478> user 07:54:34.150 --> 07:54:34.160 align:start position:0% 07:54:34.160 --> 07:54:38.750 align:start position:0% datagram<07:54:35.160> protocol 07:54:38.750 --> 07:54:38.760 align:start position:0% 07:54:38.760 --> 07:54:42.110 align:start position:0% and<07:54:39.840> UDP<07:54:40.200> is<07:54:40.500> connection<07:54:40.740> last<07:54:41.218> just<07:54:41.580> like<07:54:41.760> IP 07:54:42.110 --> 07:54:42.120 align:start position:0% and UDP is connection last just like IP 07:54:42.120 --> 07:54:44.030 align:start position:0% and UDP is connection last just like IP is 07:54:44.030 --> 07:54:44.040 align:start position:0% is 07:54:44.040 --> 07:54:46.610 align:start position:0% is and<07:54:44.520> it's<07:54:44.638> a<07:54:44.760> that<07:54:45.000> means<07:54:45.240> it's<07:54:45.420> a<07:54:45.660> best<07:54:45.958> effort 07:54:46.610 --> 07:54:46.620 align:start position:0% and it's a that means it's a best effort 07:54:46.620 --> 07:54:49.910 align:start position:0% and it's a that means it's a best effort delivery<07:54:47.520> protocol<07:54:47.940> so<07:54:48.718> with<07:54:48.898> TCP<07:54:49.440> if<07:54:49.620> packets 07:54:49.910 --> 07:54:49.920 align:start position:0% delivery protocol so with TCP if packets 07:54:49.920 --> 07:54:51.650 align:start position:0% delivery protocol so with TCP if packets get<07:54:50.160> delayed<07:54:50.580> or<07:54:50.700> if<07:54:50.820> they're<07:54:51.000> needed<07:54:51.360> to<07:54:51.478> be 07:54:51.650 --> 07:54:51.660 align:start position:0% get delayed or if they're needed to be 07:54:51.660 --> 07:54:54.468 align:start position:0% get delayed or if they're needed to be resent<07:54:52.200> due<07:54:52.558> to<07:54:52.680> a<07:54:52.860> collision<07:54:53.160> the<07:54:53.760> TCP<07:54:54.240> on<07:54:54.360> the 07:54:54.468 --> 07:54:54.478 align:start position:0% resent due to a collision the TCP on the 07:54:54.478 --> 07:54:56.090 align:start position:0% resent due to a collision the TCP on the receiving<07:54:54.660> end<07:54:54.898> is<07:54:55.138> going<07:54:55.320> to<07:54:55.440> wait<07:54:55.620> for<07:54:55.920> the 07:54:56.090 --> 07:54:56.100 align:start position:0% receiving end is going to wait for the 07:54:56.100 --> 07:54:58.610 align:start position:0% receiving end is going to wait for the lost<07:54:56.280> or<07:54:56.458> late<07:54:56.638> packets<07:54:57.058> to<07:54:57.298> arrive<07:54:57.660> and<07:54:58.378> with 07:54:58.610 --> 07:54:58.620 align:start position:0% lost or late packets to arrive and with 07:54:58.620 --> 07:55:01.128 align:start position:0% lost or late packets to arrive and with some<07:54:58.920> sensitive<07:54:59.398> data<07:54:59.820> delivery<07:55:00.600> this<07:55:01.020> is 07:55:01.128 --> 07:55:01.138 align:start position:0% some sensitive data delivery this is 07:55:01.138 --> 07:55:03.610 align:start position:0% some sensitive data delivery this is going<07:55:01.260> to<07:55:01.320> cause<07:55:01.440> a<07:55:01.620> lot<07:55:01.680> of<07:55:01.860> problems<07:55:02.280> and<07:55:03.120> UDP 07:55:03.610 --> 07:55:03.620 align:start position:0% going to cause a lot of problems and UDP 07:55:03.620 --> 07:55:06.830 align:start position:0% going to cause a lot of problems and UDP is<07:55:04.620> what<07:55:04.920> we<07:55:05.040> call<07:55:05.218> a<07:55:05.820> stateless<07:55:06.298> protocol 07:55:06.830 --> 07:55:06.840 align:start position:0% is what we call a stateless protocol 07:55:06.840 --> 07:55:10.368 align:start position:0% is what we call a stateless protocol which<07:55:07.680> prefers<07:55:08.218> the<07:55:08.520> packet<07:55:09.000> loss<07:55:09.478> over<07:55:09.898> the 07:55:10.368 --> 07:55:10.378 align:start position:0% which prefers the packet loss over the 07:55:10.378 --> 07:55:13.610 align:start position:0% which prefers the packet loss over the delay<07:55:10.740> in<07:55:11.340> waiting<07:55:11.878> so<07:55:12.540> UDP<07:55:12.898> is<07:55:13.020> only<07:55:13.260> going<07:55:13.440> to 07:55:13.610 --> 07:55:13.620 align:start position:0% delay in waiting so UDP is only going to 07:55:13.620 --> 07:55:17.208 align:start position:0% delay in waiting so UDP is only going to add<07:55:13.798> a<07:55:14.218> checksum<07:55:14.760> to<07:55:15.298> the<07:55:15.478> data<07:55:15.840> for<07:55:16.218> data 07:55:17.208 --> 07:55:17.218 align:start position:0% add a checksum to the data for data 07:55:17.218 --> 07:55:21.110 align:start position:0% add a checksum to the data for data Integrity<07:55:18.000> it's<07:55:18.958> also<07:55:19.260> going<07:55:19.500> to<07:55:20.040> uh<07:55:20.820> address 07:55:21.110 --> 07:55:21.120 align:start position:0% Integrity it's also going to uh address 07:55:21.120 --> 07:55:23.690 align:start position:0% Integrity it's also going to uh address port<07:55:21.718> numbers<07:55:22.020> for<07:55:22.558> specific<07:55:22.978> functions 07:55:23.690 --> 07:55:23.700 align:start position:0% port numbers for specific functions 07:55:23.700 --> 07:55:26.110 align:start position:0% port numbers for specific functions between<07:55:24.660> the<07:55:24.958> source<07:55:25.260> and<07:55:25.378> the<07:55:25.558> destination 07:55:26.110 --> 07:55:26.120 align:start position:0% between the source and the destination 07:55:26.120 --> 07:55:31.070 align:start position:0% between the source and the destination nodes<07:55:27.120> such<07:55:27.420> as<07:55:27.958> UDP<07:55:28.320> Port<07:55:28.558> 53<07:55:29.398> for<07:55:30.180> DNS<07:55:30.718> which 07:55:31.070 --> 07:55:31.080 align:start position:0% nodes such as UDP Port 53 for DNS which 07:55:31.080 --> 07:55:32.690 align:start position:0% nodes such as UDP Port 53 for DNS which is<07:55:31.138> one<07:55:31.320> that<07:55:31.500> you<07:55:31.620> should<07:55:31.798> remember<07:55:31.978> from<07:55:32.520> an 07:55:32.690 --> 07:55:32.700 align:start position:0% is one that you should remember from an 07:55:32.700 --> 07:55:35.868 align:start position:0% is one that you should remember from an earlier<07:55:33.000> module<07:55:33.540> Now<07:55:34.500> udp's<07:55:35.100> features<07:55:35.580> make 07:55:35.868 --> 07:55:35.878 align:start position:0% earlier module Now udp's features make 07:55:35.878 --> 07:55:38.930 align:start position:0% earlier module Now udp's features make it<07:55:36.058> a<07:55:36.298> solid<07:55:36.660> protocol<07:55:37.080> and<07:55:37.860> it's<07:55:38.100> used<07:55:38.458> for 07:55:38.930 --> 07:55:38.940 align:start position:0% it a solid protocol and it's used for 07:55:38.940 --> 07:55:41.810 align:start position:0% it a solid protocol and it's used for applications<07:55:39.540> such<07:55:40.020> as<07:55:40.260> VoIP<07:55:41.100> or<07:55:41.280> voice<07:55:41.520> over 07:55:41.810 --> 07:55:41.820 align:start position:0% applications such as VoIP or voice over 07:55:41.820 --> 07:55:43.070 align:start position:0% applications such as VoIP or voice over IP 07:55:43.070 --> 07:55:43.080 align:start position:0% IP 07:55:43.080 --> 07:55:45.948 align:start position:0% IP and<07:55:43.798> online<07:55:44.100> gaming<07:55:44.760> this<07:55:45.420> makes<07:55:45.660> sense 07:55:45.948 --> 07:55:45.958 align:start position:0% and online gaming this makes sense 07:55:45.958 --> 07:55:49.190 align:start position:0% and online gaming this makes sense because<07:55:46.440> we<07:55:47.100> don't<07:55:47.340> care<07:55:47.940> if<07:55:48.540> every<07:55:48.898> single 07:55:49.190 --> 07:55:49.200 align:start position:0% because we don't care if every single 07:55:49.200 --> 07:55:51.170 align:start position:0% because we don't care if every single little<07:55:49.320> packet<07:55:49.920> arrives<07:55:50.280> what<07:55:50.520> we<07:55:50.700> want<07:55:50.820> is<07:55:51.000> we 07:55:51.170 --> 07:55:51.180 align:start position:0% little packet arrives what we want is we 07:55:51.180 --> 07:55:54.110 align:start position:0% little packet arrives what we want is we want<07:55:51.360> the<07:55:51.600> speed<07:55:51.958> with<07:55:52.680> which 07:55:54.110 --> 07:55:54.120 align:start position:0% want the speed with which 07:55:54.120 --> 07:55:56.448 align:start position:0% want the speed with which UDP<07:55:54.478> is<07:55:54.780> going<07:55:54.958> to<07:55:55.080> deliver<07:55:55.260> stuff<07:55:55.680> obviously 07:55:56.448 --> 07:55:56.458 align:start position:0% UDP is going to deliver stuff obviously 07:55:56.458 --> 07:55:58.010 align:start position:0% UDP is going to deliver stuff obviously if<07:55:56.638> we<07:55:56.760> miss<07:55:56.940> a<07:55:57.120> couple<07:55:57.240> packets<07:55:57.600> in<07:55:57.840> voice 07:55:58.010 --> 07:55:58.020 align:start position:0% if we miss a couple packets in voice 07:55:58.020 --> 07:56:01.070 align:start position:0% if we miss a couple packets in voice that's<07:55:58.440> okay<07:55:58.620> they<07:55:59.040> drop<07:55:59.340> but<07:56:00.298> we<07:56:00.600> don't<07:56:00.780> want 07:56:01.070 --> 07:56:01.080 align:start position:0% that's okay they drop but we don't want 07:56:01.080 --> 07:56:03.350 align:start position:0% that's okay they drop but we don't want to<07:56:01.260> have<07:56:01.500> to<07:56:01.620> wait<07:56:01.860> until<07:56:02.280> the<07:56:02.878> next<07:56:03.000> packet 07:56:03.350 --> 07:56:03.360 align:start position:0% to have to wait until the next packet 07:56:03.360 --> 07:56:04.670 align:start position:0% to have to wait until the next packet arrives<07:56:03.660> that's<07:56:03.898> going<07:56:04.138> to<07:56:04.200> actually<07:56:04.378> cause 07:56:04.670 --> 07:56:04.680 align:start position:0% arrives that's going to actually cause 07:56:04.680 --> 07:56:06.650 align:start position:0% arrives that's going to actually cause much<07:56:05.040> more<07:56:05.280> of<07:56:05.398> a<07:56:05.520> delay<07:56:05.820> and<07:56:06.240> so<07:56:06.420> we're<07:56:06.540> going 07:56:06.650 --> 07:56:06.660 align:start position:0% much more of a delay and so we're going 07:56:06.660 --> 07:56:09.230 align:start position:0% much more of a delay and so we're going to<07:56:06.780> use<07:56:07.020> this<07:56:07.320> one<07:56:07.500> in<07:56:07.860> more<07:56:08.040> VoIP<07:56:08.520> and<07:56:09.058> online 07:56:09.230 --> 07:56:09.240 align:start position:0% to use this one in more VoIP and online 07:56:09.240 --> 07:56:12.590 align:start position:0% to use this one in more VoIP and online gaming<07:56:09.718> purposes<07:56:10.280> now<07:56:11.280> the<07:56:11.760> next<07:56:11.878> protocol<07:56:12.298> we 07:56:12.590 --> 07:56:12.600 align:start position:0% gaming purposes now the next protocol we 07:56:12.600 --> 07:56:14.448 align:start position:0% gaming purposes now the next protocol we want<07:56:12.718> to<07:56:12.898> be<07:56:12.958> familiar<07:56:13.440> with 07:56:14.448 --> 07:56:14.458 align:start position:0% want to be familiar with 07:56:14.458 --> 07:56:16.730 align:start position:0% want to be familiar with is<07:56:14.878> called<07:56:15.058> ARP<07:56:15.478> and<07:56:15.600> it's<07:56:15.780> also<07:56:16.138> necessary 07:56:16.730 --> 07:56:16.740 align:start position:0% is called ARP and it's also necessary 07:56:16.740 --> 07:56:21.650 align:start position:0% is called ARP and it's also necessary for<07:56:17.520> routing<07:56:18.240> ARP<07:56:19.080> or<07:56:19.558> the<07:56:19.920> address 07:56:21.650 --> 07:56:21.660 align:start position:0% for routing ARP or the address 07:56:21.660 --> 07:56:25.190 align:start position:0% for routing ARP or the address resolution 07:56:25.190 --> 07:56:25.200 align:start position:0% 07:56:25.200 --> 07:56:27.830 align:start position:0% protocol<07:56:26.120> and 07:56:27.830 --> 07:56:27.840 align:start position:0% protocol and 07:56:27.840 --> 07:56:29.628 align:start position:0% protocol and the<07:56:28.440> reverse 07:56:29.628 --> 07:56:29.638 align:start position:0% the reverse 07:56:29.638 --> 07:56:33.888 align:start position:0% the reverse address<07:56:30.180> resolution<07:56:31.080> protocol<07:56:32.240> our<07:56:33.240> request 07:56:33.888 --> 07:56:33.898 align:start position:0% address resolution protocol our request 07:56:33.898 --> 07:56:36.770 align:start position:0% address resolution protocol our request and<07:56:34.378> reply<07:56:34.798> protocols<07:56:35.458> that<07:56:35.940> are<07:56:36.058> used<07:56:36.240> to<07:56:36.600> map 07:56:36.770 --> 07:56:36.780 align:start position:0% and reply protocols that are used to map 07:56:36.780 --> 07:56:39.128 align:start position:0% and reply protocols that are used to map one<07:56:37.620> kind<07:56:37.798> of<07:56:37.978> address<07:56:38.280> to<07:56:38.760> another 07:56:39.128 --> 07:56:39.138 align:start position:0% one kind of address to another 07:56:39.138 --> 07:56:42.708 align:start position:0% one kind of address to another specifically<07:56:40.138> ARP<07:56:41.100> is<07:56:41.218> designed<07:56:41.638> to<07:56:41.820> map<07:56:42.058> IP 07:56:42.708 --> 07:56:42.718 align:start position:0% specifically ARP is designed to map IP 07:56:42.718 --> 07:56:45.110 align:start position:0% specifically ARP is designed to map IP addresses<07:56:43.260> you<07:56:43.860> need<07:56:44.040> addresses<07:56:44.520> that<07:56:44.878> are 07:56:45.110 --> 07:56:45.120 align:start position:0% addresses you need addresses that are 07:56:45.120 --> 07:56:49.490 align:start position:0% addresses you need addresses that are necessary<07:56:45.958> to<07:56:46.580> tcpip<07:56:47.580> communication<07:56:48.540> to<07:56:49.260> Mac 07:56:49.490 --> 07:56:49.500 align:start position:0% necessary to tcpip communication to Mac 07:56:49.500 --> 07:56:52.010 align:start position:0% necessary to tcpip communication to Mac addresses<07:56:50.100> which<07:56:50.760> are<07:56:50.878> also<07:56:51.180> known<07:56:51.360> as<07:56:51.780> we've 07:56:52.010 --> 07:56:52.020 align:start position:0% addresses which are also known as we've 07:56:52.020 --> 07:56:54.770 align:start position:0% addresses which are also known as we've discussed<07:56:52.260> in<07:56:52.500> the<07:56:52.680> past<07:56:52.798> as<07:56:53.638> physical 07:56:54.770 --> 07:56:54.780 align:start position:0% discussed in the past as physical 07:56:54.780 --> 07:56:59.510 align:start position:0% discussed in the past as physical addresses 07:56:59.510 --> 07:56:59.520 align:start position:0% 07:56:59.520 --> 07:57:02.090 align:start position:0% and<07:57:00.120> again<07:57:00.298> IP<07:57:00.840> addresses 07:57:02.090 --> 07:57:02.100 align:start position:0% and again IP addresses 07:57:02.100 --> 07:57:08.030 align:start position:0% and again IP addresses work<07:57:02.700> on<07:57:02.940> the<07:57:03.240> networking<07:57:04.020> layer 07:57:08.030 --> 07:57:08.040 align:start position:0% 07:57:08.040 --> 07:57:14.510 align:start position:0% or<07:57:08.940> in<07:57:09.120> tcpi<07:57:09.780> PV<07:57:10.138> internet<07:57:10.620> layer 07:57:14.510 --> 07:57:14.520 align:start position:0% 07:57:14.520 --> 07:57:17.750 align:start position:0% whereas<07:57:15.058> Mac<07:57:15.298> addresses<07:57:15.860> operate<07:57:16.860> on<07:57:17.638> the 07:57:17.750 --> 07:57:17.760 align:start position:0% whereas Mac addresses operate on the 07:57:17.760 --> 07:57:21.288 align:start position:0% whereas Mac addresses operate on the network<07:57:18.020> interface<07:57:19.020> layer<07:57:19.378> of<07:57:19.558> TCP<07:57:20.100> which<07:57:21.058> in 07:57:21.288 --> 07:57:21.298 align:start position:0% network interface layer of TCP which in 07:57:21.298 --> 07:57:24.888 align:start position:0% network interface layer of TCP which in OSI<07:57:21.898> would<07:57:22.620> be<07:57:22.798> the<07:57:23.100> data<07:57:23.458> link<07:57:23.580> layer 07:57:24.888 --> 07:57:24.898 align:start position:0% OSI would be the data link layer 07:57:24.898 --> 07:57:27.708 align:start position:0% OSI would be the data link layer layer<07:57:25.500> 2. 07:57:27.708 --> 07:57:27.718 align:start position:0% layer 2. 07:57:27.718 --> 07:57:31.010 align:start position:0% layer 2. now<07:57:28.320> in<07:57:28.620> tcpipnetworking 07:57:31.010 --> 07:57:31.020 align:start position:0% now in tcpipnetworking 07:57:31.020 --> 07:57:34.670 align:start position:0% now in tcpipnetworking ARP<07:57:31.740> operates<07:57:32.458> at<07:57:32.638> the<07:57:32.878> lowest<07:57:33.180> layer<07:57:33.680> the 07:57:34.670 --> 07:57:34.680 align:start position:0% ARP operates at the lowest layer the 07:57:34.680 --> 07:57:37.968 align:start position:0% ARP operates at the lowest layer the network<07:57:34.860> interface<07:57:35.520> layer<07:57:36.360> in<07:57:36.898> total<07:57:37.200> whereas 07:57:37.968 --> 07:57:37.978 align:start position:0% network interface layer in total whereas 07:57:37.978 --> 07:57:40.368 align:start position:0% network interface layer in total whereas in<07:57:38.160> the<07:57:38.280> OSI<07:57:38.760> model<07:57:39.058> we<07:57:39.600> say<07:57:39.780> that<07:57:40.020> it<07:57:40.138> actually 07:57:40.368 --> 07:57:40.378 align:start position:0% in the OSI model we say that it actually 07:57:40.378 --> 07:57:43.010 align:start position:0% in the OSI model we say that it actually operates<07:57:40.920> between 07:57:43.010 --> 07:57:43.020 align:start position:0% operates between 07:57:43.020 --> 07:57:45.650 align:start position:0% operates between the<07:57:43.558> data<07:57:44.100> link<07:57:44.218> layer 07:57:45.650 --> 07:57:45.660 align:start position:0% the data link layer 07:57:45.660 --> 07:57:50.330 align:start position:0% the data link layer and<07:57:46.020> the<07:57:46.138> physical<07:57:46.260> layer 07:57:50.330 --> 07:57:50.340 align:start position:0% 07:57:50.340 --> 07:57:52.310 align:start position:0% and<07:57:50.700> this<07:57:50.820> is<07:57:50.940> because<07:57:51.120> it<07:57:51.420> wasn't<07:57:51.600> designed 07:57:52.310 --> 07:57:52.320 align:start position:0% and this is because it wasn't designed 07:57:52.320 --> 07:57:55.190 align:start position:0% and this is because it wasn't designed specifically<07:57:53.218> for<07:57:53.820> the<07:57:54.000> OSI<07:57:54.360> model<07:57:54.660> it<07:57:54.958> was 07:57:55.190 --> 07:57:55.200 align:start position:0% specifically for the OSI model it was 07:57:55.200 --> 07:57:58.850 align:start position:0% specifically for the OSI model it was designed<07:57:55.680> for<07:57:56.218> the<07:57:56.458> tcpip<07:57:57.120> model<07:57:57.478> now<07:57:58.260> ARP<07:57:58.740> and 07:57:58.850 --> 07:57:58.860 align:start position:0% designed for the tcpip model now ARP and 07:57:58.860 --> 07:58:01.368 align:start position:0% designed for the tcpip model now ARP and rarp<07:57:59.280> play<07:57:59.638> very<07:58:00.180> important<07:58:00.600> roles<07:58:00.958> in<07:58:01.200> the 07:58:01.368 --> 07:58:01.378 align:start position:0% rarp play very important roles in the 07:58:01.378 --> 07:58:04.070 align:start position:0% rarp play very important roles in the way<07:58:01.500> networks<07:58:02.100> operate<07:58:03.000> the<07:58:03.420> computer<07:58:03.540> wants 07:58:04.070 --> 07:58:04.080 align:start position:0% way networks operate the computer wants 07:58:04.080 --> 07:58:05.990 align:start position:0% way networks operate the computer wants to<07:58:04.260> communicate<07:58:04.740> with<07:58:05.218> any<07:58:05.580> other<07:58:05.760> computer 07:58:05.990 --> 07:58:06.000 align:start position:0% to communicate with any other computer 07:58:06.000 --> 07:58:08.510 align:start position:0% to communicate with any other computer within<07:58:06.540> the<07:58:06.660> local<07:58:06.780> area<07:58:07.020> network<07:58:07.378> the<07:58:08.340> MAC 07:58:08.510 --> 07:58:08.520 align:start position:0% within the local area network the MAC 07:58:08.520 --> 07:58:10.610 align:start position:0% within the local area network the MAC address<07:58:08.820> is<07:58:09.298> the<07:58:09.478> identifier<07:58:10.020> that's<07:58:10.320> used 07:58:10.610 --> 07:58:10.620 align:start position:0% address is the identifier that's used 07:58:10.620 --> 07:58:12.888 align:start position:0% address is the identifier that's used and<07:58:11.280> if<07:58:11.458> that<07:58:11.700> device<07:58:11.820> wishes<07:58:12.360> to<07:58:12.478> communicate 07:58:12.888 --> 07:58:12.898 align:start position:0% and if that device wishes to communicate 07:58:12.898 --> 07:58:15.468 align:start position:0% and if that device wishes to communicate outside<07:58:13.500> of<07:58:13.860> the<07:58:13.978> local<07:58:14.100> area<07:58:14.340> network<07:58:14.700> the 07:58:15.468 --> 07:58:15.478 align:start position:0% outside of the local area network the 07:58:15.478 --> 07:58:17.628 align:start position:0% outside of the local area network the destination<07:58:15.958> Mac<07:58:16.320> address<07:58:16.558> is<07:58:17.280> going<07:58:17.398> to<07:58:17.520> be 07:58:17.628 --> 07:58:17.638 align:start position:0% destination Mac address is going to be 07:58:17.638 --> 07:58:20.810 align:start position:0% destination Mac address is going to be that<07:58:17.878> of<07:58:18.360> the<07:58:18.600> router<07:58:19.020> so<07:58:19.680> the<07:58:19.978> our<07:58:20.340> process 07:58:20.810 --> 07:58:20.820 align:start position:0% that of the router so the our process 07:58:20.820 --> 07:58:23.288 align:start position:0% that of the router so the our process works<07:58:21.478> by<07:58:22.200> first 07:58:23.288 --> 07:58:23.298 align:start position:0% works by first 07:58:23.298 --> 07:58:29.150 align:start position:0% works by first receiving<07:58:24.298> the<07:58:24.958> IP<07:58:25.320> address<07:58:25.878> from<07:58:26.878> IP<07:58:27.860> or<07:58:28.860> the 07:58:29.150 --> 07:58:29.160 align:start position:0% receiving the IP address from IP or the 07:58:29.160 --> 07:58:30.350 align:start position:0% receiving the IP address from IP or the Internet<07:58:29.280> Protocol 07:58:30.350 --> 07:58:30.360 align:start position:0% Internet Protocol 07:58:30.360 --> 07:58:34.250 align:start position:0% Internet Protocol then<07:58:31.320> ARP<07:58:31.978> has<07:58:32.160> the<07:58:32.398> MAC<07:58:32.580> address<07:58:32.820> in<07:58:33.780> its 07:58:34.250 --> 07:58:34.260 align:start position:0% then ARP has the MAC address in its 07:58:34.260 --> 07:58:37.250 align:start position:0% then ARP has the MAC address in its cached<07:58:34.740> table<07:58:35.040> so<07:58:35.760> the<07:58:36.000> router<07:58:36.420> has<07:58:36.898> what<07:58:37.138> are 07:58:37.250 --> 07:58:37.260 align:start position:0% cached table so the router has what are 07:58:37.260 --> 07:58:38.930 align:start position:0% cached table so the router has what are called<07:58:37.440> ARP<07:58:37.920> tables 07:58:38.930 --> 07:58:38.940 align:start position:0% called ARP tables 07:58:38.940 --> 07:58:42.468 align:start position:0% called ARP tables that<07:58:39.660> link<07:58:39.898> IP<07:58:40.440> addresses<07:58:40.978> to<07:58:41.700> Mac<07:58:41.940> addresses 07:58:42.468 --> 07:58:42.478 align:start position:0% that link IP addresses to Mac addresses 07:58:42.478 --> 07:58:45.530 align:start position:0% that link IP addresses to Mac addresses we<07:58:43.020> call<07:58:43.260> this<07:58:43.440> the<07:58:43.680> ARP<07:58:43.978> table 07:58:45.530 --> 07:58:45.540 align:start position:0% we call this the ARP table 07:58:45.540 --> 07:58:48.170 align:start position:0% we call this the ARP table so<07:58:45.958> it<07:58:46.020> looks<07:58:46.378> in<07:58:46.500> there<07:58:46.680> to<07:58:47.100> see<07:58:47.280> if<07:58:47.458> it<07:58:47.638> no<07:58:47.820> if 07:58:48.170 --> 07:58:48.180 align:start position:0% so it looks in there to see if it no if 07:58:48.180 --> 07:58:50.330 align:start position:0% so it looks in there to see if it no if it<07:58:48.360> has<07:58:48.600> a<07:58:48.958> MAC<07:58:49.080> address<07:58:49.260> for<07:58:49.620> the<07:58:49.798> IP<07:58:50.100> address 07:58:50.330 --> 07:58:50.340 align:start position:0% it has a MAC address for the IP address 07:58:50.340 --> 07:58:52.250 align:start position:0% it has a MAC address for the IP address listed 07:58:52.250 --> 07:58:52.260 align:start position:0% listed 07:58:52.260 --> 07:58:57.230 align:start position:0% listed it<07:58:52.740> then<07:58:52.920> sends<07:58:53.458> it<07:58:53.580> back<07:58:53.878> to<07:58:54.120> the<07:58:54.298> IP<07:58:54.860> if<07:58:55.860> it<07:58:56.638> if 07:58:57.230 --> 07:58:57.240 align:start position:0% it then sends it back to the IP if it if 07:58:57.240 --> 07:59:00.110 align:start position:0% it then sends it back to the IP if it if it<07:58:57.478> does<07:58:57.660> have<07:58:57.958> it<07:58:58.138> and<07:58:59.040> if<07:58:59.280> it<07:58:59.458> doesn't<07:58:59.700> have 07:59:00.110 --> 07:59:00.120 align:start position:0% it does have it and if it doesn't have 07:59:00.120 --> 07:59:03.350 align:start position:0% it does have it and if it doesn't have it<07:59:00.298> it<07:59:01.040> broadcasts<07:59:02.040> the<07:59:02.340> message<07:59:02.580> it's<07:59:03.058> sent 07:59:03.350 --> 07:59:03.360 align:start position:0% it it broadcasts the message it's sent 07:59:03.360 --> 07:59:06.948 align:start position:0% it it broadcasts the message it's sent in<07:59:04.200> order<07:59:04.320> to<07:59:04.740> resolve<07:59:05.520> what<07:59:05.760> we<07:59:05.820> call<07:59:06.000> resolve 07:59:06.948 --> 07:59:06.958 align:start position:0% in order to resolve what we call resolve 07:59:06.958 --> 07:59:08.510 align:start position:0% in order to resolve what we call resolve the<07:59:07.260> address 07:59:08.510 --> 07:59:08.520 align:start position:0% the address 07:59:08.520 --> 07:59:10.610 align:start position:0% the address to<07:59:09.000> a<07:59:09.240> MAC<07:59:09.420> address 07:59:10.610 --> 07:59:10.620 align:start position:0% to a MAC address 07:59:10.620 --> 07:59:12.708 align:start position:0% to a MAC address and<07:59:11.100> the<07:59:11.280> target<07:59:11.398> computer<07:59:11.760> with<07:59:12.240> the<07:59:12.420> IP 07:59:12.708 --> 07:59:12.718 align:start position:0% and the target computer with the IP 07:59:12.718 --> 07:59:15.410 align:start position:0% and the target computer with the IP address<07:59:12.978> responds<07:59:13.978> to<07:59:14.638> that<07:59:14.940> broadcast 07:59:15.410 --> 07:59:15.420 align:start position:0% address responds to that broadcast 07:59:15.420 --> 07:59:18.288 align:start position:0% address responds to that broadcast message<07:59:16.138> with<07:59:16.798> what's<07:59:17.040> called<07:59:17.340> a<07:59:17.760> unicast 07:59:18.288 --> 07:59:18.298 align:start position:0% message with what's called a unicast 07:59:18.298 --> 07:59:20.208 align:start position:0% message with what's called a unicast message<07:59:18.600> and<07:59:18.840> we've<07:59:19.080> discussed<07:59:19.440> that<07:59:19.620> that 07:59:20.208 --> 07:59:20.218 align:start position:0% message and we've discussed that that 07:59:20.218 --> 07:59:22.010 align:start position:0% message and we've discussed that that contains<07:59:20.940> the<07:59:21.120> MAC<07:59:21.298> address<07:59:21.478> that<07:59:21.898> it's 07:59:22.010 --> 07:59:22.020 align:start position:0% contains the MAC address that it's 07:59:22.020 --> 07:59:23.030 align:start position:0% contains the MAC address that it's seeking 07:59:23.030 --> 07:59:23.040 align:start position:0% seeking 07:59:23.040 --> 07:59:26.510 align:start position:0% seeking ARP<07:59:23.638> then<07:59:23.820> will<07:59:24.180> add<07:59:24.600> the<07:59:24.840> MAC<07:59:24.958> address<07:59:25.260> to<07:59:26.160> its 07:59:26.510 --> 07:59:26.520 align:start position:0% ARP then will add the MAC address to its 07:59:26.520 --> 07:59:28.670 align:start position:0% ARP then will add the MAC address to its table<07:59:26.638> so<07:59:27.420> the<07:59:27.600> next<07:59:27.718> time<07:59:27.958> we<07:59:28.200> don't<07:59:28.320> have<07:59:28.500> to 07:59:28.670 --> 07:59:28.680 align:start position:0% table so the next time we don't have to 07:59:28.680 --> 07:59:32.208 align:start position:0% table so the next time we don't have to go<07:59:28.920> through<07:59:29.218> this<07:59:29.520> whole<07:59:29.700> process 07:59:32.208 --> 07:59:32.218 align:start position:0% 07:59:32.218 --> 07:59:36.350 align:start position:0% and<07:59:32.700> then<07:59:32.878> it<07:59:33.180> Returns<07:59:33.840> the<07:59:34.320> IP<07:59:34.740> address<07:59:35.360> to 07:59:36.350 --> 07:59:36.360 align:start position:0% and then it Returns the IP address to 07:59:36.360 --> 07:59:39.230 align:start position:0% and then it Returns the IP address to the<07:59:37.260> requesting<07:59:37.680> device<07:59:37.920> as<07:59:38.760> it<07:59:38.940> would<07:59:39.058> have 07:59:39.230 --> 07:59:39.240 align:start position:0% the requesting device as it would have 07:59:39.240 --> 07:59:41.150 align:start position:0% the requesting device as it would have if<07:59:39.478> it<07:59:39.600> just<07:59:39.780> had<07:59:40.020> it 07:59:41.150 --> 07:59:41.160 align:start position:0% if it just had it 07:59:41.160 --> 07:59:45.830 align:start position:0% if it just had it now<07:59:41.878> RP<07:59:42.540> is<07:59:43.138> used<07:59:43.320> to<07:59:43.558> do<07:59:43.740> the<07:59:44.520> opposite<07:59:44.940> that 07:59:45.830 --> 07:59:45.840 align:start position:0% now RP is used to do the opposite that 07:59:45.840 --> 07:59:48.230 align:start position:0% now RP is used to do the opposite that is<07:59:46.020> to<07:59:46.440> map<07:59:46.680> Mac<07:59:47.100> addresses<07:59:47.580> of<07:59:47.820> a<07:59:47.940> given 07:59:48.230 --> 07:59:48.240 align:start position:0% is to map Mac addresses of a given 07:59:48.240 --> 07:59:50.570 align:start position:0% is to map Mac addresses of a given system<07:59:48.420> to<07:59:48.958> their<07:59:49.200> assigned<07:59:49.680> IP<07:59:50.040> addresses 07:59:50.570 --> 07:59:50.580 align:start position:0% system to their assigned IP addresses 07:59:50.580 --> 07:59:52.730 align:start position:0% system to their assigned IP addresses and<07:59:51.120> it<07:59:51.240> sort<07:59:51.478> of<07:59:51.600> works<07:59:51.840> in<07:59:52.020> Reverse<07:59:52.378> from<07:59:52.558> all 07:59:52.730 --> 07:59:52.740 align:start position:0% and it sort of works in Reverse from all 07:59:52.740 --> 07:59:55.070 align:start position:0% and it sort of works in Reverse from all this<07:59:52.978> now<07:59:53.580> that's<07:59:53.760> a<07:59:54.000> very<07:59:54.120> general<07:59:54.478> overview 07:59:55.070 --> 07:59:55.080 align:start position:0% this now that's a very general overview 07:59:55.080 --> 07:59:56.810 align:start position:0% this now that's a very general overview of<07:59:55.260> ARP<07:59:55.620> and<07:59:55.680> rarp<07:59:56.040> and<07:59:56.160> if<07:59:56.280> you<07:59:56.398> were<07:59:56.520> to<07:59:56.638> go 07:59:56.810 --> 07:59:56.820 align:start position:0% of ARP and rarp and if you were to go 07:59:56.820 --> 07:59:58.670 align:start position:0% of ARP and rarp and if you were to go into<07:59:57.000> Cisco<07:59:57.540> certifications<07:59:58.080> for<07:59:58.440> instance 07:59:58.670 --> 07:59:58.680 align:start position:0% into Cisco certifications for instance 07:59:58.680 --> 08:00:00.830 align:start position:0% into Cisco certifications for instance you<07:59:59.040> go<07:59:59.580> a<07:59:59.760> little<07:59:59.878> more<08:00:00.000> in<08:00:00.240> depth<08:00:00.478> into<08:00:00.600> this 08:00:00.830 --> 08:00:00.840 align:start position:0% you go a little more in depth into this 08:00:00.840 --> 08:00:02.448 align:start position:0% you go a little more in depth into this but<08:00:01.080> for<08:00:01.260> Network<08:00:01.378> plus<08:00:01.680> this<08:00:02.100> is<08:00:02.218> really 08:00:02.448 --> 08:00:02.458 align:start position:0% but for Network plus this is really 08:00:02.458 --> 08:00:04.730 align:start position:0% but for Network plus this is really where<08:00:02.760> we<08:00:03.000> need<08:00:03.120> to<08:00:03.360> stop<08:00:03.660> with<08:00:04.200> this<08:00:04.378> protocol 08:00:04.730 --> 08:00:04.740 align:start position:0% where we need to stop with this protocol 08:00:04.740 --> 08:00:06.530 align:start position:0% where we need to stop with this protocol so<08:00:05.458> the<08:00:05.580> next<08:00:05.700> protocol<08:00:06.058> I<08:00:06.240> want<08:00:06.360> to<08:00:06.478> talk 08:00:06.530 --> 08:00:06.540 align:start position:0% so the next protocol I want to talk 08:00:06.540 --> 08:00:11.570 align:start position:0% so the next protocol I want to talk about<08:00:06.660> is<08:00:07.040> icmp<08:00:08.040> which<08:00:08.940> is<08:00:09.058> also<08:00:09.420> called<08:00:09.718> the 08:00:11.570 --> 08:00:11.580 align:start position:0% about is icmp which is also called the 08:00:11.580 --> 08:00:17.150 align:start position:0% about is icmp which is also called the internet 08:00:17.150 --> 08:00:17.160 align:start position:0% 08:00:17.160 --> 08:00:21.048 align:start position:0% control 08:00:21.048 --> 08:00:21.058 align:start position:0% 08:00:21.058 --> 08:00:23.570 align:start position:0% message<08:00:22.040> protocol 08:00:23.570 --> 08:00:23.580 align:start position:0% message protocol 08:00:23.580 --> 08:00:26.208 align:start position:0% message protocol it's<08:00:24.000> a<08:00:24.180> protocol<08:00:24.420> designed<08:00:25.080> to<08:00:25.920> send 08:00:26.208 --> 08:00:26.218 align:start position:0% it's a protocol designed to send 08:00:26.218 --> 08:00:28.670 align:start position:0% it's a protocol designed to send messages<08:00:26.760> that<08:00:27.298> relate<08:00:27.540> to<08:00:27.718> the<08:00:27.958> status<08:00:28.200> of<08:00:28.500> a 08:00:28.670 --> 08:00:28.680 align:start position:0% messages that relate to the status of a 08:00:28.680 --> 08:00:31.010 align:start position:0% messages that relate to the status of a system<08:00:28.860> it's<08:00:29.580> not<08:00:29.760> meant<08:00:30.120> to<08:00:30.240> actually<08:00:30.478> send 08:00:31.010 --> 08:00:31.020 align:start position:0% system it's not meant to actually send 08:00:31.020 --> 08:00:35.330 align:start position:0% system it's not meant to actually send data<08:00:32.280> so<08:00:32.580> icmp<08:00:33.360> messages<08:00:33.600> are<08:00:34.080> used<08:00:34.340> generally 08:00:35.330 --> 08:00:35.340 align:start position:0% data so icmp messages are used generally 08:00:35.340 --> 08:00:37.490 align:start position:0% data so icmp messages are used generally speaking<08:00:35.878> for<08:00:36.180> Diagnostic<08:00:36.898> and<08:00:37.080> testing 08:00:37.490 --> 08:00:37.500 align:start position:0% speaking for Diagnostic and testing 08:00:37.500 --> 08:00:39.948 align:start position:0% speaking for Diagnostic and testing purposes<08:00:37.920> and<08:00:38.580> they<08:00:38.760> can<08:00:38.878> also<08:00:39.120> be<08:00:39.180> used<08:00:39.420> as<08:00:39.718> a 08:00:39.948 --> 08:00:39.958 align:start position:0% purposes and they can also be used as a 08:00:39.958 --> 08:00:42.468 align:start position:0% purposes and they can also be used as a response<08:00:40.440> to<08:00:40.680> errors<08:00:41.100> that<08:00:41.340> occur<08:00:41.760> in<08:00:42.360> the 08:00:42.468 --> 08:00:42.478 align:start position:0% response to errors that occur in the 08:00:42.478 --> 08:00:44.750 align:start position:0% response to errors that occur in the normal<08:00:42.660> operations<08:00:43.200> of<08:00:43.500> Ip<08:00:43.920> and<08:00:44.520> if<08:00:44.638> you 08:00:44.750 --> 08:00:44.760 align:start position:0% normal operations of Ip and if you 08:00:44.760 --> 08:00:46.610 align:start position:0% normal operations of Ip and if you recall<08:00:45.120> one<08:00:45.478> of<08:00:45.600> the<08:00:45.660> times<08:00:45.958> that<08:00:46.200> we<08:00:46.320> talked 08:00:46.610 --> 08:00:46.620 align:start position:0% recall one of the times that we talked 08:00:46.620 --> 08:00:50.090 align:start position:0% recall one of the times that we talked about<08:00:46.740> that<08:00:47.040> was<08:00:47.700> for<08:00:48.000> instance<08:00:48.240> with<08:00:49.080> the<08:00:49.558> MTU 08:00:50.090 --> 08:00:50.100 align:start position:0% about that was for instance with the MTU 08:00:50.100 --> 08:00:51.650 align:start position:0% about that was for instance with the MTU black<08:00:50.398> hole 08:00:51.650 --> 08:00:51.660 align:start position:0% black hole 08:00:51.660 --> 08:00:55.010 align:start position:0% black hole when<08:00:52.378> that<08:00:52.620> icmp<08:00:53.398> message<08:00:53.700> couldn't<08:00:54.360> get<08:00:54.718> back 08:00:55.010 --> 08:00:55.020 align:start position:0% when that icmp message couldn't get back 08:00:55.020 --> 08:00:58.490 align:start position:0% when that icmp message couldn't get back to<08:00:55.860> the<08:00:56.218> original<08:00:56.458> router<08:00:57.120> now<08:00:57.958> many<08:00:58.200> Internet 08:00:58.490 --> 08:00:58.500 align:start position:0% to the original router now many Internet 08:00:58.500 --> 08:01:01.010 align:start position:0% to the original router now many Internet Protocol<08:00:59.040> utilities<08:00:59.760> are<08:01:00.120> actually<08:01:00.298> derived 08:01:01.010 --> 08:01:01.020 align:start position:0% Protocol utilities are actually derived 08:01:01.020 --> 08:01:05.270 align:start position:0% Protocol utilities are actually derived from<08:01:01.260> icmp<08:01:02.100> messages<08:01:02.540> such<08:01:03.540> as<08:01:03.860> Tracer<08:01:04.860> or 08:01:05.270 --> 08:01:05.280 align:start position:0% from icmp messages such as Tracer or 08:01:05.280 --> 08:01:06.410 align:start position:0% from icmp messages such as Tracer or trace<08:01:05.580> route 08:01:06.410 --> 08:01:06.420 align:start position:0% trace route 08:01:06.420 --> 08:01:09.530 align:start position:0% trace route path<08:01:06.840> ping<08:01:07.260> and<08:01:07.978> ping<08:01:08.340> and<08:01:09.000> we'll<08:01:09.180> talk<08:01:09.420> about 08:01:09.530 --> 08:01:09.540 align:start position:0% path ping and ping and we'll talk about 08:01:09.540 --> 08:01:11.208 align:start position:0% path ping and ping and we'll talk about these<08:01:09.898> in<08:01:10.020> a<08:01:10.200> little<08:01:10.260> more<08:01:10.378> depth<08:01:10.740> than<08:01:10.920> if<08:01:11.100> you 08:01:11.208 --> 08:01:11.218 align:start position:0% these in a little more depth than if you 08:01:11.218 --> 08:01:13.910 align:start position:0% these in a little more depth than if you were<08:01:11.340> around<08:01:11.520> for<08:01:11.820> uh<08:01:12.600> a<08:01:12.840> plus<08:01:13.020> we<08:01:13.558> definitely 08:01:13.910 --> 08:01:13.920 align:start position:0% were around for uh a plus we definitely 08:01:13.920 --> 08:01:17.330 align:start position:0% were around for uh a plus we definitely talked<08:01:14.398> about<08:01:14.580> these<08:01:15.120> two<08:01:15.298> quite<08:01:15.958> a<08:01:16.138> bit<08:01:16.340> icmp 08:01:17.330 --> 08:01:17.340 align:start position:0% talked about these two quite a bit icmp 08:01:17.340 --> 08:01:19.850 align:start position:0% talked about these two quite a bit icmp is<08:01:17.520> actually<08:01:17.760> one<08:01:18.058> of<08:01:18.120> the<08:01:18.298> core<08:01:18.600> Protocols<08:01:19.378> of 08:01:19.850 --> 08:01:19.860 align:start position:0% is actually one of the core Protocols of 08:01:19.860 --> 08:01:22.850 align:start position:0% is actually one of the core Protocols of the<08:01:20.160> IP<08:01:20.520> suite<08:01:21.058> and<08:01:21.540> it<08:01:21.718> operates<08:01:22.200> at<08:01:22.680> the 08:01:22.850 --> 08:01:22.860 align:start position:0% the IP suite and it operates at the 08:01:22.860 --> 08:01:25.510 align:start position:0% the IP suite and it operates at the internet<08:01:23.040> layer<08:01:23.638> which<08:01:23.940> as<08:01:24.058> you<08:01:24.240> recall<08:01:24.600> is 08:01:25.510 --> 08:01:25.520 align:start position:0% internet layer which as you recall is 08:01:25.520 --> 08:01:27.850 align:start position:0% internet layer which as you recall is tcpip 08:01:27.850 --> 08:01:27.860 align:start position:0% tcpip 08:01:27.860 --> 08:01:30.468 align:start position:0% tcpip second<08:01:28.860> layer 08:01:30.468 --> 08:01:30.478 align:start position:0% second layer 08:01:30.478 --> 08:01:34.430 align:start position:0% second layer now<08:01:31.080> icmp<08:01:31.920> is<08:01:32.218> a<08:01:32.520> control<08:01:32.878> protocol<08:01:33.600> used<08:01:34.080> by 08:01:34.430 --> 08:01:34.440 align:start position:0% now icmp is a control protocol used by 08:01:34.440 --> 08:01:36.468 align:start position:0% now icmp is a control protocol used by networked<08:01:35.040> computers<08:01:35.520> and<08:01:36.120> operating 08:01:36.468 --> 08:01:36.478 align:start position:0% networked computers and operating 08:01:36.478 --> 08:01:39.708 align:start position:0% networked computers and operating systems<08:01:37.080> and<08:01:37.680> the<08:01:37.920> most<08:01:38.040> common<08:01:38.398> utility<08:01:38.940> that 08:01:39.708 --> 08:01:39.718 align:start position:0% systems and the most common utility that 08:01:39.718 --> 08:01:42.288 align:start position:0% systems and the most common utility that we're<08:01:39.840> going<08:01:39.958> to<08:01:40.080> see<08:01:40.260> is<08:01:40.860> what's<08:01:41.100> called 08:01:42.288 --> 08:01:42.298 align:start position:0% we're going to see is what's called 08:01:42.298 --> 08:01:44.690 align:start position:0% we're going to see is what's called ping<08:01:42.840> which<08:01:43.260> we've<08:01:43.558> talked<08:01:43.798> about<08:01:43.920> which<08:01:44.398> uses 08:01:44.690 --> 08:01:44.700 align:start position:0% ping which we've talked about which uses 08:01:44.700 --> 08:01:48.110 align:start position:0% ping which we've talked about which uses what<08:01:44.878> are<08:01:45.000> called<08:01:45.120> icmp<08:01:46.020> Echo<08:01:46.920> requests<08:01:47.580> and 08:01:48.110 --> 08:01:48.120 align:start position:0% what are called icmp Echo requests and 08:01:48.120 --> 08:01:50.270 align:start position:0% what are called icmp Echo requests and they<08:01:48.298> reply<08:01:48.780> to<08:01:49.500> determine<08:01:49.978> connection 08:01:50.270 --> 08:01:50.280 align:start position:0% they reply to determine connection 08:01:50.280 --> 08:01:53.628 align:start position:0% they reply to determine connection statuses<08:01:51.120> of<08:01:51.540> a<08:01:51.958> Target<08:01:52.138> system<08:01:52.558> so<08:01:53.340> I<08:01:53.520> could 08:01:53.628 --> 08:01:53.638 align:start position:0% statuses of a Target system so I could 08:01:53.638 --> 08:01:56.330 align:start position:0% statuses of a Target system so I could ping<08:01:54.058> a<08:01:54.360> specific<08:01:54.660> system<08:01:54.958> to<08:01:55.320> see<08:01:55.500> if<08:01:55.978> it's<08:01:56.100> on 08:01:56.330 --> 08:01:56.340 align:start position:0% ping a specific system to see if it's on 08:01:56.340 --> 08:01:58.128 align:start position:0% ping a specific system to see if it's on the<08:01:56.458> network<08:01:56.638> of<08:01:57.360> course<08:01:57.540> there<08:01:57.840> are<08:01:57.958> some 08:01:58.128 --> 08:01:58.138 align:start position:0% the network of course there are some 08:01:58.138 --> 08:02:00.170 align:start position:0% the network of course there are some reasons<08:01:58.378> why<08:01:58.558> the<08:01:58.740> icmp<08:01:59.340> as<08:01:59.580> we've<08:01:59.820> talked 08:02:00.170 --> 08:02:00.180 align:start position:0% reasons why the icmp as we've talked 08:02:00.180 --> 08:02:02.270 align:start position:0% reasons why the icmp as we've talked about<08:02:00.240> might<08:02:00.540> not<08:02:00.718> make<08:02:00.898> it<08:02:01.020> back<08:02:01.200> to<08:02:01.378> me<08:02:01.500> or 08:02:02.270 --> 08:02:02.280 align:start position:0% about might not make it back to me or 08:02:02.280 --> 08:02:04.368 align:start position:0% about might not make it back to me or it's<08:02:02.458> configured<08:02:03.000> not<08:02:03.298> to<08:02:03.478> respond<08:02:03.840> perhaps 08:02:04.368 --> 08:02:04.378 align:start position:0% it's configured not to respond perhaps 08:02:04.378 --> 08:02:06.708 align:start position:0% it's configured not to respond perhaps through<08:02:04.620> a<08:02:04.798> firewall<08:02:05.218> finally<08:02:06.058> we<08:02:06.360> need<08:02:06.540> to 08:02:06.708 --> 08:02:06.718 align:start position:0% through a firewall finally we need to 08:02:06.718 --> 08:02:14.510 align:start position:0% through a firewall finally we need to talk<08:02:06.840> about<08:02:07.398> igmp<08:02:08.398> or<08:02:09.240> the<08:02:09.600> internet 08:02:14.510 --> 08:02:14.520 align:start position:0% 08:02:14.520 --> 08:02:17.330 align:start position:0% group 08:02:17.330 --> 08:02:17.340 align:start position:0% group 08:02:17.340 --> 08:02:20.690 align:start position:0% group management<08:02:18.058> protocol 08:02:20.690 --> 08:02:20.700 align:start position:0% management protocol 08:02:20.700 --> 08:02:23.690 align:start position:0% management protocol it<08:02:21.240> should<08:02:21.420> not<08:02:21.600> be<08:02:21.780> confused<08:02:22.260> with<08:02:22.558> icmp<08:02:23.458> it's 08:02:23.690 --> 08:02:23.700 align:start position:0% it should not be confused with icmp it's 08:02:23.700 --> 08:02:25.010 align:start position:0% it should not be confused with icmp it's slightly<08:02:24.058> different 08:02:25.010 --> 08:02:25.020 align:start position:0% slightly different 08:02:25.020 --> 08:02:28.610 align:start position:0% slightly different it<08:02:25.558> is<08:02:25.680> used<08:02:25.978> to<08:02:26.398> establish<08:02:26.940> memberships<08:02:27.780> for 08:02:28.610 --> 08:02:28.620 align:start position:0% it is used to establish memberships for 08:02:28.620 --> 08:02:31.610 align:start position:0% it is used to establish memberships for multicast<08:02:29.218> groups<08:02:29.820> now<08:02:30.478> multicasting<08:02:31.320> is 08:02:31.610 --> 08:02:31.620 align:start position:0% multicast groups now multicasting is 08:02:31.620 --> 08:02:34.070 align:start position:0% multicast groups now multicasting is where<08:02:31.860> a<08:02:31.978> computer<08:02:32.160> wishes<08:02:32.820> to<08:02:33.120> send<08:02:33.360> data<08:02:33.780> to 08:02:34.070 --> 08:02:34.080 align:start position:0% where a computer wishes to send data to 08:02:34.080 --> 08:02:36.410 align:start position:0% where a computer wishes to send data to a<08:02:34.260> lot<08:02:34.378> of<08:02:34.500> other<08:02:34.680> computers<08:02:35.340> through<08:02:36.120> the 08:02:36.410 --> 08:02:36.420 align:start position:0% a lot of other computers through the 08:02:36.420 --> 08:02:38.690 align:start position:0% a lot of other computers through the internet<08:02:36.600> by<08:02:37.500> identifying<08:02:37.978> which<08:02:38.218> computers 08:02:38.690 --> 08:02:38.700 align:start position:0% internet by identifying which computers 08:02:38.700 --> 08:02:41.868 align:start position:0% internet by identifying which computers have<08:02:39.080> subscribed<08:02:40.080> or<08:02:40.798> which<08:02:41.040> ones<08:02:41.340> wish<08:02:41.638> to 08:02:41.868 --> 08:02:41.878 align:start position:0% have subscribed or which ones wish to 08:02:41.878 --> 08:02:44.150 align:start position:0% have subscribed or which ones wish to receive<08:02:42.240> the<08:02:42.478> data<08:02:42.958> we<08:02:43.620> looked<08:02:43.920> at<08:02:43.978> this 08:02:44.150 --> 08:02:44.160 align:start position:0% receive the data we looked at this 08:02:44.160 --> 08:02:45.830 align:start position:0% receive the data we looked at this earlier<08:02:44.458> and<08:02:44.638> determined<08:02:45.058> that<08:02:45.240> routers 08:02:45.830 --> 08:02:45.840 align:start position:0% earlier and determined that routers 08:02:45.840 --> 08:02:48.948 align:start position:0% earlier and determined that routers determine<08:02:46.378> a<08:02:46.740> multicast<08:02:47.160> group<08:02:47.580> now<08:02:48.360> in<08:02:48.718> a 08:02:48.948 --> 08:02:48.958 align:start position:0% determine a multicast group now in a 08:02:48.958 --> 08:02:52.070 align:start position:0% determine a multicast group now in a host<08:02:49.200> implementation<08:02:50.120> a<08:02:51.120> host<08:02:51.360> is<08:02:51.718> going<08:02:51.898> to 08:02:52.070 --> 08:02:52.080 align:start position:0% host implementation a host is going to 08:02:52.080 --> 08:02:54.830 align:start position:0% host implementation a host is going to make<08:02:52.320> a<08:02:52.500> request<08:02:52.860> for 08:02:54.830 --> 08:02:54.840 align:start position:0% make a request for 08:02:54.840 --> 08:02:59.090 align:start position:0% make a request for and<08:02:55.558> igmp<08:02:56.660> implemented<08:02:57.660> router<08:02:58.138> to<08:02:58.680> join<08:02:58.978> the 08:02:59.090 --> 08:02:59.100 align:start position:0% and igmp implemented router to join the 08:02:59.100 --> 08:03:02.388 align:start position:0% and igmp implemented router to join the membership<08:02:59.458> of<08:02:59.878> a<08:03:00.180> multicast<08:03:00.600> group 08:03:02.388 --> 08:03:02.398 align:start position:0% membership of a multicast group 08:03:02.398 --> 08:03:05.270 align:start position:0% membership of a multicast group certain<08:03:02.820> applications<08:03:03.478> such<08:03:03.958> as<08:03:04.260> those<08:03:04.680> for 08:03:05.270 --> 08:03:05.280 align:start position:0% certain applications such as those for 08:03:05.280 --> 08:03:08.990 align:start position:0% certain applications such as those for online<08:03:05.638> gaming<08:03:06.478> can<08:03:07.200> use<08:03:07.378> igmp<08:03:08.340> for<08:03:08.638> what<08:03:08.820> are 08:03:08.990 --> 08:03:09.000 align:start position:0% online gaming can use igmp for what are 08:03:09.000 --> 08:03:09.910 align:start position:0% online gaming can use igmp for what are called 08:03:09.910 --> 08:03:09.920 align:start position:0% called 08:03:09.920 --> 08:03:13.548 align:start position:0% called one-to-many<08:03:10.920> Communications<08:03:11.718> the<08:03:12.718> one<08:03:12.958> being 08:03:13.548 --> 08:03:13.558 align:start position:0% one-to-many Communications the one being 08:03:13.558 --> 08:03:16.490 align:start position:0% one-to-many Communications the one being the<08:03:13.860> game<08:03:14.040> server<08:03:14.638> and<08:03:15.298> the<08:03:15.478> many<08:03:15.660> being<08:03:16.080> all 08:03:16.490 --> 08:03:16.500 align:start position:0% the game server and the many being all 08:03:16.500 --> 08:03:19.070 align:start position:0% the game server and the many being all of<08:03:16.620> those<08:03:16.978> end<08:03:17.340> users<08:03:17.760> that<08:03:18.000> have<08:03:18.240> subscribed 08:03:19.070 --> 08:03:19.080 align:start position:0% of those end users that have subscribed 08:03:19.080 --> 08:03:21.048 align:start position:0% of those end users that have subscribed to<08:03:19.620> the<08:03:19.798> gaming<08:03:20.160> session 08:03:21.048 --> 08:03:21.058 align:start position:0% to the gaming session 08:03:21.058 --> 08:03:23.448 align:start position:0% to the gaming session so<08:03:21.540> those<08:03:21.780> routers<08:03:22.320> with<08:03:22.620> igmp 08:03:23.448 --> 08:03:23.458 align:start position:0% so those routers with igmp 08:03:23.458 --> 08:03:26.090 align:start position:0% so those routers with igmp implementation<08:03:24.500> periodically<08:03:25.500> will<08:03:25.798> send 08:03:26.090 --> 08:03:26.100 align:start position:0% implementation periodically will send 08:03:26.100 --> 08:03:28.850 align:start position:0% implementation periodically will send out<08:03:26.520> queries<08:03:27.058> to<08:03:27.540> determine<08:03:27.958> the<08:03:28.378> multicast 08:03:28.850 --> 08:03:28.860 align:start position:0% out queries to determine the multicast 08:03:28.860 --> 08:03:32.810 align:start position:0% out queries to determine the multicast membership<08:03:29.458> of<08:03:30.298> those<08:03:30.540> devices<08:03:31.398> within<08:03:32.398> range 08:03:32.810 --> 08:03:32.820 align:start position:0% membership of those devices within range 08:03:32.820 --> 08:03:34.548 align:start position:0% membership of those devices within range and<08:03:33.540> then<08:03:33.600> those<08:03:33.780> hosts<08:03:34.138> that<08:03:34.320> have 08:03:34.548 --> 08:03:34.558 align:start position:0% and then those hosts that have 08:03:34.558 --> 08:03:36.350 align:start position:0% and then those hosts that have membership<08:03:34.920> are<08:03:35.218> going<08:03:35.398> to<08:03:35.580> respond<08:03:35.940> to<08:03:36.180> the 08:03:36.350 --> 08:03:36.360 align:start position:0% membership are going to respond to the 08:03:36.360 --> 08:03:39.110 align:start position:0% membership are going to respond to the queries<08:03:36.718> with<08:03:37.558> a<08:03:37.978> membership 08:03:39.110 --> 08:03:39.120 align:start position:0% queries with a membership 08:03:39.120 --> 08:03:42.110 align:start position:0% queries with a membership report 08:03:42.110 --> 08:03:42.120 align:start position:0% 08:03:42.120 --> 08:03:45.770 align:start position:0% now<08:03:42.780> the<08:03:43.260> process<08:03:43.558> of<08:03:43.920> delivering<08:03:44.520> an<08:03:45.360> IP 08:03:45.770 --> 08:03:45.780 align:start position:0% now the process of delivering an IP 08:03:45.780 --> 08:03:47.628 align:start position:0% now the process of delivering an IP packet<08:03:46.440> is<08:03:46.920> simple 08:03:47.628 --> 08:03:47.638 align:start position:0% packet is simple 08:03:47.638 --> 08:03:50.810 align:start position:0% packet is simple it<08:03:48.180> begins<08:03:48.478> with<08:03:48.780> resolving<08:03:49.620> the<08:03:50.040> name<08:03:50.218> of<08:03:50.580> the 08:03:50.810 --> 08:03:50.820 align:start position:0% it begins with resolving the name of the 08:03:50.820 --> 08:03:54.530 align:start position:0% it begins with resolving the name of the host<08:03:51.080> to<08:03:52.080> its<08:03:52.500> assigned<08:03:53.040> IP<08:03:53.398> address<08:03:53.638> like<08:03:54.360> we 08:03:54.530 --> 08:03:54.540 align:start position:0% host to its assigned IP address like we 08:03:54.540 --> 08:03:56.868 align:start position:0% host to its assigned IP address like we talked<08:03:54.780> about<08:03:54.840> with<08:03:55.138> arp<08:03:56.040> and<08:03:56.520> the<08:03:56.700> connection 08:03:56.868 --> 08:03:56.878 align:start position:0% talked about with arp and the connection 08:03:56.878 --> 08:04:00.048 align:start position:0% talked about with arp and the connection is<08:03:57.420> established<08:03:58.080> by<08:03:58.440> a<08:03:58.620> service<08:03:58.860> at<08:03:59.700> if<08:03:59.878> you 08:04:00.048 --> 08:04:00.058 align:start position:0% is established by a service at if you 08:04:00.058 --> 08:04:03.170 align:start position:0% is established by a service at if you recall<08:04:00.420> the<08:04:01.320> transport<08:04:01.798> layer 08:04:03.170 --> 08:04:03.180 align:start position:0% recall the transport layer 08:04:03.180 --> 08:04:05.628 align:start position:0% recall the transport layer now<08:04:03.660> after<08:04:04.080> the<08:04:04.500> name<08:04:04.680> resolution<08:04:05.160> and 08:04:05.628 --> 08:04:05.638 align:start position:0% now after the name resolution and 08:04:05.638 --> 08:04:08.510 align:start position:0% now after the name resolution and connection<08:04:05.940> establishment<08:04:06.920> the<08:04:07.920> IP<08:04:08.280> address 08:04:08.510 --> 08:04:08.520 align:start position:0% connection establishment the IP address 08:04:08.520 --> 08:04:12.230 align:start position:0% connection establishment the IP address is<08:04:09.058> then<08:04:09.240> sent<08:04:09.600> down<08:04:10.020> to<08:04:10.378> the<08:04:10.680> internet<08:04:10.860> layer 08:04:12.230 --> 08:04:12.240 align:start position:0% is then sent down to the internet layer 08:04:12.240 --> 08:04:15.110 align:start position:0% is then sent down to the internet layer and<08:04:12.840> the<08:04:13.020> next<08:04:13.200> step<08:04:13.378> is<08:04:13.920> where<08:04:14.100> the<08:04:14.340> IP<08:04:14.638> looks 08:04:15.110 --> 08:04:15.120 align:start position:0% and the next step is where the IP looks 08:04:15.120 --> 08:04:17.448 align:start position:0% and the next step is where the IP looks at<08:04:15.420> the<08:04:15.600> subnet<08:04:16.020> mask<08:04:16.320> which<08:04:17.100> we've<08:04:17.280> talked 08:04:17.448 --> 08:04:17.458 align:start position:0% at the subnet mask which we've talked 08:04:17.458 --> 08:04:18.650 align:start position:0% at the subnet mask which we've talked about<08:04:17.520> in<08:04:17.700> a<08:04:17.820> plus<08:04:18.000> and<08:04:18.180> we'll<08:04:18.298> talk<08:04:18.540> about 08:04:18.650 --> 08:04:18.660 align:start position:0% about in a plus and we'll talk about 08:04:18.660 --> 08:04:21.830 align:start position:0% about in a plus and we'll talk about more<08:04:19.200> of<08:04:19.860> the<08:04:19.978> IP<08:04:20.340> address<08:04:20.520> to<08:04:21.360> determine 08:04:21.830 --> 08:04:21.840 align:start position:0% more of the IP address to determine 08:04:21.840 --> 08:04:25.250 align:start position:0% more of the IP address to determine whether<08:04:22.500> the<08:04:22.740> destination<08:04:23.298> is<08:04:24.298> local<08:04:24.660> to<08:04:25.138> the 08:04:25.250 --> 08:04:25.260 align:start position:0% whether the destination is local to the 08:04:25.260 --> 08:04:27.708 align:start position:0% whether the destination is local to the computer<08:04:25.440> on<08:04:26.218> what<08:04:26.458> we<08:04:26.638> say<08:04:26.940> is<08:04:27.180> the<08:04:27.540> same 08:04:27.708 --> 08:04:27.718 align:start position:0% computer on what we say is the same 08:04:27.718 --> 08:04:31.968 align:start position:0% computer on what we say is the same subnet<08:04:28.700> or<08:04:29.700> whether<08:04:30.360> it's<08:04:30.780> remote<08:04:31.200> or<08:04:31.740> on 08:04:31.968 --> 08:04:31.978 align:start position:0% subnet or whether it's remote or on 08:04:31.978 --> 08:04:34.968 align:start position:0% subnet or whether it's remote or on another<08:04:32.218> Network<08:04:32.898> after<08:04:33.898> this<08:04:34.260> determination 08:04:34.968 --> 08:04:34.978 align:start position:0% another Network after this determination 08:04:34.978 --> 08:04:38.090 align:start position:0% another Network after this determination is<08:04:35.580> made<08:04:35.940> then<08:04:36.898> finally<08:04:37.260> the<08:04:37.500> packet<08:04:37.860> is 08:04:38.090 --> 08:04:38.100 align:start position:0% is made then finally the packet is 08:04:38.100 --> 08:04:40.610 align:start position:0% is made then finally the packet is routed<08:04:38.520> and<08:04:39.298> delivered 08:04:40.610 --> 08:04:40.620 align:start position:0% routed and delivered 08:04:40.620 --> 08:04:44.750 align:start position:0% routed and delivered okay<08:04:41.280> so<08:04:42.058> we<08:04:42.298> now<08:04:42.478> understand<08:04:43.100> TCP<08:04:44.100> a<08:04:44.638> little 08:04:44.750 --> 08:04:44.760 align:start position:0% okay so we now understand TCP a little 08:04:44.760 --> 08:04:47.270 align:start position:0% okay so we now understand TCP a little more<08:04:44.940> fully<08:04:45.240> some<08:04:46.080> of<08:04:46.200> the<08:04:46.320> protocols<08:04:46.920> that 08:04:47.270 --> 08:04:47.280 align:start position:0% more fully some of the protocols that 08:04:47.280 --> 08:04:51.830 align:start position:0% more fully some of the protocols that are<08:04:47.458> dealt<08:04:48.360> with<08:04:48.420> in<08:04:49.138> great<08:04:49.378> detail<08:04:49.940> and<08:04:50.940> how 08:04:51.830 --> 08:04:51.840 align:start position:0% are dealt with in great detail and how 08:04:51.840 --> 08:04:54.530 align:start position:0% are dealt with in great detail and how IP<08:04:52.200> packet<08:04:52.680> delivery<08:04:53.100> works<08:04:53.520> so<08:04:54.058> let's<08:04:54.298> talk 08:04:54.530 --> 08:04:54.540 align:start position:0% IP packet delivery works so let's talk 08:04:54.540 --> 08:04:56.990 align:start position:0% IP packet delivery works so let's talk about<08:04:54.780> binary<08:04:55.620> and<08:04:55.978> decimal<08:04:56.458> which<08:04:56.700> are<08:04:56.878> going 08:04:56.990 --> 08:04:57.000 align:start position:0% about binary and decimal which are going 08:04:57.000 --> 08:04:59.030 align:start position:0% about binary and decimal which are going to<08:04:57.180> be<08:04:57.298> really<08:04:57.958> important<08:04:58.378> when<08:04:58.620> we<08:04:58.740> get<08:04:58.920> into 08:04:59.030 --> 08:04:59.040 align:start position:0% to be really important when we get into 08:04:59.040 --> 08:05:01.368 align:start position:0% to be really important when we get into what's<08:04:59.340> called<08:04:59.638> subnetting<08:05:00.420> and<08:05:01.080> it's<08:05:01.200> just 08:05:01.368 --> 08:05:01.378 align:start position:0% what's called subnetting and it's just 08:05:01.378 --> 08:05:03.170 align:start position:0% what's called subnetting and it's just good<08:05:01.558> to<08:05:01.740> know<08:05:01.920> as<08:05:02.218> an<08:05:02.398> I.T<08:05:02.700> professional 08:05:03.170 --> 08:05:03.180 align:start position:0% good to know as an I.T professional 08:05:03.180 --> 08:05:04.310 align:start position:0% good to know as an I.T professional anyway 08:05:04.310 --> 08:05:04.320 align:start position:0% anyway 08:05:04.320 --> 08:05:06.250 align:start position:0% anyway specifically 08:05:06.250 --> 08:05:06.260 align:start position:0% specifically 08:05:06.260 --> 08:05:09.190 align:start position:0% specifically understanding<08:05:07.260> binary<08:05:07.860> or<08:05:08.280> how<08:05:08.520> to<08:05:08.638> convert 08:05:09.190 --> 08:05:09.200 align:start position:0% understanding binary or how to convert 08:05:09.200 --> 08:05:11.810 align:start position:0% understanding binary or how to convert binary<08:05:10.200> which<08:05:10.860> is<08:05:10.920> the<08:05:11.100> number<08:05:11.218> of<08:05:11.398> computers 08:05:11.810 --> 08:05:11.820 align:start position:0% binary which is the number of computers 08:05:11.820 --> 08:05:14.030 align:start position:0% binary which is the number of computers the<08:05:12.180> way<08:05:12.298> computers<08:05:12.780> talk<08:05:13.080> to<08:05:13.440> decimal<08:05:13.860> which 08:05:14.030 --> 08:05:14.040 align:start position:0% the way computers talk to decimal which 08:05:14.040 --> 08:05:16.310 align:start position:0% the way computers talk to decimal which is<08:05:14.160> the<08:05:14.280> way<08:05:14.340> that<08:05:14.520> we<08:05:14.760> deal<08:05:14.878> with<08:05:15.120> numbers<08:05:15.360> and 08:05:16.310 --> 08:05:16.320 align:start position:0% is the way that we deal with numbers and 08:05:16.320 --> 08:05:19.070 align:start position:0% is the way that we deal with numbers and decimal<08:05:16.860> to<08:05:17.160> binary 08:05:19.070 --> 08:05:19.080 align:start position:0% decimal to binary 08:05:19.080 --> 08:05:21.590 align:start position:0% decimal to binary pertains<08:05:19.978> to<08:05:20.160> a<08:05:20.340> lot<08:05:20.458> of<08:05:20.638> different<08:05:20.820> aspects 08:05:21.590 --> 08:05:21.600 align:start position:0% pertains to a lot of different aspects 08:05:21.600 --> 08:05:24.830 align:start position:0% pertains to a lot of different aspects of<08:05:22.080> as<08:05:22.860> I<08:05:23.100> just<08:05:23.218> mentioned<08:05:23.520> networking<08:05:24.180> so<08:05:24.660> to 08:05:24.830 --> 08:05:24.840 align:start position:0% of as I just mentioned networking so to 08:05:24.840 --> 08:05:27.230 align:start position:0% of as I just mentioned networking so to begin<08:05:24.958> with<08:05:25.260> binary<08:05:26.160> is<08:05:26.340> the<08:05:26.520> name<08:05:26.700> implies 08:05:27.230 --> 08:05:27.240 align:start position:0% begin with binary is the name implies 08:05:27.240 --> 08:05:31.128 align:start position:0% begin with binary is the name implies from<08:05:27.660> buy<08:05:28.020> is<08:05:28.500> what<08:05:28.680> we<08:05:28.798> call<08:05:28.920> a<08:05:29.160> base<08:05:29.520> 2<08:05:30.120> system 08:05:31.128 --> 08:05:31.138 align:start position:0% from buy is what we call a base 2 system 08:05:31.138 --> 08:05:33.948 align:start position:0% from buy is what we call a base 2 system more<08:05:31.798> commonly<08:05:32.160> we<08:05:32.398> used<08:05:32.520> a<08:05:32.760> base<08:05:33.000> 10<08:05:33.540> system 08:05:33.948 --> 08:05:33.958 align:start position:0% more commonly we used a base 10 system 08:05:33.958 --> 08:05:35.868 align:start position:0% more commonly we used a base 10 system decimal 08:05:35.868 --> 08:05:35.878 align:start position:0% decimal 08:05:35.878 --> 08:05:39.110 align:start position:0% decimal now<08:05:36.600> this<08:05:37.138> means<08:05:37.620> that<08:05:38.160> we<08:05:38.398> have<08:05:38.638> 10 08:05:39.110 --> 08:05:39.120 align:start position:0% now this means that we have 10 08:05:39.120 --> 08:05:43.310 align:start position:0% now this means that we have 10 possibilities<08:05:40.100> for<08:05:41.100> every<08:05:41.520> place<08:05:42.120> value<08:05:42.478> we 08:05:43.310 --> 08:05:43.320 align:start position:0% possibilities for every place value we 08:05:43.320 --> 08:05:45.048 align:start position:0% possibilities for every place value we have<08:05:43.440> between<08:05:43.680> a<08:05:43.978> zero<08:05:44.340> and<08:05:44.458> nine<08:05:44.638> you<08:05:44.878> add 08:05:45.048 --> 08:05:45.058 align:start position:0% have between a zero and nine you add 08:05:45.058 --> 08:05:46.610 align:start position:0% have between a zero and nine you add that<08:05:45.180> up<08:05:45.298> there<08:05:45.540> are<08:05:45.718> 10. 08:05:46.610 --> 08:05:46.620 align:start position:0% that up there are 10. 08:05:46.620 --> 08:05:49.128 align:start position:0% that up there are 10. now<08:05:46.978> with<08:05:47.340> binary<08:05:47.878> there's<08:05:48.120> only<08:05:48.360> two<08:05:48.718> options 08:05:49.128 --> 08:05:49.138 align:start position:0% now with binary there's only two options 08:05:49.138 --> 08:05:53.570 align:start position:0% now with binary there's only two options either<08:05:49.740> zero<08:05:50.398> or<08:05:51.180> one 08:05:53.570 --> 08:05:53.580 align:start position:0% 08:05:53.580 --> 08:05:56.628 align:start position:0% so<08:05:54.000> we<08:05:54.120> can<08:05:54.240> either<08:05:54.420> have<08:05:54.840> a<08:05:55.200> single<08:05:55.500> zero<08:05:55.920> or<08:05:56.458> a 08:05:56.628 --> 08:05:56.638 align:start position:0% so we can either have a single zero or a 08:05:56.638 --> 08:05:59.150 align:start position:0% so we can either have a single zero or a single<08:05:56.940> one<08:05:57.120> and<08:05:57.660> that's<08:05:57.840> what<08:05:58.020> we<08:05:58.138> call<08:05:58.378> a<08:05:58.798> DOT 08:05:59.150 --> 08:05:59.160 align:start position:0% single one and that's what we call a DOT 08:05:59.160 --> 08:06:02.388 align:start position:0% single one and that's what we call a DOT a<08:05:59.218> binary<08:05:59.700> digit<08:06:00.298> or 08:06:02.388 --> 08:06:02.398 align:start position:0% a binary digit or 08:06:02.398 --> 08:06:05.690 align:start position:0% a binary digit or a<08:06:02.878> bit 08:06:05.690 --> 08:06:05.700 align:start position:0% 08:06:05.700 --> 08:06:09.708 align:start position:0% so<08:06:06.360> the<08:06:06.600> binary<08:06:07.218> number<08:06:08.218> has<08:06:08.940> Place<08:06:09.240> markers 08:06:09.708 --> 08:06:09.718 align:start position:0% so the binary number has Place markers 08:06:09.718 --> 08:06:13.010 align:start position:0% so the binary number has Place markers that<08:06:10.080> are<08:06:10.200> similar<08:06:10.620> to<08:06:11.218> the<08:06:11.398> base<08:06:11.638> 10<08:06:11.940> system 08:06:13.010 --> 08:06:13.020 align:start position:0% that are similar to the base 10 system 08:06:13.020 --> 08:06:17.270 align:start position:0% that are similar to the base 10 system for<08:06:13.558> instance<08:06:13.798> if<08:06:13.978> we<08:06:14.218> have<08:06:14.458> a<08:06:15.000> a<08:06:15.320> decimal<08:06:16.320> base 08:06:17.270 --> 08:06:17.280 align:start position:0% for instance if we have a a decimal base 08:06:17.280 --> 08:06:19.910 align:start position:0% for instance if we have a a decimal base 10<08:06:17.580> numbering<08:06:18.240> system<08:06:18.420> the<08:06:19.378> second<08:06:19.558> place 08:06:19.910 --> 08:06:19.920 align:start position:0% 10 numbering system the second place 08:06:19.920 --> 08:06:23.090 align:start position:0% 10 numbering system the second place Mark<08:06:20.478> designates<08:06:21.478> the<08:06:22.260> tens<08:06:22.500> if<08:06:22.798> we<08:06:22.920> imagine 08:06:23.090 --> 08:06:23.100 align:start position:0% Mark designates the tens if we imagine 08:06:23.100 --> 08:06:25.010 align:start position:0% Mark designates the tens if we imagine that<08:06:23.458> there's<08:06:23.638> a 08:06:25.010 --> 08:06:25.020 align:start position:0% that there's a 08:06:25.020 --> 08:06:28.910 align:start position:0% that there's a uh<08:06:25.920> period<08:06:26.398> or<08:06:26.940> a<08:06:27.180> decimal<08:06:27.600> right<08:06:28.080> there 08:06:28.910 --> 08:06:28.920 align:start position:0% uh period or a decimal right there 08:06:28.920 --> 08:06:31.250 align:start position:0% uh period or a decimal right there the<08:06:29.398> third<08:06:29.520> designates<08:06:30.058> the<08:06:30.360> hundreds<08:06:30.840> and 08:06:31.250 --> 08:06:31.260 align:start position:0% the third designates the hundreds and 08:06:31.260 --> 08:06:34.430 align:start position:0% the third designates the hundreds and then<08:06:31.378> we<08:06:31.500> move<08:06:31.620> to<08:06:31.860> thousandths<08:06:32.660> and<08:06:33.660> ten 08:06:34.430 --> 08:06:34.440 align:start position:0% then we move to thousandths and ten 08:06:34.440 --> 08:06:36.590 align:start position:0% then we move to thousandths and ten thousandths<08:06:34.920> and<08:06:35.458> hundred<08:06:35.820> thousandths<08:06:36.360> and 08:06:36.590 --> 08:06:36.600 align:start position:0% thousandths and hundred thousandths and 08:06:36.600 --> 08:06:38.990 align:start position:0% thousandths and hundred thousandths and so<08:06:36.780> on<08:06:36.958> and<08:06:37.138> so<08:06:37.378> forth<08:06:37.680> and<08:06:38.398> in<08:06:38.580> each<08:06:38.700> one<08:06:38.878> of 08:06:38.990 --> 08:06:39.000 align:start position:0% so on and so forth and in each one of 08:06:39.000 --> 08:06:42.650 align:start position:0% so on and so forth and in each one of these<08:06:39.298> we<08:06:39.600> can<08:06:39.718> have<08:06:39.898> anywhere<08:06:40.378> from<08:06:41.100> zero 08:06:42.650 --> 08:06:42.660 align:start position:0% these we can have anywhere from zero 08:06:42.660 --> 08:06:46.010 align:start position:0% these we can have anywhere from zero to<08:06:43.138> 9<08:06:43.440> and<08:06:43.920> that's<08:06:44.160> ten<08:06:44.638> options<08:06:45.180> in<08:06:45.660> each<08:06:45.840> one 08:06:46.010 --> 08:06:46.020 align:start position:0% to 9 and that's ten options in each one 08:06:46.020 --> 08:06:47.690 align:start position:0% to 9 and that's ten options in each one of<08:06:46.138> those<08:06:46.320> spots 08:06:47.690 --> 08:06:47.700 align:start position:0% of those spots 08:06:47.700 --> 08:06:52.128 align:start position:0% of those spots now<08:06:48.840> in<08:06:49.680> base<08:06:50.100> 2<08:06:50.940> numbering<08:06:51.478> system<08:06:51.660> which<08:06:52.020> is 08:06:52.128 --> 08:06:52.138 align:start position:0% now in base 2 numbering system which is 08:06:52.138 --> 08:06:55.910 align:start position:0% now in base 2 numbering system which is binary<08:06:52.620> we<08:06:53.458> have<08:06:53.638> only<08:06:54.058> two<08:06:54.660> options<08:06:55.080> a<08:06:55.558> one<08:06:55.740> or 08:06:55.910 --> 08:06:55.920 align:start position:0% binary we have only two options a one or 08:06:55.920 --> 08:06:57.888 align:start position:0% binary we have only two options a one or a<08:06:56.040> zero<08:06:56.280> in<08:06:56.398> either<08:06:56.580> one<08:06:56.760> of<08:06:56.878> those<08:06:56.940> places<08:06:57.240> and 08:06:57.888 --> 08:06:57.898 align:start position:0% a zero in either one of those places and 08:06:57.898 --> 08:07:00.948 align:start position:0% a zero in either one of those places and in<08:06:58.080> computers<08:06:58.500> especially<08:06:59.040> in<08:06:59.398> a<08:07:00.058> lot<08:07:00.478> of<08:07:00.600> Ip 08:07:00.948 --> 08:07:00.958 align:start position:0% in computers especially in a lot of Ip 08:07:00.958 --> 08:07:03.948 align:start position:0% in computers especially in a lot of Ip addressing<08:07:01.440> we<08:07:01.740> really<08:07:01.978> deal<08:07:02.420> with<08:07:03.420> the 08:07:03.948 --> 08:07:03.958 align:start position:0% addressing we really deal with the 08:07:03.958 --> 08:07:08.628 align:start position:0% addressing we really deal with the difference<08:07:04.080> between<08:07:04.558> uh<08:07:05.458> eight<08:07:06.120> different 08:07:08.628 --> 08:07:08.638 align:start position:0% 08:07:08.638 --> 08:07:10.190 align:start position:0% places 08:07:10.190 --> 08:07:10.200 align:start position:0% places 08:07:10.200 --> 08:07:13.430 align:start position:0% places so<08:07:10.620> we're<08:07:10.798> going<08:07:10.978> to<08:07:11.100> call<08:07:11.478> these<08:07:12.478> eight<08:07:12.718> and 08:07:13.430 --> 08:07:13.440 align:start position:0% so we're going to call these eight and 08:07:13.440 --> 08:07:14.628 align:start position:0% so we're going to call these eight and octet 08:07:14.628 --> 08:07:14.638 align:start position:0% octet 08:07:14.638 --> 08:07:16.788 align:start position:0% octet so<08:07:15.120> this<08:07:15.360> eight<08:07:15.540> Place<08:07:15.780> binary<08:07:16.260> digit<08:07:16.680> is 08:07:16.788 --> 08:07:16.798 align:start position:0% so this eight Place binary digit is 08:07:16.798 --> 08:07:18.230 align:start position:0% so this eight Place binary digit is referred<08:07:17.100> to<08:07:17.160> as<08:07:17.280> an<08:07:17.458> octet<08:07:17.760> because<08:07:18.000> there's 08:07:18.230 --> 08:07:18.240 align:start position:0% referred to as an octet because there's 08:07:18.240 --> 08:07:22.128 align:start position:0% referred to as an octet because there's one<08:07:18.780> two<08:07:19.440> three<08:07:19.978> four<08:07:20.520> five<08:07:20.940> six<08:07:21.360> seven<08:07:21.660> eight 08:07:22.128 --> 08:07:22.138 align:start position:0% one two three four five six seven eight 08:07:22.138 --> 08:07:23.990 align:start position:0% one two three four five six seven eight of<08:07:22.378> them<08:07:22.500> and<08:07:22.920> you'll<08:07:23.040> see<08:07:23.218> these<08:07:23.458> numbers<08:07:23.580> pop 08:07:23.990 --> 08:07:24.000 align:start position:0% of them and you'll see these numbers pop 08:07:24.000 --> 08:07:26.570 align:start position:0% of them and you'll see these numbers pop up<08:07:24.180> over<08:07:24.600> and<08:07:24.780> over<08:07:25.020> again<08:07:25.260> so<08:07:26.100> this<08:07:26.280> is<08:07:26.398> really 08:07:26.570 --> 08:07:26.580 align:start position:0% up over and over again so this is really 08:07:26.580 --> 08:07:28.190 align:start position:0% up over and over again so this is really as<08:07:26.940> far<08:07:27.058> as<08:07:27.240> you<08:07:27.298> need<08:07:27.478> to<08:07:27.540> know<08:07:27.660> for<08:07:27.840> binary 08:07:28.190 --> 08:07:28.200 align:start position:0% as far as you need to know for binary 08:07:28.200 --> 08:07:30.230 align:start position:0% as far as you need to know for binary although<08:07:28.500> you<08:07:28.680> can<08:07:28.740> go<08:07:28.920> even<08:07:29.040> further<08:07:29.458> so<08:07:30.180> if 08:07:30.230 --> 08:07:30.240 align:start position:0% although you can go even further so if 08:07:30.240 --> 08:07:32.868 align:start position:0% although you can go even further so if we<08:07:30.420> look<08:07:30.660> at<08:07:30.958> this<08:07:31.200> octet<08:07:31.740> from<08:07:32.398> the<08:07:32.638> right 08:07:32.868 --> 08:07:32.878 align:start position:0% we look at this octet from the right 08:07:32.878 --> 08:07:34.368 align:start position:0% we look at this octet from the right side<08:07:33.120> to<08:07:33.420> the<08:07:33.540> left 08:07:34.368 --> 08:07:34.378 align:start position:0% side to the left 08:07:34.378 --> 08:07:38.750 align:start position:0% side to the left the<08:07:35.040> first<08:07:35.280> place<08:07:35.520> Mark<08:07:35.940> is<08:07:36.660> what<08:07:36.840> we<08:07:36.958> call 08:07:38.750 --> 08:07:38.760 align:start position:0% the first place Mark is what we call 08:07:38.760 --> 08:07:40.610 align:start position:0% the first place Mark is what we call 2<08:07:39.240> to<08:07:39.420> the<08:07:39.600> 0<08:07:39.718> power 08:07:40.610 --> 08:07:40.620 align:start position:0% 2 to the 0 power 08:07:40.620 --> 08:07:43.190 align:start position:0% 2 to the 0 power right<08:07:41.100> if<08:07:41.458> we<08:07:41.638> were<08:07:41.878> talking<08:07:42.058> about<08:07:42.298> this<08:07:42.600> in 08:07:43.190 --> 08:07:43.200 align:start position:0% right if we were talking about this in 08:07:43.200 --> 08:07:46.490 align:start position:0% right if we were talking about this in tens<08:07:43.558> this<08:07:44.100> would<08:07:44.218> be<08:07:44.398> the<08:07:44.580> ones<08:07:44.878> place<08:07:45.120> y 08:07:46.490 --> 08:07:46.500 align:start position:0% tens this would be the ones place y 08:07:46.500 --> 08:07:48.530 align:start position:0% tens this would be the ones place y because<08:07:46.798> it's<08:07:47.040> 10<08:07:47.340> to<08:07:47.520> the<08:07:47.638> zero<08:07:48.000> power<08:07:48.120> which 08:07:48.530 --> 08:07:48.540 align:start position:0% because it's 10 to the zero power which 08:07:48.540 --> 08:07:51.048 align:start position:0% because it's 10 to the zero power which is<08:07:48.718> ones<08:07:49.138> anything<08:07:49.860> taken<08:07:50.340> to<08:07:50.458> the<08:07:50.520> zero<08:07:50.878> power 08:07:51.048 --> 08:07:51.058 align:start position:0% is ones anything taken to the zero power 08:07:51.058 --> 08:07:52.968 align:start position:0% is ones anything taken to the zero power is<08:07:51.660> one 08:07:52.968 --> 08:07:52.978 align:start position:0% is one 08:07:52.978 --> 08:07:56.030 align:start position:0% is one next<08:07:53.580> we<08:07:54.000> have<08:07:54.120> 10<08:07:54.298> to<08:07:54.600> the<08:07:54.780> first<08:07:55.080> Power<08:07:55.440> which 08:07:56.030 --> 08:07:56.040 align:start position:0% next we have 10 to the first Power which 08:07:56.040 --> 08:07:57.830 align:start position:0% next we have 10 to the first Power which is<08:07:56.160> going<08:07:56.280> to<08:07:56.340> equal<08:07:56.458> 2.<08:07:57.000> if<08:07:57.240> you<08:07:57.420> recall<08:07:57.660> we 08:07:57.830 --> 08:07:57.840 align:start position:0% is going to equal 2. if you recall we 08:07:57.840 --> 08:08:00.048 align:start position:0% is going to equal 2. if you recall we call<08:07:57.958> this<08:07:58.138> the<08:07:58.320> tens<08:07:58.558> place<08:07:58.860> 10<08:07:59.580> to<08:07:59.820> the<08:07:59.940> one 08:08:00.048 --> 08:08:00.058 align:start position:0% call this the tens place 10 to the one 08:08:00.058 --> 08:08:05.090 align:start position:0% call this the tens place 10 to the one power<08:08:00.360> means<08:08:01.080> 10<08:08:01.440> by<08:08:02.100> itself<08:08:02.458> is<08:08:03.298> 10. 08:08:05.090 --> 08:08:05.100 align:start position:0% power means 10 by itself is 10. 08:08:05.100 --> 08:08:06.888 align:start position:0% power means 10 by itself is 10. then<08:08:05.638> we<08:08:05.820> have<08:08:05.940> 10<08:08:06.120> to<08:08:06.298> the<08:08:06.420> second<08:08:06.540> power 08:08:06.888 --> 08:08:06.898 align:start position:0% then we have 10 to the second power 08:08:06.898 --> 08:08:10.368 align:start position:0% then we have 10 to the second power which<08:08:07.558> is<08:08:07.740> 4<08:08:08.040> and<08:08:08.458> if<08:08:08.638> you<08:08:08.820> recall<08:08:09.298> in<08:08:09.898> decimal 08:08:10.368 --> 08:08:10.378 align:start position:0% which is 4 and if you recall in decimal 08:08:10.378 --> 08:08:12.468 align:start position:0% which is 4 and if you recall in decimal this<08:08:10.558> is<08:08:10.680> 10<08:08:10.798> to<08:08:10.978> the<08:08:11.160> second<08:08:11.340> which<08:08:12.058> would<08:08:12.298> be 08:08:12.468 --> 08:08:12.478 align:start position:0% this is 10 to the second which would be 08:08:12.478 --> 08:08:14.388 align:start position:0% this is 10 to the second which would be 10<08:08:12.718> times<08:08:12.958> 10<08:08:13.200> which<08:08:13.440> is<08:08:13.620> 100<08:08:13.740> you<08:08:14.218> can<08:08:14.340> see 08:08:14.388 --> 08:08:14.398 align:start position:0% 10 times 10 which is 100 you can see 08:08:14.398 --> 08:08:16.190 align:start position:0% 10 times 10 which is 100 you can see where<08:08:14.580> this<08:08:14.760> is<08:08:14.940> going 08:08:16.190 --> 08:08:16.200 align:start position:0% where this is going 08:08:16.200 --> 08:08:19.310 align:start position:0% where this is going so<08:08:16.740> 2<08:08:17.100> to<08:08:17.340> the<08:08:17.458> third<08:08:17.638> is<08:08:17.940> eight<08:08:18.240> two<08:08:19.020> to<08:08:19.200> the 08:08:19.310 --> 08:08:19.320 align:start position:0% so 2 to the third is eight two to the 08:08:19.320 --> 08:08:22.310 align:start position:0% so 2 to the third is eight two to the fourth<08:08:19.680> equals<08:08:20.040> 16<08:08:20.420> 2<08:08:21.420> to<08:08:21.600> the<08:08:21.718> fifth<08:08:21.958> equals 08:08:22.310 --> 08:08:22.320 align:start position:0% fourth equals 16 2 to the fifth equals 08:08:22.320 --> 08:08:26.330 align:start position:0% fourth equals 16 2 to the fifth equals 32<08:08:22.798> 2<08:08:23.700> to<08:08:23.878> the<08:08:24.000> 6<08:08:24.120> equals<08:08:24.540> 64<08:08:25.020> and<08:08:25.798> 2<08:08:25.978> to<08:08:26.100> the<08:08:26.218> 7 08:08:26.330 --> 08:08:26.340 align:start position:0% 32 2 to the 6 equals 64 and 2 to the 7 08:08:26.340 --> 08:08:29.868 align:start position:0% 32 2 to the 6 equals 64 and 2 to the 7 equals<08:08:27.080> 128.<08:08:28.080> so<08:08:28.320> each<08:08:28.620> one<08:08:28.860> of<08:08:29.040> these<08:08:29.340> Place 08:08:29.868 --> 08:08:29.878 align:start position:0% equals 128. so each one of these Place 08:08:29.878 --> 08:08:33.948 align:start position:0% equals 128. so each one of these Place markers<08:08:30.360> is<08:08:30.958> equivalent 08:08:33.948 --> 08:08:33.958 align:start position:0% 08:08:33.958 --> 08:08:37.190 align:start position:0% to<08:08:34.798> this<08:08:35.218> number<08:08:35.878> whether<08:08:36.420> it's<08:08:36.600> turned<08:08:36.898> on<08:08:36.958> or 08:08:37.190 --> 08:08:37.200 align:start position:0% to this number whether it's turned on or 08:08:37.200 --> 08:08:40.730 align:start position:0% to this number whether it's turned on or off 08:08:40.730 --> 08:08:40.740 align:start position:0% 08:08:40.740 --> 08:08:43.730 align:start position:0% now<08:08:41.340> to<08:08:41.700> help<08:08:42.058> clarify<08:08:42.540> this<08:08:42.718> a<08:08:42.898> bit<08:08:43.020> each 08:08:43.730 --> 08:08:43.740 align:start position:0% now to help clarify this a bit each 08:08:43.740 --> 08:08:44.990 align:start position:0% now to help clarify this a bit each place<08:08:44.040> here 08:08:44.990 --> 08:08:45.000 align:start position:0% place here 08:08:45.000 --> 08:08:47.628 align:start position:0% place here has<08:08:45.540> one<08:08:45.840> of<08:08:46.020> two<08:08:46.320> options<08:08:46.680> correct<08:08:47.218> because 08:08:47.628 --> 08:08:47.638 align:start position:0% has one of two options correct because 08:08:47.638 --> 08:08:51.048 align:start position:0% has one of two options correct because it's<08:08:47.878> base<08:08:48.120> two<08:08:48.420> if<08:08:49.320> it's<08:08:49.558> off<08:08:50.160> that<08:08:50.878> means 08:08:51.048 --> 08:08:51.058 align:start position:0% it's base two if it's off that means 08:08:51.058 --> 08:08:53.690 align:start position:0% it's base two if it's off that means it's<08:08:51.240> a<08:08:51.478> zero<08:08:51.840> as<08:08:52.020> you<08:08:52.200> see<08:08:52.320> right<08:08:52.558> here<08:08:52.798> and 08:08:53.690 --> 08:08:53.700 align:start position:0% it's a zero as you see right here and 08:08:53.700 --> 08:08:55.310 align:start position:0% it's a zero as you see right here and the<08:08:53.940> numbered<08:08:54.360> means<08:08:54.660> it's<08:08:54.840> not<08:08:55.138> being 08:08:55.310 --> 08:08:55.320 align:start position:0% the numbered means it's not being 08:08:55.320 --> 08:08:57.410 align:start position:0% the numbered means it's not being counted<08:08:55.798> so<08:08:56.040> we<08:08:56.218> don't<08:08:56.398> count<08:08:56.760> any<08:08:57.120> of<08:08:57.240> these 08:08:57.410 --> 08:08:57.420 align:start position:0% counted so we don't count any of these 08:08:57.420 --> 08:08:59.690 align:start position:0% counted so we don't count any of these numbers<08:08:57.540> we've<08:08:57.958> just<08:08:58.080> calculated<08:08:58.558> so<08:08:59.340> if<08:08:59.458> all 08:08:59.690 --> 08:08:59.700 align:start position:0% numbers we've just calculated so if all 08:08:59.700 --> 08:09:01.548 align:start position:0% numbers we've just calculated so if all the<08:08:59.878> bits<08:09:00.180> are<08:09:00.360> off<08:09:00.478> that<08:09:00.898> means<08:09:01.138> that<08:09:01.320> we<08:09:01.440> have 08:09:01.548 --> 08:09:01.558 align:start position:0% the bits are off that means that we have 08:09:01.558 --> 08:09:03.230 align:start position:0% the bits are off that means that we have a<08:09:01.740> number<08:09:01.860> of<08:09:02.100> zero 08:09:03.230 --> 08:09:03.240 align:start position:0% a number of zero 08:09:03.240 --> 08:09:06.110 align:start position:0% a number of zero if<08:09:03.718> all<08:09:03.958> of<08:09:04.080> the<08:09:04.200> bits<08:09:04.500> are<08:09:04.680> on<08:09:04.920> then<08:09:05.820> this 08:09:06.110 --> 08:09:06.120 align:start position:0% if all of the bits are on then this 08:09:06.120 --> 08:09:08.030 align:start position:0% if all of the bits are on then this means<08:09:06.360> we<08:09:06.660> add<08:09:07.080> each<08:09:07.558> of<08:09:07.740> the<08:09:07.860> numbers 08:09:08.030 --> 08:09:08.040 align:start position:0% means we add each of the numbers 08:09:08.040 --> 08:09:10.250 align:start position:0% means we add each of the numbers together 08:09:10.250 --> 08:09:10.260 align:start position:0% together 08:09:10.260 --> 08:09:14.990 align:start position:0% together so<08:09:10.798> we<08:09:10.978> get<08:09:11.100> 128<08:09:11.820> plus<08:09:12.120> 64<08:09:12.840> plus<08:09:13.740> 32<08:09:14.340> plus<08:09:14.638> 16 08:09:14.990 --> 08:09:15.000 align:start position:0% so we get 128 plus 64 plus 32 plus 16 08:09:15.000 --> 08:09:18.730 align:start position:0% so we get 128 plus 64 plus 32 plus 16 plus<08:09:15.420> 8<08:09:15.780> plus<08:09:16.080> 4<08:09:16.378> plus<08:09:16.680> 2<08:09:16.920> plus<08:09:17.160> 1<08:09:17.458> which<08:09:17.700> equals 08:09:18.730 --> 08:09:18.740 align:start position:0% plus 8 plus 4 plus 2 plus 1 which equals 08:09:18.740 --> 08:09:21.230 align:start position:0% plus 8 plus 4 plus 2 plus 1 which equals 255.<08:09:19.740> now<08:09:20.280> believe<08:09:20.520> it<08:09:20.700> or<08:09:20.760> not<08:09:20.878> you<08:09:21.180> can 08:09:21.230 --> 08:09:21.240 align:start position:0% 255. now believe it or not you can 08:09:21.240 --> 08:09:24.350 align:start position:0% 255. now believe it or not you can create<08:09:21.478> any<08:09:22.080> combination<08:09:22.620> of<08:09:22.860> numbers<08:09:23.360> from 08:09:24.350 --> 08:09:24.360 align:start position:0% create any combination of numbers from 08:09:24.360 --> 08:09:27.410 align:start position:0% create any combination of numbers from just<08:09:25.080> binary<08:09:25.680> you<08:09:26.040> don't<08:09:26.218> need<08:09:26.398> decimal<08:09:26.940> we're 08:09:27.410 --> 08:09:27.420 align:start position:0% just binary you don't need decimal we're 08:09:27.420 --> 08:09:29.090 align:start position:0% just binary you don't need decimal we're going<08:09:27.540> to<08:09:27.600> see<08:09:27.718> that<08:09:27.840> in<08:09:28.020> just<08:09:28.138> a<08:09:28.320> second 08:09:29.090 --> 08:09:29.100 align:start position:0% going to see that in just a second 08:09:29.100 --> 08:09:30.948 align:start position:0% going to see that in just a second so<08:09:29.580> for<08:09:29.760> example 08:09:30.948 --> 08:09:30.958 align:start position:0% so for example 08:09:30.958 --> 08:09:37.030 align:start position:0% so for example let's<08:09:31.440> say<08:09:31.620> the<08:09:31.798> binary<08:09:32.160> number<08:09:32.780> is<08:09:33.780> uh 08:09:37.030 --> 08:09:37.040 align:start position:0% 08:09:37.040 --> 08:09:41.888 align:start position:0% zero<08:09:38.040> zero<08:09:38.638> zero<08:09:39.360> zero<08:09:40.080> zero<08:09:40.740> one<08:09:41.218> one<08:09:41.458> one 08:09:41.888 --> 08:09:41.898 align:start position:0% zero zero zero zero zero one one one 08:09:41.898 --> 08:09:47.930 align:start position:0% zero zero zero zero zero one one one well<08:09:42.898> in<08:09:43.440> this<08:09:43.558> case<08:09:43.798> the<08:09:44.700> 128<08:09:45.420> 64<08:09:46.260> 32<08:09:46.978> 16<08:09:47.340> and<08:09:47.700> 8 08:09:47.930 --> 08:09:47.940 align:start position:0% well in this case the 128 64 32 16 and 8 08:09:47.940 --> 08:09:50.810 align:start position:0% well in this case the 128 64 32 16 and 8 Bits<08:09:48.360> are<08:09:48.958> all<08:09:49.200> off<08:09:49.500> the<08:09:50.100> only<08:09:50.218> ones<08:09:50.458> that<08:09:50.638> are 08:09:50.810 --> 08:09:50.820 align:start position:0% Bits are all off the only ones that are 08:09:50.820 --> 08:09:54.170 align:start position:0% Bits are all off the only ones that are on<08:09:51.058> are<08:09:51.780> four<08:09:52.138> two<08:09:52.620> and<08:09:52.978> one<08:09:53.160> and<08:09:53.700> if<08:09:53.878> we<08:09:54.000> add 08:09:54.170 --> 08:09:54.180 align:start position:0% on are four two and one and if we add 08:09:54.180 --> 08:09:57.530 align:start position:0% on are four two and one and if we add those<08:09:54.420> together<08:09:54.680> four<08:09:55.680> plus<08:09:56.160> two<08:09:56.638> plus<08:09:57.180> one 08:09:57.530 --> 08:09:57.540 align:start position:0% those together four plus two plus one 08:09:57.540 --> 08:10:00.530 align:start position:0% those together four plus two plus one we'll<08:09:57.898> get<08:09:58.080> 7. 08:10:00.530 --> 08:10:00.540 align:start position:0% we'll get 7. 08:10:00.540 --> 08:10:04.430 align:start position:0% we'll get 7. 4<08:10:01.320> plus<08:10:01.620> 2<08:10:01.860> is<08:10:02.040> 6<08:10:02.280> plus<08:10:02.638> 1<08:10:02.940> is<08:10:03.120> 7. 08:10:04.430 --> 08:10:04.440 align:start position:0% 4 plus 2 is 6 plus 1 is 7. 08:10:04.440 --> 08:10:07.910 align:start position:0% 4 plus 2 is 6 plus 1 is 7. if<08:10:04.920> we<08:10:05.100> take<08:10:05.340> another<08:10:05.700> number 08:10:07.910 --> 08:10:07.920 align:start position:0% if we take another number 08:10:07.920 --> 08:10:12.830 align:start position:0% if we take another number say<08:10:08.398> 0<08:10:08.760> 1<08:10:09.180> 1<08:10:09.600> 0<08:10:10.138> 0<08:10:10.500> 1<08:10:10.860> 1<08:10:11.040> 0. 08:10:12.830 --> 08:10:12.840 align:start position:0% say 0 1 1 0 0 1 1 0. 08:10:12.840 --> 08:10:16.788 align:start position:0% say 0 1 1 0 0 1 1 0. then<08:10:13.200> this<08:10:13.440> is<08:10:13.558> going<08:10:13.680> to<08:10:13.740> equate<08:10:14.100> to<08:10:14.520> 102.<08:10:15.240> why 08:10:16.788 --> 08:10:16.798 align:start position:0% then this is going to equate to 102. why 08:10:16.798 --> 08:10:24.410 align:start position:0% then this is going to equate to 102. why 64<08:10:17.780> plus<08:10:18.780> 32<08:10:19.740> equals<08:10:20.580> 96<08:10:21.180> plus<08:10:22.100> 4<08:10:23.100> equals<08:10:24.058> 100 08:10:24.410 --> 08:10:24.420 align:start position:0% 64 plus 32 equals 96 plus 4 equals 100 08:10:24.420 --> 08:10:28.070 align:start position:0% 64 plus 32 equals 96 plus 4 equals 100 plus<08:10:25.260> 2<08:10:25.680> equals<08:10:26.340> 102. 08:10:28.070 --> 08:10:28.080 align:start position:0% plus 2 equals 102. 08:10:28.080 --> 08:10:30.530 align:start position:0% plus 2 equals 102. so<08:10:28.558> it's<08:10:28.680> pretty<08:10:28.920> simple<08:10:29.218> you<08:10:30.058> just<08:10:30.180> take<08:10:30.360> the 08:10:30.530 --> 08:10:30.540 align:start position:0% so it's pretty simple you just take the 08:10:30.540 --> 08:10:31.968 align:start position:0% so it's pretty simple you just take the number<08:10:30.660> with<08:10:30.958> the<08:10:31.080> ones<08:10:31.320> under<08:10:31.500> it<08:10:31.680> and<08:10:31.798> add 08:10:31.968 --> 08:10:31.978 align:start position:0% number with the ones under it and add 08:10:31.978 --> 08:10:33.468 align:start position:0% number with the ones under it and add them<08:10:32.160> together<08:10:32.340> so<08:10:33.000> now<08:10:33.120> that<08:10:33.298> we've 08:10:33.468 --> 08:10:33.478 align:start position:0% them together so now that we've 08:10:33.478 --> 08:10:37.250 align:start position:0% them together so now that we've converted<08:10:34.280> binary<08:10:35.280> into<08:10:36.240> decimal<08:10:36.780> a<08:10:37.080> number 08:10:37.250 --> 08:10:37.260 align:start position:0% converted binary into decimal a number 08:10:37.260 --> 08:10:39.888 align:start position:0% converted binary into decimal a number that<08:10:37.440> we<08:10:37.620> all<08:10:37.740> know<08:10:38.040> let's<08:10:39.000> go<08:10:39.298> ahead<08:10:39.540> and<08:10:39.780> see 08:10:39.888 --> 08:10:39.898 align:start position:0% that we all know let's go ahead and see 08:10:39.898 --> 08:10:41.570 align:start position:0% that we all know let's go ahead and see if<08:10:40.020> we<08:10:40.080> can<08:10:40.200> convert<08:10:40.500> the<08:10:40.680> other<08:10:40.798> way<08:10:40.978> decimal 08:10:41.570 --> 08:10:41.580 align:start position:0% if we can convert the other way decimal 08:10:41.580 --> 08:10:43.670 align:start position:0% if we can convert the other way decimal to<08:10:41.760> Binary<08:10:42.120> now<08:10:42.600> for<08:10:42.958> this<08:10:43.138> process<08:10:43.378> we're 08:10:43.670 --> 08:10:43.680 align:start position:0% to Binary now for this process we're 08:10:43.680 --> 08:10:45.650 align:start position:0% to Binary now for this process we're going<08:10:43.798> to<08:10:43.860> use<08:10:44.040> the<08:10:44.280> same<08:10:44.458> exact<08:10:44.820> chart 08:10:45.650 --> 08:10:45.660 align:start position:0% going to use the same exact chart 08:10:45.660 --> 08:10:47.448 align:start position:0% going to use the same exact chart that<08:10:46.138> we<08:10:46.378> just<08:10:46.558> saw 08:10:47.448 --> 08:10:47.458 align:start position:0% that we just saw 08:10:47.458 --> 08:10:49.730 align:start position:0% that we just saw with<08:10:48.058> the<08:10:48.298> binary<08:10:48.660> conversion 08:10:49.730 --> 08:10:49.740 align:start position:0% with the binary conversion 08:10:49.740 --> 08:10:51.410 align:start position:0% with the binary conversion and<08:10:50.280> this<08:10:50.458> chart<08:10:50.638> is<08:10:50.820> going<08:10:51.000> to<08:10:51.058> help<08:10:51.240> us 08:10:51.410 --> 08:10:51.420 align:start position:0% and this chart is going to help us 08:10:51.420 --> 08:10:54.048 align:start position:0% and this chart is going to help us visually<08:10:51.958> represent<08:10:52.680> all<08:10:53.040> the<08:10:53.160> binary<08:10:53.520> digits 08:10:54.048 --> 08:10:54.058 align:start position:0% visually represent all the binary digits 08:10:54.058 --> 08:10:55.368 align:start position:0% visually represent all the binary digits which<08:10:54.240> is<08:10:54.360> why<08:10:54.540> I<08:10:54.718> like<08:10:54.840> it<08:10:54.958> in<08:10:55.200> their 08:10:55.368 --> 08:10:55.378 align:start position:0% which is why I like it in their 08:10:55.378 --> 08:10:57.048 align:start position:0% which is why I like it in their placeholders<08:10:55.978> and<08:10:56.398> it<08:10:56.520> makes<08:10:56.700> it<08:10:56.820> a<08:10:56.940> lot 08:10:57.048 --> 08:10:57.058 align:start position:0% placeholders and it makes it a lot 08:10:57.058 --> 08:10:59.330 align:start position:0% placeholders and it makes it a lot easier<08:10:57.420> so<08:10:58.080> for<08:10:58.320> decimal<08:10:58.680> to<08:10:58.798> Binary<08:10:59.100> we 08:10:59.330 --> 08:10:59.340 align:start position:0% easier so for decimal to Binary we 08:10:59.340 --> 08:11:01.368 align:start position:0% easier so for decimal to Binary we simply<08:10:59.580> go<08:10:59.700> from<08:10:59.940> left<08:11:00.120> to<08:11:00.298> right<08:11:00.478> and<08:11:01.138> break 08:11:01.368 --> 08:11:01.378 align:start position:0% simply go from left to right and break 08:11:01.378 --> 08:11:04.968 align:start position:0% simply go from left to right and break down<08:11:01.680> the<08:11:01.978> number<08:11:02.240> until<08:11:03.240> we<08:11:03.718> reach<08:11:04.200> the<08:11:04.558> zero 08:11:04.968 --> 08:11:04.978 align:start position:0% down the number until we reach the zero 08:11:04.978 --> 08:11:07.190 align:start position:0% down the number until we reach the zero so<08:11:05.458> let<08:11:05.820> me<08:11:06.058> break<08:11:06.478> that<08:11:06.660> down<08:11:06.840> a<08:11:07.020> little<08:11:07.080> bit 08:11:07.190 --> 08:11:07.200 align:start position:0% so let me break that down a little bit 08:11:07.200 --> 08:11:10.548 align:start position:0% so let me break that down a little bit for<08:11:07.740> instance<08:11:07.978> if<08:11:08.218> we<08:11:08.340> take<08:11:08.458> the<08:11:08.700> number<08:11:08.878> 128 08:11:10.548 --> 08:11:10.558 align:start position:0% for instance if we take the number 128 08:11:10.558 --> 08:11:12.888 align:start position:0% for instance if we take the number 128 right<08:11:10.978> this<08:11:11.280> is<08:11:11.398> pretty<08:11:11.638> easy<08:11:11.878> to<08:11:12.180> convert<08:11:12.478> we 08:11:12.888 --> 08:11:12.898 align:start position:0% right this is pretty easy to convert we 08:11:12.898 --> 08:11:14.750 align:start position:0% right this is pretty easy to convert we plug<08:11:13.080> it<08:11:13.200> into<08:11:13.320> this<08:11:13.558> chart<08:11:13.740> how<08:11:14.398> many<08:11:14.520> times 08:11:14.750 --> 08:11:14.760 align:start position:0% plug it into this chart how many times 08:11:14.760 --> 08:11:18.048 align:start position:0% plug it into this chart how many times does<08:11:15.120> 128<08:11:15.780> go<08:11:16.260> into<08:11:16.500> 128 08:11:18.048 --> 08:11:18.058 align:start position:0% does 128 go into 128 08:11:18.058 --> 08:11:19.610 align:start position:0% does 128 go into 128 one<08:11:18.660> time 08:11:19.610 --> 08:11:19.620 align:start position:0% one time 08:11:19.620 --> 08:11:22.128 align:start position:0% one time if<08:11:20.100> we<08:11:20.280> take<08:11:20.638> all<08:11:20.940> the<08:11:21.120> others<08:11:21.478> and<08:11:22.020> we 08:11:22.128 --> 08:11:22.138 align:start position:0% if we take all the others and we 08:11:22.138 --> 08:11:23.570 align:start position:0% if we take all the others and we subtract<08:11:22.500> them<08:11:22.740> we're<08:11:22.920> going<08:11:23.040> to<08:11:23.100> have<08:11:23.218> zero 08:11:23.570 --> 08:11:23.580 align:start position:0% subtract them we're going to have zero 08:11:23.580 --> 08:11:26.570 align:start position:0% subtract them we're going to have zero right<08:11:23.760> because<08:11:24.120> now<08:11:24.478> 128<08:11:25.260> minus<08:11:25.620> 128<08:11:26.040> is<08:11:26.280> zero 08:11:26.570 --> 08:11:26.580 align:start position:0% right because now 128 minus 128 is zero 08:11:26.580 --> 08:11:29.990 align:start position:0% right because now 128 minus 128 is zero that<08:11:27.240> leaves<08:11:27.478> us<08:11:27.600> with<08:11:27.718> our<08:11:27.958> binary<08:11:28.378> number 08:11:29.990 --> 08:11:30.000 align:start position:0% that leaves us with our binary number 08:11:30.000 --> 08:11:33.708 align:start position:0% that leaves us with our binary number one<08:11:30.718> zero<08:11:31.320> zero<08:11:31.740> zero<08:11:32.218> zero<08:11:32.580> zero<08:11:33.000> zero<08:11:33.360> zero 08:11:33.708 --> 08:11:33.718 align:start position:0% one zero zero zero zero zero zero zero 08:11:33.718 --> 08:11:36.770 align:start position:0% one zero zero zero zero zero zero zero which<08:11:34.260> is<08:11:34.378> equivalent<08:11:34.798> to<08:11:35.040> 128. 08:11:36.770 --> 08:11:36.780 align:start position:0% which is equivalent to 128. 08:11:36.780 --> 08:11:38.628 align:start position:0% which is equivalent to 128. now<08:11:37.260> if<08:11:37.500> we<08:11:37.680> take<08:11:37.920> a<08:11:38.040> look<08:11:38.160> at<08:11:38.340> a<08:11:38.520> different 08:11:38.628 --> 08:11:38.638 align:start position:0% now if we take a look at a different 08:11:38.638 --> 08:11:43.368 align:start position:0% now if we take a look at a different number<08:11:38.940> let's<08:11:39.420> say<08:11:39.718> the<08:11:40.320> number<08:11:40.500> 218 08:11:43.368 --> 08:11:43.378 align:start position:0% number let's say the number 218 08:11:43.378 --> 08:11:46.490 align:start position:0% number let's say the number 218 this<08:11:43.920> is<08:11:44.040> going<08:11:44.160> to<08:11:44.218> take<08:11:44.340> a<08:11:44.520> little<08:11:44.638> more<08:11:44.878> math 08:11:46.490 --> 08:11:46.500 align:start position:0% this is going to take a little more math 08:11:46.500 --> 08:11:49.670 align:start position:0% this is going to take a little more math does<08:11:47.040> 218<08:11:47.520> go<08:11:47.820> in<08:11:48.000> does<08:11:48.180> 128<08:11:48.660> go<08:11:48.840> into<08:11:48.958> 218<08:11:49.440> it 08:11:49.670 --> 08:11:49.680 align:start position:0% does 218 go in does 128 go into 218 it 08:11:49.680 --> 08:11:51.230 align:start position:0% does 218 go in does 128 go into 218 it certainly<08:11:50.040> does 08:11:51.230 --> 08:11:51.240 align:start position:0% certainly does 08:11:51.240 --> 08:11:55.490 align:start position:0% certainly does so<08:11:51.840> 218<08:11:52.378> minus<08:11:52.920> 128<08:11:53.580> has<08:11:54.298> a<08:11:54.478> remainder 08:11:55.490 --> 08:11:55.500 align:start position:0% so 218 minus 128 has a remainder 08:11:55.500 --> 08:11:59.150 align:start position:0% so 218 minus 128 has a remainder of<08:11:55.920> a<08:11:56.040> certain<08:11:56.218> amount<08:11:56.520> which<08:11:57.420> is<08:11:57.600> 90. 08:11:59.150 --> 08:11:59.160 align:start position:0% of a certain amount which is 90. 08:11:59.160 --> 08:12:02.510 align:start position:0% of a certain amount which is 90. does<08:11:59.700> 64<08:12:00.240> go<08:12:00.478> into<08:12:00.600> 90<08:12:00.840> it<08:12:01.200> does<08:12:01.378> we<08:12:02.040> now<08:12:02.160> have<08:12:02.340> a 08:12:02.510 --> 08:12:02.520 align:start position:0% does 64 go into 90 it does we now have a 08:12:02.520 --> 08:12:07.010 align:start position:0% does 64 go into 90 it does we now have a remainder<08:12:02.940> of<08:12:03.058> 26.<08:12:04.020> does<08:12:04.860> 32<08:12:05.700> go<08:12:05.940> into<08:12:06.120> 26<08:12:06.600> no 08:12:07.010 --> 08:12:07.020 align:start position:0% remainder of 26. does 32 go into 26 no 08:12:07.020 --> 08:12:09.530 align:start position:0% remainder of 26. does 32 go into 26 no it<08:12:07.200> doesn't<08:12:07.320> so<08:12:07.620> we<08:12:07.740> put<08:12:07.920> a<08:12:08.100> zero 08:12:09.530 --> 08:12:09.540 align:start position:0% it doesn't so we put a zero 08:12:09.540 --> 08:12:12.888 align:start position:0% it doesn't so we put a zero does<08:12:10.080> 16<08:12:10.320> go<08:12:10.740> into<08:12:10.860> 26<08:12:11.398> yep<08:12:11.940> it<08:12:12.180> does<08:12:12.360> which 08:12:12.888 --> 08:12:12.898 align:start position:0% does 16 go into 26 yep it does which 08:12:12.898 --> 08:12:15.350 align:start position:0% does 16 go into 26 yep it does which leaves<08:12:13.200> us<08:12:13.320> with<08:12:13.440> a<08:12:13.558> remainder<08:12:13.860> of<08:12:14.040> 10. 08:12:15.350 --> 08:12:15.360 align:start position:0% leaves us with a remainder of 10. 08:12:15.360 --> 08:12:18.288 align:start position:0% leaves us with a remainder of 10. does<08:12:16.138> 8<08:12:16.500> go<08:12:16.798> into<08:12:16.920> 10<08:12:17.218> it<08:12:17.580> does<08:12:17.760> which<08:12:18.058> leaves 08:12:18.288 --> 08:12:18.298 align:start position:0% does 8 go into 10 it does which leaves 08:12:18.298 --> 08:12:21.230 align:start position:0% does 8 go into 10 it does which leaves us<08:12:18.420> a<08:12:18.540> remainder<08:12:18.840> of<08:12:19.020> 2<08:12:19.260> does<08:12:19.920> 4<08:12:20.160> go<08:12:20.398> into<08:12:20.520> 2<08:12:20.760> it 08:12:21.230 --> 08:12:21.240 align:start position:0% us a remainder of 2 does 4 go into 2 it 08:12:21.240 --> 08:12:23.868 align:start position:0% us a remainder of 2 does 4 go into 2 it does<08:12:21.420> not<08:12:21.660> so<08:12:22.260> that<08:12:22.500> leaves<08:12:22.740> us<08:12:22.860> with<08:12:22.978> zero<08:12:23.398> we 08:12:23.868 --> 08:12:23.878 align:start position:0% does not so that leaves us with zero we 08:12:23.878 --> 08:12:25.910 align:start position:0% does not so that leaves us with zero we still<08:12:24.000> have<08:12:24.180> our<08:12:24.420> two<08:12:24.600> does<08:12:25.260> two<08:12:25.440> go<08:12:25.620> into<08:12:25.680> 2 08:12:25.910 --> 08:12:25.920 align:start position:0% still have our two does two go into 2 08:12:25.920 --> 08:12:27.708 align:start position:0% still have our two does two go into 2 yep<08:12:26.340> and<08:12:26.820> then<08:12:26.878> do<08:12:27.058> we<08:12:27.180> have<08:12:27.298> anything<08:12:27.478> left 08:12:27.708 --> 08:12:27.718 align:start position:0% yep and then do we have anything left 08:12:27.718 --> 08:12:30.230 align:start position:0% yep and then do we have anything left over<08:12:27.898> nope<08:12:28.378> we're<08:12:28.558> at<08:12:28.680> zero<08:12:29.100> now<08:12:29.218> so<08:12:29.878> we<08:12:30.120> have 08:12:30.230 --> 08:12:30.240 align:start position:0% over nope we're at zero now so we have 08:12:30.240 --> 08:12:32.930 align:start position:0% over nope we're at zero now so we have zero<08:12:30.718> if<08:12:31.260> we<08:12:31.440> now<08:12:31.620> add<08:12:31.860> all<08:12:32.040> those<08:12:32.218> up<08:12:32.398> this<08:12:32.820> is 08:12:32.930 --> 08:12:32.940 align:start position:0% zero if we now add all those up this is 08:12:32.940 --> 08:12:35.990 align:start position:0% zero if we now add all those up this is our<08:12:33.180> binary<08:12:33.540> number<08:12:33.840> one<08:12:34.378> one<08:12:34.798> zero<08:12:35.458> one<08:12:35.638> one 08:12:35.990 --> 08:12:36.000 align:start position:0% our binary number one one zero one one 08:12:36.000 --> 08:12:39.650 align:start position:0% our binary number one one zero one one zero<08:12:36.718> one<08:12:37.320> zero<08:12:38.218> now<08:12:38.878> while<08:12:39.058> this<08:12:39.240> might<08:12:39.420> seem 08:12:39.650 --> 08:12:39.660 align:start position:0% zero one zero now while this might seem 08:12:39.660 --> 08:12:42.288 align:start position:0% zero one zero now while this might seem like<08:12:39.840> a<08:12:40.138> fairly<08:12:40.500> long<08:12:40.920> process<08:12:41.520> it's 08:12:42.288 --> 08:12:42.298 align:start position:0% like a fairly long process it's 08:12:42.298 --> 08:12:44.510 align:start position:0% like a fairly long process it's important<08:12:42.718> to<08:12:42.898> understand<08:12:43.020> how<08:12:43.798> this<08:12:44.040> works 08:12:44.510 --> 08:12:44.520 align:start position:0% important to understand how this works 08:12:44.520 --> 08:12:47.150 align:start position:0% important to understand how this works because<08:12:45.000> when<08:12:45.420> we<08:12:45.540> get<08:12:45.660> into<08:12:45.840> subnetting<08:12:46.620> it's 08:12:47.150 --> 08:12:47.160 align:start position:0% because when we get into subnetting it's 08:12:47.160 --> 08:12:49.368 align:start position:0% because when we get into subnetting it's really<08:12:47.458> going<08:12:47.700> to<08:12:47.820> become<08:12:48.058> important<08:12:48.600> so<08:12:49.138> we 08:12:49.368 --> 08:12:49.378 align:start position:0% really going to become important so we 08:12:49.378 --> 08:12:50.810 align:start position:0% really going to become important so we can<08:12:49.500> have<08:12:49.798> a<08:12:50.040> better<08:12:50.100> understanding<08:12:50.638> of 08:12:50.810 --> 08:12:50.820 align:start position:0% can have a better understanding of 08:12:50.820 --> 08:12:53.990 align:start position:0% can have a better understanding of networking<08:12:51.360> in<08:12:51.600> general 08:12:53.990 --> 08:12:54.000 align:start position:0% 08:12:54.000 --> 08:12:56.448 align:start position:0% so<08:12:54.718> just<08:12:55.200> to<08:12:55.378> recap<08:12:55.620> everything<08:12:55.860> we've<08:12:56.218> talked 08:12:56.448 --> 08:12:56.458 align:start position:0% so just to recap everything we've talked 08:12:56.458 --> 08:12:58.788 align:start position:0% so just to recap everything we've talked about<08:12:56.580> we<08:12:57.360> described<08:12:57.780> these<08:12:58.200> protocols<08:12:58.680> in 08:12:58.788 --> 08:12:58.798 align:start position:0% about we described these protocols in 08:12:58.798 --> 08:13:02.208 align:start position:0% about we described these protocols in the<08:12:58.920> tcpip<08:12:59.580> suite<08:13:00.180> first<08:13:00.840> TCP<08:13:01.620> transmission 08:13:02.208 --> 08:13:02.218 align:start position:0% the tcpip suite first TCP transmission 08:13:02.218 --> 08:13:05.448 align:start position:0% the tcpip suite first TCP transmission control<08:13:02.700> and<08:13:03.180> IP<08:13:03.540> Internet<08:13:03.780> Protocol<08:13:04.320> one<08:13:05.280> is 08:13:05.448 --> 08:13:05.458 align:start position:0% control and IP Internet Protocol one is 08:13:05.458 --> 08:13:10.548 align:start position:0% control and IP Internet Protocol one is connection<08:13:05.760> oriented 08:13:10.548 --> 08:13:10.558 align:start position:0% 08:13:10.558 --> 08:13:15.048 align:start position:0% and<08:13:10.920> the<08:13:11.040> other<08:13:11.160> is 08:13:15.048 --> 08:13:15.058 align:start position:0% 08:13:15.058 --> 08:13:16.788 align:start position:0% connection<08:13:15.420> less 08:13:16.788 --> 08:13:16.798 align:start position:0% connection less 08:13:16.798 --> 08:13:18.288 align:start position:0% connection less meaning<08:13:17.280> that<08:13:17.520> it<08:13:17.638> just<08:13:17.760> is<08:13:17.878> worried<08:13:18.180> about 08:13:18.288 --> 08:13:18.298 align:start position:0% meaning that it just is worried about 08:13:18.298 --> 08:13:20.810 align:start position:0% meaning that it just is worried about delivery<08:13:18.958> remember<08:13:19.500> IP<08:13:20.160> is<08:13:20.398> what<08:13:20.638> is 08:13:20.810 --> 08:13:20.820 align:start position:0% delivery remember IP is what is 08:13:20.820 --> 08:13:25.368 align:start position:0% delivery remember IP is what is responsible<08:13:21.420> for<08:13:22.200> that<08:13:22.378> IP<08:13:22.798> addressing 08:13:25.368 --> 08:13:25.378 align:start position:0% responsible for that IP addressing 08:13:25.378 --> 08:13:28.010 align:start position:0% responsible for that IP addressing UDP<08:13:25.740> is<08:13:25.978> also<08:13:26.280> connection<08:13:26.580> less 08:13:28.010 --> 08:13:28.020 align:start position:0% UDP is also connection less 08:13:28.020 --> 08:13:31.968 align:start position:0% UDP is also connection less similar<08:13:28.798> in<08:13:29.580> some<08:13:29.700> ways<08:13:29.940> to<08:13:30.120> TCP<08:13:30.840> but<08:13:31.558> it's<08:13:31.740> not 08:13:31.968 --> 08:13:31.978 align:start position:0% similar in some ways to TCP but it's not 08:13:31.978 --> 08:13:34.190 align:start position:0% similar in some ways to TCP but it's not connection<08:13:32.218> oriented 08:13:34.190 --> 08:13:34.200 align:start position:0% connection oriented 08:13:34.200 --> 08:13:36.770 align:start position:0% connection oriented then<08:13:34.558> we<08:13:34.740> had<08:13:34.860> ARP<08:13:35.340> and<08:13:35.458> reverse<08:13:35.820> ARP<08:13:36.298> address 08:13:36.770 --> 08:13:36.780 align:start position:0% then we had ARP and reverse ARP address 08:13:36.780 --> 08:13:40.128 align:start position:0% then we had ARP and reverse ARP address resolution<08:13:37.378> protocol<08:13:38.000> which<08:13:39.000> job<08:13:39.360> is<08:13:39.600> to<08:13:39.958> map 08:13:40.128 --> 08:13:40.138 align:start position:0% resolution protocol which job is to map 08:13:40.138 --> 08:13:43.010 align:start position:0% resolution protocol which job is to map IP<08:13:41.100> addresses 08:13:43.010 --> 08:13:43.020 align:start position:0% IP addresses 08:13:43.020 --> 08:13:44.750 align:start position:0% IP addresses to<08:13:43.260> Mac<08:13:43.500> addresses 08:13:44.750 --> 08:13:44.760 align:start position:0% to Mac addresses 08:13:44.760 --> 08:13:47.810 align:start position:0% to Mac addresses we<08:13:45.058> talked<08:13:45.298> about<08:13:45.558> icmp<08:13:46.558> which<08:13:47.218> is<08:13:47.398> what<08:13:47.638> we 08:13:47.810 --> 08:13:47.820 align:start position:0% we talked about icmp which is what we 08:13:47.820 --> 08:13:48.708 align:start position:0% we talked about icmp which is what we use 08:13:48.708 --> 08:13:48.718 align:start position:0% use 08:13:48.718 --> 08:13:50.868 align:start position:0% use when<08:13:49.200> we're<08:13:49.320> dealing<08:13:49.620> with<08:13:49.920> the<08:13:50.160> status<08:13:50.340> of<08:13:50.700> a 08:13:50.868 --> 08:13:50.878 align:start position:0% when we're dealing with the status of a 08:13:50.878 --> 08:13:52.490 align:start position:0% when we're dealing with the status of a system 08:13:52.490 --> 08:13:52.500 align:start position:0% system 08:13:52.500 --> 08:13:55.850 align:start position:0% system internet<08:13:53.100> control<08:13:53.760> message<08:13:54.540> protocol 08:13:55.850 --> 08:13:55.860 align:start position:0% internet control message protocol 08:13:55.860 --> 08:13:59.448 align:start position:0% internet control message protocol and<08:13:56.340> then<08:13:56.458> we<08:13:56.638> talk<08:13:56.878> about<08:13:57.500> igmp<08:13:58.500> the<08:13:59.340> internet 08:13:59.448 --> 08:13:59.458 align:start position:0% and then we talk about igmp the internet 08:13:59.458 --> 08:14:03.230 align:start position:0% and then we talk about igmp the internet group<08:13:59.940> management<08:14:00.780> protocol<08:14:01.700> which<08:14:02.700> is<08:14:03.000> more 08:14:03.230 --> 08:14:03.240 align:start position:0% group management protocol which is more 08:14:03.240 --> 08:14:06.830 align:start position:0% group management protocol which is more dealing<08:14:03.660> with<08:14:04.320> multicast<08:14:04.978> groups 08:14:06.830 --> 08:14:06.840 align:start position:0% dealing with multicast groups 08:14:06.840 --> 08:14:09.230 align:start position:0% dealing with multicast groups we<08:14:07.200> then<08:14:07.320> talked<08:14:07.740> very<08:14:08.040> briefly<08:14:08.398> about<08:14:08.580> the<08:14:08.940> IP 08:14:09.230 --> 08:14:09.240 align:start position:0% we then talked very briefly about the IP 08:14:09.240 --> 08:14:11.270 align:start position:0% we then talked very briefly about the IP packet<08:14:09.718> delivery<08:14:10.080> process<08:14:10.440> which<08:14:10.860> was<08:14:10.978> pretty 08:14:11.270 --> 08:14:11.280 align:start position:0% packet delivery process which was pretty 08:14:11.280 --> 08:14:15.410 align:start position:0% packet delivery process which was pretty simple<08:14:11.540> right<08:14:12.540> it's<08:14:13.020> packaged<08:14:13.680> it's<08:14:14.458> sent<08:14:14.700> we 08:14:15.410 --> 08:14:15.420 align:start position:0% simple right it's packaged it's sent we 08:14:15.420 --> 08:14:17.868 align:start position:0% simple right it's packaged it's sent we determine<08:14:15.840> where<08:14:16.138> it<08:14:16.320> needs<08:14:16.558> to<08:14:16.680> go<08:14:16.920> once<08:14:17.820> it's 08:14:17.868 --> 08:14:17.878 align:start position:0% determine where it needs to go once it's 08:14:17.878 --> 08:14:19.610 align:start position:0% determine where it needs to go once it's determined<08:14:18.298> where<08:14:18.420> it<08:14:18.540> needs<08:14:18.718> to<08:14:18.840> go<08:14:18.958> it's 08:14:19.610 --> 08:14:19.620 align:start position:0% determined where it needs to go it's 08:14:19.620 --> 08:14:20.750 align:start position:0% determined where it needs to go it's sent<08:14:19.798> there 08:14:20.750 --> 08:14:20.760 align:start position:0% sent there 08:14:20.760 --> 08:14:23.330 align:start position:0% sent there finally<08:14:21.420> we<08:14:22.080> explained<08:14:22.558> the<08:14:22.920> binary 08:14:23.330 --> 08:14:23.340 align:start position:0% finally we explained the binary 08:14:23.340 --> 08:14:25.310 align:start position:0% finally we explained the binary conversion<08:14:24.000> which<08:14:24.660> is<08:14:24.780> going<08:14:24.898> to<08:14:25.020> be<08:14:25.080> really 08:14:25.310 --> 08:14:25.320 align:start position:0% conversion which is going to be really 08:14:25.320 --> 08:14:27.650 align:start position:0% conversion which is going to be really important<08:14:25.680> for<08:14:25.920> IP<08:14:26.218> addressing<08:14:26.760> including 08:14:27.650 --> 08:14:27.660 align:start position:0% important for IP addressing including 08:14:27.660 --> 08:14:29.690 align:start position:0% important for IP addressing including how<08:14:27.898> to<08:14:28.020> go<08:14:28.200> from<08:14:28.500> binary 08:14:29.690 --> 08:14:29.700 align:start position:0% how to go from binary 08:14:29.700 --> 08:14:34.910 align:start position:0% how to go from binary which<08:14:30.360> is<08:14:30.600> a<08:14:31.320> base<08:14:32.520> 2<08:14:33.058> system 08:14:34.910 --> 08:14:34.920 align:start position:0% which is a base 2 system 08:14:34.920 --> 08:14:38.448 align:start position:0% which is a base 2 system to<08:14:35.520> decimal 08:14:38.448 --> 08:14:38.458 align:start position:0% 08:14:38.458 --> 08:14:41.810 align:start position:0% which<08:14:38.820> is<08:14:38.940> a<08:14:39.180> base<08:14:39.360> 10<08:14:40.320> system 08:14:41.810 --> 08:14:41.820 align:start position:0% which is a base 10 system 08:14:41.820 --> 08:14:47.020 align:start position:0% which is a base 10 system and<08:14:42.298> Back<08:14:42.540> Again 08:14:47.020 --> 08:14:47.030 align:start position:0% 08:14:47.030 --> 08:15:08.810 align:start position:0% [Music] 08:15:08.810 --> 08:15:08.820 align:start position:0% 08:15:08.820 --> 08:15:12.110 align:start position:0% Network<08:15:09.360> routing<08:15:09.958> and<08:15:10.080> IP<08:15:10.378> addressing<08:15:11.120> IP 08:15:12.110 --> 08:15:12.120 align:start position:0% Network routing and IP addressing IP 08:15:12.120 --> 08:15:14.930 align:start position:0% Network routing and IP addressing IP addresses<08:15:12.718> and<08:15:13.200> subnetting 08:15:14.930 --> 08:15:14.940 align:start position:0% addresses and subnetting 08:15:14.940 --> 08:15:17.448 align:start position:0% addresses and subnetting so<08:15:15.420> having<08:15:15.600> discussed<08:15:16.260> IP<08:15:16.740> addressing<08:15:17.218> and 08:15:17.448 --> 08:15:17.458 align:start position:0% so having discussed IP addressing and 08:15:17.458 --> 08:15:19.910 align:start position:0% so having discussed IP addressing and routing<08:15:17.878> in<08:15:18.420> general<08:15:18.600> we're<08:15:19.378> now<08:15:19.558> going<08:15:19.740> to 08:15:19.910 --> 08:15:19.920 align:start position:0% routing in general we're now going to 08:15:19.920 --> 08:15:22.788 align:start position:0% routing in general we're now going to further<08:15:20.218> examine<08:15:20.820> IP<08:15:21.540> addressing<08:15:22.080> and<08:15:22.680> the 08:15:22.788 --> 08:15:22.798 align:start position:0% further examine IP addressing and the 08:15:22.798 --> 08:15:25.128 align:start position:0% further examine IP addressing and the methods<08:15:23.280> of<08:15:23.580> logically<08:15:24.120> not<08:15:24.660> physically 08:15:25.128 --> 08:15:25.138 align:start position:0% methods of logically not physically 08:15:25.138 --> 08:15:28.368 align:start position:0% methods of logically not physically dividing<08:15:26.040> up<08:15:26.218> our<08:15:26.458> networks<08:15:26.940> this<08:15:27.660> way<08:15:27.840> we<08:15:28.260> can 08:15:28.368 --> 08:15:28.378 align:start position:0% dividing up our networks this way we can 08:15:28.378 --> 08:15:30.650 align:start position:0% dividing up our networks this way we can keep<08:15:28.620> not<08:15:29.040> only<08:15:29.160> better<08:15:29.700> track<08:15:30.058> of<08:15:30.360> all<08:15:30.478> the 08:15:30.650 --> 08:15:30.660 align:start position:0% keep not only better track of all the 08:15:30.660 --> 08:15:32.750 align:start position:0% keep not only better track of all the devices<08:15:30.898> on<08:15:31.200> the<08:15:31.320> network<08:15:31.440> but<08:15:31.978> also<08:15:32.218> organize 08:15:32.750 --> 08:15:32.760 align:start position:0% devices on the network but also organize 08:15:32.760 --> 08:15:35.990 align:start position:0% devices on the network but also organize them<08:15:33.000> for<08:15:33.898> security<08:15:34.520> performance<08:15:35.520> and<08:15:35.820> other 08:15:35.990 --> 08:15:36.000 align:start position:0% them for security performance and other 08:15:36.000 --> 08:15:38.510 align:start position:0% them for security performance and other reasons<08:15:36.958> after<08:15:37.378> we<08:15:37.558> complete<08:15:37.920> this<08:15:38.160> module 08:15:38.510 --> 08:15:38.520 align:start position:0% reasons after we complete this module 08:15:38.520 --> 08:15:39.288 align:start position:0% reasons after we complete this module we're<08:15:38.760> going<08:15:38.878> to<08:15:38.940> have<08:15:39.058> a<08:15:39.180> better 08:15:39.288 --> 08:15:39.298 align:start position:0% we're going to have a better 08:15:39.298 --> 08:15:41.690 align:start position:0% we're going to have a better understanding<08:15:39.958> of<08:15:40.500> how<08:15:40.740> our<08:15:40.920> network<08:15:41.160> devices 08:15:41.690 --> 08:15:41.700 align:start position:0% understanding of how our network devices 08:15:41.700 --> 08:15:45.888 align:start position:0% understanding of how our network devices are<08:15:42.420> identified<08:15:42.840> both<08:15:43.798> by<08:15:44.280> other<08:15:44.458> devices<08:15:44.898> and 08:15:45.888 --> 08:15:45.898 align:start position:0% are identified both by other devices and 08:15:45.898 --> 08:15:48.230 align:start position:0% are identified both by other devices and by<08:15:46.320> individuals<08:15:46.860> such<08:15:47.160> as<08:15:47.280> ourselves<08:15:47.700> since 08:15:48.230 --> 08:15:48.240 align:start position:0% by individuals such as ourselves since 08:15:48.240 --> 08:15:49.670 align:start position:0% by individuals such as ourselves since we're<08:15:48.420> not<08:15:48.600> computers 08:15:49.670 --> 08:15:49.680 align:start position:0% we're not computers 08:15:49.680 --> 08:15:53.150 align:start position:0% we're not computers so<08:15:50.398> first<08:15:50.760> we're<08:15:51.420> going<08:15:51.600> to<08:15:51.840> identify<08:15:52.378> what<08:15:52.920> a 08:15:53.150 --> 08:15:53.160 align:start position:0% so first we're going to identify what a 08:15:53.160 --> 08:15:56.330 align:start position:0% so first we're going to identify what a network<08:15:53.340> address<08:15:53.760> is<08:15:54.180> versus<08:15:55.020> a<08:15:55.740> network<08:15:55.920> name 08:15:56.330 --> 08:15:56.340 align:start position:0% network address is versus a network name 08:15:56.340 --> 08:15:58.910 align:start position:0% network address is versus a network name one<08:15:57.000> the<08:15:57.360> network<08:15:57.600> address<08:15:57.958> is<08:15:58.558> for<08:15:58.740> other 08:15:58.910 --> 08:15:58.920 align:start position:0% one the network address is for other 08:15:58.920 --> 08:16:01.910 align:start position:0% one the network address is for other devices<08:15:59.340> a<08:16:00.180> network<08:16:00.360> name<08:16:00.780> is<08:16:01.200> really<08:16:01.440> for<08:16:01.740> us 08:16:01.910 --> 08:16:01.920 align:start position:0% devices a network name is really for us 08:16:01.920 --> 08:16:03.530 align:start position:0% devices a network name is really for us since<08:16:02.340> it<08:16:02.520> would<08:16:02.638> be<08:16:02.760> difficult<08:16:02.940> for<08:16:03.240> us<08:16:03.360> to 08:16:03.530 --> 08:16:03.540 align:start position:0% since it would be difficult for us to 08:16:03.540 --> 08:16:05.750 align:start position:0% since it would be difficult for us to remember<08:16:03.660> all<08:16:04.020> these<08:16:04.260> numbers<08:16:04.500> much<08:16:05.458> like 08:16:05.750 --> 08:16:05.760 align:start position:0% remember all these numbers much like 08:16:05.760 --> 08:16:08.628 align:start position:0% remember all these numbers much like using<08:16:06.360> a<08:16:06.540> phone<08:16:06.718> number<08:16:06.958> and<08:16:07.440> a<08:16:07.620> cell<08:16:07.740> phone 08:16:08.628 --> 08:16:08.638 align:start position:0% using a phone number and a cell phone 08:16:08.638 --> 08:16:12.368 align:start position:0% using a phone number and a cell phone next<08:16:09.298> we're<08:16:09.898> going<08:16:10.080> to<08:16:10.260> describe<08:16:10.740> the<08:16:11.240> ipv4 08:16:12.368 --> 08:16:12.378 align:start position:0% next we're going to describe the ipv4 08:16:12.378 --> 08:16:16.788 align:start position:0% next we're going to describe the ipv4 addressing<08:16:13.378> scheme<08:16:13.798> and<08:16:15.080> ipv4<08:16:16.080> is<08:16:16.320> important 08:16:16.788 --> 08:16:16.798 align:start position:0% addressing scheme and ipv4 is important 08:16:16.798 --> 08:16:19.490 align:start position:0% addressing scheme and ipv4 is important to<08:16:16.920> know<08:16:17.398> because<08:16:17.878> even<08:16:18.660> though<08:16:18.898> we<08:16:19.200> have<08:16:19.320> a 08:16:19.490 --> 08:16:19.500 align:start position:0% to know because even though we have a 08:16:19.500 --> 08:16:22.490 align:start position:0% to know because even though we have a newer<08:16:19.740> version<08:16:19.798> IPv6<08:16:20.840> ipv4<08:16:21.840> is<08:16:22.200> still 08:16:22.490 --> 08:16:22.500 align:start position:0% newer version IPv6 ipv4 is still 08:16:22.500 --> 08:16:25.070 align:start position:0% newer version IPv6 ipv4 is still deployed<08:16:23.458> in<08:16:23.760> most<08:16:23.878> situations<08:16:24.420> and<08:16:24.898> it's 08:16:25.070 --> 08:16:25.080 align:start position:0% deployed in most situations and it's 08:16:25.080 --> 08:16:26.990 align:start position:0% deployed in most situations and it's covered<08:16:25.500> to<08:16:25.798> the<08:16:25.978> most<08:16:26.160> extent<08:16:26.520> on<08:16:26.820> network 08:16:26.990 --> 08:16:27.000 align:start position:0% covered to the most extent on network 08:16:27.000 --> 08:16:29.448 align:start position:0% covered to the most extent on network plus<08:16:27.360> when<08:16:27.958> we<08:16:28.080> get<08:16:28.200> to<08:16:28.320> IPv6<08:16:28.920> which<08:16:29.340> is 08:16:29.448 --> 08:16:29.458 align:start position:0% plus when we get to IPv6 which is 08:16:29.458 --> 08:16:31.670 align:start position:0% plus when we get to IPv6 which is different<08:16:29.638> version<08:16:30.120> six<08:16:30.540> there<08:16:31.320> are<08:16:31.440> a<08:16:31.500> lot<08:16:31.558> of 08:16:31.670 --> 08:16:31.680 align:start position:0% different version six there are a lot of 08:16:31.680 --> 08:16:33.170 align:start position:0% different version six there are a lot of benefits<08:16:31.978> then<08:16:32.218> we'll<08:16:32.458> describe<08:16:32.820> it<08:16:32.940> later 08:16:33.170 --> 08:16:33.180 align:start position:0% benefits then we'll describe it later 08:16:33.180 --> 08:16:36.530 align:start position:0% benefits then we'll describe it later but<08:16:33.718> really<08:16:34.020> understanding<08:16:34.620> ipv4<08:16:35.520> is<08:16:36.240> really 08:16:36.530 --> 08:16:36.540 align:start position:0% but really understanding ipv4 is really 08:16:36.540 --> 08:16:38.388 align:start position:0% but really understanding ipv4 is really important<08:16:36.958> after<08:16:37.558> we<08:16:37.798> take<08:16:37.978> a<08:16:38.040> look<08:16:38.160> at<08:16:38.280> that 08:16:38.388 --> 08:16:38.398 align:start position:0% important after we take a look at that 08:16:38.398 --> 08:16:40.730 align:start position:0% important after we take a look at that we're<08:16:38.638> going<08:16:38.760> to<08:16:38.878> look<08:16:39.058> at<08:16:39.420> subnetting<08:16:40.260> and<08:16:40.558> a 08:16:40.730 --> 08:16:40.740 align:start position:0% we're going to look at subnetting and a 08:16:40.740 --> 08:16:43.850 align:start position:0% we're going to look at subnetting and a subnet<08:16:41.160> mask<08:16:41.458> you<08:16:42.180> might<08:16:42.240> have<08:16:42.420> seen<08:16:42.718> this<08:16:43.020> and 08:16:43.850 --> 08:16:43.860 align:start position:0% subnet mask you might have seen this and 08:16:43.860 --> 08:16:46.070 align:start position:0% subnet mask you might have seen this and these<08:16:44.520> are<08:16:44.638> the<08:16:44.760> numbers<08:16:44.940> and<08:16:45.420> we've<08:16:45.780> probably 08:16:46.070 --> 08:16:46.080 align:start position:0% these are the numbers and we've probably 08:16:46.080 --> 08:16:50.410 align:start position:0% these are the numbers and we've probably mentioned<08:16:46.558> to<08:16:46.680> them<08:16:46.860> in<08:16:47.040> the<08:16:47.160> past<08:16:47.340> such<08:16:47.940> as 08:16:50.410 --> 08:16:50.420 align:start position:0% 08:16:50.420 --> 08:16:53.150 align:start position:0% 255.255.0.0<08:16:51.420> and<08:16:51.718> so<08:16:51.898> on<08:16:52.080> and<08:16:52.260> so<08:16:52.440> forth<08:16:52.740> and 08:16:53.150 --> 08:16:53.160 align:start position:0% 255.255.0.0 and so on and so forth and 08:16:53.160 --> 08:16:54.948 align:start position:0% 255.255.0.0 and so on and so forth and we're<08:16:53.340> going<08:16:53.458> to<08:16:53.520> describe<08:16:53.940> how<08:16:54.298> this<08:16:54.540> allows 08:16:54.948 --> 08:16:54.958 align:start position:0% we're going to describe how this allows 08:16:54.958 --> 08:16:57.948 align:start position:0% we're going to describe how this allows us<08:16:55.080> to<08:16:55.440> separate<08:16:55.920> out<08:16:56.100> the<08:16:56.760> network<08:16:56.940> ID<08:16:57.298> from 08:16:57.948 --> 08:16:57.958 align:start position:0% us to separate out the network ID from 08:16:57.958 --> 08:17:00.770 align:start position:0% us to separate out the network ID from the<08:16:58.080> node<08:16:58.260> ID<08:16:58.500> or<08:16:59.218> the<08:16:59.580> device's<08:17:00.120> ID<08:17:00.360> or 08:17:00.770 --> 08:17:00.780 align:start position:0% the node ID or the device's ID or 08:17:00.780 --> 08:17:03.888 align:start position:0% the node ID or the device's ID or address<08:17:01.020> from<08:17:01.978> the<08:17:02.340> networks<08:17:03.120> address<08:17:03.360> much 08:17:03.888 --> 08:17:03.898 align:start position:0% address from the networks address much 08:17:03.898 --> 08:17:06.110 align:start position:0% address from the networks address much like<08:17:04.138> our<08:17:04.500> ZIP<08:17:04.680> code<08:17:04.920> versus<08:17:05.458> our<08:17:05.878> street 08:17:06.110 --> 08:17:06.120 align:start position:0% like our ZIP code versus our street 08:17:06.120 --> 08:17:08.570 align:start position:0% like our ZIP code versus our street address<08:17:06.540> after<08:17:07.500> that<08:17:07.740> we're<08:17:07.920> gonna<08:17:08.040> just 08:17:08.570 --> 08:17:08.580 align:start position:0% address after that we're gonna just 08:17:08.580 --> 08:17:11.628 align:start position:0% address after that we're gonna just describe<08:17:09.298> the<08:17:09.780> rules<08:17:10.138> of<08:17:10.440> subnet<08:17:10.860> masks<08:17:11.280> and 08:17:11.628 --> 08:17:11.638 align:start position:0% describe the rules of subnet masks and 08:17:11.638 --> 08:17:14.448 align:start position:0% describe the rules of subnet masks and their<08:17:11.760> IP<08:17:12.058> addresses<08:17:12.600> and<08:17:13.138> knowing<08:17:13.620> binary<08:17:14.160> is 08:17:14.448 --> 08:17:14.458 align:start position:0% their IP addresses and knowing binary is 08:17:14.458 --> 08:17:16.610 align:start position:0% their IP addresses and knowing binary is really<08:17:14.760> going<08:17:15.000> to<08:17:15.180> help<08:17:15.298> us<08:17:15.478> understand<08:17:15.958> all 08:17:16.610 --> 08:17:16.620 align:start position:0% really going to help us understand all 08:17:16.620 --> 08:17:17.990 align:start position:0% really going to help us understand all of<08:17:16.798> this<08:17:17.040> stuff 08:17:17.990 --> 08:17:18.000 align:start position:0% of this stuff 08:17:18.000 --> 08:17:21.590 align:start position:0% of this stuff after<08:17:18.360> that<08:17:18.600> we're<08:17:18.898> going<08:17:19.138> to<08:17:19.878> apply<08:17:20.878> a<08:17:21.240> subnet 08:17:21.590 --> 08:17:21.600 align:start position:0% after that we're going to apply a subnet 08:17:21.600 --> 08:17:23.930 align:start position:0% after that we're going to apply a subnet mask<08:17:21.840> to<08:17:22.260> an<08:17:22.440> IP<08:17:22.680> address<08:17:22.860> using<08:17:23.638> something 08:17:23.930 --> 08:17:23.940 align:start position:0% mask to an IP address using something 08:17:23.940 --> 08:17:26.628 align:start position:0% mask to an IP address using something called<08:17:24.420> anding<08:17:25.320> which<08:17:25.620> again<08:17:25.740> gets<08:17:26.218> back<08:17:26.398> to 08:17:26.628 --> 08:17:26.638 align:start position:0% called anding which again gets back to 08:17:26.638 --> 08:17:28.730 align:start position:0% called anding which again gets back to Binary<08:17:27.180> and<08:17:27.840> might<08:17:28.080> even<08:17:28.200> remind<08:17:28.440> you<08:17:28.620> of 08:17:28.730 --> 08:17:28.740 align:start position:0% Binary and might even remind you of 08:17:28.740 --> 08:17:30.070 align:start position:0% Binary and might even remind you of something<08:17:28.920> you<08:17:29.160> learned<08:17:29.458> in<08:17:29.638> high<08:17:29.878> school 08:17:30.070 --> 08:17:30.080 align:start position:0% something you learned in high school 08:17:30.080 --> 08:17:32.690 align:start position:0% something you learned in high school this<08:17:31.080> ending<08:17:31.558> principle<08:17:31.978> which<08:17:32.398> is<08:17:32.520> really 08:17:32.690 --> 08:17:32.700 align:start position:0% this ending principle which is really 08:17:32.700 --> 08:17:34.430 align:start position:0% this ending principle which is really going<08:17:32.820> to<08:17:33.000> come<08:17:33.058> in<08:17:33.240> handy<08:17:33.540> again<08:17:34.020> this<08:17:34.320> is 08:17:34.430 --> 08:17:34.440 align:start position:0% going to come in handy again this is 08:17:34.440 --> 08:17:35.810 align:start position:0% going to come in handy again this is something<08:17:34.620> that<08:17:34.860> we<08:17:35.040> only<08:17:35.160> have<08:17:35.340> to<08:17:35.458> do<08:17:35.638> now 08:17:35.810 --> 08:17:35.820 align:start position:0% something that we only have to do now 08:17:35.820 --> 08:17:39.288 align:start position:0% something that we only have to do now with<08:17:36.000> ipv4<08:17:36.660> IPv6<08:17:37.500> doesn't<08:17:38.040> have<08:17:38.340> to<08:17:38.520> do<08:17:38.638> it<08:17:38.820> and 08:17:39.288 --> 08:17:39.298 align:start position:0% with ipv4 IPv6 doesn't have to do it and 08:17:39.298 --> 08:17:41.270 align:start position:0% with ipv4 IPv6 doesn't have to do it and we'll<08:17:39.478> describe<08:17:39.958> why<08:17:40.200> finally<08:17:40.920> we're<08:17:41.160> going 08:17:41.270 --> 08:17:41.280 align:start position:0% we'll describe why finally we're going 08:17:41.280 --> 08:17:42.948 align:start position:0% we'll describe why finally we're going to<08:17:41.398> take<08:17:41.520> a<08:17:41.638> look<08:17:41.700> at<08:17:41.878> what<08:17:42.120> are<08:17:42.240> called<08:17:42.420> custom 08:17:42.948 --> 08:17:42.958 align:start position:0% to take a look at what are called custom 08:17:42.958 --> 08:17:44.930 align:start position:0% to take a look at what are called custom subnet<08:17:43.680> masks<08:17:44.160> which<08:17:44.580> are<08:17:44.700> slightly 08:17:44.930 --> 08:17:44.940 align:start position:0% subnet masks which are slightly 08:17:44.940 --> 08:17:47.030 align:start position:0% subnet masks which are slightly different<08:17:45.120> from<08:17:45.600> these<08:17:46.200> default<08:17:46.558> ones<08:17:46.860> the 08:17:47.030 --> 08:17:47.040 align:start position:0% different from these default ones the 08:17:47.040 --> 08:17:51.350 align:start position:0% different from these default ones the 255<08:17:47.580> to<08:17:47.820> 255<08:17:48.298> to<08:17:48.478> 255s<08:17:49.320> and<08:17:49.740> so<08:17:49.860> on<08:17:50.520> so<08:17:51.058> having 08:17:51.350 --> 08:17:51.360 align:start position:0% 255 to 255 to 255s and so on so having 08:17:51.360 --> 08:17:53.090 align:start position:0% 255 to 255 to 255s and so on so having said<08:17:51.600> all<08:17:51.780> that<08:17:51.898> let's<08:17:52.080> get<08:17:52.440> into<08:17:52.620> it<08:17:52.860> by 08:17:53.090 --> 08:17:53.100 align:start position:0% said all that let's get into it by 08:17:53.100 --> 08:17:55.910 align:start position:0% said all that let's get into it by looking<08:17:53.280> at<08:17:53.580> Network<08:17:53.940> addresses<08:17:54.718> and<08:17:55.080> names 08:17:55.910 --> 08:17:55.920 align:start position:0% looking at Network addresses and names 08:17:55.920 --> 08:17:58.250 align:start position:0% looking at Network addresses and names so<08:17:56.340> let's<08:17:56.520> begin<08:17:56.760> by<08:17:57.180> looking<08:17:57.360> at<08:17:57.660> how<08:17:57.898> nodes 08:17:58.250 --> 08:17:58.260 align:start position:0% so let's begin by looking at how nodes 08:17:58.260 --> 08:18:00.830 align:start position:0% so let's begin by looking at how nodes on<08:17:58.500> a<08:17:58.680> network<08:17:58.798> are<08:17:59.458> identified<08:17:59.878> specifically 08:18:00.830 --> 08:18:00.840 align:start position:0% on a network are identified specifically 08:18:00.840 --> 08:18:03.770 align:start position:0% on a network are identified specifically on<08:18:01.138> the<08:18:01.320> Internet<08:18:01.558> or<08:18:02.520> network<08:18:02.760> layer<08:18:03.240> if<08:18:03.660> you 08:18:03.770 --> 08:18:03.780 align:start position:0% on the Internet or network layer if you 08:18:03.780 --> 08:18:07.548 align:start position:0% on the Internet or network layer if you recall<08:18:04.260> the<08:18:05.040> network 08:18:07.548 --> 08:18:07.558 align:start position:0% 08:18:07.558 --> 08:18:10.250 align:start position:0% layer 08:18:10.250 --> 08:18:10.260 align:start position:0% 08:18:10.260 --> 08:18:13.190 align:start position:0% is<08:18:10.680> layer<08:18:11.040> 3<08:18:11.218> of<08:18:11.458> The<08:18:11.580> OSI<08:18:12.000> model 08:18:13.190 --> 08:18:13.200 align:start position:0% is layer 3 of The OSI model 08:18:13.200 --> 08:18:16.548 align:start position:0% is layer 3 of The OSI model and<08:18:13.798> the<08:18:13.978> internet<08:18:14.160> layer 08:18:16.548 --> 08:18:16.558 align:start position:0% and the internet layer 08:18:16.558 --> 08:18:23.110 align:start position:0% and the internet layer is<08:18:17.280> layer<08:18:17.878> 2<08:18:18.478> of<08:18:19.260> the<08:18:19.500> tcpip<08:18:20.280> model 08:18:23.110 --> 08:18:23.120 align:start position:0% 08:18:23.120 --> 08:18:26.690 align:start position:0% so<08:18:24.120> to<08:18:24.240> begin<08:18:24.420> a<08:18:25.020> network<08:18:25.260> address<08:18:26.040> is 08:18:26.690 --> 08:18:26.700 align:start position:0% so to begin a network address is 08:18:26.700 --> 08:18:28.430 align:start position:0% so to begin a network address is assigned<08:18:27.180> to<08:18:27.360> every<08:18:27.660> device<08:18:27.898> and<08:18:28.200> I<08:18:28.320> think 08:18:28.430 --> 08:18:28.440 align:start position:0% assigned to every device and I think 08:18:28.440 --> 08:18:30.110 align:start position:0% assigned to every device and I think we've<08:18:28.680> discussed<08:18:29.040> this<08:18:29.218> that<08:18:29.700> wants<08:18:30.058> to 08:18:30.110 --> 08:18:30.120 align:start position:0% we've discussed this that wants to 08:18:30.120 --> 08:18:32.388 align:start position:0% we've discussed this that wants to communicate<08:18:30.660> on<08:18:31.020> a<08:18:31.138> computer<08:18:31.200> network<08:18:31.558> the 08:18:32.388 --> 08:18:32.398 align:start position:0% communicate on a computer network the 08:18:32.398 --> 08:18:34.490 align:start position:0% communicate on a computer network the network<08:18:32.580> address<08:18:32.878> is<08:18:33.180> actually<08:18:33.360> made<08:18:33.600> up<08:18:33.780> of 08:18:34.490 --> 08:18:34.500 align:start position:0% network address is actually made up of 08:18:34.500 --> 08:18:38.208 align:start position:0% network address is actually made up of two<08:18:34.978> parts<08:18:35.218> the<08:18:36.120> node<08:18:36.360> portion<08:18:36.898> that<08:18:37.620> belongs 08:18:38.208 --> 08:18:38.218 align:start position:0% two parts the node portion that belongs 08:18:38.218 --> 08:18:42.230 align:start position:0% two parts the node portion that belongs to<08:18:39.080> the<08:18:40.080> specific<08:18:40.500> device<08:18:40.920> and<08:18:41.820> the<08:18:42.058> network 08:18:42.230 --> 08:18:42.240 align:start position:0% to the specific device and the network 08:18:42.240 --> 08:18:44.448 align:start position:0% to the specific device and the network portion<08:18:42.780> which<08:18:43.080> identifies<08:18:43.620> what<08:18:44.160> network 08:18:44.448 --> 08:18:44.458 align:start position:0% portion which identifies what network 08:18:44.458 --> 08:18:47.030 align:start position:0% portion which identifies what network the<08:18:44.820> device<08:18:45.000> belongs<08:18:45.600> to<08:18:45.780> I<08:18:46.440> think<08:18:46.620> I've<08:18:46.798> just 08:18:47.030 --> 08:18:47.040 align:start position:0% the device belongs to I think I've just 08:18:47.040 --> 08:18:49.670 align:start position:0% the device belongs to I think I've just described<08:18:47.458> this<08:18:47.700> as<08:18:48.540> a<08:18:48.840> zip<08:18:49.020> code<08:18:49.260> which 08:18:49.670 --> 08:18:49.680 align:start position:0% described this as a zip code which 08:18:49.680 --> 08:18:51.888 align:start position:0% described this as a zip code which describes<08:18:50.100> the<08:18:50.340> sort<08:18:50.580> of<08:18:50.700> network<08:18:51.058> or<08:18:51.718> the 08:18:51.888 --> 08:18:51.898 align:start position:0% describes the sort of network or the 08:18:51.898 --> 08:18:54.530 align:start position:0% describes the sort of network or the area<08:18:52.080> you're<08:18:52.440> in<08:18:52.620> versus<08:18:53.280> your<08:18:53.878> street<08:18:54.180> number 08:18:54.530 --> 08:18:54.540 align:start position:0% area you're in versus your street number 08:18:54.540 --> 08:18:56.510 align:start position:0% area you're in versus your street number and<08:18:55.080> your<08:18:55.260> street<08:18:55.440> address<08:18:55.740> which<08:18:56.340> is 08:18:56.510 --> 08:18:56.520 align:start position:0% and your street address which is 08:18:56.520 --> 08:18:58.968 align:start position:0% and your street address which is specific<08:18:56.878> to<08:18:57.180> where<08:18:57.478> you<08:18:57.600> live<08:18:57.840> this<08:18:58.798> address 08:18:58.968 --> 08:18:58.978 align:start position:0% specific to where you live this address 08:18:58.978 --> 08:19:01.490 align:start position:0% specific to where you live this address is<08:18:59.280> what<08:18:59.520> is<08:18:59.700> used<08:18:59.878> by<08:19:00.180> devices<08:19:00.660> for 08:19:01.490 --> 08:19:01.500 align:start position:0% is what is used by devices for 08:19:01.500 --> 08:19:04.368 align:start position:0% is what is used by devices for identification<08:19:02.420> and<08:19:03.420> as<08:19:03.660> it's<08:19:03.780> only<08:19:03.958> made<08:19:04.200> up 08:19:04.368 --> 08:19:04.378 align:start position:0% identification and as it's only made up 08:19:04.378 --> 08:19:07.968 align:start position:0% identification and as it's only made up of<08:19:04.740> numbers<08:19:05.240> whereas<08:19:06.240> a<08:19:06.478> network<08:19:06.660> name<08:19:07.558> is 08:19:07.968 --> 08:19:07.978 align:start position:0% of numbers whereas a network name is 08:19:07.978 --> 08:19:09.948 align:start position:0% of numbers whereas a network name is made<08:19:08.218> up<08:19:08.458> of 08:19:09.948 --> 08:19:09.958 align:start position:0% made up of 08:19:09.958 --> 08:19:12.708 align:start position:0% made up of um<08:19:10.020> letters<08:19:10.978> and<08:19:11.218> such<08:19:11.398> the<08:19:12.000> real<08:19:12.240> reason 08:19:12.708 --> 08:19:12.718 align:start position:0% um letters and such the real reason 08:19:12.718 --> 08:19:15.650 align:start position:0% um letters and such the real reason being<08:19:13.138> readability<08:19:14.100> we<08:19:14.940> would<08:19:15.120> have<08:19:15.298> a<08:19:15.478> lot<08:19:15.540> of 08:19:15.650 --> 08:19:15.660 align:start position:0% being readability we would have a lot of 08:19:15.660 --> 08:19:17.388 align:start position:0% being readability we would have a lot of trouble<08:19:15.958> remembering<08:19:16.740> we<08:19:17.100> already<08:19:17.218> have 08:19:17.388 --> 08:19:17.398 align:start position:0% trouble remembering we already have 08:19:17.398 --> 08:19:19.490 align:start position:0% trouble remembering we already have trouble<08:19:17.580> remembering<08:19:18.058> a<08:19:18.240> phone<08:19:18.420> number<08:19:18.600> but 08:19:19.490 --> 08:19:19.500 align:start position:0% trouble remembering a phone number but 08:19:19.500 --> 08:19:21.048 align:start position:0% trouble remembering a phone number but if<08:19:19.680> you<08:19:19.798> imagine<08:19:19.920> remembering<08:19:20.638> a<08:19:20.820> whole 08:19:21.048 --> 08:19:21.058 align:start position:0% if you imagine remembering a whole 08:19:21.058 --> 08:19:22.850 align:start position:0% if you imagine remembering a whole binary<08:19:21.540> number<08:19:21.840> a<08:19:22.200> set<08:19:22.378> of<08:19:22.500> numbers<08:19:22.620> where 08:19:22.850 --> 08:19:22.860 align:start position:0% binary number a set of numbers where 08:19:22.860 --> 08:19:25.430 align:start position:0% binary number a set of numbers where there<08:19:23.340> infinite<08:19:24.298> possibilities<08:19:24.840> unless 08:19:25.430 --> 08:19:25.440 align:start position:0% there infinite possibilities unless 08:19:25.440 --> 08:19:26.810 align:start position:0% there infinite possibilities unless you're<08:19:25.558> using<08:19:25.860> it<08:19:25.978> a<08:19:26.100> lot<08:19:26.218> it's<08:19:26.398> easier<08:19:26.700> to 08:19:26.810 --> 08:19:26.820 align:start position:0% you're using it a lot it's easier to 08:19:26.820 --> 08:19:30.110 align:start position:0% you're using it a lot it's easier to remember<08:19:27.000> a<08:19:27.840> name<08:19:28.080> such<08:19:28.798> as<08:19:29.218> the<08:19:29.760> conference 08:19:30.110 --> 08:19:30.120 align:start position:0% remember a name such as the conference 08:19:30.120 --> 08:19:33.410 align:start position:0% remember a name such as the conference room<08:19:30.298> laptop<08:19:30.780> or<08:19:31.440> resource<08:19:32.340> server<08:19:32.700> one<08:19:32.878> than 08:19:33.410 --> 08:19:33.420 align:start position:0% room laptop or resource server one than 08:19:33.420 --> 08:19:35.690 align:start position:0% room laptop or resource server one than it<08:19:33.600> is<08:19:33.718> to<08:19:33.840> remember<08:19:34.020> an<08:19:34.798> IP<08:19:35.040> address<08:19:35.280> which 08:19:35.690 --> 08:19:35.700 align:start position:0% it is to remember an IP address which 08:19:35.700 --> 08:19:40.070 align:start position:0% it is to remember an IP address which might<08:19:35.878> be<08:19:36.058> something<08:19:36.240> like<08:19:36.540> 132.168.56.43 08:19:40.070 --> 08:19:40.080 align:start position:0% 08:19:40.080 --> 08:19:41.570 align:start position:0% especially<08:19:40.620> when<08:19:40.978> there<08:19:41.160> are<08:19:41.280> a<08:19:41.340> lot<08:19:41.458> more 08:19:41.570 --> 08:19:41.580 align:start position:0% especially when there are a lot more 08:19:41.580 --> 08:19:44.150 align:start position:0% especially when there are a lot more computers<08:19:42.058> involved<08:19:42.540> the<08:19:42.958> names<08:19:43.200> become<08:19:43.740> a 08:19:44.150 --> 08:19:44.160 align:start position:0% computers involved the names become a 08:19:44.160 --> 08:19:46.670 align:start position:0% computers involved the names become a lot<08:19:44.280> easier<08:19:44.638> so<08:19:45.478> the<08:19:45.718> network<08:19:45.840> named<08:19:46.378> is 08:19:46.670 --> 08:19:46.680 align:start position:0% lot easier so the network named is 08:19:46.680 --> 08:19:50.690 align:start position:0% lot easier so the network named is actually<08:19:46.920> mapped<08:19:47.820> to<08:19:48.600> the<08:19:49.558> address<08:19:49.798> or<08:19:50.100> the<08:19:50.280> IP 08:19:50.690 --> 08:19:50.700 align:start position:0% actually mapped to the address or the IP 08:19:50.700 --> 08:19:53.330 align:start position:0% actually mapped to the address or the IP address<08:19:50.940> by<08:19:51.840> one<08:19:52.080> or<08:19:52.260> another<08:19:52.558> naming 08:19:53.330 --> 08:19:53.340 align:start position:0% address by one or another naming 08:19:53.340 --> 08:19:54.770 align:start position:0% address by one or another naming services<08:19:53.700> and<08:19:54.180> some<08:19:54.298> of<08:19:54.420> these<08:19:54.540> we've 08:19:54.770 --> 08:19:54.780 align:start position:0% services and some of these we've 08:19:54.780 --> 08:19:56.930 align:start position:0% services and some of these we've discussed<08:19:55.260> now<08:19:55.860> as<08:19:56.040> devices<08:19:56.398> only 08:19:56.930 --> 08:19:56.940 align:start position:0% discussed now as devices only 08:19:56.940 --> 08:19:58.968 align:start position:0% discussed now as devices only communicate<08:19:57.540> with<08:19:57.840> each<08:19:58.020> other<08:19:58.200> by<08:19:58.740> their 08:19:58.968 --> 08:19:58.978 align:start position:0% communicate with each other by their 08:19:58.978 --> 08:20:01.368 align:start position:0% communicate with each other by their Network<08:19:59.160> address<08:19:59.580> the<08:20:00.298> naming<08:20:00.660> service<08:20:00.840> is<08:20:01.138> a 08:20:01.368 --> 08:20:01.378 align:start position:0% Network address the naming service is a 08:20:01.378 --> 08:20:03.590 align:start position:0% Network address the naming service is a really<08:20:01.558> crucial<08:20:02.160> to<08:20:02.638> the<08:20:02.820> operation<08:20:03.180> of<08:20:03.478> a 08:20:03.590 --> 08:20:03.600 align:start position:0% really crucial to the operation of a 08:20:03.600 --> 08:20:05.330 align:start position:0% really crucial to the operation of a network<08:20:03.780> there<08:20:04.620> are<08:20:04.798> three<08:20:05.100> different 08:20:05.330 --> 08:20:05.340 align:start position:0% network there are three different 08:20:05.340 --> 08:20:07.730 align:start position:0% network there are three different network<08:20:05.820> Services<08:20:06.240> used<08:20:06.780> that<08:20:07.378> you<08:20:07.500> should<08:20:07.620> be 08:20:07.730 --> 08:20:07.740 align:start position:0% network Services used that you should be 08:20:07.740 --> 08:20:10.128 align:start position:0% network Services used that you should be aware<08:20:07.978> of<08:20:08.160> the<08:20:08.700> first<08:20:08.878> DNS<08:20:09.718> which<08:20:09.898> we've 08:20:10.128 --> 08:20:10.138 align:start position:0% aware of the first DNS which we've 08:20:10.138 --> 08:20:12.770 align:start position:0% aware of the first DNS which we've mentioned<08:20:10.440> before<08:20:10.680> also<08:20:11.580> called<08:20:11.760> the<08:20:12.120> domain 08:20:12.770 --> 08:20:12.780 align:start position:0% mentioned before also called the domain 08:20:12.780 --> 08:20:15.230 align:start position:0% mentioned before also called the domain name<08:20:13.200> service<08:20:13.620> is<08:20:14.160> an<08:20:14.398> Aiming<08:20:14.700> service<08:20:14.878> that's 08:20:15.230 --> 08:20:15.240 align:start position:0% name service is an Aiming service that's 08:20:15.240 --> 08:20:17.330 align:start position:0% name service is an Aiming service that's used<08:20:15.478> on<08:20:15.840> the<08:20:15.958> internet<08:20:16.080> in<08:20:16.558> most<08:20:16.798> networks 08:20:17.330 --> 08:20:17.340 align:start position:0% used on the internet in most networks 08:20:17.340 --> 08:20:19.430 align:start position:0% used on the internet in most networks it's<08:20:17.878> what<08:20:18.120> allows<08:20:18.478> for<08:20:18.780> instance<08:20:19.020> you<08:20:19.260> to 08:20:19.430 --> 08:20:19.440 align:start position:0% it's what allows for instance you to 08:20:19.440 --> 08:20:21.650 align:start position:0% it's what allows for instance you to type<08:20:19.620> in<08:20:19.920> Google 08:20:21.650 --> 08:20:21.660 align:start position:0% type in Google 08:20:21.660 --> 08:20:25.368 align:start position:0% type in Google dot<08:20:22.558> com<08:20:22.620> which<08:20:23.458> we<08:20:23.638> would<08:20:23.878> call<08:20:24.120> a<08:20:24.660> fully 08:20:25.368 --> 08:20:25.378 align:start position:0% dot com which we would call a fully 08:20:25.378 --> 08:20:28.968 align:start position:0% dot com which we would call a fully qualified<08:20:26.360> domain<08:20:27.360> name<08:20:27.840> and<08:20:28.620> it<08:20:28.860> will 08:20:28.968 --> 08:20:28.978 align:start position:0% qualified domain name and it will 08:20:28.978 --> 08:20:32.628 align:start position:0% qualified domain name and it will translate<08:20:29.398> that<08:20:30.240> to<08:20:31.020> the<08:20:31.200> IP<08:20:31.558> address<08:20:31.860> of 08:20:32.628 --> 08:20:32.638 align:start position:0% translate that to the IP address of 08:20:32.638 --> 08:20:34.548 align:start position:0% translate that to the IP address of Google<08:20:32.760> whatever<08:20:33.180> that<08:20:33.540> might<08:20:33.780> be 08:20:34.548 --> 08:20:34.558 align:start position:0% Google whatever that might be 08:20:34.558 --> 08:20:36.650 align:start position:0% Google whatever that might be the<08:20:35.100> next<08:20:35.218> naming<08:20:35.638> service<08:20:35.820> is<08:20:36.240> Windows 08:20:36.650 --> 08:20:36.660 align:start position:0% the next naming service is Windows 08:20:36.660 --> 08:20:39.110 align:start position:0% the next naming service is Windows specific<08:20:37.020> and<08:20:37.320> it's<08:20:37.500> called<08:20:37.798> wins<08:20:38.520> or<08:20:38.820> the 08:20:39.110 --> 08:20:39.120 align:start position:0% specific and it's called wins or the 08:20:39.120 --> 08:20:41.750 align:start position:0% specific and it's called wins or the windows<08:20:39.718> internet<08:20:40.020> naming<08:20:40.740> service<08:20:40.978> it's 08:20:41.750 --> 08:20:41.760 align:start position:0% windows internet naming service it's 08:20:41.760 --> 08:20:44.570 align:start position:0% windows internet naming service it's really<08:20:42.000> outdated<08:20:42.660> and<08:20:43.558> it<08:20:43.860> was<08:20:43.978> used<08:20:44.218> on 08:20:44.570 --> 08:20:44.580 align:start position:0% really outdated and it was used on 08:20:44.580 --> 08:20:46.850 align:start position:0% really outdated and it was used on Windows<08:20:45.000> networks<08:20:45.600> the<08:20:46.320> only<08:20:46.440> reason<08:20:46.620> I 08:20:46.850 --> 08:20:46.860 align:start position:0% Windows networks the only reason I 08:20:46.860 --> 08:20:49.128 align:start position:0% Windows networks the only reason I mention<08:20:47.100> it<08:20:47.340> is<08:20:47.638> you<08:20:47.940> might<08:20:48.180> see<08:20:48.478> it<08:20:48.660> mentioned 08:20:49.128 --> 08:20:49.138 align:start position:0% mention it is you might see it mentioned 08:20:49.138 --> 08:20:50.990 align:start position:0% mention it is you might see it mentioned in<08:20:49.440> a<08:20:49.558> test<08:20:49.740> question<08:20:49.978> and<08:20:50.280> it<08:20:50.398> might<08:20:50.580> help<08:20:50.820> you 08:20:50.990 --> 08:20:51.000 align:start position:0% in a test question and it might help you 08:20:51.000 --> 08:20:52.490 align:start position:0% in a test question and it might help you but<08:20:51.540> you're<08:20:51.660> really<08:20:51.840> not<08:20:52.020> going<08:20:52.200> to<08:20:52.260> see<08:20:52.378> it 08:20:52.490 --> 08:20:52.500 align:start position:0% but you're really not going to see it 08:20:52.500 --> 08:20:55.190 align:start position:0% but you're really not going to see it used<08:20:52.680> in<08:20:52.920> the<08:20:53.040> field<08:20:53.280> much<08:20:53.878> anymore<08:20:54.200> and 08:20:55.190 --> 08:20:55.200 align:start position:0% used in the field much anymore and 08:20:55.200 --> 08:20:57.708 align:start position:0% used in the field much anymore and finally<08:20:55.500> we<08:20:55.920> have<08:20:56.040> one<08:20:56.280> called<08:20:56.520> net<08:20:57.120> bios 08:20:57.708 --> 08:20:57.718 align:start position:0% finally we have one called net bios 08:20:57.718 --> 08:21:00.110 align:start position:0% finally we have one called net bios which<08:20:57.958> is<08:20:58.138> a<08:20:58.440> broadcast<08:20:58.978> type<08:20:59.700> of<08:20:59.878> service 08:21:00.110 --> 08:21:00.120 align:start position:0% which is a broadcast type of service 08:21:00.120 --> 08:21:04.548 align:start position:0% which is a broadcast type of service that<08:21:00.840> has<08:21:01.020> a<08:21:01.320> maximum<08:21:01.740> length<08:21:02.660> of<08:21:03.660> uh<08:21:04.080> 15 08:21:04.548 --> 08:21:04.558 align:start position:0% that has a maximum length of uh 15 08:21:04.558 --> 08:21:08.150 align:start position:0% that has a maximum length of uh 15 characters 08:21:08.150 --> 08:21:08.160 align:start position:0% 08:21:08.160 --> 08:21:11.448 align:start position:0% and<08:21:08.878> it<08:21:09.298> was<08:21:09.478> used<08:21:09.780> or<08:21:10.260> still<08:21:10.620> is<08:21:10.798> used<08:21:11.040> to<08:21:11.218> a 08:21:11.448 --> 08:21:11.458 align:start position:0% and it was used or still is used to a 08:21:11.458 --> 08:21:13.310 align:start position:0% and it was used or still is used to a certain<08:21:11.580> extent<08:21:12.000> on<08:21:12.298> Windows<08:21:12.660> networks<08:21:13.138> as 08:21:13.310 --> 08:21:13.320 align:start position:0% certain extent on Windows networks as 08:21:13.320 --> 08:21:15.650 align:start position:0% certain extent on Windows networks as well<08:21:13.500> a<08:21:14.340> good<08:21:14.520> understanding<08:21:15.000> of<08:21:15.298> all<08:21:15.600> of 08:21:15.650 --> 08:21:15.660 align:start position:0% well a good understanding of all of 08:21:15.660 --> 08:21:17.888 align:start position:0% well a good understanding of all of these<08:21:15.958> Network<08:21:16.138> identification<08:21:16.920> aspects 08:21:17.888 --> 08:21:17.898 align:start position:0% these Network identification aspects 08:21:17.898 --> 08:21:21.888 align:start position:0% these Network identification aspects addresses<08:21:18.898> and<08:21:19.260> names<08:21:19.760> is<08:21:20.760> important<08:21:21.240> at<08:21:21.718> this 08:21:21.888 --> 08:21:21.898 align:start position:0% addresses and names is important at this 08:21:21.898 --> 08:21:23.388 align:start position:0% addresses and names is important at this very<08:21:22.080> fundamental<08:21:22.620> level 08:21:23.388 --> 08:21:23.398 align:start position:0% very fundamental level 08:21:23.398 --> 08:21:25.010 align:start position:0% very fundamental level so<08:21:23.760> now<08:21:23.940> that<08:21:24.120> we<08:21:24.298> sort<08:21:24.478> of<08:21:24.540> have<08:21:24.718> a<08:21:24.898> general 08:21:25.010 --> 08:21:25.020 align:start position:0% so now that we sort of have a general 08:21:25.020 --> 08:21:27.770 align:start position:0% so now that we sort of have a general overview<08:21:25.620> of<08:21:26.340> these<08:21:26.580> let's<08:21:26.760> take<08:21:27.000> a<08:21:27.120> look<08:21:27.240> at 08:21:27.770 --> 08:21:27.780 align:start position:0% overview of these let's take a look at 08:21:27.780 --> 08:21:29.510 align:start position:0% overview of these let's take a look at some<08:21:27.958> of<08:21:28.080> the<08:21:28.200> specific<08:21:28.440> type<08:21:28.920> of<08:21:29.280> network 08:21:29.510 --> 08:21:29.520 align:start position:0% some of the specific type of network 08:21:29.520 --> 08:21:31.750 align:start position:0% some of the specific type of network addressing<08:21:30.240> specifically 08:21:31.750 --> 08:21:31.760 align:start position:0% addressing specifically 08:21:31.760 --> 08:21:37.730 align:start position:0% addressing specifically ipv4<08:21:32.780> now<08:21:33.780> ipv4<08:21:34.878> ipv4<08:21:36.138> addresses<08:21:37.138> is<08:21:37.260> a<08:21:37.558> very 08:21:37.730 --> 08:21:37.740 align:start position:0% ipv4 now ipv4 ipv4 addresses is a very 08:21:37.740 --> 08:21:41.090 align:start position:0% ipv4 now ipv4 ipv4 addresses is a very important<08:21:38.398> aspect<08:21:38.878> of<08:21:39.298> networking<08:21:39.898> for<08:21:40.680> any 08:21:41.090 --> 08:21:41.100 align:start position:0% important aspect of networking for any 08:21:41.100 --> 08:21:44.090 align:start position:0% important aspect of networking for any administrator<08:21:41.878> or<08:21:42.378> technician<08:21:43.378> or<08:21:43.620> even<08:21:43.798> just 08:21:44.090 --> 08:21:44.100 align:start position:0% administrator or technician or even just 08:21:44.100 --> 08:21:47.570 align:start position:0% administrator or technician or even just you<08:21:44.580> know<08:21:44.638> it<08:21:45.058> guy<08:21:45.540> to<08:21:46.260> understand 08:21:47.570 --> 08:21:47.580 align:start position:0% you know it guy to understand 08:21:47.580 --> 08:21:51.948 align:start position:0% you know it guy to understand it<08:21:48.180> is<08:21:48.420> a<08:21:48.840> 32-bit<08:21:49.680> binary<08:21:50.638> address<08:21:51.058> that's 08:21:51.948 --> 08:21:51.958 align:start position:0% it is a 32-bit binary address that's 08:21:51.958 --> 08:21:54.888 align:start position:0% it is a 32-bit binary address that's used<08:21:52.260> to<08:21:52.500> identify<08:21:53.160> and<08:21:53.760> differentiate<08:21:54.360> nodes 08:21:54.888 --> 08:21:54.898 align:start position:0% used to identify and differentiate nodes 08:21:54.898 --> 08:21:58.128 align:start position:0% used to identify and differentiate nodes on<08:21:55.200> a<08:21:55.378> network<08:21:55.500> in<08:21:56.398> other<08:21:56.458> words<08:21:56.700> it<08:21:57.420> is<08:21:57.600> your 08:21:58.128 --> 08:21:58.138 align:start position:0% on a network in other words it is your 08:21:58.138 --> 08:22:00.770 align:start position:0% on a network in other words it is your address<08:21:58.558> on<08:21:59.218> the<08:21:59.340> network<08:21:59.458> or<08:22:00.000> your<08:22:00.420> social 08:22:00.770 --> 08:22:00.780 align:start position:0% address on the network or your social 08:22:00.780 --> 08:22:04.250 align:start position:0% address on the network or your social security<08:22:01.200> number<08:22:01.680> with<08:22:02.580> the<08:22:02.820> ipv4<08:22:03.540> addressing 08:22:04.250 --> 08:22:04.260 align:start position:0% security number with the ipv4 addressing 08:22:04.260 --> 08:22:07.850 align:start position:0% security number with the ipv4 addressing scheme<08:22:04.740> being<08:22:05.160> a<08:22:05.660> 32-bit<08:22:06.660> address<08:22:07.080> and<08:22:07.740> you 08:22:07.850 --> 08:22:07.860 align:start position:0% scheme being a 32-bit address and you 08:22:07.860 --> 08:22:09.650 align:start position:0% scheme being a 32-bit address and you can<08:22:07.978> see<08:22:08.218> if<08:22:08.458> we<08:22:08.638> counted<08:22:09.058> each<08:22:09.240> one<08:22:09.420> of<08:22:09.540> these 08:22:09.650 --> 08:22:09.660 align:start position:0% can see if we counted each one of these 08:22:09.660 --> 08:22:13.070 align:start position:0% can see if we counted each one of these up<08:22:09.780> remember<08:22:10.020> a<08:22:10.440> bit<08:22:10.558> is<08:22:11.160> either<08:22:11.398> 0<08:22:12.240> or<08:22:12.540> 1<08:22:12.780> and 08:22:13.070 --> 08:22:13.080 align:start position:0% up remember a bit is either 0 or 1 and 08:22:13.080 --> 08:22:15.468 align:start position:0% up remember a bit is either 0 or 1 and we<08:22:13.260> can<08:22:13.378> count<08:22:13.558> up<08:22:13.798> there<08:22:14.160> are<08:22:14.340> 32<08:22:14.940> of<08:22:15.180> these 08:22:15.468 --> 08:22:15.478 align:start position:0% we can count up there are 32 of these 08:22:15.478 --> 08:22:17.350 align:start position:0% we can count up there are 32 of these this<08:22:16.020> means<08:22:16.320> that<08:22:16.500> there<08:22:16.680> are<08:22:16.860> theoretically 08:22:17.350 --> 08:22:17.360 align:start position:0% this means that there are theoretically 08:22:17.360 --> 08:22:19.628 align:start position:0% this means that there are theoretically up<08:22:18.360> to 08:22:19.628 --> 08:22:19.638 align:start position:0% up to 08:22:19.638 --> 08:22:23.170 align:start position:0% up to 4.29<08:22:20.638> billion 08:22:23.170 --> 08:22:23.180 align:start position:0% 4.29 billion 08:22:23.180 --> 08:22:26.628 align:start position:0% 4.29 billion addresses<08:22:24.180> available<08:22:24.958> now<08:22:25.920> that<08:22:26.160> might<08:22:26.398> not 08:22:26.628 --> 08:22:26.638 align:start position:0% addresses available now that might not 08:22:26.638 --> 08:22:28.670 align:start position:0% addresses available now that might not sound<08:22:27.058> uh<08:22:27.718> like<08:22:27.898> we're<08:22:28.080> ever<08:22:28.200> going<08:22:28.440> to<08:22:28.558> hit 08:22:28.670 --> 08:22:28.680 align:start position:0% sound uh like we're ever going to hit 08:22:28.680 --> 08:22:30.708 align:start position:0% sound uh like we're ever going to hit that<08:22:28.920> but<08:22:29.398> in<08:22:29.580> fact<08:22:29.700> we've<08:22:30.058> already<08:22:30.240> gotten 08:22:30.708 --> 08:22:30.718 align:start position:0% that but in fact we've already gotten 08:22:30.718 --> 08:22:32.628 align:start position:0% that but in fact we've already gotten there<08:22:30.898> and<08:22:31.378> so<08:22:31.558> part<08:22:31.798> of<08:22:31.920> the<08:22:32.040> problem<08:22:32.160> is<08:22:32.398> how 08:22:32.628 --> 08:22:32.638 align:start position:0% there and so part of the problem is how 08:22:32.638 --> 08:22:36.170 align:start position:0% there and so part of the problem is how do<08:22:32.760> we<08:22:32.878> share<08:22:33.180> 4.29<08:22:34.080> billion<08:22:34.558> devices<08:22:35.180> with 08:22:36.170 --> 08:22:36.180 align:start position:0% do we share 4.29 billion devices with 08:22:36.180 --> 08:22:39.590 align:start position:0% do we share 4.29 billion devices with our<08:22:36.420> 4.29<08:22:37.200> billion<08:22:37.680> addresses<08:22:38.398> with<08:22:39.180> even 08:22:39.590 --> 08:22:39.600 align:start position:0% our 4.29 billion addresses with even 08:22:39.600 --> 08:22:42.770 align:start position:0% our 4.29 billion addresses with even more<08:22:40.020> billions<08:22:40.500> devices<08:22:40.920> in<08:22:41.520> the<08:22:41.638> world<08:22:41.820> so 08:22:42.770 --> 08:22:42.780 align:start position:0% more billions devices in the world so 08:22:42.780 --> 08:22:45.650 align:start position:0% more billions devices in the world so this<08:22:42.958> 32-bit<08:22:43.920> address<08:22:44.280> which<08:22:45.058> is<08:22:45.180> why<08:22:45.420> we've 08:22:45.650 --> 08:22:45.660 align:start position:0% this 32-bit address which is why we've 08:22:45.660 --> 08:22:48.468 align:start position:0% this 32-bit address which is why we've had<08:22:45.840> to<08:22:46.200> develop<08:22:46.620> another<08:22:46.978> one<08:22:47.280> called<08:22:47.580> IPv6 08:22:48.468 --> 08:22:48.478 align:start position:0% had to develop another one called IPv6 08:22:48.478 --> 08:22:51.650 align:start position:0% had to develop another one called IPv6 but<08:22:49.138> anyway<08:22:49.320> I<08:22:49.558> digress<08:22:49.920> the<08:22:50.760> 32-bit<08:22:51.360> address 08:22:51.650 --> 08:22:51.660 align:start position:0% but anyway I digress the 32-bit address 08:22:51.660 --> 08:22:55.910 align:start position:0% but anyway I digress the 32-bit address is<08:22:52.260> broken<08:22:52.378> up<08:22:52.680> into<08:22:53.058> four<08:22:54.058> octets<08:22:54.780> this<08:22:55.680> makes 08:22:55.910 --> 08:22:55.920 align:start position:0% is broken up into four octets this makes 08:22:55.920 --> 08:22:58.548 align:start position:0% is broken up into four octets this makes it<08:22:56.218> easier<08:22:56.580> for<08:22:57.240> people<08:22:57.478> to<08:22:57.780> remember<08:22:57.958> and<08:22:58.320> to 08:22:58.548 --> 08:22:58.558 align:start position:0% it easier for people to remember and to 08:22:58.558 --> 08:22:59.510 align:start position:0% it easier for people to remember and to read 08:22:59.510 --> 08:22:59.520 align:start position:0% read 08:22:59.520 --> 08:23:02.090 align:start position:0% read and<08:23:00.058> you<08:23:00.240> can<08:23:00.360> see<08:23:00.540> those<08:23:00.780> here<08:23:01.320> and<08:23:01.620> if<08:23:01.798> you've 08:23:02.090 --> 08:23:02.100 align:start position:0% and you can see those here and if you've 08:23:02.100 --> 08:23:03.910 align:start position:0% and you can see those here and if you've ever<08:23:02.458> seen<08:23:02.820> like<08:23:03.058> a 08:23:03.910 --> 08:23:03.920 align:start position:0% ever seen like a 08:23:03.920 --> 08:23:06.650 align:start position:0% ever seen like a 192.168.0.1<08:23:04.920> those<08:23:05.160> are<08:23:05.340> the<08:23:05.398> four<08:23:05.580> octets 08:23:06.650 --> 08:23:06.660 align:start position:0% 192.168.0.1 those are the four octets 08:23:06.660 --> 08:23:08.750 align:start position:0% 192.168.0.1 those are the four octets this<08:23:07.260> system<08:23:07.558> and<08:23:08.040> structure<08:23:08.398> of<08:23:08.580> these 08:23:08.750 --> 08:23:08.760 align:start position:0% this system and structure of these 08:23:08.760 --> 08:23:10.910 align:start position:0% this system and structure of these address<08:23:08.940> schemes<08:23:09.540> is<08:23:10.080> governed<08:23:10.440> and<08:23:10.558> managed 08:23:10.910 --> 08:23:10.920 align:start position:0% address schemes is governed and managed 08:23:10.920 --> 08:23:13.430 align:start position:0% address schemes is governed and managed by<08:23:11.280> two<08:23:11.520> standard<08:23:11.940> organizations<08:23:12.478> one<08:23:13.260> is 08:23:13.430 --> 08:23:13.440 align:start position:0% by two standard organizations one is 08:23:13.440 --> 08:23:17.690 align:start position:0% by two standard organizations one is called<08:23:13.620> the<08:23:13.920> a<08:23:14.160> i<08:23:14.458> a<08:23:14.700> n<08:23:15.000> a 08:23:17.690 --> 08:23:17.700 align:start position:0% 08:23:17.700 --> 08:23:19.910 align:start position:0% which<08:23:18.120> stands<08:23:18.540> for<08:23:18.660> the<08:23:18.958> internet<08:23:19.080> assigned 08:23:19.910 --> 08:23:19.920 align:start position:0% which stands for the internet assigned 08:23:19.920 --> 08:23:21.948 align:start position:0% which stands for the internet assigned numbers<08:23:20.160> Authority<08:23:20.878> and<08:23:21.478> the<08:23:21.660> other<08:23:21.718> is 08:23:21.948 --> 08:23:21.958 align:start position:0% numbers Authority and the other is 08:23:21.958 --> 08:23:24.590 align:start position:0% numbers Authority and the other is called<08:23:22.260> the<08:23:22.620> rir<08:23:23.218> or<08:23:23.760> the<08:23:23.878> regional<08:23:24.298> internet 08:23:24.590 --> 08:23:24.600 align:start position:0% called the rir or the regional internet 08:23:24.600 --> 08:23:26.510 align:start position:0% called the rir or the regional internet registry<08:23:25.378> I<08:23:25.978> wouldn't<08:23:26.040> worry<08:23:26.340> about 08:23:26.510 --> 08:23:26.520 align:start position:0% registry I wouldn't worry about 08:23:26.520 --> 08:23:28.010 align:start position:0% registry I wouldn't worry about memorizing<08:23:27.120> these<08:23:27.240> I'm<08:23:27.478> just<08:23:27.600> mentioning 08:23:28.010 --> 08:23:28.020 align:start position:0% memorizing these I'm just mentioning 08:23:28.020 --> 08:23:29.868 align:start position:0% memorizing these I'm just mentioning them<08:23:28.200> so<08:23:28.440> you<08:23:28.620> know<08:23:28.798> sort<08:23:29.040> of<08:23:29.160> who's<08:23:29.398> coming<08:23:29.760> up 08:23:29.868 --> 08:23:29.878 align:start position:0% them so you know sort of who's coming up 08:23:29.878 --> 08:23:31.128 align:start position:0% them so you know sort of who's coming up with<08:23:30.058> all<08:23:30.240> this<08:23:30.360> stuff 08:23:31.128 --> 08:23:31.138 align:start position:0% with all this stuff 08:23:31.138 --> 08:23:33.230 align:start position:0% with all this stuff now<08:23:31.740> every<08:23:31.978> device<08:23:32.218> on<08:23:32.520> the<08:23:32.638> network<08:23:32.760> is<08:23:33.120> going 08:23:33.230 --> 08:23:33.240 align:start position:0% now every device on the network is going 08:23:33.240 --> 08:23:36.170 align:start position:0% now every device on the network is going to<08:23:33.360> have<08:23:33.540> its<08:23:33.958> own<08:23:34.080> unique<08:23:34.978> address 08:23:36.170 --> 08:23:36.180 align:start position:0% to have its own unique address 08:23:36.180 --> 08:23:39.770 align:start position:0% to have its own unique address so<08:23:36.600> there<08:23:36.840> are<08:23:37.020> two<08:23:37.320> types<08:23:37.920> of<08:23:38.580> addresses<08:23:39.240> in 08:23:39.770 --> 08:23:39.780 align:start position:0% so there are two types of addresses in 08:23:39.780 --> 08:23:42.170 align:start position:0% so there are two types of addresses in general<08:23:39.898> one<08:23:40.558> is<08:23:40.740> called<08:23:40.978> class<08:23:41.398> full<08:23:41.700> and 08:23:42.170 --> 08:23:42.180 align:start position:0% general one is called class full and 08:23:42.180 --> 08:23:44.570 align:start position:0% general one is called class full and these<08:23:42.420> are<08:23:42.600> default<08:23:43.200> addresses<08:23:43.920> and<08:23:44.458> the 08:23:44.570 --> 08:23:44.580 align:start position:0% these are default addresses and the 08:23:44.580 --> 08:23:46.490 align:start position:0% these are default addresses and the other<08:23:44.700> are<08:23:44.940> called<08:23:45.120> class<08:23:45.600> less<08:23:45.898> which<08:23:46.260> are 08:23:46.490 --> 08:23:46.500 align:start position:0% other are called class less which are 08:23:46.500 --> 08:23:48.530 align:start position:0% other are called class less which are custom<08:23:46.860> addresses<08:23:47.638> we're<08:23:48.120> going<08:23:48.298> to<08:23:48.360> talk 08:23:48.530 --> 08:23:48.540 align:start position:0% custom addresses we're going to talk 08:23:48.540 --> 08:23:51.230 align:start position:0% custom addresses we're going to talk about<08:23:48.718> the<08:23:49.080> class<08:23:49.260> less<08:23:49.558> ones<08:23:50.100> in<08:23:50.820> a<08:23:51.058> later 08:23:51.230 --> 08:23:51.240 align:start position:0% about the class less ones in a later 08:23:51.240 --> 08:23:53.930 align:start position:0% about the class less ones in a later module<08:23:52.020> and<08:23:52.680> we're<08:23:52.860> going<08:23:52.978> to<08:23:53.040> Define<08:23:53.218> both<08:23:53.760> of 08:23:53.930 --> 08:23:53.940 align:start position:0% module and we're going to Define both of 08:23:53.940 --> 08:23:56.208 align:start position:0% module and we're going to Define both of these<08:23:54.180> in<08:23:54.780> Greater<08:23:55.200> detail<08:23:55.680> a<08:23:55.978> little<08:23:56.100> bit 08:23:56.208 --> 08:23:56.218 align:start position:0% these in Greater detail a little bit 08:23:56.218 --> 08:23:57.530 align:start position:0% these in Greater detail a little bit later<08:23:56.458> on 08:23:57.530 --> 08:23:57.540 align:start position:0% later on 08:23:57.540 --> 08:23:59.628 align:start position:0% later on as<08:23:58.020> a<08:23:58.200> network<08:23:58.320> address<08:23:58.680> it's<08:23:59.040> also<08:23:59.340> made<08:23:59.458> up 08:23:59.628 --> 08:23:59.638 align:start position:0% as a network address it's also made up 08:23:59.638 --> 08:24:03.530 align:start position:0% as a network address it's also made up of<08:23:59.820> two<08:24:00.120> parts<08:24:00.500> the<08:24:01.500> network<08:24:01.680> portion<08:24:02.298> and<08:24:03.298> the 08:24:03.530 --> 08:24:03.540 align:start position:0% of two parts the network portion and the 08:24:03.540 --> 08:24:05.270 align:start position:0% of two parts the network portion and the node<08:24:03.718> portion<08:24:04.200> let<08:24:04.378> me<08:24:04.500> just<08:24:04.620> erase<08:24:04.978> all<08:24:05.100> this 08:24:05.270 --> 08:24:05.280 align:start position:0% node portion let me just erase all this 08:24:05.280 --> 08:24:06.888 align:start position:0% node portion let me just erase all this writing<08:24:05.638> here<08:24:05.760> so<08:24:05.940> you<08:24:06.058> can<08:24:06.180> see<08:24:06.298> exactly<08:24:06.660> what 08:24:06.888 --> 08:24:06.898 align:start position:0% writing here so you can see exactly what 08:24:06.898 --> 08:24:09.948 align:start position:0% writing here so you can see exactly what I<08:24:07.080> mean<08:24:07.260> in<08:24:08.160> order<08:24:08.280> to<08:24:08.580> tell<08:24:08.760> now<08:24:09.240> in<08:24:09.718> this 08:24:09.948 --> 08:24:09.958 align:start position:0% I mean in order to tell now in this 08:24:09.958 --> 08:24:11.330 align:start position:0% I mean in order to tell now in this section 08:24:11.330 --> 08:24:11.340 align:start position:0% section 08:24:11.340 --> 08:24:13.070 align:start position:0% section you<08:24:11.820> can<08:24:11.940> see<08:24:12.058> the<08:24:12.240> network<08:24:12.298> portion<08:24:12.780> are<08:24:12.898> the 08:24:13.070 --> 08:24:13.080 align:start position:0% you can see the network portion are the 08:24:13.080 --> 08:24:15.468 align:start position:0% you can see the network portion are the first<08:24:13.200> two<08:24:13.500> octets<08:24:13.978> and<08:24:14.638> the<08:24:14.820> node<08:24:14.940> portion<08:24:15.360> of 08:24:15.468 --> 08:24:15.478 align:start position:0% first two octets and the node portion of 08:24:15.478 --> 08:24:17.330 align:start position:0% first two octets and the node portion of the<08:24:15.600> last<08:24:15.718> two<08:24:15.898> octets<08:24:16.320> but<08:24:16.740> that<08:24:16.860> is<08:24:17.040> not 08:24:17.330 --> 08:24:17.340 align:start position:0% the last two octets but that is not 08:24:17.340 --> 08:24:19.968 align:start position:0% the last two octets but that is not always<08:24:17.700> the<08:24:18.058> case<08:24:18.240> in<08:24:19.080> fact<08:24:19.200> if<08:24:19.558> we<08:24:19.680> were<08:24:19.860> to 08:24:19.968 --> 08:24:19.978 align:start position:0% always the case in fact if we were to 08:24:19.978 --> 08:24:22.610 align:start position:0% always the case in fact if we were to just<08:24:20.100> take<08:24:20.280> those<08:24:20.458> away<08:24:20.700> for<08:24:21.000> a<08:24:21.120> second<08:24:21.378> uh<08:24:22.378> and 08:24:22.610 --> 08:24:22.620 align:start position:0% just take those away for a second uh and 08:24:22.620 --> 08:24:24.110 align:start position:0% just take those away for a second uh and this<08:24:22.860> is<08:24:22.978> how<08:24:23.160> the<08:24:23.280> computer<08:24:23.458> looks<08:24:23.940> at<08:24:24.000> them 08:24:24.110 --> 08:24:24.120 align:start position:0% this is how the computer looks at them 08:24:24.120 --> 08:24:26.270 align:start position:0% this is how the computer looks at them we<08:24:24.718> can't<08:24:24.840> actually<08:24:25.080> tell<08:24:25.440> which<08:24:25.798> is<08:24:25.978> which 08:24:26.270 --> 08:24:26.280 align:start position:0% we can't actually tell which is which 08:24:26.280 --> 08:24:28.128 align:start position:0% we can't actually tell which is which and<08:24:26.878> that's<08:24:26.940> why<08:24:27.180> we<08:24:27.360> need<08:24:27.478> something<08:24:27.780> called 08:24:28.128 --> 08:24:28.138 align:start position:0% and that's why we need something called 08:24:28.138 --> 08:24:30.770 align:start position:0% and that's why we need something called a<08:24:28.440> subnet<08:24:28.860> mask<08:24:29.160> the<08:24:29.458> subnet<08:24:29.820> mask<08:24:30.058> allows<08:24:30.660> us 08:24:30.770 --> 08:24:30.780 align:start position:0% a subnet mask the subnet mask allows us 08:24:30.780 --> 08:24:32.448 align:start position:0% a subnet mask the subnet mask allows us to<08:24:31.320> determine<08:24:31.620> which<08:24:31.920> is<08:24:32.100> the<08:24:32.280> network 08:24:32.448 --> 08:24:32.458 align:start position:0% to determine which is the network 08:24:32.458 --> 08:24:35.388 align:start position:0% to determine which is the network portion<08:24:32.940> and<08:24:33.780> which<08:24:34.020> is<08:24:34.440> the<08:24:34.680> node<08:24:34.860> portion 08:24:35.388 --> 08:24:35.398 align:start position:0% portion and which is the node portion 08:24:35.398 --> 08:24:38.448 align:start position:0% portion and which is the node portion that<08:24:36.240> way<08:24:36.420> we<08:24:36.958> know<08:24:37.080> for<08:24:37.378> instance<08:24:37.620> where<08:24:38.040> the 08:24:38.448 --> 08:24:38.458 align:start position:0% that way we know for instance where the 08:24:38.458 --> 08:24:41.570 align:start position:0% that way we know for instance where the area<08:24:39.058> code<08:24:39.420> of<08:24:39.600> the<08:24:39.718> phone<08:24:39.898> number<08:24:40.080> begins<08:24:40.740> and 08:24:41.570 --> 08:24:41.580 align:start position:0% area code of the phone number begins and 08:24:41.580 --> 08:24:43.368 align:start position:0% area code of the phone number begins and the<08:24:41.760> rest<08:24:41.878> of<08:24:42.000> the<08:24:42.058> number<08:24:42.298> ends<08:24:42.780> so<08:24:43.200> the 08:24:43.368 --> 08:24:43.378 align:start position:0% the rest of the number ends so the 08:24:43.378 --> 08:24:44.990 align:start position:0% the rest of the number ends so the network<08:24:43.558> portion<08:24:44.040> would<08:24:44.218> be<08:24:44.340> like<08:24:44.580> the<08:24:44.878> area 08:24:44.990 --> 08:24:45.000 align:start position:0% network portion would be like the area 08:24:45.000 --> 08:24:47.090 align:start position:0% network portion would be like the area code<08:24:45.298> of<08:24:45.540> your<08:24:45.660> phone<08:24:45.840> number<08:24:46.020> or<08:24:46.798> the 08:24:47.090 --> 08:24:47.100 align:start position:0% code of your phone number or the 08:24:47.100 --> 08:24:48.830 align:start position:0% code of your phone number or the international<08:24:47.280> code<08:24:47.878> it<08:24:48.120> tells<08:24:48.420> you<08:24:48.478> which 08:24:48.830 --> 08:24:48.840 align:start position:0% international code it tells you which 08:24:48.840 --> 08:24:51.350 align:start position:0% international code it tells you which network<08:24:49.200> that<08:24:49.978> is<08:24:50.100> on<08:24:50.280> the<08:24:50.760> Node<08:24:50.878> portion 08:24:51.350 --> 08:24:51.360 align:start position:0% network that is on the Node portion 08:24:51.360 --> 08:24:53.330 align:start position:0% network that is on the Node portion tells<08:24:51.600> you<08:24:51.718> exactly<08:24:52.080> which<08:24:52.378> phone<08:24:52.680> on<08:24:53.160> that 08:24:53.330 --> 08:24:53.340 align:start position:0% tells you exactly which phone on that 08:24:53.340 --> 08:24:54.948 align:start position:0% tells you exactly which phone on that Network<08:24:53.580> we're<08:24:54.058> going<08:24:54.240> to<08:24:54.360> try<08:24:54.420> reaching<08:24:54.840> out 08:24:54.948 --> 08:24:54.958 align:start position:0% Network we're going to try reaching out 08:24:54.958 --> 08:24:58.610 align:start position:0% Network we're going to try reaching out to<08:24:55.080> so<08:24:56.040> we're<08:24:56.458> going<08:24:56.820> to<08:24:57.298> further<08:24:57.840> logically 08:24:58.610 --> 08:24:58.620 align:start position:0% to so we're going to further logically 08:24:58.620 --> 08:25:01.730 align:start position:0% to so we're going to further logically again<08:24:59.040> not<08:24:59.520> physically<08:24:59.898> divide<08:25:00.898> a<08:25:01.440> network 08:25:01.730 --> 08:25:01.740 align:start position:0% again not physically divide a network 08:25:01.740 --> 08:25:05.510 align:start position:0% again not physically divide a network into<08:25:02.520> smaller<08:25:03.058> sub<08:25:03.360> networks<08:25:03.958> called<08:25:04.680> sub 08:25:05.510 --> 08:25:05.520 align:start position:0% into smaller sub networks called sub 08:25:05.520 --> 08:25:07.670 align:start position:0% into smaller sub networks called sub Nets 08:25:07.670 --> 08:25:07.680 align:start position:0% Nets 08:25:07.680 --> 08:25:10.490 align:start position:0% Nets now<08:25:08.520> this<08:25:08.940> logical<08:25:09.298> division<08:25:09.718> is<08:25:10.020> beneficial 08:25:10.490 --> 08:25:10.500 align:start position:0% now this logical division is beneficial 08:25:10.500 --> 08:25:14.090 align:start position:0% now this logical division is beneficial because<08:25:11.218> of<08:25:11.520> three<08:25:11.820> reasons<08:25:12.420> one<08:25:13.080> it<08:25:13.920> can 08:25:14.090 --> 08:25:14.100 align:start position:0% because of three reasons one it can 08:25:14.100 --> 08:25:16.548 align:start position:0% because of three reasons one it can effectively<08:25:14.760> increase<08:25:15.180> the<08:25:15.718> efficiency<08:25:16.200> in 08:25:16.548 --> 08:25:16.558 align:start position:0% effectively increase the efficiency in 08:25:16.558 --> 08:25:20.570 align:start position:0% effectively increase the efficiency in packet<08:25:16.920> routing<08:25:17.340> because<08:25:18.058> if<08:25:18.600> I<08:25:18.718> know<08:25:18.958> that<08:25:19.580> my 08:25:20.570 --> 08:25:20.580 align:start position:0% packet routing because if I know that my 08:25:20.580 --> 08:25:23.330 align:start position:0% packet routing because if I know that my information<08:25:21.180> is<08:25:21.840> destined<08:25:22.260> for<08:25:22.558> a<08:25:22.860> specific 08:25:23.330 --> 08:25:23.340 align:start position:0% information is destined for a specific 08:25:23.340 --> 08:25:25.430 align:start position:0% information is destined for a specific Network<08:25:23.700> I<08:25:24.058> don't<08:25:24.180> have<08:25:24.360> to<08:25:24.540> bother<08:25:24.840> with 08:25:25.430 --> 08:25:25.440 align:start position:0% Network I don't have to bother with 08:25:25.440 --> 08:25:28.128 align:start position:0% Network I don't have to bother with asking<08:25:25.798> let's<08:25:26.040> say<08:25:26.280> 5<08:25:27.058> 000<08:25:27.120> or<08:25:27.298> 5<08:25:27.540> million<08:25:27.898> or 08:25:28.128 --> 08:25:28.138 align:start position:0% asking let's say 5 000 or 5 million or 08:25:28.138 --> 08:25:30.830 align:start position:0% asking let's say 5 000 or 5 million or five<08:25:28.378> billion<08:25:28.860> computers<08:25:29.340> if<08:25:29.700> I'm<08:25:30.180> meant<08:25:30.718> for 08:25:30.830 --> 08:25:30.840 align:start position:0% five billion computers if I'm meant for 08:25:30.840 --> 08:25:32.990 align:start position:0% five billion computers if I'm meant for them<08:25:31.080> I<08:25:31.680> can<08:25:31.798> go<08:25:31.978> directly<08:25:32.458> to<08:25:32.638> the<08:25:32.820> network 08:25:32.990 --> 08:25:33.000 align:start position:0% them I can go directly to the network 08:25:33.000 --> 08:25:35.030 align:start position:0% them I can go directly to the network where<08:25:33.420> I<08:25:33.540> want<08:25:33.660> to<08:25:33.780> go<08:25:33.958> just<08:25:34.440> like<08:25:34.558> with<08:25:34.860> area 08:25:35.030 --> 08:25:35.040 align:start position:0% where I want to go just like with area 08:25:35.040 --> 08:25:37.490 align:start position:0% where I want to go just like with area codes<08:25:35.398> and<08:25:35.760> phone<08:25:35.940> numbers<08:25:36.120> the<08:25:37.020> next<08:25:37.138> is<08:25:37.378> it 08:25:37.490 --> 08:25:37.500 align:start position:0% codes and phone numbers the next is it 08:25:37.500 --> 08:25:39.468 align:start position:0% codes and phone numbers the next is it allows<08:25:37.798> for<08:25:37.978> better<08:25:38.218> management<08:25:38.580> of<08:25:39.120> multiple 08:25:39.468 --> 08:25:39.478 align:start position:0% allows for better management of multiple 08:25:39.478 --> 08:25:41.230 align:start position:0% allows for better management of multiple networks<08:25:39.898> within<08:25:40.260> a<08:25:40.440> single<08:25:40.620> Organization 08:25:41.230 --> 08:25:41.240 align:start position:0% networks within a single Organization 08:25:41.240 --> 08:25:43.368 align:start position:0% networks within a single Organization for<08:25:42.240> instance<08:25:42.540> if<08:25:42.780> I'm<08:25:42.958> a<08:25:43.200> network 08:25:43.368 --> 08:25:43.378 align:start position:0% for instance if I'm a network 08:25:43.378 --> 08:25:45.708 align:start position:0% for instance if I'm a network administrator<08:25:44.040> it<08:25:44.520> might<08:25:44.700> be<08:25:44.878> easier<08:25:45.240> to<08:25:45.540> have 08:25:45.708 --> 08:25:45.718 align:start position:0% administrator it might be easier to have 08:25:45.718 --> 08:25:48.948 align:start position:0% administrator it might be easier to have separate<08:25:46.260> subnets<08:25:46.860> so<08:25:47.340> I<08:25:47.520> can<08:25:47.700> organize<08:25:48.360> who's 08:25:48.948 --> 08:25:48.958 align:start position:0% separate subnets so I can organize who's 08:25:48.958 --> 08:25:51.650 align:start position:0% separate subnets so I can organize who's on<08:25:49.200> which<08:25:49.378> subnet<08:25:49.920> so<08:25:50.100> that<08:25:50.340> way<08:25:50.520> not<08:25:51.120> only<08:25:51.298> are 08:25:51.650 --> 08:25:51.660 align:start position:0% on which subnet so that way not only are 08:25:51.660 --> 08:25:53.090 align:start position:0% on which subnet so that way not only are things<08:25:51.898> going<08:25:52.138> to<08:25:52.260> be<08:25:52.378> routed<08:25:52.920> more 08:25:53.090 --> 08:25:53.100 align:start position:0% things going to be routed more 08:25:53.100 --> 08:25:54.650 align:start position:0% things going to be routed more efficiently<08:25:53.580> for<08:25:53.878> that<08:25:54.120> person<08:25:54.298> but<08:25:54.600> it's 08:25:54.650 --> 08:25:54.660 align:start position:0% efficiently for that person but it's 08:25:54.660 --> 08:25:57.770 align:start position:0% efficiently for that person but it's easier<08:25:54.958> for<08:25:55.080> me<08:25:55.200> to<08:25:55.378> manage<08:25:55.680> on<08:25:55.978> paper<08:25:56.218> and<08:25:57.120> uh 08:25:57.770 --> 08:25:57.780 align:start position:0% easier for me to manage on paper and uh 08:25:57.780 --> 08:26:00.230 align:start position:0% easier for me to manage on paper and uh in<08:25:58.138> my<08:25:58.200> administrative<08:25:58.740> duties<08:25:59.280> and<08:26:00.000> finally 08:26:00.230 --> 08:26:00.240 align:start position:0% in my administrative duties and finally 08:26:00.240 --> 08:26:02.030 align:start position:0% in my administrative duties and finally it<08:26:00.478> potentially<08:26:00.840> offers<08:26:01.200> a<08:26:01.378> certain<08:26:01.500> level<08:26:01.740> of 08:26:02.030 --> 08:26:02.040 align:start position:0% it potentially offers a certain level of 08:26:02.040 --> 08:26:04.610 align:start position:0% it potentially offers a certain level of security<08:26:02.280> since<08:26:03.240> I'm<08:26:03.600> only<08:26:03.840> going<08:26:04.080> to<08:26:04.260> be<08:26:04.378> able 08:26:04.610 --> 08:26:04.620 align:start position:0% security since I'm only going to be able 08:26:04.620 --> 08:26:07.128 align:start position:0% security since I'm only going to be able to<08:26:04.860> access<08:26:05.160> easily<08:26:06.000> information<08:26:06.540> that's<08:26:06.958> on 08:26:07.128 --> 08:26:07.138 align:start position:0% to access easily information that's on 08:26:07.138 --> 08:26:08.990 align:start position:0% to access easily information that's on the<08:26:07.260> same<08:26:07.378> net<08:26:07.620> work<08:26:08.100> or<08:26:08.280> sub<08:26:08.458> Network<08:26:08.700> that 08:26:08.990 --> 08:26:09.000 align:start position:0% the same net work or sub Network that 08:26:09.000 --> 08:26:10.070 align:start position:0% the same net work or sub Network that I'm<08:26:09.180> on 08:26:10.070 --> 08:26:10.080 align:start position:0% I'm on 08:26:10.080 --> 08:26:13.310 align:start position:0% I'm on now<08:26:10.620> a<08:26:10.920> subnetted<08:26:11.458> ipv4<08:26:12.360> address<08:26:12.660> is<08:26:13.138> actually 08:26:13.310 --> 08:26:13.320 align:start position:0% now a subnetted ipv4 address is actually 08:26:13.320 --> 08:26:16.310 align:start position:0% now a subnetted ipv4 address is actually comprised<08:26:13.978> of<08:26:14.458> three<08:26:14.700> different<08:26:14.878> parts<08:26:15.320> the 08:26:16.310 --> 08:26:16.320 align:start position:0% comprised of three different parts the 08:26:16.320 --> 08:26:17.750 align:start position:0% comprised of three different parts the netid 08:26:17.750 --> 08:26:17.760 align:start position:0% netid 08:26:17.760 --> 08:26:19.610 align:start position:0% netid the<08:26:18.240> host<08:26:18.420> ID 08:26:19.610 --> 08:26:19.620 align:start position:0% the host ID 08:26:19.620 --> 08:26:22.490 align:start position:0% the host ID and<08:26:20.160> the<08:26:20.458> subnet<08:26:20.878> ID 08:26:22.490 --> 08:26:22.500 align:start position:0% and the subnet ID 08:26:22.500 --> 08:26:25.670 align:start position:0% and the subnet ID now<08:26:22.920> if<08:26:23.100> a<08:26:23.280> device<08:26:23.520> on<08:26:24.058> a<08:26:24.240> subnetted<08:26:24.840> tcpip 08:26:25.670 --> 08:26:25.680 align:start position:0% now if a device on a subnetted tcpip 08:26:25.680 --> 08:26:28.190 align:start position:0% now if a device on a subnetted tcpip network<08:26:26.040> wants<08:26:26.520> to<08:26:26.580> communicate<08:26:27.240> it's<08:26:27.898> going 08:26:28.190 --> 08:26:28.200 align:start position:0% network wants to communicate it's going 08:26:28.200 --> 08:26:30.948 align:start position:0% network wants to communicate it's going to<08:26:28.440> need<08:26:28.798> to<08:26:29.218> be<08:26:29.340> configured<08:26:29.878> with<08:26:30.360> an<08:26:30.600> IP 08:26:30.948 --> 08:26:30.958 align:start position:0% to need to be configured with an IP 08:26:30.958 --> 08:26:33.830 align:start position:0% to need to be configured with an IP address<08:26:31.398> and<08:26:32.398> a<08:26:32.700> subnet<08:26:33.058> mask<08:26:33.298> and<08:26:33.600> we'll<08:26:33.718> look 08:26:33.830 --> 08:26:33.840 align:start position:0% address and a subnet mask and we'll look 08:26:33.840 --> 08:26:35.930 align:start position:0% address and a subnet mask and we'll look at<08:26:33.958> these<08:26:34.138> in<08:26:34.260> just<08:26:34.378> a<08:26:34.558> second<08:26:34.680> the<08:26:35.520> subnet 08:26:35.930 --> 08:26:35.940 align:start position:0% at these in just a second the subnet 08:26:35.940 --> 08:26:39.230 align:start position:0% at these in just a second the subnet mask<08:26:36.180> is<08:26:36.660> what<08:26:36.898> is<08:26:37.020> used<08:26:37.320> to<08:26:37.740> identify<08:26:38.458> the 08:26:39.230 --> 08:26:39.240 align:start position:0% mask is what is used to identify the 08:26:39.240 --> 08:26:42.590 align:start position:0% mask is what is used to identify the subnet<08:26:39.958> that<08:26:40.740> each<08:26:40.920> node<08:26:41.280> belongs<08:26:41.820> to<08:26:41.940> this 08:26:42.590 --> 08:26:42.600 align:start position:0% subnet that each node belongs to this 08:26:42.600 --> 08:26:44.388 align:start position:0% subnet that each node belongs to this also<08:26:42.958> allows<08:26:43.260> us<08:26:43.378> to<08:26:43.620> determine<08:26:44.040> which 08:26:44.388 --> 08:26:44.398 align:start position:0% also allows us to determine which 08:26:44.398 --> 08:26:47.270 align:start position:0% also allows us to determine which network<08:26:44.760> it's<08:26:45.420> on<08:26:45.920> connectivity<08:26:46.920> devices 08:26:47.270 --> 08:26:47.280 align:start position:0% network it's on connectivity devices 08:26:47.280 --> 08:26:50.270 align:start position:0% network it's on connectivity devices such<08:26:47.760> as<08:26:47.878> routers<08:26:48.540> or<08:26:49.138> upper<08:26:49.440> layer<08:26:49.798> switches 08:26:50.270 --> 08:26:50.280 align:start position:0% such as routers or upper layer switches 08:26:50.280 --> 08:26:53.208 align:start position:0% such as routers or upper layer switches and<08:26:50.760> we're<08:26:50.878> talking<08:26:51.120> about<08:26:51.500> layer<08:26:52.500> 3<08:26:52.680> devices 08:26:53.208 --> 08:26:53.218 align:start position:0% and we're talking about layer 3 devices 08:26:53.218 --> 08:26:55.968 align:start position:0% and we're talking about layer 3 devices here<08:26:53.700> and<08:26:54.240> remember<08:26:54.420> layer<08:26:54.958> 3<08:26:55.138> devices<08:26:55.500> look 08:26:55.968 --> 08:26:55.978 align:start position:0% here and remember layer 3 devices look 08:26:55.978 --> 08:26:58.190 align:start position:0% here and remember layer 3 devices look at<08:26:56.398> IP<08:26:56.940> addresses 08:26:58.190 --> 08:26:58.200 align:start position:0% at IP addresses 08:26:58.200 --> 08:27:01.368 align:start position:0% at IP addresses not<08:26:58.860> just<08:26:59.040> Mac<08:26:59.398> addresses 08:27:01.368 --> 08:27:01.378 align:start position:0% not just Mac addresses 08:27:01.378 --> 08:27:03.708 align:start position:0% not just Mac addresses are<08:27:02.100> used<08:27:02.340> on<08:27:02.700> the<08:27:02.878> borders<08:27:03.240> of<08:27:03.478> these 08:27:03.708 --> 08:27:03.718 align:start position:0% are used on the borders of these 08:27:03.718 --> 08:27:06.048 align:start position:0% are used on the borders of these networks<08:27:04.138> to<08:27:04.680> manage<08:27:04.978> the<08:27:05.218> data<08:27:05.580> passage 08:27:06.048 --> 08:27:06.058 align:start position:0% networks to manage the data passage 08:27:06.058 --> 08:27:08.388 align:start position:0% networks to manage the data passage between<08:27:06.420> and<08:27:06.840> within<08:27:07.138> the<08:27:07.320> network<08:27:07.500> that's 08:27:08.388 --> 08:27:08.398 align:start position:0% between and within the network that's 08:27:08.398 --> 08:27:09.708 align:start position:0% between and within the network that's how<08:27:08.580> we're<08:27:08.760> going<08:27:08.878> to<08:27:09.000> get<08:27:09.058> better<08:27:09.240> routing 08:27:09.708 --> 08:27:09.718 align:start position:0% how we're going to get better routing 08:27:09.718 --> 08:27:11.570 align:start position:0% how we're going to get better routing efficiency<08:27:10.138> easier<08:27:10.920> management<08:27:11.218> and 08:27:11.570 --> 08:27:11.580 align:start position:0% efficiency easier management and 08:27:11.580 --> 08:27:13.610 align:start position:0% efficiency easier management and potentially<08:27:11.940> make<08:27:12.180> it<08:27:12.298> more<08:27:12.540> secure<08:27:12.840> because 08:27:13.610 --> 08:27:13.620 align:start position:0% potentially make it more secure because 08:27:13.620 --> 08:27:17.090 align:start position:0% potentially make it more secure because if<08:27:14.458> I<08:27:14.580> have<08:27:14.760> any<08:27:15.058> one<08:27:15.298> network<08:27:15.478> and<08:27:15.840> I<08:27:16.020> have<08:27:16.200> a 08:27:17.090 --> 08:27:17.100 align:start position:0% if I have any one network and I have a 08:27:17.100 --> 08:27:19.490 align:start position:0% if I have any one network and I have a let's<08:27:17.580> say<08:27:17.760> a<08:27:17.940> switch 08:27:19.490 --> 08:27:19.500 align:start position:0% let's say a switch 08:27:19.500 --> 08:27:22.128 align:start position:0% let's say a switch we'll<08:27:19.680> put<08:27:19.920> this<08:27:20.100> a<08:27:20.280> switch<08:27:20.540> and<08:27:21.540> it<08:27:21.718> has<08:27:21.840> four 08:27:22.128 --> 08:27:22.138 align:start position:0% we'll put this a switch and it has four 08:27:22.138 --> 08:27:23.868 align:start position:0% we'll put this a switch and it has four computers<08:27:22.620> on<08:27:22.798> it<08:27:22.920> and<08:27:23.100> then<08:27:23.218> I<08:27:23.398> have<08:27:23.520> another 08:27:23.868 --> 08:27:23.878 align:start position:0% computers on it and then I have another 08:27:23.878 --> 08:27:25.190 align:start position:0% computers on it and then I have another switch 08:27:25.190 --> 08:27:25.200 align:start position:0% switch 08:27:25.200 --> 08:27:30.948 align:start position:0% switch and<08:27:25.620> these<08:27:25.978> are<08:27:26.160> layer<08:27:26.458> 2<08:27:26.580> switches<08:27:27.600> okay 08:27:30.948 --> 08:27:30.958 align:start position:0% 08:27:30.958 --> 08:27:33.650 align:start position:0% and<08:27:31.680> each<08:27:31.978> of<08:27:32.100> these<08:27:32.340> let's<08:27:32.638> say<08:27:32.820> we<08:27:33.120> have<08:27:33.298> our 08:27:33.650 --> 08:27:33.660 align:start position:0% and each of these let's say we have our 08:27:33.660 --> 08:27:35.750 align:start position:0% and each of these let's say we have our different<08:27:33.840> subnets<08:27:34.558> then<08:27:35.218> I'm<08:27:35.398> going<08:27:35.580> to 08:27:35.750 --> 08:27:35.760 align:start position:0% different subnets then I'm going to 08:27:35.760 --> 08:27:38.750 align:start position:0% different subnets then I'm going to divide<08:27:36.058> these<08:27:36.420> up 08:27:38.750 --> 08:27:38.760 align:start position:0% 08:27:38.760 --> 08:27:41.330 align:start position:0% by<08:27:39.360> a<08:27:39.600> router<08:27:39.958> which<08:27:40.558> now<08:27:40.798> is<08:27:40.978> going<08:27:41.100> to<08:27:41.218> make 08:27:41.330 --> 08:27:41.340 align:start position:0% by a router which now is going to make 08:27:41.340 --> 08:27:43.730 align:start position:0% by a router which now is going to make sure<08:27:41.520> that<08:27:41.760> data<08:27:42.180> that's<08:27:42.360> going<08:27:42.600> here<08:27:42.958> kind<08:27:43.620> of 08:27:43.730 --> 08:27:43.740 align:start position:0% sure that data that's going here kind of 08:27:43.740 --> 08:27:46.128 align:start position:0% sure that data that's going here kind of gets<08:27:43.920> bounced<08:27:44.280> back<08:27:44.398> unless<08:27:44.760> it's<08:27:45.000> meant<08:27:45.420> for 08:27:46.128 --> 08:27:46.138 align:start position:0% gets bounced back unless it's meant for 08:27:46.138 --> 08:27:47.330 align:start position:0% gets bounced back unless it's meant for this<08:27:46.260> guy<08:27:46.440> and<08:27:46.620> this<08:27:46.798> way<08:27:46.978> we're<08:27:47.100> really 08:27:47.330 --> 08:27:47.340 align:start position:0% this guy and this way we're really 08:27:47.340 --> 08:27:49.788 align:start position:0% this guy and this way we're really reducing<08:27:47.820> the<08:27:48.240> traffic<08:27:48.600> on<08:27:49.020> it 08:27:49.788 --> 08:27:49.798 align:start position:0% reducing the traffic on it 08:27:49.798 --> 08:27:53.030 align:start position:0% reducing the traffic on it now<08:27:50.100> a<08:27:50.340> subnet<08:27:50.760> mask<08:27:50.958> is<08:27:51.958> like<08:27:52.378> an<08:27:52.558> IP<08:27:52.860> address 08:27:53.030 --> 08:27:53.040 align:start position:0% now a subnet mask is like an IP address 08:27:53.040 --> 08:27:57.468 align:start position:0% now a subnet mask is like an IP address a<08:27:53.940> 32-bit<08:27:54.718> binary<08:27:55.500> address<08:27:55.860> broken<08:27:56.700> up<08:27:57.000> into 08:27:57.468 --> 08:27:57.478 align:start position:0% a 32-bit binary address broken up into 08:27:57.478 --> 08:28:00.468 align:start position:0% a 32-bit binary address broken up into four<08:27:57.840> octets<08:27:58.440> and<08:27:58.978> a<08:27:59.160> dotted<08:27:59.520> decimal<08:28:00.058> format 08:28:00.468 --> 08:28:00.478 align:start position:0% four octets and a dotted decimal format 08:28:00.478 --> 08:28:03.170 align:start position:0% four octets and a dotted decimal format just<08:28:01.200> like<08:28:01.500> an<08:28:01.798> IP<08:28:02.100> address 08:28:03.170 --> 08:28:03.180 align:start position:0% just like an IP address 08:28:03.180 --> 08:28:06.110 align:start position:0% just like an IP address and<08:28:03.718> it's<08:28:03.898> used<08:28:04.200> to<08:28:04.620> separate<08:28:05.100> the<08:28:05.940> network 08:28:06.110 --> 08:28:06.120 align:start position:0% and it's used to separate the network 08:28:06.120 --> 08:28:08.930 align:start position:0% and it's used to separate the network portion<08:28:06.718> from<08:28:07.500> the<08:28:07.920> node<08:28:08.100> portion<08:28:08.580> I'm<08:28:08.760> going 08:28:08.930 --> 08:28:08.940 align:start position:0% portion from the node portion I'm going 08:28:08.940 --> 08:28:10.490 align:start position:0% portion from the node portion I'm going to show<08:28:09.120> you<08:28:09.180> how<08:28:09.478> that<08:28:09.600> works<08:28:09.958> in<08:28:10.260> just<08:28:10.378> a 08:28:10.490 --> 08:28:10.500 align:start position:0% to show you how that works in just a 08:28:10.500 --> 08:28:12.110 align:start position:0% to show you how that works in just a minute<08:28:10.680> and<08:28:11.160> it<08:28:11.280> involves<08:28:11.638> a<08:28:11.760> little<08:28:11.940> bit 08:28:12.110 --> 08:28:12.120 align:start position:0% minute and it involves a little bit 08:28:12.120 --> 08:28:13.548 align:start position:0% minute and it involves a little bit knowledge<08:28:12.420> of<08:28:12.600> binary<08:28:13.020> which<08:28:13.260> we've<08:28:13.378> already 08:28:13.548 --> 08:28:13.558 align:start position:0% knowledge of binary which we've already 08:28:13.558 --> 08:28:16.548 align:start position:0% knowledge of binary which we've already talked<08:28:13.860> about<08:28:14.458> so<08:28:14.940> the<08:28:15.180> subnet<08:28:15.600> mask<08:28:16.080> and<08:28:16.378> that 08:28:16.548 --> 08:28:16.558 align:start position:0% talked about so the subnet mask and that 08:28:16.558 --> 08:28:19.368 align:start position:0% talked about so the subnet mask and that name<08:28:16.740> mask<08:28:17.100> sort<08:28:17.580> of<08:28:17.700> lets<08:28:18.420> you<08:28:18.540> think<08:28:19.138> of<08:28:19.260> it 08:28:19.368 --> 08:28:19.378 align:start position:0% name mask sort of lets you think of it 08:28:19.378 --> 08:28:22.010 align:start position:0% name mask sort of lets you think of it as<08:28:19.500> being<08:28:19.740> put<08:28:19.978> onto<08:28:20.458> the<08:28:20.638> IP<08:28:21.000> address<08:28:21.180> is 08:28:22.010 --> 08:28:22.020 align:start position:0% as being put onto the IP address is 08:28:22.020 --> 08:28:24.708 align:start position:0% as being put onto the IP address is applied<08:28:22.378> to<08:28:22.500> that<08:28:22.620> IP<08:28:22.978> address<08:28:23.218> and<08:28:24.058> removes 08:28:24.708 --> 08:28:24.718 align:start position:0% applied to that IP address and removes 08:28:24.718 --> 08:28:27.468 align:start position:0% applied to that IP address and removes the<08:28:25.020> node<08:28:25.260> ID<08:28:25.620> the<08:28:26.520> subnet<08:28:26.878> mask<08:28:27.058> therefore 08:28:27.468 --> 08:28:27.478 align:start position:0% the node ID the subnet mask therefore 08:28:27.478 --> 08:28:30.350 align:start position:0% the node ID the subnet mask therefore eliminates<08:28:28.200> removes<08:28:29.040> an<08:28:29.218> entire<08:28:29.520> octet<08:28:30.120> of 08:28:30.350 --> 08:28:30.360 align:start position:0% eliminates removes an entire octet of 08:28:30.360 --> 08:28:33.230 align:start position:0% eliminates removes an entire octet of the<08:28:30.478> IP<08:28:30.718> address<08:28:30.898> by<08:28:31.860> using<08:28:32.280> eight<08:28:32.700> binary 08:28:33.230 --> 08:28:33.240 align:start position:0% the IP address by using eight binary 08:28:33.240 --> 08:28:36.468 align:start position:0% the IP address by using eight binary ones<08:28:33.780> or<08:28:34.080> 255<08:28:34.680> in<08:28:34.920> decimal<08:28:35.340> format<08:28:35.700> meaning 08:28:36.468 --> 08:28:36.478 align:start position:0% ones or 255 in decimal format meaning 08:28:36.478 --> 08:28:40.368 align:start position:0% ones or 255 in decimal format meaning that<08:28:37.138> this<08:28:37.378> 255<08:28:38.160> if<08:28:38.520> we<08:28:38.638> add<08:28:38.820> it<08:28:39.000> up<08:28:39.180> in<08:28:39.298> binary 08:28:40.368 --> 08:28:40.378 align:start position:0% that this 255 if we add it up in binary 08:28:40.378 --> 08:28:43.730 align:start position:0% that this 255 if we add it up in binary would<08:28:40.978> be<08:28:41.100> one<08:28:41.458> two<08:28:41.760> three<08:28:42.240> four<08:28:42.780> five<08:28:43.260> six 08:28:43.730 --> 08:28:43.740 align:start position:0% would be one two three four five six 08:28:43.740 --> 08:28:45.770 align:start position:0% would be one two three four five six seven<08:28:44.218> eight 08:28:45.770 --> 08:28:45.780 align:start position:0% seven eight 08:28:45.780 --> 08:28:49.208 align:start position:0% seven eight one<08:28:46.500> two<08:28:46.798> three<08:28:47.218> four<08:28:47.638> five<08:28:48.058> six<08:28:48.420> seven<08:28:48.780> eight 08:28:49.208 --> 08:28:49.218 align:start position:0% one two three four five six seven eight 08:28:49.218 --> 08:28:52.788 align:start position:0% one two three four five six seven eight one<08:28:50.218> two<08:28:50.520> three<08:28:50.878> four<08:28:51.298> five<08:28:51.718> six<08:28:52.080> seven<08:28:52.440> eight 08:28:52.788 --> 08:28:52.798 align:start position:0% one two three four five six seven eight 08:28:52.798 --> 08:28:56.030 align:start position:0% one two three four five six seven eight and<08:28:53.700> then<08:28:53.878> this<08:28:54.298> would<08:28:54.718> be<08:28:54.898> one<08:28:55.378> two<08:28:55.680> three 08:28:56.030 --> 08:28:56.040 align:start position:0% and then this would be one two three 08:28:56.040 --> 08:28:58.788 align:start position:0% and then this would be one two three four<08:28:56.520> five<08:28:57.000> six<08:28:57.360> seven<08:28:57.660> eight<08:28:57.958> so<08:28:58.500> meaning 08:28:58.788 --> 08:28:58.798 align:start position:0% four five six seven eight so meaning 08:28:58.798 --> 08:29:02.448 align:start position:0% four five six seven eight so meaning that<08:28:59.040> a<08:28:59.218> 255<08:29:00.020> equals<08:29:01.020> eight 08:29:02.448 --> 08:29:02.458 align:start position:0% that a 255 equals eight 08:29:02.458 --> 08:29:04.968 align:start position:0% that a 255 equals eight ones<08:29:03.180> which<08:29:03.898> is<08:29:03.958> the<08:29:04.080> reason<08:29:04.200> why<08:29:04.500> an<08:29:04.740> IP 08:29:04.968 --> 08:29:04.978 align:start position:0% ones which is the reason why an IP 08:29:04.978 --> 08:29:08.690 align:start position:0% ones which is the reason why an IP address<08:29:05.160> can<08:29:05.520> never<08:29:05.700> be<08:29:06.320> 255.<08:29:07.320> and<08:29:08.160> if<08:29:08.458> this<08:29:08.580> is 08:29:08.690 --> 08:29:08.700 align:start position:0% address can never be 255. and if this is 08:29:08.700 --> 08:29:09.830 align:start position:0% address can never be 255. and if this is a<08:29:08.760> little<08:29:08.820> confusing<08:29:09.180> that's<08:29:09.420> okay<08:29:09.540> we're 08:29:09.830 --> 08:29:09.840 align:start position:0% a little confusing that's okay we're 08:29:09.840 --> 08:29:12.110 align:start position:0% a little confusing that's okay we're about<08:29:10.020> to<08:29:10.200> clarify<08:29:10.620> that<08:29:10.798> in<08:29:10.978> just<08:29:11.100> a<08:29:11.280> second 08:29:12.110 --> 08:29:12.120 align:start position:0% about to clarify that in just a second 08:29:12.120 --> 08:29:16.968 align:start position:0% about to clarify that in just a second so<08:29:13.160> IP<08:29:14.160> addresses<08:29:15.058> IP<08:29:15.840> address<08:29:16.020> assignments 08:29:16.968 --> 08:29:16.978 align:start position:0% so IP addresses IP address assignments 08:29:16.978 --> 08:29:19.910 align:start position:0% so IP addresses IP address assignments and<08:29:17.160> subnet<08:29:17.700> masks<08:29:18.120> all<08:29:18.478> have<08:29:18.660> to<08:29:18.840> follow<08:29:19.080> a 08:29:19.910 --> 08:29:19.920 align:start position:0% and subnet masks all have to follow a 08:29:19.920 --> 08:29:21.590 align:start position:0% and subnet masks all have to follow a certain<08:29:20.218> set<08:29:20.458> of<08:29:20.580> rules<08:29:21.000> I'm<08:29:21.420> going<08:29:21.540> to 08:29:21.590 --> 08:29:21.600 align:start position:0% certain set of rules I'm going to 08:29:21.600 --> 08:29:22.968 align:start position:0% certain set of rules I'm going to describe<08:29:22.020> the<08:29:22.138> rules<08:29:22.378> and<08:29:22.558> then<08:29:22.680> I'm<08:29:22.798> going<08:29:22.920> to 08:29:22.968 --> 08:29:22.978 align:start position:0% describe the rules and then I'm going to 08:29:22.978 --> 08:29:25.128 align:start position:0% describe the rules and then I'm going to apply<08:29:23.340> them<08:29:23.580> so<08:29:24.120> if<08:29:24.420> some<08:29:24.540> of<08:29:24.660> this<08:29:24.780> is<08:29:24.958> a 08:29:25.128 --> 08:29:25.138 align:start position:0% apply them so if some of this is a 08:29:25.138 --> 08:29:26.990 align:start position:0% apply them so if some of this is a little<08:29:25.200> confusing<08:29:25.620> or<08:29:25.798> over<08:29:25.978> your<08:29:26.160> head<08:29:26.398> keep 08:29:26.990 --> 08:29:27.000 align:start position:0% little confusing or over your head keep 08:29:27.000 --> 08:29:28.788 align:start position:0% little confusing or over your head keep paying<08:29:27.360> attention<08:29:27.660> keep<08:29:28.080> with<08:29:28.260> me<08:29:28.440> and<08:29:28.680> I 08:29:28.788 --> 08:29:28.798 align:start position:0% paying attention keep with me and I 08:29:28.798 --> 08:29:30.650 align:start position:0% paying attention keep with me and I think<08:29:28.920> it's<08:29:29.040> going<08:29:29.218> to<08:29:29.280> clarify<08:29:29.760> itself 08:29:30.650 --> 08:29:30.660 align:start position:0% think it's going to clarify itself 08:29:30.660 --> 08:29:35.090 align:start position:0% think it's going to clarify itself the<08:29:31.260> first<08:29:31.440> is<08:29:32.160> that<08:29:32.520> the<08:29:33.120> ones<08:29:33.540> in<08:29:34.440> a<08:29:34.680> subnet 08:29:35.090 --> 08:29:35.100 align:start position:0% the first is that the ones in a subnet 08:29:35.100 --> 08:29:38.288 align:start position:0% the first is that the ones in a subnet mask<08:29:35.398> will<08:29:36.240> always<08:29:36.478> start<08:29:36.958> at<08:29:37.740> the<08:29:37.920> left 08:29:38.288 --> 08:29:38.298 align:start position:0% mask will always start at the left 08:29:38.298 --> 08:29:42.730 align:start position:0% mask will always start at the left meaning<08:29:39.298> the<08:29:40.200> first<08:29:40.378> octet<08:29:41.100> will<08:29:41.820> always<08:29:42.120> be 08:29:42.730 --> 08:29:42.740 align:start position:0% meaning the first octet will always be 08:29:42.740 --> 08:29:48.230 align:start position:0% meaning the first octet will always be 255<08:29:43.740> or<08:29:44.398> 8<08:29:44.638> binary<08:29:45.120> ones<08:29:45.540> so<08:29:46.440> my<08:29:47.218> I<08:29:47.458> my<08:29:47.820> subnet 08:29:48.230 --> 08:29:48.240 align:start position:0% 255 or 8 binary ones so my I my subnet 08:29:48.240 --> 08:29:49.548 align:start position:0% 255 or 8 binary ones so my I my subnet mask<08:29:48.420> I'm<08:29:48.660> always<08:29:48.780> going<08:29:48.958> to<08:29:49.020> start<08:29:49.200> at<08:29:49.378> the 08:29:49.548 --> 08:29:49.558 align:start position:0% mask I'm always going to start at the 08:29:49.558 --> 08:29:57.650 align:start position:0% mask I'm always going to start at the left<08:29:49.680> when<08:29:49.920> I'm<08:29:50.100> writing<08:29:50.398> it<08:29:50.520> out 08:29:57.650 --> 08:29:57.660 align:start position:0% 08:29:57.660 --> 08:30:00.530 align:start position:0% this<08:29:58.440> says<08:29:58.860> that<08:29:59.218> the<08:29:59.398> first<08:29:59.580> octet<08:30:00.058> is<08:30:00.360> going 08:30:00.530 --> 08:30:00.540 align:start position:0% this says that the first octet is going 08:30:00.540 --> 08:30:03.468 align:start position:0% this says that the first octet is going to<08:30:00.660> be<08:30:00.718> 255<08:30:01.440> which<08:30:01.740> means<08:30:02.040> 8<08:30:02.398> Bits 08:30:03.468 --> 08:30:03.478 align:start position:0% to be 255 which means 8 Bits 08:30:03.478 --> 08:30:05.990 align:start position:0% to be 255 which means 8 Bits now<08:30:03.958> the<08:30:04.260> zeros<08:30:04.620> of<08:30:04.860> the<08:30:05.040> Mask<08:30:05.160> will<08:30:05.820> always 08:30:05.990 --> 08:30:06.000 align:start position:0% now the zeros of the Mask will always 08:30:06.000 --> 08:30:07.070 align:start position:0% now the zeros of the Mask will always start 08:30:07.070 --> 08:30:07.080 align:start position:0% start 08:30:07.080 --> 08:30:08.810 align:start position:0% start at<08:30:07.680> the<08:30:07.920> one<08:30:08.040> bit 08:30:08.810 --> 08:30:08.820 align:start position:0% at the one bit 08:30:08.820 --> 08:30:10.968 align:start position:0% at the one bit or<08:30:09.298> all<08:30:09.540> the<08:30:09.660> way<08:30:09.660> on<08:30:09.898> the<08:30:10.080> right 08:30:10.968 --> 08:30:10.978 align:start position:0% or all the way on the right 08:30:10.978 --> 08:30:13.070 align:start position:0% or all the way on the right meaning<08:30:11.580> that<08:30:12.120> I'm<08:30:12.298> going<08:30:12.420> to<08:30:12.478> have<08:30:12.600> zeros 08:30:13.070 --> 08:30:13.080 align:start position:0% meaning that I'm going to have zeros 08:30:13.080 --> 08:30:14.628 align:start position:0% meaning that I'm going to have zeros from<08:30:13.320> the<08:30:13.440> right 08:30:14.628 --> 08:30:14.638 align:start position:0% from the right 08:30:14.638 --> 08:30:16.670 align:start position:0% from the right and<08:30:15.120> ones<08:30:15.478> from<08:30:15.718> the<08:30:15.840> left 08:30:16.670 --> 08:30:16.680 align:start position:0% and ones from the left 08:30:16.680 --> 08:30:19.730 align:start position:0% and ones from the left and<08:30:17.280> the<08:30:17.700> ones<08:30:18.120> in<08:30:18.718> The<08:30:18.840> Mask<08:30:19.020> have<08:30:19.378> to<08:30:19.620> be 08:30:19.730 --> 08:30:19.740 align:start position:0% and the ones in The Mask have to be 08:30:19.740 --> 08:30:23.990 align:start position:0% and the ones in The Mask have to be adjoining<08:30:20.780> adjoining<08:30:21.780> or<08:30:22.138> con<08:30:22.558> consistent<08:30:23.340> or 08:30:23.990 --> 08:30:24.000 align:start position:0% adjoining adjoining or con consistent or 08:30:24.000 --> 08:30:26.090 align:start position:0% adjoining adjoining or con consistent or continuous<08:30:24.540> or<08:30:24.898> contiguous<08:30:25.440> whichever<08:30:25.860> word 08:30:26.090 --> 08:30:26.100 align:start position:0% continuous or contiguous whichever word 08:30:26.100 --> 08:30:28.850 align:start position:0% continuous or contiguous whichever word you<08:30:26.340> want<08:30:26.458> to<08:30:26.580> use<08:30:26.760> meaning<08:30:27.540> once<08:30:28.138> there<08:30:28.320> is<08:30:28.500> a 08:30:28.850 --> 08:30:28.860 align:start position:0% you want to use meaning once there is a 08:30:28.860 --> 08:30:32.930 align:start position:0% you want to use meaning once there is a zero<08:30:29.280> we<08:30:30.240> cannot<08:30:30.660> then<08:30:31.080> go<08:30:31.440> back<08:30:31.680> to<08:30:31.920> ones<08:30:32.340> so 08:30:32.930 --> 08:30:32.940 align:start position:0% zero we cannot then go back to ones so 08:30:32.940 --> 08:30:34.850 align:start position:0% zero we cannot then go back to ones so we're<08:30:33.058> not<08:30:33.180> going<08:30:33.360> to<08:30:33.420> see<08:30:33.600> like<08:30:33.898> this<08:30:34.620> sort<08:30:34.798> of 08:30:34.850 --> 08:30:34.860 align:start position:0% we're not going to see like this sort of 08:30:34.860 --> 08:30:36.888 align:start position:0% we're not going to see like this sort of thing<08:30:35.100> happen 08:30:36.888 --> 08:30:36.898 align:start position:0% thing happen 08:30:36.898 --> 08:30:39.948 align:start position:0% thing happen in<08:30:37.620> fact<08:30:37.740> we<08:30:38.218> have<08:30:38.340> to<08:30:38.580> have<08:30:38.820> continuous<08:30:39.540> ones 08:30:39.948 --> 08:30:39.958 align:start position:0% in fact we have to have continuous ones 08:30:39.958 --> 08:30:42.888 align:start position:0% in fact we have to have continuous ones from<08:30:40.138> the<08:30:40.320> left<08:30:40.500> and<08:30:41.458> continuous<08:30:41.878> zeros<08:30:42.360> from 08:30:42.888 --> 08:30:42.898 align:start position:0% from the left and continuous zeros from 08:30:42.898 --> 08:30:43.730 align:start position:0% from the left and continuous zeros from the<08:30:43.080> right 08:30:43.730 --> 08:30:43.740 align:start position:0% the right 08:30:43.740 --> 08:30:45.948 align:start position:0% the right this<08:30:44.160> is<08:30:44.280> the<08:30:44.458> only<08:30:44.580> way<08:30:44.760> a<08:30:45.120> subnet<08:30:45.420> mask<08:30:45.660> is 08:30:45.948 --> 08:30:45.958 align:start position:0% this is the only way a subnet mask is 08:30:45.958 --> 08:30:47.990 align:start position:0% this is the only way a subnet mask is going<08:30:46.138> to<08:30:46.260> work<08:30:46.378> and<08:30:46.978> I'll<08:30:47.100> talk<08:30:47.280> about<08:30:47.458> why<08:30:47.760> in 08:30:47.990 --> 08:30:48.000 align:start position:0% going to work and I'll talk about why in 08:30:48.000 --> 08:30:49.788 align:start position:0% going to work and I'll talk about why in just<08:30:48.180> a<08:30:48.298> minute 08:30:49.788 --> 08:30:49.798 align:start position:0% just a minute 08:30:49.798 --> 08:30:52.490 align:start position:0% just a minute also<08:30:50.638> if<08:30:50.760> there<08:30:50.940> is<08:30:51.058> more<08:30:51.240> than<08:30:51.420> one<08:30:51.718> subnet<08:30:52.200> on 08:30:52.490 --> 08:30:52.500 align:start position:0% also if there is more than one subnet on 08:30:52.500 --> 08:30:55.788 align:start position:0% also if there is more than one subnet on a<08:30:52.620> network<08:30:53.000> every<08:30:54.000> subnet<08:30:54.478> has<08:30:54.898> to<08:30:55.080> have<08:30:55.378> a 08:30:55.788 --> 08:30:55.798 align:start position:0% a network every subnet has to have a 08:30:55.798 --> 08:30:58.850 align:start position:0% a network every subnet has to have a unique<08:30:56.160> network<08:30:56.878> ID<08:30:57.420> and<08:30:58.200> I'll<08:30:58.378> explain<08:30:58.558> this 08:30:58.850 --> 08:30:58.860 align:start position:0% unique network ID and I'll explain this 08:30:58.860 --> 08:31:01.910 align:start position:0% unique network ID and I'll explain this in<08:30:59.040> a<08:30:59.218> bit<08:30:59.340> but<08:30:59.760> it<08:30:59.940> makes<08:31:00.058> sense<08:31:00.298> if<08:31:00.718> I<08:31:00.898> have<08:31:01.138> a 08:31:01.910 --> 08:31:01.920 align:start position:0% in a bit but it makes sense if I have a 08:31:01.920 --> 08:31:04.250 align:start position:0% in a bit but it makes sense if I have a different<08:31:02.458> network<08:31:02.820> IDs 08:31:04.250 --> 08:31:04.260 align:start position:0% different network IDs 08:31:04.260 --> 08:31:06.888 align:start position:0% different network IDs then<08:31:04.680> I'm<08:31:04.860> not<08:31:05.100> really<08:31:05.458> I'm<08:31:06.360> sorry<08:31:06.540> if<08:31:06.660> I<08:31:06.780> have 08:31:06.888 --> 08:31:06.898 align:start position:0% then I'm not really I'm sorry if I have 08:31:06.898 --> 08:31:09.048 align:start position:0% then I'm not really I'm sorry if I have similar<08:31:07.320> Network<08:31:07.500> IDs<08:31:08.040> then<08:31:08.458> I'm<08:31:08.638> not<08:31:08.820> really 08:31:09.048 --> 08:31:09.058 align:start position:0% similar Network IDs then I'm not really 08:31:09.058 --> 08:31:11.150 align:start position:0% similar Network IDs then I'm not really dealing<08:31:09.478> with<08:31:09.780> multiple<08:31:10.620> networks<08:31:10.978> I'm 08:31:11.150 --> 08:31:11.160 align:start position:0% dealing with multiple networks I'm 08:31:11.160 --> 08:31:12.770 align:start position:0% dealing with multiple networks I'm dealing<08:31:11.458> with<08:31:11.580> the<08:31:11.760> same<08:31:11.940> network 08:31:12.770 --> 08:31:12.780 align:start position:0% dealing with the same network 08:31:12.780 --> 08:31:15.770 align:start position:0% dealing with the same network now<08:31:13.320> assignment<08:31:13.860> of<08:31:14.100> IP<08:31:14.458> addresses<08:31:15.058> have<08:31:15.600> to 08:31:15.770 --> 08:31:15.780 align:start position:0% now assignment of IP addresses have to 08:31:15.780 --> 08:31:17.448 align:start position:0% now assignment of IP addresses have to follow<08:31:16.020> a<08:31:16.260> few<08:31:16.440> more<08:31:16.620> rules<08:31:16.920> so<08:31:17.040> these<08:31:17.280> are<08:31:17.340> the 08:31:17.448 --> 08:31:17.458 align:start position:0% follow a few more rules so these are the 08:31:17.458 --> 08:31:20.270 align:start position:0% follow a few more rules so these are the subnet<08:31:17.820> masks<08:31:18.660> first<08:31:19.138> there<08:31:19.620> cannot<08:31:19.920> be<08:31:20.040> any 08:31:20.270 --> 08:31:20.280 align:start position:0% subnet masks first there cannot be any 08:31:20.280 --> 08:31:23.170 align:start position:0% subnet masks first there cannot be any duplicate<08:31:20.878> IP<08:31:21.420> addresses<08:31:22.020> on<08:31:22.798> the<08:31:22.920> network 08:31:23.170 --> 08:31:23.180 align:start position:0% duplicate IP addresses on the network 08:31:23.180 --> 08:31:26.150 align:start position:0% duplicate IP addresses on the network this<08:31:24.180> means<08:31:24.600> that<08:31:25.020> every<08:31:25.378> Network<08:31:25.620> every 08:31:26.150 --> 08:31:26.160 align:start position:0% this means that every Network every 08:31:26.160 --> 08:31:29.448 align:start position:0% this means that every Network every device<08:31:26.458> has<08:31:26.820> to<08:31:27.000> have<08:31:27.120> its<08:31:27.540> own<08:31:27.718> unique 08:31:29.448 --> 08:31:29.458 align:start position:0% device has to have its own unique 08:31:29.458 --> 08:31:32.810 align:start position:0% device has to have its own unique IP<08:31:30.120> address<08:31:30.440> we<08:31:31.440> cannot<08:31:31.740> have<08:31:32.100> more<08:31:32.458> than<08:31:32.638> one 08:31:32.810 --> 08:31:32.820 align:start position:0% IP address we cannot have more than one 08:31:32.820 --> 08:31:35.030 align:start position:0% IP address we cannot have more than one device<08:31:33.058> with<08:31:33.660> the<08:31:33.898> same<08:31:34.020> IP<08:31:34.378> address<08:31:34.500> if<08:31:34.798> we<08:31:34.920> do 08:31:35.030 --> 08:31:35.040 align:start position:0% device with the same IP address if we do 08:31:35.040 --> 08:31:36.770 align:start position:0% device with the same IP address if we do they're<08:31:35.280> not<08:31:35.398> going<08:31:35.520> to<08:31:35.580> communicate<08:31:36.240> because 08:31:36.770 --> 08:31:36.780 align:start position:0% they're not going to communicate because 08:31:36.780 --> 08:31:38.810 align:start position:0% they're not going to communicate because the<08:31:37.080> switches<08:31:37.500> won't<08:31:37.860> know<08:31:38.100> where<08:31:38.458> to<08:31:38.638> send 08:31:38.810 --> 08:31:38.820 align:start position:0% the switches won't know where to send 08:31:38.820 --> 08:31:42.708 align:start position:0% the switches won't know where to send packets<08:31:39.378> next<08:31:40.378> if<08:31:41.160> there<08:31:41.398> are<08:31:41.580> subnets<08:31:42.058> every 08:31:42.708 --> 08:31:42.718 align:start position:0% packets next if there are subnets every 08:31:42.718 --> 08:31:45.048 align:start position:0% packets next if there are subnets every node<08:31:43.080> must<08:31:43.500> be<08:31:43.740> assigned<08:31:44.280> to<08:31:44.580> one<08:31:44.820> of<08:31:44.940> them 08:31:45.048 --> 08:31:45.058 align:start position:0% node must be assigned to one of them 08:31:45.058 --> 08:31:48.170 align:start position:0% node must be assigned to one of them meaning<08:31:45.898> that<08:31:46.620> every<08:31:47.040> address<08:31:47.398> every<08:31:47.820> IP 08:31:48.170 --> 08:31:48.180 align:start position:0% meaning that every address every IP 08:31:48.180 --> 08:31:50.330 align:start position:0% meaning that every address every IP address<08:31:48.420> has<08:31:48.840> to<08:31:49.020> be<08:31:49.138> assigned<08:31:49.620> to<08:31:49.860> a<08:31:50.040> specific 08:31:50.330 --> 08:31:50.340 align:start position:0% address has to be assigned to a specific 08:31:50.340 --> 08:31:52.388 align:start position:0% address has to be assigned to a specific Network 08:31:52.388 --> 08:31:52.398 align:start position:0% Network 08:31:52.398 --> 08:31:56.510 align:start position:0% Network now<08:31:53.398> the<08:31:53.820> address<08:31:54.000> of<08:31:54.360> a<08:31:54.540> known<08:31:54.740> cannot<08:31:55.740> be<08:31:55.978> all 08:31:56.510 --> 08:31:56.520 align:start position:0% now the address of a known cannot be all 08:31:56.520 --> 08:31:59.030 align:start position:0% now the address of a known cannot be all ones<08:31:56.940> or<08:31:57.058> all<08:31:57.240> zeros<08:31:57.660> remember<08:31:58.200> all<08:31:58.680> ones 08:31:59.030 --> 08:31:59.040 align:start position:0% ones or all zeros remember all ones 08:31:59.040 --> 08:32:02.770 align:start position:0% ones or all zeros remember all ones would<08:31:59.340> be<08:31:59.458> 255.<08:32:00.898> all<08:32:01.440> zeros<08:32:01.860> would<08:32:02.100> be<08:32:02.218> just 08:32:02.770 --> 08:32:02.780 align:start position:0% would be 255. all zeros would be just 08:32:02.780 --> 08:32:05.628 align:start position:0% would be 255. all zeros would be just 0.0.0.0<08:32:03.780> so<08:32:04.138> I<08:32:04.320> cannot<08:32:04.620> have<08:32:04.860> an<08:32:05.160> IP<08:32:05.398> address 08:32:05.628 --> 08:32:05.638 align:start position:0% 0.0.0.0 so I cannot have an IP address 08:32:05.638 --> 08:32:08.888 align:start position:0% 0.0.0.0 so I cannot have an IP address that<08:32:06.000> is<08:32:06.180> either 08:32:08.888 --> 08:32:08.898 align:start position:0% 08:32:08.898 --> 08:32:12.430 align:start position:0% 255.255.255<08:32:09.920> or<08:32:10.920> that<08:32:11.340> can<08:32:11.580> be 08:32:12.430 --> 08:32:12.440 align:start position:0% 255.255.255 or that can be 08:32:12.440 --> 08:32:15.410 align:start position:0% 255.255.255 or that can be 0.0.0.0<08:32:13.440> and<08:32:14.218> you'll<08:32:14.520> see<08:32:14.700> why<08:32:14.940> when<08:32:15.180> we<08:32:15.298> get 08:32:15.410 --> 08:32:15.420 align:start position:0% 0.0.0.0 and you'll see why when we get 08:32:15.420 --> 08:32:17.270 align:start position:0% 0.0.0.0 and you'll see why when we get to<08:32:15.540> the<08:32:15.660> mathematics<08:32:16.320> of<08:32:16.500> this<08:32:16.680> in<08:32:16.978> just<08:32:17.100> a 08:32:17.270 --> 08:32:17.280 align:start position:0% to the mathematics of this in just a 08:32:17.280 --> 08:32:19.070 align:start position:0% to the mathematics of this in just a second<08:32:17.458> it's<08:32:18.058> because<08:32:18.298> then<08:32:18.600> I<08:32:18.780> would<08:32:18.898> never 08:32:19.070 --> 08:32:19.080 align:start position:0% second it's because then I would never 08:32:19.080 --> 08:32:22.010 align:start position:0% second it's because then I would never be<08:32:19.320> able<08:32:19.500> to<08:32:19.620> determine<08:32:20.218> a<08:32:20.878> network<08:32:21.180> ID<08:32:21.478> from<08:32:21.898> a 08:32:22.010 --> 08:32:22.020 align:start position:0% be able to determine a network ID from a 08:32:22.020 --> 08:32:23.330 align:start position:0% be able to determine a network ID from a node<08:32:22.260> ID 08:32:23.330 --> 08:32:23.340 align:start position:0% node ID 08:32:23.340 --> 08:32:25.610 align:start position:0% node ID finally<08:32:24.180> and<08:32:24.660> this<08:32:24.840> is<08:32:24.958> something<08:32:25.200> you<08:32:25.440> sort 08:32:25.610 --> 08:32:25.620 align:start position:0% finally and this is something you sort 08:32:25.620 --> 08:32:27.830 align:start position:0% finally and this is something you sort of<08:32:25.740> have<08:32:25.798> to<08:32:25.920> remember<08:32:26.040> the<08:32:26.878> IP<08:32:27.180> address<08:32:27.360> can 08:32:27.830 --> 08:32:27.840 align:start position:0% of have to remember the IP address can 08:32:27.840 --> 08:32:29.888 align:start position:0% of have to remember the IP address can never<08:32:28.080> be 08:32:29.888 --> 08:32:29.898 align:start position:0% never be 08:32:29.898 --> 08:32:33.708 align:start position:0% never be 127.0.0.1<08:32:30.898> we've<08:32:31.620> talked<08:32:31.860> about<08:32:31.920> this<08:32:32.340> in<08:32:33.718> um 08:32:33.708 --> 08:32:33.718 align:start position:0% 127.0.0.1 we've talked about this in um 08:32:33.718 --> 08:32:35.330 align:start position:0% 127.0.0.1 we've talked about this in um a<08:32:33.958> plus<08:32:34.138> but<08:32:34.440> that's<08:32:34.558> because<08:32:34.740> this<08:32:35.040> is<08:32:35.160> what's 08:32:35.330 --> 08:32:35.340 align:start position:0% a plus but that's because this is what's 08:32:35.340 --> 08:32:37.910 align:start position:0% a plus but that's because this is what's called<08:32:35.580> the<08:32:35.878> loopback<08:32:36.298> it's<08:32:36.660> a<08:32:36.898> reserved<08:32:37.440> IP 08:32:37.910 --> 08:32:37.920 align:start position:0% called the loopback it's a reserved IP 08:32:37.920 --> 08:32:40.670 align:start position:0% called the loopback it's a reserved IP address<08:32:38.420> specifically<08:32:39.420> for<08:32:39.780> yourself<08:32:40.080> be 08:32:40.670 --> 08:32:40.680 align:start position:0% address specifically for yourself be 08:32:40.680 --> 08:32:44.990 align:start position:0% address specifically for yourself be like<08:32:40.860> saying<08:32:41.218> me<08:32:41.398> myself<08:32:41.760> or<08:32:42.360> I<08:32:42.600> I<08:32:43.378> cannot<08:32:44.000> have 08:32:44.990 --> 08:32:45.000 align:start position:0% like saying me myself or I I cannot have 08:32:45.000 --> 08:32:47.288 align:start position:0% like saying me myself or I I cannot have a<08:32:45.660> a 08:32:47.288 --> 08:32:47.298 align:start position:0% a a 08:32:47.298 --> 08:32:50.030 align:start position:0% a a 127.0.0.1<08:32:48.298> IP<08:32:49.080> address<08:32:49.260> assigned<08:32:49.798> to<08:32:49.920> a 08:32:50.030 --> 08:32:50.040 align:start position:0% 127.0.0.1 IP address assigned to a 08:32:50.040 --> 08:32:52.368 align:start position:0% 127.0.0.1 IP address assigned to a device<08:32:50.218> because<08:32:50.580> every<08:32:51.000> device<08:32:51.240> calls<08:32:52.020> itself 08:32:52.368 --> 08:32:52.378 align:start position:0% device because every device calls itself 08:32:52.378 --> 08:32:55.310 align:start position:0% device because every device calls itself 127.0.0.1 08:32:55.310 --> 08:32:55.320 align:start position:0% 127.0.0.1 08:32:55.320 --> 08:32:57.830 align:start position:0% 127.0.0.1 now<08:32:55.920> besides<08:32:56.520> understanding<08:32:57.240> these<08:32:57.540> rules 08:32:57.830 --> 08:32:57.840 align:start position:0% now besides understanding these rules 08:32:57.840 --> 08:33:00.230 align:start position:0% now besides understanding these rules which<08:32:58.138> are<08:32:58.260> a<08:32:58.378> bit<08:32:58.558> abstract<08:32:58.978> I<08:32:59.280> think<08:32:59.520> we<08:33:00.120> need 08:33:00.230 --> 08:33:00.240 align:start position:0% which are a bit abstract I think we need 08:33:00.240 --> 08:33:02.208 align:start position:0% which are a bit abstract I think we need to<08:33:00.360> know<08:33:00.478> how<08:33:00.718> to<08:33:00.898> apply<08:33:01.200> them<08:33:01.440> and<08:33:01.920> how<08:33:02.100> to 08:33:02.208 --> 08:33:02.218 align:start position:0% to know how to apply them and how to 08:33:02.218 --> 08:33:04.850 align:start position:0% to know how to apply them and how to apply<08:33:02.580> a<08:33:02.820> subnet<08:33:03.180> mask<08:33:03.360> to<08:33:03.718> an<08:33:03.840> IP<08:33:04.080> address<08:33:04.260> I 08:33:04.850 --> 08:33:04.860 align:start position:0% apply a subnet mask to an IP address I 08:33:04.860 --> 08:33:05.810 align:start position:0% apply a subnet mask to an IP address I think<08:33:04.920> it's<08:33:05.040> going<08:33:05.218> to<08:33:05.280> make<08:33:05.398> some<08:33:05.580> of<08:33:05.700> these 08:33:05.810 --> 08:33:05.820 align:start position:0% think it's going to make some of these 08:33:05.820 --> 08:33:07.310 align:start position:0% think it's going to make some of these rules<08:33:06.120> a<08:33:06.240> little<08:33:06.360> clearer<08:33:06.660> so<08:33:06.840> let's<08:33:06.958> take<08:33:07.200> a 08:33:07.310 --> 08:33:07.320 align:start position:0% rules a little clearer so let's take a 08:33:07.320 --> 08:33:10.010 align:start position:0% rules a little clearer so let's take a look<08:33:07.378> at<08:33:07.558> those<08:33:07.680> now<08:33:08.280> when<08:33:08.580> a<08:33:08.700> subnet<08:33:09.058> mask<08:33:09.360> is 08:33:10.010 --> 08:33:10.020 align:start position:0% look at those now when a subnet mask is 08:33:10.020 --> 08:33:12.350 align:start position:0% look at those now when a subnet mask is applied<08:33:10.440> to<08:33:10.798> an<08:33:10.978> IP<08:33:11.218> address 08:33:12.350 --> 08:33:12.360 align:start position:0% applied to an IP address 08:33:12.360 --> 08:33:14.930 align:start position:0% applied to an IP address the<08:33:12.898> remainder<08:33:13.378> is<08:33:14.040> the<08:33:14.218> network<08:33:14.340> portion 08:33:14.930 --> 08:33:14.940 align:start position:0% the remainder is the network portion 08:33:14.940 --> 08:33:16.968 align:start position:0% the remainder is the network portion meaning<08:33:15.478> when<08:33:15.780> we<08:33:15.898> take<08:33:16.020> the<08:33:16.260> IP<08:33:16.500> address<08:33:16.680> and 08:33:16.968 --> 08:33:16.978 align:start position:0% meaning when we take the IP address and 08:33:16.978 --> 08:33:18.468 align:start position:0% meaning when we take the IP address and we<08:33:17.160> apply<08:33:17.398> the<08:33:17.520> subnet<08:33:17.878> mask<08:33:18.058> and<08:33:18.240> I'll<08:33:18.360> show 08:33:18.468 --> 08:33:18.478 align:start position:0% we apply the subnet mask and I'll show 08:33:18.478 --> 08:33:20.270 align:start position:0% we apply the subnet mask and I'll show you<08:33:18.540> how<08:33:18.600> to<08:33:18.718> do<08:33:18.780> that<08:33:18.898> in<08:33:19.020> a<08:33:19.138> second<08:33:19.378> what<08:33:20.160> we 08:33:20.270 --> 08:33:20.280 align:start position:0% you how to do that in a second what we 08:33:20.280 --> 08:33:22.070 align:start position:0% you how to do that in a second what we get<08:33:20.458> as<08:33:20.638> a<08:33:20.820> remainder<08:33:21.180> what's<08:33:21.420> left<08:33:21.660> over<08:33:21.840> is 08:33:22.070 --> 08:33:22.080 align:start position:0% get as a remainder what's left over is 08:33:22.080 --> 08:33:24.170 align:start position:0% get as a remainder what's left over is going<08:33:22.260> to<08:33:22.320> be<08:33:22.378> the<08:33:22.620> network<08:33:22.798> ID<08:33:23.160> this<08:33:23.878> allows 08:33:24.170 --> 08:33:24.180 align:start position:0% going to be the network ID this allows 08:33:24.180 --> 08:33:26.030 align:start position:0% going to be the network ID this allows us<08:33:24.298> to<08:33:24.478> then<08:33:24.600> determine<08:33:25.080> what<08:33:25.260> the<08:33:25.440> node<08:33:25.620> ID<08:33:25.798> is 08:33:26.030 --> 08:33:26.040 align:start position:0% us to then determine what the node ID is 08:33:26.040 --> 08:33:27.468 align:start position:0% us to then determine what the node ID is this<08:33:26.340> will<08:33:26.458> make<08:33:26.638> more<08:33:26.760> sense<08:33:26.940> in<08:33:27.120> just<08:33:27.298> a 08:33:27.468 --> 08:33:27.478 align:start position:0% this will make more sense in just a 08:33:27.478 --> 08:33:28.968 align:start position:0% this will make more sense in just a minute<08:33:27.600> the<08:33:28.200> way<08:33:28.260> we<08:33:28.378> do<08:33:28.500> this<08:33:28.620> is<08:33:28.798> through 08:33:28.968 --> 08:33:28.978 align:start position:0% minute the way we do this is through 08:33:28.978 --> 08:33:31.190 align:start position:0% minute the way we do this is through something<08:33:29.218> called<08:33:29.520> anding<08:33:30.058> ending<08:33:30.898> is<08:33:31.020> a 08:33:31.190 --> 08:33:31.200 align:start position:0% something called anding ending is a 08:33:31.200 --> 08:33:32.810 align:start position:0% something called anding ending is a mathematics<08:33:31.740> term<08:33:31.920> it<08:33:32.160> really<08:33:32.340> has<08:33:32.580> to<08:33:32.700> do 08:33:32.810 --> 08:33:32.820 align:start position:0% mathematics term it really has to do 08:33:32.820 --> 08:33:35.810 align:start position:0% mathematics term it really has to do with<08:33:33.058> Logic<08:33:33.540> the<08:33:34.320> way<08:33:34.378> it<08:33:34.558> works<08:33:34.860> is<08:33:35.100> and<08:33:35.700> you 08:33:35.810 --> 08:33:35.820 align:start position:0% with Logic the way it works is and you 08:33:35.820 --> 08:33:37.010 align:start position:0% with Logic the way it works is and you just<08:33:35.940> have<08:33:36.120> to<08:33:36.240> sort<08:33:36.420> of<08:33:36.478> remember<08:33:36.660> these 08:33:37.010 --> 08:33:37.020 align:start position:0% just have to sort of remember these 08:33:37.020 --> 08:33:37.910 align:start position:0% just have to sort of remember these rules 08:33:37.910 --> 08:33:37.920 align:start position:0% rules 08:33:37.920 --> 08:33:40.208 align:start position:0% rules one 08:33:40.208 --> 08:33:40.218 align:start position:0% one 08:33:40.218 --> 08:33:42.948 align:start position:0% one and<08:33:41.218> one 08:33:42.948 --> 08:33:42.958 align:start position:0% and one 08:33:42.958 --> 08:33:44.868 align:start position:0% and one is<08:33:43.440> one 08:33:44.868 --> 08:33:44.878 align:start position:0% is one 08:33:44.878 --> 08:33:46.430 align:start position:0% is one one 08:33:46.430 --> 08:33:46.440 align:start position:0% one 08:33:46.440 --> 08:33:48.410 align:start position:0% one and<08:33:47.100> zero 08:33:48.410 --> 08:33:48.420 align:start position:0% and zero 08:33:48.420 --> 08:33:50.628 align:start position:0% and zero is<08:33:48.898> zero<08:33:49.260> and<08:33:49.500> the<08:33:49.680> trick<08:33:49.920> there<08:33:50.100> is<08:33:50.280> that<08:33:50.520> that 08:33:50.628 --> 08:33:50.638 align:start position:0% is zero and the trick there is that that 08:33:50.638 --> 08:33:52.368 align:start position:0% is zero and the trick there is that that zero<08:33:51.058> is<08:33:51.180> there 08:33:52.368 --> 08:33:52.378 align:start position:0% zero is there 08:33:52.378 --> 08:33:54.948 align:start position:0% zero is there zero 08:33:54.948 --> 08:33:54.958 align:start position:0% zero 08:33:54.958 --> 08:33:57.110 align:start position:0% zero and<08:33:55.440> one 08:33:57.110 --> 08:33:57.120 align:start position:0% and one 08:33:57.120 --> 08:33:58.850 align:start position:0% and one is<08:33:57.600> zero 08:33:58.850 --> 08:33:58.860 align:start position:0% is zero 08:33:58.860 --> 08:34:00.708 align:start position:0% is zero and<08:33:59.340> zero 08:34:00.708 --> 08:34:00.718 align:start position:0% and zero 08:34:00.718 --> 08:34:04.310 align:start position:0% and zero and<08:34:01.138> zero<08:34:01.620> is<08:34:02.280> also<08:34:02.638> zero<08:34:03.478> so<08:34:03.840> basically<08:34:04.138> what 08:34:04.310 --> 08:34:04.320 align:start position:0% and zero is also zero so basically what 08:34:04.320 --> 08:34:07.610 align:start position:0% and zero is also zero so basically what anding<08:34:04.740> does<08:34:04.978> is<08:34:05.580> allows<08:34:06.058> us<08:34:06.180> to<08:34:06.540> hide 08:34:07.610 --> 08:34:07.620 align:start position:0% anding does is allows us to hide 08:34:07.620 --> 08:34:09.170 align:start position:0% anding does is allows us to hide certain 08:34:09.170 --> 08:34:09.180 align:start position:0% certain 08:34:09.180 --> 08:34:11.810 align:start position:0% certain um<08:34:09.298> address<08:34:09.958> certain<08:34:10.798> bits 08:34:11.810 --> 08:34:11.820 align:start position:0% um address certain bits 08:34:11.820 --> 08:34:14.690 align:start position:0% um address certain bits from<08:34:12.600> the<08:34:13.020> rest<08:34:13.200> of<08:34:13.500> the<08:34:13.740> network<08:34:13.978> and 08:34:14.690 --> 08:34:14.700 align:start position:0% from the rest of the network and 08:34:14.700 --> 08:34:17.388 align:start position:0% from the rest of the network and therefore<08:34:15.000> we're<08:34:15.180> allowed<08:34:15.540> to<08:34:15.660> get<08:34:16.100> the<08:34:17.100> IP 08:34:17.388 --> 08:34:17.398 align:start position:0% therefore we're allowed to get the IP 08:34:17.398 --> 08:34:19.850 align:start position:0% therefore we're allowed to get the IP address<08:34:17.840> or<08:34:18.840> rather<08:34:19.020> the<08:34:19.260> network<08:34:19.500> address 08:34:19.850 --> 08:34:19.860 align:start position:0% address or rather the network address 08:34:19.860 --> 08:34:21.708 align:start position:0% address or rather the network address from<08:34:20.458> the<08:34:20.580> node<08:34:20.760> address 08:34:21.708 --> 08:34:21.718 align:start position:0% from the node address 08:34:21.718 --> 08:34:23.510 align:start position:0% from the node address so<08:34:22.080> let's<08:34:22.260> take<08:34:22.440> a<08:34:22.558> look<08:34:22.680> at<08:34:22.860> this<08:34:22.978> for<08:34:23.218> just<08:34:23.398> a 08:34:23.510 --> 08:34:23.520 align:start position:0% so let's take a look at this for just a 08:34:23.520 --> 08:34:29.170 align:start position:0% so let's take a look at this for just a second<08:34:23.700> let's<08:34:24.298> say<08:34:24.420> we<08:34:24.600> have<08:34:24.718> an<08:34:24.840> IP<08:34:25.138> address 08:34:29.170 --> 08:34:29.180 align:start position:0% 08:34:29.180 --> 08:34:31.788 align:start position:0% 162.85.120.27<08:34:30.180> and<08:34:30.958> we<08:34:31.080> have<08:34:31.200> a<08:34:31.320> subnet<08:34:31.620> mask 08:34:31.788 --> 08:34:31.798 align:start position:0% 162.85.120.27 and we have a subnet mask 08:34:31.798 --> 08:34:36.048 align:start position:0% 162.85.120.27 and we have a subnet mask of<08:34:32.280> 255.255.255.0 08:34:36.048 --> 08:34:36.058 align:start position:0% 08:34:36.058 --> 08:34:38.628 align:start position:0% now<08:34:36.780> let's<08:34:37.260> take<08:34:37.440> a<08:34:37.558> look<08:34:37.680> at<08:34:37.860> how<08:34:38.100> this<08:34:38.280> works 08:34:38.628 --> 08:34:38.638 align:start position:0% now let's take a look at how this works 08:34:38.638 --> 08:34:42.548 align:start position:0% now let's take a look at how this works when<08:34:38.820> we<08:34:38.940> move<08:34:39.120> it<08:34:39.240> into<08:34:39.420> binary 08:34:42.548 --> 08:34:42.558 align:start position:0% 08:34:42.558 --> 08:34:45.468 align:start position:0% 162.85.120.127<08:34:43.558> equals<08:34:44.100> this<08:34:44.280> in<08:34:44.458> binary<08:34:44.878> and 08:34:45.468 --> 08:34:45.478 align:start position:0% 162.85.120.127 equals this in binary and 08:34:45.478 --> 08:34:48.590 align:start position:0% 162.85.120.127 equals this in binary and if<08:34:45.660> we<08:34:45.840> wanted<08:34:46.020> to<08:34:46.878> write<08:34:47.878> out<08:34:48.058> these<08:34:48.360> places 08:34:48.590 --> 08:34:48.600 align:start position:0% if we wanted to write out these places 08:34:48.600 --> 08:34:51.708 align:start position:0% if we wanted to write out these places again<08:34:48.958> if<08:34:49.320> you<08:34:49.558> remember<08:34:49.700> we<08:34:50.700> had<08:34:50.940> this<08:34:51.420> was<08:34:51.540> a 08:34:51.708 --> 08:34:51.718 align:start position:0% again if you remember we had this was a 08:34:51.718 --> 08:34:53.030 align:start position:0% again if you remember we had this was a base<08:34:51.840> two 08:34:53.030 --> 08:34:53.040 align:start position:0% base two 08:34:53.040 --> 08:34:57.288 align:start position:0% base two right<08:34:53.638> so<08:34:54.000> these<08:34:54.240> are<08:34:54.298> the<08:34:54.478> place<08:34:54.600> settings 08:34:57.288 --> 08:34:57.298 align:start position:0% 08:34:57.298 --> 08:34:58.670 align:start position:0% I'm<08:34:57.780> just<08:34:57.898> going<08:34:57.958> to<08:34:58.020> write<08:34:58.200> these<08:34:58.440> out<08:34:58.558> real 08:34:58.670 --> 08:34:58.680 align:start position:0% I'm just going to write these out real 08:34:58.680 --> 08:34:59.930 align:start position:0% I'm just going to write these out real quickly<08:34:58.978> and<08:34:59.100> then<08:34:59.218> I'm<08:34:59.340> going<08:34:59.458> to<08:34:59.458> erase<08:34:59.820> it 08:34:59.930 --> 08:34:59.940 align:start position:0% quickly and then I'm going to erase it 08:34:59.940 --> 08:35:03.770 align:start position:0% quickly and then I'm going to erase it all 08:35:03.770 --> 08:35:03.780 align:start position:0% 08:35:03.780 --> 08:35:04.968 align:start position:0% okay 08:35:04.968 --> 08:35:04.978 align:start position:0% okay 08:35:04.978 --> 08:35:06.830 align:start position:0% okay and<08:35:05.398> so<08:35:05.520> we<08:35:05.700> get<08:35:05.878> one 08:35:06.830 --> 08:35:06.840 align:start position:0% and so we get one 08:35:06.840 --> 08:35:09.468 align:start position:0% and so we get one two<08:35:07.760> four 08:35:09.468 --> 08:35:09.478 align:start position:0% two four 08:35:09.478 --> 08:35:10.750 align:start position:0% two four eight 08:35:10.750 --> 08:35:10.760 align:start position:0% eight 08:35:10.760 --> 08:35:15.368 align:start position:0% eight sixteen<08:35:11.958> thirty<08:35:12.958> two<08:35:13.398> sixty<08:35:14.398> four 08:35:15.368 --> 08:35:15.378 align:start position:0% sixteen thirty two sixty four 08:35:15.378 --> 08:35:17.750 align:start position:0% sixteen thirty two sixty four 128<08:35:16.378> and<08:35:16.500> it's<08:35:16.680> good<08:35:16.798> to<08:35:16.978> sort<08:35:17.160> of<08:35:17.280> commit 08:35:17.750 --> 08:35:17.760 align:start position:0% 128 and it's good to sort of commit 08:35:17.760 --> 08:35:19.788 align:start position:0% 128 and it's good to sort of commit these<08:35:17.940> to<08:35:18.120> memory<08:35:18.440> therefore<08:35:19.440> the<08:35:19.680> reason 08:35:19.788 --> 08:35:19.798 align:start position:0% these to memory therefore the reason 08:35:19.798 --> 08:35:24.708 align:start position:0% these to memory therefore the reason this<08:35:20.100> is<08:35:20.280> one<08:35:20.700> one<08:35:21.180> one<08:35:21.298> is<08:35:22.260> we<08:35:22.500> take<08:35:22.680> that<08:35:22.798> 128 08:35:24.708 --> 08:35:24.718 align:start position:0% this is one one one is we take that 128 08:35:24.718 --> 08:35:28.190 align:start position:0% this is one one one is we take that 128 we<08:35:25.320> add<08:35:25.500> it<08:35:25.680> to<08:35:25.860> 32<08:35:26.340> and<08:35:26.638> we<08:35:26.878> add<08:35:27.058> it<08:35:27.240> to<08:35:27.360> the<08:35:28.080> 2 08:35:28.190 --> 08:35:28.200 align:start position:0% we add it to 32 and we add it to the 2 08:35:28.200 --> 08:35:30.948 align:start position:0% we add it to 32 and we add it to the 2 because<08:35:28.500> those<08:35:28.740> are<08:35:28.920> the<08:35:29.040> bits<08:35:29.458> that<08:35:29.638> are<08:35:29.820> on 08:35:30.948 --> 08:35:30.958 align:start position:0% because those are the bits that are on 08:35:30.958 --> 08:35:36.888 align:start position:0% because those are the bits that are on and<08:35:31.378> when<08:35:31.500> we<08:35:31.740> add<08:35:32.058> 128<08:35:33.138> plus<08:35:34.138> 32 08:35:36.888 --> 08:35:36.898 align:start position:0% 08:35:36.898 --> 08:35:39.770 align:start position:0% we<08:35:37.440> get<08:35:37.620> 160 08:35:39.770 --> 08:35:39.780 align:start position:0% we get 160 08:35:39.780 --> 08:35:44.330 align:start position:0% we get 160 plus<08:35:40.440> 2<08:35:41.218> gives<08:35:41.760> us<08:35:42.000> 1<08:35:42.298> 62.<08:35:43.260> so<08:35:43.680> it<08:35:43.920> works<08:35:44.218> out 08:35:44.330 --> 08:35:44.340 align:start position:0% plus 2 gives us 1 62. so it works out 08:35:44.340 --> 08:35:45.948 align:start position:0% plus 2 gives us 1 62. so it works out and<08:35:44.520> you<08:35:44.638> can<08:35:44.760> see<08:35:44.878> my<08:35:45.058> math<08:35:45.180> is<08:35:45.420> correct<08:35:45.780> here 08:35:45.948 --> 08:35:45.958 align:start position:0% and you can see my math is correct here 08:35:45.958 --> 08:35:48.170 align:start position:0% and you can see my math is correct here I'm<08:35:46.378> going<08:35:46.558> to<08:35:46.620> erase<08:35:46.860> all<08:35:47.040> this<08:35:47.218> now<08:35:47.398> try<08:35:48.000> to 08:35:48.170 --> 08:35:48.180 align:start position:0% I'm going to erase all this now try to 08:35:48.180 --> 08:35:50.208 align:start position:0% I'm going to erase all this now try to remember<08:35:48.298> this<08:35:48.718> and<08:35:48.958> thing<08:35:49.320> in<08:35:49.558> here<08:35:49.920> for<08:35:50.100> a 08:35:50.208 --> 08:35:50.218 align:start position:0% remember this and thing in here for a 08:35:50.218 --> 08:35:51.590 align:start position:0% remember this and thing in here for a minute 08:35:51.590 --> 08:35:51.600 align:start position:0% minute 08:35:51.600 --> 08:35:54.670 align:start position:0% minute now<08:35:52.200> if<08:35:52.620> we<08:35:52.740> convert 08:35:54.670 --> 08:35:54.680 align:start position:0% now if we convert 08:35:54.680 --> 08:35:57.170 align:start position:0% now if we convert 255.255.255.0<08:35:55.680> into<08:35:56.040> binary<08:35:56.580> we've<08:35:57.058> already 08:35:57.170 --> 08:35:57.180 align:start position:0% 255.255.255.0 into binary we've already 08:35:57.180 --> 08:35:58.968 align:start position:0% 255.255.255.0 into binary we've already talked<08:35:57.540> about<08:35:57.600> this<08:35:57.840> we're<08:35:58.080> going<08:35:58.200> to<08:35:58.260> get 08:35:58.968 --> 08:35:58.978 align:start position:0% talked about this we're going to get 08:35:58.978 --> 08:36:01.368 align:start position:0% talked about this we're going to get all<08:35:59.580> these<08:35:59.820> ones<08:36:00.180> and<08:36:00.600> then<08:36:00.718> because<08:36:00.958> this<08:36:01.260> is 08:36:01.368 --> 08:36:01.378 align:start position:0% all these ones and then because this is 08:36:01.378 --> 08:36:04.430 align:start position:0% all these ones and then because this is zero<08:36:01.740> we're<08:36:01.920> gonna<08:36:02.040> get<08:36:02.218> zero<08:36:03.120> now<08:36:03.780> if<08:36:04.260> we 08:36:04.430 --> 08:36:04.440 align:start position:0% zero we're gonna get zero now if we 08:36:04.440 --> 08:36:07.788 align:start position:0% zero we're gonna get zero now if we apply<08:36:04.860> the<08:36:05.160> anding<08:36:05.520> principle 08:36:07.788 --> 08:36:07.798 align:start position:0% apply the anding principle 08:36:07.798 --> 08:36:09.530 align:start position:0% apply the anding principle this<08:36:08.160> is<08:36:08.218> what<08:36:08.398> we're<08:36:08.458> going<08:36:08.638> to<08:36:08.700> get 08:36:09.530 --> 08:36:09.540 align:start position:0% this is what we're going to get 08:36:09.540 --> 08:36:12.888 align:start position:0% this is what we're going to get anything<08:36:10.080> with<08:36:10.500> one<08:36:10.680> and<08:36:10.920> one<08:36:11.100> turns<08:36:11.760> into<08:36:11.878> one 08:36:12.888 --> 08:36:12.898 align:start position:0% anything with one and one turns into one 08:36:12.898 --> 08:36:15.708 align:start position:0% anything with one and one turns into one anytime<08:36:13.558> we<08:36:13.920> see<08:36:14.100> a<08:36:14.520> one<08:36:14.638> and<08:36:14.820> a<08:36:15.000> zero<08:36:15.360> we're 08:36:15.708 --> 08:36:15.718 align:start position:0% anytime we see a one and a zero we're 08:36:15.718 --> 08:36:17.750 align:start position:0% anytime we see a one and a zero we're going<08:36:15.898> to<08:36:15.958> get<08:36:16.080> a<08:36:16.200> zero<08:36:16.558> and<08:36:16.978> if<08:36:17.160> we<08:36:17.280> apply<08:36:17.520> this 08:36:17.750 --> 08:36:17.760 align:start position:0% going to get a zero and if we apply this 08:36:17.760 --> 08:36:19.788 align:start position:0% going to get a zero and if we apply this out 08:36:19.788 --> 08:36:19.798 align:start position:0% out 08:36:19.798 --> 08:36:21.888 align:start position:0% out here's<08:36:20.218> what<08:36:20.340> we<08:36:20.520> get<08:36:20.638> now<08:36:21.360> because<08:36:21.600> we<08:36:21.840> have 08:36:21.888 --> 08:36:21.898 align:start position:0% here's what we get now because we have 08:36:21.898 --> 08:36:23.990 align:start position:0% here's what we get now because we have all<08:36:22.080> these<08:36:22.260> zeros<08:36:22.680> here<08:36:22.978> it's<08:36:23.638> basically 08:36:23.990 --> 08:36:24.000 align:start position:0% all these zeros here it's basically 08:36:24.000 --> 08:36:26.030 align:start position:0% all these zeros here it's basically going<08:36:24.180> to<08:36:24.360> block<08:36:24.600> all<08:36:25.260> these<08:36:25.440> ones<08:36:25.740> from 08:36:26.030 --> 08:36:26.040 align:start position:0% going to block all these ones from 08:36:26.040 --> 08:36:28.190 align:start position:0% going to block all these ones from coming<08:36:26.340> down<08:36:26.638> and<08:36:26.820> coming<08:36:27.000> through 08:36:28.190 --> 08:36:28.200 align:start position:0% coming down and coming through 08:36:28.200 --> 08:36:32.690 align:start position:0% coming down and coming through right<08:36:28.740> they<08:36:28.978> all<08:36:29.100> turn<08:36:29.280> into<08:36:29.458> zero 08:36:32.690 --> 08:36:32.700 align:start position:0% 08:36:32.700 --> 08:36:35.628 align:start position:0% so<08:36:33.298> if<08:36:33.540> we<08:36:33.718> convert<08:36:34.080> this<08:36:34.320> back<08:36:34.680> into<08:36:35.398> a 08:36:35.628 --> 08:36:35.638 align:start position:0% so if we convert this back into a 08:36:35.638 --> 08:36:41.150 align:start position:0% so if we convert this back into a decimal<08:36:36.540> we<08:36:37.138> now<08:36:37.260> get<08:36:37.558> 162.85.120.0 08:36:41.150 --> 08:36:41.160 align:start position:0% 08:36:41.160 --> 08:36:43.670 align:start position:0% basically<08:36:41.878> this<08:36:42.600> is<08:36:42.780> pretty<08:36:42.958> simple<08:36:43.200> to<08:36:43.500> see 08:36:43.670 --> 08:36:43.680 align:start position:0% basically this is pretty simple to see 08:36:43.680 --> 08:36:46.968 align:start position:0% basically this is pretty simple to see we<08:36:44.340> can<08:36:44.520> see<08:36:44.760> that<08:36:45.000> the<08:36:45.298> 162<08:36:45.840> drops<08:36:46.200> down<08:36:46.320> the<08:36:46.860> 8 08:36:46.968 --> 08:36:46.978 align:start position:0% we can see that the 162 drops down the 8 08:36:46.978 --> 08:36:49.910 align:start position:0% we can see that the 162 drops down the 8 5<08:36:47.218> drops<08:36:47.760> down<08:36:47.878> the<08:36:48.600> 120<08:36:49.080> drops<08:36:49.440> down<08:36:49.558> because 08:36:49.910 --> 08:36:49.920 align:start position:0% 5 drops down the 120 drops down because 08:36:49.920 --> 08:36:52.730 align:start position:0% 5 drops down the 120 drops down because of<08:36:50.218> this<08:36:50.398> ending<08:36:50.820> that<08:36:51.000> we<08:36:51.120> just<08:36:51.298> talked<08:36:51.600> about 08:36:52.730 --> 08:36:52.740 align:start position:0% of this ending that we just talked about 08:36:52.740 --> 08:36:57.230 align:start position:0% of this ending that we just talked about and<08:36:53.040> the<08:36:53.160> 27<08:36:53.580> gets<08:36:54.000> blocked<08:36:54.898> might<08:36:55.260> be<08:36:55.440> zeros 08:36:57.230 --> 08:36:57.240 align:start position:0% and the 27 gets blocked might be zeros 08:36:57.240 --> 08:36:59.510 align:start position:0% and the 27 gets blocked might be zeros and<08:36:57.780> so<08:36:57.898> we<08:36:58.260> can<08:36:58.320> determine 08:36:59.510 --> 08:36:59.520 align:start position:0% and so we can determine 08:36:59.520 --> 08:37:01.270 align:start position:0% and so we can determine that<08:37:00.058> the 08:37:01.270 --> 08:37:01.280 align:start position:0% that the 08:37:01.280 --> 08:37:05.030 align:start position:0% that the 162.85.120<08:37:02.280> is<08:37:03.180> what<08:37:03.420> we<08:37:03.600> call 08:37:05.030 --> 08:37:05.040 align:start position:0% 162.85.120 is what we call 08:37:05.040 --> 08:37:08.150 align:start position:0% 162.85.120 is what we call the<08:37:05.760> network 08:37:08.150 --> 08:37:08.160 align:start position:0% 08:37:08.160 --> 08:37:10.128 align:start position:0% ID 08:37:10.128 --> 08:37:10.138 align:start position:0% ID 08:37:10.138 --> 08:37:12.230 align:start position:0% ID Now<08:37:10.620> by<08:37:10.920> looking<08:37:11.040> at<08:37:11.218> it<08:37:11.340> this<08:37:11.520> way<08:37:11.700> we<08:37:11.940> can<08:37:12.058> see 08:37:12.230 --> 08:37:12.240 align:start position:0% Now by looking at it this way we can see 08:37:12.240 --> 08:37:14.270 align:start position:0% Now by looking at it this way we can see then<08:37:12.478> that<08:37:12.898> the<08:37:13.080> network<08:37:13.260> portion<08:37:13.798> of<08:37:13.978> the 08:37:14.270 --> 08:37:14.280 align:start position:0% then that the network portion of the 08:37:14.280 --> 08:37:17.150 align:start position:0% then that the network portion of the address<08:37:14.898> is<08:37:15.898> going<08:37:16.020> to<08:37:16.200> be<08:37:16.260> the<08:37:16.620> first<08:37:16.798> three 08:37:17.150 --> 08:37:17.160 align:start position:0% address is going to be the first three 08:37:17.160 --> 08:37:19.910 align:start position:0% address is going to be the first three octets<08:37:17.638> as<08:37:18.000> we<08:37:18.120> just<08:37:18.298> pointed<08:37:18.600> out<08:37:18.740> and<08:37:19.740> the 08:37:19.910 --> 08:37:19.920 align:start position:0% octets as we just pointed out and the 08:37:19.920 --> 08:37:22.310 align:start position:0% octets as we just pointed out and the node<08:37:20.160> portion<08:37:20.700> is<08:37:21.478> going<08:37:21.600> to<08:37:21.780> be<08:37:21.898> the<08:37:22.138> last 08:37:22.310 --> 08:37:22.320 align:start position:0% node portion is going to be the last 08:37:22.320 --> 08:37:23.810 align:start position:0% node portion is going to be the last octet 08:37:23.810 --> 08:37:23.820 align:start position:0% octet 08:37:23.820 --> 08:37:26.208 align:start position:0% octet so<08:37:24.180> this<08:37:24.360> is<08:37:24.478> the<08:37:24.718> first<08:37:24.898> step<08:37:25.260> in<08:37:25.500> subnetting 08:37:26.208 --> 08:37:26.218 align:start position:0% so this is the first step in subnetting 08:37:26.218 --> 08:37:27.590 align:start position:0% so this is the first step in subnetting and<08:37:26.638> it<08:37:26.760> tells<08:37:27.000> us<08:37:27.058> a<08:37:27.120> lot<08:37:27.240> of<08:37:27.298> things<08:37:27.420> about 08:37:27.590 --> 08:37:27.600 align:start position:0% and it tells us a lot of things about 08:37:27.600 --> 08:37:30.110 align:start position:0% and it tells us a lot of things about the<08:37:27.840> networks<08:37:28.740> just<08:37:29.160> by<08:37:29.340> knowing<08:37:29.638> the<08:37:29.820> IP 08:37:30.110 --> 08:37:30.120 align:start position:0% the networks just by knowing the IP 08:37:30.120 --> 08:37:32.388 align:start position:0% the networks just by knowing the IP address<08:37:30.298> and<08:37:30.840> the<08:37:31.020> subnet<08:37:31.378> mask<08:37:31.558> a<08:37:32.040> technician 08:37:32.388 --> 08:37:32.398 align:start position:0% address and the subnet mask a technician 08:37:32.398 --> 08:37:35.090 align:start position:0% address and the subnet mask a technician can<08:37:32.580> now<08:37:32.760> discern<08:37:33.360> a<08:37:33.780> lot<08:37:33.840> of<08:37:33.958> things<08:37:34.138> such<08:37:34.860> as 08:37:35.090 --> 08:37:35.100 align:start position:0% can now discern a lot of things such as 08:37:35.100 --> 08:37:37.610 align:start position:0% can now discern a lot of things such as what<08:37:35.940> portion<08:37:36.240> is<08:37:36.420> the<08:37:36.540> network<08:37:36.718> ID<08:37:36.958> what 08:37:37.610 --> 08:37:37.620 align:start position:0% what portion is the network ID what 08:37:37.620 --> 08:37:40.070 align:start position:0% what portion is the network ID what portion<08:37:37.978> is<08:37:38.100> the<08:37:38.340> node<08:37:38.638> ID 08:37:40.070 --> 08:37:40.080 align:start position:0% portion is the node ID 08:37:40.080 --> 08:37:43.070 align:start position:0% portion is the node ID and<08:37:40.920> therefore<08:37:41.340> what<08:37:41.580> is<08:37:41.760> my<08:37:42.000> first<08:37:42.180> usable<08:37:42.600> IP 08:37:43.070 --> 08:37:43.080 align:start position:0% and therefore what is my first usable IP 08:37:43.080 --> 08:37:45.410 align:start position:0% and therefore what is my first usable IP address<08:37:43.260> and<08:37:43.920> what's<08:37:44.040> my<08:37:44.340> last<08:37:44.520> usable<08:37:45.000> IP 08:37:45.410 --> 08:37:45.420 align:start position:0% address and what's my last usable IP 08:37:45.420 --> 08:37:48.170 align:start position:0% address and what's my last usable IP address<08:37:45.660> that<08:37:46.200> I<08:37:46.378> could<08:37:46.500> start<08:37:46.740> to<08:37:47.040> give<08:37:47.218> to 08:37:48.170 --> 08:37:48.180 align:start position:0% address that I could start to give to 08:37:48.180 --> 08:37:49.250 align:start position:0% address that I could start to give to devices 08:37:49.250 --> 08:37:49.260 align:start position:0% devices 08:37:49.260 --> 08:37:51.650 align:start position:0% devices I<08:37:49.680> can<08:37:49.860> also<08:37:50.160> determine<08:37:50.760> stuff<08:37:51.000> like<08:37:51.240> what<08:37:51.540> we 08:37:51.650 --> 08:37:51.660 align:start position:0% I can also determine stuff like what we 08:37:51.660 --> 08:37:53.510 align:start position:0% I can also determine stuff like what we call<08:37:51.840> the<08:37:52.378> default<08:37:52.680> gateway<08:37:53.100> which<08:37:53.340> we'll 08:37:53.510 --> 08:37:53.520 align:start position:0% call the default gateway which we'll 08:37:53.520 --> 08:37:56.990 align:start position:0% call the default gateway which we'll look<08:37:53.638> at<08:37:53.760> in<08:37:53.940> a<08:37:54.058> second 08:37:56.990 --> 08:37:57.000 align:start position:0% 08:37:57.000 --> 08:37:58.610 align:start position:0% and 08:37:58.610 --> 08:37:58.620 align:start position:0% and 08:37:58.620 --> 08:38:00.708 align:start position:0% and the<08:37:59.100> broadcast<08:37:59.280> address<08:37:59.878> which<08:38:00.240> will<08:38:00.420> also 08:38:00.708 --> 08:38:00.718 align:start position:0% the broadcast address which will also 08:38:00.718 --> 08:38:03.170 align:start position:0% the broadcast address which will also look<08:38:00.898> look<08:38:01.260> at<08:38:01.500> not<08:38:02.040> in<08:38:02.218> a<08:38:02.340> second<08:38:02.458> then<08:38:02.760> in<08:38:03.000> the 08:38:03.170 --> 08:38:03.180 align:start position:0% look look at not in a second then in the 08:38:03.180 --> 08:38:06.590 align:start position:0% look look at not in a second then in the next<08:38:03.360> module 08:38:06.590 --> 08:38:06.600 align:start position:0% 08:38:06.600 --> 08:38:10.128 align:start position:0% now<08:38:07.020> there<08:38:07.320> are<08:38:07.500> three<08:38:08.100> default<08:38:08.820> subnet<08:38:09.718> masks 08:38:10.128 --> 08:38:10.138 align:start position:0% now there are three default subnet masks 08:38:10.138 --> 08:38:12.530 align:start position:0% now there are three default subnet masks as<08:38:10.320> you<08:38:10.500> can<08:38:10.620> imagine 08:38:12.530 --> 08:38:12.540 align:start position:0% as you can imagine 08:38:12.540 --> 08:38:14.270 align:start position:0% as you can imagine and<08:38:12.958> these<08:38:13.138> have<08:38:13.320> to<08:38:13.378> do<08:38:13.440> with<08:38:13.558> what<08:38:13.740> we<08:38:13.860> call<08:38:13.978> a 08:38:14.270 --> 08:38:14.280 align:start position:0% and these have to do with what we call a 08:38:14.280 --> 08:38:17.150 align:start position:0% and these have to do with what we call a class<08:38:14.520> uh<08:38:15.360> a<08:38:15.420> class<08:38:15.958> full<08:38:16.260> IP<08:38:16.740> addressing 08:38:17.150 --> 08:38:17.160 align:start position:0% class uh a class full IP addressing 08:38:17.160 --> 08:38:18.350 align:start position:0% class uh a class full IP addressing system<08:38:17.280> and<08:38:17.520> we'll<08:38:17.638> talk<08:38:17.760> about<08:38:17.878> that<08:38:18.120> next 08:38:18.350 --> 08:38:18.360 align:start position:0% system and we'll talk about that next 08:38:18.360 --> 08:38:20.750 align:start position:0% system and we'll talk about that next the<08:38:18.718> next<08:38:18.958> module<08:38:19.378> but<08:38:19.860> the<08:38:20.040> default<08:38:20.280> subnet 08:38:20.750 --> 08:38:20.760 align:start position:0% the next module but the default subnet 08:38:20.760 --> 08:38:23.448 align:start position:0% the next module but the default subnet masks<08:38:21.058> are<08:38:21.180> 255.0.0.0 08:38:23.448 --> 08:38:23.458 align:start position:0% masks are 255.0.0.0 08:38:23.458 --> 08:38:24.830 align:start position:0% masks are 255.0.0.0 just<08:38:23.638> going<08:38:23.820> to<08:38:23.878> go<08:38:23.940> with<08:38:24.058> the<08:38:24.180> class<08:38:24.298> A<08:38:24.600> and 08:38:24.830 --> 08:38:24.840 align:start position:0% just going to go with the class A and 08:38:24.840 --> 08:38:27.250 align:start position:0% just going to go with the class A and we'll<08:38:25.020> talk<08:38:25.138> about<08:38:25.320> that 08:38:27.250 --> 08:38:27.260 align:start position:0% we'll talk about that 08:38:27.260 --> 08:38:30.888 align:start position:0% we'll talk about that 255.255.0.0<08:38:28.260> and<08:38:28.440> 255.255.255.0 08:38:30.888 --> 08:38:30.898 align:start position:0% 255.255.0.0 and 255.255.255.0 08:38:30.898 --> 08:38:32.628 align:start position:0% 255.255.0.0 and 255.255.255.0 what<08:38:31.260> you<08:38:31.440> can<08:38:31.558> see<08:38:31.680> is<08:38:31.860> if<08:38:32.218> you<08:38:32.340> have<08:38:32.458> a 08:38:32.628 --> 08:38:32.638 align:start position:0% what you can see is if you have a 08:38:32.638 --> 08:38:35.330 align:start position:0% what you can see is if you have a default<08:38:33.138> subnet<08:38:34.138> mask<08:38:34.320> then<08:38:34.978> you<08:38:35.160> know 08:38:35.330 --> 08:38:35.340 align:start position:0% default subnet mask then you know 08:38:35.340 --> 08:38:37.610 align:start position:0% default subnet mask then you know immediately<08:38:35.940> just<08:38:36.240> by<08:38:36.420> looking 08:38:37.610 --> 08:38:37.620 align:start position:0% immediately just by looking 08:38:37.620 --> 08:38:39.948 align:start position:0% immediately just by looking what<08:38:38.280> the<08:38:38.458> network<08:38:38.638> address<08:38:39.000> is<08:38:39.360> and<08:38:39.660> what<08:38:39.840> the 08:38:39.948 --> 08:38:39.958 align:start position:0% what the network address is and what the 08:38:39.958 --> 08:38:41.208 align:start position:0% what the network address is and what the node<08:38:40.080> address<08:38:40.378> is 08:38:41.208 --> 08:38:41.218 align:start position:0% node address is 08:38:41.218 --> 08:38:42.888 align:start position:0% node address is as<08:38:41.638> you<08:38:41.760> can<08:38:41.878> imagine 08:38:42.888 --> 08:38:42.898 align:start position:0% as you can imagine 08:38:42.898 --> 08:38:46.190 align:start position:0% as you can imagine if<08:38:43.320> I<08:38:43.558> have<08:38:43.740> this<08:38:44.100> as<08:38:44.340> my<08:38:44.580> network<08:38:44.760> address 08:38:46.190 --> 08:38:46.200 align:start position:0% if I have this as my network address 08:38:46.200 --> 08:38:50.150 align:start position:0% if I have this as my network address I<08:38:46.680> can<08:38:46.740> have<08:38:46.860> a<08:38:47.040> lot<08:38:47.160> of<08:38:47.280> Networks<08:38:48.240> and<08:38:48.898> only<08:38:49.160> so 08:38:50.150 --> 08:38:50.160 align:start position:0% I can have a lot of Networks and only so 08:38:50.160 --> 08:38:53.868 align:start position:0% I can have a lot of Networks and only so many<08:38:50.340> nodes<08:38:51.378> this<08:38:52.378> one<08:38:52.558> I<08:38:53.040> have 08:38:53.868 --> 08:38:53.878 align:start position:0% many nodes this one I have 08:38:53.878 --> 08:38:56.990 align:start position:0% many nodes this one I have more<08:38:54.540> nodes<08:38:54.898> a<08:38:55.798> little<08:38:55.920> bit<08:38:56.100> less<08:38:56.340> networks 08:38:56.990 --> 08:38:57.000 align:start position:0% more nodes a little bit less networks 08:38:57.000 --> 08:38:58.910 align:start position:0% more nodes a little bit less networks and<08:38:57.240> this<08:38:57.478> one<08:38:57.600> I<08:38:57.718> have<08:38:57.840> a<08:38:58.020> lot<08:38:58.200> of<08:38:58.320> nodes<08:38:58.620> but 08:38:58.910 --> 08:38:58.920 align:start position:0% and this one I have a lot of nodes but 08:38:58.920 --> 08:39:01.190 align:start position:0% and this one I have a lot of nodes but fewer<08:38:59.340> networks<08:38:59.700> to<08:38:59.820> divide<08:39:00.058> them<08:39:00.180> up<08:39:00.360> on 08:39:01.190 --> 08:39:01.200 align:start position:0% fewer networks to divide them up on 08:39:01.200 --> 08:39:03.288 align:start position:0% fewer networks to divide them up on now<08:39:01.558> would<08:39:01.740> be<08:39:01.860> great<08:39:02.040> if<08:39:02.280> all<08:39:02.520> subnet<08:39:02.940> masks 08:39:03.288 --> 08:39:03.298 align:start position:0% now would be great if all subnet masks 08:39:03.298 --> 08:39:04.788 align:start position:0% now would be great if all subnet masks were<08:39:03.478> as<08:39:03.660> simple<08:39:03.780> as<08:39:04.020> this<08:39:04.138> we<08:39:04.378> wouldn't<08:39:04.558> even 08:39:04.788 --> 08:39:04.798 align:start position:0% were as simple as this we wouldn't even 08:39:04.798 --> 08:39:07.250 align:start position:0% were as simple as this we wouldn't even really<08:39:05.040> ever<08:39:05.280> have<08:39:05.520> to<08:39:05.760> break<08:39:05.940> it<08:39:06.180> down<08:39:06.420> into 08:39:07.250 --> 08:39:07.260 align:start position:0% really ever have to break it down into 08:39:07.260 --> 08:39:10.010 align:start position:0% really ever have to break it down into this<08:39:07.680> binary<08:39:08.458> sort<08:39:08.820> of<08:39:08.940> coding<08:39:09.298> because<08:39:09.780> you 08:39:10.010 --> 08:39:10.020 align:start position:0% this binary sort of coding because you 08:39:10.020 --> 08:39:11.150 align:start position:0% this binary sort of coding because you could<08:39:10.138> just<08:39:10.260> look<08:39:10.440> at<08:39:10.558> it<08:39:10.680> and<08:39:10.798> say<08:39:10.920> oh<08:39:11.040> it's 08:39:11.150 --> 08:39:11.160 align:start position:0% could just look at it and say oh it's 08:39:11.160 --> 08:39:12.830 align:start position:0% could just look at it and say oh it's 255<08:39:11.700> I<08:39:11.878> know<08:39:12.000> they're<08:39:12.120> all<08:39:12.240> going<08:39:12.360> to<08:39:12.478> be<08:39:12.540> ones 08:39:12.830 --> 08:39:12.840 align:start position:0% 255 I know they're all going to be ones 08:39:12.840 --> 08:39:14.690 align:start position:0% 255 I know they're all going to be ones I<08:39:13.138> know<08:39:13.260> that's<08:39:13.440> going<08:39:13.620> to<08:39:13.740> end<08:39:13.860> out<08:39:14.160> and 08:39:14.690 --> 08:39:14.700 align:start position:0% I know that's going to end out and 08:39:14.700 --> 08:39:15.948 align:start position:0% I know that's going to end out and therefore<08:39:14.940> I<08:39:15.120> know<08:39:15.240> it's<08:39:15.420> going<08:39:15.600> to<08:39:15.718> end<08:39:15.780> up 08:39:15.948 --> 08:39:15.958 align:start position:0% therefore I know it's going to end up 08:39:15.958 --> 08:39:17.030 align:start position:0% therefore I know it's going to end up right<08:39:16.200> here 08:39:17.030 --> 08:39:17.040 align:start position:0% right here 08:39:17.040 --> 08:39:18.830 align:start position:0% right here but<08:39:17.638> unfortunately<08:39:18.000> this<08:39:18.298> is<08:39:18.420> not<08:39:18.540> always<08:39:18.660> the 08:39:18.830 --> 08:39:18.840 align:start position:0% but unfortunately this is not always the 08:39:18.840 --> 08:39:19.968 align:start position:0% but unfortunately this is not always the case<08:39:18.958> sometimes<08:39:19.320> we<08:39:19.378> have<08:39:19.500> what<08:39:19.680> are<08:39:19.798> called 08:39:19.968 --> 08:39:19.978 align:start position:0% case sometimes we have what are called 08:39:19.978 --> 08:39:23.388 align:start position:0% case sometimes we have what are called custom<08:39:20.760> subnet<08:39:21.600> masks<08:39:22.378> Now<08:39:22.740> by<08:39:22.860> using<08:39:23.160> a 08:39:23.388 --> 08:39:23.398 align:start position:0% custom subnet masks Now by using a 08:39:23.398 --> 08:39:24.830 align:start position:0% custom subnet masks Now by using a custom<08:39:23.520> subnet<08:39:24.120> mask<08:39:24.240> we<08:39:24.600> can<08:39:24.718> actually 08:39:24.830 --> 08:39:24.840 align:start position:0% custom subnet mask we can actually 08:39:24.840 --> 08:39:27.650 align:start position:0% custom subnet mask we can actually further<08:39:25.500> divide<08:39:25.920> or<08:39:26.218> subdivide<08:39:26.820> our<08:39:27.298> IP 08:39:27.650 --> 08:39:27.660 align:start position:0% further divide or subdivide our IP 08:39:27.660 --> 08:39:29.628 align:start position:0% further divide or subdivide our IP address<08:39:27.898> and<08:39:28.558> in<08:39:28.680> these<08:39:28.860> cases<08:39:29.100> it<08:39:29.340> can<08:39:29.458> be<08:39:29.520> a 08:39:29.628 --> 08:39:29.638 align:start position:0% address and in these cases it can be a 08:39:29.638 --> 08:39:32.208 align:start position:0% address and in these cases it can be a little<08:39:29.700> more<08:39:29.878> difficult<08:39:30.320> uh<08:39:31.320> and<08:39:31.860> so 08:39:32.208 --> 08:39:32.218 align:start position:0% little more difficult uh and so 08:39:32.218 --> 08:39:33.830 align:start position:0% little more difficult uh and so converting<08:39:32.760> to<08:39:33.000> Binary<08:39:33.420> is<08:39:33.660> actually 08:39:33.830 --> 08:39:33.840 align:start position:0% converting to Binary is actually 08:39:33.840 --> 08:39:36.888 align:start position:0% converting to Binary is actually necessary<08:39:34.440> to<08:39:34.680> break<08:39:34.860> it<08:39:35.040> down<08:39:35.280> custom<08:39:36.240> subnet 08:39:36.888 --> 08:39:36.898 align:start position:0% necessary to break it down custom subnet 08:39:36.898 --> 08:39:39.530 align:start position:0% necessary to break it down custom subnet masks<08:39:37.500> are<08:39:38.218> created<08:39:38.820> by<08:39:39.120> what<08:39:39.240> we<08:39:39.360> call 08:39:39.530 --> 08:39:39.540 align:start position:0% masks are created by what we call 08:39:39.540 --> 08:39:41.930 align:start position:0% masks are created by what we call borrowing<08:39:40.440> bits 08:39:41.930 --> 08:39:41.940 align:start position:0% borrowing bits 08:39:41.940 --> 08:39:45.410 align:start position:0% borrowing bits from<08:39:42.540> the<08:39:42.718> host<08:39:42.898> portion<08:39:43.500> to<08:39:44.160> use<08:39:44.398> to<08:39:44.940> identify 08:39:45.410 --> 08:39:45.420 align:start position:0% from the host portion to use to identify 08:39:45.420 --> 08:39:47.330 align:start position:0% from the host portion to use to identify the<08:39:45.718> subnet<08:39:46.020> motion<08:39:46.378> so<08:39:46.740> you<08:39:46.860> can<08:39:46.920> see<08:39:47.040> we've 08:39:47.330 --> 08:39:47.340 align:start position:0% the subnet motion so you can see we've 08:39:47.340 --> 08:39:49.968 align:start position:0% the subnet motion so you can see we've just<08:39:47.520> borrowed<08:39:48.120> a<08:39:48.298> bit<08:39:48.420> this<08:39:48.840> one<08:39:49.080> right<08:39:49.860> over 08:39:49.968 --> 08:39:49.978 align:start position:0% just borrowed a bit this one right over 08:39:49.978 --> 08:39:50.750 align:start position:0% just borrowed a bit this one right over here 08:39:50.750 --> 08:39:50.760 align:start position:0% here 08:39:50.760 --> 08:39:52.548 align:start position:0% here now<08:39:51.180> keeping<08:39:51.540> in<08:39:51.600> mind<08:39:51.718> that<08:39:51.898> the<08:39:52.020> subnet<08:39:52.378> mask 08:39:52.548 --> 08:39:52.558 align:start position:0% now keeping in mind that the subnet mask 08:39:52.558 --> 08:39:54.708 align:start position:0% now keeping in mind that the subnet mask rules<08:39:53.100> allow<08:39:53.580> us<08:39:53.700> to<08:39:53.878> borrow<08:39:54.000> bits<08:39:54.478> from<08:39:54.540> the 08:39:54.708 --> 08:39:54.718 align:start position:0% rules allow us to borrow bits from the 08:39:54.718 --> 08:39:57.468 align:start position:0% rules allow us to borrow bits from the node<08:39:54.840> portion<08:39:55.320> and<08:39:55.978> give<08:39:56.218> them<08:39:56.458> to<08:39:57.240> the 08:39:57.468 --> 08:39:57.478 align:start position:0% node portion and give them to the 08:39:57.478 --> 08:39:59.990 align:start position:0% node portion and give them to the network<08:39:57.600> portion<08:39:58.200> the<08:39:58.920> bits<08:39:59.280> from<08:39:59.520> the<08:39:59.820> left 08:39:59.990 --> 08:40:00.000 align:start position:0% network portion the bits from the left 08:40:00.000 --> 08:40:02.150 align:start position:0% network portion the bits from the left to<08:40:00.420> the<08:40:00.600> right<08:40:00.718> of<08:40:01.080> the<08:40:01.200> portion 08:40:02.150 --> 08:40:02.160 align:start position:0% to the right of the portion 08:40:02.160 --> 08:40:04.250 align:start position:0% to the right of the portion like<08:40:02.520> this 08:40:04.250 --> 08:40:04.260 align:start position:0% like this 08:40:04.260 --> 08:40:06.410 align:start position:0% like this are<08:40:04.798> switched<08:40:05.218> on 08:40:06.410 --> 08:40:06.420 align:start position:0% are switched on 08:40:06.420 --> 08:40:08.208 align:start position:0% are switched on now<08:40:06.718> turning<08:40:07.080> this<08:40:07.200> bit<08:40:07.378> on<08:40:07.558> means<08:40:07.920> we<08:40:08.100> now 08:40:08.208 --> 08:40:08.218 align:start position:0% now turning this bit on means we now 08:40:08.218 --> 08:40:09.948 align:start position:0% now turning this bit on means we now have<08:40:08.398> different<08:40:08.638> values<08:40:09.240> for<08:40:09.478> the<08:40:09.600> subnet 08:40:09.948 --> 08:40:09.958 align:start position:0% have different values for the subnet 08:40:09.958 --> 08:40:13.270 align:start position:0% have different values for the subnet mask<08:40:10.200> instead<08:40:10.920> of<08:40:11.040> just<08:40:11.160> 255 08:40:13.270 --> 08:40:13.280 align:start position:0% mask instead of just 255 08:40:13.280 --> 08:40:14.990 align:start position:0% mask instead of just 255 .255. 08:40:14.990 --> 08:40:15.000 align:start position:0% .255. 08:40:15.000 --> 08:40:17.270 align:start position:0% .255. 255. 08:40:17.270 --> 08:40:17.280 align:start position:0% 255. 08:40:17.280 --> 08:40:19.670 align:start position:0% 255. dot<08:40:17.878> zero<08:40:18.240> we<08:40:18.360> know<08:40:18.478> this<08:40:18.718> is<08:40:18.840> no<08:40:19.020> longer<08:40:19.260> zero 08:40:19.670 --> 08:40:19.680 align:start position:0% dot zero we know this is no longer zero 08:40:19.680 --> 08:40:21.830 align:start position:0% dot zero we know this is no longer zero right<08:40:20.280> so<08:40:20.760> this<08:40:20.940> is<08:40:21.120> actually<08:40:21.298> now<08:40:21.540> going<08:40:21.718> to 08:40:21.830 --> 08:40:21.840 align:start position:0% right so this is actually now going to 08:40:21.840 --> 08:40:22.430 align:start position:0% right so this is actually now going to be 08:40:22.430 --> 08:40:22.440 align:start position:0% be 08:40:22.440 --> 08:40:25.010 align:start position:0% be 128. 08:40:25.010 --> 08:40:25.020 align:start position:0% 128. 08:40:25.020 --> 08:40:28.070 align:start position:0% 128. and<08:40:25.558> we<08:40:25.680> can<08:40:25.860> have<08:40:26.100> a<08:40:26.638> a<08:40:27.180> number<08:40:27.420> of<08:40:27.600> these<08:40:27.840> and 08:40:28.070 --> 08:40:28.080 align:start position:0% and we can have a a number of these and 08:40:28.080 --> 08:40:30.468 align:start position:0% and we can have a a number of these and if<08:40:28.200> you<08:40:28.320> keep<08:40:28.500> adding<08:40:28.920> over<08:40:29.040> to<08:40:29.340> the<08:40:29.520> right 08:40:30.468 --> 08:40:30.478 align:start position:0% if you keep adding over to the right 08:40:30.478 --> 08:40:34.070 align:start position:0% if you keep adding over to the right so<08:40:30.958> 128<08:40:31.558> and<08:40:32.040> then<08:40:32.100> we<08:40:32.280> added<08:40:32.520> 64.<08:40:33.240> we'd<08:40:33.958> get 08:40:34.070 --> 08:40:34.080 align:start position:0% so 128 and then we added 64. we'd get 08:40:34.080 --> 08:40:37.190 align:start position:0% so 128 and then we added 64. we'd get 192<08:40:34.680> and<08:40:34.920> so<08:40:35.100> on<08:40:35.218> and<08:40:35.340> so<08:40:35.520> forth<08:40:35.878> so<08:40:36.660> we<08:40:37.080> can 08:40:37.190 --> 08:40:37.200 align:start position:0% 192 and so on and so forth so we can 08:40:37.200 --> 08:40:39.170 align:start position:0% 192 and so on and so forth so we can actually<08:40:37.378> have<08:40:37.680> a<08:40:37.860> number<08:40:38.040> of<08:40:38.218> custom<08:40:38.580> subnet 08:40:39.170 --> 08:40:39.180 align:start position:0% actually have a number of custom subnet 08:40:39.180 --> 08:40:42.650 align:start position:0% actually have a number of custom subnet mask<08:40:39.420> values<08:40:40.080> in<08:40:40.680> the<08:40:40.920> last<08:40:41.100> octet<08:40:41.700> and<08:40:42.540> that's 08:40:42.650 --> 08:40:42.660 align:start position:0% mask values in the last octet and that's 08:40:42.660 --> 08:40:45.410 align:start position:0% mask values in the last octet and that's those<08:40:42.898> are<08:40:43.080> these<08:40:43.378> and<08:40:43.978> so<08:40:44.160> you<08:40:44.280> can<08:40:44.398> see<08:40:44.700> in 08:40:45.410 --> 08:40:45.420 align:start position:0% those are these and so you can see in 08:40:45.420 --> 08:40:47.270 align:start position:0% those are these and so you can see in this<08:40:45.540> case<08:40:45.840> uh<08:40:46.500> it's<08:40:46.740> not<08:40:46.860> really<08:40:46.978> going<08:40:47.160> to 08:40:47.270 --> 08:40:47.280 align:start position:0% this case uh it's not really going to 08:40:47.280 --> 08:40:49.070 align:start position:0% this case uh it's not really going to make<08:40:47.398> much<08:40:47.580> of<08:40:47.700> a<08:40:47.820> difference<08:40:48.000> when<08:40:48.420> I<08:40:48.600> I'll<08:40:48.840> do 08:40:49.070 --> 08:40:49.080 align:start position:0% make much of a difference when I I'll do 08:40:49.080 --> 08:40:52.310 align:start position:0% make much of a difference when I I'll do all<08:40:49.200> the<08:40:49.378> binary<08:40:49.740> bidding<08:40:50.218> because 08:40:52.310 --> 08:40:52.320 align:start position:0% all the binary bidding because 08:40:52.320 --> 08:40:54.230 align:start position:0% all the binary bidding because you<08:40:52.798> see<08:40:52.978> that<08:40:53.160> the<08:40:53.280> zero<08:40:53.580> and<08:40:53.700> the<08:40:53.820> zero<08:40:54.058> is 08:40:54.230 --> 08:40:54.240 align:start position:0% you see that the zero and the zero is 08:40:54.240 --> 08:40:56.448 align:start position:0% you see that the zero and the zero is still<08:40:54.420> going<08:40:54.540> to<08:40:54.660> become<08:40:54.958> a<08:40:55.558> zero<08:40:55.920> here<08:40:56.100> and<08:40:56.340> so 08:40:56.448 --> 08:40:56.458 align:start position:0% still going to become a zero here and so 08:40:56.458 --> 08:40:58.010 align:start position:0% still going to become a zero here and so all<08:40:56.638> of<08:40:56.820> this<08:40:57.000> is<08:40:57.180> really<08:40:57.360> going<08:40:57.478> to<08:40:57.600> look<08:40:57.780> the 08:40:58.010 --> 08:40:58.020 align:start position:0% all of this is really going to look the 08:40:58.020 --> 08:40:59.990 align:start position:0% all of this is really going to look the same<08:40:58.138> and<08:40:58.680> so<08:40:58.920> our<08:40:59.100> Network<08:40:59.280> portion<08:40:59.820> is 08:40:59.990 --> 08:41:00.000 align:start position:0% same and so our Network portion is 08:41:00.000 --> 08:41:01.968 align:start position:0% same and so our Network portion is actually<08:41:00.180> going<08:41:00.360> to<08:41:00.420> look<08:41:00.600> the<08:41:00.840> same<08:41:01.020> as<08:41:01.798> it 08:41:01.968 --> 08:41:01.978 align:start position:0% actually going to look the same as it 08:41:01.978 --> 08:41:03.830 align:start position:0% actually going to look the same as it did<08:41:02.160> before<08:41:02.340> we<08:41:02.638> have<08:41:02.760> the<08:41:03.000> same<08:41:03.120> network<08:41:03.420> ID 08:41:03.830 --> 08:41:03.840 align:start position:0% did before we have the same network ID 08:41:03.840 --> 08:41:06.410 align:start position:0% did before we have the same network ID as<08:41:04.138> we<08:41:04.320> did<08:41:04.440> before<08:41:04.680> but<08:41:05.638> let's<08:41:05.820> say<08:41:06.000> that<08:41:06.240> this 08:41:06.410 --> 08:41:06.420 align:start position:0% as we did before but let's say that this 08:41:06.420 --> 08:41:08.868 align:start position:0% as we did before but let's say that this was<08:41:06.660> actually<08:41:06.898> uh<08:41:07.558> you<08:41:07.798> know<08:41:07.920> this<08:41:08.458> number<08:41:08.580> by 08:41:08.868 --> 08:41:08.878 align:start position:0% was actually uh you know this number by 08:41:08.878 --> 08:41:10.910 align:start position:0% was actually uh you know this number by the<08:41:09.058> way<08:41:09.180> is<08:41:09.780> the<08:41:10.138> same<08:41:10.320> as<08:41:10.440> the<08:41:10.558> one<08:41:10.680> we<08:41:10.798> had 08:41:10.910 --> 08:41:10.920 align:start position:0% the way is the same as the one we had 08:41:10.920 --> 08:41:15.010 align:start position:0% the way is the same as the one we had before 08:41:15.010 --> 08:41:15.020 align:start position:0% 08:41:15.020 --> 08:41:17.510 align:start position:0% 162.85.120.27<08:41:16.020> if<08:41:16.740> this<08:41:16.920> was<08:41:17.100> instead 08:41:17.510 --> 08:41:17.520 align:start position:0% 162.85.120.27 if this was instead 08:41:17.520 --> 08:41:23.468 align:start position:0% 162.85.120.27 if this was instead 162.85.120 08:41:23.468 --> 08:41:23.478 align:start position:0% 08:41:23.478 --> 08:41:27.110 align:start position:0% dot<08:41:24.478> I<08:41:24.958> don't<08:41:25.080> know<08:41:25.260> one 08:41:27.110 --> 08:41:27.120 align:start position:0% dot I don't know one 08:41:27.120 --> 08:41:29.510 align:start position:0% dot I don't know one 128<08:41:28.080> we're<08:41:28.440> gonna<08:41:28.620> have<08:41:28.798> an<08:41:28.978> issue<08:41:29.340> because 08:41:29.510 --> 08:41:29.520 align:start position:0% 128 we're gonna have an issue because 08:41:29.520 --> 08:41:31.910 align:start position:0% 128 we're gonna have an issue because this<08:41:29.940> is<08:41:30.058> going<08:41:30.180> to<08:41:30.360> be<08:41:30.478> on<08:41:30.718> these<08:41:31.620> would<08:41:31.740> say 08:41:31.910 --> 08:41:31.920 align:start position:0% this is going to be on these would say 08:41:31.920 --> 08:41:34.910 align:start position:0% this is going to be on these would say let's<08:41:32.100> be<08:41:32.340> off<08:41:32.580> and<08:41:33.420> when<08:41:33.660> they<08:41:34.020> come<08:41:34.620> down 08:41:34.910 --> 08:41:34.920 align:start position:0% let's be off and when they come down 08:41:34.920 --> 08:41:37.070 align:start position:0% let's be off and when they come down this<08:41:35.520> is<08:41:35.580> going<08:41:35.760> to<08:41:35.820> turn<08:41:36.000> into<08:41:36.180> a<08:41:36.540> zero<08:41:36.840> as 08:41:37.070 --> 08:41:37.080 align:start position:0% this is going to turn into a zero as 08:41:37.080 --> 08:41:39.048 align:start position:0% this is going to turn into a zero as opposed<08:41:37.378> to<08:41:37.440> that<08:41:37.680> one<08:41:37.798> dropping<08:41:38.280> down<08:41:38.458> and<08:41:38.878> so 08:41:39.048 --> 08:41:39.058 align:start position:0% opposed to that one dropping down and so 08:41:39.058 --> 08:41:41.868 align:start position:0% opposed to that one dropping down and so it's<08:41:39.180> going<08:41:39.360> to<08:41:39.478> change<08:41:39.840> what<08:41:40.798> our<08:41:40.978> IP<08:41:41.638> address 08:41:41.868 --> 08:41:41.878 align:start position:0% it's going to change what our IP address 08:41:41.878 --> 08:41:44.090 align:start position:0% it's going to change what our IP address in<08:41:42.240> the<08:41:42.420> end<08:41:42.540> looks<08:41:43.320> like<08:41:43.440> and<08:41:43.680> so<08:41:43.798> we<08:41:43.978> actually 08:41:44.090 --> 08:41:44.100 align:start position:0% in the end looks like and so we actually 08:41:44.100 --> 08:41:45.770 align:start position:0% in the end looks like and so we actually need<08:41:44.340> to<08:41:44.458> do<08:41:44.580> some<08:41:44.760> backward<08:41:45.120> engineering<08:41:45.600> to 08:41:45.770 --> 08:41:45.780 align:start position:0% need to do some backward engineering to 08:41:45.780 --> 08:41:47.810 align:start position:0% need to do some backward engineering to get<08:41:45.898> to<08:41:46.080> our<08:41:46.200> subnet<08:41:46.558> mask<08:41:46.740> now<08:41:47.280> this<08:41:47.458> is<08:41:47.580> all 08:41:47.810 --> 08:41:47.820 align:start position:0% get to our subnet mask now this is all 08:41:47.820 --> 08:41:49.788 align:start position:0% get to our subnet mask now this is all really<08:41:48.058> complex<08:41:48.478> and<08:41:48.898> when<08:41:49.020> we<08:41:49.138> get<08:41:49.260> into<08:41:49.378> if 08:41:49.788 --> 08:41:49.798 align:start position:0% really complex and when we get into if 08:41:49.798 --> 08:41:51.170 align:start position:0% really complex and when we get into if you<08:41:49.920> ever<08:41:50.040> get<08:41:50.218> into<08:41:50.280> Cisco<08:41:50.760> you'd<08:41:51.058> really 08:41:51.170 --> 08:41:51.180 align:start position:0% you ever get into Cisco you'd really 08:41:51.180 --> 08:41:53.270 align:start position:0% you ever get into Cisco you'd really have<08:41:51.360> to<08:41:51.478> know<08:41:51.660> this<08:41:51.898> but<08:41:52.500> for<08:41:52.740> our<08:41:52.920> purposes 08:41:53.270 --> 08:41:53.280 align:start position:0% have to know this but for our purposes 08:41:53.280 --> 08:41:54.708 align:start position:0% have to know this but for our purposes you<08:41:53.580> really<08:41:53.700> don't<08:41:53.878> need<08:41:54.058> to<08:41:54.120> know<08:41:54.240> this<08:41:54.478> that 08:41:54.708 --> 08:41:54.718 align:start position:0% you really don't need to know this that 08:41:54.718 --> 08:41:57.650 align:start position:0% you really don't need to know this that in<08:41:55.080> depth<08:41:55.798> all<08:41:56.340> right<08:41:56.520> so<08:41:56.760> just<08:41:56.940> to<08:41:57.120> recap<08:41:57.478> what 08:41:57.650 --> 08:41:57.660 align:start position:0% in depth all right so just to recap what 08:41:57.660 --> 08:42:00.048 align:start position:0% in depth all right so just to recap what we<08:41:57.840> talked<08:41:58.080> about<08:41:58.200> here<08:41:58.558> we<08:41:59.340> got<08:41:59.520> a<08:41:59.760> basic 08:42:00.048 --> 08:42:00.058 align:start position:0% we talked about here we got a basic 08:42:00.058 --> 08:42:01.910 align:start position:0% we talked about here we got a basic understanding<08:42:00.540> of<08:42:00.718> a<08:42:00.840> lot<08:42:00.958> of<08:42:01.080> things<08:42:01.260> not<08:42:01.740> too 08:42:01.910 --> 08:42:01.920 align:start position:0% understanding of a lot of things not too 08:42:01.920 --> 08:42:03.230 align:start position:0% understanding of a lot of things not too in<08:42:02.160> depth<08:42:02.398> and<08:42:02.458> you<08:42:02.580> might<08:42:02.700> need<08:42:02.820> to<08:42:02.940> re-watch 08:42:03.230 --> 08:42:03.240 align:start position:0% in depth and you might need to re-watch 08:42:03.240 --> 08:42:05.090 align:start position:0% in depth and you might need to re-watch this<08:42:03.420> video<08:42:03.600> to<08:42:03.840> really<08:42:04.020> get<08:42:04.200> it<08:42:04.378> and<08:42:04.920> maybe 08:42:05.090 --> 08:42:05.100 align:start position:0% this video to really get it and maybe 08:42:05.100 --> 08:42:07.610 align:start position:0% this video to really get it and maybe even<08:42:05.398> do<08:42:05.940> a<08:42:06.120> little<08:42:06.240> bit<08:42:06.360> of<08:42:06.540> exercises<08:42:07.378> on 08:42:07.610 --> 08:42:07.620 align:start position:0% even do a little bit of exercises on 08:42:07.620 --> 08:42:08.448 align:start position:0% even do a little bit of exercises on your<08:42:07.740> own 08:42:08.448 --> 08:42:08.458 align:start position:0% your own 08:42:08.458 --> 08:42:10.548 align:start position:0% your own first<08:42:08.940> we<08:42:09.298> talked<08:42:09.600> about<08:42:09.718> the<08:42:10.440> difference 08:42:10.548 --> 08:42:10.558 align:start position:0% first we talked about the difference 08:42:10.558 --> 08:42:13.490 align:start position:0% first we talked about the difference between<08:42:10.978> a<08:42:11.820> network<08:42:12.000> address<08:42:12.420> and<08:42:13.200> a<08:42:13.320> network 08:42:13.490 --> 08:42:13.500 align:start position:0% between a network address and a network 08:42:13.500 --> 08:42:15.530 align:start position:0% between a network address and a network name<08:42:13.798> remembering<08:42:14.760> that<08:42:14.940> the<08:42:15.120> three<08:42:15.298> network 08:42:15.530 --> 08:42:15.540 align:start position:0% name remembering that the three network 08:42:15.540 --> 08:42:18.530 align:start position:0% name remembering that the three network name<08:42:16.020> services<08:42:16.378> that<08:42:17.280> match<08:42:17.520> a<08:42:17.940> name<08:42:18.120> such<08:42:18.360> as 08:42:18.530 --> 08:42:18.540 align:start position:0% name services that match a name such as 08:42:18.540 --> 08:42:21.048 align:start position:0% name services that match a name such as Bill's<08:42:18.958> laptop<08:42:19.378> to<08:42:20.040> an<08:42:20.280> address<08:42:20.458> which<08:42:20.878> would 08:42:21.048 --> 08:42:21.058 align:start position:0% Bill's laptop to an address which would 08:42:21.058 --> 08:42:24.650 align:start position:0% Bill's laptop to an address which would be<08:42:21.180> something<08:42:21.298> like<08:42:21.540> 192.168.0.1 08:42:24.650 --> 08:42:24.660 align:start position:0% 08:42:24.660 --> 08:42:27.410 align:start position:0% uh<08:42:25.378> we<08:42:25.558> can<08:42:25.740> use<08:42:25.920> either<08:42:26.160> DNS<08:42:26.700> the<08:42:26.940> domain<08:42:27.298> name 08:42:27.410 --> 08:42:27.420 align:start position:0% uh we can use either DNS the domain name 08:42:27.420 --> 08:42:29.990 align:start position:0% uh we can use either DNS the domain name service<08:42:27.780> which<08:42:28.138> is<08:42:28.260> the<08:42:28.558> most<08:42:28.740> popular<08:42:28.978> one 08:42:29.990 --> 08:42:30.000 align:start position:0% service which is the most popular one 08:42:30.000 --> 08:42:31.850 align:start position:0% service which is the most popular one something<08:42:30.540> called<08:42:30.840> wins<08:42:31.200> which<08:42:31.440> is<08:42:31.558> specific 08:42:31.850 --> 08:42:31.860 align:start position:0% something called wins which is specific 08:42:31.860 --> 08:42:35.330 align:start position:0% something called wins which is specific to<08:42:32.160> Windows<08:42:32.580> or<08:42:33.420> net<08:42:33.660> bios<08:42:34.200> also<08:42:34.798> a<08:42:34.978> Windows 08:42:35.330 --> 08:42:35.340 align:start position:0% to Windows or net bios also a Windows 08:42:35.340 --> 08:42:38.330 align:start position:0% to Windows or net bios also a Windows based 08:42:38.330 --> 08:42:38.340 align:start position:0% 08:42:38.340 --> 08:42:39.830 align:start position:0% naming<08:42:39.058> system 08:42:39.830 --> 08:42:39.840 align:start position:0% naming system 08:42:39.840 --> 08:42:41.270 align:start position:0% naming system the<08:42:40.138> one<08:42:40.320> we<08:42:40.440> want<08:42:40.558> to<08:42:40.680> be<08:42:40.740> most<08:42:40.860> familiar<08:42:41.160> with 08:42:41.270 --> 08:42:41.280 align:start position:0% the one we want to be most familiar with 08:42:41.280 --> 08:42:42.770 align:start position:0% the one we want to be most familiar with is<08:42:41.458> this<08:42:41.700> this<08:42:42.000> one's<08:42:42.298> not<08:42:42.420> really<08:42:42.540> used 08:42:42.770 --> 08:42:42.780 align:start position:0% is this this one's not really used 08:42:42.780 --> 08:42:44.930 align:start position:0% is this this one's not really used anymore<08:42:43.020> netbios<08:42:43.920> is<08:42:44.100> still<08:42:44.280> used<08:42:44.458> in<08:42:44.760> certain 08:42:44.930 --> 08:42:44.940 align:start position:0% anymore netbios is still used in certain 08:42:44.940 --> 08:42:46.730 align:start position:0% anymore netbios is still used in certain instances<08:42:45.420> especially<08:42:45.898> in<08:42:46.020> older<08:42:46.320> networks 08:42:46.730 --> 08:42:46.740 align:start position:0% instances especially in older networks 08:42:46.740 --> 08:42:50.270 align:start position:0% instances especially in older networks we<08:42:47.458> then<08:42:47.638> talked<08:42:48.120> about<08:42:48.360> the<08:42:48.718> IP<08:42:49.020> version<08:42:49.378> 4 08:42:50.270 --> 08:42:50.280 align:start position:0% we then talked about the IP version 4 08:42:50.280 --> 08:42:52.670 align:start position:0% we then talked about the IP version 4 address<08:42:50.700> and<08:42:51.478> the<08:42:51.660> things<08:42:51.780> that<08:42:52.020> it<08:42:52.138> requires 08:42:52.670 --> 08:42:52.680 align:start position:0% address and the things that it requires 08:42:52.680 --> 08:42:55.910 align:start position:0% address and the things that it requires including<08:42:53.580> and<08:42:53.760> remember<08:42:53.940> a<08:42:54.420> ipv4<08:42:55.138> address<08:42:55.558> is 08:42:55.910 --> 08:42:55.920 align:start position:0% including and remember a ipv4 address is 08:42:55.920 --> 08:43:00.468 align:start position:0% including and remember a ipv4 address is that<08:42:56.160> 32<08:42:56.878> bit<08:42:57.420> broken<08:42:58.320> up<08:42:58.558> into<08:42:58.740> four<08:42:59.478> octets 08:43:00.468 --> 08:43:00.478 align:start position:0% that 32 bit broken up into four octets 08:43:00.478 --> 08:43:02.510 align:start position:0% that 32 bit broken up into four octets the<08:43:00.780> reason<08:43:00.840> it's<08:43:01.020> called<08:43:01.200> an<08:43:01.378> octet<08:43:01.798> is 08:43:02.510 --> 08:43:02.520 align:start position:0% the reason it's called an octet is 08:43:02.520 --> 08:43:07.128 align:start position:0% the reason it's called an octet is because<08:43:03.020> we<08:43:04.020> have<08:43:04.200> eight<08:43:05.000> times<08:43:06.000> four 08:43:07.128 --> 08:43:07.138 align:start position:0% because we have eight times four 08:43:07.138 --> 08:43:09.708 align:start position:0% because we have eight times four gives<08:43:07.620> us<08:43:07.798> that<08:43:07.978> 32<08:43:08.398> and<08:43:08.580> we<08:43:08.700> break<08:43:08.820> it<08:43:09.058> up<08:43:09.180> so 08:43:09.708 --> 08:43:09.718 align:start position:0% gives us that 32 and we break it up so 08:43:09.718 --> 08:43:13.430 align:start position:0% gives us that 32 and we break it up so for<08:43:10.020> instance<08:43:10.398> 192<08:43:11.398> is<08:43:12.120> going<08:43:12.360> to<08:43:12.540> break<08:43:13.138> down 08:43:13.430 --> 08:43:13.440 align:start position:0% for instance 192 is going to break down 08:43:13.440 --> 08:43:17.868 align:start position:0% for instance 192 is going to break down to<08:43:13.920> a<08:43:14.100> certain<08:43:14.360> amount<08:43:15.360> of<08:43:15.540> bits<08:43:15.898> okay 08:43:17.868 --> 08:43:17.878 align:start position:0% to a certain amount of bits okay 08:43:17.878 --> 08:43:20.330 align:start position:0% to a certain amount of bits okay we<08:43:18.360> also<08:43:18.600> talked<08:43:18.898> about<08:43:18.958> defining<08:43:19.620> subnetting 08:43:20.330 --> 08:43:20.340 align:start position:0% we also talked about defining subnetting 08:43:20.340 --> 08:43:22.548 align:start position:0% we also talked about defining subnetting in<08:43:20.520> a<08:43:20.638> subnet<08:43:21.000> mask<08:43:21.298> which<08:43:22.080> the<08:43:22.378> most 08:43:22.548 --> 08:43:22.558 align:start position:0% in a subnet mask which the most 08:43:22.558 --> 08:43:28.128 align:start position:0% in a subnet mask which the most important<08:43:22.978> thing<08:43:23.160> it<08:43:23.398> does<08:43:23.660> is<08:43:24.660> distinguishes 08:43:28.128 --> 08:43:28.138 align:start position:0% 08:43:28.138 --> 08:43:31.368 align:start position:0% our<08:43:28.860> Network 08:43:31.368 --> 08:43:31.378 align:start position:0% 08:43:31.378 --> 08:43:33.770 align:start position:0% from<08:43:31.978> our<08:43:32.340> node 08:43:33.770 --> 08:43:33.780 align:start position:0% from our node 08:43:33.780 --> 08:43:39.350 align:start position:0% from our node ID<08:43:34.260> in<08:43:34.978> other<08:43:35.040> words<08:43:35.280> what's<08:43:36.120> our<08:43:36.478> area<08:43:37.138> code 08:43:39.350 --> 08:43:39.360 align:start position:0% ID in other words what's our area code 08:43:39.360 --> 08:43:43.430 align:start position:0% ID in other words what's our area code and<08:43:40.020> then<08:43:40.138> what<08:43:40.500> is<08:43:40.680> our<08:43:41.100> phone<08:43:41.760> number 08:43:43.430 --> 08:43:43.440 align:start position:0% and then what is our phone number 08:43:43.440 --> 08:43:45.888 align:start position:0% and then what is our phone number we<08:43:43.798> can<08:43:43.920> have<08:43:44.100> the<08:43:44.340> same<08:43:44.520> phone<08:43:44.940> number 08:43:45.888 --> 08:43:45.898 align:start position:0% we can have the same phone number 08:43:45.898 --> 08:43:47.930 align:start position:0% we can have the same phone number in<08:43:46.320> different<08:43:46.500> area<08:43:46.740> codes<08:43:47.040> but<08:43:47.520> they<08:43:47.638> go<08:43:47.820> to 08:43:47.930 --> 08:43:47.940 align:start position:0% in different area codes but they go to 08:43:47.940 --> 08:43:49.310 align:start position:0% in different area codes but they go to very<08:43:48.120> different<08:43:48.298> people 08:43:49.310 --> 08:43:49.320 align:start position:0% very different people 08:43:49.320 --> 08:43:51.230 align:start position:0% very different people we<08:43:49.680> also<08:43:49.920> talked<08:43:50.100> about<08:43:50.160> the<08:43:50.398> rules<08:43:50.638> of<08:43:50.820> subnet 08:43:51.230 --> 08:43:51.240 align:start position:0% we also talked about the rules of subnet 08:43:51.240 --> 08:43:53.750 align:start position:0% we also talked about the rules of subnet masks<08:43:51.600> and<08:43:51.718> IP<08:43:52.020> addresses<08:43:52.500> we<08:43:53.100> can<08:43:53.280> only<08:43:53.398> have 08:43:53.750 --> 08:43:53.760 align:start position:0% masks and IP addresses we can only have 08:43:53.760 --> 08:43:58.788 align:start position:0% masks and IP addresses we can only have one<08:43:54.240> IP<08:43:54.660> address 08:43:58.788 --> 08:43:58.798 align:start position:0% 08:43:58.798 --> 08:44:02.090 align:start position:0% on<08:43:59.520> any<08:43:59.878> network 08:44:02.090 --> 08:44:02.100 align:start position:0% on any network 08:44:02.100 --> 08:44:06.310 align:start position:0% on any network and<08:44:03.298> we<08:44:03.958> can<08:44:04.260> not<08:44:04.860> use 08:44:06.310 --> 08:44:06.320 align:start position:0% and we can not use 08:44:06.320 --> 08:44:08.388 align:start position:0% and we can not use 127.0.0.1<08:44:07.320> because<08:44:07.558> that<08:44:07.860> is<08:44:07.978> what<08:44:08.100> we<08:44:08.218> call 08:44:08.388 --> 08:44:08.398 align:start position:0% 127.0.0.1 because that is what we call 08:44:08.398 --> 08:44:10.368 align:start position:0% 127.0.0.1 because that is what we call the<08:44:08.580> loop<08:44:08.940> back<08:44:09.180> address 08:44:10.368 --> 08:44:10.378 align:start position:0% the loop back address 08:44:10.378 --> 08:44:12.770 align:start position:0% the loop back address as<08:44:10.740> far<08:44:10.920> as<08:44:11.040> for<08:44:11.160> the<08:44:11.280> subnet<08:44:11.638> mask<08:44:11.878> remember 08:44:12.770 --> 08:44:12.780 align:start position:0% as far as for the subnet mask remember 08:44:12.780 --> 08:44:15.170 align:start position:0% as far as for the subnet mask remember that<08:44:13.138> all<08:44:13.378> ones<08:44:13.798> have<08:44:14.040> to<08:44:14.218> be<08:44:14.340> continuous<08:44:14.878> from 08:44:15.170 --> 08:44:15.180 align:start position:0% that all ones have to be continuous from 08:44:15.180 --> 08:44:16.190 align:start position:0% that all ones have to be continuous from the<08:44:15.360> left 08:44:16.190 --> 08:44:16.200 align:start position:0% the left 08:44:16.200 --> 08:44:18.230 align:start position:0% the left and<08:44:16.680> zeros<08:44:17.040> have<08:44:17.218> to<08:44:17.340> be<08:44:17.458> continuous<08:44:17.820> from<08:44:18.120> the 08:44:18.230 --> 08:44:18.240 align:start position:0% and zeros have to be continuous from the 08:44:18.240 --> 08:44:19.250 align:start position:0% and zeros have to be continuous from the right 08:44:19.250 --> 08:44:19.260 align:start position:0% right 08:44:19.260 --> 08:44:24.530 align:start position:0% right our<08:44:19.680> defaults<08:44:20.280> our<08:44:21.000> 255.255.0.0.0 08:44:24.530 --> 08:44:24.540 align:start position:0% 08:44:24.540 --> 08:44:26.930 align:start position:0% and<08:44:25.020> then<08:44:25.138> 255 08:44:26.930 --> 08:44:26.940 align:start position:0% and then 255 08:44:26.940 --> 08:44:28.990 align:start position:0% and then 255 I'm<08:44:27.298> sorry<08:44:27.478> I<08:44:27.600> think<08:44:27.718> I<08:44:27.840> just<08:44:27.958> said 08:44:28.990 --> 08:44:29.000 align:start position:0% I'm sorry I think I just said 08:44:29.000 --> 08:44:31.510 align:start position:0% I'm sorry I think I just said 255.0.0.0 08:44:31.510 --> 08:44:31.520 align:start position:0% 255.0.0.0 08:44:31.520 --> 08:44:37.150 align:start position:0% 255.0.0.0 285.255.0.0.0<08:44:32.520> and 08:44:37.150 --> 08:44:37.160 align:start position:0% 08:44:37.160 --> 08:44:40.010 align:start position:0% 255.255.255.0<08:44:38.160> those<08:44:38.638> are<08:44:38.878> our<08:44:39.000> defaults<08:44:39.478> and 08:44:40.010 --> 08:44:40.020 align:start position:0% 255.255.255.0 those are our defaults and 08:44:40.020 --> 08:44:42.288 align:start position:0% 255.255.255.0 those are our defaults and so<08:44:40.138> we<08:44:40.378> talked<08:44:41.040> about<08:44:41.100> applying<08:44:41.700> a<08:44:41.878> subnet 08:44:42.288 --> 08:44:42.298 align:start position:0% so we talked about applying a subnet 08:44:42.298 --> 08:44:45.708 align:start position:0% so we talked about applying a subnet mask<08:44:42.500> using<08:44:43.500> something<08:44:43.798> called<08:44:44.280> anding 08:44:45.708 --> 08:44:45.718 align:start position:0% mask using something called anding 08:44:45.718 --> 08:44:47.750 align:start position:0% mask using something called anding and<08:44:46.138> we<08:44:46.260> looked<08:44:46.500> at<08:44:46.558> how<08:44:46.798> that<08:44:47.040> divides<08:44:47.580> up 08:44:47.750 --> 08:44:47.760 align:start position:0% and we looked at how that divides up 08:44:47.760 --> 08:44:50.388 align:start position:0% and we looked at how that divides up again<08:44:48.478> the<08:44:49.138> network<08:44:49.378> ID<08:44:49.680> from<08:44:49.978> the<08:44:50.100> node<08:44:50.218> ID 08:44:50.388 --> 08:44:50.398 align:start position:0% again the network ID from the node ID 08:44:50.398 --> 08:44:52.730 align:start position:0% again the network ID from the node ID and<08:44:50.638> we<08:44:50.760> saw<08:44:50.878> that<08:44:51.058> in<08:44:51.298> practice<08:44:51.620> finally<08:44:52.620> we 08:44:52.730 --> 08:44:52.740 align:start position:0% and we saw that in practice finally we 08:44:52.740 --> 08:44:54.948 align:start position:0% and we saw that in practice finally we talked<08:44:53.040> very<08:44:53.160> briefly<08:44:53.580> about<08:44:53.878> custom<08:44:54.420> subnet 08:44:54.948 --> 08:44:54.958 align:start position:0% talked very briefly about custom subnet 08:44:54.958 --> 08:44:56.270 align:start position:0% talked very briefly about custom subnet masks<08:44:55.320> something<08:44:55.558> that<08:44:55.740> we<08:44:55.860> don't<08:44:55.978> have<08:44:56.100> to 08:44:56.270 --> 08:44:56.280 align:start position:0% masks something that we don't have to 08:44:56.280 --> 08:44:58.730 align:start position:0% masks something that we don't have to get<08:44:56.458> very<08:44:57.058> much<08:44:57.240> into<08:44:57.660> but<08:44:58.260> we<08:44:58.440> talked<08:44:58.680> about 08:44:58.730 --> 08:44:58.740 align:start position:0% get very much into but we talked about 08:44:58.740 --> 08:45:03.730 align:start position:0% get very much into but we talked about how<08:44:59.040> if<08:44:59.160> we<08:44:59.280> had<08:44:59.398> 255.255 08:45:03.730 --> 08:45:03.740 align:start position:0% 08:45:03.740 --> 08:45:08.570 align:start position:0% .255<08:45:05.120> dot<08:45:06.120> for<08:45:06.298> instance<08:45:06.620> 128<08:45:07.620> we<08:45:08.280> could<08:45:08.398> have 08:45:08.570 --> 08:45:08.580 align:start position:0% .255 dot for instance 128 we could have 08:45:08.580 --> 08:45:12.530 align:start position:0% .255 dot for instance 128 we could have these<08:45:08.940> sort<08:45:09.120> of<08:45:09.240> sub<08:45:09.600> subnets<08:45:10.260> or<08:45:10.920> these<08:45:11.340> uh<08:45:11.878> we 08:45:12.530 --> 08:45:12.540 align:start position:0% these sort of sub subnets or these uh we 08:45:12.540 --> 08:45:14.270 align:start position:0% these sort of sub subnets or these uh we could<08:45:12.660> break<08:45:12.840> it<08:45:13.020> down<08:45:13.200> even<08:45:13.440> further<08:45:13.860> and 08:45:14.270 --> 08:45:14.280 align:start position:0% could break it down even further and 08:45:14.280 --> 08:45:16.250 align:start position:0% could break it down even further and therefore<08:45:14.638> we<08:45:15.180> could<08:45:15.298> start<08:45:15.540> to<08:45:15.780> do<08:45:15.958> a<08:45:16.138> lot 08:45:16.250 --> 08:45:16.260 align:start position:0% therefore we could start to do a lot 08:45:16.260 --> 08:45:18.110 align:start position:0% therefore we could start to do a lot more<08:45:16.378> stuff<08:45:16.680> and<08:45:17.040> in<08:45:17.218> the<08:45:17.398> next<08:45:17.520> module<08:45:17.940> I'm 08:45:18.110 --> 08:45:18.120 align:start position:0% more stuff and in the next module I'm 08:45:18.120 --> 08:45:19.730 align:start position:0% more stuff and in the next module I'm going<08:45:18.240> to<08:45:18.298> talk<08:45:18.478> about<08:45:18.660> this<08:45:19.080> in<08:45:19.378> a<08:45:19.500> lot<08:45:19.558> more 08:45:19.730 --> 08:45:19.740 align:start position:0% going to talk about this in a lot more 08:45:19.740 --> 08:45:25.590 align:start position:0% going to talk about this in a lot more detail<08:45:20.160> and<08:45:21.000> why<08:45:21.298> we<08:45:21.478> would<08:45:21.600> want<08:45:21.780> to<08:45:21.898> do<08:45:22.080> it 08:45:25.590 --> 08:45:25.600 align:start position:0% 08:45:25.600 --> 08:45:34.208 align:start position:0% [Music] 08:45:34.208 --> 08:45:34.218 align:start position:0% [Music] 08:45:34.218 --> 08:45:45.708 align:start position:0% [Music] thank<08:45:35.218> you 08:45:45.708 --> 08:45:45.718 align:start position:0% 08:45:45.718 --> 08:45:48.610 align:start position:0% Network<08:45:46.440> routing<08:45:47.040> and<08:45:47.458> IP<08:45:47.820> addressing 08:45:48.610 --> 08:45:48.620 align:start position:0% Network routing and IP addressing 08:45:48.620 --> 08:45:52.310 align:start position:0% Network routing and IP addressing default<08:45:49.620> and<08:45:50.040> custom<08:45:50.340> addressing 08:45:52.310 --> 08:45:52.320 align:start position:0% default and custom addressing 08:45:52.320 --> 08:45:54.708 align:start position:0% default and custom addressing so<08:45:52.798> we<08:45:52.978> described<08:45:53.580> in<08:45:53.760> the<08:45:53.940> previous<08:45:54.058> module 08:45:54.708 --> 08:45:54.718 align:start position:0% so we described in the previous module 08:45:54.718 --> 08:45:57.288 align:start position:0% so we described in the previous module subnetting<08:45:55.500> how<08:45:55.798> to<08:45:56.040> determine<08:45:56.878> the<08:45:57.120> network 08:45:57.288 --> 08:45:57.298 align:start position:0% subnetting how to determine the network 08:45:57.298 --> 08:45:59.810 align:start position:0% subnetting how to determine the network from<08:45:57.958> the<08:45:58.138> node<08:45:58.320> ID<08:45:58.620> and<08:45:59.280> we<08:45:59.458> talked 08:45:59.810 --> 08:45:59.820 align:start position:0% from the node ID and we talked 08:45:59.820 --> 08:46:02.150 align:start position:0% from the node ID and we talked specifically<08:46:00.298> about<08:46:00.600> ipv4<08:46:01.558> and<08:46:01.860> we're<08:46:02.040> going 08:46:02.150 --> 08:46:02.160 align:start position:0% specifically about ipv4 and we're going 08:46:02.160 --> 08:46:04.368 align:start position:0% specifically about ipv4 and we're going to<08:46:02.280> continue<08:46:02.520> talking<08:46:03.000> about<08:46:03.298> ipv4<08:46:04.080> a<08:46:04.320> little 08:46:04.368 --> 08:46:04.378 align:start position:0% to continue talking about ipv4 a little 08:46:04.378 --> 08:46:08.590 align:start position:0% to continue talking about ipv4 a little bit<08:46:04.500> more<08:46:04.680> first<08:46:05.580> by<08:46:06.058> defining<08:46:06.780> the<08:46:07.680> default 08:46:08.590 --> 08:46:08.600 align:start position:0% bit more first by defining the default 08:46:08.600 --> 08:46:11.868 align:start position:0% bit more first by defining the default ipv4<08:46:09.600> addressing<08:46:10.558> scheme<08:46:10.978> now<08:46:11.458> some<08:46:11.638> of<08:46:11.760> this 08:46:11.868 --> 08:46:11.878 align:start position:0% ipv4 addressing scheme now some of this 08:46:11.878 --> 08:46:13.190 align:start position:0% ipv4 addressing scheme now some of this we<08:46:12.058> sort<08:46:12.240> of<08:46:12.360> touched<08:46:12.660> on<08:46:12.780> in<08:46:12.958> the<08:46:13.080> previous 08:46:13.190 --> 08:46:13.200 align:start position:0% we sort of touched on in the previous 08:46:13.200 --> 08:46:15.110 align:start position:0% we sort of touched on in the previous module<08:46:13.798> and<08:46:14.398> some<08:46:14.520> of<08:46:14.638> the<08:46:14.700> stuff<08:46:14.820> we're<08:46:15.000> going 08:46:15.110 --> 08:46:15.120 align:start position:0% module and some of the stuff we're going 08:46:15.120 --> 08:46:17.690 align:start position:0% module and some of the stuff we're going to<08:46:15.240> talk<08:46:15.360> about<08:46:15.478> right<08:46:15.840> now<08:46:16.080> is<08:46:16.740> going<08:46:17.040> to 08:46:17.690 --> 08:46:17.700 align:start position:0% to talk about right now is going to 08:46:17.700 --> 08:46:19.730 align:start position:0% to talk about right now is going to probably<08:46:18.120> help<08:46:18.540> clarify<08:46:19.080> that<08:46:19.260> and<08:46:19.500> so<08:46:19.620> it 08:46:19.730 --> 08:46:19.740 align:start position:0% probably help clarify that and so it 08:46:19.740 --> 08:46:21.410 align:start position:0% probably help clarify that and so it might<08:46:19.860> not<08:46:20.040> it<08:46:20.218> might<08:46:20.458> even<08:46:20.580> help<08:46:20.878> to<08:46:21.180> go<08:46:21.298> back 08:46:21.410 --> 08:46:21.420 align:start position:0% might not it might even help to go back 08:46:21.420 --> 08:46:23.448 align:start position:0% might not it might even help to go back and<08:46:21.600> watch<08:46:21.780> the<08:46:22.080> previous<08:46:22.200> module<08:46:22.860> after 08:46:23.448 --> 08:46:23.458 align:start position:0% and watch the previous module after 08:46:23.458 --> 08:46:25.490 align:start position:0% and watch the previous module after watching<08:46:23.878> this<08:46:24.120> one<08:46:24.298> after<08:46:24.958> that<08:46:25.200> we're<08:46:25.378> going 08:46:25.490 --> 08:46:25.500 align:start position:0% watching this one after that we're going 08:46:25.500 --> 08:46:28.070 align:start position:0% watching this one after that we're going to<08:46:25.620> talk<08:46:25.798> about<08:46:25.978> the<08:46:26.700> reserved<08:46:27.240> or<08:46:27.478> restricted 08:46:28.070 --> 08:46:28.080 align:start position:0% to talk about the reserved or restricted 08:46:28.080 --> 08:46:31.788 align:start position:0% to talk about the reserved or restricted ipv4<08:46:29.420> addresses<08:46:30.420> one<08:46:31.138> of<08:46:31.200> the<08:46:31.320> ones<08:46:31.500> we've 08:46:31.788 --> 08:46:31.798 align:start position:0% ipv4 addresses one of the ones we've 08:46:31.798 --> 08:46:34.128 align:start position:0% ipv4 addresses one of the ones we've already<08:46:31.920> mentioned<08:46:32.520> is<08:46:33.120> what<08:46:33.360> we<08:46:33.478> called<08:46:33.660> the 08:46:34.128 --> 08:46:34.138 align:start position:0% already mentioned is what we called the 08:46:34.138 --> 08:46:36.430 align:start position:0% already mentioned is what we called the loop<08:46:34.440> back<08:46:34.680> or 08:46:36.430 --> 08:46:36.440 align:start position:0% loop back or 08:46:36.440 --> 08:46:39.230 align:start position:0% loop back or 127.0.0.1<08:46:37.440> that's<08:46:37.978> an<08:46:38.218> example<08:46:38.520> of<08:46:38.878> a 08:46:39.230 --> 08:46:39.240 align:start position:0% 127.0.0.1 that's an example of a 08:46:39.240 --> 08:46:41.628 align:start position:0% 127.0.0.1 that's an example of a reserved<08:46:39.958> IP<08:46:40.378> address<08:46:40.558> a<08:46:40.860> restricted<08:46:41.340> IP 08:46:41.628 --> 08:46:41.638 align:start position:0% reserved IP address a restricted IP 08:46:41.638 --> 08:46:43.010 align:start position:0% reserved IP address a restricted IP address<08:46:41.760> and<08:46:42.298> so<08:46:42.420> we're<08:46:42.540> going<08:46:42.660> to<08:46:42.718> talk<08:46:42.840> about 08:46:43.010 --> 08:46:43.020 align:start position:0% address and so we're going to talk about 08:46:43.020 --> 08:46:45.410 align:start position:0% address and so we're going to talk about those<08:46:43.378> in<08:46:43.620> more<08:46:43.798> depth<08:46:44.160> and<08:46:44.700> some<08:46:44.878> of<08:46:45.000> the<08:46:45.120> ones 08:46:45.410 --> 08:46:45.420 align:start position:0% those in more depth and some of the ones 08:46:45.420 --> 08:46:46.968 align:start position:0% those in more depth and some of the ones that<08:46:45.718> some<08:46:46.020> of<08:46:46.138> the<08:46:46.260> ranges<08:46:46.620> that<08:46:46.860> are 08:46:46.968 --> 08:46:46.978 align:start position:0% that some of the ranges that are 08:46:46.978 --> 08:46:49.548 align:start position:0% that some of the ranges that are restricted<08:46:47.458> and<08:46:48.000> why<08:46:48.240> they<08:46:48.478> are<08:46:48.660> then<08:46:49.378> we're 08:46:49.548 --> 08:46:49.558 align:start position:0% restricted and why they are then we're 08:46:49.558 --> 08:46:51.708 align:start position:0% restricted and why they are then we're going<08:46:49.740> to<08:46:49.920> discuss<08:46:50.280> what<08:46:51.120> are<08:46:51.180> called<08:46:51.360> the 08:46:51.708 --> 08:46:51.718 align:start position:0% going to discuss what are called the 08:46:51.718 --> 08:46:54.170 align:start position:0% going to discuss what are called the private<08:46:51.958> address<08:46:52.260> addresses<08:46:53.040> and<08:46:53.940> we're 08:46:54.170 --> 08:46:54.180 align:start position:0% private address addresses and we're 08:46:54.180 --> 08:46:56.388 align:start position:0% private address addresses and we're gonna<08:46:54.360> talk<08:46:55.080> about<08:46:55.260> these<08:46:55.798> specifically 08:46:56.388 --> 08:46:56.398 align:start position:0% gonna talk about these specifically 08:46:56.398 --> 08:46:58.070 align:start position:0% gonna talk about these specifically because<08:46:56.700> these<08:46:57.180> are<08:46:57.240> different<08:46:57.420> from<08:46:57.840> public 08:46:58.070 --> 08:46:58.080 align:start position:0% because these are different from public 08:46:58.080 --> 08:47:00.350 align:start position:0% because these are different from public IP<08:46:58.500> addresses<08:46:59.040> uh<08:46:59.700> one<08:46:59.940> you<08:47:00.058> might<08:47:00.180> be 08:47:00.350 --> 08:47:00.360 align:start position:0% IP addresses uh one you might be 08:47:00.360 --> 08:47:02.110 align:start position:0% IP addresses uh one you might be familiar<08:47:00.660> with<08:47:00.840> is<08:47:01.138> the 08:47:02.110 --> 08:47:02.120 align:start position:0% familiar with is the 08:47:02.120 --> 08:47:05.750 align:start position:0% familiar with is the 192.168<08:47:03.120> uh<08:47:04.080> public<08:47:04.320> at<08:47:04.680> a<08:47:04.978> private<08:47:05.280> addresses 08:47:05.750 --> 08:47:05.760 align:start position:0% 192.168 uh public at a private addresses 08:47:05.760 --> 08:47:07.368 align:start position:0% 192.168 uh public at a private addresses rather<08:47:06.058> and<08:47:06.600> you'll<08:47:06.780> this<08:47:07.080> is<08:47:07.138> going<08:47:07.320> to 08:47:07.368 --> 08:47:07.378 align:start position:0% rather and you'll this is going to 08:47:07.378 --> 08:47:09.410 align:start position:0% rather and you'll this is going to explain<08:47:07.558> why<08:47:07.978> every<08:47:08.340> router<08:47:08.820> that<08:47:09.240> you 08:47:09.410 --> 08:47:09.420 align:start position:0% explain why every router that you 08:47:09.420 --> 08:47:11.388 align:start position:0% explain why every router that you purchase<08:47:09.718> that<08:47:10.080> you<08:47:10.620> know<08:47:10.680> electronics<08:47:11.160> store 08:47:11.388 --> 08:47:11.398 align:start position:0% purchase that you know electronics store 08:47:11.398 --> 08:47:14.330 align:start position:0% purchase that you know electronics store has<08:47:11.760> this<08:47:12.180> as<08:47:12.478> its<08:47:12.840> default<08:47:13.200> not<08:47:13.740> everyone<08:47:13.978> but 08:47:14.330 --> 08:47:14.340 align:start position:0% has this as its default not everyone but 08:47:14.340 --> 08:47:15.770 align:start position:0% has this as its default not everyone but a<08:47:14.458> lot<08:47:14.520> of<08:47:14.638> them<08:47:14.700> have<08:47:14.878> this<08:47:15.120> is<08:47:15.240> the<08:47:15.420> default 08:47:15.770 --> 08:47:15.780 align:start position:0% a lot of them have this is the default 08:47:15.780 --> 08:47:17.628 align:start position:0% a lot of them have this is the default IP<08:47:16.200> address<08:47:16.378> and<08:47:16.620> yet<08:47:16.740> we<08:47:17.040> talked<08:47:17.280> about<08:47:17.340> how 08:47:17.628 --> 08:47:17.638 align:start position:0% IP address and yet we talked about how 08:47:17.638 --> 08:47:19.190 align:start position:0% IP address and yet we talked about how you<08:47:17.820> can't<08:47:18.000> have<08:47:18.180> more<08:47:18.420> than<08:47:18.540> one<08:47:18.660> IP<08:47:19.020> address 08:47:19.190 --> 08:47:19.200 align:start position:0% you can't have more than one IP address 08:47:19.200 --> 08:47:20.930 align:start position:0% you can't have more than one IP address with<08:47:19.500> any<08:47:19.680> device<08:47:19.920> and<08:47:20.520> so<08:47:20.638> we're<08:47:20.760> going<08:47:20.878> to 08:47:20.930 --> 08:47:20.940 align:start position:0% with any device and so we're going to 08:47:20.940 --> 08:47:23.388 align:start position:0% with any device and so we're going to describe<08:47:21.298> why<08:47:21.660> with<08:47:22.200> private<08:47:22.558> IP<08:47:22.920> addresses 08:47:23.388 --> 08:47:23.398 align:start position:0% describe why with private IP addresses 08:47:23.398 --> 08:47:24.708 align:start position:0% describe why with private IP addresses this<08:47:23.700> is<08:47:23.760> the<08:47:23.940> case<08:47:24.058> and<08:47:24.298> we'll<08:47:24.420> talk<08:47:24.600> about 08:47:24.708 --> 08:47:24.718 align:start position:0% this is the case and we'll talk about 08:47:24.718 --> 08:47:26.628 align:start position:0% this is the case and we'll talk about some<08:47:25.020> other<08:47:25.200> private<08:47:25.558> IP<08:47:25.860> addresses<08:47:26.280> as<08:47:26.458> well 08:47:26.628 --> 08:47:26.638 align:start position:0% some other private IP addresses as well 08:47:26.638 --> 08:47:29.830 align:start position:0% some other private IP addresses as well now<08:47:27.360> we're<08:47:27.540> going<08:47:27.718> to<08:47:27.780> talk<08:47:27.958> about<08:47:28.200> the<08:47:28.620> ipv4 08:47:29.830 --> 08:47:29.840 align:start position:0% now we're going to talk about the ipv4 08:47:29.840 --> 08:47:32.388 align:start position:0% now we're going to talk about the ipv4 formulas<08:47:30.840> and<08:47:31.378> that's<08:47:31.500> the<08:47:31.798> that's<08:47:32.160> what 08:47:32.388 --> 08:47:32.398 align:start position:0% formulas and that's the that's what 08:47:32.398 --> 08:47:37.010 align:start position:0% formulas and that's the that's what allows<08:47:32.820> us<08:47:32.940> to<08:47:33.240> determine<08:47:33.798> how<08:47:34.798> many 08:47:37.010 --> 08:47:37.020 align:start position:0% 08:47:37.020 --> 08:47:39.288 align:start position:0% hosts 08:47:39.288 --> 08:47:39.298 align:start position:0% hosts 08:47:39.298 --> 08:47:43.368 align:start position:0% hosts and<08:47:40.200> networks<08:47:41.040> are<08:47:41.700> permissible<08:47:42.260> based<08:47:43.260> on 08:47:43.368 --> 08:47:43.378 align:start position:0% and networks are permissible based on 08:47:43.378 --> 08:47:46.070 align:start position:0% and networks are permissible based on the<08:47:43.860> type<08:47:44.040> of<08:47:44.218> IP<08:47:44.520> address<08:47:44.760> the<08:47:45.540> class<08:47:45.780> that 08:47:46.070 --> 08:47:46.080 align:start position:0% the type of IP address the class that 08:47:46.080 --> 08:47:48.410 align:start position:0% the type of IP address the class that it's<08:47:46.260> in<08:47:46.458> and<08:47:47.458> the<08:47:47.580> subnet<08:47:47.878> mask<08:47:48.120> that's 08:47:48.410 --> 08:47:48.420 align:start position:0% it's in and the subnet mask that's 08:47:48.420 --> 08:47:50.510 align:start position:0% it's in and the subnet mask that's supplied<08:47:48.840> and<08:47:49.378> this<08:47:49.558> will<08:47:49.680> help<08:47:49.920> us<08:47:50.040> also 08:47:50.510 --> 08:47:50.520 align:start position:0% supplied and this will help us also 08:47:50.520 --> 08:47:53.090 align:start position:0% supplied and this will help us also determine<08:47:51.000> and<08:47:51.180> talk<08:47:51.540> about<08:47:51.660> in<08:47:51.840> a<08:47:51.958> second<08:47:52.100> uh 08:47:53.090 --> 08:47:53.100 align:start position:0% determine and talk about in a second uh 08:47:53.100 --> 08:47:55.368 align:start position:0% determine and talk about in a second uh why<08:47:53.398> we<08:47:53.638> might<08:47:53.760> want<08:47:53.878> to<08:47:54.000> use<08:47:54.180> custom<08:47:54.600> subnet 08:47:55.368 --> 08:47:55.378 align:start position:0% why we might want to use custom subnet 08:47:55.378 --> 08:47:57.888 align:start position:0% why we might want to use custom subnet masks<08:47:55.740> and<08:47:55.920> custom<08:47:56.160> IP<08:47:56.580> addresses 08:47:57.888 --> 08:47:57.898 align:start position:0% masks and custom IP addresses 08:47:57.898 --> 08:47:59.388 align:start position:0% masks and custom IP addresses so<08:47:58.260> then<08:47:58.378> we're<08:47:58.558> going<08:47:58.680> to<08:47:58.798> talk<08:47:58.920> about<08:47:59.040> the 08:47:59.388 --> 08:47:59.398 align:start position:0% so then we're going to talk about the 08:47:59.398 --> 08:48:01.850 align:start position:0% so then we're going to talk about the default<08:47:59.820> gateway<08:48:00.420> is<08:48:00.718> this<08:48:01.020> gets<08:48:01.320> back<08:48:01.500> to 08:48:01.850 --> 08:48:01.860 align:start position:0% default gateway is this gets back to 08:48:01.860 --> 08:48:04.190 align:start position:0% default gateway is this gets back to actually<08:48:02.520> this<08:48:02.878> right<08:48:03.120> here<08:48:03.360> it<08:48:03.600> is<08:48:03.840> the 08:48:04.190 --> 08:48:04.200 align:start position:0% actually this right here it is the 08:48:04.200 --> 08:48:08.690 align:start position:0% actually this right here it is the device<08:48:05.100> which<08:48:05.820> the<08:48:06.780> any<08:48:07.320> node<08:48:07.798> needs<08:48:08.458> to<08:48:08.520> know 08:48:08.690 --> 08:48:08.700 align:start position:0% device which the any node needs to know 08:48:08.700 --> 08:48:10.310 align:start position:0% device which the any node needs to know in<08:48:08.940> order<08:48:09.120> to<08:48:09.298> get<08:48:09.420> out<08:48:09.600> to<08:48:09.780> the<08:48:09.898> network<08:48:10.020> and 08:48:10.310 --> 08:48:10.320 align:start position:0% in order to get out to the network and 08:48:10.320 --> 08:48:12.770 align:start position:0% in order to get out to the network and to<08:48:10.500> the<08:48:10.620> rest<08:48:10.798> of<08:48:11.520> the<08:48:12.058> um<08:48:12.120> the<08:48:12.420> rest<08:48:12.540> of<08:48:12.660> the 08:48:12.770 --> 08:48:12.780 align:start position:0% to the rest of the um the rest of the 08:48:12.780 --> 08:48:14.030 align:start position:0% to the rest of the um the rest of the world 08:48:14.030 --> 08:48:14.040 align:start position:0% world 08:48:14.040 --> 08:48:16.910 align:start position:0% world finally<08:48:14.878> we're<08:48:15.298> going<08:48:15.478> to<08:48:15.600> talk<08:48:15.840> about<08:48:16.080> custom 08:48:16.910 --> 08:48:16.920 align:start position:0% finally we're going to talk about custom 08:48:16.920 --> 08:48:19.030 align:start position:0% finally we're going to talk about custom IP<08:48:17.398> address<08:48:17.638> schemes 08:48:19.030 --> 08:48:19.040 align:start position:0% IP address schemes 08:48:19.040 --> 08:48:23.990 align:start position:0% IP address schemes vlsm<08:48:20.040> and<08:48:21.020> cidr<08:48:22.218> these<08:48:23.218> are<08:48:23.398> a<08:48:23.580> little<08:48:23.638> more<08:48:23.878> in 08:48:23.990 --> 08:48:24.000 align:start position:0% vlsm and cidr these are a little more in 08:48:24.000 --> 08:48:25.788 align:start position:0% vlsm and cidr these are a little more in depth<08:48:24.298> but<08:48:24.420> these<08:48:24.718> really<08:48:24.840> get<08:48:25.080> back<08:48:25.320> to<08:48:25.558> the 08:48:25.788 --> 08:48:25.798 align:start position:0% depth but these really get back to the 08:48:25.798 --> 08:48:28.670 align:start position:0% depth but these really get back to the subnet<08:48:26.280> masks<08:48:26.760> and<08:48:27.298> why<08:48:27.540> we<08:48:27.718> can<08:48:27.840> apply<08:48:28.200> those 08:48:28.670 --> 08:48:28.680 align:start position:0% subnet masks and why we can apply those 08:48:28.680 --> 08:48:31.190 align:start position:0% subnet masks and why we can apply those uh<08:48:29.458> how<08:48:29.638> we<08:48:29.940> can<08:48:30.058> apply<08:48:30.360> sort<08:48:30.718> of<08:48:30.840> specific 08:48:31.190 --> 08:48:31.200 align:start position:0% uh how we can apply sort of specific 08:48:31.200 --> 08:48:33.410 align:start position:0% uh how we can apply sort of specific subnet<08:48:31.680> masks<08:48:31.978> to<08:48:32.160> things<08:48:32.340> and<08:48:32.820> we'll<08:48:33.000> look<08:48:33.180> at 08:48:33.410 --> 08:48:33.420 align:start position:0% subnet masks to things and we'll look at 08:48:33.420 --> 08:48:34.730 align:start position:0% subnet masks to things and we'll look at this<08:48:33.780> thing<08:48:33.898> which<08:48:34.080> you<08:48:34.260> might<08:48:34.378> have<08:48:34.558> seen 08:48:34.730 --> 08:48:34.740 align:start position:0% this thing which you might have seen 08:48:34.740 --> 08:48:37.368 align:start position:0% this thing which you might have seen cidr<08:48:35.458> which<08:48:35.700> is<08:48:35.878> has<08:48:36.360> to<08:48:36.540> do<08:48:36.660> with<08:48:36.840> why<08:48:37.080> there 08:48:37.368 --> 08:48:37.378 align:start position:0% cidr which is has to do with why there 08:48:37.378 --> 08:48:39.468 align:start position:0% cidr which is has to do with why there might<08:48:37.558> be<08:48:37.680> a<08:48:37.920> slash<08:48:38.340> after<08:48:38.700> an<08:48:39.000> IP<08:48:39.240> address 08:48:39.468 --> 08:48:39.478 align:start position:0% might be a slash after an IP address 08:48:39.478 --> 08:48:41.448 align:start position:0% might be a slash after an IP address which<08:48:40.200> really<08:48:40.378> gets<08:48:40.680> to<08:48:40.740> the<08:48:40.920> number<08:48:41.040> of<08:48:41.160> bits 08:48:41.448 --> 08:48:41.458 align:start position:0% which really gets to the number of bits 08:48:41.458 --> 08:48:43.070 align:start position:0% which really gets to the number of bits it<08:48:41.580> has<08:48:41.760> and<08:48:41.940> we'll<08:48:42.058> talk<08:48:42.298> about<08:48:42.420> that<08:48:42.718> just<08:48:42.898> a 08:48:43.070 --> 08:48:43.080 align:start position:0% it has and we'll talk about that just a 08:48:43.080 --> 08:48:44.990 align:start position:0% it has and we'll talk about that just a minute<08:48:43.200> now<08:48:43.798> aside<08:48:44.040> from<08:48:44.218> being<08:48:44.458> an<08:48:44.700> aspect 08:48:44.990 --> 08:48:45.000 align:start position:0% minute now aside from being an aspect 08:48:45.000 --> 08:48:47.150 align:start position:0% minute now aside from being an aspect that's<08:48:45.240> covered<08:48:45.600> in<08:48:45.780> many<08:48:46.020> areas<08:48:46.500> of<08:48:46.978> the 08:48:47.150 --> 08:48:47.160 align:start position:0% that's covered in many areas of the 08:48:47.160 --> 08:48:49.910 align:start position:0% that's covered in many areas of the network<08:48:47.280> plus<08:48:47.580> exam<08:48:48.320> understanding<08:48:49.320> the 08:48:49.910 --> 08:48:49.920 align:start position:0% network plus exam understanding the 08:48:49.920 --> 08:48:52.310 align:start position:0% network plus exam understanding the classes<08:48:50.398> in<08:48:50.760> a<08:48:50.940> default<08:48:51.240> IP<08:48:51.600> address<08:48:51.780> scheme 08:48:52.310 --> 08:48:52.320 align:start position:0% classes in a default IP address scheme 08:48:52.320 --> 08:48:54.770 align:start position:0% classes in a default IP address scheme is<08:48:52.740> really<08:48:52.978> important<08:48:53.398> for<08:48:53.638> us<08:48:53.760> and<08:48:54.298> this<08:48:54.478> gets 08:48:54.770 --> 08:48:54.780 align:start position:0% is really important for us and this gets 08:48:54.780 --> 08:48:57.350 align:start position:0% is really important for us and this gets back<08:48:54.958> to<08:48:55.320> uh<08:48:56.280> right<08:48:56.520> here<08:48:56.700> so<08:48:56.878> let's<08:48:57.120> talk 08:48:57.350 --> 08:48:57.360 align:start position:0% back to uh right here so let's talk 08:48:57.360 --> 08:48:58.670 align:start position:0% back to uh right here so let's talk about<08:48:57.540> remember<08:48:57.780> we<08:48:58.080> talked<08:48:58.320> about<08:48:58.378> class 08:48:58.670 --> 08:48:58.680 align:start position:0% about remember we talked about class 08:48:58.680 --> 08:49:00.350 align:start position:0% about remember we talked about class lesson<08:48:59.218> class<08:48:59.398> full<08:48:59.700> we're<08:49:00.000> going<08:49:00.120> to<08:49:00.180> talk 08:49:00.350 --> 08:49:00.360 align:start position:0% lesson class full we're going to talk 08:49:00.360 --> 08:49:03.410 align:start position:0% lesson class full we're going to talk about<08:49:00.540> the<08:49:01.020> classes<08:49:01.558> that<08:49:01.860> exist<08:49:02.280> in<08:49:03.000> an<08:49:03.120> IP 08:49:03.410 --> 08:49:03.420 align:start position:0% about the classes that exist in an IP 08:49:03.420 --> 08:49:06.110 align:start position:0% about the classes that exist in an IP address<08:49:03.600> right<08:49:04.020> now<08:49:04.200> so<08:49:04.798> as<08:49:05.340> we<08:49:05.520> learned<08:49:05.820> in 08:49:06.110 --> 08:49:06.120 align:start position:0% address right now so as we learned in 08:49:06.120 --> 08:49:09.288 align:start position:0% address right now so as we learned in previous<08:49:06.298> modules<08:49:06.958> the<08:49:07.500> ipv4<08:49:08.458> addressing 08:49:09.288 --> 08:49:09.298 align:start position:0% previous modules the ipv4 addressing 08:49:09.298 --> 08:49:13.968 align:start position:0% previous modules the ipv4 addressing scheme<08:49:09.718> is<08:49:10.378> again<08:49:10.700> 32<08:49:11.700> bits<08:49:12.540> broken<08:49:13.138> up<08:49:13.440> into 08:49:13.968 --> 08:49:13.978 align:start position:0% scheme is again 32 bits broken up into 08:49:13.978 --> 08:49:17.868 align:start position:0% scheme is again 32 bits broken up into four<08:49:14.940> octets<08:49:15.660> and<08:49:16.620> each<08:49:16.798> octet<08:49:17.340> can<08:49:17.638> range 08:49:17.868 --> 08:49:17.878 align:start position:0% four octets and each octet can range 08:49:17.878 --> 08:49:20.330 align:start position:0% four octets and each octet can range from<08:49:18.120> 0<08:49:18.360> to<08:49:18.840> 255. 08:49:20.330 --> 08:49:20.340 align:start position:0% from 0 to 255. 08:49:20.340 --> 08:49:22.310 align:start position:0% from 0 to 255. now<08:49:20.820> the<08:49:21.120> international<08:49:21.320> standards 08:49:22.310 --> 08:49:22.320 align:start position:0% now the international standards 08:49:22.320 --> 08:49:25.368 align:start position:0% now the international standards organization<08:49:23.298> icann<08:49:24.298> which<08:49:24.840> we've<08:49:25.020> mentioned 08:49:25.368 --> 08:49:25.378 align:start position:0% organization icann which we've mentioned 08:49:25.378 --> 08:49:27.770 align:start position:0% organization icann which we've mentioned in<08:49:25.558> a<08:49:25.680> previous<08:49:25.798> module<08:49:26.520> is<08:49:27.120> in<08:49:27.298> control<08:49:27.478> of 08:49:27.770 --> 08:49:27.780 align:start position:0% in a previous module is in control of 08:49:27.780 --> 08:49:30.530 align:start position:0% in a previous module is in control of how<08:49:28.260> these<08:49:28.558> IP<08:49:28.920> addresses<08:49:29.458> are<08:49:30.058> leased<08:49:30.478> and 08:49:30.530 --> 08:49:30.540 align:start position:0% how these IP addresses are leased and 08:49:30.540 --> 08:49:32.570 align:start position:0% how these IP addresses are leased and distributed<08:49:31.020> out<08:49:31.260> to<08:49:31.620> individuals<08:49:32.340> and 08:49:32.570 --> 08:49:32.580 align:start position:0% distributed out to individuals and 08:49:32.580 --> 08:49:34.430 align:start position:0% distributed out to individuals and companies<08:49:32.878> around<08:49:33.120> the<08:49:33.360> world<08:49:33.478> now<08:49:34.200> because 08:49:34.430 --> 08:49:34.440 align:start position:0% companies around the world now because 08:49:34.440 --> 08:49:36.948 align:start position:0% companies around the world now because of<08:49:34.680> the<08:49:34.920> limited<08:49:35.340> amount<08:49:35.700> of<08:49:36.000> IP<08:49:36.360> addresses 08:49:36.948 --> 08:49:36.958 align:start position:0% of the limited amount of IP addresses 08:49:36.958 --> 08:49:41.030 align:start position:0% of the limited amount of IP addresses the<08:49:37.798> default<08:49:38.180> ipv4<08:49:39.180> addressing<08:49:39.898> scheme<08:49:40.378> is 08:49:41.030 --> 08:49:41.040 align:start position:0% the default ipv4 addressing scheme is 08:49:41.040 --> 08:49:42.948 align:start position:0% the default ipv4 addressing scheme is designed<08:49:41.458> and<08:49:41.580> outlined<08:49:42.120> which<08:49:42.478> what<08:49:42.780> are 08:49:42.948 --> 08:49:42.958 align:start position:0% designed and outlined which what are 08:49:42.958 --> 08:49:45.708 align:start position:0% designed and outlined which what are called<08:49:43.218> classes<08:49:44.218> and<08:49:45.000> there<08:49:45.180> are<08:49:45.360> five<08:49:45.540> of 08:49:45.708 --> 08:49:45.718 align:start position:0% called classes and there are five of 08:49:45.718 --> 08:49:47.570 align:start position:0% called classes and there are five of them<08:49:45.898> that<08:49:46.080> we<08:49:46.200> need<08:49:46.378> to<08:49:46.500> know<08:49:46.620> now<08:49:47.280> these 08:49:47.570 --> 08:49:47.580 align:start position:0% them that we need to know now these 08:49:47.580 --> 08:49:50.930 align:start position:0% them that we need to know now these classes<08:49:47.940> are<08:49:48.120> identified<08:49:48.600> as<08:49:48.898> a<08:49:49.440> b<08:49:49.680> c<08:49:50.340> d<08:49:50.520> and<08:49:50.760> e 08:49:50.930 --> 08:49:50.940 align:start position:0% classes are identified as a b c d and e 08:49:50.940 --> 08:49:54.110 align:start position:0% classes are identified as a b c d and e and<08:49:51.780> each<08:49:52.080> class<08:49:52.440> is<08:49:52.860> designed<08:49:53.218> to<08:49:53.398> facilitate 08:49:54.110 --> 08:49:54.120 align:start position:0% and each class is designed to facilitate 08:49:54.120 --> 08:49:57.110 align:start position:0% and each class is designed to facilitate in<08:49:54.660> the<08:49:54.780> distribution<08:49:55.260> of<08:49:55.740> IP<08:49:56.100> addresses<08:49:56.700> for 08:49:57.110 --> 08:49:57.120 align:start position:0% in the distribution of IP addresses for 08:49:57.120 --> 08:49:59.388 align:start position:0% in the distribution of IP addresses for certain<08:49:57.478> types<08:49:57.780> of<08:49:57.898> purposes<08:49:58.320> now<08:49:59.100> the<08:49:59.280> First 08:49:59.388 --> 08:49:59.398 align:start position:0% certain types of purposes now the First 08:49:59.398 --> 08:50:02.930 align:start position:0% certain types of purposes now the First Class<08:49:59.638> A<08:50:00.120> Class<08:50:00.298> A<08:50:00.718> allows<08:50:01.680> you<08:50:01.740> to<08:50:01.920> have<08:50:02.160> is 08:50:02.930 --> 08:50:02.940 align:start position:0% Class A Class A allows you to have is 08:50:02.940 --> 08:50:05.868 align:start position:0% Class A Class A allows you to have is designed<08:50:03.298> for<08:50:03.660> really<08:50:04.020> large<08:50:04.558> Networks 08:50:05.868 --> 08:50:05.878 align:start position:0% designed for really large Networks 08:50:05.878 --> 08:50:08.868 align:start position:0% designed for really large Networks meaning<08:50:06.660> that<08:50:07.138> it<08:50:07.500> does<08:50:07.740> not<08:50:07.920> have<08:50:08.280> a<08:50:08.638> lot<08:50:08.760> of 08:50:08.868 --> 08:50:08.878 align:start position:0% meaning that it does not have a lot of 08:50:08.878 --> 08:50:10.968 align:start position:0% meaning that it does not have a lot of networks<08:50:09.420> because<08:50:10.020> we<08:50:10.260> only<08:50:10.378> have<08:50:10.620> a<08:50:10.740> few<08:50:10.860> of 08:50:10.968 --> 08:50:10.978 align:start position:0% networks because we only have a few of 08:50:10.978 --> 08:50:13.910 align:start position:0% networks because we only have a few of them<08:50:11.100> and<08:50:11.280> that<08:50:11.458> is<08:50:11.580> because<08:50:11.820> a<08:50:12.780> Class<08:50:12.958> A<08:50:13.378> Range 08:50:13.910 --> 08:50:13.920 align:start position:0% them and that is because a Class A Range 08:50:13.920 --> 08:50:16.070 align:start position:0% them and that is because a Class A Range goes<08:50:14.580> from<08:50:14.700> one 08:50:16.070 --> 08:50:16.080 align:start position:0% goes from one 08:50:16.080 --> 08:50:18.468 align:start position:0% goes from one to<08:50:16.558> 127. 08:50:18.468 --> 08:50:18.478 align:start position:0% to 127. 08:50:18.478 --> 08:50:21.110 align:start position:0% to 127. in<08:50:19.138> the 08:50:21.110 --> 08:50:21.120 align:start position:0% in the 08:50:21.120 --> 08:50:22.730 align:start position:0% in the first 08:50:22.730 --> 08:50:22.740 align:start position:0% first 08:50:22.740 --> 08:50:26.990 align:start position:0% first octet<08:50:23.458> meaning<08:50:24.420> that<08:50:24.780> the<08:50:25.620> remaining<08:50:26.218> octets 08:50:26.990 --> 08:50:27.000 align:start position:0% octet meaning that the remaining octets 08:50:27.000 --> 08:50:29.690 align:start position:0% octet meaning that the remaining octets are<08:50:27.478> reserved<08:50:27.898> for<08:50:28.020> nodes<08:50:28.320> and<08:50:29.040> so<08:50:29.218> we<08:50:29.458> see 08:50:29.690 --> 08:50:29.700 align:start position:0% are reserved for nodes and so we see 08:50:29.700 --> 08:50:32.448 align:start position:0% are reserved for nodes and so we see that<08:50:30.180> we<08:50:30.360> don't<08:50:30.540> have<08:50:30.898> a<08:50:31.440> lot<08:50:31.558> of<08:50:31.860> networks<08:50:32.280> we 08:50:32.448 --> 08:50:32.458 align:start position:0% that we don't have a lot of networks we 08:50:32.458 --> 08:50:37.250 align:start position:0% that we don't have a lot of networks we only<08:50:32.580> have<08:50:32.840> 126<08:50:33.840> networks<08:50:34.440> one<08:50:35.398> to<08:50:35.580> 127. 08:50:37.250 --> 08:50:37.260 align:start position:0% only have 126 networks one to 127. 08:50:37.260 --> 08:50:42.010 align:start position:0% only have 126 networks one to 127. but<08:50:38.160> we<08:50:38.580> do<08:50:38.878> have<08:50:39.240> up<08:50:39.660> to<08:50:39.840> 16 08:50:42.010 --> 08:50:42.020 align:start position:0% but we do have up to 16 08:50:42.020 --> 08:50:47.090 align:start position:0% but we do have up to 16 .7<08:50:43.020> or<08:50:43.620> 0.8<08:50:44.160> around<08:50:44.580> about<08:50:44.878> million<08:50:45.840> net<08:50:46.558> I 08:50:47.090 --> 08:50:47.100 align:start position:0% .7 or 0.8 around about million net I 08:50:47.100 --> 08:50:49.788 align:start position:0% .7 or 0.8 around about million net I nodes<08:50:47.520> that<08:50:47.878> can<08:50:48.000> be<08:50:48.240> on 08:50:49.788 --> 08:50:49.798 align:start position:0% nodes that can be on 08:50:49.798 --> 08:50:52.850 align:start position:0% nodes that can be on this<08:50:50.340> network<08:50:50.520> and<08:50:51.420> so<08:50:51.660> uh<08:50:52.020> we<08:50:52.260> have<08:50:52.440> so<08:50:52.680> many 08:50:52.850 --> 08:50:52.860 align:start position:0% this network and so uh we have so many 08:50:52.860 --> 08:50:56.388 align:start position:0% this network and so uh we have so many nodes<08:50:53.218> for<08:50:53.638> so<08:50:53.940> few<08:50:54.260> uh<08:50:55.260> networks<08:50:55.860> and<08:50:56.100> so<08:50:56.280> this 08:50:56.388 --> 08:50:56.398 align:start position:0% nodes for so few uh networks and so this 08:50:56.398 --> 08:50:59.270 align:start position:0% nodes for so few uh networks and so this is<08:50:56.580> really<08:50:56.760> for<08:50:57.120> very<08:50:57.420> large<08:50:58.080> large<08:50:58.558> networks 08:50:59.270 --> 08:50:59.280 align:start position:0% is really for very large large networks 08:50:59.280 --> 08:51:01.968 align:start position:0% is really for very large large networks and<08:50:59.940> there<08:51:00.180> are<08:51:00.360> some<08:51:00.600> specifically<08:51:01.200> reserved 08:51:01.968 --> 08:51:01.978 align:start position:0% and there are some specifically reserved 08:51:01.978 --> 08:51:03.830 align:start position:0% and there are some specifically reserved addresses<08:51:02.638> in<08:51:02.940> this<08:51:03.058> as<08:51:03.240> well<08:51:03.360> we'll<08:51:03.600> talk 08:51:03.830 --> 08:51:03.840 align:start position:0% addresses in this as well we'll talk 08:51:03.840 --> 08:51:05.750 align:start position:0% addresses in this as well we'll talk about<08:51:03.958> those<08:51:04.200> in<08:51:04.440> just<08:51:04.558> a<08:51:04.680> minute<08:51:04.798> now<08:51:05.580> with 08:51:05.750 --> 08:51:05.760 align:start position:0% about those in just a minute now with 08:51:05.760 --> 08:51:08.410 align:start position:0% about those in just a minute now with class<08:51:06.000> B<08:51:06.298> here<08:51:07.138> we<08:51:07.378> have 08:51:08.410 --> 08:51:08.420 align:start position:0% class B here we have 08:51:08.420 --> 08:51:11.930 align:start position:0% class B here we have 128<08:51:09.420> to<08:51:10.080> 191. 08:51:11.930 --> 08:51:11.940 align:start position:0% 128 to 191. 08:51:11.940 --> 08:51:14.150 align:start position:0% 128 to 191. and<08:51:12.540> these<08:51:12.840> are<08:51:12.958> called<08:51:13.138> Class<08:51:13.320> B<08:51:13.558> they<08:51:13.860> allow 08:51:14.150 --> 08:51:14.160 align:start position:0% and these are called Class B they allow 08:51:14.160 --> 08:51:17.270 align:start position:0% and these are called Class B they allow for<08:51:14.520> a<08:51:14.940> lot<08:51:15.058> more<08:51:15.240> Networks 08:51:17.270 --> 08:51:17.280 align:start position:0% for a lot more Networks 08:51:17.280 --> 08:51:21.770 align:start position:0% for a lot more Networks and<08:51:17.760> fewer<08:51:18.180> nodes<08:51:18.420> which<08:51:18.718> makes<08:51:18.958> sense 08:51:21.770 --> 08:51:21.780 align:start position:0% 08:51:21.780 --> 08:51:25.850 align:start position:0% Now<08:51:22.440> the<08:51:22.920> default<08:51:23.398> subnet<08:51:24.180> mask<08:51:24.540> for<08:51:25.260> class<08:51:25.558> A 08:51:25.850 --> 08:51:25.860 align:start position:0% Now the default subnet mask for class A 08:51:25.860 --> 08:51:30.730 align:start position:0% Now the default subnet mask for class A which<08:51:26.218> might<08:51:26.398> make<08:51:26.580> this<08:51:26.760> a<08:51:26.940> little<08:51:27.058> clearer 08:51:30.730 --> 08:51:30.740 align:start position:0% 08:51:30.740 --> 08:51:36.788 align:start position:0% 255.0.0.0<08:51:31.760> whereas<08:51:32.760> for<08:51:33.360> a<08:51:33.540> class<08:51:33.660> B<08:51:34.020> it's 08:51:36.788 --> 08:51:36.798 align:start position:0% 255.0.0.0 whereas for a class B it's 08:51:36.798 --> 08:51:39.650 align:start position:0% 255.0.0.0 whereas for a class B it's 255.255.0.0<08:51:37.798> now<08:51:38.580> as<08:51:38.760> you<08:51:38.878> can<08:51:39.000> tell<08:51:39.120> the 08:51:39.650 --> 08:51:39.660 align:start position:0% 255.255.0.0 now as you can tell the 08:51:39.660 --> 08:51:41.330 align:start position:0% 255.255.0.0 now as you can tell the class<08:51:39.780> is<08:51:40.020> actually<08:51:40.260> determined<08:51:40.740> by<08:51:40.920> the<08:51:41.160> very 08:51:41.330 --> 08:51:41.340 align:start position:0% class is actually determined by the very 08:51:41.340 --> 08:51:43.250 align:start position:0% class is actually determined by the very first<08:51:41.638> octet<08:51:42.420> the<08:51:42.660> number<08:51:42.780> in<08:51:43.020> the<08:51:43.138> first 08:51:43.250 --> 08:51:43.260 align:start position:0% first octet the number in the first 08:51:43.260 --> 08:51:44.448 align:start position:0% first octet the number in the first octet 08:51:44.448 --> 08:51:44.458 align:start position:0% octet 08:51:44.458 --> 08:51:46.368 align:start position:0% octet and<08:51:45.000> it's<08:51:45.120> important<08:51:45.420> to<08:51:45.660> then<08:51:45.840> therefore 08:51:46.368 --> 08:51:46.378 align:start position:0% and it's important to then therefore 08:51:46.378 --> 08:51:48.708 align:start position:0% and it's important to then therefore memorize<08:51:47.040> these<08:51:47.878> numbers<08:51:48.058> because<08:51:48.420> you'll 08:51:48.708 --> 08:51:48.718 align:start position:0% memorize these numbers because you'll 08:51:48.718 --> 08:51:50.930 align:start position:0% memorize these numbers because you'll see<08:51:48.898> on<08:51:49.138> your<08:51:49.318> exam<08:51:49.680> they'll<08:51:50.280> ask<08:51:50.458> you<08:51:50.580> which 08:51:50.930 --> 08:51:50.940 align:start position:0% see on your exam they'll ask you which 08:51:50.940 --> 08:51:53.570 align:start position:0% see on your exam they'll ask you which class<08:51:51.420> is<08:51:52.138> this<08:51:52.260> IP<08:51:52.558> address<08:51:52.680> a<08:51:52.978> part<08:51:53.160> of<08:51:53.280> if 08:51:53.570 --> 08:51:53.580 align:start position:0% class is this IP address a part of if 08:51:53.580 --> 08:51:55.670 align:start position:0% class is this IP address a part of if it's<08:51:53.760> between<08:51:53.940> 1<08:51:54.240> and<08:51:54.420> 127<08:51:55.020> you<08:51:55.318> know<08:51:55.378> it's<08:51:55.558> a 08:51:55.670 --> 08:51:55.680 align:start position:0% it's between 1 and 127 you know it's a 08:51:55.680 --> 08:51:59.030 align:start position:0% it's between 1 and 127 you know it's a Class<08:51:55.798> A<08:51:56.040> if<08:51:56.700> it's<08:51:56.878> between<08:51:57.200> 128<08:51:58.200> and<08:51:58.378> 191<08:51:58.798> you 08:51:59.030 --> 08:51:59.040 align:start position:0% Class A if it's between 128 and 191 you 08:51:59.040 --> 08:52:01.128 align:start position:0% Class A if it's between 128 and 191 you know<08:51:59.160> it's<08:51:59.280> a<08:51:59.398> Class<08:51:59.520> B<08:51:59.760> if<08:52:00.360> we<08:52:00.478> get<08:52:00.600> to<08:52:00.780> a<08:52:00.958> class 08:52:01.128 --> 08:52:01.138 align:start position:0% know it's a Class B if we get to a class 08:52:01.138 --> 08:52:04.548 align:start position:0% know it's a Class B if we get to a class C<08:52:01.500> now<08:52:01.860> we<08:52:02.280> have<08:52:02.458> a<08:52:02.878> lot<08:52:03.000> of<08:52:03.120> networks<08:52:03.718> and<08:52:04.378> not 08:52:04.548 --> 08:52:04.558 align:start position:0% C now we have a lot of networks and not 08:52:04.558 --> 08:52:06.948 align:start position:0% C now we have a lot of networks and not a<08:52:04.740> lot<08:52:04.860> of<08:52:05.040> nodes<08:52:05.760> and<08:52:06.360> you<08:52:06.478> can<08:52:06.600> see<08:52:06.718> that 08:52:06.948 --> 08:52:06.958 align:start position:0% a lot of nodes and you can see that 08:52:06.958 --> 08:52:12.128 align:start position:0% a lot of nodes and you can see that these<08:52:07.318> are<08:52:07.440> 192<08:52:08.340> to<08:52:09.080> 223<08:52:10.080> in<08:52:10.378> the<08:52:10.620> first 08:52:12.128 --> 08:52:12.138 align:start position:0% these are 192 to 223 in the first 08:52:12.138 --> 08:52:15.830 align:start position:0% these are 192 to 223 in the first octet<08:52:13.138> and<08:52:13.860> the<08:52:13.978> default<08:52:14.340> subnet<08:52:14.818> mask 08:52:15.830 --> 08:52:15.840 align:start position:0% octet and the default subnet mask 08:52:15.840 --> 08:52:19.570 align:start position:0% octet and the default subnet mask for<08:52:16.378> this<08:52:16.680> is<08:52:16.978> going<08:52:17.160> to<08:52:17.280> be<08:52:17.398> 255<08:52:18.000> to 08:52:19.570 --> 08:52:19.580 align:start position:0% for this is going to be 255 to 08:52:19.580 --> 08:52:22.490 align:start position:0% for this is going to be 255 to 255.255.0<08:52:20.580> and<08:52:20.878> if<08:52:21.000> you<08:52:21.120> remember<08:52:21.240> that<08:52:22.200> gives 08:52:22.490 --> 08:52:22.500 align:start position:0% 255.255.0 and if you remember that gives 08:52:22.500 --> 08:52:25.308 align:start position:0% 255.255.0 and if you remember that gives us<08:52:22.680> only<08:52:23.100> this<08:52:23.398> octet<08:52:23.878> for<08:52:24.120> nodes<08:52:24.420> and<08:52:24.898> all<08:52:25.138> of 08:52:25.308 --> 08:52:25.318 align:start position:0% us only this octet for nodes and all of 08:52:25.318 --> 08:52:28.430 align:start position:0% us only this octet for nodes and all of these<08:52:25.558> octets<08:52:26.040> for<08:52:26.700> networks<08:52:27.298> this<08:52:28.260> is 08:52:28.430 --> 08:52:28.440 align:start position:0% these octets for networks this is 08:52:28.440 --> 08:52:30.350 align:start position:0% these octets for networks this is usually<08:52:28.680> one<08:52:29.040> of<08:52:29.160> the<08:52:29.218> most<08:52:29.458> recognizable<08:52:30.180> for 08:52:30.350 --> 08:52:30.360 align:start position:0% usually one of the most recognizable for 08:52:30.360 --> 08:52:35.048 align:start position:0% usually one of the most recognizable for home<08:52:30.600> networks<08:52:31.138> because<08:52:31.798> we<08:52:32.218> have<08:52:32.340> the 08:52:35.048 --> 08:52:35.058 align:start position:0% 08:52:35.058 --> 08:52:38.090 align:start position:0% 192.168.0.1<08:52:36.058> for<08:52:36.420> instance<08:52:36.718> that<08:52:37.440> is<08:52:37.920> going 08:52:38.090 --> 08:52:38.100 align:start position:0% 192.168.0.1 for instance that is going 08:52:38.100 --> 08:52:40.730 align:start position:0% 192.168.0.1 for instance that is going to<08:52:38.280> obviously<08:52:38.700> fall<08:52:38.940> into<08:52:39.180> this<08:52:39.540> class<08:52:39.718> C<08:52:40.020> now 08:52:40.730 --> 08:52:40.740 align:start position:0% to obviously fall into this class C now 08:52:40.740 --> 08:52:42.110 align:start position:0% to obviously fall into this class C now there<08:52:40.920> are<08:52:41.040> two<08:52:41.160> other<08:52:41.340> classes<08:52:41.760> they're<08:52:41.940> not 08:52:42.110 --> 08:52:42.120 align:start position:0% there are two other classes they're not 08:52:42.120 --> 08:52:43.548 align:start position:0% there are two other classes they're not very<08:52:42.360> common<08:52:42.540> but<08:52:42.840> they're<08:52:43.020> important<08:52:43.318> to<08:52:43.440> be 08:52:43.548 --> 08:52:43.558 align:start position:0% very common but they're important to be 08:52:43.558 --> 08:52:47.330 align:start position:0% very common but they're important to be able<08:52:43.620> to<08:52:43.740> recognize<08:52:44.218> they're<08:52:45.058> a<08:52:45.298> Class<08:52:45.540> D<08:52:46.318> i<08:52:47.160> p 08:52:47.330 --> 08:52:47.340 align:start position:0% able to recognize they're a Class D i p 08:52:47.340 --> 08:52:49.010 align:start position:0% able to recognize they're a Class D i p addresses<08:52:47.818> which<08:52:48.120> are<08:52:48.298> only<08:52:48.420> used<08:52:48.660> for<08:52:48.840> what 08:52:49.010 --> 08:52:49.020 align:start position:0% addresses which are only used for what 08:52:49.020 --> 08:52:53.208 align:start position:0% addresses which are only used for what we<08:52:49.138> call<08:52:49.638> multicast<08:52:50.638> Transmissions 08:52:53.208 --> 08:52:53.218 align:start position:0% we call multicast Transmissions 08:52:53.218 --> 08:52:55.670 align:start position:0% we call multicast Transmissions and<08:52:53.760> these<08:52:54.000> are<08:52:54.120> for<08:52:54.298> special<08:52:54.660> routers<08:52:55.500> that 08:52:55.670 --> 08:52:55.680 align:start position:0% and these are for special routers that 08:52:55.680 --> 08:52:57.650 align:start position:0% and these are for special routers that are<08:52:55.860> able<08:52:56.040> to<08:52:56.160> support<08:52:56.398> the<08:52:56.818> use<08:52:56.940> of<08:52:57.240> IP 08:52:57.650 --> 08:52:57.660 align:start position:0% are able to support the use of IP 08:52:57.660 --> 08:52:59.510 align:start position:0% are able to support the use of IP addresses<08:52:58.080> within<08:52:58.440> this<08:52:58.620> range<08:52:58.920> you<08:52:59.398> don't 08:52:59.510 --> 08:52:59.520 align:start position:0% addresses within this range you don't 08:52:59.520 --> 08:53:00.948 align:start position:0% addresses within this range you don't really<08:52:59.700> need<08:52:59.878> to<08:52:59.940> worry<08:53:00.120> about<08:53:00.298> this<08:53:00.540> for<08:53:00.718> much 08:53:00.948 --> 08:53:00.958 align:start position:0% really need to worry about this for much 08:53:00.958 --> 08:53:03.048 align:start position:0% really need to worry about this for much application<08:53:01.440> unless<08:53:01.798> you're<08:53:01.920> dealing<08:53:02.218> with<08:53:02.398> a 08:53:03.048 --> 08:53:03.058 align:start position:0% application unless you're dealing with a 08:53:03.058 --> 08:53:05.448 align:start position:0% application unless you're dealing with a lot<08:53:03.298> more<08:53:03.478> advanced<08:53:04.080> stuff<08:53:04.440> and<08:53:05.040> these<08:53:05.280> deal 08:53:05.448 --> 08:53:05.458 align:start position:0% lot more advanced stuff and these deal 08:53:05.458 --> 08:53:08.330 align:start position:0% lot more advanced stuff and these deal with<08:53:05.638> 224<08:53:06.298> to<08:53:06.898> 239 08:53:08.330 --> 08:53:08.340 align:start position:0% with 224 to 239 08:53:08.340 --> 08:53:10.850 align:start position:0% with 224 to 239 finally<08:53:09.000> we<08:53:09.420> have<08:53:09.540> class<08:53:09.780> E<08:53:10.138> which<08:53:10.440> is<08:53:10.558> from 08:53:10.850 --> 08:53:10.860 align:start position:0% finally we have class E which is from 08:53:10.860 --> 08:53:15.850 align:start position:0% finally we have class E which is from 240<08:53:11.700> to<08:53:12.180> 255<08:53:13.020> and<08:53:13.978> these<08:53:14.520> are<08:53:14.638> really<08:53:14.878> for 08:53:15.850 --> 08:53:15.860 align:start position:0% 240 to 255 and these are really for 08:53:15.860 --> 08:53:18.708 align:start position:0% 240 to 255 and these are really for experimental<08:53:16.860> reasons<08:53:17.398> so<08:53:18.240> we're<08:53:18.360> really<08:53:18.540> not 08:53:18.708 --> 08:53:18.718 align:start position:0% experimental reasons so we're really not 08:53:18.718 --> 08:53:21.530 align:start position:0% experimental reasons so we're really not going<08:53:18.898> to<08:53:19.020> see<08:53:19.260> these<08:53:19.740> in<08:53:20.340> much<08:53:20.458> play<08:53:20.818> the<08:53:21.360> ones 08:53:21.530 --> 08:53:21.540 align:start position:0% going to see these in much play the ones 08:53:21.540 --> 08:53:24.048 align:start position:0% going to see these in much play the ones you<08:53:21.718> really<08:53:21.840> want<08:53:22.080> to<08:53:22.200> be<08:53:22.260> familiar<08:53:22.680> with 08:53:24.048 --> 08:53:24.058 align:start position:0% you really want to be familiar with 08:53:24.058 --> 08:53:27.708 align:start position:0% you really want to be familiar with are<08:53:24.600> these<08:53:24.898> first<08:53:25.080> three<08:53:25.500> classes<08:53:25.978> a<08:53:26.760> b<08:53:27.058> and<08:53:27.360> c 08:53:27.708 --> 08:53:27.718 align:start position:0% are these first three classes a b and c 08:53:27.718 --> 08:53:34.010 align:start position:0% are these first three classes a b and c remember<08:53:28.580> 1<08:53:29.580> to<08:53:29.818> 127<08:53:30.540> is<08:53:31.318> a<08:53:31.558> class<08:53:31.680> A<08:53:32.360> 128<08:53:33.360> to 08:53:34.010 --> 08:53:34.020 align:start position:0% remember 1 to 127 is a class A 128 to 08:53:34.020 --> 08:53:40.730 align:start position:0% remember 1 to 127 is a class A 128 to 191<08:53:34.798> is<08:53:35.760> a<08:53:36.000> Class<08:53:36.180> B<08:53:37.100> 192<08:53:38.100> to<08:53:38.580> 223<08:53:39.360> is<08:53:39.718> a<08:53:39.958> Class<08:53:40.200> C 08:53:40.730 --> 08:53:40.740 align:start position:0% 191 is a Class B 192 to 223 is a Class C 08:53:40.740 --> 08:53:42.650 align:start position:0% 191 is a Class B 192 to 223 is a Class C if<08:53:41.218> you<08:53:41.340> can<08:53:41.458> remember<08:53:41.580> those<08:53:41.878> ranges<08:53:42.360> I<08:53:42.540> would 08:53:42.650 --> 08:53:42.660 align:start position:0% if you can remember those ranges I would 08:53:42.660 --> 08:53:44.150 align:start position:0% if you can remember those ranges I would commit<08:53:42.898> them<08:53:43.020> to<08:53:43.200> Memory<08:53:43.440> you'll<08:53:43.740> be<08:53:43.860> good<08:53:44.040> to 08:53:44.150 --> 08:53:44.160 align:start position:0% commit them to Memory you'll be good to 08:53:44.160 --> 08:53:46.308 align:start position:0% commit them to Memory you'll be good to go<08:53:44.280> for<08:53:44.458> the<08:53:44.580> exam<08:53:44.878> now<08:53:45.420> within<08:53:45.780> each<08:53:45.958> of<08:53:46.138> these 08:53:46.308 --> 08:53:46.318 align:start position:0% go for the exam now within each of these 08:53:46.318 --> 08:53:49.308 align:start position:0% go for the exam now within each of these classes<08:53:46.878> there<08:53:47.878> are<08:53:48.058> a<08:53:48.298> number<08:53:48.478> of<08:53:48.600> addresses 08:53:49.308 --> 08:53:49.318 align:start position:0% classes there are a number of addresses 08:53:49.318 --> 08:53:51.770 align:start position:0% classes there are a number of addresses that<08:53:49.680> are<08:53:50.040> not<08:53:50.340> allowed<08:53:50.700> to<08:53:50.818> be<08:53:51.000> assigned<08:53:51.540> or 08:53:51.770 --> 08:53:51.780 align:start position:0% that are not allowed to be assigned or 08:53:51.780 --> 08:53:53.750 align:start position:0% that are not allowed to be assigned or leased<08:53:52.200> for<08:53:52.620> specific<08:53:52.920> reasons<08:53:53.398> these<08:53:53.700> are 08:53:53.750 --> 08:53:53.760 align:start position:0% leased for specific reasons these are 08:53:53.760 --> 08:53:55.730 align:start position:0% leased for specific reasons these are what<08:53:53.878> we<08:53:53.940> call<08:53:54.120> reserved<08:53:54.780> and<08:53:54.958> restricted<08:53:55.440> IP 08:53:55.730 --> 08:53:55.740 align:start position:0% what we call reserved and restricted IP 08:53:55.740 --> 08:53:58.388 align:start position:0% what we call reserved and restricted IP addresses<08:53:56.218> now<08:53:56.700> we've<08:53:56.940> mentioned<08:53:57.240> the 08:53:58.388 --> 08:53:58.398 align:start position:0% addresses now we've mentioned the 08:53:58.398 --> 08:54:01.850 align:start position:0% addresses now we've mentioned the 127.0.0.1<08:53:59.398> or<08:53:59.940> the<08:54:00.180> local<08:54:00.360> loopback<08:54:01.020> or<08:54:01.558> the 08:54:01.850 --> 08:54:01.860 align:start position:0% 127.0.0.1 or the local loopback or the 08:54:01.860 --> 08:54:04.610 align:start position:0% 127.0.0.1 or the local loopback or the localhost<08:54:02.398> i<08:54:02.878> p<08:54:03.000> address<08:54:03.240> before<08:54:03.660> which<08:54:04.440> can't 08:54:04.610 --> 08:54:04.620 align:start position:0% localhost i p address before which can't 08:54:04.620 --> 08:54:07.070 align:start position:0% localhost i p address before which can't be<08:54:04.860> assigned<08:54:05.398> because<08:54:05.760> it's<08:54:06.420> reserved<08:54:06.840> for<08:54:06.958> me 08:54:07.070 --> 08:54:07.080 align:start position:0% be assigned because it's reserved for me 08:54:07.080 --> 08:54:09.650 align:start position:0% be assigned because it's reserved for me for<08:54:07.378> myself<08:54:07.558> from<08:54:07.978> for<08:54:08.458> I<08:54:08.700> this<08:54:09.298> means<08:54:09.540> that 08:54:09.650 --> 08:54:09.660 align:start position:0% for myself from for I this means that 08:54:09.660 --> 08:54:11.930 align:start position:0% for myself from for I this means that this<08:54:09.840> address<08:54:10.020> is<08:54:10.318> used<08:54:10.620> when<08:54:11.040> I<08:54:11.398> want<08:54:11.638> to 08:54:11.930 --> 08:54:11.940 align:start position:0% this address is used when I want to 08:54:11.940 --> 08:54:13.730 align:start position:0% this address is used when I want to address<08:54:12.298> myself 08:54:13.730 --> 08:54:13.740 align:start position:0% address myself 08:54:13.740 --> 08:54:16.490 align:start position:0% address myself so<08:54:14.340> if<08:54:14.638> I<08:54:14.878> wanted<08:54:15.000> to<08:54:15.360> for<08:54:15.660> instance<08:54:15.898> assign 08:54:16.490 --> 08:54:16.500 align:start position:0% so if I wanted to for instance assign 08:54:16.500 --> 08:54:20.448 align:start position:0% so if I wanted to for instance assign myself<08:54:16.860> my<08:54:17.458> own<08:54:17.700> name<08:54:18.058> via<08:54:18.718> DNS<08:54:19.260> and<08:54:20.040> my<08:54:20.280> name 08:54:20.448 --> 08:54:20.458 align:start position:0% myself my own name via DNS and my name 08:54:20.458 --> 08:54:22.010 align:start position:0% myself my own name via DNS and my name was<08:54:20.700> me 08:54:22.010 --> 08:54:22.020 align:start position:0% was me 08:54:22.020 --> 08:54:25.510 align:start position:0% was me me<08:54:22.740> would<08:54:23.218> link<08:54:23.520> up<08:54:23.700> to<08:54:23.878> the<08:54:24.000> IP<08:54:24.298> address 08:54:25.510 --> 08:54:25.520 align:start position:0% me would link up to the IP address 08:54:25.520 --> 08:54:28.010 align:start position:0% me would link up to the IP address 127.0.0.1<08:54:26.520> and<08:54:27.058> that<08:54:27.240> way<08:54:27.420> it's<08:54:27.540> going<08:54:27.780> back 08:54:28.010 --> 08:54:28.020 align:start position:0% 127.0.0.1 and that way it's going back 08:54:28.020 --> 08:54:29.510 align:start position:0% 127.0.0.1 and that way it's going back to<08:54:28.200> myself<08:54:28.378> now<08:54:28.740> we're<08:54:28.920> really<08:54:29.040> going<08:54:29.218> to<08:54:29.340> use 08:54:29.510 --> 08:54:29.520 align:start position:0% to myself now we're really going to use 08:54:29.520 --> 08:54:32.808 align:start position:0% to myself now we're really going to use this<08:54:29.818> for<08:54:30.420> mostly<08:54:30.840> diagnostic<08:54:31.798> purposes<08:54:32.280> if<08:54:32.580> I 08:54:32.808 --> 08:54:32.818 align:start position:0% this for mostly diagnostic purposes if I 08:54:32.818 --> 08:54:34.308 align:start position:0% this for mostly diagnostic purposes if I want<08:54:32.940> to<08:54:33.058> double<08:54:33.240> check<08:54:33.478> to<08:54:33.780> make<08:54:33.898> sure<08:54:34.080> for 08:54:34.308 --> 08:54:34.318 align:start position:0% want to double check to make sure for 08:54:34.318 --> 08:54:37.090 align:start position:0% want to double check to make sure for instance<08:54:34.558> that<08:54:34.798> tcpip<08:54:35.580> is<08:54:35.940> running<08:54:36.120> correctly 08:54:37.090 --> 08:54:37.100 align:start position:0% instance that tcpip is running correctly 08:54:37.100 --> 08:54:39.048 align:start position:0% instance that tcpip is running correctly and<08:54:38.100> it's<08:54:38.340> also<08:54:38.580> going<08:54:38.700> to<08:54:38.760> be<08:54:38.818> used<08:54:38.878> for 08:54:39.048 --> 08:54:39.058 align:start position:0% and it's also going to be used for 08:54:39.058 --> 08:54:41.808 align:start position:0% and it's also going to be used for programmers<08:54:39.718> and<08:54:39.898> such<08:54:40.080> like<08:54:40.318> that<08:54:40.520> now<08:54:41.520> the 08:54:41.808 --> 08:54:41.818 align:start position:0% programmers and such like that now the 08:54:41.818 --> 08:54:44.468 align:start position:0% programmers and such like that now the address 08:54:44.468 --> 08:54:44.478 align:start position:0% 08:54:44.478 --> 08:54:47.570 align:start position:0% 10.0.0.0<08:54:45.478> is<08:54:46.260> also<08:54:46.558> restricted<08:54:46.978> and<08:54:47.218> it's<08:54:47.340> not 08:54:47.570 --> 08:54:47.580 align:start position:0% 10.0.0.0 is also restricted and it's not 08:54:47.580 --> 08:54:50.208 align:start position:0% 10.0.0.0 is also restricted and it's not available<08:54:47.818> to<08:54:48.180> use<08:54:48.360> because<08:54:48.660> again<08:54:49.080> this<08:54:49.978> a 08:54:50.208 --> 08:54:50.218 align:start position:0% available to use because again this a 08:54:50.218 --> 08:54:54.410 align:start position:0% available to use because again this a host<08:54:50.520> address<08:54:50.940> can<08:54:51.840> never<08:54:52.080> have<08:54:52.500> all<08:54:53.100> zeros 08:54:54.410 --> 08:54:54.420 align:start position:0% host address can never have all zeros 08:54:54.420 --> 08:54:57.288 align:start position:0% host address can never have all zeros conversely<08:54:55.378> the<08:54:55.978> addresses<08:54:56.458> that<08:54:56.700> have<08:54:56.940> all 08:54:57.288 --> 08:54:57.298 align:start position:0% conversely the addresses that have all 08:54:57.298 --> 08:55:03.910 align:start position:0% conversely the addresses that have all ones<08:54:57.780> for<08:54:58.500> instance 08:55:03.910 --> 08:55:03.920 align:start position:0% 08:55:03.920 --> 08:55:08.510 align:start position:0% 255.255.255.255<08:55:05.120> cannot<08:55:06.120> be<08:55:06.600> used<08:55:06.840> for 08:55:08.510 --> 08:55:08.520 align:start position:0% 255.255.255.255 cannot be used for 08:55:08.520 --> 08:55:11.808 align:start position:0% 255.255.255.255 cannot be used for um<08:55:08.580> uh<08:55:09.540> addresses<08:55:10.318> obviously<08:55:11.280> this<08:55:11.458> one<08:55:11.580> can't 08:55:11.808 --> 08:55:11.818 align:start position:0% um uh addresses obviously this one can't 08:55:11.818 --> 08:55:13.448 align:start position:0% um uh addresses obviously this one can't because<08:55:12.058> it<08:55:12.240> would<08:55:12.420> sort<08:55:12.660> of 08:55:13.448 --> 08:55:13.458 align:start position:0% because it would sort of 08:55:13.458 --> 08:55:16.070 align:start position:0% because it would sort of ruin<08:55:14.458> the<08:55:14.700> use<08:55:14.818> of<08:55:15.000> a<08:55:15.180> subnet<08:55:15.540> mask<08:55:15.718> but<08:55:15.958> even 08:55:16.070 --> 08:55:16.080 align:start position:0% ruin the use of a subnet mask but even 08:55:16.080 --> 08:55:19.330 align:start position:0% ruin the use of a subnet mask but even if<08:55:16.260> I<08:55:16.378> had<08:55:16.500> something<08:55:16.680> like 08:55:19.330 --> 08:55:19.340 align:start position:0% 08:55:19.340 --> 08:55:21.650 align:start position:0% 192.168.0.255<08:55:20.340> I<08:55:20.878> can't<08:55:21.000> use<08:55:21.240> that<08:55:21.420> because 08:55:21.650 --> 08:55:21.660 align:start position:0% 192.168.0.255 I can't use that because 08:55:21.660 --> 08:55:24.410 align:start position:0% 192.168.0.255 I can't use that because that's<08:55:21.958> what's<08:55:22.260> called<08:55:22.620> a<08:55:23.280> broadcast<08:55:23.580> address 08:55:24.410 --> 08:55:24.420 align:start position:0% that's what's called a broadcast address 08:55:24.420 --> 08:55:27.230 align:start position:0% that's what's called a broadcast address and<08:55:24.898> so<08:55:25.080> it's<08:55:25.260> just<08:55:25.440> simply<08:55:25.740> reserved<08:55:26.520> for 08:55:27.230 --> 08:55:27.240 align:start position:0% and so it's just simply reserved for 08:55:27.240 --> 08:55:29.448 align:start position:0% and so it's just simply reserved for that<08:55:27.420> this<08:55:27.780> means<08:55:28.080> that<08:55:28.318> if<08:55:28.558> a<08:55:28.920> message<08:55:29.100> is 08:55:29.448 --> 08:55:29.458 align:start position:0% that this means that if a message is 08:55:29.458 --> 08:55:31.610 align:start position:0% that this means that if a message is transmitted<08:55:30.298> to<08:55:30.540> a<08:55:30.718> network<08:55:30.840> address<08:55:31.138> with 08:55:31.610 --> 08:55:31.620 align:start position:0% transmitted to a network address with 08:55:31.620 --> 08:55:34.730 align:start position:0% transmitted to a network address with all<08:55:31.798> ones<08:55:32.040> in<08:55:32.160> the<08:55:32.280> host<08:55:32.458> portion<08:55:32.878> or<08:55:33.120> 255<08:55:34.020> that 08:55:34.730 --> 08:55:34.740 align:start position:0% all ones in the host portion or 255 that 08:55:34.740 --> 08:55:36.410 align:start position:0% all ones in the host portion or 255 that message<08:55:34.920> is<08:55:35.160> going<08:55:35.398> to<08:55:35.458> be<08:55:35.580> transmitted<08:55:36.120> to 08:55:36.410 --> 08:55:36.420 align:start position:0% message is going to be transmitted to 08:55:36.420 --> 08:55:38.930 align:start position:0% message is going to be transmitted to every<08:55:36.898> single<08:55:37.440> device<08:55:37.920> on<08:55:38.218> the<08:55:38.340> subnet<08:55:38.700> it's 08:55:38.930 --> 08:55:38.940 align:start position:0% every single device on the subnet it's 08:55:38.940 --> 08:55:40.850 align:start position:0% every single device on the subnet it's called<08:55:39.180> a<08:55:39.478> broadcast<08:55:39.958> and<08:55:40.440> we<08:55:40.620> talked<08:55:40.798> about 08:55:40.850 --> 08:55:40.860 align:start position:0% called a broadcast and we talked about 08:55:40.860 --> 08:55:44.410 align:start position:0% called a broadcast and we talked about broadcast<08:55:41.160> before<08:55:41.700> finally<08:55:42.660> the<08:55:42.840> address 08:55:44.410 --> 08:55:44.420 align:start position:0% broadcast before finally the address 08:55:44.420 --> 08:55:47.990 align:start position:0% broadcast before finally the address 1.1.1.1<08:55:45.420> cannot<08:55:46.138> be<08:55:46.378> used<08:55:46.620> because<08:55:47.458> this<08:55:47.878> is 08:55:47.990 --> 08:55:48.000 align:start position:0% 1.1.1.1 cannot be used because this is 08:55:48.000 --> 08:55:50.510 align:start position:0% 1.1.1.1 cannot be used because this is what's<08:55:48.298> called<08:55:48.600> the<08:55:49.080> all<08:55:49.378> hosts<08:55:49.978> or<08:55:50.218> the<08:55:50.340> who 08:55:50.510 --> 08:55:50.520 align:start position:0% what's called the all hosts or the who 08:55:50.520 --> 08:55:54.350 align:start position:0% what's called the all hosts or the who is<08:55:50.760> address<08:55:51.680> so<08:55:52.680> these<08:55:53.280> basically<08:55:53.878> what 08:55:54.350 --> 08:55:54.360 align:start position:0% is address so these basically what 08:55:54.360 --> 08:55:56.948 align:start position:0% is address so these basically what whereas<08:55:54.898> 127<08:55:55.558> is<08:55:55.798> for<08:55:55.978> me 08:55:56.948 --> 08:55:56.958 align:start position:0% whereas 127 is for me 08:55:56.958 --> 08:56:00.288 align:start position:0% whereas 127 is for me 1.1.1.1<08:55:57.958> is<08:55:58.200> for<08:55:58.500> everyone<08:55:58.798> so<08:55:59.398> these<08:55:59.818> we<08:56:00.058> can 08:56:00.288 --> 08:56:00.298 align:start position:0% 1.1.1.1 is for everyone so these we can 08:56:00.298 --> 08:56:01.968 align:start position:0% 1.1.1.1 is for everyone so these we can never<08:56:00.600> use<08:56:00.898> the<08:56:01.318> important<08:56:01.558> one<08:56:01.680> I<08:56:01.860> really 08:56:01.968 --> 08:56:01.978 align:start position:0% never use the important one I really 08:56:01.978 --> 08:56:04.128 align:start position:0% never use the important one I really want<08:56:02.160> you<08:56:02.280> to<08:56:02.398> remember<08:56:02.520> here<08:56:02.940> is<08:56:03.660> this<08:56:03.958> one 08:56:04.128 --> 08:56:04.138 align:start position:0% want you to remember here is this one 08:56:04.138 --> 08:56:05.388 align:start position:0% want you to remember here is this one and<08:56:04.680> you're<08:56:04.798> going<08:56:04.978> to<08:56:05.100> want<08:56:05.160> to<08:56:05.280> remember 08:56:05.388 --> 08:56:05.398 align:start position:0% and you're going to want to remember 08:56:05.398 --> 08:56:08.330 align:start position:0% and you're going to want to remember that<08:56:05.818> for<08:56:06.058> instance<08:56:06.298> 255<08:56:07.200> in<08:56:07.740> the<08:56:07.978> host 08:56:08.330 --> 08:56:08.340 align:start position:0% that for instance 255 in the host 08:56:08.340 --> 08:56:11.388 align:start position:0% that for instance 255 in the host portion<08:56:09.000> can<08:56:09.600> never<08:56:09.780> be<08:56:10.020> used<08:56:10.260> again<08:56:10.920> not<08:56:11.280> only 08:56:11.388 --> 08:56:11.398 align:start position:0% portion can never be used again not only 08:56:11.398 --> 08:56:13.368 align:start position:0% portion can never be used again not only because<08:56:11.638> that's<08:56:11.878> going<08:56:12.058> to<08:56:12.120> ruin<08:56:12.420> a<08:56:12.540> subnet<08:56:12.898> as 08:56:13.368 --> 08:56:13.378 align:start position:0% because that's going to ruin a subnet as 08:56:13.378 --> 08:56:15.350 align:start position:0% because that's going to ruin a subnet as we've<08:56:13.680> talked<08:56:13.920> about<08:56:13.978> but<08:56:14.638> also<08:56:14.940> this<08:56:15.240> is 08:56:15.350 --> 08:56:15.360 align:start position:0% we've talked about but also this is 08:56:15.360 --> 08:56:17.030 align:start position:0% we've talked about but also this is reserved<08:56:15.840> for<08:56:15.958> what's<08:56:16.138> called<08:56:16.378> a<08:56:16.740> broadcast 08:56:17.030 --> 08:56:17.040 align:start position:0% reserved for what's called a broadcast 08:56:17.040 --> 08:56:20.208 align:start position:0% reserved for what's called a broadcast address<08:56:17.780> now<08:56:18.780> there<08:56:19.020> are<08:56:19.200> portions<08:56:19.620> of<08:56:19.860> each 08:56:20.208 --> 08:56:20.218 align:start position:0% address now there are portions of each 08:56:20.218 --> 08:56:23.030 align:start position:0% address now there are portions of each class<08:56:20.638> that<08:56:21.540> are<08:56:21.840> allocated<08:56:22.378> either<08:56:22.680> for 08:56:23.030 --> 08:56:23.040 align:start position:0% class that are allocated either for 08:56:23.040 --> 08:56:25.670 align:start position:0% class that are allocated either for public<08:56:23.280> or<08:56:23.638> private<08:56:24.058> use<08:56:24.378> private<08:56:25.378> IP 08:56:25.670 --> 08:56:25.680 align:start position:0% public or private use private IP 08:56:25.680 --> 08:56:28.850 align:start position:0% public or private use private IP addresses<08:56:26.360> are<08:56:27.360> not<08:56:27.660> routable 08:56:28.850 --> 08:56:28.860 align:start position:0% addresses are not routable 08:56:28.860 --> 08:56:31.070 align:start position:0% addresses are not routable this<08:56:29.760> means 08:56:31.070 --> 08:56:31.080 align:start position:0% this means 08:56:31.080 --> 08:56:33.308 align:start position:0% this means that<08:56:31.680> they<08:56:31.860> are<08:56:32.040> assigned<08:56:32.458> for<08:56:32.638> use<08:56:32.878> on 08:56:33.308 --> 08:56:33.318 align:start position:0% that they are assigned for use on 08:56:33.318 --> 08:56:35.570 align:start position:0% that they are assigned for use on internal<08:56:34.318> networks<08:56:34.798> such<08:56:34.978> as<08:56:35.160> your<08:56:35.458> home 08:56:35.570 --> 08:56:35.580 align:start position:0% internal networks such as your home 08:56:35.580 --> 08:56:38.388 align:start position:0% internal networks such as your home network<08:56:35.878> or<08:56:36.600> your<08:56:36.840> office<08:56:37.080> Network<08:56:37.500> when 08:56:38.388 --> 08:56:38.398 align:start position:0% network or your office Network when 08:56:38.398 --> 08:56:40.490 align:start position:0% network or your office Network when these<08:56:38.700> addresses<08:56:39.360> transmit<08:56:39.958> data<08:56:40.260> and<08:56:40.378> it 08:56:40.490 --> 08:56:40.500 align:start position:0% these addresses transmit data and it 08:56:40.500 --> 08:56:43.730 align:start position:0% these addresses transmit data and it reaches<08:56:40.860> a<08:56:41.100> router<08:56:41.458> the<08:56:42.180> router<08:56:42.600> is<08:56:42.958> not<08:56:43.378> going 08:56:43.730 --> 08:56:43.740 align:start position:0% reaches a router the router is not going 08:56:43.740 --> 08:56:47.330 align:start position:0% reaches a router the router is not going to<08:56:44.340> uh<08:56:45.000> route<08:56:45.360> it<08:56:45.660> outside<08:56:45.958> of<08:56:46.318> the<08:56:46.440> network<08:56:46.558> so 08:56:47.330 --> 08:56:47.340 align:start position:0% to uh route it outside of the network so 08:56:47.340 --> 08:56:49.250 align:start position:0% to uh route it outside of the network so these<08:56:47.700> addresses<08:56:48.240> can<08:56:48.540> be<08:56:48.660> used<08:56:48.898> without 08:56:49.250 --> 08:56:49.260 align:start position:0% these addresses can be used without 08:56:49.260 --> 08:56:51.708 align:start position:0% these addresses can be used without needing<08:56:49.798> to<08:56:49.978> purchase<08:56:50.340> or<08:56:50.878> leasing<08:56:51.298> an<08:56:51.478> IP 08:56:51.708 --> 08:56:51.718 align:start position:0% needing to purchase or leasing an IP 08:56:51.718 --> 08:56:53.448 align:start position:0% needing to purchase or leasing an IP address<08:56:51.898> from<08:56:52.318> your<08:56:52.500> ISP<08:56:53.040> or<08:56:53.218> Internet 08:56:53.448 --> 08:56:53.458 align:start position:0% address from your ISP or Internet 08:56:53.458 --> 08:56:56.150 align:start position:0% address from your ISP or Internet service<08:56:53.818> provider<08:56:54.420> or<08:56:54.840> governing<08:56:55.378> entity<08:56:55.680> so 08:56:56.150 --> 08:56:56.160 align:start position:0% service provider or governing entity so 08:56:56.160 --> 08:56:57.770 align:start position:0% service provider or governing entity so this<08:56:56.280> is<08:56:56.398> how<08:56:56.520> I<08:56:56.638> could<08:56:56.818> create<08:56:57.058> an<08:56:57.420> internal 08:56:57.770 --> 08:56:57.780 align:start position:0% this is how I could create an internal 08:56:57.780 --> 08:57:00.410 align:start position:0% this is how I could create an internal Network<08:56:57.958> in<08:56:58.260> my<08:56:58.440> home<08:56:58.680> and<08:56:59.520> I<08:56:59.760> don't<08:56:59.878> need<08:57:00.120> to 08:57:00.410 --> 08:57:00.420 align:start position:0% Network in my home and I don't need to 08:57:00.420 --> 08:57:02.990 align:start position:0% Network in my home and I don't need to go<08:57:00.540> register<08:57:01.020> it<08:57:01.318> and<08:57:02.218> I<08:57:02.580> might<08:57:02.700> not<08:57:02.818> be<08:57:02.940> able 08:57:02.990 --> 08:57:03.000 align:start position:0% go register it and I might not be able 08:57:03.000 --> 08:57:04.250 align:start position:0% go register it and I might not be able to<08:57:03.120> access<08:57:03.240> the<08:57:03.600> internet<08:57:03.660> but<08:57:03.958> I<08:57:04.080> don't<08:57:04.138> need 08:57:04.250 --> 08:57:04.260 align:start position:0% to access the internet but I don't need 08:57:04.260 --> 08:57:05.930 align:start position:0% to access the internet but I don't need to<08:57:04.378> register<08:57:04.558> if<08:57:04.860> I<08:57:04.978> want<08:57:05.100> to<08:57:05.218> go<08:57:05.580> out<08:57:05.700> to<08:57:05.818> the 08:57:05.930 --> 08:57:05.940 align:start position:0% to register if I want to go out to the 08:57:05.940 --> 08:57:09.110 align:start position:0% to register if I want to go out to the internet<08:57:06.058> then<08:57:06.478> I<08:57:06.718> can<08:57:06.898> share<08:57:07.580> using<08:57:08.580> devices 08:57:09.110 --> 08:57:09.120 align:start position:0% internet then I can share using devices 08:57:09.120 --> 08:57:11.690 align:start position:0% internet then I can share using devices and<08:57:10.218> resources<08:57:11.218> we've<08:57:11.458> talked<08:57:11.638> about 08:57:11.690 --> 08:57:11.700 align:start position:0% and resources we've talked about 08:57:11.700 --> 08:57:13.548 align:start position:0% and resources we've talked about previously<08:57:12.120> and<08:57:12.240> we'll<08:57:12.360> talk<08:57:12.478> about<08:57:12.600> later<08:57:12.840> a 08:57:13.548 --> 08:57:13.558 align:start position:0% previously and we'll talk about later a 08:57:13.558 --> 08:57:16.128 align:start position:0% previously and we'll talk about later a public<08:57:13.740> IP<08:57:14.160> address<08:57:14.398> with<08:57:15.240> all<08:57:15.420> the<08:57:15.660> internal 08:57:16.128 --> 08:57:16.138 align:start position:0% public IP address with all the internal 08:57:16.138 --> 08:57:18.110 align:start position:0% public IP address with all the internal devices<08:57:16.440> that<08:57:16.920> are<08:57:17.160> configured<08:57:17.760> using 08:57:18.110 --> 08:57:18.120 align:start position:0% devices that are configured using 08:57:18.120 --> 08:57:20.808 align:start position:0% devices that are configured using private<08:57:18.540> IP<08:57:18.840> addresses<08:57:19.378> now<08:57:20.040> since<08:57:20.340> these<08:57:20.638> are 08:57:20.808 --> 08:57:20.818 align:start position:0% private IP addresses now since these are 08:57:20.818 --> 08:57:23.330 align:start position:0% private IP addresses now since these are not<08:57:21.420> able<08:57:21.718> to<08:57:21.840> be<08:57:22.080> used<08:57:22.318> externally<08:57:22.920> to<08:57:23.218> our 08:57:23.330 --> 08:57:23.340 align:start position:0% not able to be used externally to our 08:57:23.340 --> 08:57:26.090 align:start position:0% not able to be used externally to our Network<08:57:23.580> these<08:57:24.298> IP<08:57:24.540> addresses<08:57:24.958> can<08:57:25.260> be<08:57:25.798> used 08:57:26.090 --> 08:57:26.100 align:start position:0% Network these IP addresses can be used 08:57:26.100 --> 08:57:29.030 align:start position:0% Network these IP addresses can be used by<08:57:26.638> as<08:57:26.818> many<08:57:27.000> devices<08:57:27.298> as<08:57:27.600> necessary<08:57:28.200> as<08:57:28.860> long 08:57:29.030 --> 08:57:29.040 align:start position:0% by as many devices as necessary as long 08:57:29.040 --> 08:57:30.948 align:start position:0% by as many devices as necessary as long as<08:57:29.160> we<08:57:29.398> never<08:57:29.580> double<08:57:29.878> over<08:57:30.120> one<08:57:30.360> IP<08:57:30.660> address 08:57:30.948 --> 08:57:30.958 align:start position:0% as we never double over one IP address 08:57:30.958 --> 08:57:34.968 align:start position:0% as we never double over one IP address per<08:57:31.378> device<08:57:31.680> so<08:57:32.520> the<08:57:32.700> class<08:57:32.940> a<08:57:33.558> private<08:57:34.558> IP 08:57:34.968 --> 08:57:34.978 align:start position:0% per device so the class a private IP 08:57:34.978 --> 08:57:37.150 align:start position:0% per device so the class a private IP address<08:57:35.160> range<08:57:35.760> remember<08:57:36.360> we<08:57:36.660> talked<08:57:36.840> about 08:57:37.150 --> 08:57:37.160 align:start position:0% address range remember we talked about 08:57:37.160 --> 08:57:40.968 align:start position:0% address range remember we talked about 10.0.0.0<08:57:38.160> because<08:57:38.818> we<08:57:39.180> cannot<08:57:39.478> have<08:57:39.718> zeros 08:57:40.968 --> 08:57:40.978 align:start position:0% 10.0.0.0 because we cannot have zeros 08:57:40.978 --> 08:57:44.208 align:start position:0% 10.0.0.0 because we cannot have zeros right<08:57:41.398> remember<08:57:41.780> 10.0.0<08:57:42.780> and<08:57:43.260> 285<08:57:43.860> we 08:57:44.208 --> 08:57:44.218 align:start position:0% right remember 10.0.0 and 285 we 08:57:44.218 --> 08:57:46.610 align:start position:0% right remember 10.0.0 and 285 we actually<08:57:44.458> cannot<08:57:45.240> assign<08:57:45.600> but<08:57:46.080> any<08:57:46.318> address 08:57:46.610 --> 08:57:46.620 align:start position:0% actually cannot assign but any address 08:57:46.620 --> 08:57:51.788 align:start position:0% actually cannot assign but any address in<08:57:47.340> between<08:57:47.580> that<08:57:48.180> so 08:57:51.788 --> 08:57:51.798 align:start position:0% 08:57:51.798 --> 08:57:55.010 align:start position:0% 10.1.126.5<08:57:53.000> would<08:57:54.000> fall<08:57:54.298> into<08:57:54.540> what's<08:57:54.718> called 08:57:55.010 --> 08:57:55.020 align:start position:0% 10.1.126.5 would fall into what's called 08:57:55.020 --> 08:57:57.170 align:start position:0% 10.1.126.5 would fall into what's called a<08:57:55.558> private<08:57:55.978> address<08:57:56.218> range<08:57:56.760> and<08:57:56.878> you<08:57:57.058> might 08:57:57.170 --> 08:57:57.180 align:start position:0% a private address range and you might 08:57:57.180 --> 08:57:59.690 align:start position:0% a private address range and you might see<08:57:57.360> this<08:57:57.660> in<08:57:57.898> your<08:57:58.020> home<08:57:58.200> router<08:57:58.620> as<08:57:58.798> well<08:57:58.978> so 08:57:59.690 --> 08:57:59.700 align:start position:0% see this in your home router as well so 08:57:59.700 --> 08:58:01.548 align:start position:0% see this in your home router as well so this<08:57:59.940> makes<08:58:00.180> it<08:58:00.420> easily<08:58:00.718> discernible<08:58:01.260> from 08:58:01.548 --> 08:58:01.558 align:start position:0% this makes it easily discernible from 08:58:01.558 --> 08:58:04.010 align:start position:0% this makes it easily discernible from other<08:58:01.798> addresses<08:58:02.398> in<08:58:02.580> its<08:58:02.878> class<08:58:03.058> anything 08:58:04.010 --> 08:58:04.020 align:start position:0% other addresses in its class anything 08:58:04.020 --> 08:58:06.708 align:start position:0% other addresses in its class anything that<08:58:04.440> has<08:58:04.620> the<08:58:04.798> 10<08:58:04.978> to<08:58:05.218> begin<08:58:05.340> with<08:58:05.638> cannot<08:58:06.478> be 08:58:06.708 --> 08:58:06.718 align:start position:0% that has the 10 to begin with cannot be 08:58:06.718 --> 08:58:08.750 align:start position:0% that has the 10 to begin with cannot be used<08:58:07.020> on<08:58:07.500> a<08:58:07.620> Class<08:58:07.740> A<08:58:07.920> Network<08:58:08.160> or<08:58:08.398> any<08:58:08.520> network 08:58:08.750 --> 08:58:08.760 align:start position:0% used on a Class A Network or any network 08:58:08.760 --> 08:58:10.430 align:start position:0% used on a Class A Network or any network except<08:58:09.298> privately 08:58:10.430 --> 08:58:10.440 align:start position:0% except privately 08:58:10.440 --> 08:58:13.368 align:start position:0% except privately we<08:58:10.920> also<08:58:11.100> have<08:58:11.218> a<08:58:11.398> class<08:58:11.520> B<08:58:11.958> uh<08:58:12.958> Private 08:58:13.368 --> 08:58:13.378 align:start position:0% we also have a class B uh Private 08:58:13.378 --> 08:58:16.388 align:start position:0% we also have a class B uh Private Exchange<08:58:13.978> which<08:58:14.340> is 08:58:16.388 --> 08:58:16.398 align:start position:0% Exchange which is 08:58:16.398 --> 08:58:19.990 align:start position:0% Exchange which is 172.16.0.0<08:58:17.398> through 08:58:19.990 --> 08:58:20.000 align:start position:0% 08:58:20.000 --> 08:58:24.548 align:start position:0% 172.31.255.255<08:58:21.080> and<08:58:22.080> Class<08:58:22.378> C<08:58:22.920> which<08:58:23.520> is 08:58:24.548 --> 08:58:24.558 align:start position:0% 172.31.255.255 and Class C which is 08:58:24.558 --> 08:58:28.070 align:start position:0% 172.31.255.255 and Class C which is 192.168.0.0<08:58:25.558> through<08:58:25.920> the<08:58:26.520> 255<08:58:27.058> to<08:58:27.240> 255.<08:58:27.840> this 08:58:28.070 --> 08:58:28.080 align:start position:0% 192.168.0.0 through the 255 to 255. this 08:58:28.080 --> 08:58:29.990 align:start position:0% 192.168.0.0 through the 255 to 255. this one<08:58:28.200> you<08:58:28.378> might<08:58:28.500> have<08:58:28.680> seen<08:58:28.978> the<08:58:29.218> most<08:58:29.398> this 08:58:29.990 --> 08:58:30.000 align:start position:0% one you might have seen the most this 08:58:30.000 --> 08:58:31.430 align:start position:0% one you might have seen the most this one<08:58:30.180> I'm<08:58:30.298> guessing<08:58:30.600> you've<08:58:30.840> seen<08:58:31.020> the<08:58:31.260> last 08:58:31.430 --> 08:58:31.440 align:start position:0% one I'm guessing you've seen the last 08:58:31.440 --> 08:58:33.410 align:start position:0% one I'm guessing you've seen the last this<08:58:32.040> one's<08:58:32.340> probably<08:58:32.580> the<08:58:32.940> second<08:58:33.120> most 08:58:33.410 --> 08:58:33.420 align:start position:0% this one's probably the second most 08:58:33.420 --> 08:58:36.048 align:start position:0% this one's probably the second most common<08:58:33.660> the<08:58:33.958> 10<08:58:34.080> dot<08:58:34.558> so<08:58:35.218> if<08:58:35.458> you<08:58:35.580> have<08:58:35.760> a 08:58:36.048 --> 08:58:36.058 align:start position:0% common the 10 dot so if you have a 08:58:36.058 --> 08:58:38.510 align:start position:0% common the 10 dot so if you have a internal<08:58:36.540> Network<08:58:36.718> at<08:58:37.020> your<08:58:37.200> home<08:58:37.440> you<08:58:38.340> might 08:58:38.510 --> 08:58:38.520 align:start position:0% internal Network at your home you might 08:58:38.520 --> 08:58:40.610 align:start position:0% internal Network at your home you might have<08:58:38.878> your<08:58:39.360> address<08:58:39.540> on<08:58:39.840> your<08:58:39.958> computer<08:58:40.138> right 08:58:40.610 --> 08:58:40.620 align:start position:0% have your address on your computer right 08:58:40.620 --> 08:58:42.048 align:start position:0% have your address on your computer right now<08:58:40.798> for<08:58:41.040> instance<08:58:41.218> if<08:58:41.398> it's<08:58:41.520> not<08:58:41.700> connected 08:58:42.048 --> 08:58:42.058 align:start position:0% now for instance if it's not connected 08:58:42.058 --> 08:58:43.070 align:start position:0% now for instance if it's not connected directly<08:58:42.360> to<08:58:42.540> the<08:58:42.600> network<08:58:42.718> if<08:58:42.958> it's 08:58:43.070 --> 08:58:43.080 align:start position:0% directly to the network if it's 08:58:43.080 --> 08:58:44.948 align:start position:0% directly to the network if it's connected<08:58:43.378> to<08:58:43.440> a<08:58:43.620> router<08:58:43.920> might<08:58:44.398> be<08:58:44.580> something 08:58:44.948 --> 08:58:44.958 align:start position:0% connected to a router might be something 08:58:44.958 --> 08:58:49.128 align:start position:0% connected to a router might be something like<08:58:45.958> this<08:58:46.500> or<08:58:47.398> like 08:58:49.128 --> 08:58:49.138 align:start position:0% like this or like 08:58:49.138 --> 08:58:53.628 align:start position:0% like this or like this<08:58:49.978> or<08:58:50.398> even 08:58:53.628 --> 08:58:53.638 align:start position:0% 08:58:53.638 --> 08:58:56.150 align:start position:0% like<08:58:54.298> this<08:58:54.540> all<08:58:55.080> right<08:58:55.260> that's<08:58:55.620> because<08:58:55.798> these 08:58:56.150 --> 08:58:56.160 align:start position:0% like this all right that's because these 08:58:56.160 --> 08:58:57.948 align:start position:0% like this all right that's because these are<08:58:56.280> each<08:58:56.398> private<08:58:56.940> addresses<08:58:57.478> it's 08:58:57.948 --> 08:58:57.958 align:start position:0% are each private addresses it's 08:58:57.958 --> 08:58:59.628 align:start position:0% are each private addresses it's important<08:58:58.500> that<08:58:58.680> you<08:58:58.860> commit<08:58:59.160> these<08:58:59.458> to 08:58:59.628 --> 08:58:59.638 align:start position:0% important that you commit these to 08:58:59.638 --> 08:59:02.270 align:start position:0% important that you commit these to memory<08:58:59.878> as<08:59:00.120> well<08:59:00.240> because<08:59:00.840> these<08:59:01.378> will<08:59:01.620> appear 08:59:02.270 --> 08:59:02.280 align:start position:0% memory as well because these will appear 08:59:02.280 --> 08:59:04.070 align:start position:0% memory as well because these will appear on<08:59:02.458> the<08:59:02.580> exam<08:59:02.818> and<08:59:02.940> remember<08:59:03.120> the<08:59:03.780> important 08:59:04.070 --> 08:59:04.080 align:start position:0% on the exam and remember the important 08:59:04.080 --> 08:59:06.230 align:start position:0% on the exam and remember the important thing<08:59:04.260> with<08:59:04.500> a<08:59:04.740> uh 08:59:06.230 --> 08:59:06.240 align:start position:0% thing with a uh 08:59:06.240 --> 08:59:08.448 align:start position:0% thing with a uh with<08:59:06.718> a<08:59:06.958> private<08:59:07.318> IP<08:59:07.558> address<08:59:07.740> as<08:59:08.100> I<08:59:08.280> mentioned 08:59:08.448 --> 08:59:08.458 align:start position:0% with a private IP address as I mentioned 08:59:08.458 --> 08:59:10.010 align:start position:0% with a private IP address as I mentioned right<08:59:08.580> here<08:59:08.700> is<08:59:08.818> they're<08:59:09.058> not<08:59:09.298> routable<08:59:09.718> and<08:59:09.898> I 08:59:10.010 --> 08:59:10.020 align:start position:0% right here is they're not routable and I 08:59:10.020 --> 08:59:12.048 align:start position:0% right here is they're not routable and I don't<08:59:10.138> need<08:59:10.318> a<08:59:10.500> lease<08:59:10.798> to<08:59:10.978> use<08:59:11.100> them<08:59:11.340> so<08:59:11.940> when 08:59:12.048 --> 08:59:12.058 align:start position:0% don't need a lease to use them so when 08:59:12.058 --> 08:59:13.730 align:start position:0% don't need a lease to use them so when tasked<08:59:12.478> with<08:59:12.600> subnetting<08:59:13.138> a<08:59:13.260> network<08:59:13.378> you 08:59:13.730 --> 08:59:13.740 align:start position:0% tasked with subnetting a network you 08:59:13.740 --> 08:59:15.530 align:start position:0% tasked with subnetting a network you need<08:59:13.978> to<08:59:14.100> understand<08:59:14.280> how<08:59:14.818> to<08:59:14.940> calculate<08:59:15.298> how 08:59:15.530 --> 08:59:15.540 align:start position:0% need to understand how to calculate how 08:59:15.540 --> 08:59:17.628 align:start position:0% need to understand how to calculate how many<08:59:15.660> hosts<08:59:16.200> and<08:59:16.680> how<08:59:16.860> many<08:59:17.040> networks<08:59:17.520> are 08:59:17.628 --> 08:59:17.638 align:start position:0% many hosts and how many networks are 08:59:17.638 --> 08:59:19.430 align:start position:0% many hosts and how many networks are available<08:59:17.818> if<08:59:18.600> we<08:59:18.780> want<08:59:18.898> to<08:59:18.958> determine<08:59:19.318> the 08:59:19.430 --> 08:59:19.440 align:start position:0% available if we want to determine the 08:59:19.440 --> 08:59:21.888 align:start position:0% available if we want to determine the number<08:59:19.620> of<08:59:19.920> hosts<08:59:20.638> that<08:59:20.818> are<08:59:21.000> available<08:59:21.180> we 08:59:21.888 --> 08:59:21.898 align:start position:0% number of hosts that are available we 08:59:21.898 --> 08:59:25.490 align:start position:0% number of hosts that are available we apply<08:59:22.200> this<08:59:22.500> Formula<08:59:22.920> 2<08:59:23.160> to<08:59:23.398> the<08:59:23.520> x<08:59:23.760> minus<08:59:24.540> 2. 08:59:25.490 --> 08:59:25.500 align:start position:0% apply this Formula 2 to the x minus 2. 08:59:25.500 --> 08:59:29.930 align:start position:0% apply this Formula 2 to the x minus 2. and<08:59:26.100> this<08:59:26.280> is<08:59:26.458> where<08:59:26.760> X 08:59:29.930 --> 08:59:29.940 align:start position:0% 08:59:29.940 --> 08:59:33.230 align:start position:0% equals<08:59:30.600> the<08:59:30.780> number<08:59:30.958> of<08:59:31.440> node<08:59:32.160> bits<08:59:32.760> and 08:59:33.230 --> 08:59:33.240 align:start position:0% equals the number of node bits and 08:59:33.240 --> 08:59:35.388 align:start position:0% equals the number of node bits and that's<08:59:33.360> after<08:59:33.600> we<08:59:33.898> break<08:59:34.138> it<08:59:34.378> down<08:59:34.620> from 08:59:35.388 --> 08:59:35.398 align:start position:0% that's after we break it down from 08:59:35.398 --> 08:59:38.208 align:start position:0% that's after we break it down from decimal<08:59:36.000> to<08:59:36.600> binary 08:59:38.208 --> 08:59:38.218 align:start position:0% decimal to binary 08:59:38.218 --> 08:59:42.708 align:start position:0% decimal to binary now<08:59:38.700> the<08:59:39.000> reason<08:59:39.120> for<08:59:39.478> the<08:59:39.660> minus<08:59:40.080> 2<08:59:40.318> here 08:59:42.708 --> 08:59:42.718 align:start position:0% 08:59:42.718 --> 08:59:45.170 align:start position:0% is<08:59:43.318> because<08:59:43.558> again<08:59:43.860> we<08:59:44.218> cannot<08:59:44.520> use<08:59:44.760> a<08:59:44.940> DOT 08:59:45.170 --> 08:59:45.180 align:start position:0% is because again we cannot use a DOT 08:59:45.180 --> 08:59:49.510 align:start position:0% is because again we cannot use a DOT 0.0.0<08:59:46.138> address<08:59:46.558> or 08:59:49.510 --> 08:59:49.520 align:start position:0% 08:59:49.520 --> 08:59:52.070 align:start position:0% a.255.255.255<08:59:50.520> address<08:59:51.120> which<08:59:51.718> would<08:59:51.898> mean 08:59:52.070 --> 08:59:52.080 align:start position:0% a.255.255.255 address which would mean 08:59:52.080 --> 08:59:55.430 align:start position:0% a.255.255.255 address which would mean all<08:59:52.440> zeros<08:59:52.798> are<08:59:52.978> all<08:59:53.160> ones<08:59:53.520> in<08:59:54.180> the<08:59:54.420> subnet<08:59:54.958> and 08:59:55.430 --> 08:59:55.440 align:start position:0% all zeros are all ones in the subnet and 08:59:55.440 --> 08:59:58.490 align:start position:0% all zeros are all ones in the subnet and so<08:59:55.620> we<08:59:55.798> need<08:59:55.920> to<08:59:56.040> make<08:59:56.280> sure<08:59:56.580> uh<08:59:57.540> rather<08:59:57.840> in<08:59:58.080> the 08:59:58.490 --> 08:59:58.500 align:start position:0% so we need to make sure uh rather in the 08:59:58.500 --> 09:00:00.708 align:start position:0% so we need to make sure uh rather in the um uh<08:59:58.978> in<08:59:59.280> the<08:59:59.398> bit<08:59:59.580> right<09:00:00.180> when<09:00:00.360> it's<09:00:00.478> broken 09:00:00.708 --> 09:00:00.718 align:start position:0% um uh in the bit right when it's broken 09:00:00.718 --> 09:00:04.010 align:start position:0% um uh in the bit right when it's broken down<09:00:01.080> and<09:00:01.558> so<09:00:01.680> we<09:00:01.860> need<09:00:02.040> to<09:00:02.160> make<09:00:02.398> sure<09:00:02.700> that 09:00:04.010 --> 09:00:04.020 align:start position:0% down and so we need to make sure that 09:00:04.020 --> 09:00:06.850 align:start position:0% down and so we need to make sure that um this<09:00:04.680> is<09:00:04.798> the<09:00:04.920> case 09:00:06.850 --> 09:00:06.860 align:start position:0% um this is the case 09:00:06.860 --> 09:00:09.530 align:start position:0% um this is the case we<09:00:07.860> also<09:00:08.100> need<09:00:08.340> to<09:00:08.638> know<09:00:08.818> the<09:00:09.180> number<09:00:09.298> of 09:00:09.530 --> 09:00:09.540 align:start position:0% we also need to know the number of 09:00:09.540 --> 09:00:11.750 align:start position:0% we also need to know the number of networks<09:00:10.378> and<09:00:10.978> to<09:00:11.100> do<09:00:11.218> that<09:00:11.398> we're<09:00:11.580> going<09:00:11.700> to 09:00:11.750 --> 09:00:11.760 align:start position:0% networks and to do that we're going to 09:00:11.760 --> 09:00:14.690 align:start position:0% networks and to do that we're going to do<09:00:11.940> 2<09:00:12.120> to<09:00:12.240> the<09:00:12.360> Y<09:00:12.540> minus<09:00:12.898> 2<09:00:13.080> where<09:00:13.740> y<09:00:14.040> equals<09:00:14.520> the 09:00:14.690 --> 09:00:14.700 align:start position:0% do 2 to the Y minus 2 where y equals the 09:00:14.700 --> 09:00:17.930 align:start position:0% do 2 to the Y minus 2 where y equals the number<09:00:14.818> of<09:00:15.058> network<09:00:15.898> bits<09:00:16.558> so<09:00:17.340> let's<09:00:17.638> take<09:00:17.818> a 09:00:17.930 --> 09:00:17.940 align:start position:0% number of network bits so let's take a 09:00:17.940 --> 09:00:23.948 align:start position:0% number of network bits so let's take a look<09:00:18.000> at<09:00:18.240> this<09:00:18.420> if<09:00:19.260> we<09:00:19.440> have<09:00:19.620> the<09:00:19.860> IP<09:00:20.160> address 09:00:23.948 --> 09:00:23.958 align:start position:0% 09:00:23.958 --> 09:00:26.270 align:start position:0% 162.85.120.27<09:00:24.958> and<09:00:25.440> we<09:00:25.558> have<09:00:25.680> a<09:00:25.740> subnet<09:00:26.100> mask 09:00:26.270 --> 09:00:26.280 align:start position:0% 162.85.120.27 and we have a subnet mask 09:00:26.280 --> 09:00:27.670 align:start position:0% 162.85.120.27 and we have a subnet mask of 09:00:27.670 --> 09:00:27.680 align:start position:0% of 09:00:27.680 --> 09:00:30.530 align:start position:0% of 255.255.255.0<09:00:28.680> by<09:00:29.580> the<09:00:29.760> way 09:00:30.530 --> 09:00:30.540 align:start position:0% 255.255.255.0 by the way 09:00:30.540 --> 09:00:32.208 align:start position:0% 255.255.255.0 by the way we<09:00:30.780> can<09:00:30.840> look<09:00:31.020> at<09:00:31.200> this<09:00:31.318> and<09:00:31.558> we<09:00:31.680> automatically 09:00:32.208 --> 09:00:32.218 align:start position:0% we can look at this and we automatically 09:00:32.218 --> 09:00:34.690 align:start position:0% we can look at this and we automatically know<09:00:32.520> that 09:00:34.690 --> 09:00:34.700 align:start position:0% know that 09:00:34.700 --> 09:00:38.288 align:start position:0% know that 162.85.120.27<09:00:35.700> this<09:00:36.478> looks<09:00:36.780> like<09:00:36.958> a<09:00:37.260> class 09:00:38.288 --> 09:00:38.298 align:start position:0% 162.85.120.27 this looks like a class 09:00:38.298 --> 09:00:42.708 align:start position:0% 162.85.120.27 this looks like a class b<09:00:39.298> i<09:00:39.600> p<09:00:39.780> address<09:00:40.020> and<09:00:40.978> the<09:00:41.160> 255<09:00:41.580> the<09:00:41.700> 255<09:00:42.120> to<09:00:42.240> 255 09:00:42.708 --> 09:00:42.718 align:start position:0% b i p address and the 255 the 255 to 255 09:00:42.718 --> 09:00:46.430 align:start position:0% b i p address and the 255 the 255 to 255 is<09:00:42.958> actually<09:00:43.458> our<09:00:44.458> default<09:00:44.878> Class<09:00:45.298> C<09:00:45.958> subnet 09:00:46.430 --> 09:00:46.440 align:start position:0% is actually our default Class C subnet 09:00:46.440 --> 09:00:48.048 align:start position:0% is actually our default Class C subnet so<09:00:46.620> this<09:00:46.798> is<09:00:46.920> not<09:00:47.160> the<09:00:47.398> default<09:00:47.700> that<09:00:47.878> we're 09:00:48.048 --> 09:00:48.058 align:start position:0% so this is not the default that we're 09:00:48.058 --> 09:00:49.968 align:start position:0% so this is not the default that we're working<09:00:48.240> with<09:00:48.420> here<09:00:48.718> so<09:00:49.318> we<09:00:49.500> need<09:00:49.620> to<09:00:49.798> figure 09:00:49.968 --> 09:00:49.978 align:start position:0% working with here so we need to figure 09:00:49.978 --> 09:00:52.368 align:start position:0% working with here so we need to figure out<09:00:50.340> uh<09:00:51.058> some<09:00:51.298> information<09:00:51.478> here<09:00:51.958> so<09:00:52.260> let's 09:00:52.368 --> 09:00:52.378 align:start position:0% out uh some information here so let's 09:00:52.378 --> 09:00:54.288 align:start position:0% out uh some information here so let's break<09:00:52.620> it<09:00:52.740> down<09:00:52.920> into<09:00:53.040> bits<09:00:53.520> and<09:00:53.818> I'm<09:00:53.940> do<09:00:54.180> that 09:00:54.288 --> 09:00:54.298 align:start position:0% break it down into bits and I'm do that 09:00:54.298 --> 09:00:55.548 align:start position:0% break it down into bits and I'm do that here<09:00:54.420> and<09:00:54.540> if<09:00:54.660> you<09:00:54.780> wanted<09:00:54.898> to<09:00:55.080> check<09:00:55.200> my<09:00:55.378> math 09:00:55.548 --> 09:00:55.558 align:start position:0% here and if you wanted to check my math 09:00:55.558 --> 09:00:58.128 align:start position:0% here and if you wanted to check my math you<09:00:55.860> could<09:00:55.978> now<09:00:56.760> the<09:00:57.000> number<09:00:57.120> of<09:00:57.298> network<09:00:57.600> bits 09:00:58.128 --> 09:00:58.138 align:start position:0% you could now the number of network bits 09:00:58.138 --> 09:01:00.708 align:start position:0% you could now the number of network bits is<09:00:58.378> right<09:00:58.620> here<09:00:58.860> the<09:00:59.638> Y<09:00:59.818> and<09:01:00.298> the<09:01:00.420> number<09:01:00.540> of 09:01:00.708 --> 09:01:00.718 align:start position:0% is right here the Y and the number of 09:01:00.718 --> 09:01:02.690 align:start position:0% is right here the Y and the number of node<09:01:01.020> bits<09:01:01.378> is<09:01:01.500> right<09:01:01.680> here 09:01:02.690 --> 09:01:02.700 align:start position:0% node bits is right here 09:01:02.700 --> 09:01:06.288 align:start position:0% node bits is right here the<09:01:03.240> X<09:01:03.558> so<09:01:04.558> if<09:01:04.798> we<09:01:04.978> pop<09:01:05.218> this<09:01:05.520> into<09:01:05.760> our 09:01:06.288 --> 09:01:06.298 align:start position:0% the X so if we pop this into our 09:01:06.298 --> 09:01:08.868 align:start position:0% the X so if we pop this into our equation<09:01:06.660> the<09:01:07.558> number<09:01:07.680> of<09:01:07.860> possible<09:01:08.280> hosts<09:01:08.760> we 09:01:08.868 --> 09:01:08.878 align:start position:0% equation the number of possible hosts we 09:01:08.878 --> 09:01:11.868 align:start position:0% equation the number of possible hosts we have<09:01:09.058> is<09:01:09.240> 254<09:01:10.200> and<09:01:11.040> the<09:01:11.280> number<09:01:11.398> of<09:01:11.580> possible 09:01:11.868 --> 09:01:11.878 align:start position:0% have is 254 and the number of possible 09:01:11.878 --> 09:01:14.570 align:start position:0% have is 254 and the number of possible networks<09:01:12.420> is<09:01:12.780> over<09:01:13.080> 16<09:01:13.440> million<09:01:13.978> if<09:01:14.280> we<09:01:14.398> go 09:01:14.570 --> 09:01:14.580 align:start position:0% networks is over 16 million if we go 09:01:14.580 --> 09:01:16.368 align:start position:0% networks is over 16 million if we go back<09:01:14.700> to<09:01:14.878> that<09:01:15.058> table<09:01:15.298> we<09:01:15.660> saw<09:01:15.780> a<09:01:15.898> few<09:01:16.020> slides 09:01:16.368 --> 09:01:16.378 align:start position:0% back to that table we saw a few slides 09:01:16.378 --> 09:01:19.070 align:start position:0% back to that table we saw a few slides ago<09:01:16.680> we'd<09:01:17.280> see<09:01:17.458> then<09:01:17.700> that<09:01:18.058> that's<09:01:18.478> why<09:01:18.780> we 09:01:19.070 --> 09:01:19.080 align:start position:0% ago we'd see then that that's why we 09:01:19.080 --> 09:01:21.830 align:start position:0% ago we'd see then that that's why we have<09:01:19.260> a<09:01:19.798> default<09:01:20.100> for<09:01:20.398> class<09:01:20.580> B<09:01:20.878> and<09:01:21.298> Class<09:01:21.540> C 09:01:21.830 --> 09:01:21.840 align:start position:0% have a default for class B and Class C 09:01:21.840 --> 09:01:25.010 align:start position:0% have a default for class B and Class C networks<09:01:22.440> is<09:01:23.160> we<09:01:23.818> can<09:01:24.000> see<09:01:24.180> how<09:01:24.420> many<09:01:24.540> networks 09:01:25.010 --> 09:01:25.020 align:start position:0% networks is we can see how many networks 09:01:25.020 --> 09:01:26.510 align:start position:0% networks is we can see how many networks are<09:01:25.138> possible<09:01:25.440> and<09:01:25.680> how<09:01:25.860> many<09:01:26.040> hosts<09:01:26.398> are 09:01:26.510 --> 09:01:26.520 align:start position:0% are possible and how many hosts are 09:01:26.520 --> 09:01:28.548 align:start position:0% are possible and how many hosts are possible<09:01:26.878> now<09:01:27.660> why<09:01:27.840> would<09:01:28.020> I<09:01:28.138> want<09:01:28.260> to<09:01:28.378> know 09:01:28.548 --> 09:01:28.558 align:start position:0% possible now why would I want to know 09:01:28.558 --> 09:01:31.010 align:start position:0% possible now why would I want to know this<09:01:28.860> well<09:01:29.520> let's<09:01:30.120> say<09:01:30.298> that<09:01:30.540> I<09:01:30.780> have<09:01:30.898> to 09:01:31.010 --> 09:01:31.020 align:start position:0% this well let's say that I have to 09:01:31.020 --> 09:01:32.868 align:start position:0% this well let's say that I have to divide<09:01:31.318> up<09:01:31.500> my<09:01:31.740> network<09:01:31.860> and<09:01:32.218> I<09:01:32.398> want<09:01:32.520> to<09:01:32.700> have 09:01:32.868 --> 09:01:32.878 align:start position:0% divide up my network and I want to have 09:01:32.878 --> 09:01:34.490 align:start position:0% divide up my network and I want to have a<09:01:33.180> certain<09:01:33.298> number<09:01:33.540> of<09:01:33.718> networks<09:01:34.138> in<09:01:34.318> a 09:01:34.490 --> 09:01:34.500 align:start position:0% a certain number of networks in a 09:01:34.500 --> 09:01:36.708 align:start position:0% a certain number of networks in a certain<09:01:34.620> number<09:01:34.798> of<09:01:34.978> hosts<09:01:35.458> well<09:01:36.180> if<09:01:36.360> I<09:01:36.540> only 09:01:36.708 --> 09:01:36.718 align:start position:0% certain number of hosts well if I only 09:01:36.718 --> 09:01:39.590 align:start position:0% certain number of hosts well if I only need<09:01:37.020> five<09:01:37.318> networks<09:01:37.920> but<09:01:38.160> I<09:01:38.340> need<09:01:38.520> 30<09:01:39.478> 000 09:01:39.590 --> 09:01:39.600 align:start position:0% need five networks but I need 30 000 09:01:39.600 --> 09:01:41.690 align:start position:0% need five networks but I need 30 000 hosts<09:01:40.138> I'm<09:01:40.620> going<09:01:40.798> to<09:01:40.920> be<09:01:41.040> in<09:01:41.160> major<09:01:41.398> trouble 09:01:41.690 --> 09:01:41.700 align:start position:0% hosts I'm going to be in major trouble 09:01:41.700 --> 09:01:43.368 align:start position:0% hosts I'm going to be in major trouble here<09:01:42.000> because<09:01:42.240> now<09:01:42.478> I<09:01:42.718> have<09:01:42.840> to<09:01:42.958> divide<09:01:43.200> this 09:01:43.368 --> 09:01:43.378 align:start position:0% here because now I have to divide this 09:01:43.378 --> 09:01:45.048 align:start position:0% here because now I have to divide this up<09:01:43.500> so<09:01:43.740> much<09:01:43.860> I'm<09:01:44.040> wasting<09:01:44.458> a<09:01:44.580> lot<09:01:44.638> of<09:01:44.760> networks 09:01:45.048 --> 09:01:45.058 align:start position:0% up so much I'm wasting a lot of networks 09:01:45.058 --> 09:01:47.030 align:start position:0% up so much I'm wasting a lot of networks and<09:01:45.180> I<09:01:45.360> don't<09:01:45.478> have<09:01:45.600> enough<09:01:45.780> hosts<09:01:46.318> so<09:01:46.740> we<09:01:46.860> want 09:01:47.030 --> 09:01:47.040 align:start position:0% and I don't have enough hosts so we want 09:01:47.040 --> 09:01:48.530 align:start position:0% and I don't have enough hosts so we want to<09:01:47.160> determine<09:01:47.520> how<09:01:47.760> we<09:01:47.878> can<09:01:48.000> do<09:01:48.120> this<09:01:48.298> to 09:01:48.530 --> 09:01:48.540 align:start position:0% to determine how we can do this to 09:01:48.540 --> 09:01:50.570 align:start position:0% to determine how we can do this to reduce<09:01:48.718> the<09:01:49.020> amount<09:01:49.260> of<09:01:49.378> waste<09:01:49.798> we're<09:01:50.398> going 09:01:50.570 --> 09:01:50.580 align:start position:0% reduce the amount of waste we're going 09:01:50.580 --> 09:01:52.548 align:start position:0% reduce the amount of waste we're going to<09:01:50.638> talk<09:01:50.760> about<09:01:50.940> that<09:01:51.180> in<09:01:51.360> just<09:01:51.478> a<09:01:51.600> bit 09:01:52.548 --> 09:01:52.558 align:start position:0% to talk about that in just a bit 09:01:52.558 --> 09:01:54.350 align:start position:0% to talk about that in just a bit going<09:01:53.100> back<09:01:53.280> to<09:01:53.458> something<09:01:53.638> called<09:01:53.878> a<09:01:54.058> default 09:01:54.350 --> 09:01:54.360 align:start position:0% going back to something called a default 09:01:54.360 --> 09:01:56.930 align:start position:0% going back to something called a default gateway<09:01:54.718> for<09:01:55.020> a<09:01:55.138> second 09:01:56.930 --> 09:01:56.940 align:start position:0% gateway for a second 09:01:56.940 --> 09:01:59.030 align:start position:0% gateway for a second device<09:01:57.360> that<09:01:57.898> wants<09:01:58.200> to<09:01:58.318> connect<09:01:58.620> to<09:01:58.920> the 09:01:59.030 --> 09:01:59.040 align:start position:0% device that wants to connect to the 09:01:59.040 --> 09:02:01.308 align:start position:0% device that wants to connect to the internet<09:01:59.218> has<09:01:59.760> to<09:02:00.000> go<09:02:00.180> through<09:02:00.718> what's<09:02:00.958> called 09:02:01.308 --> 09:02:01.318 align:start position:0% internet has to go through what's called 09:02:01.318 --> 09:02:03.770 align:start position:0% internet has to go through what's called a<09:02:02.040> default<09:02:02.580> gateway<09:02:03.120> this<09:02:03.360> is<09:02:03.478> not<09:02:03.540> a<09:02:03.718> physical 09:02:03.770 --> 09:02:03.780 align:start position:0% a default gateway this is not a physical 09:02:03.780 --> 09:02:06.530 align:start position:0% a default gateway this is not a physical device<09:02:04.200> this<09:02:04.620> is<09:02:04.798> set<09:02:05.218> by<09:02:05.878> our<09:02:06.058> IP<09:02:06.360> address 09:02:06.530 --> 09:02:06.540 align:start position:0% device this is set by our IP address 09:02:06.540 --> 09:02:09.170 align:start position:0% device this is set by our IP address settings<09:02:06.958> it<09:02:07.740> is<09:02:07.978> basically<09:02:08.280> the<09:02:08.580> IP<09:02:08.940> address 09:02:09.170 --> 09:02:09.180 align:start position:0% settings it is basically the IP address 09:02:09.180 --> 09:02:11.930 align:start position:0% settings it is basically the IP address of<09:02:09.718> the<09:02:09.898> device<09:02:10.080> which<09:02:10.798> is<09:02:10.978> usually<09:02:11.398> the 09:02:11.930 --> 09:02:11.940 align:start position:0% of the device which is usually the 09:02:11.940 --> 09:02:14.208 align:start position:0% of the device which is usually the router<09:02:12.360> or<09:02:13.080> the<09:02:13.318> Border<09:02:13.620> router<09:02:13.978> that's 09:02:14.208 --> 09:02:14.218 align:start position:0% router or the Border router that's 09:02:14.218 --> 09:02:15.770 align:start position:0% router or the Border router that's connected<09:02:14.638> directly<09:02:15.000> to<09:02:15.180> the<09:02:15.360> to<09:02:15.600> the 09:02:15.770 --> 09:02:15.780 align:start position:0% connected directly to the to the 09:02:15.780 --> 09:02:17.208 align:start position:0% connected directly to the to the internet<09:02:15.958> for<09:02:16.440> instance<09:02:16.620> we<09:02:16.798> had<09:02:16.978> other 09:02:17.208 --> 09:02:17.218 align:start position:0% internet for instance we had other 09:02:17.218 --> 09:02:19.150 align:start position:0% internet for instance we had other routers<09:02:17.700> in<09:02:18.058> here 09:02:19.150 --> 09:02:19.160 align:start position:0% routers in here 09:02:19.160 --> 09:02:22.010 align:start position:0% routers in here this<09:02:20.160> is<09:02:20.280> going<09:02:20.398> to<09:02:20.458> be<09:02:20.520> the<09:02:20.700> Gateway 09:02:22.010 --> 09:02:22.020 align:start position:0% this is going to be the Gateway 09:02:22.020 --> 09:02:23.750 align:start position:0% this is going to be the Gateway and<09:02:22.558> so<09:02:22.740> three<09:02:23.040> things<09:02:23.218> need<09:02:23.520> to<09:02:23.638> be 09:02:23.750 --> 09:02:23.760 align:start position:0% and so three things need to be 09:02:23.760 --> 09:02:25.430 align:start position:0% and so three things need to be configured<09:02:24.180> on<09:02:24.478> any<09:02:24.660> device<09:02:24.898> that<09:02:25.138> wants<09:02:25.378> to 09:02:25.430 --> 09:02:25.440 align:start position:0% configured on any device that wants to 09:02:25.440 --> 09:02:26.990 align:start position:0% configured on any device that wants to connect<09:02:25.558> to<09:02:25.798> the<09:02:25.920> internet<09:02:26.100> we've<09:02:26.818> talked 09:02:26.990 --> 09:02:27.000 align:start position:0% connect to the internet we've talked 09:02:27.000 --> 09:02:28.548 align:start position:0% connect to the internet we've talked about<09:02:27.120> it<09:02:27.240> we<09:02:27.420> need<09:02:27.540> to<09:02:27.660> have<09:02:27.780> an<09:02:27.898> IP<09:02:28.138> address<09:02:28.318> a 09:02:28.548 --> 09:02:28.558 align:start position:0% about it we need to have an IP address a 09:02:28.558 --> 09:02:30.650 align:start position:0% about it we need to have an IP address a subnet<09:02:28.978> mask<09:02:29.100> and<09:02:29.280> this<09:02:29.458> is<09:02:29.520> the<09:02:29.638> new<09:02:29.760> one<09:02:29.940> a 09:02:30.650 --> 09:02:30.660 align:start position:0% subnet mask and this is the new one a 09:02:30.660 --> 09:02:33.230 align:start position:0% subnet mask and this is the new one a default<09:02:31.020> gateway<09:02:31.500> so<09:02:32.280> this<09:02:32.458> is<09:02:32.638> the<09:02:32.940> device 09:02:33.230 --> 09:02:33.240 align:start position:0% default gateway so this is the device 09:02:33.240 --> 09:02:35.690 align:start position:0% default gateway so this is the device that's<09:02:33.718> used<09:02:34.080> when<09:02:34.500> I<09:02:34.798> want<09:02:34.978> to<09:02:35.100> communicate 09:02:35.690 --> 09:02:35.700 align:start position:0% that's used when I want to communicate 09:02:35.700 --> 09:02:38.030 align:start position:0% that's used when I want to communicate with<09:02:36.000> the<09:02:36.120> internet<09:02:36.240> and<09:02:37.020> it's<09:02:37.138> not<09:02:37.440> used<09:02:37.680> when 09:02:38.030 --> 09:02:38.040 align:start position:0% with the internet and it's not used when 09:02:38.040 --> 09:02:40.670 align:start position:0% with the internet and it's not used when communicating<09:02:38.580> with<09:02:39.000> devices<09:02:39.360> on<09:02:40.318> the<09:02:40.500> same 09:02:40.670 --> 09:02:40.680 align:start position:0% communicating with devices on the same 09:02:40.680 --> 09:02:43.368 align:start position:0% communicating with devices on the same subnet<09:02:41.218> this<09:02:41.458> is<09:02:41.580> why<09:02:41.760> it's<09:02:41.940> called<09:02:42.180> a<09:02:42.478> Gateway 09:02:43.368 --> 09:02:43.378 align:start position:0% subnet this is why it's called a Gateway 09:02:43.378 --> 09:02:44.990 align:start position:0% subnet this is why it's called a Gateway think<09:02:43.680> about<09:02:43.798> it<09:02:43.978> as<09:02:44.100> your<09:02:44.280> gateway<09:02:44.638> out<09:02:44.818> to 09:02:44.990 --> 09:02:45.000 align:start position:0% think about it as your gateway out to 09:02:45.000 --> 09:02:47.090 align:start position:0% think about it as your gateway out to the<09:02:45.120> network<09:02:45.240> most<09:02:46.138> often<09:02:46.500> and<09:02:46.680> more<09:02:46.860> often 09:02:47.090 --> 09:02:47.100 align:start position:0% the network most often and more often 09:02:47.100 --> 09:02:48.708 align:start position:0% the network most often and more often than<09:02:47.280> not<09:02:47.458> as<09:02:47.818> I<09:02:48.000> mentioned<09:02:48.240> this<09:02:48.420> is<09:02:48.540> going<09:02:48.660> to 09:02:48.708 --> 09:02:48.718 align:start position:0% than not as I mentioned this is going to 09:02:48.718 --> 09:02:50.990 align:start position:0% than not as I mentioned this is going to be<09:02:48.840> the<09:02:49.020> router<09:02:49.440> so<09:02:49.920> if<09:02:50.040> you<09:02:50.160> have<09:02:50.340> at<09:02:50.520> home<09:02:50.700> for 09:02:50.990 --> 09:02:51.000 align:start position:0% be the router so if you have at home for 09:02:51.000 --> 09:02:53.288 align:start position:0% be the router so if you have at home for instance<09:02:51.298> a<09:02:52.138> router<09:02:52.500> that's 09:02:53.288 --> 09:02:53.298 align:start position:0% instance a router that's 09:02:53.298 --> 09:02:55.910 align:start position:0% instance a router that's 192.168.0.1<09:02:54.298> that<09:02:54.958> is<09:02:55.080> also<09:02:55.378> your<09:02:55.620> default 09:02:55.910 --> 09:02:55.920 align:start position:0% 192.168.0.1 that is also your default 09:02:55.920 --> 09:02:58.490 align:start position:0% 192.168.0.1 that is also your default gateway<09:02:56.878> and<09:02:57.360> if<09:02:57.478> you<09:02:57.660> went<09:02:57.780> and<09:02:57.958> did<09:02:58.260> an 09:02:58.490 --> 09:02:58.500 align:start position:0% gateway and if you went and did an 09:02:58.500 --> 09:03:00.410 align:start position:0% gateway and if you went and did an ipconfig<09:02:59.280> all<09:02:59.520> something<09:02:59.818> we'll<09:03:00.000> take<09:03:00.180> a<09:03:00.298> look 09:03:00.410 --> 09:03:00.420 align:start position:0% ipconfig all something we'll take a look 09:03:00.420 --> 09:03:03.048 align:start position:0% ipconfig all something we'll take a look at<09:03:00.600> later<09:03:00.898> and<09:03:01.558> command<09:03:01.978> prompt<09:03:02.340> you'd<09:03:03.000> be 09:03:03.048 --> 09:03:03.058 align:start position:0% at later and command prompt you'd be 09:03:03.058 --> 09:03:06.288 align:start position:0% at later and command prompt you'd be able<09:03:03.298> to<09:03:03.478> see<09:03:03.898> then<09:03:04.398> your<09:03:05.398> default<09:03:05.638> gateway<09:03:06.000> is 09:03:06.288 --> 09:03:06.298 align:start position:0% able to see then your default gateway is 09:03:06.298 --> 09:03:08.090 align:start position:0% able to see then your default gateway is this<09:03:06.478> address<09:03:06.718> basically<09:03:07.318> it<09:03:07.500> means<09:03:07.680> hey<09:03:07.860> I 09:03:08.090 --> 09:03:08.100 align:start position:0% this address basically it means hey I 09:03:08.100 --> 09:03:09.410 align:start position:0% this address basically it means hey I don't<09:03:08.218> know<09:03:08.398> I<09:03:08.818> want<09:03:08.940> to<09:03:09.000> get<09:03:09.058> up<09:03:09.180> to<09:03:09.298> the 09:03:09.410 --> 09:03:09.420 align:start position:0% don't know I want to get up to the 09:03:09.420 --> 09:03:10.368 align:start position:0% don't know I want to get up to the internet<09:03:09.540> I<09:03:09.718> don't<09:03:09.840> know<09:03:09.958> how<09:03:10.020> to<09:03:10.138> get<09:03:10.260> to 09:03:10.368 --> 09:03:10.378 align:start position:0% internet I don't know how to get to 09:03:10.378 --> 09:03:12.170 align:start position:0% internet I don't know how to get to Google<09:03:10.558> I'm<09:03:11.218> going<09:03:11.340> to<09:03:11.458> ask<09:03:11.580> my<09:03:11.818> default 09:03:12.170 --> 09:03:12.180 align:start position:0% Google I'm going to ask my default 09:03:12.180 --> 09:03:14.208 align:start position:0% Google I'm going to ask my default gateway<09:03:12.600> the<09:03:13.138> default<09:03:13.378> gateway<09:03:13.740> then<09:03:13.920> takes 09:03:14.208 --> 09:03:14.218 align:start position:0% gateway the default gateway then takes 09:03:14.218 --> 09:03:16.308 align:start position:0% gateway the default gateway then takes care<09:03:14.340> of<09:03:14.520> everything<09:03:14.638> else<09:03:15.058> and<09:03:15.958> then<09:03:16.080> the 09:03:16.308 --> 09:03:16.318 align:start position:0% care of everything else and then the 09:03:16.318 --> 09:03:18.590 align:start position:0% care of everything else and then the information<09:03:16.500> comes<09:03:17.100> back<09:03:17.218> and<09:03:18.120> it<09:03:18.240> sends<09:03:18.540> it 09:03:18.590 --> 09:03:18.600 align:start position:0% information comes back and it sends it 09:03:18.600 --> 09:03:20.510 align:start position:0% information comes back and it sends it out<09:03:18.718> to<09:03:18.898> you<09:03:19.020> again<09:03:19.260> now<09:03:20.100> there<09:03:20.280> are<09:03:20.398> a<09:03:20.458> couple 09:03:20.510 --> 09:03:20.520 align:start position:0% out to you again now there are a couple 09:03:20.520 --> 09:03:23.270 align:start position:0% out to you again now there are a couple different<09:03:20.760> ways<09:03:21.240> of<09:03:21.718> implementing<09:03:22.318> custom<09:03:22.680> IP 09:03:23.270 --> 09:03:23.280 align:start position:0% different ways of implementing custom IP 09:03:23.280 --> 09:03:25.850 align:start position:0% different ways of implementing custom IP addresses<09:03:23.818> we<09:03:24.540> previously<09:03:24.958> described<09:03:25.440> how<09:03:25.620> we 09:03:25.850 --> 09:03:25.860 align:start position:0% addresses we previously described how we 09:03:25.860 --> 09:03:28.070 align:start position:0% addresses we previously described how we could<09:03:25.920> use<09:03:26.100> custom<09:03:26.398> subnets<09:03:27.058> and<09:03:27.718> with<09:03:27.898> that 09:03:28.070 --> 09:03:28.080 align:start position:0% could use custom subnets and with that 09:03:28.080 --> 09:03:31.010 align:start position:0% could use custom subnets and with that method<09:03:28.558> a<09:03:29.218> custom<09:03:29.340> subnet<09:03:30.000> mask<09:03:30.298> and<09:03:30.600> an<09:03:30.780> IP 09:03:31.010 --> 09:03:31.020 align:start position:0% method a custom subnet mask and an IP 09:03:31.020 --> 09:03:33.110 align:start position:0% method a custom subnet mask and an IP address<09:03:31.138> is<09:03:31.440> what<09:03:31.620> we<09:03:31.680> call<09:03:31.860> anded<09:03:32.580> if<09:03:32.940> you 09:03:33.110 --> 09:03:33.120 align:start position:0% address is what we call anded if you 09:03:33.120 --> 09:03:36.288 align:start position:0% address is what we call anded if you recall<09:03:33.740> and<09:03:34.740> together<09:03:35.218> they<09:03:35.520> allow<09:03:35.818> the<09:03:36.000> node 09:03:36.288 --> 09:03:36.298 align:start position:0% recall and together they allow the node 09:03:36.298 --> 09:03:38.690 align:start position:0% recall and together they allow the node to<09:03:36.600> see<09:03:36.718> the<09:03:36.898> local<09:03:37.020> network<09:03:37.378> as<09:03:38.040> part<09:03:38.218> of<09:03:38.340> its 09:03:38.690 --> 09:03:38.700 align:start position:0% to see the local network as part of its 09:03:38.700 --> 09:03:41.270 align:start position:0% to see the local network as part of its larger<09:03:39.000> Network<09:03:39.540> now<09:03:40.138> each<09:03:40.500> customized 09:03:41.270 --> 09:03:41.280 align:start position:0% larger Network now each customized 09:03:41.280 --> 09:03:43.670 align:start position:0% larger Network now each customized subnet<09:03:41.818> is<09:03:42.420> configured<09:03:42.840> with<09:03:43.138> its<09:03:43.500> own 09:03:43.670 --> 09:03:43.680 align:start position:0% subnet is configured with its own 09:03:43.680 --> 09:03:46.968 align:start position:0% subnet is configured with its own default<09:03:44.398> gateway<09:03:44.958> allowing<09:03:45.958> the<09:03:46.200> subnets<09:03:46.558> to 09:03:46.968 --> 09:03:46.978 align:start position:0% default gateway allowing the subnets to 09:03:46.978 --> 09:03:49.368 align:start position:0% default gateway allowing the subnets to be<09:03:47.100> able<09:03:47.280> to<09:03:47.398> communicate<09:03:47.878> with<09:03:48.298> each<09:03:48.540> other 09:03:49.368 --> 09:03:49.378 align:start position:0% be able to communicate with each other 09:03:49.378 --> 09:03:51.230 align:start position:0% be able to communicate with each other now<09:03:49.860> another<09:03:50.100> method<09:03:50.520> of<09:03:50.638> doing<09:03:50.760> this<09:03:51.000> is 09:03:51.230 --> 09:03:51.240 align:start position:0% now another method of doing this is 09:03:51.240 --> 09:03:56.990 align:start position:0% now another method of doing this is called<09:03:51.500> vlsm<09:03:52.700> or<09:03:53.700> variable 09:03:56.990 --> 09:03:57.000 align:start position:0% 09:03:57.000 --> 09:04:00.350 align:start position:0% length 09:04:00.350 --> 09:04:00.360 align:start position:0% 09:04:00.360 --> 09:04:03.170 align:start position:0% subnet 09:04:03.170 --> 09:04:03.180 align:start position:0% 09:04:03.180 --> 09:04:05.808 align:start position:0% mask 09:04:05.808 --> 09:04:05.818 align:start position:0% mask 09:04:05.818 --> 09:04:08.030 align:start position:0% mask and<09:04:06.540> by<09:04:06.718> using<09:04:07.020> this<09:04:07.200> we're<09:04:07.440> going<09:04:07.558> to<09:04:07.680> assign 09:04:08.030 --> 09:04:08.040 align:start position:0% and by using this we're going to assign 09:04:08.040 --> 09:04:11.628 align:start position:0% and by using this we're going to assign each<09:04:08.520> subnet<09:04:09.058> its<09:04:09.958> own<09:04:10.080> separate<09:04:10.740> customized 09:04:11.628 --> 09:04:11.638 align:start position:0% each subnet its own separate customized 09:04:11.638 --> 09:04:14.150 align:start position:0% each subnet its own separate customized subnet<09:04:12.180> mask<09:04:12.360> that<09:04:13.138> varies 09:04:14.150 --> 09:04:14.160 align:start position:0% subnet mask that varies 09:04:14.160 --> 09:04:16.910 align:start position:0% subnet mask that varies now<09:04:14.638> the<09:04:14.818> VLS<09:04:15.240> MF<09:04:15.600> it<09:04:15.840> allows<09:04:16.138> for<09:04:16.378> a<09:04:16.740> more 09:04:16.910 --> 09:04:16.920 align:start position:0% now the VLS MF it allows for a more 09:04:16.920 --> 09:04:19.070 align:start position:0% now the VLS MF it allows for a more efficient<09:04:17.340> allocation<09:04:17.940> of<09:04:18.240> IP<09:04:18.600> addresses 09:04:19.070 --> 09:04:19.080 align:start position:0% efficient allocation of IP addresses 09:04:19.080 --> 09:04:21.770 align:start position:0% efficient allocation of IP addresses with<09:04:19.740> minimal<09:04:20.160> address<09:04:20.760> waste<09:04:21.360> which<09:04:21.540> I<09:04:21.660> was 09:04:21.770 --> 09:04:21.780 align:start position:0% with minimal address waste which I was 09:04:21.780 --> 09:04:23.690 align:start position:0% with minimal address waste which I was just<09:04:21.958> talking<09:04:22.200> about<09:04:22.378> so<09:04:23.040> for<09:04:23.218> example<09:04:23.458> let's 09:04:23.690 --> 09:04:23.700 align:start position:0% just talking about so for example let's 09:04:23.700 --> 09:04:26.150 align:start position:0% just talking about so for example let's take<09:04:23.878> a<09:04:24.058> situation<09:04:24.500> in<09:04:25.500> which<09:04:25.740> a<09:04:26.040> network 09:04:26.150 --> 09:04:26.160 align:start position:0% take a situation in which a network 09:04:26.160 --> 09:04:28.010 align:start position:0% take a situation in which a network administrator<09:04:26.760> wants<09:04:27.120> to<09:04:27.240> have<09:04:27.420> three 09:04:28.010 --> 09:04:28.020 align:start position:0% administrator wants to have three 09:04:28.020 --> 09:04:30.350 align:start position:0% administrator wants to have three networks<09:04:28.500> and<09:04:28.740> I<09:04:28.860> have<09:04:29.040> a<09:04:29.280> class 09:04:30.350 --> 09:04:30.360 align:start position:0% networks and I have a class 09:04:30.360 --> 09:04:32.448 align:start position:0% networks and I have a class c<09:04:30.780> space 09:04:32.448 --> 09:04:32.458 align:start position:0% c space 09:04:32.458 --> 09:04:35.708 align:start position:0% c space now<09:04:32.940> just<09:04:33.240> so<09:04:33.360> you<09:04:33.540> know<09:04:33.660> some<09:04:34.080> of<09:04:34.260> this<09:04:34.700> is 09:04:35.708 --> 09:04:35.718 align:start position:0% now just so you know some of this is 09:04:35.718 --> 09:04:38.030 align:start position:0% now just so you know some of this is very<09:04:36.718> outdated<09:04:37.138> and<09:04:37.378> we're<09:04:37.500> not<09:04:37.620> going<09:04:37.798> to<09:04:37.920> see 09:04:38.030 --> 09:04:38.040 align:start position:0% very outdated and we're not going to see 09:04:38.040 --> 09:04:40.010 align:start position:0% very outdated and we're not going to see it<09:04:38.218> used<09:04:38.458> a<09:04:38.818> lot<09:04:38.940> of<09:04:39.058> the<09:04:39.180> time<09:04:39.298> that<09:04:39.840> being 09:04:40.010 --> 09:04:40.020 align:start position:0% it used a lot of the time that being 09:04:40.020 --> 09:04:41.808 align:start position:0% it used a lot of the time that being said<09:04:40.318> Network<09:04:40.620> plus<09:04:40.978> really<09:04:41.280> wants<09:04:41.580> you<09:04:41.638> to 09:04:41.808 --> 09:04:41.818 align:start position:0% said Network plus really wants you to 09:04:41.818 --> 09:04:43.670 align:start position:0% said Network plus really wants you to know<09:04:41.940> about<09:04:42.058> it<09:04:42.240> so<09:04:42.420> we're<09:04:42.600> going<09:04:42.718> to<09:04:42.840> cover<09:04:42.958> it 09:04:43.670 --> 09:04:43.680 align:start position:0% know about it so we're going to cover it 09:04:43.680 --> 09:04:45.888 align:start position:0% know about it so we're going to cover it so<09:04:44.280> I<09:04:44.580> know<09:04:44.700> I<09:04:44.878> need<09:04:45.000> to<09:04:45.120> have<09:04:45.298> three<09:04:45.660> different 09:04:45.888 --> 09:04:45.898 align:start position:0% so I know I need to have three different 09:04:45.898 --> 09:04:48.230 align:start position:0% so I know I need to have three different networks<09:04:46.500> or<09:04:46.620> sub<09:04:46.798> Networks<09:04:47.340> and<09:04:47.818> I<09:04:47.878> know<09:04:48.000> on 09:04:48.230 --> 09:04:48.240 align:start position:0% networks or sub Networks and I know on 09:04:48.240 --> 09:04:50.628 align:start position:0% networks or sub Networks and I know on the<09:04:48.360> first<09:04:48.478> Network<09:04:48.780> I<09:04:49.740> want<09:04:49.920> to<09:04:50.040> have<09:04:50.218> four 09:04:50.628 --> 09:04:50.638 align:start position:0% the first Network I want to have four 09:04:50.638 --> 09:04:52.308 align:start position:0% the first Network I want to have four hosts<09:04:51.120> on<09:04:51.240> the<09:04:51.360> set<09:04:51.478> network<09:04:51.780> I<09:04:52.020> want<09:04:52.200> to<09:04:52.260> have 09:04:52.308 --> 09:04:52.318 align:start position:0% hosts on the set network I want to have 09:04:52.318 --> 09:04:54.170 align:start position:0% hosts on the set network I want to have 11<09:04:52.440> hosts<09:04:52.978> and<09:04:53.160> on<09:04:53.280> the<09:04:53.398> third<09:04:53.520> network<09:04:53.760> I<09:04:54.000> want 09:04:54.170 --> 09:04:54.180 align:start position:0% 11 hosts and on the third network I want 09:04:54.180 --> 09:04:57.048 align:start position:0% 11 hosts and on the third network I want to<09:04:54.298> have<09:04:54.478> 27<09:04:55.378> hosts<09:04:55.920> now<09:04:56.520> in<09:04:56.760> order<09:04:56.940> to 09:04:57.048 --> 09:04:57.058 align:start position:0% to have 27 hosts now in order to 09:04:57.058 --> 09:04:58.968 align:start position:0% to have 27 hosts now in order to accomplish<09:04:57.600> this<09:04:57.780> I<09:04:58.080> could<09:04:58.200> use<09:04:58.378> the<09:04:58.558> subnet 09:04:58.968 --> 09:04:58.978 align:start position:0% accomplish this I could use the subnet 09:04:58.978 --> 09:04:59.708 align:start position:0% accomplish this I could use the subnet mask 09:04:59.708 --> 09:04:59.718 align:start position:0% mask 09:04:59.718 --> 09:05:03.770 align:start position:0% mask 255.255<09:05:00.718> the<09:05:00.898> 255.20<09:05:01.798> that<09:05:02.218> 224. 09:05:03.770 --> 09:05:03.780 align:start position:0% 255.255 the 255.20 that 224. 09:05:03.780 --> 09:05:06.468 align:start position:0% 255.255 the 255.20 that 224. and<09:05:04.200> for<09:05:04.378> each<09:05:04.558> of<09:05:04.740> these<09:05:04.978> subnets<09:05:05.458> if<09:05:06.180> I<09:05:06.360> was 09:05:06.468 --> 09:05:06.478 align:start position:0% and for each of these subnets if I was 09:05:06.478 --> 09:05:09.230 align:start position:0% and for each of these subnets if I was to<09:05:06.660> add<09:05:07.020> this<09:05:07.200> out<09:05:07.440> right<09:05:07.740> one<09:05:08.100> two<09:05:08.398> three<09:05:08.818> four 09:05:09.230 --> 09:05:09.240 align:start position:0% to add this out right one two three four 09:05:09.240 --> 09:05:12.770 align:start position:0% to add this out right one two three four five<09:05:09.660> six<09:05:10.080> seven<09:05:10.440> eight<09:05:10.740> that's<09:05:11.340> 255<09:05:12.000> one<09:05:12.478> two 09:05:12.770 --> 09:05:12.780 align:start position:0% five six seven eight that's 255 one two 09:05:12.780 --> 09:05:15.650 align:start position:0% five six seven eight that's 255 one two three<09:05:13.138> four<09:05:13.500> five<09:05:13.920> six<09:05:14.280> seven<09:05:14.638> eight 09:05:15.650 --> 09:05:15.660 align:start position:0% three four five six seven eight 09:05:15.660 --> 09:05:18.948 align:start position:0% three four five six seven eight that's<09:05:16.080> 255<09:05:16.740> one<09:05:17.218> two<09:05:17.520> three<09:05:17.878> four<09:05:18.298> five<09:05:18.600> six 09:05:18.948 --> 09:05:18.958 align:start position:0% that's 255 one two three four five six 09:05:18.958 --> 09:05:22.190 align:start position:0% that's 255 one two three four five six seven<09:05:19.260> eight<09:05:19.500> that's<09:05:19.920> 255<09:05:20.520> let's<09:05:21.000> write<09:05:21.240> 224 09:05:22.190 --> 09:05:22.200 align:start position:0% seven eight that's 255 let's write 224 09:05:22.200 --> 09:05:24.590 align:start position:0% seven eight that's 255 let's write 224 in<09:05:22.500> bits<09:05:22.920> all<09:05:23.520> right<09:05:23.638> let's<09:05:24.000> go<09:05:24.240> through<09:05:24.360> our 09:05:24.590 --> 09:05:24.600 align:start position:0% in bits all right let's go through our 09:05:24.600 --> 09:05:26.628 align:start position:0% in bits all right let's go through our calculation<09:05:25.138> again<09:05:25.440> here<09:05:25.798> I'm<09:05:26.280> just<09:05:26.398> going<09:05:26.580> to 09:05:26.628 --> 09:05:26.638 align:start position:0% calculation again here I'm just going to 09:05:26.638 --> 09:05:28.788 align:start position:0% calculation again here I'm just going to do<09:05:26.818> this<09:05:27.000> because<09:05:27.240> it<09:05:27.540> never<09:05:27.718> hurts 09:05:28.788 --> 09:05:28.798 align:start position:0% do this because it never hurts 09:05:28.798 --> 09:05:31.430 align:start position:0% do this because it never hurts to<09:05:29.280> do<09:05:29.398> this<09:05:29.580> a<09:05:29.760> couple<09:05:29.878> times 09:05:31.430 --> 09:05:31.440 align:start position:0% to do this a couple times 09:05:31.440 --> 09:05:38.990 align:start position:0% to do this a couple times so<09:05:31.978> let's<09:05:32.100> write<09:05:32.398> all<09:05:32.700> of<09:05:32.818> these<09:05:33.058> out 09:05:38.990 --> 09:05:39.000 align:start position:0% 09:05:39.000 --> 09:05:43.430 align:start position:0% great<09:05:39.478> all<09:05:39.718> right<09:05:39.898> we<09:05:40.080> have<09:05:40.200> one<09:05:40.798> two<09:05:41.638> four 09:05:43.430 --> 09:05:43.440 align:start position:0% great all right we have one two four 09:05:43.440 --> 09:05:46.368 align:start position:0% great all right we have one two four eight<09:05:44.600> sixteen 09:05:46.368 --> 09:05:46.378 align:start position:0% eight sixteen 09:05:46.378 --> 09:05:50.808 align:start position:0% eight sixteen 32<09:05:47.540> 64<09:05:48.540> 128. 09:05:50.808 --> 09:05:50.818 align:start position:0% 32 64 128. 09:05:50.818 --> 09:05:53.750 align:start position:0% 32 64 128. now<09:05:51.298> we<09:05:51.540> remember<09:05:51.780> that<09:05:52.260> subnet<09:05:52.740> masks<09:05:53.218> have 09:05:53.750 --> 09:05:53.760 align:start position:0% now we remember that subnet masks have 09:05:53.760 --> 09:05:56.708 align:start position:0% now we remember that subnet masks have to<09:05:53.940> have<09:05:54.058> continuous<09:05:54.540> ones<09:05:55.020> so<09:05:55.740> that's<09:05:55.920> 128 09:05:56.708 --> 09:05:56.718 align:start position:0% to have continuous ones so that's 128 09:05:56.718 --> 09:06:00.968 align:start position:0% to have continuous ones so that's 128 128<09:05:57.718> plus<09:05:58.020> 64<09:05:58.680> is 09:06:00.968 --> 09:06:00.978 align:start position:0% 128 plus 64 is 09:06:00.978 --> 09:06:05.150 align:start position:0% 128 plus 64 is 192<09:06:02.360> plus<09:06:03.360> 32 09:06:05.150 --> 09:06:05.160 align:start position:0% 192 plus 32 09:06:05.160 --> 09:06:07.850 align:start position:0% 192 plus 32 is<09:06:05.700> 224. 09:06:07.850 --> 09:06:07.860 align:start position:0% is 224. 09:06:07.860 --> 09:06:10.190 align:start position:0% is 224. so<09:06:08.460> then<09:06:08.700> if<09:06:08.878> we<09:06:09.058> broke<09:06:09.300> this<09:06:09.480> down<09:06:09.660> into<09:06:09.782> bits 09:06:10.190 --> 09:06:10.200 align:start position:0% so then if we broke this down into bits 09:06:10.200 --> 09:06:12.112 align:start position:0% so then if we broke this down into bits this<09:06:10.378> is<09:06:10.500> what<09:06:10.622> it's<09:06:10.738> going<09:06:10.860> to<09:06:10.980> look<09:06:11.098> like 09:06:12.112 --> 09:06:12.122 align:start position:0% this is what it's going to look like 09:06:12.122 --> 09:06:13.970 align:start position:0% this is what it's going to look like okay 09:06:13.970 --> 09:06:13.980 align:start position:0% okay 09:06:13.980 --> 09:06:21.830 align:start position:0% okay so<09:06:14.878> let's<09:06:15.180> write<09:06:15.360> that<09:06:15.540> out<09:06:15.718> here 09:06:21.830 --> 09:06:21.840 align:start position:0% 09:06:21.840 --> 09:06:24.530 align:start position:0% and<09:06:22.078> if<09:06:22.258> we<09:06:22.378> do<09:06:22.558> our<09:06:22.738> calculation<09:06:23.398> we<09:06:24.122> know<09:06:24.300> we 09:06:24.530 --> 09:06:24.540 align:start position:0% and if we do our calculation we know we 09:06:24.540 --> 09:06:26.690 align:start position:0% and if we do our calculation we know we need<09:06:24.660> to<09:06:24.782> have<09:06:24.960> how<09:06:25.258> many<09:06:25.378> hosts<09:06:25.860> when<09:06:26.398> we<09:06:26.578> need 09:06:26.690 --> 09:06:26.700 align:start position:0% need to have how many hosts when we need 09:06:26.700 --> 09:06:30.470 align:start position:0% need to have how many hosts when we need four<09:06:26.938> so<09:06:27.840> let's<09:06:28.622> do<09:06:28.800> our<09:06:28.980> calculation<09:06:29.520> 2<09:06:30.238> to 09:06:30.470 --> 09:06:30.480 align:start position:0% four so let's do our calculation 2 to 09:06:30.480 --> 09:06:35.690 align:start position:0% four so let's do our calculation 2 to the<09:06:30.598> 1<09:06:31.500> 2<09:06:31.980> 3<09:06:32.460> 4<09:06:32.878> 5<09:06:33.180> power 09:06:35.690 --> 09:06:35.700 align:start position:0% 09:06:35.700 --> 09:06:37.010 align:start position:0% right 09:06:37.010 --> 09:06:37.020 align:start position:0% right 09:06:37.020 --> 09:06:38.690 align:start position:0% right we're<09:06:37.438> going<09:06:37.558> to<09:06:37.622> figure<09:06:37.738> out<09:06:37.860> how<09:06:38.098> many<09:06:38.218> hosts 09:06:38.690 --> 09:06:38.700 align:start position:0% we're going to figure out how many hosts 09:06:38.700 --> 09:06:42.112 align:start position:0% we're going to figure out how many hosts that<09:06:39.598> equals<09:06:40.020> we<09:06:40.200> already<09:06:40.320> know<09:06:40.500> it's<09:06:40.738> 32. 09:06:42.112 --> 09:06:42.122 align:start position:0% that equals we already know it's 32. 09:06:42.122 --> 09:06:45.290 align:start position:0% that equals we already know it's 32. minus<09:06:42.898> 2<09:06:43.140> means<09:06:44.040> that<09:06:44.160> we<09:06:44.340> can<09:06:44.460> have 09:06:45.290 --> 09:06:45.300 align:start position:0% minus 2 means that we can have 09:06:45.300 --> 09:06:50.990 align:start position:0% minus 2 means that we can have up<09:06:45.718> to<09:06:45.960> 30<09:06:46.258> hosts<09:06:46.980> on<09:06:47.398> this<09:06:47.578> subnet 09:06:50.990 --> 09:06:51.000 align:start position:0% 09:06:51.000 --> 09:06:55.068 align:start position:0% so<09:06:51.598> I'm<09:06:52.500> wasting<09:06:53.040> an<09:06:53.218> effect<09:06:53.398> 26<09:06:54.238> addresses<09:06:54.898> on 09:06:55.068 --> 09:06:55.078 align:start position:0% so I'm wasting an effect 26 addresses on 09:06:55.078 --> 09:06:58.130 align:start position:0% so I'm wasting an effect 26 addresses on this<09:06:55.200> subnet<09:06:55.558> 19<09:06:56.098> on<09:06:56.520> this<09:06:56.700> one<09:06:56.820> and<09:06:57.598> three<09:06:57.840> on 09:06:58.130 --> 09:06:58.140 align:start position:0% this subnet 19 on this one and three on 09:06:58.140 --> 09:07:00.650 align:start position:0% this subnet 19 on this one and three on this<09:06:58.320> one<09:06:58.438> I'm<09:06:58.680> not<09:06:58.918> really<09:06:59.218> doing<09:06:59.520> a<09:07:00.180> good<09:07:00.360> job 09:07:00.650 --> 09:07:00.660 align:start position:0% this one I'm not really doing a good job 09:07:00.660 --> 09:07:02.510 align:start position:0% this one I'm not really doing a good job because<09:07:01.020> I've<09:07:01.258> had<09:07:01.438> to<09:07:01.622> apply<09:07:01.980> the<09:07:02.340> same 09:07:02.510 --> 09:07:02.520 align:start position:0% because I've had to apply the same 09:07:02.520 --> 09:07:04.068 align:start position:0% because I've had to apply the same subnet<09:07:03.122> mask 09:07:04.068 --> 09:07:04.078 align:start position:0% subnet mask 09:07:04.078 --> 09:07:06.530 align:start position:0% subnet mask to<09:07:04.860> every<09:07:05.282> single 09:07:06.530 --> 09:07:06.540 align:start position:0% to every single 09:07:06.540 --> 09:07:08.330 align:start position:0% to every single IP<09:07:07.200> address 09:07:08.330 --> 09:07:08.340 align:start position:0% IP address 09:07:08.340 --> 09:07:10.790 align:start position:0% IP address and<09:07:08.820> in<09:07:09.000> doing<09:07:09.122> so<09:07:09.300> I'm<09:07:09.540> wasting<09:07:10.020> a<09:07:10.140> lot<09:07:10.258> of<09:07:10.438> my 09:07:10.790 --> 09:07:10.800 align:start position:0% and in doing so I'm wasting a lot of my 09:07:10.800 --> 09:07:12.772 align:start position:0% and in doing so I'm wasting a lot of my possible<09:07:11.340> addresses 09:07:12.772 --> 09:07:12.782 align:start position:0% possible addresses 09:07:12.782 --> 09:07:16.190 align:start position:0% possible addresses now<09:07:13.200> if<09:07:13.320> I<09:07:13.500> used<09:07:13.622> vlsm<09:07:14.578> instead<09:07:15.540> it's<09:07:15.960> going<09:07:16.200> to 09:07:16.190 --> 09:07:16.200 align:start position:0% now if I used vlsm instead it's going to 09:07:16.200 --> 09:07:17.690 align:start position:0% now if I used vlsm instead it's going to erase<09:07:16.500> all<09:07:16.680> this 09:07:17.690 --> 09:07:17.700 align:start position:0% erase all this 09:07:17.700 --> 09:07:20.588 align:start position:0% erase all this I<09:07:18.180> could<09:07:18.238> do 09:07:20.588 --> 09:07:20.598 align:start position:0% 09:07:20.598 --> 09:07:24.772 align:start position:0% 255.255.248.240<09:07:21.800> and.224.<09:07:22.800> now<09:07:23.398> remember<09:07:23.782> uh 09:07:24.772 --> 09:07:24.782 align:start position:0% 255.255.248.240 and.224. now remember uh 09:07:24.782 --> 09:07:26.568 align:start position:0% 255.255.248.240 and.224. now remember uh 248 09:07:26.568 --> 09:07:26.578 align:start position:0% 248 09:07:26.578 --> 09:07:28.428 align:start position:0% 248 if<09:07:26.938> we<09:07:27.058> route<09:07:27.300> that<09:07:27.540> out 09:07:28.428 --> 09:07:28.438 align:start position:0% if we route that out 09:07:28.438 --> 09:07:30.408 align:start position:0% if we route that out I'm<09:07:28.860> just<09:07:29.098> gonna 09:07:30.408 --> 09:07:30.418 align:start position:0% I'm just gonna 09:07:30.418 --> 09:07:53.928 align:start position:0% I'm just gonna really<09:07:30.898> quickly 09:07:53.928 --> 09:07:53.938 align:start position:0% 09:07:53.938 --> 09:07:55.728 align:start position:0% all<09:07:54.540> right<09:07:54.598> and<09:07:54.898> you<09:07:55.020> can<09:07:55.140> double<09:07:55.258> check<09:07:55.500> my 09:07:55.728 --> 09:07:55.738 align:start position:0% all right and you can double check my 09:07:55.738 --> 09:07:56.868 align:start position:0% all right and you can double check my math<09:07:55.918> here 09:07:56.868 --> 09:07:56.878 align:start position:0% math here 09:07:56.878 --> 09:08:00.772 align:start position:0% math here if<09:07:57.300> we<09:07:57.418> do<09:07:57.660> 248 09:08:00.772 --> 09:08:00.782 align:start position:0% 09:08:00.782 --> 09:08:02.748 align:start position:0% that<09:08:01.320> is<09:08:01.500> going<09:08:01.680> to<09:08:01.860> be 09:08:02.748 --> 09:08:02.758 align:start position:0% that is going to be 09:08:02.758 --> 09:08:06.130 align:start position:0% that is going to be one<09:08:03.598> one<09:08:03.718> one<09:08:04.200> one<09:08:04.680> one<09:08:04.738> one 09:08:06.130 --> 09:08:06.140 align:start position:0% one one one one one one 09:08:06.140 --> 09:08:08.510 align:start position:0% one one one one one one zero<09:08:07.140> zero<09:08:07.500> zero 09:08:08.510 --> 09:08:08.520 align:start position:0% zero zero zero 09:08:08.520 --> 09:08:09.830 align:start position:0% zero zero zero all<09:08:08.820> right<09:08:09.000> and<09:08:09.122> then<09:08:09.238> if<09:08:09.360> we<09:08:09.480> do<09:08:09.598> our 09:08:09.830 --> 09:08:09.840 align:start position:0% all right and then if we do our 09:08:09.840 --> 09:08:11.990 align:start position:0% all right and then if we do our calculation<09:08:10.438> two<09:08:10.918> to<09:08:11.098> the<09:08:11.218> 3<09:08:11.398> because<09:08:11.700> we<09:08:11.878> have 09:08:11.990 --> 09:08:12.000 align:start position:0% calculation two to the 3 because we have 09:08:12.000 --> 09:08:13.908 align:start position:0% calculation two to the 3 because we have three<09:08:12.180> host<09:08:12.480> bits 09:08:13.908 --> 09:08:13.918 align:start position:0% three host bits 09:08:13.918 --> 09:08:16.612 align:start position:0% three host bits what<09:08:14.340> does<09:08:14.398> that<09:08:14.578> equal<09:08:14.700> eight<09:08:15.540> minus<09:08:16.320> two 09:08:16.612 --> 09:08:16.622 align:start position:0% what does that equal eight minus two 09:08:16.622 --> 09:08:18.708 align:start position:0% what does that equal eight minus two well<09:08:17.460> now 09:08:18.708 --> 09:08:18.718 align:start position:0% well now 09:08:18.718 --> 09:08:22.490 align:start position:0% well now we<09:08:19.258> have<09:08:19.378> a<09:08:19.558> possibility<09:08:20.040> of<09:08:20.578> six<09:08:21.300> hosts<09:08:21.898> so 09:08:22.490 --> 09:08:22.500 align:start position:0% we have a possibility of six hosts so 09:08:22.500 --> 09:08:25.010 align:start position:0% we have a possibility of six hosts so what<09:08:22.680> is<09:08:22.800> our<09:08:22.980> waste<09:08:23.398> two<09:08:23.820> because<09:08:24.180> six<09:08:24.540> minus 09:08:25.010 --> 09:08:25.020 align:start position:0% what is our waste two because six minus 09:08:25.020 --> 09:08:28.728 align:start position:0% what is our waste two because six minus four<09:08:25.200> equals<09:08:26.040> two<09:08:26.218> a<09:08:26.820> lot<09:08:26.938> better<09:08:27.180> right<09:08:27.960> if<09:08:28.622> we 09:08:28.728 --> 09:08:28.738 align:start position:0% four equals two a lot better right if we 09:08:28.738 --> 09:08:31.428 align:start position:0% four equals two a lot better right if we do<09:08:28.860> the<09:08:29.040> same<09:08:29.218> thing<09:08:29.398> with<09:08:29.878> uh<09:08:30.840> the<09:08:31.140> next<09:08:31.258> one 09:08:31.428 --> 09:08:31.438 align:start position:0% do the same thing with uh the next one 09:08:31.438 --> 09:08:32.928 align:start position:0% do the same thing with uh the next one and<09:08:31.622> you<09:08:31.800> were<09:08:31.918> to<09:08:32.040> do<09:08:32.160> the<09:08:32.282> same<09:08:32.398> thing<09:08:32.520> I<09:08:32.700> just 09:08:32.928 --> 09:08:32.938 align:start position:0% and you were to do the same thing I just 09:08:32.938 --> 09:08:36.950 align:start position:0% and you were to do the same thing I just did<09:08:33.122> that<09:08:33.718> would<09:08:33.898> look<09:08:34.140> one<09:08:34.680> one<09:08:35.098> one<09:08:35.282> one<09:08:35.960> zero 09:08:36.950 --> 09:08:36.960 align:start position:0% did that would look one one one one zero 09:08:36.960 --> 09:08:39.530 align:start position:0% did that would look one one one one zero zero<09:08:37.258> zero<09:08:37.622> zero<09:08:37.918> we<09:08:38.040> did<09:08:38.160> the<09:08:38.340> calculation 09:08:39.530 --> 09:08:39.540 align:start position:0% zero zero zero we did the calculation 09:08:39.540 --> 09:08:41.990 align:start position:0% zero zero zero we did the calculation again<09:08:39.898> two<09:08:40.622> to<09:08:40.800> the<09:08:40.980> four<09:08:41.160> because<09:08:41.460> now<09:08:41.758> we 09:08:41.990 --> 09:08:42.000 align:start position:0% again two to the four because now we 09:08:42.000 --> 09:08:44.170 align:start position:0% again two to the four because now we have<09:08:42.180> four<09:08:42.718> bits 09:08:44.170 --> 09:08:44.180 align:start position:0% have four bits 09:08:44.180 --> 09:08:46.010 align:start position:0% have four bits minus<09:08:45.180> two 09:08:46.010 --> 09:08:46.020 align:start position:0% minus two 09:08:46.020 --> 09:08:49.612 align:start position:0% minus two which<09:08:46.738> equals<09:08:47.340> 16<09:08:48.300> minus<09:08:48.898> two<09:08:49.020> which<09:08:49.258> equals 09:08:49.612 --> 09:08:49.622 align:start position:0% which equals 16 minus two which equals 09:08:49.622 --> 09:08:52.548 align:start position:0% which equals 16 minus two which equals fourteen<09:08:50.218> so<09:08:50.820> now<09:08:51.058> I'm<09:08:51.238> only<09:08:51.418> wasting<09:08:51.960> three 09:08:52.548 --> 09:08:52.558 align:start position:0% fourteen so now I'm only wasting three 09:08:52.558 --> 09:08:55.010 align:start position:0% fourteen so now I'm only wasting three bits<09:08:52.980> because<09:08:53.340> 16 09:08:55.010 --> 09:08:55.020 align:start position:0% bits because 16 09:08:55.020 --> 09:08:59.030 align:start position:0% bits because 16 sorry<09:08:55.558> 14<09:08:56.040> minus<09:08:56.700> 11<09:08:57.020> equals<09:08:58.020> three<09:08:58.320> and 09:08:59.030 --> 09:08:59.040 align:start position:0% sorry 14 minus 11 equals three and 09:08:59.040 --> 09:09:00.888 align:start position:0% sorry 14 minus 11 equals three and finally<09:08:59.340> 224<09:08:59.938> is<09:09:00.058> the<09:09:00.238> same<09:09:00.360> remember<09:09:00.598> that 09:09:00.888 --> 09:09:00.898 align:start position:0% finally 224 is the same remember that 09:09:00.898 --> 09:09:04.548 align:start position:0% finally 224 is the same remember that was<09:09:01.078> 30<09:09:01.320> bits<09:09:01.860> or<09:09:02.340> 30<09:09:02.520> hosts<09:09:03.000> rather<09:09:03.360> 30<09:09:04.078> minus 09:09:04.548 --> 09:09:04.558 align:start position:0% was 30 bits or 30 hosts rather 30 minus 09:09:04.558 --> 09:09:09.708 align:start position:0% was 30 bits or 30 hosts rather 30 minus 27<09:09:04.918> is<09:09:05.160> 3.<09:09:05.578> so<09:09:06.000> doing<09:09:06.238> this<09:09:06.660> variable 09:09:09.708 --> 09:09:09.718 align:start position:0% 09:09:09.718 --> 09:09:12.708 align:start position:0% we<09:09:10.320> are<09:09:10.438> a<09:09:10.622> variable<09:09:11.040> subnet<09:09:11.460> mask<09:09:11.700> we're<09:09:12.418> no 09:09:12.708 --> 09:09:12.718 align:start position:0% we are a variable subnet mask we're no 09:09:12.718 --> 09:09:16.850 align:start position:0% we are a variable subnet mask we're no longer<09:09:13.078> wasting<09:09:13.980> as<09:09:14.398> many<09:09:14.700> host<09:09:15.360> addresses<09:09:16.200> so 09:09:16.850 --> 09:09:16.860 align:start position:0% longer wasting as many host addresses so 09:09:16.860 --> 09:09:18.588 align:start position:0% longer wasting as many host addresses so by<09:09:17.040> utilizing<09:09:17.700> this<09:09:18.058> we're<09:09:18.300> going<09:09:18.480> to 09:09:18.588 --> 09:09:18.598 align:start position:0% by utilizing this we're going to 09:09:18.598 --> 09:09:20.568 align:start position:0% by utilizing this we're going to appropriately<09:09:19.200> plan<09:09:19.680> and<09:09:19.980> Implement<09:09:20.340> a 09:09:20.568 --> 09:09:20.578 align:start position:0% appropriately plan and Implement a 09:09:20.578 --> 09:09:22.908 align:start position:0% appropriately plan and Implement a scheme<09:09:21.000> and<09:09:21.418> it<09:09:21.480> allows<09:09:21.782> us<09:09:21.898> to<09:09:22.140> use<09:09:22.320> our<09:09:22.622> space 09:09:22.908 --> 09:09:22.918 align:start position:0% scheme and it allows us to use our space 09:09:22.918 --> 09:09:25.908 align:start position:0% scheme and it allows us to use our space much<09:09:23.758> more<09:09:24.000> effectively<09:09:24.598> of<09:09:25.320> course<09:09:25.500> the 09:09:25.908 --> 09:09:25.918 align:start position:0% much more effectively of course the 09:09:25.918 --> 09:09:27.588 align:start position:0% much more effectively of course the negative<09:09:26.218> aspect<09:09:26.578> of<09:09:26.758> this<09:09:26.938> is<09:09:27.180> it's<09:09:27.300> a<09:09:27.480> lot 09:09:27.588 --> 09:09:27.598 align:start position:0% negative aspect of this is it's a lot 09:09:27.598 --> 09:09:29.388 align:start position:0% negative aspect of this is it's a lot more<09:09:27.718> harder<09:09:28.200> to<09:09:28.320> scale 09:09:29.388 --> 09:09:29.398 align:start position:0% more harder to scale 09:09:29.398 --> 09:09:31.368 align:start position:0% more harder to scale and<09:09:29.820> if<09:09:29.938> I<09:09:30.122> want<09:09:30.238> to<09:09:30.360> add<09:09:30.540> nodes<09:09:30.960> to<09:09:31.140> these 09:09:31.368 --> 09:09:31.378 align:start position:0% and if I want to add nodes to these 09:09:31.378 --> 09:09:32.690 align:start position:0% and if I want to add nodes to these customized<09:09:31.860> networks<09:09:32.098> I<09:09:32.218> might<09:09:32.340> have<09:09:32.460> to<09:09:32.578> go 09:09:32.690 --> 09:09:32.700 align:start position:0% customized networks I might have to go 09:09:32.700 --> 09:09:35.030 align:start position:0% customized networks I might have to go around<09:09:32.878> and<09:09:33.660> change<09:09:33.840> all<09:09:34.140> the<09:09:34.258> subnet<09:09:34.622> masks 09:09:35.030 --> 09:09:35.040 align:start position:0% around and change all the subnet masks 09:09:35.040 --> 09:09:39.588 align:start position:0% around and change all the subnet masks as<09:09:35.282> well<09:09:35.460> now<09:09:36.122> cider<09:09:36.782> which<09:09:37.622> is<09:09:37.800> cidr<09:09:38.758> which 09:09:39.588 --> 09:09:39.598 align:start position:0% as well now cider which is cidr which 09:09:39.598 --> 09:09:43.728 align:start position:0% as well now cider which is cidr which stands<09:09:40.020> for<09:09:40.520> class<09:09:41.520> less 09:09:43.728 --> 09:09:43.738 align:start position:0% stands for class less 09:09:43.738 --> 09:09:46.248 align:start position:0% stands for class less enter 09:09:46.248 --> 09:09:46.258 align:start position:0% enter 09:09:46.258 --> 09:09:49.068 align:start position:0% enter domain 09:09:49.068 --> 09:09:49.078 align:start position:0% domain 09:09:49.078 --> 09:09:51.530 align:start position:0% domain routing 09:09:51.530 --> 09:09:51.540 align:start position:0% routing 09:09:51.540 --> 09:09:58.010 align:start position:0% routing is<09:09:52.078> also<09:09:52.438> commonly<09:09:52.918> called<09:09:53.340> super<09:09:54.300> netting 09:09:58.010 --> 09:09:58.020 align:start position:0% 09:09:58.020 --> 09:10:01.728 align:start position:0% or<09:09:58.738> classless<09:09:59.398> routing<09:10:00.480> it's<09:10:00.840> another<09:10:01.020> method 09:10:01.728 --> 09:10:01.738 align:start position:0% or classless routing it's another method 09:10:01.738 --> 09:10:05.030 align:start position:0% or classless routing it's another method of<09:10:01.918> addressing<09:10:02.460> that<09:10:02.700> uses<09:10:03.058> the<09:10:03.300> vlsm<09:10:03.960> but<09:10:04.738> in 09:10:05.030 --> 09:10:05.040 align:start position:0% of addressing that uses the vlsm but in 09:10:05.040 --> 09:10:07.548 align:start position:0% of addressing that uses the vlsm but in a<09:10:05.160> different<09:10:05.282> way<09:10:05.520> is<09:10:05.758> at<09:10:06.058> the<09:10:06.300> 32-bit<09:10:06.898> word<09:10:07.140> so 09:10:07.548 --> 09:10:07.558 align:start position:0% a different way is at the 32-bit word so 09:10:07.558 --> 09:10:10.368 align:start position:0% a different way is at the 32-bit word so the<09:10:08.040> notation<09:10:08.520> is<09:10:09.238> much<09:10:09.540> easier<09:10:10.020> to<09:10:10.200> read 09:10:10.368 --> 09:10:10.378 align:start position:0% the notation is much easier to read 09:10:10.378 --> 09:10:13.428 align:start position:0% the notation is much easier to read because<09:10:11.040> it<09:10:11.340> combines<09:10:11.700> the<09:10:11.938> IP<09:10:12.238> address 09:10:13.428 --> 09:10:13.438 align:start position:0% because it combines the IP address 09:10:13.438 --> 09:10:15.950 align:start position:0% because it combines the IP address with<09:10:14.040> this<09:10:14.340> Dash<09:10:14.820> after<09:10:15.122> it 09:10:15.950 --> 09:10:15.960 align:start position:0% with this Dash after it 09:10:15.960 --> 09:10:18.470 align:start position:0% with this Dash after it for<09:10:16.378> instance<09:10:16.622> the<09:10:16.980> number<09:10:17.218> is<09:10:17.878> what<09:10:18.058> denotes 09:10:18.470 --> 09:10:18.480 align:start position:0% for instance the number is what denotes 09:10:18.480 --> 09:10:21.290 align:start position:0% for instance the number is what denotes the<09:10:18.660> amount<09:10:18.898> of<09:10:19.078> ones<09:10:19.800> in<09:10:20.520> the<09:10:20.700> subnet<09:10:21.122> mask 09:10:21.290 --> 09:10:21.300 align:start position:0% the amount of ones in the subnet mask 09:10:21.300 --> 09:10:25.010 align:start position:0% the amount of ones in the subnet mask from<09:10:21.660> left<09:10:21.840> to<09:10:22.140> right<09:10:22.398> so<09:10:23.398> if<09:10:23.700> we<09:10:23.878> look<09:10:24.058> at<09:10:24.360> this 09:10:25.010 --> 09:10:25.020 align:start position:0% from left to right so if we look at this 09:10:25.020 --> 09:10:29.112 align:start position:0% from left to right so if we look at this notation<09:10:25.500> right<09:10:25.918> here<09:10:26.160> we<09:10:26.520> have 09:10:29.112 --> 09:10:29.122 align:start position:0% 09:10:29.122 --> 09:10:31.850 align:start position:0% 192.168.13.0.23<09:10:30.122> well<09:10:30.718> the<09:10:30.898> 23<09:10:31.320> means<09:10:31.680> there 09:10:31.850 --> 09:10:31.860 align:start position:0% 192.168.13.0.23 well the 23 means there 09:10:31.860 --> 09:10:34.850 align:start position:0% 192.168.13.0.23 well the 23 means there are<09:10:32.098> 23<09:10:33.000> ones<09:10:33.540> from<09:10:33.840> left<09:10:34.078> to<09:10:34.320> right<09:10:34.500> in<09:10:34.738> the 09:10:34.850 --> 09:10:34.860 align:start position:0% are 23 ones from left to right in the 09:10:34.860 --> 09:10:36.408 align:start position:0% are 23 ones from left to right in the subnet<09:10:35.218> mask 09:10:36.408 --> 09:10:36.418 align:start position:0% subnet mask 09:10:36.418 --> 09:10:39.408 align:start position:0% subnet mask okay<09:10:37.020> and<09:10:37.680> now<09:10:37.800> if<09:10:38.098> we<09:10:38.282> were<09:10:38.460> to<09:10:38.578> convert<09:10:39.122> that 09:10:39.408 --> 09:10:39.418 align:start position:0% okay and now if we were to convert that 09:10:39.418 --> 09:10:41.690 align:start position:0% okay and now if we were to convert that this<09:10:40.020> allows<09:10:40.378> for<09:10:40.558> a<09:10:40.860> possible<09:10:41.160> amount<09:10:41.578> of 09:10:41.690 --> 09:10:41.700 align:start position:0% this allows for a possible amount of 09:10:41.700 --> 09:10:46.908 align:start position:0% this allows for a possible amount of host<09:10:41.938> addresses<09:10:42.660> 2<09:10:43.558> to<09:10:43.800> the<09:10:43.918> ninth 09:10:46.908 --> 09:10:46.918 align:start position:0% host addresses 2 to the ninth 09:10:46.918 --> 09:10:48.772 align:start position:0% host addresses 2 to the ninth minus<09:10:47.820> two 09:10:48.772 --> 09:10:48.782 align:start position:0% minus two 09:10:48.782 --> 09:10:51.470 align:start position:0% minus two which<09:10:49.258> equals<09:10:49.738> 500 09:10:51.470 --> 09:10:51.480 align:start position:0% which equals 500 09:10:51.480 --> 09:10:55.190 align:start position:0% which equals 500 and<09:10:52.020> 10<09:10:52.340> addresses<09:10:53.340> so<09:10:54.122> this<09:10:54.300> allows<09:10:54.660> for<09:10:54.960> more 09:10:55.190 --> 09:10:55.200 align:start position:0% and 10 addresses so this allows for more 09:10:55.200 --> 09:10:57.772 align:start position:0% and 10 addresses so this allows for more than<09:10:55.378> one<09:10:55.680> class<09:10:56.340> full<09:10:56.640> Network<09:10:57.000> to<09:10:57.660> be 09:10:57.772 --> 09:10:57.782 align:start position:0% than one class full Network to be 09:10:57.782 --> 09:11:01.010 align:start position:0% than one class full Network to be represented<09:10:58.378> by<09:10:58.680> a<09:10:58.980> single<09:10:59.398> set<09:10:59.820> basically<09:11:00.782> we 09:11:01.010 --> 09:11:01.020 align:start position:0% represented by a single set basically we 09:11:01.020 --> 09:11:02.810 align:start position:0% represented by a single set basically we can<09:11:01.140> now<09:11:01.258> break<09:11:01.438> it<09:11:01.680> up<09:11:01.800> further<09:11:02.098> into<09:11:02.340> smaller 09:11:02.810 --> 09:11:02.820 align:start position:0% can now break it up further into smaller 09:11:02.820 --> 09:11:04.728 align:start position:0% can now break it up further into smaller sub<09:11:02.938> networks<09:11:03.480> if<09:11:03.898> we<09:11:04.020> look<09:11:04.140> at<09:11:04.258> three<09:11:04.438> of<09:11:04.622> the 09:11:04.728 --> 09:11:04.738 align:start position:0% sub networks if we look at three of the 09:11:04.738 --> 09:11:07.490 align:start position:0% sub networks if we look at three of the most<09:11:04.918> easily<09:11:05.660> recognizable<09:11:06.660> ones<09:11:07.078> I'm<09:11:07.378> just 09:11:07.490 --> 09:11:07.500 align:start position:0% most easily recognizable ones I'm just 09:11:07.500 --> 09:11:08.510 align:start position:0% most easily recognizable ones I'm just going<09:11:07.622> to<09:11:07.680> erase<09:11:07.860> this<09:11:08.040> so<09:11:08.160> we<09:11:08.218> can<09:11:08.282> get<09:11:08.398> a 09:11:08.510 --> 09:11:08.520 align:start position:0% going to erase this so we can get a 09:11:08.520 --> 09:11:12.290 align:start position:0% going to erase this so we can get a better<09:11:08.578> look<09:11:08.820> here<09:11:09.200> uh<09:11:10.200> the<09:11:10.438> slash<09:11:10.800> eight 09:11:12.290 --> 09:11:12.300 align:start position:0% better look here uh the slash eight 09:11:12.300 --> 09:11:16.010 align:start position:0% better look here uh the slash eight the<09:11:13.140> slash<09:11:13.438> 16<09:11:13.738> and<09:11:14.160> the<09:11:14.340> slash<09:11:14.578> 24 09:11:16.010 --> 09:11:16.020 align:start position:0% the slash 16 and the slash 24 09:11:16.020 --> 09:11:17.510 align:start position:0% the slash 16 and the slash 24 we<09:11:16.438> can<09:11:16.558> see<09:11:16.738> that<09:11:16.918> these<09:11:17.282> translate 09:11:17.510 --> 09:11:17.520 align:start position:0% we can see that these translate 09:11:17.520 --> 09:11:20.990 align:start position:0% we can see that these translate basically<09:11:18.180> over<09:11:18.480> to<09:11:19.078> the<09:11:19.258> basic<09:11:20.160> Class<09:11:20.700> A 09:11:20.990 --> 09:11:21.000 align:start position:0% basically over to the basic Class A 09:11:21.000 --> 09:11:23.150 align:start position:0% basically over to the basic Class A Class<09:11:21.360> B<09:11:21.598> and<09:11:21.840> Class<09:11:22.020> C<09:11:22.320> networks<09:11:22.918> right 09:11:23.150 --> 09:11:23.160 align:start position:0% Class B and Class C networks right 09:11:23.160 --> 09:11:26.272 align:start position:0% Class B and Class C networks right because<09:11:23.878> slash<09:11:24.540> eight<09:11:24.898> Class<09:11:25.438> A<09:11:25.680> that<09:11:25.980> means 09:11:26.272 --> 09:11:26.282 align:start position:0% because slash eight Class A that means 09:11:26.282 --> 09:11:29.630 align:start position:0% because slash eight Class A that means it's<09:11:26.398> one<09:11:26.700> one<09:11:27.058> or<09:11:27.960> one<09:11:28.258> two<09:11:28.438> three<09:11:28.738> four<09:11:29.160> five 09:11:29.630 --> 09:11:29.640 align:start position:0% it's one one or one two three four five 09:11:29.640 --> 09:11:34.310 align:start position:0% it's one one or one two three four five six<09:11:30.058> seven<09:11:30.418> eight<09:11:31.040> dot<09:11:32.040> zero<09:11:32.640> dot<09:11:33.360> zero<09:11:33.782> dot 09:11:34.310 --> 09:11:34.320 align:start position:0% six seven eight dot zero dot zero dot 09:11:34.320 --> 09:11:38.888 align:start position:0% six seven eight dot zero dot zero dot zero<09:11:34.738> which<09:11:35.160> would<09:11:35.398> mean 09:11:38.888 --> 09:11:38.898 align:start position:0% 09:11:38.898 --> 09:11:41.388 align:start position:0% 255.25.0.0.0<09:11:39.898> which<09:11:40.258> is<09:11:40.438> our<09:11:40.622> default<09:11:40.918> subnet 09:11:41.388 --> 09:11:41.398 align:start position:0% 255.25.0.0.0 which is our default subnet 09:11:41.398 --> 09:11:42.950 align:start position:0% 255.25.0.0.0 which is our default subnet mask<09:11:41.578> for<09:11:41.878> Class<09:11:42.122> A 09:11:42.950 --> 09:11:42.960 align:start position:0% mask for Class A 09:11:42.960 --> 09:11:45.228 align:start position:0% mask for Class A because<09:11:43.438> again 09:11:45.228 --> 09:11:45.238 align:start position:0% because again 09:11:45.238 --> 09:11:47.810 align:start position:0% because again this<09:11:45.840> is<09:11:45.960> my<09:11:46.258> network<09:11:46.500> ID<09:11:46.860> is<09:11:47.098> the<09:11:47.282> first<09:11:47.398> octet 09:11:47.810 --> 09:11:47.820 align:start position:0% this is my network ID is the first octet 09:11:47.820 --> 09:11:50.088 align:start position:0% this is my network ID is the first octet and<09:11:48.000> the<09:11:48.122> node<09:11:48.300> ID<09:11:48.480> are<09:11:49.378> the<09:11:49.558> last<09:11:49.680> ones<09:11:49.980> and 09:11:50.088 --> 09:11:50.098 align:start position:0% and the node ID are the last ones and 09:11:50.098 --> 09:11:52.428 align:start position:0% and the node ID are the last ones and you<09:11:50.218> can<09:11:50.340> see<09:11:50.460> that<09:11:50.700> that<09:11:50.878> would<09:11:51.180> fall<09:11:51.960> out<09:11:52.140> for 09:11:52.428 --> 09:11:52.438 align:start position:0% you can see that that would fall out for 09:11:52.438 --> 09:11:54.772 align:start position:0% you can see that that would fall out for the<09:11:52.558> next<09:11:52.738> ones<09:11:53.040> as<09:11:53.218> well<09:11:53.398> so<09:11:54.238> because<09:11:54.418> of<09:11:54.660> the 09:11:54.772 --> 09:11:54.782 align:start position:0% the next ones as well so because of the 09:11:54.782 --> 09:11:57.588 align:start position:0% the next ones as well so because of the ease<09:11:55.020> by<09:11:55.258> which<09:11:55.500> it<09:11:56.040> is<09:11:56.218> we<09:11:57.000> can<09:11:57.122> subnet 09:11:57.588 --> 09:11:57.598 align:start position:0% ease by which it is we can subnet 09:11:57.598 --> 09:11:59.810 align:start position:0% ease by which it is we can subnet networks<09:11:58.078> this<09:11:58.258> way<09:11:58.438> because<09:11:59.040> of<09:11:59.282> readability 09:11:59.810 --> 09:11:59.820 align:start position:0% networks this way because of readability 09:11:59.820 --> 09:12:03.170 align:start position:0% networks this way because of readability and<09:12:00.360> efficiency<09:12:01.218> cider<09:12:02.218> notation<09:12:02.578> has<09:12:02.878> become 09:12:03.170 --> 09:12:03.180 align:start position:0% and efficiency cider notation has become 09:12:03.180 --> 09:12:05.990 align:start position:0% and efficiency cider notation has become extremely<09:12:04.020> popular<09:12:04.378> and<09:12:04.680> wider<09:12:05.040> widely 09:12:05.990 --> 09:12:06.000 align:start position:0% extremely popular and wider widely 09:12:06.000 --> 09:12:07.010 align:start position:0% extremely popular and wider widely adopted 09:12:07.010 --> 09:12:07.020 align:start position:0% adopted 09:12:07.020 --> 09:12:09.470 align:start position:0% adopted most<09:12:07.558> of<09:12:07.680> the<09:12:07.800> internet<09:12:07.980> in<09:12:08.340> fact<09:12:08.520> has<09:12:09.058> become 09:12:09.470 --> 09:12:09.480 align:start position:0% most of the internet in fact has become 09:12:09.480 --> 09:12:12.650 align:start position:0% most of the internet in fact has become class<09:12:10.200> less<09:12:10.558> address<09:12:11.098> space<09:12:11.520> because<09:12:12.300> of<09:12:12.540> this 09:12:12.650 --> 09:12:12.660 align:start position:0% class less address space because of this 09:12:12.660 --> 09:12:14.272 align:start position:0% class less address space because of this meaning<09:12:12.898> that<09:12:13.140> we<09:12:13.320> don't<09:12:13.378> really<09:12:13.558> use<09:12:13.800> classes 09:12:14.272 --> 09:12:14.282 align:start position:0% meaning that we don't really use classes 09:12:14.282 --> 09:12:16.612 align:start position:0% meaning that we don't really use classes and<09:12:14.460> we<09:12:14.640> get<09:12:14.758> to<09:12:14.878> IPv6<09:12:15.660> we're<09:12:16.200> not<09:12:16.378> going<09:12:16.500> to 09:12:16.612 --> 09:12:16.622 align:start position:0% and we get to IPv6 we're not going to 09:12:16.622 --> 09:12:18.470 align:start position:0% and we get to IPv6 we're not going to see<09:12:16.738> it<09:12:16.860> at<09:12:17.040> all<09:12:17.160> now<09:12:17.640> again<09:12:17.820> this<09:12:18.122> is<09:12:18.238> very 09:12:18.470 --> 09:12:18.480 align:start position:0% see it at all now again this is very 09:12:18.480 --> 09:12:19.908 align:start position:0% see it at all now again this is very complex<09:12:18.840> the<09:12:19.140> important<09:12:19.438> thing<09:12:19.558> I<09:12:19.738> just<09:12:19.800> want 09:12:19.908 --> 09:12:19.918 align:start position:0% complex the important thing I just want 09:12:19.918 --> 09:12:22.248 align:start position:0% complex the important thing I just want you<09:12:20.040> to<09:12:20.218> remember<09:12:20.340> on<09:12:20.878> this<09:12:21.058> whole<09:12:21.180> thing<09:12:21.418> is 09:12:22.248 --> 09:12:22.258 align:start position:0% you to remember on this whole thing is 09:12:22.258 --> 09:12:26.868 align:start position:0% you to remember on this whole thing is that<09:12:22.500> if<09:12:22.860> you<09:12:22.980> see<09:12:23.160> this<09:12:23.460> Dash<09:12:24.000> after 09:12:26.868 --> 09:12:26.878 align:start position:0% 09:12:26.878 --> 09:12:31.130 align:start position:0% an<09:12:27.540> address<09:12:27.782> here<09:12:28.258> you<09:12:29.160> know<09:12:29.340> exactly<09:12:30.140> what 09:12:31.130 --> 09:12:31.140 align:start position:0% an address here you know exactly what 09:12:31.140 --> 09:12:34.130 align:start position:0% an address here you know exactly what the<09:12:31.320> subnet<09:12:31.738> mask<09:12:31.918> is<09:12:32.418> and<09:12:33.418> then<09:12:33.660> you<09:12:34.020> can 09:12:34.130 --> 09:12:34.140 align:start position:0% the subnet mask is and then you can 09:12:34.140 --> 09:12:36.350 align:start position:0% the subnet mask is and then you can backwards<09:12:34.800> engineer<09:12:35.282> or<09:12:35.700> forward<09:12:35.878> engineer 09:12:36.350 --> 09:12:36.360 align:start position:0% backwards engineer or forward engineer 09:12:36.360 --> 09:12:39.530 align:start position:0% backwards engineer or forward engineer the<09:12:36.540> IP<09:12:36.840> address<09:12:37.340> or<09:12:38.340> the<09:12:38.520> network<09:12:38.640> ID<09:12:38.938> or<09:12:39.300> node 09:12:39.530 --> 09:12:39.540 align:start position:0% the IP address or the network ID or node 09:12:39.540 --> 09:12:40.428 align:start position:0% the IP address or the network ID or node ID 09:12:40.428 --> 09:12:40.438 align:start position:0% ID 09:12:40.438 --> 09:12:42.350 align:start position:0% ID so<09:12:40.860> just<09:12:41.098> to<09:12:41.282> review<09:12:41.460> some<09:12:41.758> of<09:12:41.878> the<09:12:42.000> points 09:12:42.350 --> 09:12:42.360 align:start position:0% so just to review some of the points 09:12:42.360 --> 09:12:44.450 align:start position:0% so just to review some of the points that<09:12:42.480> we<09:12:42.598> covered<09:12:42.960> here<09:12:43.258> we<09:12:44.040> started<09:12:44.398> by 09:12:44.450 --> 09:12:44.460 align:start position:0% that we covered here we started by 09:12:44.460 --> 09:12:48.170 align:start position:0% that we covered here we started by outlining<09:12:45.000> the<09:12:45.300> ipv4<09:12:46.200> addressing<09:12:47.040> scheme<09:12:47.460> we 09:12:48.170 --> 09:12:48.180 align:start position:0% outlining the ipv4 addressing scheme we 09:12:48.180 --> 09:12:50.088 align:start position:0% outlining the ipv4 addressing scheme we looked<09:12:48.480> at<09:12:48.540> the<09:12:48.898> five<09:12:49.020> classes<09:12:49.558> the<09:12:49.738> three<09:12:49.918> I 09:12:50.088 --> 09:12:50.098 align:start position:0% looked at the five classes the three I 09:12:50.098 --> 09:12:52.490 align:start position:0% looked at the five classes the three I really<09:12:50.282> want<09:12:50.460> you<09:12:50.578> to<09:12:50.700> be<09:12:50.758> aware<09:12:51.000> of<09:12:51.180> are<09:12:51.418> a<09:12:51.840> b 09:12:52.490 --> 09:12:52.500 align:start position:0% really want you to be aware of are a b 09:12:52.500 --> 09:12:56.272 align:start position:0% really want you to be aware of are a b and<09:12:52.680> c<09:12:52.918> remember<09:12:53.700> a<09:12:54.360> is<09:12:55.320> anything<09:12:55.622> in<09:12:56.040> the 09:12:56.272 --> 09:12:56.282 align:start position:0% and c remember a is anything in the 09:12:56.282 --> 09:12:58.970 align:start position:0% and c remember a is anything in the first<09:12:56.398> octet<09:12:57.058> that's<09:12:57.782> one 09:12:58.970 --> 09:12:58.980 align:start position:0% first octet that's one 09:12:58.980 --> 09:13:01.728 align:start position:0% first octet that's one through<09:12:59.960> 127 09:13:01.728 --> 09:13:01.738 align:start position:0% through 127 09:13:01.738 --> 09:13:04.568 align:start position:0% through 127 with<09:13:02.398> class<09:13:02.578> B<09:13:03.000> we're<09:13:03.782> looking<09:13:03.960> at<09:13:04.200> anything 09:13:04.568 --> 09:13:04.578 align:start position:0% with class B we're looking at anything 09:13:04.578 --> 09:13:07.908 align:start position:0% with class B we're looking at anything from<09:13:05.578> 128 09:13:07.908 --> 09:13:07.918 align:start position:0% from 128 09:13:07.918 --> 09:13:11.030 align:start position:0% from 128 to<09:13:08.520> 191<09:13:09.300> and<09:13:09.960> with<09:13:10.140> class<09:13:10.320> C<09:13:10.558> we're<09:13:10.738> looking<09:13:10.918> at 09:13:11.030 --> 09:13:11.040 align:start position:0% to 191 and with class C we're looking at 09:13:11.040 --> 09:13:16.970 align:start position:0% to 191 and with class C we're looking at anything<09:13:11.218> from<09:13:11.520> 191<09:13:12.320> or<09:13:13.320> rather<09:13:13.558> 192. 09:13:16.970 --> 09:13:16.980 align:start position:0% 09:13:16.980 --> 09:13:20.630 align:start position:0% to<09:13:17.660> 223.<09:13:18.660> anything<09:13:19.378> else<09:13:19.800> here<09:13:20.098> we're<09:13:20.398> really 09:13:20.630 --> 09:13:20.640 align:start position:0% to 223. anything else here we're really 09:13:20.640 --> 09:13:23.272 align:start position:0% to 223. anything else here we're really looking<09:13:20.938> at<09:13:21.738> experimental<09:13:22.738> and<09:13:22.918> stuff<09:13:23.098> that 09:13:23.272 --> 09:13:23.282 align:start position:0% looking at experimental and stuff that 09:13:23.282 --> 09:13:25.310 align:start position:0% looking at experimental and stuff that we<09:13:23.460> don't<09:13:23.520> really<09:13:23.700> need<09:13:23.938> remember<09:13:24.718> these 09:13:25.310 --> 09:13:25.320 align:start position:0% we don't really need remember these 09:13:25.320 --> 09:13:27.530 align:start position:0% we don't really need remember these ranges<09:13:25.800> for<09:13:26.098> that<09:13:26.218> first<09:13:26.460> octet<09:13:27.000> it's<09:13:27.238> easy 09:13:27.530 --> 09:13:27.540 align:start position:0% ranges for that first octet it's easy 09:13:27.540 --> 09:13:29.690 align:start position:0% ranges for that first octet it's easy then<09:13:27.840> to<09:13:28.438> determine<09:13:28.860> what<09:13:29.218> class<09:13:29.398> we're 09:13:29.690 --> 09:13:29.700 align:start position:0% then to determine what class we're 09:13:29.700 --> 09:13:30.772 align:start position:0% then to determine what class we're looking<09:13:29.938> at 09:13:30.772 --> 09:13:30.782 align:start position:0% looking at 09:13:30.782 --> 09:13:32.990 align:start position:0% looking at okay<09:13:31.320> so<09:13:31.622> we<09:13:31.800> also<09:13:32.040> described<09:13:32.398> the<09:13:32.578> reserved 09:13:32.990 --> 09:13:33.000 align:start position:0% okay so we also described the reserved 09:13:33.000 --> 09:13:34.728 align:start position:0% okay so we also described the reserved or<09:13:33.122> restricted<09:13:33.540> IP<09:13:33.782> addresses<09:13:34.258> for<09:13:34.500> instance 09:13:34.728 --> 09:13:34.738 align:start position:0% or restricted IP addresses for instance 09:13:34.738 --> 09:13:36.950 align:start position:0% or restricted IP addresses for instance we<09:13:35.040> can't<09:13:35.218> have<09:13:35.520> anything 09:13:36.950 --> 09:13:36.960 align:start position:0% we can't have anything 09:13:36.960 --> 09:13:40.490 align:start position:0% we can't have anything with<09:13:37.438> a<09:13:37.622> zot<09:13:38.000> 0.0.0<09:13:39.000> or 09:13:40.490 --> 09:13:40.500 align:start position:0% with a zot 0.0.0 or 09:13:40.500 --> 09:13:45.708 align:start position:0% with a zot 0.0.0 or with<09:13:40.860> a<09:13:41.098> 255.255.255. 09:13:45.708 --> 09:13:45.718 align:start position:0% 09:13:45.718 --> 09:13:48.112 align:start position:0% because<09:13:46.140> these<09:13:46.558> are<09:13:46.680> a<09:13:46.860> multicast<09:13:47.340> addresses 09:13:48.112 --> 09:13:48.122 align:start position:0% because these are a multicast addresses 09:13:48.122 --> 09:13:51.428 align:start position:0% because these are a multicast addresses and<09:13:48.660> we<09:13:48.840> also<09:13:49.078> can't<09:13:49.320> have<09:13:49.558> anything<09:13:49.800> with 09:13:51.428 --> 09:13:51.438 align:start position:0% and we also can't have anything with 09:13:51.438 --> 09:13:53.388 align:start position:0% and we also can't have anything with 127.0.0.1<09:13:52.438> ever 09:13:53.388 --> 09:13:53.398 align:start position:0% 127.0.0.1 ever 09:13:53.398 --> 09:13:54.908 align:start position:0% 127.0.0.1 ever or 09:13:54.908 --> 09:13:54.918 align:start position:0% or 09:13:54.918 --> 09:13:58.068 align:start position:0% or 1.1.1.1<09:13:55.918> because<09:13:56.640> these<09:13:57.300> are<09:13:57.418> both<09:13:57.598> ones<09:13:57.960> the 09:13:58.068 --> 09:13:58.078 align:start position:0% 1.1.1.1 because these are both ones the 09:13:58.078 --> 09:14:00.530 align:start position:0% 1.1.1.1 because these are both ones the localhost<09:13:58.500> one<09:13:58.800> is<09:13:58.918> the<09:13:59.040> who<09:13:59.160> is<09:13:59.398> address 09:14:00.530 --> 09:14:00.540 align:start position:0% localhost one is the who is address 09:14:00.540 --> 09:14:03.530 align:start position:0% localhost one is the who is address we<09:14:01.020> then<09:14:01.200> looked<09:14:01.558> at<09:14:01.680> uh<09:14:02.340> private<09:14:03.180> IP 09:14:03.530 --> 09:14:03.540 align:start position:0% we then looked at uh private IP 09:14:03.540 --> 09:14:05.510 align:start position:0% we then looked at uh private IP addresses<09:14:04.078> remember<09:14:04.622> we<09:14:05.098> had<09:14:05.282> three 09:14:05.510 --> 09:14:05.520 align:start position:0% addresses remember we had three 09:14:05.520 --> 09:14:07.612 align:start position:0% addresses remember we had three different<09:14:05.758> ones<09:14:06.058> each<09:14:06.238> for<09:14:06.480> each<09:14:06.718> class<09:14:06.960> for 09:14:07.612 --> 09:14:07.622 align:start position:0% different ones each for each class for 09:14:07.622 --> 09:14:11.990 align:start position:0% different ones each for each class for class<09:14:07.860> A<09:14:08.098> it<09:14:08.340> was<09:14:08.460> anything<09:14:08.700> 10.x.x.x 09:14:11.990 --> 09:14:12.000 align:start position:0% 09:14:12.000 --> 09:14:16.548 align:start position:0% with<09:14:12.480> class<09:14:12.660> B<09:14:13.078> it<09:14:13.918> was<09:14:14.098> one<09:14:14.520> seven<09:14:14.820> two<09:14:15.558> dot 09:14:16.548 --> 09:14:16.558 align:start position:0% with class B it was one seven two dot 09:14:16.558 --> 09:14:23.530 align:start position:0% with class B it was one seven two dot sixteen<09:14:17.218> dot<09:14:18.122> x<09:14:18.300> dot<09:14:18.718> X<09:14:18.898> through 09:14:23.530 --> 09:14:23.540 align:start position:0% 09:14:23.540 --> 09:14:25.670 align:start position:0% 172.31.x.x<09:14:24.540> and<09:14:24.960> the<09:14:25.078> one<09:14:25.258> you're<09:14:25.438> probably 09:14:25.670 --> 09:14:25.680 align:start position:0% 172.31.x.x and the one you're probably 09:14:25.680 --> 09:14:28.248 align:start position:0% 172.31.x.x and the one you're probably most<09:14:26.098> familiar<09:14:26.460> with<09:14:26.578> is<09:14:26.820> the<09:14:27.058> class<09:14:27.238> C<09:14:27.540> which 09:14:28.248 --> 09:14:28.258 align:start position:0% most familiar with is the class C which 09:14:28.258 --> 09:14:32.330 align:start position:0% most familiar with is the class C which is<09:14:28.378> 192.168.x.x 09:14:32.330 --> 09:14:32.340 align:start position:0% 09:14:32.340 --> 09:14:35.510 align:start position:0% remember<09:14:33.000> that<09:14:33.898> you<09:14:34.500> can<09:14:34.558> see<09:14:34.860> what<09:14:35.282> class 09:14:35.510 --> 09:14:35.520 align:start position:0% remember that you can see what class 09:14:35.520 --> 09:14:37.248 align:start position:0% remember that you can see what class they're<09:14:35.758> in 09:14:37.248 --> 09:14:37.258 align:start position:0% they're in 09:14:37.258 --> 09:14:40.130 align:start position:0% they're in by<09:14:37.800> looking<09:14:37.980> at<09:14:38.218> this<09:14:38.480> and<09:14:39.480> most<09:14:39.660> importantly 09:14:40.130 --> 09:14:40.140 align:start position:0% by looking at this and most importantly 09:14:40.140 --> 09:14:43.068 align:start position:0% by looking at this and most importantly class<09:14:41.040> a<09:14:41.398> private<09:14:41.878> IP<09:14:42.180> address<09:14:42.360> can<09:14:42.660> allow<09:14:42.960> for 09:14:43.068 --> 09:14:43.078 align:start position:0% class a private IP address can allow for 09:14:43.078 --> 09:14:45.470 align:start position:0% class a private IP address can allow for the<09:14:43.320> most<09:14:43.500> networks<09:14:44.460> the<09:14:44.700> fewest<09:14:44.938> I'm<09:14:45.300> sorry 09:14:45.470 --> 09:14:45.480 align:start position:0% the most networks the fewest I'm sorry 09:14:45.480 --> 09:14:47.510 align:start position:0% the most networks the fewest I'm sorry the<09:14:45.660> most<09:14:45.782> nodes<09:14:46.078> the<09:14:46.320> fewest<09:14:46.558> networks<09:14:47.040> Class 09:14:47.510 --> 09:14:47.520 align:start position:0% the most nodes the fewest networks Class 09:14:47.520 --> 09:14:48.708 align:start position:0% the most nodes the fewest networks Class C<09:14:47.758> is<09:14:47.938> going<09:14:48.058> to<09:14:48.058> be<09:14:48.122> the<09:14:48.238> complete<09:14:48.480> opposite 09:14:48.708 --> 09:14:48.718 align:start position:0% C is going to be the complete opposite 09:14:48.718 --> 09:14:51.048 align:start position:0% C is going to be the complete opposite I'm<09:14:48.898> going<09:14:49.020> to<09:14:49.078> allow<09:14:49.258> for<09:14:49.438> the<09:14:49.738> most<09:14:50.058> nodes 09:14:51.048 --> 09:14:51.058 align:start position:0% I'm going to allow for the most nodes 09:14:51.058 --> 09:14:53.388 align:start position:0% I'm going to allow for the most nodes the<09:14:51.480> most<09:14:51.598> networks<09:14:52.200> rather<09:14:52.500> but<09:14:52.918> the<09:14:53.098> fewest 09:14:53.388 --> 09:14:53.398 align:start position:0% the most networks rather but the fewest 09:14:53.398 --> 09:14:56.868 align:start position:0% the most networks rather but the fewest nodes<09:14:54.058> okay<09:14:54.540> and<09:14:55.320> again<09:14:55.622> remember<09:14:56.460> these 09:14:56.868 --> 09:14:56.878 align:start position:0% nodes okay and again remember these 09:14:56.878 --> 09:14:58.908 align:start position:0% nodes okay and again remember these ranges<09:14:57.238> because<09:14:57.418> they<09:14:57.598> will<09:14:57.718> come<09:14:57.898> up<09:14:58.078> what<09:14:58.738> is 09:14:58.908 --> 09:14:58.918 align:start position:0% ranges because they will come up what is 09:14:58.918 --> 09:15:01.612 align:start position:0% ranges because they will come up what is make<09:14:59.282> a<09:14:59.640> private<09:14:59.878> IP<09:15:00.180> address<09:15:00.360> it<09:15:01.140> is<09:15:01.320> not 09:15:01.612 --> 09:15:01.622 align:start position:0% make a private IP address it is not 09:15:01.622 --> 09:15:04.790 align:start position:0% make a private IP address it is not routed<09:15:02.218> past<09:15:03.180> a<09:15:03.480> router<09:15:03.840> onto<09:15:04.500> the<09:15:04.622> public 09:15:04.790 --> 09:15:04.800 align:start position:0% routed past a router onto the public 09:15:04.800 --> 09:15:07.450 align:start position:0% routed past a router onto the public network<09:15:05.218> okay<09:15:05.878> we<09:15:06.718> also<09:15:06.898> talked<09:15:07.140> about<09:15:07.200> the 09:15:07.450 --> 09:15:07.460 align:start position:0% network okay we also talked about the 09:15:07.460 --> 09:15:09.708 align:start position:0% network okay we also talked about the ipv4<09:15:08.460> formulas<09:15:09.058> which<09:15:09.238> allow<09:15:09.480> us<09:15:09.598> to 09:15:09.708 --> 09:15:09.718 align:start position:0% ipv4 formulas which allow us to 09:15:09.718 --> 09:15:11.030 align:start position:0% ipv4 formulas which allow us to determine 09:15:11.030 --> 09:15:11.040 align:start position:0% determine 09:15:11.040 --> 09:15:12.950 align:start position:0% determine how<09:15:11.700> many<09:15:11.878> hosts 09:15:12.950 --> 09:15:12.960 align:start position:0% how many hosts 09:15:12.960 --> 09:15:15.650 align:start position:0% how many hosts or<09:15:13.558> how<09:15:13.800> many<09:15:13.918> networks<09:15:14.520> are<09:15:14.938> allowed<09:15:15.300> on<09:15:15.540> a 09:15:15.650 --> 09:15:15.660 align:start position:0% or how many networks are allowed on a 09:15:15.660 --> 09:15:18.112 align:start position:0% or how many networks are allowed on a network<09:15:15.840> and<09:15:16.800> that<09:15:16.980> is<09:15:17.098> where<09:15:17.282> the<09:15:17.520> x<09:15:17.640> or<09:15:17.820> the<09:15:18.000> y 09:15:18.112 --> 09:15:18.122 align:start position:0% network and that is where the x or the y 09:15:18.122 --> 09:15:20.088 align:start position:0% network and that is where the x or the y equals<09:15:18.598> the<09:15:18.718> number<09:15:18.898> of<09:15:19.140> hosts<09:15:19.622> or<09:15:19.860> network 09:15:20.088 --> 09:15:20.098 align:start position:0% equals the number of hosts or network 09:15:20.098 --> 09:15:22.908 align:start position:0% equals the number of hosts or network bits<09:15:21.238> we<09:15:21.598> defined<09:15:21.898> the<09:15:22.140> default<09:15:22.438> gateway 09:15:22.908 --> 09:15:22.918 align:start position:0% bits we defined the default gateway 09:15:22.918 --> 09:15:27.048 align:start position:0% bits we defined the default gateway which<09:15:23.820> is<09:15:24.000> what<09:15:24.238> I<09:15:24.418> need 09:15:27.048 --> 09:15:27.058 align:start position:0% 09:15:27.058 --> 09:15:29.290 align:start position:0% to get<09:15:27.480> out<09:15:27.598> to<09:15:27.782> the<09:15:27.960> WAN<09:15:28.320> it's<09:15:28.558> what<09:15:28.860> a<09:15:29.040> local 09:15:29.290 --> 09:15:29.300 align:start position:0% to get out to the WAN it's what a local 09:15:29.300 --> 09:15:31.612 align:start position:0% to get out to the WAN it's what a local device<09:15:30.300> a<09:15:30.598> node<09:15:30.840> on<09:15:30.960> the<09:15:31.078> local<09:15:31.140> area<09:15:31.378> network 09:15:31.612 --> 09:15:31.622 align:start position:0% device a node on the local area network 09:15:31.622 --> 09:15:34.310 align:start position:0% device a node on the local area network needs<09:15:32.098> to<09:15:32.340> go<09:15:32.640> to<09:15:32.758> this<09:15:32.938> default<09:15:33.300> gateway<09:15:33.718> and 09:15:34.310 --> 09:15:34.320 align:start position:0% needs to go to this default gateway and 09:15:34.320 --> 09:15:36.290 align:start position:0% needs to go to this default gateway and finally<09:15:34.558> we<09:15:34.800> Define<09:15:34.980> the<09:15:35.340> two<09:15:35.520> custom<09:15:35.820> IP 09:15:36.290 --> 09:15:36.300 align:start position:0% finally we Define the two custom IP 09:15:36.300 --> 09:15:38.510 align:start position:0% finally we Define the two custom IP address<09:15:36.480> schemes<09:15:37.140> the<09:15:37.800> one<09:15:37.918> which<09:15:38.098> allows<09:15:38.398> me 09:15:38.510 --> 09:15:38.520 align:start position:0% address schemes the one which allows me 09:15:38.520 --> 09:15:41.650 align:start position:0% address schemes the one which allows me for<09:15:38.820> variable<09:15:39.300> subnetting<09:15:40.140> and<09:15:40.800> the<09:15:41.040> other 09:15:41.650 --> 09:15:41.660 align:start position:0% for variable subnetting and the other 09:15:41.660 --> 09:15:45.170 align:start position:0% for variable subnetting and the other cider<09:15:42.660> which<09:15:43.320> allows<09:15:43.860> me<09:15:44.040> to 09:15:45.170 --> 09:15:45.180 align:start position:0% cider which allows me to 09:15:45.180 --> 09:15:48.170 align:start position:0% cider which allows me to use<09:15:45.782> a<09:15:46.078> slash<09:15:46.500> and<09:15:47.040> then<09:15:47.160> put<09:15:47.398> a<09:15:47.520> number<09:15:47.700> that 09:15:48.170 --> 09:15:48.180 align:start position:0% use a slash and then put a number that 09:15:48.180 --> 09:15:50.330 align:start position:0% use a slash and then put a number that number<09:15:48.418> representing 09:15:50.330 --> 09:15:50.340 align:start position:0% number representing 09:15:50.340 --> 09:15:52.548 align:start position:0% number representing the<09:15:50.938> number<09:15:51.122> of 09:15:52.548 --> 09:15:52.558 align:start position:0% the number of 09:15:52.558 --> 09:15:58.068 align:start position:0% the number of Network<09:15:53.098> bits<09:15:54.180> in<09:15:54.660> the<09:15:54.782> subnet<09:15:55.140> mask 09:15:58.068 --> 09:15:58.078 align:start position:0% 09:15:58.078 --> 09:16:00.650 align:start position:0% right<09:15:58.558> so<09:15:59.160> the<09:15:59.460> most<09:15:59.578> popular<09:15:59.820> of<09:16:00.122> course<09:16:00.238> 24 09:16:00.650 --> 09:16:00.660 align:start position:0% right so the most popular of course 24 09:16:00.660 --> 09:16:03.530 align:start position:0% right so the most popular of course 24 would<09:16:01.258> be<09:16:01.320> for<09:16:01.558> a<09:16:01.738> class<09:16:01.860> C 09:16:03.530 --> 09:16:03.540 align:start position:0% would be for a class C 09:16:03.540 --> 09:16:07.368 align:start position:0% would be for a class C 16b<09:16:04.500> for<09:16:04.738> a<09:16:04.918> class<09:16:05.098> B<09:16:05.460> and<09:16:06.238> 8<09:16:06.480> would<09:16:06.782> be<09:16:06.898> for<09:16:07.200> a 09:16:07.368 --> 09:16:07.378 align:start position:0% 16b for a class B and 8 would be for a 09:16:07.378 --> 09:16:10.548 align:start position:0% 16b for a class B and 8 would be for a class<09:16:07.700> A<09:16:08.700> because<09:16:09.180> if<09:16:09.660> we<09:16:09.840> had<09:16:09.960> a<09:16:10.078> slash<09:16:10.378> eight 09:16:10.548 --> 09:16:10.558 align:start position:0% class A because if we had a slash eight 09:16:10.558 --> 09:16:11.990 align:start position:0% class A because if we had a slash eight that<09:16:10.800> would<09:16:10.980> mean<09:16:11.098> the<09:16:11.282> subnet<09:16:11.640> mask<09:16:11.820> is 09:16:11.990 --> 09:16:12.000 align:start position:0% that would mean the subnet mask is 09:16:12.000 --> 09:16:17.820 align:start position:0% that would mean the subnet mask is 255.0.0.0 09:16:17.820 --> 09:16:17.830 align:start position:0% 09:16:17.830 --> 09:16:25.548 align:start position:0% [Music] 09:16:25.548 --> 09:16:25.558 align:start position:0% [Music] 09:16:25.558 --> 09:16:38.272 align:start position:0% [Music] foreign 09:16:38.272 --> 09:16:38.282 align:start position:0% 09:16:38.282 --> 09:16:41.388 align:start position:0% Network<09:16:39.000> routing<09:16:39.598> and<09:16:39.960> IP<09:16:40.320> addressing 09:16:41.388 --> 09:16:41.398 align:start position:0% Network routing and IP addressing 09:16:41.398 --> 09:16:47.690 align:start position:0% Network routing and IP addressing data<09:16:42.300> delivery<09:16:42.782> techniques<09:16:43.558> and<09:16:44.398> IPv6 09:16:47.690 --> 09:16:47.700 align:start position:0% 09:16:47.700 --> 09:16:49.790 align:start position:0% now<09:16:48.122> we've<09:16:48.300> talked<09:16:48.598> a<09:16:48.782> lot<09:16:48.898> about<09:16:49.320> IP 09:16:49.790 --> 09:16:49.800 align:start position:0% now we've talked a lot about IP 09:16:49.800 --> 09:16:53.208 align:start position:0% now we've talked a lot about IP addressing<09:16:50.282> when<09:16:50.520> it<09:16:50.640> comes<09:16:50.938> to<09:16:51.122> ipv4<09:16:52.078> or<09:16:52.980> the 09:16:53.208 --> 09:16:53.218 align:start position:0% addressing when it comes to ipv4 or the 09:16:53.218 --> 09:16:56.088 align:start position:0% addressing when it comes to ipv4 or the Internet<09:16:53.340> Protocol<09:16:53.878> version<09:16:54.238> 4<09:16:54.660> but<09:16:55.622> fairly 09:16:56.088 --> 09:16:56.098 align:start position:0% Internet Protocol version 4 but fairly 09:16:56.098 --> 09:16:59.630 align:start position:0% Internet Protocol version 4 but fairly recently<09:16:56.840> IPv6<09:16:57.840> or<09:16:58.200> IP<09:16:58.558> or<09:16:58.918> Internet<09:16:59.098> Protocol 09:16:59.630 --> 09:16:59.640 align:start position:0% recently IPv6 or IP or Internet Protocol 09:16:59.640 --> 09:17:02.810 align:start position:0% recently IPv6 or IP or Internet Protocol version<09:17:00.058> 6<09:17:00.480> was<09:17:00.840> released<09:17:01.320> and<09:17:01.860> has<09:17:02.098> now<09:17:02.340> begun 09:17:02.810 --> 09:17:02.820 align:start position:0% version 6 was released and has now begun 09:17:02.820 --> 09:17:05.928 align:start position:0% version 6 was released and has now begun to<09:17:03.480> be<09:17:03.598> implemented<09:17:04.200> across<09:17:04.918> the<09:17:05.098> world<09:17:05.340> in 09:17:05.928 --> 09:17:05.938 align:start position:0% to be implemented across the world in 09:17:05.938 --> 09:17:08.990 align:start position:0% to be implemented across the world in every<09:17:06.180> Network<09:17:06.360> situation<09:17:07.282> so<09:17:08.282> in<09:17:08.700> this 09:17:08.990 --> 09:17:09.000 align:start position:0% every Network situation so in this 09:17:09.000 --> 09:17:11.748 align:start position:0% every Network situation so in this module<09:17:09.540> we're<09:17:10.078> going<09:17:10.378> to<09:17:10.680> discuss<09:17:11.098> the<09:17:11.578> Core 09:17:11.748 --> 09:17:11.758 align:start position:0% module we're going to discuss the Core 09:17:11.758 --> 09:17:14.690 align:start position:0% module we're going to discuss the Core Concepts<09:17:12.418> that<09:17:12.660> are<09:17:12.782> involved<09:17:13.258> with<09:17:13.700> IPv6 09:17:14.690 --> 09:17:14.700 align:start position:0% Concepts that are involved with IPv6 09:17:14.700 --> 09:17:18.112 align:start position:0% Concepts that are involved with IPv6 addressing<09:17:15.540> and<09:17:16.378> some<09:17:16.622> of<09:17:16.800> the<09:17:17.040> data<09:17:17.520> delivery 09:17:18.112 --> 09:17:18.122 align:start position:0% addressing and some of the data delivery 09:17:18.122 --> 09:17:21.290 align:start position:0% addressing and some of the data delivery techniques<09:17:18.898> as<09:17:19.200> well<09:17:19.438> so<09:17:20.282> at<09:17:20.578> the<09:17:20.758> completion 09:17:21.290 --> 09:17:21.300 align:start position:0% techniques as well so at the completion 09:17:21.300 --> 09:17:23.510 align:start position:0% techniques as well so at the completion of<09:17:21.480> this<09:17:21.718> module<09:17:22.200> we're<09:17:22.800> going<09:17:23.040> to<09:17:23.160> have<09:17:23.282> a 09:17:23.510 --> 09:17:23.520 align:start position:0% of this module we're going to have a 09:17:23.520 --> 09:17:26.030 align:start position:0% of this module we're going to have a complete<09:17:23.878> understanding<09:17:24.598> of<09:17:25.078> the<09:17:25.500> properties 09:17:26.030 --> 09:17:26.040 align:start position:0% complete understanding of the properties 09:17:26.040 --> 09:17:30.408 align:start position:0% complete understanding of the properties of<09:17:26.758> IP<09:17:27.300> version<09:17:27.960> 6<09:17:28.438> or<09:17:28.738> IPv6 09:17:30.408 --> 09:17:30.418 align:start position:0% of IP version 6 or IPv6 09:17:30.418 --> 09:17:31.490 align:start position:0% of IP version 6 or IPv6 and<09:17:30.898> we're<09:17:31.020> going<09:17:31.078> to<09:17:31.140> be<09:17:31.258> able<09:17:31.320> to 09:17:31.490 --> 09:17:31.500 align:start position:0% and we're going to be able to 09:17:31.500 --> 09:17:35.568 align:start position:0% and we're going to be able to differentiate<09:17:32.160> between<09:17:32.898> IPv6<09:17:33.898> and<09:17:34.738> ipv4 09:17:35.568 --> 09:17:35.578 align:start position:0% differentiate between IPv6 and ipv4 09:17:35.578 --> 09:17:36.888 align:start position:0% differentiate between IPv6 and ipv4 which<09:17:35.938> is<09:17:36.058> the<09:17:36.180> one<09:17:36.300> we've<09:17:36.540> been<09:17:36.660> talking 09:17:36.888 --> 09:17:36.898 align:start position:0% which is the one we've been talking 09:17:36.898 --> 09:17:39.170 align:start position:0% which is the one we've been talking about<09:17:37.140> up<09:17:37.558> into<09:17:37.738> this<09:17:38.040> point<09:17:38.282> as<09:17:38.878> a<09:17:39.058> reminder 09:17:39.170 --> 09:17:39.180 align:start position:0% about up into this point as a reminder 09:17:39.180 --> 09:17:43.548 align:start position:0% about up into this point as a reminder ipv4<09:17:40.078> is<09:17:40.622> that<09:17:40.800> IP<09:17:41.098> address<09:17:41.540> that<09:17:42.540> is<09:17:42.718> 38-bit 09:17:43.548 --> 09:17:43.558 align:start position:0% ipv4 is that IP address that is 38-bit 09:17:43.558 --> 09:17:48.470 align:start position:0% ipv4 is that IP address that is 38-bit 32<09:17:44.282> bits<09:17:44.640> and<09:17:45.000> divided<09:17:45.480> into<09:17:45.660> four<09:17:46.258> octets 09:17:48.470 --> 09:17:48.480 align:start position:0% 32 bits and divided into four octets 09:17:48.480 --> 09:17:50.150 align:start position:0% 32 bits and divided into four octets and<09:17:48.782> we're<09:17:48.898> also<09:17:49.140> going<09:17:49.258> to<09:17:49.378> outline<09:17:49.680> some<09:17:49.980> of 09:17:50.150 --> 09:17:50.160 align:start position:0% and we're also going to outline some of 09:17:50.160 --> 09:17:52.450 align:start position:0% and we're also going to outline some of the<09:17:50.340> improvements<09:17:51.058> in<09:17:51.238> the<09:17:51.418> mechanisms<09:17:51.960> of 09:17:52.450 --> 09:17:52.460 align:start position:0% the improvements in the mechanisms of 09:17:52.460 --> 09:17:55.850 align:start position:0% the improvements in the mechanisms of IPv6<09:17:53.460> and<09:17:54.180> why<09:17:54.360> we<09:17:54.660> needed<09:17:55.020> to<09:17:55.258> have<09:17:55.438> another 09:17:55.850 --> 09:17:55.860 align:start position:0% IPv6 and why we needed to have another 09:17:55.860 --> 09:17:58.190 align:start position:0% IPv6 and why we needed to have another version<09:17:56.282> of<09:17:56.640> Ip<09:17:57.058> addressing 09:17:58.190 --> 09:17:58.200 align:start position:0% version of Ip addressing 09:17:58.200 --> 09:17:59.630 align:start position:0% version of Ip addressing we're<09:17:58.622> also<09:17:58.860> going<09:17:58.980> to<09:17:59.040> cover<09:17:59.160> the<09:17:59.460> different 09:17:59.630 --> 09:17:59.640 align:start position:0% we're also going to cover the different 09:17:59.640 --> 09:18:03.470 align:start position:0% we're also going to cover the different data<09:18:00.300> delivery<09:18:00.718> techniques<09:18:01.640> as<09:18:02.640> well<09:18:02.820> as<09:18:03.000> what 09:18:03.470 --> 09:18:03.480 align:start position:0% data delivery techniques as well as what 09:18:03.480 --> 09:18:05.450 align:start position:0% data delivery techniques as well as what a<09:18:03.718> connection<09:18:03.898> is<09:18:04.378> different<09:18:05.160> connection 09:18:05.450 --> 09:18:05.460 align:start position:0% a connection is different connection 09:18:05.460 --> 09:18:07.310 align:start position:0% a connection is different connection modes<09:18:06.000> and<09:18:06.122> we<09:18:06.300> touched<09:18:06.598> on<09:18:06.660> these<09:18:06.898> briefly 09:18:07.310 --> 09:18:07.320 align:start position:0% modes and we touched on these briefly 09:18:07.320 --> 09:18:09.112 align:start position:0% modes and we touched on these briefly such<09:18:07.622> as<09:18:07.800> connection<09:18:08.040> oriented<09:18:08.820> and 09:18:09.112 --> 09:18:09.122 align:start position:0% such as connection oriented and 09:18:09.122 --> 09:18:11.510 align:start position:0% such as connection oriented and connection<09:18:09.300> less<09:18:09.782> and<09:18:10.680> they're<09:18:11.040> transmit 09:18:11.510 --> 09:18:11.520 align:start position:0% connection less and they're transmit 09:18:11.520 --> 09:18:14.330 align:start position:0% connection less and they're transmit types<09:18:12.020> finally<09:18:13.020> we're<09:18:13.438> going<09:18:13.622> to<09:18:13.800> go<09:18:13.918> further 09:18:14.330 --> 09:18:14.340 align:start position:0% types finally we're going to go further 09:18:14.340 --> 09:18:16.970 align:start position:0% types finally we're going to go further into<09:18:14.640> data<09:18:15.238> flow<09:18:15.480> or<09:18:16.020> flow<09:18:16.320> control<09:18:16.558> which 09:18:16.970 --> 09:18:16.980 align:start position:0% into data flow or flow control which 09:18:16.980 --> 09:18:18.650 align:start position:0% into data flow or flow control which we've<09:18:17.282> talked<09:18:17.578> about<09:18:17.700> a<09:18:18.122> bit<09:18:18.300> and<09:18:18.480> we've 09:18:18.650 --> 09:18:18.660 align:start position:0% we've talked about a bit and we've 09:18:18.660 --> 09:18:21.708 align:start position:0% we've talked about a bit and we've mentioned<09:18:19.020> a<09:18:19.140> bit<09:18:19.520> buffering<09:18:20.520> and<09:18:21.238> data 09:18:21.708 --> 09:18:21.718 align:start position:0% mentioned a bit buffering and data 09:18:21.718 --> 09:18:24.408 align:start position:0% mentioned a bit buffering and data Windows<09:18:22.200> these<09:18:22.680> are<09:18:22.800> all<09:18:23.180> techniques<09:18:24.180> that 09:18:24.408 --> 09:18:24.418 align:start position:0% Windows these are all techniques that 09:18:24.418 --> 09:18:28.490 align:start position:0% Windows these are all techniques that allow<09:18:24.782> data<09:18:25.320> to<09:18:25.438> be<09:18:25.622> sent<09:18:25.918> over<09:18:26.398> a<09:18:27.360> network<09:18:27.660> in 09:18:28.490 --> 09:18:28.500 align:start position:0% allow data to be sent over a network in 09:18:28.500 --> 09:18:31.548 align:start position:0% allow data to be sent over a network in varying<09:18:28.918> ways<09:18:29.398> and<09:18:30.180> finally<09:18:30.540> also<09:18:31.320> we're 09:18:31.548 --> 09:18:31.558 align:start position:0% varying ways and finally also we're 09:18:31.558 --> 09:18:33.650 align:start position:0% varying ways and finally also we're going<09:18:31.738> to<09:18:31.860> talk<09:18:32.040> about<09:18:32.360> error<09:18:33.360> detection 09:18:33.650 --> 09:18:33.660 align:start position:0% going to talk about error detection 09:18:33.660 --> 09:18:36.048 align:start position:0% going to talk about error detection methods<09:18:34.200> that<09:18:34.680> way<09:18:34.800> we<09:18:35.098> know<09:18:35.282> when<09:18:35.640> data 09:18:36.048 --> 09:18:36.058 align:start position:0% methods that way we know when data 09:18:36.058 --> 09:18:38.450 align:start position:0% methods that way we know when data arrives<09:18:36.360> on<09:18:36.598> the<09:18:36.782> other<09:18:36.960> end<09:18:37.258> we<09:18:38.040> can<09:18:38.218> double 09:18:38.450 --> 09:18:38.460 align:start position:0% arrives on the other end we can double 09:18:38.460 --> 09:18:40.248 align:start position:0% arrives on the other end we can double check<09:18:38.758> it<09:18:39.000> to<09:18:39.180> make<09:18:39.360> sure<09:18:39.418> it<09:18:39.660> is<09:18:39.718> the<09:18:39.960> data 09:18:40.248 --> 09:18:40.258 align:start position:0% check it to make sure it is the data 09:18:40.258 --> 09:18:42.588 align:start position:0% check it to make sure it is the data that<09:18:40.378> was<09:18:40.680> in<09:18:40.918> fact<09:18:41.040> sent 09:18:42.588 --> 09:18:42.598 align:start position:0% that was in fact sent 09:18:42.598 --> 09:18:46.190 align:start position:0% that was in fact sent so<09:18:43.500> in<09:18:44.160> the<09:18:44.282> last<09:18:44.460> module<09:18:45.122> we<09:18:45.718> learned<09:18:46.020> about 09:18:46.190 --> 09:18:46.200 align:start position:0% so in the last module we learned about 09:18:46.200 --> 09:18:49.548 align:start position:0% so in the last module we learned about the<09:18:46.738> ipv4<09:18:47.718> addressing<09:18:48.718> scheme<09:18:49.020> and<09:18:49.140> we<09:18:49.320> talked 09:18:49.548 --> 09:18:49.558 align:start position:0% the ipv4 addressing scheme and we talked 09:18:49.558 --> 09:18:50.990 align:start position:0% the ipv4 addressing scheme and we talked about<09:18:49.622> some<09:18:49.980> aspects<09:18:50.520> of<09:18:50.640> How<09:18:50.820> It's 09:18:50.990 --> 09:18:51.000 align:start position:0% about some aspects of How It's 09:18:51.000 --> 09:18:54.650 align:start position:0% about some aspects of How It's implemented<09:18:51.540> now<09:18:52.140> IPv6<09:18:53.040> is<09:18:53.820> the<09:18:54.058> successor<09:18:54.540> to 09:18:54.650 --> 09:18:54.660 align:start position:0% implemented now IPv6 is the successor to 09:18:54.660 --> 09:18:56.990 align:start position:0% implemented now IPv6 is the successor to ibv4<09:18:55.320> and<09:18:55.558> it<09:18:55.738> offers<09:18:56.160> a<09:18:56.282> lot<09:18:56.398> of<09:18:56.520> benefits 09:18:56.990 --> 09:18:57.000 align:start position:0% ibv4 and it offers a lot of benefits 09:18:57.000 --> 09:18:58.728 align:start position:0% ibv4 and it offers a lot of benefits over<09:18:57.238> its<09:18:57.598> predecessor 09:18:58.728 --> 09:18:58.738 align:start position:0% over its predecessor 09:18:58.738 --> 09:19:00.650 align:start position:0% over its predecessor the<09:18:59.098> first<09:18:59.218> major<09:18:59.640> Improvement<09:19:00.180> that<09:19:00.480> came 09:19:00.650 --> 09:19:00.660 align:start position:0% the first major Improvement that came 09:19:00.660 --> 09:19:02.208 align:start position:0% the first major Improvement that came with<09:19:00.840> this<09:19:01.020> new<09:19:01.200> version<09:19:01.378> is<09:19:01.918> that<09:19:02.098> there's 09:19:02.208 --> 09:19:02.218 align:start position:0% with this new version is that there's 09:19:02.218 --> 09:19:04.908 align:start position:0% with this new version is that there's been<09:19:02.398> an<09:19:02.758> exponential<09:19:03.660> increase<09:19:04.200> in<09:19:04.738> the 09:19:04.908 --> 09:19:04.918 align:start position:0% been an exponential increase in the 09:19:04.918 --> 09:19:07.790 align:start position:0% been an exponential increase in the number<09:19:05.098> of<09:19:05.660> possible<09:19:06.660> addresses<09:19:07.438> that<09:19:07.680> are 09:19:07.790 --> 09:19:07.800 align:start position:0% number of possible addresses that are 09:19:07.800 --> 09:19:08.650 align:start position:0% number of possible addresses that are available 09:19:08.650 --> 09:19:08.660 align:start position:0% available 09:19:08.660 --> 09:19:11.208 align:start position:0% available several<09:19:09.660> other<09:19:09.840> features<09:19:10.438> were<09:19:10.800> added<09:19:11.098> to 09:19:11.208 --> 09:19:11.218 align:start position:0% several other features were added to 09:19:11.218 --> 09:19:12.830 align:start position:0% several other features were added to this<09:19:11.398> addressing<09:19:11.878> scheme<09:19:12.122> as<09:19:12.238> well<09:19:12.360> such<09:19:12.660> as 09:19:12.830 --> 09:19:12.840 align:start position:0% this addressing scheme as well such as 09:19:12.840 --> 09:19:14.110 align:start position:0% this addressing scheme as well such as security 09:19:14.110 --> 09:19:14.120 align:start position:0% security 09:19:14.120 --> 09:19:16.190 align:start position:0% security improved<09:19:15.120> composition<09:19:15.540> for<09:19:15.840> what<09:19:15.960> are<09:19:16.080> called 09:19:16.190 --> 09:19:16.200 align:start position:0% improved composition for what are called 09:19:16.200 --> 09:19:19.370 align:start position:0% improved composition for what are called unicast<09:19:16.916> addresses<09:19:17.780> header<09:19:18.780> simplification 09:19:19.370 --> 09:19:19.380 align:start position:0% unicast addresses header simplification 09:19:19.380 --> 09:19:22.730 align:start position:0% unicast addresses header simplification and<09:19:19.860> how<09:19:20.096> they're<09:19:20.280> sent<09:19:20.660> and<09:19:21.660> a<09:19:22.080> hierarchical 09:19:22.730 --> 09:19:22.740 align:start position:0% and how they're sent and a hierarchical 09:19:22.740 --> 09:19:25.970 align:start position:0% and how they're sent and a hierarchical addressing<09:19:23.580> for<09:19:24.180> what<09:19:24.540> some<09:19:25.256> would<09:19:25.500> suggest 09:19:25.970 --> 09:19:25.980 align:start position:0% addressing for what some would suggest 09:19:25.980 --> 09:19:28.610 align:start position:0% addressing for what some would suggest is<09:19:26.220> easier<09:19:26.756> routing<09:19:27.240> and<09:19:28.020> there's<09:19:28.256> also<09:19:28.500> a 09:19:28.610 --> 09:19:28.620 align:start position:0% is easier routing and there's also a 09:19:28.620 --> 09:19:30.770 align:start position:0% is easier routing and there's also a support<09:19:28.800> for<09:19:29.220> what<09:19:29.460> we<09:19:29.580> call<09:19:29.756> time<09:19:30.180> sensitive 09:19:30.770 --> 09:19:30.780 align:start position:0% support for what we call time sensitive 09:19:30.780 --> 09:19:32.690 align:start position:0% support for what we call time sensitive traffic<09:19:31.080> or<09:19:31.436> traffic<09:19:31.620> that<09:19:31.980> needs<09:19:32.280> to<09:19:32.460> be 09:19:32.690 --> 09:19:32.700 align:start position:0% traffic or traffic that needs to be 09:19:32.700 --> 09:19:34.490 align:start position:0% traffic or traffic that needs to be received<09:19:33.540> in<09:19:33.660> a<09:19:33.780> certain<09:19:33.900> amount<09:19:34.140> of<09:19:34.320> time 09:19:34.490 --> 09:19:34.500 align:start position:0% received in a certain amount of time 09:19:34.500 --> 09:19:36.890 align:start position:0% received in a certain amount of time such<09:19:34.980> as<09:19:35.160> voice<09:19:35.700> over<09:19:35.936> IP<09:19:36.360> and<09:19:36.540> gaming<09:19:36.780> and 09:19:36.890 --> 09:19:36.900 align:start position:0% such as voice over IP and gaming and 09:19:36.900 --> 09:19:38.470 align:start position:0% such as voice over IP and gaming and we're<09:19:37.020> going<09:19:37.140> to<09:19:37.200> look<09:19:37.320> at<09:19:37.436> all<09:19:37.620> this<09:19:37.916> shortly 09:19:38.470 --> 09:19:38.480 align:start position:0% we're going to look at all this shortly 09:19:38.480 --> 09:19:45.650 align:start position:0% we're going to look at all this shortly so<09:19:39.480> the<09:19:40.520> IPv6<09:19:41.520> addressing<09:19:42.360> scheme<09:19:42.740> uses<09:19:43.740> a<09:19:44.660> 128 09:19:45.650 --> 09:19:45.660 align:start position:0% so the IPv6 addressing scheme uses a 128 09:19:45.660 --> 09:19:49.070 align:start position:0% so the IPv6 addressing scheme uses a 128 bit<09:19:46.220> binary<09:19:47.220> address<09:19:47.580> this<09:19:48.360> is<09:19:48.480> different<09:19:48.660> of 09:19:49.070 --> 09:19:49.080 align:start position:0% bit binary address this is different of 09:19:49.080 --> 09:19:53.110 align:start position:0% bit binary address this is different of course<09:19:49.256> from<09:19:50.240> ipv4<09:19:51.240> which<09:19:51.840> again<09:19:52.020> uses<09:19:52.500> a 09:19:53.110 --> 09:19:53.120 align:start position:0% course from ipv4 which again uses a 09:19:53.120 --> 09:19:56.810 align:start position:0% course from ipv4 which again uses a 32-bit<09:19:54.120> address<09:19:54.500> so<09:19:55.500> this<09:19:55.980> means<09:19:56.340> therefore 09:19:56.810 --> 09:19:56.820 align:start position:0% 32-bit address so this means therefore 09:19:56.820 --> 09:19:58.906 align:start position:0% 32-bit address so this means therefore that<09:19:57.540> there<09:19:57.780> are<09:19:57.960> two 09:19:58.906 --> 09:19:58.916 align:start position:0% that there are two 09:19:58.916 --> 09:20:03.650 align:start position:0% that there are two to<09:19:59.660> 128<09:20:00.660> power<09:20:01.080> possible<09:20:02.120> addresses<09:20:03.120> as 09:20:03.650 --> 09:20:03.660 align:start position:0% to 128 power possible addresses as 09:20:03.660 --> 09:20:07.906 align:start position:0% to 128 power possible addresses as opposed<09:20:04.020> to<09:20:04.080> 2<09:20:04.980> to<09:20:05.220> the<09:20:05.340> 32<09:20:05.820> power<09:20:06.180> with<09:20:07.500> um<09:20:07.500> IP 09:20:07.906 --> 09:20:07.916 align:start position:0% opposed to 2 to the 32 power with um IP 09:20:07.916 --> 09:20:09.830 align:start position:0% opposed to 2 to the 32 power with um IP address<09:20:08.160> 4. 09:20:09.830 --> 09:20:09.840 align:start position:0% address 4. 09:20:09.840 --> 09:20:12.950 align:start position:0% address 4. and<09:20:10.256> this<09:20:10.500> means<09:20:10.916> therefore<09:20:11.880> that<09:20:12.480> there<09:20:12.720> are 09:20:12.950 --> 09:20:12.960 align:start position:0% and this means therefore that there are 09:20:12.960 --> 09:20:14.050 align:start position:0% and this means therefore that there are around 09:20:14.050 --> 09:20:14.060 align:start position:0% around 09:20:14.060 --> 09:20:15.850 align:start position:0% around 340 09:20:15.850 --> 09:20:15.860 align:start position:0% 340 09:20:15.860 --> 09:20:18.290 align:start position:0% 340 undecilion<09:20:16.860> I'm<09:20:17.400> going<09:20:17.580> to<09:20:17.640> write<09:20:17.820> that<09:20:18.060> out 09:20:18.290 --> 09:20:18.300 align:start position:0% undecilion I'm going to write that out 09:20:18.300 --> 09:20:19.550 align:start position:0% undecilion I'm going to write that out so<09:20:18.540> that's<09:20:18.720> a<09:20:18.900> word<09:20:19.080> that<09:20:19.320> you<09:20:19.436> probably 09:20:19.550 --> 09:20:19.560 align:start position:0% so that's a word that you probably 09:20:19.560 --> 09:20:26.086 align:start position:0% so that's a word that you probably haven't<09:20:19.800> seen<09:20:20.220> a<09:20:20.400> lot<09:20:20.520> on 09:20:26.086 --> 09:20:26.096 align:start position:0% 09:20:26.096 --> 09:20:29.030 align:start position:0% decillion<09:20:27.320> addresses<09:20:28.320> and<09:20:28.620> to<09:20:28.740> put<09:20:28.916> that 09:20:29.030 --> 09:20:29.040 align:start position:0% decillion addresses and to put that 09:20:29.040 --> 09:20:32.086 align:start position:0% decillion addresses and to put that another<09:20:29.220> way<09:20:29.520> it's<09:20:30.180> enough<09:20:30.360> for<09:20:30.840> one<09:20:31.620> trillion 09:20:32.086 --> 09:20:32.096 align:start position:0% another way it's enough for one trillion 09:20:32.096 --> 09:20:35.586 align:start position:0% another way it's enough for one trillion people<09:20:32.340> to<09:20:33.180> each<09:20:33.416> have<09:20:33.660> a<09:20:34.500> trillion<09:20:34.916> addresses 09:20:35.586 --> 09:20:35.596 align:start position:0% people to each have a trillion addresses 09:20:35.596 --> 09:20:38.870 align:start position:0% people to each have a trillion addresses or<09:20:36.596> for<09:20:37.140> an<09:20:37.380> IP<09:20:37.680> address<09:20:37.860> for<09:20:38.340> every<09:20:38.580> single 09:20:38.870 --> 09:20:38.880 align:start position:0% or for an IP address for every single 09:20:38.880 --> 09:20:41.926 align:start position:0% or for an IP address for every single grain<09:20:39.180> of<09:20:39.360> sand<09:20:39.596> on<09:20:40.020> the<09:20:40.140> earth<09:20:40.520> times<09:20:41.520> a 09:20:41.926 --> 09:20:41.936 align:start position:0% grain of sand on the earth times a 09:20:41.936 --> 09:20:45.350 align:start position:0% grain of sand on the earth times a trillion<09:20:42.360> Earths<09:20:42.840> give<09:20:43.020> or<09:20:43.200> take<09:20:43.380> a<09:20:43.560> bit<09:20:43.800> so<09:20:44.756> if 09:20:45.350 --> 09:20:45.360 align:start position:0% trillion Earths give or take a bit so if 09:20:45.360 --> 09:20:48.230 align:start position:0% trillion Earths give or take a bit so if the<09:20:45.916> 128-bit<09:20:46.916> address<09:20:47.096> were<09:20:47.520> written<09:20:47.820> out<09:20:47.936> in 09:20:48.230 --> 09:20:48.240 align:start position:0% the 128-bit address were written out in 09:20:48.240 --> 09:20:50.406 align:start position:0% the 128-bit address were written out in binary<09:20:48.660> it<09:20:49.020> would<09:20:49.256> be 09:20:50.406 --> 09:20:50.416 align:start position:0% binary it would be 09:20:50.416 --> 09:20:54.830 align:start position:0% binary it would be 128<09:20:51.800> ones<09:20:52.800> and<09:20:53.160> zeros<09:20:53.756> because<09:20:54.120> that<09:20:54.540> is 09:20:54.830 --> 09:20:54.840 align:start position:0% 128 ones and zeros because that is 09:20:54.840 --> 09:20:56.690 align:start position:0% 128 ones and zeros because that is binary 09:20:56.690 --> 09:20:56.700 align:start position:0% binary 09:20:56.700 --> 09:20:59.870 align:start position:0% binary and<09:20:57.360> even<09:20:57.540> in<09:20:57.840> decimal<09:20:58.256> form<09:20:58.500> that's<09:20:59.220> a<09:20:59.580> pretty 09:20:59.870 --> 09:20:59.880 align:start position:0% and even in decimal form that's a pretty 09:20:59.880 --> 09:21:02.030 align:start position:0% and even in decimal form that's a pretty hard<09:21:00.240> to<09:21:00.540> read<09:21:00.720> and<09:21:00.960> keep<09:21:01.140> track<09:21:01.320> of<09:21:01.560> so 09:21:02.030 --> 09:21:02.040 align:start position:0% hard to read and keep track of so 09:21:02.040 --> 09:21:05.290 align:start position:0% hard to read and keep track of so because<09:21:02.220> of<09:21:02.460> this<09:21:02.700> we<09:21:03.180> use<09:21:03.360> what's<09:21:03.960> called 09:21:05.290 --> 09:21:05.300 align:start position:0% because of this we use what's called 09:21:05.300 --> 09:21:07.246 align:start position:0% because of this we use what's called hexadecimal 09:21:07.246 --> 09:21:07.256 align:start position:0% hexadecimal 09:21:07.256 --> 09:21:11.870 align:start position:0% hexadecimal as<09:21:07.916> the<09:21:08.220> format<09:21:08.640> in<09:21:09.120> which<09:21:09.500> uh<09:21:10.640> IPv6<09:21:11.640> is 09:21:11.870 --> 09:21:11.880 align:start position:0% as the format in which uh IPv6 is 09:21:11.880 --> 09:21:14.390 align:start position:0% as the format in which uh IPv6 is written<09:21:12.300> and<09:21:12.780> if<09:21:12.900> you<09:21:13.080> imagine<09:21:13.320> from<09:21:13.980> the<09:21:14.160> name 09:21:14.390 --> 09:21:14.400 align:start position:0% written and if you imagine from the name 09:21:14.400 --> 09:21:19.310 align:start position:0% written and if you imagine from the name hex<09:21:15.436> uh<09:21:16.436> binary<09:21:17.220> is<09:21:18.120> a<09:21:18.300> base<09:21:18.416> 2<09:21:18.660> system<09:21:18.960> meaning 09:21:19.310 --> 09:21:19.320 align:start position:0% hex uh binary is a base 2 system meaning 09:21:19.320 --> 09:21:21.470 align:start position:0% hex uh binary is a base 2 system meaning that<09:21:19.560> we<09:21:19.740> take<09:21:19.916> everything<09:21:20.160> to<09:21:20.820> the<09:21:21.000> power<09:21:21.240> of 09:21:21.470 --> 09:21:21.480 align:start position:0% that we take everything to the power of 09:21:21.480 --> 09:21:24.830 align:start position:0% that we take everything to the power of two<09:21:21.660> so<09:21:22.256> we<09:21:22.436> have<09:21:22.620> the<09:21:23.220> ones<09:21:23.640> place<09:21:23.880> and<09:21:24.720> then 09:21:24.830 --> 09:21:24.840 align:start position:0% two so we have the ones place and then 09:21:24.840 --> 09:21:27.230 align:start position:0% two so we have the ones place and then we<09:21:25.140> have<09:21:25.380> the<09:21:25.740> two<09:21:25.916> place<09:21:26.220> and<09:21:26.520> then<09:21:26.700> we<09:21:27.000> have 09:21:27.230 --> 09:21:27.240 align:start position:0% we have the two place and then we have 09:21:27.240 --> 09:21:30.110 align:start position:0% we have the two place and then we have the<09:21:27.900> fourth<09:21:28.320> place<09:21:28.380> and<09:21:28.680> so<09:21:28.800> on<09:21:28.980> and<09:21:29.160> so<09:21:29.340> forth 09:21:30.110 --> 09:21:30.120 align:start position:0% the fourth place and so on and so forth 09:21:30.120 --> 09:21:33.890 align:start position:0% the fourth place and so on and so forth with<09:21:31.020> decimal<09:21:31.680> which<09:21:32.280> is<09:21:32.460> a<09:21:33.000> base<09:21:33.180> 10<09:21:33.480> system 09:21:33.890 --> 09:21:33.900 align:start position:0% with decimal which is a base 10 system 09:21:33.900 --> 09:21:38.510 align:start position:0% with decimal which is a base 10 system we<09:21:34.680> have<09:21:34.980> the<09:21:35.580> ones<09:21:35.756> place<09:21:36.180> the<09:21:36.900> tens<09:21:37.080> place 09:21:38.510 --> 09:21:38.520 align:start position:0% we have the ones place the tens place 09:21:38.520 --> 09:21:40.670 align:start position:0% we have the ones place the tens place the<09:21:39.120> hundreds<09:21:39.540> place<09:21:39.780> which<09:21:40.140> is<09:21:40.256> ten<09:21:40.500> times 09:21:40.670 --> 09:21:40.680 align:start position:0% the hundreds place which is ten times 09:21:40.680 --> 09:21:44.030 align:start position:0% the hundreds place which is ten times ten<09:21:41.096> the<09:21:41.820> thousands<09:21:42.360> place<09:21:42.660> and<09:21:42.960> so<09:21:43.140> on<09:21:43.320> with 09:21:44.030 --> 09:21:44.040 align:start position:0% ten the thousands place and so on with 09:21:44.040 --> 09:21:46.130 align:start position:0% ten the thousands place and so on with hexadecimal<09:21:44.880> though 09:21:46.130 --> 09:21:46.140 align:start position:0% hexadecimal though 09:21:46.140 --> 09:21:49.426 align:start position:0% hexadecimal though we're<09:21:46.500> looking<09:21:46.680> at<09:21:46.916> a<09:21:47.096> base<09:21:47.400> 16. 09:21:49.426 --> 09:21:49.436 align:start position:0% we're looking at a base 16. 09:21:49.436 --> 09:21:52.190 align:start position:0% we're looking at a base 16. so<09:21:50.040> every<09:21:50.580> single<09:21:51.000> digit 09:21:52.190 --> 09:21:52.200 align:start position:0% so every single digit 09:21:52.200 --> 09:21:57.050 align:start position:0% so every single digit has<09:21:52.740> a<09:21:53.160> possible<09:21:53.780> 16<09:21:54.780> different<09:21:55.620> options<09:21:56.280> so 09:21:57.050 --> 09:21:57.060 align:start position:0% has a possible 16 different options so 09:21:57.060 --> 09:21:59.450 align:start position:0% has a possible 16 different options so we'd<09:21:57.360> have<09:21:57.596> a<09:21:58.320> ones<09:21:58.620> place<09:21:58.860> which<09:21:59.096> we<09:21:59.340> always 09:21:59.450 --> 09:21:59.460 align:start position:0% we'd have a ones place which we always 09:21:59.460 --> 09:22:03.290 align:start position:0% we'd have a ones place which we always start<09:21:59.700> with<09:21:59.936> a<09:22:00.416> ones<09:22:00.720> place<09:22:00.900> and<09:22:01.500> then<09:22:01.680> a<09:22:02.640> 16s 09:22:03.290 --> 09:22:03.300 align:start position:0% start with a ones place and then a 16s 09:22:03.300 --> 09:22:06.586 align:start position:0% start with a ones place and then a 16s place<09:22:03.660> and<09:22:04.560> then<09:22:04.740> so<09:22:04.980> on<09:22:05.160> and<09:22:05.460> so<09:22:05.700> forth<09:22:06.060> now 09:22:06.586 --> 09:22:06.596 align:start position:0% place and then so on and so forth now 09:22:06.596 --> 09:22:09.530 align:start position:0% place and then so on and so forth now the<09:22:06.780> way<09:22:06.900> we<09:22:07.080> do<09:22:07.256> this<09:22:07.560> is<09:22:08.520> that<09:22:08.820> every<09:22:09.180> digit 09:22:09.530 --> 09:22:09.540 align:start position:0% the way we do this is that every digit 09:22:09.540 --> 09:22:12.170 align:start position:0% the way we do this is that every digit as<09:22:09.720> opposed<09:22:10.020> to<09:22:10.140> decimal<09:22:10.680> where<09:22:11.040> we<09:22:11.280> have<09:22:11.460> zero 09:22:12.170 --> 09:22:12.180 align:start position:0% as opposed to decimal where we have zero 09:22:12.180 --> 09:22:15.470 align:start position:0% as opposed to decimal where we have zero to<09:22:12.300> nine<09:22:12.596> options<09:22:13.200> for<09:22:14.040> every<09:22:14.160> digit<09:22:14.580> and 09:22:15.470 --> 09:22:15.480 align:start position:0% to nine options for every digit and 09:22:15.480 --> 09:22:18.050 align:start position:0% to nine options for every digit and binary<09:22:16.020> where<09:22:16.380> you<09:22:16.620> have<09:22:16.800> either<09:22:17.096> zero<09:22:17.700> or<09:22:17.820> one 09:22:18.050 --> 09:22:18.060 align:start position:0% binary where you have either zero or one 09:22:18.060 --> 09:22:21.406 align:start position:0% binary where you have either zero or one with<09:22:18.960> hexadecimal<09:22:19.800> we<09:22:20.460> can<09:22:20.580> either<09:22:20.700> have<09:22:21.000> zero 09:22:21.406 --> 09:22:21.416 align:start position:0% with hexadecimal we can either have zero 09:22:21.416 --> 09:22:22.370 align:start position:0% with hexadecimal we can either have zero to<09:22:21.540> nine 09:22:22.370 --> 09:22:22.380 align:start position:0% to nine 09:22:22.380 --> 09:22:26.210 align:start position:0% to nine or<09:22:23.160> a<09:22:23.460> through<09:22:23.756> F<09:22:24.000> if<09:22:24.480> we<09:22:24.660> add<09:22:24.780> this<09:22:25.020> up<09:22:25.200> we<09:22:26.096> have 09:22:26.210 --> 09:22:26.220 align:start position:0% or a through F if we add this up we have 09:22:26.220 --> 09:22:28.730 align:start position:0% or a through F if we add this up we have 10<09:22:26.400> options<09:22:26.820> here<09:22:27.180> 0<09:22:27.596> through<09:22:27.900> 9<09:22:28.080> and<09:22:28.380> then<09:22:28.500> a 09:22:28.730 --> 09:22:28.740 align:start position:0% 10 options here 0 through 9 and then a 09:22:28.740 --> 09:22:32.450 align:start position:0% 10 options here 0 through 9 and then a through<09:22:28.980> F<09:22:29.280> we<09:22:29.820> have<09:22:29.936> six<09:22:30.240> so<09:22:31.140> a<09:22:31.800> hexadecimal 09:22:32.450 --> 09:22:32.460 align:start position:0% through F we have six so a hexadecimal 09:22:32.460 --> 09:22:34.370 align:start position:0% through F we have six so a hexadecimal number<09:22:32.580> is<09:22:32.820> going<09:22:32.936> to<09:22:33.060> be<09:22:33.120> a<09:22:33.300> combination<09:22:33.776> of 09:22:34.370 --> 09:22:34.380 align:start position:0% number is going to be a combination of 09:22:34.380 --> 09:22:37.070 align:start position:0% number is going to be a combination of anywhere<09:22:34.680> from<09:22:34.980> 0<09:22:35.276> to<09:22:36.240> f 09:22:37.070 --> 09:22:37.080 align:start position:0% anywhere from 0 to f 09:22:37.080 --> 09:22:41.570 align:start position:0% anywhere from 0 to f uh<09:22:37.740> a<09:22:37.980> would<09:22:38.276> be<09:22:38.460> 10<09:22:38.880> B<09:22:39.416> would<09:22:39.720> be<09:22:39.900> 11<09:22:40.340> C<09:22:41.340> would 09:22:41.570 --> 09:22:41.580 align:start position:0% uh a would be 10 B would be 11 C would 09:22:41.580 --> 09:22:44.570 align:start position:0% uh a would be 10 B would be 11 C would be<09:22:41.756> 12<09:22:42.000> and<09:22:42.360> so<09:22:42.540> on<09:22:42.660> and<09:22:42.900> so<09:22:43.080> forth<09:22:43.380> so<09:22:43.916> when<09:22:44.400> you 09:22:44.570 --> 09:22:44.580 align:start position:0% be 12 and so on and so forth so when you 09:22:44.580 --> 09:22:46.906 align:start position:0% be 12 and so on and so forth so when you see<09:22:44.820> uh<09:22:45.300> this<09:22:45.540> written<09:22:45.776> out<09:22:45.960> that's<09:22:46.500> what<09:22:46.740> that 09:22:46.906 --> 09:22:46.916 align:start position:0% see uh this written out that's what that 09:22:46.916 --> 09:22:50.450 align:start position:0% see uh this written out that's what that means<09:22:47.220> okay<09:22:47.520> now<09:22:48.180> the<09:22:48.596> address<09:22:48.840> is<09:22:49.620> broken<09:22:50.040> up 09:22:50.450 --> 09:22:50.460 align:start position:0% means okay now the address is broken up 09:22:50.460 --> 09:22:54.050 align:start position:0% means okay now the address is broken up into<09:22:51.360> eight<09:22:51.900> groups<09:22:52.380> of<09:22:52.860> four<09:22:53.096> hexadecimal 09:22:54.050 --> 09:22:54.060 align:start position:0% into eight groups of four hexadecimal 09:22:54.060 --> 09:22:55.190 align:start position:0% into eight groups of four hexadecimal digits 09:22:55.190 --> 09:22:55.200 align:start position:0% digits 09:22:55.200 --> 09:22:58.070 align:start position:0% digits and<09:22:55.800> these<09:22:56.040> are<09:22:56.160> separated<09:22:56.580> by<09:22:56.936> colons 09:22:58.070 --> 09:22:58.080 align:start position:0% and these are separated by colons 09:22:58.080 --> 09:23:00.290 align:start position:0% and these are separated by colons now<09:22:58.800> uh<09:22:59.276> I'm<09:22:59.520> going<09:22:59.640> to<09:22:59.700> show<09:22:59.820> you<09:22:59.936> this<09:23:00.060> in 09:23:00.290 --> 09:23:00.300 align:start position:0% now uh I'm going to show you this in 09:23:00.300 --> 09:23:01.850 align:start position:0% now uh I'm going to show you this in just<09:23:00.416> a<09:23:00.540> second<09:23:00.720> but<09:23:01.140> there<09:23:01.320> are<09:23:01.436> also<09:23:01.680> a 09:23:01.850 --> 09:23:01.860 align:start position:0% just a second but there are also a 09:23:01.860 --> 09:23:03.766 align:start position:0% just a second but there are also a couple<09:23:01.980> of<09:23:02.160> rules<09:23:02.460> when<09:23:02.640> it<09:23:02.756> applies<09:23:03.060> to<09:23:03.300> when 09:23:03.766 --> 09:23:03.776 align:start position:0% couple of rules when it applies to when 09:23:03.776 --> 09:23:05.746 align:start position:0% couple of rules when it applies to when we<09:23:03.900> come<09:23:04.080> to<09:23:04.200> readability 09:23:05.746 --> 09:23:05.756 align:start position:0% we come to readability 09:23:05.756 --> 09:23:07.906 align:start position:0% we come to readability so<09:23:06.300> the<09:23:06.720> first<09:23:06.900> rule 09:23:07.906 --> 09:23:07.916 align:start position:0% so the first rule 09:23:07.916 --> 09:23:10.130 align:start position:0% so the first rule is<09:23:08.460> that<09:23:08.640> let's<09:23:09.000> say<09:23:09.180> this<09:23:09.596> is<09:23:09.900> our 09:23:10.130 --> 09:23:10.140 align:start position:0% is that let's say this is our 09:23:10.140 --> 09:23:12.850 align:start position:0% is that let's say this is our hexadecimal 09:23:12.850 --> 09:23:12.860 align:start position:0% hexadecimal 09:23:12.860 --> 09:23:18.290 align:start position:0% hexadecimal IPv6<09:23:13.860> address<09:23:14.340> you<09:23:15.180> notice<09:23:15.480> first<09:23:15.776> of<09:23:15.960> all<09:23:16.080> one 09:23:18.290 --> 09:23:18.300 align:start position:0% IPv6 address you notice first of all one 09:23:18.300 --> 09:23:19.730 align:start position:0% IPv6 address you notice first of all one two 09:23:19.730 --> 09:23:19.740 align:start position:0% two 09:23:19.740 --> 09:23:21.170 align:start position:0% two three 09:23:21.170 --> 09:23:21.180 align:start position:0% three 09:23:21.180 --> 09:23:22.906 align:start position:0% three four 09:23:22.906 --> 09:23:22.916 align:start position:0% four 09:23:22.916 --> 09:23:24.530 align:start position:0% four five 09:23:24.530 --> 09:23:24.540 align:start position:0% five 09:23:24.540 --> 09:23:26.030 align:start position:0% five six 09:23:26.030 --> 09:23:26.040 align:start position:0% six 09:23:26.040 --> 09:23:27.350 align:start position:0% six seven 09:23:27.350 --> 09:23:27.360 align:start position:0% seven 09:23:27.360 --> 09:23:31.190 align:start position:0% seven eight<09:23:27.960> right<09:23:28.560> there<09:23:29.096> are<09:23:29.400> eight<09:23:29.936> groups 09:23:31.190 --> 09:23:31.200 align:start position:0% eight right there are eight groups 09:23:31.200 --> 09:23:34.850 align:start position:0% eight right there are eight groups of<09:23:31.800> four<09:23:32.180> hexadecimal<09:23:33.180> digits<09:23:33.596> each 09:23:34.850 --> 09:23:34.860 align:start position:0% of four hexadecimal digits each 09:23:34.860 --> 09:23:37.190 align:start position:0% of four hexadecimal digits each and<09:23:35.460> of<09:23:35.640> course<09:23:35.756> each<09:23:36.240> one<09:23:36.416> of<09:23:36.540> these<09:23:36.720> digits 09:23:37.190 --> 09:23:37.200 align:start position:0% and of course each one of these digits 09:23:37.200 --> 09:23:40.370 align:start position:0% and of course each one of these digits has<09:23:37.740> 16<09:23:38.040> possible<09:23:38.640> values<09:23:39.120> okay<09:23:39.596> so<09:23:40.256> let's 09:23:40.370 --> 09:23:40.380 align:start position:0% has 16 possible values okay so let's 09:23:40.380 --> 09:23:42.766 align:start position:0% has 16 possible values okay so let's look<09:23:40.560> at<09:23:40.740> two<09:23:41.040> rules<09:23:41.460> and<09:23:41.936> these<09:23:42.180> are<09:23:42.300> also<09:23:42.540> not 09:23:42.766 --> 09:23:42.776 align:start position:0% look at two rules and these are also not 09:23:42.776 --> 09:23:44.926 align:start position:0% look at two rules and these are also not only<09:23:42.980> readability<09:23:43.980> rules<09:23:44.400> but<09:23:44.520> what<09:23:44.640> we<09:23:44.756> call 09:23:44.926 --> 09:23:44.936 align:start position:0% only readability rules but what we call 09:23:44.936 --> 09:23:46.906 align:start position:0% only readability rules but what we call truncation<09:23:45.540> rules<09:23:46.020> meaning<09:23:46.200> this<09:23:46.436> is<09:23:46.560> how<09:23:46.740> we 09:23:46.906 --> 09:23:46.916 align:start position:0% truncation rules meaning this is how we 09:23:46.916 --> 09:23:48.350 align:start position:0% truncation rules meaning this is how we can<09:23:47.096> shorten 09:23:48.350 --> 09:23:48.360 align:start position:0% can shorten 09:23:48.360 --> 09:23:51.350 align:start position:0% can shorten an<09:23:48.840> IPv6<09:23:49.680> address<09:23:50.096> since<09:23:50.520> they<09:23:50.756> can<09:23:50.880> get<09:23:51.060> quite 09:23:51.350 --> 09:23:51.360 align:start position:0% an IPv6 address since they can get quite 09:23:51.360 --> 09:23:52.246 align:start position:0% an IPv6 address since they can get quite long 09:23:52.246 --> 09:23:52.256 align:start position:0% long 09:23:52.256 --> 09:23:55.130 align:start position:0% long the<09:23:52.860> first<09:23:53.040> rule<09:23:53.400> is<09:23:53.580> that<09:23:53.820> any<09:23:54.120> leading<09:23:54.720> zeros 09:23:55.130 --> 09:23:55.140 align:start position:0% the first rule is that any leading zeros 09:23:55.140 --> 09:23:57.830 align:start position:0% the first rule is that any leading zeros can<09:23:55.500> be<09:23:55.680> removed<09:23:56.160> so<09:23:57.000> if<09:23:57.240> we<09:23:57.360> imagine<09:23:57.540> any 09:23:57.830 --> 09:23:57.840 align:start position:0% can be removed so if we imagine any 09:23:57.840 --> 09:23:59.926 align:start position:0% can be removed so if we imagine any leading<09:23:58.256> zeros<09:23:58.620> I'm<09:23:59.276> going<09:23:59.400> to<09:23:59.460> circle<09:23:59.640> them 09:23:59.926 --> 09:23:59.936 align:start position:0% leading zeros I'm going to circle them 09:23:59.936 --> 09:24:02.030 align:start position:0% leading zeros I'm going to circle them right<09:24:00.776> there 09:24:02.030 --> 09:24:02.040 align:start position:0% right there 09:24:02.040 --> 09:24:05.690 align:start position:0% right there right<09:24:02.700> here 09:24:05.690 --> 09:24:05.700 align:start position:0% 09:24:05.700 --> 09:24:08.150 align:start position:0% right<09:24:06.360> here<09:24:06.596> and<09:24:07.256> if<09:24:07.500> we<09:24:07.620> wanted<09:24:07.740> we<09:24:08.096> could 09:24:08.150 --> 09:24:08.160 align:start position:0% right here and if we wanted we could 09:24:08.160 --> 09:24:11.510 align:start position:0% right here and if we wanted we could even<09:24:08.340> consider<09:24:08.880> these<09:24:09.596> leading<09:24:09.960> zeros 09:24:11.510 --> 09:24:11.520 align:start position:0% even consider these leading zeros 09:24:11.520 --> 09:24:13.670 align:start position:0% even consider these leading zeros and<09:24:12.120> therefore<09:24:12.480> if<09:24:12.660> we<09:24:12.840> rewrite<09:24:13.256> this<09:24:13.500> out 09:24:13.670 --> 09:24:13.680 align:start position:0% and therefore if we rewrite this out 09:24:13.680 --> 09:24:17.810 align:start position:0% and therefore if we rewrite this out below<09:24:13.980> you'll<09:24:14.340> see<09:24:14.580> we're<09:24:15.300> going<09:24:15.596> to<09:24:15.900> remove 09:24:17.810 --> 09:24:17.820 align:start position:0% below you'll see we're going to remove 09:24:17.820 --> 09:24:20.266 align:start position:0% below you'll see we're going to remove all<09:24:18.240> the<09:24:18.360> leading<09:24:18.660> zeros 09:24:20.266 --> 09:24:20.276 align:start position:0% all the leading zeros 09:24:20.276 --> 09:24:23.450 align:start position:0% all the leading zeros and<09:24:20.700> that<09:24:20.756> allows<09:24:21.120> us<09:24:21.240> to<09:24:21.480> shorten 09:24:23.450 --> 09:24:23.460 align:start position:0% and that allows us to shorten 09:24:23.460 --> 09:24:26.810 align:start position:0% and that allows us to shorten our<09:24:24.300> address 09:24:26.810 --> 09:24:26.820 align:start position:0% our address 09:24:26.820 --> 09:24:29.210 align:start position:0% our address now<09:24:27.300> we<09:24:27.596> could<09:24:27.776> also 09:24:29.210 --> 09:24:29.220 align:start position:0% now we could also 09:24:29.220 --> 09:24:30.890 align:start position:0% now we could also if I<09:24:29.640> was<09:24:29.820> just<09:24:29.936> going<09:24:30.120> to<09:24:30.180> take<09:24:30.480> this<09:24:30.720> one 09:24:30.890 --> 09:24:30.900 align:start position:0% if I was just going to take this one 09:24:30.900 --> 09:24:34.906 align:start position:0% if I was just going to take this one step<09:24:31.140> further 09:24:34.906 --> 09:24:34.916 align:start position:0% 09:24:34.916 --> 09:24:38.690 align:start position:0% I<09:24:35.520> could<09:24:35.700> also<09:24:36.180> shorten 09:24:38.690 --> 09:24:38.700 align:start position:0% I could also shorten 09:24:38.700 --> 09:24:42.586 align:start position:0% I could also shorten these<09:24:39.540> zeros<09:24:40.020> if<09:24:40.436> I<09:24:40.560> so<09:24:40.740> wished 09:24:42.586 --> 09:24:42.596 align:start position:0% these zeros if I so wished 09:24:42.596 --> 09:24:46.970 align:start position:0% these zeros if I so wished and<09:24:43.020> just<09:24:43.200> leave<09:24:43.436> one<09:24:43.916> zero<09:24:44.340> there 09:24:46.970 --> 09:24:46.980 align:start position:0% 09:24:46.980 --> 09:24:50.030 align:start position:0% now<09:24:47.520> no<09:24:47.880> matter<09:24:48.000> how<09:24:48.480> you<09:24:48.720> write<09:24:48.960> out 09:24:50.030 --> 09:24:50.040 align:start position:0% now no matter how you write out 09:24:50.040 --> 09:24:52.550 align:start position:0% now no matter how you write out the<09:24:50.580> address<09:24:50.756> the<09:24:51.660> rules<09:24:51.900> are<09:24:52.080> put<09:24:52.256> in<09:24:52.380> place 09:24:52.550 --> 09:24:52.560 align:start position:0% the address the rules are put in place 09:24:52.560 --> 09:24:55.310 align:start position:0% the address the rules are put in place in<09:24:52.740> a<09:24:52.860> way<09:24:52.980> that<09:24:53.096> you<09:24:53.340> can<09:24:53.460> always<09:24:53.700> go<09:24:54.180> back<09:24:54.480> to 09:24:55.310 --> 09:24:55.320 align:start position:0% in a way that you can always go back to 09:24:55.320 --> 09:24:56.810 align:start position:0% in a way that you can always go back to the 09:24:56.810 --> 09:24:56.820 align:start position:0% the 09:24:56.820 --> 09:24:59.746 align:start position:0% the main<09:24:57.480> address<09:24:57.776> and<09:24:58.200> so<09:24:58.500> you<09:24:59.340> don't<09:24:59.460> have<09:24:59.580> to 09:24:59.746 --> 09:24:59.756 align:start position:0% main address and so you don't have to 09:24:59.756 --> 09:25:01.490 align:start position:0% main address and so you don't have to worry<09:24:59.936> about<09:25:00.180> you<09:25:00.540> know<09:25:00.596> you<09:25:00.840> can<09:25:00.960> sort<09:25:01.380> of 09:25:01.490 --> 09:25:01.500 align:start position:0% worry about you know you can sort of 09:25:01.500 --> 09:25:03.230 align:start position:0% worry about you know you can sort of pick<09:25:01.680> and<09:25:01.916> choose<09:25:02.220> there<09:25:02.520> are<09:25:02.640> best<09:25:02.820> practices 09:25:03.230 --> 09:25:03.240 align:start position:0% pick and choose there are best practices 09:25:03.240 --> 09:25:04.550 align:start position:0% pick and choose there are best practices but<09:25:03.596> the<09:25:03.720> computer<09:25:03.840> is<09:25:04.080> always<09:25:04.200> going<09:25:04.380> to<09:25:04.436> be 09:25:04.550 --> 09:25:04.560 align:start position:0% but the computer is always going to be 09:25:04.560 --> 09:25:06.350 align:start position:0% but the computer is always going to be able<09:25:04.620> to<09:25:04.740> figure<09:25:04.916> it<09:25:05.160> out<09:25:05.276> okay 09:25:06.350 --> 09:25:06.360 align:start position:0% able to figure it out okay 09:25:06.360 --> 09:25:10.210 align:start position:0% able to figure it out okay now<09:25:07.140> the<09:25:07.620> second<09:25:07.800> rule<09:25:08.220> is<09:25:08.880> that<09:25:09.240> successive 09:25:10.210 --> 09:25:10.220 align:start position:0% now the second rule is that successive 09:25:10.220 --> 09:25:13.610 align:start position:0% now the second rule is that successive zeros<09:25:11.220> or<09:25:11.820> successive<09:25:12.416> sets<09:25:12.720> of<09:25:12.776> zeros<09:25:13.140> can<09:25:13.436> be 09:25:13.610 --> 09:25:13.620 align:start position:0% zeros or successive sets of zeros can be 09:25:13.620 --> 09:25:15.470 align:start position:0% zeros or successive sets of zeros can be removed<09:25:14.040> but<09:25:14.400> they<09:25:14.520> can<09:25:14.640> only<09:25:14.756> be<09:25:15.000> removed 09:25:15.470 --> 09:25:15.480 align:start position:0% removed but they can only be removed 09:25:15.480 --> 09:25:18.710 align:start position:0% removed but they can only be removed once<09:25:15.840> so<09:25:16.680> any<09:25:17.096> sets<09:25:17.520> of<09:25:17.580> successive<09:25:18.120> zeros<09:25:18.480> and 09:25:18.710 --> 09:25:18.720 align:start position:0% once so any sets of successive zeros and 09:25:18.720 --> 09:25:19.906 align:start position:0% once so any sets of successive zeros and here<09:25:18.900> we<09:25:19.140> see 09:25:19.906 --> 09:25:19.916 align:start position:0% here we see 09:25:19.916 --> 09:25:22.310 align:start position:0% here we see one<09:25:20.580> set<09:25:20.756> or<09:25:21.000> two<09:25:21.120> sets<09:25:21.480> rather<09:25:21.720> successive 09:25:22.310 --> 09:25:22.320 align:start position:0% one set or two sets rather successive 09:25:22.320 --> 09:25:25.310 align:start position:0% one set or two sets rather successive zeros<09:25:22.680> can<09:25:23.160> be<09:25:23.400> removed<09:25:23.820> and<09:25:24.180> replaced 09:25:25.310 --> 09:25:25.320 align:start position:0% zeros can be removed and replaced 09:25:25.320 --> 09:25:27.350 align:start position:0% zeros can be removed and replaced with<09:25:25.680> a<09:25:25.800> double<09:25:25.916> colon 09:25:27.350 --> 09:25:27.360 align:start position:0% with a double colon 09:25:27.360 --> 09:25:30.050 align:start position:0% with a double colon now<09:25:27.900> the<09:25:28.560> reason<09:25:28.680> we<09:25:28.980> can<09:25:29.160> only<09:25:29.276> apply<09:25:29.756> that 09:25:30.050 --> 09:25:30.060 align:start position:0% now the reason we can only apply that 09:25:30.060 --> 09:25:34.030 align:start position:0% now the reason we can only apply that once<09:25:30.680> is<09:25:31.680> let's<09:25:32.160> say<09:25:32.400> these<09:25:32.756> zeros 09:25:34.030 --> 09:25:34.040 align:start position:0% once is let's say these zeros 09:25:34.040 --> 09:25:37.190 align:start position:0% once is let's say these zeros were<09:25:35.040> we<09:25:35.400> had<09:25:35.520> another<09:25:35.700> set<09:25:36.000> of<09:25:36.180> zeros<09:25:36.540> over 09:25:37.190 --> 09:25:37.200 align:start position:0% were we had another set of zeros over 09:25:37.200 --> 09:25:39.350 align:start position:0% were we had another set of zeros over here<09:25:37.500> and<09:25:38.400> we 09:25:39.350 --> 09:25:39.360 align:start position:0% here and we 09:25:39.360 --> 09:25:40.010 align:start position:0% here and we um 09:25:40.010 --> 09:25:40.020 align:start position:0% um 09:25:40.020 --> 09:25:42.110 align:start position:0% um truncated<09:25:40.800> those 09:25:42.110 --> 09:25:42.120 align:start position:0% truncated those 09:25:42.120 --> 09:25:44.510 align:start position:0% truncated those we<09:25:42.720> can<09:25:42.840> add<09:25:43.020> up<09:25:43.200> right<09:25:43.436> we<09:25:43.620> know<09:25:43.740> there's<09:25:43.980> one 09:25:44.510 --> 09:25:44.520 align:start position:0% we can add up right we know there's one 09:25:44.520 --> 09:25:49.426 align:start position:0% we can add up right we know there's one two<09:25:45.180> three<09:25:45.776> four<09:25:46.560> five<09:25:47.160> six<09:25:47.640> sets<09:25:48.180> here<09:25:48.776> so<09:25:49.256> we 09:25:49.426 --> 09:25:49.436 align:start position:0% two three four five six sets here so we 09:25:49.436 --> 09:25:52.790 align:start position:0% two three four five six sets here so we know<09:25:49.620> that<09:25:49.860> this<09:25:50.096> represents<09:25:50.820> two<09:25:51.540> sets 09:25:52.790 --> 09:25:52.800 align:start position:0% know that this represents two sets 09:25:52.800 --> 09:25:56.330 align:start position:0% know that this represents two sets of<09:25:53.460> missing<09:25:53.936> zeros<09:25:54.416> but<09:25:55.320> for<09:25:55.620> instance<09:25:55.860> if<09:25:56.160> we 09:25:56.330 --> 09:25:56.340 align:start position:0% of missing zeros but for instance if we 09:25:56.340 --> 09:25:58.490 align:start position:0% of missing zeros but for instance if we had<09:25:56.580> you<09:25:56.880> know<09:25:57.000> two<09:25:57.180> other<09:25:57.416> sets 09:25:58.490 --> 09:25:58.500 align:start position:0% had you know two other sets 09:25:58.500 --> 09:26:01.426 align:start position:0% had you know two other sets here<09:25:58.980> and<09:25:59.700> we<09:25:59.820> remove<09:26:00.000> those<09:26:00.480> we<09:26:01.020> might<09:26:01.200> not 09:26:01.426 --> 09:26:01.436 align:start position:0% here and we remove those we might not 09:26:01.436 --> 09:26:02.450 align:start position:0% here and we remove those we might not know 09:26:02.450 --> 09:26:02.460 align:start position:0% know 09:26:02.460 --> 09:26:04.906 align:start position:0% know whether<09:26:02.936> it's<09:26:03.180> supposed<09:26:03.300> to<09:26:03.480> be<09:26:03.660> one<09:26:04.020> set<09:26:04.320> and 09:26:04.906 --> 09:26:04.916 align:start position:0% whether it's supposed to be one set and 09:26:04.916 --> 09:26:07.010 align:start position:0% whether it's supposed to be one set and three<09:26:05.096> sets<09:26:05.580> or<09:26:05.820> two<09:26:06.000> sets<09:26:06.360> and<09:26:06.480> two<09:26:06.596> sets<09:26:06.960> and 09:26:07.010 --> 09:26:07.020 align:start position:0% three sets or two sets and two sets and 09:26:07.020 --> 09:26:09.050 align:start position:0% three sets or two sets and two sets and so<09:26:07.200> on<09:26:07.320> and<09:26:07.436> so<09:26:07.560> forth<09:26:07.860> so<09:26:08.340> we<09:26:08.580> can<09:26:08.700> only<09:26:08.820> do 09:26:09.050 --> 09:26:09.060 align:start position:0% so on and so forth so we can only do 09:26:09.060 --> 09:26:11.266 align:start position:0% so on and so forth so we can only do this<09:26:09.240> once<09:26:09.540> because<09:26:09.776> when<09:26:10.140> we<09:26:10.320> add<09:26:10.860> them<09:26:11.040> back 09:26:11.266 --> 09:26:11.276 align:start position:0% this once because when we add them back 09:26:11.276 --> 09:26:13.610 align:start position:0% this once because when we add them back there's<09:26:11.700> no<09:26:12.000> way<09:26:12.240> to<09:26:12.480> know 09:26:13.610 --> 09:26:13.620 align:start position:0% there's no way to know 09:26:13.620 --> 09:26:14.450 align:start position:0% there's no way to know um 09:26:14.450 --> 09:26:14.460 align:start position:0% um 09:26:14.460 --> 09:26:19.246 align:start position:0% um uh<09:26:15.180> you<09:26:15.480> know<09:26:15.540> where<09:26:16.020> that<09:26:16.380> would<09:26:16.740> sort<09:26:17.460> of<09:26:17.520> lie 09:26:19.246 --> 09:26:19.256 align:start position:0% uh you know where that would sort of lie 09:26:19.256 --> 09:26:21.890 align:start position:0% uh you know where that would sort of lie now<09:26:19.916> uh<09:26:20.460> I'm<09:26:20.936> just<09:26:21.060> gonna<09:26:21.180> erase<09:26:21.480> this<09:26:21.660> for<09:26:21.840> a 09:26:21.890 --> 09:26:21.900 align:start position:0% now uh I'm just gonna erase this for a 09:26:21.900 --> 09:26:24.350 align:start position:0% now uh I'm just gonna erase this for a second<09:26:22.020> because<09:26:22.500> we<09:26:23.220> can<09:26:23.340> even<09:26:23.520> truncate<09:26:24.060> this 09:26:24.350 --> 09:26:24.360 align:start position:0% second because we can even truncate this 09:26:24.360 --> 09:26:27.110 align:start position:0% second because we can even truncate this more<09:26:24.720> we've<09:26:25.140> applied<09:26:25.500> this<09:26:25.860> rule 09:26:27.110 --> 09:26:27.120 align:start position:0% more we've applied this rule 09:26:27.120 --> 09:26:29.630 align:start position:0% more we've applied this rule so<09:26:27.660> this<09:26:28.020> applies<09:26:28.380> this<09:26:28.620> rule<09:26:28.980> this<09:26:29.400> one<09:26:29.520> is 09:26:29.630 --> 09:26:29.640 align:start position:0% so this applies this rule this one is 09:26:29.640 --> 09:26:31.246 align:start position:0% so this applies this rule this one is applied<09:26:29.936> this<09:26:30.120> rule<09:26:30.416> but<09:26:30.596> we<09:26:30.660> can<09:26:30.776> apply<09:26:31.020> both 09:26:31.246 --> 09:26:31.256 align:start position:0% applied this rule but we can apply both 09:26:31.256 --> 09:26:33.890 align:start position:0% applied this rule but we can apply both rules<09:26:31.680> right<09:26:32.520> so<09:26:32.820> we<09:26:33.000> can<09:26:33.120> remove<09:26:33.360> these 09:26:33.890 --> 09:26:33.900 align:start position:0% rules right so we can remove these 09:26:33.900 --> 09:26:35.990 align:start position:0% rules right so we can remove these leading<09:26:34.200> zeros<09:26:34.620> here<09:26:34.860> and<09:26:35.520> actually<09:26:35.700> write 09:26:35.990 --> 09:26:36.000 align:start position:0% leading zeros here and actually write 09:26:36.000 --> 09:26:37.190 align:start position:0% leading zeros here and actually write this<09:26:36.240> out 09:26:37.190 --> 09:26:37.200 align:start position:0% this out 09:26:37.200 --> 09:26:40.670 align:start position:0% this out as<09:26:37.620> 2001 09:26:40.670 --> 09:26:40.680 align:start position:0% 09:26:40.680 --> 09:26:42.470 align:start position:0% d8 09:26:42.470 --> 09:26:42.480 align:start position:0% d8 09:26:42.480 --> 09:26:46.370 align:start position:0% d8 eight<09:26:43.380> eight<09:26:43.436> a<09:26:44.160> three<09:26:44.540> double<09:26:45.540> colon<09:26:46.080> which 09:26:46.370 --> 09:26:46.380 align:start position:0% eight eight a three double colon which 09:26:46.380 --> 09:26:49.246 align:start position:0% eight eight a three double colon which means<09:26:46.620> that<09:26:46.740> those<09:26:46.916> are<09:26:47.096> successive<09:26:47.580> zeros 09:26:49.246 --> 09:26:49.256 align:start position:0% means that those are successive zeros 09:26:49.256 --> 09:26:53.690 align:start position:0% means that those are successive zeros three<09:26:50.040> e<09:26:50.520> seven<09:26:51.416> zero<09:26:52.040> seven<09:26:53.040> three<09:26:53.400> three 09:26:53.690 --> 09:26:53.700 align:start position:0% three e seven zero seven three three 09:26:53.700 --> 09:26:54.586 align:start position:0% three e seven zero seven three three four 09:26:54.586 --> 09:26:54.596 align:start position:0% four 09:26:54.596 --> 09:26:57.530 align:start position:0% four now<09:26:55.200> let's<09:26:55.560> just<09:26:55.800> I<09:26:56.096> just<09:26:56.220> want<09:26:56.400> to<09:26:56.640> uh<09:26:57.000> sort<09:26:57.416> of 09:26:57.530 --> 09:26:57.540 align:start position:0% now let's just I just want to uh sort of 09:26:57.540 --> 09:27:00.050 align:start position:0% now let's just I just want to uh sort of follow<09:26:57.720> up<09:26:58.020> and<09:26:58.320> explain<09:26:58.740> write<09:26:59.460> out<09:26:59.640> what<09:26:59.880> I 09:27:00.050 --> 09:27:00.060 align:start position:0% follow up and explain write out what I 09:27:00.060 --> 09:27:01.906 align:start position:0% follow up and explain write out what I was<09:27:00.180> just<09:27:00.360> talking<09:27:00.540> about<09:27:00.720> with<09:27:01.140> why<09:27:01.436> we<09:27:01.740> can't 09:27:01.906 --> 09:27:01.916 align:start position:0% was just talking about with why we can't 09:27:01.916 --> 09:27:03.950 align:start position:0% was just talking about with why we can't have<09:27:02.460> more<09:27:02.700> than<09:27:02.820> two<09:27:03.060> sets<09:27:03.416> of<09:27:03.416> successive 09:27:03.950 --> 09:27:03.960 align:start position:0% have more than two sets of successive 09:27:03.960 --> 09:27:08.746 align:start position:0% have more than two sets of successive zeros<09:27:04.320> okay<09:27:04.620> let's<09:27:05.580> say<09:27:05.936> that<09:27:06.900> we<09:27:07.140> have<09:27:07.256> zeros 09:27:08.746 --> 09:27:08.756 align:start position:0% zeros okay let's say that we have zeros 09:27:08.756 --> 09:27:10.490 align:start position:0% zeros okay let's say that we have zeros here<09:27:09.360> as<09:27:09.540> well 09:27:10.490 --> 09:27:10.500 align:start position:0% here as well 09:27:10.500 --> 09:27:12.950 align:start position:0% here as well okay<09:27:10.680> so<09:27:11.040> I'm<09:27:11.160> gonna<09:27:11.340> rewrite<09:27:11.820> this<09:27:12.120> out<09:27:12.300> we 09:27:12.950 --> 09:27:12.960 align:start position:0% okay so I'm gonna rewrite this out we 09:27:12.960 --> 09:27:16.790 align:start position:0% okay so I'm gonna rewrite this out we have<09:27:13.080> zero<09:27:13.680> zero<09:27:14.040> zero<09:27:14.460> zero<09:27:14.820> colon<09:27:15.596> zero<09:27:16.380> zero 09:27:16.790 --> 09:27:16.800 align:start position:0% have zero zero zero zero colon zero zero 09:27:16.800 --> 09:27:21.010 align:start position:0% have zero zero zero zero colon zero zero zero<09:27:17.220> zero<09:27:17.596> colon<09:27:18.680> zero<09:27:19.680> eight 09:27:21.010 --> 09:27:21.020 align:start position:0% zero zero colon zero eight 09:27:21.020 --> 09:27:26.630 align:start position:0% zero zero colon zero eight A3<09:27:22.220> colon<09:27:23.220> zero<09:27:24.180> zero<09:27:24.480> zero<09:27:24.776> zero<09:27:25.620> zero<09:27:26.340> zero 09:27:26.630 --> 09:27:26.640 align:start position:0% A3 colon zero zero zero zero zero zero 09:27:26.640 --> 09:27:28.790 align:start position:0% A3 colon zero zero zero zero zero zero zero<09:27:26.936> zero 09:27:28.790 --> 09:27:28.800 align:start position:0% zero zero 09:27:28.800 --> 09:27:34.490 align:start position:0% zero zero eight<09:27:29.400> c<09:27:29.820> three<09:27:30.776> e<09:27:31.400> zero<09:27:32.400> zero<09:27:32.756> seven<09:27:32.936> zero 09:27:34.490 --> 09:27:34.500 align:start position:0% eight c three e zero zero seven zero 09:27:34.500 --> 09:27:37.246 align:start position:0% eight c three e zero zero seven zero seven<09:27:35.220> three<09:27:35.520> three<09:27:35.880> four<09:27:36.180> okay 09:27:37.246 --> 09:27:37.256 align:start position:0% seven three three four okay 09:27:37.256 --> 09:27:39.170 align:start position:0% seven three three four okay let's<09:27:37.740> first<09:27:37.980> apply<09:27:38.460> our<09:27:38.580> first<09:27:38.756> rule<09:27:39.060> which 09:27:39.170 --> 09:27:39.180 align:start position:0% let's first apply our first rule which 09:27:39.180 --> 09:27:41.630 align:start position:0% let's first apply our first rule which is<09:27:39.300> that<09:27:39.480> leading<09:27:39.900> zeros<09:27:40.200> can<09:27:40.436> be<09:27:40.560> removed<09:27:40.980> so 09:27:41.630 --> 09:27:41.640 align:start position:0% is that leading zeros can be removed so 09:27:41.640 --> 09:27:42.950 align:start position:0% is that leading zeros can be removed so we<09:27:41.756> rewrite<09:27:42.180> this<09:27:42.360> and<09:27:42.540> we're<09:27:42.660> going<09:27:42.776> to<09:27:42.840> get 09:27:42.950 --> 09:27:42.960 align:start position:0% we rewrite this and we're going to get 09:27:42.960 --> 09:27:58.130 align:start position:0% we rewrite this and we're going to get this 09:27:58.130 --> 09:27:58.140 align:start position:0% 09:27:58.140 --> 09:28:02.086 align:start position:0% okay<09:27:58.620> now<09:27:59.276> we're<09:27:59.936> allowed<09:28:00.240> to<09:28:00.480> remove<09:28:00.860> one<09:28:01.860> set 09:28:02.086 --> 09:28:02.096 align:start position:0% okay now we're allowed to remove one set 09:28:02.096 --> 09:28:04.010 align:start position:0% okay now we're allowed to remove one set of<09:28:02.340> leading<09:28:02.640> of<09:28:02.880> successive<09:28:03.416> zeros<09:28:03.776> only 09:28:04.010 --> 09:28:04.020 align:start position:0% of leading of successive zeros only 09:28:04.020 --> 09:28:06.530 align:start position:0% of leading of successive zeros only which<09:28:04.620> is<09:28:04.740> the<09:28:04.916> second<09:28:05.096> rule<09:28:05.520> okay<09:28:05.880> but<09:28:06.360> let's 09:28:06.530 --> 09:28:06.540 align:start position:0% which is the second rule okay but let's 09:28:06.540 --> 09:28:09.290 align:start position:0% which is the second rule okay but let's do<09:28:06.776> it<09:28:06.900> twice<09:28:07.380> and<09:28:07.680> just<09:28:07.800> see<09:28:07.916> what<09:28:08.096> happens<09:28:08.340> so 09:28:09.290 --> 09:28:09.300 align:start position:0% do it twice and just see what happens so 09:28:09.300 --> 09:28:12.670 align:start position:0% do it twice and just see what happens so let's<09:28:09.480> say<09:28:09.660> we<09:28:09.840> have<09:28:10.200> a<09:28:10.320> double<09:28:10.436> colon<09:28:10.860> here 09:28:12.670 --> 09:28:12.680 align:start position:0% let's say we have a double colon here 09:28:12.680 --> 09:28:15.470 align:start position:0% let's say we have a double colon here 8a3<09:28:14.160> and<09:28:14.580> then<09:28:14.700> we<09:28:14.820> have<09:28:14.936> another<09:28:15.180> double 09:28:15.470 --> 09:28:15.480 align:start position:0% 8a3 and then we have another double 09:28:15.480 --> 09:28:17.030 align:start position:0% 8a3 and then we have another double colon 09:28:17.030 --> 09:28:17.040 align:start position:0% colon 09:28:17.040 --> 09:28:20.030 align:start position:0% colon 8c3e 09:28:20.030 --> 09:28:20.040 align:start position:0% 8c3e 09:28:20.040 --> 09:28:21.950 align:start position:0% 8c3e seven<09:28:20.520> zero 09:28:21.950 --> 09:28:21.960 align:start position:0% seven zero 09:28:21.960 --> 09:28:24.950 align:start position:0% seven zero seven<09:28:22.500> three<09:28:22.860> three<09:28:23.160> four<09:28:23.400> now 09:28:24.950 --> 09:28:24.960 align:start position:0% seven three three four now 09:28:24.960 --> 09:28:26.990 align:start position:0% seven three three four now let's<09:28:25.320> say<09:28:25.436> we<09:28:25.560> want<09:28:25.740> to<09:28:25.860> expand<09:28:26.400> this<09:28:26.820> back 09:28:26.990 --> 09:28:27.000 align:start position:0% let's say we want to expand this back 09:28:27.000 --> 09:28:29.150 align:start position:0% let's say we want to expand this back out<09:28:27.240> to<09:28:27.596> its<09:28:27.900> full<09:28:28.020> version 09:28:29.150 --> 09:28:29.160 align:start position:0% out to its full version 09:28:29.160 --> 09:28:31.970 align:start position:0% out to its full version well<09:28:29.700> if<09:28:30.540> we<09:28:30.660> have<09:28:30.776> the<09:28:31.020> successive<09:28:31.560> zeros 09:28:31.970 --> 09:28:31.980 align:start position:0% well if we have the successive zeros 09:28:31.980 --> 09:28:33.470 align:start position:0% well if we have the successive zeros here 09:28:33.470 --> 09:28:33.480 align:start position:0% here 09:28:33.480 --> 09:28:35.746 align:start position:0% here we<09:28:33.540> don't<09:28:34.020> know<09:28:34.320> if<09:28:34.980> this<09:28:35.160> would<09:28:35.340> be<09:28:35.460> written 09:28:35.746 --> 09:28:35.756 align:start position:0% we don't know if this would be written 09:28:35.756 --> 09:28:40.010 align:start position:0% we don't know if this would be written out<09:28:35.936> zero<09:28:36.720> zero<09:28:37.200> zero<09:28:37.740> zero 09:28:40.010 --> 09:28:40.020 align:start position:0% out zero zero zero zero 09:28:40.020 --> 09:28:46.790 align:start position:0% out zero zero zero zero dot<09:28:40.740> 883 09:28:46.790 --> 09:28:46.800 align:start position:0% 09:28:46.800 --> 09:28:51.110 align:start position:0% because<09:28:47.540> from<09:28:48.540> what<09:28:48.720> we're<09:28:48.840> seeing<09:28:49.140> here 09:28:51.110 --> 09:28:51.120 align:start position:0% because from what we're seeing here 09:28:51.120 --> 09:28:54.110 align:start position:0% because from what we're seeing here theoretically<09:28:52.080> we<09:28:52.980> could<09:28:53.096> put<09:28:53.400> three<09:28:53.756> zeros 09:28:54.110 --> 09:28:54.120 align:start position:0% theoretically we could put three zeros 09:28:54.120 --> 09:28:56.266 align:start position:0% theoretically we could put three zeros here<09:28:54.240> and<09:28:54.360> one<09:28:54.540> zero<09:28:54.900> here<09:28:55.020> right<09:28:55.860> or<09:28:56.040> we<09:28:56.160> could 09:28:56.266 --> 09:28:56.276 align:start position:0% here and one zero here right or we could 09:28:56.276 --> 09:28:57.470 align:start position:0% here and one zero here right or we could do<09:28:56.400> it<09:28:56.460> the<09:28:56.580> other<09:28:56.640> way<09:28:56.756> around<09:28:56.880> so<09:28:57.180> the<09:28:57.360> reason 09:28:57.470 --> 09:28:57.480 align:start position:0% do it the other way around so the reason 09:28:57.480 --> 09:28:59.150 align:start position:0% do it the other way around so the reason we<09:28:57.660> can<09:28:57.776> only<09:28:57.900> do<09:28:58.080> it<09:28:58.200> once<09:28:58.500> is<09:28:58.680> because<09:28:58.860> then 09:28:59.150 --> 09:28:59.160 align:start position:0% we can only do it once is because then 09:28:59.160 --> 09:29:02.690 align:start position:0% we can only do it once is because then mathematically<09:28:59.936> we<09:29:00.540> know<09:29:00.660> exactly 09:29:02.690 --> 09:29:02.700 align:start position:0% mathematically we know exactly 09:29:02.700 --> 09:29:05.390 align:start position:0% mathematically we know exactly how<09:29:03.180> many<09:29:03.300> belong<09:29:03.776> when<09:29:04.140> we<09:29:04.256> do<09:29:04.436> that<09:29:04.620> all 09:29:05.390 --> 09:29:05.400 align:start position:0% how many belong when we do that all 09:29:05.400 --> 09:29:07.426 align:start position:0% how many belong when we do that all right<09:29:05.580> so<09:29:06.360> hopefully<09:29:06.596> that<09:29:06.660> helps<09:29:06.960> clarify 09:29:07.426 --> 09:29:07.436 align:start position:0% right so hopefully that helps clarify 09:29:07.436 --> 09:29:10.010 align:start position:0% right so hopefully that helps clarify the<09:29:07.916> reason<09:29:08.096> behind<09:29:08.640> the<09:29:09.300> success<09:29:09.540> of<09:29:09.660> zeros 09:29:10.010 --> 09:29:10.020 align:start position:0% the reason behind the success of zeros 09:29:10.020 --> 09:29:12.230 align:start position:0% the reason behind the success of zeros being<09:29:10.200> removed 09:29:12.230 --> 09:29:12.240 align:start position:0% being removed 09:29:12.240 --> 09:29:15.406 align:start position:0% being removed all<09:29:12.596> right<09:29:12.776> now<09:29:13.256> uh<09:29:13.560> what<09:29:13.800> this<09:29:13.980> also<09:29:14.400> means<09:29:14.820> is 09:29:15.406 --> 09:29:15.416 align:start position:0% all right now uh what this also means is 09:29:15.416 --> 09:29:17.086 align:start position:0% all right now uh what this also means is that<09:29:15.660> if<09:29:15.960> you<09:29:16.020> remember<09:29:16.140> a<09:29:16.436> loopback<09:29:16.800> address 09:29:17.086 --> 09:29:17.096 align:start position:0% that if you remember a loopback address 09:29:17.096 --> 09:29:20.990 align:start position:0% that if you remember a loopback address an<09:29:17.520> ipv4 09:29:20.990 --> 09:29:21.000 align:start position:0% 09:29:21.000 --> 09:29:23.766 align:start position:0% the<09:29:21.540> loopback<09:29:21.960> was 09:29:23.766 --> 09:29:23.776 align:start position:0% the loopback was 09:29:23.776 --> 09:29:26.390 align:start position:0% the loopback was 127.0.0.1<09:29:24.776> while<09:29:25.200> we<09:29:25.436> also<09:29:25.680> have<09:29:25.860> a<09:29:25.980> loop<09:29:26.276> back 09:29:26.390 --> 09:29:26.400 align:start position:0% 127.0.0.1 while we also have a loop back 09:29:26.400 --> 09:29:28.670 align:start position:0% 127.0.0.1 while we also have a loop back when<09:29:26.640> it<09:29:26.756> comes<09:29:26.936> to<09:29:27.060> IPv6 09:29:28.670 --> 09:29:28.680 align:start position:0% when it comes to IPv6 09:29:28.680 --> 09:29:31.310 align:start position:0% when it comes to IPv6 that's<09:29:29.340> all<09:29:29.700> these<09:29:29.936> zeros<09:29:30.300> to<09:29:30.540> one<09:29:30.720> but 09:29:31.310 --> 09:29:31.320 align:start position:0% that's all these zeros to one but 09:29:31.320 --> 09:29:34.130 align:start position:0% that's all these zeros to one but because<09:29:31.560> we<09:29:31.860> can<09:29:31.980> apply<09:29:32.276> all<09:29:32.580> of<09:29:32.700> these<09:29:32.880> rules 09:29:34.130 --> 09:29:34.140 align:start position:0% because we can apply all of these rules 09:29:34.140 --> 09:29:38.086 align:start position:0% because we can apply all of these rules we<09:29:34.560> can<09:29:34.620> truncate<09:29:35.096> this<09:29:35.460> to<09:29:36.060> Simply<09:29:36.360> this 09:29:38.086 --> 09:29:38.096 align:start position:0% we can truncate this to Simply this 09:29:38.096 --> 09:29:39.530 align:start position:0% we can truncate this to Simply this all<09:29:38.460> right 09:29:39.530 --> 09:29:39.540 align:start position:0% all right 09:29:39.540 --> 09:29:41.870 align:start position:0% all right so<09:29:40.080> uh<09:29:40.740> this<09:29:41.096> is<09:29:41.220> important<09:29:41.580> to<09:29:41.756> remember 09:29:41.870 --> 09:29:41.880 align:start position:0% so uh this is important to remember 09:29:41.880 --> 09:29:43.426 align:start position:0% so uh this is important to remember these<09:29:42.540> rules<09:29:42.840> are<09:29:42.960> important<09:29:43.256> to<09:29:43.320> remember 09:29:43.426 --> 09:29:43.436 align:start position:0% these rules are important to remember 09:29:43.436 --> 09:29:44.690 align:start position:0% these rules are important to remember the<09:29:43.860> other<09:29:43.980> thing<09:29:44.160> I<09:29:44.276> want<09:29:44.400> you<09:29:44.460> to<09:29:44.580> remember 09:29:44.690 --> 09:29:44.700 align:start position:0% the other thing I want you to remember 09:29:44.700 --> 09:29:47.926 align:start position:0% the other thing I want you to remember is<09:29:45.180> that<09:29:45.776> hexadecimal 09:29:47.926 --> 09:29:47.936 align:start position:0% is that hexadecimal 09:29:47.936 --> 09:29:52.370 align:start position:0% is that hexadecimal zero<09:29:48.840> to<09:29:48.900> nine<09:29:49.200> a<09:29:49.980> to<09:29:50.220> f<09:29:50.880> so<09:29:51.540> they<09:29:51.960> might<09:29:52.140> show 09:29:52.370 --> 09:29:52.380 align:start position:0% zero to nine a to f so they might show 09:29:52.380 --> 09:29:53.746 align:start position:0% zero to nine a to f so they might show you<09:29:52.560> something<09:29:52.740> and<09:29:52.980> say<09:29:53.096> which<09:29:53.276> of<09:29:53.460> these<09:29:53.640> is 09:29:53.746 --> 09:29:53.756 align:start position:0% you something and say which of these is 09:29:53.756 --> 09:29:56.390 align:start position:0% you something and say which of these is not<09:29:54.000> a<09:29:54.300> valid<09:29:54.660> IP 09:29:56.390 --> 09:29:56.400 align:start position:0% not a valid IP 09:29:56.400 --> 09:29:59.690 align:start position:0% not a valid IP if<09:29:56.880> it<09:29:57.060> has<09:29:57.180> a<09:29:57.360> letter<09:29:57.480> say<09:29:57.840> G<09:29:58.256> or<09:29:58.620> an<09:29:58.800> H<09:29:58.980> then 09:29:59.690 --> 09:29:59.700 align:start position:0% if it has a letter say G or an H then 09:29:59.700 --> 09:30:01.906 align:start position:0% if it has a letter say G or an H then you<09:29:59.936> know<09:30:00.120> it's<09:30:00.840> not<09:30:01.140> going<09:30:01.256> to<09:30:01.380> be<09:30:01.436> valid<09:30:01.800> and 09:30:01.906 --> 09:30:01.916 align:start position:0% you know it's not going to be valid and 09:30:01.916 --> 09:30:04.610 align:start position:0% you know it's not going to be valid and here<09:30:02.160> we<09:30:02.340> can<09:30:02.460> check<09:30:02.700> here's<09:30:03.240> a<09:30:03.416> d<09:30:03.540> That's<09:30:04.320> good 09:30:04.610 --> 09:30:04.620 align:start position:0% here we can check here's a d That's good 09:30:04.620 --> 09:30:08.086 align:start position:0% here we can check here's a d That's good here's<09:30:05.220> an<09:30:05.276> a<09:30:05.460> that's<09:30:05.700> good<09:30:05.936> C<09:30:06.840> good 09:30:08.086 --> 09:30:08.096 align:start position:0% here's an a that's good C good 09:30:08.096 --> 09:30:11.926 align:start position:0% here's an a that's good C good e<09:30:08.640> good<09:30:08.880> so<09:30:09.596> this<09:30:09.840> is<09:30:10.020> good<09:30:10.320> to<09:30:10.436> go<09:30:10.620> right<09:30:11.040> if<09:30:11.756> we 09:30:11.926 --> 09:30:11.936 align:start position:0% e good so this is good to go right if we 09:30:11.936 --> 09:30:14.570 align:start position:0% e good so this is good to go right if we had<09:30:12.180> an<09:30:12.540> H<09:30:12.720> or<09:30:12.960> a<09:30:13.140> g<09:30:13.256> or<09:30:13.620> an<09:30:13.740> X<09:30:13.980> for<09:30:14.340> instance 09:30:14.570 --> 09:30:14.580 align:start position:0% had an H or a g or an X for instance 09:30:14.580 --> 09:30:18.290 align:start position:0% had an H or a g or an X for instance then<09:30:14.880> we<09:30:15.120> would<09:30:15.240> know<09:30:15.480> that<09:30:16.256> the<09:30:16.860> um<09:30:17.000> IPv6<09:30:18.000> was 09:30:18.290 --> 09:30:18.300 align:start position:0% then we would know that the um IPv6 was 09:30:18.300 --> 09:30:20.510 align:start position:0% then we would know that the um IPv6 was incorrect<09:30:18.840> because<09:30:19.080> there's<09:30:19.436> no<09:30:19.680> hexadecimal 09:30:20.510 --> 09:30:20.520 align:start position:0% incorrect because there's no hexadecimal 09:30:20.520 --> 09:30:21.710 align:start position:0% incorrect because there's no hexadecimal symbol<09:30:20.880> X 09:30:21.710 --> 09:30:21.720 align:start position:0% symbol X 09:30:21.720 --> 09:30:25.670 align:start position:0% symbol X so<09:30:22.256> the<09:30:22.700> ipv4<09:30:23.960> addressing<09:30:24.960> method<09:30:25.256> is<09:30:25.380> is 09:30:25.670 --> 09:30:25.680 align:start position:0% so the ipv4 addressing method is is 09:30:25.680 --> 09:30:28.070 align:start position:0% so the ipv4 addressing method is is really<09:30:26.040> different<09:30:26.276> from<09:30:26.640> IPv6<09:30:27.416> addressing 09:30:28.070 --> 09:30:28.080 align:start position:0% really different from IPv6 addressing 09:30:28.080 --> 09:30:31.790 align:start position:0% really different from IPv6 addressing and<09:30:28.740> it's<09:30:28.980> comparatively<09:30:29.756> it's<09:30:30.540> lacking<09:30:31.380> in 09:30:31.790 --> 09:30:31.800 align:start position:0% and it's comparatively it's lacking in 09:30:31.800 --> 09:30:33.890 align:start position:0% and it's comparatively it's lacking in many<09:30:31.916> areas<09:30:32.340> first<09:30:33.060> as<09:30:33.300> we've<09:30:33.540> talked<09:30:33.776> about 09:30:33.890 --> 09:30:33.900 align:start position:0% many areas first as we've talked about 09:30:33.900 --> 09:30:37.010 align:start position:0% many areas first as we've talked about we're<09:30:34.500> using<09:30:34.800> a<09:30:34.980> 32-bit<09:30:35.580> binary<09:30:36.120> address<09:30:36.480> in 09:30:37.010 --> 09:30:37.020 align:start position:0% we're using a 32-bit binary address in 09:30:37.020 --> 09:30:39.970 align:start position:0% we're using a 32-bit binary address in ipv4<09:30:37.740> versus<09:30:38.580> a 09:30:39.970 --> 09:30:39.980 align:start position:0% ipv4 versus a 09:30:39.980 --> 09:30:44.690 align:start position:0% ipv4 versus a 128-bit<09:30:40.980> binary<09:30:41.460> address<09:30:41.960> in<09:30:42.960> IPv6<09:30:43.860> and<09:30:44.520> of 09:30:44.690 --> 09:30:44.700 align:start position:0% 128-bit binary address in IPv6 and of 09:30:44.700 --> 09:30:47.150 align:start position:0% 128-bit binary address in IPv6 and of course<09:30:44.820> this<09:30:45.180> greatly<09:30:45.660> increases<09:30:46.380> the<09:30:46.916> number 09:30:47.150 --> 09:30:47.160 align:start position:0% course this greatly increases the number 09:30:47.160 --> 09:30:50.086 align:start position:0% course this greatly increases the number of<09:30:47.580> possible<09:30:47.880> IP<09:30:48.240> addresses<09:30:48.776> I<09:30:49.680> think<09:30:49.860> around 09:30:50.086 --> 09:30:50.096 align:start position:0% of possible IP addresses I think around 09:30:50.096 --> 09:30:53.150 align:start position:0% of possible IP addresses I think around February<09:30:50.756> of<09:30:51.000> 2011<09:30:51.660> all<09:30:52.436> of<09:30:52.560> these<09:30:52.860> IP 09:30:53.150 --> 09:30:53.160 align:start position:0% February of 2011 all of these IP 09:30:53.160 --> 09:30:56.810 align:start position:0% February of 2011 all of these IP addresses<09:30:53.700> had<09:30:54.000> been<09:30:54.180> leased<09:30:54.776> and<09:30:55.680> uh<09:30:56.400> so 09:30:56.810 --> 09:30:56.820 align:start position:0% addresses had been leased and uh so 09:30:56.820 --> 09:30:58.490 align:start position:0% addresses had been leased and uh so there<09:30:57.180> weren't<09:30:57.416> any<09:30:57.596> addresses<09:30:58.020> left<09:30:58.200> I<09:30:58.380> think 09:30:58.490 --> 09:30:58.500 align:start position:0% there weren't any addresses left I think 09:30:58.500 --> 09:31:00.830 align:start position:0% there weren't any addresses left I think we<09:30:58.620> had<09:30:58.740> something<09:30:58.916> right<09:30:59.160> like<09:30:59.400> 4.8<09:31:00.060> 0.7 09:31:00.830 --> 09:31:00.840 align:start position:0% we had something right like 4.8 0.7 09:31:00.840 --> 09:31:03.050 align:start position:0% we had something right like 4.8 0.7 billion<09:31:01.380> right<09:31:01.980> and<09:31:02.160> all<09:31:02.340> those<09:31:02.460> were<09:31:02.756> gone 09:31:03.050 --> 09:31:03.060 align:start position:0% billion right and all those were gone 09:31:03.060 --> 09:31:06.530 align:start position:0% billion right and all those were gone and<09:31:03.840> so<09:31:04.080> we<09:31:04.500> were<09:31:04.620> depleted<09:31:05.096> of<09:31:05.340> all<09:31:05.756> of<09:31:05.880> our<09:31:06.180> IP 09:31:06.530 --> 09:31:06.540 align:start position:0% and so we were depleted of all of our IP 09:31:06.540 --> 09:31:07.790 align:start position:0% and so we were depleted of all of our IP addresses 09:31:07.790 --> 09:31:07.800 align:start position:0% addresses 09:31:07.800 --> 09:31:09.766 align:start position:0% addresses so<09:31:08.160> this<09:31:08.340> is<09:31:08.460> why<09:31:08.580> we<09:31:08.756> had<09:31:09.000> to<09:31:09.180> transition<09:31:09.480> to 09:31:09.766 --> 09:31:09.776 align:start position:0% so this is why we had to transition to 09:31:09.776 --> 09:31:12.290 align:start position:0% so this is why we had to transition to IPv6<09:31:10.500> because<09:31:11.220> now<09:31:11.520> we<09:31:11.820> have<09:31:11.936> that 09:31:12.290 --> 09:31:12.300 align:start position:0% IPv6 because now we have that 09:31:12.300 --> 09:31:15.230 align:start position:0% IPv6 because now we have that undecillion<09:31:13.200> uh<09:31:13.980> address<09:31:14.160> which<09:31:14.520> again<09:31:14.756> is<09:31:15.000> if 09:31:15.230 --> 09:31:15.240 align:start position:0% undecillion uh address which again is if 09:31:15.240 --> 09:31:17.390 align:start position:0% undecillion uh address which again is if every<09:31:15.540> there<09:31:16.200> were<09:31:16.380> a<09:31:16.436> trillion<09:31:16.740> people<09:31:16.980> they 09:31:17.390 --> 09:31:17.400 align:start position:0% every there were a trillion people they 09:31:17.400 --> 09:31:20.150 align:start position:0% every there were a trillion people they could<09:31:17.520> each<09:31:17.700> have<09:31:17.936> a<09:31:18.300> trillion<09:31:18.660> addresses<09:31:19.256> now 09:31:20.150 --> 09:31:20.160 align:start position:0% could each have a trillion addresses now 09:31:20.160 --> 09:31:22.906 align:start position:0% could each have a trillion addresses now another<09:31:20.520> major<09:31:21.180> difference<09:31:21.900> between<09:31:22.560> these 09:31:22.906 --> 09:31:22.916 align:start position:0% another major difference between these 09:31:22.916 --> 09:31:25.810 align:start position:0% another major difference between these two<09:31:23.096> is<09:31:23.460> that<09:31:23.756> uh<09:31:24.360> ipv4 09:31:25.810 --> 09:31:25.820 align:start position:0% two is that uh ipv4 09:31:25.820 --> 09:31:29.290 align:start position:0% two is that uh ipv4 utilized<09:31:26.820> the<09:31:27.240> classless<09:31:28.220> inter-domain 09:31:29.290 --> 09:31:29.300 align:start position:0% utilized the classless inter-domain 09:31:29.300 --> 09:31:31.426 align:start position:0% utilized the classless inter-domain routing<09:31:30.300> notation<09:31:30.660> if<09:31:30.900> you<09:31:31.020> remember<09:31:31.140> which 09:31:31.426 --> 09:31:31.436 align:start position:0% routing notation if you remember which 09:31:31.436 --> 09:31:33.586 align:start position:0% routing notation if you remember which had<09:31:31.680> that<09:31:31.916> slash<09:31:32.400> and<09:31:32.580> then<09:31:32.756> a<09:31:32.880> number<09:31:33.000> of<09:31:33.180> bits 09:31:33.586 --> 09:31:33.596 align:start position:0% had that slash and then a number of bits 09:31:33.596 --> 09:31:35.570 align:start position:0% had that slash and then a number of bits well 09:31:35.570 --> 09:31:35.580 align:start position:0% well 09:31:35.580 --> 09:31:39.890 align:start position:0% well in<09:31:36.180> IPv6<09:31:36.960> this<09:31:37.380> isn't<09:31:37.620> necessary<09:31:38.120> and<09:31:39.120> IPv6 09:31:39.890 --> 09:31:39.900 align:start position:0% in IPv6 this isn't necessary and IPv6 09:31:39.900 --> 09:31:42.350 align:start position:0% in IPv6 this isn't necessary and IPv6 actually<09:31:40.140> has<09:31:40.436> a<09:31:40.620> subnet<09:31:41.040> size<09:31:41.340> of<09:31:41.756> 2<09:31:42.000> to<09:31:42.180> the 09:31:42.350 --> 09:31:42.360 align:start position:0% actually has a subnet size of 2 to the 09:31:42.360 --> 09:31:46.490 align:start position:0% actually has a subnet size of 2 to the 64<09:31:42.720> power<09:31:43.020> now<09:31:43.980> if<09:31:44.460> you<09:31:44.580> remember 09:31:46.490 --> 09:31:46.500 align:start position:0% 64 power now if you remember 09:31:46.500 --> 09:31:50.926 align:start position:0% 64 power now if you remember that<09:31:47.096> the<09:31:47.340> total<09:31:47.580> IPv6<09:31:48.300> is<09:31:48.596> 2<09:31:48.776> to<09:31:49.020> the<09:31:49.140> 128<09:31:50.096> then 09:31:50.926 --> 09:31:50.936 align:start position:0% that the total IPv6 is 2 to the 128 then 09:31:50.936 --> 09:31:53.150 align:start position:0% that the total IPv6 is 2 to the 128 then what<09:31:51.300> you<09:31:51.416> realize<09:31:51.720> is<09:31:51.900> that<09:31:52.200> the<09:31:52.560> first<09:31:52.800> half 09:31:53.150 --> 09:31:53.160 align:start position:0% what you realize is that the first half 09:31:53.160 --> 09:31:56.690 align:start position:0% what you realize is that the first half of<09:31:53.880> the<09:31:54.000> IPv6<09:31:54.776> address<09:31:55.256> so<09:31:56.160> if<09:31:56.340> we<09:31:56.460> were<09:31:56.580> to 09:31:56.690 --> 09:31:56.700 align:start position:0% of the IPv6 address so if we were to 09:31:56.700 --> 09:32:03.246 align:start position:0% of the IPv6 address so if we were to write<09:31:56.880> one<09:31:57.060> out<09:31:57.240> again<09:31:57.480> let's<09:31:58.140> say<09:31:58.460> 2<09:31:59.460> 0<09:31:59.936> 8<09:32:00.596> a 09:32:03.246 --> 09:32:03.256 align:start position:0% 09:32:03.256 --> 09:32:06.230 align:start position:0% 3<09:32:04.256> 6<09:32:04.620> 4. 09:32:06.230 --> 09:32:06.240 align:start position:0% 3 6 4. 09:32:06.240 --> 09:32:11.746 align:start position:0% 3 6 4. uh<09:32:07.140> nine<09:32:07.860> two<09:32:08.520> B 09:32:11.746 --> 09:32:11.756 align:start position:0% 09:32:11.756 --> 09:32:14.350 align:start position:0% f 09:32:14.350 --> 09:32:14.360 align:start position:0% 09:32:14.360 --> 09:32:18.830 align:start position:0% one<09:32:15.360> zero<09:32:16.020> zero<09:32:16.620> zero<09:32:17.580> right<09:32:18.060> okay<09:32:18.300> so<09:32:18.660> then 09:32:18.830 --> 09:32:18.840 align:start position:0% one zero zero zero right okay so then 09:32:18.840 --> 09:32:20.210 align:start position:0% one zero zero zero right okay so then we're<09:32:19.020> gonna<09:32:19.080> have<09:32:19.256> four<09:32:19.500> more<09:32:19.680> on<09:32:19.860> this<09:32:20.040> side 09:32:20.210 --> 09:32:20.220 align:start position:0% we're gonna have four more on this side 09:32:20.220 --> 09:32:22.130 align:start position:0% we're gonna have four more on this side the<09:32:20.756> first<09:32:20.936> four 09:32:22.130 --> 09:32:22.140 align:start position:0% the first four 09:32:22.140 --> 09:32:24.710 align:start position:0% the first four which<09:32:22.620> again<09:32:22.740> is<09:32:23.040> the<09:32:23.220> first<09:32:23.340> 64<09:32:23.880> bits<09:32:24.300> that's 09:32:24.710 --> 09:32:24.720 align:start position:0% which again is the first 64 bits that's 09:32:24.720 --> 09:32:25.850 align:start position:0% which again is the first 64 bits that's the<09:32:24.960> subnet 09:32:25.850 --> 09:32:25.860 align:start position:0% the subnet 09:32:25.860 --> 09:32:28.130 align:start position:0% the subnet so<09:32:26.220> now<09:32:26.340> we've<09:32:26.756> integrated<09:32:27.240> the<09:32:27.480> subnet<09:32:27.840> into 09:32:28.130 --> 09:32:28.140 align:start position:0% so now we've integrated the subnet into 09:32:28.140 --> 09:32:30.710 align:start position:0% so now we've integrated the subnet into the<09:32:28.380> IPv6<09:32:29.160> address<09:32:29.640> which<09:32:30.300> is<09:32:30.416> the<09:32:30.596> benefit 09:32:30.710 --> 09:32:30.720 align:start position:0% the IPv6 address which is the benefit 09:32:30.720 --> 09:32:33.110 align:start position:0% the IPv6 address which is the benefit now<09:32:31.080> we<09:32:31.320> don't<09:32:31.436> have<09:32:31.620> to<09:32:31.916> sort<09:32:32.460> of<09:32:32.520> have<09:32:32.756> this 09:32:33.110 --> 09:32:33.120 align:start position:0% now we don't have to sort of have this 09:32:33.120 --> 09:32:34.310 align:start position:0% now we don't have to sort of have this extra 09:32:34.310 --> 09:32:34.320 align:start position:0% extra 09:32:34.320 --> 09:32:37.790 align:start position:0% extra uh<09:32:35.160> uh<09:32:35.160> written<09:32:35.820> out<09:32:36.000> cidr<09:32:36.720> thing<09:32:37.020> so<09:32:37.680> it's 09:32:37.790 --> 09:32:37.800 align:start position:0% uh uh written out cidr thing so it's 09:32:37.800 --> 09:32:39.586 align:start position:0% uh uh written out cidr thing so it's been<09:32:38.040> standardized<09:32:38.640> it's<09:32:38.820> always<09:32:39.060> 2<09:32:39.360> to<09:32:39.480> the 09:32:39.586 --> 09:32:39.596 align:start position:0% been standardized it's always 2 to the 09:32:39.596 --> 09:32:42.290 align:start position:0% been standardized it's always 2 to the 64.<09:32:40.140> we<09:32:40.380> always<09:32:40.560> know<09:32:40.860> the<09:32:41.096> subnet<09:32:41.520> or<09:32:42.120> the 09:32:42.290 --> 09:32:42.300 align:start position:0% 64. we always know the subnet or the 09:32:42.300 --> 09:32:46.130 align:start position:0% 64. we always know the subnet or the network<09:32:42.540> node<09:32:43.020> is<09:32:43.200> on<09:32:43.380> the<09:32:43.620> first 09:32:46.130 --> 09:32:46.140 align:start position:0% 09:32:46.140 --> 09:32:48.830 align:start position:0% section<09:32:46.860> and<09:32:47.400> the<09:32:47.640> node<09:32:47.820> ID<09:32:48.120> is<09:32:48.540> on<09:32:48.720> the 09:32:48.830 --> 09:32:48.840 align:start position:0% section and the node ID is on the 09:32:48.840 --> 09:32:50.990 align:start position:0% section and the node ID is on the section<09:32:49.080> the<09:32:49.560> second<09:32:49.740> section<09:32:50.276> the<09:32:50.700> other<09:32:50.820> two 09:32:50.990 --> 09:32:51.000 align:start position:0% section the second section the other two 09:32:51.000 --> 09:32:54.230 align:start position:0% section the second section the other two to<09:32:51.180> the<09:32:51.300> 64.<09:32:51.840> so<09:32:52.080> this<09:32:52.320> really<09:32:52.860> help<09:32:53.340> helps<09:32:54.060> us 09:32:54.230 --> 09:32:54.240 align:start position:0% to the 64. so this really help helps us 09:32:54.240 --> 09:32:56.570 align:start position:0% to the 64. so this really help helps us simplify<09:32:54.660> things<09:32:54.900> to<09:32:55.140> a<09:32:55.256> great<09:32:55.380> extent<09:32:55.740> now 09:32:56.570 --> 09:32:56.580 align:start position:0% simplify things to a great extent now 09:32:56.580 --> 09:32:58.010 align:start position:0% simplify things to a great extent now obviously<09:32:57.000> one<09:32:57.180> of<09:32:57.300> the<09:32:57.360> issues<09:32:57.660> is<09:32:57.840> we're 09:32:58.010 --> 09:32:58.020 align:start position:0% obviously one of the issues is we're 09:32:58.020 --> 09:33:00.530 align:start position:0% obviously one of the issues is we're going<09:32:58.140> to<09:32:58.256> under<09:32:58.620> use<09:32:59.180> a<09:33:00.180> lot<09:33:00.240> of<09:33:00.416> the 09:33:00.530 --> 09:33:00.540 align:start position:0% going to under use a lot of the 09:33:00.540 --> 09:33:01.970 align:start position:0% going to under use a lot of the addresses<09:33:01.020> we're<09:33:01.200> going<09:33:01.320> to<09:33:01.380> under<09:33:01.500> use<09:33:01.680> many 09:33:01.970 --> 09:33:01.980 align:start position:0% addresses we're going to under use many 09:33:01.980 --> 09:33:03.586 align:start position:0% addresses we're going to under use many of<09:33:02.096> our<09:33:02.220> addresses<09:33:02.640> because<09:33:02.880> we're<09:33:03.180> never 09:33:03.586 --> 09:33:03.596 align:start position:0% of our addresses because we're never 09:33:03.596 --> 09:33:04.850 align:start position:0% of our addresses because we're never going<09:33:03.776> to<09:33:03.900> have<09:33:03.960> to<09:33:04.080> really<09:33:04.200> use<09:33:04.436> this<09:33:04.680> many 09:33:04.850 --> 09:33:04.860 align:start position:0% going to have to really use this many 09:33:04.860 --> 09:33:07.130 align:start position:0% going to have to really use this many subnets<09:33:05.400> or<09:33:06.000> perhaps<09:33:06.480> not<09:33:06.660> even<09:33:06.776> that<09:33:07.020> many 09:33:07.130 --> 09:33:07.140 align:start position:0% subnets or perhaps not even that many 09:33:07.140 --> 09:33:10.370 align:start position:0% subnets or perhaps not even that many networks<09:33:07.800> right<09:33:08.040> but<09:33:09.360> um<09:33:09.416> there<09:33:10.020> are<09:33:10.140> so<09:33:10.256> many 09:33:10.370 --> 09:33:10.380 align:start position:0% networks right but um there are so many 09:33:10.380 --> 09:33:12.350 align:start position:0% networks right but um there are so many other<09:33:10.680> benefits<09:33:11.160> that<09:33:11.460> it<09:33:11.520> has<09:33:11.700> with<09:33:11.936> routing 09:33:12.350 --> 09:33:12.360 align:start position:0% other benefits that it has with routing 09:33:12.360 --> 09:33:14.746 align:start position:0% other benefits that it has with routing and<09:33:12.540> efficiency<09:33:13.020> and<09:33:13.916> simplified<09:33:14.340> management 09:33:14.746 --> 09:33:14.756 align:start position:0% and efficiency and simplified management 09:33:14.756 --> 09:33:17.330 align:start position:0% and efficiency and simplified management that<09:33:15.360> it<09:33:15.660> it<09:33:15.776> sort<09:33:16.320> of 09:33:17.330 --> 09:33:17.340 align:start position:0% that it it sort of 09:33:17.340 --> 09:33:19.906 align:start position:0% that it it sort of um<09:33:17.460> makes<09:33:18.416> up<09:33:18.660> for<09:33:18.900> it<09:33:19.080> and<09:33:19.256> so<09:33:19.436> that's<09:33:19.620> why 09:33:19.906 --> 09:33:19.916 align:start position:0% um makes up for it and so that's why 09:33:19.916 --> 09:33:22.906 align:start position:0% um makes up for it and so that's why we're<09:33:20.580> going<09:33:20.936> to<09:33:21.000> make<09:33:21.180> that<09:33:21.480> sacrifice<09:33:22.080> now 09:33:22.906 --> 09:33:22.916 align:start position:0% we're going to make that sacrifice now 09:33:22.916 --> 09:33:25.970 align:start position:0% we're going to make that sacrifice now in<09:33:23.220> terms<09:33:23.460> of<09:33:23.520> domain<09:33:24.000> name<09:33:24.300> systems<09:33:24.960> uh<09:33:25.560> with 09:33:25.970 --> 09:33:25.980 align:start position:0% in terms of domain name systems uh with 09:33:25.980 --> 09:33:28.906 align:start position:0% in terms of domain name systems uh with DNS<09:33:26.880> when<09:33:27.360> we<09:33:27.480> talked<09:33:27.840> about<09:33:27.960> for<09:33:28.436> instance<09:33:28.620> a 09:33:28.906 --> 09:33:28.916 align:start position:0% DNS when we talked about for instance a 09:33:28.916 --> 09:33:31.610 align:start position:0% DNS when we talked about for instance a google.com 09:33:31.610 --> 09:33:31.620 align:start position:0% 09:33:31.620 --> 09:33:35.570 align:start position:0% going<09:33:32.580> over<09:33:33.180> to<09:33:33.900> say<09:33:34.256> you<09:33:34.680> know<09:33:34.740> whatever<09:33:34.980> that 09:33:35.570 --> 09:33:35.580 align:start position:0% going over to say you know whatever that 09:33:35.580 --> 09:33:40.310 align:start position:0% going over to say you know whatever that IP<09:33:36.300> address<09:33:36.540> is 09:33:40.310 --> 09:33:40.320 align:start position:0% 09:33:40.320 --> 09:33:42.290 align:start position:0% I'm<09:33:40.860> making<09:33:41.220> this<09:33:41.400> one<09:33:41.520> up<09:33:41.640> obviously<09:33:42.060> it's 09:33:42.290 --> 09:33:42.300 align:start position:0% I'm making this one up obviously it's 09:33:42.300 --> 09:33:43.670 align:start position:0% I'm making this one up obviously it's not<09:33:42.480> a<09:33:42.660> real<09:33:42.720> one<09:33:42.900> because<09:33:43.140> we're<09:33:43.380> in<09:33:43.560> a 09:33:43.670 --> 09:33:43.680 align:start position:0% not a real one because we're in a 09:33:43.680 --> 09:33:45.170 align:start position:0% not a real one because we're in a private<09:33:43.916> IP 09:33:45.170 --> 09:33:45.180 align:start position:0% private IP 09:33:45.180 --> 09:33:48.050 align:start position:0% private IP but<09:33:45.596> this<09:33:45.720> was<09:33:45.900> called<09:33:46.140> an<09:33:46.380> a<09:33:46.560> record<09:33:46.800> right<09:33:47.700> so 09:33:48.050 --> 09:33:48.060 align:start position:0% but this was called an a record right so 09:33:48.060 --> 09:33:50.266 align:start position:0% but this was called an a record right so a<09:33:48.240> server<09:33:48.540> would<09:33:48.720> have<09:33:48.960> something<09:33:49.620> or<09:33:49.916> a<09:33:50.040> DNS 09:33:50.266 --> 09:33:50.276 align:start position:0% a server would have something or a DNS 09:33:50.276 --> 09:33:51.586 align:start position:0% a server would have something or a DNS server<09:33:50.520> would<09:33:50.640> have<09:33:50.756> something<09:33:50.936> called<09:33:51.180> an<09:33:51.416> a 09:33:51.586 --> 09:33:51.596 align:start position:0% server would have something called an a 09:33:51.596 --> 09:33:54.586 align:start position:0% server would have something called an a record<09:33:51.840> and<09:33:52.140> that<09:33:52.256> a<09:33:52.436> record<09:33:52.756> had<09:33:53.756> this 09:33:54.586 --> 09:33:54.596 align:start position:0% record and that a record had this 09:33:54.596 --> 09:33:57.170 align:start position:0% record and that a record had this information<09:33:54.776> in<09:33:55.380> it 09:33:57.170 --> 09:33:57.180 align:start position:0% information in it 09:33:57.180 --> 09:33:59.230 align:start position:0% information in it all<09:33:57.540> right<09:33:57.660> now<09:33:58.200> when<09:33:58.436> we're<09:33:58.560> dealing<09:33:58.916> with 09:33:59.230 --> 09:33:59.240 align:start position:0% all right now when we're dealing with 09:33:59.240 --> 09:34:02.030 align:start position:0% all right now when we're dealing with IPv6<09:34:00.240> we're<09:34:00.596> utilizing 09:34:02.030 --> 09:34:02.040 align:start position:0% IPv6 we're utilizing 09:34:02.040 --> 09:34:05.870 align:start position:0% IPv6 we're utilizing a<09:34:02.936> quad<09:34:03.300> a<09:34:03.596> record<09:34:03.840> for<09:34:04.680> this<09:34:04.860> mapping<09:34:05.276> now<09:34:05.700> we 09:34:05.870 --> 09:34:05.880 align:start position:0% a quad a record for this mapping now we 09:34:05.880 --> 09:34:08.030 align:start position:0% a quad a record for this mapping now we can<09:34:06.060> also<09:34:06.300> use<09:34:06.416> the<09:34:06.720> same<09:34:06.900> a<09:34:07.140> record<09:34:07.320> but<09:34:07.800> this 09:34:08.030 --> 09:34:08.040 align:start position:0% can also use the same a record but this 09:34:08.040 --> 09:34:10.190 align:start position:0% can also use the same a record but this quad<09:34:08.340> a<09:34:08.580> record<09:34:08.756> can<09:34:09.120> be<09:34:09.300> used<09:34:09.416> as<09:34:09.660> well<09:34:09.776> so<09:34:10.020> if 09:34:10.190 --> 09:34:10.200 align:start position:0% quad a record can be used as well so if 09:34:10.200 --> 09:34:14.030 align:start position:0% quad a record can be used as well so if you<09:34:10.320> see<09:34:10.700> Four<09:34:11.700> A's<09:34:12.240> what<09:34:12.840> we<09:34:13.020> call<09:34:13.140> a<09:34:13.436> 4A 09:34:14.030 --> 09:34:14.040 align:start position:0% you see Four A's what we call a 4A 09:34:14.040 --> 09:34:16.490 align:start position:0% you see Four A's what we call a 4A record<09:34:14.220> or<09:34:14.580> a<09:34:14.756> quad<09:34:15.060> a<09:34:15.360> record<09:34:15.596> then<09:34:16.200> you<09:34:16.380> know 09:34:16.490 --> 09:34:16.500 align:start position:0% record or a quad a record then you know 09:34:16.500 --> 09:34:18.350 align:start position:0% record or a quad a record then you know we're<09:34:16.740> using<09:34:16.980> IPv6<09:34:17.700> it's<09:34:17.936> one<09:34:18.120> of<09:34:18.240> the 09:34:18.350 --> 09:34:18.360 align:start position:0% we're using IPv6 it's one of the 09:34:18.360 --> 09:34:20.390 align:start position:0% we're using IPv6 it's one of the differences<09:34:18.840> and<09:34:19.320> again<09:34:19.500> these<09:34:20.096> are<09:34:20.220> the 09:34:20.390 --> 09:34:20.400 align:start position:0% differences and again these are the 09:34:20.400 --> 09:34:22.790 align:start position:0% differences and again these are the records<09:34:20.820> that<09:34:21.120> are<09:34:21.540> used<09:34:21.776> to<09:34:22.140> map<09:34:22.320> IP 09:34:22.790 --> 09:34:22.800 align:start position:0% records that are used to map IP 09:34:22.800 --> 09:34:25.970 align:start position:0% records that are used to map IP addresses<09:34:23.400> to<09:34:24.120> what<09:34:24.596> are<09:34:24.776> called<09:34:25.020> fully 09:34:25.970 --> 09:34:25.980 align:start position:0% addresses to what are called fully 09:34:25.980 --> 09:34:28.730 align:start position:0% addresses to what are called fully qualified<09:34:26.400> domain<09:34:27.300> names 09:34:28.730 --> 09:34:28.740 align:start position:0% qualified domain names 09:34:28.740 --> 09:34:31.010 align:start position:0% qualified domain names now<09:34:29.400> while<09:34:29.640> comparing<09:34:30.180> these<09:34:30.416> two<09:34:30.540> schemes 09:34:31.010 --> 09:34:31.020 align:start position:0% now while comparing these two schemes 09:34:31.020 --> 09:34:32.350 align:start position:0% now while comparing these two schemes also 09:34:32.350 --> 09:34:32.360 align:start position:0% also 09:34:32.360 --> 09:34:35.210 align:start position:0% also ipsec<09:34:33.360> which<09:34:33.596> stands<09:34:33.900> for<09:34:34.020> IP 09:34:35.210 --> 09:34:35.220 align:start position:0% ipsec which stands for IP 09:34:35.220 --> 09:34:37.670 align:start position:0% ipsec which stands for IP security<09:34:35.880> is<09:34:36.660> another<09:34:36.840> aspect<09:34:37.256> that<09:34:37.436> we<09:34:37.560> need 09:34:37.670 --> 09:34:37.680 align:start position:0% security is another aspect that we need 09:34:37.680 --> 09:34:42.350 align:start position:0% security is another aspect that we need to<09:34:37.800> consider<09:34:38.220> in<09:34:38.756> ipv4<09:34:39.800> ipsec<09:34:40.800> is<09:34:41.096> optional 09:34:42.350 --> 09:34:42.360 align:start position:0% to consider in ipv4 ipsec is optional 09:34:42.360 --> 09:34:46.246 align:start position:0% to consider in ipv4 ipsec is optional it's<09:34:43.080> widely<09:34:43.860> used<09:34:44.160> for<09:34:44.700> secure<09:34:45.416> traffic<09:34:45.720> over 09:34:46.246 --> 09:34:46.256 align:start position:0% it's widely used for secure traffic over 09:34:46.256 --> 09:34:50.150 align:start position:0% it's widely used for secure traffic over ipv4<09:34:47.096> Communications<09:34:47.900> but<09:34:48.900> when<09:34:49.620> we<09:34:49.800> dealt 09:34:50.150 --> 09:34:50.160 align:start position:0% ipv4 Communications but when we dealt 09:34:50.160 --> 09:34:51.670 align:start position:0% ipv4 Communications but when we dealt with 09:34:51.670 --> 09:34:51.680 align:start position:0% with 09:34:51.680 --> 09:34:56.510 align:start position:0% with IPv6<09:34:52.936> ipsec<09:34:53.936> was<09:34:54.240> designed<09:34:54.840> for<09:34:55.080> it<09:34:55.200> and<09:34:55.560> so<09:34:55.860> uh 09:34:56.510 --> 09:34:56.520 align:start position:0% IPv6 ipsec was designed for it and so uh 09:34:56.520 --> 09:34:58.190 align:start position:0% IPv6 ipsec was designed for it and so uh it's<09:34:56.820> required<09:34:57.480> from<09:34:57.840> the<09:34:58.020> original 09:34:58.190 --> 09:34:58.200 align:start position:0% it's required from the original 09:34:58.200 --> 09:35:00.950 align:start position:0% it's required from the original specification<09:34:59.160> and<09:34:59.580> therefore<09:34:59.960> all 09:35:00.950 --> 09:35:00.960 align:start position:0% specification and therefore all 09:35:00.960 --> 09:35:02.630 align:start position:0% specification and therefore all Communications<09:35:01.500> that<09:35:02.040> are<09:35:02.220> working<09:35:02.400> over 09:35:02.630 --> 09:35:02.640 align:start position:0% Communications that are working over 09:35:02.640 --> 09:35:04.926 align:start position:0% Communications that are working over IPv6<09:35:03.360> are<09:35:03.720> automatically<09:35:04.320> falling<09:35:04.740> under 09:35:04.926 --> 09:35:04.936 align:start position:0% IPv6 are automatically falling under 09:35:04.936 --> 09:35:10.246 align:start position:0% IPv6 are automatically falling under ipsec<09:35:06.080> so<09:35:07.080> it<09:35:08.040> can<09:35:08.220> be<09:35:08.520> considered<09:35:09.140> in<09:35:10.140> some 09:35:10.246 --> 09:35:10.256 align:start position:0% ipsec so it can be considered in some 09:35:10.256 --> 09:35:14.390 align:start position:0% ipsec so it can be considered in some ways<09:35:10.620> optional<09:35:11.340> I<09:35:11.580> guess<09:35:11.756> but<09:35:12.436> it<09:35:13.436> is<09:35:13.620> required 09:35:14.390 --> 09:35:14.400 align:start position:0% ways optional I guess but it is required 09:35:14.400 --> 09:35:18.110 align:start position:0% ways optional I guess but it is required use<09:35:14.700> from<09:35:15.416> the<09:35:15.596> get-go<09:35:15.960> because<09:35:16.320> it<09:35:16.680> was<09:35:17.120> built 09:35:18.110 --> 09:35:18.120 align:start position:0% use from the get-go because it was built 09:35:18.120 --> 09:35:22.310 align:start position:0% use from the get-go because it was built into<09:35:18.320> IPv6<09:35:19.340> now<09:35:20.340> the<09:35:20.580> IPv6<09:35:21.240> scheme<09:35:21.776> can<09:35:22.020> also 09:35:22.310 --> 09:35:22.320 align:start position:0% into IPv6 now the IPv6 scheme can also 09:35:22.320 --> 09:35:25.490 align:start position:0% into IPv6 now the IPv6 scheme can also handle<09:35:22.800> a<09:35:23.276> much<09:35:23.400> larger<09:35:23.936> packet<09:35:24.480> size<09:35:24.660> the 09:35:25.490 --> 09:35:25.500 align:start position:0% handle a much larger packet size the 09:35:25.500 --> 09:35:29.926 align:start position:0% handle a much larger packet size the packet<09:35:25.800> size<09:35:25.916> for<09:35:26.160> ipv4<09:35:26.820> is<09:35:27.480> 65<09:35:28.160> 535<09:35:29.160> octets 09:35:29.926 --> 09:35:29.936 align:start position:0% packet size for ipv4 is 65 535 octets 09:35:29.936 --> 09:35:32.810 align:start position:0% packet size for ipv4 is 65 535 octets payload<09:35:30.596> when<09:35:31.380> we<09:35:31.500> get<09:35:31.680> to<09:35:31.860> IPv6<09:35:32.580> we're 09:35:32.810 --> 09:35:32.820 align:start position:0% payload when we get to IPv6 we're 09:35:32.820 --> 09:35:34.030 align:start position:0% payload when we get to IPv6 we're dealing<09:35:33.120> with<09:35:33.240> a 09:35:34.030 --> 09:35:34.040 align:start position:0% dealing with a 09:35:34.040 --> 09:35:37.906 align:start position:0% dealing with a 4.295<09:35:35.040> billion<09:35:35.700> octets<09:35:36.240> of<09:35:36.660> payload<09:35:37.200> so 09:35:37.906 --> 09:35:37.916 align:start position:0% 4.295 billion octets of payload so 09:35:37.916 --> 09:35:39.470 align:start position:0% 4.295 billion octets of payload so obviously<09:35:38.400> these<09:35:38.700> are<09:35:38.756> a<09:35:38.880> lot<09:35:39.000> bigger<09:35:39.240> these 09:35:39.470 --> 09:35:39.480 align:start position:0% obviously these are a lot bigger these 09:35:39.480 --> 09:35:40.810 align:start position:0% obviously these are a lot bigger these are<09:35:39.596> what<09:35:39.720> we<09:35:39.900> call 09:35:40.810 --> 09:35:40.820 align:start position:0% are what we call 09:35:40.820 --> 09:35:43.426 align:start position:0% are what we call jumbo<09:35:41.820> grams 09:35:43.426 --> 09:35:43.436 align:start position:0% jumbo grams 09:35:43.436 --> 09:35:45.950 align:start position:0% jumbo grams as<09:35:44.040> a<09:35:44.220> result<09:35:44.340> you<09:35:44.820> can<09:35:44.880> imagine<09:35:45.120> that<09:35:45.660> if<09:35:45.776> we 09:35:45.950 --> 09:35:45.960 align:start position:0% as a result you can imagine that if we 09:35:45.960 --> 09:35:48.350 align:start position:0% as a result you can imagine that if we want<09:35:46.140> to<09:35:46.256> deal<09:35:46.380> with<09:35:46.680> ipv4<09:35:47.520> and<09:35:47.936> we're<09:35:48.120> on<09:35:48.240> an 09:35:48.350 --> 09:35:48.360 align:start position:0% want to deal with ipv4 and we're on an 09:35:48.360 --> 09:35:50.570 align:start position:0% want to deal with ipv4 and we're on an IPv6<09:35:48.960> Network<09:35:49.256> we're<09:35:49.800> going<09:35:49.980> to<09:35:50.096> have<09:35:50.220> to<09:35:50.400> make 09:35:50.570 --> 09:35:50.580 align:start position:0% IPv6 Network we're going to have to make 09:35:50.580 --> 09:35:52.850 align:start position:0% IPv6 Network we're going to have to make up<09:35:50.820> for<09:35:51.060> this<09:35:51.240> now<09:35:52.020> if<09:35:52.200> you<09:35:52.320> recall<09:35:52.560> we<09:35:52.800> were 09:35:52.850 --> 09:35:52.860 align:start position:0% up for this now if you recall we were 09:35:52.860 --> 09:35:54.710 align:start position:0% up for this now if you recall we were talking<09:35:53.040> about<09:35:53.220> ethernet<09:35:54.180> we<09:35:54.416> also<09:35:54.660> were 09:35:54.710 --> 09:35:54.720 align:start position:0% talking about ethernet we also were 09:35:54.720 --> 09:35:56.210 align:start position:0% talking about ethernet we also were talking<09:35:54.900> about<09:35:55.140> the<09:35:55.320> header<09:35:55.620> sizes<09:35:55.980> and<09:35:56.096> all 09:35:56.210 --> 09:35:56.220 align:start position:0% talking about the header sizes and all 09:35:56.220 --> 09:35:57.530 align:start position:0% talking about the header sizes and all the<09:35:56.400> information<09:35:56.520> that<09:35:56.880> was<09:35:57.000> contained<09:35:57.416> in 09:35:57.530 --> 09:35:57.540 align:start position:0% the information that was contained in 09:35:57.540 --> 09:36:00.890 align:start position:0% the information that was contained in there<09:35:57.720> well<09:35:58.320> the<09:35:58.560> header<09:35:58.860> size<09:35:59.040> for<09:35:59.340> ipv4<09:36:00.240> and 09:36:00.890 --> 09:36:00.900 align:start position:0% there well the header size for ipv4 and 09:36:00.900 --> 09:36:03.650 align:start position:0% there well the header size for ipv4 and IPv6<09:36:01.620> is<09:36:01.860> also<09:36:02.220> very<09:36:02.520> different<09:36:02.756> which 09:36:03.650 --> 09:36:03.660 align:start position:0% IPv6 is also very different which 09:36:03.660 --> 09:36:06.730 align:start position:0% IPv6 is also very different which actually<09:36:03.960> makes<09:36:04.560> these<09:36:05.276> two 09:36:06.730 --> 09:36:06.740 align:start position:0% actually makes these two 09:36:06.740 --> 09:36:09.406 align:start position:0% actually makes these two protocols<09:36:07.740> not<09:36:08.160> compatible<09:36:08.756> with<09:36:09.060> each<09:36:09.240> other 09:36:09.406 --> 09:36:09.416 align:start position:0% protocols not compatible with each other 09:36:09.416 --> 09:36:13.370 align:start position:0% protocols not compatible with each other so<09:36:10.020> IPv6<09:36:10.680> is<09:36:10.980> not<09:36:11.276> compatible<09:36:11.756> with<09:36:11.936> ipv4 09:36:13.370 --> 09:36:13.380 align:start position:0% so IPv6 is not compatible with ipv4 09:36:13.380 --> 09:36:15.406 align:start position:0% so IPv6 is not compatible with ipv4 and<09:36:14.220> so<09:36:14.520> the<09:36:14.820> way<09:36:14.936> we're<09:36:15.180> going<09:36:15.300> to 09:36:15.406 --> 09:36:15.416 align:start position:0% and so the way we're going to 09:36:15.416 --> 09:36:19.970 align:start position:0% and so the way we're going to communicate<09:36:15.960> with<09:36:16.200> an<09:36:16.380> IPv6 09:36:19.970 --> 09:36:19.980 align:start position:0% 09:36:19.980 --> 09:36:23.390 align:start position:0% over<09:36:20.580> an<09:36:20.756> ipv4<09:36:21.300> network<09:36:21.596> if<09:36:21.900> we<09:36:22.080> need<09:36:22.200> to<09:36:22.380> is<09:36:22.980> by 09:36:23.390 --> 09:36:23.400 align:start position:0% over an ipv4 network if we need to is by 09:36:23.400 --> 09:36:25.310 align:start position:0% over an ipv4 network if we need to is by tunneling 09:36:25.310 --> 09:36:25.320 align:start position:0% tunneling 09:36:25.320 --> 09:36:27.710 align:start position:0% tunneling the<09:36:25.800> packets<09:36:26.160> in<09:36:26.400> other<09:36:26.520> words<09:36:26.700> we<09:36:27.120> take<09:36:27.416> an 09:36:27.710 --> 09:36:27.720 align:start position:0% the packets in other words we take an 09:36:27.720 --> 09:36:32.690 align:start position:0% the packets in other words we take an ipv4<09:36:28.320> packet<09:36:28.860> I<09:36:29.520> mean<09:36:29.640> an<09:36:30.020> IPv6<09:36:31.020> packet<09:36:31.680> and<09:36:32.400> we 09:36:32.690 --> 09:36:32.700 align:start position:0% ipv4 packet I mean an IPv6 packet and we 09:36:32.700 --> 09:36:34.906 align:start position:0% ipv4 packet I mean an IPv6 packet and we literally<09:36:33.540> wrap 09:36:34.906 --> 09:36:34.916 align:start position:0% literally wrap 09:36:34.916 --> 09:36:37.070 align:start position:0% literally wrap it<09:36:35.276> around 09:36:37.070 --> 09:36:37.080 align:start position:0% it around 09:36:37.080 --> 09:36:39.830 align:start position:0% it around where<09:36:37.436> we<09:36:37.560> wrap<09:36:37.860> around<09:36:38.096> it<09:36:38.460> in<09:36:38.756> ipv4<09:36:39.416> packet 09:36:39.830 --> 09:36:39.840 align:start position:0% where we wrap around it in ipv4 packet 09:36:39.840 --> 09:36:43.130 align:start position:0% where we wrap around it in ipv4 packet and<09:36:40.020> so<09:36:40.200> we<09:36:40.436> tunnel<09:36:40.916> the<09:36:41.160> IPv6<09:36:41.820> packet<09:36:42.300> inside 09:36:43.130 --> 09:36:43.140 align:start position:0% and so we tunnel the IPv6 packet inside 09:36:43.140 --> 09:36:45.950 align:start position:0% and so we tunnel the IPv6 packet inside of<09:36:43.500> the<09:36:43.560> ipv4<09:36:44.220> now<09:36:45.000> this<09:36:45.240> allows<09:36:45.596> it<09:36:45.720> to 09:36:45.950 --> 09:36:45.960 align:start position:0% of the ipv4 now this allows it to 09:36:45.960 --> 09:36:47.746 align:start position:0% of the ipv4 now this allows it to communicate<09:36:46.500> but<09:36:46.800> this<09:36:47.040> is<09:36:47.160> also<09:36:47.400> what<09:36:47.580> we 09:36:47.746 --> 09:36:47.756 align:start position:0% communicate but this is also what we 09:36:47.756 --> 09:36:50.690 align:start position:0% communicate but this is also what we call<09:36:47.936> a<09:36:48.300> dual 09:36:50.690 --> 09:36:50.700 align:start position:0% call a dual 09:36:50.700 --> 09:36:52.266 align:start position:0% call a dual foreign 09:36:52.266 --> 09:36:52.276 align:start position:0% foreign 09:36:52.276 --> 09:36:54.290 align:start position:0% foreign in<09:36:53.276> some<09:36:53.400> cases<09:36:53.640> we<09:36:53.756> can<09:36:53.880> have<09:36:54.000> what's<09:36:54.120> called 09:36:54.290 --> 09:36:54.300 align:start position:0% in some cases we can have what's called 09:36:54.300 --> 09:36:57.830 align:start position:0% in some cases we can have what's called a<09:36:54.416> dual<09:36:54.660> stack<09:36:55.020> where<09:36:55.436> we<09:36:55.980> have<09:36:56.096> an<09:36:56.400> ipv4<09:36:57.120> and 09:36:57.830 --> 09:36:57.840 align:start position:0% a dual stack where we have an ipv4 and 09:36:57.840 --> 09:37:00.110 align:start position:0% a dual stack where we have an ipv4 and an<09:36:58.020> IPv6<09:36:58.740> and<09:36:59.040> so<09:36:59.220> we<09:36:59.400> can<09:36:59.520> choose<09:36:59.756> which<09:37:00.000> one 09:37:00.110 --> 09:37:00.120 align:start position:0% an IPv6 and so we can choose which one 09:37:00.120 --> 09:37:01.970 align:start position:0% an IPv6 and so we can choose which one to<09:37:00.300> go<09:37:00.416> over<09:37:00.540> and<09:37:01.140> then<09:37:01.256> this<09:37:01.380> tunneling<09:37:01.800> is 09:37:01.970 --> 09:37:01.980 align:start position:0% to go over and then this tunneling is 09:37:01.980 --> 09:37:04.906 align:start position:0% to go over and then this tunneling is not<09:37:02.160> going<09:37:02.276> to<09:37:02.400> be<09:37:02.460> necessary<09:37:02.936> now 09:37:04.906 --> 09:37:04.916 align:start position:0% not going to be necessary now 09:37:04.916 --> 09:37:06.586 align:start position:0% not going to be necessary now we<09:37:05.520> don't<09:37:05.640> really<09:37:05.820> want<09:37:06.000> a<09:37:06.180> tunnel<09:37:06.480> because 09:37:06.586 --> 09:37:06.596 align:start position:0% we don't really want a tunnel because 09:37:06.596 --> 09:37:08.266 align:start position:0% we don't really want a tunnel because obviously<09:37:07.140> the<09:37:07.320> payloads<09:37:07.860> are<09:37:07.980> so<09:37:08.160> much 09:37:08.266 --> 09:37:08.276 align:start position:0% obviously the payloads are so much 09:37:08.276 --> 09:37:09.530 align:start position:0% obviously the payloads are so much different<09:37:08.460> in<09:37:08.756> size<09:37:09.000> that<09:37:09.240> it's<09:37:09.360> going<09:37:09.480> to 09:37:09.530 --> 09:37:09.540 align:start position:0% different in size that it's going to 09:37:09.540 --> 09:37:11.690 align:start position:0% different in size that it's going to cause<09:37:09.660> all<09:37:09.840> sorts<09:37:10.140> of<09:37:10.140> trouble<09:37:10.436> so<09:37:11.340> what<09:37:11.580> we'll 09:37:11.690 --> 09:37:11.700 align:start position:0% cause all sorts of trouble so what we'll 09:37:11.700 --> 09:37:13.730 align:start position:0% cause all sorts of trouble so what we'll try<09:37:11.936> to<09:37:12.060> do<09:37:12.180> is<09:37:12.300> create<09:37:12.540> this<09:37:12.840> dual<09:37:13.080> stack<09:37:13.500> in 09:37:13.730 --> 09:37:13.740 align:start position:0% try to do is create this dual stack in 09:37:13.740 --> 09:37:16.490 align:start position:0% try to do is create this dual stack in which<09:37:13.916> we<09:37:14.220> have<09:37:14.400> one<09:37:15.060> network<09:37:15.360> and<09:37:16.200> the<09:37:16.380> other 09:37:16.490 --> 09:37:16.500 align:start position:0% which we have one network and the other 09:37:16.500 --> 09:37:18.350 align:start position:0% which we have one network and the other and<09:37:16.740> they're<09:37:16.860> both<09:37:17.040> operating<09:37:17.460> sort<09:37:17.820> of<09:37:17.936> side 09:37:18.350 --> 09:37:18.360 align:start position:0% and they're both operating sort of side 09:37:18.360 --> 09:37:20.746 align:start position:0% and they're both operating sort of side by<09:37:18.540> side<09:37:18.900> if<09:37:19.500> we<09:37:19.620> can't<09:37:19.800> do<09:37:20.040> that<09:37:20.160> then<09:37:20.400> we<09:37:20.580> have 09:37:20.746 --> 09:37:20.756 align:start position:0% by side if we can't do that then we have 09:37:20.756 --> 09:37:23.450 align:start position:0% by side if we can't do that then we have to<09:37:20.880> use<09:37:21.120> tunneling<09:37:22.020> in<09:37:22.320> order<09:37:22.500> to<09:37:22.916> move<09:37:23.160> the 09:37:23.450 --> 09:37:23.460 align:start position:0% to use tunneling in order to move the 09:37:23.460 --> 09:37:26.990 align:start position:0% to use tunneling in order to move the IPv6<09:37:24.360> data<09:37:24.840> over<09:37:25.020> an<09:37:25.320> ipv4<09:37:25.980> Network<09:37:26.276> which 09:37:26.990 --> 09:37:27.000 align:start position:0% IPv6 data over an ipv4 Network which 09:37:27.000 --> 09:37:30.530 align:start position:0% IPv6 data over an ipv4 Network which might<09:37:27.300> be<09:37:27.596> necessary<09:37:28.200> even<09:37:28.860> if<09:37:29.096> the<09:37:29.220> IPv6<09:37:30.060> data 09:37:30.530 --> 09:37:30.540 align:start position:0% might be necessary even if the IPv6 data 09:37:30.540 --> 09:37:33.050 align:start position:0% might be necessary even if the IPv6 data is<09:37:30.660> traveling<09:37:31.080> through<09:37:31.320> an<09:37:31.560> ipv4<09:37:32.160> Network 09:37:33.050 --> 09:37:33.060 align:start position:0% is traveling through an ipv4 Network 09:37:33.060 --> 09:37:34.670 align:start position:0% is traveling through an ipv4 Network all<09:37:33.416> right<09:37:33.480> so<09:37:33.660> we've<09:37:33.900> compared<09:37:34.320> these<09:37:34.500> let's 09:37:34.670 --> 09:37:34.680 align:start position:0% all right so we've compared these let's 09:37:34.680 --> 09:37:36.650 align:start position:0% all right so we've compared these let's talk<09:37:34.916> about<09:37:35.096> some<09:37:35.400> of<09:37:35.520> the<09:37:35.756> improvements<09:37:36.416> that 09:37:36.650 --> 09:37:36.660 align:start position:0% talk about some of the improvements that 09:37:36.660 --> 09:37:40.970 align:start position:0% talk about some of the improvements that ipv4<09:37:37.500> did<09:37:37.980> not<09:37:38.160> have<09:37:38.400> that<09:37:38.936> IPv6<09:37:39.596> does<09:37:39.980> uh 09:37:40.970 --> 09:37:40.980 align:start position:0% ipv4 did not have that IPv6 does uh 09:37:40.980 --> 09:37:43.790 align:start position:0% ipv4 did not have that IPv6 does uh starting<09:37:41.880> with<09:37:42.240> some<09:37:42.596> security<09:37:42.960> and<09:37:43.380> privacy 09:37:43.790 --> 09:37:43.800 align:start position:0% starting with some security and privacy 09:37:43.800 --> 09:37:47.746 align:start position:0% starting with some security and privacy measures<09:37:44.360> if<09:37:45.360> privacy<09:37:45.900> extensions<09:37:46.756> are 09:37:47.746 --> 09:37:47.756 align:start position:0% measures if privacy extensions are 09:37:47.756 --> 09:37:51.830 align:start position:0% measures if privacy extensions are enabled<09:37:48.300> with<09:37:48.680> IPv6<09:37:49.880> then<09:37:50.880> we<09:37:51.480> have<09:37:51.596> something 09:37:51.830 --> 09:37:51.840 align:start position:0% enabled with IPv6 then we have something 09:37:51.840 --> 09:37:54.110 align:start position:0% enabled with IPv6 then we have something called<09:37:52.140> an<09:37:52.436> ephemeral<09:37:52.916> address<09:37:53.400> which<09:37:53.936> is 09:37:54.110 --> 09:37:54.120 align:start position:0% called an ephemeral address which is 09:37:54.120 --> 09:37:55.370 align:start position:0% called an ephemeral address which is created 09:37:55.370 --> 09:37:55.380 align:start position:0% created 09:37:55.380 --> 09:37:58.070 align:start position:0% created and<09:37:55.860> this<09:37:56.040> is<09:37:56.220> used<09:37:56.460> as<09:37:57.000> a<09:37:57.360> temporary<09:37:57.776> and 09:37:58.070 --> 09:37:58.080 align:start position:0% and this is used as a temporary and 09:37:58.080 --> 09:37:59.690 align:start position:0% and this is used as a temporary and random<09:37:58.500> address<09:37:58.740> that's<09:37:59.160> used<09:37:59.400> to 09:37:59.690 --> 09:37:59.700 align:start position:0% random address that's used to 09:37:59.700 --> 09:38:02.330 align:start position:0% random address that's used to communicate<09:38:00.060> with<09:38:00.416> external<09:38:01.020> devices<09:38:01.380> but 09:38:02.330 --> 09:38:02.340 align:start position:0% communicate with external devices but 09:38:02.340 --> 09:38:04.190 align:start position:0% communicate with external devices but the<09:38:02.880> external<09:38:03.300> device<09:38:03.480> doesn't<09:38:03.776> know<09:38:03.960> the 09:38:04.190 --> 09:38:04.200 align:start position:0% the external device doesn't know the 09:38:04.200 --> 09:38:05.926 align:start position:0% the external device doesn't know the true<09:38:04.380> address<09:38:04.680> of<09:38:05.096> the<09:38:05.220> internal<09:38:05.520> device<09:38:05.700> and 09:38:05.926 --> 09:38:05.936 align:start position:0% true address of the internal device and 09:38:05.936 --> 09:38:09.230 align:start position:0% true address of the internal device and so<09:38:06.120> this<09:38:06.416> improves<09:38:06.960> the<09:38:07.680> the<09:38:08.160> privacy<09:38:09.000> and 09:38:09.230 --> 09:38:09.240 align:start position:0% so this improves the the privacy and 09:38:09.240 --> 09:38:11.570 align:start position:0% so this improves the the privacy and security<09:38:09.480> for<09:38:10.320> the<09:38:10.500> user<09:38:10.860> and<09:38:11.220> this<09:38:11.340> is<09:38:11.400> what 09:38:11.570 --> 09:38:11.580 align:start position:0% security for the user and this is what 09:38:11.580 --> 09:38:13.610 align:start position:0% security for the user and this is what we<09:38:11.700> call<09:38:11.820> a<09:38:12.180> privacy<09:38:12.540> extension<09:38:13.200> and<09:38:13.380> it<09:38:13.500> does 09:38:13.610 --> 09:38:13.620 align:start position:0% we call a privacy extension and it does 09:38:13.620 --> 09:38:16.310 align:start position:0% we call a privacy extension and it does have<09:38:13.860> to<09:38:14.040> be<09:38:14.340> enabled 09:38:16.310 --> 09:38:16.320 align:start position:0% have to be enabled 09:38:16.320 --> 09:38:19.010 align:start position:0% have to be enabled some<09:38:16.800> sort<09:38:17.040> of<09:38:17.160> a<09:38:17.220> router<09:38:17.580> point<09:38:17.756> of<09:38:17.936> view<09:38:18.120> now 09:38:19.010 --> 09:38:19.020 align:start position:0% some sort of a router point of view now 09:38:19.020 --> 09:38:20.926 align:start position:0% some sort of a router point of view now another<09:38:19.320> Improvement<09:38:19.980> is<09:38:20.640> a<09:38:20.820> better 09:38:20.926 --> 09:38:20.936 align:start position:0% another Improvement is a better 09:38:20.936 --> 09:38:22.906 align:start position:0% another Improvement is a better composition<09:38:21.360> of<09:38:21.596> what<09:38:21.720> we<09:38:21.840> call<09:38:22.020> the<09:38:22.320> unicast 09:38:22.906 --> 09:38:22.916 align:start position:0% composition of what we call the unicast 09:38:22.916 --> 09:38:25.550 align:start position:0% composition of what we call the unicast address<09:38:23.400> what<09:38:24.180> this<09:38:24.300> means<09:38:24.540> is<09:38:24.660> that<09:38:24.840> IPv6 09:38:25.550 --> 09:38:25.560 align:start position:0% address what this means is that IPv6 09:38:25.560 --> 09:38:29.570 align:start position:0% address what this means is that IPv6 uses<09:38:26.096> a<09:38:26.580> unicast<09:38:27.480> addressing<09:38:28.256> structure<09:38:28.800> to 09:38:29.570 --> 09:38:29.580 align:start position:0% uses a unicast addressing structure to 09:38:29.580 --> 09:38:33.190 align:start position:0% uses a unicast addressing structure to replace<09:38:29.820> the<09:38:30.540> classful<09:38:31.020> addresses<09:38:31.680> of<09:38:32.160> ipv4 09:38:33.190 --> 09:38:33.200 align:start position:0% replace the classful addresses of ipv4 09:38:33.200 --> 09:38:36.230 align:start position:0% replace the classful addresses of ipv4 this<09:38:34.200> offers<09:38:34.680> a<09:38:35.096> lot<09:38:35.160> more<09:38:35.340> flexibility<09:38:35.880> and 09:38:36.230 --> 09:38:36.240 align:start position:0% this offers a lot more flexibility and 09:38:36.240 --> 09:38:38.810 align:start position:0% this offers a lot more flexibility and efficiency<09:38:36.720> with<09:38:37.380> addressing<09:38:37.980> and<09:38:38.520> depending 09:38:38.810 --> 09:38:38.820 align:start position:0% efficiency with addressing and depending 09:38:38.820 --> 09:38:40.610 align:start position:0% efficiency with addressing and depending on<09:38:39.000> the<09:38:39.180> category<09:38:39.596> of<09:38:39.776> the<09:38:39.900> unicast<09:38:40.320> address 09:38:40.610 --> 09:38:40.620 align:start position:0% on the category of the unicast address 09:38:40.620 --> 09:38:42.766 align:start position:0% on the category of the unicast address used<09:38:41.160> there<09:38:41.520> are<09:38:41.640> different<09:38:41.820> functions<09:38:42.480> for 09:38:42.766 --> 09:38:42.776 align:start position:0% used there are different functions for 09:38:42.776 --> 09:38:45.586 align:start position:0% used there are different functions for each<09:38:43.020> meaning<09:38:43.860> that<09:38:44.300> there<09:38:45.300> are<09:38:45.416> different 09:38:45.586 --> 09:38:45.596 align:start position:0% each meaning that there are different 09:38:45.596 --> 09:38:47.810 align:start position:0% each meaning that there are different types<09:38:45.960> of<09:38:46.080> addresses<09:38:46.560> that<09:38:46.800> are<09:38:46.980> used<09:38:47.160> and 09:38:47.810 --> 09:38:47.820 align:start position:0% types of addresses that are used and 09:38:47.820 --> 09:38:49.610 align:start position:0% types of addresses that are used and that<09:38:48.000> way<09:38:48.180> the<09:38:48.596> computer<09:38:48.840> automatically 09:38:49.610 --> 09:38:49.620 align:start position:0% that way the computer automatically 09:38:49.620 --> 09:38:52.010 align:start position:0% that way the computer automatically knows<09:38:50.040> what<09:38:50.400> the<09:38:50.520> function<09:38:50.820> is<09:38:51.060> the<09:38:51.660> first<09:38:51.776> is 09:38:52.010 --> 09:38:52.020 align:start position:0% knows what the function is the first is 09:38:52.020 --> 09:38:54.950 align:start position:0% knows what the function is the first is called<09:38:52.256> a<09:38:52.620> global<09:38:53.160> address<09:38:53.700> which<09:38:54.480> is<09:38:54.660> sort<09:38:54.840> of 09:38:54.950 --> 09:38:54.960 align:start position:0% called a global address which is sort of 09:38:54.960 --> 09:38:58.426 align:start position:0% called a global address which is sort of like<09:38:55.256> the<09:38:55.916> public<09:38:56.160> or<09:38:56.520> routable<09:38:56.936> addresses<09:38:57.660> uh 09:38:58.426 --> 09:38:58.436 align:start position:0% like the public or routable addresses uh 09:38:58.436 --> 09:39:01.310 align:start position:0% like the public or routable addresses uh in<09:38:58.620> ipv4<09:38:59.276> if<09:38:59.756> you<09:38:59.936> recall<09:39:00.300> most<09:39:00.720> addresses 09:39:01.310 --> 09:39:01.320 align:start position:0% in ipv4 if you recall most addresses 09:39:01.320 --> 09:39:03.350 align:start position:0% in ipv4 if you recall most addresses could<09:39:01.620> be<09:39:01.800> routed<09:39:02.276> those<09:39:02.820> are<09:39:03.000> what<09:39:03.060> we<09:39:03.180> call 09:39:03.350 --> 09:39:03.360 align:start position:0% could be routed those are what we call 09:39:03.360 --> 09:39:05.150 align:start position:0% could be routed those are what we call Global<09:39:03.840> addresses 09:39:05.150 --> 09:39:05.160 align:start position:0% Global addresses 09:39:05.160 --> 09:39:08.150 align:start position:0% Global addresses we<09:39:05.640> also<09:39:05.880> have<09:39:06.000> site<09:39:06.360> local<09:39:06.720> addresses<09:39:07.500> which 09:39:08.150 --> 09:39:08.160 align:start position:0% we also have site local addresses which 09:39:08.160 --> 09:39:09.710 align:start position:0% we also have site local addresses which are<09:39:08.400> essentially<09:39:08.756> like<09:39:09.000> the<09:39:09.300> private 09:39:09.710 --> 09:39:09.720 align:start position:0% are essentially like the private 09:39:09.720 --> 09:39:12.050 align:start position:0% are essentially like the private addresses<09:39:10.256> or<09:39:10.620> non-routable<09:39:11.276> addresses<09:39:11.820> that 09:39:12.050 --> 09:39:12.060 align:start position:0% addresses or non-routable addresses that 09:39:12.060 --> 09:39:14.030 align:start position:0% addresses or non-routable addresses that are<09:39:12.180> not<09:39:12.300> routable<09:39:12.660> to<09:39:12.840> external<09:39:13.256> networks<09:39:13.680> if 09:39:14.030 --> 09:39:14.040 align:start position:0% are not routable to external networks if 09:39:14.040 --> 09:39:15.290 align:start position:0% are not routable to external networks if you<09:39:14.220> recall 09:39:15.290 --> 09:39:15.300 align:start position:0% you recall 09:39:15.300 --> 09:39:19.210 align:start position:0% you recall these<09:39:15.960> were<09:39:16.200> for<09:39:16.500> instance<09:39:16.800> the 09:39:19.210 --> 09:39:19.220 align:start position:0% these were for instance the 09:39:19.220 --> 09:39:22.870 align:start position:0% these were for instance the 10.0.0.0<09:39:20.220> through 09:39:22.870 --> 09:39:22.880 align:start position:0% 10.0.0.0 through 09:39:22.880 --> 09:39:27.190 align:start position:0% 10.0.0.0 through 10.255.255<09:39:23.880> at<09:39:24.060> 255<09:39:24.660> and<09:39:25.200> then<09:39:25.320> the 09:39:27.190 --> 09:39:27.200 align:start position:0% 10.255.255 at 255 and then the 09:39:27.200 --> 09:39:31.246 align:start position:0% 10.255.255 at 255 and then the 172.16-32<09:39:28.200> and<09:39:28.980> then<09:39:29.040> the<09:39:29.776> 192.168<09:39:30.776> those<09:39:31.080> are 09:39:31.246 --> 09:39:31.256 align:start position:0% 172.16-32 and then the 192.168 those are 09:39:31.256 --> 09:39:34.190 align:start position:0% 172.16-32 and then the 192.168 those are the<09:39:31.380> private<09:39:31.800> addresses<09:39:32.400> well<09:39:33.060> in<09:39:33.360> IPv6<09:39:33.960> we 09:39:34.190 --> 09:39:34.200 align:start position:0% the private addresses well in IPv6 we 09:39:34.200 --> 09:39:36.890 align:start position:0% the private addresses well in IPv6 we call<09:39:34.380> them<09:39:34.560> site<09:39:34.916> local<09:39:35.220> addresses<09:39:36.000> we<09:39:36.720> also 09:39:36.890 --> 09:39:36.900 align:start position:0% call them site local addresses we also 09:39:36.900 --> 09:39:38.210 align:start position:0% call them site local addresses we also have<09:39:37.020> something<09:39:37.140> called<09:39:37.380> link<09:39:37.800> local 09:39:38.210 --> 09:39:38.220 align:start position:0% have something called link local 09:39:38.220 --> 09:39:40.190 align:start position:0% have something called link local addresses<09:39:38.936> which<09:39:39.240> are<09:39:39.360> basically<09:39:39.660> comparable 09:39:40.190 --> 09:39:40.200 align:start position:0% addresses which are basically comparable 09:39:40.200 --> 09:39:43.970 align:start position:0% addresses which are basically comparable to<09:39:41.160> a<09:39:41.640> pipa<09:39:42.360> addresses<09:39:42.840> in<09:39:43.080> ipv4<09:39:43.620> and<09:39:43.860> we're 09:39:43.970 --> 09:39:43.980 align:start position:0% to a pipa addresses in ipv4 and we're 09:39:43.980 --> 09:39:45.350 align:start position:0% to a pipa addresses in ipv4 and we're going<09:39:44.096> to<09:39:44.160> talk<09:39:44.276> more<09:39:44.460> about<09:39:44.640> what<09:39:44.936> those<09:39:45.120> mean 09:39:45.350 --> 09:39:45.360 align:start position:0% going to talk more about what those mean 09:39:45.360 --> 09:39:48.350 align:start position:0% going to talk more about what those mean in<09:39:45.660> just<09:39:45.840> a<09:39:46.200> little<09:39:46.680> bit<09:39:46.800> later<09:39:46.980> but<09:39:47.820> just<09:39:48.120> to 09:39:48.350 --> 09:39:48.360 align:start position:0% in just a little bit later but just to 09:39:48.360 --> 09:39:50.210 align:start position:0% in just a little bit later but just to give<09:39:48.660> you<09:39:48.776> a<09:39:48.960> little<09:39:49.080> heads<09:39:49.680> up<09:39:49.740> and<09:39:49.916> we<09:39:50.096> have 09:39:50.210 --> 09:39:50.220 align:start position:0% give you a little heads up and we have 09:39:50.220 --> 09:39:53.690 align:start position:0% give you a little heads up and we have talked<09:39:50.580> about<09:39:50.700> it<09:39:51.000> with<09:39:51.776> uh<09:39:52.140> uh<09:39:52.916> a<09:39:53.160> plus<09:39:53.340> if<09:39:53.580> you 09:39:53.690 --> 09:39:53.700 align:start position:0% talked about it with uh uh a plus if you 09:39:53.700 --> 09:39:56.690 align:start position:0% talked about it with uh uh a plus if you around<09:39:53.880> for<09:39:54.180> that<09:39:54.300> this<09:39:54.960> is<09:39:55.200> automatic 09:39:56.690 --> 09:39:56.700 align:start position:0% around for that this is automatic 09:39:56.700 --> 09:39:58.850 align:start position:0% around for that this is automatic private 09:39:58.850 --> 09:39:58.860 align:start position:0% private 09:39:58.860 --> 09:40:02.990 align:start position:0% private IP<09:39:59.840> addressing<09:40:00.840> and<09:40:01.620> we<09:40:01.916> need<09:40:02.096> because<09:40:02.580> every 09:40:02.990 --> 09:40:03.000 align:start position:0% IP addressing and we need because every 09:40:03.000 --> 09:40:05.266 align:start position:0% IP addressing and we need because every device<09:40:03.240> needs<09:40:03.720> an<09:40:03.960> automatic<09:40:04.436> IP<09:40:04.740> address<09:40:04.916> if 09:40:05.266 --> 09:40:05.276 align:start position:0% device needs an automatic IP address if 09:40:05.276 --> 09:40:07.426 align:start position:0% device needs an automatic IP address if it's<09:40:05.400> not<09:40:05.640> given<09:40:05.936> one<09:40:06.120> by<09:40:06.480> a<09:40:06.660> server<09:40:06.900> then<09:40:07.256> it's 09:40:07.426 --> 09:40:07.436 align:start position:0% it's not given one by a server then it's 09:40:07.436 --> 09:40:08.926 align:start position:0% it's not given one by a server then it's going<09:40:07.560> to<09:40:07.620> give<09:40:07.740> itself<09:40:08.040> one<09:40:08.276> what<09:40:08.520> we<09:40:08.640> call<09:40:08.756> an 09:40:08.926 --> 09:40:08.936 align:start position:0% going to give itself one what we call an 09:40:08.936 --> 09:40:12.050 align:start position:0% going to give itself one what we call an apipa<09:40:09.480> address<09:40:09.660> and<09:40:10.380> so<09:40:10.620> in<09:40:11.096> IPv6<09:40:11.640> these<09:40:11.936> are 09:40:12.050 --> 09:40:12.060 align:start position:0% apipa address and so in IPv6 these are 09:40:12.060 --> 09:40:15.050 align:start position:0% apipa address and so in IPv6 these are called<09:40:12.180> link<09:40:12.540> local<09:40:13.020> addresses 09:40:15.050 --> 09:40:15.060 align:start position:0% called link local addresses 09:40:15.060 --> 09:40:17.746 align:start position:0% called link local addresses finally<09:40:15.300> there<09:40:15.720> are<09:40:15.900> IPv6<09:40:16.756> transitional 09:40:17.746 --> 09:40:17.756 align:start position:0% finally there are IPv6 transitional 09:40:17.756 --> 09:40:19.670 align:start position:0% finally there are IPv6 transitional addresses<09:40:18.660> which<09:40:19.020> are<09:40:19.140> basically<09:40:19.436> going<09:40:19.620> to 09:40:19.670 --> 09:40:19.680 align:start position:0% addresses which are basically going to 09:40:19.680 --> 09:40:22.010 align:start position:0% addresses which are basically going to be<09:40:19.740> used<09:40:19.916> in<09:40:20.096> the<09:40:20.276> time<09:40:20.460> being<09:40:20.756> until<09:40:21.300> we<09:40:21.720> phase 09:40:22.010 --> 09:40:22.020 align:start position:0% be used in the time being until we phase 09:40:22.020 --> 09:40:26.990 align:start position:0% be used in the time being until we phase out<09:40:22.380> of<09:40:22.620> ipv4<09:40:23.660> these<09:40:24.660> are<09:40:24.776> used<09:40:25.020> to<09:40:25.320> Route<09:40:26.000> IPv6 09:40:26.990 --> 09:40:27.000 align:start position:0% out of ipv4 these are used to Route IPv6 09:40:27.000 --> 09:40:30.230 align:start position:0% out of ipv4 these are used to Route IPv6 traffic<09:40:27.480> across<09:40:28.380> ipv4<09:40:29.096> networks<09:40:29.640> through 09:40:30.230 --> 09:40:30.240 align:start position:0% traffic across ipv4 networks through 09:40:30.240 --> 09:40:31.970 align:start position:0% traffic across ipv4 networks through tunneling<09:40:30.776> much<09:40:30.960> like<09:40:31.140> I've<09:40:31.380> just<09:40:31.560> described 09:40:31.970 --> 09:40:31.980 align:start position:0% tunneling much like I've just described 09:40:31.980 --> 09:40:36.406 align:start position:0% tunneling much like I've just described in<09:40:32.276> the<09:40:32.460> previous<09:40:32.580> section 09:40:36.406 --> 09:40:36.416 align:start position:0% 09:40:36.416 --> 09:40:40.310 align:start position:0% now<09:40:37.080> a<09:40:37.380> mechanism<09:40:37.800> uh<09:40:38.756> built<09:40:39.180> into<09:40:39.360> IPv6 09:40:40.310 --> 09:40:40.320 align:start position:0% now a mechanism uh built into IPv6 09:40:40.320 --> 09:40:43.850 align:start position:0% now a mechanism uh built into IPv6 addresses<09:40:41.096> is<09:40:41.580> a<09:40:41.756> field<09:40:41.880> located<09:40:42.300> in<09:40:42.900> the<09:40:43.140> IP 09:40:43.850 --> 09:40:43.860 align:start position:0% addresses is a field located in the IP 09:40:43.860 --> 09:40:47.150 align:start position:0% addresses is a field located in the IP header 09:40:47.150 --> 09:40:47.160 align:start position:0% 09:40:47.160 --> 09:40:49.550 align:start position:0% that's<09:40:47.880> designed<09:40:48.360> to<09:40:48.720> guarantee<09:40:49.256> network 09:40:49.550 --> 09:40:49.560 align:start position:0% that's designed to guarantee network 09:40:49.560 --> 09:40:52.130 align:start position:0% that's designed to guarantee network resources<09:40:50.220> be<09:40:50.460> allowed<09:40:50.820> allocated<09:40:51.596> to 09:40:52.130 --> 09:40:52.140 align:start position:0% resources be allowed allocated to 09:40:52.140 --> 09:40:54.290 align:start position:0% resources be allowed allocated to services<09:40:52.380> that<09:40:52.916> need<09:40:53.040> time<09:40:53.340> sensitive<09:40:53.820> data 09:40:54.290 --> 09:40:54.300 align:start position:0% services that need time sensitive data 09:40:54.300 --> 09:40:57.530 align:start position:0% services that need time sensitive data such<09:40:54.840> as<09:40:54.960> voice<09:40:55.380> over<09:40:55.620> IP<09:40:56.160> right<09:40:56.756> we<09:40:57.120> need<09:40:57.240> that 09:40:57.530 --> 09:40:57.540 align:start position:0% such as voice over IP right we need that 09:40:57.540 --> 09:40:58.970 align:start position:0% such as voice over IP right we need that that<09:40:57.776> is<09:40:57.960> time<09:40:58.200> sensitive<09:40:58.620> because<09:40:58.740> I'm 09:40:58.970 --> 09:40:58.980 align:start position:0% that is time sensitive because I'm 09:40:58.980 --> 09:41:00.170 align:start position:0% that is time sensitive because I'm talking<09:40:59.160> and<09:40:59.340> I<09:40:59.520> want<09:40:59.580> the<09:40:59.700> person<09:40:59.820> to<09:41:00.060> hear 09:41:00.170 --> 09:41:00.180 align:start position:0% talking and I want the person to hear 09:41:00.180 --> 09:41:02.266 align:start position:0% talking and I want the person to hear almost<09:41:00.480> as<09:41:00.720> soon<09:41:00.900> as<09:41:01.020> I<09:41:01.256> talk<09:41:01.380> and<09:41:01.916> so<09:41:02.040> this 09:41:02.266 --> 09:41:02.276 align:start position:0% almost as soon as I talk and so this 09:41:02.276 --> 09:41:05.390 align:start position:0% almost as soon as I talk and so this time<09:41:02.520> sensitive<09:41:03.000> stuff<09:41:03.300> is<09:41:04.020> built<09:41:04.380> into<09:41:04.680> IPv6 09:41:05.390 --> 09:41:05.400 align:start position:0% time sensitive stuff is built into IPv6 09:41:05.400 --> 09:41:07.426 align:start position:0% time sensitive stuff is built into IPv6 one<09:41:05.640> of<09:41:05.756> the<09:41:05.820> reasons<09:41:06.060> that<09:41:06.180> we<09:41:06.360> use<09:41:06.480> it<09:41:06.660> now 09:41:07.426 --> 09:41:07.436 align:start position:0% one of the reasons that we use it now 09:41:07.436 --> 09:41:09.350 align:start position:0% one of the reasons that we use it now another<09:41:07.740> improvement<09:41:08.460> with<09:41:08.820> this<09:41:09.060> scheme 09:41:09.350 --> 09:41:09.360 align:start position:0% another improvement with this scheme 09:41:09.360 --> 09:41:12.230 align:start position:0% another improvement with this scheme IPv6<09:41:10.020> is<09:41:10.256> called<09:41:10.500> hierarchical<09:41:11.400> addressing 09:41:12.230 --> 09:41:12.240 align:start position:0% IPv6 is called hierarchical addressing 09:41:12.240 --> 09:41:14.810 align:start position:0% IPv6 is called hierarchical addressing this<09:41:12.960> eliminates<09:41:13.500> the<09:41:13.860> random<09:41:14.160> allocation<09:41:14.640> of 09:41:14.810 --> 09:41:14.820 align:start position:0% this eliminates the random allocation of 09:41:14.820 --> 09:41:18.110 align:start position:0% this eliminates the random allocation of addresses<09:41:15.680> so<09:41:16.680> connectivity<09:41:17.340> devices<09:41:17.700> such 09:41:18.110 --> 09:41:18.120 align:start position:0% addresses so connectivity devices such 09:41:18.120 --> 09:41:21.470 align:start position:0% addresses so connectivity devices such as<09:41:18.240> top<09:41:18.540> level<09:41:18.776> routers<09:41:19.436> are<09:41:20.220> assigned<09:41:20.820> a<09:41:21.240> top 09:41:21.470 --> 09:41:21.480 align:start position:0% as top level routers are assigned a top 09:41:21.480 --> 09:41:25.490 align:start position:0% as top level routers are assigned a top level<09:41:21.660> block<09:41:22.140> of<09:41:23.000> ivv6<09:41:24.000> addresses<09:41:24.776> and<09:41:25.380> then 09:41:25.490 --> 09:41:25.500 align:start position:0% level block of ivv6 addresses and then 09:41:25.500 --> 09:41:27.830 align:start position:0% level block of ivv6 addresses and then segments<09:41:26.040> are<09:41:26.096> added<09:41:26.400> to<09:41:26.520> those<09:41:26.820> with<09:41:27.416> blocks 09:41:27.830 --> 09:41:27.840 align:start position:0% segments are added to those with blocks 09:41:27.840 --> 09:41:29.330 align:start position:0% segments are added to those with blocks of<09:41:27.960> addresses<09:41:28.436> that<09:41:28.620> are<09:41:28.740> assigned<09:41:29.096> at<09:41:29.160> that 09:41:29.330 --> 09:41:29.340 align:start position:0% of addresses that are assigned at that 09:41:29.340 --> 09:41:31.610 align:start position:0% of addresses that are assigned at that level<09:41:29.520> so<09:41:30.240> basically<09:41:30.540> it<09:41:30.900> looks<09:41:31.140> like<09:41:31.320> a 09:41:31.610 --> 09:41:31.620 align:start position:0% level so basically it looks like a 09:41:31.620 --> 09:41:32.810 align:start position:0% level so basically it looks like a hierarchy 09:41:32.810 --> 09:41:32.820 align:start position:0% hierarchy 09:41:32.820 --> 09:41:36.766 align:start position:0% hierarchy from<09:41:33.360> an<09:41:33.540> IPv6<09:41:34.436> standpoint 09:41:36.766 --> 09:41:36.776 align:start position:0% from an IPv6 standpoint 09:41:36.776 --> 09:41:39.230 align:start position:0% from an IPv6 standpoint you<09:41:37.200> remember<09:41:37.320> we<09:41:37.560> looked<09:41:37.800> at<09:41:37.860> an<09:41:38.096> uh<09:41:38.580> this 09:41:39.230 --> 09:41:39.240 align:start position:0% you remember we looked at an uh this 09:41:39.240 --> 09:41:41.810 align:start position:0% you remember we looked at an uh this sort<09:41:39.360> of<09:41:39.480> topology<09:41:39.900> earlier 09:41:41.810 --> 09:41:41.820 align:start position:0% sort of topology earlier 09:41:41.820 --> 09:41:44.330 align:start position:0% sort of topology earlier now<09:41:42.300> ibv6<09:41:43.080> scheme<09:41:43.560> also<09:41:43.860> has<09:41:43.980> a<09:41:44.220> much 09:41:44.330 --> 09:41:44.340 align:start position:0% now ibv6 scheme also has a much 09:41:44.340 --> 09:41:46.610 align:start position:0% now ibv6 scheme also has a much simplified<09:41:44.756> header<09:41:45.416> and<09:41:46.140> it's<09:41:46.256> going<09:41:46.436> to<09:41:46.560> make 09:41:46.610 --> 09:41:46.620 align:start position:0% simplified header and it's going to make 09:41:46.620 --> 09:41:48.950 align:start position:0% simplified header and it's going to make addressing<09:41:47.276> a<09:41:47.460> lot<09:41:47.580> easier<09:41:47.936> to<09:41:48.180> read 09:41:48.950 --> 09:41:48.960 align:start position:0% addressing a lot easier to read 09:41:48.960 --> 09:41:51.530 align:start position:0% addressing a lot easier to read this<09:41:49.436> improves<09:41:50.040> the<09:41:50.400> speed<09:41:50.580> packet<09:41:51.120> routing 09:41:51.530 --> 09:41:51.540 align:start position:0% this improves the speed packet routing 09:41:51.540 --> 09:41:54.406 align:start position:0% this improves the speed packet routing on<09:41:52.080> an<09:41:52.320> individual<09:41:52.800> packet<09:41:53.276> basis<09:41:53.756> so 09:41:54.406 --> 09:41:54.416 align:start position:0% on an individual packet basis so 09:41:54.416 --> 09:41:56.210 align:start position:0% on an individual packet basis so obviously<09:41:54.900> if<09:41:55.140> we<09:41:55.256> can 09:41:56.210 --> 09:41:56.220 align:start position:0% obviously if we can 09:41:56.220 --> 09:41:58.850 align:start position:0% obviously if we can simplify<09:41:56.936> how<09:41:57.540> information<09:41:57.840> can<09:41:58.380> get<09:41:58.620> read 09:41:58.850 --> 09:41:58.860 align:start position:0% simplify how information can get read 09:41:58.860 --> 09:42:01.010 align:start position:0% simplify how information can get read it's<09:41:59.580> going<09:41:59.756> to<09:41:59.756> simplify<09:42:00.180> how<09:42:00.480> routing<09:42:00.840> can 09:42:01.010 --> 09:42:01.020 align:start position:0% it's going to simplify how routing can 09:42:01.020 --> 09:42:02.086 align:start position:0% it's going to simplify how routing can occur 09:42:02.086 --> 09:42:02.096 align:start position:0% occur 09:42:02.096 --> 09:42:06.710 align:start position:0% occur now<09:42:02.756> data<09:42:03.540> in<09:42:04.140> transit<09:42:04.916> is<09:42:05.276> susceptible<09:42:05.756> to<09:42:06.480> a 09:42:06.710 --> 09:42:06.720 align:start position:0% now data in transit is susceptible to a 09:42:06.720 --> 09:42:08.210 align:start position:0% now data in transit is susceptible to a variety<09:42:06.960> of<09:42:07.080> things<09:42:07.380> that<09:42:07.620> could<09:42:07.800> cause<09:42:07.916> it<09:42:08.096> to 09:42:08.210 --> 09:42:08.220 align:start position:0% variety of things that could cause it to 09:42:08.220 --> 09:42:11.746 align:start position:0% variety of things that could cause it to be<09:42:08.340> delayed<09:42:08.880> lost<09:42:09.360> or<09:42:10.140> damaged<09:42:10.620> and<09:42:11.520> these 09:42:11.746 --> 09:42:11.756 align:start position:0% be delayed lost or damaged and these 09:42:11.756 --> 09:42:13.730 align:start position:0% be delayed lost or damaged and these things<09:42:11.880> can<09:42:12.180> occur<09:42:12.540> on<09:42:12.960> the<09:42:13.080> transmit<09:42:13.500> side 09:42:13.730 --> 09:42:13.740 align:start position:0% things can occur on the transmit side 09:42:13.740 --> 09:42:16.190 align:start position:0% things can occur on the transmit side and<09:42:14.640> quite<09:42:14.880> commonly<09:42:15.300> on<09:42:15.480> the<09:42:15.596> receiving<09:42:15.900> side 09:42:16.190 --> 09:42:16.200 align:start position:0% and quite commonly on the receiving side 09:42:16.200 --> 09:42:18.710 align:start position:0% and quite commonly on the receiving side as<09:42:16.436> well<09:42:16.680> so<09:42:17.400> the<09:42:17.580> method<09:42:17.936> the<09:42:18.180> data<09:42:18.540> is 09:42:18.710 --> 09:42:18.720 align:start position:0% as well so the method the data is 09:42:18.720 --> 09:42:20.510 align:start position:0% as well so the method the data is delivered<09:42:19.256> makes<09:42:19.560> a<09:42:19.800> huge<09:42:20.040> difference<09:42:20.220> in 09:42:20.510 --> 09:42:20.520 align:start position:0% delivered makes a huge difference in 09:42:20.520 --> 09:42:22.246 align:start position:0% delivered makes a huge difference in whether<09:42:20.756> the<09:42:20.936> data<09:42:21.180> is<09:42:21.300> going<09:42:21.480> to<09:42:21.660> arrive<09:42:22.080> at 09:42:22.246 --> 09:42:22.256 align:start position:0% whether the data is going to arrive at 09:42:22.256 --> 09:42:24.310 align:start position:0% whether the data is going to arrive at the<09:42:22.380> destination<09:42:22.800> correctively 09:42:24.310 --> 09:42:24.320 align:start position:0% the destination correctively 09:42:24.320 --> 09:42:26.390 align:start position:0% the destination correctively and<09:42:25.320> efficiently 09:42:26.390 --> 09:42:26.400 align:start position:0% and efficiently 09:42:26.400 --> 09:42:28.370 align:start position:0% and efficiently so<09:42:26.880> depending<09:42:27.300> on<09:42:27.480> the<09:42:27.660> method<09:42:27.900> of<09:42:28.020> delivery 09:42:28.370 --> 09:42:28.380 align:start position:0% so depending on the method of delivery 09:42:28.380 --> 09:42:29.990 align:start position:0% so depending on the method of delivery there<09:42:28.560> can<09:42:28.740> be<09:42:28.860> error<09:42:29.220> detection<09:42:29.520> which<09:42:29.880> would 09:42:29.990 --> 09:42:30.000 align:start position:0% there can be error detection which would 09:42:30.000 --> 09:42:32.086 align:start position:0% there can be error detection which would mean<09:42:30.180> we<09:42:30.416> detect<09:42:30.776> that<09:42:30.960> there<09:42:31.200> are<09:42:31.320> errors<09:42:31.560> and 09:42:32.086 --> 09:42:32.096 align:start position:0% mean we detect that there are errors and 09:42:32.096 --> 09:42:34.010 align:start position:0% mean we detect that there are errors and error<09:42:32.640> correction<09:42:33.000> which<09:42:33.300> means<09:42:33.540> we<09:42:33.660> not<09:42:33.900> only 09:42:34.010 --> 09:42:34.020 align:start position:0% error correction which means we not only 09:42:34.020 --> 09:42:35.990 align:start position:0% error correction which means we not only detect<09:42:34.320> but<09:42:34.560> we<09:42:34.680> fix<09:42:34.860> the<09:42:35.096> errors<09:42:35.400> when<09:42:35.756> these 09:42:35.990 --> 09:42:36.000 align:start position:0% detect but we fix the errors when these 09:42:36.000 --> 09:42:38.266 align:start position:0% detect but we fix the errors when these recovery<09:42:36.416> mechanisms<09:42:36.900> are<09:42:37.140> used<09:42:37.320> now<09:42:37.980> an 09:42:38.266 --> 09:42:38.276 align:start position:0% recovery mechanisms are used now an 09:42:38.276 --> 09:42:40.310 align:start position:0% recovery mechanisms are used now an important<09:42:38.640> aspect<09:42:39.120> of<09:42:39.416> the<09:42:39.540> data<09:42:39.900> delivery 09:42:40.310 --> 09:42:40.320 align:start position:0% important aspect of the data delivery 09:42:40.320 --> 09:42:43.190 align:start position:0% important aspect of the data delivery begins<09:42:41.040> with<09:42:41.340> the<09:42:41.700> actual<09:42:42.240> connection<09:42:42.596> itself 09:42:43.190 --> 09:42:43.200 align:start position:0% begins with the actual connection itself 09:42:43.200 --> 09:42:44.746 align:start position:0% begins with the actual connection itself so<09:42:43.740> depending<09:42:44.040> on<09:42:44.160> the<09:42:44.340> type<09:42:44.460> of<09:42:44.580> connection 09:42:44.746 --> 09:42:44.756 align:start position:0% so depending on the type of connection 09:42:44.756 --> 09:42:47.810 align:start position:0% so depending on the type of connection service<09:42:45.240> used<09:42:45.596> is<09:42:46.020> going<09:42:46.200> to<09:42:46.436> give<09:42:46.680> us<09:42:46.916> an<09:42:47.520> idea 09:42:47.810 --> 09:42:47.820 align:start position:0% service used is going to give us an idea 09:42:47.820 --> 09:42:50.086 align:start position:0% service used is going to give us an idea of<09:42:48.120> what<09:42:48.660> sort<09:42:48.840> of<09:42:48.900> delivery<09:42:49.436> options<09:42:49.860> are 09:42:50.086 --> 09:42:50.096 align:start position:0% of what sort of delivery options are 09:42:50.096 --> 09:42:51.950 align:start position:0% of what sort of delivery options are available 09:42:51.950 --> 09:42:51.960 align:start position:0% available 09:42:51.960 --> 09:42:56.266 align:start position:0% available so<09:42:53.040> a<09:42:53.460> connection<09:42:53.700> in<09:42:54.416> terms<09:42:54.720> of<09:42:54.960> networks<09:42:55.620> is 09:42:56.266 --> 09:42:56.276 align:start position:0% so a connection in terms of networks is 09:42:56.276 --> 09:42:58.190 align:start position:0% so a connection in terms of networks is The<09:42:56.640> Logical<09:42:57.000> joining<09:42:57.540> of<09:42:57.776> two<09:42:57.960> network 09:42:58.190 --> 09:42:58.200 align:start position:0% The Logical joining of two network 09:42:58.200 --> 09:43:01.550 align:start position:0% The Logical joining of two network devices<09:42:58.800> through<09:42:59.700> a<09:42:59.936> specified<09:43:00.300> medium<09:43:00.900> that 09:43:01.550 --> 09:43:01.560 align:start position:0% devices through a specified medium that 09:43:01.560 --> 09:43:03.586 align:start position:0% devices through a specified medium that is<09:43:01.680> established<09:43:02.340> and<09:43:02.640> maintained<09:43:03.180> for<09:43:03.480> a 09:43:03.586 --> 09:43:03.596 align:start position:0% is established and maintained for a 09:43:03.596 --> 09:43:05.690 align:start position:0% is established and maintained for a period<09:43:03.900> of<09:43:04.080> time<09:43:04.320> during<09:43:04.980> which<09:43:05.276> the<09:43:05.520> session 09:43:05.690 --> 09:43:05.700 align:start position:0% period of time during which the session 09:43:05.700 --> 09:43:09.110 align:start position:0% period of time during which the session exists<09:43:06.360> in<09:43:07.020> other<09:43:07.140> words<09:43:07.320> the<09:43:08.096> connection<09:43:08.340> is 09:43:09.110 --> 09:43:09.120 align:start position:0% exists in other words the connection is 09:43:09.120 --> 09:43:10.906 align:start position:0% exists in other words the connection is what<09:43:09.300> allows<09:43:09.720> data<09:43:10.140> to<09:43:10.200> be<09:43:10.320> transferred 09:43:10.906 --> 09:43:10.916 align:start position:0% what allows data to be transferred 09:43:10.916 --> 09:43:13.246 align:start position:0% what allows data to be transferred between<09:43:11.340> say<09:43:11.640> my<09:43:11.880> computer<09:43:12.120> and<09:43:12.776> a<09:43:12.960> server 09:43:13.246 --> 09:43:13.256 align:start position:0% between say my computer and a server 09:43:13.256 --> 09:43:14.150 align:start position:0% between say my computer and a server computer 09:43:14.150 --> 09:43:14.160 align:start position:0% computer 09:43:14.160 --> 09:43:17.330 align:start position:0% computer now<09:43:14.756> in<09:43:15.000> networking<09:43:15.480> and<09:43:15.720> specifically<09:43:16.500> in<09:43:16.980> IP 09:43:17.330 --> 09:43:17.340 align:start position:0% now in networking and specifically in IP 09:43:17.340 --> 09:43:19.070 align:start position:0% now in networking and specifically in IP networks<09:43:17.880> there<09:43:18.416> will<09:43:18.596> be<09:43:18.720> connection 09:43:19.070 --> 09:43:19.080 align:start position:0% networks there will be connection 09:43:19.080 --> 09:43:23.086 align:start position:0% networks there will be connection services<09:43:19.800> that<09:43:20.700> attempt<09:43:21.120> to<09:43:21.300> provide<09:43:22.096> data 09:43:23.086 --> 09:43:23.096 align:start position:0% services that attempt to provide data 09:43:23.096 --> 09:43:25.906 align:start position:0% services that attempt to provide data integrity<09:43:23.580> and<09:43:24.240> reliability<09:43:24.776> now<09:43:25.500> there<09:43:25.740> are 09:43:25.906 --> 09:43:25.916 align:start position:0% integrity and reliability now there are 09:43:25.916 --> 09:43:27.406 align:start position:0% integrity and reliability now there are generally<09:43:26.160> three<09:43:26.700> types<09:43:27.120> of<09:43:27.240> connection 09:43:27.406 --> 09:43:27.416 align:start position:0% generally three types of connection 09:43:27.416 --> 09:43:30.830 align:start position:0% generally three types of connection services<09:43:27.960> that<09:43:28.620> we<09:43:28.860> see<09:43:29.276> when<09:43:30.180> we<09:43:30.416> discuss 09:43:30.830 --> 09:43:30.840 align:start position:0% services that we see when we discuss 09:43:30.840 --> 09:43:32.746 align:start position:0% services that we see when we discuss certain<09:43:31.200> protocols<09:43:31.860> and<09:43:32.160> we've<09:43:32.340> talked<09:43:32.640> about 09:43:32.746 --> 09:43:32.756 align:start position:0% certain protocols and we've talked about 09:43:32.756 --> 09:43:35.510 align:start position:0% certain protocols and we've talked about these<09:43:33.240> in<09:43:33.776> some<09:43:34.080> way<09:43:34.256> shape<09:43:34.500> or<09:43:34.740> form<09:43:34.980> but<09:43:35.400> it 09:43:35.510 --> 09:43:35.520 align:start position:0% these in some way shape or form but it 09:43:35.520 --> 09:43:37.246 align:start position:0% these in some way shape or form but it doesn't<09:43:35.640> hurt<09:43:35.880> to<09:43:36.060> sort<09:43:36.180> of<09:43:36.300> go<09:43:36.416> over<09:43:36.596> them<09:43:36.840> in 09:43:37.246 --> 09:43:37.256 align:start position:0% doesn't hurt to sort of go over them in 09:43:37.256 --> 09:43:39.110 align:start position:0% doesn't hurt to sort of go over them in a<09:43:37.380> little<09:43:37.436> more<09:43:37.680> specific<09:43:38.040> detail 09:43:39.110 --> 09:43:39.120 align:start position:0% a little more specific detail 09:43:39.120 --> 09:43:41.870 align:start position:0% a little more specific detail first<09:43:39.660> is<09:43:39.960> an<09:43:40.200> acknowledged<09:43:40.916> connectionless 09:43:41.870 --> 09:43:41.880 align:start position:0% first is an acknowledged connectionless 09:43:41.880 --> 09:43:46.010 align:start position:0% first is an acknowledged connectionless service<09:43:42.380> in<09:43:43.380> these<09:43:43.980> the<09:43:44.640> connection<09:43:45.020> isn't 09:43:46.010 --> 09:43:46.020 align:start position:0% service in these the connection isn't 09:43:46.020 --> 09:43:47.266 align:start position:0% service in these the connection isn't created 09:43:47.266 --> 09:43:47.276 align:start position:0% created 09:43:47.276 --> 09:43:51.470 align:start position:0% created however<09:43:48.120> when<09:43:49.080> data<09:43:49.860> is<09:43:50.460> received<09:43:51.060> by<09:43:51.300> the 09:43:51.470 --> 09:43:51.480 align:start position:0% however when data is received by the 09:43:51.480 --> 09:43:54.710 align:start position:0% however when data is received by the destination<09:43:51.960> there<09:43:52.916> is<09:43:53.096> a<09:43:53.520> acknowledgment<09:43:54.300> of 09:43:54.710 --> 09:43:54.720 align:start position:0% destination there is a acknowledgment of 09:43:54.720 --> 09:43:58.550 align:start position:0% destination there is a acknowledgment of a<09:43:54.900> receipt<09:43:55.640> so<09:43:56.640> website<09:43:57.360> Communications<09:43:58.080> use 09:43:58.550 --> 09:43:58.560 align:start position:0% a receipt so website Communications use 09:43:58.560 --> 09:44:01.190 align:start position:0% a receipt so website Communications use this<09:43:58.860> type<09:43:59.040> of<09:43:59.220> service<09:43:59.460> a<09:44:00.360> great<09:44:00.480> metaphor<09:44:01.020> to 09:44:01.190 --> 09:44:01.200 align:start position:0% this type of service a great metaphor to 09:44:01.200 --> 09:44:03.830 align:start position:0% this type of service a great metaphor to think<09:44:01.320> about<09:44:01.500> this<09:44:01.860> would<09:44:02.580> be<09:44:02.700> for<09:44:03.000> instance<09:44:03.300> a 09:44:03.830 --> 09:44:03.840 align:start position:0% think about this would be for instance a 09:44:03.840 --> 09:44:06.110 align:start position:0% think about this would be for instance a delivery<09:44:04.380> receipt 09:44:06.110 --> 09:44:06.120 align:start position:0% delivery receipt 09:44:06.120 --> 09:44:10.190 align:start position:0% delivery receipt with<09:44:06.660> regular<09:44:07.140> mail 09:44:10.190 --> 09:44:10.200 align:start position:0% 09:44:10.200 --> 09:44:12.406 align:start position:0% so<09:44:10.740> it's<09:44:11.040> not<09:44:11.220> certified<09:44:11.700> we're<09:44:12.120> not<09:44:12.240> going<09:44:12.360> to 09:44:12.406 --> 09:44:12.416 align:start position:0% so it's not certified we're not going to 09:44:12.416 --> 09:44:14.510 align:start position:0% so it's not certified we're not going to get<09:44:12.540> a<09:44:12.720> signature<09:44:13.140> but<09:44:13.680> what<09:44:13.860> we<09:44:13.980> do<09:44:14.096> is<09:44:14.220> we<09:44:14.400> get 09:44:14.510 --> 09:44:14.520 align:start position:0% get a signature but what we do is we get 09:44:14.520 --> 09:44:17.266 align:start position:0% get a signature but what we do is we get a<09:44:14.700> receipt<09:44:15.060> that<09:44:15.360> it<09:44:15.480> has<09:44:15.660> been<09:44:15.840> delivered<09:44:16.680> now 09:44:17.266 --> 09:44:17.276 align:start position:0% a receipt that it has been delivered now 09:44:17.276 --> 09:44:19.246 align:start position:0% a receipt that it has been delivered now with<09:44:17.640> unacknowledged<09:44:18.540> connectionless 09:44:19.246 --> 09:44:19.256 align:start position:0% with unacknowledged connectionless 09:44:19.256 --> 09:44:21.530 align:start position:0% with unacknowledged connectionless Services<09:44:19.560> there's<09:44:20.340> no<09:44:20.700> acknowledgment<09:44:21.240> sent 09:44:21.530 --> 09:44:21.540 align:start position:0% Services there's no acknowledgment sent 09:44:21.540 --> 09:44:24.230 align:start position:0% Services there's no acknowledgment sent unless<09:44:22.380> the<09:44:22.680> application<09:44:23.160> itself<09:44:23.640> does<09:44:24.000> this 09:44:24.230 --> 09:44:24.240 align:start position:0% unless the application itself does this 09:44:24.240 --> 09:44:26.926 align:start position:0% unless the application itself does this this<09:44:24.960> could<09:44:25.200> also<09:44:25.436> be<09:44:25.620> considered<09:44:26.160> Simplex 09:44:26.926 --> 09:44:26.936 align:start position:0% this could also be considered Simplex 09:44:26.936 --> 09:44:28.790 align:start position:0% this could also be considered Simplex Communications<09:44:27.596> which<09:44:28.020> we'll<09:44:28.200> talk<09:44:28.380> about<09:44:28.560> in 09:44:28.790 --> 09:44:28.800 align:start position:0% Communications which we'll talk about in 09:44:28.800 --> 09:44:31.130 align:start position:0% Communications which we'll talk about in just<09:44:28.980> a<09:44:29.160> second<09:44:29.340> so<09:44:30.060> this<09:44:30.360> is<09:44:30.540> just<09:44:30.840> like 09:44:31.130 --> 09:44:31.140 align:start position:0% just a second so this is just like 09:44:31.140 --> 09:44:33.350 align:start position:0% just a second so this is just like regular 09:44:33.350 --> 09:44:33.360 align:start position:0% regular 09:44:33.360 --> 09:44:34.610 align:start position:0% regular mail 09:44:34.610 --> 09:44:34.620 align:start position:0% mail 09:44:34.620 --> 09:44:36.950 align:start position:0% mail we<09:44:35.040> send<09:44:35.276> it<09:44:35.400> we<09:44:35.580> drop<09:44:35.700> in<09:44:35.880> the<09:44:36.060> mail<09:44:36.180> there<09:44:36.776> is 09:44:36.950 --> 09:44:36.960 align:start position:0% we send it we drop in the mail there is 09:44:36.960 --> 09:44:40.010 align:start position:0% we send it we drop in the mail there is no<09:44:37.200> acknowledgment<09:44:37.800> okay<09:44:38.596> acknowledged<09:44:39.596> at 09:44:40.010 --> 09:44:40.020 align:start position:0% no acknowledgment okay acknowledged at 09:44:40.020 --> 09:44:41.086 align:start position:0% no acknowledgment okay acknowledged at least<09:44:40.140> has 09:44:41.086 --> 09:44:41.096 align:start position:0% least has 09:44:41.096 --> 09:44:43.130 align:start position:0% least has uh<09:44:41.640> and<09:44:41.756> acknowledge<09:44:42.240> that<09:44:42.480> data<09:44:42.840> has<09:44:42.960> been 09:44:43.130 --> 09:44:43.140 align:start position:0% uh and acknowledge that data has been 09:44:43.140 --> 09:44:45.710 align:start position:0% uh and acknowledge that data has been sent<09:44:43.320> but<09:44:43.680> there<09:44:43.860> is<09:44:44.040> no<09:44:44.460> connection<09:44:44.936> made 09:44:45.710 --> 09:44:45.720 align:start position:0% sent but there is no connection made 09:44:45.720 --> 09:44:48.290 align:start position:0% sent but there is no connection made right<09:44:46.380> there<09:44:46.860> is<09:44:46.980> no<09:44:47.276> established<09:44:48.000> session 09:44:48.290 --> 09:44:48.300 align:start position:0% right there is no established session 09:44:48.300 --> 09:44:51.290 align:start position:0% right there is no established session made<09:44:48.776> between<09:44:49.200> the<09:44:49.680> receiver<09:44:49.980> and<09:44:50.220> the<09:44:50.340> sender 09:44:51.290 --> 09:44:51.300 align:start position:0% made between the receiver and the sender 09:44:51.300 --> 09:44:53.630 align:start position:0% made between the receiver and the sender finally<09:44:51.720> we<09:44:51.900> have<09:44:52.080> connection<09:44:52.640> oriented 09:44:53.630 --> 09:44:53.640 align:start position:0% finally we have connection oriented 09:44:53.640 --> 09:44:55.490 align:start position:0% finally we have connection oriented services<09:44:53.936> and<09:44:54.660> by<09:44:54.776> the<09:44:54.900> way<09:44:54.960> when<09:44:55.140> we<09:44:55.256> talked 09:44:55.490 --> 09:44:55.500 align:start position:0% services and by the way when we talked 09:44:55.500 --> 09:44:59.210 align:start position:0% services and by the way when we talked about<09:44:55.560> these<09:44:55.980> connection<09:44:56.160> lesses<09:44:56.936> we<09:44:57.840> recall 09:44:59.210 --> 09:44:59.220 align:start position:0% about these connection lesses we recall 09:44:59.220 --> 09:45:02.406 align:start position:0% about these connection lesses we recall this<09:44:59.820> is<09:45:00.000> like<09:45:00.720> UDP<09:45:01.140> which<09:45:01.740> is<09:45:01.860> connectionless 09:45:02.406 --> 09:45:02.416 align:start position:0% this is like UDP which is connectionless 09:45:02.416 --> 09:45:04.610 align:start position:0% this is like UDP which is connectionless and<09:45:03.416> IP 09:45:04.610 --> 09:45:04.620 align:start position:0% and IP 09:45:04.620 --> 09:45:06.530 align:start position:0% and IP here<09:45:05.160> connection<09:45:05.460> oriented<09:45:06.180> we're<09:45:06.360> looking 09:45:06.530 --> 09:45:06.540 align:start position:0% here connection oriented we're looking 09:45:06.540 --> 09:45:09.650 align:start position:0% here connection oriented we're looking at<09:45:06.840> TCP 09:45:09.650 --> 09:45:09.660 align:start position:0% at TCP 09:45:09.660 --> 09:45:12.406 align:start position:0% at TCP now<09:45:10.320> these<09:45:10.800> are<09:45:10.916> where<09:45:11.160> error<09:45:11.580> detection<09:45:11.936> and 09:45:12.406 --> 09:45:12.416 align:start position:0% now these are where error detection and 09:45:12.416 --> 09:45:15.170 align:start position:0% now these are where error detection and correction<09:45:12.840> are<09:45:13.320> available<09:45:13.500> as<09:45:14.460> well<09:45:14.640> as<09:45:14.820> some 09:45:15.170 --> 09:45:15.180 align:start position:0% correction are available as well as some 09:45:15.180 --> 09:45:17.330 align:start position:0% correction are available as well as some flow<09:45:15.480> controller<09:45:15.900> packet<09:45:16.256> sequencing<09:45:16.860> in 09:45:17.330 --> 09:45:17.340 align:start position:0% flow controller packet sequencing in 09:45:17.340 --> 09:45:19.246 align:start position:0% flow controller packet sequencing in other<09:45:17.460> words<09:45:17.640> this<09:45:18.000> would<09:45:18.180> be<09:45:18.300> like<09:45:18.660> certified 09:45:19.246 --> 09:45:19.256 align:start position:0% other words this would be like certified 09:45:19.256 --> 09:45:23.086 align:start position:0% other words this would be like certified mail 09:45:23.086 --> 09:45:23.096 align:start position:0% 09:45:23.096 --> 09:45:24.530 align:start position:0% now<09:45:23.460> there<09:45:23.640> are<09:45:23.756> also<09:45:23.936> three<09:45:24.120> types<09:45:24.416> of 09:45:24.530 --> 09:45:24.540 align:start position:0% now there are also three types of 09:45:24.540 --> 09:45:25.970 align:start position:0% now there are also three types of connection<09:45:24.720> modes<09:45:25.320> that<09:45:25.560> we're<09:45:25.680> typically 09:45:25.970 --> 09:45:25.980 align:start position:0% connection modes that we're typically 09:45:25.980 --> 09:45:29.150 align:start position:0% connection modes that we're typically going<09:45:26.276> to<09:45:26.400> use<09:45:26.580> they're<09:45:27.540> Simplex<09:45:28.020> half<09:45:28.680> duplex 09:45:29.150 --> 09:45:29.160 align:start position:0% going to use they're Simplex half duplex 09:45:29.160 --> 09:45:30.650 align:start position:0% going to use they're Simplex half duplex and<09:45:29.400> full<09:45:29.580> duplex 09:45:30.650 --> 09:45:30.660 align:start position:0% and full duplex 09:45:30.660 --> 09:45:32.630 align:start position:0% and full duplex with<09:45:31.140> Simplex<09:45:31.560> this<09:45:32.040> is<09:45:32.220> one<09:45:32.460> way 09:45:32.630 --> 09:45:32.640 align:start position:0% with Simplex this is one way 09:45:32.640 --> 09:45:34.970 align:start position:0% with Simplex this is one way communication<09:45:33.300> only<09:45:33.596> this<09:45:34.500> is<09:45:34.680> sort<09:45:34.860> of 09:45:34.970 --> 09:45:34.980 align:start position:0% communication only this is sort of 09:45:34.980 --> 09:45:38.510 align:start position:0% communication only this is sort of similar<09:45:35.400> to<09:45:36.240> FM<09:45:37.140> radio<09:45:37.380> broadcast 09:45:38.510 --> 09:45:38.520 align:start position:0% similar to FM radio broadcast 09:45:38.520 --> 09:45:41.030 align:start position:0% similar to FM radio broadcast right<09:45:39.120> you<09:45:39.416> turn<09:45:39.596> on<09:45:39.720> your<09:45:39.900> radio<09:45:40.080> you<09:45:40.620> tune<09:45:40.800> in 09:45:41.030 --> 09:45:41.040 align:start position:0% right you turn on your radio you tune in 09:45:41.040 --> 09:45:44.150 align:start position:0% right you turn on your radio you tune in and<09:45:41.700> you<09:45:41.880> can<09:45:42.060> receive<09:45:42.840> but<09:45:43.140> you<09:45:43.380> cannot<09:45:43.680> send 09:45:44.150 --> 09:45:44.160 align:start position:0% and you can receive but you cannot send 09:45:44.160 --> 09:45:46.790 align:start position:0% and you can receive but you cannot send data 09:45:46.790 --> 09:45:46.800 align:start position:0% data 09:45:46.800 --> 09:45:49.490 align:start position:0% data now<09:45:47.160> we<09:45:47.340> also<09:45:47.580> have<09:45:47.700> half<09:45:47.936> duplex<09:45:48.480> this<09:45:49.380> is 09:45:49.490 --> 09:45:49.500 align:start position:0% now we also have half duplex this is 09:45:49.500 --> 09:45:52.310 align:start position:0% now we also have half duplex this is two-way<09:45:50.096> communication<09:45:50.756> but<09:45:51.480> only<09:45:51.660> one<09:45:51.960> at<09:45:52.140> a 09:45:52.310 --> 09:45:52.320 align:start position:0% two-way communication but only one at a 09:45:52.320 --> 09:45:54.350 align:start position:0% two-way communication but only one at a time<09:45:52.436> this<09:45:53.220> is<09:45:53.340> like<09:45:53.520> a<09:45:53.700> pair<09:45:53.820> of<09:45:53.936> regular 09:45:54.350 --> 09:45:54.360 align:start position:0% time this is like a pair of regular 09:45:54.360 --> 09:45:57.170 align:start position:0% time this is like a pair of regular walkie-talkies<09:45:55.200> only<09:45:55.680> one<09:45:56.040> device<09:45:56.276> can 09:45:57.170 --> 09:45:57.180 align:start position:0% walkie-talkies only one device can 09:45:57.180 --> 09:46:00.766 align:start position:0% walkie-talkies only one device can transmit<09:45:57.776> at<09:45:58.620> any<09:45:58.860> one<09:45:59.460> time<09:45:59.700> which<09:46:00.180> is<09:46:00.360> why<09:46:00.540> we 09:46:00.766 --> 09:46:00.776 align:start position:0% transmit at any one time which is why we 09:46:00.776 --> 09:46:03.110 align:start position:0% transmit at any one time which is why we have<09:46:00.900> to<09:46:01.080> use<09:46:01.256> those<09:46:01.560> code<09:46:01.980> words<09:46:02.220> right<09:46:02.580> over 09:46:03.110 --> 09:46:03.120 align:start position:0% have to use those code words right over 09:46:03.120 --> 09:46:05.510 align:start position:0% have to use those code words right over over<09:46:03.660> over<09:46:03.720> and<09:46:04.380> out<09:46:04.620> so<09:46:05.040> this<09:46:05.160> is<09:46:05.276> like<09:46:05.340> a 09:46:05.510 --> 09:46:05.520 align:start position:0% over over and out so this is like a 09:46:05.520 --> 09:46:07.426 align:start position:0% over over and out so this is like a walkie-talkie<09:46:06.240> finally<09:46:06.960> we<09:46:07.140> have<09:46:07.256> full 09:46:07.426 --> 09:46:07.436 align:start position:0% walkie-talkie finally we have full 09:46:07.436 --> 09:46:10.130 align:start position:0% walkie-talkie finally we have full duplex<09:46:07.916> which<09:46:08.220> is<09:46:08.400> two-way<09:46:08.936> and<09:46:09.540> both<09:46:09.776> ways 09:46:10.130 --> 09:46:10.140 align:start position:0% duplex which is two-way and both ways 09:46:10.140 --> 09:46:13.550 align:start position:0% duplex which is two-way and both ways simultaneously<09:46:10.980> this<09:46:11.936> is<09:46:12.240> similar<09:46:12.660> to<09:46:13.320> the 09:46:13.550 --> 09:46:13.560 align:start position:0% simultaneously this is similar to the 09:46:13.560 --> 09:46:16.246 align:start position:0% simultaneously this is similar to the telephone<09:46:13.756> in<09:46:14.756> which<09:46:14.936> we<09:46:15.240> can<09:46:15.416> talk<09:46:15.720> and 09:46:16.246 --> 09:46:16.256 align:start position:0% telephone in which we can talk and 09:46:16.256 --> 09:46:19.130 align:start position:0% telephone in which we can talk and listen<09:46:16.380> at<09:46:16.680> the<09:46:16.800> same<09:46:16.980> time<09:46:17.220> in<09:46:18.060> some<09:46:18.180> ways<09:46:18.540> we 09:46:19.130 --> 09:46:19.140 align:start position:0% listen at the same time in some ways we 09:46:19.140 --> 09:46:20.810 align:start position:0% listen at the same time in some ways we have<09:46:19.436> trouble<09:46:19.620> understanding<09:46:20.340> each<09:46:20.460> other<09:46:20.580> as 09:46:20.810 --> 09:46:20.820 align:start position:0% have trouble understanding each other as 09:46:20.820 --> 09:46:23.266 align:start position:0% have trouble understanding each other as a<09:46:20.936> result<09:46:21.060> of<09:46:21.300> it<09:46:21.480> now<09:46:22.080> in<09:46:22.320> networking<09:46:22.860> devices 09:46:23.266 --> 09:46:23.276 align:start position:0% a result of it now in networking devices 09:46:23.276 --> 09:46:26.390 align:start position:0% a result of it now in networking devices are<09:46:23.640> designed<09:46:24.180> to<09:46:24.900> receive<09:46:25.500> and<09:46:25.916> transmit 09:46:26.390 --> 09:46:26.400 align:start position:0% are designed to receive and transmit 09:46:26.400 --> 09:46:28.906 align:start position:0% are designed to receive and transmit data<09:46:26.820> at<09:46:27.120> different<09:46:27.300> speeds<09:46:28.020> and<09:46:28.680> with 09:46:28.906 --> 09:46:28.916 align:start position:0% data at different speeds and with 09:46:28.916 --> 09:46:31.490 align:start position:0% data at different speeds and with different<09:46:29.096> sizes<09:46:29.640> of<09:46:29.880> packets<09:46:30.300> as<09:46:30.596> well<09:46:30.776> so 09:46:31.490 --> 09:46:31.500 align:start position:0% different sizes of packets as well so 09:46:31.500 --> 09:46:33.170 align:start position:0% different sizes of packets as well so certain<09:46:31.740> devices<09:46:32.096> are<09:46:32.460> not<09:46:32.640> going<09:46:32.820> to<09:46:32.936> be<09:46:33.060> able 09:46:33.170 --> 09:46:33.180 align:start position:0% certain devices are not going to be able 09:46:33.180 --> 09:46:35.746 align:start position:0% certain devices are not going to be able to<09:46:33.300> handle<09:46:33.596> as<09:46:33.776> much<09:46:33.960> data<09:46:34.380> as<09:46:34.560> others<09:46:35.040> at<09:46:35.520> one 09:46:35.746 --> 09:46:35.756 align:start position:0% to handle as much data as others at one 09:46:35.756 --> 09:46:37.190 align:start position:0% to handle as much data as others at one point<09:46:35.880> or<09:46:36.060> another<09:46:36.180> we<09:46:36.596> talked<09:46:36.900> about<09:46:36.960> this 09:46:37.190 --> 09:46:37.200 align:start position:0% point or another we talked about this 09:46:37.200 --> 09:46:40.426 align:start position:0% point or another we talked about this briefly<09:46:37.560> with<09:46:37.800> mtus<09:46:38.340> and<09:46:38.580> MTU<09:46:38.936> black<09:46:39.180> holes<09:46:39.596> so 09:46:40.426 --> 09:46:40.436 align:start position:0% briefly with mtus and MTU black holes so 09:46:40.436 --> 09:46:43.906 align:start position:0% briefly with mtus and MTU black holes so flow<09:46:40.916> control<09:46:41.220> is<09:46:42.060> the<09:46:42.240> managing<09:46:42.776> of<09:46:43.256> amounts 09:46:43.906 --> 09:46:43.916 align:start position:0% flow control is the managing of amounts 09:46:43.916 --> 09:46:46.070 align:start position:0% flow control is the managing of amounts of<09:46:44.040> data<09:46:44.400> and<09:46:44.880> the<09:46:45.060> rate<09:46:45.180> at<09:46:45.416> which<09:46:45.596> the<09:46:45.840> data 09:46:46.070 --> 09:46:46.080 align:start position:0% of data and the rate at which the data 09:46:46.080 --> 09:46:47.870 align:start position:0% of data and the rate at which the data is<09:46:46.200> being<09:46:46.320> transmitted<09:46:46.680> emitted<09:46:47.340> over<09:46:47.640> a 09:46:47.870 --> 09:46:47.880 align:start position:0% is being transmitted emitted over a 09:46:47.880 --> 09:46:49.070 align:start position:0% is being transmitted emitted over a network<09:46:48.000> connection 09:46:49.070 --> 09:46:49.080 align:start position:0% network connection 09:46:49.080 --> 09:46:51.830 align:start position:0% network connection flow<09:46:49.740> control<09:46:49.916> is<09:46:50.700> necessary<09:46:51.360> to<09:46:51.720> help 09:46:51.830 --> 09:46:51.840 align:start position:0% flow control is necessary to help 09:46:51.840 --> 09:46:54.950 align:start position:0% flow control is necessary to help prevent<09:46:52.200> devices<09:46:52.680> from<09:46:53.460> being<09:46:53.960> overflowed 09:46:54.950 --> 09:46:54.960 align:start position:0% prevent devices from being overflowed 09:46:54.960 --> 09:46:57.586 align:start position:0% prevent devices from being overflowed with<09:46:55.256> data<09:46:55.680> some<09:46:56.460> devices<09:46:56.820> when<09:46:57.240> there's<09:46:57.416> too 09:46:57.586 --> 09:46:57.596 align:start position:0% with data some devices when there's too 09:46:57.596 --> 09:46:59.086 align:start position:0% with data some devices when there's too much<09:46:57.720> data<09:46:58.080> is<09:46:58.200> received<09:46:58.620> are<09:46:58.860> going<09:46:58.980> to 09:46:59.086 --> 09:46:59.096 align:start position:0% much data is received are going to 09:46:59.096 --> 09:47:01.490 align:start position:0% much data is received are going to potentially<09:46:59.460> shut<09:46:59.820> down<09:47:00.180> to<09:47:00.840> prevent<09:47:01.140> certain 09:47:01.490 --> 09:47:01.500 align:start position:0% potentially shut down to prevent certain 09:47:01.500 --> 09:47:03.586 align:start position:0% potentially shut down to prevent certain attacks<09:47:02.160> or<09:47:02.700> simply<09:47:03.000> are<09:47:03.180> going<09:47:03.300> to<09:47:03.416> drop 09:47:03.586 --> 09:47:03.596 align:start position:0% attacks or simply are going to drop 09:47:03.596 --> 09:47:05.510 align:start position:0% attacks or simply are going to drop packets<09:47:04.140> that<09:47:04.436> are<09:47:04.560> too<09:47:04.800> large<09:47:05.040> because 09:47:05.510 --> 09:47:05.520 align:start position:0% packets that are too large because 09:47:05.520 --> 09:47:07.730 align:start position:0% packets that are too large because they're<09:47:05.756> going<09:47:05.936> to<09:47:06.060> cause<09:47:06.180> delays<09:47:06.840> on<09:47:07.560> the 09:47:07.730 --> 09:47:07.740 align:start position:0% they're going to cause delays on the 09:47:07.740 --> 09:47:09.350 align:start position:0% they're going to cause delays on the other<09:47:07.800> side<09:47:08.040> of<09:47:08.220> the<09:47:08.276> scale<09:47:08.520> if<09:47:09.000> too<09:47:09.120> little 09:47:09.350 --> 09:47:09.360 align:start position:0% other side of the scale if too little 09:47:09.360 --> 09:47:11.690 align:start position:0% other side of the scale if too little data<09:47:09.776> is<09:47:09.900> being<09:47:10.080> received<09:47:10.500> by<09:47:10.620> the<09:47:10.800> device<09:47:10.980> it 09:47:11.690 --> 09:47:11.700 align:start position:0% data is being received by the device it 09:47:11.700 --> 09:47:13.906 align:start position:0% data is being received by the device it may<09:47:11.820> just<09:47:12.000> be<09:47:12.120> sitting<09:47:12.540> idly<09:47:12.960> by<09:47:13.256> waiting<09:47:13.800> for 09:47:13.906 --> 09:47:13.916 align:start position:0% may just be sitting idly by waiting for 09:47:13.916 --> 09:47:16.610 align:start position:0% may just be sitting idly by waiting for the<09:47:14.096> remaining<09:47:14.460> packets<09:47:15.300> in<09:47:15.900> this<09:47:16.020> case<09:47:16.200> it's 09:47:16.610 --> 09:47:16.620 align:start position:0% the remaining packets in this case it's 09:47:16.620 --> 09:47:19.070 align:start position:0% the remaining packets in this case it's simply<09:47:16.916> a<09:47:17.040> matter<09:47:17.220> of<09:47:17.400> efficiency<09:47:17.936> so<09:47:18.900> there 09:47:19.070 --> 09:47:19.080 align:start position:0% simply a matter of efficiency so there 09:47:19.080 --> 09:47:20.690 align:start position:0% simply a matter of efficiency so there are<09:47:19.200> two<09:47:19.320> main<09:47:19.500> types<09:47:19.860> of<09:47:19.980> flow<09:47:20.220> control<09:47:20.400> that 09:47:20.690 --> 09:47:20.700 align:start position:0% are two main types of flow control that 09:47:20.700 --> 09:47:23.266 align:start position:0% are two main types of flow control that are<09:47:20.880> covered<09:47:21.120> on<09:47:21.240> the<09:47:21.416> exam<09:47:21.860> buffering<09:47:22.860> and 09:47:23.266 --> 09:47:23.276 align:start position:0% are covered on the exam buffering and 09:47:23.276 --> 09:47:24.650 align:start position:0% are covered on the exam buffering and data<09:47:23.700> windows 09:47:24.650 --> 09:47:24.660 align:start position:0% data windows 09:47:24.660 --> 09:47:27.586 align:start position:0% data windows buffering<09:47:25.620> is<09:47:26.220> a<09:47:26.520> flow<09:47:26.820> control<09:47:27.000> technique 09:47:27.586 --> 09:47:27.596 align:start position:0% buffering is a flow control technique 09:47:27.596 --> 09:47:29.810 align:start position:0% buffering is a flow control technique where<09:47:27.900> a<09:47:28.256> portion<09:47:28.560> of<09:47:28.680> the<09:47:28.860> memory<09:47:29.160> either 09:47:29.810 --> 09:47:29.820 align:start position:0% where a portion of the memory either 09:47:29.820 --> 09:47:33.050 align:start position:0% where a portion of the memory either physical<09:47:30.180> or<09:47:30.840> logical<09:47:31.200> via<09:47:31.620> software<09:47:32.040> is<09:47:32.756> used 09:47:33.050 --> 09:47:33.060 align:start position:0% physical or logical via software is used 09:47:33.060 --> 09:47:35.570 align:start position:0% physical or logical via software is used to<09:47:33.416> temporarily<09:47:33.900> store<09:47:34.380> data<09:47:34.916> as<09:47:35.160> it's<09:47:35.340> being 09:47:35.570 --> 09:47:35.580 align:start position:0% to temporarily store data as it's being 09:47:35.580 --> 09:47:39.290 align:start position:0% to temporarily store data as it's being received<09:47:36.180> in<09:47:36.900> order<09:47:37.020> to<09:47:37.500> regulate<09:47:38.400> the<09:47:39.060> amount 09:47:39.290 --> 09:47:39.300 align:start position:0% received in order to regulate the amount 09:47:39.300 --> 09:47:41.870 align:start position:0% received in order to regulate the amount of<09:47:39.416> data<09:47:39.720> that's<09:47:39.900> being<09:47:40.140> processed<09:47:41.160> buffering 09:47:41.870 --> 09:47:41.880 align:start position:0% of data that's being processed buffering 09:47:41.880 --> 09:47:44.030 align:start position:0% of data that's being processed buffering may<09:47:42.000> be<09:47:42.120> used<09:47:42.300> to<09:47:42.540> maintain<09:47:42.960> data<09:47:43.500> consistency 09:47:44.030 --> 09:47:44.040 align:start position:0% may be used to maintain data consistency 09:47:44.040 --> 09:47:47.630 align:start position:0% may be used to maintain data consistency as<09:47:44.580> well<09:47:44.756> as<09:47:45.180> minimize<09:47:45.900> overloading<09:47:46.800> now<09:47:47.340> Ram 09:47:47.630 --> 09:47:47.640 align:start position:0% as well as minimize overloading now Ram 09:47:47.640 --> 09:47:50.390 align:start position:0% as well as minimize overloading now Ram uses<09:47:48.120> a<09:47:48.240> type<09:47:48.416> of<09:47:48.596> buffer<09:47:49.256> when<09:47:49.740> data<09:47:50.096> is<09:47:50.160> being 09:47:50.390 --> 09:47:50.400 align:start position:0% uses a type of buffer when data is being 09:47:50.400 --> 09:47:53.150 align:start position:0% uses a type of buffer when data is being read<09:47:50.640> from<09:47:51.000> its<09:47:51.360> cache<09:47:51.776> right<09:47:52.256> so<09:47:52.620> remember<09:47:52.800> we 09:47:53.150 --> 09:47:53.160 align:start position:0% read from its cache right so remember we 09:47:53.160 --> 09:47:55.426 align:start position:0% read from its cache right so remember we talked<09:47:53.400> about<09:47:53.520> RAM<09:47:53.880> and<09:47:54.540> that<09:47:54.720> was<09:47:54.840> what<09:47:55.256> we 09:47:55.426 --> 09:47:55.436 align:start position:0% talked about RAM and that was what we 09:47:55.436 --> 09:47:56.870 align:start position:0% talked about RAM and that was what we called<09:47:55.620> Cash 09:47:56.870 --> 09:47:56.880 align:start position:0% called Cash 09:47:56.880 --> 09:47:59.330 align:start position:0% called Cash now<09:47:57.360> with<09:47:57.596> buff<09:47:57.776> bring<09:47:58.080> there<09:47:58.620> is<09:47:58.800> a<09:47:59.040> potential 09:47:59.330 --> 09:47:59.340 align:start position:0% now with buff bring there is a potential 09:47:59.340 --> 09:48:01.070 align:start position:0% now with buff bring there is a potential concern<09:47:59.756> because<09:48:00.060> what<09:48:00.416> if<09:48:00.596> the<09:48:00.720> buffer 09:48:01.070 --> 09:48:01.080 align:start position:0% concern because what if the buffer 09:48:01.080 --> 09:48:03.290 align:start position:0% concern because what if the buffer becomes<09:48:01.500> full<09:48:01.680> well<09:48:02.340> when<09:48:02.580> receiving<09:48:02.880> nodes 09:48:03.290 --> 09:48:03.300 align:start position:0% becomes full well when receiving nodes 09:48:03.300 --> 09:48:05.810 align:start position:0% becomes full well when receiving nodes buffer<09:48:03.720> reaches<09:48:04.080> a<09:48:04.200> certain<09:48:04.320> capacity<09:48:04.980> it 09:48:05.810 --> 09:48:05.820 align:start position:0% buffer reaches a certain capacity it 09:48:05.820 --> 09:48:09.530 align:start position:0% buffer reaches a certain capacity it actually<09:48:06.320> transmits<09:48:07.320> a<09:48:07.860> squelch<09:48:08.400> signal<09:48:09.000> I'm 09:48:09.530 --> 09:48:09.540 align:start position:0% actually transmits a squelch signal I'm 09:48:09.540 --> 09:48:10.670 align:start position:0% actually transmits a squelch signal I'm going<09:48:09.720> to<09:48:09.776> write<09:48:09.900> that<09:48:10.020> out<09:48:10.200> just<09:48:10.436> not<09:48:10.560> only 09:48:10.670 --> 09:48:10.680 align:start position:0% going to write that out just not only 09:48:10.680 --> 09:48:13.310 align:start position:0% going to write that out just not only because<09:48:10.860> it's<09:48:11.040> a<09:48:11.220> great<09:48:11.400> word 09:48:13.310 --> 09:48:13.320 align:start position:0% because it's a great word 09:48:13.320 --> 09:48:16.790 align:start position:0% because it's a great word that<09:48:13.860> says<09:48:14.480> stops<09:48:15.480> transmission<09:48:15.776> or<09:48:16.560> slow 09:48:16.790 --> 09:48:16.800 align:start position:0% that says stops transmission or slow 09:48:16.800 --> 09:48:20.030 align:start position:0% that says stops transmission or slow down<09:48:17.096> your<09:48:17.520> transmission<09:48:17.820> so<09:48:18.596> I<09:48:18.840> can<09:48:18.960> catch<09:48:19.380> up 09:48:20.030 --> 09:48:20.040 align:start position:0% down your transmission so I can catch up 09:48:20.040 --> 09:48:21.406 align:start position:0% down your transmission so I can catch up now<09:48:20.400> a<09:48:20.580> commonplace<09:48:20.936> we're<09:48:21.120> going<09:48:21.240> to<09:48:21.300> see 09:48:21.406 --> 09:48:21.416 align:start position:0% now a commonplace we're going to see 09:48:21.416 --> 09:48:23.390 align:start position:0% now a commonplace we're going to see this<09:48:21.596> type<09:48:21.720> of<09:48:21.840> flow<09:48:22.080> controls<09:48:22.560> when<09:48:22.800> we're 09:48:23.390 --> 09:48:23.400 align:start position:0% this type of flow controls when we're 09:48:23.400 --> 09:48:25.370 align:start position:0% this type of flow controls when we're streaming<09:48:24.000> movies<09:48:24.416> you<09:48:24.900> might<09:48:25.020> have<09:48:25.200> seen 09:48:25.370 --> 09:48:25.380 align:start position:0% streaming movies you might have seen 09:48:25.380 --> 09:48:27.950 align:start position:0% streaming movies you might have seen buffering<09:48:26.040> when<09:48:26.700> you're<09:48:26.880> using<09:48:27.240> movies<09:48:27.480> for 09:48:27.950 --> 09:48:27.960 align:start position:0% buffering when you're using movies for 09:48:27.960 --> 09:48:29.990 align:start position:0% buffering when you're using movies for instance<09:48:28.200> on<09:48:28.980> YouTube 09:48:29.990 --> 09:48:30.000 align:start position:0% instance on YouTube 09:48:30.000 --> 09:48:33.766 align:start position:0% instance on YouTube or<09:48:30.596> on<09:48:30.960> Netflix<09:48:31.160> or<09:48:32.160> any<09:48:32.340> of<09:48:32.460> these<09:48:32.700> sites<09:48:33.060> the 09:48:33.766 --> 09:48:33.776 align:start position:0% or on Netflix or any of these sites the 09:48:33.776 --> 09:48:35.810 align:start position:0% or on Netflix or any of these sites the idea<09:48:34.080> is<09:48:34.320> if<09:48:34.800> there's<09:48:34.980> a<09:48:35.220> problem<09:48:35.340> with<09:48:35.640> our 09:48:35.810 --> 09:48:35.820 align:start position:0% idea is if there's a problem with our 09:48:35.820 --> 09:48:37.070 align:start position:0% idea is if there's a problem with our communication 09:48:37.070 --> 09:48:37.080 align:start position:0% communication 09:48:37.080 --> 09:48:39.470 align:start position:0% communication we<09:48:37.560> have<09:48:37.680> a<09:48:37.916> little<09:48:37.980> buffer<09:48:38.460> of<09:48:38.640> data<09:48:39.000> so<09:48:39.360> that 09:48:39.470 --> 09:48:39.480 align:start position:0% we have a little buffer of data so that 09:48:39.480 --> 09:48:41.870 align:start position:0% we have a little buffer of data so that way<09:48:39.660> we're<09:48:39.900> not<09:48:40.080> going<09:48:40.256> to<09:48:40.436> see<09:48:40.680> a<09:48:41.400> dip<09:48:41.580> in 09:48:41.870 --> 09:48:41.880 align:start position:0% way we're not going to see a dip in 09:48:41.880 --> 09:48:43.426 align:start position:0% way we're not going to see a dip in quality<09:48:42.240> of<09:48:42.416> the<09:48:42.540> film 09:48:43.426 --> 09:48:43.436 align:start position:0% quality of the film 09:48:43.436 --> 09:48:45.350 align:start position:0% quality of the film now<09:48:43.916> another<09:48:44.220> type<09:48:44.460> of<09:48:44.640> flow<09:48:44.880> control<09:48:45.060> is 09:48:45.350 --> 09:48:45.360 align:start position:0% now another type of flow control is 09:48:45.360 --> 09:48:48.230 align:start position:0% now another type of flow control is called<09:48:45.660> Data<09:48:46.436> windows<09:48:47.340> the<09:48:47.756> data<09:48:48.120> window 09:48:48.230 --> 09:48:48.240 align:start position:0% called Data windows the data window 09:48:48.240 --> 09:48:50.450 align:start position:0% called Data windows the data window refers<09:48:49.080> to<09:48:49.200> the<09:48:49.320> amount<09:48:49.500> of<09:48:49.620> data<09:48:49.916> being<09:48:50.096> sent 09:48:50.450 --> 09:48:50.460 align:start position:0% refers to the amount of data being sent 09:48:50.460 --> 09:48:53.570 align:start position:0% refers to the amount of data being sent and<09:48:51.120> it<09:48:51.180> can<09:48:51.300> either<09:48:51.416> be<09:48:51.596> a<09:48:51.776> fixed<09:48:52.080> amount<09:48:52.740> or 09:48:53.570 --> 09:48:53.580 align:start position:0% and it can either be a fixed amount or 09:48:53.580 --> 09:48:56.150 align:start position:0% and it can either be a fixed amount or it<09:48:54.120> can<09:48:54.300> vary<09:48:54.540> and<09:48:55.140> these<09:48:55.380> are<09:48:55.500> fixed<09:48:55.860> length 09:48:56.150 --> 09:48:56.160 align:start position:0% it can vary and these are fixed length 09:48:56.160 --> 09:48:58.370 align:start position:0% it can vary and these are fixed length windows<09:48:56.460> or<09:48:56.700> sliding<09:48:57.180> very<09:48:57.360> sliding<09:48:58.080> Windows 09:48:58.370 --> 09:48:58.380 align:start position:0% windows or sliding very sliding Windows 09:48:58.380 --> 09:49:02.150 align:start position:0% windows or sliding very sliding Windows rather<09:48:58.620> if<09:48:58.916> you<09:48:59.096> think<09:48:59.220> about<09:48:59.340> the<09:48:59.640> window 09:49:02.150 --> 09:49:02.160 align:start position:0% 09:49:02.160 --> 09:49:04.610 align:start position:0% and<09:49:02.640> I<09:49:02.756> put<09:49:02.880> the<09:49:03.060> data<09:49:03.416> inside<09:49:03.660> of<09:49:03.960> it 09:49:04.610 --> 09:49:04.620 align:start position:0% and I put the data inside of it 09:49:04.620 --> 09:49:06.530 align:start position:0% and I put the data inside of it we<09:49:05.096> can<09:49:05.160> either<09:49:05.276> have<09:49:05.580> a<09:49:05.756> window<09:49:05.880> that<09:49:06.240> is<09:49:06.360> a 09:49:06.530 --> 09:49:06.540 align:start position:0% we can either have a window that is a 09:49:06.540 --> 09:49:08.570 align:start position:0% we can either have a window that is a specific<09:49:06.776> length<09:49:07.200> like<09:49:07.680> this 09:49:08.570 --> 09:49:08.580 align:start position:0% specific length like this 09:49:08.580 --> 09:49:10.850 align:start position:0% specific length like this or 09:49:10.850 --> 09:49:10.860 align:start position:0% or 09:49:10.860 --> 09:49:14.330 align:start position:0% or a<09:49:11.340> window<09:49:11.580> that<09:49:12.300> can't<09:49:12.480> possibly 09:49:14.330 --> 09:49:14.340 align:start position:0% a window that can't possibly 09:49:14.340 --> 09:49:18.230 align:start position:0% a window that can't possibly get<09:49:14.820> smaller<09:49:15.360> based<09:49:16.200> on<09:49:16.256> the<09:49:16.380> data 09:49:18.230 --> 09:49:18.240 align:start position:0% get smaller based on the data 09:49:18.240 --> 09:49:19.970 align:start position:0% get smaller based on the data and<09:49:18.596> that's<09:49:18.720> what<09:49:18.900> fixed<09:49:19.256> length<09:49:19.560> and<09:49:19.620> sliding 09:49:19.970 --> 09:49:19.980 align:start position:0% and that's what fixed length and sliding 09:49:19.980 --> 09:49:21.890 align:start position:0% and that's what fixed length and sliding windows<09:49:20.220> are<09:49:20.400> so<09:49:21.180> to<09:49:21.300> go<09:49:21.416> a<09:49:21.540> little<09:49:21.596> more<09:49:21.776> in 09:49:21.890 --> 09:49:21.900 align:start position:0% windows are so to go a little more in 09:49:21.900 --> 09:49:24.586 align:start position:0% windows are so to go a little more in depth<09:49:22.140> into<09:49:22.256> these<09:49:22.640> with<09:49:23.640> fixed<09:49:24.300> length 09:49:24.586 --> 09:49:24.596 align:start position:0% depth into these with fixed length 09:49:24.596 --> 09:49:26.690 align:start position:0% depth into these with fixed length Windows<09:49:25.080> the<09:49:25.560> size<09:49:25.740> of<09:49:25.980> the<09:49:26.096> packet<09:49:26.400> of<09:49:26.580> the 09:49:26.690 --> 09:49:26.700 align:start position:0% Windows the size of the packet of the 09:49:26.700 --> 09:49:30.350 align:start position:0% Windows the size of the packet of the data<09:49:27.000> being<09:49:27.180> sent<09:49:27.540> is<09:49:28.256> determined<09:49:28.916> by 09:49:30.350 --> 09:49:30.360 align:start position:0% data being sent is determined by 09:49:30.360 --> 09:49:33.426 align:start position:0% data being sent is determined by the<09:49:30.900> sender<09:49:31.320> and<09:49:32.096> the<09:49:32.340> rate<09:49:32.520> of<09:49:32.820> transmission 09:49:33.426 --> 09:49:33.436 align:start position:0% the sender and the rate of transmission 09:49:33.436 --> 09:49:36.470 align:start position:0% the sender and the rate of transmission is<09:49:34.436> determined<09:49:34.800> by<09:49:34.916> the<09:49:35.040> receiver<09:49:35.340> so<09:49:36.300> the 09:49:36.470 --> 09:49:36.480 align:start position:0% is determined by the receiver so the 09:49:36.480 --> 09:49:38.086 align:start position:0% is determined by the receiver so the size<09:49:36.660> is<09:49:37.020> typically<09:49:37.256> going<09:49:37.500> to<09:49:37.620> be<09:49:37.680> pretty 09:49:38.086 --> 09:49:38.096 align:start position:0% size is typically going to be pretty 09:49:38.096 --> 09:49:40.190 align:start position:0% size is typically going to be pretty small<09:49:38.400> and<09:49:39.180> overall<09:49:39.480> this<09:49:39.720> is<09:49:39.840> going<09:49:39.960> to<09:49:40.080> be 09:49:40.190 --> 09:49:40.200 align:start position:0% small and overall this is going to be 09:49:40.200 --> 09:49:42.890 align:start position:0% small and overall this is going to be fairly<09:49:40.860> efficient<09:49:41.820> the<09:49:42.480> other<09:49:42.596> thing<09:49:42.776> to 09:49:42.890 --> 09:49:42.900 align:start position:0% fairly efficient the other thing to 09:49:42.900 --> 09:49:44.266 align:start position:0% fairly efficient the other thing to remember<09:49:42.960> is<09:49:43.256> that<09:49:43.436> the<09:49:43.560> packet<09:49:43.860> size<09:49:44.040> is 09:49:44.266 --> 09:49:44.276 align:start position:0% remember is that the packet size is 09:49:44.276 --> 09:49:46.190 align:start position:0% remember is that the packet size is always<09:49:44.520> going<09:49:44.820> to<09:49:45.060> remain<09:49:45.416> the<09:49:45.776> same<09:49:45.900> it's 09:49:46.190 --> 09:49:46.200 align:start position:0% always going to remain the same it's 09:49:46.200 --> 09:49:48.650 align:start position:0% always going to remain the same it's never<09:49:46.380> going<09:49:46.560> to<09:49:46.740> change<09:49:46.916> so<09:49:47.820> if<09:49:48.240> I<09:49:48.416> need<09:49:48.540> to 09:49:48.650 --> 09:49:48.660 align:start position:0% never going to change so if I need to 09:49:48.660 --> 09:49:49.670 align:start position:0% never going to change so if I need to send 09:49:49.670 --> 09:49:49.680 align:start position:0% send 09:49:49.680 --> 09:49:51.650 align:start position:0% send 10<09:49:50.220> packets<09:49:50.700> they're<09:49:51.000> all<09:49:51.240> going<09:49:51.360> to<09:49:51.540> be 09:49:51.650 --> 09:49:51.660 align:start position:0% 10 packets they're all going to be 09:49:51.660 --> 09:49:55.130 align:start position:0% 10 packets they're all going to be exactly<09:49:52.380> the<09:49:52.680> same<09:49:52.916> size<09:49:53.360> or<09:49:54.360> as<09:49:54.540> much<09:49:54.776> as<09:49:54.900> I 09:49:55.130 --> 09:49:55.140 align:start position:0% exactly the same size or as much as I 09:49:55.140 --> 09:49:57.530 align:start position:0% exactly the same size or as much as I can<09:49:55.256> draw<09:49:55.436> them<09:49:55.740> as<09:49:55.916> such 09:49:57.530 --> 09:49:57.540 align:start position:0% can draw them as such 09:49:57.540 --> 09:50:00.110 align:start position:0% can draw them as such and<09:49:58.020> so<09:49:58.140> on<09:49:58.256> and<09:49:58.436> so<09:49:58.620> forth<09:49:59.276> now<09:49:59.700> with<09:49:59.880> a 09:50:00.110 --> 09:50:00.120 align:start position:0% and so on and so forth now with a 09:50:00.120 --> 09:50:02.266 align:start position:0% and so on and so forth now with a sliding<09:50:00.540> window<09:50:00.840> method<09:50:01.436> it's<09:50:01.980> a<09:50:02.160> bit 09:50:02.266 --> 09:50:02.276 align:start position:0% sliding window method it's a bit 09:50:02.276 --> 09:50:04.426 align:start position:0% sliding window method it's a bit different<09:50:02.460> the<09:50:03.180> sender<09:50:03.540> begins<09:50:03.900> to<09:50:04.020> transmit 09:50:04.426 --> 09:50:04.436 align:start position:0% different the sender begins to transmit 09:50:04.436 --> 09:50:06.230 align:start position:0% different the sender begins to transmit data<09:50:04.860> typically<09:50:05.160> with<09:50:05.400> a<09:50:05.640> small<09:50:05.820> number<09:50:06.060> of 09:50:06.230 --> 09:50:06.240 align:start position:0% data typically with a small number of 09:50:06.240 --> 09:50:09.530 align:start position:0% data typically with a small number of packets<09:50:06.720> and<09:50:07.500> with<09:50:07.740> each<09:50:08.040> transmission 09:50:09.530 --> 09:50:09.540 align:start position:0% packets and with each transmission 09:50:09.540 --> 09:50:14.030 align:start position:0% packets and with each transmission it<09:50:10.256> uh<09:50:10.980> waits<09:50:11.700> for<09:50:11.820> an<09:50:12.540> acknowledgment<09:50:13.200> or<09:50:13.740> act 09:50:14.030 --> 09:50:14.040 align:start position:0% it uh waits for an acknowledgment or act 09:50:14.040 --> 09:50:17.210 align:start position:0% it uh waits for an acknowledgment or act packet<09:50:14.640> receipt<09:50:15.660> now<09:50:16.320> with<09:50:16.620> each<09:50:16.800> receipt 09:50:17.210 --> 09:50:17.220 align:start position:0% packet receipt now with each receipt 09:50:17.220 --> 09:50:19.550 align:start position:0% packet receipt now with each receipt this<09:50:17.580> contains<09:50:18.060> the<09:50:18.540> current<09:50:18.840> maximum 09:50:19.550 --> 09:50:19.560 align:start position:0% this contains the current maximum 09:50:19.560 --> 09:50:21.650 align:start position:0% this contains the current maximum threshold<09:50:19.916> that<09:50:20.220> can<09:50:20.340> be<09:50:20.460> reached<09:50:20.880> and<09:50:21.540> then 09:50:21.650 --> 09:50:21.660 align:start position:0% threshold that can be reached and then 09:50:21.660 --> 09:50:24.426 align:start position:0% threshold that can be reached and then the<09:50:22.020> transmitter<09:50:22.560> is<09:50:23.460> going<09:50:23.640> to<09:50:23.880> begin 09:50:24.426 --> 09:50:24.436 align:start position:0% the transmitter is going to begin 09:50:24.436 --> 09:50:26.990 align:start position:0% the transmitter is going to begin increasing<09:50:25.436> the<09:50:25.680> number<09:50:25.800> of<09:50:25.980> packets<09:50:26.520> by<09:50:26.880> a 09:50:26.990 --> 09:50:27.000 align:start position:0% increasing the number of packets by a 09:50:27.000 --> 09:50:29.690 align:start position:0% increasing the number of packets by a specified<09:50:27.416> amount<09:50:27.900> in<09:50:28.800> other<09:50:28.860> words<09:50:29.096> it's 09:50:29.690 --> 09:50:29.700 align:start position:0% specified amount in other words it's 09:50:29.700 --> 09:50:32.266 align:start position:0% specified amount in other words it's going<09:50:29.880> to<09:50:30.000> start<09:50:30.180> sliding<09:50:30.776> that<09:50:30.960> window<09:50:31.276> from 09:50:32.266 --> 09:50:32.276 align:start position:0% going to start sliding that window from 09:50:32.276 --> 09:50:33.110 align:start position:0% going to start sliding that window from here 09:50:33.110 --> 09:50:33.120 align:start position:0% here 09:50:33.120 --> 09:50:34.730 align:start position:0% here over 09:50:34.730 --> 09:50:34.740 align:start position:0% over 09:50:34.740 --> 09:50:36.350 align:start position:0% over now<09:50:35.220> it's<09:50:35.340> going<09:50:35.520> to<09:50:35.640> continue<09:50:35.756> to<09:50:36.120> increase 09:50:36.350 --> 09:50:36.360 align:start position:0% now it's going to continue to increase 09:50:36.360 --> 09:50:39.470 align:start position:0% now it's going to continue to increase this<09:50:37.320> over<09:50:38.040> and<09:50:38.220> over<09:50:38.400> and<09:50:38.640> over 09:50:39.470 --> 09:50:39.480 align:start position:0% this over and over and over 09:50:39.480 --> 09:50:42.766 align:start position:0% this over and over and over until<09:50:40.020> we<09:50:40.436> reach<09:50:40.740> a<09:50:41.096> maximum<09:50:41.520> potential 09:50:42.766 --> 09:50:42.776 align:start position:0% until we reach a maximum potential 09:50:42.776 --> 09:50:44.266 align:start position:0% until we reach a maximum potential at<09:50:43.380> this<09:50:43.500> point<09:50:43.680> we're<09:50:43.916> going<09:50:44.096> to<09:50:44.096> start 09:50:44.266 --> 09:50:44.276 align:start position:0% at this point we're going to start 09:50:44.276 --> 09:50:47.510 align:start position:0% at this point we're going to start getting<09:50:44.520> some<09:50:44.756> congestion<09:50:45.300> and<09:50:46.256> so<09:50:46.520> the 09:50:47.510 --> 09:50:47.520 align:start position:0% getting some congestion and so the 09:50:47.520 --> 09:50:49.190 align:start position:0% getting some congestion and so the receiver<09:50:48.120> is<09:50:48.360> going<09:50:48.540> to<09:50:48.596> send<09:50:48.720> another<09:50:48.900> act 09:50:49.190 --> 09:50:49.200 align:start position:0% receiver is going to send another act 09:50:49.200 --> 09:50:50.870 align:start position:0% receiver is going to send another act saying<09:50:49.620> listen<09:50:49.740> you<09:50:49.980> need<09:50:50.160> to<09:50:50.276> slow<09:50:50.400> down<09:50:50.580> now 09:50:50.870 --> 09:50:50.880 align:start position:0% saying listen you need to slow down now 09:50:50.880 --> 09:50:53.990 align:start position:0% saying listen you need to slow down now and<09:50:51.540> and<09:50:51.840> this<09:50:52.320> is<09:50:52.436> a<09:50:52.620> good<09:50:52.740> rate 09:50:53.990 --> 09:50:54.000 align:start position:0% and and this is a good rate 09:50:54.000 --> 09:50:55.790 align:start position:0% and and this is a good rate this<09:50:54.540> method<09:50:54.840> is<09:50:55.020> really<09:50:55.140> going<09:50:55.320> to<09:50:55.320> allow<09:50:55.620> for 09:50:55.790 --> 09:50:55.800 align:start position:0% this method is really going to allow for 09:50:55.800 --> 09:50:58.730 align:start position:0% this method is really going to allow for minimal<09:50:56.276> data<09:50:56.756> traffic<09:50:57.000> congestion<09:50:57.776> and<09:50:58.560> a 09:50:58.730 --> 09:50:58.740 align:start position:0% minimal data traffic congestion and a 09:50:58.740 --> 09:50:59.990 align:start position:0% minimal data traffic congestion and a lot<09:50:58.800> of<09:50:58.980> throughput 09:50:59.990 --> 09:51:00.000 align:start position:0% lot of throughput 09:51:00.000 --> 09:51:01.790 align:start position:0% lot of throughput depending<09:51:00.720> on<09:51:00.776> the<09:51:00.900> amount<09:51:01.140> of<09:51:01.256> traffic<09:51:01.380> the 09:51:01.790 --> 09:51:01.800 align:start position:0% depending on the amount of traffic the 09:51:01.800 --> 09:51:03.530 align:start position:0% depending on the amount of traffic the size<09:51:01.980> of<09:51:02.160> the<09:51:02.276> window<09:51:02.460> can<09:51:03.060> really<09:51:03.240> vary 09:51:03.530 --> 09:51:03.540 align:start position:0% size of the window can really vary 09:51:03.540 --> 09:51:05.510 align:start position:0% size of the window can really vary dramatically<09:51:04.140> and<09:51:04.620> so<09:51:04.800> this<09:51:04.980> really<09:51:05.160> gives<09:51:05.340> us 09:51:05.510 --> 09:51:05.520 align:start position:0% dramatically and so this really gives us 09:51:05.520 --> 09:51:08.150 align:start position:0% dramatically and so this really gives us a<09:51:05.640> lot<09:51:05.756> more<09:51:05.880> flexibility<09:51:06.596> if<09:51:07.436> you<09:51:07.560> imagine<09:51:07.740> if 09:51:08.150 --> 09:51:08.160 align:start position:0% a lot more flexibility if you imagine if 09:51:08.160 --> 09:51:10.010 align:start position:0% a lot more flexibility if you imagine if I<09:51:08.340> have<09:51:08.520> a<09:51:08.880> home<09:51:09.000> that<09:51:09.360> has<09:51:09.480> a<09:51:09.660> whole<09:51:09.720> bunch<09:51:09.900> of 09:51:10.010 --> 09:51:10.020 align:start position:0% I have a home that has a whole bunch of 09:51:10.020 --> 09:51:11.926 align:start position:0% I have a home that has a whole bunch of irregular<09:51:10.740> Windows<09:51:11.276> I'm<09:51:11.640> going<09:51:11.756> to<09:51:11.820> want 09:51:11.926 --> 09:51:11.936 align:start position:0% irregular Windows I'm going to want 09:51:11.936 --> 09:51:13.906 align:start position:0% irregular Windows I'm going to want sliding<09:51:12.360> Windows<09:51:12.776> now<09:51:13.200> if<09:51:13.320> I<09:51:13.436> have<09:51:13.560> a<09:51:13.740> home 09:51:13.906 --> 09:51:13.916 align:start position:0% sliding Windows now if I have a home 09:51:13.916 --> 09:51:15.530 align:start position:0% sliding Windows now if I have a home with<09:51:14.220> all<09:51:14.580> these<09:51:14.756> similar<09:51:15.120> Windows 09:51:15.530 --> 09:51:15.540 align:start position:0% with all these similar Windows 09:51:15.540 --> 09:51:17.086 align:start position:0% with all these similar Windows everything<09:51:15.720> built<09:51:16.256> the<09:51:16.380> same<09:51:16.500> then<09:51:16.680> I<09:51:16.860> can<09:51:16.980> use 09:51:17.086 --> 09:51:17.096 align:start position:0% everything built the same then I can use 09:51:17.096 --> 09:51:18.890 align:start position:0% everything built the same then I can use a<09:51:17.220> fixed<09:51:17.520> link<09:51:17.640> window<09:51:17.936> but<09:51:18.416> this<09:51:18.596> one's<09:51:18.776> going 09:51:18.890 --> 09:51:18.900 align:start position:0% a fixed link window but this one's going 09:51:18.900 --> 09:51:21.586 align:start position:0% a fixed link window but this one's going to<09:51:19.020> give<09:51:19.140> me<09:51:19.256> a<09:51:19.436> lot<09:51:19.500> more<09:51:19.680> flexibility 09:51:21.586 --> 09:51:21.596 align:start position:0% to give me a lot more flexibility 09:51:21.596 --> 09:51:24.650 align:start position:0% to give me a lot more flexibility now<09:51:22.200> error<09:51:22.740> detection<09:51:23.096> and<09:51:23.520> correction<09:51:23.936> is<09:51:24.540> an 09:51:24.650 --> 09:51:24.660 align:start position:0% now error detection and correction is an 09:51:24.660 --> 09:51:26.510 align:start position:0% now error detection and correction is an important<09:51:25.020> aspect<09:51:25.380> of<09:51:25.620> how<09:51:25.860> we<09:51:26.040> know<09:51:26.220> our 09:51:26.510 --> 09:51:26.520 align:start position:0% important aspect of how we know our 09:51:26.520 --> 09:51:28.690 align:start position:0% important aspect of how we know our information<09:51:26.756> arrives<09:51:27.596> at<09:51:27.720> the<09:51:27.900> destination 09:51:28.690 --> 09:51:28.700 align:start position:0% information arrives at the destination 09:51:28.700 --> 09:51:32.030 align:start position:0% information arrives at the destination unhindered<09:51:29.700> and<09:51:30.060> unaltered<09:51:30.720> one<09:51:31.620> method 09:51:32.030 --> 09:51:32.040 align:start position:0% unhindered and unaltered one method 09:51:32.040 --> 09:51:34.790 align:start position:0% unhindered and unaltered one method achieves<09:51:32.580> this<09:51:32.880> by<09:51:33.416> attaching<09:51:33.960> supplemental 09:51:34.790 --> 09:51:34.800 align:start position:0% achieves this by attaching supplemental 09:51:34.800 --> 09:51:36.290 align:start position:0% achieves this by attaching supplemental information<09:51:35.096> at<09:51:35.580> the<09:51:35.700> end<09:51:35.756> of<09:51:35.880> the<09:51:35.936> footer 09:51:36.290 --> 09:51:36.300 align:start position:0% information at the end of the footer 09:51:36.300 --> 09:51:38.870 align:start position:0% information at the end of the footer that<09:51:36.776> pertains<09:51:37.200> to<09:51:37.320> its<09:51:37.620> contents<09:51:38.096> and<09:51:38.756> the 09:51:38.870 --> 09:51:38.880 align:start position:0% that pertains to its contents and the 09:51:38.880 --> 09:51:40.130 align:start position:0% that pertains to its contents and the receiving<09:51:39.120> station<09:51:39.416> is<09:51:39.660> going<09:51:39.840> to<09:51:39.840> look<09:51:40.020> at 09:51:40.130 --> 09:51:40.140 align:start position:0% receiving station is going to look at 09:51:40.140 --> 09:51:41.870 align:start position:0% receiving station is going to look at that<09:51:40.256> data<09:51:40.560> and<09:51:40.680> compare<09:51:41.096> it<09:51:41.220> to<09:51:41.340> the<09:51:41.460> data<09:51:41.756> it 09:51:41.870 --> 09:51:41.880 align:start position:0% that data and compare it to the data it 09:51:41.880 --> 09:51:42.950 align:start position:0% that data and compare it to the data it received 09:51:42.950 --> 09:51:42.960 align:start position:0% received 09:51:42.960 --> 09:51:44.570 align:start position:0% received the<09:51:43.140> data<09:51:43.500> matches<09:51:43.860> it's<09:51:44.040> going<09:51:44.160> to<09:51:44.160> consider 09:51:44.570 --> 09:51:44.580 align:start position:0% the data matches it's going to consider 09:51:44.580 --> 09:51:46.906 align:start position:0% the data matches it's going to consider it<09:51:44.700> error<09:51:45.060> free<09:51:45.240> if<09:51:45.900> not<09:51:46.080> the<09:51:46.380> data<09:51:46.680> is<09:51:46.800> going 09:51:46.906 --> 09:51:46.916 align:start position:0% it error free if not the data is going 09:51:46.916 --> 09:51:49.426 align:start position:0% it error free if not the data is going to<09:51:47.040> be<09:51:47.096> requested<09:51:47.580> to<09:51:47.756> be<09:51:47.880> re-transmitted<09:51:48.840> now 09:51:49.426 --> 09:51:49.436 align:start position:0% to be requested to be re-transmitted now 09:51:49.436 --> 09:51:50.990 align:start position:0% to be requested to be re-transmitted now when<09:51:49.680> an<09:51:49.860> additional<09:51:50.220> Correctional 09:51:50.990 --> 09:51:51.000 align:start position:0% when an additional Correctional 09:51:51.000 --> 09:51:53.210 align:start position:0% when an additional Correctional component<09:51:51.480> is<09:51:51.660> added<09:51:52.020> that<09:51:52.500> allows<09:51:52.800> the<09:51:52.916> data 09:51:53.210 --> 09:51:53.220 align:start position:0% component is added that allows the data 09:51:53.220 --> 09:51:55.370 align:start position:0% component is added that allows the data to<09:51:53.340> be<09:51:53.460> rebuilt<09:51:54.000> in<09:51:54.120> the<09:51:54.360> error<09:51:54.720> in<09:51:55.140> the<09:51:55.256> event 09:51:55.370 --> 09:51:55.380 align:start position:0% to be rebuilt in the error in the event 09:51:55.380 --> 09:51:57.110 align:start position:0% to be rebuilt in the error in the event of<09:51:55.620> an<09:51:55.740> error<09:51:56.096> this<09:51:56.460> is<09:51:56.580> going<09:51:56.640> to<09:51:56.700> become<09:51:56.936> an 09:51:57.110 --> 09:51:57.120 align:start position:0% of an error this is going to become an 09:51:57.120 --> 09:52:01.010 align:start position:0% of an error this is going to become an edac<09:51:57.596> or<09:51:58.140> error<09:51:58.620> detection<09:51:58.916> and<09:51:59.700> correction 09:52:01.010 --> 09:52:01.020 align:start position:0% edac or error detection and correction 09:52:01.020 --> 09:52:04.010 align:start position:0% edac or error detection and correction now<09:52:01.680> parity<09:52:02.220> check<09:52:02.520> is<09:52:03.060> a<09:52:03.240> process<09:52:03.480> where<09:52:03.776> an 09:52:04.010 --> 09:52:04.020 align:start position:0% now parity check is a process where an 09:52:04.020 --> 09:52:06.950 align:start position:0% now parity check is a process where an extra<09:52:04.200> bit<09:52:04.560> is<09:52:05.040> added<09:52:05.340> to<09:52:05.580> every<09:52:05.820> word<09:52:06.060> of<09:52:06.240> data 09:52:06.950 --> 09:52:06.960 align:start position:0% extra bit is added to every word of data 09:52:06.960 --> 09:52:09.110 align:start position:0% extra bit is added to every word of data the<09:52:07.436> receiving<09:52:07.800> station<09:52:08.160> can<09:52:08.580> look<09:52:08.756> for<09:52:08.936> the 09:52:09.110 --> 09:52:09.120 align:start position:0% the receiving station can look for the 09:52:09.120 --> 09:52:11.926 align:start position:0% the receiving station can look for the bit<09:52:09.240> on<09:52:09.660> this<09:52:09.840> word<09:52:10.140> by<09:52:10.380> word<09:52:10.620> basis<09:52:11.276> remember 09:52:11.926 --> 09:52:11.936 align:start position:0% bit on this word by word basis remember 09:52:11.936 --> 09:52:13.490 align:start position:0% bit on this word by word basis remember we're<09:52:12.240> talking<09:52:12.416> about<09:52:12.596> words<09:52:12.960> we're<09:52:13.320> not 09:52:13.490 --> 09:52:13.500 align:start position:0% we're talking about words we're not 09:52:13.500 --> 09:52:16.070 align:start position:0% we're talking about words we're not talking<09:52:13.800> about<09:52:14.180> uh<09:52:15.180> language<09:52:15.540> we're<09:52:15.900> talking 09:52:16.070 --> 09:52:16.080 align:start position:0% talking about uh language we're talking 09:52:16.080 --> 09:52:18.766 align:start position:0% talking about uh language we're talking about<09:52:16.256> words<09:52:16.560> as<09:52:16.916> far<09:52:17.040> as<09:52:17.160> data<09:52:17.580> goes<09:52:17.880> and<09:52:18.596> so 09:52:18.766 --> 09:52:18.776 align:start position:0% about words as far as data goes and so 09:52:18.776 --> 09:52:20.746 align:start position:0% about words as far as data goes and so it<09:52:18.900> can<09:52:19.020> look<09:52:19.200> at<09:52:19.380> these<09:52:19.620> and<09:52:20.220> therefore<09:52:20.520> it 09:52:20.746 --> 09:52:20.756 align:start position:0% it can look at these and therefore it 09:52:20.756 --> 09:52:23.450 align:start position:0% it can look at these and therefore it can<09:52:20.936> determine<09:52:21.480> any<09:52:21.960> errors<09:52:22.500> that<09:52:23.040> are<09:52:23.160> built 09:52:23.450 --> 09:52:23.460 align:start position:0% can determine any errors that are built 09:52:23.460 --> 09:52:27.650 align:start position:0% can determine any errors that are built in<09:52:23.580> because<09:52:24.416> parity<09:52:25.320> adds<09:52:25.916> this<09:52:26.160> extra<09:52:26.580> bit<09:52:27.300> to 09:52:27.650 --> 09:52:27.660 align:start position:0% in because parity adds this extra bit to 09:52:27.660 --> 09:52:29.630 align:start position:0% in because parity adds this extra bit to every<09:52:27.900> word<09:52:28.200> this<09:52:28.860> method<09:52:29.160> takes<09:52:29.400> a<09:52:29.520> little 09:52:29.630 --> 09:52:29.640 align:start position:0% every word this method takes a little 09:52:29.640 --> 09:52:34.730 align:start position:0% every word this method takes a little bit<09:52:29.756> of<09:52:29.880> overhead<09:52:30.416> so<09:52:31.200> it<09:52:31.320> does<09:52:31.620> ADD 09:52:34.730 --> 09:52:34.740 align:start position:0% 09:52:34.740 --> 09:52:37.010 align:start position:0% not<09:52:35.400> only<09:52:35.580> extra<09:52:35.820> resources<09:52:36.360> but<09:52:36.596> some<09:52:36.776> more 09:52:37.010 --> 09:52:37.020 align:start position:0% not only extra resources but some more 09:52:37.020 --> 09:52:38.746 align:start position:0% not only extra resources but some more data<09:52:37.320> in<09:52:37.436> there<09:52:37.560> now<09:52:38.220> with<09:52:38.400> something<09:52:38.520> called 09:52:38.746 --> 09:52:38.756 align:start position:0% data in there now with something called 09:52:38.756 --> 09:52:42.530 align:start position:0% data in there now with something called CRC<09:52:39.300> or<09:52:39.540> cyclic<09:52:40.020> redundancy<09:52:40.916> check<09:52:41.160> a<09:52:42.120> code<09:52:42.300> is 09:52:42.530 --> 09:52:42.540 align:start position:0% CRC or cyclic redundancy check a code is 09:52:42.540 --> 09:52:45.290 align:start position:0% CRC or cyclic redundancy check a code is added<09:52:42.900> to<09:52:43.200> every<09:52:43.620> block<09:52:43.916> of<09:52:44.340> data<09:52:44.700> through<09:52:45.120> a 09:52:45.290 --> 09:52:45.300 align:start position:0% added to every block of data through a 09:52:45.300 --> 09:52:47.510 align:start position:0% added to every block of data through a mathematical<09:52:45.840> operation 09:52:47.510 --> 09:52:47.520 align:start position:0% mathematical operation 09:52:47.520 --> 09:52:50.746 align:start position:0% mathematical operation which<09:52:47.880> is<09:52:48.000> also<09:52:48.240> referred<09:52:48.596> to<09:52:48.720> as<09:52:48.900> hashing 09:52:50.746 --> 09:52:50.756 align:start position:0% which is also referred to as hashing 09:52:50.756 --> 09:52:53.150 align:start position:0% which is also referred to as hashing now<09:52:51.180> this<09:52:51.416> code<09:52:51.660> is<09:52:52.020> added<09:52:52.380> to<09:52:52.500> the<09:52:52.680> end<09:52:52.860> of<09:52:53.040> the 09:52:53.150 --> 09:52:53.160 align:start position:0% now this code is added to the end of the 09:52:53.160 --> 09:52:55.970 align:start position:0% now this code is added to the end of the block<09:52:53.340> and<09:52:54.180> then<09:52:54.300> it's<09:52:54.540> transmitted 09:52:55.970 --> 09:52:55.980 align:start position:0% block and then it's transmitted 09:52:55.980 --> 09:52:59.266 align:start position:0% block and then it's transmitted when<09:52:56.460> the<09:52:56.640> receiving<09:52:57.060> station<09:52:57.800> applies<09:52:58.800> this 09:52:59.266 --> 09:52:59.276 align:start position:0% when the receiving station applies this 09:52:59.276 --> 09:53:00.650 align:start position:0% when the receiving station applies this hashing<09:52:59.640> method<09:52:59.936> this<09:53:00.180> mathematical 09:53:00.650 --> 09:53:00.660 align:start position:0% hashing method this mathematical 09:53:00.660 --> 09:53:02.570 align:start position:0% hashing method this mathematical operation<09:53:01.140> to<09:53:01.560> the<09:53:01.740> code 09:53:02.570 --> 09:53:02.580 align:start position:0% operation to the code 09:53:02.580 --> 09:53:05.926 align:start position:0% operation to the code then<09:53:03.240> it<09:53:03.480> can<09:53:03.660> should<09:53:03.900> get<09:53:04.256> the<09:53:05.040> same<09:53:05.220> data<09:53:05.700> and 09:53:05.926 --> 09:53:05.936 align:start position:0% then it can should get the same data and 09:53:05.936 --> 09:53:07.490 align:start position:0% then it can should get the same data and if<09:53:06.060> it<09:53:06.240> doesn't<09:53:06.360> then<09:53:06.720> it<09:53:06.900> knows<09:53:07.140> there's<09:53:07.256> a 09:53:07.490 --> 09:53:07.500 align:start position:0% if it doesn't then it knows there's a 09:53:07.500 --> 09:53:09.406 align:start position:0% if it doesn't then it knows there's a problem<09:53:07.680> and<09:53:08.220> it<09:53:08.400> can<09:53:08.520> request<09:53:08.880> it<09:53:09.060> to<09:53:09.300> be 09:53:09.406 --> 09:53:09.416 align:start position:0% problem and it can request it to be 09:53:09.416 --> 09:53:12.586 align:start position:0% problem and it can request it to be resent<09:53:09.960> like<09:53:10.916> parity<09:53:11.340> CRC<09:53:11.936> is<09:53:12.120> also<09:53:12.360> going<09:53:12.480> to 09:53:12.586 --> 09:53:12.596 align:start position:0% resent like parity CRC is also going to 09:53:12.596 --> 09:53:14.630 align:start position:0% resent like parity CRC is also going to add<09:53:12.776> a<09:53:12.960> certain<09:53:13.080> amount<09:53:13.320> of<09:53:13.500> overhead<09:53:14.040> because 09:53:14.630 --> 09:53:14.640 align:start position:0% add a certain amount of overhead because 09:53:14.640 --> 09:53:17.030 align:start position:0% add a certain amount of overhead because it<09:53:14.880> takes<09:53:15.060> data<09:53:15.480> and<09:53:15.596> calculation<09:53:16.140> time<09:53:16.436> all 09:53:17.030 --> 09:53:17.040 align:start position:0% it takes data and calculation time all 09:53:17.040 --> 09:53:19.550 align:start position:0% it takes data and calculation time all right<09:53:17.220> so<09:53:18.120> now<09:53:18.540> just<09:53:18.776> to<09:53:18.900> review<09:53:19.080> some<09:53:19.380> of<09:53:19.500> the 09:53:19.550 --> 09:53:19.560 align:start position:0% right so now just to review some of the 09:53:19.560 --> 09:53:21.470 align:start position:0% right so now just to review some of the topics<09:53:19.800> we<09:53:19.980> talked<09:53:20.340> about<09:53:20.400> we<09:53:21.180> talked<09:53:21.416> about 09:53:21.470 --> 09:53:21.480 align:start position:0% topics we talked about we talked about 09:53:21.480 --> 09:53:25.310 align:start position:0% topics we talked about we talked about the<09:53:22.096> IPv6<09:53:23.096> addressing<09:53:24.000> scheme<09:53:24.416> specifically 09:53:25.310 --> 09:53:25.320 align:start position:0% the IPv6 addressing scheme specifically 09:53:25.320 --> 09:53:28.330 align:start position:0% the IPv6 addressing scheme specifically we<09:53:25.560> talked<09:53:25.860> to<09:53:25.916> that<09:53:26.040> it's<09:53:26.220> a<09:53:26.460> hexadecimal 09:53:28.330 --> 09:53:28.340 align:start position:0% we talked to that it's a hexadecimal 09:53:28.340 --> 09:53:31.130 align:start position:0% we talked to that it's a hexadecimal 128<09:53:29.340> bits 09:53:31.130 --> 09:53:31.140 align:start position:0% 128 bits 09:53:31.140 --> 09:53:32.926 align:start position:0% 128 bits divided<09:53:31.980> into 09:53:32.926 --> 09:53:32.936 align:start position:0% divided into 09:53:32.936 --> 09:53:35.450 align:start position:0% divided into eight<09:53:33.540> sections 09:53:35.450 --> 09:53:35.460 align:start position:0% eight sections 09:53:35.460 --> 09:53:38.630 align:start position:0% eight sections we<09:53:35.936> also<09:53:36.180> compared<09:53:36.720> and<09:53:36.960> contrasted<09:53:37.680> IPv6 09:53:38.630 --> 09:53:38.640 align:start position:0% we also compared and contrasted IPv6 09:53:38.640 --> 09:53:41.990 align:start position:0% we also compared and contrasted IPv6 with<09:53:38.936> ipv4<09:53:39.660> we<09:53:40.380> saw<09:53:40.500> that<09:53:40.680> IPv6<09:53:41.460> for<09:53:41.756> instance 09:53:41.990 --> 09:53:42.000 align:start position:0% with ipv4 we saw that IPv6 for instance 09:53:42.000 --> 09:53:44.150 align:start position:0% with ipv4 we saw that IPv6 for instance has<09:53:42.240> ipsec<09:53:43.140> built<09:53:43.500> in 09:53:44.150 --> 09:53:44.160 align:start position:0% has ipsec built in 09:53:44.160 --> 09:53:46.150 align:start position:0% has ipsec built in and<09:53:44.460> has<09:53:44.880> a<09:53:45.300> whole<09:53:45.416> bunch<09:53:45.596> of<09:53:45.776> other 09:53:46.150 --> 09:53:46.160 align:start position:0% and has a whole bunch of other 09:53:46.160 --> 09:53:50.030 align:start position:0% and has a whole bunch of other improvements<09:53:47.160> and<09:53:47.880> mechanisms<09:53:48.596> such<09:53:49.380> as<09:53:49.560> data 09:53:50.030 --> 09:53:50.040 align:start position:0% improvements and mechanisms such as data 09:53:50.040 --> 09:53:53.450 align:start position:0% improvements and mechanisms such as data delivery<09:53:50.520> time<09:53:51.360> sensitive<09:53:52.080> and<09:53:52.680> so<09:53:52.860> on<09:53:53.040> and<09:53:53.220> so 09:53:53.450 --> 09:53:53.460 align:start position:0% delivery time sensitive and so on and so 09:53:53.460 --> 09:53:55.310 align:start position:0% delivery time sensitive and so on and so forth<09:53:53.756> the<09:53:54.300> important<09:53:54.596> thing<09:53:54.776> I<09:53:55.020> really<09:53:55.140> want 09:53:55.310 --> 09:53:55.320 align:start position:0% forth the important thing I really want 09:53:55.320 --> 09:53:57.530 align:start position:0% forth the important thing I really want you<09:53:55.436> to<09:53:55.620> know<09:53:55.740> about<09:53:55.860> IPv6 09:53:57.530 --> 09:53:57.540 align:start position:0% you to know about IPv6 09:53:57.540 --> 09:54:00.406 align:start position:0% you to know about IPv6 is<09:53:58.080> that<09:53:58.320> it<09:53:58.560> does<09:53:58.800> not<09:53:59.096> require 09:54:00.406 --> 09:54:00.416 align:start position:0% is that it does not require 09:54:00.416 --> 09:54:02.266 align:start position:0% is that it does not require a<09:54:01.020> subnet 09:54:02.266 --> 09:54:02.276 align:start position:0% a subnet 09:54:02.276 --> 09:54:05.330 align:start position:0% a subnet and<09:54:03.060> we<09:54:03.360> need<09:54:03.540> to<09:54:03.840> recall<09:54:04.320> all<09:54:04.860> of<09:54:04.980> the 09:54:05.330 --> 09:54:05.340 align:start position:0% and we need to recall all of the 09:54:05.340 --> 09:54:08.690 align:start position:0% and we need to recall all of the truncation<09:54:06.300> or<09:54:06.596> readability<09:54:07.020> rules 09:54:08.690 --> 09:54:08.700 align:start position:0% truncation or readability rules 09:54:08.700 --> 09:54:14.390 align:start position:0% truncation or readability rules which<09:54:09.240> include<09:54:10.160> removing<09:54:11.160> leading<09:54:12.000> zeros 09:54:14.390 --> 09:54:14.400 align:start position:0% which include removing leading zeros 09:54:14.400 --> 09:54:17.406 align:start position:0% which include removing leading zeros and 09:54:17.406 --> 09:54:17.416 align:start position:0% 09:54:17.416 --> 09:54:21.110 align:start position:0% combining<09:54:18.416> successive 09:54:21.110 --> 09:54:21.120 align:start position:0% combining successive 09:54:21.120 --> 09:54:22.970 align:start position:0% combining successive sets<09:54:21.660> of<09:54:21.776> zeros 09:54:22.970 --> 09:54:22.980 align:start position:0% sets of zeros 09:54:22.980 --> 09:54:26.630 align:start position:0% sets of zeros but<09:54:23.400> only<09:54:23.640> once 09:54:26.630 --> 09:54:26.640 align:start position:0% 09:54:26.640 --> 09:54:28.610 align:start position:0% we<09:54:27.060> also<09:54:27.240> explained<09:54:27.660> the<09:54:27.840> different<09:54:28.080> data 09:54:28.610 --> 09:54:28.620 align:start position:0% we also explained the different data 09:54:28.620 --> 09:54:31.550 align:start position:0% we also explained the different data delivery<09:54:29.220> techniques<09:54:30.000> and<09:54:30.720> we<09:54:30.840> defined<09:54:31.256> a 09:54:31.550 --> 09:54:31.560 align:start position:0% delivery techniques and we defined a 09:54:31.560 --> 09:54:33.050 align:start position:0% delivery techniques and we defined a connection<09:54:31.740> the<09:54:32.520> different<09:54:32.756> connection 09:54:33.050 --> 09:54:33.060 align:start position:0% connection the different connection 09:54:33.060 --> 09:54:34.850 align:start position:0% connection the different connection modes<09:54:33.720> whether<09:54:33.960> they're<09:54:34.200> acknowledged 09:54:34.850 --> 09:54:34.860 align:start position:0% modes whether they're acknowledged 09:54:34.860 --> 09:54:39.406 align:start position:0% modes whether they're acknowledged connectionless 09:54:39.406 --> 09:54:39.416 align:start position:0% 09:54:39.416 --> 09:54:42.710 align:start position:0% simply<09:54:40.220> unacknowledged<09:54:41.220> connectionless 09:54:42.710 --> 09:54:42.720 align:start position:0% simply unacknowledged connectionless 09:54:42.720 --> 09:54:45.650 align:start position:0% simply unacknowledged connectionless or<09:54:43.560> connection<09:54:43.916> oriented 09:54:45.650 --> 09:54:45.660 align:start position:0% or connection oriented 09:54:45.660 --> 09:54:47.630 align:start position:0% or connection oriented we<09:54:46.080> also<09:54:46.256> looked<09:54:46.500> at<09:54:46.500> the<09:54:46.560> different<09:54:46.800> transmit 09:54:47.630 --> 09:54:47.640 align:start position:0% we also looked at the different transmit 09:54:47.640 --> 09:54:51.530 align:start position:0% we also looked at the different transmit types<09:54:48.060> including<09:54:48.960> Simplex<09:54:49.500> which<09:54:49.916> is<09:54:50.040> one<09:54:50.276> way 09:54:51.530 --> 09:54:51.540 align:start position:0% types including Simplex which is one way 09:54:51.540 --> 09:54:53.210 align:start position:0% types including Simplex which is one way half<09:54:51.900> duplex<09:54:52.380> which<09:54:52.740> is<09:54:52.800> like<09:54:52.980> our 09:54:53.210 --> 09:54:53.220 align:start position:0% half duplex which is like our 09:54:53.220 --> 09:54:55.610 align:start position:0% half duplex which is like our walkie-talkie 09:54:55.610 --> 09:54:55.620 align:start position:0% walkie-talkie 09:54:55.620 --> 09:54:57.830 align:start position:0% walkie-talkie and<09:54:56.040> full<09:54:56.160> duplex 09:54:57.830 --> 09:54:57.840 align:start position:0% and full duplex 09:54:57.840 --> 09:55:01.130 align:start position:0% and full duplex which<09:54:58.200> in<09:54:58.500> effect<09:54:58.680> doubles<09:54:59.160> our<09:54:59.340> bandwidth 09:55:01.130 --> 09:55:01.140 align:start position:0% which in effect doubles our bandwidth 09:55:01.140 --> 09:55:03.830 align:start position:0% which in effect doubles our bandwidth we<09:55:01.500> also<09:55:01.740> explained<09:55:02.096> flow<09:55:02.580> control<09:55:02.840> buffering 09:55:03.830 --> 09:55:03.840 align:start position:0% we also explained flow control buffering 09:55:03.840 --> 09:55:06.290 align:start position:0% we also explained flow control buffering and<09:55:04.200> data<09:55:04.560> windows<09:55:04.916> we<09:55:05.400> use<09:55:05.580> buffering<09:55:06.060> a<09:55:06.240> lot 09:55:06.290 --> 09:55:06.300 align:start position:0% and data windows we use buffering a lot 09:55:06.300 --> 09:55:08.510 align:start position:0% and data windows we use buffering a lot when<09:55:06.596> we're<09:55:06.776> talking<09:55:06.960> about<09:55:07.080> videos<09:55:07.436> in<09:55:08.160> data 09:55:08.510 --> 09:55:08.520 align:start position:0% when we're talking about videos in data 09:55:08.520 --> 09:55:10.010 align:start position:0% when we're talking about videos in data Windows<09:55:08.820> remember<09:55:09.000> we<09:55:09.360> talked<09:55:09.596> about<09:55:09.660> the 09:55:10.010 --> 09:55:10.020 align:start position:0% Windows remember we talked about the 09:55:10.020 --> 09:55:13.190 align:start position:0% Windows remember we talked about the fixed 09:55:13.190 --> 09:55:13.200 align:start position:0% 09:55:13.200 --> 09:55:16.190 align:start position:0% and<09:55:13.916> sliding<09:55:14.400> windows 09:55:16.190 --> 09:55:16.200 align:start position:0% and sliding windows 09:55:16.200 --> 09:55:18.650 align:start position:0% and sliding windows finally<09:55:16.860> we<09:55:17.276> outlined<09:55:17.756> error<09:55:18.300> detection 09:55:18.650 --> 09:55:18.660 align:start position:0% finally we outlined error detection 09:55:18.660 --> 09:55:22.130 align:start position:0% finally we outlined error detection methods<09:55:19.380> including<09:55:20.340> parity<09:55:21.060> which<09:55:21.596> adds<09:55:21.900> an 09:55:22.130 --> 09:55:22.140 align:start position:0% methods including parity which adds an 09:55:22.140 --> 09:55:24.406 align:start position:0% methods including parity which adds an extra<09:55:22.320> bit<09:55:22.800> to<09:55:23.160> every<09:55:23.340> word 09:55:24.406 --> 09:55:24.416 align:start position:0% extra bit to every word 09:55:24.416 --> 09:55:25.630 align:start position:0% extra bit to every word and 09:55:25.630 --> 09:55:25.640 align:start position:0% and 09:55:25.640 --> 09:55:29.510 align:start position:0% and CRC<09:55:26.640> or<09:55:27.180> cyclical<09:55:27.660> redundancy<09:55:28.560> check<09:55:28.800> which 09:55:29.510 --> 09:55:29.520 align:start position:0% CRC or cyclical redundancy check which 09:55:29.520 --> 09:55:32.330 align:start position:0% CRC or cyclical redundancy check which uses<09:55:29.880> hashing<09:55:30.416> a<09:55:30.596> mathematical<09:55:31.200> operation<09:55:31.740> so 09:55:32.330 --> 09:55:32.340 align:start position:0% uses hashing a mathematical operation so 09:55:32.340 --> 09:55:33.710 align:start position:0% uses hashing a mathematical operation so that<09:55:32.520> we<09:55:32.640> can<09:55:32.756> ensure<09:55:33.000> the<09:55:33.180> data<09:55:33.416> that<09:55:33.540> was 09:55:33.710 --> 09:55:33.720 align:start position:0% that we can ensure the data that was 09:55:33.720 --> 09:55:41.330 align:start position:0% that we can ensure the data that was received<09:55:34.200> was<09:55:34.680> also<09:55:35.040> the<09:55:35.160> data<09:55:35.460> that<09:55:35.580> was<09:55:35.700> sent 09:55:41.330 --> 09:55:41.340 align:start position:0% 09:55:41.340 --> 09:55:58.130 align:start position:0% [Music] 09:55:58.130 --> 09:55:58.140 align:start position:0% 09:55:58.140 --> 09:56:01.850 align:start position:0% welcome<09:55:58.680> to<09:55:58.916> module<09:55:59.340> 6<09:55:59.520> lesson<09:56:00.120> 4A<09:56:00.860> IPv6 09:56:01.850 --> 09:56:01.860 align:start position:0% welcome to module 6 lesson 4A IPv6 09:56:01.860 --> 09:56:04.850 align:start position:0% welcome to module 6 lesson 4A IPv6 Concepts 09:56:04.850 --> 09:56:04.860 align:start position:0% 09:56:04.860 --> 09:56:07.790 align:start position:0% now<09:56:05.520> we<09:56:05.936> actually<09:56:06.120> covered<09:56:06.540> IPv6<09:56:07.200> earlier 09:56:07.790 --> 09:56:07.800 align:start position:0% now we actually covered IPv6 earlier 09:56:07.800 --> 09:56:11.450 align:start position:0% now we actually covered IPv6 earlier however<09:56:08.276> as<09:56:08.880> per<09:56:09.060> usual<09:56:09.360> some<09:56:09.900> new<09:56:10.256> ideas<09:56:11.040> have 09:56:11.450 --> 09:56:11.460 align:start position:0% however as per usual some new ideas have 09:56:11.460 --> 09:56:14.330 align:start position:0% however as per usual some new ideas have been<09:56:11.520> added<09:56:11.936> to<09:56:12.776> the<09:56:12.960> syllabus<09:56:13.436> so<09:56:14.040> what<09:56:14.160> I'll 09:56:14.330 --> 09:56:14.340 align:start position:0% been added to the syllabus so what I'll 09:56:14.340 --> 09:56:18.050 align:start position:0% been added to the syllabus so what I'll do<09:56:14.520> here<09:56:14.756> is<09:56:15.000> I'll<09:56:15.660> review<09:56:16.500> some<09:56:17.096> areas<09:56:17.880> that 09:56:18.050 --> 09:56:18.060 align:start position:0% do here is I'll review some areas that 09:56:18.060 --> 09:56:20.990 align:start position:0% do here is I'll review some areas that you've<09:56:18.360> already<09:56:18.596> covered<09:56:19.080> with<09:56:19.560> Josh 09:56:20.990 --> 09:56:21.000 align:start position:0% you've already covered with Josh 09:56:21.000 --> 09:56:23.330 align:start position:0% you've already covered with Josh with<09:56:21.720> my<09:56:21.960> own<09:56:22.080> take<09:56:22.320> and<09:56:22.560> then<09:56:22.740> we'll<09:56:22.980> go<09:56:23.160> into 09:56:23.330 --> 09:56:23.340 align:start position:0% with my own take and then we'll go into 09:56:23.340 --> 09:56:25.246 align:start position:0% with my own take and then we'll go into the<09:56:23.756> new<09:56:24.060> stuff 09:56:25.246 --> 09:56:25.256 align:start position:0% the new stuff 09:56:25.256 --> 09:56:28.850 align:start position:0% the new stuff so<09:56:25.740> IPv6<09:56:26.460> addressing<09:56:27.120> address<09:56:27.660> types 09:56:28.850 --> 09:56:28.860 align:start position:0% so IPv6 addressing address types 09:56:28.860 --> 09:56:31.490 align:start position:0% so IPv6 addressing address types new<09:56:29.580> is<09:56:30.000> a<09:56:30.240> neighbor<09:56:30.416> Discovery<09:56:31.020> protocol 09:56:31.490 --> 09:56:31.500 align:start position:0% new is a neighbor Discovery protocol 09:56:31.500 --> 09:56:34.970 align:start position:0% new is a neighbor Discovery protocol which<09:56:32.040> is<09:56:32.160> part<09:56:32.460> of<09:56:32.640> IPv6<09:56:33.540> built<09:56:34.200> in 09:56:34.970 --> 09:56:34.980 align:start position:0% which is part of IPv6 built in 09:56:34.980 --> 09:56:38.810 align:start position:0% which is part of IPv6 built in the<09:56:35.520> eui<09:56:36.000> 64<09:56:36.416> addressing<09:56:37.080> is<09:56:37.436> new 09:56:38.810 --> 09:56:38.820 align:start position:0% the eui 64 addressing is new 09:56:38.820 --> 09:56:43.190 align:start position:0% the eui 64 addressing is new tunneling<09:56:39.660> types<09:56:40.080> is<09:56:40.560> new 09:56:43.190 --> 09:56:43.200 align:start position:0% 09:56:43.200 --> 09:56:45.950 align:start position:0% so<09:56:43.620> ipv4<09:56:44.400> which<09:56:44.756> is<09:56:44.880> obviously<09:56:45.180> the<09:56:45.416> precursor 09:56:45.950 --> 09:56:45.960 align:start position:0% so ipv4 which is obviously the precursor 09:56:45.960 --> 09:56:49.850 align:start position:0% so ipv4 which is obviously the precursor to<09:56:46.140> IPv6<09:56:46.936> it<09:56:47.936> created<09:56:48.300> a<09:56:48.480> long<09:56:48.540> time<09:56:48.720> before<09:56:49.080> we 09:56:49.850 --> 09:56:49.860 align:start position:0% to IPv6 it created a long time before we 09:56:49.860 --> 09:56:52.730 align:start position:0% to IPv6 it created a long time before we had<09:56:50.040> home<09:56:50.220> computers<09:56:50.900> computers<09:56:51.900> were<09:56:52.380> pretty 09:56:52.730 --> 09:56:52.740 align:start position:0% had home computers computers were pretty 09:56:52.740 --> 09:56:55.190 align:start position:0% had home computers computers were pretty expensive<09:56:53.400> and<09:56:53.700> big<09:56:53.880> probably<09:56:54.540> the<09:56:54.840> size<09:56:54.960> of 09:56:55.190 --> 09:56:55.200 align:start position:0% expensive and big probably the size of 09:56:55.200 --> 09:56:56.990 align:start position:0% expensive and big probably the size of any<09:56:55.560> room<09:56:55.800> in<09:56:56.096> your<09:56:56.276> house 09:56:56.990 --> 09:56:57.000 align:start position:0% any room in your house 09:56:57.000 --> 09:56:58.850 align:start position:0% any room in your house so<09:56:57.660> no 09:56:58.850 --> 09:56:58.860 align:start position:0% so no 09:56:58.860 --> 09:57:00.890 align:start position:0% so no um<09:56:58.916> nobody<09:56:59.700> foresaw<09:57:00.180> that<09:57:00.360> people<09:57:00.540> would<09:57:00.776> be 09:57:00.890 --> 09:57:00.900 align:start position:0% um nobody foresaw that people would be 09:57:00.900 --> 09:57:01.906 align:start position:0% um nobody foresaw that people would be using 09:57:01.906 --> 09:57:01.916 align:start position:0% using 09:57:01.916 --> 09:57:04.190 align:start position:0% using uh<09:57:02.520> home<09:57:02.756> computers<09:57:03.300> just<09:57:03.720> like<09:57:03.840> when<09:57:04.020> the 09:57:04.190 --> 09:57:04.200 align:start position:0% uh home computers just like when the 09:57:04.200 --> 09:57:06.890 align:start position:0% uh home computers just like when the telephone<09:57:04.320> was<09:57:04.740> created<09:57:05.160> I<09:57:06.120> think<09:57:06.240> uh<09:57:06.540> one<09:57:06.776> of 09:57:06.890 --> 09:57:06.900 align:start position:0% telephone was created I think uh one of 09:57:06.900 --> 09:57:08.990 align:start position:0% telephone was created I think uh one of the<09:57:06.960> first<09:57:07.080> comments<09:57:07.436> was<09:57:07.620> why<09:57:07.800> would<09:57:08.040> I<09:57:08.276> I 09:57:08.990 --> 09:57:09.000 align:start position:0% the first comments was why would I I 09:57:09.000 --> 09:57:10.790 align:start position:0% the first comments was why would I I don't<09:57:09.300> need<09:57:09.416> to<09:57:09.540> phone<09:57:09.660> anyone 09:57:10.790 --> 09:57:10.800 align:start position:0% don't need to phone anyone 09:57:10.800 --> 09:57:13.670 align:start position:0% don't need to phone anyone so<09:57:11.400> uh<09:57:11.700> there<09:57:12.120> we<09:57:12.300> go 09:57:13.670 --> 09:57:13.680 align:start position:0% so uh there we go 09:57:13.680 --> 09:57:15.530 align:start position:0% so uh there we go uh<09:57:14.096> so<09:57:14.220> it<09:57:14.460> was<09:57:14.640> just<09:57:14.756> the<09:57:15.000> scheme<09:57:15.416> was 09:57:15.530 --> 09:57:15.540 align:start position:0% uh so it was just the scheme was 09:57:15.540 --> 09:57:17.330 align:start position:0% uh so it was just the scheme was designed<09:57:15.900> just<09:57:16.080> to<09:57:16.320> cater<09:57:16.980> for<09:57:17.160> commercial 09:57:17.330 --> 09:57:17.340 align:start position:0% designed just to cater for commercial 09:57:17.340 --> 09:57:19.730 align:start position:0% designed just to cater for commercial Enterprises<09:57:18.180> only<09:57:18.416> so<09:57:19.080> we<09:57:19.256> didn't<09:57:19.380> think<09:57:19.560> we 09:57:19.730 --> 09:57:19.740 align:start position:0% Enterprises only so we didn't think we 09:57:19.740 --> 09:57:21.170 align:start position:0% Enterprises only so we didn't think we were<09:57:19.860> going<09:57:19.980> to<09:57:20.096> run<09:57:20.220> out 09:57:21.170 --> 09:57:21.180 align:start position:0% were going to run out 09:57:21.180 --> 09:57:23.690 align:start position:0% were going to run out lack<09:57:21.840> of<09:57:21.960> a<09:57:22.140> simple<09:57:22.380> Auto<09:57:22.860> configuration 09:57:23.690 --> 09:57:23.700 align:start position:0% lack of a simple Auto configuration 09:57:23.700 --> 09:57:27.530 align:start position:0% lack of a simple Auto configuration mechanism<09:57:24.540> so<09:57:25.500> I<09:57:25.680> eventually<09:57:26.160> we<09:57:26.580> had 09:57:27.530 --> 09:57:27.540 align:start position:0% mechanism so I eventually we had 09:57:27.540 --> 09:57:30.906 align:start position:0% mechanism so I eventually we had um<09:57:27.596> DHCP<09:57:28.560> was<09:57:29.460> uh<09:57:29.820> created 09:57:30.906 --> 09:57:30.916 align:start position:0% um DHCP was uh created 09:57:30.916 --> 09:57:33.530 align:start position:0% um DHCP was uh created which<09:57:31.916> works<09:57:32.340> well<09:57:32.580> obviously<09:57:33.000> it's<09:57:33.180> got<09:57:33.360> some 09:57:33.530 --> 09:57:33.540 align:start position:0% which works well obviously it's got some 09:57:33.540 --> 09:57:35.570 align:start position:0% which works well obviously it's got some drawbacks 09:57:35.570 --> 09:57:35.580 align:start position:0% drawbacks 09:57:35.580 --> 09:57:39.050 align:start position:0% drawbacks an<09:57:36.180> ipv4<09:57:36.840> has<09:57:37.140> no<09:57:37.380> security<09:57:37.680> built<09:57:38.460> in<09:57:38.520> again 09:57:39.050 --> 09:57:39.060 align:start position:0% an ipv4 has no security built in again 09:57:39.060 --> 09:57:41.390 align:start position:0% an ipv4 has no security built in again nobody<09:57:39.740> realized<09:57:40.740> that 09:57:41.390 --> 09:57:41.400 align:start position:0% nobody realized that 09:57:41.400 --> 09:57:43.370 align:start position:0% nobody realized that well<09:57:42.060> there<09:57:42.240> was<09:57:42.360> no<09:57:42.480> such<09:57:42.596> thing<09:57:42.776> as<09:57:42.900> hackers 09:57:43.370 --> 09:57:43.380 align:start position:0% well there was no such thing as hackers 09:57:43.380 --> 09:57:45.170 align:start position:0% well there was no such thing as hackers obviously<09:57:44.040> when<09:57:44.220> IP<09:57:44.580> was<09:57:44.756> brought<09:57:45.000> out 09:57:45.170 --> 09:57:45.180 align:start position:0% obviously when IP was brought out 09:57:45.180 --> 09:57:47.210 align:start position:0% obviously when IP was brought out because<09:57:45.540> they<09:57:45.900> hadn't<09:57:46.500> been<09:57:46.620> invented<09:57:46.916> yet<09:57:47.040> so 09:57:47.210 --> 09:57:47.220 align:start position:0% because they hadn't been invented yet so 09:57:47.220 --> 09:57:49.190 align:start position:0% because they hadn't been invented yet so nobody<09:57:47.520> thought<09:57:47.700> that<09:57:47.880> we<09:57:48.060> needed<09:57:48.360> to<09:57:48.840> have<09:57:49.020> it 09:57:49.190 --> 09:57:49.200 align:start position:0% nobody thought that we needed to have it 09:57:49.200 --> 09:57:50.406 align:start position:0% nobody thought that we needed to have it built<09:57:49.560> in 09:57:50.406 --> 09:57:50.416 align:start position:0% built in 09:57:50.416 --> 09:57:53.230 align:start position:0% built in ipv4<09:57:51.416> is<09:57:51.660> hard<09:57:51.840> to<09:57:51.960> use<09:57:52.140> with<09:57:52.256> mobile<09:57:52.500> devices 09:57:53.230 --> 09:57:53.240 align:start position:0% ipv4 is hard to use with mobile devices 09:57:53.240 --> 09:57:55.670 align:start position:0% ipv4 is hard to use with mobile devices especially<09:57:54.240> when<09:57:54.776> we're<09:57:54.900> using<09:57:55.200> the<09:57:55.320> cellular 09:57:55.670 --> 09:57:55.680 align:start position:0% especially when we're using the cellular 09:57:55.680 --> 09:57:59.290 align:start position:0% especially when we're using the cellular Networks 09:57:59.290 --> 09:57:59.300 align:start position:0% 09:57:59.300 --> 09:58:01.790 align:start position:0% ipv4<09:58:00.300> needs<09:58:00.776> massive<09:58:01.080> writing<09:58:01.436> tables 09:58:01.790 --> 09:58:01.800 align:start position:0% ipv4 needs massive writing tables 09:58:01.800 --> 09:58:03.110 align:start position:0% ipv4 needs massive writing tables required<09:58:02.220> over<09:58:02.340> the<09:58:02.580> internet<09:58:02.700> internet 09:58:03.110 --> 09:58:03.120 align:start position:0% required over the internet internet 09:58:03.120 --> 09:58:05.990 align:start position:0% required over the internet internet service<09:58:03.540> providers<09:58:04.140> have<09:58:04.436> huge<09:58:04.800> tables<09:58:05.400> for 09:58:05.990 --> 09:58:06.000 align:start position:0% service providers have huge tables for 09:58:06.000 --> 09:58:08.570 align:start position:0% service providers have huge tables for routing<09:58:06.416> all<09:58:06.540> the<09:58:06.720> IP<09:58:07.020> traffic 09:58:08.570 --> 09:58:08.580 align:start position:0% routing all the IP traffic 09:58:08.580 --> 09:58:10.850 align:start position:0% routing all the IP traffic uh<09:58:09.480> there's<09:58:09.660> only<09:58:09.960> around<09:58:10.200> four<09:58:10.500> million 09:58:10.850 --> 09:58:10.860 align:start position:0% uh there's only around four million 09:58:10.860 --> 09:58:12.830 align:start position:0% uh there's only around four million addresses<09:58:11.276> available<09:58:11.520> we<09:58:12.180> actually<09:58:12.360> ran<09:58:12.720> out 09:58:12.830 --> 09:58:12.840 align:start position:0% addresses available we actually ran out 09:58:12.840 --> 09:58:15.230 align:start position:0% addresses available we actually ran out of<09:58:12.960> ip4<09:58:13.436> addresses<09:58:13.916> some<09:58:14.096> time<09:58:14.276> ago<09:58:14.640> and 09:58:15.230 --> 09:58:15.240 align:start position:0% of ip4 addresses some time ago and 09:58:15.240 --> 09:58:17.810 align:start position:0% of ip4 addresses some time ago and around<09:58:15.416> 50<09:58:15.720> of<09:58:16.200> the<09:58:16.320> traffic<09:58:16.560> going<09:58:17.400> over<09:58:17.640> the 09:58:17.810 --> 09:58:17.820 align:start position:0% around 50 of the traffic going over the 09:58:17.820 --> 09:58:20.510 align:start position:0% around 50 of the traffic going over the internet<09:58:17.936> at<09:58:18.180> the<09:58:18.300> moment<09:58:18.480> is<09:58:18.900> IPv6<09:58:19.800> which<09:58:20.400> is 09:58:20.510 --> 09:58:20.520 align:start position:0% internet at the moment is IPv6 which is 09:58:20.520 --> 09:58:22.550 align:start position:0% internet at the moment is IPv6 which is why<09:58:20.640> yeah<09:58:20.880> we<09:58:21.120> need<09:58:21.240> to<09:58:21.360> know<09:58:21.480> about<09:58:21.660> it 09:58:22.550 --> 09:58:22.560 align:start position:0% why yeah we need to know about it 09:58:22.560 --> 09:58:25.730 align:start position:0% why yeah we need to know about it so<09:58:22.740> IPv6<09:58:23.580> uh<09:58:24.300> there's<09:58:24.480> that<09:58:24.660> many<09:58:24.840> addresses<09:58:25.380> I 09:58:25.730 --> 09:58:25.740 align:start position:0% so IPv6 uh there's that many addresses I 09:58:25.740 --> 09:58:27.586 align:start position:0% so IPv6 uh there's that many addresses I don't<09:58:25.980> even<09:58:26.220> know<09:58:26.520> what<09:58:26.756> the<09:58:27.000> numbering 09:58:27.586 --> 09:58:27.596 align:start position:0% don't even know what the numbering 09:58:27.596 --> 09:58:29.870 align:start position:0% don't even know what the numbering system<09:58:27.840> is<09:58:28.080> called<09:58:28.320> for<09:58:29.160> calling<09:58:29.580> out<09:58:29.700> that 09:58:29.870 --> 09:58:29.880 align:start position:0% system is called for calling out that 09:58:29.880 --> 09:58:33.230 align:start position:0% system is called for calling out that many<09:58:30.060> but<09:58:30.300> for<09:58:30.596> every<09:58:31.020> person<09:58:31.700> alive<09:58:32.700> there's 09:58:33.230 --> 09:58:33.240 align:start position:0% many but for every person alive there's 09:58:33.240 --> 09:58:36.050 align:start position:0% many but for every person alive there's many<09:58:33.660> millions<09:58:34.020> of<09:58:34.200> available<09:58:34.436> addresses<09:58:35.220> now 09:58:36.050 --> 09:58:36.060 align:start position:0% many millions of available addresses now 09:58:36.060 --> 09:58:38.330 align:start position:0% many millions of available addresses now and<09:58:36.300> that<09:58:36.540> can<09:58:36.660> be<09:58:36.840> used<09:58:37.020> with<09:58:37.200> IPv6<09:58:37.980> and 09:58:38.330 --> 09:58:38.340 align:start position:0% and that can be used with IPv6 and 09:58:38.340 --> 09:58:40.610 align:start position:0% and that can be used with IPv6 and you'll<09:58:38.580> read<09:58:38.756> some<09:58:39.120> documents<09:58:39.960> about<09:58:40.140> an<09:58:40.380> app 09:58:40.610 --> 09:58:40.620 align:start position:0% you'll read some documents about an app 09:58:40.620 --> 09:58:44.746 align:start position:0% you'll read some documents about an app PT<09:58:41.040> not<09:58:41.880> really<09:58:42.060> used<09:58:42.360> and<09:58:42.840> there's<09:58:43.020> no<09:58:43.380> need 09:58:44.746 --> 09:58:44.756 align:start position:0% PT not really used and there's no need 09:58:44.756 --> 09:58:46.550 align:start position:0% PT not really used and there's no need two<09:58:45.360> and<09:58:45.596> not<09:58:45.776> because<09:58:45.960> there's<09:58:46.200> just<09:58:46.436> no 09:58:46.550 --> 09:58:46.560 align:start position:0% two and not because there's just no 09:58:46.560 --> 09:58:49.426 align:start position:0% two and not because there's just no shortage<09:58:46.980> of<09:58:47.160> addresses<09:58:47.640> really<09:58:47.960> security<09:58:48.960> is 09:58:49.426 --> 09:58:49.436 align:start position:0% shortage of addresses really security is 09:58:49.436 --> 09:58:51.710 align:start position:0% shortage of addresses really security is built<09:58:49.800> into<09:58:49.860> one<09:58:50.160> of<09:58:50.276> the<09:58:50.340> fields<09:58:50.700> in<09:58:50.936> the<09:58:51.060> IPv6 09:58:51.710 --> 09:58:51.720 align:start position:0% built into one of the fields in the IPv6 09:58:51.720 --> 09:58:54.110 align:start position:0% built into one of the fields in the IPv6 packet 09:58:54.110 --> 09:58:54.120 align:start position:0% packet 09:58:54.120 --> 09:58:57.290 align:start position:0% packet we<09:58:54.480> have<09:58:54.596> addressed<09:58:54.900> Auto<09:58:55.500> configuration 09:58:57.290 --> 09:58:57.300 align:start position:0% we have addressed Auto configuration 09:58:57.300 --> 09:59:01.010 align:start position:0% we have addressed Auto configuration which<09:58:58.080> um<09:58:58.080> is<09:58:58.436> a<09:58:58.680> major<09:58:59.040> part<09:58:59.340> of<09:58:59.520> IPv6 09:59:01.010 --> 09:59:01.020 align:start position:0% which um is a major part of IPv6 09:59:01.020 --> 09:59:03.530 align:start position:0% which um is a major part of IPv6 and<09:59:01.380> it's<09:59:01.500> plug<09:59:01.740> and<09:59:01.916> play<09:59:02.096> as<09:59:02.340> well<09:59:02.520> so<09:59:03.240> things 09:59:03.530 --> 09:59:03.540 align:start position:0% and it's plug and play as well so things 09:59:03.540 --> 09:59:05.570 align:start position:0% and it's plug and play as well so things like<09:59:03.720> when<09:59:03.960> you<09:59:04.080> enable<09:59:04.320> IPv6<09:59:05.160> on<09:59:05.400> an 09:59:05.570 --> 09:59:05.580 align:start position:0% like when you enable IPv6 on an 09:59:05.580 --> 09:59:09.230 align:start position:0% like when you enable IPv6 on an interface<09:59:06.000> with<09:59:06.596> most<09:59:06.900> devices<09:59:07.740> now<09:59:08.240> it 09:59:09.230 --> 09:59:09.240 align:start position:0% interface with most devices now it 09:59:09.240 --> 09:59:13.490 align:start position:0% interface with most devices now it actually<09:59:09.540> self-configures<09:59:10.380> an<09:59:10.620> IPv6<09:59:11.276> address 09:59:13.490 --> 09:59:13.500 align:start position:0% actually self-configures an IPv6 address 09:59:13.500 --> 09:59:16.010 align:start position:0% actually self-configures an IPv6 address we<09:59:13.980> do<09:59:14.160> not<09:59:14.340> have<09:59:14.460> broadcast<09:59:14.700> and<09:59:15.120> IPv6<09:59:15.720> we'll 09:59:16.010 --> 09:59:16.020 align:start position:0% we do not have broadcast and IPv6 we'll 09:59:16.020 --> 09:59:17.690 align:start position:0% we do not have broadcast and IPv6 we'll come<09:59:16.200> to<09:59:16.320> that<09:59:16.436> later 09:59:17.690 --> 09:59:17.700 align:start position:0% come to that later 09:59:17.700 --> 09:59:20.510 align:start position:0% come to that later uh<09:59:18.360> it's<09:59:18.480> built<09:59:18.960> to<09:59:19.020> work<09:59:19.380> plug<09:59:19.860> and<09:59:20.040> play<09:59:20.220> with 09:59:20.510 --> 09:59:20.520 align:start position:0% uh it's built to work plug and play with 09:59:20.520 --> 09:59:23.450 align:start position:0% uh it's built to work plug and play with mobile<09:59:20.700> devices<09:59:21.300> again<09:59:21.776> which<09:59:22.140> is<09:59:22.256> Handy 09:59:23.450 --> 09:59:23.460 align:start position:0% mobile devices again which is Handy 09:59:23.460 --> 09:59:25.906 align:start position:0% mobile devices again which is Handy so<09:59:23.880> the<09:59:24.120> address<09:59:24.240> is<09:59:24.596> there's<09:59:24.840> several<09:59:25.140> rfcs 09:59:25.906 --> 09:59:25.916 align:start position:0% so the address is there's several rfcs 09:59:25.916 --> 09:59:28.790 align:start position:0% so the address is there's several rfcs one<09:59:26.160> of<09:59:26.276> the<09:59:26.276> main<09:59:26.460> ones<09:59:26.700> is<09:59:27.320> 1884<09:59:28.320> if<09:59:28.620> you<09:59:28.740> want 09:59:28.790 --> 09:59:28.800 align:start position:0% one of the main ones is 1884 if you want 09:59:28.800 --> 09:59:32.746 align:start position:0% one of the main ones is 1884 if you want to<09:59:28.980> read<09:59:29.096> it<09:59:29.276> it's<09:59:30.060> a<09:59:30.300> 128<09:59:31.080> bits<09:59:31.740> each<09:59:32.400> of<09:59:32.580> these 09:59:32.746 --> 09:59:32.756 align:start position:0% to read it it's a 128 bits each of these 09:59:32.756 --> 09:59:35.086 align:start position:0% to read it it's a 128 bits each of these bits<09:59:33.000> is<09:59:33.180> divided<09:59:33.660> into<09:59:33.776> into<09:59:34.256> eight<09:59:34.680> groups 09:59:35.086 --> 09:59:35.096 align:start position:0% bits is divided into into eight groups 09:59:35.096 --> 09:59:37.906 align:start position:0% bits is divided into into eight groups of<09:59:35.276> 16<09:59:35.520> bits<09:59:36.180> and<09:59:36.900> then<09:59:37.020> each<09:59:37.256> of<09:59:37.380> those<09:59:37.500> bits 09:59:37.906 --> 09:59:37.916 align:start position:0% of 16 bits and then each of those bits 09:59:37.916 --> 09:59:41.630 align:start position:0% of 16 bits and then each of those bits is<09:59:38.096> separated<09:59:38.820> by<09:59:39.180> a<09:59:39.300> colon<09:59:39.720> which<09:59:40.080> is<09:59:40.256> a<09:59:40.860> DOT 09:59:41.630 --> 09:59:41.640 align:start position:0% is separated by a colon which is a DOT 09:59:41.640 --> 09:59:43.190 align:start position:0% is separated by a colon which is a DOT on<09:59:41.756> top<09:59:41.936> of<09:59:42.060> a<09:59:42.240> dart 09:59:43.190 --> 09:59:43.200 align:start position:0% on top of a dart 09:59:43.200 --> 09:59:45.650 align:start position:0% on top of a dart HEX<09:59:43.740> number<09:59:43.980> it<09:59:44.220> is<09:59:44.400> used<09:59:44.700> because<09:59:45.060> it's<09:59:45.416> just 09:59:45.650 --> 09:59:45.660 align:start position:0% HEX number it is used because it's just 09:59:45.660 --> 09:59:48.650 align:start position:0% HEX number it is used because it's just a<09:59:45.840> lot<09:59:46.020> easier<09:59:46.560> to<09:59:46.980> write<09:59:47.520> out<09:59:47.756> that<09:59:48.060> many<09:59:48.240> bits 09:59:48.650 --> 09:59:48.660 align:start position:0% a lot easier to write out that many bits 09:59:48.660 --> 09:59:51.586 align:start position:0% a lot easier to write out that many bits using<09:59:49.020> hex<09:59:49.320> and<09:59:49.500> it<09:59:49.680> is<09:59:49.860> in<09:59:50.340> um<09:59:50.340> binary<09:59:51.060> it 09:59:51.586 --> 09:59:51.596 align:start position:0% using hex and it is in um binary it 09:59:51.596 --> 09:59:53.086 align:start position:0% using hex and it is in um binary it would<09:59:51.776> take<09:59:51.900> forever 09:59:53.086 --> 09:59:53.096 align:start position:0% would take forever 09:59:53.096 --> 09:59:54.650 align:start position:0% would take forever the<09:59:53.580> address<09:59:53.700> is<09:59:53.936> when<09:59:54.120> you're<09:59:54.240> typing<09:59:54.540> them 09:59:54.650 --> 09:59:54.660 align:start position:0% the address is when you're typing them 09:59:54.660 --> 09:59:56.810 align:start position:0% the address is when you're typing them out<09:59:54.840> on<09:59:54.960> interfaces<09:59:55.560> is<09:59:55.680> not<09:59:56.096> case<09:59:56.276> sensitive 09:59:56.810 --> 09:59:56.820 align:start position:0% out on interfaces is not case sensitive 09:59:56.820 --> 09:59:59.450 align:start position:0% out on interfaces is not case sensitive so<09:59:57.060> you<09:59:57.300> could<09:59:57.360> use<09:59:57.596> caps<09:59:58.080> lock<09:59:58.200> or<09:59:58.620> lowercase 09:59:59.450 --> 09:59:59.460 align:start position:0% so you could use caps lock or lowercase 09:59:59.460 --> 10:00:01.670 align:start position:0% so you could use caps lock or lowercase and<09:59:59.700> the<09:59:59.880> address<10:00:00.000> will<10:00:00.300> work<10:00:01.020> fine<10:00:01.256> and<10:00:01.500> be 10:00:01.670 --> 10:00:01.680 align:start position:0% and the address will work fine and be 10:00:01.680 --> 10:00:02.810 align:start position:0% and the address will work fine and be accepted 10:00:02.810 --> 10:00:02.820 align:start position:0% accepted 10:00:02.820 --> 10:00:06.050 align:start position:0% accepted here<10:00:03.360> is<10:00:03.540> an<10:00:03.840> example<10:00:04.140> of<10:00:04.500> an<10:00:04.740> IPv6<10:00:05.400> and<10:00:05.820> you 10:00:06.050 --> 10:00:06.060 align:start position:0% here is an example of an IPv6 and you 10:00:06.060 --> 10:00:07.670 align:start position:0% here is an example of an IPv6 and you can<10:00:06.180> see 10:00:07.670 --> 10:00:07.680 align:start position:0% can see 10:00:07.680 --> 10:00:09.766 align:start position:0% can see if<10:00:08.040> we<10:00:08.160> just<10:00:08.340> come<10:00:08.460> over<10:00:08.640> here 10:00:09.766 --> 10:00:09.776 align:start position:0% if we just come over here 10:00:09.776 --> 10:00:12.170 align:start position:0% if we just come over here so<10:00:10.320> eight<10:00:10.620> groups<10:00:10.980> of<10:00:11.160> 16<10:00:11.340> bits<10:00:11.820> which<10:00:11.936> you'll 10:00:12.170 --> 10:00:12.180 align:start position:0% so eight groups of 16 bits which you'll 10:00:12.180 --> 10:00:15.766 align:start position:0% so eight groups of 16 bits which you'll go<10:00:12.300> into<10:00:12.416> into<10:00:12.960> a<10:00:13.256> minute<10:00:13.520> uh<10:00:14.520> divided<10:00:15.060> here<10:00:15.300> by 10:00:15.766 --> 10:00:15.776 align:start position:0% go into into a minute uh divided here by 10:00:15.776 --> 10:00:21.610 align:start position:0% go into into a minute uh divided here by the<10:00:15.900> colon<10:00:16.320> and<10:00:16.740> another<10:00:17.660> 16<10:00:18.660> bit<10:00:19.020> 16<10:00:19.500> 16<10:00:19.980> 16<10:00:20.096> 16 10:00:21.610 --> 10:00:21.620 align:start position:0% the colon and another 16 bit 16 16 16 16 10:00:21.620 --> 10:00:29.406 align:start position:0% the colon and another 16 bit 16 16 16 16 and<10:00:22.620> so<10:00:22.740> on 10:00:29.406 --> 10:00:29.416 align:start position:0% 10:00:29.416 --> 10:00:32.630 align:start position:0% so<10:00:30.416> if<10:00:30.840> you<10:00:31.080> wrote<10:00:31.256> the<10:00:31.620> address<10:00:32.040> out<10:00:32.400> in 10:00:32.630 --> 10:00:32.640 align:start position:0% so if you wrote the address out in 10:00:32.640 --> 10:00:35.990 align:start position:0% so if you wrote the address out in binary<10:00:33.060> just<10:00:33.596> for<10:00:33.900> the 10:00:35.990 --> 10:00:36.000 align:start position:0% binary just for the 10:00:36.000 --> 10:00:38.266 align:start position:0% binary just for the I<10:00:36.720> don't<10:00:36.900> know<10:00:37.080> why<10:00:37.256> I<10:00:37.380> should<10:00:37.620> have<10:00:37.800> said<10:00:37.980> D 10:00:38.266 --> 10:00:38.276 align:start position:0% I don't know why I should have said D 10:00:38.276 --> 10:00:43.850 align:start position:0% I don't know why I should have said D here<10:00:38.520> sorry<10:00:39.020> Eed<10:00:40.096> e<10:00:41.096> e<10:00:41.160> d<10:00:41.756> e 10:00:43.850 --> 10:00:43.860 align:start position:0% here sorry Eed e e d e 10:00:43.860 --> 10:00:47.510 align:start position:0% here sorry Eed e e d e but<10:00:44.400> if<10:00:44.820> you<10:00:45.180> change<10:00:46.020> the<10:00:46.320> hexadecimal<10:00:47.276> here 10:00:47.510 --> 10:00:47.520 align:start position:0% but if you change the hexadecimal here 10:00:47.520 --> 10:00:49.550 align:start position:0% but if you change the hexadecimal here so<10:00:47.880> this<10:00:48.120> is<10:00:48.240> the<10:00:48.540> hex 10:00:49.550 --> 10:00:49.560 align:start position:0% so this is the hex 10:00:49.560 --> 10:00:53.390 align:start position:0% so this is the hex into<10:00:50.040> the<10:00:50.276> binary<10:00:50.640> value<10:00:51.020> it's<10:00:52.020> one<10:00:52.320> in<10:00:52.680> the<10:00:52.860> uh 10:00:53.390 --> 10:00:53.400 align:start position:0% into the binary value it's one in the uh 10:00:53.400 --> 10:00:55.490 align:start position:0% into the binary value it's one in the uh if<10:00:53.640> I<10:00:53.820> go<10:00:54.060> one 10:00:55.490 --> 10:00:55.500 align:start position:0% if I go one 10:00:55.500 --> 10:00:58.490 align:start position:0% if I go one to<10:00:56.400> I<10:00:56.640> know<10:00:56.820> you<10:00:56.936> already<10:00:57.060> know<10:00:57.360> how<10:00:57.900> um<10:00:57.900> binary 10:00:58.490 --> 10:00:58.500 align:start position:0% to I know you already know how um binary 10:00:58.500 --> 10:01:02.086 align:start position:0% to I know you already know how um binary works<10:00:58.980> for<10:00:59.540> eight<10:01:00.540> so<10:01:01.380> one<10:01:01.680> in<10:01:01.916> the<10:01:01.980> eight 10:01:02.086 --> 10:01:02.096 align:start position:0% works for eight so one in the eight 10:01:02.096 --> 10:01:04.070 align:start position:0% works for eight so one in the eight column<10:01:02.400> one<10:01:02.580> in<10:01:02.756> the<10:01:02.880> four<10:01:03.000> one<10:01:03.240> in<10:01:03.480> the<10:01:03.596> two<10:01:03.776> so 10:01:04.070 --> 10:01:04.080 align:start position:0% column one in the four one in the two so 10:01:04.080 --> 10:01:06.290 align:start position:0% column one in the four one in the two so eight<10:01:04.436> plus<10:01:04.680> four 10:01:06.290 --> 10:01:06.300 align:start position:0% eight plus four 10:01:06.300 --> 10:01:09.586 align:start position:0% eight plus four uh<10:01:07.020> it's<10:01:07.140> twelve<10:01:07.800> eight<10:01:08.640> nine<10:01:08.880> ten<10:01:09.180> eleven 10:01:09.586 --> 10:01:09.596 align:start position:0% uh it's twelve eight nine ten eleven 10:01:09.596 --> 10:01:13.670 align:start position:0% uh it's twelve eight nine ten eleven twelve<10:01:09.900> thirteen<10:01:10.256> at<10:01:10.500> fourteen<10:01:11.060> so<10:01:12.060> the<10:01:12.480> E<10:01:12.776> is 10:01:13.670 --> 10:01:13.680 align:start position:0% twelve thirteen at fourteen so the E is 10:01:13.680 --> 10:01:16.190 align:start position:0% twelve thirteen at fourteen so the E is number<10:01:14.096> fourteen 10:01:16.190 --> 10:01:16.200 align:start position:0% number fourteen 10:01:16.200 --> 10:01:20.510 align:start position:0% number fourteen here<10:01:16.860> uh<10:01:17.756> 14<10:01:18.540> here<10:01:19.200> in<10:01:19.500> HEX 10:01:20.510 --> 10:01:20.520 align:start position:0% here uh 14 here in HEX 10:01:20.520 --> 10:01:25.190 align:start position:0% here uh 14 here in HEX now<10:01:20.936> we've<10:01:21.180> got<10:01:21.360> the<10:01:21.596> D<10:01:21.900> so<10:01:22.436> we've<10:01:22.740> got<10:01:23.096> uh<10:01:23.756> one 10:01:25.190 --> 10:01:25.200 align:start position:0% now we've got the D so we've got uh one 10:01:25.200 --> 10:01:29.926 align:start position:0% now we've got the D so we've got uh one plus<10:01:26.240> four<10:01:27.240> plus<10:01:27.900> eight<10:01:28.380> so<10:01:29.040> eight<10:01:29.400> nine<10:01:29.700> ten 10:01:29.926 --> 10:01:29.936 align:start position:0% plus four plus eight so eight nine ten 10:01:29.936 --> 10:01:31.990 align:start position:0% plus four plus eight so eight nine ten eleven<10:01:30.416> twelve 10:01:31.990 --> 10:01:32.000 align:start position:0% eleven twelve 10:01:32.000 --> 10:01:36.650 align:start position:0% eleven twelve thirteen<10:01:33.000> so<10:01:33.900> D<10:01:34.256> is<10:01:34.560> 13. 10:01:36.650 --> 10:01:36.660 align:start position:0% thirteen so D is 13. 10:01:36.660 --> 10:01:39.586 align:start position:0% thirteen so D is 13. and<10:01:37.140> then<10:01:37.200> we're<10:01:37.380> back<10:01:37.560> to<10:01:37.680> another<10:01:37.800> 14.<10:01:38.756> 16 10:01:39.586 --> 10:01:39.596 align:start position:0% and then we're back to another 14. 16 10:01:39.596 --> 10:01:43.490 align:start position:0% and then we're back to another 14. 16 bits<10:01:40.140> two<10:01:40.380> bytes<10:01:40.860> in<10:01:41.096> total<10:01:41.400> so<10:01:41.756> four<10:01:42.060> bits 10:01:43.490 --> 10:01:43.500 align:start position:0% bits two bytes in total so four bits 10:01:43.500 --> 10:01:45.710 align:start position:0% bits two bytes in total so four bits uh<10:01:44.040> four<10:01:44.220> bits<10:01:44.640> eight<10:01:44.880> and<10:01:45.360> then<10:01:45.480> another 10:01:45.710 --> 10:01:45.720 align:start position:0% uh four bits eight and then another 10:01:45.720 --> 10:01:50.030 align:start position:0% uh four bits eight and then another eight<10:01:46.140> 16<10:01:46.620> bits<10:01:47.220> so<10:01:47.580> that's<10:01:47.756> two<10:01:48.000> bytes 10:01:50.030 --> 10:01:50.040 align:start position:0% eight 16 bits so that's two bytes 10:01:50.040 --> 10:01:52.550 align:start position:0% eight 16 bits so that's two bytes we<10:01:50.520> can<10:01:50.640> compress<10:01:51.060> the<10:01:51.360> address 10:01:52.550 --> 10:01:52.560 align:start position:0% we can compress the address 10:01:52.560 --> 10:01:54.970 align:start position:0% we can compress the address so<10:01:52.980> you<10:01:53.276> can<10:01:53.340> remove<10:01:53.580> the<10:01:54.000> leading<10:01:54.360> zeros 10:01:54.970 --> 10:01:54.980 align:start position:0% so you can remove the leading zeros 10:01:54.980 --> 10:01:58.970 align:start position:0% so you can remove the leading zeros leading<10:01:55.980> zeros<10:01:56.580> are<10:01:57.480> numbers<10:01:58.080> that<10:01:58.436> appear 10:01:58.970 --> 10:01:58.980 align:start position:0% leading zeros are numbers that appear 10:01:58.980 --> 10:02:02.406 align:start position:0% leading zeros are numbers that appear before<10:01:59.360> and<10:02:00.360> so<10:02:00.596> this<10:02:00.900> is<10:02:01.080> a<10:02:01.320> leading<10:02:01.800> zero 10:02:02.406 --> 10:02:02.416 align:start position:0% before and so this is a leading zero 10:02:02.416 --> 10:02:06.170 align:start position:0% before and so this is a leading zero leading<10:02:03.416> zero<10:02:03.900> this<10:02:04.500> is<10:02:04.620> a<10:02:04.916> trailing<10:02:05.400> zero<10:02:05.936> so 10:02:06.170 --> 10:02:06.180 align:start position:0% leading zero this is a trailing zero so 10:02:06.180 --> 10:02:08.510 align:start position:0% leading zero this is a trailing zero so we<10:02:06.480> can't<10:02:06.660> remove<10:02:07.436> these<10:02:07.916> because<10:02:08.096> they've 10:02:08.510 --> 10:02:08.520 align:start position:0% we can't remove these because they've 10:02:08.520 --> 10:02:12.766 align:start position:0% we can't remove these because they've got<10:02:08.700> numbers<10:02:09.740> uh<10:02:10.740> prior<10:02:11.040> just<10:02:11.340> before<10:02:11.660> so<10:02:12.660> if 10:02:12.766 --> 10:02:12.776 align:start position:0% got numbers uh prior just before so if 10:02:12.776 --> 10:02:15.530 align:start position:0% got numbers uh prior just before so if we<10:02:12.900> get<10:02:13.080> rid<10:02:13.200> of<10:02:13.380> the<10:02:13.640> leading<10:02:14.640> zeros<10:02:15.180> for 10:02:15.530 --> 10:02:15.540 align:start position:0% we get rid of the leading zeros for 10:02:15.540 --> 10:02:18.950 align:start position:0% we get rid of the leading zeros for example<10:02:15.840> here<10:02:16.200> zero<10:02:17.096> zero<10:02:17.580> zero<10:02:18.360> one<10:02:18.540> becomes 10:02:18.950 --> 10:02:18.960 align:start position:0% example here zero zero zero one becomes 10:02:18.960 --> 10:02:20.210 align:start position:0% example here zero zero zero one becomes a<10:02:19.140> one 10:02:20.210 --> 10:02:20.220 align:start position:0% a one 10:02:20.220 --> 10:02:22.370 align:start position:0% a one zero<10:02:21.000> seven<10:02:21.120> eight<10:02:21.416> nine<10:02:21.720> becomes<10:02:22.140> seven 10:02:22.370 --> 10:02:22.380 align:start position:0% zero seven eight nine becomes seven 10:02:22.380 --> 10:02:26.210 align:start position:0% zero seven eight nine becomes seven eight<10:02:22.620> nine<10:02:22.860> and<10:02:23.820> this<10:02:24.060> is<10:02:24.240> uh<10:02:24.480> to<10:02:24.720> save<10:02:24.960> space 10:02:26.210 --> 10:02:26.220 align:start position:0% eight nine and this is uh to save space 10:02:26.220 --> 10:02:27.890 align:start position:0% eight nine and this is uh to save space and<10:02:26.700> for<10:02:26.820> when<10:02:27.000> we're<10:02:27.180> writing<10:02:27.596> out<10:02:27.720> the 10:02:27.890 --> 10:02:27.900 align:start position:0% and for when we're writing out the 10:02:27.900 --> 10:02:31.370 align:start position:0% and for when we're writing out the address<10:02:28.020> is<10:02:28.320> zero<10:02:28.800> ABC<10:02:29.276> becomes<10:02:29.936> ABC<10:02:30.480> and<10:02:31.256> you 10:02:31.370 --> 10:02:31.380 align:start position:0% address is zero ABC becomes ABC and you 10:02:31.380 --> 10:02:33.170 align:start position:0% address is zero ABC becomes ABC and you can<10:02:31.500> get<10:02:31.680> rid<10:02:31.860> of<10:02:31.980> the<10:02:32.220> trailing<10:02:32.580> zeros<10:02:32.936> here 10:02:33.170 --> 10:02:33.180 align:start position:0% can get rid of the trailing zeros here 10:02:33.180 --> 10:02:35.390 align:start position:0% can get rid of the trailing zeros here and<10:02:33.360> just<10:02:33.596> have<10:02:33.720> one<10:02:34.020> zero<10:02:34.436> so<10:02:35.040> this<10:02:35.220> address 10:02:35.390 --> 10:02:35.400 align:start position:0% and just have one zero so this address 10:02:35.400 --> 10:02:38.990 align:start position:0% and just have one zero so this address is<10:02:36.000> uh<10:02:36.416> legal 10:02:38.990 --> 10:02:39.000 align:start position:0% 10:02:39.000 --> 10:02:40.670 align:start position:0% to<10:02:39.300> write<10:02:39.416> that<10:02:39.596> out<10:02:39.720> you<10:02:40.080> could<10:02:40.200> possibly 10:02:40.670 --> 10:02:40.680 align:start position:0% to write that out you could possibly 10:02:40.680 --> 10:02:43.130 align:start position:0% to write that out you could possibly have<10:02:40.860> questions<10:02:41.096> in<10:02:41.400> the<10:02:41.520> exam<10:02:41.820> uh<10:02:42.660> asking<10:02:43.020> you 10:02:43.130 --> 10:02:43.140 align:start position:0% have questions in the exam uh asking you 10:02:43.140 --> 10:02:45.650 align:start position:0% have questions in the exam uh asking you to<10:02:43.380> choose<10:02:43.620> the<10:02:43.860> correct<10:02:44.040> compressed<10:02:44.640> address 10:02:45.650 --> 10:02:45.660 align:start position:0% to choose the correct compressed address 10:02:45.660 --> 10:02:48.490 align:start position:0% to choose the correct compressed address you<10:02:46.140> can<10:02:46.256> use<10:02:46.436> a<10:02:46.680> double<10:02:46.800> colon 10:02:48.490 --> 10:02:48.500 align:start position:0% you can use a double colon 10:02:48.500 --> 10:02:52.130 align:start position:0% you can use a double colon wants<10:02:49.500> to<10:02:49.620> represent<10:02:49.980> consecutive<10:02:50.580> zeros<10:02:51.180> so 10:02:52.130 --> 10:02:52.140 align:start position:0% wants to represent consecutive zeros so 10:02:52.140 --> 10:02:54.650 align:start position:0% wants to represent consecutive zeros so here<10:02:52.380> we<10:02:52.620> go<10:02:52.860> we've<10:02:53.756> got<10:02:53.936> all<10:02:54.240> these 10:02:54.650 --> 10:02:54.660 align:start position:0% here we go we've got all these 10:02:54.660 --> 10:02:56.926 align:start position:0% here we go we've got all these consecutive<10:02:55.320> zeros<10:02:55.860> here<10:02:56.160> for<10:02:56.520> some<10:02:56.700> reason 10:02:56.926 --> 10:02:56.936 align:start position:0% consecutive zeros here for some reason 10:02:56.936 --> 10:02:59.450 align:start position:0% consecutive zeros here for some reason well<10:02:57.900> we've<10:02:58.140> got<10:02:58.320> rid<10:02:58.500> of<10:02:58.680> them<10:02:58.800> just<10:02:59.276> by 10:02:59.450 --> 10:02:59.460 align:start position:0% well we've got rid of them just by 10:02:59.460 --> 10:03:02.330 align:start position:0% well we've got rid of them just by having<10:02:59.700> the<10:03:00.120> double<10:03:00.596> curl<10:03:01.080> on<10:03:01.200> here 10:03:02.330 --> 10:03:02.340 align:start position:0% having the double curl on here 10:03:02.340 --> 10:03:04.310 align:start position:0% having the double curl on here and<10:03:02.880> we've<10:03:03.120> got<10:03:03.240> a<10:03:03.360> double<10:03:03.480> coal<10:03:03.960> on<10:03:04.080> here 10:03:04.310 --> 10:03:04.320 align:start position:0% and we've got a double coal on here 10:03:04.320 --> 10:03:06.586 align:start position:0% and we've got a double coal on here between<10:03:04.680> the<10:03:04.980> one<10:03:05.096> two<10:03:05.276> three<10:03:05.520> four 10:03:06.586 --> 10:03:06.596 align:start position:0% between the one two three four 10:03:06.596 --> 10:03:08.990 align:start position:0% between the one two three four so<10:03:06.960> what<10:03:07.256> we've<10:03:07.500> done<10:03:07.740> is<10:03:07.980> just<10:03:08.220> compress<10:03:08.640> all 10:03:08.990 --> 10:03:09.000 align:start position:0% so what we've done is just compress all 10:03:09.000 --> 10:03:11.450 align:start position:0% so what we've done is just compress all of<10:03:09.120> these<10:03:09.300> zeros<10:03:09.720> and<10:03:10.620> we've<10:03:10.860> done<10:03:11.040> it<10:03:11.220> again 10:03:11.450 --> 10:03:11.460 align:start position:0% of these zeros and we've done it again 10:03:11.460 --> 10:03:15.170 align:start position:0% of these zeros and we've done it again here 10:03:15.170 --> 10:03:15.180 align:start position:0% 10:03:15.180 --> 10:03:17.870 align:start position:0% and<10:03:15.840> then<10:03:16.020> just<10:03:16.500> to<10:03:16.860> we<10:03:17.276> could<10:03:17.400> have<10:03:17.580> put<10:03:17.700> it<10:03:17.756> in 10:03:17.870 --> 10:03:17.880 align:start position:0% and then just to we could have put it in 10:03:17.880 --> 10:03:19.906 align:start position:0% and then just to we could have put it in the<10:03:18.060> second<10:03:18.240> set<10:03:18.480> of<10:03:18.660> zeros<10:03:19.020> but<10:03:19.256> just<10:03:19.436> to<10:03:19.680> save 10:03:19.906 --> 10:03:19.916 align:start position:0% the second set of zeros but just to save 10:03:19.916 --> 10:03:22.426 align:start position:0% the second set of zeros but just to save space<10:03:20.276> we've<10:03:21.120> got<10:03:21.300> rid<10:03:21.480> of<10:03:21.660> all<10:03:21.776> these<10:03:22.020> zeros 10:03:22.426 --> 10:03:22.436 align:start position:0% space we've got rid of all these zeros 10:03:22.436 --> 10:03:23.690 align:start position:0% space we've got rid of all these zeros here 10:03:23.690 --> 10:03:23.700 align:start position:0% here 10:03:23.700 --> 10:03:26.210 align:start position:0% here so<10:03:24.240> practice<10:03:24.540> this<10:03:25.020> work<10:03:25.740> out<10:03:25.916> your<10:03:26.096> own 10:03:26.210 --> 10:03:26.220 align:start position:0% so practice this work out your own 10:03:26.220 --> 10:03:28.190 align:start position:0% so practice this work out your own numbers<10:03:26.460> because<10:03:26.880> this<10:03:27.240> is<10:03:27.360> a<10:03:27.596> typical<10:03:27.840> exam 10:03:28.190 --> 10:03:28.200 align:start position:0% numbers because this is a typical exam 10:03:28.200 --> 10:03:29.510 align:start position:0% numbers because this is a typical exam type<10:03:28.436> question 10:03:29.510 --> 10:03:29.520 align:start position:0% type question 10:03:29.520 --> 10:03:30.790 align:start position:0% type question main 10:03:30.790 --> 10:03:30.800 align:start position:0% main 10:03:30.800 --> 10:03:34.426 align:start position:0% main IPv6<10:03:31.800> address<10:03:32.220> types<10:03:32.756> Global<10:03:33.060> unicast<10:03:33.596> unique 10:03:34.426 --> 10:03:34.436 align:start position:0% IPv6 address types Global unicast unique 10:03:34.436 --> 10:03:37.790 align:start position:0% IPv6 address types Global unicast unique local<10:03:34.740> link<10:03:35.700> local<10:03:36.120> and<10:03:37.020> multicast<10:03:37.560> you'll 10:03:37.790 --> 10:03:37.800 align:start position:0% local link local and multicast you'll 10:03:37.800 --> 10:03:39.530 align:start position:0% local link local and multicast you'll note<10:03:37.980> we<10:03:38.160> don't<10:03:38.276> have<10:03:38.460> broadcast<10:03:38.700> that<10:03:39.240> isn't 10:03:39.530 --> 10:03:39.540 align:start position:0% note we don't have broadcast that isn't 10:03:39.540 --> 10:03:41.570 align:start position:0% note we don't have broadcast that isn't a<10:03:39.660> legal<10:03:39.900> address<10:03:40.080> and<10:03:40.980> we<10:03:41.096> also<10:03:41.340> have<10:03:41.400> any 10:03:41.570 --> 10:03:41.580 align:start position:0% a legal address and we also have any 10:03:41.580 --> 10:03:43.130 align:start position:0% a legal address and we also have any cast<10:03:41.880> which<10:03:42.240> I'm<10:03:42.360> not<10:03:42.480> sure<10:03:42.596> if<10:03:42.660> I<10:03:42.840> mentioned 10:03:43.130 --> 10:03:43.140 align:start position:0% cast which I'm not sure if I mentioned 10:03:43.140 --> 10:03:44.510 align:start position:0% cast which I'm not sure if I mentioned here 10:03:44.510 --> 10:03:44.520 align:start position:0% here 10:03:44.520 --> 10:03:47.390 align:start position:0% here so<10:03:45.180> the<10:03:45.416> global<10:03:45.660> unicast<10:03:46.320> the<10:03:46.916> this<10:03:47.220> is 10:03:47.390 --> 10:03:47.400 align:start position:0% so the global unicast the this is 10:03:47.400 --> 10:03:49.610 align:start position:0% so the global unicast the this is allocated<10:03:47.880> by<10:03:48.180> the<10:03:48.360> ISP<10:03:48.900> and<10:03:49.200> then<10:03:49.380> you<10:03:49.500> will 10:03:49.610 --> 10:03:49.620 align:start position:0% allocated by the ISP and then you will 10:03:49.620 --> 10:03:52.426 align:start position:0% allocated by the ISP and then you will get<10:03:49.860> a<10:03:50.096> mask<10:03:50.276> Associated<10:03:51.120> whatever<10:03:51.960> the<10:03:52.256> mask 10:03:52.426 --> 10:03:52.436 align:start position:0% get a mask Associated whatever the mask 10:03:52.436 --> 10:03:56.690 align:start position:0% get a mask Associated whatever the mask may<10:03:52.740> be 10:03:56.690 --> 10:03:56.700 align:start position:0% 10:03:56.700 --> 10:03:58.790 align:start position:0% these<10:03:57.240> are<10:03:57.360> routable<10:03:57.720> on<10:03:57.960> the<10:03:58.080> internet<10:03:58.200> so 10:03:58.790 --> 10:03:58.800 align:start position:0% these are routable on the internet so 10:03:58.800 --> 10:04:02.746 align:start position:0% these are routable on the internet so you<10:03:59.096> can<10:03:59.160> send<10:03:59.400> them<10:03:59.580> out<10:03:59.756> of<10:03:59.936> your<10:04:00.416> company 10:04:02.746 --> 10:04:02.756 align:start position:0% you can send them out of your company 10:04:02.756 --> 10:04:04.550 align:start position:0% you can send them out of your company and<10:04:03.960> um 10:04:04.550 --> 10:04:04.560 align:start position:0% and um 10:04:04.560 --> 10:04:07.790 align:start position:0% and um they're<10:04:05.096> legal<10:04:05.756> they're<10:04:05.936> legally<10:04:06.240> recognized 10:04:07.790 --> 10:04:07.800 align:start position:0% they're legal they're legally recognized 10:04:07.800 --> 10:04:11.330 align:start position:0% they're legal they're legally recognized the<10:04:08.160> numbers<10:04:08.276> range<10:04:08.700> from<10:04:08.880> 2000<10:04:09.660> to<10:04:09.840> 3<10:04:10.140> FFF<10:04:10.680> in 10:04:11.330 --> 10:04:11.340 align:start position:0% the numbers range from 2000 to 3 FFF in 10:04:11.340 --> 10:04:15.050 align:start position:0% the numbers range from 2000 to 3 FFF in the<10:04:11.460> first<10:04:11.640> 16<10:04:11.936> bits 10:04:15.050 --> 10:04:15.060 align:start position:0% 10:04:15.060 --> 10:04:17.330 align:start position:0% current<10:04:15.540> allocation<10:04:16.500> there's<10:04:17.040> there's 10:04:17.330 --> 10:04:17.340 align:start position:0% current allocation there's there's 10:04:17.340 --> 10:04:18.830 align:start position:0% current allocation there's there's trillions<10:04:17.756> of<10:04:17.936> these<10:04:18.120> addresses<10:04:18.480> so<10:04:18.720> the 10:04:18.830 --> 10:04:18.840 align:start position:0% trillions of these addresses so the 10:04:18.840 --> 10:04:21.010 align:start position:0% trillions of these addresses so the current<10:04:18.960> allocation<10:04:19.500> has<10:04:19.740> come<10:04:19.916> in<10:04:20.096> from 10:04:21.010 --> 10:04:21.020 align:start position:0% current allocation has come in from 10:04:21.020 --> 10:04:23.390 align:start position:0% current allocation has come in from 2001.<10:04:22.020> this<10:04:22.436> will<10:04:22.560> this<10:04:22.860> will<10:04:22.980> last<10:04:23.160> quite 10:04:23.390 --> 10:04:23.400 align:start position:0% 2001. this will this will last quite 10:04:23.400 --> 10:04:25.490 align:start position:0% 2001. this will this will last quite some<10:04:23.580> time<10:04:23.756> obviously 10:04:25.490 --> 10:04:25.500 align:start position:0% some time obviously 10:04:25.500 --> 10:04:29.086 align:start position:0% some time obviously there's<10:04:26.040> a<10:04:26.220> 48-bit<10:04:26.880> provider<10:04:27.660> prefix<10:04:28.256> and<10:04:28.916> if 10:04:29.086 --> 10:04:29.096 align:start position:0% there's a 48-bit provider prefix and if 10:04:29.096 --> 10:04:30.650 align:start position:0% there's a 48-bit provider prefix and if you<10:04:29.276> uh<10:04:29.520> check<10:04:29.880> the 10:04:30.650 --> 10:04:30.660 align:start position:0% you uh check the 10:04:30.660 --> 10:04:34.730 align:start position:0% you uh check the images<10:04:31.560> of<10:04:32.040> the<10:04:32.220> address<10:04:33.180> packet<10:04:33.840> you'll<10:04:34.620> see 10:04:34.730 --> 10:04:34.740 align:start position:0% images of the address packet you'll see 10:04:34.740 --> 10:04:38.870 align:start position:0% images of the address packet you'll see the<10:04:34.860> 48-bit<10:04:35.756> uh<10:04:36.300> there's<10:04:36.480> a<10:04:36.596> subnet<10:04:36.960> ID 10:04:38.870 --> 10:04:38.880 align:start position:0% the 48-bit uh there's a subnet ID 10:04:38.880 --> 10:04:40.790 align:start position:0% the 48-bit uh there's a subnet ID you<10:04:39.300> can<10:04:39.360> submit<10:04:39.720> inside<10:04:39.960> the<10:04:40.200> organization 10:04:40.790 --> 10:04:40.800 align:start position:0% you can submit inside the organization 10:04:40.800 --> 10:04:44.570 align:start position:0% you can submit inside the organization if<10:04:41.460> you<10:04:41.640> wish<10:04:41.820> subnet<10:04:42.720> to<10:04:42.840> IPv6<10:04:43.560> is<10:04:44.160> a<10:04:44.276> topic 10:04:44.570 --> 10:04:44.580 align:start position:0% if you wish subnet to IPv6 is a topic 10:04:44.580 --> 10:04:47.510 align:start position:0% if you wish subnet to IPv6 is a topic but<10:04:44.756> it's<10:04:44.936> not<10:04:45.060> in<10:04:45.240> the<10:04:45.360> CompTIA<10:04:45.840> it<10:04:46.680> is<10:04:46.916> in<10:04:47.276> the 10:04:47.510 --> 10:04:47.520 align:start position:0% but it's not in the CompTIA it is in the 10:04:47.520 --> 10:04:50.926 align:start position:0% but it's not in the CompTIA it is in the Cisco<10:04:48.000> ctna<10:04:48.776> and<10:04:49.620> then<10:04:49.740> the<10:04:49.980> rest<10:04:50.160> is<10:04:50.460> the<10:04:50.756> host 10:04:50.926 --> 10:04:50.936 align:start position:0% Cisco ctna and then the rest is the host 10:04:50.936 --> 10:04:54.830 align:start position:0% Cisco ctna and then the rest is the host portion<10:04:51.480> of<10:04:51.660> the<10:04:51.840> address 10:04:54.830 --> 10:04:54.840 align:start position:0% 10:04:54.840 --> 10:04:57.710 align:start position:0% now<10:04:55.680> I'm<10:04:56.096> sure<10:04:56.276> most<10:04:56.936> equipment<10:04:57.360> can<10:04:57.596> actually 10:04:57.710 --> 10:04:57.720 align:start position:0% now I'm sure most equipment can actually 10:04:57.720 --> 10:04:59.510 align:start position:0% now I'm sure most equipment can actually do<10:04:58.020> this<10:04:58.200> but<10:04:58.380> Cisco<10:04:58.800> routers<10:04:59.276> can 10:04:59.510 --> 10:04:59.520 align:start position:0% do this but Cisco routers can 10:04:59.520 --> 10:05:02.810 align:start position:0% do this but Cisco routers can self-generate<10:05:00.300> this<10:05:01.020> part<10:05:01.200> here 10:05:02.810 --> 10:05:02.820 align:start position:0% self-generate this part here 10:05:02.820 --> 10:05:04.670 align:start position:0% self-generate this part here so<10:05:03.416> what<10:05:03.660> you<10:05:03.776> would<10:05:03.900> do<10:05:04.080> is<10:05:04.200> if<10:05:04.320> you<10:05:04.380> configure 10:05:04.670 --> 10:05:04.680 align:start position:0% so what you would do is if you configure 10:05:04.680 --> 10:05:06.230 align:start position:0% so what you would do is if you configure an<10:05:04.860> interface<10:05:05.220> you<10:05:05.460> would<10:05:05.580> you<10:05:05.936> would 10:05:06.230 --> 10:05:06.240 align:start position:0% an interface you would you would 10:05:06.240 --> 10:05:07.970 align:start position:0% an interface you would you would basically<10:05:06.660> configure<10:05:07.140> whatever<10:05:07.436> the<10:05:07.800> address 10:05:07.970 --> 10:05:07.980 align:start position:0% basically configure whatever the address 10:05:07.980 --> 10:05:10.670 align:start position:0% basically configure whatever the address is 10:05:10.670 --> 10:05:10.680 align:start position:0% 10:05:10.680 --> 10:05:13.190 align:start position:0% dot<10:05:11.400> b<10:05:11.520> dot<10:05:12.000> whatever<10:05:12.120> whatever<10:05:12.480> and<10:05:12.900> then<10:05:13.080> the 10:05:13.190 --> 10:05:13.200 align:start position:0% dot b dot whatever whatever and then the 10:05:13.200 --> 10:05:17.330 align:start position:0% dot b dot whatever whatever and then the host<10:05:13.380> portion<10:05:13.980> here<10:05:14.820> the<10:05:15.776> interface<10:05:16.140> would 10:05:17.330 --> 10:05:17.340 align:start position:0% host portion here the interface would 10:05:17.340 --> 10:05:21.050 align:start position:0% host portion here the interface would um<10:05:17.400> self-configure 10:05:21.050 --> 10:05:21.060 align:start position:0% 10:05:21.060 --> 10:05:24.950 align:start position:0% so 10:05:24.950 --> 10:05:24.960 align:start position:0% 10:05:24.960 --> 10:05:27.710 align:start position:0% um<10:05:25.140> I've<10:05:25.916> issued<10:05:26.400> oh<10:05:26.580> this<10:05:26.880> is<10:05:27.000> on<10:05:27.240> my<10:05:27.720> um 10:05:27.710 --> 10:05:27.720 align:start position:0% um I've issued oh this is on my um 10:05:27.720 --> 10:05:29.330 align:start position:0% um I've issued oh this is on my um Windows<10:05:28.200> computer<10:05:28.380> for<10:05:28.740> the<10:05:28.860> looks<10:05:29.096> of<10:05:29.220> it 10:05:29.330 --> 10:05:29.340 align:start position:0% Windows computer for the looks of it 10:05:29.340 --> 10:05:36.170 align:start position:0% Windows computer for the looks of it I've<10:05:30.300> just<10:05:30.480> issued<10:05:30.840> an<10:05:30.960> IP<10:05:31.320> config<10:05:31.980> or 10:05:36.170 --> 10:05:36.180 align:start position:0% 10:05:36.180 --> 10:05:39.406 align:start position:0% forward<10:05:36.900> slash<10:05:37.256> all<10:05:37.560> and<10:05:38.096> I've<10:05:38.340> seen<10:05:38.580> the<10:05:38.756> IPv6 10:05:39.406 --> 10:05:39.416 align:start position:0% forward slash all and I've seen the IPv6 10:05:39.416 --> 10:05:42.890 align:start position:0% forward slash all and I've seen the IPv6 address<10:05:39.720> that's<10:05:40.380> been<10:05:40.560> allocated<10:05:41.040> here<10:05:41.480> and<10:05:42.480> I 10:05:42.890 --> 10:05:42.900 align:start position:0% address that's been allocated here and I 10:05:42.900 --> 10:05:44.690 align:start position:0% address that's been allocated here and I think<10:05:43.080> Windows<10:05:43.680> self-allocates<10:05:44.340> these 10:05:44.690 --> 10:05:44.700 align:start position:0% think Windows self-allocates these 10:05:44.700 --> 10:05:47.406 align:start position:0% think Windows self-allocates these addresses<10:05:45.120> also 10:05:47.406 --> 10:05:47.416 align:start position:0% addresses also 10:05:47.416 --> 10:05:50.390 align:start position:0% addresses also uh<10:05:48.416> link<10:05:48.596> local<10:05:48.840> address<10:05:49.140> the<10:05:49.916> prefix<10:05:50.220> for 10:05:50.390 --> 10:05:50.400 align:start position:0% uh link local address the prefix for 10:05:50.400 --> 10:05:53.690 align:start position:0% uh link local address the prefix for link<10:05:50.520> local<10:05:50.756> addresses<10:05:51.300> are<10:05:51.540> feat<10:05:52.580> these<10:05:53.580> are 10:05:53.690 --> 10:05:53.700 align:start position:0% link local addresses are feat these are 10:05:53.700 --> 10:05:55.370 align:start position:0% link local addresses are feat these are only<10:05:53.820> valid<10:05:54.240> between<10:05:54.416> the<10:05:54.660> link<10:05:54.776> between<10:05:55.020> two 10:05:55.370 --> 10:05:55.380 align:start position:0% only valid between the link between two 10:05:55.380 --> 10:05:58.610 align:start position:0% only valid between the link between two IB<10:05:55.800> V6<10:05:56.276> interfaces<10:05:57.060> so<10:05:57.660> you've<10:05:57.900> got<10:05:58.140> an 10:05:58.610 --> 10:05:58.620 align:start position:0% IB V6 interfaces so you've got an 10:05:58.620 --> 10:06:01.670 align:start position:0% IB V6 interfaces so you've got an internal<10:05:59.096> router<10:06:00.060> and<10:06:00.660> say<10:06:01.080> for<10:06:01.256> example<10:06:01.436> an 10:06:01.670 --> 10:06:01.680 align:start position:0% internal router and say for example an 10:06:01.680 --> 10:06:03.530 align:start position:0% internal router and say for example an ethernet<10:06:02.040> connection<10:06:02.340> here 10:06:03.530 --> 10:06:03.540 align:start position:0% ethernet connection here 10:06:03.540 --> 10:06:06.586 align:start position:0% ethernet connection here then<10:06:04.256> these<10:06:04.680> addresses<10:06:05.096> will<10:06:05.520> be<10:06:05.640> valid<10:06:06.060> and 10:06:06.586 --> 10:06:06.596 align:start position:0% then these addresses will be valid and 10:06:06.596 --> 10:06:12.650 align:start position:0% then these addresses will be valid and these<10:06:07.140> two<10:06:07.520> IPv6<10:06:08.520> routers 10:06:12.650 --> 10:06:12.660 align:start position:0% 10:06:12.660 --> 10:06:15.290 align:start position:0% can<10:06:13.140> communicate<10:06:13.680> with<10:06:13.916> one<10:06:14.040> another<10:06:14.300> using 10:06:15.290 --> 10:06:15.300 align:start position:0% can communicate with one another using 10:06:15.300 --> 10:06:17.810 align:start position:0% can communicate with one another using this<10:06:15.480> link<10:06:15.660> local<10:06:15.900> address<10:06:16.256> what<10:06:17.160> it<10:06:17.340> can't<10:06:17.520> do 10:06:17.810 --> 10:06:17.820 align:start position:0% this link local address what it can't do 10:06:17.820 --> 10:06:20.450 align:start position:0% this link local address what it can't do is<10:06:18.180> this<10:06:18.416> address<10:06:18.540> in<10:06:18.900> here<10:06:19.080> it<10:06:19.740> can't<10:06:19.916> be<10:06:20.160> used 10:06:20.450 --> 10:06:20.460 align:start position:0% is this address in here it can't be used 10:06:20.460 --> 10:06:23.990 align:start position:0% is this address in here it can't be used to<10:06:21.060> reach<10:06:21.360> another<10:06:21.596> device<10:06:22.020> out<10:06:22.380> here 10:06:23.990 --> 10:06:24.000 align:start position:0% to reach another device out here 10:06:24.000 --> 10:06:26.086 align:start position:0% to reach another device out here now<10:06:24.360> if<10:06:24.480> you've<10:06:24.660> got<10:06:24.776> another<10:06:24.960> device<10:06:25.380> the 10:06:26.086 --> 10:06:26.096 align:start position:0% now if you've got another device the 10:06:26.096 --> 10:06:29.330 align:start position:0% now if you've got another device the link<10:06:26.276> local<10:06:26.580> addresses<10:06:27.200> of<10:06:28.200> these<10:06:28.436> two<10:06:28.620> facing 10:06:29.330 --> 10:06:29.340 align:start position:0% link local addresses of these two facing 10:06:29.340 --> 10:06:31.730 align:start position:0% link local addresses of these two facing interfaces<10:06:30.000> so<10:06:30.596> for<10:06:30.776> example<10:06:31.020> fast<10:06:31.320> ethernet 10:06:31.730 --> 10:06:31.740 align:start position:0% interfaces so for example fast ethernet 10:06:31.740 --> 10:06:34.490 align:start position:0% interfaces so for example fast ethernet here<10:06:32.220> fast<10:06:33.120> ethernet<10:06:33.480> here<10:06:33.840> they<10:06:34.320> will 10:06:34.490 --> 10:06:34.500 align:start position:0% here fast ethernet here they will 10:06:34.500 --> 10:06:38.710 align:start position:0% here fast ethernet here they will communicate<10:06:34.980> between<10:06:35.276> one<10:06:35.640> another<10:06:35.756> here 10:06:38.710 --> 10:06:38.720 align:start position:0% 10:06:38.720 --> 10:06:41.630 align:start position:0% automatically<10:06:39.720> created<10:06:40.200> once<10:06:40.740> IPv6<10:06:41.400> is 10:06:41.630 --> 10:06:41.640 align:start position:0% automatically created once IPv6 is 10:06:41.640 --> 10:06:43.426 align:start position:0% automatically created once IPv6 is enabled 10:06:43.426 --> 10:06:43.436 align:start position:0% enabled 10:06:43.436 --> 10:06:45.350 align:start position:0% enabled now<10:06:43.860> these<10:06:44.096> are<10:06:44.220> used<10:06:44.340> for<10:06:44.520> writing<10:06:44.936> protocol 10:06:45.350 --> 10:06:45.360 align:start position:0% now these are used for writing protocol 10:06:45.360 --> 10:06:48.586 align:start position:0% now these are used for writing protocol Communications<10:06:46.080> IPv6<10:06:47.040> protocols<10:06:47.756> mentioned 10:06:48.586 --> 10:06:48.596 align:start position:0% Communications IPv6 protocols mentioned 10:06:48.596 --> 10:06:50.690 align:start position:0% Communications IPv6 protocols mentioned in<10:06:48.776> the<10:06:48.900> syllabus<10:06:49.380> but<10:06:49.740> I<10:06:50.040> don't<10:06:50.220> think<10:06:50.400> I've 10:06:50.690 --> 10:06:50.700 align:start position:0% in the syllabus but I don't think I've 10:06:50.700 --> 10:06:52.246 align:start position:0% in the syllabus but I don't think I've left<10:06:50.880> it<10:06:51.060> out<10:06:51.120> for<10:06:51.300> now<10:06:51.480> because<10:06:51.720> looking<10:06:52.020> at 10:06:52.246 --> 10:06:52.256 align:start position:0% left it out for now because looking at 10:06:52.256 --> 10:06:55.670 align:start position:0% left it out for now because looking at all<10:06:52.436> the<10:06:52.740> official<10:06:53.460> guides<10:06:54.060> there's<10:06:55.020> no<10:06:55.680> um 10:06:55.670 --> 10:06:55.680 align:start position:0% all the official guides there's no um 10:06:55.680 --> 10:06:58.730 align:start position:0% all the official guides there's no um questions<10:06:55.980> yet<10:06:56.400> I<10:06:56.936> will<10:06:57.120> add<10:06:57.360> it<10:06:57.480> later<10:06:57.660> on<10:06:57.960> if 10:06:58.730 --> 10:06:58.740 align:start position:0% questions yet I will add it later on if 10:06:58.740 --> 10:07:01.906 align:start position:0% questions yet I will add it later on if um if<10:06:59.040> that<10:06:59.220> changes<10:06:59.580> though 10:07:01.906 --> 10:07:01.916 align:start position:0% 10:07:01.916 --> 10:07:03.650 align:start position:0% traffic<10:07:02.400> isn't<10:07:02.820> forwarded<10:07:03.180> off<10:07:03.360> the<10:07:03.540> local 10:07:03.650 --> 10:07:03.660 align:start position:0% traffic isn't forwarded off the local 10:07:03.660 --> 10:07:05.870 align:start position:0% traffic isn't forwarded off the local link<10:07:04.020> certainly<10:07:04.800> not<10:07:04.980> using<10:07:05.340> the<10:07:05.460> link<10:07:05.580> local 10:07:05.870 --> 10:07:05.880 align:start position:0% link certainly not using the link local 10:07:05.880 --> 10:07:07.790 align:start position:0% link certainly not using the link local address 10:07:07.790 --> 10:07:07.800 align:start position:0% address 10:07:07.800 --> 10:07:10.130 align:start position:0% address so<10:07:08.340> here's<10:07:08.700> a<10:07:08.756> configuration<10:07:09.300> for<10:07:09.660> a<10:07:09.776> Cisco 10:07:10.130 --> 10:07:10.140 align:start position:0% so here's a configuration for a Cisco 10:07:10.140 --> 10:07:13.730 align:start position:0% so here's a configuration for a Cisco router<10:07:10.680> you<10:07:11.400> I've<10:07:11.580> enabled<10:07:12.000> IPv6<10:07:12.840> routing 10:07:13.730 --> 10:07:13.740 align:start position:0% router you I've enabled IPv6 routing 10:07:13.740 --> 10:07:15.530 align:start position:0% router you I've enabled IPv6 routing I've<10:07:14.520> gone<10:07:14.700> to<10:07:14.880> the<10:07:15.000> faster<10:07:15.240> ethernet 10:07:15.530 --> 10:07:15.540 align:start position:0% I've gone to the faster ethernet 10:07:15.540 --> 10:07:18.470 align:start position:0% I've gone to the faster ethernet interface<10:07:16.140> all<10:07:17.096> I've<10:07:17.340> done<10:07:17.700> is<10:07:17.880> turned<10:07:18.300> on 10:07:18.470 --> 10:07:18.480 align:start position:0% interface all I've done is turned on 10:07:18.480 --> 10:07:21.530 align:start position:0% interface all I've done is turned on IPv6<10:07:19.380> for<10:07:19.800> this<10:07:20.096> interface<10:07:21.000> here<10:07:21.180> the<10:07:21.416> fast 10:07:21.530 --> 10:07:21.540 align:start position:0% IPv6 for this interface here the fast 10:07:21.540 --> 10:07:23.690 align:start position:0% IPv6 for this interface here the fast ethernet<10:07:21.900> zero<10:07:22.320> slash<10:07:22.560> zero 10:07:23.690 --> 10:07:23.700 align:start position:0% ethernet zero slash zero 10:07:23.700 --> 10:07:26.086 align:start position:0% ethernet zero slash zero I've<10:07:24.180> typed<10:07:24.596> end<10:07:24.776> and<10:07:25.380> then<10:07:25.500> it<10:07:25.680> I've<10:07:25.860> said 10:07:26.086 --> 10:07:26.096 align:start position:0% I've typed end and then it I've said 10:07:26.096 --> 10:07:28.610 align:start position:0% I've typed end and then it I've said show<10:07:26.460> me<10:07:26.700> this<10:07:26.936> interface<10:07:27.480> it's<10:07:28.200> down<10:07:28.436> I 10:07:28.610 --> 10:07:28.620 align:start position:0% show me this interface it's down I 10:07:28.620 --> 10:07:31.370 align:start position:0% show me this interface it's down I haven't<10:07:28.740> connected<10:07:29.160> it<10:07:29.340> to<10:07:29.460> anything<10:07:29.640> but<10:07:30.540> as 10:07:31.370 --> 10:07:31.380 align:start position:0% haven't connected it to anything but as 10:07:31.380 --> 10:07:33.830 align:start position:0% haven't connected it to anything but as we<10:07:31.560> can<10:07:31.740> see<10:07:31.980> this<10:07:32.640> address<10:07:32.880> this<10:07:33.300> link<10:07:33.540> local 10:07:33.830 --> 10:07:33.840 align:start position:0% we can see this address this link local 10:07:33.840 --> 10:07:36.010 align:start position:0% we can see this address this link local address<10:07:34.140> has<10:07:34.980> been<10:07:35.160> allocated 10:07:36.010 --> 10:07:36.020 align:start position:0% address has been allocated 10:07:36.020 --> 10:07:38.746 align:start position:0% address has been allocated self-allocated<10:07:37.020> this<10:07:37.800> is<10:07:37.916> an<10:07:38.160> important<10:07:38.520> bit 10:07:38.746 --> 10:07:38.756 align:start position:0% self-allocated this is an important bit 10:07:38.756 --> 10:07:40.130 align:start position:0% self-allocated this is an important bit here 10:07:40.130 --> 10:07:40.140 align:start position:0% here 10:07:40.140 --> 10:07:42.470 align:start position:0% here FFF<10:07:40.916> as<10:07:41.580> we'll<10:07:41.700> see<10:07:41.820> in<10:07:41.936> a<10:07:42.060> minute<10:07:42.180> but 10:07:42.470 --> 10:07:42.480 align:start position:0% FFF as we'll see in a minute but 10:07:42.480 --> 10:07:45.470 align:start position:0% FFF as we'll see in a minute but basically<10:07:43.200> this<10:07:43.436> is<10:07:43.500> my<10:07:43.740> IPv6<10:07:44.460> address<10:07:44.700> I<10:07:45.360> have 10:07:45.470 --> 10:07:45.480 align:start position:0% basically this is my IPv6 address I have 10:07:45.480 --> 10:07:51.470 align:start position:0% basically this is my IPv6 address I have an<10:07:45.720> app<10:07:45.900> to<10:07:46.080> write<10:07:46.740> it<10:07:46.916> out<10:07:47.300> manually<10:07:48.300> at<10:07:48.596> all 10:07:51.470 --> 10:07:51.480 align:start position:0% 10:07:51.480 --> 10:07:53.330 align:start position:0% I've<10:07:52.020> already<10:07:52.500> um<10:07:52.500> shown<10:07:52.800> you<10:07:52.860> the<10:07:53.040> windows 10:07:53.330 --> 10:07:53.340 align:start position:0% I've already um shown you the windows 10:07:53.340 --> 10:07:54.406 align:start position:0% I've already um shown you the windows one 10:07:54.406 --> 10:07:54.416 align:start position:0% one 10:07:54.416 --> 10:07:57.530 align:start position:0% one yeah<10:07:54.596> unique<10:07:55.200> local<10:07:55.436> uh<10:07:56.276> it's<10:07:56.460> the<10:07:56.880> IPv6 10:07:57.530 --> 10:07:57.540 align:start position:0% yeah unique local uh it's the IPv6 10:07:57.540 --> 10:07:59.630 align:start position:0% yeah unique local uh it's the IPv6 version<10:07:57.840> of<10:07:58.200> private<10:07:58.620> IP<10:07:58.916> addresses<10:07:59.340> so<10:07:59.460> you 10:07:59.630 --> 10:07:59.640 align:start position:0% version of private IP addresses so you 10:07:59.640 --> 10:08:01.790 align:start position:0% version of private IP addresses so you can<10:07:59.756> use<10:07:59.880> all<10:08:00.120> of<10:08:00.240> these<10:08:00.540> on<10:08:01.320> the<10:08:01.500> inside<10:08:01.560> of 10:08:01.790 --> 10:08:01.800 align:start position:0% can use all of these on the inside of 10:08:01.800 --> 10:08:03.290 align:start position:0% can use all of these on the inside of your<10:08:01.916> network<10:08:02.160> you<10:08:02.820> wouldn't<10:08:02.936> be<10:08:03.120> able<10:08:03.240> to 10:08:03.290 --> 10:08:03.300 align:start position:0% your network you wouldn't be able to 10:08:03.300 --> 10:08:05.630 align:start position:0% your network you wouldn't be able to Route<10:08:03.540> them<10:08:03.960> onto<10:08:04.500> the<10:08:04.620> internet<10:08:04.740> don't<10:08:05.460> think 10:08:05.630 --> 10:08:05.640 align:start position:0% Route them onto the internet don't think 10:08:05.640 --> 10:08:06.890 align:start position:0% Route them onto the internet don't think these<10:08:05.880> are<10:08:06.000> used<10:08:06.120> anymore<10:08:06.360> I<10:08:06.660> think<10:08:06.776> they're 10:08:06.890 --> 10:08:06.900 align:start position:0% these are used anymore I think they're 10:08:06.900 --> 10:08:10.130 align:start position:0% these are used anymore I think they're actually<10:08:07.080> been<10:08:07.380> depreciated 10:08:10.130 --> 10:08:10.140 align:start position:0% 10:08:10.140 --> 10:08:12.230 align:start position:0% if<10:08:10.620> you<10:08:10.800> get<10:08:10.916> a<10:08:11.040> question<10:08:11.160> in<10:08:11.400> the<10:08:11.520> exam<10:08:11.820> here 10:08:12.230 --> 10:08:12.240 align:start position:0% if you get a question in the exam here 10:08:12.240 --> 10:08:13.670 align:start position:0% if you get a question in the exam here it<10:08:12.596> would<10:08:12.720> be<10:08:12.840> something<10:08:12.960> like<10:08:13.256> this<10:08:13.436> what 10:08:13.670 --> 10:08:13.680 align:start position:0% it would be something like this what 10:08:13.680 --> 10:08:16.490 align:start position:0% it would be something like this what prefixes<10:08:14.340> link<10:08:14.580> local<10:08:14.880> addresses<10:08:15.416> are<10:08:16.200> taken 10:08:16.490 --> 10:08:16.500 align:start position:0% prefixes link local addresses are taken 10:08:16.500 --> 10:08:18.310 align:start position:0% prefixes link local addresses are taken from<10:08:16.740> fc00 10:08:18.310 --> 10:08:18.320 align:start position:0% from fc00 10:08:18.320 --> 10:08:21.470 align:start position:0% from fc00 uh<10:08:19.320> forward<10:08:19.560> slash<10:08:19.860> seven<10:08:20.160> for<10:08:20.936> your<10:08:21.180> subnet 10:08:21.470 --> 10:08:21.480 align:start position:0% uh forward slash seven for your subnet 10:08:21.480 --> 10:08:23.350 align:start position:0% uh forward slash seven for your subnet mask 10:08:23.350 --> 10:08:23.360 align:start position:0% mask 10:08:23.360 --> 10:08:26.086 align:start position:0% mask these<10:08:24.360> depreciate<10:08:24.900> site<10:08:25.140> local<10:08:25.436> addresses<10:08:25.916> oh 10:08:26.086 --> 10:08:26.096 align:start position:0% these depreciate site local addresses oh 10:08:26.096 --> 10:08:28.310 align:start position:0% these depreciate site local addresses oh sorry<10:08:26.276> so<10:08:26.520> site<10:08:26.880> local<10:08:27.060> addresses<10:08:27.660> that<10:08:28.200> have 10:08:28.310 --> 10:08:28.320 align:start position:0% sorry so site local addresses that have 10:08:28.320 --> 10:08:31.370 align:start position:0% sorry so site local addresses that have been<10:08:28.436> depreciated<10:08:29.480> and<10:08:30.480> overtaken<10:08:31.080> by<10:08:31.200> link 10:08:31.370 --> 10:08:31.380 align:start position:0% been depreciated and overtaken by link 10:08:31.380 --> 10:08:34.426 align:start position:0% been depreciated and overtaken by link local<10:08:31.680> a<10:08:32.220> unique<10:08:32.460> local<10:08:32.700> so<10:08:33.660> you'd<10:08:33.960> use<10:08:34.080> this 10:08:34.426 --> 10:08:34.436 align:start position:0% local a unique local so you'd use this 10:08:34.436 --> 10:08:35.810 align:start position:0% local a unique local so you'd use this on<10:08:34.620> the<10:08:34.740> inside<10:08:34.860> of<10:08:35.096> your<10:08:35.220> network<10:08:35.400> if<10:08:35.700> you 10:08:35.810 --> 10:08:35.820 align:start position:0% on the inside of your network if you 10:08:35.820 --> 10:08:38.030 align:start position:0% on the inside of your network if you want<10:08:35.936> to<10:08:36.060> do<10:08:36.180> any<10:08:36.360> internal<10:08:36.776> routing<10:08:37.320> what<10:08:37.860> you 10:08:38.030 --> 10:08:38.040 align:start position:0% want to do any internal routing what you 10:08:38.040 --> 10:08:40.010 align:start position:0% want to do any internal routing what you couldn't<10:08:38.160> do<10:08:38.400> is<10:08:38.580> use<10:08:38.820> it<10:08:39.000> out<10:08:39.240> on<10:08:39.540> your<10:08:39.660> on<10:08:39.900> the 10:08:40.010 --> 10:08:40.020 align:start position:0% couldn't do is use it out on your on the 10:08:40.020 --> 10:08:41.746 align:start position:0% couldn't do is use it out on your on the internet<10:08:40.140> though 10:08:41.746 --> 10:08:41.756 align:start position:0% internet though 10:08:41.756 --> 10:08:44.030 align:start position:0% internet though multicast<10:08:42.480> addresses<10:08:43.020> are<10:08:43.256> still<10:08:43.500> used<10:08:43.620> very 10:08:44.030 --> 10:08:44.040 align:start position:0% multicast addresses are still used very 10:08:44.040 --> 10:08:49.550 align:start position:0% multicast addresses are still used very much<10:08:44.276> in<10:08:45.320> IPv6<10:08:46.460> this<10:08:47.460> is<10:08:47.520> the<10:08:47.880> prefix<10:08:48.596> so<10:08:49.140> write 10:08:49.550 --> 10:08:49.560 align:start position:0% much in IPv6 this is the prefix so write 10:08:49.560 --> 10:08:51.350 align:start position:0% much in IPv6 this is the prefix so write it<10:08:49.680> down<10:08:49.860> and<10:08:50.040> put<10:08:50.220> it<10:08:50.276> into<10:08:50.400> your<10:08:50.700> studying 10:08:51.350 --> 10:08:51.360 align:start position:0% it down and put it into your studying 10:08:51.360 --> 10:08:53.150 align:start position:0% it down and put it into your studying crumb<10:08:51.720> notes 10:08:53.150 --> 10:08:53.160 align:start position:0% crumb notes 10:08:53.160 --> 10:08:54.890 align:start position:0% crumb notes and<10:08:53.640> multicast<10:08:54.120> replaces<10:08:54.720> address 10:08:54.890 --> 10:08:54.900 align:start position:0% and multicast replaces address 10:08:54.900 --> 10:08:59.450 align:start position:0% and multicast replaces address resolution<10:08:55.436> protocol<10:08:56.040> for<10:08:56.340> IPv6 10:08:59.450 --> 10:08:59.460 align:start position:0% 10:08:59.460 --> 10:09:02.390 align:start position:0% a<10:08:59.936> use<10:09:00.180> for<10:09:00.360> duplicate<10:09:00.840> address<10:09:01.020> detection<10:09:01.620> so 10:09:02.390 --> 10:09:02.400 align:start position:0% a use for duplicate address detection so 10:09:02.400 --> 10:09:06.110 align:start position:0% a use for duplicate address detection so when<10:09:02.640> you<10:09:02.880> first<10:09:03.380> fire<10:09:04.380> up<10:09:04.620> your<10:09:04.980> interface 10:09:06.110 --> 10:09:06.120 align:start position:0% when you first fire up your interface 10:09:06.120 --> 10:09:08.266 align:start position:0% when you first fire up your interface I'll<10:09:06.596> talk<10:09:06.840> about<10:09:06.960> neighbor<10:09:07.500> Discovery<10:09:07.980> in<10:09:08.160> a 10:09:08.266 --> 10:09:08.276 align:start position:0% I'll talk about neighbor Discovery in a 10:09:08.276 --> 10:09:11.330 align:start position:0% I'll talk about neighbor Discovery in a moment<10:09:08.520> but<10:09:09.300> I'll<10:09:09.660> say<10:09:09.900> just<10:09:10.620> to<10:09:10.800> save<10:09:10.980> space 10:09:11.330 --> 10:09:11.340 align:start position:0% moment but I'll say just to save space 10:09:11.340 --> 10:09:13.610 align:start position:0% moment but I'll say just to save space I'll<10:09:12.120> say<10:09:12.300> this<10:09:12.596> is<10:09:12.720> the<10:09:12.900> address<10:09:13.020> obviously 10:09:13.610 --> 10:09:13.620 align:start position:0% I'll say this is the address obviously 10:09:13.620 --> 10:09:16.246 align:start position:0% I'll say this is the address obviously it<10:09:13.740> would<10:09:13.860> be<10:09:13.980> the<10:09:14.096> IPv6<10:09:14.700> address<10:09:15.080> it<10:09:16.080> will 10:09:16.246 --> 10:09:16.256 align:start position:0% it would be the IPv6 address it will 10:09:16.256 --> 10:09:17.870 align:start position:0% it would be the IPv6 address it will this<10:09:16.436> interface<10:09:16.800> will<10:09:17.040> advertise<10:09:17.400> out<10:09:17.640> this 10:09:17.870 --> 10:09:17.880 align:start position:0% this interface will advertise out this 10:09:17.880 --> 10:09:19.070 align:start position:0% this interface will advertise out this address 10:09:19.070 --> 10:09:19.080 align:start position:0% address 10:09:19.080 --> 10:09:21.230 align:start position:0% address to<10:09:20.276> um 10:09:21.230 --> 10:09:21.240 align:start position:0% to um 10:09:21.240 --> 10:09:25.310 align:start position:0% to um the<10:09:21.900> network<10:09:22.140> this<10:09:23.096> multicast<10:09:23.640> address 10:09:25.310 --> 10:09:25.320 align:start position:0% the network this multicast address 10:09:25.320 --> 10:09:27.530 align:start position:0% the network this multicast address saying<10:09:26.040> I<10:09:26.220> want<10:09:26.276> to<10:09:26.340> use<10:09:26.400> this<10:09:26.580> address<10:09:26.756> X<10:09:27.180> and 10:09:27.530 --> 10:09:27.540 align:start position:0% saying I want to use this address X and 10:09:27.540 --> 10:09:30.110 align:start position:0% saying I want to use this address X and if<10:09:27.660> any<10:09:27.900> of<10:09:28.080> the<10:09:28.200> any<10:09:28.436> of<10:09:28.916> these<10:09:29.340> interfaces 10:09:30.110 --> 10:09:30.120 align:start position:0% if any of the any of these interfaces 10:09:30.120 --> 10:09:32.450 align:start position:0% if any of the any of these interfaces are<10:09:30.300> using<10:09:30.660> that<10:09:30.900> address<10:09:31.140> so<10:09:31.800> this<10:09:32.040> is<10:09:32.096> using 10:09:32.450 --> 10:09:32.460 align:start position:0% are using that address so this is using 10:09:32.460 --> 10:09:34.790 align:start position:0% are using that address so this is using Y<10:09:32.756> that's<10:09:33.416> using<10:09:33.840> Zed 10:09:34.790 --> 10:09:34.800 align:start position:0% Y that's using Zed 10:09:34.800 --> 10:09:36.470 align:start position:0% Y that's using Zed it<10:09:35.276> will<10:09:35.400> come<10:09:35.520> back<10:09:35.700> and<10:09:35.820> say<10:09:35.936> no<10:09:36.120> you<10:09:36.360> can't 10:09:36.470 --> 10:09:36.480 align:start position:0% it will come back and say no you can't 10:09:36.480 --> 10:09:38.210 align:start position:0% it will come back and say no you can't use<10:09:36.720> that<10:09:36.900> address<10:09:37.080> but<10:09:37.500> in<10:09:37.680> this<10:09:37.800> case<10:09:37.916> my 10:09:38.210 --> 10:09:38.220 align:start position:0% use that address but in this case my 10:09:38.220 --> 10:09:41.330 align:start position:0% use that address but in this case my example<10:09:38.580> here<10:09:38.756> nobody's<10:09:39.596> using<10:09:39.960> it 10:09:41.330 --> 10:09:41.340 align:start position:0% example here nobody's using it 10:09:41.340 --> 10:09:43.610 align:start position:0% example here nobody's using it all<10:09:41.720> routers<10:09:42.720> must<10:09:42.900> join<10:09:43.140> the<10:09:43.256> All<10:09:43.380> host 10:09:43.610 --> 10:09:43.620 align:start position:0% all routers must join the All host 10:09:43.620 --> 10:09:46.030 align:start position:0% all routers must join the All host multicast<10:09:44.276> group<10:09:44.580> of 10:09:46.030 --> 10:09:46.040 align:start position:0% multicast group of 10:09:46.040 --> 10:09:49.670 align:start position:0% multicast group of ff02<10:09:47.040> and<10:09:47.936> then<10:09:48.000> whatever<10:09:48.240> in<10:09:48.596> the<10:09:48.720> middle<10:09:48.840> uh 10:09:49.670 --> 10:09:49.680 align:start position:0% ff02 and then whatever in the middle uh 10:09:49.680 --> 10:09:52.010 align:start position:0% ff02 and then whatever in the middle uh one<10:09:49.916> so<10:09:50.276> it'll<10:09:50.460> all<10:09:50.580> be<10:09:50.756> zeros<10:09:51.180> and<10:09:51.596> then<10:09:51.720> one 10:09:52.010 --> 10:09:52.020 align:start position:0% one so it'll all be zeros and then one 10:09:52.020 --> 10:09:54.890 align:start position:0% one so it'll all be zeros and then one and<10:09:52.680> the<10:09:52.860> all<10:09:53.040> routers<10:09:53.460> multicast<10:09:54.060> group<10:09:54.360> this 10:09:54.890 --> 10:09:54.900 align:start position:0% and the all routers multicast group this 10:09:54.900 --> 10:09:56.746 align:start position:0% and the all routers multicast group this is<10:09:54.960> how<10:09:55.140> enable<10:09:55.436> Discovery<10:09:56.040> protocol<10:09:56.276> works 10:09:56.746 --> 10:09:56.756 align:start position:0% is how enable Discovery protocol works 10:09:56.756 --> 10:09:58.970 align:start position:0% is how enable Discovery protocol works so<10:09:56.880> it<10:09:57.060> must<10:09:57.240> be<10:09:57.416> allocated<10:09:57.840> and<10:09:58.140> listening<10:09:58.436> to 10:09:58.970 --> 10:09:58.980 align:start position:0% so it must be allocated and listening to 10:09:58.980 --> 10:10:00.530 align:start position:0% so it must be allocated and listening to these<10:09:59.220> two<10:09:59.340> addresses 10:10:00.530 --> 10:10:00.540 align:start position:0% these two addresses 10:10:00.540 --> 10:10:04.906 align:start position:0% these two addresses and<10:10:01.080> if<10:10:01.256> I<10:10:01.500> issue<10:10:02.040> a<10:10:02.340> show<10:10:03.300> IPv6<10:10:04.256> interface 10:10:04.906 --> 10:10:04.916 align:start position:0% and if I issue a show IPv6 interface 10:10:04.916 --> 10:10:08.266 align:start position:0% and if I issue a show IPv6 interface fast<10:10:05.276> ethernet<10:10:05.640> 0<10:10:05.936> 0<10:10:06.540> you<10:10:07.320> can<10:10:07.436> say<10:10:07.680> you<10:10:08.160> can 10:10:08.266 --> 10:10:08.276 align:start position:0% fast ethernet 0 0 you can say you can 10:10:08.276 --> 10:10:10.550 align:start position:0% fast ethernet 0 0 you can say you can see<10:10:08.580> that<10:10:09.120> it's<10:10:09.300> joined<10:10:09.720> these<10:10:10.080> two<10:10:10.200> groups 10:10:10.550 --> 10:10:10.560 align:start position:0% see that it's joined these two groups 10:10:10.560 --> 10:10:16.906 align:start position:0% see that it's joined these two groups appear<10:10:10.916> the<10:10:12.180> um<10:10:12.180> the<10:10:12.596> F2<10:10:13.080> and<10:10:13.620> the<10:10:13.740> F1 10:10:16.906 --> 10:10:16.916 align:start position:0% 10:10:16.916 --> 10:10:21.230 align:start position:0% eui<10:10:17.640> 64<10:10:18.060> addressing<10:10:18.720> is<10:10:19.020> the<10:10:19.436> new<10:10:19.860> part<10:10:20.220> in<10:10:21.060> the 10:10:21.230 --> 10:10:21.240 align:start position:0% eui 64 addressing is the new part in the 10:10:21.240 --> 10:10:23.690 align:start position:0% eui 64 addressing is the new part in the syllabus 10:10:23.690 --> 10:10:23.700 align:start position:0% syllabus 10:10:23.700 --> 10:10:26.530 align:start position:0% syllabus yeah<10:10:23.756> so<10:10:24.540> I've<10:10:24.660> issued<10:10:25.080> a<10:10:25.140> show<10:10:25.320> ipv 10:10:26.530 --> 10:10:26.540 align:start position:0% yeah so I've issued a show ipv 10:10:26.540 --> 10:10:30.730 align:start position:0% yeah so I've issued a show ipv IP<10:10:27.540> interface<10:10:27.960> sorry<10:10:28.200> I've<10:10:28.916> didn't<10:10:29.220> do<10:10:29.480> IPv6 10:10:30.730 --> 10:10:30.740 align:start position:0% IP interface sorry I've didn't do IPv6 10:10:30.740 --> 10:10:33.710 align:start position:0% IP interface sorry I've didn't do IPv6 because<10:10:31.820> I<10:10:32.820> want<10:10:32.936> to<10:10:33.060> see<10:10:33.180> what<10:10:33.416> the<10:10:33.540> MAC 10:10:33.710 --> 10:10:33.720 align:start position:0% because I want to see what the MAC 10:10:33.720 --> 10:10:35.630 align:start position:0% because I want to see what the MAC address<10:10:33.960> is 10:10:35.630 --> 10:10:35.640 align:start position:0% address is 10:10:35.640 --> 10:10:40.490 align:start position:0% address is because<10:10:36.240> this<10:10:36.720> is<10:10:36.900> how<10:10:37.140> eui<10:10:37.740> 64<10:10:38.300> obtains<10:10:39.300> the 10:10:40.490 --> 10:10:40.500 align:start position:0% because this is how eui 64 obtains the 10:10:40.500 --> 10:10:43.370 align:start position:0% because this is how eui 64 obtains the um<10:10:40.560> eui<10:10:41.400> 64<10:10:41.880> address 10:10:43.370 --> 10:10:43.380 align:start position:0% um eui 64 address 10:10:43.380 --> 10:10:45.950 align:start position:0% um eui 64 address so<10:10:44.040> this<10:10:44.640> is<10:10:44.756> how<10:10:45.000> or<10:10:45.180> one<10:10:45.416> of<10:10:45.480> the<10:10:45.540> ways<10:10:45.840> you 10:10:45.950 --> 10:10:45.960 align:start position:0% so this is how or one of the ways you 10:10:45.960 --> 10:10:48.050 align:start position:0% so this is how or one of the ways you can<10:10:46.080> self<10:10:46.256> generate<10:10:46.980> an<10:10:47.096> interface<10:10:47.520> it<10:10:47.756> uses 10:10:48.050 --> 10:10:48.060 align:start position:0% can self generate an interface it uses 10:10:48.060 --> 10:10:50.266 align:start position:0% can self generate an interface it uses the<10:10:48.180> MAC<10:10:48.360> address 10:10:50.266 --> 10:10:50.276 align:start position:0% the MAC address 10:10:50.276 --> 10:10:53.030 align:start position:0% the MAC address the<10:10:50.640> 48-bit<10:10:51.180> MAC<10:10:51.360> address<10:10:51.540> obviously<10:10:52.320> we<10:10:52.860> need 10:10:53.030 --> 10:10:53.040 align:start position:0% the 48-bit MAC address obviously we need 10:10:53.040 --> 10:10:56.450 align:start position:0% the 48-bit MAC address obviously we need 128<10:10:54.000> bits<10:10:54.596> 48<10:10:55.140> bits<10:10:55.560> isn't<10:10:55.916> enough<10:10:56.040> to 10:10:56.450 --> 10:10:56.460 align:start position:0% 128 bits 48 bits isn't enough to 10:10:56.460 --> 10:10:58.790 align:start position:0% 128 bits 48 bits isn't enough to generate<10:10:56.880> this<10:10:57.300> address 10:10:58.790 --> 10:10:58.800 align:start position:0% generate this address 10:10:58.800 --> 10:11:00.170 align:start position:0% generate this address but<10:10:59.160> what<10:10:59.276> it<10:10:59.460> does<10:10:59.580> it<10:10:59.756> takes<10:10:59.880> the<10:11:00.060> MAC 10:11:00.170 --> 10:11:00.180 align:start position:0% but what it does it takes the MAC 10:11:00.180 --> 10:11:01.246 align:start position:0% but what it does it takes the MAC address 10:11:01.246 --> 10:11:01.256 align:start position:0% address 10:11:01.256 --> 10:11:05.390 align:start position:0% address it<10:11:02.040> inverts<10:11:02.460> the<10:11:02.640> seventh<10:11:03.120> bit<10:11:03.436> and<10:11:04.436> adds<10:11:04.860> FFF 10:11:05.390 --> 10:11:05.400 align:start position:0% it inverts the seventh bit and adds FFF 10:11:05.400 --> 10:11:08.810 align:start position:0% it inverts the seventh bit and adds FFF Fe<10:11:05.700> in<10:11:06.120> the<10:11:06.240> center<10:11:06.380> so<10:11:07.380> right<10:11:08.276> in<10:11:08.520> the<10:11:08.640> middle 10:11:08.810 --> 10:11:08.820 align:start position:0% Fe in the center so right in the middle 10:11:08.820 --> 10:11:12.610 align:start position:0% Fe in the center so right in the middle of<10:11:09.300> the<10:11:09.480> MAC<10:11:09.596> address<10:11:09.900> it's<10:11:10.740> going<10:11:11.040> to<10:11:11.220> add 10:11:12.610 --> 10:11:12.620 align:start position:0% of the MAC address it's going to add 10:11:12.620 --> 10:11:15.490 align:start position:0% of the MAC address it's going to add fffe<10:11:13.620> make<10:11:14.400> sure<10:11:14.520> you<10:11:14.640> take<10:11:14.820> a<10:11:14.936> note<10:11:15.060> of<10:11:15.300> this 10:11:15.490 --> 10:11:15.500 align:start position:0% fffe make sure you take a note of this 10:11:15.500 --> 10:11:17.870 align:start position:0% fffe make sure you take a note of this for<10:11:16.500> the<10:11:16.680> exam<10:11:16.980> so 10:11:17.870 --> 10:11:17.880 align:start position:0% for the exam so 10:11:17.880 --> 10:11:22.426 align:start position:0% for the exam so uh<10:11:18.416> we've<10:11:18.776> got<10:11:19.020> zero<10:11:19.800> zero<10:11:20.220> one<10:11:20.640> one 10:11:22.426 --> 10:11:22.436 align:start position:0% uh we've got zero zero one one 10:11:22.436 --> 10:11:24.830 align:start position:0% uh we've got zero zero one one hold<10:11:23.040> cover<10:11:23.276> white<10:11:23.640> it<10:11:23.820> doesn't<10:11:23.936> say<10:11:24.240> zero 10:11:24.830 --> 10:11:24.840 align:start position:0% hold cover white it doesn't say zero 10:11:24.840 --> 10:11:29.210 align:start position:0% hold cover white it doesn't say zero zero<10:11:25.200> one<10:11:25.380> one<10:11:25.620> here<10:11:26.400> and<10:11:27.000> then<10:11:27.120> here's<10:11:27.840> the<10:11:27.960> a 10:11:29.210 --> 10:11:29.220 align:start position:0% zero one one here and then here's the a 10:11:29.220 --> 10:11:30.830 align:start position:0% zero one one here and then here's the a here 10:11:30.830 --> 10:11:30.840 align:start position:0% here 10:11:30.840 --> 10:11:33.406 align:start position:0% here and<10:11:31.320> then<10:11:31.436> you<10:11:31.560> can<10:11:31.680> see<10:11:31.860> the<10:11:32.220> fffe<10:11:33.120> has 10:11:33.406 --> 10:11:33.416 align:start position:0% and then you can see the fffe has 10:11:33.416 --> 10:11:36.830 align:start position:0% and then you can see the fffe has appeared<10:11:33.900> he<10:11:34.740> has<10:11:34.980> inserted<10:11:35.700> it<10:11:35.880> and<10:11:36.540> then<10:11:36.660> it 10:11:36.830 --> 10:11:36.840 align:start position:0% appeared he has inserted it and then it 10:11:36.840 --> 10:11:37.906 align:start position:0% appeared he has inserted it and then it carries<10:11:37.140> on<10:11:37.256> with<10:11:37.380> the<10:11:37.560> rest<10:11:37.620> of<10:11:37.740> the<10:11:37.800> MAC 10:11:37.906 --> 10:11:37.916 align:start position:0% carries on with the rest of the MAC 10:11:37.916 --> 10:11:43.670 align:start position:0% carries on with the rest of the MAC address<10:11:38.096> BB<10:11:38.820> c<10:11:39.480> c<10:11:39.720> d<10:11:39.900> d<10:11:40.140> so<10:11:40.740> b<10:11:40.980> b<10:11:41.160> c<10:11:41.400> c<10:11:41.640> c<10:11:41.756> m<10:11:42.360> c<10:11:42.840> d<10:11:43.020> so 10:11:43.670 --> 10:11:43.680 align:start position:0% address BB c c d d so b b c c c m c d so 10:11:43.680 --> 10:11:47.086 align:start position:0% address BB c c d d so b b c c c m c d so this<10:11:43.916> is<10:11:44.096> how<10:11:44.580> it<10:11:44.756> pads<10:11:45.240> out<10:11:45.300> the<10:11:45.596> address 10:11:47.086 --> 10:11:47.096 align:start position:0% this is how it pads out the address 10:11:47.096 --> 10:11:51.110 align:start position:0% this is how it pads out the address so<10:11:47.520> there's<10:11:47.700> two<10:11:47.936> bits<10:11:48.360> Mac<10:11:48.960> address 10:11:51.110 --> 10:11:51.120 align:start position:0% so there's two bits Mac address 10:11:51.120 --> 10:11:54.110 align:start position:0% so there's two bits Mac address plus<10:11:51.840> this<10:11:52.200> but<10:11:52.980> then<10:11:53.220> it<10:11:53.520> does<10:11:53.700> this<10:11:53.936> other 10:11:54.110 --> 10:11:54.120 align:start position:0% plus this but then it does this other 10:11:54.120 --> 10:11:56.330 align:start position:0% plus this but then it does this other bit<10:11:54.360> here<10:11:54.540> which<10:11:54.840> is<10:11:54.960> inverting<10:11:55.500> the<10:11:55.800> seventh 10:11:56.330 --> 10:11:56.340 align:start position:0% bit here which is inverting the seventh 10:11:56.340 --> 10:11:59.086 align:start position:0% bit here which is inverting the seventh bit 10:11:59.086 --> 10:11:59.096 align:start position:0% 10:11:59.096 --> 10:12:00.890 align:start position:0% so 10:12:00.890 --> 10:12:00.900 align:start position:0% so 10:12:00.900 --> 10:12:02.570 align:start position:0% so just<10:12:01.436> to<10:12:01.560> recap<10:12:01.860> what<10:12:02.040> I've<10:12:02.160> already<10:12:02.276> said 10:12:02.570 --> 10:12:02.580 align:start position:0% just to recap what I've already said 10:12:02.580 --> 10:12:05.510 align:start position:0% just to recap what I've already said we're<10:12:03.060> looking<10:12:03.240> at<10:12:03.480> this<10:12:03.776> part<10:12:03.960> now<10:12:04.256> zero<10:12:05.040> zero 10:12:05.510 --> 10:12:05.520 align:start position:0% we're looking at this part now zero zero 10:12:05.520 --> 10:12:07.906 align:start position:0% we're looking at this part now zero zero one<10:12:06.000> one<10:12:06.300> well<10:12:06.960> instead<10:12:07.320> of<10:12:07.436> that<10:12:07.560> now<10:12:07.680> we've 10:12:07.906 --> 10:12:07.916 align:start position:0% one one well instead of that now we've 10:12:07.916 --> 10:12:16.070 align:start position:0% one one well instead of that now we've got<10:12:08.040> zero<10:12:08.756> two<10:12:09.120> one<10:12:09.416> one 10:12:16.070 --> 10:12:16.080 align:start position:0% 10:12:16.080 --> 10:12:17.926 align:start position:0% all<10:12:16.500> right<10:12:16.680> so<10:12:16.740> going<10:12:16.980> into<10:12:17.220> the<10:12:17.460> seventh 10:12:17.926 --> 10:12:17.936 align:start position:0% all right so going into the seventh 10:12:17.936 --> 10:12:21.586 align:start position:0% all right so going into the seventh seventh<10:12:18.540> most<10:12:18.900> significant<10:12:19.860> bit 10:12:21.586 --> 10:12:21.596 align:start position:0% seventh most significant bit 10:12:21.596 --> 10:12:25.550 align:start position:0% seventh most significant bit so<10:12:22.200> this<10:12:22.380> is<10:12:22.620> our<10:12:22.800> sample<10:12:23.220> address<10:12:23.460> here 10:12:25.550 --> 10:12:25.560 align:start position:0% so this is our sample address here 10:12:25.560 --> 10:12:29.390 align:start position:0% so this is our sample address here the<10:12:26.160> first<10:12:26.276> two<10:12:26.520> nibbles<10:12:27.060> uh<10:12:28.020> or<10:12:28.320> is<10:12:28.680> one<10:12:28.980> byte 10:12:29.390 --> 10:12:29.400 align:start position:0% the first two nibbles uh or is one byte 10:12:29.400 --> 10:12:34.130 align:start position:0% the first two nibbles uh or is one byte so<10:12:29.880> this<10:12:30.180> is<10:12:30.320> 0.0<10:12:31.320> so<10:12:31.916> a<10:12:32.220> nibble<10:12:32.720> if<10:12:33.720> we<10:12:33.900> have 10:12:34.130 --> 10:12:34.140 align:start position:0% so this is 0.0 so a nibble if we have 10:12:34.140 --> 10:12:38.150 align:start position:0% so this is 0.0 so a nibble if we have one<10:12:34.800> two<10:12:35.096> three<10:12:35.580> four<10:12:36.080> five<10:12:37.080> six<10:12:37.380> seven<10:12:37.800> eight 10:12:38.150 --> 10:12:38.160 align:start position:0% one two three four five six seven eight 10:12:38.160 --> 10:12:40.970 align:start position:0% one two three four five six seven eight so<10:12:38.756> eight<10:12:39.180> bits<10:12:39.596> is<10:12:39.900> one<10:12:40.140> byte<10:12:40.560> which<10:12:40.740> we've 10:12:40.970 --> 10:12:40.980 align:start position:0% so eight bits is one byte which we've 10:12:40.980 --> 10:12:43.670 align:start position:0% so eight bits is one byte which we've covered<10:12:41.400> already<10:12:41.820> oops 10:12:43.670 --> 10:12:43.680 align:start position:0% covered already oops 10:12:43.680 --> 10:12:46.010 align:start position:0% covered already oops one<10:12:44.276> byte 10:12:46.010 --> 10:12:46.020 align:start position:0% one byte 10:12:46.020 --> 10:12:49.850 align:start position:0% one byte one<10:12:46.620> byte<10:12:47.096> eight<10:12:48.000> bits<10:12:48.480> but<10:12:49.020> what<10:12:49.320> we<10:12:49.500> can<10:12:49.620> do 10:12:49.850 --> 10:12:49.860 align:start position:0% one byte eight bits but what we can do 10:12:49.860 --> 10:12:51.470 align:start position:0% one byte eight bits but what we can do is<10:12:50.096> kind<10:12:50.340> of<10:12:50.460> subdivide<10:12:51.000> it<10:12:51.120> in<10:12:51.300> the<10:12:51.416> middle 10:12:51.470 --> 10:12:51.480 align:start position:0% is kind of subdivide it in the middle 10:12:51.480 --> 10:12:54.170 align:start position:0% is kind of subdivide it in the middle here 10:12:54.170 --> 10:12:54.180 align:start position:0% 10:12:54.180 --> 10:12:58.490 align:start position:0% and<10:12:54.720> we<10:12:54.900> can<10:12:55.020> have<10:12:55.200> a<10:12:55.380> nibble<10:12:55.800> here 10:12:58.490 --> 10:12:58.500 align:start position:0% 10:12:58.500 --> 10:13:03.406 align:start position:0% and<10:12:58.916> a<10:12:59.096> nibble<10:12:59.460> here 10:13:03.406 --> 10:13:03.416 align:start position:0% 10:13:03.416 --> 10:13:06.290 align:start position:0% all<10:13:03.960> right<10:13:04.140> so<10:13:04.860> our<10:13:05.160> first<10:13:05.340> two<10:13:05.520> nibbles<10:13:05.936> one 10:13:06.290 --> 10:13:06.300 align:start position:0% all right so our first two nibbles one 10:13:06.300 --> 10:13:07.790 align:start position:0% all right so our first two nibbles one byte<10:13:06.720> here 10:13:07.790 --> 10:13:07.800 align:start position:0% byte here 10:13:07.800 --> 10:13:10.246 align:start position:0% byte here is<10:13:08.460> zero<10:13:09.060> zero 10:13:10.246 --> 10:13:10.256 align:start position:0% is zero zero 10:13:10.256 --> 10:13:12.350 align:start position:0% is zero zero which<10:13:10.680> would<10:13:10.916> have<10:13:11.096> all<10:13:11.400> the<10:13:11.520> binary<10:13:11.880> bits 10:13:12.350 --> 10:13:12.360 align:start position:0% which would have all the binary bits 10:13:12.360 --> 10:13:17.266 align:start position:0% which would have all the binary bits basically<10:13:12.960> pretty<10:13:13.860> easy<10:13:14.040> to<10:13:14.340> work<10:13:14.460> out 10:13:17.266 --> 10:13:17.276 align:start position:0% 10:13:17.276 --> 10:13:19.790 align:start position:0% so<10:13:18.060> this<10:13:18.596> here 10:13:19.790 --> 10:13:19.800 align:start position:0% so this here 10:13:19.800 --> 10:13:22.246 align:start position:0% so this here if<10:13:20.096> you<10:13:20.160> write<10:13:20.340> it<10:13:20.520> out<10:13:20.640> with<10:13:20.756> a<10:13:20.936> nice<10:13:21.060> uh 10:13:22.246 --> 10:13:22.256 align:start position:0% if you write it out with a nice uh 10:13:22.256 --> 10:13:25.370 align:start position:0% if you write it out with a nice uh font<10:13:22.800> is<10:13:23.160> zero<10:13:23.700> zero<10:13:24.000> zero<10:13:24.300> zero<10:13:24.660> zero<10:13:25.080> zero 10:13:25.370 --> 10:13:25.380 align:start position:0% font is zero zero zero zero zero zero 10:13:25.380 --> 10:13:28.010 align:start position:0% font is zero zero zero zero zero zero zero<10:13:25.680> zero<10:13:26.040> so<10:13:26.520> what<10:13:26.756> we<10:13:26.880> need<10:13:27.000> to<10:13:27.120> do<10:13:27.300> is<10:13:27.540> flip 10:13:28.010 --> 10:13:28.020 align:start position:0% zero zero so what we need to do is flip 10:13:28.020 --> 10:13:31.550 align:start position:0% zero zero so what we need to do is flip the<10:13:28.320> seventh<10:13:28.680> most<10:13:28.980> significant<10:13:29.520> bit 10:13:31.550 --> 10:13:31.560 align:start position:0% the seventh most significant bit 10:13:31.560 --> 10:13:35.990 align:start position:0% the seventh most significant bit so<10:13:32.276> what<10:13:32.460> we've<10:13:32.580> done<10:13:32.820> is<10:13:33.060> one<10:13:33.900> two<10:13:34.380> three<10:13:35.340> four 10:13:35.990 --> 10:13:36.000 align:start position:0% so what we've done is one two three four 10:13:36.000 --> 10:13:40.310 align:start position:0% so what we've done is one two three four five<10:13:36.256> six<10:13:37.256> seven<10:13:37.860> eight<10:13:38.756> so<10:13:39.540> this<10:13:39.840> is<10:13:40.020> the 10:13:40.310 --> 10:13:40.320 align:start position:0% five six seven eight so this is the 10:13:40.320 --> 10:13:42.650 align:start position:0% five six seven eight so this is the seventh<10:13:40.680> most<10:13:40.916> significant<10:13:41.460> bit<10:13:41.700> and<10:13:42.416> what 10:13:42.650 --> 10:13:42.660 align:start position:0% seventh most significant bit and what 10:13:42.660 --> 10:13:44.510 align:start position:0% seventh most significant bit and what we've<10:13:42.840> done<10:13:43.080> is<10:13:43.320> gone<10:13:43.620> all<10:13:43.860> the<10:13:43.980> way<10:13:44.040> over<10:13:44.220> here 10:13:44.510 --> 10:13:44.520 align:start position:0% we've done is gone all the way over here 10:13:44.520 --> 10:13:46.730 align:start position:0% we've done is gone all the way over here to<10:13:45.240> find<10:13:45.360> the<10:13:45.540> seventh<10:13:45.900> bit<10:13:46.020> and<10:13:46.560> we've 10:13:46.730 --> 10:13:46.740 align:start position:0% to find the seventh bit and we've 10:13:46.740 --> 10:13:49.246 align:start position:0% to find the seventh bit and we've flipped<10:13:47.220> it<10:13:47.340> so<10:13:47.880> whatever<10:13:48.060> it<10:13:48.360> was<10:13:48.480> here<10:13:48.776> in 10:13:49.246 --> 10:13:49.256 align:start position:0% flipped it so whatever it was here in 10:13:49.256 --> 10:13:53.746 align:start position:0% flipped it so whatever it was here in binary<10:13:49.620> we<10:13:49.800> flipped<10:13:50.460> it<10:13:50.580> so<10:13:51.540> one 10:13:53.746 --> 10:13:53.756 align:start position:0% binary we flipped it so one 10:13:53.756 --> 10:13:58.246 align:start position:0% binary we flipped it so one flip<10:13:54.416> two 10:13:58.246 --> 10:13:58.256 align:start position:0% 10:13:58.256 --> 10:14:02.450 align:start position:0% sorry<10:13:58.916> zero<10:13:59.340> flip<10:13:59.640> to<10:13:59.820> be<10:13:59.936> a<10:14:00.120> one 10:14:02.450 --> 10:14:02.460 align:start position:0% 10:14:02.460 --> 10:14:05.266 align:start position:0% now<10:14:03.060> if<10:14:03.360> you<10:14:03.480> wrote<10:14:03.660> that<10:14:03.960> out<10:14:04.200> uh<10:14:04.800> this<10:14:05.096> part 10:14:05.266 --> 10:14:05.276 align:start position:0% now if you wrote that out uh this part 10:14:05.276 --> 10:14:06.650 align:start position:0% now if you wrote that out uh this part here 10:14:06.650 --> 10:14:06.660 align:start position:0% here 10:14:06.660 --> 10:14:08.690 align:start position:0% here you'd<10:14:07.320> have<10:14:07.980> um 10:14:08.690 --> 10:14:08.700 align:start position:0% you'd have um 10:14:08.700 --> 10:14:10.906 align:start position:0% you'd have um your<10:14:09.300> zero<10:14:09.776> would<10:14:10.020> be<10:14:10.140> covered<10:14:10.560> two<10:14:10.680> that's 10:14:10.906 --> 10:14:10.916 align:start position:0% your zero would be covered two that's 10:14:10.916 --> 10:14:16.610 align:start position:0% your zero would be covered two that's the<10:14:11.160> one<10:14:11.460> two<10:14:12.200> four<10:14:13.200> eight<10:14:13.800> one<10:14:14.640> two<10:14:15.480> four 10:14:16.610 --> 10:14:16.620 align:start position:0% the one two four eight one two four 10:14:16.620 --> 10:14:20.030 align:start position:0% the one two four eight one two four eight<10:14:17.040> Okay<10:14:17.820> so<10:14:18.360> we've<10:14:18.720> uh<10:14:19.080> enabled<10:14:19.860> this 10:14:20.030 --> 10:14:20.040 align:start position:0% eight Okay so we've uh enabled this 10:14:20.040 --> 10:14:22.850 align:start position:0% eight Okay so we've uh enabled this column<10:14:20.340> here<10:14:20.580> and<10:14:21.240> our<10:14:21.480> zero<10:14:21.960> has<10:14:22.256> flipped<10:14:22.740> to 10:14:22.850 --> 10:14:22.860 align:start position:0% column here and our zero has flipped to 10:14:22.860 --> 10:14:26.266 align:start position:0% column here and our zero has flipped to A2 10:14:26.266 --> 10:14:26.276 align:start position:0% 10:14:26.276 --> 10:14:29.266 align:start position:0% and<10:14:26.820> you<10:14:26.936> can<10:14:27.060> see<10:14:27.300> here<10:14:27.596> zero<10:14:28.380> two<10:14:28.620> one<10:14:29.040> one 10:14:29.266 --> 10:14:29.276 align:start position:0% and you can see here zero two one one 10:14:29.276 --> 10:14:31.246 align:start position:0% and you can see here zero two one one and<10:14:29.580> then<10:14:30.240> um<10:14:30.300> this<10:14:30.660> is<10:14:30.720> the<10:14:30.840> MAC<10:14:31.020> address 10:14:31.246 --> 10:14:31.256 align:start position:0% and then um this is the MAC address 10:14:31.256 --> 10:14:34.070 align:start position:0% and then um this is the MAC address we've<10:14:32.160> got<10:14:32.276> the<10:14:32.400> fffe<10:14:33.180> in<10:14:33.300> the<10:14:33.416> middle<10:14:33.480> and 10:14:34.070 --> 10:14:34.080 align:start position:0% we've got the fffe in the middle and 10:14:34.080 --> 10:14:35.870 align:start position:0% we've got the fffe in the middle and then<10:14:34.200> the<10:14:34.380> rest<10:14:34.436> of<10:14:34.620> the<10:14:34.680> MAC<10:14:34.800> address<10:14:35.040> this<10:14:35.820> is 10:14:35.870 --> 10:14:35.880 align:start position:0% then the rest of the MAC address this is 10:14:35.880 --> 10:14:37.310 align:start position:0% then the rest of the MAC address this is how<10:14:36.060> you<10:14:36.180> work<10:14:36.360> it<10:14:36.540> out<10:14:36.660> you<10:14:36.840> might<10:14:36.960> get<10:14:37.200> a 10:14:37.310 --> 10:14:37.320 align:start position:0% how you work it out you might get a 10:14:37.320 --> 10:14:38.990 align:start position:0% how you work it out you might get a question<10:14:37.436> on<10:14:37.740> this<10:14:37.916> so<10:14:38.160> this<10:14:38.400> is<10:14:38.520> why<10:14:38.756> I 10:14:38.990 --> 10:14:39.000 align:start position:0% question on this so this is why I 10:14:39.000 --> 10:14:41.390 align:start position:0% question on this so this is why I brought<10:14:39.480> it<10:14:39.660> to<10:14:39.776> uh<10:14:40.140> your<10:14:40.380> attention<10:14:40.680> and<10:14:41.340> you 10:14:41.390 --> 10:14:41.400 align:start position:0% brought it to uh your attention and you 10:14:41.400 --> 10:14:44.690 align:start position:0% brought it to uh your attention and you just<10:14:41.580> need<10:14:41.700> to<10:14:41.820> practice<10:14:42.000> a<10:14:42.300> few<10:14:42.480> examples 10:14:44.690 --> 10:14:44.700 align:start position:0% just need to practice a few examples 10:14:44.700 --> 10:14:47.330 align:start position:0% just need to practice a few examples so<10:14:45.360> what<10:14:45.660> would<10:14:45.840> this<10:14:46.020> address<10:14:46.200> be<10:14:46.680> changed<10:14:47.160> to 10:14:47.330 --> 10:14:47.340 align:start position:0% so what would this address be changed to 10:14:47.340 --> 10:14:53.746 align:start position:0% so what would this address be changed to if<10:14:47.820> you<10:14:48.180> write<10:14:48.480> it<10:14:48.776> down 10:14:53.746 --> 10:14:53.756 align:start position:0% 10:14:53.756 --> 10:14:55.130 align:start position:0% all<10:14:54.180> right<10:14:54.360> so<10:14:54.416> I've<10:14:54.540> just<10:14:54.720> carried<10:14:54.960> it<10:14:55.080> over 10:14:55.130 --> 10:14:55.140 align:start position:0% all right so I've just carried it over 10:14:55.140 --> 10:15:00.970 align:start position:0% all right so I've just carried it over to<10:14:55.320> the<10:14:55.500> next<10:14:55.620> slide<10:14:55.980> here 10:15:00.970 --> 10:15:00.980 align:start position:0% 10:15:00.980 --> 10:15:04.246 align:start position:0% so<10:15:01.980> Charlotte<10:15:02.276> IPv6<10:15:03.180> interface<10:15:03.720> we've<10:15:04.080> got 10:15:04.246 --> 10:15:04.256 align:start position:0% so Charlotte IPv6 interface we've got 10:15:04.256 --> 10:15:08.030 align:start position:0% so Charlotte IPv6 interface we've got this<10:15:04.620> address<10:15:04.860> here<10:15:05.520> and<10:15:06.240> we<10:15:06.480> end<10:15:06.720> up<10:15:07.040> with 10:15:08.030 --> 10:15:08.040 align:start position:0% this address here and we end up with 10:15:08.040 --> 10:15:11.030 align:start position:0% this address here and we end up with this<10:15:08.276> global<10:15:08.700> unicass<10:15:09.300> address<10:15:09.540> here 10:15:11.030 --> 10:15:11.040 align:start position:0% this global unicass address here 10:15:11.040 --> 10:15:13.550 align:start position:0% this global unicass address here and<10:15:11.460> you<10:15:11.700> can<10:15:11.880> see<10:15:12.240> already<10:15:12.596> we've<10:15:13.080> got<10:15:13.256> the 10:15:13.550 --> 10:15:13.560 align:start position:0% and you can see already we've got the 10:15:13.560 --> 10:15:15.170 align:start position:0% and you can see already we've got the fffe 10:15:15.170 --> 10:15:15.180 align:start position:0% fffe 10:15:15.180 --> 10:15:16.906 align:start position:0% fffe created<10:15:15.960> here 10:15:16.906 --> 10:15:16.916 align:start position:0% created here 10:15:16.916 --> 10:15:19.970 align:start position:0% created here so<10:15:17.820> and<10:15:18.300> because<10:15:18.720> it's<10:15:19.080> it<10:15:19.500> might<10:15:19.740> not<10:15:19.860> show 10:15:19.970 --> 10:15:19.980 align:start position:0% so and because it's it might not show 10:15:19.980 --> 10:15:20.830 align:start position:0% so and because it's it might not show you<10:15:20.096> another 10:15:20.830 --> 10:15:20.840 align:start position:0% you another 10:15:20.840 --> 10:15:23.510 align:start position:0% you another vendors<10:15:21.840> but<10:15:22.436> you<10:15:22.620> can<10:15:22.740> see<10:15:22.916> here<10:15:23.160> there's<10:15:23.400> a 10:15:23.510 --> 10:15:23.520 align:start position:0% vendors but you can see here there's a 10:15:23.520 --> 10:15:26.690 align:start position:0% vendors but you can see here there's a clue<10:15:23.700> it<10:15:23.880> says<10:15:24.060> eui<10:15:24.660> so<10:15:25.320> we<10:15:25.436> know<10:15:25.620> eui<10:15:26.160> 64<10:15:26.520> is 10:15:26.690 --> 10:15:26.700 align:start position:0% clue it says eui so we know eui 64 is 10:15:26.700 --> 10:15:27.950 align:start position:0% clue it says eui so we know eui 64 is addressing 10:15:27.950 --> 10:15:27.960 align:start position:0% addressing 10:15:27.960 --> 10:15:32.266 align:start position:0% addressing well<10:15:28.380> C2<10:15:28.860> in<10:15:29.040> decimal<10:15:29.460> is<10:15:29.640> 192. 10:15:32.266 --> 10:15:32.276 align:start position:0% well C2 in decimal is 192. 10:15:32.276 --> 10:15:36.470 align:start position:0% well C2 in decimal is 192. or<10:15:33.120> um<10:15:33.120> in<10:15:33.360> binary<10:15:33.840> here<10:15:34.740> one<10:15:35.460> one<10:15:35.700> zero<10:15:36.120> zero 10:15:36.470 --> 10:15:36.480 align:start position:0% or um in binary here one one zero zero 10:15:36.480 --> 10:15:40.730 align:start position:0% or um in binary here one one zero zero double<10:15:37.320> one<10:15:37.680> double<10:15:37.980> zero<10:15:38.580> in<10:15:39.240> hexadecimal<10:15:40.080> is 10:15:40.730 --> 10:15:40.740 align:start position:0% double one double zero in hexadecimal is 10:15:40.740 --> 10:15:41.810 align:start position:0% double one double zero in hexadecimal is C 10:15:41.810 --> 10:15:41.820 align:start position:0% C 10:15:41.820 --> 10:15:44.570 align:start position:0% C and<10:15:42.360> if<10:15:42.540> you've<10:15:42.720> just<10:15:42.840> got<10:15:43.020> a<10:15:43.200> one<10:15:43.436> in<10:15:43.916> the<10:15:44.160> uh 10:15:44.570 --> 10:15:44.580 align:start position:0% and if you've just got a one in the uh 10:15:44.580 --> 10:15:48.830 align:start position:0% and if you've just got a one in the uh two<10:15:45.000> the<10:15:45.360> two<10:15:45.596> column<10:15:45.900> here<10:15:46.140> so<10:15:46.500> one<10:15:47.220> two<10:15:47.840> four 10:15:48.830 --> 10:15:48.840 align:start position:0% two the two column here so one two four 10:15:48.840 --> 10:15:53.150 align:start position:0% two the two column here so one two four eight<10:15:49.560> you<10:15:50.276> can<10:15:50.400> see<10:15:50.640> uh<10:15:51.480> that's<10:15:51.776> a<10:15:52.080> two 10:15:53.150 --> 10:15:53.160 align:start position:0% eight you can see uh that's a two 10:15:53.160 --> 10:15:57.050 align:start position:0% eight you can see uh that's a two see<10:15:53.880> in<10:15:54.620> hexadecimal<10:15:55.620> is<10:15:55.740> 12<10:15:55.980> so<10:15:56.340> we've<10:15:56.520> got<10:15:56.640> 8 10:15:57.050 --> 10:15:57.060 align:start position:0% see in hexadecimal is 12 so we've got 8 10:15:57.060 --> 10:16:00.710 align:start position:0% see in hexadecimal is 12 so we've got 8 9<10:15:57.660> 10<10:15:57.900> 11<10:15:58.140> 12.<10:15:58.800> so<10:15:59.520> I<10:15:59.820> think<10:15:59.936> we've<10:16:00.180> covered<10:16:00.416> hex 10:16:00.710 --> 10:16:00.720 align:start position:0% 9 10 11 12. so I think we've covered hex 10:16:00.720 --> 10:16:04.010 align:start position:0% 9 10 11 12. so I think we've covered hex earlier<10:16:01.080> so<10:16:01.916> you<10:16:02.040> swap<10:16:02.340> the<10:16:02.520> seventh<10:16:02.936> bit 10:16:04.010 --> 10:16:04.020 align:start position:0% earlier so you swap the seventh bit 10:16:04.020 --> 10:16:08.510 align:start position:0% earlier so you swap the seventh bit so<10:16:05.000> one<10:16:06.000> two<10:16:06.540> three<10:16:07.080> four<10:16:07.500> five<10:16:07.860> six<10:16:08.220> seven 10:16:08.510 --> 10:16:08.520 align:start position:0% so one two three four five six seven 10:16:08.520 --> 10:16:10.670 align:start position:0% so one two three four five six seven this<10:16:09.240> bit<10:16:09.416> has<10:16:09.720> to<10:16:09.840> be<10:16:09.960> swapped<10:16:10.380> if<10:16:10.560> we're 10:16:10.670 --> 10:16:10.680 align:start position:0% this bit has to be swapped if we're 10:16:10.680 --> 10:16:13.246 align:start position:0% this bit has to be swapped if we're doing<10:16:10.860> the<10:16:11.040> UI<10:16:11.400> 64. 10:16:13.246 --> 10:16:13.256 align:start position:0% doing the UI 64. 10:16:13.256 --> 10:16:16.490 align:start position:0% doing the UI 64. and<10:16:13.860> then<10:16:14.040> it<10:16:14.340> becomes<10:16:14.820> a<10:16:15.120> zero<10:16:15.596> if<10:16:16.080> you<10:16:16.256> work 10:16:16.490 --> 10:16:16.500 align:start position:0% and then it becomes a zero if you work 10:16:16.500 --> 10:16:19.190 align:start position:0% and then it becomes a zero if you work this<10:16:16.740> out<10:16:16.916> zero<10:16:17.460> zero<10:16:17.756> zero<10:16:18.060> zero<10:16:18.480> the<10:16:19.020> second 10:16:19.190 --> 10:16:19.200 align:start position:0% this out zero zero zero zero the second 10:16:19.200 --> 10:16:25.010 align:start position:0% this out zero zero zero zero the second part<10:16:19.560> is<10:16:20.040> uh<10:16:20.700> C<10:16:21.120> zero<10:16:21.776> so<10:16:22.620> here<10:16:22.916> we<10:16:23.096> go<10:16:23.276> c0<10:16:24.240> and 10:16:25.010 --> 10:16:25.020 align:start position:0% part is uh C zero so here we go c0 and 10:16:25.020 --> 10:16:27.230 align:start position:0% part is uh C zero so here we go c0 and then<10:16:25.140> it<10:16:25.320> carries<10:16:25.620> on<10:16:25.800> as<10:16:26.040> normal<10:16:26.276> zero<10:16:26.880> zero 10:16:27.230 --> 10:16:27.240 align:start position:0% then it carries on as normal zero zero 10:16:27.240 --> 10:16:29.150 align:start position:0% then it carries on as normal zero zero instead<10:16:27.720> of<10:16:27.840> C2 10:16:29.150 --> 10:16:29.160 align:start position:0% instead of C2 10:16:29.160 --> 10:16:30.950 align:start position:0% instead of C2 so<10:16:29.640> I<10:16:29.756> know<10:16:30.000> it's<10:16:30.180> a<10:16:30.240> lot<10:16:30.360> to<10:16:30.480> get<10:16:30.660> your<10:16:30.776> head 10:16:30.950 --> 10:16:30.960 align:start position:0% so I know it's a lot to get your head 10:16:30.960 --> 10:16:32.746 align:start position:0% so I know it's a lot to get your head around<10:16:31.140> just<10:16:31.500> practice<10:16:31.740> it<10:16:32.040> watch<10:16:32.400> this<10:16:32.580> over 10:16:32.746 --> 10:16:32.756 align:start position:0% around just practice it watch this over 10:16:32.756 --> 10:16:34.246 align:start position:0% around just practice it watch this over a<10:16:33.000> few<10:16:33.120> times<10:16:33.300> and<10:16:33.540> then<10:16:33.660> practice<10:16:33.840> some<10:16:34.080> of 10:16:34.246 --> 10:16:34.256 align:start position:0% a few times and then practice some of 10:16:34.256 --> 10:16:36.766 align:start position:0% a few times and then practice some of your<10:16:34.320> own<10:16:34.436> examples 10:16:36.766 --> 10:16:36.776 align:start position:0% your own examples 10:16:36.776 --> 10:16:39.050 align:start position:0% your own examples applying<10:16:37.436> it<10:16:37.620> enter<10:16:37.916> your<10:16:38.220> desired<10:16:38.700> subnet 10:16:39.050 --> 10:16:39.060 align:start position:0% applying it enter your desired subnet 10:16:39.060 --> 10:16:43.310 align:start position:0% applying it enter your desired subnet and<10:16:39.360> then<10:16:39.540> add<10:16:39.840> the<10:16:40.080> command<10:16:40.620> the<10:16:41.276> tag<10:16:41.596> eui<10:16:42.596> 64. 10:16:43.310 --> 10:16:43.320 align:start position:0% and then add the command the tag eui 64. 10:16:43.320 --> 10:16:45.230 align:start position:0% and then add the command the tag eui 64. this<10:16:43.680> is<10:16:43.740> how<10:16:43.916> you<10:16:44.040> do<10:16:44.160> it<10:16:44.276> in<10:16:44.400> Cisco<10:16:44.820> you<10:16:45.180> won't 10:16:45.230 --> 10:16:45.240 align:start position:0% this is how you do it in Cisco you won't 10:16:45.240 --> 10:16:47.630 align:start position:0% this is how you do it in Cisco you won't be<10:16:45.416> asked<10:16:45.720> about<10:16:45.776> vendors<10:16:46.436> or<10:16:47.096> how<10:16:47.276> to<10:16:47.400> apply 10:16:47.630 --> 10:16:47.640 align:start position:0% be asked about vendors or how to apply 10:16:47.640 --> 10:16:49.070 align:start position:0% be asked about vendors or how to apply it<10:16:47.756> I'm<10:16:47.880> sure<10:16:48.060> I'm<10:16:48.240> just<10:16:48.416> telling<10:16:48.660> you<10:16:48.720> how<10:16:48.960> it 10:16:49.070 --> 10:16:49.080 align:start position:0% it I'm sure I'm just telling you how it 10:16:49.080 --> 10:16:52.190 align:start position:0% it I'm sure I'm just telling you how it works<10:16:49.460> so<10:16:50.460> I've<10:16:50.936> added<10:16:51.360> this<10:16:51.416> address<10:16:51.596> I<10:16:51.960> want 10:16:52.190 --> 10:16:52.200 align:start position:0% works so I've added this address I want 10:16:52.200 --> 10:16:54.530 align:start position:0% works so I've added this address I want to<10:16:52.320> say<10:16:52.500> we're<10:16:52.860> using<10:16:53.756> um 10:16:54.530 --> 10:16:54.540 align:start position:0% to say we're using um 10:16:54.540 --> 10:16:59.030 align:start position:0% to say we're using um this<10:16:55.460> subnet<10:16:56.460> here<10:16:56.700> this<10:16:57.060> address<10:16:57.500> and<10:16:58.500> uh 10:16:59.030 --> 10:16:59.040 align:start position:0% this subnet here this address and uh 10:16:59.040 --> 10:17:02.210 align:start position:0% this subnet here this address and uh double<10:16:59.640> colon<10:17:00.240> so<10:17:01.140> I<10:17:01.320> don't<10:17:01.560> care<10:17:01.680> what<10:17:01.860> goes 10:17:02.210 --> 10:17:02.220 align:start position:0% double colon so I don't care what goes 10:17:02.220 --> 10:17:03.010 align:start position:0% double colon so I don't care what goes there 10:17:03.010 --> 10:17:03.020 align:start position:0% there 10:17:03.020 --> 10:17:05.746 align:start position:0% there 64<10:17:04.020> and<10:17:04.500> then<10:17:04.620> I<10:17:04.740> add<10:17:04.860> the<10:17:05.040> tag<10:17:05.276> basically 10:17:05.746 --> 10:17:05.756 align:start position:0% 64 and then I add the tag basically 10:17:05.756 --> 10:17:11.170 align:start position:0% 64 and then I add the tag basically saying<10:17:06.180> you<10:17:07.560> um<10:17:07.620> you<10:17:08.460> allocate 10:17:11.170 --> 10:17:11.180 align:start position:0% 10:17:11.180 --> 10:17:15.830 align:start position:0% uh<10:17:12.180> using<10:17:12.720> the<10:17:13.080> MAC<10:17:13.916> address<10:17:14.300> plus<10:17:15.300> the 10:17:15.830 --> 10:17:15.840 align:start position:0% uh using the MAC address plus the 10:17:15.840 --> 10:17:18.290 align:start position:0% uh using the MAC address plus the seventh 10:17:18.290 --> 10:17:18.300 align:start position:0% seventh 10:17:18.300 --> 10:17:21.350 align:start position:0% seventh bit<10:17:18.840> rule<10:17:19.380> which<10:17:19.860> will<10:17:20.096> swap<10:17:20.520> the<10:17:21.060> seventh 10:17:21.350 --> 10:17:21.360 align:start position:0% bit rule which will swap the seventh 10:17:21.360 --> 10:17:23.746 align:start position:0% bit rule which will swap the seventh most<10:17:21.480> significant<10:17:21.960> bit<10:17:22.200> from<10:17:22.800> a<10:17:22.916> zero<10:17:23.340> to<10:17:23.400> one 10:17:23.746 --> 10:17:23.756 align:start position:0% most significant bit from a zero to one 10:17:23.756 --> 10:17:30.110 align:start position:0% most significant bit from a zero to one or<10:17:24.416> one<10:17:24.776> to<10:17:24.900> a<10:17:25.080> zero 10:17:30.110 --> 10:17:30.120 align:start position:0% 10:17:30.120 --> 10:17:31.850 align:start position:0% and<10:17:30.480> here's<10:17:30.776> the<10:17:30.900> command<10:17:31.200> on<10:17:31.500> an<10:17:31.620> actual 10:17:31.850 --> 10:17:31.860 align:start position:0% and here's the command on an actual 10:17:31.860 --> 10:17:34.010 align:start position:0% and here's the command on an actual router<10:17:32.276> so<10:17:32.580> yeah<10:17:32.700> you<10:17:32.936> have<10:17:33.120> to<10:17:33.300> you<10:17:33.900> can't 10:17:34.010 --> 10:17:34.020 align:start position:0% router so yeah you have to you can't 10:17:34.020 --> 10:17:36.290 align:start position:0% router so yeah you have to you can't just<10:17:34.200> say<10:17:34.500> create<10:17:35.160> the<10:17:35.400> entire<10:17:35.756> address<10:17:36.000> for 10:17:36.290 --> 10:17:36.300 align:start position:0% just say create the entire address for 10:17:36.300 --> 10:17:38.746 align:start position:0% just say create the entire address for the<10:17:36.416> routable<10:17:36.776> address 10:17:38.746 --> 10:17:38.756 align:start position:0% the routable address 10:17:38.756 --> 10:17:43.450 align:start position:0% the routable address um<10:17:38.820> you<10:17:39.416> have<10:17:39.540> to<10:17:39.660> add<10:17:39.720> this<10:17:39.960> tag<10:17:40.200> here 10:17:43.450 --> 10:17:43.460 align:start position:0% 10:17:43.460 --> 10:17:46.310 align:start position:0% all<10:17:44.460> right<10:17:44.580> next<10:17:44.820> is<10:17:45.060> the<10:17:45.416> neighbor<10:17:45.660> Discovery 10:17:46.310 --> 10:17:46.320 align:start position:0% all right next is the neighbor Discovery 10:17:46.320 --> 10:17:49.310 align:start position:0% all right next is the neighbor Discovery protocol<10:17:46.800> which<10:17:47.220> is<10:17:47.276> a<10:17:47.460> major<10:17:47.640> feature<10:17:48.180> of<10:17:48.660> uh 10:17:49.310 --> 10:17:49.320 align:start position:0% protocol which is a major feature of uh 10:17:49.320 --> 10:17:53.330 align:start position:0% protocol which is a major feature of uh of<10:17:50.096> IPv6<10:17:50.820> this<10:17:51.596> allows<10:17:52.080> other<10:17:52.436> routers<10:17:52.980> on<10:17:53.220> the 10:17:53.330 --> 10:17:53.340 align:start position:0% of IPv6 this allows other routers on the 10:17:53.340 --> 10:17:54.950 align:start position:0% of IPv6 this allows other routers on the link<10:17:53.460> to<10:17:53.640> be<10:17:53.820> discovered<10:17:54.240> there's<10:17:54.720> a<10:17:54.900> couple 10:17:54.950 --> 10:17:54.960 align:start position:0% link to be discovered there's a couple 10:17:54.960 --> 10:17:56.926 align:start position:0% link to be discovered there's a couple of<10:17:55.080> messages<10:17:55.380> you<10:17:55.800> you<10:17:56.040> need<10:17:56.276> to<10:17:56.400> be<10:17:56.520> aware<10:17:56.756> of 10:17:56.926 --> 10:17:56.936 align:start position:0% of messages you you need to be aware of 10:17:56.936 --> 10:18:01.490 align:start position:0% of messages you you need to be aware of which<10:17:57.720> is<10:17:57.900> RS<10:17:58.640> router<10:17:59.640> solicitation<10:18:00.300> like<10:18:01.200> are 10:18:01.490 --> 10:18:01.500 align:start position:0% which is RS router solicitation like are 10:18:01.500 --> 10:18:04.010 align:start position:0% which is RS router solicitation like are are<10:18:01.800> any<10:18:02.040> routers<10:18:02.520> on<10:18:02.700> the<10:18:02.820> link<10:18:03.000> this<10:18:03.720> is<10:18:03.840> the 10:18:04.010 --> 10:18:04.020 align:start position:0% are any routers on the link this is the 10:18:04.020 --> 10:18:06.230 align:start position:0% are any routers on the link this is the router<10:18:04.436> solicitation<10:18:05.096> message 10:18:06.230 --> 10:18:06.240 align:start position:0% router solicitation message 10:18:06.240 --> 10:18:08.210 align:start position:0% router solicitation message and<10:18:06.596> it's<10:18:06.720> sent<10:18:06.960> out<10:18:07.200> saying<10:18:07.620> what<10:18:07.740> what<10:18:07.980> else 10:18:08.210 --> 10:18:08.220 align:start position:0% and it's sent out saying what what else 10:18:08.220 --> 10:18:10.130 align:start position:0% and it's sent out saying what what else is<10:18:08.400> here 10:18:10.130 --> 10:18:10.140 align:start position:0% is here 10:18:10.140 --> 10:18:13.730 align:start position:0% is here the<10:18:10.560> router<10:18:10.980> advertisement<10:18:11.660> is<10:18:12.660> the<10:18:13.140> reply 10:18:13.730 --> 10:18:13.740 align:start position:0% the router advertisement is the reply 10:18:13.740 --> 10:18:17.390 align:start position:0% the router advertisement is the reply you'll<10:18:14.160> get<10:18:14.276> from<10:18:14.580> the<10:18:14.756> routers<10:18:15.240> IPv6<10:18:16.080> routers 10:18:17.390 --> 10:18:17.400 align:start position:0% you'll get from the routers IPv6 routers 10:18:17.400 --> 10:18:23.030 align:start position:0% you'll get from the routers IPv6 routers uh<10:18:18.240> yep<10:18:18.840> I'm<10:18:19.080> here<10:18:19.460> R<10:18:20.460> A<10:18:20.756> I'm<10:18:21.300> here 10:18:23.030 --> 10:18:23.040 align:start position:0% uh yep I'm here R A I'm here 10:18:23.040 --> 10:18:25.426 align:start position:0% uh yep I'm here R A I'm here it<10:18:23.460> just<10:18:23.580> give<10:18:23.756> us<10:18:23.960> prefixes<10:18:24.960> so<10:18:25.200> whatever 10:18:25.426 --> 10:18:25.436 align:start position:0% it just give us prefixes so whatever 10:18:25.436 --> 10:18:33.170 align:start position:0% it just give us prefixes so whatever your<10:18:26.096> prefix<10:18:26.756> is<10:18:27.000> on<10:18:27.180> the<10:18:27.300> network 10:18:33.170 --> 10:18:33.180 align:start position:0% 10:18:33.180 --> 10:18:35.990 align:start position:0% Etc<10:18:33.620> these<10:18:34.620> routers<10:18:34.916> will<10:18:35.160> say<10:18:35.340> we're<10:18:35.640> using 10:18:35.990 --> 10:18:36.000 align:start position:0% Etc these routers will say we're using 10:18:36.000 --> 10:18:38.266 align:start position:0% Etc these routers will say we're using this<10:18:36.240> prefix<10:18:36.720> and<10:18:37.200> then<10:18:37.320> this<10:18:37.680> will<10:18:37.980> be<10:18:38.096> able 10:18:38.266 --> 10:18:38.276 align:start position:0% this prefix and then this will be able 10:18:38.276 --> 10:18:40.610 align:start position:0% this prefix and then this will be able to<10:18:38.400> Auto<10:18:38.880> allocate<10:18:39.416> an<10:18:39.596> address<10:18:39.776> so<10:18:40.320> it<10:18:40.500> can 10:18:40.610 --> 10:18:40.620 align:start position:0% to Auto allocate an address so it can 10:18:40.620 --> 10:18:44.150 align:start position:0% to Auto allocate an address so it can communicate<10:18:41.160> communicate<10:18:41.700> on<10:18:41.820> the<10:18:41.936> subnet 10:18:44.150 --> 10:18:44.160 align:start position:0% communicate communicate on the subnet 10:18:44.160 --> 10:18:46.970 align:start position:0% communicate communicate on the subnet so<10:18:44.520> this<10:18:44.700> replaces<10:18:45.300> our<10:18:45.660> we<10:18:46.020> don't<10:18:46.140> have<10:18:46.320> ARP 10:18:46.970 --> 10:18:46.980 align:start position:0% so this replaces our we don't have ARP 10:18:46.980 --> 10:18:51.650 align:start position:0% so this replaces our we don't have ARP working<10:18:47.640> on<10:18:48.120> the<10:18:48.480> uh<10:18:48.960> on<10:18:49.200> IPv6<10:18:49.860> subnets 10:18:51.650 --> 10:18:51.660 align:start position:0% working on the uh on IPv6 subnets 10:18:51.660 --> 10:18:53.450 align:start position:0% working on the uh on IPv6 subnets also<10:18:52.560> works<10:18:52.860> to<10:18:52.916> duplicate<10:18:53.276> address 10:18:53.450 --> 10:18:53.460 align:start position:0% also works to duplicate address 10:18:53.460 --> 10:18:55.190 align:start position:0% also works to duplicate address detection<10:18:54.000> which<10:18:54.360> I've<10:18:54.480> already<10:18:54.660> mentioned 10:18:55.190 --> 10:18:55.200 align:start position:0% detection which I've already mentioned 10:18:55.200 --> 10:18:58.970 align:start position:0% detection which I've already mentioned the<10:18:56.160> device<10:18:56.340> the<10:18:56.640> ipvx<10:18:57.300> ibv6<10:18:58.256> device<10:18:58.500> will<10:18:58.800> say 10:18:58.970 --> 10:18:58.980 align:start position:0% the device the ipvx ibv6 device will say 10:18:58.980 --> 10:19:01.670 align:start position:0% the device the ipvx ibv6 device will say I<10:18:59.160> want<10:18:59.340> to<10:18:59.460> use<10:18:59.580> address<10:18:59.880> X<10:19:00.360> are<10:19:01.140> any<10:19:01.380> of<10:19:01.560> you 10:19:01.670 --> 10:19:01.680 align:start position:0% I want to use address X are any of you 10:19:01.680 --> 10:19:03.830 align:start position:0% I want to use address X are any of you using<10:19:02.096> it<10:19:02.220> and<10:19:02.460> then<10:19:02.640> there'll<10:19:02.936> be<10:19:03.000> a<10:19:03.180> reply<10:19:03.720> if 10:19:03.830 --> 10:19:03.840 align:start position:0% using it and then there'll be a reply if 10:19:03.840 --> 10:19:06.950 align:start position:0% using it and then there'll be a reply if it<10:19:04.020> is<10:19:04.080> in<10:19:04.320> use 10:19:06.950 --> 10:19:06.960 align:start position:0% 10:19:06.960 --> 10:19:09.710 align:start position:0% so<10:19:07.320> there<10:19:07.500> was<10:19:07.740> solicitation<10:19:08.416> asking<10:19:09.416> for<10:19:09.596> a 10:19:09.710 --> 10:19:09.720 align:start position:0% so there was solicitation asking for a 10:19:09.720 --> 10:19:11.510 align:start position:0% so there was solicitation asking for a neighbor's<10:19:10.140> information 10:19:11.510 --> 10:19:11.520 align:start position:0% neighbor's information 10:19:11.520 --> 10:19:13.070 align:start position:0% neighbor's information their<10:19:11.880> neighbor<10:19:12.120> advertisement<10:19:12.776> you 10:19:13.070 --> 10:19:13.080 align:start position:0% their neighbor advertisement you 10:19:13.080 --> 10:19:16.246 align:start position:0% their neighbor advertisement you advertise<10:19:13.620> yourself<10:19:13.860> out<10:19:14.340> to<10:19:14.580> Neighbors 10:19:16.246 --> 10:19:16.256 align:start position:0% advertise yourself out to Neighbors 10:19:16.256 --> 10:19:18.650 align:start position:0% advertise yourself out to Neighbors the<10:19:16.980> solicitation<10:19:17.880> asks<10:19:18.416> for<10:19:18.480> information 10:19:18.650 --> 10:19:18.660 align:start position:0% the solicitation asks for information 10:19:18.660 --> 10:19:20.510 align:start position:0% the solicitation asks for information about<10:19:19.080> local<10:19:19.380> routers<10:19:19.916> these<10:19:20.160> are<10:19:20.276> the<10:19:20.340> four 10:19:20.510 --> 10:19:20.520 align:start position:0% about local routers these are the four 10:19:20.520 --> 10:19:22.906 align:start position:0% about local routers these are the four types<10:19:20.936> that<10:19:21.120> you<10:19:21.240> need<10:19:21.360> to<10:19:21.416> know<10:19:21.540> about<10:19:21.916> router 10:19:22.906 --> 10:19:22.916 align:start position:0% types that you need to know about router 10:19:22.916 --> 10:19:24.710 align:start position:0% types that you need to know about router advertisement<10:19:23.460> advertise<10:19:24.120> yourself<10:19:24.360> as 10:19:24.710 --> 10:19:24.720 align:start position:0% advertisement advertise yourself as 10:19:24.720 --> 10:19:26.690 align:start position:0% advertisement advertise yourself as active<10:19:25.080> these<10:19:25.560> are<10:19:25.620> the<10:19:25.740> four<10:19:25.860> types<10:19:26.276> so<10:19:26.400> make 10:19:26.690 --> 10:19:26.700 align:start position:0% active these are the four types so make 10:19:26.700 --> 10:19:29.630 align:start position:0% active these are the four types so make a<10:19:26.880> note<10:19:27.000> of<10:19:27.180> them 10:19:29.630 --> 10:19:29.640 align:start position:0% 10:19:29.640 --> 10:19:31.490 align:start position:0% the<10:19:30.180> idea<10:19:30.540> I've<10:19:30.660> already<10:19:30.840> mentioned<10:19:31.256> the 10:19:31.490 --> 10:19:31.500 align:start position:0% the idea I've already mentioned the 10:19:31.500 --> 10:19:33.050 align:start position:0% the idea I've already mentioned the neighbor<10:19:31.620> advertisements<10:19:32.520> are<10:19:32.640> sent<10:19:32.880> to 10:19:33.050 --> 10:19:33.060 align:start position:0% neighbor advertisements are sent to 10:19:33.060 --> 10:19:35.690 align:start position:0% neighbor advertisements are sent to check<10:19:33.300> if<10:19:33.480> your<10:19:33.720> address<10:19:34.020> is<10:19:34.320> unique<10:19:34.740> this<10:19:35.580> is 10:19:35.690 --> 10:19:35.700 align:start position:0% check if your address is unique this is 10:19:35.700 --> 10:19:38.630 align:start position:0% check if your address is unique this is the<10:19:35.880> address<10:19:35.936> it's<10:19:36.300> sent<10:19:36.540> to<10:19:36.776> which<10:19:37.320> is<10:19:37.740> the<10:19:38.580> um 10:19:38.630 --> 10:19:38.640 align:start position:0% the address it's sent to which is the um 10:19:38.640 --> 10:19:40.190 align:start position:0% the address it's sent to which is the um save<10:19:38.936> as<10:19:39.120> a<10:19:39.240> broadcast<10:19:39.360> address<10:19:39.720> but<10:19:40.080> we're 10:19:40.190 --> 10:19:40.200 align:start position:0% save as a broadcast address but we're 10:19:40.200 --> 10:19:44.926 align:start position:0% save as a broadcast address but we're multi-cat<10:19:40.800> we're<10:19:41.160> multicasting<10:19:41.936> in<10:19:42.776> IPv6 10:19:44.926 --> 10:19:44.936 align:start position:0% multi-cat we're multicasting in IPv6 10:19:44.936 --> 10:19:46.906 align:start position:0% multi-cat we're multicasting in IPv6 no<10:19:45.360> reply<10:19:45.720> means<10:19:46.080> your<10:19:46.200> address<10:19:46.380> is<10:19:46.680> available 10:19:46.906 --> 10:19:46.916 align:start position:0% no reply means your address is available 10:19:46.916 --> 10:19:52.370 align:start position:0% no reply means your address is available to<10:19:47.340> use<10:19:47.580> the<10:19:48.240> amount<10:19:48.540> of<10:19:48.660> air<10:19:48.840> seconds 10:19:52.370 --> 10:19:52.380 align:start position:0% 10:19:52.380 --> 10:19:54.350 align:start position:0% should<10:19:52.860> vary<10:19:53.096> from<10:19:53.340> vendor<10:19:53.756> to<10:19:53.820> vendor<10:19:54.240> I 10:19:54.350 --> 10:19:54.360 align:start position:0% should vary from vendor to vendor I 10:19:54.360 --> 10:19:56.570 align:start position:0% should vary from vendor to vendor I haven't<10:19:54.480> read<10:19:54.720> the<10:19:54.840> RFC<10:19:55.320> actually<10:19:55.620> but<10:19:56.220> if<10:19:56.460> you 10:19:56.570 --> 10:19:56.580 align:start position:0% haven't read the RFC actually but if you 10:19:56.580 --> 10:19:59.950 align:start position:0% haven't read the RFC actually but if you really<10:19:56.700> wanted<10:19:56.936> to<10:19:57.120> you<10:19:57.300> can<10:19:57.480> read<10:19:57.596> it 10:19:59.950 --> 10:19:59.960 align:start position:0% 10:19:59.960 --> 10:20:02.690 align:start position:0% so<10:20:00.960> you<10:20:01.560> can<10:20:01.680> see<10:20:01.800> the<10:20:01.916> advertisement<10:20:02.460> is 10:20:02.690 --> 10:20:02.700 align:start position:0% so you can see the advertisement is 10:20:02.700 --> 10:20:05.086 align:start position:0% so you can see the advertisement is going<10:20:02.880> out<10:20:03.120> with<10:20:03.360> this<10:20:03.540> address<10:20:03.720> reply<10:20:04.620> if<10:20:04.860> you 10:20:05.086 --> 10:20:05.096 align:start position:0% going out with this address reply if you 10:20:05.096 --> 10:20:07.190 align:start position:0% going out with this address reply if you are<10:20:05.276> this<10:20:05.700> address 10:20:07.190 --> 10:20:07.200 align:start position:0% are this address 10:20:07.200 --> 10:20:11.330 align:start position:0% are this address using<10:20:07.800> the<10:20:07.936> icmpv6<10:20:08.936> packet 10:20:11.330 --> 10:20:11.340 align:start position:0% using the icmpv6 packet 10:20:11.340 --> 10:20:13.906 align:start position:0% using the icmpv6 packet um<10:20:11.460> and<10:20:11.880> then<10:20:12.060> the 10:20:13.906 --> 10:20:13.916 align:start position:0% um and then the 10:20:13.916 --> 10:20:16.790 align:start position:0% um and then the advertisement<10:20:14.756> here<10:20:15.120> I<10:20:15.660> am<10:20:15.840> this<10:20:16.320> address<10:20:16.500> so 10:20:16.790 --> 10:20:16.800 align:start position:0% advertisement here I am this address so 10:20:16.800 --> 10:20:20.470 align:start position:0% advertisement here I am this address so basically<10:20:17.160> you<10:20:17.400> can't<10:20:17.580> use<10:20:17.820> it 10:20:20.470 --> 10:20:20.480 align:start position:0% 10:20:20.480 --> 10:20:25.130 align:start position:0% DHCP<10:20:21.480> version<10:20:21.960> 6<10:20:22.320> is<10:20:22.620> used<10:20:22.860> for<10:20:23.300> IPv6<10:20:24.300> this<10:20:25.020> is 10:20:25.130 --> 10:20:25.140 align:start position:0% DHCP version 6 is used for IPv6 this is 10:20:25.140 --> 10:20:27.650 align:start position:0% DHCP version 6 is used for IPv6 this is for<10:20:25.320> auto<10:20:25.560> allocation<10:20:26.096> of<10:20:26.276> addresses 10:20:27.650 --> 10:20:27.660 align:start position:0% for auto allocation of addresses 10:20:27.660 --> 10:20:29.926 align:start position:0% for auto allocation of addresses also<10:20:28.380> used<10:20:28.560> with<10:20:28.860> uh<10:20:29.276> it's<10:20:29.580> used<10:20:29.756> in 10:20:29.926 --> 10:20:29.936 align:start position:0% also used with uh it's used in 10:20:29.936 --> 10:20:33.406 align:start position:0% also used with uh it's used in conjunction<10:20:30.300> with<10:20:30.596> DNS<10:20:31.080> for<10:20:31.380> IPv6 10:20:33.406 --> 10:20:33.416 align:start position:0% conjunction with DNS for IPv6 10:20:33.416 --> 10:20:35.870 align:start position:0% conjunction with DNS for IPv6 and<10:20:34.380> here's<10:20:34.740> the<10:20:34.800> RSC<10:20:35.276> if<10:20:35.460> you've<10:20:35.640> got<10:20:35.756> some 10:20:35.870 --> 10:20:35.880 align:start position:0% and here's the RSC if you've got some 10:20:35.880 --> 10:20:38.926 align:start position:0% and here's the RSC if you've got some spare<10:20:36.180> time<10:20:36.300> in<10:20:36.540> your<10:20:36.660> hands<10:20:37.160> allocate<10:20:38.160> IPv6 10:20:38.926 --> 10:20:38.936 align:start position:0% spare time in your hands allocate IPv6 10:20:38.936 --> 10:20:42.650 align:start position:0% spare time in your hands allocate IPv6 information<10:20:39.240> to<10:20:39.660> hose<10:20:39.960> obviously<10:20:40.936> the<10:20:41.936> IPv6 10:20:42.650 --> 10:20:42.660 align:start position:0% information to hose obviously the IPv6 10:20:42.660 --> 10:20:46.790 align:start position:0% information to hose obviously the IPv6 is<10:20:43.620> um 10:20:46.790 --> 10:20:46.800 align:start position:0% 10:20:46.800 --> 10:20:50.870 align:start position:0% the<10:20:47.340> Gateway<10:20:47.700> the<10:20:48.120> the<10:20:48.240> DNS<10:20:49.140> server 10:20:50.870 --> 10:20:50.880 align:start position:0% the Gateway the the DNS server 10:20:50.880 --> 10:20:55.550 align:start position:0% the Gateway the the DNS server and<10:20:51.480> another<10:20:51.900> DHCP<10:20:52.800> information 10:20:55.550 --> 10:20:55.560 align:start position:0% 10:20:55.560 --> 10:20:57.350 align:start position:0% host<10:20:55.916> can<10:20:56.220> request<10:20:56.520> it<10:20:56.640> with<10:20:56.820> an<10:20:56.936> outgoing 10:20:57.350 --> 10:20:57.360 align:start position:0% host can request it with an outgoing 10:20:57.360 --> 10:21:00.406 align:start position:0% host can request it with an outgoing router<10:20:57.900> advertisement<10:20:58.436> message 10:21:00.406 --> 10:21:00.416 align:start position:0% router advertisement message 10:21:00.416 --> 10:21:03.110 align:start position:0% router advertisement message allocated<10:21:01.320> and<10:21:01.436> requested<10:21:01.916> using<10:21:02.520> UDP<10:21:02.880> bear 10:21:03.110 --> 10:21:03.120 align:start position:0% allocated and requested using UDP bear 10:21:03.120 --> 10:21:04.370 align:start position:0% allocated and requested using UDP bear that<10:21:03.360> in<10:21:03.480> mind<10:21:03.660> because<10:21:03.840> some<10:21:04.020> people<10:21:04.140> think 10:21:04.370 --> 10:21:04.380 align:start position:0% that in mind because some people think 10:21:04.380 --> 10:21:10.490 align:start position:0% that in mind because some people think it's<10:21:04.500> TCP<10:21:05.220> it's<10:21:06.060> Port<10:21:06.436> 546<10:21:07.436> and<10:21:07.620> 547 10:21:10.490 --> 10:21:10.500 align:start position:0% 10:21:10.500 --> 10:21:12.650 align:start position:0% the<10:21:11.276> other<10:21:11.400> subject<10:21:11.820> you<10:21:11.936> need<10:21:12.180> to<10:21:12.300> be<10:21:12.416> aware 10:21:12.650 --> 10:21:12.660 align:start position:0% the other subject you need to be aware 10:21:12.660 --> 10:21:18.110 align:start position:0% the other subject you need to be aware of<10:21:12.840> now<10:21:13.200> is<10:21:13.560> if<10:21:13.800> you're<10:21:14.096> running<10:21:14.540> uh<10:21:15.916> IPv6<10:21:17.120> on 10:21:18.110 --> 10:21:18.120 align:start position:0% of now is if you're running uh IPv6 on 10:21:18.120 --> 10:21:21.110 align:start position:0% of now is if you're running uh IPv6 on your<10:21:18.300> network<10:21:18.540> and<10:21:19.256> then<10:21:19.380> ipv4<10:21:20.096> nobody<10:21:20.880> is 10:21:21.110 --> 10:21:21.120 align:start position:0% your network and then ipv4 nobody is 10:21:21.120 --> 10:21:22.010 align:start position:0% your network and then ipv4 nobody is going<10:21:21.300> to 10:21:22.010 --> 10:21:22.020 align:start position:0% going to 10:21:22.020 --> 10:21:25.810 align:start position:0% going to come<10:21:22.560> into<10:21:22.680> work<10:21:23.096> one<10:21:23.936> day<10:21:24.180> and<10:21:24.596> have<10:21:24.900> ipv4 10:21:25.810 --> 10:21:25.820 align:start position:0% come into work one day and have ipv4 10:21:25.820 --> 10:21:29.510 align:start position:0% come into work one day and have ipv4 taken<10:21:26.820> off<10:21:26.936> and<10:21:27.416> only<10:21:27.596> even<10:21:27.776> in<10:21:28.020> IPv6<10:21:28.800> you're 10:21:29.510 --> 10:21:29.520 align:start position:0% taken off and only even in IPv6 you're 10:21:29.520 --> 10:21:31.610 align:start position:0% taken off and only even in IPv6 you're going<10:21:29.700> to<10:21:29.820> have<10:21:30.000> a<10:21:30.416> transition<10:21:30.900> period<10:21:31.320> where 10:21:31.610 --> 10:21:31.620 align:start position:0% going to have a transition period where 10:21:31.620 --> 10:21:33.890 align:start position:0% going to have a transition period where you're<10:21:31.740> running<10:21:32.000> both<10:21:33.000> of<10:21:33.180> these<10:21:33.416> protocols 10:21:33.890 --> 10:21:33.900 align:start position:0% you're running both of these protocols 10:21:33.900 --> 10:21:35.890 align:start position:0% you're running both of these protocols so<10:21:34.020> what's<10:21:34.200> going<10:21:34.380> to<10:21:34.500> happen<10:21:34.620> is<10:21:34.860> somehow 10:21:35.890 --> 10:21:35.900 align:start position:0% so what's going to happen is somehow 10:21:35.900 --> 10:21:40.790 align:start position:0% so what's going to happen is somehow IPv6<10:21:36.900> host<10:21:37.860> reaches<10:21:38.460> an<10:21:38.640> ipv4<10:21:39.240> router<10:21:40.320> and 10:21:40.790 --> 10:21:40.800 align:start position:0% IPv6 host reaches an ipv4 router and 10:21:40.800 --> 10:21:43.490 align:start position:0% IPv6 host reaches an ipv4 router and what<10:21:40.980> you're<10:21:41.160> going<10:21:41.340> to<10:21:41.460> have<10:21:41.520> to<10:21:41.700> do 10:21:43.490 --> 10:21:43.500 align:start position:0% what you're going to have to do 10:21:43.500 --> 10:21:46.926 align:start position:0% what you're going to have to do is<10:21:44.040> tunnel<10:21:44.520> the<10:21:45.360> IPv6 10:21:46.926 --> 10:21:46.936 align:start position:0% is tunnel the IPv6 10:21:46.936 --> 10:21:51.230 align:start position:0% is tunnel the IPv6 information<10:21:47.936> inside 10:21:51.230 --> 10:21:51.240 align:start position:0% 10:21:51.240 --> 10:21:55.906 align:start position:0% an<10:21:52.040> ipv4<10:21:53.120> packet<10:21:54.120> with<10:21:54.300> a<10:21:54.416> header<10:21:54.840> and<10:21:55.680> the 10:21:55.906 --> 10:21:55.916 align:start position:0% an ipv4 packet with a header and the 10:21:55.916 --> 10:21:59.330 align:start position:0% an ipv4 packet with a header and the trailer<10:21:56.096> running<10:21:56.400> ipv4 10:21:59.330 --> 10:21:59.340 align:start position:0% 10:21:59.340 --> 10:22:02.390 align:start position:0% there's<10:21:59.756> a<10:21:59.936> few<10:22:00.060> versions<10:22:00.540> isotap 10:22:02.390 --> 10:22:02.400 align:start position:0% there's a few versions isotap 10:22:02.400 --> 10:22:03.890 align:start position:0% there's a few versions isotap uh 10:22:03.890 --> 10:22:03.900 align:start position:0% uh 10:22:03.900 --> 10:22:06.050 align:start position:0% uh 64<10:22:04.620> to<10:22:04.980> the<10:22:05.220> link 10:22:06.050 --> 10:22:06.060 align:start position:0% 64 to the link 10:22:06.060 --> 10:22:07.906 align:start position:0% 64 to the link dual<10:22:06.540> stack<10:22:06.776> is<10:22:06.960> when<10:22:07.140> you're<10:22:07.200> running<10:22:07.380> both 10:22:07.906 --> 10:22:07.916 align:start position:0% dual stack is when you're running both 10:22:07.916 --> 10:22:09.950 align:start position:0% dual stack is when you're running both at<10:22:08.640> the<10:22:08.756> same<10:22:08.880> time 10:22:09.950 --> 10:22:09.960 align:start position:0% at the same time 10:22:09.960 --> 10:22:13.010 align:start position:0% at the same time there's<10:22:10.436> a<10:22:10.680> static<10:22:11.040> to<10:22:11.220> null<10:22:11.520> I<10:22:12.180> think<10:22:12.480> yeah 10:22:13.010 --> 10:22:13.020 align:start position:0% there's a static to null I think yeah 10:22:13.020 --> 10:22:15.230 align:start position:0% there's a static to null I think yeah that's<10:22:13.256> different<10:22:13.436> to<10:22:13.680> GRE<10:22:14.060> you<10:22:15.060> don't<10:22:15.120> have 10:22:15.230 --> 10:22:15.240 align:start position:0% that's different to GRE you don't have 10:22:15.240 --> 10:22:16.730 align:start position:0% that's different to GRE you don't have to<10:22:15.360> know<10:22:15.540> the<10:22:15.720> config<10:22:16.080> so<10:22:16.320> don't<10:22:16.436> worry<10:22:16.620> about 10:22:16.730 --> 10:22:16.740 align:start position:0% to know the config so don't worry about 10:22:16.740 --> 10:22:18.890 align:start position:0% to know the config so don't worry about it<10:22:16.980> generic<10:22:17.580> routing<10:22:17.936> encapsulation<10:22:18.540> has 10:22:18.890 --> 10:22:18.900 align:start position:0% it generic routing encapsulation has 10:22:18.900 --> 10:22:20.810 align:start position:0% it generic routing encapsulation has been<10:22:19.080> around<10:22:19.200> a<10:22:19.436> long<10:22:19.620> time<10:22:19.800> but<10:22:20.340> you<10:22:20.520> can<10:22:20.640> use 10:22:20.810 --> 10:22:20.820 align:start position:0% been around a long time but you can use 10:22:20.820 --> 10:22:23.170 align:start position:0% been around a long time but you can use that<10:22:21.060> for<10:22:21.596> tunnel<10:22:21.900> in 10:22:23.170 --> 10:22:23.180 align:start position:0% that for tunnel in 10:22:23.180 --> 10:22:26.690 align:start position:0% that for tunnel in automatic<10:22:24.180> as<10:22:24.900> another<10:22:25.680> type<10:22:25.980> you<10:22:26.340> can<10:22:26.400> choose 10:22:26.690 --> 10:22:26.700 align:start position:0% automatic as another type you can choose 10:22:26.700 --> 10:22:28.310 align:start position:0% automatic as another type you can choose from 10:22:28.310 --> 10:22:28.320 align:start position:0% from 10:22:28.320 --> 10:22:30.170 align:start position:0% from if<10:22:28.800> you<10:22:28.916> want<10:22:29.040> to<10:22:29.160> study<10:22:29.460> more<10:22:29.580> I<10:22:29.820> recommend 10:22:30.170 --> 10:22:30.180 align:start position:0% if you want to study more I recommend 10:22:30.180 --> 10:22:32.990 align:start position:0% if you want to study more I recommend everyone<10:22:30.596> needs<10:22:31.320> to<10:22:31.380> do<10:22:31.560> about 10:22:32.990 --> 10:22:33.000 align:start position:0% everyone needs to do about 10:22:33.000 --> 10:22:35.450 align:start position:0% everyone needs to do about uh<10:22:33.776> four<10:22:34.020> hours 10:22:35.450 --> 10:22:35.460 align:start position:0% uh four hours 10:22:35.460 --> 10:22:40.266 align:start position:0% uh four hours studying<10:22:36.120> to<10:22:36.300> IPv6<10:22:36.960> this<10:22:37.740> is<10:22:37.860> for<10:22:38.220> interviews 10:22:40.266 --> 10:22:40.276 align:start position:0% studying to IPv6 this is for interviews 10:22:40.276 --> 10:22:43.970 align:start position:0% studying to IPv6 this is for interviews technical<10:22:41.276> jobs<10:22:41.936> uh<10:22:42.900> technical<10:22:43.256> interviews 10:22:43.970 --> 10:22:43.980 align:start position:0% technical jobs uh technical interviews 10:22:43.980 --> 10:22:46.490 align:start position:0% technical jobs uh technical interviews and<10:22:44.640> just<10:22:44.880> to<10:22:45.000> do<10:22:45.240> your<10:22:45.540> day-to-day<10:22:46.080> job<10:22:46.320> you 10:22:46.490 --> 10:22:46.500 align:start position:0% and just to do your day-to-day job you 10:22:46.500 --> 10:22:48.650 align:start position:0% and just to do your day-to-day job you do<10:22:46.680> need<10:22:46.860> to<10:22:46.980> understand<10:22:47.160> it<10:22:47.580> there's<10:22:48.360> a 10:22:48.650 --> 10:22:48.660 align:start position:0% do need to understand it there's a 10:22:48.660 --> 10:22:51.650 align:start position:0% do need to understand it there's a course<10:22:48.900> on<10:22:49.320> them<10:22:49.500> cartoon<10:22:49.916> network.com<10:22:50.660> it's 10:22:51.650 --> 10:22:51.660 align:start position:0% course on them cartoon network.com it's 10:22:51.660 --> 10:22:53.810 align:start position:0% course on them cartoon network.com it's 16<10:22:51.960> hours<10:22:52.320> in<10:22:52.680> total<10:22:52.980> but<10:22:53.220> I<10:22:53.340> broke<10:22:53.520> it<10:22:53.700> down 10:22:53.810 --> 10:22:53.820 align:start position:0% 16 hours in total but I broke it down 10:22:53.820 --> 10:22:55.790 align:start position:0% 16 hours in total but I broke it down into<10:22:54.060> I<10:22:54.360> think<10:22:54.480> the<10:22:54.660> beginner<10:22:55.256> course<10:22:55.560> is 10:22:55.790 --> 10:22:55.800 align:start position:0% into I think the beginner course is 10:22:55.800 --> 10:22:58.490 align:start position:0% into I think the beginner course is about<10:22:56.040> three<10:22:56.580> there's<10:22:57.540> an<10:22:57.776> intermediate<10:22:58.320> with 10:22:58.490 --> 10:22:58.500 align:start position:0% about three there's an intermediate with 10:22:58.500 --> 10:23:00.110 align:start position:0% about three there's an intermediate with loads<10:22:58.800> of<10:22:58.860> routing 10:23:00.110 --> 10:23:00.120 align:start position:0% loads of routing 10:23:00.120 --> 10:23:03.830 align:start position:0% loads of routing and<10:23:00.776> then<10:23:00.960> maybe<10:23:01.380> I<10:23:01.980> think<10:23:02.240> five<10:23:03.240> or<10:23:03.540> I'm 10:23:03.830 --> 10:23:03.840 align:start position:0% and then maybe I think five or I'm 10:23:03.840 --> 10:23:06.290 align:start position:0% and then maybe I think five or I'm trying<10:23:04.080> to<10:23:04.200> do<10:23:04.380> my<10:23:04.500> math<10:23:04.620> now<10:23:04.860> six<10:23:05.160> to<10:23:05.340> 12. 10:23:06.290 --> 10:23:06.300 align:start position:0% trying to do my math now six to 12. 10:23:06.300 --> 10:23:09.950 align:start position:0% trying to do my math now six to 12. seven<10:23:06.900> hours<10:23:07.200> extra<10:23:07.980> which<10:23:08.520> is<10:23:08.700> Advanced<10:23:09.416> so 10:23:09.950 --> 10:23:09.960 align:start position:0% seven hours extra which is Advanced so 10:23:09.960 --> 10:23:11.926 align:start position:0% seven hours extra which is Advanced so you<10:23:10.200> could<10:23:10.256> just<10:23:10.436> do<10:23:10.680> one<10:23:11.096> part<10:23:11.340> and<10:23:11.640> then<10:23:11.820> when 10:23:11.926 --> 10:23:11.936 align:start position:0% you could just do one part and then when 10:23:11.936 --> 10:23:13.130 align:start position:0% you could just do one part and then when you<10:23:12.060> come<10:23:12.240> to<10:23:12.360> do<10:23:12.480> something<10:23:12.660> a<10:23:12.900> bit<10:23:13.020> more 10:23:13.130 --> 10:23:13.140 align:start position:0% you come to do something a bit more 10:23:13.140 --> 10:23:15.050 align:start position:0% you come to do something a bit more difficult<10:23:13.436> do<10:23:13.680> the<10:23:13.860> second<10:23:14.040> part<10:23:14.276> and<10:23:14.820> if<10:23:14.936> you 10:23:15.050 --> 10:23:15.060 align:start position:0% difficult do the second part and if you 10:23:15.060 --> 10:23:17.570 align:start position:0% difficult do the second part and if you want<10:23:15.180> the<10:23:15.416> third<10:23:15.596> but<10:23:16.680> um<10:23:16.680> you<10:23:17.040> really<10:23:17.160> do<10:23:17.400> need 10:23:17.570 --> 10:23:17.580 align:start position:0% want the third but um you really do need 10:23:17.580 --> 10:23:19.310 align:start position:0% want the third but um you really do need to<10:23:17.700> know<10:23:17.820> IPv6<10:23:18.540> I've<10:23:18.776> been<10:23:18.960> talking<10:23:19.080> about 10:23:19.310 --> 10:23:19.320 align:start position:0% to know IPv6 I've been talking about 10:23:19.320 --> 10:23:22.426 align:start position:0% to know IPv6 I've been talking about this<10:23:19.620> for<10:23:19.980> about<10:23:20.220> four<10:23:21.000> years<10:23:21.300> now<10:23:21.596> and<10:23:22.256> it's 10:23:22.426 --> 10:23:22.436 align:start position:0% this for about four years now and it's 10:23:22.436 --> 10:23:24.890 align:start position:0% this for about four years now and it's becoming<10:23:22.860> more<10:23:23.096> and<10:23:23.276> more<10:23:23.700> urgent<10:23:23.880> so<10:23:24.120> you<10:23:24.416> I 10:23:24.890 --> 10:23:24.900 align:start position:0% becoming more and more urgent so you I 10:23:24.900 --> 10:23:26.690 align:start position:0% becoming more and more urgent so you I used<10:23:25.080> to<10:23:25.200> recommend<10:23:25.500> it<10:23:25.740> and<10:23:25.980> now<10:23:26.220> basically 10:23:26.690 --> 10:23:26.700 align:start position:0% used to recommend it and now basically 10:23:26.700 --> 10:23:30.110 align:start position:0% used to recommend it and now basically the<10:23:27.120> the<10:23:27.416> level<10:23:27.960> of<10:23:28.320> uh<10:23:29.160> understanding<10:23:29.700> in<10:23:30.000> the 10:23:30.110 --> 10:23:30.120 align:start position:0% the the level of uh understanding in the 10:23:30.120 --> 10:23:31.906 align:start position:0% the the level of uh understanding in the the<10:23:30.360> level<10:23:30.596> of<10:23:30.776> adoption<10:23:31.140> is<10:23:31.380> basically<10:23:31.680> you 10:23:31.906 --> 10:23:31.916 align:start position:0% the level of adoption is basically you 10:23:31.916 --> 10:23:34.190 align:start position:0% the level of adoption is basically you you<10:23:32.096> have<10:23:32.520> to<10:23:32.640> know<10:23:32.820> it<10:23:33.000> it's<10:23:33.660> just<10:23:33.840> like<10:23:34.020> not 10:23:34.190 --> 10:23:34.200 align:start position:0% you have to know it it's just like not 10:23:34.200 --> 10:23:36.890 align:start position:0% you have to know it it's just like not knowing<10:23:34.560> ipv4<10:23:35.340> now<10:23:35.700> if<10:23:35.936> you<10:23:36.000> go<10:23:36.120> into<10:23:36.240> it<10:23:36.660> um<10:23:36.660> if 10:23:36.890 --> 10:23:36.900 align:start position:0% knowing ipv4 now if you go into it um if 10:23:36.900 --> 10:23:39.050 align:start position:0% knowing ipv4 now if you go into it um if you<10:23:37.080> go<10:23:37.256> into<10:23:37.380> an<10:23:37.560> interview<10:23:37.680> so<10:23:38.640> please<10:23:38.820> do 10:23:39.050 --> 10:23:39.060 align:start position:0% you go into an interview so please do 10:23:39.060 --> 10:23:42.950 align:start position:0% you go into an interview so please do learn<10:23:39.300> it<10:23:39.680> and<10:23:40.680> we've<10:23:41.276> covered<10:23:41.520> IPv6<10:23:42.360> address 10:23:42.950 --> 10:23:42.960 align:start position:0% learn it and we've covered IPv6 address 10:23:42.960 --> 10:23:47.450 align:start position:0% learn it and we've covered IPv6 address types<10:23:43.560> Navy<10:23:44.160> Discovery<10:23:44.960> eui<10:23:45.960> 64<10:23:46.436> and<10:23:47.340> then 10:23:47.450 --> 10:23:47.460 align:start position:0% types Navy Discovery eui 64 and then 10:23:47.460 --> 10:23:49.550 align:start position:0% types Navy Discovery eui 64 and then tunnel<10:23:47.880> in<10:23:48.060> that's<10:23:48.416> all<10:23:48.660> for<10:23:48.840> now<10:23:49.020> thanks<10:23:49.380> for 10:23:49.550 --> 10:23:49.560 align:start position:0% tunnel in that's all for now thanks for 10:23:49.560 --> 10:23:55.240 align:start position:0% tunnel in that's all for now thanks for listening 10:23:55.240 --> 10:23:55.250 align:start position:0% 10:23:55.250 --> 10:24:01.926 align:start position:0% [Music] 10:24:01.926 --> 10:24:01.936 align:start position:0% [Music] 10:24:01.936 --> 10:24:13.970 align:start position:0% [Music] thank<10:24:02.936> you 10:24:13.970 --> 10:24:13.980 align:start position:0% 10:24:13.980 --> 10:24:17.810 align:start position:0% Network<10:24:14.756> routing<10:24:15.360> and<10:24:15.596> IP<10:24:15.960> addressing<10:24:16.820> IP 10:24:17.810 --> 10:24:17.820 align:start position:0% Network routing and IP addressing IP 10:24:17.820 --> 10:24:20.746 align:start position:0% Network routing and IP addressing IP assigning<10:24:18.596> and<10:24:18.960> addressing<10:24:19.500> methods 10:24:20.746 --> 10:24:20.756 align:start position:0% assigning and addressing methods 10:24:20.756 --> 10:24:23.810 align:start position:0% assigning and addressing methods so<10:24:21.240> having<10:24:21.416> discussed<10:24:21.900> both<10:24:22.080> ipv4<10:24:22.916> and<10:24:23.160> IPv6 10:24:23.810 --> 10:24:23.820 align:start position:0% so having discussed both ipv4 and IPv6 10:24:23.820 --> 10:24:25.426 align:start position:0% so having discussed both ipv4 and IPv6 and<10:24:24.060> the<10:24:24.180> difference<10:24:24.360> between<10:24:24.596> these 10:24:25.426 --> 10:24:25.436 align:start position:0% and the difference between these 10:24:25.436 --> 10:24:27.586 align:start position:0% and the difference between these different<10:24:25.560> types<10:24:25.980> of<10:24:26.096> IP<10:24:26.460> addresses<10:24:26.936> we<10:24:27.480> now 10:24:27.586 --> 10:24:27.596 align:start position:0% different types of IP addresses we now 10:24:27.596 --> 10:24:29.690 align:start position:0% different types of IP addresses we now want<10:24:27.840> to<10:24:28.020> talk<10:24:28.200> specifically<10:24:29.096> and<10:24:29.340> in<10:24:29.580> more 10:24:29.690 --> 10:24:29.700 align:start position:0% want to talk specifically and in more 10:24:29.700 --> 10:24:33.350 align:start position:0% want to talk specifically and in more depth<10:24:30.060> about<10:24:30.800> how<10:24:31.800> IP<10:24:32.276> addresses<10:24:32.880> are 10:24:33.350 --> 10:24:33.360 align:start position:0% depth about how IP addresses are 10:24:33.360 --> 10:24:36.650 align:start position:0% depth about how IP addresses are assigned<10:24:33.960> to<10:24:34.436> a<10:24:34.680> specific<10:24:34.916> node<10:24:35.520> or<10:24:35.820> client<10:24:36.300> or 10:24:36.650 --> 10:24:36.660 align:start position:0% assigned to a specific node or client or 10:24:36.660 --> 10:24:39.650 align:start position:0% assigned to a specific node or client or server<10:24:37.620> so<10:24:38.040> in<10:24:38.276> this<10:24:38.460> module<10:24:38.880> we're<10:24:39.300> going<10:24:39.480> to 10:24:39.650 --> 10:24:39.660 align:start position:0% server so in this module we're going to 10:24:39.660 --> 10:24:41.746 align:start position:0% server so in this module we're going to look<10:24:39.776> at<10:24:40.020> the<10:24:40.256> two<10:24:40.500> different<10:24:40.740> ways<10:24:41.160> that<10:24:41.400> IP 10:24:41.746 --> 10:24:41.756 align:start position:0% look at the two different ways that IP 10:24:41.756 --> 10:24:44.510 align:start position:0% look at the two different ways that IP addresses<10:24:42.300> are<10:24:42.900> assigned<10:24:43.436> this<10:24:44.160> involves 10:24:44.510 --> 10:24:44.520 align:start position:0% addresses are assigned this involves 10:24:44.520 --> 10:24:47.210 align:start position:0% addresses are assigned this involves defining<10:24:45.120> the<10:24:45.416> first<10:24:45.540> static<10:24:46.320> IP<10:24:46.620> addressing 10:24:47.210 --> 10:24:47.220 align:start position:0% defining the first static IP addressing 10:24:47.220 --> 10:24:49.970 align:start position:0% defining the first static IP addressing static<10:24:48.180> meaning<10:24:48.540> that<10:24:48.840> the<10:24:49.020> IP<10:24:49.320> address<10:24:49.500> is 10:24:49.970 --> 10:24:49.980 align:start position:0% static meaning that the IP address is 10:24:49.980 --> 10:24:52.790 align:start position:0% static meaning that the IP address is always<10:24:50.220> the<10:24:50.580> same<10:24:50.700> and<10:24:51.540> dynamic<10:24:52.380> IP 10:24:52.790 --> 10:24:52.800 align:start position:0% always the same and dynamic IP 10:24:52.800 --> 10:24:54.710 align:start position:0% always the same and dynamic IP addressing<10:24:53.340> which<10:24:53.880> means<10:24:54.120> that<10:24:54.300> the<10:24:54.480> IP 10:24:54.710 --> 10:24:54.720 align:start position:0% addressing which means that the IP 10:24:54.720 --> 10:24:57.350 align:start position:0% addressing which means that the IP address<10:24:54.960> can<10:24:55.436> change<10:24:55.740> we<10:24:56.580> also<10:24:56.820> want<10:24:57.000> to<10:24:57.180> talk 10:24:57.350 --> 10:24:57.360 align:start position:0% address can change we also want to talk 10:24:57.360 --> 10:25:00.406 align:start position:0% address can change we also want to talk about<10:24:57.720> the<10:24:58.200> strengths<10:24:58.740> and<10:24:59.160> weaknesses<10:24:59.756> of 10:25:00.406 --> 10:25:00.416 align:start position:0% about the strengths and weaknesses of 10:25:00.416 --> 10:25:02.990 align:start position:0% about the strengths and weaknesses of each<10:25:00.660> of<10:25:00.840> these<10:25:01.020> addressing<10:25:01.620> methods<10:25:02.040> and<10:25:02.756> we 10:25:02.990 --> 10:25:03.000 align:start position:0% each of these addressing methods and we 10:25:03.000 --> 10:25:05.450 align:start position:0% each of these addressing methods and we want<10:25:03.120> to<10:25:03.240> compare<10:25:03.660> the<10:25:04.020> features<10:25:04.436> of<10:25:04.916> one<10:25:05.220> and 10:25:05.450 --> 10:25:05.460 align:start position:0% want to compare the features of one and 10:25:05.460 --> 10:25:06.230 align:start position:0% want to compare the features of one and the<10:25:05.580> other 10:25:06.230 --> 10:25:06.240 align:start position:0% the other 10:25:06.240 --> 10:25:09.530 align:start position:0% the other we're<10:25:06.720> also<10:25:07.020> going<10:25:07.256> to<10:25:07.880> identify<10:25:08.880> when<10:25:09.360> we 10:25:09.530 --> 10:25:09.540 align:start position:0% we're also going to identify when we 10:25:09.540 --> 10:25:12.050 align:start position:0% we're also going to identify when we want<10:25:09.720> to<10:25:09.900> use<10:25:10.140> Dynamic<10:25:10.800> IP<10:25:11.096> addressing<10:25:11.580> as 10:25:12.050 --> 10:25:12.060 align:start position:0% want to use Dynamic IP addressing as 10:25:12.060 --> 10:25:14.926 align:start position:0% want to use Dynamic IP addressing as opposed<10:25:12.540> to<10:25:12.720> static<10:25:13.200> IP<10:25:13.436> addressing<10:25:14.400> and 10:25:14.926 --> 10:25:14.936 align:start position:0% opposed to static IP addressing and 10:25:14.936 --> 10:25:17.086 align:start position:0% opposed to static IP addressing and Define<10:25:15.180> when<10:25:15.900> we're<10:25:16.020> talking<10:25:16.256> about<10:25:16.500> Dynamic 10:25:17.086 --> 10:25:17.096 align:start position:0% Define when we're talking about Dynamic 10:25:17.096 --> 10:25:21.050 align:start position:0% Define when we're talking about Dynamic IP<10:25:17.400> addressing<10:25:17.880> the<10:25:18.300> terms<10:25:18.740> DHCP<10:25:19.740> the<10:25:20.640> server 10:25:21.050 --> 10:25:21.060 align:start position:0% IP addressing the terms DHCP the server 10:25:21.060 --> 10:25:23.086 align:start position:0% IP addressing the terms DHCP the server and<10:25:21.240> protocol<10:25:21.596> that<10:25:22.020> are<10:25:22.200> responsible<10:25:22.740> for 10:25:23.086 --> 10:25:23.096 align:start position:0% and protocol that are responsible for 10:25:23.096 --> 10:25:25.490 align:start position:0% and protocol that are responsible for allowing<10:25:23.520> Dynamic<10:25:24.000> IP<10:25:24.240> addressing<10:25:24.660> to<10:25:24.840> work 10:25:25.490 --> 10:25:25.500 align:start position:0% allowing Dynamic IP addressing to work 10:25:25.500 --> 10:25:28.246 align:start position:0% allowing Dynamic IP addressing to work something<10:25:25.860> called<10:25:26.160> the<10:25:26.460> scope<10:25:26.756> which<10:25:27.596> lets 10:25:28.246 --> 10:25:28.256 align:start position:0% something called the scope which lets 10:25:28.256 --> 10:25:31.610 align:start position:0% something called the scope which lets the<10:25:28.500> DHCP<10:25:29.460> server<10:25:30.060> know<10:25:30.540> which<10:25:30.840> IP<10:25:31.200> addresses 10:25:31.610 --> 10:25:31.620 align:start position:0% the DHCP server know which IP addresses 10:25:31.620 --> 10:25:34.370 align:start position:0% the DHCP server know which IP addresses are<10:25:31.800> up<10:25:31.980> for<10:25:32.220> grabs<10:25:32.700> and<10:25:33.596> then<10:25:33.776> the<10:25:34.080> lease 10:25:34.370 --> 10:25:34.380 align:start position:0% are up for grabs and then the lease 10:25:34.380 --> 10:25:36.230 align:start position:0% are up for grabs and then the lease which<10:25:35.040> just<10:25:35.276> like<10:25:35.460> the<10:25:35.640> lease<10:25:35.880> on<10:25:36.060> an 10:25:36.230 --> 10:25:36.240 align:start position:0% which just like the lease on an 10:25:36.240 --> 10:25:37.030 align:start position:0% which just like the lease on an apartment 10:25:37.030 --> 10:25:37.040 align:start position:0% apartment 10:25:37.040 --> 10:25:40.370 align:start position:0% apartment lets<10:25:38.040> the<10:25:38.520> both<10:25:39.060> the<10:25:39.360> server<10:25:39.660> and<10:25:39.900> the<10:25:40.080> client 10:25:40.370 --> 10:25:40.380 align:start position:0% lets the both the server and the client 10:25:40.380 --> 10:25:44.690 align:start position:0% lets the both the server and the client know<10:25:41.220> when<10:25:41.936> a<10:25:42.540> IP<10:25:43.256> address<10:25:43.500> can<10:25:44.160> be<10:25:44.276> used<10:25:44.460> and 10:25:44.690 --> 10:25:44.700 align:start position:0% know when a IP address can be used and 10:25:44.700 --> 10:25:47.030 align:start position:0% know when a IP address can be used and for<10:25:44.880> how<10:25:45.060> long<10:25:45.240> we<10:25:46.140> also<10:25:46.380> want<10:25:46.500> to<10:25:46.680> talk<10:25:46.860> about 10:25:47.030 --> 10:25:47.040 align:start position:0% for how long we also want to talk about 10:25:47.040 --> 10:25:49.246 align:start position:0% for how long we also want to talk about when<10:25:47.700> static<10:25:48.180> IP<10:25:48.480> addressing<10:25:48.960> would<10:25:49.140> be 10:25:49.246 --> 10:25:49.256 align:start position:0% when static IP addressing would be 10:25:49.256 --> 10:25:51.290 align:start position:0% when static IP addressing would be preferred<10:25:49.800> and<10:25:50.400> as<10:25:50.580> you<10:25:50.756> can<10:25:50.820> probably<10:25:51.000> tell 10:25:51.290 --> 10:25:51.300 align:start position:0% preferred and as you can probably tell 10:25:51.300 --> 10:25:53.630 align:start position:0% preferred and as you can probably tell from<10:25:51.596> the<10:25:51.840> way<10:25:51.960> this<10:25:52.140> is<10:25:52.256> worded<10:25:52.680> we<10:25:53.220> generally 10:25:53.630 --> 10:25:53.640 align:start position:0% from the way this is worded we generally 10:25:53.640 --> 10:25:56.450 align:start position:0% from the way this is worded we generally want<10:25:54.120> to<10:25:54.596> use<10:25:54.840> Dynamic<10:25:55.560> IP<10:25:55.860> addressing<10:25:56.276> as 10:25:56.450 --> 10:25:56.460 align:start position:0% want to use Dynamic IP addressing as 10:25:56.460 --> 10:25:57.950 align:start position:0% want to use Dynamic IP addressing as we'll<10:25:56.640> talk<10:25:56.820> about<10:25:57.000> but<10:25:57.540> there<10:25:57.720> are<10:25:57.840> certain 10:25:57.950 --> 10:25:57.960 align:start position:0% we'll talk about but there are certain 10:25:57.960 --> 10:25:59.926 align:start position:0% we'll talk about but there are certain instances<10:25:58.436> in<10:25:58.680> which<10:25:58.860> a<10:25:59.160> static<10:25:59.520> IP 10:25:59.926 --> 10:25:59.936 align:start position:0% instances in which a static IP 10:25:59.936 --> 10:26:03.230 align:start position:0% instances in which a static IP addressing<10:26:00.480> is<10:26:01.380> the<10:26:01.800> best<10:26:02.340> method<10:26:02.756> for<10:26:03.000> us<10:26:03.120> and 10:26:03.230 --> 10:26:03.240 align:start position:0% addressing is the best method for us and 10:26:03.240 --> 10:26:05.390 align:start position:0% addressing is the best method for us and we'll<10:26:03.416> talk<10:26:03.596> about<10:26:03.720> those<10:26:04.020> as<10:26:04.256> well 10:26:05.390 --> 10:26:05.400 align:start position:0% we'll talk about those as well 10:26:05.400 --> 10:26:08.086 align:start position:0% we'll talk about those as well so<10:26:06.060> first<10:26:06.300> let's<10:26:06.480> talk<10:26:06.720> about<10:26:06.840> static<10:26:07.680> IP 10:26:08.086 --> 10:26:08.096 align:start position:0% so first let's talk about static IP 10:26:08.096 --> 10:26:11.210 align:start position:0% so first let's talk about static IP addressing<10:26:08.660> it's<10:26:09.660> done<10:26:10.200> manually<10:26:10.740> and<10:26:11.096> that's 10:26:11.210 --> 10:26:11.220 align:start position:0% addressing it's done manually and that's 10:26:11.220 --> 10:26:13.190 align:start position:0% addressing it's done manually and that's what<10:26:11.400> this<10:26:11.580> really<10:26:11.756> means<10:26:12.180> static<10:26:12.776> means 10:26:13.190 --> 10:26:13.200 align:start position:0% what this really means static means 10:26:13.200 --> 10:26:16.490 align:start position:0% what this really means static means manual<10:26:13.820> assignment<10:26:14.820> which<10:26:15.596> means<10:26:15.900> that<10:26:16.140> I 10:26:16.490 --> 10:26:16.500 align:start position:0% manual assignment which means that I 10:26:16.500 --> 10:26:18.586 align:start position:0% manual assignment which means that I literally<10:26:16.860> have<10:26:17.096> to<10:26:17.276> go<10:26:17.460> to<10:26:17.580> the<10:26:17.700> computer<10:26:17.880> and 10:26:18.586 --> 10:26:18.596 align:start position:0% literally have to go to the computer and 10:26:18.596 --> 10:26:21.230 align:start position:0% literally have to go to the computer and type<10:26:18.840> in<10:26:19.200> what<10:26:19.740> the<10:26:19.800> IP<10:26:20.096> address<10:26:20.276> is<10:26:20.700> and<10:26:20.880> how<10:26:21.060> I 10:26:21.230 --> 10:26:21.240 align:start position:0% type in what the IP address is and how I 10:26:21.240 --> 10:26:23.450 align:start position:0% type in what the IP address is and how I want<10:26:21.300> to<10:26:21.416> use<10:26:21.596> it<10:26:21.776> so<10:26:22.500> there<10:26:22.860> are<10:26:23.040> two<10:26:23.220> major 10:26:23.450 --> 10:26:23.460 align:start position:0% want to use it so there are two major 10:26:23.460 --> 10:26:26.450 align:start position:0% want to use it so there are two major flaws<10:26:24.000> with<10:26:24.180> this<10:26:24.436> first<10:26:25.436> it<10:26:26.040> can<10:26:26.160> be<10:26:26.276> very 10:26:26.450 --> 10:26:26.460 align:start position:0% flaws with this first it can be very 10:26:26.460 --> 10:26:30.230 align:start position:0% flaws with this first it can be very time<10:26:27.060> consuming<10:26:27.596> because<10:26:28.520> it<10:26:29.520> has<10:26:29.700> to<10:26:29.880> be<10:26:30.060> done 10:26:30.230 --> 10:26:30.240 align:start position:0% time consuming because it has to be done 10:26:30.240 --> 10:26:32.030 align:start position:0% time consuming because it has to be done manually<10:26:30.720> and<10:26:31.020> each<10:26:31.256> address<10:26:31.436> has<10:26:31.800> to<10:26:31.980> be 10:26:32.030 --> 10:26:32.040 align:start position:0% manually and each address has to be 10:26:32.040 --> 10:26:34.906 align:start position:0% manually and each address has to be entered<10:26:32.400> individually<10:26:32.936> by<10:26:33.416> hand<10:26:33.720> in<10:26:34.680> addition 10:26:34.906 --> 10:26:34.916 align:start position:0% entered individually by hand in addition 10:26:34.916 --> 10:26:37.550 align:start position:0% entered individually by hand in addition this<10:26:35.520> takes<10:26:35.756> a<10:26:35.880> lot<10:26:36.000> of<10:26:36.180> time<10:26:36.540> and<10:26:37.020> it's<10:26:37.200> prone 10:26:37.550 --> 10:26:37.560 align:start position:0% this takes a lot of time and it's prone 10:26:37.560 --> 10:26:39.426 align:start position:0% this takes a lot of time and it's prone to<10:26:37.860> a<10:26:38.040> lot<10:26:38.160> of<10:26:38.276> Errors 10:26:39.426 --> 10:26:39.436 align:start position:0% to a lot of Errors 10:26:39.436 --> 10:26:42.586 align:start position:0% to a lot of Errors human<10:26:40.436> error<10:26:40.916> is<10:26:41.040> often<10:26:41.340> a<10:26:41.520> factor<10:26:41.880> when<10:26:42.416> we're 10:26:42.586 --> 10:26:42.596 align:start position:0% human error is often a factor when we're 10:26:42.596 --> 10:26:45.110 align:start position:0% human error is often a factor when we're configuring<10:26:43.436> addresses<10:26:44.220> for<10:26:44.520> a<10:26:44.640> large<10:26:44.820> amount 10:26:45.110 --> 10:26:45.120 align:start position:0% configuring addresses for a large amount 10:26:45.120 --> 10:26:47.266 align:start position:0% configuring addresses for a large amount of<10:26:45.240> systems<10:26:45.660> and<10:26:46.380> if<10:26:46.500> you<10:26:46.620> can<10:26:46.680> imagine<10:26:46.860> I'm 10:26:47.266 --> 10:26:47.276 align:start position:0% of systems and if you can imagine I'm 10:26:47.276 --> 10:26:50.746 align:start position:0% of systems and if you can imagine I'm working<10:26:47.460> in<10:26:47.756> a<10:26:47.936> system<10:26:48.060> of<10:26:48.480> say<10:26:49.200> 5 10:26:50.746 --> 10:26:50.756 align:start position:0% working in a system of say 5 10:26:50.756 --> 10:26:52.670 align:start position:0% working in a system of say 5 000<10:26:50.820> computers<10:26:51.416> then<10:26:52.020> I'm<10:26:52.256> going<10:26:52.436> to<10:26:52.560> be 10:26:52.670 --> 10:26:52.680 align:start position:0% 000 computers then I'm going to be 10:26:52.680 --> 10:26:55.790 align:start position:0% 000 computers then I'm going to be typing<10:26:53.096> in<10:26:53.220> IP<10:26:53.580> addresses<10:26:54.120> a<10:26:54.596> lot<10:26:54.776> now<10:26:55.500> while 10:26:55.790 --> 10:26:55.800 align:start position:0% typing in IP addresses a lot now while 10:26:55.800 --> 10:26:57.650 align:start position:0% typing in IP addresses a lot now while this<10:26:56.040> may<10:26:56.220> be<10:26:56.340> a<10:26:56.520> worthwhile<10:26:56.936> method<10:26:57.416> when 10:26:57.650 --> 10:26:57.660 align:start position:0% this may be a worthwhile method when 10:26:57.660 --> 10:26:59.086 align:start position:0% this may be a worthwhile method when assigning<10:26:58.020> a<10:26:58.256> very<10:26:58.380> small<10:26:58.620> amount<10:26:58.916> of 10:26:59.086 --> 10:26:59.096 align:start position:0% assigning a very small amount of 10:26:59.096 --> 10:27:00.530 align:start position:0% assigning a very small amount of addresses<10:26:59.520> it's<10:26:59.700> obviously<10:27:00.180> not<10:27:00.360> very 10:27:00.530 --> 10:27:00.540 align:start position:0% addresses it's obviously not very 10:27:00.540 --> 10:27:01.970 align:start position:0% addresses it's obviously not very practical<10:27:00.900> when<10:27:01.140> I'm<10:27:01.320> talking<10:27:01.500> about<10:27:01.680> large 10:27:01.970 --> 10:27:01.980 align:start position:0% practical when I'm talking about large 10:27:01.980 --> 10:27:04.906 align:start position:0% practical when I'm talking about large quantities<10:27:02.520> and<10:27:03.180> the<10:27:03.416> other<10:27:03.540> major<10:27:03.776> flaw<10:27:04.320> is 10:27:04.906 --> 10:27:04.916 align:start position:0% quantities and the other major flaw is 10:27:04.916 --> 10:27:07.370 align:start position:0% quantities and the other major flaw is that<10:27:05.096> it<10:27:05.340> has<10:27:05.936> to<10:27:06.120> be<10:27:06.240> reconfigured<10:27:07.080> every 10:27:07.370 --> 10:27:07.380 align:start position:0% that it has to be reconfigured every 10:27:07.380 --> 10:27:11.030 align:start position:0% that it has to be reconfigured every time<10:27:07.680> the<10:27:08.460> address<10:27:08.700> sync<10:27:09.540> scheme<10:27:10.020> changes<10:27:10.680> so 10:27:11.030 --> 10:27:11.040 align:start position:0% time the address sync scheme changes so 10:27:11.040 --> 10:27:12.950 align:start position:0% time the address sync scheme changes so for<10:27:11.220> instance<10:27:11.400> if<10:27:11.520> I<10:27:11.640> was<10:27:11.756> going<10:27:11.880> from<10:27:12.120> ipv4<10:27:12.776> to 10:27:12.950 --> 10:27:12.960 align:start position:0% for instance if I was going from ipv4 to 10:27:12.960 --> 10:27:15.530 align:start position:0% for instance if I was going from ipv4 to IPv6<10:27:13.620> on<10:27:13.916> my<10:27:14.096> internal<10:27:14.520> Network<10:27:14.700> I'm<10:27:15.300> going<10:27:15.416> to 10:27:15.530 --> 10:27:15.540 align:start position:0% IPv6 on my internal Network I'm going to 10:27:15.540 --> 10:27:18.830 align:start position:0% IPv6 on my internal Network I'm going to have<10:27:15.660> to<10:27:15.840> re-change<10:27:16.500> everything<10:27:17.596> once<10:27:18.596> I've 10:27:18.830 --> 10:27:18.840 align:start position:0% have to re-change everything once I've 10:27:18.840 --> 10:27:20.926 align:start position:0% have to re-change everything once I've switched<10:27:19.256> over<10:27:19.436> or<10:27:20.040> let's<10:27:20.276> say<10:27:20.460> I<10:27:20.580> want<10:27:20.756> to 10:27:20.926 --> 10:27:20.936 align:start position:0% switched over or let's say I want to 10:27:20.936 --> 10:27:22.730 align:start position:0% switched over or let's say I want to change<10:27:21.060> my<10:27:21.416> naming<10:27:21.776> system<10:27:21.960> maybe<10:27:22.320> I<10:27:22.500> want<10:27:22.620> to 10:27:22.730 --> 10:27:22.740 align:start position:0% change my naming system maybe I want to 10:27:22.740 --> 10:27:27.050 align:start position:0% change my naming system maybe I want to go<10:27:22.916> from<10:27:23.400> a<10:27:24.120> Class<10:27:24.416> C<10:27:25.140> to<10:27:25.800> a<10:27:26.096> class<10:27:26.276> AIP 10:27:27.050 --> 10:27:27.060 align:start position:0% go from a Class C to a class AIP 10:27:27.060 --> 10:27:29.746 align:start position:0% go from a Class C to a class AIP addressing<10:27:27.720> system<10:27:27.840> if<10:27:28.080> I'm<10:27:28.200> an<10:27:28.380> ipv4<10:27:28.980> and<10:27:29.580> in 10:27:29.746 --> 10:27:29.756 align:start position:0% addressing system if I'm an ipv4 and in 10:27:29.756 --> 10:27:30.710 align:start position:0% addressing system if I'm an ipv4 and in this<10:27:29.880> case<10:27:30.000> I<10:27:30.240> would<10:27:30.300> have<10:27:30.480> to<10:27:30.596> then 10:27:30.710 --> 10:27:30.720 align:start position:0% this case I would have to then 10:27:30.720 --> 10:27:32.746 align:start position:0% this case I would have to then reconfigure<10:27:31.320> everything<10:27:31.740> on<10:27:32.276> each<10:27:32.520> computer 10:27:32.746 --> 10:27:32.756 align:start position:0% reconfigure everything on each computer 10:27:32.756 --> 10:27:34.246 align:start position:0% reconfigure everything on each computer and<10:27:33.060> you<10:27:33.180> can<10:27:33.300> imagine<10:27:33.416> the<10:27:33.660> amount<10:27:33.900> of<10:27:34.080> time 10:27:34.246 --> 10:27:34.256 align:start position:0% and you can imagine the amount of time 10:27:34.256 --> 10:27:36.170 align:start position:0% and you can imagine the amount of time that<10:27:34.916> that's<10:27:35.096> going<10:27:35.340> to<10:27:35.460> take 10:27:36.170 --> 10:27:36.180 align:start position:0% that that's going to take 10:27:36.180 --> 10:27:39.530 align:start position:0% that that's going to take so<10:27:37.140> due<10:27:37.800> to<10:27:37.916> its<10:27:38.220> many<10:27:38.276> flaws<10:27:38.880> we're<10:27:39.300> really 10:27:39.530 --> 10:27:39.540 align:start position:0% so due to its many flaws we're really 10:27:39.540 --> 10:27:43.246 align:start position:0% so due to its many flaws we're really not<10:27:39.776> going<10:27:40.020> to<10:27:40.200> use<10:27:40.620> this<10:27:41.276> method<10:27:41.840> static<10:27:42.840> IP 10:27:43.246 --> 10:27:43.256 align:start position:0% not going to use this method static IP 10:27:43.256 --> 10:27:45.830 align:start position:0% not going to use this method static IP addressing<10:27:43.800> which<10:27:44.160> means<10:27:44.580> again<10:27:44.936> manual 10:27:45.830 --> 10:27:45.840 align:start position:0% addressing which means again manual 10:27:45.840 --> 10:27:47.150 align:start position:0% addressing which means again manual assignment<10:27:46.256> the<10:27:46.436> way<10:27:46.560> you<10:27:46.680> can<10:27:46.800> remember<10:27:46.916> that 10:27:47.150 --> 10:27:47.160 align:start position:0% assignment the way you can remember that 10:27:47.160 --> 10:27:50.990 align:start position:0% assignment the way you can remember that is<10:27:47.340> that<10:27:47.580> static<10:27:48.120> does<10:27:48.540> not<10:27:48.776> change<10:27:49.256> right<10:27:50.160> it 10:27:50.990 --> 10:27:51.000 align:start position:0% is that static does not change right it 10:27:51.000 --> 10:27:57.050 align:start position:0% is that static does not change right it remains<10:27:51.900> constants 10:27:57.050 --> 10:27:57.060 align:start position:0% 10:27:57.060 --> 10:27:59.690 align:start position:0% and<10:27:57.596> the<10:27:57.840> word<10:27:57.960> static<10:27:58.560> meaning<10:27:58.740> not<10:27:59.160> changing 10:27:59.690 --> 10:27:59.700 align:start position:0% and the word static meaning not changing 10:27:59.700 --> 10:28:01.850 align:start position:0% and the word static meaning not changing is<10:28:00.120> what<10:28:00.360> tells<10:28:00.776> us<10:28:00.900> that<10:28:01.140> so<10:28:01.620> we're<10:28:01.740> only 10:28:01.850 --> 10:28:01.860 align:start position:0% is what tells us that so we're only 10:28:01.860 --> 10:28:03.350 align:start position:0% is what tells us that so we're only going<10:28:02.040> to<10:28:02.040> use<10:28:02.220> that<10:28:02.340> in<10:28:02.520> specific<10:28:02.880> instances 10:28:03.350 --> 10:28:03.360 align:start position:0% going to use that in specific instances 10:28:03.360 --> 10:28:04.850 align:start position:0% going to use that in specific instances and<10:28:03.596> I'll<10:28:03.720> talk<10:28:03.900> about<10:28:04.080> that<10:28:04.436> a<10:28:04.620> little<10:28:04.740> bit 10:28:04.850 --> 10:28:04.860 align:start position:0% and I'll talk about that a little bit 10:28:04.860 --> 10:28:05.690 align:start position:0% and I'll talk about that a little bit later 10:28:05.690 --> 10:28:05.700 align:start position:0% later 10:28:05.700 --> 10:28:08.390 align:start position:0% later so<10:28:06.240> as<10:28:06.480> a<10:28:06.660> result<10:28:06.776> it's<10:28:07.500> very<10:28:07.740> rarely<10:28:08.096> used 10:28:08.390 --> 10:28:08.400 align:start position:0% so as a result it's very rarely used 10:28:08.400 --> 10:28:11.150 align:start position:0% so as a result it's very rarely used except<10:28:09.000> in<10:28:09.360> very<10:28:09.596> specific<10:28:10.020> instances<10:28:10.620> I'm 10:28:11.150 --> 10:28:11.160 align:start position:0% except in very specific instances I'm 10:28:11.160 --> 10:28:12.890 align:start position:0% except in very specific instances I'm guessing<10:28:11.460> you've<10:28:11.700> never<10:28:11.820> had<10:28:12.060> to<10:28:12.300> enter<10:28:12.540> the 10:28:12.890 --> 10:28:12.900 align:start position:0% guessing you've never had to enter the 10:28:12.900 --> 10:28:16.790 align:start position:0% guessing you've never had to enter the IAP<10:28:13.256> address<10:28:13.620> on<10:28:14.096> your<10:28:14.276> Soho<10:28:14.756> router<10:28:15.256> or<10:28:16.256> at 10:28:16.790 --> 10:28:16.800 align:start position:0% IAP address on your Soho router or at 10:28:16.800 --> 10:28:18.530 align:start position:0% IAP address on your Soho router or at your<10:28:17.096> computers<10:28:17.640> at<10:28:17.936> home<10:28:18.120> and<10:28:18.416> that's 10:28:18.530 --> 10:28:18.540 align:start position:0% your computers at home and that's 10:28:18.540 --> 10:28:19.850 align:start position:0% your computers at home and that's because<10:28:18.720> we're<10:28:19.080> going<10:28:19.200> to<10:28:19.320> use<10:28:19.380> this<10:28:19.680> other 10:28:19.850 --> 10:28:19.860 align:start position:0% because we're going to use this other 10:28:19.860 --> 10:28:23.266 align:start position:0% because we're going to use this other method<10:28:20.276> being<10:28:21.000> Dynamic<10:28:21.900> addressing<10:28:22.620> now<10:28:23.096> as 10:28:23.266 --> 10:28:23.276 align:start position:0% method being Dynamic addressing now as 10:28:23.276 --> 10:28:25.790 align:start position:0% method being Dynamic addressing now as the<10:28:23.460> name<10:28:23.580> Dynamic<10:28:24.416> implies<10:28:24.960> the<10:28:25.256> IP<10:28:25.620> address 10:28:25.790 --> 10:28:25.800 align:start position:0% the name Dynamic implies the IP address 10:28:25.800 --> 10:28:28.150 align:start position:0% the name Dynamic implies the IP address can<10:28:26.400> change<10:28:26.756> which<10:28:27.300> means<10:28:27.596> that<10:28:27.720> it<10:28:27.900> is 10:28:28.150 --> 10:28:28.160 align:start position:0% can change which means that it is 10:28:28.160 --> 10:28:31.670 align:start position:0% can change which means that it is automatically<10:28:29.160> assigned<10:28:30.540> now<10:28:31.020> this<10:28:31.256> is<10:28:31.380> a<10:28:31.560> lot 10:28:31.670 --> 10:28:31.680 align:start position:0% automatically assigned now this is a lot 10:28:31.680 --> 10:28:34.970 align:start position:0% automatically assigned now this is a lot more<10:28:31.916> useful<10:28:32.520> of<10:28:32.936> the<10:28:33.120> of<10:28:33.416> the<10:28:33.900> two<10:28:34.256> that<10:28:34.800> we 10:28:34.970 --> 10:28:34.980 align:start position:0% more useful of the of the two that we 10:28:34.980 --> 10:28:37.490 align:start position:0% more useful of the of the two that we have<10:28:35.160> for<10:28:35.756> many<10:28:35.936> reasons<10:28:36.480> it's<10:28:37.200> done 10:28:37.490 --> 10:28:37.500 align:start position:0% have for many reasons it's done 10:28:37.500 --> 10:28:40.670 align:start position:0% have for many reasons it's done automatically<10:28:38.276> through<10:28:39.060> a<10:28:39.416> protocol<10:28:40.200> called 10:28:40.670 --> 10:28:40.680 align:start position:0% automatically through a protocol called 10:28:40.680 --> 10:28:45.010 align:start position:0% automatically through a protocol called Dynamic<10:28:41.400> host<10:28:42.000> configuration<10:28:42.960> protocol<10:28:43.520> or 10:28:45.010 --> 10:28:45.020 align:start position:0% Dynamic host configuration protocol or 10:28:45.020 --> 10:28:49.130 align:start position:0% Dynamic host configuration protocol or DHCP<10:28:46.020> so<10:28:46.500> you<10:28:46.680> ever<10:28:46.740> hear<10:28:46.980> DHCP<10:28:47.880> that<10:28:48.720> is<10:28:48.840> what 10:28:49.130 --> 10:28:49.140 align:start position:0% DHCP so you ever hear DHCP that is what 10:28:49.140 --> 10:28:50.766 align:start position:0% DHCP so you ever hear DHCP that is what is<10:28:49.380> referred<10:28:49.860> to<10:28:49.980> when<10:28:50.220> we're<10:28:50.400> talking<10:28:50.580> about 10:28:50.766 --> 10:28:50.776 align:start position:0% is referred to when we're talking about 10:28:50.776 --> 10:28:54.230 align:start position:0% is referred to when we're talking about Dynamic<10:28:51.776> IP<10:28:52.436> addressing<10:28:52.980> this<10:28:53.580> is<10:28:53.756> part<10:28:54.000> of 10:28:54.230 --> 10:28:54.240 align:start position:0% Dynamic IP addressing this is part of 10:28:54.240 --> 10:28:57.110 align:start position:0% Dynamic IP addressing this is part of the<10:28:54.480> tcpip<10:28:55.200> suite<10:28:55.860> and<10:28:56.276> it<10:28:56.400> allows<10:28:56.700> a<10:28:56.936> central 10:28:57.110 --> 10:28:57.120 align:start position:0% the tcpip suite and it allows a central 10:28:57.120 --> 10:29:00.350 align:start position:0% the tcpip suite and it allows a central system<10:28:57.596> to<10:28:58.256> provide<10:28:58.560> IP<10:28:58.980> addresses<10:28:59.520> to<10:29:00.060> client 10:29:00.350 --> 10:29:00.360 align:start position:0% system to provide IP addresses to client 10:29:00.360 --> 10:29:02.210 align:start position:0% system to provide IP addresses to client systems<10:29:00.960> now<10:29:01.500> since<10:29:01.860> it's<10:29:02.040> done 10:29:02.210 --> 10:29:02.220 align:start position:0% systems now since it's done 10:29:02.220 --> 10:29:05.030 align:start position:0% systems now since it's done automatically<10:29:02.756> there's<10:29:03.180> no<10:29:03.596> possibility<10:29:04.256> of 10:29:05.030 --> 10:29:05.040 align:start position:0% automatically there's no possibility of 10:29:05.040 --> 10:29:07.246 align:start position:0% automatically there's no possibility of human<10:29:05.340> error<10:29:05.936> and<10:29:06.360> it's<10:29:06.480> also<10:29:06.776> a<10:29:06.960> lot<10:29:07.020> more 10:29:07.246 --> 10:29:07.256 align:start position:0% human error and it's also a lot more 10:29:07.256 --> 10:29:10.310 align:start position:0% human error and it's also a lot more efficient<10:29:07.740> than<10:29:08.160> static<10:29:08.580> IP<10:29:08.936> addressing<10:29:09.480> as<10:29:10.140> a 10:29:10.310 --> 10:29:10.320 align:start position:0% efficient than static IP addressing as a 10:29:10.320 --> 10:29:12.350 align:start position:0% efficient than static IP addressing as a result<10:29:10.500> it's<10:29:10.916> a<10:29:11.096> lot<10:29:11.220> more<10:29:11.580> common<10:29:11.820> of<10:29:12.180> a 10:29:12.350 --> 10:29:12.360 align:start position:0% result it's a lot more common of a 10:29:12.360 --> 10:29:13.310 align:start position:0% result it's a lot more common of a method 10:29:13.310 --> 10:29:13.320 align:start position:0% method 10:29:13.320 --> 10:29:16.246 align:start position:0% method uh<10:29:14.160> it<10:29:14.580> also<10:29:14.880> eliminates<10:29:15.540> the<10:29:15.840> need<10:29:15.960> to 10:29:16.246 --> 10:29:16.256 align:start position:0% uh it also eliminates the need to 10:29:16.256 --> 10:29:19.010 align:start position:0% uh it also eliminates the need to reconfigure<10:29:16.860> a<10:29:17.160> system<10:29:17.400> if<10:29:18.180> the<10:29:18.416> addressing 10:29:19.010 --> 10:29:19.020 align:start position:0% reconfigure a system if the addressing 10:29:19.020 --> 10:29:21.890 align:start position:0% reconfigure a system if the addressing scheme<10:29:19.436> is<10:29:19.860> changed<10:29:20.460> so<10:29:21.120> it's<10:29:21.416> far<10:29:21.660> more 10:29:21.890 --> 10:29:21.900 align:start position:0% scheme is changed so it's far more 10:29:21.900 --> 10:29:23.990 align:start position:0% scheme is changed so it's far more commonly<10:29:22.320> used<10:29:22.560> because<10:29:23.220> of<10:29:23.520> all<10:29:23.756> these 10:29:23.990 --> 10:29:24.000 align:start position:0% commonly used because of all these 10:29:24.000 --> 10:29:30.350 align:start position:0% commonly used because of all these reasons<10:29:24.416> like<10:29:24.960> we<10:29:25.140> just<10:29:25.320> said 10:29:30.350 --> 10:29:30.360 align:start position:0% 10:29:30.360 --> 10:29:32.570 align:start position:0% it's<10:29:30.840> more<10:29:31.020> practical<10:29:31.436> and<10:29:31.980> more<10:29:32.160> efficient 10:29:32.570 --> 10:29:32.580 align:start position:0% it's more practical and more efficient 10:29:32.580 --> 10:29:35.266 align:start position:0% it's more practical and more efficient because<10:29:33.120> I<10:29:33.540> don't<10:29:33.660> have<10:29:34.020> to<10:29:34.320> change<10:29:34.740> every 10:29:35.266 --> 10:29:35.276 align:start position:0% because I don't have to change every 10:29:35.276 --> 10:29:42.586 align:start position:0% because I don't have to change every computer 10:29:42.586 --> 10:29:42.596 align:start position:0% 10:29:42.596 --> 10:29:45.766 align:start position:0% all<10:29:43.080> I<10:29:43.200> have<10:29:43.320> to<10:29:43.436> do<10:29:43.620> is<10:29:44.040> tell<10:29:44.340> the<10:29:44.880> DHCP 10:29:45.766 --> 10:29:45.776 align:start position:0% all I have to do is tell the DHCP 10:29:45.776 --> 10:29:47.926 align:start position:0% all I have to do is tell the DHCP service<10:29:46.140> computer<10:29:46.620> we'll<10:29:47.276> talk<10:29:47.520> about<10:29:47.640> that 10:29:47.926 --> 10:29:47.936 align:start position:0% service computer we'll talk about that 10:29:47.936 --> 10:29:49.246 align:start position:0% service computer we'll talk about that in<10:29:48.120> a<10:29:48.240> second 10:29:49.246 --> 10:29:49.256 align:start position:0% in a second 10:29:49.256 --> 10:29:51.050 align:start position:0% in a second that<10:29:49.800> we're<10:29:49.980> changing<10:29:50.340> everything<10:29:50.580> and<10:29:50.936> all 10:29:51.050 --> 10:29:51.060 align:start position:0% that we're changing everything and all 10:29:51.060 --> 10:29:53.150 align:start position:0% that we're changing everything and all the<10:29:51.240> underling<10:29:51.660> computers<10:29:52.200> automatically 10:29:53.150 --> 10:29:53.160 align:start position:0% the underling computers automatically 10:29:53.160 --> 10:29:57.890 align:start position:0% the underling computers automatically are<10:29:53.340> going<10:29:53.460> to<10:29:53.640> change 10:29:57.890 --> 10:29:57.900 align:start position:0% 10:29:57.900 --> 10:30:06.050 align:start position:0% so<10:29:58.256> if<10:29:58.500> we<10:29:58.620> move<10:29:58.860> over<10:29:59.040> real<10:29:59.400> quickly 10:30:06.050 --> 10:30:06.060 align:start position:0% 10:30:06.060 --> 10:30:08.810 align:start position:0% into<10:30:06.596> our<10:30:07.200> Windows<10:30:07.680> system 10:30:08.810 --> 10:30:08.820 align:start position:0% into our Windows system 10:30:08.820 --> 10:30:15.710 align:start position:0% into our Windows system and<10:30:09.416> let's<10:30:09.720> go<10:30:10.080> into<10:30:10.860> our<10:30:11.520> Network 10:30:15.710 --> 10:30:15.720 align:start position:0% 10:30:15.720 --> 10:30:18.950 align:start position:0% properties 10:30:18.950 --> 10:30:18.960 align:start position:0% 10:30:18.960 --> 10:30:21.170 align:start position:0% and<10:30:19.380> we'll<10:30:19.500> go<10:30:19.680> ahead<10:30:19.916> and<10:30:20.520> go<10:30:20.820> to<10:30:20.936> change 10:30:21.170 --> 10:30:21.180 align:start position:0% and we'll go ahead and go to change 10:30:21.180 --> 10:30:23.150 align:start position:0% and we'll go ahead and go to change adapter<10:30:21.720> settings<10:30:21.900> I'm<10:30:22.740> going<10:30:22.916> to<10:30:22.980> right 10:30:23.150 --> 10:30:23.160 align:start position:0% adapter settings I'm going to right 10:30:23.160 --> 10:30:26.510 align:start position:0% adapter settings I'm going to right click<10:30:23.460> on<10:30:23.520> this<10:30:23.700> and<10:30:23.936> go<10:30:24.120> to<10:30:24.240> properties 10:30:26.510 --> 10:30:26.520 align:start position:0% click on this and go to properties 10:30:26.520 --> 10:30:29.890 align:start position:0% click on this and go to properties now<10:30:27.060> we'll<10:30:27.300> see<10:30:27.540> over<10:30:27.720> here<10:30:28.080> if<10:30:28.800> I<10:30:28.980> click<10:30:29.340> on 10:30:29.890 --> 10:30:29.900 align:start position:0% now we'll see over here if I click on 10:30:29.900 --> 10:30:33.586 align:start position:0% now we'll see over here if I click on tcpi<10:30:30.900> P4<10:30:31.380> and<10:30:31.860> go<10:30:32.096> to<10:30:32.220> properties<10:30:32.640> it<10:30:33.300> says 10:30:33.586 --> 10:30:33.596 align:start position:0% tcpi P4 and go to properties it says 10:30:33.596 --> 10:30:36.230 align:start position:0% tcpi P4 and go to properties it says obtain<10:30:34.020> an<10:30:34.140> IP<10:30:34.436> address<10:30:34.680> automatically 10:30:36.230 --> 10:30:36.240 align:start position:0% obtain an IP address automatically 10:30:36.240 --> 10:30:39.850 align:start position:0% obtain an IP address automatically so<10:30:36.776> through<10:30:37.220> DHCP<10:30:38.220> the<10:30:38.820> IP<10:30:39.060> address<10:30:39.240> is<10:30:39.540> being 10:30:39.850 --> 10:30:39.860 align:start position:0% so through DHCP the IP address is being 10:30:39.860 --> 10:30:42.586 align:start position:0% so through DHCP the IP address is being automatically<10:30:40.860> obtained<10:30:41.220> just<10:30:41.520> like<10:30:41.700> DNS<10:30:42.300> is 10:30:42.586 --> 10:30:42.596 align:start position:0% automatically obtained just like DNS is 10:30:42.596 --> 10:30:44.086 align:start position:0% automatically obtained just like DNS is also<10:30:42.840> going<10:30:42.960> to<10:30:43.020> be<10:30:43.080> given<10:30:43.380> out<10:30:43.500> automatically 10:30:44.086 --> 10:30:44.096 align:start position:0% also going to be given out automatically 10:30:44.096 --> 10:30:46.426 align:start position:0% also going to be given out automatically now<10:30:44.580> if<10:30:44.700> I<10:30:44.880> wanted<10:30:45.000> to<10:30:45.240> do<10:30:45.416> it<10:30:45.596> statically<10:30:46.140> I 10:30:46.426 --> 10:30:46.436 align:start position:0% now if I wanted to do it statically I 10:30:46.436 --> 10:30:48.830 align:start position:0% now if I wanted to do it statically I would<10:30:46.560> have<10:30:46.740> to<10:30:46.916> manually<10:30:47.460> assign<10:30:48.000> an<10:30:48.540> IP 10:30:48.830 --> 10:30:48.840 align:start position:0% would have to manually assign an IP 10:30:48.840 --> 10:30:50.870 align:start position:0% would have to manually assign an IP address<10:30:49.080> a<10:30:49.500> subnet<10:30:49.916> mask<10:30:50.040> and<10:30:50.400> a<10:30:50.580> default 10:30:50.870 --> 10:30:50.880 align:start position:0% address a subnet mask and a default 10:30:50.880 --> 10:30:53.690 align:start position:0% address a subnet mask and a default gateway<10:30:51.300> for<10:30:52.080> each<10:30:52.320> device<10:30:52.620> so<10:30:53.276> you<10:30:53.400> can<10:30:53.520> see 10:30:53.690 --> 10:30:53.700 align:start position:0% gateway for each device so you can see 10:30:53.700 --> 10:30:58.130 align:start position:0% gateway for each device so you can see where<10:30:53.936> we're<10:30:54.120> not<10:30:54.300> going<10:30:54.416> to<10:30:54.540> want<10:30:54.660> to<10:30:54.776> do<10:30:54.900> that 10:30:58.130 --> 10:30:58.140 align:start position:0% 10:30:58.140 --> 10:30:59.830 align:start position:0% so<10:30:58.620> let's<10:30:58.740> talk<10:30:58.916> a<10:30:59.096> little<10:30:59.220> bit<10:30:59.340> more<10:30:59.520> about 10:30:59.830 --> 10:30:59.840 align:start position:0% so let's talk a little bit more about 10:30:59.840 --> 10:31:02.746 align:start position:0% so let's talk a little bit more about DHCP<10:31:00.840> or<10:31:01.256> the<10:31:01.436> dynamic<10:31:01.860> host<10:31:02.040> configuration 10:31:02.746 --> 10:31:02.756 align:start position:0% DHCP or the dynamic host configuration 10:31:02.756 --> 10:31:03.830 align:start position:0% DHCP or the dynamic host configuration protocol 10:31:03.830 --> 10:31:03.840 align:start position:0% protocol 10:31:03.840 --> 10:31:07.310 align:start position:0% protocol this<10:31:04.620> is<10:31:04.916> the<10:31:05.220> protocol<10:31:05.520> which<10:31:05.936> assigns<10:31:06.776> IP 10:31:07.310 --> 10:31:07.320 align:start position:0% this is the protocol which assigns IP 10:31:07.320 --> 10:31:09.406 align:start position:0% this is the protocol which assigns IP addresses<10:31:07.800> and<10:31:07.980> it<10:31:08.096> does<10:31:08.220> this<10:31:08.400> first<10:31:08.640> by 10:31:09.406 --> 10:31:09.416 align:start position:0% addresses and it does this first by 10:31:09.416 --> 10:31:11.990 align:start position:0% addresses and it does this first by assigning<10:31:10.140> what's<10:31:10.740> called<10:31:11.096> or<10:31:11.460> defining 10:31:11.990 --> 10:31:12.000 align:start position:0% assigning what's called or defining 10:31:12.000 --> 10:31:14.690 align:start position:0% assigning what's called or defining rather<10:31:12.300> What's<10:31:12.596> called<10:31:12.960> the<10:31:13.320> scope<10:31:13.620> the<10:31:14.460> scope 10:31:14.690 --> 10:31:14.700 align:start position:0% rather What's called the scope the scope 10:31:14.700 --> 10:31:17.450 align:start position:0% rather What's called the scope the scope or<10:31:15.000> the<10:31:15.240> ranges<10:31:15.660> of<10:31:15.960> all<10:31:16.256> of<10:31:16.380> the<10:31:16.560> available<10:31:16.680> IP 10:31:17.450 --> 10:31:17.460 align:start position:0% or the ranges of all of the available IP 10:31:17.460 --> 10:31:19.850 align:start position:0% or the ranges of all of the available IP address<10:31:17.700> on<10:31:18.240> the<10:31:18.360> system<10:31:18.596> that's<10:31:19.140> running<10:31:19.500> the 10:31:19.850 --> 10:31:19.860 align:start position:0% address on the system that's running the 10:31:19.860 --> 10:31:24.406 align:start position:0% address on the system that's running the DHCP<10:31:20.640> service<10:31:21.200> and<10:31:22.200> what<10:31:22.680> this<10:31:22.916> does<10:31:23.220> is<10:31:24.000> it 10:31:24.406 --> 10:31:24.416 align:start position:0% DHCP service and what this does is it 10:31:24.416 --> 10:31:26.630 align:start position:0% DHCP service and what this does is it takes<10:31:24.776> one<10:31:25.320> of<10:31:25.436> the<10:31:25.500> IP<10:31:25.740> addresses<10:31:26.160> from<10:31:26.460> this 10:31:26.630 --> 10:31:26.640 align:start position:0% takes one of the IP addresses from this 10:31:26.640 --> 10:31:29.510 align:start position:0% takes one of the IP addresses from this scope<10:31:26.880> and<10:31:27.180> assigns<10:31:28.020> it<10:31:28.140> to<10:31:28.320> a<10:31:28.500> computer<10:31:28.620> or<10:31:29.340> a 10:31:29.510 --> 10:31:29.520 align:start position:0% scope and assigns it to a computer or a 10:31:29.520 --> 10:31:32.210 align:start position:0% scope and assigns it to a computer or a client<10:31:29.756> so<10:31:30.300> for<10:31:30.540> instance<10:31:30.840> let's<10:31:31.380> say<10:31:31.680> that 10:31:32.210 --> 10:31:32.220 align:start position:0% client so for instance let's say that 10:31:32.220 --> 10:31:35.150 align:start position:0% client so for instance let's say that we're<10:31:32.400> dealing<10:31:32.820> for<10:31:33.300> simplicity's<10:31:34.020> sake<10:31:34.256> with 10:31:35.150 --> 10:31:35.160 align:start position:0% we're dealing for simplicity's sake with 10:31:35.160 --> 10:31:37.570 align:start position:0% we're dealing for simplicity's sake with a<10:31:35.700> uh 10:31:37.570 --> 10:31:37.580 align:start position:0% a uh 10:31:37.580 --> 10:31:42.050 align:start position:0% a uh 192.168<10:31:38.720> Class<10:31:39.720> C<10:31:40.200> Network<10:31:40.680> so<10:31:41.400> the<10:31:41.756> scope 10:31:42.050 --> 10:31:42.060 align:start position:0% 192.168 Class C Network so the scope 10:31:42.060 --> 10:31:48.130 align:start position:0% 192.168 Class C Network so the scope might<10:31:42.776> be<10:31:43.020> something<10:31:43.380> like<10:31:43.860> 192.168 10:31:48.130 --> 10:31:48.140 align:start position:0% 10:31:48.140 --> 10:31:50.330 align:start position:0% dots<10:31:49.140> one 10:31:50.330 --> 10:31:50.340 align:start position:0% dots one 10:31:50.340 --> 10:31:52.070 align:start position:0% dots one dot<10:31:51.180> 10 10:31:52.070 --> 10:31:52.080 align:start position:0% dot 10 10:31:52.080 --> 10:31:53.766 align:start position:0% dot 10 through 10:31:53.766 --> 10:31:53.776 align:start position:0% through 10:31:53.776 --> 10:31:58.190 align:start position:0% through 254.<10:31:54.800> this<10:31:55.800> means<10:31:56.340> that<10:31:57.000> of<10:31:57.300> the<10:31:57.480> IP<10:31:57.776> addresses 10:31:58.190 --> 10:31:58.200 align:start position:0% 254. this means that of the IP addresses 10:31:58.200 --> 10:32:00.830 align:start position:0% 254. this means that of the IP addresses it's<10:31:58.436> going<10:31:58.680> to<10:31:58.916> assign<10:31:59.340> it's<10:32:00.120> not<10:32:00.480> going<10:32:00.660> to 10:32:00.830 --> 10:32:00.840 align:start position:0% it's going to assign it's not going to 10:32:00.840 --> 10:32:03.950 align:start position:0% it's going to assign it's not going to take<10:32:01.080> anything<10:32:01.560> in<10:32:02.460> front<10:32:02.700> of<10:32:02.936> the<10:32:03.180> 10.<10:32:03.596> so 10:32:03.950 --> 10:32:03.960 align:start position:0% take anything in front of the 10. so 10:32:03.960 --> 10:32:09.050 align:start position:0% take anything in front of the 10. so this<10:32:04.200> gives<10:32:04.560> us<10:32:04.740> dot<10:32:05.700> 1<10:32:06.596> through<10:32:07.256> dot<10:32:07.980> 9<10:32:08.220> to<10:32:08.820> use 10:32:09.050 --> 10:32:09.060 align:start position:0% this gives us dot 1 through dot 9 to use 10:32:09.060 --> 10:32:11.990 align:start position:0% this gives us dot 1 through dot 9 to use for<10:32:09.480> static<10:32:10.020> IP<10:32:10.380> addressing<10:32:10.980> so<10:32:11.460> what<10:32:11.820> this 10:32:11.990 --> 10:32:12.000 align:start position:0% for static IP addressing so what this 10:32:12.000 --> 10:32:16.906 align:start position:0% for static IP addressing so what this ensures<10:32:12.596> is<10:32:13.380> that<10:32:13.680> the<10:32:14.400> DHCP<10:32:15.180> server<10:32:15.840> is<10:32:16.560> not 10:32:16.906 --> 10:32:16.916 align:start position:0% ensures is that the DHCP server is not 10:32:16.916 --> 10:32:19.310 align:start position:0% ensures is that the DHCP server is not going<10:32:17.220> to<10:32:17.460> assign<10:32:17.820> an<10:32:18.060> IP<10:32:18.360> address<10:32:18.596> that<10:32:19.140> we 10:32:19.310 --> 10:32:19.320 align:start position:0% going to assign an IP address that we 10:32:19.320 --> 10:32:21.406 align:start position:0% going to assign an IP address that we have<10:32:19.500> already<10:32:19.800> manually<10:32:20.520> or<10:32:20.880> statically 10:32:21.406 --> 10:32:21.416 align:start position:0% have already manually or statically 10:32:21.416 --> 10:32:23.450 align:start position:0% have already manually or statically assigned<10:32:21.900> to<10:32:22.020> another<10:32:22.200> device<10:32:22.620> we'll<10:32:23.276> talk 10:32:23.450 --> 10:32:23.460 align:start position:0% assigned to another device we'll talk 10:32:23.460 --> 10:32:25.246 align:start position:0% assigned to another device we'll talk about<10:32:23.580> why<10:32:24.120> we<10:32:24.300> would<10:32:24.416> want<10:32:24.596> to<10:32:24.660> do<10:32:24.776> that<10:32:24.900> in<10:32:25.080> a 10:32:25.246 --> 10:32:25.256 align:start position:0% about why we would want to do that in a 10:32:25.256 --> 10:32:28.906 align:start position:0% about why we would want to do that in a minute<10:32:25.380> but<10:32:26.160> this<10:32:26.756> ensures<10:32:27.240> again<10:32:27.776> that<10:32:28.620> the 10:32:28.906 --> 10:32:28.916 align:start position:0% minute but this ensures again that the 10:32:28.916 --> 10:32:29.870 align:start position:0% minute but this ensures again that the scope 10:32:29.870 --> 10:32:29.880 align:start position:0% scope 10:32:29.880 --> 10:32:34.010 align:start position:0% scope uh<10:32:30.540> that<10:32:30.720> the<10:32:30.900> DHCP<10:32:31.680> is<10:32:32.520> not<10:32:32.820> going<10:32:33.180> to<10:32:33.596> assign 10:32:34.010 --> 10:32:34.020 align:start position:0% uh that the DHCP is not going to assign 10:32:34.020 --> 10:32:36.830 align:start position:0% uh that the DHCP is not going to assign an<10:32:34.200> IP<10:32:34.436> address<10:32:34.620> outside<10:32:35.096> of<10:32:35.400> its<10:32:35.640> scope<10:32:36.360> then 10:32:36.830 --> 10:32:36.840 align:start position:0% an IP address outside of its scope then 10:32:36.840 --> 10:32:38.330 align:start position:0% an IP address outside of its scope then what<10:32:37.020> it<10:32:37.140> does<10:32:37.320> it<10:32:37.740> takes<10:32:37.916> this<10:32:38.160> available 10:32:38.330 --> 10:32:38.340 align:start position:0% what it does it takes this available 10:32:38.340 --> 10:32:40.850 align:start position:0% what it does it takes this available address<10:32:38.880> and<10:32:39.660> assigned<10:32:40.080> it<10:32:40.140> to<10:32:40.256> the<10:32:40.500> client 10:32:40.850 --> 10:32:40.860 align:start position:0% address and assigned it to the client 10:32:40.860 --> 10:32:43.790 align:start position:0% address and assigned it to the client for<10:32:41.756> a<10:32:42.060> set<10:32:42.180> amount<10:32:42.540> of<10:32:42.660> time<10:32:42.900> and<10:32:43.500> this<10:32:43.680> is 10:32:43.790 --> 10:32:43.800 align:start position:0% for a set amount of time and this is 10:32:43.800 --> 10:32:47.150 align:start position:0% for a set amount of time and this is called<10:32:44.096> a<10:32:44.640> lease<10:32:44.936> so<10:32:45.660> the<10:32:45.840> lease<10:32:46.140> says<10:32:46.500> how 10:32:47.150 --> 10:32:47.160 align:start position:0% called a lease so the lease says how 10:32:47.160 --> 10:32:49.550 align:start position:0% called a lease so the lease says how long 10:32:49.550 --> 10:32:49.560 align:start position:0% 10:32:49.560 --> 10:32:55.070 align:start position:0% the<10:32:50.220> IP<10:32:50.580> address<10:32:50.820> is<10:32:51.360> going<10:32:51.540> to<10:32:51.840> last 10:32:55.070 --> 10:32:55.080 align:start position:0% 10:32:55.080 --> 10:32:57.890 align:start position:0% now<10:32:55.560> the<10:32:55.860> reason<10:32:56.096> that<10:32:56.460> we<10:32:56.700> had<10:32:56.936> leases<10:32:57.596> is 10:32:57.890 --> 10:32:57.900 align:start position:0% now the reason that we had leases is 10:32:57.900 --> 10:32:59.570 align:start position:0% now the reason that we had leases is because<10:32:58.080> remember<10:32:58.436> if<10:32:58.740> I<10:32:58.916> turn<10:32:59.096> off<10:32:59.276> my 10:32:59.570 --> 10:32:59.580 align:start position:0% because remember if I turn off my 10:32:59.580 --> 10:33:01.426 align:start position:0% because remember if I turn off my computer<10:32:59.756> it<10:33:00.240> no<10:33:00.416> longer<10:33:00.660> needs<10:33:01.020> an<10:33:01.140> IP 10:33:01.426 --> 10:33:01.436 align:start position:0% computer it no longer needs an IP 10:33:01.436 --> 10:33:04.670 align:start position:0% computer it no longer needs an IP address<10:33:01.680> it<10:33:02.580> also<10:33:02.820> means<10:33:03.180> that<10:33:03.596> let's<10:33:04.380> say<10:33:04.500> I'm 10:33:04.670 --> 10:33:04.680 align:start position:0% address it also means that let's say I'm 10:33:04.680 --> 10:33:07.970 align:start position:0% address it also means that let's say I'm taking<10:33:04.916> a<10:33:05.160> computer<10:33:05.340> away<10:33:06.080> I<10:33:07.080> don't<10:33:07.200> if<10:33:07.436> I<10:33:07.680> have 10:33:07.970 --> 10:33:07.980 align:start position:0% taking a computer away I don't if I have 10:33:07.980 --> 10:33:11.210 align:start position:0% taking a computer away I don't if I have a<10:33:08.276> if<10:33:08.640> it<10:33:08.756> has<10:33:08.936> a<10:33:09.120> lease<10:33:09.360> of<10:33:09.540> forever<10:33:09.960> then<10:33:10.860> that 10:33:11.210 --> 10:33:11.220 align:start position:0% a if it has a lease of forever then that 10:33:11.220 --> 10:33:13.370 align:start position:0% a if it has a lease of forever then that computer<10:33:11.460> now<10:33:11.820> has<10:33:12.000> one<10:33:12.240> of<10:33:12.360> my<10:33:12.540> available<10:33:12.720> IP 10:33:13.370 --> 10:33:13.380 align:start position:0% computer now has one of my available IP 10:33:13.380 --> 10:33:15.950 align:start position:0% computer now has one of my available IP addresses<10:33:13.916> so<10:33:14.520> sometimes<10:33:15.000> we'll<10:33:15.240> have<10:33:15.416> an<10:33:15.660> IP 10:33:15.950 --> 10:33:15.960 align:start position:0% addresses so sometimes we'll have an IP 10:33:15.960 --> 10:33:19.246 align:start position:0% addresses so sometimes we'll have an IP address<10:33:16.140> with<10:33:16.560> a<10:33:16.800> 24-hour<10:33:17.460> lease<10:33:18.060> or<10:33:18.720> maybe<10:33:18.840> a 10:33:19.246 --> 10:33:19.256 align:start position:0% address with a 24-hour lease or maybe a 10:33:19.256 --> 10:33:21.766 align:start position:0% address with a 24-hour lease or maybe a two<10:33:19.560> day<10:33:19.980> lease<10:33:20.400> but<10:33:20.880> whatever<10:33:21.000> that<10:33:21.300> lease<10:33:21.660> is 10:33:21.766 --> 10:33:21.776 align:start position:0% two day lease but whatever that lease is 10:33:21.776 --> 10:33:23.450 align:start position:0% two day lease but whatever that lease is at<10:33:22.080> the<10:33:22.200> end<10:33:22.256> of<10:33:22.436> that<10:33:22.560> lease<10:33:22.916> it's<10:33:23.040> going<10:33:23.276> to 10:33:23.450 --> 10:33:23.460 align:start position:0% at the end of that lease it's going to 10:33:23.460 --> 10:33:26.810 align:start position:0% at the end of that lease it's going to have<10:33:23.700> to<10:33:24.380> re-again<10:33:25.380> ask<10:33:25.740> for<10:33:26.040> another<10:33:26.340> IP 10:33:26.810 --> 10:33:26.820 align:start position:0% have to re-again ask for another IP 10:33:26.820 --> 10:33:28.970 align:start position:0% have to re-again ask for another IP address<10:33:27.000> this<10:33:27.840> is<10:33:27.960> also<10:33:28.200> the<10:33:28.320> way<10:33:28.436> that<10:33:28.620> we<10:33:28.860> can 10:33:28.970 --> 10:33:28.980 align:start position:0% address this is also the way that we can 10:33:28.980 --> 10:33:34.086 align:start position:0% address this is also the way that we can share<10:33:29.340> a<10:33:29.700> limited<10:33:30.060> number<10:33:30.240> of<10:33:30.480> IP<10:33:30.840> addresses 10:33:34.086 --> 10:33:34.096 align:start position:0% 10:33:34.096 --> 10:33:40.426 align:start position:0% with<10:33:35.096> a<10:33:36.060> lot<10:33:36.180> of<10:33:36.660> uh<10:33:37.256> computers<10:33:37.680> or<10:33:37.860> nodes 10:33:40.426 --> 10:33:40.436 align:start position:0% 10:33:40.436 --> 10:33:42.350 align:start position:0% so<10:33:40.916> when<10:33:41.160> we<10:33:41.276> had<10:33:41.460> the<10:33:41.640> internet<10:33:41.756> we<10:33:42.060> used<10:33:42.240> to 10:33:42.350 --> 10:33:42.360 align:start position:0% so when we had the internet we used to 10:33:42.360 --> 10:33:45.470 align:start position:0% so when we had the internet we used to dial<10:33:42.596> up<10:33:43.020> to<10:33:43.436> the<10:33:43.620> to<10:33:43.916> our<10:33:44.400> ISP<10:33:45.060> or<10:33:45.300> Internet 10:33:45.470 --> 10:33:45.480 align:start position:0% dial up to the to our ISP or Internet 10:33:45.480 --> 10:33:48.170 align:start position:0% dial up to the to our ISP or Internet service<10:33:45.900> provider<10:33:46.560> what<10:33:47.340> this<10:33:47.520> would<10:33:47.756> allow 10:33:48.170 --> 10:33:48.180 align:start position:0% service provider what this would allow 10:33:48.180 --> 10:33:50.510 align:start position:0% service provider what this would allow is<10:33:48.720> it<10:33:48.900> allowed<10:33:49.380> our 10:33:50.510 --> 10:33:50.520 align:start position:0% is it allowed our 10:33:50.520 --> 10:33:53.926 align:start position:0% is it allowed our uh<10:33:51.300> ISP<10:33:51.960> to<10:33:52.256> provide<10:33:52.620> us<10:33:52.860> with<10:33:53.276> one<10:33:53.400> IP<10:33:53.756> address 10:33:53.926 --> 10:33:53.936 align:start position:0% uh ISP to provide us with one IP address 10:33:53.936 --> 10:33:55.610 align:start position:0% uh ISP to provide us with one IP address that<10:33:54.300> only<10:33:54.416> lasted<10:33:54.776> for<10:33:54.960> a<10:33:55.080> certain<10:33:55.256> amount<10:33:55.436> of 10:33:55.610 --> 10:33:55.620 align:start position:0% that only lasted for a certain amount of 10:33:55.620 --> 10:33:58.426 align:start position:0% that only lasted for a certain amount of time<10:33:55.800> and<10:33:56.520> then<10:33:56.640> when<10:33:57.120> we<10:33:57.300> disconnected<10:33:58.200> the 10:33:58.426 --> 10:33:58.436 align:start position:0% time and then when we disconnected the 10:33:58.436 --> 10:34:00.586 align:start position:0% time and then when we disconnected the IP<10:33:58.740> address<10:33:58.980> or<10:33:59.340> disconnected<10:33:59.936> from<10:34:00.300> the 10:34:00.586 --> 10:34:00.596 align:start position:0% IP address or disconnected from the 10:34:00.596 --> 10:34:02.030 align:start position:0% IP address or disconnected from the server<10:34:00.900> and<10:34:01.080> therefore<10:34:01.320> didn't<10:34:01.500> need<10:34:01.680> the<10:34:01.800> IP 10:34:02.030 --> 10:34:02.040 align:start position:0% server and therefore didn't need the IP 10:34:02.040 --> 10:34:03.170 align:start position:0% server and therefore didn't need the IP address<10:34:02.160> it<10:34:02.400> could<10:34:02.520> assign<10:34:02.820> it<10:34:02.936> to<10:34:03.000> someone 10:34:03.170 --> 10:34:03.180 align:start position:0% address it could assign it to someone 10:34:03.180 --> 10:34:04.906 align:start position:0% address it could assign it to someone else<10:34:03.416> and<10:34:03.960> it<10:34:04.080> didn't<10:34:04.200> have<10:34:04.380> to<10:34:04.500> worry<10:34:04.740> about 10:34:04.906 --> 10:34:04.916 align:start position:0% else and it didn't have to worry about 10:34:04.916 --> 10:34:06.710 align:start position:0% else and it didn't have to worry about us<10:34:05.096> coming<10:34:05.400> back<10:34:05.640> on<10:34:05.880> and<10:34:06.060> wanting<10:34:06.360> to<10:34:06.416> use<10:34:06.540> the 10:34:06.710 --> 10:34:06.720 align:start position:0% us coming back on and wanting to use the 10:34:06.720 --> 10:34:08.870 align:start position:0% us coming back on and wanting to use the same<10:34:06.840> IP<10:34:07.140> address<10:34:07.380> because<10:34:08.040> remember<10:34:08.400> one<10:34:08.756> of 10:34:08.870 --> 10:34:08.880 align:start position:0% same IP address because remember one of 10:34:08.880 --> 10:34:13.670 align:start position:0% same IP address because remember one of the<10:34:09.000> rules<10:34:09.300> is<10:34:09.900> you<10:34:10.256> cannot 10:34:13.670 --> 10:34:13.680 align:start position:0% 10:34:13.680 --> 10:34:15.586 align:start position:0% have 10:34:15.586 --> 10:34:15.596 align:start position:0% have 10:34:15.596 --> 10:34:20.150 align:start position:0% have two<10:34:16.436> devices 10:34:20.150 --> 10:34:20.160 align:start position:0% 10:34:20.160 --> 10:34:24.470 align:start position:0% with<10:34:20.936> one<10:34:21.300> IP<10:34:21.960> address 10:34:24.470 --> 10:34:24.480 align:start position:0% 10:34:24.480 --> 10:34:27.650 align:start position:0% all<10:34:24.900> right<10:34:25.276> now<10:34:26.276> let's<10:34:26.820> talk<10:34:27.000> about<10:34:27.120> how<10:34:27.480> this 10:34:27.650 --> 10:34:27.660 align:start position:0% all right now let's talk about how this 10:34:27.660 --> 10:34:29.926 align:start position:0% all right now let's talk about how this works<10:34:27.960> from<10:34:28.200> the<10:34:28.380> client's<10:34:28.860> point<10:34:29.040> of<10:34:29.220> view 10:34:29.926 --> 10:34:29.936 align:start position:0% works from the client's point of view 10:34:29.936 --> 10:34:33.230 align:start position:0% works from the client's point of view basically<10:34:30.540> what<10:34:30.840> happens<10:34:31.140> is<10:34:31.740> I<10:34:31.980> have<10:34:32.160> a<10:34:32.520> DHCP 10:34:33.230 --> 10:34:33.240 align:start position:0% basically what happens is I have a DHCP 10:34:33.240 --> 10:34:36.470 align:start position:0% basically what happens is I have a DHCP server<10:34:33.776> here<10:34:34.436> and<10:34:35.160> it<10:34:35.340> has<10:34:35.460> what's<10:34:35.756> called<10:34:36.000> a 10:34:36.470 --> 10:34:36.480 align:start position:0% server here and it has what's called a 10:34:36.480 --> 10:34:39.586 align:start position:0% server here and it has what's called a trusted<10:34:37.020> connection<10:34:37.276> to<10:34:38.276> the<10:34:38.460> switch 10:34:39.586 --> 10:34:39.596 align:start position:0% trusted connection to the switch 10:34:39.596 --> 10:34:40.970 align:start position:0% trusted connection to the switch we'll<10:34:39.960> defined<10:34:40.320> what<10:34:40.500> a<10:34:40.620> switch<10:34:40.740> is 10:34:40.970 --> 10:34:40.980 align:start position:0% we'll defined what a switch is 10:34:40.980 --> 10:34:42.530 align:start position:0% we'll defined what a switch is previously<10:34:41.580> and<10:34:41.756> we'll<10:34:41.936> talk<10:34:42.120> a<10:34:42.240> bit<10:34:42.360> more 10:34:42.530 --> 10:34:42.540 align:start position:0% previously and we'll talk a bit more 10:34:42.540 --> 10:34:45.470 align:start position:0% previously and we'll talk a bit more about<10:34:42.720> them<10:34:42.960> later<10:34:43.200> as<10:34:43.500> well<10:34:43.680> but<10:34:44.580> it<10:34:45.120> has<10:34:45.240> a 10:34:45.470 --> 10:34:45.480 align:start position:0% about them later as well but it has a 10:34:45.480 --> 10:34:47.690 align:start position:0% about them later as well but it has a trusted<10:34:45.900> connection<10:34:46.080> this<10:34:46.980> computer<10:34:47.220> say 10:34:47.690 --> 10:34:47.700 align:start position:0% trusted connection this computer say 10:34:47.700 --> 10:34:50.330 align:start position:0% trusted connection this computer say comes<10:34:48.480> online 10:34:50.330 --> 10:34:50.340 align:start position:0% comes online 10:34:50.340 --> 10:34:53.690 align:start position:0% comes online and<10:34:51.000> says<10:34:51.480> hi 10:34:53.690 --> 10:34:53.700 align:start position:0% and says hi 10:34:53.700 --> 10:34:55.670 align:start position:0% and says hi can<10:34:54.240> I<10:34:54.360> join<10:34:54.660> your<10:34:54.840> network 10:34:55.670 --> 10:34:55.680 align:start position:0% can I join your network 10:34:55.680 --> 10:34:59.330 align:start position:0% can I join your network can<10:34:56.160> I<10:34:56.276> get<10:34:56.400> an<10:34:56.580> IP<10:34:56.880> address<10:34:57.380> it<10:34:58.380> sends<10:34:58.860> its 10:34:59.330 --> 10:34:59.340 align:start position:0% can I get an IP address it sends its 10:34:59.340 --> 10:35:01.906 align:start position:0% can I get an IP address it sends its request<10:34:59.700> through<10:35:00.480> what's<10:35:00.776> called<10:35:01.140> an 10:35:01.906 --> 10:35:01.916 align:start position:0% request through what's called an 10:35:01.916 --> 10:35:03.530 align:start position:0% request through what's called an untrusted<10:35:02.520> connection 10:35:03.530 --> 10:35:03.540 align:start position:0% untrusted connection 10:35:03.540 --> 10:35:06.650 align:start position:0% untrusted connection to<10:35:03.960> wherever<10:35:04.620> the<10:35:04.800> DHCP<10:35:05.400> server<10:35:05.756> is<10:35:05.936> now<10:35:06.480> the 10:35:06.650 --> 10:35:06.660 align:start position:0% to wherever the DHCP server is now the 10:35:06.660 --> 10:35:09.290 align:start position:0% to wherever the DHCP server is now the DHCP<10:35:07.256> server<10:35:07.680> at<10:35:07.860> some<10:35:08.040> point<10:35:08.276> finds<10:35:09.120> this 10:35:09.290 --> 10:35:09.300 align:start position:0% DHCP server at some point finds this 10:35:09.300 --> 10:35:12.950 align:start position:0% DHCP server at some point finds this because<10:35:09.540> this<10:35:09.840> is<10:35:10.020> generally<10:35:10.380> a<10:35:10.800> broadcast 10:35:12.950 --> 10:35:12.960 align:start position:0% because this is generally a broadcast 10:35:12.960 --> 10:35:15.710 align:start position:0% because this is generally a broadcast because<10:35:13.380> again<10:35:14.276> it's<10:35:14.640> not<10:35:14.820> a<10:35:15.000> unicast<10:35:15.360> it's<10:35:15.540> a 10:35:15.710 --> 10:35:15.720 align:start position:0% because again it's not a unicast it's a 10:35:15.720 --> 10:35:17.210 align:start position:0% because again it's not a unicast it's a broadcast<10:35:15.840> because<10:35:16.320> this<10:35:16.620> computer<10:35:16.800> coming 10:35:17.210 --> 10:35:17.220 align:start position:0% broadcast because this computer coming 10:35:17.220 --> 10:35:20.510 align:start position:0% broadcast because this computer coming on<10:35:17.580> doesn't<10:35:18.540> know<10:35:18.960> where<10:35:19.256> the<10:35:19.436> DHCP<10:35:19.980> server<10:35:20.340> is 10:35:20.510 --> 10:35:20.520 align:start position:0% on doesn't know where the DHCP server is 10:35:20.520 --> 10:35:23.150 align:start position:0% on doesn't know where the DHCP server is so<10:35:20.936> it<10:35:21.120> sends<10:35:21.416> a<10:35:21.540> broadcast<10:35:21.720> message<10:35:22.200> out<10:35:22.560> the 10:35:23.150 --> 10:35:23.160 align:start position:0% so it sends a broadcast message out the 10:35:23.160 --> 10:35:26.390 align:start position:0% so it sends a broadcast message out the DHC<10:35:23.640> per<10:35:23.936> P<10:35:24.660> server<10:35:24.960> then<10:35:25.200> responds<10:35:25.860> and 10:35:26.390 --> 10:35:26.400 align:start position:0% DHC per P server then responds and 10:35:26.400 --> 10:35:29.390 align:start position:0% DHC per P server then responds and offers<10:35:26.936> a<10:35:27.360> lease<10:35:27.540> on<10:35:27.660> an<10:35:27.776> IP<10:35:28.080> address<10:35:28.256> at<10:35:29.160> which 10:35:29.390 --> 10:35:29.400 align:start position:0% offers a lease on an IP address at which 10:35:29.400 --> 10:35:31.490 align:start position:0% offers a lease on an IP address at which point<10:35:29.640> this<10:35:30.000> untrusted<10:35:30.660> or<10:35:30.776> unassigned 10:35:31.490 --> 10:35:31.500 align:start position:0% point this untrusted or unassigned 10:35:31.500 --> 10:35:34.850 align:start position:0% point this untrusted or unassigned connection<10:35:32.060> becomes<10:35:33.060> a<10:35:33.776> trusted<10:35:34.256> one<10:35:34.436> now 10:35:34.850 --> 10:35:34.860 align:start position:0% connection becomes a trusted one now 10:35:34.860 --> 10:35:36.230 align:start position:0% connection becomes a trusted one now when<10:35:35.040> the<10:35:35.160> lease<10:35:35.400> goes<10:35:35.640> out<10:35:35.756> it's<10:35:36.000> again 10:35:36.230 --> 10:35:36.240 align:start position:0% when the lease goes out it's again 10:35:36.240 --> 10:35:38.450 align:start position:0% when the lease goes out it's again untrusted<10:35:37.200> and<10:35:37.500> so<10:35:37.560> it<10:35:37.740> needs<10:35:37.916> to<10:35:37.980> repeat<10:35:38.160> the 10:35:38.450 --> 10:35:38.460 align:start position:0% untrusted and so it needs to repeat the 10:35:38.460 --> 10:35:40.310 align:start position:0% untrusted and so it needs to repeat the entire<10:35:38.756> process<10:35:39.180> again 10:35:40.310 --> 10:35:40.320 align:start position:0% entire process again 10:35:40.320 --> 10:35:43.370 align:start position:0% entire process again now<10:35:40.860> so<10:35:41.096> far<10:35:41.276> we've<10:35:41.640> been<10:35:41.936> pretty<10:35:42.720> fair<10:35:43.020> to 10:35:43.370 --> 10:35:43.380 align:start position:0% now so far we've been pretty fair to 10:35:43.380 --> 10:35:46.490 align:start position:0% now so far we've been pretty fair to DHCP<10:35:44.096> and<10:35:44.520> expanded<10:35:45.240> on<10:35:45.416> the<10:35:45.540> benefits<10:35:46.080> for 10:35:46.490 --> 10:35:46.500 align:start position:0% DHCP and expanded on the benefits for 10:35:46.500 --> 10:35:49.130 align:start position:0% DHCP and expanded on the benefits for dynamic<10:35:47.460> addressing<10:35:48.060> but<10:35:48.540> there<10:35:48.840> are<10:35:48.960> some 10:35:49.130 --> 10:35:49.140 align:start position:0% dynamic addressing but there are some 10:35:49.140 --> 10:35:51.370 align:start position:0% dynamic addressing but there are some exceptions<10:35:49.560> when<10:35:49.860> a<10:35:50.040> network<10:35:50.220> is<10:35:50.520> configured 10:35:51.370 --> 10:35:51.380 align:start position:0% exceptions when a network is configured 10:35:51.380 --> 10:35:55.670 align:start position:0% exceptions when a network is configured uh<10:35:52.380> for<10:35:52.916> DHCP<10:35:53.700> and<10:35:54.300> we<10:35:54.596> don't<10:35:54.720> want<10:35:55.020> every 10:35:55.670 --> 10:35:55.680 align:start position:0% uh for DHCP and we don't want every 10:35:55.680 --> 10:35:58.310 align:start position:0% uh for DHCP and we don't want every single<10:35:56.096> device<10:35:56.340> to<10:35:56.820> be<10:35:57.320> automatically 10:35:58.310 --> 10:35:58.320 align:start position:0% single device to be automatically 10:35:58.320 --> 10:36:00.230 align:start position:0% single device to be automatically assigned<10:35:58.860> an<10:35:58.916> IP<10:35:59.276> address 10:36:00.230 --> 10:36:00.240 align:start position:0% assigned an IP address 10:36:00.240 --> 10:36:02.030 align:start position:0% assigned an IP address for<10:36:00.776> instance 10:36:02.030 --> 10:36:02.040 align:start position:0% for instance 10:36:02.040 --> 10:36:03.230 align:start position:0% for instance um 10:36:03.230 --> 10:36:03.240 align:start position:0% um 10:36:03.240 --> 10:36:07.550 align:start position:0% um the<10:36:03.840> DHCP<10:36:04.560> server<10:36:05.040> itself<10:36:05.596> needs<10:36:06.596> to<10:36:06.720> have<10:36:07.020> a 10:36:07.550 --> 10:36:07.560 align:start position:0% the DHCP server itself needs to have a 10:36:07.560 --> 10:36:10.906 align:start position:0% the DHCP server itself needs to have a static<10:36:07.916> IP<10:36:08.276> address<10:36:08.520> this<10:36:09.480> is<10:36:09.660> because<10:36:09.916> we 10:36:10.906 --> 10:36:10.916 align:start position:0% static IP address this is because we 10:36:10.916 --> 10:36:14.810 align:start position:0% static IP address this is because we don't<10:36:11.340> want<10:36:11.880> the<10:36:12.596> DHCP<10:36:13.380> server<10:36:13.916> to<10:36:14.580> be 10:36:14.810 --> 10:36:14.820 align:start position:0% don't want the DHCP server to be 10:36:14.820 --> 10:36:16.730 align:start position:0% don't want the DHCP server to be changing<10:36:15.540> addresses<10:36:16.140> and<10:36:16.320> what's<10:36:16.436> going<10:36:16.620> to 10:36:16.730 --> 10:36:16.740 align:start position:0% changing addresses and what's going to 10:36:16.740 --> 10:36:17.926 align:start position:0% changing addresses and what's going to happen<10:36:16.860> is<10:36:17.096> if<10:36:17.220> we<10:36:17.340> have<10:36:17.460> a<10:36:17.640> lease 10:36:17.926 --> 10:36:17.936 align:start position:0% happen is if we have a lease 10:36:17.936 --> 10:36:20.630 align:start position:0% happen is if we have a lease theoretically<10:36:18.596> the<10:36:18.840> DHCP<10:36:19.436> server<10:36:19.916> could 10:36:20.630 --> 10:36:20.640 align:start position:0% theoretically the DHCP server could 10:36:20.640 --> 10:36:23.810 align:start position:0% theoretically the DHCP server could change<10:36:20.936> its<10:36:21.416> IP<10:36:21.960> address<10:36:22.140> and<10:36:22.740> since<10:36:23.040> every 10:36:23.810 --> 10:36:23.820 align:start position:0% change its IP address and since every 10:36:23.820 --> 10:36:25.426 align:start position:0% change its IP address and since every computer<10:36:24.060> on<10:36:24.416> the<10:36:24.540> network<10:36:24.660> needs<10:36:25.200> to<10:36:25.320> know 10:36:25.426 --> 10:36:25.436 align:start position:0% computer on the network needs to know 10:36:25.436 --> 10:36:27.170 align:start position:0% computer on the network needs to know where<10:36:25.680> to<10:36:25.800> go<10:36:25.980> that's<10:36:26.640> going<10:36:26.820> to<10:36:26.936> have<10:36:27.060> to 10:36:27.170 --> 10:36:27.180 align:start position:0% where to go that's going to have to 10:36:27.180 --> 10:36:28.850 align:start position:0% where to go that's going to have to remain<10:36:27.480> the<10:36:27.660> same<10:36:27.840> this<10:36:28.320> is<10:36:28.436> going<10:36:28.500> to<10:36:28.620> go<10:36:28.680> the 10:36:28.850 --> 10:36:28.860 align:start position:0% remain the same this is going to go the 10:36:28.860 --> 10:36:30.950 align:start position:0% remain the same this is going to go the same<10:36:28.980> with<10:36:29.160> the<10:36:29.340> domain<10:36:29.820> name<10:36:30.120> server<10:36:30.596> so<10:36:30.776> the 10:36:30.950 --> 10:36:30.960 align:start position:0% same with the domain name server so the 10:36:30.960 --> 10:36:33.586 align:start position:0% same with the domain name server so the DNS<10:36:31.320> server<10:36:31.800> which<10:36:32.340> allows<10:36:32.820> us<10:36:33.000> to<10:36:33.300> convert 10:36:33.586 --> 10:36:33.596 align:start position:0% DNS server which allows us to convert 10:36:33.596 --> 10:36:37.190 align:start position:0% DNS server which allows us to convert between<10:36:33.960> say<10:36:34.500> google.com 10:36:37.190 --> 10:36:37.200 align:start position:0% between say google.com 10:36:37.200 --> 10:36:41.450 align:start position:0% between say google.com and<10:36:37.916> the<10:36:38.096> IP<10:36:38.460> address<10:36:38.900> so<10:36:39.900> we<10:36:40.620> don't<10:36:40.800> want<10:36:41.220> to 10:36:41.450 --> 10:36:41.460 align:start position:0% and the IP address so we don't want to 10:36:41.460 --> 10:36:43.906 align:start position:0% and the IP address so we don't want to have<10:36:41.640> to<10:36:41.936> find<10:36:42.180> this<10:36:42.480> every<10:36:42.840> single<10:36:43.140> time<10:36:43.380> and 10:36:43.906 --> 10:36:43.916 align:start position:0% have to find this every single time and 10:36:43.916 --> 10:36:45.890 align:start position:0% have to find this every single time and we<10:36:44.220> have<10:36:44.340> to<10:36:44.580> set<10:36:44.756> it<10:36:44.936> as<10:36:45.120> something<10:36:45.360> specific 10:36:45.890 --> 10:36:45.900 align:start position:0% we have to set it as something specific 10:36:45.900 --> 10:36:48.170 align:start position:0% we have to set it as something specific meaning<10:36:46.380> static<10:36:47.040> we're<10:36:47.700> also<10:36:47.936> going<10:36:48.000> to<10:36:48.060> put 10:36:48.170 --> 10:36:48.180 align:start position:0% meaning static we're also going to put 10:36:48.180 --> 10:36:51.350 align:start position:0% meaning static we're also going to put our<10:36:48.300> web<10:36:48.480> server<10:36:48.916> as<10:36:49.916> some<10:36:50.460> static<10:36:50.936> IP<10:36:51.180> address 10:36:51.350 --> 10:36:51.360 align:start position:0% our web server as some static IP address 10:36:51.360 --> 10:36:54.070 align:start position:0% our web server as some static IP address this<10:36:51.720> is<10:36:51.840> the<10:36:52.020> reason<10:36:52.140> why<10:36:52.620> if<10:36:53.276> you<10:36:53.460> wanted<10:36:53.640> to 10:36:54.070 --> 10:36:54.080 align:start position:0% this is the reason why if you wanted to 10:36:54.080 --> 10:36:56.926 align:start position:0% this is the reason why if you wanted to get<10:36:55.080> an<10:36:55.320> account<10:36:55.560> with<10:36:55.800> your<10:36:56.040> ISP<10:36:56.520> or<10:36:56.700> internet 10:36:56.926 --> 10:36:56.936 align:start position:0% get an account with your ISP or internet 10:36:56.936 --> 10:36:59.690 align:start position:0% get an account with your ISP or internet service<10:36:57.300> provider<10:36:58.380> and<10:36:58.860> you<10:36:59.040> wanted<10:36:59.160> to<10:36:59.460> run 10:36:59.690 --> 10:36:59.700 align:start position:0% service provider and you wanted to run 10:36:59.700 --> 10:37:02.990 align:start position:0% service provider and you wanted to run and<10:37:00.416> web<10:37:00.840> server<10:37:01.380> from<10:37:01.860> your<10:37:02.276> computer<10:37:02.580> at 10:37:02.990 --> 10:37:03.000 align:start position:0% and web server from your computer at 10:37:03.000 --> 10:37:05.630 align:start position:0% and web server from your computer at home<10:37:03.240> you<10:37:03.900> would<10:37:04.020> need<10:37:04.200> to<10:37:04.380> ask<10:37:04.620> for<10:37:04.980> a<10:37:05.220> static 10:37:05.630 --> 10:37:05.640 align:start position:0% home you would need to ask for a static 10:37:05.640 --> 10:37:08.746 align:start position:0% home you would need to ask for a static IP<10:37:06.000> address<10:37:06.240> be<10:37:06.900> because 10:37:08.746 --> 10:37:08.756 align:start position:0% IP address be because 10:37:08.756 --> 10:37:10.906 align:start position:0% IP address be because that's<10:37:09.360> the<10:37:09.596> only<10:37:09.720> way<10:37:10.020> that<10:37:10.380> someone<10:37:10.560> can 10:37:10.906 --> 10:37:10.916 align:start position:0% that's the only way that someone can 10:37:10.916 --> 10:37:13.010 align:start position:0% that's the only way that someone can link<10:37:11.160> through<10:37:11.820> DNS 10:37:13.010 --> 10:37:13.020 align:start position:0% link through DNS 10:37:13.020 --> 10:37:15.110 align:start position:0% link through DNS to<10:37:13.436> your<10:37:13.620> web<10:37:13.740> server<10:37:14.160> and<10:37:14.640> so<10:37:14.756> our<10:37:14.936> web 10:37:15.110 --> 10:37:15.120 align:start position:0% to your web server and so our web 10:37:15.120 --> 10:37:16.790 align:start position:0% to your web server and so our web servers<10:37:15.540> always<10:37:15.720> has<10:37:15.960> to<10:37:16.080> be<10:37:16.200> static<10:37:16.620> because 10:37:16.790 --> 10:37:16.800 align:start position:0% servers always has to be static because 10:37:16.800 --> 10:37:18.470 align:start position:0% servers always has to be static because when<10:37:16.980> I<10:37:17.160> type<10:37:17.276> in<10:37:17.400> google.com<10:37:17.936> I<10:37:18.360> always 10:37:18.470 --> 10:37:18.480 align:start position:0% when I type in google.com I always 10:37:18.480 --> 10:37:20.210 align:start position:0% when I type in google.com I always wanted<10:37:18.660> to<10:37:18.900> go<10:37:19.080> to<10:37:19.256> one<10:37:19.500> of<10:37:19.620> a<10:37:19.800> few<10:37:19.980> different 10:37:20.210 --> 10:37:20.220 align:start position:0% wanted to go to one of a few different 10:37:20.220 --> 10:37:21.890 align:start position:0% wanted to go to one of a few different IP<10:37:20.640> addresses 10:37:21.890 --> 10:37:21.900 align:start position:0% IP addresses 10:37:21.900 --> 10:37:24.050 align:start position:0% IP addresses finally<10:37:22.500> printers<10:37:23.040> are<10:37:23.276> something<10:37:23.460> else<10:37:23.756> that 10:37:24.050 --> 10:37:24.060 align:start position:0% finally printers are something else that 10:37:24.060 --> 10:37:27.230 align:start position:0% finally printers are something else that we<10:37:24.180> want<10:37:24.360> to<10:37:24.540> have 10:37:27.230 --> 10:37:27.240 align:start position:0% 10:37:27.240 --> 10:37:28.670 align:start position:0% the<10:37:27.300> printer<10:37:27.720> we<10:37:27.900> don't<10:37:28.020> want<10:37:28.140> to<10:37:28.320> move<10:37:28.436> around 10:37:28.670 --> 10:37:28.680 align:start position:0% the printer we don't want to move around 10:37:28.680 --> 10:37:31.490 align:start position:0% the printer we don't want to move around we<10:37:29.276> want<10:37:29.460> to<10:37:29.520> be<10:37:29.580> able<10:37:29.700> to<10:37:29.820> lock<10:37:30.000> it<10:37:30.180> in<10:37:30.360> when<10:37:30.660> we 10:37:31.490 --> 10:37:31.500 align:start position:0% we want to be able to lock it in when we 10:37:31.500 --> 10:37:34.370 align:start position:0% we want to be able to lock it in when we install<10:37:31.980> it<10:37:32.276> on<10:37:32.460> the<10:37:32.580> computer<10:37:33.180> same<10:37:33.900> with<10:37:34.140> any 10:37:34.370 --> 10:37:34.380 align:start position:0% install it on the computer same with any 10:37:34.380 --> 10:37:37.670 align:start position:0% install it on the computer same with any servers<10:37:35.120> also<10:37:36.120> routers<10:37:36.840> the<10:37:37.320> Gateway 10:37:37.670 --> 10:37:37.680 align:start position:0% servers also routers the Gateway 10:37:37.680 --> 10:37:40.070 align:start position:0% servers also routers the Gateway computer<10:37:38.096> or<10:37:38.756> the<10:37:38.936> Gateway<10:37:39.300> device<10:37:39.660> that 10:37:40.070 --> 10:37:40.080 align:start position:0% computer or the Gateway device that 10:37:40.080 --> 10:37:41.690 align:start position:0% computer or the Gateway device that allows<10:37:40.436> us<10:37:40.560> to<10:37:40.680> get<10:37:40.800> out<10:37:40.916> to<10:37:41.040> the<10:37:41.160> network<10:37:41.276> we 10:37:41.690 --> 10:37:41.700 align:start position:0% allows us to get out to the network we 10:37:41.700 --> 10:37:43.490 align:start position:0% allows us to get out to the network we need<10:37:41.820> that<10:37:42.000> to<10:37:42.120> remain<10:37:42.360> the<10:37:42.540> same<10:37:42.720> so<10:37:43.256> that's 10:37:43.490 --> 10:37:43.500 align:start position:0% need that to remain the same so that's 10:37:43.500 --> 10:37:45.890 align:start position:0% need that to remain the same so that's why<10:37:43.860> when<10:37:44.096> we<10:37:44.276> Define<10:37:44.460> the<10:37:44.880> scope<10:37:45.180> and<10:37:45.776> in 10:37:45.890 --> 10:37:45.900 align:start position:0% why when we Define the scope and in 10:37:45.900 --> 10:37:48.290 align:start position:0% why when we Define the scope and in previous<10:37:46.080> example<10:37:46.500> we<10:37:46.680> defined<10:37:47.040> it<10:37:47.220> as<10:37:47.400> any<10:37:47.880> IP 10:37:48.290 --> 10:37:48.300 align:start position:0% previous example we defined it as any IP 10:37:48.300 --> 10:37:50.690 align:start position:0% previous example we defined it as any IP address<10:37:48.480> between<10:37:48.840> 10<10:37:49.140> and<10:37:49.380> 254.<10:37:50.160> we<10:37:50.640> don't 10:37:50.690 --> 10:37:50.700 align:start position:0% address between 10 and 254. we don't 10:37:50.700 --> 10:37:52.730 align:start position:0% address between 10 and 254. we don't want<10:37:50.880> it<10:37:51.000> to<10:37:51.120> change 10:37:52.730 --> 10:37:52.740 align:start position:0% want it to change 10:37:52.740 --> 10:37:55.730 align:start position:0% want it to change because<10:37:53.340> we<10:37:53.820> want<10:37:54.000> these<10:37:54.720> nine<10:37:54.960> IP<10:37:55.320> addresses 10:37:55.730 --> 10:37:55.740 align:start position:0% because we want these nine IP addresses 10:37:55.740 --> 10:37:57.350 align:start position:0% because we want these nine IP addresses to<10:37:55.860> be<10:37:55.980> ones<10:37:56.276> that<10:37:56.340> we<10:37:56.520> can<10:37:56.640> assign<10:37:57.000> now 10:37:57.350 --> 10:37:57.360 align:start position:0% to be ones that we can assign now 10:37:57.360 --> 10:37:58.310 align:start position:0% to be ones that we can assign now sometimes<10:37:57.596> we're<10:37:57.720> going<10:37:57.840> to<10:37:57.900> make<10:37:58.020> this<10:37:58.140> a 10:37:58.310 --> 10:37:58.320 align:start position:0% sometimes we're going to make this a 10:37:58.320 --> 10:38:00.470 align:start position:0% sometimes we're going to make this a little larger<10:37:58.740> so<10:37:59.460> that<10:37:59.640> way 10:38:00.470 --> 10:38:00.480 align:start position:0% little larger so that way 10:38:00.480 --> 10:38:03.230 align:start position:0% little larger so that way we<10:38:00.960> can<10:38:01.020> assign<10:38:01.380> a<10:38:01.800> lot<10:38:02.096> more<10:38:02.460> static<10:38:02.936> IP 10:38:03.230 --> 10:38:03.240 align:start position:0% we can assign a lot more static IP 10:38:03.240 --> 10:38:06.110 align:start position:0% we can assign a lot more static IP addresses<10:38:03.776> so<10:38:04.380> also<10:38:04.740> maybe<10:38:04.916> a<10:38:05.276> wireless 10:38:06.110 --> 10:38:06.120 align:start position:0% addresses so also maybe a wireless 10:38:06.120 --> 10:38:08.570 align:start position:0% addresses so also maybe a wireless access<10:38:06.480> point<10:38:06.840> we<10:38:07.080> might<10:38:07.256> want<10:38:07.436> to<10:38:07.560> be<10:38:07.680> static 10:38:08.570 --> 10:38:08.580 align:start position:0% access point we might want to be static 10:38:08.580 --> 10:38:10.970 align:start position:0% access point we might want to be static etc<10:38:09.000> etc<10:38:09.180> and<10:38:09.720> all<10:38:09.840> of<10:38:09.960> this<10:38:10.080> again<10:38:10.256> is<10:38:10.620> done 10:38:10.970 --> 10:38:10.980 align:start position:0% etc etc and all of this again is done 10:38:10.980 --> 10:38:14.350 align:start position:0% etc etc and all of this again is done through<10:38:11.880> a<10:38:12.060> web<10:38:12.240> interface<10:38:12.776> or<10:38:13.256> through 10:38:14.350 --> 10:38:14.360 align:start position:0% through a web interface or through 10:38:14.360 --> 10:38:16.670 align:start position:0% through a web interface or through some<10:38:15.360> sort<10:38:15.540> of 10:38:16.670 --> 10:38:16.680 align:start position:0% some sort of 10:38:16.680 --> 10:38:18.406 align:start position:0% some sort of router 10:38:18.406 --> 10:38:18.416 align:start position:0% router 10:38:18.416 --> 10:38:20.870 align:start position:0% router device<10:38:19.200> or<10:38:19.740> through<10:38:19.980> a<10:38:20.160> terminal<10:38:20.520> or 10:38:20.870 --> 10:38:20.880 align:start position:0% device or through a terminal or 10:38:20.880 --> 10:38:22.610 align:start position:0% device or through a terminal or something<10:38:21.120> so<10:38:21.660> this<10:38:21.960> is<10:38:22.080> not<10:38:22.200> something<10:38:22.380> we're 10:38:22.610 --> 10:38:22.620 align:start position:0% something so this is not something we're 10:38:22.620 --> 10:38:24.350 align:start position:0% something so this is not something we're physically<10:38:22.980> hard<10:38:23.220> wiring<10:38:23.700> onto<10:38:24.060> the<10:38:24.180> device 10:38:24.350 --> 10:38:24.360 align:start position:0% physically hard wiring onto the device 10:38:24.360 --> 10:38:25.850 align:start position:0% physically hard wiring onto the device because<10:38:24.596> again<10:38:24.840> that's<10:38:25.200> that's<10:38:25.436> a<10:38:25.680> MAC 10:38:25.850 --> 10:38:25.860 align:start position:0% because again that's that's a MAC 10:38:25.860 --> 10:38:28.246 align:start position:0% because again that's that's a MAC address<10:38:26.096> a<10:38:26.700> physical<10:38:27.000> address<10:38:27.360> but<10:38:27.960> this<10:38:28.140> is 10:38:28.246 --> 10:38:28.256 align:start position:0% address a physical address but this is 10:38:28.256 --> 10:38:30.710 align:start position:0% address a physical address but this is something<10:38:28.436> that<10:38:28.620> we<10:38:28.740> want<10:38:28.916> to<10:38:29.096> set<10:38:29.520> through<10:38:30.180> a 10:38:30.710 --> 10:38:30.720 align:start position:0% something that we want to set through a 10:38:30.720 --> 10:38:33.650 align:start position:0% something that we want to set through a software<10:38:31.140> of<10:38:31.320> some<10:38:31.500> sort 10:38:33.650 --> 10:38:33.660 align:start position:0% software of some sort 10:38:33.660 --> 10:38:35.266 align:start position:0% software of some sort all<10:38:34.140> right<10:38:34.256> so<10:38:34.380> just<10:38:34.500> to<10:38:34.680> recap<10:38:34.916> what<10:38:35.160> we 10:38:35.266 --> 10:38:35.276 align:start position:0% all right so just to recap what we 10:38:35.276 --> 10:38:37.970 align:start position:0% all right so just to recap what we talked<10:38:35.520> about<10:38:35.640> we<10:38:36.360> defined<10:38:36.840> static<10:38:37.560> IP 10:38:37.970 --> 10:38:37.980 align:start position:0% talked about we defined static IP 10:38:37.980 --> 10:38:40.790 align:start position:0% talked about we defined static IP addressing<10:38:38.520> again<10:38:39.240> static<10:38:39.900> means<10:38:40.320> that<10:38:40.620> the 10:38:40.790 --> 10:38:40.800 align:start position:0% addressing again static means that the 10:38:40.800 --> 10:38:44.746 align:start position:0% addressing again static means that the IP<10:38:41.040> address<10:38:41.300> does<10:38:42.300> not<10:38:42.840> change 10:38:44.746 --> 10:38:44.756 align:start position:0% IP address does not change 10:38:44.756 --> 10:38:47.470 align:start position:0% IP address does not change it<10:38:45.360> also<10:38:45.660> means<10:38:46.020> that<10:38:46.500> it<10:38:46.620> had<10:38:46.800> to<10:38:46.980> have<10:38:47.096> been 10:38:47.470 --> 10:38:47.480 align:start position:0% it also means that it had to have been 10:38:47.480 --> 10:38:50.086 align:start position:0% it also means that it had to have been manually<10:38:48.480> assigned 10:38:50.086 --> 10:38:50.096 align:start position:0% manually assigned 10:38:50.096 --> 10:38:52.246 align:start position:0% manually assigned okay 10:38:52.246 --> 10:38:52.256 align:start position:0% okay 10:38:52.256 --> 10:38:54.470 align:start position:0% okay now<10:38:52.560> we<10:38:52.860> also<10:38:53.096> talked<10:38:53.340> about<10:38:53.400> Dynamic<10:38:54.120> IP 10:38:54.470 --> 10:38:54.480 align:start position:0% now we also talked about Dynamic IP 10:38:54.480 --> 10:38:55.670 align:start position:0% now we also talked about Dynamic IP addressing 10:38:55.670 --> 10:38:55.680 align:start position:0% addressing 10:38:55.680 --> 10:38:59.450 align:start position:0% addressing which<10:38:56.220> DHCP<10:38:57.180> allows<10:38:57.776> us<10:38:57.900> to<10:38:58.140> do<10:38:58.256> and<10:38:59.220> this 10:38:59.450 --> 10:38:59.460 align:start position:0% which DHCP allows us to do and this 10:38:59.460 --> 10:39:01.810 align:start position:0% which DHCP allows us to do and this means<10:38:59.756> that<10:39:00.240> the<10:39:00.416> IP<10:39:00.660> address<10:39:00.900> can<10:39:01.436> change 10:39:01.810 --> 10:39:01.820 align:start position:0% means that the IP address can change 10:39:01.820 --> 10:39:05.746 align:start position:0% means that the IP address can change because<10:39:02.820> it<10:39:03.660> is<10:39:03.776> automatically<10:39:04.560> assigned 10:39:05.746 --> 10:39:05.756 align:start position:0% because it is automatically assigned 10:39:05.756 --> 10:39:07.790 align:start position:0% because it is automatically assigned one<10:39:06.416> thing<10:39:06.596> I<10:39:06.900> didn't<10:39:07.020> specifically<10:39:07.500> talk 10:39:07.790 --> 10:39:07.800 align:start position:0% one thing I didn't specifically talk 10:39:07.800 --> 10:39:09.350 align:start position:0% one thing I didn't specifically talk about<10:39:07.916> what<10:39:08.220> we<10:39:08.340> referenced<10:39:08.880> in<10:39:09.180> previous 10:39:09.350 --> 10:39:09.360 align:start position:0% about what we referenced in previous 10:39:09.360 --> 10:39:13.370 align:start position:0% about what we referenced in previous modules<10:39:10.080> too<10:39:10.320> is<10:39:10.916> that<10:39:11.160> a<10:39:11.520> pipa<10:39:11.936> address 10:39:13.370 --> 10:39:13.380 align:start position:0% modules too is that a pipa address 10:39:13.380 --> 10:39:16.570 align:start position:0% modules too is that a pipa address that<10:39:14.040> automatically<10:39:14.580> assigned<10:39:15.360> IP<10:39:16.080> address 10:39:16.570 --> 10:39:16.580 align:start position:0% that automatically assigned IP address 10:39:16.580 --> 10:39:19.730 align:start position:0% that automatically assigned IP address which<10:39:17.580> if<10:39:17.936> the<10:39:18.180> dynamic<10:39:18.720> IP<10:39:19.080> address<10:39:19.320> system 10:39:19.730 --> 10:39:19.740 align:start position:0% which if the dynamic IP address system 10:39:19.740 --> 10:39:21.950 align:start position:0% which if the dynamic IP address system is<10:39:20.040> not<10:39:20.220> working<10:39:20.400> so<10:39:20.640> the<10:39:20.820> DHCP<10:39:21.360> server<10:39:21.776> for 10:39:21.950 --> 10:39:21.960 align:start position:0% is not working so the DHCP server for 10:39:21.960 --> 10:39:24.766 align:start position:0% is not working so the DHCP server for instance<10:39:22.200> is<10:39:22.380> down<10:39:22.740> and<10:39:23.400> it<10:39:23.580> can't<10:39:23.756> get<10:39:24.180> an<10:39:24.480> IP 10:39:24.766 --> 10:39:24.776 align:start position:0% instance is down and it can't get an IP 10:39:24.776 --> 10:39:27.170 align:start position:0% instance is down and it can't get an IP address<10:39:24.960> from<10:39:25.436> the<10:39:25.560> DHCP<10:39:26.160> server<10:39:26.580> it's<10:39:26.936> going 10:39:27.170 --> 10:39:27.180 align:start position:0% address from the DHCP server it's going 10:39:27.180 --> 10:39:29.926 align:start position:0% address from the DHCP server it's going to<10:39:27.240> assign<10:39:27.540> itself<10:39:27.900> its<10:39:28.680> own<10:39:28.860> IP<10:39:29.276> address<10:39:29.460> if 10:39:29.926 --> 10:39:29.936 align:start position:0% to assign itself its own IP address if 10:39:29.936 --> 10:39:34.310 align:start position:0% to assign itself its own IP address if you<10:39:30.060> remember<10:39:30.180> that<10:39:30.480> was<10:39:30.916> 169<10:39:31.916> about<10:39:32.460> 254<10:39:33.320> dot 10:39:34.310 --> 10:39:34.320 align:start position:0% you remember that was 169 about 254 dot 10:39:34.320 --> 10:39:37.310 align:start position:0% you remember that was 169 about 254 dot x<10:39:34.436> dot<10:39:34.916> X<10:39:35.096> so<10:39:35.520> if<10:39:35.700> you<10:39:35.880> see<10:39:36.180> this<10:39:36.776> is<10:39:36.900> your<10:39:37.080> IP 10:39:37.310 --> 10:39:37.320 align:start position:0% x dot X so if you see this is your IP 10:39:37.320 --> 10:39:40.670 align:start position:0% x dot X so if you see this is your IP address<10:39:37.500> then<10:39:38.220> guess<10:39:38.460> what<10:39:38.700> your<10:39:39.480> DHCP<10:39:40.200> server 10:39:40.670 --> 10:39:40.680 align:start position:0% address then guess what your DHCP server 10:39:40.680 --> 10:39:42.230 align:start position:0% address then guess what your DHCP server is<10:39:41.340> down 10:39:42.230 --> 10:39:42.240 align:start position:0% is down 10:39:42.240 --> 10:39:43.790 align:start position:0% is down we<10:39:42.720> also<10:39:42.900> identify<10:39:43.256> the<10:39:43.380> strengths<10:39:43.740> and 10:39:43.790 --> 10:39:43.800 align:start position:0% we also identify the strengths and 10:39:43.800 --> 10:39:47.266 align:start position:0% we also identify the strengths and weaknesses<10:39:44.340> of<10:39:44.520> each<10:39:44.640> of<10:39:44.756> these<10:39:44.936> so<10:39:46.320> um 10:39:47.266 --> 10:39:47.276 align:start position:0% weaknesses of each of these so um 10:39:47.276 --> 10:39:49.310 align:start position:0% weaknesses of each of these so um we<10:39:47.700> Define<10:39:47.820> the<10:39:48.060> static<10:39:48.416> we<10:39:48.596> Define<10:39:48.776> dynamic 10:39:49.310 --> 10:39:49.320 align:start position:0% we Define the static we Define dynamic 10:39:49.320 --> 10:39:50.746 align:start position:0% we Define the static we Define dynamic and<10:39:49.500> then<10:39:49.620> we<10:39:49.740> identify<10:39:50.096> the<10:39:50.276> strengths<10:39:50.640> and 10:39:50.746 --> 10:39:50.756 align:start position:0% and then we identify the strengths and 10:39:50.756 --> 10:39:53.266 align:start position:0% and then we identify the strengths and weaknesses<10:39:51.180> of<10:39:51.360> each<10:39:51.480> remember<10:39:51.960> the<10:39:52.740> strength 10:39:53.266 --> 10:39:53.276 align:start position:0% weaknesses of each remember the strength 10:39:53.276 --> 10:39:56.810 align:start position:0% weaknesses of each remember the strength of<10:39:53.820> dynamic<10:39:54.360> is<10:39:55.256> that 10:39:56.810 --> 10:39:56.820 align:start position:0% of dynamic is that 10:39:56.820 --> 10:39:58.970 align:start position:0% of dynamic is that it's<10:39:57.240> easy 10:39:58.970 --> 10:39:58.980 align:start position:0% it's easy 10:39:58.980 --> 10:40:01.610 align:start position:0% it's easy and<10:39:59.520> it<10:39:59.880> requires<10:40:00.416> less<10:40:00.720> work<10:40:00.960> if<10:40:01.200> we<10:40:01.380> change 10:40:01.610 --> 10:40:01.620 align:start position:0% and it requires less work if we change 10:40:01.620 --> 10:40:03.290 align:start position:0% and it requires less work if we change anything 10:40:03.290 --> 10:40:03.300 align:start position:0% anything 10:40:03.300 --> 10:40:05.330 align:start position:0% anything of<10:40:03.480> course<10:40:03.660> the<10:40:03.840> Dynamics<10:40:04.380> or<10:40:04.740> the<10:40:05.096> the 10:40:05.330 --> 10:40:05.340 align:start position:0% of course the Dynamics or the the 10:40:05.340 --> 10:40:06.950 align:start position:0% of course the Dynamics or the the downside<10:40:05.880> of<10:40:06.120> it 10:40:06.950 --> 10:40:06.960 align:start position:0% downside of it 10:40:06.960 --> 10:40:11.210 align:start position:0% downside of it could<10:40:07.320> be<10:40:07.500> this<10:40:07.680> apipa<10:40:08.756> or<10:40:09.360> we<10:40:09.660> don't<10:40:09.840> want 10:40:11.210 --> 10:40:11.220 align:start position:0% could be this apipa or we don't want 10:40:11.220 --> 10:40:13.670 align:start position:0% could be this apipa or we don't want um<10:40:11.276> the<10:40:11.880> IP<10:40:12.120> address<10:40:12.240> to<10:40:12.596> change 10:40:13.670 --> 10:40:13.680 align:start position:0% um the IP address to change 10:40:13.680 --> 10:40:16.310 align:start position:0% um the IP address to change we<10:40:14.340> also<10:40:14.580> talked<10:40:14.880> about<10:40:14.936> when<10:40:15.540> to<10:40:15.660> use<10:40:15.840> Dynamic 10:40:16.310 --> 10:40:16.320 align:start position:0% we also talked about when to use Dynamic 10:40:16.320 --> 10:40:19.490 align:start position:0% we also talked about when to use Dynamic IP<10:40:16.620> addressing<10:40:17.096> which<10:40:17.756> is<10:40:17.936> in<10:40:18.180> most<10:40:18.416> cases<10:40:18.840> we 10:40:19.490 --> 10:40:19.500 align:start position:0% IP addressing which is in most cases we 10:40:19.500 --> 10:40:23.150 align:start position:0% IP addressing which is in most cases we Define<10:40:19.620> DHCP<10:40:20.520> which<10:40:21.240> allows<10:40:21.960> a<10:40:22.436> dynamic<10:40:22.916> IP 10:40:23.150 --> 10:40:23.160 align:start position:0% Define DHCP which allows a dynamic IP 10:40:23.160 --> 10:40:24.350 align:start position:0% Define DHCP which allows a dynamic IP addressing<10:40:23.520> to<10:40:23.700> work 10:40:24.350 --> 10:40:24.360 align:start position:0% addressing to work 10:40:24.360 --> 10:40:27.470 align:start position:0% addressing to work scope<10:40:24.960> which<10:40:25.680> is<10:40:25.800> basically<10:40:26.096> the<10:40:26.520> range<10:40:26.880> of<10:40:27.060> IP 10:40:27.470 --> 10:40:27.480 align:start position:0% scope which is basically the range of IP 10:40:27.480 --> 10:40:30.950 align:start position:0% scope which is basically the range of IP addresses 10:40:30.950 --> 10:40:30.960 align:start position:0% 10:40:30.960 --> 10:40:33.830 align:start position:0% and<10:40:31.436> the<10:40:31.620> lease 10:40:33.830 --> 10:40:33.840 align:start position:0% and the lease 10:40:33.840 --> 10:40:36.050 align:start position:0% and the lease which<10:40:34.256> is<10:40:34.436> how<10:40:34.740> long<10:40:34.860> the<10:40:35.160> IP<10:40:35.400> address<10:40:35.580> is 10:40:36.050 --> 10:40:36.060 align:start position:0% which is how long the IP address is 10:40:36.060 --> 10:40:37.370 align:start position:0% which is how long the IP address is going<10:40:36.180> to<10:40:36.416> be 10:40:37.370 --> 10:40:37.380 align:start position:0% going to be 10:40:37.380 --> 10:40:39.710 align:start position:0% going to be sent<10:40:37.740> out<10:40:37.980> for<10:40:38.220> and<10:40:39.000> then<10:40:39.120> we<10:40:39.240> recognize<10:40:39.540> when 10:40:39.710 --> 10:40:39.720 align:start position:0% sent out for and then we recognize when 10:40:39.720 --> 10:40:41.990 align:start position:0% sent out for and then we recognize when static<10:40:40.080> IP<10:40:40.320> addressing<10:40:40.740> is<10:40:40.860> preferred<10:40:41.276> for 10:40:41.990 --> 10:40:42.000 align:start position:0% static IP addressing is preferred for 10:40:42.000 --> 10:40:43.246 align:start position:0% static IP addressing is preferred for instance<10:40:42.240> when<10:40:42.660> we're<10:40:42.776> dealing<10:40:43.080> with 10:40:43.246 --> 10:40:43.256 align:start position:0% instance when we're dealing with 10:40:43.256 --> 10:40:44.810 align:start position:0% instance when we're dealing with printers 10:40:44.810 --> 10:40:44.820 align:start position:0% printers 10:40:44.820 --> 10:40:46.850 align:start position:0% printers or<10:40:45.416> routers 10:40:46.850 --> 10:40:46.860 align:start position:0% or routers 10:40:46.860 --> 10:40:51.230 align:start position:0% or routers or<10:40:47.520> even<10:40:47.640> the<10:40:47.936> DHCP<10:40:48.596> server<10:40:49.080> itself 10:40:51.230 --> 10:40:51.240 align:start position:0% or even the DHCP server itself 10:40:51.240 --> 10:40:57.030 align:start position:0% or even the DHCP server itself which<10:40:51.776> we<10:40:52.020> cannot<10:40:52.380> have<10:40:52.680> change 10:40:57.030 --> 10:40:57.040 align:start position:0% 10:40:57.040 --> 10:41:13.690 align:start position:0% [Music] 10:41:13.690 --> 10:41:13.700 align:start position:0% 10:41:13.700 --> 10:41:17.926 align:start position:0% welcome<10:41:14.700> to<10:41:14.936> module<10:41:15.360> 6<10:41:15.540> lessons<10:41:16.140> lesson<10:41:16.916> 6<10:41:17.160> DNS 10:41:17.926 --> 10:41:17.936 align:start position:0% welcome to module 6 lessons lesson 6 DNS 10:41:17.936 --> 10:41:21.890 align:start position:0% welcome to module 6 lessons lesson 6 DNS the<10:41:18.180> name<10:41:18.416> naming<10:41:18.900> system 10:41:21.890 --> 10:41:21.900 align:start position:0% 10:41:21.900 --> 10:41:23.810 align:start position:0% covered<10:41:22.680> up<10:41:22.800> we're<10:41:22.980> going<10:41:23.096> to<10:41:23.220> cover<10:41:23.340> a<10:41:23.580> lot<10:41:23.700> of 10:41:23.810 --> 10:41:23.820 align:start position:0% covered up we're going to cover a lot of 10:41:23.820 --> 10:41:25.906 align:start position:0% covered up we're going to cover a lot of stuff<10:41:23.936> in<10:41:24.300> this<10:41:24.416> presentation<10:41:24.900> but<10:41:25.560> I'll<10:41:25.740> try 10:41:25.906 --> 10:41:25.916 align:start position:0% stuff in this presentation but I'll try 10:41:25.916 --> 10:41:27.890 align:start position:0% stuff in this presentation but I'll try and<10:41:26.040> get<10:41:26.160> through<10:41:26.276> as<10:41:26.520> quickly<10:41:26.820> as<10:41:26.936> I<10:41:27.120> can 10:41:27.890 --> 10:41:27.900 align:start position:0% and get through as quickly as I can 10:41:27.900 --> 10:41:30.110 align:start position:0% and get through as quickly as I can what<10:41:28.380> uh<10:41:28.560> we<10:41:28.740> need<10:41:28.800> to<10:41:28.916> know<10:41:29.040> what<10:41:29.160> DNS<10:41:29.580> is<10:41:29.820> what 10:41:30.110 --> 10:41:30.120 align:start position:0% what uh we need to know what DNS is what 10:41:30.120 --> 10:41:32.690 align:start position:0% what uh we need to know what DNS is what our<10:41:30.300> domains<10:41:30.840> the<10:41:31.560> fully<10:41:31.860> qualified<10:41:32.220> domain 10:41:32.690 --> 10:41:32.700 align:start position:0% our domains the fully qualified domain 10:41:32.700 --> 10:41:33.586 align:start position:0% our domains the fully qualified domain name 10:41:33.586 --> 10:41:33.596 align:start position:0% name 10:41:33.596 --> 10:41:36.170 align:start position:0% name the<10:41:34.020> DNS<10:41:34.380> root<10:41:34.740> servers<10:41:35.160> so<10:41:35.340> what<10:41:35.580> happens<10:41:35.820> or 10:41:36.170 --> 10:41:36.180 align:start position:0% the DNS root servers so what happens or 10:41:36.180 --> 10:41:38.810 align:start position:0% the DNS root servers so what happens or how<10:41:36.416> does<10:41:36.840> the<10:41:36.960> system<10:41:37.140> actually<10:41:37.520> how<10:41:38.520> do<10:41:38.700> we 10:41:38.810 --> 10:41:38.820 align:start position:0% how does the system actually how do we 10:41:38.820 --> 10:41:40.490 align:start position:0% how does the system actually how do we interrogate<10:41:39.360> it<10:41:39.540> and<10:41:39.720> how<10:41:39.900> does<10:41:40.020> it<10:41:40.200> update 10:41:40.490 --> 10:41:40.500 align:start position:0% interrogate it and how does it update 10:41:40.500 --> 10:41:41.690 align:start position:0% interrogate it and how does it update itself 10:41:41.690 --> 10:41:41.700 align:start position:0% itself 10:41:41.700 --> 10:41:43.730 align:start position:0% itself what<10:41:42.060> are<10:41:42.240> DNS<10:41:42.596> records<10:41:43.080> as<10:41:43.200> well<10:41:43.320> this<10:41:43.620> is 10:41:43.730 --> 10:41:43.740 align:start position:0% what are DNS records as well this is 10:41:43.740 --> 10:41:45.830 align:start position:0% what are DNS records as well this is stuff<10:41:43.980> that's<10:41:44.160> actually<10:41:44.460> in<10:41:44.880> the<10:41:45.180> syllabus 10:41:45.830 --> 10:41:45.840 align:start position:0% stuff that's actually in the syllabus 10:41:45.840 --> 10:41:47.810 align:start position:0% stuff that's actually in the syllabus now<10:41:46.800> I'm<10:41:46.916> sure<10:41:47.096> you've<10:41:47.276> already<10:41:47.400> heard<10:41:47.640> of 10:41:47.810 --> 10:41:47.820 align:start position:0% now I'm sure you've already heard of 10:41:47.820 --> 10:41:51.050 align:start position:0% now I'm sure you've already heard of domain<10:41:48.180> name<10:41:48.360> system<10:41:48.660> or<10:41:48.960> DNS<10:41:49.436> you<10:41:49.740> can<10:41:49.916> see<10:41:50.096> in 10:41:51.050 --> 10:41:51.060 align:start position:0% domain name system or DNS you can see in 10:41:51.060 --> 10:41:53.746 align:start position:0% domain name system or DNS you can see in the<10:41:51.776> um<10:41:51.840> output<10:41:52.800> here<10:41:53.040> the<10:41:53.220> image<10:41:53.520> we've 10:41:53.746 --> 10:41:53.756 align:start position:0% the um output here the image we've 10:41:53.756 --> 10:41:57.110 align:start position:0% the um output here the image we've got.com<10:41:54.620> dot<10:41:55.620> org.us<10:41:56.276> there's<10:41:56.936> actually 10:41:57.110 --> 10:41:57.120 align:start position:0% got.com dot org.us there's actually 10:41:57.120 --> 10:41:59.710 align:start position:0% got.com dot org.us there's actually loads<10:41:57.720> and<10:41:57.840> they're<10:41:58.020> added<10:41:58.800> um<10:41:58.916> quite<10:41:59.276> rapidly 10:41:59.710 --> 10:41:59.720 align:start position:0% loads and they're added um quite rapidly 10:41:59.720 --> 10:42:02.926 align:start position:0% loads and they're added um quite rapidly and<10:42:00.720> as<10:42:01.080> each<10:42:01.320> country<10:42:01.620> has 10:42:02.926 --> 10:42:02.936 align:start position:0% and as each country has 10:42:02.936 --> 10:42:05.746 align:start position:0% and as each country has um<10:42:03.000> appealed<10:42:03.960> for<10:42:04.500> their<10:42:04.680> own<10:42:04.916> top<10:42:05.520> level 10:42:05.746 --> 10:42:05.756 align:start position:0% um appealed for their own top level 10:42:05.756 --> 10:42:07.310 align:start position:0% um appealed for their own top level domain<10:42:06.180> more<10:42:06.360> and<10:42:06.540> more<10:42:06.660> have<10:42:06.776> been<10:42:06.900> added<10:42:07.200> so 10:42:07.310 --> 10:42:07.320 align:start position:0% domain more and more have been added so 10:42:07.320 --> 10:42:09.586 align:start position:0% domain more and more have been added so there's<10:42:07.436> lots<10:42:07.740> of<10:42:07.800> countries<10:42:08.300> now<10:42:09.300> that<10:42:09.480> you 10:42:09.586 --> 10:42:09.596 align:start position:0% there's lots of countries now that you 10:42:09.596 --> 10:42:11.926 align:start position:0% there's lots of countries now that you can<10:42:09.720> register<10:42:10.020> domain<10:42:10.436> names<10:42:10.680> for<10:42:11.040> some<10:42:11.820> of 10:42:11.926 --> 10:42:11.936 align:start position:0% can register domain names for some of 10:42:11.936 --> 10:42:14.210 align:start position:0% can register domain names for some of them<10:42:12.060> are<10:42:12.360> protected<10:42:12.840> for<10:42:13.200> example 10:42:14.210 --> 10:42:14.220 align:start position:0% them are protected for example 10:42:14.220 --> 10:42:18.710 align:start position:0% them are protected for example um<10:42:14.756> if<10:42:15.360> we<10:42:15.480> go<10:42:15.720> to.com 10:42:18.710 --> 10:42:18.720 align:start position:0% um if we go to.com 10:42:18.720 --> 10:42:22.550 align:start position:0% um if we go to.com dot<10:42:19.620> a<10:42:19.740> u<10:42:19.980> for<10:42:20.640> Australia<10:42:21.180> you<10:42:22.080> actually<10:42:22.256> have 10:42:22.550 --> 10:42:22.560 align:start position:0% dot a u for Australia you actually have 10:42:22.560 --> 10:42:26.746 align:start position:0% dot a u for Australia you actually have to<10:42:22.740> have<10:42:23.040> a<10:42:23.580> business<10:42:24.060> uh<10:42:24.776> number<10:42:25.020> so 10:42:26.746 --> 10:42:26.756 align:start position:0% to have a business uh number so 10:42:26.756 --> 10:42:29.510 align:start position:0% to have a business uh number so even<10:42:27.180> if<10:42:27.360> you<10:42:27.540> live<10:42:27.660> in<10:42:27.776> Australia<10:42:28.400> you<10:42:29.400> must 10:42:29.510 --> 10:42:29.520 align:start position:0% even if you live in Australia you must 10:42:29.520 --> 10:42:32.210 align:start position:0% even if you live in Australia you must have<10:42:30.060> um<10:42:30.060> it's<10:42:30.360> called<10:42:30.596> an<10:42:30.776> ABN<10:42:31.320> Australian 10:42:32.210 --> 10:42:32.220 align:start position:0% have um it's called an ABN Australian 10:42:32.220 --> 10:42:35.690 align:start position:0% have um it's called an ABN Australian business<10:42:33.120> number<10:42:33.596> so<10:42:34.500> not<10:42:34.740> you<10:42:35.276> can't<10:42:35.460> just 10:42:35.690 --> 10:42:35.700 align:start position:0% business number so not you can't just 10:42:35.700 --> 10:42:38.746 align:start position:0% business number so not you can't just have<10:42:35.880> anyone<10:42:36.480> having<10:42:37.200> a<10:42:37.436> DOT<10:42:37.740> com.eu<10:42:38.460> other 10:42:38.746 --> 10:42:38.756 align:start position:0% have anyone having a DOT com.eu other 10:42:38.756 --> 10:42:40.370 align:start position:0% have anyone having a DOT com.eu other countries<10:42:39.180> have<10:42:39.360> got<10:42:39.480> restrictions<10:42:39.960> some 10:42:40.370 --> 10:42:40.380 align:start position:0% countries have got restrictions some 10:42:40.380 --> 10:42:43.370 align:start position:0% countries have got restrictions some haven't<10:42:40.680> so<10:42:41.520> it<10:42:41.640> just<10:42:41.756> depends<10:42:42.180> on<10:42:42.480> where<10:42:43.200> you 10:42:43.370 --> 10:42:43.380 align:start position:0% haven't so it just depends on where you 10:42:43.380 --> 10:42:46.670 align:start position:0% haven't so it just depends on where you are<10:42:43.700> so<10:42:44.700> it's<10:42:45.120> the<10:42:45.300> name<10:42:45.596> of<10:42:45.776> a<10:42:46.020> computer<10:42:46.140> it's 10:42:46.670 --> 10:42:46.680 align:start position:0% are so it's the name of a computer it's 10:42:46.680 --> 10:42:49.550 align:start position:0% are so it's the name of a computer it's got<10:42:46.916> a<10:42:47.160> an<10:42:47.756> IP<10:42:48.060> address<10:42:48.240> on<10:42:48.540> the<10:42:48.660> internet<10:42:48.776> now 10:42:49.550 --> 10:42:49.560 align:start position:0% got a an IP address on the internet now 10:42:49.560 --> 10:42:50.990 align:start position:0% got a an IP address on the internet now these<10:42:49.860> can<10:42:49.980> actually<10:42:50.096> be<10:42:50.276> shared<10:42:50.700> you<10:42:50.820> can 10:42:50.990 --> 10:42:51.000 align:start position:0% these can actually be shared you can 10:42:51.000 --> 10:42:52.610 align:start position:0% these can actually be shared you can have<10:42:51.120> some<10:42:51.360> of<10:42:51.540> the<10:42:51.660> same<10:42:51.840> domain<10:42:52.200> names<10:42:52.380> if 10:42:52.610 --> 10:42:52.620 align:start position:0% have some of the same domain names if 10:42:52.620 --> 10:42:55.190 align:start position:0% have some of the same domain names if you<10:42:52.800> buy<10:42:52.980> cheap<10:42:53.220> hosting<10:42:53.820> and<10:42:54.720> they'll<10:42:54.900> all<10:42:55.080> be 10:42:55.190 --> 10:42:55.200 align:start position:0% you buy cheap hosting and they'll all be 10:42:55.200 --> 10:42:58.370 align:start position:0% you buy cheap hosting and they'll all be sitting<10:42:55.436> on<10:42:55.560> the<10:42:55.740> same<10:42:56.480> IP<10:42:57.480> address<10:42:57.720> but<10:42:58.200> this 10:42:58.370 --> 10:42:58.380 align:start position:0% sitting on the same IP address but this 10:42:58.380 --> 10:43:00.766 align:start position:0% sitting on the same IP address but this DNS<10:42:58.980> can<10:42:59.160> deal<10:42:59.276> with<10:42:59.460> this 10:43:00.766 --> 10:43:00.776 align:start position:0% DNS can deal with this 10:43:00.776 --> 10:43:03.110 align:start position:0% DNS can deal with this so<10:43:01.320> yep<10:43:01.620> that's<10:43:01.740> just<10:43:01.916> what<10:43:02.096> I've<10:43:02.220> said 10:43:03.110 --> 10:43:03.120 align:start position:0% so yep that's just what I've said 10:43:03.120 --> 10:43:05.030 align:start position:0% so yep that's just what I've said if<10:43:03.720> you<10:43:03.900> uh 10:43:05.030 --> 10:43:05.040 align:start position:0% if you uh 10:43:05.040 --> 10:43:07.790 align:start position:0% if you uh for<10:43:06.000> example<10:43:06.240> I<10:43:06.660> used<10:43:06.900> to<10:43:07.020> host<10:43:07.200> of<10:43:07.436> these<10:43:07.620> but 10:43:07.790 --> 10:43:07.800 align:start position:0% for example I used to host of these but 10:43:07.800 --> 10:43:08.950 align:start position:0% for example I used to host of these but not<10:43:07.916> anymore 10:43:08.950 --> 10:43:08.960 align:start position:0% not anymore 10:43:08.960 --> 10:43:10.610 align:start position:0% not anymore uh 10:43:10.610 --> 10:43:10.620 align:start position:0% uh 10:43:10.620 --> 10:43:16.790 align:start position:0% uh what<10:43:10.980> was<10:43:11.220> it<10:43:11.400> called<10:43:11.460> HostGator 10:43:16.790 --> 10:43:16.800 align:start position:0% 10:43:16.800 --> 10:43:19.426 align:start position:0% I'm<10:43:17.460> not<10:43:17.640> recommending<10:43:18.060> these<10:43:18.300> by<10:43:18.480> the<10:43:18.596> way 10:43:19.426 --> 10:43:19.436 align:start position:0% I'm not recommending these by the way 10:43:19.436 --> 10:43:21.470 align:start position:0% I'm not recommending these by the way you<10:43:19.860> could<10:43:19.916> have<10:43:20.160> this<10:43:20.460> guy's<10:43:21.060> website 10:43:21.470 --> 10:43:21.480 align:start position:0% you could have this guy's website 10:43:21.480 --> 10:43:23.870 align:start position:0% you could have this guy's website somebody<10:43:21.960> else's<10:43:22.560> another<10:43:23.040> person<10:43:23.460> another 10:43:23.870 --> 10:43:23.880 align:start position:0% somebody else's another person another 10:43:23.880 --> 10:43:30.766 align:start position:0% somebody else's another person another person<10:43:24.300> but<10:43:25.140> they're<10:43:25.320> all<10:43:25.560> sharing 10:43:30.766 --> 10:43:30.776 align:start position:0% 10:43:30.776 --> 10:43:33.406 align:start position:0% the<10:43:31.200> same<10:43:31.320> IP<10:43:31.620> address<10:43:31.860> but<10:43:32.820> that's<10:43:33.000> easily 10:43:33.406 --> 10:43:33.416 align:start position:0% the same IP address but that's easily 10:43:33.416 --> 10:43:34.970 align:start position:0% the same IP address but that's easily taken<10:43:33.840> care<10:43:33.960> of 10:43:34.970 --> 10:43:34.980 align:start position:0% taken care of 10:43:34.980 --> 10:43:37.130 align:start position:0% taken care of so<10:43:35.460> what<10:43:35.640> is<10:43:35.880> it<10:43:36.060> it<10:43:36.480> resolves<10:43:36.900> the<10:43:37.020> names 10:43:37.130 --> 10:43:37.140 align:start position:0% so what is it it resolves the names 10:43:37.140 --> 10:43:39.470 align:start position:0% so what is it it resolves the names associated<10:43:37.680> with<10:43:38.096> a<10:43:38.340> server<10:43:38.756> to<10:43:39.000> its<10:43:39.180> IP 10:43:39.470 --> 10:43:39.480 align:start position:0% associated with a server to its IP 10:43:39.480 --> 10:43:41.746 align:start position:0% associated with a server to its IP address 10:43:41.746 --> 10:43:41.756 align:start position:0% 10:43:41.756 --> 10:43:45.406 align:start position:0% so<10:43:42.416> you<10:43:42.720> can<10:43:42.840> see<10:43:43.140> on<10:43:43.800> my<10:43:44.096> home<10:43:44.580> computer<10:43:44.880> here 10:43:45.406 --> 10:43:45.416 align:start position:0% so you can see on my home computer here 10:43:45.416 --> 10:43:50.990 align:start position:0% so you can see on my home computer here I<10:43:46.020> issued<10:43:46.436> a<10:43:46.680> ping<10:43:47.180> cisco.com<10:43:48.380> well<10:43:49.380> this 10:43:50.990 --> 10:43:51.000 align:start position:0% I issued a ping cisco.com well this 10:43:51.000 --> 10:43:54.530 align:start position:0% I issued a ping cisco.com well this a<10:43:51.480> URL<10:43:51.960> is<10:43:52.200> sitting<10:43:52.620> on<10:43:52.980> a<10:43:53.160> server<10:43:53.540> somewhere 10:43:54.530 --> 10:43:54.540 align:start position:0% a URL is sitting on a server somewhere 10:43:54.540 --> 10:43:57.230 align:start position:0% a URL is sitting on a server somewhere and<10:43:55.380> probably<10:43:55.740> on<10:43:55.980> spread<10:43:56.220> among<10:43:56.520> quite<10:43:57.060> a<10:43:57.120> few 10:43:57.230 --> 10:43:57.240 align:start position:0% and probably on spread among quite a few 10:43:57.240 --> 10:44:01.610 align:start position:0% and probably on spread among quite a few servers<10:43:57.720> actually<10:43:57.960> but<10:43:58.916> somewhere<10:43:59.520> from<10:44:00.620> my 10:44:01.610 --> 10:44:01.620 align:start position:0% servers actually but somewhere from my 10:44:01.620 --> 10:44:02.510 align:start position:0% servers actually but somewhere from my home 10:44:02.510 --> 10:44:02.520 align:start position:0% home 10:44:02.520 --> 10:44:05.390 align:start position:0% home wherever<10:44:03.300> I<10:44:03.596> am<10:44:03.720> I've<10:44:04.380> got<10:44:04.560> to<10:44:04.680> get<10:44:04.800> through<10:44:05.040> to 10:44:05.390 --> 10:44:05.400 align:start position:0% wherever I am I've got to get through to 10:44:05.400 --> 10:44:06.370 align:start position:0% wherever I am I've got to get through to my 10:44:06.370 --> 10:44:06.380 align:start position:0% my 10:44:06.380 --> 10:44:09.766 align:start position:0% my ISP<10:44:07.460> and<10:44:08.460> then<10:44:08.640> obviously<10:44:09.060> we've<10:44:09.300> got<10:44:09.480> a<10:44:09.660> whole 10:44:09.766 --> 10:44:09.776 align:start position:0% ISP and then obviously we've got a whole 10:44:09.776 --> 10:44:11.230 align:start position:0% ISP and then obviously we've got a whole bunch<10:44:09.960> of<10:44:10.140> other<10:44:10.256> hosting<10:44:10.860> companies 10:44:11.230 --> 10:44:11.240 align:start position:0% bunch of other hosting companies 10:44:11.240 --> 10:44:14.690 align:start position:0% bunch of other hosting companies wherever<10:44:12.240> they<10:44:12.540> may<10:44:12.720> be<10:44:12.900> and<10:44:13.500> then<10:44:13.680> finally<10:44:14.096> we 10:44:14.690 --> 10:44:14.700 align:start position:0% wherever they may be and then finally we 10:44:14.700 --> 10:44:16.906 align:start position:0% wherever they may be and then finally we get<10:44:14.936> to<10:44:15.300> the<10:44:16.080> building 10:44:16.906 --> 10:44:16.916 align:start position:0% get to the building 10:44:16.916 --> 10:44:19.370 align:start position:0% get to the building hmm 10:44:19.370 --> 10:44:19.380 align:start position:0% hmm 10:44:19.380 --> 10:44:23.150 align:start position:0% hmm that<10:44:20.040> Cisco<10:44:20.900> owned<10:44:21.900> maybe<10:44:22.080> Paulo<10:44:22.620> Alto<10:44:22.980> or 10:44:23.150 --> 10:44:23.160 align:start position:0% that Cisco owned maybe Paulo Alto or 10:44:23.160 --> 10:44:24.766 align:start position:0% that Cisco owned maybe Paulo Alto or somewhere<10:44:23.460> else<10:44:23.580> but<10:44:24.120> there<10:44:24.240> has<10:44:24.416> to<10:44:24.540> be<10:44:24.596> a 10:44:24.766 --> 10:44:24.776 align:start position:0% somewhere else but there has to be a 10:44:24.776 --> 10:44:27.110 align:start position:0% somewhere else but there has to be a result<10:44:24.900> between<10:44:25.500> this<10:44:25.980> and<10:44:26.756> what<10:44:26.936> actually 10:44:27.110 --> 10:44:27.120 align:start position:0% result between this and what actually 10:44:27.120 --> 10:44:30.950 align:start position:0% result between this and what actually comes<10:44:27.776> back<10:44:28.020> because<10:44:28.560> tcpip<10:44:29.400> doesn't<10:44:29.960> ping 10:44:30.950 --> 10:44:30.960 align:start position:0% comes back because tcpip doesn't ping 10:44:30.960 --> 10:44:35.630 align:start position:0% comes back because tcpip doesn't ping names<10:44:31.500> it<10:44:32.400> pings<10:44:32.700> uh<10:44:33.416> IP<10:44:33.720> addresses<10:44:34.256> so<10:44:34.916> 172 10:44:35.630 --> 10:44:35.640 align:start position:0% names it pings uh IP addresses so 172 10:44:35.640 --> 10:44:38.990 align:start position:0% names it pings uh IP addresses so 172 163<10:44:36.680> 4.161<10:44:37.680> that<10:44:37.916> could<10:44:38.096> have<10:44:38.220> changed<10:44:38.400> but 10:44:38.990 --> 10:44:39.000 align:start position:0% 163 4.161 that could have changed but 10:44:39.000 --> 10:44:43.190 align:start position:0% 163 4.161 that could have changed but something<10:44:39.240> has<10:44:39.540> to<10:44:39.720> happen<10:44:39.900> before<10:44:41.000> the<10:44:42.200> icmp 10:44:43.190 --> 10:44:43.200 align:start position:0% something has to happen before the icmp 10:44:43.200 --> 10:44:46.190 align:start position:0% something has to happen before the icmp packet<10:44:43.740> can<10:44:44.276> be<10:44:44.460> built<10:44:44.880> and<10:44:45.360> as<10:44:45.596> you<10:44:45.776> know<10:44:45.960> from 10:44:46.190 --> 10:44:46.200 align:start position:0% packet can be built and as you know from 10:44:46.200 --> 10:44:48.406 align:start position:0% packet can be built and as you know from other<10:44:46.380> lectures<10:44:46.800> he's<10:44:47.096> got<10:44:47.276> to<10:44:47.460> have<10:44:47.640> uh 10:44:48.406 --> 10:44:48.416 align:start position:0% other lectures he's got to have uh 10:44:48.416 --> 10:44:52.010 align:start position:0% other lectures he's got to have uh inside<10:44:48.660> their<10:44:49.080> Source<10:44:49.700> destination<10:44:51.020> and 10:44:52.010 --> 10:44:52.020 align:start position:0% inside their Source destination and 10:44:52.020 --> 10:44:54.710 align:start position:0% inside their Source destination and their<10:44:52.256> data<10:44:52.916> whatever<10:44:53.460> else<10:44:53.820> inside<10:44:54.240> the 10:44:54.710 --> 10:44:54.720 align:start position:0% their data whatever else inside the 10:44:54.720 --> 10:44:58.426 align:start position:0% their data whatever else inside the packet<10:44:55.560> so<10:44:56.460> DNS<10:44:57.000> will<10:44:57.180> take<10:44:57.416> care<10:44:57.596> of<10:44:57.720> the<10:44:58.140> uh 10:44:58.426 --> 10:44:58.436 align:start position:0% packet so DNS will take care of the uh 10:44:58.436 --> 10:45:01.550 align:start position:0% packet so DNS will take care of the uh resolve<10:44:59.276> for<10:44:59.520> us 10:45:01.550 --> 10:45:01.560 align:start position:0% resolve for us 10:45:01.560 --> 10:45:03.050 align:start position:0% resolve for us when<10:45:02.040> we<10:45:02.220> tried<10:45:02.400> to<10:45:02.520> access<10:45:02.700> a 10:45:03.050 --> 10:45:03.060 align:start position:0% when we tried to access a 10:45:03.060 --> 10:45:04.906 align:start position:0% when we tried to access a samplecompany.com<10:45:03.900> from<10:45:04.256> the<10:45:04.380> web<10:45:04.500> browser 10:45:04.906 --> 10:45:04.916 align:start position:0% samplecompany.com from the web browser 10:45:04.916 --> 10:45:08.086 align:start position:0% samplecompany.com from the web browser DNS<10:45:05.660> translates<10:45:06.660> the<10:45:06.900> domain<10:45:07.200> name<10:45:07.436> into<10:45:07.860> an 10:45:08.086 --> 10:45:08.096 align:start position:0% DNS translates the domain name into an 10:45:08.096 --> 10:45:11.330 align:start position:0% DNS translates the domain name into an IP<10:45:08.340> address 10:45:11.330 --> 10:45:11.340 align:start position:0% 10:45:11.340 --> 10:45:13.850 align:start position:0% so<10:45:11.880> I've<10:45:12.060> just<10:45:12.300> put<10:45:12.480> an<10:45:12.660> IP<10:45:12.900> address<10:45:13.080> if<10:45:13.680> you're 10:45:13.850 --> 10:45:13.860 align:start position:0% so I've just put an IP address if you're 10:45:13.860 --> 10:45:15.830 align:start position:0% so I've just put an IP address if you're super<10:45:14.220> super<10:45:14.460> smart<10:45:14.756> and<10:45:14.936> got<10:45:15.120> a<10:45:15.300> great<10:45:15.416> memory 10:45:15.830 --> 10:45:15.840 align:start position:0% super super smart and got a great memory 10:45:15.840 --> 10:45:17.746 align:start position:0% super super smart and got a great memory you<10:45:16.320> could<10:45:16.436> basically<10:45:16.800> browse<10:45:17.220> the<10:45:17.400> entire 10:45:17.746 --> 10:45:17.756 align:start position:0% you could basically browse the entire 10:45:17.756 --> 10:45:21.350 align:start position:0% you could basically browse the entire internet<10:45:18.560> just<10:45:19.560> using<10:45:19.800> IP<10:45:20.160> addresses<10:45:20.700> however 10:45:21.350 --> 10:45:21.360 align:start position:0% internet just using IP addresses however 10:45:21.360 --> 10:45:23.810 align:start position:0% internet just using IP addresses however if<10:45:21.596> it's<10:45:21.720> something<10:45:22.020> new<10:45:22.436> for<10:45:23.220> example<10:45:23.460> if<10:45:23.700> you 10:45:23.810 --> 10:45:23.820 align:start position:0% if it's something new for example if you 10:45:23.820 --> 10:45:25.510 align:start position:0% if it's something new for example if you want<10:45:24.000> to<10:45:24.180> go<10:45:24.360> to 10:45:25.510 --> 10:45:25.520 align:start position:0% want to go to 10:45:25.520 --> 10:45:28.010 align:start position:0% want to go to xyzsite.com<10:45:26.520> you're<10:45:27.416> not<10:45:27.596> going<10:45:27.720> to<10:45:27.900> know 10:45:28.010 --> 10:45:28.020 align:start position:0% xyzsite.com you're not going to know 10:45:28.020 --> 10:45:29.870 align:start position:0% xyzsite.com you're not going to know obviously<10:45:28.380> the<10:45:28.620> IP<10:45:28.860> address<10:45:29.040> and<10:45:29.580> this<10:45:29.700> can 10:45:29.870 --> 10:45:29.880 align:start position:0% obviously the IP address and this can 10:45:29.880 --> 10:45:32.030 align:start position:0% obviously the IP address and this can change<10:45:30.000> over<10:45:30.300> time<10:45:30.540> by<10:45:30.776> the<10:45:30.960> way<10:45:31.020> they<10:45:31.860> can 10:45:32.030 --> 10:45:32.040 align:start position:0% change over time by the way they can 10:45:32.040 --> 10:45:33.950 align:start position:0% change over time by the way they can move<10:45:32.220> to<10:45:32.400> another<10:45:32.520> company<10:45:32.880> and<10:45:33.360> assimilate 10:45:33.950 --> 10:45:33.960 align:start position:0% move to another company and assimilate 10:45:33.960 --> 10:45:39.170 align:start position:0% move to another company and assimilate with<10:45:34.140> someone<10:45:34.916> else<10:45:35.220> or<10:45:35.460> buy<10:45:35.700> them<10:45:35.880> out 10:45:39.170 --> 10:45:39.180 align:start position:0% 10:45:39.180 --> 10:45:41.086 align:start position:0% so<10:45:39.660> that<10:45:39.776> IP<10:45:40.080> address<10:45:40.256> is<10:45:40.560> used<10:45:40.740> by<10:45:40.916> our 10:45:41.086 --> 10:45:41.096 align:start position:0% so that IP address is used by our 10:45:41.096 --> 10:45:42.650 align:start position:0% so that IP address is used by our computer<10:45:41.276> to<10:45:41.700> communicate<10:45:42.120> with<10:45:42.416> the 10:45:42.650 --> 10:45:42.660 align:start position:0% computer to communicate with the 10:45:42.660 --> 10:45:46.610 align:start position:0% computer to communicate with the corresponding<10:45:43.256> server<10:45:43.680> on<10:45:43.980> the<10:45:44.160> network 10:45:46.610 --> 10:45:46.620 align:start position:0% 10:45:46.620 --> 10:45:48.830 align:start position:0% as<10:45:47.040> a<10:45:47.276> database<10:45:47.700> DLS<10:45:48.240> knows<10:45:48.540> about<10:45:48.660> the 10:45:48.830 --> 10:45:48.840 align:start position:0% as a database DLS knows about the 10:45:48.840 --> 10:45:51.050 align:start position:0% as a database DLS knows about the relationship<10:45:49.200> between<10:45:49.500> the<10:45:49.800> domain<10:45:50.160> name<10:45:50.756> and 10:45:51.050 --> 10:45:51.060 align:start position:0% relationship between the domain name and 10:45:51.060 --> 10:45:53.690 align:start position:0% relationship between the domain name and its<10:45:51.300> IP<10:45:51.540> address<10:45:51.980> it's<10:45:52.980> a<10:45:53.220> distributed 10:45:53.690 --> 10:45:53.700 align:start position:0% its IP address it's a distributed 10:45:53.700 --> 10:45:56.266 align:start position:0% its IP address it's a distributed databases<10:45:54.360> spread<10:45:54.720> across<10:45:55.080> the<10:45:55.200> world<10:45:55.380> I'll 10:45:56.266 --> 10:45:56.276 align:start position:0% databases spread across the world I'll 10:45:56.276 --> 10:45:58.670 align:start position:0% databases spread across the world I'll come<10:45:56.460> up<10:45:56.580> to<10:45:56.756> this<10:45:56.880> morning<10:45:57.060> here<10:45:57.596> but<10:45:58.020> um 10:45:58.670 --> 10:45:58.680 align:start position:0% come up to this morning here but um 10:45:58.680 --> 10:46:01.246 align:start position:0% come up to this morning here but um you've<10:45:59.096> got<10:45:59.220> your<10:45:59.520> ISP<10:46:00.180> which<10:46:00.900> will<10:46:01.080> probably 10:46:01.246 --> 10:46:01.256 align:start position:0% you've got your ISP which will probably 10:46:01.256 --> 10:46:04.086 align:start position:0% you've got your ISP which will probably have<10:46:01.820> several<10:46:02.820> thousand<10:46:03.180> of<10:46:03.360> the<10:46:03.480> most<10:46:03.660> common 10:46:04.086 --> 10:46:04.096 align:start position:0% have several thousand of the most common 10:46:04.096 --> 10:46:07.070 align:start position:0% have several thousand of the most common DNS<10:46:05.096> addresses 10:46:07.070 --> 10:46:07.080 align:start position:0% DNS addresses 10:46:07.080 --> 10:46:09.890 align:start position:0% DNS addresses and<10:46:07.740> and<10:46:08.040> mappings<10:46:08.460> in<10:46:08.700> there<10:46:08.880> if<10:46:09.416> there<10:46:09.596> isn't 10:46:09.890 --> 10:46:09.900 align:start position:0% and and mappings in there if there isn't 10:46:09.900 --> 10:46:12.070 align:start position:0% and and mappings in there if there isn't one<10:46:10.080> there<10:46:10.320> then<10:46:10.620> when<10:46:10.800> you<10:46:11.040> do<10:46:11.276> your<10:46:11.700> search 10:46:12.070 --> 10:46:12.080 align:start position:0% one there then when you do your search 10:46:12.080 --> 10:46:13.850 align:start position:0% one there then when you do your search at<10:46:13.080> home 10:46:13.850 --> 10:46:13.860 align:start position:0% at home 10:46:13.860 --> 10:46:15.710 align:start position:0% at home if<10:46:14.160> it's<10:46:14.276> not<10:46:14.520> there<10:46:14.700> then<10:46:14.936> quite<10:46:15.240> quickly<10:46:15.540> it 10:46:15.710 --> 10:46:15.720 align:start position:0% if it's not there then quite quickly it 10:46:15.720 --> 10:46:17.746 align:start position:0% if it's not there then quite quickly it will<10:46:15.900> be<10:46:16.020> forwarded<10:46:16.500> to 10:46:17.746 --> 10:46:17.756 align:start position:0% will be forwarded to 10:46:17.756 --> 10:46:21.050 align:start position:0% will be forwarded to like<10:46:18.240> possibly<10:46:18.720> it<10:46:19.256> might<10:46:19.500> not<10:46:19.680> be<10:46:19.800> the<10:46:20.340> um<10:46:20.400> one 10:46:21.050 --> 10:46:21.060 align:start position:0% like possibly it might not be the um one 10:46:21.060 --> 10:46:22.426 align:start position:0% like possibly it might not be the um one of<10:46:21.180> the<10:46:21.240> root<10:46:21.416> servers<10:46:21.776> which<10:46:21.900> I'll<10:46:22.140> come<10:46:22.256> to 10:46:22.426 --> 10:46:22.436 align:start position:0% of the root servers which I'll come to 10:46:22.436 --> 10:46:25.850 align:start position:0% of the root servers which I'll come to but<10:46:22.916> it<10:46:23.096> might<10:46:23.340> be<10:46:23.520> an<10:46:24.480> authoritative<10:46:25.140> DNS 10:46:25.850 --> 10:46:25.860 align:start position:0% but it might be an authoritative DNS 10:46:25.860 --> 10:46:28.970 align:start position:0% but it might be an authoritative DNS server<10:46:26.276> that<10:46:26.880> will<10:46:27.060> hopefully<10:46:27.660> resolve<10:46:28.620> if 10:46:28.970 --> 10:46:28.980 align:start position:0% server that will hopefully resolve if 10:46:28.980 --> 10:46:32.450 align:start position:0% server that will hopefully resolve if not<10:46:29.160> then<10:46:29.640> it<10:46:29.820> can<10:46:30.000> carry<10:46:30.240> on 10:46:32.450 --> 10:46:32.460 align:start position:0% 10:46:32.460 --> 10:46:36.170 align:start position:0% it<10:46:32.880> uses<10:46:33.416> UDP<10:46:33.776> Port<10:46:34.080> 53<10:46:34.680> just<10:46:35.096> uh<10:46:35.520> bear<10:46:35.820> that<10:46:36.060> in 10:46:36.170 --> 10:46:36.180 align:start position:0% it uses UDP Port 53 just uh bear that in 10:46:36.180 --> 10:46:38.030 align:start position:0% it uses UDP Port 53 just uh bear that in mind<10:46:36.360> because<10:46:36.900> you<10:46:37.200> could<10:46:37.436> come<10:46:37.620> up<10:46:37.740> in<10:46:37.916> the 10:46:38.030 --> 10:46:38.040 align:start position:0% mind because you could come up in the 10:46:38.040 --> 10:46:39.070 align:start position:0% mind because you could come up in the exam 10:46:39.070 --> 10:46:39.080 align:start position:0% exam 10:46:39.080 --> 10:46:43.850 align:start position:0% exam uh<10:46:40.080> just<10:46:40.620> people<10:46:41.520> argue<10:46:42.000> that<10:46:42.360> it<10:46:42.660> DNS<10:46:43.620> doesn't 10:46:43.850 --> 10:46:43.860 align:start position:0% uh just people argue that it DNS doesn't 10:46:43.860 --> 10:46:44.870 align:start position:0% uh just people argue that it DNS doesn't use 10:46:44.870 --> 10:46:44.880 align:start position:0% use 10:46:44.880 --> 10:46:48.830 align:start position:0% use UDP<10:46:45.240> it<10:46:45.660> does<10:46:45.840> for<10:46:46.380> our<10:46:46.500> for<10:46:46.916> our<10:46:47.040> purposes<10:46:47.840> DNS 10:46:48.830 --> 10:46:48.840 align:start position:0% UDP it does for our for our purposes DNS 10:46:48.840 --> 10:46:51.406 align:start position:0% UDP it does for our for our purposes DNS uses<10:46:49.436> UDP<10:46:49.800> now<10:46:50.340> if<10:46:50.580> you<10:46:50.700> happen<10:46:50.880> to<10:46:51.120> be<10:46:51.240> working 10:46:51.406 --> 10:46:51.416 align:start position:0% uses UDP now if you happen to be working 10:46:51.416 --> 10:46:55.370 align:start position:0% uses UDP now if you happen to be working for<10:46:51.720> an<10:46:51.900> internet<10:46:52.020> service<10:46:52.680> provider<10:46:53.400> then<10:46:54.776> um 10:46:55.370 --> 10:46:55.380 align:start position:0% for an internet service provider then um 10:46:55.380 --> 10:46:58.310 align:start position:0% for an internet service provider then um TCP<10:46:56.340> is<10:46:56.756> used<10:46:57.000> but<10:46:57.540> it's<10:46:57.660> used<10:46:57.840> for<10:46:58.020> Zone 10:46:58.310 --> 10:46:58.320 align:start position:0% TCP is used but it's used for Zone 10:46:58.320 --> 10:47:02.210 align:start position:0% TCP is used but it's used for Zone transfer<10:46:58.800> so<10:46:59.040> all<10:46:59.340> the<10:46:59.580> domain<10:46:59.880> names<10:47:00.180> that<10:47:01.380> um 10:47:02.210 --> 10:47:02.220 align:start position:0% transfer so all the domain names that um 10:47:02.220 --> 10:47:03.650 align:start position:0% transfer so all the domain names that um will<10:47:02.640> be<10:47:02.756> transferred<10:47:03.240> across<10:47:03.480> that 10:47:03.650 --> 10:47:03.660 align:start position:0% will be transferred across that 10:47:03.660 --> 10:47:05.870 align:start position:0% will be transferred across that obviously<10:47:03.960> has<10:47:04.080> to<10:47:04.200> be<10:47:04.256> done<10:47:04.436> reliably<10:47:04.916> or 10:47:05.870 --> 10:47:05.880 align:start position:0% obviously has to be done reliably or 10:47:05.880 --> 10:47:07.490 align:start position:0% obviously has to be done reliably or large<10:47:06.180> requests 10:47:07.490 --> 10:47:07.500 align:start position:0% large requests 10:47:07.500 --> 10:47:12.890 align:start position:0% large requests it<10:47:08.220> can<10:47:08.400> also<10:47:08.756> be<10:47:09.000> used<10:47:09.240> if<10:47:09.596> there's<10:47:09.776> multiple 10:47:12.890 --> 10:47:12.900 align:start position:0% 10:47:12.900 --> 10:47:14.630 align:start position:0% this<10:47:13.500> depends<10:47:13.800> how<10:47:13.980> you've<10:47:14.160> got<10:47:14.276> it<10:47:14.400> all<10:47:14.460> set 10:47:14.630 --> 10:47:14.640 align:start position:0% this depends how you've got it all set 10:47:14.640 --> 10:47:16.426 align:start position:0% this depends how you've got it all set up<10:47:14.756> if<10:47:15.120> there's<10:47:15.240> multiple<10:47:15.660> failures<10:47:16.080> looking 10:47:16.426 --> 10:47:16.436 align:start position:0% up if there's multiple failures looking 10:47:16.436 --> 10:47:18.130 align:start position:0% up if there's multiple failures looking for 10:47:18.130 --> 10:47:18.140 align:start position:0% for 10:47:18.140 --> 10:47:23.030 align:start position:0% for xyz.com<10:47:19.220> then<10:47:20.220> it<10:47:20.400> could<10:47:20.580> also<10:47:21.200> move<10:47:22.200> to<10:47:22.436> TCP 10:47:23.030 --> 10:47:23.040 align:start position:0% xyz.com then it could also move to TCP 10:47:23.040 --> 10:47:25.670 align:start position:0% xyz.com then it could also move to TCP this<10:47:23.580> is<10:47:23.700> because<10:47:23.936> it<10:47:24.300> could<10:47:24.416> be<10:47:24.596> caused<10:47:25.080> by<10:47:25.256> a 10:47:25.670 --> 10:47:25.680 align:start position:0% this is because it could be caused by a 10:47:25.680 --> 10:47:28.550 align:start position:0% this is because it could be caused by a UDP<10:47:25.980> dropouts<10:47:26.580> or<10:47:26.756> fragmentation 10:47:28.550 --> 10:47:28.560 align:start position:0% UDP dropouts or fragmentation 10:47:28.560 --> 10:47:30.230 align:start position:0% UDP dropouts or fragmentation but<10:47:29.040> we<10:47:29.400> probably<10:47:29.580> wouldn't<10:47:29.756> need<10:47:30.000> to<10:47:30.120> worry 10:47:30.230 --> 10:47:30.240 align:start position:0% but we probably wouldn't need to worry 10:47:30.240 --> 10:47:33.766 align:start position:0% but we probably wouldn't need to worry about<10:47:30.416> that<10:47:30.660> for<10:47:30.960> our<10:47:31.080> day-to-day<10:47:31.620> jobs 10:47:33.766 --> 10:47:33.776 align:start position:0% about that for our day-to-day jobs 10:47:33.776 --> 10:47:37.010 align:start position:0% about that for our day-to-day jobs our<10:47:34.256> DNS<10:47:34.680> database<10:47:35.276> or<10:47:35.756> the<10:47:35.936> DNS<10:47:36.480> database 10:47:37.010 --> 10:47:37.020 align:start position:0% our DNS database or the DNS database 10:47:37.020 --> 10:47:39.230 align:start position:0% our DNS database or the DNS database divided<10:47:37.500> into<10:47:37.620> sections<10:47:38.040> called<10:47:38.220> zones<10:47:38.640> these 10:47:39.230 --> 10:47:39.240 align:start position:0% divided into sections called zones these 10:47:39.240 --> 10:47:40.970 align:start position:0% divided into sections called zones these store<10:47:39.360> name<10:47:39.596> information<10:47:39.900> about<10:47:40.380> one<10:47:40.680> or<10:47:40.860> more 10:47:40.970 --> 10:47:40.980 align:start position:0% store name information about one or more 10:47:40.980 --> 10:47:44.450 align:start position:0% store name information about one or more domains 10:47:44.450 --> 10:47:44.460 align:start position:0% 10:47:44.460 --> 10:47:46.426 align:start position:0% and<10:47:44.936> the<10:47:45.120> domain<10:47:45.416> is<10:47:45.596> included<10:47:45.960> in<10:47:46.140> the<10:47:46.256> zone 10:47:46.426 --> 10:47:46.436 align:start position:0% and the domain is included in the zone 10:47:46.436 --> 10:47:48.470 align:start position:0% and the domain is included in the zone The<10:47:46.680> Zone<10:47:46.860> becomes<10:47:47.220> an<10:47:47.460> authoritative<10:47:48.000> source 10:47:48.470 --> 10:47:48.480 align:start position:0% The Zone becomes an authoritative source 10:47:48.480 --> 10:47:52.850 align:start position:0% The Zone becomes an authoritative source of<10:47:48.596> information<10:47:48.840> about<10:47:49.500> that<10:47:49.800> domain 10:47:52.850 --> 10:47:52.860 align:start position:0% 10:47:52.860 --> 10:47:55.426 align:start position:0% so<10:47:53.220> as<10:47:53.400> I've<10:47:53.580> already<10:47:53.756> said<10:47:54.060> we<10:47:54.776> need<10:47:55.020> our 10:47:55.426 --> 10:47:55.436 align:start position:0% so as I've already said we need our 10:47:55.436 --> 10:47:58.310 align:start position:0% so as I've already said we need our routers<10:47:55.980> and<10:47:56.580> multiles<10:47:57.300> which<10:47:57.540> is<10:47:57.660> we<10:47:57.900> we 10:47:58.310 --> 10:47:58.320 align:start position:0% routers and multiles which is we we 10:47:58.320 --> 10:48:00.050 align:start position:0% routers and multiles which is we we concerned<10:47:58.860> about<10:47:58.916> IP<10:47:59.340> addresses<10:47:59.756> to<10:47:59.936> make 10:48:00.050 --> 10:48:00.060 align:start position:0% concerned about IP addresses to make 10:48:00.060 --> 10:48:02.086 align:start position:0% concerned about IP addresses to make forwarding<10:48:00.596> decisions<10:48:00.960> so<10:48:01.500> we<10:48:01.680> had<10:48:01.860> to<10:48:01.980> have 10:48:02.086 --> 10:48:02.096 align:start position:0% forwarding decisions so we had to have 10:48:02.096 --> 10:48:07.550 align:start position:0% forwarding decisions so we had to have this<10:48:02.340> service<10:48:02.580> created 10:48:07.550 --> 10:48:07.560 align:start position:0% 10:48:07.560 --> 10:48:09.290 align:start position:0% uh<10:48:08.220> you<10:48:08.400> we<10:48:08.580> know<10:48:08.756> this<10:48:08.936> stuff<10:48:09.120> already 10:48:09.290 --> 10:48:09.300 align:start position:0% uh you we know this stuff already 10:48:09.300 --> 10:48:11.630 align:start position:0% uh you we know this stuff already difficult<10:48:09.960> to<10:48:10.140> remember<10:48:10.320> kind<10:48:10.860> of<10:48:10.980> alluded<10:48:11.460> to 10:48:11.630 --> 10:48:11.640 align:start position:0% difficult to remember kind of alluded to 10:48:11.640 --> 10:48:14.990 align:start position:0% difficult to remember kind of alluded to it 10:48:14.990 --> 10:48:15.000 align:start position:0% 10:48:15.000 --> 10:48:17.690 align:start position:0% so<10:48:15.776> the<10:48:16.080> IP<10:48:16.380> address<10:48:16.560> with<10:48:16.916> the<10:48:17.040> domain<10:48:17.276> system 10:48:17.690 --> 10:48:17.700 align:start position:0% so the IP address with the domain system 10:48:17.700 --> 10:48:19.790 align:start position:0% so the IP address with the domain system we<10:48:17.936> don't<10:48:18.060> need<10:48:18.180> to<10:48:18.360> go<10:48:19.256> through<10:48:19.380> the<10:48:19.500> headache 10:48:19.790 --> 10:48:19.800 align:start position:0% we don't need to go through the headache 10:48:19.800 --> 10:48:23.150 align:start position:0% we don't need to go through the headache of<10:48:19.916> remembering<10:48:20.400> the<10:48:20.756> IP<10:48:21.060> addresses 10:48:23.150 --> 10:48:23.160 align:start position:0% of remembering the IP addresses 10:48:23.160 --> 10:48:25.010 align:start position:0% of remembering the IP addresses a<10:48:23.460> little<10:48:23.520> flogging<10:48:24.000> the<10:48:24.180> flogging<10:48:24.776> the<10:48:24.900> point 10:48:25.010 --> 10:48:25.020 align:start position:0% a little flogging the flogging the point 10:48:25.020 --> 10:48:26.510 align:start position:0% a little flogging the flogging the point a<10:48:25.256> bit<10:48:25.320> here 10:48:26.510 --> 10:48:26.520 align:start position:0% a bit here 10:48:26.520 --> 10:48:29.746 align:start position:0% a bit here so<10:48:27.300> the<10:48:27.660> DNS<10:48:28.020> name<10:48:28.200> system<10:48:28.560> is<10:48:28.800> based<10:48:29.220> upon<10:48:29.520> the 10:48:29.746 --> 10:48:29.756 align:start position:0% so the DNS name system is based upon the 10:48:29.756 --> 10:48:31.850 align:start position:0% so the DNS name system is based upon the domain<10:48:30.120> name<10:48:30.360> space 10:48:31.850 --> 10:48:31.860 align:start position:0% domain name space 10:48:31.860 --> 10:48:33.530 align:start position:0% domain name space collection<10:48:32.276> of<10:48:32.460> unique<10:48:32.756> names<10:48:32.936> that<10:48:33.180> denote 10:48:33.530 --> 10:48:33.540 align:start position:0% collection of unique names that denote 10:48:33.540 --> 10:48:35.390 align:start position:0% collection of unique names that denote other<10:48:33.840> kinds<10:48:34.256> of<10:48:34.320> information<10:48:34.560> such<10:48:35.096> as<10:48:35.276> the 10:48:35.390 --> 10:48:35.400 align:start position:0% other kinds of information such as the 10:48:35.400 --> 10:48:37.610 align:start position:0% other kinds of information such as the IP<10:48:35.700> address<10:48:35.880> now<10:48:36.840> there<10:48:37.020> has<10:48:37.200> to<10:48:37.320> be<10:48:37.436> certain 10:48:37.610 --> 10:48:37.620 align:start position:0% IP address now there has to be certain 10:48:37.620 --> 10:48:39.890 align:start position:0% IP address now there has to be certain rules<10:48:37.980> in<10:48:38.096> place<10:48:38.340> obviously<10:48:38.936> and<10:48:39.416> these<10:48:39.660> rules 10:48:39.890 --> 10:48:39.900 align:start position:0% rules in place obviously and these rules 10:48:39.900 --> 10:48:42.766 align:start position:0% rules in place obviously and these rules have<10:48:40.080> been<10:48:40.200> added<10:48:40.560> to<10:48:40.740> and<10:48:40.980> amended<10:48:41.520> if<10:48:42.180> you<10:48:42.416> if 10:48:42.766 --> 10:48:42.776 align:start position:0% have been added to and amended if you if 10:48:42.776 --> 10:48:44.690 align:start position:0% have been added to and amended if you if you've<10:48:42.960> got<10:48:43.080> the<10:48:43.256> time<10:48:43.560> and<10:48:44.160> the<10:48:44.340> inclination 10:48:44.690 --> 10:48:44.700 align:start position:0% you've got the time and the inclination 10:48:44.700 --> 10:48:47.086 align:start position:0% you've got the time and the inclination to<10:48:44.880> read<10:48:45.060> through<10:48:45.180> the<10:48:45.416> rfcs<10:48:46.200> and<10:48:46.860> certainly 10:48:47.086 --> 10:48:47.096 align:start position:0% to read through the rfcs and certainly 10:48:47.096 --> 10:48:49.906 align:start position:0% to read through the rfcs and certainly when<10:48:47.276> we<10:48:47.460> come<10:48:47.640> to<10:48:47.880> see<10:48:48.180> Name<10:48:48.480> Records 10:48:49.906 --> 10:48:49.916 align:start position:0% when we come to see Name Records 10:48:49.916 --> 10:48:54.050 align:start position:0% when we come to see Name Records conical<10:48:50.700> names<10:48:51.000> I'm<10:48:51.480> not<10:48:51.596> saying<10:48:51.840> that<10:48:51.960> twice 10:48:54.050 --> 10:48:54.060 align:start position:0% conical names I'm not saying that twice 10:48:54.060 --> 10:48:57.830 align:start position:0% conical names I'm not saying that twice they<10:48:54.596> had<10:48:54.840> to<10:48:54.960> issue<10:48:55.380> an<10:48:55.916> update<10:48:56.220> on<10:48:57.180> the<10:48:57.300> RFC 10:48:57.830 --> 10:48:57.840 align:start position:0% they had to issue an update on the RFC 10:48:57.840 --> 10:48:59.390 align:start position:0% they had to issue an update on the RFC because<10:48:58.140> people<10:48:58.500> were<10:48:58.860> getting<10:48:59.096> a<10:48:59.276> bit 10:48:59.390 --> 10:48:59.400 align:start position:0% because people were getting a bit 10:48:59.400 --> 10:49:01.850 align:start position:0% because people were getting a bit confused<10:48:59.820> about<10:49:00.000> what<10:49:00.416> it<10:49:00.596> what<10:49:00.840> it<10:49:01.020> did<10:49:01.200> and 10:49:01.850 --> 10:49:01.860 align:start position:0% confused about what it what it did and 10:49:01.860 --> 10:49:03.290 align:start position:0% confused about what it what it did and this<10:49:02.040> is<10:49:02.096> one<10:49:02.276> of<10:49:02.400> the<10:49:02.460> things<10:49:02.520> about<10:49:02.700> when<10:49:03.060> you 10:49:03.290 --> 10:49:03.300 align:start position:0% this is one of the things about when you 10:49:03.300 --> 10:49:05.390 align:start position:0% this is one of the things about when you when<10:49:04.020> you<10:49:04.256> create<10:49:04.436> something<10:49:04.740> and<10:49:05.040> you<10:49:05.220> write 10:49:05.390 --> 10:49:05.400 align:start position:0% when you create something and you write 10:49:05.400 --> 10:49:06.890 align:start position:0% when you create something and you write the<10:49:05.580> rules 10:49:06.890 --> 10:49:06.900 align:start position:0% the rules 10:49:06.900 --> 10:49:09.350 align:start position:0% the rules of<10:49:07.020> the<10:49:07.320> documentation<10:49:07.916> you 10:49:09.350 --> 10:49:09.360 align:start position:0% of the documentation you 10:49:09.360 --> 10:49:11.030 align:start position:0% of the documentation you you<10:49:09.660> presume<10:49:10.256> people<10:49:10.436> already<10:49:10.740> understand 10:49:11.030 --> 10:49:11.040 align:start position:0% you presume people already understand 10:49:11.040 --> 10:49:13.070 align:start position:0% you presume people already understand stuff<10:49:11.520> because<10:49:11.640> it's<10:49:11.820> in<10:49:12.060> your<10:49:12.240> head<10:49:12.416> this<10:49:12.900> is 10:49:13.070 --> 10:49:13.080 align:start position:0% stuff because it's in your head this is 10:49:13.080 --> 10:49:14.870 align:start position:0% stuff because it's in your head this is why<10:49:13.200> it's<10:49:13.380> handy<10:49:13.620> to<10:49:13.740> get<10:49:13.860> other<10:49:13.980> people<10:49:14.276> to 10:49:14.870 --> 10:49:14.880 align:start position:0% why it's handy to get other people to 10:49:14.880 --> 10:49:16.310 align:start position:0% why it's handy to get other people to write<10:49:15.120> the<10:49:15.300> documentation<10:49:15.776> and<10:49:16.020> then<10:49:16.140> you 10:49:16.310 --> 10:49:16.320 align:start position:0% write the documentation and then you 10:49:16.320 --> 10:49:17.690 align:start position:0% write the documentation and then you read<10:49:16.560> it 10:49:17.690 --> 10:49:17.700 align:start position:0% read it 10:49:17.700 --> 10:49:18.950 align:start position:0% read it and<10:49:18.120> I'm<10:49:18.360> saying<10:49:18.776> that<10:49:18.840> because 10:49:18.950 --> 10:49:18.960 align:start position:0% and I'm saying that because 10:49:18.960 --> 10:49:21.110 align:start position:0% and I'm saying that because documentation<10:49:19.620> is<10:49:19.800> included<10:49:20.220> in<10:49:20.520> the<10:49:20.700> network 10:49:21.110 --> 10:49:21.120 align:start position:0% documentation is included in the network 10:49:21.120 --> 10:49:22.610 align:start position:0% documentation is included in the network plus<10:49:21.480> the<10:49:21.720> exam 10:49:22.610 --> 10:49:22.620 align:start position:0% plus the exam 10:49:22.620 --> 10:49:25.310 align:start position:0% plus the exam so<10:49:23.400> the<10:49:23.640> namespace<10:49:24.120> is<10:49:24.416> a<10:49:24.596> hierarchically 10:49:25.310 --> 10:49:25.320 align:start position:0% so the namespace is a hierarchically 10:49:25.320 --> 10:49:27.610 align:start position:0% so the namespace is a hierarchically there's<10:49:26.160> too<10:49:26.460> many<10:49:26.580> long<10:49:27.000> words<10:49:27.180> today 10:49:27.610 --> 10:49:27.620 align:start position:0% there's too many long words today 10:49:27.620 --> 10:49:30.586 align:start position:0% there's too many long words today structured<10:49:28.620> and<10:49:28.980> has<10:49:29.096> rules<10:49:29.520> to<10:49:29.700> uh<10:49:30.240> that<10:49:30.416> let 10:49:30.586 --> 10:49:30.596 align:start position:0% structured and has rules to uh that let 10:49:30.596 --> 10:49:34.310 align:start position:0% structured and has rules to uh that let the<10:49:30.720> namespace<10:49:31.080> be<10:49:31.320> divided<10:49:31.740> into<10:49:31.916> subsets 10:49:34.310 --> 10:49:34.320 align:start position:0% the namespace be divided into subsets 10:49:34.320 --> 10:49:36.710 align:start position:0% the namespace be divided into subsets so<10:49:34.680> in<10:49:34.800> the<10:49:34.980> land<10:49:35.160> uh<10:49:35.520> the<10:49:35.820> domain<10:49:36.180> is<10:49:36.416> a<10:49:36.596> sub 10:49:36.710 --> 10:49:36.720 align:start position:0% so in the land uh the domain is a sub 10:49:36.720 --> 10:49:38.450 align:start position:0% so in the land uh the domain is a sub Network<10:49:36.960> consisting<10:49:37.500> of<10:49:37.680> a<10:49:37.800> group<10:49:37.916> of<10:49:38.096> clients 10:49:38.450 --> 10:49:38.460 align:start position:0% Network consisting of a group of clients 10:49:38.460 --> 10:49:41.150 align:start position:0% Network consisting of a group of clients and<10:49:38.580> servers<10:49:39.060> I'm<10:49:39.596> not<10:49:39.776> talking<10:49:39.900> about<10:49:40.140> the<10:49:41.096> um 10:49:41.150 --> 10:49:41.160 align:start position:0% and servers I'm not talking about the um 10:49:41.160 --> 10:49:42.530 align:start position:0% and servers I'm not talking about the um your<10:49:41.460> internal 10:49:42.530 --> 10:49:42.540 align:start position:0% your internal 10:49:42.540 --> 10:49:46.130 align:start position:0% your internal um<10:49:42.596> intranet<10:49:43.200> for<10:49:43.320> example 10:49:46.130 --> 10:49:46.140 align:start position:0% 10:49:46.140 --> 10:49:47.810 align:start position:0% I'm<10:49:46.500> just<10:49:46.620> talking<10:49:46.800> about<10:49:47.040> the<10:49:47.276> day-to-day 10:49:47.810 --> 10:49:47.820 align:start position:0% I'm just talking about the day-to-day 10:49:47.820 --> 10:49:50.030 align:start position:0% I'm just talking about the day-to-day lands<10:49:48.240> of<10:49:48.360> IP<10:49:48.720> addresses<10:49:49.140> you<10:49:49.620> could<10:49:49.740> have<10:49:49.860> the 10:49:50.030 --> 10:49:50.040 align:start position:0% lands of IP addresses you could have the 10:49:50.040 --> 10:49:52.130 align:start position:0% lands of IP addresses you could have the intranet<10:49:50.700> or<10:49:51.180> obviously 10:49:52.130 --> 10:49:52.140 align:start position:0% intranet or obviously 10:49:52.140 --> 10:49:55.070 align:start position:0% intranet or obviously um<10:49:52.200> Microsoft<10:49:52.916> also<10:49:53.820> has<10:49:54.416> a<10:49:54.596> naming<10:49:54.900> system 10:49:55.070 --> 10:49:55.080 align:start position:0% um Microsoft also has a naming system 10:49:55.080 --> 10:49:57.650 align:start position:0% um Microsoft also has a naming system the<10:49:55.436> active<10:49:55.680> directory<10:49:56.220> so<10:49:56.580> we're<10:49:57.540> not 10:49:57.650 --> 10:49:57.660 align:start position:0% the active directory so we're not 10:49:57.660 --> 10:50:01.010 align:start position:0% the active directory so we're not talking<10:49:57.840> about<10:49:58.080> that 10:50:01.010 --> 10:50:01.020 align:start position:0% 10:50:01.020 --> 10:50:03.350 align:start position:0% so<10:50:01.740> Internet<10:50:01.980> domain<10:50:02.580> is<10:50:02.756> a<10:50:02.880> descriptor<10:50:03.240> of 10:50:03.350 --> 10:50:03.360 align:start position:0% so Internet domain is a descriptor of 10:50:03.360 --> 10:50:06.350 align:start position:0% so Internet domain is a descriptor of The<10:50:03.596> Logical<10:50:04.020> grouping<10:50:04.436> of<10:50:04.620> names<10:50:05.060> and<10:50:06.060> it 10:50:06.350 --> 10:50:06.360 align:start position:0% The Logical grouping of names and it 10:50:06.360 --> 10:50:08.330 align:start position:0% The Logical grouping of names and it indicates<10:50:07.140> whether<10:50:07.436> the<10:50:07.620> names<10:50:07.800> belong<10:50:08.220> to 10:50:08.330 --> 10:50:08.340 align:start position:0% indicates whether the names belong to 10:50:08.340 --> 10:50:11.530 align:start position:0% indicates whether the names belong to the<10:50:08.520> following<10:50:08.820> commercial<10:50:09.480> entities<10:50:10.340> and 10:50:11.530 --> 10:50:11.540 align:start position:0% the following commercial entities and 10:50:11.540 --> 10:50:13.370 align:start position:0% the following commercial entities and non-non-profits<10:50:12.540> I'm<10:50:12.776> not<10:50:12.900> sure<10:50:13.020> what<10:50:13.256> the 10:50:13.370 --> 10:50:13.380 align:start position:0% non-non-profits I'm not sure what the 10:50:13.380 --> 10:50:16.190 align:start position:0% non-non-profits I'm not sure what the non-profit<10:50:14.060> is.org<10:50:15.060> isn't<10:50:15.360> it 10:50:16.190 --> 10:50:16.200 align:start position:0% non-profit is.org isn't it 10:50:16.200 --> 10:50:18.290 align:start position:0% non-profit is.org isn't it which<10:50:16.680> isn't<10:50:17.096> isn't<10:50:17.640> really<10:50:17.820> the<10:50:18.120> case 10:50:18.290 --> 10:50:18.300 align:start position:0% which isn't isn't really the case 10:50:18.300 --> 10:50:19.610 align:start position:0% which isn't isn't really the case because 10:50:19.610 --> 10:50:19.620 align:start position:0% because 10:50:19.620 --> 10:50:21.710 align:start position:0% because um I've<10:50:20.276> got<10:50:20.400> a<10:50:20.520> DOT<10:50:20.820> org<10:50:21.060> website<10:50:21.300> so<10:50:21.540> it's 10:50:21.710 --> 10:50:21.720 align:start position:0% um I've got a DOT org website so it's 10:50:21.720 --> 10:50:23.210 align:start position:0% um I've got a DOT org website so it's not<10:50:21.900> protected<10:50:22.320> you<10:50:22.560> don't<10:50:22.740> have<10:50:22.860> to<10:50:22.980> be<10:50:23.040> a 10:50:23.210 --> 10:50:23.220 align:start position:0% not protected you don't have to be a 10:50:23.220 --> 10:50:26.390 align:start position:0% not protected you don't have to be a registered<10:50:23.700> uh<10:50:24.480> charity 10:50:26.390 --> 10:50:26.400 align:start position:0% registered uh charity 10:50:26.400 --> 10:50:30.406 align:start position:0% registered uh charity educational<10:50:27.360> is<10:50:27.900> dot<10:50:28.620> uh<10:50:29.220> Ed<10:50:29.580> I<10:50:30.120> don't<10:50:30.300> think 10:50:30.406 --> 10:50:30.416 align:start position:0% educational is dot uh Ed I don't think 10:50:30.416 --> 10:50:34.670 align:start position:0% educational is dot uh Ed I don't think it's<10:50:30.480> dot<10:50:30.776> EU<10:50:31.020> it's<10:50:31.256> dot<10:50:31.800> e<10:50:32.460> d<10:50:32.880> u<10:50:33.180> now<10:50:33.840> I<10:50:34.320> you 10:50:34.670 --> 10:50:34.680 align:start position:0% it's dot EU it's dot e d u now I you 10:50:34.680 --> 10:50:36.110 align:start position:0% it's dot EU it's dot e d u now I you can't<10:50:34.860> get<10:50:35.096> these<10:50:35.340> as<10:50:35.580> far<10:50:35.700> as<10:50:35.820> I<10:50:36.000> know 10:50:36.110 --> 10:50:36.120 align:start position:0% can't get these as far as I know 10:50:36.120 --> 10:50:38.926 align:start position:0% can't get these as far as I know certainly<10:50:36.540> not<10:50:36.660> for<10:50:36.840> USA<10:50:37.380> you<10:50:37.980> have<10:50:38.096> to<10:50:38.220> be<10:50:38.936> um 10:50:38.926 --> 10:50:38.936 align:start position:0% certainly not for USA you have to be um 10:50:38.936 --> 10:50:41.450 align:start position:0% certainly not for USA you have to be um a<10:50:39.660> uni 10:50:41.450 --> 10:50:41.460 align:start position:0% a uni 10:50:41.460 --> 10:50:44.266 align:start position:0% a uni College<10:50:42.120> something<10:50:42.540> like<10:50:42.840> that<10:50:43.080> so<10:50:43.740> I<10:50:43.916> presume 10:50:44.266 --> 10:50:44.276 align:start position:0% College something like that so I presume 10:50:44.276 --> 10:50:45.050 align:start position:0% College something like that so I presume you<10:50:44.340> have<10:50:44.460> to<10:50:44.580> have<10:50:44.640> some<10:50:44.820> sort<10:50:44.936> of 10:50:45.050 --> 10:50:45.060 align:start position:0% you have to have some sort of 10:50:45.060 --> 10:50:47.870 align:start position:0% you have to have some sort of documentation<10:50:45.596> or<10:50:45.900> number 10:50:47.870 --> 10:50:47.880 align:start position:0% documentation or number 10:50:47.880 --> 10:50:51.230 align:start position:0% documentation or number government<10:50:48.240> agencies.gov 10:50:51.230 --> 10:50:51.240 align:start position:0% government agencies.gov 10:50:51.240 --> 10:50:53.870 align:start position:0% government agencies.gov and<10:50:51.720> so<10:50:51.900> on 10:50:53.870 --> 10:50:53.880 align:start position:0% and so on 10:50:53.880 --> 10:50:56.210 align:start position:0% and so on you<10:50:54.416> can<10:50:54.540> subdivide<10:50:55.200> the<10:50:55.320> domain<10:50:55.620> into<10:50:55.800> groups 10:50:56.210 --> 10:50:56.220 align:start position:0% you can subdivide the domain into groups 10:50:56.220 --> 10:50:58.370 align:start position:0% you can subdivide the domain into groups called<10:50:56.460> subdomain 10:50:58.370 --> 10:50:58.380 align:start position:0% called subdomain 10:50:58.380 --> 10:51:01.906 align:start position:0% called subdomain so<10:50:59.040> the<10:50:59.880> DNS<10:51:00.300> domain<10:51:00.660> can<10:51:00.840> also<10:51:01.080> contain<10:51:01.380> hosts 10:51:01.906 --> 10:51:01.916 align:start position:0% so the DNS domain can also contain hosts 10:51:01.916 --> 10:51:05.450 align:start position:0% so the DNS domain can also contain hosts these<10:51:02.880> refer<10:51:03.120> to<10:51:03.240> computers<10:51:03.840> and<10:51:04.020> services<10:51:04.460> so 10:51:05.450 --> 10:51:05.460 align:start position:0% these refer to computers and services so 10:51:05.460 --> 10:51:06.350 align:start position:0% these refer to computers and services so we've<10:51:05.580> got<10:51:05.700> an<10:51:05.820> example<10:51:06.120> here 10:51:06.350 --> 10:51:06.360 align:start position:0% we've got an example here 10:51:06.360 --> 10:51:11.030 align:start position:0% we've got an example here training.samplecompany.com 10:51:11.030 --> 10:51:11.040 align:start position:0% 10:51:11.040 --> 10:51:14.570 align:start position:0% so<10:51:11.640> this<10:51:11.936> is<10:51:12.120> the<10:51:12.416> first<10:51:12.660> obviously<10:51:13.256> the<10:51:13.860> top 10:51:14.570 --> 10:51:14.580 align:start position:0% so this is the first obviously the top 10:51:14.580 --> 10:51:16.550 align:start position:0% so this is the first obviously the top top<10:51:14.880> level<10:51:15.120> domain<10:51:15.660> which<10:51:15.900> we<10:51:16.200> talk<10:51:16.380> about 10:51:16.550 --> 10:51:16.560 align:start position:0% top level domain which we talk about 10:51:16.560 --> 10:51:20.450 align:start position:0% top level domain which we talk about then<10:51:17.340> somebody's<10:51:18.200> registered<10:51:19.200> this 10:51:20.450 --> 10:51:20.460 align:start position:0% then somebody's registered this 10:51:20.460 --> 10:51:22.850 align:start position:0% then somebody's registered this but<10:51:20.880> then<10:51:21.000> when<10:51:21.180> you<10:51:21.360> go<10:51:21.596> into<10:51:21.720> your 10:51:22.850 --> 10:51:22.860 align:start position:0% but then when you go into your 10:51:22.860 --> 10:51:25.550 align:start position:0% but then when you go into your admin<10:51:23.580> panel 10:51:25.550 --> 10:51:25.560 align:start position:0% admin panel 10:51:25.560 --> 10:51:29.030 align:start position:0% admin panel you<10:51:26.276> can<10:51:26.400> add<10:51:26.880> these<10:51:27.660> sub<10:51:28.020> domains<10:51:28.560> here<10:51:28.740> for 10:51:29.030 --> 10:51:29.040 align:start position:0% you can add these sub domains here for 10:51:29.040 --> 10:51:32.266 align:start position:0% you can add these sub domains here for example<10:51:29.276> my 10:51:32.266 --> 10:51:32.276 align:start position:0% 10:51:32.276 --> 10:51:35.330 align:start position:0% I<10:51:32.700> think<10:51:32.936> it's<10:51:33.120> called<10:51:33.416> rack<10:51:33.960> start 10:51:35.330 --> 10:51:35.340 align:start position:0% I think it's called rack start 10:51:35.340 --> 10:51:40.490 align:start position:0% I think it's called rack start how<10:51:36.300> to 10:51:40.490 --> 10:51:40.500 align:start position:0% 10:51:40.500 --> 10:51:42.650 align:start position:0% network.com<10:51:41.460> I've<10:51:41.820> got<10:51:42.000> the<10:51:42.180> same<10:51:42.300> sort<10:51:42.540> of 10:51:42.650 --> 10:51:42.660 align:start position:0% network.com I've got the same sort of 10:51:42.660 --> 10:51:46.490 align:start position:0% network.com I've got the same sort of thing<10:51:42.840> I<10:51:43.800> created<10:51:44.276> this<10:51:44.580> subdomain<10:51:45.660> which<10:51:46.320> has 10:51:46.490 --> 10:51:46.500 align:start position:0% thing I created this subdomain which has 10:51:46.500 --> 10:51:49.246 align:start position:0% thing I created this subdomain which has got<10:51:46.680> its<10:51:47.096> own<10:51:47.340> IP<10:51:48.180> address<10:51:48.360> at 10:51:49.246 --> 10:51:49.256 align:start position:0% got its own IP address at 10:51:49.256 --> 10:51:52.670 align:start position:0% got its own IP address at howtonnetwork.com<10:51:50.160> is<10:51:50.580> sitting<10:51:50.936> somewhere 10:51:52.670 --> 10:51:52.680 align:start position:0% howtonnetwork.com is sitting somewhere 10:51:52.680 --> 10:51:53.330 align:start position:0% howtonnetwork.com is sitting somewhere um 10:51:53.330 --> 10:51:53.340 align:start position:0% um 10:51:53.340 --> 10:51:55.490 align:start position:0% um actually<10:51:53.820> know<10:51:54.180> where<10:51:54.416> it<10:51:54.540> is<10:51:54.660> it's<10:51:54.960> sitting 10:51:55.490 --> 10:51:55.500 align:start position:0% actually know where it is it's sitting 10:51:55.500 --> 10:51:59.086 align:start position:0% actually know where it is it's sitting on<10:51:55.680> a<10:51:55.800> server<10:51:56.096> say<10:51:56.880> say<10:51:57.180> no 10:51:59.086 --> 10:51:59.096 align:start position:0% on a server say say no 10:51:59.096 --> 10:52:03.110 align:start position:0% on a server say say no I<10:51:59.520> IO<10:52:00.000> the<10:52:00.660> the<10:52:01.860> um<10:52:01.860> racks<10:52:02.460> are<10:52:02.700> sitting 10:52:03.110 --> 10:52:03.120 align:start position:0% I IO the the um racks are sitting 10:52:03.120 --> 10:52:05.330 align:start position:0% I IO the the um racks are sitting somewhere<10:52:03.540> else<10:52:03.720> because<10:52:04.080> I've<10:52:04.680> used<10:52:04.916> DNS 10:52:05.330 --> 10:52:05.340 align:start position:0% somewhere else because I've used DNS 10:52:05.340 --> 10:52:10.370 align:start position:0% somewhere else because I've used DNS records<10:52:05.936> that<10:52:06.660> sit<10:52:06.960> in<10:52:07.200> in<10:52:07.860> um<10:52:07.860> oh 10:52:10.370 --> 10:52:10.380 align:start position:0% 10:52:10.380 --> 10:52:13.370 align:start position:0% I<10:52:10.620> actually<10:52:10.916> remember<10:52:11.220> where<10:52:11.520> it<10:52:11.700> is 10:52:13.370 --> 10:52:13.380 align:start position:0% I actually remember where it is 10:52:13.380 --> 10:52:15.470 align:start position:0% I actually remember where it is up<10:52:13.916> at<10:52:14.096> Nevada<10:52:14.400> just<10:52:14.880> so<10:52:15.000> you<10:52:15.120> get<10:52:15.240> the<10:52:15.300> point 10:52:15.470 --> 10:52:15.480 align:start position:0% up at Nevada just so you get the point 10:52:15.480 --> 10:52:18.350 align:start position:0% up at Nevada just so you get the point anyway 10:52:18.350 --> 10:52:18.360 align:start position:0% 10:52:18.360 --> 10:52:21.890 align:start position:0% so<10:52:19.220> samplecomedy.com<10:52:20.300> the.com<10:52:21.300> is<10:52:21.540> known<10:52:21.720> as 10:52:21.890 --> 10:52:21.900 align:start position:0% so samplecomedy.com the.com is known as 10:52:21.900 --> 10:52:24.530 align:start position:0% so samplecomedy.com the.com is known as the<10:52:22.080> TLD<10:52:22.436> top<10:52:22.860> level<10:52:23.040> domain 10:52:24.530 --> 10:52:24.540 align:start position:0% the TLD top level domain 10:52:24.540 --> 10:52:26.330 align:start position:0% the TLD top level domain okay<10:52:24.840> so<10:52:25.140> you<10:52:25.436> could<10:52:25.500> be<10:52:25.620> asked<10:52:25.800> this<10:52:25.980> in<10:52:26.160> the 10:52:26.330 --> 10:52:26.340 align:start position:0% okay so you could be asked this in the 10:52:26.340 --> 10:52:29.390 align:start position:0% okay so you could be asked this in the exam<10:52:26.520> this<10:52:26.640> is<10:52:26.756> ISA<10:52:27.300> the<10:52:28.200> fqdn<10:52:28.916> the<10:52:29.160> fully 10:52:29.390 --> 10:52:29.400 align:start position:0% exam this is ISA the fqdn the fully 10:52:29.400 --> 10:52:31.310 align:start position:0% exam this is ISA the fqdn the fully qualified<10:52:29.700> domain<10:52:30.120> name<10:52:30.300> is<10:52:30.720> a<10:52:30.900> complete 10:52:31.310 --> 10:52:31.320 align:start position:0% qualified domain name is a complete 10:52:31.320 --> 10:52:33.350 align:start position:0% qualified domain name is a complete domain<10:52:31.800> name<10:52:31.980> for<10:52:32.220> a<10:52:32.340> specific<10:52:32.640> computer<10:52:32.936> or 10:52:33.350 --> 10:52:33.360 align:start position:0% domain name for a specific computer or 10:52:33.360 --> 10:52:36.470 align:start position:0% domain name for a specific computer or host<10:52:33.596> so<10:52:34.436> it's<10:52:34.620> got<10:52:34.800> the<10:52:34.916> host<10:52:35.096> name<10:52:35.460> and<10:52:36.300> the 10:52:36.470 --> 10:52:36.480 align:start position:0% host so it's got the host name and the 10:52:36.480 --> 10:52:38.086 align:start position:0% host so it's got the host name and the domain<10:52:36.776> name 10:52:38.086 --> 10:52:38.096 align:start position:0% domain name 10:52:38.096 --> 10:52:42.290 align:start position:0% domain name so<10:52:38.700> for<10:52:39.120> the<10:52:39.800> fqdn<10:52:40.800> for<10:52:41.340> a<10:52:41.460> hypothetical<10:52:41.936> main 10:52:42.290 --> 10:52:42.300 align:start position:0% so for the fqdn for a hypothetical main 10:52:42.300 --> 10:52:45.830 align:start position:0% so for the fqdn for a hypothetical main mail<10:52:43.020> server<10:52:43.500> might<10:52:44.040> be<10:52:44.220> mail<10:52:44.520> one<10:52:44.820> and<10:52:45.596> you 10:52:45.830 --> 10:52:45.840 align:start position:0% mail server might be mail one and you 10:52:45.840 --> 10:52:47.030 align:start position:0% mail server might be mail one and you probably<10:52:45.960> have<10:52:46.140> this<10:52:46.320> if<10:52:46.500> you're<10:52:46.680> in<10:52:46.860> a 10:52:47.030 --> 10:52:47.040 align:start position:0% probably have this if you're in a 10:52:47.040 --> 10:52:48.470 align:start position:0% probably have this if you're in a reasonably<10:52:47.400> sized<10:52:47.820> company<10:52:47.936> that's<10:52:48.180> got<10:52:48.360> a 10:52:48.470 --> 10:52:48.480 align:start position:0% reasonably sized company that's got a 10:52:48.480 --> 10:52:50.030 align:start position:0% reasonably sized company that's got a dedicated<10:52:48.900> Mouse<10:52:49.256> server<10:52:49.680> so<10:52:49.860> you're 10:52:50.030 --> 10:52:50.040 align:start position:0% dedicated Mouse server so you're 10:52:50.040 --> 10:52:52.130 align:start position:0% dedicated Mouse server so you're handling<10:52:50.700> all<10:52:50.936> your<10:52:51.120> mail 10:52:52.130 --> 10:52:52.140 align:start position:0% handling all your mail 10:52:52.140 --> 10:52:55.970 align:start position:0% handling all your mail most<10:52:52.916> of<10:52:53.160> these<10:52:53.580> services<10:52:54.120> are<10:52:54.776> named<10:52:55.380> you 10:52:55.970 --> 10:52:55.980 align:start position:0% most of these services are named you 10:52:55.980 --> 10:52:58.970 align:start position:0% most of these services are named you know<10:52:56.096> mail<10:52:56.276> one<10:52:56.580> mail<10:52:56.880> two<10:52:57.180> whatever<10:52:57.840> and<10:52:58.800> then 10:52:58.970 --> 10:52:58.980 align:start position:0% know mail one mail two whatever and then 10:52:58.980 --> 10:53:01.426 align:start position:0% know mail one mail two whatever and then your<10:52:59.340> company<10:52:59.580> name<10:52:59.936> so<10:53:00.480> you're<10:53:00.660> managing<10:53:01.140> all 10:53:01.426 --> 10:53:01.436 align:start position:0% your company name so you're managing all 10:53:01.436 --> 10:53:02.690 align:start position:0% your company name so you're managing all of<10:53:01.560> your 10:53:02.690 --> 10:53:02.700 align:start position:0% of your 10:53:02.700 --> 10:53:04.906 align:start position:0% of your um<10:53:02.756> incoming<10:53:03.300> and<10:53:03.416> outgoing<10:53:03.840> mail<10:53:04.080> which<10:53:04.740> is 10:53:04.906 --> 10:53:04.916 align:start position:0% um incoming and outgoing mail which is 10:53:04.916 --> 10:53:06.050 align:start position:0% um incoming and outgoing mail which is probably 10:53:06.050 --> 10:53:06.060 align:start position:0% probably 10:53:06.060 --> 10:53:07.850 align:start position:0% probably um<10:53:06.120> a<10:53:06.596> good<10:53:06.660> idea 10:53:07.850 --> 10:53:07.860 align:start position:0% um a good idea 10:53:07.860 --> 10:53:11.030 align:start position:0% um a good idea so<10:53:08.160> you<10:53:08.340> can<10:53:08.460> Blacklist<10:53:08.880> and<10:53:09.300> and<10:53:09.860> comply<10:53:10.860> with 10:53:11.030 --> 10:53:11.040 align:start position:0% so you can Blacklist and and comply with 10:53:11.040 --> 10:53:14.630 align:start position:0% so you can Blacklist and and comply with other<10:53:11.340> legal<10:53:11.936> requirements 10:53:14.630 --> 10:53:14.640 align:start position:0% 10:53:14.640 --> 10:53:18.050 align:start position:0% so<10:53:15.360> mail<10:53:15.840> one<10:53:16.080> is<10:53:16.320> a<10:53:16.560> host<10:53:16.740> obviously<10:53:17.520> you<10:53:17.880> can 10:53:18.050 --> 10:53:18.060 align:start position:0% so mail one is a host obviously you can 10:53:18.060 --> 10:53:20.630 align:start position:0% so mail one is a host obviously you can use<10:53:18.540> more<10:53:18.776> than<10:53:18.960> one<10:53:19.200> server<10:53:19.620> you<10:53:20.400> can<10:53:20.520> use 10:53:20.630 --> 10:53:20.640 align:start position:0% use more than one server you can use 10:53:20.640 --> 10:53:23.950 align:start position:0% use more than one server you can use virtualization<10:53:21.360> whatever<10:53:21.660> you<10:53:21.960> want<10:53:22.200> but<10:53:22.860> um 10:53:23.950 --> 10:53:23.960 align:start position:0% virtualization whatever you want but um 10:53:23.960 --> 10:53:27.370 align:start position:0% virtualization whatever you want but um hypothetically<10:53:24.960> speaking<10:53:25.320> it's<10:53:25.500> a<10:53:25.680> a<10:53:25.916> server 10:53:27.370 --> 10:53:27.380 align:start position:0% hypothetically speaking it's a a server 10:53:27.380 --> 10:53:32.150 align:start position:0% hypothetically speaking it's a a server dot<10:53:28.380> com<10:53:28.380> is<10:53:28.620> the<10:53:28.800> TRD<10:53:29.160> as<10:53:29.400> we<10:53:29.520> mentioned 10:53:32.150 --> 10:53:32.160 align:start position:0% 10:53:32.160 --> 10:53:35.266 align:start position:0% so<10:53:32.640> DNS<10:53:33.120> root<10:53:33.540> servers<10:53:33.900> these<10:53:34.560> are<10:53:34.916> the 10:53:35.266 --> 10:53:35.276 align:start position:0% so DNS root servers these are the 10:53:35.276 --> 10:53:37.730 align:start position:0% so DNS root servers these are the contain<10:53:35.880> the<10:53:36.180> top<10:53:36.416> level<10:53:36.596> domain<10:53:37.140> registry 10:53:37.730 --> 10:53:37.740 align:start position:0% contain the top level domain registry 10:53:37.740 --> 10:53:40.730 align:start position:0% contain the top level domain registry that<10:53:38.400> maintain<10:53:38.700> the<10:53:38.880> global<10:53:39.240> domains<10:53:39.776> so<10:53:40.436> at 10:53:40.730 --> 10:53:40.740 align:start position:0% that maintain the global domains so at 10:53:40.740 --> 10:53:43.426 align:start position:0% that maintain the global domains so at some<10:53:40.916> point<10:53:41.040> if<10:53:41.276> you<10:53:41.460> register<10:53:41.880> a<10:53:42.540> brand<10:53:43.320> new 10:53:43.426 --> 10:53:43.436 align:start position:0% some point if you register a brand new 10:53:43.436 --> 10:53:44.870 align:start position:0% some point if you register a brand new domain<10:53:43.916> name 10:53:44.870 --> 10:53:44.880 align:start position:0% domain name 10:53:44.880 --> 10:53:46.850 align:start position:0% domain name you'd<10:53:45.240> register<10:53:45.540> it<10:53:45.776> with<10:53:45.960> your 10:53:46.850 --> 10:53:46.860 align:start position:0% you'd register it with your 10:53:46.860 --> 10:53:48.470 align:start position:0% you'd register it with your um 10:53:48.470 --> 10:53:48.480 align:start position:0% um 10:53:48.480 --> 10:53:50.926 align:start position:0% um it<10:53:48.660> could<10:53:48.840> be<10:53:49.020> with<10:53:49.200> your<10:53:49.320> hosting<10:53:49.740> company 10:53:50.926 --> 10:53:50.936 align:start position:0% it could be with your hosting company 10:53:50.936 --> 10:53:53.390 align:start position:0% it could be with your hosting company I'll<10:53:51.300> just<10:53:51.480> put<10:53:51.596> HC<10:53:52.140> and<10:53:52.916> then<10:53:53.040> that 10:53:53.390 --> 10:53:53.400 align:start position:0% I'll just put HC and then that 10:53:53.400 --> 10:53:57.830 align:start position:0% I'll just put HC and then that eventually<10:53:54.180> will<10:53:54.416> get<10:53:54.596> forwarded<10:53:55.256> to<10:53:55.860> the<10:53:57.000> um 10:53:57.830 --> 10:53:57.840 align:start position:0% eventually will get forwarded to the um 10:53:57.840 --> 10:54:00.850 align:start position:0% eventually will get forwarded to the um the<10:53:58.500> TLD<10:53:58.916> and<10:53:59.640> then<10:53:59.756> that<10:53:59.936> will<10:54:00.120> be<10:54:00.240> forwarded 10:54:00.850 --> 10:54:00.860 align:start position:0% the TLD and then that will be forwarded 10:54:00.860 --> 10:54:05.450 align:start position:0% the TLD and then that will be forwarded to<10:54:02.300> non-root<10:54:03.300> service<10:54:03.480> So<10:54:04.200> eventually<10:54:04.740> your 10:54:05.450 --> 10:54:05.460 align:start position:0% to non-root service So eventually your 10:54:05.460 --> 10:54:08.266 align:start position:0% to non-root service So eventually your ISP<10:54:06.000> will<10:54:06.300> probably 10:54:08.266 --> 10:54:08.276 align:start position:0% ISP will probably 10:54:08.276 --> 10:54:11.870 align:start position:0% ISP will probably get<10:54:08.700> a<10:54:08.820> copy 10:54:11.870 --> 10:54:11.880 align:start position:0% 10:54:11.880 --> 10:54:16.010 align:start position:0% so<10:54:12.596> as<10:54:13.020> of<10:54:13.320> first<10:54:14.220> of<10:54:14.520> August<10:54:14.936> 2018<10:54:15.180> root 10:54:16.010 --> 10:54:16.020 align:start position:0% so as of first of August 2018 root 10:54:16.020 --> 10:54:19.790 align:start position:0% so as of first of August 2018 root server<10:54:16.320> consists<10:54:16.680> of<10:54:16.936> 933<10:54:17.936> instances<10:54:18.800> these 10:54:19.790 --> 10:54:19.800 align:start position:0% server consists of 933 instances these 10:54:19.800 --> 10:54:21.470 align:start position:0% server consists of 933 instances these are<10:54:19.916> operated<10:54:20.276> by<10:54:20.520> 12<10:54:20.756> independent<10:54:21.360> route 10:54:21.470 --> 10:54:21.480 align:start position:0% are operated by 12 independent route 10:54:21.480 --> 10:54:23.030 align:start position:0% are operated by 12 independent route servers<10:54:22.020> if<10:54:22.320> you're<10:54:22.500> interested<10:54:22.800> in<10:54:22.860> more 10:54:23.030 --> 10:54:23.040 align:start position:0% servers if you're interested in more 10:54:23.040 --> 10:54:25.030 align:start position:0% servers if you're interested in more information<10:54:23.276> you<10:54:23.820> can<10:54:23.880> go<10:54:24.000> to<10:54:24.120> root 10:54:25.030 --> 10:54:25.040 align:start position:0% information you can go to root 10:54:25.040 --> 10:54:27.230 align:start position:0% information you can go to root service.org<10:54:26.040> and<10:54:26.460> have<10:54:26.640> a<10:54:26.820> read<10:54:26.936> up<10:54:27.120> and 10:54:27.230 --> 10:54:27.240 align:start position:0% service.org and have a read up and 10:54:27.240 --> 10:54:28.906 align:start position:0% service.org and have a read up and they've<10:54:27.416> got<10:54:27.480> some<10:54:27.596> maps<10:54:27.960> on<10:54:28.080> there<10:54:28.320> of<10:54:28.680> where 10:54:28.906 --> 10:54:28.916 align:start position:0% they've got some maps on there of where 10:54:28.916 --> 10:54:31.970 align:start position:0% they've got some maps on there of where all<10:54:29.160> these<10:54:29.276> root<10:54:29.520> servers<10:54:29.820> are 10:54:31.970 --> 10:54:31.980 align:start position:0% all these root servers are 10:54:31.980 --> 10:54:36.490 align:start position:0% all these root servers are some<10:54:32.936> examples<10:54:33.300> of<10:54:33.916> globaldomainsr.com<10:54:34.916> or 10:54:36.490 --> 10:54:36.500 align:start position:0% some examples of globaldomainsr.com or 10:54:36.500 --> 10:54:40.550 align:start position:0% some examples of globaldomainsr.com or netgov.edu<10:54:37.500> country<10:54:38.220> codes<10:54:38.580> US<10:54:39.120> Canada 10:54:40.550 --> 10:54:40.560 align:start position:0% netgov.edu country codes US Canada 10:54:40.560 --> 10:54:41.990 align:start position:0% netgov.edu country codes US Canada CN 10:54:41.990 --> 10:54:42.000 align:start position:0% CN 10:54:42.000 --> 10:54:46.970 align:start position:0% CN oh<10:54:42.540> I<10:54:42.776> don't<10:54:42.840> know<10:54:43.020> Denmark<10:54:44.300> France<10:54:45.300> Japan 10:54:46.970 --> 10:54:46.980 align:start position:0% oh I don't know Denmark France Japan 10:54:46.980 --> 10:54:48.586 align:start position:0% oh I don't know Denmark France Japan CN<10:54:47.460> oh<10:54:47.700> that's<10:54:47.880> going<10:54:48.000> to<10:54:48.000> annoy<10:54:48.300> me<10:54:48.360> now<10:54:48.480> I'll 10:54:48.586 --> 10:54:48.596 align:start position:0% CN oh that's going to annoy me now I'll 10:54:48.596 --> 10:54:49.550 align:start position:0% CN oh that's going to annoy me now I'll have<10:54:48.720> to<10:54:48.776> look<10:54:48.900> when<10:54:49.080> I<10:54:49.200> finish<10:54:49.320> this 10:54:49.550 --> 10:54:49.560 align:start position:0% have to look when I finish this 10:54:49.560 --> 10:54:52.610 align:start position:0% have to look when I finish this presentation<10:54:50.040> if<10:54:50.700> he<10:54:50.880> comes<10:54:51.120> to<10:54:51.180> me<10:54:51.300> I'll<10:54:51.480> say 10:54:52.610 --> 10:54:52.620 align:start position:0% presentation if he comes to me I'll say 10:54:52.620 --> 10:54:54.230 align:start position:0% presentation if he comes to me I'll say uh<10:54:52.800> you<10:54:53.096> wouldn't<10:54:53.160> be<10:54:53.340> tested<10:54:53.640> on<10:54:53.756> that<10:54:53.936> by<10:54:54.060> the 10:54:54.230 --> 10:54:54.240 align:start position:0% uh you wouldn't be tested on that by the 10:54:54.240 --> 10:54:57.350 align:start position:0% uh you wouldn't be tested on that by the way<10:54:54.360> uh<10:54:55.256> DNS<10:54:55.740> root<10:54:56.096> servers<10:54:56.520> also<10:54:57.000> known<10:54:57.120> as 10:54:57.350 --> 10:54:57.360 align:start position:0% way uh DNS root servers also known as 10:54:57.360 --> 10:54:59.690 align:start position:0% way uh DNS root servers also known as root<10:54:57.720> name<10:54:57.900> servers<10:54:58.380> if<10:54:58.560> anyone<10:54:58.860> says<10:54:59.340> that<10:54:59.460> to 10:54:59.690 --> 10:54:59.700 align:start position:0% root name servers if anyone says that to 10:54:59.700 --> 10:55:02.030 align:start position:0% root name servers if anyone says that to you<10:54:59.880> it's<10:55:00.120> perfectly<10:55:01.256> um<10:55:01.256> fine<10:55:01.500> for<10:55:01.740> them<10:55:01.860> to 10:55:02.030 --> 10:55:02.040 align:start position:0% you it's perfectly um fine for them to 10:55:02.040 --> 10:55:04.246 align:start position:0% you it's perfectly um fine for them to say<10:55:02.160> that<10:55:02.340> and<10:55:03.240> it<10:55:03.416> describes<10:55:03.840> where<10:55:04.140> the 10:55:04.246 --> 10:55:04.256 align:start position:0% say that and it describes where the 10:55:04.256 --> 10:55:06.586 align:start position:0% say that and it describes where the authoritative<10:55:04.740> did<10:55:05.220> a<10:55:05.580> service<10:55:05.936> for<10:55:06.360> the<10:55:06.480> T 10:55:06.586 --> 10:55:06.596 align:start position:0% authoritative did a service for the T 10:55:06.596 --> 10:55:10.070 align:start position:0% authoritative did a service for the T top<10:55:06.900> level<10:55:07.080> domains<10:55:07.620> are<10:55:07.740> located 10:55:10.070 --> 10:55:10.080 align:start position:0% 10:55:10.080 --> 10:55:12.230 align:start position:0% please<10:55:10.560> give<10:55:10.800> answers<10:55:11.096> for<10:55:11.340> specified<10:55:11.756> set<10:55:12.060> of 10:55:12.230 --> 10:55:12.240 align:start position:0% please give answers for specified set of 10:55:12.240 --> 10:55:14.450 align:start position:0% please give answers for specified set of zones<10:55:12.480> from<10:55:13.200> its<10:55:13.500> own<10:55:13.560> source<10:55:13.980> so<10:55:14.096> it<10:55:14.340> doesn't 10:55:14.450 --> 10:55:14.460 align:start position:0% zones from its own source so it doesn't 10:55:14.460 --> 10:55:16.850 align:start position:0% zones from its own source so it doesn't have<10:55:14.700> anywhere<10:55:15.060> else<10:55:15.240> to<10:55:15.540> go<10:55:15.720> if<10:55:16.436> there<10:55:16.560> isn't 10:55:16.850 --> 10:55:16.860 align:start position:0% have anywhere else to go if there isn't 10:55:16.860 --> 10:55:19.730 align:start position:0% have anywhere else to go if there isn't a<10:55:16.980> response<10:55:17.520> something's<10:55:18.480> gone<10:55:18.660> wrong 10:55:19.730 --> 10:55:19.740 align:start position:0% a response something's gone wrong 10:55:19.740 --> 10:55:22.690 align:start position:0% a response something's gone wrong or<10:55:20.276> the<10:55:20.460> domain<10:55:20.756> doesn't<10:55:21.000> exist 10:55:22.690 --> 10:55:22.700 align:start position:0% or the domain doesn't exist 10:55:22.700 --> 10:55:24.950 align:start position:0% or the domain doesn't exist at<10:55:23.700> the<10:55:23.820> moment<10:55:23.936> and<10:55:24.240> you'll<10:55:24.416> you'll<10:55:24.660> get<10:55:24.776> some 10:55:24.950 --> 10:55:24.960 align:start position:0% at the moment and you'll you'll get some 10:55:24.960 --> 10:55:26.510 align:start position:0% at the moment and you'll you'll get some sort<10:55:25.140> of<10:55:25.200> timeout<10:55:25.620> message<10:55:25.860> on<10:55:26.160> your<10:55:26.276> web 10:55:26.510 --> 10:55:26.520 align:start position:0% sort of timeout message on your web 10:55:26.520 --> 10:55:28.450 align:start position:0% sort of timeout message on your web browser 10:55:28.450 --> 10:55:28.460 align:start position:0% browser 10:55:28.460 --> 10:55:30.710 align:start position:0% browser non-authoritative<10:55:29.460> servers<10:55:30.120> these<10:55:30.480> provide 10:55:30.710 --> 10:55:30.720 align:start position:0% non-authoritative servers these provide 10:55:30.720 --> 10:55:33.350 align:start position:0% non-authoritative servers these provide cash<10:55:31.140> dancers<10:55:31.800> or<10:55:32.096> Cash<10:55:32.520> Aid<10:55:32.880> I<10:55:33.060> know<10:55:33.120> some 10:55:33.350 --> 10:55:33.360 align:start position:0% cash dancers or Cash Aid I know some 10:55:33.360 --> 10:55:35.086 align:start position:0% cash dancers or Cash Aid I know some people<10:55:33.480> say<10:55:33.776> that<10:55:34.500> are<10:55:34.620> obtained<10:55:34.980> from 10:55:35.086 --> 10:55:35.096 align:start position:0% people say that are obtained from 10:55:35.096 --> 10:55:36.830 align:start position:0% people say that are obtained from another<10:55:35.276> name<10:55:35.700> server 10:55:36.830 --> 10:55:36.840 align:start position:0% another name server 10:55:36.840 --> 10:55:39.950 align:start position:0% another name server so<10:55:37.320> as<10:55:37.436> I<10:55:37.620> said<10:55:37.800> you've<10:55:38.040> got<10:55:38.160> the<10:55:38.520> uh<10:55:39.240> the<10:55:39.596> root 10:55:39.950 --> 10:55:39.960 align:start position:0% so as I said you've got the uh the root 10:55:39.960 --> 10:55:43.010 align:start position:0% so as I said you've got the uh the root servers<10:55:40.860> here 10:55:43.010 --> 10:55:43.020 align:start position:0% servers here 10:55:43.020 --> 10:55:45.110 align:start position:0% servers here and<10:55:43.800> then 10:55:45.110 --> 10:55:45.120 align:start position:0% and then 10:55:45.120 --> 10:55:47.990 align:start position:0% and then other<10:55:45.720> companies<10:55:46.256> large<10:55:46.680> organizations<10:55:47.460> just 10:55:47.990 --> 10:55:48.000 align:start position:0% other companies large organizations just 10:55:48.000 --> 10:55:51.246 align:start position:0% other companies large organizations just to<10:55:48.240> save<10:55:48.416> traffic<10:55:48.776> and<10:55:49.200> time<10:55:49.436> can<10:55:50.340> query<10:55:50.700> these 10:55:51.246 --> 10:55:51.256 align:start position:0% to save traffic and time can query these 10:55:51.256 --> 10:55:55.010 align:start position:0% to save traffic and time can query these and<10:55:52.256> then<10:55:52.380> if<10:55:53.220> they<10:55:53.400> so<10:55:53.580> wish 10:55:55.010 --> 10:55:55.020 align:start position:0% and then if they so wish 10:55:55.020 --> 10:55:57.530 align:start position:0% and then if they so wish they<10:55:55.620> could<10:55:55.800> also<10:55:56.160> be<10:55:56.400> queried<10:55:56.880> by<10:55:57.360> other 10:55:57.530 --> 10:55:57.540 align:start position:0% they could also be queried by other 10:55:57.540 --> 10:56:02.926 align:start position:0% they could also be queried by other servers<10:55:58.436> and<10:55:58.800> so<10:55:58.916> on<10:55:59.160> and<10:55:59.400> so<10:55:59.580> on<10:55:59.756> and<10:55:59.936> so<10:56:00.120> on 10:56:02.926 --> 10:56:02.936 align:start position:0% 10:56:02.936 --> 10:56:06.050 align:start position:0% the<10:56:03.300> DNS<10:56:03.720> is<10:56:03.900> composed<10:56:04.380> of<10:56:04.500> a<10:56:04.680> namespace<10:56:05.160> this 10:56:06.050 --> 10:56:06.060 align:start position:0% the DNS is composed of a namespace this 10:56:06.060 --> 10:56:08.450 align:start position:0% the DNS is composed of a namespace this is<10:56:06.180> distributed<10:56:06.900> database<10:56:07.436> it<10:56:07.860> contains<10:56:08.340> the 10:56:08.450 --> 10:56:08.460 align:start position:0% is distributed database it contains the 10:56:08.460 --> 10:56:11.290 align:start position:0% is distributed database it contains the data<10:56:08.756> that<10:56:08.936> includes<10:56:09.240> the<10:56:09.416> host<10:56:09.596> names 10:56:11.290 --> 10:56:11.300 align:start position:0% data that includes the host names 10:56:11.300 --> 10:56:13.610 align:start position:0% data that includes the host names if<10:56:12.300> you<10:56:12.480> recognize<10:56:12.960> the<10:56:13.140> structure<10:56:13.436> there 10:56:13.610 --> 10:56:13.620 align:start position:0% if you recognize the structure there 10:56:13.620 --> 10:56:17.810 align:start position:0% if you recognize the structure there it's<10:56:13.800> similar<10:56:14.096> to<10:56:14.220> a<10:56:14.460> file<10:56:14.756> system<10:56:15.000> in<10:56:15.360> Unix 10:56:17.810 --> 10:56:17.820 align:start position:0% 10:56:17.820 --> 10:56:19.850 align:start position:0% the<10:56:18.360> name<10:56:18.480> server<10:56:18.960> translates<10:56:19.320> the<10:56:19.560> domain 10:56:19.850 --> 10:56:19.860 align:start position:0% the name server translates the domain 10:56:19.860 --> 10:56:21.710 align:start position:0% the name server translates the domain name<10:56:19.980> to<10:56:20.220> its<10:56:20.460> corresponding<10:56:20.880> IP<10:56:21.240> address<10:56:21.360> and 10:56:21.710 --> 10:56:21.720 align:start position:0% name to its corresponding IP address and 10:56:21.720 --> 10:56:23.870 align:start position:0% name to its corresponding IP address and we've<10:56:21.900> seen<10:56:22.080> an<10:56:22.320> example<10:56:22.620> of<10:56:22.800> that 10:56:23.870 --> 10:56:23.880 align:start position:0% we've seen an example of that 10:56:23.880 --> 10:56:26.266 align:start position:0% we've seen an example of that does<10:56:24.416> the<10:56:24.596> response<10:56:25.080> to<10:56:25.200> the<10:56:25.380> DNS<10:56:25.740> query<10:56:26.096> it 10:56:26.266 --> 10:56:26.276 align:start position:0% does the response to the DNS query it 10:56:26.276 --> 10:56:28.246 align:start position:0% does the response to the DNS query it receives<10:56:26.640> from<10:56:26.936> resolvers<10:56:27.596> or<10:56:27.776> the<10:56:28.080> name 10:56:28.246 --> 10:56:28.256 align:start position:0% receives from resolvers or the name 10:56:28.256 --> 10:56:30.290 align:start position:0% receives from resolvers or the name servers<10:56:28.680> I'm<10:56:28.860> going<10:56:28.980> to<10:56:29.040> talk<10:56:29.160> about 10:56:30.290 --> 10:56:30.300 align:start position:0% servers I'm going to talk about 10:56:30.300 --> 10:56:31.850 align:start position:0% servers I'm going to talk about um 10:56:31.850 --> 10:56:31.860 align:start position:0% um 10:56:31.860 --> 10:56:34.550 align:start position:0% um to<10:56:32.160> our<10:56:32.460> resolvers<10:56:33.000> in<10:56:33.180> a<10:56:33.360> minute<10:56:33.480> I<10:56:33.960> think<10:56:34.200> I'm 10:56:34.550 --> 10:56:34.560 align:start position:0% to our resolvers in a minute I think I'm 10:56:34.560 --> 10:56:36.586 align:start position:0% to our resolvers in a minute I think I'm not<10:56:34.740> sure<10:56:34.800> which<10:56:34.980> slide<10:56:35.276> it<10:56:35.460> is 10:56:36.586 --> 10:56:36.596 align:start position:0% not sure which slide it is 10:56:36.596 --> 10:56:38.630 align:start position:0% not sure which slide it is so<10:56:36.840> the<10:56:37.080> answers<10:56:37.256> to<10:56:37.500> the<10:56:37.680> DNS<10:56:38.040> queries<10:56:38.460> are 10:56:38.630 --> 10:56:38.640 align:start position:0% so the answers to the DNS queries are 10:56:38.640 --> 10:56:40.310 align:start position:0% so the answers to the DNS queries are based<10:56:38.936> upon<10:56:39.120> the<10:56:39.240> contents<10:56:39.776> of<10:56:39.900> the<10:56:40.140> name 10:56:40.310 --> 10:56:40.320 align:start position:0% based upon the contents of the name 10:56:40.320 --> 10:56:42.290 align:start position:0% based upon the contents of the name server<10:56:40.800> database<10:56:41.220> so<10:56:41.460> obviously<10:56:42.120> the 10:56:42.290 --> 10:56:42.300 align:start position:0% server database so obviously the 10:56:42.300 --> 10:56:45.830 align:start position:0% server database so obviously the database<10:56:42.840> is<10:56:43.080> full<10:56:43.560> of<10:56:43.800> records<10:56:44.520> of<10:56:45.840> um 10:56:45.830 --> 10:56:45.840 align:start position:0% database is full of records of um 10:56:45.840 --> 10:56:48.906 align:start position:0% database is full of records of um mappings<10:56:46.620> so<10:56:48.000> um 10:56:48.906 --> 10:56:48.916 align:start position:0% mappings so um 10:56:48.916 --> 10:56:55.130 align:start position:0% mappings so um x.com<10:56:49.916> and<10:56:50.880> it<10:56:51.000> will<10:56:51.120> be<10:56:51.300> mapped<10:56:51.720> to 10:56:55.130 --> 10:56:55.140 align:start position:0% 10:56:55.140 --> 10:56:57.050 align:start position:0% there's<10:56:55.620> a<10:56:55.800> lot<10:56:55.916> more<10:56:56.040> than<10:56:56.220> this<10:56:56.460> but<10:56:56.640> as<10:56:56.820> a 10:56:57.050 --> 10:56:57.060 align:start position:0% there's a lot more than this but as a 10:56:57.060 --> 10:56:59.266 align:start position:0% there's a lot more than this but as a simplified<10:56:57.360> illustration 10:56:59.266 --> 10:56:59.276 align:start position:0% simplified illustration 10:56:59.276 --> 10:57:01.130 align:start position:0% simplified illustration cached<10:57:00.000> information<10:57:00.180> is<10:57:00.596> learned<10:57:00.900> by<10:57:01.020> the 10:57:01.130 --> 10:57:01.140 align:start position:0% cached information is learned by the 10:57:01.140 --> 10:57:03.766 align:start position:0% cached information is learned by the name<10:57:01.256> server<10:57:01.680> from<10:57:01.860> other<10:57:02.096> name<10:57:02.276> servers<10:57:02.880> how 10:57:03.766 --> 10:57:03.776 align:start position:0% name server from other name servers how 10:57:03.776 --> 10:57:05.630 align:start position:0% name server from other name servers how often<10:57:04.020> they<10:57:04.080> update<10:57:04.436> the<10:57:04.620> cache<10:57:05.040> uh<10:57:05.460> just 10:57:05.630 --> 10:57:05.640 align:start position:0% often they update the cache uh just 10:57:05.640 --> 10:57:07.426 align:start position:0% often they update the cache uh just depends<10:57:06.000> on<10:57:06.180> obviously<10:57:06.900> their<10:57:07.140> local 10:57:07.426 --> 10:57:07.436 align:start position:0% depends on obviously their local 10:57:07.436 --> 10:57:09.406 align:start position:0% depends on obviously their local configurations 10:57:09.406 --> 10:57:09.416 align:start position:0% configurations 10:57:09.416 --> 10:57:11.266 align:start position:0% configurations now<10:57:09.776> you<10:57:09.900> can<10:57:10.020> get<10:57:10.140> an<10:57:10.320> authoritative<10:57:10.860> answer 10:57:11.266 --> 10:57:11.276 align:start position:0% now you can get an authoritative answer 10:57:11.276 --> 10:57:13.490 align:start position:0% now you can get an authoritative answer this<10:57:12.240> is<10:57:12.360> based<10:57:12.660> on<10:57:12.720> the<10:57:12.840> contents<10:57:13.256> of<10:57:13.380> the 10:57:13.490 --> 10:57:13.500 align:start position:0% this is based on the contents of the 10:57:13.500 --> 10:57:16.550 align:start position:0% this is based on the contents of the name<10:57:13.620> server<10:57:13.980> database<10:57:14.460> if<10:57:15.360> it's<10:57:15.596> a<10:57:16.080> cached 10:57:16.550 --> 10:57:16.560 align:start position:0% name server database if it's a cached 10:57:16.560 --> 10:57:19.190 align:start position:0% name server database if it's a cached answer<10:57:16.800> it's<10:57:17.700> known<10:57:17.936> as<10:57:18.200> non-authoritative 10:57:19.190 --> 10:57:19.200 align:start position:0% answer it's known as non-authoritative 10:57:19.200 --> 10:57:24.906 align:start position:0% answer it's known as non-authoritative now<10:57:20.040> on<10:57:20.276> your<10:57:20.520> PC<10:57:21.140> you<10:57:22.140> can<10:57:22.320> issue 10:57:24.906 --> 10:57:24.916 align:start position:0% now on your PC you can issue 10:57:24.916 --> 10:57:26.766 align:start position:0% now on your PC you can issue ip 10:57:26.766 --> 10:57:26.776 align:start position:0% ip 10:57:26.776 --> 10:57:29.470 align:start position:0% ip config<10:57:27.776> and<10:57:28.320> this<10:57:28.436> has<10:57:28.560> worked<10:57:28.800> for<10:57:28.980> me<10:57:29.160> before 10:57:29.470 --> 10:57:29.480 align:start position:0% config and this has worked for me before 10:57:29.480 --> 10:57:32.950 align:start position:0% config and this has worked for me before and<10:57:30.480> forward<10:57:30.960> slash 10:57:32.950 --> 10:57:32.960 align:start position:0% and forward slash 10:57:32.960 --> 10:57:38.030 align:start position:0% and forward slash flush<10:57:34.276> DNS<10:57:35.276> say<10:57:35.756> I've<10:57:36.060> moved<10:57:36.416> my<10:57:36.660> my<10:57:36.900> website 10:57:38.030 --> 10:57:38.040 align:start position:0% flush DNS say I've moved my my website 10:57:38.040 --> 10:57:39.830 align:start position:0% flush DNS say I've moved my my website from<10:57:38.460> one<10:57:38.640> hosting<10:57:39.000> company<10:57:39.180> which<10:57:39.596> I<10:57:39.720> have 10:57:39.830 --> 10:57:39.840 align:start position:0% from one hosting company which I have 10:57:39.840 --> 10:57:43.610 align:start position:0% from one hosting company which I have done<10:57:40.020> in<10:57:40.200> the<10:57:40.380> past<10:57:40.580> to<10:57:41.580> another 10:57:43.610 --> 10:57:43.620 align:start position:0% done in the past to another 10:57:43.620 --> 10:57:47.086 align:start position:0% done in the past to another I<10:57:44.276> can<10:57:44.756> um<10:57:44.756> I<10:57:45.360> can<10:57:45.540> force<10:57:45.840> a<10:57:46.020> flush<10:57:46.320> to<10:57:46.680> find<10:57:46.860> out 10:57:47.086 --> 10:57:47.096 align:start position:0% I can um I can force a flush to find out 10:57:47.096 --> 10:57:49.550 align:start position:0% I can um I can force a flush to find out where<10:57:47.520> to<10:57:48.000> to<10:57:48.240> see<10:57:48.480> if<10:57:48.596> this 10:57:49.550 --> 10:57:49.560 align:start position:0% where to to see if this 10:57:49.560 --> 10:57:51.950 align:start position:0% where to to see if this um<10:57:49.680> it's<10:57:50.340> been<10:57:50.520> moved<10:57:50.820> correctly 10:57:51.950 --> 10:57:51.960 align:start position:0% um it's been moved correctly 10:57:51.960 --> 10:57:53.746 align:start position:0% um it's been moved correctly and<10:57:52.500> obviously<10:57:52.800> I<10:57:52.916> could<10:57:53.040> put<10:57:53.160> the<10:57:53.340> IP<10:57:53.580> address 10:57:53.746 --> 10:57:53.756 align:start position:0% and obviously I could put the IP address 10:57:53.756 --> 10:57:57.350 align:start position:0% and obviously I could put the IP address in 10:57:57.350 --> 10:57:57.360 align:start position:0% 10:57:57.360 --> 10:57:59.266 align:start position:0% but<10:57:57.900> this<10:57:58.140> is<10:57:58.256> quite<10:57:58.436> a<10:57:58.560> stressful<10:57:58.800> time<10:57:59.040> if 10:57:59.266 --> 10:57:59.276 align:start position:0% but this is quite a stressful time if 10:57:59.276 --> 10:58:00.950 align:start position:0% but this is quite a stressful time if you<10:57:59.400> own<10:57:59.520> a<10:57:59.756> business<10:57:59.936> because<10:58:00.596> you've<10:58:00.840> got 10:58:00.950 --> 10:58:00.960 align:start position:0% you own a business because you've got 10:58:00.960 --> 10:58:02.086 align:start position:0% you own a business because you've got your<10:58:01.080> website 10:58:02.086 --> 10:58:02.096 align:start position:0% your website 10:58:02.096 --> 10:58:03.530 align:start position:0% your website um technically<10:58:02.520> in<10:58:02.700> two<10:58:02.880> places<10:58:03.120> although 10:58:03.530 --> 10:58:03.540 align:start position:0% um technically in two places although 10:58:03.540 --> 10:58:06.470 align:start position:0% um technically in two places although this<10:58:03.840> is<10:58:03.960> the<10:58:04.256> old<10:58:04.916> version<10:58:05.340> and<10:58:06.180> eventually 10:58:06.470 --> 10:58:06.480 align:start position:0% this is the old version and eventually 10:58:06.480 --> 10:58:09.050 align:start position:0% this is the old version and eventually the<10:58:06.720> records<10:58:07.080> will<10:58:07.140> update<10:58:07.560> but<10:58:08.276> uh<10:58:08.580> could 10:58:09.050 --> 10:58:09.060 align:start position:0% the records will update but uh could 10:58:09.060 --> 10:58:11.870 align:start position:0% the records will update but uh could possibly<10:58:09.480> be<10:58:09.660> asked<10:58:09.960> in<10:58:10.020> the<10:58:10.140> exam<10:58:10.320> ipconfig 10:58:11.870 --> 10:58:11.880 align:start position:0% possibly be asked in the exam ipconfig 10:58:11.880 --> 10:58:14.810 align:start position:0% possibly be asked in the exam ipconfig uh<10:58:12.480> forward<10:58:12.660> slash<10:58:13.020> flush<10:58:13.500> DNS<10:58:13.916> and<10:58:14.160> try<10:58:14.340> it<10:58:14.520> at 10:58:14.810 --> 10:58:14.820 align:start position:0% uh forward slash flush DNS and try it at 10:58:14.820 --> 10:58:17.150 align:start position:0% uh forward slash flush DNS and try it at home<10:58:14.936> if<10:58:15.180> you<10:58:15.300> like 10:58:17.150 --> 10:58:17.160 align:start position:0% home if you like 10:58:17.160 --> 10:58:20.570 align:start position:0% home if you like what's<10:58:17.580> the<10:58:17.820> DNS<10:58:18.180> composed<10:58:18.720> of<10:58:18.840> as<10:58:19.560> resolvo<10:58:20.460> is 10:58:20.570 --> 10:58:20.580 align:start position:0% what's the DNS composed of as resolvo is 10:58:20.580 --> 10:58:22.550 align:start position:0% what's the DNS composed of as resolvo is the<10:58:20.700> next<10:58:20.820> part<10:58:21.000> which<10:58:21.300> I<10:58:21.416> mentioned<10:58:21.776> it's<10:58:22.320> a 10:58:22.550 --> 10:58:22.560 align:start position:0% the next part which I mentioned it's a 10:58:22.560 --> 10:58:24.110 align:start position:0% the next part which I mentioned it's a software<10:58:22.800> component<10:58:23.276> that<10:58:23.520> comes<10:58:23.756> bundled 10:58:24.110 --> 10:58:24.120 align:start position:0% software component that comes bundled 10:58:24.120 --> 10:58:26.746 align:start position:0% software component that comes bundled with<10:58:24.416> your<10:58:24.540> operating<10:58:24.960> system<10:58:25.460> also<10:58:26.460> in 10:58:26.746 --> 10:58:26.756 align:start position:0% with your operating system also in 10:58:26.756 --> 10:58:30.530 align:start position:0% with your operating system also in network<10:58:27.360> Hardware 10:58:30.530 --> 10:58:30.540 align:start position:0% 10:58:30.540 --> 10:58:32.630 align:start position:0% the<10:58:31.256> internet<10:58:31.436> applications<10:58:32.040> such<10:58:32.276> as<10:58:32.460> web 10:58:32.630 --> 10:58:32.640 align:start position:0% the internet applications such as web 10:58:32.640 --> 10:58:34.670 align:start position:0% the internet applications such as web browsers<10:58:33.060> and<10:58:33.240> email<10:58:33.360> clients<10:58:34.020> need<10:58:34.200> a<10:58:34.380> domain 10:58:34.670 --> 10:58:34.680 align:start position:0% browsers and email clients need a domain 10:58:34.680 --> 10:58:37.906 align:start position:0% browsers and email clients need a domain name<10:58:34.800> lookup<10:58:35.220> so<10:58:36.180> this<10:58:36.540> is<10:58:36.840> a<10:58:37.256> piece<10:58:37.800> of 10:58:37.906 --> 10:58:37.916 align:start position:0% name lookup so this is a piece of 10:58:37.916 --> 10:58:44.330 align:start position:0% name lookup so this is a piece of software<10:58:38.340> that<10:58:39.660> um<10:58:39.916> issues<10:58:40.916> the<10:58:41.040> DNS<10:58:41.520> request 10:58:44.330 --> 10:58:44.340 align:start position:0% 10:58:44.340 --> 10:58:46.906 align:start position:0% the<10:58:44.700> resolver<10:58:45.060> accepts<10:58:45.416> the<10:58:45.480> DNS<10:58:45.840> queries<10:58:46.320> and 10:58:46.906 --> 10:58:46.916 align:start position:0% the resolver accepts the DNS queries and 10:58:46.916 --> 10:58:48.530 align:start position:0% the resolver accepts the DNS queries and if<10:58:47.096> the<10:58:47.276> required<10:58:47.700> information<10:58:47.820> is<10:58:48.360> available 10:58:48.530 --> 10:58:48.540 align:start position:0% if the required information is available 10:58:48.540 --> 10:58:51.110 align:start position:0% if the required information is available in<10:58:49.380> the<10:58:49.560> local<10:58:49.680> cache<10:58:50.160> it<10:58:50.220> returns<10:58:50.580> that<10:58:50.700> data 10:58:51.110 --> 10:58:51.120 align:start position:0% in the local cache it returns that data 10:58:51.120 --> 10:58:53.870 align:start position:0% in the local cache it returns that data to<10:58:51.300> the<10:58:51.416> client<10:58:51.720> so<10:58:52.680> your<10:58:52.916> PC<10:58:53.276> will<10:58:53.520> use<10:58:53.700> the 10:58:53.870 --> 10:58:53.880 align:start position:0% to the client so your PC will use the 10:58:53.880 --> 10:58:55.550 align:start position:0% to the client so your PC will use the resolver 10:58:55.550 --> 10:58:55.560 align:start position:0% resolver 10:58:55.560 --> 10:58:57.230 align:start position:0% resolver a<10:58:55.800> piece<10:58:56.160> of<10:58:56.276> little<10:58:56.460> piece<10:58:56.756> of<10:58:56.880> software 10:58:57.230 --> 10:58:57.240 align:start position:0% a piece of little piece of software 10:58:57.240 --> 10:59:00.586 align:start position:0% a piece of little piece of software somewhere 10:59:00.586 --> 10:59:00.596 align:start position:0% 10:59:00.596 --> 10:59:03.470 align:start position:0% then<10:59:01.020> it<10:59:01.200> will<10:59:01.320> go<10:59:01.500> out<10:59:01.800> to<10:59:02.040> the<10:59:02.580> internet<10:59:03.060> and 10:59:03.470 --> 10:59:03.480 align:start position:0% then it will go out to the internet and 10:59:03.480 --> 10:59:05.510 align:start position:0% then it will go out to the internet and obviously<10:59:03.900> return<10:59:04.680> it<10:59:04.916> so<10:59:05.096> then<10:59:05.340> you<10:59:05.400> can 10:59:05.510 --> 10:59:05.520 align:start position:0% obviously return it so then you can 10:59:05.520 --> 10:59:09.650 align:start position:0% obviously return it so then you can issue<10:59:05.820> the<10:59:06.480> ping<10:59:07.020> which<10:59:07.200> we<10:59:07.380> already<10:59:07.560> saw 10:59:09.650 --> 10:59:09.660 align:start position:0% issue the ping which we already saw 10:59:09.660 --> 10:59:11.266 align:start position:0% issue the ping which we already saw and<10:59:10.080> it's<10:59:10.200> not<10:59:10.436> available<10:59:10.560> it<10:59:10.916> sends<10:59:11.220> the 10:59:11.266 --> 10:59:11.276 align:start position:0% and it's not available it sends the 10:59:11.276 --> 10:59:14.390 align:start position:0% and it's not available it sends the query<10:59:11.580> to<10:59:11.820> the<10:59:12.000> name<10:59:12.300> server 10:59:14.390 --> 10:59:14.400 align:start position:0% query to the name server 10:59:14.400 --> 10:59:16.070 align:start position:0% query to the name server when<10:59:14.756> the<10:59:14.880> resolver<10:59:15.240> resumes<10:59:15.720> the<10:59:15.900> name 10:59:16.070 --> 10:59:16.080 align:start position:0% when the resolver resumes the name 10:59:16.080 --> 10:59:17.690 align:start position:0% when the resolver resumes the name server's<10:59:16.560> response<10:59:16.980> it<10:59:17.040> hands<10:59:17.340> the<10:59:17.400> result<10:59:17.520> to 10:59:17.690 --> 10:59:17.700 align:start position:0% server's response it hands the result to 10:59:17.700 --> 10:59:19.246 align:start position:0% server's response it hands the result to the<10:59:17.880> application<10:59:18.240> that<10:59:18.540> initiated<10:59:19.020> the 10:59:19.246 --> 10:59:19.256 align:start position:0% the application that initiated the 10:59:19.256 --> 10:59:21.530 align:start position:0% the application that initiated the request<10:59:19.560> so<10:59:19.860> this<10:59:20.040> will<10:59:20.160> be<10:59:20.340> your<10:59:20.756> web<10:59:21.000> browser 10:59:21.530 --> 10:59:21.540 align:start position:0% request so this will be your web browser 10:59:21.540 --> 10:59:23.210 align:start position:0% request so this will be your web browser email 10:59:23.210 --> 10:59:23.220 align:start position:0% email 10:59:23.220 --> 10:59:25.010 align:start position:0% email um<10:59:23.340> email<10:59:23.880> package<10:59:24.360> whatever<10:59:24.540> you've<10:59:24.900> already 10:59:25.010 --> 10:59:25.020 align:start position:0% um email package whatever you've already 10:59:25.020 --> 10:59:26.746 align:start position:0% um email package whatever you've already in<10:59:25.320> obviously<10:59:25.860> most<10:59:26.040> of<10:59:26.220> us<10:59:26.276> are<10:59:26.400> in<10:59:26.580> our<10:59:26.640> email 10:59:26.746 --> 10:59:26.756 align:start position:0% in obviously most of us are in our email 10:59:26.756 --> 10:59:29.570 align:start position:0% in obviously most of us are in our email off<10:59:27.060> the<10:59:27.240> cloud<10:59:27.360> now<10:59:27.596> like<10:59:28.436> um 10:59:29.570 --> 10:59:29.580 align:start position:0% off the cloud now like um 10:59:29.580 --> 10:59:31.490 align:start position:0% off the cloud now like um Gmail 10:59:31.490 --> 10:59:31.500 align:start position:0% Gmail 10:59:31.500 --> 10:59:33.586 align:start position:0% Gmail so<10:59:31.980> internet<10:59:32.160> application<10:59:32.820> sends<10:59:33.300> a<10:59:33.360> query 10:59:33.586 --> 10:59:33.596 align:start position:0% so internet application sends a query 10:59:33.596 --> 10:59:37.310 align:start position:0% so internet application sends a query for<10:59:34.020> translating<10:59:34.500> the<10:59:35.340> sampler<10:59:35.820> company 10:59:37.310 --> 10:59:37.320 align:start position:0% for translating the sampler company 10:59:37.320 --> 10:59:39.530 align:start position:0% for translating the sampler company resolver<10:59:38.040> checks<10:59:38.340> the<10:59:38.460> local<10:59:38.640> cash<10:59:38.936> so<10:59:39.300> you 10:59:39.530 --> 10:59:39.540 align:start position:0% resolver checks the local cash so you 10:59:39.540 --> 10:59:41.926 align:start position:0% resolver checks the local cash so you you<10:59:39.960> could<10:59:40.200> actually<10:59:40.436> check<10:59:40.800> your<10:59:41.096> DNS<10:59:41.460> cache 10:59:41.926 --> 10:59:41.936 align:start position:0% you could actually check your DNS cache 10:59:41.936 --> 10:59:45.766 align:start position:0% you could actually check your DNS cache on<10:59:42.720> your<10:59:43.080> home<10:59:43.436> computer 10:59:45.766 --> 10:59:45.776 align:start position:0% 10:59:45.776 --> 10:59:47.390 align:start position:0% if<10:59:46.080> it's<10:59:46.256> not<10:59:46.380> available<10:59:46.500> then<10:59:46.860> it<10:59:47.040> hands<10:59:47.276> over 10:59:47.390 --> 10:59:47.400 align:start position:0% if it's not available then it hands over 10:59:47.400 --> 10:59:49.370 align:start position:0% if it's not available then it hands over to<10:59:47.580> the<10:59:47.756> result<10:59:47.880> the<10:59:48.540> resolver<10:59:48.840> hands<10:59:49.140> it<10:59:49.256> over 10:59:49.370 --> 10:59:49.380 align:start position:0% to the result the resolver hands it over 10:59:49.380 --> 10:59:51.050 align:start position:0% to the result the resolver hands it over to<10:59:49.620> the<10:59:49.740> nearest<10:59:49.916> name<10:59:50.276> server<10:59:50.700> which<10:59:50.880> would 10:59:51.050 --> 10:59:51.060 align:start position:0% to the nearest name server which would 10:59:51.060 --> 10:59:54.170 align:start position:0% to the nearest name server which would be<10:59:51.180> normally<10:59:51.596> your<10:59:52.140> ISP 10:59:54.170 --> 10:59:54.180 align:start position:0% be normally your ISP 10:59:54.180 --> 10:59:56.570 align:start position:0% be normally your ISP name<10:59:54.540> serversy<10:59:55.380> determines<10:59:55.916> whether<10:59:56.096> it<10:59:56.400> can 10:59:56.570 --> 10:59:56.580 align:start position:0% name serversy determines whether it can 10:59:56.580 --> 10:59:59.630 align:start position:0% name serversy determines whether it can provide<10:59:56.820> the<10:59:57.120> data 10:59:59.630 --> 10:59:59.640 align:start position:0% 10:59:59.640 --> 11:00:01.490 align:start position:0% if<10:59:59.936> it's<11:00:00.120> not<11:00:00.240> available<11:00:00.360> then<11:00:00.840> it<11:00:01.080> goes<11:00:01.320> all 11:00:01.490 --> 11:00:01.500 align:start position:0% if it's not available then it goes all 11:00:01.500 --> 11:00:02.810 align:start position:0% if it's not available then it goes all the<11:00:01.680> way<11:00:01.740> off 11:00:02.810 --> 11:00:02.820 align:start position:0% the way off 11:00:02.820 --> 11:00:05.690 align:start position:0% the way off so<11:00:03.180> PC 11:00:05.690 --> 11:00:05.700 align:start position:0% so PC 11:00:05.700 --> 11:00:08.926 align:start position:0% so PC resolver 11:00:08.926 --> 11:00:08.936 align:start position:0% 11:00:08.936 --> 11:00:11.630 align:start position:0% which<11:00:09.540> basically<11:00:09.960> just<11:00:10.140> checks<11:00:10.620> your<11:00:11.220> your 11:00:11.630 --> 11:00:11.640 align:start position:0% which basically just checks your your 11:00:11.640 --> 11:00:13.790 align:start position:0% which basically just checks your your DNS 11:00:13.790 --> 11:00:13.800 align:start position:0% DNS 11:00:13.800 --> 11:00:18.050 align:start position:0% DNS cash<11:00:14.400> on<11:00:14.756> your<11:00:15.000> home<11:00:15.540> computer<11:00:15.860> if<11:00:16.860> not<11:00:17.096> it'll 11:00:18.050 --> 11:00:18.060 align:start position:0% cash on your home computer if not it'll 11:00:18.060 --> 11:00:21.290 align:start position:0% cash on your home computer if not it'll go<11:00:18.240> off<11:00:18.416> to<11:00:18.660> your<11:00:18.900> ISP<11:00:19.860> if<11:00:20.520> the<11:00:20.640> ISP<11:00:21.000> doesn't 11:00:21.290 --> 11:00:21.300 align:start position:0% go off to your ISP if the ISP doesn't 11:00:21.300 --> 11:00:22.246 align:start position:0% go off to your ISP if the ISP doesn't know 11:00:22.246 --> 11:00:22.256 align:start position:0% know 11:00:22.256 --> 11:00:24.350 align:start position:0% know it<11:00:22.800> could<11:00:22.916> query<11:00:23.220> another<11:00:23.460> server<11:00:24.000> but<11:00:24.180> let's 11:00:24.350 --> 11:00:24.360 align:start position:0% it could query another server but let's 11:00:24.360 --> 11:00:26.810 align:start position:0% it could query another server but let's just<11:00:24.480> say<11:00:24.660> it<11:00:24.776> goes<11:00:25.080> off<11:00:25.200> to<11:00:25.436> the<11:00:25.800> the<11:00:26.580> air 11:00:26.810 --> 11:00:26.820 align:start position:0% just say it goes off to the the air 11:00:26.820 --> 11:00:29.150 align:start position:0% just say it goes off to the the air route<11:00:27.120> there<11:00:27.596> so<11:00:28.320> this<11:00:28.500> would<11:00:28.680> all<11:00:28.916> happen 11:00:29.150 --> 11:00:29.160 align:start position:0% route there so this would all happen 11:00:29.160 --> 11:00:32.450 align:start position:0% route there so this would all happen pretty<11:00:30.000> quickly<11:00:30.416> obviously<11:00:31.020> you've<11:00:31.980> you<11:00:32.220> know 11:00:32.450 --> 11:00:32.460 align:start position:0% pretty quickly obviously you've you know 11:00:32.460 --> 11:00:34.790 align:start position:0% pretty quickly obviously you've you know yourself<11:00:32.640> you've<11:00:33.120> put<11:00:33.240> in<11:00:33.416> a<11:00:33.540> URL<11:00:33.960> and<11:00:34.620> just 11:00:34.790 --> 11:00:34.800 align:start position:0% yourself you've put in a URL and just 11:00:34.800 --> 11:00:38.210 align:start position:0% yourself you've put in a URL and just sat<11:00:34.980> there<11:00:35.756> in<11:00:36.480> how<11:00:37.200> we're<11:00:37.500> so<11:00:37.740> impatient 11:00:38.210 --> 11:00:38.220 align:start position:0% sat there in how we're so impatient 11:00:38.220 --> 11:00:39.950 align:start position:0% sat there in how we're so impatient nowadays<11:00:38.756> you<11:00:38.880> sat<11:00:39.060> there<11:00:39.240> in<11:00:39.480> any<11:00:39.660> more<11:00:39.840> than 11:00:39.950 --> 11:00:39.960 align:start position:0% nowadays you sat there in any more than 11:00:39.960 --> 11:00:41.870 align:start position:0% nowadays you sat there in any more than five<11:00:40.140> seconds<11:00:40.320> you<11:00:40.680> start<11:00:40.916> hitting<11:00:41.820> the 11:00:41.870 --> 11:00:41.880 align:start position:0% five seconds you start hitting the 11:00:41.880 --> 11:00:44.570 align:start position:0% five seconds you start hitting the refresh<11:00:42.240> button 11:00:44.570 --> 11:00:44.580 align:start position:0% refresh button 11:00:44.580 --> 11:00:46.550 align:start position:0% refresh button all<11:00:45.060> right<11:00:45.180> so<11:00:45.360> the<11:00:45.480> name<11:00:45.596> server<11:00:45.960> ask<11:00:46.140> the.com 11:00:46.550 --> 11:00:46.560 align:start position:0% all right so the name server ask the.com 11:00:46.560 --> 11:00:48.586 align:start position:0% all right so the name server ask the.com name<11:00:46.800> server<11:00:47.220> and<11:00:47.400> gets<11:00:47.700> finally<11:00:48.000> gets<11:00:48.240> the<11:00:48.300> IP 11:00:48.586 --> 11:00:48.596 align:start position:0% name server and gets finally gets the IP 11:00:48.596 --> 11:00:49.790 align:start position:0% name server and gets finally gets the IP address 11:00:49.790 --> 11:00:49.800 align:start position:0% address 11:00:49.800 --> 11:00:51.766 align:start position:0% address since<11:00:50.340> the<11:00:50.520> sample<11:00:50.880> company<11:00:51.060> has<11:00:51.416> the<11:00:51.540> IP 11:00:51.766 --> 11:00:51.776 align:start position:0% since the sample company has the IP 11:00:51.776 --> 11:00:54.170 align:start position:0% since the sample company has the IP address<11:00:51.900> in<11:00:52.200> its<11:00:52.500> own<11:00:52.560> database<11:00:53.096> uh<11:00:54.000> this<11:00:54.180> this 11:00:54.170 --> 11:00:54.180 align:start position:0% address in its own database uh this this 11:00:54.180 --> 11:00:56.810 align:start position:0% address in its own database uh this this would<11:00:54.480> be<11:00:54.596> for<11:00:54.776> a<11:00:54.960> new<11:00:55.140> domain<11:00:55.740> I<11:00:55.916> guess<11:00:56.096> the 11:00:56.810 --> 11:00:56.820 align:start position:0% would be for a new domain I guess the 11:00:56.820 --> 11:00:58.310 align:start position:0% would be for a new domain I guess the name<11:00:56.936> server<11:00:57.300> that<11:00:57.480> requested<11:00:57.900> the<11:00:58.020> IP 11:00:58.310 --> 11:00:58.320 align:start position:0% name server that requested the IP 11:00:58.320 --> 11:01:00.470 align:start position:0% name server that requested the IP address<11:00:58.500> now<11:00:58.916> gets<11:00:59.276> an<11:00:59.400> authoritative<11:00:59.936> IP 11:01:00.470 --> 11:01:00.480 align:start position:0% address now gets an authoritative IP 11:01:00.480 --> 11:01:02.086 align:start position:0% address now gets an authoritative IP address<11:01:00.776> as<11:01:01.140> the<11:01:01.380> answer 11:01:02.086 --> 11:01:02.096 align:start position:0% address as the answer 11:01:02.096 --> 11:01:04.426 align:start position:0% address as the answer and<11:01:02.460> that's<11:01:02.580> all<11:01:02.820> finally<11:01:03.180> relayed 11:01:04.426 --> 11:01:04.436 align:start position:0% and that's all finally relayed 11:01:04.436 --> 11:01:06.766 align:start position:0% and that's all finally relayed you<11:01:04.916> could<11:01:04.980> have<11:01:05.160> a<11:01:05.276> couple<11:01:05.400> of<11:01:05.520> query<11:01:05.880> types<11:01:06.360> a 11:01:06.766 --> 11:01:06.776 align:start position:0% you could have a couple of query types a 11:01:06.776 --> 11:01:09.406 align:start position:0% you could have a couple of query types a query<11:01:07.140> received<11:01:07.740> by<11:01:07.860> the<11:01:08.040> name<11:01:08.160> server<11:01:08.640> this 11:01:09.406 --> 11:01:09.416 align:start position:0% query received by the name server this 11:01:09.416 --> 11:01:12.110 align:start position:0% query received by the name server this is<11:01:09.540> a<11:01:09.720> recursive<11:01:10.380> query<11:01:10.740> this<11:01:11.220> is<11:01:11.340> received<11:01:11.880> by 11:01:12.110 --> 11:01:12.120 align:start position:0% is a recursive query this is received by 11:01:12.120 --> 11:01:14.830 align:start position:0% is a recursive query this is received by the<11:01:12.416> uh<11:01:13.080> received<11:01:13.500> from<11:01:13.620> the<11:01:13.800> resolver 11:01:14.830 --> 11:01:14.840 align:start position:0% the uh received from the resolver 11:01:14.840 --> 11:01:17.086 align:start position:0% the uh received from the resolver non-recursive<11:01:15.840> is<11:01:16.140> received<11:01:16.620> by<11:01:16.860> other 11:01:17.086 --> 11:01:17.096 align:start position:0% non-recursive is received by other 11:01:17.096 --> 11:01:19.790 align:start position:0% non-recursive is received by other servers<11:01:17.700> so<11:01:18.480> they<11:01:18.660> could<11:01:18.840> just<11:01:19.020> be<11:01:19.140> doing<11:01:19.320> an 11:01:19.790 --> 11:01:19.800 align:start position:0% servers so they could just be doing an 11:01:19.800 --> 11:01:23.810 align:start position:0% servers so they could just be doing an update<11:01:20.700> of<11:01:20.880> their<11:01:21.000> own<11:01:21.120> records 11:01:23.810 --> 11:01:23.820 align:start position:0% 11:01:23.820 --> 11:01:26.570 align:start position:0% uh<11:01:24.776> probably<11:01:25.020> in<11:01:25.256> the<11:01:25.436> exam<11:01:25.680> you'll<11:01:26.096> be<11:01:26.276> asked 11:01:26.570 --> 11:01:26.580 align:start position:0% uh probably in the exam you'll be asked 11:01:26.580 --> 11:01:28.906 align:start position:0% uh probably in the exam you'll be asked a<11:01:26.700> little<11:01:26.756> bit<11:01:26.880> about<11:01:27.120> what<11:01:28.020> are<11:01:28.140> DNS<11:01:28.500> records 11:01:28.906 --> 11:01:28.916 align:start position:0% a little bit about what are DNS records 11:01:28.916 --> 11:01:31.610 align:start position:0% a little bit about what are DNS records what<11:01:29.096> do<11:01:29.220> they<11:01:29.340> consist<11:01:29.640> of 11:01:31.610 --> 11:01:31.620 align:start position:0% what do they consist of 11:01:31.620 --> 11:01:34.070 align:start position:0% what do they consist of also<11:01:32.340> known<11:01:32.520> as<11:01:32.700> resource<11:01:33.240> records<11:01:33.660> these 11:01:34.070 --> 11:01:34.080 align:start position:0% also known as resource records these 11:01:34.080 --> 11:01:35.990 align:start position:0% also known as resource records these have<11:01:34.200> the<11:01:34.436> information<11:01:34.620> that<11:01:35.160> we<11:01:35.340> need<11:01:35.520> to<11:01:35.756> do 11:01:35.990 --> 11:01:36.000 align:start position:0% have the information that we need to do 11:01:36.000 --> 11:01:38.266 align:start position:0% have the information that we need to do the<11:01:36.180> resolving 11:01:38.266 --> 11:01:38.276 align:start position:0% the resolving 11:01:38.276 --> 11:01:41.030 align:start position:0% the resolving the<11:01:38.880> records<11:01:39.240> map<11:01:39.416> a<11:01:39.660> domain<11:01:39.960> to<11:01:40.140> its<11:01:40.380> ipv4 11:01:41.030 --> 11:01:41.040 align:start position:0% the records map a domain to its ipv4 11:01:41.040 --> 11:01:44.210 align:start position:0% the records map a domain to its ipv4 address<11:01:41.340> these<11:01:42.120> are<11:01:42.240> a<11:01:42.480> records 11:01:44.210 --> 11:01:44.220 align:start position:0% address these are a records 11:01:44.220 --> 11:01:45.950 align:start position:0% address these are a records so<11:01:44.580> this<11:01:44.820> is<11:01:44.936> the<11:01:45.120> type<11:01:45.300> of<11:01:45.416> question<11:01:45.596> you 11:01:45.950 --> 11:01:45.960 align:start position:0% so this is the type of question you 11:01:45.960 --> 11:01:48.110 align:start position:0% so this is the type of question you might<11:01:46.140> get<11:01:46.320> asked<11:01:46.436> what<11:01:46.620> has<11:01:46.800> an<11:01:46.916> a<11:01:47.040> record<11:01:47.276> it 11:01:48.110 --> 11:01:48.120 align:start position:0% might get asked what has an a record it 11:01:48.120 --> 11:01:50.810 align:start position:0% might get asked what has an a record it maps<11:01:48.660> The<11:01:48.840> Domain<11:01:49.200> to<11:01:49.380> its<11:01:49.560> high<11:01:49.680> people<11:01:49.916> for 11:01:50.810 --> 11:01:50.820 align:start position:0% maps The Domain to its high people for 11:01:50.820 --> 11:01:52.310 align:start position:0% maps The Domain to its high people for address 11:01:52.310 --> 11:01:52.320 align:start position:0% address 11:01:52.320 --> 11:01:55.850 align:start position:0% address so<11:01:52.740> here's<11:01:53.040> an<11:01:53.096> example<11:01:53.900> you<11:01:54.900> would<11:01:55.140> put<11:01:55.500> these 11:01:55.850 --> 11:01:55.860 align:start position:0% so here's an example you would put these 11:01:55.860 --> 11:01:58.670 align:start position:0% so here's an example you would put these in<11:01:56.096> when<11:01:56.520> you<11:01:56.700> register<11:01:57.000> your<11:01:57.300> domain<11:01:57.720> name<11:01:57.900> if 11:01:58.670 --> 11:01:58.680 align:start position:0% in when you register your domain name if 11:01:58.680 --> 11:02:00.586 align:start position:0% in when you register your domain name if you<11:01:58.916> host<11:01:59.220> with<11:01:59.580> the<11:01:59.756> same<11:01:59.880> company<11:02:00.060> that<11:02:00.416> you 11:02:00.586 --> 11:02:00.596 align:start position:0% you host with the same company that you 11:02:00.596 --> 11:02:03.950 align:start position:0% you host with the same company that you register<11:02:00.980> so<11:02:01.980> there's<11:02:02.756> a<11:02:03.000> company<11:02:03.300> called<11:02:03.596> one 11:02:03.950 --> 11:02:03.960 align:start position:0% register so there's a company called one 11:02:03.960 --> 11:02:08.266 align:start position:0% register so there's a company called one two<11:02:04.256> three<11:02:04.756> reg<11:02:05.756> dot<11:02:06.416> Co<11:02:06.540> dot<11:02:07.080> UK<11:02:07.436> that<11:02:07.980> I<11:02:08.096> used 11:02:08.266 --> 11:02:08.276 align:start position:0% two three reg dot Co dot UK that I used 11:02:08.276 --> 11:02:12.230 align:start position:0% two three reg dot Co dot UK that I used to<11:02:08.460> register<11:02:09.300> my<11:02:09.540> names<11:02:09.720> with<11:02:10.020> and<11:02:10.980> host<11:02:11.220> so<11:02:11.820> I 11:02:12.230 --> 11:02:12.240 align:start position:0% to register my names with and host so I 11:02:12.240 --> 11:02:15.230 align:start position:0% to register my names with and host so I think<11:02:12.300> it<11:02:12.480> was<11:02:12.596> all<11:02:12.720> done<11:02:12.900> for<11:02:13.140> me<11:02:13.256> there 11:02:15.230 --> 11:02:15.240 align:start position:0% think it was all done for me there 11:02:15.240 --> 11:02:17.810 align:start position:0% think it was all done for me there now<11:02:15.840> some<11:02:16.140> of<11:02:16.256> these<11:02:16.380> domain<11:02:16.740> names 11:02:17.810 --> 11:02:17.820 align:start position:0% now some of these domain names 11:02:17.820 --> 11:02:19.370 align:start position:0% now some of these domain names um say<11:02:18.240> in 11:02:19.370 --> 11:02:19.380 align:start position:0% um say in 11:02:19.380 --> 11:02:23.570 align:start position:0% um say in 60<11:02:20.276> days.com 11:02:23.570 --> 11:02:23.580 align:start position:0% 11:02:23.580 --> 11:02:27.170 align:start position:0% I<11:02:24.840> um<11:02:24.840> had<11:02:25.500> it<11:02:25.680> registered<11:02:26.220> here<11:02:26.520> but<11:02:27.000> it's 11:02:27.170 --> 11:02:27.180 align:start position:0% I um had it registered here but it's 11:02:27.180 --> 11:02:29.510 align:start position:0% I um had it registered here but it's actually<11:02:27.360> hosted<11:02:28.020> somewhere<11:02:28.620> else<11:02:28.800> now<11:02:29.096> so 11:02:29.510 --> 11:02:29.520 align:start position:0% actually hosted somewhere else now so 11:02:29.520 --> 11:02:31.850 align:start position:0% actually hosted somewhere else now so about<11:02:29.756> to<11:02:30.000> go<11:02:30.180> in<11:02:30.360> and 11:02:31.850 --> 11:02:31.860 align:start position:0% about to go in and 11:02:31.860 --> 11:02:33.350 align:start position:0% about to go in and um<11:02:31.916> I<11:02:32.096> actually<11:02:32.220> put<11:02:32.460> the<11:02:32.640> name<11:02:32.756> server<11:02:33.180> that's 11:02:33.350 --> 11:02:33.360 align:start position:0% um I actually put the name server that's 11:02:33.360 --> 11:02:35.570 align:start position:0% um I actually put the name server that's the<11:02:33.540> only<11:02:33.660> part<11:02:33.960> I've<11:02:34.200> put<11:02:34.436> in<11:02:34.620> but<11:02:35.160> there's<11:02:35.400> a 11:02:35.570 --> 11:02:35.580 align:start position:0% the only part I've put in but there's a 11:02:35.580 --> 11:02:37.670 align:start position:0% the only part I've put in but there's a there's<11:02:35.880> other<11:02:36.060> records<11:02:36.776> I<11:02:37.020> can<11:02:37.140> manipulate 11:02:37.670 --> 11:02:37.680 align:start position:0% there's other records I can manipulate 11:02:37.680 --> 11:02:40.310 align:start position:0% there's other records I can manipulate and<11:02:38.160> as<11:02:38.276> the<11:02:38.460> owner<11:02:38.700> of<11:02:38.820> this<11:02:38.936> domain<11:02:39.360> I<11:02:40.080> can<11:02:40.200> do 11:02:40.310 --> 11:02:40.320 align:start position:0% and as the owner of this domain I can do 11:02:40.320 --> 11:02:42.290 align:start position:0% and as the owner of this domain I can do that<11:02:40.436> but<11:02:40.860> just<11:02:41.096> be<11:02:41.220> very<11:02:41.460> careful<11:02:41.820> what<11:02:42.120> you 11:02:42.290 --> 11:02:42.300 align:start position:0% that but just be very careful what you 11:02:42.300 --> 11:02:43.970 align:start position:0% that but just be very careful what you do<11:02:42.480> if<11:02:43.256> you<11:02:43.380> don't<11:02:43.500> know<11:02:43.560> what<11:02:43.680> you're<11:02:43.860> doing 11:02:43.970 --> 11:02:43.980 align:start position:0% do if you don't know what you're doing 11:02:43.980 --> 11:02:45.950 align:start position:0% do if you don't know what you're doing then<11:02:44.700> you<11:02:45.060> need<11:02:45.180> to<11:02:45.240> ask<11:02:45.360> for<11:02:45.540> help<11:02:45.720> because 11:02:45.950 --> 11:02:45.960 align:start position:0% then you need to ask for help because 11:02:45.960 --> 11:02:48.170 align:start position:0% then you need to ask for help because things<11:02:46.256> can<11:02:46.500> go<11:02:46.680> wrong<11:02:46.860> because<11:02:47.520> as<11:02:47.756> I've<11:02:47.936> told 11:02:48.170 --> 11:02:48.180 align:start position:0% things can go wrong because as I've told 11:02:48.180 --> 11:02:49.970 align:start position:0% things can go wrong because as I've told you<11:02:48.300> you<11:02:48.540> can<11:02:48.720> split 11:02:49.970 --> 11:02:49.980 align:start position:0% you you can split 11:02:49.980 --> 11:02:52.670 align:start position:0% you you can split your<11:02:50.756> mail 11:02:52.670 --> 11:02:52.680 align:start position:0% your mail 11:02:52.680 --> 11:02:56.210 align:start position:0% your mail to<11:02:53.276> go<11:02:53.400> to<11:02:53.520> oneip<11:02:54.000> address<11:02:54.416> your 11:02:56.210 --> 11:02:56.220 align:start position:0% to go to oneip address your 11:02:56.220 --> 11:02:59.510 align:start position:0% to go to oneip address your um your<11:02:57.060> web<11:02:57.240> server<11:02:58.200> can<11:02:58.680> be<11:02:58.860> hosted<11:02:59.276> on 11:02:59.510 --> 11:02:59.520 align:start position:0% um your web server can be hosted on 11:02:59.520 --> 11:03:01.070 align:start position:0% um your web server can be hosted on another<11:02:59.640> IP<11:03:00.060> address<11:03:00.240> you've<11:03:00.596> got<11:03:00.720> to<11:03:00.900> have 11:03:01.070 --> 11:03:01.080 align:start position:0% another IP address you've got to have 11:03:01.080 --> 11:03:03.766 align:start position:0% another IP address you've got to have records<11:03:01.620> for<11:03:01.740> all<11:03:01.916> of<11:03:02.040> this 11:03:03.766 --> 11:03:03.776 align:start position:0% records for all of this 11:03:03.776 --> 11:03:06.890 align:start position:0% records for all of this so<11:03:04.256> example<11:03:04.740> of<11:03:04.860> an<11:03:05.040> a<11:03:05.160> record<11:03:05.400> first<11:03:06.360> is<11:03:06.720> used 11:03:06.890 --> 11:03:06.900 align:start position:0% so example of an a record first is used 11:03:06.900 --> 11:03:08.630 align:start position:0% so example of an a record first is used to<11:03:07.140> take<11:03:07.256> care<11:03:07.436> of<11:03:07.560> situations<11:03:07.980> when<11:03:08.340> someone 11:03:08.630 --> 11:03:08.640 align:start position:0% to take care of situations when someone 11:03:08.640 --> 11:03:11.086 align:start position:0% to take care of situations when someone tries<11:03:09.360> to<11:03:09.480> access<11:03:09.660> the<11:03:09.960> domain<11:03:10.320> name<11:03:10.500> without 11:03:11.086 --> 11:03:11.096 align:start position:0% tries to access the domain name without 11:03:11.096 --> 11:03:14.450 align:start position:0% tries to access the domain name without typing<11:03:11.640> www<11:03:12.360> most<11:03:12.900> of<11:03:13.080> us<11:03:13.140> don't<11:03:13.320> bother<11:03:13.620> now 11:03:14.450 --> 11:03:14.460 align:start position:0% typing www most of us don't bother now 11:03:14.460 --> 11:03:16.670 align:start position:0% typing www most of us don't bother now so<11:03:14.820> it'll<11:03:15.060> resolved<11:03:15.480> correctly<11:03:15.840> the<11:03:16.256> the 11:03:16.670 --> 11:03:16.680 align:start position:0% so it'll resolved correctly the the 11:03:16.680 --> 11:03:18.950 align:start position:0% so it'll resolved correctly the the first<11:03:16.916> one<11:03:17.160> being 11:03:18.950 --> 11:03:18.960 align:start position:0% first one being 11:03:18.960 --> 11:03:20.926 align:start position:0% first one being they<11:03:19.500> say<11:03:19.740> ah<11:03:20.040> sorry 11:03:20.926 --> 11:03:20.936 align:start position:0% they say ah sorry 11:03:20.936 --> 11:03:24.350 align:start position:0% they say ah sorry so<11:03:21.416> somebody<11:03:21.660> hasn't<11:03:22.080> put<11:03:22.200> www 11:03:24.350 --> 11:03:24.360 align:start position:0% so somebody hasn't put www 11:03:24.360 --> 11:03:26.746 align:start position:0% so somebody hasn't put www and<11:03:24.900> this<11:03:25.080> is<11:03:25.560> um<11:03:25.560> this<11:03:25.916> is<11:03:26.040> a<11:03:26.160> wild<11:03:26.276> card<11:03:26.520> so 11:03:26.746 --> 11:03:26.756 align:start position:0% and this is um this is a wild card so 11:03:26.756 --> 11:03:29.746 align:start position:0% and this is um this is a wild card so anything<11:03:26.936> before<11:03:27.416> your<11:03:28.320> domain<11:03:28.680> name<11:03:28.916> is<11:03:29.580> just 11:03:29.746 --> 11:03:29.756 align:start position:0% anything before your domain name is just 11:03:29.756 --> 11:03:31.790 align:start position:0% anything before your domain name is just going<11:03:30.060> to<11:03:30.180> go<11:03:30.300> to<11:03:30.480> and<11:03:31.020> whatever<11:03:31.380> server 11:03:31.790 --> 11:03:31.800 align:start position:0% going to go to and whatever server 11:03:31.800 --> 11:03:37.070 align:start position:0% going to go to and whatever server they're<11:03:31.980> hosting<11:03:32.340> it<11:03:32.520> on<11:03:32.700> here 11:03:37.070 --> 11:03:37.080 align:start position:0% 11:03:37.080 --> 11:03:38.926 align:start position:0% the<11:03:37.560> second<11:03:37.680> record<11:03:37.916> we<11:03:38.276> saw<11:03:38.460> is<11:03:38.640> the<11:03:38.820> wild 11:03:38.926 --> 11:03:38.936 align:start position:0% the second record we saw is the wild 11:03:38.936 --> 11:03:41.150 align:start position:0% the second record we saw is the wild card<11:03:39.180> it<11:03:39.416> will<11:03:39.540> direct<11:03:39.720> any<11:03:40.020> subdomains<11:03:40.800> to 11:03:41.150 --> 11:03:41.160 align:start position:0% card it will direct any subdomains to 11:03:41.160 --> 11:03:43.490 align:start position:0% card it will direct any subdomains to the<11:03:41.520> hosting<11:03:41.880> server<11:03:42.300> if<11:03:42.776> you<11:03:42.840> so<11:03:43.020> wish<11:03:43.256> you 11:03:43.490 --> 11:03:43.500 align:start position:0% the hosting server if you so wish you 11:03:43.500 --> 11:03:46.370 align:start position:0% the hosting server if you so wish you can<11:03:43.620> then<11:03:43.740> point<11:03:44.040> it<11:03:44.276> off<11:03:44.520> somewhere<11:03:45.360> else<11:03:45.540> or 11:03:46.370 --> 11:03:46.380 align:start position:0% can then point it off somewhere else or 11:03:46.380 --> 11:03:50.530 align:start position:0% can then point it off somewhere else or you<11:03:46.560> can<11:03:46.680> add<11:03:47.220> it<11:03:47.340> into<11:03:47.520> the<11:03:47.756> DNA<11:03:48.480> DNS<11:03:49.020> records 11:03:50.530 --> 11:03:50.540 align:start position:0% you can add it into the DNA DNS records 11:03:50.540 --> 11:03:53.390 align:start position:0% you can add it into the DNA DNS records the<11:03:51.740> quadrupalade<11:03:52.740> if<11:03:52.980> there's<11:03:53.096> any<11:03:53.220> quick 11:03:53.390 --> 11:03:53.400 align:start position:0% the quadrupalade if there's any quick 11:03:53.400 --> 11:03:56.630 align:start position:0% the quadrupalade if there's any quick way<11:03:53.580> of<11:03:53.756> saying<11:03:54.000> this<11:03:54.180> actually<11:03:54.360> AAA<11:03:55.276> oh<11:03:56.276> could 11:03:56.630 --> 11:03:56.640 align:start position:0% way of saying this actually AAA oh could 11:03:56.640 --> 11:03:57.950 align:start position:0% way of saying this actually AAA oh could you<11:03:56.756> play 11:03:57.950 --> 11:03:57.960 align:start position:0% you play 11:03:57.960 --> 11:04:01.190 align:start position:0% you play because<11:03:58.860> um<11:03:59.120> over<11:04:00.120> in<11:04:00.416> Australia<11:04:00.776> this<11:04:00.960> means 11:04:01.190 --> 11:04:01.200 align:start position:0% because um over in Australia this means 11:04:01.200 --> 11:04:02.690 align:start position:0% because um over in Australia this means the<11:04:01.320> Australian 11:04:02.690 --> 11:04:02.700 align:start position:0% the Australian 11:04:02.700 --> 11:04:04.906 align:start position:0% the Australian um<11:04:02.820> Automobile<11:04:03.596> Association<11:04:04.256> I<11:04:04.680> know<11:04:04.800> it's 11:04:04.906 --> 11:04:04.916 align:start position:0% um Automobile Association I know it's 11:04:04.916 --> 11:04:06.950 align:start position:0% um Automobile Association I know it's Triple<11:04:05.276> A<11:04:05.460> we've<11:04:05.640> got<11:04:05.756> over<11:04:05.880> here<11:04:06.180> so<11:04:06.776> you're 11:04:06.950 --> 11:04:06.960 align:start position:0% Triple A we've got over here so you're 11:04:06.960 --> 11:04:08.690 align:start position:0% Triple A we've got over here so you're just<11:04:07.140> gonna<11:04:07.256> be<11:04:07.380> careful<11:04:07.620> what<11:04:07.916> if<11:04:08.400> anyone 11:04:08.690 --> 11:04:08.700 align:start position:0% just gonna be careful what if anyone 11:04:08.700 --> 11:04:12.230 align:start position:0% just gonna be careful what if anyone else<11:04:08.880> is<11:04:09.000> using<11:04:09.360> these<11:04:09.720> uh<11:04:10.320> letters 11:04:12.230 --> 11:04:12.240 align:start position:0% else is using these uh letters 11:04:12.240 --> 11:04:14.510 align:start position:0% else is using these uh letters this<11:04:12.596> is<11:04:12.660> an<11:04:12.840> IPv6<11:04:13.436> address<11:04:13.680> that<11:04:14.040> maps<11:04:14.400> The 11:04:14.510 --> 11:04:14.520 align:start position:0% this is an IPv6 address that maps The 11:04:14.520 --> 11:04:16.906 align:start position:0% this is an IPv6 address that maps The Domain<11:04:14.756> to<11:04:14.936> its<11:04:15.180> IPv6<11:04:15.900> address<11:04:16.200> obvious 11:04:16.906 --> 11:04:16.916 align:start position:0% Domain to its IPv6 address obvious 11:04:16.916 --> 11:04:20.266 align:start position:0% Domain to its IPv6 address obvious obviously<11:04:17.580> because<11:04:18.480> um<11:04:18.480> we<11:04:18.776> need<11:04:18.960> to<11:04:19.080> be<11:04:19.276> we're 11:04:20.266 --> 11:04:20.276 align:start position:0% obviously because um we need to be we're 11:04:20.276 --> 11:04:22.246 align:start position:0% obviously because um we need to be we're moving<11:04:20.460> to<11:04:20.640> IPv6<11:04:21.300> now 11:04:22.246 --> 11:04:22.256 align:start position:0% moving to IPv6 now 11:04:22.256 --> 11:04:25.790 align:start position:0% moving to IPv6 now so<11:04:22.680> the<11:04:22.800> 128-bit<11:04:23.756> address 11:04:25.790 --> 11:04:25.800 align:start position:0% so the 128-bit address 11:04:25.800 --> 11:04:28.370 align:start position:0% so the 128-bit address there's<11:04:26.220> an<11:04:26.400> MX<11:04:26.756> record<11:04:27.000> which<11:04:27.720> you<11:04:28.080> probably 11:04:28.370 --> 11:04:28.380 align:start position:0% there's an MX record which you probably 11:04:28.380 --> 11:04:31.070 align:start position:0% there's an MX record which you probably won't<11:04:28.800> be<11:04:29.160> touching<11:04:29.580> unless<11:04:30.000> you're<11:04:30.300> doing 11:04:31.070 --> 11:04:31.080 align:start position:0% won't be touching unless you're doing 11:04:31.080 --> 11:04:32.690 align:start position:0% won't be touching unless you're doing your<11:04:31.380> own<11:04:31.500> mail<11:04:31.740> stuff 11:04:32.690 --> 11:04:32.700 align:start position:0% your own mail stuff 11:04:32.700 --> 11:04:34.370 align:start position:0% your own mail stuff to<11:04:33.120> Maps<11:04:33.480> the<11:04:33.540> domain<11:04:33.776> name<11:04:33.900> to<11:04:34.140> an<11:04:34.256> email 11:04:34.370 --> 11:04:34.380 align:start position:0% to Maps the domain name to an email 11:04:34.380 --> 11:04:36.350 align:start position:0% to Maps the domain name to an email server<11:04:35.340> if<11:04:35.700> you're<11:04:35.820> working<11:04:35.936> for<11:04:36.180> a<11:04:36.300> big 11:04:36.350 --> 11:04:36.360 align:start position:0% server if you're working for a big 11:04:36.360 --> 11:04:38.150 align:start position:0% server if you're working for a big company<11:04:36.596> they'll<11:04:37.020> take<11:04:37.200> care<11:04:37.380> of<11:04:37.500> that 11:04:38.150 --> 11:04:38.160 align:start position:0% company they'll take care of that 11:04:38.160 --> 11:04:39.766 align:start position:0% company they'll take care of that but<11:04:38.460> looking<11:04:38.580> at<11:04:38.756> the<11:04:38.880> MX<11:04:39.120> record<11:04:39.360> we<11:04:39.660> could 11:04:39.766 --> 11:04:39.776 align:start position:0% but looking at the MX record we could 11:04:39.776 --> 11:04:41.570 align:start position:0% but looking at the MX record we could identify<11:04:40.200> the<11:04:40.380> mail<11:04:40.500> server<11:04:40.980> to<11:04:41.160> which<11:04:41.340> the 11:04:41.570 --> 11:04:41.580 align:start position:0% identify the mail server to which the 11:04:41.580 --> 11:04:44.330 align:start position:0% identify the mail server to which the emails<11:04:42.120> are<11:04:42.240> sent 11:04:44.330 --> 11:04:44.340 align:start position:0% emails are sent 11:04:44.340 --> 11:04:48.710 align:start position:0% emails are sent uh<11:04:45.060> C<11:04:45.240> name<11:04:45.596> conical<11:04:46.560> name<11:04:47.220> record 11:04:48.710 --> 11:04:48.720 align:start position:0% uh C name conical name record 11:04:48.720 --> 11:04:50.390 align:start position:0% uh C name conical name record used<11:04:49.080> to<11:04:49.256> specify<11:04:49.680> a<11:04:49.860> domain<11:04:50.096> name<11:04:50.220> or 11:04:50.390 --> 11:04:50.400 align:start position:0% used to specify a domain name or 11:04:50.400 --> 11:04:54.710 align:start position:0% used to specify a domain name or subdomain<11:04:50.936> as<11:04:51.240> an<11:04:51.416> alias<11:04:51.900> of<11:04:52.436> another<11:04:53.160> domain 11:04:54.710 --> 11:04:54.720 align:start position:0% subdomain as an alias of another domain 11:04:54.720 --> 11:04:57.230 align:start position:0% subdomain as an alias of another domain so<11:04:55.200> it<11:04:55.320> allows<11:04:55.800> the<11:04:55.980> mapping<11:04:56.276> of<11:04:56.400> a<11:04:56.580> domain<11:04:56.880> to 11:04:57.230 --> 11:04:57.240 align:start position:0% so it allows the mapping of a domain to 11:04:57.240 --> 11:04:59.330 align:start position:0% so it allows the mapping of a domain to another<11:04:57.480> domain 11:04:59.330 --> 11:04:59.340 align:start position:0% another domain 11:04:59.340 --> 11:05:01.490 align:start position:0% another domain so<11:04:59.880> for<11:05:00.180> example 11:05:01.490 --> 11:05:01.500 align:start position:0% so for example 11:05:01.500 --> 11:05:02.570 align:start position:0% so for example um 11:05:02.570 --> 11:05:02.580 align:start position:0% um 11:05:02.580 --> 11:05:04.970 align:start position:0% um you<11:05:03.060> complete<11:05:03.540> subdomains<11:05:04.140> such<11:05:04.380> as<11:05:04.500> the<11:05:04.800> mail 11:05:04.970 --> 11:05:04.980 align:start position:0% you complete subdomains such as the mail 11:05:04.980 --> 11:05:08.926 align:start position:0% you complete subdomains such as the mail or<11:05:05.460> your<11:05:05.640> FTP<11:05:06.240> to<11:05:07.080> your<11:05:07.380> main<11:05:07.620> address<11:05:07.916> and<11:05:08.756> you 11:05:08.926 --> 11:05:08.936 align:start position:0% or your FTP to your main address and you 11:05:08.936 --> 11:05:10.190 align:start position:0% or your FTP to your main address and you can<11:05:09.000> do<11:05:09.120> you<11:05:09.360> could<11:05:09.416> do<11:05:09.596> this<11:05:09.720> to<11:05:09.960> make<11:05:10.080> your 11:05:10.190 --> 11:05:10.200 align:start position:0% can do you could do this to make your 11:05:10.200 --> 11:05:12.110 align:start position:0% can do you could do this to make your company<11:05:10.620> look<11:05:10.916> bigger 11:05:12.110 --> 11:05:12.120 align:start position:0% company look bigger 11:05:12.120 --> 11:05:15.586 align:start position:0% company look bigger and<11:05:12.900> I<11:05:13.320> think<11:05:13.500> my<11:05:14.040> FTP<11:05:14.520> certainly<11:05:14.936> just<11:05:15.180> points 11:05:15.586 --> 11:05:15.596 align:start position:0% and I think my FTP certainly just points 11:05:15.596 --> 11:05:19.370 align:start position:0% and I think my FTP certainly just points to<11:05:15.720> my<11:05:16.140> my<11:05:16.740> normal<11:05:17.040> server 11:05:19.370 --> 11:05:19.380 align:start position:0% to my my normal server 11:05:19.380 --> 11:05:21.890 align:start position:0% to my my normal server yeah<11:05:19.980> but<11:05:20.220> obviously<11:05:20.820> when<11:05:21.060> you're<11:05:21.180> doing<11:05:21.300> FTP 11:05:21.890 --> 11:05:21.900 align:start position:0% yeah but obviously when you're doing FTP 11:05:21.900 --> 11:05:24.050 align:start position:0% yeah but obviously when you're doing FTP you<11:05:22.140> need<11:05:22.256> to<11:05:22.380> specify 11:05:24.050 --> 11:05:24.060 align:start position:0% you need to specify 11:05:24.060 --> 11:05:26.746 align:start position:0% you need to specify um<11:05:24.120> in<11:05:24.660> your<11:05:24.900> software<11:05:25.380> that<11:05:25.740> you're<11:05:26.040> using 11:05:26.746 --> 11:05:26.756 align:start position:0% um in your software that you're using 11:05:26.756 --> 11:05:29.330 align:start position:0% um in your software that you're using FTP<11:05:27.240> so<11:05:27.480> this<11:05:27.840> that<11:05:28.140> was<11:05:28.320> that's<11:05:28.680> how<11:05:28.980> it<11:05:29.160> would 11:05:29.330 --> 11:05:29.340 align:start position:0% FTP so this that was that's how it would 11:05:29.340 --> 11:05:30.766 align:start position:0% FTP so this that was that's how it would work 11:05:30.766 --> 11:05:30.776 align:start position:0% work 11:05:30.776 --> 11:05:32.210 align:start position:0% work so<11:05:30.840> there<11:05:31.200> must<11:05:31.320> be<11:05:31.436> an<11:05:31.620> a<11:05:31.680> record<11:05:31.860> for<11:05:32.096> the 11:05:32.210 --> 11:05:32.220 align:start position:0% so there must be an a record for the 11:05:32.220 --> 11:05:34.790 align:start position:0% so there must be an a record for the hosting<11:05:32.580> server<11:05:33.000> before<11:05:33.480> aliases<11:05:34.436> can<11:05:34.620> be 11:05:34.790 --> 11:05:34.800 align:start position:0% hosting server before aliases can be 11:05:34.800 --> 11:05:36.890 align:start position:0% hosting server before aliases can be added 11:05:36.890 --> 11:05:36.900 align:start position:0% added 11:05:36.900 --> 11:05:39.586 align:start position:0% added so<11:05:37.436> cname<11:05:38.040> aliases<11:05:38.520> must<11:05:39.000> point<11:05:39.240> to<11:05:39.416> another 11:05:39.586 --> 11:05:39.596 align:start position:0% so cname aliases must point to another 11:05:39.596 --> 11:05:40.790 align:start position:0% so cname aliases must point to another domain 11:05:40.790 --> 11:05:40.800 align:start position:0% domain 11:05:40.800 --> 11:05:43.070 align:start position:0% domain so<11:05:41.276> if<11:05:41.460> somebody<11:05:41.640> types 11:05:43.070 --> 11:05:43.080 align:start position:0% so if somebody types 11:05:43.080 --> 11:05:43.990 align:start position:0% so if somebody types um 11:05:43.990 --> 11:05:44.000 align:start position:0% um 11:05:44.000 --> 11:05:47.630 align:start position:0% um bar.example.com<11:05:45.000> there's<11:05:45.960> a<11:05:46.200> cname<11:05:46.860> record 11:05:47.630 --> 11:05:47.640 align:start position:0% bar.example.com there's a cname record 11:05:47.640 --> 11:05:51.650 align:start position:0% bar.example.com there's a cname record that<11:05:48.416> basically<11:05:48.776> says<11:05:49.200> that<11:05:50.040> is<11:05:50.220> actually<11:05:50.520> on 11:05:51.650 --> 11:05:51.660 align:start position:0% that basically says that is actually on 11:05:51.660 --> 11:05:53.030 align:start position:0% that basically says that is actually on um 11:05:53.030 --> 11:05:53.040 align:start position:0% um 11:05:53.040 --> 11:05:56.746 align:start position:0% um the<11:05:53.580> C<11:05:53.756> name<11:05:54.000> is<11:05:54.140> food.example.com<11:05:55.220> then<11:05:56.220> the 11:05:56.746 --> 11:05:56.756 align:start position:0% the C name is food.example.com then the 11:05:56.756 --> 11:05:59.030 align:start position:0% the C name is food.example.com then the the<11:05:57.060> search<11:05:57.360> takes<11:05:57.840> place<11:05:58.020> the<11:05:58.436> DNS<11:05:58.800> search 11:05:59.030 --> 11:05:59.040 align:start position:0% the search takes place the DNS search 11:05:59.040 --> 11:06:02.510 align:start position:0% the search takes place the DNS search takes<11:05:59.460> place<11:05:59.640> for<11:06:00.436> food.example.com<11:06:01.520> there's 11:06:02.510 --> 11:06:02.520 align:start position:0% takes place for food.example.com there's 11:06:02.520 --> 11:06:06.710 align:start position:0% takes place for food.example.com there's an<11:06:02.640> a<11:06:02.820> record<11:06:03.120> so<11:06:03.840> IP<11:06:04.500> B4<11:06:05.340> record<11:06:05.700> and<11:06:06.596> it's 11:06:06.710 --> 11:06:06.720 align:start position:0% an a record so IP B4 record and it's 11:06:06.720 --> 11:06:09.290 align:start position:0% an a record so IP B4 record and it's saying<11:06:07.080> yeah<11:06:07.256> this<11:06:07.680> is<11:06:07.880> posted<11:06:08.880> on<11:06:09.000> this 11:06:09.290 --> 11:06:09.300 align:start position:0% saying yeah this is posted on this 11:06:09.300 --> 11:06:13.010 align:start position:0% saying yeah this is posted on this particular<11:06:09.596> server 11:06:13.010 --> 11:06:13.020 align:start position:0% 11:06:13.020 --> 11:06:17.030 align:start position:0% PTR<11:06:13.680> records<11:06:14.520> pointers<11:06:15.416> Maps<11:06:16.140> like<11:06:16.320> pv4 11:06:17.030 --> 11:06:17.040 align:start position:0% PTR records pointers Maps like pv4 11:06:17.040 --> 11:06:18.890 align:start position:0% PTR records pointers Maps like pv4 address<11:06:17.220> to<11:06:17.580> a<11:06:17.756> clinical<11:06:18.240> name<11:06:18.540> for<11:06:18.776> the 11:06:18.890 --> 11:06:18.900 align:start position:0% address to a clinical name for the 11:06:18.900 --> 11:06:21.890 align:start position:0% address to a clinical name for the purposes<11:06:19.200> of<11:06:19.560> the<11:06:19.740> reverse<11:06:20.096> DNS<11:06:20.640> lookup 11:06:21.890 --> 11:06:21.900 align:start position:0% purposes of the reverse DNS lookup 11:06:21.900 --> 11:06:24.830 align:start position:0% purposes of the reverse DNS lookup so<11:06:22.500> this<11:06:22.800> is<11:06:23.096> uh<11:06:23.276> the<11:06:23.580> reverse<11:06:23.880> so<11:06:24.120> normally<11:06:24.416> we 11:06:24.830 --> 11:06:24.840 align:start position:0% so this is uh the reverse so normally we 11:06:24.840 --> 11:06:25.970 align:start position:0% so this is uh the reverse so normally we do 11:06:25.970 --> 11:06:25.980 align:start position:0% do 11:06:25.980 --> 11:06:27.610 align:start position:0% do um 11:06:27.610 --> 11:06:27.620 align:start position:0% um 11:06:27.620 --> 11:06:33.890 align:start position:0% um xyz.com<11:06:28.756> and<11:06:29.756> that<11:06:29.880> goes<11:06:30.300> to 11:06:33.890 --> 11:06:33.900 align:start position:0% 11:06:33.900 --> 11:06:35.870 align:start position:0% but<11:06:34.500> the<11:06:34.740> reverse<11:06:35.096> can<11:06:35.340> happen<11:06:35.520> somebody 11:06:35.870 --> 11:06:35.880 align:start position:0% but the reverse can happen somebody 11:06:35.880 --> 11:06:37.266 align:start position:0% but the reverse can happen somebody could<11:06:36.240> type 11:06:37.266 --> 11:06:37.276 align:start position:0% could type 11:06:37.276 --> 11:06:39.650 align:start position:0% could type 192.1.1.1<11:06:38.276> when<11:06:38.820> you<11:06:38.936> type<11:06:39.120> that<11:06:39.300> in<11:06:39.480> your 11:06:39.650 --> 11:06:39.660 align:start position:0% 192.1.1.1 when you type that in your 11:06:39.660 --> 11:06:42.830 align:start position:0% 192.1.1.1 when you type that in your browser<11:06:40.200> I<11:06:40.916> think 11:06:42.830 --> 11:06:42.840 align:start position:0% browser I think 11:06:42.840 --> 11:06:45.050 align:start position:0% browser I think you<11:06:44.096> um 11:06:45.050 --> 11:06:45.060 align:start position:0% you um 11:06:45.060 --> 11:06:47.330 align:start position:0% you um I<11:06:45.416> need<11:06:45.596> to<11:06:45.720> test<11:06:45.900> that<11:06:46.080> actually 11:06:47.330 --> 11:06:47.340 align:start position:0% I need to test that actually 11:06:47.340 --> 11:06:49.906 align:start position:0% I need to test that actually it<11:06:47.756> won't<11:06:47.936> stay<11:06:48.180> so<11:06:48.416> if<11:06:48.540> you<11:06:48.840> if<11:06:49.256> you<11:06:49.436> type<11:06:49.620> that 11:06:49.906 --> 11:06:49.916 align:start position:0% it won't stay so if you if you type that 11:06:49.916 --> 11:06:52.190 align:start position:0% it won't stay so if you if you type that you<11:06:50.400> may<11:06:50.520> well<11:06:50.756> see<11:06:51.000> it<11:06:51.180> actually<11:06:51.416> resolves<11:06:52.020> to 11:06:52.190 --> 11:06:52.200 align:start position:0% you may well see it actually resolves to 11:06:52.200 --> 11:06:53.030 align:start position:0% you may well see it actually resolves to this 11:06:53.030 --> 11:06:53.040 align:start position:0% this 11:06:53.040 --> 11:06:56.030 align:start position:0% this might<11:06:53.460> depend<11:06:53.756> on<11:06:53.880> your<11:06:54.060> browser<11:06:54.480> software 11:06:56.030 --> 11:06:56.040 align:start position:0% might depend on your browser software 11:06:56.040 --> 11:06:58.850 align:start position:0% might depend on your browser software SOA<11:06:56.936> State<11:06:57.300> start<11:06:57.596> of<11:06:57.840> authority<11:06:58.200> record<11:06:58.436> it's 11:06:58.850 --> 11:06:58.860 align:start position:0% SOA State start of authority record it's 11:06:58.860 --> 11:07:01.426 align:start position:0% SOA State start of authority record it's the<11:06:59.096> first<11:06:59.220> record<11:06:59.460> in<11:06:59.820> the<11:07:00.000> zone<11:07:00.240> file<11:07:00.540> it 11:07:01.426 --> 11:07:01.436 align:start position:0% the first record in the zone file it 11:07:01.436 --> 11:07:03.290 align:start position:0% the first record in the zone file it declares<11:07:01.916> it<11:07:02.276> contains<11:07:02.640> the<11:07:02.936> most 11:07:03.290 --> 11:07:03.300 align:start position:0% declares it contains the most 11:07:03.300 --> 11:07:09.470 align:start position:0% declares it contains the most authoritative<11:07:03.960> information<11:07:04.756> for<11:07:05.756> the<11:07:05.936> zone 11:07:09.470 --> 11:07:09.480 align:start position:0% 11:07:09.480 --> 11:07:12.010 align:start position:0% information<11:07:10.140> is<11:07:10.680> the<11:07:10.860> email<11:07:10.980> address<11:07:11.276> of<11:07:11.640> the 11:07:12.010 --> 11:07:12.020 align:start position:0% information is the email address of the 11:07:12.020 --> 11:07:13.970 align:start position:0% information is the email address of the administrator<11:07:13.020> you<11:07:13.380> normally<11:07:13.620> have<11:07:13.740> to<11:07:13.860> put 11:07:13.970 --> 11:07:13.980 align:start position:0% administrator you normally have to put 11:07:13.980 --> 11:07:15.350 align:start position:0% administrator you normally have to put something<11:07:14.220> in<11:07:14.460> unless<11:07:14.756> you<11:07:14.880> want<11:07:15.000> it<11:07:15.120> to<11:07:15.240> be 11:07:15.350 --> 11:07:15.360 align:start position:0% something in unless you want it to be 11:07:15.360 --> 11:07:18.110 align:start position:0% something in unless you want it to be private<11:07:15.840> the<11:07:16.800> name<11:07:16.980> of<11:07:17.160> the<11:07:17.340> primary<11:07:17.640> DNS 11:07:18.110 --> 11:07:18.120 align:start position:0% private the name of the primary DNS 11:07:18.120 --> 11:07:20.926 align:start position:0% private the name of the primary DNS server<11:07:18.540> there's<11:07:18.960> a<11:07:19.140> serial<11:07:19.436> number<11:07:19.936> time 11:07:20.926 --> 11:07:20.936 align:start position:0% server there's a serial number time 11:07:20.936 --> 11:07:22.970 align:start position:0% server there's a serial number time Fields<11:07:21.416> when<11:07:21.540> it<11:07:21.660> was<11:07:21.776> all<11:07:21.900> registered<11:07:22.380> and<11:07:22.680> on 11:07:22.970 --> 11:07:22.980 align:start position:0% Fields when it was all registered and on 11:07:22.980 --> 11:07:25.310 align:start position:0% Fields when it was all registered and on their<11:07:23.160> last<11:07:23.340> updates 11:07:25.310 --> 11:07:25.320 align:start position:0% their last updates 11:07:25.320 --> 11:07:27.650 align:start position:0% their last updates uh<11:07:25.680> two<11:07:25.860> of<11:07:25.980> the<11:07:26.096> types<11:07:26.460> of<11:07:26.640> Records<11:07:27.120> static<11:07:27.480> is 11:07:27.650 --> 11:07:27.660 align:start position:0% uh two of the types of Records static is 11:07:27.660 --> 11:07:30.050 align:start position:0% uh two of the types of Records static is when<11:07:27.840> it's<11:07:28.080> done<11:07:28.320> manually 11:07:30.050 --> 11:07:30.060 align:start position:0% when it's done manually 11:07:30.060 --> 11:07:33.350 align:start position:0% when it's done manually here<11:07:30.660> and<11:07:31.140> dynamic<11:07:31.740> it's<11:07:32.700> automatically 11:07:33.350 --> 11:07:33.360 align:start position:0% here and dynamic it's automatically 11:07:33.360 --> 11:07:37.906 align:start position:0% here and dynamic it's automatically updated<11:07:33.776> there's<11:07:34.200> two<11:07:34.500> types<11:07:34.740> of<11:07:34.860> Records 11:07:37.906 --> 11:07:37.916 align:start position:0% 11:07:37.916 --> 11:07:42.350 align:start position:0% and<11:07:38.756> Dynamic<11:07:39.480> DNS<11:07:40.020> this<11:07:40.620> is<11:07:40.740> a<11:07:41.460> process<11:07:42.120> of 11:07:42.350 --> 11:07:42.360 align:start position:0% and Dynamic DNS this is a process of 11:07:42.360 --> 11:07:43.730 align:start position:0% and Dynamic DNS this is a process of automatically 11:07:43.730 --> 11:07:43.740 align:start position:0% automatically 11:07:43.740 --> 11:07:46.490 align:start position:0% automatically um<11:07:43.800> updating<11:07:44.220> a<11:07:45.000> Dynamic<11:07:45.540> DNS<11:07:45.900> record<11:07:46.080> in<11:07:46.320> the 11:07:46.490 --> 11:07:46.500 align:start position:0% um updating a Dynamic DNS record in the 11:07:46.500 --> 11:07:48.890 align:start position:0% um updating a Dynamic DNS record in the name<11:07:46.560> server<11:07:47.040> what<11:07:47.936> can<11:07:48.060> happen<11:07:48.240> is<11:07:48.480> this<11:07:48.776> is 11:07:48.890 --> 11:07:48.900 align:start position:0% name server what can happen is this is 11:07:48.900 --> 11:07:51.406 align:start position:0% name server what can happen is this is all<11:07:49.140> almost 11:07:51.406 --> 11:07:51.416 align:start position:0% all almost 11:07:51.416 --> 11:07:53.570 align:start position:0% all almost in<11:07:52.140> real<11:07:52.320> time 11:07:53.570 --> 11:07:53.580 align:start position:0% in real time 11:07:53.580 --> 11:07:57.010 align:start position:0% in real time could<11:07:54.060> well<11:07:54.240> be<11:07:54.416> used<11:07:54.660> if<11:07:55.080> you're<11:07:55.380> using<11:07:56.096> cloud 11:07:57.010 --> 11:07:57.020 align:start position:0% could well be used if you're using cloud 11:07:57.020 --> 11:08:00.730 align:start position:0% could well be used if you're using cloud computing<11:07:58.020> and<11:07:58.320> your<11:07:59.160> setting<11:07:59.880> up<11:08:00.000> servers 11:08:00.730 --> 11:08:00.740 align:start position:0% computing and your setting up servers 11:08:00.740 --> 11:08:04.570 align:start position:0% computing and your setting up servers tearing<11:08:01.740> down<11:08:01.916> servers<11:08:02.776> moving<11:08:03.776> information 11:08:04.570 --> 11:08:04.580 align:start position:0% tearing down servers moving information 11:08:04.580 --> 11:08:08.570 align:start position:0% tearing down servers moving information Dynamic<11:08:05.580> DNS 11:08:08.570 --> 11:08:08.580 align:start position:0% 11:08:08.580 --> 11:08:11.926 align:start position:0% will<11:08:08.936> update<11:08:09.360> the<11:08:09.720> lap<11:08:10.020> information<11:08:10.400> and<11:08:11.400> the 11:08:11.926 --> 11:08:11.936 align:start position:0% will update the lap information and the 11:08:11.936 --> 11:08:17.990 align:start position:0% will update the lap information and the um names 11:08:17.990 --> 11:08:18.000 align:start position:0% 11:08:18.000 --> 11:08:20.086 align:start position:0% so<11:08:18.416> useful<11:08:18.720> when<11:08:18.900> the<11:08:19.020> IP<11:08:19.256> addresses<11:08:19.740> of<11:08:19.916> our 11:08:20.086 --> 11:08:20.096 align:start position:0% so useful when the IP addresses of our 11:08:20.096 --> 11:08:24.950 align:start position:0% so useful when the IP addresses of our devices<11:08:20.400> keep<11:08:20.756> changing 11:08:24.950 --> 11:08:24.960 align:start position:0% 11:08:24.960 --> 11:08:27.710 align:start position:0% uh<11:08:25.680> whenever<11:08:26.040> a<11:08:26.160> client<11:08:26.340> computer<11:08:26.520> using<11:08:27.060> DHCP 11:08:27.710 --> 11:08:27.720 align:start position:0% uh whenever a client computer using DHCP 11:08:27.720 --> 11:08:29.690 align:start position:0% uh whenever a client computer using DHCP gets<11:08:28.080> a<11:08:28.080> new<11:08:28.256> IP<11:08:28.500> address<11:08:28.620> it<11:08:28.916> can<11:08:29.096> use<11:08:29.220> Dynamic 11:08:29.690 --> 11:08:29.700 align:start position:0% gets a new IP address it can use Dynamic 11:08:29.700 --> 11:08:31.790 align:start position:0% gets a new IP address it can use Dynamic DNS 11:08:31.790 --> 11:08:31.800 align:start position:0% DNS 11:08:31.800 --> 11:08:33.170 align:start position:0% DNS all<11:08:32.040> right<11:08:32.096> so<11:08:32.220> we<11:08:32.340> covered<11:08:32.640> a<11:08:32.756> lot<11:08:32.880> of<11:08:33.000> stuff 11:08:33.170 --> 11:08:33.180 align:start position:0% all right so we covered a lot of stuff 11:08:33.180 --> 11:08:35.510 align:start position:0% all right so we covered a lot of stuff you<11:08:33.720> know<11:08:33.900> the<11:08:34.140> core<11:08:34.320> stuff<11:08:34.680> about<11:08:35.040> root 11:08:35.510 --> 11:08:35.520 align:start position:0% you know the core stuff about root 11:08:35.520 --> 11:08:38.210 align:start position:0% you know the core stuff about root servers<11:08:36.000> and<11:08:36.416> AE<11:08:36.776> records<11:08:37.256> and<11:08:37.436> quadruple<11:08:37.980> a 11:08:38.210 --> 11:08:38.220 align:start position:0% servers and AE records and quadruple a 11:08:38.220 --> 11:08:40.010 align:start position:0% servers and AE records and quadruple a records<11:08:38.700> I<11:08:38.936> think<11:08:39.120> that's<11:08:39.416> the<11:08:39.660> type<11:08:39.776> of<11:08:39.840> stuff 11:08:40.010 --> 11:08:40.020 align:start position:0% records I think that's the type of stuff 11:08:40.020 --> 11:08:42.310 align:start position:0% records I think that's the type of stuff that<11:08:40.140> has<11:08:40.320> questions<11:08:40.560> on 11:08:42.310 --> 11:08:42.320 align:start position:0% that has questions on 11:08:42.320 --> 11:08:45.950 align:start position:0% that has questions on DNS<11:08:43.320> domains<11:08:44.040> fully<11:08:44.520> quite<11:08:44.820> fully<11:08:45.596> qualified 11:08:45.950 --> 11:08:45.960 align:start position:0% DNS domains fully quite fully qualified 11:08:45.960 --> 11:08:50.086 align:start position:0% DNS domains fully quite fully qualified domains<11:08:46.560> root<11:08:47.096> servers<11:08:47.900> records<11:08:48.900> a<11:08:49.860> lot<11:08:49.980> of 11:08:50.086 --> 11:08:50.096 align:start position:0% domains root servers records a lot of 11:08:50.096 --> 11:08:55.280 align:start position:0% domains root servers records a lot of information<11:08:50.276> and<11:08:50.936> thanks<11:08:51.120> for<11:08:51.300> watching 11:08:55.280 --> 11:08:55.290 align:start position:0% 11:08:55.290 --> 11:09:03.730 align:start position:0% [Music] 11:09:03.730 --> 11:09:03.740 align:start position:0% [Music] 11:09:03.740 --> 11:09:11.450 align:start position:0% [Music] thank<11:09:04.740> you 11:09:11.450 --> 11:09:11.460 align:start position:0% 11:09:11.460 --> 11:09:14.210 align:start position:0% welcome<11:09:11.936> to<11:09:12.180> module<11:09:12.540> 6<11:09:12.660> lesson<11:09:13.200> 7<11:09:13.380> proxy 11:09:14.210 --> 11:09:14.220 align:start position:0% welcome to module 6 lesson 7 proxy 11:09:14.220 --> 11:09:17.746 align:start position:0% welcome to module 6 lesson 7 proxy servers 11:09:17.746 --> 11:09:17.756 align:start position:0% 11:09:17.756 --> 11:09:19.610 align:start position:0% objectives<11:09:18.540> we're<11:09:18.776> looking<11:09:18.900> at<11:09:19.080> what<11:09:19.200> a<11:09:19.320> proxy 11:09:19.610 --> 11:09:19.620 align:start position:0% objectives we're looking at what a proxy 11:09:19.620 --> 11:09:23.210 align:start position:0% objectives we're looking at what a proxy server<11:09:20.040> is<11:09:20.276> an<11:09:20.756> introduction<11:09:21.436> uh<11:09:22.436> the<11:09:22.740> uses<11:09:23.040> of 11:09:23.210 --> 11:09:23.220 align:start position:0% server is an introduction uh the uses of 11:09:23.220 --> 11:09:26.086 align:start position:0% server is an introduction uh the uses of proxy<11:09:23.640> servers<11:09:24.120> and<11:09:24.720> forward<11:09:24.960> proxy<11:09:25.560> servers 11:09:26.086 --> 11:09:26.096 align:start position:0% proxy servers and forward proxy servers 11:09:26.096 --> 11:09:28.906 align:start position:0% proxy servers and forward proxy servers reverse<11:09:26.700> proxy<11:09:27.300> servers 11:09:28.906 --> 11:09:28.916 align:start position:0% reverse proxy servers 11:09:28.916 --> 11:09:30.950 align:start position:0% reverse proxy servers so<11:09:29.700> you<11:09:29.936> may<11:09:30.060> have<11:09:30.180> actually<11:09:30.300> heard<11:09:30.540> of<11:09:30.720> these 11:09:30.950 --> 11:09:30.960 align:start position:0% so you may have actually heard of these 11:09:30.960 --> 11:09:32.630 align:start position:0% so you may have actually heard of these before<11:09:31.140> especially<11:09:31.680> if<11:09:31.860> you've<11:09:32.040> worked<11:09:32.340> in<11:09:32.460> an 11:09:32.630 --> 11:09:32.640 align:start position:0% before especially if you've worked in an 11:09:32.640 --> 11:09:34.550 align:start position:0% before especially if you've worked in an office<11:09:32.880> whereby 11:09:34.550 --> 11:09:34.560 align:start position:0% office whereby 11:09:34.560 --> 11:09:36.710 align:start position:0% office whereby instead<11:09:35.220> of<11:09:35.340> connecting<11:09:35.880> directly<11:09:36.360> out<11:09:36.540> to 11:09:36.710 --> 11:09:36.720 align:start position:0% instead of connecting directly out to 11:09:36.720 --> 11:09:38.630 align:start position:0% instead of connecting directly out to the<11:09:36.840> internet<11:09:37.020> your<11:09:37.800> settings<11:09:38.040> will<11:09:38.460> be 11:09:38.630 --> 11:09:38.640 align:start position:0% the internet your settings will be 11:09:38.640 --> 11:09:40.906 align:start position:0% the internet your settings will be searched<11:09:39.180> that<11:09:39.300> you'll<11:09:40.020> connect<11:09:40.140> to<11:09:40.380> a<11:09:40.560> proxy 11:09:40.906 --> 11:09:40.916 align:start position:0% searched that you'll connect to a proxy 11:09:40.916 --> 11:09:43.246 align:start position:0% searched that you'll connect to a proxy server<11:09:41.340> especially 11:09:43.246 --> 11:09:43.256 align:start position:0% server especially 11:09:43.256 --> 11:09:46.426 align:start position:0% server especially um<11:09:43.320> for<11:09:43.560> getting<11:09:43.740> out<11:09:43.980> to<11:09:44.776> surfing<11:09:45.776> websites 11:09:46.426 --> 11:09:46.436 align:start position:0% um for getting out to surfing websites 11:09:46.436 --> 11:09:49.010 align:start position:0% um for getting out to surfing websites the<11:09:47.096> proxy<11:09:47.520> server<11:09:47.880> will<11:09:48.120> do<11:09:48.360> a<11:09:48.540> few<11:09:48.720> things 11:09:49.010 --> 11:09:49.020 align:start position:0% the proxy server will do a few things 11:09:49.020 --> 11:09:53.086 align:start position:0% the proxy server will do a few things which<11:09:49.980> we'll<11:09:50.220> look<11:09:50.700> at<11:09:50.756> in<11:09:50.880> a<11:09:51.060> bit 11:09:53.086 --> 11:09:53.096 align:start position:0% which we'll look at in a bit 11:09:53.096 --> 11:09:56.746 align:start position:0% which we'll look at in a bit so<11:09:53.520> it's<11:09:53.640> in<11:09:53.936> a<11:09:54.360> mediator<11:09:55.320> or<11:09:55.860> an<11:09:56.096> intermediary 11:09:56.746 --> 11:09:56.756 align:start position:0% so it's in a mediator or an intermediary 11:09:56.756 --> 11:10:00.710 align:start position:0% so it's in a mediator or an intermediary between<11:09:57.240> you<11:09:57.776> and<11:09:58.380> some<11:09:58.560> other<11:09:58.740> service 11:10:00.710 --> 11:10:00.720 align:start position:0% between you and some other service 11:10:00.720 --> 11:10:02.450 align:start position:0% between you and some other service you've<11:10:01.200> got<11:10:01.320> the<11:10:01.500> client<11:10:01.620> computer<11:10:01.916> the 11:10:02.450 --> 11:10:02.460 align:start position:0% you've got the client computer the 11:10:02.460 --> 11:10:03.950 align:start position:0% you've got the client computer the destination<11:10:02.820> server<11:10:03.360> and<11:10:03.596> then<11:10:03.720> obviously 11:10:03.950 --> 11:10:03.960 align:start position:0% destination server and then obviously 11:10:03.960 --> 11:10:05.510 align:start position:0% destination server and then obviously the<11:10:04.080> proxy<11:10:04.436> in<11:10:04.620> the<11:10:04.740> middle 11:10:05.510 --> 11:10:05.520 align:start position:0% the proxy in the middle 11:10:05.520 --> 11:10:08.030 align:start position:0% the proxy in the middle here's<11:10:06.180> an<11:10:06.416> illustration<11:10:06.960> here<11:10:07.380> which<11:10:07.860> we'll 11:10:08.030 --> 11:10:08.040 align:start position:0% here's an illustration here which we'll 11:10:08.040 --> 11:10:10.970 align:start position:0% here's an illustration here which we'll talk<11:10:08.276> about<11:10:08.400> the<11:10:08.700> caching<11:10:09.060> and<11:10:09.180> web<11:10:09.360> filter<11:10:09.596> in 11:10:10.970 --> 11:10:10.980 align:start position:0% talk about the caching and web filter in 11:10:10.980 --> 11:10:15.650 align:start position:0% talk about the caching and web filter in so<11:10:11.640> it's<11:10:12.540> mainly<11:10:13.080> uh<11:10:13.860> used<11:10:14.220> for<11:10:14.756> uh<11:10:15.180> surfing 11:10:15.650 --> 11:10:15.660 align:start position:0% so it's mainly uh used for uh surfing 11:10:15.660 --> 11:10:17.690 align:start position:0% so it's mainly uh used for uh surfing when<11:10:16.380> you<11:10:16.500> want<11:10:16.620> to<11:10:16.740> go<11:10:16.800> out<11:10:16.916> and<11:10:17.040> surf<11:10:17.400> the<11:10:17.520> web 11:10:17.690 --> 11:10:17.700 align:start position:0% when you want to go out and surf the web 11:10:17.700 --> 11:10:20.870 align:start position:0% when you want to go out and surf the web for<11:10:17.936> whatever<11:10:18.180> reason<11:10:18.560> it<11:10:19.560> can<11:10:19.740> then<11:10:20.040> filter 11:10:20.870 --> 11:10:20.880 align:start position:0% for whatever reason it can then filter 11:10:20.880 --> 11:10:24.290 align:start position:0% for whatever reason it can then filter what<11:10:21.540> sites<11:10:21.960> you<11:10:22.080> can<11:10:22.256> and<11:10:22.500> can't<11:10:22.936> connect<11:10:23.936> to 11:10:24.290 --> 11:10:24.300 align:start position:0% what sites you can and can't connect to 11:10:24.300 --> 11:10:26.150 align:start position:0% what sites you can and can't connect to it's<11:10:25.560> um 11:10:26.150 --> 11:10:26.160 align:start position:0% it's um 11:10:26.160 --> 11:10:28.610 align:start position:0% it's um caches<11:10:27.000> some<11:10:27.240> of<11:10:27.360> the<11:10:27.480> content<11:10:27.776> so<11:10:28.020> it's<11:10:28.200> got<11:10:28.436> a 11:10:28.610 --> 11:10:28.620 align:start position:0% caches some of the content so it's got a 11:10:28.620 --> 11:10:32.746 align:start position:0% caches some of the content so it's got a copy<11:10:29.340> of<11:10:30.060> regularly<11:10:30.540> visited<11:10:31.620> our<11:10:32.220> websites 11:10:32.746 --> 11:10:32.756 align:start position:0% copy of regularly visited our websites 11:10:32.756 --> 11:10:34.550 align:start position:0% copy of regularly visited our websites to<11:10:33.000> speed<11:10:33.180> up<11:10:33.416> the<11:10:34.020> um 11:10:34.550 --> 11:10:34.560 align:start position:0% to speed up the um 11:10:34.560 --> 11:10:38.510 align:start position:0% to speed up the um the<11:10:35.220> surfing<11:10:35.580> experience<11:10:36.060> for<11:10:36.660> you 11:10:38.510 --> 11:10:38.520 align:start position:0% the surfing experience for you 11:10:38.520 --> 11:10:40.550 align:start position:0% the surfing experience for you makes<11:10:38.936> requests<11:10:39.416> on<11:10:39.720> behalf<11:10:40.080> of<11:10:40.256> the<11:10:40.436> client 11:10:40.550 --> 11:10:40.560 align:start position:0% makes requests on behalf of the client 11:10:40.560 --> 11:10:42.830 align:start position:0% makes requests on behalf of the client computer<11:10:40.916> so<11:10:41.400> you're<11:10:41.756> sending<11:10:42.416> the<11:10:42.540> request 11:10:42.830 --> 11:10:42.840 align:start position:0% computer so you're sending the request 11:10:42.840 --> 11:10:44.690 align:start position:0% computer so you're sending the request out<11:10:43.256> to<11:10:43.500> you<11:10:43.740> to<11:10:43.860> what<11:10:44.096> you<11:10:44.220> think<11:10:44.340> is<11:10:44.520> the 11:10:44.690 --> 11:10:44.700 align:start position:0% out to you to what you think is the 11:10:44.700 --> 11:10:46.730 align:start position:0% out to you to what you think is the internet<11:10:44.756> but<11:10:45.180> it's<11:10:45.300> going<11:10:45.416> to<11:10:45.540> the<11:10:45.660> proxy<11:10:46.140> and 11:10:46.730 --> 11:10:46.740 align:start position:0% internet but it's going to the proxy and 11:10:46.740 --> 11:10:48.830 align:start position:0% internet but it's going to the proxy and then<11:10:46.800> the<11:10:46.916> proxy<11:10:47.220> design<11:10:47.400> your<11:10:47.756> behalf<11:10:48.180> the 11:10:48.830 --> 11:10:48.840 align:start position:0% then the proxy design your behalf the 11:10:48.840 --> 11:10:50.810 align:start position:0% then the proxy design your behalf the proxy<11:10:49.200> receives<11:10:49.560> a<11:10:49.800> response<11:10:50.220> from<11:10:50.400> whichever 11:10:50.810 --> 11:10:50.820 align:start position:0% proxy receives a response from whichever 11:10:50.820 --> 11:10:52.550 align:start position:0% proxy receives a response from whichever server<11:10:51.300> say<11:10:51.596> the<11:10:51.720> web<11:10:51.900> server<11:10:52.200> on<11:10:52.436> the 11:10:52.550 --> 11:10:52.560 align:start position:0% server say the web server on the 11:10:52.560 --> 11:10:54.230 align:start position:0% server say the web server on the internet<11:10:52.740> and<11:10:53.460> then<11:10:53.580> sends<11:10:53.936> that<11:10:54.000> information 11:10:54.230 --> 11:10:54.240 align:start position:0% internet and then sends that information 11:10:54.240 --> 11:10:58.246 align:start position:0% internet and then sends that information back<11:10:54.720> to<11:10:54.960> you 11:10:58.246 --> 11:10:58.256 align:start position:0% 11:10:58.256 --> 11:11:00.950 align:start position:0% so<11:10:58.916> it<11:10:59.460> intercepts<11:11:00.300> the<11:11:00.540> communication 11:11:00.950 --> 11:11:00.960 align:start position:0% so it intercepts the communication 11:11:00.960 --> 11:11:02.810 align:start position:0% so it intercepts the communication between<11:11:01.256> the<11:11:01.620> client's<11:11:01.980> computer<11:11:02.160> and<11:11:02.700> the 11:11:02.810 --> 11:11:02.820 align:start position:0% between the client's computer and the 11:11:02.820 --> 11:11:04.550 align:start position:0% between the client's computer and the destination<11:11:03.180> server 11:11:04.550 --> 11:11:04.560 align:start position:0% destination server 11:11:04.560 --> 11:11:06.110 align:start position:0% destination server I've<11:11:05.096> already<11:11:05.276> mentioned<11:11:05.580> that<11:11:05.756> you<11:11:05.936> don't 11:11:06.110 --> 11:11:06.120 align:start position:0% I've already mentioned that you don't 11:11:06.120 --> 11:11:07.246 align:start position:0% I've already mentioned that you don't actually<11:11:06.300> directly<11:11:06.720> connect<11:11:06.900> to<11:11:07.140> the 11:11:07.246 --> 11:11:07.256 align:start position:0% actually directly connect to the 11:11:07.256 --> 11:11:10.010 align:start position:0% actually directly connect to the destination<11:11:08.060> you<11:11:09.060> can<11:11:09.240> have<11:11:09.360> different<11:11:09.540> proxy 11:11:10.010 --> 11:11:10.020 align:start position:0% destination you can have different proxy 11:11:10.020 --> 11:11:13.190 align:start position:0% destination you can have different proxy servers<11:11:10.560> to<11:11:11.460> serve<11:11:12.060> different<11:11:12.240> traffic<11:11:12.596> needs 11:11:13.190 --> 11:11:13.200 align:start position:0% servers to serve different traffic needs 11:11:13.200 --> 11:11:15.350 align:start position:0% servers to serve different traffic needs you<11:11:13.740> might<11:11:13.916> have<11:11:14.040> a<11:11:14.160> proxy<11:11:14.460> server<11:11:14.880> to<11:11:15.000> handle 11:11:15.350 --> 11:11:15.360 align:start position:0% you might have a proxy server to handle 11:11:15.360 --> 11:11:18.730 align:start position:0% you might have a proxy server to handle only<11:11:15.680> HTTP<11:11:16.680> and<11:11:17.460> then<11:11:17.520> if<11:11:17.700> you're<11:11:17.820> doing<11:11:18.000> FTP 11:11:18.730 --> 11:11:18.740 align:start position:0% only HTTP and then if you're doing FTP 11:11:18.740 --> 11:11:22.670 align:start position:0% only HTTP and then if you're doing FTP then<11:11:19.740> it<11:11:19.980> may<11:11:20.160> handle<11:11:20.580> those<11:11:20.820> requests<11:11:21.480> and<11:11:22.320> on 11:11:22.670 --> 11:11:22.680 align:start position:0% then it may handle those requests and on 11:11:22.680 --> 11:11:25.610 align:start position:0% then it may handle those requests and on a<11:11:22.860> different<11:11:22.980> server 11:11:25.610 --> 11:11:25.620 align:start position:0% 11:11:25.620 --> 11:11:27.710 align:start position:0% what<11:11:26.096> does<11:11:26.220> it<11:11:26.340> do<11:11:26.520> it<11:11:26.756> increases<11:11:27.120> performance 11:11:27.710 --> 11:11:27.720 align:start position:0% what does it do it increases performance 11:11:27.720 --> 11:11:29.330 align:start position:0% what does it do it increases performance so 11:11:29.330 --> 11:11:29.340 align:start position:0% so 11:11:29.340 --> 11:11:31.790 align:start position:0% so um<11:11:29.400> it's<11:11:29.700> mainly<11:11:30.000> due<11:11:30.180> to<11:11:30.360> caching<11:11:30.840> or<11:11:31.500> you<11:11:31.680> may 11:11:31.790 --> 11:11:31.800 align:start position:0% um it's mainly due to caching or you may 11:11:31.800 --> 11:11:34.426 align:start position:0% um it's mainly due to caching or you may have<11:11:31.916> quite<11:11:32.220> a<11:11:32.400> powerful<11:11:33.140> proxy<11:11:34.140> server 11:11:34.426 --> 11:11:34.436 align:start position:0% have quite a powerful proxy server 11:11:34.436 --> 11:11:36.230 align:start position:0% have quite a powerful proxy server that's<11:11:34.680> done<11:11:34.916> doing<11:11:35.276> all<11:11:35.460> these<11:11:35.700> requests<11:11:36.060> for 11:11:36.230 --> 11:11:36.240 align:start position:0% that's done doing all these requests for 11:11:36.240 --> 11:11:37.370 align:start position:0% that's done doing all these requests for you 11:11:37.370 --> 11:11:37.380 align:start position:0% you 11:11:37.380 --> 11:11:40.070 align:start position:0% you increases<11:11:38.276> security<11:11:38.580> because<11:11:39.180> what<11:11:39.776> the 11:11:40.070 --> 11:11:40.080 align:start position:0% increases security because what the 11:11:40.080 --> 11:11:42.710 align:start position:0% increases security because what the outside<11:11:40.320> servers<11:11:41.276> on<11:11:41.400> the<11:11:41.580> web<11:11:41.700> see<11:11:42.060> is<11:11:42.596> the 11:11:42.710 --> 11:11:42.720 align:start position:0% outside servers on the web see is the 11:11:42.720 --> 11:11:45.350 align:start position:0% outside servers on the web see is the connection<11:11:42.900> coming<11:11:43.320> from<11:11:43.620> the<11:11:43.860> proxy<11:11:44.340> are<11:11:45.180> not 11:11:45.350 --> 11:11:45.360 align:start position:0% connection coming from the proxy are not 11:11:45.360 --> 11:11:48.350 align:start position:0% connection coming from the proxy are not actually<11:11:45.660> and<11:11:46.436> the<11:11:46.800> uh<11:11:47.400> the<11:11:47.640> client<11:11:47.820> device<11:11:48.060> or 11:11:48.350 --> 11:11:48.360 align:start position:0% actually and the uh the client device or 11:11:48.360 --> 11:11:50.086 align:start position:0% actually and the uh the client device or the<11:11:48.480> host<11:11:48.660> device 11:11:50.086 --> 11:11:50.096 align:start position:0% the host device 11:11:50.096 --> 11:11:53.210 align:start position:0% the host device it<11:11:50.640> also<11:11:50.880> as<11:11:51.060> I<11:11:51.240> said<11:11:51.360> caches<11:11:52.256> content<11:11:52.740> so<11:11:52.980> it 11:11:53.210 --> 11:11:53.220 align:start position:0% it also as I said caches content so it 11:11:53.220 --> 11:11:58.190 align:start position:0% it also as I said caches content so it can<11:11:53.480> serve<11:11:54.480> up<11:11:54.800> and<11:11:55.800> saved<11:11:57.120> copies<11:11:57.900> of<11:11:58.080> a 11:11:58.190 --> 11:11:58.200 align:start position:0% can serve up and saved copies of a 11:11:58.200 --> 11:12:00.290 align:start position:0% can serve up and saved copies of a website<11:11:58.560> it<11:11:58.800> could<11:11:58.916> be<11:11:59.040> a<11:11:59.160> News<11:11:59.340> website<11:11:59.936> or 11:12:00.290 --> 11:12:00.300 align:start position:0% website it could be a News website or 11:12:00.300 --> 11:12:02.926 align:start position:0% website it could be a News website or something<11:12:00.540> else<11:12:00.840> that<11:12:01.320> may<11:12:01.800> not<11:12:02.520> um<11:12:02.580> be 11:12:02.926 --> 11:12:02.936 align:start position:0% something else that may not um be 11:12:02.936 --> 11:12:05.390 align:start position:0% something else that may not um be updated<11:12:03.360> too<11:12:03.900> regularly<11:12:04.500> and<11:12:05.096> then<11:12:05.220> whatever 11:12:05.390 --> 11:12:05.400 align:start position:0% updated too regularly and then whatever 11:12:05.400 --> 11:12:08.450 align:start position:0% updated too regularly and then whatever these<11:12:06.000> rules<11:12:06.360> are<11:12:06.596> on<11:12:06.720> that<11:12:06.960> proxy<11:12:07.320> server<11:12:07.800> it 11:12:08.450 --> 11:12:08.460 align:start position:0% these rules are on that proxy server it 11:12:08.460 --> 11:12:11.150 align:start position:0% these rules are on that proxy server it will<11:12:08.640> refresh<11:12:09.000> that<11:12:09.240> content<11:12:09.776> at<11:12:10.620> given 11:12:11.150 --> 11:12:11.160 align:start position:0% will refresh that content at given 11:12:11.160 --> 11:12:13.130 align:start position:0% will refresh that content at given intervals 11:12:13.130 --> 11:12:13.140 align:start position:0% intervals 11:12:13.140 --> 11:12:14.690 align:start position:0% intervals so<11:12:13.560> you've<11:12:13.740> got<11:12:13.800> to<11:12:13.916> be<11:12:13.980> careful<11:12:14.276> sometimes 11:12:14.690 --> 11:12:14.700 align:start position:0% so you've got to be careful sometimes 11:12:14.700 --> 11:12:16.970 align:start position:0% so you've got to be careful sometimes you<11:12:14.936> can<11:12:15.000> actually<11:12:15.120> be<11:12:15.360> served<11:12:15.776> up<11:12:15.960> a<11:12:16.380> cache<11:12:16.800> of 11:12:16.970 --> 11:12:16.980 align:start position:0% you can actually be served up a cache of 11:12:16.980 --> 11:12:19.730 align:start position:0% you can actually be served up a cache of a<11:12:17.160> web<11:12:17.400> page<11:12:17.640> and<11:12:18.416> the<11:12:18.660> actual<11:12:18.900> live<11:12:19.200> website 11:12:19.730 --> 11:12:19.740 align:start position:0% a web page and the actual live website 11:12:19.740 --> 11:12:22.130 align:start position:0% a web page and the actual live website has<11:12:20.640> changed<11:12:21.120> so<11:12:21.300> it's<11:12:21.416> something<11:12:21.596> to<11:12:21.840> bear<11:12:21.960> in 11:12:22.130 --> 11:12:22.140 align:start position:0% has changed so it's something to bear in 11:12:22.140 --> 11:12:24.170 align:start position:0% has changed so it's something to bear in mind<11:12:22.256> when<11:12:22.500> you're<11:12:23.160> configuring<11:12:23.820> this<11:12:24.000> on 11:12:24.170 --> 11:12:24.180 align:start position:0% mind when you're configuring this on 11:12:24.180 --> 11:12:32.586 align:start position:0% mind when you're configuring this on your<11:12:24.416> network<11:12:24.660> if<11:12:25.020> you<11:12:25.200> do<11:12:25.320> it 11:12:32.586 --> 11:12:32.596 align:start position:0% 11:12:32.596 --> 11:12:35.690 align:start position:0% crazy<11:12:33.596> security<11:12:34.080> as<11:12:34.500> well<11:12:34.680> filters<11:12:35.460> our 11:12:35.690 --> 11:12:35.700 align:start position:0% crazy security as well filters our 11:12:35.700 --> 11:12:37.906 align:start position:0% crazy security as well filters our unwanted<11:12:36.240> web<11:12:36.480> traffic<11:12:36.720> malicious<11:12:37.436> files 11:12:37.906 --> 11:12:37.916 align:start position:0% unwanted web traffic malicious files 11:12:37.916 --> 11:12:41.746 align:start position:0% unwanted web traffic malicious files before<11:12:38.460> sending<11:12:39.060> that<11:12:39.240> onto<11:12:39.720> the<11:12:40.080> end<11:12:40.256> client 11:12:41.746 --> 11:12:41.756 align:start position:0% before sending that onto the end client 11:12:41.756 --> 11:12:44.746 align:start position:0% before sending that onto the end client if<11:12:42.300> the<11:12:42.540> client<11:12:43.200> tries<11:12:43.680> to<11:12:43.800> download<11:12:44.340> a 11:12:44.746 --> 11:12:44.756 align:start position:0% if the client tries to download a 11:12:44.756 --> 11:12:46.970 align:start position:0% if the client tries to download a malicious<11:12:45.180> file<11:12:45.416> unknowingly<11:12:46.140> the<11:12:46.560> proxy 11:12:46.970 --> 11:12:46.980 align:start position:0% malicious file unknowingly the proxy 11:12:46.980 --> 11:12:48.950 align:start position:0% malicious file unknowingly the proxy server<11:12:47.340> can<11:12:47.520> filter<11:12:47.700> it<11:12:48.000> out<11:12:48.180> and<11:12:48.720> you<11:12:48.900> can 11:12:48.950 --> 11:12:48.960 align:start position:0% server can filter it out and you can 11:12:48.960 --> 11:12:51.530 align:start position:0% server can filter it out and you can have<11:12:49.140> a<11:12:49.256> firewall<11:12:49.680> in<11:12:50.580> between<11:12:50.700> your<11:12:51.180> proxy 11:12:51.530 --> 11:12:51.540 align:start position:0% have a firewall in between your proxy 11:12:51.540 --> 11:12:55.070 align:start position:0% have a firewall in between your proxy server<11:12:51.960> and<11:12:52.380> a<11:12:52.620> client<11:12:53.096> or<11:12:53.700> between<11:12:54.240> the<11:12:54.660> proxy 11:12:55.070 --> 11:12:55.080 align:start position:0% server and a client or between the proxy 11:12:55.080 --> 11:12:57.050 align:start position:0% server and a client or between the proxy server<11:12:55.436> and<11:12:55.560> the<11:12:55.680> internet<11:12:55.800> or<11:12:56.340> both 11:12:57.050 --> 11:12:57.060 align:start position:0% server and the internet or both 11:12:57.060 --> 11:13:00.050 align:start position:0% server and the internet or both depending<11:12:57.776> on<11:12:57.840> what<11:12:58.080> your<11:12:58.200> requirements<11:12:58.860> are 11:13:00.050 --> 11:13:00.060 align:start position:0% depending on what your requirements are 11:13:00.060 --> 11:13:03.110 align:start position:0% depending on what your requirements are so<11:13:00.900> already<11:13:01.380> covered<11:13:01.916> that<11:13:02.096> actually 11:13:03.110 --> 11:13:03.120 align:start position:0% so already covered that actually 11:13:03.120 --> 11:13:06.350 align:start position:0% so already covered that actually a<11:13:03.660> forward<11:13:03.840> proxy<11:13:04.436> server<11:13:04.916> is<11:13:05.520> a<11:13:05.756> new<11:13:05.880> thing<11:13:06.180> on 11:13:06.350 --> 11:13:06.360 align:start position:0% a forward proxy server is a new thing on 11:13:06.360 --> 11:13:08.810 align:start position:0% a forward proxy server is a new thing on this<11:13:06.480> syllabus<11:13:06.960> it<11:13:07.800> acts<11:13:08.096> on<11:13:08.220> behalf<11:13:08.520> of<11:13:08.640> a 11:13:08.810 --> 11:13:08.820 align:start position:0% this syllabus it acts on behalf of a 11:13:08.820 --> 11:13:11.086 align:start position:0% this syllabus it acts on behalf of a client<11:13:09.120> computer<11:13:09.360> it<11:13:10.256> gets<11:13:10.500> the<11:13:10.620> requested 11:13:11.086 --> 11:13:11.096 align:start position:0% client computer it gets the requested 11:13:11.096 --> 11:13:14.030 align:start position:0% client computer it gets the requested information<11:13:11.276> from<11:13:12.060> different<11:13:12.360> servers 11:13:14.030 --> 11:13:14.040 align:start position:0% information from different servers 11:13:14.040 --> 11:13:15.950 align:start position:0% information from different servers servers<11:13:14.700> on<11:13:14.820> the<11:13:14.936> Internet<11:13:15.060> only<11:13:15.540> interact 11:13:15.950 --> 11:13:15.960 align:start position:0% servers on the Internet only interact 11:13:15.960 --> 11:13:17.570 align:start position:0% servers on the Internet only interact with<11:13:16.080> the<11:13:16.256> proxy<11:13:16.620> server<11:13:17.040> and<11:13:17.276> they<11:13:17.400> don't 11:13:17.570 --> 11:13:17.580 align:start position:0% with the proxy server and they don't 11:13:17.580 --> 11:13:19.730 align:start position:0% with the proxy server and they don't know<11:13:17.700> about<11:13:17.820> the<11:13:18.060> client's<11:13:18.416> existence<11:13:18.900> which 11:13:19.730 --> 11:13:19.740 align:start position:0% know about the client's existence which 11:13:19.740 --> 11:13:20.990 align:start position:0% know about the client's existence which is<11:13:19.860> the<11:13:19.980> concept<11:13:20.276> we've<11:13:20.520> already<11:13:20.700> been 11:13:20.990 --> 11:13:21.000 align:start position:0% is the concept we've already been 11:13:21.000 --> 11:13:23.990 align:start position:0% is the concept we've already been discussing<11:13:21.900> now<11:13:22.800> there's<11:13:23.040> something 11:13:23.990 --> 11:13:24.000 align:start position:0% discussing now there's something 11:13:24.000 --> 11:13:26.990 align:start position:0% discussing now there's something um<11:13:24.060> known<11:13:24.360> as<11:13:24.540> a<11:13:24.660> reverse<11:13:25.020> proxy<11:13:25.436> server 11:13:26.990 --> 11:13:27.000 align:start position:0% um known as a reverse proxy server 11:13:27.000 --> 11:13:29.630 align:start position:0% um known as a reverse proxy server and<11:13:27.480> the<11:13:27.660> clues<11:13:27.960> in<11:13:28.080> the<11:13:28.200> title<11:13:28.560> I<11:13:28.680> suppose<11:13:28.916> it 11:13:29.630 --> 11:13:29.640 align:start position:0% and the clues in the title I suppose it 11:13:29.640 --> 11:13:31.310 align:start position:0% and the clues in the title I suppose it acts<11:13:29.936> on<11:13:30.000> behalf<11:13:30.360> of<11:13:30.480> the<11:13:30.720> servers<11:13:31.020> on<11:13:31.200> the 11:13:31.310 --> 11:13:31.320 align:start position:0% acts on behalf of the servers on the 11:13:31.320 --> 11:13:34.010 align:start position:0% acts on behalf of the servers on the inside<11:13:31.380> of<11:13:31.620> an<11:13:31.740> organization<11:13:32.540> but<11:13:33.540> you<11:13:33.900> can 11:13:34.010 --> 11:13:34.020 align:start position:0% inside of an organization but you can 11:13:34.020 --> 11:13:35.086 align:start position:0% inside of an organization but you can see<11:13:34.200> here 11:13:35.086 --> 11:13:35.096 align:start position:0% see here 11:13:35.096 --> 11:13:38.150 align:start position:0% see here some<11:13:36.000> host<11:13:36.360> on<11:13:37.020> the<11:13:37.200> Internet<11:13:37.320> is<11:13:37.740> trying<11:13:37.980> to 11:13:38.150 --> 11:13:38.160 align:start position:0% some host on the Internet is trying to 11:13:38.160 --> 11:13:41.330 align:start position:0% some host on the Internet is trying to access<11:13:38.340> your<11:13:38.700> web<11:13:38.936> server<11:13:39.800> internally<11:13:40.800> and 11:13:41.330 --> 11:13:41.340 align:start position:0% access your web server internally and 11:13:41.340 --> 11:13:42.830 align:start position:0% access your web server internally and the<11:13:41.460> proxy<11:13:41.820> server<11:13:42.180> will<11:13:42.360> act<11:13:42.480> as<11:13:42.660> the 11:13:42.830 --> 11:13:42.840 align:start position:0% the proxy server will act as the 11:13:42.840 --> 11:13:44.926 align:start position:0% the proxy server will act as the intermediary<11:13:43.380> deciding<11:13:44.040> what<11:13:44.580> does<11:13:44.756> and 11:13:44.926 --> 11:13:44.936 align:start position:0% intermediary deciding what does and 11:13:44.936 --> 11:13:47.086 align:start position:0% intermediary deciding what does and doesn't<11:13:45.120> go<11:13:45.360> out<11:13:45.540> and<11:13:45.776> also<11:13:46.080> obviously<11:13:46.500> it 11:13:47.086 --> 11:13:47.096 align:start position:0% doesn't go out and also obviously it 11:13:47.096 --> 11:13:49.610 align:start position:0% doesn't go out and also obviously it will<11:13:47.276> could<11:13:47.700> have<11:13:47.936> cached<11:13:48.360> copies<11:13:48.776> of<11:13:49.436> what's 11:13:49.610 --> 11:13:49.620 align:start position:0% will could have cached copies of what's 11:13:49.620 --> 11:13:52.190 align:start position:0% will could have cached copies of what's actually<11:13:50.096> on<11:13:50.460> the<11:13:50.700> web<11:13:51.240> server<11:13:51.660> the<11:13:51.960> actual 11:13:52.190 --> 11:13:52.200 align:start position:0% actually on the web server the actual 11:13:52.200 --> 11:13:56.086 align:start position:0% actually on the web server the actual web<11:13:52.320> server<11:13:52.680> on<11:13:52.800> the<11:13:52.916> inside 11:13:56.086 --> 11:13:56.096 align:start position:0% 11:13:56.096 --> 11:13:58.246 align:start position:0% so<11:13:57.060> um<11:13:57.120> since<11:13:57.360> the<11:13:57.540> service<11:13:57.720> is<11:13:57.900> behind<11:13:58.140> the 11:13:58.246 --> 11:13:58.256 align:start position:0% so um since the service is behind the 11:13:58.256 --> 11:14:00.470 align:start position:0% so um since the service is behind the proxy<11:13:58.560> server<11:13:58.860> the<11:13:59.096> following<11:13:59.340> is<11:13:59.460> true<11:13:59.700> the 11:14:00.470 --> 11:14:00.480 align:start position:0% proxy server the following is true the 11:14:00.480 --> 11:14:02.050 align:start position:0% proxy server the following is true the client<11:14:00.660> is<11:14:00.900> not<11:14:01.020> aware<11:14:01.256> of<11:14:01.380> the<11:14:01.500> services 11:14:02.050 --> 11:14:02.060 align:start position:0% client is not aware of the services 11:14:02.060 --> 11:14:04.246 align:start position:0% client is not aware of the services existence<11:14:03.060> this<11:14:03.360> is<11:14:03.480> the<11:14:03.596> internet<11:14:03.776> client 11:14:04.246 --> 11:14:04.256 align:start position:0% existence this is the internet client 11:14:04.256 --> 11:14:06.406 align:start position:0% existence this is the internet client wherever<11:14:04.620> that<11:14:04.860> may<11:14:05.040> be<11:14:05.220> and<11:14:05.880> it<11:14:06.060> treats<11:14:06.300> a 11:14:06.406 --> 11:14:06.416 align:start position:0% wherever that may be and it treats a 11:14:06.416 --> 11:14:09.830 align:start position:0% wherever that may be and it treats a proxy<11:14:06.776> server<11:14:07.140> as<11:14:07.320> the<11:14:07.560> origin 11:14:09.830 --> 11:14:09.840 align:start position:0% proxy server as the origin 11:14:09.840 --> 11:14:12.710 align:start position:0% proxy server as the origin foreign<11:14:10.820> it<11:14:11.820> can<11:14:11.880> also<11:14:12.060> be<11:14:12.180> used<11:14:12.300> to<11:14:12.480> balance 11:14:12.710 --> 11:14:12.720 align:start position:0% foreign it can also be used to balance 11:14:12.720 --> 11:14:14.746 align:start position:0% foreign it can also be used to balance the<11:14:12.900> load<11:14:13.140> under<11:14:13.380> server<11:14:13.800> farm<11:14:14.096> so<11:14:14.400> it<11:14:14.580> can 11:14:14.746 --> 11:14:14.756 align:start position:0% the load under server farm so it can 11:14:14.756 --> 11:14:18.110 align:start position:0% the load under server farm so it can pull<11:14:15.596> different<11:14:16.436> servers<11:14:17.040> at<11:14:17.520> the<11:14:17.700> same<11:14:17.820> time 11:14:18.110 --> 11:14:18.120 align:start position:0% pull different servers at the same time 11:14:18.120 --> 11:14:21.950 align:start position:0% pull different servers at the same time or<11:14:18.480> load<11:14:18.776> balance 11:14:21.950 --> 11:14:21.960 align:start position:0% 11:14:21.960 --> 11:14:23.990 align:start position:0% now<11:14:22.500> the<11:14:22.740> servers<11:14:23.160> are<11:14:23.220> considered<11:14:23.580> to<11:14:23.700> be<11:14:23.820> on 11:14:23.990 --> 11:14:24.000 align:start position:0% now the servers are considered to be on 11:14:24.000 --> 11:14:26.266 align:start position:0% now the servers are considered to be on the<11:14:24.240> server<11:14:25.200> side<11:14:25.320> of<11:14:25.740> the<11:14:25.860> internet<11:14:25.916> because 11:14:26.266 --> 11:14:26.276 align:start position:0% the server side of the internet because 11:14:26.276 --> 11:14:28.370 align:start position:0% the server side of the internet because of<11:14:26.460> the<11:14:26.520> following<11:14:26.880> The<11:14:27.596> Intercept<11:14:27.960> all<11:14:28.200> the 11:14:28.370 --> 11:14:28.380 align:start position:0% of the following The Intercept all the 11:14:28.380 --> 11:14:30.230 align:start position:0% of the following The Intercept all the traffic<11:14:28.500> coming<11:14:28.800> from<11:14:29.040> the<11:14:29.220> internet<11:14:29.400> they 11:14:30.230 --> 11:14:30.240 align:start position:0% traffic coming from the internet they 11:14:30.240 --> 11:14:31.970 align:start position:0% traffic coming from the internet they make<11:14:30.416> it<11:14:30.596> more<11:14:30.840> difficult<11:14:31.200> for<11:14:31.436> hackers<11:14:31.800> not 11:14:31.970 --> 11:14:31.980 align:start position:0% make it more difficult for hackers not 11:14:31.980 --> 11:14:34.010 align:start position:0% make it more difficult for hackers not impossible<11:14:32.460> but<11:14:32.820> more<11:14:33.000> difficult<11:14:33.300> to<11:14:33.540> get<11:14:33.720> to 11:14:34.010 --> 11:14:34.020 align:start position:0% impossible but more difficult to get to 11:14:34.020 --> 11:14:38.330 align:start position:0% impossible but more difficult to get to get<11:14:34.200> the<11:14:34.320> details<11:14:34.740> of<11:14:34.860> the<11:14:35.040> internal<11:14:35.400> Network 11:14:38.330 --> 11:14:38.340 align:start position:0% 11:14:38.340 --> 11:14:40.550 align:start position:0% all<11:14:38.820> right<11:14:39.000> so<11:14:39.300> in<11:14:39.720> brief<11:14:40.020> we've<11:14:40.320> covered 11:14:40.550 --> 11:14:40.560 align:start position:0% all right so in brief we've covered 11:14:40.560 --> 11:14:43.190 align:start position:0% all right so in brief we've covered proxies<11:14:41.160> and<11:14:41.756> introduction<11:14:42.240> the<11:14:42.596> uses<11:14:42.960> of 11:14:43.190 --> 11:14:43.200 align:start position:0% proxies and introduction the uses of 11:14:43.200 --> 11:14:46.010 align:start position:0% proxies and introduction the uses of them<11:14:43.380> forward<11:14:44.160> proxy<11:14:44.756> servers<11:14:45.300> and<11:14:45.660> reverse 11:14:46.010 --> 11:14:46.020 align:start position:0% them forward proxy servers and reverse 11:14:46.020 --> 11:14:47.510 align:start position:0% them forward proxy servers and reverse proxy<11:14:46.436> servers 11:14:47.510 --> 11:14:47.520 align:start position:0% proxy servers 11:14:47.520 --> 11:14:49.426 align:start position:0% proxy servers all<11:14:48.000> right<11:14:48.180> that's<11:14:48.300> all<11:14:48.480> for<11:14:48.660> now<11:14:48.840> thanks<11:14:49.256> for 11:14:49.426 --> 11:14:49.436 align:start position:0% all right that's all for now thanks for 11:14:49.436 --> 11:14:55.280 align:start position:0% all right that's all for now thanks for watching 11:14:55.280 --> 11:14:55.290 align:start position:0% 11:14:55.290 --> 11:15:11.690 align:start position:0% [Music] 11:15:11.690 --> 11:15:11.700 align:start position:0% 11:15:11.700 --> 11:15:13.906 align:start position:0% welcome<11:15:12.240> to<11:15:12.540> the<11:15:12.720> lesson<11:15:13.256> on<11:15:13.436> network<11:15:13.620> address 11:15:13.906 --> 11:15:13.916 align:start position:0% welcome to the lesson on network address 11:15:13.916 --> 11:15:18.406 align:start position:0% welcome to the lesson on network address translation<11:15:14.700> on<11:15:15.300> Nat<11:15:15.720> for<11:15:16.200> short 11:15:18.406 --> 11:15:18.416 align:start position:0% 11:15:18.416 --> 11:15:21.906 align:start position:0% and<11:15:18.720> a<11:15:18.900> look<11:15:19.020> at<11:15:19.200> what<11:15:19.436> it<11:15:19.620> is<11:15:20.120> ipv4<11:15:21.120> addresses 11:15:21.906 --> 11:15:21.916 align:start position:0% and a look at what it is ipv4 addresses 11:15:21.916 --> 11:15:24.470 align:start position:0% and a look at what it is ipv4 addresses IPv6<11:15:22.916> addresses 11:15:24.470 --> 11:15:24.480 align:start position:0% IPv6 addresses 11:15:24.480 --> 11:15:27.950 align:start position:0% IPv6 addresses benefit<11:15:25.140> of<11:15:25.800> having<11:15:26.220> NASA<11:15:26.756> using<11:15:27.120> it 11:15:27.950 --> 11:15:27.960 align:start position:0% benefit of having NASA using it 11:15:27.960 --> 11:15:30.050 align:start position:0% benefit of having NASA using it Source<11:15:28.740> Network<11:15:28.916> address<11:15:29.276> translation 11:15:30.050 --> 11:15:30.060 align:start position:0% Source Network address translation 11:15:30.060 --> 11:15:32.870 align:start position:0% Source Network address translation destination<11:15:31.020> that<11:15:31.500> and<11:15:32.460> port<11:15:32.700> address 11:15:32.870 --> 11:15:32.880 align:start position:0% destination that and port address 11:15:32.880 --> 11:15:36.650 align:start position:0% destination that and port address translation<11:15:33.596> or<11:15:34.320> also<11:15:35.040> called<11:15:35.160> Pat<11:15:35.580> or<11:15:36.416> Nat 11:15:36.650 --> 11:15:36.660 align:start position:0% translation or also called Pat or Nat 11:15:36.660 --> 11:15:38.710 align:start position:0% translation or also called Pat or Nat overload 11:15:38.710 --> 11:15:38.720 align:start position:0% overload 11:15:38.720 --> 11:15:42.230 align:start position:0% overload so<11:15:39.720> what<11:15:40.020> is<11:15:40.200> in<11:15:40.436> that 11:15:42.230 --> 11:15:42.240 align:start position:0% so what is in that 11:15:42.240 --> 11:15:44.810 align:start position:0% so what is in that it<11:15:42.660> basically<11:15:42.960> translates<11:15:43.500> in<11:15:43.740> private<11:15:44.340> IP 11:15:44.810 --> 11:15:44.820 align:start position:0% it basically translates in private IP 11:15:44.820 --> 11:15:47.450 align:start position:0% it basically translates in private IP addresses<11:15:45.416> into<11:15:45.840> public<11:15:46.140> IP<11:15:46.620> for<11:15:46.860> addresses 11:15:47.450 --> 11:15:47.460 align:start position:0% addresses into public IP for addresses 11:15:47.460 --> 11:15:51.290 align:start position:0% addresses into public IP for addresses the<11:15:48.416> private<11:15:48.776> IP<11:15:49.200> for<11:15:49.620> addresses 11:15:51.290 --> 11:15:51.300 align:start position:0% the private IP for addresses 11:15:51.300 --> 11:15:52.570 align:start position:0% the private IP for addresses um 11:15:52.570 --> 11:15:52.580 align:start position:0% um 11:15:52.580 --> 11:15:56.766 align:start position:0% um RFC<11:15:53.580> 1918<11:15:54.300> I<11:15:54.596> think<11:15:54.776> it<11:15:54.900> is<11:15:55.560> these<11:15:56.276> provide 11:15:56.766 --> 11:15:56.776 align:start position:0% RFC 1918 I think it is these provide 11:15:56.776 --> 11:15:59.330 align:start position:0% RFC 1918 I think it is these provide addresses<11:15:57.776> that<11:15:58.020> you<11:15:58.140> can<11:15:58.256> use<11:15:58.500> internally<11:15:59.160> on 11:15:59.330 --> 11:15:59.340 align:start position:0% addresses that you can use internally on 11:15:59.340 --> 11:16:00.950 align:start position:0% addresses that you can use internally on your<11:15:59.520> network<11:15:59.700> but<11:16:00.120> they<11:16:00.240> can't<11:16:00.416> be<11:16:00.540> routed 11:16:00.950 --> 11:16:00.960 align:start position:0% your network but they can't be routed 11:16:00.960 --> 11:16:02.926 align:start position:0% your network but they can't be routed over<11:16:01.200> the<11:16:01.436> Internet<11:16:01.620> so<11:16:02.520> all<11:16:02.700> of<11:16:02.820> a<11:16:02.880> sudden 11:16:02.926 --> 11:16:02.936 align:start position:0% over the Internet so all of a sudden 11:16:02.936 --> 11:16:04.330 align:start position:0% over the Internet so all of a sudden you've<11:16:03.180> got<11:16:03.360> a<11:16:03.480> problem 11:16:04.330 --> 11:16:04.340 align:start position:0% you've got a problem 11:16:04.340 --> 11:16:07.550 align:start position:0% you've got a problem so<11:16:05.340> this<11:16:06.180> helped<11:16:06.776> solve<11:16:07.080> the<11:16:07.200> issue<11:16:07.436> of 11:16:07.550 --> 11:16:07.560 align:start position:0% so this helped solve the issue of 11:16:07.560 --> 11:16:10.190 align:start position:0% so this helped solve the issue of running<11:16:07.740> out<11:16:08.040> of<11:16:08.160> ipv4<11:16:08.880> addresses<11:16:09.480> however 11:16:10.190 --> 11:16:10.200 align:start position:0% running out of ipv4 addresses however 11:16:10.200 --> 11:16:11.926 align:start position:0% running out of ipv4 addresses however then<11:16:10.436> we<11:16:10.680> have<11:16:10.800> to<11:16:10.916> resolve<11:16:11.276> the<11:16:11.400> issue<11:16:11.640> of<11:16:11.700> not 11:16:11.926 --> 11:16:11.936 align:start position:0% then we have to resolve the issue of not 11:16:11.936 --> 11:16:13.490 align:start position:0% then we have to resolve the issue of not being<11:16:12.060> able<11:16:12.300> to<11:16:12.416> wrote<11:16:12.776> route<11:16:13.200> those 11:16:13.490 --> 11:16:13.500 align:start position:0% being able to wrote route those 11:16:13.500 --> 11:16:16.130 align:start position:0% being able to wrote route those addresses 11:16:16.130 --> 11:16:16.140 align:start position:0% 11:16:16.140 --> 11:16:18.170 align:start position:0% so<11:16:16.680> and<11:16:16.916> that<11:16:17.096> is<11:16:17.340> a<11:16:17.460> router<11:16:17.820> function 11:16:18.170 --> 11:16:18.180 align:start position:0% so and that is a router function 11:16:18.180 --> 11:16:21.050 align:start position:0% so and that is a router function actually<11:16:18.660> these<11:16:18.960> routers<11:16:19.500> and<11:16:19.860> firewalls<11:16:20.640> can 11:16:21.050 --> 11:16:21.060 align:start position:0% actually these routers and firewalls can 11:16:21.060 --> 11:16:24.230 align:start position:0% actually these routers and firewalls can do<11:16:21.300> nothing 11:16:24.230 --> 11:16:24.240 align:start position:0% 11:16:24.240 --> 11:16:26.510 align:start position:0% so<11:16:24.840> normally<11:16:25.200> it's<11:16:25.620> enabled<11:16:26.040> at<11:16:26.160> the<11:16:26.276> boundary 11:16:26.510 --> 11:16:26.520 align:start position:0% so normally it's enabled at the boundary 11:16:26.520 --> 11:16:28.730 align:start position:0% so normally it's enabled at the boundary where<11:16:26.880> your<11:16:27.060> local<11:16:27.180> area<11:16:27.480> network<11:16:27.776> meets<11:16:28.560> your 11:16:28.730 --> 11:16:28.740 align:start position:0% where your local area network meets your 11:16:28.740 --> 11:16:31.210 align:start position:0% where your local area network meets your internet<11:16:29.340> connection 11:16:31.210 --> 11:16:31.220 align:start position:0% internet connection 11:16:31.220 --> 11:16:33.766 align:start position:0% internet connection you<11:16:32.220> don't<11:16:32.340> need<11:16:32.460> to<11:16:32.580> bother<11:16:32.820> not<11:16:33.060> in<11:16:33.360> usually 11:16:33.766 --> 11:16:33.776 align:start position:0% you don't need to bother not in usually 11:16:33.776 --> 11:16:35.570 align:start position:0% you don't need to bother not in usually internally<11:16:34.256> on<11:16:34.436> your<11:16:34.620> network<11:16:34.740> no<11:16:35.220> particular 11:16:35.570 --> 11:16:35.580 align:start position:0% internally on your network no particular 11:16:35.580 --> 11:16:38.390 align:start position:0% internally on your network no particular reason<11:16:35.840> and<11:16:36.840> we<11:16:37.020> use<11:16:37.140> Nat<11:16:37.500> with<11:16:37.620> ipv4 11:16:38.390 --> 11:16:38.400 align:start position:0% reason and we use Nat with ipv4 11:16:38.400 --> 11:16:39.710 align:start position:0% reason and we use Nat with ipv4 addresses 11:16:39.710 --> 11:16:39.720 align:start position:0% addresses 11:16:39.720 --> 11:16:43.610 align:start position:0% addresses ipv4<11:16:40.620> has<11:16:40.860> approximately<11:16:41.340> 4.3<11:16:42.180> billion 11:16:43.610 --> 11:16:43.620 align:start position:0% ipv4 has approximately 4.3 billion 11:16:43.620 --> 11:16:45.890 align:start position:0% ipv4 has approximately 4.3 billion unfortunately<11:16:44.460> the<11:16:44.880> DraStic<11:16:45.180> growth<11:16:45.596> of<11:16:45.720> the 11:16:45.890 --> 11:16:45.900 align:start position:0% unfortunately the DraStic growth of the 11:16:45.900 --> 11:16:49.490 align:start position:0% unfortunately the DraStic growth of the internet<11:16:46.020> due<11:16:46.436> to<11:16:46.620> affordability<11:16:47.276> of<11:16:48.256> and<11:16:49.256> and 11:16:49.490 --> 11:16:49.500 align:start position:0% internet due to affordability of and and 11:16:49.500 --> 11:16:52.906 align:start position:0% internet due to affordability of and and user<11:16:50.040> equipment<11:16:50.840> basically<11:16:51.840> I<11:16:52.020> mean<11:16:52.200> maybe<11:16:52.680> we 11:16:52.906 --> 11:16:52.916 align:start position:0% user equipment basically I mean maybe we 11:16:52.916 --> 11:16:55.850 align:start position:0% user equipment basically I mean maybe we were<11:16:53.040> running<11:16:53.160> out<11:16:53.400> of<11:16:53.580> ipv4<11:16:54.416> addresses 11:16:55.850 --> 11:16:55.860 align:start position:0% were running out of ipv4 addresses 11:16:55.860 --> 11:16:59.746 align:start position:0% were running out of ipv4 addresses so<11:16:56.756> Nat<11:16:57.180> was<11:16:57.480> a<11:16:57.900> temporary<11:16:58.320> solution<11:16:58.800> to<11:16:59.340> a 11:16:59.746 --> 11:16:59.756 align:start position:0% so Nat was a temporary solution to a 11:16:59.756 --> 11:17:03.310 align:start position:0% so Nat was a temporary solution to a permanent<11:17:00.180> problem 11:17:03.310 --> 11:17:03.320 align:start position:0% 11:17:03.320 --> 11:17:06.650 align:start position:0% IPv6<11:17:04.320> is<11:17:05.160> the<11:17:05.520> replacement<11:17:05.700> obviously<11:17:06.360> for 11:17:06.650 --> 11:17:06.660 align:start position:0% IPv6 is the replacement obviously for 11:17:06.660 --> 11:17:10.370 align:start position:0% IPv6 is the replacement obviously for ipv<11:17:07.080> version<11:17:07.500> 4.<11:17:08.040> now<11:17:08.820> this<11:17:09.540> is<11:17:09.660> the<11:17:09.900> long-term 11:17:10.370 --> 11:17:10.380 align:start position:0% ipv version 4. now this is the long-term 11:17:10.380 --> 11:17:13.010 align:start position:0% ipv version 4. now this is the long-term solution<11:17:10.740> there<11:17:11.700> is<11:17:11.820> a<11:17:12.060> version<11:17:12.300> of<11:17:12.596> nat 11:17:13.010 --> 11:17:13.020 align:start position:0% solution there is a version of nat 11:17:13.020 --> 11:17:17.630 align:start position:0% solution there is a version of nat available<11:17:13.400> for<11:17:14.900> IPv6<11:17:15.916> I<11:17:16.916> don't<11:17:17.160> even<11:17:17.340> think 11:17:17.630 --> 11:17:17.640 align:start position:0% available for IPv6 I don't even think 11:17:17.640 --> 11:17:19.370 align:start position:0% available for IPv6 I don't even think Cisco<11:17:18.060> included<11:17:18.480> on<11:17:18.660> the<11:17:18.776> syllabus<11:17:19.200> anymore 11:17:19.370 --> 11:17:19.380 align:start position:0% Cisco included on the syllabus anymore 11:17:19.380 --> 11:17:21.586 align:start position:0% Cisco included on the syllabus anymore the<11:17:20.276> reason<11:17:20.460> is<11:17:20.756> there's<11:17:21.000> an<11:17:21.416> almost 11:17:21.586 --> 11:17:21.596 align:start position:0% the reason is there's an almost 11:17:21.596 --> 11:17:23.150 align:start position:0% the reason is there's an almost inexhaustible 11:17:23.150 --> 11:17:23.160 align:start position:0% inexhaustible 11:17:23.160 --> 11:17:26.266 align:start position:0% inexhaustible number<11:17:23.880> of<11:17:24.240> available<11:17:24.480> IP<11:17:25.380> version<11:17:25.680> 6 11:17:26.266 --> 11:17:26.276 align:start position:0% number of available IP version 6 11:17:26.276 --> 11:17:28.070 align:start position:0% number of available IP version 6 addresses 11:17:28.070 --> 11:17:28.080 align:start position:0% addresses 11:17:28.080 --> 11:17:30.230 align:start position:0% addresses um<11:17:28.140> I<11:17:28.860> think<11:17:28.980> something<11:17:29.160> like<11:17:29.460> Millions<11:17:29.880> per 11:17:30.230 --> 11:17:30.240 align:start position:0% um I think something like Millions per 11:17:30.240 --> 11:17:33.586 align:start position:0% um I think something like Millions per every<11:17:30.596> per<11:17:30.960> every<11:17:31.256> person<11:17:31.560> in<11:17:32.460> the<11:17:32.580> world<11:17:32.820> so 11:17:33.586 --> 11:17:33.596 align:start position:0% every per every person in the world so 11:17:33.596 --> 11:17:35.330 align:start position:0% every per every person in the world so it's<11:17:33.900> pretty<11:17:34.200> much<11:17:34.320> inconceivable<11:17:35.040> that 11:17:35.330 --> 11:17:35.340 align:start position:0% it's pretty much inconceivable that 11:17:35.340 --> 11:17:37.190 align:start position:0% it's pretty much inconceivable that we're<11:17:35.520> going<11:17:35.700> to<11:17:35.820> be<11:17:35.936> running<11:17:36.540> out<11:17:36.900> of<11:17:37.080> them 11:17:37.190 --> 11:17:37.200 align:start position:0% we're going to be running out of them 11:17:37.200 --> 11:17:39.230 align:start position:0% we're going to be running out of them anytime<11:17:37.800> soon<11:17:38.040> certainly<11:17:38.700> within<11:17:39.060> our 11:17:39.230 --> 11:17:39.240 align:start position:0% anytime soon certainly within our 11:17:39.240 --> 11:17:41.086 align:start position:0% anytime soon certainly within our lifetimes<11:17:39.720> anyway 11:17:41.086 --> 11:17:41.096 align:start position:0% lifetimes anyway 11:17:41.096 --> 11:17:43.906 align:start position:0% lifetimes anyway so<11:17:41.580> it<11:17:41.820> benefits<11:17:42.360> as<11:17:42.776> well<11:17:42.960> as<11:17:43.080> using<11:17:43.436> it<11:17:43.560> so<11:17:43.740> we 11:17:43.906 --> 11:17:43.916 align:start position:0% so it benefits as well as using it so we 11:17:43.916 --> 11:17:45.350 align:start position:0% so it benefits as well as using it so we don't<11:17:44.040> really<11:17:44.160> have<11:17:44.400> addresses<11:17:44.820> it<11:17:45.180> actually 11:17:45.350 --> 11:17:45.360 align:start position:0% don't really have addresses it actually 11:17:45.360 --> 11:17:48.230 align:start position:0% don't really have addresses it actually hides<11:17:46.020> our<11:17:46.916> internal<11:17:47.340> addresses<11:17:47.820> on<11:17:48.000> our 11:17:48.230 --> 11:17:48.240 align:start position:0% hides our internal addresses on our 11:17:48.240 --> 11:17:50.810 align:start position:0% hides our internal addresses on our private<11:17:48.540> network<11:17:48.776> from<11:17:49.560> the<11:17:50.220> internet<11:17:50.400> which 11:17:50.810 --> 11:17:50.820 align:start position:0% private network from the internet which 11:17:50.820 --> 11:17:52.370 align:start position:0% private network from the internet which is<11:17:50.936> pretty<11:17:51.120> handy<11:17:51.540> so<11:17:51.840> it's<11:17:52.020> a<11:17:52.200> security 11:17:52.370 --> 11:17:52.380 align:start position:0% is pretty handy so it's a security 11:17:52.380 --> 11:17:54.350 align:start position:0% is pretty handy so it's a security feature 11:17:54.350 --> 11:17:54.360 align:start position:0% feature 11:17:54.360 --> 11:17:56.450 align:start position:0% feature these<11:17:54.960> are<11:17:55.080> the<11:17:55.200> private<11:17:55.560> addresses<11:17:56.040> which 11:17:56.450 --> 11:17:56.460 align:start position:0% these are the private addresses which 11:17:56.460 --> 11:17:57.890 align:start position:0% these are the private addresses which hopefully<11:17:56.820> you're<11:17:57.000> already<11:17:57.180> familiar<11:17:57.660> with 11:17:57.890 --> 11:17:57.900 align:start position:0% hopefully you're already familiar with 11:17:57.900 --> 11:18:00.050 align:start position:0% hopefully you're already familiar with you<11:17:58.200> need<11:17:58.320> to<11:17:58.436> know<11:17:58.740> this<11:17:59.220> range<11:17:59.520> of<11:17:59.640> addresses 11:18:00.050 --> 11:18:00.060 align:start position:0% you need to know this range of addresses 11:18:00.060 --> 11:18:02.746 align:start position:0% you need to know this range of addresses because<11:18:00.240> this<11:18:00.480> is<11:18:00.660> a<11:18:00.840> favorite<11:18:01.276> exam<11:18:02.276> topic 11:18:02.746 --> 11:18:02.756 align:start position:0% because this is a favorite exam topic 11:18:02.756 --> 11:18:07.610 align:start position:0% because this is a favorite exam topic for<11:18:03.660> comtier<11:18:04.200> and<11:18:04.380> also<11:18:04.620> Cisco<11:18:05.040> and<11:18:05.276> Microsoft 11:18:07.610 --> 11:18:07.620 align:start position:0% for comtier and also Cisco and Microsoft 11:18:07.620 --> 11:18:09.830 align:start position:0% for comtier and also Cisco and Microsoft these<11:18:08.400> addresses<11:18:08.756> you<11:18:09.000> can<11:18:09.120> arbitrarily 11:18:09.830 --> 11:18:09.840 align:start position:0% these addresses you can arbitrarily 11:18:09.840 --> 11:18:12.586 align:start position:0% these addresses you can arbitrarily inside<11:18:10.020> them<11:18:10.380> with<11:18:10.620> the<11:18:10.740> dhp<11:18:11.276> server<11:18:11.820> inside 11:18:12.586 --> 11:18:12.596 align:start position:0% inside them with the dhp server inside 11:18:12.596 --> 11:18:14.926 align:start position:0% inside them with the dhp server inside your<11:18:12.960> network<11:18:13.320> or 11:18:14.926 --> 11:18:14.936 align:start position:0% your network or 11:18:14.936 --> 11:18:17.690 align:start position:0% your network or um<11:18:15.416> yeah<11:18:15.960> you'll<11:18:16.256> have<11:18:16.620> DHCP<11:18:17.276> server 11:18:17.690 --> 11:18:17.700 align:start position:0% um yeah you'll have DHCP server 11:18:17.700 --> 11:18:19.490 align:start position:0% um yeah you'll have DHCP server somewhere<11:18:18.240> usually 11:18:19.490 --> 11:18:19.500 align:start position:0% somewhere usually 11:18:19.500 --> 11:18:21.290 align:start position:0% somewhere usually I<11:18:19.980> wouldn't<11:18:20.096> let<11:18:20.276> any<11:18:20.460> users<11:18:20.820> assign<11:18:21.120> their 11:18:21.290 --> 11:18:21.300 align:start position:0% I wouldn't let any users assign their 11:18:21.300 --> 11:18:22.970 align:start position:0% I wouldn't let any users assign their own<11:18:21.416> IP<11:18:21.720> addresses 11:18:22.970 --> 11:18:22.980 align:start position:0% own IP addresses 11:18:22.980 --> 11:18:24.470 align:start position:0% own IP addresses so<11:18:23.400> let's<11:18:23.460> say<11:18:23.640> we<11:18:23.820> have<11:18:23.936> a<11:18:24.060> lan<11:18:24.300> with 11:18:24.470 --> 11:18:24.480 align:start position:0% so let's say we have a lan with 11:18:24.480 --> 11:18:26.330 align:start position:0% so let's say we have a lan with computers<11:18:24.900> that<11:18:25.080> assign<11:18:25.500> these<11:18:25.740> private<11:18:26.040> IP 11:18:26.330 --> 11:18:26.340 align:start position:0% computers that assign these private IP 11:18:26.340 --> 11:18:29.030 align:start position:0% computers that assign these private IP addresses<11:18:26.900> and<11:18:27.900> internally<11:18:28.256> we've<11:18:28.500> got<11:18:28.620> a<11:18:28.740> PC 11:18:29.030 --> 11:18:29.040 align:start position:0% addresses and internally we've got a PC 11:18:29.040 --> 11:18:31.670 align:start position:0% addresses and internally we've got a PC one<11:18:29.340> the<11:18:30.000> data<11:18:30.300> back<11:18:30.416> it<11:18:30.660> goes<11:18:30.900> to<11:18:30.960> our<11:18:31.140> router 11:18:31.670 --> 11:18:31.680 align:start position:0% one the data back it goes to our router 11:18:31.680 --> 11:18:34.190 align:start position:0% one the data back it goes to our router the<11:18:32.276> router<11:18:32.640> will<11:18:32.880> Nat<11:18:33.240> to<11:18:33.480> this<11:18:33.596> address<11:18:33.776> for 11:18:34.190 --> 11:18:34.200 align:start position:0% the router will Nat to this address for 11:18:34.200 --> 11:18:36.710 align:start position:0% the router will Nat to this address for a<11:18:34.436> routable<11:18:34.800> address<11:18:35.096> which<11:18:35.640> you've<11:18:36.000> added<11:18:36.596> to 11:18:36.710 --> 11:18:36.720 align:start position:0% a routable address which you've added to 11:18:36.720 --> 11:18:38.810 align:start position:0% a routable address which you've added to the<11:18:36.840> configuration<11:18:37.436> somewhere 11:18:38.810 --> 11:18:38.820 align:start position:0% the configuration somewhere 11:18:38.820 --> 11:18:40.130 align:start position:0% the configuration somewhere and<11:18:39.180> it's<11:18:39.300> one<11:18:39.480> of<11:18:39.596> the<11:18:39.596> addresses<11:18:39.960> you've 11:18:40.130 --> 11:18:40.140 align:start position:0% and it's one of the addresses you've 11:18:40.140 --> 11:18:42.406 align:start position:0% and it's one of the addresses you've been<11:18:40.256> allocated<11:18:40.740> the<11:18:41.400> packet<11:18:41.756> goes<11:18:42.060> out<11:18:42.180> to 11:18:42.406 --> 11:18:42.416 align:start position:0% been allocated the packet goes out to 11:18:42.416 --> 11:18:45.290 align:start position:0% been allocated the packet goes out to the<11:18:42.660> internet<11:18:42.980> somewhere<11:18:43.980> comes<11:18:44.820> back<11:18:45.000> your 11:18:45.290 --> 11:18:45.300 align:start position:0% the internet somewhere comes back your 11:18:45.300 --> 11:18:47.086 align:start position:0% the internet somewhere comes back your router<11:18:45.720> will<11:18:45.840> have<11:18:46.020> a<11:18:46.200> table<11:18:46.320> and<11:18:46.860> that 11:18:47.086 --> 11:18:47.096 align:start position:0% router will have a table and that 11:18:47.096 --> 11:18:48.830 align:start position:0% router will have a table and that translation<11:18:47.700> table 11:18:48.830 --> 11:18:48.840 align:start position:0% translation table 11:18:48.840 --> 11:18:51.470 align:start position:0% translation table and<11:18:49.500> it<11:18:49.680> will<11:18:49.916> recall<11:18:50.460> which<11:18:50.756> address<11:18:51.000> on<11:18:51.240> is 11:18:51.470 --> 11:18:51.480 align:start position:0% and it will recall which address on is 11:18:51.480 --> 11:18:53.406 align:start position:0% and it will recall which address on is on<11:18:51.720> the<11:18:51.840> inside<11:18:52.020> which<11:18:52.680> is<11:18:52.916> on<11:18:53.096> the<11:18:53.276> outside 11:18:53.406 --> 11:18:53.416 align:start position:0% on the inside which is on the outside 11:18:53.416 --> 11:18:55.246 align:start position:0% on the inside which is on the outside and<11:18:54.416> then 11:18:55.246 --> 11:18:55.256 align:start position:0% and then 11:18:55.256 --> 11:18:57.650 align:start position:0% and then um<11:18:55.320> re-nut<11:18:55.860> it<11:18:56.040> so<11:18:56.160> it<11:18:56.340> populates<11:18:56.700> the<11:18:56.936> packets 11:18:57.650 --> 11:18:57.660 align:start position:0% um re-nut it so it populates the packets 11:18:57.660 --> 11:18:59.690 align:start position:0% um re-nut it so it populates the packets for<11:18:57.900> the<11:18:58.020> correct<11:18:58.200> header<11:18:58.680> and<11:18:59.160> then<11:18:59.220> forwards 11:18:59.690 --> 11:18:59.700 align:start position:0% for the correct header and then forwards 11:18:59.700 --> 11:19:01.550 align:start position:0% for the correct header and then forwards it<11:18:59.820> back<11:19:00.060> to<11:19:00.180> the 11:19:01.550 --> 11:19:01.560 align:start position:0% it back to the 11:19:01.560 --> 11:19:06.406 align:start position:0% it back to the um PC<11:19:02.220> on<11:19:02.520> the<11:19:02.580> inside<11:19:02.700> of<11:19:02.936> your<11:19:03.120> LAN 11:19:06.406 --> 11:19:06.416 align:start position:0% 11:19:06.416 --> 11:19:09.650 align:start position:0% so<11:19:07.020> in<11:19:07.380> this<11:19:07.560> case<11:19:07.860> this<11:19:08.700> is<11:19:08.880> in<11:19:09.060> Long<11:19:09.240> longer 11:19:09.650 --> 11:19:09.660 align:start position:0% so in this case this is in Long longer 11:19:09.660 --> 11:19:11.630 align:start position:0% so in this case this is in Long longer version<11:19:09.720> of<11:19:10.020> what<11:19:10.140> I've<11:19:10.256> said<11:19:10.500> really<11:19:10.740> this 11:19:11.630 --> 11:19:11.640 align:start position:0% version of what I've said really this 11:19:11.640 --> 11:19:14.330 align:start position:0% version of what I've said really this case<11:19:11.880> the<11:19:12.560> hudternetwork.com<11:19:13.560> so<11:19:13.916> if<11:19:14.096> I<11:19:14.276> have 11:19:14.330 --> 11:19:14.340 align:start position:0% case the hudternetwork.com so if I have 11:19:14.340 --> 11:19:16.010 align:start position:0% case the hudternetwork.com so if I have the<11:19:14.400> server<11:19:14.640> on<11:19:14.756> the<11:19:14.880> right<11:19:15.000> there<11:19:15.240> a<11:19:15.776> scene 11:19:16.010 --> 11:19:16.020 align:start position:0% the server on the right there a scene 11:19:16.020 --> 11:19:18.110 align:start position:0% the server on the right there a scene that<11:19:16.200> it's<11:19:16.320> coming<11:19:16.500> from<11:19:16.740> a<11:19:16.916> routable<11:19:17.460> IP 11:19:18.110 --> 11:19:18.120 align:start position:0% that it's coming from a routable IP 11:19:18.120 --> 11:19:19.310 align:start position:0% that it's coming from a routable IP address 11:19:19.310 --> 11:19:19.320 align:start position:0% address 11:19:19.320 --> 11:19:21.586 align:start position:0% address it<11:19:19.800> just<11:19:19.980> wouldn't<11:19:20.096> get<11:19:20.276> routed<11:19:20.756> by<11:19:21.060> your<11:19:21.596> um 11:19:21.586 --> 11:19:21.596 align:start position:0% it just wouldn't get routed by your um 11:19:21.596 --> 11:19:23.450 align:start position:0% it just wouldn't get routed by your um ISP<11:19:22.256> otherwise 11:19:23.450 --> 11:19:23.460 align:start position:0% ISP otherwise 11:19:23.460 --> 11:19:25.906 align:start position:0% ISP otherwise you<11:19:24.060> can<11:19:24.240> tunnel<11:19:24.776> addresses<11:19:25.380> but<11:19:25.620> you<11:19:25.800> still 11:19:25.906 --> 11:19:25.916 align:start position:0% you can tunnel addresses but you still 11:19:25.916 --> 11:19:27.350 align:start position:0% you can tunnel addresses but you still need<11:19:26.096> to<11:19:26.160> Tunnel<11:19:26.520> them<11:19:26.640> inside<11:19:26.756> a<11:19:27.000> routable 11:19:27.350 --> 11:19:27.360 align:start position:0% need to Tunnel them inside a routable 11:19:27.360 --> 11:19:28.906 align:start position:0% need to Tunnel them inside a routable packet 11:19:28.906 --> 11:19:28.916 align:start position:0% packet 11:19:28.916 --> 11:19:31.310 align:start position:0% packet Source<11:19:29.520> Network<11:19:29.700> address<11:19:29.936> translation<11:19:30.660> a<11:19:31.140> bit 11:19:31.310 --> 11:19:31.320 align:start position:0% Source Network address translation a bit 11:19:31.320 --> 11:19:32.990 align:start position:0% Source Network address translation a bit of<11:19:31.436> a<11:19:31.500> strange<11:19:31.740> term<11:19:31.916> this<11:19:32.220> but<11:19:32.460> comps<11:19:32.880> here 11:19:32.990 --> 11:19:33.000 align:start position:0% of a strange term this but comps here 11:19:33.000 --> 11:19:34.610 align:start position:0% of a strange term this but comps here are<11:19:33.180> coining<11:19:33.540> it 11:19:34.610 --> 11:19:34.620 align:start position:0% are coining it 11:19:34.620 --> 11:19:38.030 align:start position:0% are coining it basically<11:19:35.160> it<11:19:35.276> means<11:19:35.640> the<11:19:36.540> um<11:19:36.540> Source<11:19:37.320> on<11:19:37.916> the 11:19:38.030 --> 11:19:38.040 align:start position:0% basically it means the um Source on the 11:19:38.040 --> 11:19:39.950 align:start position:0% basically it means the um Source on the inside<11:19:38.160> of<11:19:38.400> your<11:19:38.460> network<11:19:38.756> is<11:19:39.180> being<11:19:39.360> nattted 11:19:39.950 --> 11:19:39.960 align:start position:0% inside of your network is being nattted 11:19:39.960 --> 11:19:42.350 align:start position:0% inside of your network is being nattted out<11:19:40.500> to<11:19:40.680> a<11:19:40.860> routable<11:19:41.276> address<11:19:41.580> so<11:19:42.000> you're 11:19:42.350 --> 11:19:42.360 align:start position:0% out to a routable address so you're 11:19:42.360 --> 11:19:44.926 align:start position:0% out to a routable address so you're initiating<11:19:43.256> the<11:19:43.680> connection<11:19:43.860> from<11:19:44.700> your 11:19:44.926 --> 11:19:44.936 align:start position:0% initiating the connection from your 11:19:44.936 --> 11:19:46.426 align:start position:0% initiating the connection from your source 11:19:46.426 --> 11:19:46.436 align:start position:0% source 11:19:46.436 --> 11:19:48.766 align:start position:0% source so<11:19:46.980> you've<11:19:47.160> got<11:19:47.220> a<11:19:47.400> 192<11:19:47.880> Network<11:19:48.180> and<11:19:48.596> it's 11:19:48.766 --> 11:19:48.776 align:start position:0% so you've got a 192 Network and it's 11:19:48.776 --> 11:19:51.650 align:start position:0% so you've got a 192 Network and it's been<11:19:48.960> translated<11:19:49.436> to<11:19:50.096> a<11:19:50.640> range<11:19:51.120> of<11:19:51.240> addresses 11:19:51.650 --> 11:19:51.660 align:start position:0% been translated to a range of addresses 11:19:51.660 --> 11:19:53.630 align:start position:0% been translated to a range of addresses on<11:19:51.900> this<11:19:52.080> router<11:19:52.500> probably<11:19:52.980> not<11:19:53.160> a<11:19:53.340> good<11:19:53.400> idea 11:19:53.630 --> 11:19:53.640 align:start position:0% on this router probably not a good idea 11:19:53.640 --> 11:19:55.310 align:start position:0% on this router probably not a good idea to<11:19:53.820> have<11:19:53.936> one<11:19:54.120> routable<11:19:54.540> address<11:19:54.776> because<11:19:55.080> you 11:19:55.310 --> 11:19:55.320 align:start position:0% to have one routable address because you 11:19:55.320 --> 11:19:57.290 align:start position:0% to have one routable address because you can<11:19:55.436> only<11:19:55.620> ever<11:19:56.400> have 11:19:57.290 --> 11:19:57.300 align:start position:0% can only ever have 11:19:57.300 --> 11:20:00.170 align:start position:0% can only ever have uh<11:19:57.900> one<11:19:58.200> connection<11:19:58.500> live<11:19:59.340> from<11:19:59.880> the<11:20:00.060> inside 11:20:00.170 --> 11:20:00.180 align:start position:0% uh one connection live from the inside 11:20:00.180 --> 11:20:02.990 align:start position:0% uh one connection live from the inside to<11:20:00.540> the<11:20:00.720> outside 11:20:02.990 --> 11:20:03.000 align:start position:0% 11:20:03.000 --> 11:20:05.266 align:start position:0% so<11:20:03.360> I've<11:20:03.480> covered<11:20:03.840> that<11:20:04.080> and<11:20:04.680> since<11:20:04.980> the 11:20:05.266 --> 11:20:05.276 align:start position:0% so I've covered that and since the 11:20:05.276 --> 11:20:07.070 align:start position:0% so I've covered that and since the source<11:20:05.700> private<11:20:06.000> IP<11:20:06.300> address<11:20:06.416> is<11:20:06.660> replaced 11:20:07.070 --> 11:20:07.080 align:start position:0% source private IP address is replaced 11:20:07.080 --> 11:20:09.830 align:start position:0% source private IP address is replaced with<11:20:07.200> an<11:20:07.320> external<11:20:07.820> public<11:20:08.820> address<11:20:09.480> it's 11:20:09.830 --> 11:20:09.840 align:start position:0% with an external public address it's 11:20:09.840 --> 11:20:11.510 align:start position:0% with an external public address it's called<11:20:10.020> sourcenat 11:20:11.510 --> 11:20:11.520 align:start position:0% called sourcenat 11:20:11.520 --> 11:20:13.970 align:start position:0% called sourcenat to<11:20:11.820> be<11:20:11.936> honest<11:20:12.120> I've<11:20:12.360> only<11:20:12.596> heard<11:20:13.380> um<11:20:13.380> the<11:20:13.800> term 11:20:13.970 --> 11:20:13.980 align:start position:0% to be honest I've only heard um the term 11:20:13.980 --> 11:20:16.010 align:start position:0% to be honest I've only heard um the term that's<11:20:14.340> used<11:20:14.756> in<11:20:15.300> all<11:20:15.480> my<11:20:15.596> years<11:20:15.776> on 11:20:16.010 --> 11:20:16.020 align:start position:0% that's used in all my years on 11:20:16.020 --> 11:20:18.050 align:start position:0% that's used in all my years on networking<11:20:16.620> but<11:20:16.860> you<11:20:17.340> need<11:20:17.520> to<11:20:17.640> be<11:20:17.700> familiar 11:20:18.050 --> 11:20:18.060 align:start position:0% networking but you need to be familiar 11:20:18.060 --> 11:20:19.310 align:start position:0% networking but you need to be familiar with<11:20:18.240> this<11:20:18.360> because<11:20:18.540> they've<11:20:18.776> put<11:20:18.900> it<11:20:19.020> in<11:20:19.140> the 11:20:19.310 --> 11:20:19.320 align:start position:0% with this because they've put it in the 11:20:19.320 --> 11:20:23.570 align:start position:0% with this because they've put it in the syllabus<11:20:20.160> for<11:20:20.520> some<11:20:20.640> reason 11:20:23.570 --> 11:20:23.580 align:start position:0% 11:20:23.580 --> 11:20:25.730 align:start position:0% okay<11:20:24.120> so<11:20:24.540> I've<11:20:24.840> covered<11:20:25.140> this<11:20:25.320> the<11:20:25.620> other 11:20:25.730 --> 11:20:25.740 align:start position:0% okay so I've covered this the other 11:20:25.740 --> 11:20:28.906 align:start position:0% okay so I've covered this the other thing<11:20:25.916> is<11:20:26.160> destination<11:20:26.936> Nat<11:20:27.720> this<11:20:28.620> is<11:20:28.740> where 11:20:28.906 --> 11:20:28.916 align:start position:0% thing is destination Nat this is where 11:20:28.916 --> 11:20:31.610 align:start position:0% thing is destination Nat this is where the<11:20:29.096> connection<11:20:29.220> has<11:20:29.640> been<11:20:29.820> initiated<11:20:30.620> from 11:20:31.610 --> 11:20:31.620 align:start position:0% the connection has been initiated from 11:20:31.620 --> 11:20:33.406 align:start position:0% the connection has been initiated from outside<11:20:31.980> the<11:20:32.276> network 11:20:33.406 --> 11:20:33.416 align:start position:0% outside the network 11:20:33.416 --> 11:20:37.730 align:start position:0% outside the network and<11:20:34.080> say<11:20:34.320> you've<11:20:34.620> got<11:20:34.800> some<11:20:35.160> sort<11:20:35.400> of<11:20:35.520> internal 11:20:37.730 --> 11:20:37.740 align:start position:0% and say you've got some sort of internal 11:20:37.740 --> 11:20:40.246 align:start position:0% and say you've got some sort of internal um<11:20:37.800> web<11:20:38.340> server<11:20:38.820> that<11:20:39.416> serves<11:20:39.720> members<11:20:40.080> of<11:20:40.140> the 11:20:40.246 --> 11:20:40.256 align:start position:0% um web server that serves members of the 11:20:40.256 --> 11:20:41.810 align:start position:0% um web server that serves members of the public<11:20:40.436> who<11:20:40.800> want<11:20:40.980> to<11:20:41.096> find<11:20:41.276> out<11:20:41.460> more<11:20:41.640> about 11:20:41.810 --> 11:20:41.820 align:start position:0% public who want to find out more about 11:20:41.820 --> 11:20:43.850 align:start position:0% public who want to find out more about your<11:20:42.120> company<11:20:42.360> you<11:20:43.080> normally<11:20:43.320> have<11:20:43.500> this<11:20:43.680> off 11:20:43.850 --> 11:20:43.860 align:start position:0% your company you normally have this off 11:20:43.860 --> 11:20:48.406 align:start position:0% your company you normally have this off a<11:20:44.040> DMZ<11:20:44.640> on<11:20:45.416> a<11:20:45.540> router<11:20:46.460> interface<11:20:47.460> also<11:20:48.000> or<11:20:48.120> a 11:20:48.406 --> 11:20:48.416 align:start position:0% a DMZ on a router interface also or a 11:20:48.416 --> 11:20:50.510 align:start position:0% a DMZ on a router interface also or a firewall<11:20:48.720> somewhere<11:20:49.200> so<11:20:49.980> this<11:20:50.160> time<11:20:50.340> the 11:20:50.510 --> 11:20:50.520 align:start position:0% firewall somewhere so this time the 11:20:50.520 --> 11:20:52.730 align:start position:0% firewall somewhere so this time the packet<11:20:50.936> has<11:20:51.120> come<11:20:51.360> from<11:20:51.720> and<11:20:52.020> the<11:20:52.320> in<11:20:52.436> the 11:20:52.730 --> 11:20:52.740 align:start position:0% packet has come from and the in the 11:20:52.740 --> 11:20:53.870 align:start position:0% packet has come from and the in the internet 11:20:53.870 --> 11:20:53.880 align:start position:0% internet 11:20:53.880 --> 11:20:56.510 align:start position:0% internet and<11:20:54.480> it's<11:20:54.596> hitting<11:20:55.200> your<11:20:55.380> router<11:20:55.916> and<11:20:56.340> your 11:20:56.510 --> 11:20:56.520 align:start position:0% and it's hitting your router and your 11:20:56.520 --> 11:20:58.850 align:start position:0% and it's hitting your router and your router<11:20:56.880> has<11:20:57.000> a<11:20:57.180> map<11:20:57.360> in<11:20:57.540> so<11:20:58.080> this<11:20:58.256> will<11:20:58.380> be<11:20:58.560> a 11:20:58.850 --> 11:20:58.860 align:start position:0% router has a map in so this will be a 11:20:58.860 --> 11:21:02.746 align:start position:0% router has a map in so this will be a permanently<11:20:59.900> permanently<11:21:00.900> featured<11:21:01.380> address 11:21:02.746 --> 11:21:02.756 align:start position:0% permanently permanently featured address 11:21:02.756 --> 11:21:04.850 align:start position:0% permanently permanently featured address um<11:21:02.880> a<11:21:03.240> mapping<11:21:03.660> inside<11:21:03.900> your<11:21:04.256> router<11:21:04.740> or 11:21:04.850 --> 11:21:04.860 align:start position:0% um a mapping inside your router or 11:21:04.860 --> 11:21:07.330 align:start position:0% um a mapping inside your router or firewall 11:21:07.330 --> 11:21:07.340 align:start position:0% firewall 11:21:07.340 --> 11:21:09.950 align:start position:0% firewall now<11:21:08.340> if<11:21:08.640> you<11:21:08.820> look<11:21:08.936> at<11:21:09.060> this<11:21:09.240> image<11:21:09.540> it's 11:21:09.950 --> 11:21:09.960 align:start position:0% now if you look at this image it's 11:21:09.960 --> 11:21:12.650 align:start position:0% now if you look at this image it's probably<11:21:10.340> would<11:21:11.340> make<11:21:11.520> more<11:21:11.820> sense<11:21:12.060> just<11:21:12.480> to 11:21:12.650 --> 11:21:12.660 align:start position:0% probably would make more sense just to 11:21:12.660 --> 11:21:15.170 align:start position:0% probably would make more sense just to have<11:21:12.840> a<11:21:13.080> routable<11:21:13.500> address<11:21:13.860> anyway<11:21:14.340> on<11:21:15.060> the 11:21:15.170 --> 11:21:15.180 align:start position:0% have a routable address anyway on the 11:21:15.180 --> 11:21:17.086 align:start position:0% have a routable address anyway on the inside<11:21:15.300> of<11:21:15.776> your 11:21:17.086 --> 11:21:17.096 align:start position:0% inside of your 11:21:17.096 --> 11:21:20.030 align:start position:0% inside of your um<11:21:17.160> Network<11:21:17.580> somewhere<11:21:18.180> in<11:21:18.480> the<11:21:18.660> DMZ 11:21:20.030 --> 11:21:20.040 align:start position:0% um Network somewhere in the DMZ 11:21:20.040 --> 11:21:22.310 align:start position:0% um Network somewhere in the DMZ the<11:21:20.700> demilitarized<11:21:21.360> zone<11:21:21.540> which<11:21:21.900> is<11:21:22.020> a<11:21:22.200> safe 11:21:22.310 --> 11:21:22.320 align:start position:0% the demilitarized zone which is a safe 11:21:22.320 --> 11:21:23.690 align:start position:0% the demilitarized zone which is a safe zone<11:21:22.680> for 11:21:23.690 --> 11:21:23.700 align:start position:0% zone for 11:21:23.700 --> 11:21:28.730 align:start position:0% zone for external<11:21:24.596> hosts<11:21:25.080> to<11:21:25.620> access<11:21:26.596> that<11:21:27.596> isn't<11:21:28.140> on 11:21:28.730 --> 11:21:28.740 align:start position:0% external hosts to access that isn't on 11:21:28.740 --> 11:21:30.766 align:start position:0% external hosts to access that isn't on the<11:21:28.916> same<11:21:29.160> interface<11:21:30.000> as<11:21:30.180> your<11:21:30.360> local<11:21:30.540> area 11:21:30.766 --> 11:21:30.776 align:start position:0% the same interface as your local area 11:21:30.776 --> 11:21:32.746 align:start position:0% the same interface as your local area network<11:21:31.140> that<11:21:31.980> would<11:21:32.096> probably<11:21:32.276> be<11:21:32.460> a<11:21:32.580> better 11:21:32.746 --> 11:21:32.756 align:start position:0% network that would probably be a better 11:21:32.756 --> 11:21:35.990 align:start position:0% network that would probably be a better idea<11:21:33.120> but<11:21:33.416> otherwise<11:21:33.840> this<11:21:34.500> destination<11:21:35.040> that 11:21:35.990 --> 11:21:36.000 align:start position:0% idea but otherwise this destination that 11:21:36.000 --> 11:21:38.690 align:start position:0% idea but otherwise this destination that is<11:21:36.240> an<11:21:36.416> option<11:21:36.900> here 11:21:38.690 --> 11:21:38.700 align:start position:0% is an option here 11:21:38.700 --> 11:21:42.230 align:start position:0% is an option here so<11:21:39.660> I've<11:21:39.840> mentioned<11:21:40.140> dmz's 11:21:42.230 --> 11:21:42.240 align:start position:0% so I've mentioned dmz's 11:21:42.240 --> 11:21:44.690 align:start position:0% so I've mentioned dmz's uh<11:21:43.200> through<11:21:43.500> our<11:21:43.680> public<11:21:43.860> facing<11:21:44.340> server 11:21:44.690 --> 11:21:44.700 align:start position:0% uh through our public facing server 11:21:44.700 --> 11:21:47.150 align:start position:0% uh through our public facing server Although<11:21:45.120> our<11:21:45.240> public<11:21:45.680> facing<11:21:46.680> server<11:21:46.916> has<11:21:47.040> an 11:21:47.150 --> 11:21:47.160 align:start position:0% Although our public facing server has an 11:21:47.160 --> 11:21:49.070 align:start position:0% Although our public facing server has an internal<11:21:47.520> IP<11:21:47.756> address<11:21:47.936> the<11:21:48.480> users<11:21:48.840> on<11:21:48.960> the 11:21:49.070 --> 11:21:49.080 align:start position:0% internal IP address the users on the 11:21:49.080 --> 11:21:50.810 align:start position:0% internal IP address the users on the internet<11:21:49.200> obviously<11:21:49.800> cannot<11:21:50.276> connect<11:21:50.400> to<11:21:50.700> it 11:21:50.810 --> 11:21:50.820 align:start position:0% internet obviously cannot connect to it 11:21:50.820 --> 11:21:53.870 align:start position:0% internet obviously cannot connect to it which<11:21:51.120> we've<11:21:51.300> already<11:21:51.480> covered<11:21:51.900> so<11:21:52.800> dnat<11:21:53.700> to 11:21:53.870 --> 11:21:53.880 align:start position:0% which we've already covered so dnat to 11:21:53.880 --> 11:21:56.690 align:start position:0% which we've already covered so dnat to destination<11:21:54.300> that<11:21:54.596> is<11:21:54.776> the<11:21:54.960> solution<11:21:55.320> there 11:21:56.690 --> 11:21:56.700 align:start position:0% destination that is the solution there 11:21:56.700 --> 11:21:58.670 align:start position:0% destination that is the solution there you<11:21:57.120> can<11:21:57.180> use<11:21:57.360> destination<11:21:57.776> app<11:21:58.140> for<11:21:58.380> load 11:21:58.670 --> 11:21:58.680 align:start position:0% you can use destination app for load 11:21:58.680 --> 11:21:59.870 align:start position:0% you can use destination app for load balancing 11:21:59.870 --> 11:21:59.880 align:start position:0% balancing 11:21:59.880 --> 11:22:01.730 align:start position:0% balancing um<11:22:00.000> the<11:22:00.540> traffic<11:22:00.720> coming<11:22:00.960> to<11:22:01.256> servers<11:22:01.560> from 11:22:01.730 --> 11:22:01.740 align:start position:0% um the traffic coming to servers from 11:22:01.740 --> 11:22:03.650 align:start position:0% um the traffic coming to servers from the<11:22:01.916> internet<11:22:02.040> so<11:22:02.880> you<11:22:03.000> could<11:22:03.120> have<11:22:03.300> three 11:22:03.650 --> 11:22:03.660 align:start position:0% the internet so you could have three 11:22:03.660 --> 11:22:05.690 align:start position:0% the internet so you could have three servers<11:22:04.140> low<11:22:04.436> balancing 11:22:05.690 --> 11:22:05.700 align:start position:0% servers low balancing 11:22:05.700 --> 11:22:07.970 align:start position:0% servers low balancing um<11:22:05.756> lots<11:22:06.120> of<11:22:06.180> web<11:22:06.360> connections<11:22:06.960> coming<11:22:07.200> in<11:22:07.436> and 11:22:07.970 --> 11:22:07.980 align:start position:0% um lots of web connections coming in and 11:22:07.980 --> 11:22:09.766 align:start position:0% um lots of web connections coming in and there's<11:22:08.160> different<11:22:08.340> types<11:22:08.820> of<11:22:08.936> device<11:22:09.416> you 11:22:09.766 --> 11:22:09.776 align:start position:0% there's different types of device you 11:22:09.776 --> 11:22:12.110 align:start position:0% there's different types of device you can<11:22:09.900> actually<11:22:10.080> use<11:22:10.500> for<11:22:10.740> this 11:22:12.110 --> 11:22:12.120 align:start position:0% can actually use for this 11:22:12.120 --> 11:22:13.730 align:start position:0% can actually use for this um and<11:22:12.360> so<11:22:12.480> it's<11:22:12.660> all<11:22:12.776> getting<11:22:13.020> load<11:22:13.380> balanced 11:22:13.730 --> 11:22:13.740 align:start position:0% um and so it's all getting load balanced 11:22:13.740 --> 11:22:16.490 align:start position:0% um and so it's all getting load balanced to<11:22:13.980> one<11:22:14.220> routerable<11:22:15.120> IP<11:22:15.416> address<11:22:15.596> but<11:22:16.080> then 11:22:16.490 --> 11:22:16.500 align:start position:0% to one routerable IP address but then 11:22:16.500 --> 11:22:19.610 align:start position:0% to one routerable IP address but then two<11:22:16.800> three<11:22:17.096> four<11:22:17.340> or<11:22:17.700> more<11:22:17.936> and<11:22:18.840> non-routable 11:22:19.610 --> 11:22:19.620 align:start position:0% two three four or more and non-routable 11:22:19.620 --> 11:22:24.230 align:start position:0% two three four or more and non-routable addresses<11:22:20.096> on<11:22:20.276> the<11:22:20.400> inside<11:22:20.520> of<11:22:20.820> your<11:22:20.936> network 11:22:24.230 --> 11:22:24.240 align:start position:0% 11:22:24.240 --> 11:22:26.630 align:start position:0% so<11:22:24.900> when<11:22:25.140> the<11:22:25.256> user<11:22:25.560> sends<11:22:25.916> a<11:22:25.980> packet<11:22:26.340> it 11:22:26.630 --> 11:22:26.640 align:start position:0% so when the user sends a packet it 11:22:26.640 --> 11:22:29.030 align:start position:0% so when the user sends a packet it changes<11:22:27.120> the<11:22:27.660> destination<11:22:28.140> public<11:22:28.560> IP 11:22:29.030 --> 11:22:29.040 align:start position:0% changes the destination public IP 11:22:29.040 --> 11:22:31.426 align:start position:0% changes the destination public IP address<11:22:29.360> and<11:22:30.360> to<11:22:30.596> one<11:22:30.776> of<11:22:30.960> the<11:22:31.080> internal 11:22:31.426 --> 11:22:31.436 align:start position:0% address and to one of the internal 11:22:31.436 --> 11:22:34.070 align:start position:0% address and to one of the internal private<11:22:31.800> IP<11:22:32.096> addresses 11:22:34.070 --> 11:22:34.080 align:start position:0% private IP addresses 11:22:34.080 --> 11:22:36.050 align:start position:0% private IP addresses the<11:22:34.500> last<11:22:34.680> thing<11:22:34.860> is<11:22:34.980> Pat<11:22:35.276> which<11:22:35.640> is<11:22:35.820> actually 11:22:36.050 --> 11:22:36.060 align:start position:0% the last thing is Pat which is actually 11:22:36.060 --> 11:22:38.810 align:start position:0% the last thing is Pat which is actually used<11:22:36.540> more<11:22:36.900> often<11:22:37.320> than<11:22:37.560> that 11:22:38.810 --> 11:22:38.820 align:start position:0% used more often than that 11:22:38.820 --> 11:22:41.390 align:start position:0% used more often than that port<11:22:39.180> address<11:22:39.360> translation<11:22:40.080> normally<11:22:40.680> when 11:22:41.390 --> 11:22:41.400 align:start position:0% port address translation normally when 11:22:41.400 --> 11:22:43.850 align:start position:0% port address translation normally when you<11:22:41.580> have<11:22:42.300> a<11:22:42.480> small<11:22:42.660> company<11:22:43.020> you'll<11:22:43.740> be 11:22:43.850 --> 11:22:43.860 align:start position:0% you have a small company you'll be 11:22:43.860 --> 11:22:46.490 align:start position:0% you have a small company you'll be allocated<11:22:44.276> a<11:22:44.700> single<11:22:44.936> IP<11:22:45.300> address<11:22:45.540> but<11:22:46.320> you 11:22:46.490 --> 11:22:46.500 align:start position:0% allocated a single IP address but you 11:22:46.500 --> 11:22:48.766 align:start position:0% allocated a single IP address but you still<11:22:46.740> want<11:22:46.916> to<11:22:47.096> do<11:22:47.220> nothing<11:22:47.480> so<11:22:48.480> what<11:22:48.660> this 11:22:48.766 --> 11:22:48.776 align:start position:0% still want to do nothing so what this 11:22:48.776 --> 11:22:51.050 align:start position:0% still want to do nothing so what this does<11:22:48.960> is<11:22:49.140> it<11:22:49.380> uses<11:22:49.740> your<11:22:49.916> oneop<11:22:50.340> address<11:22:50.700> but 11:22:51.050 --> 11:22:51.060 align:start position:0% does is it uses your oneop address but 11:22:51.060 --> 11:22:53.870 align:start position:0% does is it uses your oneop address but uses<11:22:51.480> port<11:22:51.720> numbers<11:22:52.096> after<11:22:53.096> the<11:22:53.340> IP<11:22:53.640> address 11:22:53.870 --> 11:22:53.880 align:start position:0% uses port numbers after the IP address 11:22:53.880 --> 11:22:57.230 align:start position:0% uses port numbers after the IP address for<11:22:54.300> source<11:22:54.720> and<11:22:54.840> destination 11:22:57.230 --> 11:22:57.240 align:start position:0% for source and destination 11:22:57.240 --> 11:23:00.170 align:start position:0% for source and destination so<11:22:58.080> this<11:22:58.436> is<11:22:58.620> the<11:22:59.096> this<11:22:59.400> is<11:22:59.580> the<11:22:59.820> solution 11:23:00.170 --> 11:23:00.180 align:start position:0% so this is the this is the solution 11:23:00.180 --> 11:23:02.086 align:start position:0% so this is the this is the solution normally 11:23:02.086 --> 11:23:02.096 align:start position:0% normally 11:23:02.096 --> 11:23:05.030 align:start position:0% normally um<11:23:02.160> for<11:23:02.756> this<11:23:02.936> solution<11:23:03.240> here<11:23:03.540> you'd<11:23:03.840> have<11:23:04.040> a 11:23:05.030 --> 11:23:05.040 align:start position:0% um for this solution here you'd have a 11:23:05.040 --> 11:23:08.570 align:start position:0% um for this solution here you'd have a static<11:23:05.580> IP<11:23:06.540> address<11:23:06.720> in<11:23:07.140> one<11:23:07.436> to<11:23:07.620> one<11:23:07.860> but<11:23:08.400> you 11:23:08.570 --> 11:23:08.580 align:start position:0% static IP address in one to one but you 11:23:08.580 --> 11:23:10.070 align:start position:0% static IP address in one to one but you can't<11:23:08.700> afford<11:23:09.000> that<11:23:09.120> for<11:23:09.300> whatever<11:23:09.480> reason<11:23:09.776> so 11:23:10.070 --> 11:23:10.080 align:start position:0% can't afford that for whatever reason so 11:23:10.080 --> 11:23:11.630 align:start position:0% can't afford that for whatever reason so you've<11:23:10.256> just<11:23:10.380> got<11:23:10.500> one<11:23:10.916> IP<11:23:11.520> address 11:23:11.630 --> 11:23:11.640 align:start position:0% you've just got one IP address 11:23:11.640 --> 11:23:13.610 align:start position:0% you've just got one IP address externally<11:23:12.300> but<11:23:12.596> several<11:23:12.960> hosts<11:23:13.320> on<11:23:13.500> the 11:23:13.610 --> 11:23:13.620 align:start position:0% externally but several hosts on the 11:23:13.620 --> 11:23:16.010 align:start position:0% externally but several hosts on the inside 11:23:16.010 --> 11:23:16.020 align:start position:0% 11:23:16.020 --> 11:23:19.130 align:start position:0% so<11:23:16.500> what<11:23:16.740> we<11:23:16.980> have<11:23:17.220> is<11:23:17.756> a<11:23:18.000> port<11:23:18.180> number<11:23:18.480> for 11:23:19.130 --> 11:23:19.140 align:start position:0% so what we have is a port number for 11:23:19.140 --> 11:23:22.730 align:start position:0% so what we have is a port number for example<11:23:19.380> 192<11:23:19.980> 168<11:23:20.580> 1.3<11:23:21.240> and<11:23:22.080> then<11:23:22.200> a<11:23:22.500> port 11:23:22.730 --> 11:23:22.740 align:start position:0% example 192 168 1.3 and then a port 11:23:22.740 --> 11:23:26.450 align:start position:0% example 192 168 1.3 and then a port number<11:23:23.416> your<11:23:24.416> connection<11:23:24.596> would<11:23:25.200> go<11:23:25.436> out 11:23:26.450 --> 11:23:26.460 align:start position:0% number your connection would go out 11:23:26.460 --> 11:23:29.630 align:start position:0% number your connection would go out on<11:23:27.360> a<11:23:27.720> specific<11:23:28.080> port<11:23:28.860> number<11:23:29.160> for<11:23:29.400> example 11:23:29.630 --> 11:23:29.640 align:start position:0% on a specific port number for example 11:23:29.640 --> 11:23:31.190 align:start position:0% on a specific port number for example Port<11:23:29.936> 80<11:23:30.240> if<11:23:30.596> you<11:23:30.720> were<11:23:30.776> doing<11:23:30.900> a<11:23:31.080> web 11:23:31.190 --> 11:23:31.200 align:start position:0% Port 80 if you were doing a web 11:23:31.200 --> 11:23:33.830 align:start position:0% Port 80 if you were doing a web connection<11:23:31.436> but<11:23:32.340> it<11:23:32.520> would<11:23:32.640> come<11:23:32.880> back<11:23:33.060> in<11:23:33.300> and 11:23:33.830 --> 11:23:33.840 align:start position:0% connection but it would come back in and 11:23:33.840 --> 11:23:37.190 align:start position:0% connection but it would come back in and then<11:23:33.960> get<11:23:34.200> changed<11:23:34.740> to<11:23:35.180> a<11:23:36.180> a<11:23:36.416> random<11:23:37.020> port 11:23:37.190 --> 11:23:37.200 align:start position:0% then get changed to a a random port 11:23:37.200 --> 11:23:39.766 align:start position:0% then get changed to a a random port number<11:23:37.560> or<11:23:38.276> you<11:23:38.520> can<11:23:38.640> configure<11:23:39.120> a<11:23:39.300> range<11:23:39.596> of 11:23:39.766 --> 11:23:39.776 align:start position:0% number or you can configure a range of 11:23:39.776 --> 11:23:42.766 align:start position:0% number or you can configure a range of usable<11:23:40.620> port<11:23:40.860> numbers<11:23:41.220> that<11:23:42.120> are<11:23:42.300> outside<11:23:42.480> the 11:23:42.766 --> 11:23:42.776 align:start position:0% usable port numbers that are outside the 11:23:42.776 --> 11:23:47.510 align:start position:0% usable port numbers that are outside the well-known<11:23:43.256> port<11:23:43.500> numbers<11:23:43.800> of<11:23:44.220> m0<11:23:44.820> to<11:23:45.240> 10<11:23:46.140> 23<11:23:47.096> I 11:23:47.510 --> 11:23:47.520 align:start position:0% well-known port numbers of m0 to 10 23 I 11:23:47.520 --> 11:23:51.766 align:start position:0% well-known port numbers of m0 to 10 23 I think<11:23:47.640> it<11:23:47.820> is 11:23:51.766 --> 11:23:51.776 align:start position:0% 11:23:51.776 --> 11:23:53.630 align:start position:0% when<11:23:52.140> the<11:23:52.320> internal<11:23:52.620> host<11:23:52.800> of<11:23:52.980> the<11:23:53.096> private<11:23:53.340> IP 11:23:53.630 --> 11:23:53.640 align:start position:0% when the internal host of the private IP 11:23:53.640 --> 11:23:55.310 align:start position:0% when the internal host of the private IP address<11:23:53.820> initiates<11:23:54.540> the<11:23:54.720> session<11:23:54.960> it<11:23:55.200> will 11:23:55.310 --> 11:23:55.320 align:start position:0% address initiates the session it will 11:23:55.320 --> 11:23:58.070 align:start position:0% address initiates the session it will generate<11:23:55.680> a<11:23:55.800> TCP<11:23:56.340> or<11:23:56.700> UDP<11:23:57.060> port<11:23:57.300> and<11:23:57.840> that's 11:23:58.070 --> 11:23:58.080 align:start position:0% generate a TCP or UDP port and that's 11:23:58.080 --> 11:24:00.050 align:start position:0% generate a TCP or UDP port and that's just<11:23:58.200> unique<11:23:58.500> to<11:23:58.680> that<11:23:58.860> session<11:23:59.160> so<11:23:59.756> you<11:23:59.936> can 11:24:00.050 --> 11:24:00.060 align:start position:0% just unique to that session so you can 11:24:00.060 --> 11:24:03.010 align:start position:0% just unique to that session so you can see<11:24:00.180> here<11:24:00.416> internally<11:24:00.900> we've<11:24:01.200> got<11:24:01.320> Port 11:24:03.010 --> 11:24:03.020 align:start position:0% see here internally we've got Port 11:24:03.020 --> 11:24:06.950 align:start position:0% see here internally we've got Port 15345<11:24:04.020> externally<11:24:04.756> two<11:24:05.756> zero<11:24:06.120> two<11:24:06.416> zero<11:24:06.720> one 11:24:06.950 --> 11:24:06.960 align:start position:0% 15345 externally two zero two zero one 11:24:06.960 --> 11:24:09.350 align:start position:0% 15345 externally two zero two zero one to<11:24:07.560> be<11:24:07.740> honest<11:24:07.916> it<11:24:08.160> would<11:24:08.340> normally<11:24:08.640> be<11:24:08.936> a 11:24:09.350 --> 11:24:09.360 align:start position:0% to be honest it would normally be a 11:24:09.360 --> 11:24:12.950 align:start position:0% to be honest it would normally be a well-known<11:24:09.900> port<11:24:10.140> number<11:24:10.436> such<11:24:11.220> as<11:24:11.400> a<11:24:11.700> FTP<11:24:12.240> DNS 11:24:12.950 --> 11:24:12.960 align:start position:0% well-known port number such as a FTP DNS 11:24:12.960 --> 11:24:16.850 align:start position:0% well-known port number such as a FTP DNS or<11:24:13.200> web<11:24:13.436> traffic 11:24:16.850 --> 11:24:16.860 align:start position:0% 11:24:16.860 --> 11:24:18.230 align:start position:0% yeah 11:24:18.230 --> 11:24:18.240 align:start position:0% yeah 11:24:18.240 --> 11:24:20.990 align:start position:0% yeah this<11:24:18.900> port<11:24:19.560> um<11:24:19.560> mapping<11:24:20.040> is<11:24:20.276> kept<11:24:20.580> on<11:24:20.756> a<11:24:20.880> table 11:24:20.990 --> 11:24:21.000 align:start position:0% this port um mapping is kept on a table 11:24:21.000 --> 11:24:23.690 align:start position:0% this port um mapping is kept on a table inside<11:24:21.360> the<11:24:21.596> router<11:24:22.020> it<11:24:22.620> does<11:24:22.740> expire<11:24:23.160> after<11:24:23.400> a 11:24:23.690 --> 11:24:23.700 align:start position:0% inside the router it does expire after a 11:24:23.700 --> 11:24:26.030 align:start position:0% inside the router it does expire after a while<11:24:23.820> just<11:24:24.180> to<11:24:24.300> clear<11:24:24.480> the<11:24:24.720> table<11:24:25.040> but 11:24:26.030 --> 11:24:26.040 align:start position:0% while just to clear the table but 11:24:26.040 --> 11:24:27.110 align:start position:0% while just to clear the table but normally 11:24:27.110 --> 11:24:27.120 align:start position:0% normally 11:24:27.120 --> 11:24:28.310 align:start position:0% normally um more<11:24:27.360> than<11:24:27.416> enough<11:24:27.660> time<11:24:27.960> for<11:24:28.080> you<11:24:28.200> to 11:24:28.310 --> 11:24:28.320 align:start position:0% um more than enough time for you to 11:24:28.320 --> 11:24:30.290 align:start position:0% um more than enough time for you to complete<11:24:28.620> all<11:24:28.800> of<11:24:28.916> your<11:24:29.040> sessions<11:24:29.520> but<11:24:30.060> that 11:24:30.290 --> 11:24:30.300 align:start position:0% complete all of your sessions but that 11:24:30.300 --> 11:24:33.470 align:start position:0% complete all of your sessions but that end<11:24:30.540> table<11:24:31.080> expiration<11:24:31.860> time<11:24:32.276> can<11:24:32.936> be<11:24:33.120> altered 11:24:33.470 --> 11:24:33.480 align:start position:0% end table expiration time can be altered 11:24:33.480 --> 11:24:37.130 align:start position:0% end table expiration time can be altered on<11:24:33.660> the<11:24:33.776> router 11:24:37.130 --> 11:24:37.140 align:start position:0% 11:24:37.140 --> 11:24:41.810 align:start position:0% all<11:24:37.620> right<11:24:37.800> so<11:24:38.220> now<11:24:38.700> at<11:24:39.060> ipv4<11:24:40.096> IPv6<11:24:41.096> which<11:24:41.460> is<11:24:41.640> a 11:24:41.810 --> 11:24:41.820 align:start position:0% all right so now at ipv4 IPv6 which is a 11:24:41.820 --> 11:24:44.266 align:start position:0% all right so now at ipv4 IPv6 which is a solution<11:24:42.120> to<11:24:42.596> address<11:24:43.080> to<11:24:43.380> depletion<11:24:43.916> but<11:24:44.160> we 11:24:44.266 --> 11:24:44.276 align:start position:0% solution to address to depletion but we 11:24:44.276 --> 11:24:47.086 align:start position:0% solution to address to depletion but we don't<11:24:44.460> really<11:24:44.640> use<11:24:45.360> that<11:24:45.660> much<11:24:46.436> at<11:24:46.740> all<11:24:46.860> with 11:24:47.086 --> 11:24:47.096 align:start position:0% don't really use that much at all with 11:24:47.096 --> 11:24:50.330 align:start position:0% don't really use that much at all with IPv6<11:24:48.080> some<11:24:49.080> of<11:24:49.256> the<11:24:49.320> advantages<11:24:49.740> remember 11:24:50.330 --> 11:24:50.340 align:start position:0% IPv6 some of the advantages remember 11:24:50.340 --> 11:24:53.030 align:start position:0% IPv6 some of the advantages remember security<11:24:50.820> and<11:24:51.360> also<11:24:51.720> you<11:24:52.320> get<11:24:52.436> to<11:24:52.560> use<11:24:52.680> lots<11:24:52.980> of 11:24:53.030 --> 11:24:53.040 align:start position:0% security and also you get to use lots of 11:24:53.040 --> 11:24:54.490 align:start position:0% security and also you get to use lots of addresses<11:24:53.460> on<11:24:53.640> the<11:24:53.756> inside<11:24:53.880> of<11:24:54.120> your<11:24:54.180> network 11:24:54.490 --> 11:24:54.500 align:start position:0% addresses on the inside of your network 11:24:54.500 --> 11:24:57.950 align:start position:0% addresses on the inside of your network and<11:24:55.500> and<11:24:55.740> up<11:24:56.040> and<11:24:56.756> and<11:24:56.936> one<11:24:57.180> address<11:24:57.360> or<11:24:57.660> more 11:24:57.950 --> 11:24:57.960 align:start position:0% and and up and and one address or more 11:24:57.960 --> 11:25:00.470 align:start position:0% and and up and and one address or more on<11:24:58.500> the<11:24:58.620> outside<11:24:58.740> of<11:24:59.040> your<11:24:59.220> network 11:25:00.470 --> 11:25:00.480 align:start position:0% on the outside of your network 11:25:00.480 --> 11:25:02.570 align:start position:0% on the outside of your network all<11:25:01.080> right<11:25:01.256> so<11:25:01.436> that's<11:25:01.620> all<11:25:01.800> for<11:25:02.040> now<11:25:02.220> thanks 11:25:02.570 --> 11:25:02.580 align:start position:0% all right so that's all for now thanks 11:25:02.580 --> 11:25:08.350 align:start position:0% all right so that's all for now thanks for<11:25:02.756> watching 11:25:08.350 --> 11:25:08.360 align:start position:0% 11:25:08.360 --> 11:25:28.450 align:start position:0% [Music] 11:25:28.450 --> 11:25:28.460 align:start position:0% 11:25:28.460 --> 11:25:30.190 align:start position:0% tcpip 11:25:30.190 --> 11:25:30.200 align:start position:0% tcpip 11:25:30.200 --> 11:25:33.830 align:start position:0% tcpip tcpip<11:25:31.200> simple<11:25:32.096> services 11:25:33.830 --> 11:25:33.840 align:start position:0% tcpip simple services 11:25:33.840 --> 11:25:36.470 align:start position:0% tcpip simple services in<11:25:34.436> the<11:25:34.560> previous<11:25:34.680> module<11:25:35.276> and<11:25:35.400> lesson<11:25:35.756> we 11:25:36.470 --> 11:25:36.480 align:start position:0% in the previous module and lesson we 11:25:36.480 --> 11:25:39.110 align:start position:0% in the previous module and lesson we discussed<11:25:36.960> the<11:25:37.080> way<11:25:37.320> that<11:25:37.620> IP<11:25:37.980> addresses<11:25:38.580> are 11:25:39.110 --> 11:25:39.120 align:start position:0% discussed the way that IP addresses are 11:25:39.120 --> 11:25:41.926 align:start position:0% discussed the way that IP addresses are assigned<11:25:39.596> now<11:25:40.200> in<11:25:40.500> this<11:25:40.800> next<11:25:41.220> lesson<11:25:41.700> we're 11:25:41.926 --> 11:25:41.936 align:start position:0% assigned now in this next lesson we're 11:25:41.936 --> 11:25:44.926 align:start position:0% assigned now in this next lesson we're going<11:25:42.060> to<11:25:42.180> be<11:25:42.240> talking<11:25:42.596> more<11:25:43.140> about<11:25:43.740> the<11:25:44.160> tcpip 11:25:44.926 --> 11:25:44.936 align:start position:0% going to be talking more about the tcpip 11:25:44.936 --> 11:25:48.766 align:start position:0% going to be talking more about the tcpip suite<11:25:45.660> and<11:25:46.500> specifically<11:25:47.096> in<11:25:47.640> this<11:25:47.820> module<11:25:48.240> I 11:25:48.766 --> 11:25:48.776 align:start position:0% suite and specifically in this module I 11:25:48.776 --> 11:25:50.810 align:start position:0% suite and specifically in this module I want<11:25:48.900> to<11:25:49.020> discuss<11:25:49.380> some<11:25:49.680> of<11:25:49.860> the<11:25:50.160> simple 11:25:50.810 --> 11:25:50.820 align:start position:0% want to discuss some of the simple 11:25:50.820 --> 11:25:55.130 align:start position:0% want to discuss some of the simple services<11:25:51.860> that<11:25:52.860> are<11:25:53.160> in<11:25:53.520> the<11:25:53.820> tcpip<11:25:54.540> suite 11:25:55.130 --> 11:25:55.140 align:start position:0% services that are in the tcpip suite 11:25:55.140 --> 11:25:58.730 align:start position:0% services that are in the tcpip suite what<11:25:55.680> they<11:25:55.860> do<11:25:56.040> and<11:25:56.880> what<11:25:57.120> some<11:25:57.416> of<11:25:57.596> the<11:25:58.020> output 11:25:58.730 --> 11:25:58.740 align:start position:0% what they do and what some of the output 11:25:58.740 --> 11:26:00.766 align:start position:0% what they do and what some of the output might<11:25:59.160> look<11:25:59.400> like<11:25:59.580> for<11:26:00.180> some<11:26:00.360> of<11:26:00.480> the<11:26:00.596> services 11:26:00.766 --> 11:26:00.776 align:start position:0% might look like for some of the services 11:26:00.776 --> 11:26:03.050 align:start position:0% might look like for some of the services and<11:26:01.320> why<11:26:01.500> we<11:26:01.680> might<11:26:01.800> not<11:26:01.980> see<11:26:02.220> output<11:26:02.580> for<11:26:02.880> some 11:26:03.050 --> 11:26:03.060 align:start position:0% and why we might not see output for some 11:26:03.060 --> 11:26:04.730 align:start position:0% and why we might not see output for some of<11:26:03.180> the<11:26:03.360> other<11:26:03.480> services 11:26:04.730 --> 11:26:04.740 align:start position:0% of the other services 11:26:04.740 --> 11:26:06.766 align:start position:0% of the other services now<11:26:05.276> you<11:26:05.520> might<11:26:05.640> see<11:26:05.820> this<11:26:06.000> on<11:26:06.180> the<11:26:06.300> exam<11:26:06.596> and 11:26:06.766 --> 11:26:06.776 align:start position:0% now you might see this on the exam and 11:26:06.776 --> 11:26:09.890 align:start position:0% now you might see this on the exam and you<11:26:06.960> might<11:26:07.140> not<11:26:07.380> but<11:26:08.096> either<11:26:08.340> way<11:26:08.580> it's<11:26:09.480> a<11:26:09.720> good 11:26:09.890 --> 11:26:09.900 align:start position:0% you might not but either way it's a good 11:26:09.900 --> 11:26:12.890 align:start position:0% you might not but either way it's a good thing<11:26:10.380> to<11:26:10.740> know<11:26:10.916> about<11:26:11.160> and<11:26:11.640> just<11:26:11.880> in<11:26:12.060> case 11:26:12.890 --> 11:26:12.900 align:start position:0% thing to know about and just in case 11:26:12.900 --> 11:26:16.010 align:start position:0% thing to know about and just in case now<11:26:13.500> first<11:26:14.160> we're<11:26:14.460> going<11:26:14.580> to<11:26:14.756> talk<11:26:14.936> about<11:26:15.180> all 11:26:16.010 --> 11:26:16.020 align:start position:0% now first we're going to talk about all 11:26:16.020 --> 11:26:18.290 align:start position:0% now first we're going to talk about all of<11:26:16.080> these<11:26:16.380> different<11:26:16.500> simple<11:26:16.980> tcpip<11:26:17.880> services 11:26:18.290 --> 11:26:18.300 align:start position:0% of these different simple tcpip services 11:26:18.300 --> 11:26:20.210 align:start position:0% of these different simple tcpip services and<11:26:19.140> in<11:26:19.320> some<11:26:19.436> cases<11:26:19.680> we're<11:26:19.916> going<11:26:20.040> to 11:26:20.210 --> 11:26:20.220 align:start position:0% and in some cases we're going to 11:26:20.220 --> 11:26:22.310 align:start position:0% and in some cases we're going to demonstrate<11:26:20.640> them<11:26:20.880> and<11:26:21.660> just<11:26:21.900> to<11:26:22.020> give<11:26:22.140> you<11:26:22.256> an 11:26:22.310 --> 11:26:22.320 align:start position:0% demonstrate them and just to give you an 11:26:22.320 --> 11:26:24.110 align:start position:0% demonstrate them and just to give you an overview<11:26:22.560> of<11:26:22.680> what<11:26:22.860> these<11:26:23.096> are<11:26:23.220> these<11:26:24.000> are 11:26:24.110 --> 11:26:24.120 align:start position:0% overview of what these are these are 11:26:24.120 --> 11:26:26.926 align:start position:0% overview of what these are these are cargen<11:26:24.720> or<11:26:25.256> charge<11:26:25.620> in<11:26:25.916> or<11:26:26.400> character 11:26:26.926 --> 11:26:26.936 align:start position:0% cargen or charge in or character 11:26:26.936 --> 11:26:28.906 align:start position:0% cargen or charge in or character generation 11:26:28.906 --> 11:26:28.916 align:start position:0% generation 11:26:28.916 --> 11:26:31.070 align:start position:0% generation the<11:26:29.220> daytime<11:26:29.580> service 11:26:31.070 --> 11:26:31.080 align:start position:0% the daytime service 11:26:31.080 --> 11:26:33.530 align:start position:0% the daytime service the<11:26:31.740> discard<11:26:32.096> service 11:26:33.530 --> 11:26:33.540 align:start position:0% the discard service 11:26:33.540 --> 11:26:36.406 align:start position:0% the discard service the<11:26:34.080> echo<11:26:34.436> service<11:26:34.756> and<11:26:35.756> quote<11:26:36.060> of<11:26:36.180> the<11:26:36.300> day 11:26:36.406 --> 11:26:36.416 align:start position:0% the echo service and quote of the day 11:26:36.416 --> 11:26:38.690 align:start position:0% the echo service and quote of the day service<11:26:36.660> now<11:26:37.620> some<11:26:37.860> of<11:26:37.980> these<11:26:38.096> happen<11:26:38.276> in<11:26:38.520> the 11:26:38.690 --> 11:26:38.700 align:start position:0% service now some of these happen in the 11:26:38.700 --> 11:26:40.370 align:start position:0% service now some of these happen in the background<11:26:38.936> are<11:26:39.240> sort<11:26:39.660> of<11:26:39.720> embedded<11:26:40.200> into 11:26:40.370 --> 11:26:40.380 align:start position:0% background are sort of embedded into 11:26:40.380 --> 11:26:43.426 align:start position:0% background are sort of embedded into other<11:26:41.240> protocols<11:26:42.240> and<11:26:42.596> services<11:26:42.840> that<11:26:43.320> we 11:26:43.426 --> 11:26:43.436 align:start position:0% other protocols and services that we 11:26:43.436 --> 11:26:45.110 align:start position:0% other protocols and services that we might<11:26:43.560> have<11:26:43.680> seen<11:26:43.916> but<11:26:44.460> these<11:26:44.640> are<11:26:44.756> important 11:26:45.110 --> 11:26:45.120 align:start position:0% might have seen but these are important 11:26:45.120 --> 11:26:47.266 align:start position:0% might have seen but these are important again<11:26:45.300> to<11:26:45.900> know<11:26:46.020> about<11:26:46.200> in<11:26:46.620> a<11:26:46.800> sort<11:26:46.916> of<11:26:47.040> General 11:26:47.266 --> 11:26:47.276 align:start position:0% again to know about in a sort of General 11:26:47.276 --> 11:26:48.470 align:start position:0% again to know about in a sort of General way 11:26:48.470 --> 11:26:48.480 align:start position:0% way 11:26:48.480 --> 11:26:50.406 align:start position:0% way so 11:26:50.406 --> 11:26:50.416 align:start position:0% so 11:26:50.416 --> 11:26:54.950 align:start position:0% so the<11:26:51.416> five<11:26:51.720> uh<11:26:52.380> simple<11:26:52.680> tcpip<11:26:53.640> services<11:26:54.180> are 11:26:54.950 --> 11:26:54.960 align:start position:0% the five uh simple tcpip services are 11:26:54.960 --> 11:26:56.990 align:start position:0% the five uh simple tcpip services are listed<11:26:55.320> here<11:26:55.620> along<11:26:56.160> with<11:26:56.400> the<11:26:56.580> description 11:26:56.990 --> 11:26:57.000 align:start position:0% listed here along with the description 11:26:57.000 --> 11:26:59.630 align:start position:0% listed here along with the description of<11:26:57.660> what<11:26:57.900> it<11:26:58.020> is<11:26:58.140> they<11:26:58.500> do 11:26:59.630 --> 11:26:59.640 align:start position:0% of what it is they do 11:26:59.640 --> 11:27:02.990 align:start position:0% of what it is they do cargan<11:27:00.360> or<11:27:01.256> character<11:27:01.916> generation<11:27:02.400> or<11:27:02.756> charge 11:27:02.990 --> 11:27:03.000 align:start position:0% cargan or character generation or charge 11:27:03.000 --> 11:27:06.830 align:start position:0% cargan or character generation or charge n<11:27:03.360> or<11:27:03.596> whatever<11:27:04.140> the<11:27:04.620> uh<11:27:05.160> preferred<11:27:05.820> way<11:27:06.596> that 11:27:06.830 --> 11:27:06.840 align:start position:0% n or whatever the uh preferred way that 11:27:06.840 --> 11:27:08.150 align:start position:0% n or whatever the uh preferred way that you<11:27:06.960> want<11:27:07.080> to<11:27:07.200> pronounce<11:27:07.436> it<11:27:07.620> is<11:27:07.800> is 11:27:08.150 --> 11:27:08.160 align:start position:0% you want to pronounce it is is 11:27:08.160 --> 11:27:10.490 align:start position:0% you want to pronounce it is is essentially<11:27:08.640> what<11:27:09.000> you<11:27:09.120> get<11:27:09.360> anytime<11:27:10.256> you 11:27:10.490 --> 11:27:10.500 align:start position:0% essentially what you get anytime you 11:27:10.500 --> 11:27:14.086 align:start position:0% essentially what you get anytime you choose<11:27:10.740> the<11:27:10.916> option<11:27:11.300> send<11:27:12.300> test<11:27:12.840> page<11:27:13.320> to<11:27:13.980> a 11:27:14.086 --> 11:27:14.096 align:start position:0% choose the option send test page to a 11:27:14.096 --> 11:27:16.730 align:start position:0% choose the option send test page to a printer<11:27:14.460> it's<11:27:15.300> made<11:27:15.596> up<11:27:15.776> of<11:27:15.960> ASCII<11:27:16.500> characters 11:27:16.730 --> 11:27:16.740 align:start position:0% printer it's made up of ASCII characters 11:27:16.740 --> 11:27:20.290 align:start position:0% printer it's made up of ASCII characters and<11:27:17.276> ASCII<11:27:17.756> again<11:27:17.880> stands<11:27:18.416> for<11:27:18.660> the<11:27:19.560> American 11:27:20.290 --> 11:27:20.300 align:start position:0% and ASCII again stands for the American 11:27:20.300 --> 11:27:23.810 align:start position:0% and ASCII again stands for the American Standard<11:27:21.300> code 11:27:23.810 --> 11:27:23.820 align:start position:0% Standard code 11:27:23.820 --> 11:27:25.510 align:start position:0% Standard code for<11:27:24.540> information 11:27:25.510 --> 11:27:25.520 align:start position:0% for information 11:27:25.520 --> 11:27:29.050 align:start position:0% for information interchange<11:27:26.520> so<11:27:27.480> this<11:27:27.840> is<11:27:28.080> usually<11:27:28.436> used<11:27:28.680> as<11:27:28.860> a 11:27:29.050 --> 11:27:29.060 align:start position:0% interchange so this is usually used as a 11:27:29.060 --> 11:27:32.570 align:start position:0% interchange so this is usually used as a debugging<11:27:30.060> tool<11:27:30.360> when<11:27:30.596> you're<11:27:31.020> uh<11:27:31.980> creating 11:27:32.570 --> 11:27:32.580 align:start position:0% debugging tool when you're uh creating 11:27:32.580 --> 11:27:34.606 align:start position:0% debugging tool when you're uh creating or<11:27:32.880> troubleshooting<11:27:33.540> printers<11:27:34.020> or<11:27:34.380> print 11:27:34.606 --> 11:27:34.616 align:start position:0% or troubleshooting printers or print 11:27:34.616 --> 11:27:36.830 align:start position:0% or troubleshooting printers or print test<11:27:34.916> pages<11:27:35.340> and<11:27:36.000> so<11:27:36.116> what<11:27:36.300> it<11:27:36.416> does<11:27:36.540> it 11:27:36.830 --> 11:27:36.840 align:start position:0% test pages and so what it does it 11:27:36.840 --> 11:27:40.550 align:start position:0% test pages and so what it does it literally<11:27:37.200> just<11:27:38.000> generates<11:27:39.000> characters<11:27:39.900> and 11:27:40.550 --> 11:27:40.560 align:start position:0% literally just generates characters and 11:27:40.560 --> 11:27:42.586 align:start position:0% literally just generates characters and we'll<11:27:40.680> look<11:27:40.860> at<11:27:41.040> this<11:27:41.220> in<11:27:41.400> a<11:27:41.520> little<11:27:41.640> bit<11:27:41.820> the 11:27:42.586 --> 11:27:42.596 align:start position:0% we'll look at this in a little bit the 11:27:42.596 --> 11:27:45.170 align:start position:0% we'll look at this in a little bit the next<11:27:42.720> one<11:27:42.840> is<11:27:43.020> the<11:27:43.320> daytime<11:27:43.860> service<11:27:44.220> that<11:27:44.820> ATM 11:27:45.170 --> 11:27:45.180 align:start position:0% next one is the daytime service that ATM 11:27:45.180 --> 11:27:46.730 align:start position:0% next one is the daytime service that ATM service<11:27:45.360> is<11:27:45.596> usually<11:27:45.840> used<11:27:46.080> for<11:27:46.320> checking 11:27:46.730 --> 11:27:46.740 align:start position:0% service is usually used for checking 11:27:46.740 --> 11:27:49.730 align:start position:0% service is usually used for checking errors<11:27:47.160> or<11:27:47.400> changes<11:27:47.880> that<11:27:48.480> happen<11:27:48.660> within<11:27:49.436> a 11:27:49.730 --> 11:27:49.740 align:start position:0% errors or changes that happen within a 11:27:49.740 --> 11:27:52.670 align:start position:0% errors or changes that happen within a system's<11:27:50.220> internal<11:27:50.880> clock<11:27:51.240> it<11:27:52.080> presents<11:27:52.500> a 11:27:52.670 --> 11:27:52.680 align:start position:0% system's internal clock it presents a 11:27:52.680 --> 11:27:54.766 align:start position:0% system's internal clock it presents a message<11:27:52.860> with<11:27:53.340> the<11:27:53.520> exact<11:27:53.880> time<11:27:54.300> that<11:27:54.660> a 11:27:54.766 --> 11:27:54.776 align:start position:0% message with the exact time that a 11:27:54.776 --> 11:27:57.766 align:start position:0% message with the exact time that a change<11:27:54.960> was<11:27:55.256> made<11:27:55.500> or<11:27:56.340> an<11:27:56.640> error<11:27:57.000> occurred<11:27:57.360> and 11:27:57.766 --> 11:27:57.776 align:start position:0% change was made or an error occurred and 11:27:57.776 --> 11:28:00.650 align:start position:0% change was made or an error occurred and we'll<11:27:57.900> look<11:27:58.080> at<11:27:58.256> this<11:27:58.500> format<11:27:59.060> in<11:28:00.060> just<11:28:00.416> a 11:28:00.650 --> 11:28:00.660 align:start position:0% we'll look at this format in just a 11:28:00.660 --> 11:28:02.690 align:start position:0% we'll look at this format in just a minute<11:28:00.840> but<11:28:01.560> basically<11:28:01.980> what's<11:28:02.276> important 11:28:02.690 --> 11:28:02.700 align:start position:0% minute but basically what's important 11:28:02.700 --> 11:28:04.670 align:start position:0% minute but basically what's important here<11:28:02.880> is<11:28:03.060> that<11:28:03.180> the<11:28:03.416> output<11:28:03.660> from<11:28:03.960> this<11:28:04.140> can<11:28:04.500> be 11:28:04.670 --> 11:28:04.680 align:start position:0% here is that the output from this can be 11:28:04.680 --> 11:28:07.426 align:start position:0% here is that the output from this can be used<11:28:04.916> for<11:28:05.756> for<11:28:05.936> instance<11:28:06.300> the<11:28:06.720> Event<11:28:06.840> Viewer 11:28:07.426 --> 11:28:07.436 align:start position:0% used for for instance the Event Viewer 11:28:07.436 --> 11:28:09.766 align:start position:0% used for for instance the Event Viewer sort<11:28:07.860> of<11:28:07.916> what<11:28:08.096> provides<11:28:08.580> information<11:28:08.936> to 11:28:09.766 --> 11:28:09.776 align:start position:0% sort of what provides information to 11:28:09.776 --> 11:28:12.586 align:start position:0% sort of what provides information to that<11:28:09.960> and<11:28:10.436> if<11:28:10.616> we're<11:28:10.740> going<11:28:10.916> to<11:28:11.040> see<11:28:11.160> it<11:28:11.340> in<11:28:11.640> a 11:28:12.586 --> 11:28:12.596 align:start position:0% that and if we're going to see it in a 11:28:12.596 --> 11:28:15.350 align:start position:0% that and if we're going to see it in a um<11:28:13.080> text<11:28:13.740> based<11:28:14.220> mode<11:28:14.340> you<11:28:14.580> will<11:28:14.700> see<11:28:14.936> exactly 11:28:15.350 --> 11:28:15.360 align:start position:0% um text based mode you will see exactly 11:28:15.360 --> 11:28:16.850 align:start position:0% um text based mode you will see exactly what<11:28:15.596> that's<11:28:15.720> going<11:28:15.960> to<11:28:16.080> present<11:28:16.320> in<11:28:16.616> the<11:28:16.740> next 11:28:16.850 --> 11:28:16.860 align:start position:0% what that's going to present in the next 11:28:16.860 --> 11:28:20.030 align:start position:0% what that's going to present in the next slide<11:28:17.700> now<11:28:18.116> the<11:28:18.300> discard<11:28:18.660> service<11:28:19.080> so<11:28:19.740> we've 11:28:20.030 --> 11:28:20.040 align:start position:0% slide now the discard service so we've 11:28:20.040 --> 11:28:21.106 align:start position:0% slide now the discard service so we've talked<11:28:20.340> about 11:28:21.106 --> 11:28:21.116 align:start position:0% talked about 11:28:21.116 --> 11:28:23.926 align:start position:0% talked about character<11:28:21.720> generator<11:28:22.256> and<11:28:22.916> daytime<11:28:23.340> the 11:28:23.926 --> 11:28:23.936 align:start position:0% character generator and daytime the 11:28:23.936 --> 11:28:26.450 align:start position:0% character generator and daytime the discard<11:28:24.240> service<11:28:24.680> is<11:28:25.680> basically<11:28:25.980> used<11:28:26.160> for 11:28:26.450 --> 11:28:26.460 align:start position:0% discard service is basically used for 11:28:26.460 --> 11:28:28.246 align:start position:0% discard service is basically used for messages<11:28:26.700> and<11:28:27.116> information<11:28:27.360> that<11:28:27.840> are<11:28:28.020> not 11:28:28.246 --> 11:28:28.256 align:start position:0% messages and information that are not 11:28:28.256 --> 11:28:29.990 align:start position:0% messages and information that are not important<11:28:28.740> and<11:28:29.276> therefore<11:28:29.520> should<11:28:29.820> be 11:28:29.990 --> 11:28:30.000 align:start position:0% important and therefore should be 11:28:30.000 --> 11:28:32.950 align:start position:0% important and therefore should be disposed<11:28:30.720> of<11:28:30.840> it<11:28:31.680> discards<11:28:32.276> these<11:28:32.640> messages 11:28:32.950 --> 11:28:32.960 align:start position:0% disposed of it discards these messages 11:28:32.960 --> 11:28:36.106 align:start position:0% disposed of it discards these messages automatically<11:28:33.960> when<11:28:34.380> they<11:28:34.680> enter<11:28:34.980> this<11:28:35.820> port 11:28:36.106 --> 11:28:36.116 align:start position:0% automatically when they enter this port 11:28:36.116 --> 11:28:38.150 align:start position:0% automatically when they enter this port or<11:28:36.540> the<11:28:36.720> port<11:28:36.840> that<11:28:37.080> discard<11:28:37.436> is<11:28:37.680> working<11:28:37.860> off 11:28:38.150 --> 11:28:38.160 align:start position:0% or the port that discard is working off 11:28:38.160 --> 11:28:39.830 align:start position:0% or the port that discard is working off of<11:28:38.340> this<11:28:38.880> can<11:28:39.116> be<11:28:39.240> useful<11:28:39.480> when<11:28:39.720> you're 11:28:39.830 --> 11:28:39.840 align:start position:0% of this can be useful when you're 11:28:39.840 --> 11:28:41.570 align:start position:0% of this can be useful when you're configuring<11:28:40.380> a<11:28:40.616> system<11:28:40.740> and<11:28:41.040> using<11:28:41.340> test 11:28:41.570 --> 11:28:41.580 align:start position:0% configuring a system and using test 11:28:41.580 --> 11:28:43.606 align:start position:0% configuring a system and using test messages<11:28:41.880> that<11:28:42.480> you<11:28:42.660> don't<11:28:42.776> want<11:28:43.020> necessarily 11:28:43.606 --> 11:28:43.616 align:start position:0% messages that you don't want necessarily 11:28:43.616 --> 11:28:44.870 align:start position:0% messages that you don't want necessarily to<11:28:43.916> display 11:28:44.870 --> 11:28:44.880 align:start position:0% to display 11:28:44.880 --> 11:28:47.390 align:start position:0% to display so<11:28:45.540> note<11:28:45.840> that<11:28:46.140> because<11:28:46.380> the<11:28:46.680> messages<11:28:46.860> are 11:28:47.390 --> 11:28:47.400 align:start position:0% so note that because the messages are 11:28:47.400 --> 11:28:49.810 align:start position:0% so note that because the messages are immediately<11:28:47.820> discarded<11:28:48.480> there's<11:28:49.020> really<11:28:49.320> no 11:28:49.810 --> 11:28:49.820 align:start position:0% immediately discarded there's really no 11:28:49.820 --> 11:28:52.370 align:start position:0% immediately discarded there's really no response<11:28:50.820> message<11:28:51.000> that's<11:28:51.416> issued<11:28:51.900> and 11:28:52.370 --> 11:28:52.380 align:start position:0% response message that's issued and 11:28:52.380 --> 11:28:54.406 align:start position:0% response message that's issued and therefore<11:28:52.740> I<11:28:53.160> can't<11:28:53.276> show<11:28:53.520> you<11:28:53.700> an<11:28:53.880> example<11:28:54.240> of 11:28:54.406 --> 11:28:54.416 align:start position:0% therefore I can't show you an example of 11:28:54.416 --> 11:28:57.350 align:start position:0% therefore I can't show you an example of one<11:28:54.660> but<11:28:55.200> just<11:28:55.380> realize<11:28:55.980> that<11:28:56.460> discard<11:28:57.060> is 11:28:57.350 --> 11:28:57.360 align:start position:0% one but just realize that discard is 11:28:57.360 --> 11:28:59.330 align:start position:0% one but just realize that discard is going<11:28:57.596> to<11:28:57.720> usually<11:28:58.020> be<11:28:58.256> used<11:28:58.500> for<11:28:59.160> network 11:28:59.330 --> 11:28:59.340 align:start position:0% going to usually be used for network 11:28:59.340 --> 11:29:02.390 align:start position:0% going to usually be used for network setup<11:28:59.880> and<11:29:00.060> configuration 11:29:02.390 --> 11:29:02.400 align:start position:0% setup and configuration 11:29:02.400 --> 11:29:04.730 align:start position:0% setup and configuration and<11:29:02.820> is<11:29:02.936> going<11:29:03.116> to<11:29:03.240> make<11:29:03.360> sure<11:29:03.480> there<11:29:03.840> is<11:29:04.080> no 11:29:04.730 --> 11:29:04.740 align:start position:0% and is going to make sure there is no 11:29:04.740 --> 11:29:08.210 align:start position:0% and is going to make sure there is no response<11:29:05.520> or<11:29:06.000> acknowledgment 11:29:08.210 --> 11:29:08.220 align:start position:0% response or acknowledgment 11:29:08.220 --> 11:29:11.690 align:start position:0% response or acknowledgment now<11:29:08.640> echo<11:29:09.116> or<11:29:09.480> the<11:29:09.660> echo<11:29:10.080> service<11:29:10.580> sends<11:29:11.580> an 11:29:11.690 --> 11:29:11.700 align:start position:0% now echo or the echo service sends an 11:29:11.700 --> 11:29:15.766 align:start position:0% now echo or the echo service sends an exact<11:29:12.116> copy<11:29:12.660> or<11:29:12.900> an<11:29:13.140> echo<11:29:13.616> hence<11:29:14.276> the<11:29:14.520> name<11:29:14.776> of 11:29:15.766 --> 11:29:15.776 align:start position:0% exact copy or an echo hence the name of 11:29:15.776 --> 11:29:18.890 align:start position:0% exact copy or an echo hence the name of any<11:29:16.380> message<11:29:16.680> that<11:29:17.096> enters<11:29:17.400> its<11:29:17.880> port<11:29:18.000> to<11:29:18.720> a 11:29:18.890 --> 11:29:18.900 align:start position:0% any message that enters its port to a 11:29:18.900 --> 11:29:20.510 align:start position:0% any message that enters its port to a place<11:29:19.080> in<11:29:19.320> the<11:29:19.500> system<11:29:19.680> where<11:29:20.220> the<11:29:20.400> message 11:29:20.510 --> 11:29:20.520 align:start position:0% place in the system where the message 11:29:20.520 --> 11:29:22.850 align:start position:0% place in the system where the message can<11:29:20.880> be<11:29:21.000> monitored<11:29:21.416> so<11:29:21.900> this<11:29:22.080> is<11:29:22.200> often<11:29:22.560> useful 11:29:22.850 --> 11:29:22.860 align:start position:0% can be monitored so this is often useful 11:29:22.860 --> 11:29:25.070 align:start position:0% can be monitored so this is often useful for<11:29:23.096> when<11:29:23.580> you're<11:29:23.936> monitoring<11:29:24.596> things<11:29:24.900> that 11:29:25.070 --> 11:29:25.080 align:start position:0% for when you're monitoring things that 11:29:25.080 --> 11:29:27.470 align:start position:0% for when you're monitoring things that are<11:29:25.200> going<11:29:25.256> on<11:29:25.500> in<11:29:25.680> a<11:29:25.800> network<11:29:26.220> because<11:29:27.000> the 11:29:27.470 --> 11:29:27.480 align:start position:0% are going on in a network because the 11:29:27.480 --> 11:29:30.406 align:start position:0% are going on in a network because the echo<11:29:27.900> service<11:29:28.200> simply<11:29:28.860> Echoes<11:29:29.580> and<11:29:29.936> copies 11:29:30.406 --> 11:29:30.416 align:start position:0% echo service simply Echoes and copies 11:29:30.416 --> 11:29:32.266 align:start position:0% echo service simply Echoes and copies and<11:29:30.720> forwards<11:29:31.200> any<11:29:31.320> messages<11:29:31.560> it<11:29:31.980> receives 11:29:32.266 --> 11:29:32.276 align:start position:0% and forwards any messages it receives 11:29:32.276 --> 11:29:34.130 align:start position:0% and forwards any messages it receives there's<11:29:32.756> really<11:29:32.936> no<11:29:33.116> way<11:29:33.300> to<11:29:33.480> show<11:29:33.596> what<11:29:33.960> an 11:29:34.130 --> 11:29:34.140 align:start position:0% there's really no way to show what an 11:29:34.140 --> 11:29:36.050 align:start position:0% there's really no way to show what an example<11:29:34.436> would<11:29:34.680> look<11:29:34.916> like<11:29:35.160> because<11:29:35.700> they 11:29:36.050 --> 11:29:36.060 align:start position:0% example would look like because they 11:29:36.060 --> 11:29:37.550 align:start position:0% example would look like because they each<11:29:36.180> look<11:29:36.416> very<11:29:36.596> different<11:29:36.840> from<11:29:37.200> each<11:29:37.380> other 11:29:37.550 --> 11:29:37.560 align:start position:0% each look very different from each other 11:29:37.560 --> 11:29:40.310 align:start position:0% each look very different from each other but<11:29:38.276> basically<11:29:38.640> in<11:29:39.000> many<11:29:39.116> cases<11:29:39.660> we're<11:29:40.200> going 11:29:40.310 --> 11:29:40.320 align:start position:0% but basically in many cases we're going 11:29:40.320 --> 11:29:41.926 align:start position:0% but basically in many cases we're going to<11:29:40.500> get<11:29:40.616> some<11:29:40.860> sort<11:29:41.040> of<11:29:41.160> message<11:29:41.400> that<11:29:41.756> happens 11:29:41.926 --> 11:29:41.936 align:start position:0% to get some sort of message that happens 11:29:41.936 --> 11:29:44.926 align:start position:0% to get some sort of message that happens internally<11:29:42.720> and<11:29:43.320> we<11:29:43.616> want<11:29:43.916> the<11:29:44.220> computer<11:29:44.400> to 11:29:44.926 --> 11:29:44.936 align:start position:0% internally and we want the computer to 11:29:44.936 --> 11:29:47.086 align:start position:0% internally and we want the computer to tell<11:29:45.240> us<11:29:45.480> that<11:29:45.776> message<11:29:46.080> once<11:29:46.500> again<11:29:46.616> so<11:29:46.916> we 11:29:47.086 --> 11:29:47.096 align:start position:0% tell us that message once again so we 11:29:47.096 --> 11:29:49.130 align:start position:0% tell us that message once again so we can<11:29:47.276> see<11:29:47.460> what's<11:29:47.700> going<11:29:47.936> on<11:29:48.116> internally<11:29:48.660> and 11:29:49.130 --> 11:29:49.140 align:start position:0% can see what's going on internally and 11:29:49.140 --> 11:29:50.510 align:start position:0% can see what's going on internally and that's<11:29:49.256> when<11:29:49.436> we're<11:29:49.616> going<11:29:49.740> to<11:29:49.800> use<11:29:49.980> the<11:29:50.220> echo 11:29:50.510 --> 11:29:50.520 align:start position:0% that's when we're going to use the echo 11:29:50.520 --> 11:29:52.850 align:start position:0% that's when we're going to use the echo service<11:29:50.840> finally<11:29:51.840> the<11:29:52.080> quote<11:29:52.320> or<11:29:52.500> the<11:29:52.680> quote 11:29:52.850 --> 11:29:52.860 align:start position:0% service finally the quote or the quote 11:29:52.860 --> 11:29:55.606 align:start position:0% service finally the quote or the quote of<11:29:52.980> the<11:29:53.096> day<11:29:53.276> service<11:29:53.900> sends<11:29:54.900> a<11:29:55.080> short<11:29:55.200> message 11:29:55.606 --> 11:29:55.616 align:start position:0% of the day service sends a short message 11:29:55.616 --> 11:29:57.230 align:start position:0% of the day service sends a short message that's<11:29:55.980> been<11:29:56.220> selected<11:29:56.640> by<11:29:56.936> the 11:29:57.230 --> 11:29:57.240 align:start position:0% that's been selected by the 11:29:57.240 --> 11:29:59.990 align:start position:0% that's been selected by the administrator<11:29:58.020> of<11:29:58.320> the<11:29:58.500> system<11:29:58.740> to<11:29:59.640> a 11:29:59.990 --> 11:30:00.000 align:start position:0% administrator of the system to a 11:30:00.000 --> 11:30:02.990 align:start position:0% administrator of the system to a client's<11:30:00.416> device<11:30:00.720> now<11:30:01.500> this<11:30:01.800> service<11:30:02.096> is<11:30:02.640> used 11:30:02.990 --> 11:30:03.000 align:start position:0% client's device now this service is used 11:30:03.000 --> 11:30:05.390 align:start position:0% client's device now this service is used primarily<11:30:03.720> for<11:30:04.080> checking<11:30:04.500> the<11:30:04.800> connection<11:30:04.980> to 11:30:05.390 --> 11:30:05.400 align:start position:0% primarily for checking the connection to 11:30:05.400 --> 11:30:08.630 align:start position:0% primarily for checking the connection to client<11:30:05.640> devices<11:30:06.140> so<11:30:07.140> it's<11:30:07.560> really<11:30:07.800> similar<11:30:08.096> to 11:30:08.630 --> 11:30:08.640 align:start position:0% client devices so it's really similar to 11:30:08.640 --> 11:30:10.906 align:start position:0% client devices so it's really similar to like<11:30:08.820> Echo<11:30:09.300> the<11:30:09.960> content<11:30:10.256> of<11:30:10.380> the<11:30:10.560> message<11:30:10.680> is 11:30:10.906 --> 11:30:10.916 align:start position:0% like Echo the content of the message is 11:30:10.916 --> 11:30:12.830 align:start position:0% like Echo the content of the message is not<11:30:11.160> this<11:30:11.340> is<11:30:11.520> not<11:30:11.756> what's<11:30:11.936> important<11:30:12.360> what's 11:30:12.830 --> 11:30:12.840 align:start position:0% not this is not what's important what's 11:30:12.840 --> 11:30:14.690 align:start position:0% not this is not what's important what's important<11:30:13.320> is<11:30:13.916> that 11:30:14.690 --> 11:30:14.700 align:start position:0% important is that 11:30:14.700 --> 11:30:17.746 align:start position:0% important is that it<11:30:15.300> is<11:30:15.720> sending<11:30:16.200> something<11:30:16.616> and<11:30:16.980> that<11:30:17.160> way<11:30:17.400> we 11:30:17.746 --> 11:30:17.756 align:start position:0% it is sending something and that way we 11:30:17.756 --> 11:30:20.746 align:start position:0% it is sending something and that way we can<11:30:17.936> make<11:30:18.596> sure<11:30:18.960> that<11:30:19.616> the<11:30:19.860> service<11:30:20.096> is 11:30:20.746 --> 11:30:20.756 align:start position:0% can make sure that the service is 11:30:20.756 --> 11:30:24.010 align:start position:0% can make sure that the service is working<11:30:21.596> and<11:30:22.436> that<11:30:22.740> the<11:30:23.400> um 11:30:24.010 --> 11:30:24.020 align:start position:0% working and that the um 11:30:24.020 --> 11:30:27.406 align:start position:0% working and that the um troubleshooting<11:30:25.020> is<11:30:25.256> sort<11:30:25.436> of<11:30:25.560> easily 11:30:27.406 --> 11:30:27.416 align:start position:0% troubleshooting is sort of easily 11:30:27.416 --> 11:30:30.470 align:start position:0% troubleshooting is sort of easily solved<11:30:28.140> now<11:30:28.500> as<11:30:28.616> it<11:30:28.860> mentions<11:30:29.160> here<11:30:29.460> it<11:30:30.240> can<11:30:30.360> be 11:30:30.470 --> 11:30:30.480 align:start position:0% solved now as it mentions here it can be 11:30:30.480 --> 11:30:33.950 align:start position:0% solved now as it mentions here it can be taken<11:30:30.840> from<11:30:31.140> a<11:30:31.320> specific<11:30:31.680> file 11:30:33.950 --> 11:30:33.960 align:start position:0% taken from a specific file 11:30:33.960 --> 11:30:36.350 align:start position:0% taken from a specific file right<11:30:34.560> in<11:30:34.740> here<11:30:34.916> which<11:30:35.460> is<11:30:35.580> where<11:30:35.880> random 11:30:36.350 --> 11:30:36.360 align:start position:0% right in here which is where random 11:30:36.360 --> 11:30:38.266 align:start position:0% right in here which is where random quotes<11:30:36.540> can<11:30:36.900> be<11:30:37.020> taken<11:30:37.320> of<11:30:37.500> if<11:30:37.980> you<11:30:38.096> remember 11:30:38.266 --> 11:30:38.276 align:start position:0% quotes can be taken of if you remember 11:30:38.276 --> 11:30:41.390 align:start position:0% quotes can be taken of if you remember or<11:30:39.060> if<11:30:39.240> you<11:30:39.360> know<11:30:39.480> the<11:30:39.776> hosts<11:30:40.256> file<11:30:40.560> it<11:30:40.860> is<11:30:41.040> also 11:30:41.390 --> 11:30:41.400 align:start position:0% or if you know the hosts file it is also 11:30:41.400 --> 11:30:42.710 align:start position:0% or if you know the hosts file it is also located 11:30:42.710 --> 11:30:42.720 align:start position:0% located 11:30:42.720 --> 11:30:46.010 align:start position:0% located in<11:30:43.680> this<11:30:43.980> folder 11:30:46.010 --> 11:30:46.020 align:start position:0% in this folder 11:30:46.020 --> 11:30:48.650 align:start position:0% in this folder so<11:30:46.616> let's<11:30:46.980> take<11:30:47.160> a<11:30:47.276> look<11:30:47.400> at<11:30:47.700> this<11:30:48.116> character 11:30:48.650 --> 11:30:48.660 align:start position:0% so let's take a look at this character 11:30:48.660 --> 11:30:50.926 align:start position:0% so let's take a look at this character generator<11:30:49.200> uh<11:30:49.916> and<11:30:50.096> some<11:30:50.276> output<11:30:50.580> that<11:30:50.756> it 11:30:50.926 --> 11:30:50.936 align:start position:0% generator uh and some output that it 11:30:50.936 --> 11:30:54.710 align:start position:0% generator uh and some output that it might<11:30:51.116> give<11:30:51.300> you 11:30:54.710 --> 11:30:54.720 align:start position:0% 11:30:54.720 --> 11:30:58.190 align:start position:0% now<11:30:55.256> this<11:30:55.560> is<11:30:55.740> what<11:30:56.040> a<11:30:56.936> test<11:30:57.116> code<11:30:57.480> page<11:30:57.900> would 11:30:58.190 --> 11:30:58.200 align:start position:0% now this is what a test code page would 11:30:58.200 --> 11:31:01.670 align:start position:0% now this is what a test code page would look<11:30:58.436> like<11:30:58.560> these<11:30:59.400> characters<11:30:59.700> are<11:31:00.416> used<11:31:00.720> uh 11:31:01.670 --> 11:31:01.680 align:start position:0% look like these characters are used uh 11:31:01.680 --> 11:31:05.450 align:start position:0% look like these characters are used uh and<11:31:01.980> they<11:31:02.160> are<11:31:02.340> the<11:31:02.596> 95<11:31:03.596> printable<11:31:04.460> ASCII 11:31:05.450 --> 11:31:05.460 align:start position:0% and they are the 95 printable ASCII 11:31:05.460 --> 11:31:08.210 align:start position:0% and they are the 95 printable ASCII characters<11:31:05.700> as<11:31:06.180> you<11:31:06.360> can<11:31:06.480> see 11:31:08.210 --> 11:31:08.220 align:start position:0% characters as you can see 11:31:08.220 --> 11:31:10.970 align:start position:0% characters as you can see from<11:31:08.700> here<11:31:08.936> and<11:31:09.596> basically<11:31:10.080> What's<11:31:10.436> Happening 11:31:10.970 --> 11:31:10.980 align:start position:0% from here and basically What's Happening 11:31:10.980 --> 11:31:13.970 align:start position:0% from here and basically What's Happening Here<11:31:11.340> is<11:31:12.000> that<11:31:12.240> when<11:31:12.480> I<11:31:12.720> uh<11:31:13.020> for<11:31:13.320> instance<11:31:13.560> and 11:31:13.970 --> 11:31:13.980 align:start position:0% Here is that when I uh for instance and 11:31:13.980 --> 11:31:15.710 align:start position:0% Here is that when I uh for instance and this<11:31:14.220> is<11:31:14.276> someone<11:31:14.460> going<11:31:14.756> into<11:31:15.000> telnet<11:31:15.596> so 11:31:15.710 --> 11:31:15.720 align:start position:0% this is someone going into telnet so 11:31:15.720 --> 11:31:17.086 align:start position:0% this is someone going into telnet so they've<11:31:15.960> talented<11:31:16.320> in 11:31:17.086 --> 11:31:17.096 align:start position:0% they've talented in 11:31:17.096 --> 11:31:19.970 align:start position:0% they've talented in they<11:31:17.820> have<11:31:18.000> connected<11:31:18.480> and<11:31:19.080> now<11:31:19.256> I've<11:31:19.500> told<11:31:19.740> it 11:31:19.970 --> 11:31:19.980 align:start position:0% they have connected and now I've told it 11:31:19.980 --> 11:31:22.606 align:start position:0% they have connected and now I've told it basically<11:31:20.580> to<11:31:21.116> create<11:31:21.360> some<11:31:21.660> characters<11:31:21.900> and 11:31:22.606 --> 11:31:22.616 align:start position:0% basically to create some characters and 11:31:22.616 --> 11:31:24.350 align:start position:0% basically to create some characters and that's<11:31:22.800> what<11:31:23.040> it's<11:31:23.160> doing<11:31:23.400> here<11:31:23.756> and<11:31:24.240> it's 11:31:24.350 --> 11:31:24.360 align:start position:0% that's what it's doing here and it's 11:31:24.360 --> 11:31:26.210 align:start position:0% that's what it's doing here and it's using<11:31:24.776> all<11:31:25.020> the<11:31:25.200> characters<11:31:25.500> that<11:31:26.096> are 11:31:26.210 --> 11:31:26.220 align:start position:0% using all the characters that are 11:31:26.220 --> 11:31:30.766 align:start position:0% using all the characters that are available<11:31:26.520> to<11:31:27.416> it<11:31:27.596> in<11:31:27.840> ASCII 11:31:30.766 --> 11:31:30.776 align:start position:0% 11:31:30.776 --> 11:31:32.086 align:start position:0% and<11:31:31.140> you<11:31:31.256> would<11:31:31.380> usually<11:31:31.616> use<11:31:31.740> this<11:31:31.916> when 11:31:32.086 --> 11:31:32.096 align:start position:0% and you would usually use this when 11:31:32.096 --> 11:31:34.010 align:start position:0% and you would usually use this when you're<11:31:32.220> setting<11:31:32.460> up<11:31:32.520> a<11:31:32.640> printer<11:31:32.936> testing<11:31:33.900> a 11:31:34.010 --> 11:31:34.020 align:start position:0% you're setting up a printer testing a 11:31:34.020 --> 11:31:36.950 align:start position:0% you're setting up a printer testing a connection<11:31:34.200> to<11:31:34.860> a<11:31:35.096> device<11:31:35.520> or<11:31:36.060> printer<11:31:36.480> it 11:31:36.950 --> 11:31:36.960 align:start position:0% connection to a device or printer it 11:31:36.960 --> 11:31:38.150 align:start position:0% connection to a device or printer it doesn't<11:31:37.080> really<11:31:37.256> have<11:31:37.436> much<11:31:37.680> of<11:31:37.800> a<11:31:37.916> function 11:31:38.150 --> 11:31:38.160 align:start position:0% doesn't really have much of a function 11:31:38.160 --> 11:31:40.370 align:start position:0% doesn't really have much of a function otherwise<11:31:38.520> you<11:31:38.756> can<11:31:38.880> see<11:31:39.060> that<11:31:39.300> the<11:31:39.720> content 11:31:40.370 --> 11:31:40.380 align:start position:0% otherwise you can see that the content 11:31:40.380 --> 11:31:42.470 align:start position:0% otherwise you can see that the content is<11:31:40.616> not<11:31:40.800> very<11:31:41.040> important<11:31:41.460> but<11:31:41.936> all<11:31:42.116> it's<11:31:42.300> doing 11:31:42.470 --> 11:31:42.480 align:start position:0% is not very important but all it's doing 11:31:42.480 --> 11:31:44.926 align:start position:0% is not very important but all it's doing is<11:31:42.776> basically<11:31:43.140> creating<11:31:43.860> characters<11:31:44.460> or 11:31:44.926 --> 11:31:44.936 align:start position:0% is basically creating characters or 11:31:44.936 --> 11:31:47.510 align:start position:0% is basically creating characters or content<11:31:45.300> for<11:31:45.540> us<11:31:45.660> to<11:31:45.840> test<11:31:46.020> with 11:31:47.510 --> 11:31:47.520 align:start position:0% content for us to test with 11:31:47.520 --> 11:31:50.330 align:start position:0% content for us to test with the<11:31:48.116> next<11:31:48.240> one<11:31:48.480> is<11:31:49.020> the<11:31:49.380> daytime<11:31:49.916> service 11:31:50.330 --> 11:31:50.340 align:start position:0% the next one is the daytime service 11:31:50.340 --> 11:31:52.130 align:start position:0% the next one is the daytime service report<11:31:50.700> and<11:31:51.300> this<11:31:51.416> is<11:31:51.480> what<11:31:51.596> it<11:31:51.720> looks<11:31:51.960> like 11:31:52.130 --> 11:31:52.140 align:start position:0% report and this is what it looks like 11:31:52.140 --> 11:31:54.350 align:start position:0% report and this is what it looks like and<11:31:52.616> you<11:31:52.860> can<11:31:52.980> see<11:31:53.220> that<11:31:53.460> it's<11:31:53.820> presented<11:31:54.240> in 11:31:54.350 --> 11:31:54.360 align:start position:0% and you can see that it's presented in 11:31:54.360 --> 11:31:55.906 align:start position:0% and you can see that it's presented in the<11:31:54.540> following<11:31:54.840> order<11:31:55.020> it's<11:31:55.560> going<11:31:55.740> to<11:31:55.860> show 11:31:55.906 --> 11:31:55.916 align:start position:0% the following order it's going to show 11:31:55.916 --> 11:31:57.650 align:start position:0% the following order it's going to show us<11:31:56.096> the<11:31:56.276> day<11:31:56.400> of<11:31:56.580> the<11:31:56.700> week 11:31:57.650 --> 11:31:57.660 align:start position:0% us the day of the week 11:31:57.660 --> 11:31:59.266 align:start position:0% us the day of the week the<11:31:58.200> months 11:31:59.266 --> 11:31:59.276 align:start position:0% the months 11:31:59.276 --> 11:32:01.010 align:start position:0% the months the<11:31:59.880> day 11:32:01.010 --> 11:32:01.020 align:start position:0% the day 11:32:01.020 --> 11:32:03.230 align:start position:0% the day the<11:32:01.616> year 11:32:03.230 --> 11:32:03.240 align:start position:0% the year 11:32:03.240 --> 11:32:06.470 align:start position:0% the year the<11:32:03.900> hours<11:32:04.200> minutes<11:32:04.860> and<11:32:05.276> seconds<11:32:05.520> in<11:32:06.300> that 11:32:06.470 --> 11:32:06.480 align:start position:0% the hours minutes and seconds in that 11:32:06.480 --> 11:32:09.050 align:start position:0% the hours minutes and seconds in that format<11:32:06.960> and<11:32:07.860> finally<11:32:08.096> and<11:32:08.400> very<11:32:08.700> importantly 11:32:09.050 --> 11:32:09.060 align:start position:0% format and finally and very importantly 11:32:09.060 --> 11:32:10.730 align:start position:0% format and finally and very importantly the<11:32:09.360> time<11:32:09.540> zone<11:32:09.776> the<11:32:09.960> reason<11:32:10.080> the<11:32:10.320> time<11:32:10.500> zone 11:32:10.730 --> 11:32:10.740 align:start position:0% the time zone the reason the time zone 11:32:10.740 --> 11:32:12.406 align:start position:0% the time zone the reason the time zone is<11:32:10.860> important<11:32:11.276> is<11:32:11.820> let's<11:32:11.936> say<11:32:12.116> that<11:32:12.300> we're 11:32:12.406 --> 11:32:12.416 align:start position:0% is important is let's say that we're 11:32:12.416 --> 11:32:14.390 align:start position:0% is important is let's say that we're looking<11:32:12.596> at<11:32:12.776> this<11:32:12.900> daytime<11:32:13.380> in<11:32:13.800> an<11:32:13.980> email<11:32:14.096> and 11:32:14.390 --> 11:32:14.400 align:start position:0% looking at this daytime in an email and 11:32:14.400 --> 11:32:15.766 align:start position:0% looking at this daytime in an email and sometimes<11:32:14.700> the<11:32:14.880> headers<11:32:15.180> are<11:32:15.360> going<11:32:15.540> to<11:32:15.660> use 11:32:15.766 --> 11:32:15.776 align:start position:0% sometimes the headers are going to use 11:32:15.776 --> 11:32:18.170 align:start position:0% sometimes the headers are going to use this<11:32:16.616> same<11:32:16.800> format<11:32:17.340> all<11:32:17.756> right<11:32:17.880> that's 11:32:18.170 --> 11:32:18.180 align:start position:0% this same format all right that's 11:32:18.180 --> 11:32:20.690 align:start position:0% this same format all right that's provided<11:32:18.720> by<11:32:18.960> the<11:32:19.140> daytime<11:32:19.680> service<11:32:20.460> and 11:32:20.690 --> 11:32:20.700 align:start position:0% provided by the daytime service and 11:32:20.700 --> 11:32:23.810 align:start position:0% provided by the daytime service and tcpap<11:32:21.416> well<11:32:22.140> I<11:32:22.500> can<11:32:22.616> see<11:32:22.800> that<11:32:22.980> oh<11:32:23.220> yeah<11:32:23.400> it<11:32:23.640> was 11:32:23.810 --> 11:32:23.820 align:start position:0% tcpap well I can see that oh yeah it was 11:32:23.820 --> 11:32:25.010 align:start position:0% tcpap well I can see that oh yeah it was sent 11:32:25.010 --> 11:32:25.020 align:start position:0% sent 11:32:25.020 --> 11:32:28.606 align:start position:0% sent at<11:32:25.740> 1845<11:32:26.700> which<11:32:27.240> that's<11:32:27.596> military<11:32:27.900> time<11:32:28.320> so 11:32:28.606 --> 11:32:28.616 align:start position:0% at 1845 which that's military time so 11:32:28.616 --> 11:32:32.690 align:start position:0% at 1845 which that's military time so this<11:32:28.800> would<11:32:28.916> be<11:32:29.096> 6<11:32:29.880> 45<11:32:30.560> PM<11:32:31.560> in<11:32:32.276> sort<11:32:32.460> of<11:32:32.580> our 11:32:32.690 --> 11:32:32.700 align:start position:0% this would be 6 45 PM in sort of our 11:32:32.700 --> 11:32:37.070 align:start position:0% this would be 6 45 PM in sort of our lingo<11:32:33.240> but<11:32:33.720> by<11:32:34.080> knowing<11:32:34.500> the<11:32:35.040> time<11:32:35.640> zone<11:32:36.300> I<11:32:36.960> can 11:32:37.070 --> 11:32:37.080 align:start position:0% lingo but by knowing the time zone I can 11:32:37.080 --> 11:32:38.390 align:start position:0% lingo but by knowing the time zone I can actually<11:32:37.256> determine<11:32:37.680> where<11:32:37.860> in<11:32:38.040> the<11:32:38.160> world<11:32:38.220> it 11:32:38.390 --> 11:32:38.400 align:start position:0% actually determine where in the world it 11:32:38.400 --> 11:32:40.070 align:start position:0% actually determine where in the world it was<11:32:38.520> sent<11:32:38.640> from<11:32:38.880> and<11:32:39.240> therefore<11:32:39.540> for<11:32:39.840> instance 11:32:40.070 --> 11:32:40.080 align:start position:0% was sent from and therefore for instance 11:32:40.080 --> 11:32:42.710 align:start position:0% was sent from and therefore for instance this<11:32:40.380> was<11:32:40.560> sent<11:32:40.800> on<11:32:41.460> Pacific<11:32:41.880> Standard<11:32:42.480> time 11:32:42.710 --> 11:32:42.720 align:start position:0% this was sent on Pacific Standard time 11:32:42.720 --> 11:32:46.670 align:start position:0% this was sent on Pacific Standard time which<11:32:43.256> is<11:32:43.380> in<11:32:43.560> the<11:32:43.740> U.S<11:32:44.040> then<11:32:44.936> uh<11:32:45.776> I<11:32:46.380> would<11:32:46.500> know 11:32:46.670 --> 11:32:46.680 align:start position:0% which is in the U.S then uh I would know 11:32:46.680 --> 11:32:49.490 align:start position:0% which is in the U.S then uh I would know that<11:32:46.916> this<11:32:47.160> is<11:32:47.400> three<11:32:47.880> hours<11:32:48.116> later<11:32:48.540> or<11:32:48.900> 9<11:32:49.140> 45 11:32:49.490 --> 11:32:49.500 align:start position:0% that this is three hours later or 9 45 11:32:49.500 --> 11:32:53.810 align:start position:0% that this is three hours later or 9 45 in<11:32:49.980> the<11:32:50.220> Eastern<11:32:50.820> Time<11:32:51.116> Zone 11:32:53.810 --> 11:32:53.820 align:start position:0% 11:32:53.820 --> 11:32:56.330 align:start position:0% now<11:32:54.416> none<11:32:54.720> of<11:32:54.900> the<11:32:55.080> other<11:32:55.256> uh<11:32:55.860> as<11:32:56.096> we've 11:32:56.330 --> 11:32:56.340 align:start position:0% now none of the other uh as we've 11:32:56.340 --> 11:32:58.550 align:start position:0% now none of the other uh as we've mentioned<11:32:56.640> none<11:32:57.000> of<11:32:57.116> the<11:32:57.240> other<11:32:57.360> uh<11:32:58.200> Services 11:32:58.550 --> 11:32:58.560 align:start position:0% mentioned none of the other uh Services 11:32:58.560 --> 11:33:01.130 align:start position:0% mentioned none of the other uh Services have<11:32:59.520> any<11:32:59.756> sort<11:32:59.936> of<11:33:00.000> output<11:33:00.300> I<11:33:00.540> can<11:33:00.720> show<11:33:00.960> you 11:33:01.130 --> 11:33:01.140 align:start position:0% have any sort of output I can show you 11:33:01.140 --> 11:33:03.766 align:start position:0% have any sort of output I can show you but<11:33:01.916> just<11:33:02.220> to<11:33:02.460> recap 11:33:03.766 --> 11:33:03.776 align:start position:0% but just to recap 11:33:03.776 --> 11:33:05.810 align:start position:0% but just to recap what<11:33:04.256> we've<11:33:04.436> talked<11:33:04.740> about<11:33:04.800> we<11:33:05.340> described<11:33:05.700> and 11:33:05.810 --> 11:33:05.820 align:start position:0% what we've talked about we described and 11:33:05.820 --> 11:33:07.970 align:start position:0% what we've talked about we described and demonstrated<11:33:06.360> really<11:33:06.776> briefly<11:33:07.200> the<11:33:07.500> TCP 11:33:07.970 --> 11:33:07.980 align:start position:0% demonstrated really briefly the TCP 11:33:07.980 --> 11:33:10.370 align:start position:0% demonstrated really briefly the TCP simple<11:33:08.520> services<11:33:08.880> and<11:33:09.660> these<11:33:09.840> again<11:33:09.960> include 11:33:10.370 --> 11:33:10.380 align:start position:0% simple services and these again include 11:33:10.380 --> 11:33:12.230 align:start position:0% simple services and these again include a<11:33:10.560> character<11:33:10.800> generator<11:33:11.340> we're<11:33:11.880> really<11:33:12.060> going 11:33:12.230 --> 11:33:12.240 align:start position:0% a character generator we're really going 11:33:12.240 --> 11:33:13.730 align:start position:0% a character generator we're really going to<11:33:12.360> see<11:33:12.416> this<11:33:12.596> a<11:33:12.776> lot<11:33:12.900> when<11:33:13.320> we're<11:33:13.500> dealing 11:33:13.730 --> 11:33:13.740 align:start position:0% to see this a lot when we're dealing 11:33:13.740 --> 11:33:16.246 align:start position:0% to see this a lot when we're dealing with<11:33:13.800> printers<11:33:14.220> it's<11:33:14.580> just<11:33:14.820> generating 11:33:16.246 --> 11:33:16.256 align:start position:0% with printers it's just generating 11:33:16.256 --> 11:33:18.350 align:start position:0% with printers it's just generating ASCII<11:33:17.040> code 11:33:18.350 --> 11:33:18.360 align:start position:0% ASCII code 11:33:18.360 --> 11:33:20.870 align:start position:0% ASCII code we<11:33:18.840> looked<11:33:19.080> at<11:33:19.200> the<11:33:19.740> daytime<11:33:20.160> service<11:33:20.460> which 11:33:20.870 --> 11:33:20.880 align:start position:0% we looked at the daytime service which 11:33:20.880 --> 11:33:23.330 align:start position:0% we looked at the daytime service which is<11:33:21.000> presenting<11:33:21.540> the<11:33:21.900> day 11:33:23.330 --> 11:33:23.340 align:start position:0% is presenting the day 11:33:23.340 --> 11:33:27.106 align:start position:0% is presenting the day the<11:33:23.936> time<11:33:24.240> and<11:33:25.200> also<11:33:25.500> don't<11:33:25.680> forget<11:33:25.860> the<11:33:26.700> time 11:33:27.106 --> 11:33:27.116 align:start position:0% the time and also don't forget the time 11:33:27.116 --> 11:33:30.350 align:start position:0% the time and also don't forget the time zone<11:33:27.480> which<11:33:28.436> is<11:33:28.680> really<11:33:28.980> important 11:33:30.350 --> 11:33:30.360 align:start position:0% zone which is really important 11:33:30.360 --> 11:33:32.086 align:start position:0% zone which is really important we<11:33:30.720> looked<11:33:30.900> at<11:33:30.960> the<11:33:31.080> discard<11:33:31.436> service<11:33:31.680> which 11:33:32.086 --> 11:33:32.096 align:start position:0% we looked at the discard service which 11:33:32.096 --> 11:33:35.210 align:start position:0% we looked at the discard service which automatically<11:33:32.820> deletes 11:33:35.210 --> 11:33:35.220 align:start position:0% automatically deletes 11:33:35.220 --> 11:33:37.246 align:start position:0% automatically deletes messages<11:33:35.700> that<11:33:36.300> we<11:33:36.480> don't<11:33:36.596> need<11:33:36.776> and<11:33:37.080> so 11:33:37.246 --> 11:33:37.256 align:start position:0% messages that we don't need and so 11:33:37.256 --> 11:33:38.810 align:start position:0% messages that we don't need and so there's<11:33:37.436> really<11:33:37.560> nothing<11:33:37.800> there 11:33:38.810 --> 11:33:38.820 align:start position:0% there's really nothing there 11:33:38.820 --> 11:33:42.406 align:start position:0% there's really nothing there Echo<11:33:39.480> simply<11:33:40.256> repeats 11:33:42.406 --> 11:33:42.416 align:start position:0% Echo simply repeats 11:33:42.416 --> 11:33:46.310 align:start position:0% Echo simply repeats or<11:33:42.840> Echoes<11:33:43.436> any<11:33:43.916> services<11:33:44.340> or<11:33:45.180> a<11:33:45.596> message<11:33:46.020> that 11:33:46.310 --> 11:33:46.320 align:start position:0% or Echoes any services or a message that 11:33:46.320 --> 11:33:48.890 align:start position:0% or Echoes any services or a message that are<11:33:46.436> happening<11:33:46.740> internally<11:33:47.340> and<11:33:48.300> finally<11:33:48.596> the 11:33:48.890 --> 11:33:48.900 align:start position:0% are happening internally and finally the 11:33:48.900 --> 11:33:51.290 align:start position:0% are happening internally and finally the quote<11:33:49.080> of<11:33:49.256> the<11:33:49.380> day<11:33:49.560> takes<11:33:50.276> a<11:33:50.520> random<11:33:50.936> quote 11:33:51.290 --> 11:33:51.300 align:start position:0% quote of the day takes a random quote 11:33:51.300 --> 11:33:53.450 align:start position:0% quote of the day takes a random quote selected<11:33:52.020> by<11:33:52.200> the<11:33:52.320> administrator<11:33:52.800> or<11:33:53.040> taken 11:33:53.450 --> 11:33:53.460 align:start position:0% selected by the administrator or taken 11:33:53.460 --> 11:33:56.170 align:start position:0% selected by the administrator or taken out<11:33:53.640> of<11:33:53.820> a<11:33:54.360> etc<11:33:54.540> folder<11:33:55.020> in<11:33:55.200> the<11:33:55.320> system<11:33:55.436> 32 11:33:56.170 --> 11:33:56.180 align:start position:0% out of a etc folder in the system 32 11:33:56.180 --> 11:34:00.050 align:start position:0% out of a etc folder in the system 32 quotes<11:33:57.180> area<11:33:58.140> so<11:33:58.560> that<11:33:58.740> would<11:33:58.980> be<11:33:59.160> if<11:33:59.640> we<11:33:59.820> had 11:34:00.050 --> 11:34:00.060 align:start position:0% quotes area so that would be if we had 11:34:00.060 --> 11:34:05.086 align:start position:0% quotes area so that would be if we had the<11:34:00.416> root 11:34:05.086 --> 11:34:05.096 align:start position:0% 11:34:05.096 --> 11:34:11.990 align:start position:0% which<11:34:05.580> would<11:34:05.756> be<11:34:05.880> like<11:34:06.000> system<11:34:06.180> 32 11:34:11.990 --> 11:34:12.000 align:start position:0% 11:34:12.000 --> 11:34:14.390 align:start position:0% and<11:34:12.596> then<11:34:12.960> Etc<11:34:13.140> and<11:34:13.740> then<11:34:13.916> quotes<11:34:14.096> that's 11:34:14.390 --> 11:34:14.400 align:start position:0% and then Etc and then quotes that's 11:34:14.400 --> 11:34:15.650 align:start position:0% and then Etc and then quotes that's where<11:34:14.580> it's<11:34:14.700> going<11:34:14.880> to<11:34:14.880> draw<11:34:15.060> something<11:34:15.300> from 11:34:15.650 --> 11:34:15.660 align:start position:0% where it's going to draw something from 11:34:15.660 --> 11:34:18.050 align:start position:0% where it's going to draw something from and<11:34:16.140> again<11:34:16.256> this<11:34:16.560> is<11:34:16.680> also<11:34:16.980> used<11:34:17.220> for 11:34:18.050 --> 11:34:18.060 align:start position:0% and again this is also used for 11:34:18.060 --> 11:34:20.990 align:start position:0% and again this is also used for troubleshooting<11:34:18.840> purposes 11:34:20.990 --> 11:34:21.000 align:start position:0% troubleshooting purposes 11:34:21.000 --> 11:34:22.790 align:start position:0% troubleshooting purposes I<11:34:21.116> showed<11:34:21.540> you<11:34:21.660> examples<11:34:22.020> of<11:34:22.380> these<11:34:22.680> two 11:34:22.790 --> 11:34:22.800 align:start position:0% I showed you examples of these two 11:34:22.800 --> 11:34:23.990 align:start position:0% I showed you examples of these two because<11:34:23.040> they're<11:34:23.276> the<11:34:23.400> only<11:34:23.520> ones<11:34:23.700> that<11:34:23.820> have 11:34:23.990 --> 11:34:24.000 align:start position:0% because they're the only ones that have 11:34:24.000 --> 11:34:26.030 align:start position:0% because they're the only ones that have their<11:34:24.180> own<11:34:24.360> format<11:34:24.776> all<11:34:25.320> of<11:34:25.436> the<11:34:25.560> others<11:34:25.860> the 11:34:26.030 --> 11:34:26.040 align:start position:0% their own format all of the others the 11:34:26.040 --> 11:34:28.310 align:start position:0% their own format all of the others the form<11:34:26.220> is<11:34:26.520> not<11:34:26.700> as<11:34:26.820> important<11:34:27.240> all<11:34:27.840> it<11:34:27.960> does<11:34:28.140> is 11:34:28.310 --> 11:34:28.320 align:start position:0% form is not as important all it does is 11:34:28.320 --> 11:34:30.230 align:start position:0% form is not as important all it does is take<11:34:28.680> other<11:34:29.160> information<11:34:29.460> sort<11:34:30.116> of 11:34:30.230 --> 11:34:30.240 align:start position:0% take other information sort of 11:34:30.240 --> 11:34:34.426 align:start position:0% take other information sort of regurgitate<11:34:30.900> it 11:34:34.426 --> 11:34:34.436 align:start position:0% 11:34:34.436 --> 11:34:35.990 align:start position:0% now<11:34:34.860> in<11:34:35.096> the<11:34:35.160> next<11:34:35.276> module<11:34:35.700> we're<11:34:35.880> going<11:34:36.000> to 11:34:35.990 --> 11:34:36.000 align:start position:0% now in the next module we're going to 11:34:36.000 --> 11:34:37.606 align:start position:0% now in the next module we're going to take<11:34:36.180> a<11:34:36.360> step<11:34:36.540> further<11:34:36.840> and<11:34:36.960> talk<11:34:37.200> more<11:34:37.500> about 11:34:37.606 --> 11:34:37.616 align:start position:0% take a step further and talk more about 11:34:37.616 --> 11:34:41.330 align:start position:0% take a step further and talk more about some<11:34:37.860> of<11:34:37.980> the<11:34:38.040> tcpi<11:34:38.840> tools<11:34:39.840> and<11:34:40.320> commands<11:34:40.800> and 11:34:41.330 --> 11:34:41.340 align:start position:0% some of the tcpi tools and commands and 11:34:41.340 --> 11:34:43.070 align:start position:0% some of the tcpi tools and commands and get<11:34:41.520> into<11:34:41.700> the<11:34:42.000> operating<11:34:42.300> system<11:34:42.540> when<11:34:42.776> we<11:34:42.900> do 11:34:43.070 --> 11:34:43.080 align:start position:0% get into the operating system when we do 11:34:43.080 --> 11:34:47.590 align:start position:0% get into the operating system when we do so 11:34:47.590 --> 11:34:47.600 align:start position:0% 11:34:47.600 --> 11:34:56.230 align:start position:0% [Music] 11:34:56.230 --> 11:34:56.240 align:start position:0% [Music] 11:34:56.240 --> 11:35:11.650 align:start position:0% [Music] thank<11:34:57.240> you 11:35:11.650 --> 11:35:11.660 align:start position:0% 11:35:11.660 --> 11:35:13.266 align:start position:0% tcpip 11:35:13.266 --> 11:35:13.276 align:start position:0% tcpip 11:35:13.276 --> 11:35:16.790 align:start position:0% tcpip tcpip<11:35:14.276> tools<11:35:15.060> and<11:35:15.360> commands 11:35:16.790 --> 11:35:16.800 align:start position:0% tcpip tools and commands 11:35:16.800 --> 11:35:18.710 align:start position:0% tcpip tools and commands so<11:35:17.276> in<11:35:17.460> the<11:35:17.580> last<11:35:17.700> module<11:35:18.180> we<11:35:18.416> talked<11:35:18.660> about 11:35:18.710 --> 11:35:18.720 align:start position:0% so in the last module we talked about 11:35:18.720 --> 11:35:21.710 align:start position:0% so in the last module we talked about the<11:35:19.140> simple<11:35:19.320> services<11:35:19.680> that<11:35:20.220> tcpip<11:35:21.000> provides 11:35:21.710 --> 11:35:21.720 align:start position:0% the simple services that tcpip provides 11:35:21.720 --> 11:35:24.530 align:start position:0% the simple services that tcpip provides and<11:35:22.380> those<11:35:22.560> you<11:35:23.040> may<11:35:23.276> or<11:35:23.460> may<11:35:23.756> not<11:35:23.936> see<11:35:24.240> on<11:35:24.416> the 11:35:24.530 --> 11:35:24.540 align:start position:0% and those you may or may not see on the 11:35:24.540 --> 11:35:27.406 align:start position:0% and those you may or may not see on the network<11:35:24.660> plus<11:35:24.960> exam 11:35:27.406 --> 11:35:27.416 align:start position:0% network plus exam 11:35:27.416 --> 11:35:29.086 align:start position:0% network plus exam however<11:35:27.960> in<11:35:28.256> this<11:35:28.436> module<11:35:28.680> we're<11:35:28.860> going<11:35:28.980> to 11:35:29.086 --> 11:35:29.096 align:start position:0% however in this module we're going to 11:35:29.096 --> 11:35:30.710 align:start position:0% however in this module we're going to talk<11:35:29.220> about<11:35:29.340> some<11:35:29.640> of<11:35:29.756> the<11:35:29.880> most<11:35:30.000> essential 11:35:30.710 --> 11:35:30.720 align:start position:0% talk about some of the most essential 11:35:30.720 --> 11:35:34.426 align:start position:0% talk about some of the most essential tools<11:35:31.500> when<11:35:32.160> it<11:35:32.340> comes<11:35:32.640> to<11:35:32.820> the<11:35:33.000> tcpip<11:35:33.840> suite 11:35:34.426 --> 11:35:34.436 align:start position:0% tools when it comes to the tcpip suite 11:35:34.436 --> 11:35:36.470 align:start position:0% tools when it comes to the tcpip suite and<11:35:34.860> I<11:35:34.980> can<11:35:35.040> almost<11:35:35.220> guarantee<11:35:36.000> you<11:35:36.180> you're 11:35:36.470 --> 11:35:36.480 align:start position:0% and I can almost guarantee you you're 11:35:36.480 --> 11:35:39.406 align:start position:0% and I can almost guarantee you you're going<11:35:36.660> to<11:35:36.776> see<11:35:37.020> these<11:35:37.616> on<11:35:37.800> the<11:35:37.980> exam<11:35:38.276> so<11:35:39.116> we're 11:35:39.406 --> 11:35:39.416 align:start position:0% going to see these on the exam so we're 11:35:39.416 --> 11:35:41.390 align:start position:0% going to see these on the exam so we're first<11:35:39.660> going<11:35:40.020> to<11:35:40.200> discuss<11:35:40.680> and<11:35:40.860> demonstrate 11:35:41.390 --> 11:35:41.400 align:start position:0% first going to discuss and demonstrate 11:35:41.400 --> 11:35:45.050 align:start position:0% first going to discuss and demonstrate all<11:35:41.756> of<11:35:41.936> the<11:35:42.060> tcpip<11:35:42.900> tools<11:35:43.616> and<11:35:44.400> some<11:35:44.700> of<11:35:44.820> these 11:35:45.050 --> 11:35:45.060 align:start position:0% all of the tcpip tools and some of these 11:35:45.060 --> 11:35:47.570 align:start position:0% all of the tcpip tools and some of these tools<11:35:45.416> include<11:35:45.960> the<11:35:46.680> Ping<11:35:46.980> command<11:35:47.276> and<11:35:47.460> some 11:35:47.570 --> 11:35:47.580 align:start position:0% tools include the Ping command and some 11:35:47.580 --> 11:35:48.830 align:start position:0% tools include the Ping command and some of<11:35:47.700> these<11:35:47.756> we<11:35:47.880> might<11:35:48.060> have<11:35:48.180> seen<11:35:48.360> previously 11:35:48.830 --> 11:35:48.840 align:start position:0% of these we might have seen previously 11:35:48.840 --> 11:35:51.586 align:start position:0% of these we might have seen previously as<11:35:49.080> well<11:35:49.256> perhaps<11:35:49.680> an<11:35:49.800> A-Plus<11:35:50.340> and<11:35:51.300> some<11:35:51.480> of 11:35:51.586 --> 11:35:51.596 align:start position:0% as well perhaps an A-Plus and some of 11:35:51.596 --> 11:35:53.086 align:start position:0% as well perhaps an A-Plus and some of these<11:35:51.776> also<11:35:52.080> I'll<11:35:52.256> go<11:35:52.436> into<11:35:52.560> the<11:35:52.800> operating 11:35:53.086 --> 11:35:53.096 align:start position:0% these also I'll go into the operating 11:35:53.096 --> 11:35:55.370 align:start position:0% these also I'll go into the operating system<11:35:53.340> and<11:35:53.580> show<11:35:53.756> you<11:35:53.936> so<11:35:54.596> we're<11:35:54.900> going<11:35:55.140> to 11:35:55.370 --> 11:35:55.380 align:start position:0% system and show you so we're going to 11:35:55.380 --> 11:35:57.950 align:start position:0% system and show you so we're going to see<11:35:55.616> the<11:35:56.460> Ping<11:35:56.820> command<11:35:57.240> which<11:35:57.540> basically 11:35:57.950 --> 11:35:57.960 align:start position:0% see the Ping command which basically 11:35:57.960 --> 11:36:00.606 align:start position:0% see the Ping command which basically tests 11:36:00.606 --> 11:36:00.616 align:start position:0% 11:36:00.616 --> 11:36:05.450 align:start position:0% for<11:36:01.616> connectivity 11:36:05.450 --> 11:36:05.460 align:start position:0% 11:36:05.460 --> 11:36:07.246 align:start position:0% we're<11:36:05.880> also<11:36:06.116> going<11:36:06.240> to<11:36:06.240> look<11:36:06.416> at<11:36:06.540> the<11:36:06.900> trace 11:36:07.246 --> 11:36:07.256 align:start position:0% we're also going to look at the trace 11:36:07.256 --> 11:36:12.470 align:start position:0% we're also going to look at the trace route<11:36:07.616> command<11:36:08.480> which<11:36:09.480> basically<11:36:10.700> traces<11:36:11.700> a 11:36:12.470 --> 11:36:12.480 align:start position:0% route command which basically traces a 11:36:12.480 --> 11:36:13.370 align:start position:0% route command which basically traces a ping 11:36:13.370 --> 11:36:13.380 align:start position:0% ping 11:36:13.380 --> 11:36:14.570 align:start position:0% ping route 11:36:14.570 --> 11:36:14.580 align:start position:0% route 11:36:14.580 --> 11:36:17.746 align:start position:0% route and<11:36:15.116> remember<11:36:15.360> when<11:36:15.660> we<11:36:15.840> were<11:36:15.960> talking<11:36:16.256> about 11:36:17.746 --> 11:36:17.756 align:start position:0% and remember when we were talking about 11:36:17.756 --> 11:36:21.586 align:start position:0% and remember when we were talking about um<11:36:17.820> uh<11:36:18.840> protocols<11:36:19.740> previously<11:36:20.700> we<11:36:21.240> mentioned 11:36:21.586 --> 11:36:21.596 align:start position:0% um uh protocols previously we mentioned 11:36:21.596 --> 11:36:24.106 align:start position:0% um uh protocols previously we mentioned the<11:36:21.840> icmp<11:36:22.800> protocol 11:36:24.106 --> 11:36:24.116 align:start position:0% the icmp protocol 11:36:24.116 --> 11:36:27.170 align:start position:0% the icmp protocol the<11:36:24.540> control<11:36:24.720> messaging<11:36:25.380> protocol<11:36:25.756> and<11:36:26.756> that 11:36:27.170 --> 11:36:27.180 align:start position:0% the control messaging protocol and that 11:36:27.180 --> 11:36:29.746 align:start position:0% the control messaging protocol and that is<11:36:27.360> what<11:36:27.720> a<11:36:28.020> ping<11:36:28.320> and<11:36:28.616> a<11:36:28.800> trace<11:36:29.040> route<11:36:29.276> command 11:36:29.746 --> 11:36:29.756 align:start position:0% is what a ping and a trace route command 11:36:29.756 --> 11:36:32.510 align:start position:0% is what a ping and a trace route command use<11:36:29.936> or<11:36:30.180> these<11:36:30.480> types<11:36:30.720> of<11:36:30.840> packets 11:36:32.510 --> 11:36:32.520 align:start position:0% use or these types of packets 11:36:32.520 --> 11:36:34.010 align:start position:0% use or these types of packets so<11:36:33.060> we're<11:36:33.240> also<11:36:33.480> going<11:36:33.540> to<11:36:33.596> look<11:36:33.720> at<11:36:33.776> a 11:36:34.010 --> 11:36:34.020 align:start position:0% so we're also going to look at a 11:36:34.020 --> 11:36:37.730 align:start position:0% so we're also going to look at a protocol<11:36:34.320> analyzer<11:36:35.276> not<11:36:36.060> necessarily<11:36:36.900> a 11:36:37.730 --> 11:36:37.740 align:start position:0% protocol analyzer not necessarily a 11:36:37.740 --> 11:36:39.470 align:start position:0% protocol analyzer not necessarily a command<11:36:38.040> line<11:36:38.220> tool<11:36:38.700> but<11:36:38.880> something<11:36:39.116> that 11:36:39.470 --> 11:36:39.480 align:start position:0% command line tool but something that 11:36:39.480 --> 11:36:44.390 align:start position:0% command line tool but something that allows<11:36:39.840> us<11:36:40.020> to<11:36:40.436> analyze<11:36:41.220> the<11:36:42.000> protocols<11:36:43.220> uh<11:36:44.220> or 11:36:44.390 --> 11:36:44.400 align:start position:0% allows us to analyze the protocols uh or 11:36:44.400 --> 11:36:46.130 align:start position:0% allows us to analyze the protocols uh or rather<11:36:44.640> the<11:36:44.880> packets<11:36:45.300> that<11:36:45.480> are<11:36:45.596> going<11:36:45.776> in<11:36:45.960> and 11:36:46.130 --> 11:36:46.140 align:start position:0% rather the packets that are going in and 11:36:46.140 --> 11:36:48.370 align:start position:0% rather the packets that are going in and out<11:36:46.320> of<11:36:46.800> a 11:36:48.370 --> 11:36:48.380 align:start position:0% out of a 11:36:48.380 --> 11:36:50.810 align:start position:0% out of a network<11:36:49.380> or<11:36:49.740> system 11:36:50.810 --> 11:36:50.820 align:start position:0% network or system 11:36:50.820 --> 11:36:52.730 align:start position:0% network or system we'll<11:36:51.116> get<11:36:51.360> a<11:36:51.480> port<11:36:51.596> scanner<11:36:52.140> sort<11:36:52.436> of<11:36:52.560> does 11:36:52.730 --> 11:36:52.740 align:start position:0% we'll get a port scanner sort of does 11:36:52.740 --> 11:36:54.170 align:start position:0% we'll get a port scanner sort of does the<11:36:52.980> same<11:36:53.096> thing<11:36:53.340> we'll<11:36:53.580> talk<11:36:53.756> about<11:36:53.880> the 11:36:54.170 --> 11:36:54.180 align:start position:0% the same thing we'll talk about the 11:36:54.180 --> 11:36:56.150 align:start position:0% the same thing we'll talk about the difference<11:36:54.360> between<11:36:54.720> these<11:36:55.140> two 11:36:56.150 --> 11:36:56.160 align:start position:0% difference between these two 11:36:56.160 --> 11:36:57.950 align:start position:0% difference between these two we'll<11:36:56.460> also<11:36:56.700> get<11:36:56.820> something<11:36:57.000> called<11:36:57.180> nslookup 11:36:57.950 --> 11:36:57.960 align:start position:0% we'll also get something called nslookup 11:36:57.960 --> 11:36:59.390 align:start position:0% we'll also get something called nslookup and 11:36:59.390 --> 11:36:59.400 align:start position:0% and 11:36:59.400 --> 11:37:02.266 align:start position:0% and NS<11:37:00.116> doesn't<11:37:00.416> ring<11:37:00.720> a<11:37:00.900> bell<11:37:01.020> with<11:37:01.256> you<11:37:01.380> that<11:37:02.096> is 11:37:02.266 --> 11:37:02.276 align:start position:0% NS doesn't ring a bell with you that is 11:37:02.276 --> 11:37:07.550 align:start position:0% NS doesn't ring a bell with you that is like<11:37:02.580> DNS<11:37:03.680> or<11:37:04.680> name<11:37:05.580> server<11:37:06.116> lookup 11:37:07.550 --> 11:37:07.560 align:start position:0% like DNS or name server lookup 11:37:07.560 --> 11:37:13.606 align:start position:0% like DNS or name server lookup how<11:37:08.400> we<11:37:08.700> convert<11:37:09.180> between<11:37:09.800> an<11:37:10.800> IP<11:37:11.220> address 11:37:13.606 --> 11:37:13.616 align:start position:0% 11:37:13.616 --> 11:37:18.106 align:start position:0% and<11:37:14.400> a<11:37:14.936> fully<11:37:15.360> qualified<11:37:15.840> domain<11:37:16.740> name<11:37:17.340> such 11:37:18.106 --> 11:37:18.116 align:start position:0% and a fully qualified domain name such 11:37:18.116 --> 11:37:18.950 align:start position:0% and a fully qualified domain name such as 11:37:18.950 --> 11:37:18.960 align:start position:0% as 11:37:18.960 --> 11:37:20.990 align:start position:0% as Google 11:37:20.990 --> 11:37:21.000 align:start position:0% Google 11:37:21.000 --> 11:37:23.746 align:start position:0% Google we're<11:37:21.416> also<11:37:21.660> look<11:37:21.840> at<11:37:21.960> the<11:37:22.080> ARP<11:37:22.436> command<11:37:23.096> which 11:37:23.746 --> 11:37:23.756 align:start position:0% we're also look at the ARP command which 11:37:23.756 --> 11:37:27.350 align:start position:0% we're also look at the ARP command which allows<11:37:24.180> us<11:37:24.300> just<11:37:24.776> like<11:37:24.960> NS<11:37:25.436> DNS<11:37:26.040> which<11:37:26.520> does<11:37:26.756> a 11:37:27.350 --> 11:37:27.360 align:start position:0% allows us just like NS DNS which does a 11:37:27.360 --> 11:37:29.810 align:start position:0% allows us just like NS DNS which does a name<11:37:27.900> to<11:37:28.140> an<11:37:28.320> IP<11:37:28.560> address<11:37:28.680> ARP<11:37:29.340> is<11:37:29.580> what<11:37:29.700> is 11:37:29.810 --> 11:37:29.820 align:start position:0% name to an IP address ARP is what is 11:37:29.820 --> 11:37:31.850 align:start position:0% name to an IP address ARP is what is responsible<11:37:30.240> for<11:37:30.596> routing<11:37:31.020> and<11:37:31.436> allowed<11:37:31.740> us 11:37:31.850 --> 11:37:31.860 align:start position:0% responsible for routing and allowed us 11:37:31.860 --> 11:37:34.606 align:start position:0% responsible for routing and allowed us to<11:37:32.040> convert<11:37:32.460> between<11:37:32.700> an<11:37:33.000> IP<11:37:33.360> address 11:37:34.606 --> 11:37:34.616 align:start position:0% to convert between an IP address 11:37:34.616 --> 11:37:38.330 align:start position:0% to convert between an IP address and<11:37:35.040> a<11:37:35.220> MAC<11:37:35.520> address<11:37:35.776> or<11:37:36.776> physical<11:37:37.020> address 11:37:38.330 --> 11:37:38.340 align:start position:0% and a MAC address or physical address 11:37:38.340 --> 11:37:39.890 align:start position:0% and a MAC address or physical address so<11:37:38.756> you<11:37:38.880> can<11:37:39.000> see<11:37:39.116> where<11:37:39.300> this<11:37:39.480> is<11:37:39.660> really 11:37:39.890 --> 11:37:39.900 align:start position:0% so you can see where this is really 11:37:39.900 --> 11:37:42.890 align:start position:0% so you can see where this is really going<11:37:40.080> to<11:37:40.256> come<11:37:40.436> into<11:37:41.276> uh<11:37:42.000> into<11:37:42.300> handy<11:37:42.720> when 11:37:42.890 --> 11:37:42.900 align:start position:0% going to come into uh into handy when 11:37:42.900 --> 11:37:47.086 align:start position:0% going to come into uh into handy when we're<11:37:43.020> talking<11:37:43.200> about<11:37:43.256> routing<11:37:43.680> and<11:37:43.800> switches 11:37:47.086 --> 11:37:47.096 align:start position:0% 11:37:47.096 --> 11:37:49.310 align:start position:0% finally<11:37:47.640> we're<11:37:47.820> going<11:37:47.936> to<11:37:48.000> look<11:37:48.180> at<11:37:48.360> the<11:37:48.776> route 11:37:49.310 --> 11:37:49.320 align:start position:0% finally we're going to look at the route 11:37:49.320 --> 11:37:51.170 align:start position:0% finally we're going to look at the route command<11:37:49.860> which<11:37:50.096> can<11:37:50.340> present<11:37:50.700> us<11:37:50.880> with 11:37:51.170 --> 11:37:51.180 align:start position:0% command which can present us with 11:37:51.180 --> 11:37:53.510 align:start position:0% command which can present us with routing<11:37:51.660> tables 11:37:53.510 --> 11:37:53.520 align:start position:0% routing tables 11:37:53.520 --> 11:37:55.550 align:start position:0% routing tables and<11:37:54.000> it's<11:37:54.240> specifically<11:37:54.660> more<11:37:55.020> or<11:37:55.140> less<11:37:55.256> used 11:37:55.550 --> 11:37:55.560 align:start position:0% and it's specifically more or less used 11:37:55.560 --> 11:37:57.530 align:start position:0% and it's specifically more or less used when<11:37:55.800> we're<11:37:55.916> dealing<11:37:56.160> with<11:37:56.340> routers<11:37:56.880> not<11:37:57.300> so 11:37:57.530 --> 11:37:57.540 align:start position:0% when we're dealing with routers not so 11:37:57.540 --> 11:38:00.890 align:start position:0% when we're dealing with routers not so much<11:37:57.720> in<11:37:58.256> Windows 11:38:00.890 --> 11:38:00.900 align:start position:0% 11:38:00.900 --> 11:38:03.890 align:start position:0% all<11:38:01.256> right<11:38:01.436> so<11:38:01.860> first<11:38:02.160> the<11:38:02.580> Ping<11:38:02.820> command<11:38:03.300> the 11:38:03.890 --> 11:38:03.900 align:start position:0% all right so first the Ping command the 11:38:03.900 --> 11:38:05.450 align:start position:0% all right so first the Ping command the Ping<11:38:04.256> tool<11:38:04.560> in<11:38:04.680> the<11:38:04.800> Ping<11:38:04.980> command<11:38:05.276> are 11:38:05.450 --> 11:38:05.460 align:start position:0% Ping tool in the Ping command are 11:38:05.460 --> 11:38:07.010 align:start position:0% Ping tool in the Ping command are extremely<11:38:05.936> useful<11:38:06.300> when<11:38:06.540> it<11:38:06.660> comes<11:38:06.840> to 11:38:07.010 --> 11:38:07.020 align:start position:0% extremely useful when it comes to 11:38:07.020 --> 11:38:09.490 align:start position:0% extremely useful when it comes to troubleshooting<11:38:07.740> and<11:38:08.276> testing<11:38:08.700> connectivity 11:38:09.490 --> 11:38:09.500 align:start position:0% troubleshooting and testing connectivity 11:38:09.500 --> 11:38:12.230 align:start position:0% troubleshooting and testing connectivity basically<11:38:10.500> what<11:38:11.040> the<11:38:11.160> tool<11:38:11.400> does<11:38:11.520> is<11:38:11.700> send<11:38:12.060> a 11:38:12.230 --> 11:38:12.240 align:start position:0% basically what the tool does is send a 11:38:12.240 --> 11:38:14.450 align:start position:0% basically what the tool does is send a packet<11:38:12.660> of<11:38:12.960> information<11:38:13.436> in<11:38:13.916> that<11:38:14.040> packet 11:38:14.450 --> 11:38:14.460 align:start position:0% packet of information in that packet 11:38:14.460 --> 11:38:17.086 align:start position:0% packet of information in that packet again<11:38:14.640> is<11:38:15.360> icmp 11:38:17.086 --> 11:38:17.096 align:start position:0% again is icmp 11:38:17.096 --> 11:38:19.426 align:start position:0% again is icmp through<11:38:17.700> a<11:38:17.936> connection<11:38:18.060> and<11:38:18.540> waits<11:38:19.020> to<11:38:19.140> see<11:38:19.256> if 11:38:19.426 --> 11:38:19.436 align:start position:0% through a connection and waits to see if 11:38:19.436 --> 11:38:21.650 align:start position:0% through a connection and waits to see if it<11:38:19.616> receives<11:38:19.916> some<11:38:20.160> packets<11:38:20.520> back<11:38:20.820> this<11:38:21.480> is 11:38:21.650 --> 11:38:21.660 align:start position:0% it receives some packets back this is 11:38:21.660 --> 11:38:24.406 align:start position:0% it receives some packets back this is not<11:38:21.840> unlike<11:38:22.256> when<11:38:22.616> you<11:38:22.800> used<11:38:22.980> to<11:38:23.160> see<11:38:23.460> the 11:38:24.406 --> 11:38:24.416 align:start position:0% not unlike when you used to see the 11:38:24.416 --> 11:38:28.130 align:start position:0% not unlike when you used to see the radar<11:38:24.960> screens<11:38:25.436> on<11:38:26.096> a<11:38:26.400> computer<11:38:26.460> on<11:38:26.880> a<11:38:27.000> TV<11:38:27.300> or 11:38:28.130 --> 11:38:28.140 align:start position:0% radar screens on a computer on a TV or 11:38:28.140 --> 11:38:31.130 align:start position:0% radar screens on a computer on a TV or program<11:38:28.436> we're<11:38:28.800> talking<11:38:29.040> about<11:38:29.276> with<11:38:30.000> um<11:38:30.140> uh 11:38:31.130 --> 11:38:31.140 align:start position:0% program we're talking about with um uh 11:38:31.140 --> 11:38:33.050 align:start position:0% program we're talking about with um uh submarines<11:38:31.680> for<11:38:31.980> instance<11:38:32.220> and<11:38:32.756> you<11:38:32.880> would 11:38:33.050 --> 11:38:33.060 align:start position:0% submarines for instance and you would 11:38:33.060 --> 11:38:35.266 align:start position:0% submarines for instance and you would see<11:38:33.300> basically<11:38:33.840> a<11:38:34.140> submarine<11:38:34.616> here<11:38:34.860> and<11:38:35.040> you'd 11:38:35.266 --> 11:38:35.276 align:start position:0% see basically a submarine here and you'd 11:38:35.276 --> 11:38:36.650 align:start position:0% see basically a submarine here and you'd hear<11:38:35.460> a<11:38:35.700> ping 11:38:36.650 --> 11:38:36.660 align:start position:0% hear a ping 11:38:36.660 --> 11:38:39.290 align:start position:0% hear a ping coming<11:38:37.080> off<11:38:37.560> of<11:38:38.096> that<11:38:38.340> so<11:38:38.520> it<11:38:38.700> gets<11:38:39.000> its<11:38:39.060> name 11:38:39.290 --> 11:38:39.300 align:start position:0% coming off of that so it gets its name 11:38:39.300 --> 11:38:41.810 align:start position:0% coming off of that so it gets its name from<11:38:39.596> that<11:38:39.776> sort<11:38:40.020> of<11:38:40.200> sound<11:38:40.560> so<11:38:41.276> the<11:38:41.460> data 11:38:41.810 --> 11:38:41.820 align:start position:0% from that sort of sound so the data 11:38:41.820 --> 11:38:44.450 align:start position:0% from that sort of sound so the data literally<11:38:42.180> bounces<11:38:42.776> or<11:38:43.080> pings<11:38:43.380> right<11:38:43.860> back<11:38:44.096> if 11:38:44.450 --> 11:38:44.460 align:start position:0% literally bounces or pings right back if 11:38:44.460 --> 11:38:46.370 align:start position:0% literally bounces or pings right back if there's<11:38:44.580> an<11:38:44.820> established<11:38:45.300> connection 11:38:46.370 --> 11:38:46.380 align:start position:0% there's an established connection 11:38:46.380 --> 11:38:49.310 align:start position:0% there's an established connection can<11:38:46.860> be<11:38:46.980> also<11:38:47.276> used<11:38:47.460> to<11:38:47.756> test<11:38:48.000> the<11:38:48.416> maximum 11:38:49.310 --> 11:38:49.320 align:start position:0% can be also used to test the maximum 11:38:49.320 --> 11:38:52.010 align:start position:0% can be also used to test the maximum transmission<11:38:49.680> unit<11:38:50.160> or<11:38:50.580> the<11:38:50.756> mtus<11:38:51.480> and 11:38:52.010 --> 11:38:52.020 align:start position:0% transmission unit or the mtus and 11:38:52.020 --> 11:38:53.510 align:start position:0% transmission unit or the mtus and remember<11:38:52.140> we<11:38:52.436> talked<11:38:52.800> about<11:38:52.860> that<11:38:53.160> when<11:38:53.400> we 11:38:53.510 --> 11:38:53.520 align:start position:0% remember we talked about that when we 11:38:53.520 --> 11:38:57.586 align:start position:0% remember we talked about that when we dealt<11:38:53.820> with<11:38:53.880> an<11:38:54.116> MTU<11:38:54.840> black<11:38:55.800> hole<11:38:56.820> was<11:38:57.240> in<11:38:57.480> a 11:38:57.586 --> 11:38:57.596 align:start position:0% dealt with an MTU black hole was in a 11:38:57.596 --> 11:38:59.990 align:start position:0% dealt with an MTU black hole was in a previous<11:38:57.720> lesson<11:38:58.740> this<11:38:59.220> is<11:38:59.400> the<11:38:59.640> maximum 11:38:59.990 --> 11:39:00.000 align:start position:0% previous lesson this is the maximum 11:39:00.000 --> 11:39:02.870 align:start position:0% previous lesson this is the maximum amount<11:39:00.116> of<11:39:00.360> data<11:39:00.840> packets<11:39:01.200> that<11:39:02.160> can<11:39:02.340> be<11:39:02.520> sent 11:39:02.870 --> 11:39:02.880 align:start position:0% amount of data packets that can be sent 11:39:02.880 --> 11:39:05.210 align:start position:0% amount of data packets that can be sent over<11:39:03.360> a<11:39:03.596> network<11:39:03.720> at<11:39:04.080> any<11:39:04.320> one<11:39:04.560> time<11:39:04.740> or<11:39:05.040> the 11:39:05.210 --> 11:39:05.220 align:start position:0% over a network at any one time or the 11:39:05.220 --> 11:39:07.730 align:start position:0% over a network at any one time or the maximum<11:39:05.820> size<11:39:06.240> of<11:39:06.480> that<11:39:06.596> data<11:39:07.020> packets<11:39:07.320> so 11:39:07.730 --> 11:39:07.740 align:start position:0% maximum size of that data packets so 11:39:07.740 --> 11:39:09.470 align:start position:0% maximum size of that data packets so using<11:39:08.096> this<11:39:08.220> you<11:39:08.400> can<11:39:08.520> test<11:39:08.756> the<11:39:09.000> time<11:39:09.180> it 11:39:09.470 --> 11:39:09.480 align:start position:0% using this you can test the time it 11:39:09.480 --> 11:39:12.406 align:start position:0% using this you can test the time it takes<11:39:09.660> in<11:39:09.900> milliseconds<11:39:10.680> for<11:39:11.276> data<11:39:11.756> to<11:39:12.180> travel 11:39:12.406 --> 11:39:12.416 align:start position:0% takes in milliseconds for data to travel 11:39:12.416 --> 11:39:14.690 align:start position:0% takes in milliseconds for data to travel end<11:39:12.900> to<11:39:13.080> Android<11:39:13.320> to<11:39:13.800> other<11:39:13.916> devices<11:39:14.276> on<11:39:14.580> the 11:39:14.690 --> 11:39:14.700 align:start position:0% end to Android to other devices on the 11:39:14.700 --> 11:39:15.830 align:start position:0% end to Android to other devices on the network 11:39:15.830 --> 11:39:15.840 align:start position:0% network 11:39:15.840 --> 11:39:17.870 align:start position:0% network this<11:39:16.256> can<11:39:16.436> also<11:39:16.616> be<11:39:16.740> done<11:39:16.916> on<11:39:17.096> the<11:39:17.340> localhost 11:39:17.870 --> 11:39:17.880 align:start position:0% this can also be done on the localhost 11:39:17.880 --> 11:39:21.070 align:start position:0% this can also be done on the localhost and<11:39:18.240> you<11:39:18.360> remember<11:39:18.540> the<11:39:18.840> localhost<11:39:19.256> is 11:39:21.070 --> 11:39:21.080 align:start position:0% and you remember the localhost is 11:39:21.080 --> 11:39:26.390 align:start position:0% and you remember the localhost is 127.0.0.1<11:39:22.080> that's<11:39:22.860> the<11:39:23.096> IP<11:39:23.460> address<11:39:23.700> for<11:39:24.060> it 11:39:26.390 --> 11:39:26.400 align:start position:0% 11:39:26.400 --> 11:39:28.426 align:start position:0% and<11:39:26.880> we<11:39:27.000> can<11:39:27.116> test<11:39:27.300> this<11:39:27.480> all<11:39:27.660> by<11:39:27.900> opening<11:39:28.256> the 11:39:28.426 --> 11:39:28.436 align:start position:0% and we can test this all by opening the 11:39:28.436 --> 11:39:32.030 align:start position:0% and we can test this all by opening the command<11:39:28.740> prompt<11:39:29.160> and<11:39:29.640> typing<11:39:30.060> in<11:39:30.416> ping<11:39:31.320> and 11:39:32.030 --> 11:39:32.040 align:start position:0% command prompt and typing in ping and 11:39:32.040 --> 11:39:34.130 align:start position:0% command prompt and typing in ping and then<11:39:32.276> the<11:39:32.820> IP<11:39:33.116> address 11:39:34.130 --> 11:39:34.140 align:start position:0% then the IP address 11:39:34.140 --> 11:39:37.010 align:start position:0% then the IP address so<11:39:34.740> let's<11:39:35.040> take<11:39:35.220> a<11:39:35.340> look<11:39:35.460> at<11:39:35.700> this<11:39:35.880> uh<11:39:36.660> for<11:39:36.900> just 11:39:37.010 --> 11:39:37.020 align:start position:0% so let's take a look at this uh for just 11:39:37.020 --> 11:39:40.370 align:start position:0% so let's take a look at this uh for just a<11:39:37.200> second 11:39:40.370 --> 11:39:40.380 align:start position:0% 11:39:40.380 --> 11:39:42.890 align:start position:0% if<11:39:40.916> we're<11:39:41.096> here<11:39:41.340> and<11:39:41.460> we<11:39:41.756> have<11:39:42.000> our<11:39:42.480> Command 11:39:42.890 --> 11:39:42.900 align:start position:0% if we're here and we have our Command 11:39:42.900 --> 11:39:45.106 align:start position:0% if we're here and we have our Command Prompt<11:39:43.256> and<11:39:44.040> I<11:39:44.220> wanted<11:39:44.340> to<11:39:44.520> type<11:39:44.700> for<11:39:44.880> instance 11:39:45.106 --> 11:39:45.116 align:start position:0% Prompt and I wanted to type for instance 11:39:45.116 --> 11:39:48.406 align:start position:0% Prompt and I wanted to type for instance ping<11:39:45.540> 127.0.0.1 11:39:48.406 --> 11:39:48.416 align:start position:0% ping 127.0.0.1 11:39:48.416 --> 11:39:51.050 align:start position:0% ping 127.0.0.1 which<11:39:48.776> would<11:39:48.960> be<11:39:49.140> the<11:39:49.680> Local<11:39:49.860> Host 11:39:51.050 --> 11:39:51.060 align:start position:0% which would be the Local Host 11:39:51.060 --> 11:39:54.050 align:start position:0% which would be the Local Host I<11:39:51.480> can<11:39:51.596> tell<11:39:51.776> that<11:39:52.500> my<11:39:52.800> time<11:39:53.040> is<11:39:53.340> less<11:39:53.580> than<11:39:53.820> one 11:39:54.050 --> 11:39:54.060 align:start position:0% I can tell that my time is less than one 11:39:54.060 --> 11:39:56.030 align:start position:0% I can tell that my time is less than one millisecond<11:39:54.596> which<11:39:54.900> makes<11:39:55.140> complete<11:39:55.740> sense 11:39:56.030 --> 11:39:56.040 align:start position:0% millisecond which makes complete sense 11:39:56.040 --> 11:39:58.670 align:start position:0% millisecond which makes complete sense since<11:39:56.880> there<11:39:57.300> should<11:39:57.540> be<11:39:57.720> no<11:39:58.020> loss<11:39:58.320> of<11:39:58.380> data<11:39:58.680> it 11:39:58.670 --> 11:39:58.680 align:start position:0% since there should be no loss of data it 11:39:58.680 --> 11:40:00.766 align:start position:0% since there should be no loss of data it should<11:39:58.916> take<11:39:59.096> no<11:39:59.460> time<11:39:59.756> and<11:40:00.240> you<11:40:00.360> can<11:40:00.480> see<11:40:00.596> that 11:40:00.766 --> 11:40:00.776 align:start position:0% should take no time and you can see that 11:40:00.776 --> 11:40:03.350 align:start position:0% should take no time and you can see that no<11:40:01.020> loss<11:40:01.320> of<11:40:01.380> data<11:40:01.740> right<11:40:02.460> here 11:40:03.350 --> 11:40:03.360 align:start position:0% no loss of data right here 11:40:03.360 --> 11:40:05.630 align:start position:0% no loss of data right here right<11:40:03.960> because<11:40:04.320> we're<11:40:04.740> sending<11:40:05.096> it<11:40:05.220> there<11:40:05.460> and 11:40:05.630 --> 11:40:05.640 align:start position:0% right because we're sending it there and 11:40:05.640 --> 11:40:07.790 align:start position:0% right because we're sending it there and back<11:40:05.880> and<11:40:06.596> obviously<11:40:07.080> we're<11:40:07.256> dealing<11:40:07.616> with 11:40:07.790 --> 11:40:07.800 align:start position:0% back and obviously we're dealing with 11:40:07.800 --> 11:40:11.690 align:start position:0% back and obviously we're dealing with ourselves<11:40:08.220> the<11:40:08.640> local<11:40:08.820> host<11:40:09.180> or<11:40:09.960> the<11:40:10.700> 127.0.01 11:40:11.690 --> 11:40:11.700 align:start position:0% ourselves the local host or the 127.0.01 11:40:11.700 --> 11:40:13.550 align:start position:0% ourselves the local host or the 127.0.01 so<11:40:11.936> it<11:40:12.060> shouldn't<11:40:12.300> be<11:40:12.416> an<11:40:12.540> issue<11:40:12.776> and<11:40:13.140> if<11:40:13.320> we<11:40:13.436> do 11:40:13.550 --> 11:40:13.560 align:start position:0% so it shouldn't be an issue and if we do 11:40:13.560 --> 11:40:15.350 align:start position:0% so it shouldn't be an issue and if we do that<11:40:13.800> notice<11:40:14.340> that<11:40:14.460> when<11:40:14.580> I<11:40:14.700> use<11:40:14.820> localhost 11:40:15.350 --> 11:40:15.360 align:start position:0% that notice that when I use localhost 11:40:15.360 --> 11:40:19.550 align:start position:0% that notice that when I use localhost I'm<11:40:16.140> using<11:40:16.640> my<11:40:17.640> own<11:40:17.700> name<11:40:17.936> and<11:40:18.416> and<11:40:19.020> it's<11:40:19.256> also 11:40:19.550 --> 11:40:19.560 align:start position:0% I'm using my own name and and it's also 11:40:19.560 --> 11:40:22.490 align:start position:0% I'm using my own name and and it's also giving<11:40:19.616> the<11:40:19.860> IPv6<11:40:20.580> IP<11:40:21.116> address<11:40:21.240> here<11:40:21.660> now<11:40:22.200> if<11:40:22.320> I 11:40:22.490 --> 11:40:22.500 align:start position:0% giving the IPv6 IP address here now if I 11:40:22.500 --> 11:40:24.230 align:start position:0% giving the IPv6 IP address here now if I clear<11:40:22.616> the<11:40:22.860> screen<11:40:23.040> for<11:40:23.276> a<11:40:23.400> second<11:40:23.520> I<11:40:23.880> can<11:40:23.936> also 11:40:24.230 --> 11:40:24.240 align:start position:0% clear the screen for a second I can also 11:40:24.240 --> 11:40:26.870 align:start position:0% clear the screen for a second I can also for<11:40:24.480> instance<11:40:24.720> ping<11:40:25.140> google.com<11:40:25.756> and<11:40:26.756> you'll 11:40:26.870 --> 11:40:26.880 align:start position:0% for instance ping google.com and you'll 11:40:26.880 --> 11:40:29.266 align:start position:0% for instance ping google.com and you'll see<11:40:27.060> that<11:40:27.300> it<11:40:27.480> actually<11:40:27.660> sends<11:40:28.320> first<11:40:28.916> it 11:40:29.266 --> 11:40:29.276 align:start position:0% see that it actually sends first it 11:40:29.276 --> 11:40:31.010 align:start position:0% see that it actually sends first it figures<11:40:29.700> out<11:40:29.880> what<11:40:30.000> the<11:40:30.116> IP<11:40:30.360> address<11:40:30.540> is<11:40:30.840> and 11:40:31.010 --> 11:40:31.020 align:start position:0% figures out what the IP address is and 11:40:31.020 --> 11:40:32.870 align:start position:0% figures out what the IP address is and then<11:40:31.200> sends<11:40:31.616> that<11:40:31.800> and<11:40:32.040> it<11:40:32.160> gives<11:40:32.340> us<11:40:32.460> the<11:40:32.700> time 11:40:32.870 --> 11:40:32.880 align:start position:0% then sends that and it gives us the time 11:40:32.880 --> 11:40:34.190 align:start position:0% then sends that and it gives us the time that<11:40:33.180> it<11:40:33.360> takes 11:40:34.190 --> 11:40:34.200 align:start position:0% that it takes 11:40:34.200 --> 11:40:36.350 align:start position:0% that it takes to<11:40:34.616> get<11:40:34.740> there<11:40:34.860> and<11:40:35.040> back<11:40:35.220> it<11:40:35.756> also<11:40:36.000> gives<11:40:36.116> us 11:40:36.350 --> 11:40:36.360 align:start position:0% to get there and back it also gives us 11:40:36.360 --> 11:40:38.746 align:start position:0% to get there and back it also gives us some<11:40:36.540> statistics<11:40:37.500> for<11:40:37.800> instance<11:40:38.040> it<11:40:38.340> was<11:40:38.520> sent 11:40:38.746 --> 11:40:38.756 align:start position:0% some statistics for instance it was sent 11:40:38.756 --> 11:40:40.790 align:start position:0% some statistics for instance it was sent four<11:40:39.300> of<11:40:39.480> them<11:40:39.540> were<11:40:39.720> sent<11:40:39.900> for<11:40:40.140> them<11:40:40.320> received 11:40:40.790 --> 11:40:40.800 align:start position:0% four of them were sent for them received 11:40:40.800 --> 11:40:43.970 align:start position:0% four of them were sent for them received zero<11:40:41.160> lost<11:40:41.340> and<11:40:42.000> so<11:40:42.180> we<11:40:42.360> know<11:40:42.540> that<11:40:42.840> on<11:40:43.800> average 11:40:43.970 --> 11:40:43.980 align:start position:0% zero lost and so we know that on average 11:40:43.980 --> 11:40:45.950 align:start position:0% zero lost and so we know that on average this<11:40:44.400> is<11:40:44.520> taking<11:40:44.640> 13<11:40:45.000> milliseconds<11:40:45.660> to<11:40:45.840> get 11:40:45.950 --> 11:40:45.960 align:start position:0% this is taking 13 milliseconds to get 11:40:45.960 --> 11:40:48.170 align:start position:0% this is taking 13 milliseconds to get from<11:40:46.140> us<11:40:46.320> to<11:40:46.740> Google<11:40:46.916> and<11:40:47.580> if<11:40:47.880> you<11:40:48.000> imagine 11:40:48.170 --> 11:40:48.180 align:start position:0% from us to Google and if you imagine 11:40:48.180 --> 11:40:52.070 align:start position:0% from us to Google and if you imagine that<11:40:48.540> this<11:40:48.776> was<11:40:49.140> a<11:40:49.800> local<11:40:50.400> host<11:40:50.756> uh<11:40:51.540> or<11:40:51.720> rather 11:40:52.070 --> 11:40:52.080 align:start position:0% that this was a local host uh or rather 11:40:52.080 --> 11:40:54.830 align:start position:0% that this was a local host uh or rather a<11:40:52.320> sorry<11:40:52.616> a<11:40:52.916> local<11:40:53.276> uh<11:40:53.936> server<11:40:54.300> on<11:40:54.480> my<11:40:54.660> network 11:40:54.830 --> 11:40:54.840 align:start position:0% a sorry a local uh server on my network 11:40:54.840 --> 11:40:57.406 align:start position:0% a sorry a local uh server on my network and<11:40:55.560> I<11:40:55.740> was<11:40:55.916> rebooting<11:40:56.460> that<11:40:56.700> server<11:40:57.060> this 11:40:57.406 --> 11:40:57.416 align:start position:0% and I was rebooting that server this 11:40:57.416 --> 11:40:58.850 align:start position:0% and I was rebooting that server this could<11:40:57.596> help<11:40:57.720> me<11:40:57.840> tell<11:40:58.020> whether<11:40:58.320> the<11:40:58.500> server<11:40:58.800> is 11:40:58.850 --> 11:40:58.860 align:start position:0% could help me tell whether the server is 11:40:58.860 --> 11:41:00.766 align:start position:0% could help me tell whether the server is back<11:40:59.040> up<11:40:59.220> again<11:40:59.460> and<11:41:00.060> one<11:41:00.240> of<11:41:00.360> the<11:41:00.416> things<11:41:00.540> I 11:41:00.766 --> 11:41:00.776 align:start position:0% back up again and one of the things I 11:41:00.776 --> 11:41:02.450 align:start position:0% back up again and one of the things I might<11:41:00.900> want<11:41:01.080> to<11:41:01.200> do<11:41:01.320> with<11:41:01.560> that<11:41:01.740> and<11:41:02.160> I'm<11:41:02.276> just 11:41:02.450 --> 11:41:02.460 align:start position:0% might want to do with that and I'm just 11:41:02.460 --> 11:41:03.530 align:start position:0% might want to do with that and I'm just going<11:41:02.580> to<11:41:02.700> use 11:41:03.530 --> 11:41:03.540 align:start position:0% going to use 11:41:03.540 --> 11:41:06.106 align:start position:0% going to use The<11:41:04.140> Local<11:41:04.256> Host<11:41:04.500> right<11:41:04.860> now<11:41:05.040> is<11:41:05.460> use<11:41:05.700> the 11:41:06.106 --> 11:41:06.116 align:start position:0% The Local Host right now is use the 11:41:06.116 --> 11:41:08.570 align:start position:0% The Local Host right now is use the slash<11:41:06.900> T 11:41:08.570 --> 11:41:08.580 align:start position:0% slash T 11:41:08.580 --> 11:41:09.350 align:start position:0% slash T um 11:41:09.350 --> 11:41:09.360 align:start position:0% um 11:41:09.360 --> 11:41:11.510 align:start position:0% um switch<11:41:09.960> and<11:41:10.380> what<11:41:10.560> this<11:41:10.680> will<11:41:10.800> do<11:41:10.980> is<11:41:11.160> it'll 11:41:11.510 --> 11:41:11.520 align:start position:0% switch and what this will do is it'll 11:41:11.520 --> 11:41:14.150 align:start position:0% switch and what this will do is it'll continually<11:41:12.300> ping<11:41:12.900> the<11:41:13.380> same<11:41:13.560> IP<11:41:13.916> address 11:41:14.150 --> 11:41:14.160 align:start position:0% continually ping the same IP address 11:41:14.160 --> 11:41:17.330 align:start position:0% continually ping the same IP address over<11:41:15.116> and<11:41:15.300> over<11:41:15.480> again<11:41:15.660> now<11:41:16.320> I<11:41:16.616> so<11:41:17.096> for 11:41:17.330 --> 11:41:17.340 align:start position:0% over and over again now I so for 11:41:17.340 --> 11:41:18.650 align:start position:0% over and over again now I so for instance<11:41:17.580> if<11:41:17.756> I<11:41:17.880> was<11:41:18.000> waiting<11:41:18.180> for<11:41:18.300> a<11:41:18.416> server 11:41:18.650 --> 11:41:18.660 align:start position:0% instance if I was waiting for a server 11:41:18.660 --> 11:41:20.086 align:start position:0% instance if I was waiting for a server to<11:41:18.840> come<11:41:18.960> back<11:41:19.080> online<11:41:19.256> this<11:41:19.740> would<11:41:19.860> be<11:41:19.980> an 11:41:20.086 --> 11:41:20.096 align:start position:0% to come back online this would be an 11:41:20.096 --> 11:41:21.950 align:start position:0% to come back online this would be an easy<11:41:20.276> way<11:41:20.520> for<11:41:20.700> me<11:41:20.820> to<11:41:21.060> tell<11:41:21.180> whether<11:41:21.776> it's 11:41:21.950 --> 11:41:21.960 align:start position:0% easy way for me to tell whether it's 11:41:21.960 --> 11:41:25.246 align:start position:0% easy way for me to tell whether it's come<11:41:22.200> back<11:41:22.436> online<11:41:22.680> or<11:41:23.400> not<11:41:23.580> and<11:41:24.060> I<11:41:24.240> could<11:41:24.360> exit 11:41:25.246 --> 11:41:25.256 align:start position:0% come back online or not and I could exit 11:41:25.256 --> 11:41:28.606 align:start position:0% come back online or not and I could exit that<11:41:25.380> by<11:41:25.616> pressing<11:41:25.980> Ctrl<11:41:26.700> C<11:41:27.300> all<11:41:27.900> right 11:41:28.606 --> 11:41:28.616 align:start position:0% that by pressing Ctrl C all right 11:41:28.616 --> 11:41:30.230 align:start position:0% that by pressing Ctrl C all right so<11:41:28.860> the<11:41:29.040> next<11:41:29.160> one<11:41:29.340> I<11:41:29.460> want<11:41:29.580> to<11:41:29.640> talk<11:41:29.756> about<11:41:29.880> is 11:41:30.230 --> 11:41:30.240 align:start position:0% so the next one I want to talk about is 11:41:30.240 --> 11:41:32.150 align:start position:0% so the next one I want to talk about is trace<11:41:30.660> route<11:41:30.900> which<11:41:31.256> actually<11:41:31.436> goes<11:41:31.800> hand<11:41:31.980> in 11:41:32.150 --> 11:41:32.160 align:start position:0% trace route which actually goes hand in 11:41:32.160 --> 11:41:35.406 align:start position:0% trace route which actually goes hand in hand<11:41:32.276> with<11:41:32.520> ping<11:41:32.820> because<11:41:33.240> he<11:41:33.540> also<11:41:33.900> uses<11:41:34.256> that 11:41:35.406 --> 11:41:35.416 align:start position:0% hand with ping because he also uses that 11:41:35.416 --> 11:41:38.570 align:start position:0% hand with ping because he also uses that icmp<11:41:36.416> data<11:41:37.380> packet<11:41:37.740> or 11:41:38.570 --> 11:41:38.580 align:start position:0% icmp data packet or 11:41:38.580 --> 11:41:42.050 align:start position:0% icmp data packet or protocol<11:41:39.740> it<11:41:40.740> basically<11:41:41.160> tells<11:41:41.520> us<11:41:41.640> the<11:41:41.936> time 11:41:42.050 --> 11:41:42.060 align:start position:0% protocol it basically tells us the time 11:41:42.060 --> 11:41:44.266 align:start position:0% protocol it basically tells us the time it<11:41:42.360> takes<11:41:42.540> for<11:41:42.776> a<11:41:42.900> pack<11:41:43.080> to<11:41:43.380> travel<11:41:43.616> between 11:41:44.266 --> 11:41:44.276 align:start position:0% it takes for a pack to travel between 11:41:44.276 --> 11:41:46.606 align:start position:0% it takes for a pack to travel between different<11:41:44.700> routers<11:41:45.180> and<11:41:45.360> devices<11:41:45.720> and<11:41:46.436> we 11:41:46.606 --> 11:41:46.616 align:start position:0% different routers and devices and we 11:41:46.616 --> 11:41:49.790 align:start position:0% different routers and devices and we call<11:41:46.860> this<11:41:47.160> the<11:41:47.700> amount<11:41:47.936> of<11:41:48.116> hops<11:41:48.840> along<11:41:49.256> the 11:41:49.790 --> 11:41:49.800 align:start position:0% call this the amount of hops along the 11:41:49.800 --> 11:41:52.906 align:start position:0% call this the amount of hops along the uh<11:41:50.460> the<11:41:50.820> network<11:41:50.936> so<11:41:51.596> not<11:41:51.840> only<11:41:51.960> tests<11:41:52.500> where 11:41:52.906 --> 11:41:52.916 align:start position:0% uh the network so not only tests where 11:41:52.916 --> 11:41:55.310 align:start position:0% uh the network so not only tests where connectivity<11:41:53.580> might<11:41:53.880> have<11:41:54.000> been<11:41:54.116> lost<11:41:54.360> but 11:41:55.310 --> 11:41:55.320 align:start position:0% connectivity might have been lost but 11:41:55.320 --> 11:41:57.230 align:start position:0% connectivity might have been lost but it's<11:41:55.436> also<11:41:55.740> going<11:41:55.916> to<11:41:56.096> test 11:41:57.230 --> 11:41:57.240 align:start position:0% it's also going to test 11:41:57.240 --> 11:41:58.570 align:start position:0% it's also going to test um 11:41:58.570 --> 11:41:58.580 align:start position:0% um 11:41:58.580 --> 11:42:01.190 align:start position:0% um the<11:41:59.580> time<11:41:59.756> that<11:42:00.000> it<11:42:00.116> takes<11:42:00.300> to<11:42:00.480> get<11:42:00.596> from<11:42:00.960> one 11:42:01.190 --> 11:42:01.200 align:start position:0% the time that it takes to get from one 11:42:01.200 --> 11:42:02.870 align:start position:0% the time that it takes to get from one end<11:42:01.560> to<11:42:01.860> the<11:42:02.040> other<11:42:02.160> end<11:42:02.340> of<11:42:02.580> the<11:42:02.700> connection 11:42:02.870 --> 11:42:02.880 align:start position:0% end to the other end of the connection 11:42:02.880 --> 11:42:05.210 align:start position:0% end to the other end of the connection and<11:42:03.660> it's<11:42:03.776> also<11:42:04.080> going<11:42:04.256> to<11:42:04.436> also<11:42:04.740> show<11:42:04.860> us<11:42:05.040> the 11:42:05.210 --> 11:42:05.220 align:start position:0% and it's also going to also show us the 11:42:05.220 --> 11:42:06.830 align:start position:0% and it's also going to also show us the number<11:42:05.400> of<11:42:05.580> hops 11:42:06.830 --> 11:42:06.840 align:start position:0% number of hops 11:42:06.840 --> 11:42:10.190 align:start position:0% number of hops between<11:42:07.500> those<11:42:08.160> computers<11:42:08.640> so<11:42:08.936> for<11:42:09.180> instance 11:42:10.190 --> 11:42:10.200 align:start position:0% between those computers so for instance 11:42:10.200 --> 11:42:12.230 align:start position:0% between those computers so for instance between<11:42:10.980> me<11:42:11.276> and<11:42:11.400> Google<11:42:11.520> there<11:42:11.880> might<11:42:12.060> be 11:42:12.230 --> 11:42:12.240 align:start position:0% between me and Google there might be 11:42:12.240 --> 11:42:15.050 align:start position:0% between me and Google there might be four<11:42:12.596> different<11:42:12.840> computers<11:42:13.436> and<11:42:14.160> so 11:42:15.050 --> 11:42:15.060 align:start position:0% four different computers and so 11:42:15.060 --> 11:42:19.130 align:start position:0% four different computers and so each<11:42:15.540> one<11:42:15.720> of<11:42:15.840> these<11:42:16.020> is<11:42:16.320> called<11:42:16.560> a<11:42:16.916> hop 11:42:19.130 --> 11:42:19.140 align:start position:0% 11:42:19.140 --> 11:42:21.830 align:start position:0% and<11:42:19.500> we<11:42:19.616> can<11:42:19.740> measure<11:42:20.096> how<11:42:20.700> far<11:42:20.936> the<11:42:21.300> packet<11:42:21.660> is 11:42:21.830 --> 11:42:21.840 align:start position:0% and we can measure how far the packet is 11:42:21.840 --> 11:42:25.130 align:start position:0% and we can measure how far the packet is traveling<11:42:22.380> before<11:42:22.860> it<11:42:23.096> gets<11:42:23.400> back<11:42:23.520> to<11:42:23.820> us 11:42:25.130 --> 11:42:25.140 align:start position:0% traveling before it gets back to us 11:42:25.140 --> 11:42:28.790 align:start position:0% traveling before it gets back to us now<11:42:25.616> I<11:42:25.800> can<11:42:25.980> also<11:42:26.220> use<11:42:26.400> this<11:42:26.700> to<11:42:27.000> test<11:42:27.720> where<11:42:28.320> a 11:42:28.790 --> 11:42:28.800 align:start position:0% now I can also use this to test where a 11:42:28.800 --> 11:42:31.130 align:start position:0% now I can also use this to test where a where<11:42:29.520> a<11:42:29.756> downed<11:42:30.116> router<11:42:30.480> might<11:42:30.596> be<11:42:30.776> or<11:42:30.960> where 11:42:31.130 --> 11:42:31.140 align:start position:0% where a downed router might be or where 11:42:31.140 --> 11:42:32.746 align:start position:0% where a downed router might be or where in<11:42:31.380> the<11:42:31.500> connection<11:42:31.616> a<11:42:31.916> down<11:42:32.096> to<11:42:32.276> router<11:42:32.640> might 11:42:32.746 --> 11:42:32.756 align:start position:0% in the connection a down to router might 11:42:32.756 --> 11:42:35.870 align:start position:0% in the connection a down to router might be<11:42:33.180> so<11:42:33.720> if<11:42:33.960> we<11:42:34.140> go<11:42:34.320> in<11:42:34.436> here<11:42:34.680> for<11:42:34.980> a<11:42:35.096> second<11:42:35.276> and 11:42:35.870 --> 11:42:35.880 align:start position:0% be so if we go in here for a second and 11:42:35.880 --> 11:42:38.690 align:start position:0% be so if we go in here for a second and let's<11:42:36.060> take<11:42:36.300> a<11:42:36.416> look<11:42:36.596> at<11:42:37.096> the<11:42:38.096> command<11:42:38.340> prompt 11:42:38.690 --> 11:42:38.700 align:start position:0% let's take a look at the command prompt 11:42:38.700 --> 11:42:39.950 align:start position:0% let's take a look at the command prompt here 11:42:39.950 --> 11:42:39.960 align:start position:0% here 11:42:39.960 --> 11:42:43.730 align:start position:0% here and<11:42:40.436> let's<11:42:40.616> say<11:42:40.800> I<11:42:41.040> go<11:42:41.340> to<11:42:42.140> trace<11:42:43.140> route 11:42:43.730 --> 11:42:43.740 align:start position:0% and let's say I go to trace route 11:42:43.740 --> 11:42:46.490 align:start position:0% and let's say I go to trace route google.com<11:42:44.720> now<11:42:45.720> what's<11:42:45.900> going<11:42:46.080> to<11:42:46.140> happen<11:42:46.256> is 11:42:46.490 --> 11:42:46.500 align:start position:0% google.com now what's going to happen is 11:42:46.500 --> 11:42:48.890 align:start position:0% google.com now what's going to happen is it's<11:42:46.680> going<11:42:46.916> to<11:42:47.040> start<11:42:47.220> saying<11:42:47.776> all<11:42:48.776> the 11:42:48.890 --> 11:42:48.900 align:start position:0% it's going to start saying all the 11:42:48.900 --> 11:42:50.390 align:start position:0% it's going to start saying all the different<11:42:49.020> hops<11:42:49.500> going<11:42:49.680> to<11:42:49.800> tell<11:42:49.916> me<11:42:50.040> how<11:42:50.340> long 11:42:50.390 --> 11:42:50.400 align:start position:0% different hops going to tell me how long 11:42:50.400 --> 11:42:52.790 align:start position:0% different hops going to tell me how long it<11:42:50.640> takes<11:42:50.820> to<11:42:51.116> get<11:42:51.240> from<11:42:51.660> one<11:42:52.020> place<11:42:52.380> to<11:42:52.616> the 11:42:52.790 --> 11:42:52.800 align:start position:0% it takes to get from one place to the 11:42:52.800 --> 11:42:55.190 align:start position:0% it takes to get from one place to the next<11:42:52.916> and<11:42:53.580> we<11:42:53.700> can<11:42:53.820> see<11:42:54.060> also<11:42:54.480> where<11:42:54.776> it's<11:42:54.960> so 11:42:55.190 --> 11:42:55.200 align:start position:0% next and we can see also where it's so 11:42:55.200 --> 11:42:58.190 align:start position:0% next and we can see also where it's so right<11:42:55.616> here<11:42:55.740> we're<11:42:56.040> still<11:42:56.276> in<11:42:57.240> New<11:42:57.540> York<11:42:57.720> let's 11:42:58.190 --> 11:42:58.200 align:start position:0% right here we're still in New York let's 11:42:58.200 --> 11:43:00.890 align:start position:0% right here we're still in New York let's see<11:42:58.380> NYC<11:42:59.040> I<11:42:59.820> can<11:43:00.000> probably<11:43:00.180> guess<11:43:00.480> this<11:43:00.776> is 11:43:00.890 --> 11:43:00.900 align:start position:0% see NYC I can probably guess this is 11:43:00.900 --> 11:43:03.530 align:start position:0% see NYC I can probably guess this is some<11:43:01.200> place<11:43:01.380> in<11:43:01.616> my<11:43:01.800> ISP<11:43:02.340> and<11:43:02.936> now<11:43:03.116> it<11:43:03.300> looks 11:43:03.530 --> 11:43:03.540 align:start position:0% some place in my ISP and now it looks 11:43:03.540 --> 11:43:05.570 align:start position:0% some place in my ISP and now it looks like<11:43:03.660> it's<11:43:03.776> starting<11:43:04.020> to<11:43:04.200> go<11:43:04.436> out<11:43:04.680> get<11:43:05.220> further 11:43:05.570 --> 11:43:05.580 align:start position:0% like it's starting to go out get further 11:43:05.580 --> 11:43:06.830 align:start position:0% like it's starting to go out get further out<11:43:05.700> and<11:43:05.820> we<11:43:06.000> can<11:43:06.060> see<11:43:06.180> that<11:43:06.360> the<11:43:06.540> amount<11:43:06.720> of 11:43:06.830 --> 11:43:06.840 align:start position:0% out and we can see that the amount of 11:43:06.840 --> 11:43:09.290 align:start position:0% out and we can see that the amount of time<11:43:07.020> it's<11:43:07.256> taking<11:43:07.500> is<11:43:07.800> also<11:43:08.040> more<11:43:08.276> and<11:43:08.400> more 11:43:09.290 --> 11:43:09.300 align:start position:0% time it's taking is also more and more 11:43:09.300 --> 11:43:11.870 align:start position:0% time it's taking is also more and more so<11:43:09.720> between<11:43:09.960> getting<11:43:10.320> between<11:43:10.680> me<11:43:11.460> and<11:43:11.640> and 11:43:11.870 --> 11:43:11.880 align:start position:0% so between getting between me and and 11:43:11.880 --> 11:43:14.266 align:start position:0% so between getting between me and and Google<11:43:12.180> you<11:43:12.900> can<11:43:13.020> see<11:43:13.200> how<11:43:13.680> far<11:43:13.800> we're<11:43:14.040> having 11:43:14.266 --> 11:43:14.276 align:start position:0% Google you can see how far we're having 11:43:14.276 --> 11:43:15.710 align:start position:0% Google you can see how far we're having to<11:43:14.400> go<11:43:14.520> until<11:43:14.756> we<11:43:15.060> finally<11:43:15.240> get<11:43:15.416> to<11:43:15.540> the 11:43:15.710 --> 11:43:15.720 align:start position:0% to go until we finally get to the 11:43:15.720 --> 11:43:19.370 align:start position:0% to go until we finally get to the google.com<11:43:16.276> web<11:43:17.300> uh<11:43:18.300> server<11:43:18.720> which<11:43:19.080> would<11:43:19.256> be 11:43:19.370 --> 11:43:19.380 align:start position:0% google.com web uh server which would be 11:43:19.380 --> 11:43:22.130 align:start position:0% google.com web uh server which would be right<11:43:19.616> here<11:43:19.880> and<11:43:20.880> we<11:43:21.300> know<11:43:21.416> it<11:43:21.540> took<11:43:21.720> about<11:43:21.840> 10 11:43:22.130 --> 11:43:22.140 align:start position:0% right here and we know it took about 10 11:43:22.140 --> 11:43:23.870 align:start position:0% right here and we know it took about 10 hops 11:43:23.870 --> 11:43:23.880 align:start position:0% hops 11:43:23.880 --> 11:43:25.730 align:start position:0% hops now<11:43:24.240> you<11:43:24.360> can<11:43:24.480> see<11:43:24.596> it<11:43:24.720> has<11:43:24.840> a<11:43:25.080> maximum<11:43:25.380> of<11:43:25.560> 30 11:43:25.730 --> 11:43:25.740 align:start position:0% now you can see it has a maximum of 30 11:43:25.740 --> 11:43:28.246 align:start position:0% now you can see it has a maximum of 30 Hops<11:43:26.220> and<11:43:26.400> we<11:43:26.580> can<11:43:26.700> actually<11:43:26.880> set<11:43:27.360> that<11:43:27.660> in<11:43:28.140> the 11:43:28.246 --> 11:43:28.256 align:start position:0% Hops and we can actually set that in the 11:43:28.256 --> 11:43:29.630 align:start position:0% Hops and we can actually set that in the switches<11:43:28.560> if<11:43:28.740> we<11:43:28.860> need<11:43:28.980> to<11:43:29.096> but<11:43:29.400> I<11:43:29.520> wouldn't 11:43:29.630 --> 11:43:29.640 align:start position:0% switches if we need to but I wouldn't 11:43:29.640 --> 11:43:32.570 align:start position:0% switches if we need to but I wouldn't worry<11:43:29.880> about<11:43:30.060> that<11:43:30.300> for<11:43:30.480> the<11:43:30.660> exam 11:43:32.570 --> 11:43:32.580 align:start position:0% worry about that for the exam 11:43:32.580 --> 11:43:34.070 align:start position:0% worry about that for the exam and<11:43:32.936> just<11:43:33.060> to<11:43:33.180> show<11:43:33.360> you<11:43:33.416> what<11:43:33.660> it<11:43:33.776> looks<11:43:33.960> like 11:43:34.070 --> 11:43:34.080 align:start position:0% and just to show you what it looks like 11:43:34.080 --> 11:43:36.766 align:start position:0% and just to show you what it looks like if<11:43:34.256> I'm<11:43:34.436> tracing<11:43:35.096> the<11:43:35.640> Local<11:43:35.756> Host<11:43:36.116> you<11:43:36.596> can 11:43:36.766 --> 11:43:36.776 align:start position:0% if I'm tracing the Local Host you can 11:43:36.776 --> 11:43:38.926 align:start position:0% if I'm tracing the Local Host you can see<11:43:36.900> it<11:43:37.080> only<11:43:37.200> takes<11:43:37.436> one<11:43:37.980> hop<11:43:38.220> obviously 11:43:38.926 --> 11:43:38.936 align:start position:0% see it only takes one hop obviously 11:43:38.936 --> 11:43:41.870 align:start position:0% see it only takes one hop obviously because<11:43:39.720> or<11:43:40.140> not<11:43:40.320> even<11:43:40.436> a<11:43:40.680> hop<11:43:40.860> because<11:43:41.220> it's 11:43:41.870 --> 11:43:41.880 align:start position:0% because or not even a hop because it's 11:43:41.880 --> 11:43:45.530 align:start position:0% because or not even a hop because it's myself<11:43:42.240> I<11:43:42.776> should<11:43:43.020> be<11:43:43.320> no<11:43:43.560> route<11:43:43.800> to<11:43:44.096> get<11:43:44.220> to<11:43:44.340> me 11:43:45.530 --> 11:43:45.540 align:start position:0% myself I should be no route to get to me 11:43:45.540 --> 11:43:47.390 align:start position:0% myself I should be no route to get to me now<11:43:46.020> going<11:43:46.200> away<11:43:46.380> from<11:43:46.560> the<11:43:46.680> command<11:43:46.916> line<11:43:47.096> for 11:43:47.390 --> 11:43:47.400 align:start position:0% now going away from the command line for 11:43:47.400 --> 11:43:48.830 align:start position:0% now going away from the command line for a<11:43:47.520> second<11:43:47.640> I<11:43:47.936> want<11:43:48.000> to<11:43:48.116> talk<11:43:48.240> about<11:43:48.416> what's 11:43:48.830 --> 11:43:48.840 align:start position:0% a second I want to talk about what's 11:43:48.840 --> 11:43:50.990 align:start position:0% a second I want to talk about what's called<11:43:49.020> a<11:43:49.256> protocol<11:43:49.500> analyzer<11:43:50.220> or<11:43:50.640> a<11:43:50.820> network 11:43:50.990 --> 11:43:51.000 align:start position:0% called a protocol analyzer or a network 11:43:51.000 --> 11:43:53.266 align:start position:0% called a protocol analyzer or a network analyzer<11:43:51.720> this<11:43:52.140> is<11:43:52.320> an<11:43:52.436> essential<11:43:52.860> tool<11:43:53.160> when 11:43:53.266 --> 11:43:53.276 align:start position:0% analyzer this is an essential tool when 11:43:53.276 --> 11:43:54.710 align:start position:0% analyzer this is an essential tool when you're<11:43:53.400> running<11:43:53.580> a<11:43:53.756> network<11:43:53.936> it<11:43:54.480> basically 11:43:54.710 --> 11:43:54.720 align:start position:0% you're running a network it basically 11:43:54.720 --> 11:43:57.406 align:start position:0% you're running a network it basically gives<11:43:54.960> you<11:43:55.080> a<11:43:55.680> readable<11:43:56.276> report<11:43:56.700> of<11:43:57.116> virtually 11:43:57.406 --> 11:43:57.416 align:start position:0% gives you a readable report of virtually 11:43:57.416 --> 11:43:58.970 align:start position:0% gives you a readable report of virtually everything<11:43:57.900> that's<11:43:58.200> being<11:43:58.436> sent<11:43:58.740> and 11:43:58.970 --> 11:43:58.980 align:start position:0% everything that's being sent and 11:43:58.980 --> 11:44:01.010 align:start position:0% everything that's being sent and transferred<11:43:59.400> over<11:43:59.520> your<11:43:59.700> network<11:43:59.936> so<11:44:00.660> these 11:44:01.010 --> 11:44:01.020 align:start position:0% transferred over your network so these 11:44:01.020 --> 11:44:03.710 align:start position:0% transferred over your network so these analyzers<11:44:01.740> will<11:44:02.340> capture<11:44:02.756> packets<11:44:03.360> that<11:44:03.596> are 11:44:03.710 --> 11:44:03.720 align:start position:0% analyzers will capture packets that are 11:44:03.720 --> 11:44:05.266 align:start position:0% analyzers will capture packets that are going<11:44:03.900> through<11:44:04.140> the<11:44:04.320> network<11:44:04.500> and<11:44:04.980> put<11:44:05.160> them 11:44:05.266 --> 11:44:05.276 align:start position:0% going through the network and put them 11:44:05.276 --> 11:44:08.150 align:start position:0% going through the network and put them into<11:44:05.520> a<11:44:05.820> buffer<11:44:06.416> zone<11:44:06.720> now<11:44:07.256> this<11:44:07.500> buffer<11:44:07.860> zone 11:44:08.150 --> 11:44:08.160 align:start position:0% into a buffer zone now this buffer zone 11:44:08.160 --> 11:44:09.586 align:start position:0% into a buffer zone now this buffer zone just<11:44:08.340> like<11:44:08.520> the<11:44:08.640> buffer<11:44:08.936> zone<11:44:09.180> we're<11:44:09.300> dealing 11:44:09.586 --> 11:44:09.596 align:start position:0% just like the buffer zone we're dealing 11:44:09.596 --> 11:44:13.550 align:start position:0% just like the buffer zone we're dealing with<11:44:09.720> YouTube<11:44:10.400> or<11:44:11.400> Netflix<11:44:11.936> and<11:44:12.660> buffering<11:44:13.436> a 11:44:13.550 --> 11:44:13.560 align:start position:0% with YouTube or Netflix and buffering a 11:44:13.560 --> 11:44:16.190 align:start position:0% with YouTube or Netflix and buffering a video<11:44:14.000> is<11:44:15.000> going<11:44:15.180> to<11:44:15.416> hold<11:44:15.660> on<11:44:15.840> to<11:44:15.960> these 11:44:16.190 --> 11:44:16.200 align:start position:0% video is going to hold on to these 11:44:16.200 --> 11:44:18.950 align:start position:0% video is going to hold on to these packets<11:44:16.616> and<11:44:17.400> we<11:44:17.640> can<11:44:17.820> either<11:44:18.000> capture<11:44:18.720> all 11:44:18.950 --> 11:44:18.960 align:start position:0% packets and we can either capture all 11:44:18.960 --> 11:44:21.710 align:start position:0% packets and we can either capture all the<11:44:19.080> packets<11:44:19.436> or<11:44:20.276> we<11:44:20.640> can<11:44:20.820> capture<11:44:21.180> specific 11:44:21.710 --> 11:44:21.720 align:start position:0% the packets or we can capture specific 11:44:21.720 --> 11:44:29.086 align:start position:0% the packets or we can capture specific packets<11:44:22.380> based<11:44:23.340> on<11:44:23.400> a<11:44:24.060> filter 11:44:29.086 --> 11:44:29.096 align:start position:0% 11:44:29.096 --> 11:44:31.370 align:start position:0% it<11:44:29.580> can<11:44:29.756> then<11:44:29.880> provide<11:44:30.240> us<11:44:30.416> with<11:44:30.840> an<11:44:31.080> easy 11:44:31.370 --> 11:44:31.380 align:start position:0% it can then provide us with an easy 11:44:31.380 --> 11:44:33.470 align:start position:0% it can then provide us with an easy readable<11:44:31.980> overview<11:44:32.460> of<11:44:32.640> what<11:44:32.936> is<11:44:33.060> contained 11:44:33.470 --> 11:44:33.480 align:start position:0% readable overview of what is contained 11:44:33.480 --> 11:44:35.746 align:start position:0% readable overview of what is contained within<11:44:33.960> each<11:44:34.200> packet<11:44:34.680> this<11:44:35.220> allows<11:44:35.640> the 11:44:35.746 --> 11:44:35.756 align:start position:0% within each packet this allows the 11:44:35.756 --> 11:44:38.210 align:start position:0% within each packet this allows the administrator<11:44:36.240> total<11:44:36.720> control<11:44:36.960> of<11:44:37.680> what<11:44:37.916> does 11:44:38.210 --> 11:44:38.220 align:start position:0% administrator total control of what does 11:44:38.220 --> 11:44:39.950 align:start position:0% administrator total control of what does and<11:44:38.640> doesn't<11:44:38.820> pass<11:44:39.116> through<11:44:39.360> the<11:44:39.540> network<11:44:39.660> and 11:44:39.950 --> 11:44:39.960 align:start position:0% and doesn't pass through the network and 11:44:39.960 --> 11:44:43.246 align:start position:0% and doesn't pass through the network and can<11:44:40.140> also<11:44:40.500> stop<11:44:40.880> potentially<11:44:41.880> dangerous<11:44:42.776> or 11:44:43.246 --> 11:44:43.256 align:start position:0% can also stop potentially dangerous or 11:44:43.256 --> 11:44:45.710 align:start position:0% can also stop potentially dangerous or unwanted<11:44:44.160> pieces<11:44:44.580> of<11:44:44.756> data<11:44:45.060> to<11:44:45.300> pass<11:44:45.480> through 11:44:45.710 --> 11:44:45.720 align:start position:0% unwanted pieces of data to pass through 11:44:45.720 --> 11:44:47.690 align:start position:0% unwanted pieces of data to pass through the<11:44:45.960> network<11:44:46.140> undetected 11:44:47.690 --> 11:44:47.700 align:start position:0% the network undetected 11:44:47.700 --> 11:44:50.030 align:start position:0% the network undetected and<11:44:48.116> so<11:44:48.240> what<11:44:48.480> you<11:44:48.596> can<11:44:48.720> see<11:44:48.900> here<11:44:49.140> is<11:44:49.380> if<11:44:49.560> this 11:44:50.030 --> 11:44:50.040 align:start position:0% and so what you can see here is if this 11:44:50.040 --> 11:44:52.246 align:start position:0% and so what you can see here is if this is<11:44:50.160> our<11:44:50.400> cloud<11:44:50.700> or<11:44:51.060> our<11:44:51.240> Network<11:44:51.416> we're<11:44:52.080> going 11:44:52.246 --> 11:44:52.256 align:start position:0% is our cloud or our Network we're going 11:44:52.256 --> 11:44:53.810 align:start position:0% is our cloud or our Network we're going to<11:44:52.320> call<11:44:52.380> this<11:44:52.500> a<11:44:52.680> TCP<11:44:52.980> Network<11:44:53.400> just<11:44:53.640> because 11:44:53.810 --> 11:44:53.820 align:start position:0% to call this a TCP Network just because 11:44:53.820 --> 11:44:56.926 align:start position:0% to call this a TCP Network just because this<11:44:54.180> is<11:44:54.360> basically<11:44:54.720> our<11:44:55.080> our<11:44:55.436> Wan<11:44:55.916> and<11:44:56.756> here 11:44:56.926 --> 11:44:56.936 align:start position:0% this is basically our our Wan and here 11:44:56.936 --> 11:44:59.450 align:start position:0% this is basically our our Wan and here let's<11:44:57.180> say<11:44:57.360> I<11:44:57.540> have<11:44:57.660> one<11:44:58.080> Lan<11:44:58.436> and<11:44:59.276> another 11:44:59.450 --> 11:44:59.460 align:start position:0% let's say I have one Lan and another 11:44:59.460 --> 11:45:01.730 align:start position:0% let's say I have one Lan and another land<11:44:59.756> I'm<11:45:00.060> going<11:45:00.240> to<11:45:00.416> have<11:45:00.660> a<11:45:01.436> protocol 11:45:01.730 --> 11:45:01.740 align:start position:0% land I'm going to have a protocol 11:45:01.740 --> 11:45:03.950 align:start position:0% land I'm going to have a protocol analyzer<11:45:02.460> a<11:45:02.640> network<11:45:02.820> analyzer<11:45:03.480> in<11:45:03.840> between 11:45:03.950 --> 11:45:03.960 align:start position:0% analyzer a network analyzer in between 11:45:03.960 --> 11:45:05.950 align:start position:0% analyzer a network analyzer in between my<11:45:04.916> network 11:45:05.950 --> 11:45:05.960 align:start position:0% my network 11:45:05.960 --> 11:45:09.406 align:start position:0% my network in<11:45:06.960> my<11:45:07.740> land<11:45:07.980> that<11:45:08.640> way<11:45:08.756> I<11:45:08.936> can<11:45:09.000> analyze 11:45:09.406 --> 11:45:09.416 align:start position:0% in my land that way I can analyze 11:45:09.416 --> 11:45:11.450 align:start position:0% in my land that way I can analyze exactly<11:45:09.776> what's<11:45:10.080> going<11:45:10.380> on<11:45:10.560> some<11:45:11.096> ways<11:45:11.400> this 11:45:11.450 --> 11:45:11.460 align:start position:0% exactly what's going on some ways this 11:45:11.460 --> 11:45:14.990 align:start position:0% exactly what's going on some ways this might<11:45:11.700> also<11:45:11.936> take<11:45:12.060> the<11:45:12.300> form<11:45:12.540> of<11:45:13.436> a<11:45:13.560> firewall 11:45:14.990 --> 11:45:15.000 align:start position:0% might also take the form of a firewall 11:45:15.000 --> 11:45:16.606 align:start position:0% might also take the form of a firewall now<11:45:15.416> this<11:45:15.596> is<11:45:15.720> different<11:45:15.900> from<11:45:16.256> what's<11:45:16.380> called 11:45:16.606 --> 11:45:16.616 align:start position:0% now this is different from what's called 11:45:16.616 --> 11:45:19.190 align:start position:0% now this is different from what's called a<11:45:16.916> port<11:45:17.096> scanner<11:45:17.820> a<11:45:18.300> port<11:45:18.480> scanner<11:45:18.960> does 11:45:19.190 --> 11:45:19.200 align:start position:0% a port scanner a port scanner does 11:45:19.200 --> 11:45:21.530 align:start position:0% a port scanner a port scanner does exactly<11:45:19.680> what<11:45:20.096> it<11:45:20.580> sounds<11:45:20.756> like<11:45:20.936> it<11:45:21.240> basically 11:45:21.530 --> 11:45:21.540 align:start position:0% exactly what it sounds like it basically 11:45:21.540 --> 11:45:25.010 align:start position:0% exactly what it sounds like it basically scans<11:45:22.320> the<11:45:22.616> network<11:45:22.916> for<11:45:23.580> open<11:45:23.756> ports<11:45:24.416> either 11:45:25.010 --> 11:45:25.020 align:start position:0% scans the network for open ports either 11:45:25.020 --> 11:45:29.030 align:start position:0% scans the network for open ports either for<11:45:25.320> malicious<11:45:25.860> or<11:45:26.756> for<11:45:27.180> safety<11:45:27.776> reasons<11:45:28.256> so 11:45:29.030 --> 11:45:29.040 align:start position:0% for malicious or for safety reasons so 11:45:29.040 --> 11:45:31.190 align:start position:0% for malicious or for safety reasons so it's<11:45:29.460> usually<11:45:29.756> used<11:45:30.000> by<11:45:30.240> administrators<11:45:30.900> to 11:45:31.190 --> 11:45:31.200 align:start position:0% it's usually used by administrators to 11:45:31.200 --> 11:45:33.106 align:start position:0% it's usually used by administrators to check<11:45:31.436> the<11:45:31.740> security<11:45:31.980> of<11:45:32.340> their<11:45:32.520> system<11:45:32.700> and 11:45:33.106 --> 11:45:33.116 align:start position:0% check the security of their system and 11:45:33.116 --> 11:45:34.970 align:start position:0% check the security of their system and make<11:45:33.240> sure<11:45:33.360> nothing's<11:45:33.660> left<11:45:33.840> open<11:45:34.020> oppositely 11:45:34.970 --> 11:45:34.980 align:start position:0% make sure nothing's left open oppositely 11:45:34.980 --> 11:45:37.010 align:start position:0% make sure nothing's left open oppositely it<11:45:35.160> can<11:45:35.340> be<11:45:35.460> used<11:45:35.580> by<11:45:35.936> attackers<11:45:36.540> for<11:45:36.900> their 11:45:37.010 --> 11:45:37.020 align:start position:0% it can be used by attackers for their 11:45:37.020 --> 11:45:40.246 align:start position:0% it can be used by attackers for their advantage<11:45:37.560> so<11:45:38.400> uh<11:45:38.820> if<11:45:39.180> a<11:45:39.360> poor<11:45:39.596> if<11:45:39.720> I'm<11:45:39.900> on<11:45:40.080> the 11:45:40.246 --> 11:45:40.256 align:start position:0% advantage so uh if a poor if I'm on the 11:45:40.256 --> 11:45:43.426 align:start position:0% advantage so uh if a poor if I'm on the internal<11:45:40.740> I<11:45:41.340> might<11:45:41.520> use<11:45:41.700> a<11:45:41.936> port<11:45:42.060> scanner<11:45:42.660> to 11:45:43.426 --> 11:45:43.436 align:start position:0% internal I might use a port scanner to 11:45:43.436 --> 11:45:46.010 align:start position:0% internal I might use a port scanner to scan<11:45:43.740> my<11:45:44.400> firewall<11:45:44.936> to<11:45:45.240> see<11:45:45.416> what's<11:45:45.720> going<11:45:45.900> to 11:45:46.010 --> 11:45:46.020 align:start position:0% scan my firewall to see what's going to 11:45:46.020 --> 11:45:48.470 align:start position:0% scan my firewall to see what's going to be<11:45:46.140> allowed<11:45:46.500> through<11:45:46.680> I<11:45:47.400> might<11:45:47.580> also<11:45:47.820> put<11:45:48.116> my 11:45:48.470 --> 11:45:48.480 align:start position:0% be allowed through I might also put my 11:45:48.480 --> 11:45:50.810 align:start position:0% be allowed through I might also put my port<11:45:48.596> scanner<11:45:49.200> over<11:45:49.436> here<11:45:49.740> and<11:45:50.340> have<11:45:50.460> it<11:45:50.640> try 11:45:50.810 --> 11:45:50.820 align:start position:0% port scanner over here and have it try 11:45:50.820 --> 11:45:53.450 align:start position:0% port scanner over here and have it try to<11:45:51.000> come<11:45:51.116> in<11:45:51.436> alternatively<11:45:52.436> a<11:45:52.680> hacker<11:45:53.096> could 11:45:53.450 --> 11:45:53.460 align:start position:0% to come in alternatively a hacker could 11:45:53.460 --> 11:45:55.606 align:start position:0% to come in alternatively a hacker could use<11:45:53.640> a<11:45:53.820> port<11:45:53.880> scanner<11:45:54.416> to<11:45:54.540> go<11:45:54.660> through<11:45:54.900> and 11:45:55.606 --> 11:45:55.616 align:start position:0% use a port scanner to go through and 11:45:55.616 --> 11:45:58.070 align:start position:0% use a port scanner to go through and scan<11:45:55.916> for<11:45:56.160> open<11:45:56.400> ports<11:45:57.000> if<11:45:57.540> there<11:45:57.720> are<11:45:57.840> any 11:45:58.070 --> 11:45:58.080 align:start position:0% scan for open ports if there are any 11:45:58.080 --> 11:46:01.790 align:start position:0% scan for open ports if there are any open<11:45:58.320> ports<11:45:58.980> it<11:45:59.340> can<11:45:59.460> then<11:45:59.640> use<11:46:00.060> those 11:46:01.790 --> 11:46:01.800 align:start position:0% open ports it can then use those 11:46:01.800 --> 11:46:04.426 align:start position:0% open ports it can then use those to<11:46:02.340> try<11:46:02.460> to<11:46:02.580> get<11:46:02.700> into<11:46:02.880> my<11:46:03.180> system<11:46:03.360> so<11:46:04.080> I<11:46:04.320> can 11:46:04.426 --> 11:46:04.436 align:start position:0% to try to get into my system so I can 11:46:04.436 --> 11:46:11.926 align:start position:0% to try to get into my system so I can use<11:46:04.616> it<11:46:04.800> either<11:46:05.096> as<11:46:05.880> a<11:46:06.180> white<11:46:06.416> hat 11:46:11.926 --> 11:46:11.936 align:start position:0% 11:46:11.936 --> 11:46:13.850 align:start position:0% or<11:46:12.416> as<11:46:12.540> a<11:46:12.720> black<11:46:12.840> hat 11:46:13.850 --> 11:46:13.860 align:start position:0% or as a black hat 11:46:13.860 --> 11:46:16.670 align:start position:0% or as a black hat white<11:46:14.400> hat<11:46:14.700> means<11:46:15.060> a<11:46:15.360> good<11:46:15.596> hacker<11:46:16.080> black<11:46:16.436> hat 11:46:16.670 --> 11:46:16.680 align:start position:0% white hat means a good hacker black hat 11:46:16.680 --> 11:46:20.150 align:start position:0% white hat means a good hacker black hat means<11:46:17.040> a<11:46:17.220> bad<11:46:17.700> hacker 11:46:20.150 --> 11:46:20.160 align:start position:0% means a bad hacker 11:46:20.160 --> 11:46:22.606 align:start position:0% means a bad hacker now<11:46:20.460> let's<11:46:20.580> get<11:46:20.820> back<11:46:21.000> into<11:46:21.540> uh<11:46:22.200> our<11:46:22.380> command 11:46:22.606 --> 11:46:22.616 align:start position:0% now let's get back into uh our command 11:46:22.616 --> 11:46:24.470 align:start position:0% now let's get back into uh our command line<11:46:22.740> for<11:46:22.916> just<11:46:23.096> a<11:46:23.220> second<11:46:23.400> here<11:46:23.640> the<11:46:24.300> name 11:46:24.470 --> 11:46:24.480 align:start position:0% line for just a second here the name 11:46:24.480 --> 11:46:26.926 align:start position:0% line for just a second here the name server<11:46:24.900> lookup<11:46:25.256> or<11:46:25.680> NS<11:46:26.276> lookup<11:46:26.640> and<11:46:26.820> again 11:46:26.926 --> 11:46:26.936 align:start position:0% server lookup or NS lookup and again 11:46:26.936 --> 11:46:29.390 align:start position:0% server lookup or NS lookup and again whenever<11:46:27.300> you<11:46:27.480> see<11:46:27.596> NS<11:46:28.080> as<11:46:28.320> in<11:46:28.500> DNS<11:46:28.980> domain 11:46:29.390 --> 11:46:29.400 align:start position:0% whenever you see NS as in DNS domain 11:46:29.400 --> 11:46:31.070 align:start position:0% whenever you see NS as in DNS domain name<11:46:29.580> system<11:46:29.880> you<11:46:30.480> can<11:46:30.540> think<11:46:30.660> that<11:46:30.840> has 11:46:31.070 --> 11:46:31.080 align:start position:0% name system you can think that has 11:46:31.080 --> 11:46:32.690 align:start position:0% name system you can think that has something<11:46:31.200> to<11:46:31.320> do<11:46:31.380> with<11:46:31.560> name<11:46:31.800> server<11:46:32.276> or<11:46:32.400> name 11:46:32.690 --> 11:46:32.700 align:start position:0% something to do with name server or name 11:46:32.700 --> 11:46:37.210 align:start position:0% something to do with name server or name system<11:46:33.140> it's<11:46:34.140> used<11:46:34.380> to<11:46:34.916> basically<11:46:35.480> find<11:46:36.480> out 11:46:37.210 --> 11:46:37.220 align:start position:0% system it's used to basically find out 11:46:37.220 --> 11:46:39.586 align:start position:0% system it's used to basically find out uh<11:46:38.220> what<11:46:38.700> the<11:46:38.880> server<11:46:39.180> and<11:46:39.360> address 11:46:39.586 --> 11:46:39.596 align:start position:0% uh what the server and address 11:46:39.596 --> 11:46:41.266 align:start position:0% uh what the server and address information<11:46:39.960> is<11:46:40.436> for<11:46:40.680> a<11:46:40.860> domain<11:46:41.096> that's 11:46:41.266 --> 11:46:41.276 align:start position:0% information is for a domain that's 11:46:41.276 --> 11:46:45.830 align:start position:0% information is for a domain that's queried<11:46:41.820> it's<11:46:42.480> mostly<11:46:42.960> used<11:46:43.756> to<11:46:44.840> troubleshoot 11:46:45.830 --> 11:46:45.840 align:start position:0% queried it's mostly used to troubleshoot 11:46:45.840 --> 11:46:48.170 align:start position:0% queried it's mostly used to troubleshoot domain<11:46:46.256> name<11:46:46.436> service<11:46:46.740> related<11:46:47.220> items<11:46:47.700> and 11:46:48.170 --> 11:46:48.180 align:start position:0% domain name service related items and 11:46:48.180 --> 11:46:49.426 align:start position:0% domain name service related items and you<11:46:48.240> can<11:46:48.360> also<11:46:48.540> get<11:46:48.660> information<11:46:48.776> about<11:46:49.200> a 11:46:49.426 --> 11:46:49.436 align:start position:0% you can also get information about a 11:46:49.436 --> 11:46:51.890 align:start position:0% you can also get information about a systems<11:46:49.860> configuration<11:46:50.520> now<11:46:51.240> dig<11:46:51.540> actually 11:46:51.890 --> 11:46:51.900 align:start position:0% systems configuration now dig actually 11:46:51.900 --> 11:46:54.170 align:start position:0% systems configuration now dig actually does<11:46:52.140> the<11:46:52.436> same<11:46:52.616> thing<11:46:53.040> but<11:46:53.580> it's<11:46:53.820> a<11:46:54.060> little 11:46:54.170 --> 11:46:54.180 align:start position:0% does the same thing but it's a little 11:46:54.180 --> 11:46:56.266 align:start position:0% does the same thing but it's a little more<11:46:54.480> detailed<11:46:55.140> and<11:46:55.436> it<11:46:55.560> only<11:46:55.680> works<11:46:56.040> with 11:46:56.266 --> 11:46:56.276 align:start position:0% more detailed and it only works with 11:46:56.276 --> 11:46:58.850 align:start position:0% more detailed and it only works with Unix<11:46:56.700> or<11:46:56.936> Linux<11:46:57.416> systems<11:46:58.080> so<11:46:58.560> here's<11:46:58.800> an 11:46:58.850 --> 11:46:58.860 align:start position:0% Unix or Linux systems so here's an 11:46:58.860 --> 11:47:00.830 align:start position:0% Unix or Linux systems so here's an example<11:46:59.160> of<11:46:59.340> what<11:46:59.580> the<11:46:59.756> NS<11:47:00.060> lookup<11:47:00.416> would<11:47:00.720> look 11:47:00.830 --> 11:47:00.840 align:start position:0% example of what the NS lookup would look 11:47:00.840 --> 11:47:03.106 align:start position:0% example of what the NS lookup would look like<11:47:01.020> and<11:47:01.740> you<11:47:01.800> can<11:47:01.916> see<11:47:02.040> if<11:47:02.276> NS<11:47:02.520> look<11:47:02.700> up<11:47:02.880> here 11:47:03.106 --> 11:47:03.116 align:start position:0% like and you can see if NS look up here 11:47:03.116 --> 11:47:05.746 align:start position:0% like and you can see if NS look up here and<11:47:03.960> then<11:47:04.140> what<11:47:04.500> did<11:47:04.616> we<11:47:04.800> do<11:47:04.916> well<11:47:05.096> we<11:47:05.340> asked<11:47:05.640> it 11:47:05.746 --> 11:47:05.756 align:start position:0% and then what did we do well we asked it 11:47:05.756 --> 11:47:10.246 align:start position:0% and then what did we do well we asked it for<11:47:06.500> Wikipedia's<11:47:07.500> name<11:47:08.160> and<11:47:08.700> up<11:47:08.880> it<11:47:09.060> pops<11:47:09.480> the 11:47:10.246 --> 11:47:10.256 align:start position:0% for Wikipedia's name and up it pops the 11:47:10.256 --> 11:47:12.650 align:start position:0% for Wikipedia's name and up it pops the IP<11:47:10.560> address<11:47:10.800> and<11:47:11.640> it<11:47:11.820> also<11:47:12.060> tells<11:47:12.300> us<11:47:12.360> when 11:47:12.650 --> 11:47:12.660 align:start position:0% IP address and it also tells us when 11:47:12.660 --> 11:47:14.086 align:start position:0% IP address and it also tells us when whether<11:47:13.020> it's<11:47:13.200> authoritative<11:47:13.800> or 11:47:14.086 --> 11:47:14.096 align:start position:0% whether it's authoritative or 11:47:14.096 --> 11:47:16.246 align:start position:0% whether it's authoritative or non-authoritative<11:47:14.900> authoritative<11:47:15.900> would<11:47:16.140> be 11:47:16.246 --> 11:47:16.256 align:start position:0% non-authoritative authoritative would be 11:47:16.256 --> 11:47:18.350 align:start position:0% non-authoritative authoritative would be a<11:47:16.380> DNS<11:47:16.740> server<11:47:17.160> that's<11:47:17.640> somewhere<11:47:17.936> out<11:47:18.116> on<11:47:18.240> the 11:47:18.350 --> 11:47:18.360 align:start position:0% a DNS server that's somewhere out on the 11:47:18.360 --> 11:47:20.690 align:start position:0% a DNS server that's somewhere out on the internet<11:47:18.480> that<11:47:19.256> is<11:47:19.500> definitely<11:47:19.980> has<11:47:20.340> all<11:47:20.520> the 11:47:20.690 --> 11:47:20.700 align:start position:0% internet that is definitely has all the 11:47:20.700 --> 11:47:22.550 align:start position:0% internet that is definitely has all the information<11:47:21.020> non-authoritative<11:47:22.020> means<11:47:22.436> it 11:47:22.550 --> 11:47:22.560 align:start position:0% information non-authoritative means it 11:47:22.560 --> 11:47:24.586 align:start position:0% information non-authoritative means it might<11:47:22.680> be<11:47:22.800> a<11:47:22.980> local<11:47:23.096> one<11:47:23.460> so<11:47:24.116> if<11:47:24.240> we<11:47:24.360> were<11:47:24.480> to 11:47:24.586 --> 11:47:24.596 align:start position:0% might be a local one so if we were to 11:47:24.596 --> 11:47:27.890 align:start position:0% might be a local one so if we were to look<11:47:24.720> at<11:47:24.900> this<11:47:25.020> for<11:47:25.256> a<11:47:25.436> second<11:47:25.560> for<11:47:25.860> ourselves 11:47:27.890 --> 11:47:27.900 align:start position:0% look at this for a second for ourselves 11:47:27.900 --> 11:47:30.230 align:start position:0% look at this for a second for ourselves let's<11:47:28.380> do<11:47:28.500> NS<11:47:28.916> lookup<11:47:29.276> to<11:47:29.520> go<11:47:29.700> into<11:47:30.000> the 11:47:30.230 --> 11:47:30.240 align:start position:0% let's do NS lookup to go into the 11:47:30.240 --> 11:47:31.906 align:start position:0% let's do NS lookup to go into the utility 11:47:31.906 --> 11:47:31.916 align:start position:0% utility 11:47:31.916 --> 11:47:35.330 align:start position:0% utility and<11:47:32.520> now<11:47:32.756> we<11:47:33.360> could<11:47:33.480> for<11:47:33.840> instance<11:47:34.140> look<11:47:34.616> up<11:47:34.860> uh 11:47:35.330 --> 11:47:35.340 align:start position:0% and now we could for instance look up uh 11:47:35.340 --> 11:47:38.030 align:start position:0% and now we could for instance look up uh google.com 11:47:38.030 --> 11:47:38.040 align:start position:0% 11:47:38.040 --> 11:47:40.730 align:start position:0% and<11:47:38.520> it'll<11:47:38.640> tell<11:47:38.880> us<11:47:39.060> all<11:47:39.660> the<11:47:39.840> different<11:47:40.020> IP 11:47:40.730 --> 11:47:40.740 align:start position:0% and it'll tell us all the different IP 11:47:40.740 --> 11:47:41.870 align:start position:0% and it'll tell us all the different IP addresses<11:47:41.220> that<11:47:41.400> are<11:47:41.520> available<11:47:41.580> for 11:47:41.870 --> 11:47:41.880 align:start position:0% addresses that are available for 11:47:41.880 --> 11:47:43.070 align:start position:0% addresses that are available for google.com 11:47:43.070 --> 11:47:43.080 align:start position:0% google.com 11:47:43.080 --> 11:47:44.570 align:start position:0% google.com yahoo.com 11:47:44.570 --> 11:47:44.580 align:start position:0% yahoo.com 11:47:44.580 --> 11:47:47.210 align:start position:0% yahoo.com maybe<11:47:45.300> even<11:47:45.540> microsoft.com 11:47:47.210 --> 11:47:47.220 align:start position:0% maybe even microsoft.com 11:47:47.220 --> 11:47:48.830 align:start position:0% maybe even microsoft.com CNN.com 11:47:48.830 --> 11:47:48.840 align:start position:0% CNN.com 11:47:48.840 --> 11:47:51.230 align:start position:0% CNN.com etc<11:47:49.320> etc<11:47:49.500> so<11:47:50.040> you<11:47:50.160> can<11:47:50.276> see<11:47:50.520> all<11:47:51.060> these 11:47:51.230 --> 11:47:51.240 align:start position:0% etc etc so you can see all these 11:47:51.240 --> 11:47:52.246 align:start position:0% etc etc so you can see all these different<11:47:51.360> ones<11:47:51.660> that<11:47:51.776> are<11:47:51.900> coming<11:47:52.020> through 11:47:52.246 --> 11:47:52.256 align:start position:0% different ones that are coming through 11:47:52.256 --> 11:47:54.710 align:start position:0% different ones that are coming through now<11:47:52.860> notice<11:47:53.160> that<11:47:53.340> CNN.com<11:47:54.000> actually 11:47:54.710 --> 11:47:54.720 align:start position:0% now notice that CNN.com actually 11:47:54.720 --> 11:47:56.266 align:start position:0% now notice that CNN.com actually wouldn't<11:47:55.020> let<11:47:55.256> us<11:47:55.436> out<11:47:55.560> and<11:47:55.860> neither<11:47:56.096> would 11:47:56.266 --> 11:47:56.276 align:start position:0% wouldn't let us out and neither would 11:47:56.276 --> 11:47:58.906 align:start position:0% wouldn't let us out and neither would microsoft.com<11:47:57.540> that's<11:47:57.960> because<11:47:58.200> they're 11:47:58.906 --> 11:47:58.916 align:start position:0% microsoft.com that's because they're 11:47:58.916 --> 11:48:01.606 align:start position:0% microsoft.com that's because they're actually<11:47:59.160> blocking<11:47:59.936> the<11:48:00.720> they're<11:48:01.020> filtering 11:48:01.606 --> 11:48:01.616 align:start position:0% actually blocking the they're filtering 11:48:01.616 --> 11:48:05.810 align:start position:0% actually blocking the they're filtering out<11:48:01.800> the<11:48:02.580> type<11:48:02.880> of<11:48:03.320> uh<11:48:04.320> ports<11:48:05.160> or<11:48:05.340> protocols 11:48:05.810 --> 11:48:05.820 align:start position:0% out the type of uh ports or protocols 11:48:05.820 --> 11:48:07.606 align:start position:0% out the type of uh ports or protocols that<11:48:05.936> are<11:48:06.060> going<11:48:06.116> to<11:48:06.240> be<11:48:06.416> allowing<11:48:06.960> uh<11:48:07.436> that 11:48:07.606 --> 11:48:07.616 align:start position:0% that are going to be allowing uh that 11:48:07.616 --> 11:48:10.130 align:start position:0% that are going to be allowing uh that are<11:48:07.916> going<11:48:07.980> to<11:48:08.096> allow<11:48:08.460> like<11:48:08.640> the<11:48:08.820> icmp<11:48:09.416> Ping<11:48:09.776> so 11:48:10.130 --> 11:48:10.140 align:start position:0% are going to allow like the icmp Ping so 11:48:10.140 --> 11:48:11.330 align:start position:0% are going to allow like the icmp Ping so if<11:48:10.256> we<11:48:10.380> were<11:48:10.436> to<11:48:10.560> go<11:48:10.680> out<11:48:10.740> of<11:48:10.860> this<11:48:10.980> for<11:48:11.220> a 11:48:11.330 --> 11:48:11.340 align:start position:0% if we were to go out of this for a 11:48:11.340 --> 11:48:12.890 align:start position:0% if we were to go out of this for a second 11:48:12.890 --> 11:48:12.900 align:start position:0% second 11:48:12.900 --> 11:48:15.650 align:start position:0% second and<11:48:13.256> by<11:48:13.380> the<11:48:13.436> way<11:48:13.500> you<11:48:13.680> do<11:48:13.800> that<11:48:13.916> as<11:48:14.096> Ctrl<11:48:14.580> C<11:48:14.820> and 11:48:15.650 --> 11:48:15.660 align:start position:0% and by the way you do that as Ctrl C and 11:48:15.660 --> 11:48:18.406 align:start position:0% and by the way you do that as Ctrl C and if<11:48:15.776> I<11:48:15.960> tried<11:48:16.200> pinging<11:48:16.936> microsoft.com<11:48:17.936> you'll 11:48:18.406 --> 11:48:18.416 align:start position:0% if I tried pinging microsoft.com you'll 11:48:18.416 --> 11:48:19.606 align:start position:0% if I tried pinging microsoft.com you'll notice 11:48:19.606 --> 11:48:19.616 align:start position:0% notice 11:48:19.616 --> 11:48:22.246 align:start position:0% notice that<11:48:20.220> it<11:48:20.400> actually<11:48:20.520> doesn't<11:48:20.820> come<11:48:21.060> back<11:48:21.360> and 11:48:22.246 --> 11:48:22.256 align:start position:0% that it actually doesn't come back and 11:48:22.256 --> 11:48:24.290 align:start position:0% that it actually doesn't come back and that's<11:48:22.436> because<11:48:22.740> they're<11:48:23.580> actually<11:48:23.880> shutting 11:48:24.290 --> 11:48:24.300 align:start position:0% that's because they're actually shutting 11:48:24.300 --> 11:48:30.230 align:start position:0% that's because they're actually shutting out<11:48:24.416> icmp<11:48:25.140> packets<11:48:25.560> from<11:48:25.800> going<11:48:26.040> in 11:48:30.230 --> 11:48:30.240 align:start position:0% 11:48:30.240 --> 11:48:32.990 align:start position:0% now<11:48:30.660> another<11:48:30.900> one<11:48:31.200> related<11:48:31.860> somewhat<11:48:32.580> is 11:48:32.990 --> 11:48:33.000 align:start position:0% now another one related somewhat is 11:48:33.000 --> 11:48:35.030 align:start position:0% now another one related somewhat is what's<11:48:33.180> called<11:48:33.416> ARP<11:48:33.960> or<11:48:34.256> address<11:48:34.436> resolution 11:48:35.030 --> 11:48:35.040 align:start position:0% what's called ARP or address resolution 11:48:35.040 --> 11:48:36.890 align:start position:0% what's called ARP or address resolution protocol<11:48:35.580> we<11:48:35.936> actually<11:48:36.060> talked<11:48:36.480> about<11:48:36.596> this 11:48:36.890 --> 11:48:36.900 align:start position:0% protocol we actually talked about this 11:48:36.900 --> 11:48:39.406 align:start position:0% protocol we actually talked about this previously<11:48:37.500> and<11:48:38.040> it's<11:48:38.220> you<11:48:38.520> really<11:48:38.756> use<11:48:39.116> to 11:48:39.406 --> 11:48:39.416 align:start position:0% previously and it's you really use to 11:48:39.416 --> 11:48:41.926 align:start position:0% previously and it's you really use to find<11:48:39.596> the<11:48:39.900> media<11:48:40.256> access<11:48:40.436> control<11:48:41.040> or<11:48:41.640> Mac 11:48:41.926 --> 11:48:41.936 align:start position:0% find the media access control or Mac 11:48:41.936 --> 11:48:45.470 align:start position:0% find the media access control or Mac address<11:48:42.240> or<11:48:43.140> the<11:48:43.436> physical<11:48:44.040> address<11:48:44.640> for<11:48:45.360> an 11:48:45.470 --> 11:48:45.480 align:start position:0% address or the physical address for an 11:48:45.480 --> 11:48:48.586 align:start position:0% address or the physical address for an IP<11:48:45.776> address<11:48:46.020> or<11:48:46.800> vice<11:48:47.160> versa<11:48:47.700> remember<11:48:48.240> this 11:48:48.586 --> 11:48:48.596 align:start position:0% IP address or vice versa remember this 11:48:48.596 --> 11:48:51.290 align:start position:0% IP address or vice versa remember this is<11:48:48.776> the<11:48:49.080> physical 11:48:51.290 --> 11:48:51.300 align:start position:0% is the physical 11:48:51.300 --> 11:48:54.290 align:start position:0% is the physical address<11:48:51.960> it's<11:48:52.860> hardwired<11:48:53.580> onto<11:48:54.000> the<11:48:54.116> device 11:48:54.290 --> 11:48:54.300 align:start position:0% address it's hardwired onto the device 11:48:54.300 --> 11:48:56.690 align:start position:0% address it's hardwired onto the device the<11:48:55.256> MAC<11:48:55.436> address<11:48:55.680> is<11:48:55.980> the<11:48:56.160> system's<11:48:56.520> physical 11:48:56.690 --> 11:48:56.700 align:start position:0% the MAC address is the system's physical 11:48:56.700 --> 11:48:58.970 align:start position:0% the MAC address is the system's physical address<11:48:57.116> and<11:48:57.840> the<11:48:57.960> IP<11:48:58.256> address<11:48:58.436> is<11:48:58.740> the<11:48:58.860> one 11:48:58.970 --> 11:48:58.980 align:start position:0% address and the IP address is the one 11:48:58.980 --> 11:49:01.246 align:start position:0% address and the IP address is the one again<11:48:59.276> assigned<11:48:59.820> by<11:48:59.936> a<11:49:00.116> server<11:49:00.480> or<11:49:00.840> manually 11:49:01.246 --> 11:49:01.256 align:start position:0% again assigned by a server or manually 11:49:01.256 --> 11:49:03.830 align:start position:0% again assigned by a server or manually assigned<11:49:01.916> in<11:49:02.460> a<11:49:02.640> way<11:49:02.756> this<11:49:03.116> would<11:49:03.300> be<11:49:03.480> like 11:49:03.830 --> 11:49:03.840 align:start position:0% assigned in a way this would be like 11:49:03.840 --> 11:49:05.510 align:start position:0% assigned in a way this would be like your<11:49:04.320> phone<11:49:04.500> number 11:49:05.510 --> 11:49:05.520 align:start position:0% your phone number 11:49:05.520 --> 11:49:07.070 align:start position:0% your phone number and<11:49:05.936> this<11:49:06.116> would<11:49:06.360> be<11:49:06.540> like<11:49:06.720> your<11:49:06.900> social 11:49:07.070 --> 11:49:07.080 align:start position:0% and this would be like your social 11:49:07.080 --> 11:49:08.926 align:start position:0% and this would be like your social security<11:49:07.380> number<11:49:07.740> which<11:49:08.040> is<11:49:08.160> given<11:49:08.460> to<11:49:08.520> you<11:49:08.700> by 11:49:08.926 --> 11:49:08.936 align:start position:0% security number which is given to you by 11:49:08.936 --> 11:49:10.246 align:start position:0% security number which is given to you by the<11:49:09.360> government 11:49:10.246 --> 11:49:10.256 align:start position:0% the government 11:49:10.256 --> 11:49:12.106 align:start position:0% the government the<11:49:10.680> way<11:49:10.740> it<11:49:10.860> does<11:49:11.040> this<11:49:11.276> is<11:49:11.756> we're<11:49:11.936> actually 11:49:12.106 --> 11:49:12.116 align:start position:0% the way it does this is we're actually 11:49:12.116 --> 11:49:14.150 align:start position:0% the way it does this is we're actually going<11:49:12.360> to<11:49:12.540> send<11:49:12.720> out<11:49:12.900> Discovery<11:49:13.616> packets<11:49:13.980> in 11:49:14.150 --> 11:49:14.160 align:start position:0% going to send out Discovery packets in 11:49:14.160 --> 11:49:15.890 align:start position:0% going to send out Discovery packets in order<11:49:14.276> to<11:49:14.400> find<11:49:14.580> out<11:49:14.756> the<11:49:14.936> MAC<11:49:15.060> address<11:49:15.300> of<11:49:15.720> a 11:49:15.890 --> 11:49:15.900 align:start position:0% order to find out the MAC address of a 11:49:15.900 --> 11:49:17.690 align:start position:0% order to find out the MAC address of a destination<11:49:16.320> system<11:49:16.740> and<11:49:17.340> once<11:49:17.580> it 11:49:17.690 --> 11:49:17.700 align:start position:0% destination system and once it 11:49:17.700 --> 11:49:19.490 align:start position:0% destination system and once it establishes<11:49:18.180> that<11:49:18.416> it<11:49:18.900> sends<11:49:19.200> that<11:49:19.256> Mac 11:49:19.490 --> 11:49:19.500 align:start position:0% establishes that it sends that Mac 11:49:19.500 --> 11:49:21.530 align:start position:0% establishes that it sends that Mac address<11:49:19.740> to<11:49:20.276> the<11:49:20.756> sending<11:49:21.116> or<11:49:21.240> receiving 11:49:21.530 --> 11:49:21.540 align:start position:0% address to the sending or receiving 11:49:21.540 --> 11:49:23.630 align:start position:0% address to the sending or receiving computer<11:49:21.900> now<11:49:22.616> the<11:49:22.740> two<11:49:22.860> computers<11:49:23.220> can<11:49:23.460> now 11:49:23.630 --> 11:49:23.640 align:start position:0% computer now the two computers can now 11:49:23.640 --> 11:49:26.030 align:start position:0% computer now the two computers can now communicate<11:49:24.300> using<11:49:25.020> IP<11:49:25.380> addresses<11:49:25.800> because 11:49:26.030 --> 11:49:26.040 align:start position:0% communicate using IP addresses because 11:49:26.040 --> 11:49:28.790 align:start position:0% communicate using IP addresses because they<11:49:26.400> can<11:49:26.580> both<11:49:26.820> actually<11:49:27.240> resolve<11:49:28.020> to<11:49:28.320> IP 11:49:28.790 --> 11:49:28.800 align:start position:0% they can both actually resolve to IP 11:49:28.800 --> 11:49:31.370 align:start position:0% they can both actually resolve to IP addresses<11:49:29.340> so<11:49:30.180> basically<11:49:30.540> I<11:49:30.840> want<11:49:31.020> to<11:49:31.140> send 11:49:31.370 --> 11:49:31.380 align:start position:0% addresses so basically I want to send 11:49:31.380 --> 11:49:32.390 align:start position:0% addresses so basically I want to send something 11:49:32.390 --> 11:49:32.400 align:start position:0% something 11:49:32.400 --> 11:49:33.830 align:start position:0% something right<11:49:32.880> so<11:49:33.116> what<11:49:33.240> I'm<11:49:33.300> going<11:49:33.416> to<11:49:33.416> do<11:49:33.596> is<11:49:33.660> I'm 11:49:33.830 --> 11:49:33.840 align:start position:0% right so what I'm going to do is I'm 11:49:33.840 --> 11:49:36.586 align:start position:0% right so what I'm going to do is I'm going<11:49:33.960> to<11:49:33.960> go<11:49:34.200> out<11:49:34.380> hit<11:49:34.860> a<11:49:35.096> router<11:49:35.460> the<11:49:36.240> router 11:49:36.586 --> 11:49:36.596 align:start position:0% going to go out hit a router the router 11:49:36.596 --> 11:49:43.490 align:start position:0% going to go out hit a router the router uses<11:49:36.900> arp<11:49:37.860> in<11:49:38.340> order<11:49:38.520> to<11:49:39.060> get<11:49:39.960> the<11:49:40.380> MAC<11:49:40.560> address 11:49:43.490 --> 11:49:43.500 align:start position:0% 11:49:43.500 --> 11:49:46.010 align:start position:0% to<11:49:43.860> the<11:49:43.980> sending<11:49:44.340> computer<11:49:44.520> and<11:49:45.240> now<11:49:45.480> we<11:49:45.840> can 11:49:46.010 --> 11:49:46.020 align:start position:0% to the sending computer and now we can 11:49:46.020 --> 11:49:48.290 align:start position:0% to the sending computer and now we can talk<11:49:46.320> directly 11:49:48.290 --> 11:49:48.300 align:start position:0% talk directly 11:49:48.300 --> 11:49:51.230 align:start position:0% talk directly because<11:49:48.596> now<11:49:49.080> I<11:49:49.436> know<11:49:49.680> what<11:49:50.580> your<11:49:50.820> Mac<11:49:51.000> address 11:49:51.230 --> 11:49:51.240 align:start position:0% because now I know what your Mac address 11:49:51.240 --> 11:49:56.266 align:start position:0% because now I know what your Mac address and<11:49:51.900> IP<11:49:52.256> address<11:49:52.436> equal 11:49:56.266 --> 11:49:56.276 align:start position:0% 11:49:56.276 --> 11:50:00.710 align:start position:0% finally 11:50:00.710 --> 11:50:00.720 align:start position:0% 11:50:00.720 --> 11:50:03.530 align:start position:0% the<11:50:01.320> route<11:50:01.500> command<11:50:01.980> is<11:50:02.160> extremely<11:50:02.700> handy<11:50:03.180> and 11:50:03.530 --> 11:50:03.540 align:start position:0% the route command is extremely handy and 11:50:03.540 --> 11:50:04.810 align:start position:0% the route command is extremely handy and can<11:50:03.720> be<11:50:03.900> used 11:50:04.810 --> 11:50:04.820 align:start position:0% can be used 11:50:04.820 --> 11:50:07.730 align:start position:0% can be used fairly<11:50:05.820> often<11:50:06.116> it<11:50:06.300> basically<11:50:06.660> just<11:50:06.960> shows<11:50:07.616> you 11:50:07.730 --> 11:50:07.740 align:start position:0% fairly often it basically just shows you 11:50:07.740 --> 11:50:10.246 align:start position:0% fairly often it basically just shows you the<11:50:08.040> routing<11:50:08.460> table<11:50:08.840> which<11:50:09.840> is<11:50:09.960> going<11:50:10.080> to<11:50:10.140> give 11:50:10.246 --> 11:50:10.256 align:start position:0% the routing table which is going to give 11:50:10.256 --> 11:50:12.290 align:start position:0% the routing table which is going to give you<11:50:10.320> a<11:50:10.560> list<11:50:10.740> of<11:50:11.160> all<11:50:11.340> the<11:50:11.460> routes<11:50:11.820> network 11:50:12.290 --> 11:50:12.300 align:start position:0% you a list of all the routes network 11:50:12.300 --> 11:50:14.570 align:start position:0% you a list of all the routes network connections<11:50:13.020> and<11:50:13.200> so<11:50:13.380> on<11:50:13.560> that<11:50:14.040> the<11:50:14.160> user<11:50:14.460> has 11:50:14.570 --> 11:50:14.580 align:start position:0% connections and so on that the user has 11:50:14.580 --> 11:50:17.150 align:start position:0% connections and so on that the user has the<11:50:14.756> option<11:50:15.116> to<11:50:15.416> then<11:50:15.596> edit<11:50:16.256> now<11:50:16.916> the<11:50:17.040> reason 11:50:17.150 --> 11:50:17.160 align:start position:0% the option to then edit now the reason 11:50:17.160 --> 11:50:19.246 align:start position:0% the option to then edit now the reason you<11:50:17.400> might<11:50:17.520> want<11:50:17.640> to<11:50:17.820> edit<11:50:18.060> it<11:50:18.240> is<11:50:18.720> if<11:50:19.020> for 11:50:19.246 --> 11:50:19.256 align:start position:0% you might want to edit it is if for 11:50:19.256 --> 11:50:22.010 align:start position:0% you might want to edit it is if for instance<11:50:19.500> in<11:50:19.980> your<11:50:20.220> router<11:50:20.880> you<11:50:21.596> want<11:50:21.720> to<11:50:21.840> tell 11:50:22.010 --> 11:50:22.020 align:start position:0% instance in your router you want to tell 11:50:22.020 --> 11:50:24.650 align:start position:0% instance in your router you want to tell it<11:50:22.200> to<11:50:22.380> use<11:50:22.560> one<11:50:22.916> route<11:50:23.160> instead<11:50:23.640> of<11:50:23.756> another 11:50:24.650 --> 11:50:24.660 align:start position:0% it to use one route instead of another 11:50:24.660 --> 11:50:27.710 align:start position:0% it to use one route instead of another so<11:50:25.200> an<11:50:25.380> example<11:50:25.740> here 11:50:27.710 --> 11:50:27.720 align:start position:0% so an example here 11:50:27.720 --> 11:50:31.550 align:start position:0% so an example here shows<11:50:28.436> us<11:50:28.616> The<11:50:29.220> Gateway 11:50:31.550 --> 11:50:31.560 align:start position:0% shows us The Gateway 11:50:31.560 --> 11:50:35.266 align:start position:0% shows us The Gateway the<11:50:32.096> mask 11:50:35.266 --> 11:50:35.276 align:start position:0% 11:50:35.276 --> 11:50:38.086 align:start position:0% so<11:50:35.640> draw<11:50:36.060> these<11:50:36.300> really<11:50:36.416> quickly 11:50:38.086 --> 11:50:38.096 align:start position:0% so draw these really quickly 11:50:38.096 --> 11:50:40.606 align:start position:0% so draw these really quickly and<11:50:38.460> the<11:50:38.640> interface<11:50:39.116> and<11:50:39.596> the<11:50:40.140> sorry<11:50:40.320> the 11:50:40.606 --> 11:50:40.616 align:start position:0% and the interface and the sorry the 11:50:40.616 --> 11:50:42.290 align:start position:0% and the interface and the sorry the metric 11:50:42.290 --> 11:50:42.300 align:start position:0% metric 11:50:42.300 --> 11:50:44.030 align:start position:0% metric as<11:50:42.776> well<11:50:42.900> as<11:50:43.080> the<11:50:43.256> interface<11:50:43.560> and<11:50:43.740> these<11:50:43.916> are 11:50:44.030 --> 11:50:44.040 align:start position:0% as well as the interface and these are 11:50:44.040 --> 11:50:46.310 align:start position:0% as well as the interface and these are all<11:50:44.096> numbers<11:50:44.340> so<11:50:44.756> these<11:50:45.000> might<11:50:45.240> not<11:50:45.480> mean<11:50:46.080> a 11:50:46.310 --> 11:50:46.320 align:start position:0% all numbers so these might not mean a 11:50:46.320 --> 11:50:47.990 align:start position:0% all numbers so these might not mean a lot<11:50:46.436> to<11:50:46.616> you<11:50:46.800> but<11:50:46.980> if<11:50:47.096> you<11:50:47.276> had<11:50:47.400> a<11:50:47.640> guide<11:50:47.756> and 11:50:47.990 --> 11:50:48.000 align:start position:0% lot to you but if you had a guide and 11:50:48.000 --> 11:50:49.190 align:start position:0% lot to you but if you had a guide and you<11:50:48.116> knew<11:50:48.300> where<11:50:48.416> they<11:50:48.540> were<11:50:48.660> going<11:50:48.776> if<11:50:49.080> you 11:50:49.190 --> 11:50:49.200 align:start position:0% you knew where they were going if you 11:50:49.200 --> 11:50:50.690 align:start position:0% you knew where they were going if you knew<11:50:49.436> what<11:50:49.616> your<11:50:49.800> interface<11:50:50.160> was<11:50:50.400> for 11:50:50.690 --> 11:50:50.700 align:start position:0% knew what your interface was for 11:50:50.700 --> 11:50:52.246 align:start position:0% knew what your interface was for instance<11:50:50.880> is<11:50:51.060> it<11:50:51.240> a<11:50:51.416> wireless<11:50:51.540> internet<11:50:51.840> base 11:50:52.246 --> 11:50:52.256 align:start position:0% instance is it a wireless internet base 11:50:52.256 --> 11:50:55.130 align:start position:0% instance is it a wireless internet base or<11:50:52.916> was<11:50:53.096> it<11:50:53.340> a<11:50:53.640> your<11:50:54.060> wired<11:50:54.480> interface<11:50:54.840> that 11:50:55.130 --> 11:50:55.140 align:start position:0% or was it a your wired interface that 11:50:55.140 --> 11:50:57.650 align:start position:0% or was it a your wired interface that would<11:50:55.256> prescribe<11:50:55.800> a<11:50:55.980> specific<11:50:56.340> number 11:50:57.650 --> 11:50:57.660 align:start position:0% would prescribe a specific number 11:50:57.660 --> 11:50:59.266 align:start position:0% would prescribe a specific number the<11:50:58.080> Gateway<11:50:58.320> is<11:50:58.436> going<11:50:58.560> to<11:50:58.560> say<11:50:58.680> what<11:50:58.860> Gateway 11:50:59.266 --> 11:50:59.276 align:start position:0% the Gateway is going to say what Gateway 11:50:59.276 --> 11:51:01.730 align:start position:0% the Gateway is going to say what Gateway you<11:50:59.700> need<11:50:59.820> to<11:50:59.936> get<11:51:00.116> out<11:51:00.300> and<11:51:01.020> the<11:51:01.140> subnet<11:51:01.560> mask 11:51:01.730 --> 11:51:01.740 align:start position:0% you need to get out and the subnet mask 11:51:01.740 --> 11:51:05.870 align:start position:0% you need to get out and the subnet mask and<11:51:02.580> you<11:51:02.820> could<11:51:02.936> actually<11:51:03.180> add 11:51:05.870 --> 11:51:05.880 align:start position:0% 11:51:05.880 --> 11:51:09.170 align:start position:0% specific<11:51:06.660> information<11:51:07.140> to<11:51:07.916> this<11:51:08.160> to<11:51:08.820> create 11:51:09.170 --> 11:51:09.180 align:start position:0% specific information to this to create 11:51:09.180 --> 11:51:11.150 align:start position:0% specific information to this to create your<11:51:09.480> own<11:51:09.596> routing<11:51:10.020> table<11:51:10.200> and<11:51:10.860> this<11:51:11.040> you 11:51:11.150 --> 11:51:11.160 align:start position:0% your own routing table and this you 11:51:11.160 --> 11:51:12.766 align:start position:0% your own routing table and this you would<11:51:11.340> do<11:51:11.580> really<11:51:11.936> not<11:51:12.180> so<11:51:12.300> much<11:51:12.480> on<11:51:12.596> your 11:51:12.766 --> 11:51:12.776 align:start position:0% would do really not so much on your 11:51:12.776 --> 11:51:14.630 align:start position:0% would do really not so much on your computer<11:51:12.960> but<11:51:13.560> more<11:51:13.740> if<11:51:13.916> you're<11:51:14.096> working<11:51:14.276> on<11:51:14.520> a 11:51:14.630 --> 11:51:14.640 align:start position:0% computer but more if you're working on a 11:51:14.640 --> 11:51:17.390 align:start position:0% computer but more if you're working on a router<11:51:14.936> say<11:51:15.180> Cisco<11:51:15.660> router<11:51:16.080> so<11:51:16.200> you<11:51:16.380> can<11:51:16.560> do 11:51:17.390 --> 11:51:17.400 align:start position:0% router say Cisco router so you can do 11:51:17.400 --> 11:51:19.130 align:start position:0% router say Cisco router so you can do to tell<11:51:17.880> it<11:51:18.000> exactly<11:51:18.540> where<11:51:18.840> you<11:51:18.960> want 11:51:19.130 --> 11:51:19.140 align:start position:0% to tell it exactly where you want 11:51:19.140 --> 11:51:23.330 align:start position:0% to tell it exactly where you want information<11:51:19.320> to<11:51:19.740> be<11:51:19.860> routed 11:51:23.330 --> 11:51:23.340 align:start position:0% 11:51:23.340 --> 11:51:25.906 align:start position:0% so<11:51:23.936> just<11:51:24.060> to<11:51:24.240> recap<11:51:24.596> we<11:51:25.380> discussed<11:51:25.800> and 11:51:25.906 --> 11:51:25.916 align:start position:0% so just to recap we discussed and 11:51:25.916 --> 11:51:28.850 align:start position:0% so just to recap we discussed and demonstrated<11:51:26.340> several<11:51:26.756> TCP<11:51:27.300> tools<11:51:28.020> including 11:51:28.850 --> 11:51:28.860 align:start position:0% demonstrated several TCP tools including 11:51:28.860 --> 11:51:32.150 align:start position:0% demonstrated several TCP tools including ping<11:51:29.276> which<11:51:30.240> we're<11:51:30.480> really<11:51:30.720> going<11:51:31.020> to<11:51:31.200> use<11:51:31.436> to 11:51:32.150 --> 11:51:32.160 align:start position:0% ping which we're really going to use to 11:51:32.160 --> 11:51:34.190 align:start position:0% ping which we're really going to use to test<11:51:32.400> connectivity 11:51:34.190 --> 11:51:34.200 align:start position:0% test connectivity 11:51:34.200 --> 11:51:37.790 align:start position:0% test connectivity and<11:51:34.740> remember<11:51:34.916> you<11:51:35.340> want<11:51:35.520> to<11:51:35.756> hold<11:51:36.180> on<11:51:36.360> to<11:51:36.960> the 11:51:37.790 --> 11:51:37.800 align:start position:0% and remember you want to hold on to the 11:51:37.800 --> 11:51:38.870 align:start position:0% and remember you want to hold on to the Slash 11:51:38.870 --> 11:51:38.880 align:start position:0% Slash 11:51:38.880 --> 11:51:41.510 align:start position:0% Slash t-switch<11:51:39.840> which<11:51:40.800> is<11:51:40.916> going<11:51:41.096> to<11:51:41.220> do<11:51:41.400> it 11:51:41.510 --> 11:51:41.520 align:start position:0% t-switch which is going to do it 11:51:41.520 --> 11:51:44.030 align:start position:0% t-switch which is going to do it indefinitely<11:51:42.200> trace<11:51:43.200> route<11:51:43.436> which<11:51:43.740> is<11:51:43.860> going 11:51:44.030 --> 11:51:44.040 align:start position:0% indefinitely trace route which is going 11:51:44.040 --> 11:51:46.670 align:start position:0% indefinitely trace route which is going to<11:51:44.096> measure<11:51:44.520> the<11:51:45.060> Hops<11:51:45.480> and<11:51:45.960> can<11:51:46.080> also<11:51:46.380> tell 11:51:46.670 --> 11:51:46.680 align:start position:0% to measure the Hops and can also tell 11:51:46.680 --> 11:51:50.150 align:start position:0% to measure the Hops and can also tell you<11:51:46.860> where 11:51:50.150 --> 11:51:50.160 align:start position:0% 11:51:50.160 --> 11:51:53.510 align:start position:0% uh<11:51:50.936> connection<11:51:51.300> has<11:51:51.840> been<11:51:52.140> lost<11:51:52.380> a<11:51:53.220> protocol 11:51:53.510 --> 11:51:53.520 align:start position:0% uh connection has been lost a protocol 11:51:53.520 --> 11:51:55.370 align:start position:0% uh connection has been lost a protocol analyzer<11:51:54.180> which<11:51:54.360> is<11:51:54.480> going<11:51:54.660> to<11:51:54.720> look<11:51:54.900> at<11:51:55.080> or 11:51:55.370 --> 11:51:55.380 align:start position:0% analyzer which is going to look at or 11:51:55.380 --> 11:51:57.350 align:start position:0% analyzer which is going to look at or network<11:51:55.800> protocol<11:51:56.276> analyzer<11:51:56.880> we're<11:51:57.180> going<11:51:57.360> to 11:51:57.350 --> 11:51:57.360 align:start position:0% network protocol analyzer we're going to 11:51:57.360 --> 11:51:58.850 align:start position:0% network protocol analyzer we're going to look<11:51:57.540> at<11:51:57.596> all<11:51:57.720> the<11:51:57.840> protocols<11:51:58.256> coming<11:51:58.436> in<11:51:58.680> and 11:51:58.850 --> 11:51:58.860 align:start position:0% look at all the protocols coming in and 11:51:58.860 --> 11:52:01.426 align:start position:0% look at all the protocols coming in and can<11:51:59.096> actually<11:51:59.460> filter<11:51:59.820> them<11:52:00.116> in<11:52:00.360> or<11:52:00.540> out<11:52:00.660> a 11:52:01.426 --> 11:52:01.436 align:start position:0% can actually filter them in or out a 11:52:01.436 --> 11:52:03.766 align:start position:0% can actually filter them in or out a port<11:52:01.616> scanner<11:52:02.160> which<11:52:02.640> can<11:52:02.820> be<11:52:02.936> used<11:52:03.116> to<11:52:03.540> show 11:52:03.766 --> 11:52:03.776 align:start position:0% port scanner which can be used to show 11:52:03.776 --> 11:52:06.710 align:start position:0% port scanner which can be used to show open<11:52:04.140> ports<11:52:04.740> either<11:52:05.520> as<11:52:06.360> a<11:52:06.540> security 11:52:06.710 --> 11:52:06.720 align:start position:0% open ports either as a security 11:52:06.720 --> 11:52:08.746 align:start position:0% open ports either as a security precaution<11:52:07.500> or<11:52:08.040> if<11:52:08.220> I'm<11:52:08.340> trying<11:52:08.520> to 11:52:08.746 --> 11:52:08.756 align:start position:0% precaution or if I'm trying to 11:52:08.756 --> 11:52:12.470 align:start position:0% precaution or if I'm trying to infiltrate<11:52:09.660> your<11:52:10.080> network<11:52:10.320> the<11:52:11.220> NS<11:52:11.520> lookup 11:52:12.470 --> 11:52:12.480 align:start position:0% infiltrate your network the NS lookup 11:52:12.480 --> 11:52:14.810 align:start position:0% infiltrate your network the NS lookup which<11:52:12.900> is<11:52:13.020> that<11:52:13.256> name<11:52:13.436> server<11:52:13.916> could<11:52:14.340> also<11:52:14.640> be 11:52:14.810 --> 11:52:14.820 align:start position:0% which is that name server could also be 11:52:14.820 --> 11:52:18.470 align:start position:0% which is that name server could also be dig<11:52:15.116> by<11:52:15.660> the<11:52:15.776> way<11:52:15.900> which<11:52:16.256> is<11:52:16.320> on<11:52:16.500> Unix<11:52:16.916> systems 11:52:18.470 --> 11:52:18.480 align:start position:0% dig by the way which is on Unix systems 11:52:18.480 --> 11:52:20.266 align:start position:0% dig by the way which is on Unix systems and<11:52:18.900> this<11:52:19.080> is<11:52:19.140> going<11:52:19.256> to<11:52:19.320> allow<11:52:19.560> me<11:52:19.680> to<11:52:19.860> get<11:52:19.980> my 11:52:20.266 --> 11:52:20.276 align:start position:0% and this is going to allow me to get my 11:52:20.276 --> 11:52:24.170 align:start position:0% and this is going to allow me to get my IP<11:52:20.580> address<11:52:21.200> to<11:52:22.200> a<11:52:22.616> fully<11:52:22.916> qualified<11:52:23.400> domain 11:52:24.170 --> 11:52:24.180 align:start position:0% IP address to a fully qualified domain 11:52:24.180 --> 11:52:25.310 align:start position:0% IP address to a fully qualified domain name 11:52:25.310 --> 11:52:25.320 align:start position:0% name 11:52:25.320 --> 11:52:28.790 align:start position:0% name ARP<11:52:26.040> address<11:52:26.400> resolution<11:52:27.116> protocol<11:52:27.660> which<11:52:28.560> is 11:52:28.790 --> 11:52:28.800 align:start position:0% ARP address resolution protocol which is 11:52:28.800 --> 11:52:30.950 align:start position:0% ARP address resolution protocol which is specifically<11:52:29.340> going<11:52:29.640> from<11:52:30.060> IP<11:52:30.416> address<11:52:30.660> to 11:52:30.950 --> 11:52:30.960 align:start position:0% specifically going from IP address to 11:52:30.960 --> 11:52:33.170 align:start position:0% specifically going from IP address to MAC<11:52:31.140> address<11:52:31.380> it<11:52:32.220> sort<11:52:32.400> of<11:52:32.520> really<11:52:32.756> allows 11:52:33.170 --> 11:52:33.180 align:start position:0% MAC address it sort of really allows 11:52:33.180 --> 11:52:35.570 align:start position:0% MAC address it sort of really allows routing<11:52:33.660> to<11:52:33.960> occur<11:52:34.380> this<11:52:34.980> is<11:52:35.096> really<11:52:35.276> a 11:52:35.570 --> 11:52:35.580 align:start position:0% routing to occur this is really a 11:52:35.580 --> 11:52:38.086 align:start position:0% routing to occur this is really a principle<11:52:36.000> in<11:52:36.840> routers 11:52:38.086 --> 11:52:38.096 align:start position:0% principle in routers 11:52:38.096 --> 11:52:41.150 align:start position:0% principle in routers and<11:52:38.700> finally<11:52:39.000> the<11:52:39.480> route<11:52:40.200> command<11:52:40.800> which 11:52:41.150 --> 11:52:41.160 align:start position:0% and finally the route command which 11:52:41.160 --> 11:52:44.630 align:start position:0% and finally the route command which allows<11:52:41.520> us<11:52:41.640> to<11:52:41.880> edit<11:52:42.720> the<11:52:43.320> routing<11:52:43.740> tables<11:52:44.220> and 11:52:44.630 --> 11:52:44.640 align:start position:0% allows us to edit the routing tables and 11:52:44.640 --> 11:52:47.210 align:start position:0% allows us to edit the routing tables and would<11:52:44.820> be<11:52:45.060> really<11:52:45.480> useful<11:52:45.900> if<11:52:46.560> I<11:52:46.740> was<11:52:46.916> using 11:52:47.210 --> 11:52:47.220 align:start position:0% would be really useful if I was using 11:52:47.220 --> 11:52:50.086 align:start position:0% would be really useful if I was using one<11:52:47.520> of<11:52:47.640> my<11:52:47.700> servers<11:52:48.116> as<11:52:48.480> a<11:52:48.840> router<11:52:49.560> you're<11:52:49.980> not 11:52:50.086 --> 11:52:50.096 align:start position:0% one of my servers as a router you're not 11:52:50.096 --> 11:52:51.766 align:start position:0% one of my servers as a router you're not really<11:52:50.276> going<11:52:50.400> to<11:52:50.520> see<11:52:50.640> routing<11:52:51.180> a<11:52:51.596> route 11:52:51.766 --> 11:52:51.776 align:start position:0% really going to see routing a route 11:52:51.776 --> 11:52:55.246 align:start position:0% really going to see routing a route command<11:52:52.580> on<11:52:53.580> the<11:52:53.880> network<11:52:54.180> plus<11:52:54.480> exam<11:52:54.840> but<11:52:55.080> I 11:52:55.246 --> 11:52:55.256 align:start position:0% command on the network plus exam but I 11:52:55.256 --> 11:52:57.290 align:start position:0% command on the network plus exam but I guarantee<11:52:55.740> you'll<11:52:56.276> see<11:52:56.460> all<11:52:56.700> these<11:52:56.880> others 11:52:57.290 --> 11:52:57.300 align:start position:0% guarantee you'll see all these others 11:52:57.300 --> 11:52:59.990 align:start position:0% guarantee you'll see all these others mentioned 11:52:59.990 --> 11:53:00.000 align:start position:0% mentioned 11:53:00.000 --> 11:53:01.970 align:start position:0% mentioned so<11:53:00.480> uh<11:53:00.900> now<11:53:01.080> that<11:53:01.256> we've<11:53:01.380> finished<11:53:01.500> up<11:53:01.740> this 11:53:01.970 --> 11:53:01.980 align:start position:0% so uh now that we've finished up this 11:53:01.980 --> 11:53:04.970 align:start position:0% so uh now that we've finished up this very<11:53:02.220> brief<11:53:02.460> lesson<11:53:02.820> on<11:53:03.060> TCP<11:53:03.560> the<11:53:04.560> tools<11:53:04.860> and 11:53:04.970 --> 11:53:04.980 align:start position:0% very brief lesson on TCP the tools and 11:53:04.980 --> 11:53:06.650 align:start position:0% very brief lesson on TCP the tools and the<11:53:05.160> simple<11:53:05.220> Services<11:53:05.580> we're<11:53:06.240> going<11:53:06.416> to<11:53:06.540> go 11:53:06.650 --> 11:53:06.660 align:start position:0% the simple Services we're going to go 11:53:06.660 --> 11:53:08.990 align:start position:0% the simple Services we're going to go into<11:53:06.900> Lan<11:53:07.680> Administration<11:53:08.340> and 11:53:08.990 --> 11:53:09.000 align:start position:0% into Lan Administration and 11:53:09.000 --> 11:53:15.180 align:start position:0% into Lan Administration and implementation<11:53:09.596> a<11:53:09.960> bit<11:53:10.140> more<11:53:10.380> in<11:53:10.680> depth 11:53:15.180 --> 11:53:15.190 align:start position:0% 11:53:15.190 --> 11:53:19.266 align:start position:0% [Music] 11:53:19.266 --> 11:53:19.276 align:start position:0% [Music] 11:53:19.276 --> 11:53:22.906 align:start position:0% [Music] thank<11:53:20.276> you 11:53:22.906 --> 11:53:22.916 align:start position:0% 11:53:22.916 --> 11:53:38.470 align:start position:0% foreign 11:53:38.470 --> 11:53:38.480 align:start position:0% 11:53:38.480 --> 11:53:41.150 align:start position:0% Network<11:53:39.616> Administration<11:53:40.616> and 11:53:41.150 --> 11:53:41.160 align:start position:0% Network Administration and 11:53:41.160 --> 11:53:42.830 align:start position:0% Network Administration and implementation 11:53:42.830 --> 11:53:42.840 align:start position:0% implementation 11:53:42.840 --> 11:53:45.470 align:start position:0% implementation so<11:53:43.320> in<11:53:43.740> previous<11:53:43.916> lessons<11:53:44.460> we've<11:53:44.880> discussed<11:53:45.300> a 11:53:45.470 --> 11:53:45.480 align:start position:0% so in previous lessons we've discussed a 11:53:45.480 --> 11:53:47.450 align:start position:0% so in previous lessons we've discussed a lot<11:53:45.540> of<11:53:45.660> the<11:53:45.776> tools<11:53:46.256> the<11:53:47.040> networking 11:53:47.450 --> 11:53:47.460 align:start position:0% lot of the tools the networking 11:53:47.460 --> 11:53:50.086 align:start position:0% lot of the tools the networking fundamentals<11:53:48.360> the<11:53:48.720> theory<11:53:49.020> and<11:53:49.200> so<11:53:49.436> on<11:53:49.560> and 11:53:50.086 --> 11:53:50.096 align:start position:0% fundamentals the theory and so on and 11:53:50.096 --> 11:53:52.370 align:start position:0% fundamentals the theory and so on and now<11:53:50.340> we're<11:53:50.820> going<11:53:51.060> to<11:53:51.360> get<11:53:51.596> into<11:53:51.960> a<11:53:52.256> little 11:53:52.370 --> 11:53:52.380 align:start position:0% now we're going to get into a little 11:53:52.380 --> 11:53:54.406 align:start position:0% now we're going to get into a little more<11:53:52.560> of<11:53:52.680> the<11:53:52.800> Practical<11:53:53.220> side<11:53:53.520> and<11:53:53.936> that's<11:53:54.116> in 11:53:54.406 --> 11:53:54.416 align:start position:0% more of the Practical side and that's in 11:53:54.416 --> 11:53:57.106 align:start position:0% more of the Practical side and that's in creating<11:53:54.840> and<11:53:55.140> maintaining<11:53:55.740> a<11:53:56.580> local<11:53:56.880> area 11:53:57.106 --> 11:53:57.116 align:start position:0% creating and maintaining a local area 11:53:57.116 --> 11:53:58.790 align:start position:0% creating and maintaining a local area network<11:53:57.360> wide<11:53:57.840> area<11:53:57.960> network<11:53:58.200> and<11:53:58.436> so<11:53:58.560> on<11:53:58.740> and 11:53:58.790 --> 11:53:58.800 align:start position:0% network wide area network and so on and 11:53:58.800 --> 11:54:01.550 align:start position:0% network wide area network and so on and so<11:53:58.980> forth<11:53:59.276> this<11:54:00.180> module<11:54:00.596> is<11:54:00.840> certainly<11:54:01.200> just 11:54:01.550 --> 11:54:01.560 align:start position:0% so forth this module is certainly just 11:54:01.560 --> 11:54:04.246 align:start position:0% so forth this module is certainly just an<11:54:01.916> overview<11:54:02.460> of<11:54:03.240> local<11:54:03.480> area<11:54:03.720> network<11:54:03.960> and 11:54:04.246 --> 11:54:04.256 align:start position:0% an overview of local area network and 11:54:04.256 --> 11:54:05.810 align:start position:0% an overview of local area network and some<11:54:04.380> of<11:54:04.500> the<11:54:04.560> best<11:54:04.740> practices<11:54:05.220> that<11:54:05.520> go<11:54:05.640> along 11:54:05.810 --> 11:54:05.820 align:start position:0% some of the best practices that go along 11:54:05.820 --> 11:54:07.850 align:start position:0% some of the best practices that go along with<11:54:06.000> it<11:54:06.180> as<11:54:06.540> we<11:54:06.776> get<11:54:06.900> more<11:54:07.080> in<11:54:07.256> depth<11:54:07.500> over<11:54:07.680> the 11:54:07.850 --> 11:54:07.860 align:start position:0% with it as we get more in depth over the 11:54:07.860 --> 11:54:10.370 align:start position:0% with it as we get more in depth over the coming<11:54:08.040> lessons<11:54:08.580> and<11:54:08.820> modules<11:54:09.240> we'll<11:54:10.020> talk 11:54:10.370 --> 11:54:10.380 align:start position:0% coming lessons and modules we'll talk 11:54:10.380 --> 11:54:12.290 align:start position:0% coming lessons and modules we'll talk more<11:54:10.680> about<11:54:10.916> the<11:54:11.276> specifics<11:54:11.880> and<11:54:12.000> what<11:54:12.180> we 11:54:12.290 --> 11:54:12.300 align:start position:0% more about the specifics and what we 11:54:12.300 --> 11:54:13.246 align:start position:0% more about the specifics and what we need<11:54:12.416> to<11:54:12.540> do 11:54:13.246 --> 11:54:13.256 align:start position:0% need to do 11:54:13.256 --> 11:54:16.010 align:start position:0% need to do so<11:54:13.916> in<11:54:14.276> this<11:54:14.460> module<11:54:14.880> we're<11:54:15.360> going<11:54:15.540> to<11:54:15.776> talk 11:54:16.010 --> 11:54:16.020 align:start position:0% so in this module we're going to talk 11:54:16.020 --> 11:54:18.350 align:start position:0% so in this module we're going to talk about<11:54:16.380> an<11:54:16.800> overview<11:54:17.096> of<11:54:17.340> a<11:54:17.520> lan<11:54:17.756> kind<11:54:18.116> of<11:54:18.300> go 11:54:18.350 --> 11:54:18.360 align:start position:0% about an overview of a lan kind of go 11:54:18.360 --> 11:54:21.290 align:start position:0% about an overview of a lan kind of go back<11:54:18.540> over<11:54:18.720> what<11:54:19.020> it<11:54:19.200> is<11:54:19.320> and<11:54:20.096> also 11:54:21.290 --> 11:54:21.300 align:start position:0% back over what it is and also 11:54:21.300 --> 11:54:23.570 align:start position:0% back over what it is and also um<11:54:21.380> when<11:54:22.380> we'd<11:54:22.680> probably<11:54:22.800> want<11:54:23.040> to<11:54:23.160> use<11:54:23.276> one 11:54:23.570 --> 11:54:23.580 align:start position:0% um when we'd probably want to use one 11:54:23.580 --> 11:54:25.490 align:start position:0% um when we'd probably want to use one and<11:54:24.060> then<11:54:24.116> we're<11:54:24.240> going<11:54:24.360> to<11:54:24.416> identify<11:54:25.020> the 11:54:25.490 --> 11:54:25.500 align:start position:0% and then we're going to identify the 11:54:25.500 --> 11:54:27.890 align:start position:0% and then we're going to identify the steps<11:54:25.860> to<11:54:26.040> setting<11:54:26.400> up<11:54:26.520> a<11:54:26.756> lan<11:54:27.060> including 11:54:27.890 --> 11:54:27.900 align:start position:0% steps to setting up a lan including 11:54:27.900 --> 11:54:30.710 align:start position:0% steps to setting up a lan including using<11:54:28.436> a<11:54:28.560> network<11:54:28.740> plan<11:54:29.096> having<11:54:30.000> backups 11:54:30.710 --> 11:54:30.720 align:start position:0% using a network plan having backups 11:54:30.720 --> 11:54:34.010 align:start position:0% using a network plan having backups creating<11:54:31.560> proper<11:54:31.980> documentation<11:54:33.020> auditing 11:54:34.010 --> 11:54:34.020 align:start position:0% creating proper documentation auditing 11:54:34.020 --> 11:54:36.406 align:start position:0% creating proper documentation auditing and<11:54:34.616> security 11:54:36.406 --> 11:54:36.416 align:start position:0% and security 11:54:36.416 --> 11:54:38.210 align:start position:0% and security so<11:54:36.776> first<11:54:36.900> what<11:54:37.200> is<11:54:37.320> a<11:54:37.436> lan<11:54:37.680> well<11:54:37.860> there<11:54:38.096> are 11:54:38.210 --> 11:54:38.220 align:start position:0% so first what is a lan well there are 11:54:38.220 --> 11:54:40.310 align:start position:0% so first what is a lan well there are two<11:54:38.400> types<11:54:38.700> of<11:54:38.820> networks<11:54:39.180> as<11:54:39.300> you<11:54:39.480> recall<11:54:39.840> one 11:54:40.310 --> 11:54:40.320 align:start position:0% two types of networks as you recall one 11:54:40.320 --> 11:54:42.766 align:start position:0% two types of networks as you recall one is<11:54:40.500> a<11:54:40.616> lan<11:54:40.800> and<11:54:40.916> the<11:54:41.040> other<11:54:41.160> is<11:54:41.276> a<11:54:41.400> Wan<11:54:41.700> a<11:54:42.596> land 11:54:42.766 --> 11:54:42.776 align:start position:0% is a lan and the other is a Wan a land 11:54:42.776 --> 11:54:45.350 align:start position:0% is a lan and the other is a Wan a land stands<11:54:43.256> for<11:54:43.380> again<11:54:43.740> a<11:54:44.276> local<11:54:44.520> area<11:54:44.880> network 11:54:45.350 --> 11:54:45.360 align:start position:0% stands for again a local area network 11:54:45.360 --> 11:54:48.650 align:start position:0% stands for again a local area network and<11:54:45.900> the<11:54:46.080> local<11:54:46.200> area<11:54:46.436> network<11:54:46.800> is<11:54:47.460> really<11:54:47.756> any 11:54:48.650 --> 11:54:48.660 align:start position:0% and the local area network is really any 11:54:48.660 --> 11:54:52.070 align:start position:0% and the local area network is really any sort<11:54:48.960> of<11:54:49.140> local<11:54:49.860> or<11:54:50.220> geographically 11:54:52.070 --> 11:54:52.080 align:start position:0% sort of local or geographically 11:54:52.080 --> 11:54:52.670 align:start position:0% sort of local or geographically um 11:54:52.670 --> 11:54:52.680 align:start position:0% um 11:54:52.680 --> 11:54:57.406 align:start position:0% um uh<11:54:53.460> specific<11:54:54.436> Network<11:54:55.436> now<11:54:56.096> Wan<11:54:56.580> stands<11:54:57.000> for<11:54:57.116> a 11:54:57.406 --> 11:54:57.416 align:start position:0% uh specific Network now Wan stands for a 11:54:57.416 --> 11:54:58.490 align:start position:0% uh specific Network now Wan stands for a wide<11:54:57.596> area<11:54:57.720> network<11:54:57.960> and<11:54:58.256> we're<11:54:58.380> going<11:54:58.436> to 11:54:58.490 --> 11:54:58.500 align:start position:0% wide area network and we're going to 11:54:58.500 --> 11:54:59.990 align:start position:0% wide area network and we're going to talk<11:54:58.616> about<11:54:58.740> that<11:54:59.040> in<11:54:59.276> more<11:54:59.460> depth<11:54:59.756> in<11:54:59.880> the 11:54:59.990 --> 11:55:00.000 align:start position:0% talk about that in more depth in the 11:55:00.000 --> 11:55:02.266 align:start position:0% talk about that in more depth in the future<11:55:00.180> so<11:55:00.960> because<11:55:01.140> Lan<11:55:01.560> is<11:55:01.740> restricted<11:55:02.096> to 11:55:02.266 --> 11:55:02.276 align:start position:0% future so because Lan is restricted to 11:55:02.276 --> 11:55:04.550 align:start position:0% future so because Lan is restricted to one<11:55:02.400> geographical<11:55:03.060> location<11:55:03.540> such<11:55:04.200> as<11:55:04.320> a 11:55:04.550 --> 11:55:04.560 align:start position:0% one geographical location such as a 11:55:04.560 --> 11:55:06.530 align:start position:0% one geographical location such as a school<11:55:04.740> or<11:55:05.040> a<11:55:05.160> small<11:55:05.340> office<11:55:05.580> building<11:55:05.880> it's<11:55:06.300> a 11:55:06.530 --> 11:55:06.540 align:start position:0% school or a small office building it's a 11:55:06.540 --> 11:55:09.050 align:start position:0% school or a small office building it's a lot<11:55:06.596> easier<11:55:07.020> to<11:55:07.320> administer<11:55:07.800> and<11:55:08.400> requires<11:55:08.880> a 11:55:09.050 --> 11:55:09.060 align:start position:0% lot easier to administer and requires a 11:55:09.060 --> 11:55:11.746 align:start position:0% lot easier to administer and requires a certain<11:55:09.240> specific<11:55:10.020> set<11:55:10.320> of<11:55:10.500> skills<11:55:10.980> since 11:55:11.746 --> 11:55:11.756 align:start position:0% certain specific set of skills since 11:55:11.756 --> 11:55:14.150 align:start position:0% certain specific set of skills since it's<11:55:12.180> so<11:55:12.540> localized<11:55:13.080> it<11:55:13.200> also<11:55:13.500> has<11:55:13.680> higher 11:55:14.150 --> 11:55:14.160 align:start position:0% it's so localized it also has higher 11:55:14.160 --> 11:55:15.950 align:start position:0% it's so localized it also has higher speed<11:55:14.400> capabilities<11:55:15.000> than<11:55:15.300> a<11:55:15.416> Wan<11:55:15.660> and<11:55:15.840> it's 11:55:15.950 --> 11:55:15.960 align:start position:0% speed capabilities than a Wan and it's 11:55:15.960 --> 11:55:18.650 align:start position:0% speed capabilities than a Wan and it's often<11:55:16.320> a<11:55:16.500> lot<11:55:16.560> less<11:55:16.916> expensive<11:55:17.520> so<11:55:18.240> here's<11:55:18.540> an 11:55:18.650 --> 11:55:18.660 align:start position:0% often a lot less expensive so here's an 11:55:18.660 --> 11:55:22.550 align:start position:0% often a lot less expensive so here's an example<11:55:19.020> of<11:55:19.680> a<11:55:19.980> local<11:55:20.276> area<11:55:20.700> network<11:55:21.560> the 11:55:22.550 --> 11:55:22.560 align:start position:0% example of a local area network the 11:55:22.560 --> 11:55:25.730 align:start position:0% example of a local area network the internet<11:55:22.936> connectivity<11:55:23.936> comes<11:55:24.596> from<11:55:24.900> the 11:55:25.730 --> 11:55:25.740 align:start position:0% internet connectivity comes from the 11:55:25.740 --> 11:55:28.730 align:start position:0% internet connectivity comes from the server 11:55:28.730 --> 11:55:28.740 align:start position:0% 11:55:28.740 --> 11:55:32.030 align:start position:0% which<11:55:29.400> is<11:55:29.580> going<11:55:29.820> to<11:55:29.936> also<11:55:30.300> go<11:55:30.540> out 11:55:32.030 --> 11:55:32.040 align:start position:0% which is going to also go out 11:55:32.040 --> 11:55:35.086 align:start position:0% which is going to also go out to<11:55:32.720> the<11:55:33.720> WAN<11:55:34.020> which<11:55:34.380> would<11:55:34.500> generally<11:55:34.916> be 11:55:35.086 --> 11:55:35.096 align:start position:0% to the WAN which would generally be 11:55:35.096 --> 11:55:38.330 align:start position:0% to the WAN which would generally be represented<11:55:35.520> by<11:55:35.880> a<11:55:36.060> cloud<11:55:36.660> the<11:55:37.080> WAN<11:55:37.380> being<11:55:37.616> the 11:55:38.330 --> 11:55:38.340 align:start position:0% represented by a cloud the WAN being the 11:55:38.340 --> 11:55:41.150 align:start position:0% represented by a cloud the WAN being the internet<11:55:38.720> and<11:55:39.720> we<11:55:39.900> can<11:55:40.020> see<11:55:40.200> that<11:55:40.436> there<11:55:40.616> is<11:55:40.800> a 11:55:41.150 --> 11:55:41.160 align:start position:0% internet and we can see that there is a 11:55:41.160 --> 11:55:43.850 align:start position:0% internet and we can see that there is a switch<11:55:41.520> here<11:55:42.000> which<11:55:42.596> connects<11:55:43.200> each<11:55:43.500> one<11:55:43.740> of 11:55:43.850 --> 11:55:43.860 align:start position:0% switch here which connects each one of 11:55:43.860 --> 11:55:45.606 align:start position:0% switch here which connects each one of these<11:55:44.096> PCS 11:55:45.606 --> 11:55:45.616 align:start position:0% these PCS 11:55:45.616 --> 11:55:48.230 align:start position:0% these PCS wirelessly<11:55:46.616> perhaps<11:55:47.096> has<11:55:47.276> a<11:55:47.520> PC<11:55:47.756> connected 11:55:48.230 --> 11:55:48.240 align:start position:0% wirelessly perhaps has a PC connected 11:55:48.240 --> 11:55:51.050 align:start position:0% wirelessly perhaps has a PC connected through<11:55:48.480> it<11:55:48.660> thanks<11:55:49.256> to<11:55:49.616> a<11:55:49.980> wireless<11:55:50.460> access 11:55:51.050 --> 11:55:51.060 align:start position:0% through it thanks to a wireless access 11:55:51.060 --> 11:55:53.390 align:start position:0% through it thanks to a wireless access point<11:55:51.416> perhaps<11:55:51.900> connected<11:55:52.436> to<11:55:52.680> the<11:55:52.860> switch<11:55:53.040> or 11:55:53.390 --> 11:55:53.400 align:start position:0% point perhaps connected to the switch or 11:55:53.400 --> 11:55:56.210 align:start position:0% point perhaps connected to the switch or router<11:55:53.820> by<11:55:54.360> the<11:55:54.480> way<11:55:54.540> here<11:55:54.900> this<11:55:55.436> server<11:55:55.916> is 11:55:56.210 --> 11:55:56.220 align:start position:0% router by the way here this server is 11:55:56.220 --> 11:55:58.310 align:start position:0% router by the way here this server is acting<11:55:56.700> as<11:55:56.880> a<11:55:57.060> router<11:55:57.360> and<11:55:57.720> we<11:55:57.900> might<11:55:58.020> also 11:55:58.310 --> 11:55:58.320 align:start position:0% acting as a router and we might also 11:55:58.320 --> 11:56:00.530 align:start position:0% acting as a router and we might also have<11:55:58.500> the<11:55:58.680> network<11:55:59.040> connected<11:55:59.580> printer<11:55:59.936> very 11:56:00.530 --> 11:56:00.540 align:start position:0% have the network connected printer very 11:56:00.540 --> 11:56:03.766 align:start position:0% have the network connected printer very simple<11:56:00.840> but<11:56:01.616> effective<11:56:02.340> Lan<11:56:02.700> here 11:56:03.766 --> 11:56:03.776 align:start position:0% simple but effective Lan here 11:56:03.776 --> 11:56:07.310 align:start position:0% simple but effective Lan here now<11:56:04.320> at<11:56:04.560> the<11:56:04.740> heart<11:56:04.980> of<11:56:05.340> every<11:56:05.700> network<11:56:06.116> is<11:56:07.020> a 11:56:07.310 --> 11:56:07.320 align:start position:0% now at the heart of every network is a 11:56:07.320 --> 11:56:09.470 align:start position:0% now at the heart of every network is a server<11:56:07.616> the<11:56:08.096> server<11:56:08.460> is<11:56:08.640> really<11:56:08.820> what<11:56:09.116> powers 11:56:09.470 --> 11:56:09.480 align:start position:0% server the server is really what powers 11:56:09.480 --> 11:56:11.150 align:start position:0% server the server is really what powers the<11:56:09.840> internet<11:56:09.960> connection<11:56:10.256> to<11:56:10.740> every<11:56:10.916> device 11:56:11.150 --> 11:56:11.160 align:start position:0% the internet connection to every device 11:56:11.160 --> 11:56:13.906 align:start position:0% the internet connection to every device that's<11:56:11.520> on<11:56:11.700> the<11:56:11.820> network<11:56:11.936> and<11:56:12.360> provides 11:56:13.906 --> 11:56:13.916 align:start position:0% that's on the network and provides 11:56:13.916 --> 11:56:15.730 align:start position:0% that's on the network and provides um 11:56:15.730 --> 11:56:15.740 align:start position:0% um 11:56:15.740 --> 11:56:18.850 align:start position:0% um devices<11:56:16.740> on<11:56:17.276> the<11:56:17.400> network<11:56:17.520> with<11:56:18.000> resources 11:56:18.850 --> 11:56:18.860 align:start position:0% devices on the network with resources 11:56:18.860 --> 11:56:22.490 align:start position:0% devices on the network with resources and<11:56:19.860> other<11:56:20.460> sorts<11:56:21.000> of<11:56:21.116> information<11:56:21.416> now<11:56:22.200> in 11:56:22.490 --> 11:56:22.500 align:start position:0% and other sorts of information now in 11:56:22.500 --> 11:56:23.746 align:start position:0% and other sorts of information now in some<11:56:22.616> cases<11:56:22.860> we're<11:56:23.096> not<11:56:23.220> going<11:56:23.340> to<11:56:23.460> have<11:56:23.580> a 11:56:23.746 --> 11:56:23.756 align:start position:0% some cases we're not going to have a 11:56:23.756 --> 11:56:25.190 align:start position:0% some cases we're not going to have a server<11:56:24.000> network<11:56:24.180> but<11:56:24.480> we're<11:56:24.596> going<11:56:24.720> to<11:56:24.776> assume 11:56:25.190 --> 11:56:25.200 align:start position:0% server network but we're going to assume 11:56:25.200 --> 11:56:26.690 align:start position:0% server network but we're going to assume here<11:56:25.320> that<11:56:25.560> we're<11:56:25.680> talking<11:56:25.860> about<11:56:26.160> very 11:56:26.690 --> 11:56:26.700 align:start position:0% here that we're talking about very 11:56:26.700 --> 11:56:29.030 align:start position:0% here that we're talking about very technical<11:56:27.180> Network<11:56:27.416> okay<11:56:27.840> and<11:56:28.680> the<11:56:28.860> first 11:56:29.030 --> 11:56:29.040 align:start position:0% technical Network okay and the first 11:56:29.040 --> 11:56:30.766 align:start position:0% technical Network okay and the first step<11:56:29.340> to<11:56:29.820> implementing<11:56:30.300> a<11:56:30.416> local<11:56:30.540> area 11:56:30.766 --> 11:56:30.776 align:start position:0% step to implementing a local area 11:56:30.776 --> 11:56:33.170 align:start position:0% step to implementing a local area network<11:56:31.020> is<11:56:31.560> to<11:56:31.860> generally<11:56:32.220> set<11:56:32.640> up<11:56:32.820> the 11:56:33.170 --> 11:56:33.180 align:start position:0% network is to generally set up the 11:56:33.180 --> 11:56:36.170 align:start position:0% network is to generally set up the server<11:56:33.540> or<11:56:34.380> if<11:56:34.740> we<11:56:34.860> don't<11:56:35.040> have<11:56:35.400> a<11:56:35.700> server<11:56:36.000> to 11:56:36.170 --> 11:56:36.180 align:start position:0% server or if we don't have a server to 11:56:36.180 --> 11:56:37.850 align:start position:0% server or if we don't have a server to set<11:56:36.360> up<11:56:36.480> the<11:56:36.776> router 11:56:37.850 --> 11:56:37.860 align:start position:0% set up the router 11:56:37.860 --> 11:56:41.086 align:start position:0% set up the router or<11:56:38.340> the<11:56:38.580> Soho<11:56:39.000> router<11:56:39.840> in<11:56:40.500> a<11:56:40.680> small<11:56:40.860> office 11:56:41.086 --> 11:56:41.096 align:start position:0% or the Soho router in a small office 11:56:41.096 --> 11:56:42.890 align:start position:0% or the Soho router in a small office home<11:56:41.520> office<11:56:41.756> remember<11:56:42.240> the<11:56:42.540> server<11:56:42.776> is 11:56:42.890 --> 11:56:42.900 align:start position:0% home office remember the server is 11:56:42.900 --> 11:56:46.190 align:start position:0% home office remember the server is really<11:56:43.080> going<11:56:43.256> to<11:56:43.380> serve<11:56:43.616> up<11:56:43.740> resources 11:56:46.190 --> 11:56:46.200 align:start position:0% really going to serve up resources 11:56:46.200 --> 11:56:49.490 align:start position:0% really going to serve up resources it's<11:56:46.500> going<11:56:46.740> to<11:56:46.800> serve<11:56:47.096> up<11:56:47.220> a<11:56:48.060> DHCP<11:56:48.720> server<11:56:49.080> so 11:56:49.490 --> 11:56:49.500 align:start position:0% it's going to serve up a DHCP server so 11:56:49.500 --> 11:56:50.990 align:start position:0% it's going to serve up a DHCP server so on<11:56:49.680> and<11:56:49.800> so<11:56:49.916> forth<11:56:50.160> so<11:56:50.340> the<11:56:50.460> word<11:56:50.580> Server 11:56:50.990 --> 11:56:51.000 align:start position:0% on and so forth so the word Server 11:56:51.000 --> 11:56:53.030 align:start position:0% on and so forth so the word Server doesn't<11:56:51.180> necessarily<11:56:51.596> mean<11:56:51.776> a<11:56:52.040> freestanding 11:56:53.030 --> 11:56:53.040 align:start position:0% doesn't necessarily mean a freestanding 11:56:53.040 --> 11:56:55.130 align:start position:0% doesn't necessarily mean a freestanding personal<11:56:53.400> computer<11:56:53.820> or<11:56:54.180> a<11:56:54.480> more<11:56:54.720> powerful 11:56:55.130 --> 11:56:55.140 align:start position:0% personal computer or a more powerful 11:56:55.140 --> 11:56:56.926 align:start position:0% personal computer or a more powerful computer<11:56:55.436> it's<11:56:56.096> really<11:56:56.276> just<11:56:56.460> the<11:56:56.700> device 11:56:56.926 --> 11:56:56.936 align:start position:0% computer it's really just the device 11:56:56.936 --> 11:56:59.570 align:start position:0% computer it's really just the device that's<11:56:57.240> at<11:56:57.480> the<11:56:57.660> center<11:56:57.840> of<11:56:58.380> our<11:56:58.500> Network 11:56:59.570 --> 11:56:59.580 align:start position:0% that's at the center of our Network 11:56:59.580 --> 11:57:01.730 align:start position:0% that's at the center of our Network now<11:57:00.116> usually<11:57:00.596> we're<11:57:00.776> going<11:57:00.900> to<11:57:00.960> do<11:57:01.140> this<11:57:01.320> with 11:57:01.730 --> 11:57:01.740 align:start position:0% now usually we're going to do this with 11:57:01.740 --> 11:57:03.290 align:start position:0% now usually we're going to do this with some<11:57:02.220> sort<11:57:02.460> of<11:57:02.580> professional<11:57:02.936> setup 11:57:03.290 --> 11:57:03.300 align:start position:0% some sort of professional setup 11:57:03.300 --> 11:57:04.370 align:start position:0% some sort of professional setup sometimes<11:57:03.660> we'll<11:57:03.776> have<11:57:03.960> someone<11:57:04.020> else<11:57:04.256> come 11:57:04.370 --> 11:57:04.380 align:start position:0% sometimes we'll have someone else come 11:57:04.380 --> 11:57:05.330 align:start position:0% sometimes we'll have someone else come in<11:57:04.500> and<11:57:04.616> sometimes<11:57:04.860> we're<11:57:04.980> going<11:57:05.040> to<11:57:05.096> do<11:57:05.220> it 11:57:05.330 --> 11:57:05.340 align:start position:0% in and sometimes we're going to do it 11:57:05.340 --> 11:57:06.230 align:start position:0% in and sometimes we're going to do it ourselves 11:57:06.230 --> 11:57:06.240 align:start position:0% ourselves 11:57:06.240 --> 11:57:09.106 align:start position:0% ourselves now<11:57:06.840> the<11:57:07.200> network<11:57:07.460> topography<11:57:08.460> and<11:57:08.640> design<11:57:08.820> is 11:57:09.106 --> 11:57:09.116 align:start position:0% now the network topography and design is 11:57:09.116 --> 11:57:10.550 align:start position:0% now the network topography and design is also<11:57:09.416> pretty<11:57:09.596> important<11:57:09.900> we<11:57:10.140> need<11:57:10.256> to<11:57:10.380> figure 11:57:10.550 --> 11:57:10.560 align:start position:0% also pretty important we need to figure 11:57:10.560 --> 11:57:12.230 align:start position:0% also pretty important we need to figure out<11:57:10.860> how<11:57:11.340> we're<11:57:11.520> going<11:57:11.700> to<11:57:11.880> set<11:57:12.000> up<11:57:12.116> the 11:57:12.230 --> 11:57:12.240 align:start position:0% out how we're going to set up the 11:57:12.240 --> 11:57:13.490 align:start position:0% out how we're going to set up the network<11:57:12.416> we<11:57:12.900> talked<11:57:13.140> about<11:57:13.256> different 11:57:13.490 --> 11:57:13.500 align:start position:0% network we talked about different 11:57:13.500 --> 11:57:16.730 align:start position:0% network we talked about different topographies<11:57:14.220> previously<11:57:14.880> so<11:57:15.660> we<11:57:16.436> probably 11:57:16.730 --> 11:57:16.740 align:start position:0% topographies previously so we probably 11:57:16.740 --> 11:57:18.950 align:start position:0% topographies previously so we probably are<11:57:16.980> going<11:57:17.096> to<11:57:17.220> want<11:57:17.400> some<11:57:17.756> sort<11:57:18.000> of<11:57:18.116> star 11:57:18.950 --> 11:57:18.960 align:start position:0% are going to want some sort of star 11:57:18.960 --> 11:57:20.150 align:start position:0% are going to want some sort of star Network 11:57:20.150 --> 11:57:20.160 align:start position:0% Network 11:57:20.160 --> 11:57:22.550 align:start position:0% Network if<11:57:20.580> you<11:57:20.640> recall<11:57:21.000> what<11:57:21.116> that<11:57:21.300> is<11:57:21.480> we<11:57:22.020> might<11:57:22.200> for 11:57:22.550 --> 11:57:22.560 align:start position:0% if you recall what that is we might for 11:57:22.560 --> 11:57:24.890 align:start position:0% if you recall what that is we might for some<11:57:22.680> reason<11:57:22.916> have<11:57:23.340> a<11:57:23.520> ring<11:57:23.756> if<11:57:24.300> we<11:57:24.540> have<11:57:24.660> a 11:57:24.890 --> 11:57:24.900 align:start position:0% some reason have a ring if we have a 11:57:24.900 --> 11:57:27.106 align:start position:0% some reason have a ring if we have a really<11:57:25.020> intense<11:57:25.500> local<11:57:26.220> area<11:57:26.520> network<11:57:26.820> all 11:57:27.106 --> 11:57:27.116 align:start position:0% really intense local area network all 11:57:27.116 --> 11:57:28.370 align:start position:0% really intense local area network all this<11:57:27.300> is<11:57:27.480> usually<11:57:27.660> going<11:57:27.776> to<11:57:27.900> be<11:57:27.960> used<11:57:28.080> in<11:57:28.256> a 11:57:28.370 --> 11:57:28.380 align:start position:0% this is usually going to be used in a 11:57:28.380 --> 11:57:29.990 align:start position:0% this is usually going to be used in a Wan<11:57:28.616> setting<11:57:28.980> so<11:57:29.400> really<11:57:29.520> what<11:57:29.756> we're<11:57:29.880> going 11:57:29.990 --> 11:57:30.000 align:start position:0% Wan setting so really what we're going 11:57:30.000 --> 11:57:34.190 align:start position:0% Wan setting so really what we're going to<11:57:30.060> see<11:57:30.180> usually<11:57:30.540> is<11:57:30.916> a<11:57:31.916> star 11:57:34.190 --> 11:57:34.200 align:start position:0% to see usually is a star 11:57:34.200 --> 11:57:36.050 align:start position:0% to see usually is a star and<11:57:34.800> as<11:57:34.980> you<11:57:35.096> can<11:57:35.220> see<11:57:35.340> everything<11:57:35.700> is 11:57:36.050 --> 11:57:36.060 align:start position:0% and as you can see everything is 11:57:36.060 --> 11:57:39.230 align:start position:0% and as you can see everything is hardwired<11:57:36.840> and<11:57:37.500> this<11:57:37.800> is<11:57:37.980> a<11:57:38.276> bird's<11:57:38.880> eye<11:57:39.000> view 11:57:39.230 --> 11:57:39.240 align:start position:0% hardwired and this is a bird's eye view 11:57:39.240 --> 11:57:41.746 align:start position:0% hardwired and this is a bird's eye view of<11:57:40.080> how<11:57:40.256> we're<11:57:40.436> going<11:57:40.560> to<11:57:40.680> connect<11:57:40.916> this 11:57:41.746 --> 11:57:41.756 align:start position:0% of how we're going to connect this 11:57:41.756 --> 11:57:44.690 align:start position:0% of how we're going to connect this network 11:57:44.690 --> 11:57:44.700 align:start position:0% 11:57:44.700 --> 11:57:46.906 align:start position:0% so<11:57:45.116> you<11:57:45.240> can<11:57:45.360> see<11:57:45.540> we<11:57:45.900> see<11:57:46.256> each<11:57:46.616> device 11:57:46.906 --> 11:57:46.916 align:start position:0% so you can see we see each device 11:57:46.916 --> 11:57:48.890 align:start position:0% so you can see we see each device plugged<11:57:47.640> up<11:57:47.756> we<11:57:48.180> see<11:57:48.300> where<11:57:48.480> every<11:57:48.660> device 11:57:48.890 --> 11:57:48.900 align:start position:0% plugged up we see where every device 11:57:48.900 --> 11:57:50.746 align:start position:0% plugged up we see where every device plugs<11:57:49.320> in<11:57:49.436> for<11:57:49.680> instance<11:57:49.860> this<11:57:50.160> printer<11:57:50.400> plugs 11:57:50.746 --> 11:57:50.756 align:start position:0% plugs in for instance this printer plugs 11:57:50.756 --> 11:57:52.670 align:start position:0% plugs in for instance this printer plugs up<11:57:50.880> directly<11:57:51.116> to<11:57:51.240> Mike's<11:57:51.596> PC<11:57:51.900> so<11:57:52.380> if<11:57:52.560> you're 11:57:52.670 --> 11:57:52.680 align:start position:0% up directly to Mike's PC so if you're 11:57:52.680 --> 11:57:54.050 align:start position:0% up directly to Mike's PC so if you're having<11:57:52.860> a<11:57:53.040> trouble<11:57:53.276> problem<11:57:53.640> with<11:57:53.936> the 11:57:54.050 --> 11:57:54.060 align:start position:0% having a trouble problem with the 11:57:54.060 --> 11:57:56.450 align:start position:0% having a trouble problem with the printer<11:57:54.360> we<11:57:54.840> know<11:57:54.960> that<11:57:55.200> actually<11:57:55.380> the<11:57:56.096> PC 11:57:56.450 --> 11:57:56.460 align:start position:0% printer we know that actually the PC 11:57:56.460 --> 11:57:58.190 align:start position:0% printer we know that actually the PC could<11:57:56.700> be<11:57:56.880> the<11:57:57.060> problem<11:57:57.240> not<11:57:57.660> necessarily 11:57:58.190 --> 11:57:58.200 align:start position:0% could be the problem not necessarily 11:57:58.200 --> 11:58:00.586 align:start position:0% could be the problem not necessarily this<11:57:58.616> chord<11:57:58.916> here<11:57:59.220> and<11:57:59.700> so<11:57:59.880> knowing<11:58:00.360> where 11:58:00.586 --> 11:58:00.596 align:start position:0% this chord here and so knowing where 11:58:00.596 --> 11:58:02.210 align:start position:0% this chord here and so knowing where everything<11:58:00.720> is<11:58:01.020> set<11:58:01.256> up<11:58:01.380> and<11:58:01.860> how<11:58:02.040> everything 11:58:02.210 --> 11:58:02.220 align:start position:0% everything is set up and how everything 11:58:02.220 --> 11:58:04.850 align:start position:0% everything is set up and how everything is<11:58:02.520> set<11:58:02.756> up<11:58:02.880> is<11:58:03.180> really<11:58:03.540> important<11:58:04.020> as<11:58:04.500> you<11:58:04.680> go 11:58:04.850 --> 11:58:04.860 align:start position:0% is set up is really important as you go 11:58:04.860 --> 11:58:06.710 align:start position:0% is set up is really important as you go forth<11:58:05.220> and<11:58:05.460> of<11:58:05.640> course<11:58:05.700> important<11:58:06.180> before<11:58:06.360> I 11:58:06.710 --> 11:58:06.720 align:start position:0% forth and of course important before I 11:58:06.720 --> 11:58:10.670 align:start position:0% forth and of course important before I start<11:58:06.840> to<11:58:07.276> create<11:58:08.276> a<11:58:08.640> huge<11:58:09.060> Network<11:58:09.500> by<11:58:10.500> the 11:58:10.670 --> 11:58:10.680 align:start position:0% start to create a huge Network by the 11:58:10.680 --> 11:58:12.530 align:start position:0% start to create a huge Network by the way<11:58:10.740> your<11:58:11.096> network<11:58:11.276> and<11:58:11.520> your<11:58:11.756> plan 11:58:12.530 --> 11:58:12.540 align:start position:0% way your network and your plan 11:58:12.540 --> 11:58:14.266 align:start position:0% way your network and your plan probably<11:58:13.020> a<11:58:13.256> lot<11:58:13.320> more<11:58:13.500> complex<11:58:13.800> than<11:58:14.040> this 11:58:14.266 --> 11:58:14.276 align:start position:0% probably a lot more complex than this 11:58:14.276 --> 11:58:16.490 align:start position:0% probably a lot more complex than this but<11:58:14.756> try<11:58:14.936> drawing<11:58:15.300> out<11:58:15.480> your<11:58:15.840> network<11:58:16.080> at<11:58:16.320> home 11:58:16.490 --> 11:58:16.500 align:start position:0% but try drawing out your network at home 11:58:16.500 --> 11:58:19.246 align:start position:0% but try drawing out your network at home and<11:58:16.740> see<11:58:16.860> if<11:58:16.980> you<11:58:17.040> can<11:58:17.160> do<11:58:17.340> it<11:58:17.460> as<11:58:17.640> well 11:58:19.246 --> 11:58:19.256 align:start position:0% and see if you can do it as well 11:58:19.256 --> 11:58:22.190 align:start position:0% and see if you can do it as well now<11:58:19.756> backups<11:58:20.756> are<11:58:21.240> extremely<11:58:21.660> important<11:58:22.020> when 11:58:22.190 --> 11:58:22.200 align:start position:0% now backups are extremely important when 11:58:22.200 --> 11:58:24.890 align:start position:0% now backups are extremely important when I<11:58:22.380> have<11:58:22.560> especially<11:58:23.040> Enterprise<11:58:23.460> setup<11:58:24.180> the 11:58:24.890 --> 11:58:24.900 align:start position:0% I have especially Enterprise setup the 11:58:24.900 --> 11:58:27.170 align:start position:0% I have especially Enterprise setup the loss<11:58:25.200> of<11:58:25.320> data<11:58:25.740> that<11:58:25.980> can<11:58:26.160> occur<11:58:26.580> could<11:58:27.000> take 11:58:27.170 --> 11:58:27.180 align:start position:0% loss of data that can occur could take 11:58:27.180 --> 11:58:29.210 align:start position:0% loss of data that can occur could take us<11:58:27.360> out<11:58:27.720> of<11:58:27.900> operating<11:58:28.380> and<11:58:28.680> if<11:58:28.860> I'm<11:58:28.980> talking 11:58:29.210 --> 11:58:29.220 align:start position:0% us out of operating and if I'm talking 11:58:29.220 --> 11:58:32.390 align:start position:0% us out of operating and if I'm talking about<11:58:29.580> a<11:58:30.116> network<11:58:30.900> that<11:58:31.680> is<11:58:31.800> running<11:58:31.980> Bank 11:58:32.390 --> 11:58:32.400 align:start position:0% about a network that is running Bank 11:58:32.400 --> 11:58:34.970 align:start position:0% about a network that is running Bank information<11:58:32.700> or<11:58:33.300> health<11:58:33.660> care<11:58:33.900> then<11:58:34.560> I<11:58:34.860> really 11:58:34.970 --> 11:58:34.980 align:start position:0% information or health care then I really 11:58:34.980 --> 11:58:37.970 align:start position:0% information or health care then I really need<11:58:35.276> to<11:58:35.580> potentially<11:58:36.180> stop<11:58:36.720> or<11:58:37.020> avoid<11:58:37.500> this 11:58:37.970 --> 11:58:37.980 align:start position:0% need to potentially stop or avoid this 11:58:37.980 --> 11:58:40.130 align:start position:0% need to potentially stop or avoid this critical<11:58:38.276> loss<11:58:38.640> of<11:58:38.700> data<11:58:39.060> so<11:58:39.300> regular<11:58:39.660> backups 11:58:40.130 --> 11:58:40.140 align:start position:0% critical loss of data so regular backups 11:58:40.140 --> 11:58:41.690 align:start position:0% critical loss of data so regular backups are<11:58:40.256> key<11:58:40.616> now<11:58:41.096> there<11:58:41.220> are<11:58:41.340> a<11:58:41.400> lot<11:58:41.520> of<11:58:41.640> different 11:58:41.690 --> 11:58:41.700 align:start position:0% are key now there are a lot of different 11:58:41.700 --> 11:58:43.310 align:start position:0% are key now there are a lot of different ways<11:58:42.000> to<11:58:42.116> do<11:58:42.300> this<11:58:42.480> and<11:58:42.776> we'll<11:58:42.960> talk<11:58:43.140> about 11:58:43.310 --> 11:58:43.320 align:start position:0% ways to do this and we'll talk about 11:58:43.320 --> 11:58:45.766 align:start position:0% ways to do this and we'll talk about specifically<11:58:44.040> some<11:58:44.756> of<11:58:44.936> the<11:58:45.180> difference 11:58:45.766 --> 11:58:45.776 align:start position:0% specifically some of the difference 11:58:45.776 --> 11:58:49.490 align:start position:0% specifically some of the difference between<11:58:46.080> an<11:58:46.320> incremental<11:58:46.916> backup 11:58:49.490 --> 11:58:49.500 align:start position:0% 11:58:49.500 --> 11:58:52.550 align:start position:0% and<11:58:50.040> a<11:58:50.276> differential<11:58:50.700> backup 11:58:52.550 --> 11:58:52.560 align:start position:0% and a differential backup 11:58:52.560 --> 11:58:55.130 align:start position:0% and a differential backup disgusting<11:58:53.160> a<11:58:53.340> plus<11:58:53.520> as<11:58:53.756> well 11:58:55.130 --> 11:58:55.140 align:start position:0% disgusting a plus as well 11:58:55.140 --> 11:58:57.406 align:start position:0% disgusting a plus as well but<11:58:55.860> there<11:58:56.160> are<11:58:56.276> some<11:58:56.400> other<11:58:56.520> Surefire<11:58:57.060> ways 11:58:57.406 --> 11:58:57.416 align:start position:0% but there are some other Surefire ways 11:58:57.416 --> 11:58:59.510 align:start position:0% but there are some other Surefire ways that<11:58:57.540> we<11:58:57.660> want<11:58:57.776> to<11:58:57.900> do<11:58:57.960> this<11:58:58.140> first<11:58:58.380> all<11:58:59.096> users 11:58:59.510 --> 11:58:59.520 align:start position:0% that we want to do this first all users 11:58:59.520 --> 11:59:00.950 align:start position:0% that we want to do this first all users on<11:58:59.640> the<11:58:59.756> networks<11:59:00.060> need<11:59:00.300> to<11:59:00.416> be<11:59:00.480> regularly 11:59:00.950 --> 11:59:00.960 align:start position:0% on the networks need to be regularly 11:59:00.960 --> 11:59:02.450 align:start position:0% on the networks need to be regularly saving<11:59:01.380> and<11:59:01.500> backing<11:59:01.800> up<11:59:01.916> their<11:59:02.096> own<11:59:02.220> work 11:59:02.450 --> 11:59:02.460 align:start position:0% saving and backing up their own work 11:59:02.460 --> 11:59:04.550 align:start position:0% saving and backing up their own work then<11:59:03.180> we<11:59:03.416> might<11:59:03.660> want<11:59:03.776> to<11:59:03.900> have<11:59:04.020> an<11:59:04.320> outside 11:59:04.550 --> 11:59:04.560 align:start position:0% then we might want to have an outside 11:59:04.560 --> 11:59:07.130 align:start position:0% then we might want to have an outside service<11:59:05.160> also<11:59:05.756> taking<11:59:05.936> care<11:59:06.240> of<11:59:06.360> our<11:59:06.540> backups 11:59:07.130 --> 11:59:07.140 align:start position:0% service also taking care of our backups 11:59:07.140 --> 11:59:10.310 align:start position:0% service also taking care of our backups so<11:59:07.916> I<11:59:08.220> might<11:59:08.400> want<11:59:08.640> to<11:59:08.820> have<11:59:08.936> the<11:59:09.116> backup<11:59:09.480> going 11:59:10.310 --> 11:59:10.320 align:start position:0% so I might want to have the backup going 11:59:10.320 --> 11:59:11.210 align:start position:0% so I might want to have the backup going out 11:59:11.210 --> 11:59:11.220 align:start position:0% out 11:59:11.220 --> 11:59:14.570 align:start position:0% out to<11:59:11.520> a<11:59:11.820> cloud<11:59:12.000> or<11:59:12.300> to<11:59:12.416> a<11:59:12.660> Wan<11:59:12.960> in<11:59:13.740> this<11:59:13.860> case<11:59:14.040> I 11:59:14.570 --> 11:59:14.580 align:start position:0% to a cloud or to a Wan in this case I 11:59:14.580 --> 11:59:15.890 align:start position:0% to a cloud or to a Wan in this case I probably<11:59:14.756> have<11:59:15.060> and<11:59:15.240> this<11:59:15.416> computer<11:59:15.596> is 11:59:15.890 --> 11:59:15.900 align:start position:0% probably have and this computer is 11:59:15.900 --> 11:59:18.050 align:start position:0% probably have and this computer is representing<11:59:16.380> My<11:59:16.616> Lan<11:59:16.980> all<11:59:17.756> of<11:59:17.936> the 11:59:18.050 --> 11:59:18.060 align:start position:0% representing My Lan all of the 11:59:18.060 --> 11:59:19.906 align:start position:0% representing My Lan all of the information<11:59:18.240> going<11:59:18.900> to<11:59:19.200> a<11:59:19.320> central<11:59:19.500> service 11:59:19.906 --> 11:59:19.916 align:start position:0% information going to a central service 11:59:19.916 --> 11:59:23.330 align:start position:0% information going to a central service and<11:59:20.580> then<11:59:20.756> going<11:59:21.060> out<11:59:21.300> if<11:59:21.720> I<11:59:21.960> have<11:59:22.080> a<11:59:22.200> server 11:59:23.330 --> 11:59:23.340 align:start position:0% and then going out if I have a server 11:59:23.340 --> 11:59:26.450 align:start position:0% and then going out if I have a server and<11:59:23.936> all<11:59:24.116> of<11:59:24.240> the<11:59:24.360> devices<11:59:24.660> are<11:59:25.080> hooked<11:59:25.380> up 11:59:26.450 --> 11:59:26.460 align:start position:0% and all of the devices are hooked up 11:59:26.460 --> 11:59:28.606 align:start position:0% and all of the devices are hooked up to<11:59:26.936> the<11:59:27.116> server<11:59:27.480> then<11:59:27.900> they're<11:59:28.080> going<11:59:28.256> to<11:59:28.436> feed 11:59:28.606 --> 11:59:28.616 align:start position:0% to the server then they're going to feed 11:59:28.616 --> 11:59:30.766 align:start position:0% to the server then they're going to feed the<11:59:28.860> server<11:59:29.160> with<11:59:29.460> the<11:59:29.640> information<11:59:29.820> once 11:59:30.766 --> 11:59:30.776 align:start position:0% the server with the information once 11:59:30.776 --> 11:59:32.810 align:start position:0% the server with the information once that<11:59:30.900> information<11:59:31.020> is<11:59:31.380> on<11:59:31.560> the<11:59:31.680> server<11:59:31.980> then<11:59:32.580> I 11:59:32.810 --> 11:59:32.820 align:start position:0% that information is on the server then I 11:59:32.820 --> 11:59:34.246 align:start position:0% that information is on the server then I can<11:59:32.936> make<11:59:33.060> sure<11:59:33.240> that<11:59:33.416> battle<11:59:33.596> goes<11:59:34.080> out<11:59:34.140> to 11:59:34.246 --> 11:59:34.256 align:start position:0% can make sure that battle goes out to 11:59:34.256 --> 11:59:36.170 align:start position:0% can make sure that battle goes out to the<11:59:34.436> cloud<11:59:34.560> the<11:59:35.276> important<11:59:35.520> thing<11:59:35.640> is<11:59:35.880> to 11:59:36.170 --> 11:59:36.180 align:start position:0% the cloud the important thing is to 11:59:36.180 --> 11:59:37.670 align:start position:0% the cloud the important thing is to centralize<11:59:36.720> where<11:59:36.960> your<11:59:37.140> information<11:59:37.320> is 11:59:37.670 --> 11:59:37.680 align:start position:0% centralize where your information is 11:59:37.680 --> 11:59:40.370 align:start position:0% centralize where your information is being<11:59:37.860> saved<11:59:38.276> if<11:59:38.936> I<11:59:39.116> have<11:59:39.360> for<11:59:39.660> instance<11:59:39.900> data 11:59:40.370 --> 11:59:40.380 align:start position:0% being saved if I have for instance data 11:59:40.380 --> 11:59:42.650 align:start position:0% being saved if I have for instance data being<11:59:40.500> saved<11:59:41.096> to 11:59:42.650 --> 11:59:42.660 align:start position:0% being saved to 11:59:42.660 --> 11:59:45.050 align:start position:0% being saved to various<11:59:43.616> computers<11:59:44.160> and<11:59:44.460> those<11:59:44.640> computers 11:59:45.050 --> 11:59:45.060 align:start position:0% various computers and those computers 11:59:45.060 --> 11:59:47.266 align:start position:0% various computers and those computers don't<11:59:45.300> have<11:59:45.596> a<11:59:46.020> central<11:59:46.256> place<11:59:46.616> to<11:59:46.916> store<11:59:47.096> all 11:59:47.266 --> 11:59:47.276 align:start position:0% don't have a central place to store all 11:59:47.276 --> 11:59:49.606 align:start position:0% don't have a central place to store all the<11:59:47.460> data<11:59:47.820> then<11:59:48.300> backing<11:59:48.840> up<11:59:49.020> simply<11:59:49.380> the 11:59:49.606 --> 11:59:49.616 align:start position:0% the data then backing up simply the 11:59:49.616 --> 11:59:51.106 align:start position:0% the data then backing up simply the server<11:59:49.916> is<11:59:50.040> not<11:59:50.160> going<11:59:50.276> to<11:59:50.340> do<11:59:50.460> it<11:59:50.520> a<11:59:50.700> map<11:59:50.820> to<11:59:51.000> go 11:59:51.106 --> 11:59:51.116 align:start position:0% server is not going to do it a map to go 11:59:51.116 --> 11:59:52.970 align:start position:0% server is not going to do it a map to go back<11:59:51.240> up<11:59:51.416> every<11:59:51.900> individual<11:59:52.380> computer<11:59:52.616> and 11:59:52.970 --> 11:59:52.980 align:start position:0% back up every individual computer and 11:59:52.980 --> 11:59:54.950 align:start position:0% back up every individual computer and that<11:59:53.096> really<11:59:53.276> doesn't<11:59:53.460> work<11:59:53.820> so<11:59:54.540> what<11:59:54.776> we 11:59:54.950 --> 11:59:54.960 align:start position:0% that really doesn't work so what we 11:59:54.960 --> 11:59:57.230 align:start position:0% that really doesn't work so what we really<11:59:55.140> want<11:59:55.380> to<11:59:55.560> have<11:59:55.740> is<11:59:56.160> a<11:59:56.520> centralized 11:59:57.230 --> 11:59:57.240 align:start position:0% really want to have is a centralized 11:59:57.240 --> 11:59:59.450 align:start position:0% really want to have is a centralized backup<11:59:57.720> system<11:59:58.020> and<11:59:58.616> sometimes<11:59:58.980> we<11:59:59.160> want<11:59:59.340> to 11:59:59.450 --> 11:59:59.460 align:start position:0% backup system and sometimes we want to 11:59:59.460 --> 12:00:02.450 align:start position:0% backup system and sometimes we want to have<11:59:59.700> redundancy 12:00:02.450 --> 12:00:02.460 align:start position:0% have redundancy 12:00:02.460 --> 12:00:04.246 align:start position:0% have redundancy in<12:00:03.180> this<12:00:03.360> system 12:00:04.246 --> 12:00:04.256 align:start position:0% in this system 12:00:04.256 --> 12:00:06.530 align:start position:0% in this system by<12:00:04.680> not<12:00:04.860> only<12:00:04.980> backing<12:00:05.340> it<12:00:05.460> up<12:00:05.580> locally<12:00:05.936> but 12:00:06.530 --> 12:00:06.540 align:start position:0% by not only backing it up locally but 12:00:06.540 --> 12:00:09.290 align:start position:0% by not only backing it up locally but backing<12:00:06.960> it<12:00:07.140> up<12:00:07.320> out<12:00:07.800> to<12:00:08.096> the<12:00:08.340> WAN<12:00:08.700> or 12:00:09.290 --> 12:00:09.300 align:start position:0% backing it up out to the WAN or 12:00:09.300 --> 12:00:10.906 align:start position:0% backing it up out to the WAN or alternatively<12:00:09.840> having<12:00:10.140> tapes<12:00:10.616> that<12:00:10.800> we're 12:00:10.906 --> 12:00:10.916 align:start position:0% alternatively having tapes that we're 12:00:10.916 --> 12:00:13.310 align:start position:0% alternatively having tapes that we're going<12:00:11.096> to<12:00:11.220> take<12:00:11.400> off<12:00:11.880> site<12:00:12.180> in<12:00:12.540> case<12:00:12.840> God 12:00:13.310 --> 12:00:13.320 align:start position:0% going to take off site in case God 12:00:13.320 --> 12:00:15.290 align:start position:0% going to take off site in case God forbid<12:00:13.740> something<12:00:14.040> happened<12:00:14.400> to<12:00:14.756> my<12:00:14.936> backup 12:00:15.290 --> 12:00:15.300 align:start position:0% forbid something happened to my backup 12:00:15.300 --> 12:00:16.850 align:start position:0% forbid something happened to my backup plan 12:00:16.850 --> 12:00:16.860 align:start position:0% plan 12:00:16.860 --> 12:00:19.010 align:start position:0% plan now<12:00:17.520> it's<12:00:17.640> also<12:00:17.880> important<12:00:18.116> that<12:00:18.300> we<12:00:18.480> document 12:00:19.010 --> 12:00:19.020 align:start position:0% now it's also important that we document 12:00:19.020 --> 12:00:20.926 align:start position:0% now it's also important that we document our<12:00:19.436> Network<12:00:19.560> and<12:00:19.860> once<12:00:20.096> we've<12:00:20.340> documented<12:00:20.820> it 12:00:20.926 --> 12:00:20.936 align:start position:0% our Network and once we've documented it 12:00:20.936 --> 12:00:22.670 align:start position:0% our Network and once we've documented it we<12:00:21.116> need<12:00:21.240> to<12:00:21.360> continually<12:00:21.720> audit<12:00:22.256> where<12:00:22.500> our 12:00:22.670 --> 12:00:22.680 align:start position:0% we need to continually audit where our 12:00:22.680 --> 12:00:24.290 align:start position:0% we need to continually audit where our Network's<12:00:23.040> weaknesses<12:00:23.520> and<12:00:23.700> strengths<12:00:24.116> are 12:00:24.290 --> 12:00:24.300 align:start position:0% Network's weaknesses and strengths are 12:00:24.300 --> 12:00:25.850 align:start position:0% Network's weaknesses and strengths are so<12:00:24.596> I<12:00:24.720> want<12:00:24.776> to<12:00:24.900> keep<12:00:25.020> track<12:00:25.200> of<12:00:25.436> everything 12:00:25.850 --> 12:00:25.860 align:start position:0% so I want to keep track of everything 12:00:25.860 --> 12:00:28.670 align:start position:0% so I want to keep track of everything that's<12:00:26.160> on<12:00:26.400> the<12:00:26.580> network<12:00:26.776> including<12:00:27.776> the 12:00:28.670 --> 12:00:28.680 align:start position:0% that's on the network including the 12:00:28.680 --> 12:00:30.670 align:start position:0% that's on the network including the hardware<12:00:28.916> the<12:00:29.520> software 12:00:30.670 --> 12:00:30.680 align:start position:0% hardware the software 12:00:30.680 --> 12:00:33.766 align:start position:0% hardware the software diagrams<12:00:31.680> that<12:00:31.916> we<12:00:32.096> have<12:00:32.340> numbers<12:00:33.180> serial 12:00:33.766 --> 12:00:33.776 align:start position:0% diagrams that we have numbers serial 12:00:33.776 --> 12:00:36.170 align:start position:0% diagrams that we have numbers serial numbers<12:00:34.380> Etc<12:00:34.560> we<12:00:35.276> also<12:00:35.460> need<12:00:35.580> to<12:00:35.700> audit<12:00:36.060> the 12:00:36.170 --> 12:00:36.180 align:start position:0% numbers Etc we also need to audit the 12:00:36.180 --> 12:00:37.730 align:start position:0% numbers Etc we also need to audit the network<12:00:36.300> for<12:00:36.660> security<12:00:36.900> strengths<12:00:37.616> and 12:00:37.730 --> 12:00:37.740 align:start position:0% network for security strengths and 12:00:37.740 --> 12:00:39.650 align:start position:0% network for security strengths and weaknesses<12:00:38.220> we<12:00:38.640> might<12:00:38.820> do<12:00:39.000> this<12:00:39.060> by<12:00:39.300> using<12:00:39.480> a 12:00:39.650 --> 12:00:39.660 align:start position:0% weaknesses we might do this by using a 12:00:39.660 --> 12:00:41.926 align:start position:0% weaknesses we might do this by using a port<12:00:39.776> scanner 12:00:41.926 --> 12:00:41.936 align:start position:0% port scanner 12:00:41.936 --> 12:00:44.450 align:start position:0% port scanner by<12:00:42.660> having<12:00:42.960> some<12:00:43.256> sort<12:00:43.436> of<12:00:43.560> centralized<12:00:43.980> virus 12:00:44.450 --> 12:00:44.460 align:start position:0% by having some sort of centralized virus 12:00:44.460 --> 12:00:46.790 align:start position:0% by having some sort of centralized virus scan<12:00:44.580> program<12:00:44.880> like<12:00:45.116> we'll<12:00:45.300> see<12:00:45.540> in<12:00:45.720> a<12:00:46.680> minute 12:00:46.790 --> 12:00:46.800 align:start position:0% scan program like we'll see in a minute 12:00:46.800 --> 12:00:48.470 align:start position:0% scan program like we'll see in a minute and<12:00:47.220> maybe<12:00:47.340> even<12:00:47.520> by<12:00:47.756> hiring<12:00:48.116> an<12:00:48.300> outside 12:00:48.470 --> 12:00:48.480 align:start position:0% and maybe even by hiring an outside 12:00:48.480 --> 12:00:50.570 align:start position:0% and maybe even by hiring an outside security<12:00:48.840> firm<12:00:49.380> to<12:00:49.560> try<12:00:49.680> to<12:00:49.860> hack<12:00:50.096> into<12:00:50.276> my 12:00:50.570 --> 12:00:50.580 align:start position:0% security firm to try to hack into my 12:00:50.580 --> 12:00:52.906 align:start position:0% security firm to try to hack into my system<12:00:50.820> so<12:00:51.416> I<12:00:51.596> can<12:00:51.720> see<12:00:51.960> where<12:00:52.256> the<12:00:52.436> weaknesses 12:00:52.906 --> 12:00:52.916 align:start position:0% system so I can see where the weaknesses 12:00:52.916 --> 12:00:54.890 align:start position:0% system so I can see where the weaknesses and<12:00:53.160> strengths<12:00:53.580> are 12:00:54.890 --> 12:00:54.900 align:start position:0% and strengths are 12:00:54.900 --> 12:00:57.290 align:start position:0% and strengths are all<12:00:55.740> this<12:00:55.860> information<12:00:56.040> is<12:00:56.520> going<12:00:56.700> to<12:00:56.820> be<12:00:57.000> key 12:00:57.290 --> 12:00:57.300 align:start position:0% all this information is going to be key 12:00:57.300 --> 12:00:59.746 align:start position:0% all this information is going to be key in<12:00:57.900> recovering 12:00:59.746 --> 12:00:59.756 align:start position:0% in recovering 12:00:59.756 --> 12:01:04.190 align:start position:0% in recovering in<12:01:00.300> case<12:01:00.416> of<12:01:00.660> major<12:01:00.960> data<12:01:01.436> loss 12:01:04.190 --> 12:01:04.200 align:start position:0% 12:01:04.200 --> 12:01:05.570 align:start position:0% and<12:01:04.616> that's<12:01:04.680> the<12:01:04.860> reason<12:01:04.980> I<12:01:05.220> want<12:01:05.340> to<12:01:05.460> always 12:01:05.570 --> 12:01:05.580 align:start position:0% and that's the reason I want to always 12:01:05.580 --> 12:01:08.086 align:start position:0% and that's the reason I want to always just<12:01:05.880> keep<12:01:06.180> a<12:01:06.540> nice<12:01:07.080> long<12:01:07.380> paper<12:01:07.800> trail 12:01:08.086 --> 12:01:08.096 align:start position:0% just keep a nice long paper trail 12:01:08.096 --> 12:01:09.350 align:start position:0% just keep a nice long paper trail sometimes<12:01:08.700> you<12:01:08.820> might<12:01:08.936> want<12:01:09.060> to<12:01:09.116> print<12:01:09.240> this 12:01:09.350 --> 12:01:09.360 align:start position:0% sometimes you might want to print this 12:01:09.360 --> 12:01:10.970 align:start position:0% sometimes you might want to print this stuff<12:01:09.540> off<12:01:09.720> too<12:01:09.900> because<12:01:10.200> again<12:01:10.436> the<12:01:10.800> computer 12:01:10.970 --> 12:01:10.980 align:start position:0% stuff off too because again the computer 12:01:10.980 --> 12:01:12.650 align:start position:0% stuff off too because again the computer goes<12:01:11.400> down<12:01:11.460> I<12:01:11.640> can't<12:01:11.820> access<12:01:12.000> anything<12:01:12.416> that's 12:01:12.650 --> 12:01:12.660 align:start position:0% goes down I can't access anything that's 12:01:12.660 --> 12:01:14.810 align:start position:0% goes down I can't access anything that's digital<12:01:13.080> or<12:01:13.500> throw<12:01:13.680> it<12:01:13.860> up<12:01:13.980> in<12:01:14.096> the<12:01:14.220> cloud<12:01:14.340> then 12:01:14.810 --> 12:01:14.820 align:start position:0% digital or throw it up in the cloud then 12:01:14.820 --> 12:01:17.030 align:start position:0% digital or throw it up in the cloud then I<12:01:15.000> don't<12:01:15.116> have<12:01:15.240> to<12:01:15.360> worry<12:01:15.540> about<12:01:15.776> it 12:01:17.030 --> 12:01:17.040 align:start position:0% I don't have to worry about it 12:01:17.040 --> 12:01:18.710 align:start position:0% I don't have to worry about it now<12:01:17.700> when<12:01:17.820> we<12:01:17.936> kept<12:01:18.240> the<12:01:18.300> management<12:01:18.416> and 12:01:18.710 --> 12:01:18.720 align:start position:0% now when we kept the management and 12:01:18.720 --> 12:01:19.850 align:start position:0% now when we kept the management and troubleshooting<12:01:19.256> we<12:01:19.380> always<12:01:19.500> want<12:01:19.680> to<12:01:19.800> make 12:01:19.850 --> 12:01:19.860 align:start position:0% troubleshooting we always want to make 12:01:19.860 --> 12:01:22.070 align:start position:0% troubleshooting we always want to make sure<12:01:19.980> the<12:01:20.160> network<12:01:20.340> is<12:01:20.640> running<12:01:20.900> smoothly<12:01:21.900> and 12:01:22.070 --> 12:01:22.080 align:start position:0% sure the network is running smoothly and 12:01:22.080 --> 12:01:23.810 align:start position:0% sure the network is running smoothly and since<12:01:22.256> you're<12:01:22.436> the<12:01:22.680> administrator<12:01:23.220> you're 12:01:23.810 --> 12:01:23.820 align:start position:0% since you're the administrator you're 12:01:23.820 --> 12:01:25.790 align:start position:0% since you're the administrator you're the<12:01:24.000> person<12:01:24.116> who<12:01:24.360> has<12:01:24.480> to<12:01:24.596> be<12:01:24.720> monitoring<12:01:25.320> and 12:01:25.790 --> 12:01:25.800 align:start position:0% the person who has to be monitoring and 12:01:25.800 --> 12:01:27.710 align:start position:0% the person who has to be monitoring and managing<12:01:26.160> everything<12:01:26.400> that's<12:01:26.640> going<12:01:26.880> on<12:01:27.060> now 12:01:27.710 --> 12:01:27.720 align:start position:0% managing everything that's going on now 12:01:27.720 --> 12:01:29.630 align:start position:0% managing everything that's going on now when<12:01:27.900> there<12:01:28.140> are<12:01:28.256> issues<12:01:28.800> you<12:01:29.340> want<12:01:29.520> to 12:01:29.630 --> 12:01:29.640 align:start position:0% when there are issues you want to 12:01:29.640 --> 12:01:31.190 align:start position:0% when there are issues you want to troubleshoot<12:01:30.240> and<12:01:30.360> solve<12:01:30.660> the<12:01:30.776> issues<12:01:31.020> where 12:01:31.190 --> 12:01:31.200 align:start position:0% troubleshoot and solve the issues where 12:01:31.200 --> 12:01:34.070 align:start position:0% troubleshoot and solve the issues where they<12:01:31.380> arise<12:01:31.740> using<12:01:32.400> the<12:01:32.520> OSI<12:01:32.936> model<12:01:33.300> can<12:01:33.960> be 12:01:34.070 --> 12:01:34.080 align:start position:0% they arise using the OSI model can be 12:01:34.080 --> 12:01:35.746 align:start position:0% they arise using the OSI model can be really<12:01:34.320> helpful<12:01:34.680> in<12:01:34.916> this<12:01:35.096> case<12:01:35.276> because<12:01:35.520> you 12:01:35.746 --> 12:01:35.756 align:start position:0% really helpful in this case because you 12:01:35.756 --> 12:01:37.490 align:start position:0% really helpful in this case because you can<12:01:35.936> determine<12:01:36.416> where<12:01:36.900> the<12:01:37.140> issue<12:01:37.380> is 12:01:37.490 --> 12:01:37.500 align:start position:0% can determine where the issue is 12:01:37.500 --> 12:01:39.586 align:start position:0% can determine where the issue is occurring<12:01:37.916> for<12:01:38.580> instance<12:01:38.756> if<12:01:39.000> I'm<12:01:39.116> having<12:01:39.360> a 12:01:39.586 --> 12:01:39.596 align:start position:0% occurring for instance if I'm having a 12:01:39.596 --> 12:01:43.010 align:start position:0% occurring for instance if I'm having a trouble<12:01:39.776> getting<12:01:40.500> out<12:01:40.740> to<12:01:41.276> a<12:01:42.180> certain<12:01:42.540> website 12:01:43.010 --> 12:01:43.020 align:start position:0% trouble getting out to a certain website 12:01:43.020 --> 12:01:44.990 align:start position:0% trouble getting out to a certain website but<12:01:43.320> everyone<12:01:43.500> seems<12:01:44.040> to<12:01:44.096> be<12:01:44.220> getting<12:01:44.460> out<12:01:44.700> to 12:01:44.990 --> 12:01:45.000 align:start position:0% but everyone seems to be getting out to 12:01:45.000 --> 12:01:47.390 align:start position:0% but everyone seems to be getting out to information<12:01:45.300> then<12:01:46.200> maybe<12:01:46.380> the<12:01:46.616> DNS<12:01:47.040> is<12:01:47.220> the 12:01:47.390 --> 12:01:47.400 align:start position:0% information then maybe the DNS is the 12:01:47.400 --> 12:01:49.670 align:start position:0% information then maybe the DNS is the problem<12:01:47.580> if<12:01:48.240> for<12:01:48.416> instance<12:01:48.660> new<12:01:49.080> devices 12:01:49.670 --> 12:01:49.680 align:start position:0% problem if for instance new devices 12:01:49.680 --> 12:01:51.350 align:start position:0% problem if for instance new devices can't<12:01:50.096> get<12:01:50.276> on<12:01:50.400> the<12:01:50.520> network<12:01:50.640> but<12:01:50.936> if<12:01:51.116> I 12:01:51.350 --> 12:01:51.360 align:start position:0% can't get on the network but if I 12:01:51.360 --> 12:01:53.086 align:start position:0% can't get on the network but if I manually<12:01:51.660> assign<12:01:52.080> them<12:01:52.200> an<12:01:52.380> IP<12:01:52.616> address<12:01:52.800> it 12:01:53.086 --> 12:01:53.096 align:start position:0% manually assign them an IP address it 12:01:53.096 --> 12:01:55.130 align:start position:0% manually assign them an IP address it does<12:01:53.276> work<12:01:53.520> well<12:01:53.936> then<12:01:54.116> probably<12:01:54.300> my<12:01:54.540> DHCP 12:01:55.130 --> 12:01:55.140 align:start position:0% does work well then probably my DHCP 12:01:55.140 --> 12:01:58.426 align:start position:0% does work well then probably my DHCP server<12:01:55.560> is<12:01:55.740> is<12:01:56.220> getting<12:01:57.000> funky<12:01:57.480> again<12:01:58.080> this<12:01:58.380> is 12:01:58.426 --> 12:01:58.436 align:start position:0% server is is getting funky again this is 12:01:58.436 --> 12:01:59.630 align:start position:0% server is is getting funky again this is just<12:01:58.616> an<12:01:58.740> overview<12:01:59.040> we're<12:01:59.340> going<12:01:59.460> to<12:01:59.520> talk 12:01:59.630 --> 12:01:59.640 align:start position:0% just an overview we're going to talk 12:01:59.640 --> 12:02:01.370 align:start position:0% just an overview we're going to talk about<12:01:59.756> all<12:02:00.000> this<12:02:00.180> in<12:02:00.360> more<12:02:00.540> specifics<12:02:01.080> as<12:02:01.200> we 12:02:01.370 --> 12:02:01.380 align:start position:0% about all this in more specifics as we 12:02:01.380 --> 12:02:02.690 align:start position:0% about all this in more specifics as we go<12:02:01.560> forward 12:02:02.690 --> 12:02:02.700 align:start position:0% go forward 12:02:02.700 --> 12:02:04.370 align:start position:0% go forward so<12:02:03.116> I<12:02:03.300> need<12:02:03.416> to<12:02:03.540> take<12:02:03.660> a<12:02:03.776> look<12:02:03.900> at<12:02:04.020> what<12:02:04.200> the 12:02:04.370 --> 12:02:04.380 align:start position:0% so I need to take a look at what the 12:02:04.380 --> 12:02:05.926 align:start position:0% so I need to take a look at what the error<12:02:04.616> is<12:02:04.740> figure<12:02:05.040> out<12:02:05.220> what<12:02:05.400> the<12:02:05.580> problem<12:02:05.700> is 12:02:05.926 --> 12:02:05.936 align:start position:0% error is figure out what the problem is 12:02:05.936 --> 12:02:09.106 align:start position:0% error is figure out what the problem is and<12:02:06.840> get<12:02:07.256> to<12:02:07.500> the<12:02:07.740> root<12:02:08.096> issue<12:02:08.460> especially 12:02:09.106 --> 12:02:09.116 align:start position:0% and get to the root issue especially 12:02:09.116 --> 12:02:10.550 align:start position:0% and get to the root issue especially because<12:02:09.360> what<12:02:09.720> I'm<12:02:09.840> really<12:02:09.960> going<12:02:10.200> for<12:02:10.380> here 12:02:10.550 --> 12:02:10.560 align:start position:0% because what I'm really going for here 12:02:10.560 --> 12:02:12.586 align:start position:0% because what I'm really going for here is<12:02:10.740> what's<12:02:10.916> called<12:02:11.160> five<12:02:11.520> nines<12:02:11.936> which<12:02:12.360> means 12:02:12.586 --> 12:02:12.596 align:start position:0% is what's called five nines which means 12:02:12.596 --> 12:02:14.230 align:start position:0% is what's called five nines which means I<12:02:12.720> want<12:02:12.840> to<12:02:12.960> be<12:02:13.080> up 12:02:14.230 --> 12:02:14.240 align:start position:0% I want to be up 12:02:14.240 --> 12:02:17.050 align:start position:0% I want to be up 99.999<12:02:15.240> of<12:02:16.140> the<12:02:16.320> time 12:02:17.050 --> 12:02:17.060 align:start position:0% 99.999 of the time 12:02:17.060 --> 12:02:19.790 align:start position:0% 99.999 of the time that's<12:02:18.060> like<12:02:18.240> five<12:02:18.540> minutes<12:02:18.776> of<12:02:19.020> downtime<12:02:19.436> per 12:02:19.790 --> 12:02:19.800 align:start position:0% that's like five minutes of downtime per 12:02:19.800 --> 12:02:22.246 align:start position:0% that's like five minutes of downtime per year<12:02:19.980> that<12:02:20.520> five<12:02:20.756> minutes<12:02:21.000> however<12:02:21.480> can<12:02:21.960> be 12:02:22.246 --> 12:02:22.256 align:start position:0% year that five minutes however can be 12:02:22.256 --> 12:02:24.710 align:start position:0% year that five minutes however can be really<12:02:22.616> a<12:02:22.980> big<12:02:23.220> issue<12:02:23.640> this<12:02:24.116> also<12:02:24.416> means<12:02:24.596> I 12:02:24.710 --> 12:02:24.720 align:start position:0% really a big issue this also means I 12:02:24.720 --> 12:02:26.570 align:start position:0% really a big issue this also means I want<12:02:24.840> to<12:02:24.960> be<12:02:25.020> updating<12:02:25.436> with<12:02:25.800> Windows<12:02:26.160> updates 12:02:26.570 --> 12:02:26.580 align:start position:0% want to be updating with Windows updates 12:02:26.580 --> 12:02:28.426 align:start position:0% want to be updating with Windows updates and<12:02:27.116> I<12:02:27.240> want<12:02:27.360> to<12:02:27.480> be<12:02:27.540> providing<12:02:28.020> as<12:02:28.256> much 12:02:28.426 --> 12:02:28.436 align:start position:0% and I want to be providing as much 12:02:28.436 --> 12:02:31.310 align:start position:0% and I want to be providing as much information<12:02:28.740> as<12:02:29.160> possible<12:02:29.720> to<12:02:30.720> my<12:02:31.200> network 12:02:31.310 --> 12:02:31.320 align:start position:0% information as possible to my network 12:02:31.320 --> 12:02:33.730 align:start position:0% information as possible to my network and<12:02:31.616> my<12:02:31.800> network<12:02:31.916> staff<12:02:32.276> and<12:02:32.580> even<12:02:32.700> the 12:02:33.730 --> 12:02:33.740 align:start position:0% and my network staff and even the 12:02:33.740 --> 12:02:35.810 align:start position:0% and my network staff and even the individuals<12:02:34.740> who<12:02:34.916> are<12:02:35.096> using<12:02:35.276> the<12:02:35.400> network<12:02:35.520> as 12:02:35.810 --> 12:02:35.820 align:start position:0% individuals who are using the network as 12:02:35.820 --> 12:02:37.490 align:start position:0% individuals who are using the network as possible 12:02:37.490 --> 12:02:37.500 align:start position:0% possible 12:02:37.500 --> 12:02:39.170 align:start position:0% possible finally<12:02:37.980> when<12:02:38.096> it<12:02:38.276> comes<12:02:38.400> to<12:02:38.580> security<12:02:38.756> and 12:02:39.170 --> 12:02:39.180 align:start position:0% finally when it comes to security and 12:02:39.180 --> 12:02:41.086 align:start position:0% finally when it comes to security and virus<12:02:39.480> protection<12:02:39.840> I<12:02:40.500> want<12:02:40.616> to<12:02:40.740> make<12:02:40.800> sure<12:02:40.980> to 12:02:41.086 --> 12:02:41.096 align:start position:0% virus protection I want to make sure to 12:02:41.096 --> 12:02:43.190 align:start position:0% virus protection I want to make sure to audit<12:02:41.460> and<12:02:41.640> protect<12:02:42.060> prevent<12:02:42.660> the<12:02:42.840> attacks 12:02:43.190 --> 12:02:43.200 align:start position:0% audit and protect prevent the attacks 12:02:43.200 --> 12:02:44.870 align:start position:0% audit and protect prevent the attacks before<12:02:43.320> they<12:02:43.616> can<12:02:43.740> happen<12:02:43.916> so<12:02:44.520> I'm<12:02:44.700> going<12:02:44.820> to 12:02:44.870 --> 12:02:44.880 align:start position:0% before they can happen so I'm going to 12:02:44.880 --> 12:02:47.330 align:start position:0% before they can happen so I'm going to audit<12:02:45.180> it<12:02:45.416> and<12:02:45.840> once<12:02:46.020> I<12:02:46.140> audit<12:02:46.436> I<12:02:46.680> can<12:02:46.860> see<12:02:47.040> what 12:02:47.330 --> 12:02:47.340 align:start position:0% audit it and once I audit I can see what 12:02:47.340 --> 12:02:49.130 align:start position:0% audit it and once I audit I can see what sort<12:02:47.460> of<12:02:47.580> the<12:02:47.700> issues<12:02:48.000> are<12:02:48.180> if<12:02:48.660> I<12:02:48.776> notice<12:02:49.020> that 12:02:49.130 --> 12:02:49.140 align:start position:0% sort of the issues are if I notice that 12:02:49.140 --> 12:02:50.990 align:start position:0% sort of the issues are if I notice that there's<12:02:49.320> no<12:02:49.560> Virus<12:02:49.980> Protection<12:02:50.340> Program<12:02:50.640> then 12:02:50.990 --> 12:02:51.000 align:start position:0% there's no Virus Protection Program then 12:02:51.000 --> 12:02:52.550 align:start position:0% there's no Virus Protection Program then I'm<12:02:51.116> going<12:02:51.240> to<12:02:51.360> want<12:02:51.480> to<12:02:51.540> use<12:02:51.660> some<12:02:51.900> antivirus 12:02:52.550 --> 12:02:52.560 align:start position:0% I'm going to want to use some antivirus 12:02:52.560 --> 12:02:56.266 align:start position:0% I'm going to want to use some antivirus software<12:02:52.980> if<12:02:53.700> I<12:02:53.820> notice<12:02:54.180> that<12:02:55.040> there<12:02:56.040> are<12:02:56.160> open 12:02:56.266 --> 12:02:56.276 align:start position:0% software if I notice that there are open 12:02:56.276 --> 12:02:59.030 align:start position:0% software if I notice that there are open ports<12:02:56.936> getting<12:02:57.540> out<12:02:57.776> to<12:02:57.960> the<12:02:58.140> server<12:02:58.436> through 12:02:59.030 --> 12:02:59.040 align:start position:0% ports getting out to the server through 12:02:59.040 --> 12:03:00.586 align:start position:0% ports getting out to the server through the<12:02:59.276> firewall<12:02:59.700> then<12:03:00.060> I'm<12:03:00.240> going<12:03:00.300> to<12:03:00.416> want<12:03:00.480> to 12:03:00.586 --> 12:03:00.596 align:start position:0% the firewall then I'm going to want to 12:03:00.596 --> 12:03:01.790 align:start position:0% the firewall then I'm going to want to use<12:03:00.660> that<12:03:00.840> if<12:03:00.960> I<12:03:01.080> notice<12:03:01.320> there<12:03:01.436> isn't<12:03:01.680> a 12:03:01.790 --> 12:03:01.800 align:start position:0% use that if I notice there isn't a 12:03:01.800 --> 12:03:03.290 align:start position:0% use that if I notice there isn't a firewall<12:03:02.220> I'm<12:03:02.640> going<12:03:02.756> to<12:03:02.880> want<12:03:02.936> to<12:03:03.060> have<12:03:03.180> to 12:03:03.290 --> 12:03:03.300 align:start position:0% firewall I'm going to want to have to 12:03:03.300 --> 12:03:05.690 align:start position:0% firewall I'm going to want to have to put<12:03:03.540> a<12:03:03.660> firewall<12:03:04.080> up<12:03:04.320> so<12:03:04.860> basically<12:03:05.220> all<12:03:05.580> the 12:03:05.690 --> 12:03:05.700 align:start position:0% put a firewall up so basically all the 12:03:05.700 --> 12:03:08.030 align:start position:0% put a firewall up so basically all the things<12:03:05.936> I<12:03:06.240> can<12:03:06.360> do<12:03:06.540> there's<12:03:06.720> no<12:03:07.020> one<12:03:07.256> size<12:03:07.616> fits 12:03:08.030 --> 12:03:08.040 align:start position:0% things I can do there's no one size fits 12:03:08.040 --> 12:03:09.350 align:start position:0% things I can do there's no one size fits all<12:03:08.096> practice<12:03:08.400> what<12:03:08.700> you<12:03:08.880> really<12:03:09.000> have<12:03:09.116> to<12:03:09.240> do 12:03:09.350 --> 12:03:09.360 align:start position:0% all practice what you really have to do 12:03:09.360 --> 12:03:11.390 align:start position:0% all practice what you really have to do is<12:03:09.480> use<12:03:09.720> the<12:03:09.960> skills<12:03:10.256> that<12:03:10.380> you<12:03:10.560> have<12:03:10.740> in<12:03:11.276> order 12:03:11.390 --> 12:03:11.400 align:start position:0% is use the skills that you have in order 12:03:11.400 --> 12:03:14.266 align:start position:0% is use the skills that you have in order to<12:03:11.820> audit<12:03:12.660> the<12:03:12.840> system<12:03:13.020> and<12:03:13.560> then<12:03:13.680> prevent<12:03:14.096> the 12:03:14.266 --> 12:03:14.276 align:start position:0% to audit the system and then prevent the 12:03:14.276 --> 12:03:16.070 align:start position:0% to audit the system and then prevent the attacks<12:03:14.640> before<12:03:14.756> they<12:03:15.060> happen<12:03:15.240> using<12:03:15.960> a 12:03:16.070 --> 12:03:16.080 align:start position:0% attacks before they happen using a 12:03:16.080 --> 12:03:17.870 align:start position:0% attacks before they happen using a number<12:03:16.200> of<12:03:16.320> different<12:03:16.560> tools<12:03:17.040> might<12:03:17.520> even<12:03:17.640> use 12:03:17.870 --> 12:03:17.880 align:start position:0% number of different tools might even use 12:03:17.880 --> 12:03:20.390 align:start position:0% number of different tools might even use something<12:03:18.060> called<12:03:18.300> an<12:03:18.540> IPS<12:03:18.840> or<12:03:19.140> IDs<12:03:19.680> which 12:03:20.390 --> 12:03:20.400 align:start position:0% something called an IPS or IDs which 12:03:20.400 --> 12:03:22.510 align:start position:0% something called an IPS or IDs which would<12:03:20.580> be<12:03:20.776> uh 12:03:22.510 --> 12:03:22.520 align:start position:0% would be uh 12:03:22.520 --> 12:03:24.766 align:start position:0% would be uh intrusion<12:03:23.520> protection<12:03:24.000> or<12:03:24.240> intrusion 12:03:24.766 --> 12:03:24.776 align:start position:0% intrusion protection or intrusion 12:03:24.776 --> 12:03:28.606 align:start position:0% intrusion protection or intrusion detection<12:03:25.320> service<12:03:26.220> or<12:03:27.180> scanner 12:03:28.606 --> 12:03:28.616 align:start position:0% detection service or scanner 12:03:28.616 --> 12:03:30.470 align:start position:0% detection service or scanner all<12:03:29.040> right<12:03:29.220> so<12:03:29.340> just<12:03:29.580> to<12:03:29.700> go<12:03:29.880> back<12:03:30.000> over<12:03:30.240> this 12:03:30.470 --> 12:03:30.480 align:start position:0% all right so just to go back over this 12:03:30.480 --> 12:03:32.570 align:start position:0% all right so just to go back over this it<12:03:30.660> was<12:03:30.840> a<12:03:30.960> very<12:03:31.080> broad<12:03:31.320> overview<12:03:31.800> of<12:03:32.276> what<12:03:32.400> a 12:03:32.570 --> 12:03:32.580 align:start position:0% it was a very broad overview of what a 12:03:32.580 --> 12:03:34.070 align:start position:0% it was a very broad overview of what a local<12:03:32.700> area<12:03:32.880> network<12:03:33.116> is<12:03:33.416> and<12:03:33.776> some<12:03:33.900> of<12:03:34.080> the 12:03:34.070 --> 12:03:34.080 align:start position:0% local area network is and some of the 12:03:34.080 --> 12:03:35.510 align:start position:0% local area network is and some of the things<12:03:34.256> that<12:03:34.500> we<12:03:34.616> need<12:03:34.740> to<12:03:34.860> do<12:03:34.980> in<12:03:35.160> setting<12:03:35.460> up 12:03:35.510 --> 12:03:35.520 align:start position:0% things that we need to do in setting up 12:03:35.520 --> 12:03:37.370 align:start position:0% things that we need to do in setting up maintaining<12:03:36.060> a<12:03:36.180> land<12:03:36.360> including<12:03:37.080> creating 12:03:37.370 --> 12:03:37.380 align:start position:0% maintaining a land including creating 12:03:37.380 --> 12:03:39.710 align:start position:0% maintaining a land including creating and<12:03:37.680> having<12:03:37.980> a<12:03:38.220> network<12:03:38.340> plan<12:03:38.720> performing 12:03:39.710 --> 12:03:39.720 align:start position:0% and having a network plan performing 12:03:39.720 --> 12:03:42.106 align:start position:0% and having a network plan performing regular<12:03:40.080> backups<12:03:40.680> providing<12:03:41.460> documentation 12:03:42.106 --> 12:03:42.116 align:start position:0% regular backups providing documentation 12:03:42.116 --> 12:03:44.050 align:start position:0% regular backups providing documentation keeping<12:03:42.776> holding<12:03:43.140> on<12:03:43.200> to<12:03:43.380> that<12:03:43.500> documentation 12:03:44.050 --> 12:03:44.060 align:start position:0% keeping holding on to that documentation 12:03:44.060 --> 12:03:46.490 align:start position:0% keeping holding on to that documentation auditing<12:03:45.060> our<12:03:45.180> Network<12:03:45.416> to<12:03:45.840> identify 12:03:46.490 --> 12:03:46.500 align:start position:0% auditing our Network to identify 12:03:46.500 --> 12:03:48.406 align:start position:0% auditing our Network to identify weaknesses<12:03:47.160> which<12:03:47.520> is<12:03:47.700> the<12:03:47.820> main<12:03:47.936> reason<12:03:48.116> for 12:03:48.406 --> 12:03:48.416 align:start position:0% weaknesses which is the main reason for 12:03:48.416 --> 12:03:50.690 align:start position:0% weaknesses which is the main reason for an<12:03:48.540> audit<12:03:48.840> we<12:03:49.436> also<12:03:49.680> might<12:03:49.800> want<12:03:50.040> to<12:03:50.276> use<12:03:50.460> the 12:03:50.690 --> 12:03:50.700 align:start position:0% an audit we also might want to use the 12:03:50.700 --> 12:03:51.790 align:start position:0% an audit we also might want to use the audit<12:03:51.060> to 12:03:51.790 --> 12:03:51.800 align:start position:0% audit to 12:03:51.800 --> 12:03:56.150 align:start position:0% audit to identify<12:03:52.800> bottlenecks<12:03:53.756> or<12:03:54.560> slow<12:03:55.560> issues<12:03:56.040> that 12:03:56.150 --> 12:03:56.160 align:start position:0% identify bottlenecks or slow issues that 12:03:56.160 --> 12:04:00.766 align:start position:0% identify bottlenecks or slow issues that are<12:03:56.276> going<12:03:56.400> to<12:03:56.460> cause<12:03:56.640> speed<12:03:57.060> issues 12:04:00.766 --> 12:04:00.776 align:start position:0% 12:04:00.776 --> 12:04:02.990 align:start position:0% so<12:04:01.320> on<12:04:01.500> and<12:04:01.860> then<12:04:01.980> of<12:04:02.096> course<12:04:02.220> having<12:04:02.520> proper 12:04:02.990 --> 12:04:03.000 align:start position:0% so on and then of course having proper 12:04:03.000 --> 12:04:05.150 align:start position:0% so on and then of course having proper security<12:04:03.180> such<12:04:03.660> as<12:04:03.840> virus<12:04:04.500> scan<12:04:04.680> programs 12:04:05.150 --> 12:04:05.160 align:start position:0% security such as virus scan programs 12:04:05.160 --> 12:04:07.426 align:start position:0% security such as virus scan programs intrusion<12:04:05.936> detection<12:04:06.300> prevention<12:04:06.900> systems 12:04:07.426 --> 12:04:07.436 align:start position:0% intrusion detection prevention systems 12:04:07.436 --> 12:04:09.766 align:start position:0% intrusion detection prevention systems firewalls<12:04:08.400> and<12:04:08.520> so<12:04:08.700> on<12:04:08.820> we're<12:04:09.416> going<12:04:09.540> to<12:04:09.660> talk 12:04:09.766 --> 12:04:09.776 align:start position:0% firewalls and so on we're going to talk 12:04:09.776 --> 12:04:11.570 align:start position:0% firewalls and so on we're going to talk all<12:04:09.960> about<12:04:10.200> this<12:04:10.500> and<12:04:10.860> more<12:04:11.040> in<12:04:11.340> the<12:04:11.520> coming 12:04:11.570 --> 12:04:11.580 align:start position:0% all about this and more in the coming 12:04:11.580 --> 12:04:13.190 align:start position:0% all about this and more in the coming lessons<12:04:12.116> but<12:04:12.480> this<12:04:12.660> was<12:04:12.776> just<12:04:12.900> a<12:04:13.020> broad 12:04:13.190 --> 12:04:13.200 align:start position:0% lessons but this was just a broad 12:04:13.200 --> 12:04:19.650 align:start position:0% lessons but this was just a broad overview<12:04:13.560> to<12:04:13.980> get<12:04:14.096> a<12:04:14.220> sort<12:04:14.460> of<12:04:14.580> set<12:04:14.756> up 12:04:19.650 --> 12:04:19.660 align:start position:0% 12:04:19.660 --> 12:04:28.330 align:start position:0% [Music] 12:04:28.330 --> 12:04:28.340 align:start position:0% [Music] 12:04:28.340 --> 12:04:41.990 align:start position:0% [Music] thank<12:04:29.340> you 12:04:41.990 --> 12:04:42.000 align:start position:0% 12:04:42.000 --> 12:04:45.830 align:start position:0% local<12:04:42.480> area<12:04:42.776> networks<12:04:43.500> switching 12:04:45.830 --> 12:04:45.840 align:start position:0% local area networks switching 12:04:45.840 --> 12:04:47.690 align:start position:0% local area networks switching so<12:04:46.256> in<12:04:46.500> the<12:04:46.560> last<12:04:46.680> module<12:04:47.096> we<12:04:47.400> talked<12:04:47.580> about 12:04:47.690 --> 12:04:47.700 align:start position:0% so in the last module we talked about 12:04:47.700 --> 12:04:49.970 align:start position:0% so in the last module we talked about local<12:04:48.060> area<12:04:48.300> networks<12:04:48.840> in<12:04:49.020> general<12:04:49.200> what<12:04:49.800> they 12:04:49.970 --> 12:04:49.980 align:start position:0% local area networks in general what they 12:04:49.980 --> 12:04:52.010 align:start position:0% local area networks in general what they do<12:04:50.096> how<12:04:50.400> we<12:04:50.520> set<12:04:50.700> them<12:04:50.880> up<12:04:51.060> how<12:04:51.540> we<12:04:51.660> administer 12:04:52.010 --> 12:04:52.020 align:start position:0% do how we set them up how we administer 12:04:52.020 --> 12:04:55.070 align:start position:0% do how we set them up how we administer them<12:04:52.320> but<12:04:53.276> in<12:04:53.640> order<12:04:53.820> to<12:04:54.000> have<12:04:54.180> a<12:04:54.480> functioning 12:04:55.070 --> 12:04:55.080 align:start position:0% them but in order to have a functioning 12:04:55.080 --> 12:04:57.586 align:start position:0% them but in order to have a functioning local<12:04:55.616> area<12:04:55.980> network<12:04:56.460> one<12:04:57.240> of<12:04:57.360> the<12:04:57.416> most 12:04:57.586 --> 12:04:57.596 align:start position:0% local area network one of the most 12:04:57.596 --> 12:05:00.406 align:start position:0% local area network one of the most important<12:04:58.560> developments<12:04:59.520> that<12:04:59.700> we<12:04:59.880> had<12:05:00.000> was 12:05:00.406 --> 12:05:00.416 align:start position:0% important developments that we had was 12:05:00.416 --> 12:05:02.746 align:start position:0% important developments that we had was called<12:05:00.660> switching<12:05:01.200> if<12:05:01.860> you<12:05:01.980> recall<12:05:02.340> earlier 12:05:02.746 --> 12:05:02.756 align:start position:0% called switching if you recall earlier 12:05:02.756 --> 12:05:05.390 align:start position:0% called switching if you recall earlier on<12:05:02.936> we<12:05:03.360> talked<12:05:03.540> about<12:05:03.660> the<12:05:03.840> OSI<12:05:04.256> model<12:05:04.500> and<12:05:05.160> if 12:05:05.390 --> 12:05:05.400 align:start position:0% on we talked about the OSI model and if 12:05:05.400 --> 12:05:07.670 align:start position:0% on we talked about the OSI model and if you<12:05:05.520> recall<12:05:05.880> the<12:05:06.416> OSI<12:05:06.840> model<12:05:07.020> went<12:05:07.256> from<12:05:07.436> level 12:05:07.670 --> 12:05:07.680 align:start position:0% you recall the OSI model went from level 12:05:07.680 --> 12:05:12.470 align:start position:0% you recall the OSI model went from level one<12:05:08.340> all<12:05:09.116> the<12:05:09.240> way<12:05:09.240> up<12:05:09.416> to<12:05:09.596> level<12:05:09.776> seven 12:05:12.470 --> 12:05:12.480 align:start position:0% one all the way up to level seven 12:05:12.480 --> 12:05:15.530 align:start position:0% one all the way up to level seven now<12:05:13.080> level<12:05:13.320> one<12:05:13.560> was<12:05:13.800> the<12:05:13.980> physical<12:05:14.160> layer<12:05:15.116> and 12:05:15.530 --> 12:05:15.540 align:start position:0% now level one was the physical layer and 12:05:15.540 --> 12:05:17.926 align:start position:0% now level one was the physical layer and on<12:05:15.720> there<12:05:15.900> we<12:05:16.560> talked<12:05:16.916> briefly<12:05:17.400> about<12:05:17.640> a 12:05:17.926 --> 12:05:17.936 align:start position:0% on there we talked briefly about a 12:05:17.936 --> 12:05:20.390 align:start position:0% on there we talked briefly about a device<12:05:18.116> called<12:05:18.776> a<12:05:18.960> hub 12:05:20.390 --> 12:05:20.400 align:start position:0% device called a hub 12:05:20.400 --> 12:05:22.550 align:start position:0% device called a hub now<12:05:20.936> the<12:05:21.240> problem<12:05:21.360> with<12:05:21.596> the<12:05:21.840> Hub<12:05:21.960> was 12:05:22.550 --> 12:05:22.560 align:start position:0% now the problem with the Hub was 12:05:22.560 --> 12:05:24.650 align:start position:0% now the problem with the Hub was whenever<12:05:22.916> data 12:05:24.650 --> 12:05:24.660 align:start position:0% whenever data 12:05:24.660 --> 12:05:28.370 align:start position:0% whenever data went<12:05:25.140> from<12:05:25.436> one<12:05:25.680> computer<12:05:26.116> into<12:05:27.116> the<12:05:27.416> Hub 12:05:28.370 --> 12:05:28.380 align:start position:0% went from one computer into the Hub 12:05:28.380 --> 12:05:31.790 align:start position:0% went from one computer into the Hub The<12:05:28.800> Hub<12:05:28.860> spouted<12:05:29.460> all<12:05:29.640> of<12:05:29.820> that<12:05:30.000> data<12:05:30.360> out 12:05:31.790 --> 12:05:31.800 align:start position:0% The Hub spouted all of that data out 12:05:31.800 --> 12:05:33.530 align:start position:0% The Hub spouted all of that data out to<12:05:32.340> all<12:05:32.520> the<12:05:32.640> other<12:05:32.756> computers<12:05:33.240> on<12:05:33.416> the 12:05:33.530 --> 12:05:33.540 align:start position:0% to all the other computers on the 12:05:33.540 --> 12:05:35.690 align:start position:0% to all the other computers on the network<12:05:33.720> this<12:05:34.616> created<12:05:34.980> a<12:05:35.160> lot<12:05:35.276> of<12:05:35.460> broadcast 12:05:35.690 --> 12:05:35.700 align:start position:0% network this created a lot of broadcast 12:05:35.700 --> 12:05:40.310 align:start position:0% network this created a lot of broadcast traffic<12:05:36.416> because<12:05:37.320> the<12:05:38.220> Hub<12:05:38.820> itself<12:05:39.300> worked<12:05:40.080> on 12:05:40.310 --> 12:05:40.320 align:start position:0% traffic because the Hub itself worked on 12:05:40.320 --> 12:05:43.070 align:start position:0% traffic because the Hub itself worked on the<12:05:40.560> physical<12:05:40.860> layer<12:05:41.400> all<12:05:42.116> it<12:05:42.240> did<12:05:42.416> was<12:05:42.720> repeat 12:05:43.070 --> 12:05:43.080 align:start position:0% the physical layer all it did was repeat 12:05:43.080 --> 12:05:45.650 align:start position:0% the physical layer all it did was repeat all<12:05:43.680> of<12:05:43.800> the<12:05:43.916> bits<12:05:44.220> that<12:05:44.460> went<12:05:44.580> into<12:05:44.756> it<12:05:45.060> out<12:05:45.480> to 12:05:45.650 --> 12:05:45.660 align:start position:0% all of the bits that went into it out to 12:05:45.660 --> 12:05:47.330 align:start position:0% all of the bits that went into it out to all<12:05:45.960> the<12:05:46.080> other<12:05:46.256> devices 12:05:47.330 --> 12:05:47.340 align:start position:0% all the other devices 12:05:47.340 --> 12:05:49.790 align:start position:0% all the other devices but<12:05:47.820> now<12:05:48.116> we<12:05:48.660> have<12:05:48.840> something<12:05:49.200> and<12:05:49.500> we've<12:05:49.680> had 12:05:49.790 --> 12:05:49.800 align:start position:0% but now we have something and we've had 12:05:49.800 --> 12:05:52.010 align:start position:0% but now we have something and we've had for<12:05:50.096> quite<12:05:50.340> a<12:05:50.460> while<12:05:50.580> a<12:05:51.300> thing<12:05:51.416> called<12:05:51.660> a 12:05:52.010 --> 12:05:52.020 align:start position:0% for quite a while a thing called a 12:05:52.020 --> 12:05:53.870 align:start position:0% for quite a while a thing called a switch<12:05:52.200> and<12:05:52.916> this<12:05:53.040> allows<12:05:53.276> for<12:05:53.460> switching 12:05:53.870 --> 12:05:53.880 align:start position:0% switch and this allows for switching 12:05:53.880 --> 12:05:58.070 align:start position:0% switch and this allows for switching which<12:05:54.116> operates<12:05:54.660> mostly<12:05:55.436> on<12:05:56.220> level<12:05:56.520> two 12:05:58.070 --> 12:05:58.080 align:start position:0% which operates mostly on level two 12:05:58.080 --> 12:06:00.530 align:start position:0% which operates mostly on level two of<12:05:58.436> the<12:05:58.560> OSI<12:05:58.980> model<12:05:59.220> which<12:05:59.700> if<12:05:59.880> you<12:06:00.000> recall<12:06:00.360> is 12:06:00.530 --> 12:06:00.540 align:start position:0% of the OSI model which if you recall is 12:06:00.540 --> 12:06:01.850 align:start position:0% of the OSI model which if you recall is the 12:06:01.850 --> 12:06:01.860 align:start position:0% the 12:06:01.860 --> 12:06:04.130 align:start position:0% the data<12:06:02.400> link<12:06:02.460> layer 12:06:04.130 --> 12:06:04.140 align:start position:0% data link layer 12:06:04.140 --> 12:06:06.290 align:start position:0% data link layer switching<12:06:04.740> allows<12:06:05.160> us<12:06:05.340> to<12:06:05.640> have<12:06:05.756> a<12:06:06.060> fully 12:06:06.290 --> 12:06:06.300 align:start position:0% switching allows us to have a fully 12:06:06.300 --> 12:06:08.810 align:start position:0% switching allows us to have a fully functioning<12:06:06.840> local<12:06:07.200> area<12:06:07.500> network<12:06:07.916> because 12:06:08.810 --> 12:06:08.820 align:start position:0% functioning local area network because 12:06:08.820 --> 12:06:13.190 align:start position:0% functioning local area network because it<12:06:09.596> allows<12:06:09.900> devices<12:06:10.256> to<12:06:10.740> talk 12:06:13.190 --> 12:06:13.200 align:start position:0% 12:06:13.200 --> 12:06:15.766 align:start position:0% using<12:06:13.860> the<12:06:14.040> MAC<12:06:14.160> address<12:06:14.460> or<12:06:15.360> the<12:06:15.596> physical 12:06:15.766 --> 12:06:15.776 align:start position:0% using the MAC address or the physical 12:06:15.776 --> 12:06:18.350 align:start position:0% using the MAC address or the physical address<12:06:16.200> of<12:06:17.040> the<12:06:17.220> computer 12:06:18.350 --> 12:06:18.360 align:start position:0% address of the computer 12:06:18.360 --> 12:06:20.810 align:start position:0% address of the computer so<12:06:19.020> in<12:06:19.320> this<12:06:19.500> module<12:06:19.860> we're<12:06:20.340> going<12:06:20.460> to<12:06:20.640> talk 12:06:20.810 --> 12:06:20.820 align:start position:0% so in this module we're going to talk 12:06:20.820 --> 12:06:24.290 align:start position:0% so in this module we're going to talk more<12:06:21.300> in<12:06:21.480> depth<12:06:21.776> about<12:06:22.256> what<12:06:22.616> a<12:06:22.740> switch<12:06:22.916> is 12:06:24.290 --> 12:06:24.300 align:start position:0% more in depth about what a switch is 12:06:24.300 --> 12:06:26.330 align:start position:0% more in depth about what a switch is how<12:06:24.900> a<12:06:25.080> switch<12:06:25.256> operates<12:06:25.740> which<12:06:26.040> I<12:06:26.220> just 12:06:26.330 --> 12:06:26.340 align:start position:0% how a switch operates which I just 12:06:26.340 --> 12:06:28.730 align:start position:0% how a switch operates which I just touched<12:06:26.700> upon<12:06:26.936> a<12:06:27.116> bit<12:06:27.240> and<12:06:28.080> then<12:06:28.256> I'm<12:06:28.436> going<12:06:28.616> to 12:06:28.730 --> 12:06:28.740 align:start position:0% touched upon a bit and then I'm going to 12:06:28.740 --> 12:06:31.370 align:start position:0% touched upon a bit and then I'm going to talk<12:06:28.860> about<12:06:29.040> a<12:06:29.880> couple<12:06:30.180> Advanced<12:06:30.960> switches 12:06:31.370 --> 12:06:31.380 align:start position:0% talk about a couple Advanced switches 12:06:31.380 --> 12:06:32.870 align:start position:0% talk about a couple Advanced switches you<12:06:31.560> need<12:06:31.740> to<12:06:31.860> know<12:06:31.980> about<12:06:32.160> for<12:06:32.580> the<12:06:32.756> network 12:06:32.870 --> 12:06:32.880 align:start position:0% you need to know about for the network 12:06:32.880 --> 12:06:35.690 align:start position:0% you need to know about for the network plus<12:06:33.180> exam<12:06:33.680> these<12:06:34.680> are<12:06:34.740> the<12:06:35.096> multi-layer 12:06:35.690 --> 12:06:35.700 align:start position:0% plus exam these are the multi-layer 12:06:35.700 --> 12:06:41.330 align:start position:0% plus exam these are the multi-layer switch<12:06:35.880> also<12:06:36.480> called<12:06:36.720> a<12:06:37.080> layer<12:06:37.980> 3<12:06:38.220> switch<12:06:39.140> or<12:06:40.140> a 12:06:41.330 --> 12:06:41.340 align:start position:0% switch also called a layer 3 switch or a 12:06:41.340 --> 12:06:43.670 align:start position:0% switch also called a layer 3 switch or a Smart<12:06:41.820> Switch 12:06:43.670 --> 12:06:43.680 align:start position:0% Smart Switch 12:06:43.680 --> 12:06:45.406 align:start position:0% Smart Switch and<12:06:44.160> then<12:06:44.340> we're<12:06:44.460> going<12:06:44.580> to<12:06:44.640> talk<12:06:44.820> about<12:06:45.000> a 12:06:45.406 --> 12:06:45.416 align:start position:0% and then we're going to talk about a 12:06:45.416 --> 12:06:48.170 align:start position:0% and then we're going to talk about a Content<12:06:45.840> switch<12:06:46.200> which<12:06:47.040> as<12:06:47.400> the<12:06:47.580> name<12:06:47.700> implies 12:06:48.170 --> 12:06:48.180 align:start position:0% Content switch which as the name implies 12:06:48.180 --> 12:06:50.926 align:start position:0% Content switch which as the name implies deals<12:06:48.720> with<12:06:48.900> the<12:06:49.140> content<12:06:49.500> in<12:06:49.916> the<12:06:50.040> packet<12:06:50.400> not 12:06:50.926 --> 12:06:50.936 align:start position:0% deals with the content in the packet not 12:06:50.936 --> 12:06:55.130 align:start position:0% deals with the content in the packet not just<12:06:51.180> relaying<12:06:51.900> the<12:06:51.960> packet<12:06:52.320> of<12:06:52.380> data<12:06:52.740> itself 12:06:55.130 --> 12:06:55.140 align:start position:0% 12:06:55.140 --> 12:06:58.606 align:start position:0% so<12:06:55.916> a<12:06:56.520> switch<12:06:56.700> is<12:06:57.000> an<12:06:57.240> extremely<12:06:57.660> important 12:06:58.606 --> 12:06:58.616 align:start position:0% so a switch is an extremely important 12:06:58.616 --> 12:07:01.070 align:start position:0% so a switch is an extremely important part<12:06:58.860> of<12:06:59.096> a<12:06:59.220> functioning<12:06:59.700> Network<12:07:00.300> so<12:07:00.960> let's 12:07:01.070 --> 12:07:01.080 align:start position:0% part of a functioning Network so let's 12:07:01.080 --> 12:07:03.766 align:start position:0% part of a functioning Network so let's look<12:07:01.320> for<12:07:01.500> a<12:07:01.616> minute<12:07:01.800> about<12:07:02.220> a<12:07:02.640> light<12:07:02.880> switch<12:07:03.116> a 12:07:03.766 --> 12:07:03.776 align:start position:0% look for a minute about a light switch a 12:07:03.776 --> 12:07:05.390 align:start position:0% look for a minute about a light switch a light<12:07:03.900> switch<12:07:04.140> essentially<12:07:04.616> has<12:07:04.916> two<12:07:05.096> pieces 12:07:05.390 --> 12:07:05.400 align:start position:0% light switch essentially has two pieces 12:07:05.400 --> 12:07:08.450 align:start position:0% light switch essentially has two pieces of<12:07:05.580> wire<12:07:05.960> attached<12:07:06.960> to<12:07:07.140> it<12:07:07.800> if<12:07:08.040> we<12:07:08.160> look<12:07:08.340> at 12:07:08.450 --> 12:07:08.460 align:start position:0% of wire attached to it if we look at 12:07:08.460 --> 12:07:11.450 align:start position:0% of wire attached to it if we look at like<12:07:08.640> so 12:07:11.450 --> 12:07:11.460 align:start position:0% 12:07:11.460 --> 12:07:13.070 align:start position:0% I'll<12:07:11.700> put<12:07:11.936> the<12:07:12.060> little<12:07:12.180> switch<12:07:12.416> right<12:07:12.776> there 12:07:13.070 --> 12:07:13.080 align:start position:0% I'll put the little switch right there 12:07:13.080 --> 12:07:16.070 align:start position:0% I'll put the little switch right there and<12:07:13.916> when<12:07:14.160> the<12:07:14.340> switch<12:07:14.580> is<12:07:15.116> flipped<12:07:15.540> in<12:07:15.900> One 12:07:16.070 --> 12:07:16.080 align:start position:0% and when the switch is flipped in One 12:07:16.080 --> 12:07:19.550 align:start position:0% and when the switch is flipped in One Direction<12:07:16.320> the<12:07:17.220> circuit<12:07:17.640> is<12:07:18.180> completed<12:07:19.140> when 12:07:19.550 --> 12:07:19.560 align:start position:0% Direction the circuit is completed when 12:07:19.560 --> 12:07:22.550 align:start position:0% Direction the circuit is completed when it's<12:07:19.740> flipped<12:07:20.096> the<12:07:20.580> other<12:07:20.700> way<12:07:21.256> then<12:07:22.256> the 12:07:22.550 --> 12:07:22.560 align:start position:0% it's flipped the other way then the 12:07:22.560 --> 12:07:24.290 align:start position:0% it's flipped the other way then the circuit<12:07:22.800> is<12:07:22.980> sort<12:07:23.160> of<12:07:23.220> broken<12:07:23.460> and<12:07:23.936> so<12:07:24.116> the 12:07:24.290 --> 12:07:24.300 align:start position:0% circuit is sort of broken and so the 12:07:24.300 --> 12:07:26.266 align:start position:0% circuit is sort of broken and so the light<12:07:24.480> turns<12:07:25.256> off 12:07:26.266 --> 12:07:26.276 align:start position:0% light turns off 12:07:26.276 --> 12:07:28.970 align:start position:0% light turns off in<12:07:26.820> a<12:07:27.000> way<12:07:27.116> an<12:07:27.416> ethernet<12:07:27.720> switch<12:07:28.140> follows<12:07:28.800> the 12:07:28.970 --> 12:07:28.980 align:start position:0% in a way an ethernet switch follows the 12:07:28.980 --> 12:07:30.890 align:start position:0% in a way an ethernet switch follows the same<12:07:29.160> principle<12:07:29.640> except<12:07:30.360> it's<12:07:30.540> not<12:07:30.776> only 12:07:30.890 --> 12:07:30.900 align:start position:0% same principle except it's not only 12:07:30.900 --> 12:07:33.470 align:start position:0% same principle except it's not only attached<12:07:31.436> to<12:07:31.916> one<12:07:32.340> single<12:07:32.700> wire<12:07:32.936> and<12:07:33.240> cable 12:07:33.470 --> 12:07:33.480 align:start position:0% attached to one single wire and cable 12:07:33.480 --> 12:07:36.290 align:start position:0% attached to one single wire and cable but<12:07:34.020> to<12:07:34.320> many<12:07:34.500> some<12:07:35.400> switches<12:07:35.820> can<12:07:36.000> even<12:07:36.116> have 12:07:36.290 --> 12:07:36.300 align:start position:0% but to many some switches can even have 12:07:36.300 --> 12:07:39.766 align:start position:0% but to many some switches can even have upwards<12:07:36.840> of<12:07:37.160> 200<12:07:38.160> cables<12:07:38.700> attached<12:07:39.116> to<12:07:39.180> them 12:07:39.766 --> 12:07:39.776 align:start position:0% upwards of 200 cables attached to them 12:07:39.776 --> 12:07:42.170 align:start position:0% upwards of 200 cables attached to them now<12:07:40.140> these<12:07:40.436> ethernet<12:07:40.860> switches<12:07:41.340> are<12:07:41.700> used<12:07:41.880> to 12:07:42.170 --> 12:07:42.180 align:start position:0% now these ethernet switches are used to 12:07:42.180 --> 12:07:44.630 align:start position:0% now these ethernet switches are used to connect<12:07:42.300> many<12:07:42.960> if<12:07:43.560> not<12:07:43.740> all<12:07:44.096> of<12:07:44.220> the<12:07:44.340> devices 12:07:44.630 --> 12:07:44.640 align:start position:0% connect many if not all of the devices 12:07:44.640 --> 12:07:49.130 align:start position:0% connect many if not all of the devices on<12:07:45.060> network<12:07:45.240> and<12:07:46.020> it<12:07:46.200> establishes<12:07:46.860> a<12:07:47.700> flow<12:07:48.300> of 12:07:49.130 --> 12:07:49.140 align:start position:0% on network and it establishes a flow of 12:07:49.140 --> 12:07:51.170 align:start position:0% on network and it establishes a flow of data<12:07:49.616> between<12:07:50.096> them 12:07:51.170 --> 12:07:51.180 align:start position:0% data between them 12:07:51.180 --> 12:07:54.350 align:start position:0% data between them this<12:07:51.840> switch<12:07:52.020> like<12:07:52.436> a<12:07:52.800> light<12:07:52.980> switch<12:07:53.220> makes<12:07:54.116> a 12:07:54.350 --> 12:07:54.360 align:start position:0% this switch like a light switch makes a 12:07:54.360 --> 12:07:56.150 align:start position:0% this switch like a light switch makes a connection<12:07:54.480> between<12:07:55.020> two<12:07:55.436> different<12:07:55.616> cables 12:07:56.150 --> 12:07:56.160 align:start position:0% connection between two different cables 12:07:56.160 --> 12:07:58.730 align:start position:0% connection between two different cables and<12:07:56.756> allows<12:07:57.180> the<12:07:57.596> data<12:07:57.900> to<12:07:58.020> flow<12:07:58.256> specifically 12:07:58.730 --> 12:07:58.740 align:start position:0% and allows the data to flow specifically 12:07:58.740 --> 12:08:00.650 align:start position:0% and allows the data to flow specifically between<12:07:59.096> those<12:07:59.400> two<12:07:59.640> devices 12:08:00.650 --> 12:08:00.660 align:start position:0% between those two devices 12:08:00.660 --> 12:08:04.130 align:start position:0% between those two devices now<12:08:01.380> Lan<12:08:02.096> switches<12:08:02.640> are<12:08:03.116> used<12:08:03.300> to<12:08:03.540> send<12:08:03.720> data 12:08:04.130 --> 12:08:04.140 align:start position:0% now Lan switches are used to send data 12:08:04.140 --> 12:08:06.850 align:start position:0% now Lan switches are used to send data from<12:08:04.380> a<12:08:04.560> single<12:08:04.800> device<12:08:05.116> to<12:08:06.116> another 12:08:06.850 --> 12:08:06.860 align:start position:0% from a single device to another 12:08:06.860 --> 12:08:09.650 align:start position:0% from a single device to another sometimes<12:08:07.860> uh<12:08:08.400> the<12:08:08.640> and<12:08:08.936> sometimes<12:08:09.360> even 12:08:09.650 --> 12:08:09.660 align:start position:0% sometimes uh the and sometimes even 12:08:09.660 --> 12:08:12.406 align:start position:0% sometimes uh the and sometimes even multiple<12:08:10.140> devices<12:08:10.560> there<12:08:11.520> are<12:08:11.640> devices<12:08:12.000> as<12:08:12.240> I 12:08:12.406 --> 12:08:12.416 align:start position:0% multiple devices there are devices as I 12:08:12.416 --> 12:08:14.030 align:start position:0% multiple devices there are devices as I said<12:08:12.480> called<12:08:12.776> hubs<12:08:13.200> but<12:08:13.436> these<12:08:13.680> do<12:08:13.860> something 12:08:14.030 --> 12:08:14.040 align:start position:0% said called hubs but these do something 12:08:14.040 --> 12:08:15.170 align:start position:0% said called hubs but these do something different 12:08:15.170 --> 12:08:15.180 align:start position:0% different 12:08:15.180 --> 12:08:17.926 align:start position:0% different so<12:08:15.720> what<12:08:16.256> the<12:08:16.380> switch<12:08:16.560> really<12:08:16.916> does<12:08:17.220> here<12:08:17.460> is 12:08:17.926 --> 12:08:17.936 align:start position:0% so what the switch really does here is 12:08:17.936 --> 12:08:20.570 align:start position:0% so what the switch really does here is it<12:08:18.116> allows<12:08:18.416> data<12:08:18.776> sent<12:08:18.960> from<12:08:19.256> one<12:08:19.560> device<12:08:19.800> to 12:08:20.570 --> 12:08:20.580 align:start position:0% it allows data sent from one device to 12:08:20.580 --> 12:08:22.370 align:start position:0% it allows data sent from one device to go<12:08:20.756> specifically 12:08:22.370 --> 12:08:22.380 align:start position:0% go specifically 12:08:22.380 --> 12:08:24.050 align:start position:0% go specifically to<12:08:22.740> the<12:08:22.860> other<12:08:22.980> device<12:08:23.220> that<12:08:23.520> it's<12:08:23.640> meant<12:08:23.936> for 12:08:24.050 --> 12:08:24.060 align:start position:0% to the other device that it's meant for 12:08:24.060 --> 12:08:25.670 align:start position:0% to the other device that it's meant for and<12:08:24.480> it<12:08:24.660> does<12:08:24.840> this 12:08:25.670 --> 12:08:25.680 align:start position:0% and it does this 12:08:25.680 --> 12:08:29.266 align:start position:0% and it does this because<12:08:26.276> it<12:08:26.820> knows<12:08:27.240> the<12:08:27.660> MAC<12:08:27.776> address 12:08:29.266 --> 12:08:29.276 align:start position:0% because it knows the MAC address 12:08:29.276 --> 12:08:32.086 align:start position:0% because it knows the MAC address that<12:08:29.756> it<12:08:29.880> wants<12:08:30.180> to<12:08:30.240> send<12:08:30.480> to<12:08:31.140> now<12:08:31.680> it<12:08:31.916> doesn't 12:08:32.086 --> 12:08:32.096 align:start position:0% that it wants to send to now it doesn't 12:08:32.096 --> 12:08:34.906 align:start position:0% that it wants to send to now it doesn't necessarily<12:08:32.756> know<12:08:33.200> where<12:08:34.200> that<12:08:34.500> Mac<12:08:34.680> address 12:08:34.906 --> 12:08:34.916 align:start position:0% necessarily know where that Mac address 12:08:34.916 --> 12:08:37.550 align:start position:0% necessarily know where that Mac address is<12:08:35.276> on<12:08:35.460> the<12:08:35.580> network<12:08:35.700> all<12:08:36.660> it<12:08:36.840> knows<12:08:37.200> and<12:08:37.436> it 12:08:37.550 --> 12:08:37.560 align:start position:0% is on the network all it knows and it 12:08:37.560 --> 12:08:39.050 align:start position:0% is on the network all it knows and it puts<12:08:37.800> this<12:08:37.916> into<12:08:38.096> the<12:08:38.276> packet<12:08:38.580> remember<12:08:38.756> we 12:08:39.050 --> 12:08:39.060 align:start position:0% puts this into the packet remember we 12:08:39.060 --> 12:08:40.426 align:start position:0% puts this into the packet remember we talked<12:08:39.360> about<12:08:39.416> that<12:08:39.660> it<12:08:39.840> puts<12:08:40.080> it<12:08:40.140> into<12:08:40.256> the 12:08:40.426 --> 12:08:40.436 align:start position:0% talked about that it puts it into the 12:08:40.436 --> 12:08:42.350 align:start position:0% talked about that it puts it into the header<12:08:40.740> of<12:08:40.860> the<12:08:40.980> packet 12:08:42.350 --> 12:08:42.360 align:start position:0% header of the packet 12:08:42.360 --> 12:08:44.570 align:start position:0% header of the packet the<12:08:43.020> address<12:08:43.256> which<12:08:43.680> would<12:08:43.860> be<12:08:44.040> sort<12:08:44.276> of<12:08:44.400> like 12:08:44.570 --> 12:08:44.580 align:start position:0% the address which would be sort of like 12:08:44.580 --> 12:08:46.790 align:start position:0% the address which would be sort of like the<12:08:44.880> phone<12:08:45.060> number<12:08:45.300> or<12:08:46.020> the<12:08:46.320> social<12:08:46.436> security 12:08:46.790 --> 12:08:46.800 align:start position:0% the phone number or the social security 12:08:46.800 --> 12:08:50.030 align:start position:0% the phone number or the social security number<12:08:47.360> of<12:08:48.360> the<12:08:48.720> computer<12:08:48.900> that<12:08:49.680> wants<12:08:49.980> to 12:08:50.030 --> 12:08:50.040 align:start position:0% number of the computer that wants to 12:08:50.040 --> 12:08:52.850 align:start position:0% number of the computer that wants to receive<12:08:50.276> the<12:08:50.460> data<12:08:50.756> the<12:08:51.300> switch<12:08:51.480> then<12:08:51.840> has<12:08:52.560> a 12:08:52.850 --> 12:08:52.860 align:start position:0% receive the data the switch then has a 12:08:52.860 --> 12:08:56.390 align:start position:0% receive the data the switch then has a table<12:08:53.180> that<12:08:54.180> says<12:08:54.540> in<12:08:55.020> each<12:08:55.256> port 12:08:56.390 --> 12:08:56.400 align:start position:0% table that says in each port 12:08:56.400 --> 12:09:02.330 align:start position:0% table that says in each port so<12:08:56.880> if<12:08:57.000> we<12:08:57.180> had<12:08:57.300> Port<12:08:57.596> 1<12:08:57.960> 2<12:08:59.116> 3<12:09:00.116> 4<12:09:00.776> and<12:09:01.080> 5<12:09:01.380> it<12:09:02.220> would 12:09:02.330 --> 12:09:02.340 align:start position:0% so if we had Port 1 2 3 4 and 5 it would 12:09:02.340 --> 12:09:03.530 align:start position:0% so if we had Port 1 2 3 4 and 5 it would say 12:09:03.530 --> 12:09:03.540 align:start position:0% say 12:09:03.540 --> 12:09:06.170 align:start position:0% say the<12:09:04.140> MAC<12:09:04.256> address<12:09:04.500> connected<12:09:05.460> to<12:09:05.700> each<12:09:05.936> port 12:09:06.170 --> 12:09:06.180 align:start position:0% the MAC address connected to each port 12:09:06.180 --> 12:09:10.070 align:start position:0% the MAC address connected to each port and<12:09:07.140> so<12:09:07.380> when<12:09:07.916> Port<12:09:08.160> 1<12:09:08.460> sends<12:09:09.000> data<12:09:09.300> meant<12:09:09.960> for 12:09:10.070 --> 12:09:10.080 align:start position:0% and so when Port 1 sends data meant for 12:09:10.080 --> 12:09:11.630 align:start position:0% and so when Port 1 sends data meant for a<12:09:10.380> MAC<12:09:10.500> address 12:09:11.630 --> 12:09:11.640 align:start position:0% a MAC address 12:09:11.640 --> 12:09:13.790 align:start position:0% a MAC address it<12:09:12.180> knows<12:09:12.540> oh<12:09:12.776> I'm<12:09:13.140> going<12:09:13.320> to<12:09:13.320> send<12:09:13.500> that<12:09:13.616> to 12:09:13.790 --> 12:09:13.800 align:start position:0% it knows oh I'm going to send that to 12:09:13.800 --> 12:09:15.230 align:start position:0% it knows oh I'm going to send that to Port<12:09:13.916> 5. 12:09:15.230 --> 12:09:15.240 align:start position:0% Port 5. 12:09:15.240 --> 12:09:17.086 align:start position:0% Port 5. now<12:09:15.540> it<12:09:15.720> could<12:09:15.900> also<12:09:16.080> do<12:09:16.256> this<12:09:16.436> for<12:09:16.680> multiple 12:09:17.086 --> 12:09:17.096 align:start position:0% now it could also do this for multiple 12:09:17.096 --> 12:09:18.710 align:start position:0% now it could also do this for multiple for<12:09:17.400> instance<12:09:17.700> I'm<12:09:18.116> going<12:09:18.300> to<12:09:18.360> send<12:09:18.480> it<12:09:18.596> to 12:09:18.710 --> 12:09:18.720 align:start position:0% for instance I'm going to send it to 12:09:18.720 --> 12:09:20.926 align:start position:0% for instance I'm going to send it to Port<12:09:18.840> 2<12:09:19.140> and<12:09:19.560> port<12:09:19.800> 5. 12:09:20.926 --> 12:09:20.936 align:start position:0% Port 2 and port 5. 12:09:20.936 --> 12:09:22.906 align:start position:0% Port 2 and port 5. the<12:09:21.180> key<12:09:21.360> difference<12:09:21.596> here<12:09:22.020> as<12:09:22.256> I<12:09:22.500> pointed<12:09:22.800> out 12:09:22.906 --> 12:09:22.916 align:start position:0% the key difference here as I pointed out 12:09:22.916 --> 12:09:25.490 align:start position:0% the key difference here as I pointed out in<12:09:23.276> the<12:09:23.400> very<12:09:23.580> first<12:09:23.820> slide<12:09:24.180> was<12:09:24.840> rather<12:09:25.320> than 12:09:25.490 --> 12:09:25.500 align:start position:0% in the very first slide was rather than 12:09:25.500 --> 12:09:26.810 align:start position:0% in the very first slide was rather than a<12:09:25.740> hub 12:09:26.810 --> 12:09:26.820 align:start position:0% a hub 12:09:26.820 --> 12:09:31.370 align:start position:0% a hub which<12:09:27.360> broadcasts<12:09:28.256> out 12:09:31.370 --> 12:09:31.380 align:start position:0% 12:09:31.380 --> 12:09:33.230 align:start position:0% to<12:09:31.980> all<12:09:32.220> devices 12:09:33.230 --> 12:09:33.240 align:start position:0% to all devices 12:09:33.240 --> 12:09:38.030 align:start position:0% to all devices the<12:09:33.900> switch<12:09:34.160> creates<12:09:35.160> a<12:09:35.520> single<12:09:35.756> switch 12:09:38.030 --> 12:09:38.040 align:start position:0% 12:09:38.040 --> 12:09:41.086 align:start position:0% between<12:09:38.700> two<12:09:39.540> specific<12:09:39.900> devices<12:09:40.256> and<12:09:40.740> closes 12:09:41.086 --> 12:09:41.096 align:start position:0% between two specific devices and closes 12:09:41.096 --> 12:09:42.350 align:start position:0% between two specific devices and closes a<12:09:41.276> connection 12:09:42.350 --> 12:09:42.360 align:start position:0% a connection 12:09:42.360 --> 12:09:45.106 align:start position:0% a connection what<12:09:42.776> this<12:09:42.960> does<12:09:43.200> in<12:09:43.500> effect<12:09:43.680> therefore<12:09:44.340> is 12:09:45.106 --> 12:09:45.116 align:start position:0% what this does in effect therefore is 12:09:45.116 --> 12:09:47.450 align:start position:0% what this does in effect therefore is reduce<12:09:45.416> broadcast<12:09:45.960> traffic<12:09:46.500> and<12:09:46.980> allow<12:09:47.276> the 12:09:47.450 --> 12:09:47.460 align:start position:0% reduce broadcast traffic and allow the 12:09:47.460 --> 12:09:49.790 align:start position:0% reduce broadcast traffic and allow the network<12:09:47.640> to<12:09:48.116> run<12:09:48.360> much<12:09:49.020> more<12:09:49.256> efficiently 12:09:49.790 --> 12:09:49.800 align:start position:0% network to run much more efficiently 12:09:49.800 --> 12:09:52.370 align:start position:0% network to run much more efficiently than<12:09:50.276> a<12:09:50.460> hub<12:09:50.640> allowed 12:09:52.370 --> 12:09:52.380 align:start position:0% than a hub allowed 12:09:52.380 --> 12:09:54.830 align:start position:0% than a hub allowed now<12:09:52.800> there<12:09:53.160> was<12:09:53.276> a<12:09:53.460> time<12:09:53.700> when<12:09:54.116> networking 12:09:54.830 --> 12:09:54.840 align:start position:0% now there was a time when networking 12:09:54.840 --> 12:09:57.406 align:start position:0% now there was a time when networking devices<12:09:55.200> only<12:09:55.680> served<12:09:56.160> one<12:09:56.460> purpose<12:09:56.820> and 12:09:57.406 --> 12:09:57.416 align:start position:0% devices only served one purpose and 12:09:57.416 --> 12:09:59.086 align:start position:0% devices only served one purpose and their<12:09:57.596> functions<12:09:58.020> were<12:09:58.256> specific<12:09:58.616> to<12:09:58.860> that 12:09:59.086 --> 12:09:59.096 align:start position:0% their functions were specific to that 12:09:59.096 --> 12:10:01.010 align:start position:0% their functions were specific to that type<12:09:59.276> of<12:09:59.400> device<12:09:59.640> but<12:10:00.360> over<12:10:00.480> years<12:10:00.720> things 12:10:01.010 --> 12:10:01.020 align:start position:0% type of device but over years things 12:10:01.020 --> 12:10:03.050 align:start position:0% type of device but over years things have<12:10:01.320> evolved<12:10:01.740> so<12:10:02.040> now<12:10:02.160> devices<12:10:02.400> can<12:10:02.880> do 12:10:03.050 --> 12:10:03.060 align:start position:0% have evolved so now devices can do 12:10:03.060 --> 12:10:06.290 align:start position:0% have evolved so now devices can do multiple<12:10:03.660> things<12:10:03.960> now<12:10:04.740> we<12:10:05.276> see<12:10:05.700> this 12:10:06.290 --> 12:10:06.300 align:start position:0% multiple things now we see this 12:10:06.300 --> 12:10:08.150 align:start position:0% multiple things now we see this multi-layer<12:10:07.200> switch<12:10:07.380> or<12:10:07.680> what<12:10:07.916> you<12:10:08.040> might 12:10:08.150 --> 12:10:08.160 align:start position:0% multi-layer switch or what you might 12:10:08.160 --> 12:10:11.210 align:start position:0% multi-layer switch or what you might also<12:10:08.460> see<12:10:08.640> as<12:10:08.820> a<12:10:09.060> layer<12:10:09.360> three<12:10:10.080> switch<12:10:10.436> or<12:10:10.980> a 12:10:11.210 --> 12:10:11.220 align:start position:0% also see as a layer three switch or a 12:10:11.220 --> 12:10:12.766 align:start position:0% also see as a layer three switch or a Smart<12:10:11.700> Switch 12:10:12.766 --> 12:10:12.776 align:start position:0% Smart Switch 12:10:12.776 --> 12:10:14.990 align:start position:0% Smart Switch what<12:10:13.380> it<12:10:13.500> does<12:10:13.616> is<12:10:13.800> it<12:10:14.040> is<12:10:14.220> not<12:10:14.400> only<12:10:14.580> a<12:10:14.820> switch 12:10:14.990 --> 12:10:15.000 align:start position:0% what it does is it is not only a switch 12:10:15.000 --> 12:10:17.690 align:start position:0% what it does is it is not only a switch it's<12:10:15.416> also<12:10:15.776> a<12:10:16.140> router<12:10:16.916> this<12:10:17.400> is<12:10:17.460> the<12:10:17.580> reason 12:10:17.690 --> 12:10:17.700 align:start position:0% it's also a router this is the reason 12:10:17.700 --> 12:10:19.790 align:start position:0% it's also a router this is the reason why<12:10:17.936> it's<12:10:18.116> called<12:10:18.300> a<12:10:18.480> layer<12:10:18.840> 3<12:10:19.020> switch<12:10:19.380> I 12:10:19.790 --> 12:10:19.800 align:start position:0% why it's called a layer 3 switch I 12:10:19.800 --> 12:10:21.290 align:start position:0% why it's called a layer 3 switch I brought<12:10:19.980> up<12:10:20.096> the<12:10:20.220> OSI<12:10:20.580> model<12:10:20.820> on<12:10:21.116> the<12:10:21.240> very 12:10:21.290 --> 12:10:21.300 align:start position:0% brought up the OSI model on the very 12:10:21.300 --> 12:10:22.906 align:start position:0% brought up the OSI model on the very first<12:10:21.540> slide 12:10:22.906 --> 12:10:22.916 align:start position:0% first slide 12:10:22.916 --> 12:10:26.870 align:start position:0% first slide layer<12:10:23.460> 1<12:10:23.640> physical 12:10:26.870 --> 12:10:26.880 align:start position:0% 12:10:26.880 --> 12:10:30.710 align:start position:0% layer<12:10:27.416> 2<12:10:27.540> data<12:10:28.500> link 12:10:30.710 --> 12:10:30.720 align:start position:0% 12:10:30.720 --> 12:10:32.810 align:start position:0% and<12:10:31.080> if<12:10:31.200> you<12:10:31.320> recall<12:10:31.680> layer<12:10:32.160> three<12:10:32.340> let's<12:10:32.640> use 12:10:32.810 --> 12:10:32.820 align:start position:0% and if you recall layer three let's use 12:10:32.820 --> 12:10:37.670 align:start position:0% and if you recall layer three let's use our<12:10:33.180> mnemonic<12:10:34.140> device<12:10:34.460> please<12:10:35.460> do<12:10:36.360> not<12:10:37.020> throw 12:10:37.670 --> 12:10:37.680 align:start position:0% our mnemonic device please do not throw 12:10:37.680 --> 12:10:40.010 align:start position:0% our mnemonic device please do not throw sausage<12:10:38.160> pizza<12:10:38.400> away<12:10:38.756> so<12:10:39.480> this<12:10:39.660> is<12:10:39.776> the 12:10:40.010 --> 12:10:40.020 align:start position:0% sausage pizza away so this is the 12:10:40.020 --> 12:10:41.870 align:start position:0% sausage pizza away so this is the network<12:10:40.200> layer 12:10:41.870 --> 12:10:41.880 align:start position:0% network layer 12:10:41.880 --> 12:10:44.210 align:start position:0% network layer if<12:10:42.300> you<12:10:42.480> recall<12:10:42.900> we<12:10:43.256> mentioned<12:10:43.616> briefly<12:10:43.980> that 12:10:44.210 --> 12:10:44.220 align:start position:0% if you recall we mentioned briefly that 12:10:44.220 --> 12:10:45.766 align:start position:0% if you recall we mentioned briefly that routers<12:10:44.640> which<12:10:44.820> we'll<12:10:45.000> talk<12:10:45.180> about<12:10:45.300> in<12:10:45.596> more 12:10:45.766 --> 12:10:45.776 align:start position:0% routers which we'll talk about in more 12:10:45.776 --> 12:10:46.906 align:start position:0% routers which we'll talk about in more depth<12:10:46.080> later 12:10:46.906 --> 12:10:46.916 align:start position:0% depth later 12:10:46.916 --> 12:10:50.266 align:start position:0% depth later operate<12:10:47.640> on<12:10:47.820> layer<12:10:48.116> three<12:10:48.240> that's<12:10:49.080> because 12:10:50.266 --> 12:10:50.276 align:start position:0% operate on layer three that's because 12:10:50.276 --> 12:10:54.470 align:start position:0% operate on layer three that's because IP<12:10:51.000> addresses<12:10:51.596> operate<12:10:52.320> on<12:10:52.500> layer<12:10:52.800> three<12:10:52.916> so<12:10:53.880> a 12:10:54.470 --> 12:10:54.480 align:start position:0% IP addresses operate on layer three so a 12:10:54.480 --> 12:10:56.390 align:start position:0% IP addresses operate on layer three so a switch<12:10:54.596> can<12:10:55.140> not<12:10:55.320> only<12:10:55.436> look<12:10:55.680> at<12:10:55.860> the<12:10:56.160> MAC 12:10:56.390 --> 12:10:56.400 align:start position:0% switch can not only look at the MAC 12:10:56.400 --> 12:10:58.606 align:start position:0% switch can not only look at the MAC address 12:10:58.606 --> 12:10:58.616 align:start position:0% address 12:10:58.616 --> 12:11:01.010 align:start position:0% address but<12:10:59.096> a<12:10:59.400> multi-layer<12:11:00.060> switch<12:11:00.240> one<12:11:00.840> that 12:11:01.010 --> 12:11:01.020 align:start position:0% but a multi-layer switch one that 12:11:01.020 --> 12:11:02.870 align:start position:0% but a multi-layer switch one that operates<12:11:01.436> not<12:11:01.680> only<12:11:01.800> in<12:11:01.916> Layer<12:11:02.160> Two<12:11:02.276> but<12:11:02.580> also 12:11:02.870 --> 12:11:02.880 align:start position:0% operates not only in Layer Two but also 12:11:02.880 --> 12:11:04.426 align:start position:0% operates not only in Layer Two but also on<12:11:03.060> layer<12:11:03.416> three 12:11:04.426 --> 12:11:04.436 align:start position:0% on layer three 12:11:04.436 --> 12:11:09.350 align:start position:0% on layer three can<12:11:04.740> also<12:11:04.980> look<12:11:05.160> at<12:11:05.340> IP<12:11:06.000> addresses 12:11:09.350 --> 12:11:09.360 align:start position:0% 12:11:09.360 --> 12:11:13.550 align:start position:0% so<12:11:09.840> because<12:11:10.256> this<12:11:11.096> switch<12:11:11.660> operates<12:11:12.660> as<12:11:13.256> both 12:11:13.550 --> 12:11:13.560 align:start position:0% so because this switch operates as both 12:11:13.560 --> 12:11:17.570 align:start position:0% so because this switch operates as both a<12:11:14.580> router<12:11:15.240> and<12:11:15.480> a<12:11:15.660> switch<12:11:15.840> it<12:11:16.680> can<12:11:16.916> send 12:11:17.570 --> 12:11:17.580 align:start position:0% a router and a switch it can send 12:11:17.580 --> 12:11:19.310 align:start position:0% a router and a switch it can send information<12:11:17.880> between<12:11:18.540> several<12:11:19.140> different 12:11:19.310 --> 12:11:19.320 align:start position:0% information between several different 12:11:19.320 --> 12:11:21.350 align:start position:0% information between several different networks<12:11:19.916> so<12:11:20.400> here<12:11:20.640> for<12:11:20.880> instance<12:11:21.060> I<12:11:21.240> have 12:11:21.350 --> 12:11:21.360 align:start position:0% networks so here for instance I have 12:11:21.360 --> 12:11:24.106 align:start position:0% networks so here for instance I have Network<12:11:21.596> a<12:11:22.080> and<12:11:22.616> network<12:11:22.860> B<12:11:23.160> and<12:11:23.756> let's<12:11:23.936> see 12:11:24.106 --> 12:11:24.116 align:start position:0% Network a and network B and let's see 12:11:24.116 --> 12:11:27.710 align:start position:0% Network a and network B and let's see this<12:11:24.480> PC<12:11:24.900> wants<12:11:25.860> to<12:11:25.980> talk<12:11:26.160> with<12:11:26.400> the<12:11:26.640> server 12:11:27.710 --> 12:11:27.720 align:start position:0% this PC wants to talk with the server 12:11:27.720 --> 12:11:31.850 align:start position:0% this PC wants to talk with the server on<12:11:28.320> network<12:11:28.500> B<12:11:28.980> in<12:11:29.936> the<12:11:30.060> old<12:11:30.180> system<12:11:30.480> uh<12:11:31.436> unless 12:11:31.850 --> 12:11:31.860 align:start position:0% on network B in the old system uh unless 12:11:31.860 --> 12:11:34.370 align:start position:0% on network B in the old system uh unless network<12:11:32.340> uh<12:11:33.180> unless<12:11:33.540> the<12:11:33.720> server<12:11:34.080> was 12:11:34.370 --> 12:11:34.380 align:start position:0% network uh unless the server was 12:11:34.380 --> 12:11:36.406 align:start position:0% network uh unless the server was actually<12:11:34.740> connected<12:11:35.400> directly<12:11:35.936> to<12:11:36.240> the 12:11:36.406 --> 12:11:36.416 align:start position:0% actually connected directly to the 12:11:36.416 --> 12:11:38.690 align:start position:0% actually connected directly to the switch<12:11:36.596> there<12:11:37.200> would<12:11:37.320> be<12:11:37.500> no<12:11:37.740> way<12:11:37.980> for<12:11:38.400> the<12:11:38.580> two 12:11:38.690 --> 12:11:38.700 align:start position:0% switch there would be no way for the two 12:11:38.700 --> 12:11:40.370 align:start position:0% switch there would be no way for the two networks<12:11:39.180> to<12:11:39.416> sort<12:11:39.540> of<12:11:39.660> speak<12:11:39.840> to<12:11:40.020> one<12:11:40.200> another 12:11:40.370 --> 12:11:40.380 align:start position:0% networks to sort of speak to one another 12:11:40.380 --> 12:11:43.370 align:start position:0% networks to sort of speak to one another but<12:11:41.040> because<12:11:41.220> we<12:11:41.700> have<12:11:41.820> a<12:11:42.060> device<12:11:42.240> here 12:11:43.370 --> 12:11:43.380 align:start position:0% but because we have a device here 12:11:43.380 --> 12:11:46.790 align:start position:0% but because we have a device here that's<12:11:43.800> perhaps<12:11:44.220> operating<12:11:44.756> as<12:11:45.240> a<12:11:45.596> switch<12:11:45.800> and 12:11:46.790 --> 12:11:46.800 align:start position:0% that's perhaps operating as a switch and 12:11:46.800 --> 12:11:48.530 align:start position:0% that's perhaps operating as a switch and a<12:11:46.980> router 12:11:48.530 --> 12:11:48.540 align:start position:0% a router 12:11:48.540 --> 12:11:51.766 align:start position:0% a router it<12:11:49.140> can<12:11:49.380> route<12:11:50.220> the<12:11:50.520> data<12:11:50.880> onto<12:11:51.360> a<12:11:51.596> different 12:11:51.766 --> 12:11:51.776 align:start position:0% it can route the data onto a different 12:11:51.776 --> 12:11:57.170 align:start position:0% it can route the data onto a different network<12:11:52.580> using<12:11:53.580> an<12:11:54.116> IP<12:11:54.480> address 12:11:57.170 --> 12:11:57.180 align:start position:0% 12:11:57.180 --> 12:11:59.390 align:start position:0% in<12:11:57.900> some<12:11:58.020> ways<12:11:58.380> you<12:11:58.616> could<12:11:58.680> think<12:11:58.860> about<12:11:58.980> this 12:11:59.390 --> 12:11:59.400 align:start position:0% in some ways you could think about this 12:11:59.400 --> 12:12:03.586 align:start position:0% in some ways you could think about this as<12:11:59.880> the<12:12:00.116> Advent<12:12:00.240> of<12:12:00.776> the<12:12:01.256> area<12:12:01.436> code 12:12:03.586 --> 12:12:03.596 align:start position:0% as the Advent of the area code 12:12:03.596 --> 12:12:05.570 align:start position:0% as the Advent of the area code when<12:12:04.020> we<12:12:04.200> had<12:12:04.320> a<12:12:04.500> phone<12:12:04.616> number 12:12:05.570 --> 12:12:05.580 align:start position:0% when we had a phone number 12:12:05.580 --> 12:12:07.850 align:start position:0% when we had a phone number which<12:12:06.060> was<12:12:06.240> only 12:12:07.850 --> 12:12:07.860 align:start position:0% which was only 12:12:07.860 --> 12:12:11.210 align:start position:0% which was only five<12:12:08.460> digits<12:12:08.936> or<12:12:09.360> uh<12:12:09.960> sorry<12:12:10.140> seven<12:12:10.680> digits 12:12:11.210 --> 12:12:11.220 align:start position:0% five digits or uh sorry seven digits 12:12:11.220 --> 12:12:13.310 align:start position:0% five digits or uh sorry seven digits such<12:12:11.880> as 12:12:13.310 --> 12:12:13.320 align:start position:0% such as 12:12:13.320 --> 12:12:15.246 align:start position:0% such as um seven<12:12:13.916> two<12:12:14.276> three 12:12:15.246 --> 12:12:15.256 align:start position:0% um seven two three 12:12:15.256 --> 12:12:18.830 align:start position:0% um seven two three five<12:12:16.256> four<12:12:16.740> one<12:12:17.040> one<12:12:17.340> we<12:12:18.180> could<12:12:18.300> talk<12:12:18.596> to 12:12:18.830 --> 12:12:18.840 align:start position:0% five four one one we could talk to 12:12:18.840 --> 12:12:21.470 align:start position:0% five four one one we could talk to anyone<12:12:19.200> within<12:12:19.916> our<12:12:20.160> local<12:12:20.460> network<12:12:20.820> if<12:12:21.360> we 12:12:21.470 --> 12:12:21.480 align:start position:0% anyone within our local network if we 12:12:21.480 --> 12:12:22.490 align:start position:0% anyone within our local network if we knew 12:12:22.490 --> 12:12:22.500 align:start position:0% knew 12:12:22.500 --> 12:12:25.246 align:start position:0% knew this<12:12:23.276> number<12:12:23.520> when<12:12:24.116> we<12:12:24.240> added<12:12:24.540> the<12:12:24.720> area<12:12:24.960> code 12:12:25.246 --> 12:12:25.256 align:start position:0% this number when we added the area code 12:12:25.256 --> 12:12:28.010 align:start position:0% this number when we added the area code we<12:12:25.740> were<12:12:25.860> allowed<12:12:26.220> to<12:12:26.520> then<12:12:26.936> dial<12:12:27.240> out<12:12:27.840> to 12:12:28.010 --> 12:12:28.020 align:start position:0% we were allowed to then dial out to 12:12:28.020 --> 12:12:30.586 align:start position:0% we were allowed to then dial out to other<12:12:28.200> states<12:12:28.640> and<12:12:29.640> then<12:12:29.756> we<12:12:30.000> were<12:12:30.116> allowed<12:12:30.416> by 12:12:30.586 --> 12:12:30.596 align:start position:0% other states and then we were allowed by 12:12:30.596 --> 12:12:32.630 align:start position:0% other states and then we were allowed by putting<12:12:30.840> an<12:12:30.960> international<12:12:31.140> code<12:12:31.740> to<12:12:32.460> dial 12:12:32.630 --> 12:12:32.640 align:start position:0% putting an international code to dial 12:12:32.640 --> 12:12:35.150 align:start position:0% putting an international code to dial out<12:12:33.060> to<12:12:33.240> different<12:12:33.416> countries<12:12:34.020> so<12:12:34.916> we're 12:12:35.150 --> 12:12:35.160 align:start position:0% out to different countries so we're 12:12:35.160 --> 12:12:36.766 align:start position:0% out to different countries so we're allowed<12:12:35.460> to<12:12:35.520> go<12:12:35.640> then<12:12:35.820> outside<12:12:36.240> of<12:12:36.596> our 12:12:36.766 --> 12:12:36.776 align:start position:0% allowed to go then outside of our 12:12:36.776 --> 12:12:39.470 align:start position:0% allowed to go then outside of our specific<12:12:37.200> Network<12:12:37.616> in<12:12:38.400> this<12:12:38.640> way<12:12:38.820> we're<12:12:39.300> not 12:12:39.470 --> 12:12:39.480 align:start position:0% specific Network in this way we're not 12:12:39.480 --> 12:12:41.510 align:start position:0% specific Network in this way we're not just<12:12:39.660> dealing<12:12:39.900> with<12:12:40.140> Mac<12:12:40.380> addresses<12:12:40.980> we're 12:12:41.510 --> 12:12:41.520 align:start position:0% just dealing with Mac addresses we're 12:12:41.520 --> 12:12:43.906 align:start position:0% just dealing with Mac addresses we're dealing<12:12:41.880> with<12:12:42.116> IP<12:12:42.720> addresses<12:12:43.200> and<12:12:43.380> as<12:12:43.560> we've 12:12:43.906 --> 12:12:43.916 align:start position:0% dealing with IP addresses and as we've 12:12:43.916 --> 12:12:46.490 align:start position:0% dealing with IP addresses and as we've talked<12:12:44.220> about<12:12:44.340> IP<12:12:45.180> addresses 12:12:46.490 --> 12:12:46.500 align:start position:0% talked about IP addresses 12:12:46.500 --> 12:12:49.426 align:start position:0% talked about IP addresses are<12:12:47.160> assigned<12:12:47.700> by<12:12:48.300> for<12:12:48.480> instance<12:12:48.596> a<12:12:48.840> DHCP 12:12:49.426 --> 12:12:49.436 align:start position:0% are assigned by for instance a DHCP 12:12:49.436 --> 12:12:51.530 align:start position:0% are assigned by for instance a DHCP server<12:12:49.860> and<12:12:50.160> so<12:12:50.340> as<12:12:50.460> a<12:12:50.640> result<12:12:50.820> they're<12:12:51.360> more 12:12:51.530 --> 12:12:51.540 align:start position:0% server and so as a result they're more 12:12:51.540 --> 12:12:53.510 align:start position:0% server and so as a result they're more temporary<12:12:52.020> they're<12:12:52.560> not<12:12:52.680> hardwired<12:12:53.160> onto<12:12:53.400> the 12:12:53.510 --> 12:12:53.520 align:start position:0% temporary they're not hardwired onto the 12:12:53.520 --> 12:12:55.310 align:start position:0% temporary they're not hardwired onto the device<12:12:53.640> and<12:12:54.540> it<12:12:54.720> not<12:12:54.840> only<12:12:54.900> allows<12:12:55.200> for 12:12:55.310 --> 12:12:55.320 align:start position:0% device and it not only allows for 12:12:55.320 --> 12:12:56.926 align:start position:0% device and it not only allows for routing<12:12:55.740> but<12:12:56.040> it<12:12:56.160> makes<12:12:56.276> it<12:12:56.460> a<12:12:56.580> little<12:12:56.580> more 12:12:56.926 --> 12:12:56.936 align:start position:0% routing but it makes it a little more 12:12:56.936 --> 12:12:59.030 align:start position:0% routing but it makes it a little more complex<12:12:57.720> to<12:12:58.020> figure<12:12:58.140> out<12:12:58.256> where<12:12:58.560> a<12:12:58.680> device<12:12:58.800> is 12:12:59.030 --> 12:12:59.040 align:start position:0% complex to figure out where a device is 12:12:59.040 --> 12:13:00.650 align:start position:0% complex to figure out where a device is at<12:12:59.160> any<12:12:59.340> one<12:12:59.520> time<12:12:59.700> we'll<12:13:00.116> talk<12:13:00.300> more<12:13:00.480> about 12:13:00.650 --> 12:13:00.660 align:start position:0% at any one time we'll talk more about 12:13:00.660 --> 12:13:02.630 align:start position:0% at any one time we'll talk more about that<12:13:00.900> in<12:13:01.080> the<12:13:01.200> next<12:13:01.380> module<12:13:01.800> the<12:13:02.340> important 12:13:02.630 --> 12:13:02.640 align:start position:0% that in the next module the important 12:13:02.640 --> 12:13:05.510 align:start position:0% that in the next module the important thing<12:13:02.756> here<12:13:02.936> to<12:13:03.180> realize<12:13:03.480> though<12:13:03.840> is<12:13:04.560> that<12:13:05.220> a 12:13:05.510 --> 12:13:05.520 align:start position:0% thing here to realize though is that a 12:13:05.520 --> 12:13:08.330 align:start position:0% thing here to realize though is that a multi-layer<12:13:06.240> switch<12:13:06.416> operates<12:13:07.200> both<12:13:07.560> as<12:13:08.160> a 12:13:08.330 --> 12:13:08.340 align:start position:0% multi-layer switch operates both as a 12:13:08.340 --> 12:13:09.290 align:start position:0% multi-layer switch operates both as a router 12:13:09.290 --> 12:13:09.300 align:start position:0% router 12:13:09.300 --> 12:13:12.470 align:start position:0% router and<12:13:09.900> as<12:13:10.140> a<12:13:10.320> switch<12:13:10.500> because<12:13:11.340> it<12:13:12.116> works<12:13:12.360> on 12:13:12.470 --> 12:13:12.480 align:start position:0% and as a switch because it works on 12:13:12.480 --> 12:13:16.010 align:start position:0% and as a switch because it works on layer<12:13:12.840> 3<12:13:13.020> and<12:13:13.980> layer<12:13:14.460> 2<12:13:14.580> which<12:13:15.360> means<12:13:15.660> it<12:13:15.840> not 12:13:16.010 --> 12:13:16.020 align:start position:0% layer 3 and layer 2 which means it not 12:13:16.020 --> 12:13:17.330 align:start position:0% layer 3 and layer 2 which means it not only<12:13:16.140> reads 12:13:17.330 --> 12:13:17.340 align:start position:0% only reads 12:13:17.340 --> 12:13:19.070 align:start position:0% only reads Mac<12:13:17.936> addresses 12:13:19.070 --> 12:13:19.080 align:start position:0% Mac addresses 12:13:19.080 --> 12:13:24.406 align:start position:0% Mac addresses but<12:13:19.680> also<12:13:19.980> IP<12:13:20.880> addresses 12:13:24.406 --> 12:13:24.416 align:start position:0% 12:13:24.416 --> 12:13:25.906 align:start position:0% now<12:13:24.776> the<12:13:24.900> next<12:13:25.020> type<12:13:25.200> of<12:13:25.256> switch<12:13:25.436> I<12:13:25.680> want<12:13:25.800> to 12:13:25.906 --> 12:13:25.916 align:start position:0% now the next type of switch I want to 12:13:25.916 --> 12:13:27.710 align:start position:0% now the next type of switch I want to mention<12:13:26.040> is<12:13:26.340> something<12:13:26.520> called<12:13:26.880> a<12:13:27.240> Content 12:13:27.710 --> 12:13:27.720 align:start position:0% mention is something called a Content 12:13:27.720 --> 12:13:30.106 align:start position:0% mention is something called a Content switch<12:13:28.080> the<12:13:28.740> name<12:13:28.916> content<12:13:29.520> should<12:13:29.756> give<12:13:29.936> away 12:13:30.106 --> 12:13:30.116 align:start position:0% switch the name content should give away 12:13:30.116 --> 12:13:32.150 align:start position:0% switch the name content should give away what<12:13:30.416> we're<12:13:30.596> about<12:13:30.720> to<12:13:30.900> talk<12:13:31.020> about<12:13:31.200> here<12:13:31.560> now 12:13:32.150 --> 12:13:32.160 align:start position:0% what we're about to talk about here now 12:13:32.160 --> 12:13:34.130 align:start position:0% what we're about to talk about here now these<12:13:32.460> are<12:13:32.580> not<12:13:32.756> really<12:13:33.116> used<12:13:33.360> as<12:13:33.596> much<12:13:33.776> as<12:13:33.900> we 12:13:34.130 --> 12:13:34.140 align:start position:0% these are not really used as much as we 12:13:34.140 --> 12:13:36.290 align:start position:0% these are not really used as much as we see<12:13:34.380> in<12:13:34.860> today's<12:13:35.040> networks<12:13:35.700> because<12:13:35.936> they're 12:13:36.290 --> 12:13:36.300 align:start position:0% see in today's networks because they're 12:13:36.300 --> 12:13:39.890 align:start position:0% see in today's networks because they're quite<12:13:36.596> costly<12:13:37.080> but<12:13:37.800> a<12:13:38.580> Content<12:13:39.240> switch<12:13:39.480> will 12:13:39.890 --> 12:13:39.900 align:start position:0% quite costly but a Content switch will 12:13:39.900 --> 12:13:42.106 align:start position:0% quite costly but a Content switch will actually<12:13:40.140> analyze<12:13:40.916> the<12:13:41.096> data<12:13:41.400> it<12:13:41.700> receives 12:13:42.106 --> 12:13:42.116 align:start position:0% actually analyze the data it receives 12:13:42.116 --> 12:13:45.650 align:start position:0% actually analyze the data it receives and<12:13:42.900> forward<12:13:43.140> it<12:13:43.436> based<12:13:43.860> on<12:13:44.040> its<12:13:44.880> content<12:13:45.300> only 12:13:45.650 --> 12:13:45.660 align:start position:0% and forward it based on its content only 12:13:45.660 --> 12:13:49.190 align:start position:0% and forward it based on its content only so<12:13:46.256> rather<12:13:46.560> than<12:13:46.680> dealing<12:13:47.640> with<12:13:48.416> simply<12:13:48.776> an<12:13:48.960> IP 12:13:49.190 --> 12:13:49.200 align:start position:0% so rather than dealing with simply an IP 12:13:49.200 --> 12:13:51.470 align:start position:0% so rather than dealing with simply an IP address<12:13:49.436> or<12:13:49.800> Mac<12:13:49.980> address<12:13:50.220> it<12:13:50.936> actually<12:13:51.060> looks 12:13:51.470 --> 12:13:51.480 align:start position:0% address or Mac address it actually looks 12:13:51.480 --> 12:13:53.926 align:start position:0% address or Mac address it actually looks at<12:13:51.660> what's<12:13:52.380> inside 12:13:53.926 --> 12:13:53.936 align:start position:0% at what's inside 12:13:53.936 --> 12:13:57.170 align:start position:0% at what's inside of<12:13:54.540> the<12:13:54.660> of<12:13:55.020> the<12:13:55.320> packet<12:13:55.980> if<12:13:56.520> we<12:13:56.640> have<12:13:56.820> a<12:13:57.000> MAC 12:13:57.170 --> 12:13:57.180 align:start position:0% of the of the packet if we have a MAC 12:13:57.180 --> 12:13:59.746 align:start position:0% of the of the packet if we have a MAC address<12:13:57.416> here<12:13:58.140> and<12:13:58.740> then<12:13:58.916> we<12:13:59.160> put<12:13:59.276> an<12:13:59.400> IP 12:13:59.746 --> 12:13:59.756 align:start position:0% address here and then we put an IP 12:13:59.756 --> 12:14:01.370 align:start position:0% address here and then we put an IP address<12:13:59.936> on<12:14:00.240> the<12:14:00.360> outside<12:14:00.480> of<12:14:00.840> that<12:14:01.020> in<12:14:01.256> order 12:14:01.370 --> 12:14:01.380 align:start position:0% address on the outside of that in order 12:14:01.380 --> 12:14:03.230 align:start position:0% address on the outside of that in order to<12:14:01.560> tell<12:14:01.800> where<12:14:02.096> to<12:14:02.220> go<12:14:02.340> it's<12:14:02.880> actually<12:14:03.060> going 12:14:03.230 --> 12:14:03.240 align:start position:0% to tell where to go it's actually going 12:14:03.240 --> 12:14:05.990 align:start position:0% to tell where to go it's actually going to<12:14:03.360> look<12:14:03.540> inside<12:14:03.840> and<12:14:04.200> look<12:14:04.380> at<12:14:04.500> the<12:14:04.740> data<12:14:05.460> and 12:14:05.990 --> 12:14:06.000 align:start position:0% to look inside and look at the data and 12:14:06.000 --> 12:14:08.330 align:start position:0% to look inside and look at the data and determine<12:14:06.416> where<12:14:07.200> that<12:14:07.436> content<12:14:07.800> is<12:14:08.040> going<12:14:08.160> to 12:14:08.330 --> 12:14:08.340 align:start position:0% determine where that content is going to 12:14:08.340 --> 12:14:08.990 align:start position:0% determine where that content is going to go 12:14:08.990 --> 12:14:09.000 align:start position:0% go 12:14:09.000 --> 12:14:11.350 align:start position:0% go these<12:14:09.480> switches<12:14:09.840> are<12:14:10.020> also<12:14:10.256> sometimes<12:14:10.680> called 12:14:11.350 --> 12:14:11.360 align:start position:0% these switches are also sometimes called 12:14:11.360 --> 12:14:15.170 align:start position:0% these switches are also sometimes called load<12:14:12.360> bearing<12:14:13.200> switches 12:14:15.170 --> 12:14:15.180 align:start position:0% load bearing switches 12:14:15.180 --> 12:14:18.426 align:start position:0% load bearing switches because<12:14:15.720> they<12:14:16.080> can<12:14:16.256> evenly<12:14:16.740> distribute<12:14:17.276> data 12:14:18.426 --> 12:14:18.436 align:start position:0% because they can evenly distribute data 12:14:18.436 --> 12:14:20.690 align:start position:0% because they can evenly distribute data based<12:14:19.436> on<12:14:19.500> the<12:14:19.740> type<12:14:19.860> of<12:14:19.980> data<12:14:20.220> there<12:14:20.400> is<12:14:20.520> in 12:14:20.690 --> 12:14:20.700 align:start position:0% based on the type of data there is in 12:14:20.700 --> 12:14:22.490 align:start position:0% based on the type of data there is in the<12:14:20.880> appropriate<12:14:21.240> destinations<12:14:21.720> which<12:14:22.320> can 12:14:22.490 --> 12:14:22.500 align:start position:0% the appropriate destinations which can 12:14:22.500 --> 12:14:25.130 align:start position:0% the appropriate destinations which can alleviate<12:14:23.220> stress<12:14:23.580> on<12:14:23.820> a<12:14:24.060> single<12:14:24.300> server<12:14:24.776> or 12:14:25.130 --> 12:14:25.140 align:start position:0% alleviate stress on a single server or 12:14:25.140 --> 12:14:26.150 align:start position:0% alleviate stress on a single server or device 12:14:26.150 --> 12:14:26.160 align:start position:0% device 12:14:26.160 --> 12:14:28.606 align:start position:0% device so<12:14:26.700> for<12:14:26.936> instance<12:14:27.240> if<12:14:27.720> I<12:14:27.900> erase<12:14:28.140> all<12:14:28.320> this<12:14:28.500> for 12:14:28.606 --> 12:14:28.616 align:start position:0% so for instance if I erase all this for 12:14:28.616 --> 12:14:30.290 align:start position:0% so for instance if I erase all this for a<12:14:28.740> second<12:14:28.860> let's<12:14:29.160> say<12:14:29.276> we<12:14:29.580> have 12:14:30.290 --> 12:14:30.300 align:start position:0% a second let's say we have 12:14:30.300 --> 12:14:32.330 align:start position:0% a second let's say we have for<12:14:30.840> some<12:14:31.020> reason<12:14:31.200> and<12:14:31.616> let's<12:14:31.800> say<12:14:31.916> we<12:14:32.096> have<12:14:32.160> a 12:14:32.330 --> 12:14:32.340 align:start position:0% for some reason and let's say we have a 12:14:32.340 --> 12:14:34.130 align:start position:0% for some reason and let's say we have a router<12:14:32.640> right<12:14:32.880> here<12:14:33.116> which<12:14:33.540> allows<12:14:33.840> us<12:14:33.960> to 12:14:34.130 --> 12:14:34.140 align:start position:0% router right here which allows us to 12:14:34.140 --> 12:14:36.050 align:start position:0% router right here which allows us to connect<12:14:34.256> out<12:14:34.560> to<12:14:34.740> the<12:14:34.860> internet<12:14:35.040> and<12:14:35.936> then 12:14:36.050 --> 12:14:36.060 align:start position:0% connect out to the internet and then 12:14:36.060 --> 12:14:37.850 align:start position:0% connect out to the internet and then information<12:14:36.480> comes<12:14:37.140> in<12:14:37.256> straight<12:14:37.560> from<12:14:37.740> the 12:14:37.850 --> 12:14:37.860 align:start position:0% information comes in straight from the 12:14:37.860 --> 12:14:39.890 align:start position:0% information comes in straight from the router<12:14:38.096> to<12:14:38.220> the<12:14:38.400> content<12:14:38.756> switch<12:14:39.060> and<12:14:39.720> we 12:14:39.890 --> 12:14:39.900 align:start position:0% router to the content switch and we 12:14:39.900 --> 12:14:41.746 align:start position:0% router to the content switch and we don't<12:14:40.020> know<12:14:40.256> where<12:14:40.616> the<12:14:40.800> information<12:14:40.980> is<12:14:41.520> set 12:14:41.746 --> 12:14:41.756 align:start position:0% don't know where the information is set 12:14:41.756 --> 12:14:44.926 align:start position:0% don't know where the information is set for<12:14:42.000> or<12:14:42.776> let's<12:14:43.140> say<12:14:43.320> we<12:14:43.616> have 12:14:44.926 --> 12:14:44.936 align:start position:0% for or let's say we have 12:14:44.936 --> 12:14:47.570 align:start position:0% for or let's say we have six<12:14:45.480> different<12:14:45.720> clients<12:14:46.500> or<12:14:46.916> servers<12:14:47.460> it 12:14:47.570 --> 12:14:47.580 align:start position:0% six different clients or servers it 12:14:47.580 --> 12:14:49.246 align:start position:0% six different clients or servers it doesn't<12:14:47.700> really<12:14:47.936> matter<12:14:48.180> that<12:14:48.840> each<12:14:49.020> could 12:14:49.246 --> 12:14:49.256 align:start position:0% doesn't really matter that each could 12:14:49.256 --> 12:14:52.670 align:start position:0% doesn't really matter that each could operate<12:14:49.740> under<12:14:50.276> the<12:14:50.640> same<12:14:50.936> sort<12:14:51.540> of<12:14:51.776> IP 12:14:52.670 --> 12:14:52.680 align:start position:0% operate under the same sort of IP 12:14:52.680 --> 12:14:54.766 align:start position:0% operate under the same sort of IP address<12:14:52.860> for<12:14:53.400> instance<12:14:53.580> we're<12:14:53.936> going<12:14:54.116> to<12:14:54.240> put 12:14:54.766 --> 12:14:54.776 align:start position:0% address for instance we're going to put 12:14:54.776 --> 12:14:56.510 align:start position:0% address for instance we're going to put them<12:14:54.960> all<12:14:55.080> together<12:14:55.256> or<12:14:55.616> group<12:14:55.800> them<12:14:56.040> the 12:14:56.510 --> 12:14:56.520 align:start position:0% them all together or group them the 12:14:56.520 --> 12:14:58.550 align:start position:0% them all together or group them the content<12:14:56.880> switch<12:14:57.116> can<12:14:57.480> say<12:14:57.720> which<12:14:58.140> one<12:14:58.320> it's 12:14:58.550 --> 12:14:58.560 align:start position:0% content switch can say which one it's 12:14:58.560 --> 12:15:00.470 align:start position:0% content switch can say which one it's going<12:14:58.740> to<12:14:58.860> go<12:14:59.040> to<12:14:59.220> based<12:15:00.060> on<12:15:00.116> the<12:15:00.240> type<12:15:00.360> of 12:15:00.470 --> 12:15:00.480 align:start position:0% going to go to based on the type of 12:15:00.480 --> 12:15:02.266 align:start position:0% going to go to based on the type of information<12:15:00.660> it's<12:15:01.080> receiving<12:15:01.436> so<12:15:02.040> for 12:15:02.266 --> 12:15:02.276 align:start position:0% information it's receiving so for 12:15:02.276 --> 12:15:04.490 align:start position:0% information it's receiving so for instance<12:15:02.580> email<12:15:03.060> is<12:15:03.840> probably<12:15:04.020> going<12:15:04.200> to<12:15:04.380> go 12:15:04.490 --> 12:15:04.500 align:start position:0% instance email is probably going to go 12:15:04.500 --> 12:15:07.190 align:start position:0% instance email is probably going to go to<12:15:04.680> one<12:15:04.916> computer<12:15:05.160> whereas<12:15:06.116> web<12:15:06.540> is<12:15:07.020> going<12:15:07.200> to 12:15:07.190 --> 12:15:07.200 align:start position:0% to one computer whereas web is going to 12:15:07.200 --> 12:15:09.050 align:start position:0% to one computer whereas web is going to go<12:15:07.320> to<12:15:07.436> another<12:15:07.616> whereas<12:15:08.096> the<12:15:08.220> FTP<12:15:08.640> might<12:15:08.820> go 12:15:09.050 --> 12:15:09.060 align:start position:0% go to another whereas the FTP might go 12:15:09.060 --> 12:15:11.150 align:start position:0% go to another whereas the FTP might go to<12:15:09.116> another<12:15:09.300> and<12:15:10.020> the<12:15:10.256> packet<12:15:10.616> itself<12:15:10.916> doesn't 12:15:11.150 --> 12:15:11.160 align:start position:0% to another and the packet itself doesn't 12:15:11.160 --> 12:15:12.586 align:start position:0% to another and the packet itself doesn't have<12:15:11.400> to<12:15:11.520> know<12:15:11.640> which<12:15:11.880> computer<12:15:12.060> it's<12:15:12.360> going 12:15:12.586 --> 12:15:12.596 align:start position:0% have to know which computer it's going 12:15:12.596 --> 12:15:15.586 align:start position:0% have to know which computer it's going to<12:15:12.776> the<12:15:13.500> packet<12:15:13.860> just<12:15:14.160> has<12:15:14.400> to<12:15:14.580> have<12:15:14.820> an<12:15:15.300> IP 12:15:15.586 --> 12:15:15.596 align:start position:0% to the packet just has to have an IP 12:15:15.596 --> 12:15:18.230 align:start position:0% to the packet just has to have an IP address<12:15:15.840> and<12:15:16.436> or<12:15:16.680> Mac<12:15:16.980> address<12:15:17.160> and<12:15:17.880> then<12:15:18.000> the 12:15:18.230 --> 12:15:18.240 align:start position:0% address and or Mac address and then the 12:15:18.240 --> 12:15:20.030 align:start position:0% address and or Mac address and then the contents<12:15:18.660> which<12:15:18.840> itself<12:15:19.200> based<12:15:19.800> on<12:15:19.860> the 12:15:20.030 --> 12:15:20.040 align:start position:0% contents which itself based on the 12:15:20.040 --> 12:15:21.106 align:start position:0% contents which itself based on the content<12:15:20.276> is<12:15:20.400> going<12:15:20.580> to<12:15:20.640> send<12:15:20.756> that<12:15:20.936> over 12:15:21.106 --> 12:15:21.116 align:start position:0% content is going to send that over 12:15:21.116 --> 12:15:23.570 align:start position:0% content is going to send that over another<12:15:21.776> way<12:15:22.080> to<12:15:22.200> think<12:15:22.436> about<12:15:22.616> this<12:15:22.916> is<12:15:23.400> if 12:15:23.570 --> 12:15:23.580 align:start position:0% another way to think about this is if 12:15:23.580 --> 12:15:26.870 align:start position:0% another way to think about this is if I'm<12:15:23.756> dealing<12:15:24.116> with<12:15:24.416> some<12:15:24.720> sort<12:15:24.900> of<12:15:25.020> firewall 12:15:26.870 --> 12:15:26.880 align:start position:0% I'm dealing with some sort of firewall 12:15:26.880 --> 12:15:31.070 align:start position:0% I'm dealing with some sort of firewall and<12:15:27.480> I<12:15:27.720> want<12:15:27.840> the<12:15:28.140> firewall<12:15:28.756> to<12:15:29.776> put<12:15:30.776> certain 12:15:31.070 --> 12:15:31.080 align:start position:0% and I want the firewall to put certain 12:15:31.080 --> 12:15:33.830 align:start position:0% and I want the firewall to put certain types<12:15:31.436> of<12:15:31.500> data<12:15:31.916> into<12:15:32.580> a 12:15:33.830 --> 12:15:33.840 align:start position:0% types of data into a 12:15:33.840 --> 12:15:35.210 align:start position:0% types of data into a um 12:15:35.210 --> 12:15:35.220 align:start position:0% um 12:15:35.220 --> 12:15:36.950 align:start position:0% um filtered 12:15:36.950 --> 12:15:36.960 align:start position:0% filtered 12:15:36.960 --> 12:15:38.266 align:start position:0% filtered area 12:15:38.266 --> 12:15:38.276 align:start position:0% area 12:15:38.276 --> 12:15:40.730 align:start position:0% area that<12:15:38.700> needs<12:15:38.936> to<12:15:39.000> be<12:15:39.116> scanned<12:15:39.540> for<12:15:39.776> viruses<12:15:40.320> so 12:15:40.730 --> 12:15:40.740 align:start position:0% that needs to be scanned for viruses so 12:15:40.740 --> 12:15:41.870 align:start position:0% that needs to be scanned for viruses so this<12:15:40.916> is<12:15:40.980> really<12:15:41.160> going<12:15:41.400> to<12:15:41.520> help<12:15:41.640> me 12:15:41.870 --> 12:15:41.880 align:start position:0% this is really going to help me 12:15:41.880 --> 12:15:46.246 align:start position:0% this is really going to help me alleviate<12:15:42.720> uh<12:15:43.140> certain<12:15:43.500> processes 12:15:46.246 --> 12:15:46.256 align:start position:0% alleviate uh certain processes 12:15:46.256 --> 12:15:48.650 align:start position:0% alleviate uh certain processes and<12:15:46.616> also<12:15:46.800> help<12:15:46.980> keep<12:15:47.160> my<12:15:47.400> network<12:15:47.580> safer<12:15:48.416> and 12:15:48.650 --> 12:15:48.660 align:start position:0% and also help keep my network safer and 12:15:48.660 --> 12:15:50.030 align:start position:0% and also help keep my network safer and we'll<12:15:48.776> talk<12:15:48.900> about<12:15:49.020> other<12:15:49.256> devices<12:15:49.560> that<12:15:49.800> do 12:15:50.030 --> 12:15:50.040 align:start position:0% we'll talk about other devices that do 12:15:50.040 --> 12:15:51.106 align:start position:0% we'll talk about other devices that do this<12:15:50.160> as<12:15:50.340> well 12:15:51.106 --> 12:15:51.116 align:start position:0% this as well 12:15:51.116 --> 12:15:52.606 align:start position:0% this as well but<12:15:51.480> when<12:15:51.596> we're<12:15:51.720> dealing<12:15:51.960> with<12:15:52.020> the<12:15:52.200> content 12:15:52.606 --> 12:15:52.616 align:start position:0% but when we're dealing with the content 12:15:52.616 --> 12:15:54.950 align:start position:0% but when we're dealing with the content we're<12:15:53.040> dealing<12:15:53.400> with<12:15:53.580> further<12:15:53.936> up<12:15:54.116> on<12:15:54.480> the<12:15:54.540> OSI 12:15:54.950 --> 12:15:54.960 align:start position:0% we're dealing with further up on the OSI 12:15:54.960 --> 12:15:56.390 align:start position:0% we're dealing with further up on the OSI model<12:15:55.256> so<12:15:55.616> we're<12:15:55.800> not<12:15:55.916> just<12:15:56.040> dealing<12:15:56.276> with 12:15:56.390 --> 12:15:56.400 align:start position:0% model so we're not just dealing with 12:15:56.400 --> 12:15:58.906 align:start position:0% model so we're not just dealing with layer<12:15:56.700> one<12:15:56.880> or<12:15:57.116> two<12:15:57.360> or<12:15:58.020> three<12:15:58.320> even<12:15:58.500> we<12:15:58.800> might 12:15:58.906 --> 12:15:58.916 align:start position:0% layer one or two or three even we might 12:15:58.916 --> 12:16:01.070 align:start position:0% layer one or two or three even we might even<12:15:59.040> be<12:15:59.160> dealing<12:15:59.340> with<12:15:59.460> layer<12:15:59.880> four<12:16:00.060> to<12:16:00.840> some 12:16:01.070 --> 12:16:01.080 align:start position:0% even be dealing with layer four to some 12:16:01.080 --> 12:16:03.050 align:start position:0% even be dealing with layer four to some extent 12:16:03.050 --> 12:16:03.060 align:start position:0% extent 12:16:03.060 --> 12:16:05.570 align:start position:0% extent so<12:16:03.660> just<12:16:03.900> to<12:16:04.020> recap<12:16:04.380> we<12:16:04.980> first<12:16:05.096> talked<12:16:05.460> about 12:16:05.570 --> 12:16:05.580 align:start position:0% so just to recap we first talked about 12:16:05.580 --> 12:16:09.350 align:start position:0% so just to recap we first talked about what<12:16:06.000> a<12:16:06.116> switch<12:16:06.300> is<12:16:06.596> a<12:16:07.380> switch<12:16:07.800> again<12:16:08.360> allows 12:16:09.350 --> 12:16:09.360 align:start position:0% what a switch is a switch again allows 12:16:09.360 --> 12:16:12.470 align:start position:0% what a switch is a switch again allows for<12:16:09.720> a<12:16:09.960> direct<12:16:10.140> connection 12:16:12.470 --> 12:16:12.480 align:start position:0% for a direct connection 12:16:12.480 --> 12:16:13.850 align:start position:0% for a direct connection between 12:16:13.850 --> 12:16:13.860 align:start position:0% between 12:16:13.860 --> 12:16:20.150 align:start position:0% between two<12:16:14.220> devices 12:16:20.150 --> 12:16:20.160 align:start position:0% 12:16:20.160 --> 12:16:21.830 align:start position:0% or<12:16:20.640> more 12:16:21.830 --> 12:16:21.840 align:start position:0% or more 12:16:21.840 --> 12:16:23.390 align:start position:0% or more the<12:16:22.256> important<12:16:22.500> thing<12:16:22.616> to<12:16:22.800> hear<12:16:22.916> to<12:16:23.096> realize 12:16:23.390 --> 12:16:23.400 align:start position:0% the important thing to hear to realize 12:16:23.400 --> 12:16:25.550 align:start position:0% the important thing to hear to realize is<12:16:23.820> that<12:16:23.936> the<12:16:24.060> devices<12:16:24.300> communicate<12:16:25.020> directly 12:16:25.550 --> 12:16:25.560 align:start position:0% is that the devices communicate directly 12:16:25.560 --> 12:16:28.490 align:start position:0% is that the devices communicate directly because<12:16:25.980> the<12:16:26.276> switch<12:16:26.460> creates<12:16:27.240> a<12:16:27.360> circuit 12:16:28.490 --> 12:16:28.500 align:start position:0% because the switch creates a circuit 12:16:28.500 --> 12:16:31.906 align:start position:0% because the switch creates a circuit between<12:16:28.916> those<12:16:29.276> two<12:16:29.460> devices<12:16:29.756> Within 12:16:31.906 --> 12:16:31.916 align:start position:0% between those two devices Within 12:16:31.916 --> 12:16:35.450 align:start position:0% between those two devices Within a<12:16:32.340> box<12:16:32.520> based<12:16:33.480> on<12:16:33.540> ports 12:16:35.450 --> 12:16:35.460 align:start position:0% a box based on ports 12:16:35.460 --> 12:16:37.850 align:start position:0% a box based on ports now<12:16:36.000> how<12:16:36.180> it<12:16:36.360> does<12:16:36.540> this<12:16:36.720> is<12:16:37.080> it<12:16:37.256> creates<12:16:37.616> a 12:16:37.850 --> 12:16:37.860 align:start position:0% now how it does this is it creates a 12:16:37.860 --> 12:16:40.670 align:start position:0% now how it does this is it creates a table 12:16:40.670 --> 12:16:40.680 align:start position:0% 12:16:40.680 --> 12:16:43.790 align:start position:0% defining<12:16:41.520> which<12:16:41.936> ports<12:16:42.416> are<12:16:42.840> connected 12:16:43.790 --> 12:16:43.800 align:start position:0% defining which ports are connected 12:16:43.800 --> 12:16:46.550 align:start position:0% defining which ports are connected to<12:16:44.220> which<12:16:44.400> Mac<12:16:45.000> addresses<12:16:45.596> again<12:16:46.140> a<12:16:46.436> MAC 12:16:46.550 --> 12:16:46.560 align:start position:0% to which Mac addresses again a MAC 12:16:46.560 --> 12:16:49.550 align:start position:0% to which Mac addresses again a MAC address<12:16:46.800> is<12:16:47.276> the<12:16:47.580> physical<12:16:47.820> address<12:16:48.660> that's 12:16:49.550 --> 12:16:49.560 align:start position:0% address is the physical address that's 12:16:49.560 --> 12:16:52.970 align:start position:0% address is the physical address that's built<12:16:50.040> into<12:16:50.220> a<12:16:50.520> device<12:16:50.640> when<12:16:50.936> it's<12:16:51.116> made 12:16:52.970 --> 12:16:52.980 align:start position:0% built into a device when it's made 12:16:52.980 --> 12:16:55.730 align:start position:0% built into a device when it's made this<12:16:53.340> is<12:16:53.520> different<12:16:53.700> from<12:16:54.116> a<12:16:54.300> hub<12:16:54.480> which<12:16:55.436> just 12:16:55.730 --> 12:16:55.740 align:start position:0% this is different from a hub which just 12:16:55.740 --> 12:16:58.246 align:start position:0% this is different from a hub which just broadcasts<12:16:56.640> everything<12:16:56.936> so<12:16:57.776> if<12:16:57.900> we<12:16:58.080> were<12:16:58.140> to 12:16:58.246 --> 12:16:58.256 align:start position:0% broadcasts everything so if we were to 12:16:58.256 --> 12:17:00.586 align:start position:0% broadcasts everything so if we were to create<12:16:58.380> an<12:16:58.616> analogy<12:16:59.160> we<12:16:59.756> could<12:16:59.820> say<12:17:00.060> broadcast 12:17:00.586 --> 12:17:00.596 align:start position:0% create an analogy we could say broadcast 12:17:00.596 --> 12:17:03.050 align:start position:0% create an analogy we could say broadcast which<12:17:01.560> would<12:17:01.800> mean<12:17:01.916> all<12:17:02.160> the<12:17:02.340> data<12:17:02.640> going<12:17:02.820> out 12:17:03.050 --> 12:17:03.060 align:start position:0% which would mean all the data going out 12:17:03.060 --> 12:17:04.606 align:start position:0% which would mean all the data going out to<12:17:03.240> every<12:17:03.416> other<12:17:03.596> device 12:17:04.606 --> 12:17:04.616 align:start position:0% to every other device 12:17:04.616 --> 12:17:05.926 align:start position:0% to every other device is 12:17:05.926 --> 12:17:05.936 align:start position:0% is 12:17:05.936 --> 12:17:08.330 align:start position:0% is to<12:17:06.596> a<12:17:06.720> hub 12:17:08.330 --> 12:17:08.340 align:start position:0% to a hub 12:17:08.340 --> 12:17:11.150 align:start position:0% to a hub what<12:17:09.000> unicast 12:17:11.150 --> 12:17:11.160 align:start position:0% what unicast 12:17:11.160 --> 12:17:14.990 align:start position:0% what unicast or<12:17:11.880> multicast 12:17:14.990 --> 12:17:15.000 align:start position:0% 12:17:15.000 --> 12:17:17.390 align:start position:0% is 12:17:17.390 --> 12:17:17.400 align:start position:0% is 12:17:17.400 --> 12:17:19.670 align:start position:0% is to<12:17:17.820> a<12:17:17.936> switch 12:17:19.670 --> 12:17:19.680 align:start position:0% to a switch 12:17:19.680 --> 12:17:21.586 align:start position:0% to a switch we<12:17:20.040> also<12:17:20.276> looked<12:17:20.520> at<12:17:20.580> some<12:17:20.820> Advanced<12:17:21.240> switches 12:17:21.586 --> 12:17:21.596 align:start position:0% we also looked at some Advanced switches 12:17:21.596 --> 12:17:23.330 align:start position:0% we also looked at some Advanced switches you<12:17:21.720> need<12:17:21.840> to<12:17:21.960> know<12:17:22.080> about<12:17:22.200> the<12:17:22.800> first<12:17:22.916> is<12:17:23.096> a 12:17:23.330 --> 12:17:23.340 align:start position:0% you need to know about the first is a 12:17:23.340 --> 12:17:25.906 align:start position:0% you need to know about the first is a multi-layer<12:17:23.936> switch<12:17:24.116> which<12:17:24.960> operates<12:17:25.560> on 12:17:25.906 --> 12:17:25.916 align:start position:0% multi-layer switch which operates on 12:17:25.916 --> 12:17:29.926 align:start position:0% multi-layer switch which operates on layer<12:17:26.276> 2<12:17:26.596> and<12:17:27.596> 3.<12:17:28.560> our<12:17:28.916> usual<12:17:29.276> switch<12:17:29.520> because 12:17:29.926 --> 12:17:29.936 align:start position:0% layer 2 and 3. our usual switch because 12:17:29.936 --> 12:17:32.450 align:start position:0% layer 2 and 3. our usual switch because it's<12:17:30.300> only<12:17:30.480> dealing<12:17:30.840> with<12:17:31.020> Mac<12:17:31.200> addresses<12:17:31.800> is 12:17:32.450 --> 12:17:32.460 align:start position:0% it's only dealing with Mac addresses is 12:17:32.460 --> 12:17:35.690 align:start position:0% it's only dealing with Mac addresses is dealing<12:17:32.756> with<12:17:32.936> the<12:17:33.180> data<12:17:33.480> link<12:17:33.596> layer 12:17:35.690 --> 12:17:35.700 align:start position:0% dealing with the data link layer 12:17:35.700 --> 12:17:38.510 align:start position:0% dealing with the data link layer which<12:17:36.060> on<12:17:36.300> the<12:17:36.416> OSI<12:17:36.776> model 12:17:38.510 --> 12:17:38.520 align:start position:0% which on the OSI model 12:17:38.520 --> 12:17:40.310 align:start position:0% which on the OSI model is<12:17:39.000> Layer<12:17:39.416> Two 12:17:40.310 --> 12:17:40.320 align:start position:0% is Layer Two 12:17:40.320 --> 12:17:43.190 align:start position:0% is Layer Two a<12:17:40.980> multi-layer<12:17:41.520> switch<12:17:41.700> is<12:17:42.540> also<12:17:42.840> operating 12:17:43.190 --> 12:17:43.200 align:start position:0% a multi-layer switch is also operating 12:17:43.200 --> 12:17:47.150 align:start position:0% a multi-layer switch is also operating on<12:17:43.560> layer<12:17:44.040> 3.<12:17:44.460> it<12:17:45.180> also<12:17:45.660> routes 12:17:47.150 --> 12:17:47.160 align:start position:0% on layer 3. it also routes 12:17:47.160 --> 12:17:50.150 align:start position:0% on layer 3. it also routes so<12:17:47.820> it<12:17:48.240> is<12:17:48.900> not<12:17:49.080> just<12:17:49.256> a<12:17:49.380> switch<12:17:49.500> it's<12:17:49.740> also<12:17:50.040> a 12:17:50.150 --> 12:17:50.160 align:start position:0% so it is not just a switch it's also a 12:17:50.160 --> 12:17:52.310 align:start position:0% so it is not just a switch it's also a router<12:17:50.460> a<12:17:51.180> Content<12:17:51.480> switch<12:17:51.720> is<12:17:51.960> even<12:17:52.080> going 12:17:52.310 --> 12:17:52.320 align:start position:0% router a Content switch is even going 12:17:52.320 --> 12:17:56.510 align:start position:0% router a Content switch is even going further<12:17:52.680> up<12:17:52.860> the<12:17:52.980> OSI<12:17:53.400> model<12:17:53.640> and<12:17:54.480> analyzes 12:17:56.510 --> 12:17:56.520 align:start position:0% further up the OSI model and analyzes 12:17:56.520 --> 12:18:00.950 align:start position:0% further up the OSI model and analyzes the<12:17:57.180> content 12:18:00.950 --> 12:18:00.960 align:start position:0% 12:18:00.960 --> 12:18:02.746 align:start position:0% in<12:18:01.380> a<12:18:01.500> packet 12:18:02.746 --> 12:18:02.756 align:start position:0% in a packet 12:18:02.756 --> 12:18:04.370 align:start position:0% in a packet to<12:18:03.180> determine 12:18:04.370 --> 12:18:04.380 align:start position:0% to determine 12:18:04.380 --> 12:18:06.766 align:start position:0% to determine where<12:18:04.800> to<12:18:04.980> send<12:18:05.220> it 12:18:06.766 --> 12:18:06.776 align:start position:0% where to send it 12:18:06.776 --> 12:18:10.850 align:start position:0% where to send it this<12:18:07.140> is<12:18:07.380> also<12:18:07.616> why<12:18:07.800> it's<12:18:07.980> called<12:18:08.276> a<12:18:09.180> load 12:18:10.850 --> 12:18:10.860 align:start position:0% this is also why it's called a load 12:18:10.860 --> 12:18:13.906 align:start position:0% this is also why it's called a load bearing<12:18:11.820> switch<12:18:12.060> because<12:18:12.720> it<12:18:13.020> helps<12:18:13.380> reduce 12:18:13.906 --> 12:18:13.916 align:start position:0% bearing switch because it helps reduce 12:18:13.916 --> 12:18:18.406 align:start position:0% bearing switch because it helps reduce the<12:18:14.880> load<12:18:15.240> on<12:18:16.080> a<12:18:16.256> specific<12:18:16.500> node<12:18:17.040> by 12:18:18.406 --> 12:18:18.416 align:start position:0% the load on a specific node by 12:18:18.416 --> 12:18:20.450 align:start position:0% the load on a specific node by sending<12:18:19.020> the<12:18:19.140> data<12:18:19.436> out<12:18:19.616> to<12:18:20.096> several 12:18:20.450 --> 12:18:20.460 align:start position:0% sending the data out to several 12:18:20.460 --> 12:18:22.370 align:start position:0% sending the data out to several different<12:18:20.756> devices 12:18:22.370 --> 12:18:22.380 align:start position:0% different devices 12:18:22.380 --> 12:18:26.690 align:start position:0% different devices that<12:18:22.860> can<12:18:22.980> all<12:18:23.160> deal<12:18:23.400> with<12:18:23.820> the<12:18:24.060> same<12:18:24.240> content 12:18:26.690 --> 12:18:26.700 align:start position:0% that can all deal with the same content 12:18:26.700 --> 12:18:28.906 align:start position:0% that can all deal with the same content in<12:18:27.116> a<12:18:27.300> device 12:18:28.906 --> 12:18:28.916 align:start position:0% in a device 12:18:28.916 --> 12:18:31.190 align:start position:0% in a device now<12:18:29.520> we're<12:18:29.936> going<12:18:30.116> to<12:18:30.240> talk<12:18:30.480> further<12:18:30.960> about 12:18:31.190 --> 12:18:31.200 align:start position:0% now we're going to talk further about 12:18:31.200 --> 12:18:37.320 align:start position:0% now we're going to talk further about routing<12:18:31.916> in<12:18:32.340> the<12:18:32.400> next<12:18:32.520> lesson 12:18:37.320 --> 12:18:37.330 align:start position:0% 12:18:37.330 --> 12:18:53.266 align:start position:0% [Music] 12:18:53.266 --> 12:18:53.276 align:start position:0% 12:18:53.276 --> 12:18:56.870 align:start position:0% spanning<12:18:54.180> tree<12:18:54.300> protocol 12:18:56.870 --> 12:18:56.880 align:start position:0% 12:18:56.880 --> 12:19:00.050 align:start position:0% so<12:18:57.360> what<12:18:57.596> is<12:18:57.720> spanning<12:18:58.200> tree 12:19:00.050 --> 12:19:00.060 align:start position:0% so what is spanning tree 12:19:00.060 --> 12:19:02.650 align:start position:0% so what is spanning tree it's<12:19:00.540> defined<12:19:00.960> by<12:19:01.080> the<12:19:01.256> IEEE 12:19:02.650 --> 12:19:02.660 align:start position:0% it's defined by the IEEE 12:19:02.660 --> 12:19:05.266 align:start position:0% it's defined by the IEEE 802.1d<12:19:03.660> standard 12:19:05.266 --> 12:19:05.276 align:start position:0% 802.1d standard 12:19:05.276 --> 12:19:07.130 align:start position:0% 802.1d standard and<12:19:05.700> basically<12:19:05.936> it<12:19:06.116> allows<12:19:06.360> switches<12:19:06.776> to 12:19:07.130 --> 12:19:07.140 align:start position:0% and basically it allows switches to 12:19:07.140 --> 12:19:09.890 align:start position:0% and basically it allows switches to communicate<12:19:07.740> in<12:19:08.096> order<12:19:08.220> to<12:19:08.580> prevent<12:19:09.000> loops<12:19:09.596> on 12:19:09.890 --> 12:19:09.900 align:start position:0% communicate in order to prevent loops on 12:19:09.900 --> 12:19:12.106 align:start position:0% communicate in order to prevent loops on our<12:19:10.020> switch<12:19:10.256> Network 12:19:12.106 --> 12:19:12.116 align:start position:0% our switch Network 12:19:12.116 --> 12:19:15.670 align:start position:0% our switch Network it<12:19:12.540> runs<12:19:12.960> a<12:19:13.320> mathematical<12:19:14.116> algorithm 12:19:15.670 --> 12:19:15.680 align:start position:0% it runs a mathematical algorithm 12:19:15.680 --> 12:19:19.490 align:start position:0% it runs a mathematical algorithm it<12:19:16.680> finds<12:19:16.980> out<12:19:17.040> on<12:19:17.276> blocks<12:19:17.756> which<12:19:18.480> ports<12:19:19.200> would 12:19:19.490 --> 12:19:19.500 align:start position:0% it finds out on blocks which ports would 12:19:19.500 --> 12:19:24.586 align:start position:0% it finds out on blocks which ports would be<12:19:19.740> the<12:19:20.400> possible<12:19:20.700> causes<12:19:21.480> of<12:19:21.900> layer<12:19:22.320> 2<12:19:22.500> loops 12:19:24.586 --> 12:19:24.596 align:start position:0% be the possible causes of layer 2 loops 12:19:24.596 --> 12:19:26.926 align:start position:0% be the possible causes of layer 2 loops basically<12:19:25.380> a<12:19:25.500> loop<12:19:25.800> will<12:19:25.916> occur<12:19:26.340> on<12:19:26.756> our 12:19:26.926 --> 12:19:26.936 align:start position:0% basically a loop will occur on our 12:19:26.936 --> 12:19:28.970 align:start position:0% basically a loop will occur on our switch<12:19:27.180> Network<12:19:27.596> when<12:19:28.380> there's<12:19:28.560> more<12:19:28.800> than 12:19:28.970 --> 12:19:28.980 align:start position:0% switch Network when there's more than 12:19:28.980 --> 12:19:31.070 align:start position:0% switch Network when there's more than one<12:19:29.160> path<12:19:29.340> for<12:19:29.640> a<12:19:29.756> frame<12:19:30.000> to<12:19:30.180> take 12:19:31.070 --> 12:19:31.080 align:start position:0% one path for a frame to take 12:19:31.080 --> 12:19:34.150 align:start position:0% one path for a frame to take and<12:19:31.680> this<12:19:32.096> could<12:19:32.276> cause<12:19:32.580> obviously<12:19:33.240> confusion 12:19:34.150 --> 12:19:34.160 align:start position:0% and this could cause obviously confusion 12:19:34.160 --> 12:19:37.310 align:start position:0% and this could cause obviously confusion as<12:19:35.160> I'll<12:19:35.400> illustrate<12:19:35.820> in<12:19:36.000> a<12:19:36.180> moment<12:19:36.416> so<12:19:37.020> it's<12:19:37.200> a 12:19:37.310 --> 12:19:37.320 align:start position:0% as I'll illustrate in a moment so it's a 12:19:37.320 --> 12:19:38.630 align:start position:0% as I'll illustrate in a moment so it's a real<12:19:37.436> simple 12:19:38.630 --> 12:19:38.640 align:start position:0% real simple 12:19:38.640 --> 12:19:41.570 align:start position:0% real simple illustration<12:19:39.540> here<12:19:39.900> with<12:19:40.256> our<12:19:40.436> diagram 12:19:41.570 --> 12:19:41.580 align:start position:0% illustration here with our diagram 12:19:41.580 --> 12:19:44.030 align:start position:0% illustration here with our diagram so<12:19:42.000> switch<12:19:42.180> one<12:19:42.540> for<12:19:42.840> example<12:19:43.140> will<12:19:43.380> receive<12:19:43.800> a 12:19:44.030 --> 12:19:44.040 align:start position:0% so switch one for example will receive a 12:19:44.040 --> 12:19:45.950 align:start position:0% so switch one for example will receive a frame<12:19:44.276> on<12:19:44.400> its<12:19:44.700> fast<12:19:44.820> ethernet<12:19:45.116> zero<12:19:45.720> slash 12:19:45.950 --> 12:19:45.960 align:start position:0% frame on its fast ethernet zero slash 12:19:45.960 --> 12:19:47.030 align:start position:0% frame on its fast ethernet zero slash one 12:19:47.030 --> 12:19:47.040 align:start position:0% one 12:19:47.040 --> 12:19:49.606 align:start position:0% one and<12:19:47.340> it<12:19:47.520> will<12:19:47.640> flood<12:19:47.880> it<12:19:48.060> out<12:19:48.360> of<12:19:48.540> its<12:19:49.500> next 12:19:49.606 --> 12:19:49.616 align:start position:0% and it will flood it out of its next 12:19:49.616 --> 12:19:51.766 align:start position:0% and it will flood it out of its next interface<12:19:50.096> fast<12:19:50.400> ethernet<12:19:50.700> zero<12:19:51.300> slash<12:19:51.540> two 12:19:51.766 --> 12:19:51.776 align:start position:0% interface fast ethernet zero slash two 12:19:51.776 --> 12:19:54.170 align:start position:0% interface fast ethernet zero slash two and<12:19:52.256> remember<12:19:52.436> if<12:19:52.800> there's<12:19:52.980> 24<12:19:53.220> interfaces 12:19:54.170 --> 12:19:54.180 align:start position:0% and remember if there's 24 interfaces 12:19:54.180 --> 12:19:56.030 align:start position:0% and remember if there's 24 interfaces then<12:19:54.776> it<12:19:54.960> would<12:19:55.080> be<12:19:55.200> flooded<12:19:55.560> in<12:19:55.616> them<12:19:55.800> out<12:19:55.916> of 12:19:56.030 --> 12:19:56.040 align:start position:0% then it would be flooded in them out of 12:19:56.040 --> 12:19:58.130 align:start position:0% then it would be flooded in them out of all<12:19:56.220> 24. 12:19:58.130 --> 12:19:58.140 align:start position:0% all 24. 12:19:58.140 --> 12:20:01.070 align:start position:0% all 24. now<12:19:58.616> switch<12:19:58.860> 2<12:19:59.160> would<12:19:59.400> receive<12:19:59.820> this 12:20:01.070 --> 12:20:01.080 align:start position:0% now switch 2 would receive this 12:20:01.080 --> 12:20:03.170 align:start position:0% now switch 2 would receive this um<12:20:01.200> and<12:20:01.436> the<12:20:01.980> address 12:20:03.170 --> 12:20:03.180 align:start position:0% um and the address 12:20:03.180 --> 12:20:05.266 align:start position:0% um and the address would<12:20:03.660> be<12:20:03.720> for<12:20:03.900> host<12:20:04.140> a<12:20:04.436> and<12:20:04.680> it<12:20:04.916> would<12:20:05.040> be 12:20:05.266 --> 12:20:05.276 align:start position:0% would be for host a and it would be 12:20:05.276 --> 12:20:08.870 align:start position:0% would be for host a and it would be firstly<12:20:05.936> received<12:20:06.360> by<12:20:06.480> switch<12:20:06.720> a<12:20:07.020> switch<12:20:07.560> one 12:20:08.870 --> 12:20:08.880 align:start position:0% firstly received by switch a switch one 12:20:08.880 --> 12:20:10.906 align:start position:0% firstly received by switch a switch one and<12:20:09.300> recognize<12:20:09.776> that<12:20:09.960> host<12:20:10.140> a<12:20:10.436> was<12:20:10.616> connected 12:20:10.906 --> 12:20:10.916 align:start position:0% and recognize that host a was connected 12:20:10.916 --> 12:20:14.210 align:start position:0% and recognize that host a was connected to<12:20:10.980> fast<12:20:11.220> ethernet<12:20:11.580> 0.1<12:20:12.680> unfortunately<12:20:13.680> that 12:20:14.210 --> 12:20:14.220 align:start position:0% to fast ethernet 0.1 unfortunately that 12:20:14.220 --> 12:20:16.070 align:start position:0% to fast ethernet 0.1 unfortunately that address<12:20:14.400> would<12:20:14.756> come<12:20:14.936> out<12:20:15.116> of<12:20:15.300> the<12:20:15.540> bottom<12:20:15.840> of 12:20:16.070 --> 12:20:16.080 align:start position:0% address would come out of the bottom of 12:20:16.080 --> 12:20:18.586 align:start position:0% address would come out of the bottom of switch<12:20:16.256> one<12:20:16.616> go<12:20:17.520> around<12:20:17.820> and<12:20:18.180> reach<12:20:18.416> the 12:20:18.586 --> 12:20:18.596 align:start position:0% switch one go around and reach the 12:20:18.596 --> 12:20:21.290 align:start position:0% switch one go around and reach the bottom<12:20:18.840> of<12:20:18.960> switch<12:20:19.200> two<12:20:19.500> switch<12:20:20.400> two<12:20:20.880> then 12:20:21.290 --> 12:20:21.300 align:start position:0% bottom of switch two switch two then 12:20:21.300 --> 12:20:22.790 align:start position:0% bottom of switch two switch two then thinks<12:20:21.900> that 12:20:22.790 --> 12:20:22.800 align:start position:0% thinks that 12:20:22.800 --> 12:20:26.810 align:start position:0% thinks that it<12:20:23.700> knows<12:20:24.060> the<12:20:24.180> way<12:20:24.300> to<12:20:24.480> get<12:20:24.660> to<12:20:25.020> host<12:20:25.320> a<12:20:26.096> and 12:20:26.810 --> 12:20:26.820 align:start position:0% it knows the way to get to host a and 12:20:26.820 --> 12:20:28.670 align:start position:0% it knows the way to get to host a and the<12:20:27.240> direction<12:20:27.480> to<12:20:27.840> go<12:20:28.020> is<12:20:28.256> through<12:20:28.500> fast 12:20:28.670 --> 12:20:28.680 align:start position:0% the direction to go is through fast 12:20:28.680 --> 12:20:30.890 align:start position:0% the direction to go is through fast ethernet<12:20:29.096> zero<12:20:29.640> slash<12:20:29.880> one<12:20:30.116> it<12:20:30.660> will<12:20:30.720> send 12:20:30.890 --> 12:20:30.900 align:start position:0% ethernet zero slash one it will send 12:20:30.900 --> 12:20:33.406 align:start position:0% ethernet zero slash one it will send that<12:20:31.140> out<12:20:31.320> of<12:20:31.436> fast<12:20:31.616> ethernet<12:20:32.040> uh<12:20:32.756> sorry<12:20:32.936> first 12:20:33.406 --> 12:20:33.416 align:start position:0% that out of fast ethernet uh sorry first 12:20:33.416 --> 12:20:35.870 align:start position:0% that out of fast ethernet uh sorry first ethernet<12:20:33.660> 0-2<12:20:34.560> and<12:20:35.040> it<12:20:35.160> will<12:20:35.276> send<12:20:35.400> that<12:20:35.520> to 12:20:35.870 --> 12:20:35.880 align:start position:0% ethernet 0-2 and it will send that to 12:20:35.880 --> 12:20:38.990 align:start position:0% ethernet 0-2 and it will send that to zero<12:20:36.116> slash<12:20:36.360> one<12:20:36.660> now<12:20:37.320> we<12:20:37.500> have<12:20:37.680> a<12:20:37.800> problem<12:20:38.000> in 12:20:38.990 --> 12:20:39.000 align:start position:0% zero slash one now we have a problem in 12:20:39.000 --> 12:20:41.630 align:start position:0% zero slash one now we have a problem in that<12:20:39.300> the<12:20:39.720> ports<12:20:40.256> on<12:20:40.380> the<12:20:40.500> switch<12:20:40.680> all<12:20:41.340> think 12:20:41.630 --> 12:20:41.640 align:start position:0% that the ports on the switch all think 12:20:41.640 --> 12:20:44.510 align:start position:0% that the ports on the switch all think that<12:20:41.820> they<12:20:42.000> can<12:20:42.116> release<12:20:42.300> reach<12:20:43.020> host<12:20:43.256> a<12:20:43.520> and 12:20:44.510 --> 12:20:44.520 align:start position:0% that they can release reach host a and 12:20:44.520 --> 12:20:47.926 align:start position:0% that they can release reach host a and that<12:20:44.880> isn't<12:20:45.180> in<12:20:45.300> fact<12:20:45.416> the<12:20:45.660> case 12:20:47.926 --> 12:20:47.936 align:start position:0% 12:20:47.936 --> 12:20:50.150 align:start position:0% now<12:20:48.416> there's<12:20:48.596> no<12:20:48.840> time<12:20:49.020> to<12:20:49.200> live<12:20:49.320> field<12:20:49.616> in 12:20:50.150 --> 12:20:50.160 align:start position:0% now there's no time to live field in 12:20:50.160 --> 12:20:51.766 align:start position:0% now there's no time to live field in layer<12:20:50.460> 2<12:20:50.580> frames<12:20:51.000> so<12:20:51.180> that<12:20:51.360> would<12:20:51.480> go<12:20:51.660> around 12:20:51.766 --> 12:20:51.776 align:start position:0% layer 2 frames so that would go around 12:20:51.776 --> 12:20:53.870 align:start position:0% layer 2 frames so that would go around around<12:20:52.140> the<12:20:52.616> network<12:20:52.800> until<12:20:53.220> every<12:20:53.520> single 12:20:53.870 --> 12:20:53.880 align:start position:0% around the network until every single 12:20:53.880 --> 12:20:55.310 align:start position:0% around the network until every single switch<12:20:54.000> thinks<12:20:54.480> it<12:20:54.596> knows<12:20:54.840> how<12:20:54.900> to<12:20:55.020> get<12:20:55.200> to 12:20:55.310 --> 12:20:55.320 align:start position:0% switch thinks it knows how to get to 12:20:55.320 --> 12:20:56.450 align:start position:0% switch thinks it knows how to get to host<12:20:55.560> a 12:20:56.450 --> 12:20:56.460 align:start position:0% host a 12:20:56.460 --> 12:20:58.550 align:start position:0% host a and<12:20:56.880> it<12:20:57.180> would<12:20:57.300> bring<12:20:57.480> your<12:20:57.776> network<12:20:58.020> to<12:20:58.380> a 12:20:58.550 --> 12:20:58.560 align:start position:0% and it would bring your network to a 12:20:58.560 --> 12:20:59.926 align:start position:0% and it would bring your network to a grinding<12:20:58.916> halt 12:20:59.926 --> 12:20:59.936 align:start position:0% grinding halt 12:20:59.936 --> 12:21:02.926 align:start position:0% grinding halt so<12:21:00.416> there's<12:21:00.596> a<12:21:00.720> mathematical<12:21:01.640> algorithm<12:21:02.640> was 12:21:02.926 --> 12:21:02.936 align:start position:0% so there's a mathematical algorithm was 12:21:02.936 --> 12:21:05.810 align:start position:0% so there's a mathematical algorithm was created 12:21:05.810 --> 12:21:05.820 align:start position:0% 12:21:05.820 --> 12:21:08.210 align:start position:0% and<12:21:06.180> it's<12:21:06.300> based<12:21:06.596> on<12:21:06.660> two<12:21:06.960> key<12:21:07.380> components<12:21:07.980> the 12:21:08.210 --> 12:21:08.220 align:start position:0% and it's based on two key components the 12:21:08.220 --> 12:21:09.710 align:start position:0% and it's based on two key components the bridge<12:21:08.400> ID 12:21:09.710 --> 12:21:09.720 align:start position:0% bridge ID 12:21:09.720 --> 12:21:11.510 align:start position:0% bridge ID for<12:21:10.080> bridge<12:21:10.256> ID<12:21:10.500> you<12:21:10.860> can<12:21:10.980> basically<12:21:11.276> read 12:21:11.510 --> 12:21:11.520 align:start position:0% for bridge ID you can basically read 12:21:11.520 --> 12:21:14.266 align:start position:0% for bridge ID you can basically read switch<12:21:11.936> ID<12:21:12.240> it's<12:21:12.596> the<12:21:12.776> same<12:21:12.960> thing<12:21:13.380> and<12:21:14.040> the 12:21:14.266 --> 12:21:14.276 align:start position:0% switch ID it's the same thing and the 12:21:14.276 --> 12:21:16.310 align:start position:0% switch ID it's the same thing and the path<12:21:14.520> cost 12:21:16.310 --> 12:21:16.320 align:start position:0% path cost 12:21:16.320 --> 12:21:20.390 align:start position:0% path cost so<12:21:16.860> these<12:21:17.276> are<12:21:17.700> contained<12:21:18.240> inside<12:21:18.540> the<12:21:19.080> frame 12:21:20.390 --> 12:21:20.400 align:start position:0% so these are contained inside the frame 12:21:20.400 --> 12:21:22.130 align:start position:0% so these are contained inside the frame Bridge<12:21:20.880> ideas<12:21:21.180> and<12:21:21.540> eight<12:21:21.660> byte<12:21:22.020> field 12:21:22.130 --> 12:21:22.140 align:start position:0% Bridge ideas and eight byte field 12:21:22.140 --> 12:21:24.710 align:start position:0% Bridge ideas and eight byte field consisting<12:21:22.740> of<12:21:22.916> the<12:21:23.096> bridge<12:21:23.220> priority<12:21:23.756> and 12:21:24.710 --> 12:21:24.720 align:start position:0% consisting of the bridge priority and 12:21:24.720 --> 12:21:27.650 align:start position:0% consisting of the bridge priority and the<12:21:25.020> MAC<12:21:25.256> address<12:21:25.756> the<12:21:26.756> base<12:21:26.880> Mac<12:21:27.116> address<12:21:27.300> of 12:21:27.650 --> 12:21:27.660 align:start position:0% the MAC address the base Mac address of 12:21:27.660 --> 12:21:30.106 align:start position:0% the MAC address the base Mac address of the<12:21:27.840> switch 12:21:30.106 --> 12:21:30.116 align:start position:0% 12:21:30.116 --> 12:21:34.606 align:start position:0% the<12:21:30.540> default<12:21:30.776> Bridge<12:21:30.960> priority<12:21:31.560> is<12:21:32.040> 32768 12:21:34.606 --> 12:21:34.616 align:start position:0% the default Bridge priority is 32768 12:21:34.616 --> 12:21:35.990 align:start position:0% the default Bridge priority is 32768 and<12:21:34.916> then<12:21:35.040> this<12:21:35.220> is<12:21:35.340> added<12:21:35.640> to<12:21:35.756> the<12:21:35.880> MAC 12:21:35.990 --> 12:21:36.000 align:start position:0% and then this is added to the MAC 12:21:36.000 --> 12:21:38.746 align:start position:0% and then this is added to the MAC address<12:21:36.256> now<12:21:37.256> I've<12:21:37.436> issued<12:21:37.860> a<12:21:38.040> show<12:21:38.276> version 12:21:38.746 --> 12:21:38.756 align:start position:0% address now I've issued a show version 12:21:38.756 --> 12:21:42.106 align:start position:0% address now I've issued a show version on<12:21:39.240> a<12:21:39.416> switch<12:21:39.740> and<12:21:40.740> it<12:21:41.040> showed<12:21:41.460> the<12:21:41.640> base<12:21:41.880> Mac 12:21:42.106 --> 12:21:42.116 align:start position:0% on a switch and it showed the base Mac 12:21:42.116 --> 12:21:46.010 align:start position:0% on a switch and it showed the base Mac address<12:21:42.360> among<12:21:43.320> other<12:21:43.560> information<12:21:44.776> and<12:21:45.776> each 12:21:46.010 --> 12:21:46.020 align:start position:0% address among other information and each 12:21:46.020 --> 12:21:49.730 align:start position:0% address among other information and each one<12:21:46.140> will<12:21:46.380> be<12:21:46.500> different 12:21:49.730 --> 12:21:49.740 align:start position:0% 12:21:49.740 --> 12:21:51.830 align:start position:0% so<12:21:50.220> the<12:21:50.340> path<12:21:50.520> cost<12:21:50.820> is<12:21:51.060> used<12:21:51.240> to<12:21:51.416> calculate 12:21:51.830 --> 12:21:51.840 align:start position:0% so the path cost is used to calculate 12:21:51.840 --> 12:21:54.890 align:start position:0% so the path cost is used to calculate the<12:21:52.020> proximity<12:21:52.500> to<12:21:52.860> neighbor<12:21:53.096> switches<12:21:53.900> the 12:21:54.890 --> 12:21:54.900 align:start position:0% the proximity to neighbor switches the 12:21:54.900 --> 12:21:56.570 align:start position:0% the proximity to neighbor switches the higher<12:21:55.200> the<12:21:55.320> bandwidth<12:21:55.860> the<12:21:56.040> lower<12:21:56.276> the 12:21:56.570 --> 12:21:56.580 align:start position:0% higher the bandwidth the lower the 12:21:56.580 --> 12:21:59.086 align:start position:0% higher the bandwidth the lower the default<12:21:56.936> cost<12:21:57.596> so<12:21:58.380> we<12:21:58.560> can<12:21:58.680> see<12:21:58.740> the<12:21:58.916> 10 12:21:59.086 --> 12:21:59.096 align:start position:0% default cost so we can see the 10 12:21:59.096 --> 12:22:00.650 align:start position:0% default cost so we can see the 10 gigabit<12:21:59.580> connection<12:21:59.820> here<12:22:00.180> has<12:22:00.360> got<12:22:00.480> the 12:22:00.650 --> 12:22:00.660 align:start position:0% gigabit connection here has got the 12:22:00.660 --> 12:22:04.550 align:start position:0% gigabit connection here has got the lowest<12:22:00.960> forecast<12:22:01.860> allocated<12:22:02.640> to<12:22:02.936> it 12:22:04.550 --> 12:22:04.560 align:start position:0% lowest forecast allocated to it 12:22:04.560 --> 12:22:07.490 align:start position:0% lowest forecast allocated to it so<12:22:05.160> there's<12:22:05.400> a<12:22:05.756> four-step<12:22:06.596> path<12:22:07.020> selection 12:22:07.490 --> 12:22:07.500 align:start position:0% so there's a four-step path selection 12:22:07.500 --> 12:22:09.650 align:start position:0% so there's a four-step path selection process 12:22:09.650 --> 12:22:09.660 align:start position:0% process 12:22:09.660 --> 12:22:12.650 align:start position:0% process so<12:22:10.140> the<12:22:10.320> lowest<12:22:10.616> route<12:22:10.860> to<12:22:11.096> bridge<12:22:11.276> ID<12:22:11.660> the 12:22:12.650 --> 12:22:12.660 align:start position:0% so the lowest route to bridge ID the 12:22:12.660 --> 12:22:16.190 align:start position:0% so the lowest route to bridge ID the lowest<12:22:13.080> path<12:22:13.256> cost<12:22:13.616> to<12:22:14.160> the<12:22:14.400> root<12:22:14.640> Bridge 12:22:16.190 --> 12:22:16.200 align:start position:0% lowest path cost to the root Bridge 12:22:16.200 --> 12:22:18.710 align:start position:0% lowest path cost to the root Bridge the<12:22:16.800> lowest<12:22:17.096> sender<12:22:17.460> Bridge<12:22:17.700> ID 12:22:18.710 --> 12:22:18.720 align:start position:0% the lowest sender Bridge ID 12:22:18.720 --> 12:22:20.630 align:start position:0% the lowest sender Bridge ID and<12:22:19.020> the<12:22:19.140> lowest<12:22:19.436> Port<12:22:19.616> ID<12:22:19.916> and<12:22:20.276> it<12:22:20.400> will<12:22:20.460> go 12:22:20.630 --> 12:22:20.640 align:start position:0% and the lowest Port ID and it will go 12:22:20.640 --> 12:22:22.370 align:start position:0% and the lowest Port ID and it will go through<12:22:20.756> this<12:22:20.936> four<12:22:21.180> steps<12:22:21.540> until<12:22:21.720> it<12:22:22.020> makes<12:22:22.140> a 12:22:22.370 --> 12:22:22.380 align:start position:0% through this four steps until it makes a 12:22:22.380 --> 12:22:23.450 align:start position:0% through this four steps until it makes a decision 12:22:23.450 --> 12:22:23.460 align:start position:0% decision 12:22:23.460 --> 12:22:25.490 align:start position:0% decision this<12:22:23.880> all<12:22:24.116> happens<12:22:24.300> after<12:22:24.596> the<12:22:24.900> exchange<12:22:25.256> of 12:22:25.490 --> 12:22:25.500 align:start position:0% this all happens after the exchange of 12:22:25.500 --> 12:22:27.650 align:start position:0% this all happens after the exchange of bridge<12:22:25.740> protocol<12:22:26.220> data<12:22:26.820> units<12:22:27.240> which<12:22:27.540> are 12:22:27.650 --> 12:22:27.660 align:start position:0% bridge protocol data units which are 12:22:27.660 --> 12:22:30.890 align:start position:0% bridge protocol data units which are called<12:22:27.776> bpdus 12:22:30.890 --> 12:22:30.900 align:start position:0% 12:22:30.900 --> 12:22:33.350 align:start position:0% so<12:22:31.320> let's<12:22:31.436> have<12:22:31.616> a<12:22:31.740> look<12:22:31.800> at<12:22:31.980> our<12:22:32.220> diagram<12:22:32.700> we 12:22:33.350 --> 12:22:33.360 align:start position:0% so let's have a look at our diagram we 12:22:33.360 --> 12:22:35.630 align:start position:0% so let's have a look at our diagram we have<12:22:33.660> three<12:22:34.080> switches<12:22:34.616> here<12:22:34.860> and<12:22:35.276> just<12:22:35.460> to 12:22:35.630 --> 12:22:35.640 align:start position:0% have three switches here and just to 12:22:35.640 --> 12:22:37.130 align:start position:0% have three switches here and just to keep<12:22:35.756> things<12:22:35.936> simple<12:22:36.180> we've<12:22:36.660> given<12:22:36.840> them<12:22:37.020> the 12:22:37.130 --> 12:22:37.140 align:start position:0% keep things simple we've given them the 12:22:37.140 --> 12:22:39.290 align:start position:0% keep things simple we've given them the Mac<12:22:37.256> addresses<12:22:37.680> of<12:22:37.980> all<12:22:38.096> A's<12:22:38.520> or<12:22:38.640> B's<12:22:39.060> and<12:22:39.180> all 12:22:39.290 --> 12:22:39.300 align:start position:0% Mac addresses of all A's or B's and all 12:22:39.300 --> 12:22:40.730 align:start position:0% Mac addresses of all A's or B's and all C's 12:22:40.730 --> 12:22:40.740 align:start position:0% C's 12:22:40.740 --> 12:22:42.290 align:start position:0% C's they're<12:22:41.276> all<12:22:41.460> connected<12:22:41.820> so<12:22:42.060> we<12:22:42.180> could 12:22:42.290 --> 12:22:42.300 align:start position:0% they're all connected so we could 12:22:42.300 --> 12:22:44.690 align:start position:0% they're all connected so we could possibly<12:22:42.660> have<12:22:43.500> a<12:22:43.740> loop<12:22:43.980> here<12:22:44.160> unless 12:22:44.690 --> 12:22:44.700 align:start position:0% possibly have a loop here unless 12:22:44.700 --> 12:22:47.330 align:start position:0% possibly have a loop here unless something<12:22:45.060> is<12:22:45.416> done<12:22:45.660> to<12:22:45.840> close<12:22:46.200> down<12:22:46.500> one<12:22:47.160> or 12:22:47.330 --> 12:22:47.340 align:start position:0% something is done to close down one or 12:22:47.340 --> 12:22:48.890 align:start position:0% something is done to close down one or more<12:22:47.520> of<12:22:47.700> the<12:22:47.820> ports 12:22:48.890 --> 12:22:48.900 align:start position:0% more of the ports 12:22:48.900 --> 12:22:50.266 align:start position:0% more of the ports so<12:22:49.320> there's<12:22:49.436> a<12:22:49.616> root<12:22:49.800> Bridge<12:22:49.980> election 12:22:50.266 --> 12:22:50.276 align:start position:0% so there's a root Bridge election 12:22:50.276 --> 12:22:51.710 align:start position:0% so there's a root Bridge election firstly 12:22:51.710 --> 12:22:51.720 align:start position:0% firstly 12:22:51.720 --> 12:22:54.710 align:start position:0% firstly then<12:22:52.200> there's<12:22:52.380> root<12:22:52.800> Port<12:22:52.980> selection 12:22:54.710 --> 12:22:54.720 align:start position:0% then there's root Port selection 12:22:54.720 --> 12:22:58.246 align:start position:0% then there's root Port selection then<12:22:55.140> there's<12:22:55.320> a<12:22:55.560> designated<12:22:55.980> Port<12:22:56.400> election 12:22:58.246 --> 12:22:58.256 align:start position:0% then there's a designated Port election 12:22:58.256 --> 12:23:01.070 align:start position:0% then there's a designated Port election the<12:22:58.680> bridge<12:22:58.860> with<12:22:59.460> the<12:22:59.700> lowest<12:23:00.000> Bridge<12:23:00.416> ID<12:23:00.720> is 12:23:01.070 --> 12:23:01.080 align:start position:0% the bridge with the lowest Bridge ID is 12:23:01.080 --> 12:23:03.170 align:start position:0% the bridge with the lowest Bridge ID is selected<12:23:01.500> as<12:23:01.616> a<12:23:01.800> route<12:23:02.040> and<12:23:02.580> remember<12:23:02.756> it's<12:23:03.060> a 12:23:03.170 --> 12:23:03.180 align:start position:0% selected as a route and remember it's a 12:23:03.180 --> 12:23:05.030 align:start position:0% selected as a route and remember it's a combination<12:23:03.540> between<12:23:03.840> the<12:23:04.200> priority<12:23:04.560> and<12:23:04.916> the 12:23:05.030 --> 12:23:05.040 align:start position:0% combination between the priority and the 12:23:05.040 --> 12:23:07.426 align:start position:0% combination between the priority and the MAC<12:23:05.220> address<12:23:05.400> in<12:23:06.360> this<12:23:06.480> case<12:23:06.596> the<12:23:07.020> lowest<12:23:07.256> Mac 12:23:07.426 --> 12:23:07.436 align:start position:0% MAC address in this case the lowest Mac 12:23:07.436 --> 12:23:09.290 align:start position:0% MAC address in this case the lowest Mac address<12:23:07.680> is<12:23:08.040> going<12:23:08.220> to<12:23:08.276> be<12:23:08.400> the<12:23:08.640> one<12:23:08.756> with<12:23:09.060> all 12:23:09.290 --> 12:23:09.300 align:start position:0% address is going to be the one with all 12:23:09.300 --> 12:23:11.990 align:start position:0% address is going to be the one with all of<12:23:09.480> the<12:23:09.776> A's<12:23:10.380> because<12:23:11.096> that's<12:23:11.400> a<12:23:11.580> lower<12:23:11.756> number 12:23:11.990 --> 12:23:12.000 align:start position:0% of the A's because that's a lower number 12:23:12.000 --> 12:23:14.746 align:start position:0% of the A's because that's a lower number in<12:23:12.240> hexadecimal 12:23:14.746 --> 12:23:14.756 align:start position:0% in hexadecimal 12:23:14.756 --> 12:23:18.170 align:start position:0% in hexadecimal so<12:23:15.660> root<12:23:16.140> Port<12:23:16.320> is<12:23:16.800> the<12:23:17.096> port<12:23:17.276> closest<12:23:17.756> to<12:23:18.060> the 12:23:18.170 --> 12:23:18.180 align:start position:0% so root Port is the port closest to the 12:23:18.180 --> 12:23:20.266 align:start position:0% so root Port is the port closest to the root<12:23:18.480> bridge<12:23:18.660> now<12:23:19.380> the<12:23:19.560> route<12:23:19.680> bridge<12:23:19.980> will 12:23:20.266 --> 12:23:20.276 align:start position:0% root bridge now the route bridge will 12:23:20.276 --> 12:23:22.190 align:start position:0% root bridge now the route bridge will not<12:23:20.400> have<12:23:20.580> any<12:23:20.700> root<12:23:21.180> ports<12:23:21.480> because<12:23:21.720> it<12:23:22.080> is 12:23:22.190 --> 12:23:22.200 align:start position:0% not have any root ports because it is 12:23:22.200 --> 12:23:24.406 align:start position:0% not have any root ports because it is the<12:23:22.320> route<12:23:22.500> Bridge<12:23:22.800> so<12:23:23.160> its<12:23:23.756> ports<12:23:24.116> will<12:23:24.240> all 12:23:24.406 --> 12:23:24.416 align:start position:0% the route Bridge so its ports will all 12:23:24.416 --> 12:23:27.230 align:start position:0% the route Bridge so its ports will all be<12:23:24.596> known<12:23:24.960> as<12:23:25.140> designated<12:23:25.616> ports<12:23:26.580> you<12:23:27.060> can<12:23:27.116> see 12:23:27.230 --> 12:23:27.240 align:start position:0% be known as designated ports you can see 12:23:27.240 --> 12:23:29.266 align:start position:0% be known as designated ports you can see switch<12:23:27.480> two<12:23:27.776> and<12:23:27.960> three<12:23:28.080> has<12:23:28.380> elected<12:23:28.980> its 12:23:29.266 --> 12:23:29.276 align:start position:0% switch two and three has elected its 12:23:29.276 --> 12:23:34.130 align:start position:0% switch two and three has elected its closest<12:23:29.776> port<12:23:30.980> to<12:23:31.980> the<12:23:32.400> uh<12:23:32.700> route<12:23:33.000> Bridge<12:23:33.416> as 12:23:34.130 --> 12:23:34.140 align:start position:0% closest port to the uh route Bridge as 12:23:34.140 --> 12:23:38.150 align:start position:0% closest port to the uh route Bridge as fast<12:23:34.380> ethernet<12:23:34.860> zero<12:23:35.220> slash<12:23:35.460> one 12:23:38.150 --> 12:23:38.160 align:start position:0% 12:23:38.160 --> 12:23:39.710 align:start position:0% every<12:23:38.640> bridge<12:23:38.880> you<12:23:39.060> set<12:23:39.180> the<12:23:39.360> root<12:23:39.540> Bridge 12:23:39.710 --> 12:23:39.720 align:start position:0% every bridge you set the root Bridge 12:23:39.720 --> 12:23:42.230 align:start position:0% every bridge you set the root Bridge must<12:23:40.020> elect<12:23:40.256> the<12:23:40.500> root<12:23:40.740> ports<12:23:41.160> and<12:23:41.700> each 12:23:42.230 --> 12:23:42.240 align:start position:0% must elect the root ports and each 12:23:42.240 --> 12:23:44.210 align:start position:0% must elect the root ports and each interface<12:23:42.840> adds<12:23:43.380> a<12:23:43.436> cost 12:23:44.210 --> 12:23:44.220 align:start position:0% interface adds a cost 12:23:44.220 --> 12:23:46.310 align:start position:0% interface adds a cost so<12:23:44.700> as<12:23:44.880> it<12:23:45.060> goes<12:23:45.300> as<12:23:45.416> the<12:23:45.660> frame<12:23:45.900> goes<12:23:46.200> through 12:23:46.310 --> 12:23:46.320 align:start position:0% so as it goes as the frame goes through 12:23:46.320 --> 12:23:50.266 align:start position:0% so as it goes as the frame goes through different<12:23:46.500> interfaces<12:23:47.220> the<12:23:47.580> cost<12:23:47.700> is<12:23:47.936> added 12:23:50.266 --> 12:23:50.276 align:start position:0% different interfaces the cost is added 12:23:50.276 --> 12:23:54.530 align:start position:0% different interfaces the cost is added you<12:23:50.756> can<12:23:50.880> see<12:23:51.000> fast<12:23:51.300> ethernet<12:23:51.660> 0<12:23:52.020> 1<12:23:52.560> is<12:23:52.980> 19.<12:23:53.756> as 12:23:54.530 --> 12:23:54.540 align:start position:0% you can see fast ethernet 0 1 is 19. as 12:23:54.540 --> 12:23:58.426 align:start position:0% you can see fast ethernet 0 1 is 19. as it<12:23:54.720> gets<12:23:55.020> to<12:23:55.080> fast<12:23:55.560> ethernet<12:23:55.980> 0<12:23:56.340> 2.<12:23:57.540> that<12:23:58.256> Port 12:23:58.426 --> 12:23:58.436 align:start position:0% it gets to fast ethernet 0 2. that Port 12:23:58.436 --> 12:24:02.210 align:start position:0% it gets to fast ethernet 0 2. that Port cost<12:23:58.680> is<12:23:58.916> added<12:23:59.276> again<12:23:59.460> and<12:23:59.880> 19<12:24:00.180> plus<12:24:00.660> 19<12:24:01.220> costs 12:24:02.210 --> 12:24:02.220 align:start position:0% cost is added again and 19 plus 19 costs 12:24:02.220 --> 12:24:05.690 align:start position:0% cost is added again and 19 plus 19 costs have<12:24:02.276> been<12:24:02.460> 19<12:24:02.700> each<12:24:03.240> uh<12:24:04.140> comes<12:24:04.436> up<12:24:04.500> as<12:24:04.680> 38.<12:24:05.400> so 12:24:05.690 --> 12:24:05.700 align:start position:0% have been 19 each uh comes up as 38. so 12:24:05.700 --> 12:24:09.406 align:start position:0% have been 19 each uh comes up as 38. so fast<12:24:05.936> ethernet<12:24:06.300> 0<12:24:06.660> 1<12:24:07.200> wins 12:24:09.406 --> 12:24:09.416 align:start position:0% fast ethernet 0 1 wins 12:24:09.416 --> 12:24:11.630 align:start position:0% fast ethernet 0 1 wins the<12:24:09.900> designated<12:24:10.256> Port<12:24:10.560> election<12:24:10.916> and 12:24:11.630 --> 12:24:11.640 align:start position:0% the designated Port election and 12:24:11.640 --> 12:24:13.010 align:start position:0% the designated Port election and designated<12:24:12.060> report<12:24:12.300> sends<12:24:12.720> it<12:24:12.840> receives 12:24:13.010 --> 12:24:13.020 align:start position:0% designated report sends it receives 12:24:13.020 --> 12:24:15.170 align:start position:0% designated report sends it receives traffic<12:24:13.256> on<12:24:13.560> the<12:24:13.680> segment<12:24:14.040> to<12:24:14.756> the<12:24:14.936> root 12:24:15.170 --> 12:24:15.180 align:start position:0% traffic on the segment to the root 12:24:15.180 --> 12:24:16.010 align:start position:0% traffic on the segment to the root Bridge 12:24:16.010 --> 12:24:16.020 align:start position:0% Bridge 12:24:16.020 --> 12:24:19.550 align:start position:0% Bridge only<12:24:16.680> one<12:24:17.040> designated<12:24:17.580> Port<12:24:18.000> per<12:24:18.480> segment<12:24:18.960> you 12:24:19.550 --> 12:24:19.560 align:start position:0% only one designated Port per segment you 12:24:19.560 --> 12:24:21.050 align:start position:0% only one designated Port per segment you can<12:24:19.680> see<12:24:19.800> there's<12:24:19.980> a<12:24:20.160> segment<12:24:20.460> at<12:24:20.700> the<12:24:20.820> bottom 12:24:21.050 --> 12:24:21.060 align:start position:0% can see there's a segment at the bottom 12:24:21.060 --> 12:24:22.246 align:start position:0% can see there's a segment at the bottom here 12:24:22.246 --> 12:24:22.256 align:start position:0% here 12:24:22.256 --> 12:24:24.586 align:start position:0% here if<12:24:22.616> I<12:24:22.740> see<12:24:22.916> Zero<12:24:23.520> slash<12:24:23.700> two<12:24:23.880> on<12:24:24.116> switch<12:24:24.300> two 12:24:24.586 --> 12:24:24.596 align:start position:0% if I see Zero slash two on switch two 12:24:24.596 --> 12:24:25.970 align:start position:0% if I see Zero slash two on switch two and<12:24:24.840> three 12:24:25.970 --> 12:24:25.980 align:start position:0% and three 12:24:25.980 --> 12:24:28.130 align:start position:0% and three the<12:24:26.400> toy<12:24:26.700> goes<12:24:27.000> to<12:24:27.116> the<12:24:27.300> lowest<12:24:27.596> root<12:24:27.960> Bridge 12:24:28.130 --> 12:24:28.140 align:start position:0% the toy goes to the lowest root Bridge 12:24:28.140 --> 12:24:31.490 align:start position:0% the toy goes to the lowest root Bridge ID<12:24:28.500> lowest<12:24:29.340> root<12:24:29.640> path<12:24:29.880> cost<12:24:30.200> lowest<12:24:31.200> sender 12:24:31.490 --> 12:24:31.500 align:start position:0% ID lowest root path cost lowest sender 12:24:31.500 --> 12:24:34.070 align:start position:0% ID lowest root path cost lowest sender Bridge<12:24:31.860> ID<12:24:32.160> and<12:24:32.520> lowest<12:24:32.936> Port<12:24:33.060> ID 12:24:34.070 --> 12:24:34.080 align:start position:0% Bridge ID and lowest Port ID 12:24:34.080 --> 12:24:35.746 align:start position:0% Bridge ID and lowest Port ID and<12:24:34.436> you<12:24:34.560> can<12:24:34.680> see<12:24:34.800> on<12:24:35.040> switch<12:24:35.160> two<12:24:35.400> and<12:24:35.580> three 12:24:35.746 --> 12:24:35.756 align:start position:0% and you can see on switch two and three 12:24:35.756 --> 12:24:37.490 align:start position:0% and you can see on switch two and three the<12:24:36.000> lowest<12:24:36.300> out<12:24:36.480> of<12:24:36.596> the<12:24:36.720> two<12:24:36.900> would<12:24:37.200> be<12:24:37.320> the 12:24:37.490 --> 12:24:37.500 align:start position:0% the lowest out of the two would be the 12:24:37.500 --> 12:24:40.970 align:start position:0% the lowest out of the two would be the switch<12:24:37.616> with<12:24:37.980> the<12:24:38.096> number<12:24:38.220> MAC<12:24:38.700> address<12:24:38.880> bb<12:24:39.480> bb 12:24:40.970 --> 12:24:40.980 align:start position:0% switch with the number MAC address bb bb 12:24:40.980 --> 12:24:42.530 align:start position:0% switch with the number MAC address bb bb and<12:24:41.340> so<12:24:41.520> on 12:24:42.530 --> 12:24:42.540 align:start position:0% and so on 12:24:42.540 --> 12:24:45.290 align:start position:0% and so on the<12:24:43.020> port<12:24:43.200> States<12:24:43.436> for<12:24:43.680> STP<12:24:44.220> can<12:24:44.640> only<12:24:44.820> be<12:24:45.060> one 12:24:45.290 --> 12:24:45.300 align:start position:0% the port States for STP can only be one 12:24:45.300 --> 12:24:47.330 align:start position:0% the port States for STP can only be one of<12:24:45.416> the<12:24:45.540> five<12:24:45.660> following<12:24:46.256> it's<12:24:46.740> forwarding 12:24:47.330 --> 12:24:47.340 align:start position:0% of the five following it's forwarding 12:24:47.340 --> 12:24:50.746 align:start position:0% of the five following it's forwarding it's<12:24:47.700> learning<12:24:48.300> it's<12:24:48.720> listening<12:24:49.200> blocking<12:24:49.980> or 12:24:50.746 --> 12:24:50.756 align:start position:0% it's learning it's listening blocking or 12:24:50.756 --> 12:24:52.490 align:start position:0% it's learning it's listening blocking or disabled 12:24:52.490 --> 12:24:52.500 align:start position:0% disabled 12:24:52.500 --> 12:24:54.170 align:start position:0% disabled all<12:24:52.980> right<12:24:53.096> so<12:24:53.276> we've<12:24:53.400> covered<12:24:53.700> a<12:24:53.820> fair<12:24:53.936> bit 12:24:54.170 --> 12:24:54.180 align:start position:0% all right so we've covered a fair bit 12:24:54.180 --> 12:24:55.850 align:start position:0% all right so we've covered a fair bit there<12:24:54.480> I<12:24:54.776> only<12:24:54.960> wanted<12:24:55.140> to<12:24:55.320> give<12:24:55.436> you<12:24:55.560> a<12:24:55.680> taster 12:24:55.850 --> 12:24:55.860 align:start position:0% there I only wanted to give you a taster 12:24:55.860 --> 12:24:59.510 align:start position:0% there I only wanted to give you a taster STP<12:24:56.756> and<12:24:58.140> um<12:24:58.140> there<12:24:58.616> could<12:24:58.740> be<12:24:58.860> a<12:24:58.980> lab<12:24:59.096> on<12:24:59.400> this 12:24:59.510 --> 12:24:59.520 align:start position:0% STP and um there could be a lab on this 12:24:59.520 --> 12:25:01.970 align:start position:0% STP and um there could be a lab on this I<12:24:59.820> haven't<12:24:59.936> decided<12:25:00.416> yet<12:25:00.740> obviously<12:25:01.740> you'll 12:25:01.970 --> 12:25:01.980 align:start position:0% I haven't decided yet obviously you'll 12:25:01.980 --> 12:25:03.350 align:start position:0% I haven't decided yet obviously you'll be<12:25:02.040> digging<12:25:02.276> into<12:25:02.400> a<12:25:02.640> lot<12:25:02.700> more<12:25:02.820> detail<12:25:03.180> when 12:25:03.350 --> 12:25:03.360 align:start position:0% be digging into a lot more detail when 12:25:03.360 --> 12:25:05.810 align:start position:0% be digging into a lot more detail when you<12:25:03.596> actually<12:25:03.720> come<12:25:04.020> to<12:25:04.200> do<12:25:04.380> the<12:25:04.560> CCNA<12:25:05.276> thanks 12:25:05.810 --> 12:25:05.820 align:start position:0% you actually come to do the CCNA thanks 12:25:05.820 --> 12:25:09.620 align:start position:0% you actually come to do the CCNA thanks for<12:25:06.000> listening 12:25:09.620 --> 12:25:09.630 align:start position:0% 12:25:09.630 --> 12:25:25.670 align:start position:0% [Music] 12:25:25.670 --> 12:25:25.680 align:start position:0% 12:25:25.680 --> 12:25:28.970 align:start position:0% welcome<12:25:26.220> to<12:25:26.460> modulate<12:25:27.000> lesson<12:25:27.480> 2B<12:25:28.020> power<12:25:28.560> over 12:25:28.970 --> 12:25:28.980 align:start position:0% welcome to modulate lesson 2B power over 12:25:28.980 --> 12:25:30.950 align:start position:0% welcome to modulate lesson 2B power over ethernet 12:25:30.950 --> 12:25:30.960 align:start position:0% ethernet 12:25:30.960 --> 12:25:32.926 align:start position:0% ethernet or<12:25:31.616> Poe 12:25:32.926 --> 12:25:32.936 align:start position:0% or Poe 12:25:32.936 --> 12:25:37.370 align:start position:0% or Poe what<12:25:33.660> is<12:25:33.840> poe<12:25:34.616> the<12:25:35.160> benefits<12:25:35.756> components 12:25:37.370 --> 12:25:37.380 align:start position:0% what is poe the benefits components 12:25:37.380 --> 12:25:40.010 align:start position:0% what is poe the benefits components the<12:25:37.980> power<12:25:38.160> supply<12:25:38.400> equipment<12:25:39.116> we<12:25:39.660> love<12:25:39.840> our 12:25:40.010 --> 12:25:40.020 align:start position:0% the power supply equipment we love our 12:25:40.020 --> 12:25:42.170 align:start position:0% the power supply equipment we love our abbreviations<12:25:40.500> there<12:25:40.860> PSE 12:25:42.170 --> 12:25:42.180 align:start position:0% abbreviations there PSE 12:25:42.180 --> 12:25:44.870 align:start position:0% abbreviations there PSE n-span<12:25:43.080> mid<12:25:43.740> span 12:25:44.870 --> 12:25:44.880 align:start position:0% n-span mid span 12:25:44.880 --> 12:25:46.790 align:start position:0% n-span mid span power<12:25:45.300> devices 12:25:46.790 --> 12:25:46.800 align:start position:0% power devices 12:25:46.800 --> 12:25:52.246 align:start position:0% power devices modes<12:25:47.640> in<12:25:47.936> Poe<12:25:48.680> standards<12:25:49.680> how<12:25:50.400> does<12:25:50.520> it<12:25:50.700> work 12:25:52.246 --> 12:25:52.256 align:start position:0% modes in Poe standards how does it work 12:25:52.256 --> 12:25:53.990 align:start position:0% modes in Poe standards how does it work what<12:25:52.740> is<12:25:52.980> it<12:25:53.096> first 12:25:53.990 --> 12:25:54.000 align:start position:0% what is it first 12:25:54.000 --> 12:25:57.350 align:start position:0% what is it first Poe<12:25:54.776> is<12:25:55.020> a<12:25:55.256> technology<12:25:55.616> that<12:25:55.980> allows<12:25:56.340> a<12:25:57.116> um<12:25:57.180> a 12:25:57.350 --> 12:25:57.360 align:start position:0% Poe is a technology that allows a um a 12:25:57.360 --> 12:25:59.510 align:start position:0% Poe is a technology that allows a um a device<12:25:57.720> connected<12:25:58.200> to<12:25:58.320> an<12:25:58.560> ethernet<12:25:58.740> cable<12:25:59.096> to 12:25:59.510 --> 12:25:59.520 align:start position:0% device connected to an ethernet cable to 12:25:59.520 --> 12:26:02.030 align:start position:0% device connected to an ethernet cable to receive<12:25:59.880> the<12:26:00.060> following<12:26:00.800> electrical<12:26:01.800> power 12:26:02.030 --> 12:26:02.040 align:start position:0% receive the following electrical power 12:26:02.040 --> 12:26:03.766 align:start position:0% receive the following electrical power and<12:26:02.756> data 12:26:03.766 --> 12:26:03.776 align:start position:0% and data 12:26:03.776 --> 12:26:06.830 align:start position:0% and data now<12:26:04.256> obviously<12:26:04.800> a<12:26:05.640> device<12:26:06.060> connected<12:26:06.480> to<12:26:06.660> an 12:26:06.830 --> 12:26:06.840 align:start position:0% now obviously a device connected to an 12:26:06.840 --> 12:26:08.690 align:start position:0% now obviously a device connected to an ether<12:26:07.080> cable<12:26:07.380> was<12:26:07.800> already<12:26:08.276> going<12:26:08.580> to<12:26:08.700> be 12:26:08.690 --> 12:26:08.700 align:start position:0% ether cable was already going to be 12:26:08.700 --> 12:26:10.906 align:start position:0% ether cable was already going to be receiving<12:26:09.060> data<12:26:09.596> because<12:26:09.776> that's<12:26:10.140> what<12:26:10.916> um 12:26:10.906 --> 12:26:10.916 align:start position:0% receiving data because that's what um 12:26:10.916 --> 12:26:12.950 align:start position:0% receiving data because that's what um ethernet<12:26:11.340> was<12:26:11.580> designed<12:26:11.936> for 12:26:12.950 --> 12:26:12.960 align:start position:0% ethernet was designed for 12:26:12.960 --> 12:26:14.990 align:start position:0% ethernet was designed for however<12:26:13.560> what<12:26:13.916> it<12:26:14.096> wasn't<12:26:14.460> initially 12:26:14.990 --> 12:26:15.000 align:start position:0% however what it wasn't initially 12:26:15.000 --> 12:26:16.980 align:start position:0% however what it wasn't initially designed<12:26:15.480> for<12:26:15.596> and<12:26:15.900> some<12:26:16.140> very<12:26:16.320> clever<12:26:16.616> people 12:26:16.980 --> 12:26:16.990 align:start position:0% designed for and some very clever people 12:26:16.990 --> 12:26:18.170 align:start position:0% designed for and some very clever people [Music] 12:26:18.170 --> 12:26:18.180 align:start position:0% [Music] 12:26:18.180 --> 12:26:21.586 align:start position:0% [Music] um found<12:26:18.720> or<12:26:19.020> realized<12:26:19.740> away<12:26:19.860> and<12:26:20.160> tested<12:26:20.580> it 12:26:21.586 --> 12:26:21.596 align:start position:0% um found or realized away and tested it 12:26:21.596 --> 12:26:23.630 align:start position:0% um found or realized away and tested it is<12:26:22.020> to<12:26:22.320> deliver<12:26:22.500> power 12:26:23.630 --> 12:26:23.640 align:start position:0% is to deliver power 12:26:23.640 --> 12:26:26.030 align:start position:0% is to deliver power and<12:26:24.416> it's<12:26:24.596> got<12:26:24.776> all<12:26:24.960> sorts<12:26:25.256> of<12:26:25.256> uses<12:26:25.740> we're 12:26:26.030 --> 12:26:26.040 align:start position:0% and it's got all sorts of uses we're 12:26:26.040 --> 12:26:28.490 align:start position:0% and it's got all sorts of uses we're talking<12:26:26.400> in<12:26:26.756> the<12:26:26.936> context<12:26:27.660> of<12:26:27.840> networking 12:26:28.490 --> 12:26:28.500 align:start position:0% talking in the context of networking 12:26:28.500 --> 12:26:31.370 align:start position:0% talking in the context of networking however<12:26:29.460> I<12:26:30.116> recently<12:26:30.480> bought<12:26:30.720> a<12:26:31.140> guitar 12:26:31.370 --> 12:26:31.380 align:start position:0% however I recently bought a guitar 12:26:31.380 --> 12:26:34.246 align:start position:0% however I recently bought a guitar effects<12:26:32.340> board<12:26:32.520> that<12:26:33.416> plugs<12:26:33.720> into<12:26:33.840> the<12:26:34.080> back 12:26:34.246 --> 12:26:34.256 align:start position:0% effects board that plugs into the back 12:26:34.256 --> 12:26:38.210 align:start position:0% effects board that plugs into the back of<12:26:34.436> my<12:26:34.680> amp<12:26:35.160> using<12:26:35.820> a<12:26:36.360> ethernet<12:26:36.840> cable<12:26:37.256> and<12:26:38.040> I 12:26:38.210 --> 12:26:38.220 align:start position:0% of my amp using a ethernet cable and I 12:26:38.220 --> 12:26:39.290 align:start position:0% of my amp using a ethernet cable and I thought<12:26:38.400> it<12:26:38.520> was<12:26:38.640> going<12:26:38.700> to<12:26:38.756> come<12:26:39.000> with<12:26:39.116> a 12:26:39.290 --> 12:26:39.300 align:start position:0% thought it was going to come with a 12:26:39.300 --> 12:26:40.906 align:start position:0% thought it was going to come with a power<12:26:39.416> supply<12:26:39.720> but<12:26:40.080> as<12:26:40.256> soon<12:26:40.380> as<12:26:40.436> I<12:26:40.560> plug<12:26:40.740> the 12:26:40.906 --> 12:26:40.916 align:start position:0% power supply but as soon as I plug the 12:26:40.916 --> 12:26:43.070 align:start position:0% power supply but as soon as I plug the ethernet<12:26:41.220> cable<12:26:41.580> in<12:26:41.820> it<12:26:42.360> actually<12:26:42.540> powered<12:26:42.960> up 12:26:43.070 --> 12:26:43.080 align:start position:0% ethernet cable in it actually powered up 12:26:43.080 --> 12:26:44.330 align:start position:0% ethernet cable in it actually powered up the<12:26:43.200> pedalboard 12:26:44.330 --> 12:26:44.340 align:start position:0% the pedalboard 12:26:44.340 --> 12:26:46.190 align:start position:0% the pedalboard and<12:26:44.820> the<12:26:44.936> pedal<12:26:45.180> board<12:26:45.300> offers<12:26:45.660> a<12:26:45.900> whole<12:26:46.020> bunch 12:26:46.190 --> 12:26:46.200 align:start position:0% and the pedal board offers a whole bunch 12:26:46.200 --> 12:26:49.010 align:start position:0% and the pedal board offers a whole bunch of<12:26:46.380> effects<12:26:46.980> you<12:26:47.276> can<12:26:47.460> record<12:26:47.936> about<12:26:48.720> five 12:26:49.010 --> 12:26:49.020 align:start position:0% of effects you can record about five 12:26:49.020 --> 12:26:51.766 align:start position:0% of effects you can record about five minutes<12:26:49.256> of<12:26:49.560> Music<12:26:50.060> Loop<12:26:51.060> it<12:26:51.180> add<12:26:51.480> other 12:26:51.766 --> 12:26:51.776 align:start position:0% minutes of Music Loop it add other 12:26:51.776 --> 12:26:54.106 align:start position:0% minutes of Music Loop it add other tracks<12:26:52.200> onto<12:26:52.560> that<12:26:52.800> Loop<12:26:53.160> and<12:26:53.700> a<12:26:53.880> whole<12:26:53.936> bunch 12:26:54.106 --> 12:26:54.116 align:start position:0% tracks onto that Loop and a whole bunch 12:26:54.116 --> 12:26:57.106 align:start position:0% tracks onto that Loop and a whole bunch of<12:26:54.300> stuff<12:26:54.540> so<12:26:55.980> um<12:26:56.040> very<12:26:56.340> clever<12:26:56.640> technology 12:26:57.106 --> 12:26:57.116 align:start position:0% of stuff so um very clever technology 12:26:57.116 --> 12:26:59.746 align:start position:0% of stuff so um very clever technology and<12:26:57.360> it's<12:26:57.480> got<12:26:57.720> a<12:26:57.840> multitude<12:26:58.436> of<12:26:58.680> purposes 12:26:59.746 --> 12:26:59.756 align:start position:0% and it's got a multitude of purposes 12:26:59.756 --> 12:27:01.190 align:start position:0% and it's got a multitude of purposes and<12:27:00.116> it's<12:27:00.240> just<12:27:00.360> one<12:27:00.540> of<12:27:00.660> those<12:27:00.720> things<12:27:00.900> when 12:27:01.190 --> 12:27:01.200 align:start position:0% and it's just one of those things when 12:27:01.200 --> 12:27:02.630 align:start position:0% and it's just one of those things when it's<12:27:01.380> invented<12:27:01.860> you<12:27:02.040> think<12:27:02.160> why<12:27:02.400> didn't 12:27:02.630 --> 12:27:02.640 align:start position:0% it's invented you think why didn't 12:27:02.640 --> 12:27:05.630 align:start position:0% it's invented you think why didn't somebody<12:27:02.880> think<12:27:03.180> of<12:27:03.300> that<12:27:03.480> earlier 12:27:05.630 --> 12:27:05.640 align:start position:0% somebody think of that earlier 12:27:05.640 --> 12:27:07.906 align:start position:0% somebody think of that earlier the<12:27:05.820> power<12:27:06.000> devices<12:27:06.416> that<12:27:06.776> support<12:27:07.020> Poe<12:27:07.680> only 12:27:07.906 --> 12:27:07.916 align:start position:0% the power devices that support Poe only 12:27:07.916 --> 12:27:09.766 align:start position:0% the power devices that support Poe only operate<12:27:08.276> from<12:27:08.520> the<12:27:08.700> piracies<12:27:09.360> through<12:27:09.660> the 12:27:09.766 --> 12:27:09.776 align:start position:0% operate from the piracies through the 12:27:09.776 --> 12:27:11.746 align:start position:0% operate from the piracies through the ethernet<12:27:10.080> cable<12:27:10.500> obviously<12:27:11.400> there's<12:27:11.580> a 12:27:11.746 --> 12:27:11.756 align:start position:0% ethernet cable obviously there's a 12:27:11.756 --> 12:27:15.106 align:start position:0% ethernet cable obviously there's a finite<12:27:12.180> amount<12:27:12.596> of<12:27:12.720> charge<12:27:13.436> or<12:27:13.980> power<12:27:14.220> that 12:27:15.106 --> 12:27:15.116 align:start position:0% finite amount of charge or power that 12:27:15.116 --> 12:27:17.510 align:start position:0% finite amount of charge or power that you<12:27:15.240> can<12:27:15.360> push<12:27:15.720> through<12:27:16.200> the<12:27:16.740> cable<12:27:17.220> because 12:27:17.510 --> 12:27:17.520 align:start position:0% you can push through the cable because 12:27:17.520 --> 12:27:19.970 align:start position:0% you can push through the cable because it's<12:27:17.880> quite<12:27:18.116> a<12:27:18.300> thin<12:27:18.480> strand<12:27:18.840> of<12:27:19.020> metal 12:27:19.970 --> 12:27:19.980 align:start position:0% it's quite a thin strand of metal 12:27:19.980 --> 12:27:22.790 align:start position:0% it's quite a thin strand of metal but<12:27:20.936> um<12:27:20.936> obviously<12:27:21.540> avoid<12:27:22.140> the<12:27:22.320> need<12:27:22.500> for 12:27:22.790 --> 12:27:22.800 align:start position:0% but um obviously avoid the need for 12:27:22.800 --> 12:27:25.370 align:start position:0% but um obviously avoid the need for additional<12:27:23.400> electrical<12:27:24.240> wiring<12:27:24.720> are<12:27:25.200> you 12:27:25.370 --> 12:27:25.380 align:start position:0% additional electrical wiring are you 12:27:25.380 --> 12:27:27.710 align:start position:0% additional electrical wiring are you your<12:27:25.616> power<12:27:25.860> supply<12:27:26.096> unit<12:27:26.460> and<12:27:26.820> all<12:27:27.000> the<12:27:27.180> wires 12:27:27.710 --> 12:27:27.720 align:start position:0% your power supply unit and all the wires 12:27:27.720 --> 12:27:29.630 align:start position:0% your power supply unit and all the wires that<12:27:27.840> come<12:27:28.020> with<12:27:28.200> that<12:27:28.320> and<12:27:28.560> as<12:27:29.160> we<12:27:29.276> all<12:27:29.460> know 12:27:29.630 --> 12:27:29.640 align:start position:0% that come with that and as we all know 12:27:29.640 --> 12:27:31.426 align:start position:0% that come with that and as we all know every<12:27:30.000> single<12:27:30.300> power<12:27:30.480> device<12:27:30.840> has<12:27:31.140> got<12:27:31.320> a 12:27:31.426 --> 12:27:31.436 align:start position:0% every single power device has got a 12:27:31.436 --> 12:27:32.266 align:start position:0% every single power device has got a different 12:27:32.266 --> 12:27:32.276 align:start position:0% different 12:27:32.276 --> 12:27:34.606 align:start position:0% different and<12:27:32.936> socket<12:27:33.416> a<12:27:33.596> jack<12:27:33.776> on<12:27:34.020> it<12:27:34.140> and<12:27:34.320> it<12:27:34.500> just 12:27:34.606 --> 12:27:34.616 align:start position:0% and socket a jack on it and it just 12:27:34.616 --> 12:27:36.406 align:start position:0% and socket a jack on it and it just makes<12:27:34.740> it<12:27:34.980> very<12:27:35.096> awkward<12:27:35.520> to<12:27:35.756> keep<12:27:35.880> a<12:27:36.060> track<12:27:36.240> of 12:27:36.406 --> 12:27:36.416 align:start position:0% makes it very awkward to keep a track of 12:27:36.416 --> 12:27:38.630 align:start position:0% makes it very awkward to keep a track of which<12:27:36.596> is<12:27:36.840> which<12:27:37.080> and<12:27:37.860> then<12:27:37.980> obviously<12:27:38.340> your 12:27:38.630 --> 12:27:38.640 align:start position:0% which is which and then obviously your 12:27:38.640 --> 12:27:41.266 align:start position:0% which is which and then obviously your power<12:27:38.820> supply<12:27:39.116> can<12:27:39.540> die<12:27:39.776> making<12:27:40.616> our<12:27:40.916> lives<12:27:41.040> a 12:27:41.266 --> 12:27:41.276 align:start position:0% power supply can die making our lives a 12:27:41.276 --> 12:27:42.766 align:start position:0% power supply can die making our lives a misery 12:27:42.766 --> 12:27:42.776 align:start position:0% misery 12:27:42.776 --> 12:27:44.510 align:start position:0% misery so<12:27:43.020> what<12:27:43.256> is<12:27:43.380> it<12:27:43.500> we're<12:27:43.740> supplying<12:27:44.096> electrical 12:27:44.510 --> 12:27:44.520 align:start position:0% so what is it we're supplying electrical 12:27:44.520 --> 12:27:46.310 align:start position:0% so what is it we're supplying electrical power<12:27:44.700> through<12:27:45.000> the<12:27:45.240> electrical<12:27:45.720> ethernet 12:27:46.310 --> 12:27:46.320 align:start position:0% power through the electrical ethernet 12:27:46.320 --> 12:27:48.350 align:start position:0% power through the electrical ethernet cable<12:27:46.680> in<12:27:46.980> order<12:27:47.160> to<12:27:47.340> power<12:27:47.520> devices<12:27:47.936> I<12:27:48.240> know 12:27:48.350 --> 12:27:48.360 align:start position:0% cable in order to power devices I know 12:27:48.360 --> 12:27:50.870 align:start position:0% cable in order to power devices I know I'm<12:27:48.540> stating<12:27:48.720> the<12:27:48.960> obvious<12:27:49.200> here 12:27:50.870 --> 12:27:50.880 align:start position:0% I'm stating the obvious here 12:27:50.880 --> 12:27:52.970 align:start position:0% I'm stating the obvious here and<12:27:51.416> of<12:27:51.660> course<12:27:51.776> is<12:27:52.020> uh<12:27:52.320> designed<12:27:52.800> for 12:27:52.970 --> 12:27:52.980 align:start position:0% and of course is uh designed for 12:27:52.980 --> 12:27:55.370 align:start position:0% and of course is uh designed for beginners<12:27:53.340> as<12:27:53.520> well<12:27:53.700> very<12:27:54.660> handy<12:27:54.960> for<12:27:55.140> voice 12:27:55.370 --> 12:27:55.380 align:start position:0% beginners as well very handy for voice 12:27:55.380 --> 12:27:58.790 align:start position:0% beginners as well very handy for voice over<12:27:55.616> IP<12:27:56.160> uh<12:27:56.880> telephony<12:27:57.360> very<12:27:58.140> useful<12:27:58.436> indeed 12:27:58.790 --> 12:27:58.800 align:start position:0% over IP uh telephony very useful indeed 12:27:58.800 --> 12:28:00.890 align:start position:0% over IP uh telephony very useful indeed because<12:27:58.916> it<12:27:59.220> just<12:27:59.936> um<12:28:00.000> saves<12:28:00.540> those<12:28:00.660> extra 12:28:00.890 --> 12:28:00.900 align:start position:0% because it just um saves those extra 12:28:00.900 --> 12:28:02.990 align:start position:0% because it just um saves those extra wires<12:28:01.436> and<12:28:01.560> cables 12:28:02.990 --> 12:28:03.000 align:start position:0% wires and cables 12:28:03.000 --> 12:28:05.870 align:start position:0% wires and cables wireless<12:28:03.360> access<12:28:03.776> points<12:28:04.380> network<12:28:04.680> cameras 12:28:05.870 --> 12:28:05.880 align:start position:0% wireless access points network cameras 12:28:05.880 --> 12:28:07.310 align:start position:0% wireless access points network cameras um very<12:28:06.180> big<12:28:06.360> in<12:28:06.540> the<12:28:06.660> field<12:28:06.840> of<12:28:07.020> security 12:28:07.310 --> 12:28:07.320 align:start position:0% um very big in the field of security 12:28:07.320 --> 12:28:09.766 align:start position:0% um very big in the field of security especially<12:28:07.980> industrial<12:28:08.460> security<12:28:08.820> and<12:28:09.300> shops 12:28:09.766 --> 12:28:09.776 align:start position:0% especially industrial security and shops 12:28:09.776 --> 12:28:12.650 align:start position:0% especially industrial security and shops and<12:28:09.900> warehouses 12:28:12.650 --> 12:28:12.660 align:start position:0% 12:28:12.660 --> 12:28:14.570 align:start position:0% since<12:28:13.020> the<12:28:13.320> devices<12:28:13.500> can<12:28:14.040> consume<12:28:14.460> the 12:28:14.570 --> 12:28:14.580 align:start position:0% since the devices can consume the 12:28:14.580 --> 12:28:16.010 align:start position:0% since the devices can consume the required<12:28:14.936> power<12:28:15.116> from<12:28:15.360> the<12:28:15.540> ethernet<12:28:15.776> cable 12:28:16.010 --> 12:28:16.020 align:start position:0% required power from the ethernet cable 12:28:16.020 --> 12:28:18.406 align:start position:0% required power from the ethernet cable there's<12:28:16.436> no<12:28:16.616> need<12:28:16.800> for<12:28:16.980> the<12:28:17.276> separate<12:28:18.060> local 12:28:18.406 --> 12:28:18.416 align:start position:0% there's no need for the separate local 12:28:18.416 --> 12:28:20.030 align:start position:0% there's no need for the separate local power<12:28:18.720> supply 12:28:20.030 --> 12:28:20.040 align:start position:0% power supply 12:28:20.040 --> 12:28:21.830 align:start position:0% power supply if<12:28:20.460> the<12:28:20.700> device<12:28:20.880> is<12:28:21.116> an<12:28:21.300> outdoor<12:28:21.660> wireless 12:28:21.830 --> 12:28:21.840 align:start position:0% if the device is an outdoor wireless 12:28:21.840 --> 12:28:24.890 align:start position:0% if the device is an outdoor wireless access<12:28:22.500> point<12:28:22.916> or<12:28:23.220> a<12:28:23.340> WAP<12:28:23.640> it<12:28:24.240> supports<12:28:24.660> then 12:28:24.890 --> 12:28:24.900 align:start position:0% access point or a WAP it supports then 12:28:24.900 --> 12:28:26.690 align:start position:0% access point or a WAP it supports then we<12:28:25.080> can<12:28:25.200> do<12:28:25.320> the<12:28:25.436> following<12:28:25.800> we<12:28:26.220> can<12:28:26.340> send<12:28:26.520> it 12:28:26.690 --> 12:28:26.700 align:start position:0% we can do the following we can send it 12:28:26.700 --> 12:28:28.850 align:start position:0% we can do the following we can send it electrical<12:28:27.180> power<12:28:27.360> and<12:28:28.080> we<12:28:28.200> can<12:28:28.320> send<12:28:28.500> data 12:28:28.850 --> 12:28:28.860 align:start position:0% electrical power and we can send data 12:28:28.860 --> 12:28:30.530 align:start position:0% electrical power and we can send data through<12:28:28.980> the<12:28:29.160> cable 12:28:30.530 --> 12:28:30.540 align:start position:0% through the cable 12:28:30.540 --> 12:28:33.290 align:start position:0% through the cable eliminates<12:28:31.436> the<12:28:31.680> local<12:28:31.860> power<12:28:32.160> source 12:28:33.290 --> 12:28:33.300 align:start position:0% eliminates the local power source 12:28:33.300 --> 12:28:35.990 align:start position:0% eliminates the local power source it's<12:28:33.840> saving<12:28:34.200> you<12:28:34.320> money<12:28:34.560> no<12:28:35.220> great<12:28:35.460> no<12:28:35.820> need 12:28:35.990 --> 12:28:36.000 align:start position:0% it's saving you money no great no need 12:28:36.000 --> 12:28:38.630 align:start position:0% it's saving you money no great no need to<12:28:36.240> upgrade<12:28:36.720> the<12:28:36.960> existing<12:28:37.256> CAT5<12:28:37.800> or<12:28:38.040> coccyx 12:28:38.630 --> 12:28:38.640 align:start position:0% to upgrade the existing CAT5 or coccyx 12:28:38.640 --> 12:28:41.266 align:start position:0% to upgrade the existing CAT5 or coccyx cabling<12:28:39.180> which<12:28:39.540> is<12:28:39.660> another<12:28:39.776> Lifesaver<12:28:40.560> and<12:28:41.160> a 12:28:41.266 --> 12:28:41.276 align:start position:0% cabling which is another Lifesaver and a 12:28:41.276 --> 12:28:43.790 align:start position:0% cabling which is another Lifesaver and a wallet<12:28:41.580> saver<12:28:41.820> for<12:28:42.116> companies<12:28:42.500> no<12:28:43.500> need<12:28:43.680> to 12:28:43.790 --> 12:28:43.800 align:start position:0% wallet saver for companies no need to 12:28:43.800 --> 12:28:45.890 align:start position:0% wallet saver for companies no need to purchase<12:28:44.160> the<12:28:44.460> power<12:28:44.640> outlets<12:28:45.480> electrical 12:28:45.890 --> 12:28:45.900 align:start position:0% purchase the power outlets electrical 12:28:45.900 --> 12:28:48.050 align:start position:0% purchase the power outlets electrical wiring 12:28:48.050 --> 12:28:48.060 align:start position:0% wiring 12:28:48.060 --> 12:28:49.906 align:start position:0% wiring I'm<12:28:48.416> not<12:28:48.540> sure<12:28:48.660> if<12:28:48.776> I'd<12:28:48.960> talk<12:28:49.200> about<12:28:49.380> that<12:28:49.616> in<12:28:49.800> a 12:28:49.906 --> 12:28:49.916 align:start position:0% I'm not sure if I'd talk about that in a 12:28:49.916 --> 12:28:51.290 align:start position:0% I'm not sure if I'd talk about that in a moment<12:28:50.096> as<12:28:50.400> well<12:28:50.520> but<12:28:50.700> it's<12:28:50.880> just<12:28:51.060> another 12:28:51.290 --> 12:28:51.300 align:start position:0% moment as well but it's just another 12:28:51.300 --> 12:28:54.230 align:start position:0% moment as well but it's just another thing<12:28:51.776> uh<12:28:52.436> that<12:28:52.680> that<12:28:52.980> wouldn't<12:28:53.580> possibly<12:28:54.000> go 12:28:54.230 --> 12:28:54.240 align:start position:0% thing uh that that wouldn't possibly go 12:28:54.240 --> 12:28:55.730 align:start position:0% thing uh that that wouldn't possibly go wrong<12:28:54.416> I<12:28:54.720> can't<12:28:54.840> remember<12:28:55.020> if<12:28:55.256> I've<12:28:55.436> put<12:28:55.616> this 12:28:55.730 --> 12:28:55.740 align:start position:0% wrong I can't remember if I've put this 12:28:55.740 --> 12:28:58.010 align:start position:0% wrong I can't remember if I've put this in<12:28:55.916> a<12:28:56.040> slide<12:28:56.276> somewhere<12:28:56.756> so<12:28:57.360> you've<12:28:57.596> got<12:28:57.720> one 12:28:58.010 --> 12:28:58.020 align:start position:0% in a slide somewhere so you've got one 12:28:58.020 --> 12:28:58.906 align:start position:0% in a slide somewhere so you've got one less 12:28:58.906 --> 12:28:58.916 align:start position:0% less 12:28:58.916 --> 12:29:03.106 align:start position:0% less um<12:28:58.980> point<12:28:59.276> of<12:28:59.460> failure<12:28:59.936> there 12:29:03.106 --> 12:29:03.116 align:start position:0% 12:29:03.116 --> 12:29:05.630 align:start position:0% very<12:29:04.020> easy<12:29:04.140> to<12:29:04.436> install<12:29:04.680> basically<12:29:05.400> you<12:29:05.520> just 12:29:05.630 --> 12:29:05.640 align:start position:0% very easy to install basically you just 12:29:05.640 --> 12:29:08.150 align:start position:0% very easy to install basically you just plug<12:29:05.820> it<12:29:06.000> plug<12:29:06.300> and<12:29:06.480> play<12:29:06.720> you<12:29:07.560> can<12:29:07.680> install<12:29:07.860> it 12:29:08.150 --> 12:29:08.160 align:start position:0% plug it plug and play you can install it 12:29:08.160 --> 12:29:09.530 align:start position:0% plug it plug and play you can install it even<12:29:08.276> though<12:29:08.520> locations<12:29:08.936> that<12:29:09.116> are<12:29:09.240> hard<12:29:09.360> to 12:29:09.530 --> 12:29:09.540 align:start position:0% even though locations that are hard to 12:29:09.540 --> 12:29:11.150 align:start position:0% even though locations that are hard to reach<12:29:09.720> because<12:29:09.960> there's<12:29:10.200> no<12:29:10.436> need<12:29:10.616> for<12:29:10.860> local 12:29:11.150 --> 12:29:11.160 align:start position:0% reach because there's no need for local 12:29:11.160 --> 12:29:13.190 align:start position:0% reach because there's no need for local power 12:29:13.190 --> 12:29:13.200 align:start position:0% power 12:29:13.200 --> 12:29:15.650 align:start position:0% power increase<12:29:13.616> reliability 12:29:15.650 --> 12:29:15.660 align:start position:0% increase reliability 12:29:15.660 --> 12:29:17.630 align:start position:0% increase reliability um<12:29:15.720> less<12:29:16.436> risk<12:29:16.800> of<12:29:16.860> power<12:29:17.040> interruptions 12:29:17.630 --> 12:29:17.640 align:start position:0% um less risk of power interruptions 12:29:17.640 --> 12:29:21.106 align:start position:0% um less risk of power interruptions caused<12:29:18.060> by<12:29:18.116> human<12:29:18.680> interference<12:29:19.880> because<12:29:20.880> the 12:29:21.106 --> 12:29:21.116 align:start position:0% caused by human interference because the 12:29:21.116 --> 12:29:23.266 align:start position:0% caused by human interference because the device<12:29:21.360> is<12:29:21.596> essentially<12:29:22.080> powered<12:29:22.616> a<12:29:23.040> lot<12:29:23.220> of 12:29:23.266 --> 12:29:23.276 align:start position:0% device is essentially powered a lot of 12:29:23.276 --> 12:29:25.310 align:start position:0% device is essentially powered a lot of the<12:29:23.340> time<12:29:23.460> our<12:29:23.700> networking<12:29:24.116> equipment<12:29:24.540> has<12:29:25.020> a 12:29:25.310 --> 12:29:25.320 align:start position:0% the time our networking equipment has a 12:29:25.320 --> 12:29:26.990 align:start position:0% the time our networking equipment has a redundant<12:29:25.740> power<12:29:26.040> supplies<12:29:26.460> as<12:29:26.640> well<12:29:26.756> and 12:29:26.990 --> 12:29:27.000 align:start position:0% redundant power supplies as well and 12:29:27.000 --> 12:29:29.210 align:start position:0% redundant power supplies as well and backup<12:29:27.300> generators<12:29:27.900> especially<12:29:28.800> if<12:29:28.916> it's<12:29:29.040> an 12:29:29.210 --> 12:29:29.220 align:start position:0% backup generators especially if it's an 12:29:29.220 --> 12:29:30.470 align:start position:0% backup generators especially if it's an ISP 12:29:30.470 --> 12:29:30.480 align:start position:0% ISP 12:29:30.480 --> 12:29:32.450 align:start position:0% ISP so<12:29:30.960> they'll<12:29:31.140> keep<12:29:31.380> working 12:29:32.450 --> 12:29:32.460 align:start position:0% so they'll keep working 12:29:32.460 --> 12:29:35.030 align:start position:0% so they'll keep working enhanced<12:29:33.416> Operational<12:29:33.840> Support<12:29:34.320> and 12:29:35.030 --> 12:29:35.040 align:start position:0% enhanced Operational Support and 12:29:35.040 --> 12:29:36.830 align:start position:0% enhanced Operational Support and monitoring<12:29:35.580> and<12:29:35.756> Remote<12:29:35.936> Management<12:29:36.240> we<12:29:36.720> can 12:29:36.830 --> 12:29:36.840 align:start position:0% monitoring and Remote Management we can 12:29:36.840 --> 12:29:39.290 align:start position:0% monitoring and Remote Management we can do<12:29:36.960> through<12:29:37.140> SNMP<12:29:37.800> so<12:29:38.040> we<12:29:38.220> can<12:29:38.400> power<12:29:39.000> the 12:29:39.290 --> 12:29:39.300 align:start position:0% do through SNMP so we can power the 12:29:39.300 --> 12:29:41.870 align:start position:0% do through SNMP so we can power the devices<12:29:39.720> and<12:29:40.680> perform<12:29:40.980> different<12:29:41.340> operations 12:29:41.870 --> 12:29:41.880 align:start position:0% devices and perform different operations 12:29:41.880 --> 12:29:43.906 align:start position:0% devices and perform different operations over<12:29:42.416> the<12:29:42.660> network 12:29:43.906 --> 12:29:43.916 align:start position:0% over the network 12:29:43.916 --> 12:29:46.070 align:start position:0% over the network very<12:29:44.400> handy<12:29:44.756> I<12:29:45.000> know<12:29:45.180> I<12:29:45.360> could<12:29:45.540> remotely 12:29:46.070 --> 12:29:46.080 align:start position:0% very handy I know I could remotely 12:29:46.080 --> 12:29:49.490 align:start position:0% very handy I know I could remotely reboot<12:29:47.040> different<12:29:47.340> devices<12:29:48.080> on<12:29:49.080> my<12:29:49.256> remote 12:29:49.490 --> 12:29:49.500 align:start position:0% reboot different devices on my remote 12:29:49.500 --> 12:29:51.290 align:start position:0% reboot different devices on my remote rack 12:29:51.290 --> 12:29:51.300 align:start position:0% rack 12:29:51.300 --> 12:29:52.850 align:start position:0% rack um<12:29:51.416> if<12:29:51.660> I<12:29:51.840> couldn't<12:29:51.960> reach<12:29:52.320> it<12:29:52.436> and<12:29:52.680> I<12:29:52.800> didn't 12:29:52.850 --> 12:29:52.860 align:start position:0% um if I couldn't reach it and I didn't 12:29:52.860 --> 12:29:54.650 align:start position:0% um if I couldn't reach it and I didn't want<12:29:53.040> to<12:29:53.160> pay<12:29:53.276> a<12:29:53.460> tech<12:29:53.640> to<12:29:53.820> go<12:29:53.936> and<12:29:54.116> power<12:29:54.300> cycle 12:29:54.650 --> 12:29:54.660 align:start position:0% want to pay a tech to go and power cycle 12:29:54.660 --> 12:29:57.650 align:start position:0% want to pay a tech to go and power cycle stuff<12:29:54.960> I<12:29:55.616> could<12:29:55.740> just<12:29:55.916> send<12:29:56.160> a<12:29:56.400> message<12:29:57.000> for 12:29:57.650 --> 12:29:57.660 align:start position:0% stuff I could just send a message for 12:29:57.660 --> 12:30:02.150 align:start position:0% stuff I could just send a message for the<12:29:57.840> power<12:29:58.020> unit<12:29:58.320> to<12:29:58.680> reboot<12:29:59.400> if<12:29:59.580> it<12:29:59.756> needed<12:30:00.000> to 12:30:02.150 --> 12:30:02.160 align:start position:0% the power unit to reboot if it needed to 12:30:02.160 --> 12:30:04.130 align:start position:0% the power unit to reboot if it needed to all<12:30:02.580> right<12:30:02.756> two<12:30:02.936> basic<12:30:03.300> components<12:30:03.900> your 12:30:04.130 --> 12:30:04.140 align:start position:0% all right two basic components your 12:30:04.140 --> 12:30:06.290 align:start position:0% all right two basic components your power<12:30:04.380> supply<12:30:04.616> equipment<12:30:05.096> and<12:30:05.520> your<12:30:05.700> powered 12:30:06.290 --> 12:30:06.300 align:start position:0% power supply equipment and your powered 12:30:06.300 --> 12:30:07.490 align:start position:0% power supply equipment and your powered device 12:30:07.490 --> 12:30:07.500 align:start position:0% device 12:30:07.500 --> 12:30:10.970 align:start position:0% device your<12:30:08.096> PSE<12:30:08.660> is<12:30:09.660> the<12:30:09.960> a<12:30:10.200> unit<12:30:10.500> that<12:30:10.740> adds 12:30:10.970 --> 12:30:10.980 align:start position:0% your PSE is the a unit that adds 12:30:10.980 --> 12:30:13.130 align:start position:0% your PSE is the a unit that adds electrical<12:30:11.340> power<12:30:11.520> to<12:30:11.700> the<12:30:11.880> ethernet<12:30:12.180> cable 12:30:13.130 --> 12:30:13.140 align:start position:0% electrical power to the ethernet cable 12:30:13.140 --> 12:30:16.370 align:start position:0% electrical power to the ethernet cable you've<12:30:13.560> got<12:30:13.680> n<12:30:13.980> Span<12:30:14.460> and<12:30:14.820> mid<12:30:15.060> span 12:30:16.370 --> 12:30:16.380 align:start position:0% you've got n Span and mid span 12:30:16.380 --> 12:30:18.230 align:start position:0% you've got n Span and mid span the<12:30:16.740> end<12:30:16.800> span<12:30:17.160> is<12:30:17.400> it<12:30:17.520> refers<12:30:17.820> to<12:30:17.936> a<12:30:18.116> switch 12:30:18.230 --> 12:30:18.240 align:start position:0% the end span is it refers to a switch 12:30:18.240 --> 12:30:20.990 align:start position:0% the end span is it refers to a switch that<12:30:18.540> supports<12:30:19.020> Poe<12:30:19.740> in<12:30:20.096> addition<12:30:20.400> to<12:30:20.700> its 12:30:20.990 --> 12:30:21.000 align:start position:0% that supports Poe in addition to its 12:30:21.000 --> 12:30:23.870 align:start position:0% that supports Poe in addition to its switching<12:30:21.360> role<12:30:21.776> so<12:30:22.080> we<12:30:22.256> can<12:30:22.436> do<12:30:22.560> both<12:30:22.880> these 12:30:23.870 --> 12:30:23.880 align:start position:0% switching role so we can do both these 12:30:23.880 --> 12:30:25.670 align:start position:0% switching role so we can do both these switches<12:30:24.240> are<12:30:24.480> capable<12:30:24.840> of<12:30:25.200> sending 12:30:25.670 --> 12:30:25.680 align:start position:0% switches are capable of sending 12:30:25.680 --> 12:30:29.630 align:start position:0% switches are capable of sending electrical<12:30:26.276> power<12:30:26.460> and<12:30:27.000> data<12:30:27.480> to<12:30:27.596> the<12:30:28.020> device 12:30:29.630 --> 12:30:29.640 align:start position:0% electrical power and data to the device 12:30:29.640 --> 12:30:32.030 align:start position:0% electrical power and data to the device mid-span<12:30:30.300> refers<12:30:30.660> to<12:30:30.840> a<12:30:30.960> standalone<12:30:31.436> inline 12:30:32.030 --> 12:30:32.040 align:start position:0% mid-span refers to a standalone inline 12:30:32.040 --> 12:30:34.010 align:start position:0% mid-span refers to a standalone inline injector<12:30:32.820> that<12:30:33.116> provides<12:30:33.480> power<12:30:33.660> to<12:30:33.900> the 12:30:34.010 --> 12:30:34.020 align:start position:0% injector that provides power to the 12:30:34.020 --> 12:30:36.230 align:start position:0% injector that provides power to the Ethernet<12:30:34.380> cable<12:30:34.680> so<12:30:35.096> it's<12:30:35.276> not<12:30:35.520> built<12:30:35.820> into<12:30:35.880> a 12:30:36.230 --> 12:30:36.240 align:start position:0% Ethernet cable so it's not built into a 12:30:36.240 --> 12:30:37.070 align:start position:0% Ethernet cable so it's not built into a switch 12:30:37.070 --> 12:30:37.080 align:start position:0% switch 12:30:37.080 --> 12:30:38.870 align:start position:0% switch this<12:30:37.616> is<12:30:37.740> a<12:30:37.916> situations<12:30:38.276> where<12:30:38.580> a<12:30:38.700> switch 12:30:38.870 --> 12:30:38.880 align:start position:0% this is a situations where a switch 12:30:38.880 --> 12:30:41.630 align:start position:0% this is a situations where a switch doesn't<12:30:39.180> have<12:30:39.416> the<12:30:39.660> built-in<12:30:40.080> Poe<12:30:40.740> it<12:30:41.460> could 12:30:41.630 --> 12:30:41.640 align:start position:0% doesn't have the built-in Poe it could 12:30:41.640 --> 12:30:43.370 align:start position:0% doesn't have the built-in Poe it could be<12:30:41.700> an<12:30:41.820> older<12:30:42.116> model<12:30:42.240> or<12:30:42.480> a<12:30:42.660> cheaper<12:30:42.960> model<12:30:43.080> for 12:30:43.370 --> 12:30:43.380 align:start position:0% be an older model or a cheaper model for 12:30:43.380 --> 12:30:45.290 align:start position:0% be an older model or a cheaper model for whatever<12:30:43.500> reason 12:30:45.290 --> 12:30:45.300 align:start position:0% whatever reason 12:30:45.300 --> 12:30:47.390 align:start position:0% whatever reason so<12:30:45.776> you<12:30:45.900> can<12:30:46.020> pass<12:30:46.140> the<12:30:46.380> data<12:30:46.740> coming<12:30:46.980> from<12:30:47.220> the 12:30:47.390 --> 12:30:47.400 align:start position:0% so you can pass the data coming from the 12:30:47.400 --> 12:30:50.450 align:start position:0% so you can pass the data coming from the switch<12:30:47.580> to<12:30:47.936> the<12:30:48.116> inline<12:30:48.416> injector<12:30:49.160> and<12:30:50.160> can 12:30:50.450 --> 12:30:50.460 align:start position:0% switch to the inline injector and can 12:30:50.460 --> 12:30:52.730 align:start position:0% switch to the inline injector and can output<12:30:50.820> the<12:30:51.060> same<12:30:51.180> data<12:30:51.720> but<12:30:51.960> it<12:30:52.140> adds<12:30:52.500> power 12:30:52.730 --> 12:30:52.740 align:start position:0% output the same data but it adds power 12:30:52.740 --> 12:30:54.830 align:start position:0% output the same data but it adds power to<12:30:53.520> the<12:30:54.180> um 12:30:54.830 --> 12:30:54.840 align:start position:0% to the um 12:30:54.840 --> 12:30:57.290 align:start position:0% to the um points<12:30:55.436> of<12:30:55.560> the<12:30:55.680> cable<12:30:55.860> there 12:30:57.290 --> 12:30:57.300 align:start position:0% points of the cable there 12:30:57.300 --> 12:30:59.990 align:start position:0% points of the cable there the<12:30:57.776> power<12:30:57.900> device<12:30:58.200> supports<12:30:58.860> Poe<12:30:59.400> receives 12:30:59.990 --> 12:31:00.000 align:start position:0% the power device supports Poe receives 12:31:00.000 --> 12:31:03.170 align:start position:0% the power device supports Poe receives the<12:31:00.180> power<12:31:00.360> via<12:31:00.720> an<12:31:00.900> ethernet<12:31:01.140> cable 12:31:03.170 --> 12:31:03.180 align:start position:0% the power via an ethernet cable 12:31:03.180 --> 12:31:05.926 align:start position:0% the power via an ethernet cable now<12:31:03.720> in<12:31:04.140> Poe<12:31:04.740> there's<12:31:05.040> two<12:31:05.220> different<12:31:05.460> modes 12:31:05.926 --> 12:31:05.936 align:start position:0% now in Poe there's two different modes 12:31:05.936 --> 12:31:08.690 align:start position:0% now in Poe there's two different modes for<12:31:06.116> combining<12:31:06.660> the<12:31:06.900> following<12:31:07.460> data<12:31:08.460> and 12:31:08.690 --> 12:31:08.700 align:start position:0% for combining the following data and 12:31:08.700 --> 12:31:11.030 align:start position:0% for combining the following data and power<12:31:08.880> of<12:31:09.116> the<12:31:09.300> ethernet<12:31:09.596> cable<12:31:10.020> the<12:31:10.916> two 12:31:11.030 --> 12:31:11.040 align:start position:0% power of the ethernet cable the two 12:31:11.040 --> 12:31:13.310 align:start position:0% power of the ethernet cable the two modes<12:31:11.580> are<12:31:12.116> not<12:31:12.596> very<12:31:12.720> imaginative 12:31:13.310 --> 12:31:13.320 align:start position:0% modes are not very imaginative 12:31:13.320 --> 12:31:16.310 align:start position:0% modes are not very imaginative unfortunately<12:31:13.980> mode<12:31:14.520> a<12:31:14.880> and<12:31:15.240> mode<12:31:15.540> B 12:31:16.310 --> 12:31:16.320 align:start position:0% unfortunately mode a and mode B 12:31:16.320 --> 12:31:18.406 align:start position:0% unfortunately mode a and mode B suppose<12:31:16.800> it<12:31:16.980> could<12:31:17.096> have<12:31:17.160> been<12:31:17.276> one<12:31:17.520> or<12:31:17.700> two<12:31:17.936> or 12:31:18.406 --> 12:31:18.416 align:start position:0% suppose it could have been one or two or 12:31:18.416 --> 12:31:19.906 align:start position:0% suppose it could have been one or two or Jack<12:31:18.720> and<12:31:18.900> Jill 12:31:19.906 --> 12:31:19.916 align:start position:0% Jack and Jill 12:31:19.916 --> 12:31:22.310 align:start position:0% Jack and Jill mode<12:31:20.520> a<12:31:20.880> the<12:31:21.180> electrical<12:31:21.596> power<12:31:21.776> and<12:31:21.960> the<12:31:22.080> data 12:31:22.310 --> 12:31:22.320 align:start position:0% mode a the electrical power and the data 12:31:22.320 --> 12:31:24.170 align:start position:0% mode a the electrical power and the data are<12:31:22.560> combined<12:31:22.916> on<12:31:23.160> the<12:31:23.276> same<12:31:23.460> wires<12:31:23.820> over<12:31:23.936> the 12:31:24.170 --> 12:31:24.180 align:start position:0% are combined on the same wires over the 12:31:24.180 --> 12:31:25.490 align:start position:0% are combined on the same wires over the ethernet<12:31:24.416> cable 12:31:25.490 --> 12:31:25.500 align:start position:0% ethernet cable 12:31:25.500 --> 12:31:28.550 align:start position:0% ethernet cable this<12:31:25.980> is<12:31:26.160> called<12:31:26.460> Phantom<12:31:27.000> powering 12:31:28.550 --> 12:31:28.560 align:start position:0% this is called Phantom powering 12:31:28.560 --> 12:31:30.830 align:start position:0% this is called Phantom powering mode<12:31:28.860> B<12:31:29.160> the<12:31:29.340> electrical<12:31:29.820> power<12:31:30.116> and<12:31:30.416> data<12:31:30.776> are 12:31:30.830 --> 12:31:30.840 align:start position:0% mode B the electrical power and data are 12:31:30.840 --> 12:31:32.690 align:start position:0% mode B the electrical power and data are carried<12:31:31.200> on<12:31:31.320> different<12:31:31.500> wires<12:31:31.980> which<12:31:32.160> is<12:31:32.340> more 12:31:32.690 --> 12:31:32.700 align:start position:0% carried on different wires which is more 12:31:32.700 --> 12:31:34.310 align:start position:0% carried on different wires which is more common 12:31:34.310 --> 12:31:34.320 align:start position:0% common 12:31:34.320 --> 12:31:36.230 align:start position:0% common separate<12:31:34.860> the<12:31:35.040> data<12:31:35.340> and<12:31:35.460> power<12:31:35.700> inside<12:31:36.000> the 12:31:36.230 --> 12:31:36.240 align:start position:0% separate the data and power inside the 12:31:36.240 --> 12:31:38.570 align:start position:0% separate the data and power inside the ethernet<12:31:36.596> cable 12:31:38.570 --> 12:31:38.580 align:start position:0% ethernet cable 12:31:38.580 --> 12:31:41.150 align:start position:0% ethernet cable so<12:31:39.116> in<12:31:39.416> the<12:31:39.540> internet<12:31:39.720> cable<12:31:40.256> if<12:31:40.560> you've<12:31:40.980> got<12:31:41.040> a 12:31:41.150 --> 12:31:41.160 align:start position:0% so in the internet cable if you've got a 12:31:41.160 --> 12:31:42.710 align:start position:0% so in the internet cable if you've got a pair<12:31:41.400> of<12:31:41.520> wires<12:31:41.820> carried<12:31:42.240> only<12:31:42.360> the<12:31:42.540> power 12:31:42.710 --> 12:31:42.720 align:start position:0% pair of wires carried only the power 12:31:42.720 --> 12:31:44.810 align:start position:0% pair of wires carried only the power then<12:31:43.020> the<12:31:43.200> other<12:31:43.320> pair<12:31:43.740> of<12:31:43.860> wires<12:31:44.220> would<12:31:44.400> carry 12:31:44.810 --> 12:31:44.820 align:start position:0% then the other pair of wires would carry 12:31:44.820 --> 12:31:47.746 align:start position:0% then the other pair of wires would carry only<12:31:45.300> the<12:31:45.660> data 12:31:47.746 --> 12:31:47.756 align:start position:0% only the data 12:31:47.756 --> 12:31:49.810 align:start position:0% only the data uh<12:31:48.416> First<12:31:48.660> International<12:31:48.900> standard<12:31:49.500> was 12:31:49.810 --> 12:31:49.820 align:start position:0% uh First International standard was 12:31:49.820 --> 12:31:51.950 align:start position:0% uh First International standard was 802.3<12:31:50.820> AF 12:31:51.950 --> 12:31:51.960 align:start position:0% 802.3 AF 12:31:51.960 --> 12:31:55.850 align:start position:0% 802.3 AF ratified<12:31:52.740> a<12:31:53.040> long<12:31:53.220> time<12:31:53.400> ago<12:31:53.640> June<12:31:54.180> 2003<12:31:54.900> and 12:31:55.850 --> 12:31:55.860 align:start position:0% ratified a long time ago June 2003 and 12:31:55.860 --> 12:31:58.670 align:start position:0% ratified a long time ago June 2003 and it<12:31:55.980> defines<12:31:56.936> um<12:31:56.936> a<12:31:57.720> power<12:31:57.840> supply<12:31:58.020> of<12:31:58.320> up<12:31:58.500> to 12:31:58.670 --> 12:31:58.680 align:start position:0% it defines um a power supply of up to 12:31:58.680 --> 12:32:03.470 align:start position:0% it defines um a power supply of up to 1.54<12:31:59.640> watts<12:32:00.116> of<12:32:00.480> DC 12:32:03.470 --> 12:32:03.480 align:start position:0% 12:32:03.480 --> 12:32:05.810 align:start position:0% uses<12:32:04.080> 48<12:32:04.500> volts 12:32:05.810 --> 12:32:05.820 align:start position:0% uses 48 volts 12:32:05.820 --> 12:32:07.790 align:start position:0% uses 48 volts as<12:32:06.180> growing<12:32:06.596> demand<12:32:06.840> for<12:32:07.020> more<12:32:07.200> power<12:32:07.436> over 12:32:07.790 --> 12:32:07.800 align:start position:0% as growing demand for more power over 12:32:07.800 --> 12:32:09.406 align:start position:0% as growing demand for more power over Ethernet<12:32:08.096> cable<12:32:08.460> so<12:32:08.756> the<12:32:08.936> standard<12:32:09.240> was 12:32:09.406 --> 12:32:09.416 align:start position:0% Ethernet cable so the standard was 12:32:09.416 --> 12:32:14.650 align:start position:0% Ethernet cable so the standard was updated<12:32:10.040> and<12:32:11.040> 802.3 12:32:14.650 --> 12:32:14.660 align:start position:0% 12:32:14.660 --> 12:32:16.790 align:start position:0% Poe<12:32:15.660> Plus 12:32:16.790 --> 12:32:16.800 align:start position:0% Poe Plus 12:32:16.800 --> 12:32:20.030 align:start position:0% Poe Plus this<12:32:17.276> was<12:32:17.400> adopted<12:32:17.880> back<12:32:18.116> in<12:32:18.360> 2009 12:32:20.030 --> 12:32:20.040 align:start position:0% this was adopted back in 2009 12:32:20.040 --> 12:32:21.830 align:start position:0% this was adopted back in 2009 and<12:32:20.520> it<12:32:20.640> defines<12:32:21.000> the<12:32:21.060> following<12:32:21.416> a<12:32:21.660> power 12:32:21.830 --> 12:32:21.840 align:start position:0% and it defines the following a power 12:32:21.840 --> 12:32:24.710 align:start position:0% and it defines the following a power supply<12:32:22.020> of<12:32:22.256> up<12:32:22.436> to<12:32:22.640> 34.2<12:32:23.640> watts<12:32:24.000> of<12:32:24.116> DC<12:32:24.416> power 12:32:24.710 --> 12:32:24.720 align:start position:0% supply of up to 34.2 watts of DC power 12:32:24.720 --> 12:32:27.530 align:start position:0% supply of up to 34.2 watts of DC power using<12:32:25.560> 48<12:32:26.096> volts 12:32:27.530 --> 12:32:27.540 align:start position:0% using 48 volts 12:32:27.540 --> 12:32:33.170 align:start position:0% using 48 volts both<12:32:28.020> the<12:32:28.380> I<12:32:29.220> um<12:32:29.596> IEEE<12:32:30.860> 802.3<12:32:31.860> AF<12:32:32.340> and<12:32:32.580> 80<12:32:32.756> are 12:32:33.170 --> 12:32:33.180 align:start position:0% both the I um IEEE 802.3 AF and 80 are 12:32:33.180 --> 12:32:35.150 align:start position:0% both the I um IEEE 802.3 AF and 80 are now<12:32:33.300> included<12:32:33.720> in<12:32:34.020> the<12:32:34.200> ethernet<12:32:34.616> standards 12:32:35.150 --> 12:32:35.160 align:start position:0% now included in the ethernet standards 12:32:35.160 --> 12:32:37.970 align:start position:0% now included in the ethernet standards they've<12:32:35.460> all<12:32:35.580> been<12:32:35.640> combined<12:32:36.240> together 12:32:37.970 --> 12:32:37.980 align:start position:0% they've all been combined together 12:32:37.980 --> 12:32:40.310 align:start position:0% they've all been combined together as<12:32:38.460> we<12:32:38.640> know<12:32:38.820> from<12:32:39.240> earlier<12:32:39.776> presentations 12:32:40.310 --> 12:32:40.320 align:start position:0% as we know from earlier presentations 12:32:40.320 --> 12:32:42.970 align:start position:0% as we know from earlier presentations the<12:32:40.916> ethernet<12:32:41.276> cable<12:32:41.460> has<12:32:41.880> four 12:32:42.970 --> 12:32:42.980 align:start position:0% the ethernet cable has four 12:32:42.980 --> 12:32:45.350 align:start position:0% the ethernet cable has four pairs<12:32:43.980> of<12:32:44.096> Twisted<12:32:44.460> wire 12:32:45.350 --> 12:32:45.360 align:start position:0% pairs of Twisted wire 12:32:45.360 --> 12:32:49.070 align:start position:0% pairs of Twisted wire this<12:32:45.840> is<12:32:46.020> cart<12:32:46.200> 5e<12:32:46.800> and<12:32:47.040> Cat6 12:32:49.070 --> 12:32:49.080 align:start position:0% this is cart 5e and Cat6 12:32:49.080 --> 12:32:52.310 align:start position:0% this is cart 5e and Cat6 uh<12:32:49.980> for<12:32:50.580> and<12:32:51.300> we<12:32:51.596> already<12:32:51.720> covered<12:32:52.080> earlier 12:32:52.310 --> 12:32:52.320 align:start position:0% uh for and we already covered earlier 12:32:52.320 --> 12:32:55.390 align:start position:0% uh for and we already covered earlier that<12:32:52.500> 10<12:32:52.680> base<12:32:52.916> T<12:32:53.160> and<12:32:53.460> about<12:32:54.180> um<12:32:54.180> 100<12:32:54.596> base<12:32:54.960> T 12:32:55.390 --> 12:32:55.400 align:start position:0% that 10 base T and about um 100 base T 12:32:55.400 --> 12:32:58.906 align:start position:0% that 10 base T and about um 100 base T ethernet<12:32:56.400> only<12:32:56.820> use<12:32:57.180> uh<12:32:58.020> two<12:32:58.200> pairs<12:32:58.560> of<12:32:58.800> wire 12:32:58.906 --> 12:32:58.916 align:start position:0% ethernet only use uh two pairs of wire 12:32:58.916 --> 12:33:01.550 align:start position:0% ethernet only use uh two pairs of wire to<12:32:59.160> send<12:32:59.400> the<12:32:59.580> data<12:32:59.936> so<12:33:00.360> this<12:33:00.540> leaves<12:33:00.900> us<12:33:01.080> some 12:33:01.550 --> 12:33:01.560 align:start position:0% to send the data so this leaves us some 12:33:01.560 --> 12:33:04.730 align:start position:0% to send the data so this leaves us some spare<12:33:01.980> wires<12:33:02.460> two<12:33:02.700> pairs<12:33:03.000> of<12:33:03.116> spare<12:33:03.416> wires 12:33:04.730 --> 12:33:04.740 align:start position:0% spare wires two pairs of spare wires 12:33:04.740 --> 12:33:07.010 align:start position:0% spare wires two pairs of spare wires so<12:33:05.220> electrical<12:33:05.820> current<12:33:06.000> flows<12:33:06.480> in<12:33:06.720> the<12:33:06.900> loop 12:33:07.010 --> 12:33:07.020 align:start position:0% so electrical current flows in the loop 12:33:07.020 --> 12:33:08.510 align:start position:0% so electrical current flows in the loop powering<12:33:07.436> the<12:33:07.560> electrical<12:33:07.860> components<12:33:08.340> such 12:33:08.510 --> 12:33:08.520 align:start position:0% powering the electrical components such 12:33:08.520 --> 12:33:11.086 align:start position:0% powering the electrical components such as<12:33:08.700> bulbs<12:33:09.240> and<12:33:09.360> fans<12:33:09.660> the<12:33:10.436> loop<12:33:10.740> is<12:33:10.916> an 12:33:11.086 --> 12:33:11.096 align:start position:0% as bulbs and fans the loop is an 12:33:11.096 --> 12:33:14.150 align:start position:0% as bulbs and fans the loop is an electrical<12:33:11.640> circuit 12:33:14.150 --> 12:33:14.160 align:start position:0% 12:33:14.160 --> 12:33:15.890 align:start position:0% and<12:33:14.580> since<12:33:14.820> the<12:33:15.000> electrical<12:33:15.360> current<12:33:15.480> flows 12:33:15.890 --> 12:33:15.900 align:start position:0% and since the electrical current flows 12:33:15.900 --> 12:33:17.450 align:start position:0% and since the electrical current flows in<12:33:16.020> the<12:33:16.140> loop<12:33:16.320> we<12:33:16.500> need<12:33:16.560> two<12:33:16.740> conductors<12:33:17.220> to 12:33:17.450 --> 12:33:17.460 align:start position:0% in the loop we need two conductors to 12:33:17.460 --> 12:33:21.530 align:start position:0% in the loop we need two conductors to deliver<12:33:17.700> power<12:33:18.060> over<12:33:18.300> an<12:33:18.596> ethernet<12:33:18.840> cable 12:33:21.530 --> 12:33:21.540 align:start position:0% 12:33:21.540 --> 12:33:24.470 align:start position:0% uh<12:33:22.140> typically<12:33:22.500> we<12:33:22.740> use<12:33:22.860> 48<12:33:23.400> volts<12:33:23.880> that<12:33:24.116> says 12:33:24.470 --> 12:33:24.480 align:start position:0% uh typically we use 48 volts that says 12:33:24.480 --> 12:33:26.086 align:start position:0% uh typically we use 48 volts that says sufficient<12:33:24.840> power<12:33:25.080> to<12:33:25.380> transfer<12:33:25.740> over<12:33:25.916> the 12:33:26.086 --> 12:33:26.096 align:start position:0% sufficient power to transfer over the 12:33:26.096 --> 12:33:28.246 align:start position:0% sufficient power to transfer over the cable<12:33:26.340> and<12:33:27.060> it's<12:33:27.240> safe<12:33:27.416> for<12:33:27.660> users<12:33:27.960> so<12:33:28.140> it's 12:33:28.246 --> 12:33:28.256 align:start position:0% cable and it's safe for users so it's 12:33:28.256 --> 12:33:31.730 align:start position:0% cable and it's safe for users so it's not<12:33:28.436> going<12:33:28.616> to<12:33:28.800> injure<12:33:29.640> anyone 12:33:31.730 --> 12:33:31.740 align:start position:0% not going to injure anyone 12:33:31.740 --> 12:33:36.230 align:start position:0% not going to injure anyone now<12:33:32.580> if<12:33:32.936> you<12:33:33.240> plug<12:33:33.960> a<12:33:34.080> Poe<12:33:34.616> device<12:33:34.860> into<12:33:35.580> one 12:33:36.230 --> 12:33:36.240 align:start position:0% now if you plug a Poe device into one 12:33:36.240 --> 12:33:38.086 align:start position:0% now if you plug a Poe device into one that<12:33:36.416> isn't<12:33:36.660> designed<12:33:37.020> for<12:33:37.200> use<12:33:37.380> with<12:33:37.560> Poe 12:33:38.086 --> 12:33:38.096 align:start position:0% that isn't designed for use with Poe 12:33:38.096 --> 12:33:41.330 align:start position:0% that isn't designed for use with Poe then<12:33:39.060> you<12:33:39.300> could<12:33:39.480> cause<12:33:39.960> damage<12:33:40.436> and<12:33:40.680> fry<12:33:41.160> it 12:33:41.330 --> 12:33:41.340 align:start position:0% then you could cause damage and fry it 12:33:41.340 --> 12:33:42.106 align:start position:0% then you could cause damage and fry it and 12:33:42.106 --> 12:33:42.116 align:start position:0% and 12:33:42.116 --> 12:33:44.086 align:start position:0% and in<12:33:42.480> other<12:33:42.660> words 12:33:44.086 --> 12:33:44.096 align:start position:0% in other words 12:33:44.096 --> 12:33:46.490 align:start position:0% in other words and<12:33:44.520> the<12:33:44.700> PSE<12:33:45.000> sends<12:33:45.480> a<12:33:45.540> lower<12:33:45.660> voltage<12:33:46.140> to<12:33:46.320> a 12:33:46.490 --> 12:33:46.500 align:start position:0% and the PSE sends a lower voltage to a 12:33:46.500 --> 12:33:48.350 align:start position:0% and the PSE sends a lower voltage to a device<12:33:46.680> to<12:33:47.096> detect<12:33:47.400> the<12:33:47.580> characteristic 12:33:48.350 --> 12:33:48.360 align:start position:0% device to detect the characteristic 12:33:48.360 --> 12:33:51.470 align:start position:0% device to detect the characteristic signature<12:33:49.080> of<12:33:49.200> a<12:33:49.380> compatible<12:33:49.740> PD 12:33:51.470 --> 12:33:51.480 align:start position:0% signature of a compatible PD 12:33:51.480 --> 12:33:53.630 align:start position:0% signature of a compatible PD if<12:33:51.960> he<12:33:52.140> takes<12:33:52.436> a<12:33:52.616> signature<12:33:52.980> then<12:33:53.160> it<12:33:53.340> knows 12:33:53.630 --> 12:33:53.640 align:start position:0% if he takes a signature then it knows 12:33:53.640 --> 12:33:55.970 align:start position:0% if he takes a signature then it knows the<12:33:53.756> 48<12:33:54.060> volts<12:33:54.416> can<12:33:54.540> be<12:33:54.660> applied 12:33:55.970 --> 12:33:55.980 align:start position:0% the 48 volts can be applied 12:33:55.980 --> 12:33:58.246 align:start position:0% the 48 volts can be applied the<12:33:56.400> PD<12:33:56.640> lets<12:33:57.000> the<12:33:57.060> PSE<12:33:57.360> know<12:33:57.720> how<12:33:57.900> much<12:33:58.020> power 12:33:58.246 --> 12:33:58.256 align:start position:0% the PD lets the PSE know how much power 12:33:58.256 --> 12:34:00.890 align:start position:0% the PD lets the PSE know how much power it<12:33:58.436> requires<12:33:58.800> to<12:33:58.916> operate<12:33:59.340> so<12:34:00.240> this<12:34:00.596> is<12:34:00.720> to 12:34:00.890 --> 12:34:00.900 align:start position:0% it requires to operate so this is to 12:34:00.900 --> 12:34:03.106 align:start position:0% it requires to operate so this is to save<12:34:01.080> a<12:34:01.380> surge<12:34:01.616> basically<12:34:02.040> on<12:34:02.340> the 12:34:03.106 --> 12:34:03.116 align:start position:0% save a surge basically on the 12:34:03.116 --> 12:34:06.106 align:start position:0% save a surge basically on the um line<12:34:03.360> now<12:34:03.540> too<12:34:03.840> much<12:34:03.960> power<12:34:04.140> has<12:34:04.320> been<12:34:04.500> sent 12:34:06.106 --> 12:34:06.116 align:start position:0% um line now too much power has been sent 12:34:06.116 --> 12:34:08.450 align:start position:0% um line now too much power has been sent the<12:34:06.596> requirement<12:34:06.960> of<12:34:07.140> power<12:34:07.380> is<12:34:07.980> classified 12:34:08.450 --> 12:34:08.460 align:start position:0% the requirement of power is classified 12:34:08.460 --> 12:34:11.150 align:start position:0% the requirement of power is classified in<12:34:08.936> the<12:34:09.116> power<12:34:09.300> classes<12:34:09.776> shown<12:34:10.020> below 12:34:11.150 --> 12:34:11.160 align:start position:0% in the power classes shown below 12:34:11.160 --> 12:34:12.830 align:start position:0% in the power classes shown below probably<12:34:11.520> worth<12:34:11.756> making<12:34:12.116> a<12:34:12.360> note<12:34:12.540> of<12:34:12.720> these 12:34:12.830 --> 12:34:12.840 align:start position:0% probably worth making a note of these 12:34:12.840 --> 12:34:15.106 align:start position:0% probably worth making a note of these write<12:34:13.080> them<12:34:13.320> down<12:34:13.616> just<12:34:14.220> in<12:34:14.400> case<12:34:14.580> it<12:34:14.756> comes<12:34:15.000> up 12:34:15.106 --> 12:34:15.116 align:start position:0% write them down just in case it comes up 12:34:15.116 --> 12:34:20.746 align:start position:0% write them down just in case it comes up in<12:34:15.300> the<12:34:15.416> exam 12:34:20.746 --> 12:34:20.756 align:start position:0% 12:34:20.756 --> 12:34:22.490 align:start position:0% difference<12:34:21.180> between<12:34:21.416> the<12:34:21.776> following<12:34:22.080> power 12:34:22.490 --> 12:34:22.500 align:start position:0% difference between the following power 12:34:22.500 --> 12:34:25.730 align:start position:0% difference between the following power supplied<12:34:22.980> by<12:34:23.276> the<12:34:23.520> PSE<12:34:24.060> power<12:34:25.020> received<12:34:25.560> by 12:34:25.730 --> 12:34:25.740 align:start position:0% supplied by the PSE power received by 12:34:25.740 --> 12:34:28.906 align:start position:0% supplied by the PSE power received by the<12:34:25.860> PD<12:34:26.220> account<12:34:26.640> for<12:34:27.300> lostpower 12:34:28.906 --> 12:34:28.916 align:start position:0% the PD account for lostpower 12:34:28.916 --> 12:34:31.010 align:start position:0% the PD account for lostpower now<12:34:29.460> there<12:34:29.640> is<12:34:29.756> a<12:34:29.936> maximum<12:34:30.300> distance<12:34:30.540> which 12:34:31.010 --> 12:34:31.020 align:start position:0% now there is a maximum distance which 12:34:31.020 --> 12:34:33.050 align:start position:0% now there is a maximum distance which matches<12:34:31.436> in<12:34:31.616> with<12:34:31.800> the<12:34:31.980> ethernet<12:34:32.460> standards 12:34:33.050 --> 12:34:33.060 align:start position:0% matches in with the ethernet standards 12:34:33.060 --> 12:34:35.450 align:start position:0% matches in with the ethernet standards and<12:34:33.480> maximum<12:34:34.020> support<12:34:34.380> distance<12:34:34.800> is<12:34:35.160> 100 12:34:35.450 --> 12:34:35.460 align:start position:0% and maximum support distance is 100 12:34:35.460 --> 12:34:38.746 align:start position:0% and maximum support distance is 100 meters 12:34:38.746 --> 12:34:38.756 align:start position:0% 12:34:38.756 --> 12:34:40.730 align:start position:0% there's<12:34:39.360> a<12:34:39.540> new<12:34:39.660> standard<12:34:40.020> which<12:34:40.256> increases 12:34:40.730 --> 12:34:40.740 align:start position:0% there's a new standard which increases 12:34:40.740 --> 12:34:44.210 align:start position:0% there's a new standard which increases the<12:34:40.980> power<12:34:41.096> available<12:34:41.596> and<12:34:42.596> uses<12:34:43.380> a<12:34:43.680> wide 12:34:44.210 --> 12:34:44.220 align:start position:0% the power available and uses a wide 12:34:44.220 --> 12:34:46.490 align:start position:0% the power available and uses a wide range<12:34:44.460> of<12:34:44.640> the<12:34:44.756> following<12:34:45.116> devices<12:34:45.500> Thin 12:34:46.490 --> 12:34:46.500 align:start position:0% range of the following devices Thin 12:34:46.500 --> 12:34:49.426 align:start position:0% range of the following devices Thin Client<12:34:46.800> Terminals<12:34:47.520> and<12:34:48.240> pointer<12:34:48.840> sales<12:34:49.080> stuff 12:34:49.426 --> 12:34:49.436 align:start position:0% Client Terminals and pointer sales stuff 12:34:49.436 --> 12:34:51.470 align:start position:0% Client Terminals and pointer sales stuff in<12:34:50.340> shops 12:34:51.470 --> 12:34:51.480 align:start position:0% in shops 12:34:51.480 --> 12:34:54.586 align:start position:0% in shops video<12:34:51.960> conferencing 12:34:54.586 --> 12:34:54.596 align:start position:0% video conferencing 12:34:54.596 --> 12:34:56.030 align:start position:0% video conferencing so<12:34:54.960> I<12:34:55.020> think<12:34:55.200> that's<12:34:55.320> all<12:34:55.500> we<12:34:55.616> need<12:34:55.800> to<12:34:55.916> know 12:34:56.030 --> 12:34:56.040 align:start position:0% so I think that's all we need to know 12:34:56.040 --> 12:34:58.670 align:start position:0% so I think that's all we need to know we've<12:34:56.400> covered<12:34:56.700> Poe<12:34:57.360> the<12:34:57.660> benefits<12:34:58.380> the 12:34:58.670 --> 12:34:58.680 align:start position:0% we've covered Poe the benefits the 12:34:58.680 --> 12:35:03.766 align:start position:0% we've covered Poe the benefits the components<12:34:59.400> the<12:34:59.756> PSE<12:35:00.380> end<12:35:01.380> span<12:35:01.936> mid-span<12:35:02.936> the 12:35:03.766 --> 12:35:03.776 align:start position:0% components the PSE end span mid-span the 12:35:03.776 --> 12:35:07.790 align:start position:0% components the PSE end span mid-span the power<12:35:03.900> device<12:35:04.380> the<12:35:05.160> the<12:35:05.400> modes<12:35:05.700> for<12:35:05.936> Poe 12:35:07.790 --> 12:35:07.800 align:start position:0% power device the the modes for Poe 12:35:07.800 --> 12:35:10.850 align:start position:0% power device the the modes for Poe which<12:35:08.520> is<12:35:08.700> a<12:35:08.936> and<12:35:09.116> b<12:35:09.300> uh<12:35:09.840> the<12:35:10.020> standards<12:35:10.560> and 12:35:10.850 --> 12:35:10.860 align:start position:0% which is a and b uh the standards and 12:35:10.860 --> 12:35:13.130 align:start position:0% which is a and b uh the standards and how<12:35:11.040> does<12:35:11.220> it<12:35:11.340> work<12:35:11.580> so<12:35:12.240> that's<12:35:12.480> all<12:35:12.776> for<12:35:12.960> now 12:35:13.130 --> 12:35:13.140 align:start position:0% how does it work so that's all for now 12:35:13.140 --> 12:35:19.090 align:start position:0% how does it work so that's all for now thanks<12:35:13.500> for<12:35:13.680> watching 12:35:19.090 --> 12:35:19.100 align:start position:0% 12:35:19.100 --> 12:35:41.210 align:start position:0% [Music] 12:35:41.210 --> 12:35:41.220 align:start position:0% 12:35:41.220 --> 12:35:45.710 align:start position:0% local<12:35:41.936> area<12:35:42.240> Networks<12:35:43.436> routing 12:35:45.710 --> 12:35:45.720 align:start position:0% local area Networks routing 12:35:45.720 --> 12:35:48.170 align:start position:0% local area Networks routing so<12:35:46.256> in<12:35:46.500> the<12:35:46.560> previous<12:35:46.680> module<12:35:47.276> we<12:35:47.700> discussed 12:35:48.170 --> 12:35:48.180 align:start position:0% so in the previous module we discussed 12:35:48.180 --> 12:35:50.266 align:start position:0% so in the previous module we discussed switches<12:35:48.960> and<12:35:49.436> as<12:35:49.560> you<12:35:49.680> remember<12:35:49.740> they're 12:35:50.266 --> 12:35:50.276 align:start position:0% switches and as you remember they're 12:35:50.276 --> 12:35:52.906 align:start position:0% switches and as you remember they're very<12:35:50.580> important<12:35:51.116> for<12:35:51.360> the<12:35:51.540> functionality<12:35:52.140> of 12:35:52.906 --> 12:35:52.916 align:start position:0% very important for the functionality of 12:35:52.916 --> 12:35:55.670 align:start position:0% very important for the functionality of a<12:35:53.220> local<12:35:53.520> area<12:35:53.820> network 12:35:55.670 --> 12:35:55.680 align:start position:0% a local area network 12:35:55.680 --> 12:35:58.070 align:start position:0% a local area network now<12:35:56.220> when<12:35:56.640> we<12:35:56.820> talk<12:35:57.060> about<12:35:57.240> connecting 12:35:58.070 --> 12:35:58.080 align:start position:0% now when we talk about connecting 12:35:58.080 --> 12:36:00.830 align:start position:0% now when we talk about connecting several<12:35:58.740> different<12:35:59.096> local<12:35:59.880> area<12:36:00.180> networks 12:36:00.830 --> 12:36:00.840 align:start position:0% several different local area networks 12:36:00.840 --> 12:36:02.630 align:start position:0% several different local area networks together<12:36:01.080> through 12:36:02.630 --> 12:36:02.640 align:start position:0% together through 12:36:02.640 --> 12:36:06.050 align:start position:0% together through the<12:36:03.116> internet<12:36:03.240> we<12:36:04.080> have<12:36:04.256> to<12:36:04.436> deal<12:36:04.616> with<12:36:05.340> how<12:36:05.700> a 12:36:06.050 --> 12:36:06.060 align:start position:0% the internet we have to deal with how a 12:36:06.060 --> 12:36:08.150 align:start position:0% the internet we have to deal with how a switch<12:36:06.240> which<12:36:06.900> again 12:36:08.150 --> 12:36:08.160 align:start position:0% switch which again 12:36:08.160 --> 12:36:11.030 align:start position:0% switch which again is<12:36:08.756> based<12:36:09.116> on<12:36:09.240> Mac<12:36:09.720> addresses<12:36:10.320> the<12:36:10.860> physical 12:36:11.030 --> 12:36:11.040 align:start position:0% is based on Mac addresses the physical 12:36:11.040 --> 12:36:12.790 align:start position:0% is based on Mac addresses the physical address<12:36:11.400> on<12:36:11.820> a<12:36:11.936> computer 12:36:12.790 --> 12:36:12.800 align:start position:0% address on a computer 12:36:12.800 --> 12:36:16.330 align:start position:0% address on a computer can<12:36:13.800> find<12:36:14.400> the<12:36:14.640> MAC<12:36:14.880> address<12:36:15.116> of<12:36:15.840> a<12:36:16.020> computer 12:36:16.330 --> 12:36:16.340 align:start position:0% can find the MAC address of a computer 12:36:16.340 --> 12:36:18.290 align:start position:0% can find the MAC address of a computer halfway<12:36:17.340> across 12:36:18.290 --> 12:36:18.300 align:start position:0% halfway across 12:36:18.300 --> 12:36:20.086 align:start position:0% halfway across the<12:36:18.776> world 12:36:20.086 --> 12:36:20.096 align:start position:0% the world 12:36:20.096 --> 12:36:22.370 align:start position:0% the world and<12:36:20.460> the<12:36:20.580> way<12:36:20.640> it<12:36:20.820> does<12:36:20.936> this<12:36:21.180> is<12:36:21.540> by<12:36:21.776> assigning 12:36:22.370 --> 12:36:22.380 align:start position:0% and the way it does this is by assigning 12:36:22.380 --> 12:36:26.030 align:start position:0% and the way it does this is by assigning each<12:36:22.616> Mac<12:36:22.860> address<12:36:23.480> uh<12:36:24.480> an<12:36:24.660> IP<12:36:25.020> address 12:36:26.030 --> 12:36:26.040 align:start position:0% each Mac address uh an IP address 12:36:26.040 --> 12:36:27.406 align:start position:0% each Mac address uh an IP address now<12:36:26.400> when<12:36:26.520> we<12:36:26.640> start<12:36:26.756> dealing<12:36:27.000> with<12:36:27.116> IP 12:36:27.406 --> 12:36:27.416 align:start position:0% now when we start dealing with IP 12:36:27.416 --> 12:36:28.970 align:start position:0% now when we start dealing with IP address<12:36:27.596> we<12:36:27.960> deal<12:36:28.080> with<12:36:28.256> a<12:36:28.500> completely 12:36:28.970 --> 12:36:28.980 align:start position:0% address we deal with a completely 12:36:28.980 --> 12:36:31.606 align:start position:0% address we deal with a completely different<12:36:29.520> type<12:36:30.180> of<12:36:30.300> device<12:36:30.540> one<12:36:31.256> which<12:36:31.436> is 12:36:31.606 --> 12:36:31.616 align:start position:0% different type of device one which is 12:36:31.616 --> 12:36:33.766 align:start position:0% different type of device one which is called<12:36:31.860> routing<12:36:32.580> and<12:36:33.060> the<12:36:33.300> process<12:36:33.540> of 12:36:33.766 --> 12:36:33.776 align:start position:0% called routing and the process of 12:36:33.776 --> 12:36:35.690 align:start position:0% called routing and the process of routing<12:36:34.320> is<12:36:34.740> what<12:36:34.916> really<12:36:35.096> allows<12:36:35.520> the 12:36:35.690 --> 12:36:35.700 align:start position:0% routing is what really allows the 12:36:35.700 --> 12:36:38.810 align:start position:0% routing is what really allows the internet<12:36:35.880> to<12:36:36.720> work<12:36:36.900> and<12:36:37.616> so<12:36:37.800> in<12:36:38.220> this<12:36:38.400> module 12:36:38.810 --> 12:36:38.820 align:start position:0% internet to work and so in this module 12:36:38.820 --> 12:36:40.426 align:start position:0% internet to work and so in this module we're<12:36:39.000> going<12:36:39.180> to<12:36:39.300> talk<12:36:39.480> more<12:36:39.720> about<12:36:39.960> the 12:36:40.426 --> 12:36:40.436 align:start position:0% we're going to talk more about the 12:36:40.436 --> 12:36:42.530 align:start position:0% we're going to talk more about the devices<12:36:40.740> that<12:36:41.520> allow<12:36:41.756> routing<12:36:42.180> to<12:36:42.360> work 12:36:42.530 --> 12:36:42.540 align:start position:0% devices that allow routing to work 12:36:42.540 --> 12:36:44.570 align:start position:0% devices that allow routing to work called<12:36:43.140> routers 12:36:44.570 --> 12:36:44.580 align:start position:0% called routers 12:36:44.580 --> 12:36:46.790 align:start position:0% called routers so<12:36:45.240> first<12:36:45.776> of<12:36:45.960> all<12:36:46.020> we're<12:36:46.256> going<12:36:46.380> to<12:36:46.560> Define 12:36:46.790 --> 12:36:46.800 align:start position:0% so first of all we're going to Define 12:36:46.800 --> 12:36:49.970 align:start position:0% so first of all we're going to Define what<12:36:47.756> a<12:36:48.000> router<12:36:48.416> is<12:36:48.720> and<12:36:49.436> then<12:36:49.560> we're<12:36:49.740> going<12:36:49.860> to 12:36:49.970 --> 12:36:49.980 align:start position:0% what a router is and then we're going to 12:36:49.980 --> 12:36:52.426 align:start position:0% what a router is and then we're going to talk<12:36:50.160> about<12:36:50.400> how<12:36:50.820> it<12:36:50.936> functions<12:36:51.480> which<12:36:52.256> is 12:36:52.426 --> 12:36:52.436 align:start position:0% talk about how it functions which is 12:36:52.436 --> 12:36:56.450 align:start position:0% talk about how it functions which is also<12:36:52.800> called<12:36:53.096> routing 12:36:56.450 --> 12:36:56.460 align:start position:0% 12:36:56.460 --> 12:36:58.970 align:start position:0% then<12:36:57.060> we're<12:36:57.660> going<12:36:57.900> to<12:36:58.140> identify<12:36:58.616> something 12:36:58.970 --> 12:36:58.980 align:start position:0% then we're going to identify something 12:36:58.980 --> 12:37:02.030 align:start position:0% then we're going to identify something called<12:36:59.400> static<12:37:00.300> routing<12:37:00.900> just<12:37:01.560> like<12:37:01.740> we've 12:37:02.030 --> 12:37:02.040 align:start position:0% called static routing just like we've 12:37:02.040 --> 12:37:05.510 align:start position:0% called static routing just like we've talked<12:37:02.340> about<12:37:02.460> dynamic 12:37:05.510 --> 12:37:05.520 align:start position:0% 12:37:05.520 --> 12:37:10.130 align:start position:0% versus<12:37:06.256> static<12:37:07.256> IP<12:37:07.680> addresses 12:37:10.130 --> 12:37:10.140 align:start position:0% versus static IP addresses 12:37:10.140 --> 12:37:11.810 align:start position:0% versus static IP addresses we<12:37:10.800> also<12:37:10.980> have 12:37:11.810 --> 12:37:11.820 align:start position:0% we also have 12:37:11.820 --> 12:37:15.106 align:start position:0% we also have Dynamic<12:37:12.540> and<12:37:12.776> static<12:37:13.200> routing<12:37:13.700> obviously<12:37:14.700> one 12:37:15.106 --> 12:37:15.116 align:start position:0% Dynamic and static routing obviously one 12:37:15.116 --> 12:37:17.926 align:start position:0% Dynamic and static routing obviously one is<12:37:15.480> more<12:37:15.980> resilient<12:37:16.980> than<12:37:17.220> the<12:37:17.400> other<12:37:17.520> but 12:37:17.926 --> 12:37:17.936 align:start position:0% is more resilient than the other but 12:37:17.936 --> 12:37:19.490 align:start position:0% is more resilient than the other but there<12:37:18.180> are<12:37:18.300> certain<12:37:18.540> instances<12:37:18.900> in<12:37:19.140> which<12:37:19.320> we 12:37:19.490 --> 12:37:19.500 align:start position:0% there are certain instances in which we 12:37:19.500 --> 12:37:21.890 align:start position:0% there are certain instances in which we want<12:37:19.680> to<12:37:19.860> always<12:37:20.160> go<12:37:20.460> to<12:37:20.640> the<12:37:20.936> same<12:37:21.116> location 12:37:21.890 --> 12:37:21.900 align:start position:0% want to always go to the same location 12:37:21.900 --> 12:37:23.390 align:start position:0% want to always go to the same location and<12:37:22.560> that's<12:37:22.680> why<12:37:22.860> we're<12:37:23.040> going<12:37:23.220> to<12:37:23.276> have 12:37:23.390 --> 12:37:23.400 align:start position:0% and that's why we're going to have 12:37:23.400 --> 12:37:25.370 align:start position:0% and that's why we're going to have static<12:37:23.880> routing<12:37:24.240> then<12:37:24.840> we<12:37:25.020> need<12:37:25.140> to<12:37:25.256> cover 12:37:25.370 --> 12:37:25.380 align:start position:0% static routing then we need to cover 12:37:25.380 --> 12:37:27.950 align:start position:0% static routing then we need to cover some<12:37:25.800> terms<12:37:26.340> that<12:37:27.300> you<12:37:27.416> might<12:37:27.540> see<12:37:27.776> when 12:37:27.950 --> 12:37:27.960 align:start position:0% some terms that you might see when 12:37:27.960 --> 12:37:29.746 align:start position:0% some terms that you might see when you're<12:37:28.080> dealing<12:37:28.256> with<12:37:28.380> routing<12:37:28.800> these<12:37:29.460> terms 12:37:29.746 --> 12:37:29.756 align:start position:0% you're dealing with routing these terms 12:37:29.756 --> 12:37:31.990 align:start position:0% you're dealing with routing these terms are<12:37:30.116> hop<12:37:30.540> counts 12:37:31.990 --> 12:37:32.000 align:start position:0% are hop counts 12:37:32.000 --> 12:37:33.586 align:start position:0% are hop counts costs 12:37:33.586 --> 12:37:33.596 align:start position:0% costs 12:37:33.596 --> 12:37:35.150 align:start position:0% costs latency 12:37:35.150 --> 12:37:35.160 align:start position:0% latency 12:37:35.160 --> 12:37:37.426 align:start position:0% latency and<12:37:35.936> convergence<12:37:36.596> so<12:37:37.020> we're<12:37:37.140> going<12:37:37.256> to<12:37:37.256> cover 12:37:37.426 --> 12:37:37.436 align:start position:0% and convergence so we're going to cover 12:37:37.436 --> 12:37:39.290 align:start position:0% and convergence so we're going to cover all<12:37:37.680> those<12:37:37.860> terms<12:37:38.220> so<12:37:38.400> you<12:37:38.580> have<12:37:38.756> a<12:37:38.936> good<12:37:39.000> idea 12:37:39.290 --> 12:37:39.300 align:start position:0% all those terms so you have a good idea 12:37:39.300 --> 12:37:40.790 align:start position:0% all those terms so you have a good idea in<12:37:39.480> case<12:37:39.660> you<12:37:39.840> see<12:37:39.960> them<12:37:40.140> on<12:37:40.256> the<12:37:40.380> exam<12:37:40.616> what 12:37:40.790 --> 12:37:40.800 align:start position:0% in case you see them on the exam what 12:37:40.800 --> 12:37:42.106 align:start position:0% in case you see them on the exam what they're<12:37:40.980> referring<12:37:41.400> to 12:37:42.106 --> 12:37:42.116 align:start position:0% they're referring to 12:37:42.116 --> 12:37:45.350 align:start position:0% they're referring to so<12:37:42.480> a<12:37:43.320> router<12:37:43.800> is<12:37:44.400> essentially<12:37:44.756> like<12:37:45.116> an 12:37:45.350 --> 12:37:45.360 align:start position:0% so a router is essentially like an 12:37:45.360 --> 12:37:47.570 align:start position:0% so a router is essentially like an extension<12:37:45.776> cable<12:37:46.616> an<12:37:46.980> extension<12:37:47.340> cable 12:37:47.570 --> 12:37:47.580 align:start position:0% extension cable an extension cable 12:37:47.580 --> 12:37:49.670 align:start position:0% extension cable an extension cable connects<12:37:48.060> two<12:37:48.180> sources<12:37:48.596> of<12:37:48.776> power<12:37:49.020> and<12:37:49.560> in 12:37:49.670 --> 12:37:49.680 align:start position:0% connects two sources of power and in 12:37:49.680 --> 12:37:52.550 align:start position:0% connects two sources of power and in this<12:37:49.800> case<12:37:49.916> a<12:37:50.340> router<12:37:50.700> connects<12:37:51.480> to<12:37:51.660> networks 12:37:52.550 --> 12:37:52.560 align:start position:0% this case a router connects to networks 12:37:52.560 --> 12:37:54.530 align:start position:0% this case a router connects to networks together<12:37:52.680> in<12:37:53.220> order<12:37:53.340> to<12:37:53.520> make<12:37:53.700> a<12:37:54.180> larger 12:37:54.530 --> 12:37:54.540 align:start position:0% together in order to make a larger 12:37:54.540 --> 12:37:55.670 align:start position:0% together in order to make a larger Network 12:37:55.670 --> 12:37:55.680 align:start position:0% Network 12:37:55.680 --> 12:37:57.530 align:start position:0% Network in<12:37:56.040> networking<12:37:56.460> the<12:37:56.640> router<12:37:57.000> is<12:37:57.116> used<12:37:57.240> to 12:37:57.530 --> 12:37:57.540 align:start position:0% in networking the router is used to 12:37:57.540 --> 12:38:00.050 align:start position:0% in networking the router is used to connect<12:37:57.720> two<12:37:58.436> networks<12:37:59.096> together<12:37:59.340> and<12:37:59.700> give<12:37:59.880> a 12:38:00.050 --> 12:38:00.060 align:start position:0% connect two networks together and give a 12:38:00.060 --> 12:38:02.830 align:start position:0% connect two networks together and give a clear<12:38:00.300> route<12:38:00.720> for<12:38:01.320> data<12:38:01.740> to<12:38:01.860> travel<12:38:02.096> between 12:38:02.830 --> 12:38:02.840 align:start position:0% clear route for data to travel between 12:38:02.840 --> 12:38:05.926 align:start position:0% clear route for data to travel between these<12:38:03.840> two<12:38:04.020> devices<12:38:04.500> now<12:38:05.340> in<12:38:05.520> smaller 12:38:05.926 --> 12:38:05.936 align:start position:0% these two devices now in smaller 12:38:05.936 --> 12:38:09.650 align:start position:0% these two devices now in smaller settings<12:38:06.180> such<12:38:06.776> as<12:38:07.020> houses<12:38:07.980> or<12:38:08.880> a<12:38:09.240> small 12:38:09.650 --> 12:38:09.660 align:start position:0% settings such as houses or a small 12:38:09.660 --> 12:38:13.070 align:start position:0% settings such as houses or a small office<12:38:09.900> home<12:38:10.320> office<12:38:10.560> or<12:38:11.040> Soho 12:38:13.070 --> 12:38:13.080 align:start position:0% office home office or Soho 12:38:13.080 --> 12:38:15.950 align:start position:0% office home office or Soho the<12:38:13.860> router<12:38:14.220> connects<12:38:14.700> the<12:38:14.936> device<12:38:15.180> is<12:38:15.540> to<12:38:15.776> the 12:38:15.950 --> 12:38:15.960 align:start position:0% the router connects the device is to the 12:38:15.960 --> 12:38:19.310 align:start position:0% the router connects the device is to the Internet<12:38:16.080> so<12:38:16.916> for<12:38:17.160> instance<12:38:17.460> you<12:38:18.240> have<12:38:18.596> uh 12:38:19.310 --> 12:38:19.320 align:start position:0% Internet so for instance you have uh 12:38:19.320 --> 12:38:22.246 align:start position:0% Internet so for instance you have uh your<12:38:19.740> computer<12:38:20.116> and<12:38:21.116> you<12:38:21.300> have<12:38:21.360> a<12:38:21.596> laptop<12:38:21.900> and 12:38:22.246 --> 12:38:22.256 align:start position:0% your computer and you have a laptop and 12:38:22.256 --> 12:38:24.290 align:start position:0% your computer and you have a laptop and perhaps<12:38:22.560> you<12:38:22.800> have<12:38:22.980> some<12:38:23.276> sort<12:38:23.460> of<12:38:23.580> Apple<12:38:23.820> TV 12:38:24.290 --> 12:38:24.300 align:start position:0% perhaps you have some sort of Apple TV 12:38:24.300 --> 12:38:26.510 align:start position:0% perhaps you have some sort of Apple TV device<12:38:24.720> or<12:38:25.500> some<12:38:25.680> device<12:38:25.860> that's<12:38:26.160> connecting 12:38:26.510 --> 12:38:26.520 align:start position:0% device or some device that's connecting 12:38:26.520 --> 12:38:28.130 align:start position:0% device or some device that's connecting to<12:38:26.640> your<12:38:26.756> TV<12:38:27.000> and<12:38:27.116> the<12:38:27.300> internet<12:38:27.360> and<12:38:27.840> all<12:38:28.020> of 12:38:28.130 --> 12:38:28.140 align:start position:0% to your TV and the internet and all of 12:38:28.140 --> 12:38:30.170 align:start position:0% to your TV and the internet and all of these<12:38:28.320> connect<12:38:28.500> through<12:38:28.860> what<12:38:29.096> you<12:38:29.220> call<12:38:29.460> your 12:38:30.170 --> 12:38:30.180 align:start position:0% these connect through what you call your 12:38:30.180 --> 12:38:31.370 align:start position:0% these connect through what you call your router 12:38:31.370 --> 12:38:31.380 align:start position:0% router 12:38:31.380 --> 12:38:33.950 align:start position:0% router now<12:38:31.860> this<12:38:32.220> Soho<12:38:32.880> router<12:38:33.360> is<12:38:33.480> actually<12:38:33.720> doing 12:38:33.950 --> 12:38:33.960 align:start position:0% now this Soho router is actually doing 12:38:33.960 --> 12:38:36.650 align:start position:0% now this Soho router is actually doing several<12:38:34.500> things<12:38:34.800> it's<12:38:35.460> not<12:38:35.700> just<12:38:36.000> a<12:38:36.300> router 12:38:36.650 --> 12:38:36.660 align:start position:0% several things it's not just a router 12:38:36.660 --> 12:38:39.406 align:start position:0% several things it's not just a router but<12:38:37.320> one<12:38:37.560> of<12:38:37.680> the<12:38:37.740> things<12:38:37.916> that<12:38:38.220> it<12:38:38.400> does<12:38:38.580> is<12:38:39.180> it 12:38:39.406 --> 12:38:39.416 align:start position:0% but one of the things that it does is it 12:38:39.416 --> 12:38:41.810 align:start position:0% but one of the things that it does is it allows<12:38:39.840> you<12:38:40.380> to<12:38:40.616> connect<12:38:40.740> all<12:38:41.276> of<12:38:41.400> these 12:38:41.810 --> 12:38:41.820 align:start position:0% allows you to connect all of these 12:38:41.820 --> 12:38:44.650 align:start position:0% allows you to connect all of these devices<12:38:42.480> in<12:38:43.080> your<12:38:43.320> internal<12:38:43.860> Network 12:38:44.650 --> 12:38:44.660 align:start position:0% devices in your internal Network 12:38:44.660 --> 12:38:48.650 align:start position:0% devices in your internal Network otherwise<12:38:45.660> known<12:38:45.900> as<12:38:46.080> your<12:38:46.320> Lan<12:38:46.616> out<12:38:47.400> to<12:38:47.660> the 12:38:48.650 --> 12:38:48.660 align:start position:0% otherwise known as your Lan out to the 12:38:48.660 --> 12:38:51.530 align:start position:0% otherwise known as your Lan out to the large<12:38:48.840> Wan<12:38:49.560> or<12:38:49.740> wide<12:38:50.096> area<12:38:50.340> network<12:38:50.756> that 12:38:51.530 --> 12:38:51.540 align:start position:0% large Wan or wide area network that 12:38:51.540 --> 12:38:54.650 align:start position:0% large Wan or wide area network that exists<12:38:52.020> in<12:38:52.320> the<12:38:52.500> world<12:38:52.680> this<12:38:53.400> is<12:38:53.580> called<12:38:53.820> the 12:38:54.650 --> 12:38:54.660 align:start position:0% exists in the world this is called the 12:38:54.660 --> 12:38:57.586 align:start position:0% exists in the world this is called the internet 12:38:57.586 --> 12:38:57.596 align:start position:0% 12:38:57.596 --> 12:39:00.890 align:start position:0% so<12:38:58.500> in<12:38:58.860> a<12:38:59.040> larger<12:38:59.276> scale<12:38:59.580> environment<12:39:00.116> the 12:39:00.890 --> 12:39:00.900 align:start position:0% so in a larger scale environment the 12:39:00.900 --> 12:39:03.170 align:start position:0% so in a larger scale environment the routers<12:39:01.256> are<12:39:01.500> used<12:39:01.680> to<12:39:02.160> make<12:39:02.340> bigger<12:39:02.880> Network 12:39:03.170 --> 12:39:03.180 align:start position:0% routers are used to make bigger Network 12:39:03.180 --> 12:39:05.210 align:start position:0% routers are used to make bigger Network pieces<12:39:03.776> so<12:39:04.200> if<12:39:04.320> you<12:39:04.436> can<12:39:04.616> imagine<12:39:04.800> that 12:39:05.210 --> 12:39:05.220 align:start position:0% pieces so if you can imagine that 12:39:05.220 --> 12:39:07.670 align:start position:0% pieces so if you can imagine that instead<12:39:05.520> of<12:39:05.580> just<12:39:05.756> having<12:39:06.000> my<12:39:06.360> own<12:39:06.480> home<12:39:06.776> I 12:39:07.670 --> 12:39:07.680 align:start position:0% instead of just having my own home I 12:39:07.680 --> 12:39:10.606 align:start position:0% instead of just having my own home I have<12:39:07.980> say<12:39:08.640> a<12:39:09.060> number<12:39:09.180> of<12:39:09.416> buildings<12:39:09.900> across<12:39:10.500> a 12:39:10.606 --> 12:39:10.616 align:start position:0% have say a number of buildings across a 12:39:10.616 --> 12:39:13.490 align:start position:0% have say a number of buildings across a city<12:39:10.800> or<12:39:11.580> a<12:39:11.880> number<12:39:12.000> of<12:39:12.180> buildings<12:39:12.720> across<12:39:13.380> the 12:39:13.490 --> 12:39:13.500 align:start position:0% city or a number of buildings across the 12:39:13.500 --> 12:39:15.890 align:start position:0% city or a number of buildings across the world<12:39:13.740> and<12:39:14.340> I<12:39:14.460> want<12:39:14.640> them<12:39:14.820> all<12:39:15.000> to<12:39:15.360> talk<12:39:15.540> to<12:39:15.776> one 12:39:15.890 --> 12:39:15.900 align:start position:0% world and I want them all to talk to one 12:39:15.900 --> 12:39:17.926 align:start position:0% world and I want them all to talk to one another<12:39:16.080> and<12:39:16.800> be<12:39:17.040> able<12:39:17.220> to<12:39:17.340> locate<12:39:17.756> one 12:39:17.926 --> 12:39:17.936 align:start position:0% another and be able to locate one 12:39:17.936 --> 12:39:19.426 align:start position:0% another and be able to locate one another<12:39:18.060> as<12:39:18.416> though<12:39:18.596> they're<12:39:18.840> sitting<12:39:19.256> right 12:39:19.426 --> 12:39:19.436 align:start position:0% another as though they're sitting right 12:39:19.436 --> 12:39:21.470 align:start position:0% another as though they're sitting right next<12:39:19.560> to<12:39:19.740> each<12:39:19.916> other<12:39:20.040> this<12:39:20.640> is<12:39:20.756> where<12:39:21.000> routers 12:39:21.470 --> 12:39:21.480 align:start position:0% next to each other this is where routers 12:39:21.480 --> 12:39:23.086 align:start position:0% next to each other this is where routers are<12:39:21.596> going<12:39:21.720> to<12:39:21.840> come<12:39:21.960> into<12:39:22.140> play 12:39:23.086 --> 12:39:23.096 align:start position:0% are going to come into play 12:39:23.096 --> 12:39:25.550 align:start position:0% are going to come into play this<12:39:23.520> is<12:39:23.700> also<12:39:23.936> why<12:39:24.060> routers<12:39:24.596> do<12:39:25.080> a<12:39:25.256> lot<12:39:25.320> more 12:39:25.550 --> 12:39:25.560 align:start position:0% this is also why routers do a lot more 12:39:25.560 --> 12:39:28.010 align:start position:0% this is also why routers do a lot more and<12:39:25.916> are<12:39:26.096> more<12:39:26.276> expensive<12:39:26.820> than<12:39:27.416> switches 12:39:28.010 --> 12:39:28.020 align:start position:0% and are more expensive than switches 12:39:28.020 --> 12:39:30.890 align:start position:0% and are more expensive than switches it's<12:39:28.740> also<12:39:29.040> why<12:39:29.160> we<12:39:29.340> need<12:39:29.460> fewer<12:39:29.936> of<12:39:30.116> them 12:39:30.890 --> 12:39:30.900 align:start position:0% it's also why we need fewer of them 12:39:30.900 --> 12:39:35.150 align:start position:0% it's also why we need fewer of them now<12:39:31.616> in<12:39:32.520> modern<12:39:32.756> networking<12:39:33.540> the<12:39:34.140> router<12:39:34.560> is 12:39:35.150 --> 12:39:35.160 align:start position:0% now in modern networking the router is 12:39:35.160 --> 12:39:38.330 align:start position:0% now in modern networking the router is either<12:39:35.340> going<12:39:35.640> to<12:39:35.820> be<12:39:36.000> a<12:39:36.300> dedicated<12:39:36.720> device<12:39:37.340> or 12:39:38.330 --> 12:39:38.340 align:start position:0% either going to be a dedicated device or 12:39:38.340 --> 12:39:41.150 align:start position:0% either going to be a dedicated device or it<12:39:39.116> could<12:39:39.240> be<12:39:39.416> a<12:39:39.720> server 12:39:41.150 --> 12:39:41.160 align:start position:0% it could be a server 12:39:41.160 --> 12:39:44.150 align:start position:0% it could be a server with<12:39:41.936> a<12:39:42.180> routing<12:39:42.596> functionality 12:39:44.150 --> 12:39:44.160 align:start position:0% with a routing functionality 12:39:44.160 --> 12:39:48.106 align:start position:0% with a routing functionality meaning<12:39:44.756> it's<12:39:45.360> a<12:39:45.596> large<12:39:45.900> computer<12:39:46.400> with<12:39:47.400> two 12:39:48.106 --> 12:39:48.116 align:start position:0% meaning it's a large computer with two 12:39:48.116 --> 12:39:51.290 align:start position:0% meaning it's a large computer with two or<12:39:48.360> more<12:39:48.596> network<12:39:49.140> cards<12:39:49.616> or<12:39:49.740> Nicks<12:39:50.276> in<12:39:50.460> it<12:39:50.640> so 12:39:51.290 --> 12:39:51.300 align:start position:0% or more network cards or Nicks in it so 12:39:51.300 --> 12:39:54.650 align:start position:0% or more network cards or Nicks in it so that<12:39:51.540> you<12:39:51.776> can<12:39:51.960> have<12:39:52.680> traffic<12:39:53.460> going<12:39:53.820> in<12:39:54.116> and 12:39:54.650 --> 12:39:54.660 align:start position:0% that you can have traffic going in and 12:39:54.660 --> 12:39:56.870 align:start position:0% that you can have traffic going in and then<12:39:54.776> traffic<12:39:55.140> going<12:39:55.436> out 12:39:56.870 --> 12:39:56.880 align:start position:0% then traffic going out 12:39:56.880 --> 12:40:00.470 align:start position:0% then traffic going out now<12:39:57.540> when<12:39:58.020> a<12:39:58.256> router<12:39:58.680> receives<12:39:59.340> a<12:40:00.060> packet<12:40:00.360> of 12:40:00.470 --> 12:40:00.480 align:start position:0% now when a router receives a packet of 12:40:00.480 --> 12:40:02.990 align:start position:0% now when a router receives a packet of data<12:40:00.720> from<12:40:00.900> a<12:40:01.080> client<12:40:01.256> device<12:40:01.500> it<12:40:02.460> reads<12:40:02.820> the 12:40:02.990 --> 12:40:03.000 align:start position:0% data from a client device it reads the 12:40:03.000 --> 12:40:06.470 align:start position:0% data from a client device it reads the information<12:40:03.500> in<12:40:04.500> the<12:40:04.740> packets<12:40:05.220> header<12:40:06.060> and 12:40:06.470 --> 12:40:06.480 align:start position:0% information in the packets header and 12:40:06.480 --> 12:40:08.086 align:start position:0% information in the packets header and determines<12:40:06.900> what<12:40:07.256> the<12:40:07.380> destination<12:40:07.740> of<12:40:07.980> the 12:40:08.086 --> 12:40:08.096 align:start position:0% determines what the destination of the 12:40:08.096 --> 12:40:10.850 align:start position:0% determines what the destination of the packet<12:40:08.460> is<12:40:08.720> after<12:40:09.720> it<12:40:09.960> finds<12:40:10.256> out<12:40:10.380> what<12:40:10.680> the 12:40:10.850 --> 12:40:10.860 align:start position:0% packet is after it finds out what the 12:40:10.860 --> 12:40:13.850 align:start position:0% packet is after it finds out what the destination<12:40:11.220> address<12:40:11.580> is<12:40:12.300> it<12:40:13.020> looks<12:40:13.320> at<12:40:13.500> a 12:40:13.850 --> 12:40:13.860 align:start position:0% destination address is it looks at a 12:40:13.860 --> 12:40:16.070 align:start position:0% destination address is it looks at a routing<12:40:14.276> table 12:40:16.070 --> 12:40:16.080 align:start position:0% routing table 12:40:16.080 --> 12:40:19.030 align:start position:0% routing table in<12:40:16.616> the<12:40:16.800> router<12:40:17.160> in<12:40:17.880> order<12:40:18.000> to<12:40:18.300> determine 12:40:19.030 --> 12:40:19.040 align:start position:0% in the router in order to determine 12:40:19.040 --> 12:40:22.190 align:start position:0% in the router in order to determine where<12:40:20.040> the<12:40:20.460> packet<12:40:20.820> is<12:40:21.116> going<12:40:21.300> to<12:40:21.480> go<12:40:21.660> in<12:40:21.960> its 12:40:22.190 --> 12:40:22.200 align:start position:0% where the packet is going to go in its 12:40:22.200 --> 12:40:24.890 align:start position:0% where the packet is going to go in its next<12:40:22.320> route<12:40:22.560> so<12:40:23.340> for<12:40:23.580> instance<12:40:23.880> let's<12:40:24.596> say 12:40:24.890 --> 12:40:24.900 align:start position:0% next route so for instance let's say 12:40:24.900 --> 12:40:27.766 align:start position:0% next route so for instance let's say this<12:40:25.500> PC<12:40:25.860> here<12:40:26.160> which<12:40:26.580> for<12:40:26.936> sake<12:40:27.300> of<12:40:27.480> ease 12:40:27.766 --> 12:40:27.776 align:start position:0% this PC here which for sake of ease 12:40:27.776 --> 12:40:31.426 align:start position:0% this PC here which for sake of ease we'll<12:40:27.900> call<12:40:28.080> pc1<12:40:28.680> wants<12:40:29.460> to<12:40:29.580> talk<12:40:29.756> to<12:40:30.180> PC2 12:40:31.426 --> 12:40:31.436 align:start position:0% we'll call pc1 wants to talk to PC2 12:40:31.436 --> 12:40:34.370 align:start position:0% we'll call pc1 wants to talk to PC2 now<12:40:31.860> it<12:40:32.040> has<12:40:32.276> an<12:40:32.520> IP<12:40:32.820> address<12:40:33.000> in<12:40:33.416> mind<12:40:33.596> and<12:40:34.256> so 12:40:34.370 --> 12:40:34.380 align:start position:0% now it has an IP address in mind and so 12:40:34.380 --> 12:40:36.950 align:start position:0% now it has an IP address in mind and so what<12:40:34.560> it<12:40:34.680> does<12:40:34.860> is<12:40:35.096> it<12:40:35.400> goes<12:40:35.936> perhaps<12:40:36.660> through 12:40:36.950 --> 12:40:36.960 align:start position:0% what it does is it goes perhaps through 12:40:36.960 --> 12:40:39.406 align:start position:0% what it does is it goes perhaps through a<12:40:37.200> switch<12:40:37.380> but<12:40:37.740> eventually<12:40:38.160> to<12:40:38.580> the<12:40:38.880> router<12:40:39.240> at 12:40:39.406 --> 12:40:39.416 align:start position:0% a switch but eventually to the router at 12:40:39.416 --> 12:40:43.010 align:start position:0% a switch but eventually to the router at the<12:40:39.540> end<12:40:39.660> of<12:40:39.776> its<12:40:40.020> LAN 12:40:43.010 --> 12:40:43.020 align:start position:0% 12:40:43.020 --> 12:40:45.350 align:start position:0% and<12:40:43.560> it<12:40:43.680> says<12:40:43.980> hey<12:40:44.160> I'm<12:40:44.460> looking<12:40:44.700> for<12:40:45.060> this 12:40:45.350 --> 12:40:45.360 align:start position:0% and it says hey I'm looking for this 12:40:45.360 --> 12:40:48.290 align:start position:0% and it says hey I'm looking for this specific<12:40:45.660> PC<12:40:46.140> now<12:40:46.980> this<12:40:47.220> router<12:40:47.640> has<12:40:48.060> what's 12:40:48.290 --> 12:40:48.300 align:start position:0% specific PC now this router has what's 12:40:48.300 --> 12:40:51.106 align:start position:0% specific PC now this router has what's called<12:40:48.596> a<12:40:49.436> routing<12:40:49.800> table<12:40:49.980> which<12:40:50.820> sometimes 12:40:51.106 --> 12:40:51.116 align:start position:0% called a routing table which sometimes 12:40:51.116 --> 12:40:53.266 align:start position:0% called a routing table which sometimes we're<12:40:51.300> going<12:40:51.480> to<12:40:51.540> call<12:40:51.660> an<12:40:51.900> ARP<12:40:52.320> table<12:40:52.560> because 12:40:53.266 --> 12:40:53.276 align:start position:0% we're going to call an ARP table because 12:40:53.276 --> 12:40:55.670 align:start position:0% we're going to call an ARP table because ARP<12:40:54.000> again<12:40:54.300> the<12:40:54.660> address<12:40:54.840> resolution 12:40:55.670 --> 12:40:55.680 align:start position:0% ARP again the address resolution 12:40:55.680 --> 12:40:58.670 align:start position:0% ARP again the address resolution protocol<12:40:56.400> is<12:40:57.116> what<12:40:57.300> allows<12:40:57.720> routing<12:40:58.140> to<12:40:58.320> occur 12:40:58.670 --> 12:40:58.680 align:start position:0% protocol is what allows routing to occur 12:40:58.680 --> 12:41:00.950 align:start position:0% protocol is what allows routing to occur it's<12:40:59.276> this<12:40:59.640> protocol<12:41:00.116> that<12:41:00.480> we've<12:41:00.660> talked 12:41:00.950 --> 12:41:00.960 align:start position:0% it's this protocol that we've talked 12:41:00.960 --> 12:41:03.170 align:start position:0% it's this protocol that we've talked about<12:41:01.020> which<12:41:01.740> allows<12:41:02.160> for<12:41:02.340> a<12:41:02.580> table<12:41:02.756> that 12:41:03.170 --> 12:41:03.180 align:start position:0% about which allows for a table that 12:41:03.180 --> 12:41:06.470 align:start position:0% about which allows for a table that would<12:41:03.300> say<12:41:03.540> for<12:41:03.776> instance<12:41:03.960> one<12:41:04.400> goes<12:41:05.400> to<12:41:05.580> IP 12:41:06.470 --> 12:41:06.480 align:start position:0% would say for instance one goes to IP 12:41:06.480 --> 12:41:09.766 align:start position:0% would say for instance one goes to IP address<12:41:06.916> 192<12:41:07.916> whatever<12:41:08.160> whatever<12:41:08.880> Etc 12:41:09.766 --> 12:41:09.776 align:start position:0% address 192 whatever whatever Etc 12:41:09.776 --> 12:41:13.850 align:start position:0% address 192 whatever whatever Etc and<12:41:10.436> so<12:41:10.616> this<12:41:11.220> router<12:41:11.700> would<12:41:12.360> look<12:41:12.660> for<12:41:12.960> this 12:41:13.850 --> 12:41:13.860 align:start position:0% and so this router would look for this 12:41:13.860 --> 12:41:16.310 align:start position:0% and so this router would look for this information<12:41:14.300> if<12:41:15.300> it<12:41:15.480> doesn't<12:41:15.660> know<12:41:15.840> it<12:41:16.020> it's 12:41:16.310 --> 12:41:16.320 align:start position:0% information if it doesn't know it it's 12:41:16.320 --> 12:41:17.510 align:start position:0% information if it doesn't know it it's going<12:41:16.500> to<12:41:16.560> say<12:41:16.680> I<12:41:16.860> don't<12:41:16.980> know<12:41:17.096> it<12:41:17.220> but<12:41:17.400> I'm 12:41:17.510 --> 12:41:17.520 align:start position:0% going to say I don't know it but I'm 12:41:17.520 --> 12:41:19.130 align:start position:0% going to say I don't know it but I'm going<12:41:17.640> to<12:41:17.640> go<12:41:17.820> to<12:41:17.936> the<12:41:18.116> next<12:41:18.360> router<12:41:18.840> that 12:41:19.130 --> 12:41:19.140 align:start position:0% going to go to the next router that 12:41:19.140 --> 12:41:22.190 align:start position:0% going to go to the next router that might<12:41:19.400> goes<12:41:20.400> to<12:41:20.460> this<12:41:20.640> router<12:41:21.060> and<12:41:21.900> the<12:41:22.080> second 12:41:22.190 --> 12:41:22.200 align:start position:0% might goes to this router and the second 12:41:22.200 --> 12:41:24.350 align:start position:0% might goes to this router and the second router<12:41:22.680> says<12:41:22.916> oh<12:41:23.096> yeah<12:41:23.340> I<12:41:23.880> know<12:41:24.000> where<12:41:24.180> that 12:41:24.350 --> 12:41:24.360 align:start position:0% router says oh yeah I know where that 12:41:24.360 --> 12:41:25.850 align:start position:0% router says oh yeah I know where that computer<12:41:24.480> is 12:41:25.850 --> 12:41:25.860 align:start position:0% computer is 12:41:25.860 --> 12:41:28.490 align:start position:0% computer is and<12:41:26.276> then<12:41:26.400> can<12:41:26.756> forward<12:41:27.000> the<12:41:27.300> packet<12:41:27.720> onto<12:41:28.380> the 12:41:28.490 --> 12:41:28.500 align:start position:0% and then can forward the packet onto the 12:41:28.500 --> 12:41:29.810 align:start position:0% and then can forward the packet onto the computer 12:41:29.810 --> 12:41:29.820 align:start position:0% computer 12:41:29.820 --> 12:41:32.926 align:start position:0% computer it<12:41:30.240> also<12:41:30.596> tells<12:41:31.200> this<12:41:31.680> router<12:41:32.096> the<12:41:32.520> first<12:41:32.700> one 12:41:32.926 --> 12:41:32.936 align:start position:0% it also tells this router the first one 12:41:32.936 --> 12:41:35.746 align:start position:0% it also tells this router the first one which<12:41:33.660> we'll<12:41:33.840> call<12:41:34.020> let's<12:41:34.256> say<12:41:34.436> router<12:41:34.916> a<12:41:35.160> and 12:41:35.746 --> 12:41:35.756 align:start position:0% which we'll call let's say router a and 12:41:35.756 --> 12:41:37.070 align:start position:0% which we'll call let's say router a and router<12:41:36.180> B 12:41:37.070 --> 12:41:37.080 align:start position:0% router B 12:41:37.080 --> 12:41:39.530 align:start position:0% router B where<12:41:37.616> that<12:41:37.800> destination<12:41:38.220> was<12:41:38.580> so<12:41:39.060> it<12:41:39.240> can<12:41:39.360> add 12:41:39.530 --> 12:41:39.540 align:start position:0% where that destination was so it can add 12:41:39.540 --> 12:41:43.670 align:start position:0% where that destination was so it can add it<12:41:39.720> to<12:41:40.080> its<12:41:40.380> ARP<12:41:40.740> or<12:41:41.756> routing<12:41:42.720> table 12:41:43.670 --> 12:41:43.680 align:start position:0% it to its ARP or routing table 12:41:43.680 --> 12:41:46.130 align:start position:0% it to its ARP or routing table and<12:41:44.340> if<12:41:44.580> you<12:41:44.700> imagine<12:41:44.820> this<12:41:45.360> is<12:41:45.480> only<12:41:45.660> what<12:41:45.960> we 12:41:46.130 --> 12:41:46.140 align:start position:0% and if you imagine this is only what we 12:41:46.140 --> 12:41:48.530 align:start position:0% and if you imagine this is only what we call<12:41:46.700> one<12:41:47.700> hop 12:41:48.530 --> 12:41:48.540 align:start position:0% call one hop 12:41:48.540 --> 12:41:52.850 align:start position:0% call one hop because<12:41:49.020> there<12:41:49.380> is<12:41:49.560> one<12:41:50.276> hop<12:41:51.000> between<12:41:51.860> these 12:41:52.850 --> 12:41:52.860 align:start position:0% because there is one hop between these 12:41:52.860 --> 12:41:54.830 align:start position:0% because there is one hop between these two<12:41:52.980> routers<12:41:53.400> but<12:41:53.880> you<12:41:54.000> can<12:41:54.116> imagine<12:41:54.300> in<12:41:54.660> the 12:41:54.830 --> 12:41:54.840 align:start position:0% two routers but you can imagine in the 12:41:54.840 --> 12:41:57.670 align:start position:0% two routers but you can imagine in the entire<12:41:55.080> world<12:41:55.320> if<12:41:55.800> I'm<12:41:55.980> traveling<12:41:56.460> from<12:41:56.880> say 12:41:57.670 --> 12:41:57.680 align:start position:0% entire world if I'm traveling from say 12:41:57.680 --> 12:42:00.586 align:start position:0% entire world if I'm traveling from say here<12:41:58.680> in<12:41:59.096> New<12:41:59.340> York<12:41:59.520> City<12:41:59.756> all<12:42:00.180> the<12:42:00.360> way<12:42:00.416> to 12:42:00.586 --> 12:42:00.596 align:start position:0% here in New York City all the way to 12:42:00.596 --> 12:42:02.450 align:start position:0% here in New York City all the way to Australia<12:42:01.140> for<12:42:01.380> instance<12:42:01.616> I<12:42:02.040> might<12:42:02.160> have<12:42:02.340> to 12:42:02.450 --> 12:42:02.460 align:start position:0% Australia for instance I might have to 12:42:02.460 --> 12:42:04.850 align:start position:0% Australia for instance I might have to take<12:42:02.640> several<12:42:03.060> different<12:42:03.240> Hops<12:42:03.840> and<12:42:04.436> also<12:42:04.680> if 12:42:04.850 --> 12:42:04.860 align:start position:0% take several different Hops and also if 12:42:04.860 --> 12:42:06.406 align:start position:0% take several different Hops and also if you<12:42:04.980> imagine<12:42:05.160> there<12:42:05.700> are<12:42:05.820> probably<12:42:06.000> many 12:42:06.406 --> 12:42:06.416 align:start position:0% you imagine there are probably many 12:42:06.416 --> 12:42:09.170 align:start position:0% you imagine there are probably many different<12:42:06.776> routes<12:42:07.380> that<12:42:07.860> I<12:42:08.096> can<12:42:08.220> take<12:42:08.460> to<12:42:09.000> get 12:42:09.170 --> 12:42:09.180 align:start position:0% different routes that I can take to get 12:42:09.180 --> 12:42:11.150 align:start position:0% different routes that I can take to get to<12:42:09.480> a<12:42:09.720> specific<12:42:09.960> computer 12:42:11.150 --> 12:42:11.160 align:start position:0% to a specific computer 12:42:11.160 --> 12:42:13.370 align:start position:0% to a specific computer if<12:42:11.580> we<12:42:11.700> imagine 12:42:13.370 --> 12:42:13.380 align:start position:0% if we imagine 12:42:13.380 --> 12:42:17.450 align:start position:0% if we imagine that<12:42:14.096> the<12:42:14.340> circles<12:42:14.640> are<12:42:14.820> the<12:42:15.000> two<12:42:15.116> computers 12:42:17.450 --> 12:42:17.460 align:start position:0% that the circles are the two computers 12:42:17.460 --> 12:42:21.950 align:start position:0% that the circles are the two computers and<12:42:18.240> the<12:42:18.596> squares<12:42:19.140> are<12:42:19.916> the<12:42:20.340> different<12:42:21.300> types 12:42:21.950 --> 12:42:21.960 align:start position:0% and the squares are the different types 12:42:21.960 --> 12:42:31.790 align:start position:0% and the squares are the different types of<12:42:22.276> routers<12:42:23.276> and<12:42:24.116> we<12:42:24.300> have<12:42:24.416> them<12:42:24.660> connected 12:42:31.790 --> 12:42:31.800 align:start position:0% 12:42:31.800 --> 12:42:33.650 align:start position:0% like<12:42:32.400> so 12:42:33.650 --> 12:42:33.660 align:start position:0% like so 12:42:33.660 --> 12:42:35.150 align:start position:0% like so well<12:42:33.960> there<12:42:34.140> are<12:42:34.256> a<12:42:34.320> lot<12:42:34.436> of<12:42:34.500> different<12:42:34.680> routes 12:42:35.150 --> 12:42:35.160 align:start position:0% well there are a lot of different routes 12:42:35.160 --> 12:42:37.490 align:start position:0% well there are a lot of different routes that<12:42:35.400> a<12:42:35.580> packet<12:42:35.880> can<12:42:36.060> take<12:42:36.300> to<12:42:36.960> get<12:42:37.080> from<12:42:37.256> point 12:42:37.490 --> 12:42:37.500 align:start position:0% that a packet can take to get from point 12:42:37.500 --> 12:42:38.266 align:start position:0% that a packet can take to get from point A 12:42:38.266 --> 12:42:38.276 align:start position:0% A 12:42:38.276 --> 12:42:41.210 align:start position:0% A to<12:42:38.640> point<12:42:38.880> B<12:42:39.116> and<12:42:39.720> so<12:42:39.900> we<12:42:40.020> were<12:42:40.140> allowed<12:42:40.436> on<12:42:40.616> WE 12:42:41.210 --> 12:42:41.220 align:start position:0% to point B and so we were allowed on WE 12:42:41.220 --> 12:42:43.850 align:start position:0% to point B and so we were allowed on WE rely<12:42:41.640> rather<12:42:42.000> on<12:42:42.240> routers<12:42:42.660> to<12:42:42.960> tell<12:42:43.080> us<12:42:43.256> which 12:42:43.850 --> 12:42:43.860 align:start position:0% rely rather on routers to tell us which 12:42:43.860 --> 12:42:45.710 align:start position:0% rely rather on routers to tell us which path<12:42:44.040> it's<12:42:44.276> going<12:42:44.520> to<12:42:44.580> take<12:42:44.756> it<12:42:45.360> could<12:42:45.540> take 12:42:45.710 --> 12:42:45.720 align:start position:0% path it's going to take it could take 12:42:45.720 --> 12:42:47.990 align:start position:0% path it's going to take it could take this<12:42:45.960> path 12:42:47.990 --> 12:42:48.000 align:start position:0% this path 12:42:48.000 --> 12:42:52.970 align:start position:0% this path or<12:42:48.960> it<12:42:49.560> could<12:42:49.740> take 12:42:52.970 --> 12:42:52.980 align:start position:0% 12:42:52.980 --> 12:42:56.390 align:start position:0% this<12:42:53.640> path<12:42:53.820> and<12:42:54.360> so<12:42:54.480> on<12:42:54.660> and<12:42:54.840> so<12:42:55.020> forth<12:42:55.680> and<12:42:56.220> so 12:42:56.390 --> 12:42:56.400 align:start position:0% this path and so on and so forth and so 12:42:56.400 --> 12:42:59.266 align:start position:0% this path and so on and so forth and so uh<12:42:57.240> depending<12:42:57.840> on<12:42:58.080> the<12:42:58.200> number<12:42:58.320> of<12:42:58.500> hops<12:42:59.040> and<12:42:59.160> a 12:42:59.266 --> 12:42:59.276 align:start position:0% uh depending on the number of hops and a 12:42:59.276 --> 12:43:00.350 align:start position:0% uh depending on the number of hops and a number<12:42:59.400> of<12:42:59.520> other<12:42:59.640> things<12:42:59.880> we'll<12:43:00.060> talk<12:43:00.240> about 12:43:00.350 --> 12:43:00.360 align:start position:0% number of other things we'll talk about 12:43:00.360 --> 12:43:02.570 align:start position:0% number of other things we'll talk about in<12:43:00.540> just<12:43:00.720> a<12:43:00.900> minute<12:43:01.020> it'll<12:43:01.740> determine<12:43:02.160> where 12:43:02.570 --> 12:43:02.580 align:start position:0% in just a minute it'll determine where 12:43:02.580 --> 12:43:04.190 align:start position:0% in just a minute it'll determine where the<12:43:02.756> packet<12:43:03.060> needs<12:43:03.360> to<12:43:03.416> go<12:43:03.540> in<12:43:03.720> order<12:43:03.840> to<12:43:04.080> get 12:43:04.190 --> 12:43:04.200 align:start position:0% the packet needs to go in order to get 12:43:04.200 --> 12:43:06.230 align:start position:0% the packet needs to go in order to get from<12:43:04.500> point<12:43:04.616> A<12:43:04.800> to<12:43:04.980> point<12:43:05.160> B<12:43:05.340> some<12:43:06.060> other 12:43:06.230 --> 12:43:06.240 align:start position:0% from point A to point B some other 12:43:06.240 --> 12:43:07.550 align:start position:0% from point A to point B some other things<12:43:06.416> it's<12:43:06.596> going<12:43:06.776> to<12:43:06.776> determine<12:43:07.140> too<12:43:07.256> or 12:43:07.550 --> 12:43:07.560 align:start position:0% things it's going to determine too or 12:43:07.560 --> 12:43:09.470 align:start position:0% things it's going to determine too or what<12:43:07.680> if<12:43:07.860> there's<12:43:07.980> a<12:43:08.160> cut<12:43:08.276> in<12:43:08.520> the<12:43:08.640> line<12:43:08.820> well 12:43:09.470 --> 12:43:09.480 align:start position:0% what if there's a cut in the line well 12:43:09.480 --> 12:43:11.810 align:start position:0% what if there's a cut in the line well now<12:43:09.660> it<12:43:09.900> can't<12:43:10.080> get<12:43:10.256> here 12:43:11.810 --> 12:43:11.820 align:start position:0% now it can't get here 12:43:11.820 --> 12:43:13.310 align:start position:0% now it can't get here and<12:43:12.180> so<12:43:12.300> instead<12:43:12.596> it'll<12:43:12.776> say<12:43:12.900> well<12:43:13.020> let's<12:43:13.140> try 12:43:13.310 --> 12:43:13.320 align:start position:0% and so instead it'll say well let's try 12:43:13.320 --> 12:43:16.190 align:start position:0% and so instead it'll say well let's try one<12:43:13.500> of<12:43:13.616> our<12:43:13.740> alternate<12:43:14.160> routes<12:43:14.400> as<12:43:14.580> well 12:43:16.190 --> 12:43:16.200 align:start position:0% one of our alternate routes as well 12:43:16.200 --> 12:43:18.350 align:start position:0% one of our alternate routes as well now<12:43:16.560> in<12:43:16.740> the<12:43:16.916> previous<12:43:17.040> slide<12:43:17.580> I<12:43:18.060> talked<12:43:18.300> about 12:43:18.350 --> 12:43:18.360 align:start position:0% now in the previous slide I talked about 12:43:18.360 --> 12:43:21.106 align:start position:0% now in the previous slide I talked about how<12:43:18.776> routers<12:43:19.320> might<12:43:19.560> talk<12:43:19.860> to<12:43:20.096> one<12:43:20.276> another<12:43:20.400> in 12:43:21.106 --> 12:43:21.116 align:start position:0% how routers might talk to one another in 12:43:21.116 --> 12:43:23.086 align:start position:0% how routers might talk to one another in order<12:43:21.300> to<12:43:21.540> automatically<12:43:22.080> update<12:43:22.680> their 12:43:23.086 --> 12:43:23.096 align:start position:0% order to automatically update their 12:43:23.096 --> 12:43:26.570 align:start position:0% order to automatically update their routing<12:43:23.520> tables<12:43:23.936> this<12:43:24.720> way<12:43:25.096> two<12:43:26.096> routers 12:43:26.570 --> 12:43:26.580 align:start position:0% routing tables this way two routers 12:43:26.580 --> 12:43:28.490 align:start position:0% routing tables this way two routers always<12:43:26.820> know<12:43:27.116> how<12:43:27.360> to<12:43:27.540> communicate<12:43:28.020> with<12:43:28.320> each 12:43:28.490 --> 12:43:28.500 align:start position:0% always know how to communicate with each 12:43:28.500 --> 12:43:30.950 align:start position:0% always know how to communicate with each other<12:43:28.680> or<12:43:29.520> one<12:43:29.880> computer<12:43:30.116> on<12:43:30.416> one<12:43:30.596> side<12:43:30.720> of<12:43:30.840> the 12:43:30.950 --> 12:43:30.960 align:start position:0% other or one computer on one side of the 12:43:30.960 --> 12:43:33.350 align:start position:0% other or one computer on one side of the world<12:43:31.020> can<12:43:31.380> always<12:43:31.560> get<12:43:31.860> routed<12:43:32.400> or<12:43:33.000> the 12:43:33.350 --> 12:43:33.360 align:start position:0% world can always get routed or the 12:43:33.360 --> 12:43:34.906 align:start position:0% world can always get routed or the information<12:43:33.480> sent<12:43:34.020> from<12:43:34.256> one<12:43:34.436> computer<12:43:34.616> on 12:43:34.906 --> 12:43:34.916 align:start position:0% information sent from one computer on 12:43:34.916 --> 12:43:35.926 align:start position:0% information sent from one computer on one<12:43:35.096> side<12:43:35.220> of<12:43:35.340> the<12:43:35.400> world<12:43:35.460> can<12:43:35.640> always<12:43:35.756> get 12:43:35.926 --> 12:43:35.936 align:start position:0% one side of the world can always get 12:43:35.936 --> 12:43:37.550 align:start position:0% one side of the world can always get routed<12:43:36.416> to<12:43:36.660> the<12:43:36.840> information<12:43:36.960> on<12:43:37.380> another 12:43:37.550 --> 12:43:37.560 align:start position:0% routed to the information on another 12:43:37.560 --> 12:43:38.810 align:start position:0% routed to the information on another side<12:43:37.800> of<12:43:37.980> the<12:43:38.040> world 12:43:38.810 --> 12:43:38.820 align:start position:0% side of the world 12:43:38.820 --> 12:43:42.586 align:start position:0% side of the world but<12:43:39.416> in<12:43:39.720> some<12:43:39.840> instances<12:43:40.320> we<12:43:41.276> want<12:43:41.580> to<12:43:42.060> tell<12:43:42.300> a 12:43:42.586 --> 12:43:42.596 align:start position:0% but in some instances we want to tell a 12:43:42.596 --> 12:43:44.766 align:start position:0% but in some instances we want to tell a router<12:43:43.020> exactly<12:43:43.560> where<12:43:43.916> to<12:43:44.040> send<12:43:44.276> information 12:43:44.766 --> 12:43:44.776 align:start position:0% router exactly where to send information 12:43:44.776 --> 12:43:47.926 align:start position:0% router exactly where to send information destined<12:43:45.776> for<12:43:45.900> a<12:43:46.140> specific<12:43:46.436> Network<12:43:46.800> now<12:43:47.700> it 12:43:47.926 --> 12:43:47.936 align:start position:0% destined for a specific Network now it 12:43:47.936 --> 12:43:49.310 align:start position:0% destined for a specific Network now it might<12:43:48.060> not<12:43:48.180> always<12:43:48.360> be<12:43:48.540> the<12:43:48.720> most<12:43:48.900> practical 12:43:49.310 --> 12:43:49.320 align:start position:0% might not always be the most practical 12:43:49.320 --> 12:43:52.070 align:start position:0% might not always be the most practical way<12:43:49.616> but<12:43:50.040> sometimes<12:43:50.400> it's<12:43:50.580> necessary<12:43:51.116> so 12:43:52.070 --> 12:43:52.080 align:start position:0% way but sometimes it's necessary so 12:43:52.080 --> 12:43:55.310 align:start position:0% way but sometimes it's necessary so static<12:43:52.680> routing<12:43:53.340> is<12:43:53.640> when<12:43:53.936> a<12:43:54.240> routes<12:43:54.776> and 12:43:55.310 --> 12:43:55.320 align:start position:0% static routing is when a routes and 12:43:55.320 --> 12:43:57.890 align:start position:0% static routing is when a routes and routing<12:43:55.860> information<12:43:56.116> are<12:43:57.116> entered<12:43:57.596> into 12:43:57.890 --> 12:43:57.900 align:start position:0% routing information are entered into 12:43:57.900 --> 12:44:00.650 align:start position:0% routing information are entered into routing<12:43:58.380> tables<12:43:58.800> manually<12:43:59.400> and<12:44:00.000> this<12:44:00.240> can<12:44:00.416> be 12:44:00.650 --> 12:44:00.660 align:start position:0% routing tables manually and this can be 12:44:00.660 --> 12:44:03.350 align:start position:0% routing tables manually and this can be time<12:44:01.140> consuming<12:44:01.740> and<12:44:02.160> because<12:44:02.400> it's<12:44:02.880> prone<12:44:03.240> to 12:44:03.350 --> 12:44:03.360 align:start position:0% time consuming and because it's prone to 12:44:03.360 --> 12:44:06.650 align:start position:0% time consuming and because it's prone to human<12:44:03.596> error<12:44:04.020> it<12:44:04.560> can<12:44:04.740> be<12:44:05.300> error<12:44:06.300> written<12:44:06.540> and 12:44:06.650 --> 12:44:06.660 align:start position:0% human error it can be error written and 12:44:06.660 --> 12:44:08.690 align:start position:0% human error it can be error written and can<12:44:06.840> cause<12:44:07.020> some<12:44:07.320> problems<12:44:07.800> so<12:44:08.276> this<12:44:08.460> is<12:44:08.520> why 12:44:08.690 --> 12:44:08.700 align:start position:0% can cause some problems so this is why 12:44:08.700 --> 12:44:11.746 align:start position:0% can cause some problems so this is why it's<12:44:08.880> only<12:44:09.000> done<12:44:09.240> on<12:44:09.480> very<12:44:09.900> small<12:44:10.380> systems<12:44:11.096> or 12:44:11.746 --> 12:44:11.756 align:start position:0% it's only done on very small systems or 12:44:11.756 --> 12:44:13.550 align:start position:0% it's only done on very small systems or on<12:44:11.936> ones<12:44:12.300> that<12:44:12.480> are<12:44:12.660> very<12:44:12.776> internal<12:44:13.380> and 12:44:13.550 --> 12:44:13.560 align:start position:0% on ones that are very internal and 12:44:13.560 --> 12:44:14.810 align:start position:0% on ones that are very internal and controlled 12:44:14.810 --> 12:44:14.820 align:start position:0% controlled 12:44:14.820 --> 12:44:17.810 align:start position:0% controlled now<12:44:15.360> in<12:44:15.660> order<12:44:15.776> to<12:44:16.320> statically<12:44:16.980> add<12:44:17.460> a<12:44:17.640> route 12:44:17.810 --> 12:44:17.820 align:start position:0% now in order to statically add a route 12:44:17.820 --> 12:44:19.490 align:start position:0% now in order to statically add a route we're<12:44:18.416> usually<12:44:18.720> going<12:44:18.900> to<12:44:19.080> use<12:44:19.200> something 12:44:19.490 --> 12:44:19.500 align:start position:0% we're usually going to use something 12:44:19.500 --> 12:44:22.606 align:start position:0% we're usually going to use something called<12:44:19.916> the<12:44:20.276> route<12:44:20.820> add<12:44:21.240> command<12:44:21.776> now<12:44:22.320> this<12:44:22.500> is 12:44:22.606 --> 12:44:22.616 align:start position:0% called the route add command now this is 12:44:22.616 --> 12:44:24.230 align:start position:0% called the route add command now this is the<12:44:22.800> sort<12:44:22.980> of<12:44:23.040> thing<12:44:23.220> you<12:44:23.460> might<12:44:23.640> use<12:44:23.880> if<12:44:24.180> you 12:44:24.230 --> 12:44:24.240 align:start position:0% the sort of thing you might use if you 12:44:24.240 --> 12:44:27.766 align:start position:0% the sort of thing you might use if you were<12:44:24.360> adding<12:44:24.660> a<12:44:24.776> route<12:44:24.960> to<12:44:25.200> a<12:44:25.320> Cisco<12:44:26.116> router<12:44:27.116> or 12:44:27.766 --> 12:44:27.776 align:start position:0% were adding a route to a Cisco router or 12:44:27.776 --> 12:44:30.170 align:start position:0% were adding a route to a Cisco router or to<12:44:28.020> a<12:44:28.200> Windows<12:44:28.616> machine<12:44:28.860> for<12:44:29.340> instance<12:44:29.580> that 12:44:30.170 --> 12:44:30.180 align:start position:0% to a Windows machine for instance that 12:44:30.180 --> 12:44:32.150 align:start position:0% to a Windows machine for instance that was<12:44:30.360> acting<12:44:30.720> as<12:44:30.840> a<12:44:31.020> router<12:44:31.320> or<12:44:31.500> even<12:44:31.616> a<12:44:31.860> Windows 12:44:32.150 --> 12:44:32.160 align:start position:0% was acting as a router or even a Windows 12:44:32.160 --> 12:44:33.586 align:start position:0% was acting as a router or even a Windows machine<12:44:32.400> that's<12:44:32.700> at<12:44:32.936> the<12:44:33.060> edge<12:44:33.180> of<12:44:33.300> a<12:44:33.480> network 12:44:33.586 --> 12:44:33.596 align:start position:0% machine that's at the edge of a network 12:44:33.596 --> 12:44:36.106 align:start position:0% machine that's at the edge of a network and<12:44:34.200> needs<12:44:34.436> to<12:44:34.500> go<12:44:34.616> out<12:44:34.740> to<12:44:34.860> another<12:44:35.040> the<12:44:36.000> way 12:44:36.106 --> 12:44:36.116 align:start position:0% and needs to go out to another the way 12:44:36.116 --> 12:44:39.890 align:start position:0% and needs to go out to another the way it<12:44:36.300> works<12:44:36.720> is<12:44:37.320> we<12:44:37.560> use<12:44:37.740> the<12:44:37.916> route<12:44:38.160> add<12:44:38.640> command 12:44:39.890 --> 12:44:39.900 align:start position:0% it works is we use the route add command 12:44:39.900 --> 12:44:44.510 align:start position:0% it works is we use the route add command with<12:44:40.740> the<12:44:41.340> network<12:44:41.520> name 12:44:44.510 --> 12:44:44.520 align:start position:0% 12:44:44.520 --> 12:44:48.790 align:start position:0% The<12:44:45.180> Mask<12:44:45.360> or<12:44:45.596> the<12:44:45.840> subnet<12:44:46.256> mask 12:44:48.790 --> 12:44:48.800 align:start position:0% 12:44:48.800 --> 12:44:53.746 align:start position:0% and<12:44:49.800> the<12:44:50.160> IP<12:44:50.520> address<12:44:50.756> of<12:44:51.596> the<12:44:51.720> Gateway 12:44:53.746 --> 12:44:53.756 align:start position:0% and the IP address of the Gateway 12:44:53.756 --> 12:44:57.106 align:start position:0% and the IP address of the Gateway so<12:44:54.480> this<12:44:55.140> tells<12:44:55.500> us<12:44:55.680> if<12:44:56.276> we<12:44:56.460> want<12:44:56.640> to<12:44:56.756> get<12:44:56.936> to 12:44:57.106 --> 12:44:57.116 align:start position:0% so this tells us if we want to get to 12:44:57.116 --> 12:45:01.130 align:start position:0% so this tells us if we want to get to the<12:44:57.240> network<12:44:57.540> 192.168.2.1 12:45:01.130 --> 12:45:01.140 align:start position:0% 12:45:01.140 --> 12:45:03.406 align:start position:0% we<12:45:01.616> need<12:45:01.740> to<12:45:01.916> go<12:45:02.160> to<12:45:02.756> the<12:45:02.880> subnet<12:45:03.240> mask 12:45:03.406 --> 12:45:03.416 align:start position:0% we need to go to the subnet mask 12:45:03.416 --> 12:45:06.406 align:start position:0% we need to go to the subnet mask 255.255.0 12:45:06.406 --> 12:45:06.416 align:start position:0% 255.255.0 12:45:06.416 --> 12:45:09.850 align:start position:0% 255.255.0 and<12:45:06.960> the<12:45:07.140> Gateway 12:45:09.850 --> 12:45:09.860 align:start position:0% and the Gateway 12:45:09.860 --> 12:45:12.170 align:start position:0% and the Gateway 192.168.2.4<12:45:10.860> now<12:45:11.580> all<12:45:11.820> this<12:45:11.936> information 12:45:12.170 --> 12:45:12.180 align:start position:0% 192.168.2.4 now all this information 12:45:12.180 --> 12:45:15.350 align:start position:0% 192.168.2.4 now all this information would<12:45:12.776> automatically<12:45:13.320> be<12:45:13.616> done<12:45:14.360> uh 12:45:15.350 --> 12:45:15.360 align:start position:0% would automatically be done uh 12:45:15.360 --> 12:45:17.570 align:start position:0% would automatically be done uh dynamically<12:45:16.140> by<12:45:16.500> most<12:45:16.740> routers<12:45:17.096> but<12:45:17.340> in<12:45:17.460> some 12:45:17.570 --> 12:45:17.580 align:start position:0% dynamically by most routers but in some 12:45:17.580 --> 12:45:19.850 align:start position:0% dynamically by most routers but in some cases<12:45:17.820> we're<12:45:18.116> going<12:45:18.240> to<12:45:18.360> want<12:45:18.480> to<12:45:18.596> add<12:45:18.776> it<12:45:18.960> or 12:45:19.850 --> 12:45:19.860 align:start position:0% cases we're going to want to add it or 12:45:19.860 --> 12:45:21.650 align:start position:0% cases we're going to want to add it or statically<12:45:20.340> now<12:45:20.820> this<12:45:21.000> isn't<12:45:21.180> something<12:45:21.416> of 12:45:21.650 --> 12:45:21.660 align:start position:0% statically now this isn't something of 12:45:21.660 --> 12:45:23.570 align:start position:0% statically now this isn't something of necessarily<12:45:22.320> seen<12:45:22.680> come<12:45:22.980> up<12:45:23.160> on<12:45:23.400> the<12:45:23.520> network 12:45:23.570 --> 12:45:23.580 align:start position:0% necessarily seen come up on the network 12:45:23.580 --> 12:45:26.210 align:start position:0% necessarily seen come up on the network plus<12:45:23.936> exam<12:45:24.360> but<12:45:24.900> I<12:45:25.080> did<12:45:25.200> want<12:45:25.380> to<12:45:25.560> clarify<12:45:26.040> it 12:45:26.210 --> 12:45:26.220 align:start position:0% plus exam but I did want to clarify it 12:45:26.220 --> 12:45:28.550 align:start position:0% plus exam but I did want to clarify it and<12:45:26.400> go<12:45:26.580> over<12:45:26.756> it<12:45:27.000> just<12:45:27.300> briefly<12:45:27.720> in<12:45:28.200> case<12:45:28.380> you 12:45:28.550 --> 12:45:28.560 align:start position:0% and go over it just briefly in case you 12:45:28.560 --> 12:45:30.406 align:start position:0% and go over it just briefly in case you ever<12:45:28.680> saw<12:45:28.980> it<12:45:29.096> in<12:45:29.276> the<12:45:29.400> field<12:45:29.520> since<12:45:30.180> this 12:45:30.406 --> 12:45:30.416 align:start position:0% ever saw it in the field since this 12:45:30.416 --> 12:45:32.210 align:start position:0% ever saw it in the field since this might<12:45:30.596> be<12:45:30.776> something<12:45:30.960> to<12:45:31.200> do<12:45:31.380> something<12:45:31.860> that 12:45:32.210 --> 12:45:32.220 align:start position:0% might be something to do something that 12:45:32.220 --> 12:45:34.850 align:start position:0% might be something to do something that your<12:45:32.520> administrator<12:45:33.300> or<12:45:33.840> your<12:45:34.020> boss<12:45:34.200> asks<12:45:34.740> you 12:45:34.850 --> 12:45:34.860 align:start position:0% your administrator or your boss asks you 12:45:34.860 --> 12:45:36.230 align:start position:0% your administrator or your boss asks you to<12:45:34.980> do<12:45:35.096> for<12:45:35.340> whatever<12:45:35.460> reason<12:45:35.756> or<12:45:36.116> maybe 12:45:36.230 --> 12:45:36.240 align:start position:0% to do for whatever reason or maybe 12:45:36.240 --> 12:45:37.670 align:start position:0% to do for whatever reason or maybe something<12:45:36.540> you<12:45:36.776> want<12:45:36.900> to<12:45:37.020> play<12:45:37.140> around<12:45:37.320> with 12:45:37.670 --> 12:45:37.680 align:start position:0% something you want to play around with 12:45:37.680 --> 12:45:40.010 align:start position:0% something you want to play around with if<12:45:38.276> you<12:45:38.400> need<12:45:38.520> more<12:45:38.700> information 12:45:40.010 --> 12:45:40.020 align:start position:0% if you need more information 12:45:40.020 --> 12:45:43.010 align:start position:0% if you need more information simply<12:45:40.740> Google<12:45:41.096> the<12:45:41.520> route<12:45:41.700> add<12:45:42.000> command<12:45:42.480> but 12:45:43.010 --> 12:45:43.020 align:start position:0% simply Google the route add command but 12:45:43.020 --> 12:45:44.690 align:start position:0% simply Google the route add command but again<12:45:43.200> I<12:45:43.680> don't<12:45:43.800> think<12:45:43.916> you'll<12:45:44.096> see<12:45:44.276> it<12:45:44.400> on<12:45:44.580> the 12:45:44.690 --> 12:45:44.700 align:start position:0% again I don't think you'll see it on the 12:45:44.700 --> 12:45:47.450 align:start position:0% again I don't think you'll see it on the network<12:45:44.756> plus<12:45:45.060> exam 12:45:47.450 --> 12:45:47.460 align:start position:0% network plus exam 12:45:47.460 --> 12:45:49.310 align:start position:0% network plus exam finally<12:45:48.060> I<12:45:48.360> mentioned<12:45:48.660> that<12:45:48.776> there<12:45:49.020> were<12:45:49.140> some 12:45:49.310 --> 12:45:49.320 align:start position:0% finally I mentioned that there were some 12:45:49.320 --> 12:45:51.766 align:start position:0% finally I mentioned that there were some important<12:45:49.740> terms<12:45:50.160> we<12:45:50.520> had<12:45:50.700> to<12:45:50.880> mention<12:45:51.116> when 12:45:51.766 --> 12:45:51.776 align:start position:0% important terms we had to mention when 12:45:51.776 --> 12:45:54.406 align:start position:0% important terms we had to mention when we<12:45:52.020> talk<12:45:52.200> about<12:45:52.380> routing<12:45:52.980> the<12:45:53.756> first<12:45:53.880> is<12:45:54.116> the 12:45:54.406 --> 12:45:54.416 align:start position:0% we talk about routing the first is the 12:45:54.416 --> 12:45:58.070 align:start position:0% we talk about routing the first is the hop<12:45:54.596> count<12:45:54.900> this<12:45:55.680> is<12:45:55.800> the<12:45:56.040> number<12:45:56.220> of<12:45:56.580> hops<12:45:57.480> it 12:45:58.070 --> 12:45:58.080 align:start position:0% hop count this is the number of hops it 12:45:58.080 --> 12:46:00.530 align:start position:0% hop count this is the number of hops it takes<12:45:58.256> to<12:45:58.616> reach<12:45:58.980> a<12:45:59.276> connection<12:45:59.400> or<12:46:00.060> before<12:46:00.240> an 12:46:00.530 --> 12:46:00.540 align:start position:0% takes to reach a connection or before an 12:46:00.540 --> 12:46:02.570 align:start position:0% takes to reach a connection or before an appropriate<12:46:00.960> connection<12:46:01.200> is<12:46:01.616> made<12:46:01.860> if<12:46:02.460> you 12:46:02.570 --> 12:46:02.580 align:start position:0% appropriate connection is made if you 12:46:02.580 --> 12:46:04.490 align:start position:0% appropriate connection is made if you remember<12:46:02.700> when<12:46:03.000> we<12:46:03.180> used<12:46:03.360> the<12:46:03.776> trace<12:46:04.140> route 12:46:04.490 --> 12:46:04.500 align:start position:0% remember when we used the trace route 12:46:04.500 --> 12:46:05.630 align:start position:0% remember when we used the trace route command 12:46:05.630 --> 12:46:05.640 align:start position:0% command 12:46:05.640 --> 12:46:08.510 align:start position:0% command remember<12:46:05.880> that<12:46:06.300> was<12:46:06.480> trace<12:46:07.140> route<12:46:07.400> it<12:46:08.400> went 12:46:08.510 --> 12:46:08.520 align:start position:0% remember that was trace route it went 12:46:08.520 --> 12:46:10.310 align:start position:0% remember that was trace route it went through<12:46:08.700> a<12:46:08.936> number<12:46:09.060> of<12:46:09.240> hops<12:46:09.720> or<12:46:09.900> a<12:46:10.020> number<12:46:10.140> of 12:46:10.310 --> 12:46:10.320 align:start position:0% through a number of hops or a number of 12:46:10.320 --> 12:46:12.650 align:start position:0% through a number of hops or a number of routers<12:46:10.860> until<12:46:11.460> it<12:46:11.700> got<12:46:11.880> from<12:46:12.180> our<12:46:12.416> computer 12:46:12.650 --> 12:46:12.660 align:start position:0% routers until it got from our computer 12:46:12.660 --> 12:46:15.830 align:start position:0% routers until it got from our computer to<12:46:13.436> for<12:46:13.800> instance<12:46:13.980> Googles<12:46:14.580> so<12:46:15.240> if<12:46:15.660> our 12:46:15.830 --> 12:46:15.840 align:start position:0% to for instance Googles so if our 12:46:15.840 --> 12:46:17.810 align:start position:0% to for instance Googles so if our computer<12:46:16.080> and<12:46:16.860> the<12:46:17.096> destination<12:46:17.460> computer 12:46:17.810 --> 12:46:17.820 align:start position:0% computer and the destination computer 12:46:17.820 --> 12:46:21.170 align:start position:0% computer and the destination computer are<12:46:18.596> represented<12:46:19.200> by<12:46:19.616> these<12:46:19.860> two<12:46:19.980> circles<12:46:20.400> and 12:46:21.170 --> 12:46:21.180 align:start position:0% are represented by these two circles and 12:46:21.180 --> 12:46:24.586 align:start position:0% are represented by these two circles and let's<12:46:21.480> say<12:46:21.720> we<12:46:22.560> have<12:46:22.740> our<12:46:23.040> internal<12:46:23.460> router<12:46:23.880> so 12:46:24.586 --> 12:46:24.596 align:start position:0% let's say we have our internal router so 12:46:24.596 --> 12:46:29.830 align:start position:0% let's say we have our internal router so for<12:46:24.840> instance<12:46:25.080> perhaps<12:46:25.560> we<12:46:25.800> are<12:46:25.980> in<12:46:26.160> a 12:46:29.830 --> 12:46:29.840 align:start position:0% 12:46:29.840 --> 12:46:32.266 align:start position:0% 10.0.0.xnetwork<12:46:30.840> and<12:46:31.680> then<12:46:31.800> they're<12:46:32.096> on 12:46:32.266 --> 12:46:32.276 align:start position:0% 10.0.0.xnetwork and then they're on 12:46:32.276 --> 12:46:35.210 align:start position:0% 10.0.0.xnetwork and then they're on their<12:46:32.400> own<12:46:32.520> network<12:46:32.756> as<12:46:33.116> well 12:46:35.210 --> 12:46:35.220 align:start position:0% their own network as well 12:46:35.220 --> 12:46:44.530 align:start position:0% their own network as well let's<12:46:35.880> say<12:46:36.060> that<12:46:36.360> this<12:46:36.540> is<12:46:36.840> a<12:46:37.200> for<12:46:38.040> instance<12:46:38.340> uh 12:46:44.530 --> 12:46:44.540 align:start position:0% 12:46:44.540 --> 12:46:46.850 align:start position:0% 124.68.24.3<12:46:45.540> Network 12:46:46.850 --> 12:46:46.860 align:start position:0% 124.68.24.3 Network 12:46:46.860 --> 12:46:49.790 align:start position:0% 124.68.24.3 Network now<12:46:47.520> we<12:46:47.936> need<12:46:48.060> to<12:46:48.240> get<12:46:48.360> from<12:46:48.660> hours<12:46:49.020> to<12:46:49.380> theirs 12:46:49.790 --> 12:46:49.800 align:start position:0% now we need to get from hours to theirs 12:46:49.800 --> 12:46:52.730 align:start position:0% now we need to get from hours to theirs and<12:46:50.700> so<12:46:50.936> let's<12:46:51.360> say<12:46:51.540> there<12:46:52.256> are<12:46:52.320> a<12:46:52.436> number<12:46:52.560> of 12:46:52.730 --> 12:46:52.740 align:start position:0% and so let's say there are a number of 12:46:52.740 --> 12:46:54.530 align:start position:0% and so let's say there are a number of different<12:46:52.916> routers<12:46:53.400> in<12:46:53.580> between<12:46:53.700> well<12:46:54.416> in 12:46:54.530 --> 12:46:54.540 align:start position:0% different routers in between well in 12:46:54.540 --> 12:46:57.890 align:start position:0% different routers in between well in this<12:46:54.720> case<12:46:54.840> we<12:46:55.080> have<12:46:55.200> one<12:46:55.616> two<12:46:56.400> three<12:46:57.240> four 12:46:57.890 --> 12:46:57.900 align:start position:0% this case we have one two three four 12:46:57.900 --> 12:47:01.490 align:start position:0% this case we have one two three four five<12:46:58.616> six<12:46:59.220> hops<12:46:59.756> between<12:47:00.300> us<12:47:00.776> and<12:47:01.320> the 12:47:01.490 --> 12:47:01.500 align:start position:0% five six hops between us and the 12:47:01.500 --> 12:47:02.810 align:start position:0% five six hops between us and the destination 12:47:02.810 --> 12:47:02.820 align:start position:0% destination 12:47:02.820 --> 12:47:05.266 align:start position:0% destination so<12:47:03.480> if<12:47:03.840> there<12:47:04.080> are<12:47:04.200> an<12:47:04.380> infinite<12:47:04.800> number<12:47:05.040> of 12:47:05.266 --> 12:47:05.276 align:start position:0% so if there are an infinite number of 12:47:05.276 --> 12:47:07.970 align:start position:0% so if there are an infinite number of hops<12:47:05.756> that<12:47:06.540> means<12:47:06.840> that<12:47:07.140> the<12:47:07.320> destination<12:47:07.680> is 12:47:07.970 --> 12:47:07.980 align:start position:0% hops that means that the destination is 12:47:07.980 --> 12:47:10.310 align:start position:0% hops that means that the destination is unreachable<12:47:08.520> or<12:47:09.416> that<12:47:09.776> for<12:47:10.020> some<12:47:10.140> reason 12:47:10.310 --> 12:47:10.320 align:start position:0% unreachable or that for some reason 12:47:10.320 --> 12:47:12.406 align:start position:0% unreachable or that for some reason we're<12:47:10.616> getting<12:47:10.860> caught<12:47:11.160> into<12:47:11.640> some<12:47:12.060> sort<12:47:12.300> of 12:47:12.406 --> 12:47:12.416 align:start position:0% we're getting caught into some sort of 12:47:12.416 --> 12:47:13.790 align:start position:0% we're getting caught into some sort of loop 12:47:13.790 --> 12:47:13.800 align:start position:0% loop 12:47:13.800 --> 12:47:17.210 align:start position:0% loop so<12:47:14.400> the<12:47:14.520> Hops<12:47:14.880> keep<12:47:15.060> coming<12:47:15.300> back<12:47:15.720> to<12:47:15.960> itself 12:47:17.210 --> 12:47:17.220 align:start position:0% so the Hops keep coming back to itself 12:47:17.220 --> 12:47:18.830 align:start position:0% so the Hops keep coming back to itself one<12:47:17.700> another<12:47:17.880> way<12:47:18.116> that<12:47:18.300> this<12:47:18.416> can<12:47:18.540> you<12:47:18.776> can 12:47:18.830 --> 12:47:18.840 align:start position:0% one another way that this can you can 12:47:18.840 --> 12:47:21.310 align:start position:0% one another way that this can you can see<12:47:18.960> this<12:47:19.140> as<12:47:19.380> I<12:47:19.560> erase<12:47:19.800> this<12:47:20.040> is<12:47:20.640> for<12:47:21.000> instance 12:47:21.310 --> 12:47:21.320 align:start position:0% see this as I erase this is for instance 12:47:21.320 --> 12:47:25.190 align:start position:0% see this as I erase this is for instance we<12:47:22.320> have 12:47:25.190 --> 12:47:25.200 align:start position:0% 12:47:25.200 --> 12:47:27.586 align:start position:0% A<12:47:25.560> system<12:47:25.740> that<12:47:26.096> looks<12:47:26.400> something<12:47:26.580> like 12:47:27.586 --> 12:47:27.596 align:start position:0% A system that looks something like 12:47:27.596 --> 12:47:31.130 align:start position:0% A system that looks something like this<12:47:28.140> and<12:47:28.740> these<12:47:28.980> are<12:47:29.096> each<12:47:29.220> routers 12:47:31.130 --> 12:47:31.140 align:start position:0% this and these are each routers 12:47:31.140 --> 12:47:32.926 align:start position:0% this and these are each routers so<12:47:31.500> what<12:47:31.616> might<12:47:31.800> happen 12:47:32.926 --> 12:47:32.936 align:start position:0% so what might happen 12:47:32.936 --> 12:47:35.926 align:start position:0% so what might happen as<12:47:33.416> I<12:47:33.720> draw<12:47:34.140> out<12:47:34.320> all<12:47:34.436> the<12:47:34.560> connections 12:47:35.926 --> 12:47:35.936 align:start position:0% as I draw out all the connections 12:47:35.936 --> 12:47:39.586 align:start position:0% as I draw out all the connections is<12:47:36.480> the<12:47:36.776> route<12:47:36.960> might<12:47:37.256> go<12:47:37.500> from<12:47:37.800> here<12:47:38.580> one<12:47:39.300> hop 12:47:39.586 --> 12:47:39.596 align:start position:0% is the route might go from here one hop 12:47:39.596 --> 12:47:42.170 align:start position:0% is the route might go from here one hop to<12:47:40.020> here<12:47:40.256> and<12:47:41.096> then<12:47:41.160> instead<12:47:41.460> of<12:47:41.580> going<12:47:41.756> to<12:47:42.000> the 12:47:42.170 --> 12:47:42.180 align:start position:0% to here and then instead of going to the 12:47:42.180 --> 12:47:44.870 align:start position:0% to here and then instead of going to the destination<12:47:42.916> it<12:47:43.916> simply<12:47:44.160> goes<12:47:44.460> like<12:47:44.640> this 12:47:44.870 --> 12:47:44.880 align:start position:0% destination it simply goes like this 12:47:44.880 --> 12:47:46.490 align:start position:0% destination it simply goes like this because 12:47:46.490 --> 12:47:46.500 align:start position:0% because 12:47:46.500 --> 12:47:49.850 align:start position:0% because this<12:47:47.160> could<12:47:47.340> be<12:47:47.520> a<12:47:47.936> valid<12:47:48.300> way<12:47:48.540> of<12:47:49.436> getting<12:47:49.616> to 12:47:49.850 --> 12:47:49.860 align:start position:0% this could be a valid way of getting to 12:47:49.860 --> 12:47:52.606 align:start position:0% this could be a valid way of getting to the<12:47:49.980> router<12:47:50.276> right<12:47:50.520> we<12:47:51.116> could<12:47:51.240> hop<12:47:51.480> here<12:47:51.776> and 12:47:52.606 --> 12:47:52.616 align:start position:0% the router right we could hop here and 12:47:52.616 --> 12:47:55.490 align:start position:0% the router right we could hop here and then<12:47:52.740> we<12:47:52.980> could<12:47:53.096> go<12:47:53.400> over<12:47:54.180> there<12:47:54.480> but<12:47:55.200> instead 12:47:55.490 --> 12:47:55.500 align:start position:0% then we could go over there but instead 12:47:55.500 --> 12:47:58.426 align:start position:0% then we could go over there but instead it<12:47:55.800> hops<12:47:56.220> and<12:47:57.000> then<12:47:57.116> this<12:47:57.596> one<12:47:57.720> sends<12:47:58.200> it<12:47:58.256> along 12:47:58.426 --> 12:47:58.436 align:start position:0% it hops and then this one sends it along 12:47:58.436 --> 12:48:02.150 align:start position:0% it hops and then this one sends it along this<12:47:59.096> route<12:47:59.276> so<12:48:00.240> we<12:48:00.416> move<12:48:00.596> here<12:48:00.900> and<12:48:01.740> basically 12:48:02.150 --> 12:48:02.160 align:start position:0% this route so we move here and basically 12:48:02.160 --> 12:48:04.426 align:start position:0% this route so we move here and basically we<12:48:02.400> create<12:48:02.640> a<12:48:02.880> loop<12:48:03.116> in<12:48:03.900> which<12:48:04.140> the 12:48:04.426 --> 12:48:04.436 align:start position:0% we create a loop in which the 12:48:04.436 --> 12:48:06.650 align:start position:0% we create a loop in which the destination<12:48:04.860> is<12:48:05.096> never<12:48:05.220> reachable<12:48:06.116> now<12:48:06.480> this 12:48:06.650 --> 12:48:06.660 align:start position:0% destination is never reachable now this 12:48:06.660 --> 12:48:09.650 align:start position:0% destination is never reachable now this could<12:48:06.776> be<12:48:06.960> because<12:48:07.200> of<12:48:07.616> some<12:48:07.860> sort<12:48:08.040> of<12:48:08.160> poor<12:48:08.820> uh 12:48:09.650 --> 12:48:09.660 align:start position:0% could be because of some sort of poor uh 12:48:09.660 --> 12:48:11.570 align:start position:0% could be because of some sort of poor uh routing<12:48:10.320> table<12:48:10.500> and<12:48:11.040> what<12:48:11.220> you<12:48:11.276> would<12:48:11.400> need<12:48:11.520> to 12:48:11.570 --> 12:48:11.580 align:start position:0% routing table and what you would need to 12:48:11.580 --> 12:48:13.010 align:start position:0% routing table and what you would need to do<12:48:11.700> is<12:48:11.936> basically<12:48:12.240> tell<12:48:12.480> one<12:48:12.776> of<12:48:12.840> these 12:48:13.010 --> 12:48:13.020 align:start position:0% do is basically tell one of these 12:48:13.020 --> 12:48:15.470 align:start position:0% do is basically tell one of these routers<12:48:13.436> that<12:48:13.680> the<12:48:13.916> destination<12:48:14.400> goes<12:48:15.360> over 12:48:15.470 --> 12:48:15.480 align:start position:0% routers that the destination goes over 12:48:15.480 --> 12:48:16.606 align:start position:0% routers that the destination goes over here 12:48:16.606 --> 12:48:16.616 align:start position:0% here 12:48:16.616 --> 12:48:19.130 align:start position:0% here the<12:48:17.096> next<12:48:17.220> term<12:48:17.460> is<12:48:18.060> What's<12:48:18.300> called<12:48:18.596> the<12:48:18.840> cost 12:48:19.130 --> 12:48:19.140 align:start position:0% the next term is What's called the cost 12:48:19.140 --> 12:48:22.310 align:start position:0% the next term is What's called the cost this<12:48:19.740> is<12:48:19.860> the<12:48:20.160> number<12:48:20.400> of<12:48:21.060> uh<12:48:21.776> or<12:48:21.900> these<12:48:22.200> are 12:48:22.310 --> 12:48:22.320 align:start position:0% this is the number of uh or these are 12:48:22.320 --> 12:48:24.050 align:start position:0% this is the number of uh or these are the<12:48:22.436> numbers<12:48:22.616> rather<12:48:23.220> that<12:48:23.520> are<12:48:23.640> associated 12:48:24.050 --> 12:48:24.060 align:start position:0% the numbers rather that are associated 12:48:24.060 --> 12:48:26.950 align:start position:0% the numbers rather that are associated with<12:48:24.360> traveling<12:48:24.840> from<12:48:25.436> point<12:48:25.680> A<12:48:25.980> to<12:48:26.400> point<12:48:26.580> B 12:48:26.950 --> 12:48:26.960 align:start position:0% with traveling from point A to point B 12:48:26.960 --> 12:48:29.870 align:start position:0% with traveling from point A to point B generally<12:48:27.960> this<12:48:28.320> means<12:48:28.680> Hops<12:48:29.340> and<12:48:29.580> several 12:48:29.870 --> 12:48:29.880 align:start position:0% generally this means Hops and several 12:48:29.880 --> 12:48:32.630 align:start position:0% generally this means Hops and several different<12:48:30.060> links<12:48:30.540> along<12:48:30.776> the<12:48:31.020> path<12:48:31.460> the<12:48:32.460> lower 12:48:32.630 --> 12:48:32.640 align:start position:0% different links along the path the lower 12:48:32.640 --> 12:48:34.670 align:start position:0% different links along the path the lower number<12:48:33.116> of<12:48:33.416> of 12:48:34.670 --> 12:48:34.680 align:start position:0% number of of 12:48:34.680 --> 12:48:38.570 align:start position:0% number of of hops<12:48:35.640> the<12:48:36.480> better<12:48:36.596> we<12:48:36.960> are<12:48:37.200> so<12:48:37.860> the<12:48:38.040> cost<12:48:38.276> would 12:48:38.570 --> 12:48:38.580 align:start position:0% hops the better we are so the cost would 12:48:38.580 --> 12:48:41.266 align:start position:0% hops the better we are so the cost would be<12:48:38.756> how<12:48:39.240> many<12:48:39.416> hops<12:48:40.080> total<12:48:40.500> we<12:48:40.860> need<12:48:41.040> to<12:48:41.160> travel 12:48:41.266 --> 12:48:41.276 align:start position:0% be how many hops total we need to travel 12:48:41.276 --> 12:48:43.426 align:start position:0% be how many hops total we need to travel from<12:48:41.580> point<12:48:41.700> A<12:48:41.880> to<12:48:42.060> point<12:48:42.240> B<12:48:42.436> generally 12:48:43.426 --> 12:48:43.436 align:start position:0% from point A to point B generally 12:48:43.436 --> 12:48:45.890 align:start position:0% from point A to point B generally speaking<12:48:44.040> we're<12:48:44.580> going<12:48:44.820> to<12:48:45.060> look<12:48:45.240> at<12:48:45.720> the 12:48:45.890 --> 12:48:45.900 align:start position:0% speaking we're going to look at the 12:48:45.900 --> 12:48:49.246 align:start position:0% speaking we're going to look at the lowest<12:48:46.256> number<12:48:46.616> of<12:48:47.460> hops<12:48:47.880> possible<12:48:48.300> but<12:48:49.020> there 12:48:49.246 --> 12:48:49.256 align:start position:0% lowest number of hops possible but there 12:48:49.256 --> 12:48:52.070 align:start position:0% lowest number of hops possible but there are<12:48:49.436> some<12:48:49.800> instances<12:48:50.400> in<12:48:51.180> which<12:48:51.416> we<12:48:51.900> could 12:48:52.070 --> 12:48:52.080 align:start position:0% are some instances in which we could 12:48:52.080 --> 12:48:55.970 align:start position:0% are some instances in which we could want<12:48:52.320> to<12:48:52.500> go<12:48:52.700> more<12:48:53.700> hops<12:48:54.240> or<12:48:55.080> have<12:48:55.320> a<12:48:55.560> higher 12:48:55.970 --> 12:48:55.980 align:start position:0% want to go more hops or have a higher 12:48:55.980 --> 12:48:59.810 align:start position:0% want to go more hops or have a higher cost<12:48:56.596> through<12:48:57.596> hops<12:48:58.140> in<12:48:59.040> order<12:48:59.160> to<12:48:59.400> save<12:48:59.580> on 12:48:59.810 --> 12:48:59.820 align:start position:0% cost through hops in order to save on 12:48:59.820 --> 12:49:01.670 align:start position:0% cost through hops in order to save on something<12:49:00.000> else<12:49:00.240> for<12:49:00.540> instance<12:49:00.776> latency 12:49:01.670 --> 12:49:01.680 align:start position:0% something else for instance latency 12:49:01.680 --> 12:49:03.890 align:start position:0% something else for instance latency latency<12:49:02.640> is<12:49:02.880> the<12:49:03.000> time<12:49:03.180> it<12:49:03.416> takes<12:49:03.540> from<12:49:03.776> a 12:49:03.890 --> 12:49:03.900 align:start position:0% latency is the time it takes from a 12:49:03.900 --> 12:49:05.870 align:start position:0% latency is the time it takes from a packet<12:49:04.200> to<12:49:04.320> go<12:49:04.500> from<12:49:04.740> one<12:49:04.980> location<12:49:05.220> to 12:49:05.870 --> 12:49:05.880 align:start position:0% packet to go from one location to 12:49:05.880 --> 12:49:07.906 align:start position:0% packet to go from one location to another<12:49:06.060> so<12:49:06.960> to<12:49:07.200> give<12:49:07.320> you<12:49:07.436> an<12:49:07.500> example<12:49:07.740> of 12:49:07.906 --> 12:49:07.916 align:start position:0% another so to give you an example of 12:49:07.916 --> 12:49:09.890 align:start position:0% another so to give you an example of what<12:49:08.040> I<12:49:08.160> was<12:49:08.276> just<12:49:08.340> talking<12:49:08.520> about<12:49:08.900> sometimes 12:49:09.890 --> 12:49:09.900 align:start position:0% what I was just talking about sometimes 12:49:09.900 --> 12:49:12.350 align:start position:0% what I was just talking about sometimes we<12:49:10.560> go<12:49:10.740> route<12:49:11.040> specific 12:49:12.350 --> 12:49:12.360 align:start position:0% we go route specific 12:49:12.360 --> 12:49:14.690 align:start position:0% we go route specific which<12:49:12.900> means<12:49:13.256> that<12:49:13.560> it's<12:49:14.220> going<12:49:14.400> to<12:49:14.520> choose 12:49:14.690 --> 12:49:14.700 align:start position:0% which means that it's going to choose 12:49:14.700 --> 12:49:19.426 align:start position:0% which means that it's going to choose this<12:49:15.000> route<12:49:15.180> because<12:49:15.596> this<12:49:16.380> is<12:49:16.500> only<12:49:16.800> two<12:49:17.580> hops 12:49:19.426 --> 12:49:19.436 align:start position:0% this route because this is only two hops 12:49:19.436 --> 12:49:21.586 align:start position:0% this route because this is only two hops however 12:49:21.586 --> 12:49:21.596 align:start position:0% however 12:49:21.596 --> 12:49:27.950 align:start position:0% however let's<12:49:22.200> say 12:49:27.950 --> 12:49:27.960 align:start position:0% 12:49:27.960 --> 12:49:29.810 align:start position:0% let's<12:49:28.380> say<12:49:28.560> that<12:49:28.740> instead<12:49:29.096> of<12:49:29.160> traveling<12:49:29.580> this 12:49:29.810 --> 12:49:29.820 align:start position:0% let's say that instead of traveling this 12:49:29.820 --> 12:49:31.790 align:start position:0% let's say that instead of traveling this let's<12:49:30.300> say<12:49:30.480> this<12:49:30.720> was<12:49:30.900> a<12:49:31.140> dial-up<12:49:31.560> connection 12:49:31.790 --> 12:49:31.800 align:start position:0% let's say this was a dial-up connection 12:49:31.800 --> 12:49:33.406 align:start position:0% let's say this was a dial-up connection right<12:49:32.220> here 12:49:33.406 --> 12:49:33.416 align:start position:0% right here 12:49:33.416 --> 12:49:37.550 align:start position:0% right here and<12:49:33.960> this<12:49:34.140> was<12:49:34.916> a<12:49:35.160> broadband<12:49:35.580> connection 12:49:37.550 --> 12:49:37.560 align:start position:0% and this was a broadband connection 12:49:37.560 --> 12:49:39.530 align:start position:0% and this was a broadband connection well<12:49:38.040> obviously 12:49:39.530 --> 12:49:39.540 align:start position:0% well obviously 12:49:39.540 --> 12:49:42.650 align:start position:0% well obviously even<12:49:40.080> though<12:49:40.256> we<12:49:40.500> have<12:49:40.616> to<12:49:40.740> go<12:49:40.916> one<12:49:41.340> two<12:49:41.880> three 12:49:42.650 --> 12:49:42.660 align:start position:0% even though we have to go one two three 12:49:42.660 --> 12:49:45.406 align:start position:0% even though we have to go one two three four<12:49:43.320> hops<12:49:43.860> as<12:49:44.220> opposed<12:49:44.640> to<12:49:44.640> three<12:49:44.936> on<12:49:45.240> this 12:49:45.406 --> 12:49:45.416 align:start position:0% four hops as opposed to three on this 12:49:45.416 --> 12:49:46.426 align:start position:0% four hops as opposed to three on this one 12:49:46.426 --> 12:49:46.436 align:start position:0% one 12:49:46.436 --> 12:49:48.650 align:start position:0% one we<12:49:46.980> would<12:49:47.096> want<12:49:47.340> to<12:49:47.460> take<12:49:47.640> the<12:49:48.000> four<12:49:48.180> hops 12:49:48.650 --> 12:49:48.660 align:start position:0% we would want to take the four hops 12:49:48.660 --> 12:49:50.926 align:start position:0% we would want to take the four hops because<12:49:49.020> the<12:49:49.740> latency<12:49:50.096> is<12:49:50.400> going<12:49:50.520> to<12:49:50.640> be<12:49:50.756> less 12:49:50.926 --> 12:49:50.936 align:start position:0% because the latency is going to be less 12:49:50.936 --> 12:49:53.450 align:start position:0% because the latency is going to be less and<12:49:51.776> so<12:49:51.900> the<12:49:52.256> cost<12:49:52.436> would<12:49:52.740> be<12:49:52.860> determined 12:49:53.450 --> 12:49:53.460 align:start position:0% and so the cost would be determined 12:49:53.460 --> 12:49:56.266 align:start position:0% and so the cost would be determined based<12:49:54.360> not<12:49:54.480> only<12:49:54.596> in<12:49:54.776> hops<12:49:55.200> but<12:49:55.380> on<12:49:55.560> latency<12:49:55.916> as 12:49:56.266 --> 12:49:56.276 align:start position:0% based not only in hops but on latency as 12:49:56.276 --> 12:49:57.650 align:start position:0% based not only in hops but on latency as well 12:49:57.650 --> 12:49:57.660 align:start position:0% well 12:49:57.660 --> 12:50:01.190 align:start position:0% well now<12:49:58.080> convergence<12:49:59.060> is<12:50:00.060> the<12:50:00.540> process<12:50:00.900> of 12:50:01.190 --> 12:50:01.200 align:start position:0% now convergence is the process of 12:50:01.200 --> 12:50:03.230 align:start position:0% now convergence is the process of routers<12:50:01.680> discovering<12:50:02.460> the<12:50:03.060> network 12:50:03.230 --> 12:50:03.240 align:start position:0% routers discovering the network 12:50:03.240 --> 12:50:05.870 align:start position:0% routers discovering the network structure<12:50:03.776> has<12:50:04.080> changed<12:50:04.560> in<12:50:05.340> this<12:50:05.460> way<12:50:05.580> it 12:50:05.870 --> 12:50:05.880 align:start position:0% structure has changed in this way it 12:50:05.880 --> 12:50:07.550 align:start position:0% structure has changed in this way it updates<12:50:06.240> the<12:50:06.540> routing<12:50:06.900> tables<12:50:07.256> to<12:50:07.436> the 12:50:07.550 --> 12:50:07.560 align:start position:0% updates the routing tables to the 12:50:07.560 --> 12:50:09.290 align:start position:0% updates the routing tables to the knowledge<12:50:07.800> of<12:50:07.916> the<12:50:08.040> networks<12:50:08.520> so<12:50:09.000> for 12:50:09.290 --> 12:50:09.300 align:start position:0% knowledge of the networks so for 12:50:09.300 --> 12:50:11.690 align:start position:0% knowledge of the networks so for instance 12:50:11.690 --> 12:50:11.700 align:start position:0% 12:50:11.700 --> 12:50:14.450 align:start position:0% if we<12:50:12.240> have<12:50:12.480> two<12:50:12.840> different<12:50:13.080> paths<12:50:13.740> that<12:50:14.340> a 12:50:14.450 --> 12:50:14.460 align:start position:0% if we have two different paths that a 12:50:14.460 --> 12:50:16.370 align:start position:0% if we have two different paths that a route<12:50:14.640> could<12:50:14.936> take 12:50:16.370 --> 12:50:16.380 align:start position:0% route could take 12:50:16.380 --> 12:50:18.586 align:start position:0% route could take it<12:50:16.860> could<12:50:16.980> either<12:50:17.096> go 12:50:18.586 --> 12:50:18.596 align:start position:0% it could either go 12:50:18.596 --> 12:50:22.310 align:start position:0% it could either go like<12:50:19.140> this<12:50:19.860> or 12:50:22.310 --> 12:50:22.320 align:start position:0% like this or 12:50:22.320 --> 12:50:25.606 align:start position:0% like this or like<12:50:22.980> this<12:50:23.160> we<12:50:24.000> would<12:50:24.180> want<12:50:24.360> to<12:50:24.540> know<12:50:24.720> if<12:50:25.500> one 12:50:25.606 --> 12:50:25.616 align:start position:0% like this we would want to know if one 12:50:25.616 --> 12:50:28.130 align:start position:0% like this we would want to know if one of<12:50:25.800> the<12:50:25.860> connections<12:50:26.276> had<12:50:26.520> been<12:50:26.640> severed<12:50:27.480> and 12:50:28.130 --> 12:50:28.140 align:start position:0% of the connections had been severed and 12:50:28.140 --> 12:50:30.830 align:start position:0% of the connections had been severed and then<12:50:28.320> this<12:50:29.276> routing<12:50:29.640> table<12:50:29.820> would<12:50:30.180> be<12:50:30.300> updated 12:50:30.830 --> 12:50:30.840 align:start position:0% then this routing table would be updated 12:50:30.840 --> 12:50:34.310 align:start position:0% then this routing table would be updated to<12:50:31.800> know<12:50:31.980> don't<12:50:32.400> go<12:50:32.640> on<12:50:32.820> this<12:50:33.060> route<12:50:33.320> instead 12:50:34.310 --> 12:50:34.320 align:start position:0% to know don't go on this route instead 12:50:34.320 --> 12:50:35.926 align:start position:0% to know don't go on this route instead go<12:50:34.680> on<12:50:34.860> that<12:50:35.040> route 12:50:35.926 --> 12:50:35.936 align:start position:0% go on that route 12:50:35.936 --> 12:50:38.390 align:start position:0% go on that route the<12:50:36.180> process<12:50:36.596> of<12:50:36.776> this<12:50:37.020> happening 12:50:38.390 --> 12:50:38.400 align:start position:0% the process of this happening 12:50:38.400 --> 12:50:41.630 align:start position:0% the process of this happening is<12:50:38.880> called<12:50:39.116> convergence 12:50:41.630 --> 12:50:41.640 align:start position:0% is called convergence 12:50:41.640 --> 12:50:44.450 align:start position:0% is called convergence so<12:50:42.180> although<12:50:42.776> this<12:50:43.200> module<12:50:44.040> might<12:50:44.220> have<12:50:44.340> been 12:50:44.450 --> 12:50:44.460 align:start position:0% so although this module might have been 12:50:44.460 --> 12:50:46.970 align:start position:0% so although this module might have been short<12:50:44.820> and<12:50:45.240> a<12:50:45.416> brief<12:50:45.660> overview<12:50:46.020> of<12:50:46.200> routing<12:50:46.560> we 12:50:46.970 --> 12:50:46.980 align:start position:0% short and a brief overview of routing we 12:50:46.980 --> 12:50:48.586 align:start position:0% short and a brief overview of routing we went<12:50:47.096> over<12:50:47.276> some<12:50:47.580> key<12:50:47.820> things<12:50:48.060> first<12:50:48.416> of<12:50:48.540> all 12:50:48.586 --> 12:50:48.596 align:start position:0% went over some key things first of all 12:50:48.596 --> 12:50:50.870 align:start position:0% went over some key things first of all we<12:50:48.776> talked<12:50:49.080> about<12:50:49.200> a<12:50:49.740> router<12:50:50.096> this<12:50:50.520> is<12:50:50.640> the 12:50:50.870 --> 12:50:50.880 align:start position:0% we talked about a router this is the 12:50:50.880 --> 12:50:52.606 align:start position:0% we talked about a router this is the device<12:50:51.060> that<12:50:51.776> generally<12:50:52.020> allows<12:50:52.320> us<12:50:52.436> to 12:50:52.606 --> 12:50:52.616 align:start position:0% device that generally allows us to 12:50:52.616 --> 12:50:56.150 align:start position:0% device that generally allows us to connect<12:50:52.740> our<12:50:53.220> Lan<12:50:53.580> out<12:50:54.360> to<12:50:54.596> a<12:50:55.200> Wan 12:50:56.150 --> 12:50:56.160 align:start position:0% connect our Lan out to a Wan 12:50:56.160 --> 12:50:59.266 align:start position:0% connect our Lan out to a Wan it<12:50:56.640> does<12:50:56.820> this<12:50:57.000> by<12:50:57.240> operating<12:50:57.660> on<12:50:58.020> layer<12:50:58.436> 3<12:50:58.680> of 12:50:59.266 --> 12:50:59.276 align:start position:0% it does this by operating on layer 3 of 12:50:59.276 --> 12:51:02.330 align:start position:0% it does this by operating on layer 3 of The<12:50:59.400> OSI<12:50:59.880> model<12:51:00.116> which<12:51:00.960> again<12:51:01.200> is<12:51:01.800> responsible 12:51:02.330 --> 12:51:02.340 align:start position:0% The OSI model which again is responsible 12:51:02.340 --> 12:51:05.746 align:start position:0% The OSI model which again is responsible for<12:51:02.820> IP<12:51:03.240> addresses<12:51:03.840> as<12:51:04.560> opposed<12:51:04.916> to<12:51:04.980> switches 12:51:05.746 --> 12:51:05.756 align:start position:0% for IP addresses as opposed to switches 12:51:05.756 --> 12:51:07.730 align:start position:0% for IP addresses as opposed to switches which<12:51:06.300> work<12:51:06.540> with<12:51:06.776> Mac<12:51:07.020> addresses<12:51:07.500> and 12:51:07.730 --> 12:51:07.740 align:start position:0% which work with Mac addresses and 12:51:07.740 --> 12:51:09.890 align:start position:0% which work with Mac addresses and therefore<12:51:07.916> operate<12:51:08.340> on<12:51:08.520> layer<12:51:08.756> 2.<12:51:09.116> we<12:51:09.660> also 12:51:09.890 --> 12:51:09.900 align:start position:0% therefore operate on layer 2. we also 12:51:09.900 --> 12:51:12.586 align:start position:0% therefore operate on layer 2. we also talked<12:51:10.140> about<12:51:10.200> how<12:51:10.740> a<12:51:10.916> router<12:51:11.276> functions<12:51:11.756> in 12:51:12.586 --> 12:51:12.596 align:start position:0% talked about how a router functions in 12:51:12.596 --> 12:51:14.570 align:start position:0% talked about how a router functions in this<12:51:12.720> case<12:51:12.960> we<12:51:13.560> talked<12:51:13.860> about<12:51:13.916> the<12:51:14.160> fact<12:51:14.340> that 12:51:14.570 --> 12:51:14.580 align:start position:0% this case we talked about the fact that 12:51:14.580 --> 12:51:16.970 align:start position:0% this case we talked about the fact that a<12:51:14.700> router<12:51:15.060> has<12:51:15.240> what's<12:51:15.540> called<12:51:15.840> a<12:51:16.560> routing 12:51:16.970 --> 12:51:16.980 align:start position:0% a router has what's called a routing 12:51:16.980 --> 12:51:18.766 align:start position:0% a router has what's called a routing table 12:51:18.766 --> 12:51:18.776 align:start position:0% table 12:51:18.776 --> 12:51:21.106 align:start position:0% table which<12:51:19.256> can<12:51:19.436> sometimes<12:51:19.800> be<12:51:20.040> called<12:51:20.276> an<12:51:20.756> ARP 12:51:21.106 --> 12:51:21.116 align:start position:0% which can sometimes be called an ARP 12:51:21.116 --> 12:51:22.670 align:start position:0% which can sometimes be called an ARP table 12:51:22.670 --> 12:51:22.680 align:start position:0% table 12:51:22.680 --> 12:51:24.370 align:start position:0% table the<12:51:23.340> ARP<12:51:23.640> table 12:51:24.370 --> 12:51:24.380 align:start position:0% the ARP table 12:51:24.380 --> 12:51:29.330 align:start position:0% the ARP table tells<12:51:25.380> it<12:51:25.500> where<12:51:25.980> an<12:51:26.220> IP<12:51:26.460> address<12:51:26.900> goes<12:51:28.220> to<12:51:29.220> get 12:51:29.330 --> 12:51:29.340 align:start position:0% tells it where an IP address goes to get 12:51:29.340 --> 12:51:31.670 align:start position:0% tells it where an IP address goes to get to<12:51:29.520> a<12:51:29.700> specific<12:51:29.936> place<12:51:30.180> so<12:51:30.480> it<12:51:30.596> Maps<12:51:31.020> basic<12:51:31.320> IPS 12:51:31.670 --> 12:51:31.680 align:start position:0% to a specific place so it Maps basic IPS 12:51:31.680 --> 12:51:33.766 align:start position:0% to a specific place so it Maps basic IPS to<12:51:31.980> Mac<12:51:32.096> addresses<12:51:32.640> and<12:51:33.240> then<12:51:33.416> the<12:51:33.540> routing 12:51:33.766 --> 12:51:33.776 align:start position:0% to Mac addresses and then the routing 12:51:33.776 --> 12:51:36.106 align:start position:0% to Mac addresses and then the routing table<12:51:33.960> would<12:51:34.200> say<12:51:34.436> how<12:51:34.916> many<12:51:35.096> routes<12:51:35.700> you<12:51:35.936> take 12:51:36.106 --> 12:51:36.116 align:start position:0% table would say how many routes you take 12:51:36.116 --> 12:51:39.950 align:start position:0% table would say how many routes you take to<12:51:36.480> get<12:51:36.660> to<12:51:37.020> a<12:51:37.800> specific<12:51:38.096> node<12:51:38.700> on<12:51:38.880> the<12:51:39.060> network 12:51:39.950 --> 12:51:39.960 align:start position:0% to get to a specific node on the network 12:51:39.960 --> 12:51:41.870 align:start position:0% to get to a specific node on the network we<12:51:40.380> also<12:51:40.616> looked<12:51:40.800> at<12:51:40.860> static<12:51:41.276> routing<12:51:41.640> which 12:51:41.870 --> 12:51:41.880 align:start position:0% we also looked at static routing which 12:51:41.880 --> 12:51:43.906 align:start position:0% we also looked at static routing which is<12:51:42.116> manually<12:51:42.596> updating<12:51:43.140> the<12:51:43.380> routing<12:51:43.740> table 12:51:43.906 --> 12:51:43.916 align:start position:0% is manually updating the routing table 12:51:43.916 --> 12:51:46.970 align:start position:0% is manually updating the routing table so<12:51:44.520> that<12:51:44.640> way<12:51:44.820> you<12:51:45.000> can<12:51:45.060> tell<12:51:45.300> it<12:51:45.480> where<12:51:45.720> to<12:51:45.840> go 12:51:46.970 --> 12:51:46.980 align:start position:0% so that way you can tell it where to go 12:51:46.980 --> 12:51:48.650 align:start position:0% so that way you can tell it where to go we<12:51:47.340> also<12:51:47.580> talked<12:51:47.756> about<12:51:47.820> some<12:51:48.060> key<12:51:48.300> terms 12:51:48.650 --> 12:51:48.660 align:start position:0% we also talked about some key terms 12:51:48.660 --> 12:51:51.050 align:start position:0% we also talked about some key terms including<12:51:49.080> hop<12:51:49.436> counts<12:51:50.040> which<12:51:50.520> would<12:51:50.640> be<12:51:50.820> like 12:51:51.050 --> 12:51:51.060 align:start position:0% including hop counts which would be like 12:51:51.060 --> 12:51:52.850 align:start position:0% including hop counts which would be like the<12:51:51.540> number<12:51:51.720> of<12:51:51.900> places<12:51:52.200> we're<12:51:52.500> going<12:51:52.616> to<12:51:52.740> go 12:51:52.850 --> 12:51:52.860 align:start position:0% the number of places we're going to go 12:51:52.860 --> 12:51:55.010 align:start position:0% the number of places we're going to go if<12:51:53.340> we're<12:51:53.460> going<12:51:53.580> to<12:51:53.700> take<12:51:53.880> a<12:51:54.060> trip<12:51:54.300> this<12:51:54.840> would 12:51:55.010 --> 12:51:55.020 align:start position:0% if we're going to take a trip this would 12:51:55.020 --> 12:51:58.730 align:start position:0% if we're going to take a trip this would be<12:51:55.140> for<12:51:55.436> instance<12:51:55.860> the<12:51:56.820> miles 12:51:58.730 --> 12:51:58.740 align:start position:0% be for instance the miles 12:51:58.740 --> 12:52:00.950 align:start position:0% be for instance the miles we<12:51:59.096> looked<12:51:59.340> at<12:51:59.400> the<12:51:59.640> cost<12:51:59.820> which<12:52:00.596> basically 12:52:00.950 --> 12:52:00.960 align:start position:0% we looked at the cost which basically 12:52:00.960 --> 12:52:02.630 align:start position:0% we looked at the cost which basically means<12:52:01.256> we're<12:52:01.436> going<12:52:01.616> to<12:52:01.680> take<12:52:01.860> several<12:52:02.340> things 12:52:02.630 --> 12:52:02.640 align:start position:0% means we're going to take several things 12:52:02.640 --> 12:52:05.926 align:start position:0% means we're going to take several things into<12:52:03.480> consideration<12:52:04.140> when<12:52:04.500> determining<12:52:05.096> our 12:52:05.926 --> 12:52:05.936 align:start position:0% into consideration when determining our 12:52:05.936 --> 12:52:07.130 align:start position:0% into consideration when determining our trip 12:52:07.130 --> 12:52:07.140 align:start position:0% trip 12:52:07.140 --> 12:52:11.870 align:start position:0% trip for<12:52:07.740> instance<12:52:08.040> if<12:52:08.936> one<12:52:09.240> has<12:52:09.660> a<12:52:09.960> highway 12:52:11.870 --> 12:52:11.880 align:start position:0% for instance if one has a highway 12:52:11.880 --> 12:52:13.970 align:start position:0% for instance if one has a highway whereas<12:52:12.596> the<12:52:12.720> other<12:52:12.900> are<12:52:13.320> a<12:52:13.500> bunch<12:52:13.616> of<12:52:13.740> local 12:52:13.970 --> 12:52:13.980 align:start position:0% whereas the other are a bunch of local 12:52:13.980 --> 12:52:17.630 align:start position:0% whereas the other are a bunch of local roads<12:52:14.640> with<12:52:15.416> stop<12:52:15.660> lights 12:52:17.630 --> 12:52:17.640 align:start position:0% roads with stop lights 12:52:17.640 --> 12:52:20.086 align:start position:0% roads with stop lights then<12:52:18.116> even<12:52:18.300> though<12:52:18.540> it<12:52:18.776> might<12:52:19.020> be<12:52:19.256> more<12:52:19.800> miles 12:52:20.086 --> 12:52:20.096 align:start position:0% then even though it might be more miles 12:52:20.096 --> 12:52:23.810 align:start position:0% then even though it might be more miles to<12:52:20.820> go<12:52:21.000> on<12:52:21.240> the<12:52:21.960> Highway<12:52:22.560> we're<12:52:23.400> going<12:52:23.580> to<12:52:23.700> go 12:52:23.810 --> 12:52:23.820 align:start position:0% to go on the Highway we're going to go 12:52:23.820 --> 12:52:25.246 align:start position:0% to go on the Highway we're going to go there<12:52:24.000> as<12:52:24.180> opposed<12:52:24.540> to<12:52:24.540> this<12:52:24.776> one<12:52:24.960> with<12:52:25.140> the 12:52:25.246 --> 12:52:25.256 align:start position:0% there as opposed to this one with the 12:52:25.256 --> 12:52:26.210 align:start position:0% there as opposed to this one with the stop<12:52:25.380> lights<12:52:25.560> because<12:52:25.800> we<12:52:25.980> know<12:52:26.096> we're 12:52:26.210 --> 12:52:26.220 align:start position:0% stop lights because we know we're 12:52:26.220 --> 12:52:27.830 align:start position:0% stop lights because we know we're getting<12:52:26.400> there<12:52:26.580> faster 12:52:27.830 --> 12:52:27.840 align:start position:0% getting there faster 12:52:27.840 --> 12:52:30.170 align:start position:0% getting there faster finally<12:52:28.320> convergence<12:52:28.980> is<12:52:29.340> keeping<12:52:29.756> all<12:52:30.000> these 12:52:30.170 --> 12:52:30.180 align:start position:0% finally convergence is keeping all these 12:52:30.180 --> 12:52:32.810 align:start position:0% finally convergence is keeping all these routing<12:52:30.596> tables<12:52:31.020> up<12:52:31.560> to<12:52:31.680> date 12:52:32.810 --> 12:52:32.820 align:start position:0% routing tables up to date 12:52:32.820 --> 12:52:35.210 align:start position:0% routing tables up to date that<12:52:33.300> way<12:52:33.480> we<12:52:33.776> know<12:52:34.020> which<12:52:34.500> route<12:52:34.740> is<12:52:34.980> the<12:52:35.096> most 12:52:35.210 --> 12:52:35.220 align:start position:0% that way we know which route is the most 12:52:35.220 --> 12:52:38.690 align:start position:0% that way we know which route is the most effective<12:52:35.640> at<12:52:35.820> any<12:52:35.936> one<12:52:36.180> time 12:52:38.690 --> 12:52:38.700 align:start position:0% 12:52:38.700 --> 12:52:40.370 align:start position:0% in<12:52:39.116> the<12:52:39.240> next<12:52:39.360> module<12:52:39.776> I'm<12:52:39.960> going<12:52:40.080> to<12:52:40.200> talk 12:52:40.370 --> 12:52:40.380 align:start position:0% in the next module I'm going to talk 12:52:40.380 --> 12:52:43.790 align:start position:0% in the next module I'm going to talk more<12:52:40.800> about<12:52:41.040> how<12:52:41.756> all<12:52:41.880> this<12:52:42.116> works<12:52:42.480> in<12:52:43.256> Dynamic 12:52:43.790 --> 12:52:43.800 align:start position:0% more about how all this works in Dynamic 12:52:43.800 --> 12:52:45.890 align:start position:0% more about how all this works in Dynamic routing<12:52:44.276> and<12:52:44.640> the<12:52:44.756> protocols<12:52:45.300> that<12:52:45.596> are 12:52:45.890 --> 12:52:45.900 align:start position:0% routing and the protocols that are 12:52:45.900 --> 12:52:50.720 align:start position:0% routing and the protocols that are involved<12:52:46.680> with<12:52:46.860> it 12:52:50.720 --> 12:52:50.730 align:start position:0% 12:52:50.730 --> 12:52:59.406 align:start position:0% [Music] 12:52:59.406 --> 12:52:59.416 align:start position:0% [Music] 12:52:59.416 --> 12:53:07.070 align:start position:0% [Music] thank<12:53:00.416> you 12:53:07.070 --> 12:53:07.080 align:start position:0% 12:53:07.080 --> 12:53:10.426 align:start position:0% welcome<12:53:07.560> to<12:53:07.860> module<12:53:08.276> 8<12:53:08.520> lesson<12:53:09.060> 3A<12:53:09.596> on<12:53:09.960> routing 12:53:10.426 --> 12:53:10.436 align:start position:0% welcome to module 8 lesson 3A on routing 12:53:10.436 --> 12:53:13.246 align:start position:0% welcome to module 8 lesson 3A on routing metrics<12:53:11.040> or<12:53:11.340> if<12:53:11.520> you're<12:53:11.640> in<12:53:11.820> the<12:53:12.000> UK<12:53:12.360> routing 12:53:13.246 --> 12:53:13.256 align:start position:0% metrics or if you're in the UK routing 12:53:13.256 --> 12:53:15.710 align:start position:0% metrics or if you're in the UK routing metrics 12:53:15.710 --> 12:53:15.720 align:start position:0% metrics 12:53:15.720 --> 12:53:18.050 align:start position:0% metrics so<12:53:16.256> this<12:53:16.380> is<12:53:16.500> a<12:53:16.560> little<12:53:16.616> bit<12:53:16.800> esoteric<12:53:17.520> in<12:53:17.820> as 12:53:18.050 --> 12:53:18.060 align:start position:0% so this is a little bit esoteric in as 12:53:18.060 --> 12:53:19.246 align:start position:0% so this is a little bit esoteric in as much<12:53:18.300> as 12:53:19.246 --> 12:53:19.256 align:start position:0% much as 12:53:19.256 --> 12:53:21.586 align:start position:0% much as you're<12:53:19.800> better<12:53:20.040> off<12:53:20.276> configuring<12:53:20.936> routing 12:53:21.586 --> 12:53:21.596 align:start position:0% you're better off configuring routing 12:53:21.596 --> 12:53:23.926 align:start position:0% you're better off configuring routing and<12:53:21.840> playing<12:53:22.320> with<12:53:22.616> this<12:53:22.860> and<12:53:23.160> doing<12:53:23.400> Hands-On 12:53:23.926 --> 12:53:23.936 align:start position:0% and playing with this and doing Hands-On 12:53:23.936 --> 12:53:27.050 align:start position:0% and playing with this and doing Hands-On labs<12:53:24.900> which<12:53:25.380> you<12:53:25.500> don't<12:53:25.680> do<12:53:25.916> for<12:53:26.220> the<12:53:26.520> content 12:53:27.050 --> 12:53:27.060 align:start position:0% labs which you don't do for the content 12:53:27.060 --> 12:53:29.630 align:start position:0% labs which you don't do for the content Network<12:53:27.300> plus<12:53:27.660> but<12:53:28.020> if<12:53:28.436> you're<12:53:28.560> doing<12:53:28.740> a<12:53:28.980> CCNA 12:53:29.630 --> 12:53:29.640 align:start position:0% Network plus but if you're doing a CCNA 12:53:29.640 --> 12:53:31.426 align:start position:0% Network plus but if you're doing a CCNA exam<12:53:29.936> for<12:53:30.060> Cisco<12:53:30.480> for<12:53:30.720> example<12:53:30.900> you'd 12:53:31.426 --> 12:53:31.436 align:start position:0% exam for Cisco for example you'd 12:53:31.436 --> 12:53:33.530 align:start position:0% exam for Cisco for example you'd actually<12:53:31.616> have<12:53:32.580> examples<12:53:33.000> where<12:53:33.300> you<12:53:33.416> could 12:53:33.530 --> 12:53:33.540 align:start position:0% actually have examples where you could 12:53:33.540 --> 12:53:35.870 align:start position:0% actually have examples where you could see<12:53:33.776> this<12:53:34.140> and<12:53:34.500> been<12:53:34.860> affected<12:53:35.276> as<12:53:35.640> you 12:53:35.870 --> 12:53:35.880 align:start position:0% see this and been affected as you 12:53:35.880 --> 12:53:37.850 align:start position:0% see this and been affected as you configure<12:53:36.416> the<12:53:37.200> different<12:53:37.380> routing 12:53:37.850 --> 12:53:37.860 align:start position:0% configure the different routing 12:53:37.860 --> 12:53:40.606 align:start position:0% configure the different routing protocols<12:53:38.460> and<12:53:38.700> add<12:53:38.880> more<12:53:39.060> hops<12:53:39.720> or<12:53:40.020> other 12:53:40.606 --> 12:53:40.616 align:start position:0% protocols and add more hops or other 12:53:40.616 --> 12:53:42.170 align:start position:0% protocols and add more hops or other devices 12:53:42.170 --> 12:53:42.180 align:start position:0% devices 12:53:42.180 --> 12:53:44.210 align:start position:0% devices but<12:53:42.596> we'll<12:53:42.900> do<12:53:43.020> our<12:53:43.200> best<12:53:43.380> we're<12:53:43.980> going<12:53:44.096> to 12:53:44.210 --> 12:53:44.220 align:start position:0% but we'll do our best we're going to 12:53:44.220 --> 12:53:47.810 align:start position:0% but we'll do our best we're going to look<12:53:44.276> at<12:53:44.400> routing<12:53:44.820> metrics<12:53:45.596> the<12:53:45.960> MTU 12:53:47.810 --> 12:53:47.820 align:start position:0% look at routing metrics the MTU 12:53:47.820 --> 12:53:52.606 align:start position:0% look at routing metrics the MTU metric<12:53:48.596> costs<12:53:49.200> latency<12:53:50.096> load<12:53:50.820> reliability 12:53:52.606 --> 12:53:52.616 align:start position:0% metric costs latency load reliability 12:53:52.616 --> 12:53:55.790 align:start position:0% metric costs latency load reliability so<12:53:53.040> routing<12:53:53.580> metrics<12:53:54.060> and<12:53:55.020> tables<12:53:55.500> on<12:53:55.616> a 12:53:55.790 --> 12:53:55.800 align:start position:0% so routing metrics and tables on a 12:53:55.800 --> 12:53:57.290 align:start position:0% so routing metrics and tables on a router 12:53:57.290 --> 12:53:57.300 align:start position:0% router 12:53:57.300 --> 12:53:59.030 align:start position:0% router and<12:53:57.776> it's<12:53:57.960> actually<12:53:58.080> the<12:53:58.320> same<12:53:58.436> for<12:53:58.616> servers 12:53:59.030 --> 12:53:59.040 align:start position:0% and it's actually the same for servers 12:53:59.040 --> 12:54:00.170 align:start position:0% and it's actually the same for servers as<12:53:59.220> well 12:54:00.170 --> 12:54:00.180 align:start position:0% as well 12:54:00.180 --> 12:54:02.570 align:start position:0% as well and<12:54:00.776> the<12:54:00.960> writing<12:54:01.320> table<12:54:01.500> can<12:54:01.980> contain<12:54:02.276> a 12:54:02.570 --> 12:54:02.580 align:start position:0% and the writing table can contain a 12:54:02.580 --> 12:54:04.850 align:start position:0% and the writing table can contain a field<12:54:02.756> known<12:54:03.240> as<12:54:03.416> the<12:54:03.660> metric 12:54:04.850 --> 12:54:04.860 align:start position:0% field known as the metric 12:54:04.860 --> 12:54:06.890 align:start position:0% field known as the metric now<12:54:05.276> a<12:54:05.400> metric<12:54:05.756> is<12:54:05.936> a<12:54:06.116> value<12:54:06.300> and<12:54:06.540> that<12:54:06.720> value 12:54:06.890 --> 12:54:06.900 align:start position:0% now a metric is a value and that value 12:54:06.900 --> 12:54:09.170 align:start position:0% now a metric is a value and that value can<12:54:07.200> be<12:54:07.320> made<12:54:07.560> from<12:54:07.860> a<12:54:08.096> number<12:54:08.640> of<12:54:08.820> different 12:54:09.170 --> 12:54:09.180 align:start position:0% can be made from a number of different 12:54:09.180 --> 12:54:12.230 align:start position:0% can be made from a number of different factors<12:54:10.020> depending<12:54:10.500> on<12:54:10.800> the<12:54:11.640> route<12:54:11.820> the 12:54:12.230 --> 12:54:12.240 align:start position:0% factors depending on the route the 12:54:12.240 --> 12:54:14.450 align:start position:0% factors depending on the route the routing<12:54:12.660> protocol 12:54:14.450 --> 12:54:14.460 align:start position:0% routing protocol 12:54:14.460 --> 12:54:18.170 align:start position:0% routing protocol this<12:54:15.060> is<12:54:15.240> used<12:54:15.900> by<12:54:16.140> the<12:54:16.320> router<12:54:16.800> when<12:54:17.276> it<12:54:17.520> runs 12:54:18.170 --> 12:54:18.180 align:start position:0% this is used by the router when it runs 12:54:18.180 --> 12:54:21.050 align:start position:0% this is used by the router when it runs a<12:54:18.360> mathematical<12:54:19.020> algorithm<12:54:19.500> to<12:54:19.800> work<12:54:19.980> out<12:54:20.220> the 12:54:21.050 --> 12:54:21.060 align:start position:0% a mathematical algorithm to work out the 12:54:21.060 --> 12:54:23.870 align:start position:0% a mathematical algorithm to work out the best<12:54:21.180> path<12:54:21.480> to<12:54:21.840> get<12:54:22.020> from<12:54:22.380> a<12:54:22.860> which<12:54:23.580> will<12:54:23.700> be 12:54:23.870 --> 12:54:23.880 align:start position:0% best path to get from a which will be 12:54:23.880 --> 12:54:27.470 align:start position:0% best path to get from a which will be the<12:54:24.180> local<12:54:24.416> router<12:54:25.400> 2B<12:54:26.400> which<12:54:26.820> is<12:54:26.936> the<12:54:27.240> remote 12:54:27.470 --> 12:54:27.480 align:start position:0% the local router 2B which is the remote 12:54:27.480 --> 12:54:30.406 align:start position:0% the local router 2B which is the remote router 12:54:30.406 --> 12:54:30.416 align:start position:0% router 12:54:30.416 --> 12:54:33.890 align:start position:0% router now<12:54:31.080> I<12:54:31.256> issue<12:54:31.616> the<12:54:31.740> show<12:54:31.916> IP<12:54:32.640> routes<12:54:33.240> on<12:54:33.720> a 12:54:33.890 --> 12:54:33.900 align:start position:0% now I issue the show IP routes on a 12:54:33.900 --> 12:54:36.710 align:start position:0% now I issue the show IP routes on a router<12:54:34.320> in<12:54:34.560> the<12:54:34.740> image<12:54:35.276> here<12:54:35.460> and<12:54:36.300> I<12:54:36.480> just 12:54:36.710 --> 12:54:36.720 align:start position:0% router in the image here and I just 12:54:36.720 --> 12:54:39.710 align:start position:0% router in the image here and I just highlighted<12:54:37.436> MD<12:54:38.340> if<12:54:38.936> you<12:54:39.060> did<12:54:39.180> look<12:54:39.360> at<12:54:39.540> the 12:54:39.710 --> 12:54:39.720 align:start position:0% highlighted MD if you did look at the 12:54:39.720 --> 12:54:44.210 align:start position:0% highlighted MD if you did look at the table<12:54:39.900> there<12:54:40.256> is<12:54:40.680> short<12:54:40.980> for<12:54:41.480> eigrp<12:54:42.680> on<12:54:43.680> Cisco 12:54:44.210 --> 12:54:44.220 align:start position:0% table there is short for eigrp on Cisco 12:54:44.220 --> 12:54:45.710 align:start position:0% table there is short for eigrp on Cisco routing<12:54:44.640> tables<12:54:44.936> it'd<12:54:45.180> be<12:54:45.300> different<12:54:45.416> if 12:54:45.710 --> 12:54:45.720 align:start position:0% routing tables it'd be different if 12:54:45.720 --> 12:54:47.390 align:start position:0% routing tables it'd be different if you're<12:54:45.900> using<12:54:46.256> Juniper<12:54:46.800> or<12:54:47.040> a<12:54:47.220> different 12:54:47.390 --> 12:54:47.400 align:start position:0% you're using Juniper or a different 12:54:47.400 --> 12:54:50.570 align:start position:0% you're using Juniper or a different device<12:54:47.840> but<12:54:48.840> just<12:54:49.020> for<12:54:49.200> your<12:54:49.380> information<12:54:49.616> the 12:54:50.570 --> 12:54:50.580 align:start position:0% device but just for your information the 12:54:50.580 --> 12:54:52.550 align:start position:0% device but just for your information the different<12:54:50.756> numbers<12:54:51.116> there<12:54:51.596> are<12:54:51.960> the<12:54:52.140> routing 12:54:52.550 --> 12:54:52.560 align:start position:0% different numbers there are the routing 12:54:52.560 --> 12:54:56.150 align:start position:0% different numbers there are the routing metrics<12:54:53.160> the<12:54:53.840> ergrp<12:54:54.840> is<12:54:55.020> calculated<12:54:55.560> based 12:54:56.150 --> 12:54:56.160 align:start position:0% metrics the ergrp is calculated based 12:54:56.160 --> 12:54:58.070 align:start position:0% metrics the ergrp is calculated based upon<12:54:56.340> the<12:54:56.580> location<12:54:56.756> of<12:54:57.720> the<12:54:57.960> different 12:54:58.070 --> 12:54:58.080 align:start position:0% upon the location of the different 12:54:58.080 --> 12:55:03.010 align:start position:0% upon the location of the different networks<12:54:58.880> which<12:54:59.880> are<12:55:00.060> 34<12:55:01.160> uh 12:55:03.010 --> 12:55:03.020 align:start position:0% networks which are 34 uh 12:55:03.020 --> 12:55:07.130 align:start position:0% networks which are 34 uh 4.4.4.4<12:55:04.020> the<12:55:04.380> 23<12:55:04.860> Network<12:55:05.160> 24<12:55:05.880> and<12:55:06.776> the<12:55:07.020> 12 12:55:07.130 --> 12:55:07.140 align:start position:0% 4.4.4.4 the 23 Network 24 and the 12 12:55:07.140 --> 12:55:08.210 align:start position:0% 4.4.4.4 the 23 Network 24 and the 12 Network 12:55:08.210 --> 12:55:08.220 align:start position:0% Network 12:55:08.220 --> 12:55:09.950 align:start position:0% Network don't<12:55:08.700> worry<12:55:08.880> too<12:55:09.060> much<12:55:09.240> about<12:55:09.416> that<12:55:09.596> but<12:55:09.776> I 12:55:09.950 --> 12:55:09.960 align:start position:0% don't worry too much about that but I 12:55:09.960 --> 12:55:11.150 align:start position:0% don't worry too much about that but I just<12:55:10.080> wanted<12:55:10.200> to<12:55:10.380> show<12:55:10.560> you<12:55:10.680> that<12:55:10.800> you<12:55:11.096> can 12:55:11.150 --> 12:55:11.160 align:start position:0% just wanted to show you that you can 12:55:11.160 --> 12:55:13.730 align:start position:0% just wanted to show you that you can actually<12:55:11.340> see<12:55:11.640> it<12:55:11.820> in<12:55:12.000> a<12:55:12.116> routing<12:55:12.416> table<12:55:12.740> and 12:55:13.730 --> 12:55:13.740 align:start position:0% actually see it in a routing table and 12:55:13.740 --> 12:55:16.670 align:start position:0% actually see it in a routing table and the<12:55:13.916> number<12:55:14.040> 90<12:55:14.400> before<12:55:14.936> the 12:55:16.670 --> 12:55:16.680 align:start position:0% the number 90 before the 12:55:16.680 --> 12:55:18.950 align:start position:0% the number 90 before the the<12:55:17.160> routing<12:55:17.756> metric<12:55:18.116> there<12:55:18.360> is<12:55:18.776> the 12:55:18.950 --> 12:55:18.960 align:start position:0% the routing metric there is the 12:55:18.960 --> 12:55:22.310 align:start position:0% the routing metric there is the administrative<12:55:19.500> distance<12:55:19.980> that<12:55:21.416> um<12:55:21.416> is<12:55:22.020> is 12:55:22.310 --> 12:55:22.320 align:start position:0% administrative distance that um is is 12:55:22.320 --> 12:55:25.550 align:start position:0% administrative distance that um is is allocated<12:55:22.800> to<12:55:23.040> the<12:55:23.160> protocol<12:55:23.580> and<12:55:24.416> for<12:55:24.596> ergrp 12:55:25.550 --> 12:55:25.560 align:start position:0% allocated to the protocol and for ergrp 12:55:25.560 --> 12:55:29.926 align:start position:0% allocated to the protocol and for ergrp it's<12:55:26.580> um<12:55:26.580> 90<12:55:27.060> internally<12:55:27.960> ergrp 12:55:29.926 --> 12:55:29.936 align:start position:0% it's um 90 internally ergrp 12:55:29.936 --> 12:55:32.570 align:start position:0% it's um 90 internally ergrp so<12:55:30.660> if<12:55:31.020> a<12:55:31.320> router<12:55:31.680> has<12:55:31.800> different<12:55:32.040> routes<12:55:32.400> to 12:55:32.570 --> 12:55:32.580 align:start position:0% so if a router has different routes to 12:55:32.580 --> 12:55:34.310 align:start position:0% so if a router has different routes to the<12:55:32.700> same<12:55:32.880> network<12:55:33.116> the<12:55:33.596> routing<12:55:34.020> metric 12:55:34.310 --> 12:55:34.320 align:start position:0% the same network the routing metric 12:55:34.320 --> 12:55:36.650 align:start position:0% the same network the routing metric helps<12:55:34.800> the<12:55:34.860> router<12:55:35.160> decide<12:55:35.580> which<12:55:36.240> of<12:55:36.416> these 12:55:36.650 --> 12:55:36.660 align:start position:0% helps the router decide which of these 12:55:36.660 --> 12:55:38.870 align:start position:0% helps the router decide which of these routes<12:55:37.020> to<12:55:37.200> choose<12:55:37.500> because<12:55:37.800> you<12:55:38.520> could<12:55:38.700> have 12:55:38.870 --> 12:55:38.880 align:start position:0% routes to choose because you could have 12:55:38.880 --> 12:55:43.390 align:start position:0% routes to choose because you could have 30<12:55:39.300> 40<12:55:39.660> 50<12:55:40.080> plus<12:55:40.640> ways<12:55:41.640> to<12:55:41.820> get<12:55:42.000> from<12:55:42.360> A<12:55:42.840> to<12:55:43.080> B 12:55:43.390 --> 12:55:43.400 align:start position:0% 30 40 50 plus ways to get from A to B 12:55:43.400 --> 12:55:46.550 align:start position:0% 30 40 50 plus ways to get from A to B and<12:55:44.400> the<12:55:44.580> writing<12:55:44.936> table<12:55:45.116> will<12:55:45.480> just<12:55:45.720> be<12:55:46.320> too 12:55:46.550 --> 12:55:46.560 align:start position:0% and the writing table will just be too 12:55:46.560 --> 12:55:48.950 align:start position:0% and the writing table will just be too big<12:55:46.740> and<12:55:46.980> the<12:55:47.160> router<12:55:47.580> would<12:55:47.700> crash<12:55:48.060> so<12:55:48.840> it 12:55:48.950 --> 12:55:48.960 align:start position:0% big and the router would crash so it 12:55:48.960 --> 12:55:51.230 align:start position:0% big and the router would crash so it uses<12:55:49.320> the<12:55:49.500> best<12:55:49.680> path<12:55:49.980> and<12:55:50.520> inserts<12:55:51.000> the<12:55:51.116> best 12:55:51.230 --> 12:55:51.240 align:start position:0% uses the best path and inserts the best 12:55:51.240 --> 12:55:54.170 align:start position:0% uses the best path and inserts the best path<12:55:51.480> in<12:55:51.660> the<12:55:51.840> routing<12:55:52.140> table 12:55:54.170 --> 12:55:54.180 align:start position:0% path in the routing table 12:55:54.180 --> 12:55:56.510 align:start position:0% path in the routing table all<12:55:54.720> right<12:55:54.900> each<12:55:55.140> writing<12:55:55.560> protocol<12:55:55.860> uses<12:55:56.340> a 12:55:56.510 --> 12:55:56.520 align:start position:0% all right each writing protocol uses a 12:55:56.520 --> 12:55:58.246 align:start position:0% all right each writing protocol uses a different<12:55:56.640> metric<12:55:57.180> I<12:55:57.720> think<12:55:57.900> you<12:55:58.080> probably 12:55:58.246 --> 12:55:58.256 align:start position:0% different metric I think you probably 12:55:58.256 --> 12:55:59.870 align:start position:0% different metric I think you probably need<12:55:58.436> an<12:55:58.680> overview<12:55:58.980> just<12:55:59.340> for<12:55:59.520> the<12:55:59.700> network 12:55:59.870 --> 12:55:59.880 align:start position:0% need an overview just for the network 12:55:59.880 --> 12:56:00.950 align:start position:0% need an overview just for the network Plus 12:56:00.950 --> 12:56:00.960 align:start position:0% Plus 12:56:00.960 --> 12:56:03.230 align:start position:0% Plus so<12:56:01.380> we've<12:56:01.500> got<12:56:01.616> two<12:56:01.860> routers<12:56:02.400> a<12:56:02.700> router<12:56:03.060> one 12:56:03.230 --> 12:56:03.240 align:start position:0% so we've got two routers a router one 12:56:03.240 --> 12:56:05.266 align:start position:0% so we've got two routers a router one and<12:56:03.416> a<12:56:03.540> router<12:56:03.840> 11<12:56:03.960> between<12:56:04.500> these<12:56:04.980> two 12:56:05.266 --> 12:56:05.276 align:start position:0% and a router 11 between these two 12:56:05.276 --> 12:56:07.490 align:start position:0% and a router 11 between these two routers<12:56:05.756> you've<12:56:06.416> got<12:56:06.540> nine<12:56:06.776> other<12:56:07.020> routers 12:56:07.490 --> 12:56:07.500 align:start position:0% routers you've got nine other routers 12:56:07.500 --> 12:56:10.010 align:start position:0% routers you've got nine other routers that<12:56:08.096> connect<12:56:08.276> to<12:56:08.460> different<12:56:08.640> Networks 12:56:10.010 --> 12:56:10.020 align:start position:0% that connect to different Networks 12:56:10.020 --> 12:56:11.810 align:start position:0% that connect to different Networks and<12:56:10.436> you<12:56:10.560> can<12:56:10.680> see<12:56:10.916> the<12:56:11.220> different<12:56:11.340> routers 12:56:11.810 --> 12:56:11.820 align:start position:0% and you can see the different routers 12:56:11.820 --> 12:56:14.810 align:start position:0% and you can see the different routers there<12:56:12.000> path<12:56:12.416> x<12:56:12.960> y<12:56:13.256> and<12:56:13.800> z<12:56:14.096> are<12:56:14.460> the<12:56:14.640> different 12:56:14.810 --> 12:56:14.820 align:start position:0% there path x y and z are the different 12:56:14.820 --> 12:56:18.406 align:start position:0% there path x y and z are the different paths<12:56:15.596> in<12:56:16.380> order<12:56:16.500> to<12:56:16.740> get<12:56:16.860> to<12:56:17.040> router<12:56:17.400> 11<12:56:17.580> and 12:56:18.406 --> 12:56:18.416 align:start position:0% paths in order to get to router 11 and 12:56:18.416 --> 12:56:19.550 align:start position:0% paths in order to get to router 11 and of<12:56:18.596> course<12:56:18.720> you<12:56:18.900> could<12:56:19.020> make<12:56:19.256> it<12:56:19.380> more 12:56:19.550 --> 12:56:19.560 align:start position:0% of course you could make it more 12:56:19.560 --> 12:56:21.950 align:start position:0% of course you could make it more complicated<12:56:20.096> by<12:56:20.460> connecting<12:56:21.000> all<12:56:21.660> of<12:56:21.776> the 12:56:21.950 --> 12:56:21.960 align:start position:0% complicated by connecting all of the 12:56:21.960 --> 12:56:23.746 align:start position:0% complicated by connecting all of the routers<12:56:22.320> in<12:56:22.500> between<12:56:22.680> the<12:56:22.980> paths<12:56:23.276> which<12:56:23.520> may 12:56:23.746 --> 12:56:23.756 align:start position:0% routers in between the paths which may 12:56:23.756 --> 12:56:25.970 align:start position:0% routers in between the paths which may well<12:56:23.936> be<12:56:24.180> the<12:56:24.360> case 12:56:25.970 --> 12:56:25.980 align:start position:0% well be the case 12:56:25.980 --> 12:56:28.010 align:start position:0% well be the case so<12:56:26.580> you<12:56:26.700> want<12:56:26.880> to<12:56:27.000> get<12:56:27.060> from<12:56:27.300> router<12:56:27.720> 1<12:56:27.900> to 12:56:28.010 --> 12:56:28.020 align:start position:0% so you want to get from router 1 to 12:56:28.020 --> 12:56:29.810 align:start position:0% so you want to get from router 1 to router<12:56:28.380> 11<12:56:28.560> and<12:56:29.220> there's<12:56:29.400> three<12:56:29.580> different 12:56:29.810 --> 12:56:29.820 align:start position:0% router 11 and there's three different 12:56:29.820 --> 12:56:32.450 align:start position:0% router 11 and there's three different paths<12:56:30.360> to<12:56:30.540> choose<12:56:30.960> from 12:56:32.450 --> 12:56:32.460 align:start position:0% paths to choose from 12:56:32.460 --> 12:56:35.030 align:start position:0% paths to choose from sake<12:56:33.060> of<12:56:33.240> convenience<12:56:33.660> as<12:56:34.020> I<12:56:34.200> said<12:56:34.320> x<12:56:34.560> y<12:56:34.740> and<12:56:34.916> z 12:56:35.030 --> 12:56:35.040 align:start position:0% sake of convenience as I said x y and z 12:56:35.040 --> 12:56:37.190 align:start position:0% sake of convenience as I said x y and z are<12:56:35.220> the<12:56:35.400> different<12:56:35.520> path<12:56:35.756> names<12:56:36.200> writing 12:56:37.190 --> 12:56:37.200 align:start position:0% are the different path names writing 12:56:37.200 --> 12:56:40.070 align:start position:0% are the different path names writing protocols<12:56:37.740> will<12:56:37.916> choose<12:56:38.400> a<12:56:39.180> route<12:56:39.480> with<12:56:39.776> the 12:56:40.070 --> 12:56:40.080 align:start position:0% protocols will choose a route with the 12:56:40.080 --> 12:56:42.710 align:start position:0% protocols will choose a route with the lowest<12:56:40.560> metric 12:56:42.710 --> 12:56:42.720 align:start position:0% lowest metric 12:56:42.720 --> 12:56:44.746 align:start position:0% lowest metric now<12:56:43.080> if<12:56:43.256> we<12:56:43.436> use<12:56:43.680> rip<12:56:44.096> routing<12:56:44.580> information 12:56:44.746 --> 12:56:44.756 align:start position:0% now if we use rip routing information 12:56:44.756 --> 12:56:48.530 align:start position:0% now if we use rip routing information protocol<12:56:45.480> it<12:56:46.380> only<12:56:46.560> uses<12:56:46.980> hop<12:56:47.276> count<12:56:47.640> it 12:56:48.530 --> 12:56:48.540 align:start position:0% protocol it only uses hop count it 12:56:48.540 --> 12:56:50.266 align:start position:0% protocol it only uses hop count it doesn't<12:56:48.720> care<12:56:48.960> about<12:56:49.200> the<12:56:49.616> speed<12:56:49.740> of<12:56:49.980> the<12:56:50.096> link 12:56:50.266 --> 12:56:50.276 align:start position:0% doesn't care about the speed of the link 12:56:50.276 --> 12:56:52.130 align:start position:0% doesn't care about the speed of the link or<12:56:50.520> if<12:56:50.700> the<12:56:50.880> Link's<12:56:51.116> reliable<12:56:51.596> or<12:56:51.900> anything 12:56:52.130 --> 12:56:52.140 align:start position:0% or if the Link's reliable or anything 12:56:52.140 --> 12:56:54.230 align:start position:0% or if the Link's reliable or anything like<12:56:52.500> that<12:56:52.680> it's 12:56:54.230 --> 12:56:54.240 align:start position:0% like that it's 12:56:54.240 --> 12:56:57.170 align:start position:0% like that it's um a<12:56:54.660> fairly<12:56:54.900> old<12:56:55.380> writing<12:56:56.040> protocol<12:56:56.460> and<12:56:57.060> it 12:56:57.170 --> 12:56:57.180 align:start position:0% um a fairly old writing protocol and it 12:56:57.180 --> 12:56:58.970 align:start position:0% um a fairly old writing protocol and it was<12:56:57.300> built<12:56:57.596> for<12:56:57.776> quite<12:56:58.020> small<12:56:58.380> networks 12:56:58.970 --> 12:56:58.980 align:start position:0% was built for quite small networks 12:56:58.980 --> 12:57:00.710 align:start position:0% was built for quite small networks because<12:56:59.220> all<12:56:59.400> networks<12:56:59.880> were<12:57:00.060> small<12:57:00.360> at<12:57:00.540> the 12:57:00.710 --> 12:57:00.720 align:start position:0% because all networks were small at the 12:57:00.720 --> 12:57:02.150 align:start position:0% because all networks were small at the time 12:57:02.150 --> 12:57:02.160 align:start position:0% time 12:57:02.160 --> 12:57:05.870 align:start position:0% time and<12:57:02.936> so<12:57:03.240> you<12:57:03.660> can<12:57:03.776> see<12:57:04.020> there<12:57:04.256> that<12:57:04.560> there's<12:57:04.980> uh 12:57:05.870 --> 12:57:05.880 align:start position:0% and so you can see there that there's uh 12:57:05.880 --> 12:57:08.810 align:start position:0% and so you can see there that there's uh one<12:57:06.300> path<12:57:06.596> has<12:57:06.776> got<12:57:06.960> three<12:57:07.200> hops<12:57:07.740> one<12:57:08.400> has<12:57:08.580> got 12:57:08.810 --> 12:57:08.820 align:start position:0% one path has got three hops one has got 12:57:08.820 --> 12:57:11.450 align:start position:0% one path has got three hops one has got one<12:57:09.360> two<12:57:09.596> three<12:57:09.840> four<12:57:10.080> hops<12:57:10.560> in<12:57:10.860> the<12:57:10.980> middle<12:57:11.096> if 12:57:11.450 --> 12:57:11.460 align:start position:0% one two three four hops in the middle if 12:57:11.460 --> 12:57:13.490 align:start position:0% one two three four hops in the middle if you're<12:57:11.640> not<12:57:11.820> counting<12:57:12.416> the<12:57:13.020> um<12:57:13.020> source<12:57:13.436> and 12:57:13.490 --> 12:57:13.500 align:start position:0% you're not counting the um source and 12:57:13.500 --> 12:57:16.310 align:start position:0% you're not counting the um source and destination<12:57:14.000> the<12:57:15.000> other<12:57:15.116> has<12:57:15.480> two<12:57:15.720> routers 12:57:16.310 --> 12:57:16.320 align:start position:0% destination the other has two routers 12:57:16.320 --> 12:57:18.050 align:start position:0% destination the other has two routers nine<12:57:16.560> and<12:57:16.800> ten<12:57:17.040> so<12:57:17.400> that's<12:57:17.580> going<12:57:17.756> to<12:57:17.820> be<12:57:17.936> the 12:57:18.050 --> 12:57:18.060 align:start position:0% nine and ten so that's going to be the 12:57:18.060 --> 12:57:21.586 align:start position:0% nine and ten so that's going to be the shortest<12:57:18.480> amount<12:57:18.776> of<12:57:18.960> hops 12:57:21.586 --> 12:57:21.596 align:start position:0% 12:57:21.596 --> 12:57:26.570 align:start position:0% two<12:57:22.020> hops<12:57:22.500> four<12:57:23.276> or<12:57:23.700> three 12:57:26.570 --> 12:57:26.580 align:start position:0% 12:57:26.580 --> 12:57:28.606 align:start position:0% so<12:57:27.000> if<12:57:27.116> rip<12:57:27.416> chooses<12:57:27.776> the<12:57:28.080> route<12:57:28.320> between 12:57:28.606 --> 12:57:28.616 align:start position:0% so if rip chooses the route between 12:57:28.616 --> 12:57:31.370 align:start position:0% so if rip chooses the route between router<12:57:29.580> 1<12:57:29.936> and<12:57:30.180> 11<12:57:30.360> it<12:57:30.660> will<12:57:30.776> choose<12:57:31.020> the<12:57:31.200> best 12:57:31.370 --> 12:57:31.380 align:start position:0% router 1 and 11 it will choose the best 12:57:31.380 --> 12:57:34.246 align:start position:0% router 1 and 11 it will choose the best path<12:57:31.800> as<12:57:32.096> path<12:57:32.460> X 12:57:34.246 --> 12:57:34.256 align:start position:0% path as path X 12:57:34.256 --> 12:57:36.890 align:start position:0% path as path X it's<12:57:34.740> got<12:57:34.916> the<12:57:35.040> lowest<12:57:35.340> top<12:57:35.520> count 12:57:36.890 --> 12:57:36.900 align:start position:0% it's got the lowest top count 12:57:36.900 --> 12:57:39.470 align:start position:0% it's got the lowest top count now<12:57:37.680> I've<12:57:38.040> introduced<12:57:38.460> a<12:57:38.640> problem<12:57:38.820> here<12:57:39.116> I've 12:57:39.470 --> 12:57:39.480 align:start position:0% now I've introduced a problem here I've 12:57:39.480 --> 12:57:41.450 align:start position:0% now I've introduced a problem here I've actually<12:57:39.720> shown<12:57:40.616> you<12:57:40.740> the<12:57:40.980> speed<12:57:41.096> of<12:57:41.276> the 12:57:41.450 --> 12:57:41.460 align:start position:0% actually shown you the speed of the 12:57:41.460 --> 12:57:44.086 align:start position:0% actually shown you the speed of the links<12:57:41.700> and<12:57:41.880> the<12:57:42.060> speed<12:57:42.240> of<12:57:42.776> path<12:57:43.080> X<12:57:43.436> is<12:57:43.800> only 12:57:44.086 --> 12:57:44.096 align:start position:0% links and the speed of path X is only 12:57:44.096 --> 12:57:45.710 align:start position:0% links and the speed of path X is only 56k 12:57:45.710 --> 12:57:45.720 align:start position:0% 56k 12:57:45.720 --> 12:57:47.870 align:start position:0% 56k which<12:57:46.256> is<12:57:46.436> a<12:57:46.680> crazy<12:57:46.916> slow<12:57:47.220> when<12:57:47.460> you<12:57:47.640> compare 12:57:47.870 --> 12:57:47.880 align:start position:0% which is a crazy slow when you compare 12:57:47.880 --> 12:57:51.050 align:start position:0% which is a crazy slow when you compare it<12:57:48.000> to<12:57:48.180> path<12:57:48.360> Y<12:57:48.776> which<12:57:49.380> is<12:57:49.500> one<12:57:49.740> Meg<12:57:50.160> however 12:57:51.050 --> 12:57:51.060 align:start position:0% it to path Y which is one Meg however 12:57:51.060 --> 12:57:53.870 align:start position:0% it to path Y which is one Meg however rip<12:57:51.416> won't<12:57:51.776> understand<12:57:52.080> this<12:57:52.916> now<12:57:53.520> you<12:57:53.756> can 12:57:53.870 --> 12:57:53.880 align:start position:0% rip won't understand this now you can 12:57:53.880 --> 12:57:55.370 align:start position:0% rip won't understand this now you can configure<12:57:54.416> it 12:57:55.370 --> 12:57:55.380 align:start position:0% configure it 12:57:55.380 --> 12:57:58.906 align:start position:0% configure it and<12:57:55.980> and<12:57:56.040> do<12:57:56.820> extra<12:57:57.000> configurations<12:57:57.660> to 12:57:58.906 --> 12:57:58.916 align:start position:0% and and do extra configurations to 12:57:58.916 --> 12:58:01.970 align:start position:0% and and do extra configurations to um<12:57:58.980> force<12:57:59.640> it<12:57:59.756> to<12:57:59.936> take<12:58:00.300> path<12:58:00.596> y<12:58:00.900> but<12:58:01.680> by 12:58:01.970 --> 12:58:01.980 align:start position:0% um force it to take path y but by 12:58:01.980 --> 12:58:05.570 align:start position:0% um force it to take path y but by default<12:58:02.400> it<12:58:03.776> um<12:58:03.776> it<12:58:04.320> won't<12:58:04.436> it<12:58:04.740> won't<12:58:04.916> use<12:58:05.160> path 12:58:05.570 --> 12:58:05.580 align:start position:0% default it um it won't it won't use path 12:58:05.580 --> 12:58:11.210 align:start position:0% default it um it won't it won't use path y<12:58:05.820> because<12:58:06.300> the<12:58:06.540> volt<12:58:06.900> counts 12:58:11.210 --> 12:58:11.220 align:start position:0% 12:58:11.220 --> 12:58:13.130 align:start position:0% so<12:58:11.756> different<12:58:12.060> routes<12:58:12.416> and<12:58:12.480> protocols<12:58:12.840> use 12:58:13.130 --> 12:58:13.140 align:start position:0% so different routes and protocols use 12:58:13.140 --> 12:58:15.710 align:start position:0% so different routes and protocols use different<12:58:13.380> metrics<12:58:14.040> and<12:58:14.580> since<12:58:14.880> the<12:58:15.300> link 12:58:15.710 --> 12:58:15.720 align:start position:0% different metrics and since the link 12:58:15.720 --> 12:58:18.950 align:start position:0% different metrics and since the link speed<12:58:16.160> affects<12:58:17.160> the<12:58:17.340> throughput<12:58:17.960> writing 12:58:18.950 --> 12:58:18.960 align:start position:0% speed affects the throughput writing 12:58:18.960 --> 12:58:21.290 align:start position:0% speed affects the throughput writing protocols<12:58:19.616> such<12:58:19.740> as<12:58:19.860> ergrp<12:58:20.756> which<12:58:21.000> is<12:58:21.060> an 12:58:21.290 --> 12:58:21.300 align:start position:0% protocols such as ergrp which is an 12:58:21.300 --> 12:58:23.450 align:start position:0% protocols such as ergrp which is an advanced<12:58:21.660> writing<12:58:22.080> protocol<12:58:22.436> take<12:58:23.276> into 12:58:23.450 --> 12:58:23.460 align:start position:0% advanced writing protocol take into 12:58:23.460 --> 12:58:26.630 align:start position:0% advanced writing protocol take into account<12:58:23.900> now<12:58:24.900> it<12:58:25.560> can<12:58:25.740> take<12:58:26.040> into<12:58:26.276> account 12:58:26.630 --> 12:58:26.640 align:start position:0% account now it can take into account 12:58:26.640 --> 12:58:30.170 align:start position:0% account now it can take into account Cisco's<12:58:27.596> version<12:58:27.840> of<12:58:28.080> vrgrp<12:58:28.980> only<12:58:29.580> uses<12:58:30.000> two 12:58:30.170 --> 12:58:30.180 align:start position:0% Cisco's version of vrgrp only uses two 12:58:30.180 --> 12:58:32.746 align:start position:0% Cisco's version of vrgrp only uses two of<12:58:30.360> the<12:58:30.480> possible<12:58:30.776> values 12:58:32.746 --> 12:58:32.756 align:start position:0% of the possible values 12:58:32.756 --> 12:58:37.130 align:start position:0% of the possible values um<12:58:32.820> that<12:58:33.960> um<12:58:33.960> are<12:58:34.616> usable<12:58:35.040> Within<12:58:35.400> ergrp 12:58:37.130 --> 12:58:37.140 align:start position:0% um that um are usable Within ergrp 12:58:37.140 --> 12:58:39.050 align:start position:0% um that um are usable Within ergrp and<12:58:37.800> Cisco<12:58:38.276> have<12:58:38.400> their<12:58:38.580> own<12:58:38.700> version<12:58:38.880> of 12:58:39.050 --> 12:58:39.060 align:start position:0% and Cisco have their own version of 12:58:39.060 --> 12:58:40.970 align:start position:0% and Cisco have their own version of ergrp 12:58:40.970 --> 12:58:40.980 align:start position:0% ergrp 12:58:40.980 --> 12:58:44.870 align:start position:0% ergrp now<12:58:41.700> considering<12:58:42.480> now<12:58:43.020> ergb<12:58:43.680> ergrp<12:58:44.640> can 12:58:44.870 --> 12:58:44.880 align:start position:0% now considering now ergb ergrp can 12:58:44.880 --> 12:58:46.550 align:start position:0% now considering now ergb ergrp can actually<12:58:45.000> use<12:58:45.240> five<12:58:45.540> but<12:58:45.840> we've<12:58:46.080> only<12:58:46.200> listed 12:58:46.550 --> 12:58:46.560 align:start position:0% actually use five but we've only listed 12:58:46.560 --> 12:58:48.650 align:start position:0% actually use five but we've only listed the<12:58:46.680> two<12:58:46.860> used<12:58:47.040> by<12:58:47.276> Cisco<12:58:47.640> devices<12:58:48.060> here<12:58:48.360> which 12:58:48.650 --> 12:58:48.660 align:start position:0% the two used by Cisco devices here which 12:58:48.660 --> 12:58:52.190 align:start position:0% the two used by Cisco devices here which are<12:58:48.840> bandwidth<12:58:49.680> and<12:58:49.740> delay 12:58:52.190 --> 12:58:52.200 align:start position:0% 12:58:52.200 --> 12:58:54.230 align:start position:0% now<12:58:52.560> considering<12:58:53.040> the<12:58:53.160> link<12:58:53.276> speeds<12:58:53.756> path<12:58:54.000> Y 12:58:54.230 --> 12:58:54.240 align:start position:0% now considering the link speeds path Y 12:58:54.240 --> 12:58:56.330 align:start position:0% now considering the link speeds path Y is<12:58:54.480> better<12:58:54.720> because<12:58:55.500> we<12:58:55.800> want<12:58:55.916> to<12:58:56.040> take<12:58:56.160> the 12:58:56.330 --> 12:58:56.340 align:start position:0% is better because we want to take the 12:58:56.340 --> 12:58:57.406 align:start position:0% is better because we want to take the faster 12:58:57.406 --> 12:58:57.416 align:start position:0% faster 12:58:57.416 --> 12:58:59.086 align:start position:0% faster um<12:58:57.480> route<12:58:57.776> there 12:58:59.086 --> 12:58:59.096 align:start position:0% um route there 12:58:59.096 --> 12:59:01.850 align:start position:0% um route there routine<12:58:59.820> can<12:59:00.300> be<12:59:00.416> based<12:59:00.776> on<12:59:01.080> the<12:59:01.560> following 12:59:01.850 --> 12:59:01.860 align:start position:0% routine can be based on the following 12:59:01.860 --> 12:59:04.070 align:start position:0% routine can be based on the following factors<12:59:02.276> the<12:59:02.640> MTU 12:59:04.070 --> 12:59:04.080 align:start position:0% factors the MTU 12:59:04.080 --> 12:59:08.390 align:start position:0% factors the MTU the<12:59:04.616> costs<12:59:05.040> cost<12:59:06.380> latency<12:59:07.400> administrative 12:59:08.390 --> 12:59:08.400 align:start position:0% the costs cost latency administrative 12:59:08.400 --> 12:59:12.586 align:start position:0% the costs cost latency administrative distance<12:59:08.960> shortest<12:59:09.960> path<12:59:10.200> bridging 12:59:12.586 --> 12:59:12.596 align:start position:0% distance shortest path bridging 12:59:12.596 --> 12:59:14.810 align:start position:0% distance shortest path bridging uh<12:59:13.200> the<12:59:13.436> MTU 12:59:14.810 --> 12:59:14.820 align:start position:0% uh the MTU 12:59:14.820 --> 12:59:16.370 align:start position:0% uh the MTU um<12:59:14.936> is<12:59:15.300> one<12:59:15.416> factor<12:59:15.840> as<12:59:15.960> I've<12:59:16.080> mentioned 12:59:16.370 --> 12:59:16.380 align:start position:0% um is one factor as I've mentioned 12:59:16.380 --> 12:59:18.170 align:start position:0% um is one factor as I've mentioned stands<12:59:16.860> for<12:59:16.980> maximum<12:59:17.400> transmission<12:59:17.640> unit 12:59:18.170 --> 12:59:18.180 align:start position:0% stands for maximum transmission unit 12:59:18.180 --> 12:59:20.570 align:start position:0% stands for maximum transmission unit this<12:59:19.080> is<12:59:19.200> the<12:59:19.380> largest<12:59:19.680> size<12:59:19.916> of<12:59:20.096> the<12:59:20.276> packet 12:59:20.570 --> 12:59:20.580 align:start position:0% this is the largest size of the packet 12:59:20.580 --> 12:59:22.550 align:start position:0% this is the largest size of the packet that<12:59:20.820> can<12:59:21.000> be<12:59:21.180> transmitted<12:59:21.840> across<12:59:22.256> the<12:59:22.380> link 12:59:22.550 --> 12:59:22.560 align:start position:0% that can be transmitted across the link 12:59:22.560 --> 12:59:25.426 align:start position:0% that can be transmitted across the link without<12:59:23.520> that<12:59:23.880> packet<12:59:24.240> being<12:59:24.436> fragmented 12:59:25.426 --> 12:59:25.436 align:start position:0% without that packet being fragmented 12:59:25.436 --> 12:59:27.470 align:start position:0% without that packet being fragmented fragmented<12:59:26.340> means<12:59:26.640> it<12:59:26.756> gets<12:59:27.000> chopped<12:59:27.360> into 12:59:27.470 --> 12:59:27.480 align:start position:0% fragmented means it gets chopped into 12:59:27.480 --> 12:59:29.450 align:start position:0% fragmented means it gets chopped into different<12:59:27.960> sizes 12:59:29.450 --> 12:59:29.460 align:start position:0% different sizes 12:59:29.460 --> 12:59:32.510 align:start position:0% different sizes and<12:59:30.060> numbered<12:59:30.660> sent<12:59:31.436> and<12:59:31.740> then<12:59:31.860> reassembled 12:59:32.510 --> 12:59:32.520 align:start position:0% and numbered sent and then reassembled 12:59:32.520 --> 12:59:34.670 align:start position:0% and numbered sent and then reassembled on<12:59:32.640> the<12:59:32.820> other<12:59:32.936> side<12:59:33.180> of<12:59:33.360> the<12:59:33.596> link<12:59:33.776> and 12:59:34.670 --> 12:59:34.680 align:start position:0% on the other side of the link and 12:59:34.680 --> 12:59:36.530 align:start position:0% on the other side of the link and obviously<12:59:34.980> this<12:59:35.340> can<12:59:35.700> introduce<12:59:36.060> the<12:59:36.240> scope 12:59:36.530 --> 12:59:36.540 align:start position:0% obviously this can introduce the scope 12:59:36.540 --> 12:59:38.650 align:start position:0% obviously this can introduce the scope for<12:59:36.720> errors<12:59:37.080> and<12:59:37.560> obviously<12:59:37.916> there's<12:59:38.160> delay 12:59:38.650 --> 12:59:38.660 align:start position:0% for errors and obviously there's delay 12:59:38.660 --> 12:59:42.650 align:start position:0% for errors and obviously there's delay while<12:59:39.660> this<12:59:39.900> fragmentation<12:59:40.436> takes<12:59:40.860> place 12:59:42.650 --> 12:59:42.660 align:start position:0% while this fragmentation takes place 12:59:42.660 --> 12:59:45.290 align:start position:0% while this fragmentation takes place thank<12:59:43.200> you<12:59:43.560> also<12:59:44.276> overhead<12:59:44.640> involved<12:59:45.116> because 12:59:45.290 --> 12:59:45.300 align:start position:0% thank you also overhead involved because 12:59:45.300 --> 12:59:47.390 align:start position:0% thank you also overhead involved because of<12:59:45.596> the<12:59:45.900> acknowledgments<12:59:46.560> each<12:59:46.800> packet<12:59:47.220> is 12:59:47.390 --> 12:59:47.400 align:start position:0% of the acknowledgments each packet is 12:59:47.400 --> 12:59:49.790 align:start position:0% of the acknowledgments each packet is sent<12:59:47.640> and<12:59:48.540> received<12:59:49.020> as<12:59:49.140> it<12:59:49.256> goes<12:59:49.500> along<12:59:49.560> and 12:59:49.790 --> 12:59:49.800 align:start position:0% sent and received as it goes along and 12:59:49.800 --> 12:59:50.990 align:start position:0% sent and received as it goes along and it<12:59:49.916> could<12:59:50.040> be<12:59:50.160> requested<12:59:50.700> to<12:59:50.880> be 12:59:50.990 --> 12:59:51.000 align:start position:0% it could be requested to be 12:59:51.000 --> 12:59:53.210 align:start position:0% it could be requested to be re-transmitted<12:59:51.840> also 12:59:53.210 --> 12:59:53.220 align:start position:0% re-transmitted also 12:59:53.220 --> 12:59:55.130 align:start position:0% re-transmitted also largest<12:59:53.820> packet<12:59:54.180> you<12:59:54.416> can<12:59:54.540> send<12:59:54.776> by<12:59:54.960> an 12:59:55.130 --> 12:59:55.140 align:start position:0% largest packet you can send by an 12:59:55.140 --> 12:59:56.746 align:start position:0% largest packet you can send by an Ethernet<12:59:55.320> Network<12:59:55.680> because<12:59:56.096> of<12:59:56.276> the<12:59:56.400> way<12:59:56.520> the 12:59:56.746 --> 12:59:56.756 align:start position:0% Ethernet Network because of the way the 12:59:56.756 --> 13:00:01.550 align:start position:0% Ethernet Network because of the way the technology<12:59:57.116> is<12:59:57.416> designed<12:59:57.960> is<12:59:58.680> a<12:59:59.040> 1500<12:59:59.640> byte 13:00:01.550 --> 13:00:01.560 align:start position:0% technology is designed is a 1500 byte 13:00:01.560 --> 13:00:04.246 align:start position:0% technology is designed is a 1500 byte now<13:00:02.096> cost<13:00:02.400> I<13:00:02.880> actually<13:00:03.060> did<13:00:03.416> an<13:00:03.596> output<13:00:03.960> here 13:00:04.246 --> 13:00:04.256 align:start position:0% now cost I actually did an output here 13:00:04.256 --> 13:00:07.970 align:start position:0% now cost I actually did an output here of<13:00:04.860> a<13:00:05.220> router<13:00:05.936> running<13:00:06.360> ospf<13:00:07.200> or<13:00:07.436> an<13:00:07.616> interface 13:00:07.970 --> 13:00:07.980 align:start position:0% of a router running ospf or an interface 13:00:07.980 --> 13:00:09.950 align:start position:0% of a router running ospf or an interface running<13:00:08.276> ospf<13:00:08.936> here 13:00:09.950 --> 13:00:09.960 align:start position:0% running ospf here 13:00:09.960 --> 13:00:12.350 align:start position:0% running ospf here and<13:00:10.436> you<13:00:10.616> can<13:00:10.740> see<13:00:10.980> the<13:00:11.400> other<13:00:11.520> information<13:00:11.880> is 13:00:12.350 --> 13:00:12.360 align:start position:0% and you can see the other information is 13:00:12.360 --> 13:00:14.210 align:start position:0% and you can see the other information is irrelevant<13:00:12.840> for<13:00:13.080> our<13:00:13.200> purposes<13:00:13.560> but<13:00:13.860> the<13:00:14.096> cost 13:00:14.210 --> 13:00:14.220 align:start position:0% irrelevant for our purposes but the cost 13:00:14.220 --> 13:00:17.570 align:start position:0% irrelevant for our purposes but the cost has<13:00:14.520> been<13:00:14.700> allocated<13:00:15.240> as<13:00:16.020> 64.<13:00:16.860> different 13:00:17.570 --> 13:00:17.580 align:start position:0% has been allocated as 64. different 13:00:17.580 --> 13:00:19.370 align:start position:0% has been allocated as 64. different interface<13:00:18.116> speeds<13:00:18.596> are<13:00:18.776> given<13:00:19.140> different 13:00:19.370 --> 13:00:19.380 align:start position:0% interface speeds are given different 13:00:19.380 --> 13:00:25.310 align:start position:0% interface speeds are given different costs<13:00:19.980> by<13:00:20.700> ospf 13:00:25.310 --> 13:00:25.320 align:start position:0% 13:00:25.320 --> 13:00:27.890 align:start position:0% total<13:00:26.160> cost<13:00:26.400> so<13:00:26.880> this<13:00:27.116> link<13:00:27.360> and<13:00:27.660> the<13:00:27.840> other 13:00:27.890 --> 13:00:27.900 align:start position:0% total cost so this link and the other 13:00:27.900 --> 13:00:30.530 align:start position:0% total cost so this link and the other link<13:00:28.140> and<13:00:28.380> all<13:00:28.560> the<13:00:28.616> other<13:00:28.740> links<13:00:29.040> between<13:00:29.540> and 13:00:30.530 --> 13:00:30.540 align:start position:0% link and all the other links between and 13:00:30.540 --> 13:00:32.810 align:start position:0% link and all the other links between and the<13:00:30.840> hosts<13:00:31.256> are<13:00:31.500> added<13:00:31.860> up<13:00:31.980> together<13:00:32.220> and<13:00:32.700> then 13:00:32.810 --> 13:00:32.820 align:start position:0% the hosts are added up together and then 13:00:32.820 --> 13:00:35.870 align:start position:0% the hosts are added up together and then the<13:00:33.116> best<13:00:33.300> cast<13:00:34.200> which<13:00:34.560> is<13:00:34.680> the<13:00:34.860> lowest<13:00:35.160> one<13:00:35.400> is 13:00:35.870 --> 13:00:35.880 align:start position:0% the best cast which is the lowest one is 13:00:35.880 --> 13:00:38.390 align:start position:0% the best cast which is the lowest one is installed<13:00:36.360> into<13:00:36.480> the<13:00:36.720> routing<13:00:37.020> table<13:00:37.320> and<13:00:38.220> the 13:00:38.390 --> 13:00:38.400 align:start position:0% installed into the routing table and the 13:00:38.400 --> 13:00:39.650 align:start position:0% installed into the routing table and the other<13:00:38.520> costs 13:00:39.650 --> 13:00:39.660 align:start position:0% other costs 13:00:39.660 --> 13:00:41.710 align:start position:0% other costs um<13:00:39.776> can<13:00:40.020> be<13:00:40.200> put<13:00:40.320> into<13:00:40.500> the<13:00:40.740> topology<13:00:41.160> table 13:00:41.710 --> 13:00:41.720 align:start position:0% um can be put into the topology table 13:00:41.720 --> 13:00:44.870 align:start position:0% um can be put into the topology table for<13:00:42.720> use<13:00:42.840> if<13:00:43.140> the<13:00:43.320> best<13:00:43.560> path<13:00:43.916> goes<13:00:44.460> down<13:00:44.640> so 13:00:44.870 --> 13:00:44.880 align:start position:0% for use if the best path goes down so 13:00:44.880 --> 13:00:47.330 align:start position:0% for use if the best path goes down so you<13:00:45.060> can<13:00:45.116> have<13:00:45.300> second<13:00:45.596> best<13:00:46.380> third<13:00:46.740> best<13:00:46.980> and 13:00:47.330 --> 13:00:47.340 align:start position:0% you can have second best third best and 13:00:47.340 --> 13:00:49.906 align:start position:0% you can have second best third best and so<13:00:47.520> on 13:00:49.906 --> 13:00:49.916 align:start position:0% 13:00:49.916 --> 13:00:52.370 align:start position:0% a<13:00:50.220> router<13:00:50.580> protocol<13:00:50.936> can<13:00:51.416> also<13:00:51.660> use<13:00:51.776> delay<13:00:52.200> or 13:00:52.370 --> 13:00:52.380 align:start position:0% a router protocol can also use delay or 13:00:52.380 --> 13:00:54.650 align:start position:0% a router protocol can also use delay or latency<13:00:52.800> as<13:00:53.096> a<13:00:53.220> metric 13:00:54.650 --> 13:00:54.660 align:start position:0% latency as a metric 13:00:54.660 --> 13:00:57.106 align:start position:0% latency as a metric delay<13:00:55.436> refers<13:00:55.860> to<13:00:55.980> the<13:00:56.160> delay<13:00:56.520> of<13:00:56.700> the<13:00:56.820> links 13:00:57.106 --> 13:00:57.116 align:start position:0% delay refers to the delay of the links 13:00:57.116 --> 13:01:00.050 align:start position:0% delay refers to the delay of the links across<13:00:57.540> the<13:00:57.660> route<13:00:57.840> so<13:00:58.256> is<13:00:59.040> there<13:00:59.160> any<13:00:59.340> delays 13:01:00.050 --> 13:01:00.060 align:start position:0% across the route so is there any delays 13:01:00.060 --> 13:01:02.630 align:start position:0% across the route so is there any delays to<13:01:00.180> the<13:01:00.300> packets<13:01:00.596> been<13:01:00.840> sent<13:01:01.020> and<13:01:01.200> received 13:01:02.630 --> 13:01:02.640 align:start position:0% to the packets been sent and received 13:01:02.640 --> 13:01:04.906 align:start position:0% to the packets been sent and received a<13:01:03.416> load<13:01:03.840> I've<13:01:04.020> actually<13:01:04.256> issued<13:01:04.616> a<13:01:04.740> show 13:01:04.906 --> 13:01:04.916 align:start position:0% a load I've actually issued a show 13:01:04.916 --> 13:01:07.730 align:start position:0% a load I've actually issued a show interfaces<13:01:05.580> serial<13:01:06.180> zero<13:01:06.840> slash<13:01:07.080> one<13:01:07.320> on<13:01:07.560> this 13:01:07.730 --> 13:01:07.740 align:start position:0% interfaces serial zero slash one on this 13:01:07.740 --> 13:01:09.766 align:start position:0% interfaces serial zero slash one on this router<13:01:08.220> and<13:01:09.000> you<13:01:09.116> can<13:01:09.240> see<13:01:09.360> some<13:01:09.540> of<13:01:09.720> the 13:01:09.766 --> 13:01:09.776 align:start position:0% router and you can see some of the 13:01:09.776 --> 13:01:12.890 align:start position:0% router and you can see some of the metrics<13:01:10.320> that<13:01:10.980> are<13:01:11.276> allocated 13:01:12.890 --> 13:01:12.900 align:start position:0% metrics that are allocated 13:01:12.900 --> 13:01:15.950 align:start position:0% metrics that are allocated to<13:01:13.436> this<13:01:13.740> particular<13:01:13.980> interface<13:01:14.580> the<13:01:15.416> mtus 13:01:15.950 --> 13:01:15.960 align:start position:0% to this particular interface the mtus 13:01:15.960 --> 13:01:21.130 align:start position:0% to this particular interface the mtus 1500<13:01:16.560> the<13:01:16.800> bandwidth<13:01:17.276> is<13:01:17.400> 1544<13:01:18.300> so<13:01:18.720> one<13:01:19.080> Meg 13:01:21.130 --> 13:01:21.140 align:start position:0% 1500 the bandwidth is 1544 so one Meg 13:01:21.140 --> 13:01:25.730 align:start position:0% 1500 the bandwidth is 1544 so one Meg delay<13:01:22.140> and<13:01:22.860> twenty<13:01:23.460> thousand<13:01:24.000> millisecs 13:01:25.730 --> 13:01:25.740 align:start position:0% delay and twenty thousand millisecs 13:01:25.740 --> 13:01:30.406 align:start position:0% delay and twenty thousand millisecs a<13:01:26.276> reliability<13:01:27.140> 255<13:01:28.140> out<13:01:28.436> of<13:01:28.560> 255<13:01:29.040> is<13:01:29.400> the<13:01:29.640> best 13:01:30.406 --> 13:01:30.416 align:start position:0% a reliability 255 out of 255 is the best 13:01:30.416 --> 13:01:33.106 align:start position:0% a reliability 255 out of 255 is the best it<13:01:30.960> means<13:01:31.560> um<13:01:31.560> it's<13:01:31.860> very<13:01:32.096> reliable<13:01:32.580> and<13:01:32.936> that 13:01:33.106 --> 13:01:33.116 align:start position:0% it means um it's very reliable and that 13:01:33.116 --> 13:01:35.926 align:start position:0% it means um it's very reliable and that if<13:01:33.360> there's<13:01:33.596> problems<13:01:34.080> then<13:01:34.380> the<13:01:34.740> number<13:01:35.520> goes 13:01:35.926 --> 13:01:35.936 align:start position:0% if there's problems then the number goes 13:01:35.936 --> 13:01:38.030 align:start position:0% if there's problems then the number goes down<13:01:36.116> like<13:01:36.480> 10<13:01:36.776> out<13:01:37.020> of<13:01:37.140> two<13:01:37.320> five<13:01:37.616> five<13:01:37.800> is 13:01:38.030 --> 13:01:38.040 align:start position:0% down like 10 out of two five five is 13:01:38.040 --> 13:01:39.050 align:start position:0% down like 10 out of two five five is very<13:01:38.276> bad 13:01:39.050 --> 13:01:39.060 align:start position:0% very bad 13:01:39.060 --> 13:01:41.390 align:start position:0% very bad the<13:01:39.596> transmission<13:01:39.776> load<13:01:40.380> is<13:01:40.616> low<13:01:40.860> it's<13:01:41.220> the 13:01:41.390 --> 13:01:41.400 align:start position:0% the transmission load is low it's the 13:01:41.400 --> 13:01:43.670 align:start position:0% the transmission load is low it's the lowest<13:01:41.700> one<13:01:42.000> out<13:01:42.180> of<13:01:42.300> two<13:01:42.416> five<13:01:42.660> five<13:01:42.900> receive 13:01:43.670 --> 13:01:43.680 align:start position:0% lowest one out of two five five receive 13:01:43.680 --> 13:01:46.190 align:start position:0% lowest one out of two five five receive load<13:01:44.096> is<13:01:44.220> one<13:01:44.400> out<13:01:44.640> of<13:01:44.756> two<13:01:44.936> five<13:01:45.240> five 13:01:46.190 --> 13:01:46.200 align:start position:0% load is one out of two five five 13:01:46.200 --> 13:01:49.070 align:start position:0% load is one out of two five five which<13:01:46.560> is<13:01:46.616> an<13:01:46.800> arbitrary<13:01:47.340> value 13:01:49.070 --> 13:01:49.080 align:start position:0% which is an arbitrary value 13:01:49.080 --> 13:01:50.510 align:start position:0% which is an arbitrary value so<13:01:49.500> load<13:01:49.800> is<13:01:49.860> the<13:01:49.980> measure<13:01:50.220> of<13:01:50.340> traffic 13:01:50.510 --> 13:01:50.520 align:start position:0% so load is the measure of traffic 13:01:50.520 --> 13:01:52.246 align:start position:0% so load is the measure of traffic consuming<13:01:51.116> the<13:01:51.300> links<13:01:51.596> we<13:01:51.840> don't<13:01:51.960> want<13:01:52.080> our 13:01:52.246 --> 13:01:52.256 align:start position:0% consuming the links we don't want our 13:01:52.256 --> 13:01:53.746 align:start position:0% consuming the links we don't want our package<13:01:52.500> to<13:01:52.616> be<13:01:52.740> traveling<13:01:53.096> along<13:01:53.276> a<13:01:53.580> path 13:01:53.746 --> 13:01:53.756 align:start position:0% package to be traveling along a path 13:01:53.756 --> 13:01:56.030 align:start position:0% package to be traveling along a path with<13:01:54.480> high<13:01:54.660> traffic 13:01:56.030 --> 13:01:56.040 align:start position:0% with high traffic 13:01:56.040 --> 13:01:58.130 align:start position:0% with high traffic so<13:01:56.460> the<13:01:56.640> past<13:01:56.820> with<13:01:57.060> the<13:01:57.240> lowest<13:01:57.540> load<13:01:57.900> would 13:01:58.130 --> 13:01:58.140 align:start position:0% so the past with the lowest load would 13:01:58.140 --> 13:02:00.406 align:start position:0% so the past with the lowest load would be<13:01:58.256> the<13:01:58.436> best<13:01:58.560> path<13:01:58.860> if<13:01:59.520> we're<13:01:59.640> using<13:01:59.936> load<13:02:00.300> as 13:02:00.406 --> 13:02:00.416 align:start position:0% be the best path if we're using load as 13:02:00.416 --> 13:02:02.390 align:start position:0% be the best path if we're using load as a<13:02:00.540> metric<13:02:00.840> of<13:02:01.080> course 13:02:02.390 --> 13:02:02.400 align:start position:0% a metric of course 13:02:02.400 --> 13:02:04.730 align:start position:0% a metric of course reliability<13:02:03.360> is<13:02:03.660> in<13:02:03.840> there<13:02:03.960> also<13:02:04.320> which<13:02:04.560> I've 13:02:04.730 --> 13:02:04.740 align:start position:0% reliability is in there also which I've 13:02:04.740 --> 13:02:06.650 align:start position:0% reliability is in there also which I've discussed<13:02:05.220> we<13:02:05.820> want<13:02:05.936> to<13:02:06.116> take<13:02:06.240> into 13:02:06.650 --> 13:02:06.660 align:start position:0% discussed we want to take into 13:02:06.660 --> 13:02:08.390 align:start position:0% discussed we want to take into consideration<13:02:07.200> the<13:02:07.500> reliability<13:02:07.980> of<13:02:08.276> the 13:02:08.390 --> 13:02:08.400 align:start position:0% consideration the reliability of the 13:02:08.400 --> 13:02:09.470 align:start position:0% consideration the reliability of the path 13:02:09.470 --> 13:02:09.480 align:start position:0% path 13:02:09.480 --> 13:02:12.586 align:start position:0% path reliability<13:02:10.380> metric<13:02:11.096> has<13:02:11.520> a<13:02:12.000> value<13:02:12.300> that 13:02:12.586 --> 13:02:12.596 align:start position:0% reliability metric has a value that 13:02:12.596 --> 13:02:14.690 align:start position:0% reliability metric has a value that denotes<13:02:13.020> a<13:02:13.140> number<13:02:13.256> of<13:02:13.436> times<13:02:13.680> any<13:02:14.460> of<13:02:14.640> the 13:02:14.690 --> 13:02:14.700 align:start position:0% denotes a number of times any of the 13:02:14.700 --> 13:02:17.690 align:start position:0% denotes a number of times any of the following<13:02:15.000> occurs<13:02:15.540> the<13:02:16.140> link<13:02:16.320> goes<13:02:16.800> down<13:02:17.040> or 13:02:17.690 --> 13:02:17.700 align:start position:0% following occurs the link goes down or 13:02:17.700 --> 13:02:22.010 align:start position:0% following occurs the link goes down or had<13:02:17.936> errors<13:02:18.300> at<13:02:18.540> a<13:02:18.840> certain<13:02:19.020> period<13:02:19.436> of<13:02:19.616> time 13:02:22.010 --> 13:02:22.020 align:start position:0% 13:02:22.020 --> 13:02:24.106 align:start position:0% the<13:02:22.860> router<13:02:23.160> protocol<13:02:23.520> may<13:02:23.756> use<13:02:23.936> the 13:02:24.106 --> 13:02:24.116 align:start position:0% the router protocol may use the 13:02:24.116 --> 13:02:27.170 align:start position:0% the router protocol may use the following<13:02:24.540> one<13:02:25.080> metric<13:02:25.436> as<13:02:25.740> in<13:02:25.980> rip<13:02:26.276> multiple 13:02:27.170 --> 13:02:27.180 align:start position:0% following one metric as in rip multiple 13:02:27.180 --> 13:02:30.106 align:start position:0% following one metric as in rip multiple link<13:02:27.616> characteristics<13:02:28.616> to<13:02:29.460> calculate<13:02:29.880> a 13:02:30.106 --> 13:02:30.116 align:start position:0% link characteristics to calculate a 13:02:30.116 --> 13:02:33.350 align:start position:0% link characteristics to calculate a metric<13:02:30.720> for<13:02:31.616> example<13:02:32.000> ergrp<13:02:33.000> which<13:02:33.240> is 13:02:33.350 --> 13:02:33.360 align:start position:0% metric for example ergrp which is 13:02:33.360 --> 13:02:37.030 align:start position:0% metric for example ergrp which is bandwidth<13:02:33.900> and<13:02:34.020> delay<13:02:34.256> of<13:02:34.436> the<13:02:34.616> line 13:02:37.030 --> 13:02:37.040 align:start position:0% 13:02:37.040 --> 13:02:40.130 align:start position:0% ergp<13:02:38.040> uses<13:02:38.460> characteristics<13:02:39.180> to<13:02:39.480> calculate<13:02:39.900> a 13:02:40.130 --> 13:02:40.140 align:start position:0% ergp uses characteristics to calculate a 13:02:40.140 --> 13:02:43.390 align:start position:0% ergp uses characteristics to calculate a metric<13:02:40.500> for<13:02:40.680> best<13:02:40.860> path<13:02:41.160> I've<13:02:42.116> actually 13:02:43.390 --> 13:02:43.400 align:start position:0% metric for best path I've actually 13:02:43.400 --> 13:02:47.330 align:start position:0% metric for best path I've actually done<13:02:44.400> a<13:02:44.700> output<13:02:45.360> of<13:02:45.596> a<13:02:45.776> Cisco<13:02:46.140> router<13:02:46.616> here 13:02:47.330 --> 13:02:47.340 align:start position:0% done a output of a Cisco router here 13:02:47.340 --> 13:02:49.670 align:start position:0% done a output of a Cisco router here for<13:02:47.756> ergrp<13:02:48.596> and<13:02:48.960> you<13:02:49.020> can<13:02:49.140> see<13:02:49.320> the<13:02:49.500> different 13:02:49.670 --> 13:02:49.680 align:start position:0% for ergrp and you can see the different 13:02:49.680 --> 13:02:53.150 align:start position:0% for ergrp and you can see the different metrics<13:02:50.220> here<13:02:50.400> some<13:02:50.880> won't<13:02:51.180> be<13:02:51.416> used 13:02:53.150 --> 13:02:53.160 align:start position:0% metrics here some won't be used 13:02:53.160 --> 13:02:55.970 align:start position:0% metrics here some won't be used you<13:02:53.520> can<13:02:53.580> actually<13:02:53.840> affect<13:02:54.840> this<13:02:55.140> if<13:02:55.740> you<13:02:55.860> want 13:02:55.970 --> 13:02:55.980 align:start position:0% you can actually affect this if you want 13:02:55.980 --> 13:02:58.310 align:start position:0% you can actually affect this if you want in<13:02:56.220> the<13:02:56.340> configuration<13:02:56.820> normally<13:02:57.720> best<13:02:58.020> to 13:02:58.310 --> 13:02:58.320 align:start position:0% in the configuration normally best to 13:02:58.320 --> 13:03:01.130 align:start position:0% in the configuration normally best to speak<13:02:58.680> to<13:02:58.916> a<13:02:59.520> Cisco<13:03:00.116> engineer<13:03:00.540> before<13:03:00.720> you<13:03:00.960> do 13:03:01.130 --> 13:03:01.140 align:start position:0% speak to a Cisco engineer before you do 13:03:01.140 --> 13:03:02.990 align:start position:0% speak to a Cisco engineer before you do this 13:03:02.990 --> 13:03:03.000 align:start position:0% this 13:03:03.000 --> 13:03:05.450 align:start position:0% this so<13:03:03.416> some<13:03:03.596> of<13:03:03.776> the<13:03:03.900> delay<13:03:04.200> characteristics<13:03:04.980> are 13:03:05.450 --> 13:03:05.460 align:start position:0% so some of the delay characteristics are 13:03:05.460 --> 13:03:10.150 align:start position:0% so some of the delay characteristics are delay<13:03:06.140> bandwidth<13:03:07.140> reliability<13:03:07.800> load 13:03:10.150 --> 13:03:10.160 align:start position:0% delay bandwidth reliability load 13:03:10.160 --> 13:03:12.890 align:start position:0% delay bandwidth reliability load and<13:03:11.160> you<13:03:11.460> can<13:03:11.580> see<13:03:11.700> others<13:03:12.180> in<13:03:12.300> there<13:03:12.480> but 13:03:12.890 --> 13:03:12.900 align:start position:0% and you can see others in there but 13:03:12.900 --> 13:03:14.510 align:start position:0% and you can see others in there but again<13:03:13.080> it's<13:03:13.256> bandwidth<13:03:13.800> And<13:03:13.860> Delay<13:03:14.096> the<13:03:14.340> line 13:03:14.510 --> 13:03:14.520 align:start position:0% again it's bandwidth And Delay the line 13:03:14.520 --> 13:03:17.570 align:start position:0% again it's bandwidth And Delay the line is<13:03:14.756> usually<13:03:15.180> used 13:03:17.570 --> 13:03:17.580 align:start position:0% 13:03:17.580 --> 13:03:20.210 align:start position:0% uh<13:03:18.360> summary<13:03:18.660> so<13:03:19.080> far<13:03:19.256> we've<13:03:19.436> covered<13:03:19.800> routing 13:03:20.210 --> 13:03:20.220 align:start position:0% uh summary so far we've covered routing 13:03:20.220 --> 13:03:22.370 align:start position:0% uh summary so far we've covered routing metrics<13:03:20.700> the<13:03:21.060> MTU 13:03:22.370 --> 13:03:22.380 align:start position:0% metrics the MTU 13:03:22.380 --> 13:03:27.050 align:start position:0% metrics the MTU metric<13:03:22.980> costs<13:03:23.480> uh<13:03:24.480> latency<13:03:24.960> load<13:03:26.060> reliability 13:03:27.050 --> 13:03:27.060 align:start position:0% metric costs uh latency load reliability 13:03:27.060 --> 13:03:29.150 align:start position:0% metric costs uh latency load reliability so<13:03:28.020> that's<13:03:28.140> all<13:03:28.320> we<13:03:28.436> need<13:03:28.560> to<13:03:28.680> know<13:03:28.800> for<13:03:28.980> now 13:03:29.150 --> 13:03:29.160 align:start position:0% so that's all we need to know for now 13:03:29.160 --> 13:03:35.290 align:start position:0% so that's all we need to know for now thanks<13:03:29.520> for<13:03:29.700> watching 13:03:35.290 --> 13:03:35.300 align:start position:0% 13:03:35.300 --> 13:03:51.050 align:start position:0% [Music] 13:03:51.050 --> 13:03:51.060 align:start position:0% 13:03:51.060 --> 13:03:54.290 align:start position:0% welcome<13:03:51.660> to<13:03:51.900> module<13:03:52.256> 8<13:03:52.436> lesson<13:03:52.980> 3B<13:03:53.640> routing 13:03:54.290 --> 13:03:54.300 align:start position:0% welcome to module 8 lesson 3B routing 13:03:54.300 --> 13:03:55.370 align:start position:0% welcome to module 8 lesson 3B routing tables 13:03:55.370 --> 13:03:55.380 align:start position:0% tables 13:03:55.380 --> 13:03:57.230 align:start position:0% tables another<13:03:55.800> hard<13:03:56.160> one<13:03:56.340> to<13:03:56.520> put<13:03:56.640> in<13:03:56.820> perspective 13:03:57.230 --> 13:03:57.240 align:start position:0% another hard one to put in perspective 13:03:57.240 --> 13:03:58.906 align:start position:0% another hard one to put in perspective if<13:03:57.540> we<13:03:57.720> don't<13:03:57.900> configure 13:03:58.906 --> 13:03:58.916 align:start position:0% if we don't configure 13:03:58.916 --> 13:04:01.850 align:start position:0% if we don't configure live<13:03:59.520> routers<13:04:00.116> but<13:04:00.596> we'll<13:04:01.020> do<13:04:01.200> our<13:04:01.380> best<13:04:01.560> we're 13:04:01.850 --> 13:04:01.860 align:start position:0% live routers but we'll do our best we're 13:04:01.860 --> 13:04:03.290 align:start position:0% live routers but we'll do our best we're going<13:04:01.980> to<13:04:02.040> look<13:04:02.160> at<13:04:02.276> routing<13:04:02.640> the<13:04:02.880> routing 13:04:03.290 --> 13:04:03.300 align:start position:0% going to look at routing the routing 13:04:03.300 --> 13:04:04.550 align:start position:0% going to look at routing the routing table 13:04:04.550 --> 13:04:04.560 align:start position:0% table 13:04:04.560 --> 13:04:07.210 align:start position:0% table static<13:04:05.220> routes<13:04:05.580> and<13:04:05.756> a<13:04:05.936> static<13:04:06.300> route<13:04:06.480> example 13:04:07.210 --> 13:04:07.220 align:start position:0% static routes and a static route example 13:04:07.220 --> 13:04:11.150 align:start position:0% static routes and a static route example and<13:04:08.220> dynamic<13:04:08.700> routing<13:04:09.116> protocols<13:04:09.776> only<13:04:10.160> an 13:04:11.150 --> 13:04:11.160 align:start position:0% and dynamic routing protocols only an 13:04:11.160 --> 13:04:13.850 align:start position:0% and dynamic routing protocols only an overview<13:04:11.520> really<13:04:11.880> and<13:04:12.240> then<13:04:12.360> an<13:04:12.540> example<13:04:12.960> and 13:04:13.850 --> 13:04:13.860 align:start position:0% overview really and then an example and 13:04:13.860 --> 13:04:16.490 align:start position:0% overview really and then an example and physically<13:04:14.276> connected<13:04:14.880> Networks 13:04:16.490 --> 13:04:16.500 align:start position:0% physically connected Networks 13:04:16.500 --> 13:04:19.790 align:start position:0% physically connected Networks so<13:04:17.096> routing<13:04:17.520> is<13:04:17.700> the<13:04:17.880> process<13:04:18.180> of<13:04:18.540> sending<13:04:19.080> a 13:04:19.790 --> 13:04:19.800 align:start position:0% so routing is the process of sending a 13:04:19.800 --> 13:04:22.790 align:start position:0% so routing is the process of sending a packet<13:04:20.460> from<13:04:20.640> a<13:04:20.756> source<13:04:21.116> Network<13:04:21.560> to<13:04:22.560> a 13:04:22.790 --> 13:04:22.800 align:start position:0% packet from a source Network to a 13:04:22.800 --> 13:04:25.670 align:start position:0% packet from a source Network to a destination<13:04:23.220> in<13:04:23.820> another<13:04:23.936> Network 13:04:25.670 --> 13:04:25.680 align:start position:0% destination in another Network 13:04:25.680 --> 13:04:27.170 align:start position:0% destination in another Network we<13:04:26.096> actually<13:04:26.276> have<13:04:26.460> to<13:04:26.580> differentiate 13:04:27.170 --> 13:04:27.180 align:start position:0% we actually have to differentiate 13:04:27.180 --> 13:04:29.510 align:start position:0% we actually have to differentiate between<13:04:27.480> routing<13:04:28.380> and<13:04:28.680> packet<13:04:29.040> switching 13:04:29.510 --> 13:04:29.520 align:start position:0% between routing and packet switching 13:04:29.520 --> 13:04:31.850 align:start position:0% between routing and packet switching writing<13:04:30.360> is<13:04:30.540> a<13:04:30.660> process<13:04:30.900> where<13:04:31.256> the<13:04:31.436> router 13:04:31.850 --> 13:04:31.860 align:start position:0% writing is a process where the router 13:04:31.860 --> 13:04:34.426 align:start position:0% writing is a process where the router actually<13:04:32.040> decides<13:04:32.640> the<13:04:32.756> best<13:04:33.060> route<13:04:33.416> to<13:04:34.320> get 13:04:34.426 --> 13:04:34.436 align:start position:0% actually decides the best route to get 13:04:34.436 --> 13:04:38.390 align:start position:0% actually decides the best route to get from<13:04:34.740> A<13:04:35.096> to<13:04:35.276> Z<13:04:35.580> and<13:04:36.480> then<13:04:36.660> switching<13:04:37.320> in<13:04:37.916> the<13:04:38.040> in 13:04:38.390 --> 13:04:38.400 align:start position:0% from A to Z and then switching in the in 13:04:38.400 --> 13:04:41.210 align:start position:0% from A to Z and then switching in the in the<13:04:38.580> context<13:04:38.880> of<13:04:39.116> sending<13:04:39.540> IP<13:04:40.020> packets<13:04:40.500> is 13:04:41.210 --> 13:04:41.220 align:start position:0% the context of sending IP packets is 13:04:41.220 --> 13:04:43.370 align:start position:0% the context of sending IP packets is actually<13:04:41.460> pushing<13:04:42.000> the<13:04:42.300> packet<13:04:43.020> out<13:04:43.200> of<13:04:43.320> the 13:04:43.370 --> 13:04:43.380 align:start position:0% actually pushing the packet out of the 13:04:43.380 --> 13:04:45.470 align:start position:0% actually pushing the packet out of the correct<13:04:43.616> interface<13:04:44.220> I<13:04:44.880> just<13:04:45.060> want<13:04:45.180> to<13:04:45.360> do 13:04:45.470 --> 13:04:45.480 align:start position:0% correct interface I just want to do 13:04:45.480 --> 13:04:48.310 align:start position:0% correct interface I just want to do highlight<13:04:45.960> the<13:04:46.200> difference<13:04:46.436> between<13:04:46.916> the<13:04:47.276> two 13:04:48.310 --> 13:04:48.320 align:start position:0% highlight the difference between the two 13:04:48.320 --> 13:04:50.690 align:start position:0% highlight the difference between the two and<13:04:49.320> obviously<13:04:49.800> we're<13:04:49.980> looking<13:04:50.276> at<13:04:50.520> Network 13:04:50.690 --> 13:04:50.700 align:start position:0% and obviously we're looking at Network 13:04:50.700 --> 13:04:53.030 align:start position:0% and obviously we're looking at Network plus<13:04:51.060> level<13:04:51.300> stuff<13:04:51.660> here<13:04:51.900> so<13:04:52.680> there's<13:04:52.860> two 13:04:53.030 --> 13:04:53.040 align:start position:0% plus level stuff here so there's two 13:04:53.040 --> 13:04:55.246 align:start position:0% plus level stuff here so there's two aspects<13:04:53.700> determining<13:04:54.240> the<13:04:54.416> optimal<13:04:54.900> route 13:04:55.246 --> 13:04:55.256 align:start position:0% aspects determining the optimal route 13:04:55.256 --> 13:04:57.406 align:start position:0% aspects determining the optimal route which<13:04:55.680> is<13:04:55.800> the<13:04:55.980> routing<13:04:56.340> part<13:04:56.640> and<13:04:57.300> then 13:04:57.406 --> 13:04:57.416 align:start position:0% which is the routing part and then 13:04:57.416 --> 13:04:58.906 align:start position:0% which is the routing part and then pushing<13:04:57.840> the<13:04:57.960> packet<13:04:58.320> through<13:04:58.560> the<13:04:58.800> network 13:04:58.906 --> 13:04:58.916 align:start position:0% pushing the packet through the network 13:04:58.916 --> 13:05:02.390 align:start position:0% pushing the packet through the network which<13:04:59.340> is<13:04:59.520> the<13:04:59.700> switching<13:05:00.116> part 13:05:02.390 --> 13:05:02.400 align:start position:0% which is the switching part 13:05:02.400 --> 13:05:04.730 align:start position:0% which is the switching part so<13:05:02.880> routes<13:05:03.300> are<13:05:03.416> based<13:05:03.720> on<13:05:03.776> networks<13:05:04.256> we<13:05:04.500> don't 13:05:04.730 --> 13:05:04.740 align:start position:0% so routes are based on networks we don't 13:05:04.740 --> 13:05:06.470 align:start position:0% so routes are based on networks we don't really 13:05:06.470 --> 13:05:06.480 align:start position:0% really 13:05:06.480 --> 13:05:07.190 align:start position:0% really um 13:05:07.190 --> 13:05:07.200 align:start position:0% um 13:05:07.200 --> 13:05:08.990 align:start position:0% um we<13:05:07.616> don't<13:05:07.860> want<13:05:08.040> to<13:05:08.096> concern<13:05:08.400> ourselves<13:05:08.756> with 13:05:08.990 --> 13:05:09.000 align:start position:0% we don't want to concern ourselves with 13:05:09.000 --> 13:05:10.730 align:start position:0% we don't want to concern ourselves with host<13:05:09.240> on<13:05:09.480> networks<13:05:10.080> because<13:05:10.256> if<13:05:10.500> you<13:05:10.616> can 13:05:10.730 --> 13:05:10.740 align:start position:0% host on networks because if you can 13:05:10.740 --> 13:05:13.370 align:start position:0% host on networks because if you can imagine<13:05:11.000> even<13:05:12.000> an<13:05:12.300> Enterprise<13:05:12.480> Network<13:05:12.960> for 13:05:13.370 --> 13:05:13.380 align:start position:0% imagine even an Enterprise Network for 13:05:13.380 --> 13:05:14.990 align:start position:0% imagine even an Enterprise Network for some<13:05:13.560> large<13:05:13.740> company<13:05:13.980> could<13:05:14.340> have<13:05:14.460> thousands 13:05:14.990 --> 13:05:15.000 align:start position:0% some large company could have thousands 13:05:15.000 --> 13:05:16.370 align:start position:0% some large company could have thousands of<13:05:15.116> hosts 13:05:16.370 --> 13:05:16.380 align:start position:0% of hosts 13:05:16.380 --> 13:05:18.586 align:start position:0% of hosts it'd<13:05:17.096> be<13:05:17.160> pointless<13:05:17.640> every<13:05:17.936> router<13:05:18.360> having 13:05:18.586 --> 13:05:18.596 align:start position:0% it'd be pointless every router having 13:05:18.596 --> 13:05:21.050 align:start position:0% it'd be pointless every router having thousands<13:05:19.320> of<13:05:19.436> hosts<13:05:20.276> listed<13:05:20.640> so<13:05:20.820> what<13:05:20.936> it 13:05:21.050 --> 13:05:21.060 align:start position:0% thousands of hosts listed so what it 13:05:21.060 --> 13:05:23.450 align:start position:0% thousands of hosts listed so what it wants<13:05:21.240> to<13:05:21.300> do<13:05:21.416> is<13:05:21.540> focus<13:05:21.840> on<13:05:22.020> Networks 13:05:23.450 --> 13:05:23.460 align:start position:0% wants to do is focus on Networks 13:05:23.460 --> 13:05:25.730 align:start position:0% wants to do is focus on Networks and<13:05:24.060> then<13:05:24.180> it<13:05:24.416> will<13:05:24.596> then<13:05:24.840> switch<13:05:25.200> the<13:05:25.436> packet 13:05:25.730 --> 13:05:25.740 align:start position:0% and then it will then switch the packet 13:05:25.740 --> 13:05:28.310 align:start position:0% and then it will then switch the packet to<13:05:25.860> the<13:05:26.096> correct<13:05:26.340> Network<13:05:27.300> and<13:05:28.080> another 13:05:28.310 --> 13:05:28.320 align:start position:0% to the correct Network and another 13:05:28.320 --> 13:05:31.246 align:start position:0% to the correct Network and another router<13:05:28.860> and<13:05:29.340> then<13:05:29.460> finally<13:05:30.000> the<13:05:30.776> host<13:05:30.900> address 13:05:31.246 --> 13:05:31.256 align:start position:0% router and then finally the host address 13:05:31.256 --> 13:05:32.450 align:start position:0% router and then finally the host address in 13:05:32.450 --> 13:05:32.460 align:start position:0% in 13:05:32.460 --> 13:05:34.370 align:start position:0% in the<13:05:33.060> Mac<13:05:33.180> part<13:05:33.480> of<13:05:33.596> the<13:05:33.720> address<13:05:33.840> will<13:05:34.200> be 13:05:34.370 --> 13:05:34.380 align:start position:0% the Mac part of the address will be 13:05:34.380 --> 13:05:38.630 align:start position:0% the Mac part of the address will be taken<13:05:34.740> care<13:05:34.916> of<13:05:35.040> by<13:05:35.460> the<13:05:35.700> Lan<13:05:36.300> switches 13:05:38.630 --> 13:05:38.640 align:start position:0% taken care of by the Lan switches 13:05:38.640 --> 13:05:40.970 align:start position:0% taken care of by the Lan switches so<13:05:39.300> a<13:05:39.540> route<13:05:39.720> is<13:05:39.960> not<13:05:40.140> based<13:05:40.436> on<13:05:40.500> the<13:05:40.740> host 13:05:40.970 --> 13:05:40.980 align:start position:0% so a route is not based on the host 13:05:40.980 --> 13:05:43.070 align:start position:0% so a route is not based on the host because<13:05:41.340> the<13:05:41.756> packets<13:05:42.180> are<13:05:42.480> routed<13:05:42.900> through 13:05:43.070 --> 13:05:43.080 align:start position:0% because the packets are routed through 13:05:43.080 --> 13:05:45.106 align:start position:0% because the packets are routed through the<13:05:43.256> networks<13:05:43.680> it<13:05:44.220> doesn't<13:05:44.460> use<13:05:44.640> the<13:05:44.880> physical 13:05:45.106 --> 13:05:45.116 align:start position:0% the networks it doesn't use the physical 13:05:45.116 --> 13:05:48.350 align:start position:0% the networks it doesn't use the physical Mac<13:05:45.480> address<13:05:45.660> of<13:05:46.020> the<13:05:46.200> hosts 13:05:48.350 --> 13:05:48.360 align:start position:0% Mac address of the hosts 13:05:48.360 --> 13:05:51.766 align:start position:0% Mac address of the hosts so<13:05:49.140> here's<13:05:49.740> the<13:05:49.800> example<13:05:50.220> we've<13:05:50.520> got<13:05:50.640> a<13:05:50.936> a<13:05:51.540> few 13:05:51.766 --> 13:05:51.776 align:start position:0% so here's the example we've got a a few 13:05:51.776 --> 13:05:53.810 align:start position:0% so here's the example we've got a a few different<13:05:52.020> I've<13:05:52.380> shrunk<13:05:53.040> down<13:05:53.276> each<13:05:53.640> switch 13:05:53.810 --> 13:05:53.820 align:start position:0% different I've shrunk down each switch 13:05:53.820 --> 13:05:56.926 align:start position:0% different I've shrunk down each switch would<13:05:54.180> have<13:05:54.416> it<13:05:55.140> could<13:05:55.320> have<13:05:55.436> a<13:05:55.680> 12<13:05:55.980> or<13:05:56.220> 24<13:05:56.460> host 13:05:56.926 --> 13:05:56.936 align:start position:0% would have it could have a 12 or 24 host 13:05:56.936 --> 13:05:59.150 align:start position:0% would have it could have a 12 or 24 host connected<13:05:57.416> but<13:05:57.596> I've<13:05:57.720> just<13:05:57.900> added<13:05:58.200> one<13:05:58.436> and 13:05:59.150 --> 13:05:59.160 align:start position:0% connected but I've just added one and 13:05:59.160 --> 13:06:00.406 align:start position:0% connected but I've just added one and you<13:05:59.276> can<13:05:59.400> see<13:05:59.460> we've<13:05:59.640> got<13:05:59.820> three<13:06:00.240> different 13:06:00.406 --> 13:06:00.416 align:start position:0% you can see we've got three different 13:06:00.416 --> 13:06:03.050 align:start position:0% you can see we've got three different networks<13:06:00.960> listed<13:06:01.256> here<13:06:01.436> the<13:06:01.560> 192<13:06:02.220> a<13:06:02.460> 10<13:06:02.700> and<13:06:02.936> a 13:06:03.050 --> 13:06:03.060 align:start position:0% networks listed here the 192 a 10 and a 13:06:03.060 --> 13:06:05.210 align:start position:0% networks listed here the 192 a 10 and a 172<13:06:03.720> Network 13:06:05.210 --> 13:06:05.220 align:start position:0% 172 Network 13:06:05.220 --> 13:06:08.086 align:start position:0% 172 Network so<13:06:05.700> the<13:06:05.880> MAC<13:06:06.000> address<13:06:06.560> of<13:06:07.560> the<13:06:07.740> destination 13:06:08.086 --> 13:06:08.096 align:start position:0% so the MAC address of the destination 13:06:08.096 --> 13:06:10.790 align:start position:0% so the MAC address of the destination host<13:06:08.400> is<13:06:08.640> only<13:06:08.880> used<13:06:09.116> for<13:06:09.300> the<13:06:09.540> final<13:06:09.660> delivery 13:06:10.790 --> 13:06:10.800 align:start position:0% host is only used for the final delivery 13:06:10.800 --> 13:06:13.426 align:start position:0% host is only used for the final delivery so<13:06:11.580> the<13:06:12.116> switch<13:06:12.360> if<13:06:12.660> these<13:06:12.900> are<13:06:13.020> layer<13:06:13.320> 2 13:06:13.426 --> 13:06:13.436 align:start position:0% so the switch if these are layer 2 13:06:13.436 --> 13:06:15.470 align:start position:0% so the switch if these are layer 2 switches<13:06:13.980> which<13:06:14.276> are<13:06:14.400> my<13:06:14.580> examples<13:06:15.000> they<13:06:15.300> are 13:06:15.470 --> 13:06:15.480 align:start position:0% switches which are my examples they are 13:06:15.480 --> 13:06:18.766 align:start position:0% switches which are my examples they are it<13:06:16.256> won't<13:06:16.436> understand<13:06:16.680> the<13:06:17.220> IP 13:06:18.766 --> 13:06:18.776 align:start position:0% it won't understand the IP 13:06:18.776 --> 13:06:22.310 align:start position:0% it won't understand the IP address<13:06:19.560> portion<13:06:20.400> of<13:06:20.700> the<13:06:21.000> packet<13:06:21.480> because 13:06:22.310 --> 13:06:22.320 align:start position:0% address portion of the packet because 13:06:22.320 --> 13:06:25.130 align:start position:0% address portion of the packet because we're<13:06:22.860> looking<13:06:23.040> inside<13:06:23.400> the<13:06:23.756> frame<13:06:24.116> and<13:06:24.960> it 13:06:25.130 --> 13:06:25.140 align:start position:0% we're looking inside the frame and it 13:06:25.140 --> 13:06:28.310 align:start position:0% we're looking inside the frame and it will<13:06:25.320> match<13:06:25.860> the<13:06:26.400> MAC<13:06:26.880> address 13:06:28.310 --> 13:06:28.320 align:start position:0% will match the MAC address 13:06:28.320 --> 13:06:31.070 align:start position:0% will match the MAC address to<13:06:28.916> the<13:06:29.160> correct<13:06:29.460> port<13:06:29.820> and<13:06:30.240> then<13:06:30.360> deliver<13:06:30.596> the 13:06:31.070 --> 13:06:31.080 align:start position:0% to the correct port and then deliver the 13:06:31.080 --> 13:06:33.530 align:start position:0% to the correct port and then deliver the frame<13:06:31.680> to<13:06:31.980> that<13:06:32.220> particular<13:06:32.520> Port<13:06:32.880> this<13:06:33.416> is 13:06:33.530 --> 13:06:33.540 align:start position:0% frame to that particular Port this is 13:06:33.540 --> 13:06:34.970 align:start position:0% frame to that particular Port this is what<13:06:33.720> our<13:06:33.840> switches<13:06:34.256> are<13:06:34.436> concerned<13:06:34.860> with 13:06:34.970 --> 13:06:34.980 align:start position:0% what our switches are concerned with 13:06:34.980 --> 13:06:36.766 align:start position:0% what our switches are concerned with whereas<13:06:35.640> all<13:06:35.756> the<13:06:35.880> routing<13:06:36.240> between<13:06:36.416> the 13:06:36.766 --> 13:06:36.776 align:start position:0% whereas all the routing between the 13:06:36.776 --> 13:06:38.390 align:start position:0% whereas all the routing between the three<13:06:36.900> routers<13:06:37.380> in<13:06:37.680> the<13:06:37.800> diagram<13:06:38.040> here 13:06:38.390 --> 13:06:38.400 align:start position:0% three routers in the diagram here 13:06:38.400 --> 13:06:40.490 align:start position:0% three routers in the diagram here they're<13:06:38.936> concerned<13:06:39.360> with<13:06:39.480> which<13:06:39.720> network<13:06:40.080> or 13:06:40.490 --> 13:06:40.500 align:start position:0% they're concerned with which network or 13:06:40.500 --> 13:06:43.190 align:start position:0% they're concerned with which network or which<13:06:40.800> Port<13:06:41.040> which<13:06:42.000> network<13:06:42.300> is<13:06:42.660> connected<13:06:43.020> to 13:06:43.190 --> 13:06:43.200 align:start position:0% which Port which network is connected to 13:06:43.200 --> 13:06:44.746 align:start position:0% which Port which network is connected to of<13:06:43.500> the<13:06:43.616> router 13:06:44.746 --> 13:06:44.756 align:start position:0% of the router 13:06:44.756 --> 13:06:47.990 align:start position:0% of the router so<13:06:45.540> the<13:06:46.256> switch<13:06:46.436> down<13:06:46.740> here<13:06:46.980> on<13:06:47.160> the<13:06:47.340> right<13:06:47.460> if 13:06:47.990 --> 13:06:48.000 align:start position:0% so the switch down here on the right if 13:06:48.000 --> 13:06:50.570 align:start position:0% so the switch down here on the right if you<13:06:48.180> issue<13:06:48.416> a<13:06:48.596> show<13:06:48.840> Mac<13:06:49.436> address<13:06:49.680> table<13:06:50.040> on<13:06:50.460> a 13:06:50.570 --> 13:06:50.580 align:start position:0% you issue a show Mac address table on a 13:06:50.580 --> 13:06:52.730 align:start position:0% you issue a show Mac address table on a Cisco<13:06:50.880> switch<13:06:51.116> at<13:06:51.416> least<13:06:51.596> you'll<13:06:52.200> see<13:06:52.380> a<13:06:52.560> map 13:06:52.730 --> 13:06:52.740 align:start position:0% Cisco switch at least you'll see a map 13:06:52.740 --> 13:06:55.190 align:start position:0% Cisco switch at least you'll see a map in<13:06:52.980> and<13:06:53.580> you'll<13:06:53.700> see<13:06:53.936> which<13:06:54.240> Mac<13:06:54.480> address<13:06:54.720> and 13:06:55.190 --> 13:06:55.200 align:start position:0% in and you'll see which Mac address and 13:06:55.200 --> 13:06:57.890 align:start position:0% in and you'll see which Mac address and each<13:06:55.380> one's<13:06:55.680> unique<13:06:56.040> is<13:06:56.640> connected<13:06:57.116> to<13:06:57.596> which 13:06:57.890 --> 13:06:57.900 align:start position:0% each one's unique is connected to which 13:06:57.900 --> 13:07:00.230 align:start position:0% each one's unique is connected to which physical<13:06:58.256> ports<13:06:58.980> and<13:06:59.460> this<13:06:59.756> particular<13:07:00.000> one 13:07:00.230 --> 13:07:00.240 align:start position:0% physical ports and this particular one 13:07:00.240 --> 13:07:01.550 align:start position:0% physical ports and this particular one they're<13:07:00.416> all<13:07:00.596> in<13:07:00.720> the<13:07:00.840> same<13:07:00.900> VLAN<13:07:01.380> because 13:07:01.550 --> 13:07:01.560 align:start position:0% they're all in the same VLAN because 13:07:01.560 --> 13:07:03.586 align:start position:0% they're all in the same VLAN because we're<13:07:01.740> not<13:07:01.860> worried<13:07:02.096> about 13:07:03.586 --> 13:07:03.596 align:start position:0% we're not worried about 13:07:03.596 --> 13:07:07.246 align:start position:0% we're not worried about um into<13:07:03.900> VLAN<13:07:04.500> any<13:07:05.096> any<13:07:05.340> VLAN<13:07:05.820> stuff<13:07:06.060> here<13:07:06.300> so 13:07:07.246 --> 13:07:07.256 align:start position:0% um into VLAN any any VLAN stuff here so 13:07:07.256 --> 13:07:09.830 align:start position:0% um into VLAN any any VLAN stuff here so gigabit<13:07:08.040> zero<13:07:08.640> slash<13:07:08.880> two<13:07:09.060> zero<13:07:09.480> slash<13:07:09.720> two 13:07:09.830 --> 13:07:09.840 align:start position:0% gigabit zero slash two zero slash two 13:07:09.840 --> 13:07:12.050 align:start position:0% gigabit zero slash two zero slash two zero<13:07:10.140> slash<13:07:10.380> two<13:07:10.500> and<13:07:10.800> fast<13:07:11.220> ethernet<13:07:11.580> zero 13:07:12.050 --> 13:07:12.060 align:start position:0% zero slash two and fast ethernet zero 13:07:12.060 --> 13:07:14.690 align:start position:0% zero slash two and fast ethernet zero slash<13:07:12.360> one<13:07:13.020> if<13:07:13.560> you<13:07:13.740> see<13:07:13.916> more<13:07:14.160> than<13:07:14.340> one<13:07:14.520> host 13:07:14.690 --> 13:07:14.700 align:start position:0% slash one if you see more than one host 13:07:14.700 --> 13:07:17.510 align:start position:0% slash one if you see more than one host connected<13:07:15.240> to<13:07:15.480> one<13:07:15.720> port<13:07:16.020> it<13:07:16.800> means<13:07:17.040> it's<13:07:17.340> a 13:07:17.510 --> 13:07:17.520 align:start position:0% connected to one port it means it's a 13:07:17.520 --> 13:07:19.010 align:start position:0% connected to one port it means it's a trunk<13:07:17.880> and<13:07:18.060> it's<13:07:18.240> connected<13:07:18.596> to<13:07:18.840> another 13:07:19.010 --> 13:07:19.020 align:start position:0% trunk and it's connected to another 13:07:19.020 --> 13:07:21.350 align:start position:0% trunk and it's connected to another switch<13:07:19.436> somebody<13:07:19.980> somewhere 13:07:21.350 --> 13:07:21.360 align:start position:0% switch somebody somewhere 13:07:21.360 --> 13:07:23.086 align:start position:0% switch somebody somewhere so<13:07:21.900> this<13:07:22.140> switch<13:07:22.320> down<13:07:22.560> here<13:07:22.800> would<13:07:22.980> be 13:07:23.086 --> 13:07:23.096 align:start position:0% so this switch down here would be 13:07:23.096 --> 13:07:24.650 align:start position:0% so this switch down here would be connected<13:07:23.400> to<13:07:23.640> another<13:07:23.820> switch<13:07:24.180> via<13:07:24.540> a 13:07:24.650 --> 13:07:24.660 align:start position:0% connected to another switch via a 13:07:24.660 --> 13:07:27.106 align:start position:0% connected to another switch via a gigabit<13:07:25.140> Ethernet<13:07:25.860> port<13:07:26.160> and<13:07:26.520> it's<13:07:26.640> learned<13:07:27.000> a 13:07:27.106 --> 13:07:27.116 align:start position:0% gigabit Ethernet port and it's learned a 13:07:27.116 --> 13:07:29.330 align:start position:0% gigabit Ethernet port and it's learned a few<13:07:27.240> host<13:07:27.540> addresses<13:07:28.500> that<13:07:28.740> are<13:07:28.860> connected<13:07:29.160> to 13:07:29.330 --> 13:07:29.340 align:start position:0% few host addresses that are connected to 13:07:29.340 --> 13:07:30.890 align:start position:0% few host addresses that are connected to that 13:07:30.890 --> 13:07:30.900 align:start position:0% that 13:07:30.900 --> 13:07:32.926 align:start position:0% that all<13:07:31.320> right<13:07:31.436> so<13:07:31.616> when<13:07:31.860> we<13:07:32.040> send<13:07:32.220> packets<13:07:32.580> out<13:07:32.756> to 13:07:32.926 --> 13:07:32.936 align:start position:0% all right so when we send packets out to 13:07:32.936 --> 13:07:35.086 align:start position:0% all right so when we send packets out to the<13:07:33.060> internet<13:07:33.180> the<13:07:33.660> following<13:07:34.020> is<13:07:34.140> true<13:07:34.436> the 13:07:35.086 --> 13:07:35.096 align:start position:0% the internet the following is true the 13:07:35.096 --> 13:07:37.670 align:start position:0% the internet the following is true the routers<13:07:35.520> have<13:07:35.820> a<13:07:36.000> database<13:07:36.416> of<13:07:36.720> routes<13:07:37.140> stored 13:07:37.670 --> 13:07:37.680 align:start position:0% routers have a database of routes stored 13:07:37.680 --> 13:07:39.766 align:start position:0% routers have a database of routes stored in<13:07:37.916> a<13:07:38.040> table<13:07:38.276> called<13:07:38.580> a<13:07:38.756> routing<13:07:39.000> table<13:07:39.180> it 13:07:39.766 --> 13:07:39.776 align:start position:0% in a table called a routing table it 13:07:39.776 --> 13:07:41.690 align:start position:0% in a table called a routing table it could<13:07:39.900> actually<13:07:40.140> be<13:07:40.616> a<13:07:40.740> database<13:07:41.096> consisting 13:07:41.690 --> 13:07:41.700 align:start position:0% could actually be a database consisting 13:07:41.700 --> 13:07:44.086 align:start position:0% could actually be a database consisting of<13:07:41.880> one<13:07:42.116> route<13:07:42.416> or<13:07:43.020> just<13:07:43.256> connected<13:07:43.680> routes 13:07:44.086 --> 13:07:44.096 align:start position:0% of one route or just connected routes 13:07:44.096 --> 13:07:46.850 align:start position:0% of one route or just connected routes depends<13:07:45.000> how<13:07:45.180> we<13:07:45.300> configure<13:07:45.720> stuff<13:07:45.960> really 13:07:46.850 --> 13:07:46.860 align:start position:0% depends how we configure stuff really 13:07:46.860 --> 13:07:48.650 align:start position:0% depends how we configure stuff really the<13:07:47.220> writers<13:07:47.580> use<13:07:47.756> this<13:07:47.936> information<13:07:48.180> in<13:07:48.540> the 13:07:48.650 --> 13:07:48.660 align:start position:0% the writers use this information in the 13:07:48.660 --> 13:07:50.266 align:start position:0% the writers use this information in the writing<13:07:48.960> tables<13:07:49.320> and<13:07:49.500> they<13:07:49.680> make<13:07:49.860> a<13:07:50.040> decision 13:07:50.266 --> 13:07:50.276 align:start position:0% writing tables and they make a decision 13:07:50.276 --> 13:07:52.906 align:start position:0% writing tables and they make a decision based<13:07:50.700> upon<13:07:50.936> the<13:07:51.776> next<13:07:51.900> hop<13:07:52.200> this<13:07:52.680> is<13:07:52.740> what 13:07:52.906 --> 13:07:52.916 align:start position:0% based upon the next hop this is what 13:07:52.916 --> 13:07:55.790 align:start position:0% based upon the next hop this is what routers<13:07:53.340> all<13:07:53.520> do<13:07:53.640> they<13:07:53.936> send<13:07:54.180> a<13:07:55.080> packet<13:07:55.500> to<13:07:55.616> the 13:07:55.790 --> 13:07:55.800 align:start position:0% routers all do they send a packet to the 13:07:55.800 --> 13:07:56.870 align:start position:0% routers all do they send a packet to the next<13:07:55.980> hop 13:07:56.870 --> 13:07:56.880 align:start position:0% next hop 13:07:56.880 --> 13:07:59.926 align:start position:0% next hop unless<13:07:57.660> they<13:07:57.960> are<13:07:58.140> the<13:07:58.436> the<13:07:58.800> last<13:07:59.040> hop<13:07:59.340> in<13:07:59.640> the 13:07:59.926 --> 13:07:59.936 align:start position:0% unless they are the the last hop in the 13:07:59.936 --> 13:08:01.790 align:start position:0% unless they are the the last hop in the journey 13:08:01.790 --> 13:08:01.800 align:start position:0% journey 13:08:01.800 --> 13:08:04.670 align:start position:0% journey so<13:08:02.276> there's<13:08:02.460> a<13:08:02.640> routing<13:08:02.936> table<13:08:03.116> here<13:08:03.660> you<13:08:04.500> can 13:08:04.670 --> 13:08:04.680 align:start position:0% so there's a routing table here you can 13:08:04.680 --> 13:08:07.310 align:start position:0% so there's a routing table here you can see<13:08:05.096> uh<13:08:05.756> there's<13:08:05.880> a<13:08:06.116> network<13:08:06.360> been<13:08:06.776> learned 13:08:07.310 --> 13:08:07.320 align:start position:0% see uh there's a network been learned 13:08:07.320 --> 13:08:08.926 align:start position:0% see uh there's a network been learned and 13:08:08.926 --> 13:08:08.936 align:start position:0% and 13:08:08.936 --> 13:08:11.266 align:start position:0% and if<13:08:09.300> I<13:08:09.540> just<13:08:09.900> put<13:08:10.080> the<13:08:10.256> text<13:08:10.616> here<13:08:10.860> the<13:08:11.040> routing 13:08:11.266 --> 13:08:11.276 align:start position:0% if I just put the text here the routing 13:08:11.276 --> 13:08:12.586 align:start position:0% if I just put the text here the routing table<13:08:11.460> contains<13:08:11.880> the<13:08:12.000> following<13:08:12.240> the<13:08:12.416> network 13:08:12.586 --> 13:08:12.596 align:start position:0% table contains the following the network 13:08:12.596 --> 13:08:16.790 align:start position:0% table contains the following the network ID<13:08:13.220> here<13:08:14.220> the<13:08:14.520> network<13:08:14.700> is<13:08:15.540> three<13:08:15.960> zero<13:08:16.436> zero 13:08:16.790 --> 13:08:16.800 align:start position:0% ID here the network is three zero zero 13:08:16.800 --> 13:08:18.830 align:start position:0% ID here the network is three zero zero zero<13:08:17.160> and<13:08:17.640> it's<13:08:17.756> actually<13:08:17.936> found<13:08:18.180> a<13:08:18.416> host<13:08:18.540> on 13:08:18.830 --> 13:08:18.840 align:start position:0% zero and it's actually found a host on 13:08:18.840 --> 13:08:21.406 align:start position:0% zero and it's actually found a host on this<13:08:19.020> network 13:08:21.406 --> 13:08:21.416 align:start position:0% 13:08:21.416 --> 13:08:23.690 align:start position:0% destination<13:08:22.256> Network<13:08:22.560> address<13:08:22.916> and<13:08:23.276> subnet 13:08:23.690 --> 13:08:23.700 align:start position:0% destination Network address and subnet 13:08:23.700 --> 13:08:25.426 align:start position:0% destination Network address and subnet mask<13:08:23.936> I'm<13:08:24.300> not<13:08:24.416> sure<13:08:24.540> how<13:08:24.720> this<13:08:24.840> is<13:08:25.020> been 13:08:25.426 --> 13:08:25.436 align:start position:0% mask I'm not sure how this is been 13:08:25.436 --> 13:08:27.050 align:start position:0% mask I'm not sure how this is been configured<13:08:25.980> because<13:08:26.096> I<13:08:26.340> pulled<13:08:26.640> this<13:08:26.700> one<13:08:26.880> off 13:08:27.050 --> 13:08:27.060 align:start position:0% configured because I pulled this one off 13:08:27.060 --> 13:08:29.630 align:start position:0% configured because I pulled this one off the<13:08:27.720> um<13:08:27.776> off<13:08:28.500> the<13:08:28.680> internet<13:08:28.860> you<13:08:29.460> can<13:08:29.520> actually 13:08:29.630 --> 13:08:29.640 align:start position:0% the um off the internet you can actually 13:08:29.640 --> 13:08:33.290 align:start position:0% the um off the internet you can actually see<13:08:29.880> at<13:08:30.060> the<13:08:30.180> bottom<13:08:30.540> 10<13:08:30.900> 10<13:08:31.400> 23<13:08:32.400> 0<13:08:32.700> is<13:08:33.116> a 13:08:33.290 --> 13:08:33.300 align:start position:0% see at the bottom 10 10 23 0 is a 13:08:33.300 --> 13:08:36.586 align:start position:0% see at the bottom 10 10 23 0 is a network<13:08:33.480> found<13:08:33.840> by<13:08:34.140> ospf 13:08:36.586 --> 13:08:36.596 align:start position:0% network found by ospf 13:08:36.596 --> 13:08:38.926 align:start position:0% network found by ospf and<13:08:37.320> it<13:08:37.560> will<13:08:37.740> have<13:08:37.916> the<13:08:38.160> next<13:08:38.276> top<13:08:38.580> and 13:08:38.926 --> 13:08:38.936 align:start position:0% and it will have the next top and 13:08:38.936 --> 13:08:43.310 align:start position:0% and it will have the next top and Gateway<13:08:39.500> so<13:08:40.500> if<13:08:41.040> we<13:08:41.160> go<13:08:41.340> to<13:08:41.460> the<13:08:41.640> bottom<13:08:42.060> 10<13:08:43.020> 10 13:08:43.310 --> 13:08:43.320 align:start position:0% Gateway so if we go to the bottom 10 10 13:08:43.320 --> 13:08:47.266 align:start position:0% Gateway so if we go to the bottom 10 10 23<13:08:44.160> 0<13:08:44.840> 110<13:08:45.840> is<13:08:46.140> the<13:08:46.380> administrative<13:08:46.916> distance 13:08:47.266 --> 13:08:47.276 align:start position:0% 23 0 110 is the administrative distance 13:08:47.276 --> 13:08:50.330 align:start position:0% 23 0 110 is the administrative distance for<13:08:47.640> rspf<13:08:48.300> 20<13:08:48.840> is<13:08:49.140> the<13:08:49.320> cost 13:08:50.330 --> 13:08:50.340 align:start position:0% for rspf 20 is the cost 13:08:50.340 --> 13:08:54.230 align:start position:0% for rspf 20 is the cost and<13:08:51.000> it's<13:08:51.360> been<13:08:51.660> learned<13:08:52.200> via<13:08:52.800> the<13:08:53.460> address<13:08:53.580> 10 13:08:54.230 --> 13:08:54.240 align:start position:0% and it's been learned via the address 10 13:08:54.240 --> 13:08:57.170 align:start position:0% and it's been learned via the address 10 10<13:08:54.916> 12.2<13:08:55.916> which<13:08:56.160> will<13:08:56.276> be<13:08:56.460> another<13:08:56.580> router 13:08:57.170 --> 13:08:57.180 align:start position:0% 10 12.2 which will be another router 13:08:57.180 --> 13:08:59.690 align:start position:0% 10 12.2 which will be another router interface<13:08:57.660> somewhere<13:08:58.560> connected 13:08:59.690 --> 13:08:59.700 align:start position:0% interface somewhere connected 13:08:59.700 --> 13:09:01.606 align:start position:0% interface somewhere connected it<13:09:00.116> was<13:09:00.240> actually<13:09:00.360> learned<13:09:00.900> one<13:09:01.200> minute<13:09:01.436> and 13:09:01.606 --> 13:09:01.616 align:start position:0% it was actually learned one minute and 13:09:01.616 --> 13:09:05.450 align:start position:0% it was actually learned one minute and 17<13:09:01.860> seconds<13:09:02.220> ago<13:09:02.756> via<13:09:03.720> the<13:09:03.900> fast<13:09:04.080> ethernet<13:09:04.436> 0<13:09:04.860> 0 13:09:05.450 --> 13:09:05.460 align:start position:0% 17 seconds ago via the fast ethernet 0 0 13:09:05.460 --> 13:09:07.906 align:start position:0% 17 seconds ago via the fast ethernet 0 0 interface 13:09:07.906 --> 13:09:07.916 align:start position:0% interface 13:09:07.916 --> 13:09:10.246 align:start position:0% interface all<13:09:08.460> right<13:09:08.580> so<13:09:08.756> these<13:09:09.240> the<13:09:09.480> router<13:09:09.900> has<13:09:10.080> enough 13:09:10.246 --> 13:09:10.256 align:start position:0% all right so these the router has enough 13:09:10.256 --> 13:09:12.650 align:start position:0% all right so these the router has enough information<13:09:10.700> that<13:09:11.700> if<13:09:11.820> it<13:09:11.936> wants<13:09:12.180> to<13:09:12.240> send<13:09:12.416> any 13:09:12.650 --> 13:09:12.660 align:start position:0% information that if it wants to send any 13:09:12.660 --> 13:09:15.470 align:start position:0% information that if it wants to send any packets<13:09:13.080> to<13:09:13.320> any<13:09:13.500> host<13:09:13.740> on<13:09:14.040> the<13:09:14.220> 10<13:09:14.400> 10<13:09:14.640> 23 13:09:15.470 --> 13:09:15.480 align:start position:0% packets to any host on the 10 10 23 13:09:15.480 --> 13:09:18.050 align:start position:0% packets to any host on the 10 10 23 Network<13:09:15.776> it<13:09:16.560> knows<13:09:16.860> where<13:09:17.040> to<13:09:17.160> send<13:09:17.400> it<13:09:17.580> and<13:09:17.936> it 13:09:18.050 --> 13:09:18.060 align:start position:0% Network it knows where to send it and it 13:09:18.060 --> 13:09:23.870 align:start position:0% Network it knows where to send it and it also<13:09:18.360> knows<13:09:18.660> how<13:09:19.080> fresh<13:09:19.680> that<13:09:20.460> route<13:09:20.640> is 13:09:23.870 --> 13:09:23.880 align:start position:0% 13:09:23.880 --> 13:09:26.630 align:start position:0% all<13:09:24.360> right<13:09:24.480> the<13:09:24.840> metric<13:09:25.500> metrics<13:09:26.400> used<13:09:26.520> to 13:09:26.630 --> 13:09:26.640 align:start position:0% all right the metric metrics used to 13:09:26.640 --> 13:09:28.790 align:start position:0% all right the metric metrics used to decide<13:09:26.880> which<13:09:27.116> route<13:09:27.360> is<13:09:27.660> to<13:09:27.776> be<13:09:27.900> taken<13:09:28.200> if<13:09:28.500> if 13:09:28.790 --> 13:09:28.800 align:start position:0% decide which route is to be taken if if 13:09:28.800 --> 13:09:30.766 align:start position:0% decide which route is to be taken if if multiple<13:09:29.220> routes<13:09:29.580> exist<13:09:29.880> for<13:09:30.116> a<13:09:30.360> given 13:09:30.766 --> 13:09:30.776 align:start position:0% multiple routes exist for a given 13:09:30.776 --> 13:09:34.266 align:start position:0% multiple routes exist for a given destination<13:09:31.320> Network<13:09:32.300> so<13:09:33.300> we<13:09:33.480> can<13:09:33.660> see<13:09:33.776> some 13:09:34.266 --> 13:09:34.276 align:start position:0% destination Network so we can see some 13:09:34.276 --> 13:09:37.010 align:start position:0% destination Network so we can see some metrics<13:09:35.276> here<13:09:35.460> in<13:09:35.820> fact 13:09:37.010 --> 13:09:37.020 align:start position:0% metrics here in fact 13:09:37.020 --> 13:09:40.730 align:start position:0% metrics here in fact um squared<13:09:37.980> in<13:09:38.160> the<13:09:38.400> yellow<13:09:38.640> highlighting 13:09:40.730 --> 13:09:40.740 align:start position:0% um squared in the yellow highlighting 13:09:40.740 --> 13:09:43.010 align:start position:0% um squared in the yellow highlighting you<13:09:41.400> can<13:09:41.520> see<13:09:41.700> two<13:09:42.000> routes<13:09:42.360> have<13:09:42.480> been<13:09:42.660> learned 13:09:43.010 --> 13:09:43.020 align:start position:0% you can see two routes have been learned 13:09:43.020 --> 13:09:46.130 align:start position:0% you can see two routes have been learned to<13:09:43.140> the<13:09:43.436> same<13:09:43.800> network<13:09:44.520> the<13:09:45.416> reason<13:09:45.596> is<13:09:45.900> the 13:09:46.130 --> 13:09:46.140 align:start position:0% to the same network the reason is the 13:09:46.140 --> 13:09:49.010 align:start position:0% to the same network the reason is the metric<13:09:46.500> is<13:09:46.800> exactly<13:09:47.220> the<13:09:47.580> same<13:09:47.756> so<13:09:48.540> it<13:09:48.720> must<13:09:48.840> be 13:09:49.010 --> 13:09:49.020 align:start position:0% metric is exactly the same so it must be 13:09:49.020 --> 13:09:52.370 align:start position:0% metric is exactly the same so it must be exactly<13:09:49.500> the<13:09:49.860> same<13:09:50.096> cost 13:09:52.370 --> 13:09:52.380 align:start position:0% exactly the same cost 13:09:52.380 --> 13:09:55.190 align:start position:0% exactly the same cost to<13:09:53.160> reach<13:09:53.756> the<13:09:53.880> destination<13:09:54.300> via<13:09:54.900> two 13:09:55.190 --> 13:09:55.200 align:start position:0% to reach the destination via two 13:09:55.200 --> 13:09:57.106 align:start position:0% to reach the destination via two different<13:09:55.380> IP<13:09:55.860> addresses<13:09:56.276> one<13:09:56.640> seven<13:09:56.880> two 13:09:57.106 --> 13:09:57.116 align:start position:0% different IP addresses one seven two 13:09:57.116 --> 13:10:00.050 align:start position:0% different IP addresses one seven two twenty<13:09:57.596> four<13:09:57.720> one<13:09:58.020> two<13:09:58.256> two<13:09:58.580> and<13:09:59.580> one<13:09:59.820> seven 13:10:00.050 --> 13:10:00.060 align:start position:0% twenty four one two two and one seven 13:10:00.060 --> 13:10:01.970 align:start position:0% twenty four one two two and one seven two<13:10:00.300> twenty<13:10:00.660> four<13:10:00.720> one<13:10:01.020> three<13:10:01.200> four<13:10:01.380> so<13:10:01.800> as 13:10:01.970 --> 13:10:01.980 align:start position:0% two twenty four one three four so as 13:10:01.980 --> 13:10:05.106 align:start position:0% two twenty four one three four so as long<13:10:02.096> as<13:10:02.220> the<13:10:02.400> costs<13:10:02.700> are<13:10:02.936> the<13:10:03.180> same<13:10:03.500> then 13:10:05.106 --> 13:10:05.116 align:start position:0% long as the costs are the same then 13:10:05.116 --> 13:10:08.510 align:start position:0% long as the costs are the same then ergrp<13:10:06.116> is<13:10:06.960> configured<13:10:07.616> to<13:10:07.740> load<13:10:08.040> balance<13:10:08.340> over 13:10:08.510 --> 13:10:08.520 align:start position:0% ergrp is configured to load balance over 13:10:08.520 --> 13:10:09.586 align:start position:0% ergrp is configured to load balance over those 13:10:09.586 --> 13:10:09.596 align:start position:0% those 13:10:09.596 --> 13:10:13.070 align:start position:0% those I<13:10:10.200> think<13:10:10.320> with<13:10:11.040> um<13:10:11.040> Cisco<13:10:12.080> ergrp 13:10:13.070 --> 13:10:13.080 align:start position:0% I think with um Cisco ergrp 13:10:13.080 --> 13:10:15.586 align:start position:0% I think with um Cisco ergrp automatically<13:10:13.860> load<13:10:14.520> balances<13:10:14.936> over<13:10:15.116> up<13:10:15.360> to 13:10:15.586 --> 13:10:15.596 align:start position:0% automatically load balances over up to 13:10:15.596 --> 13:10:17.746 align:start position:0% automatically load balances over up to four<13:10:15.776> links<13:10:16.256> and<13:10:16.800> you<13:10:16.916> can<13:10:17.040> change<13:10:17.220> that<13:10:17.520> value 13:10:17.746 --> 13:10:17.756 align:start position:0% four links and you can change that value 13:10:17.756 --> 13:10:20.390 align:start position:0% four links and you can change that value up<13:10:18.000> to<13:10:18.300> 16.<13:10:19.380> but<13:10:19.860> this<13:10:20.040> could<13:10:20.220> change 13:10:20.390 --> 13:10:20.400 align:start position:0% up to 16. but this could change 13:10:20.400 --> 13:10:23.390 align:start position:0% up to 16. but this could change depending<13:10:20.820> on<13:10:20.936> your<13:10:21.180> platform 13:10:23.390 --> 13:10:23.400 align:start position:0% depending on your platform 13:10:23.400 --> 13:10:25.246 align:start position:0% depending on your platform all<13:10:23.880> right<13:10:24.000> so<13:10:24.180> the<13:10:24.360> administrative<13:10:24.840> distance 13:10:25.246 --> 13:10:25.256 align:start position:0% all right so the administrative distance 13:10:25.256 --> 13:10:27.170 align:start position:0% all right so the administrative distance when<13:10:25.680> a<13:10:25.860> router's<13:10:26.220> right<13:10:26.340> running<13:10:26.580> two<13:10:26.820> roads 13:10:27.170 --> 13:10:27.180 align:start position:0% when a router's right running two roads 13:10:27.180 --> 13:10:29.266 align:start position:0% when a router's right running two roads right<13:10:27.416> on<13:10:27.540> protocols<13:10:28.140> such<13:10:28.256> as<13:10:28.380> rip<13:10:28.616> and<13:10:28.800> SPF 13:10:29.266 --> 13:10:29.276 align:start position:0% right on protocols such as rip and SPF 13:10:29.276 --> 13:10:32.030 align:start position:0% right on protocols such as rip and SPF and<13:10:29.580> everything<13:10:29.820> else<13:10:30.060> is<13:10:30.360> equal 13:10:32.030 --> 13:10:32.040 align:start position:0% and everything else is equal 13:10:32.040 --> 13:10:34.246 align:start position:0% and everything else is equal so<13:10:32.520> for<13:10:32.640> example<13:10:32.880> rip<13:10:33.180> and<13:10:33.300> SPF<13:10:33.776> it<13:10:34.020> will<13:10:34.140> use 13:10:34.246 --> 13:10:34.256 align:start position:0% so for example rip and SPF it will use 13:10:34.256 --> 13:10:36.350 align:start position:0% so for example rip and SPF it will use the<13:10:34.560> ad<13:10:34.800> administrative<13:10:35.640> distance<13:10:36.000> to 13:10:36.350 --> 13:10:36.360 align:start position:0% the ad administrative distance to 13:10:36.360 --> 13:10:39.406 align:start position:0% the ad administrative distance to determine<13:10:37.080> which<13:10:37.380> route<13:10:37.680> to<13:10:37.916> choose<13:10:38.460> I've 13:10:39.406 --> 13:10:39.416 align:start position:0% determine which route to choose I've 13:10:39.416 --> 13:10:42.350 align:start position:0% determine which route to choose I've configured<13:10:40.080> uh<13:10:40.560> two<13:10:40.740> routers<13:10:41.220> up<13:10:41.460> here<13:10:41.580> just 13:10:42.350 --> 13:10:42.360 align:start position:0% configured uh two routers up here just 13:10:42.360 --> 13:10:44.746 align:start position:0% configured uh two routers up here just connected<13:10:42.840> by<13:10:42.960> a<13:10:43.200> gigabit<13:10:43.560> zero<13:10:44.040> and<13:10:44.400> zero 13:10:44.746 --> 13:10:44.756 align:start position:0% connected by a gigabit zero and zero 13:10:44.756 --> 13:10:45.766 align:start position:0% connected by a gigabit zero and zero slash<13:10:45.000> one 13:10:45.766 --> 13:10:45.776 align:start position:0% slash one 13:10:45.776 --> 13:10:49.850 align:start position:0% slash one the<13:10:46.436> top<13:10:46.680> Network<13:10:47.580> for<13:10:48.116> the<13:10:48.300> top<13:10:48.480> link<13:10:48.776> is<13:10:48.960> 192. 13:10:49.850 --> 13:10:49.860 align:start position:0% the top Network for the top link is 192. 13:10:49.860 --> 13:10:51.890 align:start position:0% the top Network for the top link is 192. the<13:10:50.220> bot<13:10:50.400> and<13:10:50.700> it's<13:10:50.880> using<13:10:51.116> rip<13:10:51.360> the<13:10:51.596> bottom<13:10:51.776> is 13:10:51.890 --> 13:10:51.900 align:start position:0% the bot and it's using rip the bottom is 13:10:51.900 --> 13:10:55.490 align:start position:0% the bot and it's using rip the bottom is rspf<13:10:52.560> and<13:10:52.800> it's<13:10:52.916> 172.<13:10:54.240> and<13:10:54.776> at<13:10:54.960> the<13:10:55.080> end<13:10:55.200> we 13:10:55.490 --> 13:10:55.500 align:start position:0% rspf and it's 172. and at the end we 13:10:55.500 --> 13:10:58.310 align:start position:0% rspf and it's 172. and at the end we have<13:10:55.740> another<13:10:55.980> Network<13:10:56.340> a<13:10:57.000> Ted<13:10:57.240> Network<13:10:57.480> that 13:10:58.310 --> 13:10:58.320 align:start position:0% have another Network a Ted Network that 13:10:58.320 --> 13:11:01.550 align:start position:0% have another Network a Ted Network that is<13:10:58.500> advertised<13:10:58.980> via<13:10:59.276> rip<13:10:59.580> and<13:11:00.300> ospf 13:11:01.550 --> 13:11:01.560 align:start position:0% is advertised via rip and ospf 13:11:01.560 --> 13:11:04.130 align:start position:0% is advertised via rip and ospf so<13:11:02.276> rip<13:11:02.936> I<13:11:03.240> know<13:11:03.360> the<13:11:03.660> administrative 13:11:04.130 --> 13:11:04.140 align:start position:0% so rip I know the administrative 13:11:04.140 --> 13:11:09.050 align:start position:0% so rip I know the administrative distance<13:11:04.560> is<13:11:04.860> 120<13:11:05.840> ospf<13:11:06.840> is<13:11:06.960> 110<13:11:07.740> so<13:11:08.340> routes<13:11:08.880> to 13:11:09.050 --> 13:11:09.060 align:start position:0% distance is 120 ospf is 110 so routes to 13:11:09.060 --> 13:11:12.010 align:start position:0% distance is 120 ospf is 110 so routes to get<13:11:09.240> from<13:11:09.480> router<13:11:09.840> 0<13:11:10.340> to<13:11:11.340> the<13:11:11.460> 10<13:11:11.640> Network 13:11:12.010 --> 13:11:12.020 align:start position:0% get from router 0 to the 10 Network 13:11:12.020 --> 13:11:14.746 align:start position:0% get from router 0 to the 10 Network should<13:11:13.020> use<13:11:13.320> ospf 13:11:14.746 --> 13:11:14.756 align:start position:0% should use ospf 13:11:14.756 --> 13:11:17.746 align:start position:0% should use ospf and<13:11:15.116> if<13:11:15.300> the<13:11:15.540> ospf<13:11:16.080> network<13:11:16.320> goes<13:11:16.916> down<13:11:17.096> or<13:11:17.580> the 13:11:17.746 --> 13:11:17.756 align:start position:0% and if the ospf network goes down or the 13:11:17.756 --> 13:11:20.210 align:start position:0% and if the ospf network goes down or the interface<13:11:18.116> is<13:11:18.300> really<13:11:18.480> no<13:11:18.720> SPF<13:11:19.256> then<13:11:19.800> the<13:11:19.980> rip 13:11:20.210 --> 13:11:20.220 align:start position:0% interface is really no SPF then the rip 13:11:20.220 --> 13:11:23.570 align:start position:0% interface is really no SPF then the rip Network<13:11:20.580> could<13:11:21.360> be<13:11:21.596> chosen<13:11:22.080> this<13:11:23.040> is<13:11:23.160> a<13:11:23.340> part 13:11:23.570 --> 13:11:23.580 align:start position:0% Network could be chosen this is a part 13:11:23.580 --> 13:11:26.510 align:start position:0% Network could be chosen this is a part of<13:11:23.820> the<13:11:23.936> output<13:11:24.240> from<13:11:24.416> a<13:11:24.596> show<13:11:24.776> ospf<13:11:25.740> you<13:11:26.460> can 13:11:26.510 --> 13:11:26.520 align:start position:0% of the output from a show ospf you can 13:11:26.520 --> 13:11:31.850 align:start position:0% of the output from a show ospf you can see<13:11:26.700> 120<13:11:27.540> is<13:11:28.500> the<13:11:28.800> ad<13:11:29.096> one<13:11:30.000> is<13:11:30.300> how<13:11:30.540> many<13:11:30.720> hops 13:11:31.850 --> 13:11:31.860 align:start position:0% see 120 is the ad one is how many hops 13:11:31.860 --> 13:11:35.390 align:start position:0% see 120 is the ad one is how many hops and<13:11:32.340> under<13:11:32.520> the<13:11:32.700> 810<13:11:33.416> is<13:11:33.596> the<13:11:33.840> ad<13:11:34.020> Slash<13:11:34.980> 2<13:11:35.160> is 13:11:35.390 --> 13:11:35.400 align:start position:0% and under the 810 is the ad Slash 2 is 13:11:35.400 --> 13:11:38.746 align:start position:0% and under the 810 is the ad Slash 2 is the<13:11:35.700> cost<13:11:35.880> because<13:11:36.300> rspf<13:11:36.960> uses<13:11:37.320> a<13:11:37.560> cost<13:11:37.800> not<13:11:38.580> a 13:11:38.746 --> 13:11:38.756 align:start position:0% the cost because rspf uses a cost not a 13:11:38.756 --> 13:11:42.650 align:start position:0% the cost because rspf uses a cost not a hop<13:11:39.000> value<13:11:39.360> so<13:11:40.256> it's<13:11:40.500> the<13:11:41.096> um<13:11:41.160> the<13:11:41.936> calculation 13:11:42.650 --> 13:11:42.660 align:start position:0% hop value so it's the um the calculation 13:11:42.660 --> 13:11:45.710 align:start position:0% hop value so it's the um the calculation is<13:11:43.320> used<13:11:43.560> looking<13:11:44.340> at<13:11:44.520> the<13:11:45.060> um<13:11:45.060> speed<13:11:45.416> of<13:11:45.596> the 13:11:45.710 --> 13:11:45.720 align:start position:0% is used looking at the um speed of the 13:11:45.720 --> 13:11:48.350 align:start position:0% is used looking at the um speed of the link<13:11:45.840> is<13:11:46.200> put<13:11:46.436> into<13:11:46.616> a<13:11:46.800> formula 13:11:48.350 --> 13:11:48.360 align:start position:0% link is put into a formula 13:11:48.360 --> 13:11:50.086 align:start position:0% link is put into a formula and<13:11:48.840> each<13:11:48.960> link<13:11:49.200> between<13:11:49.500> source<13:11:49.980> and 13:11:50.086 --> 13:11:50.096 align:start position:0% and each link between source and 13:11:50.096 --> 13:11:52.490 align:start position:0% and each link between source and destination<13:11:50.520> is<13:11:50.880> added<13:11:51.180> to<13:11:51.300> the<13:11:51.480> cast<13:11:51.660> so<13:11:52.380> the 13:11:52.490 --> 13:11:52.500 align:start position:0% destination is added to the cast so the 13:11:52.500 --> 13:11:54.830 align:start position:0% destination is added to the cast so the cost<13:11:52.680> is<13:11:52.860> only<13:11:53.096> two<13:11:53.460> which<13:11:54.000> is<13:11:54.180> the<13:11:54.416> gigabit 13:11:54.830 --> 13:11:54.840 align:start position:0% cost is only two which is the gigabit 13:11:54.840 --> 13:11:56.746 align:start position:0% cost is only two which is the gigabit Ethernet<13:11:55.256> speed<13:11:55.560> there 13:11:56.746 --> 13:11:56.756 align:start position:0% Ethernet speed there 13:11:56.756 --> 13:11:58.730 align:start position:0% Ethernet speed there and<13:11:57.180> it'll<13:11:57.360> be<13:11:57.540> the<13:11:57.720> speed<13:11:57.840> of<13:11:58.080> the<13:11:58.256> interface 13:11:58.730 --> 13:11:58.740 align:start position:0% and it'll be the speed of the interface 13:11:58.740 --> 13:12:01.426 align:start position:0% and it'll be the speed of the interface that<13:11:58.980> the<13:11:59.160> 10<13:11:59.340> networks<13:11:59.820> connected<13:12:00.240> to 13:12:01.426 --> 13:12:01.436 align:start position:0% that the 10 networks connected to 13:12:01.436 --> 13:12:05.086 align:start position:0% that the 10 networks connected to so<13:12:02.040> if<13:12:02.160> if<13:12:02.460> I<13:12:02.700> try<13:12:02.880> and<13:12:03.060> Trace<13:12:03.500> traffic<13:12:04.500> going 13:12:05.086 --> 13:12:05.096 align:start position:0% so if if I try and Trace traffic going 13:12:05.096 --> 13:12:08.450 align:start position:0% so if if I try and Trace traffic going from<13:12:05.276> router<13:12:05.700> 0<13:12:05.936> to<13:12:06.360> the<13:12:06.596> 10<13:12:06.720> Network<13:12:07.340> you<13:12:08.340> can 13:12:08.450 --> 13:12:08.460 align:start position:0% from router 0 to the 10 Network you can 13:12:08.460 --> 13:12:10.790 align:start position:0% from router 0 to the 10 Network you can see<13:12:08.756> it's<13:12:09.180> traced<13:12:09.660> and<13:12:09.840> it's<13:12:10.020> used<13:12:10.200> the<13:12:10.500> next 13:12:10.790 --> 13:12:10.800 align:start position:0% see it's traced and it's used the next 13:12:10.800 --> 13:12:14.170 align:start position:0% see it's traced and it's used the next hop<13:12:11.096> address<13:12:11.340> of 13:12:14.170 --> 13:12:14.180 align:start position:0% hop address of 13:12:14.180 --> 13:12:18.406 align:start position:0% hop address of 172.16.1.2<13:12:15.180> which<13:12:15.960> is<13:12:16.080> the<13:12:16.256> gigabit<13:12:17.060> uh<13:12:18.060> zero 13:12:18.406 --> 13:12:18.416 align:start position:0% 172.16.1.2 which is the gigabit uh zero 13:12:18.416 --> 13:12:20.990 align:start position:0% 172.16.1.2 which is the gigabit uh zero slash<13:12:18.660> one<13:12:18.960> of<13:12:19.380> router<13:12:19.860> one 13:12:20.990 --> 13:12:21.000 align:start position:0% slash one of router one 13:12:21.000 --> 13:12:23.210 align:start position:0% slash one of router one and<13:12:21.540> so<13:12:21.840> that's<13:12:22.080> basically<13:12:22.436> the<13:12:22.800> preferred 13:12:23.210 --> 13:12:23.220 align:start position:0% and so that's basically the preferred 13:12:23.220 --> 13:12:25.426 align:start position:0% and so that's basically the preferred path<13:12:23.460> if<13:12:23.936> for<13:12:24.116> some<13:12:24.416> reason<13:12:24.540> that<13:12:24.900> path<13:12:25.140> went 13:12:25.426 --> 13:12:25.436 align:start position:0% path if for some reason that path went 13:12:25.436 --> 13:12:27.890 align:start position:0% path if for some reason that path went down<13:12:25.740> it<13:12:26.220> would<13:12:26.340> start<13:12:26.520> using<13:12:27.000> the<13:12:27.300> next<13:12:27.660> best 13:12:27.890 --> 13:12:27.900 align:start position:0% down it would start using the next best 13:12:27.900 --> 13:12:31.850 align:start position:0% down it would start using the next best a<13:12:28.320> next<13:12:28.740> best<13:12:29.096> ad<13:12:29.640> which<13:12:30.480> is<13:12:30.596> Rip 13:12:31.850 --> 13:12:31.860 align:start position:0% a next best ad which is Rip 13:12:31.860 --> 13:12:34.370 align:start position:0% a next best ad which is Rip writing<13:12:32.580> table<13:12:32.756> writing<13:12:33.596> information<13:12:33.776> is 13:12:34.370 --> 13:12:34.380 align:start position:0% writing table writing information is 13:12:34.380 --> 13:12:36.470 align:start position:0% writing table writing information is populated<13:12:34.860> through<13:12:35.400> a<13:12:35.756> few<13:12:35.880> different<13:12:36.060> means 13:12:36.470 --> 13:12:36.480 align:start position:0% populated through a few different means 13:12:36.480 --> 13:12:39.530 align:start position:0% populated through a few different means it<13:12:36.596> can<13:12:36.776> be<13:12:36.900> a<13:12:37.200> connected<13:12:37.616> route<13:12:37.916> actually<13:12:38.640> a 13:12:39.530 --> 13:12:39.540 align:start position:0% it can be a connected route actually a 13:12:39.540 --> 13:12:42.350 align:start position:0% it can be a connected route actually a static<13:12:39.960> route<13:12:40.400> I<13:12:41.400> I<13:12:41.700> suppose<13:12:41.936> I<13:12:42.180> said 13:12:42.350 --> 13:12:42.360 align:start position:0% static route I I suppose I said 13:12:42.360 --> 13:12:44.450 align:start position:0% static route I I suppose I said connected<13:12:42.776> there<13:12:43.020> or<13:12:43.500> a<13:12:43.680> dynamic<13:12:44.040> routing 13:12:44.450 --> 13:12:44.460 align:start position:0% connected there or a dynamic routing 13:12:44.460 --> 13:12:46.850 align:start position:0% connected there or a dynamic routing protocol<13:12:44.820> what<13:12:45.540> you<13:12:45.720> can<13:12:45.900> figure<13:12:46.080> depends<13:12:46.680> on 13:12:46.850 --> 13:12:46.860 align:start position:0% protocol what you can figure depends on 13:12:46.860 --> 13:12:48.470 align:start position:0% protocol what you can figure depends on your<13:12:47.040> network<13:12:47.276> if<13:12:47.700> it's<13:12:47.880> a<13:12:48.116> tiny<13:12:48.360> little 13:12:48.470 --> 13:12:48.480 align:start position:0% your network if it's a tiny little 13:12:48.480 --> 13:12:51.290 align:start position:0% your network if it's a tiny little Network<13:12:48.776> or<13:12:49.256> if<13:12:49.616> it's<13:12:49.916> in<13:12:50.276> a<13:12:50.880> remote<13:12:50.936> office 13:12:51.290 --> 13:12:51.300 align:start position:0% Network or if it's in a remote office 13:12:51.300 --> 13:12:53.630 align:start position:0% Network or if it's in a remote office somewhere<13:12:51.840> then<13:12:52.560> you<13:12:52.740> probably<13:12:52.916> use<13:12:53.096> a<13:12:53.276> static 13:12:53.630 --> 13:12:53.640 align:start position:0% somewhere then you probably use a static 13:12:53.640 --> 13:12:55.970 align:start position:0% somewhere then you probably use a static route<13:12:53.820> to<13:12:54.180> just<13:12:54.360> send<13:12:54.720> all<13:12:54.900> traffic<13:12:55.200> to<13:12:55.800> the 13:12:55.970 --> 13:12:55.980 align:start position:0% route to just send all traffic to the 13:12:55.980 --> 13:12:58.190 align:start position:0% route to just send all traffic to the next<13:12:56.160> top<13:12:56.400> router 13:12:58.190 --> 13:12:58.200 align:start position:0% next top router 13:12:58.200 --> 13:13:00.766 align:start position:0% next top router so<13:12:58.800> this<13:12:58.980> is<13:12:59.096> the<13:12:59.276> show<13:12:59.400> IP<13:12:59.820> route<13:13:00.116> and<13:13:00.596> I've 13:13:00.766 --> 13:13:00.776 align:start position:0% so this is the show IP route and I've 13:13:00.776 --> 13:13:03.070 align:start position:0% so this is the show IP route and I've highlighted<13:13:01.320> in<13:13:01.436> red<13:13:01.616> the<13:13:01.916> connected<13:13:02.460> routes 13:13:03.070 --> 13:13:03.080 align:start position:0% highlighted in red the connected routes 13:13:03.080 --> 13:13:06.710 align:start position:0% highlighted in red the connected routes for<13:13:04.160> router<13:13:05.160> 0. 13:13:06.710 --> 13:13:06.720 align:start position:0% for router 0. 13:13:06.720 --> 13:13:10.970 align:start position:0% for router 0. it's<13:13:07.140> a<13:13:07.380> 17216<13:13:08.276> another<13:13:08.840> 192.1681<13:13:09.840> network<13:13:10.140> is 13:13:10.970 --> 13:13:10.980 align:start position:0% it's a 17216 another 192.1681 network is 13:13:10.980 --> 13:13:15.530 align:start position:0% it's a 17216 another 192.1681 network is showing<13:13:11.820> as<13:13:12.116> C<13:13:12.416> connected<13:13:13.276> are<13:13:14.276> in<13:13:14.880> Cisco<13:13:15.300> at 13:13:15.530 --> 13:13:15.540 align:start position:0% showing as C connected are in Cisco at 13:13:15.540 --> 13:13:17.810 align:start position:0% showing as C connected are in Cisco at least<13:13:15.660> that's<13:13:16.020> for<13:13:16.320> it<13:13:16.560> oh<13:13:16.860> stands<13:13:17.220> for<13:13:17.276> ospf 13:13:17.810 --> 13:13:17.820 align:start position:0% least that's for it oh stands for ospf 13:13:17.820 --> 13:13:22.970 align:start position:0% least that's for it oh stands for ospf and<13:13:18.360> L<13:13:18.596> stands<13:13:19.080> for<13:13:19.200> local 13:13:22.970 --> 13:13:22.980 align:start position:0% 13:13:22.980 --> 13:13:25.906 align:start position:0% static<13:13:23.756> route<13:13:24.000> is<13:13:24.776> a<13:13:25.020> route<13:13:25.200> that<13:13:25.436> is<13:13:25.616> manually 13:13:25.906 --> 13:13:25.916 align:start position:0% static route is a route that is manually 13:13:25.916 --> 13:13:28.606 align:start position:0% static route is a route that is manually added<13:13:26.220> to<13:13:26.340> a<13:13:26.520> router<13:13:26.820> by<13:13:27.000> administrator 13:13:28.606 --> 13:13:28.616 align:start position:0% added to a router by administrator 13:13:28.616 --> 13:13:30.950 align:start position:0% added to a router by administrator so<13:13:29.220> you<13:13:29.400> can<13:13:29.520> see<13:13:29.700> here<13:13:29.936> router<13:13:30.416> 1<13:13:30.540> on<13:13:30.776> the<13:13:30.900> left 13:13:30.950 --> 13:13:30.960 align:start position:0% so you can see here router 1 on the left 13:13:30.960 --> 13:13:33.790 align:start position:0% so you can see here router 1 on the left has<13:13:31.200> got<13:13:31.380> a<13:13:31.560> default<13:13:31.916> static<13:13:32.520> route 13:13:33.790 --> 13:13:33.800 align:start position:0% has got a default static route 13:13:33.800 --> 13:13:36.050 align:start position:0% has got a default static route which<13:13:34.800> you<13:13:34.980> can<13:13:35.096> recognize<13:13:35.400> it<13:13:35.580> because<13:13:35.756> it's 13:13:36.050 --> 13:13:36.060 align:start position:0% which you can recognize it because it's 13:13:36.060 --> 13:13:38.330 align:start position:0% which you can recognize it because it's all<13:13:36.240> zeros 13:13:38.330 --> 13:13:38.340 align:start position:0% all zeros 13:13:38.340 --> 13:13:40.606 align:start position:0% all zeros I'll<13:13:38.700> give<13:13:38.880> you<13:13:39.000> an<13:13:39.116> example<13:13:39.416> in<13:13:39.660> a<13:13:39.776> moment<13:13:39.960> if 13:13:40.606 --> 13:13:40.616 align:start position:0% I'll give you an example in a moment if 13:13:40.616 --> 13:13:43.130 align:start position:0% I'll give you an example in a moment if router<13:13:41.096> 1<13:13:41.276> receives<13:13:42.060> traffic<13:13:42.360> destined<13:13:43.080> to 13:13:43.130 --> 13:13:43.140 align:start position:0% router 1 receives traffic destined to 13:13:43.140 --> 13:13:45.586 align:start position:0% router 1 receives traffic destined to any<13:13:43.380> network<13:13:43.680> other<13:13:44.400> than<13:13:44.640> a<13:13:44.820> local<13:13:45.000> one<13:13:45.300> are 13:13:45.586 --> 13:13:45.596 align:start position:0% any network other than a local one are 13:13:45.596 --> 13:13:47.330 align:start position:0% any network other than a local one are you<13:13:45.720> one<13:13:45.900> that's<13:13:46.020> connected<13:13:46.500> it<13:13:47.160> should 13:13:47.330 --> 13:13:47.340 align:start position:0% you one that's connected it should 13:13:47.340 --> 13:13:48.710 align:start position:0% you one that's connected it should really<13:13:47.520> know<13:13:47.756> where<13:13:48.000> to<13:13:48.116> send<13:13:48.300> that<13:13:48.540> traffic 13:13:48.710 --> 13:13:48.720 align:start position:0% really know where to send that traffic 13:13:48.720 --> 13:13:51.530 align:start position:0% really know where to send that traffic if<13:13:49.680> there's<13:13:49.800> no<13:13:50.040> entry<13:13:50.340> listed<13:13:50.756> then<13:13:51.000> it<13:13:51.240> by 13:13:51.530 --> 13:13:51.540 align:start position:0% if there's no entry listed then it by 13:13:51.540 --> 13:13:55.190 align:start position:0% if there's no entry listed then it by default<13:13:51.900> routers<13:13:52.380> will<13:13:52.560> drop<13:13:52.800> the<13:13:52.980> packets 13:13:55.190 --> 13:13:55.200 align:start position:0% default routers will drop the packets 13:13:55.200 --> 13:13:57.530 align:start position:0% default routers will drop the packets since<13:13:55.740> R2<13:13:56.160> is<13:13:56.400> the<13:13:56.520> next<13:13:56.640> hop<13:13:56.820> for<13:13:57.060> router<13:13:57.416> want 13:13:57.530 --> 13:13:57.540 align:start position:0% since R2 is the next hop for router want 13:13:57.540 --> 13:13:59.210 align:start position:0% since R2 is the next hop for router want to<13:13:57.660> reach<13:13:57.900> the<13:13:58.080> internet<13:13:58.200> what<13:13:58.916> we<13:13:59.096> can 13:13:59.210 --> 13:13:59.220 align:start position:0% to reach the internet what we can 13:13:59.220 --> 13:14:00.830 align:start position:0% to reach the internet what we can basically<13:13:59.520> do<13:13:59.640> is<13:13:59.756> put<13:13:59.936> a<13:14:00.116> static<13:14:00.416> route<13:14:00.596> on 13:14:00.830 --> 13:14:00.840 align:start position:0% basically do is put a static route on 13:14:00.840 --> 13:14:03.470 align:start position:0% basically do is put a static route on router<13:14:01.200> 1<13:14:01.380> saying<13:14:01.800> send<13:14:01.980> any<13:14:02.160> traffic<13:14:02.460> to<13:14:03.240> any 13:14:03.470 --> 13:14:03.480 align:start position:0% router 1 saying send any traffic to any 13:14:03.480 --> 13:14:06.586 align:start position:0% router 1 saying send any traffic to any network<13:14:03.776> over<13:14:04.560> to<13:14:04.800> R2<13:14:05.276> and<13:14:05.756> let<13:14:05.936> R2<13:14:06.300> worry 13:14:06.586 --> 13:14:06.596 align:start position:0% network over to R2 and let R2 worry 13:14:06.596 --> 13:14:09.530 align:start position:0% network over to R2 and let R2 worry about<13:14:06.776> where<13:14:07.200> to<13:14:07.380> send<13:14:07.616> it 13:14:09.530 --> 13:14:09.540 align:start position:0% about where to send it 13:14:09.540 --> 13:14:11.330 align:start position:0% about where to send it when<13:14:10.020> our<13:14:10.256> one<13:14:10.436> receives<13:14:10.740> the<13:14:10.860> traffic<13:14:10.980> for<13:14:11.220> a 13:14:11.330 --> 13:14:11.340 align:start position:0% when our one receives the traffic for a 13:14:11.340 --> 13:14:12.830 align:start position:0% when our one receives the traffic for a network<13:14:11.460> it's<13:14:11.820> not<13:14:11.936> available<13:14:12.116> it<13:14:12.596> will<13:14:12.720> now 13:14:12.830 --> 13:14:12.840 align:start position:0% network it's not available it will now 13:14:12.840 --> 13:14:15.290 align:start position:0% network it's not available it will now send<13:14:13.080> it<13:14:13.320> out<13:14:13.616> of<13:14:13.740> its<13:14:14.040> interface<13:14:14.400> using<13:14:15.116> the 13:14:15.290 --> 13:14:15.300 align:start position:0% send it out of its interface using the 13:14:15.300 --> 13:14:17.510 align:start position:0% send it out of its interface using the default<13:14:15.596> static<13:14:16.020> routes<13:14:16.860> I've<13:14:17.276> actually 13:14:17.510 --> 13:14:17.520 align:start position:0% default static routes I've actually 13:14:17.520 --> 13:14:20.266 align:start position:0% default static routes I've actually configured<13:14:18.180> a<13:14:18.900> static<13:14:19.436> route<13:14:19.616> here<13:14:19.860> on<13:14:20.096> a 13:14:20.266 --> 13:14:20.276 align:start position:0% configured a static route here on a 13:14:20.276 --> 13:14:22.570 align:start position:0% configured a static route here on a Cisco<13:14:20.580> router 13:14:22.570 --> 13:14:22.580 align:start position:0% Cisco router 13:14:22.580 --> 13:14:25.850 align:start position:0% Cisco router iprout000<13:14:23.580> and<13:14:24.240> then<13:14:24.480> zero<13:14:24.900> zero<13:14:25.256> zero<13:14:25.560> zero 13:14:25.850 --> 13:14:25.860 align:start position:0% iprout000 and then zero zero zero zero 13:14:25.860 --> 13:14:26.990 align:start position:0% iprout000 and then zero zero zero zero so<13:14:26.040> any 13:14:26.990 --> 13:14:27.000 align:start position:0% so any 13:14:27.000 --> 13:14:28.870 align:start position:0% so any and<13:14:27.596> IP<13:14:28.080> address 13:14:28.870 --> 13:14:28.880 align:start position:0% and IP address 13:14:28.880 --> 13:14:33.050 align:start position:0% and IP address and<13:14:29.880> any<13:14:30.116> network<13:14:30.416> go<13:14:31.320> out<13:14:31.500> to<13:14:31.980> our<13:14:32.520> gigabit 13:14:33.050 --> 13:14:33.060 align:start position:0% and any network go out to our gigabit 13:14:33.060 --> 13:14:36.650 align:start position:0% and any network go out to our gigabit Ethernet<13:14:33.960> interface<13:14:34.500> instead<13:14:35.340> of<13:14:35.400> g00<13:14:35.936> I 13:14:36.650 --> 13:14:36.660 align:start position:0% Ethernet interface instead of g00 I 13:14:36.660 --> 13:14:38.030 align:start position:0% Ethernet interface instead of g00 I could<13:14:36.776> have<13:14:36.900> put<13:14:37.020> an<13:14:37.200> IP<13:14:37.436> address<13:14:37.616> for<13:14:37.916> the 13:14:38.030 --> 13:14:38.040 align:start position:0% could have put an IP address for the 13:14:38.040 --> 13:14:40.130 align:start position:0% could have put an IP address for the next<13:14:38.096> top<13:14:38.340> router<13:14:38.936> as<13:14:39.416> long<13:14:39.660> as<13:14:39.776> the<13:14:39.840> router 13:14:40.130 --> 13:14:40.140 align:start position:0% next top router as long as the router 13:14:40.140 --> 13:14:41.990 align:start position:0% next top router as long as the router knows<13:14:40.380> how<13:14:40.500> to<13:14:40.616> get<13:14:40.800> there 13:14:41.990 --> 13:14:42.000 align:start position:0% knows how to get there 13:14:42.000 --> 13:14:44.810 align:start position:0% knows how to get there and<13:14:42.776> for<13:14:43.080> the<13:14:43.256> R2<13:14:43.740> you<13:14:44.096> can<13:14:44.160> do<13:14:44.340> the<13:14:44.520> same<13:14:44.640> thing 13:14:44.810 --> 13:14:44.820 align:start position:0% and for the R2 you can do the same thing 13:14:44.820 --> 13:14:46.850 align:start position:0% and for the R2 you can do the same thing you<13:14:45.060> could<13:14:45.180> have<13:14:45.300> a<13:14:45.480> static<13:14:45.776> route<13:14:46.020> as<13:14:46.616> long<13:14:46.740> as 13:14:46.850 --> 13:14:46.860 align:start position:0% you could have a static route as long as 13:14:46.860 --> 13:14:48.530 align:start position:0% you could have a static route as long as you<13:14:46.980> know<13:14:47.160> your<13:14:47.460> next<13:14:47.580> hop<13:14:47.880> which<13:14:48.240> would<13:14:48.360> be 13:14:48.530 --> 13:14:48.540 align:start position:0% you know your next hop which would be 13:14:48.540 --> 13:14:51.830 align:start position:0% you know your next hop which would be your<13:14:48.720> ISP<13:14:49.200> router<13:14:49.740> let<13:14:50.220> your<13:14:50.460> ISP<13:14:51.060> take<13:14:51.660> care 13:14:51.830 --> 13:14:51.840 align:start position:0% your ISP router let your ISP take care 13:14:51.840 --> 13:14:57.586 align:start position:0% your ISP router let your ISP take care of<13:14:51.960> any<13:14:52.080> routing<13:14:52.560> decisions 13:14:57.586 --> 13:14:57.596 align:start position:0% 13:14:57.596 --> 13:14:59.630 align:start position:0% all<13:14:58.020> right<13:14:58.140> Dynamic<13:14:58.560> routing<13:14:58.916> practicals 13:14:59.630 --> 13:14:59.640 align:start position:0% all right Dynamic routing practicals 13:14:59.640 --> 13:15:01.670 align:start position:0% all right Dynamic routing practicals this<13:15:00.240> is<13:15:00.360> a<13:15:00.540> routing<13:15:00.960> protocol<13:15:01.320> that 13:15:01.670 --> 13:15:01.680 align:start position:0% this is a routing protocol that 13:15:01.680 --> 13:15:03.170 align:start position:0% this is a routing protocol that dynamically<13:15:02.220> builds<13:15:02.580> routing<13:15:02.936> information 13:15:03.170 --> 13:15:03.180 align:start position:0% dynamically builds routing information 13:15:03.180 --> 13:15:05.746 align:start position:0% dynamically builds routing information such<13:15:03.720> as<13:15:03.900> the<13:15:04.140> following<13:15:04.500> the<13:15:05.160> network<13:15:05.340> the 13:15:05.746 --> 13:15:05.756 align:start position:0% such as the following the network the 13:15:05.756 --> 13:15:08.330 align:start position:0% such as the following the network the next<13:15:05.936> harp<13:15:06.480> and<13:15:07.200> it<13:15:07.436> will<13:15:07.560> build<13:15:07.680> a<13:15:07.916> topology 13:15:08.330 --> 13:15:08.340 align:start position:0% next harp and it will build a topology 13:15:08.340 --> 13:15:10.970 align:start position:0% next harp and it will build a topology table<13:15:09.300> and<13:15:09.660> from<13:15:09.840> the<13:15:09.960> topology<13:15:10.380> table<13:15:10.680> it 13:15:10.970 --> 13:15:10.980 align:start position:0% table and from the topology table it 13:15:10.980 --> 13:15:12.890 align:start position:0% table and from the topology table it will<13:15:11.096> choose<13:15:11.220> the<13:15:11.520> best<13:15:11.640> route<13:15:11.936> to<13:15:12.480> put<13:15:12.596> in<13:15:12.776> the 13:15:12.890 --> 13:15:12.900 align:start position:0% will choose the best route to put in the 13:15:12.900 --> 13:15:16.490 align:start position:0% will choose the best route to put in the routing<13:15:13.256> table<13:15:13.500> and<13:15:14.276> the<13:15:14.460> topology<13:15:15.300> table 13:15:16.490 --> 13:15:16.500 align:start position:0% routing table and the topology table 13:15:16.500 --> 13:15:19.730 align:start position:0% routing table and the topology table can<13:15:17.276> supply<13:15:17.880> second<13:15:18.360> third<13:15:18.720> and<13:15:19.020> fourth<13:15:19.380> best 13:15:19.730 --> 13:15:19.740 align:start position:0% can supply second third and fourth best 13:15:19.740 --> 13:15:21.406 align:start position:0% can supply second third and fourth best routes<13:15:20.220> and<13:15:20.400> so<13:15:20.580> on 13:15:21.406 --> 13:15:21.416 align:start position:0% routes and so on 13:15:21.416 --> 13:15:23.926 align:start position:0% routes and so on static<13:15:22.256> routing<13:15:22.680> does<13:15:22.980> not<13:15:23.160> do<13:15:23.340> well<13:15:23.520> in<13:15:23.756> large 13:15:23.926 --> 13:15:23.936 align:start position:0% static routing does not do well in large 13:15:23.936 --> 13:15:25.310 align:start position:0% static routing does not do well in large networks<13:15:24.480> because<13:15:24.720> you<13:15:24.900> would<13:15:25.020> have<13:15:25.140> to 13:15:25.310 --> 13:15:25.320 align:start position:0% networks because you would have to 13:15:25.320 --> 13:15:30.350 align:start position:0% networks because you would have to manually<13:15:25.740> add<13:15:26.700> 5<13:15:27.540> 10<13:15:27.776> 15<13:15:28.080> 20<13:15:28.756> routes<13:15:29.756> per 13:15:30.350 --> 13:15:30.360 align:start position:0% manually add 5 10 15 20 routes per 13:15:30.360 --> 13:15:32.030 align:start position:0% manually add 5 10 15 20 routes per router 13:15:32.030 --> 13:15:32.040 align:start position:0% router 13:15:32.040 --> 13:15:33.290 align:start position:0% router so<13:15:32.276> you<13:15:32.400> can<13:15:32.520> imagine<13:15:32.700> you're<13:15:32.936> going<13:15:33.116> to<13:15:33.180> have 13:15:33.290 --> 13:15:33.300 align:start position:0% so you can imagine you're going to have 13:15:33.300 --> 13:15:35.390 align:start position:0% so you can imagine you're going to have a<13:15:33.416> lot<13:15:33.540> of<13:15:33.660> work<13:15:33.840> there<13:15:34.256> if<13:15:34.740> you<13:15:34.916> decide<13:15:35.220> to 13:15:35.390 --> 13:15:35.400 align:start position:0% a lot of work there if you decide to 13:15:35.400 --> 13:15:37.490 align:start position:0% a lot of work there if you decide to change<13:15:35.640> the<13:15:36.300> IP<13:15:36.540> address<13:15:36.720> and<13:15:36.960> or<13:15:37.200> even<13:15:37.320> add 13:15:37.490 --> 13:15:37.500 align:start position:0% change the IP address and or even add 13:15:37.500 --> 13:15:39.230 align:start position:0% change the IP address and or even add one<13:15:37.740> device 13:15:39.230 --> 13:15:39.240 align:start position:0% one device 13:15:39.240 --> 13:15:41.210 align:start position:0% one device so<13:15:39.840> you<13:15:40.200> don't<13:15:40.320> want<13:15:40.500> your<13:15:40.680> routers<13:15:41.040> to 13:15:41.210 --> 13:15:41.220 align:start position:0% so you don't want your routers to 13:15:41.220 --> 13:15:43.550 align:start position:0% so you don't want your routers to automatically<13:15:41.756> learn<13:15:42.060> the<13:15:42.300> routes<13:15:42.720> update 13:15:43.550 --> 13:15:43.560 align:start position:0% automatically learn the routes update 13:15:43.560 --> 13:15:45.290 align:start position:0% automatically learn the routes update any<13:15:43.740> changes<13:15:44.276> without<13:15:44.580> you<13:15:44.820> having<13:15:45.000> to<13:15:45.180> worry 13:15:45.290 --> 13:15:45.300 align:start position:0% any changes without you having to worry 13:15:45.300 --> 13:15:47.330 align:start position:0% any changes without you having to worry about<13:15:45.540> it<13:15:45.900> and<13:15:46.500> this<13:15:46.616> is<13:15:46.740> where<13:15:46.860> routing 13:15:47.330 --> 13:15:47.340 align:start position:0% about it and this is where routing 13:15:47.340 --> 13:15:50.030 align:start position:0% about it and this is where routing protocols<13:15:47.880> make<13:15:48.060> our<13:15:48.240> life<13:15:48.480> a<13:15:48.660> lot<13:15:48.776> easier 13:15:50.030 --> 13:15:50.040 align:start position:0% protocols make our life a lot easier 13:15:50.040 --> 13:15:51.890 align:start position:0% protocols make our life a lot easier once<13:15:50.700> you've<13:15:50.820> configured<13:15:51.240> which<13:15:51.480> networks 13:15:51.890 --> 13:15:51.900 align:start position:0% once you've configured which networks 13:15:51.900 --> 13:15:54.050 align:start position:0% once you've configured which networks you<13:15:52.020> want<13:15:52.140> to<13:15:52.256> advertise<13:15:52.860> then<13:15:53.580> depending<13:15:54.000> on 13:15:54.050 --> 13:15:54.060 align:start position:0% you want to advertise then depending on 13:15:54.060 --> 13:15:55.970 align:start position:0% you want to advertise then depending on which<13:15:54.240> protocol<13:15:54.660> you're<13:15:54.960> using 13:15:55.970 --> 13:15:55.980 align:start position:0% which protocol you're using 13:15:55.980 --> 13:15:57.766 align:start position:0% which protocol you're using and<13:15:56.340> the<13:15:56.520> writing<13:15:56.820> protocol<13:15:57.116> will<13:15:57.416> go<13:15:57.596> ahead 13:15:57.766 --> 13:15:57.776 align:start position:0% and the writing protocol will go ahead 13:15:57.776 --> 13:15:59.990 align:start position:0% and the writing protocol will go ahead and<13:15:57.960> run<13:15:58.200> on<13:15:58.436> automatic<13:15:58.980> settings<13:15:59.220> unless<13:15:59.820> you 13:15:59.990 --> 13:16:00.000 align:start position:0% and run on automatic settings unless you 13:16:00.000 --> 13:16:03.406 align:start position:0% and run on automatic settings unless you change<13:16:00.240> the<13:16:00.480> settings<13:16:00.720> for<13:16:01.020> whatever<13:16:01.436> reason 13:16:03.406 --> 13:16:03.416 align:start position:0% change the settings for whatever reason 13:16:03.416 --> 13:16:05.926 align:start position:0% change the settings for whatever reason the<13:16:04.080> routers<13:16:04.800> use<13:16:04.980> the<13:16:05.096> router<13:16:05.340> protocols<13:16:05.820> to 13:16:05.926 --> 13:16:05.936 align:start position:0% the routers use the router protocols to 13:16:05.936 --> 13:16:07.790 align:start position:0% the routers use the router protocols to learn<13:16:06.060> about<13:16:06.240> available<13:16:06.540> routes<13:16:07.200> to<13:16:07.500> build<13:16:07.616> a 13:16:07.790 --> 13:16:07.800 align:start position:0% learn about available routes to build a 13:16:07.800 --> 13:16:10.550 align:start position:0% learn about available routes to build a routing<13:16:08.160> table 13:16:10.550 --> 13:16:10.560 align:start position:0% 13:16:10.560 --> 13:16:13.730 align:start position:0% and<13:16:11.276> the<13:16:11.880> routing<13:16:12.300> protocol<13:16:12.900> communicates 13:16:13.730 --> 13:16:13.740 align:start position:0% and the routing protocol communicates 13:16:13.740 --> 13:16:15.530 align:start position:0% and the routing protocol communicates with<13:16:13.916> the<13:16:14.096> same<13:16:14.276> router<13:16:14.756> protocol<13:16:15.060> on<13:16:15.416> another 13:16:15.530 --> 13:16:15.540 align:start position:0% with the same router protocol on another 13:16:15.540 --> 13:16:18.290 align:start position:0% with the same router protocol on another router<13:16:16.140> you<13:16:16.860> can't<13:16:16.980> have<13:16:17.160> rip<13:16:17.520> on<13:16:17.700> one<13:16:17.880> router 13:16:18.290 --> 13:16:18.300 align:start position:0% router you can't have rip on one router 13:16:18.300 --> 13:16:20.210 align:start position:0% router you can't have rip on one router communicating<13:16:18.840> with<13:16:19.200> rspf<13:16:19.800> on<13:16:19.980> the<13:16:20.096> other 13:16:20.210 --> 13:16:20.220 align:start position:0% communicating with rspf on the other 13:16:20.220 --> 13:16:22.310 align:start position:0% communicating with rspf on the other because<13:16:20.820> they<13:16:21.180> work<13:16:21.416> in<13:16:21.596> entirely<13:16:22.140> different 13:16:22.310 --> 13:16:22.320 align:start position:0% because they work in entirely different 13:16:22.320 --> 13:16:25.670 align:start position:0% because they work in entirely different ways<13:16:22.800> and<13:16:23.400> use<13:16:23.640> different<13:16:24.500> protocols<13:16:25.500> and 13:16:25.670 --> 13:16:25.680 align:start position:0% ways and use different protocols and 13:16:25.680 --> 13:16:27.106 align:start position:0% ways and use different protocols and ports 13:16:27.106 --> 13:16:27.116 align:start position:0% ports 13:16:27.116 --> 13:16:30.530 align:start position:0% ports to<13:16:28.200> um<13:16:28.200> send<13:16:28.680> their<13:16:28.860> information 13:16:30.530 --> 13:16:30.540 align:start position:0% to um send their information 13:16:30.540 --> 13:16:32.330 align:start position:0% to um send their information so<13:16:31.020> this<13:16:31.200> information<13:16:31.380> is<13:16:31.860> placed<13:16:32.160> in<13:16:32.220> the 13:16:32.330 --> 13:16:32.340 align:start position:0% so this information is placed in the 13:16:32.340 --> 13:16:34.190 align:start position:0% so this information is placed in the writing<13:16:32.700> table 13:16:34.190 --> 13:16:34.200 align:start position:0% writing table 13:16:34.200 --> 13:16:36.406 align:start position:0% writing table so<13:16:34.616> as<13:16:34.740> an<13:16:34.860> example<13:16:35.160> here<13:16:35.400> router<13:16:35.880> one<13:16:36.000> two<13:16:36.180> and 13:16:36.406 --> 13:16:36.416 align:start position:0% so as an example here router one two and 13:16:36.416 --> 13:16:38.630 align:start position:0% so as an example here router one two and three<13:16:36.596> you've<13:16:36.840> got<13:16:36.960> some<13:16:37.200> different<13:16:37.640> networks 13:16:38.630 --> 13:16:38.640 align:start position:0% three you've got some different networks 13:16:38.640 --> 13:16:40.790 align:start position:0% three you've got some different networks connected 13:16:40.790 --> 13:16:40.800 align:start position:0% connected 13:16:40.800 --> 13:16:43.550 align:start position:0% connected a<13:16:41.160> pc1's<13:16:41.880> default<13:16:42.116> gateway<13:16:42.540> because<13:16:42.900> PCS 13:16:43.550 --> 13:16:43.560 align:start position:0% a pc1's default gateway because PCS 13:16:43.560 --> 13:16:44.926 align:start position:0% a pc1's default gateway because PCS won't<13:16:43.680> do<13:16:43.860> the<13:16:43.980> routing<13:16:44.276> will<13:16:44.520> always<13:16:44.700> be 13:16:44.926 --> 13:16:44.936 align:start position:0% won't do the routing will always be 13:16:44.936 --> 13:16:47.030 align:start position:0% won't do the routing will always be router<13:16:45.416> one<13:16:45.596> you'll<13:16:46.320> just<13:16:46.436> send<13:16:46.616> all<13:16:46.800> traffic 13:16:47.030 --> 13:16:47.040 align:start position:0% router one you'll just send all traffic 13:16:47.040 --> 13:16:50.510 align:start position:0% router one you'll just send all traffic to<13:16:47.520> whatever<13:16:48.300> the<13:16:48.776> IP<13:16:49.680> address<13:16:49.916> is<13:16:50.160> of<13:16:50.400> the 13:16:50.510 --> 13:16:50.520 align:start position:0% to whatever the IP address is of the 13:16:50.520 --> 13:16:52.970 align:start position:0% to whatever the IP address is of the router<13:16:50.880> there<13:16:51.060> normally<13:16:51.776> in<13:16:52.200> In<13:16:52.436> fairness<13:16:52.800> the 13:16:52.970 --> 13:16:52.980 align:start position:0% router there normally in In fairness the 13:16:52.980 --> 13:16:54.830 align:start position:0% router there normally in In fairness the PC<13:16:53.276> is<13:16:53.460> connected<13:16:53.756> to<13:16:53.936> a<13:16:54.116> switch<13:16:54.240> and<13:16:54.480> then<13:16:54.660> a 13:16:54.830 --> 13:16:54.840 align:start position:0% PC is connected to a switch and then a 13:16:54.840 --> 13:16:58.670 align:start position:0% PC is connected to a switch and then a router<13:16:55.200> this<13:16:55.740> is<13:16:55.916> just<13:16:56.160> a<13:16:56.520> simplified<13:16:57.180> diagram 13:16:58.670 --> 13:16:58.680 align:start position:0% router this is just a simplified diagram 13:16:58.680 --> 13:17:00.950 align:start position:0% router this is just a simplified diagram so<13:16:59.220> if<13:16:59.400> router<13:16:59.820> one<13:16:59.936> has<13:17:00.116> two<13:17:00.300> routes<13:17:00.660> to<13:17:00.840> the 13:17:00.950 --> 13:17:00.960 align:start position:0% so if router one has two routes to the 13:17:00.960 --> 13:17:02.086 align:start position:0% so if router one has two routes to the internet<13:17:01.080> then<13:17:01.436> it<13:17:01.560> will<13:17:01.680> choose<13:17:01.860> the<13:17:01.980> best 13:17:02.086 --> 13:17:02.096 align:start position:0% internet then it will choose the best 13:17:02.096 --> 13:17:03.766 align:start position:0% internet then it will choose the best one<13:17:02.276> depending<13:17:02.756> on<13:17:02.880> the<13:17:03.060> routing<13:17:03.360> protocol 13:17:03.766 --> 13:17:03.776 align:start position:0% one depending on the routing protocol 13:17:03.776 --> 13:17:06.710 align:start position:0% one depending on the routing protocol unless<13:17:04.740> you've<13:17:05.040> changed<13:17:05.460> the<13:17:05.700> settings<13:17:06.116> you 13:17:06.710 --> 13:17:06.720 align:start position:0% unless you've changed the settings you 13:17:06.720 --> 13:17:09.650 align:start position:0% unless you've changed the settings you can<13:17:06.900> obviously<13:17:07.740> manipulate<13:17:08.340> things 13:17:09.650 --> 13:17:09.660 align:start position:0% can obviously manipulate things 13:17:09.660 --> 13:17:11.570 align:start position:0% can obviously manipulate things if<13:17:09.960> rip<13:17:10.256> has<13:17:10.436> been<13:17:10.560> used<13:17:10.680> then<13:17:10.860> it<13:17:11.040> will<13:17:11.160> choose 13:17:11.570 --> 13:17:11.580 align:start position:0% if rip has been used then it will choose 13:17:11.580 --> 13:17:13.130 align:start position:0% if rip has been used then it will choose a<13:17:11.936> hop<13:17:12.060> count<13:17:12.360> and<13:17:12.596> it<13:17:12.720> will<13:17:12.840> choose<13:17:12.960> the 13:17:13.130 --> 13:17:13.140 align:start position:0% a hop count and it will choose the 13:17:13.140 --> 13:17:15.050 align:start position:0% a hop count and it will choose the lowest<13:17:13.380> top<13:17:13.560> count<13:17:13.740> so<13:17:14.096> it<13:17:14.220> will<13:17:14.276> be<13:17:14.460> router<13:17:14.880> 1 13:17:15.050 --> 13:17:15.060 align:start position:0% lowest top count so it will be router 1 13:17:15.060 --> 13:17:18.370 align:start position:0% lowest top count so it will be router 1 to<13:17:15.596> router<13:17:16.020> 3.<13:17:16.916> even<13:17:17.400> though<13:17:17.580> it's 13:17:18.370 --> 13:17:18.380 align:start position:0% to router 3. even though it's 13:17:18.380 --> 13:17:22.070 align:start position:0% to router 3. even though it's 128k<13:17:19.380> the<13:17:19.800> link<13:17:20.040> there 13:17:22.070 --> 13:17:22.080 align:start position:0% 128k the link there 13:17:22.080 --> 13:17:25.246 align:start position:0% 128k the link there if<13:17:22.380> rspf<13:17:23.160> is<13:17:23.640> being<13:17:23.936> used 13:17:25.246 --> 13:17:25.256 align:start position:0% if rspf is being used 13:17:25.256 --> 13:17:27.710 align:start position:0% if rspf is being used um<13:17:25.380> then<13:17:25.560> it<13:17:25.800> will<13:17:25.916> choose<13:17:26.220> R2 13:17:27.710 --> 13:17:27.720 align:start position:0% um then it will choose R2 13:17:27.720 --> 13:17:29.746 align:start position:0% um then it will choose R2 that<13:17:28.380> might<13:17:28.560> not<13:17:28.680> be<13:17:28.860> correct<13:17:29.096> actually<13:17:29.276> if<13:17:29.580> I 13:17:29.746 --> 13:17:29.756 align:start position:0% that might not be correct actually if I 13:17:29.756 --> 13:17:31.606 align:start position:0% that might not be correct actually if I look<13:17:29.880> at<13:17:30.116> the<13:17:30.416> diagram 13:17:31.606 --> 13:17:31.616 align:start position:0% look at the diagram 13:17:31.616 --> 13:17:34.426 align:start position:0% look at the diagram you'd<13:17:32.400> have<13:17:32.580> to<13:17:32.700> add<13:17:32.880> up<13:17:33.116> the<13:17:33.720> um<13:17:33.720> speed<13:17:34.140> of<13:17:34.320> the 13:17:34.426 --> 13:17:34.436 align:start position:0% you'd have to add up the um speed of the 13:17:34.436 --> 13:17:36.530 align:start position:0% you'd have to add up the um speed of the links<13:17:34.680> but<13:17:34.860> the<13:17:35.040> speed<13:17:35.220> between<13:17:35.460> router<13:17:36.300> 2<13:17:36.416> and 13:17:36.530 --> 13:17:36.540 align:start position:0% links but the speed between router 2 and 13:17:36.540 --> 13:17:40.310 align:start position:0% links but the speed between router 2 and router<13:17:36.776> 3<13:17:36.960> is<13:17:37.080> being<13:17:37.256> put<13:17:37.436> as<13:17:37.700> 128k<13:17:38.700> so<13:17:40.020> um<13:17:40.080> that 13:17:40.310 --> 13:17:40.320 align:start position:0% router 3 is being put as 128k so um that 13:17:40.320 --> 13:17:41.810 align:start position:0% router 3 is being put as 128k so um that isn't<13:17:40.560> quite<13:17:40.680> correct<13:17:41.040> say<13:17:41.340> you've<13:17:41.520> got<13:17:41.640> a<13:17:41.700> one 13:17:41.810 --> 13:17:41.820 align:start position:0% isn't quite correct say you've got a one 13:17:41.820 --> 13:17:44.390 align:start position:0% isn't quite correct say you've got a one Meg<13:17:42.116> link<13:17:42.300> between<13:17:42.596> router<13:17:43.140> one<13:17:43.380> and<13:17:43.616> two<13:17:43.860> and 13:17:44.390 --> 13:17:44.400 align:start position:0% Meg link between router one and two and 13:17:44.400 --> 13:17:47.086 align:start position:0% Meg link between router one and two and then<13:17:44.520> two<13:17:44.756> and<13:17:45.000> three<13:17:45.180> then<13:17:45.900> ospf<13:17:46.680> should 13:17:47.086 --> 13:17:47.096 align:start position:0% then two and three then ospf should 13:17:47.096 --> 13:17:49.246 align:start position:0% then two and three then ospf should choose<13:17:47.936> the 13:17:49.246 --> 13:17:49.256 align:start position:0% choose the 13:17:49.256 --> 13:17:51.890 align:start position:0% choose the um<13:17:49.320> that<13:17:49.740> link<13:17:49.980> even<13:17:50.400> though<13:17:50.640> it's<13:17:50.756> more<13:17:50.936> hops 13:17:51.890 --> 13:17:51.900 align:start position:0% um that link even though it's more hops 13:17:51.900 --> 13:17:55.790 align:start position:0% um that link even though it's more hops because<13:17:52.320> it's<13:17:52.560> only<13:17:52.800> looking<13:17:53.040> at<13:17:53.276> the<13:17:53.460> costs 13:17:55.790 --> 13:17:55.800 align:start position:0% because it's only looking at the costs 13:17:55.800 --> 13:17:58.246 align:start position:0% because it's only looking at the costs so<13:17:56.276> Dynamic<13:17:56.756> router<13:17:57.180> protocol<13:17:57.480> also<13:17:57.840> allows<13:17:58.140> a 13:17:58.246 --> 13:17:58.256 align:start position:0% so Dynamic router protocol also allows a 13:17:58.256 --> 13:18:00.230 align:start position:0% so Dynamic router protocol also allows a router<13:17:58.560> to<13:17:58.740> reroute<13:17:59.340> around<13:17:59.520> a<13:17:59.756> fellow<13:18:00.060> link 13:18:00.230 --> 13:18:00.240 align:start position:0% router to reroute around a fellow link 13:18:00.240 --> 13:18:01.606 align:start position:0% router to reroute around a fellow link and<13:18:00.416> this<13:18:00.480> is<13:18:00.596> where<13:18:00.720> the<13:18:00.900> topology<13:18:01.256> table 13:18:01.606 --> 13:18:01.616 align:start position:0% and this is where the topology table 13:18:01.616 --> 13:18:04.730 align:start position:0% and this is where the topology table will<13:18:01.916> come<13:18:02.160> in<13:18:02.340> it<13:18:02.820> will<13:18:02.936> have<13:18:03.180> a<13:18:03.900> um<13:18:03.960> ability 13:18:04.730 --> 13:18:04.740 align:start position:0% will come in it will have a um ability 13:18:04.740 --> 13:18:07.490 align:start position:0% will come in it will have a um ability or<13:18:05.220> most<13:18:05.520> advanced<13:18:06.000> protocols<13:18:06.540> do<13:18:06.720> to<13:18:07.256> have 13:18:07.490 --> 13:18:07.500 align:start position:0% or most advanced protocols do to have 13:18:07.500 --> 13:18:09.290 align:start position:0% or most advanced protocols do to have some<13:18:07.740> backup<13:18:08.040> routes<13:18:08.400> in<13:18:08.520> the<13:18:08.640> topology<13:18:09.000> table 13:18:09.290 --> 13:18:09.300 align:start position:0% some backup routes in the topology table 13:18:09.300 --> 13:18:12.710 align:start position:0% some backup routes in the topology table that<13:18:09.540> will<13:18:09.720> quickly<13:18:10.080> take<13:18:10.680> over 13:18:12.710 --> 13:18:12.720 align:start position:0% that will quickly take over 13:18:12.720 --> 13:18:15.406 align:start position:0% that will quickly take over uh<13:18:13.256> physically<13:18:13.740> connected<13:18:14.160> networks<13:18:14.880> routers 13:18:15.406 --> 13:18:15.416 align:start position:0% uh physically connected networks routers 13:18:15.416 --> 13:18:17.690 align:start position:0% uh physically connected networks routers interfaces<13:18:15.960> physically<13:18:16.500> connected<13:18:17.340> to<13:18:17.520> a 13:18:17.690 --> 13:18:17.700 align:start position:0% interfaces physically connected to a 13:18:17.700 --> 13:18:19.606 align:start position:0% interfaces physically connected to a network<13:18:17.820> it<13:18:18.540> obviously<13:18:18.900> knows<13:18:19.140> how<13:18:19.256> to<13:18:19.380> reach 13:18:19.606 --> 13:18:19.616 align:start position:0% network it obviously knows how to reach 13:18:19.616 --> 13:18:21.170 align:start position:0% network it obviously knows how to reach that<13:18:19.800> Network 13:18:21.170 --> 13:18:21.180 align:start position:0% that Network 13:18:21.180 --> 13:18:23.330 align:start position:0% that Network since<13:18:21.660> r1's<13:18:22.380> interface<13:18:22.800> is<13:18:23.040> directly 13:18:23.330 --> 13:18:23.340 align:start position:0% since r1's interface is directly 13:18:23.340 --> 13:18:24.830 align:start position:0% since r1's interface is directly connected<13:18:23.640> to<13:18:23.820> these<13:18:24.116> networks<13:18:24.480> it<13:18:24.660> already 13:18:24.830 --> 13:18:24.840 align:start position:0% connected to these networks it already 13:18:24.840 --> 13:18:28.190 align:start position:0% connected to these networks it already knows<13:18:25.256> how<13:18:25.380> to<13:18:25.500> reach<13:18:25.860> them 13:18:28.190 --> 13:18:28.200 align:start position:0% 13:18:28.200 --> 13:18:30.530 align:start position:0% all<13:18:28.616> right<13:18:28.740> so<13:18:28.980> we've<13:18:29.220> covered<13:18:29.580> routing<13:18:30.180> just 13:18:30.530 --> 13:18:30.540 align:start position:0% all right so we've covered routing just 13:18:30.540 --> 13:18:33.230 align:start position:0% all right so we've covered routing just in<13:18:30.720> an<13:18:30.900> overview<13:18:31.256> the<13:18:31.680> routing<13:18:31.980> table 13:18:33.230 --> 13:18:33.240 align:start position:0% in an overview the routing table 13:18:33.240 --> 13:18:35.926 align:start position:0% in an overview the routing table static<13:18:33.900> routes<13:18:34.436> an<13:18:34.860> example<13:18:35.160> of<13:18:35.400> a<13:18:35.580> static 13:18:35.926 --> 13:18:35.936 align:start position:0% static routes an example of a static 13:18:35.936 --> 13:18:38.870 align:start position:0% static routes an example of a static route<13:18:36.436> autonomic<13:18:37.436> routing<13:18:37.916> protocols<13:18:38.580> as<13:18:38.756> an 13:18:38.870 --> 13:18:38.880 align:start position:0% route autonomic routing protocols as an 13:18:38.880 --> 13:18:41.630 align:start position:0% route autonomic routing protocols as an example<13:18:39.300> and<13:18:39.960> then<13:18:40.140> physically<13:18:40.640> connected 13:18:41.630 --> 13:18:41.640 align:start position:0% example and then physically connected 13:18:41.640 --> 13:18:43.246 align:start position:0% example and then physically connected Networks 13:18:43.246 --> 13:18:43.256 align:start position:0% Networks 13:18:43.256 --> 13:18:45.170 align:start position:0% Networks now<13:18:43.740> your<13:18:43.980> physically<13:18:44.276> connected<13:18:44.640> networks 13:18:45.170 --> 13:18:45.180 align:start position:0% now your physically connected networks 13:18:45.180 --> 13:18:47.870 align:start position:0% now your physically connected networks you<13:18:45.416> don't<13:18:45.776> have<13:18:46.020> to<13:18:46.380> advertise<13:18:47.096> but 13:18:47.870 --> 13:18:47.880 align:start position:0% you don't have to advertise but 13:18:47.880 --> 13:18:49.310 align:start position:0% you don't have to advertise but obviously<13:18:48.180> if<13:18:48.360> you<13:18:48.480> want<13:18:48.660> traffic<13:18:48.840> to<13:18:49.080> be<13:18:49.200> able 13:18:49.310 --> 13:18:49.320 align:start position:0% obviously if you want traffic to be able 13:18:49.320 --> 13:18:50.630 align:start position:0% obviously if you want traffic to be able to<13:18:49.436> reach<13:18:49.616> that<13:18:49.800> Network<13:18:50.040> then<13:18:50.400> you're<13:18:50.580> going 13:18:50.630 --> 13:18:50.640 align:start position:0% to reach that Network then you're going 13:18:50.640 --> 13:18:53.690 align:start position:0% to reach that Network then you're going to<13:18:50.756> need<13:18:50.880> to<13:18:51.000> add<13:18:51.180> a<13:18:51.360> dynamic<13:18:51.840> or<13:18:52.380> static<13:18:52.800> route 13:18:53.690 --> 13:18:53.700 align:start position:0% to need to add a dynamic or static route 13:18:53.700 --> 13:18:55.010 align:start position:0% to need to add a dynamic or static route but<13:18:54.000> that's<13:18:54.116> all<13:18:54.300> for<13:18:54.480> now<13:18:54.596> thanks<13:18:54.900> for 13:18:55.010 --> 13:18:55.020 align:start position:0% but that's all for now thanks for 13:18:55.020 --> 13:19:01.590 align:start position:0% but that's all for now thanks for watching 13:19:01.590 --> 13:19:01.600 align:start position:0% 13:19:01.600 --> 13:19:21.730 align:start position:0% [Music] 13:19:21.730 --> 13:19:21.740 align:start position:0% 13:19:21.740 --> 13:19:25.730 align:start position:0% local<13:19:22.740> area<13:19:23.096> networks<13:19:23.900> Dynamic<13:19:24.900> routing<13:19:25.380> and 13:19:25.730 --> 13:19:25.740 align:start position:0% local area networks Dynamic routing and 13:19:25.740 --> 13:19:26.990 align:start position:0% local area networks Dynamic routing and protocols 13:19:26.990 --> 13:19:27.000 align:start position:0% protocols 13:19:27.000 --> 13:19:29.150 align:start position:0% protocols so<13:19:27.416> in<13:19:27.596> the<13:19:27.776> previous<13:19:27.840> module<13:19:28.500> we<13:19:28.800> discussed 13:19:29.150 --> 13:19:29.160 align:start position:0% so in the previous module we discussed 13:19:29.160 --> 13:19:31.130 align:start position:0% so in the previous module we discussed what<13:19:29.340> a<13:19:29.520> router<13:19:29.820> is<13:19:30.000> and<13:19:30.416> how<13:19:30.596> it<13:19:30.720> functions 13:19:31.130 --> 13:19:31.140 align:start position:0% what a router is and how it functions 13:19:31.140 --> 13:19:34.550 align:start position:0% what a router is and how it functions and<13:19:31.616> we<13:19:31.800> discussed<13:19:32.400> static<13:19:33.300> routing<13:19:33.776> which<13:19:34.436> is 13:19:34.550 --> 13:19:34.560 align:start position:0% and we discussed static routing which is 13:19:34.560 --> 13:19:36.890 align:start position:0% and we discussed static routing which is the<13:19:34.800> process<13:19:35.096> of<13:19:35.640> manually<13:19:36.060> creating<13:19:36.596> a 13:19:36.890 --> 13:19:36.900 align:start position:0% the process of manually creating a 13:19:36.900 --> 13:19:39.710 align:start position:0% the process of manually creating a routing<13:19:37.200> table<13:19:37.460> so<13:19:38.460> in<13:19:38.700> this<13:19:38.880> module<13:19:39.240> we're 13:19:39.710 --> 13:19:39.720 align:start position:0% routing table so in this module we're 13:19:39.720 --> 13:19:42.170 align:start position:0% routing table so in this module we're going<13:19:39.900> to<13:19:39.960> Define<13:19:40.140> in<13:19:40.860> more<13:19:41.040> depth 13:19:42.170 --> 13:19:42.180 align:start position:0% going to Define in more depth 13:19:42.180 --> 13:19:45.406 align:start position:0% going to Define in more depth Dynamic<13:19:43.080> routing<13:19:43.680> which<13:19:44.400> is<13:19:44.700> what<13:19:44.936> allows 13:19:45.406 --> 13:19:45.416 align:start position:0% Dynamic routing which is what allows 13:19:45.416 --> 13:19:49.070 align:start position:0% Dynamic routing which is what allows routing<13:19:46.320> just<13:19:47.160> like<13:19:47.400> with<13:19:48.000> DHCP<13:19:48.660> and<13:19:48.776> IP 13:19:49.070 --> 13:19:49.080 align:start position:0% routing just like with DHCP and IP 13:19:49.080 --> 13:19:51.710 align:start position:0% routing just like with DHCP and IP addresses<13:19:49.560> to<13:19:49.980> be<13:19:50.160> dynamically<13:19:50.936> up<13:19:51.300> kept 13:19:51.710 --> 13:19:51.720 align:start position:0% addresses to be dynamically up kept 13:19:51.720 --> 13:19:54.470 align:start position:0% addresses to be dynamically up kept which<13:19:52.140> is<13:19:52.320> going<13:19:52.436> to<13:19:52.560> allow<13:19:52.916> for 13:19:54.470 --> 13:19:54.480 align:start position:0% which is going to allow for 13:19:54.480 --> 13:19:57.890 align:start position:0% which is going to allow for a<13:19:55.080> much<13:19:55.320> more<13:19:55.560> flexible<13:19:56.160> Network<13:19:57.060> now 13:19:57.890 --> 13:19:57.900 align:start position:0% a much more flexible Network now 13:19:57.900 --> 13:19:59.870 align:start position:0% a much more flexible Network now although<13:19:58.436> this<13:19:58.860> title<13:19:59.276> of<13:19:59.400> this<13:19:59.580> entire 13:19:59.870 --> 13:19:59.880 align:start position:0% although this title of this entire 13:19:59.880 --> 13:20:01.790 align:start position:0% although this title of this entire lesson<13:20:00.300> is<13:20:00.416> local<13:20:00.660> area<13:20:00.900> networks<13:20:01.436> in<13:20:01.616> some 13:20:01.790 --> 13:20:01.800 align:start position:0% lesson is local area networks in some 13:20:01.800 --> 13:20:03.830 align:start position:0% lesson is local area networks in some ways<13:20:02.096> we<13:20:02.400> could<13:20:02.520> extend<13:20:02.936> this<13:20:03.180> to<13:20:03.360> wide<13:20:03.660> area 13:20:03.830 --> 13:20:03.840 align:start position:0% ways we could extend this to wide area 13:20:03.840 --> 13:20:05.870 align:start position:0% ways we could extend this to wide area Networks<13:20:04.560> so<13:20:05.096> we're<13:20:05.276> going<13:20:05.400> to<13:20:05.520> talk<13:20:05.700> about 13:20:05.870 --> 13:20:05.880 align:start position:0% Networks so we're going to talk about 13:20:05.880 --> 13:20:07.850 align:start position:0% Networks so we're going to talk about Dynamic<13:20:06.540> routing<13:20:06.960> and<13:20:07.436> then<13:20:07.500> we're<13:20:07.680> going<13:20:07.800> to 13:20:07.850 --> 13:20:07.860 align:start position:0% Dynamic routing and then we're going to 13:20:07.860 --> 13:20:10.070 align:start position:0% Dynamic routing and then we're going to talk<13:20:08.096> about<13:20:08.276> two<13:20:09.060> different<13:20:09.300> types<13:20:09.900> of 13:20:10.070 --> 13:20:10.080 align:start position:0% talk about two different types of 13:20:10.080 --> 13:20:13.130 align:start position:0% talk about two different types of dynamic<13:20:10.500> routing<13:20:10.916> these<13:20:11.756> are<13:20:11.936> distant<13:20:12.660> vector 13:20:13.130 --> 13:20:13.140 align:start position:0% dynamic routing these are distant vector 13:20:13.140 --> 13:20:17.266 align:start position:0% dynamic routing these are distant vector and<13:20:13.860> Link<13:20:14.160> State<13:20:14.580> now<13:20:15.416> we<13:20:15.960> sort<13:20:16.256> of<13:20:16.380> alluded<13:20:17.096> to 13:20:17.266 --> 13:20:17.276 align:start position:0% and Link State now we sort of alluded to 13:20:17.276 --> 13:20:19.246 align:start position:0% and Link State now we sort of alluded to the<13:20:17.640> difference<13:20:17.820> between<13:20:18.240> these<13:20:18.660> in<13:20:19.080> the 13:20:19.246 --> 13:20:19.256 align:start position:0% the difference between these in the 13:20:19.256 --> 13:20:21.050 align:start position:0% the difference between these in the previous<13:20:19.380> module<13:20:20.040> when<13:20:20.276> I<13:20:20.460> was<13:20:20.520> discussing 13:20:21.050 --> 13:20:21.060 align:start position:0% previous module when I was discussing 13:20:21.060 --> 13:20:24.470 align:start position:0% previous module when I was discussing Hops<13:20:21.900> and<13:20:22.616> simply<13:20:23.040> relying<13:20:23.756> on<13:20:24.000> the<13:20:24.116> number<13:20:24.300> of 13:20:24.470 --> 13:20:24.480 align:start position:0% Hops and simply relying on the number of 13:20:24.480 --> 13:20:26.210 align:start position:0% Hops and simply relying on the number of hops<13:20:24.900> to<13:20:25.080> get<13:20:25.200> from<13:20:25.380> one<13:20:25.560> place<13:20:25.740> to<13:20:25.980> the<13:20:26.096> other 13:20:26.210 --> 13:20:26.220 align:start position:0% hops to get from one place to the other 13:20:26.220 --> 13:20:30.350 align:start position:0% hops to get from one place to the other versus<13:20:27.116> looking<13:20:27.900> at<13:20:28.256> for<13:20:28.680> instance<13:20:28.980> if<13:20:29.820> one 13:20:30.350 --> 13:20:30.360 align:start position:0% versus looking at for instance if one 13:20:30.360 --> 13:20:33.710 align:start position:0% versus looking at for instance if one link<13:20:30.680> was<13:20:31.680> a<13:20:31.980> dial-up<13:20:32.340> or<13:20:32.700> Broadband<13:20:33.240> or<13:20:33.596> if 13:20:33.710 --> 13:20:33.720 align:start position:0% link was a dial-up or Broadband or if 13:20:33.720 --> 13:20:36.106 align:start position:0% link was a dial-up or Broadband or if the<13:20:33.840> link<13:20:33.960> was<13:20:34.200> even<13:20:34.436> shut<13:20:34.860> down<13:20:35.096> completely 13:20:36.106 --> 13:20:36.116 align:start position:0% the link was even shut down completely 13:20:36.116 --> 13:20:39.650 align:start position:0% the link was even shut down completely and<13:20:36.720> so<13:20:36.960> there<13:20:37.616> are<13:20:37.860> two<13:20:38.460> different<13:20:38.640> types<13:20:39.416> of 13:20:39.650 --> 13:20:39.660 align:start position:0% and so there are two different types of 13:20:39.660 --> 13:20:41.150 align:start position:0% and so there are two different types of protocol<13:20:40.080> sets<13:20:40.560> we're<13:20:40.680> going<13:20:40.800> to<13:20:40.860> look<13:20:41.040> at 13:20:41.150 --> 13:20:41.160 align:start position:0% protocol sets we're going to look at 13:20:41.160 --> 13:20:44.030 align:start position:0% protocol sets we're going to look at there<13:20:41.880> are<13:20:42.000> distant<13:20:42.360> Vector<13:20:42.900> protocols<13:20:43.560> these 13:20:44.030 --> 13:20:44.040 align:start position:0% there are distant Vector protocols these 13:20:44.040 --> 13:20:46.070 align:start position:0% there are distant Vector protocols these are<13:20:44.096> the<13:20:44.276> protocols<13:20:44.820> that<13:20:45.116> allow<13:20:45.540> distant 13:20:46.070 --> 13:20:46.080 align:start position:0% are the protocols that allow distant 13:20:46.080 --> 13:20:48.350 align:start position:0% are the protocols that allow distant Vector<13:20:46.560> routing<13:20:46.980> and<13:20:47.580> then<13:20:47.700> there<13:20:47.936> are<13:20:48.060> link 13:20:48.350 --> 13:20:48.360 align:start position:0% Vector routing and then there are link 13:20:48.360 --> 13:20:50.690 align:start position:0% Vector routing and then there are link State<13:20:48.720> protocols<13:20:49.436> you'll<13:20:50.160> see<13:20:50.276> them<13:20:50.400> listed 13:20:50.690 --> 13:20:50.700 align:start position:0% State protocols you'll see them listed 13:20:50.700 --> 13:20:52.246 align:start position:0% State protocols you'll see them listed here<13:20:50.880> and<13:20:51.000> we'll<13:20:51.180> talk<13:20:51.360> about<13:20:51.540> each<13:20:51.900> one<13:20:52.020> in 13:20:52.246 --> 13:20:52.256 align:start position:0% here and we'll talk about each one in 13:20:52.256 --> 13:20:54.586 align:start position:0% here and we'll talk about each one in depth<13:20:52.616> and<13:20:53.040> if<13:20:53.340> the<13:20:53.756> acronyms<13:20:54.416> are<13:20:54.480> already 13:20:54.586 --> 13:20:54.596 align:start position:0% depth and if the acronyms are already 13:20:54.596 --> 13:20:56.390 align:start position:0% depth and if the acronyms are already starting<13:20:54.840> to<13:20:55.080> freak<13:20:55.380> you<13:20:55.500> out<13:20:55.680> don't<13:20:56.160> worry 13:20:56.390 --> 13:20:56.400 align:start position:0% starting to freak you out don't worry 13:20:56.400 --> 13:20:58.850 align:start position:0% starting to freak you out don't worry about<13:20:56.580> it<13:20:56.820> what<13:20:57.416> we<13:20:57.540> want<13:20:57.660> to<13:20:57.776> do<13:20:57.960> is<13:20:58.320> just<13:20:58.616> know 13:20:58.850 --> 13:20:58.860 align:start position:0% about it what we want to do is just know 13:20:58.860 --> 13:21:00.890 align:start position:0% about it what we want to do is just know which<13:20:59.160> ones<13:20:59.400> are<13:20:59.580> distance<13:20:59.756> vector<13:21:00.300> and<13:21:00.776> which 13:21:00.890 --> 13:21:00.900 align:start position:0% which ones are distance vector and which 13:21:00.900 --> 13:21:03.710 align:start position:0% which ones are distance vector and which ones<13:21:01.320> are<13:21:01.560> link<13:21:01.800> state<13:21:02.160> so<13:21:03.000> as<13:21:03.240> you<13:21:03.416> can<13:21:03.540> tell 13:21:03.710 --> 13:21:03.720 align:start position:0% ones are link state so as you can tell 13:21:03.720 --> 13:21:05.810 align:start position:0% ones are link state so as you can tell if<13:21:04.140> you<13:21:04.256> can<13:21:04.380> remember<13:21:04.560> that<13:21:04.860> these<13:21:05.220> two<13:21:05.460> are 13:21:05.810 --> 13:21:05.820 align:start position:0% if you can remember that these two are 13:21:05.820 --> 13:21:07.426 align:start position:0% if you can remember that these two are link<13:21:06.000> State<13:21:06.360> you'll<13:21:06.840> be<13:21:06.960> fine<13:21:07.080> for<13:21:07.320> the 13:21:07.426 --> 13:21:07.436 align:start position:0% link State you'll be fine for the 13:21:07.436 --> 13:21:08.870 align:start position:0% link State you'll be fine for the network<13:21:07.500> plus<13:21:07.800> exam<13:21:08.220> which<13:21:08.520> again<13:21:08.640> is 13:21:08.870 --> 13:21:08.880 align:start position:0% network plus exam which again is 13:21:08.880 --> 13:21:10.310 align:start position:0% network plus exam which again is multiple<13:21:09.240> choice<13:21:09.480> and<13:21:09.720> will<13:21:09.900> ask<13:21:10.020> you<13:21:10.200> to 13:21:10.310 --> 13:21:10.320 align:start position:0% multiple choice and will ask you to 13:21:10.320 --> 13:21:12.890 align:start position:0% multiple choice and will ask you to recognize<13:21:10.740> it<13:21:10.916> but<13:21:11.340> we'll<13:21:11.520> go<13:21:11.820> over<13:21:12.240> them<13:21:12.480> in<13:21:12.776> a 13:21:12.890 --> 13:21:12.900 align:start position:0% recognize it but we'll go over them in a 13:21:12.900 --> 13:21:14.510 align:start position:0% recognize it but we'll go over them in a little<13:21:12.960> more<13:21:13.140> depth<13:21:13.500> than<13:21:13.680> that 13:21:14.510 --> 13:21:14.520 align:start position:0% little more depth than that 13:21:14.520 --> 13:21:18.170 align:start position:0% little more depth than that so<13:21:15.256> Dynamic<13:21:16.256> routing<13:21:16.680> uses<13:21:17.460> a<13:21:17.756> series<13:21:17.880> of 13:21:18.170 --> 13:21:18.180 align:start position:0% so Dynamic routing uses a series of 13:21:18.180 --> 13:21:20.210 align:start position:0% so Dynamic routing uses a series of protocols<13:21:18.960> to<13:21:19.200> establish<13:21:19.560> the<13:21:19.740> routing<13:21:20.040> table 13:21:20.210 --> 13:21:20.220 align:start position:0% protocols to establish the routing table 13:21:20.220 --> 13:21:24.050 align:start position:0% protocols to establish the routing table as<13:21:20.880> opposed<13:21:21.300> to<13:21:21.360> the<13:21:22.140> route<13:21:22.320> add<13:21:22.680> command<13:21:23.220> all 13:21:24.050 --> 13:21:24.060 align:start position:0% as opposed to the route add command all 13:21:24.060 --> 13:21:26.266 align:start position:0% as opposed to the route add command all of<13:21:24.180> the<13:21:24.416> routers<13:21:24.840> pass<13:21:25.256> information<13:21:25.616> about 13:21:26.266 --> 13:21:26.276 align:start position:0% of the routers pass information about 13:21:26.276 --> 13:21:28.906 align:start position:0% of the routers pass information about themselves<13:21:26.880> along<13:21:27.480> to<13:21:27.900> the<13:21:28.140> other<13:21:28.320> routers 13:21:28.906 --> 13:21:28.916 align:start position:0% themselves along to the other routers 13:21:28.916 --> 13:21:31.970 align:start position:0% themselves along to the other routers and<13:21:29.880> they<13:21:30.240> use<13:21:30.480> this<13:21:30.840> information<13:21:31.080> to 13:21:31.970 --> 13:21:31.980 align:start position:0% and they use this information to 13:21:31.980 --> 13:21:34.490 align:start position:0% and they use this information to establish<13:21:32.400> a<13:21:32.880> routing<13:21:33.240> table<13:21:33.416> based<13:21:34.380> on 13:21:34.490 --> 13:21:34.500 align:start position:0% establish a routing table based on 13:21:34.500 --> 13:21:37.426 align:start position:0% establish a routing table based on certain<13:21:34.800> specifics<13:21:35.580> of<13:21:36.000> the<13:21:36.180> other<13:21:36.360> routers 13:21:37.426 --> 13:21:37.436 align:start position:0% certain specifics of the other routers 13:21:37.436 --> 13:21:39.290 align:start position:0% certain specifics of the other routers now<13:21:37.800> there<13:21:38.096> are<13:21:38.220> two<13:21:38.520> different<13:21:38.700> types<13:21:39.180> of 13:21:39.290 --> 13:21:39.300 align:start position:0% now there are two different types of 13:21:39.300 --> 13:21:41.030 align:start position:0% now there are two different types of protocols<13:21:39.900> that<13:21:40.080> are<13:21:40.200> used<13:21:40.380> like<13:21:40.680> I<13:21:40.860> just 13:21:41.030 --> 13:21:41.040 align:start position:0% protocols that are used like I just 13:21:41.040 --> 13:21:43.730 align:start position:0% protocols that are used like I just mentioned<13:21:41.520> there<13:21:42.300> are<13:21:42.480> the<13:21:42.720> distance<13:21:43.020> Vector 13:21:43.730 --> 13:21:43.740 align:start position:0% mentioned there are the distance Vector 13:21:43.740 --> 13:21:48.050 align:start position:0% mentioned there are the distance Vector protocols<13:21:44.400> which<13:21:44.880> in<13:21:45.180> some<13:21:45.300> ways<13:21:45.660> are<13:21:46.320> older 13:21:48.050 --> 13:21:48.060 align:start position:0% protocols which in some ways are older 13:21:48.060 --> 13:21:50.746 align:start position:0% protocols which in some ways are older and<13:21:48.596> the<13:21:48.840> link<13:21:49.020> State<13:21:49.256> protocols 13:21:50.746 --> 13:21:50.756 align:start position:0% and the link State protocols 13:21:50.756 --> 13:21:53.926 align:start position:0% and the link State protocols which<13:21:51.240> are<13:21:51.416> newer<13:21:52.200> the<13:21:52.740> reason<13:21:52.916> being<13:21:53.640> that 13:21:53.926 --> 13:21:53.936 align:start position:0% which are newer the reason being that 13:21:53.936 --> 13:21:55.606 align:start position:0% which are newer the reason being that distance<13:21:54.180> vector 13:21:55.606 --> 13:21:55.616 align:start position:0% distance vector 13:21:55.616 --> 13:21:58.970 align:start position:0% distance vector looks<13:21:56.340> just<13:21:56.580> at<13:21:56.880> the<13:21:57.540> number<13:21:57.720> of<13:21:58.080> miles<13:21:58.560> we 13:21:58.970 --> 13:21:58.980 align:start position:0% looks just at the number of miles we 13:21:58.980 --> 13:22:02.330 align:start position:0% looks just at the number of miles we have<13:21:59.096> to<13:21:59.276> travel<13:21:59.660> and<13:22:00.660> the<13:22:00.840> link<13:22:01.020> state 13:22:02.330 --> 13:22:02.340 align:start position:0% have to travel and the link state 13:22:02.340 --> 13:22:06.106 align:start position:0% have to travel and the link state also<13:22:03.000> looks<13:22:03.240> at<13:22:03.360> the<13:22:04.320> traffic<13:22:04.580> so<13:22:05.580> it<13:22:05.820> can<13:22:05.936> tell 13:22:06.106 --> 13:22:06.116 align:start position:0% also looks at the traffic so it can tell 13:22:06.116 --> 13:22:08.990 align:start position:0% also looks at the traffic so it can tell us<13:22:06.360> if<13:22:07.020> although<13:22:07.380> we'll<13:22:07.616> have<13:22:07.800> to<13:22:07.916> go<13:22:08.220> further 13:22:08.990 --> 13:22:09.000 align:start position:0% us if although we'll have to go further 13:22:09.000 --> 13:22:11.746 align:start position:0% us if although we'll have to go further miles<13:22:09.240> it's<13:22:10.140> going<13:22:10.320> to<13:22:10.500> be<13:22:10.616> quicker<13:22:11.220> based<13:22:11.700> on 13:22:11.746 --> 13:22:11.756 align:start position:0% miles it's going to be quicker based on 13:22:11.756 --> 13:22:14.870 align:start position:0% miles it's going to be quicker based on traffic<13:22:12.060> just<13:22:12.480> like<13:22:12.660> our<13:22:12.840> GPS<13:22:13.080> system 13:22:14.870 --> 13:22:14.880 align:start position:0% traffic just like our GPS system 13:22:14.880 --> 13:22:16.130 align:start position:0% traffic just like our GPS system so 13:22:16.130 --> 13:22:16.140 align:start position:0% so 13:22:16.140 --> 13:22:18.350 align:start position:0% so let's<13:22:16.680> talk<13:22:16.860> about<13:22:16.980> distance<13:22:17.460> Vector<13:22:18.060> first 13:22:18.350 --> 13:22:18.360 align:start position:0% let's talk about distance Vector first 13:22:18.360 --> 13:22:21.290 align:start position:0% let's talk about distance Vector first in<13:22:19.080> distance<13:22:19.320> Vector<13:22:20.096> routing<13:22:20.580> the<13:22:21.000> routers 13:22:21.290 --> 13:22:21.300 align:start position:0% in distance Vector routing the routers 13:22:21.300 --> 13:22:23.630 align:start position:0% in distance Vector routing the routers on<13:22:21.480> the<13:22:21.596> network<13:22:21.720> are<13:22:22.140> only<13:22:22.436> aware<13:22:22.860> of<13:22:23.460> the 13:22:23.630 --> 13:22:23.640 align:start position:0% on the network are only aware of the 13:22:23.640 --> 13:22:25.790 align:start position:0% on the network are only aware of the routers<13:22:24.000> that<13:22:24.180> they<13:22:24.360> are<13:22:24.596> directly<13:22:25.140> connected 13:22:25.790 --> 13:22:25.800 align:start position:0% routers that they are directly connected 13:22:25.800 --> 13:22:28.906 align:start position:0% routers that they are directly connected to<13:22:26.000> so<13:22:27.000> if<13:22:27.596> this<13:22:27.776> is<13:22:27.900> one<13:22:28.080> router<13:22:28.500> let's<13:22:28.740> call 13:22:28.906 --> 13:22:28.916 align:start position:0% to so if this is one router let's call 13:22:28.916 --> 13:22:31.426 align:start position:0% to so if this is one router let's call this<13:22:29.040> router<13:22:29.460> one 13:22:31.426 --> 13:22:31.436 align:start position:0% this router one 13:22:31.436 --> 13:22:34.190 align:start position:0% this router one and<13:22:31.916> there's<13:22:32.040> a<13:22:32.220> router<13:22:32.580> two 13:22:34.190 --> 13:22:34.200 align:start position:0% and there's a router two 13:22:34.200 --> 13:22:37.670 align:start position:0% and there's a router two a<13:22:34.680> router<13:22:35.160> three 13:22:37.670 --> 13:22:37.680 align:start position:0% 13:22:37.680 --> 13:22:42.406 align:start position:0% and<13:22:38.220> a<13:22:38.460> router<13:22:38.820> four<13:22:39.080> router<13:22:40.080> 1<13:22:40.140> is<13:22:40.436> only<13:22:40.560> aware 13:22:42.406 --> 13:22:42.416 align:start position:0% and a router four router 1 is only aware 13:22:42.416 --> 13:22:45.406 align:start position:0% and a router four router 1 is only aware of<13:22:42.900> routers<13:22:43.256> two<13:22:43.500> and<13:22:44.460> three<13:22:44.640> so<13:22:45.116> these 13:22:45.406 --> 13:22:45.416 align:start position:0% of routers two and three so these 13:22:45.416 --> 13:22:47.030 align:start position:0% of routers two and three so these routers<13:22:45.776> don't<13:22:46.020> know<13:22:46.140> anything<13:22:46.320> about<13:22:46.680> the 13:22:47.030 --> 13:22:47.040 align:start position:0% routers don't know anything about the 13:22:47.040 --> 13:22:48.406 align:start position:0% routers don't know anything about the rest<13:22:47.160> of<13:22:47.276> the<13:22:47.400> routers<13:22:47.756> on<13:22:48.116> the<13:22:48.240> network 13:22:48.406 --> 13:22:48.416 align:start position:0% rest of the routers on the network 13:22:48.416 --> 13:22:50.450 align:start position:0% rest of the routers on the network unless<13:22:49.140> of<13:22:49.320> course<13:22:49.436> they're<13:22:49.680> directly<13:22:50.040> linked 13:22:50.450 --> 13:22:50.460 align:start position:0% unless of course they're directly linked 13:22:50.460 --> 13:22:52.370 align:start position:0% unless of course they're directly linked now<13:22:51.116> they<13:22:51.360> can<13:22:51.480> share<13:22:51.776> route<13:22:52.080> information 13:22:52.370 --> 13:22:52.380 align:start position:0% now they can share route information 13:22:52.380 --> 13:22:54.950 align:start position:0% now they can share route information with<13:22:53.096> these<13:22:53.640> directly<13:22:54.060> connected<13:22:54.480> routers 13:22:54.950 --> 13:22:54.960 align:start position:0% with these directly connected routers 13:22:54.960 --> 13:22:57.830 align:start position:0% with these directly connected routers but<13:22:55.800> the<13:22:56.096> flow<13:22:56.400> of<13:22:56.520> communication<13:22:57.060> is<13:22:57.416> limited 13:22:57.830 --> 13:22:57.840 align:start position:0% but the flow of communication is limited 13:22:57.840 --> 13:23:01.246 align:start position:0% but the flow of communication is limited as<13:22:57.960> a<13:22:58.140> result<13:22:58.276> the<13:22:59.276> spaces<13:22:59.756> between<13:23:00.256> distance 13:23:01.246 --> 13:23:01.256 align:start position:0% as a result the spaces between distance 13:23:01.256 --> 13:23:04.606 align:start position:0% as a result the spaces between distance Vector<13:23:01.980> routers<13:23:02.400> are<13:23:03.180> known<13:23:03.416> as<13:23:03.596> we<13:23:04.436> just 13:23:04.606 --> 13:23:04.616 align:start position:0% Vector routers are known as we just 13:23:04.616 --> 13:23:06.290 align:start position:0% Vector routers are known as we just talked<13:23:04.916> about<13:23:04.980> this 13:23:06.290 --> 13:23:06.300 align:start position:0% talked about this 13:23:06.300 --> 13:23:09.766 align:start position:0% talked about this hops<13:23:07.256> now<13:23:07.980> each<13:23:08.276> router<13:23:08.700> along<13:23:08.880> these<13:23:09.360> paths 13:23:09.766 --> 13:23:09.776 align:start position:0% hops now each router along these paths 13:23:09.776 --> 13:23:12.830 align:start position:0% hops now each router along these paths represent<13:23:10.436> a<13:23:10.800> hop<13:23:10.980> for<13:23:11.756> example<13:23:12.060> a<13:23:12.720> network 13:23:12.830 --> 13:23:12.840 align:start position:0% represent a hop for example a network 13:23:12.840 --> 13:23:16.130 align:start position:0% represent a hop for example a network with<13:23:13.256> a<13:23:13.560> five<13:23:13.980> distance<13:23:14.276> Vector<13:23:14.936> routers<13:23:15.360> has 13:23:16.130 --> 13:23:16.140 align:start position:0% with a five distance Vector routers has 13:23:16.140 --> 13:23:18.950 align:start position:0% with a five distance Vector routers has four<13:23:16.436> hops<13:23:16.916> from<13:23:17.340> the<13:23:17.520> first<13:23:17.640> to<13:23:17.820> last<13:23:18.060> router 13:23:18.950 --> 13:23:18.960 align:start position:0% four hops from the first to last router 13:23:18.960 --> 13:23:23.390 align:start position:0% four hops from the first to last router if<13:23:19.256> we<13:23:19.380> have<13:23:19.560> one<13:23:19.860> two<13:23:20.900> three<13:23:21.900> four<13:23:22.740> five 13:23:23.390 --> 13:23:23.400 align:start position:0% if we have one two three four five 13:23:23.400 --> 13:23:24.530 align:start position:0% if we have one two three four five routers 13:23:24.530 --> 13:23:24.540 align:start position:0% routers 13:23:24.540 --> 13:23:26.990 align:start position:0% routers there's<13:23:25.020> one<13:23:25.436> two<13:23:25.980> three 13:23:26.990 --> 13:23:27.000 align:start position:0% there's one two three 13:23:27.000 --> 13:23:28.490 align:start position:0% there's one two three four<13:23:27.416> hops 13:23:28.490 --> 13:23:28.500 align:start position:0% four hops 13:23:28.500 --> 13:23:30.830 align:start position:0% four hops it's<13:23:28.916> also<13:23:29.220> important<13:23:29.640> to<13:23:29.936> notice<13:23:30.240> that 13:23:30.830 --> 13:23:30.840 align:start position:0% it's also important to notice that 13:23:30.840 --> 13:23:33.950 align:start position:0% it's also important to notice that convergence<13:23:31.560> that's<13:23:32.160> the<13:23:32.520> updating<13:23:32.936> of<13:23:33.720> all 13:23:33.950 --> 13:23:33.960 align:start position:0% convergence that's the updating of all 13:23:33.960 --> 13:23:38.810 align:start position:0% convergence that's the updating of all of<13:23:34.080> the<13:23:34.256> information<13:23:34.436> to<13:23:34.980> the<13:23:35.160> router<13:23:35.460> table 13:23:38.810 --> 13:23:38.820 align:start position:0% 13:23:38.820 --> 13:23:41.150 align:start position:0% is<13:23:39.360> going<13:23:39.540> to<13:23:39.720> take<13:23:39.960> longer<13:23:40.436> with<13:23:40.680> this<13:23:40.860> set<13:23:41.040> of 13:23:41.150 --> 13:23:41.160 align:start position:0% is going to take longer with this set of 13:23:41.160 --> 13:23:42.890 align:start position:0% is going to take longer with this set of protocols<13:23:41.756> than<13:23:42.060> with<13:23:42.240> link<13:23:42.416> state<13:23:42.660> which 13:23:42.890 --> 13:23:42.900 align:start position:0% protocols than with link state which 13:23:42.900 --> 13:23:44.390 align:start position:0% protocols than with link state which we'll<13:23:43.020> look<13:23:43.140> at<13:23:43.256> in<13:23:43.380> a<13:23:43.560> second<13:23:43.616> this<13:23:44.340> is 13:23:44.390 --> 13:23:44.400 align:start position:0% we'll look at in a second this is 13:23:44.400 --> 13:23:46.310 align:start position:0% we'll look at in a second this is because<13:23:44.580> the<13:23:44.880> routers<13:23:45.240> don't<13:23:45.540> have<13:23:45.900> the 13:23:46.310 --> 13:23:46.320 align:start position:0% because the routers don't have the 13:23:46.320 --> 13:23:48.406 align:start position:0% because the routers don't have the knowledge<13:23:46.680> of<13:23:46.980> the<13:23:47.096> entire<13:23:47.400> network<13:23:47.700> so<13:23:48.300> it 13:23:48.406 --> 13:23:48.416 align:start position:0% knowledge of the entire network so it 13:23:48.416 --> 13:23:50.810 align:start position:0% knowledge of the entire network so it takes<13:23:48.596> longer<13:23:48.960> for<13:23:49.140> them<13:23:49.256> to<13:23:49.500> become<13:23:49.800> aware<13:23:50.340> of 13:23:50.810 --> 13:23:50.820 align:start position:0% takes longer for them to become aware of 13:23:50.820 --> 13:23:52.790 align:start position:0% takes longer for them to become aware of a<13:23:51.000> change<13:23:51.300> in<13:23:51.596> the<13:23:51.720> network 13:23:52.790 --> 13:23:52.800 align:start position:0% a change in the network 13:23:52.800 --> 13:23:55.606 align:start position:0% a change in the network so<13:23:53.276> there<13:23:53.580> are<13:23:53.756> four<13:23:54.060> main<13:23:54.596> distance<13:23:55.020> Vector 13:23:55.606 --> 13:23:55.616 align:start position:0% so there are four main distance Vector 13:23:55.616 --> 13:23:57.650 align:start position:0% so there are four main distance Vector protocols<13:23:56.096> that<13:23:56.220> are<13:23:56.340> still<13:23:56.460> in<13:23:56.580> use<13:23:56.756> today 13:23:57.650 --> 13:23:57.660 align:start position:0% protocols that are still in use today 13:23:57.660 --> 13:24:00.470 align:start position:0% protocols that are still in use today the<13:23:58.020> first<13:23:58.140> one<13:23:58.380> is<13:23:59.096> called<13:23:59.400> the<13:24:00.060> routing 13:24:00.470 --> 13:24:00.480 align:start position:0% the first one is called the routing 13:24:00.480 --> 13:24:03.230 align:start position:0% the first one is called the routing information<13:24:00.776> protocol<13:24:01.560> or<13:24:02.276> rip 13:24:03.230 --> 13:24:03.240 align:start position:0% information protocol or rip 13:24:03.240 --> 13:24:06.670 align:start position:0% information protocol or rip routing<13:24:03.900> information<13:24:04.080> protocol<13:24:04.820> version<13:24:05.820> 2 13:24:06.670 --> 13:24:06.680 align:start position:0% routing information protocol version 2 13:24:06.680 --> 13:24:09.950 align:start position:0% routing information protocol version 2 there's<13:24:07.680> the<13:24:08.096> Border<13:24:08.520> Gateway<13:24:09.116> protocol<13:24:09.596> or 13:24:09.950 --> 13:24:09.960 align:start position:0% there's the Border Gateway protocol or 13:24:09.960 --> 13:24:13.310 align:start position:0% there's the Border Gateway protocol or bgp<13:24:10.616> and<13:24:11.460> finally<13:24:11.700> the<13:24:12.060> enhanced<13:24:12.540> interior 13:24:13.310 --> 13:24:13.320 align:start position:0% bgp and finally the enhanced interior 13:24:13.320 --> 13:24:17.390 align:start position:0% bgp and finally the enhanced interior Gateway<13:24:14.096> routing<13:24:14.580> protocol<13:24:14.936> or<13:24:15.800> eigrp<13:24:16.800> you 13:24:17.390 --> 13:24:17.400 align:start position:0% Gateway routing protocol or eigrp you 13:24:17.400 --> 13:24:19.850 align:start position:0% Gateway routing protocol or eigrp you see<13:24:18.060> how<13:24:18.300> these<13:24:18.900> two<13:24:19.020> sort<13:24:19.380> of<13:24:19.436> have<13:24:19.616> some 13:24:19.850 --> 13:24:19.860 align:start position:0% see how these two sort of have some 13:24:19.860 --> 13:24:21.130 align:start position:0% see how these two sort of have some similar 13:24:21.130 --> 13:24:21.140 align:start position:0% similar 13:24:21.140 --> 13:24:24.170 align:start position:0% similar names<13:24:22.140> in<13:24:22.436> them<13:24:22.616> and<13:24:23.460> these<13:24:23.756> two<13:24:23.880> are 13:24:24.170 --> 13:24:24.180 align:start position:0% names in them and these two are 13:24:24.180 --> 13:24:26.570 align:start position:0% names in them and these two are obviously<13:24:24.596> related 13:24:26.570 --> 13:24:26.580 align:start position:0% obviously related 13:24:26.580 --> 13:24:29.926 align:start position:0% obviously related rip<13:24:27.416> or<13:24:27.776> routing<13:24:28.256> information<13:24:28.436> protocol<13:24:29.276> is 13:24:29.926 --> 13:24:29.936 align:start position:0% rip or routing information protocol is 13:24:29.936 --> 13:24:33.406 align:start position:0% rip or routing information protocol is limited<13:24:30.360> to<13:24:30.596> only<13:24:30.916> 15<13:24:31.916> hops 13:24:33.406 --> 13:24:33.416 align:start position:0% limited to only 15 hops 13:24:33.416 --> 13:24:35.330 align:start position:0% limited to only 15 hops originally<13:24:34.080> it<13:24:34.380> required<13:24:34.916> the<13:24:35.096> information 13:24:35.330 --> 13:24:35.340 align:start position:0% originally it required the information 13:24:35.340 --> 13:24:39.530 align:start position:0% originally it required the information that<13:24:36.116> updated<13:24:36.596> every<13:24:37.380> 30<13:24:37.740> seconds 13:24:39.530 --> 13:24:39.540 align:start position:0% that updated every 30 seconds 13:24:39.540 --> 13:24:41.390 align:start position:0% that updated every 30 seconds and<13:24:40.020> on<13:24:40.256> a<13:24:40.436> small<13:24:40.560> Network<13:24:40.800> this<13:24:41.220> wouldn't 13:24:41.390 --> 13:24:41.400 align:start position:0% and on a small Network this wouldn't 13:24:41.400 --> 13:24:43.790 align:start position:0% and on a small Network this wouldn't have<13:24:41.580> been<13:24:41.700> a<13:24:41.880> problem<13:24:42.060> but<13:24:42.776> if<13:24:43.436> we're<13:24:43.560> talking 13:24:43.790 --> 13:24:43.800 align:start position:0% have been a problem but if we're talking 13:24:43.800 --> 13:24:45.530 align:start position:0% have been a problem but if we're talking about<13:24:43.980> a<13:24:44.276> very<13:24:44.460> large<13:24:44.700> Network<13:24:45.060> which<13:24:45.416> is 13:24:45.530 --> 13:24:45.540 align:start position:0% about a very large Network which is 13:24:45.540 --> 13:24:47.810 align:start position:0% about a very large Network which is where<13:24:45.776> networks<13:24:46.380> went<13:24:46.680> there<13:24:47.520> was<13:24:47.640> going<13:24:47.756> to 13:24:47.810 --> 13:24:47.820 align:start position:0% where networks went there was going to 13:24:47.820 --> 13:24:49.970 align:start position:0% where networks went there was going to be<13:24:47.880> a<13:24:48.180> large<13:24:48.300> amount<13:24:48.776> of<13:24:49.020> traffic<13:24:49.256> being<13:24:49.680> sent 13:24:49.970 --> 13:24:49.980 align:start position:0% be a large amount of traffic being sent 13:24:49.980 --> 13:24:52.606 align:start position:0% be a large amount of traffic being sent between<13:24:50.340> routers<13:24:50.936> at<13:24:51.116> any<13:24:51.300> one<13:24:51.480> time<13:24:51.720> and<13:24:52.436> so 13:24:52.606 --> 13:24:52.616 align:start position:0% between routers at any one time and so 13:24:52.616 --> 13:24:55.426 align:start position:0% between routers at any one time and so this<13:24:52.980> became<13:24:53.400> not<13:24:54.240> very<13:24:54.480> useful<13:24:54.900> because<13:24:55.200> of 13:24:55.426 --> 13:24:55.436 align:start position:0% this became not very useful because of 13:24:55.436 --> 13:24:58.010 align:start position:0% this became not very useful because of speed<13:24:55.680> and<13:24:56.400> also<13:24:56.640> the<13:24:57.000> protocol<13:24:57.300> itself<13:24:57.720> was 13:24:58.010 --> 13:24:58.020 align:start position:0% speed and also the protocol itself was 13:24:58.020 --> 13:25:01.070 align:start position:0% speed and also the protocol itself was just<13:24:58.256> not<13:24:58.616> very<13:24:59.040> secure<13:24:59.880> and<13:25:00.540> it<13:25:00.660> was<13:25:00.840> very 13:25:01.070 --> 13:25:01.080 align:start position:0% just not very secure and it was very 13:25:01.080 --> 13:25:03.530 align:start position:0% just not very secure and it was very vulnerable<13:25:01.560> to<13:25:01.800> attacks<13:25:02.340> and<13:25:03.060> it<13:25:03.360> didn't 13:25:03.530 --> 13:25:03.540 align:start position:0% vulnerable to attacks and it didn't 13:25:03.540 --> 13:25:06.766 align:start position:0% vulnerable to attacks and it didn't support<13:25:04.160> authentication<13:25:05.160> of<13:25:05.580> any<13:25:05.756> sort<13:25:06.000> now 13:25:06.766 --> 13:25:06.776 align:start position:0% support authentication of any sort now 13:25:06.776 --> 13:25:08.150 align:start position:0% support authentication of any sort now remember<13:25:06.960> we<13:25:07.320> want<13:25:07.560> something<13:25:07.860> like 13:25:08.150 --> 13:25:08.160 align:start position:0% remember we want something like 13:25:08.160 --> 13:25:10.850 align:start position:0% remember we want something like authentication<13:25:08.880> which<13:25:09.596> would<13:25:09.776> be<13:25:09.960> a<13:25:10.436> username 13:25:10.850 --> 13:25:10.860 align:start position:0% authentication which would be a username 13:25:10.860 --> 13:25:12.710 align:start position:0% authentication which would be a username and<13:25:11.040> a<13:25:11.160> password<13:25:11.340> so<13:25:11.880> I<13:25:12.000> can<13:25:12.116> make<13:25:12.360> sure<13:25:12.540> the 13:25:12.710 --> 13:25:12.720 align:start position:0% and a password so I can make sure the 13:25:12.720 --> 13:25:14.390 align:start position:0% and a password so I can make sure the router<13:25:13.020> contacted<13:25:13.560> me<13:25:13.680> is<13:25:13.860> the<13:25:13.980> one<13:25:14.096> that<13:25:14.276> I 13:25:14.390 --> 13:25:14.400 align:start position:0% router contacted me is the one that I 13:25:14.400 --> 13:25:16.670 align:start position:0% router contacted me is the one that I wanted<13:25:14.520> to<13:25:14.756> talk<13:25:15.000> with<13:25:15.240> so 13:25:16.670 --> 13:25:16.680 align:start position:0% wanted to talk with so 13:25:16.680 --> 13:25:20.390 align:start position:0% wanted to talk with so rip<13:25:17.640> 2<13:25:17.880> came<13:25:18.360> out<13:25:18.560> and<13:25:19.560> this<13:25:19.916> featured 13:25:20.390 --> 13:25:20.400 align:start position:0% rip 2 came out and this featured 13:25:20.400 --> 13:25:23.330 align:start position:0% rip 2 came out and this featured authentication<13:25:21.180> so<13:25:21.840> it<13:25:22.020> added<13:25:22.436> it<13:25:22.616> for<13:25:23.160> better 13:25:23.330 --> 13:25:23.340 align:start position:0% authentication so it added it for better 13:25:23.340 --> 13:25:28.130 align:start position:0% authentication so it added it for better security 13:25:28.130 --> 13:25:28.140 align:start position:0% 13:25:28.140 --> 13:25:30.970 align:start position:0% and<13:25:28.800> it<13:25:29.040> also<13:25:29.276> was<13:25:29.460> designed<13:25:29.936> to<13:25:30.416> reduce 13:25:30.970 --> 13:25:30.980 align:start position:0% and it also was designed to reduce 13:25:30.980 --> 13:25:34.850 align:start position:0% and it also was designed to reduce traffic<13:25:31.980> flow 13:25:34.850 --> 13:25:34.860 align:start position:0% 13:25:34.860 --> 13:25:39.650 align:start position:0% but<13:25:35.400> it<13:25:35.820> only<13:25:35.936> supported<13:25:36.480> 15<13:25:37.140> hops<13:25:37.980> because<13:25:38.756> it 13:25:39.650 --> 13:25:39.660 align:start position:0% but it only supported 15 hops because it 13:25:39.660 --> 13:25:41.990 align:start position:0% but it only supported 15 hops because it had<13:25:39.840> to<13:25:39.960> be<13:25:40.080> backwards<13:25:40.616> compatible<13:25:41.096> with<13:25:41.756> the 13:25:41.990 --> 13:25:42.000 align:start position:0% had to be backwards compatible with the 13:25:42.000 --> 13:25:44.030 align:start position:0% had to be backwards compatible with the previous<13:25:42.116> version<13:25:42.596> and<13:25:43.436> since<13:25:43.680> the<13:25:43.916> previous 13:25:44.030 --> 13:25:44.040 align:start position:0% previous version and since the previous 13:25:44.040 --> 13:25:47.086 align:start position:0% previous version and since the previous version<13:25:44.520> was<13:25:44.880> only<13:25:45.060> 15<13:25:45.360> hops<13:25:45.960> so<13:25:46.560> was<13:25:46.740> this<13:25:46.916> one 13:25:47.086 --> 13:25:47.096 align:start position:0% version was only 15 hops so was this one 13:25:47.096 --> 13:25:49.906 align:start position:0% version was only 15 hops so was this one so<13:25:47.580> again<13:25:47.756> not<13:25:48.180> very<13:25:48.360> useful<13:25:48.776> for<13:25:49.140> very<13:25:49.436> large 13:25:49.906 --> 13:25:49.916 align:start position:0% so again not very useful for very large 13:25:49.916 --> 13:25:56.990 align:start position:0% so again not very useful for very large intense<13:25:50.756> networks<13:25:51.416> such<13:25:52.020> as<13:25:52.200> the<13:25:52.980> internet 13:25:56.990 --> 13:25:57.000 align:start position:0% 13:25:57.000 --> 13:26:01.070 align:start position:0% now<13:25:57.720> bgp<13:25:58.560> is<13:25:58.860> often<13:25:59.400> associated<13:25:59.936> with<13:26:00.840> the 13:26:01.070 --> 13:26:01.080 align:start position:0% now bgp is often associated with the 13:26:01.080 --> 13:26:03.290 align:start position:0% now bgp is often associated with the internet<13:26:01.200> and<13:26:01.980> the<13:26:02.096> reason<13:26:02.276> is<13:26:02.640> because<13:26:03.060> it 13:26:03.290 --> 13:26:03.300 align:start position:0% internet and the reason is because it 13:26:03.300 --> 13:26:06.050 align:start position:0% internet and the reason is because it can<13:26:03.416> be<13:26:03.660> used<13:26:03.900> between<13:26:04.436> internet<13:26:05.160> gateway 13:26:06.050 --> 13:26:06.060 align:start position:0% can be used between internet gateway 13:26:06.060 --> 13:26:08.810 align:start position:0% can be used between internet gateway hosts<13:26:06.660> as<13:26:07.320> this<13:26:07.740> name 13:26:08.810 --> 13:26:08.820 align:start position:0% hosts as this name 13:26:08.820 --> 13:26:10.606 align:start position:0% hosts as this name implies 13:26:10.606 --> 13:26:10.616 align:start position:0% implies 13:26:10.616 --> 13:26:13.190 align:start position:0% implies so<13:26:10.980> it<13:26:11.220> examines<13:26:11.700> the<13:26:11.936> routing<13:26:12.300> table<13:26:12.540> and 13:26:13.190 --> 13:26:13.200 align:start position:0% so it examines the routing table and 13:26:13.200 --> 13:26:16.190 align:start position:0% so it examines the routing table and decides<13:26:13.740> what<13:26:14.220> is<13:26:14.340> the<13:26:14.520> best<13:26:14.700> route<13:26:15.240> for<13:26:15.840> data 13:26:16.190 --> 13:26:16.200 align:start position:0% decides what is the best route for data 13:26:16.200 --> 13:26:18.830 align:start position:0% decides what is the best route for data to<13:26:16.380> travel<13:26:16.640> based<13:26:17.640> on<13:26:17.700> the<13:26:17.936> connections<13:26:18.480> the 13:26:18.830 --> 13:26:18.840 align:start position:0% to travel based on the connections the 13:26:18.840 --> 13:26:21.586 align:start position:0% to travel based on the connections the distances<13:26:19.320> and<13:26:20.040> certain<13:26:20.276> addresses 13:26:21.586 --> 13:26:21.596 align:start position:0% distances and certain addresses 13:26:21.596 --> 13:26:24.106 align:start position:0% distances and certain addresses now<13:26:22.140> the<13:26:22.616> enhanced<13:26:23.040> interior<13:26:23.700> Gateway 13:26:24.106 --> 13:26:24.116 align:start position:0% now the enhanced interior Gateway 13:26:24.116 --> 13:26:27.586 align:start position:0% now the enhanced interior Gateway routing<13:26:24.540> protocol<13:26:24.840> are<13:26:25.340> eigrp<13:26:26.340> draws<13:26:27.300> upon 13:26:27.586 --> 13:26:27.596 align:start position:0% routing protocol are eigrp draws upon 13:26:27.596 --> 13:26:30.350 align:start position:0% routing protocol are eigrp draws upon information<13:26:27.840> that<13:26:28.800> its<13:26:29.276> neighboring<13:26:29.880> routers 13:26:30.350 --> 13:26:30.360 align:start position:0% information that its neighboring routers 13:26:30.360 --> 13:26:31.730 align:start position:0% information that its neighboring routers have 13:26:31.730 --> 13:26:31.740 align:start position:0% have 13:26:31.740 --> 13:26:35.390 align:start position:0% have so<13:26:32.220> it<13:26:32.400> would<13:26:32.460> look<13:26:32.700> at<13:26:32.880> all<13:26:33.240> the<13:26:33.360> routers 13:26:35.390 --> 13:26:35.400 align:start position:0% so it would look at all the routers 13:26:35.400 --> 13:26:37.730 align:start position:0% so it would look at all the routers that<13:26:35.880> it's<13:26:36.000> a<13:26:36.180> neighbor<13:26:36.300> with<13:26:36.596> now<13:26:37.256> route<13:26:37.500> is 13:26:37.730 --> 13:26:37.740 align:start position:0% that it's a neighbor with now route is 13:26:37.740 --> 13:26:40.370 align:start position:0% that it's a neighbor with now route is configured<13:26:38.160> with<13:26:38.480> eigrp<13:26:39.480> would<13:26:39.960> use<13:26:40.200> that 13:26:40.370 --> 13:26:40.380 align:start position:0% configured with eigrp would use that 13:26:40.380 --> 13:26:42.230 align:start position:0% configured with eigrp would use that information<13:26:40.616> to<13:26:41.160> determine<13:26:41.520> the<13:26:41.756> best<13:26:41.936> path 13:26:42.230 --> 13:26:42.240 align:start position:0% information to determine the best path 13:26:42.240 --> 13:26:45.050 align:start position:0% information to determine the best path for<13:26:42.480> data<13:26:42.900> all<13:26:43.560> determined<13:26:44.096> by<13:26:44.580> what<13:26:44.880> all 13:26:45.050 --> 13:26:45.060 align:start position:0% for data all determined by what all 13:26:45.060 --> 13:26:47.390 align:start position:0% for data all determined by what all these<13:26:45.360> other<13:26:45.596> routers<13:26:46.080> know<13:26:46.380> so<13:26:47.040> that's<13:26:47.160> one 13:26:47.390 --> 13:26:47.400 align:start position:0% these other routers know so that's one 13:26:47.400 --> 13:26:49.130 align:start position:0% these other routers know so that's one of<13:26:47.520> the<13:26:47.520> benefits<13:26:47.936> is<13:26:48.116> it<13:26:48.300> went<13:26:48.480> outside<13:26:48.840> of 13:26:49.130 --> 13:26:49.140 align:start position:0% of the benefits is it went outside of 13:26:49.140 --> 13:26:50.210 align:start position:0% of the benefits is it went outside of itself 13:26:50.210 --> 13:26:50.220 align:start position:0% itself 13:26:50.220 --> 13:26:53.390 align:start position:0% itself so<13:26:50.700> here's<13:26:51.180> an<13:26:51.300> example<13:26:51.720> of<13:26:52.080> basically 13:26:53.390 --> 13:26:53.400 align:start position:0% so here's an example of basically 13:26:53.400 --> 13:26:56.150 align:start position:0% so here's an example of basically distance<13:26:53.936> Vector<13:26:54.596> routing<13:26:55.020> the<13:26:55.560> router<13:26:55.980> on 13:26:56.150 --> 13:26:56.160 align:start position:0% distance Vector routing the router on 13:26:56.160 --> 13:26:59.030 align:start position:0% distance Vector routing the router on the<13:26:56.340> top<13:26:56.520> left<13:26:57.116> over<13:26:57.900> here 13:26:59.030 --> 13:26:59.040 align:start position:0% the top left over here 13:26:59.040 --> 13:27:03.586 align:start position:0% the top left over here has<13:26:59.700> no<13:27:00.060> idea<13:27:01.040> what's<13:27:02.040> going<13:27:02.460> on 13:27:03.586 --> 13:27:03.596 align:start position:0% has no idea what's going on 13:27:03.596 --> 13:27:06.230 align:start position:0% has no idea what's going on with<13:27:04.080> the<13:27:04.256> routers<13:27:04.680> over<13:27:05.220> here 13:27:06.230 --> 13:27:06.240 align:start position:0% with the routers over here 13:27:06.240 --> 13:27:09.050 align:start position:0% with the routers over here it<13:27:06.660> can<13:27:06.840> only<13:27:07.020> make<13:27:07.256> a<13:27:07.436> routing<13:27:07.740> table<13:27:08.060> based 13:27:09.050 --> 13:27:09.060 align:start position:0% it can only make a routing table based 13:27:09.060 --> 13:27:11.330 align:start position:0% it can only make a routing table based on<13:27:09.116> the<13:27:09.360> routers<13:27:09.720> it's<13:27:10.020> connected<13:27:10.560> to<13:27:10.740> just 13:27:11.330 --> 13:27:11.340 align:start position:0% on the routers it's connected to just 13:27:11.340 --> 13:27:12.950 align:start position:0% on the routers it's connected to just like<13:27:11.460> the<13:27:11.640> one<13:27:11.700> on<13:27:11.880> the<13:27:12.000> right<13:27:12.116> can<13:27:12.480> only<13:27:12.660> make 13:27:12.950 --> 13:27:12.960 align:start position:0% like the one on the right can only make 13:27:12.960 --> 13:27:15.290 align:start position:0% like the one on the right can only make uh 13:27:15.290 --> 13:27:15.300 align:start position:0% uh 13:27:15.300 --> 13:27:17.330 align:start position:0% uh routing<13:27:16.020> table<13:27:16.140> based<13:27:16.616> on<13:27:16.680> the<13:27:16.800> routers<13:27:17.040> it's 13:27:17.330 --> 13:27:17.340 align:start position:0% routing table based on the routers it's 13:27:17.340 --> 13:27:19.550 align:start position:0% routing table based on the routers it's connected<13:27:17.756> to 13:27:19.550 --> 13:27:19.560 align:start position:0% connected to 13:27:19.560 --> 13:27:22.190 align:start position:0% connected to therefore<13:27:20.276> these<13:27:20.936> two<13:27:21.060> are<13:27:21.416> unaware<13:27:21.900> of<13:27:22.020> each 13:27:22.190 --> 13:27:22.200 align:start position:0% therefore these two are unaware of each 13:27:22.200 --> 13:27:24.906 align:start position:0% therefore these two are unaware of each other's<13:27:22.560> dis<13:27:22.860> of<13:27:23.400> each<13:27:23.640> other's 13:27:24.906 --> 13:27:24.916 align:start position:0% other's dis of each other's 13:27:24.916 --> 13:27:27.290 align:start position:0% other's dis of each other's existence<13:27:25.916> because<13:27:26.520> they're<13:27:26.756> not<13:27:26.936> connected 13:27:27.290 --> 13:27:27.300 align:start position:0% existence because they're not connected 13:27:27.300 --> 13:27:28.426 align:start position:0% existence because they're not connected to<13:27:27.480> each<13:27:27.596> other 13:27:28.426 --> 13:27:28.436 align:start position:0% to each other 13:27:28.436 --> 13:27:30.766 align:start position:0% to each other now<13:27:28.916> of<13:27:29.160> course<13:27:29.340> they<13:27:29.756> can<13:27:29.936> still<13:27:30.116> communicate 13:27:30.766 --> 13:27:30.776 align:start position:0% now of course they can still communicate 13:27:30.776 --> 13:27:33.830 align:start position:0% now of course they can still communicate because<13:27:31.436> there's<13:27:31.860> probably<13:27:32.220> a<13:27:32.820> router<13:27:33.416> some 13:27:33.830 --> 13:27:33.840 align:start position:0% because there's probably a router some 13:27:33.840 --> 13:27:36.710 align:start position:0% because there's probably a router some place<13:27:34.276> that<13:27:35.276> one<13:27:35.580> of<13:27:35.640> these<13:27:35.880> is<13:27:36.060> connected<13:27:36.480> to 13:27:36.710 --> 13:27:36.720 align:start position:0% place that one of these is connected to 13:27:36.720 --> 13:27:38.630 align:start position:0% place that one of these is connected to that<13:27:37.256> will<13:27:37.380> connect<13:27:37.560> them<13:27:37.916> but<13:27:38.340> you<13:27:38.460> can<13:27:38.520> see 13:27:38.630 --> 13:27:38.640 align:start position:0% that will connect them but you can see 13:27:38.640 --> 13:27:40.906 align:start position:0% that will connect them but you can see how<13:27:38.880> this<13:27:39.116> is<13:27:39.300> going<13:27:39.480> to<13:27:39.720> make<13:27:39.960> for<13:27:40.320> a<13:27:40.500> lot<13:27:40.616> less 13:27:40.906 --> 13:27:40.916 align:start position:0% how this is going to make for a lot less 13:27:40.916 --> 13:27:44.450 align:start position:0% how this is going to make for a lot less efficient<13:27:41.640> routing 13:27:44.450 --> 13:27:44.460 align:start position:0% 13:27:44.460 --> 13:27:47.810 align:start position:0% so<13:27:45.116> unlike<13:27:45.596> those<13:27:46.020> distance<13:27:46.436> Vector<13:27:47.400> routers 13:27:47.810 --> 13:27:47.820 align:start position:0% so unlike those distance Vector routers 13:27:47.820 --> 13:27:50.330 align:start position:0% so unlike those distance Vector routers routers<13:27:48.776> configured<13:27:49.320> with<13:27:49.680> link<13:27:49.980> State 13:27:50.330 --> 13:27:50.340 align:start position:0% routers configured with link State 13:27:50.340 --> 13:27:52.370 align:start position:0% routers configured with link State Protocols<13:27:51.060> are<13:27:51.240> aware<13:27:51.480> of<13:27:51.660> every<13:27:52.140> other 13:27:52.370 --> 13:27:52.380 align:start position:0% Protocols are aware of every other 13:27:52.380 --> 13:27:54.710 align:start position:0% Protocols are aware of every other router<13:27:52.860> on<13:27:53.040> the<13:27:53.160> entire<13:27:53.400> network<13:27:53.700> they<13:27:54.540> use 13:27:54.710 --> 13:27:54.720 align:start position:0% router on the entire network they use 13:27:54.720 --> 13:27:57.290 align:start position:0% router on the entire network they use each<13:27:55.020> other<13:27:55.140> to<13:27:55.436> build<13:27:55.616> an<13:27:56.160> enormous<13:27:56.756> Network 13:27:57.290 --> 13:27:57.300 align:start position:0% each other to build an enormous Network 13:27:57.300 --> 13:28:02.086 align:start position:0% each other to build an enormous Network map 13:28:02.086 --> 13:28:02.096 align:start position:0% 13:28:02.096 --> 13:28:04.670 align:start position:0% and<13:28:02.460> then<13:28:02.580> this<13:28:02.820> network<13:28:03.000> Mac<13:28:03.416> is<13:28:04.020> shared<13:28:04.436> with 13:28:04.670 --> 13:28:04.680 align:start position:0% and then this network Mac is shared with 13:28:04.680 --> 13:28:07.606 align:start position:0% and then this network Mac is shared with each<13:28:04.860> other<13:28:05.180> unlike<13:28:06.180> distance<13:28:06.480> Vector<13:28:07.140> link 13:28:07.606 --> 13:28:07.616 align:start position:0% each other unlike distance Vector link 13:28:07.616 --> 13:28:09.650 align:start position:0% each other unlike distance Vector link State<13:28:07.916> routers<13:28:08.340> will<13:28:08.580> update<13:28:08.936> with<13:28:09.360> less 13:28:09.650 --> 13:28:09.660 align:start position:0% State routers will update with less 13:28:09.660 --> 13:28:12.586 align:start position:0% State routers will update with less frequency<13:28:10.256> so<13:28:11.096> there's<13:28:11.400> less<13:28:11.756> traffic<13:28:12.116> on<13:28:12.480> the 13:28:12.586 --> 13:28:12.596 align:start position:0% frequency so there's less traffic on the 13:28:12.596 --> 13:28:16.906 align:start position:0% frequency so there's less traffic on the network 13:28:16.906 --> 13:28:16.916 align:start position:0% 13:28:16.916 --> 13:28:20.150 align:start position:0% now<13:28:17.520> if<13:28:17.820> a<13:28:18.060> change<13:28:18.300> in<13:28:18.900> the<13:28:19.256> Network's 13:28:20.150 --> 13:28:20.160 align:start position:0% now if a change in the Network's 13:28:20.160 --> 13:28:22.246 align:start position:0% now if a change in the Network's topography<13:28:20.820> occurs<13:28:21.360> then<13:28:21.960> they 13:28:22.246 --> 13:28:22.256 align:start position:0% topography occurs then they 13:28:22.256 --> 13:28:24.230 align:start position:0% topography occurs then they automatically<13:28:22.740> update<13:28:23.160> with<13:28:23.460> each<13:28:23.580> other<13:28:23.756> and 13:28:24.230 --> 13:28:24.240 align:start position:0% automatically update with each other and 13:28:24.240 --> 13:28:26.450 align:start position:0% automatically update with each other and share<13:28:24.416> the<13:28:24.596> map<13:28:24.720> with<13:28:25.020> each<13:28:25.140> other<13:28:25.320> so<13:28:26.096> instead 13:28:26.450 --> 13:28:26.460 align:start position:0% share the map with each other so instead 13:28:26.460 --> 13:28:28.670 align:start position:0% share the map with each other so instead of<13:28:26.640> Simply<13:28:27.116> updating<13:28:27.480> at<13:28:27.776> a<13:28:27.960> certain<13:28:28.140> interval 13:28:28.670 --> 13:28:28.680 align:start position:0% of Simply updating at a certain interval 13:28:28.680 --> 13:28:32.390 align:start position:0% of Simply updating at a certain interval of<13:28:28.860> time<13:28:29.040> they're<13:28:29.580> going<13:28:29.820> to<13:28:30.116> update<13:28:30.720> whenever 13:28:32.390 --> 13:28:32.400 align:start position:0% of time they're going to update whenever 13:28:32.400 --> 13:28:34.246 align:start position:0% of time they're going to update whenever there's<13:28:32.936> a<13:28:33.180> change 13:28:34.246 --> 13:28:34.256 align:start position:0% there's a change 13:28:34.256 --> 13:28:36.530 align:start position:0% there's a change now<13:28:34.616> though<13:28:34.800> this<13:28:35.096> seems<13:28:35.520> like<13:28:35.936> link<13:28:36.240> state 13:28:36.530 --> 13:28:36.540 align:start position:0% now though this seems like link state 13:28:36.540 --> 13:28:38.990 align:start position:0% now though this seems like link state has<13:28:36.840> a<13:28:36.960> better<13:28:37.080> set<13:28:37.256> of<13:28:37.436> protocols<13:28:38.040> link<13:28:38.640> State 13:28:38.990 --> 13:28:39.000 align:start position:0% has a better set of protocols link State 13:28:39.000 --> 13:28:40.970 align:start position:0% has a better set of protocols link State routers<13:28:39.480> also<13:28:39.840> require<13:28:40.020> a<13:28:40.436> more<13:28:40.616> powerful 13:28:40.970 --> 13:28:40.980 align:start position:0% routers also require a more powerful 13:28:40.980 --> 13:28:44.266 align:start position:0% routers also require a more powerful system<13:28:41.276> components<13:28:42.060> such<13:28:42.360> as<13:28:42.596> better<13:28:43.080> Ram 13:28:44.266 --> 13:28:44.276 align:start position:0% system components such as better Ram 13:28:44.276 --> 13:28:46.970 align:start position:0% system components such as better Ram cetera<13:28:45.060> then<13:28:45.480> distance<13:28:45.720> vector<13:28:46.380> and<13:28:46.860> that's 13:28:46.970 --> 13:28:46.980 align:start position:0% cetera then distance vector and that's 13:28:46.980 --> 13:28:48.830 align:start position:0% cetera then distance vector and that's why<13:28:47.220> we<13:28:47.460> still<13:28:47.580> see<13:28:47.820> distance<13:28:48.060> Vector<13:28:48.660> used 13:28:48.830 --> 13:28:48.840 align:start position:0% why we still see distance Vector used 13:28:48.840 --> 13:28:51.350 align:start position:0% why we still see distance Vector used quite<13:28:49.256> a<13:28:49.380> bit<13:28:49.500> in<13:28:50.276> some<13:28:50.400> cases<13:28:50.700> we<13:28:50.936> don't<13:28:51.116> need 13:28:51.350 --> 13:28:51.360 align:start position:0% quite a bit in some cases we don't need 13:28:51.360 --> 13:28:52.790 align:start position:0% quite a bit in some cases we don't need link<13:28:51.596> state 13:28:52.790 --> 13:28:52.800 align:start position:0% link state 13:28:52.800 --> 13:28:55.850 align:start position:0% link state so<13:28:53.340> it<13:28:53.700> offers<13:28:54.000> quicker<13:28:54.540> convergence 13:28:55.850 --> 13:28:55.860 align:start position:0% so it offers quicker convergence 13:28:55.860 --> 13:28:58.010 align:start position:0% so it offers quicker convergence as<13:28:56.276> a<13:28:56.400> result<13:28:56.580> of<13:28:57.240> this<13:28:57.480> automatically 13:28:58.010 --> 13:28:58.020 align:start position:0% as a result of this automatically 13:28:58.020 --> 13:28:59.926 align:start position:0% as a result of this automatically updating<13:28:58.436> but<13:28:58.916> this<13:28:59.096> also<13:28:59.340> means<13:28:59.580> it<13:28:59.700> needs 13:28:59.926 --> 13:28:59.936 align:start position:0% updating but this also means it needs 13:28:59.936 --> 13:29:01.070 align:start position:0% updating but this also means it needs more<13:29:00.116> power 13:29:01.070 --> 13:29:01.080 align:start position:0% more power 13:29:01.080 --> 13:29:02.810 align:start position:0% more power so<13:29:01.380> there<13:29:01.560> are<13:29:01.680> two<13:29:01.800> protocols<13:29:02.276> I<13:29:02.460> want<13:29:02.580> to<13:29:02.700> go 13:29:02.810 --> 13:29:02.820 align:start position:0% so there are two protocols I want to go 13:29:02.820 --> 13:29:05.030 align:start position:0% so there are two protocols I want to go over<13:29:03.000> with<13:29:03.360> this<13:29:03.540> the<13:29:04.080> first<13:29:04.200> is 13:29:05.030 --> 13:29:05.040 align:start position:0% over with this the first is 13:29:05.040 --> 13:29:08.450 align:start position:0% over with this the first is the<13:29:05.580> open<13:29:05.700> shortest<13:29:06.300> path<13:29:06.540> first<13:29:06.840> or<13:29:07.080> ospf<13:29:07.800> and 13:29:08.450 --> 13:29:08.460 align:start position:0% the open shortest path first or ospf and 13:29:08.460 --> 13:29:10.850 align:start position:0% the open shortest path first or ospf and the<13:29:08.640> second<13:29:08.756> is<13:29:09.300> the<13:29:09.596> intermediate<13:29:10.200> system<13:29:10.500> to 13:29:10.850 --> 13:29:10.860 align:start position:0% the second is the intermediate system to 13:29:10.860 --> 13:29:13.670 align:start position:0% the second is the intermediate system to intermediate<13:29:11.520> system<13:29:11.820> protocol<13:29:12.500> these<13:29:13.500> are 13:29:13.670 --> 13:29:13.680 align:start position:0% intermediate system protocol these are 13:29:13.680 --> 13:29:16.246 align:start position:0% intermediate system protocol these are really<13:29:14.040> similar<13:29:14.640> and<13:29:15.180> they<13:29:15.360> both<13:29:15.596> use<13:29:15.900> a 13:29:16.246 --> 13:29:16.256 align:start position:0% really similar and they both use a 13:29:16.256 --> 13:29:19.550 align:start position:0% really similar and they both use a shortest<13:29:16.616> path<13:29:17.220> algorithm 13:29:19.550 --> 13:29:19.560 align:start position:0% shortest path algorithm 13:29:19.560 --> 13:29:21.530 align:start position:0% shortest path algorithm to<13:29:20.160> determine<13:29:20.520> the<13:29:20.756> shortest<13:29:21.060> way<13:29:21.180> for<13:29:21.416> the 13:29:21.530 --> 13:29:21.540 align:start position:0% to determine the shortest way for the 13:29:21.540 --> 13:29:23.810 align:start position:0% to determine the shortest way for the data<13:29:21.840> to<13:29:22.020> travel<13:29:22.220> however<13:29:23.220> we're<13:29:23.520> generally 13:29:23.810 --> 13:29:23.820 align:start position:0% data to travel however we're generally 13:29:23.820 --> 13:29:28.070 align:start position:0% data to travel however we're generally going<13:29:24.060> to<13:29:24.116> see<13:29:24.480> this<13:29:24.900> one<13:29:25.080> the<13:29:25.980> OS<13:29:26.460> PF<13:29:27.116> on 13:29:28.070 --> 13:29:28.080 align:start position:0% going to see this one the OS PF on 13:29:28.080 --> 13:29:31.490 align:start position:0% going to see this one the OS PF on medium<13:29:28.680> networks<13:29:29.220> and<13:29:29.880> Isis 13:29:31.490 --> 13:29:31.500 align:start position:0% medium networks and Isis 13:29:31.500 --> 13:29:33.830 align:start position:0% medium networks and Isis on<13:29:32.096> larger<13:29:32.460> Networks 13:29:33.830 --> 13:29:33.840 align:start position:0% on larger Networks 13:29:33.840 --> 13:29:35.926 align:start position:0% on larger Networks another<13:29:34.320> benefit<13:29:34.680> of<13:29:34.980> this<13:29:35.096> is<13:29:35.400> because<13:29:35.580> it 13:29:35.926 --> 13:29:35.936 align:start position:0% another benefit of this is because it 13:29:35.936 --> 13:29:38.870 align:start position:0% another benefit of this is because it knows<13:29:36.360> all<13:29:36.840> of<13:29:36.960> the<13:29:37.140> routers<13:29:37.436> on<13:29:37.616> the<13:29:37.800> network 13:29:38.870 --> 13:29:38.880 align:start position:0% knows all of the routers on the network 13:29:38.880 --> 13:29:41.450 align:start position:0% knows all of the routers on the network it<13:29:39.300> doesn't<13:29:39.416> just<13:29:39.660> think<13:29:39.840> about<13:29:40.080> distance<13:29:40.740> it 13:29:41.450 --> 13:29:41.460 align:start position:0% it doesn't just think about distance it 13:29:41.460 --> 13:29:43.730 align:start position:0% it doesn't just think about distance it also<13:29:41.756> looks<13:29:42.060> at<13:29:42.180> what<13:29:42.900> type<13:29:43.140> of<13:29:43.256> connections 13:29:43.730 --> 13:29:43.740 align:start position:0% also looks at what type of connections 13:29:43.740 --> 13:29:45.890 align:start position:0% also looks at what type of connections we<13:29:43.916> have<13:29:44.096> it<13:29:44.460> looks<13:29:44.756> at<13:29:44.880> the<13:29:45.180> state<13:29:45.480> of<13:29:45.720> the 13:29:45.890 --> 13:29:45.900 align:start position:0% we have it looks at the state of the 13:29:45.900 --> 13:29:48.406 align:start position:0% we have it looks at the state of the links<13:29:46.256> and<13:29:46.860> therefore<13:29:47.160> it<13:29:47.640> can<13:29:47.756> make<13:29:47.936> give<13:29:48.240> you 13:29:48.406 --> 13:29:48.416 align:start position:0% links and therefore it can make give you 13:29:48.416 --> 13:29:51.710 align:start position:0% links and therefore it can make give you in<13:29:48.840> some<13:29:48.960> cases<13:29:49.320> the<13:29:50.160> best<13:29:50.400> route<13:29:51.000> available 13:29:51.710 --> 13:29:51.720 align:start position:0% in some cases the best route available 13:29:51.720 --> 13:29:54.406 align:start position:0% in some cases the best route available not<13:29:52.500> just<13:29:52.616> based<13:29:52.916> on<13:29:53.040> the<13:29:53.160> number<13:29:53.276> of<13:29:53.460> hops<13:29:53.936> but 13:29:54.406 --> 13:29:54.416 align:start position:0% not just based on the number of hops but 13:29:54.416 --> 13:29:57.766 align:start position:0% not just based on the number of hops but on<13:29:54.660> a<13:29:54.840> lot<13:29:54.960> of<13:29:55.080> different<13:29:55.320> factors<13:29:55.916> so<13:29:56.880> here<13:29:57.116> we 13:29:57.766 --> 13:29:57.776 align:start position:0% on a lot of different factors so here we 13:29:57.776 --> 13:30:01.190 align:start position:0% on a lot of different factors so here we can<13:29:57.960> see<13:29:58.200> what<13:29:58.740> a<13:29:59.160> link<13:29:59.460> State<13:29:59.936> protocol<13:30:00.480> might 13:30:01.190 --> 13:30:01.200 align:start position:0% can see what a link State protocol might 13:30:01.200 --> 13:30:03.106 align:start position:0% can see what a link State protocol might look<13:30:01.436> like<13:30:01.616> the<13:30:02.340> two<13:30:02.520> different<13:30:02.700> groups 13:30:03.106 --> 13:30:03.116 align:start position:0% look like the two different groups 13:30:03.116 --> 13:30:05.570 align:start position:0% look like the two different groups aren't<13:30:03.360> connected<13:30:03.916> directly<13:30:04.916> however 13:30:05.570 --> 13:30:05.580 align:start position:0% aren't connected directly however 13:30:05.580 --> 13:30:07.906 align:start position:0% aren't connected directly however they're<13:30:06.000> both<13:30:06.240> aware<13:30:06.776> of<13:30:07.020> the<13:30:07.256> entire<13:30:07.560> network 13:30:07.906 --> 13:30:07.916 align:start position:0% they're both aware of the entire network 13:30:07.916 --> 13:30:10.970 align:start position:0% they're both aware of the entire network layout<13:30:08.640> as<13:30:09.240> you<13:30:09.416> can<13:30:09.540> see<13:30:09.720> if<13:30:10.320> we<13:30:10.436> imagine<13:30:10.616> that 13:30:10.970 --> 13:30:10.980 align:start position:0% layout as you can see if we imagine that 13:30:10.980 --> 13:30:13.550 align:start position:0% layout as you can see if we imagine that this<13:30:11.220> was<13:30:11.400> a<13:30:11.640> map<13:30:11.936> inside<13:30:12.300> of<13:30:12.596> the<13:30:12.776> router<13:30:13.140> and 13:30:13.550 --> 13:30:13.560 align:start position:0% this was a map inside of the router and 13:30:13.560 --> 13:30:15.350 align:start position:0% this was a map inside of the router and then<13:30:13.680> they<13:30:13.860> can<13:30:13.980> then<13:30:14.160> share<13:30:14.880> that<13:30:15.116> Network 13:30:15.350 --> 13:30:15.360 align:start position:0% then they can then share that Network 13:30:15.360 --> 13:30:18.470 align:start position:0% then they can then share that Network layout<13:30:15.900> with<13:30:16.320> all<13:30:16.560> of<13:30:16.680> their<13:30:16.860> other<13:30:17.096> routers 13:30:18.470 --> 13:30:18.480 align:start position:0% layout with all of their other routers 13:30:18.480 --> 13:30:20.450 align:start position:0% layout with all of their other routers in<13:30:19.020> this<13:30:19.140> way<13:30:19.256> they<13:30:19.500> create<13:30:19.740> a<13:30:20.040> massive 13:30:20.450 --> 13:30:20.460 align:start position:0% in this way they create a massive 13:30:20.460 --> 13:30:21.406 align:start position:0% in this way they create a massive Network 13:30:21.406 --> 13:30:21.416 align:start position:0% Network 13:30:21.416 --> 13:30:24.170 align:start position:0% Network and<13:30:22.200> massive<13:30:22.740> routing<13:30:23.160> map<13:30:23.460> on<13:30:23.820> their<13:30:23.936> Network 13:30:24.170 --> 13:30:24.180 align:start position:0% and massive routing map on their Network 13:30:24.180 --> 13:30:26.210 align:start position:0% and massive routing map on their Network and<13:30:25.080> can<13:30:25.320> communicate<13:30:25.800> much<13:30:26.040> more 13:30:26.210 --> 13:30:26.220 align:start position:0% and can communicate much more 13:30:26.220 --> 13:30:28.730 align:start position:0% and can communicate much more efficiently<13:30:26.700> and<13:30:27.060> quickly 13:30:28.730 --> 13:30:28.740 align:start position:0% efficiently and quickly 13:30:28.740 --> 13:30:31.190 align:start position:0% efficiently and quickly so<13:30:29.220> we've<13:30:29.820> just<13:30:29.936> talked<13:30:30.240> about<13:30:30.360> Dynamic 13:30:31.190 --> 13:30:31.200 align:start position:0% so we've just talked about Dynamic 13:30:31.200 --> 13:30:33.350 align:start position:0% so we've just talked about Dynamic routing<13:30:31.680> which<13:30:32.160> means<13:30:32.580> basically<13:30:32.936> that<13:30:33.116> the 13:30:33.350 --> 13:30:33.360 align:start position:0% routing which means basically that the 13:30:33.360 --> 13:30:35.086 align:start position:0% routing which means basically that the routers 13:30:35.086 --> 13:30:35.096 align:start position:0% routers 13:30:35.096 --> 13:30:38.266 align:start position:0% routers builds 13:30:38.266 --> 13:30:38.276 align:start position:0% 13:30:38.276 --> 13:30:43.246 align:start position:0% their<13:30:38.880> own<13:30:39.116> network<13:30:39.416> map 13:30:43.246 --> 13:30:43.256 align:start position:0% 13:30:43.256 --> 13:30:46.426 align:start position:0% or<13:30:44.000> routing<13:30:45.000> table 13:30:46.426 --> 13:30:46.436 align:start position:0% or routing table 13:30:46.436 --> 13:30:48.950 align:start position:0% or routing table this<13:30:46.740> is<13:30:46.916> much<13:30:47.096> more<13:30:47.340> efficient<13:30:47.756> than<13:30:48.416> static 13:30:48.950 --> 13:30:48.960 align:start position:0% this is much more efficient than static 13:30:48.960 --> 13:30:52.010 align:start position:0% this is much more efficient than static routing<13:30:50.096> we<13:30:50.580> also<13:30:50.820> compare<13:30:51.116> distance<13:30:51.480> Vector 13:30:52.010 --> 13:30:52.020 align:start position:0% routing we also compare distance Vector 13:30:52.020 --> 13:30:54.950 align:start position:0% routing we also compare distance Vector to<13:30:52.200> link<13:30:52.380> State<13:30:52.680> again<13:30:53.340> distance<13:30:53.756> Vector<13:30:54.416> is 13:30:54.950 --> 13:30:54.960 align:start position:0% to link State again distance Vector is 13:30:54.960 --> 13:30:57.350 align:start position:0% to link State again distance Vector is focused<13:30:55.320> very<13:30:55.560> much<13:30:55.740> on<13:30:56.040> Hops<13:30:56.460> and<13:30:57.000> isn't 13:30:57.350 --> 13:30:57.360 align:start position:0% focused very much on Hops and isn't 13:30:57.360 --> 13:30:59.450 align:start position:0% focused very much on Hops and isn't aware<13:30:57.660> of<13:30:57.960> all<13:30:58.320> of<13:30:58.436> the<13:30:58.680> devices<13:30:58.980> on<13:30:59.340> the 13:30:59.450 --> 13:30:59.460 align:start position:0% aware of all of the devices on the 13:30:59.460 --> 13:31:04.190 align:start position:0% aware of all of the devices on the network<13:30:59.580> only<13:31:00.416> direct<13:31:00.960> connections 13:31:04.190 --> 13:31:04.200 align:start position:0% 13:31:04.200 --> 13:31:06.586 align:start position:0% link<13:31:04.680> State<13:31:05.040> on<13:31:05.220> the<13:31:05.340> other<13:31:05.460> hand 13:31:06.586 --> 13:31:06.596 align:start position:0% link State on the other hand 13:31:06.596 --> 13:31:08.990 align:start position:0% link State on the other hand looks<13:31:07.200> at<13:31:07.320> other<13:31:07.616> features 13:31:08.990 --> 13:31:09.000 align:start position:0% looks at other features 13:31:09.000 --> 13:31:12.710 align:start position:0% looks at other features so<13:31:09.540> for<13:31:09.776> instance<13:31:10.080> traffic<13:31:10.680> latency<13:31:11.700> Etc 13:31:12.710 --> 13:31:12.720 align:start position:0% so for instance traffic latency Etc 13:31:12.720 --> 13:31:16.370 align:start position:0% so for instance traffic latency Etc and<13:31:13.380> has<13:31:13.916> a<13:31:14.220> huge<13:31:14.520> Network<13:31:14.700> map 13:31:16.370 --> 13:31:16.380 align:start position:0% and has a huge Network map 13:31:16.380 --> 13:31:19.310 align:start position:0% and has a huge Network map of<13:31:16.916> course<13:31:17.040> the<13:31:17.580> downside<13:31:18.060> is<13:31:18.840> that<13:31:19.020> distance 13:31:19.310 --> 13:31:19.320 align:start position:0% of course the downside is that distance 13:31:19.320 --> 13:31:21.830 align:start position:0% of course the downside is that distance Vector<13:31:19.916> is<13:31:20.520> going<13:31:20.756> to<13:31:21.000> be<13:31:21.180> a<13:31:21.480> lot<13:31:21.596> more 13:31:21.830 --> 13:31:21.840 align:start position:0% Vector is going to be a lot more 13:31:21.840 --> 13:31:24.170 align:start position:0% Vector is going to be a lot more efficient<13:31:22.256> with<13:31:22.680> the<13:31:23.040> resources<13:31:23.520> it<13:31:23.756> has<13:31:23.880> in 13:31:24.170 --> 13:31:24.180 align:start position:0% efficient with the resources it has in 13:31:24.180 --> 13:31:25.426 align:start position:0% efficient with the resources it has in the<13:31:24.300> router<13:31:24.540> than<13:31:24.660> link<13:31:24.840> state<13:31:25.140> which 13:31:25.426 --> 13:31:25.436 align:start position:0% the router than link state which 13:31:25.436 --> 13:31:29.570 align:start position:0% the router than link state which requires<13:31:25.916> uh<13:31:26.820> perhaps<13:31:27.300> better<13:31:27.900> or<13:31:28.800> more 13:31:29.570 --> 13:31:29.580 align:start position:0% requires uh perhaps better or more 13:31:29.580 --> 13:31:31.550 align:start position:0% requires uh perhaps better or more powerful<13:31:30.000> system<13:31:30.300> components 13:31:31.550 --> 13:31:31.560 align:start position:0% powerful system components 13:31:31.560 --> 13:31:33.710 align:start position:0% powerful system components we<13:31:32.220> also<13:31:32.580> finally<13:31:32.936> talked<13:31:33.360> about<13:31:33.416> the 13:31:33.710 --> 13:31:33.720 align:start position:0% we also finally talked about the 13:31:33.720 --> 13:31:36.490 align:start position:0% we also finally talked about the different<13:31:33.840> protocols<13:31:34.616> rip<13:31:35.460> rip<13:31:35.820> version<13:31:36.000> 2 13:31:36.490 --> 13:31:36.500 align:start position:0% different protocols rip rip version 2 13:31:36.500 --> 13:31:41.390 align:start position:0% different protocols rip rip version 2 bgp<13:31:37.500> and<13:31:37.980> eigrp<13:31:38.936> were<13:31:39.720> our<13:31:40.020> disinspectors<13:31:40.916> and 13:31:41.390 --> 13:31:41.400 align:start position:0% bgp and eigrp were our disinspectors and 13:31:41.400 --> 13:31:44.210 align:start position:0% bgp and eigrp were our disinspectors and our<13:31:41.580> two<13:31:41.700> link<13:31:41.936> States<13:31:42.240> again<13:31:42.840> ospf<13:31:43.680> is<13:31:44.040> for 13:31:44.210 --> 13:31:44.220 align:start position:0% our two link States again ospf is for 13:31:44.220 --> 13:31:45.766 align:start position:0% our two link States again ospf is for medium<13:31:44.640> Networks 13:31:45.766 --> 13:31:45.776 align:start position:0% medium Networks 13:31:45.776 --> 13:31:48.650 align:start position:0% medium Networks and<13:31:46.500> Isis 13:31:48.650 --> 13:31:48.660 align:start position:0% and Isis 13:31:48.660 --> 13:31:52.670 align:start position:0% and Isis or<13:31:49.020> Isis<13:31:49.616> is<13:31:50.520> for<13:31:50.756> larger<13:31:51.116> Networks 13:31:52.670 --> 13:31:52.680 align:start position:0% or Isis is for larger Networks 13:31:52.680 --> 13:31:56.210 align:start position:0% or Isis is for larger Networks we<13:31:53.160> still<13:31:53.340> see<13:31:53.580> all<13:31:53.820> of<13:31:53.936> these<13:31:54.180> used 13:31:56.210 --> 13:31:56.220 align:start position:0% we still see all of these used 13:31:56.220 --> 13:31:58.190 align:start position:0% we still see all of these used but<13:31:56.700> these<13:31:57.180> are<13:31:57.300> newer 13:31:58.190 --> 13:31:58.200 align:start position:0% but these are newer 13:31:58.200 --> 13:32:04.550 align:start position:0% but these are newer perhaps<13:31:58.860> a<13:31:59.340> faster<13:31:59.700> at<13:32:00.000> convergence 13:32:04.550 --> 13:32:04.560 align:start position:0% 13:32:04.560 --> 13:32:07.790 align:start position:0% although<13:32:05.340> perhaps<13:32:05.820> not<13:32:06.180> the<13:32:06.540> most<13:32:06.720> ideal<13:32:07.140> for 13:32:07.790 --> 13:32:07.800 align:start position:0% although perhaps not the most ideal for 13:32:07.800 --> 13:32:09.530 align:start position:0% although perhaps not the most ideal for our<13:32:07.980> Network<13:32:08.220> or<13:32:08.640> necessary<13:32:09.060> for<13:32:09.300> the<13:32:09.416> network 13:32:09.530 --> 13:32:09.540 align:start position:0% our Network or necessary for the network 13:32:09.540 --> 13:32:11.450 align:start position:0% our Network or necessary for the network we<13:32:09.900> have 13:32:11.450 --> 13:32:11.460 align:start position:0% we have 13:32:11.460 --> 13:32:13.426 align:start position:0% we have so<13:32:11.880> now<13:32:12.060> that<13:32:12.180> we've<13:32:12.360> talked<13:32:12.660> about<13:32:12.776> switching 13:32:13.426 --> 13:32:13.436 align:start position:0% so now that we've talked about switching 13:32:13.436 --> 13:32:15.170 align:start position:0% so now that we've talked about switching and<13:32:13.860> routing<13:32:14.220> I<13:32:14.640> want<13:32:14.756> to<13:32:14.880> talk<13:32:15.000> about 13:32:15.170 --> 13:32:15.180 align:start position:0% and routing I want to talk about 13:32:15.180 --> 13:32:18.650 align:start position:0% and routing I want to talk about something<13:32:15.616> which<13:32:16.616> is<13:32:16.740> a<13:32:16.980> little<13:32:17.300> not<13:32:18.300> so<13:32:18.480> much 13:32:18.650 --> 13:32:18.660 align:start position:0% something which is a little not so much 13:32:18.660 --> 13:32:21.170 align:start position:0% something which is a little not so much complex<13:32:19.140> but<13:32:19.616> allows<13:32:20.040> for<13:32:20.276> more<13:32:20.640> organization 13:32:21.170 --> 13:32:21.180 align:start position:0% complex but allows for more organization 13:32:21.180 --> 13:32:23.810 align:start position:0% complex but allows for more organization within<13:32:21.540> our<13:32:21.720> Network<13:32:21.900> which<13:32:22.436> is<13:32:22.616> called<13:32:22.916> vlans 13:32:23.810 --> 13:32:23.820 align:start position:0% within our Network which is called vlans 13:32:23.820 --> 13:32:30.590 align:start position:0% within our Network which is called vlans or<13:32:24.300> virtual<13:32:24.776> lands 13:32:30.590 --> 13:32:30.600 align:start position:0% 13:32:30.600 --> 13:32:46.490 align:start position:0% [Music] 13:32:46.490 --> 13:32:46.500 align:start position:0% 13:32:46.500 --> 13:32:50.150 align:start position:0% welcome<13:32:47.040> to<13:32:47.276> module<13:32:47.700> 8<13:32:47.820> lesson<13:32:48.240> 4A<13:32:48.800> igp<13:32:49.800> and 13:32:50.150 --> 13:32:50.160 align:start position:0% welcome to module 8 lesson 4A igp and 13:32:50.160 --> 13:32:53.030 align:start position:0% welcome to module 8 lesson 4A igp and EGP 13:32:53.030 --> 13:32:53.040 align:start position:0% 13:32:53.040 --> 13:32:54.830 align:start position:0% all<13:32:53.400> right<13:32:53.580> so<13:32:53.640> we're<13:32:53.756> going<13:32:53.880> to<13:32:54.000> look<13:32:54.180> uh<13:32:54.660> this 13:32:54.830 --> 13:32:54.840 align:start position:0% all right so we're going to look uh this 13:32:54.840 --> 13:32:57.050 align:start position:0% all right so we're going to look uh this is<13:32:54.900> an<13:32:55.080> overview<13:32:55.436> really<13:32:55.860> to<13:32:56.220> put<13:32:56.580> things<13:32:56.820> in 13:32:57.050 --> 13:32:57.060 align:start position:0% is an overview really to put things in 13:32:57.060 --> 13:32:59.530 align:start position:0% is an overview really to put things in context<13:32:57.416> a<13:32:57.776> dynamic<13:32:58.200> router<13:32:58.560> protocols 13:32:59.530 --> 13:32:59.540 align:start position:0% context a dynamic router protocols 13:32:59.540 --> 13:33:02.446 align:start position:0% context a dynamic router protocols interior<13:33:00.540> Gateway<13:33:01.020> protocols<13:33:01.800> autonomous 13:33:02.446 --> 13:33:02.456 align:start position:0% interior Gateway protocols autonomous 13:33:02.456 --> 13:33:03.790 align:start position:0% interior Gateway protocols autonomous systems 13:33:03.790 --> 13:33:03.800 align:start position:0% systems 13:33:03.800 --> 13:33:07.010 align:start position:0% systems bgp<13:33:04.800> in<13:33:05.276> brief<13:33:05.580> obviously<13:33:06.360> how<13:33:06.596> the<13:33:06.720> protocol 13:33:07.010 --> 13:33:07.020 align:start position:0% bgp in brief obviously how the protocol 13:33:07.020 --> 13:33:09.710 align:start position:0% bgp in brief obviously how the protocol works<13:33:07.500> much 13:33:09.710 --> 13:33:09.720 align:start position:0% works much 13:33:09.720 --> 13:33:11.870 align:start position:0% works much so<13:33:10.080> we<13:33:10.256> can<13:33:10.380> classify<13:33:10.916> Dynamic<13:33:11.520> writing 13:33:11.870 --> 13:33:11.880 align:start position:0% so we can classify Dynamic writing 13:33:11.880 --> 13:33:16.730 align:start position:0% so we can classify Dynamic writing protocols<13:33:12.480> into<13:33:12.776> interior<13:33:13.740> uh<13:33:14.580> and<13:33:14.756> exterior 13:33:16.730 --> 13:33:16.740 align:start position:0% protocols into interior uh and exterior 13:33:16.740 --> 13:33:19.010 align:start position:0% protocols into interior uh and exterior the<13:33:17.400> interior<13:33:17.820> protocols<13:33:18.540> these<13:33:18.840> are<13:33:18.900> the 13:33:19.010 --> 13:33:19.020 align:start position:0% the interior protocols these are the 13:33:19.020 --> 13:33:21.530 align:start position:0% the interior protocols these are the ones<13:33:19.256> that<13:33:19.436> we'll<13:33:19.616> be<13:33:19.800> using<13:33:20.220> mostly<13:33:20.880> As 13:33:21.530 --> 13:33:21.540 align:start position:0% ones that we'll be using mostly As 13:33:21.540 --> 13:33:23.570 align:start position:0% ones that we'll be using mostly As Network<13:33:21.776> Engineers<13:33:22.320> on<13:33:22.616> a<13:33:22.740> day-to-day<13:33:23.160> basis 13:33:23.570 --> 13:33:23.580 align:start position:0% Network Engineers on a day-to-day basis 13:33:23.580 --> 13:33:26.690 align:start position:0% Network Engineers on a day-to-day basis unless<13:33:24.416> we<13:33:24.596> end<13:33:24.776> up<13:33:24.900> working<13:33:25.200> for<13:33:25.616> an<13:33:25.916> ISP<13:33:26.456> an 13:33:26.690 --> 13:33:26.700 align:start position:0% unless we end up working for an ISP an 13:33:26.700 --> 13:33:29.390 align:start position:0% unless we end up working for an ISP an internet<13:33:26.880> service<13:33:27.240> provider 13:33:29.390 --> 13:33:29.400 align:start position:0% internet service provider 13:33:29.400 --> 13:33:31.370 align:start position:0% internet service provider so<13:33:29.936> in<13:33:30.116> order<13:33:30.300> to<13:33:30.416> understand<13:33:30.720> what<13:33:31.080> we<13:33:31.200> mean 13:33:31.370 --> 13:33:31.380 align:start position:0% so in order to understand what we mean 13:33:31.380 --> 13:33:32.926 align:start position:0% so in order to understand what we mean by<13:33:31.560> the<13:33:31.680> inside<13:33:31.800> of<13:33:32.096> a<13:33:32.160> network<13:33:32.276> we<13:33:32.820> actually 13:33:32.926 --> 13:33:32.936 align:start position:0% by the inside of a network we actually 13:33:32.936 --> 13:33:35.390 align:start position:0% by the inside of a network we actually need<13:33:33.180> to<13:33:33.416> understand<13:33:33.660> the<13:33:34.080> term<13:33:34.400> autonomous 13:33:35.390 --> 13:33:35.400 align:start position:0% need to understand the term autonomous 13:33:35.400 --> 13:33:37.606 align:start position:0% need to understand the term autonomous system<13:33:35.640> which<13:33:36.060> we<13:33:36.300> generally<13:33:36.660> shorten<13:33:37.140> as<13:33:37.380> an 13:33:37.606 --> 13:33:37.616 align:start position:0% system which we generally shorten as an 13:33:37.616 --> 13:33:40.606 align:start position:0% system which we generally shorten as an m2as 13:33:40.606 --> 13:33:40.616 align:start position:0% m2as 13:33:40.616 --> 13:33:43.010 align:start position:0% m2as so<13:33:41.040> an<13:33:41.220> AES<13:33:41.580> is<13:33:41.936> one<13:33:42.180> or<13:33:42.360> more<13:33:42.480> networks<13:33:42.900> that 13:33:43.010 --> 13:33:43.020 align:start position:0% so an AES is one or more networks that 13:33:43.020 --> 13:33:44.746 align:start position:0% so an AES is one or more networks that are<13:33:43.200> governed<13:33:43.560> by<13:33:43.680> a<13:33:43.860> single<13:33:44.160> Administration 13:33:44.746 --> 13:33:44.756 align:start position:0% are governed by a single Administration 13:33:44.756 --> 13:33:47.870 align:start position:0% are governed by a single Administration so<13:33:45.596> it<13:33:45.720> could<13:33:45.900> be<13:33:46.140> a<13:33:46.560> company<13:33:46.800> Network<13:33:47.160> or<13:33:47.700> a 13:33:47.870 --> 13:33:47.880 align:start position:0% so it could be a company Network or a 13:33:47.880 --> 13:33:50.210 align:start position:0% so it could be a company Network or a large<13:33:48.000> company<13:33:48.240> Network<13:33:48.740> and<13:33:49.740> you<13:33:49.860> can<13:33:49.980> see 13:33:50.210 --> 13:33:50.220 align:start position:0% large company Network and you can see 13:33:50.220 --> 13:33:53.870 align:start position:0% large company Network and you can see here<13:33:50.456> we<13:33:50.820> have<13:33:51.596> um<13:33:51.596> three<13:33:51.956> different<13:33:52.276> asses 13:33:53.870 --> 13:33:53.880 align:start position:0% here we have um three different asses 13:33:53.880 --> 13:33:56.266 align:start position:0% here we have um three different asses now<13:33:54.360> these<13:33:54.660> as<13:33:54.776> could<13:33:55.436> actually<13:33:55.680> all<13:33:55.980> belong 13:33:56.266 --> 13:33:56.276 align:start position:0% now these as could actually all belong 13:33:56.276 --> 13:33:58.670 align:start position:0% now these as could actually all belong to<13:33:56.400> the<13:33:56.580> same<13:33:56.756> company<13:33:57.080> and<13:33:58.080> inside<13:33:58.256> you've 13:33:58.670 --> 13:33:58.680 align:start position:0% to the same company and inside you've 13:33:58.680 --> 13:34:00.586 align:start position:0% to the same company and inside you've got<13:33:58.800> a<13:33:58.980> different<13:33:59.160> administrative<13:33:59.880> domains 13:34:00.586 --> 13:34:00.596 align:start position:0% got a different administrative domains 13:34:00.596 --> 13:34:04.010 align:start position:0% got a different administrative domains for<13:34:00.840> example<13:34:01.276> the<13:34:02.276> large<13:34:02.456> Cloud<13:34:02.756> as200<13:34:03.660> could 13:34:04.010 --> 13:34:04.020 align:start position:0% for example the large Cloud as200 could 13:34:04.020 --> 13:34:06.470 align:start position:0% for example the large Cloud as200 could all<13:34:04.140> be<13:34:04.320> running<13:34:04.436> ospf<13:34:05.340> and<13:34:06.060> you<13:34:06.180> could<13:34:06.300> have 13:34:06.470 --> 13:34:06.480 align:start position:0% all be running ospf and you could have 13:34:06.480 --> 13:34:08.570 align:start position:0% all be running ospf and you could have bought<13:34:06.660> a<13:34:06.900> company<13:34:07.020> on<13:34:07.560> the<13:34:07.680> top<13:34:07.860> left<13:34:08.096> there 13:34:08.570 --> 13:34:08.580 align:start position:0% bought a company on the top left there 13:34:08.580 --> 13:34:12.530 align:start position:0% bought a company on the top left there that<13:34:09.720> um<13:34:09.720> is<13:34:10.080> running<13:34:10.340> ergrp<13:34:11.340> or<13:34:11.936> just<13:34:12.180> has<13:34:12.360> a 13:34:12.530 --> 13:34:12.540 align:start position:0% that um is running ergrp or just has a 13:34:12.540 --> 13:34:13.906 align:start position:0% that um is running ergrp or just has a different<13:34:12.660> set<13:34:13.256> of<13:34:13.380> administrative 13:34:13.906 --> 13:34:13.916 align:start position:0% different set of administrative 13:34:13.916 --> 13:34:17.330 align:start position:0% different set of administrative principle<13:34:14.700> principles<13:34:15.480> and<13:34:15.720> roles<13:34:16.616> in<13:34:17.160> this 13:34:17.330 --> 13:34:17.340 align:start position:0% principle principles and roles in this 13:34:17.340 --> 13:34:20.510 align:start position:0% principle principles and roles in this particular<13:34:17.640> example<13:34:18.360> you<13:34:18.660> can<13:34:18.776> see<13:34:19.220> as100<13:34:20.220> on 13:34:20.510 --> 13:34:20.520 align:start position:0% particular example you can see as100 on 13:34:20.520 --> 13:34:23.210 align:start position:0% particular example you can see as100 on the<13:34:20.700> top<13:34:20.820> left<13:34:21.000> and<13:34:21.900> as300<13:34:22.560> on<13:34:22.800> the<13:34:22.916> top<13:34:22.980> right 13:34:23.210 --> 13:34:23.220 align:start position:0% the top left and as300 on the top right 13:34:23.220 --> 13:34:25.670 align:start position:0% the top left and as300 on the top right are<13:34:23.520> actually<13:34:23.700> isps 13:34:25.670 --> 13:34:25.680 align:start position:0% are actually isps 13:34:25.680 --> 13:34:29.350 align:start position:0% are actually isps these<13:34:26.276> are<13:34:26.400> internet<13:34:26.580> service<13:34:26.936> providers 13:34:29.350 --> 13:34:29.360 align:start position:0% these are internet service providers 13:34:29.360 --> 13:34:30.890 align:start position:0% these are internet service providers so 13:34:30.890 --> 13:34:30.900 align:start position:0% so 13:34:30.900 --> 13:34:33.350 align:start position:0% so um<13:34:30.956> even<13:34:31.560> though<13:34:31.740> it<13:34:32.040> says<13:34:32.276> here<13:34:32.400> that<13:34:32.640> the<13:34:33.000> as 13:34:33.350 --> 13:34:33.360 align:start position:0% um even though it says here that the as 13:34:33.360 --> 13:34:36.106 align:start position:0% um even though it says here that the as within<13:34:34.320> is<13:34:34.916> under<13:34:35.096> the<13:34:35.340> control<13:34:35.520> of<13:34:35.756> a<13:34:35.880> single 13:34:36.106 --> 13:34:36.116 align:start position:0% within is under the control of a single 13:34:36.116 --> 13:34:38.446 align:start position:0% within is under the control of a single Authority<13:34:36.596> you<13:34:37.380> could<13:34:37.500> have<13:34:37.680> various<13:34:38.040> teams 13:34:38.446 --> 13:34:38.456 align:start position:0% Authority you could have various teams 13:34:38.456 --> 13:34:40.070 align:start position:0% Authority you could have various teams managing<13:34:38.936> different<13:34:39.180> parts<13:34:39.480> of<13:34:39.720> the<13:34:39.900> network 13:34:40.070 --> 13:34:40.080 align:start position:0% managing different parts of the network 13:34:40.080 --> 13:34:42.070 align:start position:0% managing different parts of the network however<13:34:40.980> it's<13:34:41.160> all<13:34:41.340> under<13:34:41.520> the<13:34:41.820> same 13:34:42.070 --> 13:34:42.080 align:start position:0% however it's all under the same 13:34:42.080 --> 13:34:45.830 align:start position:0% however it's all under the same administrative<13:34:43.080> control 13:34:45.830 --> 13:34:45.840 align:start position:0% 13:34:45.840 --> 13:34:48.230 align:start position:0% as<13:34:46.380> is<13:34:46.800> actually<13:34:46.980> defined<13:34:47.520> in<13:34:47.640> the<13:34:47.820> one<13:34:48.060> of<13:34:48.180> the 13:34:48.230 --> 13:34:48.240 align:start position:0% as is actually defined in the one of the 13:34:48.240 --> 13:34:51.230 align:start position:0% as is actually defined in the one of the rfcs<13:34:49.020> 1930<13:34:49.800> if<13:34:50.160> you<13:34:50.276> wanted<13:34:50.400> to<13:34:50.640> Google<13:34:50.880> that 13:34:51.230 --> 13:34:51.240 align:start position:0% rfcs 1930 if you wanted to Google that 13:34:51.240 --> 13:34:52.906 align:start position:0% rfcs 1930 if you wanted to Google that but<13:34:51.540> it'd<13:34:51.900> probably<13:34:52.080> be<13:34:52.256> a<13:34:52.380> fairly<13:34:52.616> long<13:34:52.800> and 13:34:52.906 --> 13:34:52.916 align:start position:0% but it'd probably be a fairly long and 13:34:52.916 --> 13:34:54.530 align:start position:0% but it'd probably be a fairly long and boring<13:34:53.276> read<13:34:53.520> I<13:34:53.756> think 13:34:54.530 --> 13:34:54.540 align:start position:0% boring read I think 13:34:54.540 --> 13:34:56.710 align:start position:0% boring read I think according<13:34:55.256> to<13:34:55.436> the<13:34:55.616> definition<13:34:55.800> of<13:34:56.276> the<13:34:56.456> as 13:34:56.710 --> 13:34:56.720 align:start position:0% according to the definition of the as 13:34:56.720 --> 13:34:59.210 align:start position:0% according to the definition of the as it's<13:34:57.720> a<13:34:57.900> set<13:34:58.020> of<13:34:58.200> routers<13:34:58.560> under<13:34:58.740> a<13:34:58.980> single 13:34:59.210 --> 13:34:59.220 align:start position:0% it's a set of routers under a single 13:34:59.220 --> 13:35:02.810 align:start position:0% it's a set of routers under a single technical<13:34:59.580> Administration<13:35:00.616> uses<13:35:01.616> an<13:35:02.040> igp 13:35:02.810 --> 13:35:02.820 align:start position:0% technical Administration uses an igp 13:35:02.820 --> 13:35:05.210 align:start position:0% technical Administration uses an igp interior<13:35:03.360> Gateway<13:35:03.720> protocol<13:35:04.200> and<13:35:05.096> common 13:35:05.210 --> 13:35:05.220 align:start position:0% interior Gateway protocol and common 13:35:05.220 --> 13:35:08.870 align:start position:0% interior Gateway protocol and common metrics<13:35:05.820> to<13:35:05.936> Route<13:35:06.116> packets<13:35:06.660> within<13:35:07.140> the<13:35:07.380> as 13:35:08.870 --> 13:35:08.880 align:start position:0% metrics to Route packets within the as 13:35:08.880 --> 13:35:11.746 align:start position:0% metrics to Route packets within the as you<13:35:09.480> would<13:35:09.660> you<13:35:09.776> generally<13:35:10.140> use<13:35:10.616> an<13:35:11.220> exterior 13:35:11.746 --> 13:35:11.756 align:start position:0% you would you generally use an exterior 13:35:11.756 --> 13:35:14.510 align:start position:0% you would you generally use an exterior Gateway<13:35:12.180> protocol<13:35:12.720> an<13:35:13.080> EGP<13:35:13.680> to<13:35:13.860> Route<13:35:14.096> package 13:35:14.510 --> 13:35:14.520 align:start position:0% Gateway protocol an EGP to Route package 13:35:14.520 --> 13:35:19.010 align:start position:0% Gateway protocol an EGP to Route package to<13:35:14.756> other<13:35:15.000> autonomous<13:35:15.596> systems 13:35:19.010 --> 13:35:19.020 align:start position:0% 13:35:19.020 --> 13:35:21.766 align:start position:0% The<13:35:19.560> ROC<13:35:20.040> says<13:35:20.340> that<13:35:20.456> the<13:35:20.700> as<13:35:20.880> a<13:35:21.480> single<13:35:21.660> and 13:35:21.766 --> 13:35:21.776 align:start position:0% The ROC says that the as a single and 13:35:21.776 --> 13:35:23.690 align:start position:0% The ROC says that the as a single and clearly<13:35:22.140> defined<13:35:22.560> routing<13:35:22.980> policy<13:35:23.520> which 13:35:23.690 --> 13:35:23.700 align:start position:0% clearly defined routing policy which 13:35:23.700 --> 13:35:26.330 align:start position:0% clearly defined routing policy which makes<13:35:23.936> sense<13:35:24.240> if<13:35:24.596> your<13:35:25.020> company<13:35:25.980> is<13:35:26.220> running 13:35:26.330 --> 13:35:26.340 align:start position:0% makes sense if your company is running 13:35:26.340 --> 13:35:28.970 align:start position:0% makes sense if your company is running the<13:35:26.580> administration 13:35:28.970 --> 13:35:28.980 align:start position:0% the administration 13:35:28.980 --> 13:35:31.490 align:start position:0% the administration now<13:35:29.276> routers<13:35:29.700> within<13:35:30.060> an<13:35:30.180> AES<13:35:30.480> use<13:35:30.776> an<13:35:30.956> igp 13:35:31.490 --> 13:35:31.500 align:start position:0% now routers within an AES use an igp 13:35:31.500 --> 13:35:34.970 align:start position:0% now routers within an AES use an igp which<13:35:31.800> I've<13:35:31.980> already<13:35:32.160> said<13:35:32.540> so<13:35:33.540> here's<13:35:34.436> um 13:35:34.970 --> 13:35:34.980 align:start position:0% which I've already said so here's um 13:35:34.980 --> 13:35:38.510 align:start position:0% which I've already said so here's um an<13:35:35.456> image<13:35:35.700> from<13:35:36.020> Microsoft's<13:35:37.020> tech<13:35:37.200> net<13:35:37.520> you 13:35:38.510 --> 13:35:38.520 align:start position:0% an image from Microsoft's tech net you 13:35:38.520 --> 13:35:41.210 align:start position:0% an image from Microsoft's tech net you can<13:35:38.640> see<13:35:38.880> there's<13:35:39.240> two<13:35:39.540> different<13:35:40.220> autonomous 13:35:41.210 --> 13:35:41.220 align:start position:0% can see there's two different autonomous 13:35:41.220 --> 13:35:44.150 align:start position:0% can see there's two different autonomous systems<13:35:41.640> here<13:35:41.880> they're<13:35:42.720> running<13:35:42.956> an<13:35:43.256> igp<13:35:43.800> and 13:35:44.150 --> 13:35:44.160 align:start position:0% systems here they're running an igp and 13:35:44.160 --> 13:35:46.010 align:start position:0% systems here they're running an igp and is<13:35:44.340> here<13:35:44.520> we<13:35:44.640> Gateway<13:35:44.936> protocol<13:35:45.300> doing<13:35:45.720> all 13:35:46.010 --> 13:35:46.020 align:start position:0% is here we Gateway protocol doing all 13:35:46.020 --> 13:35:49.010 align:start position:0% is here we Gateway protocol doing all their<13:35:46.456> ospf<13:35:47.456> routing<13:35:48.060> whatever<13:35:48.360> they<13:35:48.660> need<13:35:48.840> to 13:35:49.010 --> 13:35:49.020 align:start position:0% their ospf routing whatever they need to 13:35:49.020 --> 13:35:51.650 align:start position:0% their ospf routing whatever they need to do<13:35:49.200> and<13:35:50.096> then<13:35:50.220> in<13:35:50.456> order<13:35:50.580> to<13:35:50.756> communicate<13:35:51.300> with 13:35:51.650 --> 13:35:51.660 align:start position:0% do and then in order to communicate with 13:35:51.660 --> 13:35:53.690 align:start position:0% do and then in order to communicate with another<13:35:51.840> autonomous<13:35:52.560> system<13:35:52.740> it's<13:35:53.400> running 13:35:53.690 --> 13:35:53.700 align:start position:0% another autonomous system it's running 13:35:53.700 --> 13:35:57.010 align:start position:0% another autonomous system it's running in<13:35:53.936> the<13:35:54.180> EGP<13:35:54.840> between<13:35:55.560> the<13:35:55.916> two<13:35:56.096> border 13:35:57.010 --> 13:35:57.020 align:start position:0% in the EGP between the two border 13:35:57.020 --> 13:36:01.070 align:start position:0% in the EGP between the two border routers<13:35:58.020> there 13:36:01.070 --> 13:36:01.080 align:start position:0% 13:36:01.080 --> 13:36:05.390 align:start position:0% you<13:36:01.616> can<13:36:01.800> further<13:36:02.240> and<13:36:03.240> divide<13:36:04.040> igps<13:36:05.040> into 13:36:05.390 --> 13:36:05.400 align:start position:0% you can further and divide igps into 13:36:05.400 --> 13:36:08.446 align:start position:0% you can further and divide igps into distance<13:36:05.756> Vector<13:36:06.300> link<13:36:06.540> state<13:36:06.840> or<13:36:07.140> hybrid 13:36:08.446 --> 13:36:08.456 align:start position:0% distance Vector link state or hybrid 13:36:08.456 --> 13:36:10.550 align:start position:0% distance Vector link state or hybrid some<13:36:09.000> of<13:36:09.116> the<13:36:09.240> common<13:36:09.360> ones<13:36:09.660> are<13:36:09.840> rip<13:36:10.080> or<13:36:10.380> rip 13:36:10.550 --> 13:36:10.560 align:start position:0% some of the common ones are rip or rip 13:36:10.560 --> 13:36:11.810 align:start position:0% some of the common ones are rip or rip version<13:36:10.800> two 13:36:11.810 --> 13:36:11.820 align:start position:0% version two 13:36:11.820 --> 13:36:14.390 align:start position:0% version two ospf<13:36:12.720> is<13:36:12.900> an<13:36:13.140> advanced<13:36:13.560> writing<13:36:13.980> protocol 13:36:14.390 --> 13:36:14.400 align:start position:0% ospf is an advanced writing protocol 13:36:14.400 --> 13:36:15.970 align:start position:0% ospf is an advanced writing protocol Isis 13:36:15.970 --> 13:36:15.980 align:start position:0% Isis 13:36:15.980 --> 13:36:20.810 align:start position:0% Isis ergrp<13:36:16.980> is<13:36:17.580> a<13:36:18.360> hybrid<13:36:18.956> which<13:36:19.740> is<13:36:19.860> uses<13:36:20.276> parts<13:36:20.580> of 13:36:20.810 --> 13:36:20.820 align:start position:0% ergrp is a hybrid which is uses parts of 13:36:20.820 --> 13:36:23.330 align:start position:0% ergrp is a hybrid which is uses parts of the<13:36:21.000> distance<13:36:21.180> vector<13:36:21.840> and<13:36:22.740> part<13:36:22.916> of<13:36:23.096> the<13:36:23.220> link 13:36:23.330 --> 13:36:23.340 align:start position:0% the distance vector and part of the link 13:36:23.340 --> 13:36:26.746 align:start position:0% the distance vector and part of the link state<13:36:24.140> igrp<13:36:25.140> is<13:36:26.160> um 13:36:26.746 --> 13:36:26.756 align:start position:0% state igrp is um 13:36:26.756 --> 13:36:28.906 align:start position:0% state igrp is um pretty<13:36:27.416> redundant<13:36:27.956> now<13:36:28.140> to<13:36:28.380> be<13:36:28.500> honest<13:36:28.740> it's 13:36:28.906 --> 13:36:28.916 align:start position:0% pretty redundant now to be honest it's 13:36:28.916 --> 13:36:31.490 align:start position:0% pretty redundant now to be honest it's not<13:36:29.220> very<13:36:29.456> rarely<13:36:29.820> used<13:36:30.116> because<13:36:31.020> of<13:36:31.256> its 13:36:31.490 --> 13:36:31.500 align:start position:0% not very rarely used because of its 13:36:31.500 --> 13:36:35.266 align:start position:0% not very rarely used because of its aging<13:36:31.800> it's<13:36:31.980> not<13:36:32.276> very<13:36:32.400> flexible<13:36:32.820> at<13:36:33.116> all 13:36:35.266 --> 13:36:35.276 align:start position:0% 13:36:35.276 --> 13:36:37.850 align:start position:0% uh<13:36:36.060> exterior<13:36:36.480> Gateway<13:36:36.840> protocol<13:36:37.256> is<13:36:37.680> a 13:36:37.850 --> 13:36:37.860 align:start position:0% uh exterior Gateway protocol is a 13:36:37.860 --> 13:36:39.710 align:start position:0% uh exterior Gateway protocol is a routing<13:36:38.160> protocol<13:36:38.456> used<13:36:38.756> to<13:36:38.936> route<13:36:39.060> between<13:36:39.360> a 13:36:39.710 --> 13:36:39.720 align:start position:0% routing protocol used to route between a 13:36:39.720 --> 13:36:41.926 align:start position:0% routing protocol used to route between a s's<13:36:40.080> which<13:36:40.256> we've<13:36:40.500> already<13:36:40.616> mentioned<13:36:41.400> if 13:36:41.926 --> 13:36:41.936 align:start position:0% s's which we've already mentioned if 13:36:41.936 --> 13:36:43.550 align:start position:0% s's which we've already mentioned if you're<13:36:42.060> going<13:36:42.180> to<13:36:42.300> route<13:36:42.480> between<13:36:42.776> autonomous 13:36:43.550 --> 13:36:43.560 align:start position:0% you're going to route between autonomous 13:36:43.560 --> 13:36:46.550 align:start position:0% you're going to route between autonomous systems<13:36:43.916> it's<13:36:44.160> referred<13:36:44.640> to<13:36:44.756> as<13:36:45.116> inter<13:36:45.560> as 13:36:46.550 --> 13:36:46.560 align:start position:0% systems it's referred to as inter as 13:36:46.560 --> 13:36:49.550 align:start position:0% systems it's referred to as inter as routing 13:36:49.550 --> 13:36:49.560 align:start position:0% routing 13:36:49.560 --> 13:36:52.606 align:start position:0% routing so<13:36:49.916> an<13:36:50.040> example<13:36:50.400> is<13:36:50.756> bgp<13:36:51.540> which<13:36:52.200> is<13:36:52.320> mentioned 13:36:52.606 --> 13:36:52.616 align:start position:0% so an example is bgp which is mentioned 13:36:52.616 --> 13:36:55.010 align:start position:0% so an example is bgp which is mentioned in<13:36:52.800> the<13:36:52.980> syllabus<13:36:53.400> is<13:36:54.000> used<13:36:54.360> for<13:36:54.540> inter<13:36:54.720> as 13:36:55.010 --> 13:36:55.020 align:start position:0% in the syllabus is used for inter as 13:36:55.020 --> 13:36:57.426 align:start position:0% in the syllabus is used for inter as routing<13:36:55.560> so<13:36:55.800> it's<13:36:55.916> a<13:36:56.160> route<13:36:56.276> between 13:36:57.426 --> 13:36:57.436 align:start position:0% routing so it's a route between 13:36:57.436 --> 13:37:01.606 align:start position:0% routing so it's a route between as1<13:36:58.436> 2<13:36:58.916> and<13:36:59.160> 3<13:36:59.340> here<13:36:59.720> we've<13:37:00.720> got<13:37:00.840> an<13:37:01.140> exterior 13:37:01.606 --> 13:37:01.616 align:start position:0% as1 2 and 3 here we've got an exterior 13:37:01.616 --> 13:37:04.010 align:start position:0% as1 2 and 3 here we've got an exterior Gateway<13:37:02.220> routing<13:37:02.820> protocol<13:37:03.180> there<13:37:03.900> is 13:37:04.010 --> 13:37:04.020 align:start position:0% Gateway routing protocol there is 13:37:04.020 --> 13:37:06.290 align:start position:0% Gateway routing protocol there is actually<13:37:04.256> a<13:37:04.616> writing<13:37:05.220> protocol<13:37:05.580> called 13:37:06.290 --> 13:37:06.300 align:start position:0% actually a writing protocol called 13:37:06.300 --> 13:37:09.890 align:start position:0% actually a writing protocol called interior<13:37:07.160> bgp<13:37:08.160> which<13:37:08.756> you<13:37:08.880> can<13:37:09.060> use<13:37:09.240> to<13:37:09.720> Route 13:37:09.890 --> 13:37:09.900 align:start position:0% interior bgp which you can use to Route 13:37:09.900 --> 13:37:12.890 align:start position:0% interior bgp which you can use to Route within<13:37:10.380> an<13:37:10.616> autonomous<13:37:11.160> system<13:37:11.480> and<13:37:12.480> I<13:37:12.596> think 13:37:12.890 --> 13:37:12.900 align:start position:0% within an autonomous system and I think 13:37:12.900 --> 13:37:15.050 align:start position:0% within an autonomous system and I think that's<13:37:13.020> mentioned<13:37:13.500> in<13:37:13.740> the<13:37:13.916> syllabus<13:37:14.340> in<13:37:14.936> any 13:37:15.050 --> 13:37:15.060 align:start position:0% that's mentioned in the syllabus in any 13:37:15.060 --> 13:37:19.070 align:start position:0% that's mentioned in the syllabus in any detail<13:37:15.596> but<13:37:16.860> um<13:37:16.860> bgp<13:37:17.456> is<13:37:17.820> used<13:37:18.060> to<13:37:18.840> route 13:37:19.070 --> 13:37:19.080 align:start position:0% detail but um bgp is used to route 13:37:19.080 --> 13:37:24.290 align:start position:0% detail but um bgp is used to route between<13:37:19.936> autonomous<13:37:20.936> systems<13:37:21.360> exterior<13:37:21.956> bgp 13:37:24.290 --> 13:37:24.300 align:start position:0% between autonomous systems exterior bgp 13:37:24.300 --> 13:37:26.810 align:start position:0% between autonomous systems exterior bgp now<13:37:24.840> each<13:37:25.020> as<13:37:25.256> is<13:37:25.680> actually<13:37:25.860> given<13:37:26.276> a<13:37:26.456> unique 13:37:26.810 --> 13:37:26.820 align:start position:0% now each as is actually given a unique 13:37:26.820 --> 13:37:29.390 align:start position:0% now each as is actually given a unique number<13:37:27.720> you<13:37:28.436> have<13:37:28.560> to<13:37:28.680> apply<13:37:28.980> for<13:37:29.160> these 13:37:29.390 --> 13:37:29.400 align:start position:0% number you have to apply for these 13:37:29.400 --> 13:37:31.850 align:start position:0% number you have to apply for these numbers<13:37:29.580> to<13:37:30.000> your<13:37:30.300> service<13:37:30.480> provider<13:37:31.200> or<13:37:31.500> your 13:37:31.850 --> 13:37:31.860 align:start position:0% numbers to your service provider or your 13:37:31.860 --> 13:37:37.550 align:start position:0% numbers to your service provider or your internet<13:37:32.116> registry<13:37:33.116> whoever<13:37:33.540> that<13:37:33.776> may<13:37:33.956> be 13:37:37.550 --> 13:37:37.560 align:start position:0% 13:37:37.560 --> 13:37:40.070 align:start position:0% and<13:37:38.160> as<13:37:38.400> I<13:37:38.580> said<13:37:38.756> I've<13:37:39.240> already<13:37:39.480> said<13:37:39.720> this<13:37:39.900> it 13:37:40.070 --> 13:37:40.080 align:start position:0% and as I said I've already said this it 13:37:40.080 --> 13:37:42.350 align:start position:0% and as I said I've already said this it needs<13:37:40.380> to<13:37:40.436> be<13:37:40.500> a<13:37:40.616> unique<13:37:40.916> Asm 13:37:42.350 --> 13:37:42.360 align:start position:0% needs to be a unique Asm 13:37:42.360 --> 13:37:46.370 align:start position:0% needs to be a unique Asm and<13:37:43.140> the<13:37:43.740> ASN<13:37:44.220> is<13:37:44.640> a<13:37:44.936> actually<13:37:45.300> supplied<13:37:46.140> by 13:37:46.370 --> 13:37:46.380 align:start position:0% and the ASN is a actually supplied by 13:37:46.380 --> 13:37:48.470 align:start position:0% and the ASN is a actually supplied by the<13:37:46.616> internet<13:37:46.860> assigned<13:37:47.756> numbers<13:37:47.880> Authority 13:37:48.470 --> 13:37:48.480 align:start position:0% the internet assigned numbers Authority 13:37:48.480 --> 13:37:50.630 align:start position:0% the internet assigned numbers Authority and<13:37:49.436> they'll<13:37:49.680> split<13:37:49.980> the<13:37:50.096> numbers<13:37:50.276> between 13:37:50.630 --> 13:37:50.640 align:start position:0% and they'll split the numbers between 13:37:50.640 --> 13:37:53.086 align:start position:0% and they'll split the numbers between whoever<13:37:51.060> governs<13:37:51.596> the<13:37:51.776> numbers<13:37:52.140> within<13:37:52.916> your 13:37:53.086 --> 13:37:53.096 align:start position:0% whoever governs the numbers within your 13:37:53.096 --> 13:37:54.530 align:start position:0% whoever governs the numbers within your country 13:37:54.530 --> 13:37:54.540 align:start position:0% country 13:37:54.540 --> 13:37:56.870 align:start position:0% country uh<13:37:55.200> all<13:37:55.380> organizations<13:37:56.040> within<13:37:56.520> the<13:37:56.700> network 13:37:56.870 --> 13:37:56.880 align:start position:0% uh all organizations within the network 13:37:56.880 --> 13:37:59.570 align:start position:0% uh all organizations within the network don't<13:37:57.360> need<13:37:57.596> ASN<13:37:58.320> the<13:37:58.680> Network<13:37:58.860> that<13:37:59.276> has<13:37:59.456> a 13:37:59.570 --> 13:37:59.580 align:start position:0% don't need ASN the Network that has a 13:37:59.580 --> 13:38:01.550 align:start position:0% don't need ASN the Network that has a single<13:37:59.820> connection<13:38:00.000> to<13:38:00.300> an<13:38:00.416> ISP<13:38:00.840> and<13:38:01.080> a<13:38:01.256> single 13:38:01.550 --> 13:38:01.560 align:start position:0% single connection to an ISP and a single 13:38:01.560 --> 13:38:02.630 align:start position:0% single connection to an ISP and a single prefix 13:38:02.630 --> 13:38:02.640 align:start position:0% prefix 13:38:02.640 --> 13:38:05.570 align:start position:0% prefix which<13:38:03.240> is<13:38:03.360> a<13:38:03.540> subnet<13:38:03.900> mask<13:38:04.200> doesn't<13:38:05.160> need<13:38:05.456> the 13:38:05.570 --> 13:38:05.580 align:start position:0% which is a subnet mask doesn't need the 13:38:05.580 --> 13:38:07.246 align:start position:0% which is a subnet mask doesn't need the ASM<13:38:06.060> because<13:38:06.240> the<13:38:06.480> prefix<13:38:06.776> of<13:38:06.956> that<13:38:07.140> network 13:38:07.246 --> 13:38:07.256 align:start position:0% ASM because the prefix of that network 13:38:07.256 --> 13:38:08.746 align:start position:0% ASM because the prefix of that network is<13:38:07.560> managed<13:38:07.916> by<13:38:08.096> the<13:38:08.276> internet<13:38:08.400> service 13:38:08.746 --> 13:38:08.756 align:start position:0% is managed by the internet service 13:38:08.756 --> 13:38:11.210 align:start position:0% is managed by the internet service provider<13:38:09.416> so<13:38:09.956> you<13:38:10.200> may<13:38:10.380> not<13:38:10.560> actually<13:38:10.740> need<13:38:11.096> to 13:38:11.210 --> 13:38:11.220 align:start position:0% provider so you may not actually need to 13:38:11.220 --> 13:38:13.130 align:start position:0% provider so you may not actually need to worry<13:38:11.400> about<13:38:11.640> any<13:38:11.936> of<13:38:12.060> the<13:38:12.180> exterior<13:38:12.596> routing 13:38:13.130 --> 13:38:13.140 align:start position:0% worry about any of the exterior routing 13:38:13.140 --> 13:38:15.530 align:start position:0% worry about any of the exterior routing you<13:38:13.916> could<13:38:14.040> be<13:38:14.160> really<13:38:14.340> low<13:38:14.640> SPF<13:38:15.116> all<13:38:15.300> through 13:38:15.530 --> 13:38:15.540 align:start position:0% you could be really low SPF all through 13:38:15.540 --> 13:38:18.290 align:start position:0% you could be really low SPF all through your<13:38:15.720> network<13:38:16.040> send<13:38:17.040> your<13:38:17.456> traffic<13:38:17.820> to<13:38:18.116> your 13:38:18.290 --> 13:38:18.300 align:start position:0% your network send your traffic to your 13:38:18.300 --> 13:38:20.266 align:start position:0% your network send your traffic to your internet<13:38:18.416> service<13:38:18.776> provider<13:38:19.436> and<13:38:19.860> let<13:38:20.096> that 13:38:20.266 --> 13:38:20.276 align:start position:0% internet service provider and let that 13:38:20.276 --> 13:38:22.606 align:start position:0% internet service provider and let that let<13:38:20.700> them<13:38:20.880> take<13:38:21.116> care<13:38:21.300> of<13:38:21.480> any<13:38:21.776> exterior 13:38:22.606 --> 13:38:22.616 align:start position:0% let them take care of any exterior 13:38:22.616 --> 13:38:24.606 align:start position:0% let them take care of any exterior routing 13:38:24.606 --> 13:38:24.616 align:start position:0% routing 13:38:24.616 --> 13:38:28.246 align:start position:0% routing bgp<13:38:25.756> exterior<13:38:26.756> Gateway<13:38:27.116> protocol<13:38:27.596> and<13:38:28.080> it 13:38:28.246 --> 13:38:28.256 align:start position:0% bgp exterior Gateway protocol and it 13:38:28.256 --> 13:38:30.710 align:start position:0% bgp exterior Gateway protocol and it routes<13:38:28.680> packets<13:38:29.040> between<13:38:29.276> the<13:38:29.640> Asus<13:38:30.416> which 13:38:30.710 --> 13:38:30.720 align:start position:0% routes packets between the Asus which 13:38:30.720 --> 13:38:33.050 align:start position:0% routes packets between the Asus which I've<13:38:31.080> already<13:38:31.256> said<13:38:31.500> here<13:38:31.740> is<13:38:32.340> an<13:38:32.520> example<13:38:32.820> of 13:38:33.050 --> 13:38:33.060 align:start position:0% I've already said here is an example of 13:38:33.060 --> 13:38:34.906 align:start position:0% I've already said here is an example of some<13:38:33.416> different<13:38:33.596> ases<13:38:34.200> and<13:38:34.436> on<13:38:34.560> the<13:38:34.680> bottom 13:38:34.906 --> 13:38:34.916 align:start position:0% some different ases and on the bottom 13:38:34.916 --> 13:38:36.350 align:start position:0% some different ases and on the bottom you've<13:38:35.160> got<13:38:35.276> as1 13:38:36.350 --> 13:38:36.360 align:start position:0% you've got as1 13:38:36.360 --> 13:38:40.086 align:start position:0% you've got as1 which<13:38:37.020> has<13:38:37.200> the<13:38:38.040> um<13:38:38.096> prefix 13:38:40.086 --> 13:38:40.096 align:start position:0% which has the um prefix 13:38:40.096 --> 13:38:45.890 align:start position:0% which has the um prefix 192.020<13:38:41.240> and<13:38:42.240> the<13:38:42.840> subnet<13:38:43.560> mask<13:38:43.800> of<13:38:44.220> Slash<13:38:44.520> 24. 13:38:45.890 --> 13:38:45.900 align:start position:0% 192.020 and the subnet mask of Slash 24. 13:38:45.900 --> 13:38:49.070 align:start position:0% 192.020 and the subnet mask of Slash 24. 24<13:38:46.380> bits 13:38:49.070 --> 13:38:49.080 align:start position:0% 24 bits 13:38:49.080 --> 13:38:52.670 align:start position:0% 24 bits according<13:38:49.740> to<13:38:49.860> the<13:38:49.980> RFC<13:38:50.580> and<13:38:51.540> bgp<13:38:52.140> is<13:38:52.500> an 13:38:52.670 --> 13:38:52.680 align:start position:0% according to the RFC and bgp is an 13:38:52.680 --> 13:38:54.470 align:start position:0% according to the RFC and bgp is an inter-autonomous<13:38:53.400> system<13:38:53.580> router<13:38:54.116> protocol 13:38:54.470 --> 13:38:54.480 align:start position:0% inter-autonomous system router protocol 13:38:54.480 --> 13:38:57.766 align:start position:0% inter-autonomous system router protocol it<13:38:55.320> actually<13:38:55.436> uses<13:38:55.916> TCP<13:38:56.640> so<13:38:56.880> it<13:38:57.060> uses<13:38:57.596> a 13:38:57.766 --> 13:38:57.776 align:start position:0% it actually uses TCP so it uses a 13:38:57.776 --> 13:39:00.290 align:start position:0% it actually uses TCP so it uses a reliable<13:38:58.140> transport<13:38:58.680> method<13:38:59.160> as<13:39:00.000> opposed<13:39:00.240> to 13:39:00.290 --> 13:39:00.300 align:start position:0% reliable transport method as opposed to 13:39:00.300 --> 13:39:03.230 align:start position:0% reliable transport method as opposed to other<13:39:00.680> protocols<13:39:01.680> it<13:39:02.096> listens<13:39:02.520> on<13:39:02.640> TC<13:39:03.000> Port 13:39:03.230 --> 13:39:03.240 align:start position:0% other protocols it listens on TC Port 13:39:03.240 --> 13:39:05.870 align:start position:0% other protocols it listens on TC Port what<13:39:03.660> TCP<13:39:04.256> Port<13:39:04.436> 179 13:39:05.870 --> 13:39:05.880 align:start position:0% what TCP Port 179 13:39:05.880 --> 13:39:08.086 align:start position:0% what TCP Port 179 and<13:39:06.360> you<13:39:06.480> can<13:39:06.596> see<13:39:06.660> we've<13:39:06.956> caught<13:39:07.320> a<13:39:07.680> captured 13:39:08.086 --> 13:39:08.096 align:start position:0% and you can see we've caught a captured 13:39:08.096 --> 13:39:11.330 align:start position:0% and you can see we've caught a captured a<13:39:08.276> bgp<13:39:08.756> message<13:39:09.060> with<13:39:09.480> a<13:39:10.080> a<13:39:10.616> packet<13:39:11.040> capture 13:39:11.330 --> 13:39:11.340 align:start position:0% a bgp message with a a packet capture 13:39:11.340 --> 13:39:13.190 align:start position:0% a bgp message with a a packet capture program<13:39:11.580> looks<13:39:12.060> like<13:39:12.180> Wireshark<13:39:12.720> there's<13:39:13.020> an 13:39:13.190 --> 13:39:13.200 align:start position:0% program looks like Wireshark there's an 13:39:13.200 --> 13:39:14.390 align:start position:0% program looks like Wireshark there's an open<13:39:13.256> message<13:39:13.616> and<13:39:13.916> you<13:39:14.040> can<13:39:14.160> see<13:39:14.220> the 13:39:14.390 --> 13:39:14.400 align:start position:0% open message and you can see the 13:39:14.400 --> 13:39:17.330 align:start position:0% open message and you can see the destination<13:39:14.820> Port<13:39:15.116> there<13:39:15.480> is<13:39:16.080> 179<13:39:16.800> and<13:39:17.160> it's 13:39:17.330 --> 13:39:17.340 align:start position:0% destination Port there is 179 and it's 13:39:17.340 --> 13:39:21.470 align:start position:0% destination Port there is 179 and it's using<13:39:17.640> TCP 13:39:21.470 --> 13:39:21.480 align:start position:0% 13:39:21.480 --> 13:39:23.570 align:start position:0% current<13:39:21.956> version<13:39:22.256> is<13:39:22.560> four<13:39:22.860> if<13:39:23.220> you<13:39:23.400> could 13:39:23.570 --> 13:39:23.580 align:start position:0% current version is four if you could 13:39:23.580 --> 13:39:26.570 align:start position:0% current version is four if you could look<13:39:24.020> further<13:39:25.020> down<13:39:25.200> inside<13:39:25.436> the<13:39:25.740> bgp<13:39:26.160> packet 13:39:26.570 --> 13:39:26.580 align:start position:0% look further down inside the bgp packet 13:39:26.580 --> 13:39:29.266 align:start position:0% look further down inside the bgp packet it<13:39:27.116> says<13:39:27.416> version<13:39:27.660> four 13:39:29.266 --> 13:39:29.276 align:start position:0% it says version four 13:39:29.276 --> 13:39:33.946 align:start position:0% it says version four that's<13:39:29.700> the<13:39:29.880> current<13:39:30.000> version<13:39:30.300> in<13:39:30.596> use<13:39:30.776> today 13:39:33.946 --> 13:39:33.956 align:start position:0% 13:39:33.956 --> 13:39:35.926 align:start position:0% all<13:39:34.320> right<13:39:34.500> so<13:39:34.616> CompTIA<13:39:35.220> they<13:39:35.580> actually<13:39:35.700> list 13:39:35.926 --> 13:39:35.936 align:start position:0% all right so CompTIA they actually list 13:39:35.936 --> 13:39:38.150 align:start position:0% all right so CompTIA they actually list it<13:39:36.180> as<13:39:36.360> a<13:39:36.540> hybrid<13:39:36.840> protocol<13:39:37.320> I'm<13:39:37.680> not<13:39:37.860> sure<13:39:37.916> why 13:39:38.150 --> 13:39:38.160 align:start position:0% it as a hybrid protocol I'm not sure why 13:39:38.160 --> 13:39:39.406 align:start position:0% it as a hybrid protocol I'm not sure why they<13:39:38.340> do<13:39:38.520> that 13:39:39.406 --> 13:39:39.416 align:start position:0% they do that 13:39:39.416 --> 13:39:42.650 align:start position:0% they do that it's<13:39:39.900> a<13:39:40.140> path<13:39:40.320> Vector<13:39:40.860> routing<13:39:41.276> protocol 13:39:42.650 --> 13:39:42.660 align:start position:0% it's a path Vector routing protocol 13:39:42.660 --> 13:39:46.370 align:start position:0% it's a path Vector routing protocol so<13:39:43.380> you<13:39:43.616> can<13:39:43.740> see<13:39:43.916> the<13:39:44.220> paths<13:39:44.640> here<13:39:45.020> as1<13:39:46.020> at<13:39:46.256> the 13:39:46.370 --> 13:39:46.380 align:start position:0% so you can see the paths here as1 at the 13:39:46.380 --> 13:39:50.390 align:start position:0% so you can see the paths here as1 at the bottom<13:39:46.740> is<13:39:47.640> sending<13:39:48.116> the<13:39:48.740> nlris<13:39:49.740> network 13:39:50.390 --> 13:39:50.400 align:start position:0% bottom is sending the nlris network 13:39:50.400 --> 13:39:53.330 align:start position:0% bottom is sending the nlris network layer<13:39:50.820> reachability<13:39:51.360> information<13:39:52.096> I.E<13:39:53.096> how 13:39:53.330 --> 13:39:53.340 align:start position:0% layer reachability information I.E how 13:39:53.340 --> 13:39:55.010 align:start position:0% layer reachability information I.E how to<13:39:53.456> get<13:39:53.640> to<13:39:53.756> that<13:39:54.000> particular<13:39:54.300> Network<13:39:54.660> and 13:39:55.010 --> 13:39:55.020 align:start position:0% to get to that particular Network and 13:39:55.020 --> 13:39:56.746 align:start position:0% to get to that particular Network and prefix 13:39:56.746 --> 13:39:56.756 align:start position:0% prefix 13:39:56.756 --> 13:40:00.290 align:start position:0% prefix router<13:39:57.596> 3<13:39:57.840> appends<13:39:58.436> its<13:39:58.740> path<13:39:59.040> which<13:39:59.456> is<13:39:59.580> as3 13:40:00.290 --> 13:40:00.300 align:start position:0% router 3 appends its path which is as3 13:40:00.300 --> 13:40:02.390 align:start position:0% router 3 appends its path which is as3 and<13:40:01.020> then<13:40:01.256> when<13:40:01.560> the 13:40:02.390 --> 13:40:02.400 align:start position:0% and then when the 13:40:02.400 --> 13:40:03.650 align:start position:0% and then when the um 13:40:03.650 --> 13:40:03.660 align:start position:0% um 13:40:03.660 --> 13:40:04.926 align:start position:0% um network 13:40:04.926 --> 13:40:04.936 align:start position:0% network 13:40:04.936 --> 13:40:09.170 align:start position:0% network 192020<13:40:06.140> is<13:40:07.140> sent<13:40:07.380> to<13:40:07.560> as5<13:40:08.220> it's<13:40:08.520> appended<13:40:09.000> with 13:40:09.170 --> 13:40:09.180 align:start position:0% 192020 is sent to as5 it's appended with 13:40:09.180 --> 13:40:11.266 align:start position:0% 192020 is sent to as5 it's appended with the<13:40:09.360> paths<13:40:09.776> four<13:40:10.020> three<13:40:10.320> and<13:40:10.500> one 13:40:11.266 --> 13:40:11.276 align:start position:0% the paths four three and one 13:40:11.276 --> 13:40:13.970 align:start position:0% the paths four three and one as<13:40:11.820> a<13:40:12.000> reply<13:40:12.360> is<13:40:12.596> sent<13:40:12.776> the<13:40:13.320> different<13:40:13.500> paths 13:40:13.970 --> 13:40:13.980 align:start position:0% as a reply is sent the different paths 13:40:13.980 --> 13:40:17.390 align:start position:0% as a reply is sent the different paths are<13:40:14.096> removed<13:40:14.456> so<13:40:14.580> as4<13:40:15.300> will<13:40:16.200> remove<13:40:16.500> path<13:40:17.160> four 13:40:17.390 --> 13:40:17.400 align:start position:0% are removed so as4 will remove path four 13:40:17.400 --> 13:40:19.490 align:start position:0% are removed so as4 will remove path four and<13:40:17.640> send<13:40:17.820> it<13:40:17.936> to<13:40:18.060> three<13:40:18.300> we'll<13:40:18.776> remove<13:40:19.080> three 13:40:19.490 --> 13:40:19.500 align:start position:0% and send it to three we'll remove three 13:40:19.500 --> 13:40:24.650 align:start position:0% and send it to three we'll remove three and<13:40:20.220> back<13:40:20.400> over<13:40:20.580> to<13:40:20.820> one 13:40:24.650 --> 13:40:24.660 align:start position:0% 13:40:24.660 --> 13:40:26.926 align:start position:0% all<13:40:25.140> right<13:40:25.320> so<13:40:25.436> we've<13:40:25.616> covered<13:40:25.980> an<13:40:26.580> overview 13:40:26.926 --> 13:40:26.936 align:start position:0% all right so we've covered an overview 13:40:26.936 --> 13:40:29.746 align:start position:0% all right so we've covered an overview of<13:40:27.180> dynamic<13:40:27.720> protocols<13:40:28.436> interior<13:40:29.160> routing 13:40:29.746 --> 13:40:29.756 align:start position:0% of dynamic protocols interior routing 13:40:29.756 --> 13:40:33.766 align:start position:0% of dynamic protocols interior routing protocols<13:40:30.480> what<13:40:31.200> an<13:40:31.380> as<13:40:31.616> is<13:40:31.980> bgp<13:40:32.756> that's<13:40:33.540> all 13:40:33.766 --> 13:40:33.776 align:start position:0% protocols what an as is bgp that's all 13:40:33.776 --> 13:40:40.650 align:start position:0% protocols what an as is bgp that's all for<13:40:33.956> now<13:40:34.200> thanks<13:40:34.616> for<13:40:34.740> watching 13:40:40.650 --> 13:40:40.660 align:start position:0% 13:40:40.660 --> 13:40:57.050 align:start position:0% [Music] 13:40:57.050 --> 13:40:57.060 align:start position:0% 13:40:57.060 --> 13:40:59.746 align:start position:0% log<13:40:57.360> into<13:40:57.596> module<13:40:58.020> 8<13:40:58.200> lesson<13:40:58.616> 4B<13:40:59.096> routing 13:40:59.746 --> 13:40:59.756 align:start position:0% log into module 8 lesson 4B routing 13:40:59.756 --> 13:41:01.550 align:start position:0% log into module 8 lesson 4B routing loops 13:41:01.550 --> 13:41:01.560 align:start position:0% loops 13:41:01.560 --> 13:41:03.650 align:start position:0% loops but<13:41:02.040> look<13:41:02.220> at<13:41:02.340> what<13:41:02.456> a<13:41:02.640> writing<13:41:02.936> loop<13:41:03.180> is<13:41:03.360> and 13:41:03.650 --> 13:41:03.660 align:start position:0% but look at what a writing loop is and 13:41:03.660 --> 13:41:05.510 align:start position:0% but look at what a writing loop is and distance<13:41:03.776> Vector<13:41:04.320> writing<13:41:04.740> protocols 13:41:05.510 --> 13:41:05.520 align:start position:0% distance Vector writing protocols 13:41:05.520 --> 13:41:08.810 align:start position:0% distance Vector writing protocols splitter<13:41:05.936> Eisen<13:41:06.680> and<13:41:07.680> poison<13:41:07.860> reverse<13:41:08.456> which 13:41:08.810 --> 13:41:08.820 align:start position:0% splitter Eisen and poison reverse which 13:41:08.820 --> 13:41:10.606 align:start position:0% splitter Eisen and poison reverse which are<13:41:09.000> there<13:41:09.240> a<13:41:09.540> couple<13:41:09.660> of<13:41:09.776> the<13:41:09.956> solutions<13:41:10.256> to 13:41:10.606 --> 13:41:10.616 align:start position:0% are there a couple of the solutions to 13:41:10.616 --> 13:41:11.630 align:start position:0% are there a couple of the solutions to prevent 13:41:11.630 --> 13:41:11.640 align:start position:0% prevent 13:41:11.640 --> 13:41:16.246 align:start position:0% prevent routing<13:41:12.480> loops<13:41:12.840> on<13:41:13.140> a<13:41:13.380> network<13:41:13.800> layer<13:41:14.640> 3<13:41:14.820> loops 13:41:16.246 --> 13:41:16.256 align:start position:0% routing loops on a network layer 3 loops 13:41:16.256 --> 13:41:18.406 align:start position:0% routing loops on a network layer 3 loops so<13:41:16.800> writing<13:41:17.400> Loop<13:41:17.640> is<13:41:17.820> a<13:41:17.936> network<13:41:18.116> problem 13:41:18.406 --> 13:41:18.416 align:start position:0% so writing Loop is a network problem 13:41:18.416 --> 13:41:20.570 align:start position:0% so writing Loop is a network problem where<13:41:18.660> a<13:41:18.776> pucky<13:41:18.956> gets<13:41:19.256> routed<13:41:19.616> between<13:41:19.800> two<13:41:20.400> or 13:41:20.570 --> 13:41:20.580 align:start position:0% where a pucky gets routed between two or 13:41:20.580 --> 13:41:22.670 align:start position:0% where a pucky gets routed between two or more<13:41:20.756> routers<13:41:21.240> endlessly 13:41:22.670 --> 13:41:22.680 align:start position:0% more routers endlessly 13:41:22.680 --> 13:41:24.766 align:start position:0% more routers endlessly now<13:41:23.160> this<13:41:23.400> is<13:41:23.520> a<13:41:23.756> different<13:41:23.936> solution<13:41:24.416> to 13:41:24.766 --> 13:41:24.776 align:start position:0% now this is a different solution to 13:41:24.776 --> 13:41:28.670 align:start position:0% now this is a different solution to layer<13:41:25.436> 2<13:41:26.240> Loops<13:41:27.240> where<13:41:27.660> we<13:41:27.956> have<13:41:28.080> a<13:41:28.256> spanning 13:41:28.670 --> 13:41:28.680 align:start position:0% layer 2 Loops where we have a spanning 13:41:28.680 --> 13:41:30.170 align:start position:0% layer 2 Loops where we have a spanning tree<13:41:28.860> protocol 13:41:30.170 --> 13:41:30.180 align:start position:0% tree protocol 13:41:30.180 --> 13:41:32.990 align:start position:0% tree protocol and<13:41:30.840> some<13:41:31.020> Advanced<13:41:31.436> versions<13:41:31.740> of<13:41:32.040> that<13:41:32.276> that 13:41:32.990 --> 13:41:33.000 align:start position:0% and some Advanced versions of that that 13:41:33.000 --> 13:41:35.330 align:start position:0% and some Advanced versions of that that uh<13:41:33.300> there<13:41:33.720> to<13:41:33.900> stop<13:41:34.080> layer<13:41:34.800> 2<13:41:34.980> packet 13:41:35.330 --> 13:41:35.340 align:start position:0% uh there to stop layer 2 packet 13:41:35.340 --> 13:41:37.070 align:start position:0% uh there to stop layer 2 packet circulated<13:41:35.880> because<13:41:36.180> Layer<13:41:36.540> Two<13:41:36.720> packets 13:41:37.070 --> 13:41:37.080 align:start position:0% circulated because Layer Two packets 13:41:37.080 --> 13:41:41.086 align:start position:0% circulated because Layer Two packets don't<13:41:37.320> have<13:41:37.560> a<13:41:37.860> time<13:41:38.520> to<13:41:38.700> live<13:41:38.880> value 13:41:41.086 --> 13:41:41.096 align:start position:0% don't have a time to live value 13:41:41.096 --> 13:41:42.946 align:start position:0% don't have a time to live value so<13:41:41.640> this<13:41:41.820> happens<13:41:42.000> when<13:41:42.300> the<13:41:42.416> writing<13:41:42.776> table 13:41:42.946 --> 13:41:42.956 align:start position:0% so this happens when the writing table 13:41:42.956 --> 13:41:45.650 align:start position:0% so this happens when the writing table has<13:41:43.436> incorrect<13:41:43.980> information 13:41:45.650 --> 13:41:45.660 align:start position:0% has incorrect information 13:41:45.660 --> 13:41:48.710 align:start position:0% has incorrect information as<13:41:46.200> we<13:41:46.380> know<13:41:46.820> during<13:41:47.820> the<13:41:48.000> writing<13:41:48.360> process 13:41:48.710 --> 13:41:48.720 align:start position:0% as we know during the writing process 13:41:48.720 --> 13:41:50.746 align:start position:0% as we know during the writing process routers<13:41:49.500> forward<13:41:49.740> packets<13:41:50.220> to<13:41:50.456> various 13:41:50.746 --> 13:41:50.756 align:start position:0% routers forward packets to various 13:41:50.756 --> 13:41:52.730 align:start position:0% routers forward packets to various destinations<13:41:51.300> these<13:41:52.200> are<13:41:52.320> based<13:41:52.500> on<13:41:52.616> the 13:41:52.730 --> 13:41:52.740 align:start position:0% destinations these are based on the 13:41:52.740 --> 13:41:55.190 align:start position:0% destinations these are based on the entries<13:41:52.980> in<13:41:53.220> the<13:41:53.340> routing<13:41:53.700> table<13:41:53.936> now<13:41:54.900> if<13:41:55.020> one 13:41:55.190 --> 13:41:55.200 align:start position:0% entries in the routing table now if one 13:41:55.200 --> 13:41:56.926 align:start position:0% entries in the routing table now if one of<13:41:55.320> these<13:41:55.436> entries<13:41:55.740> is<13:41:56.160> incorrect<13:41:56.640> for 13:41:56.926 --> 13:41:56.936 align:start position:0% of these entries is incorrect for 13:41:56.936 --> 13:41:58.970 align:start position:0% of these entries is incorrect for example<13:41:57.180> a<13:41:57.416> network<13:41:57.596> goes<13:41:58.080> down 13:41:58.970 --> 13:41:58.980 align:start position:0% example a network goes down 13:41:58.980 --> 13:42:02.330 align:start position:0% example a network goes down then<13:41:59.456> a<13:41:59.756> routing<13:42:00.180> Loop<13:42:00.540> can<13:42:00.720> occur<13:42:01.680> so<13:42:02.096> here's 13:42:02.330 --> 13:42:02.340 align:start position:0% then a routing Loop can occur so here's 13:42:02.340 --> 13:42:05.030 align:start position:0% then a routing Loop can occur so here's an<13:42:02.456> example<13:42:02.820> I'll<13:42:03.596> go<13:42:03.776> into<13:42:03.900> more<13:42:04.140> detail<13:42:04.500> in<13:42:04.616> a 13:42:05.030 --> 13:42:05.040 align:start position:0% an example I'll go into more detail in a 13:42:05.040 --> 13:42:08.350 align:start position:0% an example I'll go into more detail in a bit<13:42:05.160> but<13:42:05.880> for<13:42:06.360> today's<13:42:06.776> advertising 13:42:08.350 --> 13:42:08.360 align:start position:0% bit but for today's advertising 13:42:08.360 --> 13:42:11.870 align:start position:0% bit but for today's advertising 192.168.20<13:42:09.436> which<13:42:10.436> advertises<13:42:11.040> out<13:42:11.276> of<13:42:11.520> both 13:42:11.870 --> 13:42:11.880 align:start position:0% 192.168.20 which advertises out of both 13:42:11.880 --> 13:42:14.990 align:start position:0% 192.168.20 which advertises out of both interfaces<13:42:12.840> there<13:42:13.140> it<13:42:13.860> goes<13:42:14.096> to<13:42:14.160> router<13:42:14.580> BM 13:42:14.990 --> 13:42:15.000 align:start position:0% interfaces there it goes to router BM 13:42:15.000 --> 13:42:17.870 align:start position:0% interfaces there it goes to router BM router<13:42:15.720> C<13:42:16.020> both<13:42:16.860> of<13:42:17.040> which<13:42:17.160> advertise<13:42:17.640> to 13:42:17.870 --> 13:42:17.880 align:start position:0% router C both of which advertise to 13:42:17.880 --> 13:42:19.310 align:start position:0% router C both of which advertise to router<13:42:18.300> a 13:42:19.310 --> 13:42:19.320 align:start position:0% router a 13:42:19.320 --> 13:42:22.550 align:start position:0% router a now<13:42:19.860> rights<13:42:20.400> array<13:42:20.580> unfortunately<13:42:21.060> has<13:42:21.660> two 13:42:22.550 --> 13:42:22.560 align:start position:0% now rights array unfortunately has two 13:42:22.560 --> 13:42:27.406 align:start position:0% now rights array unfortunately has two ways<13:42:23.300> to<13:42:24.300> send<13:42:24.480> the<13:42:24.776> packet<13:42:25.200> to<13:42:25.916> router 13:42:27.406 --> 13:42:27.416 align:start position:0% ways to send the packet to router 13:42:27.416 --> 13:42:29.870 align:start position:0% ways to send the packet to router um<13:42:27.540> or<13:42:28.020> to<13:42:28.200> to<13:42:28.560> paths<13:42:29.040> to<13:42:29.160> see 13:42:29.870 --> 13:42:29.880 align:start position:0% um or to to paths to see 13:42:29.880 --> 13:42:33.290 align:start position:0% um or to to paths to see uh<13:42:30.560> 192.16820<13:42:31.560> which<13:42:32.160> isn't<13:42:32.520> necessarily<13:42:33.060> a 13:42:33.290 --> 13:42:33.300 align:start position:0% uh 192.16820 which isn't necessarily a 13:42:33.300 --> 13:42:36.470 align:start position:0% uh 192.16820 which isn't necessarily a problem<13:42:33.560> however<13:42:34.560> what<13:42:34.860> router<13:42:35.340> a<13:42:35.520> does 13:42:36.470 --> 13:42:36.480 align:start position:0% problem however what router a does 13:42:36.480 --> 13:42:38.630 align:start position:0% problem however what router a does advertised<13:42:37.436> the<13:42:37.560> fact<13:42:37.680> that<13:42:37.800> it<13:42:37.980> knows<13:42:38.340> how<13:42:38.520> to 13:42:38.630 --> 13:42:38.640 align:start position:0% advertised the fact that it knows how to 13:42:38.640 --> 13:42:41.150 align:start position:0% advertised the fact that it knows how to get<13:42:38.756> to<13:42:38.936> that<13:42:39.180> Network<13:42:39.360> to<13:42:39.900> router<13:42:40.380> C<13:42:40.560> to 13:42:41.150 --> 13:42:41.160 align:start position:0% get to that Network to router C to 13:42:41.160 --> 13:42:43.490 align:start position:0% get to that Network to router C to router<13:42:41.580> B<13:42:41.756> which<13:42:42.540> then<13:42:42.776> forwards<13:42:43.200> it<13:42:43.320> to 13:42:43.490 --> 13:42:43.500 align:start position:0% router B which then forwards it to 13:42:43.500 --> 13:42:47.690 align:start position:0% router B which then forwards it to router<13:42:44.040> D<13:42:44.520> now<13:42:45.480> router<13:42:46.020> D<13:42:46.256> is<13:42:47.160> hearing<13:42:47.520> from 13:42:47.690 --> 13:42:47.700 align:start position:0% router D now router D is hearing from 13:42:47.700 --> 13:42:49.850 align:start position:0% router D now router D is hearing from other<13:42:47.880> routers<13:42:48.416> that<13:42:48.776> they<13:42:49.020> know<13:42:49.200> or<13:42:49.680> they 13:42:49.850 --> 13:42:49.860 align:start position:0% other routers that they know or they 13:42:49.860 --> 13:42:54.766 align:start position:0% other routers that they know or they have<13:42:50.040> a<13:42:50.276> route<13:42:50.580> to<13:42:51.540> get<13:42:51.720> to<13:42:52.020> 192.1682.0 13:42:54.766 --> 13:42:54.776 align:start position:0% have a route to get to 192.1682.0 13:42:54.776 --> 13:42:58.790 align:start position:0% have a route to get to 192.1682.0 now<13:42:55.256> if<13:42:55.500> that<13:42:55.680> Network<13:42:55.916> goes<13:42:56.520> down<13:42:56.900> router<13:42:57.900> d 13:42:58.790 --> 13:42:58.800 align:start position:0% now if that Network goes down router d 13:42:58.800 --> 13:43:01.390 align:start position:0% now if that Network goes down router d will<13:42:59.276> be<13:42:59.456> sending<13:42:59.756> packets<13:43:00.116> to<13:43:00.416> that<13:43:00.660> Network 13:43:01.390 --> 13:43:01.400 align:start position:0% will be sending packets to that Network 13:43:01.400 --> 13:43:04.490 align:start position:0% will be sending packets to that Network either<13:43:02.400> to<13:43:02.700> router<13:43:03.116> C<13:43:03.300> or<13:43:03.596> router<13:43:04.020> B<13:43:04.200> because 13:43:04.490 --> 13:43:04.500 align:start position:0% either to router C or router B because 13:43:04.500 --> 13:43:07.550 align:start position:0% either to router C or router B because it's<13:43:04.860> heard<13:43:05.220> from<13:43:05.580> those<13:43:05.880> routers<13:43:06.720> that<13:43:07.436> it 13:43:07.550 --> 13:43:07.560 align:start position:0% it's heard from those routers that it 13:43:07.560 --> 13:43:09.710 align:start position:0% it's heard from those routers that it knows<13:43:07.860> how<13:43:08.040> to<13:43:08.160> reach<13:43:08.456> that<13:43:08.700> Network 13:43:09.710 --> 13:43:09.720 align:start position:0% knows how to reach that Network 13:43:09.720 --> 13:43:13.130 align:start position:0% knows how to reach that Network so<13:43:10.080> this<13:43:10.320> is<13:43:10.436> how<13:43:10.800> our<13:43:11.096> writing<13:43:11.700> Loop<13:43:12.060> can 13:43:13.130 --> 13:43:13.140 align:start position:0% so this is how our writing Loop can 13:43:13.140 --> 13:43:15.710 align:start position:0% so this is how our writing Loop can um<13:43:13.256> cause<13:43:13.860> havoc<13:43:14.276> on<13:43:14.456> your<13:43:14.640> network 13:43:15.710 --> 13:43:15.720 align:start position:0% um cause havoc on your network 13:43:15.720 --> 13:43:17.630 align:start position:0% um cause havoc on your network so<13:43:16.080> go<13:43:16.256> go<13:43:16.436> to<13:43:16.680> a<13:43:16.800> bit<13:43:16.916> more<13:43:17.040> detail<13:43:17.400> with 13:43:17.630 --> 13:43:17.640 align:start position:0% so go go to a bit more detail with 13:43:17.640 --> 13:43:19.670 align:start position:0% so go go to a bit more detail with another<13:43:17.756> example<13:43:18.360> here<13:43:18.660> obviously<13:43:19.380> have<13:43:19.500> a 13:43:19.670 --> 13:43:19.680 align:start position:0% another example here obviously have a 13:43:19.680 --> 13:43:21.730 align:start position:0% another example here obviously have a detrimental<13:43:20.220> effect 13:43:21.730 --> 13:43:21.740 align:start position:0% detrimental effect 13:43:21.740 --> 13:43:25.010 align:start position:0% detrimental effect increases<13:43:22.740> packet<13:43:23.220> loss<13:43:23.640> utilization<13:43:24.596> of<13:43:24.900> the 13:43:25.010 --> 13:43:25.020 align:start position:0% increases packet loss utilization of the 13:43:25.020 --> 13:43:27.530 align:start position:0% increases packet loss utilization of the links<13:43:25.320> CPU<13:43:26.096> utilization<13:43:26.700> on<13:43:27.000> your<13:43:27.116> routers 13:43:27.530 --> 13:43:27.540 align:start position:0% links CPU utilization on your routers 13:43:27.540 --> 13:43:29.446 align:start position:0% links CPU utilization on your routers because<13:43:27.720> it<13:43:27.840> has<13:43:28.020> to<13:43:28.200> process 13:43:29.446 --> 13:43:29.456 align:start position:0% because it has to process 13:43:29.456 --> 13:43:32.926 align:start position:0% because it has to process every<13:43:30.300> time<13:43:30.540> the<13:43:30.776> packet's<13:43:31.256> received 13:43:32.926 --> 13:43:32.936 align:start position:0% every time the packet's received 13:43:32.936 --> 13:43:36.170 align:start position:0% every time the packet's received so<13:43:33.720> in<13:43:34.200> distance<13:43:34.380> Vector<13:43:35.040> protocols<13:43:35.756> slow 13:43:36.170 --> 13:43:36.180 align:start position:0% so in distance Vector protocols slow 13:43:36.180 --> 13:43:38.630 align:start position:0% so in distance Vector protocols slow convergence<13:43:36.720> causes<13:43:37.200> routing<13:43:37.680> Loops<13:43:38.096> this<13:43:38.580> is 13:43:38.630 --> 13:43:38.640 align:start position:0% convergence causes routing Loops this is 13:43:38.640 --> 13:43:41.266 align:start position:0% convergence causes routing Loops this is when<13:43:38.880> other<13:43:39.416> parts<13:43:39.660> of<13:43:39.840> the<13:43:40.020> network<13:43:40.276> are 13:43:41.266 --> 13:43:41.276 align:start position:0% when other parts of the network are 13:43:41.276 --> 13:43:43.490 align:start position:0% when other parts of the network are stabilizing<13:43:42.060> their<13:43:42.360> routing<13:43:42.720> tables<13:43:43.080> slower 13:43:43.490 --> 13:43:43.500 align:start position:0% stabilizing their routing tables slower 13:43:43.500 --> 13:43:46.070 align:start position:0% stabilizing their routing tables slower than<13:43:44.040> other<13:43:44.340> parts<13:43:44.520> of<13:43:44.700> the<13:43:44.880> network 13:43:46.070 --> 13:43:46.080 align:start position:0% than other parts of the network 13:43:46.080 --> 13:43:48.350 align:start position:0% than other parts of the network any<13:43:46.740> change<13:43:46.980> in<13:43:47.160> the<13:43:47.276> network<13:43:47.400> is<13:43:47.756> updated<13:43:48.116> in 13:43:48.350 --> 13:43:48.360 align:start position:0% any change in the network is updated in 13:43:48.360 --> 13:43:51.470 align:start position:0% any change in the network is updated in the<13:43:48.540> writing<13:43:48.840> tables 13:43:51.470 --> 13:43:51.480 align:start position:0% 13:43:51.480 --> 13:43:53.990 align:start position:0% so<13:43:52.020> during<13:43:52.320> the<13:43:52.560> process<13:43:52.860> the<13:43:53.276> routing<13:43:53.640> tables 13:43:53.990 --> 13:43:54.000 align:start position:0% so during the process the routing tables 13:43:54.000 --> 13:43:57.230 align:start position:0% so during the process the routing tables have<13:43:54.240> inconsistent<13:43:55.140> entries<13:43:55.936> due<13:43:56.936> to<13:43:57.060> slow 13:43:57.230 --> 13:43:57.240 align:start position:0% have inconsistent entries due to slow 13:43:57.240 --> 13:43:58.790 align:start position:0% have inconsistent entries due to slow convergence<13:43:57.900> this<13:43:58.200> could<13:43:58.380> be<13:43:58.500> due<13:43:58.616> to 13:43:58.790 --> 13:43:58.800 align:start position:0% convergence this could be due to 13:43:58.800 --> 13:44:01.670 align:start position:0% convergence this could be due to bandwidth<13:43:59.340> or<13:43:59.456> pros<13:44:00.060> and<13:44:00.416> processing<13:44:01.140> speeds 13:44:01.670 --> 13:44:01.680 align:start position:0% bandwidth or pros and processing speeds 13:44:01.680 --> 13:44:04.730 align:start position:0% bandwidth or pros and processing speeds on<13:44:01.916> your<13:44:02.220> router 13:44:04.730 --> 13:44:04.740 align:start position:0% on your router 13:44:04.740 --> 13:44:06.470 align:start position:0% on your router the<13:44:05.276> network<13:44:05.400> is<13:44:05.640> said<13:44:05.820> to<13:44:06.000> have<13:44:06.116> converged 13:44:06.470 --> 13:44:06.480 align:start position:0% the network is said to have converged 13:44:06.480 --> 13:44:08.266 align:start position:0% the network is said to have converged when<13:44:06.660> all<13:44:06.840> writing<13:44:07.200> tables<13:44:07.560> are<13:44:07.740> consistent 13:44:08.266 --> 13:44:08.276 align:start position:0% when all writing tables are consistent 13:44:08.276 --> 13:44:10.790 align:start position:0% when all writing tables are consistent so<13:44:09.000> this<13:44:09.180> means<13:44:09.480> every<13:44:09.720> router's<13:44:10.320> got<13:44:10.436> the 13:44:10.790 --> 13:44:10.800 align:start position:0% so this means every router's got the 13:44:10.800 --> 13:44:12.586 align:start position:0% so this means every router's got the same<13:44:10.980> picture<13:44:11.276> of<13:44:11.580> the<13:44:11.700> network<13:44:11.880> and<13:44:12.360> they<13:44:12.480> all 13:44:12.586 --> 13:44:12.596 align:start position:0% same picture of the network and they all 13:44:12.596 --> 13:44:16.130 align:start position:0% same picture of the network and they all agree<13:44:12.900> on<13:44:13.140> which<13:44:13.320> networks<13:44:13.860> are<13:44:13.980> where 13:44:16.130 --> 13:44:16.140 align:start position:0% agree on which networks are where 13:44:16.140 --> 13:44:18.350 align:start position:0% agree on which networks are where so<13:44:16.680> here<13:44:16.860> we've<13:44:17.040> got<13:44:17.160> router<13:44:17.640> C<13:44:17.756> advertising 13:44:18.350 --> 13:44:18.360 align:start position:0% so here we've got router C advertising 13:44:18.360 --> 13:44:22.070 align:start position:0% so here we've got router C advertising the<13:44:18.900> 1011<13:44:19.860> Network 13:44:22.070 --> 13:44:22.080 align:start position:0% the 1011 Network 13:44:22.080 --> 13:44:24.106 align:start position:0% the 1011 Network when<13:44:22.380> the<13:44:22.560> net<13:44:22.680> was<13:44:22.916> converged<13:44:23.400> all<13:44:23.640> routers 13:44:24.106 --> 13:44:24.116 align:start position:0% when the net was converged all routers 13:44:24.116 --> 13:44:26.210 align:start position:0% when the net was converged all routers will<13:44:24.360> agree<13:44:24.720> that<13:44:25.020> that<13:44:25.140> Network<13:44:25.380> exists<13:44:26.040> and 13:44:26.210 --> 13:44:26.220 align:start position:0% will agree that that Network exists and 13:44:26.220 --> 13:44:28.550 align:start position:0% will agree that that Network exists and they<13:44:26.520> will<13:44:26.700> agree<13:44:26.936> on<13:44:27.240> how<13:44:27.480> to<13:44:27.596> reach<13:44:28.020> that 13:44:28.550 --> 13:44:28.560 align:start position:0% they will agree on how to reach that 13:44:28.560 --> 13:44:31.130 align:start position:0% they will agree on how to reach that Network<13:44:28.820> so<13:44:29.820> a<13:44:30.060> will<13:44:30.300> send<13:44:30.480> it<13:44:30.660> out<13:44:30.840> of<13:44:31.020> the 13:44:31.130 --> 13:44:31.140 align:start position:0% Network so a will send it out of the 13:44:31.140 --> 13:44:33.106 align:start position:0% Network so a will send it out of the right<13:44:31.380> hand<13:44:31.560> interface<13:44:32.096> B<13:44:32.456> out<13:44:32.820> to<13:44:32.936> the<13:44:33.060> right 13:44:33.106 --> 13:44:33.116 align:start position:0% right hand interface B out to the right 13:44:33.116 --> 13:44:35.446 align:start position:0% right hand interface B out to the right hand<13:44:33.300> interface<13:44:33.776> and<13:44:34.020> then<13:44:34.140> C<13:44:34.500> is<13:44:35.096> directly 13:44:35.446 --> 13:44:35.456 align:start position:0% hand interface and then C is directly 13:44:35.456 --> 13:44:37.730 align:start position:0% hand interface and then C is directly connected 13:44:37.730 --> 13:44:37.740 align:start position:0% connected 13:44:37.740 --> 13:44:40.730 align:start position:0% connected now<13:44:38.520> if<13:44:39.300> this<13:44:39.480> network<13:44:39.720> goes<13:44:40.200> down<13:44:40.320> or<13:44:40.616> the 13:44:40.730 --> 13:44:40.740 align:start position:0% now if this network goes down or the 13:44:40.740 --> 13:44:42.890 align:start position:0% now if this network goes down or the interface<13:44:41.040> goes<13:44:41.520> down 13:44:42.890 --> 13:44:42.900 align:start position:0% interface goes down 13:44:42.900 --> 13:44:46.310 align:start position:0% interface goes down relative<13:44:43.616> c<13:44:43.916> will<13:44:44.700> remove<13:44:44.936> that<13:44:45.240> route<13:44:45.540> to<13:44:46.140> the 13:44:46.310 --> 13:44:46.320 align:start position:0% relative c will remove that route to the 13:44:46.320 --> 13:44:48.586 align:start position:0% relative c will remove that route to the network<13:44:46.436> from<13:44:46.800> his<13:44:46.980> writing<13:44:47.400> table<13:44:47.596> but 13:44:48.586 --> 13:44:48.596 align:start position:0% network from his writing table but 13:44:48.596 --> 13:44:50.570 align:start position:0% network from his writing table but before<13:44:48.776> this<13:44:49.080> update<13:44:49.436> is<13:44:49.616> the<13:44:49.860> center<13:44:50.040> out<13:44:50.400> to 13:44:50.570 --> 13:44:50.580 align:start position:0% before this update is the center out to 13:44:50.580 --> 13:44:51.230 align:start position:0% before this update is the center out to be 13:44:51.230 --> 13:44:51.240 align:start position:0% be 13:44:51.240 --> 13:44:53.990 align:start position:0% be router<13:44:51.956> B<13:44:52.080> sends<13:44:52.560> a<13:44:52.616> periodic<13:44:53.096> update<13:44:53.520> to 13:44:53.990 --> 13:44:54.000 align:start position:0% router B sends a periodic update to 13:44:54.000 --> 13:44:56.210 align:start position:0% router B sends a periodic update to router<13:44:54.596> C<13:44:54.776> saying<13:44:55.200> it<13:44:55.320> knows<13:44:55.560> how<13:44:55.680> to<13:44:55.800> reach 13:44:56.210 --> 13:44:56.220 align:start position:0% router C saying it knows how to reach 13:44:56.220 --> 13:45:00.710 align:start position:0% router C saying it knows how to reach the<13:44:56.880> 10110<13:44:57.596> Network 13:45:00.710 --> 13:45:00.720 align:start position:0% 13:45:00.720 --> 13:45:02.870 align:start position:0% so<13:45:01.080> this<13:45:01.256> update<13:45:01.860> makes<13:45:02.040> for<13:45:02.220> how<13:45:02.456> to<13:45:02.580> c<13:45:02.640> think 13:45:02.870 --> 13:45:02.880 align:start position:0% so this update makes for how to c think 13:45:02.880 --> 13:45:05.210 align:start position:0% so this update makes for how to c think that<13:45:03.060> router<13:45:03.416> B<13:45:03.540> has<13:45:03.956> an<13:45:04.200> alternative<13:45:04.560> path<13:45:04.980> to 13:45:05.210 --> 13:45:05.220 align:start position:0% that router B has an alternative path to 13:45:05.220 --> 13:45:06.106 align:start position:0% that router B has an alternative path to get<13:45:05.400> there 13:45:06.106 --> 13:45:06.116 align:start position:0% get there 13:45:06.116 --> 13:45:08.446 align:start position:0% get there obviously<13:45:06.956> through<13:45:07.200> some<13:45:07.500> of<13:45:07.680> the<13:45:07.800> series<13:45:08.160> of 13:45:08.446 --> 13:45:08.456 align:start position:0% obviously through some of the series of 13:45:08.456 --> 13:45:10.550 align:start position:0% obviously through some of the series of routers<13:45:09.000> it<13:45:09.360> doesn't 13:45:10.550 --> 13:45:10.560 align:start position:0% routers it doesn't 13:45:10.560 --> 13:45:12.670 align:start position:0% routers it doesn't uh<13:45:11.220> have<13:45:11.456> a<13:45:11.640> picture<13:45:11.756> of<13:45:11.936> the<13:45:12.060> entire<13:45:12.360> network 13:45:12.670 --> 13:45:12.680 align:start position:0% uh have a picture of the entire network 13:45:12.680 --> 13:45:15.106 align:start position:0% uh have a picture of the entire network and<13:45:13.680> well<13:45:14.040> it's<13:45:14.400> got<13:45:14.640> this<13:45:14.820> directly 13:45:15.106 --> 13:45:15.116 align:start position:0% and well it's got this directly 13:45:15.116 --> 13:45:16.670 align:start position:0% and well it's got this directly connected<13:45:15.540> Network<13:45:15.720> and<13:45:16.020> it<13:45:16.200> believes<13:45:16.500> what 13:45:16.670 --> 13:45:16.680 align:start position:0% connected Network and it believes what 13:45:16.680 --> 13:45:19.190 align:start position:0% connected Network and it believes what it<13:45:16.860> has<13:45:16.980> from<13:45:17.220> other<13:45:17.400> routers 13:45:19.190 --> 13:45:19.200 align:start position:0% it has from other routers 13:45:19.200 --> 13:45:22.670 align:start position:0% it has from other routers so<13:45:19.560> it<13:45:19.740> will<13:45:19.916> mark<13:45:20.220> this<13:45:20.756> uh<13:45:21.240> route<13:45:21.480> to<13:45:22.436> get<13:45:22.560> to 13:45:22.670 --> 13:45:22.680 align:start position:0% so it will mark this uh route to get to 13:45:22.680 --> 13:45:26.210 align:start position:0% so it will mark this uh route to get to the<13:45:22.860> 10110<13:45:23.456> Network<13:45:24.140> as<13:45:25.140> reachable<13:45:25.860> through 13:45:26.210 --> 13:45:26.220 align:start position:0% the 10110 Network as reachable through 13:45:26.220 --> 13:45:29.210 align:start position:0% the 10110 Network as reachable through router<13:45:26.700> B 13:45:29.210 --> 13:45:29.220 align:start position:0% 13:45:29.220 --> 13:45:31.790 align:start position:0% a<13:45:29.520> periodic<13:45:30.060> update<13:45:30.416> from<13:45:30.660> RTC<13:45:31.140> will<13:45:31.380> contain 13:45:31.790 --> 13:45:31.800 align:start position:0% a periodic update from RTC will contain 13:45:31.800 --> 13:45:33.606 align:start position:0% a periodic update from RTC will contain that<13:45:32.040> Network<13:45:32.400> which<13:45:32.880> we've<13:45:33.060> already<13:45:33.180> said 13:45:33.606 --> 13:45:33.616 align:start position:0% that Network which we've already said 13:45:33.616 --> 13:45:35.870 align:start position:0% that Network which we've already said router<13:45:34.616> B<13:45:34.740> assumes<13:45:35.096> it<13:45:35.220> knows<13:45:35.456> how<13:45:35.580> to<13:45:35.700> reach 13:45:35.870 --> 13:45:35.880 align:start position:0% router B assumes it knows how to reach 13:45:35.880 --> 13:45:39.650 align:start position:0% router B assumes it knows how to reach that<13:45:36.060> Network<13:45:36.360> mentioned<13:45:37.080> in<13:45:37.200> the<13:45:37.380> update 13:45:39.650 --> 13:45:39.660 align:start position:0% that Network mentioned in the update 13:45:39.660 --> 13:45:42.170 align:start position:0% that Network mentioned in the update now<13:45:40.200> when<13:45:40.380> router<13:45:40.800> B<13:45:40.980> receives<13:45:41.700> a<13:45:41.936> packet 13:45:42.170 --> 13:45:42.180 align:start position:0% now when router B receives a packet 13:45:42.180 --> 13:45:44.266 align:start position:0% now when router B receives a packet destined<13:45:42.540> to<13:45:42.720> the<13:45:42.776> 10110<13:45:43.380> Network<13:45:43.860> it<13:45:44.160> will 13:45:44.266 --> 13:45:44.276 align:start position:0% destined to the 10110 Network it will 13:45:44.276 --> 13:45:47.870 align:start position:0% destined to the 10110 Network it will forward<13:45:44.456> it<13:45:44.700> to<13:45:44.820> router<13:45:45.116> C 13:45:47.870 --> 13:45:47.880 align:start position:0% 13:45:47.880 --> 13:45:49.730 align:start position:0% when<13:45:48.300> Route<13:45:48.540> 60<13:45:48.776> receives<13:45:49.140> the<13:45:49.320> packet<13:45:49.560> it 13:45:49.730 --> 13:45:49.740 align:start position:0% when Route 60 receives the packet it 13:45:49.740 --> 13:45:51.350 align:start position:0% when Route 60 receives the packet it sends<13:45:50.040> it<13:45:50.096> back<13:45:50.276> to<13:45:50.456> router<13:45:50.820> B<13:45:50.936> and<13:45:51.180> this<13:45:51.300> is 13:45:51.350 --> 13:45:51.360 align:start position:0% sends it back to router B and this is 13:45:51.360 --> 13:45:53.810 align:start position:0% sends it back to router B and this is where<13:45:51.596> the<13:45:51.720> loop<13:45:51.956> is<13:45:52.140> happening 13:45:53.810 --> 13:45:53.820 align:start position:0% where the loop is happening 13:45:53.820 --> 13:45:57.290 align:start position:0% where the loop is happening so<13:45:54.300> unlike<13:45:54.720> switching<13:45:55.200> Loops<13:45:55.916> the<13:45:56.520> in<13:45:56.880> writing 13:45:57.290 --> 13:45:57.300 align:start position:0% so unlike switching Loops the in writing 13:45:57.300 --> 13:45:59.746 align:start position:0% so unlike switching Loops the in writing like<13:45:57.480> the<13:45:57.660> packet<13:45:58.080> will<13:45:58.560> last<13:45:59.096> until<13:45:59.340> the<13:45:59.580> time 13:45:59.746 --> 13:45:59.756 align:start position:0% like the packet will last until the time 13:45:59.756 --> 13:46:02.690 align:start position:0% like the packet will last until the time to<13:45:59.880> live<13:46:00.060> value<13:46:00.300> which<13:46:00.596> is<13:46:00.720> TTL<13:46:01.436> in<13:46:02.276> the<13:46:02.400> packet 13:46:02.690 --> 13:46:02.700 align:start position:0% to live value which is TTL in the packet 13:46:02.700 --> 13:46:04.730 align:start position:0% to live value which is TTL in the packet header<13:46:03.116> reaches<13:46:03.480> zero 13:46:04.730 --> 13:46:04.740 align:start position:0% header reaches zero 13:46:04.740 --> 13:46:07.730 align:start position:0% header reaches zero so<13:46:05.040> you<13:46:05.220> can<13:46:05.400> see<13:46:05.640> the<13:46:06.180> time<13:46:06.540> to<13:46:06.720> live<13:46:06.900> fields 13:46:07.730 --> 13:46:07.740 align:start position:0% so you can see the time to live fields 13:46:07.740 --> 13:46:09.470 align:start position:0% so you can see the time to live fields in<13:46:08.040> this<13:46:08.220> particular<13:46:08.580> packet<13:46:09.000> here<13:46:09.180> which<13:46:09.360> is 13:46:09.470 --> 13:46:09.480 align:start position:0% in this particular packet here which is 13:46:09.480 --> 13:46:13.030 align:start position:0% in this particular packet here which is a<13:46:09.660> bgp<13:46:10.200> packet<13:46:10.916> capture 13:46:13.030 --> 13:46:13.040 align:start position:0% a bgp packet capture 13:46:13.040 --> 13:46:15.946 align:start position:0% a bgp packet capture once<13:46:14.040> the<13:46:14.160> time<13:46:14.340> to<13:46:14.580> live<13:46:14.880> value<13:46:15.180> reaches<13:46:15.596> zero 13:46:15.946 --> 13:46:15.956 align:start position:0% once the time to live value reaches zero 13:46:15.956 --> 13:46:19.730 align:start position:0% once the time to live value reaches zero the<13:46:16.200> routers<13:46:16.800> then<13:46:17.040> drop<13:46:17.276> that<13:46:17.520> packet 13:46:19.730 --> 13:46:19.740 align:start position:0% the routers then drop that packet 13:46:19.740 --> 13:46:21.946 align:start position:0% the routers then drop that packet and<13:46:20.220> disinfected<13:46:21.060> protocols<13:46:21.596> we've<13:46:21.720> got<13:46:21.840> a 13:46:21.946 --> 13:46:21.956 align:start position:0% and disinfected protocols we've got a 13:46:21.956 --> 13:46:23.710 align:start position:0% and disinfected protocols we've got a couple<13:46:22.080> of<13:46:22.200> solutions 13:46:23.710 --> 13:46:23.720 align:start position:0% couple of solutions 13:46:23.720 --> 13:46:26.870 align:start position:0% couple of solutions splitterizing<13:46:24.720> and<13:46:24.956> poison<13:46:25.140> reverse<13:46:25.800> so<13:46:26.700> this 13:46:26.870 --> 13:46:26.880 align:start position:0% splitterizing and poison reverse so this 13:46:26.880 --> 13:46:29.746 align:start position:0% splitterizing and poison reverse so this is<13:46:27.000> split<13:46:27.360> Horizon<13:46:27.720> the<13:46:28.560> rule<13:46:28.800> is<13:46:28.916> that<13:46:29.160> if<13:46:29.520> an 13:46:29.746 --> 13:46:29.756 align:start position:0% is split Horizon the rule is that if an 13:46:29.756 --> 13:46:32.330 align:start position:0% is split Horizon the rule is that if an interface<13:46:30.116> learns<13:46:30.540> a<13:46:30.720> particular<13:46:31.080> route<13:46:31.380> it 13:46:32.330 --> 13:46:32.340 align:start position:0% interface learns a particular route it 13:46:32.340 --> 13:46:34.190 align:start position:0% interface learns a particular route it doesn't<13:46:32.456> advertise<13:46:33.000> that<13:46:33.180> route<13:46:33.416> back<13:46:33.840> out<13:46:34.020> of 13:46:34.190 --> 13:46:34.200 align:start position:0% doesn't advertise that route back out of 13:46:34.200 --> 13:46:37.010 align:start position:0% doesn't advertise that route back out of the<13:46:34.320> same<13:46:34.500> interface<13:46:35.180> now<13:46:36.180> this<13:46:36.660> causes 13:46:37.010 --> 13:46:37.020 align:start position:0% the same interface now this causes 13:46:37.020 --> 13:46:39.470 align:start position:0% the same interface now this causes problems<13:46:37.436> when<13:46:37.680> you<13:46:37.800> come<13:46:37.980> to<13:46:38.160> configure<13:46:38.820> a 13:46:39.470 --> 13:46:39.480 align:start position:0% problems when you come to configure a 13:46:39.480 --> 13:46:41.810 align:start position:0% problems when you come to configure a hub<13:46:39.660> and<13:46:39.776> spoke<13:46:40.080> Network<13:46:40.380> and<13:46:41.276> there's<13:46:41.456> ways 13:46:41.810 --> 13:46:41.820 align:start position:0% hub and spoke Network and there's ways 13:46:41.820 --> 13:46:42.890 align:start position:0% hub and spoke Network and there's ways around<13:46:41.936> it<13:46:42.116> which<13:46:42.300> we're<13:46:42.480> not<13:46:42.596> going<13:46:42.720> to<13:46:42.776> cover 13:46:42.890 --> 13:46:42.900 align:start position:0% around it which we're not going to cover 13:46:42.900 --> 13:46:46.370 align:start position:0% around it which we're not going to cover here<13:46:43.256> with<13:46:43.860> ergrp<13:46:44.820> and<13:46:45.180> ospf<13:46:45.776> in<13:46:46.080> particular 13:46:46.370 --> 13:46:46.380 align:start position:0% here with ergrp and ospf in particular 13:46:46.380 --> 13:46:48.766 align:start position:0% here with ergrp and ospf in particular you<13:46:47.340> can<13:46:47.456> change<13:46:47.640> this<13:46:47.880> rule<13:46:48.240> or<13:46:48.416> turn<13:46:48.596> this 13:46:48.766 --> 13:46:48.776 align:start position:0% you can change this rule or turn this 13:46:48.776 --> 13:46:52.010 align:start position:0% you can change this rule or turn this rule<13:46:49.140> off<13:46:49.500> and<13:46:50.456> set<13:46:51.000> of<13:46:51.240> ways<13:46:51.540> to<13:46:51.660> get<13:46:51.840> around 13:46:52.010 --> 13:46:52.020 align:start position:0% rule off and set of ways to get around 13:46:52.020 --> 13:46:54.050 align:start position:0% rule off and set of ways to get around it<13:46:52.320> so<13:46:52.436> routing<13:46:52.916> works 13:46:54.050 --> 13:46:54.060 align:start position:0% it so routing works 13:46:54.060 --> 13:46:57.766 align:start position:0% it so routing works so<13:46:54.916> router<13:46:55.916> a<13:46:56.340> learns<13:46:56.756> about<13:46:56.880> rata<13:46:57.416> C<13:46:57.540> from 13:46:57.766 --> 13:46:57.776 align:start position:0% so router a learns about rata C from 13:46:57.776 --> 13:46:59.746 align:start position:0% so router a learns about rata C from router<13:46:58.140> B<13:46:58.256> what<13:46:58.800> it<13:46:58.980> won't<13:46:59.160> do<13:46:59.400> then<13:46:59.580> is 13:46:59.746 --> 13:46:59.756 align:start position:0% router B what it won't do then is 13:46:59.756 --> 13:47:01.426 align:start position:0% router B what it won't do then is advertise<13:47:00.240> the<13:47:00.416> network<13:47:00.596> back<13:47:01.020> out<13:47:01.140> of<13:47:01.320> the 13:47:01.426 --> 13:47:01.436 align:start position:0% advertise the network back out of the 13:47:01.436 --> 13:47:03.890 align:start position:0% advertise the network back out of the same<13:47:01.560> interface<13:47:02.040> to<13:47:02.220> router<13:47:02.640> B<13:47:02.820> because<13:47:03.660> this 13:47:03.890 --> 13:47:03.900 align:start position:0% same interface to router B because this 13:47:03.900 --> 13:47:06.170 align:start position:0% same interface to router B because this would<13:47:04.080> breach<13:47:04.380> the<13:47:04.500> split<13:47:04.740> Horizon<13:47:05.040> Rule<13:47:05.520> and 13:47:06.170 --> 13:47:06.180 align:start position:0% would breach the split Horizon Rule and 13:47:06.180 --> 13:47:07.850 align:start position:0% would breach the split Horizon Rule and basically<13:47:06.540> route<13:47:06.956> and<13:47:07.320> the<13:47:07.560> networks 13:47:07.850 --> 13:47:07.860 align:start position:0% basically route and the networks 13:47:07.860 --> 13:47:10.246 align:start position:0% basically route and the networks attached<13:47:08.220> to<13:47:08.276> router<13:47:08.640> C<13:47:08.880> can<13:47:09.540> be<13:47:09.660> reached<13:47:09.956> via 13:47:10.246 --> 13:47:10.256 align:start position:0% attached to router C can be reached via 13:47:10.256 --> 13:47:12.470 align:start position:0% attached to router C can be reached via B<13:47:10.500> so<13:47:11.096> it<13:47:11.220> doesn't<13:47:11.340> need<13:47:11.580> to<13:47:11.700> be<13:47:11.820> re-advertised 13:47:12.470 --> 13:47:12.480 align:start position:0% B so it doesn't need to be re-advertised 13:47:12.480 --> 13:47:15.766 align:start position:0% B so it doesn't need to be re-advertised back<13:47:12.660> to<13:47:12.776> router<13:47:13.200> B<13:47:13.380> and<13:47:13.560> cause<13:47:13.800> confusion 13:47:15.766 --> 13:47:15.776 align:start position:0% back to router B and cause confusion 13:47:15.776 --> 13:47:18.766 align:start position:0% back to router B and cause confusion poison<13:47:16.400> reverses<13:47:17.400> a<13:47:17.640> form<13:47:17.756> of<13:47:18.000> split<13:47:18.416> Horizon 13:47:18.766 --> 13:47:18.776 align:start position:0% poison reverses a form of split Horizon 13:47:18.776 --> 13:47:22.490 align:start position:0% poison reverses a form of split Horizon it<13:47:19.500> uses<13:47:19.800> a<13:47:20.096> method<13:47:20.520> to<13:47:21.360> use<13:47:22.020> um<13:47:22.020> known<13:47:22.380> as 13:47:22.490 --> 13:47:22.500 align:start position:0% it uses a method to use um known as 13:47:22.500 --> 13:47:25.190 align:start position:0% it uses a method to use um known as route<13:47:22.916> posing<13:47:23.400> angle<13:47:23.700> poison<13:47:23.936> reverse<13:47:24.480> it 13:47:25.190 --> 13:47:25.200 align:start position:0% route posing angle poison reverse it 13:47:25.200 --> 13:47:27.170 align:start position:0% route posing angle poison reverse it allows<13:47:25.560> the<13:47:25.680> router<13:47:25.980> to<13:47:26.096> set<13:47:26.276> a<13:47:26.456> distance<13:47:26.700> to 13:47:27.170 --> 13:47:27.180 align:start position:0% allows the router to set a distance to 13:47:27.180 --> 13:47:30.350 align:start position:0% allows the router to set a distance to the<13:47:27.300> network<13:47:27.480> as<13:47:27.840> Infinity<13:47:28.456> this<13:47:29.456> is<13:47:29.580> for<13:47:29.820> the 13:47:30.350 --> 13:47:30.360 align:start position:0% the network as Infinity this is for the 13:47:30.360 --> 13:47:30.890 align:start position:0% the network as Infinity this is for the um 13:47:30.890 --> 13:47:30.900 align:start position:0% um 13:47:30.900 --> 13:47:33.946 align:start position:0% um how<13:47:31.436> many<13:47:31.616> hops<13:47:32.040> for<13:47:32.160> example<13:47:32.400> in<13:47:32.700> rip 13:47:33.946 --> 13:47:33.956 align:start position:0% how many hops for example in rip 13:47:33.956 --> 13:47:36.946 align:start position:0% how many hops for example in rip this<13:47:34.500> allows<13:47:34.800> the<13:47:35.040> network<13:47:35.936> to<13:47:36.300> converge<13:47:36.720> so 13:47:36.946 --> 13:47:36.956 align:start position:0% this allows the network to converge so 13:47:36.956 --> 13:47:39.106 align:start position:0% this allows the network to converge so perhaps<13:47:37.320> you've<13:47:37.500> had<13:47:37.616> some<13:47:37.800> instability 13:47:39.106 --> 13:47:39.116 align:start position:0% perhaps you've had some instability 13:47:39.116 --> 13:47:41.810 align:start position:0% perhaps you've had some instability the<13:47:39.596> network<13:47:39.720> attached<13:47:40.436> to<13:47:40.560> router<13:47:41.456> E<13:47:41.580> network 13:47:41.810 --> 13:47:41.820 align:start position:0% the network attached to router E network 13:47:41.820 --> 13:47:44.446 align:start position:0% the network attached to router E network 5<13:47:42.116> has<13:47:42.360> gone<13:47:42.596> down<13:47:42.776> so<13:47:43.380> router<13:47:43.860> e<13:47:44.040> will<13:47:44.276> quickly 13:47:44.446 --> 13:47:44.456 align:start position:0% 5 has gone down so router e will quickly 13:47:44.456 --> 13:47:46.550 align:start position:0% 5 has gone down so router e will quickly advertise<13:47:44.936> that<13:47:45.180> with<13:47:45.540> an<13:47:45.776> infinite<13:47:46.200> distance 13:47:46.550 --> 13:47:46.560 align:start position:0% advertise that with an infinite distance 13:47:46.560 --> 13:47:50.630 align:start position:0% advertise that with an infinite distance which<13:47:47.456> is<13:47:47.580> known<13:47:47.700> as<13:47:47.880> rat<13:47:48.240> poisoning 13:47:50.630 --> 13:47:50.640 align:start position:0% which is known as rat poisoning 13:47:50.640 --> 13:47:52.790 align:start position:0% which is known as rat poisoning so<13:47:50.936> I've<13:47:51.060> looked<13:47:51.360> at<13:47:51.416> Loops<13:47:51.900> distance<13:47:52.200> Vector 13:47:52.790 --> 13:47:52.800 align:start position:0% so I've looked at Loops distance Vector 13:47:52.800 --> 13:47:55.246 align:start position:0% so I've looked at Loops distance Vector routing<13:47:53.276> protocols<13:47:53.936> bit<13:47:54.240> Horizon<13:47:54.720> poison 13:47:55.246 --> 13:47:55.256 align:start position:0% routing protocols bit Horizon poison 13:47:55.256 --> 13:47:57.766 align:start position:0% routing protocols bit Horizon poison reverse<13:47:55.916> that's<13:47:56.640> all<13:47:56.936> for<13:47:57.116> now<13:47:57.300> thanks<13:47:57.660> for 13:47:57.766 --> 13:47:57.776 align:start position:0% reverse that's all for now thanks for 13:47:57.776 --> 13:48:03.750 align:start position:0% reverse that's all for now thanks for watching 13:48:03.750 --> 13:48:03.760 align:start position:0% 13:48:03.760 --> 13:48:11.510 align:start position:0% [Music] 13:48:11.510 --> 13:48:11.520 align:start position:0% [Music] 13:48:11.520 --> 13:48:24.550 align:start position:0% [Music] foreign 13:48:24.550 --> 13:48:24.560 align:start position:0% 13:48:24.560 --> 13:48:29.210 align:start position:0% networks<13:48:25.936> vlans<13:48:26.936> and<13:48:27.540> sohos 13:48:29.210 --> 13:48:29.220 align:start position:0% networks vlans and sohos 13:48:29.220 --> 13:48:31.370 align:start position:0% networks vlans and sohos so<13:48:29.640> we<13:48:29.756> finished<13:48:30.000> talking<13:48:30.300> about<13:48:30.596> switching 13:48:31.370 --> 13:48:31.380 align:start position:0% so we finished talking about switching 13:48:31.380 --> 13:48:34.850 align:start position:0% so we finished talking about switching and<13:48:32.040> routing<13:48:32.520> how<13:48:33.360> networks<13:48:34.320> communicate 13:48:34.850 --> 13:48:34.860 align:start position:0% and routing how networks communicate 13:48:34.860 --> 13:48:37.070 align:start position:0% and routing how networks communicate with<13:48:35.040> one<13:48:35.276> another<13:48:35.456> and<13:48:36.180> so<13:48:36.300> now<13:48:36.480> we<13:48:36.720> want<13:48:36.900> to 13:48:37.070 --> 13:48:37.080 align:start position:0% with one another and so now we want to 13:48:37.080 --> 13:48:40.190 align:start position:0% with one another and so now we want to talk<13:48:37.320> about<13:48:37.916> two<13:48:38.580> other<13:48:38.880> terms<13:48:39.480> that<13:48:39.720> we<13:48:39.840> see<13:48:39.956> a 13:48:40.190 --> 13:48:40.200 align:start position:0% talk about two other terms that we see a 13:48:40.200 --> 13:48:41.510 align:start position:0% talk about two other terms that we see a lot<13:48:40.256> when<13:48:40.500> we<13:48:40.616> talk<13:48:40.740> about<13:48:40.860> local<13:48:41.220> area 13:48:41.510 --> 13:48:41.520 align:start position:0% lot when we talk about local area 13:48:41.520 --> 13:48:43.190 align:start position:0% lot when we talk about local area networks<13:48:42.060> and<13:48:42.240> they're<13:48:42.480> important<13:48:42.900> to<13:48:43.080> know 13:48:43.190 --> 13:48:43.200 align:start position:0% networks and they're important to know 13:48:43.200 --> 13:48:45.290 align:start position:0% networks and they're important to know for<13:48:43.680> the<13:48:43.800> network<13:48:43.916> plus<13:48:44.220> exam 13:48:45.290 --> 13:48:45.300 align:start position:0% for the network plus exam 13:48:45.300 --> 13:48:48.470 align:start position:0% for the network plus exam the<13:48:45.776> first<13:48:45.956> is<13:48:46.560> called<13:48:46.800> VLAN<13:48:47.456> or<13:48:47.936> virtual 13:48:48.470 --> 13:48:48.480 align:start position:0% the first is called VLAN or virtual 13:48:48.480 --> 13:48:51.170 align:start position:0% the first is called VLAN or virtual local<13:48:48.900> area<13:48:49.200> network<13:48:49.560> it<13:48:50.340> has<13:48:50.456> to<13:48:50.640> do<13:48:50.820> with 13:48:51.170 --> 13:48:51.180 align:start position:0% local area network it has to do with 13:48:51.180 --> 13:48:54.170 align:start position:0% local area network it has to do with segmenting<13:48:51.840> a<13:48:52.616> physical<13:48:52.800> local<13:48:53.580> area<13:48:53.880> network 13:48:54.170 --> 13:48:54.180 align:start position:0% segmenting a physical local area network 13:48:54.180 --> 13:48:57.766 align:start position:0% segmenting a physical local area network into<13:48:55.140> two<13:48:55.616> or<13:48:55.800> more<13:48:56.040> virtual<13:48:56.820> or<13:48:57.300> logical 13:48:57.766 --> 13:48:57.776 align:start position:0% into two or more virtual or logical 13:48:57.776 --> 13:49:00.766 align:start position:0% into two or more virtual or logical local<13:48:58.616> area<13:48:58.916> networks<13:48:59.580> and<13:49:00.240> we're<13:49:00.416> also<13:49:00.660> going 13:49:00.766 --> 13:49:00.776 align:start position:0% local area networks and we're also going 13:49:00.776 --> 13:49:03.766 align:start position:0% local area networks and we're also going to<13:49:00.956> discuss<13:49:01.320> what<13:49:02.096> they<13:49:02.220> do<13:49:02.456> and<13:49:03.116> how<13:49:03.416> we 13:49:03.766 --> 13:49:03.776 align:start position:0% to discuss what they do and how we 13:49:03.776 --> 13:49:07.190 align:start position:0% to discuss what they do and how we Define<13:49:03.956> memberships<13:49:04.916> in<13:49:05.456> vlans<13:49:06.060> since<13:49:06.900> this 13:49:07.190 --> 13:49:07.200 align:start position:0% Define memberships in vlans since this 13:49:07.200 --> 13:49:09.946 align:start position:0% Define memberships in vlans since this is<13:49:07.320> not<13:49:07.560> a<13:49:07.916> physical<13:49:08.160> distinction<13:49:08.820> but<13:49:09.540> a 13:49:09.946 --> 13:49:09.956 align:start position:0% is not a physical distinction but a 13:49:09.956 --> 13:49:12.586 align:start position:0% is not a physical distinction but a logical<13:49:10.436> one<13:49:10.740> we're<13:49:11.580> also<13:49:11.880> going<13:49:12.060> to<13:49:12.240> discuss 13:49:12.586 --> 13:49:12.596 align:start position:0% logical one we're also going to discuss 13:49:12.596 --> 13:49:16.070 align:start position:0% logical one we're also going to discuss a<13:49:13.560> Soho<13:49:14.096> Network<13:49:14.456> also<13:49:15.360> called<13:49:15.596> a<13:49:15.900> small 13:49:16.070 --> 13:49:16.080 align:start position:0% a Soho Network also called a small 13:49:16.080 --> 13:49:18.106 align:start position:0% a Soho Network also called a small office<13:49:16.320> home<13:49:16.740> office<13:49:16.916> Network<13:49:17.340> we've 13:49:18.106 --> 13:49:18.116 align:start position:0% office home office Network we've 13:49:18.116 --> 13:49:19.550 align:start position:0% office home office Network we've probably<13:49:18.300> seen<13:49:18.596> this<13:49:18.840> term<13:49:19.020> in<13:49:19.256> the<13:49:19.380> past 13:49:19.550 --> 13:49:19.560 align:start position:0% probably seen this term in the past 13:49:19.560 --> 13:49:21.530 align:start position:0% probably seen this term in the past because<13:49:20.160> we<13:49:20.456> deal<13:49:20.700> with<13:49:20.880> it<13:49:21.000> when<13:49:21.180> we<13:49:21.360> talk 13:49:21.530 --> 13:49:21.540 align:start position:0% because we deal with it when we talk 13:49:21.540 --> 13:49:24.650 align:start position:0% because we deal with it when we talk about<13:49:22.160> Soho<13:49:23.160> routers<13:49:23.936> which<13:49:24.360> are<13:49:24.480> those 13:49:24.650 --> 13:49:24.660 align:start position:0% about Soho routers which are those 13:49:24.660 --> 13:49:26.810 align:start position:0% about Soho routers which are those routers<13:49:25.080> like<13:49:25.436> the<13:49:25.616> d-links<13:49:26.220> and<13:49:26.276> the<13:49:26.400> Linksys 13:49:26.810 --> 13:49:26.820 align:start position:0% routers like the d-links and the Linksys 13:49:26.820 --> 13:49:29.570 align:start position:0% routers like the d-links and the Linksys that<13:49:27.360> you<13:49:27.540> have<13:49:27.776> at<13:49:28.320> your<13:49:28.560> home<13:49:28.740> that<13:49:29.340> allow 13:49:29.570 --> 13:49:29.580 align:start position:0% that you have at your home that allow 13:49:29.580 --> 13:49:31.246 align:start position:0% that you have at your home that allow you<13:49:29.700> to<13:49:29.820> get<13:49:29.936> for<13:49:30.180> instance<13:49:30.416> wireless<13:49:30.720> access 13:49:31.246 --> 13:49:31.256 align:start position:0% you to get for instance wireless access 13:49:31.256 --> 13:49:33.106 align:start position:0% you to get for instance wireless access although 13:49:33.106 --> 13:49:33.116 align:start position:0% although 13:49:33.116 --> 13:49:34.906 align:start position:0% although these<13:49:33.720> provide<13:49:34.080> many<13:49:34.320> different<13:49:34.500> things 13:49:34.906 --> 13:49:34.916 align:start position:0% these provide many different things 13:49:34.916 --> 13:49:38.086 align:start position:0% these provide many different things they're<13:49:35.880> distinct<13:49:36.480> from<13:49:36.840> a<13:49:37.080> regular<13:49:37.320> router<13:49:37.740> a 13:49:38.086 --> 13:49:38.096 align:start position:0% they're distinct from a regular router a 13:49:38.096 --> 13:49:40.730 align:start position:0% they're distinct from a regular router a Soho<13:49:38.456> router<13:49:38.880> because<13:49:39.480> a<13:49:40.020> regular<13:49:40.256> router 13:49:40.730 --> 13:49:40.740 align:start position:0% Soho router because a regular router 13:49:40.740 --> 13:49:42.890 align:start position:0% Soho router because a regular router just<13:49:40.980> does<13:49:41.160> routing<13:49:41.640> whereas<13:49:42.116> a<13:49:42.240> Soho<13:49:42.540> router 13:49:42.890 --> 13:49:42.900 align:start position:0% just does routing whereas a Soho router 13:49:42.900 --> 13:49:44.926 align:start position:0% just does routing whereas a Soho router does<13:49:43.020> several<13:49:43.436> different<13:49:43.560> things<13:49:43.860> now<13:49:44.756> that's 13:49:44.926 --> 13:49:44.936 align:start position:0% does several different things now that's 13:49:44.936 --> 13:49:46.790 align:start position:0% does several different things now that's an<13:49:45.116> example<13:49:45.416> of<13:49:45.660> why<13:49:45.900> a<13:49:46.140> small<13:49:46.256> office<13:49:46.436> home 13:49:46.790 --> 13:49:46.800 align:start position:0% an example of why a small office home 13:49:46.800 --> 13:49:49.670 align:start position:0% an example of why a small office home office<13:49:47.096> is<13:49:47.880> so<13:49:48.060> such<13:49:48.360> an<13:49:48.596> important<13:49:49.020> term<13:49:49.256> when 13:49:49.670 --> 13:49:49.680 align:start position:0% office is so such an important term when 13:49:49.680 --> 13:49:51.650 align:start position:0% office is so such an important term when it<13:49:49.800> comes<13:49:49.980> to<13:49:50.096> network<13:49:50.276> Plus 13:49:51.650 --> 13:49:51.660 align:start position:0% it comes to network Plus 13:49:51.660 --> 13:49:55.370 align:start position:0% it comes to network Plus so<13:49:52.200> virtual<13:49:53.096> local<13:49:53.520> area<13:49:53.936> networks<13:49:54.540> or<13:49:54.776> vlans 13:49:55.370 --> 13:49:55.380 align:start position:0% so virtual local area networks or vlans 13:49:55.380 --> 13:49:57.470 align:start position:0% so virtual local area networks or vlans are<13:49:55.916> a<13:49:56.096> type<13:49:56.276> of<13:49:56.520> local<13:49:56.756> area<13:49:57.060> network 13:49:57.470 --> 13:49:57.480 align:start position:0% are a type of local area network 13:49:57.480 --> 13:50:00.350 align:start position:0% are a type of local area network configuration<13:49:58.400> they're<13:49:59.400> actually<13:49:59.700> somewhat 13:50:00.350 --> 13:50:00.360 align:start position:0% configuration they're actually somewhat 13:50:00.360 --> 13:50:03.170 align:start position:0% configuration they're actually somewhat of<13:50:00.540> a<13:50:00.660> misnomer<13:50:01.256> though<13:50:01.800> the<13:50:02.040> word<13:50:02.220> virtual<13:50:02.820> is 13:50:03.170 --> 13:50:03.180 align:start position:0% of a misnomer though the word virtual is 13:50:03.180 --> 13:50:05.870 align:start position:0% of a misnomer though the word virtual is really<13:50:03.416> the<13:50:03.956> focus<13:50:04.320> of<13:50:04.680> the<13:50:04.916> name<13:50:05.096> they're 13:50:05.870 --> 13:50:05.880 align:start position:0% really the focus of the name they're 13:50:05.880 --> 13:50:09.766 align:start position:0% really the focus of the name they're really<13:50:06.116> more<13:50:06.480> segmented<13:50:07.380> than<13:50:07.860> virtual<13:50:08.776> VLAN 13:50:09.766 --> 13:50:09.776 align:start position:0% really more segmented than virtual VLAN 13:50:09.776 --> 13:50:12.530 align:start position:0% really more segmented than virtual VLAN can<13:50:10.080> be<13:50:10.256> described<13:50:10.916> or<13:50:11.160> defined<13:50:11.700> as<13:50:12.240> a<13:50:12.416> group 13:50:12.530 --> 13:50:12.540 align:start position:0% can be described or defined as a group 13:50:12.540 --> 13:50:14.870 align:start position:0% can be described or defined as a group of<13:50:12.720> computers<13:50:13.320> that<13:50:13.980> are<13:50:14.096> connected<13:50:14.520> to<13:50:14.700> one 13:50:14.870 --> 13:50:14.880 align:start position:0% of computers that are connected to one 13:50:14.880 --> 13:50:17.810 align:start position:0% of computers that are connected to one another<13:50:15.320> although<13:50:16.320> they<13:50:16.680> function<13:50:17.096> as<13:50:17.640> though 13:50:17.810 --> 13:50:17.820 align:start position:0% another although they function as though 13:50:17.820 --> 13:50:19.606 align:start position:0% another although they function as though they<13:50:18.060> are<13:50:18.180> on<13:50:18.360> different<13:50:18.596> networks<13:50:19.140> even 13:50:19.606 --> 13:50:19.616 align:start position:0% they are on different networks even 13:50:19.616 --> 13:50:22.550 align:start position:0% they are on different networks even though<13:50:19.800> they<13:50:20.096> sometimes<13:50:20.580> aren't<13:50:21.300> so<13:50:22.200> the 13:50:22.550 --> 13:50:22.560 align:start position:0% though they sometimes aren't so the 13:50:22.560 --> 13:50:24.710 align:start position:0% though they sometimes aren't so the computers<13:50:23.160> that<13:50:23.756> are<13:50:23.880> segmented<13:50:24.416> together 13:50:24.710 --> 13:50:24.720 align:start position:0% computers that are segmented together 13:50:24.720 --> 13:50:27.710 align:start position:0% computers that are segmented together are<13:50:25.560> usually<13:50:25.916> ones<13:50:26.580> that<13:50:26.880> are<13:50:27.000> in<13:50:27.300> a<13:50:27.480> same 13:50:27.710 --> 13:50:27.720 align:start position:0% are usually ones that are in a same 13:50:27.720 --> 13:50:30.586 align:start position:0% are usually ones that are in a same Department<13:50:28.020> as<13:50:28.436> the<13:50:28.616> others<13:50:28.980> for<13:50:29.640> example<13:50:29.936> we 13:50:30.586 --> 13:50:30.596 align:start position:0% Department as the others for example we 13:50:30.596 --> 13:50:34.490 align:start position:0% Department as the others for example we might<13:50:30.840> have<13:50:31.256> an<13:50:31.740> office<13:50:31.980> building<13:50:32.400> with<13:50:33.840> four 13:50:34.490 --> 13:50:34.500 align:start position:0% might have an office building with four 13:50:34.500 --> 13:50:37.310 align:start position:0% might have an office building with four floors 13:50:37.310 --> 13:50:37.320 align:start position:0% 13:50:37.320 --> 13:50:41.086 align:start position:0% and<13:50:38.096> the<13:50:38.340> encounting<13:50:38.936> employees<13:50:39.480> could<13:50:40.200> be<13:50:40.436> on 13:50:41.086 --> 13:50:41.096 align:start position:0% and the encounting employees could be on 13:50:41.096 --> 13:50:45.106 align:start position:0% and the encounting employees could be on every<13:50:41.340> floor 13:50:45.106 --> 13:50:45.116 align:start position:0% 13:50:45.116 --> 13:50:48.406 align:start position:0% a<13:50:45.660> VLAN<13:50:46.140> would<13:50:46.740> allow<13:50:47.096> them<13:50:47.400> to<13:50:48.000> all<13:50:48.180> be 13:50:48.406 --> 13:50:48.416 align:start position:0% a VLAN would allow them to all be 13:50:48.416 --> 13:50:50.570 align:start position:0% a VLAN would allow them to all be connected<13:50:48.840> to<13:50:49.320> one<13:50:49.500> another 13:50:50.570 --> 13:50:50.580 align:start position:0% connected to one another 13:50:50.580 --> 13:50:53.870 align:start position:0% connected to one another even<13:50:51.240> though<13:50:51.916> they're<13:50:52.916> really 13:50:53.870 --> 13:50:53.880 align:start position:0% even though they're really 13:50:53.880 --> 13:50:57.710 align:start position:0% even though they're really sort<13:50:54.480> of<13:50:54.660> sharing<13:50:55.436> the<13:50:56.400> network 13:50:57.710 --> 13:50:57.720 align:start position:0% sort of sharing the network 13:50:57.720 --> 13:51:00.106 align:start position:0% sort of sharing the network with<13:50:58.140> every<13:50:58.380> other<13:50:58.680> department<13:50:59.060> in<13:51:00.060> other 13:51:00.106 --> 13:51:00.116 align:start position:0% with every other department in other 13:51:00.116 --> 13:51:01.130 align:start position:0% with every other department in other words 13:51:01.130 --> 13:51:01.140 align:start position:0% words 13:51:01.140 --> 13:51:03.710 align:start position:0% words if<13:51:01.500> we<13:51:01.616> had<13:51:01.916> the<13:51:02.276> accountants<13:51:02.756> and<13:51:03.060> then<13:51:03.300> let's 13:51:03.710 --> 13:51:03.720 align:start position:0% if we had the accountants and then let's 13:51:03.720 --> 13:51:06.230 align:start position:0% if we had the accountants and then let's say<13:51:03.900> the<13:51:04.320> managers<13:51:04.800> they<13:51:05.520> would<13:51:05.700> all<13:51:05.936> be 13:51:06.230 --> 13:51:06.240 align:start position:0% say the managers they would all be 13:51:06.240 --> 13:51:09.170 align:start position:0% say the managers they would all be connected<13:51:07.020> to<13:51:07.320> the<13:51:07.560> same<13:51:07.860> physical<13:51:08.640> Network 13:51:09.170 --> 13:51:09.180 align:start position:0% connected to the same physical Network 13:51:09.180 --> 13:51:11.690 align:start position:0% connected to the same physical Network in<13:51:09.720> the<13:51:09.840> building<13:51:10.080> but<13:51:10.800> we<13:51:11.096> could<13:51:11.220> segment 13:51:11.690 --> 13:51:11.700 align:start position:0% in the building but we could segment 13:51:11.700 --> 13:51:15.230 align:start position:0% in the building but we could segment them<13:51:11.936> into<13:51:12.596> separate<13:51:13.140> virtual<13:51:14.040> local<13:51:15.000> area 13:51:15.230 --> 13:51:15.240 align:start position:0% them into separate virtual local area 13:51:15.240 --> 13:51:17.266 align:start position:0% them into separate virtual local area networks<13:51:15.900> so<13:51:16.436> that<13:51:16.680> way<13:51:16.860> they<13:51:17.160> can 13:51:17.266 --> 13:51:17.276 align:start position:0% networks so that way they can 13:51:17.276 --> 13:51:19.130 align:start position:0% networks so that way they can communicate<13:51:17.700> with<13:51:17.880> one<13:51:18.060> another<13:51:18.240> and<13:51:18.956> other 13:51:19.130 --> 13:51:19.140 align:start position:0% communicate with one another and other 13:51:19.140 --> 13:51:22.070 align:start position:0% communicate with one another and other folks<13:51:19.500> can't<13:51:19.740> communicate<13:51:20.400> with<13:51:21.000> them 13:51:22.070 --> 13:51:22.080 align:start position:0% folks can't communicate with them 13:51:22.080 --> 13:51:25.426 align:start position:0% folks can't communicate with them they<13:51:22.980> would<13:51:23.160> therefore<13:51:23.640> think<13:51:24.480> that<13:51:25.256> they 13:51:25.426 --> 13:51:25.436 align:start position:0% they would therefore think that they 13:51:25.436 --> 13:51:27.350 align:start position:0% they would therefore think that they were<13:51:25.560> connected<13:51:26.040> physically<13:51:26.580> to<13:51:27.000> one<13:51:27.180> another 13:51:27.350 --> 13:51:27.360 align:start position:0% were connected physically to one another 13:51:27.360 --> 13:51:31.190 align:start position:0% were connected physically to one another or<13:51:28.080> all<13:51:28.436> plugged<13:51:28.740> into<13:51:28.860> the<13:51:29.220> same<13:51:29.520> switch<13:51:30.200> even 13:51:31.190 --> 13:51:31.200 align:start position:0% or all plugged into the same switch even 13:51:31.200 --> 13:51:33.406 align:start position:0% or all plugged into the same switch even though<13:51:31.436> were<13:51:31.916> you<13:51:32.096> really<13:51:32.400> using<13:51:32.880> four 13:51:33.406 --> 13:51:33.416 align:start position:0% though were you really using four 13:51:33.416 --> 13:51:37.130 align:start position:0% though were you really using four different<13:51:33.776> switches<13:51:34.380> one<13:51:35.160> for<13:51:35.520> each<13:51:35.820> floor 13:51:37.130 --> 13:51:37.140 align:start position:0% different switches one for each floor 13:51:37.140 --> 13:51:39.946 align:start position:0% different switches one for each floor now<13:51:37.500> there's<13:51:37.680> some<13:51:37.980> very<13:51:38.220> clear<13:51:38.456> benefits<13:51:39.300> to 13:51:39.946 --> 13:51:39.956 align:start position:0% now there's some very clear benefits to 13:51:39.956 --> 13:51:42.230 align:start position:0% now there's some very clear benefits to having<13:51:40.200> VLAN<13:51:40.980> set<13:51:41.220> up 13:51:42.230 --> 13:51:42.240 align:start position:0% having VLAN set up 13:51:42.240 --> 13:51:45.290 align:start position:0% having VLAN set up first<13:51:42.776> the<13:51:43.436> security<13:51:43.616> is<13:51:44.096> increased<13:51:44.640> this<13:51:45.180> is 13:51:45.290 --> 13:51:45.300 align:start position:0% first the security is increased this is 13:51:45.300 --> 13:51:49.310 align:start position:0% first the security is increased this is because<13:51:45.680> when<13:51:46.680> we<13:51:47.040> segment<13:51:47.520> a<13:51:47.880> network 13:51:49.310 --> 13:51:49.320 align:start position:0% because when we segment a network 13:51:49.320 --> 13:51:52.070 align:start position:0% because when we segment a network there<13:51:50.040> are<13:51:50.220> virtual<13:51:50.700> boundaries<13:51:51.240> and<13:51:51.900> that 13:51:52.070 --> 13:51:52.080 align:start position:0% there are virtual boundaries and that 13:51:52.080 --> 13:51:54.350 align:start position:0% there are virtual boundaries and that makes<13:51:52.256> attacking<13:51:53.096> the<13:51:53.340> entire<13:51:53.700> network<13:51:54.000> very 13:51:54.350 --> 13:51:54.360 align:start position:0% makes attacking the entire network very 13:51:54.360 --> 13:51:57.170 align:start position:0% makes attacking the entire network very unlikely<13:51:54.956> it<13:51:55.740> also<13:51:56.040> makes<13:51:56.220> sure<13:51:56.520> that 13:51:57.170 --> 13:51:57.180 align:start position:0% unlikely it also makes sure that 13:51:57.180 --> 13:51:58.850 align:start position:0% unlikely it also makes sure that accounting<13:51:57.720> people<13:51:57.956> are<13:51:58.200> going<13:51:58.320> to<13:51:58.500> have<13:51:58.616> a 13:51:58.850 --> 13:51:58.860 align:start position:0% accounting people are going to have a 13:51:58.860 --> 13:52:01.426 align:start position:0% accounting people are going to have a harder<13:51:59.160> time<13:51:59.400> getting<13:52:00.060> into<13:52:00.416> the<13:52:01.256> management 13:52:01.426 --> 13:52:01.436 align:start position:0% harder time getting into the management 13:52:01.436 --> 13:52:03.290 align:start position:0% harder time getting into the management people's<13:52:02.160> information 13:52:03.290 --> 13:52:03.300 align:start position:0% people's information 13:52:03.300 --> 13:52:05.746 align:start position:0% people's information so<13:52:03.900> again<13:52:04.080> even<13:52:04.740> though<13:52:04.916> they're<13:52:05.340> physically 13:52:05.746 --> 13:52:05.756 align:start position:0% so again even though they're physically 13:52:05.756 --> 13:52:08.570 align:start position:0% so again even though they're physically connected<13:52:06.360> all<13:52:07.080> the<13:52:07.320> same<13:52:07.500> we're<13:52:08.160> giving<13:52:08.340> them 13:52:08.570 --> 13:52:08.580 align:start position:0% connected all the same we're giving them 13:52:08.580 --> 13:52:11.570 align:start position:0% connected all the same we're giving them a<13:52:08.880> virtual<13:52:09.240> segmentation<13:52:10.140> so<13:52:10.980> that<13:52:11.160> they<13:52:11.400> are 13:52:11.570 --> 13:52:11.580 align:start position:0% a virtual segmentation so that they are 13:52:11.580 --> 13:52:13.850 align:start position:0% a virtual segmentation so that they are separate<13:52:12.000> and<13:52:12.480> therefore<13:52:12.776> it's<13:52:13.256> a<13:52:13.500> slightly 13:52:13.850 --> 13:52:13.860 align:start position:0% separate and therefore it's a slightly 13:52:13.860 --> 13:52:15.290 align:start position:0% separate and therefore it's a slightly more<13:52:14.160> secure 13:52:15.290 --> 13:52:15.300 align:start position:0% more secure 13:52:15.300 --> 13:52:18.650 align:start position:0% more secure they<13:52:15.900> also<13:52:16.256> increase<13:52:16.860> the<13:52:17.756> performance<13:52:18.240> by 13:52:18.650 --> 13:52:18.660 align:start position:0% they also increase the performance by 13:52:18.660 --> 13:52:21.290 align:start position:0% they also increase the performance by freeing<13:52:19.140> up<13:52:19.320> bandwidth<13:52:20.096> and<13:52:20.580> reducing<13:52:21.116> and 13:52:21.290 --> 13:52:21.300 align:start position:0% freeing up bandwidth and reducing and 13:52:21.300 --> 13:52:23.870 align:start position:0% freeing up bandwidth and reducing and splitting<13:52:21.720> up<13:52:21.840> traffic<13:52:22.080> from<13:52:22.436> the<13:52:22.616> network<13:52:22.880> if 13:52:23.870 --> 13:52:23.880 align:start position:0% splitting up traffic from the network if 13:52:23.880 --> 13:52:26.510 align:start position:0% splitting up traffic from the network if accounting<13:52:24.480> for<13:52:24.720> instance<13:52:25.020> uses<13:52:25.680> a<13:52:26.220> lot<13:52:26.340> of 13:52:26.510 --> 13:52:26.520 align:start position:0% accounting for instance uses a lot of 13:52:26.520 --> 13:52:29.630 align:start position:0% accounting for instance uses a lot of bandwidth<13:52:27.116> and<13:52:27.480> management<13:52:27.776> doesn't<13:52:28.436> well<13:52:29.340> we 13:52:29.630 --> 13:52:29.640 align:start position:0% bandwidth and management doesn't well we 13:52:29.640 --> 13:52:31.606 align:start position:0% bandwidth and management doesn't well we don't<13:52:29.756> want<13:52:29.936> management<13:52:30.360> to<13:52:30.956> suffer<13:52:31.320> because 13:52:31.606 --> 13:52:31.616 align:start position:0% don't want management to suffer because 13:52:31.616 --> 13:52:33.890 align:start position:0% don't want management to suffer because accounting<13:52:32.340> is<13:52:32.580> using<13:52:32.880> QuickBooks<13:52:33.540> and<13:52:33.720> the 13:52:33.890 --> 13:52:33.900 align:start position:0% accounting is using QuickBooks and the 13:52:33.900 --> 13:52:36.710 align:start position:0% accounting is using QuickBooks and the servers<13:52:34.380> so<13:52:34.680> much<13:52:34.860> therefore<13:52:35.820> by<13:52:36.180> segmenting 13:52:36.710 --> 13:52:36.720 align:start position:0% servers so much therefore by segmenting 13:52:36.720 --> 13:52:38.990 align:start position:0% servers so much therefore by segmenting it<13:52:36.900> we<13:52:37.140> can<13:52:37.320> make<13:52:37.560> sure<13:52:37.800> all<13:52:38.456> of<13:52:38.580> the<13:52:38.820> traffic 13:52:38.990 --> 13:52:39.000 align:start position:0% it we can make sure all of the traffic 13:52:39.000 --> 13:52:41.870 align:start position:0% it we can make sure all of the traffic that<13:52:39.416> accounting<13:52:39.900> is<13:52:40.080> using<13:52:40.436> is<13:52:41.096> staying<13:52:41.520> on 13:52:41.870 --> 13:52:41.880 align:start position:0% that accounting is using is staying on 13:52:41.880 --> 13:52:45.170 align:start position:0% that accounting is using is staying on their<13:52:42.060> segment<13:52:42.480> and<13:52:43.320> management<13:52:44.180> performance 13:52:45.170 --> 13:52:45.180 align:start position:0% their segment and management performance 13:52:45.180 --> 13:52:48.290 align:start position:0% their segment and management performance doesn't<13:52:45.660> suffer<13:52:46.200> as<13:52:46.680> a<13:52:46.860> result 13:52:48.290 --> 13:52:48.300 align:start position:0% doesn't suffer as a result 13:52:48.300 --> 13:52:50.690 align:start position:0% doesn't suffer as a result we<13:52:48.840> can<13:52:49.020> also<13:52:49.320> group<13:52:49.616> users<13:52:50.096> that<13:52:50.400> often 13:52:50.690 --> 13:52:50.700 align:start position:0% we can also group users that often 13:52:50.700 --> 13:52:53.510 align:start position:0% we can also group users that often communicate<13:52:51.180> and<13:52:51.360> share<13:52:51.596> data<13:52:52.080> and<13:52:52.380> so<13:52:52.616> this 13:52:53.510 --> 13:52:53.520 align:start position:0% communicate and share data and so this 13:52:53.520 --> 13:52:56.330 align:start position:0% communicate and share data and so this network<13:52:53.700> becomes<13:52:54.596> far<13:52:54.956> more<13:52:55.140> organized<13:52:55.800> this 13:52:56.330 --> 13:52:56.340 align:start position:0% network becomes far more organized this 13:52:56.340 --> 13:52:57.830 align:start position:0% network becomes far more organized this is<13:52:56.456> not<13:52:56.640> just<13:52:56.820> from<13:52:57.116> security<13:52:57.480> and 13:52:57.830 --> 13:52:57.840 align:start position:0% is not just from security and 13:52:57.840 --> 13:53:00.586 align:start position:0% is not just from security and performance<13:52:58.380> perspectives<13:52:59.240> organization<13:53:00.240> is 13:53:00.586 --> 13:53:00.596 align:start position:0% performance perspectives organization is 13:53:00.596 --> 13:53:02.630 align:start position:0% performance perspectives organization is just<13:53:00.840> from<13:53:01.080> a<13:53:01.256> logistical<13:53:01.740> perspective<13:53:02.276> as 13:53:02.630 --> 13:53:02.640 align:start position:0% just from a logistical perspective as 13:53:02.640 --> 13:53:04.730 align:start position:0% just from a logistical perspective as well<13:53:02.756> I<13:53:03.360> can<13:53:03.480> put<13:53:03.660> someone<13:53:03.840> in<13:53:04.080> a<13:53:04.140> VLAN<13:53:04.560> and 13:53:04.730 --> 13:53:04.740 align:start position:0% well I can put someone in a VLAN and 13:53:04.740 --> 13:53:06.830 align:start position:0% well I can put someone in a VLAN and automatically<13:53:05.276> they're<13:53:05.640> going<13:53:05.820> to<13:53:06.000> have<13:53:06.180> all 13:53:06.830 --> 13:53:06.840 align:start position:0% automatically they're going to have all 13:53:06.840 --> 13:53:09.106 align:start position:0% automatically they're going to have all the<13:53:07.080> benefits<13:53:07.616> that<13:53:08.096> come<13:53:08.276> with<13:53:08.580> being<13:53:08.820> in 13:53:09.106 --> 13:53:09.116 align:start position:0% the benefits that come with being in 13:53:09.116 --> 13:53:11.690 align:start position:0% the benefits that come with being in that<13:53:09.240> segmented<13:53:09.840> area<13:53:10.276> independent<13:53:11.276> of<13:53:11.456> their 13:53:11.690 --> 13:53:11.700 align:start position:0% that segmented area independent of their 13:53:11.700 --> 13:53:14.690 align:start position:0% that segmented area independent of their physical<13:53:11.936> location 13:53:14.690 --> 13:53:14.700 align:start position:0% physical location 13:53:14.700 --> 13:53:16.490 align:start position:0% physical location finally<13:53:15.360> it<13:53:15.776> also<13:53:16.080> makes<13:53:16.200> the 13:53:16.490 --> 13:53:16.500 align:start position:0% finally it also makes the 13:53:16.500 --> 13:53:18.586 align:start position:0% finally it also makes the administrator's<13:53:17.276> job<13:53:17.520> a<13:53:17.820> lot<13:53:17.936> more<13:53:18.180> easier 13:53:18.586 --> 13:53:18.596 align:start position:0% administrator's job a lot more easier 13:53:18.596 --> 13:53:20.990 align:start position:0% administrator's job a lot more easier because<13:53:19.256> when<13:53:19.680> everything<13:53:19.916> is<13:53:20.220> segmented<13:53:20.820> up 13:53:20.990 --> 13:53:21.000 align:start position:0% because when everything is segmented up 13:53:21.000 --> 13:53:23.870 align:start position:0% because when everything is segmented up things<13:53:21.360> become<13:53:21.840> easier<13:53:22.436> to<13:53:22.740> deal<13:53:22.916> with<13:53:23.160> I 13:53:23.870 --> 13:53:23.880 align:start position:0% things become easier to deal with I 13:53:23.880 --> 13:53:27.230 align:start position:0% things become easier to deal with I don't<13:53:24.060> have<13:53:24.480> to<13:53:24.840> create<13:53:25.436> a<13:53:26.096> specific<13:53:26.456> set<13:53:26.880> of 13:53:27.230 --> 13:53:27.240 align:start position:0% don't have to create a specific set of 13:53:27.240 --> 13:53:30.470 align:start position:0% don't have to create a specific set of policies<13:53:27.956> or<13:53:28.616> security<13:53:28.860> for<13:53:29.640> one<13:53:29.880> individual 13:53:30.470 --> 13:53:30.480 align:start position:0% policies or security for one individual 13:53:30.480 --> 13:53:33.170 align:start position:0% policies or security for one individual when<13:53:31.320> I<13:53:31.616> can<13:53:31.740> simply 13:53:33.170 --> 13:53:33.180 align:start position:0% when I can simply 13:53:33.180 --> 13:53:35.570 align:start position:0% when I can simply uh<13:53:33.840> put<13:53:34.140> them<13:53:34.256> into<13:53:34.436> a<13:53:34.680> VLAN<13:53:35.040> and<13:53:35.160> let<13:53:35.340> it<13:53:35.456> all 13:53:35.570 --> 13:53:35.580 align:start position:0% uh put them into a VLAN and let it all 13:53:35.580 --> 13:53:37.670 align:start position:0% uh put them into a VLAN and let it all sort<13:53:35.756> of<13:53:35.880> work<13:53:36.000> itself<13:53:36.360> out 13:53:37.670 --> 13:53:37.680 align:start position:0% sort of work itself out 13:53:37.680 --> 13:53:40.606 align:start position:0% sort of work itself out so<13:53:38.160> here's<13:53:38.520> an<13:53:38.700> example<13:53:39.116> of<13:53:39.776> what<13:53:40.020> a<13:53:40.200> VLAN 13:53:40.606 --> 13:53:40.616 align:start position:0% so here's an example of what a VLAN 13:53:40.616 --> 13:53:42.586 align:start position:0% so here's an example of what a VLAN might<13:53:40.860> look<13:53:41.040> like<13:53:41.220> as<13:53:41.700> you<13:53:41.880> can<13:53:42.000> see<13:53:42.116> there<13:53:42.416> are 13:53:42.586 --> 13:53:42.596 align:start position:0% might look like as you can see there are 13:53:42.596 --> 13:53:44.030 align:start position:0% might look like as you can see there are four<13:53:42.720> floors<13:53:43.140> to<13:53:43.320> the<13:53:43.436> building<13:53:43.616> with 13:53:44.030 --> 13:53:44.040 align:start position:0% four floors to the building with 13:53:44.040 --> 13:53:45.830 align:start position:0% four floors to the building with computers<13:53:44.520> on<13:53:44.700> each<13:53:44.880> of<13:53:45.000> them<13:53:45.116> and<13:53:45.720> the 13:53:45.830 --> 13:53:45.840 align:start position:0% computers on each of them and the 13:53:45.840 --> 13:53:47.690 align:start position:0% computers on each of them and the computers<13:53:46.200> are<13:53:46.380> all<13:53:46.560> connected<13:53:46.980> to<13:53:47.160> the<13:53:47.456> same 13:53:47.690 --> 13:53:47.700 align:start position:0% computers are all connected to the same 13:53:47.700 --> 13:53:50.926 align:start position:0% computers are all connected to the same network<13:53:48.060> I<13:53:48.956> very<13:53:49.256> much<13:53:49.380> simplified<13:53:49.980> this<13:53:50.456> in 13:53:50.926 --> 13:53:50.936 align:start position:0% network I very much simplified this in 13:53:50.936 --> 13:53:54.230 align:start position:0% network I very much simplified this in fact<13:53:51.060> we<13:53:51.596> would<13:53:51.776> probably<13:53:52.140> have<13:53:52.680> uh<13:53:53.580> switch<13:53:53.820> on 13:53:54.230 --> 13:53:54.240 align:start position:0% fact we would probably have uh switch on 13:53:54.240 --> 13:53:55.490 align:start position:0% fact we would probably have uh switch on every<13:53:54.480> floor 13:53:55.490 --> 13:53:55.500 align:start position:0% every floor 13:53:55.500 --> 13:53:59.870 align:start position:0% every floor remember<13:53:55.800> this<13:53:56.220> would<13:53:56.400> be<13:53:56.520> called<13:53:56.880> the<13:53:57.300> idfs 13:53:59.870 --> 13:53:59.880 align:start position:0% remember this would be called the idfs 13:53:59.880 --> 13:54:01.850 align:start position:0% remember this would be called the idfs and<13:54:00.480> then<13:54:00.660> they<13:54:00.900> would<13:54:01.080> all<13:54:01.320> come<13:54:01.616> together 13:54:01.850 --> 13:54:01.860 align:start position:0% and then they would all come together 13:54:01.860 --> 13:54:06.170 align:start position:0% and then they would all come together like<13:54:02.456> we<13:54:02.640> see<13:54:02.820> here<13:54:03.116> in<13:54:03.900> one<13:54:04.200> Central<13:54:04.580> MDF<13:54:05.580> but 13:54:06.170 --> 13:54:06.180 align:start position:0% like we see here in one Central MDF but 13:54:06.180 --> 13:54:08.510 align:start position:0% like we see here in one Central MDF but for<13:54:06.416> all<13:54:06.540> intensive<13:54:07.020> purposes<13:54:07.380> they're<13:54:08.220> all 13:54:08.510 --> 13:54:08.520 align:start position:0% for all intensive purposes they're all 13:54:08.520 --> 13:54:10.870 align:start position:0% for all intensive purposes they're all connected<13:54:09.000> to<13:54:09.300> the<13:54:09.540> same<13:54:09.776> physical<13:54:10.200> Network 13:54:10.870 --> 13:54:10.880 align:start position:0% connected to the same physical Network 13:54:10.880 --> 13:54:14.030 align:start position:0% connected to the same physical Network however<13:54:11.880> we<13:54:12.596> only<13:54:12.776> want<13:54:13.140> the<13:54:13.616> accounting 13:54:14.030 --> 13:54:14.040 align:start position:0% however we only want the accounting 13:54:14.040 --> 13:54:16.790 align:start position:0% however we only want the accounting employees<13:54:14.520> to<13:54:15.480> share<13:54:15.720> data<13:54:16.080> with<13:54:16.320> themselves 13:54:16.790 --> 13:54:16.800 align:start position:0% employees to share data with themselves 13:54:16.800 --> 13:54:19.310 align:start position:0% employees to share data with themselves not<13:54:17.520> with<13:54:17.700> the<13:54:17.936> graphic<13:54:18.300> designers<13:54:18.776> or<13:54:19.140> the 13:54:19.310 --> 13:54:19.320 align:start position:0% not with the graphic designers or the 13:54:19.320 --> 13:54:21.586 align:start position:0% not with the graphic designers or the marketing<13:54:19.680> folks<13:54:20.040> and<13:54:20.456> we<13:54:20.580> want<13:54:20.756> them<13:54:21.060> to<13:54:21.416> have 13:54:21.586 --> 13:54:21.596 align:start position:0% marketing folks and we want them to have 13:54:21.596 --> 13:54:24.170 align:start position:0% marketing folks and we want them to have their<13:54:21.900> own<13:54:22.020> segmented<13:54:22.680> Network<13:54:22.916> as<13:54:23.340> well 13:54:24.170 --> 13:54:24.180 align:start position:0% their own segmented Network as well 13:54:24.180 --> 13:54:27.946 align:start position:0% their own segmented Network as well so<13:54:24.840> with<13:54:25.200> VLAN<13:54:25.680> we<13:54:26.276> can<13:54:26.456> actually<13:54:26.700> segment<13:54:27.416> out 13:54:27.946 --> 13:54:27.956 align:start position:0% so with VLAN we can actually segment out 13:54:27.956 --> 13:54:29.510 align:start position:0% so with VLAN we can actually segment out the 13:54:29.510 --> 13:54:29.520 align:start position:0% the 13:54:29.520 --> 13:54:32.446 align:start position:0% the counting<13:54:30.240> folks<13:54:30.720> into<13:54:31.080> their<13:54:31.380> own<13:54:31.560> virtual 13:54:32.446 --> 13:54:32.456 align:start position:0% counting folks into their own virtual 13:54:32.456 --> 13:54:34.310 align:start position:0% counting folks into their own virtual Network<13:54:32.756> even<13:54:33.416> though<13:54:33.596> they're<13:54:33.776> on<13:54:33.956> the<13:54:34.140> same 13:54:34.310 --> 13:54:34.320 align:start position:0% Network even though they're on the same 13:54:34.320 --> 13:54:36.710 align:start position:0% Network even though they're on the same physical<13:54:35.160> Network 13:54:36.710 --> 13:54:36.720 align:start position:0% physical Network 13:54:36.720 --> 13:54:38.926 align:start position:0% physical Network the<13:54:37.140> same<13:54:37.256> could<13:54:37.500> go<13:54:37.680> for<13:54:37.980> the<13:54:38.456> graphic<13:54:38.756> design 13:54:38.926 --> 13:54:38.936 align:start position:0% the same could go for the graphic design 13:54:38.936 --> 13:54:42.470 align:start position:0% the same could go for the graphic design folks<13:54:39.596> and<13:54:40.560> the<13:54:40.980> marketing<13:54:41.400> folks<13:54:41.756> they're 13:54:42.470 --> 13:54:42.480 align:start position:0% folks and the marketing folks they're 13:54:42.480 --> 13:54:44.746 align:start position:0% folks and the marketing folks they're all<13:54:42.720> split<13:54:43.140> into<13:54:43.256> segments<13:54:43.916> with<13:54:44.276> similar 13:54:44.746 --> 13:54:44.756 align:start position:0% all split into segments with similar 13:54:44.756 --> 13:54:46.670 align:start position:0% all split into segments with similar employees<13:54:45.300> and<13:54:45.956> we<13:54:46.080> would<13:54:46.256> actually<13:54:46.436> give 13:54:46.670 --> 13:54:46.680 align:start position:0% employees and we would actually give 13:54:46.680 --> 13:54:49.550 align:start position:0% employees and we would actually give these<13:54:46.980> vlans<13:54:47.456> numbers<13:54:47.756> for<13:54:48.596> instance<13:54:48.776> VLAN<13:54:49.320> 1 13:54:49.550 --> 13:54:49.560 align:start position:0% these vlans numbers for instance VLAN 1 13:54:49.560 --> 13:54:51.586 align:start position:0% these vlans numbers for instance VLAN 1 2 13:54:51.586 --> 13:54:51.596 align:start position:0% 2 13:54:51.596 --> 13:54:55.370 align:start position:0% 2 and<13:54:52.140> three 13:54:55.370 --> 13:54:55.380 align:start position:0% 13:54:55.380 --> 13:54:57.650 align:start position:0% now<13:54:55.980> there<13:54:56.220> are<13:54:56.340> three<13:54:56.580> different<13:54:56.880> ways<13:54:57.360> that 13:54:57.650 --> 13:54:57.660 align:start position:0% now there are three different ways that 13:54:57.660 --> 13:55:00.406 align:start position:0% now there are three different ways that VLAN<13:54:58.080> membership<13:54:58.500> can<13:54:58.860> be<13:54:59.040> assigned<13:54:59.520> a 13:55:00.406 --> 13:55:00.416 align:start position:0% VLAN membership can be assigned a 13:55:00.416 --> 13:55:02.150 align:start position:0% VLAN membership can be assigned a membership<13:55:00.720> is<13:55:00.956> a<13:55:01.140> way<13:55:01.256> that<13:55:01.436> the<13:55:01.560> device<13:55:01.800> is 13:55:02.150 --> 13:55:02.160 align:start position:0% membership is a way that the device is 13:55:02.160 --> 13:55:04.606 align:start position:0% membership is a way that the device is assigned<13:55:02.700> to<13:55:02.820> that<13:55:03.060> specific<13:55:03.300> VLAN<13:55:03.900> for 13:55:04.606 --> 13:55:04.616 align:start position:0% assigned to that specific VLAN for 13:55:04.616 --> 13:55:06.230 align:start position:0% assigned to that specific VLAN for instance<13:55:04.860> the<13:55:05.096> one<13:55:05.276> two<13:55:05.520> or<13:55:05.700> three<13:55:05.880> that<13:55:06.060> we 13:55:06.230 --> 13:55:06.240 align:start position:0% instance the one two or three that we 13:55:06.240 --> 13:55:10.030 align:start position:0% instance the one two or three that we just<13:55:06.360> mentioned<13:55:06.776> the<13:55:07.740> first<13:55:07.916> method<13:55:08.540> involves 13:55:10.030 --> 13:55:10.040 align:start position:0% just mentioned the first method involves 13:55:10.040 --> 13:55:12.530 align:start position:0% just mentioned the first method involves protocol-based<13:55:11.040> vlans<13:55:11.640> in<13:55:12.300> this<13:55:12.416> way 13:55:12.530 --> 13:55:12.540 align:start position:0% protocol-based vlans in this way 13:55:12.540 --> 13:55:15.710 align:start position:0% protocol-based vlans in this way computers<13:55:13.256> are<13:55:13.560> assigned<13:55:13.980> to<13:55:14.096> vlans<13:55:14.720> using 13:55:15.710 --> 13:55:15.720 align:start position:0% computers are assigned to vlans using 13:55:15.720 --> 13:55:17.990 align:start position:0% computers are assigned to vlans using networking<13:55:16.680> protocols<13:55:17.340> that<13:55:17.520> are<13:55:17.640> in<13:55:17.756> place 13:55:17.990 --> 13:55:18.000 align:start position:0% networking protocols that are in place 13:55:18.000 --> 13:55:21.470 align:start position:0% networking protocols that are in place such<13:55:18.360> as<13:55:18.540> the<13:55:18.776> IP<13:55:19.080> address<13:55:19.400> the<13:55:20.400> IP<13:55:20.756> number<13:55:21.180> is 13:55:21.470 --> 13:55:21.480 align:start position:0% such as the IP address the IP number is 13:55:21.480 --> 13:55:23.150 align:start position:0% such as the IP address the IP number is only<13:55:21.660> used<13:55:21.900> to<13:55:22.140> determine<13:55:22.500> the<13:55:22.740> membership 13:55:23.150 --> 13:55:23.160 align:start position:0% only used to determine the membership 13:55:23.160 --> 13:55:25.730 align:start position:0% only used to determine the membership but<13:55:23.820> has<13:55:24.000> nothing<13:55:24.300> to<13:55:24.540> do<13:55:24.596> with<13:55:24.956> the<13:55:25.256> routing 13:55:25.730 --> 13:55:25.740 align:start position:0% but has nothing to do with the routing 13:55:25.740 --> 13:55:28.550 align:start position:0% but has nothing to do with the routing of<13:55:26.096> the<13:55:26.276> VLAN<13:55:26.700> Network<13:55:27.000> so<13:55:27.776> for<13:55:28.020> instance<13:55:28.256> we 13:55:28.550 --> 13:55:28.560 align:start position:0% of the VLAN Network so for instance we 13:55:28.560 --> 13:55:31.906 align:start position:0% of the VLAN Network so for instance we could<13:55:28.680> say<13:55:28.980> all<13:55:29.640> IP<13:55:30.000> addresses<13:55:30.596> from<13:55:31.020> 1<13:55:31.380> to<13:55:31.616> 100 13:55:31.906 --> 13:55:31.916 align:start position:0% could say all IP addresses from 1 to 100 13:55:31.916 --> 13:55:35.030 align:start position:0% could say all IP addresses from 1 to 100 are<13:55:32.700> on<13:55:32.936> a<13:55:33.116> specific<13:55:33.360> VLAN<13:55:33.840> and<13:55:34.436> all<13:55:34.616> the<13:55:34.800> ones 13:55:35.030 --> 13:55:35.040 align:start position:0% are on a specific VLAN and all the ones 13:55:35.040 --> 13:55:39.050 align:start position:0% are on a specific VLAN and all the ones from<13:55:35.276> 101<13:55:35.820> to<13:55:36.116> 200<13:55:36.660> are<13:55:37.320> in<13:55:37.560> another 13:55:39.050 --> 13:55:39.060 align:start position:0% from 101 to 200 are in another 13:55:39.060 --> 13:55:41.446 align:start position:0% from 101 to 200 are in another another<13:55:39.720> thing<13:55:39.956> we<13:55:40.140> can<13:55:40.256> do<13:55:40.436> is<13:55:40.916> what's<13:55:41.160> called 13:55:41.446 --> 13:55:41.456 align:start position:0% another thing we can do is what's called 13:55:41.456 --> 13:55:43.370 align:start position:0% another thing we can do is what's called Port<13:55:41.820> based<13:55:42.300> vlans 13:55:43.370 --> 13:55:43.380 align:start position:0% Port based vlans 13:55:43.380 --> 13:55:45.650 align:start position:0% Port based vlans this<13:55:44.040> requires<13:55:44.640> that<13:55:44.880> ports<13:55:45.300> on<13:55:45.360> the<13:55:45.480> network 13:55:45.650 --> 13:55:45.660 align:start position:0% this requires that ports on the network 13:55:45.660 --> 13:55:49.130 align:start position:0% this requires that ports on the network switch<13:55:46.080> are<13:55:46.560> assigned<13:55:47.040> to<13:55:47.220> specific<13:55:47.520> vlans<13:55:48.596> so 13:55:49.130 --> 13:55:49.140 align:start position:0% switch are assigned to specific vlans so 13:55:49.140 --> 13:55:52.310 align:start position:0% switch are assigned to specific vlans so as<13:55:49.436> you<13:55:49.616> saw<13:55:49.800> previously<13:55:50.456> we<13:55:51.360> had<13:55:51.660> uh 13:55:52.310 --> 13:55:52.320 align:start position:0% as you saw previously we had uh 13:55:52.320 --> 13:55:55.010 align:start position:0% as you saw previously we had uh accounting<13:55:52.980> and<13:55:53.340> marketing<13:55:53.880> and<13:55:54.360> Graphics 13:55:55.010 --> 13:55:55.020 align:start position:0% accounting and marketing and Graphics 13:55:55.020 --> 13:55:57.406 align:start position:0% accounting and marketing and Graphics all<13:55:55.500> in<13:55:55.680> sort<13:55:55.980> of<13:55:56.096> different 13:55:57.406 --> 13:55:57.416 align:start position:0% all in sort of different 13:55:57.416 --> 13:55:59.210 align:start position:0% all in sort of different um<13:55:57.480> physical<13:55:58.020> locations<13:55:58.680> but<13:55:58.860> they<13:55:58.980> were<13:55:59.096> all 13:55:59.210 --> 13:55:59.220 align:start position:0% um physical locations but they were all 13:55:59.220 --> 13:56:01.790 align:start position:0% um physical locations but they were all plugged<13:55:59.520> up<13:55:59.640> to<13:55:59.880> a<13:56:00.060> central<13:56:00.360> switch 13:56:01.790 --> 13:56:01.800 align:start position:0% plugged up to a central switch 13:56:01.800 --> 13:56:04.190 align:start position:0% plugged up to a central switch so<13:56:02.096> what<13:56:02.276> we<13:56:02.400> would<13:56:02.520> say<13:56:02.700> is<13:56:02.936> for<13:56:03.240> instance 13:56:04.190 --> 13:56:04.200 align:start position:0% so what we would say is for instance 13:56:04.200 --> 13:56:07.426 align:start position:0% so what we would say is for instance any<13:56:04.860> computers<13:56:05.400> plugged<13:56:05.936> up<13:56:06.060> to<13:56:06.480> supports<13:56:07.080> one 13:56:07.426 --> 13:56:07.436 align:start position:0% any computers plugged up to supports one 13:56:07.436 --> 13:56:10.670 align:start position:0% any computers plugged up to supports one through<13:56:07.680> three<13:56:07.980> are<13:56:08.700> in<13:56:08.880> VLAN<13:56:09.300> one<13:56:09.540> and<13:56:10.380> the 13:56:10.670 --> 13:56:10.680 align:start position:0% through three are in VLAN one and the 13:56:10.680 --> 13:56:13.370 align:start position:0% through three are in VLAN one and the ports<13:56:11.040> plugged<13:56:11.456> up<13:56:11.640> to<13:56:12.116> four<13:56:12.416> and<13:56:12.660> five<13:56:12.900> or<13:56:13.140> in 13:56:13.370 --> 13:56:13.380 align:start position:0% ports plugged up to four and five or in 13:56:13.380 --> 13:56:15.830 align:start position:0% ports plugged up to four and five or in two<13:56:13.616> and<13:56:14.220> six<13:56:14.456> and<13:56:14.640> seven<13:56:14.880> are<13:56:15.060> three<13:56:15.300> now 13:56:15.830 --> 13:56:15.840 align:start position:0% two and six and seven are three now 13:56:15.840 --> 13:56:17.390 align:start position:0% two and six and seven are three now remember<13:56:16.020> a<13:56:16.320> lot<13:56:16.436> of<13:56:16.560> switches<13:56:16.916> can<13:56:17.220> have 13:56:17.390 --> 13:56:17.400 align:start position:0% remember a lot of switches can have 13:56:17.400 --> 13:56:20.390 align:start position:0% remember a lot of switches can have perhaps<13:56:17.880> 200<13:56:18.596> ports<13:56:19.200> so<13:56:19.616> this<13:56:19.800> can<13:56:19.980> get<13:56:20.220> a 13:56:20.390 --> 13:56:20.400 align:start position:0% perhaps 200 ports so this can get a 13:56:20.400 --> 13:56:23.690 align:start position:0% perhaps 200 ports so this can get a little<13:56:20.520> complex 13:56:23.690 --> 13:56:23.700 align:start position:0% 13:56:23.700 --> 13:56:27.406 align:start position:0% finally<13:56:24.480> there's<13:56:25.080> mac<13:56:25.560> address<13:56:25.916> based<13:56:26.820> vlans 13:56:27.406 --> 13:56:27.416 align:start position:0% finally there's mac address based vlans 13:56:27.416 --> 13:56:31.246 align:start position:0% finally there's mac address based vlans in<13:56:28.080> this<13:56:28.256> way<13:56:28.436> you've<13:56:29.400> heard<13:56:29.640> of<13:56:30.000> the<13:56:30.540> physical 13:56:31.246 --> 13:56:31.256 align:start position:0% in this way you've heard of the physical 13:56:31.256 --> 13:56:33.406 align:start position:0% in this way you've heard of the physical address<13:56:31.916> and<13:56:32.456> when<13:56:32.580> you<13:56:32.756> know<13:56:32.936> that<13:56:33.116> we<13:56:33.300> can 13:56:33.406 --> 13:56:33.416 align:start position:0% address and when you know that we can 13:56:33.416 --> 13:56:35.870 align:start position:0% address and when you know that we can use<13:56:33.720> this<13:56:34.020> to<13:56:34.256> actually<13:56:34.436> filter<13:56:34.800> out 13:56:35.870 --> 13:56:35.880 align:start position:0% use this to actually filter out 13:56:35.880 --> 13:56:38.266 align:start position:0% use this to actually filter out um using<13:56:36.540> a<13:56:36.840> what's<13:56:37.080> called<13:56:37.380> an<13:56:37.616> ACL<13:56:37.980> or 13:56:38.266 --> 13:56:38.276 align:start position:0% um using a what's called an ACL or 13:56:38.276 --> 13:56:39.946 align:start position:0% um using a what's called an ACL or Access<13:56:38.520> Control<13:56:38.880> lists<13:56:39.416> certain<13:56:39.660> Mac 13:56:39.946 --> 13:56:39.956 align:start position:0% Access Control lists certain Mac 13:56:39.956 --> 13:56:41.990 align:start position:0% Access Control lists certain Mac addresses<13:56:40.436> from<13:56:40.740> a<13:56:40.980> wireless<13:56:41.160> access<13:56:41.520> point 13:56:41.990 --> 13:56:42.000 align:start position:0% addresses from a wireless access point 13:56:42.000 --> 13:56:44.150 align:start position:0% addresses from a wireless access point well<13:56:42.480> it<13:56:42.660> works<13:56:42.900> the<13:56:43.080> same<13:56:43.200> way<13:56:43.320> with<13:56:43.560> a<13:56:43.740> VLAN 13:56:44.150 --> 13:56:44.160 align:start position:0% well it works the same way with a VLAN 13:56:44.160 --> 13:56:46.550 align:start position:0% well it works the same way with a VLAN depending<13:56:44.936> on<13:56:45.116> the<13:56:45.300> Mac<13:56:45.480> address<13:56:45.776> of<13:56:46.380> the 13:56:46.550 --> 13:56:46.560 align:start position:0% depending on the Mac address of the 13:56:46.560 --> 13:56:49.790 align:start position:0% depending on the Mac address of the computer<13:56:46.820> that<13:56:47.820> is<13:56:47.936> being<13:56:48.300> connected<13:56:48.900> it<13:56:49.680> will 13:56:49.790 --> 13:56:49.800 align:start position:0% computer that is being connected it will 13:56:49.800 --> 13:56:51.830 align:start position:0% computer that is being connected it will automatically<13:56:50.340> place<13:56:50.756> it<13:56:51.000> into<13:56:51.240> a<13:56:51.596> specific 13:56:51.830 --> 13:56:51.840 align:start position:0% automatically place it into a specific 13:56:51.840 --> 13:56:54.406 align:start position:0% automatically place it into a specific VLAN<13:56:52.560> of<13:56:53.040> course<13:56:53.160> the<13:56:53.456> benefit<13:56:53.580> with<13:56:53.936> this<13:56:54.180> is 13:56:54.406 --> 13:56:54.416 align:start position:0% VLAN of course the benefit with this is 13:56:54.416 --> 13:56:56.266 align:start position:0% VLAN of course the benefit with this is because<13:56:54.596> the<13:56:54.956> MAC<13:56:55.080> address<13:56:55.380> is<13:56:55.800> the<13:56:56.096> physical 13:56:56.266 --> 13:56:56.276 align:start position:0% because the MAC address is the physical 13:56:56.276 --> 13:56:58.906 align:start position:0% because the MAC address is the physical address<13:56:56.700> of<13:56:57.060> the<13:56:57.240> computer<13:56:57.416> and<13:56:58.380> is<13:56:58.616> always 13:56:58.906 --> 13:56:58.916 align:start position:0% address of the computer and is always 13:56:58.916 --> 13:57:01.010 align:start position:0% address of the computer and is always hardwired<13:56:59.640> onto<13:56:59.880> that<13:57:00.060> computer 13:57:01.010 --> 13:57:01.020 align:start position:0% hardwired onto that computer 13:57:01.020 --> 13:57:03.350 align:start position:0% hardwired onto that computer I<13:57:01.560> can<13:57:01.740> move<13:57:01.860> the<13:57:02.096> computer<13:57:02.276> into<13:57:03.060> any 13:57:03.350 --> 13:57:03.360 align:start position:0% I can move the computer into any 13:57:03.360 --> 13:57:05.210 align:start position:0% I can move the computer into any different<13:57:03.596> port<13:57:03.900> and<13:57:04.500> it<13:57:04.616> can<13:57:04.740> get<13:57:04.916> any 13:57:05.210 --> 13:57:05.220 align:start position:0% different port and it can get any 13:57:05.220 --> 13:57:06.946 align:start position:0% different port and it can get any different<13:57:05.400> IP<13:57:05.820> address<13:57:06.000> and<13:57:06.480> it'll<13:57:06.720> always 13:57:06.946 --> 13:57:06.956 align:start position:0% different IP address and it'll always 13:57:06.956 --> 13:57:10.850 align:start position:0% different IP address and it'll always remain<13:57:07.500> in<13:57:08.040> the<13:57:08.276> same<13:57:08.580> virtual<13:57:09.480> local<13:57:10.320> area 13:57:10.850 --> 13:57:10.860 align:start position:0% remain in the same virtual local area 13:57:10.860 --> 13:57:13.850 align:start position:0% remain in the same virtual local area network 13:57:13.850 --> 13:57:13.860 align:start position:0% 13:57:13.860 --> 13:57:15.890 align:start position:0% now<13:57:14.276> the<13:57:14.456> other<13:57:14.580> term<13:57:14.880> we<13:57:15.180> want<13:57:15.360> to<13:57:15.480> talk<13:57:15.720> about 13:57:15.890 --> 13:57:15.900 align:start position:0% now the other term we want to talk about 13:57:15.900 --> 13:57:20.446 align:start position:0% now the other term we want to talk about is<13:57:16.740> a<13:57:17.096> Soho<13:57:17.580> Network<13:57:17.880> or<13:57:18.300> a<13:57:18.596> small<13:57:19.380> office<13:57:19.616> home 13:57:20.446 --> 13:57:20.456 align:start position:0% is a Soho Network or a small office home 13:57:20.456 --> 13:57:23.150 align:start position:0% is a Soho Network or a small office home office<13:57:20.700> Network<13:57:21.200> this<13:57:22.200> is<13:57:22.436> generally 13:57:23.150 --> 13:57:23.160 align:start position:0% office Network this is generally 13:57:23.160 --> 13:57:26.570 align:start position:0% office Network this is generally speaking<13:57:23.640> as<13:57:23.820> the<13:57:24.000> name<13:57:24.180> implies<13:57:24.800> a<13:57:25.800> smaller 13:57:26.570 --> 13:57:26.580 align:start position:0% speaking as the name implies a smaller 13:57:26.580 --> 13:57:29.446 align:start position:0% speaking as the name implies a smaller home<13:57:27.060> office<13:57:27.360> Network<13:57:27.776> that<13:57:28.560> serves<13:57:28.980> between 13:57:29.446 --> 13:57:29.456 align:start position:0% home office Network that serves between 13:57:29.456 --> 13:57:32.330 align:start position:0% home office Network that serves between one<13:57:30.116> to<13:57:30.300> ten<13:57:30.540> users<13:57:30.900> on<13:57:31.080> the<13:57:31.200> network<13:57:31.380> now<13:57:32.096> you 13:57:32.330 --> 13:57:32.340 align:start position:0% one to ten users on the network now you 13:57:32.340 --> 13:57:34.426 align:start position:0% one to ten users on the network now you can<13:57:32.456> have<13:57:32.700> more<13:57:33.060> users<13:57:33.416> or<13:57:33.720> less<13:57:33.900> users 13:57:34.426 --> 13:57:34.436 align:start position:0% can have more users or less users 13:57:34.436 --> 13:57:36.106 align:start position:0% can have more users or less users although<13:57:35.160> I<13:57:35.276> guess<13:57:35.456> you<13:57:35.580> wouldn't<13:57:35.700> have<13:57:35.936> less 13:57:36.106 --> 13:57:36.116 align:start position:0% although I guess you wouldn't have less 13:57:36.116 --> 13:57:38.746 align:start position:0% although I guess you wouldn't have less users<13:57:36.540> than<13:57:36.720> one<13:57:36.956> but<13:57:37.800> generally<13:57:38.276> speaking 13:57:38.746 --> 13:57:38.756 align:start position:0% users than one but generally speaking 13:57:38.756 --> 13:57:40.970 align:start position:0% users than one but generally speaking it's<13:57:39.116> really<13:57:39.480> going<13:57:39.900> to<13:57:40.080> designate<13:57:40.500> a<13:57:40.800> very 13:57:40.970 --> 13:57:40.980 align:start position:0% it's really going to designate a very 13:57:40.980 --> 13:57:44.266 align:start position:0% it's really going to designate a very small<13:57:41.400> Network<13:57:42.020> although<13:57:43.020> they're<13:57:43.500> smaller 13:57:44.266 --> 13:57:44.276 align:start position:0% small Network although they're smaller 13:57:44.276 --> 13:57:46.730 align:start position:0% small Network although they're smaller in<13:57:44.580> physical<13:57:45.240> size<13:57:45.660> and<13:57:46.020> generally<13:57:46.380> smaller 13:57:46.730 --> 13:57:46.740 align:start position:0% in physical size and generally smaller 13:57:46.740 --> 13:57:48.470 align:start position:0% in physical size and generally smaller than<13:57:46.800> the<13:57:46.916> number<13:57:46.980> of<13:57:47.160> users<13:57:47.520> they're<13:57:48.300> going 13:57:48.470 --> 13:57:48.480 align:start position:0% than the number of users they're going 13:57:48.480 --> 13:57:50.870 align:start position:0% than the number of users they're going to<13:57:48.660> accommodate<13:57:49.320> the<13:57:50.040> network<13:57:50.160> in<13:57:50.580> the<13:57:50.756> same 13:57:50.870 --> 13:57:50.880 align:start position:0% to accommodate the network in the same 13:57:50.880 --> 13:57:52.246 align:start position:0% to accommodate the network in the same sort<13:57:51.116> of<13:57:51.240> way<13:57:51.360> meaning<13:57:51.660> we're<13:57:51.900> going<13:57:52.020> to<13:57:52.140> use 13:57:52.246 --> 13:57:52.256 align:start position:0% sort of way meaning we're going to use 13:57:52.256 --> 13:57:54.586 align:start position:0% sort of way meaning we're going to use some<13:57:52.560> of<13:57:52.680> the<13:57:52.860> same<13:57:53.040> protocols<13:57:53.820> and<13:57:54.240> devices 13:57:54.586 --> 13:57:54.596 align:start position:0% some of the same protocols and devices 13:57:54.596 --> 13:57:55.850 align:start position:0% some of the same protocols and devices they're<13:57:55.020> just<13:57:55.200> going<13:57:55.256> to<13:57:55.380> be<13:57:55.500> built 13:57:55.850 --> 13:57:55.860 align:start position:0% they're just going to be built 13:57:55.860 --> 13:57:57.406 align:start position:0% they're just going to be built differently<13:57:56.340> because<13:57:56.756> they<13:57:57.000> don't<13:57:57.116> need<13:57:57.240> to 13:57:57.406 --> 13:57:57.416 align:start position:0% differently because they don't need to 13:57:57.416 --> 13:57:58.970 align:start position:0% differently because they don't need to be<13:57:57.540> as<13:57:57.956> powerful 13:57:58.970 --> 13:57:58.980 align:start position:0% be as powerful 13:57:58.980 --> 13:58:02.086 align:start position:0% be as powerful so<13:57:59.880> for<13:58:00.360> instance<13:58:00.596> here<13:58:01.080> is<13:58:01.320> a<13:58:01.616> small<13:58:01.800> office 13:58:02.086 --> 13:58:02.096 align:start position:0% so for instance here is a small office 13:58:02.096 --> 13:58:05.030 align:start position:0% so for instance here is a small office home<13:58:02.456> office<13:58:02.700> Network<13:58:03.116> you<13:58:03.900> have<13:58:04.080> two<13:58:04.320> PCS<13:58:04.860> in 13:58:05.030 --> 13:58:05.040 align:start position:0% home office Network you have two PCS in 13:58:05.040 --> 13:58:06.890 align:start position:0% home office Network you have two PCS in it<13:58:05.160> perhaps<13:58:05.520> I<13:58:05.700> have<13:58:05.880> one<13:58:06.240> in<13:58:06.416> the<13:58:06.540> living<13:58:06.596> room 13:58:06.890 --> 13:58:06.900 align:start position:0% it perhaps I have one in the living room 13:58:06.900 --> 13:58:09.530 align:start position:0% it perhaps I have one in the living room or<13:58:07.680> one<13:58:07.860> in<13:58:08.040> the<13:58:08.160> bedroom<13:58:08.276> and<13:58:08.700> one<13:58:08.880> in<13:58:09.060> my<13:58:09.240> home 13:58:09.530 --> 13:58:09.540 align:start position:0% or one in the bedroom and one in my home 13:58:09.540 --> 13:58:12.650 align:start position:0% or one in the bedroom and one in my home office<13:58:09.776> and<13:58:10.560> maybe<13:58:10.860> even<13:58:11.160> we<13:58:11.520> have<13:58:11.820> a<13:58:12.180> laptop 13:58:12.650 --> 13:58:12.660 align:start position:0% office and maybe even we have a laptop 13:58:12.660 --> 13:58:14.030 align:start position:0% office and maybe even we have a laptop as<13:58:13.080> well 13:58:14.030 --> 13:58:14.040 align:start position:0% as well 13:58:14.040 --> 13:58:15.470 align:start position:0% as well so<13:58:14.456> maybe<13:58:14.640> we<13:58:14.880> have<13:58:15.000> three<13:58:15.240> different 13:58:15.470 --> 13:58:15.480 align:start position:0% so maybe we have three different 13:58:15.480 --> 13:58:18.050 align:start position:0% so maybe we have three different computers<13:58:15.956> ones<13:58:16.380> for<13:58:16.500> the<13:58:16.680> kids<13:58:16.860> one's<13:58:17.700> for<13:58:17.820> my 13:58:18.050 --> 13:58:18.060 align:start position:0% computers ones for the kids one's for my 13:58:18.060 --> 13:58:19.850 align:start position:0% computers ones for the kids one's for my wife<13:58:18.180> and<13:58:18.416> one's<13:58:18.776> for<13:58:18.900> me 13:58:19.850 --> 13:58:19.860 align:start position:0% wife and one's for me 13:58:19.860 --> 13:58:21.230 align:start position:0% wife and one's for me now 13:58:21.230 --> 13:58:21.240 align:start position:0% now 13:58:21.240 --> 13:58:23.990 align:start position:0% now we<13:58:21.900> have<13:58:22.200> what's<13:58:22.616> called<13:58:22.980> a<13:58:23.456> small<13:58:23.756> office 13:58:23.990 --> 13:58:24.000 align:start position:0% we have what's called a small office 13:58:24.000 --> 13:58:25.790 align:start position:0% we have what's called a small office home<13:58:24.360> office<13:58:24.596> router 13:58:25.790 --> 13:58:25.800 align:start position:0% home office router 13:58:25.800 --> 13:58:28.790 align:start position:0% home office router now<13:58:26.340> it's<13:58:26.520> called<13:58:26.820> just<13:58:27.300> a<13:58:27.720> router<13:58:28.140> to<13:58:28.436> many<13:58:28.616> of 13:58:28.790 --> 13:58:28.800 align:start position:0% now it's called just a router to many of 13:58:28.800 --> 13:58:30.710 align:start position:0% now it's called just a router to many of us<13:58:28.980> but<13:58:29.456> really<13:58:29.640> this<13:58:29.880> is<13:58:30.060> a<13:58:30.300> small<13:58:30.480> office 13:58:30.710 --> 13:58:30.720 align:start position:0% us but really this is a small office 13:58:30.720 --> 13:58:32.086 align:start position:0% us but really this is a small office home<13:58:31.020> office<13:58:31.200> router<13:58:31.680> because<13:58:31.800> it<13:58:31.980> does 13:58:32.086 --> 13:58:32.096 align:start position:0% home office router because it does 13:58:32.096 --> 13:58:34.970 align:start position:0% home office router because it does several<13:58:32.456> things<13:58:32.700> it<13:58:33.540> has<13:58:33.720> a<13:58:33.900> built-in<13:58:34.200> DHCP 13:58:34.970 --> 13:58:34.980 align:start position:0% several things it has a built-in DHCP 13:58:34.980 --> 13:58:36.170 align:start position:0% several things it has a built-in DHCP server 13:58:36.170 --> 13:58:36.180 align:start position:0% server 13:58:36.180 --> 13:58:40.190 align:start position:0% server for<13:58:36.776> a<13:58:36.900> lot<13:58:37.020> of<13:58:37.140> us<13:58:37.256> it<13:58:37.680> also<13:58:37.980> is<13:58:38.220> Wireless 13:58:40.190 --> 13:58:40.200 align:start position:0% for a lot of us it also is Wireless 13:58:40.200 --> 13:58:43.746 align:start position:0% for a lot of us it also is Wireless so<13:58:40.740> it's<13:58:40.980> a<13:58:41.160> wireless<13:58:41.400> access<13:58:41.936> point<13:58:42.360> or<13:58:42.660> WAP 13:58:43.746 --> 13:58:43.756 align:start position:0% so it's a wireless access point or WAP 13:58:43.756 --> 13:58:47.446 align:start position:0% so it's a wireless access point or WAP it's<13:58:44.756> also<13:58:45.240> has<13:58:45.956> uh<13:58:46.256> plugs<13:58:46.680> on<13:58:46.800> the<13:58:46.916> back<13:58:47.040> so<13:58:47.340> in 13:58:47.446 --> 13:58:47.456 align:start position:0% it's also has uh plugs on the back so in 13:58:47.456 --> 13:58:49.370 align:start position:0% it's also has uh plugs on the back so in some<13:58:47.700> ways<13:58:47.936> it<13:58:48.240> acts<13:58:48.540> as<13:58:48.660> a<13:58:48.776> switch<13:58:48.956> for<13:58:49.256> us 13:58:49.370 --> 13:58:49.380 align:start position:0% some ways it acts as a switch for us 13:58:49.380 --> 13:58:51.106 align:start position:0% some ways it acts as a switch for us although<13:58:49.740> that's<13:58:49.916> built<13:58:50.340> into<13:58:50.456> a<13:58:50.700> router<13:58:51.000> so 13:58:51.106 --> 13:58:51.116 align:start position:0% although that's built into a router so 13:58:51.116 --> 13:58:52.310 align:start position:0% although that's built into a router so I'm<13:58:51.240> not<13:58:51.360> going<13:58:51.480> to<13:58:51.540> write<13:58:51.660> that<13:58:51.840> separately 13:58:52.310 --> 13:58:52.320 align:start position:0% I'm not going to write that separately 13:58:52.320 --> 13:58:55.630 align:start position:0% I'm not going to write that separately it<13:58:53.220> does<13:58:53.400> something<13:58:53.700> called<13:58:54.116> Network<13:58:54.840> address 13:58:55.630 --> 13:58:55.640 align:start position:0% it does something called Network address 13:58:55.640 --> 13:58:58.906 align:start position:0% it does something called Network address translation<13:58:56.640> which<13:58:57.540> allows<13:58:57.956> the<13:58:58.380> IP<13:58:58.680> address 13:58:58.906 --> 13:58:58.916 align:start position:0% translation which allows the IP address 13:58:58.916 --> 13:59:00.650 align:start position:0% translation which allows the IP address coming<13:58:59.340> from<13:58:59.756> our<13:59:00.116> internet<13:59:00.300> service 13:59:00.650 --> 13:59:00.660 align:start position:0% coming from our internet service 13:59:00.660 --> 13:59:03.230 align:start position:0% coming from our internet service provider<13:59:01.256> on<13:59:01.500> our<13:59:01.680> modem<13:59:02.096> which<13:59:02.756> might<13:59:03.060> be 13:59:03.230 --> 13:59:03.240 align:start position:0% provider on our modem which might be 13:59:03.240 --> 13:59:07.330 align:start position:0% provider on our modem which might be let's<13:59:03.596> say 13:59:07.330 --> 13:59:07.340 align:start position:0% 13:59:07.340 --> 13:59:11.030 align:start position:0% 126.43.17.3<13:59:08.360> to<13:59:09.360> be<13:59:09.660> shared<13:59:10.200> among<13:59:10.616> three 13:59:11.030 --> 13:59:11.040 align:start position:0% 126.43.17.3 to be shared among three 13:59:11.040 --> 13:59:14.870 align:start position:0% 126.43.17.3 to be shared among three different<13:59:11.660> uh<13:59:12.660> internal<13:59:13.436> devices 13:59:14.870 --> 13:59:14.880 align:start position:0% different uh internal devices 13:59:14.880 --> 13:59:18.586 align:start position:0% different uh internal devices so<13:59:15.660> that<13:59:16.256> way<13:59:16.436> when<13:59:17.220> information<13:59:17.700> comes<13:59:18.480> in 13:59:18.586 --> 13:59:18.596 align:start position:0% so that way when information comes in 13:59:18.596 --> 13:59:20.990 align:start position:0% so that way when information comes in from<13:59:18.776> the<13:59:18.956> internet<13:59:19.080> it<13:59:20.040> knows<13:59:20.400> which<13:59:20.700> device 13:59:20.990 --> 13:59:21.000 align:start position:0% from the internet it knows which device 13:59:21.000 --> 13:59:23.690 align:start position:0% from the internet it knows which device to<13:59:21.540> send<13:59:21.776> it<13:59:22.200> out<13:59:22.380> to 13:59:23.690 --> 13:59:23.700 align:start position:0% to send it out to 13:59:23.700 --> 13:59:25.790 align:start position:0% to send it out to and<13:59:24.116> also<13:59:24.416> does<13:59:24.540> a<13:59:24.720> couple<13:59:24.840> other<13:59:25.080> things<13:59:25.436> for 13:59:25.790 --> 13:59:25.800 align:start position:0% and also does a couple other things for 13:59:25.800 --> 13:59:28.490 align:start position:0% and also does a couple other things for instance<13:59:26.040> it<13:59:26.340> might<13:59:26.520> have<13:59:26.700> a<13:59:26.936> firewall 13:59:28.490 --> 13:59:28.500 align:start position:0% instance it might have a firewall 13:59:28.500 --> 13:59:30.406 align:start position:0% instance it might have a firewall and<13:59:29.220> to<13:59:29.340> do<13:59:29.580> some<13:59:29.700> other<13:59:29.820> stuff<13:59:30.060> we've 13:59:30.406 --> 13:59:30.416 align:start position:0% and to do some other stuff we've 13:59:30.416 --> 13:59:32.150 align:start position:0% and to do some other stuff we've mentioned<13:59:30.900> as<13:59:31.140> well 13:59:32.150 --> 13:59:32.160 align:start position:0% mentioned as well 13:59:32.160 --> 13:59:34.670 align:start position:0% mentioned as well no<13:59:32.756> matter<13:59:33.000> and<13:59:33.540> it<13:59:33.660> might<13:59:33.840> even<13:59:34.020> allow<13:59:34.500> for 13:59:34.670 --> 13:59:34.680 align:start position:0% no matter and it might even allow for 13:59:34.680 --> 13:59:36.406 align:start position:0% no matter and it might even allow for vlans<13:59:35.340> actually 13:59:36.406 --> 13:59:36.416 align:start position:0% vlans actually 13:59:36.416 --> 13:59:38.510 align:start position:0% vlans actually but<13:59:36.840> no<13:59:37.020> matter<13:59:37.200> you<13:59:37.560> can<13:59:37.680> see<13:59:37.800> that<13:59:37.980> this<13:59:38.220> one 13:59:38.510 --> 13:59:38.520 align:start position:0% but no matter you can see that this one 13:59:38.520 --> 13:59:41.510 align:start position:0% but no matter you can see that this one device<13:59:38.820> is<13:59:39.416> taking<13:59:39.660> on<13:59:39.956> several<13:59:40.916> devices<13:59:41.220> that 13:59:41.510 --> 13:59:41.520 align:start position:0% device is taking on several devices that 13:59:41.520 --> 13:59:43.730 align:start position:0% device is taking on several devices that we've<13:59:41.756> talked<13:59:42.060> about<13:59:42.116> previously 13:59:43.730 --> 13:59:43.740 align:start position:0% we've talked about previously 13:59:43.740 --> 13:59:47.330 align:start position:0% we've talked about previously this<13:59:44.340> was<13:59:44.520> your<13:59:44.880> only<13:59:45.180> uh<13:59:46.256> experience<13:59:46.916> with<13:59:47.220> a 13:59:47.330 --> 13:59:47.340 align:start position:0% this was your only uh experience with a 13:59:47.340 --> 13:59:49.246 align:start position:0% this was your only uh experience with a router<13:59:47.700> and<13:59:48.116> you<13:59:48.300> might<13:59:48.416> think<13:59:48.596> all<13:59:48.776> routers 13:59:49.246 --> 13:59:49.256 align:start position:0% router and you might think all routers 13:59:49.256 --> 13:59:51.230 align:start position:0% router and you might think all routers operate<13:59:49.680> this<13:59:49.916> way<13:59:50.096> in<13:59:50.340> fact<13:59:50.520> they<13:59:50.756> don't<13:59:50.880> we 13:59:51.230 --> 13:59:51.240 align:start position:0% operate this way in fact they don't we 13:59:51.240 --> 13:59:53.746 align:start position:0% operate this way in fact they don't we just<13:59:51.416> call<13:59:51.720> it<13:59:51.956> a<13:59:52.436> router<13:59:52.980> because<13:59:53.220> that's 13:59:53.746 --> 13:59:53.756 align:start position:0% just call it a router because that's 13:59:53.756 --> 13:59:55.490 align:start position:0% just call it a router because that's probably<13:59:54.000> the<13:59:54.300> most<13:59:54.416> important<13:59:54.900> function<13:59:55.256> it 13:59:55.490 --> 13:59:55.500 align:start position:0% probably the most important function it 13:59:55.500 --> 13:59:57.470 align:start position:0% probably the most important function it does<13:59:55.680> which<13:59:55.980> allows<13:59:56.580> us<13:59:56.700> to<13:59:56.936> get<13:59:57.060> out<13:59:57.180> to<13:59:57.300> the 13:59:57.470 --> 13:59:57.480 align:start position:0% does which allows us to get out to the 13:59:57.480 --> 13:59:58.426 align:start position:0% does which allows us to get out to the network 13:59:58.426 --> 13:59:58.436 align:start position:0% network 13:59:58.436 --> 14:00:01.310 align:start position:0% network but<13:59:59.040> there's<13:59:59.700> not<14:00:00.000> floors<14:00:00.596> and<14:00:00.776> floors<14:00:01.140> and 14:00:01.310 --> 14:00:01.320 align:start position:0% but there's not floors and floors and 14:00:01.320 --> 14:00:03.530 align:start position:0% but there's not floors and floors and floors<14:00:01.680> of<14:00:01.860> stuff<14:00:02.096> going<14:00:02.400> on<14:00:02.580> here<14:00:02.880> and<14:00:03.360> this 14:00:03.530 --> 14:00:03.540 align:start position:0% floors of stuff going on here and this 14:00:03.540 --> 14:00:05.570 align:start position:0% floors of stuff going on here and this router<14:00:03.956> wouldn't<14:00:04.140> do<14:00:04.436> very<14:00:04.740> well 14:00:05.570 --> 14:00:05.580 align:start position:0% router wouldn't do very well 14:00:05.580 --> 14:00:07.730 align:start position:0% router wouldn't do very well is<14:00:05.936> because<14:00:06.116> it's<14:00:06.300> not<14:00:06.480> built<14:00:06.840> to<14:00:06.900> if<14:00:07.380> I<14:00:07.560> tried 14:00:07.730 --> 14:00:07.740 align:start position:0% is because it's not built to if I tried 14:00:07.740 --> 14:00:10.606 align:start position:0% is because it's not built to if I tried plugging<14:00:08.160> a<14:00:08.456> hundred<14:00:08.700> computers<14:00:09.180> up<14:00:09.416> to<14:00:09.540> it<14:00:10.080> so 14:00:10.606 --> 14:00:10.616 align:start position:0% plugging a hundred computers up to it so 14:00:10.616 --> 14:00:13.070 align:start position:0% plugging a hundred computers up to it so the<14:00:11.276> real<14:00:11.456> important<14:00:11.880> thing<14:00:12.116> here<14:00:12.360> is<14:00:12.540> as<14:00:12.900> you 14:00:13.070 --> 14:00:13.080 align:start position:0% the real important thing here is as you 14:00:13.080 --> 14:00:15.350 align:start position:0% the real important thing here is as you go<14:00:13.256> forward<14:00:13.560> in<14:00:14.160> your<14:00:14.340> career<14:00:14.700> you'll 14:00:15.350 --> 14:00:15.360 align:start position:0% go forward in your career you'll 14:00:15.360 --> 14:00:16.906 align:start position:0% go forward in your career you'll probably<14:00:15.540> be<14:00:15.660> seeing<14:00:15.956> more<14:00:16.200> and<14:00:16.380> more<14:00:16.616> of<14:00:16.740> this 14:00:16.906 --> 14:00:16.916 align:start position:0% probably be seeing more and more of this 14:00:16.916 --> 14:00:17.990 align:start position:0% probably be seeing more and more of this and<14:00:17.096> if<14:00:17.276> you're<14:00:17.340> going<14:00:17.456> to<14:00:17.520> be<14:00:17.640> supporting 14:00:17.990 --> 14:00:18.000 align:start position:0% and if you're going to be supporting 14:00:18.000 --> 14:00:20.810 align:start position:0% and if you're going to be supporting homes<14:00:18.300> or<14:00:18.776> really<14:00:19.320> small<14:00:19.616> businesses<14:00:20.276> then 14:00:20.810 --> 14:00:20.820 align:start position:0% homes or really small businesses then 14:00:20.820 --> 14:00:22.490 align:start position:0% homes or really small businesses then you<14:00:21.060> want<14:00:21.116> to<14:00:21.300> know<14:00:21.480> that<14:00:21.840> perhaps<14:00:22.140> they<14:00:22.380> don't 14:00:22.490 --> 14:00:22.500 align:start position:0% you want to know that perhaps they don't 14:00:22.500 --> 14:00:24.650 align:start position:0% you want to know that perhaps they don't need<14:00:22.740> a<14:00:23.040> separate<14:00:23.276> switch<14:00:23.520> and<14:00:23.756> router<14:00:24.180> they 14:00:24.650 --> 14:00:24.660 align:start position:0% need a separate switch and router they 14:00:24.660 --> 14:00:26.990 align:start position:0% need a separate switch and router they just<14:00:24.840> need<14:00:25.020> one<14:00:25.320> device<14:00:25.560> that<14:00:26.276> being<14:00:26.456> said<14:00:26.700> if 14:00:26.990 --> 14:00:27.000 align:start position:0% just need one device that being said if 14:00:27.000 --> 14:00:29.810 align:start position:0% just need one device that being said if a<14:00:27.240> company<14:00:27.596> is<14:00:27.900> growing<14:00:28.320> really<14:00:28.616> fast<14:00:28.980> perhaps 14:00:29.810 --> 14:00:29.820 align:start position:0% a company is growing really fast perhaps 14:00:29.820 --> 14:00:31.670 align:start position:0% a company is growing really fast perhaps they<14:00:30.116> need<14:00:30.300> to<14:00:30.540> purchase<14:00:30.900> a<14:00:31.140> separate<14:00:31.436> switch 14:00:31.670 --> 14:00:31.680 align:start position:0% they need to purchase a separate switch 14:00:31.680 --> 14:00:33.890 align:start position:0% they need to purchase a separate switch that<14:00:32.040> then<14:00:32.220> plugs<14:00:32.580> into<14:00:32.820> the<14:00:33.060> router<14:00:33.416> the 14:00:33.890 --> 14:00:33.900 align:start position:0% that then plugs into the router the 14:00:33.900 --> 14:00:36.050 align:start position:0% that then plugs into the router the switch<14:00:34.080> therefore<14:00:34.616> can<14:00:34.916> help<14:00:35.160> work<14:00:35.756> with 14:00:36.050 --> 14:00:36.060 align:start position:0% switch therefore can help work with 14:00:36.060 --> 14:00:38.330 align:start position:0% switch therefore can help work with traffic<14:00:36.300> internally<14:00:36.956> of<14:00:37.200> the<14:00:37.320> network<14:00:37.500> and 14:00:38.330 --> 14:00:38.340 align:start position:0% traffic internally of the network and 14:00:38.340 --> 14:00:40.246 align:start position:0% traffic internally of the network and the<14:00:38.520> router<14:00:38.936> will<14:00:39.416> help<14:00:39.596> get<14:00:39.840> the<14:00:40.080> information 14:00:40.246 --> 14:00:40.256 align:start position:0% the router will help get the information 14:00:40.256 --> 14:00:42.170 align:start position:0% the router will help get the information out<14:00:40.800> onto<14:00:41.096> the<14:00:41.276> network 14:00:42.170 --> 14:00:42.180 align:start position:0% out onto the network 14:00:42.180 --> 14:00:44.210 align:start position:0% out onto the network but<14:00:42.660> it's<14:00:42.776> important<14:00:43.140> again<14:00:43.320> to<14:00:43.616> realize<14:00:43.916> that 14:00:44.210 --> 14:00:44.220 align:start position:0% but it's important again to realize that 14:00:44.220 --> 14:00:46.246 align:start position:0% but it's important again to realize that even<14:00:44.400> though<14:00:44.700> this<14:00:45.180> is<14:00:45.300> a<14:00:45.480> small<14:00:45.596> office<14:00:45.840> home 14:00:46.246 --> 14:00:46.256 align:start position:0% even though this is a small office home 14:00:46.256 --> 14:00:49.010 align:start position:0% even though this is a small office home office<14:00:46.500> or<14:00:47.096> Soho<14:00:47.640> that's<14:00:48.180> not<14:00:48.360> the<14:00:48.596> area<14:00:48.720> or 14:00:49.010 --> 14:00:49.020 align:start position:0% office or Soho that's not the area or 14:00:49.020 --> 14:00:51.106 align:start position:0% office or Soho that's not the area or the<14:00:49.200> geographic<14:00:49.616> location<14:00:49.860> remember<14:00:50.340> that's 14:00:51.106 --> 14:00:51.116 align:start position:0% the geographic location remember that's 14:00:51.116 --> 14:00:52.690 align:start position:0% the geographic location remember that's just<14:00:51.360> the<14:00:51.596> name<14:00:51.720> of<14:00:51.956> this<14:00:52.140> type<14:00:52.320> of<14:00:52.436> network 14:00:52.690 --> 14:00:52.700 align:start position:0% just the name of this type of network 14:00:52.700 --> 14:00:55.370 align:start position:0% just the name of this type of network that<14:00:53.700> it's<14:00:54.116> going<14:00:54.300> to<14:00:54.480> have<14:00:54.720> all<14:00:55.080> the<14:00:55.256> same 14:00:55.370 --> 14:00:55.380 align:start position:0% that it's going to have all the same 14:00:55.380 --> 14:00:57.710 align:start position:0% that it's going to have all the same principles<14:00:55.916> apply<14:00:56.400> it's<14:00:57.000> just<14:00:57.240> the<14:00:57.416> devices 14:00:57.710 --> 14:00:57.720 align:start position:0% principles apply it's just the devices 14:00:57.720 --> 14:01:01.010 align:start position:0% principles apply it's just the devices might<14:00:58.140> be<14:00:58.320> smaller<14:00:58.800> and<14:00:59.520> less<14:00:59.756> able<14:01:00.180> to<14:01:00.300> handle 14:01:01.010 --> 14:01:01.020 align:start position:0% might be smaller and less able to handle 14:01:01.020 --> 14:01:03.406 align:start position:0% might be smaller and less able to handle a<14:01:01.436> lot<14:01:01.560> of<14:01:01.740> people 14:01:03.406 --> 14:01:03.416 align:start position:0% a lot of people 14:01:03.416 --> 14:01:07.190 align:start position:0% a lot of people so<14:01:04.020> we've<14:01:04.740> talked<14:01:05.096> about<14:01:05.480> uh<14:01:06.480> virtual<14:01:06.956> local 14:01:07.190 --> 14:01:07.200 align:start position:0% so we've talked about uh virtual local 14:01:07.200 --> 14:01:09.290 align:start position:0% so we've talked about uh virtual local area<14:01:07.500> network<14:01:07.916> which<14:01:08.640> is<14:01:08.820> basically 14:01:09.290 --> 14:01:09.300 align:start position:0% area network which is basically 14:01:09.300 --> 14:01:13.150 align:start position:0% area network which is basically segmenting 14:01:13.150 --> 14:01:13.160 align:start position:0% 14:01:13.160 --> 14:01:16.790 align:start position:0% a<14:01:14.160> lan<14:01:14.820> or<14:01:14.936> local<14:01:15.116> area<14:01:15.416> network<14:01:15.720> into<14:01:16.256> several 14:01:16.790 --> 14:01:16.800 align:start position:0% a lan or local area network into several 14:01:16.800 --> 14:01:19.426 align:start position:0% a lan or local area network into several logical<14:01:17.160> partitions 14:01:19.426 --> 14:01:19.436 align:start position:0% logical partitions 14:01:19.436 --> 14:01:22.906 align:start position:0% logical partitions but<14:01:20.040> physically<14:01:20.520> everything<14:01:21.300> is<14:01:21.900> exactly<14:01:22.560> the 14:01:22.906 --> 14:01:22.916 align:start position:0% but physically everything is exactly the 14:01:22.916 --> 14:01:25.246 align:start position:0% but physically everything is exactly the same 14:01:25.246 --> 14:01:25.256 align:start position:0% 14:01:25.256 --> 14:01:26.746 align:start position:0% we<14:01:25.680> talked<14:01:25.916> about<14:01:25.980> how<14:01:26.276> we<14:01:26.456> do<14:01:26.580> the 14:01:26.746 --> 14:01:26.756 align:start position:0% we talked about how we do the 14:01:26.756 --> 14:01:29.086 align:start position:0% we talked about how we do the memberships<14:01:27.180> for<14:01:27.540> these<14:01:27.776> we<14:01:28.380> can<14:01:28.500> do<14:01:28.616> it<14:01:28.740> based 14:01:29.086 --> 14:01:29.096 align:start position:0% memberships for these we can do it based 14:01:29.096 --> 14:01:31.190 align:start position:0% memberships for these we can do it based on<14:01:29.160> the<14:01:29.340> port<14:01:29.456> it's<14:01:29.756> plugged<14:01:30.116> into 14:01:31.190 --> 14:01:31.200 align:start position:0% on the port it's plugged into 14:01:31.200 --> 14:01:33.530 align:start position:0% on the port it's plugged into we<14:01:31.616> can<14:01:31.740> also<14:01:31.980> do<14:01:32.096> it<14:01:32.276> based<14:01:32.700> on<14:01:32.820> the<14:01:33.360> Mac 14:01:33.530 --> 14:01:33.540 align:start position:0% we can also do it based on the Mac 14:01:33.540 --> 14:01:34.670 align:start position:0% we can also do it based on the Mac address 14:01:34.670 --> 14:01:34.680 align:start position:0% address 14:01:34.680 --> 14:01:36.650 align:start position:0% address or<14:01:35.040> based<14:01:35.400> on<14:01:35.456> the<14:01:35.640> protocol 14:01:36.650 --> 14:01:36.660 align:start position:0% or based on the protocol 14:01:36.660 --> 14:01:38.446 align:start position:0% or based on the protocol which<14:01:37.020> in<14:01:37.256> some<14:01:37.436> ways<14:01:37.740> would<14:01:37.916> be<14:01:38.040> linked<14:01:38.340> to 14:01:38.446 --> 14:01:38.456 align:start position:0% which in some ways would be linked to 14:01:38.456 --> 14:01:40.190 align:start position:0% which in some ways would be linked to the<14:01:38.700> IP<14:01:39.000> address 14:01:40.190 --> 14:01:40.200 align:start position:0% the IP address 14:01:40.200 --> 14:01:43.010 align:start position:0% the IP address finally<14:01:40.740> we<14:01:40.980> talked<14:01:41.220> about<14:01:41.340> a<14:01:41.820> Soho<14:01:42.720> Network 14:01:43.010 --> 14:01:43.020 align:start position:0% finally we talked about a Soho Network 14:01:43.020 --> 14:01:44.690 align:start position:0% finally we talked about a Soho Network or<14:01:43.320> small<14:01:43.560> office<14:01:43.800> home<14:01:44.096> office<14:01:44.340> Network 14:01:44.690 --> 14:01:44.700 align:start position:0% or small office home office Network 14:01:44.700 --> 14:01:46.490 align:start position:0% or small office home office Network which<14:01:45.480> the<14:01:45.660> real<14:01:45.776> reason<14:01:45.956> we<14:01:46.140> want<14:01:46.256> to<14:01:46.380> know 14:01:46.490 --> 14:01:46.500 align:start position:0% which the real reason we want to know 14:01:46.500 --> 14:01:49.730 align:start position:0% which the real reason we want to know that<14:01:46.680> is<14:01:46.916> because<14:01:47.160> the<14:01:47.880> devices<14:01:48.320> are<14:01:49.320> going<14:01:49.500> to 14:01:49.730 --> 14:01:49.740 align:start position:0% that is because the devices are going to 14:01:49.740 --> 14:01:53.210 align:start position:0% that is because the devices are going to be<14:01:50.000> less<14:01:51.000> powerful 14:01:53.210 --> 14:01:53.220 align:start position:0% be less powerful 14:01:53.220 --> 14:01:54.050 align:start position:0% be less powerful okay 14:01:54.050 --> 14:01:54.060 align:start position:0% okay 14:01:54.060 --> 14:01:57.710 align:start position:0% okay and<14:01:55.020> they're<14:01:55.680> going<14:01:55.980> to<14:01:56.520> sort<14:01:57.000> of<14:01:57.116> converge 14:01:57.710 --> 14:01:57.720 align:start position:0% and they're going to sort of converge 14:01:57.720 --> 14:01:59.810 align:start position:0% and they're going to sort of converge meaning<14:01:58.380> that<14:01:58.616> we're<14:01:58.800> going<14:01:58.980> to<14:01:59.160> have<14:01:59.520> a 14:01:59.810 --> 14:01:59.820 align:start position:0% meaning that we're going to have a 14:01:59.820 --> 14:02:01.670 align:start position:0% meaning that we're going to have a wireless<14:02:00.116> access<14:02:00.480> point<14:02:00.840> that's<14:02:01.200> also<14:02:01.560> a 14:02:01.670 --> 14:02:01.680 align:start position:0% wireless access point that's also a 14:02:01.680 --> 14:02:04.550 align:start position:0% wireless access point that's also a router<14:02:02.040> that's<14:02:02.580> also<14:02:02.880> a<14:02:03.060> DHCP<14:02:03.596> server<14:02:04.020> whereas 14:02:04.550 --> 14:02:04.560 align:start position:0% router that's also a DHCP server whereas 14:02:04.560 --> 14:02:06.350 align:start position:0% router that's also a DHCP server whereas in<14:02:04.740> a<14:02:04.860> large<14:02:04.980> Network<14:02:05.220> we<14:02:05.580> would<14:02:05.756> separate<14:02:06.116> all 14:02:06.350 --> 14:02:06.360 align:start position:0% in a large Network we would separate all 14:02:06.360 --> 14:02:08.390 align:start position:0% in a large Network we would separate all of<14:02:06.540> this<14:02:06.776> out 14:02:08.390 --> 14:02:08.400 align:start position:0% of this out 14:02:08.400 --> 14:02:10.490 align:start position:0% of this out so<14:02:08.880> that's<14:02:09.360> sort<14:02:09.596> of 14:02:10.490 --> 14:02:10.500 align:start position:0% so that's sort of 14:02:10.500 --> 14:02:12.586 align:start position:0% so that's sort of finishes<14:02:11.276> our<14:02:11.520> discussion<14:02:11.936> on<14:02:12.180> local<14:02:12.360> area 14:02:12.586 --> 14:02:12.596 align:start position:0% finishes our discussion on local area 14:02:12.596 --> 14:02:15.766 align:start position:0% finishes our discussion on local area networks<14:02:13.200> and<14:02:13.380> lands<14:02:13.860> the<14:02:14.580> next<14:02:14.700> lesson<14:02:15.300> is 14:02:15.766 --> 14:02:15.776 align:start position:0% networks and lands the next lesson is 14:02:15.776 --> 14:02:18.470 align:start position:0% networks and lands the next lesson is going<14:02:15.956> to<14:02:16.200> talk<14:02:16.500> about<14:02:16.820> wide<14:02:17.820> area<14:02:18.000> networks 14:02:18.470 --> 14:02:18.480 align:start position:0% going to talk about wide area networks 14:02:18.480 --> 14:02:20.810 align:start position:0% going to talk about wide area networks or<14:02:18.900> wans<14:02:19.680> which<14:02:19.980> we've<14:02:20.220> already<14:02:20.400> talked<14:02:20.700> about 14:02:20.810 --> 14:02:20.820 align:start position:0% or wans which we've already talked about 14:02:20.820 --> 14:02:22.970 align:start position:0% or wans which we've already talked about slightly<14:02:21.540> when<14:02:21.776> dealing<14:02:22.140> with<14:02:22.200> routing<14:02:22.616> but 14:02:22.970 --> 14:02:22.980 align:start position:0% slightly when dealing with routing but 14:02:22.980 --> 14:02:24.766 align:start position:0% slightly when dealing with routing but we're<14:02:23.096> going<14:02:23.220> to<14:02:23.340> talk<14:02:23.456> about<14:02:23.640> that<14:02:23.936> in<14:02:24.240> a<14:02:24.360> bit 14:02:24.766 --> 14:02:24.776 align:start position:0% we're going to talk about that in a bit 14:02:24.776 --> 14:02:26.690 align:start position:0% we're going to talk about that in a bit more<14:02:24.900> depth 14:02:26.690 --> 14:02:26.700 align:start position:0% more depth 14:02:26.700 --> 14:02:28.790 align:start position:0% more depth vlans<14:02:27.660> and<14:02:27.776> drugs 14:02:28.790 --> 14:02:28.800 align:start position:0% vlans and drugs 14:02:28.800 --> 14:02:31.490 align:start position:0% vlans and drugs we'll<14:02:29.276> be<14:02:29.400> doing<14:02:29.580> some<14:02:29.880> Labs<14:02:30.240> on<14:02:30.416> this<14:02:30.596> as<14:02:31.320> we 14:02:31.490 --> 14:02:31.500 align:start position:0% we'll be doing some Labs on this as we 14:02:31.500 --> 14:02:33.766 align:start position:0% we'll be doing some Labs on this as we go<14:02:31.616> through<14:02:31.740> the<14:02:31.916> course<14:02:32.096> so<14:02:32.340> don't<14:02:32.640> worry 14:02:33.766 --> 14:02:33.776 align:start position:0% go through the course so don't worry 14:02:33.776 --> 14:02:36.406 align:start position:0% go through the course so don't worry um<14:02:33.840> if<14:02:34.200> it<14:02:34.320> doesn't<14:02:34.500> sink<14:02:34.740> in<14:02:34.916> straight<14:02:35.160> away 14:02:36.406 --> 14:02:36.416 align:start position:0% um if it doesn't sink in straight away 14:02:36.416 --> 14:02:38.870 align:start position:0% um if it doesn't sink in straight away a<14:02:36.776> VLAN<14:02:37.320> is<14:02:37.500> a<14:02:37.680> virtual<14:02:37.980> local<14:02:38.220> area<14:02:38.520> network 14:02:38.870 --> 14:02:38.880 align:start position:0% a VLAN is a virtual local area network 14:02:38.880 --> 14:02:41.330 align:start position:0% a VLAN is a virtual local area network so<14:02:39.240> it's<14:02:39.416> not<14:02:39.540> something<14:02:39.776> you<14:02:40.080> can<14:02:40.256> see<14:02:40.560> by 14:02:41.330 --> 14:02:41.340 align:start position:0% so it's not something you can see by 14:02:41.340 --> 14:02:42.890 align:start position:0% so it's not something you can see by physically<14:02:41.756> looking<14:02:41.936> at<14:02:42.180> the<14:02:42.300> network<14:02:42.416> you'd 14:02:42.890 --> 14:02:42.900 align:start position:0% physically looking at the network you'd 14:02:42.900 --> 14:02:45.230 align:start position:0% physically looking at the network you'd have<14:02:42.956> to<14:02:43.080> look<14:02:43.256> at<14:02:43.436> the<14:02:43.740> configuration<14:02:44.640> of<14:02:45.000> the 14:02:45.230 --> 14:02:45.240 align:start position:0% have to look at the configuration of the 14:02:45.240 --> 14:02:46.730 align:start position:0% have to look at the configuration of the switches 14:02:46.730 --> 14:02:46.740 align:start position:0% switches 14:02:46.740 --> 14:02:48.710 align:start position:0% switches it<14:02:47.160> defines<14:02:47.520> a<14:02:47.700> broadcast<14:02:47.820> domain<14:02:48.416> in<14:02:48.596> the 14:02:48.710 --> 14:02:48.720 align:start position:0% it defines a broadcast domain in the 14:02:48.720 --> 14:02:50.150 align:start position:0% it defines a broadcast domain in the layer<14:02:49.020> 2<14:02:49.140> Network 14:02:50.150 --> 14:02:50.160 align:start position:0% layer 2 Network 14:02:50.160 --> 14:02:53.210 align:start position:0% layer 2 Network so<14:02:51.000> just<14:02:51.596> the<14:02:51.840> same<14:02:52.020> as 14:02:53.210 --> 14:02:53.220 align:start position:0% so just the same as 14:02:53.220 --> 14:02:56.446 align:start position:0% so just the same as local<14:02:53.880> area<14:02:54.180> network<14:02:54.416> using<14:02:54.900> the<14:02:55.020> switch 14:02:56.446 --> 14:02:56.456 align:start position:0% local area network using the switch 14:02:56.456 --> 14:02:59.446 align:start position:0% local area network using the switch the<14:02:57.240> switch<14:02:57.416> will<14:02:57.900> forward<14:02:58.456> broadcasts 14:02:59.446 --> 14:02:59.456 align:start position:0% the switch will forward broadcasts 14:02:59.456 --> 14:03:01.970 align:start position:0% the switch will forward broadcasts however<14:02:59.820> if<14:03:00.116> you<14:03:00.300> have<14:03:00.540> two<14:03:01.080> vlans<14:03:01.616> on<14:03:01.860> a 14:03:01.970 --> 14:03:01.980 align:start position:0% however if you have two vlans on a 14:03:01.980 --> 14:03:03.650 align:start position:0% however if you have two vlans on a switch<14:03:02.160> for<14:03:02.520> example<14:03:02.820> the<14:03:03.180> one<14:03:03.240> on<14:03:03.416> the<14:03:03.540> top 14:03:03.650 --> 14:03:03.660 align:start position:0% switch for example the one on the top 14:03:03.660 --> 14:03:05.446 align:start position:0% switch for example the one on the top right<14:03:03.840> diagram<14:03:04.500> there 14:03:05.446 --> 14:03:05.456 align:start position:0% right diagram there 14:03:05.456 --> 14:03:07.426 align:start position:0% right diagram there the<14:03:05.880> broadcast<14:03:06.060> will<14:03:06.416> stop<14:03:06.720> as<14:03:06.956> far<14:03:07.140> as<14:03:07.256> the 14:03:07.426 --> 14:03:07.436 align:start position:0% the broadcast will stop as far as the 14:03:07.436 --> 14:03:10.906 align:start position:0% the broadcast will stop as far as the VLAN<14:03:07.800> reason<14:03:08.400> is<14:03:08.700> you<14:03:08.880> need<14:03:09.060> a<14:03:09.300> layer<14:03:09.596> 3<14:03:09.720> device 14:03:10.906 --> 14:03:10.916 align:start position:0% VLAN reason is you need a layer 3 device 14:03:10.916 --> 14:03:13.870 align:start position:0% VLAN reason is you need a layer 3 device which<14:03:11.340> is<14:03:11.456> normally<14:03:11.820> a<14:03:12.060> router<14:03:12.480> in<14:03:13.140> order<14:03:13.320> to 14:03:13.870 --> 14:03:13.880 align:start position:0% which is normally a router in order to 14:03:13.880 --> 14:03:16.490 align:start position:0% which is normally a router in order to send<14:03:14.880> information<14:03:15.180> from<14:03:15.660> one<14:03:15.900> network<14:03:16.140> to 14:03:16.490 --> 14:03:16.500 align:start position:0% send information from one network to 14:03:16.500 --> 14:03:18.670 align:start position:0% send information from one network to another<14:03:16.680> so<14:03:17.340> virtual<14:03:17.820> local<14:03:18.000> area<14:03:18.240> network 14:03:18.670 --> 14:03:18.680 align:start position:0% another so virtual local area network 14:03:18.680 --> 14:03:21.946 align:start position:0% another so virtual local area network for<14:03:19.680> all<14:03:19.860> intents<14:03:20.456> and<14:03:20.580> purposes<14:03:21.060> it<14:03:21.416> follows 14:03:21.946 --> 14:03:21.956 align:start position:0% for all intents and purposes it follows 14:03:21.956 --> 14:03:24.290 align:start position:0% for all intents and purposes it follows the<14:03:22.080> same<14:03:22.200> rule<14:03:22.500> as<14:03:22.680> a<14:03:22.980> normal<14:03:23.700> Network<14:03:24.000> or 14:03:24.290 --> 14:03:24.300 align:start position:0% the same rule as a normal Network or 14:03:24.300 --> 14:03:27.230 align:start position:0% the same rule as a normal Network or subnet 14:03:27.230 --> 14:03:27.240 align:start position:0% 14:03:27.240 --> 14:03:30.230 align:start position:0% so<14:03:28.140> you<14:03:28.680> can<14:03:28.860> separate<14:03:29.160> broadcast<14:03:29.456> domains 14:03:30.230 --> 14:03:30.240 align:start position:0% so you can separate broadcast domains 14:03:30.240 --> 14:03:31.606 align:start position:0% so you can separate broadcast domains even<14:03:30.480> though<14:03:30.596> it's<14:03:30.776> on<14:03:30.956> the<14:03:31.140> same<14:03:31.320> physical 14:03:31.606 --> 14:03:31.616 align:start position:0% even though it's on the same physical 14:03:31.616 --> 14:03:36.766 align:start position:0% even though it's on the same physical switch<14:03:32.040> by<14:03:32.520> configuring<14:03:33.240> a<14:03:33.480> layer<14:03:33.900> 2. 14:03:36.766 --> 14:03:36.776 align:start position:0% 14:03:36.776 --> 14:03:39.290 align:start position:0% a<14:03:37.436> VLAN<14:03:37.980> is<14:03:38.096> a<14:03:38.276> logical<14:03:38.520> division<14:03:38.880> of<14:03:39.060> switch 14:03:39.290 --> 14:03:39.300 align:start position:0% a VLAN is a logical division of switch 14:03:39.300 --> 14:03:42.230 align:start position:0% a VLAN is a logical division of switch ports<14:03:39.840> so<14:03:40.320> if<14:03:40.680> you<14:03:40.800> had<14:03:40.980> 20 14:03:42.230 --> 14:03:42.240 align:start position:0% ports so if you had 20 14:03:42.240 --> 14:03:44.390 align:start position:0% ports so if you had 20 switch<14:03:42.776> ports<14:03:43.320> physically<14:03:43.740> on<14:03:44.096> the<14:03:44.220> switch 14:03:44.390 --> 14:03:44.400 align:start position:0% switch ports physically on the switch 14:03:44.400 --> 14:03:47.870 align:start position:0% switch ports physically on the switch you<14:03:44.880> could<14:03:45.060> in<14:03:45.720> theory<14:03:46.020> have<14:03:46.380> 20<14:03:46.980> different 14:03:47.870 --> 14:03:47.880 align:start position:0% you could in theory have 20 different 14:03:47.880 --> 14:03:48.650 align:start position:0% you could in theory have 20 different um 14:03:48.650 --> 14:03:48.660 align:start position:0% um 14:03:48.660 --> 14:03:52.490 align:start position:0% um devices<14:03:49.320> each<14:03:49.680> in<14:03:49.860> its<14:03:50.160> own<14:03:50.160> VLAN 14:03:52.490 --> 14:03:52.500 align:start position:0% devices each in its own VLAN 14:03:52.500 --> 14:03:54.106 align:start position:0% devices each in its own VLAN you<14:03:52.800> need<14:03:52.916> a<14:03:53.096> router<14:03:53.340> to<14:03:53.520> pass<14:03:53.700> packets 14:03:54.106 --> 14:03:54.116 align:start position:0% you need a router to pass packets 14:03:54.116 --> 14:03:56.570 align:start position:0% you need a router to pass packets between<14:03:54.416> vlans<14:03:55.080> some<14:03:55.740> switches<14:03:56.340> actually 14:03:56.570 --> 14:03:56.580 align:start position:0% between vlans some switches actually 14:03:56.580 --> 14:03:57.946 align:start position:0% between vlans some switches actually come<14:03:56.820> with<14:03:57.116> a 14:03:57.946 --> 14:03:57.956 align:start position:0% come with a 14:03:57.956 --> 14:04:01.070 align:start position:0% come with a a<14:03:58.436> writing<14:03:59.040> module<14:03:59.400> that<14:03:59.640> you<14:03:59.756> can<14:03:59.880> insert 14:04:01.070 --> 14:04:01.080 align:start position:0% a writing module that you can insert 14:04:01.080 --> 14:04:05.330 align:start position:0% a writing module that you can insert which<14:04:01.860> is<14:04:02.040> a<14:04:02.820> bit<14:04:03.180> beyond<14:04:03.596> CCNA<14:04:04.320> level<14:04:04.500> to<14:04:05.220> be 14:04:05.330 --> 14:04:05.340 align:start position:0% which is a bit beyond CCNA level to be 14:04:05.340 --> 14:04:08.630 align:start position:0% which is a bit beyond CCNA level to be honest<14:04:05.900> just<14:04:06.900> for<14:04:07.020> your<14:04:07.200> own<14:04:07.320> information<14:04:07.640> so 14:04:08.630 --> 14:04:08.640 align:start position:0% honest just for your own information so 14:04:08.640 --> 14:04:10.310 align:start position:0% honest just for your own information so vlans<14:04:09.116> can<14:04:09.360> spun<14:04:09.660> multiple<14:04:10.080> physical 14:04:10.310 --> 14:04:10.320 align:start position:0% vlans can spun multiple physical 14:04:10.320 --> 14:04:12.350 align:start position:0% vlans can spun multiple physical switches 14:04:12.350 --> 14:04:12.360 align:start position:0% switches 14:04:12.360 --> 14:04:14.330 align:start position:0% switches so<14:04:12.840> we've<14:04:13.080> got<14:04:13.200> switch<14:04:13.436> one<14:04:13.740> two<14:04:13.980> and<14:04:14.160> three 14:04:14.330 --> 14:04:14.340 align:start position:0% so we've got switch one two and three 14:04:14.340 --> 14:04:16.850 align:start position:0% so we've got switch one two and three here<14:04:14.640> and<14:04:14.880> you<14:04:15.060> can<14:04:15.180> see<14:04:15.360> we've<14:04:15.720> got<14:04:16.020> a<14:04:16.560> couple 14:04:16.850 --> 14:04:16.860 align:start position:0% here and you can see we've got a couple 14:04:16.860 --> 14:04:19.850 align:start position:0% here and you can see we've got a couple of<14:04:17.040> different<14:04:17.220> vlans<14:04:17.820> configured 14:04:19.850 --> 14:04:19.860 align:start position:0% of different vlans configured 14:04:19.860 --> 14:04:22.310 align:start position:0% of different vlans configured best<14:04:20.276> to<14:04:20.520> have<14:04:20.640> all<14:04:20.880> hosts<14:04:21.360> in<14:04:21.540> the<14:04:21.660> same<14:04:21.776> VLAN 14:04:22.310 --> 14:04:22.320 align:start position:0% best to have all hosts in the same VLAN 14:04:22.320 --> 14:04:24.946 align:start position:0% best to have all hosts in the same VLAN on<14:04:22.616> the<14:04:22.800> same<14:04:22.980> subnet<14:04:23.520> that's<14:04:24.480> all<14:04:24.720> really 14:04:24.946 --> 14:04:24.956 align:start position:0% on the same subnet that's all really 14:04:24.956 --> 14:04:26.570 align:start position:0% on the same subnet that's all really wanted<14:04:25.140> to<14:04:25.380> say<14:04:25.500> on<14:04:25.680> that<14:04:25.860> particular<14:04:26.220> subject 14:04:26.570 --> 14:04:26.580 align:start position:0% wanted to say on that particular subject 14:04:26.580 --> 14:04:28.730 align:start position:0% wanted to say on that particular subject but<14:04:26.936> it's<14:04:27.060> just<14:04:27.300> the<14:04:27.480> best 14:04:28.730 --> 14:04:28.740 align:start position:0% but it's just the best 14:04:28.740 --> 14:04:30.290 align:start position:0% but it's just the best um idea 14:04:30.290 --> 14:04:30.300 align:start position:0% um idea 14:04:30.300 --> 14:04:34.370 align:start position:0% um idea no<14:04:31.020> need<14:04:31.200> for<14:04:31.436> a<14:04:31.680> variety<14:04:32.520> to<14:04:33.300> communicate<14:04:33.900> if 14:04:34.370 --> 14:04:34.380 align:start position:0% no need for a variety to communicate if 14:04:34.380 --> 14:04:40.246 align:start position:0% no need for a variety to communicate if all<14:04:34.616> the<14:04:34.740> devices<14:04:35.040> are<14:04:35.520> all<14:04:35.700> on<14:04:36.060> the<14:04:36.180> same<14:04:36.300> VLAN 14:04:40.246 --> 14:04:40.256 align:start position:0% 14:04:40.256 --> 14:04:42.050 align:start position:0% some<14:04:40.680> of<14:04:40.800> the<14:04:40.916> benefits<14:04:41.400> or<14:04:41.580> why<14:04:41.756> would<14:04:41.880> you 14:04:42.050 --> 14:04:42.060 align:start position:0% some of the benefits or why would you 14:04:42.060 --> 14:04:44.390 align:start position:0% some of the benefits or why would you bother<14:04:42.360> logical<14:04:43.256> separation<14:04:43.740> just<14:04:44.096> gives<14:04:44.276> you 14:04:44.390 --> 14:04:44.400 align:start position:0% bother logical separation just gives you 14:04:44.400 --> 14:04:45.670 align:start position:0% bother logical separation just gives you better<14:04:44.640> security 14:04:45.670 --> 14:04:45.680 align:start position:0% better security 14:04:45.680 --> 14:04:48.890 align:start position:0% better security helps<14:04:46.680> with<14:04:47.220> the<14:04:47.520> broadcast<14:04:47.820> issues<14:04:48.540> if<14:04:48.776> you 14:04:48.890 --> 14:04:48.900 align:start position:0% helps with the broadcast issues if you 14:04:48.900 --> 14:04:51.470 align:start position:0% helps with the broadcast issues if you do<14:04:49.020> up<14:04:49.320> on<14:04:49.560> better<14:04:50.276> utilization<14:04:51.060> of<14:04:51.360> your 14:04:51.470 --> 14:04:51.480 align:start position:0% do up on better utilization of your 14:04:51.480 --> 14:04:53.406 align:start position:0% do up on better utilization of your bandwidth 14:04:53.406 --> 14:04:53.416 align:start position:0% bandwidth 14:04:53.416 --> 14:04:55.906 align:start position:0% bandwidth Avila<14:04:54.416> marking<14:04:54.840> obviously<14:04:55.200> it<14:04:55.320> has<14:04:55.500> to<14:04:55.680> be 14:04:55.906 --> 14:04:55.916 align:start position:0% Avila marking obviously it has to be 14:04:55.916 --> 14:04:57.890 align:start position:0% Avila marking obviously it has to be some<14:04:56.096> way<14:04:56.340> if<14:04:56.700> you're<14:04:57.000> chopping<14:04:57.540> your<14:04:57.660> network 14:04:57.890 --> 14:04:57.900 align:start position:0% some way if you're chopping your network 14:04:57.900 --> 14:05:00.470 align:start position:0% some way if you're chopping your network into<14:04:58.200> vlans<14:04:58.800> for<14:04:59.456> the<14:04:59.520> VLAN<14:04:59.936> to<14:05:00.060> identify 14:05:00.470 --> 14:05:00.480 align:start position:0% into vlans for the VLAN to identify 14:05:00.480 --> 14:05:01.730 align:start position:0% into vlans for the VLAN to identify itself 14:05:01.730 --> 14:05:01.740 align:start position:0% itself 14:05:01.740 --> 14:05:03.710 align:start position:0% itself vendors<14:05:02.520> use<14:05:02.700> different<14:05:02.880> approaches<14:05:03.360> for 14:05:03.710 --> 14:05:03.720 align:start position:0% vendors use different approaches for 14:05:03.720 --> 14:05:06.470 align:start position:0% vendors use different approaches for example<14:05:03.956> Cisco<14:05:04.616> created<14:05:05.220> ISL<14:05:05.820> into<14:05:06.180> switch 14:05:06.470 --> 14:05:06.480 align:start position:0% example Cisco created ISL into switch 14:05:06.480 --> 14:05:09.406 align:start position:0% example Cisco created ISL into switch link<14:05:06.900> which<14:05:07.740> is<14:05:07.860> a<14:05:08.096> proprietary<14:05:08.640> for<14:05:08.936> Cisco 14:05:09.406 --> 14:05:09.416 align:start position:0% link which is a proprietary for Cisco 14:05:09.416 --> 14:05:11.630 align:start position:0% link which is a proprietary for Cisco devices<14:05:09.840> they've<14:05:10.680> actually<14:05:10.860> moved<14:05:11.220> away<14:05:11.276> from 14:05:11.630 --> 14:05:11.640 align:start position:0% devices they've actually moved away from 14:05:11.640 --> 14:05:13.790 align:start position:0% devices they've actually moved away from ISL<14:05:12.116> now<14:05:12.360> though<14:05:12.596> many<14:05:12.840> of<14:05:13.200> their<14:05:13.380> switches 14:05:13.790 --> 14:05:13.800 align:start position:0% ISL now though many of their switches 14:05:13.800 --> 14:05:15.710 align:start position:0% ISL now though many of their switches still<14:05:13.980> support<14:05:14.220> it<14:05:14.520> and<14:05:15.000> they<14:05:15.180> moved<14:05:15.480> on<14:05:15.540> to 14:05:15.710 --> 14:05:15.720 align:start position:0% still support it and they moved on to 14:05:15.720 --> 14:05:19.010 align:start position:0% still support it and they moved on to IEEE<14:05:16.500> standard<14:05:16.916> 802.1q 14:05:19.010 --> 14:05:19.020 align:start position:0% IEEE standard 802.1q 14:05:19.020 --> 14:05:21.470 align:start position:0% IEEE standard 802.1q called<14:05:19.500> frame<14:05:19.860> tagging<14:05:20.640> frame<14:05:21.116> tagging 14:05:21.470 --> 14:05:21.480 align:start position:0% called frame tagging frame tagging 14:05:21.480 --> 14:05:23.630 align:start position:0% called frame tagging frame tagging inserts<14:05:21.900> a<14:05:22.020> 32-bit<14:05:22.616> tag<14:05:22.860> field<14:05:23.096> into<14:05:23.400> the 14:05:23.630 --> 14:05:23.640 align:start position:0% inserts a 32-bit tag field into the 14:05:23.640 --> 14:05:26.210 align:start position:0% inserts a 32-bit tag field into the original<14:05:23.820> frame 14:05:26.210 --> 14:05:26.220 align:start position:0% original frame 14:05:26.220 --> 14:05:29.150 align:start position:0% original frame so<14:05:26.700> concept<14:05:27.180> of<14:05:27.416> a<14:05:27.660> native<14:05:28.256> VLAN<14:05:28.740> is<14:05:28.980> something 14:05:29.150 --> 14:05:29.160 align:start position:0% so concept of a native VLAN is something 14:05:29.160 --> 14:05:30.766 align:start position:0% so concept of a native VLAN is something you<14:05:29.340> should<14:05:29.520> be<14:05:29.640> familiar<14:05:29.936> with<14:05:30.060> as<14:05:30.240> a<14:05:30.416> Cisco 14:05:30.766 --> 14:05:30.776 align:start position:0% you should be familiar with as a Cisco 14:05:30.776 --> 14:05:32.030 align:start position:0% you should be familiar with as a Cisco engineer 14:05:32.030 --> 14:05:32.040 align:start position:0% engineer 14:05:32.040 --> 14:05:36.246 align:start position:0% engineer a<14:05:32.820> native<14:05:33.360> VLAN<14:05:34.080> on<14:05:34.560> Cisco<14:05:35.276> devices<14:05:35.640> certainly 14:05:36.246 --> 14:05:36.256 align:start position:0% a native VLAN on Cisco devices certainly 14:05:36.256 --> 14:05:41.926 align:start position:0% a native VLAN on Cisco devices certainly is<14:05:37.340> all<14:05:38.340> allocated<14:05:38.880> to<14:05:39.720> VLAN<14:05:40.560> one<14:05:40.800> by<14:05:41.580> default 14:05:41.926 --> 14:05:41.936 align:start position:0% is all allocated to VLAN one by default 14:05:41.936 --> 14:05:44.030 align:start position:0% is all allocated to VLAN one by default all<14:05:42.240> devices<14:05:42.540> in<14:05:42.956> a<14:05:43.080> VLAN<14:05:43.500> will<14:05:43.680> be<14:05:43.740> assigned 14:05:44.030 --> 14:05:44.040 align:start position:0% all devices in a VLAN will be assigned 14:05:44.040 --> 14:05:46.906 align:start position:0% all devices in a VLAN will be assigned to<14:05:44.160> VLAN<14:05:44.520> 1<14:05:44.700> unless<14:05:45.540> you<14:05:45.720> configure<14:05:46.320> and<14:05:46.740> then 14:05:46.906 --> 14:05:46.916 align:start position:0% to VLAN 1 unless you configure and then 14:05:46.916 --> 14:05:48.830 align:start position:0% to VLAN 1 unless you configure and then to<14:05:47.096> be<14:05:47.220> in<14:05:47.400> a<14:05:47.520> different<14:05:47.580> VLAN 14:05:48.830 --> 14:05:48.840 align:start position:0% to be in a different VLAN 14:05:48.840 --> 14:05:51.650 align:start position:0% to be in a different VLAN so<14:05:49.256> traffic<14:05:49.500> on<14:05:49.800> a<14:05:49.980> VLAN<14:05:50.456> on<14:05:51.180> that<14:05:51.360> on<14:05:51.540> the 14:05:51.650 --> 14:05:51.660 align:start position:0% so traffic on a VLAN on that on the 14:05:51.660 --> 14:05:53.926 align:start position:0% so traffic on a VLAN on that on the native<14:05:51.776> VLAN<14:05:52.256> is<14:05:52.500> not<14:05:52.800> tagged<14:05:53.220> it's<14:05:53.400> not<14:05:53.580> given 14:05:53.926 --> 14:05:53.936 align:start position:0% native VLAN is not tagged it's not given 14:05:53.936 --> 14:05:56.870 align:start position:0% native VLAN is not tagged it's not given the<14:05:54.080> 802.1<14:05:55.080> Q<14:05:55.680> tagging 14:05:56.870 --> 14:05:56.880 align:start position:0% the 802.1 Q tagging 14:05:56.880 --> 14:05:59.570 align:start position:0% the 802.1 Q tagging well<14:05:57.596> the<14:05:57.956> reason<14:05:58.080> is<14:05:58.380> it<14:05:58.616> uh<14:05:58.980> we<14:05:59.160> have<14:05:59.276> it<14:05:59.456> is 14:05:59.570 --> 14:05:59.580 align:start position:0% well the reason is it uh we have it is 14:05:59.580 --> 14:06:01.310 align:start position:0% well the reason is it uh we have it is it<14:05:59.820> allows<14:06:00.116> the<14:06:00.240> switch<14:06:00.416> to<14:06:00.660> communicate<14:06:01.140> with 14:06:01.310 --> 14:06:01.320 align:start position:0% it allows the switch to communicate with 14:06:01.320 --> 14:06:02.510 align:start position:0% it allows the switch to communicate with the<14:06:01.500> device<14:06:01.616> that<14:06:01.916> doesn't<14:06:02.160> understand 14:06:02.510 --> 14:06:02.520 align:start position:0% the device that doesn't understand 14:06:02.520 --> 14:06:05.330 align:start position:0% the device that doesn't understand 802.1q 14:06:05.330 --> 14:06:05.340 align:start position:0% 802.1q 14:06:05.340 --> 14:06:07.550 align:start position:0% 802.1q it<14:06:05.820> is<14:06:05.936> a<14:06:06.060> security<14:06:06.300> risk<14:06:06.840> which<14:06:07.080> we'll<14:06:07.320> cover 14:06:07.550 --> 14:06:07.560 align:start position:0% it is a security risk which we'll cover 14:06:07.560 --> 14:06:10.550 align:start position:0% it is a security risk which we'll cover later<14:06:07.916> on 14:06:10.550 --> 14:06:10.560 align:start position:0% 14:06:10.560 --> 14:06:14.086 align:start position:0% vlr<14:06:11.340> membership<14:06:11.640> so<14:06:12.480> you<14:06:12.776> can<14:06:12.840> assign<14:06:13.200> VLAN 14:06:14.086 --> 14:06:14.096 align:start position:0% vlr membership so you can assign VLAN 14:06:14.096 --> 14:06:18.230 align:start position:0% vlr membership so you can assign VLAN devices<14:06:15.000> or<14:06:15.360> ports<14:06:15.840> to<14:06:16.320> a<14:06:16.560> VLAN<14:06:16.980> statically<14:06:17.820> as 14:06:18.230 --> 14:06:18.240 align:start position:0% devices or ports to a VLAN statically as 14:06:18.240 --> 14:06:19.850 align:start position:0% devices or ports to a VLAN statically as a<14:06:18.416> network<14:06:18.540> administrator 14:06:19.850 --> 14:06:19.860 align:start position:0% a network administrator 14:06:19.860 --> 14:06:22.130 align:start position:0% a network administrator it<14:06:20.276> can<14:06:20.456> be<14:06:20.580> dynamic<14:06:21.116> based<14:06:21.416> upon<14:06:21.660> device<14:06:21.840> Mac 14:06:22.130 --> 14:06:22.140 align:start position:0% it can be dynamic based upon device Mac 14:06:22.140 --> 14:06:23.330 align:start position:0% it can be dynamic based upon device Mac address 14:06:23.330 --> 14:06:23.340 align:start position:0% address 14:06:23.340 --> 14:06:25.906 align:start position:0% address switch<14:06:23.880> ports<14:06:24.416> are<14:06:24.776> assigned<14:06:25.140> to<14:06:25.200> vlans<14:06:25.680> and 14:06:25.906 --> 14:06:25.916 align:start position:0% switch ports are assigned to vlans and 14:06:25.916 --> 14:06:27.470 align:start position:0% switch ports are assigned to vlans and then<14:06:26.096> devices<14:06:26.340> plug<14:06:26.756> into<14:06:26.936> the<14:06:27.240> physical 14:06:27.470 --> 14:06:27.480 align:start position:0% then devices plug into the physical 14:06:27.480 --> 14:06:28.606 align:start position:0% then devices plug into the physical ports 14:06:28.606 --> 14:06:28.616 align:start position:0% ports 14:06:28.616 --> 14:06:33.586 align:start position:0% ports access<14:06:29.220> ports<14:06:29.820> connect<14:06:29.936> to<14:06:30.300> network<14:06:30.660> hosts 14:06:33.586 --> 14:06:33.596 align:start position:0% 14:06:33.596 --> 14:06:35.690 align:start position:0% a<14:06:33.900> network<14:06:34.200> hosts<14:06:34.616> connect<14:06:34.800> to<14:06:34.980> access<14:06:35.160> ports 14:06:35.690 --> 14:06:35.700 align:start position:0% a network hosts connect to access ports 14:06:35.700 --> 14:06:38.086 align:start position:0% a network hosts connect to access ports it<14:06:35.936> works<14:06:36.300> both<14:06:36.416> way<14:06:36.596> around<14:06:36.776> that<14:06:37.140> sentence 14:06:38.086 --> 14:06:38.096 align:start position:0% it works both way around that sentence 14:06:38.096 --> 14:06:39.650 align:start position:0% it works both way around that sentence if<14:06:38.456> you<14:06:38.580> want<14:06:38.700> to<14:06:38.820> connect<14:06:38.936> to<14:06:39.116> another<14:06:39.300> switch 14:06:39.650 --> 14:06:39.660 align:start position:0% if you want to connect to another switch 14:06:39.660 --> 14:06:41.990 align:start position:0% if you want to connect to another switch and<14:06:40.080> you're<14:06:40.256> using<14:06:40.560> multiple<14:06:40.980> vlans<14:06:41.700> then 14:06:41.990 --> 14:06:42.000 align:start position:0% and you're using multiple vlans then 14:06:42.000 --> 14:06:44.446 align:start position:0% and you're using multiple vlans then these<14:06:42.776> connections<14:06:43.740> are<14:06:43.860> known<14:06:44.040> as<14:06:44.160> trunk 14:06:44.446 --> 14:06:44.456 align:start position:0% these connections are known as trunk 14:06:44.456 --> 14:06:45.830 align:start position:0% these connections are known as trunk ports 14:06:45.830 --> 14:06:45.840 align:start position:0% ports 14:06:45.840 --> 14:06:49.490 align:start position:0% ports so<14:06:46.080> trunk<14:06:46.436> ports<14:06:46.860> uh<14:06:47.700> will<14:06:48.240> connect<14:06:48.480> more<14:06:49.320> than 14:06:49.490 --> 14:06:49.500 align:start position:0% so trunk ports uh will connect more than 14:06:49.500 --> 14:06:52.310 align:start position:0% so trunk ports uh will connect more than one<14:06:49.680> VLAN<14:06:50.160> which<14:06:50.700> is<14:06:50.936> connecting<14:06:51.660> more<14:06:52.200> than 14:06:52.310 --> 14:06:52.320 align:start position:0% one VLAN which is connecting more than 14:06:52.320 --> 14:06:55.246 align:start position:0% one VLAN which is connecting more than one<14:06:52.436> VLAN<14:06:52.860> together 14:06:55.246 --> 14:06:55.256 align:start position:0% 14:06:55.256 --> 14:06:57.586 align:start position:0% so<14:06:55.616> a<14:06:55.860> special<14:06:55.980> Port<14:06:56.276> type<14:06:56.520> carries<14:06:57.060> data<14:06:57.416> from 14:06:57.586 --> 14:06:57.596 align:start position:0% so a special Port type carries data from 14:06:57.596 --> 14:07:00.290 align:start position:0% so a special Port type carries data from multiple<14:06:57.956> vlans<14:06:58.500> it<14:06:58.800> can<14:06:59.040> use<14:06:59.220> ISL<14:06:59.936> although 14:07:00.290 --> 14:07:00.300 align:start position:0% multiple vlans it can use ISL although 14:07:00.300 --> 14:07:02.510 align:start position:0% multiple vlans it can use ISL although that's<14:07:00.540> pretty<14:07:00.776> much<14:07:00.956> been<14:07:01.500> depreciated<14:07:02.160> now 14:07:02.510 --> 14:07:02.520 align:start position:0% that's pretty much been depreciated now 14:07:02.520 --> 14:07:04.070 align:start position:0% that's pretty much been depreciated now so<14:07:02.820> you<14:07:03.116> shouldn't<14:07:03.360> be<14:07:03.416> looking<14:07:03.540> at<14:07:03.776> it<14:07:03.900> for 14:07:04.070 --> 14:07:04.080 align:start position:0% so you shouldn't be looking at it for 14:07:04.080 --> 14:07:07.070 align:start position:0% so you shouldn't be looking at it for the<14:07:04.256> CISCO<14:07:04.616> exams<14:07:05.040> at<14:07:05.220> least 14:07:07.070 --> 14:07:07.080 align:start position:0% the CISCO exams at least 14:07:07.080 --> 14:07:10.010 align:start position:0% the CISCO exams at least frame<14:07:07.740> tag<14:07:08.040> in<14:07:08.220> is<14:07:08.520> transparent<14:07:09.060> to<14:07:09.240> end<14:07:09.416> hosts 14:07:10.010 --> 14:07:10.020 align:start position:0% frame tag in is transparent to end hosts 14:07:10.020 --> 14:07:12.586 align:start position:0% frame tag in is transparent to end hosts so<14:07:10.500> the<14:07:10.916> tag<14:07:11.096> is<14:07:11.700> attached<14:07:12.116> by<14:07:12.240> the<14:07:12.416> switch 14:07:12.586 --> 14:07:12.596 align:start position:0% so the tag is attached by the switch 14:07:12.596 --> 14:07:14.510 align:start position:0% so the tag is attached by the switch sent<14:07:13.140> to<14:07:13.380> another<14:07:13.500> switch<14:07:13.800> and<14:07:14.096> before<14:07:14.276> it 14:07:14.510 --> 14:07:14.520 align:start position:0% sent to another switch and before it 14:07:14.520 --> 14:07:16.790 align:start position:0% sent to another switch and before it reaches<14:07:14.936> the<14:07:15.116> end<14:07:15.240> hosts<14:07:15.776> the<14:07:16.380> tag<14:07:16.616> is 14:07:16.790 --> 14:07:16.800 align:start position:0% reaches the end hosts the tag is 14:07:16.800 --> 14:07:18.350 align:start position:0% reaches the end hosts the tag is actually<14:07:16.980> removed 14:07:18.350 --> 14:07:18.360 align:start position:0% actually removed 14:07:18.360 --> 14:07:22.130 align:start position:0% actually removed trunkport<14:07:19.140> modes<14:07:19.980> we<14:07:20.880> can<14:07:21.116> manually<14:07:21.596> set<14:07:21.900> the 14:07:22.130 --> 14:07:22.140 align:start position:0% trunkport modes we can manually set the 14:07:22.140 --> 14:07:24.050 align:start position:0% trunkport modes we can manually set the interface<14:07:22.560> to<14:07:22.916> trunk<14:07:23.276> with<14:07:23.520> the<14:07:23.700> command 14:07:24.050 --> 14:07:24.060 align:start position:0% interface to trunk with the command 14:07:24.060 --> 14:07:26.390 align:start position:0% interface to trunk with the command switch<14:07:24.240> Port<14:07:24.596> mode<14:07:24.956> trunk 14:07:26.390 --> 14:07:26.400 align:start position:0% switch Port mode trunk 14:07:26.400 --> 14:07:29.150 align:start position:0% switch Port mode trunk trunk<14:07:26.880> modes<14:07:27.240> include<14:07:27.660> on<14:07:28.020> which<14:07:28.740> is<14:07:28.860> manually 14:07:29.150 --> 14:07:29.160 align:start position:0% trunk modes include on which is manually 14:07:29.160 --> 14:07:31.790 align:start position:0% trunk modes include on which is manually set<14:07:29.456> the<14:07:29.580> interface<14:07:29.936> to<14:07:30.180> trunk<14:07:30.480> off<14:07:31.380> you<14:07:31.680> can 14:07:31.790 --> 14:07:31.800 align:start position:0% set the interface to trunk off you can 14:07:31.800 --> 14:07:34.190 align:start position:0% set the interface to trunk off you can tell<14:07:31.980> it<14:07:32.160> to<14:07:32.276> never<14:07:32.520> become<14:07:32.880> a<14:07:33.060> trunk 14:07:34.190 --> 14:07:34.200 align:start position:0% tell it to never become a trunk 14:07:34.200 --> 14:07:36.586 align:start position:0% tell it to never become a trunk Auto<14:07:34.916> silently<14:07:35.580> wait<14:07:35.820> for<14:07:36.000> a<14:07:36.180> request<14:07:36.416> to 14:07:36.586 --> 14:07:36.596 align:start position:0% Auto silently wait for a request to 14:07:36.596 --> 14:07:39.470 align:start position:0% Auto silently wait for a request to become<14:07:36.840> a<14:07:37.020> trunk<14:07:37.740> desirable<14:07:38.640> which<14:07:39.180> means 14:07:39.470 --> 14:07:39.480 align:start position:0% become a trunk desirable which means 14:07:39.480 --> 14:07:42.586 align:start position:0% become a trunk desirable which means actively<14:07:39.956> seek<14:07:40.380> to<14:07:40.560> become<14:07:40.860> a<14:07:41.040> trunk<14:07:41.340> or<14:07:42.300> no 14:07:42.586 --> 14:07:42.596 align:start position:0% actively seek to become a trunk or no 14:07:42.596 --> 14:07:45.710 align:start position:0% actively seek to become a trunk or no negotiate<14:07:43.320> you'll<14:07:44.040> cover<14:07:44.220> these<14:07:44.580> commands 14:07:45.710 --> 14:07:45.720 align:start position:0% negotiate you'll cover these commands 14:07:45.720 --> 14:07:48.890 align:start position:0% negotiate you'll cover these commands in<14:07:46.320> detail<14:07:46.616> when<14:07:46.800> you<14:07:46.916> come<14:07:47.096> to<14:07:47.220> do<14:07:47.400> the<14:07:47.580> CCNA<14:07:48.240> I 14:07:48.890 --> 14:07:48.900 align:start position:0% in detail when you come to do the CCNA I 14:07:48.900 --> 14:07:50.266 align:start position:0% in detail when you come to do the CCNA I probably<14:07:49.020> won't<14:07:49.256> be<14:07:49.436> doing 14:07:50.266 --> 14:07:50.276 align:start position:0% probably won't be doing 14:07:50.276 --> 14:07:50.810 align:start position:0% probably won't be doing um 14:07:50.810 --> 14:07:50.820 align:start position:0% um 14:07:50.820 --> 14:07:52.490 align:start position:0% um covering<14:07:51.660> these<14:07:51.840> commands<14:07:52.140> and<14:07:52.256> how<14:07:52.380> to 14:07:52.490 --> 14:07:52.500 align:start position:0% covering these commands and how to 14:07:52.500 --> 14:07:55.490 align:start position:0% covering these commands and how to configure<14:07:52.916> them<14:07:53.040> for<14:07:53.400> the<14:07:53.936> primer 14:07:55.490 --> 14:07:55.500 align:start position:0% configure them for the primer 14:07:55.500 --> 14:07:57.830 align:start position:0% configure them for the primer configuring<14:07:56.160> a<14:07:56.340> VLAN<14:07:56.700> you<14:07:57.300> need<14:07:57.416> to<14:07:57.540> manually 14:07:57.830 --> 14:07:57.840 align:start position:0% configuring a VLAN you need to manually 14:07:57.840 --> 14:07:59.926 align:start position:0% configuring a VLAN you need to manually add<14:07:58.080> the<14:07:58.256> ports<14:07:58.560> to<14:07:58.680> vlans 14:07:59.926 --> 14:07:59.936 align:start position:0% add the ports to vlans 14:07:59.936 --> 14:08:02.990 align:start position:0% add the ports to vlans and<14:08:00.360> you<14:08:00.480> need<14:08:00.660> to<14:08:00.720> set<14:08:00.900> your<14:08:01.080> ports<14:08:01.560> to<14:08:01.680> trunk 14:08:02.990 --> 14:08:03.000 align:start position:0% and you need to set your ports to trunk 14:08:03.000 --> 14:08:06.106 align:start position:0% and you need to set your ports to trunk so<14:08:03.900> here's<14:08:04.320> a<14:08:04.436> configuration<14:08:04.916> I've<14:08:05.456> just<14:08:05.700> done 14:08:06.106 --> 14:08:06.116 align:start position:0% so here's a configuration I've just done 14:08:06.116 --> 14:08:07.790 align:start position:0% so here's a configuration I've just done one<14:08:06.360> side<14:08:06.540> because<14:08:06.776> the<14:08:07.020> configuration<14:08:07.560> is 14:08:07.790 --> 14:08:07.800 align:start position:0% one side because the configuration is 14:08:07.800 --> 14:08:10.190 align:start position:0% one side because the configuration is the<14:08:08.096> same<14:08:08.220> for<14:08:08.580> both<14:08:08.880> switches 14:08:10.190 --> 14:08:10.200 align:start position:0% the same for both switches 14:08:10.200 --> 14:08:13.730 align:start position:0% the same for both switches I've<14:08:11.040> created<14:08:11.340> VLAN<14:08:11.880> 5<14:08:12.180> in<14:08:12.596> config<14:08:13.020> mode<14:08:13.200> by 14:08:13.730 --> 14:08:13.740 align:start position:0% I've created VLAN 5 in config mode by 14:08:13.740 --> 14:08:15.650 align:start position:0% I've created VLAN 5 in config mode by typing<14:08:13.980> VLAN<14:08:14.456> 5. 14:08:15.650 --> 14:08:15.660 align:start position:0% typing VLAN 5. 14:08:15.660 --> 14:08:19.490 align:start position:0% typing VLAN 5. I've<14:08:16.560> given<14:08:16.800> it<14:08:16.980> a<14:08:17.096> name<14:08:17.276> called<14:08:17.640> RND<14:08:18.416> so<14:08:19.320> you 14:08:19.490 --> 14:08:19.500 align:start position:0% I've given it a name called RND so you 14:08:19.500 --> 14:08:21.830 align:start position:0% I've given it a name called RND so you can<14:08:19.616> name<14:08:19.800> your<14:08:19.916> vlans<14:08:20.400> it<14:08:20.820> probably<14:08:21.360> makes<14:08:21.660> it 14:08:21.830 --> 14:08:21.840 align:start position:0% can name your vlans it probably makes it 14:08:21.840 --> 14:08:23.870 align:start position:0% can name your vlans it probably makes it easy<14:08:22.020> for<14:08:22.200> you<14:08:22.320> to<14:08:22.436> manage<14:08:22.740> interface<14:08:23.640> fast 14:08:23.870 --> 14:08:23.880 align:start position:0% easy for you to manage interface fast 14:08:23.880 --> 14:08:25.906 align:start position:0% easy for you to manage interface fast ethernet<14:08:24.240> zero<14:08:24.660> slash<14:08:24.956> one<14:08:25.140> I've<14:08:25.560> created 14:08:25.906 --> 14:08:25.916 align:start position:0% ethernet zero slash one I've created 14:08:25.916 --> 14:08:29.926 align:start position:0% ethernet zero slash one I've created switch<14:08:26.276> Port<14:08:26.640> access<14:08:27.596> VLAN<14:08:28.320> 5.<14:08:29.220> so<14:08:29.580> this<14:08:29.756> is 14:08:29.926 --> 14:08:29.936 align:start position:0% switch Port access VLAN 5. so this is 14:08:29.936 --> 14:08:32.570 align:start position:0% switch Port access VLAN 5. so this is telling<14:08:30.480> the<14:08:30.776> port<14:08:31.080> that<14:08:31.380> it's<14:08:31.616> a<14:08:31.916> switch<14:08:32.276> Port 14:08:32.570 --> 14:08:32.580 align:start position:0% telling the port that it's a switch Port 14:08:32.580 --> 14:08:36.170 align:start position:0% telling the port that it's a switch Port layer<14:08:33.116> 2<14:08:33.300> and<14:08:33.840> it<14:08:34.020> and<14:08:34.380> the<14:08:34.680> device<14:08:34.860> is<14:08:35.520> belongs 14:08:36.170 --> 14:08:36.180 align:start position:0% layer 2 and it and the device is belongs 14:08:36.180 --> 14:08:38.746 align:start position:0% layer 2 and it and the device is belongs to<14:08:36.300> VLAN<14:08:36.660> file<14:08:36.956> that's<14:08:37.080> connected<14:08:37.436> to<14:08:37.680> it 14:08:38.746 --> 14:08:38.756 align:start position:0% to VLAN file that's connected to it 14:08:38.756 --> 14:08:41.530 align:start position:0% to VLAN file that's connected to it I've<14:08:39.180> gone<14:08:39.360> on<14:08:39.480> to<14:08:39.596> my<14:08:39.720> fast<14:08:39.840> ethernet<14:08:40.276> 0-15 14:08:41.530 --> 14:08:41.540 align:start position:0% I've gone on to my fast ethernet 0-15 14:08:41.540 --> 14:08:45.170 align:start position:0% I've gone on to my fast ethernet 0-15 switchboard<14:08:42.540> trunk<14:08:43.020> encapsulation.1q 14:08:45.170 --> 14:08:45.180 align:start position:0% switchboard trunk encapsulation.1q 14:08:45.180 --> 14:08:47.330 align:start position:0% switchboard trunk encapsulation.1q to<14:08:45.720> tell<14:08:45.900> it<14:08:46.080> what<14:08:46.320> encapsulation<14:08:46.860> to<14:08:47.096> use 14:08:47.330 --> 14:08:47.340 align:start position:0% to tell it what encapsulation to use 14:08:47.340 --> 14:08:50.106 align:start position:0% to tell it what encapsulation to use that<14:08:48.000> won't<14:08:48.116> work<14:08:48.360> on<14:08:48.540> a<14:08:48.720> 2960<14:08:49.256> switch<14:08:49.616> because 14:08:50.106 --> 14:08:50.116 align:start position:0% that won't work on a 2960 switch because 14:08:50.116 --> 14:08:53.570 align:start position:0% that won't work on a 2960 switch because 2960<14:08:51.116> will<14:08:51.480> only<14:08:51.660> recognize.monkey 14:08:53.570 --> 14:08:53.580 align:start position:0% 2960 will only recognize.monkey 14:08:53.580 --> 14:08:57.710 align:start position:0% 2960 will only recognize.monkey and<14:08:53.936> I've<14:08:54.060> told<14:08:54.300> it<14:08:54.416> to<14:08:54.540> become<14:08:54.776> a<14:08:54.956> trump<14:08:55.080> port 14:08:57.710 --> 14:08:57.720 align:start position:0% 14:08:57.720 --> 14:08:59.570 align:start position:0% okay<14:08:58.200> so<14:08:58.500> you'll<14:08:58.740> be<14:08:58.860> labbing<14:08:59.276> some<14:08:59.400> of<14:08:59.520> this 14:08:59.570 --> 14:08:59.580 align:start position:0% okay so you'll be labbing some of this 14:08:59.580 --> 14:09:01.970 align:start position:0% okay so you'll be labbing some of this up<14:08:59.700> later<14:08:59.936> on<14:09:00.240> but<14:09:00.900> for<14:09:01.080> now<14:09:01.256> that's<14:09:01.680> the<14:09:01.860> end 14:09:01.970 --> 14:09:01.980 align:start position:0% up later on but for now that's the end 14:09:01.980 --> 14:09:07.390 align:start position:0% up later on but for now that's the end thanks<14:09:02.160> for<14:09:02.400> listening 14:09:07.390 --> 14:09:07.400 align:start position:0% 14:09:07.400 --> 14:09:27.606 align:start position:0% [Music] 14:09:27.606 --> 14:09:27.616 align:start position:0% 14:09:27.616 --> 14:09:31.426 align:start position:0% wide<14:09:28.616> area<14:09:28.860> networks<14:09:29.720> implementation<14:09:30.720> and 14:09:31.426 --> 14:09:31.436 align:start position:0% wide area networks implementation and 14:09:31.436 --> 14:09:33.230 align:start position:0% wide area networks implementation and administration 14:09:33.230 --> 14:09:33.240 align:start position:0% administration 14:09:33.240 --> 14:09:35.990 align:start position:0% administration in<14:09:33.776> the<14:09:33.900> previous<14:09:34.020> lesson<14:09:34.740> we<14:09:35.400> discussed 14:09:35.990 --> 14:09:36.000 align:start position:0% in the previous lesson we discussed 14:09:36.000 --> 14:09:39.530 align:start position:0% in the previous lesson we discussed local<14:09:36.300> area<14:09:36.660> networks<14:09:37.256> or<14:09:38.040> lands<14:09:38.820> these<14:09:39.480> were 14:09:39.530 --> 14:09:39.540 align:start position:0% local area networks or lands these were 14:09:39.540 --> 14:09:41.690 align:start position:0% local area networks or lands these were networks<14:09:39.956> that<14:09:40.140> were<14:09:40.380> restricted<14:09:40.860> to<14:09:41.456> a 14:09:41.690 --> 14:09:41.700 align:start position:0% networks that were restricted to a 14:09:41.700 --> 14:09:45.106 align:start position:0% networks that were restricted to a specific<14:09:42.000> single<14:09:42.720> geographic<14:09:43.560> location<14:09:44.116> now 14:09:45.106 --> 14:09:45.116 align:start position:0% specific single geographic location now 14:09:45.116 --> 14:09:47.150 align:start position:0% specific single geographic location now in<14:09:45.596> this<14:09:45.776> lesson<14:09:46.140> we're<14:09:46.560> going<14:09:46.680> to<14:09:46.800> talk<14:09:46.916> more 14:09:47.150 --> 14:09:47.160 align:start position:0% in this lesson we're going to talk more 14:09:47.160 --> 14:09:51.170 align:start position:0% in this lesson we're going to talk more about<14:09:47.400> wide<14:09:48.240> area<14:09:48.416> networks<14:09:49.080> or<14:09:49.680> wans<14:09:50.456> we're 14:09:51.170 --> 14:09:51.180 align:start position:0% about wide area networks or wans we're 14:09:51.180 --> 14:09:53.570 align:start position:0% about wide area networks or wans we're going<14:09:51.300> to<14:09:51.360> Define<14:09:51.540> them<14:09:52.080> and<14:09:52.616> talk<14:09:52.800> about<14:09:53.040> how 14:09:53.570 --> 14:09:53.580 align:start position:0% going to Define them and talk about how 14:09:53.580 --> 14:09:56.926 align:start position:0% going to Define them and talk about how they<14:09:53.880> compare<14:09:54.360> to<14:09:55.080> local<14:09:55.320> area<14:09:55.616> Networks 14:09:56.926 --> 14:09:56.936 align:start position:0% they compare to local area Networks 14:09:56.936 --> 14:10:00.290 align:start position:0% they compare to local area Networks so<14:09:57.720> we're<14:09:58.256> first<14:09:58.500> going<14:09:58.800> to<14:09:58.980> define<14:09:59.640> a<14:10:00.000> Wan 14:10:00.290 --> 14:10:00.300 align:start position:0% so we're first going to define a Wan 14:10:00.300 --> 14:10:01.970 align:start position:0% so we're first going to define a Wan which<14:10:00.900> we've<14:10:01.140> talked<14:10:01.380> about<14:10:01.500> in<14:10:01.800> general 14:10:01.970 --> 14:10:01.980 align:start position:0% which we've talked about in general 14:10:01.980 --> 14:10:04.130 align:start position:0% which we've talked about in general before<14:10:02.340> and<14:10:03.116> then<14:10:03.240> we're<14:10:03.360> going<14:10:03.480> to<14:10:03.596> identify 14:10:04.130 --> 14:10:04.140 align:start position:0% before and then we're going to identify 14:10:04.140 --> 14:10:05.690 align:start position:0% before and then we're going to identify some<14:10:04.500> of<14:10:04.616> the<14:10:04.740> steps<14:10:05.040> we<14:10:05.160> would<14:10:05.276> take<14:10:05.456> to 14:10:05.690 --> 14:10:05.700 align:start position:0% some of the steps we would take to 14:10:05.700 --> 14:10:08.086 align:start position:0% some of the steps we would take to implement<14:10:06.060> one<14:10:06.416> uh<14:10:07.200> specifically<14:10:07.740> some<14:10:07.980> of 14:10:08.086 --> 14:10:08.096 align:start position:0% implement one uh specifically some of 14:10:08.096 --> 14:10:09.890 align:start position:0% implement one uh specifically some of the<14:10:08.160> things<14:10:08.340> that<14:10:08.580> make<14:10:08.756> it<14:10:08.936> different<14:10:09.116> from<14:10:09.660> a 14:10:09.890 --> 14:10:09.900 align:start position:0% the things that make it different from a 14:10:09.900 --> 14:10:12.406 align:start position:0% the things that make it different from a local<14:10:10.020> area<14:10:10.256> network<14:10:10.616> or<14:10:11.160> LAN 14:10:12.406 --> 14:10:12.416 align:start position:0% local area network or LAN 14:10:12.416 --> 14:10:15.050 align:start position:0% local area network or LAN finally<14:10:13.020> we<14:10:13.500> want<14:10:13.616> to<14:10:13.800> identify<14:10:14.340> some<14:10:14.700> of<14:10:14.820> the 14:10:15.050 --> 14:10:15.060 align:start position:0% finally we want to identify some of the 14:10:15.060 --> 14:10:17.810 align:start position:0% finally we want to identify some of the administrative<14:10:15.660> tasks<14:10:16.320> that<14:10:16.616> go<14:10:16.860> along<14:10:17.096> with 14:10:17.810 --> 14:10:17.820 align:start position:0% administrative tasks that go along with 14:10:17.820 --> 14:10:20.086 align:start position:0% administrative tasks that go along with or<14:10:18.240> that<14:10:18.660> challenge<14:10:19.020> us<14:10:19.380> as<14:10:19.680> Wan 14:10:20.086 --> 14:10:20.096 align:start position:0% or that challenge us as Wan 14:10:20.096 --> 14:10:23.510 align:start position:0% or that challenge us as Wan administrators<14:10:20.840> specifically<14:10:21.840> backup<14:10:22.740> and 14:10:23.510 --> 14:10:23.520 align:start position:0% administrators specifically backup and 14:10:23.520 --> 14:10:24.890 align:start position:0% administrators specifically backup and security 14:10:24.890 --> 14:10:24.900 align:start position:0% security 14:10:24.900 --> 14:10:28.906 align:start position:0% security so<14:10:25.560> a<14:10:26.220> Wan<14:10:26.456> is<14:10:26.936> a<14:10:27.360> wide<14:10:27.596> area<14:10:27.776> network<14:10:28.200> and 14:10:28.906 --> 14:10:28.916 align:start position:0% so a Wan is a wide area network and 14:10:28.916 --> 14:10:31.730 align:start position:0% so a Wan is a wide area network and though<14:10:29.160> it<14:10:29.276> functions<14:10:29.756> very<14:10:30.180> similarly<14:10:30.840> to<14:10:31.436> a 14:10:31.730 --> 14:10:31.740 align:start position:0% though it functions very similarly to a 14:10:31.740 --> 14:10:35.330 align:start position:0% though it functions very similarly to a lan<14:10:32.040> it<14:10:32.756> is<14:10:32.936> different<14:10:33.300> in<14:10:33.840> that<14:10:34.140> it's<14:10:34.436> the<14:10:35.160> way 14:10:35.330 --> 14:10:35.340 align:start position:0% lan it is different in that it's the way 14:10:35.340 --> 14:10:37.606 align:start position:0% lan it is different in that it's the way it's<14:10:35.520> set<14:10:35.756> up<14:10:35.880> and<14:10:36.596> the<14:10:36.840> way<14:10:36.956> it's<14:10:37.140> connected 14:10:37.606 --> 14:10:37.616 align:start position:0% it's set up and the way it's connected 14:10:37.616 --> 14:10:41.210 align:start position:0% it's set up and the way it's connected when<14:10:38.580> is<14:10:39.116> uh<14:10:39.660> Network<14:10:39.956> that's<14:10:40.500> not<14:10:40.740> restricted 14:10:41.210 --> 14:10:41.220 align:start position:0% when is uh Network that's not restricted 14:10:41.220 --> 14:10:44.266 align:start position:0% when is uh Network that's not restricted to<14:10:41.520> a<14:10:41.700> single<14:10:42.116> geographic<14:10:42.900> location<14:10:43.320> like<14:10:44.040> a 14:10:44.266 --> 14:10:44.276 align:start position:0% to a single geographic location like a 14:10:44.276 --> 14:10:46.490 align:start position:0% to a single geographic location like a lan<14:10:44.580> in<14:10:45.180> fact<14:10:45.300> it's<14:10:45.540> often<14:10:45.840> made<14:10:46.020> up<14:10:46.200> of 14:10:46.490 --> 14:10:46.500 align:start position:0% lan in fact it's often made up of 14:10:46.500 --> 14:10:49.190 align:start position:0% lan in fact it's often made up of multiple<14:10:47.096> lands<14:10:47.640> all<14:10:48.000> linked<14:10:48.416> into<14:10:48.660> one<14:10:48.956> big 14:10:49.190 --> 14:10:49.200 align:start position:0% multiple lands all linked into one big 14:10:49.200 --> 14:10:52.730 align:start position:0% multiple lands all linked into one big win<14:10:49.436> and<14:10:50.400> these<14:10:51.116> lands<14:10:51.660> can<14:10:51.900> be<14:10:52.080> across<14:10:52.616> town 14:10:52.730 --> 14:10:52.740 align:start position:0% win and these lands can be across town 14:10:52.740 --> 14:10:55.426 align:start position:0% win and these lands can be across town from<14:10:53.040> each<14:10:53.220> other<14:10:53.340> or<14:10:53.936> even<14:10:54.360> across<14:10:54.900> the<14:10:55.020> globe 14:10:55.426 --> 14:10:55.436 align:start position:0% from each other or even across the globe 14:10:55.436 --> 14:10:57.586 align:start position:0% from each other or even across the globe now<14:10:55.916> we've<14:10:56.160> talked<14:10:56.456> about<14:10:56.580> some<14:10:56.936> other<14:10:57.060> terms 14:10:57.586 --> 14:10:57.596 align:start position:0% now we've talked about some other terms 14:10:57.596 --> 14:10:59.990 align:start position:0% now we've talked about some other terms for<14:10:57.900> instance<14:10:58.200> can<14:10:58.916> like<14:10:59.276> a<14:10:59.520> campus<14:10:59.820> area 14:10:59.990 --> 14:11:00.000 align:start position:0% for instance can like a campus area 14:11:00.000 --> 14:11:02.870 align:start position:0% for instance can like a campus area network<14:11:00.300> or<14:11:01.020> city<14:11:01.200> area<14:11:01.436> network<14:11:01.800> and<14:11:02.580> a<14:11:02.756> man 14:11:02.870 --> 14:11:02.880 align:start position:0% network or city area network and a man 14:11:02.880 --> 14:11:05.210 align:start position:0% network or city area network and a man or<14:11:03.180> a<14:11:03.300> metropolitan<14:11:04.020> area<14:11:04.200> network<14:11:04.436> but<14:11:05.040> all 14:11:05.210 --> 14:11:05.220 align:start position:0% or a metropolitan area network but all 14:11:05.220 --> 14:11:07.310 align:start position:0% or a metropolitan area network but all of<14:11:05.340> these<14:11:05.580> could<14:11:05.880> be<14:11:06.116> in<14:11:06.596> some<14:11:06.776> way<14:11:06.900> shape<14:11:07.200> or 14:11:07.310 --> 14:11:07.320 align:start position:0% of these could be in some way shape or 14:11:07.320 --> 14:11:10.010 align:start position:0% of these could be in some way shape or form<14:11:07.560> are<14:11:08.340> considered<14:11:08.820> a<14:11:09.060> Wan<14:11:09.416> and<14:11:09.720> of<14:11:09.900> course 14:11:10.010 --> 14:11:10.020 align:start position:0% form are considered a Wan and of course 14:11:10.020 --> 14:11:13.130 align:start position:0% form are considered a Wan and of course the<14:11:10.320> biggest<14:11:10.500> win<14:11:10.980> that's<14:11:11.756> out<14:11:12.000> there<14:11:12.180> is<14:11:12.900> the 14:11:13.130 --> 14:11:13.140 align:start position:0% the biggest win that's out there is the 14:11:13.140 --> 14:11:14.266 align:start position:0% the biggest win that's out there is the internet 14:11:14.266 --> 14:11:14.276 align:start position:0% internet 14:11:14.276 --> 14:11:17.926 align:start position:0% internet usually<14:11:15.240> referred<14:11:16.140> to<14:11:16.256> as<14:11:16.500> the<14:11:16.800> cloud<14:11:16.980> because 14:11:17.926 --> 14:11:17.936 align:start position:0% usually referred to as the cloud because 14:11:17.936 --> 14:11:21.350 align:start position:0% usually referred to as the cloud because on<14:11:18.540> network<14:11:18.776> diagrams<14:11:19.436> a<14:11:20.340> cloud<14:11:20.520> is<14:11:20.880> used<14:11:21.116> to 14:11:21.350 --> 14:11:21.360 align:start position:0% on network diagrams a cloud is used to 14:11:21.360 --> 14:11:22.906 align:start position:0% on network diagrams a cloud is used to represent<14:11:22.140> it 14:11:22.906 --> 14:11:22.916 align:start position:0% represent it 14:11:22.916 --> 14:11:26.150 align:start position:0% represent it now<14:11:23.520> because<14:11:23.936> of<14:11:24.416> this<14:11:24.660> Geographic<14:11:25.616> distance 14:11:26.150 --> 14:11:26.160 align:start position:0% now because of this Geographic distance 14:11:26.160 --> 14:11:28.850 align:start position:0% now because of this Geographic distance lands<14:11:27.116> are<14:11:27.300> generally<14:11:27.596> slower<14:11:28.200> than<14:11:28.380> lands 14:11:28.850 --> 14:11:28.860 align:start position:0% lands are generally slower than lands 14:11:28.860 --> 14:11:31.130 align:start position:0% lands are generally slower than lands because<14:11:29.456> they<14:11:29.936> have<14:11:30.060> to<14:11:30.240> as<14:11:30.540> it<14:11:30.776> makes<14:11:30.900> sense 14:11:31.130 --> 14:11:31.140 align:start position:0% because they have to as it makes sense 14:11:31.140 --> 14:11:33.946 align:start position:0% because they have to as it makes sense travel<14:11:31.500> a<14:11:31.860> longer<14:11:32.220> distance<14:11:32.456> to<14:11:33.180> deliver<14:11:33.360> data 14:11:33.946 --> 14:11:33.956 align:start position:0% travel a longer distance to deliver data 14:11:33.956 --> 14:11:35.810 align:start position:0% travel a longer distance to deliver data just<14:11:34.616> like<14:11:34.860> if<14:11:35.096> I<14:11:35.276> sent<14:11:35.456> a<14:11:35.640> letter 14:11:35.810 --> 14:11:35.820 align:start position:0% just like if I sent a letter 14:11:35.820 --> 14:11:37.426 align:start position:0% just like if I sent a letter internationally<14:11:36.720> it's<14:11:37.080> going<14:11:37.256> to<14:11:37.380> take 14:11:37.426 --> 14:11:37.436 align:start position:0% internationally it's going to take 14:11:37.436 --> 14:11:39.586 align:start position:0% internationally it's going to take longer<14:11:37.860> to<14:11:37.980> get<14:11:38.160> there<14:11:38.340> than<14:11:38.756> one<14:11:39.000> across<14:11:39.416> town 14:11:39.586 --> 14:11:39.596 align:start position:0% longer to get there than one across town 14:11:39.596 --> 14:11:41.746 align:start position:0% longer to get there than one across town or<14:11:39.840> even<14:11:39.956> across<14:11:40.380> the<14:11:40.500> country<14:11:40.740> that<14:11:41.520> being 14:11:41.746 --> 14:11:41.756 align:start position:0% or even across the country that being 14:11:41.756 --> 14:11:45.350 align:start position:0% or even across the country that being said<14:11:42.060> newer<14:11:42.900> Technologies<14:11:43.616> such<14:11:44.580> as<14:11:44.756> fiber 14:11:45.350 --> 14:11:45.360 align:start position:0% said newer Technologies such as fiber 14:11:45.360 --> 14:11:48.710 align:start position:0% said newer Technologies such as fiber optics<14:11:45.720> and<14:11:46.740> etc<14:11:47.220> etc<14:11:47.340> are<14:11:47.756> making<14:11:48.060> Wan 14:11:48.710 --> 14:11:48.720 align:start position:0% optics and etc etc are making Wan 14:11:48.720 --> 14:11:50.926 align:start position:0% optics and etc etc are making Wan connections<14:11:49.320> faster<14:11:49.680> and<14:11:50.340> therefore<14:11:50.700> are 14:11:50.926 --> 14:11:50.936 align:start position:0% connections faster and therefore are 14:11:50.936 --> 14:11:52.850 align:start position:0% connections faster and therefore are connecting<14:11:51.360> parts<14:11:51.660> of<14:11:51.900> the<14:11:52.020> globe<14:11:52.320> that<14:11:52.680> have 14:11:52.850 --> 14:11:52.860 align:start position:0% connecting parts of the globe that have 14:11:52.860 --> 14:11:55.070 align:start position:0% connecting parts of the globe that have never<14:11:53.040> really<14:11:53.276> been<14:11:53.456> connected<14:11:53.880> before 14:11:55.070 --> 14:11:55.080 align:start position:0% never really been connected before 14:11:55.080 --> 14:11:58.426 align:start position:0% never really been connected before so<14:11:55.740> here's<14:11:56.400> an<14:11:56.700> example<14:11:57.240> of<14:11:57.596> what<14:11:57.900> a<14:11:58.080> wide<14:11:58.200> area 14:11:58.426 --> 14:11:58.436 align:start position:0% so here's an example of what a wide area 14:11:58.436 --> 14:12:00.530 align:start position:0% so here's an example of what a wide area network<14:11:58.800> might<14:11:59.340> look<14:11:59.520> like<14:11:59.640> let's<14:12:00.180> say<14:12:00.360> for 14:12:00.530 --> 14:12:00.540 align:start position:0% network might look like let's say for 14:12:00.540 --> 14:12:02.746 align:start position:0% network might look like let's say for example<14:12:00.776> that<14:12:01.020> a<14:12:01.140> company<14:12:01.256> had<14:12:01.800> two<14:12:02.220> branches 14:12:02.746 --> 14:12:02.756 align:start position:0% example that a company had two branches 14:12:02.756 --> 14:12:04.670 align:start position:0% example that a company had two branches one<14:12:03.480> in<14:12:03.720> New<14:12:03.956> York 14:12:04.670 --> 14:12:04.680 align:start position:0% one in New York 14:12:04.680 --> 14:12:06.766 align:start position:0% one in New York and<14:12:05.040> the<14:12:05.160> one<14:12:05.340> in<14:12:05.456> Houston<14:12:05.640> each<14:12:06.480> of<14:12:06.660> the 14:12:06.766 --> 14:12:06.776 align:start position:0% and the one in Houston each of the 14:12:06.776 --> 14:12:09.530 align:start position:0% and the one in Houston each of the branches<14:12:07.320> has<14:12:07.740> their<14:12:08.040> own<14:12:08.276> local<14:12:09.116> area 14:12:09.530 --> 14:12:09.540 align:start position:0% branches has their own local area 14:12:09.540 --> 14:12:11.510 align:start position:0% branches has their own local area network 14:12:11.510 --> 14:12:11.520 align:start position:0% network 14:12:11.520 --> 14:12:14.510 align:start position:0% network here<14:12:11.820> the<14:12:12.300> one<14:12:12.416> in<14:12:12.596> New<14:12:12.776> York<14:12:12.956> and<14:12:13.800> the<14:12:14.220> one<14:12:14.340> in 14:12:14.510 --> 14:12:14.520 align:start position:0% here the one in New York and the one in 14:12:14.520 --> 14:12:16.550 align:start position:0% here the one in New York and the one in Houston<14:12:14.776> obviously<14:12:15.776> these<14:12:16.020> are<14:12:16.140> simplified 14:12:16.550 --> 14:12:16.560 align:start position:0% Houston obviously these are simplified 14:12:16.560 --> 14:12:19.246 align:start position:0% Houston obviously these are simplified so<14:12:16.980> imagine<14:12:17.220> that<14:12:17.640> instead<14:12:18.240> of<14:12:18.300> just<14:12:18.480> two<14:12:18.660> PCS 14:12:19.246 --> 14:12:19.256 align:start position:0% so imagine that instead of just two PCS 14:12:19.256 --> 14:12:21.290 align:start position:0% so imagine that instead of just two PCS on<14:12:19.380> each<14:12:19.560> there<14:12:19.916> are<14:12:20.096> maybe<14:12:20.276> five<14:12:20.820> thousand 14:12:21.290 --> 14:12:21.300 align:start position:0% on each there are maybe five thousand 14:12:21.300 --> 14:12:23.330 align:start position:0% on each there are maybe five thousand and<14:12:21.660> instead<14:12:22.140> of<14:12:22.256> just<14:12:22.436> one<14:12:22.680> server<14:12:23.096> maybe 14:12:23.330 --> 14:12:23.340 align:start position:0% and instead of just one server maybe 14:12:23.340 --> 14:12:26.570 align:start position:0% and instead of just one server maybe there<14:12:23.700> are<14:12:23.880> 20.<14:12:24.360> but<14:12:25.200> they<14:12:25.860> each<14:12:26.040> have<14:12:26.276> their 14:12:26.570 --> 14:12:26.580 align:start position:0% there are 20. but they each have their 14:12:26.580 --> 14:12:29.266 align:start position:0% there are 20. but they each have their own<14:12:26.700> switch<14:12:27.060> to<14:12:27.776> talk<14:12:27.956> locally<14:12:28.616> to<14:12:29.096> one 14:12:29.266 --> 14:12:29.276 align:start position:0% own switch to talk locally to one 14:12:29.276 --> 14:12:32.266 align:start position:0% own switch to talk locally to one another<14:12:29.456> through<14:12:30.180> Mac<14:12:30.416> addresses 14:12:32.266 --> 14:12:32.276 align:start position:0% another through Mac addresses 14:12:32.276 --> 14:12:35.150 align:start position:0% another through Mac addresses then<14:12:33.060> there's<14:12:33.416> a<14:12:33.660> router<14:12:34.020> on<14:12:34.616> the<14:12:34.740> edge<14:12:34.916> of 14:12:35.150 --> 14:12:35.160 align:start position:0% then there's a router on the edge of 14:12:35.160 --> 14:12:37.790 align:start position:0% then there's a router on the edge of each<14:12:35.400> Network<14:12:35.580> that<14:12:36.240> connects<14:12:36.596> it<14:12:36.720> out<14:12:36.840> to<14:12:37.380> the 14:12:37.790 --> 14:12:37.800 align:start position:0% each Network that connects it out to the 14:12:37.800 --> 14:12:39.946 align:start position:0% each Network that connects it out to the WAN<14:12:38.096> or<14:12:38.820> the<14:12:39.180> internet 14:12:39.946 --> 14:12:39.956 align:start position:0% WAN or the internet 14:12:39.956 --> 14:12:43.790 align:start position:0% WAN or the internet of<14:12:40.436> course<14:12:40.616> the<14:12:41.456> WAN<14:12:42.140> if<14:12:43.140> configured 14:12:43.790 --> 14:12:43.800 align:start position:0% of course the WAN if configured 14:12:43.800 --> 14:12:47.266 align:start position:0% of course the WAN if configured correctly<14:12:44.540> can<14:12:45.540> also<14:12:46.140> connect<14:12:46.380> these<14:12:46.980> two 14:12:47.266 --> 14:12:47.276 align:start position:0% correctly can also connect these two 14:12:47.276 --> 14:12:49.970 align:start position:0% correctly can also connect these two lands<14:12:48.240> as<14:12:48.540> though<14:12:48.720> they<14:12:49.020> seem<14:12:49.320> like<14:12:49.616> they're 14:12:49.970 --> 14:12:49.980 align:start position:0% lands as though they seem like they're 14:12:49.980 --> 14:12:52.370 align:start position:0% lands as though they seem like they're in<14:12:50.456> the<14:12:50.640> same<14:12:50.880> location<14:12:51.360> just<14:12:51.956> like<14:12:52.140> their 14:12:52.370 --> 14:12:52.380 align:start position:0% in the same location just like their 14:12:52.380 --> 14:12:55.606 align:start position:0% in the same location just like their next<14:12:52.616> door<14:12:52.880> now<14:12:53.880> we<14:12:54.240> could<14:12:54.480> set<14:12:55.140> up<14:12:55.256> our<14:12:55.500> own 14:12:55.606 --> 14:12:55.616 align:start position:0% next door now we could set up our own 14:12:55.616 --> 14:12:58.370 align:start position:0% next door now we could set up our own Wan<14:12:55.980> in<14:12:56.580> other<14:12:56.700> words<14:12:56.820> we<14:12:57.240> could<14:12:57.540> have<14:12:57.900> our<14:12:58.200> own 14:12:58.370 --> 14:12:58.380 align:start position:0% Wan in other words we could have our own 14:12:58.380 --> 14:13:02.390 align:start position:0% Wan in other words we could have our own cables<14:12:59.160> and<14:12:59.400> wires<14:12:59.820> running<14:13:00.320> through<14:13:01.320> uh<14:13:01.980> from 14:13:02.390 --> 14:13:02.400 align:start position:0% cables and wires running through uh from 14:13:02.400 --> 14:13:04.370 align:start position:0% cables and wires running through uh from New<14:13:02.700> York<14:13:02.880> to<14:13:03.180> Houston<14:13:03.360> and<14:13:03.956> that's<14:13:04.140> going<14:13:04.320> to 14:13:04.370 --> 14:13:04.380 align:start position:0% New York to Houston and that's going to 14:13:04.380 --> 14:13:05.926 align:start position:0% New York to Houston and that's going to get<14:13:04.500> really<14:13:04.616> expensive<14:13:05.160> and<14:13:05.520> so<14:13:05.640> we've<14:13:05.820> come 14:13:05.926 --> 14:13:05.936 align:start position:0% get really expensive and so we've come 14:13:05.936 --> 14:13:08.586 align:start position:0% get really expensive and so we've come up<14:13:06.060> with<14:13:06.180> Technologies<14:13:06.720> to<14:13:07.080> use<14:13:07.200> the<14:13:07.560> existing 14:13:08.586 --> 14:13:08.596 align:start position:0% up with Technologies to use the existing 14:13:08.596 --> 14:13:13.670 align:start position:0% up with Technologies to use the existing Wan<14:13:09.596> that's<14:13:09.776> out<14:13:10.020> there<14:13:10.200> I.E<14:13:11.096> the<14:13:11.640> internet 14:13:13.670 --> 14:13:13.680 align:start position:0% Wan that's out there I.E the internet 14:13:13.680 --> 14:13:16.190 align:start position:0% Wan that's out there I.E the internet in<14:13:14.220> order<14:13:14.400> to<14:13:14.756> create<14:13:15.000> secure<14:13:15.596> connections 14:13:16.190 --> 14:13:16.200 align:start position:0% in order to create secure connections 14:13:16.200 --> 14:13:19.190 align:start position:0% in order to create secure connections between<14:13:16.740> two<14:13:17.340> locations<14:13:17.936> without<14:13:18.540> having<14:13:18.900> to 14:13:19.190 --> 14:13:19.200 align:start position:0% between two locations without having to 14:13:19.200 --> 14:13:21.766 align:start position:0% between two locations without having to actually<14:13:19.616> physically<14:13:20.340> lay<14:13:20.756> our<14:13:21.060> own<14:13:21.180> chords 14:13:21.766 --> 14:13:21.776 align:start position:0% actually physically lay our own chords 14:13:21.776 --> 14:13:24.830 align:start position:0% actually physically lay our own chords however<14:13:22.560> the<14:13:23.220> idea<14:13:23.400> is<14:13:23.580> the<14:13:23.820> same<14:13:24.000> we<14:13:24.660> connect 14:13:24.830 --> 14:13:24.840 align:start position:0% however the idea is the same we connect 14:13:24.840 --> 14:13:27.890 align:start position:0% however the idea is the same we connect two<14:13:25.200> lands<14:13:25.680> through<14:13:26.400> a<14:13:27.000> Wan 14:13:27.890 --> 14:13:27.900 align:start position:0% two lands through a Wan 14:13:27.900 --> 14:13:30.946 align:start position:0% two lands through a Wan and<14:13:28.320> this<14:13:28.436> allows<14:13:28.916> users<14:13:29.700> in<14:13:30.116> both<14:13:30.300> locations 14:13:30.946 --> 14:13:30.956 align:start position:0% and this allows users in both locations 14:13:30.956 --> 14:13:33.106 align:start position:0% and this allows users in both locations to<14:13:31.616> share<14:13:31.800> data<14:13:32.220> easily 14:13:33.106 --> 14:13:33.116 align:start position:0% to share data easily 14:13:33.116 --> 14:13:35.030 align:start position:0% to share data easily a<14:13:33.480> great<14:13:33.660> example<14:13:33.956> of<14:13:34.140> how<14:13:34.320> this<14:13:34.436> is<14:13:34.616> deployed 14:13:35.030 --> 14:13:35.040 align:start position:0% a great example of how this is deployed 14:13:35.040 --> 14:13:37.970 align:start position:0% a great example of how this is deployed worldwide<14:13:35.520> would<14:13:35.756> be<14:13:35.880> Banks<14:13:36.596> or<14:13:37.320> for<14:13:37.800> instance 14:13:37.970 --> 14:13:37.980 align:start position:0% worldwide would be Banks or for instance 14:13:37.980 --> 14:13:40.906 align:start position:0% worldwide would be Banks or for instance American<14:13:38.456> Express<14:13:39.000> or<14:13:39.900> chase 14:13:40.906 --> 14:13:40.916 align:start position:0% American Express or chase 14:13:40.916 --> 14:13:42.946 align:start position:0% American Express or chase you<14:13:41.580> can<14:13:41.700> buy<14:13:42.000> something<14:13:42.300> with<14:13:42.596> your<14:13:42.776> American 14:13:42.946 --> 14:13:42.956 align:start position:0% you can buy something with your American 14:13:42.956 --> 14:13:45.290 align:start position:0% you can buy something with your American Express<14:13:43.256> card<14:13:43.680> just<14:13:44.096> about<14:13:44.276> anywhere<14:13:44.880> in<14:13:45.116> the 14:13:45.290 --> 14:13:45.300 align:start position:0% Express card just about anywhere in the 14:13:45.300 --> 14:13:48.586 align:start position:0% Express card just about anywhere in the world<14:13:45.560> and<14:13:46.560> it<14:13:47.520> still<14:13:47.700> takes<14:13:48.000> the<14:13:48.180> money<14:13:48.360> out 14:13:48.586 --> 14:13:48.596 align:start position:0% world and it still takes the money out 14:13:48.596 --> 14:13:50.570 align:start position:0% world and it still takes the money out of<14:13:48.720> your<14:13:48.900> bank<14:13:49.140> or<14:13:49.680> puts<14:13:49.980> it<14:13:50.096> onto<14:13:50.400> your 14:13:50.570 --> 14:13:50.580 align:start position:0% of your bank or puts it onto your 14:13:50.580 --> 14:13:53.510 align:start position:0% of your bank or puts it onto your account<14:13:50.756> almost<14:13:51.540> instantaneously 14:13:53.510 --> 14:13:53.520 align:start position:0% account almost instantaneously 14:13:53.520 --> 14:13:56.266 align:start position:0% account almost instantaneously now<14:13:54.116> the<14:13:54.416> process<14:13:54.720> of<14:13:55.020> establishing<14:13:55.680> a<14:13:56.160> wide 14:13:56.266 --> 14:13:56.276 align:start position:0% now the process of establishing a wide 14:13:56.276 --> 14:13:59.690 align:start position:0% now the process of establishing a wide area<14:13:56.520> network<14:13:56.936> is<14:13:57.720> really<14:13:58.080> it<14:13:58.800> can<14:13:59.220> be<14:13:59.456> quite 14:13:59.690 --> 14:13:59.700 align:start position:0% area network is really it can be quite 14:13:59.700 --> 14:14:01.970 align:start position:0% area network is really it can be quite complicated<14:14:00.300> although<14:14:01.200> it's<14:14:01.320> gotten<14:14:01.740> more 14:14:01.970 --> 14:14:01.980 align:start position:0% complicated although it's gotten more 14:14:01.980 --> 14:14:04.010 align:start position:0% complicated although it's gotten more and<14:14:02.160> more<14:14:02.400> simplified<14:14:02.820> over<14:14:03.116> the<14:14:03.360> years<14:14:03.480> so 14:14:04.010 --> 14:14:04.020 align:start position:0% and more simplified over the years so 14:14:04.020 --> 14:14:05.210 align:start position:0% and more simplified over the years so I'm<14:14:04.140> just<14:14:04.256> going<14:14:04.380> to<14:14:04.436> go<14:14:04.500> over<14:14:04.616> some<14:14:04.916> of<14:14:05.040> the 14:14:05.210 --> 14:14:05.220 align:start position:0% I'm just going to go over some of the 14:14:05.220 --> 14:14:06.586 align:start position:0% I'm just going to go over some of the basic<14:14:05.580> steps<14:14:05.936> and<14:14:06.060> do<14:14:06.240> it<14:14:06.300> in<14:14:06.416> a<14:14:06.540> really 14:14:06.586 --> 14:14:06.596 align:start position:0% basic steps and do it in a really 14:14:06.596 --> 14:14:09.290 align:start position:0% basic steps and do it in a really simplified<14:14:06.956> manner<14:14:07.500> uh<14:14:08.400> basically<14:14:08.936> what<14:14:09.180> you 14:14:09.290 --> 14:14:09.300 align:start position:0% simplified manner uh basically what you 14:14:09.300 --> 14:14:11.690 align:start position:0% simplified manner uh basically what you need<14:14:09.416> to<14:14:09.596> understand<14:14:09.720> for<14:14:10.140> Network<14:14:10.320> plus<14:14:10.740> a 14:14:11.690 --> 14:14:11.700 align:start position:0% need to understand for Network plus a 14:14:11.700 --> 14:14:13.150 align:start position:0% need to understand for Network plus a good<14:14:12.000> way<14:14:12.116> to<14:14:12.300> start<14:14:12.480> with<14:14:12.720> the<14:14:12.840> Implement 14:14:13.150 --> 14:14:13.160 align:start position:0% good way to start with the Implement 14:14:13.160 --> 14:14:15.586 align:start position:0% good way to start with the Implement implementation<14:14:14.160> process<14:14:14.700> to<14:14:14.936> set<14:14:15.116> up<14:14:15.240> what<14:14:15.416> we 14:14:15.586 --> 14:14:15.596 align:start position:0% implementation process to set up what we 14:14:15.596 --> 14:14:20.030 align:start position:0% implementation process to set up what we call<14:14:15.776> a<14:14:16.380> VPN<14:14:16.916> or<14:14:17.756> a<14:14:18.060> virtual 14:14:20.030 --> 14:14:20.040 align:start position:0% call a VPN or a virtual 14:14:20.040 --> 14:14:22.670 align:start position:0% call a VPN or a virtual private 14:14:22.670 --> 14:14:22.680 align:start position:0% private 14:14:22.680 --> 14:14:25.370 align:start position:0% private Network<14:14:23.340> so<14:14:24.000> the<14:14:24.116> name<14:14:24.240> implies<14:14:24.720> it's<14:14:25.020> not 14:14:25.370 --> 14:14:25.380 align:start position:0% Network so the name implies it's not 14:14:25.380 --> 14:14:27.530 align:start position:0% Network so the name implies it's not actually<14:14:25.916> a<14:14:26.220> private<14:14:26.520> Network<14:14:26.700> that<14:14:27.300> would<14:14:27.480> be 14:14:27.530 --> 14:14:27.540 align:start position:0% actually a private Network that would be 14:14:27.540 --> 14:14:29.266 align:start position:0% actually a private Network that would be one<14:14:27.776> in<14:14:27.956> which<14:14:28.140> I<14:14:28.436> actually<14:14:28.560> have<14:14:28.916> a<14:14:29.096> cord 14:14:29.266 --> 14:14:29.276 align:start position:0% one in which I actually have a cord 14:14:29.276 --> 14:14:31.606 align:start position:0% one in which I actually have a cord stretched<14:14:30.060> across<14:14:30.480> the<14:14:30.596> country<14:14:30.776> connecting 14:14:31.606 --> 14:14:31.616 align:start position:0% stretched across the country connecting 14:14:31.616 --> 14:14:34.606 align:start position:0% stretched across the country connecting one<14:14:32.276> computer<14:14:32.456> to<14:14:32.820> another<14:14:33.020> rather<14:14:34.020> this<14:14:34.256> is<14:14:34.380> a 14:14:34.606 --> 14:14:34.616 align:start position:0% one computer to another rather this is a 14:14:34.616 --> 14:14:36.290 align:start position:0% one computer to another rather this is a virtual<14:14:34.916> private<14:14:35.400> Network 14:14:36.290 --> 14:14:36.300 align:start position:0% virtual private Network 14:14:36.300 --> 14:14:39.830 align:start position:0% virtual private Network so<14:14:37.080> this<14:14:37.500> is<14:14:37.740> a<14:14:38.040> type<14:14:38.160> of<14:14:38.340> Wan<14:14:38.700> and<14:14:39.540> what<14:14:39.720> it 14:14:39.830 --> 14:14:39.840 align:start position:0% so this is a type of Wan and what it 14:14:39.840 --> 14:14:44.030 align:start position:0% so this is a type of Wan and what it does<14:14:40.080> is<14:14:40.800> it<14:14:40.980> actually<14:14:41.540> allows<14:14:42.540> us 14:14:44.030 --> 14:14:44.040 align:start position:0% does is it actually allows us 14:14:44.040 --> 14:14:48.050 align:start position:0% does is it actually allows us to<14:14:44.640> use<14:14:44.880> the<14:14:45.416> public<14:14:45.596> Wan<14:14:46.200> the<14:14:46.740> internet<14:14:47.060> and 14:14:48.050 --> 14:14:48.060 align:start position:0% to use the public Wan the internet and 14:14:48.060 --> 14:14:51.830 align:start position:0% to use the public Wan the internet and create<14:14:48.300> a<14:14:48.900> tunnel<14:14:49.256> through<14:14:49.740> it 14:14:51.830 --> 14:14:51.840 align:start position:0% create a tunnel through it 14:14:51.840 --> 14:14:54.530 align:start position:0% create a tunnel through it called<14:14:52.256> a<14:14:52.436> virtual<14:14:52.800> private<14:14:53.456> Network<14:14:53.700> that 14:14:54.530 --> 14:14:54.540 align:start position:0% called a virtual private Network that 14:14:54.540 --> 14:14:57.050 align:start position:0% called a virtual private Network that then<14:14:54.840> makes<14:14:55.500> it<14:14:55.740> seem<14:14:56.040> like<14:14:56.700> the<14:14:56.880> two 14:14:57.050 --> 14:14:57.060 align:start position:0% then makes it seem like the two 14:14:57.060 --> 14:14:59.330 align:start position:0% then makes it seem like the two locations<14:14:57.720> are<14:14:58.320> right<14:14:58.560> there<14:14:58.740> next<14:14:58.980> to<14:14:59.160> each 14:14:59.330 --> 14:14:59.340 align:start position:0% locations are right there next to each 14:14:59.340 --> 14:15:01.670 align:start position:0% locations are right there next to each other<14:14:59.456> the<14:15:00.180> benefit<14:15:00.360> of<14:15:00.660> a<14:15:00.776> VPN<14:15:01.200> is<14:15:01.380> that<14:15:01.500> it 14:15:01.670 --> 14:15:01.680 align:start position:0% other the benefit of a VPN is that it 14:15:01.680 --> 14:15:03.230 align:start position:0% other the benefit of a VPN is that it makes<14:15:01.860> it<14:15:02.096> secure 14:15:03.230 --> 14:15:03.240 align:start position:0% makes it secure 14:15:03.240 --> 14:15:06.650 align:start position:0% makes it secure so<14:15:03.840> once<14:15:04.320> you<14:15:04.580> basically<14:15:05.580> install<14:15:06.116> the 14:15:06.650 --> 14:15:06.660 align:start position:0% so once you basically install the 14:15:06.660 --> 14:15:07.906 align:start position:0% so once you basically install the settings<14:15:06.776> you<14:15:07.140> need<14:15:07.256> to<14:15:07.380> put<14:15:07.616> in<14:15:07.740> some 14:15:07.906 --> 14:15:07.916 align:start position:0% settings you need to put in some 14:15:07.916 --> 14:15:10.426 align:start position:0% settings you need to put in some administrative<14:15:08.520> policies<14:15:09.180> and<14:15:09.416> rules<14:15:09.776> so<14:15:10.256> not 14:15:10.426 --> 14:15:10.436 align:start position:0% administrative policies and rules so not 14:15:10.436 --> 14:15:12.710 align:start position:0% administrative policies and rules so not just<14:15:10.680> anyone<14:15:11.220> can<14:15:11.580> tap<14:15:11.880> into<14:15:12.000> your<14:15:12.360> tunnel 14:15:12.710 --> 14:15:12.720 align:start position:0% just anyone can tap into your tunnel 14:15:12.720 --> 14:15:14.746 align:start position:0% just anyone can tap into your tunnel otherwise<14:15:13.436> it<14:15:13.800> wouldn't<14:15:13.916> be<14:15:14.096> very<14:15:14.276> secure<14:15:14.640> and 14:15:14.746 --> 14:15:14.756 align:start position:0% otherwise it wouldn't be very secure and 14:15:14.756 --> 14:15:16.670 align:start position:0% otherwise it wouldn't be very secure and there<14:15:14.936> wouldn't<14:15:15.060> be<14:15:15.240> any<14:15:15.416> point<14:15:15.720> we<14:15:16.380> also<14:15:16.616> need 14:15:16.670 --> 14:15:16.680 align:start position:0% there wouldn't be any point we also need 14:15:16.680 --> 14:15:18.350 align:start position:0% there wouldn't be any point we also need to<14:15:16.800> select<14:15:17.096> certain<14:15:17.276> users<14:15:17.880> who<14:15:18.116> are<14:15:18.240> going<14:15:18.300> to 14:15:18.350 --> 14:15:18.360 align:start position:0% to select certain users who are going to 14:15:18.360 --> 14:15:20.446 align:start position:0% to select certain users who are going to be<14:15:18.480> able<14:15:18.540> to<14:15:18.660> get<14:15:18.776> access<14:15:19.020> to<14:15:19.436> it<14:15:19.616> and<14:15:20.096> how<14:15:20.276> we 14:15:20.446 --> 14:15:20.456 align:start position:0% be able to get access to it and how we 14:15:20.456 --> 14:15:21.890 align:start position:0% be able to get access to it and how we want<14:15:20.580> to<14:15:20.700> allow<14:15:20.936> them<14:15:21.060> to<14:15:21.300> have<14:15:21.416> these<14:15:21.720> remote 14:15:21.890 --> 14:15:21.900 align:start position:0% want to allow them to have these remote 14:15:21.900 --> 14:15:24.406 align:start position:0% want to allow them to have these remote capabilities<14:15:22.560> we'll<14:15:22.916> talk<14:15:23.096> about<14:15:23.220> a<14:15:23.456> VPN<14:15:23.936> in<14:15:24.116> a 14:15:24.406 --> 14:15:24.416 align:start position:0% capabilities we'll talk about a VPN in a 14:15:24.416 --> 14:15:25.670 align:start position:0% capabilities we'll talk about a VPN in a bit<14:15:24.540> more<14:15:24.720> detail<14:15:25.080> and<14:15:25.200> we've<14:15:25.380> talked<14:15:25.616> about 14:15:25.670 --> 14:15:25.680 align:start position:0% bit more detail and we've talked about 14:15:25.680 --> 14:15:27.350 align:start position:0% bit more detail and we've talked about it<14:15:25.860> a<14:15:25.980> bit<14:15:26.096> in<14:15:26.220> the<14:15:26.340> past 14:15:27.350 --> 14:15:27.360 align:start position:0% it a bit in the past 14:15:27.360 --> 14:15:30.650 align:start position:0% it a bit in the past finally<14:15:28.080> we<14:15:28.320> have<14:15:28.500> to<14:15:28.740> add<14:15:29.040> the<14:15:29.700> user<14:15:30.116> accounts 14:15:30.650 --> 14:15:30.660 align:start position:0% finally we have to add the user accounts 14:15:30.660 --> 14:15:33.106 align:start position:0% finally we have to add the user accounts to<14:15:31.140> our<14:15:31.680> local<14:15:31.916> networks 14:15:33.106 --> 14:15:33.116 align:start position:0% to our local networks 14:15:33.116 --> 14:15:35.390 align:start position:0% to our local networks so<14:15:33.596> that<14:15:33.776> then<14:15:34.020> they<14:15:34.200> can<14:15:34.380> communicate 14:15:35.390 --> 14:15:35.400 align:start position:0% so that then they can communicate 14:15:35.400 --> 14:15:37.850 align:start position:0% so that then they can communicate throughout<14:15:36.180> uh<14:15:36.720> the<14:15:37.020> Wan 14:15:37.850 --> 14:15:37.860 align:start position:0% throughout uh the Wan 14:15:37.860 --> 14:15:40.310 align:start position:0% throughout uh the Wan this<14:15:38.276> can<14:15:38.400> be<14:15:38.520> configured<14:15:38.936> using<14:15:39.416> either<14:15:39.660> IP 14:15:40.310 --> 14:15:40.320 align:start position:0% this can be configured using either IP 14:15:40.320 --> 14:15:43.370 align:start position:0% this can be configured using either IP addresses<14:15:40.916> or<14:15:41.456> Mac<14:15:41.700> addresses<14:15:42.240> or<14:15:42.840> domain 14:15:43.370 --> 14:15:43.380 align:start position:0% addresses or Mac addresses or domain 14:15:43.380 --> 14:15:45.830 align:start position:0% addresses or Mac addresses or domain names<14:15:43.616> so<14:15:44.456> just<14:15:44.756> to<14:15:44.880> go<14:15:45.000> back<14:15:45.116> over<14:15:45.300> that<14:15:45.540> again 14:15:45.830 --> 14:15:45.840 align:start position:0% names so just to go back over that again 14:15:45.840 --> 14:15:49.190 align:start position:0% names so just to go back over that again I<14:15:46.500> create<14:15:46.740> the<14:15:47.160> VPN<14:15:47.936> I<14:15:48.360> give<14:15:48.540> access<14:15:48.776> to<14:15:49.080> the 14:15:49.190 --> 14:15:49.200 align:start position:0% I create the VPN I give access to the 14:15:49.200 --> 14:15:51.530 align:start position:0% I create the VPN I give access to the users<14:15:49.560> and<14:15:50.040> then<14:15:50.160> I<14:15:50.400> connect<14:15:50.580> those<14:15:51.000> users<14:15:51.300> to 14:15:51.530 --> 14:15:51.540 align:start position:0% users and then I connect those users to 14:15:51.540 --> 14:15:53.810 align:start position:0% users and then I connect those users to the<14:15:51.720> network<14:15:52.096> perhaps<14:15:53.096> I<14:15:53.276> connect<14:15:53.456> them<14:15:53.700> to 14:15:53.810 --> 14:15:53.820 align:start position:0% the network perhaps I connect them to 14:15:53.820 --> 14:15:56.446 align:start position:0% the network perhaps I connect them to the<14:15:53.936> network<14:15:54.116> from<14:15:54.540> home<14:15:55.040> perhaps<14:15:56.040> from<14:15:56.276> their 14:15:56.446 --> 14:15:56.456 align:start position:0% the network from home perhaps from their 14:15:56.456 --> 14:15:59.210 align:start position:0% the network from home perhaps from their own<14:15:56.640> internet<14:15:56.936> access<14:15:57.360> at<14:15:58.140> home<14:15:58.320> or<14:15:58.800> their<14:15:59.040> own 14:15:59.210 --> 14:15:59.220 align:start position:0% own internet access at home or their own 14:15:59.220 --> 14:16:01.370 align:start position:0% own internet access at home or their own internet<14:15:59.520> router<14:16:00.116> but<14:16:00.720> in<14:16:00.900> some<14:16:01.020> way<14:16:01.140> I<14:16:01.256> have 14:16:01.370 --> 14:16:01.380 align:start position:0% internet router but in some way I have 14:16:01.380 --> 14:16:02.810 align:start position:0% internet router but in some way I have to<14:16:01.500> give<14:16:01.616> them<14:16:01.800> access<14:16:01.980> and<14:16:02.340> that<14:16:02.520> generally 14:16:02.810 --> 14:16:02.820 align:start position:0% to give them access and that generally 14:16:02.820 --> 14:16:04.730 align:start position:0% to give them access and that generally involves<14:16:03.240> some<14:16:03.596> sort<14:16:03.776> of<14:16:03.900> special<14:16:04.140> software 14:16:04.730 --> 14:16:04.740 align:start position:0% involves some sort of special software 14:16:04.740 --> 14:16:07.550 align:start position:0% involves some sort of special software or<14:16:05.340> device<14:16:05.660> and<14:16:06.660> some<14:16:07.320> sort<14:16:07.436> of 14:16:07.550 --> 14:16:07.560 align:start position:0% or device and some sort of 14:16:07.560 --> 14:16:09.946 align:start position:0% or device and some sort of authentication<14:16:08.160> such<14:16:08.580> as<14:16:08.700> a<14:16:08.936> password<14:16:09.060> or<14:16:09.540> pin 14:16:09.946 --> 14:16:09.956 align:start position:0% authentication such as a password or pin 14:16:09.956 --> 14:16:11.210 align:start position:0% authentication such as a password or pin number 14:16:11.210 --> 14:16:11.220 align:start position:0% number 14:16:11.220 --> 14:16:14.030 align:start position:0% number now<14:16:11.880> being<14:16:12.480> the<14:16:12.720> administrator<14:16:13.140> for<14:16:13.436> Awan<14:16:13.800> can 14:16:14.030 --> 14:16:14.040 align:start position:0% now being the administrator for Awan can 14:16:14.040 --> 14:16:15.106 align:start position:0% now being the administrator for Awan can actually<14:16:14.160> be<14:16:14.340> pretty<14:16:14.520> demanding<14:16:15.000> because 14:16:15.106 --> 14:16:15.116 align:start position:0% actually be pretty demanding because 14:16:15.116 --> 14:16:16.730 align:start position:0% actually be pretty demanding because it's<14:16:15.300> not<14:16:15.480> restricted<14:16:15.900> to<14:16:16.140> a<14:16:16.320> single<14:16:16.560> location 14:16:16.730 --> 14:16:16.740 align:start position:0% it's not restricted to a single location 14:16:16.740 --> 14:16:19.490 align:start position:0% it's not restricted to a single location the<14:16:17.456> job<14:16:17.700> involves<14:16:18.180> a<14:16:18.360> lot<14:16:18.480> more<14:16:18.776> than<14:16:19.140> being<14:16:19.320> a 14:16:19.490 --> 14:16:19.500 align:start position:0% the job involves a lot more than being a 14:16:19.500 --> 14:16:21.406 align:start position:0% the job involves a lot more than being a land<14:16:19.616> administrator<14:16:20.220> because<14:16:20.880> you<14:16:21.240> might 14:16:21.406 --> 14:16:21.416 align:start position:0% land administrator because you might 14:16:21.416 --> 14:16:23.446 align:start position:0% land administrator because you might have<14:16:21.596> a<14:16:21.900> land<14:16:21.956> that's<14:16:22.320> all<14:16:22.500> in<14:16:22.740> New<14:16:22.916> York<14:16:23.096> but 14:16:23.446 --> 14:16:23.456 align:start position:0% have a land that's all in New York but 14:16:23.456 --> 14:16:25.246 align:start position:0% have a land that's all in New York but if<14:16:23.640> I<14:16:23.756> have<14:16:23.880> a<14:16:24.000> win<14:16:24.116> I<14:16:24.360> could<14:16:24.480> have<14:16:24.596> offices<14:16:24.956> all 14:16:25.246 --> 14:16:25.256 align:start position:0% if I have a win I could have offices all 14:16:25.256 --> 14:16:27.530 align:start position:0% if I have a win I could have offices all over<14:16:25.436> the<14:16:25.680> world<14:16:25.860> so<14:16:26.456> the<14:16:26.640> main<14:16:26.820> tasks<14:16:27.300> though 14:16:27.530 --> 14:16:27.540 align:start position:0% over the world so the main tasks though 14:16:27.540 --> 14:16:29.266 align:start position:0% over the world so the main tasks though are<14:16:27.776> still<14:16:28.020> the<14:16:28.200> same<14:16:28.380> they're<14:16:29.096> just 14:16:29.266 --> 14:16:29.276 align:start position:0% are still the same they're just 14:16:29.276 --> 14:16:31.790 align:start position:0% are still the same they're just generally<14:16:29.520> on<14:16:29.700> a<14:16:29.820> much<14:16:29.936> larger<14:16:30.416> scale<14:16:30.776> in<14:16:31.616> fact 14:16:31.790 --> 14:16:31.800 align:start position:0% generally on a much larger scale in fact 14:16:31.800 --> 14:16:33.406 align:start position:0% generally on a much larger scale in fact almost<14:16:32.160> every<14:16:32.580> task<14:16:32.820> that<14:16:33.240> both 14:16:33.406 --> 14:16:33.416 align:start position:0% almost every task that both 14:16:33.416 --> 14:16:36.350 align:start position:0% almost every task that both administrators<14:16:34.200> would<14:16:35.096> share<14:16:35.456> is<14:16:35.700> just 14:16:36.350 --> 14:16:36.360 align:start position:0% administrators would share is just 14:16:36.360 --> 14:16:38.390 align:start position:0% administrators would share is just larger<14:16:36.776> in<14:16:37.020> scale<14:16:37.320> and<14:16:37.916> just<14:16:38.040> a<14:16:38.160> little<14:16:38.276> more 14:16:38.390 --> 14:16:38.400 align:start position:0% larger in scale and just a little more 14:16:38.400 --> 14:16:40.730 align:start position:0% larger in scale and just a little more difficult<14:16:38.756> for<14:16:39.116> the<14:16:39.180> wan<14:16:39.480> to<14:16:39.660> admin 14:16:40.730 --> 14:16:40.740 align:start position:0% difficult for the wan to admin 14:16:40.740 --> 14:16:42.830 align:start position:0% difficult for the wan to admin so<14:16:41.276> backups<14:16:41.880> are<14:16:41.936> just<14:16:42.116> as<14:16:42.240> important<14:16:42.596> on<14:16:42.720> a 14:16:42.830 --> 14:16:42.840 align:start position:0% so backups are just as important on a 14:16:42.840 --> 14:16:44.630 align:start position:0% so backups are just as important on a Wan<14:16:43.080> as<14:16:43.256> they<14:16:43.380> are<14:16:43.436> in<14:16:43.560> a<14:16:43.680> land<14:16:43.800> if<14:16:44.040> not<14:16:44.220> more<14:16:44.400> so 14:16:44.630 --> 14:16:44.640 align:start position:0% Wan as they are in a land if not more so 14:16:44.640 --> 14:16:46.730 align:start position:0% Wan as they are in a land if not more so because<14:16:45.240> data<14:16:45.660> loss<14:16:45.900> of<14:16:46.020> any<14:16:46.200> kind<14:16:46.500> is 14:16:46.730 --> 14:16:46.740 align:start position:0% because data loss of any kind is 14:16:46.740 --> 14:16:48.530 align:start position:0% because data loss of any kind is something<14:16:46.916> that<14:16:47.096> needs<14:16:47.340> to<14:16:47.400> be<14:16:47.520> avoided<14:16:48.000> it's 14:16:48.530 --> 14:16:48.540 align:start position:0% something that needs to be avoided it's 14:16:48.540 --> 14:16:50.510 align:start position:0% something that needs to be avoided it's the<14:16:48.776> way<14:16:48.956> an<14:16:49.200> admin's<14:16:49.740> job<14:16:49.916> to<14:16:50.160> be<14:16:50.276> in<14:16:50.400> charge 14:16:50.510 --> 14:16:50.520 align:start position:0% the way an admin's job to be in charge 14:16:50.520 --> 14:16:53.150 align:start position:0% the way an admin's job to be in charge of<14:16:50.700> backups<14:16:51.300> for<14:16:51.480> the<14:16:51.660> entire<14:16:52.020> wide<14:16:52.980> area 14:16:53.150 --> 14:16:53.160 align:start position:0% of backups for the entire wide area 14:16:53.160 --> 14:16:54.230 align:start position:0% of backups for the entire wide area network<14:16:53.456> and<14:16:53.756> make<14:16:53.880> sure<14:16:54.000> that<14:16:54.060> everything 14:16:54.230 --> 14:16:54.240 align:start position:0% network and make sure that everything 14:16:54.240 --> 14:16:56.990 align:start position:0% network and make sure that everything goes<14:16:54.660> well<14:16:54.840> the<14:16:55.680> actual<14:16:55.916> process<14:16:56.340> of<14:16:56.580> backing 14:16:56.990 --> 14:16:57.000 align:start position:0% goes well the actual process of backing 14:16:57.000 --> 14:16:59.330 align:start position:0% goes well the actual process of backing up<14:16:57.116> everything<14:16:57.660> is<14:16:58.020> virtually<14:16:58.436> identical<14:16:59.040> on 14:16:59.330 --> 14:16:59.340 align:start position:0% up everything is virtually identical on 14:16:59.340 --> 14:17:01.730 align:start position:0% up everything is virtually identical on both<14:16:59.520> networks<14:17:00.060> however<14:17:00.776> with<14:17:01.020> Wan<14:17:01.320> it's<14:17:01.560> much 14:17:01.730 --> 14:17:01.740 align:start position:0% both networks however with Wan it's much 14:17:01.740 --> 14:17:04.210 align:start position:0% both networks however with Wan it's much more<14:17:01.980> difficult<14:17:02.340> because<14:17:03.000> as<14:17:03.180> we<14:17:03.360> said<14:17:03.540> before 14:17:04.210 --> 14:17:04.220 align:start position:0% more difficult because as we said before 14:17:04.220 --> 14:17:07.490 align:start position:0% more difficult because as we said before lands<14:17:05.220> span<14:17:05.756> over<14:17:06.116> two<14:17:06.720> or<14:17:06.956> more<14:17:07.200> physical 14:17:07.490 --> 14:17:07.500 align:start position:0% lands span over two or more physical 14:17:07.500 --> 14:17:10.190 align:start position:0% lands span over two or more physical locations<14:17:08.720> geographically<14:17:09.720> and<14:17:10.020> are 14:17:10.190 --> 14:17:10.200 align:start position:0% locations geographically and are 14:17:10.200 --> 14:17:13.850 align:start position:0% locations geographically and are grouping<14:17:11.116> Lan<14:17:12.116> networks<14:17:12.660> together<14:17:12.840> so<14:17:13.680> we 14:17:13.850 --> 14:17:13.860 align:start position:0% grouping Lan networks together so we 14:17:13.860 --> 14:17:15.586 align:start position:0% grouping Lan networks together so we need<14:17:13.980> to<14:17:14.096> not<14:17:14.276> only<14:17:14.400> back<14:17:14.700> up<14:17:14.880> stuff<14:17:15.240> at<14:17:15.416> the 14:17:15.586 --> 14:17:15.596 align:start position:0% need to not only back up stuff at the 14:17:15.596 --> 14:17:17.150 align:start position:0% need to not only back up stuff at the individual<14:17:15.900> Land<14:17:16.140> locations<14:17:16.680> but<14:17:16.860> then<14:17:17.040> we 14:17:17.150 --> 14:17:17.160 align:start position:0% individual Land locations but then we 14:17:17.160 --> 14:17:19.550 align:start position:0% individual Land locations but then we need<14:17:17.340> to<14:17:17.456> put<14:17:17.756> all<14:17:17.936> that<14:17:18.116> together<14:17:18.360> into<14:17:19.020> one 14:17:19.550 --> 14:17:19.560 align:start position:0% need to put all that together into one 14:17:19.560 --> 14:17:22.606 align:start position:0% need to put all that together into one big<14:17:19.980> huge<14:17:20.820> backup<14:17:21.360> of<14:17:22.080> course<14:17:22.200> one<14:17:22.500> of<14:17:22.560> the 14:17:22.606 --> 14:17:22.616 align:start position:0% big huge backup of course one of the 14:17:22.616 --> 14:17:24.170 align:start position:0% big huge backup of course one of the main<14:17:22.800> differences<14:17:23.220> we<14:17:23.520> mentioned<14:17:23.880> at<14:17:24.000> the 14:17:24.170 --> 14:17:24.180 align:start position:0% main differences we mentioned at the 14:17:24.180 --> 14:17:27.470 align:start position:0% main differences we mentioned at the outset<14:17:24.480> is<14:17:24.720> speed<14:17:25.140> and<14:17:25.980> so<14:17:26.220> when<14:17:27.116> we're<14:17:27.300> trying 14:17:27.470 --> 14:17:27.480 align:start position:0% outset is speed and so when we're trying 14:17:27.480 --> 14:17:29.990 align:start position:0% outset is speed and so when we're trying to<14:17:27.720> back<14:17:27.840> stuff<14:17:28.140> up<14:17:28.380> to<14:17:29.160> a<14:17:29.340> wan<14:17:29.640> to<14:17:29.820> the 14:17:29.990 --> 14:17:30.000 align:start position:0% to back stuff up to a wan to the 14:17:30.000 --> 14:17:30.890 align:start position:0% to back stuff up to a wan to the internet 14:17:30.890 --> 14:17:30.900 align:start position:0% internet 14:17:30.900 --> 14:17:32.570 align:start position:0% internet speed<14:17:31.380> becomes<14:17:31.740> an<14:17:31.860> issue<14:17:32.096> I<14:17:32.220> can<14:17:32.400> back 14:17:32.570 --> 14:17:32.580 align:start position:0% speed becomes an issue I can back 14:17:32.580 --> 14:17:34.490 align:start position:0% speed becomes an issue I can back something<14:17:32.820> up<14:17:33.060> really<14:17:33.240> quickly<14:17:33.660> if<14:17:34.020> I<14:17:34.200> plug<14:17:34.320> it 14:17:34.490 --> 14:17:34.500 align:start position:0% something up really quickly if I plug it 14:17:34.500 --> 14:17:35.990 align:start position:0% something up really quickly if I plug it into<14:17:34.560> the<14:17:34.800> computer<14:17:34.980> when<14:17:35.580> I<14:17:35.700> start<14:17:35.820> going 14:17:35.990 --> 14:17:36.000 align:start position:0% into the computer when I start going 14:17:36.000 --> 14:17:37.490 align:start position:0% into the computer when I start going over<14:17:36.180> the<14:17:36.360> network<14:17:36.540> that's<14:17:36.900> a<14:17:37.080> little<14:17:37.140> slower 14:17:37.490 --> 14:17:37.500 align:start position:0% over the network that's a little slower 14:17:37.500 --> 14:17:39.946 align:start position:0% over the network that's a little slower and<14:17:38.040> then<14:17:38.160> when<14:17:38.400> I<14:17:38.520> start<14:17:38.640> going<14:17:38.936> over<14:17:39.240> a<14:17:39.660> Wan 14:17:39.946 --> 14:17:39.956 align:start position:0% and then when I start going over a Wan 14:17:39.956 --> 14:17:41.086 align:start position:0% and then when I start going over a Wan it's<14:17:40.140> going<14:17:40.320> to<14:17:40.380> get<14:17:40.436> a<14:17:40.560> little<14:17:40.680> bit<14:17:40.800> slower 14:17:41.086 --> 14:17:41.096 align:start position:0% it's going to get a little bit slower 14:17:41.096 --> 14:17:43.790 align:start position:0% it's going to get a little bit slower too<14:17:41.276> so<14:17:41.880> full<14:17:42.240> backups<14:17:42.840> can<14:17:43.200> take<14:17:43.500> days 14:17:43.790 --> 14:17:43.800 align:start position:0% too so full backups can take days 14:17:43.800 --> 14:17:45.830 align:start position:0% too so full backups can take days depending<14:17:44.400> on<14:17:44.520> the<14:17:44.700> size<14:17:44.820> of<14:17:45.000> the<14:17:45.116> WAN<14:17:45.360> and 14:17:45.830 --> 14:17:45.840 align:start position:0% depending on the size of the WAN and 14:17:45.840 --> 14:17:47.390 align:start position:0% depending on the size of the WAN and obviously<14:17:46.200> the<14:17:46.320> issue<14:17:46.560> with<14:17:46.680> that<14:17:46.860> is<14:17:47.040> if<14:17:47.220> it 14:17:47.390 --> 14:17:47.400 align:start position:0% obviously the issue with that is if it 14:17:47.400 --> 14:17:48.946 align:start position:0% obviously the issue with that is if it takes<14:17:47.580> days<14:17:47.880> for<14:17:48.116> me<14:17:48.240> to<14:17:48.360> back<14:17:48.480> something<14:17:48.720> up 14:17:48.946 --> 14:17:48.956 align:start position:0% takes days for me to back something up 14:17:48.956 --> 14:17:50.810 align:start position:0% takes days for me to back something up and<14:17:49.140> I'm<14:17:49.320> working<14:17:49.500> on<14:17:49.800> it<14:17:49.916> then<14:17:50.340> by<14:17:50.580> the<14:17:50.700> time 14:17:50.810 --> 14:17:50.820 align:start position:0% and I'm working on it then by the time 14:17:50.820 --> 14:17:52.790 align:start position:0% and I'm working on it then by the time it's<14:17:51.060> backed<14:17:51.360> up<14:17:51.480> it's<14:17:51.776> actually<14:17:51.956> hasn't 14:17:52.790 --> 14:17:52.800 align:start position:0% it's backed up it's actually hasn't 14:17:52.800 --> 14:17:54.710 align:start position:0% it's backed up it's actually hasn't gotten<14:17:52.980> the<14:17:53.096> backup<14:17:53.340> at<14:17:53.580> all<14:17:53.700> and<14:17:54.300> so<14:17:54.416> we<14:17:54.596> have 14:17:54.710 --> 14:17:54.720 align:start position:0% gotten the backup at all and so we have 14:17:54.720 --> 14:17:56.210 align:start position:0% gotten the backup at all and so we have to<14:17:54.776> deal<14:17:54.900> with<14:17:55.200> all<14:17:55.380> sorts<14:17:55.680> of<14:17:55.800> stuff<14:17:55.980> when 14:17:56.210 --> 14:17:56.220 align:start position:0% to deal with all sorts of stuff when 14:17:56.220 --> 14:17:57.470 align:start position:0% to deal with all sorts of stuff when we're<14:17:56.400> doing<14:17:56.580> this 14:17:57.470 --> 14:17:57.480 align:start position:0% we're doing this 14:17:57.480 --> 14:18:00.406 align:start position:0% we're doing this so<14:17:58.140> as<14:17:58.500> you<14:17:58.680> can<14:17:58.800> see<14:17:59.040> here<14:17:59.400> I<14:17:59.880> generally<14:18:00.116> might 14:18:00.406 --> 14:18:00.416 align:start position:0% so as you can see here I generally might 14:18:00.416 --> 14:18:03.350 align:start position:0% so as you can see here I generally might have<14:18:00.720> some<14:18:01.140> sort<14:18:01.380> of<14:18:01.560> off-site 14:18:03.350 --> 14:18:03.360 align:start position:0% have some sort of off-site 14:18:03.360 --> 14:18:06.350 align:start position:0% have some sort of off-site backup<14:18:04.200> area<14:18:04.616> that<14:18:05.340> all<14:18:05.520> the<14:18:05.700> data<14:18:05.936> would<14:18:06.180> sort 14:18:06.350 --> 14:18:06.360 align:start position:0% backup area that all the data would sort 14:18:06.360 --> 14:18:09.470 align:start position:0% backup area that all the data would sort of<14:18:06.480> Route<14:18:06.720> into<14:18:07.340> sometimes<14:18:08.340> what<14:18:08.520> we'll<14:18:08.700> do<14:18:08.880> is 14:18:09.470 --> 14:18:09.480 align:start position:0% of Route into sometimes what we'll do is 14:18:09.480 --> 14:18:12.230 align:start position:0% of Route into sometimes what we'll do is we'll<14:18:09.720> actually<14:18:09.956> back<14:18:10.740> stuff<14:18:10.980> onto<14:18:11.700> a<14:18:12.000> local 14:18:12.230 --> 14:18:12.240 align:start position:0% we'll actually back stuff onto a local 14:18:12.240 --> 14:18:13.370 align:start position:0% we'll actually back stuff onto a local backup 14:18:13.370 --> 14:18:13.380 align:start position:0% backup 14:18:13.380 --> 14:18:15.650 align:start position:0% backup and<14:18:13.860> then<14:18:13.916> the<14:18:14.220> local<14:18:14.340> backup<14:18:14.820> will<14:18:15.060> be<14:18:15.240> backed 14:18:15.650 --> 14:18:15.660 align:start position:0% and then the local backup will be backed 14:18:15.660 --> 14:18:18.710 align:start position:0% and then the local backup will be backed up<14:18:15.776> to<14:18:16.140> a<14:18:16.380> cloud<14:18:16.560> backup<14:18:17.096> or<14:18:17.276> a<14:18:17.456> Wan<14:18:17.756> backup 14:18:18.710 --> 14:18:18.720 align:start position:0% up to a cloud backup or a Wan backup 14:18:18.720 --> 14:18:22.490 align:start position:0% up to a cloud backup or a Wan backup so<14:18:19.616> we<14:18:19.860> have<14:18:19.980> to<14:18:20.160> deal<14:18:20.340> with<14:18:20.640> space<14:18:20.880> issues<14:18:21.500> and 14:18:22.490 --> 14:18:22.500 align:start position:0% so we have to deal with space issues and 14:18:22.500 --> 14:18:26.266 align:start position:0% so we have to deal with space issues and we<14:18:23.040> also<14:18:23.276> have<14:18:23.456> to<14:18:23.640> deal<14:18:23.880> with<14:18:24.300> speed<14:18:25.080> issues 14:18:26.266 --> 14:18:26.276 align:start position:0% we also have to deal with speed issues 14:18:26.276 --> 14:18:28.310 align:start position:0% we also have to deal with speed issues now<14:18:26.756> when<14:18:26.936> it<14:18:27.116> comes<14:18:27.300> to<14:18:27.416> backups<14:18:27.900> as<14:18:28.080> you<14:18:28.200> can 14:18:28.310 --> 14:18:28.320 align:start position:0% now when it comes to backups as you can 14:18:28.320 --> 14:18:29.810 align:start position:0% now when it comes to backups as you can imagine<14:18:28.436> that's<14:18:29.040> some<14:18:29.276> pretty<14:18:29.456> important 14:18:29.810 --> 14:18:29.820 align:start position:0% imagine that's some pretty important 14:18:29.820 --> 14:18:32.210 align:start position:0% imagine that's some pretty important data<14:18:30.180> that's<14:18:30.360> flying<14:18:30.840> over<14:18:31.020> the<14:18:31.256> network<14:18:31.436> and 14:18:32.210 --> 14:18:32.220 align:start position:0% data that's flying over the network and 14:18:32.220 --> 14:18:34.130 align:start position:0% data that's flying over the network and so<14:18:32.400> I<14:18:32.640> also<14:18:32.880> need<14:18:33.000> to<14:18:33.180> make<14:18:33.360> sure<14:18:33.540> not<14:18:33.840> only<14:18:33.956> my 14:18:34.130 --> 14:18:34.140 align:start position:0% so I also need to make sure not only my 14:18:34.140 --> 14:18:36.470 align:start position:0% so I also need to make sure not only my backups<14:18:34.616> but<14:18:34.740> my<14:18:34.860> entire<14:18:35.160> network<14:18:35.456> are<14:18:36.060> secure 14:18:36.470 --> 14:18:36.480 align:start position:0% backups but my entire network are secure 14:18:36.480 --> 14:18:38.330 align:start position:0% backups but my entire network are secure and<14:18:36.956> this<14:18:37.140> is<14:18:37.256> a<14:18:37.380> massive<14:18:37.740> job<14:18:37.916> for<14:18:38.220> the 14:18:38.330 --> 14:18:38.340 align:start position:0% and this is a massive job for the 14:18:38.340 --> 14:18:40.606 align:start position:0% and this is a massive job for the administrator<14:18:38.756> of<14:18:38.880> Rowan<14:18:39.300> in<14:18:39.540> fact<14:18:39.720> generally 14:18:40.606 --> 14:18:40.616 align:start position:0% administrator of Rowan in fact generally 14:18:40.616 --> 14:18:42.650 align:start position:0% administrator of Rowan in fact generally when<14:18:41.060> administrators<14:18:42.060> don't<14:18:42.180> do<14:18:42.360> this<14:18:42.416> they 14:18:42.650 --> 14:18:42.660 align:start position:0% when administrators don't do this they 14:18:42.660 --> 14:18:44.690 align:start position:0% when administrators don't do this they hire<14:18:42.840> someone<14:18:43.140> else<14:18:43.500> to<14:18:43.860> specifically<14:18:44.340> focus 14:18:44.690 --> 14:18:44.700 align:start position:0% hire someone else to specifically focus 14:18:44.700 --> 14:18:47.086 align:start position:0% hire someone else to specifically focus on<14:18:45.000> security<14:18:45.596> again<14:18:46.560> the<14:18:46.800> big<14:18:46.916> difference 14:18:47.086 --> 14:18:47.096 align:start position:0% on security again the big difference 14:18:47.096 --> 14:18:49.426 align:start position:0% on security again the big difference with<14:18:47.456> Wan<14:18:47.820> is<14:18:48.416> that<14:18:48.596> the<14:18:48.840> network<14:18:48.956> is<14:18:49.256> not 14:18:49.426 --> 14:18:49.436 align:start position:0% with Wan is that the network is not 14:18:49.436 --> 14:18:51.470 align:start position:0% with Wan is that the network is not limited<14:18:49.740> to<14:18:49.916> a<14:18:50.040> single<14:18:50.340> location<14:18:50.520> so<14:18:51.300> there 14:18:51.470 --> 14:18:51.480 align:start position:0% limited to a single location so there 14:18:51.480 --> 14:18:53.446 align:start position:0% limited to a single location so there are<14:18:51.596> many<14:18:51.720> more<14:18:51.900> points<14:18:52.256> for<14:18:52.500> Access<14:18:52.800> for 14:18:53.446 --> 14:18:53.456 align:start position:0% are many more points for Access for 14:18:53.456 --> 14:18:55.906 align:start position:0% are many more points for Access for people<14:18:53.700> who<14:18:54.180> might<14:18:54.416> have<14:18:54.596> nefarious<14:18:55.380> uh 14:18:55.906 --> 14:18:55.916 align:start position:0% people who might have nefarious uh 14:18:55.916 --> 14:18:58.670 align:start position:0% people who might have nefarious uh purposes<14:18:56.756> to<14:18:57.116> get<14:18:57.240> into<14:18:57.416> our<14:18:57.660> Network 14:18:58.670 --> 14:18:58.680 align:start position:0% purposes to get into our Network 14:18:58.680 --> 14:19:00.650 align:start position:0% purposes to get into our Network this<14:18:59.160> means<14:18:59.520> the<14:18:59.700> administrators<14:19:00.180> not<14:19:00.540> only 14:19:00.650 --> 14:19:00.660 align:start position:0% this means the administrators not only 14:19:00.660 --> 14:19:02.746 align:start position:0% this means the administrators not only controlling<14:19:01.616> the<14:19:01.740> security<14:19:01.980> at<14:19:02.580> each 14:19:02.746 --> 14:19:02.756 align:start position:0% controlling the security at each 14:19:02.756 --> 14:19:05.086 align:start position:0% controlling the security at each physical<14:19:03.000> location<14:19:03.416> but<14:19:04.380> also<14:19:04.680> the<14:19:04.916> security 14:19:05.086 --> 14:19:05.096 align:start position:0% physical location but also the security 14:19:05.096 --> 14:19:08.050 align:start position:0% physical location but also the security of<14:19:05.936> the<14:19:06.300> entire<14:19:06.660> network<14:19:06.900> as<14:19:07.200> a<14:19:07.380> whole 14:19:08.050 --> 14:19:08.060 align:start position:0% of the entire network as a whole 14:19:08.060 --> 14:19:10.730 align:start position:0% of the entire network as a whole theoretically<14:19:09.060> if<14:19:09.776> an<14:19:10.020> attacker<14:19:10.380> were<14:19:10.560> to 14:19:10.730 --> 14:19:10.740 align:start position:0% theoretically if an attacker were to 14:19:10.740 --> 14:19:12.350 align:start position:0% theoretically if an attacker were to infiltrate<14:19:11.160> one<14:19:11.456> of<14:19:11.580> the<14:19:11.700> lands<14:19:12.060> it<14:19:12.240> could 14:19:12.350 --> 14:19:12.360 align:start position:0% infiltrate one of the lands it could 14:19:12.360 --> 14:19:14.926 align:start position:0% infiltrate one of the lands it could infect<14:19:12.720> the<14:19:13.020> rest<14:19:13.256> of<14:19:13.436> the<14:19:13.680> WAN<14:19:13.916> so<14:19:14.520> we<14:19:14.700> have<14:19:14.820> to 14:19:14.926 --> 14:19:14.936 align:start position:0% infect the rest of the WAN so we have to 14:19:14.936 --> 14:19:16.790 align:start position:0% infect the rest of the WAN so we have to have<14:19:15.116> a<14:19:15.300> lot<14:19:15.360> of<14:19:15.540> fault<14:19:15.900> sort<14:19:16.200> of<14:19:16.256> safety 14:19:16.790 --> 14:19:16.800 align:start position:0% have a lot of fault sort of safety 14:19:16.800 --> 14:19:19.130 align:start position:0% have a lot of fault sort of safety measures<14:19:17.220> in<14:19:17.520> there<14:19:17.640> as<14:19:17.820> well<14:19:18.000> it<14:19:18.720> makes<14:19:18.900> our 14:19:19.130 --> 14:19:19.140 align:start position:0% measures in there as well it makes our 14:19:19.140 --> 14:19:21.586 align:start position:0% measures in there as well it makes our job<14:19:19.320> really<14:19:19.740> difficult<14:19:20.096> and<14:19:21.060> we<14:19:21.240> not<14:19:21.480> only 14:19:21.586 --> 14:19:21.596 align:start position:0% job really difficult and we not only 14:19:21.596 --> 14:19:24.170 align:start position:0% job really difficult and we not only have<14:19:21.840> to<14:19:22.080> spread<14:19:22.680> against<14:19:22.800> these<14:19:23.340> attacks<14:19:23.756> but 14:19:24.170 --> 14:19:24.180 align:start position:0% have to spread against these attacks but 14:19:24.180 --> 14:19:27.890 align:start position:0% have to spread against these attacks but also<14:19:24.480> the<14:19:24.776> spread<14:19:25.256> of<14:19:25.860> attacks<14:19:26.400> if<14:19:27.060> one<14:19:27.540> site 14:19:27.890 --> 14:19:27.900 align:start position:0% also the spread of attacks if one site 14:19:27.900 --> 14:19:30.230 align:start position:0% also the spread of attacks if one site gets<14:19:28.380> infiltrated<14:19:28.916> well<14:19:29.700> I<14:19:29.936> can't<14:19:30.000> do 14:19:30.230 --> 14:19:30.240 align:start position:0% gets infiltrated well I can't do 14:19:30.240 --> 14:19:31.730 align:start position:0% gets infiltrated well I can't do anything<14:19:30.416> about<14:19:30.720> that<14:19:30.956> at<14:19:31.140> that<14:19:31.320> point<14:19:31.380> but<14:19:31.616> I 14:19:31.730 --> 14:19:31.740 align:start position:0% anything about that at that point but I 14:19:31.740 --> 14:19:32.810 align:start position:0% anything about that at that point but I want<14:19:31.800> to<14:19:31.916> make<14:19:31.980> sure<14:19:32.096> all<14:19:32.276> my<14:19:32.400> other<14:19:32.520> sites 14:19:32.810 --> 14:19:32.820 align:start position:0% want to make sure all my other sites 14:19:32.820 --> 14:19:34.850 align:start position:0% want to make sure all my other sites don't<14:19:32.936> get<14:19:33.060> infiltrated<14:19:33.540> as<14:19:33.840> well 14:19:34.850 --> 14:19:34.860 align:start position:0% don't get infiltrated as well 14:19:34.860 --> 14:19:37.010 align:start position:0% don't get infiltrated as well so<14:19:35.340> here<14:19:35.580> we<14:19:35.756> see<14:19:35.880> the<14:19:36.240> same<14:19:36.360> wind<14:19:36.660> from 14:19:37.010 --> 14:19:37.020 align:start position:0% so here we see the same wind from 14:19:37.020 --> 14:19:40.370 align:start position:0% so here we see the same wind from earlier<14:19:37.320> but<14:19:38.096> unfortunately<14:19:38.700> a<14:19:39.596> virus<14:19:40.020> has 14:19:40.370 --> 14:19:40.380 align:start position:0% earlier but unfortunately a virus has 14:19:40.380 --> 14:19:42.170 align:start position:0% earlier but unfortunately a virus has been<14:19:40.560> sent<14:19:40.800> by<14:19:41.040> a<14:19:41.220> hacker<14:19:41.520> and<14:19:41.700> it's<14:19:41.880> making 14:19:42.170 --> 14:19:42.180 align:start position:0% been sent by a hacker and it's making 14:19:42.180 --> 14:19:44.690 align:start position:0% been sent by a hacker and it's making its<14:19:42.720> way<14:19:42.900> through<14:19:43.380> the<14:19:43.740> wan<14:19:44.040> to<14:19:44.456> the<14:19:44.580> other 14:19:44.690 --> 14:19:44.700 align:start position:0% its way through the wan to the other 14:19:44.700 --> 14:19:49.130 align:start position:0% its way through the wan to the other land<14:19:45.140> this<14:19:46.140> is<14:19:46.380> an<14:19:46.560> example<14:19:47.116> of<14:19:48.116> something<14:19:48.776> an 14:19:49.130 --> 14:19:49.140 align:start position:0% land this is an example of something an 14:19:49.140 --> 14:19:52.190 align:start position:0% land this is an example of something an admin<14:19:49.616> would<14:19:49.860> have<14:19:50.040> to<14:19:50.160> be<14:19:50.276> diligent<14:19:50.820> about<14:19:51.200> in 14:19:52.190 --> 14:19:52.200 align:start position:0% admin would have to be diligent about in 14:19:52.200 --> 14:19:53.870 align:start position:0% admin would have to be diligent about in some<14:19:52.320> ways<14:19:52.616> what<14:19:52.800> we<14:19:52.980> want<14:19:53.160> to<14:19:53.276> do<14:19:53.400> is<14:19:53.580> create 14:19:53.870 --> 14:19:53.880 align:start position:0% some ways what we want to do is create 14:19:53.880 --> 14:19:57.290 align:start position:0% some ways what we want to do is create some<14:19:54.240> sort<14:19:54.416> of<14:19:54.596> wall<14:19:55.020> here<14:19:55.500> so<14:19:56.040> that<14:19:56.276> way<14:19:56.520> the 14:19:57.290 --> 14:19:57.300 align:start position:0% some sort of wall here so that way the 14:19:57.300 --> 14:19:59.446 align:start position:0% some sort of wall here so that way the virus<14:19:57.776> or<14:19:58.140> the<14:19:58.320> logic<14:19:58.680> bomb<14:19:58.800> in<14:19:59.096> this<14:19:59.276> case 14:19:59.446 --> 14:19:59.456 align:start position:0% virus or the logic bomb in this case 14:19:59.456 --> 14:20:02.030 align:start position:0% virus or the logic bomb in this case couldn't<14:20:00.060> make<14:20:00.416> its<14:20:00.720> way<14:20:00.776> over<14:20:01.080> and<14:20:01.616> just<14:20:01.860> got 14:20:02.030 --> 14:20:02.040 align:start position:0% couldn't make its way over and just got 14:20:02.040 --> 14:20:04.190 align:start position:0% couldn't make its way over and just got stuck<14:20:02.400> and<14:20:02.640> stayed<14:20:02.936> in<14:20:03.060> Houston<14:20:03.240> while<14:20:04.020> it's 14:20:04.190 --> 14:20:04.200 align:start position:0% stuck and stayed in Houston while it's 14:20:04.200 --> 14:20:06.650 align:start position:0% stuck and stayed in Houston while it's still<14:20:04.380> a<14:20:04.560> pretty<14:20:04.680> bad<14:20:04.916> scenario<14:20:05.520> at<14:20:06.116> least<14:20:06.300> New 14:20:06.650 --> 14:20:06.660 align:start position:0% still a pretty bad scenario at least New 14:20:06.660 --> 14:20:09.230 align:start position:0% still a pretty bad scenario at least New York<14:20:06.840> hasn't<14:20:07.500> gotten<14:20:07.800> infected 14:20:09.230 --> 14:20:09.240 align:start position:0% York hasn't gotten infected 14:20:09.240 --> 14:20:11.746 align:start position:0% York hasn't gotten infected so<14:20:09.900> in<14:20:10.380> this<14:20:10.500> module<14:20:10.860> I<14:20:11.096> really<14:20:11.220> briefly 14:20:11.746 --> 14:20:11.756 align:start position:0% so in this module I really briefly 14:20:11.756 --> 14:20:14.690 align:start position:0% so in this module I really briefly talked<14:20:12.180> about<14:20:12.300> a<14:20:12.596> Wan<14:20:12.956> or<14:20:13.500> a<14:20:13.916> wide<14:20:14.276> area 14:20:14.690 --> 14:20:14.700 align:start position:0% talked about a Wan or a wide area 14:20:14.700 --> 14:20:15.946 align:start position:0% talked about a Wan or a wide area network 14:20:15.946 --> 14:20:15.956 align:start position:0% network 14:20:15.956 --> 14:20:19.850 align:start position:0% network remember<14:20:16.500> a<14:20:16.916> Wan<14:20:17.220> is<14:20:18.000> comprised<14:20:18.840> of<14:20:19.256> several 14:20:19.850 --> 14:20:19.860 align:start position:0% remember a Wan is comprised of several 14:20:19.860 --> 14:20:22.370 align:start position:0% remember a Wan is comprised of several lands<14:20:20.456> that<14:20:21.116> are<14:20:21.240> connected 14:20:22.370 --> 14:20:22.380 align:start position:0% lands that are connected 14:20:22.380 --> 14:20:24.586 align:start position:0% lands that are connected over<14:20:22.916> a<14:20:23.160> geographic<14:20:23.756> area 14:20:24.586 --> 14:20:24.596 align:start position:0% over a geographic area 14:20:24.596 --> 14:20:27.350 align:start position:0% over a geographic area in<14:20:25.080> some<14:20:25.200> cases<14:20:25.680> we're<14:20:26.580> going<14:20:26.880> to<14:20:27.180> connect 14:20:27.350 --> 14:20:27.360 align:start position:0% in some cases we're going to connect 14:20:27.360 --> 14:20:30.890 align:start position:0% in some cases we're going to connect them<14:20:27.776> through<14:20:28.436> the<14:20:28.740> use<14:20:28.916> of<14:20:29.580> what's<14:20:29.700> called<14:20:30.060> a 14:20:30.890 --> 14:20:30.900 align:start position:0% them through the use of what's called a 14:20:30.900 --> 14:20:31.970 align:start position:0% them through the use of what's called a VPN 14:20:31.970 --> 14:20:31.980 align:start position:0% VPN 14:20:31.980 --> 14:20:35.210 align:start position:0% VPN well<14:20:32.340> we<14:20:32.520> have<14:20:32.640> a<14:20:32.820> VPN<14:20:33.300> or<14:20:33.720> a<14:20:34.020> virtual<14:20:34.616> private 14:20:35.210 --> 14:20:35.220 align:start position:0% well we have a VPN or a virtual private 14:20:35.220 --> 14:20:38.446 align:start position:0% well we have a VPN or a virtual private Network<14:20:35.456> it<14:20:36.416> creates<14:20:36.720> a<14:20:37.080> tunnel<14:20:37.436> over<14:20:38.096> the 14:20:38.446 --> 14:20:38.456 align:start position:0% Network it creates a tunnel over the 14:20:38.456 --> 14:20:40.730 align:start position:0% Network it creates a tunnel over the Internet<14:20:38.640> which<14:20:39.240> is<14:20:39.360> our<14:20:39.660> public<14:20:40.140> switched 14:20:40.730 --> 14:20:40.740 align:start position:0% Internet which is our public switched 14:20:40.740 --> 14:20:43.906 align:start position:0% Internet which is our public switched Network<14:20:40.916> or<14:20:41.340> our<14:20:41.580> public<14:20:41.756> network<14:20:42.616> and<14:20:43.616> we 14:20:43.906 --> 14:20:43.916 align:start position:0% Network or our public network and we 14:20:43.916 --> 14:20:45.650 align:start position:0% Network or our public network and we create<14:20:44.096> a<14:20:44.456> private<14:20:44.820> Network<14:20:45.000> within<14:20:45.480> that 14:20:45.650 --> 14:20:45.660 align:start position:0% create a private Network within that 14:20:45.660 --> 14:20:47.210 align:start position:0% create a private Network within that using<14:20:46.080> all<14:20:46.200> sorts<14:20:46.500> of<14:20:46.560> protocols<14:20:47.040> we'll 14:20:47.210 --> 14:20:47.220 align:start position:0% using all sorts of protocols we'll 14:20:47.220 --> 14:20:49.730 align:start position:0% using all sorts of protocols we'll discuss<14:20:47.640> so<14:20:48.300> that<14:20:48.416> way<14:20:48.596> these<14:20:49.140> two<14:20:49.200> lands<14:20:49.616> can 14:20:49.730 --> 14:20:49.740 align:start position:0% discuss so that way these two lands can 14:20:49.740 --> 14:20:51.650 align:start position:0% discuss so that way these two lands can communicate<14:20:50.220> as<14:20:50.456> though<14:20:50.640> they<14:20:51.116> are<14:20:51.300> actually 14:20:51.650 --> 14:20:51.660 align:start position:0% communicate as though they are actually 14:20:51.660 --> 14:20:53.870 align:start position:0% communicate as though they are actually one<14:20:52.256> Lan<14:20:52.680> or<14:20:53.040> they're<14:20:53.220> right<14:20:53.400> next<14:20:53.580> to<14:20:53.756> each 14:20:53.870 --> 14:20:53.880 align:start position:0% one Lan or they're right next to each 14:20:53.880 --> 14:20:56.510 align:start position:0% one Lan or they're right next to each other<14:20:54.060> we<14:20:54.840> also<14:20:55.020> need<14:20:55.200> to<14:20:55.320> have<14:20:55.500> user<14:20:56.040> accounts 14:20:56.510 --> 14:20:56.520 align:start position:0% other we also need to have user accounts 14:20:56.520 --> 14:20:59.870 align:start position:0% other we also need to have user accounts so<14:20:57.116> that<14:20:57.416> way<14:20:57.800> the<14:20:58.800> users 14:20:59.870 --> 14:20:59.880 align:start position:0% so that way the users 14:20:59.880 --> 14:21:02.266 align:start position:0% so that way the users can't<14:21:00.540> just<14:21:00.776> not<14:21:01.256> anyone<14:21:01.616> can<14:21:01.800> get<14:21:01.980> onto<14:21:02.220> a 14:21:02.266 --> 14:21:02.276 align:start position:0% can't just not anyone can get onto a 14:21:02.276 --> 14:21:03.586 align:start position:0% can't just not anyone can get onto a network<14:21:02.400> they<14:21:02.756> have<14:21:02.880> to<14:21:03.000> have<14:21:03.180> a<14:21:03.360> specific 14:21:03.586 --> 14:21:03.596 align:start position:0% network they have to have a specific 14:21:03.596 --> 14:21:05.990 align:start position:0% network they have to have a specific password<14:21:04.020> authentication<14:21:05.096> Etc<14:21:05.276> and<14:21:05.880> those 14:21:05.990 --> 14:21:06.000 align:start position:0% password authentication Etc and those 14:21:06.000 --> 14:21:09.290 align:start position:0% password authentication Etc and those users<14:21:06.360> also<14:21:06.660> have<14:21:06.840> to<14:21:07.020> have<14:21:07.256> access<14:21:08.300> somehow 14:21:09.290 --> 14:21:09.300 align:start position:0% users also have to have access somehow 14:21:09.300 --> 14:21:11.870 align:start position:0% users also have to have access somehow whether<14:21:09.900> that's<14:21:10.140> through<14:21:10.380> the<14:21:10.560> internet<14:21:10.880> or 14:21:11.870 --> 14:21:11.880 align:start position:0% whether that's through the internet or 14:21:11.880 --> 14:21:13.426 align:start position:0% whether that's through the internet or they<14:21:12.360> actually<14:21:12.540> are<14:21:12.720> physically<14:21:13.020> connected 14:21:13.426 --> 14:21:13.436 align:start position:0% they actually are physically connected 14:21:13.436 --> 14:21:15.170 align:start position:0% they actually are physically connected through<14:21:13.740> our<14:21:13.980> land<14:21:14.160> site 14:21:15.170 --> 14:21:15.180 align:start position:0% through our land site 14:21:15.180 --> 14:21:16.426 align:start position:0% through our land site we<14:21:15.540> also<14:21:15.720> talked<14:21:15.956> about<14:21:16.020> some<14:21:16.256> of<14:21:16.380> the 14:21:16.426 --> 14:21:16.436 align:start position:0% we also talked about some of the 14:21:16.436 --> 14:21:17.746 align:start position:0% we also talked about some of the administrative<14:21:16.800> tasks<14:21:17.276> that<14:21:17.456> can<14:21:17.640> be 14:21:17.746 --> 14:21:17.756 align:start position:0% administrative tasks that can be 14:21:17.756 --> 14:21:20.390 align:start position:0% administrative tasks that can be difficult<14:21:18.060> for<14:21:18.300> lands<14:21:18.776> specifically<14:21:19.560> backup 14:21:20.390 --> 14:21:20.400 align:start position:0% difficult for lands specifically backup 14:21:20.400 --> 14:21:23.030 align:start position:0% difficult for lands specifically backup where<14:21:20.936> we're<14:21:21.116> dealing<14:21:21.416> not<14:21:21.660> only<14:21:21.840> with<14:21:22.320> speed 14:21:23.030 --> 14:21:23.040 align:start position:0% where we're dealing not only with speed 14:21:23.040 --> 14:21:26.810 align:start position:0% where we're dealing not only with speed but<14:21:23.936> also<14:21:24.180> with<14:21:24.480> amount<14:21:24.900> of<14:21:25.020> data 14:21:26.810 --> 14:21:26.820 align:start position:0% but also with amount of data 14:21:26.820 --> 14:21:29.810 align:start position:0% but also with amount of data and<14:21:27.660> we<14:21:27.900> talked<14:21:28.140> about<14:21:28.200> security<14:21:28.680> we're<14:21:29.580> not 14:21:29.810 --> 14:21:29.820 align:start position:0% and we talked about security we're not 14:21:29.820 --> 14:21:32.870 align:start position:0% and we talked about security we're not just<14:21:30.140> stopping<14:21:31.140> intrusions 14:21:32.870 --> 14:21:32.880 align:start position:0% just stopping intrusions 14:21:32.880 --> 14:21:37.010 align:start position:0% just stopping intrusions but<14:21:33.360> we<14:21:33.660> also<14:21:34.020> need<14:21:34.916> to<14:21:35.220> limit<14:21:35.580> the<14:21:36.360> spread<14:21:36.776> of 14:21:37.010 --> 14:21:37.020 align:start position:0% but we also need to limit the spread of 14:21:37.020 --> 14:21:42.020 align:start position:0% but we also need to limit the spread of an<14:21:37.200> attack 14:21:42.020 --> 14:21:42.030 align:start position:0% 14:21:42.030 --> 14:22:02.106 align:start position:0% [Music] 14:22:02.106 --> 14:22:02.116 align:start position:0% 14:22:02.116 --> 14:22:05.390 align:start position:0% wide<14:22:03.116> area<14:22:03.300> networks<14:22:04.020> Wan<14:22:04.980> transmission 14:22:05.390 --> 14:22:05.400 align:start position:0% wide area networks Wan transmission 14:22:05.400 --> 14:22:07.246 align:start position:0% wide area networks Wan transmission technologies 14:22:07.246 --> 14:22:07.256 align:start position:0% technologies 14:22:07.256 --> 14:22:11.570 align:start position:0% technologies so<14:22:07.800> in<14:22:07.980> the<14:22:08.220> last<14:22:08.340> module<14:22:09.000> we<14:22:09.416> talked<14:22:09.916> very<14:22:10.916> uh 14:22:11.570 --> 14:22:11.580 align:start position:0% so in the last module we talked very uh 14:22:11.580 --> 14:22:14.870 align:start position:0% so in the last module we talked very uh briefly<14:22:12.300> and<14:22:13.256> in<14:22:13.680> an<14:22:13.916> overview<14:22:14.220> sense<14:22:14.580> about 14:22:14.870 --> 14:22:14.880 align:start position:0% briefly and in an overview sense about 14:22:14.880 --> 14:22:17.330 align:start position:0% briefly and in an overview sense about the<14:22:15.116> implementation<14:22:15.660> and<14:22:15.956> administration<14:22:16.680> of 14:22:17.330 --> 14:22:17.340 align:start position:0% the implementation and administration of 14:22:17.340 --> 14:22:19.310 align:start position:0% the implementation and administration of wide<14:22:17.580> area<14:22:17.756> networks<14:22:18.360> now<14:22:18.840> the<14:22:18.956> reason<14:22:19.080> we 14:22:19.310 --> 14:22:19.320 align:start position:0% wide area networks now the reason we 14:22:19.320 --> 14:22:21.050 align:start position:0% wide area networks now the reason we didn't<14:22:19.436> get<14:22:19.560> into<14:22:19.680> too<14:22:19.980> much<14:22:20.160> detail<14:22:20.640> is 14:22:21.050 --> 14:22:21.060 align:start position:0% didn't get into too much detail is 14:22:21.060 --> 14:22:23.990 align:start position:0% didn't get into too much detail is because<14:22:21.300> it<14:22:22.256> gets<14:22:22.800> quite<14:22:23.096> complicated<14:22:23.700> when 14:22:23.990 --> 14:22:24.000 align:start position:0% because it gets quite complicated when 14:22:24.000 --> 14:22:25.730 align:start position:0% because it gets quite complicated when we<14:22:24.180> talk<14:22:24.416> not<14:22:24.720> only<14:22:24.900> about<14:22:25.080> connecting 14:22:25.730 --> 14:22:25.740 align:start position:0% we talk not only about connecting 14:22:25.740 --> 14:22:27.230 align:start position:0% we talk not only about connecting computers<14:22:26.220> together<14:22:26.456> in<14:22:26.756> a<14:22:26.880> local<14:22:27.000> area 14:22:27.230 --> 14:22:27.240 align:start position:0% computers together in a local area 14:22:27.240 --> 14:22:29.926 align:start position:0% computers together in a local area network<14:22:27.540> but<14:22:28.256> in<14:22:28.560> a<14:22:28.740> wide<14:22:28.860> area<14:22:29.096> network<14:22:29.400> and 14:22:29.926 --> 14:22:29.936 align:start position:0% network but in a wide area network and 14:22:29.936 --> 14:22:32.690 align:start position:0% network but in a wide area network and as<14:22:30.180> a<14:22:30.360> result<14:22:30.480> the<14:22:30.900> Technologies<14:22:31.500> become<14:22:32.220> more 14:22:32.690 --> 14:22:32.700 align:start position:0% as a result the Technologies become more 14:22:32.700 --> 14:22:35.266 align:start position:0% as a result the Technologies become more and<14:22:32.820> more<14:22:33.060> complex<14:22:33.416> and<14:22:34.380> just<14:22:34.860> like<14:22:34.980> we<14:22:35.160> have 14:22:35.266 --> 14:22:35.276 align:start position:0% and more complex and just like we have 14:22:35.276 --> 14:22:36.710 align:start position:0% and more complex and just like we have people<14:22:35.520> who<14:22:35.756> specialize<14:22:36.116> in<14:22:36.300> lands<14:22:36.596> they're 14:22:36.710 --> 14:22:36.720 align:start position:0% people who specialize in lands they're 14:22:36.720 --> 14:22:38.990 align:start position:0% people who specialize in lands they're people<14:22:36.956> who<14:22:37.140> specialize<14:22:37.500> in<14:22:37.616> lands<14:22:38.160> since<14:22:38.756> the 14:22:38.990 --> 14:22:39.000 align:start position:0% people who specialize in lands since the 14:22:39.000 --> 14:22:40.490 align:start position:0% people who specialize in lands since the purpose<14:22:39.300> of<14:22:39.480> network<14:22:39.660> plus<14:22:39.956> is<14:22:40.200> to<14:22:40.320> give<14:22:40.436> you 14:22:40.490 --> 14:22:40.500 align:start position:0% purpose of network plus is to give you 14:22:40.500 --> 14:22:42.350 align:start position:0% purpose of network plus is to give you an<14:22:40.616> overview<14:22:40.860> of<14:22:41.040> all<14:22:41.276> the<14:22:41.456> stuff<14:22:41.640> we<14:22:42.180> just 14:22:42.350 --> 14:22:42.360 align:start position:0% an overview of all the stuff we just 14:22:42.360 --> 14:22:43.850 align:start position:0% an overview of all the stuff we just want<14:22:42.480> to<14:22:42.596> get<14:22:42.720> you<14:22:42.900> familiar<14:22:43.380> with<14:22:43.560> certain 14:22:43.850 --> 14:22:43.860 align:start position:0% want to get you familiar with certain 14:22:43.860 --> 14:22:46.426 align:start position:0% want to get you familiar with certain terms<14:22:44.340> so<14:22:45.000> in<14:22:45.180> case<14:22:45.360> you<14:22:45.596> were<14:22:45.776> to<14:22:45.900> come<14:22:46.020> across 14:22:46.426 --> 14:22:46.436 align:start position:0% terms so in case you were to come across 14:22:46.436 --> 14:22:48.766 align:start position:0% terms so in case you were to come across them<14:22:46.616> you<14:22:47.040> would<14:22:47.160> sort<14:22:47.340> of<14:22:47.520> know<14:22:47.756> where<14:22:48.540> to 14:22:48.766 --> 14:22:48.776 align:start position:0% them you would sort of know where to 14:22:48.776 --> 14:22:51.106 align:start position:0% them you would sort of know where to look<14:22:48.956> or<14:22:49.380> what<14:22:49.980> to<14:22:50.160> start<14:22:50.340> with<14:22:50.580> when<14:22:50.880> you<14:22:51.000> look 14:22:51.106 --> 14:22:51.116 align:start position:0% look or what to start with when you look 14:22:51.116 --> 14:22:53.510 align:start position:0% look or what to start with when you look for<14:22:51.240> more<14:22:51.480> information<14:22:51.740> now<14:22:52.740> in<14:22:53.096> this<14:22:53.220> module 14:22:53.510 --> 14:22:53.520 align:start position:0% for more information now in this module 14:22:53.520 --> 14:22:54.406 align:start position:0% for more information now in this module we're<14:22:53.700> going<14:22:53.820> to<14:22:53.880> talk<14:22:54.000> a<14:22:54.180> little<14:22:54.300> more 14:22:54.406 --> 14:22:54.416 align:start position:0% we're going to talk a little more 14:22:54.416 --> 14:22:56.510 align:start position:0% we're going to talk a little more specifically<14:22:54.956> about<14:22:55.380> Wan<14:22:56.160> transmission 14:22:56.510 --> 14:22:56.520 align:start position:0% specifically about Wan transmission 14:22:56.520 --> 14:22:58.790 align:start position:0% specifically about Wan transmission techniques<14:22:57.416> again<14:22:58.080> we're<14:22:58.320> going<14:22:58.500> to<14:22:58.560> look<14:22:58.680> at 14:22:58.790 --> 14:22:58.800 align:start position:0% techniques again we're going to look at 14:22:58.800 --> 14:23:01.370 align:start position:0% techniques again we're going to look at this<14:22:58.980> from<14:22:59.220> a<14:22:59.340> mile<14:22:59.520> high<14:22:59.880> view<14:23:00.116> so<14:23:00.900> the 14:23:01.370 --> 14:23:01.380 align:start position:0% this from a mile high view so the 14:23:01.380 --> 14:23:02.746 align:start position:0% this from a mile high view so the techniques<14:23:02.040> then<14:23:02.220> the<14:23:02.520> transmission 14:23:02.746 --> 14:23:02.756 align:start position:0% techniques then the transmission 14:23:02.756 --> 14:23:04.490 align:start position:0% techniques then the transmission technologies<14:23:03.596> we're<14:23:03.900> going<14:23:04.020> to<14:23:04.140> talk<14:23:04.320> about 14:23:04.490 --> 14:23:04.500 align:start position:0% technologies we're going to talk about 14:23:04.500 --> 14:23:07.190 align:start position:0% technologies we're going to talk about are<14:23:04.800> specifically<14:23:05.540> ISDN<14:23:06.540> which<14:23:06.900> you<14:23:06.956> might 14:23:07.190 --> 14:23:07.200 align:start position:0% are specifically ISDN which you might 14:23:07.200 --> 14:23:08.810 align:start position:0% are specifically ISDN which you might remember<14:23:07.616> if<14:23:07.916> you've<14:23:08.096> been<14:23:08.220> around<14:23:08.400> for<14:23:08.756> a 14:23:08.810 --> 14:23:08.820 align:start position:0% remember if you've been around for a 14:23:08.820 --> 14:23:11.810 align:start position:0% remember if you've been around for a while<14:23:08.880> it's<14:23:09.180> mostly<14:23:09.596> been<14:23:09.916> supplanted<14:23:10.916> by<14:23:11.220> DSL 14:23:11.810 --> 14:23:11.820 align:start position:0% while it's mostly been supplanted by DSL 14:23:11.820 --> 14:23:15.710 align:start position:0% while it's mostly been supplanted by DSL and<14:23:12.660> cable<14:23:13.080> to<14:23:13.500> this<14:23:13.800> uh<14:23:14.400> nowadays<14:23:15.240> as 14:23:15.710 --> 14:23:15.720 align:start position:0% and cable to this uh nowadays as 14:23:15.720 --> 14:23:17.570 align:start position:0% and cable to this uh nowadays as actually<14:23:16.080> you<14:23:16.320> have<14:23:16.560> most<14:23:16.980> of<14:23:17.220> these 14:23:17.570 --> 14:23:17.580 align:start position:0% actually you have most of these 14:23:17.580 --> 14:23:19.190 align:start position:0% actually you have most of these Technologies<14:23:18.116> but<14:23:18.596> some<14:23:18.660> of<14:23:18.776> these<14:23:18.900> are<14:23:19.020> still 14:23:19.190 --> 14:23:19.200 align:start position:0% Technologies but some of these are still 14:23:19.200 --> 14:23:20.330 align:start position:0% Technologies but some of these are still around<14:23:19.320> and<14:23:19.560> you<14:23:19.740> probably<14:23:19.860> have<14:23:20.040> heard<14:23:20.220> of 14:23:20.330 --> 14:23:20.340 align:start position:0% around and you probably have heard of 14:23:20.340 --> 14:23:22.070 align:start position:0% around and you probably have heard of them<14:23:20.520> so<14:23:20.820> ISDN<14:23:21.360> is<14:23:21.480> the<14:23:21.596> first<14:23:21.720> we're<14:23:21.900> going<14:23:22.020> to 14:23:22.070 --> 14:23:22.080 align:start position:0% them so ISDN is the first we're going to 14:23:22.080 --> 14:23:23.570 align:start position:0% them so ISDN is the first we're going to talk<14:23:22.200> about<14:23:22.380> we're<14:23:22.860> also<14:23:23.096> going<14:23:23.220> to<14:23:23.276> talk 14:23:23.570 --> 14:23:23.580 align:start position:0% talk about we're also going to talk 14:23:23.580 --> 14:23:25.426 align:start position:0% talk about we're also going to talk about<14:23:23.700> t<14:23:24.060> carrier<14:23:24.540> and<14:23:24.660> if<14:23:24.776> you've<14:23:24.956> ever<14:23:25.080> seen 14:23:25.426 --> 14:23:25.436 align:start position:0% about t carrier and if you've ever seen 14:23:25.436 --> 14:23:28.730 align:start position:0% about t carrier and if you've ever seen the<14:23:25.980> term<14:23:26.096> a<14:23:26.640> T1<14:23:27.060> or<14:23:27.480> T3<14:23:27.956> line<14:23:28.256> that's<14:23:28.500> what 14:23:28.730 --> 14:23:28.740 align:start position:0% the term a T1 or T3 line that's what 14:23:28.740 --> 14:23:30.586 align:start position:0% the term a T1 or T3 line that's what this<14:23:28.860> is<14:23:29.040> referring<14:23:29.400> to<14:23:29.640> we're<14:23:30.300> going<14:23:30.416> to<14:23:30.540> talk 14:23:30.586 --> 14:23:30.596 align:start position:0% this is referring to we're going to talk 14:23:30.596 --> 14:23:33.830 align:start position:0% this is referring to we're going to talk about<14:23:30.720> Sonet<14:23:31.320> which<14:23:31.860> is<14:23:32.580> responsible<14:23:33.240> for<14:23:33.660> a 14:23:33.830 --> 14:23:33.840 align:start position:0% about Sonet which is responsible for a 14:23:33.840 --> 14:23:36.290 align:start position:0% about Sonet which is responsible for a different<14:23:33.956> type<14:23:34.380> of<14:23:34.680> classification<14:23:35.400> it's 14:23:36.290 --> 14:23:36.300 align:start position:0% different type of classification it's 14:23:36.300 --> 14:23:38.690 align:start position:0% different type of classification it's also<14:23:36.596> using<14:23:36.840> some<14:23:37.080> Optics<14:23:37.560> which<14:23:38.096> is<14:23:38.220> why<14:23:38.456> it's 14:23:38.690 --> 14:23:38.700 align:start position:0% also using some Optics which is why it's 14:23:38.700 --> 14:23:40.970 align:start position:0% also using some Optics which is why it's a<14:23:38.936> bit<14:23:39.416> faster<14:23:39.776> and<14:23:40.020> required<14:23:40.500> a<14:23:40.680> completely 14:23:40.970 --> 14:23:40.980 align:start position:0% a bit faster and required a completely 14:23:40.980 --> 14:23:44.746 align:start position:0% a bit faster and required a completely different<14:23:41.220> form<14:23:41.756> of<14:23:42.300> rating<14:23:43.080> the<14:23:43.860> cabling<14:23:44.276> and 14:23:44.746 --> 14:23:44.756 align:start position:0% different form of rating the cabling and 14:23:44.756 --> 14:23:46.550 align:start position:0% different form of rating the cabling and the<14:23:44.936> speeds<14:23:45.300> and<14:23:46.080> then<14:23:46.140> we're<14:23:46.256> going<14:23:46.380> to<14:23:46.436> look 14:23:46.550 --> 14:23:46.560 align:start position:0% the speeds and then we're going to look 14:23:46.560 --> 14:23:48.766 align:start position:0% the speeds and then we're going to look at<14:23:46.740> some<14:23:47.040> technologies<14:23:47.580> that<14:23:47.936> allow<14:23:48.240> the<14:23:48.416> data 14:23:48.766 --> 14:23:48.776 align:start position:0% at some technologies that allow the data 14:23:48.776 --> 14:23:52.790 align:start position:0% at some technologies that allow the data to<14:23:49.400> transmit<14:23:50.400> over<14:23:50.756> this<14:23:51.596> stuff<14:23:52.256> these<14:23:52.680> T 14:23:52.790 --> 14:23:52.800 align:start position:0% to transmit over this stuff these T 14:23:52.800 --> 14:23:55.790 align:start position:0% to transmit over this stuff these T carrier<14:23:53.220> and<14:23:53.276> sonets<14:23:53.776> including<14:23:54.776> x25<14:23:55.560> and 14:23:55.790 --> 14:23:55.800 align:start position:0% carrier and sonets including x25 and 14:23:55.800 --> 14:23:59.210 align:start position:0% carrier and sonets including x25 and frame<14:23:56.160> relay<14:23:56.660> x25<14:23:57.660> was<14:23:58.020> supplanted<14:23:58.616> by<14:23:58.860> frame 14:23:59.210 --> 14:23:59.220 align:start position:0% frame relay x25 was supplanted by frame 14:23:59.220 --> 14:24:02.030 align:start position:0% frame relay x25 was supplanted by frame relay<14:23:59.520> and<14:24:00.240> ATM<14:24:00.776> which<14:24:01.020> is<14:24:01.140> not<14:24:01.380> the<14:24:01.616> thing<14:24:01.740> you 14:24:02.030 --> 14:24:02.040 align:start position:0% relay and ATM which is not the thing you 14:24:02.040 --> 14:24:04.310 align:start position:0% relay and ATM which is not the thing you put<14:24:02.220> your<14:24:02.700> card<14:24:03.180> into<14:24:03.360> to<14:24:03.660> get<14:24:03.776> money<14:24:03.956> out<14:24:04.200> of 14:24:04.310 --> 14:24:04.320 align:start position:0% put your card into to get money out of 14:24:04.320 --> 14:24:06.830 align:start position:0% put your card into to get money out of but<14:24:04.680> rather<14:24:04.980> a<14:24:05.276> technology<14:24:05.640> of<14:24:06.180> protocol<14:24:06.540> that 14:24:06.830 --> 14:24:06.840 align:start position:0% but rather a technology of protocol that 14:24:06.840 --> 14:24:08.926 align:start position:0% but rather a technology of protocol that allows<14:24:07.020> us<14:24:07.200> to<14:24:07.800> communicate<14:24:08.400> over<14:24:08.580> when 14:24:08.926 --> 14:24:08.936 align:start position:0% allows us to communicate over when 14:24:08.936 --> 14:24:10.310 align:start position:0% allows us to communicate over when Networks 14:24:10.310 --> 14:24:10.320 align:start position:0% Networks 14:24:10.320 --> 14:24:11.446 align:start position:0% Networks so<14:24:10.680> the<14:24:10.800> first<14:24:10.916> one<14:24:11.040> we're<14:24:11.160> going<14:24:11.276> to<14:24:11.340> talk 14:24:11.446 --> 14:24:11.456 align:start position:0% so the first one we're going to talk 14:24:11.456 --> 14:24:13.730 align:start position:0% so the first one we're going to talk about<14:24:11.640> here<14:24:11.936> is<14:24:12.300> the<14:24:12.660> integrated<14:24:13.140> Services 14:24:13.730 --> 14:24:13.740 align:start position:0% about here is the integrated Services 14:24:13.740 --> 14:24:16.690 align:start position:0% about here is the integrated Services digital<14:24:14.276> Network<14:24:14.520> or 14:24:16.690 --> 14:24:16.700 align:start position:0% digital Network or 14:24:16.700 --> 14:24:21.470 align:start position:0% digital Network or ISDN<14:24:17.700> now<14:24:18.660> uh<14:24:19.140> the<14:24:19.800> ISDN<14:24:20.276> is<14:24:20.520> very<14:24:21.000> high<14:24:21.240> speed 14:24:21.470 --> 14:24:21.480 align:start position:0% ISDN now uh the ISDN is very high speed 14:24:21.480 --> 14:24:24.406 align:start position:0% ISDN now uh the ISDN is very high speed but<14:24:21.840> it's<14:24:22.020> also<14:24:22.380> high<14:24:22.740> cost<14:24:23.040> and<14:24:24.000> the<14:24:24.240> reason 14:24:24.406 --> 14:24:24.416 align:start position:0% but it's also high cost and the reason 14:24:24.416 --> 14:24:26.870 align:start position:0% but it's also high cost and the reason for<14:24:24.720> that<14:24:24.840> is<14:24:25.080> because<14:24:25.256> in<14:24:25.500> order<14:24:25.680> to<14:24:25.916> use<14:24:26.160> ISDN 14:24:26.870 --> 14:24:26.880 align:start position:0% for that is because in order to use ISDN 14:24:26.880 --> 14:24:29.030 align:start position:0% for that is because in order to use ISDN a<14:24:27.180> special<14:24:27.360> phone<14:24:27.776> line<14:24:28.020> is<14:24:28.256> required<14:24:28.680> to<14:24:28.800> set 14:24:29.030 --> 14:24:29.040 align:start position:0% a special phone line is required to set 14:24:29.040 --> 14:24:31.730 align:start position:0% a special phone line is required to set it<14:24:29.220> up<14:24:29.400> now<14:24:30.180> the<14:24:30.480> line<14:24:30.660> is<14:24:30.840> paid<14:24:31.080> for<14:24:31.320> monthly 14:24:31.730 --> 14:24:31.740 align:start position:0% it up now the line is paid for monthly 14:24:31.740 --> 14:24:34.190 align:start position:0% it up now the line is paid for monthly just<14:24:32.040> like<14:24:32.220> with<14:24:32.640> any<14:24:32.880> phone<14:24:33.180> line<14:24:33.416> and<14:24:34.020> this 14:24:34.190 --> 14:24:34.200 align:start position:0% just like with any phone line and this 14:24:34.200 --> 14:24:36.170 align:start position:0% just like with any phone line and this is<14:24:34.256> where<14:24:34.500> the<14:24:34.740> high<14:24:35.040> costs<14:24:35.520> come<14:24:35.756> in<14:24:35.936> because 14:24:36.170 --> 14:24:36.180 align:start position:0% is where the high costs come in because 14:24:36.180 --> 14:24:38.030 align:start position:0% is where the high costs come in because the<14:24:36.480> service<14:24:36.720> is<14:24:37.080> pretty<14:24:37.256> expensive<14:24:37.740> to<14:24:37.916> pay 14:24:38.030 --> 14:24:38.040 align:start position:0% the service is pretty expensive to pay 14:24:38.040 --> 14:24:40.606 align:start position:0% the service is pretty expensive to pay for<14:24:38.220> every<14:24:38.400> month<14:24:39.116> in<14:24:39.596> order<14:24:39.840> to<14:24:40.080> set<14:24:40.256> up<14:24:40.380> a 14:24:40.606 --> 14:24:40.616 align:start position:0% for every month in order to set up a 14:24:40.616 --> 14:24:43.130 align:start position:0% for every month in order to set up a connection<14:24:40.740> the<14:24:41.456> phone<14:24:41.580> line<14:24:41.820> has<14:24:42.300> to<14:24:42.776> dial 14:24:43.130 --> 14:24:43.140 align:start position:0% connection the phone line has to dial 14:24:43.140 --> 14:24:44.510 align:start position:0% connection the phone line has to dial the<14:24:43.380> address<14:24:43.560> of<14:24:43.800> the<14:24:43.980> receiving<14:24:44.160> computer 14:24:44.510 --> 14:24:44.520 align:start position:0% the address of the receiving computer 14:24:44.520 --> 14:24:47.330 align:start position:0% the address of the receiving computer very<14:24:45.360> similar<14:24:45.720> to<14:24:45.900> the<14:24:46.080> process<14:24:46.436> of<14:24:46.680> calling<14:24:47.096> a 14:24:47.330 --> 14:24:47.340 align:start position:0% very similar to the process of calling a 14:24:47.340 --> 14:24:49.246 align:start position:0% very similar to the process of calling a phone<14:24:47.520> on<14:24:48.060> the<14:24:48.180> other<14:24:48.240> end<14:24:48.416> and<14:24:48.900> once<14:24:49.140> the 14:24:49.246 --> 14:24:49.256 align:start position:0% phone on the other end and once the 14:24:49.256 --> 14:24:50.630 align:start position:0% phone on the other end and once the connection<14:24:49.436> is<14:24:49.740> established<14:24:50.220> you<14:24:50.400> can<14:24:50.520> drop 14:24:50.630 --> 14:24:50.640 align:start position:0% connection is established you can drop 14:24:50.640 --> 14:24:53.810 align:start position:0% connection is established you can drop it<14:24:50.880> by<14:24:51.060> just<14:24:51.240> hanging<14:24:51.660> it<14:24:51.776> up<14:24:51.956> so<14:24:52.860> if<14:24:53.520> we<14:24:53.700> were 14:24:53.810 --> 14:24:53.820 align:start position:0% it by just hanging it up so if we were 14:24:53.820 --> 14:24:57.406 align:start position:0% it by just hanging it up so if we were to<14:24:53.936> consider<14:24:54.416> this<14:24:54.776> for<14:24:55.080> instance<14:24:55.380> to<14:24:55.740> be<14:24:55.980> our 14:24:57.406 --> 14:24:57.416 align:start position:0% to consider this for instance to be our 14:24:57.416 --> 14:25:00.710 align:start position:0% to consider this for instance to be our um<14:24:57.480> uh<14:24:58.640> ISDN<14:24:59.640> line<14:24:59.820> you<14:25:00.060> would<14:25:00.180> notice<14:25:00.416> there 14:25:00.710 --> 14:25:00.720 align:start position:0% um uh ISDN line you would notice there 14:25:00.720 --> 14:25:02.810 align:start position:0% um uh ISDN line you would notice there is<14:25:00.900> sort<14:25:01.140> of<14:25:01.200> a<14:25:01.436> box<14:25:02.096> here<14:25:02.340> and<14:25:02.520> that's<14:25:02.640> because 14:25:02.810 --> 14:25:02.820 align:start position:0% is sort of a box here and that's because 14:25:02.820 --> 14:25:05.030 align:start position:0% is sort of a box here and that's because we<14:25:03.060> need<14:25:03.180> a<14:25:03.360> special<14:25:03.480> box<14:25:03.776> to<14:25:04.080> allow<14:25:04.380> the<14:25:04.500> istn 14:25:05.030 --> 14:25:05.040 align:start position:0% we need a special box to allow the istn 14:25:05.040 --> 14:25:06.470 align:start position:0% we need a special box to allow the istn to<14:25:05.220> communicate<14:25:05.640> and<14:25:06.060> it<14:25:06.180> would<14:25:06.360> then 14:25:06.470 --> 14:25:06.480 align:start position:0% to communicate and it would then 14:25:06.480 --> 14:25:08.746 align:start position:0% to communicate and it would then communicate<14:25:07.140> onto<14:25:07.980> the<14:25:08.096> other<14:25:08.220> side<14:25:08.400> to<14:25:08.640> the 14:25:08.746 --> 14:25:08.756 align:start position:0% communicate onto the other side to the 14:25:08.756 --> 14:25:11.030 align:start position:0% communicate onto the other side to the ISP<14:25:09.300> now<14:25:09.840> what's<14:25:10.020> interesting<14:25:10.380> here<14:25:10.616> is<14:25:10.800> this 14:25:11.030 --> 14:25:11.040 align:start position:0% ISP now what's interesting here is this 14:25:11.040 --> 14:25:13.246 align:start position:0% ISP now what's interesting here is this is<14:25:11.220> actually<14:25:11.456> a<14:25:12.000> plain<14:25:12.180> old<14:25:12.480> telephone<14:25:12.776> system 14:25:13.246 --> 14:25:13.256 align:start position:0% is actually a plain old telephone system 14:25:13.256 --> 14:25:16.790 align:start position:0% is actually a plain old telephone system line<14:25:13.640> or<14:25:14.640> uh<14:25:15.416> by<14:25:15.900> the<14:25:15.956> way<14:25:16.020> Plano<14:25:16.560> telephone 14:25:16.790 --> 14:25:16.800 align:start position:0% line or uh by the way Plano telephone 14:25:16.800 --> 14:25:19.490 align:start position:0% line or uh by the way Plano telephone system<14:25:17.580> or<14:25:18.000> pstn<14:25:18.660> public<14:25:18.900> switch<14:25:19.140> telephone 14:25:19.490 --> 14:25:19.500 align:start position:0% system or pstn public switch telephone 14:25:19.500 --> 14:25:22.970 align:start position:0% system or pstn public switch telephone Network<14:25:19.916> so<14:25:20.520> this<14:25:20.700> is<14:25:20.820> using<14:25:21.300> uh<14:25:21.956> old 14:25:22.970 --> 14:25:22.980 align:start position:0% Network so this is using uh old 14:25:22.980 --> 14:25:25.426 align:start position:0% Network so this is using uh old telephone<14:25:23.640> technology<14:25:24.480> but<14:25:24.900> the<14:25:25.200> difference 14:25:25.426 --> 14:25:25.436 align:start position:0% telephone technology but the difference 14:25:25.436 --> 14:25:27.106 align:start position:0% telephone technology but the difference is<14:25:25.740> instead<14:25:26.160> of<14:25:26.220> using<14:25:26.520> the<14:25:26.640> one<14:25:26.756> that's 14:25:27.106 --> 14:25:27.116 align:start position:0% is instead of using the one that's 14:25:27.116 --> 14:25:29.630 align:start position:0% is instead of using the one that's already<14:25:27.416> been<14:25:27.980> installed<14:25:28.980> into<14:25:29.096> your<14:25:29.340> home<14:25:29.456> or 14:25:29.630 --> 14:25:29.640 align:start position:0% already been installed into your home or 14:25:29.640 --> 14:25:31.426 align:start position:0% already been installed into your home or to<14:25:29.820> your<14:25:29.936> office<14:25:30.116> it's<14:25:30.416> actually<14:25:30.660> another<14:25:31.080> one 14:25:31.426 --> 14:25:31.436 align:start position:0% to your office it's actually another one 14:25:31.436 --> 14:25:33.050 align:start position:0% to your office it's actually another one that<14:25:31.680> has<14:25:31.800> to<14:25:31.980> be<14:25:32.096> laid<14:25:32.400> down<14:25:32.580> which<14:25:32.820> is<14:25:32.880> how 14:25:33.050 --> 14:25:33.060 align:start position:0% that has to be laid down which is how 14:25:33.060 --> 14:25:35.210 align:start position:0% that has to be laid down which is how it's<14:25:33.180> different<14:25:33.416> from<14:25:33.720> DSL<14:25:34.320> now<14:25:34.916> there<14:25:35.096> are 14:25:35.210 --> 14:25:35.220 align:start position:0% it's different from DSL now there are 14:25:35.220 --> 14:25:37.246 align:start position:0% it's different from DSL now there are actually<14:25:35.276> two<14:25:35.520> different<14:25:35.756> types<14:25:36.416> of<14:25:36.596> ISDN 14:25:37.246 --> 14:25:37.256 align:start position:0% actually two different types of ISDN 14:25:37.256 --> 14:25:39.530 align:start position:0% actually two different types of ISDN we've<14:25:38.160> talked<14:25:38.400> about<14:25:38.456> these<14:25:38.756> in<14:25:38.880> a<14:25:39.000> plus<14:25:39.180> as 14:25:39.530 --> 14:25:39.540 align:start position:0% we've talked about these in a plus as 14:25:39.540 --> 14:25:43.690 align:start position:0% we've talked about these in a plus as well<14:25:39.660> one<14:25:40.140> is<14:25:40.320> the<14:25:40.500> Bri<14:25:41.040> and<14:25:41.700> the<14:25:41.820> other<14:25:42.000> is<14:25:42.720> PRI 14:25:43.690 --> 14:25:43.700 align:start position:0% well one is the Bri and the other is PRI 14:25:43.700 --> 14:25:48.650 align:start position:0% well one is the Bri and the other is PRI Bri<14:25:44.700> by<14:25:44.936> the<14:25:45.060> way<14:25:45.116> stands<14:25:45.480> for<14:25:45.720> basic 14:25:48.650 --> 14:25:48.660 align:start position:0% 14:25:48.660 --> 14:25:52.010 align:start position:0% rate<14:25:49.320> interface<14:25:49.916> and<14:25:50.880> this<14:25:51.180> one<14:25:51.300> stands<14:25:51.720> for 14:25:52.010 --> 14:25:52.020 align:start position:0% rate interface and this one stands for 14:25:52.020 --> 14:25:55.970 align:start position:0% rate interface and this one stands for primary<14:25:52.916> rate<14:25:53.880> interface<14:25:54.480> primary<14:25:55.436> is<14:25:55.680> a<14:25:55.860> bit 14:25:55.970 --> 14:25:55.980 align:start position:0% primary rate interface primary is a bit 14:25:55.980 --> 14:25:57.406 align:start position:0% primary rate interface primary is a bit faster 14:25:57.406 --> 14:25:57.416 align:start position:0% faster 14:25:57.416 --> 14:25:58.790 align:start position:0% faster but<14:25:57.900> it's<14:25:58.020> also<14:25:58.256> a<14:25:58.436> little<14:25:58.500> bit<14:25:58.616> more 14:25:58.790 --> 14:25:58.800 align:start position:0% but it's also a little bit more 14:25:58.800 --> 14:26:01.426 align:start position:0% but it's also a little bit more expensive<14:25:59.276> now<14:26:00.116> there<14:26:00.360> are<14:26:00.480> certain<14:26:00.660> speeds 14:26:01.426 --> 14:26:01.436 align:start position:0% expensive now there are certain speeds 14:26:01.436 --> 14:26:04.010 align:start position:0% expensive now there are certain speeds these<14:26:01.740> operate<14:26:02.040> at<14:26:02.276> generally<14:26:02.756> 64<14:26:03.360> kilobits 14:26:04.010 --> 14:26:04.020 align:start position:0% these operate at generally 64 kilobits 14:26:04.020 --> 14:26:06.830 align:start position:0% these operate at generally 64 kilobits per<14:26:04.680> second<14:26:04.916> or<14:26:05.340> 128<14:26:05.880> kilobits<14:26:06.480> per<14:26:06.596> second 14:26:06.830 --> 14:26:06.840 align:start position:0% per second or 128 kilobits per second 14:26:06.840 --> 14:26:09.946 align:start position:0% per second or 128 kilobits per second again<14:26:07.740> that's<14:26:08.520> pretty<14:26:08.880> slow<14:26:09.180> when<14:26:09.480> we<14:26:09.660> compare 14:26:09.946 --> 14:26:09.956 align:start position:0% again that's pretty slow when we compare 14:26:09.956 --> 14:26:12.830 align:start position:0% again that's pretty slow when we compare it<14:26:10.080> to<14:26:10.256> modern<14:26:10.436> day<14:26:10.740> DSL<14:26:11.456> or<14:26:12.000> modern<14:26:12.180> day<14:26:12.480> cable 14:26:12.830 --> 14:26:12.840 align:start position:0% it to modern day DSL or modern day cable 14:26:12.840 --> 14:26:14.690 align:start position:0% it to modern day DSL or modern day cable Technologies<14:26:13.436> but<14:26:13.680> this<14:26:13.860> was<14:26:14.040> a<14:26:14.276> dedicated 14:26:14.690 --> 14:26:14.700 align:start position:0% Technologies but this was a dedicated 14:26:14.700 --> 14:26:18.830 align:start position:0% Technologies but this was a dedicated line<14:26:15.000> specifically<14:26:15.596> from<14:26:15.956> you<14:26:16.200> to<14:26:17.160> uh<14:26:17.756> the<14:26:18.360> ISP 14:26:18.830 --> 14:26:18.840 align:start position:0% line specifically from you to uh the ISP 14:26:18.840 --> 14:26:21.050 align:start position:0% line specifically from you to uh the ISP which<14:26:19.380> is<14:26:19.500> the<14:26:19.740> reason<14:26:19.860> why<14:26:20.340> even<14:26:20.756> though<14:26:20.936> it 14:26:21.050 --> 14:26:21.060 align:start position:0% which is the reason why even though it 14:26:21.060 --> 14:26:22.790 align:start position:0% which is the reason why even though it was<14:26:21.180> a<14:26:21.300> little<14:26:21.416> less<14:26:21.660> fast<14:26:21.956> it<14:26:22.320> was<14:26:22.380> still<14:26:22.616> used 14:26:22.790 --> 14:26:22.800 align:start position:0% was a little less fast it was still used 14:26:22.800 --> 14:26:25.130 align:start position:0% was a little less fast it was still used although<14:26:23.580> nowadays<14:26:24.060> we<14:26:24.360> don't<14:26:24.480> see<14:26:24.776> it<14:26:24.956> used 14:26:25.130 --> 14:26:25.140 align:start position:0% although nowadays we don't see it used 14:26:25.140 --> 14:26:26.990 align:start position:0% although nowadays we don't see it used as<14:26:25.560> much<14:26:25.740> because<14:26:26.040> it<14:26:26.276> requires<14:26:26.756> special 14:26:26.990 --> 14:26:27.000 align:start position:0% as much because it requires special 14:26:27.000 --> 14:26:29.030 align:start position:0% as much because it requires special technology<14:26:27.540> special<14:26:28.256> boxes<14:26:28.800> special 14:26:29.030 --> 14:26:29.040 align:start position:0% technology special boxes special 14:26:29.040 --> 14:26:31.490 align:start position:0% technology special boxes special equipment<14:26:29.520> and<14:26:29.700> so<14:26:29.880> on<14:26:30.000> and<14:26:30.180> so<14:26:30.360> forth 14:26:31.490 --> 14:26:31.500 align:start position:0% equipment and so on and so forth 14:26:31.500 --> 14:26:33.290 align:start position:0% equipment and so on and so forth now<14:26:32.040> the<14:26:32.220> next<14:26:32.340> technology<14:26:32.700> I<14:26:32.936> want<14:26:33.060> to<14:26:33.180> talk 14:26:33.290 --> 14:26:33.300 align:start position:0% now the next technology I want to talk 14:26:33.300 --> 14:26:35.630 align:start position:0% now the next technology I want to talk about<14:26:33.416> are<14:26:33.720> called<14:26:33.956> t<14:26:34.436> carrier<14:26:34.916> lines<14:26:35.220> T 14:26:35.630 --> 14:26:35.640 align:start position:0% about are called t carrier lines T 14:26:35.640 --> 14:26:37.426 align:start position:0% about are called t carrier lines T carrier<14:26:36.060> lines<14:26:36.240> are<14:26:36.360> dedicated<14:26:36.840> digital 14:26:37.426 --> 14:26:37.436 align:start position:0% carrier lines are dedicated digital 14:26:37.436 --> 14:26:39.470 align:start position:0% carrier lines are dedicated digital lines<14:26:37.860> that<14:26:38.400> are<14:26:38.520> leased<14:26:38.936> from<14:26:39.180> the<14:26:39.300> telephone 14:26:39.470 --> 14:26:39.480 align:start position:0% lines that are leased from the telephone 14:26:39.480 --> 14:26:42.350 align:start position:0% lines that are leased from the telephone companies<14:26:40.080> much<14:26:40.380> like<14:26:40.560> ISDN<14:26:41.220> but<14:26:41.936> they're 14:26:42.350 --> 14:26:42.360 align:start position:0% companies much like ISDN but they're 14:26:42.360 --> 14:26:44.390 align:start position:0% companies much like ISDN but they're high<14:26:42.660> speed<14:26:42.900> and<14:26:43.500> they<14:26:43.616> establish<14:26:43.980> a<14:26:44.160> stable 14:26:44.390 --> 14:26:44.400 align:start position:0% high speed and they establish a stable 14:26:44.400 --> 14:26:46.906 align:start position:0% high speed and they establish a stable connection<14:26:44.700> on<14:26:45.116> both<14:26:45.300> sides<14:26:45.660> just<14:26:46.140> like<14:26:46.256> ISDN 14:26:46.906 --> 14:26:46.916 align:start position:0% connection on both sides just like ISDN 14:26:46.916 --> 14:26:49.190 align:start position:0% connection on both sides just like ISDN now<14:26:47.520> these<14:26:47.936> connections<14:26:48.360> are<14:26:48.660> always<14:26:48.900> open 14:26:49.190 --> 14:26:49.200 align:start position:0% now these connections are always open 14:26:49.200 --> 14:26:51.946 align:start position:0% now these connections are always open unlike<14:26:49.860> isdns<14:26:50.700> so<14:26:50.936> communication<14:26:51.540> can<14:26:51.840> be 14:26:51.946 --> 14:26:51.956 align:start position:0% unlike isdns so communication can be 14:26:51.956 --> 14:26:53.870 align:start position:0% unlike isdns so communication can be made<14:26:52.140> between<14:26:52.436> the<14:26:52.740> two<14:26:52.860> ends<14:26:53.220> whenever<14:26:53.700> it's 14:26:53.870 --> 14:26:53.880 align:start position:0% made between the two ends whenever it's 14:26:53.880 --> 14:26:55.850 align:start position:0% made between the two ends whenever it's needed<14:26:54.180> there's<14:26:54.480> no<14:26:54.776> hanging<14:26:55.380> up<14:26:55.500> in<14:26:55.680> other 14:26:55.850 --> 14:26:55.860 align:start position:0% needed there's no hanging up in other 14:26:55.860 --> 14:26:58.370 align:start position:0% needed there's no hanging up in other words<14:26:56.040> because<14:26:56.700> they<14:26:57.060> provide<14:26:57.416> such<14:26:57.956> a<14:26:58.256> good 14:26:58.370 --> 14:26:58.380 align:start position:0% words because they provide such a good 14:26:58.380 --> 14:27:01.606 align:start position:0% words because they provide such a good dedicated<14:26:59.276> link<14:26:59.580> they're<14:27:00.180> also<14:27:00.540> expensive<14:27:01.380> to 14:27:01.606 --> 14:27:01.616 align:start position:0% dedicated link they're also expensive to 14:27:01.616 --> 14:27:04.310 align:start position:0% dedicated link they're also expensive to use<14:27:01.800> on<14:27:02.096> lands<14:27:02.520> although<14:27:03.360> they<14:27:03.720> were<14:27:03.900> faster 14:27:04.310 --> 14:27:04.320 align:start position:0% use on lands although they were faster 14:27:04.320 --> 14:27:06.650 align:start position:0% use on lands although they were faster and<14:27:04.916> so<14:27:05.040> we<14:27:05.276> saw<14:27:05.400> a<14:27:05.640> lot<14:27:05.700> of<14:27:05.820> companies<14:27:06.240> used<14:27:06.540> to 14:27:06.650 --> 14:27:06.660 align:start position:0% and so we saw a lot of companies used to 14:27:06.660 --> 14:27:09.106 align:start position:0% and so we saw a lot of companies used to have<14:27:06.776> T1<14:27:07.256> or<14:27:07.500> T3<14:27:07.800> connections<14:27:08.400> and<14:27:08.580> they<14:27:08.880> might 14:27:09.106 --> 14:27:09.116 align:start position:0% have T1 or T3 connections and they might 14:27:09.116 --> 14:27:11.870 align:start position:0% have T1 or T3 connections and they might still<14:27:09.416> do<14:27:09.740> now<14:27:10.740> there<14:27:10.916> are<14:27:11.040> different<14:27:11.220> types 14:27:11.870 --> 14:27:11.880 align:start position:0% still do now there are different types 14:27:11.880 --> 14:27:14.086 align:start position:0% still do now there are different types of<14:27:12.300> T<14:27:12.540> connections<14:27:13.080> available<14:27:13.256> depending<14:27:13.980> on 14:27:14.086 --> 14:27:14.096 align:start position:0% of T connections available depending on 14:27:14.096 --> 14:27:17.570 align:start position:0% of T connections available depending on the<14:27:14.276> speed<14:27:14.400> you<14:27:14.640> require<14:27:14.880> the<14:27:15.776> first<14:27:15.980> T1<14:27:16.980> is 14:27:17.570 --> 14:27:17.580 align:start position:0% the speed you require the first T1 is 14:27:17.580 --> 14:27:21.230 align:start position:0% the speed you require the first T1 is the<14:27:17.820> slowest<14:27:18.180> of<14:27:18.416> the<14:27:18.596> four<14:27:18.720> types<14:27:19.200> now 14:27:21.230 --> 14:27:21.240 align:start position:0% the slowest of the four types now 14:27:21.240 --> 14:27:24.230 align:start position:0% the slowest of the four types now like<14:27:21.956> the<14:27:22.200> other<14:27:22.380> three<14:27:22.800> it<14:27:23.756> does<14:27:24.000> create 14:27:24.230 --> 14:27:24.240 align:start position:0% like the other three it does create 14:27:24.240 --> 14:27:28.370 align:start position:0% like the other three it does create dedicated<14:27:24.900> ends<14:27:25.436> and<14:27:25.740> it's<14:27:26.220> secure 14:27:28.370 --> 14:27:28.380 align:start position:0% dedicated ends and it's secure 14:27:28.380 --> 14:27:30.170 align:start position:0% dedicated ends and it's secure and<14:27:28.860> t1s<14:27:29.340> are<14:27:29.456> generally<14:27:29.640> going<14:27:29.756> to<14:27:29.880> be<14:27:29.936> used 14:27:30.170 --> 14:27:30.180 align:start position:0% and t1s are generally going to be used 14:27:30.180 --> 14:27:34.070 align:start position:0% and t1s are generally going to be used to<14:27:30.800> connect<14:27:31.800> lands<14:27:32.580> together<14:27:32.840> so<14:27:33.840> for 14:27:34.070 --> 14:27:34.080 align:start position:0% to connect lands together so for 14:27:34.080 --> 14:27:37.426 align:start position:0% to connect lands together so for instance<14:27:34.380> if<14:27:34.860> I<14:27:35.096> have<14:27:35.276> my<14:27:35.640> Lan<14:27:36.000> on<14:27:36.900> in<14:27:37.080> one<14:27:37.320> side 14:27:37.426 --> 14:27:37.436 align:start position:0% instance if I have my Lan on in one side 14:27:37.436 --> 14:27:38.746 align:start position:0% instance if I have my Lan on in one side of<14:27:37.560> the<14:27:37.680> city<14:27:37.740> and<14:27:37.980> you<14:27:38.096> have<14:27:38.220> another<14:27:38.340> one<14:27:38.580> we 14:27:38.746 --> 14:27:38.756 align:start position:0% of the city and you have another one we 14:27:38.756 --> 14:27:40.670 align:start position:0% of the city and you have another one we might<14:27:38.936> get<14:27:39.300> or<14:27:39.660> lease<14:27:40.020> a<14:27:40.200> line<14:27:40.380> from<14:27:40.560> the 14:27:40.670 --> 14:27:40.680 align:start position:0% might get or lease a line from the 14:27:40.680 --> 14:27:41.990 align:start position:0% might get or lease a line from the telephone<14:27:40.800> company<14:27:41.160> to<14:27:41.456> directly<14:27:41.820> connect 14:27:41.990 --> 14:27:42.000 align:start position:0% telephone company to directly connect 14:27:42.000 --> 14:27:43.730 align:start position:0% telephone company to directly connect them<14:27:42.360> if<14:27:42.660> we<14:27:42.776> don't<14:27:42.840> want<14:27:42.956> to<14:27:43.080> use<14:27:43.256> the 14:27:43.730 --> 14:27:43.740 align:start position:0% them if we don't want to use the 14:27:43.740 --> 14:27:45.290 align:start position:0% them if we don't want to use the internet<14:27:43.860> nowadays<14:27:44.756> we<14:27:44.936> have<14:27:45.060> the<14:27:45.180> internet 14:27:45.290 --> 14:27:45.300 align:start position:0% internet nowadays we have the internet 14:27:45.300 --> 14:27:47.030 align:start position:0% internet nowadays we have the internet so<14:27:45.596> a<14:27:45.776> lot<14:27:45.900> of<14:27:46.020> organizations<14:27:46.616> are<14:27:46.860> going<14:27:46.980> to 14:27:47.030 --> 14:27:47.040 align:start position:0% so a lot of organizations are going to 14:27:47.040 --> 14:27:48.290 align:start position:0% so a lot of organizations are going to use<14:27:47.096> that<14:27:47.220> and<14:27:47.400> just<14:27:47.520> get<14:27:47.700> a<14:27:47.880> very<14:27:48.060> fast 14:27:48.290 --> 14:27:48.300 align:start position:0% use that and just get a very fast 14:27:48.300 --> 14:27:50.630 align:start position:0% use that and just get a very fast connection<14:27:48.596> perhaps<14:27:49.436> a<14:27:49.560> T1<14:27:49.860> or<14:27:50.040> T3<14:27:50.340> line 14:27:50.630 --> 14:27:50.640 align:start position:0% connection perhaps a T1 or T3 line 14:27:50.640 --> 14:27:53.630 align:start position:0% connection perhaps a T1 or T3 line between<14:27:51.180> them<14:27:51.660> and<14:27:52.560> their<14:27:52.740> ISP<14:27:53.220> your<14:27:53.400> internet 14:27:53.630 --> 14:27:53.640 align:start position:0% between them and their ISP your internet 14:27:53.640 --> 14:27:55.850 align:start position:0% between them and their ISP your internet service<14:27:54.000> provider<14:27:54.596> you<14:27:55.140> might<14:27:55.256> sometimes<14:27:55.680> see 14:27:55.850 --> 14:27:55.860 align:start position:0% service provider you might sometimes see 14:27:55.860 --> 14:27:58.190 align:start position:0% service provider you might sometimes see this<14:27:56.096> by<14:27:56.276> the<14:27:56.400> way<14:27:56.456> referred<14:27:57.000> to<14:27:57.116> as<14:27:57.540> Digital 14:27:58.190 --> 14:27:58.200 align:start position:0% this by the way referred to as Digital 14:27:58.200 --> 14:28:03.050 align:start position:0% this by the way referred to as Digital Signal<14:27:59.040> one<14:27:59.520> or<14:28:00.416> DS1 14:28:03.050 --> 14:28:03.060 align:start position:0% Signal one or DS1 14:28:03.060 --> 14:28:05.086 align:start position:0% Signal one or DS1 so<14:28:03.480> if<14:28:03.596> you<14:28:03.720> ever<14:28:03.776> see<14:28:04.080> DS<14:28:04.500> it's<14:28:04.800> the<14:28:04.980> same 14:28:05.086 --> 14:28:05.096 align:start position:0% so if you ever see DS it's the same 14:28:05.096 --> 14:28:07.790 align:start position:0% so if you ever see DS it's the same thing<14:28:05.160> as<14:28:05.400> a<14:28:05.580> t<14:28:05.700> line<14:28:06.000> now<14:28:06.900> T2<14:28:07.320> as<14:28:07.616> you<14:28:07.740> can 14:28:07.790 --> 14:28:07.800 align:start position:0% thing as a t line now T2 as you can 14:28:07.800 --> 14:28:09.830 align:start position:0% thing as a t line now T2 as you can imagine<14:28:07.980> are<14:28:08.456> slightly<14:28:08.880> faster<14:28:09.240> than<14:28:09.480> T1 14:28:09.830 --> 14:28:09.840 align:start position:0% imagine are slightly faster than T1 14:28:09.840 --> 14:28:11.746 align:start position:0% imagine are slightly faster than T1 lines<14:28:10.200> they're<14:28:10.680> not<14:28:10.860> much<14:28:11.040> different<14:28:11.220> they're 14:28:11.746 --> 14:28:11.756 align:start position:0% lines they're not much different they're 14:28:11.756 --> 14:28:14.210 align:start position:0% lines they're not much different they're for<14:28:12.116> some<14:28:12.240> reason<14:28:12.416> used<14:28:12.840> a<14:28:13.436> little<14:28:13.560> less<14:28:13.860> it's 14:28:14.210 --> 14:28:14.220 align:start position:0% for some reason used a little less it's 14:28:14.220 --> 14:28:16.010 align:start position:0% for some reason used a little less it's probably<14:28:14.400> because<14:28:14.580> the<14:28:14.880> speed<14:28:15.116> is<14:28:15.416> not<14:28:15.660> worth 14:28:16.010 --> 14:28:16.020 align:start position:0% probably because the speed is not worth 14:28:16.020 --> 14:28:20.390 align:start position:0% probably because the speed is not worth the<14:28:16.740> uh<14:28:16.980> upgrade<14:28:17.456> uh<14:28:18.240> and<14:28:18.480> because 14:28:20.390 --> 14:28:20.400 align:start position:0% the uh upgrade uh and because 14:28:20.400 --> 14:28:23.210 align:start position:0% the uh upgrade uh and because the<14:28:20.820> T3<14:28:21.180> is<14:28:21.540> actually<14:28:21.776> even<14:28:22.080> faster<14:28:22.500> than<14:28:22.740> T1 14:28:23.210 --> 14:28:23.220 align:start position:0% the T3 is actually even faster than T1 14:28:23.220 --> 14:28:26.630 align:start position:0% the T3 is actually even faster than T1 and<14:28:23.640> 2<14:28:23.820> T2<14:28:24.360> put<14:28:24.720> together<14:28:24.956> so<14:28:25.800> if<14:28:26.040> we<14:28:26.220> add<14:28:26.400> both 14:28:26.630 --> 14:28:26.640 align:start position:0% and 2 T2 put together so if we add both 14:28:26.640 --> 14:28:28.850 align:start position:0% and 2 T2 put together so if we add both of<14:28:26.756> those<14:28:26.880> together<14:28:27.116> we'll<14:28:27.416> get<14:28:27.540> a<14:28:27.660> T3<14:28:28.020> this<14:28:28.740> is 14:28:28.850 --> 14:28:28.860 align:start position:0% of those together we'll get a T3 this is 14:28:28.860 --> 14:28:34.426 align:start position:0% of those together we'll get a T3 this is sometimes<14:28:29.220> also<14:28:29.580> called<14:28:29.820> a<14:28:31.096> DS3<14:28:32.096> and<14:28:33.000> t1s 14:28:34.426 --> 14:28:34.436 align:start position:0% sometimes also called a DS3 and t1s 14:28:34.436 --> 14:28:36.530 align:start position:0% sometimes also called a DS3 and t1s and<14:28:35.040> t3s 14:28:36.530 --> 14:28:36.540 align:start position:0% and t3s 14:28:36.540 --> 14:28:39.830 align:start position:0% and t3s are<14:28:37.140> the<14:28:37.380> most<14:28:37.500> commonly<14:28:37.980> one<14:28:38.276> used<14:28:39.000> T<14:28:39.480> lines 14:28:39.830 --> 14:28:39.840 align:start position:0% are the most commonly one used T lines 14:28:39.840 --> 14:28:41.150 align:start position:0% are the most commonly one used T lines that<14:28:40.020> you'll<14:28:40.256> probably<14:28:40.436> see<14:28:40.680> out<14:28:40.916> in<14:28:41.040> the 14:28:41.150 --> 14:28:41.160 align:start position:0% that you'll probably see out in the 14:28:41.160 --> 14:28:41.990 align:start position:0% that you'll probably see out in the field 14:28:41.990 --> 14:28:42.000 align:start position:0% field 14:28:42.000 --> 14:28:45.650 align:start position:0% field T4<14:28:42.776> is<14:28:43.200> even<14:28:43.380> faster<14:28:43.916> in<14:28:44.400> fact<14:28:44.580> it<14:28:45.060> is<14:28:45.416> a 14:28:45.650 --> 14:28:45.660 align:start position:0% T4 is even faster in fact it is a 14:28:45.660 --> 14:28:48.530 align:start position:0% T4 is even faster in fact it is a combination<14:28:46.080> of<14:28:46.500> all<14:28:47.096> of<14:28:47.340> the<14:28:47.640> top<14:28:48.180> ones 14:28:48.530 --> 14:28:48.540 align:start position:0% combination of all of the top ones 14:28:48.540 --> 14:28:50.570 align:start position:0% combination of all of the top ones meaning<14:28:48.776> it's<14:28:49.020> faster<14:28:49.916> than<14:28:50.096> all<14:28:50.340> of<14:28:50.456> them 14:28:50.570 --> 14:28:50.580 align:start position:0% meaning it's faster than all of them 14:28:50.580 --> 14:28:52.790 align:start position:0% meaning it's faster than all of them combined<14:28:51.240> but<14:28:51.660> it's<14:28:51.840> also<14:28:52.140> pretty<14:28:52.320> expensive 14:28:52.790 --> 14:28:52.800 align:start position:0% combined but it's also pretty expensive 14:28:52.800 --> 14:28:54.530 align:start position:0% combined but it's also pretty expensive and<14:28:53.040> for<14:28:53.276> most<14:28:53.400> part<14:28:53.640> we're<14:28:53.936> going<14:28:54.060> to<14:28:54.180> see<14:28:54.300> if 14:28:54.530 --> 14:28:54.540 align:start position:0% and for most part we're going to see if 14:28:54.540 --> 14:28:57.350 align:start position:0% and for most part we're going to see if you<14:28:54.660> really<14:28:54.776> want<14:28:55.020> to<14:28:55.140> fast<14:28:55.380> line<14:28:55.560> a<14:28:55.800> T3<14:28:56.160> and<14:28:57.116> if 14:28:57.350 --> 14:28:57.360 align:start position:0% you really want to fast line a T3 and if 14:28:57.360 --> 14:28:59.390 align:start position:0% you really want to fast line a T3 and if not<14:28:57.540> you'll<14:28:57.956> probably<14:28:58.080> see<14:28:58.320> a<14:28:58.560> T1<14:28:58.860> out<14:28:59.160> in<14:28:59.276> the 14:28:59.390 --> 14:28:59.400 align:start position:0% not you'll probably see a T1 out in the 14:28:59.400 --> 14:29:01.370 align:start position:0% not you'll probably see a T1 out in the field<14:28:59.520> a<14:29:00.060> lot<14:29:00.240> of<14:29:00.360> companies<14:29:00.720> maybe<14:29:00.900> 10<14:29:01.140> 15 14:29:01.370 --> 14:29:01.380 align:start position:0% field a lot of companies maybe 10 15 14:29:01.380 --> 14:29:04.426 align:start position:0% field a lot of companies maybe 10 15 years<14:29:01.680> ago<14:29:01.860> used<14:29:02.096> to<14:29:02.276> connect<14:29:02.400> via<14:29:03.116> a<14:29:03.540> T1<14:29:03.900> or<14:29:04.320> a 14:29:04.426 --> 14:29:04.436 align:start position:0% years ago used to connect via a T1 or a 14:29:04.436 --> 14:29:05.406 align:start position:0% years ago used to connect via a T1 or a T3 14:29:05.406 --> 14:29:05.416 align:start position:0% T3 14:29:05.416 --> 14:29:07.490 align:start position:0% T3 sometimes<14:29:06.416> you'll<14:29:06.720> still<14:29:06.840> see<14:29:07.080> that<14:29:07.200> if<14:29:07.380> it's 14:29:07.490 --> 14:29:07.500 align:start position:0% sometimes you'll still see that if it's 14:29:07.500 --> 14:29:09.050 align:start position:0% sometimes you'll still see that if it's a<14:29:07.680> very<14:29:07.800> large<14:29:07.980> company<14:29:08.340> otherwise<14:29:08.880> they're 14:29:09.050 --> 14:29:09.060 align:start position:0% a very large company otherwise they're 14:29:09.060 --> 14:29:11.810 align:start position:0% a very large company otherwise they're going<14:29:09.240> to<14:29:09.300> connect<14:29:09.416> via<14:29:09.900> perhaps<14:29:10.320> a<14:29:10.500> DSL<14:29:11.160> or 14:29:11.810 --> 14:29:11.820 align:start position:0% going to connect via perhaps a DSL or 14:29:11.820 --> 14:29:13.970 align:start position:0% going to connect via perhaps a DSL or cable<14:29:12.180> connection<14:29:12.480> generally<14:29:13.380> commercially 14:29:13.970 --> 14:29:13.980 align:start position:0% cable connection generally commercially 14:29:13.980 --> 14:29:17.870 align:start position:0% cable connection generally commercially again<14:29:14.936> this<14:29:15.300> was<14:29:15.540> before<14:29:15.900> you<14:29:16.740> had<14:29:17.096> cable<14:29:17.700> and 14:29:17.870 --> 14:29:17.880 align:start position:0% again this was before you had cable and 14:29:17.880 --> 14:29:20.210 align:start position:0% again this was before you had cable and DSL<14:29:18.360> at<14:29:18.540> everyone's<14:29:18.900> homes<14:29:19.080> so<14:29:19.680> now<14:29:19.860> the 14:29:20.210 --> 14:29:20.220 align:start position:0% DSL at everyone's homes so now the 14:29:20.220 --> 14:29:21.766 align:start position:0% DSL at everyone's homes so now the technology<14:29:20.520> has<14:29:20.880> shifted<14:29:21.300> a<14:29:21.416> bit<14:29:21.540> but<14:29:21.720> it's 14:29:21.766 --> 14:29:21.776 align:start position:0% technology has shifted a bit but it's 14:29:21.776 --> 14:29:23.030 align:start position:0% technology has shifted a bit but it's important<14:29:22.080> to<14:29:22.256> know<14:29:22.380> about<14:29:22.500> this<14:29:22.680> for<14:29:22.860> Network 14:29:23.030 --> 14:29:23.040 align:start position:0% important to know about this for Network 14:29:23.040 --> 14:29:24.830 align:start position:0% important to know about this for Network plus<14:29:23.400> because<14:29:23.880> they're<14:29:24.116> testing<14:29:24.540> knowledge 14:29:24.830 --> 14:29:24.840 align:start position:0% plus because they're testing knowledge 14:29:24.840 --> 14:29:26.390 align:start position:0% plus because they're testing knowledge that<14:29:25.140> you<14:29:25.256> might<14:29:25.436> see<14:29:25.616> even<14:29:25.860> Legacy 14:29:26.390 --> 14:29:26.400 align:start position:0% that you might see even Legacy 14:29:26.400 --> 14:29:28.850 align:start position:0% that you might see even Legacy information<14:29:26.660> meaning<14:29:27.660> old<14:29:28.200> information<14:29:28.436> that 14:29:28.850 --> 14:29:28.860 align:start position:0% information meaning old information that 14:29:28.860 --> 14:29:31.070 align:start position:0% information meaning old information that you<14:29:28.980> might<14:29:29.096> run<14:29:29.276> into<14:29:29.520> or<14:29:29.756> encounter<14:29:30.300> at<14:29:30.900> an 14:29:31.070 --> 14:29:31.080 align:start position:0% you might run into or encounter at an 14:29:31.080 --> 14:29:32.630 align:start position:0% you might run into or encounter at an office<14:29:31.256> or<14:29:31.560> a<14:29:31.740> building 14:29:32.630 --> 14:29:32.640 align:start position:0% office or a building 14:29:32.640 --> 14:29:36.710 align:start position:0% office or a building now<14:29:33.240> in<14:29:33.720> 1984<14:29:34.756> if<14:29:35.756> you<14:29:35.880> recall<14:29:36.240> your<14:29:36.480> history 14:29:36.710 --> 14:29:36.720 align:start position:0% now in 1984 if you recall your history 14:29:36.720 --> 14:29:38.630 align:start position:0% now in 1984 if you recall your history or<14:29:37.020> if<14:29:37.140> you<14:29:37.320> were<14:29:37.436> around<14:29:37.500> then<14:29:38.040> you<14:29:38.580> might 14:29:38.630 --> 14:29:38.640 align:start position:0% or if you were around then you might 14:29:38.640 --> 14:29:40.130 align:start position:0% or if you were around then you might recall<14:29:38.936> that<14:29:39.116> 18t<14:29:39.596> in<14:29:39.776> the<14:29:39.840> United<14:29:39.900> States 14:29:40.130 --> 14:29:40.140 align:start position:0% recall that 18t in the United States 14:29:40.140 --> 14:29:42.470 align:start position:0% recall that 18t in the United States held<14:29:40.616> a<14:29:40.680> monopoly<14:29:41.220> on<14:29:41.400> the<14:29:41.580> network<14:29:41.756> carrier 14:29:42.470 --> 14:29:42.480 align:start position:0% held a monopoly on the network carrier 14:29:42.480 --> 14:29:45.290 align:start position:0% held a monopoly on the network carrier industry<14:29:42.956> I.E<14:29:43.680> phones<14:29:44.160> so<14:29:44.700> preceding<14:29:45.116> this 14:29:45.290 --> 14:29:45.300 align:start position:0% industry I.E phones so preceding this 14:29:45.300 --> 14:29:47.570 align:start position:0% industry I.E phones so preceding this smaller<14:29:45.840> companies<14:29:46.256> were<14:29:46.860> given<14:29:47.220> a<14:29:47.340> chance 14:29:47.570 --> 14:29:47.580 align:start position:0% smaller companies were given a chance 14:29:47.580 --> 14:29:49.490 align:start position:0% smaller companies were given a chance and<14:29:47.936> a<14:29:48.116> challenge<14:29:48.300> to<14:29:48.660> come<14:29:48.776> up<14:29:48.900> with<14:29:49.020> a<14:29:49.256> system 14:29:49.490 --> 14:29:49.500 align:start position:0% and a challenge to come up with a system 14:29:49.500 --> 14:29:52.670 align:start position:0% and a challenge to come up with a system that<14:29:50.096> was<14:29:50.220> going<14:29:50.400> to<14:29:50.456> rival<14:29:50.820> a<14:29:51.240> t<14:29:51.416> that<14:29:52.320> the<14:29:52.560> one 14:29:52.670 --> 14:29:52.680 align:start position:0% that was going to rival a t that the one 14:29:52.680 --> 14:29:55.070 align:start position:0% that was going to rival a t that the one that<14:29:52.800> they<14:29:52.980> had<14:29:53.220> so<14:29:54.060> a<14:29:54.360> company<14:29:54.480> called<14:29:54.776> Bell 14:29:55.070 --> 14:29:55.080 align:start position:0% that they had so a company called Bell 14:29:55.080 --> 14:29:56.690 align:start position:0% that they had so a company called Bell Communications<14:29:55.740> which<14:29:56.096> you<14:29:56.276> might<14:29:56.456> have 14:29:56.690 --> 14:29:56.700 align:start position:0% Communications which you might have 14:29:56.700 --> 14:29:59.446 align:start position:0% Communications which you might have heard<14:29:57.240> of<14:29:57.416> came<14:29:58.080> up<14:29:58.256> with<14:29:58.616> this<14:29:58.980> called<14:29:59.220> the 14:29:59.446 --> 14:29:59.456 align:start position:0% heard of came up with this called the 14:29:59.456 --> 14:30:02.926 align:start position:0% heard of came up with this called the synchronous<14:29:59.936> Optical<14:30:00.416> Network<14:30:00.660> or<14:30:01.616> Sonet<14:30:02.456> now 14:30:02.926 --> 14:30:02.936 align:start position:0% synchronous Optical Network or Sonet now 14:30:02.936 --> 14:30:06.290 align:start position:0% synchronous Optical Network or Sonet now sonnet<14:30:03.300> is<14:30:03.596> fiber<14:30:04.436> optic<14:30:04.916> okay<14:30:05.456> so<14:30:06.060> rather 14:30:06.290 --> 14:30:06.300 align:start position:0% sonnet is fiber optic okay so rather 14:30:06.300 --> 14:30:08.030 align:start position:0% sonnet is fiber optic okay so rather than<14:30:06.480> being<14:30:06.660> copper<14:30:07.200> we're<14:30:07.560> dealing<14:30:07.860> with 14:30:08.030 --> 14:30:08.040 align:start position:0% than being copper we're dealing with 14:30:08.040 --> 14:30:10.426 align:start position:0% than being copper we're dealing with fiber<14:30:08.520> optics<14:30:08.880> which<14:30:09.240> uses<14:30:09.540> plastic<14:30:09.956> or<14:30:10.200> glass 14:30:10.426 --> 14:30:10.436 align:start position:0% fiber optics which uses plastic or glass 14:30:10.436 --> 14:30:13.850 align:start position:0% fiber optics which uses plastic or glass and<14:30:11.276> delivers<14:30:11.820> information<14:30:12.616> and<14:30:13.616> either 14:30:13.850 --> 14:30:13.860 align:start position:0% and delivers information and either 14:30:13.860 --> 14:30:16.426 align:start position:0% and delivers information and either voice<14:30:14.276> data<14:30:14.936> and<14:30:15.300> Video<14:30:15.480> in<14:30:15.900> much<14:30:16.080> higher 14:30:16.426 --> 14:30:16.436 align:start position:0% voice data and Video in much higher 14:30:16.436 --> 14:30:19.010 align:start position:0% voice data and Video in much higher speeds<14:30:16.800> as<14:30:16.916> a<14:30:17.160> result<14:30:17.276> because<14:30:18.180> it's<14:30:18.660> using 14:30:19.010 --> 14:30:19.020 align:start position:0% speeds as a result because it's using 14:30:19.020 --> 14:30:20.446 align:start position:0% speeds as a result because it's using light<14:30:19.320> pulses 14:30:20.446 --> 14:30:20.456 align:start position:0% light pulses 14:30:20.456 --> 14:30:23.266 align:start position:0% light pulses now<14:30:21.000> this<14:30:21.360> achievement<14:30:21.900> was<14:30:22.616> so<14:30:22.860> great<14:30:22.980> that 14:30:23.266 --> 14:30:23.276 align:start position:0% now this achievement was so great that 14:30:23.276 --> 14:30:25.370 align:start position:0% now this achievement was so great that it<14:30:23.400> sparked<14:30:23.756> a<14:30:24.060> new<14:30:24.180> system<14:30:24.416> of<14:30:24.660> defining<14:30:25.020> data 14:30:25.370 --> 14:30:25.380 align:start position:0% it sparked a new system of defining data 14:30:25.380 --> 14:30:29.266 align:start position:0% it sparked a new system of defining data rates<14:30:25.560> meaning<14:30:26.276> that<14:30:27.116> the<14:30:27.720> old<14:30:27.900> systems<14:30:28.436> uh 14:30:29.266 --> 14:30:29.276 align:start position:0% rates meaning that the old systems uh 14:30:29.276 --> 14:30:31.010 align:start position:0% rates meaning that the old systems uh just<14:30:30.060> didn't 14:30:31.010 --> 14:30:31.020 align:start position:0% just didn't 14:30:31.020 --> 14:30:33.350 align:start position:0% just didn't it<14:30:31.436> was<14:30:31.680> so<14:30:31.980> slow<14:30:32.220> in<14:30:32.520> comparison<14:30:32.936> there<14:30:33.240> was 14:30:33.350 --> 14:30:33.360 align:start position:0% it was so slow in comparison there was 14:30:33.360 --> 14:30:36.946 align:start position:0% it was so slow in comparison there was nothing<14:30:33.540> that<14:30:33.900> could<14:30:34.256> sort<14:30:34.980> of<14:30:35.096> uh<14:30:35.756> uh<14:30:35.956> counter 14:30:36.946 --> 14:30:36.956 align:start position:0% nothing that could sort of uh uh counter 14:30:36.956 --> 14:30:38.990 align:start position:0% nothing that could sort of uh uh counter this<14:30:37.200> and<14:30:37.436> so<14:30:37.616> we<14:30:37.800> start<14:30:37.980> seeing<14:30:38.340> the<14:30:38.580> OC 14:30:38.990 --> 14:30:39.000 align:start position:0% this and so we start seeing the OC 14:30:39.000 --> 14:30:41.030 align:start position:0% this and so we start seeing the OC levels<14:30:39.416> like<14:30:39.720> for<14:30:40.020> instance<14:30:40.256> one<14:30:40.740> you<14:30:40.916> might 14:30:41.030 --> 14:30:41.040 align:start position:0% levels like for instance one you might 14:30:41.040 --> 14:30:42.310 align:start position:0% levels like for instance one you might have<14:30:41.220> seen<14:30:41.400> is 14:30:42.310 --> 14:30:42.320 align:start position:0% have seen is 14:30:42.320 --> 14:30:45.290 align:start position:0% have seen is oc9<14:30:43.320> and<14:30:43.860> that<14:30:43.980> would<14:30:44.160> be<14:30:44.340> really<14:30:44.756> really<14:30:44.936> fast 14:30:45.290 --> 14:30:45.300 align:start position:0% oc9 and that would be really really fast 14:30:45.300 --> 14:30:47.030 align:start position:0% oc9 and that would be really really fast now<14:30:45.596> don't<14:30:45.840> worry<14:30:46.080> about<14:30:46.320> knowing<14:30:46.800> the 14:30:47.030 --> 14:30:47.040 align:start position:0% now don't worry about knowing the 14:30:47.040 --> 14:30:48.530 align:start position:0% now don't worry about knowing the specific<14:30:47.340> speeds<14:30:47.880> for<14:30:48.060> the<14:30:48.180> network<14:30:48.240> plus 14:30:48.530 --> 14:30:48.540 align:start position:0% specific speeds for the network plus 14:30:48.540 --> 14:30:50.030 align:start position:0% specific speeds for the network plus exam<14:30:48.840> that's<14:30:49.080> why<14:30:49.200> I'm<14:30:49.320> not<14:30:49.500> covering<14:30:49.916> them 14:30:50.030 --> 14:30:50.040 align:start position:0% exam that's why I'm not covering them 14:30:50.040 --> 14:30:52.070 align:start position:0% exam that's why I'm not covering them what<14:30:50.520> you<14:30:50.756> just<14:30:50.880> want<14:30:51.060> to<14:30:51.180> make<14:30:51.300> sure<14:30:51.540> of<14:30:51.720> is<14:30:51.900> if 14:30:52.070 --> 14:30:52.080 align:start position:0% what you just want to make sure of is if 14:30:52.080 --> 14:30:54.946 align:start position:0% what you just want to make sure of is if you<14:30:52.200> see<14:30:52.500> OC<14:30:53.340> versus<14:30:53.580> like<14:30:53.880> a<14:30:54.000> T1<14:30:54.240> or<14:30:54.416> T3<14:30:54.720> you 14:30:54.946 --> 14:30:54.956 align:start position:0% you see OC versus like a T1 or T3 you 14:30:54.956 --> 14:30:56.330 align:start position:0% you see OC versus like a T1 or T3 you want<14:30:55.080> to<14:30:55.200> know<14:30:55.256> that<14:30:55.436> the<14:30:55.560> OC<14:30:55.860> is<14:30:56.096> generally 14:30:56.330 --> 14:30:56.340 align:start position:0% want to know that the OC is generally 14:30:56.340 --> 14:30:58.310 align:start position:0% want to know that the OC is generally going<14:30:56.580> to<14:30:56.700> be<14:30:56.756> faster<14:30:57.116> because<14:30:57.596> again<14:30:57.900> look<14:30:58.140> at 14:30:58.310 --> 14:30:58.320 align:start position:0% going to be faster because again look at 14:30:58.320 --> 14:31:01.190 align:start position:0% going to be faster because again look at this<14:30:58.500> word<14:30:58.616> Optical<14:30:59.276> carrier<14:30:59.880> levels 14:31:01.190 --> 14:31:01.200 align:start position:0% this word Optical carrier levels 14:31:01.200 --> 14:31:03.230 align:start position:0% this word Optical carrier levels now<14:31:01.800> in<14:31:02.220> the<14:31:02.400> mid 14:31:03.230 --> 14:31:03.240 align:start position:0% now in the mid 14:31:03.240 --> 14:31:06.530 align:start position:0% now in the mid um<14:31:03.560> 1970s<14:31:04.560> we<14:31:05.096> had<14:31:05.220> something<14:31:05.456> called<14:31:05.756> x25 14:31:06.530 --> 14:31:06.540 align:start position:0% um 1970s we had something called x25 14:31:06.540 --> 14:31:09.830 align:start position:0% um 1970s we had something called x25 which<14:31:07.020> was<14:31:07.756> everywhere<14:31:08.756> and<14:31:09.480> this<14:31:09.660> was 14:31:09.830 --> 14:31:09.840 align:start position:0% which was everywhere and this was 14:31:09.840 --> 14:31:11.510 align:start position:0% which was everywhere and this was technology<14:31:10.256> that<14:31:10.616> was<14:31:10.740> developed<14:31:11.096> as<14:31:11.220> a<14:31:11.456> way 14:31:11.510 --> 14:31:11.520 align:start position:0% technology that was developed as a way 14:31:11.520 --> 14:31:14.210 align:start position:0% technology that was developed as a way to<14:31:11.756> send<14:31:11.936> data<14:31:12.416> over<14:31:12.840> copper<14:31:13.436> wiring<14:31:13.800> so<14:31:14.040> not 14:31:14.210 --> 14:31:14.220 align:start position:0% to send data over copper wiring so not 14:31:14.220 --> 14:31:17.086 align:start position:0% to send data over copper wiring so not that<14:31:14.400> OC<14:31:14.756> stuff<14:31:15.060> but<14:31:15.300> more<14:31:15.416> the<14:31:15.596> t1s<14:31:16.320> ETC<14:31:16.436> and 14:31:17.086 --> 14:31:17.096 align:start position:0% that OC stuff but more the t1s ETC and 14:31:17.096 --> 14:31:19.730 align:start position:0% that OC stuff but more the t1s ETC and isdns<14:31:17.936> but<14:31:18.300> during<14:31:18.596> its<14:31:18.900> creation<14:31:19.200> everyone 14:31:19.730 --> 14:31:19.740 align:start position:0% isdns but during its creation everyone 14:31:19.740 --> 14:31:21.170 align:start position:0% isdns but during its creation everyone in<14:31:19.980> the<14:31:20.096> networking<14:31:20.400> Communications<14:31:20.880> world 14:31:21.170 --> 14:31:21.180 align:start position:0% in the networking Communications world 14:31:21.180 --> 14:31:23.030 align:start position:0% in the networking Communications world had<14:31:21.540> a<14:31:21.720> part<14:31:21.840> in<14:31:21.956> creating<14:31:22.320> and<14:31:22.500> implementing 14:31:23.030 --> 14:31:23.040 align:start position:0% had a part in creating and implementing 14:31:23.040 --> 14:31:26.390 align:start position:0% had a part in creating and implementing it<14:31:23.220> you<14:31:23.700> might<14:31:23.880> see<14:31:24.180> x25<14:31:24.956> or<14:31:25.320> terms<14:31:25.860> and<14:31:26.096> you 14:31:26.390 --> 14:31:26.400 align:start position:0% it you might see x25 or terms and you 14:31:26.400 --> 14:31:29.390 align:start position:0% it you might see x25 or terms and you used<14:31:27.116> to<14:31:27.480> talk<14:31:27.720> about<14:31:27.840> how<14:31:28.256> they<14:31:28.500> would<14:31:28.740> take 14:31:29.390 --> 14:31:29.400 align:start position:0% used to talk about how they would take 14:31:29.400 --> 14:31:33.106 align:start position:0% used to talk about how they would take data<14:31:29.936> and<14:31:30.660> send<14:31:30.900> it<14:31:31.080> over<14:31:31.200> these<14:31:31.860> uh<14:31:32.400> this 14:31:33.106 --> 14:31:33.116 align:start position:0% data and send it over these uh this 14:31:33.116 --> 14:31:35.990 align:start position:0% data and send it over these uh this technologies<14:31:33.660> that<14:31:34.020> it<14:31:34.436> had<14:31:34.680> and<14:31:35.220> its<14:31:35.580> format 14:31:35.990 --> 14:31:36.000 align:start position:0% technologies that it had and its format 14:31:36.000 --> 14:31:38.690 align:start position:0% technologies that it had and its format was<14:31:36.240> virtually<14:31:36.840> Universal<14:31:37.500> however<14:31:38.220> it<14:31:38.580> was 14:31:38.690 --> 14:31:38.700 align:start position:0% was virtually Universal however it was 14:31:38.700 --> 14:31:40.970 align:start position:0% was virtually Universal however it was really<14:31:38.936> limited<14:31:39.360> by<14:31:39.660> speeds<14:31:40.256> because<14:31:40.560> of<14:31:40.860> the 14:31:40.970 --> 14:31:40.980 align:start position:0% really limited by speeds because of the 14:31:40.980 --> 14:31:42.350 align:start position:0% really limited by speeds because of the copper<14:31:41.276> wiring<14:31:41.580> and<14:31:41.756> just<14:31:41.936> because<14:31:42.060> of<14:31:42.240> the 14:31:42.350 --> 14:31:42.360 align:start position:0% copper wiring and just because of the 14:31:42.360 --> 14:31:45.050 align:start position:0% copper wiring and just because of the way<14:31:42.480> that<14:31:42.720> the<14:31:42.840> protocol<14:31:43.140> worked<14:31:43.700> uh<14:31:44.700> which 14:31:45.050 --> 14:31:45.060 align:start position:0% way that the protocol worked uh which 14:31:45.060 --> 14:31:48.106 align:start position:0% way that the protocol worked uh which I'll<14:31:45.240> write<14:31:45.480> up<14:31:45.660> here 14:31:48.106 --> 14:31:48.116 align:start position:0% 14:31:48.116 --> 14:31:50.530 align:start position:0% and<14:31:48.660> so<14:31:48.840> it<14:31:49.080> was<14:31:49.200> replaced<14:31:49.800> by<14:31:50.040> something 14:31:50.530 --> 14:31:50.540 align:start position:0% and so it was replaced by something 14:31:50.540 --> 14:31:54.766 align:start position:0% and so it was replaced by something called<14:31:51.540> frame<14:31:52.380> relay<14:31:53.040> now<14:31:53.640> frame<14:31:54.000> relay<14:31:54.416> is<14:31:54.660> a 14:31:54.766 --> 14:31:54.776 align:start position:0% called frame relay now frame relay is a 14:31:54.776 --> 14:31:56.990 align:start position:0% called frame relay now frame relay is a protocol<14:31:55.020> that<14:31:55.320> was<14:31:55.436> developed<14:31:55.916> basically<14:31:56.640> to 14:31:56.990 --> 14:31:57.000 align:start position:0% protocol that was developed basically to 14:31:57.000 --> 14:32:00.350 align:start position:0% protocol that was developed basically to transfer<14:31:57.540> between<14:31:58.256> LAN 14:32:00.350 --> 14:32:00.360 align:start position:0% transfer between LAN 14:32:00.360 --> 14:32:02.746 align:start position:0% transfer between LAN and<14:32:00.900> Wan<14:32:01.256> end<14:32:01.560> points<14:32:02.096> in<14:32:02.520> other<14:32:02.580> words 14:32:02.746 --> 14:32:02.756 align:start position:0% and Wan end points in other words 14:32:02.756 --> 14:32:06.406 align:start position:0% and Wan end points in other words between<14:32:03.060> My<14:32:03.540> Lan<14:32:03.900> and<14:32:04.320> the<14:32:04.500> ISP<14:32:05.096> or<14:32:05.756> my<14:32:06.000> larger 14:32:06.406 --> 14:32:06.416 align:start position:0% between My Lan and the ISP or my larger 14:32:06.416 --> 14:32:08.810 align:start position:0% between My Lan and the ISP or my larger wide<14:32:06.776> area<14:32:06.956> network<14:32:07.256> the<14:32:08.160> way<14:32:08.276> it<14:32:08.400> functions 14:32:08.810 --> 14:32:08.820 align:start position:0% wide area network the way it functions 14:32:08.820 --> 14:32:10.490 align:start position:0% wide area network the way it functions is<14:32:09.000> not<14:32:09.240> important<14:32:09.660> just<14:32:09.956> know<14:32:10.140> that<14:32:10.320> it 14:32:10.490 --> 14:32:10.500 align:start position:0% is not important just know that it 14:32:10.500 --> 14:32:14.330 align:start position:0% is not important just know that it functions<14:32:10.860> similarly<14:32:11.580> to<14:32:12.240> x25<14:32:13.140> but<14:32:13.916> it's 14:32:14.330 --> 14:32:14.340 align:start position:0% functions similarly to x25 but it's 14:32:14.340 --> 14:32:18.406 align:start position:0% functions similarly to x25 but it's faster 14:32:18.406 --> 14:32:18.416 align:start position:0% 14:32:18.416 --> 14:32:21.050 align:start position:0% and<14:32:18.956> it<14:32:19.080> has<14:32:19.200> a<14:32:19.436> more<14:32:19.560> modern<14:32:19.800> build<14:32:20.220> behind<14:32:20.820> it 14:32:21.050 --> 14:32:21.060 align:start position:0% and it has a more modern build behind it 14:32:21.060 --> 14:32:23.630 align:start position:0% and it has a more modern build behind it they're<14:32:22.020> also<14:32:22.380> both<14:32:22.560> called<14:32:22.980> packet 14:32:23.630 --> 14:32:23.640 align:start position:0% they're also both called packet 14:32:23.640 --> 14:32:25.970 align:start position:0% they're also both called packet switching<14:32:24.060> Technologies<14:32:24.660> and<14:32:25.380> we'll<14:32:25.800> talk 14:32:25.970 --> 14:32:25.980 align:start position:0% switching Technologies and we'll talk 14:32:25.980 --> 14:32:29.746 align:start position:0% switching Technologies and we'll talk about<14:32:26.160> that<14:32:26.400> later<14:32:26.640> but<14:32:27.416> frame<14:32:28.140> relay<14:32:28.560> can<14:32:29.160> can 14:32:29.746 --> 14:32:29.756 align:start position:0% about that later but frame relay can can 14:32:29.756 --> 14:32:32.746 align:start position:0% about that later but frame relay can can send<14:32:30.320> smaller<14:32:31.320> packets<14:32:31.800> and<14:32:32.340> it<14:32:32.456> can<14:32:32.580> send 14:32:32.746 --> 14:32:32.756 align:start position:0% send smaller packets and it can send 14:32:32.756 --> 14:32:37.730 align:start position:0% send smaller packets and it can send them<14:32:32.936> faster 14:32:37.730 --> 14:32:37.740 align:start position:0% 14:32:37.740 --> 14:32:39.710 align:start position:0% we'll<14:32:38.276> talk<14:32:38.456> more<14:32:38.700> about<14:32:38.880> uh<14:32:39.360> packet 14:32:39.710 --> 14:32:39.720 align:start position:0% we'll talk more about uh packet 14:32:39.720 --> 14:32:43.490 align:start position:0% we'll talk more about uh packet switching<14:32:40.200> in<14:32:40.980> the<14:32:41.456> next<14:32:41.820> module 14:32:43.490 --> 14:32:43.500 align:start position:0% switching in the next module 14:32:43.500 --> 14:32:44.710 align:start position:0% switching in the next module finally<14:32:44.040> I<14:32:44.160> want<14:32:44.276> to<14:32:44.400> talk<14:32:44.520> about 14:32:44.710 --> 14:32:44.720 align:start position:0% finally I want to talk about 14:32:44.720 --> 14:32:48.830 align:start position:0% finally I want to talk about asynchronous<14:32:45.720> transfer<14:32:46.200> mode<14:32:46.456> or<14:32:47.660> ATMs<14:32:48.660> if 14:32:48.830 --> 14:32:48.840 align:start position:0% asynchronous transfer mode or ATMs if 14:32:48.840 --> 14:32:50.390 align:start position:0% asynchronous transfer mode or ATMs if you<14:32:48.956> ever<14:32:49.020> see<14:32:49.200> ATM<14:32:49.616> on<14:32:49.800> the<14:32:49.916> test<14:32:50.040> this<14:32:50.276> is 14:32:50.390 --> 14:32:50.400 align:start position:0% you ever see ATM on the test this is 14:32:50.400 --> 14:32:52.370 align:start position:0% you ever see ATM on the test this is what<14:32:50.520> they're<14:32:50.640> referring<14:32:51.000> to<14:32:51.180> a<14:32:51.900> wide<14:32:52.140> area 14:32:52.370 --> 14:32:52.380 align:start position:0% what they're referring to a wide area 14:32:52.380 --> 14:32:55.310 align:start position:0% what they're referring to a wide area network<14:32:52.740> uh<14:32:53.700> transmission<14:32:54.060> or<14:32:54.540> transfer<14:32:55.080> mode 14:32:55.310 --> 14:32:55.320 align:start position:0% network uh transmission or transfer mode 14:32:55.320 --> 14:32:57.406 align:start position:0% network uh transmission or transfer mode it<14:32:55.916> was<14:32:55.980> introduced<14:32:56.340> in<14:32:56.456> the<14:32:56.640> 90s<14:32:57.000> as<14:32:57.240> a 14:32:57.406 --> 14:32:57.416 align:start position:0% it was introduced in the 90s as a 14:32:57.416 --> 14:32:59.926 align:start position:0% it was introduced in the 90s as a successor<14:32:57.956> two<14:32:58.320> frame<14:32:58.680> relay<14:32:59.096> and<14:32:59.640> it<14:32:59.820> was 14:32:59.926 --> 14:32:59.936 align:start position:0% successor two frame relay and it was 14:32:59.936 --> 14:33:01.570 align:start position:0% successor two frame relay and it was really<14:33:00.180> considered<14:33:00.660> a<14:33:00.840> breakthrough<14:33:01.320> because 14:33:01.570 --> 14:33:01.580 align:start position:0% really considered a breakthrough because 14:33:01.580 --> 14:33:04.850 align:start position:0% really considered a breakthrough because it<14:33:02.580> was<14:33:03.116> what<14:33:03.360> they<14:33:03.540> call<14:33:03.720> an<14:33:04.140> end-to-end 14:33:04.850 --> 14:33:04.860 align:start position:0% it was what they call an end-to-end 14:33:04.860 --> 14:33:07.490 align:start position:0% it was what they call an end-to-end solution<14:33:05.400> that<14:33:06.000> could<14:33:06.180> work<14:33:06.360> either<14:33:06.776> desk 14:33:07.490 --> 14:33:07.500 align:start position:0% solution that could work either desk 14:33:07.500 --> 14:33:10.130 align:start position:0% solution that could work either desk from<14:33:07.980> the<14:33:08.160> desktop<14:33:08.520> or<14:33:09.000> remotely<14:33:09.416> what<14:33:09.956> this 14:33:10.130 --> 14:33:10.140 align:start position:0% from the desktop or remotely what this 14:33:10.140 --> 14:33:13.370 align:start position:0% from the desktop or remotely what this meant<14:33:10.436> is<14:33:10.680> that<14:33:11.276> it<14:33:11.520> could<14:33:11.640> work<14:33:11.936> on<14:33:12.416> a<14:33:12.956> Wan<14:33:13.200> a 14:33:13.370 --> 14:33:13.380 align:start position:0% meant is that it could work on a Wan a 14:33:13.380 --> 14:33:15.606 align:start position:0% meant is that it could work on a Wan a wide<14:33:13.560> area<14:33:13.680> network<14:33:13.916> and<14:33:14.400> within<14:33:14.936> the<14:33:15.180> land 14:33:15.606 --> 14:33:15.616 align:start position:0% wide area network and within the land 14:33:15.616 --> 14:33:18.050 align:start position:0% wide area network and within the land however<14:33:16.616> this<14:33:16.980> sort<14:33:17.160> of<14:33:17.276> proves<14:33:17.640> not<14:33:17.936> really 14:33:18.050 --> 14:33:18.060 align:start position:0% however this sort of proves not really 14:33:18.060 --> 14:33:20.746 align:start position:0% however this sort of proves not really to<14:33:18.300> be<14:33:18.416> true<14:33:18.596> because<14:33:18.956> the<14:33:19.380> technology<14:33:19.860> sort 14:33:20.746 --> 14:33:20.756 align:start position:0% to be true because the technology sort 14:33:20.756 --> 14:33:21.890 align:start position:0% to be true because the technology sort of<14:33:20.820> got 14:33:21.890 --> 14:33:21.900 align:start position:0% of got 14:33:21.900 --> 14:33:24.710 align:start position:0% of got for<14:33:22.560> lack<14:33:22.800> of<14:33:22.860> a<14:33:23.040> better<14:33:23.096> word<14:33:23.340> pushed<14:33:24.180> out<14:33:24.360> of 14:33:24.710 --> 14:33:24.720 align:start position:0% for lack of a better word pushed out of 14:33:24.720 --> 14:33:26.150 align:start position:0% for lack of a better word pushed out of the<14:33:24.956> land<14:33:25.140> market<14:33:25.436> because<14:33:25.800> other 14:33:26.150 --> 14:33:26.160 align:start position:0% the land market because other 14:33:26.160 --> 14:33:27.650 align:start position:0% the land market because other technologists<14:33:26.756> came<14:33:26.936> around<14:33:27.116> that<14:33:27.300> were<14:33:27.480> just 14:33:27.650 --> 14:33:27.660 align:start position:0% technologists came around that were just 14:33:27.660 --> 14:33:30.406 align:start position:0% technologists came around that were just better<14:33:27.840> it<14:33:28.560> was<14:33:28.740> actually<14:33:28.916> pretty<14:33:29.456> expensive 14:33:30.406 --> 14:33:30.416 align:start position:0% better it was actually pretty expensive 14:33:30.416 --> 14:33:32.926 align:start position:0% better it was actually pretty expensive to<14:33:30.660> use<14:33:30.840> but<14:33:31.320> it<14:33:31.436> did<14:33:31.616> have<14:33:31.740> some<14:33:31.916> benefits<14:33:32.640> one 14:33:32.926 --> 14:33:32.936 align:start position:0% to use but it did have some benefits one 14:33:32.936 --> 14:33:34.790 align:start position:0% to use but it did have some benefits one of<14:33:33.000> the<14:33:33.116> main<14:33:33.240> ones<14:33:33.660> just<14:33:34.140> like<14:33:34.256> with<14:33:34.436> the<14:33:34.680> T 14:33:34.790 --> 14:33:34.800 align:start position:0% of the main ones just like with the T 14:33:34.800 --> 14:33:37.670 align:start position:0% of the main ones just like with the T aligns<14:33:35.456> is<14:33:35.700> it<14:33:35.936> could<14:33:36.300> transfer<14:33:36.956> data<14:33:37.436> voice 14:33:37.670 --> 14:33:37.680 align:start position:0% aligns is it could transfer data voice 14:33:37.680 --> 14:33:40.606 align:start position:0% aligns is it could transfer data voice and<14:33:38.400> video<14:33:38.820> it's<14:33:39.480> also<14:33:39.840> a<14:33:39.956> packet<14:33:40.256> switching 14:33:40.606 --> 14:33:40.616 align:start position:0% and video it's also a packet switching 14:33:40.616 --> 14:33:41.810 align:start position:0% and video it's also a packet switching technology<14:33:40.916> something<14:33:41.220> we're<14:33:41.456> going<14:33:41.580> to<14:33:41.640> talk 14:33:41.810 --> 14:33:41.820 align:start position:0% technology something we're going to talk 14:33:41.820 --> 14:33:44.086 align:start position:0% technology something we're going to talk about<14:33:41.936> and<14:33:42.596> it's<14:33:42.720> pretty<14:33:42.956> fast<14:33:43.256> and<14:33:43.800> one<14:33:43.980> of 14:33:44.086 --> 14:33:44.096 align:start position:0% about and it's pretty fast and one of 14:33:44.096 --> 14:33:45.230 align:start position:0% about and it's pretty fast and one of the<14:33:44.160> major<14:33:44.340> things<14:33:44.640> we're<14:33:44.936> going<14:33:45.060> to<14:33:45.116> talk 14:33:45.230 --> 14:33:45.240 align:start position:0% the major things we're going to talk 14:33:45.240 --> 14:33:46.970 align:start position:0% the major things we're going to talk about<14:33:45.416> with<14:33:45.660> it<14:33:45.840> is<14:33:46.020> that<14:33:46.200> it<14:33:46.320> used<14:33:46.500> what<14:33:46.800> are 14:33:46.970 --> 14:33:46.980 align:start position:0% about with it is that it used what are 14:33:46.980 --> 14:33:50.810 align:start position:0% about with it is that it used what are called<14:33:47.160> cells<14:33:48.000> and<14:33:48.480> the<14:33:48.660> cells<14:33:49.080> were<14:33:49.616> 53<14:33:50.276> bytes 14:33:50.810 --> 14:33:50.820 align:start position:0% called cells and the cells were 53 bytes 14:33:50.820 --> 14:33:53.150 align:start position:0% called cells and the cells were 53 bytes long<14:33:51.116> which<14:33:51.480> is<14:33:51.596> fairly<14:33:52.020> large<14:33:52.256> for<14:33:52.680> a<14:33:52.860> packet 14:33:53.150 --> 14:33:53.160 align:start position:0% long which is fairly large for a packet 14:33:53.160 --> 14:33:55.670 align:start position:0% long which is fairly large for a packet of<14:33:53.276> data<14:33:53.640> and<14:33:54.360> I<14:33:54.540> shouldn't<14:33:54.776> say<14:33:54.900> even<14:33:55.080> pack<14:33:55.436> it 14:33:55.670 --> 14:33:55.680 align:start position:0% of data and I shouldn't say even pack it 14:33:55.680 --> 14:33:57.170 align:start position:0% of data and I shouldn't say even pack it because<14:33:56.096> what<14:33:56.520> it<14:33:56.640> really<14:33:56.756> we're<14:33:57.000> talking 14:33:57.170 --> 14:33:57.180 align:start position:0% because what it really we're talking 14:33:57.180 --> 14:33:59.926 align:start position:0% because what it really we're talking about<14:33:57.360> is<14:33:57.720> it<14:33:58.256> was<14:33:58.380> replaced<14:33:58.800> by<14:33:58.980> cells<14:33:59.456> so 14:33:59.926 --> 14:33:59.936 align:start position:0% about is it was replaced by cells so 14:33:59.936 --> 14:34:02.746 align:start position:0% about is it was replaced by cells so these<14:34:00.180> cells<14:34:00.540> have<14:34:01.500> proven<14:34:01.860> to<14:34:02.160> work<14:34:02.340> more 14:34:02.746 --> 14:34:02.756 align:start position:0% these cells have proven to work more 14:34:02.756 --> 14:34:04.790 align:start position:0% these cells have proven to work more efficiently<14:34:03.240> for<14:34:03.596> transferring<14:34:04.256> than 14:34:04.790 --> 14:34:04.800 align:start position:0% efficiently for transferring than 14:34:04.800 --> 14:34:07.010 align:start position:0% efficiently for transferring than packets<14:34:05.456> that<14:34:05.700> were<14:34:05.820> used<14:34:06.000> by<14:34:06.300> frame<14:34:06.596> relay 14:34:07.010 --> 14:34:07.020 align:start position:0% packets that were used by frame relay 14:34:07.020 --> 14:34:09.050 align:start position:0% packets that were used by frame relay and<14:34:07.436> this<14:34:07.616> is<14:34:07.800> really<14:34:08.040> sort<14:34:08.276> of<14:34:08.400> the<14:34:08.520> legacy<14:34:08.936> of 14:34:09.050 --> 14:34:09.060 align:start position:0% and this is really sort of the legacy of 14:34:09.060 --> 14:34:11.630 align:start position:0% and this is really sort of the legacy of ATM<14:34:09.480> was<14:34:09.720> using<14:34:10.020> these<14:34:10.380> cells<14:34:10.740> that<14:34:11.160> had<14:34:11.400> a<14:34:11.520> lot 14:34:11.630 --> 14:34:11.640 align:start position:0% ATM was using these cells that had a lot 14:34:11.640 --> 14:34:13.670 align:start position:0% ATM was using these cells that had a lot more<14:34:11.820> information<14:34:12.116> in<14:34:12.720> them<14:34:12.900> than<14:34:13.256> the<14:34:13.436> frame 14:34:13.670 --> 14:34:13.680 align:start position:0% more information in them than the frame 14:34:13.680 --> 14:34:15.350 align:start position:0% more information in them than the frame relay<14:34:14.040> packets<14:34:14.400> which<14:34:14.640> were<14:34:14.756> much<14:34:14.936> smaller 14:34:15.350 --> 14:34:15.360 align:start position:0% relay packets which were much smaller 14:34:15.360 --> 14:34:16.790 align:start position:0% relay packets which were much smaller obviously<14:34:15.956> the<14:34:16.080> more<14:34:16.200> information<14:34:16.380> we<14:34:16.680> could 14:34:16.790 --> 14:34:16.800 align:start position:0% obviously the more information we could 14:34:16.800 --> 14:34:18.350 align:start position:0% obviously the more information we could cram<14:34:17.040> into<14:34:17.220> a<14:34:17.400> packet<14:34:17.640> the<14:34:17.820> faster<14:34:18.060> we<14:34:18.240> could 14:34:18.350 --> 14:34:18.360 align:start position:0% cram into a packet the faster we could 14:34:18.360 --> 14:34:19.730 align:start position:0% cram into a packet the faster we could send<14:34:18.540> it<14:34:18.720> the<14:34:19.020> quicker<14:34:19.380> we<14:34:19.500> can<14:34:19.616> get 14:34:19.730 --> 14:34:19.740 align:start position:0% send it the quicker we can get 14:34:19.740 --> 14:34:21.830 align:start position:0% send it the quicker we can get information<14:34:19.916> to<14:34:20.456> the<14:34:20.640> other<14:34:20.880> side 14:34:21.830 --> 14:34:21.840 align:start position:0% information to the other side 14:34:21.840 --> 14:34:24.946 align:start position:0% information to the other side of<14:34:22.256> a<14:34:22.560> network<14:34:22.680> or<14:34:23.096> a<14:34:23.276> wide<14:34:23.520> area<14:34:23.700> network 14:34:24.946 --> 14:34:24.956 align:start position:0% of a network or a wide area network 14:34:24.956 --> 14:34:26.990 align:start position:0% of a network or a wide area network and<14:34:25.436> if<14:34:25.500> we<14:34:25.680> just<14:34:25.800> look<14:34:25.980> at<14:34:26.096> this<14:34:26.340> this<14:34:26.756> is<14:34:26.880> just 14:34:26.990 --> 14:34:27.000 align:start position:0% and if we just look at this this is just 14:34:27.000 --> 14:34:30.470 align:start position:0% and if we just look at this this is just to<14:34:27.180> show<14:34:27.300> us<14:34:27.480> that<14:34:27.776> it<14:34:28.020> has<14:34:28.256> again<14:34:28.860> voice 14:34:30.470 --> 14:34:30.480 align:start position:0% to show us that it has again voice 14:34:30.480 --> 14:34:32.990 align:start position:0% to show us that it has again voice data<14:34:31.200> and<14:34:32.040> video 14:34:32.990 --> 14:34:33.000 align:start position:0% data and video 14:34:33.000 --> 14:34:35.210 align:start position:0% data and video all<14:34:33.720> in<14:34:33.956> one 14:34:35.210 --> 14:34:35.220 align:start position:0% all in one 14:34:35.220 --> 14:34:38.870 align:start position:0% all in one cell<14:34:35.880> which<14:34:36.416> was<14:34:36.596> sort<14:34:36.840> of<14:34:36.900> the<14:34:37.200> amazing<14:34:37.680> thing 14:34:38.870 --> 14:34:38.880 align:start position:0% cell which was sort of the amazing thing 14:34:38.880 --> 14:34:41.870 align:start position:0% cell which was sort of the amazing thing that<14:34:39.360> this<14:34:39.596> technology<14:34:40.080> ATM<14:34:40.860> did<14:34:41.096> good<14:34:41.580> way<14:34:41.756> to 14:34:41.870 --> 14:34:41.880 align:start position:0% that this technology ATM did good way to 14:34:41.880 --> 14:34:43.246 align:start position:0% that this technology ATM did good way to remember<14:34:42.000> it<14:34:42.240> is<14:34:42.360> to<14:34:42.480> think<14:34:42.596> about<14:34:42.720> going<14:34:43.020> to 14:34:43.246 --> 14:34:43.256 align:start position:0% remember it is to think about going to 14:34:43.256 --> 14:34:44.926 align:start position:0% remember it is to think about going to the<14:34:43.380> ATM<14:34:43.740> you<14:34:43.980> can<14:34:44.040> check<14:34:44.220> your<14:34:44.400> balance<14:34:44.700> you 14:34:44.926 --> 14:34:44.936 align:start position:0% the ATM you can check your balance you 14:34:44.936 --> 14:34:46.130 align:start position:0% the ATM you can check your balance you can<14:34:45.060> get<14:34:45.180> money<14:34:45.360> you<14:34:45.596> can<14:34:45.660> pull<14:34:45.776> out<14:34:45.956> of<14:34:46.080> your 14:34:46.130 --> 14:34:46.140 align:start position:0% can get money you can pull out of your 14:34:46.140 --> 14:34:47.150 align:start position:0% can get money you can pull out of your savings<14:34:46.380> you<14:34:46.616> can<14:34:46.680> pull<14:34:46.800> out<14:34:46.916> of<14:34:47.096> your 14:34:47.150 --> 14:34:47.160 align:start position:0% savings you can pull out of your 14:34:47.160 --> 14:34:49.010 align:start position:0% savings you can pull out of your checking<14:34:47.520> and<14:34:47.936> so<14:34:48.116> it<14:34:48.240> sort<14:34:48.480> of<14:34:48.540> does<14:34:48.660> a<14:34:48.840> lot<14:34:48.900> of 14:34:49.010 --> 14:34:49.020 align:start position:0% checking and so it sort of does a lot of 14:34:49.020 --> 14:34:50.690 align:start position:0% checking and so it sort of does a lot of things<14:34:49.140> when<14:34:49.320> it<14:34:49.436> comes<14:34:49.560> to<14:34:49.680> your<14:34:49.860> bank<14:34:50.040> same 14:34:50.690 --> 14:34:50.700 align:start position:0% things when it comes to your bank same 14:34:50.700 --> 14:34:52.970 align:start position:0% things when it comes to your bank same with<14:34:51.000> the<14:34:51.180> ATM<14:34:51.596> cell 14:34:52.970 --> 14:34:52.980 align:start position:0% with the ATM cell 14:34:52.980 --> 14:34:55.490 align:start position:0% with the ATM cell all<14:34:53.580> right<14:34:53.756> so<14:34:54.240> those<14:34:54.840> are<14:34:54.956> all<14:34:55.080> the<14:34:55.256> WAN 14:34:55.490 --> 14:34:55.500 align:start position:0% all right so those are all the WAN 14:34:55.500 --> 14:34:56.926 align:start position:0% all right so those are all the WAN transmission<14:34:55.740> technologies<14:34:56.400> I<14:34:56.580> just<14:34:56.700> want<14:34:56.820> to 14:34:56.926 --> 14:34:56.936 align:start position:0% transmission technologies I just want to 14:34:56.936 --> 14:34:59.030 align:start position:0% transmission technologies I just want to briefly<14:34:57.180> go<14:34:57.360> over<14:34:57.480> obviously<14:34:58.140> we<14:34:58.560> took<14:34:58.740> a<14:34:58.860> very 14:34:59.030 --> 14:34:59.040 align:start position:0% briefly go over obviously we took a very 14:34:59.040 --> 14:35:00.946 align:start position:0% briefly go over obviously we took a very cursory<14:34:59.456> overview<14:34:59.880> of<14:35:00.000> them<14:35:00.240> and<14:35:00.416> and<14:35:00.660> you 14:35:00.946 --> 14:35:00.956 align:start position:0% cursory overview of them and and you 14:35:00.956 --> 14:35:02.446 align:start position:0% cursory overview of them and and you could<14:35:01.436> probably<14:35:01.560> Google<14:35:01.800> and<14:35:02.040> find<14:35:02.160> a<14:35:02.340> lot 14:35:02.446 --> 14:35:02.456 align:start position:0% could probably Google and find a lot 14:35:02.456 --> 14:35:03.650 align:start position:0% could probably Google and find a lot more<14:35:02.580> information<14:35:02.820> that's<14:35:03.180> going<14:35:03.416> to<14:35:03.416> go<14:35:03.540> over 14:35:03.650 --> 14:35:03.660 align:start position:0% more information that's going to go over 14:35:03.660 --> 14:35:04.970 align:start position:0% more information that's going to go over your<14:35:03.900> head<14:35:04.080> and<14:35:04.436> you<14:35:04.560> don't<14:35:04.616> need<14:35:04.740> to<14:35:04.860> know 14:35:04.970 --> 14:35:04.980 align:start position:0% your head and you don't need to know 14:35:04.980 --> 14:35:06.350 align:start position:0% your head and you don't need to know that<14:35:05.096> for<14:35:05.276> Network<14:35:05.400> plus<14:35:05.700> but<14:35:06.000> what<14:35:06.180> I<14:35:06.300> want 14:35:06.350 --> 14:35:06.360 align:start position:0% that for Network plus but what I want 14:35:06.360 --> 14:35:08.926 align:start position:0% that for Network plus but what I want you<14:35:06.480> to<14:35:06.596> remember<14:35:06.720> again<14:35:07.140> is<14:35:07.800> that<14:35:07.980> ISDN<14:35:08.700> was 14:35:08.926 --> 14:35:08.936 align:start position:0% you to remember again is that ISDN was 14:35:08.936 --> 14:35:12.766 align:start position:0% you to remember again is that ISDN was used<14:35:09.116> it<14:35:09.596> really<14:35:09.776> either<14:35:10.436> came<14:35:10.680> in<14:35:10.916> that<14:35:11.160> BPI 14:35:12.766 --> 14:35:12.776 align:start position:0% used it really either came in that BPI 14:35:12.776 --> 14:35:16.850 align:start position:0% used it really either came in that BPI or<14:35:13.080> rather<14:35:13.256> Bri<14:35:13.860> or<14:35:14.416> PRI<14:35:15.416> modes<14:35:16.080> PR<14:35:16.436> was 14:35:16.850 --> 14:35:16.860 align:start position:0% or rather Bri or PRI modes PR was 14:35:16.860 --> 14:35:19.190 align:start position:0% or rather Bri or PRI modes PR was slightly<14:35:17.276> faster<14:35:17.640> it<14:35:18.300> was<14:35:18.416> either<14:35:18.540> in<14:35:18.776> 64 14:35:19.190 --> 14:35:19.200 align:start position:0% slightly faster it was either in 64 14:35:19.200 --> 14:35:21.530 align:start position:0% slightly faster it was either in 64 kilobits<14:35:19.740> per<14:35:19.860> second<14:35:20.040> or<14:35:20.340> 128<14:35:20.880> kilobits<14:35:21.416> per 14:35:21.530 --> 14:35:21.540 align:start position:0% kilobits per second or 128 kilobits per 14:35:21.540 --> 14:35:24.170 align:start position:0% kilobits per second or 128 kilobits per second<14:35:21.720> it<14:35:22.436> worked<14:35:22.680> over<14:35:22.860> the<14:35:23.160> existing<14:35:23.580> pots 14:35:24.170 --> 14:35:24.180 align:start position:0% second it worked over the existing pots 14:35:24.180 --> 14:35:28.010 align:start position:0% second it worked over the existing pots or<14:35:25.020> pstn<14:35:25.800> phone<14:35:26.040> system<14:35:26.540> but<14:35:27.540> it<14:35:27.720> was<14:35:27.840> still 14:35:28.010 --> 14:35:28.020 align:start position:0% or pstn phone system but it was still 14:35:28.020 --> 14:35:29.630 align:start position:0% or pstn phone system but it was still relatively<14:35:28.560> slow<14:35:28.740> we<14:35:28.980> don't<14:35:29.160> see<14:35:29.276> it<14:35:29.456> much 14:35:29.630 --> 14:35:29.640 align:start position:0% relatively slow we don't see it much 14:35:29.640 --> 14:35:31.310 align:start position:0% relatively slow we don't see it much anymore<14:35:29.880> although<14:35:30.416> it<14:35:30.540> was<14:35:30.660> pretty<14:35:30.900> big<14:35:31.080> maybe 14:35:31.310 --> 14:35:31.320 align:start position:0% anymore although it was pretty big maybe 14:35:31.320 --> 14:35:34.010 align:start position:0% anymore although it was pretty big maybe 15<14:35:31.616> years<14:35:31.980> ago<14:35:32.340> the<14:35:33.000> T<14:35:33.116> carriers<14:35:33.540> the<14:35:33.720> big<14:35:33.840> ones 14:35:34.010 --> 14:35:34.020 align:start position:0% 15 years ago the T carriers the big ones 14:35:34.020 --> 14:35:36.170 align:start position:0% 15 years ago the T carriers the big ones you're<14:35:34.140> going<14:35:34.256> to<14:35:34.256> see<14:35:34.380> are<14:35:34.616> T1<14:35:34.980> and<14:35:35.756> T3 14:35:36.170 --> 14:35:36.180 align:start position:0% you're going to see are T1 and T3 14:35:36.180 --> 14:35:40.850 align:start position:0% you're going to see are T1 and T3 remember<14:35:36.776> that<14:35:37.140> T3<14:35:37.616> is<14:35:38.456> faster<14:35:38.820> than<14:35:39.180> T1<14:35:39.860> Sonet 14:35:40.850 --> 14:35:40.860 align:start position:0% remember that T3 is faster than T1 Sonet 14:35:40.860 --> 14:35:43.490 align:start position:0% remember that T3 is faster than T1 Sonet as<14:35:41.160> well<14:35:41.340> was<14:35:41.880> introduced 14:35:43.490 --> 14:35:43.500 align:start position:0% as well was introduced 14:35:43.500 --> 14:35:46.426 align:start position:0% as well was introduced excuse<14:35:44.096> me<14:35:44.276> it<14:35:44.936> replaced 14:35:46.426 --> 14:35:46.436 align:start position:0% excuse me it replaced 14:35:46.436 --> 14:35:49.850 align:start position:0% excuse me it replaced the<14:35:47.340> sort<14:35:47.640> of<14:35:47.756> tea<14:35:48.000> way<14:35:48.416> of<14:35:48.596> looking<14:35:48.900> at<14:35:49.200> speeds 14:35:49.850 --> 14:35:49.860 align:start position:0% the sort of tea way of looking at speeds 14:35:49.860 --> 14:35:51.530 align:start position:0% the sort of tea way of looking at speeds with<14:35:50.040> the<14:35:50.220> OC 14:35:51.530 --> 14:35:51.540 align:start position:0% with the OC 14:35:51.540 --> 14:35:54.650 align:start position:0% with the OC system<14:35:52.020> OC 14:35:54.650 --> 14:35:54.660 align:start position:0% system OC 14:35:54.660 --> 14:35:56.746 align:start position:0% system OC is<14:35:55.080> fiber<14:35:55.500> optic<14:35:55.800> and<14:35:56.040> if<14:35:56.220> you<14:35:56.340> think<14:35:56.580> about 14:35:56.746 --> 14:35:56.756 align:start position:0% is fiber optic and if you think about 14:35:56.756 --> 14:35:59.630 align:start position:0% is fiber optic and if you think about the<14:35:57.116> O<14:35:57.360> in<14:35:57.840> there<14:35:58.020> being<14:35:58.200> optic<14:35:58.680> that's<14:35:58.980> why<14:35:59.340> it 14:35:59.630 --> 14:35:59.640 align:start position:0% the O in there being optic that's why it 14:35:59.640 --> 14:36:03.890 align:start position:0% the O in there being optic that's why it was<14:35:59.820> faster<14:36:00.560> x25<14:36:01.560> and<14:36:01.800> frame<14:36:02.160> relay<14:36:02.580> both<14:36:03.240> ways 14:36:03.890 --> 14:36:03.900 align:start position:0% was faster x25 and frame relay both ways 14:36:03.900 --> 14:36:05.510 align:start position:0% was faster x25 and frame relay both ways of<14:36:04.080> transferring 14:36:05.510 --> 14:36:05.520 align:start position:0% of transferring 14:36:05.520 --> 14:36:09.230 align:start position:0% of transferring when<14:36:06.480> data<14:36:07.080> this<14:36:07.616> was<14:36:07.800> replaced<14:36:08.400> mostly<14:36:08.756> by 14:36:09.230 --> 14:36:09.240 align:start position:0% when data this was replaced mostly by 14:36:09.240 --> 14:36:11.330 align:start position:0% when data this was replaced mostly by ATM<14:36:09.840> both<14:36:10.380> of<14:36:10.560> these<14:36:10.680> are<14:36:10.800> what<14:36:10.980> we<14:36:11.096> call 14:36:11.330 --> 14:36:11.340 align:start position:0% ATM both of these are what we call 14:36:11.340 --> 14:36:14.510 align:start position:0% ATM both of these are what we call packet<14:36:12.300> switching<14:36:12.840> which<14:36:13.740> we<14:36:13.916> will<14:36:14.096> look<14:36:14.276> at 14:36:14.510 --> 14:36:14.520 align:start position:0% packet switching which we will look at 14:36:14.520 --> 14:36:16.850 align:start position:0% packet switching which we will look at in<14:36:15.060> the<14:36:15.180> next<14:36:15.360> module 14:36:16.850 --> 14:36:16.860 align:start position:0% in the next module 14:36:16.860 --> 14:36:19.030 align:start position:0% in the next module and<14:36:17.456> the<14:36:17.640> important<14:36:17.880> thing<14:36:18.000> with<14:36:18.180> ATM<14:36:18.660> again 14:36:19.030 --> 14:36:19.040 align:start position:0% and the important thing with ATM again 14:36:19.040 --> 14:36:21.290 align:start position:0% and the important thing with ATM again not<14:36:20.040> the<14:36:20.340> thing<14:36:20.456> that<14:36:20.700> you<14:36:20.820> put<14:36:20.936> your<14:36:21.116> money 14:36:21.290 --> 14:36:21.300 align:start position:0% not the thing that you put your money 14:36:21.300 --> 14:36:24.350 align:start position:0% not the thing that you put your money into<14:36:21.540> but<14:36:22.140> rather<14:36:22.380> a<14:36:22.680> Wan<14:36:22.980> technology<14:36:23.456> it<14:36:24.180> was 14:36:24.350 --> 14:36:24.360 align:start position:0% into but rather a Wan technology it was 14:36:24.360 --> 14:36:26.390 align:start position:0% into but rather a Wan technology it was marketed<14:36:24.776> as<14:36:24.956> being 14:36:26.390 --> 14:36:26.400 align:start position:0% marketed as being 14:36:26.400 --> 14:36:29.086 align:start position:0% marketed as being end<14:36:26.936> to<14:36:27.116> end<14:36:27.360> meaning<14:36:27.956> it<14:36:28.200> could<14:36:28.380> work<14:36:28.616> from 14:36:29.086 --> 14:36:29.096 align:start position:0% end to end meaning it could work from 14:36:29.096 --> 14:36:31.070 align:start position:0% end to end meaning it could work from the<14:36:29.400> computer<14:36:29.700> to<14:36:30.060> the<14:36:30.180> computer<14:36:30.360> although 14:36:31.070 --> 14:36:31.080 align:start position:0% the computer to the computer although 14:36:31.080 --> 14:36:33.050 align:start position:0% the computer to the computer although nowadays<14:36:31.560> we<14:36:31.860> really<14:36:31.980> use<14:36:32.220> it<14:36:32.400> in<14:36:32.700> Wan 14:36:33.050 --> 14:36:33.060 align:start position:0% nowadays we really use it in Wan 14:36:33.060 --> 14:36:35.266 align:start position:0% nowadays we really use it in Wan Technologies<14:36:33.596> from<14:36:34.320> a<14:36:34.500> land<14:36:34.680> to<14:36:34.980> a<14:36:35.096> land 14:36:35.266 --> 14:36:35.276 align:start position:0% Technologies from a land to a land 14:36:35.276 --> 14:36:37.190 align:start position:0% Technologies from a land to a land endpoint<14:36:36.000> and<14:36:36.540> the<14:36:36.720> other<14:36:36.776> thing<14:36:36.900> it<14:36:37.020> really 14:36:37.190 --> 14:36:37.200 align:start position:0% endpoint and the other thing it really 14:36:37.200 --> 14:36:40.606 align:start position:0% endpoint and the other thing it really introduced<14:36:37.680> was<14:36:37.860> that<14:36:38.096> 53<14:36:38.580> byte<14:36:39.240> long<14:36:39.956> info 14:36:40.606 --> 14:36:40.616 align:start position:0% introduced was that 53 byte long info 14:36:40.616 --> 14:36:43.370 align:start position:0% introduced was that 53 byte long info cell 14:36:43.370 --> 14:36:43.380 align:start position:0% cell 14:36:43.380 --> 14:36:46.490 align:start position:0% cell which<14:36:43.916> again<14:36:44.040> can<14:36:44.340> hold<14:36:44.520> video<14:36:45.080> voice<14:36:46.080> and 14:36:46.490 --> 14:36:46.500 align:start position:0% which again can hold video voice and 14:36:46.500 --> 14:36:51.090 align:start position:0% which again can hold video voice and data<14:36:46.916> in<14:36:47.040> it 14:36:51.090 --> 14:36:51.100 align:start position:0% 14:36:51.100 --> 14:36:59.766 align:start position:0% [Music] 14:36:59.766 --> 14:36:59.776 align:start position:0% [Music] 14:36:59.776 --> 14:37:07.246 align:start position:0% [Music] thank<14:37:00.776> you 14:37:07.246 --> 14:37:07.256 align:start position:0% 14:37:07.256 --> 14:37:10.010 align:start position:0% look<14:37:07.616> at<14:37:07.916> the<14:37:07.980> module<14:37:08.340> 9<14:37:08.640> lesson<14:37:09.116> 2A<14:37:09.660> least 14:37:10.010 --> 14:37:10.020 align:start position:0% look at the module 9 lesson 2A least 14:37:10.020 --> 14:37:11.446 align:start position:0% look at the module 9 lesson 2A least lines 14:37:11.446 --> 14:37:11.456 align:start position:0% lines 14:37:11.456 --> 14:37:16.970 align:start position:0% lines I'm<14:37:11.640> gonna<14:37:11.820> look<14:37:12.000> at<14:37:12.180> T1<14:37:12.660> E1<14:37:13.380> T3<14:37:14.040> E3<14:37:15.200> and<14:37:16.200> sonnet 14:37:16.970 --> 14:37:16.980 align:start position:0% I'm gonna look at T1 E1 T3 E3 and sonnet 14:37:16.980 --> 14:37:19.730 align:start position:0% I'm gonna look at T1 E1 T3 E3 and sonnet synchronized<14:37:17.820> Optical<14:37:18.180> networking 14:37:19.730 --> 14:37:19.740 align:start position:0% synchronized Optical networking 14:37:19.740 --> 14:37:22.190 align:start position:0% synchronized Optical networking these<14:37:20.580> are<14:37:20.700> a<14:37:20.820> syllabus<14:37:21.240> talking<14:37:21.480> points<14:37:22.020> so 14:37:22.190 --> 14:37:22.200 align:start position:0% these are a syllabus talking points so 14:37:22.200 --> 14:37:23.570 align:start position:0% these are a syllabus talking points so kind<14:37:22.500> of<14:37:22.616> need<14:37:22.740> to<14:37:22.860> cover<14:37:22.980> some<14:37:23.220> of<14:37:23.340> the<14:37:23.400> things 14:37:23.570 --> 14:37:23.580 align:start position:0% kind of need to cover some of the things 14:37:23.580 --> 14:37:26.510 align:start position:0% kind of need to cover some of the things I<14:37:23.820> think<14:37:23.936> could<14:37:24.116> come<14:37:24.360> up<14:37:24.500> it's<14:37:25.500> uh<14:37:25.740> Ali<14:37:26.276> you've 14:37:26.510 --> 14:37:26.520 align:start position:0% I think could come up it's uh Ali you've 14:37:26.520 --> 14:37:28.490 align:start position:0% I think could come up it's uh Ali you've got<14:37:26.580> a<14:37:26.936> lot<14:37:27.000> of<14:37:27.116> choices<14:37:27.480> when<14:37:27.840> you<14:37:28.140> want<14:37:28.380> to 14:37:28.490 --> 14:37:28.500 align:start position:0% got a lot of choices when you want to 14:37:28.500 --> 14:37:30.586 align:start position:0% got a lot of choices when you want to connect<14:37:28.740> your<14:37:29.400> small<14:37:29.640> office<14:37:29.880> or<14:37:30.240> even<14:37:30.360> a 14:37:30.586 --> 14:37:30.596 align:start position:0% connect your small office or even a 14:37:30.596 --> 14:37:32.330 align:start position:0% connect your small office or even a larger<14:37:30.840> office 14:37:32.330 --> 14:37:32.340 align:start position:0% larger office 14:37:32.340 --> 14:37:34.490 align:start position:0% larger office across<14:37:33.000> to<14:37:33.116> the<14:37:33.240> internet<14:37:33.416> or<14:37:33.956> to<14:37:34.200> another 14:37:34.490 --> 14:37:34.500 align:start position:0% across to the internet or to another 14:37:34.500 --> 14:37:36.530 align:start position:0% across to the internet or to another remote<14:37:35.040> office<14:37:35.456> somewhere<14:37:36.000> else<14:37:36.116> that<14:37:36.416> you 14:37:36.530 --> 14:37:36.540 align:start position:0% remote office somewhere else that you 14:37:36.540 --> 14:37:38.926 align:start position:0% remote office somewhere else that you own 14:37:38.926 --> 14:37:38.936 align:start position:0% 14:37:38.936 --> 14:37:41.390 align:start position:0% now<14:37:39.300> one<14:37:39.540> of<14:37:39.660> these<14:37:39.900> options<14:37:40.256> is<14:37:40.616> a<14:37:40.860> lease<14:37:41.160> line 14:37:41.390 --> 14:37:41.400 align:start position:0% now one of these options is a lease line 14:37:41.400 --> 14:37:44.446 align:start position:0% now one of these options is a lease line which<14:37:42.000> is<14:37:42.060> a<14:37:42.300> dedicated<14:37:42.720> telecoms<14:37:43.616> line 14:37:44.446 --> 14:37:44.456 align:start position:0% which is a dedicated telecoms line 14:37:44.456 --> 14:37:46.870 align:start position:0% which is a dedicated telecoms line now<14:37:44.936> you<14:37:45.240> don't<14:37:45.360> install<14:37:45.660> the<14:37:46.020> line<14:37:46.200> it'll<14:37:46.616> be 14:37:46.870 --> 14:37:46.880 align:start position:0% now you don't install the line it'll be 14:37:46.880 --> 14:37:49.670 align:start position:0% now you don't install the line it'll be the<14:37:47.880> roads<14:37:48.180> will<14:37:48.300> be<14:37:48.480> dug<14:37:48.660> up<14:37:48.900> or<14:37:49.320> wherever 14:37:49.670 --> 14:37:49.680 align:start position:0% the roads will be dug up or wherever 14:37:49.680 --> 14:37:52.370 align:start position:0% the roads will be dug up or wherever they<14:37:49.916> put<14:37:50.096> their<14:37:50.340> cables<14:37:50.936> will<14:37:51.596> be 14:37:52.370 --> 14:37:52.380 align:start position:0% they put their cables will be 14:37:52.380 --> 14:37:55.790 align:start position:0% they put their cables will be um<14:37:52.436> all<14:37:52.980> laid<14:37:53.340> by<14:37:53.820> telecoms<14:37:54.720> company<14:37:54.900> and 14:37:55.790 --> 14:37:55.800 align:start position:0% um all laid by telecoms company and 14:37:55.800 --> 14:37:58.070 align:start position:0% um all laid by telecoms company and you'll<14:37:55.980> release<14:37:56.160> that<14:37:56.520> line<14:37:56.756> for<14:37:57.060> a<14:37:57.240> fixed<14:37:57.720> fee 14:37:58.070 --> 14:37:58.080 align:start position:0% you'll release that line for a fixed fee 14:37:58.080 --> 14:38:00.230 align:start position:0% you'll release that line for a fixed fee usually<14:37:58.436> monthly<14:37:58.860> and<14:37:59.096> you<14:37:59.276> have<14:37:59.640> to<14:37:59.820> sign<14:38:00.060> a 14:38:00.230 --> 14:38:00.240 align:start position:0% usually monthly and you have to sign a 14:38:00.240 --> 14:38:03.050 align:start position:0% usually monthly and you have to sign a contract<14:38:00.660> this<14:38:01.320> lease<14:38:01.680> line<14:38:01.916> is<14:38:02.400> available<14:38:02.640> to 14:38:03.050 --> 14:38:03.060 align:start position:0% contract this lease line is available to 14:38:03.060 --> 14:38:06.586 align:start position:0% contract this lease line is available to you<14:38:03.180> all<14:38:03.480> of<14:38:03.660> the<14:38:03.840> time<14:38:04.020> 24<14:38:04.916> 7. 14:38:06.586 --> 14:38:06.596 align:start position:0% you all of the time 24 7. 14:38:06.596 --> 14:38:08.926 align:start position:0% you all of the time 24 7. so<14:38:07.200> since<14:38:07.560> this<14:38:07.740> dedicated<14:38:08.160> line<14:38:08.400> it's<14:38:08.700> not 14:38:08.926 --> 14:38:08.936 align:start position:0% so since this dedicated line it's not 14:38:08.936 --> 14:38:11.266 align:start position:0% so since this dedicated line it's not shared<14:38:09.240> with<14:38:09.300> other<14:38:09.540> users<14:38:10.160> here's<14:38:11.160> an 14:38:11.266 --> 14:38:11.276 align:start position:0% shared with other users here's an 14:38:11.276 --> 14:38:12.946 align:start position:0% shared with other users here's an illustration<14:38:11.820> it's<14:38:12.180> an<14:38:12.480> image<14:38:12.776> from 14:38:12.946 --> 14:38:12.956 align:start position:0% illustration it's an image from 14:38:12.956 --> 14:38:15.350 align:start position:0% illustration it's an image from Wikipedia<14:38:13.680> at<14:38:14.640> the<14:38:14.756> bottom<14:38:14.936> you've<14:38:15.240> got 14:38:15.350 --> 14:38:15.360 align:start position:0% Wikipedia at the bottom you've got 14:38:15.360 --> 14:38:19.730 align:start position:0% Wikipedia at the bottom you've got remote<14:38:15.660> users<14:38:16.320> using<14:38:17.096> the<14:38:17.456> public<14:38:17.820> uh<14:38:19.256> switch 14:38:19.730 --> 14:38:19.740 align:start position:0% remote users using the public uh switch 14:38:19.740 --> 14:38:22.310 align:start position:0% remote users using the public uh switch telephone<14:38:20.040> Network<14:38:20.520> they're<14:38:21.060> dialing<14:38:21.480> in 14:38:22.310 --> 14:38:22.320 align:start position:0% telephone Network they're dialing in 14:38:22.320 --> 14:38:24.230 align:start position:0% telephone Network they're dialing in I<14:38:22.800> suppose<14:38:22.980> nowadays<14:38:23.456> they'd<14:38:23.756> be<14:38:23.880> using 14:38:24.230 --> 14:38:24.240 align:start position:0% I suppose nowadays they'd be using 14:38:24.240 --> 14:38:27.050 align:start position:0% I suppose nowadays they'd be using broadband<14:38:24.720> and<14:38:25.560> um<14:38:25.560> vpns<14:38:26.456> they<14:38:26.700> could<14:38:26.880> be 14:38:27.050 --> 14:38:27.060 align:start position:0% broadband and um vpns they could be 14:38:27.060 --> 14:38:28.370 align:start position:0% broadband and um vpns they could be working<14:38:27.116> from<14:38:27.416> anywhere 14:38:28.370 --> 14:38:28.380 align:start position:0% working from anywhere 14:38:28.380 --> 14:38:30.350 align:start position:0% working from anywhere but<14:38:28.740> you've<14:38:28.916> got<14:38:29.040> two<14:38:29.340> Regional<14:38:29.756> Offices<14:38:30.116> on 14:38:30.350 --> 14:38:30.360 align:start position:0% but you've got two Regional Offices on 14:38:30.360 --> 14:38:31.670 align:start position:0% but you've got two Regional Offices on the<14:38:30.480> left<14:38:30.596> that<14:38:30.840> need<14:38:31.020> a<14:38:31.256> dedicated 14:38:31.670 --> 14:38:31.680 align:start position:0% the left that need a dedicated 14:38:31.680 --> 14:38:34.606 align:start position:0% the left that need a dedicated connection<14:38:32.040> of<14:38:32.456> 24<14:38:32.820> 7.<14:38:33.480> they'll<14:38:34.320> go<14:38:34.500> through 14:38:34.606 --> 14:38:34.616 align:start position:0% connection of 24 7. they'll go through 14:38:34.616 --> 14:38:38.086 align:start position:0% connection of 24 7. they'll go through the<14:38:34.800> telecoms<14:38:35.400> network<14:38:35.580> using<14:38:36.300> a<14:38:36.540> lease<14:38:36.900> line 14:38:38.086 --> 14:38:38.096 align:start position:0% the telecoms network using a lease line 14:38:38.096 --> 14:38:40.670 align:start position:0% the telecoms network using a lease line foreign 14:38:40.670 --> 14:38:40.680 align:start position:0% foreign 14:38:40.680 --> 14:38:43.130 align:start position:0% foreign based<14:38:41.640> on<14:38:41.700> the<14:38:41.880> technology<14:38:42.180> the<14:38:42.480> bandwidth<14:38:43.020> of 14:38:43.130 --> 14:38:43.140 align:start position:0% based on the technology the bandwidth of 14:38:43.140 --> 14:38:45.290 align:start position:0% based on the technology the bandwidth of a<14:38:43.320> lease<14:38:43.500> line<14:38:43.680> varies<14:38:44.096> typically<14:38:44.700> between 14:38:45.290 --> 14:38:45.300 align:start position:0% a lease line varies typically between 14:38:45.300 --> 14:38:48.350 align:start position:0% a lease line varies typically between 56k<14:38:46.140> and<14:38:46.500> 2<14:38:46.680> Meg<14:38:47.096> to<14:38:47.756> be<14:38:47.880> honest<14:38:48.116> there's 14:38:48.350 --> 14:38:48.360 align:start position:0% 56k and 2 Meg to be honest there's 14:38:48.360 --> 14:38:50.990 align:start position:0% 56k and 2 Meg to be honest there's unlikely<14:38:48.956> be<14:38:49.256> using<14:38:49.500> 56k<14:38:50.220> unless<14:38:50.700> you<14:38:50.820> just 14:38:50.990 --> 14:38:51.000 align:start position:0% unlikely be using 56k unless you just 14:38:51.000 --> 14:38:53.150 align:start position:0% unlikely be using 56k unless you just wanted<14:38:51.240> to<14:38:51.660> have 14:38:53.150 --> 14:38:53.160 align:start position:0% wanted to have 14:38:53.160 --> 14:38:54.890 align:start position:0% wanted to have um<14:38:53.220> like<14:38:53.580> some<14:38:53.820> sort<14:38:54.000> of<14:38:54.116> keyless<14:38:54.480> entry 14:38:54.890 --> 14:38:54.900 align:start position:0% um like some sort of keyless entry 14:38:54.900 --> 14:38:57.530 align:start position:0% um like some sort of keyless entry system<14:38:55.200> perhaps<14:38:55.800> for<14:38:56.096> a<14:38:56.276> gym<14:38:56.456> where<14:38:57.180> it<14:38:57.360> just 14:38:57.530 --> 14:38:57.540 align:start position:0% system perhaps for a gym where it just 14:38:57.540 --> 14:39:00.230 align:start position:0% system perhaps for a gym where it just needs<14:38:57.776> to<14:38:57.916> authenticate<14:38:58.916> people<14:38:59.220> but<14:39:00.060> even 14:39:00.230 --> 14:39:00.240 align:start position:0% needs to authenticate people but even 14:39:00.240 --> 14:39:02.390 align:start position:0% needs to authenticate people but even then<14:39:00.480> the<14:39:00.720> costs<14:39:01.020> are<14:39:01.080> so<14:39:01.256> low<14:39:01.436> now<14:39:01.740> that<14:39:02.400> um 14:39:02.390 --> 14:39:02.400 align:start position:0% then the costs are so low now that um 14:39:02.400 --> 14:39:05.150 align:start position:0% then the costs are so low now that um it's<14:39:03.000> unlikely<14:39:03.480> to<14:39:03.596> be<14:39:03.720> that<14:39:03.956> slow 14:39:05.150 --> 14:39:05.160 align:start position:0% it's unlikely to be that slow 14:39:05.160 --> 14:39:07.550 align:start position:0% it's unlikely to be that slow okay<14:39:05.756> some<14:39:06.116> advantages<14:39:06.540> we've<14:39:07.080> already<14:39:07.256> said 14:39:07.550 --> 14:39:07.560 align:start position:0% okay some advantages we've already said 14:39:07.560 --> 14:39:09.766 align:start position:0% okay some advantages we've already said it's<14:39:07.860> it's<14:39:07.980> your<14:39:08.400> connection<14:39:08.700> dedicated<14:39:09.480> to 14:39:09.766 --> 14:39:09.776 align:start position:0% it's it's your connection dedicated to 14:39:09.776 --> 14:39:11.690 align:start position:0% it's it's your connection dedicated to you<14:39:09.956> and<14:39:10.380> you<14:39:10.560> can<14:39:10.680> choose<14:39:10.916> how<14:39:11.160> you<14:39:11.276> allocate 14:39:11.690 --> 14:39:11.700 align:start position:0% you and you can choose how you allocate 14:39:11.700 --> 14:39:13.606 align:start position:0% you and you can choose how you allocate that<14:39:11.880> bandwidth<14:39:12.480> if<14:39:13.080> you<14:39:13.140> want<14:39:13.256> to<14:39:13.436> use<14:39:13.500> it 14:39:13.606 --> 14:39:13.616 align:start position:0% that bandwidth if you want to use it 14:39:13.616 --> 14:39:16.850 align:start position:0% that bandwidth if you want to use it mainly<14:39:13.916> for<14:39:14.096> video<14:39:14.276> conferencing<14:39:15.116> or<14:39:15.720> some<14:39:16.680> of 14:39:16.850 --> 14:39:16.860 align:start position:0% mainly for video conferencing or some of 14:39:16.860 --> 14:39:19.426 align:start position:0% mainly for video conferencing or some of the<14:39:16.980> some<14:39:17.340> of<14:39:17.580> the<14:39:17.700> use<14:39:18.140> disadvantage<14:39:19.140> they 14:39:19.426 --> 14:39:19.436 align:start position:0% the some of the use disadvantage they 14:39:19.436 --> 14:39:22.310 align:start position:0% the some of the use disadvantage they are<14:39:19.616> quite<14:39:19.860> expensive 14:39:22.310 --> 14:39:22.320 align:start position:0% are quite expensive 14:39:22.320 --> 14:39:25.730 align:start position:0% are quite expensive and<14:39:23.220> typically<14:39:23.756> used<14:39:24.180> to<14:39:24.956> connect<14:39:25.080> businesses 14:39:25.730 --> 14:39:25.740 align:start position:0% and typically used to connect businesses 14:39:25.740 --> 14:39:27.470 align:start position:0% and typically used to connect businesses that<14:39:25.980> have<14:39:26.160> a<14:39:26.400> geographically<14:39:27.000> distant 14:39:27.470 --> 14:39:27.480 align:start position:0% that have a geographically distant 14:39:27.480 --> 14:39:30.290 align:start position:0% that have a geographically distant offices<14:39:27.840> so<14:39:28.320> they<14:39:28.860> tend<14:39:29.096> to<14:39:29.220> be<14:39:29.820> um<14:39:29.820> Somewhere 14:39:30.290 --> 14:39:30.300 align:start position:0% offices so they tend to be um Somewhere 14:39:30.300 --> 14:39:32.030 align:start position:0% offices so they tend to be um Somewhere Out<14:39:30.540> In<14:39:30.660> The<14:39:30.840> Sticks 14:39:32.030 --> 14:39:32.040 align:start position:0% Out In The Sticks 14:39:32.040 --> 14:39:35.210 align:start position:0% Out In The Sticks and<14:39:32.640> a<14:39:32.820> bit<14:39:33.000> more<14:39:33.180> difficult<14:39:33.540> to<14:39:34.080> use<14:39:34.980> other 14:39:35.210 --> 14:39:35.220 align:start position:0% and a bit more difficult to use other 14:39:35.220 --> 14:39:37.606 align:start position:0% and a bit more difficult to use other connections<14:39:35.756> for<14:39:36.060> example<14:39:36.300> a<14:39:36.776> broadband 14:39:37.606 --> 14:39:37.616 align:start position:0% connections for example a broadband 14:39:37.616 --> 14:39:40.010 align:start position:0% connections for example a broadband connection<14:39:38.276> with<14:39:38.700> a<14:39:38.880> VPN 14:39:40.010 --> 14:39:40.020 align:start position:0% connection with a VPN 14:39:40.020 --> 14:39:41.690 align:start position:0% connection with a VPN always<14:39:40.380> active<14:39:40.860> and<14:39:41.040> like<14:39:41.160> a<14:39:41.340> dial-up 14:39:41.690 --> 14:39:41.700 align:start position:0% always active and like a dial-up 14:39:41.700 --> 14:39:43.790 align:start position:0% always active and like a dial-up connection<14:39:41.936> dial-ups<14:39:42.776> are<14:39:42.956> fairly<14:39:43.320> old 14:39:43.790 --> 14:39:43.800 align:start position:0% connection dial-ups are fairly old 14:39:43.800 --> 14:39:45.470 align:start position:0% connection dial-ups are fairly old technology<14:39:44.340> now 14:39:45.470 --> 14:39:45.480 align:start position:0% technology now 14:39:45.480 --> 14:39:47.630 align:start position:0% technology now and<14:39:45.900> quite<14:39:46.256> expensive 14:39:47.630 --> 14:39:47.640 align:start position:0% and quite expensive 14:39:47.640 --> 14:39:50.210 align:start position:0% and quite expensive okay<14:39:48.360> the<14:39:48.900> telecoms<14:39:49.616> company<14:39:49.740> will<14:39:50.040> charge 14:39:50.210 --> 14:39:50.220 align:start position:0% okay the telecoms company will charge 14:39:50.220 --> 14:39:52.990 align:start position:0% okay the telecoms company will charge you<14:39:50.456> monthly<14:39:50.880> for<14:39:51.660> use<14:39:51.840> of<14:39:52.020> the<14:39:52.140> lease<14:39:52.380> line 14:39:52.990 --> 14:39:53.000 align:start position:0% you monthly for use of the lease line 14:39:53.000 --> 14:39:56.150 align:start position:0% you monthly for use of the lease line fee<14:39:54.000> varies<14:39:54.540> based<14:39:54.900> upon<14:39:55.140> the<14:39:55.436> distant<14:39:55.860> speed 14:39:56.150 --> 14:39:56.160 align:start position:0% fee varies based upon the distant speed 14:39:56.160 --> 14:39:58.426 align:start position:0% fee varies based upon the distant speed of<14:39:56.400> the<14:39:56.520> connection<14:39:56.776> also<14:39:57.776> where<14:39:58.020> you<14:39:58.140> are<14:39:58.256> in 14:39:58.426 --> 14:39:58.436 align:start position:0% of the connection also where you are in 14:39:58.436 --> 14:39:59.446 align:start position:0% of the connection also where you are in the<14:39:58.616> world 14:39:59.446 --> 14:39:59.456 align:start position:0% the world 14:39:59.456 --> 14:40:01.246 align:start position:0% the world um<14:39:59.580> some<14:39:59.880> places<14:40:00.060> the<14:40:00.416> Technologies<14:40:00.956> still 14:40:01.246 --> 14:40:01.256 align:start position:0% um some places the Technologies still 14:40:01.256 --> 14:40:02.510 align:start position:0% um some places the Technologies still emerging 14:40:02.510 --> 14:40:02.520 align:start position:0% emerging 14:40:02.520 --> 14:40:06.050 align:start position:0% emerging some<14:40:03.240> places<14:40:03.416> still<14:40:03.720> established 14:40:06.050 --> 14:40:06.060 align:start position:0% some places still established 14:40:06.060 --> 14:40:08.510 align:start position:0% some places still established so<14:40:06.596> level<14:40:06.840> level<14:40:06.956> of<14:40:07.500> quality<14:40:07.860> is<14:40:08.040> assured 14:40:08.510 --> 14:40:08.520 align:start position:0% so level level of quality is assured 14:40:08.520 --> 14:40:10.070 align:start position:0% so level level of quality is assured it's<14:40:08.700> not<14:40:08.880> as<14:40:09.000> if<14:40:09.116> you<14:40:09.300> can<14:40:09.480> use<14:40:09.720> more 14:40:10.070 --> 14:40:10.080 align:start position:0% it's not as if you can use more 14:40:10.080 --> 14:40:11.746 align:start position:0% it's not as if you can use more bandwidth<14:40:10.680> at<14:40:10.800> certain<14:40:11.040> times<14:40:11.220> of<14:40:11.456> the<14:40:11.580> day 14:40:11.746 --> 14:40:11.756 align:start position:0% bandwidth at certain times of the day 14:40:11.756 --> 14:40:15.350 align:start position:0% bandwidth at certain times of the day like<14:40:12.000> frame<14:40:12.416> relay<14:40:12.776> and<14:40:13.500> lesser<14:40:13.860> others 14:40:15.350 --> 14:40:15.360 align:start position:0% like frame relay and lesser others 14:40:15.360 --> 14:40:18.650 align:start position:0% like frame relay and lesser others uh<14:40:16.080> quite<14:40:16.380> uh<14:40:16.860> old<14:40:17.220> technology<14:40:17.700> still<14:40:18.116> in 14:40:18.650 --> 14:40:18.660 align:start position:0% uh quite uh old technology still in 14:40:18.660 --> 14:40:21.230 align:start position:0% uh quite uh old technology still in quite<14:40:19.200> prominent<14:40:19.616> use<14:40:19.916> but<14:40:20.400> the<14:40:21.000> technology 14:40:21.230 --> 14:40:21.240 align:start position:0% quite prominent use but the technology 14:40:21.240 --> 14:40:23.390 align:start position:0% quite prominent use but the technology is<14:40:21.416> quite<14:40:21.720> old<14:40:21.956> originally<14:40:22.916> used<14:40:23.096> to<14:40:23.276> connect 14:40:23.390 --> 14:40:23.400 align:start position:0% is quite old originally used to connect 14:40:23.400 --> 14:40:26.570 align:start position:0% is quite old originally used to connect your<14:40:23.700> mainframes<14:40:24.360> to<14:40:25.080> remote<14:40:25.320> sites 14:40:26.570 --> 14:40:26.580 align:start position:0% your mainframes to remote sites 14:40:26.580 --> 14:40:28.370 align:start position:0% your mainframes to remote sites so<14:40:26.880> a<14:40:27.000> few<14:40:27.116> examples<14:40:27.540> that<14:40:27.776> they<14:40:27.956> mentioned<14:40:28.256> in 14:40:28.370 --> 14:40:28.380 align:start position:0% so a few examples that they mentioned in 14:40:28.380 --> 14:40:31.310 align:start position:0% so a few examples that they mentioned in the<14:40:28.500> syllabus<14:40:28.860> the<14:40:29.160> T<14:40:29.400> carrier<14:40:29.936> and<14:40:30.540> e-carrier 14:40:31.310 --> 14:40:31.320 align:start position:0% the syllabus the T carrier and e-carrier 14:40:31.320 --> 14:40:34.310 align:start position:0% the syllabus the T carrier and e-carrier T<14:40:31.860> carrier<14:40:32.400> one<14:40:32.580> e<14:40:32.880> carrier<14:40:33.240> one<14:40:33.416> and<14:40:33.776> then<14:40:33.900> T3 14:40:34.310 --> 14:40:34.320 align:start position:0% T carrier one e carrier one and then T3 14:40:34.320 --> 14:40:36.530 align:start position:0% T carrier one e carrier one and then T3 and<14:40:34.680> E3 14:40:36.530 --> 14:40:36.540 align:start position:0% and E3 14:40:36.540 --> 14:40:39.890 align:start position:0% and E3 the<14:40:37.256> T1<14:40:37.616> transmission<14:40:37.916> system<14:40:38.900> originally 14:40:39.890 --> 14:40:39.900 align:start position:0% the T1 transmission system originally 14:40:39.900 --> 14:40:43.970 align:start position:0% the T1 transmission system originally developed<14:40:40.320> by<14:40:40.500> a<14:40:40.800> t 14:40:43.970 --> 14:40:43.980 align:start position:0% 14:40:43.980 --> 14:40:47.690 align:start position:0% 1<14:40:44.700> induced<14:40:45.416> introduced<14:40:45.900> back<14:40:46.080> in<14:40:46.700> 1961. 14:40:47.690 --> 14:40:47.700 align:start position:0% 1 induced introduced back in 1961. 14:40:47.700 --> 14:40:50.926 align:start position:0% 1 induced introduced back in 1961. originally<14:40:48.660> uh<14:40:49.256> developed<14:40:49.740> to<14:40:49.860> to<14:40:50.220> transmit 14:40:50.926 --> 14:40:50.936 align:start position:0% originally uh developed to to transmit 14:40:50.936 --> 14:40:54.470 align:start position:0% originally uh developed to to transmit 24<14:40:51.240> phone<14:40:51.776> signals<14:40:52.560> at<14:40:52.740> the<14:40:52.860> same<14:40:53.040> time<14:40:53.480> over 14:40:54.470 --> 14:40:54.480 align:start position:0% 24 phone signals at the same time over 14:40:54.480 --> 14:40:58.190 align:start position:0% 24 phone signals at the same time over uh<14:40:55.200> the<14:40:55.640> copper<14:40:56.640> wire 14:40:58.190 --> 14:40:58.200 align:start position:0% uh the copper wire 14:40:58.200 --> 14:41:00.290 align:start position:0% uh the copper wire he<14:40:58.680> uses<14:40:58.980> something<14:40:59.160> called<14:40:59.400> TDM<14:41:00.000> time 14:41:00.290 --> 14:41:00.300 align:start position:0% he uses something called TDM time 14:41:00.300 --> 14:41:02.926 align:start position:0% he uses something called TDM time divisional<14:41:00.956> multiplexing<14:41:01.800> this<14:41:02.400> mixes<14:41:02.756> up 14:41:02.926 --> 14:41:02.936 align:start position:0% divisional multiplexing this mixes up 14:41:02.936 --> 14:41:05.630 align:start position:0% divisional multiplexing this mixes up the<14:41:03.116> signal<14:41:03.480> in<14:41:04.200> order<14:41:04.320> to<14:41:04.500> use 14:41:05.630 --> 14:41:05.640 align:start position:0% the signal in order to use 14:41:05.640 --> 14:41:07.130 align:start position:0% the signal in order to use um<14:41:05.700> multiple<14:41:06.116> signals<14:41:06.596> over<14:41:06.720> the<14:41:06.956> same 14:41:07.130 --> 14:41:07.140 align:start position:0% um multiple signals over the same 14:41:07.140 --> 14:41:08.570 align:start position:0% um multiple signals over the same physical<14:41:07.380> link 14:41:08.570 --> 14:41:08.580 align:start position:0% physical link 14:41:08.580 --> 14:41:10.670 align:start position:0% physical link I<14:41:09.060> don't<14:41:09.240> think<14:41:09.360> they<14:41:09.540> go<14:41:09.660> into<14:41:09.776> any<14:41:10.020> detail<14:41:10.436> on 14:41:10.670 --> 14:41:10.680 align:start position:0% I don't think they go into any detail on 14:41:10.680 --> 14:41:15.050 align:start position:0% I don't think they go into any detail on TDM<14:41:11.640> in<14:41:11.936> the<14:41:12.180> exam<14:41:13.140> there 14:41:15.050 --> 14:41:15.060 align:start position:0% TDM in the exam there 14:41:15.060 --> 14:41:18.890 align:start position:0% TDM in the exam there so<14:41:15.660> T1<14:41:16.200> will<14:41:16.500> give<14:41:16.680> you<14:41:16.800> a<14:41:16.860> bandwidth<14:41:17.456> of<14:41:17.900> 1.544 14:41:18.890 --> 14:41:18.900 align:start position:0% so T1 will give you a bandwidth of 1.544 14:41:18.900 --> 14:41:22.370 align:start position:0% so T1 will give you a bandwidth of 1.544 Meg<14:41:19.936> upstream<14:41:20.936> and<14:41:21.116> downstream<14:41:21.900> so 14:41:22.370 --> 14:41:22.380 align:start position:0% Meg upstream and downstream so 14:41:22.380 --> 14:41:25.370 align:start position:0% Meg upstream and downstream so synchronous<14:41:23.240> T1<14:41:24.240> system<14:41:24.596> is<14:41:24.840> used<14:41:25.020> in<14:41:25.200> America 14:41:25.370 --> 14:41:25.380 align:start position:0% synchronous T1 system is used in America 14:41:25.380 --> 14:41:28.490 align:start position:0% synchronous T1 system is used in America Japan<14:41:25.800> and<14:41:26.160> South<14:41:26.340> Korea<14:41:26.820> e<14:41:27.416> the<14:41:27.840> e-system<14:41:28.256> is 14:41:28.490 --> 14:41:28.500 align:start position:0% Japan and South Korea e the e-system is 14:41:28.500 --> 14:41:31.970 align:start position:0% Japan and South Korea e the e-system is generally<14:41:28.860> used<14:41:29.096> in<14:41:29.400> Europe 14:41:31.970 --> 14:41:31.980 align:start position:0% 14:41:31.980 --> 14:41:34.550 align:start position:0% the<14:41:32.456> bandwidth<14:41:33.000> level<14:41:33.116> of<14:41:33.360> T1<14:41:33.660> was<14:41:34.080> originally 14:41:34.550 --> 14:41:34.560 align:start position:0% the bandwidth level of T1 was originally 14:41:34.560 --> 14:41:38.810 align:start position:0% the bandwidth level of T1 was originally called<14:41:35.096> the<14:41:35.580> digital<14:41:36.116> signal<14:41:36.540> level<14:41:36.720> 1<14:41:37.080> or<14:41:37.380> DS1 14:41:38.810 --> 14:41:38.820 align:start position:0% called the digital signal level 1 or DS1 14:41:38.820 --> 14:41:41.210 align:start position:0% called the digital signal level 1 or DS1 I<14:41:39.300> mentioned<14:41:39.596> before<14:41:39.776> the<14:41:40.020> T1<14:41:40.320> line<14:41:40.616> has<14:41:40.916> 24 14:41:41.210 --> 14:41:41.220 align:start position:0% I mentioned before the T1 line has 24 14:41:41.220 --> 14:41:45.830 align:start position:0% I mentioned before the T1 line has 24 channels<14:41:41.936> each<14:41:42.540> channel<14:41:42.720> is<14:41:42.900> called<14:41:43.080> a<14:41:43.320> ds0 14:41:45.830 --> 14:41:45.840 align:start position:0% channels each channel is called a ds0 14:41:45.840 --> 14:41:48.530 align:start position:0% channels each channel is called a ds0 and<14:41:46.256> you<14:41:46.436> could<14:41:46.560> have<14:41:46.740> one<14:41:47.220> two<14:41:47.640> three<14:41:48.000> of 14:41:48.530 --> 14:41:48.540 align:start position:0% and you could have one two three of 14:41:48.540 --> 14:41:50.210 align:start position:0% and you could have one two three of these<14:41:48.720> channels<14:41:49.080> or<14:41:49.380> all<14:41:49.616> of<14:41:49.800> the<14:41:49.860> channels 14:41:50.210 --> 14:41:50.220 align:start position:0% these channels or all of the channels 14:41:50.220 --> 14:41:52.130 align:start position:0% these channels or all of the channels depending<14:41:50.640> on<14:41:50.756> how<14:41:51.540> much<14:41:51.596> you<14:41:51.776> want<14:41:51.900> to<14:41:52.080> pay 14:41:52.130 --> 14:41:52.140 align:start position:0% depending on how much you want to pay 14:41:52.140 --> 14:41:54.050 align:start position:0% depending on how much you want to pay and<14:41:52.320> how<14:41:52.500> much<14:41:52.560> bandwidth<14:41:52.980> you<14:41:53.220> need 14:41:54.050 --> 14:41:54.060 align:start position:0% and how much bandwidth you need 14:41:54.060 --> 14:41:56.570 align:start position:0% and how much bandwidth you need each<14:41:54.480> channel<14:41:54.720> is<14:41:54.956> capable<14:41:55.436> of<14:41:55.680> transmitting 14:41:56.570 --> 14:41:56.580 align:start position:0% each channel is capable of transmitting 14:41:56.580 --> 14:42:01.490 align:start position:0% each channel is capable of transmitting data<14:41:56.880> at<14:41:57.000> up<14:41:57.180> to<14:41:57.360> 64k 14:42:01.490 --> 14:42:01.500 align:start position:0% 14:42:01.500 --> 14:42:04.070 align:start position:0% uh<14:42:02.040> lease<14:42:02.400> line<14:42:02.580> T1<14:42:03.060> multiple<14:42:03.660> channels 14:42:04.070 --> 14:42:04.080 align:start position:0% uh lease line T1 multiple channels 14:42:04.080 --> 14:42:06.710 align:start position:0% uh lease line T1 multiple channels provide<14:42:04.380> flexibility<14:42:05.180> so<14:42:06.180> I've<14:42:06.300> said<14:42:06.540> you 14:42:06.710 --> 14:42:06.720 align:start position:0% provide flexibility so I've said you 14:42:06.720 --> 14:42:08.210 align:start position:0% provide flexibility so I've said you could<14:42:06.840> already<14:42:06.956> choose<14:42:07.380> some<14:42:07.616> channels<14:42:08.040> or 14:42:08.210 --> 14:42:08.220 align:start position:0% could already choose some channels or 14:42:08.220 --> 14:42:11.570 align:start position:0% could already choose some channels or all<14:42:08.456> the<14:42:08.640> channels<14:42:09.200> E1<14:42:10.200> is<14:42:10.740> the<14:42:11.160> European 14:42:11.570 --> 14:42:11.580 align:start position:0% all the channels E1 is the European 14:42:11.580 --> 14:42:14.530 align:start position:0% all the channels E1 is the European version<14:42:11.936> of<14:42:12.540> T1<14:42:13.200> however<14:42:13.680> because<14:42:13.916> of<14:42:14.220> the 14:42:14.530 --> 14:42:14.540 align:start position:0% version of T1 however because of the 14:42:14.540 --> 14:42:17.030 align:start position:0% version of T1 however because of the infrastructure<14:42:15.540> that<14:42:16.256> was<14:42:16.380> in<14:42:16.500> place<14:42:16.680> at<14:42:16.860> the 14:42:17.030 --> 14:42:17.040 align:start position:0% infrastructure that was in place at the 14:42:17.040 --> 14:42:19.746 align:start position:0% infrastructure that was in place at the time<14:42:17.160> you<14:42:17.400> could<14:42:17.520> get<14:42:17.700> up<14:42:17.880> to<14:42:18.180> two<14:42:18.596> Meg 14:42:19.746 --> 14:42:19.756 align:start position:0% time you could get up to two Meg 14:42:19.756 --> 14:42:22.190 align:start position:0% time you could get up to two Meg 2.048<14:42:20.756> mag 14:42:22.190 --> 14:42:22.200 align:start position:0% 2.048 mag 14:42:22.200 --> 14:42:24.946 align:start position:0% 2.048 mag this<14:42:22.860> has<14:42:23.040> 32<14:42:23.520> channels<14:42:24.000> in<14:42:24.240> each<14:42:24.360> Channel's 14:42:24.946 --> 14:42:24.956 align:start position:0% this has 32 channels in each Channel's 14:42:24.956 --> 14:42:27.890 align:start position:0% this has 32 channels in each Channel's capable<14:42:25.740> of<14:42:25.916> transmitting<14:42:26.520> data<14:42:26.880> up<14:42:27.000> to<14:42:27.116> 64k 14:42:27.890 --> 14:42:27.900 align:start position:0% capable of transmitting data up to 64k 14:42:27.900 --> 14:42:30.106 align:start position:0% capable of transmitting data up to 64k you<14:42:28.800> can<14:42:28.980> add<14:42:29.096> them<14:42:29.340> all<14:42:29.456> up<14:42:29.640> and<14:42:29.820> then<14:42:29.936> there's 14:42:30.106 --> 14:42:30.116 align:start position:0% you can add them all up and then there's 14:42:30.116 --> 14:42:33.710 align:start position:0% you can add them all up and then there's a<14:42:30.720> um<14:42:30.720> a<14:42:31.256> signaling<14:42:31.740> Channel<14:42:31.980> also 14:42:33.710 --> 14:42:33.720 align:start position:0% a um a signaling Channel also 14:42:33.720 --> 14:42:37.730 align:start position:0% a um a signaling Channel also T3<14:42:34.436> is<14:42:35.096> equivalent<14:42:35.820> to<14:42:36.000> bundling<14:42:36.416> together<14:42:36.740> 28 14:42:37.730 --> 14:42:37.740 align:start position:0% T3 is equivalent to bundling together 28 14:42:37.740 --> 14:42:40.670 align:start position:0% T3 is equivalent to bundling together 28 T1<14:42:38.400> line<14:42:38.700> so<14:42:38.936> much<14:42:39.300> faster 14:42:40.670 --> 14:42:40.680 align:start position:0% T1 line so much faster 14:42:40.680 --> 14:42:43.906 align:start position:0% T1 line so much faster also<14:42:41.276> referred<14:42:41.520> to<14:42:41.640> as<14:42:41.820> DS3 14:42:43.906 --> 14:42:43.916 align:start position:0% also referred to as DS3 14:42:43.916 --> 14:42:47.510 align:start position:0% also referred to as DS3 since<14:42:44.520> there<14:42:44.880> are<14:42:45.060> 24<14:42:45.596> channels<14:42:46.256> the<14:42:46.916> T3<14:42:47.276> is 14:42:47.510 --> 14:42:47.520 align:start position:0% since there are 24 channels the T3 is 14:42:47.520 --> 14:42:52.426 align:start position:0% since there are 24 channels the T3 is capable<14:42:47.820> of<14:42:47.936> carrying<14:42:48.800> 672<14:42:49.936> T1<14:42:50.936> circuits<14:42:51.660> so 14:42:52.426 --> 14:42:52.436 align:start position:0% capable of carrying 672 T1 circuits so 14:42:52.436 --> 14:42:53.990 align:start position:0% capable of carrying 672 T1 circuits so multiple<14:42:52.916> companies<14:42:53.276> will<14:42:53.456> be<14:42:53.580> using<14:42:53.880> these 14:42:53.990 --> 14:42:54.000 align:start position:0% multiple companies will be using these 14:42:54.000 --> 14:42:58.970 align:start position:0% multiple companies will be using these it's<14:42:54.180> not<14:42:54.360> likely<14:42:54.660> that<14:42:54.776> B1<14:42:55.256> companies 14:42:58.970 --> 14:42:58.980 align:start position:0% 14:42:58.980 --> 14:43:01.210 align:start position:0% so<14:42:59.520> you<14:42:59.700> get<14:42:59.820> up<14:43:00.060> to 14:43:01.210 --> 14:43:01.220 align:start position:0% so you get up to 14:43:01.220 --> 14:43:03.946 align:start position:0% so you get up to 44.736<14:43:02.220> megabits<14:43:02.880> per<14:43:03.000> second<14:43:03.116> with<14:43:03.416> the<14:43:03.596> T3 14:43:03.946 --> 14:43:03.956 align:start position:0% 44.736 megabits per second with the T3 14:43:03.956 --> 14:43:07.190 align:start position:0% 44.736 megabits per second with the T3 lease<14:43:04.380> line<14:43:04.560> if<14:43:04.860> you<14:43:04.980> add<14:43:05.096> the<14:43:05.276> whole<14:43:05.400> line 14:43:07.190 --> 14:43:07.200 align:start position:0% lease line if you add the whole line 14:43:07.200 --> 14:43:09.946 align:start position:0% lease line if you add the whole line 30<14:43:07.680> times<14:43:07.980> faster<14:43:08.400> than<14:43:08.700> T1 14:43:09.946 --> 14:43:09.956 align:start position:0% 30 times faster than T1 14:43:09.956 --> 14:43:13.190 align:start position:0% 30 times faster than T1 E1<14:43:10.616> is<14:43:10.860> the<14:43:11.040> equivalent<14:43:11.456> to<14:43:11.640> 16<14:43:12.000> or<14:43:12.596> E3<14:43:12.956> sorry 14:43:13.190 --> 14:43:13.200 align:start position:0% E1 is the equivalent to 16 or E3 sorry 14:43:13.200 --> 14:43:16.570 align:start position:0% E1 is the equivalent to 16 or E3 sorry equivalent<14:43:13.800> to<14:43:13.980> 16<14:43:14.400> E1<14:43:15.360> lines 14:43:16.570 --> 14:43:16.580 align:start position:0% equivalent to 16 E1 lines 14:43:16.580 --> 14:43:20.990 align:start position:0% equivalent to 16 E1 lines 512<14:43:17.580> E1<14:43:18.060> channels<14:43:18.660> so<14:43:19.080> you<14:43:19.256> get<14:43:19.320> up<14:43:19.500> to<14:43:20.000> 34.4 14:43:20.990 --> 14:43:21.000 align:start position:0% 512 E1 channels so you get up to 34.4 14:43:21.000 --> 14:43:23.390 align:start position:0% 512 E1 channels so you get up to 34.4 mag<14:43:21.300> there 14:43:23.390 --> 14:43:23.400 align:start position:0% mag there 14:43:23.400 --> 14:43:27.350 align:start position:0% mag there so<14:43:23.820> T3<14:43:24.300> has<14:43:24.660> more<14:43:24.840> bandwidth<14:43:25.256> than<14:43:25.500> E3 14:43:27.350 --> 14:43:27.360 align:start position:0% so T3 has more bandwidth than E3 14:43:27.360 --> 14:43:29.570 align:start position:0% so T3 has more bandwidth than E3 sonnet<14:43:28.256> I<14:43:28.500> think<14:43:28.616> is<14:43:28.800> mentioned<14:43:29.276> in<14:43:29.400> the 14:43:29.570 --> 14:43:29.580 align:start position:0% sonnet I think is mentioned in the 14:43:29.580 --> 14:43:31.446 align:start position:0% sonnet I think is mentioned in the syllabus<14:43:29.936> which<14:43:30.116> is<14:43:30.240> why<14:43:30.416> we've<14:43:30.660> got<14:43:30.840> it<14:43:31.020> here 14:43:31.446 --> 14:43:31.456 align:start position:0% syllabus which is why we've got it here 14:43:31.456 --> 14:43:34.426 align:start position:0% syllabus which is why we've got it here synchronous<14:43:32.456> Optical<14:43:32.820> networking<14:43:33.660> this<14:43:34.320> can 14:43:34.426 --> 14:43:34.436 align:start position:0% synchronous Optical networking this can 14:43:34.436 --> 14:43:36.406 align:start position:0% synchronous Optical networking this can be<14:43:34.616> used<14:43:34.740> as<14:43:34.916> lease<14:43:35.276> lines<14:43:35.456> also<14:43:35.820> but<14:43:36.060> it<14:43:36.180> uses 14:43:36.406 --> 14:43:36.416 align:start position:0% be used as lease lines also but it uses 14:43:36.416 --> 14:43:38.926 align:start position:0% be used as lease lines also but it uses fiber<14:43:36.900> cabling<14:43:37.320> instead<14:43:37.916> of<14:43:37.980> copper 14:43:38.926 --> 14:43:38.936 align:start position:0% fiber cabling instead of copper 14:43:38.936 --> 14:43:40.906 align:start position:0% fiber cabling instead of copper you<14:43:39.480> get<14:43:39.840> um<14:43:39.840> higher<14:43:40.256> bandwidth<14:43:40.680> for<14:43:40.800> that 14:43:40.906 --> 14:43:40.916 align:start position:0% you get um higher bandwidth for that 14:43:40.916 --> 14:43:44.810 align:start position:0% you get um higher bandwidth for that obviously<14:43:41.220> because<14:43:41.340> it's<14:43:41.580> using<14:43:41.880> fiber<14:43:42.300> optic 14:43:44.810 --> 14:43:44.820 align:start position:0% 14:43:44.820 --> 14:43:47.330 align:start position:0% um<14:43:44.936> the<14:43:45.776> transmission<14:43:46.140> of<14:43:46.560> solid<14:43:46.916> fiber 14:43:47.330 --> 14:43:47.340 align:start position:0% um the transmission of solid fiber 14:43:47.340 --> 14:43:49.970 align:start position:0% um the transmission of solid fiber networks<14:43:47.880> is<14:43:48.116> specified<14:43:48.720> as<14:43:49.020> Optical<14:43:49.380> carrier 14:43:49.970 --> 14:43:49.980 align:start position:0% networks is specified as Optical carrier 14:43:49.980 --> 14:43:53.746 align:start position:0% networks is specified as Optical carrier or<14:43:50.400> OC<14:43:50.936> transmission<14:43:51.776> rates 14:43:53.746 --> 14:43:53.756 align:start position:0% or OC transmission rates 14:43:53.756 --> 14:43:56.746 align:start position:0% or OC transmission rates oc1<14:43:54.720> is<14:43:55.080> a<14:43:55.200> transmission<14:43:55.380> line<14:43:55.860> with<14:43:56.400> speeds 14:43:56.746 --> 14:43:56.756 align:start position:0% oc1 is a transmission line with speeds 14:43:56.756 --> 14:43:59.350 align:start position:0% oc1 is a transmission line with speeds of<14:43:56.820> up<14:43:56.936> to<14:43:57.320> 51.84<14:43:58.320> Meg 14:43:59.350 --> 14:43:59.360 align:start position:0% of up to 51.84 Meg 14:43:59.360 --> 14:44:03.650 align:start position:0% of up to 51.84 Meg oc3<14:44:00.360> you<14:44:00.660> get<14:44:00.776> up<14:44:00.900> to<14:44:01.080> 155.52 14:44:03.650 --> 14:44:03.660 align:start position:0% oc3 you get up to 155.52 14:44:03.660 --> 14:44:06.970 align:start position:0% oc3 you get up to 155.52 and<14:44:04.080> then<14:44:04.200> OC<14:44:04.560> 12<14:44:04.800> you<14:44:05.160> get<14:44:05.340> up<14:44:05.456> to<14:44:05.900> 622 14:44:06.970 --> 14:44:06.980 align:start position:0% and then OC 12 you get up to 622 14:44:06.980 --> 14:44:11.266 align:start position:0% and then OC 12 you get up to 622 megabits<14:44:07.980> per<14:44:08.096> second 14:44:11.266 --> 14:44:11.276 align:start position:0% 14:44:11.276 --> 14:44:13.790 align:start position:0% uh<14:44:11.880> the<14:44:12.116> oc-12<14:44:12.660> is<14:44:12.900> typically<14:44:13.140> used<14:44:13.380> by<14:44:13.616> your 14:44:13.790 --> 14:44:13.800 align:start position:0% uh the oc-12 is typically used by your 14:44:13.800 --> 14:44:16.010 align:start position:0% uh the oc-12 is typically used by your isps<14:44:14.400> as<14:44:14.756> a<14:44:15.000> wide<14:44:15.116> area<14:44:15.300> connection<14:44:15.660> you 14:44:16.010 --> 14:44:16.020 align:start position:0% isps as a wide area connection you 14:44:16.020 --> 14:44:17.630 align:start position:0% isps as a wide area connection you wouldn't<14:44:16.140> be<14:44:16.320> using<14:44:16.560> it<14:44:16.680> in<14:44:16.860> a 14:44:17.630 --> 14:44:17.640 align:start position:0% wouldn't be using it in a 14:44:17.640 --> 14:44:20.330 align:start position:0% wouldn't be using it in a and<14:44:18.240> small<14:44:18.596> company<14:44:18.900> for<14:44:19.616> sure 14:44:20.330 --> 14:44:20.340 align:start position:0% and small company for sure 14:44:20.340 --> 14:44:24.406 align:start position:0% and small company for sure so<14:44:20.700> we've<14:44:20.820> looked<14:44:21.116> at<14:44:21.180> T1<14:44:21.660> E1<14:44:22.436> T1<14:44:23.160> T3<14:44:23.880> and<14:44:24.060> E3 14:44:24.406 --> 14:44:24.416 align:start position:0% so we've looked at T1 E1 T1 T3 and E3 14:44:24.416 --> 14:44:27.290 align:start position:0% so we've looked at T1 E1 T1 T3 and E3 and<14:44:25.140> also<14:44:25.380> solid<14:44:25.800> networking 14:44:27.290 --> 14:44:27.300 align:start position:0% and also solid networking 14:44:27.300 --> 14:44:33.790 align:start position:0% and also solid networking thanks<14:44:27.776> for<14:44:27.956> watching 14:44:33.790 --> 14:44:33.800 align:start position:0% 14:44:33.800 --> 14:44:41.570 align:start position:0% [Music] 14:44:41.570 --> 14:44:41.580 align:start position:0% [Music] 14:44:41.580 --> 14:44:50.106 align:start position:0% [Music] foreign 14:44:50.106 --> 14:44:50.116 align:start position:0% 14:44:50.116 --> 14:44:53.926 align:start position:0% module<14:44:51.116> 9<14:44:51.300> lesson<14:44:51.776> 2B<14:44:52.520> wavelength<14:44:53.520> division 14:44:53.926 --> 14:44:53.936 align:start position:0% module 9 lesson 2B wavelength division 14:44:53.936 --> 14:44:57.050 align:start position:0% module 9 lesson 2B wavelength division multiplexing<14:44:54.900> bit<14:44:55.560> of<14:44:55.680> a<14:44:55.800> mouthful<14:44:56.160> but<14:44:56.880> it's 14:44:57.050 --> 14:44:57.060 align:start position:0% multiplexing bit of a mouthful but it's 14:44:57.060 --> 14:44:58.426 align:start position:0% multiplexing bit of a mouthful but it's a<14:44:57.300> new<14:44:57.900> um 14:44:58.426 --> 14:44:58.436 align:start position:0% a new um 14:44:58.436 --> 14:45:00.890 align:start position:0% a new um objective<14:44:59.160> in<14:44:59.276> the<14:44:59.456> network<14:44:59.520> plus<14:44:59.880> exam 14:45:00.890 --> 14:45:00.900 align:start position:0% objective in the network plus exam 14:45:00.900 --> 14:45:04.970 align:start position:0% objective in the network plus exam we'll<14:45:01.256> look<14:45:01.436> at<14:45:01.560> what<14:45:01.740> is<14:45:01.916> a<14:45:02.096> wdm 14:45:04.970 --> 14:45:04.980 align:start position:0% 14:45:04.980 --> 14:45:08.746 align:start position:0% that<14:45:05.276> he<14:45:05.456> said<14:45:05.580> wmd<14:45:06.500> wdm<14:45:07.500> system<14:45:07.860> course 14:45:08.746 --> 14:45:08.756 align:start position:0% that he said wmd wdm system course 14:45:08.756 --> 14:45:12.830 align:start position:0% that he said wmd wdm system course length<14:45:09.300> division<14:45:09.900> multiplexing<14:45:10.820> cwdm<14:45:11.840> again 14:45:12.830 --> 14:45:12.840 align:start position:0% length division multiplexing cwdm again 14:45:12.840 --> 14:45:15.350 align:start position:0% length division multiplexing cwdm again we<14:45:13.140> love<14:45:13.200> our<14:45:13.436> abbreviations<14:45:14.040> here<14:45:14.400> a<14:45:15.060> dense 14:45:15.350 --> 14:45:15.360 align:start position:0% we love our abbreviations here a dense 14:45:15.360 --> 14:45:19.970 align:start position:0% we love our abbreviations here a dense wavelength<14:45:16.020> division<14:45:16.380> multiplexing 14:45:19.970 --> 14:45:19.980 align:start position:0% 14:45:19.980 --> 14:45:23.266 align:start position:0% so<14:45:20.580> what<14:45:20.880> is<14:45:21.000> it<14:45:21.180> basically<14:45:21.956> the<14:45:22.560> idea<14:45:22.800> is<14:45:23.040> to 14:45:23.266 --> 14:45:23.276 align:start position:0% so what is it basically the idea is to 14:45:23.276 --> 14:45:26.690 align:start position:0% so what is it basically the idea is to get<14:45:23.520> the<14:45:24.240> most<14:45:24.480> you<14:45:25.200> can<14:45:25.380> out<14:45:26.096> of<14:45:26.220> what<14:45:26.456> you've 14:45:26.690 --> 14:45:26.700 align:start position:0% get the most you can out of what you've 14:45:26.700 --> 14:45:28.790 align:start position:0% get the most you can out of what you've got<14:45:26.880> and<14:45:27.660> this 14:45:28.790 --> 14:45:28.800 align:start position:0% got and this 14:45:28.800 --> 14:45:31.010 align:start position:0% got and this um<14:45:28.860> instance<14:45:29.340> what<14:45:29.756> we've<14:45:30.000> got<14:45:30.180> is<14:45:30.480> a<14:45:30.720> single 14:45:31.010 --> 14:45:31.020 align:start position:0% um instance what we've got is a single 14:45:31.020 --> 14:45:33.830 align:start position:0% um instance what we've got is a single optical<14:45:31.380> fiber<14:45:32.040> and<14:45:32.700> what<14:45:32.936> we<14:45:33.116> need<14:45:33.300> to<14:45:33.480> do<14:45:33.596> is 14:45:33.830 --> 14:45:33.840 align:start position:0% optical fiber and what we need to do is 14:45:33.840 --> 14:45:37.550 align:start position:0% optical fiber and what we need to do is is<14:45:34.140> get<14:45:35.096> as<14:45:35.340> many<14:45:35.580> signals<14:45:36.300> to<14:45:37.080> cross<14:45:37.256> this 14:45:37.550 --> 14:45:37.560 align:start position:0% is get as many signals to cross this 14:45:37.560 --> 14:45:41.030 align:start position:0% is get as many signals to cross this fiber<14:45:38.040> at<14:45:38.936> the<14:45:39.060> same<14:45:39.240> time<14:45:39.480> as<14:45:39.840> possible<14:45:40.256> if 14:45:41.030 --> 14:45:41.040 align:start position:0% fiber at the same time as possible if 14:45:41.040 --> 14:45:44.210 align:start position:0% fiber at the same time as possible if you<14:45:41.160> just<14:45:41.276> had<14:45:41.400> one<14:45:41.640> signal<14:45:42.000> pass<14:45:42.660> in<14:45:42.776> then 14:45:44.210 --> 14:45:44.220 align:start position:0% you just had one signal pass in then 14:45:44.220 --> 14:45:46.010 align:start position:0% you just had one signal pass in then um<14:45:44.340> so<14:45:44.880> the<14:45:45.180> internet<14:45:45.240> would<14:45:45.480> grow<14:45:45.660> into<14:45:45.776> a 14:45:46.010 --> 14:45:46.020 align:start position:0% um so the internet would grow into a 14:45:46.020 --> 14:45:48.650 align:start position:0% um so the internet would grow into a whole<14:45:46.080> basically<14:45:46.560> it<14:45:47.456> allows<14:45:47.820> bi-directional 14:45:48.650 --> 14:45:48.660 align:start position:0% whole basically it allows bi-directional 14:45:48.660 --> 14:45:51.106 align:start position:0% whole basically it allows bi-directional Communications<14:45:49.200> over<14:45:49.560> a<14:45:49.860> single<14:45:50.096> fiber<14:45:50.520> so 14:45:51.106 --> 14:45:51.116 align:start position:0% Communications over a single fiber so 14:45:51.116 --> 14:45:53.330 align:start position:0% Communications over a single fiber so two<14:45:51.480> directions 14:45:53.330 --> 14:45:53.340 align:start position:0% two directions 14:45:53.340 --> 14:45:58.310 align:start position:0% two directions uh<14:45:53.936> wdm<14:45:54.720> uses<14:45:55.436> a<14:45:56.240> multiplexer<14:45:57.240> which<14:45:57.900> is<14:45:58.320> um 14:45:58.310 --> 14:45:58.320 align:start position:0% uh wdm uses a multiplexer which is um 14:45:58.320 --> 14:45:59.926 align:start position:0% uh wdm uses a multiplexer which is um you'll<14:45:58.680> often<14:45:58.916> see<14:45:59.040> it<14:45:59.220> referred<14:45:59.580> to<14:45:59.756> in 14:45:59.926 --> 14:45:59.936 align:start position:0% you'll often see it referred to in 14:45:59.936 --> 14:46:03.470 align:start position:0% you'll often see it referred to in diagrams<14:46:00.540> as<14:46:00.776> mux<14:46:01.500> mux<14:46:02.220> and<14:46:03.000> then<14:46:03.116> a<14:46:03.300> d 14:46:03.470 --> 14:46:03.480 align:start position:0% diagrams as mux mux and then a d 14:46:03.480 --> 14:46:05.690 align:start position:0% diagrams as mux mux and then a d multiplexer<14:46:04.080> on<14:46:04.320> the<14:46:04.436> other<14:46:04.500> side<14:46:04.740> dmux 14:46:05.690 --> 14:46:05.700 align:start position:0% multiplexer on the other side dmux 14:46:05.700 --> 14:46:10.670 align:start position:0% multiplexer on the other side dmux d-e-m-u-x 14:46:10.670 --> 14:46:10.680 align:start position:0% 14:46:10.680 --> 14:46:14.150 align:start position:0% so<14:46:11.220> this<14:46:11.820> um<14:46:11.820> if<14:46:12.180> we<14:46:12.360> just<14:46:12.540> go<14:46:12.660> back<14:46:12.840> sorry<14:46:13.140> it 14:46:14.150 --> 14:46:14.160 align:start position:0% so this um if we just go back sorry it 14:46:14.160 --> 14:46:14.810 align:start position:0% so this um if we just go back sorry it um 14:46:14.810 --> 14:46:14.820 align:start position:0% um 14:46:14.820 --> 14:46:17.150 align:start position:0% um the<14:46:15.416> multiplexers<14:46:16.080> that<14:46:16.320> the<14:46:16.436> transmitter<14:46:16.860> to 14:46:17.150 --> 14:46:17.160 align:start position:0% the multiplexers that the transmitter to 14:46:17.160 --> 14:46:19.790 align:start position:0% the multiplexers that the transmitter to combine<14:46:17.520> multiple<14:46:17.900> obstacle<14:46:18.900> signals<14:46:19.436> of 14:46:19.790 --> 14:46:19.800 align:start position:0% combine multiple obstacle signals of 14:46:19.800 --> 14:46:21.830 align:start position:0% combine multiple obstacle signals of different<14:46:20.040> wavelengths<14:46:20.820> and<14:46:21.416> at<14:46:21.596> the<14:46:21.720> other 14:46:21.830 --> 14:46:21.840 align:start position:0% different wavelengths and at the other 14:46:21.840 --> 14:46:24.230 align:start position:0% different wavelengths and at the other side<14:46:22.020> this<14:46:22.320> needs<14:46:22.560> to<14:46:22.616> be<14:46:22.820> demultiplexed<14:46:23.820> back 14:46:24.230 --> 14:46:24.240 align:start position:0% side this needs to be demultiplexed back 14:46:24.240 --> 14:46:28.030 align:start position:0% side this needs to be demultiplexed back to<14:46:24.416> the<14:46:24.540> original<14:46:24.680> separate<14:46:25.680> signals 14:46:28.030 --> 14:46:28.040 align:start position:0% to the original separate signals 14:46:28.040 --> 14:46:30.710 align:start position:0% to the original separate signals wdm<14:46:29.040> systems<14:46:29.456> mostly<14:46:29.820> used<14:46:29.936> by<14:46:30.116> telecoms 14:46:30.710 --> 14:46:30.720 align:start position:0% wdm systems mostly used by telecoms 14:46:30.720 --> 14:46:32.446 align:start position:0% wdm systems mostly used by telecoms companies<14:46:31.020> because<14:46:31.256> of<14:46:31.500> the<14:46:31.616> capacity<14:46:32.040> of<14:46:32.400> the 14:46:32.446 --> 14:46:32.456 align:start position:0% companies because of the capacity of the 14:46:32.456 --> 14:46:35.690 align:start position:0% companies because of the capacity of the network<14:46:32.956> and<14:46:33.956> the<14:46:34.200> again<14:46:34.560> the<14:46:34.800> idea<14:46:35.096> is<14:46:35.340> and 14:46:35.690 --> 14:46:35.700 align:start position:0% network and the again the idea is and 14:46:35.700 --> 14:46:37.550 align:start position:0% network and the again the idea is and getting<14:46:36.000> more<14:46:36.300> out<14:46:36.540> of<14:46:36.720> less<14:46:36.900> so<14:46:37.140> they<14:46:37.380> can 14:46:37.550 --> 14:46:37.560 align:start position:0% getting more out of less so they can 14:46:37.560 --> 14:46:39.530 align:start position:0% getting more out of less so they can expand<14:46:38.096> the<14:46:38.276> network<14:46:38.400> without<14:46:38.820> having<14:46:39.116> to<14:46:39.360> lay 14:46:39.530 --> 14:46:39.540 align:start position:0% expand the network without having to lay 14:46:39.540 --> 14:46:42.050 align:start position:0% expand the network without having to lay more<14:46:40.320> fiber<14:46:40.800> optic<14:46:41.040> cables<14:46:41.456> which<14:46:41.700> obviously 14:46:42.050 --> 14:46:42.060 align:start position:0% more fiber optic cables which obviously 14:46:42.060 --> 14:46:46.606 align:start position:0% more fiber optic cables which obviously take<14:46:42.540> uh<14:46:43.140> takes<14:46:43.560> a<14:46:43.680> lot<14:46:43.740> of<14:46:43.916> time<14:46:44.276> and<14:46:44.640> money 14:46:46.606 --> 14:46:46.616 align:start position:0% take uh takes a lot of time and money 14:46:46.616 --> 14:46:50.570 align:start position:0% take uh takes a lot of time and money wdm<14:46:47.840> they're<14:46:48.840> divided<14:46:49.256> into<14:46:49.380> two<14:46:49.740> types<14:46:50.220> and 14:46:50.570 --> 14:46:50.580 align:start position:0% wdm they're divided into two types and 14:46:50.580 --> 14:46:51.946 align:start position:0% wdm they're divided into two types and these<14:46:50.820> are<14:46:50.880> based<14:46:51.180> on<14:46:51.300> the<14:46:51.416> wavelength 14:46:51.946 --> 14:46:51.956 align:start position:0% these are based on the wavelength 14:46:51.956 --> 14:46:55.070 align:start position:0% these are based on the wavelength patterns<14:46:52.320> that<14:46:52.500> are<14:46:52.616> used<14:46:52.800> CWD 14:46:55.070 --> 14:46:55.080 align:start position:0% patterns that are used CWD 14:46:55.080 --> 14:46:58.790 align:start position:0% patterns that are used CWD um<14:46:55.200> and<14:46:55.616> DWD<14:46:56.880> um 14:46:58.790 --> 14:46:58.800 align:start position:0% um and DWD um 14:46:58.800 --> 14:47:02.510 align:start position:0% um and DWD um wavelength<14:46:59.700> division<14:47:00.000> multiplexing<14:47:00.840> through 14:47:02.510 --> 14:47:02.520 align:start position:0% wavelength division multiplexing through 14:47:02.520 --> 14:47:06.530 align:start position:0% wavelength division multiplexing through um<14:47:02.776> dwdm<14:47:03.776> and<14:47:04.020> cwdm<14:47:04.916> these<14:47:05.400> they<14:47:05.936> use<14:47:06.116> multiple 14:47:06.530 --> 14:47:06.540 align:start position:0% um dwdm and cwdm these they use multiple 14:47:06.540 --> 14:47:09.350 align:start position:0% um dwdm and cwdm these they use multiple wavelengths<14:47:07.140> or<14:47:07.256> lights<14:47:07.436> but<14:47:08.040> they<14:47:08.220> differ<14:47:08.400> in 14:47:09.350 --> 14:47:09.360 align:start position:0% wavelengths or lights but they differ in 14:47:09.360 --> 14:47:11.690 align:start position:0% wavelengths or lights but they differ in the<14:47:09.480> spacing<14:47:10.020> I'll<14:47:10.860> show<14:47:10.980> a<14:47:11.220> diagram<14:47:11.400> actually 14:47:11.690 --> 14:47:11.700 align:start position:0% the spacing I'll show a diagram actually 14:47:11.700 --> 14:47:13.850 align:start position:0% the spacing I'll show a diagram actually in<14:47:11.936> a<14:47:12.060> moment 14:47:13.850 --> 14:47:13.860 align:start position:0% in a moment 14:47:13.860 --> 14:47:15.530 align:start position:0% in a moment um<14:47:13.980> so<14:47:14.456> in<14:47:14.580> the<14:47:14.700> following<14:47:15.000> factors<14:47:15.300> a 14:47:15.530 --> 14:47:15.540 align:start position:0% um so in the following factors a 14:47:15.540 --> 14:47:17.210 align:start position:0% um so in the following factors a wavelength<14:47:16.020> on<14:47:16.080> the<14:47:16.256> number<14:47:16.320> of<14:47:16.560> channels<14:47:16.980> the 14:47:17.210 --> 14:47:17.220 align:start position:0% wavelength on the number of channels the 14:47:17.220 --> 14:47:19.850 align:start position:0% wavelength on the number of channels the ability<14:47:17.520> to<14:47:17.936> amplify<14:47:18.416> the<14:47:18.776> multiplex<14:47:19.380> signals 14:47:19.850 --> 14:47:19.860 align:start position:0% ability to amplify the multiplex signals 14:47:19.860 --> 14:47:22.390 align:start position:0% ability to amplify the multiplex signals in<14:47:20.040> the<14:47:20.160> optical<14:47:20.456> space 14:47:22.390 --> 14:47:22.400 align:start position:0% in the optical space 14:47:22.400 --> 14:47:28.606 align:start position:0% in the optical space cwdm<14:47:23.400> uses<14:47:24.060> a<14:47:24.360> smaller<14:47:24.720> number<14:47:24.900> of<14:47:25.080> channels 14:47:28.606 --> 14:47:28.616 align:start position:0% 14:47:28.616 --> 14:47:30.830 align:start position:0% you<14:47:29.160> can<14:47:29.276> use<14:47:29.456> four<14:47:29.880> or<14:47:30.060> eight<14:47:30.240> channels<14:47:30.596> with 14:47:30.830 --> 14:47:30.840 align:start position:0% you can use four or eight channels with 14:47:30.840 --> 14:47:33.170 align:start position:0% you can use four or eight channels with large<14:47:31.020> space<14:47:31.320> in<14:47:31.560> between<14:47:31.740> the<14:47:32.096> channels<14:47:32.520> the 14:47:33.170 --> 14:47:33.180 align:start position:0% large space in between the channels the 14:47:33.180 --> 14:47:35.470 align:start position:0% large space in between the channels the bandwidth<14:47:33.720> of<14:47:33.776> each<14:47:33.956> channel<14:47:34.256> is 14:47:35.470 --> 14:47:35.480 align:start position:0% bandwidth of each channel is 14:47:35.480 --> 14:47:41.510 align:start position:0% bandwidth of each channel is 3.125<14:47:36.480> gigabits 14:47:41.510 --> 14:47:41.520 align:start position:0% 14:47:41.520 --> 14:47:44.746 align:start position:0% so<14:47:42.060> here's<14:47:42.360> an<14:47:42.416> example<14:47:42.660> of<14:47:42.980> cwdm<14:47:43.980> used<14:47:44.520> to 14:47:44.746 --> 14:47:44.756 align:start position:0% so here's an example of cwdm used to 14:47:44.756 --> 14:47:46.730 align:start position:0% so here's an example of cwdm used to transporting<14:47:45.300> data<14:47:45.660> within<14:47:45.956> 100<14:47:46.080> kilometers 14:47:46.730 --> 14:47:46.740 align:start position:0% transporting data within 100 kilometers 14:47:46.740 --> 14:47:53.266 align:start position:0% transporting data within 100 kilometers So<14:47:47.640> within<14:47:48.360> a<14:47:48.540> metropolis<14:47:49.140> area 14:47:53.266 --> 14:47:53.276 align:start position:0% 14:47:53.276 --> 14:47:56.746 align:start position:0% an<14:47:53.936> example<14:47:54.240> of<14:47:54.416> cwdm<14:47:55.256> is<14:47:55.500> 10<14:47:55.680> base<14:47:55.980> lx4 14:47:56.746 --> 14:47:56.756 align:start position:0% an example of cwdm is 10 base lx4 14:47:56.756 --> 14:48:00.830 align:start position:0% an example of cwdm is 10 base lx4 Network<14:47:57.116> it<14:47:57.660> can<14:47:57.840> transmit<14:47:58.380> data<14:47:58.980> at<14:47:59.220> up<14:47:59.520> to<14:47:59.840> 10 14:48:00.830 --> 14:48:00.840 align:start position:0% Network it can transmit data at up to 10 14:48:00.840 --> 14:48:03.490 align:start position:0% Network it can transmit data at up to 10 gigabits<14:48:01.436> per<14:48:01.560> second 14:48:03.490 --> 14:48:03.500 align:start position:0% gigabits per second 14:48:03.500 --> 14:48:06.290 align:start position:0% gigabits per second cwdm<14:48:04.500> cable<14:48:04.916> televisions<14:48:05.520> actually<14:48:05.756> use<14:48:06.060> this 14:48:06.290 --> 14:48:06.300 align:start position:0% cwdm cable televisions actually use this 14:48:06.300 --> 14:48:07.906 align:start position:0% cwdm cable televisions actually use this where<14:48:06.596> different<14:48:06.840> wavelengths<14:48:07.436> are<14:48:07.560> used<14:48:07.680> for 14:48:07.906 --> 14:48:07.916 align:start position:0% where different wavelengths are used for 14:48:07.916 --> 14:48:12.290 align:start position:0% where different wavelengths are used for the<14:48:08.040> downstream<14:48:08.640> and<14:48:09.180> Upstream<14:48:09.776> signals 14:48:12.290 --> 14:48:12.300 align:start position:0% 14:48:12.300 --> 14:48:15.650 align:start position:0% a<14:48:12.956> dense<14:48:13.320> wave<14:48:13.740> then<14:48:14.700> dense<14:48:15.116> wave<14:48:15.360> length 14:48:15.650 --> 14:48:15.660 align:start position:0% a dense wave then dense wave length 14:48:15.660 --> 14:48:18.350 align:start position:0% a dense wave then dense wave length division<14:48:15.956> multiplexing<14:48:16.680> dwdm<14:48:17.640> uses<14:48:18.060> a<14:48:18.240> large 14:48:18.350 --> 14:48:18.360 align:start position:0% division multiplexing dwdm uses a large 14:48:18.360 --> 14:48:21.050 align:start position:0% division multiplexing dwdm uses a large number<14:48:18.540> of<14:48:18.720> channels<14:48:19.140> it<14:48:19.616> could<14:48:19.800> be<14:48:19.916> 40<14:48:20.276> 80<14:48:20.700> or 14:48:21.050 --> 14:48:21.060 align:start position:0% number of channels it could be 40 80 or 14:48:21.060 --> 14:48:24.050 align:start position:0% number of channels it could be 40 80 or 160<14:48:21.660> but<14:48:22.560> they<14:48:22.800> have<14:48:22.980> small<14:48:23.220> spacing<14:48:23.820> between 14:48:24.050 --> 14:48:24.060 align:start position:0% 160 but they have small spacing between 14:48:24.060 --> 14:48:26.086 align:start position:0% 160 but they have small spacing between the<14:48:24.360> channels<14:48:24.840> and<14:48:25.380> here<14:48:25.560> we<14:48:25.740> go<14:48:25.800> is<14:48:25.980> an 14:48:26.086 --> 14:48:26.096 align:start position:0% the channels and here we go is an 14:48:26.096 --> 14:48:28.670 align:start position:0% the channels and here we go is an example<14:48:26.456> from<14:48:27.000> I'll<14:48:27.776> put<14:48:27.956> the<14:48:28.080> link<14:48:28.200> in<14:48:28.436> down 14:48:28.670 --> 14:48:28.680 align:start position:0% example from I'll put the link in down 14:48:28.680 --> 14:48:30.530 align:start position:0% example from I'll put the link in down here<14:48:28.916> you<14:48:29.700> can<14:48:29.820> see<14:48:29.936> the<14:48:30.116> difference<14:48:30.240> here 14:48:30.530 --> 14:48:30.540 align:start position:0% here you can see the difference here 14:48:30.540 --> 14:48:32.810 align:start position:0% here you can see the difference here between<14:48:30.776> the<14:48:31.140> spacing<14:48:31.560> and<14:48:32.400> obviously<14:48:32.640> the 14:48:32.810 --> 14:48:32.820 align:start position:0% between the spacing and obviously the 14:48:32.820 --> 14:48:34.070 align:start position:0% between the spacing and obviously the numbers 14:48:34.070 --> 14:48:34.080 align:start position:0% numbers 14:48:34.080 --> 14:48:35.086 align:start position:0% numbers um 14:48:35.086 --> 14:48:35.096 align:start position:0% um 14:48:35.096 --> 14:48:36.766 align:start position:0% um the<14:48:35.456> numbers<14:48:35.580> are<14:48:35.820> shown<14:48:36.000> in<14:48:36.116> the<14:48:36.300> diagrams 14:48:36.766 --> 14:48:36.776 align:start position:0% the numbers are shown in the diagrams 14:48:36.776 --> 14:48:39.290 align:start position:0% the numbers are shown in the diagrams there<14:48:37.220> cwdm<14:48:38.220> you<14:48:38.340> can<14:48:38.456> see<14:48:38.580> the<14:48:38.700> spacing<14:48:39.116> where 14:48:39.290 --> 14:48:39.300 align:start position:0% there cwdm you can see the spacing where 14:48:39.300 --> 14:48:41.330 align:start position:0% there cwdm you can see the spacing where it's<14:48:39.416> DW<14:48:39.776> DM 14:48:41.330 --> 14:48:41.340 align:start position:0% it's DW DM 14:48:41.340 --> 14:48:43.246 align:start position:0% it's DW DM um<14:48:41.400> very<14:48:41.700> hard<14:48:41.936> to<14:48:42.116> see<14:48:42.240> any<14:48:42.480> spacing<14:48:42.956> between 14:48:43.246 --> 14:48:43.256 align:start position:0% um very hard to see any spacing between 14:48:43.256 --> 14:48:46.730 align:start position:0% um very hard to see any spacing between the<14:48:43.916> channels 14:48:46.730 --> 14:48:46.740 align:start position:0% 14:48:46.740 --> 14:48:48.710 align:start position:0% okay<14:48:47.276> the<14:48:47.580> high<14:48:47.756> number<14:48:47.936> of<14:48:48.116> channels<14:48:48.416> was<14:48:48.540> the 14:48:48.710 --> 14:48:48.720 align:start position:0% okay the high number of channels was the 14:48:48.720 --> 14:48:53.870 align:start position:0% okay the high number of channels was the reason<14:48:48.840> for<14:48:49.080> the<14:48:49.256> name<14:48:49.380> dense<14:48:49.800> wave 14:48:53.870 --> 14:48:53.880 align:start position:0% 14:48:53.880 --> 14:48:56.330 align:start position:0% typical<14:48:54.480> dwdm<14:48:55.320> system<14:48:55.560> would<14:48:55.860> use<14:48:55.980> one<14:48:56.160> of<14:48:56.276> the 14:48:56.330 --> 14:48:56.340 align:start position:0% typical dwdm system would use one of the 14:48:56.340 --> 14:48:59.086 align:start position:0% typical dwdm system would use one of the following<14:48:56.640> 40<14:48:57.116> channels<14:48:57.660> at<14:48:57.776> 100<14:48:58.096> gigahertz 14:48:59.086 --> 14:48:59.096 align:start position:0% following 40 channels at 100 gigahertz 14:48:59.096 --> 14:49:02.150 align:start position:0% following 40 channels at 100 gigahertz spacing<14:48:59.700> 80<14:49:00.660> Channels<14:49:01.200> with<14:49:01.436> 50<14:49:01.616> gigahertz 14:49:02.150 --> 14:49:02.160 align:start position:0% spacing 80 Channels with 50 gigahertz 14:49:02.160 --> 14:49:03.710 align:start position:0% spacing 80 Channels with 50 gigahertz space<14:49:02.520> in 14:49:03.710 --> 14:49:03.720 align:start position:0% space in 14:49:03.720 --> 14:49:05.870 align:start position:0% space in the<14:49:04.080> bandwidth<14:49:04.500> of<14:49:04.616> a<14:49:04.800> single<14:49:05.040> channel<14:49:05.340> is<14:49:05.640> 100 14:49:05.870 --> 14:49:05.880 align:start position:0% the bandwidth of a single channel is 100 14:49:05.880 --> 14:49:09.290 align:start position:0% the bandwidth of a single channel is 100 Gig 14:49:09.290 --> 14:49:09.300 align:start position:0% 14:49:09.300 --> 14:49:11.570 align:start position:0% used<14:49:09.660> for<14:49:09.900> transporting<14:49:10.500> data<14:49:10.980> over<14:49:11.220> long 14:49:11.570 --> 14:49:11.580 align:start position:0% used for transporting data over long 14:49:11.580 --> 14:49:13.370 align:start position:0% used for transporting data over long distances<14:49:12.180> mainly<14:49:12.660> used<14:49:12.840> as<14:49:13.080> the<14:49:13.320> internet 14:49:13.370 --> 14:49:13.380 align:start position:0% distances mainly used as the internet 14:49:13.380 --> 14:49:16.190 align:start position:0% distances mainly used as the internet background<14:49:14.040> so<14:49:14.340> this<14:49:14.520> cable<14:49:14.820> will<14:49:15.180> be<14:49:15.360> laid 14:49:16.190 --> 14:49:16.200 align:start position:0% background so this cable will be laid 14:49:16.200 --> 14:49:19.246 align:start position:0% background so this cable will be laid over<14:49:16.436> long<14:49:16.916> stretches<14:49:17.520> and<14:49:18.660> um<14:49:18.720> under<14:49:19.020> the 14:49:19.246 --> 14:49:19.256 align:start position:0% over long stretches and um under the 14:49:19.256 --> 14:49:20.990 align:start position:0% over long stretches and um under the ocean 14:49:20.990 --> 14:49:21.000 align:start position:0% ocean 14:49:21.000 --> 14:49:23.390 align:start position:0% ocean into<14:49:21.800> interconnects<14:49:22.800> large<14:49:22.916> strategic 14:49:23.390 --> 14:49:23.400 align:start position:0% into interconnects large strategic 14:49:23.400 --> 14:49:26.030 align:start position:0% into interconnects large strategic computer<14:49:23.640> networks<14:49:24.240> and<14:49:24.480> core<14:49:24.720> routers 14:49:26.030 --> 14:49:26.040 align:start position:0% computer networks and core routers 14:49:26.040 --> 14:49:28.246 align:start position:0% computer networks and core routers all<14:49:26.456> right<14:49:26.580> so<14:49:26.700> we<14:49:26.820> looked<14:49:27.060> at<14:49:27.060> what<14:49:27.300> is<14:49:27.416> wdm 14:49:28.246 --> 14:49:28.256 align:start position:0% all right so we looked at what is wdm 14:49:28.256 --> 14:49:32.106 align:start position:0% all right so we looked at what is wdm the<14:49:28.980> system<14:49:29.220> and<14:49:30.060> cwdm 14:49:32.106 --> 14:49:32.116 align:start position:0% the system and cwdm 14:49:32.116 --> 14:49:36.470 align:start position:0% the system and cwdm dndm<14:49:33.116> no<14:49:33.596> dwdm<14:49:34.436> sorry<14:49:34.680> typo 14:49:36.470 --> 14:49:36.480 align:start position:0% dndm no dwdm sorry typo 14:49:36.480 --> 14:49:38.086 align:start position:0% dndm no dwdm sorry typo all<14:49:36.840> right<14:49:36.956> that's<14:49:37.080> all<14:49:37.320> for<14:49:37.436> now<14:49:37.616> thanks<14:49:37.980> for 14:49:38.086 --> 14:49:38.096 align:start position:0% all right that's all for now thanks for 14:49:38.096 --> 14:49:44.120 align:start position:0% all right that's all for now thanks for watching 14:49:44.120 --> 14:49:44.130 align:start position:0% 14:49:44.130 --> 14:49:59.990 align:start position:0% [Music] 14:49:59.990 --> 14:50:00.000 align:start position:0% 14:50:00.000 --> 14:50:03.170 align:start position:0% welcome<14:50:00.540> to<14:50:00.840> module<14:50:01.256> 9<14:50:01.380> lesson<14:50:01.860> 2C<14:50:02.340> uh 14:50:03.170 --> 14:50:03.180 align:start position:0% welcome to module 9 lesson 2C uh 14:50:03.180 --> 14:50:08.230 align:start position:0% welcome to module 9 lesson 2C uh multi-protocol<14:50:03.840> label<14:50:04.380> switching<14:50:04.860> mpls 14:50:08.230 --> 14:50:08.240 align:start position:0% 14:50:08.240 --> 14:50:11.690 align:start position:0% so<14:50:09.240> what<14:50:09.540> is<14:50:09.660> it<14:50:09.900> a<14:50:10.740> label<14:50:11.096> switch<14:50:11.276> path 14:50:11.690 --> 14:50:11.700 align:start position:0% so what is it a label switch path 14:50:11.700 --> 14:50:13.770 align:start position:0% so what is it a label switch path benefits<14:50:12.540> tunneling 14:50:13.770 --> 14:50:13.780 align:start position:0% benefits tunneling 14:50:13.780 --> 14:50:15.290 align:start position:0% benefits tunneling [Music] 14:50:15.290 --> 14:50:15.300 align:start position:0% [Music] 14:50:15.300 --> 14:50:16.850 align:start position:0% [Music] it's<14:50:15.660> just<14:50:15.776> an<14:50:15.956> overview<14:50:16.256> really<14:50:16.616> because 14:50:16.850 --> 14:50:16.860 align:start position:0% it's just an overview really because 14:50:16.860 --> 14:50:20.030 align:start position:0% it's just an overview really because they<14:50:17.160> mention<14:50:17.400> it<14:50:17.756> once<14:50:18.596> in<14:50:19.200> brief<14:50:19.500> in<14:50:19.860> the 14:50:20.030 --> 14:50:20.040 align:start position:0% they mention it once in brief in the 14:50:20.040 --> 14:50:21.290 align:start position:0% they mention it once in brief in the syllabus 14:50:21.290 --> 14:50:21.300 align:start position:0% syllabus 14:50:21.300 --> 14:50:24.406 align:start position:0% syllabus but<14:50:21.720> an<14:50:21.900> mperls<14:50:22.800> Network<14:50:23.040> it<14:50:23.700> provides<14:50:24.116> one 14:50:24.406 --> 14:50:24.416 align:start position:0% but an mperls Network it provides one 14:50:24.416 --> 14:50:26.446 align:start position:0% but an mperls Network it provides one connectivity<14:50:25.020> between<14:50:25.500> two<14:50:25.800> geographically 14:50:26.446 --> 14:50:26.456 align:start position:0% connectivity between two geographically 14:50:26.456 --> 14:50:29.030 align:start position:0% connectivity between two geographically distant<14:50:27.000> offices<14:50:27.480> so<14:50:28.080> it's<14:50:28.256> one<14:50:28.500> of<14:50:28.680> a<14:50:28.800> number 14:50:29.030 --> 14:50:29.040 align:start position:0% distant offices so it's one of a number 14:50:29.040 --> 14:50:32.570 align:start position:0% distant offices so it's one of a number of<14:50:29.660> methods<14:50:30.660> for<14:50:30.840> connecting<14:50:31.340> across<14:50:32.340> a<14:50:32.456> wide 14:50:32.570 --> 14:50:32.580 align:start position:0% of methods for connecting across a wide 14:50:32.580 --> 14:50:34.550 align:start position:0% of methods for connecting across a wide area<14:50:32.820> network<14:50:33.180> and<14:50:33.540> obviously<14:50:33.840> each<14:50:33.956> has<14:50:34.200> its 14:50:34.550 --> 14:50:34.560 align:start position:0% area network and obviously each has its 14:50:34.560 --> 14:50:38.746 align:start position:0% area network and obviously each has its pros<14:50:34.980> and<14:50:35.096> cons<14:50:35.540> which<14:50:36.540> we'll<14:50:36.720> go<14:50:37.140> into<14:50:37.756> mpls 14:50:38.746 --> 14:50:38.756 align:start position:0% pros and cons which we'll go into mpls 14:50:38.756 --> 14:50:40.550 align:start position:0% pros and cons which we'll go into mpls it's<14:50:39.060> high<14:50:39.300> performance<14:50:39.720> it's<14:50:40.020> packet 14:50:40.550 --> 14:50:40.560 align:start position:0% it's high performance it's packet 14:50:40.560 --> 14:50:43.606 align:start position:0% it's high performance it's packet switching<14:50:41.096> a<14:50:41.820> packet<14:50:42.180> forward<14:50:42.360> in<14:50:42.720> it<14:50:43.320> uses 14:50:43.606 --> 14:50:43.616 align:start position:0% switching a packet forward in it uses 14:50:43.616 --> 14:50:45.350 align:start position:0% switching a packet forward in it uses labels<14:50:44.040> to<14:50:44.220> address<14:50:44.400> packets<14:50:44.936> in<14:50:45.180> the 14:50:45.350 --> 14:50:45.360 align:start position:0% labels to address packets in the 14:50:45.360 --> 14:50:48.106 align:start position:0% labels to address packets in the telecoms<14:50:45.840> network 14:50:48.106 --> 14:50:48.116 align:start position:0% 14:50:48.116 --> 14:50:50.570 align:start position:0% now<14:50:49.020> uh<14:50:49.436> it's<14:50:49.560> called<14:50:49.800> label<14:50:50.160> switching 14:50:50.570 --> 14:50:50.580 align:start position:0% now uh it's called label switching 14:50:50.580 --> 14:50:52.730 align:start position:0% now uh it's called label switching because<14:50:50.756> it<14:50:51.000> makes<14:50:51.116> forwarding<14:50:51.720> decisions<14:50:52.140> of 14:50:52.730 --> 14:50:52.740 align:start position:0% because it makes forwarding decisions of 14:50:52.740 --> 14:50:55.370 align:start position:0% because it makes forwarding decisions of the<14:50:52.980> packets<14:50:53.400> based<14:50:53.936> upon<14:50:54.240> the<14:50:54.720> values<14:50:55.020> of<14:50:55.200> the 14:50:55.370 --> 14:50:55.380 align:start position:0% the packets based upon the values of the 14:50:55.380 --> 14:50:58.246 align:start position:0% the packets based upon the values of the labels<14:50:55.756> and<14:50:56.756> as<14:50:57.060> opposed<14:50:57.416> to<14:50:57.480> the<14:50:57.720> usual<14:50:58.020> way 14:50:58.246 --> 14:50:58.256 align:start position:0% labels and as opposed to the usual way 14:50:58.256 --> 14:51:01.070 align:start position:0% labels and as opposed to the usual way which<14:50:58.500> is<14:50:58.616> looking<14:50:58.800> at<14:50:59.040> the<14:50:59.220> IP<14:50:59.640> headers 14:51:01.070 --> 14:51:01.080 align:start position:0% which is looking at the IP headers 14:51:01.080 --> 14:51:04.426 align:start position:0% which is looking at the IP headers so<14:51:01.500> this<14:51:01.616> avoids<14:51:02.040> having<14:51:02.276> to<14:51:02.840> look<14:51:03.840> at<14:51:04.020> the 14:51:04.426 --> 14:51:04.436 align:start position:0% so this avoids having to look at the 14:51:04.436 --> 14:51:06.290 align:start position:0% so this avoids having to look at the routing<14:51:04.800> table<14:51:04.980> lookups<14:51:05.580> and<14:51:05.756> all<14:51:05.936> of<14:51:06.116> the 14:51:06.290 --> 14:51:06.300 align:start position:0% routing table lookups and all of the 14:51:06.300 --> 14:51:10.606 align:start position:0% routing table lookups and all of the problems<14:51:07.256> associated<14:51:08.116> associated<14:51:09.116> with<14:51:09.616> uh 14:51:10.606 --> 14:51:10.616 align:start position:0% problems associated associated with uh 14:51:10.616 --> 14:51:12.946 align:start position:0% problems associated associated with uh routing<14:51:11.096> table<14:51:11.276> lookups 14:51:12.946 --> 14:51:12.956 align:start position:0% routing table lookups 14:51:12.956 --> 14:51:15.766 align:start position:0% routing table lookups cool<14:51:13.680> concept<14:51:14.160> is<14:51:14.340> labels<14:51:14.820> are<14:51:15.000> assigned<14:51:15.480> or 14:51:15.766 --> 14:51:15.776 align:start position:0% cool concept is labels are assigned or 14:51:15.776 --> 14:51:18.586 align:start position:0% cool concept is labels are assigned or pushed<14:51:16.200> into<14:51:16.560> Data<14:51:17.096> packets<14:51:17.456> this<14:51:18.240> is<14:51:18.480> the 14:51:18.586 --> 14:51:18.596 align:start position:0% pushed into Data packets this is the 14:51:18.596 --> 14:51:20.266 align:start position:0% pushed into Data packets this is the packets<14:51:18.840> are<14:51:18.956> labeled<14:51:19.320> the<14:51:19.560> routers<14:51:19.980> in<14:51:20.160> the 14:51:20.266 --> 14:51:20.276 align:start position:0% packets are labeled the routers in the 14:51:20.276 --> 14:51:22.426 align:start position:0% packets are labeled the routers in the impulse<14:51:20.700> Network<14:51:21.000> make<14:51:21.776> forwarding 14:51:22.426 --> 14:51:22.436 align:start position:0% impulse Network make forwarding 14:51:22.436 --> 14:51:25.130 align:start position:0% impulse Network make forwarding decisions<14:51:22.916> based<14:51:23.640> upon<14:51:23.820> that<14:51:24.060> label 14:51:25.130 --> 14:51:25.140 align:start position:0% decisions based upon that label 14:51:25.140 --> 14:51:26.870 align:start position:0% decisions based upon that label you're<14:51:25.616> still<14:51:25.800> without<14:51:25.980> having<14:51:26.276> to<14:51:26.456> examine 14:51:26.870 --> 14:51:26.880 align:start position:0% you're still without having to examine 14:51:26.880 --> 14:51:28.906 align:start position:0% you're still without having to examine the<14:51:27.060> actual<14:51:27.300> packet<14:51:27.840> it's<14:51:27.956> only<14:51:28.256> the<14:51:28.500> label 14:51:28.906 --> 14:51:28.916 align:start position:0% the actual packet it's only the label 14:51:28.916 --> 14:51:32.990 align:start position:0% the actual packet it's only the label has<14:51:29.220> to<14:51:29.400> be<14:51:29.580> examined 14:51:32.990 --> 14:51:33.000 align:start position:0% 14:51:33.000 --> 14:51:35.266 align:start position:0% so<14:51:33.540> say<14:51:33.840> remote<14:51:34.256> office<14:51:34.560> say<14:51:34.800> what's<14:51:34.980> the<14:51:35.160> same 14:51:35.266 --> 14:51:35.276 align:start position:0% so say remote office say what's the same 14:51:35.276 --> 14:51:38.266 align:start position:0% so say remote office say what's the same package<14:51:35.700> to<14:51:35.880> remote<14:51:36.116> office<14:51:36.416> B 14:51:38.266 --> 14:51:38.276 align:start position:0% package to remote office B 14:51:38.276 --> 14:51:40.790 align:start position:0% package to remote office B and<14:51:38.640> the<14:51:38.820> data<14:51:39.060> sent<14:51:39.180> by<14:51:39.416> a<14:51:39.660> reaches<14:51:40.200> the<14:51:40.320> mpls 14:51:40.790 --> 14:51:40.800 align:start position:0% and the data sent by a reaches the mpls 14:51:40.800 --> 14:51:43.130 align:start position:0% and the data sent by a reaches the mpls network<14:51:41.040> the<14:51:41.520> data<14:51:41.756> will<14:51:41.880> be<14:51:42.060> labeled<14:51:42.480> just 14:51:43.130 --> 14:51:43.140 align:start position:0% network the data will be labeled just 14:51:43.140 --> 14:51:44.810 align:start position:0% network the data will be labeled just like<14:51:43.256> how<14:51:43.500> we'd<14:51:43.860> label 14:51:44.810 --> 14:51:44.820 align:start position:0% like how we'd label 14:51:44.820 --> 14:51:46.606 align:start position:0% like how we'd label um<14:51:44.936> a<14:51:45.180> packet<14:51:45.540> if<14:51:45.720> we<14:51:45.840> were<14:51:45.956> sending<14:51:46.320> it<14:51:46.436> by 14:51:46.606 --> 14:51:46.616 align:start position:0% um a packet if we were sending it by 14:51:46.616 --> 14:51:48.530 align:start position:0% um a packet if we were sending it by shipping 14:51:48.530 --> 14:51:48.540 align:start position:0% shipping 14:51:48.540 --> 14:51:50.390 align:start position:0% shipping and<14:51:48.900> then<14:51:49.020> the<14:51:49.200> routers<14:51:49.500> in<14:51:49.616> the<14:51:49.740> mpls<14:51:50.220> network 14:51:50.390 --> 14:51:50.400 align:start position:0% and then the routers in the mpls network 14:51:50.400 --> 14:51:52.606 align:start position:0% and then the routers in the mpls network will<14:51:50.580> act<14:51:50.880> like<14:51:51.000> a<14:51:51.180> courier<14:51:51.480> service<14:51:51.720> the 14:51:52.606 --> 14:51:52.616 align:start position:0% will act like a courier service the 14:51:52.616 --> 14:51:55.370 align:start position:0% will act like a courier service the routers<14:51:53.040> do<14:51:53.340> not<14:51:53.520> open<14:51:54.240> the<14:51:54.480> packet<14:51:54.900> they<14:51:55.200> just 14:51:55.370 --> 14:51:55.380 align:start position:0% routers do not open the packet they just 14:51:55.380 --> 14:51:57.530 align:start position:0% routers do not open the packet they just look<14:51:55.500> at<14:51:55.680> the<14:51:55.860> label<14:51:56.220> and<14:51:56.580> decide<14:51:57.116> where<14:51:57.416> to 14:51:57.530 --> 14:51:57.540 align:start position:0% look at the label and decide where to 14:51:57.540 --> 14:52:00.170 align:start position:0% look at the label and decide where to send<14:51:57.720> it<14:51:57.900> for<14:51:58.500> the<14:51:58.680> next<14:51:58.800> destination 14:52:00.170 --> 14:52:00.180 align:start position:0% send it for the next destination 14:52:00.180 --> 14:52:02.570 align:start position:0% send it for the next destination process<14:52:00.900> continues<14:52:01.436> until<14:52:01.616> you<14:52:02.096> reach<14:52:02.340> the 14:52:02.570 --> 14:52:02.580 align:start position:0% process continues until you reach the 14:52:02.580 --> 14:52:04.970 align:start position:0% process continues until you reach the edge<14:52:02.880> of<14:52:03.116> the<14:52:03.300> mpls<14:52:03.840> network<14:52:04.080> when<14:52:04.500> the<14:52:04.680> label 14:52:04.970 --> 14:52:04.980 align:start position:0% edge of the mpls network when the label 14:52:04.980 --> 14:52:07.310 align:start position:0% edge of the mpls network when the label is<14:52:05.096> removed<14:52:05.580> or<14:52:05.936> popped<14:52:06.416> before<14:52:07.020> being 14:52:07.310 --> 14:52:07.320 align:start position:0% is removed or popped before being 14:52:07.320 --> 14:52:10.010 align:start position:0% is removed or popped before being forwarded<14:52:07.740> to<14:52:07.980> the<14:52:08.096> remote<14:52:08.220> office<14:52:08.880> B 14:52:10.010 --> 14:52:10.020 align:start position:0% forwarded to the remote office B 14:52:10.020 --> 14:52:13.606 align:start position:0% forwarded to the remote office B here's<14:52:10.616> an<14:52:10.680> example<14:52:11.040> of<14:52:11.456> a<14:52:11.700> mpls<14:52:12.300> network<14:52:12.616> from 14:52:13.606 --> 14:52:13.616 align:start position:0% here's an example of a mpls network from 14:52:13.616 --> 14:52:16.310 align:start position:0% here's an example of a mpls network from netcerts.net 14:52:16.310 --> 14:52:16.320 align:start position:0% netcerts.net 14:52:16.320 --> 14:52:18.650 align:start position:0% netcerts.net the<14:52:16.740> labels<14:52:17.040> in<14:52:17.276> the<14:52:17.400> mpls<14:52:17.820> network<14:52:18.060> have<14:52:18.416> the 14:52:18.650 --> 14:52:18.660 align:start position:0% the labels in the mpls network have the 14:52:18.660 --> 14:52:20.390 align:start position:0% the labels in the mpls network have the information<14:52:18.776> that<14:52:19.320> tells<14:52:19.616> the<14:52:19.740> routers<14:52:20.096> where 14:52:20.390 --> 14:52:20.400 align:start position:0% information that tells the routers where 14:52:20.400 --> 14:52:22.310 align:start position:0% information that tells the routers where to<14:52:20.520> forward<14:52:20.640> the<14:52:20.936> packets<14:52:21.240> this<14:52:22.020> is<14:52:22.140> a 14:52:22.310 --> 14:52:22.320 align:start position:0% to forward the packets this is a 14:52:22.320 --> 14:52:25.906 align:start position:0% to forward the packets this is a simplified<14:52:22.680> diagram<14:52:23.276> where<14:52:23.936> the<14:52:24.180> IP<14:52:24.916> packet 14:52:25.906 --> 14:52:25.916 align:start position:0% simplified diagram where the IP packet 14:52:25.916 --> 14:52:28.130 align:start position:0% simplified diagram where the IP packet has<14:52:26.096> gone<14:52:26.276> across<14:52:26.640> to<14:52:26.756> two<14:52:27.000> routers<14:52:27.416> and<14:52:28.080> then 14:52:28.130 --> 14:52:28.140 align:start position:0% has gone across to two routers and then 14:52:28.140 --> 14:52:30.650 align:start position:0% has gone across to two routers and then it's<14:52:28.320> hitting<14:52:28.740> the<14:52:28.860> mpls<14:52:29.580> network<14:52:29.820> at<14:52:30.180> router 14:52:30.650 --> 14:52:30.660 align:start position:0% it's hitting the mpls network at router 14:52:30.660 --> 14:52:34.010 align:start position:0% it's hitting the mpls network at router p<14:52:31.200> e<14:52:31.436> a<14:52:31.680> which<14:52:31.980> adds<14:52:32.276> a<14:52:32.456> label<14:52:32.756> and<14:52:33.660> then<14:52:33.776> the 14:52:34.010 --> 14:52:34.020 align:start position:0% p e a which adds a label and then the 14:52:34.020 --> 14:52:37.730 align:start position:0% p e a which adds a label and then the label<14:52:34.500> is<14:52:34.616> finally<14:52:34.980> removed<14:52:35.700> at<14:52:36.360> router<14:52:37.256> p<14:52:37.500> e 14:52:37.730 --> 14:52:37.740 align:start position:0% label is finally removed at router p e 14:52:37.740 --> 14:52:38.990 align:start position:0% label is finally removed at router p e Zed 14:52:38.990 --> 14:52:39.000 align:start position:0% Zed 14:52:39.000 --> 14:52:40.670 align:start position:0% Zed so<14:52:39.360> there's<14:52:39.596> only<14:52:39.720> three<14:52:39.900> routers<14:52:40.320> involved 14:52:40.670 --> 14:52:40.680 align:start position:0% so there's only three routers involved 14:52:40.680 --> 14:52:45.766 align:start position:0% so there's only three routers involved in<14:52:40.800> the<14:52:40.916> mpls<14:52:41.456> network<14:52:41.820> here 14:52:45.766 --> 14:52:45.776 align:start position:0% 14:52:45.776 --> 14:52:48.470 align:start position:0% so<14:52:46.436> as<14:52:46.740> I<14:52:46.916> said<14:52:47.040> this<14:52:47.456> is<14:52:47.700> different<14:52:47.936> to<14:52:48.240> the 14:52:48.470 --> 14:52:48.480 align:start position:0% so as I said this is different to the 14:52:48.480 --> 14:52:50.266 align:start position:0% so as I said this is different to the traditional<14:52:48.776> routing<14:52:49.256> where<14:52:49.500> each<14:52:49.740> packet's 14:52:50.266 --> 14:52:50.276 align:start position:0% traditional routing where each packet's 14:52:50.276 --> 14:52:52.850 align:start position:0% traditional routing where each packet's header<14:52:50.640> has<14:52:51.240> to<14:52:51.360> be<14:52:51.480> examined<14:52:51.956> each<14:52:52.320> router 14:52:52.850 --> 14:52:52.860 align:start position:0% header has to be examined each router 14:52:52.860 --> 14:52:55.490 align:start position:0% header has to be examined each router step<14:52:53.520> by<14:52:53.700> step<14:52:53.936> has<14:52:54.180> to<14:52:54.360> do<14:52:54.480> complex<14:52:54.840> lookups 14:52:55.490 --> 14:52:55.500 align:start position:0% step by step has to do complex lookups 14:52:55.500 --> 14:52:57.290 align:start position:0% step by step has to do complex lookups and<14:52:56.040> obviously<14:52:56.340> deal<14:52:56.520> with<14:52:56.700> all<14:52:56.880> the<14:52:57.180> other 14:52:57.290 --> 14:52:57.300 align:start position:0% and obviously deal with all the other 14:52:57.300 --> 14:53:01.070 align:start position:0% and obviously deal with all the other issues<14:52:57.840> associated<14:52:58.500> with<14:52:59.400> routing 14:53:01.070 --> 14:53:01.080 align:start position:0% issues associated with routing 14:53:01.080 --> 14:53:03.230 align:start position:0% issues associated with routing a<14:53:01.500> label<14:53:01.860> switch<14:53:01.980> pass<14:53:02.340> the<14:53:02.756> data 14:53:03.230 --> 14:53:03.240 align:start position:0% a label switch pass the data 14:53:03.240 --> 14:53:06.050 align:start position:0% a label switch pass the data transmission<14:53:03.596> in<14:53:04.200> an<14:53:04.380> mpls<14:53:04.800> Network<14:53:05.096> occurs 14:53:06.050 --> 14:53:06.060 align:start position:0% transmission in an mpls Network occurs 14:53:06.060 --> 14:53:07.490 align:start position:0% transmission in an mpls Network occurs through<14:53:06.240> a<14:53:06.416> path<14:53:06.596> called<14:53:06.776> the<14:53:06.956> label<14:53:07.256> switch 14:53:07.490 --> 14:53:07.500 align:start position:0% through a path called the label switch 14:53:07.500 --> 14:53:09.470 align:start position:0% through a path called the label switch paths 14:53:09.470 --> 14:53:09.480 align:start position:0% paths 14:53:09.480 --> 14:53:11.510 align:start position:0% paths this<14:53:10.080> is<14:53:10.200> the<14:53:10.380> sequence<14:53:10.680> of<14:53:10.800> labels<14:53:11.160> that<14:53:11.340> each 14:53:11.510 --> 14:53:11.520 align:start position:0% this is the sequence of labels that each 14:53:11.520 --> 14:53:13.370 align:start position:0% this is the sequence of labels that each and<14:53:11.700> every<14:53:11.820> nose<14:53:12.116> along<14:53:12.360> the<14:53:12.596> path<14:53:12.776> that 14:53:13.370 --> 14:53:13.380 align:start position:0% and every nose along the path that 14:53:13.380 --> 14:53:15.530 align:start position:0% and every nose along the path that establishes<14:53:13.980> between<14:53:14.520> the<14:53:14.820> source<14:53:15.116> and<14:53:15.360> the 14:53:15.530 --> 14:53:15.540 align:start position:0% establishes between the source and the 14:53:15.540 --> 14:53:17.746 align:start position:0% establishes between the source and the destination<14:53:16.020> this<14:53:16.860> is<14:53:16.980> all<14:53:17.160> actually<14:53:17.340> set<14:53:17.640> up 14:53:17.746 --> 14:53:17.756 align:start position:0% destination this is all actually set up 14:53:17.756 --> 14:53:20.870 align:start position:0% destination this is all actually set up before<14:53:17.936> the<14:53:18.240> data<14:53:18.596> is<14:53:18.720> transmitted 14:53:20.870 --> 14:53:20.880 align:start position:0% before the data is transmitted 14:53:20.880 --> 14:53:22.970 align:start position:0% before the data is transmitted multi-protocol<14:53:21.840> basically<14:53:22.380> means<14:53:22.680> a<14:53:22.800> number 14:53:22.970 --> 14:53:22.980 align:start position:0% multi-protocol basically means a number 14:53:22.980 --> 14:53:25.370 align:start position:0% multi-protocol basically means a number of<14:53:23.096> protocols<14:53:23.756> can<14:53:23.936> be<14:53:24.060> used<14:53:24.300> really<14:53:25.020> the<14:53:25.256> only 14:53:25.370 --> 14:53:25.380 align:start position:0% of protocols can be used really the only 14:53:25.380 --> 14:53:28.570 align:start position:0% of protocols can be used really the only protocol<14:53:25.800> left<14:53:26.160> to<14:53:26.456> send<14:53:26.756> over<14:53:27.060> mpls<14:53:27.660> is<14:53:27.956> IP 14:53:28.570 --> 14:53:28.580 align:start position:0% protocol left to send over mpls is IP 14:53:28.580 --> 14:53:33.406 align:start position:0% protocol left to send over mpls is IP and<14:53:29.580> ipx<14:53:30.300> SPX<14:53:31.020> and<14:53:31.436> other<14:53:31.740> such<14:53:32.520> protocols<14:53:33.300> or 14:53:33.406 --> 14:53:33.416 align:start position:0% and ipx SPX and other such protocols or 14:53:33.416 --> 14:53:37.030 align:start position:0% and ipx SPX and other such protocols or apple<14:53:33.660> talk<14:53:33.900> aren't<14:53:34.256> used<14:53:34.500> anymore<14:53:34.800> at<14:53:35.220> all 14:53:37.030 --> 14:53:37.040 align:start position:0% apple talk aren't used anymore at all 14:53:37.040 --> 14:53:40.130 align:start position:0% apple talk aren't used anymore at all npls<14:53:38.040> is<14:53:38.220> often<14:53:38.520> referred<14:53:38.880> to<14:53:39.000> as<14:53:39.300> layer<14:53:39.660> 2.5 14:53:40.130 --> 14:53:40.140 align:start position:0% npls is often referred to as layer 2.5 14:53:40.140 --> 14:53:43.246 align:start position:0% npls is often referred to as layer 2.5 because<14:53:40.616> it<14:53:40.860> sits<14:53:41.220> between<14:53:41.340> layers<14:53:42.060> 2<14:53:42.360> and 14:53:43.246 --> 14:53:43.256 align:start position:0% because it sits between layers 2 and 14:53:43.256 --> 14:53:46.906 align:start position:0% because it sits between layers 2 and layer<14:53:43.616> 3<14:53:43.860> of<14:53:44.820> The<14:53:45.116> OSI 14:53:46.906 --> 14:53:46.916 align:start position:0% layer 3 of The OSI 14:53:46.916 --> 14:53:49.246 align:start position:0% layer 3 of The OSI some<14:53:47.456> of<14:53:47.580> the<14:53:47.700> benefits<14:53:48.240> not<14:53:48.660> dependent<14:53:49.080> on 14:53:49.246 --> 14:53:49.256 align:start position:0% some of the benefits not dependent on 14:53:49.256 --> 14:53:52.070 align:start position:0% some of the benefits not dependent on layer<14:53:49.680> two<14:53:49.936> technologies<14:53:50.936> such<14:53:51.300> as<14:53:51.416> ATMs 14:53:52.070 --> 14:53:52.080 align:start position:0% layer two technologies such as ATMs 14:53:52.080 --> 14:53:53.746 align:start position:0% layer two technologies such as ATMs sonnet<14:53:52.500> and<14:53:52.680> ethernet 14:53:53.746 --> 14:53:53.756 align:start position:0% sonnet and ethernet 14:53:53.756 --> 14:53:55.606 align:start position:0% sonnet and ethernet it<14:53:54.116> can<14:53:54.180> be<14:53:54.300> used<14:53:54.416> to<14:53:54.596> carry<14:53:54.956> different<14:53:55.256> types 14:53:55.606 --> 14:53:55.616 align:start position:0% it can be used to carry different types 14:53:55.616 --> 14:53:56.586 align:start position:0% it can be used to carry different types of<14:53:55.740> traffic 14:53:56.586 --> 14:53:56.596 align:start position:0% of traffic 14:53:56.596 --> 14:53:58.210 align:start position:0% of traffic and 14:53:58.210 --> 14:53:58.220 align:start position:0% and 14:53:58.220 --> 14:54:04.790 align:start position:0% and ATMs<14:53:59.220> on<14:53:59.340> it<14:53:59.580> and<14:53:59.820> ethernet<14:54:00.240> frames 14:54:04.790 --> 14:54:04.800 align:start position:0% 14:54:04.800 --> 14:54:07.550 align:start position:0% tunneling<14:54:05.540> mpls<14:54:06.540> can<14:54:06.776> control<14:54:07.020> the<14:54:07.320> entire 14:54:07.550 --> 14:54:07.560 align:start position:0% tunneling mpls can control the entire 14:54:07.560 --> 14:54:09.350 align:start position:0% tunneling mpls can control the entire path<14:54:07.740> of<14:54:07.980> a<14:54:08.160> packet<14:54:08.580> by<14:54:08.756> tunneling<14:54:09.180> through 14:54:09.350 --> 14:54:09.360 align:start position:0% path of a packet by tunneling through 14:54:09.360 --> 14:54:11.510 align:start position:0% path of a packet by tunneling through the<14:54:09.480> intermediate<14:54:10.020> routers<14:54:10.500> that<14:54:11.160> span 14:54:11.510 --> 14:54:11.520 align:start position:0% the intermediate routers that span 14:54:11.520 --> 14:54:15.586 align:start position:0% the intermediate routers that span multiple<14:54:11.936> segments 14:54:15.586 --> 14:54:15.596 align:start position:0% 14:54:15.596 --> 14:54:18.350 align:start position:0% this<14:54:16.256> is<14:54:16.380> a<14:54:16.680> unique<14:54:17.160> feature<14:54:17.456> of<14:54:17.580> mpls<14:54:18.060> it's 14:54:18.350 --> 14:54:18.360 align:start position:0% this is a unique feature of mpls it's 14:54:18.360 --> 14:54:21.586 align:start position:0% this is a unique feature of mpls it's used<14:54:18.540> in<14:54:18.840> provisioning<14:54:19.616> in<14:54:19.740> mpls<14:54:20.456> based<14:54:21.060> vpns 14:54:21.586 --> 14:54:21.596 align:start position:0% used in provisioning in mpls based vpns 14:54:21.596 --> 14:54:25.310 align:start position:0% used in provisioning in mpls based vpns which<14:54:21.776> is<14:54:21.900> actually<14:54:22.140> outside<14:54:22.580> the<14:54:23.580> syllabus 14:54:25.310 --> 14:54:25.320 align:start position:0% which is actually outside the syllabus 14:54:25.320 --> 14:54:28.670 align:start position:0% which is actually outside the syllabus all<14:54:25.800> right<14:54:25.980> so<14:54:26.040> we've<14:54:26.220> looked<14:54:26.456> at<14:54:26.520> mpls<14:54:27.680> LSPs 14:54:28.670 --> 14:54:28.680 align:start position:0% all right so we've looked at mpls LSPs 14:54:28.680 --> 14:54:31.130 align:start position:0% all right so we've looked at mpls LSPs some<14:54:29.096> of<14:54:29.276> the<14:54:29.340> benefits<14:54:29.880> and<14:54:30.300> we've<14:54:30.720> mentioned 14:54:31.130 --> 14:54:31.140 align:start position:0% some of the benefits and we've mentioned 14:54:31.140 --> 14:54:32.446 align:start position:0% some of the benefits and we've mentioned tunneling<14:54:31.616> we<14:54:31.800> haven't<14:54:31.916> gone<14:54:32.096> into<14:54:32.220> any 14:54:32.446 --> 14:54:32.456 align:start position:0% tunneling we haven't gone into any 14:54:32.456 --> 14:54:34.850 align:start position:0% tunneling we haven't gone into any detail<14:54:32.880> obviously<14:54:33.360> that's<14:54:34.256> all<14:54:34.500> for<14:54:34.680> now 14:54:34.850 --> 14:54:34.860 align:start position:0% detail obviously that's all for now 14:54:34.860 --> 14:54:40.690 align:start position:0% detail obviously that's all for now thanks<14:54:35.160> for<14:54:35.340> watching 14:54:40.690 --> 14:54:40.700 align:start position:0% 14:54:40.700 --> 14:54:56.870 align:start position:0% [Music] 14:54:56.870 --> 14:54:56.880 align:start position:0% 14:54:56.880 --> 14:54:59.990 align:start position:0% welcome<14:54:57.416> to<14:54:57.660> module<14:54:58.020> 9<14:54:58.140> lesson<14:54:58.680> 2D<14:54:59.096> an 14:54:59.990 --> 14:55:00.000 align:start position:0% welcome to module 9 lesson 2D an 14:55:00.000 --> 14:55:03.830 align:start position:0% welcome to module 9 lesson 2D an overview<14:55:00.360> of<14:55:00.660> GSM<14:55:01.320> CDMA<14:55:02.096> and<14:55:02.640> Y<14:55:02.880> Max<14:55:03.116> again 14:55:03.830 --> 14:55:03.840 align:start position:0% overview of GSM CDMA and Y Max again 14:55:03.840 --> 14:55:06.406 align:start position:0% overview of GSM CDMA and Y Max again we're<14:55:04.080> just<14:55:04.256> hitting<14:55:04.560> a<14:55:04.680> few<14:55:05.000> syllabus<14:55:06.000> topics 14:55:06.406 --> 14:55:06.416 align:start position:0% we're just hitting a few syllabus topics 14:55:06.416 --> 14:55:08.390 align:start position:0% we're just hitting a few syllabus topics that<14:55:06.840> comment<14:55:07.436> here<14:55:07.560> kind<14:55:07.860> of<14:55:07.980> mentioned<14:55:08.220> in 14:55:08.390 --> 14:55:08.400 align:start position:0% that comment here kind of mentioned in 14:55:08.400 --> 14:55:10.070 align:start position:0% that comment here kind of mentioned in passing<14:55:08.756> really<14:55:09.000> but<14:55:09.300> they<14:55:09.480> are<14:55:09.596> marked<14:55:09.956> down 14:55:10.070 --> 14:55:10.080 align:start position:0% passing really but they are marked down 14:55:10.080 --> 14:55:11.150 align:start position:0% passing really but they are marked down there 14:55:11.150 --> 14:55:11.160 align:start position:0% there 14:55:11.160 --> 14:55:13.850 align:start position:0% there look<14:55:11.756> at<14:55:11.936> what<14:55:12.240> is<14:55:12.416> 2G 14:55:13.850 --> 14:55:13.860 align:start position:0% look at what is 2G 14:55:13.860 --> 14:55:15.650 align:start position:0% look at what is 2G um<14:55:13.916> you<14:55:14.160> may<14:55:14.340> have<14:55:14.520> be<14:55:14.880> familiar<14:55:15.300> with<14:55:15.360> it<14:55:15.480> if 14:55:15.650 --> 14:55:15.660 align:start position:0% um you may have be familiar with it if 14:55:15.660 --> 14:55:18.470 align:start position:0% um you may have be familiar with it if you've<14:55:15.840> had<14:55:15.956> a<14:55:16.256> a<14:55:16.916> mobile<14:55:17.160> phone<14:55:17.580> or<14:55:18.116> I<14:55:18.360> think 14:55:18.470 --> 14:55:18.480 align:start position:0% you've had a a mobile phone or I think 14:55:18.480 --> 14:55:20.690 align:start position:0% you've had a a mobile phone or I think you<14:55:18.596> call<14:55:18.776> them<14:55:18.900> cellular<14:55:19.320> phones<14:55:20.040> in<14:55:20.700> um 14:55:20.690 --> 14:55:20.700 align:start position:0% you call them cellular phones in um 14:55:20.700 --> 14:55:22.850 align:start position:0% you call them cellular phones in um America<14:55:21.596> perhaps 14:55:22.850 --> 14:55:22.860 align:start position:0% America perhaps 14:55:22.860 --> 14:55:25.670 align:start position:0% America perhaps enhanced<14:55:23.580> rates<14:55:23.880> for<14:55:24.116> GSM 14:55:25.670 --> 14:55:25.680 align:start position:0% enhanced rates for GSM 14:55:25.680 --> 14:55:30.650 align:start position:0% enhanced rates for GSM LTE<14:55:26.520> long-term<14:55:27.300> Evolution<14:55:27.720> and<14:55:28.200> CDMA 14:55:30.650 --> 14:55:30.660 align:start position:0% LTE long-term Evolution and CDMA 14:55:30.660 --> 14:55:33.350 align:start position:0% LTE long-term Evolution and CDMA so<14:55:31.140> what<14:55:31.320> is<14:55:31.500> it<14:55:31.680> it<14:55:32.400> stands<14:55:32.820> for<14:55:32.880> global 14:55:33.350 --> 14:55:33.360 align:start position:0% so what is it it stands for global 14:55:33.360 --> 14:55:36.106 align:start position:0% so what is it it stands for global system<14:55:33.596> for<14:55:34.080> mobile<14:55:34.320> Communications 14:55:36.106 --> 14:55:36.116 align:start position:0% system for mobile Communications 14:55:36.116 --> 14:55:38.446 align:start position:0% system for mobile Communications I<14:55:36.416> used<14:55:36.540> to<14:55:36.720> actually<14:55:36.840> be<14:55:37.080> able<14:55:37.320> to<14:55:37.436> plug<14:55:37.916> an 14:55:38.446 --> 14:55:38.456 align:start position:0% I used to actually be able to plug an 14:55:38.456 --> 14:55:39.730 align:start position:0% I used to actually be able to plug an adapter 14:55:39.730 --> 14:55:39.740 align:start position:0% adapter 14:55:39.740 --> 14:55:42.230 align:start position:0% adapter into<14:55:40.740> your 14:55:42.230 --> 14:55:42.240 align:start position:0% into your 14:55:42.240 --> 14:55:44.746 align:start position:0% into your um<14:55:42.596> a<14:55:43.436> laptop 14:55:44.746 --> 14:55:44.756 align:start position:0% um a laptop 14:55:44.756 --> 14:55:49.130 align:start position:0% um a laptop and<14:55:45.480> use<14:55:45.840> a<14:55:46.080> GSM<14:55:46.616> card<14:55:47.040> for<14:55:48.000> accessing<14:55:48.596> the 14:55:49.130 --> 14:55:49.140 align:start position:0% and use a GSM card for accessing the 14:55:49.140 --> 14:55:51.650 align:start position:0% and use a GSM card for accessing the internet<14:55:49.380> but<14:55:49.800> it<14:55:49.916> was<14:55:50.096> pretty<14:55:50.756> slow<14:55:51.116> my 14:55:51.650 --> 14:55:51.660 align:start position:0% internet but it was pretty slow my 14:55:51.660 --> 14:55:53.510 align:start position:0% internet but it was pretty slow my experience<14:55:52.020> was<14:55:52.256> pretty<14:55:52.500> unreliable<14:55:53.040> and 14:55:53.510 --> 14:55:53.520 align:start position:0% experience was pretty unreliable and 14:55:53.520 --> 14:55:56.690 align:start position:0% experience was pretty unreliable and pretty<14:55:53.900> expensive<14:55:54.900> so<14:55:55.200> not<14:55:55.436> fantastic<14:55:55.860> but<14:55:56.700> um 14:55:56.690 --> 14:55:56.700 align:start position:0% pretty expensive so not fantastic but um 14:55:56.700 --> 14:55:58.606 align:start position:0% pretty expensive so not fantastic but um if<14:55:57.060> you<14:55:57.180> were<14:55:57.300> desperate<14:55:57.596> it<14:55:57.840> kind<14:55:58.200> of<14:55:58.256> did<14:55:58.436> the 14:55:58.606 --> 14:55:58.616 align:start position:0% if you were desperate it kind of did the 14:55:58.616 --> 14:56:01.310 align:start position:0% if you were desperate it kind of did the job<14:55:58.800> developed<14:55:59.700> by<14:55:59.820> European<14:56:00.720> Telecom 14:56:01.310 --> 14:56:01.320 align:start position:0% job developed by European Telecom 14:56:01.320 --> 14:56:03.230 align:start position:0% job developed by European Telecom standards<14:56:01.916> Institute 14:56:03.230 --> 14:56:03.240 align:start position:0% standards Institute 14:56:03.240 --> 14:56:04.130 align:start position:0% standards Institute Etsy 14:56:04.130 --> 14:56:04.140 align:start position:0% Etsy 14:56:04.140 --> 14:56:06.050 align:start position:0% Etsy and<14:56:04.560> this<14:56:04.800> is<14:56:04.860> the<14:56:05.096> protocols<14:56:05.700> for<14:56:05.756> second 14:56:06.050 --> 14:56:06.060 align:start position:0% and this is the protocols for second 14:56:06.060 --> 14:56:08.990 align:start position:0% and this is the protocols for second generation<14:56:06.596> the<14:56:07.020> 2G<14:56:07.380> cellular<14:56:08.000> networks 14:56:08.990 --> 14:56:09.000 align:start position:0% generation the 2G cellular networks 14:56:09.000 --> 14:56:11.926 align:start position:0% generation the 2G cellular networks digital<14:56:09.416> used<14:56:09.956> by<14:56:10.200> mobiles 14:56:11.926 --> 14:56:11.936 align:start position:0% digital used by mobiles 14:56:11.936 --> 14:56:13.850 align:start position:0% digital used by mobiles the<14:56:12.480> original<14:56:12.660> standard<14:56:13.200> was<14:56:13.320> for<14:56:13.500> 2G 14:56:13.850 --> 14:56:13.860 align:start position:0% the original standard was for 2G 14:56:13.860 --> 14:56:15.650 align:start position:0% the original standard was for 2G Wireless<14:56:14.096> telephone<14:56:14.520> technology<14:56:15.180> and<14:56:15.596> it 14:56:15.650 --> 14:56:15.660 align:start position:0% Wireless telephone technology and it 14:56:15.660 --> 14:56:17.630 align:start position:0% Wireless telephone technology and it became<14:56:15.956> the<14:56:16.080> global<14:56:16.436> standard<14:56:16.860> for<14:56:17.340> mobile 14:56:17.630 --> 14:56:17.640 align:start position:0% became the global standard for mobile 14:56:17.640 --> 14:56:21.370 align:start position:0% became the global standard for mobile Communications<14:56:18.416> a<14:56:19.020> bit<14:56:19.140> left<14:56:19.320> behind<14:56:19.680> now 14:56:21.370 --> 14:56:21.380 align:start position:0% Communications a bit left behind now 14:56:21.380 --> 14:56:24.350 align:start position:0% Communications a bit left behind now so<14:56:22.380> GSM<14:56:22.860> is<14:56:23.040> a<14:56:23.160> cellular<14:56:23.400> network<14:56:23.756> that<14:56:24.060> uses 14:56:24.350 --> 14:56:24.360 align:start position:0% so GSM is a cellular network that uses 14:56:24.360 --> 14:56:27.106 align:start position:0% so GSM is a cellular network that uses radio<14:56:24.596> signals<14:56:25.256> for<14:56:25.500> mobile<14:56:25.680> and<14:56:26.456> mobile 14:56:27.106 --> 14:56:27.116 align:start position:0% radio signals for mobile and mobile 14:56:27.116 --> 14:56:28.426 align:start position:0% radio signals for mobile and mobile comms 14:56:28.426 --> 14:56:28.436 align:start position:0% comms 14:56:28.436 --> 14:56:30.290 align:start position:0% comms the<14:56:28.800> cellular<14:56:29.160> network<14:56:29.400> is<14:56:29.700> a<14:56:29.880> mobile<14:56:30.000> network 14:56:30.290 --> 14:56:30.300 align:start position:0% the cellular network is a mobile network 14:56:30.300 --> 14:56:31.850 align:start position:0% the cellular network is a mobile network that<14:56:30.596> is<14:56:30.776> spread<14:56:31.020> across<14:56:31.320> the<14:56:31.436> land<14:56:31.616> area 14:56:31.850 --> 14:56:31.860 align:start position:0% that is spread across the land area 14:56:31.860 --> 14:56:33.710 align:start position:0% that is spread across the land area called<14:56:32.220> cells 14:56:33.710 --> 14:56:33.720 align:start position:0% called cells 14:56:33.720 --> 14:56:35.870 align:start position:0% called cells one<14:56:34.140> or<14:56:34.320> more<14:56:34.500> fixed<14:56:34.860> transceivers<14:56:35.456> or<14:56:35.640> base 14:56:35.870 --> 14:56:35.880 align:start position:0% one or more fixed transceivers or base 14:56:35.880 --> 14:56:37.790 align:start position:0% one or more fixed transceivers or base stations<14:56:36.360> were<14:56:36.660> probably<14:56:36.900> more<14:56:37.200> familiar 14:56:37.790 --> 14:56:37.800 align:start position:0% stations were probably more familiar 14:56:37.800 --> 14:56:39.766 align:start position:0% stations were probably more familiar with<14:56:37.980> they<14:56:38.640> provide<14:56:38.936> each<14:56:39.116> cell<14:56:39.360> with<14:56:39.596> network 14:56:39.766 --> 14:56:39.776 align:start position:0% with they provide each cell with network 14:56:39.776 --> 14:56:41.926 align:start position:0% with they provide each cell with network coverage<14:56:40.380> obviously 14:56:41.926 --> 14:56:41.936 align:start position:0% coverage obviously 14:56:41.936 --> 14:56:43.670 align:start position:0% coverage obviously the<14:56:42.360> further<14:56:42.596> away<14:56:42.720> you<14:56:42.956> are<14:56:43.140> from<14:56:43.256> these<14:56:43.500> base 14:56:43.670 --> 14:56:43.680 align:start position:0% the further away you are from these base 14:56:43.680 --> 14:56:45.586 align:start position:0% the further away you are from these base stations<14:56:44.160> the<14:56:44.340> poorier<14:56:44.756> signal<14:56:45.180> light<14:56:45.360> is 14:56:45.586 --> 14:56:45.596 align:start position:0% stations the poorier signal light is 14:56:45.596 --> 14:56:47.330 align:start position:0% stations the poorier signal light is until<14:56:45.776> at<14:56:46.080> some<14:56:46.256> point<14:56:46.500> you'll<14:56:47.040> have<14:56:47.160> no 14:56:47.330 --> 14:56:47.340 align:start position:0% until at some point you'll have no 14:56:47.340 --> 14:56:50.746 align:start position:0% until at some point you'll have no signal<14:56:47.700> at<14:56:47.936> all 14:56:50.746 --> 14:56:50.756 align:start position:0% 14:56:50.756 --> 14:56:52.670 align:start position:0% um<14:56:50.820> we<14:56:51.116> commonly<14:56:51.416> call<14:56:51.596> them<14:56:51.776> mobile<14:56:52.020> phones 14:56:52.670 --> 14:56:52.680 align:start position:0% um we commonly call them mobile phones 14:56:52.680 --> 14:56:58.570 align:start position:0% um we commonly call them mobile phones during<14:56:53.640> the<14:56:53.880> cellular<14:56:54.300> network<14:56:54.900> calls 14:56:58.570 --> 14:56:58.580 align:start position:0% 14:56:58.580 --> 14:57:01.130 align:start position:0% all<14:56:59.580> right<14:56:59.700> so<14:56:59.936> what<14:57:00.180> is<14:57:00.360> 2G<14:57:00.776> second 14:57:01.130 --> 14:57:01.140 align:start position:0% all right so what is 2G second 14:57:01.140 --> 14:57:03.470 align:start position:0% all right so what is 2G second generation<14:57:01.616> as<14:57:01.916> we've<14:57:02.220> said<14:57:02.340> they<14:57:03.060> use<14:57:03.240> radio 14:57:03.470 --> 14:57:03.480 align:start position:0% generation as we've said they use radio 14:57:03.480 --> 14:57:05.446 align:start position:0% generation as we've said they use radio signals<14:57:04.020> developed<14:57:04.500> as<14:57:04.616> a<14:57:04.800> replacement<14:57:04.916> for 14:57:05.446 --> 14:57:05.456 align:start position:0% signals developed as a replacement for 14:57:05.456 --> 14:57:08.570 align:start position:0% signals developed as a replacement for the<14:57:05.700> old<14:57:06.116> cellular<14:57:06.956> network<14:57:07.320> they<14:57:07.680> used 14:57:08.570 --> 14:57:08.580 align:start position:0% the old cellular network they used 14:57:08.580 --> 14:57:11.446 align:start position:0% the old cellular network they used um<14:57:08.640> analog<14:57:09.480> radio<14:57:09.776> signals<14:57:10.560> so<14:57:11.040> that<14:57:11.160> was<14:57:11.340> a 14:57:11.446 --> 14:57:11.456 align:start position:0% um analog radio signals so that was a 14:57:11.456 --> 14:57:14.510 align:start position:0% um analog radio signals so that was a real<14:57:11.580> old<14:57:11.820> school<14:57:12.060> and<14:57:13.020> stuff 14:57:14.510 --> 14:57:14.520 align:start position:0% real old school and stuff 14:57:14.520 --> 14:57:17.150 align:start position:0% real old school and stuff they<14:57:14.936> were<14:57:15.116> quite<14:57:15.240> easily<14:57:15.596> hacked<14:57:16.200> into<14:57:16.320> at 14:57:17.150 --> 14:57:17.160 align:start position:0% they were quite easily hacked into at 14:57:17.160 --> 14:57:19.070 align:start position:0% they were quite easily hacked into at the<14:57:17.520> time<14:57:17.756> you<14:57:18.060> if<14:57:18.416> you<14:57:18.596> had<14:57:18.660> the<14:57:18.776> equipment 14:57:19.070 --> 14:57:19.080 align:start position:0% the time you if you had the equipment 14:57:19.080 --> 14:57:21.530 align:start position:0% the time you if you had the equipment you<14:57:19.256> could<14:57:19.380> listen<14:57:19.560> to<14:57:19.740> people's 14:57:21.530 --> 14:57:21.540 align:start position:0% you could listen to people's 14:57:21.540 --> 14:57:23.266 align:start position:0% you could listen to people's um<14:57:21.660> telephone<14:57:21.840> conversations<14:57:22.680> with<14:57:23.096> a 14:57:23.266 --> 14:57:23.276 align:start position:0% um telephone conversations with a 14:57:23.276 --> 14:57:25.850 align:start position:0% um telephone conversations with a scanner 14:57:25.850 --> 14:57:25.860 align:start position:0% 14:57:25.860 --> 14:57:28.130 align:start position:0% the<14:57:26.456> original<14:57:26.580> GSM<14:57:27.180> standard<14:57:27.660> was<14:57:27.840> actually 14:57:28.130 --> 14:57:28.140 align:start position:0% the original GSM standard was actually 14:57:28.140 --> 14:57:30.530 align:start position:0% the original GSM standard was actually designed<14:57:28.560> for<14:57:28.800> full<14:57:28.980> duplex<14:57:29.580> voice<14:57:29.880> telephony 14:57:30.530 --> 14:57:30.540 align:start position:0% designed for full duplex voice telephony 14:57:30.540 --> 14:57:33.130 align:start position:0% designed for full duplex voice telephony it<14:57:31.256> was<14:57:31.436> just<14:57:31.616> adopted<14:57:32.096> for<14:57:32.276> data<14:57:32.700> later<14:57:32.820> on 14:57:33.130 --> 14:57:33.140 align:start position:0% it was just adopted for data later on 14:57:33.140 --> 14:57:36.406 align:start position:0% it was just adopted for data later on originally<14:57:34.140> operated<14:57:34.560> at<14:57:34.860> 96<14:57:35.700> bits<14:57:36.360> per 14:57:36.406 --> 14:57:36.416 align:start position:0% originally operated at 96 bits per 14:57:36.416 --> 14:57:37.370 align:start position:0% originally operated at 96 bits per second 14:57:37.370 --> 14:57:37.380 align:start position:0% second 14:57:37.380 --> 14:57:39.830 align:start position:0% second which<14:57:37.800> is<14:57:37.916> pretty<14:57:38.160> darn<14:57:38.400> slow<14:57:38.720> evolved<14:57:39.720> over 14:57:39.830 --> 14:57:39.840 align:start position:0% which is pretty darn slow evolved over 14:57:39.840 --> 14:57:41.630 align:start position:0% which is pretty darn slow evolved over time<14:57:40.080> to<14:57:40.256> allow<14:57:40.500> Datacom<14:57:41.096> through<14:57:41.400> an 14:57:41.630 --> 14:57:41.640 align:start position:0% time to allow Datacom through an 14:57:41.640 --> 14:57:44.870 align:start position:0% time to allow Datacom through an enhanced<14:57:42.000> GSM<14:57:42.540> technology<14:57:43.140> called<14:57:43.616> Edge<14:57:44.580> or 14:57:44.870 --> 14:57:44.880 align:start position:0% enhanced GSM technology called Edge or 14:57:44.880 --> 14:57:49.790 align:start position:0% enhanced GSM technology called Edge or enhanced<14:57:45.360> data<14:57:45.776> rates<14:57:45.900> for<14:57:46.140> GSM<14:57:46.680> evolution 14:57:49.790 --> 14:57:49.800 align:start position:0% 14:57:49.800 --> 14:57:53.086 align:start position:0% this<14:57:50.340> was<14:57:50.456> considered<14:57:51.060> a<14:57:51.616> pre-3g<14:57:52.616> radio 14:57:53.086 --> 14:57:53.096 align:start position:0% this was considered a pre-3g radio 14:57:53.096 --> 14:57:54.766 align:start position:0% this was considered a pre-3g radio technology 14:57:54.766 --> 14:57:54.776 align:start position:0% technology 14:57:54.776 --> 14:57:58.730 align:start position:0% technology it's<14:57:54.900> part<14:57:55.200> of<14:57:55.380> the<14:57:55.560> itu's<14:57:56.276> 3G<14:57:56.700> definition<14:57:57.740> and 14:57:58.730 --> 14:57:58.740 align:start position:0% it's part of the itu's 3G definition and 14:57:58.740 --> 14:58:00.830 align:start position:0% it's part of the itu's 3G definition and the<14:57:58.916> idea<14:57:59.276> is<14:57:59.400> it<14:57:59.640> delivers<14:57:59.936> higher<14:58:00.300> rate<14:58:00.416> bits 14:58:00.830 --> 14:58:00.840 align:start position:0% the idea is it delivers higher rate bits 14:58:00.840 --> 14:58:03.470 align:start position:0% the idea is it delivers higher rate bits per<14:58:01.436> radio<14:58:01.740> channel<14:58:02.096> so<14:58:02.880> it's<14:58:03.060> three<14:58:03.300> times 14:58:03.470 --> 14:58:03.480 align:start position:0% per radio channel so it's three times 14:58:03.480 --> 14:58:06.946 align:start position:0% per radio channel so it's three times faster<14:58:03.840> than<14:58:04.160> ordinary<14:58:05.160> GSM<14:58:05.820> also<14:58:06.596> used<14:58:06.720> for 14:58:06.946 --> 14:58:06.956 align:start position:0% faster than ordinary GSM also used for 14:58:06.956 --> 14:58:09.350 align:start position:0% faster than ordinary GSM also used for internet<14:58:07.200> connections 14:58:09.350 --> 14:58:09.360 align:start position:0% internet connections 14:58:09.360 --> 14:58:12.710 align:start position:0% internet connections a<14:58:10.200> long-term<14:58:10.740> Evolution<14:58:11.040> LTE<14:58:11.880> is<14:58:12.416> today's 14:58:12.710 --> 14:58:12.720 align:start position:0% a long-term Evolution LTE is today's 14:58:12.720 --> 14:58:14.926 align:start position:0% a long-term Evolution LTE is today's mobile<14:58:13.080> networks<14:58:13.680> used<14:58:13.916> something<14:58:14.096> called<14:58:14.936> um 14:58:14.926 --> 14:58:14.936 align:start position:0% mobile networks used something called um 14:58:14.936 --> 14:58:16.970 align:start position:0% mobile networks used something called um LTE 14:58:16.970 --> 14:58:16.980 align:start position:0% LTE 14:58:16.980 --> 14:58:19.550 align:start position:0% LTE commonly<14:58:17.580> marketed<14:58:18.116> as<14:58:18.416> 4G<14:58:18.900> you<14:58:19.256> may<14:58:19.436> have 14:58:19.550 --> 14:58:19.560 align:start position:0% commonly marketed as 4G you may have 14:58:19.560 --> 14:58:22.906 align:start position:0% commonly marketed as 4G you may have heard<14:58:19.740> 4G<14:58:20.276> LTE 14:58:22.906 --> 14:58:22.916 align:start position:0% 14:58:22.916 --> 14:58:25.906 align:start position:0% high-speed<14:58:23.820> data<14:58:24.480> rate<14:58:24.596> access<14:58:24.900> based<14:58:25.500> on<14:58:25.616> the 14:58:25.906 --> 14:58:25.916 align:start position:0% high-speed data rate access based on the 14:58:25.916 --> 14:58:28.970 align:start position:0% high-speed data rate access based on the edge<14:58:26.096> and<14:58:26.340> HSPA<14:58:27.240> network<14:58:27.480> Technologies<14:58:28.256> which 14:58:28.970 --> 14:58:28.980 align:start position:0% edge and HSPA network Technologies which 14:58:28.980 --> 14:58:30.290 align:start position:0% edge and HSPA network Technologies which are<14:58:29.160> Legacy 14:58:30.290 --> 14:58:30.300 align:start position:0% are Legacy 14:58:30.300 --> 14:58:34.130 align:start position:0% are Legacy download<14:58:30.776> speed<14:58:31.256> is<14:58:31.500> 300<14:58:31.860> Meg<14:58:32.220> upload<14:58:32.756> is<14:58:33.180> 75 14:58:34.130 --> 14:58:34.140 align:start position:0% download speed is 300 Meg upload is 75 14:58:34.140 --> 14:58:37.070 align:start position:0% download speed is 300 Meg upload is 75 so<14:58:34.500> it's<14:58:34.680> asynchronous 14:58:37.070 --> 14:58:37.080 align:start position:0% so it's asynchronous 14:58:37.080 --> 14:58:42.050 align:start position:0% so it's asynchronous CDMA<14:58:37.980> is<14:58:38.456> code<14:58:38.756> division<14:58:39.680> multiple<14:58:40.680> access 14:58:42.050 --> 14:58:42.060 align:start position:0% CDMA is code division multiple access 14:58:42.060 --> 14:58:44.810 align:start position:0% CDMA is code division multiple access this<14:58:42.660> uses<14:58:42.956> a<14:58:43.200> special<14:58:43.500> spread<14:58:44.220> Spectrum 14:58:44.810 --> 14:58:44.820 align:start position:0% this uses a special spread Spectrum 14:58:44.820 --> 14:58:47.446 align:start position:0% this uses a special spread Spectrum technology<14:58:45.480> and<14:58:46.320> basically<14:58:46.680> the<14:58:46.860> idea<14:58:47.340> is 14:58:47.446 --> 14:58:47.456 align:start position:0% technology and basically the idea is 14:58:47.456 --> 14:58:49.246 align:start position:0% technology and basically the idea is multiple<14:58:47.936> users<14:58:48.416> can<14:58:48.660> communicate 14:58:49.246 --> 14:58:49.256 align:start position:0% multiple users can communicate 14:58:49.256 --> 14:58:51.050 align:start position:0% multiple users can communicate independently<14:58:49.860> but<14:58:50.400> using<14:58:50.756> the<14:58:50.936> same 14:58:51.050 --> 14:58:51.060 align:start position:0% independently but using the same 14:58:51.060 --> 14:58:53.390 align:start position:0% independently but using the same bandwidth<14:58:51.596> and<14:58:51.720> they<14:58:51.956> shouldn't<14:58:52.320> in<14:58:53.096> theory 14:58:53.390 --> 14:58:53.400 align:start position:0% bandwidth and they shouldn't in theory 14:58:53.400 --> 14:58:56.510 align:start position:0% bandwidth and they shouldn't in theory be<14:58:53.580> any<14:58:53.936> interference<14:58:54.480> on<14:58:54.720> the<14:58:54.840> connection 14:58:56.510 --> 14:58:56.520 align:start position:0% be any interference on the connection 14:58:56.520 --> 14:59:00.350 align:start position:0% be any interference on the connection uh<14:58:57.116> represents<14:58:57.776> a<14:58:57.956> second<14:58:58.500> generation<14:58:59.360> 2G 14:59:00.350 --> 14:59:00.360 align:start position:0% uh represents a second generation 2G 14:59:00.360 --> 14:59:03.650 align:start position:0% uh represents a second generation 2G Digital<14:59:00.900> radio<14:59:01.320> solution 14:59:03.650 --> 14:59:03.660 align:start position:0% Digital radio solution 14:59:03.660 --> 14:59:06.406 align:start position:0% Digital radio solution uses<14:59:04.380> the<14:59:04.680> spectrally<14:59:05.276> efficient<14:59:05.936> technology 14:59:06.406 --> 14:59:06.416 align:start position:0% uses the spectrally efficient technology 14:59:06.416 --> 14:59:09.406 align:start position:0% uses the spectrally efficient technology for<14:59:06.956> mobile<14:59:07.256> communication 14:59:09.406 --> 14:59:09.416 align:start position:0% for mobile communication 14:59:09.416 --> 14:59:11.990 align:start position:0% for mobile communication all<14:59:09.840> right<14:59:10.020> moving<14:59:10.320> on<14:59:10.436> to<14:59:10.616> Y<14:59:10.800> Max 14:59:11.990 --> 14:59:12.000 align:start position:0% all right moving on to Y Max 14:59:12.000 --> 14:59:15.350 align:start position:0% all right moving on to Y Max worldwide<14:59:12.956> interrupt<14:59:13.936> interoperability<14:59:14.936> for 14:59:15.350 --> 14:59:15.360 align:start position:0% worldwide interrupt interoperability for 14:59:15.360 --> 14:59:17.266 align:start position:0% worldwide interrupt interoperability for microwave<14:59:16.020> access<14:59:16.320> now<14:59:16.740> what<14:59:16.980> do<14:59:17.096> they've 14:59:17.266 --> 14:59:17.276 align:start position:0% microwave access now what do they've 14:59:17.276 --> 14:59:19.850 align:start position:0% microwave access now what do they've shortened<14:59:17.640> that<14:59:17.756> one<14:59:18.320> technology<14:59:19.320> is<14:59:19.560> based 14:59:19.850 --> 14:59:19.860 align:start position:0% shortened that one technology is based 14:59:19.860 --> 14:59:22.490 align:start position:0% shortened that one technology is based on<14:59:20.060> 802.16<14:59:21.060> standard<14:59:21.480> which<14:59:21.776> you<14:59:21.956> can<14:59:22.200> look<14:59:22.320> up 14:59:22.490 --> 14:59:22.500 align:start position:0% on 802.16 standard which you can look up 14:59:22.500 --> 14:59:23.810 align:start position:0% on 802.16 standard which you can look up in<14:59:22.680> your<14:59:22.800> own<14:59:22.980> time 14:59:23.810 --> 14:59:23.820 align:start position:0% in your own time 14:59:23.820 --> 14:59:26.390 align:start position:0% in your own time it<14:59:24.540> delivers<14:59:25.140> a<14:59:25.436> wireless<14:59:25.680> Broadband 14:59:26.390 --> 14:59:26.400 align:start position:0% it delivers a wireless Broadband 14:59:26.400 --> 14:59:28.790 align:start position:0% it delivers a wireless Broadband Services<14:59:26.700> anytime<14:59:27.540> and<14:59:27.840> anywhere 14:59:28.790 --> 14:59:28.800 align:start position:0% Services anytime and anywhere 14:59:28.800 --> 14:59:32.330 align:start position:0% Services anytime and anywhere here's<14:59:29.456> an<14:59:29.580> image<14:59:29.820> from<14:59:30.240> conique.com 14:59:32.330 --> 14:59:32.340 align:start position:0% here's an image from conique.com 14:59:32.340 --> 14:59:35.870 align:start position:0% here's an image from conique.com of<14:59:33.000> indirect<14:59:33.540> access<14:59:33.956> with<14:59:34.500> the<14:59:34.880> outdoor 14:59:35.870 --> 14:59:35.880 align:start position:0% of indirect access with the outdoor 14:59:35.880 --> 14:59:37.670 align:start position:0% of indirect access with the outdoor customer<14:59:36.060> premise<14:59:36.660> equipment<14:59:37.020> connecting 14:59:37.670 --> 14:59:37.680 align:start position:0% customer premise equipment connecting 14:59:37.680 --> 14:59:39.766 align:start position:0% customer premise equipment connecting through<14:59:38.340> a<14:59:38.520> base<14:59:38.640> station<14:59:38.880> when<14:59:39.180> you've<14:59:39.360> got<14:59:39.480> a 14:59:39.766 --> 14:59:39.776 align:start position:0% through a base station when you've got a 14:59:39.776 --> 14:59:40.730 align:start position:0% through a base station when you've got a poor 14:59:40.730 --> 14:59:40.740 align:start position:0% poor 14:59:40.740 --> 14:59:43.010 align:start position:0% poor um<14:59:40.800> connectivity<14:59:41.580> and<14:59:42.360> but<14:59:42.540> you've<14:59:42.720> got<14:59:42.776> the 14:59:43.010 --> 14:59:43.020 align:start position:0% um connectivity and but you've got the 14:59:43.020 --> 14:59:46.010 align:start position:0% um connectivity and but you've got the signal<14:59:43.256> goes<14:59:43.560> through<14:59:43.616> multiple<14:59:44.040> paths 14:59:46.010 --> 14:59:46.020 align:start position:0% signal goes through multiple paths 14:59:46.020 --> 14:59:48.766 align:start position:0% signal goes through multiple paths uh<14:59:46.680> the<14:59:46.800> 802.16<14:59:47.700> standard<14:59:48.060> is<14:59:48.300> developed<14:59:48.596> for 14:59:48.766 --> 14:59:48.776 align:start position:0% uh the 802.16 standard is developed for 14:59:48.776 --> 14:59:51.106 align:start position:0% uh the 802.16 standard is developed for providing<14:59:49.320> an<14:59:49.560> online<14:59:49.740> science<14:59:50.400> connectivity 14:59:51.106 --> 14:59:51.116 align:start position:0% providing an online science connectivity 14:59:51.116 --> 14:59:54.586 align:start position:0% providing an online science connectivity so<14:59:51.956> it'd<14:59:52.140> be<14:59:52.256> quite<14:59:52.436> useful<14:59:52.740> in<14:59:53.400> um 14:59:54.586 --> 14:59:54.596 align:start position:0% so it'd be quite useful in um 14:59:54.596 --> 14:59:56.630 align:start position:0% so it'd be quite useful in um areas<14:59:55.380> where<14:59:55.560> there's<14:59:55.680> a<14:59:55.860> lot<14:59:55.916> of<14:59:56.040> buildings 14:59:56.630 --> 14:59:56.640 align:start position:0% areas where there's a lot of buildings 14:59:56.640 --> 14:59:59.086 align:start position:0% areas where there's a lot of buildings and<14:59:57.000> things<14:59:57.660> in<14:59:57.900> the<14:59:58.080> way<14:59:58.200> trees<14:59:58.800> and<14:59:58.980> other 14:59:59.086 --> 14:59:59.096 align:start position:0% and things in the way trees and other 14:59:59.096 --> 15:00:00.946 align:start position:0% and things in the way trees and other buildings<14:59:59.520> and<14:59:59.756> antennas 15:00:00.946 --> 15:00:00.956 align:start position:0% buildings and antennas 15:00:00.956 --> 15:00:02.926 align:start position:0% buildings and antennas why<15:00:01.436> Max<15:00:01.740> is<15:00:01.980> sometimes<15:00:02.340> referred<15:00:02.700> to<15:00:02.756> as 15:00:02.926 --> 15:00:02.936 align:start position:0% why Max is sometimes referred to as 15:00:02.936 --> 15:00:06.106 align:start position:0% why Max is sometimes referred to as Wi-Fi<15:00:03.300> on<15:00:03.596> steroids<15:00:04.276> similar<15:00:05.276> to<15:00:05.456> Wi-Fi<15:00:05.756> but 15:00:06.106 --> 15:00:06.116 align:start position:0% Wi-Fi on steroids similar to Wi-Fi but 15:00:06.116 --> 15:00:08.210 align:start position:0% Wi-Fi on steroids similar to Wi-Fi but can<15:00:06.660> provide<15:00:06.956> Broadband<15:00:07.380> access<15:00:07.616> to<15:00:07.916> a<15:00:08.096> large 15:00:08.210 --> 15:00:08.220 align:start position:0% can provide Broadband access to a large 15:00:08.220 --> 15:00:11.150 align:start position:0% can provide Broadband access to a large area<15:00:08.720> supports<15:00:09.720> Communications<15:00:10.256> over<15:00:10.800> a 15:00:11.150 --> 15:00:11.160 align:start position:0% area supports Communications over a 15:00:11.160 --> 15:00:15.470 align:start position:0% area supports Communications over a maximum<15:00:11.820> of<15:00:12.000> 30<15:00:12.240> mile<15:00:12.540> radius 15:00:15.470 --> 15:00:15.480 align:start position:0% 15:00:15.480 --> 15:00:17.926 align:start position:0% there<15:00:16.020> are<15:00:16.200> other<15:00:16.380> available<15:00:17.096> for<15:00:17.520> fixed 15:00:17.926 --> 15:00:17.936 align:start position:0% there are other available for fixed 15:00:17.936 --> 15:00:21.710 align:start position:0% there are other available for fixed usage<15:00:18.300> or<15:00:18.720> mobile 15:00:21.710 --> 15:00:21.720 align:start position:0% 15:00:21.720 --> 15:00:24.350 align:start position:0% so<15:00:22.200> why<15:00:22.436> Max<15:00:22.680> is<15:00:22.980> the<15:00:23.340> standard<15:00:23.880> which<15:00:24.180> we've 15:00:24.350 --> 15:00:24.360 align:start position:0% so why Max is the standard which we've 15:00:24.360 --> 15:00:27.050 align:start position:0% so why Max is the standard which we've already<15:00:24.416> said<15:00:24.720> download<15:00:25.380> speed<15:00:25.860> is<15:00:26.160> up<15:00:26.340> to<15:00:26.456> 37 15:00:27.050 --> 15:00:27.060 align:start position:0% already said download speed is up to 37 15:00:27.060 --> 15:00:33.190 align:start position:0% already said download speed is up to 37 Meg<15:00:27.596> and<15:00:27.776> the<15:00:27.900> upload<15:00:28.200> speed<15:00:28.436> is<15:00:28.680> up<15:00:28.916> to<15:00:29.160> 17. 15:00:33.190 --> 15:00:33.200 align:start position:0% 15:00:33.200 --> 15:00:36.670 align:start position:0% mobile<15:00:34.200> y<15:00:34.616> next<15:00:34.800> is<15:00:35.160> based<15:00:35.520> on<15:00:35.640> the 15:00:36.670 --> 15:00:36.680 align:start position:0% mobile y next is based on the 15:00:36.680 --> 15:00:41.210 align:start position:0% mobile y next is based on the 802.16a<15:00:37.680> standard<15:00:38.340> from<15:00:38.580> 2005.<15:00:40.080> and<15:00:40.560> this<15:00:40.800> the 15:00:41.210 --> 15:00:41.220 align:start position:0% 802.16a standard from 2005. and this the 15:00:41.220 --> 15:00:44.570 align:start position:0% 802.16a standard from 2005. and this the got<15:00:41.456> a<15:00:41.580> throughput<15:00:41.880> of<15:00:42.180> up<15:00:42.360> to<15:00:42.596> 100<15:00:42.840> Meg 15:00:44.570 --> 15:00:44.580 align:start position:0% got a throughput of up to 100 Meg 15:00:44.580 --> 15:00:47.086 align:start position:0% got a throughput of up to 100 Meg so<15:00:45.000> we've<15:00:45.116> covered<15:00:45.416> in<15:00:45.596> brief<15:00:45.900> GSM<15:00:46.500> 2G 15:00:47.086 --> 15:00:47.096 align:start position:0% so we've covered in brief GSM 2G 15:00:47.096 --> 15:00:49.670 align:start position:0% so we've covered in brief GSM 2G enhanced<15:00:47.756> data<15:00:48.060> rates<15:00:48.240> for<15:00:48.416> GSM 15:00:49.670 --> 15:00:49.680 align:start position:0% enhanced data rates for GSM 15:00:49.680 --> 15:00:54.230 align:start position:0% enhanced data rates for GSM LTE<15:00:50.596> CDMA<15:00:51.596> and<15:00:52.436> Y<15:00:52.616> Max<15:00:52.916> that's<15:00:53.700> all<15:00:53.880> for<15:00:54.060> now 15:00:54.230 --> 15:00:54.240 align:start position:0% LTE CDMA and Y Max that's all for now 15:00:54.240 --> 15:00:59.920 align:start position:0% LTE CDMA and Y Max that's all for now thanks<15:00:54.720> for<15:00:54.840> listening 15:00:59.920 --> 15:00:59.930 align:start position:0% 15:00:59.930 --> 15:01:19.630 align:start position:0% [Music] 15:01:19.630 --> 15:01:19.640 align:start position:0% 15:01:19.640 --> 15:01:23.870 align:start position:0% wide<15:01:20.640> area<15:01:21.000> networks<15:01:21.720> Wan<15:01:22.680> connectivity<15:01:23.276> and 15:01:23.870 --> 15:01:23.880 align:start position:0% wide area networks Wan connectivity and 15:01:23.880 --> 15:01:26.030 align:start position:0% wide area networks Wan connectivity and voice<15:01:24.060> over<15:01:24.360> IP 15:01:26.030 --> 15:01:26.040 align:start position:0% voice over IP 15:01:26.040 --> 15:01:28.190 align:start position:0% voice over IP in<15:01:26.456> the<15:01:26.580> last<15:01:26.700> module<15:01:27.180> we<15:01:27.660> discussed<15:01:28.080> the 15:01:28.190 --> 15:01:28.200 align:start position:0% in the last module we discussed the 15:01:28.200 --> 15:01:30.710 align:start position:0% in the last module we discussed the different<15:01:28.436> types<15:01:28.860> of<15:01:29.096> Wan<15:01:29.580> switching<15:01:30.116> and<15:01:30.540> the 15:01:30.710 --> 15:01:30.720 align:start position:0% different types of Wan switching and the 15:01:30.720 --> 15:01:33.230 align:start position:0% different types of Wan switching and the different<15:01:30.900> transmission<15:01:31.520> technologies<15:01:32.520> some 15:01:33.230 --> 15:01:33.240 align:start position:0% different transmission technologies some 15:01:33.240 --> 15:01:34.730 align:start position:0% different transmission technologies some of<15:01:33.360> which<15:01:33.480> are<15:01:33.596> going<15:01:33.776> to<15:01:33.900> reappear<15:01:34.320> in<15:01:34.560> this 15:01:34.730 --> 15:01:34.740 align:start position:0% of which are going to reappear in this 15:01:34.740 --> 15:01:37.926 align:start position:0% of which are going to reappear in this module<15:01:35.220> that's<15:01:35.820> because<15:01:36.320> uh<15:01:37.320> transmission 15:01:37.926 --> 15:01:37.936 align:start position:0% module that's because uh transmission 15:01:37.936 --> 15:01:40.606 align:start position:0% module that's because uh transmission technologies<15:01:38.936> and<15:01:39.596> connectivity<15:01:40.256> options 15:01:40.606 --> 15:01:40.616 align:start position:0% technologies and connectivity options 15:01:40.616 --> 15:01:43.246 align:start position:0% technologies and connectivity options are<15:01:40.800> going<15:01:40.916> to<15:01:41.040> go<15:01:41.220> hand<15:01:41.520> in<15:01:41.700> hand<15:01:41.956> so<15:01:42.956> we're 15:01:43.246 --> 15:01:43.256 align:start position:0% are going to go hand in hand so we're 15:01:43.256 --> 15:01:45.470 align:start position:0% are going to go hand in hand so we're going<15:01:43.436> to<15:01:43.616> talk<15:01:43.860> about<15:01:44.456> some<15:01:44.820> of<15:01:44.936> the<15:01:45.060> WAN 15:01:45.470 --> 15:01:45.480 align:start position:0% going to talk about some of the WAN 15:01:45.480 --> 15:01:47.106 align:start position:0% going to talk about some of the WAN connectivity<15:01:46.080> options<15:01:46.500> that<15:01:46.740> we<15:01:46.916> have 15:01:47.106 --> 15:01:47.116 align:start position:0% connectivity options that we have 15:01:47.116 --> 15:01:49.790 align:start position:0% connectivity options that we have including<15:01:48.116> a<15:01:48.480> least<15:01:48.660> line 15:01:49.790 --> 15:01:49.800 align:start position:0% including a least line 15:01:49.800 --> 15:01:53.086 align:start position:0% including a least line packet<15:01:50.640> switching<15:01:51.116> which<15:01:51.900> is<15:01:52.200> different<15:01:52.436> from 15:01:53.086 --> 15:01:53.096 align:start position:0% packet switching which is different from 15:01:53.096 --> 15:01:56.330 align:start position:0% packet switching which is different from circuit<15:01:53.756> switching<15:01:54.116> we've<15:01:54.360> seen<15:01:54.480> in<15:01:54.660> the<15:01:54.776> past 15:01:56.330 --> 15:01:56.340 align:start position:0% circuit switching we've seen in the past 15:01:56.340 --> 15:01:59.510 align:start position:0% circuit switching we've seen in the past something<15:01:56.820> called<15:01:57.180> cell<15:01:57.776> relay<15:01:58.320> which<15:01:58.980> is<15:01:59.220> the 15:01:59.510 --> 15:01:59.520 align:start position:0% something called cell relay which is the 15:01:59.520 --> 15:02:03.106 align:start position:0% something called cell relay which is the name<15:01:59.700> implies<15:02:00.416> it's<15:02:00.720> related<15:02:01.080> to<15:02:01.436> ATM 15:02:03.106 --> 15:02:03.116 align:start position:0% name implies it's related to ATM 15:02:03.116 --> 15:02:05.150 align:start position:0% name implies it's related to ATM and<15:02:03.480> then<15:02:03.596> we're<15:02:03.720> going<15:02:03.900> to<15:02:03.956> discuss<15:02:04.380> briefly 15:02:05.150 --> 15:02:05.160 align:start position:0% and then we're going to discuss briefly 15:02:05.160 --> 15:02:07.310 align:start position:0% and then we're going to discuss briefly voice<15:02:05.756> over<15:02:06.060> IP<15:02:06.540> which<15:02:06.900> is<15:02:06.956> something<15:02:07.140> that 15:02:07.310 --> 15:02:07.320 align:start position:0% voice over IP which is something that 15:02:07.320 --> 15:02:09.406 align:start position:0% voice over IP which is something that will<15:02:07.436> come<15:02:07.616> up<15:02:07.740> again<15:02:08.040> but<15:02:08.640> which<15:02:08.936> is<15:02:09.116> more<15:02:09.300> and 15:02:09.406 --> 15:02:09.416 align:start position:0% will come up again but which is more and 15:02:09.416 --> 15:02:11.746 align:start position:0% will come up again but which is more and more<15:02:09.596> become<15:02:09.956> a<15:02:10.140> necessary<15:02:10.616> part<15:02:11.160> of<15:02:11.640> our 15:02:11.746 --> 15:02:11.756 align:start position:0% more become a necessary part of our 15:02:11.756 --> 15:02:15.650 align:start position:0% more become a necessary part of our networks<15:02:12.300> that<15:02:12.840> is<15:02:13.140> making<15:02:13.980> phone<15:02:14.340> calls<15:02:14.880> over 15:02:15.650 --> 15:02:15.660 align:start position:0% networks that is making phone calls over 15:02:15.660 --> 15:02:18.830 align:start position:0% networks that is making phone calls over our<15:02:16.500> internet<15:02:16.980> Network<15:02:17.580> or<15:02:18.060> our<15:02:18.300> ethernet 15:02:18.830 --> 15:02:18.840 align:start position:0% our internet Network or our ethernet 15:02:18.840 --> 15:02:22.070 align:start position:0% our internet Network or our ethernet Network<15:02:19.096> rather<15:02:20.096> than<15:02:20.276> over<15:02:20.880> the<15:02:21.300> plain<15:02:21.596> old 15:02:22.070 --> 15:02:22.080 align:start position:0% Network rather than over the plain old 15:02:22.080 --> 15:02:24.766 align:start position:0% Network rather than over the plain old telephone<15:02:22.436> system<15:02:22.980> or<15:02:23.700> public<15:02:24.360> switch 15:02:24.766 --> 15:02:24.776 align:start position:0% telephone system or public switch 15:02:24.776 --> 15:02:27.766 align:start position:0% telephone system or public switch telephone<15:02:25.320> Network<15:02:25.800> and<15:02:26.640> just<15:02:26.936> to<15:02:27.240> recall 15:02:27.766 --> 15:02:27.776 align:start position:0% telephone Network and just to recall 15:02:27.776 --> 15:02:31.790 align:start position:0% telephone Network and just to recall that's<15:02:28.436> either<15:02:28.680> called<15:02:28.980> pots<15:02:29.640> or<15:02:30.240> pstn<15:02:31.200> that 15:02:31.790 --> 15:02:31.800 align:start position:0% that's either called pots or pstn that 15:02:31.800 --> 15:02:34.246 align:start position:0% that's either called pots or pstn that was<15:02:31.980> the<15:02:32.160> phone<15:02:32.276> network<15:02:32.580> we<15:02:33.000> used<15:02:33.116> for<15:02:33.596> lots 15:02:34.246 --> 15:02:34.256 align:start position:0% was the phone network we used for lots 15:02:34.256 --> 15:02:36.170 align:start position:0% was the phone network we used for lots and<15:02:34.380> lots<15:02:34.616> of<15:02:34.680> years<15:02:34.860> until<15:02:35.520> we<15:02:35.880> started 15:02:36.170 --> 15:02:36.180 align:start position:0% and lots of years until we started 15:02:36.180 --> 15:02:40.730 align:start position:0% and lots of years until we started getting<15:02:36.416> more<15:02:36.720> into<15:02:36.956> a<15:02:37.436> why<15:02:38.360> internet<15:02:39.740> wide 15:02:40.730 --> 15:02:40.740 align:start position:0% getting more into a why internet wide 15:02:40.740 --> 15:02:42.650 align:start position:0% getting more into a why internet wide world 15:02:42.650 --> 15:02:42.660 align:start position:0% world 15:02:42.660 --> 15:02:44.150 align:start position:0% world so 15:02:44.150 --> 15:02:44.160 align:start position:0% so 15:02:44.160 --> 15:02:46.550 align:start position:0% so when<15:02:44.756> we<15:02:44.880> talk<15:02:45.060> about<15:02:45.240> voice<15:02:45.540> over<15:02:45.776> IP<15:02:46.200> I<15:02:46.436> want 15:02:46.550 --> 15:02:46.560 align:start position:0% when we talk about voice over IP I want 15:02:46.560 --> 15:02:48.406 align:start position:0% when we talk about voice over IP I want to<15:02:46.680> bring<15:02:46.800> up<15:02:46.980> a<15:02:47.276> very<15:02:47.456> important<15:02:48.000> protocol 15:02:48.406 --> 15:02:48.416 align:start position:0% to bring up a very important protocol 15:02:48.416 --> 15:02:52.190 align:start position:0% to bring up a very important protocol called<15:02:49.200> sip<15:02:49.740> if<15:02:50.400> you<15:02:50.580> see<15:02:50.756> sip<15:02:51.116> on<15:02:51.480> the<15:02:51.660> test<15:02:51.776> it 15:02:52.190 --> 15:02:52.200 align:start position:0% called sip if you see sip on the test it 15:02:52.200 --> 15:02:54.230 align:start position:0% called sip if you see sip on the test it is<15:02:52.320> going<15:02:52.500> to<15:02:52.680> be<15:02:52.800> directly<15:02:53.276> related<15:02:53.640> to<15:02:53.936> voice 15:02:54.230 --> 15:02:54.240 align:start position:0% is going to be directly related to voice 15:02:54.240 --> 15:02:56.926 align:start position:0% is going to be directly related to voice over<15:02:54.596> IP 15:02:56.926 --> 15:02:56.936 align:start position:0% over IP 15:02:56.936 --> 15:02:59.030 align:start position:0% over IP now<15:02:57.360> one<15:02:57.540> of<15:02:57.660> the<15:02:57.776> ways<15:02:58.200> in<15:02:58.380> which<15:02:58.560> wide<15:02:58.800> area 15:02:59.030 --> 15:02:59.040 align:start position:0% now one of the ways in which wide area 15:02:59.040 --> 15:03:00.830 align:start position:0% now one of the ways in which wide area networks<15:02:59.520> can<15:02:59.700> gain<15:02:59.880> connectivity<15:03:00.480> is 15:03:00.830 --> 15:03:00.840 align:start position:0% networks can gain connectivity is 15:03:00.840 --> 15:03:02.870 align:start position:0% networks can gain connectivity is through<15:03:01.020> a<15:03:01.200> leased<15:03:01.500> line<15:03:01.680> we've<15:03:02.160> seen<15:03:02.400> this<15:03:02.640> in 15:03:02.870 --> 15:03:02.880 align:start position:0% through a leased line we've seen this in 15:03:02.880 --> 15:03:06.650 align:start position:0% through a leased line we've seen this in the<15:03:03.060> past<15:03:03.180> module<15:03:03.776> at<15:03:04.436> least<15:03:04.616> line<15:03:05.040> is<15:03:05.820> sold<15:03:06.180> to 15:03:06.650 --> 15:03:06.660 align:start position:0% the past module at least line is sold to 15:03:06.660 --> 15:03:09.290 align:start position:0% the past module at least line is sold to a<15:03:06.840> company<15:03:07.020> for<15:03:07.500> a<15:03:07.560> set<15:03:07.740> amount<15:03:07.980> of<15:03:08.160> time<15:03:08.400> thus 15:03:09.290 --> 15:03:09.300 align:start position:0% a company for a set amount of time thus 15:03:09.300 --> 15:03:11.746 align:start position:0% a company for a set amount of time thus the<15:03:09.660> word<15:03:09.840> least 15:03:11.746 --> 15:03:11.756 align:start position:0% the word least 15:03:11.756 --> 15:03:15.490 align:start position:0% the word least now<15:03:12.360> a<15:03:12.596> least<15:03:12.776> line<15:03:13.640> provides<15:03:14.640> steady 15:03:15.490 --> 15:03:15.500 align:start position:0% now a least line provides steady 15:03:15.500 --> 15:03:18.710 align:start position:0% now a least line provides steady permanently<15:03:16.500> set<15:03:16.740> up<15:03:16.916> connection<15:03:17.160> such<15:03:18.060> as<15:03:18.300> a 15:03:18.710 --> 15:03:18.720 align:start position:0% permanently set up connection such as a 15:03:18.720 --> 15:03:21.350 align:start position:0% permanently set up connection such as a T1<15:03:19.020> connection<15:03:19.380> or<15:03:20.276> perhaps<15:03:20.640> even<15:03:20.820> a<15:03:21.116> T3 15:03:21.350 --> 15:03:21.360 align:start position:0% T1 connection or perhaps even a T3 15:03:21.360 --> 15:03:23.746 align:start position:0% T1 connection or perhaps even a T3 connection<15:03:21.660> or<15:03:22.140> oc9<15:03:22.680> connection<15:03:22.980> this 15:03:23.746 --> 15:03:23.756 align:start position:0% connection or oc9 connection this 15:03:23.756 --> 15:03:27.946 align:start position:0% connection or oc9 connection this connection<15:03:24.000> usually<15:03:24.660> allows<15:03:25.140> data<15:03:26.040> voice<15:03:26.956> and 15:03:27.946 --> 15:03:27.956 align:start position:0% connection usually allows data voice and 15:03:27.956 --> 15:03:30.530 align:start position:0% connection usually allows data voice and internet<15:03:28.200> connectivity<15:03:29.040> to<15:03:29.880> pass<15:03:30.060> through<15:03:30.300> it 15:03:30.530 --> 15:03:30.540 align:start position:0% internet connectivity to pass through it 15:03:30.540 --> 15:03:32.266 align:start position:0% internet connectivity to pass through it now<15:03:31.020> typically<15:03:31.380> these<15:03:31.740> are<15:03:31.860> used<15:03:31.980> for 15:03:32.266 --> 15:03:32.276 align:start position:0% now typically these are used for 15:03:32.276 --> 15:03:35.446 align:start position:0% now typically these are used for establishing<15:03:32.880> a<15:03:33.240> Wan<15:03:33.540> and<15:03:34.080> connecting<15:03:34.616> two 15:03:35.446 --> 15:03:35.456 align:start position:0% establishing a Wan and connecting two 15:03:35.456 --> 15:03:38.266 align:start position:0% establishing a Wan and connecting two different<15:03:35.756> geographical<15:03:36.540> locations<15:03:37.320> to<15:03:38.040> One 15:03:38.266 --> 15:03:38.276 align:start position:0% different geographical locations to One 15:03:38.276 --> 15:03:40.246 align:start position:0% different geographical locations to One Network<15:03:38.640> though<15:03:39.480> this<15:03:39.720> connection<15:03:39.840> is 15:03:40.246 --> 15:03:40.256 align:start position:0% Network though this connection is 15:03:40.256 --> 15:03:41.690 align:start position:0% Network though this connection is permanently<15:03:40.740> there<15:03:40.980> it<15:03:41.220> can<15:03:41.400> only<15:03:41.520> be 15:03:41.690 --> 15:03:41.700 align:start position:0% permanently there it can only be 15:03:41.700 --> 15:03:43.426 align:start position:0% permanently there it can only be accessed<15:03:42.300> as<15:03:42.540> long<15:03:42.660> as<15:03:42.776> the<15:03:42.956> customer<15:03:43.140> is 15:03:43.426 --> 15:03:43.436 align:start position:0% accessed as long as the customer is 15:03:43.436 --> 15:03:45.586 align:start position:0% accessed as long as the customer is paying<15:03:43.860> the<15:03:44.096> lease<15:03:44.400> for<15:03:44.580> it<15:03:44.756> this<15:03:45.300> is<15:03:45.416> where 15:03:45.586 --> 15:03:45.596 align:start position:0% paying the lease for it this is where 15:03:45.596 --> 15:03:47.870 align:start position:0% paying the lease for it this is where the<15:03:45.720> disadvantage<15:03:46.320> to<15:03:46.500> it<15:03:46.740> is<15:03:46.916> this<15:03:47.580> can<15:03:47.700> be 15:03:47.870 --> 15:03:47.880 align:start position:0% the disadvantage to it is this can be 15:03:47.880 --> 15:03:49.550 align:start position:0% the disadvantage to it is this can be pretty<15:03:48.060> expensive<15:03:48.596> to<15:03:48.900> buy<15:03:49.020> a<15:03:49.200> lease<15:03:49.380> for 15:03:49.550 --> 15:03:49.560 align:start position:0% pretty expensive to buy a lease for 15:03:49.560 --> 15:03:52.426 align:start position:0% pretty expensive to buy a lease for because<15:03:50.096> again<15:03:50.820> if<15:03:51.240> I<15:03:51.480> have<15:03:51.596> an<15:03:51.720> office<15:03:51.956> in 15:03:52.426 --> 15:03:52.436 align:start position:0% because again if I have an office in 15:03:52.436 --> 15:03:57.830 align:start position:0% because again if I have an office in let's<15:03:53.096> say<15:03:53.480> Manhattan<15:03:54.500> and<15:03:55.500> I<15:03:55.860> have<15:03:56.096> an<15:03:56.640> office 15:03:57.830 --> 15:03:57.840 align:start position:0% let's say Manhattan and I have an office 15:03:57.840 --> 15:04:01.490 align:start position:0% let's say Manhattan and I have an office in<15:03:58.740> Houston<15:03:59.040> the<15:03:59.880> idea<15:04:00.180> is<15:04:00.360> I'm<15:04:00.660> leasing<15:04:01.140> a 15:04:01.490 --> 15:04:01.500 align:start position:0% in Houston the idea is I'm leasing a 15:04:01.500 --> 15:04:03.350 align:start position:0% in Houston the idea is I'm leasing a direct<15:04:01.680> line 15:04:03.350 --> 15:04:03.360 align:start position:0% direct line 15:04:03.360 --> 15:04:05.150 align:start position:0% direct line between<15:04:03.776> the<15:04:04.200> two<15:04:04.320> and<15:04:04.560> as<15:04:04.740> you<15:04:04.860> can<15:04:04.980> imagine 15:04:05.150 --> 15:04:05.160 align:start position:0% between the two and as you can imagine 15:04:05.160 --> 15:04:07.190 align:start position:0% between the two and as you can imagine because<15:04:05.580> I<15:04:05.880> have<15:04:06.060> my<15:04:06.360> own<15:04:06.540> line<15:04:06.720> that's<15:04:07.020> going 15:04:07.190 --> 15:04:07.200 align:start position:0% because I have my own line that's going 15:04:07.200 --> 15:04:09.170 align:start position:0% because I have my own line that's going between<15:04:07.436> these<15:04:07.800> it's<15:04:07.980> pretty<15:04:08.160> expensive<15:04:08.640> the 15:04:09.170 --> 15:04:09.180 align:start position:0% between these it's pretty expensive the 15:04:09.180 --> 15:04:10.970 align:start position:0% between these it's pretty expensive the reason<15:04:09.300> I<15:04:09.480> lease<15:04:09.720> it<15:04:09.840> again<15:04:10.020> is<15:04:10.256> because<15:04:10.436> I'm 15:04:10.970 --> 15:04:10.980 align:start position:0% reason I lease it again is because I'm 15:04:10.980 --> 15:04:12.830 align:start position:0% reason I lease it again is because I'm not<15:04:11.160> a<15:04:11.340> telecommunications<15:04:11.936> company<15:04:12.300> I<15:04:12.596> can't 15:04:12.830 --> 15:04:12.840 align:start position:0% not a telecommunications company I can't 15:04:12.840 --> 15:04:15.170 align:start position:0% not a telecommunications company I can't just<15:04:13.020> lay<15:04:13.380> this<15:04:13.680> cord<15:04:13.916> I<15:04:14.220> need<15:04:14.400> them<15:04:14.640> to<15:04:14.880> lay<15:04:15.000> it 15:04:15.170 --> 15:04:15.180 align:start position:0% just lay this cord I need them to lay it 15:04:15.180 --> 15:04:16.906 align:start position:0% just lay this cord I need them to lay it for<15:04:15.360> me<15:04:15.480> and<15:04:15.956> then<15:04:16.080> I'm<15:04:16.200> going<15:04:16.320> to<15:04:16.436> lease<15:04:16.740> it 15:04:16.906 --> 15:04:16.916 align:start position:0% for me and then I'm going to lease it 15:04:16.916 --> 15:04:18.586 align:start position:0% for me and then I'm going to lease it from<15:04:17.520> them 15:04:18.586 --> 15:04:18.596 align:start position:0% from them 15:04:18.596 --> 15:04:21.766 align:start position:0% from them so<15:04:19.256> the<15:04:20.040> upside<15:04:20.880> to<15:04:21.116> this<15:04:21.240> although<15:04:21.660> that's 15:04:21.766 --> 15:04:21.776 align:start position:0% so the upside to this although that's 15:04:21.776 --> 15:04:24.470 align:start position:0% so the upside to this although that's the<15:04:22.020> downside<15:04:22.436> is<15:04:23.096> that<15:04:23.340> it's<15:04:23.880> the<15:04:24.240> most 15:04:24.470 --> 15:04:24.480 align:start position:0% the downside is that it's the most 15:04:24.480 --> 15:04:27.106 align:start position:0% the downside is that it's the most secure<15:04:24.900> connection<15:04:25.200> that<15:04:26.096> we<15:04:26.276> have 15:04:27.106 --> 15:04:27.116 align:start position:0% secure connection that we have 15:04:27.116 --> 15:04:30.050 align:start position:0% secure connection that we have now<15:04:27.596> in<15:04:27.720> the<15:04:27.900> last<15:04:27.956> module<15:04:28.380> we<15:04:28.616> talked<15:04:28.916> about<15:04:29.060> a 15:04:30.050 --> 15:04:30.060 align:start position:0% now in the last module we talked about a 15:04:30.060 --> 15:04:34.010 align:start position:0% now in the last module we talked about a t<15:04:30.480> carrier<15:04:31.080> lines<15:04:31.436> and<15:04:32.340> a<15:04:32.700> T1<15:04:33.060> line<15:04:33.416> can<15:04:33.840> be 15:04:34.010 --> 15:04:34.020 align:start position:0% t carrier lines and a T1 line can be 15:04:34.020 --> 15:04:35.990 align:start position:0% t carrier lines and a T1 line can be leased<15:04:34.560> and<15:04:34.916> provides<15:04:35.276> a<15:04:35.456> secure<15:04:35.756> connection 15:04:35.990 --> 15:04:36.000 align:start position:0% leased and provides a secure connection 15:04:36.000 --> 15:04:48.050 align:start position:0% leased and provides a secure connection so<15:04:36.776> therefore<15:04:37.200> it<15:04:37.740> is<15:04:37.980> a<15:04:38.936> leased<15:04:39.416> line 15:04:48.050 --> 15:04:48.060 align:start position:0% 15:04:48.060 --> 15:04:49.790 align:start position:0% and<15:04:48.480> we<15:04:48.660> also<15:04:48.956> talked<15:04:49.200> about<15:04:49.320> in<15:04:49.616> previous 15:04:49.790 --> 15:04:49.800 align:start position:0% and we also talked about in previous 15:04:49.800 --> 15:04:52.426 align:start position:0% and we also talked about in previous lessons<15:04:50.456> switching<15:04:51.180> we<15:04:51.660> talked<15:04:51.956> about<15:04:52.020> how 15:04:52.426 --> 15:04:52.436 align:start position:0% lessons switching we talked about how 15:04:52.436 --> 15:04:53.990 align:start position:0% lessons switching we talked about how important<15:04:52.860> switches<15:04:53.456> were<15:04:53.700> to<15:04:53.880> the 15:04:53.990 --> 15:04:54.000 align:start position:0% important switches were to the 15:04:54.000 --> 15:04:55.730 align:start position:0% important switches were to the functionality<15:04:54.540> of<15:04:54.776> a<15:04:54.956> local<15:04:55.080> area<15:04:55.380> network 15:04:55.730 --> 15:04:55.740 align:start position:0% functionality of a local area network 15:04:55.740 --> 15:04:57.650 align:start position:0% functionality of a local area network they<15:04:56.400> provide<15:04:56.700> a<15:04:56.820> communication<15:04:57.300> path 15:04:57.650 --> 15:04:57.660 align:start position:0% they provide a communication path 15:04:57.660 --> 15:05:00.106 align:start position:0% they provide a communication path between<15:04:58.020> two<15:04:58.500> endpoints<15:04:59.276> and<15:04:59.640> they<15:04:59.820> manage 15:05:00.106 --> 15:05:00.116 align:start position:0% between two endpoints and they manage 15:05:00.116 --> 15:05:01.850 align:start position:0% between two endpoints and they manage that<15:05:00.300> flow<15:05:00.596> of<15:05:00.720> data<15:05:01.080> so<15:05:01.256> that<15:05:01.380> way<15:05:01.560> we<15:05:01.800> don't 15:05:01.850 --> 15:05:01.860 align:start position:0% that flow of data so that way we don't 15:05:01.860 --> 15:05:04.606 align:start position:0% that flow of data so that way we don't have<15:05:02.096> a<15:05:02.340> bunch<15:05:02.456> of<15:05:02.580> traffic<15:05:03.000> going<15:05:03.480> on<15:05:03.776> in 15:05:04.606 --> 15:05:04.616 align:start position:0% have a bunch of traffic going on in 15:05:04.616 --> 15:05:06.650 align:start position:0% have a bunch of traffic going on in effect<15:05:04.860> they<15:05:05.456> basically<15:05:05.820> make<15:05:06.116> sure<15:05:06.360> that 15:05:06.650 --> 15:05:06.660 align:start position:0% effect they basically make sure that 15:05:06.660 --> 15:05:08.990 align:start position:0% effect they basically make sure that packet<15:05:07.080> going<15:05:07.256> from<15:05:07.436> one<15:05:07.680> location<15:05:07.936> gets<15:05:08.936> to 15:05:08.990 --> 15:05:09.000 align:start position:0% packet going from one location gets to 15:05:09.000 --> 15:05:11.390 align:start position:0% packet going from one location gets to the<15:05:09.180> other<15:05:09.300> and<15:05:09.900> doesn't<15:05:10.200> sort<15:05:10.800> of<15:05:10.916> interrupt 15:05:11.390 --> 15:05:11.400 align:start position:0% the other and doesn't sort of interrupt 15:05:11.400 --> 15:05:12.890 align:start position:0% the other and doesn't sort of interrupt the<15:05:11.520> flow<15:05:11.820> of<15:05:11.936> all<15:05:12.116> the<15:05:12.240> other<15:05:12.360> packets<15:05:12.720> that 15:05:12.890 --> 15:05:12.900 align:start position:0% the flow of all the other packets that 15:05:12.900 --> 15:05:15.230 align:start position:0% the flow of all the other packets that are<15:05:13.020> going<15:05:13.200> on<15:05:13.436> now<15:05:14.220> in<15:05:14.456> Lan<15:05:14.880> these<15:05:15.180> two 15:05:15.230 --> 15:05:15.240 align:start position:0% are going on now in Lan these two 15:05:15.240 --> 15:05:16.970 align:start position:0% are going on now in Lan these two endpoints<15:05:15.776> aren't<15:05:15.956> very<15:05:16.140> far<15:05:16.380> away<15:05:16.500> from<15:05:16.800> each 15:05:16.970 --> 15:05:16.980 align:start position:0% endpoints aren't very far away from each 15:05:16.980 --> 15:05:19.310 align:start position:0% endpoints aren't very far away from each other<15:05:17.160> however<15:05:17.880> on<15:05:18.180> a<15:05:18.360> Wan<15:05:18.596> or<15:05:18.840> a<15:05:18.956> wide<15:05:19.200> area 15:05:19.310 --> 15:05:19.320 align:start position:0% other however on a Wan or a wide area 15:05:19.320 --> 15:05:21.230 align:start position:0% other however on a Wan or a wide area network<15:05:19.680> these<15:05:20.276> endpoints<15:05:20.756> could<15:05:21.000> be<15:05:21.116> on 15:05:21.230 --> 15:05:21.240 align:start position:0% network these endpoints could be on 15:05:21.240 --> 15:05:23.330 align:start position:0% network these endpoints could be on opposite<15:05:21.660> sides 15:05:23.330 --> 15:05:23.340 align:start position:0% opposite sides 15:05:23.340 --> 15:05:25.790 align:start position:0% opposite sides the<15:05:23.880> globe<15:05:24.360> and<15:05:24.900> that's<15:05:25.080> why<15:05:25.256> switching<15:05:25.680> is 15:05:25.790 --> 15:05:25.800 align:start position:0% the globe and that's why switching is 15:05:25.800 --> 15:05:26.990 align:start position:0% the globe and that's why switching is such<15:05:25.980> an<15:05:26.096> important<15:05:26.400> topic<15:05:26.700> to<15:05:26.880> understand 15:05:26.990 --> 15:05:27.000 align:start position:0% such an important topic to understand 15:05:27.000 --> 15:05:29.330 align:start position:0% such an important topic to understand now<15:05:27.900> when<15:05:28.080> it<15:05:28.256> comes<15:05:28.436> to<15:05:28.616> a<15:05:28.740> win<15:05:28.860> or<15:05:29.096> a<15:05:29.220> wide 15:05:29.330 --> 15:05:29.340 align:start position:0% now when it comes to a win or a wide 15:05:29.340 --> 15:05:30.406 align:start position:0% now when it comes to a win or a wide area<15:05:29.456> network<15:05:29.700> there<15:05:30.060> are<15:05:30.180> two<15:05:30.300> different 15:05:30.406 --> 15:05:30.416 align:start position:0% area network there are two different 15:05:30.416 --> 15:05:32.630 align:start position:0% area network there are two different types<15:05:30.776> of<15:05:30.840> switching<15:05:31.740> there's<15:05:32.220> packet 15:05:32.630 --> 15:05:32.640 align:start position:0% types of switching there's packet 15:05:32.640 --> 15:05:35.446 align:start position:0% types of switching there's packet switching<15:05:33.116> and<15:05:33.900> there's<15:05:34.080> circuit<15:05:34.436> switching 15:05:35.446 --> 15:05:35.456 align:start position:0% switching and there's circuit switching 15:05:35.456 --> 15:05:39.350 align:start position:0% switching and there's circuit switching packet<15:05:36.116> switching<15:05:36.596> is<15:05:37.200> when<15:05:37.500> the<15:05:37.980> data<15:05:38.880> is 15:05:39.350 --> 15:05:39.360 align:start position:0% packet switching is when the data is 15:05:39.360 --> 15:05:44.330 align:start position:0% packet switching is when the data is broken<15:05:39.596> up<15:05:39.900> into<15:05:40.380> smaller<15:05:41.096> chunks 15:05:44.330 --> 15:05:44.340 align:start position:0% 15:05:44.340 --> 15:05:45.586 align:start position:0% or 15:05:45.586 --> 15:05:45.596 align:start position:0% or 15:05:45.596 --> 15:05:47.086 align:start position:0% or pockets 15:05:47.086 --> 15:05:47.096 align:start position:0% pockets 15:05:47.096 --> 15:05:49.426 align:start position:0% pockets and<15:05:47.520> then<15:05:47.640> they're<15:05:47.820> assigned<15:05:48.360> a<15:05:48.540> source<15:05:49.020> and<15:05:49.256> a 15:05:49.426 --> 15:05:49.436 align:start position:0% and then they're assigned a source and a 15:05:49.436 --> 15:05:51.586 align:start position:0% and then they're assigned a source and a destination<15:05:49.860> and<15:05:50.700> they<15:05:50.936> stop<15:05:51.116> at<15:05:51.360> different 15:05:51.586 --> 15:05:51.596 align:start position:0% destination and they stop at different 15:05:51.596 --> 15:05:53.266 align:start position:0% destination and they stop at different nodes<15:05:52.020> along<15:05:52.256> the<15:05:52.500> way 15:05:53.266 --> 15:05:53.276 align:start position:0% nodes along the way 15:05:53.276 --> 15:05:55.970 align:start position:0% nodes along the way every<15:05:53.936> packet<15:05:54.480> has<15:05:54.900> these<15:05:55.256> assigned<15:05:55.740> to<15:05:55.860> it 15:05:55.970 --> 15:05:55.980 align:start position:0% every packet has these assigned to it 15:05:55.980 --> 15:05:57.710 align:start position:0% every packet has these assigned to it because<15:05:56.220> they<15:05:56.456> don't<15:05:56.580> always<15:05:56.756> stay<15:05:57.116> in<15:05:57.540> the 15:05:57.710 --> 15:05:57.720 align:start position:0% because they don't always stay in the 15:05:57.720 --> 15:06:00.050 align:start position:0% because they don't always stay in the same<15:05:57.900> path<15:05:58.256> as<15:05:58.916> the<15:05:59.160> other<15:05:59.340> packet<15:05:59.756> and<15:05:59.936> I'll 15:06:00.050 --> 15:06:00.060 align:start position:0% same path as the other packet and I'll 15:06:00.060 --> 15:06:01.606 align:start position:0% same path as the other packet and I'll show<15:06:00.180> you<15:06:00.300> a<15:06:00.416> visual<15:06:00.660> to<15:06:00.900> clarify<15:06:01.320> this<15:06:01.436> in 15:06:01.606 --> 15:06:01.616 align:start position:0% show you a visual to clarify this in 15:06:01.616 --> 15:06:03.350 align:start position:0% show you a visual to clarify this in just<15:06:01.800> a<15:06:01.916> second<15:06:02.096> they're<15:06:02.756> usually<15:06:03.060> going<15:06:03.240> to 15:06:03.350 --> 15:06:03.360 align:start position:0% just a second they're usually going to 15:06:03.360 --> 15:06:05.570 align:start position:0% just a second they're usually going to split<15:06:04.140> up<15:06:04.320> which<15:06:04.680> paths<15:06:05.220> they're<15:06:05.340> going<15:06:05.520> to 15:06:05.570 --> 15:06:05.580 align:start position:0% split up which paths they're going to 15:06:05.580 --> 15:06:07.606 align:start position:0% split up which paths they're going to take<15:06:05.700> in<15:06:06.000> order<15:06:06.116> to<15:06:06.416> avoid<15:06:06.840> colliding<15:06:07.500> with 15:06:07.606 --> 15:06:07.616 align:start position:0% take in order to avoid colliding with 15:06:07.616 --> 15:06:13.850 align:start position:0% take in order to avoid colliding with each<15:06:07.740> other<15:06:07.860> and<15:06:08.520> to<15:06:08.640> make<15:06:08.820> it<15:06:08.936> much<15:06:09.116> faster 15:06:13.850 --> 15:06:13.860 align:start position:0% 15:06:13.860 --> 15:06:16.970 align:start position:0% this<15:06:14.400> principle<15:06:14.880> of<15:06:15.300> packet<15:06:15.840> switching<15:06:16.380> is 15:06:16.970 --> 15:06:16.980 align:start position:0% this principle of packet switching is 15:06:16.980 --> 15:06:19.670 align:start position:0% this principle of packet switching is sort<15:06:17.276> of<15:06:17.456> similar<15:06:17.820> to<15:06:18.180> a<15:06:18.416> torrent<15:06:18.900> if<15:06:19.560> you 15:06:19.670 --> 15:06:19.680 align:start position:0% sort of similar to a torrent if you 15:06:19.680 --> 15:06:21.650 align:start position:0% sort of similar to a torrent if you remember<15:06:19.860> a<15:06:20.520> torrent<15:06:20.880> file<15:06:21.116> if<15:06:21.300> you've<15:06:21.416> ever 15:06:21.650 --> 15:06:21.660 align:start position:0% remember a torrent file if you've ever 15:06:21.660 --> 15:06:23.030 align:start position:0% remember a torrent file if you've ever used<15:06:22.020> one 15:06:23.030 --> 15:06:23.040 align:start position:0% used one 15:06:23.040 --> 15:06:27.050 align:start position:0% used one it<15:06:23.820> contains<15:06:24.480> information<15:06:25.436> about<15:06:26.160> data<15:06:26.756> like 15:06:27.050 --> 15:06:27.060 align:start position:0% it contains information about data like 15:06:27.060 --> 15:06:28.490 align:start position:0% it contains information about data like files<15:06:27.540> and<15:06:27.660> folders<15:06:28.020> that<15:06:28.256> can<15:06:28.380> be 15:06:28.490 --> 15:06:28.500 align:start position:0% files and folders that can be 15:06:28.500 --> 15:06:31.010 align:start position:0% files and folders that can be distributed<15:06:28.980> now<15:06:29.520> if<15:06:29.700> someone<15:06:29.880> torrents<15:06:30.596> a 15:06:31.010 --> 15:06:31.020 align:start position:0% distributed now if someone torrents a 15:06:31.020 --> 15:06:33.106 align:start position:0% distributed now if someone torrents a file<15:06:31.320> the<15:06:31.860> folders<15:06:32.220> and<15:06:32.340> files<15:06:32.640> within<15:06:32.936> that 15:06:33.106 --> 15:06:33.116 align:start position:0% file the folders and files within that 15:06:33.116 --> 15:06:35.266 align:start position:0% file the folders and files within that torrent<15:06:33.540> are<15:06:33.776> downloaded<15:06:34.320> to<15:06:34.680> the<15:06:34.860> user's 15:06:35.266 --> 15:06:35.276 align:start position:0% torrent are downloaded to the user's 15:06:35.276 --> 15:06:36.946 align:start position:0% torrent are downloaded to the user's computer<15:06:35.400> but<15:06:36.300> the<15:06:36.416> torrents<15:06:36.840> are 15:06:36.946 --> 15:06:36.956 align:start position:0% computer but the torrents are 15:06:36.956 --> 15:06:39.230 align:start position:0% computer but the torrents are peer-to-peer<15:06:37.616> sharing<15:06:38.040> system<15:06:38.276> they<15:06:39.000> Mark 15:06:39.230 --> 15:06:39.240 align:start position:0% peer-to-peer sharing system they Mark 15:06:39.240 --> 15:06:40.970 align:start position:0% peer-to-peer sharing system they Mark almost<15:06:39.480> exactly<15:06:39.956> like<15:06:40.080> packet<15:06:40.560> switching 15:06:40.970 --> 15:06:40.980 align:start position:0% almost exactly like packet switching 15:06:40.980 --> 15:06:43.310 align:start position:0% almost exactly like packet switching does<15:06:41.160> torrents<15:06:42.060> collects<15:06:42.480> packets<15:06:42.900> of<15:06:43.080> data 15:06:43.310 --> 15:06:43.320 align:start position:0% does torrents collects packets of data 15:06:43.320 --> 15:06:44.990 align:start position:0% does torrents collects packets of data from<15:06:43.500> wherever<15:06:43.740> the<15:06:43.916> data<15:06:44.220> is<15:06:44.400> available<15:06:44.580> and 15:06:44.990 --> 15:06:45.000 align:start position:0% from wherever the data is available and 15:06:45.000 --> 15:06:47.210 align:start position:0% from wherever the data is available and then<15:06:45.180> reassemble<15:06:45.900> it<15:06:46.020> in<15:06:46.256> the<15:06:46.436> whole<15:06:46.560> file<15:06:46.916> on 15:06:47.210 --> 15:06:47.220 align:start position:0% then reassemble it in the whole file on 15:06:47.220 --> 15:06:48.406 align:start position:0% then reassemble it in the whole file on your<15:06:47.456> computer 15:06:48.406 --> 15:06:48.416 align:start position:0% your computer 15:06:48.416 --> 15:06:51.050 align:start position:0% your computer in<15:06:48.956> other<15:06:49.080> words<15:06:49.256> you<15:06:50.096> can<15:06:50.220> be<15:06:50.400> downloading 15:06:51.050 --> 15:06:51.060 align:start position:0% in other words you can be downloading 15:06:51.060 --> 15:06:52.970 align:start position:0% in other words you can be downloading information<15:06:51.416> for<15:06:52.140> the<15:06:52.500> movie<15:06:52.680> you're 15:06:52.970 --> 15:06:52.980 align:start position:0% information for the movie you're 15:06:52.980 --> 15:06:55.426 align:start position:0% information for the movie you're torrenting<15:06:53.640> or<15:06:54.480> of<15:06:54.776> course<15:06:54.900> the<15:06:55.080> movie<15:06:55.200> that 15:06:55.426 --> 15:06:55.436 align:start position:0% torrenting or of course the movie that 15:06:55.436 --> 15:06:56.690 align:start position:0% torrenting or of course the movie that you<15:06:55.616> own<15:06:55.680> that<15:06:55.916> you're<15:06:56.040> torrent<15:06:56.400> and<15:06:56.580> we 15:06:56.690 --> 15:06:56.700 align:start position:0% you own that you're torrent and we 15:06:56.700 --> 15:06:57.710 align:start position:0% you own that you're torrent and we wouldn't<15:06:56.820> want<15:06:57.060> to<15:06:57.116> say<15:06:57.240> to<15:06:57.416> do<15:06:57.596> anything 15:06:57.710 --> 15:06:57.720 align:start position:0% wouldn't want to say to do anything 15:06:57.720 --> 15:06:59.746 align:start position:0% wouldn't want to say to do anything illegal<15:06:58.320> and<15:06:58.740> what<15:06:58.916> you're<15:06:59.040> doing<15:06:59.220> is<15:06:59.520> you're 15:06:59.746 --> 15:06:59.756 align:start position:0% illegal and what you're doing is you're 15:06:59.756 --> 15:07:02.266 align:start position:0% illegal and what you're doing is you're actually<15:07:00.000> taking<15:07:00.360> that<15:07:00.660> information<15:07:01.276> from 15:07:02.266 --> 15:07:02.276 align:start position:0% actually taking that information from 15:07:02.276 --> 15:07:06.650 align:start position:0% actually taking that information from say<15:07:02.756> 5<15:07:03.480> or<15:07:03.776> 10<15:07:04.080> or<15:07:04.500> 100<15:07:04.936> different<15:07:05.936> systems 15:07:06.650 --> 15:07:06.660 align:start position:0% say 5 or 10 or 100 different systems 15:07:06.660 --> 15:07:08.210 align:start position:0% say 5 or 10 or 100 different systems that<15:07:06.776> are<15:07:06.900> out<15:07:07.080> there<15:07:07.256> they're<15:07:07.800> all<15:07:08.040> coming 15:07:08.210 --> 15:07:08.220 align:start position:0% that are out there they're all coming 15:07:08.220 --> 15:07:11.810 align:start position:0% that are out there they're all coming down<15:07:08.580> into<15:07:09.360> your<15:07:09.840> system<15:07:10.220> and<15:07:11.220> then<15:07:11.400> you're 15:07:11.810 --> 15:07:11.820 align:start position:0% down into your system and then you're 15:07:11.820 --> 15:07:13.730 align:start position:0% down into your system and then you're compiling<15:07:12.416> it<15:07:12.596> all<15:07:12.720> together 15:07:13.730 --> 15:07:13.740 align:start position:0% compiling it all together 15:07:13.740 --> 15:07:15.890 align:start position:0% compiling it all together to<15:07:14.340> make 15:07:15.890 --> 15:07:15.900 align:start position:0% to make 15:07:15.900 --> 15:07:17.570 align:start position:0% to make one<15:07:16.500> movie 15:07:17.570 --> 15:07:17.580 align:start position:0% one movie 15:07:17.580 --> 15:07:19.790 align:start position:0% one movie this<15:07:18.116> isn't<15:07:18.360> unlike<15:07:18.660> Willy<15:07:19.080> Wonka<15:07:19.436> where<15:07:19.616> the 15:07:19.790 --> 15:07:19.800 align:start position:0% this isn't unlike Willy Wonka where the 15:07:19.800 --> 15:07:21.890 align:start position:0% this isn't unlike Willy Wonka where the information<15:07:20.000> goes<15:07:21.000> up<15:07:21.116> into<15:07:21.300> the<15:07:21.480> Wonka 15:07:21.890 --> 15:07:21.900 align:start position:0% information goes up into the Wonka 15:07:21.900 --> 15:07:23.990 align:start position:0% information goes up into the Wonka vision<15:07:22.160> gets<15:07:23.160> split<15:07:23.340> up<15:07:23.456> into<15:07:23.640> a<15:07:23.820> whole<15:07:23.820> bunch 15:07:23.990 --> 15:07:24.000 align:start position:0% vision gets split up into a whole bunch 15:07:24.000 --> 15:07:25.606 align:start position:0% vision gets split up into a whole bunch of<15:07:24.116> little<15:07:24.240> pieces<15:07:24.596> and<15:07:24.840> then<15:07:25.020> gets<15:07:25.380> brought 15:07:25.606 --> 15:07:25.616 align:start position:0% of little pieces and then gets brought 15:07:25.616 --> 15:07:27.650 align:start position:0% of little pieces and then gets brought back<15:07:25.800> to<15:07:26.040> you<15:07:26.220> except<15:07:26.880> all<15:07:27.000> the<15:07:27.180> little<15:07:27.300> pieces 15:07:27.650 --> 15:07:27.660 align:start position:0% back to you except all the little pieces 15:07:27.660 --> 15:07:29.690 align:start position:0% back to you except all the little pieces don't<15:07:27.900> have<15:07:28.080> to<15:07:28.256> be<15:07:28.436> sent<15:07:28.616> from<15:07:29.040> all<15:07:29.276> the<15:07:29.456> same 15:07:29.690 --> 15:07:29.700 align:start position:0% don't have to be sent from all the same 15:07:29.700 --> 15:07:31.130 align:start position:0% don't have to be sent from all the same place 15:07:31.130 --> 15:07:31.140 align:start position:0% place 15:07:31.140 --> 15:07:34.310 align:start position:0% place so<15:07:32.040> the<15:07:32.880> benefit<15:07:33.116> of<15:07:33.480> this<15:07:33.596> is<15:07:33.776> that<15:07:33.956> it<15:07:34.080> can<15:07:34.200> go 15:07:34.310 --> 15:07:34.320 align:start position:0% so the benefit of this is that it can go 15:07:34.320 --> 15:07:36.230 align:start position:0% so the benefit of this is that it can go a<15:07:34.500> lot<15:07:34.616> faster<15:07:34.980> that's<15:07:35.640> with<15:07:35.880> packet 15:07:36.230 --> 15:07:36.240 align:start position:0% a lot faster that's with packet 15:07:36.240 --> 15:07:38.266 align:start position:0% a lot faster that's with packet switching<15:07:36.660> the<15:07:37.080> downside<15:07:37.380> of<15:07:37.616> course<15:07:37.800> is<15:07:38.040> that 15:07:38.266 --> 15:07:38.276 align:start position:0% switching the downside of course is that 15:07:38.276 --> 15:07:40.730 align:start position:0% switching the downside of course is that there's<15:07:38.700> a<15:07:39.000> good<15:07:39.116> chance<15:07:39.416> that<15:07:39.956> the<15:07:40.380> packets 15:07:40.730 --> 15:07:40.740 align:start position:0% there's a good chance that the packets 15:07:40.740 --> 15:07:43.490 align:start position:0% there's a good chance that the packets can<15:07:41.040> be<15:07:41.220> lost<15:07:41.456> along<15:07:41.880> the<15:07:42.180> way<15:07:42.300> now<15:07:43.200> the<15:07:43.320> second 15:07:43.490 --> 15:07:43.500 align:start position:0% can be lost along the way now the second 15:07:43.500 --> 15:07:45.710 align:start position:0% can be lost along the way now the second type<15:07:43.740> of<15:07:44.040> switching<15:07:44.456> is<15:07:44.820> called<15:07:45.116> circuit 15:07:45.710 --> 15:07:45.720 align:start position:0% type of switching is called circuit 15:07:45.720 --> 15:07:47.570 align:start position:0% type of switching is called circuit switching<15:07:46.200> this<15:07:46.800> method<15:07:47.096> of<15:07:47.220> switching 15:07:47.570 --> 15:07:47.580 align:start position:0% switching this method of switching 15:07:47.580 --> 15:07:49.606 align:start position:0% switching this method of switching requires<15:07:48.116> dedicated 15:07:49.606 --> 15:07:49.616 align:start position:0% requires dedicated 15:07:49.616 --> 15:07:52.970 align:start position:0% requires dedicated physical<15:07:50.220> connections<15:07:51.116> so<15:07:51.480> whereas<15:07:51.980> packet 15:07:52.970 --> 15:07:52.980 align:start position:0% physical connections so whereas packet 15:07:52.980 --> 15:07:56.086 align:start position:0% physical connections so whereas packet we're<15:07:53.220> dealing<15:07:53.640> with<15:07:54.256> data<15:07:55.256> in<15:07:55.560> circuit<15:07:55.980> we're 15:07:56.086 --> 15:07:56.096 align:start position:0% we're dealing with data in circuit we're 15:07:56.096 --> 15:07:59.390 align:start position:0% we're dealing with data in circuit we're dealing<15:07:56.400> with<15:07:56.520> physical<15:07:56.756> connections<15:07:57.596> that 15:07:59.390 --> 15:07:59.400 align:start position:0% dealing with physical connections that 15:07:59.400 --> 15:08:02.266 align:start position:0% dealing with physical connections that allow<15:08:00.240> data<15:08:00.660> to<15:08:00.720> be<15:08:00.840> transferred<15:08:01.380> now<15:08:01.980> it<15:08:02.160> can 15:08:02.266 --> 15:08:02.276 align:start position:0% allow data to be transferred now it can 15:08:02.276 --> 15:08:03.586 align:start position:0% allow data to be transferred now it can be<15:08:02.400> difficult<15:08:02.580> to<15:08:02.880> establish<15:08:03.300> these 15:08:03.586 --> 15:08:03.596 align:start position:0% be difficult to establish these 15:08:03.596 --> 15:08:05.150 align:start position:0% be difficult to establish these connections<15:08:04.020> but<15:08:04.380> the<15:08:04.500> results<15:08:04.616> are<15:08:04.916> a<15:08:05.040> lot 15:08:05.150 --> 15:08:05.160 align:start position:0% connections but the results are a lot 15:08:05.160 --> 15:08:07.310 align:start position:0% connections but the results are a lot more<15:08:05.276> reliable<15:08:05.936> than<15:08:06.300> with<15:08:06.540> packet<15:08:06.900> switching 15:08:07.310 --> 15:08:07.320 align:start position:0% more reliable than with packet switching 15:08:07.320 --> 15:08:08.746 align:start position:0% more reliable than with packet switching with<15:08:07.740> circuit<15:08:08.096> switching<15:08:08.400> the<15:08:08.580> connection 15:08:08.746 --> 15:08:08.756 align:start position:0% with circuit switching the connection 15:08:08.756 --> 15:08:11.446 align:start position:0% with circuit switching the connection that's<15:08:09.116> made<15:08:09.540> is<15:08:10.380> dedicated<15:08:10.980> for<15:08:11.276> that 15:08:11.446 --> 15:08:11.456 align:start position:0% that's made is dedicated for that 15:08:11.456 --> 15:08:14.630 align:start position:0% that's made is dedicated for that purpose<15:08:11.880> only<15:08:12.116> in<15:08:12.720> other<15:08:12.840> words<15:08:13.020> I<15:08:13.500> create 15:08:14.630 --> 15:08:14.640 align:start position:0% purpose only in other words I create 15:08:14.640 --> 15:08:21.050 align:start position:0% purpose only in other words I create switch<15:08:15.300> over<15:08:16.080> which<15:08:16.380> all<15:08:17.220> the<15:08:17.400> data<15:08:17.700> is<15:08:18.060> going 15:08:21.050 --> 15:08:21.060 align:start position:0% 15:08:21.060 --> 15:08:24.830 align:start position:0% to<15:08:21.660> be<15:08:21.900> sent<15:08:22.276> once<15:08:23.276> I'm<15:08:23.456> done<15:08:23.756> with<15:08:24.060> that<15:08:24.300> and 15:08:24.830 --> 15:08:24.840 align:start position:0% to be sent once I'm done with that and 15:08:24.840 --> 15:08:27.050 align:start position:0% to be sent once I'm done with that and the<15:08:25.080> transfer<15:08:25.380> is<15:08:25.560> complete<15:08:25.980> I<15:08:26.520> no<15:08:26.756> longer 15:08:27.050 --> 15:08:27.060 align:start position:0% the transfer is complete I no longer 15:08:27.060 --> 15:08:28.670 align:start position:0% the transfer is complete I no longer need<15:08:27.300> this<15:08:27.540> circuit<15:08:27.956> and<15:08:28.140> so<15:08:28.256> it<15:08:28.380> might<15:08:28.560> be 15:08:28.670 --> 15:08:28.680 align:start position:0% need this circuit and so it might be 15:08:28.680 --> 15:08:30.530 align:start position:0% need this circuit and so it might be switched<15:08:29.096> to<15:08:29.276> allow<15:08:29.580> another<15:08:29.820> computer<15:08:30.180> or 15:08:30.530 --> 15:08:30.540 align:start position:0% switched to allow another computer or 15:08:30.540 --> 15:08:32.446 align:start position:0% switched to allow another computer or system<15:08:30.840> to<15:08:31.140> talk<15:08:31.320> to<15:08:31.436> one<15:08:31.616> another<15:08:31.740> now 15:08:32.446 --> 15:08:32.456 align:start position:0% system to talk to one another now 15:08:32.456 --> 15:08:34.010 align:start position:0% system to talk to one another now there's<15:08:32.640> a<15:08:32.880> very<15:08:33.000> small<15:08:33.240> chance<15:08:33.480> of<15:08:33.720> the<15:08:33.776> data 15:08:34.010 --> 15:08:34.020 align:start position:0% there's a very small chance of the data 15:08:34.020 --> 15:08:35.690 align:start position:0% there's a very small chance of the data getting<15:08:34.140> lost<15:08:34.380> or<15:08:34.740> along<15:08:35.040> the<15:08:35.276> way<15:08:35.400> because 15:08:35.690 --> 15:08:35.700 align:start position:0% getting lost or along the way because 15:08:35.700 --> 15:08:38.510 align:start position:0% getting lost or along the way because the<15:08:36.000> circuit<15:08:36.300> switching<15:08:36.776> establishes<15:08:37.740> a 15:08:38.510 --> 15:08:38.520 align:start position:0% the circuit switching establishes a 15:08:38.520 --> 15:08:41.150 align:start position:0% the circuit switching establishes a consistent<15:08:39.060> data<15:08:39.540> transfer<15:08:39.956> however<15:08:40.740> the 15:08:41.150 --> 15:08:41.160 align:start position:0% consistent data transfer however the 15:08:41.160 --> 15:08:43.730 align:start position:0% consistent data transfer however the downside<15:08:41.456> is<15:08:41.756> I<15:08:42.000> can't<15:08:42.116> take<15:08:42.416> it<15:08:42.660> from<15:08:43.200> say<15:08:43.500> 10 15:08:43.730 --> 15:08:43.740 align:start position:0% downside is I can't take it from say 10 15:08:43.740 --> 15:08:46.246 align:start position:0% downside is I can't take it from say 10 different<15:08:43.980> sources<15:08:44.580> instead<15:08:45.416> I<15:08:45.720> have<15:08:45.840> to<15:08:46.020> have 15:08:46.246 --> 15:08:46.256 align:start position:0% different sources instead I have to have 15:08:46.256 --> 15:08:49.130 align:start position:0% different sources instead I have to have one<15:08:46.616> sender<15:08:47.096> one<15:08:47.640> receiver<15:08:48.000> and<15:08:48.596> in<15:08:48.776> this<15:08:48.956> case 15:08:49.130 --> 15:08:49.140 align:start position:0% one sender one receiver and in this case 15:08:49.140 --> 15:08:51.530 align:start position:0% one sender one receiver and in this case because<15:08:49.860> I<15:08:50.456> can't<15:08:50.520> split<15:08:50.880> it<15:08:51.000> up<15:08:51.116> it<15:08:51.360> might 15:08:51.530 --> 15:08:51.540 align:start position:0% because I can't split it up it might 15:08:51.540 --> 15:08:53.330 align:start position:0% because I can't split it up it might take<15:08:51.720> longer<15:08:52.200> to<15:08:52.380> find<15:08:52.560> that<15:08:52.916> one<15:08:53.096> connection 15:08:53.330 --> 15:08:53.340 align:start position:0% take longer to find that one connection 15:08:53.340 --> 15:08:55.070 align:start position:0% take longer to find that one connection although<15:08:54.116> once<15:08:54.416> that<15:08:54.540> connection<15:08:54.720> is 15:08:55.070 --> 15:08:55.080 align:start position:0% although once that connection is 15:08:55.080 --> 15:08:57.406 align:start position:0% although once that connection is established<15:08:55.500> it's<15:08:55.680> a<15:08:55.860> lot<15:08:55.980> stronger<15:08:56.820> so 15:08:57.406 --> 15:08:57.416 align:start position:0% established it's a lot stronger so 15:08:57.416 --> 15:08:59.510 align:start position:0% established it's a lot stronger so here's<15:08:57.900> an<15:08:58.020> example<15:08:58.320> of<15:08:58.680> what<15:08:58.980> packet 15:08:59.510 --> 15:08:59.520 align:start position:0% here's an example of what packet 15:08:59.520 --> 15:09:01.606 align:start position:0% here's an example of what packet switching<15:09:00.000> might<15:09:00.240> look<15:09:00.480> like<15:09:00.596> the<15:09:01.320> packets 15:09:01.606 --> 15:09:01.616 align:start position:0% switching might look like the packets 15:09:01.616 --> 15:09:02.810 align:start position:0% switching might look like the packets that<15:09:01.800> are<15:09:01.916> traveling<15:09:02.220> across<15:09:02.580> the<15:09:02.640> network 15:09:02.810 --> 15:09:02.820 align:start position:0% that are traveling across the network 15:09:02.820 --> 15:09:05.086 align:start position:0% that are traveling across the network are<15:09:03.116> all<15:09:03.360> going<15:09:03.596> on<15:09:03.900> different<15:09:04.080> paths<15:09:04.616> right 15:09:05.086 --> 15:09:05.096 align:start position:0% are all going on different paths right 15:09:05.096 --> 15:09:09.650 align:start position:0% are all going on different paths right one<15:09:05.640> might<15:09:05.880> be<15:09:06.060> going<15:09:06.800> like<15:09:07.800> this 15:09:09.650 --> 15:09:09.660 align:start position:0% one might be going like this 15:09:09.660 --> 15:09:12.406 align:start position:0% one might be going like this one<15:09:10.256> might<15:09:10.560> be<15:09:10.740> going<15:09:11.040> like<15:09:11.700> this<15:09:11.936> the<15:09:12.360> other 15:09:12.406 --> 15:09:12.416 align:start position:0% one might be going like this the other 15:09:12.416 --> 15:09:15.106 align:start position:0% one might be going like this the other might<15:09:12.720> be<15:09:12.900> going<15:09:13.140> like<15:09:13.680> this 15:09:15.106 --> 15:09:15.116 align:start position:0% might be going like this 15:09:15.116 --> 15:09:16.730 align:start position:0% might be going like this etc<15:09:15.720> etc 15:09:16.730 --> 15:09:16.740 align:start position:0% etc etc 15:09:16.740 --> 15:09:17.990 align:start position:0% etc etc they're<15:09:17.220> all<15:09:17.400> going<15:09:17.520> to<15:09:17.640> reach<15:09:17.820> the 15:09:17.990 --> 15:09:18.000 align:start position:0% they're all going to reach the 15:09:18.000 --> 15:09:21.106 align:start position:0% they're all going to reach the destination<15:09:18.500> on<15:09:19.500> the<15:09:19.616> right<15:09:20.276> but<15:09:20.880> they're 15:09:21.106 --> 15:09:21.116 align:start position:0% destination on the right but they're 15:09:21.116 --> 15:09:22.730 align:start position:0% destination on the right but they're going<15:09:21.240> to<15:09:21.360> do<15:09:21.540> so<15:09:21.660> in<15:09:21.900> a<15:09:22.020> different<15:09:22.140> way<15:09:22.320> if<15:09:22.616> we 15:09:22.730 --> 15:09:22.740 align:start position:0% going to do so in a different way if we 15:09:22.740 --> 15:09:24.710 align:start position:0% going to do so in a different way if we say<15:09:22.916> that<15:09:23.096> this<15:09:23.276> is<15:09:23.456> the<15:09:23.640> source 15:09:24.710 --> 15:09:24.720 align:start position:0% say that this is the source 15:09:24.720 --> 15:09:28.670 align:start position:0% say that this is the source and<15:09:25.256> this<15:09:25.436> is<15:09:25.680> the<15:09:25.860> destination 15:09:28.670 --> 15:09:28.680 align:start position:0% 15:09:28.680 --> 15:09:30.710 align:start position:0% this<15:09:29.220> is<15:09:29.340> going<15:09:29.520> to<15:09:29.580> alleviate<15:09:30.360> traffic 15:09:30.710 --> 15:09:30.720 align:start position:0% this is going to alleviate traffic 15:09:30.720 --> 15:09:37.550 align:start position:0% this is going to alleviate traffic Network<15:09:31.340> because<15:09:32.340> as<15:09:32.820> you<15:09:33.000> can<15:09:33.116> imagine 15:09:37.550 --> 15:09:37.560 align:start position:0% 15:09:37.560 --> 15:09:39.710 align:start position:0% I<15:09:38.040> don't<15:09:38.096> have<15:09:38.276> to<15:09:38.520> require<15:09:38.756> everything<15:09:39.240> to<15:09:39.596> go 15:09:39.710 --> 15:09:39.720 align:start position:0% I don't have to require everything to go 15:09:39.720 --> 15:09:41.926 align:start position:0% I don't have to require everything to go across<15:09:40.200> this<15:09:40.500> one 15:09:41.926 --> 15:09:41.936 align:start position:0% across this one 15:09:41.936 --> 15:09:43.606 align:start position:0% across this one dedicated<15:09:42.596> line<15:09:42.900> instead<15:09:43.320> it<15:09:43.436> can<15:09:43.560> use 15:09:43.606 --> 15:09:43.616 align:start position:0% dedicated line instead it can use 15:09:43.616 --> 15:09:45.470 align:start position:0% dedicated line instead it can use whichever<15:09:43.916> line<15:09:44.220> has<15:09:44.700> the<15:09:44.880> least<15:09:44.936> traffic<15:09:45.240> on 15:09:45.470 --> 15:09:45.480 align:start position:0% whichever line has the least traffic on 15:09:45.480 --> 15:09:46.970 align:start position:0% whichever line has the least traffic on it<15:09:45.660> at<15:09:45.776> that<15:09:45.956> time<15:09:46.200> and<15:09:46.800> therefore 15:09:46.970 --> 15:09:46.980 align:start position:0% it at that time and therefore 15:09:46.980 --> 15:09:48.650 align:start position:0% it at that time and therefore everything's<15:09:47.400> going<15:09:47.580> to<15:09:47.640> get<15:09:47.880> there<15:09:48.060> without 15:09:48.650 --> 15:09:48.660 align:start position:0% everything's going to get there without 15:09:48.660 --> 15:09:50.630 align:start position:0% everything's going to get there without with<15:09:49.080> the<15:09:49.200> least<15:09:49.320> amount<15:09:49.616> of<15:09:49.740> traffic<15:09:49.916> however 15:09:50.630 --> 15:09:50.640 align:start position:0% with the least amount of traffic however 15:09:50.640 --> 15:09:52.310 align:start position:0% with the least amount of traffic however it's<15:09:50.880> also<15:09:51.180> not<15:09:51.300> the<15:09:51.540> most<15:09:51.660> secure<15:09:52.080> way 15:09:52.310 --> 15:09:52.320 align:start position:0% it's also not the most secure way 15:09:52.320 --> 15:09:54.586 align:start position:0% it's also not the most secure way because<15:09:53.040> obviously<15:09:53.820> there<15:09:54.060> are<15:09:54.240> a<15:09:54.300> lot<15:09:54.416> more 15:09:54.586 --> 15:09:54.596 align:start position:0% because obviously there are a lot more 15:09:54.596 --> 15:09:57.170 align:start position:0% because obviously there are a lot more points<15:09:55.080> for<15:09:55.380> someone<15:09:55.560> to<15:09:55.916> enter<15:09:56.096> in<15:09:56.400> and 15:09:57.170 --> 15:09:57.180 align:start position:0% points for someone to enter in and 15:09:57.180 --> 15:09:59.210 align:start position:0% points for someone to enter in and perhaps<15:09:57.480> steal<15:09:57.956> information<15:09:58.200> or<15:09:58.800> sniff 15:09:59.210 --> 15:09:59.220 align:start position:0% perhaps steal information or sniff 15:09:59.220 --> 15:10:02.030 align:start position:0% perhaps steal information or sniff information<15:09:59.776> and<15:10:00.776> this<15:10:01.200> packet<15:10:01.560> for<15:10:01.800> instance 15:10:02.030 --> 15:10:02.040 align:start position:0% information and this packet for instance 15:10:02.040 --> 15:10:04.490 align:start position:0% information and this packet for instance might<15:10:02.340> have<15:10:02.456> been<15:10:02.580> gobbled<15:10:03.060> up<15:10:03.180> by<15:10:03.720> a<15:10:04.200> hacker 15:10:04.490 --> 15:10:04.500 align:start position:0% might have been gobbled up by a hacker 15:10:04.500 --> 15:10:06.710 align:start position:0% might have been gobbled up by a hacker someone<15:10:04.800> who<15:10:05.040> wanted<15:10:05.220> to<15:10:05.596> get<15:10:06.596> the 15:10:06.710 --> 15:10:06.720 align:start position:0% someone who wanted to get the 15:10:06.720 --> 15:10:08.570 align:start position:0% someone who wanted to get the information<15:10:06.900> or<15:10:07.256> it<15:10:07.500> somehow<15:10:07.860> just<15:10:08.040> got<15:10:08.220> lost 15:10:08.570 --> 15:10:08.580 align:start position:0% information or it somehow just got lost 15:10:08.580 --> 15:10:10.490 align:start position:0% information or it somehow just got lost so<15:10:09.116> this<15:10:09.180> is<15:10:09.300> where<15:10:09.416> the<15:10:09.596> issues<15:10:09.900> with<15:10:10.080> packet 15:10:10.490 --> 15:10:10.500 align:start position:0% so this is where the issues with packet 15:10:10.500 --> 15:10:12.530 align:start position:0% so this is where the issues with packet switching<15:10:10.916> come<15:10:11.220> in 15:10:12.530 --> 15:10:12.540 align:start position:0% switching come in 15:10:12.540 --> 15:10:14.630 align:start position:0% switching come in now<15:10:13.080> in<15:10:13.380> the<15:10:13.500> last<15:10:13.560> module<15:10:14.040> we<15:10:14.276> talked<15:10:14.520> about 15:10:14.630 --> 15:10:14.640 align:start position:0% now in the last module we talked about 15:10:14.640 --> 15:10:15.586 align:start position:0% now in the last module we talked about many<15:10:15.000> of<15:10:15.116> the<15:10:15.180> different<15:10:15.300> transmission 15:10:15.586 --> 15:10:15.596 align:start position:0% many of the different transmission 15:10:15.596 --> 15:10:17.810 align:start position:0% many of the different transmission technologies<15:10:16.436> that<15:10:16.800> Wan<15:10:17.040> has<15:10:17.340> in<15:10:17.520> one<15:10:17.700> of 15:10:17.810 --> 15:10:17.820 align:start position:0% technologies that Wan has in one of 15:10:17.820 --> 15:10:22.330 align:start position:0% technologies that Wan has in one of those<15:10:17.936> if<15:10:18.180> you<15:10:18.300> recall<15:10:18.660> was<15:10:19.560> ATM<15:10:20.456> or 15:10:22.330 --> 15:10:22.340 align:start position:0% those if you recall was ATM or 15:10:22.340 --> 15:10:24.830 align:start position:0% those if you recall was ATM or asynchronous<15:10:23.340> transfer<15:10:23.756> mode<15:10:23.936> and<15:10:24.480> imagine 15:10:24.830 --> 15:10:24.840 align:start position:0% asynchronous transfer mode and imagine 15:10:24.840 --> 15:10:27.946 align:start position:0% asynchronous transfer mode and imagine that<15:10:25.256> name<15:10:25.436> asynchronous 15:10:27.946 --> 15:10:27.956 align:start position:0% that name asynchronous 15:10:27.956 --> 15:10:29.870 align:start position:0% that name asynchronous that's<15:10:28.436> important<15:10:28.916> because<15:10:29.220> it's<15:10:29.456> not<15:10:29.640> at<15:10:29.756> the 15:10:29.870 --> 15:10:29.880 align:start position:0% that's important because it's not at the 15:10:29.880 --> 15:10:32.810 align:start position:0% that's important because it's not at the same<15:10:30.000> time<15:10:30.116> it's<15:10:30.416> asynchronous<15:10:31.256> now<15:10:32.096> ATM 15:10:32.810 --> 15:10:32.820 align:start position:0% same time it's asynchronous now ATM 15:10:32.820 --> 15:10:36.530 align:start position:0% same time it's asynchronous now ATM splits<15:10:33.540> data<15:10:33.956> packets<15:10:34.256> into<15:10:34.916> these<15:10:35.400> cells<15:10:36.060> and 15:10:36.530 --> 15:10:36.540 align:start position:0% splits data packets into these cells and 15:10:36.540 --> 15:10:39.350 align:start position:0% splits data packets into these cells and these<15:10:36.776> cells<15:10:37.080> again<15:10:37.200> are<15:10:37.560> 53<15:10:37.916> bytes<15:10:38.456> in<15:10:39.180> order 15:10:39.350 --> 15:10:39.360 align:start position:0% these cells again are 53 bytes in order 15:10:39.360 --> 15:10:41.510 align:start position:0% these cells again are 53 bytes in order to<15:10:39.540> send<15:10:39.720> them<15:10:39.956> now<15:10:40.616> this<15:10:40.800> made<15:10:40.980> data<15:10:41.340> flow 15:10:41.510 --> 15:10:41.520 align:start position:0% to send them now this made data flow 15:10:41.520 --> 15:10:43.246 align:start position:0% to send them now this made data flow simple<15:10:41.700> and<15:10:42.000> it<15:10:42.116> did<15:10:42.240> not<15:10:42.416> back<15:10:42.720> up<15:10:42.900> the<15:10:43.080> system 15:10:43.246 --> 15:10:43.256 align:start position:0% simple and it did not back up the system 15:10:43.256 --> 15:10:45.406 align:start position:0% simple and it did not back up the system and<15:10:43.560> didn't<15:10:43.740> cause<15:10:43.980> too<15:10:44.160> much<15:10:44.340> traffic<15:10:44.640> so 15:10:45.406 --> 15:10:45.416 align:start position:0% and didn't cause too much traffic so 15:10:45.416 --> 15:10:48.710 align:start position:0% and didn't cause too much traffic so very<15:10:45.776> similar<15:10:46.080> to<15:10:46.380> ATM<15:10:46.860> is<15:10:47.276> what<15:10:47.456> we<15:10:47.580> call<15:10:47.756> cell 15:10:48.710 --> 15:10:48.720 align:start position:0% very similar to ATM is what we call cell 15:10:48.720 --> 15:10:49.906 align:start position:0% very similar to ATM is what we call cell relay 15:10:49.906 --> 15:10:49.916 align:start position:0% relay 15:10:49.916 --> 15:10:52.730 align:start position:0% relay so<15:10:50.456> relay<15:10:51.000> is<15:10:51.240> a<15:10:51.416> connectivity<15:10:51.956> method<15:10:52.436> that 15:10:52.730 --> 15:10:52.740 align:start position:0% so relay is a connectivity method that 15:10:52.740 --> 15:10:56.030 align:start position:0% so relay is a connectivity method that breaks<15:10:53.160> data<15:10:53.640> up<15:10:53.820> into<15:10:54.720> equal<15:10:55.140> size<15:10:55.500> cells<15:10:55.980> and 15:10:56.030 --> 15:10:56.040 align:start position:0% breaks data up into equal size cells and 15:10:56.040 --> 15:10:58.070 align:start position:0% breaks data up into equal size cells and then<15:10:56.220> sends<15:10:56.520> them<15:10:56.580> to<15:10:56.700> the<15:10:56.820> destination<15:10:57.300> now 15:10:58.070 --> 15:10:58.080 align:start position:0% then sends them to the destination now 15:10:58.080 --> 15:11:00.406 align:start position:0% then sends them to the destination now unlike<15:10:58.740> ATM<15:10:59.400> these<15:10:59.820> cells<15:11:00.116> aren't 15:11:00.406 --> 15:11:00.416 align:start position:0% unlike ATM these cells aren't 15:11:00.416 --> 15:11:03.530 align:start position:0% unlike ATM these cells aren't necessarily<15:11:01.200> 53<15:11:01.980> bytes<15:11:02.456> but<15:11:03.060> they're<15:11:03.300> all 15:11:03.530 --> 15:11:03.540 align:start position:0% necessarily 53 bytes but they're all 15:11:03.540 --> 15:11:05.086 align:start position:0% necessarily 53 bytes but they're all even<15:11:03.720> with<15:11:03.956> each<15:11:04.200> other 15:11:05.086 --> 15:11:05.096 align:start position:0% even with each other 15:11:05.096 --> 15:11:07.070 align:start position:0% even with each other so<15:11:05.640> they're<15:11:06.180> all<15:11:06.300> sent<15:11:06.480> across<15:11:06.840> the<15:11:06.956> network 15:11:07.070 --> 15:11:07.080 align:start position:0% so they're all sent across the network 15:11:07.080 --> 15:11:09.530 align:start position:0% so they're all sent across the network and<15:11:07.616> they<15:11:07.916> all 15:11:09.530 --> 15:11:09.540 align:start position:0% and they all 15:11:09.540 --> 15:11:11.630 align:start position:0% and they all are<15:11:09.956> even<15:11:10.200> meaning<15:11:10.560> they<15:11:10.916> each<15:11:11.096> have<15:11:11.276> the<15:11:11.580> same 15:11:11.630 --> 15:11:11.640 align:start position:0% are even meaning they each have the same 15:11:11.640 --> 15:11:14.150 align:start position:0% are even meaning they each have the same amount<15:11:11.820> of<15:11:12.060> bytes<15:11:12.480> now<15:11:13.080> the<15:11:13.256> data<15:11:13.560> itself<15:11:13.800> is 15:11:14.150 --> 15:11:14.160 align:start position:0% amount of bytes now the data itself is 15:11:14.160 --> 15:11:15.766 align:start position:0% amount of bytes now the data itself is transferred<15:11:14.640> very<15:11:14.820> similar<15:11:15.180> to<15:11:15.300> a<15:11:15.480> method 15:11:15.766 --> 15:11:15.776 align:start position:0% transferred very similar to a method 15:11:15.776 --> 15:11:17.446 align:start position:0% transferred very similar to a method that<15:11:16.140> we<15:11:16.256> just<15:11:16.380> talked<15:11:16.616> about<15:11:16.740> in<15:11:16.980> packet 15:11:17.446 --> 15:11:17.456 align:start position:0% that we just talked about in packet 15:11:17.456 --> 15:11:19.246 align:start position:0% that we just talked about in packet switching<15:11:17.880> the<15:11:18.416> difference<15:11:18.540> is<15:11:18.720> that<15:11:18.900> packet 15:11:19.246 --> 15:11:19.256 align:start position:0% switching the difference is that packet 15:11:19.256 --> 15:11:20.746 align:start position:0% switching the difference is that packet switching<15:11:19.616> doesn't<15:11:19.800> evenly<15:11:20.220> break<15:11:20.340> up<15:11:20.520> the 15:11:20.746 --> 15:11:20.756 align:start position:0% switching doesn't evenly break up the 15:11:20.756 --> 15:11:22.426 align:start position:0% switching doesn't evenly break up the packs<15:11:21.116> which<15:11:21.596> could<15:11:21.776> cause<15:11:22.020> some<15:11:22.256> Network 15:11:22.426 --> 15:11:22.436 align:start position:0% packs which could cause some Network 15:11:22.436 --> 15:11:24.766 align:start position:0% packs which could cause some Network traffic<15:11:22.800> so<15:11:23.400> cell<15:11:23.580> relay<15:11:23.936> is<15:11:24.180> good<15:11:24.480> for 15:11:24.766 --> 15:11:24.776 align:start position:0% traffic so cell relay is good for 15:11:24.776 --> 15:11:27.106 align:start position:0% traffic so cell relay is good for simultaneous<15:11:25.616> transfer<15:11:26.220> of<15:11:26.340> data<15:11:26.700> and<15:11:26.820> voice 15:11:27.106 --> 15:11:27.116 align:start position:0% simultaneous transfer of data and voice 15:11:27.116 --> 15:11:30.766 align:start position:0% simultaneous transfer of data and voice meaning<15:11:27.900> it<15:11:28.256> allows<15:11:28.560> me<15:11:28.680> to<15:11:28.916> do<15:11:29.096> voice<15:11:29.776> and 15:11:30.766 --> 15:11:30.776 align:start position:0% meaning it allows me to do voice and 15:11:30.776 --> 15:11:32.150 align:start position:0% meaning it allows me to do voice and data 15:11:32.150 --> 15:11:32.160 align:start position:0% data 15:11:32.160 --> 15:11:35.446 align:start position:0% data at<15:11:32.820> the<15:11:32.936> same<15:11:33.116> time<15:11:33.360> however<15:11:34.320> just<15:11:35.040> like<15:11:35.220> with 15:11:35.446 --> 15:11:35.456 align:start position:0% at the same time however just like with 15:11:35.456 --> 15:11:37.130 align:start position:0% at the same time however just like with packet<15:11:35.756> switching<15:11:36.116> it's<15:11:36.300> not<15:11:36.540> very<15:11:36.776> secure 15:11:37.130 --> 15:11:37.140 align:start position:0% packet switching it's not very secure 15:11:37.140 --> 15:11:39.106 align:start position:0% packet switching it's not very secure and<15:11:37.800> some<15:11:38.040> of<15:11:38.096> the<15:11:38.220> cells<15:11:38.520> could<15:11:38.700> also<15:11:38.936> be 15:11:39.106 --> 15:11:39.116 align:start position:0% and some of the cells could also be 15:11:39.116 --> 15:11:41.690 align:start position:0% and some of the cells could also be easily<15:11:39.480> lost<15:11:39.776> along<15:11:40.256> the<15:11:40.500> way<15:11:40.616> now<15:11:41.276> as<15:11:41.456> we<15:11:41.580> all 15:11:41.690 --> 15:11:41.700 align:start position:0% easily lost along the way now as we all 15:11:41.700 --> 15:11:45.530 align:start position:0% easily lost along the way now as we all know<15:11:41.880> voice<15:11:42.360> over<15:11:42.660> IP<15:11:43.340> has<15:11:44.340> sort<15:11:44.756> of<15:11:44.880> taken<15:11:45.416> the 15:11:45.530 --> 15:11:45.540 align:start position:0% know voice over IP has sort of taken the 15:11:45.540 --> 15:11:47.690 align:start position:0% know voice over IP has sort of taken the World<15:11:45.660> by<15:11:45.956> storm<15:11:46.200> international<15:11:46.740> calling<15:11:47.456> can 15:11:47.690 --> 15:11:47.700 align:start position:0% World by storm international calling can 15:11:47.700 --> 15:11:50.330 align:start position:0% World by storm international calling can be<15:11:48.000> really<15:11:48.540> really<15:11:48.776> expensive<15:11:49.560> and<15:11:49.980> so<15:11:50.096> voice 15:11:50.330 --> 15:11:50.340 align:start position:0% be really really expensive and so voice 15:11:50.340 --> 15:11:52.426 align:start position:0% be really really expensive and so voice over<15:11:50.580> IP<15:11:51.000> is<15:11:51.240> a<15:11:51.480> way<15:11:51.596> to<15:11:51.720> make<15:11:51.840> calls<15:11:52.200> through 15:11:52.426 --> 15:11:52.436 align:start position:0% over IP is a way to make calls through 15:11:52.436 --> 15:11:55.310 align:start position:0% over IP is a way to make calls through IP<15:11:52.860> packets<15:11:53.400> or<15:11:54.060> using<15:11:54.480> the<15:11:54.596> internet<15:11:54.720> you 15:11:55.310 --> 15:11:55.320 align:start position:0% IP packets or using the internet you 15:11:55.320 --> 15:11:57.586 align:start position:0% IP packets or using the internet you recall<15:11:55.680> IP<15:11:56.160> packets<15:11:56.640> are<15:11:56.820> part<15:11:57.000> of<15:11:57.060> the<15:11:57.180> TCP 15:11:57.586 --> 15:11:57.596 align:start position:0% recall IP packets are part of the TCP 15:11:57.596 --> 15:12:00.470 align:start position:0% recall IP packets are part of the TCP Suite<15:11:58.500> they<15:11:59.040> involve<15:11:59.400> giving<15:11:59.700> every<15:12:00.180> single 15:12:00.470 --> 15:12:00.480 align:start position:0% Suite they involve giving every single 15:12:00.480 --> 15:12:02.810 align:start position:0% Suite they involve giving every single device<15:12:00.776> on<15:12:01.140> a<15:12:01.256> network<15:12:01.436> and<15:12:01.740> IP<15:12:02.160> address<15:12:02.400> which 15:12:02.810 --> 15:12:02.820 align:start position:0% device on a network and IP address which 15:12:02.820 --> 15:12:04.670 align:start position:0% device on a network and IP address which is<15:12:02.936> just<15:12:03.116> like<15:12:03.300> a<15:12:03.660> phone<15:12:03.840> number<15:12:04.020> in<15:12:04.320> an<15:12:04.500> old 15:12:04.670 --> 15:12:04.680 align:start position:0% is just like a phone number in an old 15:12:04.680 --> 15:12:08.926 align:start position:0% is just like a phone number in an old system<15:12:05.060> and<15:12:06.060> uh<15:12:06.900> this<15:12:07.320> would<15:12:07.500> allow<15:12:07.980> us<15:12:08.700> to 15:12:08.926 --> 15:12:08.936 align:start position:0% system and uh this would allow us to 15:12:08.936 --> 15:12:11.746 align:start position:0% system and uh this would allow us to save<15:12:09.116> money<15:12:09.360> on<15:12:09.720> international<15:12:10.140> calls<15:12:11.096> it's 15:12:11.746 --> 15:12:11.756 align:start position:0% save money on international calls it's 15:12:11.756 --> 15:12:13.730 align:start position:0% save money on international calls it's by<15:12:12.000> far<15:12:12.240> cheaper<15:12:12.840> alternative<15:12:13.200> to<15:12:13.436> a<15:12:13.616> phone 15:12:13.730 --> 15:12:13.740 align:start position:0% by far cheaper alternative to a phone 15:12:13.740 --> 15:12:15.730 align:start position:0% by far cheaper alternative to a phone service<15:12:14.040> because<15:12:14.400> unlike<15:12:15.000> a<15:12:15.240> phone<15:12:15.416> service 15:12:15.730 --> 15:12:15.740 align:start position:0% service because unlike a phone service 15:12:15.740 --> 15:12:18.470 align:start position:0% service because unlike a phone service there<15:12:16.740> are<15:12:16.916> no<15:12:17.160> monthly<15:12:17.520> bills<15:12:17.936> to<15:12:18.060> pay<15:12:18.180> and 15:12:18.470 --> 15:12:18.480 align:start position:0% there are no monthly bills to pay and 15:12:18.480 --> 15:12:20.690 align:start position:0% there are no monthly bills to pay and there<15:12:18.720> are<15:12:18.900> no<15:12:19.140> long<15:12:19.380> distance<15:12:19.680> charges<15:12:20.520> to 15:12:20.690 --> 15:12:20.700 align:start position:0% there are no long distance charges to 15:12:20.700 --> 15:12:23.446 align:start position:0% there are no long distance charges to deal<15:12:20.880> with<15:12:21.060> so<15:12:21.660> VoIP<15:12:22.140> uses<15:12:22.860> the<15:12:23.096> existing 15:12:23.446 --> 15:12:23.456 align:start position:0% deal with so VoIP uses the existing 15:12:23.456 --> 15:12:24.890 align:start position:0% deal with so VoIP uses the existing internet<15:12:23.700> infrastructure<15:12:24.480> that's<15:12:24.660> already 15:12:24.890 --> 15:12:24.900 align:start position:0% internet infrastructure that's already 15:12:24.900 --> 15:12:27.350 align:start position:0% internet infrastructure that's already in<15:12:25.140> place<15:12:25.320> to<15:12:25.916> make<15:12:26.040> connections<15:12:26.640> for<15:12:26.936> calls 15:12:27.350 --> 15:12:27.360 align:start position:0% in place to make connections for calls 15:12:27.360 --> 15:12:29.030 align:start position:0% in place to make connections for calls and<15:12:27.660> what<15:12:27.840> it<15:12:27.956> does<15:12:28.080> is<15:12:28.320> it 15:12:29.030 --> 15:12:29.040 align:start position:0% and what it does is it 15:12:29.040 --> 15:12:31.850 align:start position:0% and what it does is it basically<15:12:29.936> puts<15:12:30.480> the<15:12:30.660> information<15:12:30.840> from<15:12:31.616> your 15:12:31.850 --> 15:12:31.860 align:start position:0% basically puts the information from your 15:12:31.860 --> 15:12:34.190 align:start position:0% basically puts the information from your voice<15:12:32.040> into<15:12:32.580> packets<15:12:33.116> and<15:12:33.480> streams<15:12:33.956> those 15:12:34.190 --> 15:12:34.200 align:start position:0% voice into packets and streams those 15:12:34.200 --> 15:12:36.710 align:start position:0% voice into packets and streams those across<15:12:35.160> a<15:12:35.276> network<15:12:35.456> now<15:12:36.116> like<15:12:36.416> almost 15:12:36.710 --> 15:12:36.720 align:start position:0% across a network now like almost 15:12:36.720 --> 15:12:38.390 align:start position:0% across a network now like almost everything<15:12:37.200> in<15:12:37.500> Computing<15:12:37.860> there<15:12:38.096> is<15:12:38.220> a 15:12:38.390 --> 15:12:38.400 align:start position:0% everything in Computing there is a 15:12:38.400 --> 15:12:40.730 align:start position:0% everything in Computing there is a protocol<15:12:38.700> that<15:12:39.116> allows<15:12:39.480> this<15:12:39.776> to<15:12:39.956> work<15:12:40.140> and 15:12:40.730 --> 15:12:40.740 align:start position:0% protocol that allows this to work and 15:12:40.740 --> 15:12:43.606 align:start position:0% protocol that allows this to work and that<15:12:40.916> is<15:12:41.096> called<15:12:41.540> the<15:12:42.540> session<15:12:42.776> initiation 15:12:43.606 --> 15:12:43.616 align:start position:0% that is called the session initiation 15:12:43.616 --> 15:12:45.050 align:start position:0% that is called the session initiation protocol 15:12:45.050 --> 15:12:45.060 align:start position:0% protocol 15:12:45.060 --> 15:12:46.730 align:start position:0% protocol or<15:12:45.840> sip 15:12:46.730 --> 15:12:46.740 align:start position:0% or sip 15:12:46.740 --> 15:12:52.606 align:start position:0% or sip write<15:12:47.160> that<15:12:47.340> out 15:12:52.606 --> 15:12:52.616 align:start position:0% 15:12:52.616 --> 15:12:55.246 align:start position:0% now<15:12:52.980> if<15:12:53.276> you<15:12:53.456> see<15:12:53.640> sip<15:12:54.116> on<15:12:54.300> the<15:12:54.416> test<15:12:54.596> or<15:12:54.956> if<15:12:55.080> you 15:12:55.246 --> 15:12:55.256 align:start position:0% now if you see sip on the test or if you 15:12:55.256 --> 15:12:58.550 align:start position:0% now if you see sip on the test or if you see<15:12:55.456> voice<15:12:56.456> over<15:12:56.640> IP<15:12:57.116> on<15:12:57.360> the<15:12:57.540> test<15:12:57.660> you<15:12:58.080> can<15:12:58.200> be 15:12:58.550 --> 15:12:58.560 align:start position:0% see voice over IP on the test you can be 15:12:58.560 --> 15:13:00.650 align:start position:0% see voice over IP on the test you can be guaranteed<15:12:59.220> they're<15:12:59.700> related<15:13:00.116> the<15:13:00.596> other 15:13:00.650 --> 15:13:00.660 align:start position:0% guaranteed they're related the other 15:13:00.660 --> 15:13:02.570 align:start position:0% guaranteed they're related the other thing<15:13:00.840> you're<15:13:00.956> going<15:13:01.140> to<15:13:01.256> see<15:13:01.320> when<15:13:01.560> it<15:13:01.680> comes 15:13:02.570 --> 15:13:02.580 align:start position:0% thing you're going to see when it comes 15:13:02.580 --> 15:13:08.926 align:start position:0% thing you're going to see when it comes to<15:13:03.060> voice<15:13:03.240> over<15:13:03.416> p<15:13:03.776> is<15:13:04.140> called<15:13:04.436> qos<15:13:05.400> or<15:13:06.000> quality 15:13:08.926 --> 15:13:08.936 align:start position:0% 15:13:08.936 --> 15:13:10.730 align:start position:0% of 15:13:10.730 --> 15:13:10.740 align:start position:0% of 15:13:10.740 --> 15:13:13.070 align:start position:0% of service<15:13:11.520> the<15:13:12.180> reason<15:13:12.300> is<15:13:12.540> we<15:13:12.776> want<15:13:12.900> to<15:13:13.020> make 15:13:13.070 --> 15:13:13.080 align:start position:0% service the reason is we want to make 15:13:13.080 --> 15:13:14.390 align:start position:0% service the reason is we want to make sure<15:13:13.256> the<15:13:13.436> quality<15:13:13.800> is<15:13:13.916> pretty<15:13:14.160> good 15:13:14.390 --> 15:13:14.400 align:start position:0% sure the quality is pretty good 15:13:14.400 --> 15:13:17.086 align:start position:0% sure the quality is pretty good otherwise<15:13:15.000> if<15:13:15.240> we're<15:13:15.416> getting<15:13:15.660> the<15:13:16.256> packet<15:13:16.680> at 15:13:17.086 --> 15:13:17.096 align:start position:0% otherwise if we're getting the packet at 15:13:17.096 --> 15:13:18.890 align:start position:0% otherwise if we're getting the packet at the<15:13:17.220> end<15:13:17.340> you<15:13:17.700> know<15:13:17.820> if<15:13:17.880> we're<15:13:17.936> getting<15:13:18.116> uh<15:13:18.480> if 15:13:18.890 --> 15:13:18.900 align:start position:0% the end you know if we're getting uh if 15:13:18.900 --> 15:13:20.266 align:start position:0% the end you know if we're getting uh if I<15:13:19.080> say<15:13:19.200> a<15:13:19.320> sentence<15:13:19.560> and<15:13:19.740> I<15:13:19.860> get<15:13:19.980> the<15:13:20.040> end<15:13:20.160> of 15:13:20.266 --> 15:13:20.276 align:start position:0% I say a sentence and I get the end of 15:13:20.276 --> 15:13:21.230 align:start position:0% I say a sentence and I get the end of the<15:13:20.400> sentence<15:13:20.640> before<15:13:20.756> I<15:13:20.936> get<15:13:21.000> the<15:13:21.116> beginning 15:13:21.230 --> 15:13:21.240 align:start position:0% the sentence before I get the beginning 15:13:21.240 --> 15:13:22.606 align:start position:0% the sentence before I get the beginning of<15:13:21.416> the<15:13:21.480> sentence<15:13:21.720> then<15:13:21.956> the<15:13:22.080> quality<15:13:22.380> is<15:13:22.500> not 15:13:22.606 --> 15:13:22.616 align:start position:0% of the sentence then the quality is not 15:13:22.616 --> 15:13:24.350 align:start position:0% of the sentence then the quality is not really<15:13:22.800> good<15:13:23.040> and<15:13:23.340> I<15:13:23.456> can't<15:13:23.580> really<15:13:23.756> rely<15:13:24.180> on 15:13:24.350 --> 15:13:24.360 align:start position:0% really good and I can't really rely on 15:13:24.360 --> 15:13:26.810 align:start position:0% really good and I can't really rely on this<15:13:24.900> so<15:13:25.380> getting<15:13:25.680> back<15:13:25.916> to<15:13:26.040> sip<15:13:26.276> for<15:13:26.520> a<15:13:26.640> second 15:13:26.810 --> 15:13:26.820 align:start position:0% this so getting back to sip for a second 15:13:26.820 --> 15:13:29.086 align:start position:0% this so getting back to sip for a second this<15:13:27.480> is<15:13:27.596> the<15:13:27.956> protocol<15:13:28.256> that's<15:13:28.616> designed<15:13:28.980> to 15:13:29.086 --> 15:13:29.096 align:start position:0% this is the protocol that's designed to 15:13:29.096 --> 15:13:31.550 align:start position:0% this is the protocol that's designed to set<15:13:29.220> up<15:13:29.400> and<15:13:29.640> maintain<15:13:30.060> internet<15:13:30.596> multimedia 15:13:31.550 --> 15:13:31.560 align:start position:0% set up and maintain internet multimedia 15:13:31.560 --> 15:13:34.970 align:start position:0% set up and maintain internet multimedia sessions<15:13:32.220> such<15:13:32.756> as<15:13:33.000> voice<15:13:33.540> calls<15:13:34.080> it's<15:13:34.680> also 15:13:34.970 --> 15:13:34.980 align:start position:0% sessions such as voice calls it's also 15:13:34.980 --> 15:13:36.710 align:start position:0% sessions such as voice calls it's also responsible<15:13:35.400> for<15:13:35.820> communication<15:13:36.416> that's 15:13:36.710 --> 15:13:36.720 align:start position:0% responsible for communication that's 15:13:36.720 --> 15:13:39.470 align:start position:0% responsible for communication that's used<15:13:37.020> in<15:13:37.680> video<15:13:38.040> and<15:13:38.456> audio<15:13:38.700> conferencing 15:13:39.470 --> 15:13:39.480 align:start position:0% used in video and audio conferencing 15:13:39.480 --> 15:13:42.050 align:start position:0% used in video and audio conferencing online<15:13:40.200> games<15:13:40.740> voice<15:13:41.276> Chats<15:13:41.756> on<15:13:41.880> the<15:13:42.000> internet 15:13:42.050 --> 15:13:42.060 align:start position:0% online games voice Chats on the internet 15:13:42.060 --> 15:13:44.690 align:start position:0% online games voice Chats on the internet and<15:13:42.416> so<15:13:42.596> on<15:13:42.720> so<15:13:43.200> it's<15:13:43.500> extremely<15:13:44.276> important 15:13:44.690 --> 15:13:44.700 align:start position:0% and so on so it's extremely important 15:13:44.700 --> 15:13:46.670 align:start position:0% and so on so it's extremely important and<15:13:44.820> without<15:13:45.060> it<15:13:45.360> basically<15:13:45.776> VoIP<15:13:46.380> wouldn't 15:13:46.670 --> 15:13:46.680 align:start position:0% and without it basically VoIP wouldn't 15:13:46.680 --> 15:13:47.690 align:start position:0% and without it basically VoIP wouldn't function 15:13:47.690 --> 15:13:47.700 align:start position:0% function 15:13:47.700 --> 15:13:50.630 align:start position:0% function so<15:13:48.240> here's<15:13:48.660> an<15:13:48.956> example<15:13:49.320> of<15:13:49.560> what<15:13:49.800> VoIP<15:13:50.220> might 15:13:50.630 --> 15:13:50.640 align:start position:0% so here's an example of what VoIP might 15:13:50.640 --> 15:13:53.810 align:start position:0% so here's an example of what VoIP might look<15:13:50.880> like<15:13:51.060> as<15:13:51.660> you<15:13:51.840> can<15:13:51.900> see<15:13:52.080> there's<15:13:52.680> both<15:13:53.040> a 15:13:53.810 --> 15:13:53.820 align:start position:0% look like as you can see there's both a 15:13:53.820 --> 15:13:55.850 align:start position:0% look like as you can see there's both a phone<15:13:54.360> and<15:13:54.776> a<15:13:54.956> computer<15:13:55.080> that<15:13:55.436> are<15:13:55.560> connected 15:13:55.850 --> 15:13:55.860 align:start position:0% phone and a computer that are connected 15:13:55.860 --> 15:13:57.946 align:start position:0% phone and a computer that are connected to<15:13:56.040> this<15:13:56.220> network<15:13:56.400> on<15:13:56.820> the<15:13:57.000> top<15:13:57.116> end 15:13:57.946 --> 15:13:57.956 align:start position:0% to this network on the top end 15:13:57.956 --> 15:14:00.830 align:start position:0% to this network on the top end PC<15:13:58.560> connects<15:13:59.096> through<15:13:59.276> a<15:13:59.456> modem<15:13:59.756> or<15:14:00.480> perhaps 15:14:00.830 --> 15:14:00.840 align:start position:0% PC connects through a modem or perhaps 15:14:00.840 --> 15:14:03.290 align:start position:0% PC connects through a modem or perhaps even<15:14:01.140> a<15:14:01.560> network<15:14:01.860> card 15:14:03.290 --> 15:14:03.300 align:start position:0% even a network card 15:14:03.300 --> 15:14:05.990 align:start position:0% even a network card and<15:14:03.900> the<15:14:04.140> telephone<15:14:04.580> connects<15:14:05.580> through<15:14:05.756> some 15:14:05.990 --> 15:14:06.000 align:start position:0% and the telephone connects through some 15:14:06.000 --> 15:14:07.906 align:start position:0% and the telephone connects through some sort<15:14:06.180> of<15:14:06.300> adapter<15:14:06.840> and<15:14:07.380> they<15:14:07.560> both<15:14:07.680> connect 15:14:07.906 --> 15:14:07.916 align:start position:0% sort of adapter and they both connect 15:14:07.916 --> 15:14:09.650 align:start position:0% sort of adapter and they both connect through<15:14:08.276> the<15:14:08.520> internet<15:14:08.700> generally<15:14:09.300> there's 15:14:09.650 --> 15:14:09.660 align:start position:0% through the internet generally there's 15:14:09.660 --> 15:14:11.690 align:start position:0% through the internet generally there's also<15:14:10.020> one<15:14:10.256> box<15:14:10.500> that<15:14:10.916> everything<15:14:11.220> sort<15:14:11.580> of 15:14:11.690 --> 15:14:11.700 align:start position:0% also one box that everything sort of 15:14:11.700 --> 15:14:14.690 align:start position:0% also one box that everything sort of connects<15:14:12.060> into<15:14:12.180> and<15:14:12.956> that<15:14:13.140> sends<15:14:13.500> it<15:14:13.616> out<15:14:13.800> into 15:14:14.690 --> 15:14:14.700 align:start position:0% connects into and that sends it out into 15:14:14.700 --> 15:14:17.086 align:start position:0% connects into and that sends it out into the<15:14:15.416> internet<15:14:15.776> out<15:14:16.256> to<15:14:16.436> your<15:14:16.860> internet 15:14:17.086 --> 15:14:17.096 align:start position:0% the internet out to your internet 15:14:17.096 --> 15:14:19.550 align:start position:0% the internet out to your internet service<15:14:17.400> provider<15:14:18.060> and<15:14:18.596> again<15:14:18.776> the<15:14:19.200> important 15:14:19.550 --> 15:14:19.560 align:start position:0% service provider and again the important 15:14:19.560 --> 15:14:21.050 align:start position:0% service provider and again the important thing<15:14:19.680> here<15:14:19.860> is<15:14:20.040> that<15:14:20.220> everything<15:14:20.456> is<15:14:20.820> being 15:14:21.050 --> 15:14:21.060 align:start position:0% thing here is that everything is being 15:14:21.060 --> 15:14:23.510 align:start position:0% thing here is that everything is being captured<15:14:21.540> into<15:14:21.776> IP<15:14:22.256> packets<15:14:22.740> so<15:14:23.160> your<15:14:23.400> voice 15:14:23.510 --> 15:14:23.520 align:start position:0% captured into IP packets so your voice 15:14:23.520 --> 15:14:26.266 align:start position:0% captured into IP packets so your voice is<15:14:23.700> being<15:14:23.936> turned<15:14:24.480> into<15:14:25.020> for<15:14:25.800> lack<15:14:26.096> of<15:14:26.160> a 15:14:26.266 --> 15:14:26.276 align:start position:0% is being turned into for lack of a 15:14:26.276 --> 15:14:28.490 align:start position:0% is being turned into for lack of a better<15:14:26.400> term<15:14:26.580> data<15:14:27.240> in<15:14:27.540> an<15:14:27.660> IP<15:14:27.956> packet<15:14:28.320> which 15:14:28.490 --> 15:14:28.500 align:start position:0% better term data in an IP packet which 15:14:28.500 --> 15:14:31.670 align:start position:0% better term data in an IP packet which can<15:14:28.680> then<15:14:28.800> be<15:14:28.980> sent<15:14:29.276> over<15:14:29.820> the<15:14:30.180> internet 15:14:31.670 --> 15:14:31.680 align:start position:0% can then be sent over the internet 15:14:31.680 --> 15:14:34.190 align:start position:0% can then be sent over the internet great<15:14:32.276> so<15:14:32.640> now<15:14:32.820> we've<15:14:33.060> identified<15:14:33.540> some<15:14:33.900> Wan 15:14:34.190 --> 15:14:34.200 align:start position:0% great so now we've identified some Wan 15:14:34.200 --> 15:14:36.290 align:start position:0% great so now we've identified some Wan connectivity<15:14:34.800> options<15:14:35.160> including<15:14:35.756> a<15:14:35.936> leased 15:14:36.290 --> 15:14:36.300 align:start position:0% connectivity options including a leased 15:14:36.300 --> 15:14:38.390 align:start position:0% connectivity options including a leased line<15:14:36.416> which<15:14:36.720> is<15:14:36.900> a<15:14:37.200> line<15:14:37.436> that<15:14:37.800> you<15:14:37.980> lease 15:14:38.390 --> 15:14:38.400 align:start position:0% line which is a line that you lease 15:14:38.400 --> 15:14:41.330 align:start position:0% line which is a line that you lease between<15:14:39.180> two<15:14:39.900> places<15:14:40.320> an<15:14:40.740> example<15:14:40.980> of<15:14:41.160> that 15:14:41.330 --> 15:14:41.340 align:start position:0% between two places an example of that 15:14:41.340 --> 15:14:44.266 align:start position:0% between two places an example of that would<15:14:41.520> be<15:14:41.640> that<15:14:41.820> T1<15:14:42.300> or<15:14:42.956> that<15:14:43.140> T3<15:14:43.560> line<15:14:43.860> the 15:14:44.266 --> 15:14:44.276 align:start position:0% would be that T1 or that T3 line the 15:14:44.276 --> 15:14:45.350 align:start position:0% would be that T1 or that T3 line the reason<15:14:44.400> it's<15:14:44.580> leased<15:14:44.880> is<15:14:44.936> we<15:14:45.116> don't<15:14:45.240> actually 15:14:45.350 --> 15:14:45.360 align:start position:0% reason it's leased is we don't actually 15:14:45.360 --> 15:14:47.030 align:start position:0% reason it's leased is we don't actually put<15:14:45.596> it<15:14:45.720> in<15:14:45.840> the<15:14:46.020> Telecommunications<15:14:46.680> Company 15:14:47.030 --> 15:14:47.040 align:start position:0% put it in the Telecommunications Company 15:14:47.040 --> 15:14:49.130 align:start position:0% put it in the Telecommunications Company does<15:14:47.340> that<15:14:47.520> for<15:14:47.700> us<15:14:47.880> we<15:14:48.360> simply<15:14:48.660> lease<15:14:48.900> it<15:14:49.020> for 15:14:49.130 --> 15:14:49.140 align:start position:0% does that for us we simply lease it for 15:14:49.140 --> 15:14:50.810 align:start position:0% does that for us we simply lease it for a<15:14:49.256> certain<15:14:49.380> amount<15:14:49.616> of<15:14:49.740> time<15:14:49.860> it's<15:14:50.400> very 15:14:50.810 --> 15:14:50.820 align:start position:0% a certain amount of time it's very 15:14:50.820 --> 15:14:52.310 align:start position:0% a certain amount of time it's very expensive<15:14:51.300> and<15:14:51.480> so<15:14:51.596> a<15:14:51.720> lot<15:14:51.840> of<15:14:51.956> companies 15:14:52.310 --> 15:14:52.320 align:start position:0% expensive and so a lot of companies 15:14:52.320 --> 15:14:53.746 align:start position:0% expensive and so a lot of companies don't<15:14:52.560> use<15:14:52.680> lease<15:14:53.040> lines<15:14:53.276> unless<15:14:53.580> they 15:14:53.746 --> 15:14:53.756 align:start position:0% don't use lease lines unless they 15:14:53.756 --> 15:14:55.550 align:start position:0% don't use lease lines unless they require<15:14:53.936> one<15:14:54.300> what<15:14:54.720> they<15:14:54.840> use<15:14:55.020> instead<15:14:55.320> is<15:14:55.436> a 15:14:55.550 --> 15:14:55.560 align:start position:0% require one what they use instead is a 15:14:55.560 --> 15:14:57.170 align:start position:0% require one what they use instead is a connection<15:14:55.680> to<15:14:55.916> the<15:14:56.096> internet<15:14:56.276> and<15:14:56.880> then<15:14:57.000> they 15:14:57.170 --> 15:14:57.180 align:start position:0% connection to the internet and then they 15:14:57.180 --> 15:15:00.106 align:start position:0% connection to the internet and then they will<15:14:57.360> have<15:14:57.720> uh<15:14:58.616> basically<15:14:58.980> virtual<15:14:59.700> private 15:15:00.106 --> 15:15:00.116 align:start position:0% will have uh basically virtual private 15:15:00.116 --> 15:15:01.730 align:start position:0% will have uh basically virtual private networks<15:15:00.540> and<15:15:00.720> software<15:15:01.140> and<15:15:01.320> other<15:15:01.500> Hardware 15:15:01.730 --> 15:15:01.740 align:start position:0% networks and software and other Hardware 15:15:01.740 --> 15:15:05.870 align:start position:0% networks and software and other Hardware that<15:15:02.276> create<15:15:02.580> a<15:15:03.360> virtual<15:15:03.800> leased<15:15:04.800> line<15:15:04.980> over<15:15:05.400> a 15:15:05.870 --> 15:15:05.880 align:start position:0% that create a virtual leased line over a 15:15:05.880 --> 15:15:08.086 align:start position:0% that create a virtual leased line over a public<15:15:06.060> line<15:15:06.480> we<15:15:07.200> also<15:15:07.436> talked<15:15:07.560> about<15:15:07.616> packet 15:15:08.086 --> 15:15:08.096 align:start position:0% public line we also talked about packet 15:15:08.096 --> 15:15:09.830 align:start position:0% public line we also talked about packet switching<15:15:08.520> which<15:15:09.000> was<15:15:09.116> important<15:15:09.540> different 15:15:09.830 --> 15:15:09.840 align:start position:0% switching which was important different 15:15:09.840 --> 15:15:12.290 align:start position:0% switching which was important different from<15:15:10.340> circuit<15:15:11.340> switching<15:15:11.756> which<15:15:11.936> is<15:15:12.060> sort<15:15:12.240> of 15:15:12.290 --> 15:15:12.300 align:start position:0% from circuit switching which is sort of 15:15:12.300 --> 15:15:14.446 align:start position:0% from circuit switching which is sort of what<15:15:12.480> switches<15:15:12.900> do<15:15:13.140> pocket<15:15:13.860> switching<15:15:14.220> would 15:15:14.446 --> 15:15:14.456 align:start position:0% what switches do pocket switching would 15:15:14.456 --> 15:15:16.190 align:start position:0% what switches do pocket switching would allow<15:15:14.700> me<15:15:14.820> to<15:15:15.060> send 15:15:16.190 --> 15:15:16.200 align:start position:0% allow me to send 15:15:16.200 --> 15:15:19.246 align:start position:0% allow me to send data<15:15:17.160> and<15:15:17.756> if<15:15:17.936> I<15:15:18.116> had<15:15:18.300> many<15:15:18.596> different<15:15:18.840> routes 15:15:19.246 --> 15:15:19.256 align:start position:0% data and if I had many different routes 15:15:19.256 --> 15:15:21.946 align:start position:0% data and if I had many different routes for<15:15:19.436> that<15:15:19.616> data<15:15:19.980> to<15:15:20.160> take<15:15:20.400> it<15:15:21.116> could<15:15:21.300> take<15:15:21.596> any 15:15:21.946 --> 15:15:21.956 align:start position:0% for that data to take it could take any 15:15:21.956 --> 15:15:23.810 align:start position:0% for that data to take it could take any one<15:15:22.200> of<15:15:22.256> those<15:15:22.380> pack<15:15:22.680> those<15:15:23.160> those<15:15:23.160> data 15:15:23.810 --> 15:15:23.820 align:start position:0% one of those pack those those data 15:15:23.820 --> 15:15:26.390 align:start position:0% one of those pack those those data packets<15:15:24.256> run<15:15:25.256> in<15:15:25.560> sort<15:15:25.740> of<15:15:25.860> any<15:15:26.096> different 15:15:26.390 --> 15:15:26.400 align:start position:0% packets run in sort of any different 15:15:26.400 --> 15:15:29.030 align:start position:0% packets run in sort of any different configuration<15:15:27.060> I<15:15:27.360> wanted<15:15:27.540> it<15:15:27.776> to<15:15:27.956> and<15:15:28.800> it 15:15:29.030 --> 15:15:29.040 align:start position:0% configuration I wanted it to and it 15:15:29.040 --> 15:15:30.586 align:start position:0% configuration I wanted it to and it would<15:15:29.160> all<15:15:29.340> arrive<15:15:29.640> at<15:15:29.756> the<15:15:29.880> enemy<15:15:30.180> put<15:15:30.360> back 15:15:30.586 --> 15:15:30.596 align:start position:0% would all arrive at the enemy put back 15:15:30.596 --> 15:15:33.106 align:start position:0% would all arrive at the enemy put back together<15:15:30.840> so<15:15:31.560> the<15:15:31.680> packets<15:15:32.096> all<15:15:32.640> basically 15:15:33.106 --> 15:15:33.116 align:start position:0% together so the packets all basically 15:15:33.116 --> 15:15:35.230 align:start position:0% together so the packets all basically get<15:15:33.240> broken<15:15:33.480> up<15:15:33.720> sent<15:15:34.140> out 15:15:35.230 --> 15:15:35.240 align:start position:0% get broken up sent out 15:15:35.240 --> 15:15:37.550 align:start position:0% get broken up sent out shuffled<15:15:36.240> sent<15:15:36.480> in<15:15:36.840> whatever<15:15:36.956> order<15:15:37.256> they 15:15:37.550 --> 15:15:37.560 align:start position:0% shuffled sent in whatever order they 15:15:37.560 --> 15:15:40.790 align:start position:0% shuffled sent in whatever order they need<15:15:37.740> in<15:15:38.520> the<15:15:38.700> packet<15:15:39.060> each<15:15:39.300> packet<15:15:39.720> has<15:15:40.140> the 15:15:40.790 --> 15:15:40.800 align:start position:0% need in the packet each packet has the 15:15:40.800 --> 15:15:44.266 align:start position:0% need in the packet each packet has the source<15:15:41.220> and<15:15:42.116> the<15:15:42.416> destination<15:15:42.900> and<15:15:43.740> also<15:15:44.040> it 15:15:44.266 --> 15:15:44.276 align:start position:0% source and the destination and also it 15:15:44.276 --> 15:15:48.350 align:start position:0% source and the destination and also it has<15:15:44.520> a<15:15:44.936> number<15:15:45.116> basically 15:15:48.350 --> 15:15:48.360 align:start position:0% 15:15:48.360 --> 15:15:50.690 align:start position:0% so<15:15:48.840> that<15:15:49.080> way<15:15:49.320> at<15:15:49.560> the<15:15:49.740> end<15:15:49.800> it<15:15:50.096> knows<15:15:50.456> how<15:15:50.580> to 15:15:50.690 --> 15:15:50.700 align:start position:0% so that way at the end it knows how to 15:15:50.700 --> 15:15:51.830 align:start position:0% so that way at the end it knows how to put<15:15:50.820> it<15:15:50.936> back<15:15:51.060> together<15:15:51.240> in<15:15:51.540> the<15:15:51.660> correct 15:15:51.830 --> 15:15:51.840 align:start position:0% put it back together in the correct 15:15:51.840 --> 15:15:53.810 align:start position:0% put it back together in the correct order<15:15:52.020> this<15:15:52.740> is<15:15:52.860> somewhat<15:15:53.160> similar<15:15:53.456> to<15:15:53.640> cell 15:15:53.810 --> 15:15:53.820 align:start position:0% order this is somewhat similar to cell 15:15:53.820 --> 15:15:55.426 align:start position:0% order this is somewhat similar to cell relay<15:15:54.180> the<15:15:54.416> difference<15:15:54.596> with<15:15:54.900> cell<15:15:55.080> relay 15:15:55.426 --> 15:15:55.436 align:start position:0% relay the difference with cell relay 15:15:55.436 --> 15:15:57.946 align:start position:0% relay the difference with cell relay which<15:15:55.740> is<15:15:55.860> linked<15:15:56.160> sormal<15:15:56.580> to<15:15:56.756> ATM<15:15:57.116> is<15:15:57.720> that 15:15:57.946 --> 15:15:57.956 align:start position:0% which is linked sormal to ATM is that 15:15:57.956 --> 15:16:00.050 align:start position:0% which is linked sormal to ATM is that all<15:15:58.256> packets 15:16:00.050 --> 15:16:00.060 align:start position:0% all packets 15:16:00.060 --> 15:16:03.530 align:start position:0% all packets are<15:16:00.776> the<15:16:01.080> same 15:16:03.530 --> 15:16:03.540 align:start position:0% 15:16:03.540 --> 15:16:05.030 align:start position:0% size 15:16:05.030 --> 15:16:05.040 align:start position:0% size 15:16:05.040 --> 15:16:06.650 align:start position:0% size we<15:16:05.276> also<15:16:05.520> briefly<15:16:05.936> which<15:16:06.180> we'll<15:16:06.300> talk<15:16:06.540> about 15:16:06.650 --> 15:16:06.660 align:start position:0% we also briefly which we'll talk about 15:16:06.660 --> 15:16:10.246 align:start position:0% we also briefly which we'll talk about more<15:16:07.020> discussed<15:16:07.616> VoIP<15:16:08.096> or<15:16:08.456> voice<15:16:08.820> over<15:16:09.256> IP 15:16:10.246 --> 15:16:10.256 align:start position:0% more discussed VoIP or voice over IP 15:16:10.256 --> 15:16:13.850 align:start position:0% more discussed VoIP or voice over IP which<15:16:10.800> allows<15:16:11.160> us<15:16:11.276> to<15:16:11.520> make 15:16:13.850 --> 15:16:13.860 align:start position:0% 15:16:13.860 --> 15:16:17.390 align:start position:0% phone<15:16:14.456> calls<15:16:15.060> or<15:16:15.840> voice<15:16:16.200> calls 15:16:17.390 --> 15:16:17.400 align:start position:0% phone calls or voice calls 15:16:17.400 --> 15:16:20.690 align:start position:0% phone calls or voice calls over<15:16:18.180> the<15:16:18.900> Internet<15:16:19.020> or<15:16:19.740> using<15:16:20.160> ethernet 15:16:20.690 --> 15:16:20.700 align:start position:0% over the Internet or using ethernet 15:16:20.700 --> 15:16:23.210 align:start position:0% over the Internet or using ethernet technology<15:16:21.180> the<15:16:22.080> protocol<15:16:22.380> that<15:16:22.800> allows<15:16:23.096> us 15:16:23.210 --> 15:16:23.220 align:start position:0% technology the protocol that allows us 15:16:23.220 --> 15:16:31.490 align:start position:0% technology the protocol that allows us to<15:16:23.520> occur<15:16:23.936> is<15:16:24.540> called<15:16:24.840> sip<15:16:25.400> or<15:16:26.400> the<15:16:27.000> session 15:16:31.490 --> 15:16:31.500 align:start position:0% 15:16:31.500 --> 15:16:34.010 align:start position:0% initiation 15:16:34.010 --> 15:16:34.020 align:start position:0% initiation 15:16:34.020 --> 15:16:36.710 align:start position:0% initiation protocol<15:16:34.680> again<15:16:35.340> if<15:16:35.640> you<15:16:35.756> see<15:16:35.936> sip<15:16:36.360> on<15:16:36.540> the 15:16:36.710 --> 15:16:36.720 align:start position:0% protocol again if you see sip on the 15:16:36.720 --> 15:16:38.570 align:start position:0% protocol again if you see sip on the test<15:16:36.840> you<15:16:37.200> can<15:16:37.320> guarantee<15:16:37.800> that<15:16:38.040> it<15:16:38.160> has<15:16:38.340> to<15:16:38.456> do 15:16:38.570 --> 15:16:38.580 align:start position:0% test you can guarantee that it has to do 15:16:38.580 --> 15:16:41.570 align:start position:0% test you can guarantee that it has to do with<15:16:38.756> VoIP<15:16:39.180> or<15:16:39.360> voice<15:16:39.660> over<15:16:39.900> IP<15:16:40.500> now<15:16:41.276> in<15:16:41.456> the 15:16:41.570 --> 15:16:41.580 align:start position:0% with VoIP or voice over IP now in the 15:16:41.580 --> 15:16:43.606 align:start position:0% with VoIP or voice over IP now in the net<15:16:41.756> next<15:16:42.060> lesson<15:16:42.596> we're<15:16:42.956> going<15:16:43.140> to<15:16:43.256> talk<15:16:43.380> more 15:16:43.606 --> 15:16:43.616 align:start position:0% net next lesson we're going to talk more 15:16:43.616 --> 15:16:45.766 align:start position:0% net next lesson we're going to talk more about<15:16:43.860> remote<15:16:44.400> networking<15:16:45.180> obviously 15:16:45.766 --> 15:16:45.776 align:start position:0% about remote networking obviously 15:16:45.776 --> 15:16:47.150 align:start position:0% about remote networking obviously something<15:16:45.956> more<15:16:46.256> and<15:16:46.380> more<15:16:46.560> of<15:16:46.680> us<15:16:46.800> need<15:16:46.980> to<15:16:47.040> do 15:16:47.150 --> 15:16:47.160 align:start position:0% something more and more of us need to do 15:16:47.160 --> 15:16:48.946 align:start position:0% something more and more of us need to do with<15:16:47.340> telecommuting<15:16:48.060> and<15:16:48.480> also<15:16:48.720> something 15:16:48.946 --> 15:16:48.956 align:start position:0% with telecommuting and also something 15:16:48.956 --> 15:16:50.570 align:start position:0% with telecommuting and also something that<15:16:49.256> would<15:16:49.436> allow<15:16:49.740> us<15:16:49.800> to<15:16:49.980> replace<15:16:50.096> for 15:16:50.570 --> 15:16:50.580 align:start position:0% that would allow us to replace for 15:16:50.580 --> 15:16:52.550 align:start position:0% that would allow us to replace for instance<15:16:50.756> a<15:16:51.060> leased<15:16:51.416> line<15:16:51.540> with<15:16:52.080> more<15:16:52.256> of<15:16:52.380> a 15:16:52.550 --> 15:16:52.560 align:start position:0% instance a leased line with more of a 15:16:52.560 --> 15:16:57.130 align:start position:0% instance a leased line with more of a temporary<15:16:52.916> solution 15:16:57.130 --> 15:16:57.140 align:start position:0% 15:16:57.140 --> 15:17:06.426 align:start position:0% [Music] 15:17:06.426 --> 15:17:06.436 align:start position:0% [Music] 15:17:06.436 --> 15:17:14.030 align:start position:0% [Music] thank<15:17:07.436> you 15:17:14.030 --> 15:17:14.040 align:start position:0% 15:17:14.040 --> 15:17:17.150 align:start position:0% welcome<15:17:14.580> to<15:17:14.820> module<15:17:15.240> 9<15:17:15.360> lesson<15:17:16.160> 4.1 15:17:17.150 --> 15:17:17.160 align:start position:0% welcome to module 9 lesson 4.1 15:17:17.160 --> 15:17:19.906 align:start position:0% welcome to module 9 lesson 4.1 practicals<15:17:17.880> and<15:17:18.000> services<15:17:18.436> uh<15:17:19.436> as<15:17:19.680> usual 15:17:19.906 --> 15:17:19.916 align:start position:0% practicals and services uh as usual 15:17:19.916 --> 15:17:21.350 align:start position:0% practicals and services uh as usual covering<15:17:20.340> the<15:17:20.520> things<15:17:20.640> we<15:17:20.880> haven't<15:17:21.060> already 15:17:21.350 --> 15:17:21.360 align:start position:0% covering the things we haven't already 15:17:21.360 --> 15:17:23.810 align:start position:0% covering the things we haven't already gone<15:17:21.720> over 15:17:23.810 --> 15:17:23.820 align:start position:0% gone over 15:17:23.820 --> 15:17:25.906 align:start position:0% gone over it's<15:17:24.180> a<15:17:24.480> wonder<15:17:24.596> wide<15:17:24.956> area<15:17:25.140> network<15:17:25.500> still 15:17:25.906 --> 15:17:25.916 align:start position:0% it's a wonder wide area network still 15:17:25.916 --> 15:17:28.906 align:start position:0% it's a wonder wide area network still we're<15:17:26.640> in<15:17:26.936> brief<15:17:27.360> I.E<15:17:28.080> the<15:17:28.256> stuff<15:17:28.436> I<15:17:28.616> think<15:17:28.740> you 15:17:28.906 --> 15:17:28.916 align:start position:0% we're in brief I.E the stuff I think you 15:17:28.916 --> 15:17:30.470 align:start position:0% we're in brief I.E the stuff I think you need<15:17:29.096> to<15:17:29.276> know<15:17:29.456> because<15:17:29.820> there's<15:17:30.060> entire 15:17:30.470 --> 15:17:30.480 align:start position:0% need to know because there's entire 15:17:30.480 --> 15:17:34.790 align:start position:0% need to know because there's entire books<15:17:30.956> on<15:17:31.080> some<15:17:31.256> of<15:17:31.380> these<15:17:31.616> protocols<15:17:32.400> PPP 15:17:34.790 --> 15:17:34.800 align:start position:0% books on some of these protocols PPP 15:17:34.800 --> 15:17:38.690 align:start position:0% books on some of these protocols PPP PPP<15:17:35.756> over<15:17:36.300> ethernet 15:17:38.690 --> 15:17:38.700 align:start position:0% PPP over ethernet 15:17:38.700 --> 15:17:40.970 align:start position:0% PPP over ethernet Dynamic<15:17:39.416> multi-point<15:17:39.956> VPN<15:17:40.616> which<15:17:40.860> has 15:17:40.970 --> 15:17:40.980 align:start position:0% Dynamic multi-point VPN which has 15:17:40.980 --> 15:17:42.290 align:start position:0% Dynamic multi-point VPN which has actually<15:17:41.160> just<15:17:41.400> been<15:17:41.580> brought<15:17:41.820> into<15:17:42.000> the 15:17:42.290 --> 15:17:42.300 align:start position:0% actually just been brought into the 15:17:42.300 --> 15:17:45.106 align:start position:0% actually just been brought into the Cisco<15:17:42.980> CCNA<15:17:43.980> syllabus 15:17:45.106 --> 15:17:45.116 align:start position:0% Cisco CCNA syllabus 15:17:45.116 --> 15:17:48.290 align:start position:0% Cisco CCNA syllabus sip<15:17:45.956> trunks<15:17:46.380> uh<15:17:47.096> Josh<15:17:47.276> talked<15:17:47.756> about<15:17:47.880> sip 15:17:48.290 --> 15:17:48.300 align:start position:0% sip trunks uh Josh talked about sip 15:17:48.300 --> 15:17:50.150 align:start position:0% sip trunks uh Josh talked about sip trunks<15:17:48.720> earlier 15:17:50.150 --> 15:17:50.160 align:start position:0% trunks earlier 15:17:50.160 --> 15:17:52.970 align:start position:0% trunks earlier uh<15:17:50.640> briefly<15:17:51.060> it<15:17:51.596> he<15:17:52.080> actually<15:17:52.256> wrote<15:17:52.616> it<15:17:52.740> onto 15:17:52.970 --> 15:17:52.980 align:start position:0% uh briefly it he actually wrote it onto 15:17:52.980 --> 15:17:54.170 align:start position:0% uh briefly it he actually wrote it onto one<15:17:53.096> of<15:17:53.220> the<15:17:53.276> slides<15:17:53.580> when<15:17:53.700> he<15:17:53.880> talked<15:17:54.060> about 15:17:54.170 --> 15:17:54.180 align:start position:0% one of the slides when he talked about 15:17:54.180 --> 15:17:56.210 align:start position:0% one of the slides when he talked about voice<15:17:54.480> so<15:17:54.900> I'll<15:17:55.080> just<15:17:55.256> cover<15:17:55.560> an<15:17:55.800> extra<15:17:55.980> little 15:17:56.210 --> 15:17:56.220 align:start position:0% voice so I'll just cover an extra little 15:17:56.220 --> 15:17:57.586 align:start position:0% voice so I'll just cover an extra little bit 15:17:57.586 --> 15:17:57.596 align:start position:0% bit 15:17:57.596 --> 15:18:00.890 align:start position:0% bit PPP<15:17:58.380> very<15:17:58.980> popular<15:17:59.220> over<15:17:59.640> dedicated<15:18:00.360> and 15:18:00.890 --> 15:18:00.900 align:start position:0% PPP very popular over dedicated and 15:18:00.900 --> 15:18:02.926 align:start position:0% PPP very popular over dedicated and circuit<15:18:01.320> switch<15:18:01.500> links<15:18:02.040> for<15:18:02.456> wide<15:18:02.756> area 15:18:02.926 --> 15:18:02.936 align:start position:0% circuit switch links for wide area 15:18:02.936 --> 15:18:05.210 align:start position:0% circuit switch links for wide area connection 15:18:05.210 --> 15:18:05.220 align:start position:0% connection 15:18:05.220 --> 15:18:07.730 align:start position:0% connection now<15:18:05.880> where<15:18:06.240> the<15:18:06.416> typical<15:18:06.720> question<15:18:07.140> you<15:18:07.560> would 15:18:07.730 --> 15:18:07.740 align:start position:0% now where the typical question you would 15:18:07.740 --> 15:18:09.946 align:start position:0% now where the typical question you would get<15:18:07.980> certainly<15:18:08.580> for<15:18:08.700> Cisco<15:18:09.116> is<15:18:09.416> if<15:18:09.840> you're 15:18:09.946 --> 15:18:09.956 align:start position:0% get certainly for Cisco is if you're 15:18:09.956 --> 15:18:12.766 align:start position:0% get certainly for Cisco is if you're collecting<15:18:10.320> a<15:18:10.500> Cisco<15:18:10.860> to<15:18:11.040> a<15:18:11.276> device<15:18:11.540> over<15:18:12.540> a 15:18:12.766 --> 15:18:12.776 align:start position:0% collecting a Cisco to a device over a 15:18:12.776 --> 15:18:14.630 align:start position:0% collecting a Cisco to a device over a wide<15:18:12.900> area<15:18:13.080> network<15:18:13.436> to<15:18:13.740> a<15:18:13.916> non-cisco<15:18:14.456> device 15:18:14.630 --> 15:18:14.640 align:start position:0% wide area network to a non-cisco device 15:18:14.640 --> 15:18:17.150 align:start position:0% wide area network to a non-cisco device what<15:18:15.060> protocol<15:18:15.480> would<15:18:16.020> you<15:18:16.200> use<15:18:16.380> you'd 15:18:17.150 --> 15:18:17.160 align:start position:0% what protocol would you use you'd 15:18:17.160 --> 15:18:19.670 align:start position:0% what protocol would you use you'd probably<15:18:17.340> use<15:18:17.700> PPP 15:18:19.670 --> 15:18:19.680 align:start position:0% probably use PPP 15:18:19.680 --> 15:18:24.230 align:start position:0% probably use PPP because<15:18:20.416> it's<15:18:21.416> a<15:18:21.720> vendor<15:18:22.680> neutral<15:18:23.456> anyone<15:18:24.060> can 15:18:24.230 --> 15:18:24.240 align:start position:0% because it's a vendor neutral anyone can 15:18:24.240 --> 15:18:27.050 align:start position:0% because it's a vendor neutral anyone can use<15:18:24.416> it<15:18:24.596> whereas<15:18:24.956> Cisco<15:18:25.380> has<15:18:26.160> a<15:18:26.456> their<15:18:26.640> own<15:18:26.820> set 15:18:27.050 --> 15:18:27.060 align:start position:0% use it whereas Cisco has a their own set 15:18:27.060 --> 15:18:28.906 align:start position:0% use it whereas Cisco has a their own set of<15:18:27.180> protocols<15:18:27.900> that<15:18:28.140> you<15:18:28.256> can<15:18:28.380> choose<15:18:28.680> from 15:18:28.906 --> 15:18:28.916 align:start position:0% of protocols that you can choose from 15:18:28.916 --> 15:18:32.210 align:start position:0% of protocols that you can choose from for<15:18:29.640> your<15:18:29.820> server-wide<15:18:30.300> area<15:18:30.480> networks<15:18:31.220> also 15:18:32.210 --> 15:18:32.220 align:start position:0% for your server-wide area networks also 15:18:32.220 --> 15:18:34.446 align:start position:0% for your server-wide area networks also works<15:18:32.520> over<15:18:32.640> many<15:18:32.936> different<15:18:33.180> link<15:18:33.480> types<15:18:33.956> so 15:18:34.446 --> 15:18:34.456 align:start position:0% works over many different link types so 15:18:34.456 --> 15:18:39.830 align:start position:0% works over many different link types so synchronous<15:18:35.660> ISDN<15:18:36.680> asynchronous<15:18:37.680> DSL<15:18:39.000> Etc 15:18:39.830 --> 15:18:39.840 align:start position:0% synchronous ISDN asynchronous DSL Etc 15:18:39.840 --> 15:18:42.426 align:start position:0% synchronous ISDN asynchronous DSL Etc two<15:18:40.380> components<15:18:41.040> inside 15:18:42.426 --> 15:18:42.436 align:start position:0% two components inside 15:18:42.436 --> 15:18:45.710 align:start position:0% two components inside PPP<15:18:43.436> you've<15:18:44.220> got<15:18:44.276> your<15:18:44.456> ncps<15:18:45.000> which<15:18:45.360> show<15:18:45.540> your 15:18:45.710 --> 15:18:45.720 align:start position:0% PPP you've got your ncps which show your 15:18:45.720 --> 15:18:47.926 align:start position:0% PPP you've got your ncps which show your network<15:18:45.900> control<15:18:46.256> protocols<15:18:47.220> these 15:18:47.926 --> 15:18:47.936 align:start position:0% network control protocols these 15:18:47.936 --> 15:18:50.810 align:start position:0% network control protocols these interface<15:18:48.360> with<15:18:48.596> the<15:18:48.776> TCP<15:18:49.380> or<15:18:49.980> network<15:18:50.276> layer 15:18:50.810 --> 15:18:50.820 align:start position:0% interface with the TCP or network layer 15:18:50.820 --> 15:18:53.330 align:start position:0% interface with the TCP or network layer talking<15:18:51.596> about<15:18:51.776> OSI<15:18:52.380> and<15:18:53.040> then<15:18:53.160> you've<15:18:53.276> got 15:18:53.330 --> 15:18:53.340 align:start position:0% talking about OSI and then you've got 15:18:53.340 --> 15:18:55.906 align:start position:0% talking about OSI and then you've got link<15:18:53.520> control<15:18:53.756> protocols<15:18:54.540> this<15:18:55.020> manages<15:18:55.436> the 15:18:55.906 --> 15:18:55.916 align:start position:0% link control protocols this manages the 15:18:55.916 --> 15:18:58.246 align:start position:0% link control protocols this manages the data<15:18:56.276> link<15:18:56.400> sessions<15:18:57.000> and<15:18:57.540> connections 15:18:58.246 --> 15:18:58.256 align:start position:0% data link sessions and connections 15:18:58.256 --> 15:19:03.106 align:start position:0% data link sessions and connections that'd<15:18:59.160> be<15:18:59.276> a<15:18:59.456> typical<15:18:59.700> exam<15:19:00.300> type<15:19:00.660> question 15:19:03.106 --> 15:19:03.116 align:start position:0% 15:19:03.116 --> 15:19:05.510 align:start position:0% the<15:19:03.480> other<15:19:03.540> thing<15:19:03.720> about<15:19:03.900> PPP<15:19:04.500> is<15:19:04.740> it<15:19:04.916> offers 15:19:05.510 --> 15:19:05.520 align:start position:0% the other thing about PPP is it offers 15:19:05.520 --> 15:19:07.370 align:start position:0% the other thing about PPP is it offers authentication<15:19:06.180> built<15:19:06.720> in<15:19:06.776> which<15:19:07.020> is<15:19:07.140> very 15:19:07.370 --> 15:19:07.380 align:start position:0% authentication built in which is very 15:19:07.380 --> 15:19:09.050 align:start position:0% authentication built in which is very useful 15:19:09.050 --> 15:19:09.060 align:start position:0% useful 15:19:09.060 --> 15:19:11.990 align:start position:0% useful now<15:19:09.596> you've<15:19:09.776> got<15:19:09.900> two<15:19:10.140> types<15:19:10.616> pap 15:19:11.990 --> 15:19:12.000 align:start position:0% now you've got two types pap 15:19:12.000 --> 15:19:14.210 align:start position:0% now you've got two types pap and<15:19:12.776> chap 15:19:14.210 --> 15:19:14.220 align:start position:0% and chap 15:19:14.220 --> 15:19:17.210 align:start position:0% and chap uh<15:19:15.000> unfortunately<15:19:15.480> if<15:19:16.080> we<15:19:16.320> go<15:19:16.500> over<15:19:16.680> to 15:19:17.210 --> 15:19:17.220 align:start position:0% uh unfortunately if we go over to 15:19:17.220 --> 15:19:19.550 align:start position:0% uh unfortunately if we go over to password<15:19:17.880> authenticate<15:19:18.660> Authentication 15:19:19.550 --> 15:19:19.560 align:start position:0% password authenticate Authentication 15:19:19.560 --> 15:19:20.830 align:start position:0% password authenticate Authentication Protocol 15:19:20.830 --> 15:19:20.840 align:start position:0% Protocol 15:19:20.840 --> 15:19:24.290 align:start position:0% Protocol your<15:19:21.840> password<15:19:22.080> if<15:19:22.500> you<15:19:22.680> sniffed<15:19:23.220> the<15:19:23.820> packet 15:19:24.290 --> 15:19:24.300 align:start position:0% your password if you sniffed the packet 15:19:24.300 --> 15:19:26.330 align:start position:0% your password if you sniffed the packet been<15:19:24.596> sent<15:19:24.840> over<15:19:25.200> the<15:19:25.500> line 15:19:26.330 --> 15:19:26.340 align:start position:0% been sent over the line 15:19:26.340 --> 15:19:34.370 align:start position:0% been sent over the line uh<15:19:26.820> the<15:19:27.000> fields<15:19:27.360> you<15:19:27.840> would<15:19:28.020> see 15:19:34.370 --> 15:19:34.380 align:start position:0% 15:19:34.380 --> 15:19:37.790 align:start position:0% password<15:19:34.916> it<15:19:35.456> doesn't<15:19:35.756> encrypt<15:19:36.360> the<15:19:36.596> password 15:19:37.790 --> 15:19:37.800 align:start position:0% password it doesn't encrypt the password 15:19:37.800 --> 15:19:40.246 align:start position:0% password it doesn't encrypt the password chap 15:19:40.246 --> 15:19:40.256 align:start position:0% chap 15:19:40.256 --> 15:19:43.790 align:start position:0% chap actually<15:19:40.916> sends<15:19:41.640> a<15:19:42.060> hashed<15:19:42.540> value 15:19:43.790 --> 15:19:43.800 align:start position:0% actually sends a hashed value 15:19:43.800 --> 15:19:45.130 align:start position:0% actually sends a hashed value of 15:19:45.130 --> 15:19:45.140 align:start position:0% of 15:19:45.140 --> 15:19:50.390 align:start position:0% of characters<15:19:46.340> whatever<15:19:47.340> they<15:19:47.756> may<15:19:47.936> be 15:19:50.390 --> 15:19:50.400 align:start position:0% 15:19:50.400 --> 15:19:52.130 align:start position:0% so<15:19:50.936> you<15:19:51.240> don't<15:19:51.300> actually<15:19:51.480> see<15:19:51.776> the<15:19:52.020> password 15:19:52.130 --> 15:19:52.140 align:start position:0% so you don't actually see the password 15:19:52.140 --> 15:19:53.990 align:start position:0% so you don't actually see the password so<15:19:52.560> this<15:19:52.860> is<15:19:52.980> the<15:19:53.220> one<15:19:53.340> you're<15:19:53.640> going<15:19:53.756> to<15:19:53.880> want 15:19:53.990 --> 15:19:54.000 align:start position:0% so this is the one you're going to want 15:19:54.000 --> 15:19:55.790 align:start position:0% so this is the one you're going to want to<15:19:54.180> use<15:19:54.360> no<15:19:54.720> one<15:19:54.900> really<15:19:55.020> is<15:19:55.200> going<15:19:55.380> to<15:19:55.436> use<15:19:55.560> Pap 15:19:55.790 --> 15:19:55.800 align:start position:0% to use no one really is going to use Pap 15:19:55.800 --> 15:19:58.370 align:start position:0% to use no one really is going to use Pap anymore<15:19:56.096> unless<15:19:56.580> it's<15:19:57.116> um<15:19:57.116> you<15:19:57.720> can<15:19:57.840> configure 15:19:58.370 --> 15:19:58.380 align:start position:0% anymore unless it's um you can configure 15:19:58.380 --> 15:20:02.086 align:start position:0% anymore unless it's um you can configure it<15:19:58.500> if<15:19:59.040> for<15:19:59.220> any<15:19:59.340> reason<15:19:59.580> chap<15:20:00.060> goes<15:20:00.900> down<15:20:01.200> you 15:20:02.086 --> 15:20:02.096 align:start position:0% it if for any reason chap goes down you 15:20:02.096 --> 15:20:04.670 align:start position:0% it if for any reason chap goes down you can<15:20:02.160> configure<15:20:02.700> it's<15:20:03.240> a<15:20:03.540> it's<15:20:03.900> called<15:20:04.140> a<15:20:04.436> full 15:20:04.670 --> 15:20:04.680 align:start position:0% can configure it's a it's called a full 15:20:04.680 --> 15:20:08.030 align:start position:0% can configure it's a it's called a full back<15:20:04.860> PPP<15:20:05.520> fullback<15:20:06.060> but<15:20:06.900> really<15:20:07.140> you'd 15:20:08.030 --> 15:20:08.040 align:start position:0% back PPP fullback but really you'd 15:20:08.040 --> 15:20:10.246 align:start position:0% back PPP fullback but really you'd probably<15:20:08.096> rather<15:20:08.456> just<15:20:08.700> have<15:20:08.936> your<15:20:09.360> PPP<15:20:10.020> line 15:20:10.246 --> 15:20:10.256 align:start position:0% probably rather just have your PPP line 15:20:10.256 --> 15:20:12.470 align:start position:0% probably rather just have your PPP line go<15:20:10.560> down<15:20:10.740> and<15:20:10.980> you<15:20:11.160> troubleshoot<15:20:11.756> it 15:20:12.470 --> 15:20:12.480 align:start position:0% go down and you troubleshoot it 15:20:12.480 --> 15:20:14.210 align:start position:0% go down and you troubleshoot it but<15:20:12.956> search<15:20:13.200> up<15:20:13.436> is<15:20:13.616> what<15:20:13.740> you<15:20:13.860> will<15:20:13.980> want<15:20:14.096> to 15:20:14.210 --> 15:20:14.220 align:start position:0% but search up is what you will want to 15:20:14.220 --> 15:20:16.190 align:start position:0% but search up is what you will want to use<15:20:14.340> because<15:20:14.580> it<15:20:14.820> offers<15:20:15.180> the<15:20:15.480> encryption 15:20:16.190 --> 15:20:16.200 align:start position:0% use because it offers the encryption 15:20:16.200 --> 15:20:18.406 align:start position:0% use because it offers the encryption there's<15:20:16.980> a<15:20:17.160> three-way<15:20:17.520> handshake<15:20:18.000> this<15:20:18.300> is 15:20:18.406 --> 15:20:18.416 align:start position:0% there's a three-way handshake this is 15:20:18.416 --> 15:20:20.926 align:start position:0% there's a three-way handshake this is another<15:20:18.540> typical<15:20:18.956> exam<15:20:19.380> question 15:20:20.926 --> 15:20:20.936 align:start position:0% another typical exam question 15:20:20.936 --> 15:20:22.130 align:start position:0% another typical exam question um<15:20:21.000> and<15:20:21.300> you<15:20:21.360> can<15:20:21.480> see<15:20:21.596> it<15:20:21.720> in<15:20:21.840> the<15:20:21.900> diagram 15:20:22.130 --> 15:20:22.140 align:start position:0% um and you can see it in the diagram 15:20:22.140 --> 15:20:25.010 align:start position:0% um and you can see it in the diagram here<15:20:22.560> there's<15:20:23.160> a<15:20:23.400> challenge<15:20:23.820> a<15:20:24.240> response<15:20:24.776> and 15:20:25.010 --> 15:20:25.020 align:start position:0% here there's a challenge a response and 15:20:25.020 --> 15:20:26.810 align:start position:0% here there's a challenge a response and then<15:20:25.200> it's<15:20:25.436> accepted<15:20:25.860> or<15:20:26.040> rejected<15:20:26.456> if<15:20:26.640> it's 15:20:26.810 --> 15:20:26.820 align:start position:0% then it's accepted or rejected if it's 15:20:26.820 --> 15:20:29.746 align:start position:0% then it's accepted or rejected if it's accepted<15:20:27.180> then<15:20:27.900> the<15:20:28.140> line<15:20:28.320> comes<15:20:28.740> up<15:20:28.860> and<15:20:29.640> you 15:20:29.746 --> 15:20:29.756 align:start position:0% accepted then the line comes up and you 15:20:29.756 --> 15:20:33.170 align:start position:0% accepted then the line comes up and you can<15:20:29.880> pass<15:20:30.060> then<15:20:30.360> your<15:20:30.660> data<15:20:31.140> if<15:20:32.520> um<15:20:32.580> it's 15:20:33.170 --> 15:20:33.180 align:start position:0% can pass then your data if um it's 15:20:33.180 --> 15:20:35.630 align:start position:0% can pass then your data if um it's rejected<15:20:33.660> then<15:20:34.200> obviously<15:20:34.500> the<15:20:34.740> PPP<15:20:35.220> session 15:20:35.630 --> 15:20:35.640 align:start position:0% rejected then obviously the PPP session 15:20:35.640 --> 15:20:38.946 align:start position:0% rejected then obviously the PPP session uh<15:20:36.480> won't<15:20:36.720> come<15:20:36.956> up<15:20:37.140> and<15:20:37.380> I<15:20:37.740> spent<15:20:38.040> some<15:20:38.520> time 15:20:38.946 --> 15:20:38.956 align:start position:0% uh won't come up and I spent some time 15:20:38.956 --> 15:20:41.030 align:start position:0% uh won't come up and I spent some time debugging<15:20:39.956> this<15:20:40.080> when<15:20:40.200> I<15:20:40.320> work<15:20:40.436> for<15:20:40.680> Cisco 15:20:41.030 --> 15:20:41.040 align:start position:0% debugging this when I work for Cisco 15:20:41.040 --> 15:20:42.586 align:start position:0% debugging this when I work for Cisco Systems 15:20:42.586 --> 15:20:42.596 align:start position:0% Systems 15:20:42.596 --> 15:20:44.926 align:start position:0% Systems a<15:20:43.140> continual<15:20:43.680> authentication<15:20:44.400> so<15:20:44.640> it<15:20:44.820> doesn't 15:20:44.926 --> 15:20:44.936 align:start position:0% a continual authentication so it doesn't 15:20:44.936 --> 15:20:47.390 align:start position:0% a continual authentication so it doesn't just<15:20:45.116> do<15:20:45.300> it<15:20:45.480> once<15:20:45.956> I'm<15:20:46.860> not<15:20:46.980> sure<15:20:47.096> you'd<15:20:47.276> have 15:20:47.390 --> 15:20:47.400 align:start position:0% just do it once I'm not sure you'd have 15:20:47.400 --> 15:20:49.426 align:start position:0% just do it once I'm not sure you'd have to<15:20:47.520> read<15:20:47.580> the<15:20:47.820> RFC<15:20:48.300> and<15:20:48.596> see<15:20:48.840> how<15:20:49.140> it's<15:20:49.256> been 15:20:49.426 --> 15:20:49.436 align:start position:0% to read the RFC and see how it's been 15:20:49.436 --> 15:20:50.746 align:start position:0% to read the RFC and see how it's been implemented<15:20:49.916> but<15:20:50.160> there's<15:20:50.400> regular 15:20:50.746 --> 15:20:50.756 align:start position:0% implemented but there's regular 15:20:50.756 --> 15:20:53.106 align:start position:0% implemented but there's regular challenges<15:20:51.240> take<15:20:51.540> place<15:20:51.776> during<15:20:52.616> the<15:20:52.860> session 15:20:53.106 --> 15:20:53.116 align:start position:0% challenges take place during the session 15:20:53.116 --> 15:20:56.086 align:start position:0% challenges take place during the session uh<15:20:54.116> usually<15:20:54.480> there's<15:20:54.900> a<15:20:55.080> a<15:20:55.320> host<15:20:55.680> name<15:20:55.860> and 15:20:56.086 --> 15:20:56.096 align:start position:0% uh usually there's a a host name and 15:20:56.096 --> 15:20:58.246 align:start position:0% uh usually there's a a host name and password<15:20:56.276> for<15:20:56.820> example<15:20:57.060> the<15:20:57.660> host<15:20:57.840> name<15:20:58.080> of 15:20:58.246 --> 15:20:58.256 align:start position:0% password for example the host name of 15:20:58.256 --> 15:21:00.230 align:start position:0% password for example the host name of this<15:20:58.436> router<15:20:58.800> is<15:20:58.980> router<15:20:59.400> B 15:21:00.230 --> 15:21:00.240 align:start position:0% this router is router B 15:21:00.240 --> 15:21:02.390 align:start position:0% this router is router B and<15:21:00.776> you<15:21:00.956> would<15:21:01.080> configure<15:21:01.616> on<15:21:02.040> this<15:21:02.220> side 15:21:02.390 --> 15:21:02.400 align:start position:0% and you would configure on this side 15:21:02.400 --> 15:21:04.730 align:start position:0% and you would configure on this side here<15:21:02.700> you<15:21:03.060> would<15:21:03.180> say<15:21:03.360> the<15:21:03.660> host<15:21:03.956> the<15:21:04.320> username 15:21:04.730 --> 15:21:04.740 align:start position:0% here you would say the host the username 15:21:04.740 --> 15:21:07.490 align:start position:0% here you would say the host the username that's<15:21:04.916> permitted<15:21:05.520> is<15:21:06.240> router<15:21:06.720> a<15:21:06.956> and<15:21:07.320> I've 15:21:07.490 --> 15:21:07.500 align:start position:0% that's permitted is router a and I've 15:21:07.500 --> 15:21:09.290 align:start position:0% that's permitted is router a and I've just<15:21:07.680> used<15:21:07.860> a<15:21:08.040> simple<15:21:08.160> password<15:21:08.456> so<15:21:09.116> what 15:21:09.290 --> 15:21:09.300 align:start position:0% just used a simple password so what 15:21:09.300 --> 15:21:11.446 align:start position:0% just used a simple password so what happens<15:21:09.480> is<15:21:09.776> this<15:21:10.080> router's<15:21:10.616> host<15:21:10.800> name<15:21:11.040> acts 15:21:11.446 --> 15:21:11.456 align:start position:0% happens is this router's host name acts 15:21:11.456 --> 15:21:13.190 align:start position:0% happens is this router's host name acts as<15:21:11.520> the<15:21:11.700> Authentication 15:21:13.190 --> 15:21:13.200 align:start position:0% as the Authentication 15:21:13.200 --> 15:21:18.290 align:start position:0% as the Authentication a<15:21:13.800> hostname<15:21:14.456> it<15:21:15.000> calls<15:21:15.480> using<15:21:16.436> its<15:21:17.096> um<15:21:17.300> host 15:21:18.290 --> 15:21:18.300 align:start position:0% a hostname it calls using its um host 15:21:18.300 --> 15:21:21.890 align:start position:0% a hostname it calls using its um host name<15:21:18.596> here<15:21:19.560> and<15:21:20.276> its<15:21:20.640> password<15:21:20.756> and<15:21:21.540> in<15:21:21.720> the 15:21:21.890 --> 15:21:21.900 align:start position:0% name here and its password and in the 15:21:21.900 --> 15:21:24.050 align:start position:0% name here and its password and in the database<15:21:22.320> over<15:21:22.740> here<15:21:23.040> you've<15:21:23.580> configured 15:21:24.050 --> 15:21:24.060 align:start position:0% database over here you've configured 15:21:24.060 --> 15:21:26.150 align:start position:0% database over here you've configured that<15:21:24.596> as<15:21:24.776> the<15:21:25.020> parameters<15:21:25.560> that's<15:21:25.800> going<15:21:26.040> to 15:21:26.150 --> 15:21:26.160 align:start position:0% that as the parameters that's going to 15:21:26.160 --> 15:21:27.890 align:start position:0% that as the parameters that's going to be<15:21:26.220> permitted 15:21:27.890 --> 15:21:27.900 align:start position:0% be permitted 15:21:27.900 --> 15:21:29.690 align:start position:0% be permitted you<15:21:28.320> can<15:21:28.380> do<15:21:28.500> it<15:21:28.616> in<15:21:28.740> a<15:21:28.916> lot<15:21:29.040> more<15:21:29.220> complicated 15:21:29.690 --> 15:21:29.700 align:start position:0% you can do it in a lot more complicated 15:21:29.700 --> 15:21:30.946 align:start position:0% you can do it in a lot more complicated ways 15:21:30.946 --> 15:21:30.956 align:start position:0% ways 15:21:30.956 --> 15:21:34.190 align:start position:0% ways the<15:21:31.700> commands<15:21:32.700> on<15:21:32.820> a<15:21:33.000> Cisco<15:21:33.240> router<15:21:33.660> are<15:21:33.776> PPP 15:21:34.190 --> 15:21:34.200 align:start position:0% the commands on a Cisco router are PPP 15:21:34.200 --> 15:21:37.130 align:start position:0% the commands on a Cisco router are PPP authentication<15:21:34.860> chap<15:21:35.480> uh<15:21:36.480> or<15:21:36.660> if<15:21:36.840> you<15:21:36.900> want<15:21:37.020> to 15:21:37.130 --> 15:21:37.140 align:start position:0% authentication chap uh or if you want to 15:21:37.140 --> 15:21:39.170 align:start position:0% authentication chap uh or if you want to use<15:21:37.800> um<15:21:37.916> and 15:21:39.170 --> 15:21:39.180 align:start position:0% use um and 15:21:39.180 --> 15:21:42.106 align:start position:0% use um and um<15:21:39.240> your<15:21:39.480> clear<15:21:39.720> text<15:21:39.900> is<15:21:40.200> pap 15:21:42.106 --> 15:21:42.116 align:start position:0% um your clear text is pap 15:21:42.116 --> 15:21:45.710 align:start position:0% um your clear text is pap moving<15:21:42.776> on<15:21:42.900> to<15:21:43.340> pppoe<15:21:44.340> it<15:21:45.300> allows 15:21:45.710 --> 15:21:45.720 align:start position:0% moving on to pppoe it allows 15:21:45.720 --> 15:21:49.010 align:start position:0% moving on to pppoe it allows encapsulating<15:21:46.320> PPP<15:21:47.040> inside<15:21:48.000> ethernet<15:21:48.540> frames 15:21:49.010 --> 15:21:49.020 align:start position:0% encapsulating PPP inside ethernet frames 15:21:49.020 --> 15:21:50.870 align:start position:0% encapsulating PPP inside ethernet frames no<15:21:49.320> surprise<15:21:49.616> really<15:21:49.860> because<15:21:50.096> the<15:21:50.340> clues<15:21:50.700> in 15:21:50.870 --> 15:21:50.880 align:start position:0% no surprise really because the clues in 15:21:50.880 --> 15:21:53.570 align:start position:0% no surprise really because the clues in the<15:21:51.000> name<15:21:51.240> there<15:21:51.900> often<15:21:52.560> used<15:21:52.680> with<15:21:52.916> your<15:21:53.096> DSL 15:21:53.570 --> 15:21:53.580 align:start position:0% the name there often used with your DSL 15:21:53.580 --> 15:21:55.550 align:start position:0% the name there often used with your DSL connections<15:21:54.300> and<15:21:54.480> it<15:21:54.660> tunnels<15:21:55.020> to<15:21:55.200> the<15:21:55.380> your 15:21:55.550 --> 15:21:55.560 align:start position:0% connections and it tunnels to the your 15:21:55.560 --> 15:21:58.246 align:start position:0% connections and it tunnels to the your internet<15:21:55.740> service<15:21:56.300> provider<15:21:57.300> I'm<15:21:58.140> just 15:21:58.246 --> 15:21:58.256 align:start position:0% internet service provider I'm just 15:21:58.256 --> 15:21:59.746 align:start position:0% internet service provider I'm just thinking<15:21:58.560> of<15:21:58.740> questions<15:21:58.916> of<15:21:59.400> the<15:21:59.580> last 15:21:59.746 --> 15:21:59.756 align:start position:0% thinking of questions of the last 15:21:59.756 --> 15:22:01.310 align:start position:0% thinking of questions of the last because<15:22:00.180> you're<15:22:00.720> not<15:22:00.840> going<15:22:00.956> to<15:22:01.080> have<15:22:01.200> to 15:22:01.310 --> 15:22:01.320 align:start position:0% because you're not going to have to 15:22:01.320 --> 15:22:04.010 align:start position:0% because you're not going to have to configure<15:22:01.740> this<15:22:02.060> so<15:22:03.060> they<15:22:03.300> may<15:22:03.540> ask<15:22:03.840> a 15:22:04.010 --> 15:22:04.020 align:start position:0% configure this so they may ask a 15:22:04.020 --> 15:22:06.530 align:start position:0% configure this so they may ask a question<15:22:04.200> what<15:22:04.560> are<15:22:04.740> the<15:22:05.000> pppoe<15:22:06.000> stage<15:22:06.360> is 15:22:06.530 --> 15:22:06.540 align:start position:0% question what are the pppoe stage is 15:22:06.540 --> 15:22:09.586 align:start position:0% question what are the pppoe stage is there's<15:22:07.080> a<15:22:07.380> discovery<15:22:08.060> which<15:22:09.060> is<15:22:09.180> obviously 15:22:09.586 --> 15:22:09.596 align:start position:0% there's a discovery which is obviously 15:22:09.596 --> 15:22:11.086 align:start position:0% there's a discovery which is obviously the<15:22:10.140> um<15:22:10.140> building<15:22:10.436> up<15:22:10.740> the<15:22:10.860> connection 15:22:11.086 --> 15:22:11.096 align:start position:0% the um building up the connection 15:22:11.096 --> 15:22:13.426 align:start position:0% the um building up the connection between<15:22:11.520> the<15:22:11.820> two<15:22:12.000> devices<15:22:12.360> and<15:22:13.140> then<15:22:13.200> the 15:22:13.426 --> 15:22:13.436 align:start position:0% between the two devices and then the 15:22:13.436 --> 15:22:15.406 align:start position:0% between the two devices and then the actual<15:22:13.680> session<15:22:13.980> where<15:22:14.700> the<15:22:14.880> data<15:22:15.180> is<15:22:15.300> going 15:22:15.406 --> 15:22:15.416 align:start position:0% actual session where the data is going 15:22:15.416 --> 15:22:17.150 align:start position:0% actual session where the data is going to<15:22:15.540> be<15:22:15.596> sent<15:22:15.776> across<15:22:16.256> the<15:22:16.380> line 15:22:17.150 --> 15:22:17.160 align:start position:0% to be sent across the line 15:22:17.160 --> 15:22:19.310 align:start position:0% to be sent across the line this<15:22:17.700> is<15:22:17.880> the<15:22:18.000> same<15:22:18.116> with<15:22:18.300> most<15:22:18.540> protocols<15:22:19.200> as 15:22:19.310 --> 15:22:19.320 align:start position:0% this is the same with most protocols as 15:22:19.320 --> 15:22:21.106 align:start position:0% this is the same with most protocols as you<15:22:19.500> know 15:22:21.106 --> 15:22:21.116 align:start position:0% you know 15:22:21.116 --> 15:22:25.850 align:start position:0% you know moving<15:22:21.900> on<15:22:22.080> to<15:22:22.380> Dynamic<15:22:23.160> multi-point<15:22:23.936> vpm 15:22:25.850 --> 15:22:25.860 align:start position:0% moving on to Dynamic multi-point vpm 15:22:25.860 --> 15:22:28.310 align:start position:0% moving on to Dynamic multi-point vpm this<15:22:26.580> allows<15:22:26.936> your<15:22:27.060> remote<15:22:27.300> VPN<15:22:27.776> connections 15:22:28.310 --> 15:22:28.320 align:start position:0% this allows your remote VPN connections 15:22:28.320 --> 15:22:31.970 align:start position:0% this allows your remote VPN connections to<15:22:28.740> bypass<15:22:29.580> your<15:22:29.936> your<15:22:30.300> headquarters<15:22:30.956> VPN<15:22:31.500> so 15:22:31.970 --> 15:22:31.980 align:start position:0% to bypass your your headquarters VPN so 15:22:31.980 --> 15:22:33.730 align:start position:0% to bypass your your headquarters VPN so in<15:22:32.160> your<15:22:32.340> traditional 15:22:33.730 --> 15:22:33.740 align:start position:0% in your traditional 15:22:33.740 --> 15:22:38.446 align:start position:0% in your traditional VPN<15:22:35.240> service<15:22:36.240> your<15:22:37.200> spoke<15:22:37.500> router<15:22:37.916> over<15:22:38.096> here 15:22:38.446 --> 15:22:38.456 align:start position:0% VPN service your spoke router over here 15:22:38.456 --> 15:22:40.070 align:start position:0% VPN service your spoke router over here say 15:22:40.070 --> 15:22:40.080 align:start position:0% say 15:22:40.080 --> 15:22:43.246 align:start position:0% say um<15:22:40.140> say<15:22:40.380> it's<15:22:40.500> in<15:22:40.680> Las<15:22:40.916> Vegas<15:22:41.360> this<15:22:42.360> is<15:22:42.540> in<15:22:42.840> LA 15:22:43.246 --> 15:22:43.256 align:start position:0% um say it's in Las Vegas this is in LA 15:22:43.256 --> 15:22:45.106 align:start position:0% um say it's in Las Vegas this is in LA and 15:22:45.106 --> 15:22:45.116 align:start position:0% and 15:22:45.116 --> 15:22:47.210 align:start position:0% and um this<15:22:45.596> is<15:22:45.720> in 15:22:47.210 --> 15:22:47.220 align:start position:0% um this is in 15:22:47.220 --> 15:22:51.106 align:start position:0% um this is in where<15:22:47.820> can<15:22:48.000> we<15:22:48.180> have<15:22:48.240> this<15:22:48.416> Atlanta 15:22:51.106 --> 15:22:51.116 align:start position:0% 15:22:51.116 --> 15:22:55.190 align:start position:0% a<15:22:51.840> bit<15:22:52.020> of<15:22:52.256> a<15:22:52.500> pain<15:22:53.000> your<15:22:54.000> branch<15:22:54.720> office<15:22:54.900> would 15:22:55.190 --> 15:22:55.200 align:start position:0% a bit of a pain your branch office would 15:22:55.200 --> 15:22:58.510 align:start position:0% a bit of a pain your branch office would have<15:22:55.380> to<15:22:55.500> communicate<15:22:56.040> to<15:22:56.456> your<15:22:57.320> headquarters 15:22:58.510 --> 15:22:58.520 align:start position:0% have to communicate to your headquarters 15:22:58.520 --> 15:23:01.730 align:start position:0% have to communicate to your headquarters in<15:22:59.520> order<15:22:59.640> for<15:23:00.000> the<15:23:00.240> the<15:23:00.900> tunnel<15:23:01.380> to<15:23:01.560> actually 15:23:01.730 --> 15:23:01.740 align:start position:0% in order for the the tunnel to actually 15:23:01.740 --> 15:23:03.946 align:start position:0% in order for the the tunnel to actually take<15:23:02.096> place<15:23:02.340> but<15:23:02.580> it'll<15:23:02.756> be<15:23:02.880> routed<15:23:03.300> from<15:23:03.776> here 15:23:03.946 --> 15:23:03.956 align:start position:0% take place but it'll be routed from here 15:23:03.956 --> 15:23:06.170 align:start position:0% take place but it'll be routed from here to<15:23:04.140> here<15:23:04.380> and<15:23:04.980> obviously<15:23:05.456> if<15:23:06.060> there's 15:23:06.170 --> 15:23:06.180 align:start position:0% to here and obviously if there's 15:23:06.180 --> 15:23:08.150 align:start position:0% to here and obviously if there's problems<15:23:06.596> in<15:23:06.840> your<15:23:07.080> headquarters<15:23:07.740> office<15:23:07.916> for 15:23:08.150 --> 15:23:08.160 align:start position:0% problems in your headquarters office for 15:23:08.160 --> 15:23:10.070 align:start position:0% problems in your headquarters office for whatever<15:23:08.340> reason<15:23:08.640> or<15:23:09.000> the<15:23:09.116> line<15:23:09.360> is<15:23:09.540> congested 15:23:10.070 --> 15:23:10.080 align:start position:0% whatever reason or the line is congested 15:23:10.080 --> 15:23:12.890 align:start position:0% whatever reason or the line is congested your<15:23:11.040> connection<15:23:11.400> won't<15:23:11.756> take<15:23:11.936> place<15:23:12.180> so<15:23:12.776> the 15:23:12.890 --> 15:23:12.900 align:start position:0% your connection won't take place so the 15:23:12.900 --> 15:23:13.906 align:start position:0% your connection won't take place so the point<15:23:13.140> of 15:23:13.906 --> 15:23:13.916 align:start position:0% point of 15:23:13.916 --> 15:23:17.446 align:start position:0% point of um Dynamic<15:23:14.580> multiple<15:23:14.936> in<15:23:15.060> VPN<15:23:15.480> is<15:23:15.720> your 15:23:17.446 --> 15:23:17.456 align:start position:0% um Dynamic multiple in VPN is your 15:23:17.456 --> 15:23:19.906 align:start position:0% um Dynamic multiple in VPN is your Branch<15:23:18.180> offices<15:23:18.540> your<15:23:18.900> spoke<15:23:19.140> routers<15:23:19.616> can 15:23:19.906 --> 15:23:19.916 align:start position:0% Branch offices your spoke routers can 15:23:19.916 --> 15:23:22.010 align:start position:0% Branch offices your spoke routers can directly<15:23:20.456> make<15:23:20.640> a<15:23:20.880> connection<15:23:21.060> and<15:23:21.900> it 15:23:22.010 --> 15:23:22.020 align:start position:0% directly make a connection and it 15:23:22.020 --> 15:23:26.390 align:start position:0% directly make a connection and it bypasses<15:23:22.560> your<15:23:23.180> vpn's<15:23:24.180> router 15:23:26.390 --> 15:23:26.400 align:start position:0% bypasses your vpn's router 15:23:26.400 --> 15:23:28.370 align:start position:0% bypasses your vpn's router you<15:23:26.756> do<15:23:26.880> require<15:23:27.060> a<15:23:27.360> hub<15:23:27.480> and<15:23:27.660> spoke<15:23:27.900> topology 15:23:28.370 --> 15:23:28.380 align:start position:0% you do require a hub and spoke topology 15:23:28.380 --> 15:23:31.190 align:start position:0% you do require a hub and spoke topology which<15:23:28.800> we<15:23:28.916> spoke<15:23:29.220> about<15:23:29.400> earlier<15:23:30.000> in<15:23:30.900> our 15:23:31.190 --> 15:23:31.200 align:start position:0% which we spoke about earlier in our 15:23:31.200 --> 15:23:32.926 align:start position:0% which we spoke about earlier in our topology 15:23:32.926 --> 15:23:32.936 align:start position:0% topology 15:23:32.936 --> 15:23:35.570 align:start position:0% topology topology<15:23:33.416> sessions 15:23:35.570 --> 15:23:35.580 align:start position:0% topology sessions 15:23:35.580 --> 15:23:37.426 align:start position:0% topology sessions um<15:23:35.700> oh<15:23:36.116> that<15:23:36.720> shouldn't<15:23:36.900> be<15:23:37.020> in<15:23:37.140> there<15:23:37.256> sorry 15:23:37.426 --> 15:23:37.436 align:start position:0% um oh that shouldn't be in there sorry 15:23:37.436 --> 15:23:38.926 align:start position:0% um oh that shouldn't be in there sorry about<15:23:37.680> that 15:23:38.926 --> 15:23:38.936 align:start position:0% about that 15:23:38.936 --> 15:23:43.370 align:start position:0% about that left<15:23:39.360> that<15:23:39.596> in<15:23:39.720> from<15:23:39.900> my<15:23:40.140> last<15:23:40.740> slide 15:23:43.370 --> 15:23:43.380 align:start position:0% 15:23:43.380 --> 15:23:45.970 align:start position:0% all<15:23:43.800> right<15:23:43.980> and<15:23:44.160> finally<15:23:44.520> I've<15:23:44.820> got<15:23:45.060> this 15:23:45.970 --> 15:23:45.980 align:start position:0% all right and finally I've got this 15:23:45.980 --> 15:23:49.010 align:start position:0% all right and finally I've got this slide<15:23:46.980> here<15:23:47.220> this<15:23:47.520> image<15:23:47.880> from 15:23:49.010 --> 15:23:49.020 align:start position:0% slide here this image from 15:23:49.020 --> 15:23:50.470 align:start position:0% slide here this image from um<15:23:49.140> my 15:23:50.470 --> 15:23:50.480 align:start position:0% um my 15:23:50.480 --> 15:23:53.266 align:start position:0% um my netphone.com.au<15:23:51.480> this<15:23:52.320> explains<15:23:52.916> basically 15:23:53.266 --> 15:23:53.276 align:start position:0% netphone.com.au this explains basically 15:23:53.276 --> 15:23:55.970 align:start position:0% netphone.com.au this explains basically how<15:23:54.020> citrunks<15:23:55.020> work<15:23:55.140> especially<15:23:55.916> an 15:23:55.970 --> 15:23:55.980 align:start position:0% how citrunks work especially an 15:23:55.980 --> 15:23:58.370 align:start position:0% how citrunks work especially an initiation<15:23:56.456> protocol<15:23:57.000> if<15:23:57.540> you<15:23:57.660> ever<15:23:57.776> hear<15:23:58.020> sip 15:23:58.370 --> 15:23:58.380 align:start position:0% initiation protocol if you ever hear sip 15:23:58.380 --> 15:24:00.230 align:start position:0% initiation protocol if you ever hear sip or<15:23:58.680> a<15:23:58.800> session<15:23:59.096> initiative<15:23:59.640> initiation 15:24:00.230 --> 15:24:00.240 align:start position:0% or a session initiative initiation 15:24:00.240 --> 15:24:02.746 align:start position:0% or a session initiative initiation protocol<15:24:00.660> which<15:24:00.956> Josh<15:24:01.200> mentioned<15:24:01.800> you 15:24:02.746 --> 15:24:02.756 align:start position:0% protocol which Josh mentioned you 15:24:02.756 --> 15:24:05.630 align:start position:0% protocol which Josh mentioned you immediately<15:24:03.116> think<15:24:03.480> voice<15:24:04.320> over<15:24:04.616> IP<15:24:05.096> this<15:24:05.520> is 15:24:05.630 --> 15:24:05.640 align:start position:0% immediately think voice over IP this is 15:24:05.640 --> 15:24:08.830 align:start position:0% immediately think voice over IP this is what<15:24:05.756> enables<15:24:06.116> voice<15:24:06.416> over<15:24:06.900> IP<15:24:07.320> to<15:24:07.500> work 15:24:08.830 --> 15:24:08.840 align:start position:0% what enables voice over IP to work 15:24:08.840 --> 15:24:12.170 align:start position:0% what enables voice over IP to work trunks<15:24:09.840> enable<15:24:10.080> your<15:24:10.740> PBX<15:24:11.700> to<15:24:11.880> send<15:24:12.060> and 15:24:12.170 --> 15:24:12.180 align:start position:0% trunks enable your PBX to send and 15:24:12.180 --> 15:24:14.390 align:start position:0% trunks enable your PBX to send and receive<15:24:12.480> calls<15:24:12.900> via<15:24:13.200> the<15:24:13.320> Internet<15:24:13.500> so<15:24:14.160> what 15:24:14.390 --> 15:24:14.400 align:start position:0% receive calls via the Internet so what 15:24:14.400 --> 15:24:16.490 align:start position:0% receive calls via the Internet so what it<15:24:14.580> does<15:24:14.756> is<15:24:15.000> it<15:24:15.240> takes<15:24:15.540> your 15:24:16.490 --> 15:24:16.500 align:start position:0% it does is it takes your 15:24:16.500 --> 15:24:18.350 align:start position:0% it does is it takes your um<15:24:16.616> the<15:24:17.220> phone<15:24:17.340> your<15:24:17.700> typical<15:24:18.060> phone 15:24:18.350 --> 15:24:18.360 align:start position:0% um the phone your typical phone 15:24:18.360 --> 15:24:19.730 align:start position:0% um the phone your typical phone connection 15:24:19.730 --> 15:24:19.740 align:start position:0% connection 15:24:19.740 --> 15:24:22.130 align:start position:0% connection and<15:24:20.276> acts<15:24:20.580> as<15:24:20.700> a<15:24:20.936> bridge<15:24:21.060> between<15:24:21.540> the 15:24:22.130 --> 15:24:22.140 align:start position:0% and acts as a bridge between the 15:24:22.140 --> 15:24:24.530 align:start position:0% and acts as a bridge between the internet 15:24:24.530 --> 15:24:24.540 align:start position:0% internet 15:24:24.540 --> 15:24:25.906 align:start position:0% internet that's<15:24:24.956> the 15:24:25.906 --> 15:24:25.916 align:start position:0% that's the 15:24:25.916 --> 15:24:28.850 align:start position:0% that's the um<15:24:25.980> the<15:24:26.220> point<15:24:26.400> of<15:24:26.640> this<15:24:27.060> the<15:24:27.480> SIP<15:24:27.776> trunk 15:24:28.850 --> 15:24:28.860 align:start position:0% um the point of this the SIP trunk 15:24:28.860 --> 15:24:32.086 align:start position:0% um the point of this the SIP trunk so<15:24:29.276> digital<15:24:29.700> equivalent<15:24:30.240> of<15:24:30.416> a<15:24:30.596> phone<15:24:30.776> line 15:24:32.086 --> 15:24:32.096 align:start position:0% so digital equivalent of a phone line 15:24:32.096 --> 15:24:35.390 align:start position:0% so digital equivalent of a phone line enables<15:24:32.820> you<15:24:32.936> to<15:24:33.116> make<15:24:33.360> and<15:24:34.080> voice<15:24:34.916> and<15:24:35.220> or 15:24:35.390 --> 15:24:35.400 align:start position:0% enables you to make and voice and or 15:24:35.400 --> 15:24:38.086 align:start position:0% enables you to make and voice and or video<15:24:35.700> calls<15:24:36.240> video<15:24:36.416> conferencing<15:24:37.020> calls<15:24:37.380> via 15:24:38.086 --> 15:24:38.096 align:start position:0% video calls video conferencing calls via 15:24:38.096 --> 15:24:41.030 align:start position:0% video calls video conferencing calls via the<15:24:38.276> Internet 15:24:41.030 --> 15:24:41.040 align:start position:0% 15:24:41.040 --> 15:24:43.790 align:start position:0% acts<15:24:41.820> as<15:24:41.880> a<15:24:42.060> bridge<15:24:42.180> between<15:24:42.480> your<15:24:42.840> PBX<15:24:43.500> which 15:24:43.790 --> 15:24:43.800 align:start position:0% acts as a bridge between your PBX which 15:24:43.800 --> 15:24:46.790 align:start position:0% acts as a bridge between your PBX which is<15:24:43.980> your<15:24:44.340> phone<15:24:44.776> system<15:24:45.776> that<15:24:46.256> you'd<15:24:46.436> have<15:24:46.560> at 15:24:46.790 --> 15:24:46.800 align:start position:0% is your phone system that you'd have at 15:24:46.800 --> 15:24:50.330 align:start position:0% is your phone system that you'd have at your<15:24:47.580> um<15:24:47.580> corporate<15:24:48.116> office<15:24:48.540> there<15:24:48.956> and<15:24:49.800> IP 15:24:50.330 --> 15:24:50.340 align:start position:0% your um corporate office there and IP 15:24:50.340 --> 15:24:51.650 align:start position:0% your um corporate office there and IP telephony 15:24:51.650 --> 15:24:51.660 align:start position:0% telephony 15:24:51.660 --> 15:24:53.210 align:start position:0% telephony all<15:24:51.956> right<15:24:52.080> so<15:24:52.200> we<15:24:52.380> covered<15:24:52.616> a<15:24:52.740> lot<15:24:52.860> of<15:24:53.040> stuff 15:24:53.210 --> 15:24:53.220 align:start position:0% all right so we covered a lot of stuff 15:24:53.220 --> 15:24:55.370 align:start position:0% all right so we covered a lot of stuff but<15:24:53.936> I<15:24:54.116> think<15:24:54.416> only<15:24:54.596> what<15:24:54.840> you<15:24:54.900> need<15:24:55.020> today<15:24:55.200> and 15:24:55.370 --> 15:24:55.380 align:start position:0% but I think only what you need today and 15:24:55.380 --> 15:24:57.170 align:start position:0% but I think only what you need today and it<15:24:55.560> is<15:24:55.680> covered<15:24:55.860> in<15:24:55.980> other<15:24:56.160> presentations<15:24:56.756> as 15:24:57.170 --> 15:24:57.180 align:start position:0% it is covered in other presentations as 15:24:57.180 --> 15:24:59.710 align:start position:0% it is covered in other presentations as well<15:24:57.360> uh<15:24:57.900> by<15:24:58.200> Josh<15:24:58.380> PPP 15:24:59.710 --> 15:24:59.720 align:start position:0% well uh by Josh PPP 15:24:59.720 --> 15:25:02.810 align:start position:0% well uh by Josh PPP pppoe<15:25:00.720> Dynamic<15:25:01.500> multi-point<15:25:01.980> VPN<15:25:02.400> and<15:25:02.640> zip 15:25:02.810 --> 15:25:02.820 align:start position:0% pppoe Dynamic multi-point VPN and zip 15:25:02.820 --> 15:25:04.906 align:start position:0% pppoe Dynamic multi-point VPN and zip Trunks<15:25:03.300> and<15:25:03.480> I've<15:25:03.660> highlighted<15:25:04.436> what<15:25:04.616> I<15:25:04.740> think 15:25:04.906 --> 15:25:04.916 align:start position:0% Trunks and I've highlighted what I think 15:25:04.916 --> 15:25:07.730 align:start position:0% Trunks and I've highlighted what I think would<15:25:05.096> be<15:25:05.220> the<15:25:05.340> typical<15:25:05.700> exam<15:25:06.480> questions<15:25:06.740> so 15:25:07.730 --> 15:25:07.740 align:start position:0% would be the typical exam questions so 15:25:07.740 --> 15:25:14.630 align:start position:0% would be the typical exam questions so that's<15:25:07.860> all<15:25:08.040> for<15:25:08.220> now<15:25:08.400> thanks<15:25:08.756> for<15:25:08.936> watching 15:25:14.630 --> 15:25:14.640 align:start position:0% 15:25:14.640 --> 15:25:21.426 align:start position:0% [Music] 15:25:21.426 --> 15:25:21.436 align:start position:0% [Music] 15:25:21.436 --> 15:25:37.730 align:start position:0% [Music] thank<15:25:22.436> you 15:25:37.730 --> 15:25:37.740 align:start position:0% 15:25:37.740 --> 15:25:41.210 align:start position:0% remote<15:25:38.456> access<15:25:39.200> remote<15:25:40.220> networking 15:25:41.210 --> 15:25:41.220 align:start position:0% remote access remote networking 15:25:41.220 --> 15:25:43.310 align:start position:0% remote access remote networking fundamentals 15:25:43.310 --> 15:25:43.320 align:start position:0% fundamentals 15:25:43.320 --> 15:25:46.426 align:start position:0% fundamentals in<15:25:43.860> the<15:25:44.040> last<15:25:44.160> lesson<15:25:44.640> we<15:25:45.060> talked<15:25:45.540> about<15:25:45.596> wide 15:25:46.426 --> 15:25:46.436 align:start position:0% in the last lesson we talked about wide 15:25:46.436 --> 15:25:49.010 align:start position:0% in the last lesson we talked about wide area<15:25:46.616> networks<15:25:47.340> we<15:25:48.060> talked<15:25:48.360> about<15:25:48.416> how<15:25:48.900> they 15:25:49.010 --> 15:25:49.020 align:start position:0% area networks we talked about how they 15:25:49.020 --> 15:25:50.870 align:start position:0% area networks we talked about how they can<15:25:49.140> be<15:25:49.256> implemented<15:25:49.800> what<15:25:50.160> their<15:25:50.340> benefits 15:25:50.870 --> 15:25:50.880 align:start position:0% can be implemented what their benefits 15:25:50.880 --> 15:25:53.746 align:start position:0% can be implemented what their benefits are<15:25:51.116> how<15:25:51.900> they<15:25:52.080> transfer<15:25:52.436> information<15:25:52.756> some 15:25:53.746 --> 15:25:53.756 align:start position:0% are how they transfer information some 15:25:53.756 --> 15:25:55.850 align:start position:0% are how they transfer information some of<15:25:53.880> the<15:25:53.936> Technologies<15:25:54.416> we<15:25:54.840> use<15:25:55.020> and<15:25:55.500> so<15:25:55.616> on<15:25:55.740> and 15:25:55.850 --> 15:25:55.860 align:start position:0% of the Technologies we use and so on and 15:25:55.860 --> 15:25:58.010 align:start position:0% of the Technologies we use and so on and so<15:25:56.040> forth<15:25:56.340> now<15:25:57.000> in<15:25:57.240> this<15:25:57.416> lesson<15:25:57.720> we're<15:25:57.900> going 15:25:58.010 --> 15:25:58.020 align:start position:0% so forth now in this lesson we're going 15:25:58.020 --> 15:26:00.586 align:start position:0% so forth now in this lesson we're going to<15:25:58.200> talk<15:25:58.320> more<15:25:58.680> about<15:25:59.040> remote<15:25:59.756> networking 15:26:00.586 --> 15:26:00.596 align:start position:0% to talk more about remote networking 15:26:00.596 --> 15:26:03.406 align:start position:0% to talk more about remote networking access<15:26:00.980> remote<15:26:01.980> networking<15:26:02.700> in<15:26:02.880> wands 15:26:03.406 --> 15:26:03.416 align:start position:0% access remote networking in wands 15:26:03.416 --> 15:26:05.926 align:start position:0% access remote networking in wands actually<15:26:03.660> really<15:26:03.840> go<15:26:04.140> hand<15:26:04.380> in<15:26:04.560> hand<15:26:04.800> and<15:26:05.756> if 15:26:05.926 --> 15:26:05.936 align:start position:0% actually really go hand in hand and if 15:26:05.936 --> 15:26:07.790 align:start position:0% actually really go hand in hand and if you<15:26:06.060> think<15:26:06.300> about<15:26:06.416> it<15:26:06.720> more<15:26:07.200> of<15:26:07.320> what<15:26:07.500> we<15:26:07.616> do 15:26:07.790 --> 15:26:07.800 align:start position:0% you think about it more of what we do 15:26:07.800 --> 15:26:10.550 align:start position:0% you think about it more of what we do now<15:26:08.040> more<15:26:08.400> than<15:26:08.520> ever<15:26:08.756> allows<15:26:09.720> us<15:26:09.840> to<15:26:10.256> remote 15:26:10.550 --> 15:26:10.560 align:start position:0% now more than ever allows us to remote 15:26:10.560 --> 15:26:14.390 align:start position:0% now more than ever allows us to remote in<15:26:11.220> from<15:26:11.936> home<15:26:12.300> to<15:26:13.140> the<15:26:13.380> Wan 15:26:14.390 --> 15:26:14.400 align:start position:0% in from home to the Wan 15:26:14.400 --> 15:26:16.906 align:start position:0% in from home to the Wan the<15:26:15.000> largest<15:26:15.240> land<15:26:15.416> in<15:26:15.720> the<15:26:15.776> world<15:26:15.900> being<15:26:16.380> the 15:26:16.906 --> 15:26:16.916 align:start position:0% the largest land in the world being the 15:26:16.916 --> 15:26:20.570 align:start position:0% the largest land in the world being the wide<15:26:17.820> area<15:26:18.000> network<15:26:18.416> of<15:26:18.900> the<15:26:19.140> internet<15:26:19.580> and 15:26:20.570 --> 15:26:20.580 align:start position:0% wide area network of the internet and 15:26:20.580 --> 15:26:22.550 align:start position:0% wide area network of the internet and then<15:26:20.756> access 15:26:22.550 --> 15:26:22.560 align:start position:0% then access 15:26:22.560 --> 15:26:25.906 align:start position:0% then access our<15:26:23.160> lands<15:26:23.640> at<15:26:24.000> work<15:26:24.240> this<15:26:25.200> really<15:26:25.436> allows<15:26:25.800> us 15:26:25.906 --> 15:26:25.916 align:start position:0% our lands at work this really allows us 15:26:25.916 --> 15:26:28.010 align:start position:0% our lands at work this really allows us to<15:26:26.456> not<15:26:26.756> only<15:26:26.880> get<15:26:27.116> stuff<15:26:27.360> done<15:26:27.596> but<15:26:27.840> is 15:26:28.010 --> 15:26:28.020 align:start position:0% to not only get stuff done but is 15:26:28.020 --> 15:26:32.030 align:start position:0% to not only get stuff done but is changing<15:26:28.500> the<15:26:28.800> landscape<15:26:29.400> of<15:26:30.060> how<15:26:31.040> networking 15:26:32.030 --> 15:26:32.040 align:start position:0% changing the landscape of how networking 15:26:32.040 --> 15:26:35.510 align:start position:0% changing the landscape of how networking the<15:26:32.340> internet<15:26:32.456> and<15:26:32.880> security<15:26:33.180> have 15:26:35.510 --> 15:26:35.520 align:start position:0% the internet and security have 15:26:35.520 --> 15:26:38.266 align:start position:0% the internet and security have been<15:26:36.180> created<15:26:36.540> and<15:26:37.320> how<15:26:37.500> we<15:26:37.680> continue<15:26:37.860> to<15:26:38.096> work 15:26:38.266 --> 15:26:38.276 align:start position:0% been created and how we continue to work 15:26:38.276 --> 15:26:40.550 align:start position:0% been created and how we continue to work with<15:26:38.456> them<15:26:38.640> so<15:26:39.540> we're<15:26:39.956> going<15:26:40.140> to<15:26:40.256> talk<15:26:40.380> about 15:26:40.550 --> 15:26:40.560 align:start position:0% with them so we're going to talk about 15:26:40.560 --> 15:26:42.230 align:start position:0% with them so we're going to talk about this<15:26:40.860> in<15:26:41.160> this<15:26:41.340> module<15:26:41.700> and<15:26:41.820> in<15:26:42.000> the<15:26:42.116> next 15:26:42.230 --> 15:26:42.240 align:start position:0% this in this module and in the next 15:26:42.240 --> 15:26:44.150 align:start position:0% this in this module and in the next couple<15:26:42.480> but<15:26:43.140> for<15:26:43.320> this<15:26:43.436> one<15:26:43.560> the<15:26:43.916> first<15:26:44.040> thing 15:26:44.150 --> 15:26:44.160 align:start position:0% couple but for this one the first thing 15:26:44.160 --> 15:26:45.710 align:start position:0% couple but for this one the first thing we<15:26:44.276> want<15:26:44.400> to<15:26:44.520> do<15:26:44.580> is<15:26:44.756> Define<15:26:45.000> what<15:26:45.540> remote 15:26:45.710 --> 15:26:45.720 align:start position:0% we want to do is Define what remote 15:26:45.720 --> 15:26:48.586 align:start position:0% we want to do is Define what remote networking<15:26:46.380> really<15:26:46.680> is<15:26:47.000> then<15:26:48.000> we<15:26:48.360> want<15:26:48.480> to 15:26:48.586 --> 15:26:48.596 align:start position:0% networking really is then we want to 15:26:48.596 --> 15:26:50.690 align:start position:0% networking really is then we want to identify<15:26:49.140> some<15:26:49.500> of<15:26:49.616> the<15:26:49.800> technologies<15:26:50.340> that 15:26:50.690 --> 15:26:50.700 align:start position:0% identify some of the technologies that 15:26:50.700 --> 15:26:52.550 align:start position:0% identify some of the technologies that we<15:26:50.880> see<15:26:51.000> in<15:26:51.240> place<15:26:51.416> when<15:26:51.720> we<15:26:51.900> discuss<15:26:52.256> remote 15:26:52.550 --> 15:26:52.560 align:start position:0% we see in place when we discuss remote 15:26:52.560 --> 15:26:55.730 align:start position:0% we see in place when we discuss remote networking<15:26:53.220> these<15:26:53.880> include<15:26:54.320> VPN<15:26:55.320> which<15:26:55.616> we've 15:26:55.730 --> 15:26:55.740 align:start position:0% networking these include VPN which we've 15:26:55.740 --> 15:26:59.210 align:start position:0% networking these include VPN which we've already<15:26:55.860> discussed<15:26:56.400> in<15:26:56.820> some<15:26:57.180> raw<15:26:58.020> detail<15:26:58.380> or 15:26:59.210 --> 15:26:59.220 align:start position:0% already discussed in some raw detail or 15:26:59.220 --> 15:27:01.190 align:start position:0% already discussed in some raw detail or a<15:26:59.520> virtual 15:27:01.190 --> 15:27:01.200 align:start position:0% a virtual 15:27:01.200 --> 15:27:04.606 align:start position:0% a virtual private 15:27:04.606 --> 15:27:04.616 align:start position:0% 15:27:04.616 --> 15:27:09.350 align:start position:0% Network 15:27:09.350 --> 15:27:09.360 align:start position:0% 15:27:09.360 --> 15:27:14.210 align:start position:0% radius<15:27:10.276> which<15:27:11.276> allows<15:27:11.880> us<15:27:12.180> to<15:27:13.220> authenticate 15:27:14.210 --> 15:27:14.220 align:start position:0% radius which allows us to authenticate 15:27:14.220 --> 15:27:17.810 align:start position:0% radius which allows us to authenticate users<15:27:14.640> once<15:27:15.116> they<15:27:15.360> connect<15:27:15.980> and<15:27:16.980> Tech<15:27:17.276> acts 15:27:17.810 --> 15:27:17.820 align:start position:0% users once they connect and Tech acts 15:27:17.820 --> 15:27:20.510 align:start position:0% users once they connect and Tech acts which<15:27:18.360> allows<15:27:18.900> us<15:27:19.080> to<15:27:19.380> keep<15:27:19.616> its<15:27:20.040> all<15:27:20.096> secure 15:27:20.510 --> 15:27:20.520 align:start position:0% which allows us to keep its all secure 15:27:20.520 --> 15:27:23.630 align:start position:0% which allows us to keep its all secure so<15:27:21.480> these<15:27:21.840> three<15:27:22.020> are<15:27:22.500> used<15:27:22.800> in<15:27:23.276> Enterprise 15:27:23.630 --> 15:27:23.640 align:start position:0% so these three are used in Enterprise 15:27:23.640 --> 15:27:26.746 align:start position:0% so these three are used in Enterprise settings<15:27:24.300> to<15:27:24.720> allow<15:27:25.020> someone<15:27:25.320> to<15:27:26.160> remote<15:27:26.400> in 15:27:26.746 --> 15:27:26.756 align:start position:0% settings to allow someone to remote in 15:27:26.756 --> 15:27:30.050 align:start position:0% settings to allow someone to remote in from<15:27:27.300> home<15:27:27.596> and<15:27:28.200> connect<15:27:28.436> to<15:27:29.160> the<15:27:29.276> network<15:27:29.456> at 15:27:30.050 --> 15:27:30.060 align:start position:0% from home and connect to the network at 15:27:30.060 --> 15:27:30.890 align:start position:0% from home and connect to the network at work 15:27:30.890 --> 15:27:30.900 align:start position:0% work 15:27:30.900 --> 15:27:33.406 align:start position:0% work so<15:27:31.680> wands<15:27:32.276> are<15:27:32.400> networks<15:27:32.820> that<15:27:33.060> are<15:27:33.240> not 15:27:33.406 --> 15:27:33.416 align:start position:0% so wands are networks that are not 15:27:33.416 --> 15:27:35.446 align:start position:0% so wands are networks that are not restrained<15:27:34.080> to<15:27:34.380> one<15:27:34.860> single<15:27:35.220> physical 15:27:35.446 --> 15:27:35.456 align:start position:0% restrained to one single physical 15:27:35.456 --> 15:27:37.670 align:start position:0% restrained to one single physical location<15:27:35.900> they're<15:27:36.900> typically<15:27:37.256> as<15:27:37.436> we've 15:27:37.670 --> 15:27:37.680 align:start position:0% location they're typically as we've 15:27:37.680 --> 15:27:39.766 align:start position:0% location they're typically as we've discussed<15:27:38.096> many<15:27:38.520> local<15:27:38.820> area<15:27:39.060> networks<15:27:39.596> that 15:27:39.766 --> 15:27:39.776 align:start position:0% discussed many local area networks that 15:27:39.776 --> 15:27:41.746 align:start position:0% discussed many local area networks that are<15:27:39.956> joined<15:27:40.320> together<15:27:40.560> to<15:27:40.916> create<15:27:41.096> one<15:27:41.520> big 15:27:41.746 --> 15:27:41.756 align:start position:0% are joined together to create one big 15:27:41.756 --> 15:27:43.906 align:start position:0% are joined together to create one big Wham<15:27:42.300> however<15:27:42.956> this<15:27:43.436> isn't<15:27:43.680> the<15:27:43.800> only 15:27:43.906 --> 15:27:43.916 align:start position:0% Wham however this isn't the only 15:27:43.916 --> 15:27:45.406 align:start position:0% Wham however this isn't the only configuration<15:27:44.400> they<15:27:44.640> can<15:27:44.820> have<15:27:44.936> and<15:27:45.180> remote 15:27:45.406 --> 15:27:45.416 align:start position:0% configuration they can have and remote 15:27:45.416 --> 15:27:47.030 align:start position:0% configuration they can have and remote networking<15:27:46.020> is<15:27:46.200> something<15:27:46.320> that<15:27:46.560> ties<15:27:46.860> in 15:27:47.030 --> 15:27:47.040 align:start position:0% networking is something that ties in 15:27:47.040 --> 15:27:49.370 align:start position:0% networking is something that ties in really<15:27:47.340> well<15:27:47.580> with<15:27:47.880> wide<15:27:48.060> area<15:27:48.240> Networks<15:27:49.020> you 15:27:49.370 --> 15:27:49.380 align:start position:0% really well with wide area Networks you 15:27:49.380 --> 15:27:51.650 align:start position:0% really well with wide area Networks you see<15:27:49.500> remote<15:27:49.680> networking<15:27:50.276> is<15:27:50.520> the<15:27:50.756> process<15:27:51.116> of 15:27:51.650 --> 15:27:51.660 align:start position:0% see remote networking is the process of 15:27:51.660 --> 15:27:53.870 align:start position:0% see remote networking is the process of connecting<15:27:52.140> to<15:27:52.500> a<15:27:52.680> network<15:27:52.800> without<15:27:53.520> being 15:27:53.870 --> 15:27:53.880 align:start position:0% connecting to a network without being 15:27:53.880 --> 15:27:56.810 align:start position:0% connecting to a network without being directly<15:27:54.596> attached<15:27:55.320> to<15:27:55.616> it<15:27:55.800> or<15:27:56.400> physically 15:27:56.810 --> 15:27:56.820 align:start position:0% directly attached to it or physically 15:27:56.820 --> 15:27:59.690 align:start position:0% directly attached to it or physically present<15:27:57.300> at<15:27:57.720> the<15:27:57.900> site<15:27:58.080> in<15:27:58.800> other<15:27:58.916> words<15:27:59.096> a 15:27:59.690 --> 15:27:59.700 align:start position:0% present at the site in other words a 15:27:59.700 --> 15:28:02.390 align:start position:0% present at the site in other words a user<15:28:00.240> or<15:28:00.416> group<15:28:00.660> of<15:28:00.776> users<15:28:01.200> can<15:28:01.680> remotely 15:28:02.390 --> 15:28:02.400 align:start position:0% user or group of users can remotely 15:28:02.400 --> 15:28:04.490 align:start position:0% user or group of users can remotely connect<15:28:02.756> to<15:28:03.240> a<15:28:03.416> network<15:28:03.540> without<15:28:04.200> actually 15:28:04.490 --> 15:28:04.500 align:start position:0% connect to a network without actually 15:28:04.500 --> 15:28:06.586 align:start position:0% connect to a network without actually being<15:28:04.980> where<15:28:05.456> the<15:28:05.640> network<15:28:05.756> is<15:28:06.116> established 15:28:06.586 --> 15:28:06.596 align:start position:0% being where the network is established 15:28:06.596 --> 15:28:09.406 align:start position:0% being where the network is established so<15:28:07.436> if<15:28:07.916> I<15:28:08.160> were<15:28:08.340> at<15:28:08.580> home<15:28:08.756> and<15:28:09.000> wanted<15:28:09.240> to 15:28:09.406 --> 15:28:09.416 align:start position:0% so if I were at home and wanted to 15:28:09.416 --> 15:28:11.870 align:start position:0% so if I were at home and wanted to connect<15:28:09.596> to<15:28:09.900> a<15:28:10.080> network<15:28:10.256> say<15:28:10.616> in<15:28:10.916> China<15:28:11.160> I 15:28:11.870 --> 15:28:11.880 align:start position:0% connect to a network say in China I 15:28:11.880 --> 15:28:13.790 align:start position:0% connect to a network say in China I could<15:28:12.060> actually<15:28:12.300> connect<15:28:12.840> as<15:28:13.256> though<15:28:13.436> I<15:28:13.616> were 15:28:13.790 --> 15:28:13.800 align:start position:0% could actually connect as though I were 15:28:13.800 --> 15:28:15.470 align:start position:0% could actually connect as though I were sitting<15:28:14.096> right<15:28:14.456> in<15:28:14.640> an<15:28:14.820> office<15:28:15.000> in<15:28:15.300> China 15:28:15.470 --> 15:28:15.480 align:start position:0% sitting right in an office in China 15:28:15.480 --> 15:28:17.086 align:start position:0% sitting right in an office in China without<15:28:15.956> actually<15:28:16.256> physically<15:28:16.740> being 15:28:17.086 --> 15:28:17.096 align:start position:0% without actually physically being 15:28:17.096 --> 15:28:19.370 align:start position:0% without actually physically being present<15:28:17.520> this<15:28:18.300> type<15:28:18.480> of<15:28:18.596> thing<15:28:18.720> comes<15:28:19.140> in 15:28:19.370 --> 15:28:19.380 align:start position:0% present this type of thing comes in 15:28:19.380 --> 15:28:20.810 align:start position:0% present this type of thing comes in handy<15:28:19.740> quite<15:28:20.040> a<15:28:20.160> bit 15:28:20.810 --> 15:28:20.820 align:start position:0% handy quite a bit 15:28:20.820 --> 15:28:23.086 align:start position:0% handy quite a bit now<15:28:21.240> remote<15:28:21.416> networking<15:28:21.900> isn't<15:28:22.380> always 15:28:23.086 --> 15:28:23.096 align:start position:0% now remote networking isn't always 15:28:23.096 --> 15:28:24.830 align:start position:0% now remote networking isn't always happen<15:28:23.400> between<15:28:23.756> two<15:28:24.240> very<15:28:24.480> distant 15:28:24.830 --> 15:28:24.840 align:start position:0% happen between two very distant 15:28:24.840 --> 15:28:27.106 align:start position:0% happen between two very distant locations<15:28:25.500> in<15:28:26.160> fact<15:28:26.276> it<15:28:26.456> can<15:28:26.580> be<15:28:26.700> used<15:28:26.756> within 15:28:27.106 --> 15:28:27.116 align:start position:0% locations in fact it can be used within 15:28:27.116 --> 15:28:30.106 align:start position:0% locations in fact it can be used within the<15:28:27.240> same<15:28:27.416> building<15:28:27.776> the<15:28:28.380> same<15:28:28.616> room<15:28:29.116> while 15:28:30.106 --> 15:28:30.116 align:start position:0% the same building the same room while 15:28:30.116 --> 15:28:32.446 align:start position:0% the same building the same room while traveling<15:28:30.720> and<15:28:31.256> remote<15:28:31.436> networking<15:28:32.096> not<15:28:32.276> only 15:28:32.446 --> 15:28:32.456 align:start position:0% traveling and remote networking not only 15:28:32.456 --> 15:28:35.150 align:start position:0% traveling and remote networking not only works<15:28:32.880> on<15:28:33.360> a<15:28:33.596> long<15:28:33.720> distance<15:28:33.956> level<15:28:34.320> but<15:28:34.740> on<15:28:35.040> a 15:28:35.150 --> 15:28:35.160 align:start position:0% works on a long distance level but on a 15:28:35.160 --> 15:28:36.946 align:start position:0% works on a long distance level but on a local<15:28:35.276> network<15:28:35.580> as<15:28:35.936> well<15:28:36.060> for<15:28:36.720> instance 15:28:36.946 --> 15:28:36.956 align:start position:0% local network as well for instance 15:28:36.956 --> 15:28:39.710 align:start position:0% local network as well for instance suppose<15:28:37.436> that<15:28:37.860> I'm<15:28:38.276> an<15:28:38.456> administrator<15:28:39.000> in<15:28:39.480> my 15:28:39.710 --> 15:28:39.720 align:start position:0% suppose that I'm an administrator in my 15:28:39.720 --> 15:28:42.350 align:start position:0% suppose that I'm an administrator in my office<15:28:40.256> and<15:28:40.916> I<15:28:41.040> want<15:28:41.160> to<15:28:41.340> access<15:28:41.520> the<15:28:41.936> contents 15:28:42.350 --> 15:28:42.360 align:start position:0% office and I want to access the contents 15:28:42.360 --> 15:28:44.150 align:start position:0% office and I want to access the contents of<15:28:42.480> a<15:28:42.660> user's<15:28:42.956> computer<15:28:43.080> where<15:28:43.740> I<15:28:43.860> want<15:28:44.040> to 15:28:44.150 --> 15:28:44.160 align:start position:0% of a user's computer where I want to 15:28:44.160 --> 15:28:46.370 align:start position:0% of a user's computer where I want to restart<15:28:44.340> a<15:28:44.756> server<15:28:45.060> well<15:28:45.660> instead<15:28:46.080> of<15:28:46.200> having 15:28:46.370 --> 15:28:46.380 align:start position:0% restart a server well instead of having 15:28:46.380 --> 15:28:48.470 align:start position:0% restart a server well instead of having to<15:28:46.616> get<15:28:46.740> up<15:28:46.860> walk<15:28:47.160> up<15:28:47.340> to<15:28:47.520> the<15:28:47.640> fourth<15:28:47.936> floor<15:28:48.116> or 15:28:48.470 --> 15:28:48.480 align:start position:0% to get up walk up to the fourth floor or 15:28:48.480 --> 15:28:50.086 align:start position:0% to get up walk up to the fourth floor or down<15:28:48.660> to<15:28:48.776> the<15:28:48.900> basement<15:28:49.080> wherever<15:28:49.616> the<15:28:49.800> server 15:28:50.086 --> 15:28:50.096 align:start position:0% down to the basement wherever the server 15:28:50.096 --> 15:28:52.790 align:start position:0% down to the basement wherever the server is<15:28:50.276> I<15:28:51.000> could<15:28:51.116> simply<15:28:51.480> remote<15:28:51.776> in<15:28:52.320> to<15:28:52.616> the 15:28:52.790 --> 15:28:52.800 align:start position:0% is I could simply remote in to the 15:28:52.800 --> 15:28:55.246 align:start position:0% is I could simply remote in to the server<15:28:53.096> and<15:28:53.456> reboot<15:28:53.880> it<15:28:54.000> from<15:28:54.180> there<15:28:54.360> so<15:28:55.140> you 15:28:55.246 --> 15:28:55.256 align:start position:0% server and reboot it from there so you 15:28:55.256 --> 15:28:57.290 align:start position:0% server and reboot it from there so you can<15:28:55.380> see<15:28:55.500> that<15:28:55.740> it's<15:28:55.980> a<15:28:56.220> huge<15:28:56.640> time<15:28:56.820> saving 15:28:57.290 --> 15:28:57.300 align:start position:0% can see that it's a huge time saving 15:28:57.300 --> 15:29:00.230 align:start position:0% can see that it's a huge time saving device<15:28:57.540> however<15:28:58.320> it<15:28:58.740> also<15:28:59.040> opens<15:28:59.400> up<15:28:59.520> a<15:29:00.000> lot<15:29:00.060> of 15:29:00.230 --> 15:29:00.240 align:start position:0% device however it also opens up a lot of 15:29:00.240 --> 15:29:02.690 align:start position:0% device however it also opens up a lot of possibilities<15:29:00.776> for<15:29:01.320> security<15:29:01.616> issues<15:29:02.340> and<15:29:02.520> so 15:29:02.690 --> 15:29:02.700 align:start position:0% possibilities for security issues and so 15:29:02.700 --> 15:29:05.990 align:start position:0% possibilities for security issues and so on<15:29:02.820> so<15:29:03.540> here<15:29:04.020> is<15:29:04.200> an<15:29:04.380> example<15:29:04.680> of<15:29:05.040> what<15:29:05.400> remote 15:29:05.990 --> 15:29:06.000 align:start position:0% on so here is an example of what remote 15:29:06.000 --> 15:29:08.630 align:start position:0% on so here is an example of what remote network<15:29:06.416> connectivity<15:29:07.140> could<15:29:07.500> look<15:29:07.800> like<15:29:07.980> the 15:29:08.630 --> 15:29:08.640 align:start position:0% network connectivity could look like the 15:29:08.640 --> 15:29:10.490 align:start position:0% network connectivity could look like the user<15:29:08.880> is<15:29:09.000> in<15:29:09.240> China<15:29:09.416> on<15:29:09.900> the<15:29:10.020> right<15:29:10.140> and<15:29:10.320> they 15:29:10.490 --> 15:29:10.500 align:start position:0% user is in China on the right and they 15:29:10.500 --> 15:29:13.550 align:start position:0% user is in China on the right and they need<15:29:10.680> to<15:29:10.860> connect<15:29:11.300> into<15:29:12.300> the<15:29:12.776> network<15:29:12.956> in<15:29:13.320> New 15:29:13.550 --> 15:29:13.560 align:start position:0% need to connect into the network in New 15:29:13.560 --> 15:29:16.246 align:start position:0% need to connect into the network in New York<15:29:13.680> here<15:29:14.040> on<15:29:14.220> the<15:29:14.400> left<15:29:14.520> so<15:29:15.480> they're<15:29:15.840> sitting 15:29:16.246 --> 15:29:16.256 align:start position:0% York here on the left so they're sitting 15:29:16.256 --> 15:29:18.470 align:start position:0% York here on the left so they're sitting at<15:29:16.380> one<15:29:16.616> physical<15:29:16.860> location<15:29:17.276> and<15:29:18.240> they 15:29:18.470 --> 15:29:18.480 align:start position:0% at one physical location and they 15:29:18.480 --> 15:29:20.690 align:start position:0% at one physical location and they connect<15:29:18.720> through<15:29:19.320> a<15:29:19.616> Wan<15:29:19.980> which<15:29:20.456> we're<15:29:20.580> going 15:29:20.690 --> 15:29:20.700 align:start position:0% connect through a Wan which we're going 15:29:20.700 --> 15:29:23.210 align:start position:0% connect through a Wan which we're going to<15:29:20.880> called<15:29:21.360> the<15:29:21.596> internet<15:29:21.776> the<15:29:22.320> largest<15:29:22.616> Wan 15:29:23.210 --> 15:29:23.220 align:start position:0% to called the internet the largest Wan 15:29:23.220 --> 15:29:26.150 align:start position:0% to called the internet the largest Wan in<15:29:23.640> the<15:29:23.820> entire<15:29:24.180> world<15:29:24.540> and<15:29:25.500> they<15:29:25.800> remotely 15:29:26.150 --> 15:29:26.160 align:start position:0% in the entire world and they remotely 15:29:26.160 --> 15:29:28.246 align:start position:0% in the entire world and they remotely connect<15:29:26.400> in<15:29:27.360> some<15:29:27.540> sort<15:29:27.660> of<15:29:27.776> way<15:29:27.840> which<15:29:28.080> we'll 15:29:28.246 --> 15:29:28.256 align:start position:0% connect in some sort of way which we'll 15:29:28.256 --> 15:29:29.390 align:start position:0% connect in some sort of way which we'll talk<15:29:28.436> about<15:29:28.560> usually<15:29:28.980> through<15:29:29.160> something 15:29:29.390 --> 15:29:29.400 align:start position:0% talk about usually through something 15:29:29.400 --> 15:29:34.370 align:start position:0% talk about usually through something called<15:29:29.700> a<15:29:30.060> VPN<15:29:31.020> using<15:29:31.800> all<15:29:32.040> sorts<15:29:32.340> of<15:29:32.456> public 15:29:34.370 --> 15:29:34.380 align:start position:0% called a VPN using all sorts of public 15:29:34.380 --> 15:29:37.670 align:start position:0% called a VPN using all sorts of public networks<15:29:35.160> and<15:29:35.880> eventually<15:29:36.300> they<15:29:36.900> reach<15:29:37.256> the 15:29:37.670 --> 15:29:37.680 align:start position:0% networks and eventually they reach the 15:29:37.680 --> 15:29:41.446 align:start position:0% networks and eventually they reach the router<15:29:38.096> at<15:29:38.880> their<15:29:39.180> corporate<15:29:39.660> office 15:29:41.446 --> 15:29:41.456 align:start position:0% router at their corporate office 15:29:41.456 --> 15:29:44.630 align:start position:0% router at their corporate office and<15:29:42.116> then<15:29:42.300> it's<15:29:42.776> as<15:29:43.080> if<15:29:43.320> they<15:29:44.220> are<15:29:44.400> actually 15:29:44.630 --> 15:29:44.640 align:start position:0% and then it's as if they are actually 15:29:44.640 --> 15:29:46.730 align:start position:0% and then it's as if they are actually sitting<15:29:45.116> there<15:29:45.360> connected<15:29:45.956> into<15:29:46.320> the<15:29:46.560> network 15:29:46.730 --> 15:29:46.740 align:start position:0% sitting there connected into the network 15:29:46.740 --> 15:29:49.426 align:start position:0% sitting there connected into the network they<15:29:47.400> can<15:29:47.580> now<15:29:47.756> access<15:29:48.060> resources<15:29:48.956> on<15:29:49.256> local 15:29:49.426 --> 15:29:49.436 align:start position:0% they can now access resources on local 15:29:49.436 --> 15:29:52.190 align:start position:0% they can now access resources on local clients<15:29:49.980> or<15:29:50.640> even<15:29:50.820> on<15:29:51.060> the<15:29:51.180> server<15:29:51.480> and<15:29:52.020> all 15:29:52.190 --> 15:29:52.200 align:start position:0% clients or even on the server and all 15:29:52.200 --> 15:29:54.406 align:start position:0% clients or even on the server and all without<15:29:52.380> physically<15:29:52.916> being<15:29:53.276> at<15:29:54.000> the<15:29:54.240> location 15:29:54.406 --> 15:29:54.416 align:start position:0% without physically being at the location 15:29:54.416 --> 15:29:57.170 align:start position:0% without physically being at the location in<15:29:55.380> New<15:29:55.560> York<15:29:55.740> now<15:29:56.220> there<15:29:56.520> are<15:29:56.580> a<15:29:56.640> lot<15:29:56.700> of<15:29:56.880> terms 15:29:57.170 --> 15:29:57.180 align:start position:0% in New York now there are a lot of terms 15:29:57.180 --> 15:29:59.990 align:start position:0% in New York now there are a lot of terms we<15:29:57.416> hear<15:29:57.660> when<15:29:57.956> we<15:29:58.140> talk<15:29:58.320> about<15:29:59.000> remote 15:29:59.990 --> 15:30:00.000 align:start position:0% we hear when we talk about remote 15:30:00.000 --> 15:30:02.266 align:start position:0% we hear when we talk about remote networking<15:30:00.596> and<15:30:00.720> remote<15:30:00.956> access<15:30:01.320> most<15:30:02.096> of 15:30:02.266 --> 15:30:02.276 align:start position:0% networking and remote access most of 15:30:02.276 --> 15:30:04.790 align:start position:0% networking and remote access most of them<15:30:02.340> end<15:30:02.700> up<15:30:02.820> being<15:30:03.060> acronyms<15:30:03.900> for<15:30:04.320> the<15:30:04.616> sake 15:30:04.790 --> 15:30:04.800 align:start position:0% them end up being acronyms for the sake 15:30:04.800 --> 15:30:06.946 align:start position:0% them end up being acronyms for the sake of<15:30:04.980> time<15:30:05.096> and<15:30:05.340> convenience<15:30:05.820> but<15:30:06.660> there<15:30:06.840> are 15:30:06.946 --> 15:30:06.956 align:start position:0% of time and convenience but there are 15:30:06.956 --> 15:30:08.510 align:start position:0% of time and convenience but there are three<15:30:07.140> that<15:30:07.320> I<15:30:07.500> want<15:30:07.616> to<15:30:07.740> specifically<15:30:08.160> talk 15:30:08.510 --> 15:30:08.520 align:start position:0% three that I want to specifically talk 15:30:08.520 --> 15:30:09.710 align:start position:0% three that I want to specifically talk about<15:30:08.700> here<15:30:09.060> that<15:30:09.300> we're<15:30:09.416> going<15:30:09.540> to<15:30:09.596> talk 15:30:09.710 --> 15:30:09.720 align:start position:0% about here that we're going to talk 15:30:09.720 --> 15:30:11.330 align:start position:0% about here that we're going to talk about<15:30:09.840> in<15:30:10.320> more<15:30:10.500> detail<15:30:10.860> in<15:30:11.096> the<15:30:11.220> coming 15:30:11.330 --> 15:30:11.340 align:start position:0% about in more detail in the coming 15:30:11.340 --> 15:30:15.106 align:start position:0% about in more detail in the coming modules<15:30:11.900> the<15:30:12.900> first<15:30:13.020> is<15:30:13.436> VPN<15:30:14.220> or<15:30:14.640> virtual 15:30:15.106 --> 15:30:15.116 align:start position:0% modules the first is VPN or virtual 15:30:15.116 --> 15:30:16.906 align:start position:0% modules the first is VPN or virtual private<15:30:15.540> network<15:30:15.720> is<15:30:16.380> this<15:30:16.560> something<15:30:16.680> we've 15:30:16.906 --> 15:30:16.916 align:start position:0% private network is this something we've 15:30:16.916 --> 15:30:18.290 align:start position:0% private network is this something we've talked<15:30:17.160> before<15:30:17.276> and<15:30:17.456> we'll<15:30:17.640> talk<15:30:17.756> about<15:30:17.936> late 15:30:18.290 --> 15:30:18.300 align:start position:0% talked before and we'll talk about late 15:30:18.300 --> 15:30:20.746 align:start position:0% talked before and we'll talk about late a<15:30:18.776> little<15:30:18.900> bit<15:30:19.020> later<15:30:19.200> but<15:30:19.800> in<15:30:19.980> essence<15:30:20.340> it 15:30:20.746 --> 15:30:20.756 align:start position:0% a little bit later but in essence it 15:30:20.756 --> 15:30:23.510 align:start position:0% a little bit later but in essence it extends<15:30:21.300> a<15:30:21.540> lan<15:30:21.840> or<15:30:22.020> a<15:30:22.200> local<15:30:22.320> area<15:30:22.560> network<15:30:22.916> by 15:30:23.510 --> 15:30:23.520 align:start position:0% extends a lan or a local area network by 15:30:23.520 --> 15:30:25.310 align:start position:0% extends a lan or a local area network by adding<15:30:23.880> the<15:30:24.000> ability<15:30:24.240> to<15:30:24.540> have<15:30:24.660> remote<15:30:24.900> users 15:30:25.310 --> 15:30:25.320 align:start position:0% adding the ability to have remote users 15:30:25.320 --> 15:30:28.070 align:start position:0% adding the ability to have remote users connect<15:30:25.560> to<15:30:25.800> it<15:30:25.916> the<15:30:26.520> way<15:30:26.640> it<15:30:26.756> does<15:30:26.936> this<15:30:27.180> is<15:30:27.660> by 15:30:28.070 --> 15:30:28.080 align:start position:0% connect to it the way it does this is by 15:30:28.080 --> 15:30:31.070 align:start position:0% connect to it the way it does this is by using<15:30:28.560> what's<15:30:28.916> called<15:30:29.220> tunneling<15:30:30.416> it 15:30:31.070 --> 15:30:31.080 align:start position:0% using what's called tunneling it 15:30:31.080 --> 15:30:35.086 align:start position:0% using what's called tunneling it basically<15:30:31.500> creates<15:30:32.220> a<15:30:32.580> tunnel<15:30:33.020> in<15:30:34.020> a<15:30:34.560> through 15:30:35.086 --> 15:30:35.096 align:start position:0% basically creates a tunnel in a through 15:30:35.096 --> 15:30:38.150 align:start position:0% basically creates a tunnel in a through the<15:30:35.640> wide<15:30:36.000> area<15:30:36.180> network 15:30:38.150 --> 15:30:38.160 align:start position:0% the wide area network 15:30:38.160 --> 15:30:39.406 align:start position:0% the wide area network the<15:30:38.580> internet 15:30:39.406 --> 15:30:39.416 align:start position:0% the internet 15:30:39.416 --> 15:30:41.926 align:start position:0% the internet that<15:30:39.956> then<15:30:40.200> I<15:30:40.616> can<15:30:40.800> connect<15:30:41.040> to<15:30:41.520> and<15:30:41.756> through 15:30:41.926 --> 15:30:41.936 align:start position:0% that then I can connect to and through 15:30:41.936 --> 15:30:45.470 align:start position:0% that then I can connect to and through so<15:30:42.900> all<15:30:43.560> of<15:30:43.740> my<15:30:43.980> data<15:30:44.340> is<15:30:44.700> traveling<15:30:45.240> through 15:30:45.470 --> 15:30:45.480 align:start position:0% so all of my data is traveling through 15:30:45.480 --> 15:30:48.650 align:start position:0% so all of my data is traveling through this<15:30:45.720> tunnel<15:30:46.140> between<15:30:46.800> the<15:30:47.400> server<15:30:47.756> or<15:30:48.300> the 15:30:48.650 --> 15:30:48.660 align:start position:0% this tunnel between the server or the 15:30:48.660 --> 15:30:50.946 align:start position:0% this tunnel between the server or the corporate<15:30:49.020> office<15:30:49.200> and<15:30:50.040> the<15:30:50.220> client<15:30:50.456> computer 15:30:50.946 --> 15:30:50.956 align:start position:0% corporate office and the client computer 15:30:50.956 --> 15:30:53.630 align:start position:0% corporate office and the client computer this<15:30:51.956> way<15:30:52.080> I<15:30:52.380> can<15:30:52.500> make<15:30:52.680> sure<15:30:52.916> that<15:30:53.160> no<15:30:53.456> one 15:30:53.630 --> 15:30:53.640 align:start position:0% this way I can make sure that no one 15:30:53.640 --> 15:30:55.790 align:start position:0% this way I can make sure that no one outside<15:30:54.000> the<15:30:54.360> tunnel<15:30:54.720> or<15:30:55.080> anyone<15:30:55.380> else<15:30:55.500> on<15:30:55.680> the 15:30:55.790 --> 15:30:55.800 align:start position:0% outside the tunnel or anyone else on the 15:30:55.800 --> 15:30:58.070 align:start position:0% outside the tunnel or anyone else on the network<15:30:55.980> can<15:30:56.640> get<15:30:56.880> in<15:30:57.060> and<15:30:57.540> I<15:30:57.660> can<15:30:57.776> be<15:30:57.900> sure 15:30:58.070 --> 15:30:58.080 align:start position:0% network can get in and I can be sure 15:30:58.080 --> 15:31:00.766 align:start position:0% network can get in and I can be sure that<15:30:58.320> all<15:30:58.436> of<15:30:58.560> my<15:30:58.740> data<15:30:59.096> is<15:30:59.276> kept<15:30:59.640> secure<15:31:00.060> this 15:31:00.766 --> 15:31:00.776 align:start position:0% that all of my data is kept secure this 15:31:00.776 --> 15:31:03.230 align:start position:0% that all of my data is kept secure this is<15:31:00.900> why<15:31:01.140> it's<15:31:01.380> called<15:31:01.616> a<15:31:02.220> virtual 15:31:03.230 --> 15:31:03.240 align:start position:0% is why it's called a virtual 15:31:03.240 --> 15:31:06.106 align:start position:0% is why it's called a virtual private<15:31:04.080> Network<15:31:04.560> it's<15:31:05.096> virtual<15:31:05.520> it's<15:31:05.880> not 15:31:06.106 --> 15:31:06.116 align:start position:0% private Network it's virtual it's not 15:31:06.116 --> 15:31:08.330 align:start position:0% private Network it's virtual it's not real<15:31:06.300> it's<15:31:06.540> not<15:31:06.776> physical<15:31:07.020> it's<15:31:07.980> definitely 15:31:08.330 --> 15:31:08.340 align:start position:0% real it's not physical it's definitely 15:31:08.340 --> 15:31:10.190 align:start position:0% real it's not physical it's definitely private<15:31:08.820> because<15:31:09.060> the<15:31:09.360> tunnel<15:31:09.660> makes<15:31:09.840> sure<15:31:10.020> to 15:31:10.190 --> 15:31:10.200 align:start position:0% private because the tunnel makes sure to 15:31:10.200 --> 15:31:12.350 align:start position:0% private because the tunnel makes sure to keep<15:31:10.380> everything<15:31:10.616> out<15:31:11.340> now<15:31:11.756> the<15:31:11.880> next<15:31:12.000> term<15:31:12.180> we 15:31:12.350 --> 15:31:12.360 align:start position:0% keep everything out now the next term we 15:31:12.360 --> 15:31:14.530 align:start position:0% keep everything out now the next term we want<15:31:12.480> to<15:31:12.596> talk<15:31:12.720> about<15:31:12.840> is<15:31:13.256> called<15:31:13.560> radius 15:31:14.530 --> 15:31:14.540 align:start position:0% want to talk about is called radius 15:31:14.540 --> 15:31:17.570 align:start position:0% want to talk about is called radius radius<15:31:15.540> by<15:31:15.840> the<15:31:16.020> way<15:31:16.140> stands<15:31:16.916> for<15:31:17.096> remote 15:31:17.570 --> 15:31:17.580 align:start position:0% radius by the way stands for remote 15:31:17.580 --> 15:31:21.586 align:start position:0% radius by the way stands for remote authentication<15:31:18.560> dial<15:31:19.560> in<15:31:20.040> user<15:31:20.700> service<15:31:20.880> I'm 15:31:21.586 --> 15:31:21.596 align:start position:0% authentication dial in user service I'm 15:31:21.596 --> 15:31:24.470 align:start position:0% authentication dial in user service I'm going<15:31:21.776> to<15:31:21.840> write<15:31:22.020> that<15:31:22.200> out<15:31:22.380> here<15:31:22.680> remote 15:31:24.470 --> 15:31:24.480 align:start position:0% going to write that out here remote 15:31:24.480 --> 15:31:28.130 align:start position:0% going to write that out here remote Authentication 15:31:28.130 --> 15:31:28.140 align:start position:0% 15:31:28.140 --> 15:31:30.050 align:start position:0% dial 15:31:30.050 --> 15:31:30.060 align:start position:0% dial 15:31:30.060 --> 15:31:33.890 align:start position:0% dial in 15:31:33.890 --> 15:31:33.900 align:start position:0% 15:31:33.900 --> 15:31:37.130 align:start position:0% U-verse<15:31:34.800> user<15:31:35.340> service<15:31:35.640> now<15:31:36.540> if<15:31:36.776> you<15:31:36.900> notice 15:31:37.130 --> 15:31:37.140 align:start position:0% U-verse user service now if you notice 15:31:37.140 --> 15:31:40.310 align:start position:0% U-verse user service now if you notice there's<15:31:37.380> a<15:31:37.560> dial<15:31:37.740> in<15:31:38.040> well<15:31:38.880> remote<15:31:39.660> can 15:31:40.310 --> 15:31:40.320 align:start position:0% there's a dial in well remote can 15:31:40.320 --> 15:31:42.106 align:start position:0% there's a dial in well remote can actually<15:31:40.560> be<15:31:40.916> uh 15:31:42.106 --> 15:31:42.116 align:start position:0% actually be uh 15:31:42.116 --> 15:31:44.570 align:start position:0% actually be uh dialing<15:31:42.956> in<15:31:43.080> using<15:31:43.436> a<15:31:43.560> modem<15:31:43.860> we<15:31:44.276> don't<15:31:44.400> use 15:31:44.570 --> 15:31:44.580 align:start position:0% dialing in using a modem we don't use 15:31:44.580 --> 15:31:47.330 align:start position:0% dialing in using a modem we don't use that<15:31:44.820> much<15:31:45.000> anymore<15:31:45.300> but<15:31:46.080> this<15:31:46.320> is<15:31:46.616> an<15:31:46.916> older 15:31:47.330 --> 15:31:47.340 align:start position:0% that much anymore but this is an older 15:31:47.340 --> 15:31:49.730 align:start position:0% that much anymore but this is an older service<15:31:47.640> what<15:31:48.540> this<15:31:48.660> does<15:31:48.900> is<15:31:49.080> it<15:31:49.200> allows<15:31:49.616> us 15:31:49.730 --> 15:31:49.740 align:start position:0% service what this does is it allows us 15:31:49.740 --> 15:31:52.070 align:start position:0% service what this does is it allows us to<15:31:50.040> have<15:31:50.276> centralized<15:31:51.180> authorization 15:31:52.070 --> 15:31:52.080 align:start position:0% to have centralized authorization 15:31:52.080 --> 15:31:55.130 align:start position:0% to have centralized authorization authentication<15:31:53.116> and<15:31:54.116> accounting<15:31:54.840> management 15:31:55.130 --> 15:31:55.140 align:start position:0% authentication and accounting management 15:31:55.140 --> 15:31:57.710 align:start position:0% authentication and accounting management for<15:31:55.800> computers<15:31:56.220> and<15:31:56.400> users<15:31:56.756> on<15:31:57.300> a<15:31:57.596> remote 15:31:57.710 --> 15:31:57.720 align:start position:0% for computers and users on a remote 15:31:57.720 --> 15:31:58.790 align:start position:0% for computers and users on a remote Network 15:31:58.790 --> 15:31:58.800 align:start position:0% Network 15:31:58.800 --> 15:32:01.670 align:start position:0% Network in<15:31:59.160> other<15:31:59.276> words<15:31:59.456> it<15:32:00.060> allows<15:32:00.416> me<15:32:00.540> to<15:32:00.840> have<15:32:01.020> one 15:32:01.670 --> 15:32:01.680 align:start position:0% in other words it allows me to have one 15:32:01.680 --> 15:32:03.586 align:start position:0% in other words it allows me to have one server<15:32:02.096> that's<15:32:02.580> going<15:32:02.756> to<15:32:02.880> be<15:32:03.000> responsible 15:32:03.586 --> 15:32:03.596 align:start position:0% server that's going to be responsible 15:32:03.596 --> 15:32:05.630 align:start position:0% server that's going to be responsible and<15:32:03.840> we're<15:32:04.020> going<15:32:04.140> to<15:32:04.200> call<15:32:04.380> this<15:32:04.616> the<15:32:05.040> radius 15:32:05.630 --> 15:32:05.640 align:start position:0% and we're going to call this the radius 15:32:05.640 --> 15:32:07.010 align:start position:0% and we're going to call this the radius server 15:32:07.010 --> 15:32:07.020 align:start position:0% server 15:32:07.020 --> 15:32:09.350 align:start position:0% server that's<15:32:07.560> responsible<15:32:08.096> for<15:32:08.400> making<15:32:08.580> sure<15:32:08.880> once 15:32:09.350 --> 15:32:09.360 align:start position:0% that's responsible for making sure once 15:32:09.360 --> 15:32:11.690 align:start position:0% that's responsible for making sure once a<15:32:09.480> VPN<15:32:09.900> is<15:32:10.140> established 15:32:11.690 --> 15:32:11.700 align:start position:0% a VPN is established 15:32:11.700 --> 15:32:13.606 align:start position:0% a VPN is established that<15:32:12.180> the<15:32:12.360> person<15:32:12.480> on<15:32:12.776> the<15:32:12.900> other<15:32:13.020> end<15:32:13.256> is 15:32:13.606 --> 15:32:13.616 align:start position:0% that the person on the other end is 15:32:13.616 --> 15:32:15.050 align:start position:0% that the person on the other end is actually<15:32:13.800> someone<15:32:14.160> who<15:32:14.580> should<15:32:14.820> be 15:32:15.050 --> 15:32:15.060 align:start position:0% actually someone who should be 15:32:15.060 --> 15:32:17.210 align:start position:0% actually someone who should be connecting<15:32:15.540> to<15:32:15.720> my<15:32:15.900> network<15:32:16.080> remember<15:32:16.860> I 15:32:17.210 --> 15:32:17.220 align:start position:0% connecting to my network remember I 15:32:17.220 --> 15:32:19.010 align:start position:0% connecting to my network remember I don't<15:32:17.400> want<15:32:17.520> to<15:32:17.640> just<15:32:17.700> let<15:32:17.880> anyone<15:32:18.360> connect<15:32:18.596> I 15:32:19.010 --> 15:32:19.020 align:start position:0% don't want to just let anyone connect I 15:32:19.020 --> 15:32:20.150 align:start position:0% don't want to just let anyone connect I want<15:32:19.140> to<15:32:19.256> make<15:32:19.380> sure<15:32:19.616> the<15:32:19.800> person<15:32:19.980> who 15:32:20.150 --> 15:32:20.160 align:start position:0% want to make sure the person who 15:32:20.160 --> 15:32:21.530 align:start position:0% want to make sure the person who connects<15:32:20.520> is<15:32:20.640> someone<15:32:20.820> who<15:32:21.000> belongs<15:32:21.300> to<15:32:21.416> my 15:32:21.530 --> 15:32:21.540 align:start position:0% connects is someone who belongs to my 15:32:21.540 --> 15:32:23.870 align:start position:0% connects is someone who belongs to my network<15:32:21.720> generally<15:32:22.616> what<15:32:22.740> we'll<15:32:22.916> do<15:32:23.160> is<15:32:23.640> we'll 15:32:23.870 --> 15:32:23.880 align:start position:0% network generally what we'll do is we'll 15:32:23.880 --> 15:32:26.330 align:start position:0% network generally what we'll do is we'll have<15:32:24.180> active<15:32:24.720> directories 15:32:26.330 --> 15:32:26.340 align:start position:0% have active directories 15:32:26.340 --> 15:32:30.766 align:start position:0% have active directories which<15:32:26.936> is<15:32:27.116> what<15:32:27.480> Microsoft<15:32:27.956> uses 15:32:30.766 --> 15:32:30.776 align:start position:0% 15:32:30.776 --> 15:32:32.810 align:start position:0% to<15:32:31.380> create<15:32:31.500> for<15:32:31.860> instance<15:32:32.040> usernames<15:32:32.700> and 15:32:32.810 --> 15:32:32.820 align:start position:0% to create for instance usernames and 15:32:32.820 --> 15:32:35.746 align:start position:0% to create for instance usernames and passwords<15:32:33.300> and<15:32:34.020> we'll<15:32:34.200> link<15:32:34.500> that<15:32:34.800> up<15:32:34.980> or<15:32:35.400> sync 15:32:35.746 --> 15:32:35.756 align:start position:0% passwords and we'll link that up or sync 15:32:35.756 --> 15:32:38.330 align:start position:0% passwords and we'll link that up or sync it<15:32:35.880> with<15:32:36.360> the<15:32:36.660> radius<15:32:36.956> server<15:32:37.380> sometimes<15:32:38.096> this 15:32:38.330 --> 15:32:38.340 align:start position:0% it with the radius server sometimes this 15:32:38.340 --> 15:32:41.210 align:start position:0% it with the radius server sometimes this is<15:32:38.456> done<15:32:38.640> on<15:32:39.116> a<15:32:39.360> separate<15:32:40.140> um<15:32:40.436> a<15:32:40.740> separate 15:32:41.210 --> 15:32:41.220 align:start position:0% is done on a separate um a separate 15:32:41.220 --> 15:32:43.246 align:start position:0% is done on a separate um a separate server<15:32:41.820> sometimes<15:32:42.240> it's<15:32:42.360> done<15:32:42.596> on<15:32:42.776> the<15:32:43.080> same 15:32:43.246 --> 15:32:43.256 align:start position:0% server sometimes it's done on the same 15:32:43.256 --> 15:32:45.830 align:start position:0% server sometimes it's done on the same server<15:32:43.680> either<15:32:44.220> way<15:32:44.456> once<15:32:45.240> you<15:32:45.360> connect<15:32:45.540> the 15:32:45.830 --> 15:32:45.840 align:start position:0% server either way once you connect the 15:32:45.840 --> 15:32:48.470 align:start position:0% server either way once you connect the VPN<15:32:46.320> the<15:32:46.740> VPN<15:32:47.160> then<15:32:47.520> goes<15:32:47.880> to<15:32:48.000> the<15:32:48.180> radius 15:32:48.470 --> 15:32:48.480 align:start position:0% VPN the VPN then goes to the radius 15:32:48.480 --> 15:32:50.630 align:start position:0% VPN the VPN then goes to the radius server<15:32:48.900> the<15:32:49.380> radius<15:32:49.680> server<15:32:50.040> checks<15:32:50.456> the 15:32:50.630 --> 15:32:50.640 align:start position:0% server the radius server checks the 15:32:50.640 --> 15:32:52.606 align:start position:0% server the radius server checks the active<15:32:50.880> directory<15:32:51.360> and<15:32:51.840> now<15:32:51.956> I<15:32:52.140> can<15:32:52.256> make<15:32:52.436> sure 15:32:52.606 --> 15:32:52.616 align:start position:0% active directory and now I can make sure 15:32:52.616 --> 15:32:53.926 align:start position:0% active directory and now I can make sure that<15:32:52.800> only<15:32:52.980> users<15:32:53.276> of<15:32:53.456> the<15:32:53.580> network<15:32:53.700> are 15:32:53.926 --> 15:32:53.936 align:start position:0% that only users of the network are 15:32:53.936 --> 15:32:55.370 align:start position:0% that only users of the network are allowed<15:32:54.240> onto<15:32:54.540> my<15:32:54.596> network 15:32:55.370 --> 15:32:55.380 align:start position:0% allowed onto my network 15:32:55.380 --> 15:32:57.650 align:start position:0% allowed onto my network finally<15:32:56.096> we<15:32:56.520> have<15:32:56.640> something<15:32:56.880> called<15:32:57.116> tacax 15:32:57.650 --> 15:32:57.660 align:start position:0% finally we have something called tacax 15:32:57.660 --> 15:32:59.870 align:start position:0% finally we have something called tacax or<15:32:58.020> terminal<15:32:58.436> Access<15:32:58.740> Controller<15:32:59.580> access 15:32:59.870 --> 15:32:59.880 align:start position:0% or terminal Access Controller access 15:32:59.880 --> 15:33:02.446 align:start position:0% or terminal Access Controller access control<15:33:00.416> system<15:33:00.900> it's<15:33:01.616> really<15:33:01.916> long<15:33:02.096> I'm<15:33:02.340> not 15:33:02.446 --> 15:33:02.456 align:start position:0% control system it's really long I'm not 15:33:02.456 --> 15:33:04.606 align:start position:0% control system it's really long I'm not going<15:33:02.580> to<15:33:02.700> write<15:33:02.820> it<15:33:03.000> out<15:33:03.180> this<15:33:03.776> is<15:33:03.900> actually<15:33:04.200> a 15:33:04.606 --> 15:33:04.616 align:start position:0% going to write it out this is actually a 15:33:04.616 --> 15:33:07.190 align:start position:0% going to write it out this is actually a replacement<15:33:04.880> for<15:33:05.880> radius<15:33:06.300> there<15:33:06.840> was<15:33:06.956> another 15:33:07.190 --> 15:33:07.200 align:start position:0% replacement for radius there was another 15:33:07.200 --> 15:33:09.650 align:start position:0% replacement for radius there was another replacement<15:33:08.160> for<15:33:08.640> radius<15:33:09.000> by<15:33:09.180> the<15:33:09.300> way<15:33:09.360> it<15:33:09.480> was 15:33:09.650 --> 15:33:09.660 align:start position:0% replacement for radius by the way it was 15:33:09.660 --> 15:33:11.570 align:start position:0% replacement for radius by the way it was called<15:33:09.840> diameter<15:33:10.616> and<15:33:10.916> if<15:33:11.096> you're<15:33:11.220> a<15:33:11.456> math 15:33:11.570 --> 15:33:11.580 align:start position:0% called diameter and if you're a math 15:33:11.580 --> 15:33:15.170 align:start position:0% called diameter and if you're a math whiz<15:33:12.000> you'll<15:33:12.360> notice<15:33:12.660> that<15:33:13.020> radius<15:33:13.520> is<15:33:14.520> half 15:33:15.170 --> 15:33:15.180 align:start position:0% whiz you'll notice that radius is half 15:33:15.180 --> 15:33:17.150 align:start position:0% whiz you'll notice that radius is half of<15:33:15.480> a<15:33:15.596> diameter<15:33:16.020> when<15:33:16.200> we<15:33:16.380> talk<15:33:16.500> about<15:33:16.616> circles 15:33:17.150 --> 15:33:17.160 align:start position:0% of a diameter when we talk about circles 15:33:17.160 --> 15:33:19.570 align:start position:0% of a diameter when we talk about circles but<15:33:17.880> diameter<15:33:18.480> wasn't<15:33:18.660> really<15:33:18.840> used<15:33:19.140> much 15:33:19.570 --> 15:33:19.580 align:start position:0% but diameter wasn't really used much 15:33:19.580 --> 15:33:21.710 align:start position:0% but diameter wasn't really used much tacx<15:33:20.580> on<15:33:20.756> the<15:33:20.820> other<15:33:20.880> hand<15:33:21.000> is<15:33:21.360> a<15:33:21.540> security 15:33:21.710 --> 15:33:21.720 align:start position:0% tacx on the other hand is a security 15:33:21.720 --> 15:33:24.050 align:start position:0% tacx on the other hand is a security protocol<15:33:22.320> it<15:33:23.040> allows<15:33:23.276> us<15:33:23.400> to<15:33:23.640> validate 15:33:24.050 --> 15:33:24.060 align:start position:0% protocol it allows us to validate 15:33:24.060 --> 15:33:25.370 align:start position:0% protocol it allows us to validate information<15:33:24.360> with<15:33:25.020> the<15:33:25.256> network 15:33:25.370 --> 15:33:25.380 align:start position:0% information with the network 15:33:25.380 --> 15:33:27.586 align:start position:0% information with the network administrator<15:33:26.160> or<15:33:26.400> server<15:33:26.820> and<15:33:27.416> the 15:33:27.586 --> 15:33:27.596 align:start position:0% administrator or server and the 15:33:27.596 --> 15:33:29.510 align:start position:0% administrator or server and the validation<15:33:28.020> is<15:33:28.380> tested<15:33:28.740> when<15:33:28.980> we<15:33:29.220> try<15:33:29.340> to 15:33:29.510 --> 15:33:29.520 align:start position:0% validation is tested when we try to 15:33:29.520 --> 15:33:31.490 align:start position:0% validation is tested when we try to connect<15:33:29.700> just<15:33:30.116> like<15:33:30.240> with<15:33:30.480> radius<15:33:30.840> of<15:33:31.380> course 15:33:31.490 --> 15:33:31.500 align:start position:0% connect just like with radius of course 15:33:31.500 --> 15:33:34.606 align:start position:0% connect just like with radius of course the<15:33:31.740> benefit<15:33:31.860> is<15:33:32.220> tacx<15:33:32.820> is<15:33:33.300> newer 15:33:34.606 --> 15:33:34.616 align:start position:0% the benefit is tacx is newer 15:33:34.616 --> 15:33:36.470 align:start position:0% the benefit is tacx is newer and 15:33:36.470 --> 15:33:36.480 align:start position:0% and 15:33:36.480 --> 15:33:40.310 align:start position:0% and more<15:33:37.140> secure<15:33:37.860> than<15:33:38.340> radius<15:33:38.820> so<15:33:39.660> it<15:33:40.020> basically 15:33:40.310 --> 15:33:40.320 align:start position:0% more secure than radius so it basically 15:33:40.320 --> 15:33:42.530 align:start position:0% more secure than radius so it basically does<15:33:40.500> the<15:33:40.800> same<15:33:40.916> thing<15:33:41.160> it's<15:33:41.700> just<15:33:41.936> a<15:33:42.360> little 15:33:42.530 --> 15:33:42.540 align:start position:0% does the same thing it's just a little 15:33:42.540 --> 15:33:44.446 align:start position:0% does the same thing it's just a little more<15:33:43.020> powerful 15:33:44.446 --> 15:33:44.456 align:start position:0% more powerful 15:33:44.456 --> 15:33:46.606 align:start position:0% more powerful all<15:33:44.936> right<15:33:45.060> so<15:33:45.596> this<15:33:45.720> was<15:33:45.900> short<15:33:46.080> but<15:33:46.380> I<15:33:46.500> just 15:33:46.606 --> 15:33:46.616 align:start position:0% all right so this was short but I just 15:33:46.616 --> 15:33:48.050 align:start position:0% all right so this was short but I just wanted<15:33:46.740> to<15:33:46.916> give<15:33:47.040> us<15:33:47.160> an<15:33:47.340> overview<15:33:47.756> of<15:33:47.880> remote 15:33:48.050 --> 15:33:48.060 align:start position:0% wanted to give us an overview of remote 15:33:48.060 --> 15:33:49.550 align:start position:0% wanted to give us an overview of remote networking<15:33:48.660> and<15:33:48.900> we're<15:33:49.020> going<15:33:49.140> to<15:33:49.200> talk<15:33:49.380> more 15:33:49.550 --> 15:33:49.560 align:start position:0% networking and we're going to talk more 15:33:49.560 --> 15:33:51.406 align:start position:0% networking and we're going to talk more about<15:33:49.740> that<15:33:49.916> in<15:33:50.096> the<15:33:50.220> coming<15:33:50.340> modules<15:33:50.880> so<15:33:51.240> we 15:33:51.406 --> 15:33:51.416 align:start position:0% about that in the coming modules so we 15:33:51.416 --> 15:33:52.906 align:start position:0% about that in the coming modules so we talked<15:33:51.596> about<15:33:51.660> remote<15:33:51.956> networking<15:33:52.500> what<15:33:52.740> it 15:33:52.906 --> 15:33:52.916 align:start position:0% talked about remote networking what it 15:33:52.916 --> 15:33:55.670 align:start position:0% talked about remote networking what it is<15:33:53.096> allowing<15:33:53.880> us 15:33:55.670 --> 15:33:55.680 align:start position:0% is allowing us 15:33:55.680 --> 15:33:58.190 align:start position:0% is allowing us to<15:33:56.220> access<15:33:56.456> a<15:33:57.240> lan 15:33:58.190 --> 15:33:58.200 align:start position:0% to access a lan 15:33:58.200 --> 15:34:00.170 align:start position:0% to access a lan basically<15:33:58.980> through 15:34:00.170 --> 15:34:00.180 align:start position:0% basically through 15:34:00.180 --> 15:34:02.690 align:start position:0% basically through a<15:34:00.660> Wham<15:34:01.020> whether<15:34:01.680> that<15:34:01.860> Wan<15:34:02.220> is<15:34:02.456> the<15:34:02.580> internet 15:34:02.690 --> 15:34:02.700 align:start position:0% a Wham whether that Wan is the internet 15:34:02.700 --> 15:34:05.150 align:start position:0% a Wham whether that Wan is the internet or<15:34:03.060> public<15:34:03.360> switch<15:34:03.596> telephone<15:34:03.840> Network<15:34:04.256> it 15:34:05.150 --> 15:34:05.160 align:start position:0% or public switch telephone Network it 15:34:05.160 --> 15:34:10.606 align:start position:0% or public switch telephone Network it also<15:34:05.400> allows<15:34:05.700> us<15:34:05.820> to<15:34:06.060> access<15:34:06.240> the<15:34:06.720> LAN 15:34:10.606 --> 15:34:10.616 align:start position:0% 15:34:10.616 --> 15:34:14.210 align:start position:0% from<15:34:11.520> a<15:34:11.700> different 15:34:14.210 --> 15:34:14.220 align:start position:0% 15:34:14.220 --> 15:34:16.426 align:start position:0% physical 15:34:16.426 --> 15:34:16.436 align:start position:0% physical 15:34:16.436 --> 15:34:19.550 align:start position:0% physical location 15:34:19.550 --> 15:34:19.560 align:start position:0% 15:34:19.560 --> 15:34:22.070 align:start position:0% we<15:34:19.980> can<15:34:20.096> also<15:34:20.400> identify<15:34:21.300> three<15:34:21.776> remote 15:34:22.070 --> 15:34:22.080 align:start position:0% we can also identify three remote 15:34:22.080 --> 15:34:25.490 align:start position:0% we can also identify three remote networking<15:34:22.616> Technologies<15:34:23.160> the<15:34:23.880> first 15:34:25.490 --> 15:34:25.500 align:start position:0% networking Technologies the first 15:34:25.500 --> 15:34:28.490 align:start position:0% networking Technologies the first virtual<15:34:26.276> private 15:34:28.490 --> 15:34:28.500 align:start position:0% virtual private 15:34:28.500 --> 15:34:31.426 align:start position:0% virtual private Network 15:34:31.426 --> 15:34:31.436 align:start position:0% 15:34:31.436 --> 15:34:33.530 align:start position:0% creates<15:34:32.040> a<15:34:32.456> tunnel 15:34:33.530 --> 15:34:33.540 align:start position:0% creates a tunnel 15:34:33.540 --> 15:34:37.550 align:start position:0% creates a tunnel over<15:34:33.840> the<15:34:34.140> win 15:34:37.550 --> 15:34:37.560 align:start position:0% 15:34:37.560 --> 15:34:39.230 align:start position:0% through<15:34:37.916> which<15:34:38.096> we<15:34:38.456> create<15:34:38.640> a<15:34:38.936> virtual 15:34:39.230 --> 15:34:39.240 align:start position:0% through which we create a virtual 15:34:39.240 --> 15:34:41.810 align:start position:0% through which we create a virtual Network<15:34:39.540> that<15:34:39.956> is<15:34:40.080> also<15:34:40.380> private<15:34:40.740> we<15:34:41.520> also 15:34:41.810 --> 15:34:41.820 align:start position:0% Network that is also private we also 15:34:41.820 --> 15:34:44.446 align:start position:0% Network that is also private we also talked<15:34:42.060> about<15:34:42.180> radius<15:34:42.840> and<15:34:43.200> tachs<15:34:43.860> both<15:34:44.276> of 15:34:44.446 --> 15:34:44.456 align:start position:0% talked about radius and tachs both of 15:34:44.456 --> 15:34:47.570 align:start position:0% talked about radius and tachs both of these<15:34:44.756> allow<15:34:45.596> for<15:34:45.776> authentication<15:34:46.500> so<15:34:47.276> we<15:34:47.456> can 15:34:47.570 --> 15:34:47.580 align:start position:0% these allow for authentication so we can 15:34:47.580 --> 15:34:49.490 align:start position:0% these allow for authentication so we can make<15:34:47.756> sure<15:34:47.936> the<15:34:48.240> person<15:34:48.416> who<15:34:48.776> establishes<15:34:49.320> the 15:34:49.490 --> 15:34:49.500 align:start position:0% make sure the person who establishes the 15:34:49.500 --> 15:34:54.950 align:start position:0% make sure the person who establishes the VPN<15:34:49.916> is<15:34:50.220> actually<15:34:50.400> allowed<15:34:50.820> on<15:34:50.936> our<15:34:51.116> Network 15:34:54.950 --> 15:34:54.960 align:start position:0% 15:34:54.960 --> 15:35:03.490 align:start position:0% [Music] 15:35:03.490 --> 15:35:03.500 align:start position:0% [Music] 15:35:03.500 --> 15:35:15.170 align:start position:0% [Music] thank<15:35:04.500> you 15:35:15.170 --> 15:35:15.180 align:start position:0% 15:35:15.180 --> 15:35:18.106 align:start position:0% remote<15:35:15.720> access<15:35:16.276> remote<15:35:17.276> access<15:35:17.640> and 15:35:18.106 --> 15:35:18.116 align:start position:0% remote access remote access and 15:35:18.116 --> 15:35:21.586 align:start position:0% remote access remote access and implementation 15:35:21.586 --> 15:35:21.596 align:start position:0% 15:35:21.596 --> 15:35:23.266 align:start position:0% we've<15:35:22.020> now<15:35:22.140> talked<15:35:22.436> about<15:35:22.560> some<15:35:22.800> of<15:35:22.916> the<15:35:22.980> basic 15:35:23.266 --> 15:35:23.276 align:start position:0% we've now talked about some of the basic 15:35:23.276 --> 15:35:24.586 align:start position:0% we've now talked about some of the basic information<15:35:23.456> when<15:35:23.880> it<15:35:24.060> comes<15:35:24.300> to<15:35:24.480> remote 15:35:24.586 --> 15:35:24.596 align:start position:0% information when it comes to remote 15:35:24.596 --> 15:35:27.350 align:start position:0% information when it comes to remote networking<15:35:25.320> and<15:35:25.800> with<15:35:26.040> that<15:35:26.340> base<15:35:26.820> knowledge 15:35:27.350 --> 15:35:27.360 align:start position:0% networking and with that base knowledge 15:35:27.360 --> 15:35:28.970 align:start position:0% networking and with that base knowledge it's<15:35:27.596> going<15:35:27.840> to<15:35:27.840> come<15:35:27.956> into<15:35:28.140> play<15:35:28.380> in<15:35:28.740> this 15:35:28.970 --> 15:35:28.980 align:start position:0% it's going to come into play in this 15:35:28.980 --> 15:35:31.010 align:start position:0% it's going to come into play in this module<15:35:29.340> we're<15:35:29.580> going<15:35:29.700> to<15:35:29.820> talk<15:35:30.060> more<15:35:30.480> about 15:35:31.010 --> 15:35:31.020 align:start position:0% module we're going to talk more about 15:35:31.020 --> 15:35:33.170 align:start position:0% module we're going to talk more about remote<15:35:31.380> access<15:35:31.740> and<15:35:32.160> how<15:35:32.400> to<15:35:32.580> implement<15:35:32.936> it 15:35:33.170 --> 15:35:33.180 align:start position:0% remote access and how to implement it 15:35:33.180 --> 15:35:34.426 align:start position:0% remote access and how to implement it some<15:35:33.660> of<15:35:33.776> the<15:35:33.840> stuff<15:35:33.956> we're<15:35:34.140> going<15:35:34.256> to<15:35:34.320> talk 15:35:34.426 --> 15:35:34.436 align:start position:0% some of the stuff we're going to talk 15:35:34.436 --> 15:35:36.290 align:start position:0% some of the stuff we're going to talk about<15:35:34.560> is<15:35:34.916> overview<15:35:35.400> and<15:35:35.756> some<15:35:35.936> of<15:35:36.060> it<15:35:36.180> is 15:35:36.290 --> 15:35:36.300 align:start position:0% about is overview and some of it is 15:35:36.300 --> 15:35:37.970 align:start position:0% about is overview and some of it is still<15:35:36.480> pretty<15:35:36.720> basic<15:35:37.200> again<15:35:37.680> you're<15:35:37.860> not 15:35:37.970 --> 15:35:37.980 align:start position:0% still pretty basic again you're not 15:35:37.980 --> 15:35:39.766 align:start position:0% still pretty basic again you're not going<15:35:38.160> to<15:35:38.160> take<15:35:38.520> this<15:35:38.820> information<15:35:39.000> and<15:35:39.540> just 15:35:39.766 --> 15:35:39.776 align:start position:0% going to take this information and just 15:35:39.776 --> 15:35:42.290 align:start position:0% going to take this information and just Implement<15:35:40.320> a<15:35:40.680> network<15:35:40.860> or<15:35:41.276> remote<15:35:41.580> access<15:35:41.880> to 15:35:42.290 --> 15:35:42.300 align:start position:0% Implement a network or remote access to 15:35:42.300 --> 15:35:44.890 align:start position:0% Implement a network or remote access to a<15:35:42.480> network<15:35:42.596> that<15:35:43.256> would<15:35:43.436> take<15:35:43.560> a<15:35:43.740> little<15:35:43.860> more 15:35:44.890 --> 15:35:44.900 align:start position:0% a network that would take a little more 15:35:44.900 --> 15:35:48.350 align:start position:0% a network that would take a little more leg<15:35:45.900> work<15:35:46.140> and<15:35:46.436> a<15:35:46.616> little<15:35:46.680> more<15:35:46.800> research<15:35:47.640> what 15:35:48.350 --> 15:35:48.360 align:start position:0% leg work and a little more research what 15:35:48.360 --> 15:35:50.086 align:start position:0% leg work and a little more research what this<15:35:48.540> is<15:35:48.660> really<15:35:48.840> giving<15:35:49.080> us<15:35:49.320> is<15:35:49.560> an<15:35:49.800> overview 15:35:50.086 --> 15:35:50.096 align:start position:0% this is really giving us is an overview 15:35:50.096 --> 15:35:51.710 align:start position:0% this is really giving us is an overview of<15:35:50.400> how<15:35:50.580> it<15:35:50.700> all<15:35:50.880> functions<15:35:51.300> and<15:35:51.480> what<15:35:51.596> you 15:35:51.710 --> 15:35:51.720 align:start position:0% of how it all functions and what you 15:35:51.720 --> 15:35:54.050 align:start position:0% of how it all functions and what you need<15:35:51.840> to<15:35:51.956> know<15:35:52.080> for<15:35:52.256> the<15:35:52.436> exam<15:35:52.740> so<15:35:53.640> we're<15:35:53.880> going 15:35:54.050 --> 15:35:54.060 align:start position:0% need to know for the exam so we're going 15:35:54.060 --> 15:35:56.086 align:start position:0% need to know for the exam so we're going to<15:35:54.180> talk<15:35:54.300> about<15:35:54.480> remote<15:35:54.900> access<15:35:55.256> as<15:35:55.680> opposed 15:35:56.086 --> 15:35:56.096 align:start position:0% to talk about remote access as opposed 15:35:56.096 --> 15:35:58.010 align:start position:0% to talk about remote access as opposed to remote<15:35:56.340> networking<15:35:57.180> remember<15:35:57.596> remote 15:35:58.010 --> 15:35:58.020 align:start position:0% to remote networking remember remote 15:35:58.020 --> 15:35:59.926 align:start position:0% to remote networking remember remote networking<15:35:58.740> is<15:35:59.160> sort<15:35:59.340> of<15:35:59.456> the<15:35:59.580> act<15:35:59.756> of 15:35:59.926 --> 15:35:59.936 align:start position:0% networking is sort of the act of 15:35:59.936 --> 15:36:02.810 align:start position:0% networking is sort of the act of creating<15:36:00.360> the<15:36:00.660> network<15:36:00.840> to<15:36:01.560> allow<15:36:02.456> remote 15:36:02.810 --> 15:36:02.820 align:start position:0% creating the network to allow remote 15:36:02.820 --> 15:36:04.790 align:start position:0% creating the network to allow remote access<15:36:03.240> so<15:36:04.020> we're<15:36:04.140> going<15:36:04.256> to<15:36:04.320> talk<15:36:04.436> about<15:36:04.560> what 15:36:04.790 --> 15:36:04.800 align:start position:0% access so we're going to talk about what 15:36:04.800 --> 15:36:08.266 align:start position:0% access so we're going to talk about what it<15:36:04.980> is<15:36:05.116> what<15:36:06.116> it<15:36:06.240> does<15:36:06.480> and<15:36:07.436> the<15:36:07.680> benefits<15:36:08.096> for 15:36:08.266 --> 15:36:08.276 align:start position:0% it is what it does and the benefits for 15:36:08.276 --> 15:36:10.550 align:start position:0% it is what it does and the benefits for it<15:36:08.400> we're<15:36:08.880> then<15:36:09.060> going<15:36:09.300> to<15:36:09.360> discuss<15:36:09.840> the<15:36:10.320> steps 15:36:10.550 --> 15:36:10.560 align:start position:0% it we're then going to discuss the steps 15:36:10.560 --> 15:36:13.850 align:start position:0% it we're then going to discuss the steps of<15:36:10.800> implementing<15:36:11.700> a<15:36:12.240> remote<15:36:12.360> access<15:36:12.900> policy 15:36:13.850 --> 15:36:13.860 align:start position:0% of implementing a remote access policy 15:36:13.860 --> 15:36:16.730 align:start position:0% of implementing a remote access policy or<15:36:14.580> remote<15:36:14.820> access<15:36:15.180> Technologies 15:36:16.730 --> 15:36:16.740 align:start position:0% or remote access Technologies 15:36:16.740 --> 15:36:19.970 align:start position:0% or remote access Technologies so<15:36:17.400> remote<15:36:17.936> access<15:36:18.360> is<15:36:18.840> a<15:36:19.080> practice<15:36:19.256> that's 15:36:19.970 --> 15:36:19.980 align:start position:0% so remote access is a practice that's 15:36:19.980 --> 15:36:21.766 align:start position:0% so remote access is a practice that's extremely<15:36:20.640> useful<15:36:21.000> and<15:36:21.180> becoming<15:36:21.540> more<15:36:21.720> and 15:36:21.766 --> 15:36:21.776 align:start position:0% extremely useful and becoming more and 15:36:21.776 --> 15:36:23.870 align:start position:0% extremely useful and becoming more and more<15:36:22.020> popular<15:36:22.256> constantly<15:36:23.096> All<15:36:23.456> Around<15:36:23.580> the 15:36:23.870 --> 15:36:23.880 align:start position:0% more popular constantly All Around the 15:36:23.880 --> 15:36:27.050 align:start position:0% more popular constantly All Around the World<15:36:24.000> in<15:36:24.596> every<15:36:24.840> I.T<15:36:25.200> situation<15:36:25.740> as<15:36:26.700> we've 15:36:27.050 --> 15:36:27.060 align:start position:0% World in every I.T situation as we've 15:36:27.060 --> 15:36:28.606 align:start position:0% World in every I.T situation as we've mentioned<15:36:27.416> it's<15:36:27.776> a<15:36:27.956> way<15:36:28.080> for<15:36:28.200> someone<15:36:28.380> to 15:36:28.606 --> 15:36:28.616 align:start position:0% mentioned it's a way for someone to 15:36:28.616 --> 15:36:30.350 align:start position:0% mentioned it's a way for someone to connect<15:36:28.740> to<15:36:29.040> a<15:36:29.220> corporate<15:36:29.520> land<15:36:29.700> from<15:36:30.000> outs 15:36:30.350 --> 15:36:30.360 align:start position:0% connect to a corporate land from outs 15:36:30.360 --> 15:36:32.446 align:start position:0% connect to a corporate land from outs from<15:36:30.540> an<15:36:30.596> outside<15:36:30.720> location<15:36:31.140> it's<15:36:32.096> not<15:36:32.276> always 15:36:32.446 --> 15:36:32.456 align:start position:0% from an outside location it's not always 15:36:32.456 --> 15:36:34.370 align:start position:0% from an outside location it's not always used<15:36:32.756> in<15:36:32.936> a<15:36:33.060> corporate<15:36:33.360> setting<15:36:33.776> but<15:36:34.140> for<15:36:34.256> the 15:36:34.370 --> 15:36:34.380 align:start position:0% used in a corporate setting but for the 15:36:34.380 --> 15:36:36.830 align:start position:0% used in a corporate setting but for the most<15:36:34.500> part<15:36:34.740> that<15:36:35.040> is<15:36:35.160> its<15:36:35.520> main<15:36:35.580> use<15:36:35.840> however 15:36:36.830 --> 15:36:36.840 align:start position:0% most part that is its main use however 15:36:36.840 --> 15:36:38.330 align:start position:0% most part that is its main use however for<15:36:37.200> instance<15:36:37.436> perhaps<15:36:37.800> you<15:36:37.916> wanted<15:36:38.096> to 15:36:38.330 --> 15:36:38.340 align:start position:0% for instance perhaps you wanted to 15:36:38.340 --> 15:36:41.150 align:start position:0% for instance perhaps you wanted to remote<15:36:38.456> into<15:36:38.880> your<15:36:39.360> home<15:36:40.020> network<15:36:40.436> or<15:36:40.860> a<15:36:40.980> home 15:36:41.150 --> 15:36:41.160 align:start position:0% remote into your home network or a home 15:36:41.160 --> 15:36:43.310 align:start position:0% remote into your home network or a home computer<15:36:41.400> from<15:36:42.060> the<15:36:42.240> office<15:36:42.416> or<15:36:43.020> you<15:36:43.200> wanted 15:36:43.310 --> 15:36:43.320 align:start position:0% computer from the office or you wanted 15:36:43.320 --> 15:36:46.070 align:start position:0% computer from the office or you wanted to<15:36:43.500> remote<15:36:43.616> in<15:36:43.980> from<15:36:44.340> outside<15:36:45.180> your<15:36:45.840> home 15:36:46.070 --> 15:36:46.080 align:start position:0% to remote in from outside your home 15:36:46.080 --> 15:36:47.630 align:start position:0% to remote in from outside your home these<15:36:46.616> are<15:36:46.680> things<15:36:46.800> you<15:36:46.980> could<15:36:47.096> set<15:36:47.276> up<15:36:47.456> as 15:36:47.630 --> 15:36:47.640 align:start position:0% these are things you could set up as 15:36:47.640 --> 15:36:48.350 align:start position:0% these are things you could set up as well 15:36:48.350 --> 15:36:48.360 align:start position:0% well 15:36:48.360 --> 15:36:50.390 align:start position:0% well with<15:36:48.776> remote<15:36:48.956> access<15:36:49.320> you<15:36:49.800> then<15:36:49.980> have<15:36:50.160> the 15:36:50.390 --> 15:36:50.400 align:start position:0% with remote access you then have the 15:36:50.400 --> 15:36:52.010 align:start position:0% with remote access you then have the ability<15:36:50.580> to<15:36:50.936> connect<15:36:51.060> to<15:36:51.300> a<15:36:51.480> physical<15:36:51.596> Network 15:36:52.010 --> 15:36:52.020 align:start position:0% ability to connect to a physical Network 15:36:52.020 --> 15:36:54.710 align:start position:0% ability to connect to a physical Network without<15:36:52.680> having<15:36:53.040> to<15:36:53.160> be<15:36:53.400> anywhere<15:36:54.060> near<15:36:54.480> the 15:36:54.710 --> 15:36:54.720 align:start position:0% without having to be anywhere near the 15:36:54.720 --> 15:36:56.266 align:start position:0% without having to be anywhere near the network<15:36:54.900> in<15:36:55.560> fact<15:36:55.740> you<15:36:55.860> could<15:36:55.980> be<15:36:56.096> on<15:36:56.160> the 15:36:56.266 --> 15:36:56.276 align:start position:0% network in fact you could be on the 15:36:56.276 --> 15:36:57.350 align:start position:0% network in fact you could be on the other<15:36:56.340> side<15:36:56.456> of<15:36:56.580> the<15:36:56.700> world<15:36:56.880> and<15:36:57.180> still 15:36:57.350 --> 15:36:57.360 align:start position:0% other side of the world and still 15:36:57.360 --> 15:36:58.906 align:start position:0% other side of the world and still connect<15:36:57.540> as<15:36:57.900> though<15:36:58.080> you're<15:36:58.320> sitting<15:36:58.616> at<15:36:58.740> a 15:36:58.906 --> 15:36:58.916 align:start position:0% connect as though you're sitting at a 15:36:58.916 --> 15:37:02.030 align:start position:0% connect as though you're sitting at a desktop<15:36:59.276> PC<15:36:59.880> on<15:37:00.300> your<15:37:00.416> land<15:37:00.596> now<15:37:01.500> you<15:37:01.916> can 15:37:02.030 --> 15:37:02.040 align:start position:0% desktop PC on your land now you can 15:37:02.040 --> 15:37:03.710 align:start position:0% desktop PC on your land now you can imagine<15:37:02.220> how<15:37:02.700> this<15:37:02.936> is<15:37:03.060> even<15:37:03.180> going<15:37:03.480> to<15:37:03.596> take 15:37:03.710 --> 15:37:03.720 align:start position:0% imagine how this is even going to take 15:37:03.720 --> 15:37:05.690 align:start position:0% imagine how this is even going to take it<15:37:03.900> to<15:37:04.020> another<15:37:04.200> step<15:37:04.616> where<15:37:05.160> we<15:37:05.340> could<15:37:05.520> start 15:37:05.690 --> 15:37:05.700 align:start position:0% it to another step where we could start 15:37:05.700 --> 15:37:09.350 align:start position:0% it to another step where we could start to<15:37:06.000> have<15:37:06.240> computers<15:37:06.956> that<15:37:07.616> are<15:37:07.800> on<15:37:08.096> a<15:37:08.580> lan<15:37:09.060> or<15:37:09.240> a 15:37:09.350 --> 15:37:09.360 align:start position:0% to have computers that are on a lan or a 15:37:09.360 --> 15:37:11.690 align:start position:0% to have computers that are on a lan or a land<15:37:09.540> that<15:37:09.900> we<15:37:10.020> don't<15:37:10.140> even<15:37:10.320> control<15:37:10.740> or<15:37:11.520> have 15:37:11.690 --> 15:37:11.700 align:start position:0% land that we don't even control or have 15:37:11.700 --> 15:37:14.030 align:start position:0% land that we don't even control or have any<15:37:11.936> physical<15:37:12.180> access<15:37:12.480> to<15:37:12.776> at<15:37:12.956> all<15:37:13.140> instead 15:37:14.030 --> 15:37:14.040 align:start position:0% any physical access to at all instead 15:37:14.040 --> 15:37:15.710 align:start position:0% any physical access to at all instead all<15:37:14.456> of<15:37:14.640> our<15:37:14.756> Computing<15:37:15.180> will<15:37:15.416> be<15:37:15.540> done 15:37:15.710 --> 15:37:15.720 align:start position:0% all of our Computing will be done 15:37:15.720 --> 15:37:17.810 align:start position:0% all of our Computing will be done remotely<15:37:16.436> this<15:37:17.040> is<15:37:17.160> already<15:37:17.340> coming<15:37:17.640> into 15:37:17.810 --> 15:37:17.820 align:start position:0% remotely this is already coming into 15:37:17.820 --> 15:37:19.790 align:start position:0% remotely this is already coming into play<15:37:18.060> when<15:37:18.300> we<15:37:18.480> talk<15:37:18.660> about<15:37:18.840> cloud<15:37:19.200> computing 15:37:19.790 --> 15:37:19.800 align:start position:0% play when we talk about cloud computing 15:37:19.800 --> 15:37:24.290 align:start position:0% play when we talk about cloud computing and<15:37:20.340> things<15:37:20.520> like<15:37:20.880> Amazon's<15:37:21.800> elastic<15:37:22.800> cloud 15:37:24.290 --> 15:37:24.300 align:start position:0% and things like Amazon's elastic cloud 15:37:24.300 --> 15:37:26.510 align:start position:0% and things like Amazon's elastic cloud which<15:37:24.660> allows<15:37:25.080> you<15:37:25.140> to<15:37:25.320> set<15:37:25.436> up<15:37:25.616> a<15:37:26.160> virtual 15:37:26.510 --> 15:37:26.520 align:start position:0% which allows you to set up a virtual 15:37:26.520 --> 15:37:29.086 align:start position:0% which allows you to set up a virtual computer<15:37:26.820> on<15:37:27.660> a<15:37:27.840> remote<15:37:27.956> system<15:37:28.436> and<15:37:28.980> then 15:37:29.086 --> 15:37:29.096 align:start position:0% computer on a remote system and then 15:37:29.096 --> 15:37:30.946 align:start position:0% computer on a remote system and then remote<15:37:29.340> into<15:37:29.700> it<15:37:30.060> and<15:37:30.180> through<15:37:30.416> remote<15:37:30.596> access 15:37:30.946 --> 15:37:30.956 align:start position:0% remote into it and through remote access 15:37:30.956 --> 15:37:33.230 align:start position:0% remote into it and through remote access and<15:37:31.616> connect<15:37:31.980> to<15:37:32.276> it<15:37:32.456> just<15:37:32.640> like<15:37:32.756> you<15:37:32.936> would<15:37:33.116> be 15:37:33.230 --> 15:37:33.240 align:start position:0% and connect to it just like you would be 15:37:33.240 --> 15:37:35.086 align:start position:0% and connect to it just like you would be connecting<15:37:33.596> to<15:37:33.900> the<15:37:34.380> computers<15:37:34.680> though<15:37:34.916> you 15:37:35.086 --> 15:37:35.096 align:start position:0% connecting to the computers though you 15:37:35.096 --> 15:37:36.286 align:start position:0% connecting to the computers though you were<15:37:35.220> sitting<15:37:35.456> in<15:37:35.580> front<15:37:35.700> of<15:37:35.820> an<15:37:36.060> actual 15:37:36.286 --> 15:37:36.296 align:start position:0% were sitting in front of an actual 15:37:36.296 --> 15:37:38.870 align:start position:0% were sitting in front of an actual computer<15:37:36.596> now<15:37:37.256> this<15:37:37.680> obviously<15:37:38.160> speaks<15:37:38.700> to 15:37:38.870 --> 15:37:38.880 align:start position:0% computer now this obviously speaks to 15:37:38.880 --> 15:37:42.230 align:start position:0% computer now this obviously speaks to not<15:37:39.596> only<15:37:39.776> a<15:37:40.380> greatly<15:37:40.980> reduct<15:37:41.400> reduced<15:37:42.000> amount 15:37:42.230 --> 15:37:42.240 align:start position:0% not only a greatly reduct reduced amount 15:37:42.240 --> 15:37:44.266 align:start position:0% not only a greatly reduct reduced amount of<15:37:42.360> cost<15:37:42.596> but<15:37:42.956> also<15:37:43.256> a<15:37:43.380> lot<15:37:43.500> more<15:37:43.616> flexibility 15:37:44.266 --> 15:37:44.276 align:start position:0% of cost but also a lot more flexibility 15:37:44.276 --> 15:37:47.086 align:start position:0% of cost but also a lot more flexibility because<15:37:45.180> now<15:37:45.776> I<15:37:46.256> can<15:37:46.380> set<15:37:46.616> up<15:37:46.740> a<15:37:46.916> computer 15:37:47.086 --> 15:37:47.096 align:start position:0% because now I can set up a computer 15:37:47.096 --> 15:37:49.670 align:start position:0% because now I can set up a computer anywhere<15:37:47.880> in<15:37:48.060> the<15:37:48.180> world<15:37:48.360> and<15:37:49.200> for<15:37:49.500> instance 15:37:49.670 --> 15:37:49.680 align:start position:0% anywhere in the world and for instance 15:37:49.680 --> 15:37:51.766 align:start position:0% anywhere in the world and for instance if<15:37:49.916> I<15:37:50.096> had<15:37:50.276> 20<15:37:50.520> computers<15:37:51.060> I<15:37:51.240> could<15:37:51.360> remotely 15:37:51.766 --> 15:37:51.776 align:start position:0% if I had 20 computers I could remotely 15:37:51.776 --> 15:37:54.606 align:start position:0% if I had 20 computers I could remotely access<15:37:52.080> them<15:37:52.500> and<15:37:52.916> I<15:37:53.040> would<15:37:53.160> only<15:37:53.340> need<15:37:53.700> one 15:37:54.606 --> 15:37:54.616 align:start position:0% access them and I would only need one 15:37:54.616 --> 15:37:57.470 align:start position:0% access them and I would only need one monitor<15:37:55.616> keyboard<15:37:56.160> and<15:37:56.700> mouse 15:37:57.470 --> 15:37:57.480 align:start position:0% monitor keyboard and mouse 15:37:57.480 --> 15:37:59.390 align:start position:0% monitor keyboard and mouse so<15:37:58.080> you<15:37:58.320> can<15:37:58.500> see<15:37:58.616> where<15:37:58.796> this<15:37:58.980> is<15:37:59.160> really 15:37:59.390 --> 15:37:59.400 align:start position:0% so you can see where this is really 15:37:59.400 --> 15:38:01.426 align:start position:0% so you can see where this is really going<15:37:59.580> to<15:37:59.700> come<15:37:59.820> into<15:38:00.060> major<15:38:00.416> play 15:38:01.426 --> 15:38:01.436 align:start position:0% going to come into major play 15:38:01.436 --> 15:38:03.050 align:start position:0% going to come into major play now<15:38:01.916> we've<15:38:02.160> already<15:38:02.276> seen<15:38:02.456> this<15:38:02.640> before<15:38:02.756> but 15:38:03.050 --> 15:38:03.060 align:start position:0% now we've already seen this before but 15:38:03.060 --> 15:38:05.390 align:start position:0% now we've already seen this before but here's<15:38:03.360> another<15:38:03.480> example<15:38:04.020> of<15:38:04.616> what<15:38:04.916> remote 15:38:05.390 --> 15:38:05.400 align:start position:0% here's another example of what remote 15:38:05.400 --> 15:38:08.990 align:start position:0% here's another example of what remote access<15:38:05.756> might<15:38:06.180> look<15:38:06.416> like<15:38:06.596> I'm<15:38:07.200> at<15:38:07.436> home<15:38:07.640> and<15:38:08.640> I 15:38:08.990 --> 15:38:09.000 align:start position:0% access might look like I'm at home and I 15:38:09.000 --> 15:38:11.926 align:start position:0% access might look like I'm at home and I want<15:38:09.180> to<15:38:09.296> access<15:38:09.540> the<15:38:10.020> office<15:38:10.200> computer<15:38:10.580> so<15:38:11.580> I 15:38:11.926 --> 15:38:11.936 align:start position:0% want to access the office computer so I 15:38:11.936 --> 15:38:14.210 align:start position:0% want to access the office computer so I connect<15:38:12.116> through<15:38:12.540> the<15:38:12.840> internet<15:38:13.020> to<15:38:13.916> the 15:38:14.210 --> 15:38:14.220 align:start position:0% connect through the internet to the 15:38:14.220 --> 15:38:16.310 align:start position:0% connect through the internet to the router<15:38:14.640> over<15:38:14.936> at<15:38:15.116> the<15:38:15.296> office<15:38:15.480> through 15:38:16.310 --> 15:38:16.320 align:start position:0% router over at the office through 15:38:16.320 --> 15:38:19.010 align:start position:0% router over at the office through something<15:38:16.616> called<15:38:17.096> a<15:38:17.756> VPN 15:38:19.010 --> 15:38:19.020 align:start position:0% something called a VPN 15:38:19.020 --> 15:38:21.246 align:start position:0% something called a VPN and<15:38:19.500> now<15:38:19.680> it<15:38:20.040> says<15:38:20.220> though<15:38:20.400> I'm<15:38:20.580> sitting<15:38:21.000> there 15:38:21.246 --> 15:38:21.256 align:start position:0% and now it says though I'm sitting there 15:38:21.256 --> 15:38:24.350 align:start position:0% and now it says though I'm sitting there working<15:38:22.256> at<15:38:22.860> the<15:38:23.040> office<15:38:23.220> in<15:38:23.756> fact<15:38:24.000> if<15:38:24.240> it 15:38:24.350 --> 15:38:24.360 align:start position:0% working at the office in fact if it 15:38:24.360 --> 15:38:26.390 align:start position:0% working at the office in fact if it wasn't<15:38:24.480> for<15:38:24.720> the<15:38:24.900> fact<15:38:25.020> the<15:38:25.380> boss<15:38:25.560> had<15:38:25.916> to<15:38:26.160> see 15:38:26.390 --> 15:38:26.400 align:start position:0% wasn't for the fact the boss had to see 15:38:26.400 --> 15:38:28.730 align:start position:0% wasn't for the fact the boss had to see my<15:38:26.756> face<15:38:27.060> they<15:38:27.840> would<15:38:28.020> think<15:38:28.200> that<15:38:28.436> I<15:38:28.616> was 15:38:28.730 --> 15:38:28.740 align:start position:0% my face they would think that I was 15:38:28.740 --> 15:38:29.926 align:start position:0% my face they would think that I was actually<15:38:28.916> there 15:38:29.926 --> 15:38:29.936 align:start position:0% actually there 15:38:29.936 --> 15:38:32.990 align:start position:0% actually there so<15:38:30.480> the<15:38:30.720> first<15:38:30.840> step<15:38:31.080> in<15:38:31.380> implementing<15:38:32.160> on 15:38:32.990 --> 15:38:33.000 align:start position:0% so the first step in implementing on 15:38:33.000 --> 15:38:36.586 align:start position:0% so the first step in implementing on remote<15:38:33.480> access<15:38:33.916> is<15:38:34.916> assessing<15:38:35.456> it<15:38:35.640> we<15:38:36.360> need<15:38:36.480> to 15:38:36.586 --> 15:38:36.596 align:start position:0% remote access is assessing it we need to 15:38:36.596 --> 15:38:38.210 align:start position:0% remote access is assessing it we need to before<15:38:36.840> we<15:38:37.140> can<15:38:37.200> set<15:38:37.320> anything<15:38:37.500> up<15:38:37.740> we<15:38:37.980> need<15:38:38.096> to 15:38:38.210 --> 15:38:38.220 align:start position:0% before we can set anything up we need to 15:38:38.220 --> 15:38:40.670 align:start position:0% before we can set anything up we need to know<15:38:38.400> what<15:38:39.000> exactly<15:38:39.480> we<15:38:39.776> are<15:38:39.956> going<15:38:40.200> to<15:38:40.380> set<15:38:40.560> up 15:38:40.670 --> 15:38:40.680 align:start position:0% know what exactly we are going to set up 15:38:40.680 --> 15:38:42.106 align:start position:0% know what exactly we are going to set up so<15:38:41.040> first<15:38:41.220> you<15:38:41.400> need<15:38:41.520> to<15:38:41.580> review<15:38:41.756> and 15:38:42.106 --> 15:38:42.116 align:start position:0% so first you need to review and 15:38:42.116 --> 15:38:43.606 align:start position:0% so first you need to review and determine<15:38:42.596> all<15:38:42.840> the<15:38:42.956> connections<15:38:43.380> that<15:38:43.500> are 15:38:43.606 --> 15:38:43.616 align:start position:0% determine all the connections that are 15:38:43.616 --> 15:38:45.586 align:start position:0% determine all the connections that are going<15:38:43.740> in<15:38:43.980> and<15:38:44.096> out<15:38:44.220> of<15:38:44.340> the<15:38:44.520> Lan<15:38:44.756> this<15:38:45.360> means 15:38:45.586 --> 15:38:45.596 align:start position:0% going in and out of the Lan this means 15:38:45.596 --> 15:38:47.330 align:start position:0% going in and out of the Lan this means deciding<15:38:46.140> how<15:38:46.380> remote<15:38:46.560> users<15:38:47.040> are<15:38:47.096> going<15:38:47.220> to 15:38:47.330 --> 15:38:47.340 align:start position:0% deciding how remote users are going to 15:38:47.340 --> 15:38:49.786 align:start position:0% deciding how remote users are going to connect<15:38:47.400> to<15:38:47.580> the<15:38:47.756> network<15:38:47.880> for<15:38:48.596> instance<15:38:48.900> if<15:38:49.560> I 15:38:49.786 --> 15:38:49.796 align:start position:0% connect to the network for instance if I 15:38:49.796 --> 15:38:52.130 align:start position:0% connect to the network for instance if I want<15:38:50.160> someone<15:38:50.400> to<15:38:50.880> dial<15:38:51.116> in<15:38:51.416> directly<15:38:52.020> they 15:38:52.130 --> 15:38:52.140 align:start position:0% want someone to dial in directly they 15:38:52.140 --> 15:38:53.810 align:start position:0% want someone to dial in directly they could<15:38:52.320> use<15:38:52.436> a<15:38:52.560> modem<15:38:52.916> this<15:38:53.276> is<15:38:53.400> going<15:38:53.580> to<15:38:53.700> go 15:38:53.810 --> 15:38:53.820 align:start position:0% could use a modem this is going to go 15:38:53.820 --> 15:38:55.730 align:start position:0% could use a modem this is going to go over<15:38:54.000> the<15:38:54.360> public<15:38:54.596> switch<15:38:54.956> telephone<15:38:55.320> Network 15:38:55.730 --> 15:38:55.740 align:start position:0% over the public switch telephone Network 15:38:55.740 --> 15:38:58.070 align:start position:0% over the public switch telephone Network or<15:38:56.220> pots<15:38:57.060> the 15:38:58.070 --> 15:38:58.080 align:start position:0% or pots the 15:38:58.080 --> 15:39:01.070 align:start position:0% or pots the plain<15:38:58.860> old<15:38:59.096> telephone<15:38:59.400> system<15:39:00.080> alternatively 15:39:01.070 --> 15:39:01.080 align:start position:0% plain old telephone system alternatively 15:39:01.080 --> 15:39:02.746 align:start position:0% plain old telephone system alternatively let's<15:39:01.380> say<15:39:01.560> I<15:39:01.796> have<15:39:01.916> a<15:39:02.096> T3<15:39:02.456> connection 15:39:02.746 --> 15:39:02.756 align:start position:0% let's say I have a T3 connection 15:39:02.756 --> 15:39:05.446 align:start position:0% let's say I have a T3 connection connecting<15:39:03.360> to<15:39:03.480> corporate<15:39:03.840> Lan<15:39:04.140> out<15:39:04.916> to<15:39:05.096> an 15:39:05.446 --> 15:39:05.456 align:start position:0% connecting to corporate Lan out to an 15:39:05.456 --> 15:39:08.446 align:start position:0% connecting to corporate Lan out to an ISP<15:39:06.116> well<15:39:06.900> then<15:39:07.200> as<15:39:07.560> long<15:39:07.680> as<15:39:07.796> people<15:39:07.980> at<15:39:08.276> home 15:39:08.446 --> 15:39:08.456 align:start position:0% ISP well then as long as people at home 15:39:08.456 --> 15:39:11.030 align:start position:0% ISP well then as long as people at home have<15:39:08.756> internet<15:39:09.000> access<15:39:09.360> which<15:39:09.956> today<15:39:10.436> they 15:39:11.030 --> 15:39:11.040 align:start position:0% have internet access which today they 15:39:11.040 --> 15:39:12.350 align:start position:0% have internet access which today they basically<15:39:11.456> would<15:39:11.700> and<15:39:11.880> most<15:39:12.060> of<15:39:12.180> them<15:39:12.240> have 15:39:12.350 --> 15:39:12.360 align:start position:0% basically would and most of them have 15:39:12.360 --> 15:39:14.210 align:start position:0% basically would and most of them have Broadband<15:39:12.776> access<15:39:13.020> they'd<15:39:13.740> be<15:39:13.860> able<15:39:14.096> to 15:39:14.210 --> 15:39:14.220 align:start position:0% Broadband access they'd be able to 15:39:14.220 --> 15:39:16.906 align:start position:0% Broadband access they'd be able to connect<15:39:14.456> back<15:39:14.880> through<15:39:15.116> their<15:39:15.360> ISP<15:39:15.840> to<15:39:16.560> the 15:39:16.906 --> 15:39:16.916 align:start position:0% connect back through their ISP to the 15:39:16.916 --> 15:39:17.630 align:start position:0% connect back through their ISP to the network 15:39:17.630 --> 15:39:17.640 align:start position:0% network 15:39:17.640 --> 15:39:20.210 align:start position:0% network second<15:39:18.240> we<15:39:18.840> have<15:39:19.080> to<15:39:19.320> understand<15:39:19.616> know 15:39:20.210 --> 15:39:20.220 align:start position:0% second we have to understand know 15:39:20.220 --> 15:39:22.010 align:start position:0% second we have to understand know exactly<15:39:20.640> what<15:39:20.820> applications<15:39:21.296> and<15:39:21.660> systems 15:39:22.010 --> 15:39:22.020 align:start position:0% exactly what applications and systems 15:39:22.020 --> 15:39:24.530 align:start position:0% exactly what applications and systems they're<15:39:22.200> going<15:39:22.320> to<15:39:22.500> need<15:39:22.560> for<15:39:23.400> instance<15:39:23.640> I<15:39:24.296> can 15:39:24.530 --> 15:39:24.540 align:start position:0% they're going to need for instance I can 15:39:24.540 --> 15:39:28.070 align:start position:0% they're going to need for instance I can give<15:39:24.840> them<15:39:24.956> access<15:39:25.320> to<15:39:26.160> their<15:39:26.580> computer<15:39:27.080> which 15:39:28.070 --> 15:39:28.080 align:start position:0% give them access to their computer which 15:39:28.080 --> 15:39:30.350 align:start position:0% give them access to their computer which might<15:39:28.436> be<15:39:28.616> one<15:39:28.860> way<15:39:28.980> to<15:39:29.160> do<15:39:29.276> it<15:39:29.456> but<15:39:29.880> if<15:39:30.116> I<15:39:30.240> have 15:39:30.350 --> 15:39:30.360 align:start position:0% might be one way to do it but if I have 15:39:30.360 --> 15:39:32.510 align:start position:0% might be one way to do it but if I have a<15:39:30.540> lot<15:39:30.660> of<15:39:30.776> people<15:39:30.956> logging<15:39:31.500> in<15:39:31.680> constantly 15:39:32.510 --> 15:39:32.520 align:start position:0% a lot of people logging in constantly 15:39:32.520 --> 15:39:34.370 align:start position:0% a lot of people logging in constantly remotely<15:39:33.296> and<15:39:33.480> I<15:39:33.660> need<15:39:33.720> to<15:39:33.900> give<15:39:34.020> them<15:39:34.200> access 15:39:34.370 --> 15:39:34.380 align:start position:0% remotely and I need to give them access 15:39:34.380 --> 15:39:35.690 align:start position:0% remotely and I need to give them access to<15:39:34.680> their<15:39:34.860> computer<15:39:35.040> that's<15:39:35.340> going<15:39:35.520> to<15:39:35.520> be 15:39:35.690 --> 15:39:35.700 align:start position:0% to their computer that's going to be 15:39:35.700 --> 15:39:38.746 align:start position:0% to their computer that's going to be pretty<15:39:35.880> difficult<15:39:36.240> to<15:39:36.540> set<15:39:36.660> up<15:39:36.840> and<15:39:37.500> quite 15:39:38.746 --> 15:39:38.756 align:start position:0% pretty difficult to set up and quite 15:39:38.756 --> 15:39:41.710 align:start position:0% pretty difficult to set up and quite um 15:39:41.710 --> 15:39:41.720 align:start position:0% 15:39:41.720 --> 15:39:44.690 align:start position:0% uncentralized<15:39:42.720> so<15:39:43.320> what<15:39:43.560> I<15:39:43.740> might<15:39:43.860> do<15:39:44.096> is 15:39:44.690 --> 15:39:44.700 align:start position:0% uncentralized so what I might do is 15:39:44.700 --> 15:39:48.830 align:start position:0% uncentralized so what I might do is create<15:39:45.060> one<15:39:45.660> remote<15:39:46.020> access<15:39:46.500> server<15:39:47.220> RS<15:39:47.840> in 15:39:48.830 --> 15:39:48.840 align:start position:0% create one remote access server RS in 15:39:48.840 --> 15:39:51.406 align:start position:0% create one remote access server RS in which<15:39:49.080> uh<15:39:49.740> everyone<15:39:49.980> can<15:39:50.400> connect<15:39:50.640> and<15:39:51.180> get 15:39:51.406 --> 15:39:51.416 align:start position:0% which uh everyone can connect and get 15:39:51.416 --> 15:39:54.170 align:start position:0% which uh everyone can connect and get their<15:39:51.720> profile<15:39:52.200> or<15:39:52.560> information<15:39:52.916> this<15:39:53.880> also 15:39:54.170 --> 15:39:54.180 align:start position:0% their profile or information this also 15:39:54.180 --> 15:39:55.390 align:start position:0% their profile or information this also goes<15:39:54.480> with<15:39:54.660> something<15:39:54.900> called 15:39:55.390 --> 15:39:55.400 align:start position:0% goes with something called 15:39:55.400 --> 15:39:57.946 align:start position:0% goes with something called virtualization<15:39:56.400> or 15:39:57.946 --> 15:39:57.956 align:start position:0% virtualization or 15:39:57.956 --> 15:40:01.070 align:start position:0% virtualization or cloud<15:39:58.500> computing<15:39:59.220> so<15:40:00.180> basically<15:40:00.660> they<15:40:00.900> would 15:40:01.070 --> 15:40:01.080 align:start position:0% cloud computing so basically they would 15:40:01.080 --> 15:40:03.650 align:start position:0% cloud computing so basically they would log<15:40:01.256> on<15:40:01.500> to<15:40:01.680> this<15:40:01.980> very<15:40:02.276> powerful<15:40:02.756> server<15:40:03.180> and 15:40:03.650 --> 15:40:03.660 align:start position:0% log on to this very powerful server and 15:40:03.660 --> 15:40:05.446 align:start position:0% log on to this very powerful server and they<15:40:03.776> would<15:40:03.956> see<15:40:04.140> what<15:40:04.436> looks<15:40:04.796> like<15:40:04.980> their 15:40:05.446 --> 15:40:05.456 align:start position:0% they would see what looks like their 15:40:05.456 --> 15:40:07.906 align:start position:0% they would see what looks like their computer<15:40:05.756> in<15:40:06.480> fact<15:40:06.596> if<15:40:06.956> I<15:40:07.256> was<15:40:07.500> basically 15:40:07.906 --> 15:40:07.916 align:start position:0% computer in fact if I was basically 15:40:07.916 --> 15:40:09.766 align:start position:0% computer in fact if I was basically doing<15:40:08.160> this<15:40:08.400> all<15:40:08.580> the<15:40:08.700> time<15:40:08.820> I<15:40:09.296> might<15:40:09.416> just<15:40:09.596> do 15:40:09.766 --> 15:40:09.776 align:start position:0% doing this all the time I might just do 15:40:09.776 --> 15:40:11.390 align:start position:0% doing this all the time I might just do this<15:40:10.020> for<15:40:10.500> when<15:40:10.616> they<15:40:10.796> sit<15:40:10.916> at<15:40:11.096> the<15:40:11.220> office 15:40:11.390 --> 15:40:11.400 align:start position:0% this for when they sit at the office 15:40:11.400 --> 15:40:13.370 align:start position:0% this for when they sit at the office they<15:40:11.820> just<15:40:12.116> sit<15:40:12.240> at<15:40:12.416> a<15:40:12.540> terminal<15:40:12.900> sort<15:40:13.256> of 15:40:13.370 --> 15:40:13.380 align:start position:0% they just sit at a terminal sort of 15:40:13.380 --> 15:40:15.530 align:start position:0% they just sit at a terminal sort of thing<15:40:13.560> turn<15:40:14.400> on<15:40:14.580> the<15:40:14.700> computer<15:40:14.880> and<15:40:15.360> they're 15:40:15.530 --> 15:40:15.540 align:start position:0% thing turn on the computer and they're 15:40:15.540 --> 15:40:17.266 align:start position:0% thing turn on the computer and they're connecting<15:40:16.020> actually<15:40:16.320> to<15:40:16.680> a<15:40:16.860> server<15:40:17.096> that's 15:40:17.266 --> 15:40:17.276 align:start position:0% connecting actually to a server that's 15:40:17.276 --> 15:40:20.150 align:start position:0% connecting actually to a server that's not<15:40:17.520> even<15:40:17.640> located<15:40:17.936> in<15:40:18.296> the<15:40:18.480> building 15:40:20.150 --> 15:40:20.160 align:start position:0% not even located in the building 15:40:20.160 --> 15:40:21.650 align:start position:0% not even located in the building finally<15:40:20.640> I<15:40:20.820> want<15:40:20.936> to<15:40:21.060> determine<15:40:21.360> the<15:40:21.540> number 15:40:21.650 --> 15:40:21.660 align:start position:0% finally I want to determine the number 15:40:21.660 --> 15:40:23.446 align:start position:0% finally I want to determine the number of<15:40:21.840> remote<15:40:22.020> users<15:40:22.436> if<15:40:22.616> I'm<15:40:22.740> only<15:40:22.916> giving<15:40:23.160> this 15:40:23.446 --> 15:40:23.456 align:start position:0% of remote users if I'm only giving this 15:40:23.456 --> 15:40:27.470 align:start position:0% of remote users if I'm only giving this to<15:40:23.820> say<15:40:24.140> uh<15:40:25.140> the<15:40:25.560> top<15:40:25.860> hun<15:40:26.400> shows<15:40:26.880> at<15:40:27.060> the<15:40:27.180> firm 15:40:27.470 --> 15:40:27.480 align:start position:0% to say uh the top hun shows at the firm 15:40:27.480 --> 15:40:29.990 align:start position:0% to say uh the top hun shows at the firm that's<15:40:28.320> one<15:40:28.616> thing<15:40:28.796> that's<15:40:29.220> going<15:40:29.456> to<15:40:29.580> be<15:40:29.700> for 15:40:29.990 --> 15:40:30.000 align:start position:0% that's one thing that's going to be for 15:40:30.000 --> 15:40:32.086 align:start position:0% that's one thing that's going to be for everyone<15:40:30.296> in<15:40:30.660> the<15:40:30.900> entire<15:40:31.080> operation<15:40:31.860> I'm 15:40:32.086 --> 15:40:32.096 align:start position:0% everyone in the entire operation I'm 15:40:32.096 --> 15:40:33.350 align:start position:0% everyone in the entire operation I'm going<15:40:32.276> to<15:40:32.400> need<15:40:32.456> to<15:40:32.580> spend<15:40:32.820> a<15:40:32.936> lot<15:40:33.000> more<15:40:33.116> time 15:40:33.350 --> 15:40:33.360 align:start position:0% going to need to spend a lot more time 15:40:33.360 --> 15:40:35.990 align:start position:0% going to need to spend a lot more time and<15:40:33.540> resources<15:40:34.080> devoted<15:40:34.796> to<15:40:35.520> setting<15:40:35.936> up 15:40:35.990 --> 15:40:36.000 align:start position:0% and resources devoted to setting up 15:40:36.000 --> 15:40:37.670 align:start position:0% and resources devoted to setting up remote<15:40:36.240> access 15:40:37.670 --> 15:40:37.680 align:start position:0% remote access 15:40:37.680 --> 15:40:39.230 align:start position:0% remote access now<15:40:38.160> the<15:40:38.340> next<15:40:38.400> thing<15:40:38.520> I<15:40:38.640> have<15:40:38.756> to<15:40:38.880> do<15:40:38.936> is<15:40:39.060> think 15:40:39.230 --> 15:40:39.240 align:start position:0% now the next thing I have to do is think 15:40:39.240 --> 15:40:40.970 align:start position:0% now the next thing I have to do is think about<15:40:39.360> the<15:40:39.660> considerations<15:40:40.256> and<15:40:40.680> the<15:40:40.860> things 15:40:40.970 --> 15:40:40.980 align:start position:0% about the considerations and the things 15:40:40.980 --> 15:40:43.310 align:start position:0% about the considerations and the things that<15:40:41.160> are<15:40:41.340> necessary<15:40:41.820> for<15:40:42.480> remote<15:40:42.720> access<15:40:43.020> in 15:40:43.310 --> 15:40:43.320 align:start position:0% that are necessary for remote access in 15:40:43.320 --> 15:40:45.230 align:start position:0% that are necessary for remote access in order<15:40:43.500> to<15:40:43.616> implement<15:40:43.980> for<15:40:44.820> instance<15:40:45.000> the 15:40:45.230 --> 15:40:45.240 align:start position:0% order to implement for instance the 15:40:45.240 --> 15:40:47.030 align:start position:0% order to implement for instance the first<15:40:45.360> step<15:40:45.596> is<15:40:45.776> to<15:40:46.020> make<15:40:46.380> sure<15:40:46.560> that<15:40:46.916> the 15:40:47.030 --> 15:40:47.040 align:start position:0% first step is to make sure that the 15:40:47.040 --> 15:40:48.530 align:start position:0% first step is to make sure that the remote<15:40:47.160> access<15:40:47.456> solution<15:40:47.936> you<15:40:48.116> create<15:40:48.296> is 15:40:48.530 --> 15:40:48.540 align:start position:0% remote access solution you create is 15:40:48.540 --> 15:40:50.210 align:start position:0% remote access solution you create is flexible<15:40:49.020> enough<15:40:49.256> to<15:40:49.740> support<15:40:49.860> all<15:40:50.096> those 15:40:50.210 --> 15:40:50.220 align:start position:0% flexible enough to support all those 15:40:50.220 --> 15:40:51.650 align:start position:0% flexible enough to support all those connections<15:40:50.640> and<15:40:50.820> the<15:40:51.000> users<15:40:51.240> that<15:40:51.360> are<15:40:51.540> that 15:40:51.650 --> 15:40:51.660 align:start position:0% connections and the users that are that 15:40:51.660 --> 15:40:53.926 align:start position:0% connections and the users that are that you've<15:40:51.900> just<15:40:52.080> established<15:40:52.616> for<15:40:53.276> example<15:40:53.520> if 15:40:53.926 --> 15:40:53.936 align:start position:0% you've just established for example if 15:40:53.936 --> 15:40:55.906 align:start position:0% you've just established for example if one<15:40:54.180> remote<15:40:54.360> user<15:40:55.020> is<15:40:55.080> connected<15:40:55.380> to<15:40:55.500> a<15:40:55.680> T1 15:40:55.906 --> 15:40:55.916 align:start position:0% one remote user is connected to a T1 15:40:55.916 --> 15:40:57.530 align:start position:0% one remote user is connected to a T1 Line<15:40:56.220> and<15:40:56.700> other<15:40:56.880> ones<15:40:57.060> can't<15:40:57.240> get<15:40:57.416> through 15:40:57.530 --> 15:40:57.540 align:start position:0% Line and other ones can't get through 15:40:57.540 --> 15:40:59.446 align:start position:0% Line and other ones can't get through dial<15:40:57.776> up<15:40:58.020> your<15:40:58.680> solution<15:40:58.916> is<15:40:59.096> going<15:40:59.276> to<15:40:59.340> need 15:40:59.446 --> 15:40:59.456 align:start position:0% dial up your solution is going to need 15:40:59.456 --> 15:41:00.906 align:start position:0% dial up your solution is going to need to<15:40:59.520> be<15:40:59.640> able<15:40:59.756> to<15:40:59.880> accommodate<15:41:00.360> both<15:41:00.596> of<15:41:00.720> them 15:41:00.906 --> 15:41:00.916 align:start position:0% to be able to accommodate both of them 15:41:00.916 --> 15:41:03.406 align:start position:0% to be able to accommodate both of them of<15:41:01.916> course<15:41:02.040> nowadays<15:41:02.580> that's<15:41:02.820> not<15:41:03.060> such<15:41:03.240> an 15:41:03.406 --> 15:41:03.416 align:start position:0% of course nowadays that's not such an 15:41:03.416 --> 15:41:05.746 align:start position:0% of course nowadays that's not such an issue<15:41:03.720> because<15:41:03.956> everyone<15:41:04.256> has 15:41:05.746 --> 15:41:05.756 align:start position:0% issue because everyone has 15:41:05.756 --> 15:41:08.446 align:start position:0% issue because everyone has um Broadband<15:41:06.596> connections<15:41:07.200> but<15:41:07.860> if<15:41:08.220> they're 15:41:08.446 --> 15:41:08.456 align:start position:0% um Broadband connections but if they're 15:41:08.456 --> 15:41:10.370 align:start position:0% um Broadband connections but if they're not<15:41:08.640> connecting<15:41:09.116> in<15:41:09.416> the<15:41:09.540> same<15:41:09.660> way<15:41:09.840> or<15:41:10.080> one 15:41:10.370 --> 15:41:10.380 align:start position:0% not connecting in the same way or one 15:41:10.380 --> 15:41:11.810 align:start position:0% not connecting in the same way or one person<15:41:10.560> is<15:41:10.796> going<15:41:10.916> to<15:41:11.040> be<15:41:11.040> connect<15:41:11.220> traveling 15:41:11.810 --> 15:41:11.820 align:start position:0% person is going to be connect traveling 15:41:11.820 --> 15:41:13.010 align:start position:0% person is going to be connect traveling around<15:41:12.000> while<15:41:12.296> most<15:41:12.480> people<15:41:12.660> are<15:41:12.776> going<15:41:12.840> to<15:41:12.956> be 15:41:13.010 --> 15:41:13.020 align:start position:0% around while most people are going to be 15:41:13.020 --> 15:41:14.746 align:start position:0% around while most people are going to be coming<15:41:13.140> from<15:41:13.436> home<15:41:13.680> well<15:41:14.220> and<15:41:14.400> those<15:41:14.580> are<15:41:14.700> all 15:41:14.746 --> 15:41:14.756 align:start position:0% coming from home well and those are all 15:41:14.756 --> 15:41:16.550 align:start position:0% coming from home well and those are all things<15:41:14.936> I<15:41:15.060> need<15:41:15.180> to<15:41:15.296> take<15:41:15.416> into<15:41:15.660> account 15:41:16.550 --> 15:41:16.560 align:start position:0% things I need to take into account 15:41:16.560 --> 15:41:19.426 align:start position:0% things I need to take into account next<15:41:17.340> need<15:41:18.180> to<15:41:18.360> establish<15:41:18.900> some<15:41:19.140> sort<15:41:19.320> of 15:41:19.426 --> 15:41:19.436 align:start position:0% next need to establish some sort of 15:41:19.436 --> 15:41:22.190 align:start position:0% next need to establish some sort of centralized<15:41:20.040> access<15:41:20.276> point<15:41:20.700> meaning<15:41:21.540> when 15:41:22.190 --> 15:41:22.200 align:start position:0% centralized access point meaning when 15:41:22.200 --> 15:41:24.530 align:start position:0% centralized access point meaning when they<15:41:22.436> hit<15:41:22.616> that<15:41:23.040> router<15:41:23.580> uh<15:41:24.240> if<15:41:24.416> they're 15:41:24.530 --> 15:41:24.540 align:start position:0% they hit that router uh if they're 15:41:24.540 --> 15:41:27.106 align:start position:0% they hit that router uh if they're coming<15:41:24.720> out<15:41:25.020> of<15:41:25.200> the<15:41:25.436> internet<15:41:25.880> into<15:41:26.880> the 15:41:27.106 --> 15:41:27.116 align:start position:0% coming out of the internet into the 15:41:27.116 --> 15:41:29.086 align:start position:0% coming out of the internet into the router<15:41:27.416> I<15:41:27.596> need<15:41:27.776> something<15:41:28.080> here<15:41:28.500> that<15:41:28.916> is 15:41:29.086 --> 15:41:29.096 align:start position:0% router I need something here that is 15:41:29.096 --> 15:41:30.946 align:start position:0% router I need something here that is going<15:41:29.340> to<15:41:29.580> centralize<15:41:30.180> all<15:41:30.596> of<15:41:30.720> the<15:41:30.840> stuff 15:41:30.946 --> 15:41:30.956 align:start position:0% going to centralize all of the stuff 15:41:30.956 --> 15:41:32.810 align:start position:0% going to centralize all of the stuff coming<15:41:31.256> in<15:41:31.500> I<15:41:31.980> also<15:41:32.220> don't<15:41:32.276> want<15:41:32.456> to<15:41:32.580> just<15:41:32.640> give 15:41:32.810 --> 15:41:32.820 align:start position:0% coming in I also don't want to just give 15:41:32.820 --> 15:41:34.246 align:start position:0% coming in I also don't want to just give them<15:41:33.000> access<15:41:33.180> to<15:41:33.416> the<15:41:33.480> network<15:41:33.596> I<15:41:33.956> might<15:41:34.080> want 15:41:34.246 --> 15:41:34.256 align:start position:0% them access to the network I might want 15:41:34.256 --> 15:41:37.786 align:start position:0% them access to the network I might want to<15:41:34.380> send<15:41:34.560> them<15:41:34.740> into<15:41:35.040> a<15:41:35.456> separate 15:41:37.786 --> 15:41:37.796 align:start position:0% to send them into a separate 15:41:37.796 --> 15:41:40.246 align:start position:0% to send them into a separate Network<15:41:38.340> temporarily<15:41:39.240> while<15:41:39.776> I<15:41:39.956> make<15:41:40.140> sure 15:41:40.246 --> 15:41:40.256 align:start position:0% Network temporarily while I make sure 15:41:40.256 --> 15:41:42.050 align:start position:0% Network temporarily while I make sure that<15:41:40.436> they<15:41:40.616> get<15:41:40.740> authenticated<15:41:41.400> perhaps<15:41:41.880> a 15:41:42.050 --> 15:41:42.060 align:start position:0% that they get authenticated perhaps a 15:41:42.060 --> 15:41:45.050 align:start position:0% that they get authenticated perhaps a virtual<15:41:42.416> Lan<15:41:42.776> or<15:41:43.200> a<15:41:43.640> Honeypot<15:41:44.640> or<15:41:44.880> something 15:41:45.050 --> 15:41:45.060 align:start position:0% virtual Lan or a Honeypot or something 15:41:45.060 --> 15:41:48.170 align:start position:0% virtual Lan or a Honeypot or something so<15:41:45.956> it's<15:41:46.560> important<15:41:46.860> or<15:41:47.040> demilitarized<15:41:47.880> zone 15:41:48.170 --> 15:41:48.180 align:start position:0% so it's important or demilitarized zone 15:41:48.180 --> 15:41:50.630 align:start position:0% so it's important or demilitarized zone so<15:41:48.900> it's<15:41:49.200> important<15:41:49.560> that<15:41:49.796> I<15:41:49.980> have<15:41:50.160> some<15:41:50.400> area 15:41:50.630 --> 15:41:50.640 align:start position:0% so it's important that I have some area 15:41:50.640 --> 15:41:52.426 align:start position:0% so it's important that I have some area where<15:41:50.936> they<15:41:51.116> can<15:41:51.240> go<15:41:51.416> and<15:41:51.900> understand<15:41:52.020> what 15:41:52.426 --> 15:41:52.436 align:start position:0% where they can go and understand what 15:41:52.436 --> 15:41:54.350 align:start position:0% where they can go and understand what the<15:41:52.560> central<15:41:52.740> device<15:41:53.040> is<15:41:53.276> going<15:41:53.456> to<15:41:53.580> be<15:41:53.700> in 15:41:54.350 --> 15:41:54.360 align:start position:0% the central device is going to be in 15:41:54.360 --> 15:41:58.210 align:start position:0% the central device is going to be in some<15:41:54.540> cases<15:41:54.840> we<15:41:55.140> could<15:41:55.320> call<15:41:55.560> this<15:41:55.860> a<15:41:56.400> VPN 15:41:58.210 --> 15:41:58.220 align:start position:0% some cases we could call this a VPN 15:41:58.220 --> 15:42:00.106 align:start position:0% some cases we could call this a VPN concentrator 15:42:00.106 --> 15:42:00.116 align:start position:0% concentrator 15:42:00.116 --> 15:42:02.390 align:start position:0% concentrator which<15:42:00.720> is<15:42:01.020> basically<15:42:01.380> a<15:42:01.616> device<15:42:01.796> that<15:42:02.160> helps 15:42:02.390 --> 15:42:02.400 align:start position:0% which is basically a device that helps 15:42:02.400 --> 15:42:05.330 align:start position:0% which is basically a device that helps set<15:42:02.520> up<15:42:02.700> vpns<15:42:03.900> finally<15:42:04.380> I<15:42:04.560> need<15:42:04.740> to<15:42:04.860> consider 15:42:05.330 --> 15:42:05.340 align:start position:0% set up vpns finally I need to consider 15:42:05.340 --> 15:42:06.830 align:start position:0% set up vpns finally I need to consider security<15:42:05.580> when<15:42:06.060> I'm<15:42:06.180> establishing<15:42:06.660> this 15:42:06.830 --> 15:42:06.840 align:start position:0% security when I'm establishing this 15:42:06.840 --> 15:42:08.630 align:start position:0% security when I'm establishing this remote<15:42:07.020> system<15:42:07.380> as<15:42:07.980> I<15:42:08.096> mentioned<15:42:08.340> I<15:42:08.520> don't 15:42:08.630 --> 15:42:08.640 align:start position:0% remote system as I mentioned I don't 15:42:08.640 --> 15:42:09.946 align:start position:0% remote system as I mentioned I don't just<15:42:08.756> want<15:42:08.880> to<15:42:09.000> give<15:42:09.060> people<15:42:09.296> access<15:42:09.540> to<15:42:09.776> the 15:42:09.946 --> 15:42:09.956 align:start position:0% just want to give people access to the 15:42:09.956 --> 15:42:11.150 align:start position:0% just want to give people access to the network<15:42:10.080> I<15:42:10.380> want<15:42:10.560> to<15:42:10.680> make<15:42:10.740> sure<15:42:10.860> the<15:42:10.980> people 15:42:11.150 --> 15:42:11.160 align:start position:0% network I want to make sure the people 15:42:11.160 --> 15:42:13.850 align:start position:0% network I want to make sure the people on<15:42:11.400> my<15:42:11.640> network<15:42:11.820> connecting<15:42:12.540> wirelessly<15:42:13.256> or 15:42:13.850 --> 15:42:13.860 align:start position:0% on my network connecting wirelessly or 15:42:13.860 --> 15:42:16.490 align:start position:0% on my network connecting wirelessly or remotely<15:42:14.456> or<15:42:15.180> physically<15:42:15.840> connecting<15:42:16.256> can 15:42:16.490 --> 15:42:16.500 align:start position:0% remotely or physically connecting can 15:42:16.500 --> 15:42:18.530 align:start position:0% remotely or physically connecting can all<15:42:16.740> connect<15:42:16.916> securely<15:42:17.520> I<15:42:18.180> don't<15:42:18.296> want 15:42:18.530 --> 15:42:18.540 align:start position:0% all connect securely I don't want 15:42:18.540 --> 15:42:21.230 align:start position:0% all connect securely I don't want someone<15:42:18.900> to<15:42:19.256> tap<15:42:19.560> into<15:42:19.740> their<15:42:20.220> connection<15:42:20.400> on 15:42:21.230 --> 15:42:21.240 align:start position:0% someone to tap into their connection on 15:42:21.240 --> 15:42:23.746 align:start position:0% someone to tap into their connection on my<15:42:21.416> end<15:42:21.596> or<15:42:22.200> on<15:42:22.436> their<15:42:22.560> end<15:42:22.796> so<15:42:23.340> it's<15:42:23.520> really 15:42:23.746 --> 15:42:23.756 align:start position:0% my end or on their end so it's really 15:42:23.756 --> 15:42:25.266 align:start position:0% my end or on their end so it's really important<15:42:24.060> we<15:42:24.240> take<15:42:24.416> security<15:42:24.596> into<15:42:24.956> account 15:42:25.266 --> 15:42:25.276 align:start position:0% important we take security into account 15:42:25.276 --> 15:42:27.946 align:start position:0% important we take security into account nowadays<15:42:26.276> we<15:42:26.580> have<15:42:26.700> a<15:42:27.060> lot<15:42:27.180> of<15:42:27.360> uh 15:42:27.946 --> 15:42:27.956 align:start position:0% nowadays we have a lot of uh 15:42:27.956 --> 15:42:29.690 align:start position:0% nowadays we have a lot of uh authentication<15:42:28.740> methods<15:42:29.340> that<15:42:29.580> would 15:42:29.690 --> 15:42:29.700 align:start position:0% authentication methods that would 15:42:29.700 --> 15:42:32.210 align:start position:0% authentication methods that would provide<15:42:29.936> you<15:42:30.116> with<15:42:30.416> say<15:42:30.660> a<15:42:31.320> key<15:42:31.436> ring<15:42:31.740> and<15:42:32.040> on 15:42:32.210 --> 15:42:32.220 align:start position:0% provide you with say a key ring and on 15:42:32.220 --> 15:42:33.710 align:start position:0% provide you with say a key ring and on that<15:42:32.400> key<15:42:32.580> ring<15:42:32.880> you'll<15:42:33.296> have<15:42:33.480> it<15:42:33.596> what's 15:42:33.710 --> 15:42:33.720 align:start position:0% that key ring you'll have it what's 15:42:33.720 --> 15:42:35.330 align:start position:0% that key ring you'll have it what's called<15:42:33.956> a<15:42:34.256> token 15:42:35.330 --> 15:42:35.340 align:start position:0% called a token 15:42:35.340 --> 15:42:37.370 align:start position:0% called a token the<15:42:35.820> token<15:42:36.180> provides<15:42:36.540> you<15:42:36.660> with<15:42:36.900> say<15:42:37.080> a<15:42:37.256> six 15:42:37.370 --> 15:42:37.380 align:start position:0% the token provides you with say a six 15:42:37.380 --> 15:42:39.470 align:start position:0% the token provides you with say a six digit<15:42:37.740> number<15:42:37.916> that<15:42:38.580> randomly<15:42:39.000> alternates 15:42:39.470 --> 15:42:39.480 align:start position:0% digit number that randomly alternates 15:42:39.480 --> 15:42:41.630 align:start position:0% digit number that randomly alternates every<15:42:39.776> minute<15:42:40.020> unless<15:42:40.616> you<15:42:40.860> have<15:42:41.040> the<15:42:41.276> token 15:42:41.630 --> 15:42:41.640 align:start position:0% every minute unless you have the token 15:42:41.640 --> 15:42:43.310 align:start position:0% every minute unless you have the token and<15:42:41.880> that<15:42:42.060> token<15:42:42.416> is<15:42:42.540> set<15:42:42.720> up<15:42:42.840> with<15:42:43.140> your 15:42:43.310 --> 15:42:43.320 align:start position:0% and that token is set up with your 15:42:43.320 --> 15:42:44.746 align:start position:0% and that token is set up with your computer<15:42:43.500> you<15:42:44.040> won't<15:42:44.096> be<15:42:44.276> able<15:42:44.340> to<15:42:44.456> get<15:42:44.580> access 15:42:44.746 --> 15:42:44.756 align:start position:0% computer you won't be able to get access 15:42:44.756 --> 15:42:46.786 align:start position:0% computer you won't be able to get access to<15:42:45.060> the<15:42:45.180> internet<15:42:45.416> these<15:42:46.380> things<15:42:46.500> we've 15:42:46.786 --> 15:42:46.796 align:start position:0% to the internet these things we've 15:42:46.796 --> 15:42:48.170 align:start position:0% to the internet these things we've talked<15:42:47.040> about<15:42:47.096> in<15:42:47.340> a<15:42:47.456> plus<15:42:47.640> but<15:42:47.936> I'm<15:42:48.060> just 15:42:48.170 --> 15:42:48.180 align:start position:0% talked about in a plus but I'm just 15:42:48.180 --> 15:42:50.330 align:start position:0% talked about in a plus but I'm just reviewing<15:42:48.540> them<15:42:48.720> a<15:42:48.900> bit<15:42:49.020> more 15:42:50.330 --> 15:42:50.340 align:start position:0% reviewing them a bit more 15:42:50.340 --> 15:42:51.710 align:start position:0% reviewing them a bit more now<15:42:50.580> I<15:42:50.700> also<15:42:50.880> need<15:42:51.000> to<15:42:51.116> have<15:42:51.240> some<15:42:51.360> procedures 15:42:51.710 --> 15:42:51.720 align:start position:0% now I also need to have some procedures 15:42:51.720 --> 15:42:53.746 align:start position:0% now I also need to have some procedures and<15:42:51.956> policies<15:42:52.380> in<15:42:52.680> place<15:42:52.796> so<15:42:53.220> that<15:42:53.456> people 15:42:53.746 --> 15:42:53.756 align:start position:0% and policies in place so that people 15:42:53.756 --> 15:42:55.070 align:start position:0% and policies in place so that people understand<15:42:54.060> how<15:42:54.596> they're<15:42:54.720> going<15:42:54.840> to<15:42:54.900> be<15:42:55.020> able 15:42:55.070 --> 15:42:55.080 align:start position:0% understand how they're going to be able 15:42:55.080 --> 15:42:56.086 align:start position:0% understand how they're going to be able to<15:42:55.256> access<15:42:55.320> and<15:42:55.616> what<15:42:55.740> they're<15:42:55.860> going<15:42:55.980> to<15:42:56.040> be 15:42:56.086 --> 15:42:56.096 align:start position:0% to access and what they're going to be 15:42:56.096 --> 15:42:57.106 align:start position:0% to access and what they're going to be able<15:42:56.220> to<15:42:56.340> do 15:42:57.106 --> 15:42:57.116 align:start position:0% able to do 15:42:57.116 --> 15:42:59.510 align:start position:0% able to do the<15:42:57.540> policies<15:42:57.956> ensure<15:42:58.380> that<15:42:58.740> the<15:42:59.040> procedures 15:42:59.510 --> 15:42:59.520 align:start position:0% the policies ensure that the procedures 15:42:59.520 --> 15:43:01.606 align:start position:0% the policies ensure that the procedures are<15:42:59.756> followed<15:43:00.180> and<15:43:00.540> the<15:43:00.720> procedures<15:43:01.080> ensure 15:43:01.606 --> 15:43:01.616 align:start position:0% are followed and the procedures ensure 15:43:01.616 --> 15:43:04.670 align:start position:0% are followed and the procedures ensure that<15:43:01.980> the<15:43:02.220> safety<15:43:02.640> is<15:43:03.180> used<15:43:03.480> when<15:43:03.900> remoting 15:43:04.670 --> 15:43:04.680 align:start position:0% that the safety is used when remoting 15:43:04.680 --> 15:43:06.946 align:start position:0% that the safety is used when remoting into<15:43:04.980> the<15:43:05.340> system<15:43:05.580> so<15:43:06.296> designing<15:43:06.776> these 15:43:06.946 --> 15:43:06.956 align:start position:0% into the system so designing these 15:43:06.956 --> 15:43:08.926 align:start position:0% into the system so designing these policies<15:43:07.436> is<15:43:07.680> up<15:43:07.980> to<15:43:08.220> the<15:43:08.700> network 15:43:08.926 --> 15:43:08.936 align:start position:0% policies is up to the network 15:43:08.936 --> 15:43:11.446 align:start position:0% policies is up to the network administrator<15:43:09.660> and<15:43:10.256> perhaps<15:43:10.616> this<15:43:11.160> Central 15:43:11.446 --> 15:43:11.456 align:start position:0% administrator and perhaps this Central 15:43:11.456 --> 15:43:14.926 align:start position:0% administrator and perhaps this Central information<15:43:11.756> officer<15:43:12.540> or<15:43:13.140> the<15:43:13.320> CIO<15:43:13.796> or<15:43:14.756> the 15:43:14.926 --> 15:43:14.936 align:start position:0% information officer or the CIO or the 15:43:14.936 --> 15:43:17.390 align:start position:0% information officer or the CIO or the Chief<15:43:15.240> Information<15:43:15.540> officer<15:43:16.860> now<15:43:17.276> it's 15:43:17.390 --> 15:43:17.400 align:start position:0% Chief Information officer now it's 15:43:17.400 --> 15:43:18.830 align:start position:0% Chief Information officer now it's common<15:43:17.580> to<15:43:17.756> have<15:43:17.880> a<15:43:18.000> system<15:43:18.116> configuration 15:43:18.830 --> 15:43:18.840 align:start position:0% common to have a system configuration 15:43:18.840 --> 15:43:21.350 align:start position:0% common to have a system configuration that<15:43:19.680> does<15:43:19.860> not<15:43:20.040> allow<15:43:20.340> users<15:43:20.820> to<15:43:21.000> remotely 15:43:21.350 --> 15:43:21.360 align:start position:0% that does not allow users to remotely 15:43:21.360 --> 15:43:23.570 align:start position:0% that does not allow users to remotely access<15:43:21.596> uh<15:43:22.500> the<15:43:22.796> system<15:43:22.980> after<15:43:23.276> a<15:43:23.456> certain 15:43:23.570 --> 15:43:23.580 align:start position:0% access uh the system after a certain 15:43:23.580 --> 15:43:24.890 align:start position:0% access uh the system after a certain time<15:43:23.820> at<15:43:23.936> night<15:43:24.116> I<15:43:24.360> might<15:43:24.480> want<15:43:24.596> to<15:43:24.660> do<15:43:24.776> this 15:43:24.890 --> 15:43:24.900 align:start position:0% time at night I might want to do this 15:43:24.900 --> 15:43:27.286 align:start position:0% time at night I might want to do this for<15:43:25.020> a<15:43:25.140> number<15:43:25.256> of<15:43:25.380> reasons<15:43:26.276> however<15:43:26.820> the 15:43:27.286 --> 15:43:27.296 align:start position:0% for a number of reasons however the 15:43:27.296 --> 15:43:29.030 align:start position:0% for a number of reasons however the policies<15:43:27.776> need<15:43:28.020> to<15:43:28.140> be<15:43:28.256> whatever<15:43:28.436> they<15:43:28.796> are 15:43:29.030 --> 15:43:29.040 align:start position:0% policies need to be whatever they are 15:43:29.040 --> 15:43:32.510 align:start position:0% policies need to be whatever they are well<15:43:29.520> documented<15:43:30.180> and<15:43:30.416> easy<15:43:30.660> to<15:43:30.900> understand<15:43:31.520> I 15:43:32.510 --> 15:43:32.520 align:start position:0% well documented and easy to understand I 15:43:32.520 --> 15:43:33.830 align:start position:0% well documented and easy to understand I need<15:43:32.640> to<15:43:32.756> know<15:43:32.936> exactly<15:43:33.360> how<15:43:33.596> I'm<15:43:33.720> going<15:43:33.840> to 15:43:33.830 --> 15:43:33.840 align:start position:0% need to know exactly how I'm going to 15:43:33.840 --> 15:43:35.390 align:start position:0% need to know exactly how I'm going to access<15:43:34.020> stuff<15:43:34.436> otherwise<15:43:35.040> what's<15:43:35.220> going<15:43:35.400> to 15:43:35.390 --> 15:43:35.400 align:start position:0% access stuff otherwise what's going to 15:43:35.400 --> 15:43:36.286 align:start position:0% access stuff otherwise what's going to happen<15:43:35.520> is<15:43:35.640> you're<15:43:35.820> going<15:43:35.936> to<15:43:35.936> say<15:43:36.060> hey<15:43:36.180> we 15:43:36.286 --> 15:43:36.296 align:start position:0% happen is you're going to say hey we 15:43:36.296 --> 15:43:38.210 align:start position:0% happen is you're going to say hey we have<15:43:36.416> remote<15:43:36.596> access<15:43:36.956> and<15:43:37.680> suddenly<15:43:38.040> people 15:43:38.210 --> 15:43:38.220 align:start position:0% have remote access and suddenly people 15:43:38.220 --> 15:43:39.350 align:start position:0% have remote access and suddenly people are<15:43:38.400> going<15:43:38.520> to<15:43:38.580> start<15:43:38.700> calling<15:43:38.936> the<15:43:39.060> help<15:43:39.180> desk 15:43:39.350 --> 15:43:39.360 align:start position:0% are going to start calling the help desk 15:43:39.360 --> 15:43:41.266 align:start position:0% are going to start calling the help desk saying<15:43:39.720> it's<15:43:39.776> not<15:43:39.956> working<15:43:40.200> properly 15:43:41.266 --> 15:43:41.276 align:start position:0% saying it's not working properly 15:43:41.276 --> 15:43:42.830 align:start position:0% saying it's not working properly we<15:43:41.756> also<15:43:42.000> want<15:43:42.116> to<15:43:42.240> make<15:43:42.296> sure<15:43:42.480> that<15:43:42.660> they're 15:43:42.830 --> 15:43:42.840 align:start position:0% we also want to make sure that they're 15:43:42.840 --> 15:43:44.086 align:start position:0% we also want to make sure that they're accountable<15:43:43.256> if<15:43:43.500> they<15:43:43.680> don't<15:43:43.860> follow 15:43:44.086 --> 15:43:44.096 align:start position:0% accountable if they don't follow 15:43:44.096 --> 15:43:47.446 align:start position:0% accountable if they don't follow specific<15:43:44.640> rules<15:43:45.060> policies<15:43:46.140> Etc<15:43:46.320> so<15:43:47.040> I<15:43:47.160> need<15:43:47.340> to 15:43:47.446 --> 15:43:47.456 align:start position:0% specific rules policies Etc so I need to 15:43:47.456 --> 15:43:49.310 align:start position:0% specific rules policies Etc so I need to say<15:43:47.520> if<15:43:47.700> someone<15:43:47.880> remotes<15:43:48.360> in<15:43:48.480> or<15:43:48.660> loses<15:43:49.080> their 15:43:49.310 --> 15:43:49.320 align:start position:0% say if someone remotes in or loses their 15:43:49.320 --> 15:43:52.130 align:start position:0% say if someone remotes in or loses their token<15:43:49.680> they<15:43:50.096> could<15:43:50.276> be<15:43:50.596> possibly<15:43:51.596> fired 15:43:52.130 --> 15:43:52.140 align:start position:0% token they could be possibly fired 15:43:52.140 --> 15:43:53.926 align:start position:0% token they could be possibly fired because<15:43:52.500> that's<15:43:52.860> a<15:43:52.980> huge<15:43:53.276> security<15:43:53.400> breach 15:43:53.926 --> 15:43:53.936 align:start position:0% because that's a huge security breach 15:43:53.936 --> 15:43:55.490 align:start position:0% because that's a huge security breach just<15:43:54.416> like<15:43:54.540> I<15:43:54.660> don't<15:43:54.720> want<15:43:54.840> to<15:43:54.900> give<15:43:55.020> my<15:43:55.200> laptop 15:43:55.490 --> 15:43:55.500 align:start position:0% just like I don't want to give my laptop 15:43:55.500 --> 15:43:57.710 align:start position:0% just like I don't want to give my laptop or<15:43:55.740> my<15:43:55.980> token<15:43:56.276> to<15:43:56.400> someone<15:43:56.640> even<15:43:57.296> if<15:43:57.480> it's<15:43:57.540> some 15:43:57.710 --> 15:43:57.720 align:start position:0% or my token to someone even if it's some 15:43:57.720 --> 15:43:58.906 align:start position:0% or my token to someone even if it's some within<15:43:58.020> the<15:43:58.140> network<15:43:58.256> if<15:43:58.500> I've<15:43:58.616> been<15:43:58.796> told 15:43:58.906 --> 15:43:58.916 align:start position:0% within the network if I've been told 15:43:58.916 --> 15:44:00.586 align:start position:0% within the network if I've been told specifically<15:43:59.520> to<15:43:59.756> keep<15:43:59.880> it<15:44:00.060> same<15:44:00.416> with 15:44:00.586 --> 15:44:00.596 align:start position:0% specifically to keep it same with 15:44:00.596 --> 15:44:02.746 align:start position:0% specifically to keep it same with passwords<15:44:01.140> usernames<15:44:01.740> basically<15:44:02.400> the<15:44:02.520> idea 15:44:02.746 --> 15:44:02.756 align:start position:0% passwords usernames basically the idea 15:44:02.756 --> 15:44:05.150 align:start position:0% passwords usernames basically the idea is<15:44:02.880> the<15:44:03.296> more<15:44:03.416> ability<15:44:04.200> I<15:44:04.500> give<15:44:04.680> people<15:44:04.860> the 15:44:05.150 --> 15:44:05.160 align:start position:0% is the more ability I give people the 15:44:05.160 --> 15:44:07.010 align:start position:0% is the more ability I give people the flexibility<15:44:05.520> I<15:44:05.756> get<15:44:05.880> people<15:44:06.000> to<15:44:06.240> connect<15:44:06.360> it 15:44:07.010 --> 15:44:07.020 align:start position:0% flexibility I get people to connect it 15:44:07.020 --> 15:44:09.230 align:start position:0% flexibility I get people to connect it also<15:44:07.256> makes<15:44:07.436> it<15:44:07.740> much<15:44:08.640> more<15:44:08.820> of<15:44:08.936> a<15:44:09.116> security 15:44:09.230 --> 15:44:09.240 align:start position:0% also makes it much more of a security 15:44:09.240 --> 15:44:10.370 align:start position:0% also makes it much more of a security hazard 15:44:10.370 --> 15:44:10.380 align:start position:0% hazard 15:44:10.380 --> 15:44:12.230 align:start position:0% hazard finally<15:44:11.160> you<15:44:11.520> need<15:44:11.580> to<15:44:11.700> make<15:44:11.820> sure<15:44:12.000> Human 15:44:12.230 --> 15:44:12.240 align:start position:0% finally you need to make sure Human 15:44:12.240 --> 15:44:14.446 align:start position:0% finally you need to make sure Human Resources<15:44:12.900> is<15:44:13.080> behind<15:44:13.436> all<15:44:13.680> of<15:44:13.796> your<15:44:13.980> policies 15:44:14.446 --> 15:44:14.456 align:start position:0% Resources is behind all of your policies 15:44:14.456 --> 15:44:15.830 align:start position:0% Resources is behind all of your policies they're<15:44:14.936> the<15:44:15.180> ones<15:44:15.296> who<15:44:15.480> are<15:44:15.540> going<15:44:15.660> to<15:44:15.776> be 15:44:15.830 --> 15:44:15.840 align:start position:0% they're the ones who are going to be 15:44:15.840 --> 15:44:18.230 align:start position:0% they're the ones who are going to be training<15:44:16.320> everyone<15:44:16.560> and<15:44:17.220> so<15:44:17.340> if<15:44:17.520> HR<15:44:17.936> isn't 15:44:18.230 --> 15:44:18.240 align:start position:0% training everyone and so if HR isn't 15:44:18.240 --> 15:44:19.606 align:start position:0% training everyone and so if HR isn't behind<15:44:18.540> you<15:44:18.660> you're<15:44:18.900> going<15:44:19.020> to<15:44:19.080> be<15:44:19.200> in<15:44:19.320> major 15:44:19.606 --> 15:44:19.616 align:start position:0% behind you you're going to be in major 15:44:19.616 --> 15:44:21.106 align:start position:0% behind you you're going to be in major issues<15:44:20.096> and<15:44:20.400> they're<15:44:20.520> going<15:44:20.700> to<15:44:20.820> fight<15:44:20.936> you 15:44:21.106 --> 15:44:21.116 align:start position:0% issues and they're going to fight you 15:44:21.116 --> 15:44:22.850 align:start position:0% issues and they're going to fight you the<15:44:21.296> whole<15:44:21.480> way<15:44:21.596> speaking<15:44:22.560> of<15:44:22.680> Human 15:44:22.850 --> 15:44:22.860 align:start position:0% the whole way speaking of Human 15:44:22.860 --> 15:44:25.190 align:start position:0% the whole way speaking of Human Resources<15:44:23.456> I<15:44:23.936> bet<15:44:24.180> it's<15:44:24.360> pretty<15:44:24.540> fair<15:44:24.720> to<15:44:24.956> say 15:44:25.190 --> 15:44:25.200 align:start position:0% Resources I bet it's pretty fair to say 15:44:25.200 --> 15:44:26.926 align:start position:0% Resources I bet it's pretty fair to say that<15:44:25.680> not<15:44:25.980> everyone<15:44:26.276> is<15:44:26.580> going<15:44:26.756> to<15:44:26.820> be 15:44:26.926 --> 15:44:26.936 align:start position:0% that not everyone is going to be 15:44:26.936 --> 15:44:29.990 align:start position:0% that not everyone is going to be qualified<15:44:27.416> or<15:44:27.840> knowledgeable<15:44:28.320> to<15:44:29.220> enough<15:44:29.456> to 15:44:29.990 --> 15:44:30.000 align:start position:0% qualified or knowledgeable to enough to 15:44:30.000 --> 15:44:32.266 align:start position:0% qualified or knowledgeable to enough to connect<15:44:30.116> to<15:44:30.416> remote<15:44:30.660> access<15:44:30.956> so<15:44:31.740> it's<15:44:32.040> really 15:44:32.266 --> 15:44:32.276 align:start position:0% connect to remote access so it's really 15:44:32.276 --> 15:44:34.906 align:start position:0% connect to remote access so it's really important<15:44:32.756> that<15:44:33.296> we<15:44:33.596> train<15:44:33.900> the<15:44:34.140> end<15:44:34.320> users<15:44:34.680> on 15:44:34.906 --> 15:44:34.916 align:start position:0% important that we train the end users on 15:44:34.916 --> 15:44:36.586 align:start position:0% important that we train the end users on what's<15:44:35.096> happening<15:44:35.520> on<15:44:35.700> their<15:44:35.820> end<15:44:36.060> and<15:44:36.480> how 15:44:36.586 --> 15:44:36.596 align:start position:0% what's happening on their end and how 15:44:36.596 --> 15:44:38.630 align:start position:0% what's happening on their end and how the<15:44:36.720> connection<15:44:36.900> works<15:44:37.500> it's<15:44:37.916> a<15:44:38.096> good<15:44:38.220> idea<15:44:38.456> to 15:44:38.630 --> 15:44:38.640 align:start position:0% the connection works it's a good idea to 15:44:38.640 --> 15:44:40.130 align:start position:0% the connection works it's a good idea to have<15:44:38.756> the<15:44:38.880> remote<15:44:39.000> users<15:44:39.416> learn<15:44:39.660> about<15:44:39.840> what's 15:44:40.130 --> 15:44:40.140 align:start position:0% have the remote users learn about what's 15:44:40.140 --> 15:44:42.170 align:start position:0% have the remote users learn about what's actually<15:44:40.436> happening<15:44:40.916> when<15:44:41.160> they<15:44:41.340> connect<15:44:41.520> and 15:44:42.170 --> 15:44:42.180 align:start position:0% actually happening when they connect and 15:44:42.180 --> 15:44:43.370 align:start position:0% actually happening when they connect and how<15:44:42.360> to<15:44:42.480> set<15:44:42.596> up<15:44:42.720> their<15:44:42.900> ends<15:44:43.200> of<15:44:43.256> the 15:44:43.370 --> 15:44:43.380 align:start position:0% how to set up their ends of the 15:44:43.380 --> 15:44:45.406 align:start position:0% how to set up their ends of the connections<15:44:43.860> otherwise<15:44:44.520> your<15:44:44.756> help<15:44:44.936> desk<15:44:45.116> is 15:44:45.406 --> 15:44:45.416 align:start position:0% connections otherwise your help desk is 15:44:45.416 --> 15:44:47.446 align:start position:0% connections otherwise your help desk is going<15:44:45.540> to<15:44:45.660> be<15:44:45.720> inundated<15:44:46.256> with<15:44:46.560> calls<15:44:46.980> and<15:44:47.276> not 15:44:47.446 --> 15:44:47.456 align:start position:0% going to be inundated with calls and not 15:44:47.456 --> 15:44:48.406 align:start position:0% going to be inundated with calls and not only<15:44:47.580> that<15:44:47.700> but<15:44:47.880> you're<15:44:48.000> gonna<15:44:48.060> have<15:44:48.180> a<15:44:48.240> lot<15:44:48.360> of 15:44:48.406 --> 15:44:48.416 align:start position:0% only that but you're gonna have a lot of 15:44:48.416 --> 15:44:49.670 align:start position:0% only that but you're gonna have a lot of people<15:44:48.540> upset<15:44:48.900> when<15:44:49.140> things<15:44:49.320> aren't<15:44:49.500> working 15:44:49.670 --> 15:44:49.680 align:start position:0% people upset when things aren't working 15:44:49.680 --> 15:44:51.286 align:start position:0% people upset when things aren't working properly<15:44:50.096> even<15:44:50.580> if<15:44:50.756> it's<15:44:50.880> something<15:44:51.060> that 15:44:51.286 --> 15:44:51.296 align:start position:0% properly even if it's something that 15:44:51.296 --> 15:44:52.670 align:start position:0% properly even if it's something that they<15:44:51.416> could<15:44:51.540> easily<15:44:51.900> fix 15:44:52.670 --> 15:44:52.680 align:start position:0% they could easily fix 15:44:52.680 --> 15:44:56.030 align:start position:0% they could easily fix so<15:44:53.340> like<15:44:53.700> the<15:44:53.936> job<15:44:54.180> of<15:44:54.840> an<15:44:55.256> admin<15:44:55.560> in<15:44:55.740> any<15:44:55.860> other 15:44:56.030 --> 15:44:56.040 align:start position:0% so like the job of an admin in any other 15:44:56.040 --> 15:44:58.490 align:start position:0% so like the job of an admin in any other case<15:44:56.276> it<15:44:56.580> falls<15:44:56.756> upon<15:44:57.180> your<15:44:57.540> shoulders<15:44:57.900> to 15:44:58.490 --> 15:44:58.500 align:start position:0% case it falls upon your shoulders to 15:44:58.500 --> 15:45:00.050 align:start position:0% case it falls upon your shoulders to help<15:44:58.680> users<15:44:59.096> when<15:44:59.400> there's<15:44:59.520> any<15:44:59.756> sort<15:44:59.936> of 15:45:00.050 --> 15:45:00.060 align:start position:0% help users when there's any sort of 15:45:00.060 --> 15:45:01.850 align:start position:0% help users when there's any sort of issue<15:45:00.480> this<15:45:01.080> will<15:45:01.256> become<15:45:01.436> a<15:45:01.616> lot<15:45:01.680> more 15:45:01.850 --> 15:45:01.860 align:start position:0% issue this will become a lot more 15:45:01.860 --> 15:45:04.310 align:start position:0% issue this will become a lot more difficult<15:45:02.220> when<15:45:02.520> the<15:45:02.700> admin<15:45:03.116> doesn't<15:45:03.480> go<15:45:04.080> over 15:45:04.310 --> 15:45:04.320 align:start position:0% difficult when the admin doesn't go over 15:45:04.320 --> 15:45:06.406 align:start position:0% difficult when the admin doesn't go over to<15:45:04.500> the<15:45:04.616> user's<15:45:04.916> desk<15:45:05.040> and<15:45:05.276> help<15:45:05.456> them<15:45:05.640> out<15:45:05.820> or 15:45:06.406 --> 15:45:06.416 align:start position:0% to the user's desk and help them out or 15:45:06.416 --> 15:45:07.550 align:start position:0% to the user's desk and help them out or doesn't<15:45:06.596> have<15:45:06.776> the<15:45:06.956> time<15:45:07.080> to<15:45:07.320> go<15:45:07.436> over 15:45:07.550 --> 15:45:07.560 align:start position:0% doesn't have the time to go over 15:45:07.560 --> 15:45:09.710 align:start position:0% doesn't have the time to go over hundreds<15:45:08.040> people<15:45:08.220> desks<15:45:08.820> you<15:45:09.480> have<15:45:09.596> to 15:45:09.710 --> 15:45:09.720 align:start position:0% hundreds people desks you have to 15:45:09.720 --> 15:45:11.446 align:start position:0% hundreds people desks you have to connect<15:45:09.900> with<15:45:10.256> the<15:45:10.436> user<15:45:10.740> in<15:45:10.860> some<15:45:11.096> other<15:45:11.220> way 15:45:11.446 --> 15:45:11.456 align:start position:0% connect with the user in some other way 15:45:11.456 --> 15:45:13.606 align:start position:0% connect with the user in some other way though<15:45:11.756> perhaps<15:45:12.180> it's<15:45:12.360> through<15:45:12.540> a<15:45:12.720> handout<15:45:13.080> or 15:45:13.606 --> 15:45:13.616 align:start position:0% though perhaps it's through a handout or 15:45:13.616 --> 15:45:15.890 align:start position:0% though perhaps it's through a handout or through<15:45:13.796> an<15:45:14.040> email<15:45:14.276> or<15:45:15.060> perhaps<15:45:15.360> you<15:45:15.540> remotely 15:45:15.890 --> 15:45:15.900 align:start position:0% through an email or perhaps you remotely 15:45:15.900 --> 15:45:18.830 align:start position:0% through an email or perhaps you remotely access<15:45:16.256> their<15:45:16.680> computer<15:45:17.000> or<15:45:18.000> even<15:45:18.180> give<15:45:18.596> the 15:45:18.830 --> 15:45:18.840 align:start position:0% access their computer or even give the 15:45:18.840 --> 15:45:21.370 align:start position:0% access their computer or even give the computers<15:45:19.200> to<15:45:19.380> them<15:45:19.560> set<15:45:19.796> up<15:45:19.916> already<15:45:20.276> to<15:45:20.820> to 15:45:21.370 --> 15:45:21.380 align:start position:0% computers to them set up already to to 15:45:21.380 --> 15:45:23.990 align:start position:0% computers to them set up already to to remotely<15:45:22.380> connect<15:45:22.560> or<15:45:23.160> talk<15:45:23.340> to<15:45:23.456> HR<15:45:23.820> about 15:45:23.990 --> 15:45:24.000 align:start position:0% remotely connect or talk to HR about 15:45:24.000 --> 15:45:26.210 align:start position:0% remotely connect or talk to HR about creating<15:45:24.416> some<15:45:24.660> sort<15:45:24.900> of<15:45:25.020> training<15:45:25.860> program 15:45:26.210 --> 15:45:26.220 align:start position:0% creating some sort of training program 15:45:26.220 --> 15:45:28.606 align:start position:0% creating some sort of training program that's<15:45:26.580> going<15:45:26.756> to<15:45:26.880> help<15:45:27.000> support<15:45:27.240> all<15:45:27.596> of<15:45:27.776> this 15:45:28.606 --> 15:45:28.616 align:start position:0% that's going to help support all of this 15:45:28.616 --> 15:45:30.650 align:start position:0% that's going to help support all of this finally<15:45:29.276> once<15:45:29.700> we've<15:45:29.820> set<15:45:30.000> all<15:45:30.116> this<15:45:30.296> up<15:45:30.416> we 15:45:30.650 --> 15:45:30.660 align:start position:0% finally once we've set all this up we 15:45:30.660 --> 15:45:32.690 align:start position:0% finally once we've set all this up we need<15:45:30.776> to<15:45:30.956> monitor<15:45:31.320> the<15:45:31.560> network<15:45:31.740> to<15:45:32.220> make<15:45:32.456> sure 15:45:32.690 --> 15:45:32.700 align:start position:0% need to monitor the network to make sure 15:45:32.700 --> 15:45:35.210 align:start position:0% need to monitor the network to make sure the<15:45:33.240> remote<15:45:33.416> access<15:45:33.660> is<15:45:34.020> working<15:45:34.256> as<15:45:34.740> intended 15:45:35.210 --> 15:45:35.220 align:start position:0% the remote access is working as intended 15:45:35.220 --> 15:45:37.850 align:start position:0% the remote access is working as intended the<15:45:36.116> first<15:45:36.360> step<15:45:36.596> towards<15:45:37.020> doing<15:45:37.200> this<15:45:37.436> is<15:45:37.680> to 15:45:37.850 --> 15:45:37.860 align:start position:0% the first step towards doing this is to 15:45:37.860 --> 15:45:40.490 align:start position:0% the first step towards doing this is to manage<15:45:38.160> all<15:45:38.640> of<15:45:38.756> the<15:45:38.936> entry<15:45:39.296> points<15:45:39.720> that<15:45:40.320> any 15:45:40.490 --> 15:45:40.500 align:start position:0% manage all of the entry points that any 15:45:40.500 --> 15:45:42.830 align:start position:0% manage all of the entry points that any of<15:45:40.616> the<15:45:40.740> users<15:45:41.040> could<15:45:41.276> use<15:45:41.520> it<15:45:42.296> should<15:45:42.480> be<15:45:42.596> kept 15:45:42.830 --> 15:45:42.840 align:start position:0% of the users could use it should be kept 15:45:42.840 --> 15:45:45.470 align:start position:0% of the users could use it should be kept down<15:45:42.956> to<15:45:43.200> one<15:45:43.680> single<15:45:44.160> access<15:45:44.456> point<15:45:45.000> and 15:45:45.470 --> 15:45:45.480 align:start position:0% down to one single access point and 15:45:45.480 --> 15:45:46.906 align:start position:0% down to one single access point and that's<15:45:45.540> important<15:45:45.956> because<15:45:46.200> obviously<15:45:46.740> it's 15:45:46.906 --> 15:45:46.916 align:start position:0% that's important because obviously it's 15:45:46.916 --> 15:45:48.890 align:start position:0% that's important because obviously it's easier<15:45:47.276> to<15:45:47.400> manage<15:45:47.700> one<15:45:47.880> access<15:45:48.116> point<15:45:48.480> than 15:45:48.890 --> 15:45:48.900 align:start position:0% easier to manage one access point than 15:45:48.900 --> 15:45:51.350 align:start position:0% easier to manage one access point than several<15:45:49.320> father<15:45:50.040> users<15:45:50.700> enter<15:45:51.000> the<15:45:51.240> network 15:45:51.350 --> 15:45:51.360 align:start position:0% several father users enter the network 15:45:51.360 --> 15:45:53.150 align:start position:0% several father users enter the network in<15:45:51.596> the<15:45:51.776> same<15:45:51.900> place<15:45:52.140> it's<15:45:52.436> going<15:45:52.796> to<15:45:52.916> be<15:45:52.980> a<15:45:53.096> lot 15:45:53.150 --> 15:45:53.160 align:start position:0% in the same place it's going to be a lot 15:45:53.160 --> 15:45:54.586 align:start position:0% in the same place it's going to be a lot easier<15:45:53.400> to<15:45:53.580> monitor<15:45:53.880> them 15:45:54.586 --> 15:45:54.596 align:start position:0% easier to monitor them 15:45:54.596 --> 15:45:56.330 align:start position:0% easier to monitor them next<15:45:55.200> we<15:45:55.380> need<15:45:55.560> to<15:45:55.616> make<15:45:55.796> sure<15:45:55.916> that<15:45:56.160> the 15:45:56.330 --> 15:45:56.340 align:start position:0% next we need to make sure that the 15:45:56.340 --> 15:45:58.246 align:start position:0% next we need to make sure that the policies<15:45:56.756> and<15:45:56.880> procedures<15:45:57.240> are<15:45:57.480> followed<15:45:57.840> so 15:45:58.246 --> 15:45:58.256 align:start position:0% policies and procedures are followed so 15:45:58.256 --> 15:45:59.926 align:start position:0% policies and procedures are followed so when<15:45:58.436> users<15:45:58.740> start<15:45:58.916> using<15:45:59.220> wrong<15:45:59.400> procedures 15:45:59.926 --> 15:45:59.936 align:start position:0% when users start using wrong procedures 15:45:59.936 --> 15:46:01.906 align:start position:0% when users start using wrong procedures don't<15:46:00.180> follow<15:46:00.416> the<15:46:00.660> policies<15:46:01.140> there's<15:46:01.680> a 15:46:01.906 --> 15:46:01.916 align:start position:0% don't follow the policies there's a 15:46:01.916 --> 15:46:02.926 align:start position:0% don't follow the policies there's a really<15:46:01.980> good<15:46:02.096> chance<15:46:02.276> something's<15:46:02.700> going<15:46:02.880> to 15:46:02.926 --> 15:46:02.936 align:start position:0% really good chance something's going to 15:46:02.936 --> 15:46:04.906 align:start position:0% really good chance something's going to go<15:46:03.060> wrong<15:46:03.180> and<15:46:03.900> it's<15:46:04.020> important<15:46:04.380> to<15:46:04.560> have<15:46:04.680> the 15:46:04.906 --> 15:46:04.916 align:start position:0% go wrong and it's important to have the 15:46:04.916 --> 15:46:07.010 align:start position:0% go wrong and it's important to have the remote<15:46:05.040> users<15:46:05.520> follow<15:46:05.820> a<15:46:06.240> strict<15:46:06.540> procedure 15:46:07.010 --> 15:46:07.020 align:start position:0% remote users follow a strict procedure 15:46:07.020 --> 15:46:09.170 align:start position:0% remote users follow a strict procedure in<15:46:07.200> order<15:46:07.320> to<15:46:07.500> avoid<15:46:07.796> any<15:46:08.096> problems<15:46:08.520> and<15:46:09.000> to 15:46:09.170 --> 15:46:09.180 align:start position:0% in order to avoid any problems and to 15:46:09.180 --> 15:46:10.970 align:start position:0% in order to avoid any problems and to help<15:46:09.296> take<15:46:09.480> the<15:46:09.720> load<15:46:10.020> off<15:46:10.256> of<15:46:10.380> you<15:46:10.560> and<15:46:10.796> the 15:46:10.970 --> 15:46:10.980 align:start position:0% help take the load off of you and the 15:46:10.980 --> 15:46:11.926 align:start position:0% help take the load off of you and the help<15:46:11.096> desk 15:46:11.926 --> 15:46:11.936 align:start position:0% help desk 15:46:11.936 --> 15:46:14.210 align:start position:0% help desk it's<15:46:12.776> also<15:46:13.200> very<15:46:13.560> important<15:46:13.916> to<15:46:14.040> understand 15:46:14.210 --> 15:46:14.220 align:start position:0% it's also very important to understand 15:46:14.220 --> 15:46:16.490 align:start position:0% it's also very important to understand everything<15:46:15.060> that's<15:46:15.416> going<15:46:15.660> on<15:46:15.840> within<15:46:16.320> the 15:46:16.490 --> 15:46:16.500 align:start position:0% everything that's going on within the 15:46:16.500 --> 15:46:17.926 align:start position:0% everything that's going on within the network<15:46:16.616> you<15:46:17.220> have<15:46:17.400> to<15:46:17.520> know<15:46:17.580> where<15:46:17.820> the 15:46:17.926 --> 15:46:17.936 align:start position:0% network you have to know where the 15:46:17.936 --> 15:46:20.266 align:start position:0% network you have to know where the connections<15:46:18.416> are<15:46:18.540> what<15:46:18.956> they're<15:46:19.140> doing<15:46:19.380> what 15:46:20.266 --> 15:46:20.276 align:start position:0% connections are what they're doing what 15:46:20.276 --> 15:46:22.190 align:start position:0% connections are what they're doing what the<15:46:20.456> users<15:46:20.756> are<15:46:20.936> up<15:46:21.116> to<15:46:21.296> you<15:46:21.840> have<15:46:22.020> to<15:46:22.080> keep 15:46:22.190 --> 15:46:22.200 align:start position:0% the users are up to you have to keep 15:46:22.200 --> 15:46:23.990 align:start position:0% the users are up to you have to keep track<15:46:22.500> of<15:46:22.740> all<15:46:22.980> of<15:46:23.096> this<15:46:23.276> stuff<15:46:23.520> and<15:46:23.756> there<15:46:23.880> are 15:46:23.990 --> 15:46:24.000 align:start position:0% track of all of this stuff and there are 15:46:24.000 --> 15:46:25.246 align:start position:0% track of all of this stuff and there are different<15:46:24.116> ways<15:46:24.480> to<15:46:24.660> do<15:46:24.776> this<15:46:24.956> different 15:46:25.246 --> 15:46:25.256 align:start position:0% different ways to do this different 15:46:25.256 --> 15:46:27.170 align:start position:0% different ways to do this different devices<15:46:25.680> we<15:46:25.980> can<15:46:26.096> deploy<15:46:26.400> and<15:46:26.580> software<15:46:27.000> that 15:46:27.170 --> 15:46:27.180 align:start position:0% devices we can deploy and software that 15:46:27.180 --> 15:46:29.086 align:start position:0% devices we can deploy and software that we'll<15:46:27.360> talk<15:46:27.596> about 15:46:29.086 --> 15:46:29.096 align:start position:0% we'll talk about 15:46:29.096 --> 15:46:31.490 align:start position:0% we'll talk about so<15:46:29.580> just<15:46:29.936> to<15:46:30.180> recap<15:46:30.540> we've<15:46:31.080> defined<15:46:31.320> what 15:46:31.490 --> 15:46:31.500 align:start position:0% so just to recap we've defined what 15:46:31.500 --> 15:46:35.030 align:start position:0% so just to recap we've defined what remote<15:46:31.680> access<15:46:32.040> is<15:46:32.456> what<15:46:33.240> it<15:46:33.416> is<15:46:33.616> what<15:46:34.616> it<15:46:34.796> does 15:46:35.030 --> 15:46:35.040 align:start position:0% remote access is what it is what it does 15:46:35.040 --> 15:46:38.390 align:start position:0% remote access is what it is what it does and<15:46:35.700> its<15:46:36.000> benefits<15:46:36.416> all<15:46:36.956> in<15:46:37.140> all<15:46:37.320> it<15:46:37.860> allows<15:46:38.220> us 15:46:38.390 --> 15:46:38.400 align:start position:0% and its benefits all in all it allows us 15:46:38.400 --> 15:46:41.810 align:start position:0% and its benefits all in all it allows us to<15:46:38.880> again<15:46:39.140> be<15:46:40.220> geographically<15:46:41.220> at<15:46:41.640> a 15:46:41.810 --> 15:46:41.820 align:start position:0% to again be geographically at a 15:46:41.820 --> 15:46:46.030 align:start position:0% to again be geographically at a different<15:46:42.000> location 15:46:46.030 --> 15:46:46.040 align:start position:0% 15:46:46.040 --> 15:46:51.650 align:start position:0% and<15:46:47.040> connect 15:46:51.650 --> 15:46:51.660 align:start position:0% 15:46:51.660 --> 15:46:54.170 align:start position:0% to<15:46:52.140> the<15:46:52.256> lamp 15:46:54.170 --> 15:46:54.180 align:start position:0% to the lamp 15:46:54.180 --> 15:46:55.970 align:start position:0% to the lamp we<15:46:54.720> also<15:46:54.900> talked<15:46:55.140> about<15:46:55.200> lots<15:46:55.560> of<15:46:55.616> the<15:46:55.740> steps 15:46:55.970 --> 15:46:55.980 align:start position:0% we also talked about lots of the steps 15:46:55.980 --> 15:46:58.246 align:start position:0% we also talked about lots of the steps of<15:46:56.160> implementation<15:46:56.756> and<15:46:57.660> although<15:46:57.956> this 15:46:58.246 --> 15:46:58.256 align:start position:0% of implementation and although this 15:46:58.256 --> 15:46:59.630 align:start position:0% of implementation and although this isn't<15:46:58.500> very<15:46:58.680> technical<15:46:59.040> all<15:46:59.340> this<15:46:59.456> stuff 15:46:59.630 --> 15:46:59.640 align:start position:0% isn't very technical all this stuff 15:46:59.640 --> 15:47:01.670 align:start position:0% isn't very technical all this stuff comes<15:46:59.880> up<15:46:59.936> on<15:47:00.116> the<15:47:00.240> network<15:47:00.360> plus<15:47:00.660> exam<15:47:01.140> you 15:47:01.670 --> 15:47:01.680 align:start position:0% comes up on the network plus exam you 15:47:01.680 --> 15:47:02.990 align:start position:0% comes up on the network plus exam you have<15:47:01.796> to<15:47:01.916> know<15:47:02.096> what<15:47:02.400> it<15:47:02.520> is<15:47:02.640> you're<15:47:02.820> supposed 15:47:02.990 --> 15:47:03.000 align:start position:0% have to know what it is you're supposed 15:47:03.000 --> 15:47:05.030 align:start position:0% have to know what it is you're supposed to<15:47:03.180> do<15:47:03.296> so<15:47:03.840> remember<15:47:03.956> we<15:47:04.256> talked<15:47:04.560> about<15:47:04.616> some 15:47:05.030 --> 15:47:05.040 align:start position:0% to do so remember we talked about some 15:47:05.040 --> 15:47:07.100 align:start position:0% to do so remember we talked about some policies<15:47:05.700> procedures 15:47:07.100 --> 15:47:07.110 align:start position:0% policies procedures 15:47:07.110 --> 15:47:09.170 align:start position:0% policies procedures [Music] 15:47:09.170 --> 15:47:09.180 align:start position:0% [Music] 15:47:09.180 --> 15:47:13.190 align:start position:0% [Music] training 15:47:13.190 --> 15:47:13.200 align:start position:0% 15:47:13.200 --> 15:47:16.426 align:start position:0% and<15:47:13.916> monitoring 15:47:16.426 --> 15:47:16.436 align:start position:0% and monitoring 15:47:16.436 --> 15:47:18.170 align:start position:0% and monitoring now<15:47:17.096> in<15:47:17.340> the<15:47:17.456> next<15:47:17.520> module<15:47:17.880> we're<15:47:18.000> going<15:47:18.116> to 15:47:18.170 --> 15:47:18.180 align:start position:0% now in the next module we're going to 15:47:18.180 --> 15:47:19.730 align:start position:0% now in the next module we're going to talk<15:47:18.296> more<15:47:18.540> specifically<15:47:18.900> about<15:47:19.080> how<15:47:19.436> we<15:47:19.560> set 15:47:19.730 --> 15:47:19.740 align:start position:0% talk more specifically about how we set 15:47:19.740 --> 15:47:21.050 align:start position:0% talk more specifically about how we set some<15:47:19.916> of<15:47:20.040> this<15:47:20.160> stuff<15:47:20.276> up<15:47:20.520> and<15:47:20.820> what<15:47:20.936> we're 15:47:21.050 --> 15:47:21.060 align:start position:0% some of this stuff up and what we're 15:47:21.060 --> 15:47:22.730 align:start position:0% some of this stuff up and what we're going<15:47:21.240> to<15:47:21.360> do<15:47:21.480> to<15:47:22.080> make<15:47:22.200> sure<15:47:22.320> it<15:47:22.436> works 15:47:22.730 --> 15:47:22.740 align:start position:0% going to do to make sure it works 15:47:22.740 --> 15:47:28.270 align:start position:0% going to do to make sure it works properly 15:47:28.270 --> 15:47:28.280 align:start position:0% 15:47:28.280 --> 15:47:45.350 align:start position:0% [Music] 15:47:45.350 --> 15:47:45.360 align:start position:0% 15:47:45.360 --> 15:47:48.710 align:start position:0% welcome<15:47:45.776> to<15:47:46.020> module<15:47:46.380> 10<15:47:46.560> lesson<15:47:47.160> 2A<15:47:48.060> a<15:47:48.540> remote 15:47:48.710 --> 15:47:48.720 align:start position:0% welcome to module 10 lesson 2A a remote 15:47:48.720 --> 15:47:50.810 align:start position:0% welcome to module 10 lesson 2A a remote access<15:47:49.140> methods 15:47:50.810 --> 15:47:50.820 align:start position:0% access methods 15:47:50.820 --> 15:47:53.086 align:start position:0% access methods so<15:47:51.296> remote<15:47:51.480> access<15:47:51.776> is<15:47:52.140> all<15:47:52.320> about<15:47:52.500> how<15:47:52.916> you 15:47:53.086 --> 15:47:53.096 align:start position:0% so remote access is all about how you 15:47:53.096 --> 15:47:55.606 align:start position:0% so remote access is all about how you can<15:47:53.220> reach<15:47:53.580> various<15:47:54.000> network<15:47:54.240> devices<15:47:54.900> when 15:47:55.606 --> 15:47:55.616 align:start position:0% can reach various network devices when 15:47:55.616 --> 15:47:59.150 align:start position:0% can reach various network devices when you're<15:47:55.796> not<15:47:55.916> at<15:47:56.276> the<15:47:56.520> physical<15:47:56.756> location 15:47:59.150 --> 15:47:59.160 align:start position:0% you're not at the physical location 15:47:59.160 --> 15:48:03.586 align:start position:0% you're not at the physical location look<15:47:59.700> at<15:47:59.820> RDP<15:48:00.416> SSH<15:48:01.380> VNC 15:48:03.586 --> 15:48:03.596 align:start position:0% look at RDP SSH VNC 15:48:03.596 --> 15:48:08.990 align:start position:0% look at RDP SSH VNC telnet<15:48:04.580> management<15:48:05.580> through<15:48:06.000> the<15:48:06.180> https 15:48:08.990 --> 15:48:09.000 align:start position:0% telnet management through the https 15:48:09.000 --> 15:48:12.710 align:start position:0% telnet management through the https and<15:48:09.540> file<15:48:09.776> access<15:48:10.160> and<15:48:11.160> then<15:48:11.276> outer<15:48:11.700> band 15:48:12.710 --> 15:48:12.720 align:start position:0% and file access and then outer band 15:48:12.720 --> 15:48:16.606 align:start position:0% and file access and then outer band RDP<15:48:13.616> this<15:48:14.400> is<15:48:14.580> uh<15:48:15.416> proprietary<15:48:15.956> to<15:48:16.200> Microsoft 15:48:16.606 --> 15:48:16.616 align:start position:0% RDP this is uh proprietary to Microsoft 15:48:16.616 --> 15:48:18.530 align:start position:0% RDP this is uh proprietary to Microsoft so<15:48:16.860> they've<15:48:17.276> come<15:48:17.580> up<15:48:17.700> with<15:48:17.820> this<15:48:18.060> software 15:48:18.530 --> 15:48:18.540 align:start position:0% so they've come up with this software 15:48:18.540 --> 15:48:21.286 align:start position:0% so they've come up with this software you<15:48:19.200> may<15:48:19.320> have<15:48:19.436> seen<15:48:19.560> it<15:48:19.680> before<15:48:19.860> when<15:48:20.276> you<15:48:20.520> can 15:48:21.286 --> 15:48:21.296 align:start position:0% you may have seen it before when you can 15:48:21.296 --> 15:48:22.926 align:start position:0% you may have seen it before when you can um<15:48:21.360> if<15:48:21.720> you<15:48:21.776> check<15:48:21.956> on<15:48:22.140> your<15:48:22.320> Windows<15:48:22.680> machine 15:48:22.926 --> 15:48:22.936 align:start position:0% um if you check on your Windows machine 15:48:22.936 --> 15:48:24.946 align:start position:0% um if you check on your Windows machine you<15:48:23.936> can<15:48:24.000> normally 15:48:24.946 --> 15:48:24.956 align:start position:0% you can normally 15:48:24.956 --> 15:48:28.070 align:start position:0% you can normally and<15:48:25.740> find<15:48:26.040> the<15:48:26.340> uh 15:48:28.070 --> 15:48:28.080 align:start position:0% and find the uh 15:48:28.080 --> 15:48:30.586 align:start position:0% and find the uh the<15:48:28.560> button<15:48:28.796> to<15:48:28.980> click<15:48:29.340> that<15:48:30.000> it<15:48:30.180> will<15:48:30.296> allow 15:48:30.586 --> 15:48:30.596 align:start position:0% the button to click that it will allow 15:48:30.596 --> 15:48:32.210 align:start position:0% the button to click that it will allow you<15:48:30.720> to<15:48:30.900> connect<15:48:31.140> to<15:48:31.320> a<15:48:31.500> remote<15:48:31.616> computer<15:48:31.916> and 15:48:32.210 --> 15:48:32.220 align:start position:0% you to connect to a remote computer and 15:48:32.220 --> 15:48:33.710 align:start position:0% you to connect to a remote computer and you<15:48:32.340> might<15:48:32.400> use<15:48:32.580> this<15:48:32.700> if<15:48:32.880> you<15:48:33.000> work<15:48:33.116> in<15:48:33.296> a<15:48:33.416> harp 15:48:33.710 --> 15:48:33.720 align:start position:0% you might use this if you work in a harp 15:48:33.720 --> 15:48:36.170 align:start position:0% you might use this if you work in a harp desk<15:48:33.840> if<15:48:34.560> you<15:48:34.680> need<15:48:34.796> to<15:48:35.096> support<15:48:35.520> a<15:48:36.000> remote 15:48:36.170 --> 15:48:36.180 align:start position:0% desk if you need to support a remote 15:48:36.180 --> 15:48:38.390 align:start position:0% desk if you need to support a remote user 15:48:38.390 --> 15:48:38.400 align:start position:0% user 15:48:38.400 --> 15:48:40.426 align:start position:0% user you<15:48:38.820> can<15:48:38.880> have<15:48:39.000> remote<15:48:39.296> access<15:48:39.660> and<15:48:40.200> control 15:48:40.426 --> 15:48:40.436 align:start position:0% you can have remote access and control 15:48:40.436 --> 15:48:43.246 align:start position:0% you can have remote access and control via<15:48:40.980> screen<15:48:41.220> sharing 15:48:43.246 --> 15:48:43.256 align:start position:0% via screen sharing 15:48:43.256 --> 15:48:45.050 align:start position:0% via screen sharing this<15:48:43.740> is<15:48:43.860> actually<15:48:44.040> how<15:48:44.220> a<15:48:44.400> lot<15:48:44.520> of<15:48:44.640> scammers 15:48:45.050 --> 15:48:45.060 align:start position:0% this is actually how a lot of scammers 15:48:45.060 --> 15:48:46.670 align:start position:0% this is actually how a lot of scammers will 15:48:46.670 --> 15:48:46.680 align:start position:0% will 15:48:46.680 --> 15:48:49.490 align:start position:0% will get<15:48:47.520> people<15:48:47.756> to<15:48:48.296> hand<15:48:48.596> over<15:48:48.840> remote<15:48:49.140> control 15:48:49.490 --> 15:48:49.500 align:start position:0% get people to hand over remote control 15:48:49.500 --> 15:48:52.246 align:start position:0% get people to hand over remote control they'll<15:48:49.916> phone<15:48:50.220> somebody<15:48:50.596> who's<15:48:51.596> a<15:48:51.840> bit<15:48:51.956> naive 15:48:52.246 --> 15:48:52.256 align:start position:0% they'll phone somebody who's a bit naive 15:48:52.256 --> 15:48:54.406 align:start position:0% they'll phone somebody who's a bit naive and<15:48:52.560> say<15:48:53.160> um<15:48:53.160> we've<15:48:53.580> found<15:48:53.756> a<15:48:53.936> technical<15:48:54.180> floor 15:48:54.406 --> 15:48:54.416 align:start position:0% and say um we've found a technical floor 15:48:54.416 --> 15:48:57.650 align:start position:0% and say um we've found a technical floor in<15:48:54.720> your<15:48:54.840> computer<15:48:55.160> and<15:48:56.160> Handover<15:48:56.640> can<15:48:57.540> you 15:48:57.650 --> 15:48:57.660 align:start position:0% in your computer and Handover can you 15:48:57.660 --> 15:49:00.530 align:start position:0% in your computer and Handover can you hand<15:48:57.776> over<15:48:57.956> access<15:48:58.200> so<15:48:58.500> we<15:48:58.680> can<15:48:58.796> fix<15:48:59.040> it 15:49:00.530 --> 15:49:00.540 align:start position:0% hand over access so we can fix it 15:49:00.540 --> 15:49:03.406 align:start position:0% hand over access so we can fix it typical<15:49:01.200> exam<15:49:01.560> question<15:49:01.796> would<15:49:02.276> be<15:49:02.456> what<15:49:03.180> port 15:49:03.406 --> 15:49:03.416 align:start position:0% typical exam question would be what port 15:49:03.416 --> 15:49:05.510 align:start position:0% typical exam question would be what port does<15:49:03.720> it<15:49:03.900> use<15:49:04.020> it's<15:49:04.320> TCP<15:49:04.916> it<15:49:05.096> has<15:49:05.276> to<15:49:05.400> be 15:49:05.510 --> 15:49:05.520 align:start position:0% does it use it's TCP it has to be 15:49:05.520 --> 15:49:07.850 align:start position:0% does it use it's TCP it has to be reliable<15:49:05.880> obviously<15:49:06.416> and<15:49:07.080> the<15:49:07.256> port<15:49:07.380> is<15:49:07.680> three 15:49:07.850 --> 15:49:07.860 align:start position:0% reliable obviously and the port is three 15:49:07.860 --> 15:49:09.350 align:start position:0% reliable obviously and the port is three three<15:49:08.096> eight<15:49:08.340> nine 15:49:09.350 --> 15:49:09.360 align:start position:0% three eight nine 15:49:09.360 --> 15:49:10.906 align:start position:0% three eight nine you<15:49:09.776> need<15:49:09.900> to<15:49:10.020> know<15:49:10.140> this<15:49:10.320> kind<15:49:10.436> of<15:49:10.560> stuff<15:49:10.680> if 15:49:10.906 --> 15:49:10.916 align:start position:0% you need to know this kind of stuff if 15:49:10.916 --> 15:49:12.946 align:start position:0% you need to know this kind of stuff if you<15:49:11.040> need<15:49:11.220> to<15:49:11.400> permit<15:49:11.820> this<15:49:12.360> through<15:49:12.660> your 15:49:12.946 --> 15:49:12.956 align:start position:0% you need to permit this through your 15:49:12.956 --> 15:49:14.150 align:start position:0% you need to permit this through your firewall 15:49:14.150 --> 15:49:14.160 align:start position:0% firewall 15:49:14.160 --> 15:49:16.246 align:start position:0% firewall or<15:49:14.520> deny<15:49:14.820> obviously 15:49:16.246 --> 15:49:16.256 align:start position:0% or deny obviously 15:49:16.256 --> 15:49:18.830 align:start position:0% or deny obviously now<15:49:16.616> the<15:49:16.796> client<15:49:17.040> side<15:49:17.276> can<15:49:17.640> be<15:49:17.820> Windows<15:49:18.596> Mac 15:49:18.830 --> 15:49:18.840 align:start position:0% now the client side can be Windows Mac 15:49:18.840 --> 15:49:20.470 align:start position:0% now the client side can be Windows Mac or<15:49:19.140> Linux<15:49:19.500> there's<15:49:19.740> a<15:49:19.980> few<15:49:20.096> different 15:49:20.470 --> 15:49:20.480 align:start position:0% or Linux there's a few different 15:49:20.480 --> 15:49:24.650 align:start position:0% or Linux there's a few different operating<15:49:21.480> systems<15:49:21.900> that<15:49:22.080> are<15:49:22.256> supported 15:49:24.650 --> 15:49:24.660 align:start position:0% operating systems that are supported 15:49:24.660 --> 15:49:26.810 align:start position:0% operating systems that are supported SSH 15:49:26.810 --> 15:49:26.820 align:start position:0% SSH 15:49:26.820 --> 15:49:29.990 align:start position:0% SSH this<15:49:27.540> allows<15:49:28.200> remote<15:49:28.680> terminal<15:49:29.340> access<15:49:29.580> by 15:49:29.990 --> 15:49:30.000 align:start position:0% this allows remote terminal access by 15:49:30.000 --> 15:49:32.746 align:start position:0% this allows remote terminal access by terminal<15:49:30.360> we<15:49:30.776> mean<15:49:31.020> a<15:49:31.740> window<15:49:32.096> like<15:49:32.520> this 15:49:32.746 --> 15:49:32.756 align:start position:0% terminal we mean a window like this 15:49:32.756 --> 15:49:35.810 align:start position:0% terminal we mean a window like this where<15:49:33.060> you've<15:49:33.296> got<15:49:33.480> command<15:49:33.900> line<15:49:34.080> access<15:49:34.820> to 15:49:35.810 --> 15:49:35.820 align:start position:0% where you've got command line access to 15:49:35.820 --> 15:49:38.926 align:start position:0% where you've got command line access to a<15:49:36.296> remote<15:49:36.900> computer<15:49:37.380> server 15:49:38.926 --> 15:49:38.936 align:start position:0% a remote computer server 15:49:38.936 --> 15:49:41.210 align:start position:0% a remote computer server or<15:49:39.840> in<15:49:40.256> this<15:49:40.380> case<15:49:40.500> I'm<15:49:40.680> not<15:49:40.740> sure<15:49:40.916> what<15:49:41.040> this 15:49:41.210 --> 15:49:41.220 align:start position:0% or in this case I'm not sure what this 15:49:41.220 --> 15:49:43.370 align:start position:0% or in this case I'm not sure what this is<15:49:41.340> actually<15:49:41.580> it<15:49:41.880> could<15:49:42.000> be<15:49:42.180> a<15:49:42.416> Cisco<15:49:43.140> device 15:49:43.370 --> 15:49:43.380 align:start position:0% is actually it could be a Cisco device 15:49:43.380 --> 15:49:45.586 align:start position:0% is actually it could be a Cisco device of<15:49:43.680> some<15:49:43.860> sort 15:49:45.586 --> 15:49:45.596 align:start position:0% of some sort 15:49:45.596 --> 15:49:47.630 align:start position:0% of some sort it<15:49:46.140> encrypts<15:49:46.560> communication<15:49:46.980> between<15:49:47.340> the 15:49:47.630 --> 15:49:47.640 align:start position:0% it encrypts communication between the 15:49:47.640 --> 15:49:51.530 align:start position:0% it encrypts communication between the endpoint<15:49:48.000> so<15:49:48.500> most<15:49:49.500> places<15:49:49.796> now<15:49:50.456> you<15:49:51.296> can't 15:49:51.530 --> 15:49:51.540 align:start position:0% endpoint so most places now you can't 15:49:51.540 --> 15:49:54.406 align:start position:0% endpoint so most places now you can't tell<15:49:51.956> Nets<15:49:52.436> across<15:49:52.740> the<15:49:52.796> network 15:49:54.406 --> 15:49:54.416 align:start position:0% tell Nets across the network 15:49:54.416 --> 15:49:56.870 align:start position:0% tell Nets across the network you<15:49:55.020> uh<15:49:55.256> because<15:49:55.436> it's<15:49:55.740> all<15:49:56.220> traffic<15:49:56.456> is<15:49:56.700> sent 15:49:56.870 --> 15:49:56.880 align:start position:0% you uh because it's all traffic is sent 15:49:56.880 --> 15:49:58.606 align:start position:0% you uh because it's all traffic is sent in<15:49:57.060> clear<15:49:57.180> text<15:49:57.416> you<15:49:57.720> have<15:49:57.900> to<15:49:58.020> use<15:49:58.200> secure 15:49:58.606 --> 15:49:58.616 align:start position:0% in clear text you have to use secure 15:49:58.616 --> 15:50:02.030 align:start position:0% in clear text you have to use secure shell<15:49:58.980> as<15:49:59.276> part<15:49:59.456> of<15:49:59.640> the<15:49:59.956> policy<15:50:00.956> the<15:50:01.796> network 15:50:02.030 --> 15:50:02.040 align:start position:0% shell as part of the policy the network 15:50:02.040 --> 15:50:03.710 align:start position:0% shell as part of the policy the network policy 15:50:03.710 --> 15:50:03.720 align:start position:0% policy 15:50:03.720 --> 15:50:06.830 align:start position:0% policy in<15:50:04.256> order<15:50:04.380> to<15:50:04.680> use<15:50:04.916> the<15:50:05.160> Kershaw<15:50:05.820> you<15:50:06.540> have<15:50:06.720> to 15:50:06.830 --> 15:50:06.840 align:start position:0% in order to use the Kershaw you have to 15:50:06.840 --> 15:50:08.570 align:start position:0% in order to use the Kershaw you have to enable<15:50:07.080> it<15:50:07.256> on<15:50:07.500> your<15:50:07.680> server<15:50:08.040> router<15:50:08.456> or 15:50:08.570 --> 15:50:08.580 align:start position:0% enable it on your server router or 15:50:08.580 --> 15:50:10.970 align:start position:0% enable it on your server router or switch<15:50:08.820> it<15:50:09.116> isn't<15:50:09.540> usually<15:50:09.956> enabled<15:50:10.796> by 15:50:10.970 --> 15:50:10.980 align:start position:0% switch it isn't usually enabled by 15:50:10.980 --> 15:50:12.286 align:start position:0% switch it isn't usually enabled by default 15:50:12.286 --> 15:50:12.296 align:start position:0% default 15:50:12.296 --> 15:50:15.286 align:start position:0% default the<15:50:12.840> client<15:50:13.020> software<15:50:13.500> you<15:50:13.796> install<15:50:14.040> on<15:50:14.820> your 15:50:15.286 --> 15:50:15.296 align:start position:0% the client software you install on your 15:50:15.296 --> 15:50:16.786 align:start position:0% the client software you install on your computer 15:50:16.786 --> 15:50:16.796 align:start position:0% computer 15:50:16.796 --> 15:50:20.446 align:start position:0% computer the<15:50:17.456> one<15:50:17.520> I<15:50:17.700> use<15:50:17.936> mostly<15:50:18.740> to<15:50:19.740> get<15:50:19.980> my<15:50:20.220> remote 15:50:20.446 --> 15:50:20.456 align:start position:0% the one I use mostly to get my remote 15:50:20.456 --> 15:50:24.766 align:start position:0% the one I use mostly to get my remote secure<15:50:21.240> uh<15:50:22.140> shell<15:50:22.860> sessions<15:50:23.220> is<15:50:23.580> putty<15:50:24.180> it's<15:50:24.660> a 15:50:24.766 --> 15:50:24.776 align:start position:0% secure uh shell sessions is putty it's a 15:50:24.776 --> 15:50:26.990 align:start position:0% secure uh shell sessions is putty it's a free<15:50:24.956> download<15:50:25.200> if<15:50:25.980> you<15:50:26.160> Google<15:50:26.340> putty<15:50:26.880> I 15:50:26.990 --> 15:50:27.000 align:start position:0% free download if you Google putty I 15:50:27.000 --> 15:50:29.150 align:start position:0% free download if you Google putty I think<15:50:27.116> it's<15:50:27.180> pretty.org<15:50:28.080> you<15:50:28.380> got<15:50:28.500> to<15:50:28.616> you<15:50:28.980> get 15:50:29.150 --> 15:50:29.160 align:start position:0% think it's pretty.org you got to you get 15:50:29.160 --> 15:50:31.246 align:start position:0% think it's pretty.org you got to you get taken<15:50:29.456> to 15:50:31.246 --> 15:50:31.256 align:start position:0% taken to 15:50:31.256 --> 15:50:33.470 align:start position:0% taken to BNC<15:50:32.040> I<15:50:32.276> used<15:50:32.456> this<15:50:32.640> a<15:50:32.756> while<15:50:32.880> ago<15:50:33.180> when<15:50:33.240> I<15:50:33.416> was 15:50:33.470 --> 15:50:33.480 align:start position:0% BNC I used this a while ago when I was 15:50:33.480 --> 15:50:35.810 align:start position:0% BNC I used this a while ago when I was at<15:50:33.596> holiday<15:50:33.776> and<15:50:34.080> needed<15:50:34.380> to<15:50:34.500> connect<15:50:35.276> to<15:50:35.520> my 15:50:35.810 --> 15:50:35.820 align:start position:0% at holiday and needed to connect to my 15:50:35.820 --> 15:50:38.390 align:start position:0% at holiday and needed to connect to my work<15:50:36.416> computer<15:50:36.860> this<15:50:37.860> is<15:50:37.980> platform 15:50:38.390 --> 15:50:38.400 align:start position:0% work computer this is platform 15:50:38.400 --> 15:50:44.330 align:start position:0% work computer this is platform independent<15:50:39.116> it's<15:50:40.020> a<15:50:40.256> GUI<15:50:40.616> based 15:50:44.330 --> 15:50:44.340 align:start position:0% 15:50:44.340 --> 15:50:46.070 align:start position:0% which<15:50:44.820> is<15:50:44.936> pretty<15:50:45.116> handy<15:50:45.480> if<15:50:45.596> you're<15:50:45.776> not<15:50:45.900> too 15:50:46.070 --> 15:50:46.080 align:start position:0% which is pretty handy if you're not too 15:50:46.080 --> 15:50:48.050 align:start position:0% which is pretty handy if you're not too familiar<15:50:46.436> with<15:50:46.616> command<15:50:47.040> line<15:50:47.160> desktop 15:50:48.050 --> 15:50:48.060 align:start position:0% familiar with command line desktop 15:50:48.060 --> 15:50:51.710 align:start position:0% familiar with command line desktop sharing<15:50:48.596> it<15:50:49.436> uses<15:50:49.680> remote<15:50:49.980> frame<15:50:50.456> buffer<15:50:50.820> to<15:50:51.360> a 15:50:51.710 --> 15:50:51.720 align:start position:0% sharing it uses remote frame buffer to a 15:50:51.720 --> 15:50:55.490 align:start position:0% sharing it uses remote frame buffer to a remote<15:50:51.956> controller<15:50:52.560> computer 15:50:55.490 --> 15:50:55.500 align:start position:0% 15:50:55.500 --> 15:50:58.310 align:start position:0% all<15:50:55.980> right<15:50:56.040> you<15:50:56.220> get<15:50:56.340> the<15:50:56.456> TCP<15:50:57.000> Port<15:50:57.240> basic<15:50:57.840> uh 15:50:58.310 --> 15:50:58.320 align:start position:0% all right you get the TCP Port basic uh 15:50:58.320 --> 15:51:00.946 align:start position:0% all right you get the TCP Port basic uh the<15:50:58.500> port<15:50:58.616> is<15:50:59.276> um<15:50:59.276> 5900<15:51:00.180> and<15:51:00.480> then<15:51:00.596> there's<15:51:00.776> a 15:51:00.946 --> 15:51:00.956 align:start position:0% the port is um 5900 and then there's a 15:51:00.956 --> 15:51:02.570 align:start position:0% the port is um 5900 and then there's a number<15:51:01.080> the<15:51:01.436> number<15:51:01.616> will<15:51:01.916> you<15:51:02.220> check<15:51:02.456> the 15:51:02.570 --> 15:51:02.580 align:start position:0% number the number will you check the 15:51:02.580 --> 15:51:03.890 align:start position:0% number the number will you check the documentation<15:51:03.060> but<15:51:03.360> there's<15:51:03.540> various 15:51:03.890 --> 15:51:03.900 align:start position:0% documentation but there's various 15:51:03.900 --> 15:51:06.586 align:start position:0% documentation but there's various numbers<15:51:04.276> you<15:51:05.276> will<15:51:05.700> be<15:51:05.880> using<15:51:06.116> depending<15:51:06.540> on 15:51:06.586 --> 15:51:06.596 align:start position:0% numbers you will be using depending on 15:51:06.596 --> 15:51:09.230 align:start position:0% numbers you will be using depending on what<15:51:07.020> you're<15:51:07.980> connecting<15:51:08.520> to<15:51:08.700> and<15:51:08.936> how<15:51:09.116> you 15:51:09.230 --> 15:51:09.240 align:start position:0% what you're connecting to and how you 15:51:09.240 --> 15:51:12.106 align:start position:0% what you're connecting to and how you want<15:51:09.360> to<15:51:09.480> connect 15:51:12.106 --> 15:51:12.116 align:start position:0% 15:51:12.116 --> 15:51:16.606 align:start position:0% now telnet<15:51:13.040> is<15:51:14.040> uh<15:51:14.640> TCP<15:51:15.540> protocol<15:51:16.020> is<15:51:16.380> used 15:51:16.606 --> 15:51:16.616 align:start position:0% now telnet is uh TCP protocol is used 15:51:16.616 --> 15:51:19.190 align:start position:0% now telnet is uh TCP protocol is used for<15:51:16.796> remote<15:51:16.916> access<15:51:17.276> I<15:51:17.756> did<15:51:17.936> mention<15:51:18.116> SSH<15:51:18.660> so 15:51:19.190 --> 15:51:19.200 align:start position:0% for remote access I did mention SSH so 15:51:19.200 --> 15:51:22.850 align:start position:0% for remote access I did mention SSH so really<15:51:19.640> tell<15:51:20.640> net<15:51:20.880> you'd<15:51:21.240> use<15:51:21.360> it<15:51:21.540> at<15:51:21.720> home<15:51:21.956> if 15:51:22.850 --> 15:51:22.860 align:start position:0% really tell net you'd use it at home if 15:51:22.860 --> 15:51:24.830 align:start position:0% really tell net you'd use it at home if you've<15:51:22.980> got<15:51:23.220> a<15:51:23.640> rack<15:51:24.060> or<15:51:24.296> something<15:51:24.480> you<15:51:24.720> want 15:51:24.830 --> 15:51:24.840 align:start position:0% you've got a rack or something you want 15:51:24.840 --> 15:51:26.630 align:start position:0% you've got a rack or something you want to<15:51:24.956> troubleshoot<15:51:25.560> you<15:51:25.980> would<15:51:26.096> never<15:51:26.276> use<15:51:26.456> this 15:51:26.630 --> 15:51:26.640 align:start position:0% to troubleshoot you would never use this 15:51:26.640 --> 15:51:29.150 align:start position:0% to troubleshoot you would never use this in<15:51:26.820> a<15:51:26.936> corporate<15:51:27.240> environment<15:51:27.660> now<15:51:27.900> you'd<15:51:28.436> if 15:51:29.150 --> 15:51:29.160 align:start position:0% in a corporate environment now you'd if 15:51:29.160 --> 15:51:31.730 align:start position:0% in a corporate environment now you'd if you<15:51:29.340> went<15:51:29.520> and<15:51:29.756> did<15:51:30.180> some<15:51:30.480> configuration<15:51:31.380> or 15:51:31.730 --> 15:51:31.740 align:start position:0% you went and did some configuration or 15:51:31.740 --> 15:51:33.406 align:start position:0% you went and did some configuration or network<15:51:32.040> installation<15:51:32.640> for<15:51:32.936> a<15:51:33.060> company<15:51:33.180> and 15:51:33.406 --> 15:51:33.416 align:start position:0% network installation for a company and 15:51:33.416 --> 15:51:35.446 align:start position:0% network installation for a company and left<15:51:33.596> town<15:51:33.776> to<15:51:34.020> open<15:51:34.200> then<15:51:34.860> I<15:51:35.040> think<15:51:35.220> you're 15:51:35.446 --> 15:51:35.456 align:start position:0% left town to open then I think you're 15:51:35.456 --> 15:51:36.350 align:start position:0% left town to open then I think you're probably 15:51:36.350 --> 15:51:36.360 align:start position:0% probably 15:51:36.360 --> 15:51:37.906 align:start position:0% probably um be<15:51:36.720> in<15:51:36.840> trouble<15:51:37.020> legally<15:51:37.500> because<15:51:37.740> you've 15:51:37.906 --> 15:51:37.916 align:start position:0% um be in trouble legally because you've 15:51:37.916 --> 15:51:39.830 align:start position:0% um be in trouble legally because you've left<15:51:38.096> a<15:51:38.276> big<15:51:38.400> hole<15:51:39.116> in<15:51:39.180> their<15:51:39.296> Network<15:51:39.540> for 15:51:39.830 --> 15:51:39.840 align:start position:0% left a big hole in their Network for 15:51:39.840 --> 15:51:41.746 align:start position:0% left a big hole in their Network for other<15:51:40.020> people<15:51:40.200> to<15:51:40.436> connect 15:51:41.746 --> 15:51:41.756 align:start position:0% other people to connect 15:51:41.756 --> 15:51:44.810 align:start position:0% other people to connect it<15:51:42.296> requires<15:51:42.840> client<15:51:43.320> software<15:51:43.680> just<15:51:44.276> uh 15:51:44.810 --> 15:51:44.820 align:start position:0% it requires client software just uh 15:51:44.820 --> 15:51:46.550 align:start position:0% it requires client software just uh something<15:51:45.180> like<15:51:45.360> putty<15:51:45.776> used<15:51:45.956> to<15:51:46.080> have<15:51:46.200> hyper 15:51:46.550 --> 15:51:46.560 align:start position:0% something like putty used to have hyper 15:51:46.560 --> 15:51:50.570 align:start position:0% something like putty used to have hyper terminal<15:51:47.116> with<15:51:48.116> a<15:51:48.360> Microsoft<15:51:48.900> they<15:51:49.860> stopped<15:51:50.276> a 15:51:50.570 --> 15:51:50.580 align:start position:0% terminal with a Microsoft they stopped a 15:51:50.580 --> 15:51:53.030 align:start position:0% terminal with a Microsoft they stopped a bundle<15:51:51.000> in<15:51:51.240> it<15:51:51.360> with<15:51:51.480> the<15:51:51.660> software<15:51:51.956> I<15:51:52.256> think 15:51:53.030 --> 15:51:53.040 align:start position:0% bundle in it with the software I think 15:51:53.040 --> 15:51:55.190 align:start position:0% bundle in it with the software I think um about<15:51:53.520> four<15:51:53.756> or<15:51:53.936> five<15:51:54.060> years<15:51:54.296> ago 15:51:55.190 --> 15:51:55.200 align:start position:0% um about four or five years ago 15:51:55.200 --> 15:51:57.710 align:start position:0% um about four or five years ago you<15:51:55.616> could<15:51:55.740> still<15:51:55.916> enable<15:51:56.220> it<15:51:56.580> but<15:51:57.296> you<15:51:57.480> had<15:51:57.596> to 15:51:57.710 --> 15:51:57.720 align:start position:0% you could still enable it but you had to 15:51:57.720 --> 15:52:00.230 align:start position:0% you could still enable it but you had to go<15:51:57.840> into<15:51:58.020> the<15:51:58.436> back<15:51:58.860> end<15:51:59.040> and<15:51:59.700> um<15:51:59.700> I<15:52:00.000> think<15:52:00.180> you 15:52:00.230 --> 15:52:00.240 align:start position:0% go into the back end and um I think you 15:52:00.240 --> 15:52:02.746 align:start position:0% go into the back end and um I think you have<15:52:00.360> to<15:52:00.480> download<15:52:00.660> some<15:52:00.956> extra<15:52:01.140> software<15:52:01.616> but 15:52:02.746 --> 15:52:02.756 align:start position:0% have to download some extra software but 15:52:02.756 --> 15:52:04.310 align:start position:0% have to download some extra software but um it<15:52:03.000> didn't<15:52:03.296> work<15:52:03.480> it<15:52:03.660> doesn't<15:52:03.900> work<15:52:04.140> too 15:52:04.310 --> 15:52:04.320 align:start position:0% um it didn't work it doesn't work too 15:52:04.320 --> 15:52:08.570 align:start position:0% um it didn't work it doesn't work too well<15:52:04.436> anyway<15:52:04.756> uh<15:52:05.756> uses<15:52:06.180> TCP<15:52:06.720> Port<15:52:07.020> 23<15:52:07.740> make<15:52:08.400> a 15:52:08.570 --> 15:52:08.580 align:start position:0% well anyway uh uses TCP Port 23 make a 15:52:08.580 --> 15:52:11.086 align:start position:0% well anyway uh uses TCP Port 23 make a note<15:52:08.640> of<15:52:08.880> that<15:52:09.000> all<15:52:09.900> traffic<15:52:10.200> isn't<15:52:10.616> encrypted 15:52:11.086 --> 15:52:11.096 align:start position:0% note of that all traffic isn't encrypted 15:52:11.096 --> 15:52:12.530 align:start position:0% note of that all traffic isn't encrypted not<15:52:11.340> secure<15:52:11.580> which<15:52:11.880> is<15:52:12.000> why<15:52:12.180> we<15:52:12.416> don't 15:52:12.530 --> 15:52:12.540 align:start position:0% not secure which is why we don't 15:52:12.540 --> 15:52:15.650 align:start position:0% not secure which is why we don't recommend<15:52:12.900> you<15:52:13.080> use<15:52:13.380> it 15:52:15.650 --> 15:52:15.660 align:start position:0% 15:52:15.660 --> 15:52:17.446 align:start position:0% I've<15:52:16.320> already<15:52:16.500> mentioned<15:52:16.860> this<15:52:17.040> bundle 15:52:17.446 --> 15:52:17.456 align:start position:0% I've already mentioned this bundle 15:52:17.456 --> 15:52:19.390 align:start position:0% I've already mentioned this bundle blocked 15:52:19.390 --> 15:52:19.400 align:start position:0% blocked 15:52:19.400 --> 15:52:21.946 align:start position:0% blocked https<15:52:20.400> management 15:52:21.946 --> 15:52:21.956 align:start position:0% https management 15:52:21.956 --> 15:52:25.670 align:start position:0% https management this<15:52:22.500> gives<15:52:22.796> you<15:52:22.916> the<15:52:23.220> graphical<15:52:23.640> uh<15:52:25.140> access 15:52:25.670 --> 15:52:25.680 align:start position:0% this gives you the graphical uh access 15:52:25.680 --> 15:52:28.426 align:start position:0% this gives you the graphical uh access method<15:52:26.220> for<15:52:26.456> a<15:52:26.580> device<15:52:26.756> when<15:52:27.540> you<15:52:27.720> first<15:52:28.020> buy 15:52:28.426 --> 15:52:28.436 align:start position:0% method for a device when you first buy 15:52:28.436 --> 15:52:30.890 align:start position:0% method for a device when you first buy for<15:52:28.796> example<15:52:28.980> a<15:52:29.220> Cisco<15:52:29.580> router<15:52:30.060> and<15:52:30.540> say<15:52:30.720> you 15:52:30.890 --> 15:52:30.900 align:start position:0% for example a Cisco router and say you 15:52:30.900 --> 15:52:33.050 align:start position:0% for example a Cisco router and say you don't<15:52:31.080> know<15:52:31.200> how<15:52:31.380> to<15:52:31.560> configure<15:52:32.040> it<15:52:32.220> you<15:52:33.000> can 15:52:33.050 --> 15:52:33.060 align:start position:0% don't know how to configure it you can 15:52:33.060 --> 15:52:36.530 align:start position:0% don't know how to configure it you can get<15:52:33.240> the<15:52:33.480> router<15:52:33.900> you<15:52:34.560> basically<15:52:34.860> plug<15:52:35.276> in<15:52:35.540> an 15:52:36.530 --> 15:52:36.540 align:start position:0% get the router you basically plug in an 15:52:36.540 --> 15:52:38.446 align:start position:0% get the router you basically plug in an ethernet<15:52:36.900> cable<15:52:37.320> here 15:52:38.446 --> 15:52:38.456 align:start position:0% ethernet cable here 15:52:38.456 --> 15:52:40.670 align:start position:0% ethernet cable here you<15:52:39.000> connect<15:52:39.180> your 15:52:40.670 --> 15:52:40.680 align:start position:0% you connect your 15:52:40.680 --> 15:52:43.550 align:start position:0% you connect your PC<15:52:41.340> or<15:52:41.640> laptop<15:52:42.000> and<15:52:42.660> in<15:52:42.776> the<15:52:42.900> documentation 15:52:43.550 --> 15:52:43.560 align:start position:0% PC or laptop and in the documentation 15:52:43.560 --> 15:52:46.246 align:start position:0% PC or laptop and in the documentation that<15:52:44.220> will<15:52:44.400> come<15:52:44.640> on<15:52:44.936> a<15:52:45.060> CD-ROM<15:52:45.660> or<15:52:45.840> you<15:52:46.020> get<15:52:46.140> a 15:52:46.246 --> 15:52:46.256 align:start position:0% that will come on a CD-ROM or you get a 15:52:46.256 --> 15:52:49.370 align:start position:0% that will come on a CD-ROM or you get a little<15:52:46.380> card<15:52:46.740> it<15:52:47.456> will<15:52:47.640> basically<15:52:48.000> say<15:52:48.380> in 15:52:49.370 --> 15:52:49.380 align:start position:0% little card it will basically say in 15:52:49.380 --> 15:52:52.330 align:start position:0% little card it will basically say in your<15:52:49.616> browser<15:52:50.160> window<15:52:50.340> you<15:52:50.820> put 15:52:52.330 --> 15:52:52.340 align:start position:0% your browser window you put 15:52:52.340 --> 15:52:56.926 align:start position:0% your browser window you put HTTP<15:52:53.340> possibly<15:52:54.296> https<15:52:55.400> and<15:52:56.400> then<15:52:56.580> you<15:52:56.756> will 15:52:56.926 --> 15:52:56.936 align:start position:0% HTTP possibly https and then you will 15:52:56.936 --> 15:52:59.746 align:start position:0% HTTP possibly https and then you will put<15:52:57.240> a<15:52:57.660> number<15:52:58.020> so<15:52:58.796> say<15:52:59.040> for<15:52:59.220> example<15:52:59.400> your 15:52:59.746 --> 15:52:59.756 align:start position:0% put a number so say for example your 15:52:59.756 --> 15:53:02.210 align:start position:0% put a number so say for example your home<15:52:59.936> router<15:53:00.416> will<15:53:00.720> normally<15:53:01.080> be<15:53:01.380> something 15:53:02.210 --> 15:53:02.220 align:start position:0% home router will normally be something 15:53:02.220 --> 15:53:06.050 align:start position:0% home router will normally be something like<15:53:02.520> this<15:53:02.756> 192.168.0.1 15:53:06.050 --> 15:53:06.060 align:start position:0% 15:53:06.060 --> 15:53:08.030 align:start position:0% and<15:53:06.660> then<15:53:06.840> that<15:53:07.020> will<15:53:07.200> result<15:53:07.380> that<15:53:07.860> will 15:53:08.030 --> 15:53:08.040 align:start position:0% and then that will result that will 15:53:08.040 --> 15:53:10.370 align:start position:0% and then that will result that will resolve<15:53:08.700> it<15:53:09.296> doesn't<15:53:09.480> need<15:53:09.660> to<15:53:09.776> use<15:53:09.840> DNS 15:53:10.370 --> 15:53:10.380 align:start position:0% resolve it doesn't need to use DNS 15:53:10.380 --> 15:53:12.230 align:start position:0% resolve it doesn't need to use DNS because<15:53:10.616> it's<15:53:10.860> uh<15:53:11.096> the<15:53:11.276> using<15:53:11.640> an<15:53:11.756> IP<15:53:12.060> address 15:53:12.230 --> 15:53:12.240 align:start position:0% because it's uh the using an IP address 15:53:12.240 --> 15:53:14.926 align:start position:0% because it's uh the using an IP address it<15:53:13.080> will<15:53:13.200> resolve<15:53:13.680> them<15:53:13.860> to<15:53:14.456> this<15:53:14.700> management 15:53:14.926 --> 15:53:14.936 align:start position:0% it will resolve them to this management 15:53:14.936 --> 15:53:18.766 align:start position:0% it will resolve them to this management window<15:53:15.740> and<15:53:16.740> on<15:53:16.980> my<15:53:17.220> route<15:53:17.700> up<15:53:18.060> on<15:53:18.296> my<15:53:18.596> home 15:53:18.766 --> 15:53:18.776 align:start position:0% window and on my route up on my home 15:53:18.776 --> 15:53:21.050 align:start position:0% window and on my route up on my home router<15:53:19.256> you've<15:53:19.860> got<15:53:20.040> a<15:53:20.220> whole<15:53:20.340> bunch<15:53:20.520> of<15:53:20.640> menus 15:53:21.050 --> 15:53:21.060 align:start position:0% router you've got a whole bunch of menus 15:53:21.060 --> 15:53:24.586 align:start position:0% router you've got a whole bunch of menus here<15:53:21.480> you<15:53:22.200> can<15:53:22.380> configure<15:53:22.980> the<15:53:23.640> firewall<15:53:24.116> you 15:53:24.586 --> 15:53:24.596 align:start position:0% here you can configure the firewall you 15:53:24.596 --> 15:53:26.210 align:start position:0% here you can configure the firewall you can<15:53:24.720> reboot 15:53:26.210 --> 15:53:26.220 align:start position:0% can reboot 15:53:26.220 --> 15:53:29.570 align:start position:0% can reboot you<15:53:26.820> can<15:53:26.936> check<15:53:27.180> your<15:53:27.540> DNS<15:53:28.020> settings<15:53:28.456> you<15:53:29.456> can 15:53:29.570 --> 15:53:29.580 align:start position:0% you can check your DNS settings you can 15:53:29.580 --> 15:53:31.850 align:start position:0% you can check your DNS settings you can permit<15:53:30.116> or<15:53:30.360> deny<15:53:30.720> different<15:53:31.020> devices<15:53:31.436> if<15:53:31.740> you 15:53:31.850 --> 15:53:31.860 align:start position:0% permit or deny different devices if you 15:53:31.860 --> 15:53:34.906 align:start position:0% permit or deny different devices if you want<15:53:32.040> your<15:53:32.276> kids<15:53:32.520> to<15:53:33.480> access<15:53:33.660> the<15:53:34.200> internet<15:53:34.500> or 15:53:34.906 --> 15:53:34.916 align:start position:0% want your kids to access the internet or 15:53:34.916 --> 15:53:38.690 align:start position:0% want your kids to access the internet or you<15:53:35.040> want<15:53:35.160> to<15:53:35.276> block<15:53:35.456> them<15:53:35.900> and<15:53:36.900> you<15:53:37.616> can<15:53:37.740> you 15:53:38.690 --> 15:53:38.700 align:start position:0% you want to block them and you can you 15:53:38.700 --> 15:53:40.906 align:start position:0% you want to block them and you can you can<15:53:38.820> configure<15:53:39.360> that 15:53:40.906 --> 15:53:40.916 align:start position:0% can configure that 15:53:40.916 --> 15:53:42.170 align:start position:0% can configure that um 15:53:42.170 --> 15:53:42.180 align:start position:0% um 15:53:42.180 --> 15:53:44.690 align:start position:0% um firmware<15:53:43.320> etc<15:53:43.616> etc<15:53:43.740> anyway<15:53:44.040> you<15:53:44.276> get<15:53:44.340> you<15:53:44.520> get 15:53:44.690 --> 15:53:44.700 align:start position:0% firmware etc etc anyway you get you get 15:53:44.700 --> 15:53:47.690 align:start position:0% firmware etc etc anyway you get you get the<15:53:44.820> idea<15:53:45.240> so<15:53:46.020> this<15:53:46.320> is<15:53:46.436> your<15:53:46.796> way<15:53:47.160> of<15:53:47.340> managing 15:53:47.690 --> 15:53:47.700 align:start position:0% the idea so this is your way of managing 15:53:47.700 --> 15:53:50.990 align:start position:0% the idea so this is your way of managing your<15:53:48.000> device<15:53:48.180> it's<15:53:49.020> a<15:53:49.200> security<15:53:49.436> issue<15:53:50.160> if 15:53:50.990 --> 15:53:51.000 align:start position:0% your device it's a security issue if 15:53:51.000 --> 15:53:53.086 align:start position:0% your device it's a security issue if enabled<15:53:51.480> by<15:53:51.660> default 15:53:53.086 --> 15:53:53.096 align:start position:0% enabled by default 15:53:53.096 --> 15:53:55.190 align:start position:0% enabled by default I'm<15:53:53.580> trying<15:53:53.756> to<15:53:53.936> remember<15:53:54.060> now<15:53:54.416> I<15:53:54.776> think<15:53:54.956> uh 15:53:55.190 --> 15:53:55.200 align:start position:0% I'm trying to remember now I think uh 15:53:55.200 --> 15:53:58.010 align:start position:0% I'm trying to remember now I think uh Cisco<15:53:55.616> devices<15:53:55.980> is<15:53:56.276> disabled<15:53:56.820> by<15:53:57.000> default<15:53:57.360> but 15:53:58.010 --> 15:53:58.020 align:start position:0% Cisco devices is disabled by default but 15:53:58.020 --> 15:53:59.330 align:start position:0% Cisco devices is disabled by default but sometimes<15:53:58.436> you<15:53:58.740> can<15:53:58.860> have<15:53:59.040> different 15:53:59.330 --> 15:53:59.340 align:start position:0% sometimes you can have different 15:53:59.340 --> 15:54:01.086 align:start position:0% sometimes you can have different versions<15:53:59.880> of<15:54:00.116> iOS 15:54:01.086 --> 15:54:01.096 align:start position:0% versions of iOS 15:54:01.096 --> 15:54:03.890 align:start position:0% versions of iOS where<15:54:02.096> all<15:54:02.880> enabled<15:54:03.360> and<15:54:03.596> then<15:54:03.720> there's 15:54:03.890 --> 15:54:03.900 align:start position:0% where all enabled and then there's 15:54:03.900 --> 15:54:06.370 align:start position:0% where all enabled and then there's something<15:54:04.160> there's<15:54:05.160> some<15:54:05.456> change<15:54:05.640> happens 15:54:06.370 --> 15:54:06.380 align:start position:0% something there's some change happens 15:54:06.380 --> 15:54:09.946 align:start position:0% something there's some change happens and<15:54:07.380> the<15:54:08.220> command<15:54:08.520> changes<15:54:09.060> or<15:54:09.480> the<15:54:09.720> default 15:54:09.946 --> 15:54:09.956 align:start position:0% and the command changes or the default 15:54:09.956 --> 15:54:12.170 align:start position:0% and the command changes or the default setting<15:54:10.380> changes<15:54:10.740> this<15:54:11.276> is<15:54:11.400> for<15:54:11.640> routing 15:54:12.170 --> 15:54:12.180 align:start position:0% setting changes this is for routing 15:54:12.180 --> 15:54:15.710 align:start position:0% setting changes this is for routing commands<15:54:12.840> security<15:54:13.500> commands<15:54:14.360> how<15:54:15.360> to<15:54:15.540> switch 15:54:15.710 --> 15:54:15.720 align:start position:0% commands security commands how to switch 15:54:15.720 --> 15:54:18.050 align:start position:0% commands security commands how to switch traffic<15:54:16.140> packet<15:54:16.796> switching<15:54:17.220> and<15:54:17.520> track<15:54:17.756> and 15:54:18.050 --> 15:54:18.060 align:start position:0% traffic packet switching and track and 15:54:18.060 --> 15:54:19.550 align:start position:0% traffic packet switching and track and frame<15:54:18.360> switching 15:54:19.550 --> 15:54:19.560 align:start position:0% frame switching 15:54:19.560 --> 15:54:22.310 align:start position:0% frame switching so<15:54:20.640> um<15:54:20.640> check<15:54:21.000> what<15:54:21.296> device<15:54:21.540> you're<15:54:21.776> on<15:54:22.020> and<15:54:22.140> if 15:54:22.310 --> 15:54:22.320 align:start position:0% so um check what device you're on and if 15:54:22.320 --> 15:54:23.990 align:start position:0% so um check what device you're on and if it's<15:54:22.436> enabled<15:54:22.980> or<15:54:23.096> disabled<15:54:23.520> by<15:54:23.640> default 15:54:23.990 --> 15:54:24.000 align:start position:0% it's enabled or disabled by default 15:54:24.000 --> 15:54:27.286 align:start position:0% it's enabled or disabled by default generally<15:54:24.660> you'll<15:54:24.956> want<15:54:25.140> it<15:54:25.320> uh<15:54:25.560> disabled 15:54:27.286 --> 15:54:27.296 align:start position:0% generally you'll want it uh disabled 15:54:27.296 --> 15:54:28.606 align:start position:0% generally you'll want it uh disabled otherwise<15:54:27.900> you've<15:54:28.080> got<15:54:28.200> to<15:54:28.320> configure 15:54:28.606 --> 15:54:28.616 align:start position:0% otherwise you've got to configure 15:54:28.616 --> 15:54:31.426 align:start position:0% otherwise you've got to configure Advanced<15:54:29.096> usernames<15:54:29.700> and<15:54:29.820> passwords<15:54:30.416> so<15:54:31.200> put 15:54:31.426 --> 15:54:31.436 align:start position:0% Advanced usernames and passwords so put 15:54:31.436 --> 15:54:33.946 align:start position:0% Advanced usernames and passwords so put the<15:54:31.560> IP<15:54:31.796> address<15:54:31.980> into<15:54:32.340> the<15:54:32.700> browser<15:54:33.180> bar 15:54:33.946 --> 15:54:33.956 align:start position:0% the IP address into the browser bar 15:54:33.956 --> 15:54:37.246 align:start position:0% the IP address into the browser bar remote<15:54:35.116> file<15:54:36.116> access 15:54:37.246 --> 15:54:37.256 align:start position:0% remote file access 15:54:37.256 --> 15:54:39.946 align:start position:0% remote file access FTP<15:54:38.040> is<15:54:38.220> used<15:54:38.400> to<15:54:38.756> upload<15:54:39.116> and<15:54:39.360> download<15:54:39.540> large 15:54:39.946 --> 15:54:39.956 align:start position:0% FTP is used to upload and download large 15:54:39.956 --> 15:54:42.170 align:start position:0% FTP is used to upload and download large files<15:54:40.500> in<15:54:40.980> securely 15:54:42.170 --> 15:54:42.180 align:start position:0% files in securely 15:54:42.180 --> 15:54:46.446 align:start position:0% files in securely so<15:54:42.540> this<15:54:42.840> represents<15:54:43.680> a<15:54:43.860> problem 15:54:46.446 --> 15:54:46.456 align:start position:0% 15:54:46.456 --> 15:54:49.490 align:start position:0% SFTP<15:54:47.456> this<15:54:47.880> is<15:54:48.000> a<15:54:48.180> protocol<15:54:48.540> in<15:54:48.956> its<15:54:49.200> own<15:54:49.256> right 15:54:49.490 --> 15:54:49.500 align:start position:0% SFTP this is a protocol in its own right 15:54:49.500 --> 15:54:52.070 align:start position:0% SFTP this is a protocol in its own right so<15:54:49.796> it's<15:54:49.980> not<15:54:50.160> as<15:54:50.340> if<15:54:50.456> you've<15:54:50.700> got<15:54:50.820> FTP<15:54:51.416> and 15:54:52.070 --> 15:54:52.080 align:start position:0% so it's not as if you've got FTP and 15:54:52.080 --> 15:54:54.530 align:start position:0% so it's not as if you've got FTP and added<15:54:52.500> something<15:54:52.740> to<15:54:53.096> it<15:54:53.276> this<15:54:53.936> is<15:54:54.116> its<15:54:54.480> own 15:54:54.530 --> 15:54:54.540 align:start position:0% added something to it this is its own 15:54:54.540 --> 15:54:55.730 align:start position:0% added something to it this is its own protocol 15:54:55.730 --> 15:54:55.740 align:start position:0% protocol 15:54:55.740 --> 15:54:58.670 align:start position:0% protocol so<15:54:56.340> just<15:54:56.580> be<15:54:56.756> careful<15:54:57.060> it's<15:54:57.720> encrypts<15:54:58.380> a 15:54:58.670 --> 15:54:58.680 align:start position:0% so just be careful it's encrypts a 15:54:58.680 --> 15:55:01.190 align:start position:0% so just be careful it's encrypts a secures<15:54:59.640> an<15:54:59.700> eclipse<15:55:00.000> traffic<15:55:00.180> it<15:55:00.416> uses<15:55:00.720> SSH 15:55:01.190 --> 15:55:01.200 align:start position:0% secures an eclipse traffic it uses SSH 15:55:01.200 --> 15:55:03.766 align:start position:0% secures an eclipse traffic it uses SSH which<15:55:01.680> is<15:55:01.796> port<15:55:01.980> 22. 15:55:03.766 --> 15:55:03.776 align:start position:0% which is port 22. 15:55:03.776 --> 15:55:07.426 align:start position:0% which is port 22. so<15:55:04.740> um<15:55:04.740> don't<15:55:04.980> think<15:55:05.220> that<15:55:05.400> it's<15:55:05.640> an<15:55:05.880> FTP<15:55:06.480> with 15:55:07.426 --> 15:55:07.436 align:start position:0% so um don't think that it's an FTP with 15:55:07.436 --> 15:55:10.190 align:start position:0% so um don't think that it's an FTP with some<15:55:07.616> little<15:55:07.860> extra<15:55:08.160> bit<15:55:08.820> on<15:55:09.060> here 15:55:10.190 --> 15:55:10.200 align:start position:0% some little extra bit on here 15:55:10.200 --> 15:55:13.850 align:start position:0% some little extra bit on here security<15:55:10.560> bit<15:55:11.060> security<15:55:12.060> issue<15:55:12.776> if<15:55:13.320> enabled 15:55:13.850 --> 15:55:13.860 align:start position:0% security bit security issue if enabled 15:55:13.860 --> 15:55:16.070 align:start position:0% security bit security issue if enabled by<15:55:13.980> default<15:55:14.340> this<15:55:14.700> is<15:55:15.116> um<15:55:15.116> again<15:55:15.596> I've<15:55:15.900> done 15:55:16.070 --> 15:55:16.080 align:start position:0% by default this is um again I've done 15:55:16.080 --> 15:55:18.050 align:start position:0% by default this is um again I've done that<15:55:16.256> again<15:55:16.380> sorry<15:55:16.740> I've<15:55:17.276> left<15:55:17.580> it<15:55:17.756> from<15:55:17.936> the 15:55:18.050 --> 15:55:18.060 align:start position:0% that again sorry I've left it from the 15:55:18.060 --> 15:55:20.266 align:start position:0% that again sorry I've left it from the last<15:55:18.240> slide 15:55:20.266 --> 15:55:20.276 align:start position:0% last slide 15:55:20.276 --> 15:55:22.746 align:start position:0% last slide your<15:55:20.880> other<15:55:21.116> file<15:55:21.660> transfer<15:55:22.140> method<15:55:22.500> is 15:55:22.746 --> 15:55:22.756 align:start position:0% your other file transfer method is 15:55:22.756 --> 15:55:25.310 align:start position:0% your other file transfer method is Trivial<15:55:23.756> file<15:55:24.060> transfer<15:55:24.540> protocol<15:55:24.900> which<15:55:25.200> I 15:55:25.310 --> 15:55:25.320 align:start position:0% Trivial file transfer protocol which I 15:55:25.320 --> 15:55:26.870 align:start position:0% Trivial file transfer protocol which I think<15:55:25.436> we've<15:55:25.616> mentioned<15:55:25.916> earlier<15:55:26.220> if<15:55:26.700> you've 15:55:26.870 --> 15:55:26.880 align:start position:0% think we've mentioned earlier if you've 15:55:26.880 --> 15:55:30.286 align:start position:0% think we've mentioned earlier if you've got<15:55:27.000> a<15:55:27.180> small<15:55:27.360> file<15:55:27.776> that<15:55:28.680> you<15:55:28.860> want<15:55:28.980> to<15:55:29.296> send 15:55:30.286 --> 15:55:30.296 align:start position:0% got a small file that you want to send 15:55:30.296 --> 15:55:33.050 align:start position:0% got a small file that you want to send over<15:55:30.480> your<15:55:30.776> network<15:55:31.096> again<15:55:32.096> please<15:55:32.520> don't<15:55:32.756> use 15:55:33.050 --> 15:55:33.060 align:start position:0% over your network again please don't use 15:55:33.060 --> 15:55:35.266 align:start position:0% over your network again please don't use this<15:55:33.360> this<15:55:33.540> is<15:55:33.720> just<15:55:33.956> what<15:55:34.256> it's<15:55:34.436> used<15:55:34.616> for<15:55:34.796> if 15:55:35.266 --> 15:55:35.276 align:start position:0% this this is just what it's used for if 15:55:35.276 --> 15:55:37.130 align:start position:0% this this is just what it's used for if you've<15:55:35.520> got<15:55:35.700> a<15:55:35.820> router<15:55:36.240> and<15:55:36.660> you<15:55:36.776> want<15:55:36.900> to<15:55:37.020> back 15:55:37.130 --> 15:55:37.140 align:start position:0% you've got a router and you want to back 15:55:37.140 --> 15:55:39.470 align:start position:0% you've got a router and you want to back up<15:55:37.256> the<15:55:37.380> configuration<15:55:37.980> you've<15:55:38.756> got<15:55:38.880> a<15:55:39.116> tiny 15:55:39.470 --> 15:55:39.480 align:start position:0% up the configuration you've got a tiny 15:55:39.480 --> 15:55:41.870 align:start position:0% up the configuration you've got a tiny little<15:55:39.660> file<15:55:40.020> like<15:55:40.980> about 15:55:41.870 --> 15:55:41.880 align:start position:0% little file like about 15:55:41.880 --> 15:55:45.766 align:start position:0% little file like about a<15:55:42.660> by<15:55:43.020> uh<15:55:43.500> eight<15:55:43.740> bytes<15:55:44.220> whatever<15:55:44.540> or<15:55:45.540> eight 15:55:45.766 --> 15:55:45.776 align:start position:0% a by uh eight bytes whatever or eight 15:55:45.776 --> 15:55:47.810 align:start position:0% a by uh eight bytes whatever or eight kilobytes<15:55:46.320> probably 15:55:47.810 --> 15:55:47.820 align:start position:0% kilobytes probably 15:55:47.820 --> 15:55:50.210 align:start position:0% kilobytes probably um<15:55:47.880> you'll<15:55:48.296> you'll<15:55:48.596> back<15:55:48.720> it<15:55:48.840> up<15:55:49.020> here<15:55:49.256> using 15:55:50.210 --> 15:55:50.220 align:start position:0% um you'll you'll back it up here using 15:55:50.220 --> 15:55:52.370 align:start position:0% um you'll you'll back it up here using tftp 15:55:52.370 --> 15:55:52.380 align:start position:0% tftp 15:55:52.380 --> 15:55:55.130 align:start position:0% tftp but<15:55:52.796> again<15:55:53.040> this<15:55:53.400> file<15:55:53.640> really<15:55:54.060> is<15:55:54.540> sensitive 15:55:55.130 --> 15:55:55.140 align:start position:0% but again this file really is sensitive 15:55:55.140 --> 15:55:57.106 align:start position:0% but again this file really is sensitive because<15:55:55.320> it's<15:55:55.560> got<15:55:55.740> IP<15:55:56.040> addresses<15:55:56.520> passwords 15:55:57.106 --> 15:55:57.116 align:start position:0% because it's got IP addresses passwords 15:55:57.116 --> 15:56:00.106 align:start position:0% because it's got IP addresses passwords and<15:55:57.240> heaven<15:55:57.480> knows<15:55:57.840> what<15:55:58.020> so<15:55:58.980> really<15:55:59.400> using 15:56:00.106 --> 15:56:00.116 align:start position:0% and heaven knows what so really using 15:56:00.116 --> 15:56:03.350 align:start position:0% and heaven knows what so really using tftp<15:56:00.900> it<15:56:01.616> shouldn't<15:56:02.040> be<15:56:02.096> done<15:56:02.276> anymore<15:56:02.580> if 15:56:03.350 --> 15:56:03.360 align:start position:0% tftp it shouldn't be done anymore if 15:56:03.360 --> 15:56:04.850 align:start position:0% tftp it shouldn't be done anymore if you're<15:56:03.480> at<15:56:03.720> home<15:56:03.900> you've<15:56:04.500> got<15:56:04.560> your<15:56:04.740> little 15:56:04.850 --> 15:56:04.860 align:start position:0% you're at home you've got your little 15:56:04.860 --> 15:56:06.350 align:start position:0% you're at home you've got your little home<15:56:05.096> network<15:56:05.340> and<15:56:05.640> you<15:56:05.820> want<15:56:05.880> to<15:56:06.000> have<15:56:06.116> a<15:56:06.240> play 15:56:06.350 --> 15:56:06.360 align:start position:0% home network and you want to have a play 15:56:06.360 --> 15:56:09.350 align:start position:0% home network and you want to have a play with<15:56:06.596> your<15:56:06.776> software<15:56:07.140> fine<15:56:07.916> and<15:56:08.820> if<15:56:09.060> you're<15:56:09.180> in 15:56:09.350 --> 15:56:09.360 align:start position:0% with your software fine and if you're in 15:56:09.360 --> 15:56:12.350 align:start position:0% with your software fine and if you're in a<15:56:09.480> corporate<15:56:09.840> environment<15:56:10.456> no<15:56:11.456> I<15:56:11.880> I<15:56:12.116> think 15:56:12.350 --> 15:56:12.360 align:start position:0% a corporate environment no I I think 15:56:12.360 --> 15:56:14.390 align:start position:0% a corporate environment no I I think it's<15:56:12.480> a<15:56:12.596> really<15:56:12.720> bad<15:56:12.900> idea 15:56:14.390 --> 15:56:14.400 align:start position:0% it's a really bad idea 15:56:14.400 --> 15:56:17.570 align:start position:0% it's a really bad idea out<15:56:15.060> of<15:56:15.180> band<15:56:15.416> access<15:56:15.720> outer<15:56:16.380> band<15:56:16.500> basically 15:56:17.570 --> 15:56:17.580 align:start position:0% out of band access outer band basically 15:56:17.580 --> 15:56:18.470 align:start position:0% out of band access outer band basically um 15:56:18.470 --> 15:56:18.480 align:start position:0% um 15:56:18.480 --> 15:56:20.990 align:start position:0% um it's<15:56:19.080> not<15:56:19.200> within<15:56:19.560> your<15:56:19.860> normal<15:56:20.040> ethernet 15:56:20.990 --> 15:56:21.000 align:start position:0% it's not within your normal ethernet 15:56:21.000 --> 15:56:22.130 align:start position:0% it's not within your normal ethernet connection 15:56:22.130 --> 15:56:22.140 align:start position:0% connection 15:56:22.140 --> 15:56:24.710 align:start position:0% connection so<15:56:22.560> say<15:56:22.796> you've<15:56:22.980> got<15:56:23.160> a<15:56:23.340> router<15:56:23.756> you've<15:56:24.296> got<15:56:24.480> a 15:56:24.710 --> 15:56:24.720 align:start position:0% so say you've got a router you've got a 15:56:24.720 --> 15:56:26.990 align:start position:0% so say you've got a router you've got a fast<15:56:24.900> ethernet<15:56:25.256> port<15:56:25.680> here<15:56:26.040> and<15:56:26.640> then<15:56:26.756> you've 15:56:26.990 --> 15:56:27.000 align:start position:0% fast ethernet port here and then you've 15:56:27.000 --> 15:56:30.530 align:start position:0% fast ethernet port here and then you've got<15:56:27.116> your<15:56:27.660> again<15:56:28.436> your<15:56:29.276> PC<15:56:29.880> or<15:56:30.180> whatever<15:56:30.296> you 15:56:30.530 --> 15:56:30.540 align:start position:0% got your again your PC or whatever you 15:56:30.540 --> 15:56:31.850 align:start position:0% got your again your PC or whatever you use<15:56:30.720> to<15:56:30.900> connect 15:56:31.850 --> 15:56:31.860 align:start position:0% use to connect 15:56:31.860 --> 15:56:36.406 align:start position:0% use to connect so<15:56:32.160> this<15:56:32.340> will<15:56:32.520> be<15:56:32.700> your<15:56:33.000> in-band 15:56:36.406 --> 15:56:36.416 align:start position:0% 15:56:36.416 --> 15:56:39.766 align:start position:0% out<15:56:37.080> of<15:56:37.256> band<15:56:37.500> would<15:56:38.040> be<15:56:38.220> something<15:56:38.700> like<15:56:39.240> a 15:56:39.766 --> 15:56:39.776 align:start position:0% out of band would be something like a 15:56:39.776 --> 15:56:42.766 align:start position:0% out of band would be something like a modem<15:56:40.320> connection<15:56:40.860> so<15:56:41.640> you've<15:56:42.480> got<15:56:42.596> your 15:56:42.766 --> 15:56:42.776 align:start position:0% modem connection so you've got your 15:56:42.776 --> 15:56:44.150 align:start position:0% modem connection so you've got your router 15:56:44.150 --> 15:56:44.160 align:start position:0% router 15:56:44.160 --> 15:56:47.086 align:start position:0% router and<15:56:45.060> your 15:56:47.086 --> 15:56:47.096 align:start position:0% and your 15:56:47.096 --> 15:56:48.470 align:start position:0% and your your<15:56:47.160> you've<15:56:47.820> got<15:56:47.936> your<15:56:48.296> telephone 15:56:48.470 --> 15:56:48.480 align:start position:0% your you've got your telephone 15:56:48.480 --> 15:56:53.746 align:start position:0% your you've got your telephone connection<15:56:49.020> here<15:56:49.680> and<15:56:50.400> then<15:56:50.580> a<15:56:50.820> modem 15:56:53.746 --> 15:56:53.756 align:start position:0% 15:56:53.756 --> 15:56:56.570 align:start position:0% which<15:56:54.296> is<15:56:54.416> connected<15:56:54.840> to<15:56:55.200> your<15:56:55.500> computer<15:56:55.916> so 15:56:56.570 --> 15:56:56.580 align:start position:0% which is connected to your computer so 15:56:56.580 --> 15:56:58.370 align:start position:0% which is connected to your computer so out<15:56:56.880> of<15:56:57.116> band 15:56:58.370 --> 15:56:58.380 align:start position:0% out of band 15:56:58.380 --> 15:57:01.010 align:start position:0% out of band used<15:56:58.860> for<15:56:59.096> emergency<15:56:59.520> access<15:57:00.000> normally<15:57:00.660> if 15:57:01.010 --> 15:57:01.020 align:start position:0% used for emergency access normally if 15:57:01.020 --> 15:57:03.230 align:start position:0% used for emergency access normally if you're<15:57:01.200> connecting<15:57:01.616> out<15:57:01.860> a<15:57:02.096> band<15:57:02.276> something 15:57:03.230 --> 15:57:03.240 align:start position:0% you're connecting out a band something 15:57:03.240 --> 15:57:05.690 align:start position:0% you're connecting out a band something has<15:57:03.540> gone<15:57:03.776> wrong 15:57:05.690 --> 15:57:05.700 align:start position:0% has gone wrong 15:57:05.700 --> 15:57:07.850 align:start position:0% has gone wrong now<15:57:06.116> it<15:57:06.240> looks<15:57:06.540> like<15:57:06.596> this<15:57:06.840> is<15:57:06.956> a<15:57:07.200> modem<15:57:07.560> here 15:57:07.850 --> 15:57:07.860 align:start position:0% now it looks like this is a modem here 15:57:07.860 --> 15:57:10.730 align:start position:0% now it looks like this is a modem here and<15:57:08.700> you<15:57:08.936> can<15:57:09.000> connect<15:57:09.240> uh<15:57:09.956> over<15:57:10.436> the<15:57:10.616> Internet 15:57:10.730 --> 15:57:10.740 align:start position:0% and you can connect uh over the Internet 15:57:10.740 --> 15:57:12.946 align:start position:0% and you can connect uh over the Internet so<15:57:11.040> you<15:57:11.220> could<15:57:11.340> connect<15:57:11.520> to<15:57:11.820> the<15:57:12.000> modem<15:57:12.360> and 15:57:12.946 --> 15:57:12.956 align:start position:0% so you could connect to the modem and 15:57:12.956 --> 15:57:15.170 align:start position:0% so you could connect to the modem and then<15:57:13.080> there's<15:57:13.320> a<15:57:13.616> a<15:57:14.040> modem<15:57:14.640> Port<15:57:14.820> here 15:57:15.170 --> 15:57:15.180 align:start position:0% then there's a a modem Port here 15:57:15.180 --> 15:57:17.746 align:start position:0% then there's a a modem Port here normally<15:57:15.720> on<15:57:15.900> Cisco<15:57:16.320> devices<15:57:16.740> it's<15:57:17.160> got<15:57:17.340> aux 15:57:17.746 --> 15:57:17.756 align:start position:0% normally on Cisco devices it's got aux 15:57:17.756 --> 15:57:19.550 align:start position:0% normally on Cisco devices it's got aux written<15:57:18.240> on<15:57:18.416> it<15:57:18.540> again<15:57:19.080> check<15:57:19.380> your 15:57:19.550 --> 15:57:19.560 align:start position:0% written on it again check your 15:57:19.560 --> 15:57:21.586 align:start position:0% written on it again check your documentation<15:57:20.096> because<15:57:20.340> things<15:57:20.756> change<15:57:21.296> over 15:57:21.586 --> 15:57:21.596 align:start position:0% documentation because things change over 15:57:21.596 --> 15:57:22.606 align:start position:0% documentation because things change over time 15:57:22.606 --> 15:57:22.616 align:start position:0% time 15:57:22.616 --> 15:57:24.890 align:start position:0% time so<15:57:23.040> attach<15:57:23.276> your<15:57:23.456> mode<15:57:23.640> and<15:57:23.820> support<15:57:24.000> what<15:57:24.776> you 15:57:24.890 --> 15:57:24.900 align:start position:0% so attach your mode and support what you 15:57:24.900 --> 15:57:26.746 align:start position:0% so attach your mode and support what you would<15:57:25.020> normally<15:57:25.320> do<15:57:25.616> is<15:57:26.040> this<15:57:26.340> wouldn't<15:57:26.520> be 15:57:26.746 --> 15:57:26.756 align:start position:0% would normally do is this wouldn't be 15:57:26.756 --> 15:57:28.370 align:start position:0% would normally do is this wouldn't be connected<15:57:27.180> say<15:57:27.480> you're<15:57:27.660> in<15:57:27.776> a<15:57:28.020> corporate 15:57:28.370 --> 15:57:28.380 align:start position:0% connected say you're in a corporate 15:57:28.380 --> 15:57:30.650 align:start position:0% connected say you're in a corporate environment<15:57:29.220> so<15:57:29.456> this<15:57:29.700> is<15:57:29.820> in<15:57:30.060> your<15:57:30.296> corporate 15:57:30.650 --> 15:57:30.660 align:start position:0% environment so this is in your corporate 15:57:30.660 --> 15:57:31.906 align:start position:0% environment so this is in your corporate Network 15:57:31.906 --> 15:57:31.916 align:start position:0% Network 15:57:31.916 --> 15:57:36.830 align:start position:0% Network and<15:57:32.640> you've<15:57:33.000> got<15:57:33.296> a<15:57:34.320> um 15:57:36.830 --> 15:57:36.840 align:start position:0% 15:57:36.840 --> 15:57:39.710 align:start position:0% you've<15:57:37.380> got<15:57:37.560> your<15:57:37.860> remote<15:57:38.160> hands<15:57:38.880> so<15:57:39.360> this<15:57:39.540> is 15:57:39.710 --> 15:57:39.720 align:start position:0% you've got your remote hands so this is 15:57:39.720 --> 15:57:42.106 align:start position:0% you've got your remote hands so this is like<15:57:39.956> your<15:57:40.436> help<15:57:40.616> desk<15:57:40.916> team<15:57:41.220> they're<15:57:41.936> not 15:57:42.106 --> 15:57:42.116 align:start position:0% like your help desk team they're not 15:57:42.116 --> 15:57:44.030 align:start position:0% like your help desk team they're not they're<15:57:42.480> not<15:57:42.720> that<15:57:43.020> technical<15:57:43.380> say<15:57:43.796> they're 15:57:44.030 --> 15:57:44.040 align:start position:0% they're not that technical say they're 15:57:44.040 --> 15:57:46.490 align:start position:0% they're not that technical say they're level<15:57:44.220> one<15:57:44.580> but<15:57:45.360> you've<15:57:45.596> got<15:57:45.720> people<15:57:46.020> who<15:57:46.380> if 15:57:46.490 --> 15:57:46.500 align:start position:0% level one but you've got people who if 15:57:46.500 --> 15:57:49.070 align:start position:0% level one but you've got people who if you<15:57:46.680> send<15:57:46.796> them<15:57:46.916> in<15:57:47.160> the<15:57:47.276> instructions<15:57:47.936> to<15:57:48.840> go 15:57:49.070 --> 15:57:49.080 align:start position:0% you send them in the instructions to go 15:57:49.080 --> 15:57:50.990 align:start position:0% you send them in the instructions to go to<15:57:49.436> rack 15:57:50.990 --> 15:57:51.000 align:start position:0% to rack 15:57:51.000 --> 15:57:53.510 align:start position:0% to rack one<15:57:51.980> and 15:57:53.510 --> 15:57:53.520 align:start position:0% one and 15:57:53.520 --> 15:57:55.070 align:start position:0% one and um<15:57:53.580> find 15:57:55.070 --> 15:57:55.080 align:start position:0% um find 15:57:55.080 --> 15:57:58.310 align:start position:0% um find say<15:57:55.740> Row<15:57:56.220> three<15:57:56.400> or<15:57:56.580> whatever<15:57:56.776> and<15:57:57.776> ask<15:57:58.140> them 15:57:58.310 --> 15:57:58.320 align:start position:0% say Row three or whatever and ask them 15:57:58.320 --> 15:57:59.690 align:start position:0% say Row three or whatever and ask them to<15:57:58.500> plug<15:57:58.616> in<15:57:58.796> the<15:57:58.916> cable<15:57:59.160> and<15:57:59.340> you'll<15:57:59.456> have<15:57:59.580> the 15:57:59.690 --> 15:57:59.700 align:start position:0% to plug in the cable and you'll have the 15:57:59.700 --> 15:58:01.190 align:start position:0% to plug in the cable and you'll have the cable<15:57:59.880> sitting<15:58:00.240> there<15:58:00.360> but<15:58:00.540> not<15:58:00.660> plugged<15:58:01.080> in 15:58:01.190 --> 15:58:01.200 align:start position:0% cable sitting there but not plugged in 15:58:01.200 --> 15:58:04.070 align:start position:0% cable sitting there but not plugged in you'll<15:58:01.916> do<15:58:02.040> the<15:58:02.276> fix<15:58:02.456> bring<15:58:03.416> the<15:58:03.596> router<15:58:03.900> back 15:58:04.070 --> 15:58:04.080 align:start position:0% you'll do the fix bring the router back 15:58:04.080 --> 15:58:05.630 align:start position:0% you'll do the fix bring the router back up<15:58:04.200> so<15:58:04.436> all<15:58:04.680> the<15:58:04.796> other<15:58:04.916> ports<15:58:05.340> are<15:58:05.456> working 15:58:05.630 --> 15:58:05.640 align:start position:0% up so all the other ports are working 15:58:05.640 --> 15:58:08.286 align:start position:0% up so all the other ports are working and<15:58:06.296> then<15:58:06.540> they<15:58:06.900> will<15:58:07.020> disconnect<15:58:07.320> that<15:58:08.040> again 15:58:08.286 --> 15:58:08.296 align:start position:0% and then they will disconnect that again 15:58:08.296 --> 15:58:10.606 align:start position:0% and then they will disconnect that again and<15:58:09.296> you'll<15:58:09.720> normally<15:58:09.900> have<15:58:10.080> obviously<15:58:10.500> a 15:58:10.606 --> 15:58:10.616 align:start position:0% and you'll normally have obviously a 15:58:10.616 --> 15:58:12.586 align:start position:0% and you'll normally have obviously a ticketing<15:58:11.096> system<15:58:11.340> of<15:58:11.640> some<15:58:11.880> sort<15:58:12.060> where 15:58:12.586 --> 15:58:12.596 align:start position:0% ticketing system of some sort where 15:58:12.596 --> 15:58:15.230 align:start position:0% ticketing system of some sort where you'll<15:58:12.900> say<15:58:13.080> plug<15:58:13.740> it<15:58:13.980> in<15:58:14.160> and<15:58:14.640> then<15:58:14.756> confirm 15:58:15.230 --> 15:58:15.240 align:start position:0% you'll say plug it in and then confirm 15:58:15.240 --> 15:58:16.550 align:start position:0% you'll say plug it in and then confirm that<15:58:15.360> they<15:58:15.480> have<15:58:15.660> unplugged<15:58:16.080> it<15:58:16.140> because<15:58:16.320> it's 15:58:16.550 --> 15:58:16.560 align:start position:0% that they have unplugged it because it's 15:58:16.560 --> 15:58:18.286 align:start position:0% that they have unplugged it because it's a<15:58:16.796> security 15:58:18.286 --> 15:58:18.296 align:start position:0% a security 15:58:18.296 --> 15:58:21.586 align:start position:0% a security um<15:58:18.360> issue<15:58:18.840> so<15:58:19.500> just<15:58:19.680> be<15:58:19.860> careful 15:58:21.586 --> 15:58:21.596 align:start position:0% um issue so just be careful 15:58:21.596 --> 15:58:23.926 align:start position:0% um issue so just be careful so<15:58:22.080> I've<15:58:22.256> mentioned<15:58:22.560> remote<15:58:22.740> hands<15:58:23.700> um<15:58:23.820> you 15:58:23.926 --> 15:58:23.936 align:start position:0% so I've mentioned remote hands um you 15:58:23.936 --> 15:58:25.670 align:start position:0% so I've mentioned remote hands um you can<15:58:24.060> use<15:58:24.180> a<15:58:24.360> console<15:58:24.720> oh<15:58:25.020> you<15:58:25.256> can<15:58:25.380> use<15:58:25.500> a 15:58:25.670 --> 15:58:25.680 align:start position:0% can use a console oh you can use a 15:58:25.680 --> 15:58:28.130 align:start position:0% can use a console oh you can use a console<15:58:26.040> router<15:58:26.456> for<15:58:26.640> multiple<15:58:27.060> out<15:58:27.776> of<15:58:27.956> band 15:58:28.130 --> 15:58:28.140 align:start position:0% console router for multiple out of band 15:58:28.140 --> 15:58:30.650 align:start position:0% console router for multiple out of band devices<15:58:28.560> so<15:58:29.276> say<15:58:29.520> you've<15:58:29.880> got<15:58:30.000> this<15:58:30.480> is 15:58:30.650 --> 15:58:30.660 align:start position:0% devices so say you've got this is 15:58:30.660 --> 15:58:32.690 align:start position:0% devices so say you've got this is normally<15:58:31.080> we<15:58:31.616> used<15:58:31.796> to<15:58:31.916> do<15:58:32.040> this<15:58:32.160> when<15:58:32.400> we<15:58:32.580> were 15:58:32.690 --> 15:58:32.700 align:start position:0% normally we used to do this when we were 15:58:32.700 --> 15:58:35.630 align:start position:0% normally we used to do this when we were practicing<15:58:33.116> for<15:58:33.360> Cisco<15:58:33.720> exams<15:58:34.200> you<15:58:34.916> out<15:58:35.160> of<15:58:35.340> a 15:58:35.630 --> 15:58:35.640 align:start position:0% practicing for Cisco exams you out of a 15:58:35.640 --> 15:58:39.106 align:start position:0% practicing for Cisco exams you out of a rack<15:58:35.936> of<15:58:36.776> all<15:58:37.020> of<15:58:37.140> these<15:58:37.380> different<15:58:37.616> routers 15:58:39.106 --> 15:58:39.116 align:start position:0% rack of all of these different routers 15:58:39.116 --> 15:58:42.890 align:start position:0% rack of all of these different routers say<15:58:39.660> router<15:58:40.140> 1<15:58:40.380> router<15:58:41.096> 2<15:58:41.400> router<15:58:42.060> 3<15:58:42.296> switch 15:58:42.890 --> 15:58:42.900 align:start position:0% say router 1 router 2 router 3 switch 15:58:42.900 --> 15:58:44.690 align:start position:0% say router 1 router 2 router 3 switch one 15:58:44.690 --> 15:58:44.700 align:start position:0% one 15:58:44.700 --> 15:58:47.390 align:start position:0% one switch<15:58:45.240> to<15:58:45.540> and<15:58:46.500> you<15:58:46.740> haven't<15:58:46.860> got<15:58:47.096> ethernet 15:58:47.390 --> 15:58:47.400 align:start position:0% switch to and you haven't got ethernet 15:58:47.400 --> 15:58:50.210 align:start position:0% switch to and you haven't got ethernet access<15:58:47.756> for<15:58:48.180> whatever<15:58:48.296> reason<15:58:48.680> so<15:58:49.680> what<15:58:49.916> you 15:58:50.210 --> 15:58:50.220 align:start position:0% access for whatever reason so what you 15:58:50.220 --> 15:58:53.746 align:start position:0% access for whatever reason so what you do<15:58:50.700> is<15:58:51.240> you'd<15:58:51.540> have<15:58:51.720> this<15:58:52.080> uh<15:58:52.616> a<15:58:53.340> console 15:58:53.746 --> 15:58:53.756 align:start position:0% do is you'd have this uh a console 15:58:53.756 --> 15:58:55.906 align:start position:0% do is you'd have this uh a console router<15:58:54.240> I<15:58:54.416> can't<15:58:54.480> fit<15:58:54.776> it<15:58:54.900> all<15:58:54.956> in<15:58:55.140> a<15:58:55.560> console 15:58:55.906 --> 15:58:55.916 align:start position:0% router I can't fit it all in a console 15:58:55.916 --> 15:58:57.710 align:start position:0% router I can't fit it all in a console router 15:58:57.710 --> 15:58:57.720 align:start position:0% router 15:58:57.720 --> 15:58:59.630 align:start position:0% router which<15:58:58.140> basically<15:58:58.500> connects<15:58:58.916> to<15:58:59.040> the<15:58:59.276> console 15:58:59.630 --> 15:58:59.640 align:start position:0% which basically connects to the console 15:58:59.640 --> 15:59:02.330 align:start position:0% which basically connects to the console ports<15:59:00.116> of<15:59:00.240> all<15:59:00.416> these<15:59:00.720> devices<15:59:01.080> now<15:59:01.916> console 15:59:02.330 --> 15:59:02.340 align:start position:0% ports of all these devices now console 15:59:02.340 --> 15:59:04.246 align:start position:0% ports of all these devices now console connections<15:59:02.880> don't<15:59:03.060> work<15:59:03.360> over<15:59:03.660> the<15:59:04.140> Internet 15:59:04.246 --> 15:59:04.256 align:start position:0% connections don't work over the Internet 15:59:04.256 --> 15:59:07.246 align:start position:0% connections don't work over the Internet it's<15:59:04.796> an<15:59:04.980> out<15:59:05.160> of<15:59:05.276> band<15:59:05.520> thing<15:59:06.416> so<15:59:06.900> what<15:59:07.080> you 15:59:07.246 --> 15:59:07.256 align:start position:0% it's an out of band thing so what you 15:59:07.256 --> 15:59:09.230 align:start position:0% it's an out of band thing so what you would<15:59:07.380> do<15:59:07.560> would<15:59:07.916> would<15:59:08.340> tell<15:59:08.640> net<15:59:08.820> to<15:59:09.060> this 15:59:09.230 --> 15:59:09.240 align:start position:0% would do would would tell net to this 15:59:09.240 --> 15:59:10.370 align:start position:0% would do would would tell net to this device<15:59:09.416> here 15:59:10.370 --> 15:59:10.380 align:start position:0% device here 15:59:10.380 --> 15:59:12.650 align:start position:0% device here and<15:59:11.040> then<15:59:11.276> through<15:59:11.640> this<15:59:11.880> router<15:59:12.240> here<15:59:12.416> it 15:59:12.650 --> 15:59:12.660 align:start position:0% and then through this router here it 15:59:12.660 --> 15:59:15.406 align:start position:0% and then through this router here it would<15:59:12.776> have<15:59:13.020> the<15:59:13.680> telnet<15:59:14.400> the<15:59:14.936> software<15:59:15.180> the 15:59:15.406 --> 15:59:15.416 align:start position:0% would have the telnet the software the 15:59:15.416 --> 15:59:17.990 align:start position:0% would have the telnet the software the client<15:59:15.660> software<15:59:16.080> that<15:59:16.916> you<15:59:17.096> could<15:59:17.340> configure 15:59:17.990 --> 15:59:18.000 align:start position:0% client software that you could configure 15:59:18.000 --> 15:59:19.606 align:start position:0% client software that you could configure all<15:59:18.296> of<15:59:18.416> these<15:59:18.596> devices<15:59:18.840> through<15:59:19.200> a<15:59:19.380> command 15:59:19.606 --> 15:59:19.616 align:start position:0% all of these devices through a command 15:59:19.616 --> 15:59:20.690 align:start position:0% all of these devices through a command line 15:59:20.690 --> 15:59:20.700 align:start position:0% line 15:59:20.700 --> 15:59:23.210 align:start position:0% line and<15:59:21.840> um<15:59:21.840> really<15:59:22.140> handy<15:59:22.436> way<15:59:22.616> of<15:59:22.740> connecting<15:59:23.040> to 15:59:23.210 --> 15:59:23.220 align:start position:0% and um really handy way of connecting to 15:59:23.220 --> 15:59:24.946 align:start position:0% and um really handy way of connecting to remote<15:59:23.400> racks<15:59:23.936> but<15:59:24.116> you<15:59:24.296> could<15:59:24.416> have<15:59:24.540> this<15:59:24.776> for 15:59:24.946 --> 15:59:24.956 align:start position:0% remote racks but you could have this for 15:59:24.956 --> 15:59:27.406 align:start position:0% remote racks but you could have this for your<15:59:25.200> corporate<15:59:26.160> Network 15:59:27.406 --> 15:59:27.416 align:start position:0% your corporate Network 15:59:27.416 --> 15:59:30.286 align:start position:0% your corporate Network this<15:59:27.900> is<15:59:28.020> an<15:59:28.200> example<15:59:28.436> of<15:59:28.680> one<15:59:28.860> this<15:59:29.340> is<15:59:29.580> a<15:59:30.116> the 15:59:30.286 --> 15:59:30.296 align:start position:0% this is an example of one this is a the 15:59:30.296 --> 15:59:32.926 align:start position:0% this is an example of one this is a the the<15:59:30.360> models<15:59:31.140> of<15:59:31.256> routers<15:59:31.616> for<15:59:31.796> Cisco<15:59:32.220> are<15:59:32.580> 25 15:59:32.926 --> 15:59:32.936 align:start position:0% the models of routers for Cisco are 25 15:59:32.936 --> 15:59:35.586 align:start position:0% the models of routers for Cisco are 25 11<15:59:33.740> and<15:59:34.740> 25 15:59:35.586 --> 15:59:35.596 align:start position:0% 11 and 25 15:59:35.596 --> 15:59:38.446 align:start position:0% 11 and 25 21.<15:59:36.596> now<15:59:36.776> you<15:59:36.956> can<15:59:37.020> see<15:59:37.256> how<15:59:37.500> old<15:59:37.680> this<15:59:37.916> is<15:59:38.096> this 15:59:38.446 --> 15:59:38.456 align:start position:0% 21. now you can see how old this is this 15:59:38.456 --> 15:59:40.246 align:start position:0% 21. now you can see how old this is this is<15:59:38.580> your<15:59:38.880> ethernet<15:59:39.296> connection<15:59:39.540> look<15:59:39.956> at<15:59:40.140> that 15:59:40.246 --> 15:59:40.256 align:start position:0% is your ethernet connection look at that 15:59:40.256 --> 15:59:41.926 align:start position:0% is your ethernet connection look at that the<15:59:40.796> aui 15:59:41.926 --> 15:59:41.936 align:start position:0% the aui 15:59:41.936 --> 15:59:43.850 align:start position:0% the aui so<15:59:42.480> what<15:59:42.660> you<15:59:42.776> do<15:59:42.956> we've<15:59:43.200> all<15:59:43.320> we've<15:59:43.616> talked 15:59:43.850 --> 15:59:43.860 align:start position:0% so what you do we've all we've talked 15:59:43.860 --> 15:59:45.946 align:start position:0% so what you do we've all we've talked about<15:59:43.980> transceivers<15:59:44.820> already<15:59:45.000> you<15:59:45.296> think<15:59:45.480> but 15:59:45.946 --> 15:59:45.956 align:start position:0% about transceivers already you think but 15:59:45.956 --> 15:59:48.286 align:start position:0% about transceivers already you think but you'd<15:59:46.200> have<15:59:46.380> this<15:59:46.560> transceiver<15:59:47.096> that's<15:59:47.820> got<15:59:48.060> a 15:59:48.286 --> 15:59:48.296 align:start position:0% you'd have this transceiver that's got a 15:59:48.296 --> 15:59:49.970 align:start position:0% you'd have this transceiver that's got a an<15:59:48.540> ethernet<15:59:48.840> port<15:59:49.200> in<15:59:49.436> here<15:59:49.560> so<15:59:49.740> you<15:59:49.860> could 15:59:49.970 --> 15:59:49.980 align:start position:0% an ethernet port in here so you could 15:59:49.980 --> 15:59:51.946 align:start position:0% an ethernet port in here so you could connect<15:59:50.096> an<15:59:50.340> Ethernet<15:59:50.700> cable<15:59:51.116> to<15:59:51.776> another 15:59:51.946 --> 15:59:51.956 align:start position:0% connect an Ethernet cable to another 15:59:51.956 --> 15:59:55.490 align:start position:0% connect an Ethernet cable to another device<15:59:52.616> which<15:59:53.220> then<15:59:53.456> lets<15:59:53.756> you<15:59:53.820> get<15:59:54.060> in<15:59:54.320> at<15:59:55.320> 10 15:59:55.490 --> 15:59:55.500 align:start position:0% device which then lets you get in at 10 15:59:55.500 --> 15:59:57.830 align:start position:0% device which then lets you get in at 10 Meg 15:59:57.830 --> 15:59:57.840 align:start position:0% Meg 15:59:57.840 --> 16:00:00.530 align:start position:0% Meg um<15:59:57.956> so<15:59:58.436> pretty<15:59:58.860> slow<15:59:59.160> uh<15:59:59.936> old-fashioned 16:00:00.530 --> 16:00:00.540 align:start position:0% um so pretty slow uh old-fashioned 16:00:00.540 --> 16:00:04.786 align:start position:0% um so pretty slow uh old-fashioned serial<16:00:00.840> connection<16:00:01.140> there<16:00:01.740> I<16:00:02.520> said<16:00:02.756> db60 16:00:04.786 --> 16:00:04.796 align:start position:0% serial connection there I said db60 16:00:04.796 --> 16:00:06.830 align:start position:0% serial connection there I said db60 and<16:00:05.220> then<16:00:05.340> your<16:00:05.580> console<16:00:06.000> port<16:00:06.240> for<16:00:06.480> console 16:00:06.830 --> 16:00:06.840 align:start position:0% and then your console port for console 16:00:06.840 --> 16:00:08.926 align:start position:0% and then your console port for console connections<16:00:07.500> this<16:00:08.096> is<16:00:08.220> your<16:00:08.400> modem<16:00:08.756> I've 16:00:08.926 --> 16:00:08.936 align:start position:0% connections this is your modem I've 16:00:08.936 --> 16:00:10.606 align:start position:0% connections this is your modem I've talked<16:00:09.296> about 16:00:10.606 --> 16:00:10.616 align:start position:0% talked about 16:00:10.616 --> 16:00:13.906 align:start position:0% talked about your<16:00:11.340> uh<16:00:11.640> for<16:00:11.880> your<16:00:12.116> outer<16:00:12.360> band<16:00:12.480> access 16:00:13.906 --> 16:00:13.916 align:start position:0% your uh for your outer band access 16:00:13.916 --> 16:00:16.730 align:start position:0% your uh for your outer band access and<16:00:14.520> what<16:00:14.820> this<16:00:15.060> is<16:00:15.240> is<16:00:15.596> a<16:00:15.900> bunch<16:00:16.020> of<16:00:16.256> console 16:00:16.730 --> 16:00:16.740 align:start position:0% and what this is is a bunch of console 16:00:16.740 --> 16:00:18.766 align:start position:0% and what this is is a bunch of console connections<16:00:17.400> so<16:00:17.640> you<16:00:17.880> can<16:00:18.000> see<16:00:18.240> one<16:00:18.540> here 16:00:18.766 --> 16:00:18.776 align:start position:0% connections so you can see one here 16:00:18.776 --> 16:00:20.570 align:start position:0% connections so you can see one here they've<16:00:19.080> all<16:00:19.256> got<16:00:19.380> numbers<16:00:19.616> on 16:00:20.570 --> 16:00:20.580 align:start position:0% they've all got numbers on 16:00:20.580 --> 16:00:23.630 align:start position:0% they've all got numbers on and<16:00:21.000> it's<16:00:21.240> numbered<16:00:21.660> one<16:00:21.840> to<16:00:22.080> eight<16:00:22.320> here<16:00:23.040> and 16:00:23.630 --> 16:00:23.640 align:start position:0% and it's numbered one to eight here and 16:00:23.640 --> 16:00:25.190 align:start position:0% and it's numbered one to eight here and then<16:00:23.756> if<16:00:23.880> you<16:00:24.000> plugged<16:00:24.296> in<16:00:24.360> the<16:00:24.480> second<16:00:24.660> one<16:00:24.900> if 16:00:25.190 --> 16:00:25.200 align:start position:0% then if you plugged in the second one if 16:00:25.200 --> 16:00:28.246 align:start position:0% then if you plugged in the second one if you<16:00:25.320> needed<16:00:26.040> um<16:00:26.040> up<16:00:26.340> to<16:00:26.400> 16<16:00:26.580> devices<16:00:27.256> then 16:00:28.246 --> 16:00:28.256 align:start position:0% you needed um up to 16 devices then 16:00:28.256 --> 16:00:29.926 align:start position:0% you needed um up to 16 devices then these<16:00:28.616> numbers<16:00:28.980> I<16:00:29.276> won't<16:00:29.400> tell<16:00:29.640> you<16:00:29.756> how<16:00:29.880> to 16:00:29.926 --> 16:00:29.936 align:start position:0% these numbers I won't tell you how to 16:00:29.936 --> 16:00:31.370 align:start position:0% these numbers I won't tell you how to configure<16:00:30.296> it<16:00:30.416> I've<16:00:30.540> got<16:00:30.720> a<16:00:30.840> video<16:00:30.956> on<16:00:31.200> YouTube 16:00:31.370 --> 16:00:31.380 align:start position:0% configure it I've got a video on YouTube 16:00:31.380 --> 16:00:33.766 align:start position:0% configure it I've got a video on YouTube if<16:00:31.740> you<16:00:31.860> want<16:00:31.980> to<16:00:32.160> look<16:00:32.936> that<16:00:33.116> up<16:00:33.240> under<16:00:33.540> my 16:00:33.766 --> 16:00:33.776 align:start position:0% if you want to look that up under my 16:00:33.776 --> 16:00:35.870 align:start position:0% if you want to look that up under my name<16:00:33.956> Paul<16:00:34.200> Browning 16:00:35.870 --> 16:00:35.880 align:start position:0% name Paul Browning 16:00:35.880 --> 16:00:37.670 align:start position:0% name Paul Browning and<16:00:36.240> you<16:00:36.480> could<16:00:36.540> connect<16:00:36.720> these<16:00:37.020> from<16:00:37.256> a<16:00:37.500> load 16:00:37.670 --> 16:00:37.680 align:start position:0% and you could connect these from a load 16:00:37.680 --> 16:00:39.586 align:start position:0% and you could connect these from a load of<16:00:37.740> other<16:00:37.796> devices<16:00:38.160> so<16:00:38.820> really<16:00:39.000> what<16:00:39.360> you<16:00:39.480> were 16:00:39.586 --> 16:00:39.596 align:start position:0% of other devices so really what you were 16:00:39.596 --> 16:00:41.030 align:start position:0% of other devices so really what you were doing<16:00:39.720> is<16:00:39.900> connecting<16:00:40.380> to<16:00:40.560> this<16:00:40.796> device 16:00:41.030 --> 16:00:41.040 align:start position:0% doing is connecting to this device 16:00:41.040 --> 16:00:43.906 align:start position:0% doing is connecting to this device whatever<16:00:41.520> this<16:00:42.000> modeler<16:00:42.596> switch<16:00:42.776> is 16:00:43.906 --> 16:00:43.916 align:start position:0% whatever this modeler switch is 16:00:43.916 --> 16:00:46.370 align:start position:0% whatever this modeler switch is but<16:00:44.520> you're<16:00:44.700> doing<16:00:44.936> it<16:00:45.116> you're<16:00:45.360> telnetting<16:00:46.080> or 16:00:46.370 --> 16:00:46.380 align:start position:0% but you're doing it you're telnetting or 16:00:46.380 --> 16:00:49.550 align:start position:0% but you're doing it you're telnetting or get<16:00:46.560> all<16:00:46.740> rem<16:00:47.096> or<16:00:48.000> connected<16:00:48.540> through<16:00:48.776> a<16:00:49.080> modem 16:00:49.550 --> 16:00:49.560 align:start position:0% get all rem or connected through a modem 16:00:49.560 --> 16:00:52.786 align:start position:0% get all rem or connected through a modem connection<16:00:49.796> to<16:00:50.160> this<16:00:50.400> device<16:00:50.720> and<16:00:51.720> then<16:00:51.900> from 16:00:52.786 --> 16:00:52.796 align:start position:0% connection to this device and then from 16:00:52.796 --> 16:00:54.710 align:start position:0% connection to this device and then from here<16:00:53.096> you're<16:00:53.640> choosing<16:00:54.000> whatever<16:00:54.116> console 16:00:54.710 --> 16:00:54.720 align:start position:0% here you're choosing whatever console 16:00:54.720 --> 16:00:57.766 align:start position:0% here you're choosing whatever console line<16:00:55.020> is<16:00:55.380> free<16:00:55.616> so<16:00:56.400> for<16:00:56.640> example<16:00:56.880> one<16:00:57.240> and<16:00:57.660> then 16:00:57.766 --> 16:00:57.776 align:start position:0% line is free so for example one and then 16:00:57.776 --> 16:00:59.990 align:start position:0% line is free so for example one and then you<16:00:57.956> can<16:00:58.140> actually<16:00:58.256> configure<16:00:58.740> this<16:00:59.040> device 16:00:59.990 --> 16:01:00.000 align:start position:0% you can actually configure this device 16:01:00.000 --> 16:01:01.786 align:start position:0% you can actually configure this device so<16:01:00.416> it's<16:01:00.540> a<16:01:00.660> slightly<16:01:01.080> longer<16:01:01.380> way<16:01:01.500> of<16:01:01.680> doing 16:01:01.786 --> 16:01:01.796 align:start position:0% so it's a slightly longer way of doing 16:01:01.796 --> 16:01:03.650 align:start position:0% so it's a slightly longer way of doing things<16:01:02.096> but 16:01:03.650 --> 16:01:03.660 align:start position:0% things but 16:01:03.660 --> 16:01:05.690 align:start position:0% things but um<16:01:03.720> that<16:01:04.140> saves<16:01:04.500> you<16:01:04.616> having<16:01:05.160> to<16:01:05.400> configure 16:01:05.690 --> 16:01:05.700 align:start position:0% um that saves you having to configure 16:01:05.700 --> 16:01:08.150 align:start position:0% um that saves you having to configure tile<16:01:06.000> net<16:01:06.240> connections 16:01:08.150 --> 16:01:08.160 align:start position:0% tile net connections 16:01:08.160 --> 16:01:11.990 align:start position:0% tile net connections to<16:01:08.640> 16<16:01:09.000> different<16:01:09.360> devices<16:01:09.840> so<16:01:10.436> pretty<16:01:10.796> handy 16:01:11.990 --> 16:01:12.000 align:start position:0% to 16 different devices so pretty handy 16:01:12.000 --> 16:01:14.746 align:start position:0% to 16 different devices so pretty handy so<16:01:12.416> we<16:01:12.540> covered<16:01:12.840> a<16:01:12.956> load<16:01:13.140> of<16:01:13.256> stuff<16:01:13.436> RDP<16:01:14.276> SSH 16:01:14.746 --> 16:01:14.756 align:start position:0% so we covered a load of stuff RDP SSH 16:01:14.756 --> 16:01:16.926 align:start position:0% so we covered a load of stuff RDP SSH VNC<16:01:15.540> telnet 16:01:16.926 --> 16:01:16.936 align:start position:0% VNC telnet 16:01:16.936 --> 16:01:20.510 align:start position:0% VNC telnet https<16:01:17.936> for<16:01:18.480> your<16:01:18.660> GUI<16:01:19.080> uh 16:01:20.510 --> 16:01:20.520 align:start position:0% https for your GUI uh 16:01:20.520 --> 16:01:23.746 align:start position:0% https for your GUI uh access<16:01:21.180> here<16:01:21.596> file<16:01:22.560> access<16:01:22.796> and<16:01:23.220> then<16:01:23.400> outer 16:01:23.746 --> 16:01:23.756 align:start position:0% access here file access and then outer 16:01:23.756 --> 16:01:25.906 align:start position:0% access here file access and then outer band<16:01:23.880> so<16:01:24.116> it<16:01:24.240> covered<16:01:24.480> a<16:01:24.596> lot<16:01:24.660> of<16:01:24.776> stuff<16:01:24.956> so 16:01:25.906 --> 16:01:25.916 align:start position:0% band so it covered a lot of stuff so 16:01:25.916 --> 16:01:27.350 align:start position:0% band so it covered a lot of stuff so thanks<16:01:26.160> for<16:01:26.340> listening<16:01:26.580> I'll<16:01:26.936> see<16:01:27.060> you<16:01:27.180> on<16:01:27.240> the 16:01:27.350 --> 16:01:27.360 align:start position:0% thanks for listening I'll see you on the 16:01:27.360 --> 16:01:31.250 align:start position:0% thanks for listening I'll see you on the next<16:01:27.480> presentation 16:01:31.250 --> 16:01:31.260 align:start position:0% 16:01:31.260 --> 16:01:51.310 align:start position:0% [Music] 16:01:51.310 --> 16:01:51.320 align:start position:0% 16:01:51.320 --> 16:01:53.470 align:start position:0% remote<16:01:52.320> access 16:01:53.470 --> 16:01:53.480 align:start position:0% remote access 16:01:53.480 --> 16:01:57.050 align:start position:0% remote access vpns<16:01:54.480> and<16:01:55.020> their<16:01:55.200> protocols 16:01:57.050 --> 16:01:57.060 align:start position:0% vpns and their protocols 16:01:57.060 --> 16:01:59.390 align:start position:0% vpns and their protocols in<16:01:57.540> the<16:01:57.720> last<16:01:57.840> two<16:01:58.080> modules<16:01:58.500> we<16:01:58.860> discussed 16:01:59.390 --> 16:01:59.400 align:start position:0% in the last two modules we discussed 16:01:59.400 --> 16:02:03.766 align:start position:0% in the last two modules we discussed remote<16:01:59.700> access<16:02:00.616> and<16:02:01.616> remote<16:02:02.160> networking<16:02:03.060> both 16:02:03.766 --> 16:02:03.776 align:start position:0% remote access and remote networking both 16:02:03.776 --> 16:02:05.570 align:start position:0% remote access and remote networking both are<16:02:04.140> basically<16:02:04.500> around<16:02:04.616> the<16:02:04.860> same<16:02:05.040> concept 16:02:05.570 --> 16:02:05.580 align:start position:0% are basically around the same concept 16:02:05.580 --> 16:02:07.786 align:start position:0% are basically around the same concept remote<16:02:05.936> networking<16:02:06.596> meaning<16:02:06.900> that<16:02:07.320> I<16:02:07.680> can 16:02:07.786 --> 16:02:07.796 align:start position:0% remote networking meaning that I can 16:02:07.796 --> 16:02:10.370 align:start position:0% remote networking meaning that I can create<16:02:07.980> a<16:02:08.220> network<16:02:08.400> that<16:02:09.116> exists<16:02:09.596> in<16:02:09.900> two<16:02:10.140> very 16:02:10.370 --> 16:02:10.380 align:start position:0% create a network that exists in two very 16:02:10.380 --> 16:02:12.350 align:start position:0% create a network that exists in two very different<16:02:10.560> geographical<16:02:11.220> locations<16:02:11.880> and 16:02:12.350 --> 16:02:12.360 align:start position:0% different geographical locations and 16:02:12.360 --> 16:02:14.926 align:start position:0% different geographical locations and remote<16:02:12.596> access<16:02:13.020> meaning<16:02:13.560> that<16:02:13.796> I<16:02:14.040> can<16:02:14.220> access 16:02:14.926 --> 16:02:14.936 align:start position:0% remote access meaning that I can access 16:02:14.936 --> 16:02:17.990 align:start position:0% remote access meaning that I can access a<16:02:15.540> computer<16:02:15.720> or<16:02:16.380> a<16:02:16.560> network<16:02:16.796> from<16:02:17.700> one 16:02:17.990 --> 16:02:18.000 align:start position:0% a computer or a network from one 16:02:18.000 --> 16:02:19.786 align:start position:0% a computer or a network from one geographic<16:02:18.540> location<16:02:18.776> to<16:02:19.200> another<16:02:19.380> so 16:02:19.786 --> 16:02:19.796 align:start position:0% geographic location to another so 16:02:19.796 --> 16:02:21.050 align:start position:0% geographic location to another so they're<16:02:19.916> both<16:02:20.160> basically<16:02:20.520> the<16:02:20.640> same<16:02:20.820> thing 16:02:21.050 --> 16:02:21.060 align:start position:0% they're both basically the same thing 16:02:21.060 --> 16:02:23.630 align:start position:0% they're both basically the same thing but<16:02:21.596> how<16:02:21.776> we<16:02:21.956> accomplish<16:02:22.500> this<16:02:22.860> in<16:02:23.220> a<16:02:23.400> secure 16:02:23.630 --> 16:02:23.640 align:start position:0% but how we accomplish this in a secure 16:02:23.640 --> 16:02:25.310 align:start position:0% but how we accomplish this in a secure fashion<16:02:24.180> is<16:02:24.660> what<16:02:24.840> we're<16:02:24.956> going<16:02:25.080> to<16:02:25.200> talk 16:02:25.310 --> 16:02:25.320 align:start position:0% fashion is what we're going to talk 16:02:25.320 --> 16:02:27.586 align:start position:0% fashion is what we're going to talk about<16:02:25.500> in<16:02:26.040> this<16:02:26.220> module<16:02:26.640> and<16:02:27.060> that<16:02:27.180> revolves 16:02:27.586 --> 16:02:27.596 align:start position:0% about in this module and that revolves 16:02:27.596 --> 16:02:30.766 align:start position:0% about in this module and that revolves around<16:02:27.720> this<16:02:28.140> term<16:02:28.320> VPN<16:02:29.220> a<16:02:29.820> VPN<16:02:30.240> I've<16:02:30.480> talked 16:02:30.766 --> 16:02:30.776 align:start position:0% around this term VPN a VPN I've talked 16:02:30.776 --> 16:02:32.390 align:start position:0% around this term VPN a VPN I've talked about<16:02:30.840> a<16:02:31.080> bit<16:02:31.200> in<16:02:31.320> the<16:02:31.500> future<16:02:31.680> in<16:02:32.096> the<16:02:32.276> past 16:02:32.390 --> 16:02:32.400 align:start position:0% about a bit in the future in the past 16:02:32.400 --> 16:02:36.050 align:start position:0% about a bit in the future in the past rather<16:02:32.820> and<16:02:33.540> it<16:02:33.900> stands<16:02:34.320> for<16:02:34.740> virtual 16:02:36.050 --> 16:02:36.060 align:start position:0% rather and it stands for virtual 16:02:36.060 --> 16:02:38.690 align:start position:0% rather and it stands for virtual private 16:02:38.690 --> 16:02:38.700 align:start position:0% private 16:02:38.700 --> 16:02:41.086 align:start position:0% private Network<16:02:39.240> and<16:02:39.660> as<16:02:39.840> that<16:02:40.140> term<16:02:40.320> implies<16:02:40.860> and 16:02:41.086 --> 16:02:41.096 align:start position:0% Network and as that term implies and 16:02:41.096 --> 16:02:44.746 align:start position:0% Network and as that term implies and like<16:02:41.276> we've<16:02:41.580> discussed<16:02:42.000> it<16:02:42.660> creates<16:02:43.020> a<16:02:43.500> tunnel 16:02:44.746 --> 16:02:44.756 align:start position:0% like we've discussed it creates a tunnel 16:02:44.756 --> 16:02:47.990 align:start position:0% like we've discussed it creates a tunnel through<16:02:45.540> the<16:02:46.256> net<16:02:46.380> the<16:02:46.740> internet<16:02:46.916> the<16:02:47.756> wide 16:02:47.990 --> 16:02:48.000 align:start position:0% through the net the internet the wide 16:02:48.000 --> 16:02:50.926 align:start position:0% through the net the internet the wide area<16:02:48.240> network<16:02:48.596> in<16:02:49.560> which<16:02:49.740> we<16:02:50.040> can<16:02:50.220> securely 16:02:50.926 --> 16:02:50.936 align:start position:0% area network in which we can securely 16:02:50.936 --> 16:02:55.130 align:start position:0% area network in which we can securely send<16:02:51.776> uh<16:02:52.500> data<16:02:52.916> between<16:02:53.400> two<16:02:53.756> locations<16:02:54.416> and 16:02:55.130 --> 16:02:55.140 align:start position:0% send uh data between two locations and 16:02:55.140 --> 16:02:56.870 align:start position:0% send uh data between two locations and why<16:02:55.320> the<16:02:55.560> tunnel<16:02:55.860> well<16:02:56.040> that's<16:02:56.220> what<16:02:56.456> keeps<16:02:56.756> it 16:02:56.870 --> 16:02:56.880 align:start position:0% why the tunnel well that's what keeps it 16:02:56.880 --> 16:02:58.850 align:start position:0% why the tunnel well that's what keeps it secure<16:02:57.296> and<16:02:57.480> private<16:02:57.900> from<16:02:58.140> everyone<16:02:58.256> else<16:02:58.560> on 16:02:58.850 --> 16:02:58.860 align:start position:0% secure and private from everyone else on 16:02:58.860 --> 16:03:00.710 align:start position:0% secure and private from everyone else on the<16:02:58.980> internet<16:02:59.160> and<16:02:59.820> this<16:02:59.936> is<16:03:00.060> how<16:03:00.240> we've<16:03:00.596> been 16:03:00.710 --> 16:03:00.720 align:start position:0% the internet and this is how we've been 16:03:00.720 --> 16:03:02.746 align:start position:0% the internet and this is how we've been able<16:03:00.956> to<16:03:01.080> allow<16:03:01.860> remote<16:03:02.040> networking<16:03:02.580> to 16:03:02.746 --> 16:03:02.756 align:start position:0% able to allow remote networking to 16:03:02.756 --> 16:03:04.550 align:start position:0% able to allow remote networking to become<16:03:03.000> so<16:03:03.240> ubiquitous<16:03:03.900> in<16:03:04.200> our<16:03:04.320> world 16:03:04.550 --> 16:03:04.560 align:start position:0% become so ubiquitous in our world 16:03:04.560 --> 16:03:06.890 align:start position:0% become so ubiquitous in our world because<16:03:05.220> I<16:03:05.580> no<16:03:05.756> longer<16:03:06.000> have<16:03:06.240> to<16:03:06.360> have<16:03:06.660> a 16:03:06.890 --> 16:03:06.900 align:start position:0% because I no longer have to have a 16:03:06.900 --> 16:03:09.170 align:start position:0% because I no longer have to have a direct<16:03:07.020> T3<16:03:07.500> or<16:03:07.740> T1<16:03:08.040> line<16:03:08.276> between<16:03:08.580> my<16:03:09.000> office 16:03:09.170 --> 16:03:09.180 align:start position:0% direct T3 or T1 line between my office 16:03:09.180 --> 16:03:11.746 align:start position:0% direct T3 or T1 line between my office and<16:03:10.140> my<16:03:10.380> home<16:03:10.560> instead<16:03:11.160> I<16:03:11.276> can<16:03:11.400> use<16:03:11.520> the 16:03:11.746 --> 16:03:11.756 align:start position:0% and my home instead I can use the 16:03:11.756 --> 16:03:13.310 align:start position:0% and my home instead I can use the internet<16:03:11.820> which<16:03:12.360> is<16:03:12.480> fairly<16:03:12.776> ubiquitous 16:03:13.310 --> 16:03:13.320 align:start position:0% internet which is fairly ubiquitous 16:03:13.320 --> 16:03:16.130 align:start position:0% internet which is fairly ubiquitous these<16:03:13.680> days<16:03:13.796> and<16:03:14.580> create<16:03:14.820> a<16:03:15.116> virtual<16:03:15.540> private 16:03:16.130 --> 16:03:16.140 align:start position:0% these days and create a virtual private 16:03:16.140 --> 16:03:18.406 align:start position:0% these days and create a virtual private Network<16:03:16.320> again<16:03:16.860> virtual<16:03:17.580> being<16:03:17.880> the<16:03:18.116> key<16:03:18.240> word 16:03:18.406 --> 16:03:18.416 align:start position:0% Network again virtual being the key word 16:03:18.416 --> 16:03:19.730 align:start position:0% Network again virtual being the key word there<16:03:18.660> because<16:03:18.900> it's<16:03:19.140> not<16:03:19.320> actually<16:03:19.500> a 16:03:19.730 --> 16:03:19.740 align:start position:0% there because it's not actually a 16:03:19.740 --> 16:03:21.106 align:start position:0% there because it's not actually a private<16:03:19.980> Network<16:03:20.160> it's<16:03:20.400> a<16:03:20.580> virtual<16:03:20.756> private 16:03:21.106 --> 16:03:21.116 align:start position:0% private Network it's a virtual private 16:03:21.116 --> 16:03:22.606 align:start position:0% private Network it's a virtual private Network<16:03:21.296> because<16:03:21.956> of<16:03:22.140> this<16:03:22.380> sort<16:03:22.500> of 16:03:22.606 --> 16:03:22.616 align:start position:0% Network because of this sort of 16:03:22.616 --> 16:03:24.050 align:start position:0% Network because of this sort of tunneling<16:03:23.096> concept<16:03:23.456> that<16:03:23.700> we're<16:03:23.820> going<16:03:23.936> to 16:03:24.050 --> 16:03:24.060 align:start position:0% tunneling concept that we're going to 16:03:24.060 --> 16:03:25.070 align:start position:0% tunneling concept that we're going to talk<16:03:24.180> about 16:03:25.070 --> 16:03:25.080 align:start position:0% talk about 16:03:25.080 --> 16:03:26.630 align:start position:0% talk about so<16:03:25.560> what<16:03:25.680> we're<16:03:25.860> going<16:03:25.980> to<16:03:26.040> talk<16:03:26.160> about<16:03:26.276> in 16:03:26.630 --> 16:03:26.640 align:start position:0% so what we're going to talk about in 16:03:26.640 --> 16:03:29.086 align:start position:0% so what we're going to talk about in this<16:03:26.820> module<16:03:27.296> is<16:03:27.900> first<16:03:28.080> to<16:03:28.320> Define<16:03:28.500> virtual 16:03:29.086 --> 16:03:29.096 align:start position:0% this module is first to Define virtual 16:03:29.096 --> 16:03:30.946 align:start position:0% this module is first to Define virtual private<16:03:29.456> networks<16:03:29.820> a<16:03:29.936> bit<16:03:30.060> more<16:03:30.240> and<16:03:30.840> then 16:03:30.946 --> 16:03:30.956 align:start position:0% private networks a bit more and then 16:03:30.956 --> 16:03:32.446 align:start position:0% private networks a bit more and then talk<16:03:31.200> about<16:03:31.320> the<16:03:31.560> different<16:03:31.680> scene<16:03:31.916> of<16:03:32.160> VPN 16:03:32.446 --> 16:03:32.456 align:start position:0% talk about the different scene of VPN 16:03:32.456 --> 16:03:34.670 align:start position:0% talk about the different scene of VPN client<16:03:32.820> and<16:03:33.060> VPN<16:03:33.480> server<16:03:33.840> we've<16:03:34.320> seen<16:03:34.500> the 16:03:34.670 --> 16:03:34.680 align:start position:0% client and VPN server we've seen the 16:03:34.680 --> 16:03:36.350 align:start position:0% client and VPN server we've seen the terms<16:03:34.916> client<16:03:35.220> and<16:03:35.400> server<16:03:35.700> in<16:03:35.820> the<16:03:35.936> past<16:03:36.000> so 16:03:36.350 --> 16:03:36.360 align:start position:0% terms client and server in the past so 16:03:36.360 --> 16:03:38.810 align:start position:0% terms client and server in the past so these<16:03:36.720> shouldn't<16:03:37.140> be<16:03:37.320> too<16:03:37.616> new<16:03:37.860> for<16:03:38.096> you 16:03:38.810 --> 16:03:38.820 align:start position:0% these shouldn't be too new for you 16:03:38.820 --> 16:03:41.446 align:start position:0% these shouldn't be too new for you then<16:03:39.360> I<16:03:39.840> want<16:03:39.956> to<16:03:40.080> talk<16:03:40.256> about<16:03:40.500> the<16:03:40.860> VPN 16:03:41.446 --> 16:03:41.456 align:start position:0% then I want to talk about the VPN 16:03:41.456 --> 16:03:43.606 align:start position:0% then I want to talk about the VPN protocols<16:03:42.296> there<16:03:42.596> are<16:03:42.720> two<16:03:42.900> specific<16:03:43.200> ones 16:03:43.606 --> 16:03:43.616 align:start position:0% protocols there are two specific ones 16:03:43.616 --> 16:03:45.710 align:start position:0% protocols there are two specific ones that<16:03:44.096> you<16:03:44.220> need<16:03:44.400> to<16:03:44.520> know<16:03:44.640> about<16:03:44.820> for<16:03:45.240> the<16:03:45.416> exam 16:03:45.710 --> 16:03:45.720 align:start position:0% that you need to know about for the exam 16:03:45.720 --> 16:03:50.570 align:start position:0% that you need to know about for the exam one<16:03:46.320> is<16:03:46.500> called<16:03:47.000> pptp<16:03:48.000> and<16:03:48.660> the<16:03:48.840> other<16:03:48.956> is<16:03:49.580> l2tp 16:03:50.570 --> 16:03:50.580 align:start position:0% one is called pptp and the other is l2tp 16:03:50.580 --> 16:03:54.230 align:start position:0% one is called pptp and the other is l2tp notice<16:03:51.480> the<16:03:51.900> T<16:03:52.080> in<16:03:52.380> there<16:03:52.560> for<16:03:52.980> tunneling 16:03:54.230 --> 16:03:54.240 align:start position:0% notice the T in there for tunneling 16:03:54.240 --> 16:03:55.786 align:start position:0% notice the T in there for tunneling so<16:03:54.660> we're<16:03:54.720> going<16:03:54.900> to<16:03:54.900> discuss<16:03:55.200> both<16:03:55.436> of<16:03:55.616> those 16:03:55.786 --> 16:03:55.796 align:start position:0% so we're going to discuss both of those 16:03:55.796 --> 16:03:59.086 align:start position:0% so we're going to discuss both of those and<16:03:56.276> how<16:03:56.520> they<16:03:56.700> all<16:03:56.820> work<16:03:57.116> all<16:03:57.900> right<16:03:58.500> so<16:03:58.916> first 16:03:59.086 --> 16:03:59.096 align:start position:0% and how they all work all right so first 16:03:59.096 --> 16:04:01.370 align:start position:0% and how they all work all right so first virtual<16:03:59.640> private<16:04:00.180> networks<16:04:00.596> a<16:04:00.840> virtual 16:04:01.370 --> 16:04:01.380 align:start position:0% virtual private networks a virtual 16:04:01.380 --> 16:04:03.830 align:start position:0% virtual private networks a virtual private<16:04:01.680> Network<16:04:01.860> or<16:04:02.220> a<16:04:02.340> VPN<16:04:02.756> is<16:04:02.936> is<16:04:03.240> nowadays 16:04:03.830 --> 16:04:03.840 align:start position:0% private Network or a VPN is is nowadays 16:04:03.840 --> 16:04:06.050 align:start position:0% private Network or a VPN is is nowadays an<16:04:04.140> essential<16:04:04.500> part<16:04:04.680> of<16:04:04.860> networking<16:04:05.340> it's 16:04:06.050 --> 16:04:06.060 align:start position:0% an essential part of networking it's 16:04:06.060 --> 16:04:08.330 align:start position:0% an essential part of networking it's basically<16:04:06.416> used<16:04:06.720> anytime<16:04:07.256> a<16:04:07.560> network<16:04:07.860> is 16:04:08.330 --> 16:04:08.340 align:start position:0% basically used anytime a network is 16:04:08.340 --> 16:04:11.030 align:start position:0% basically used anytime a network is extended<16:04:08.880> Beyond<16:04:09.360> a<16:04:10.140> lan<16:04:10.380> or<16:04:10.560> local<16:04:10.796> area 16:04:11.030 --> 16:04:11.040 align:start position:0% extended Beyond a lan or local area 16:04:11.040 --> 16:04:13.490 align:start position:0% extended Beyond a lan or local area network<16:04:11.456> so<16:04:12.360> it<16:04:12.480> establishes<16:04:13.080> a<16:04:13.380> remote 16:04:13.490 --> 16:04:13.500 align:start position:0% network so it establishes a remote 16:04:13.500 --> 16:04:16.426 align:start position:0% network so it establishes a remote connection<16:04:14.060> through<16:04:15.060> a<16:04:15.540> public<16:04:15.720> network<16:04:16.020> such 16:04:16.426 --> 16:04:16.436 align:start position:0% connection through a public network such 16:04:16.436 --> 16:04:18.946 align:start position:0% connection through a public network such as<16:04:16.560> the<16:04:16.740> internet<16:04:16.916> in<16:04:17.640> order<16:04:17.756> to<16:04:18.116> extend<16:04:18.596> the 16:04:18.946 --> 16:04:18.956 align:start position:0% as the internet in order to extend the 16:04:18.956 --> 16:04:20.510 align:start position:0% as the internet in order to extend the Lan<16:04:19.200> and<16:04:19.436> I'll<16:04:19.560> show<16:04:19.680> you<16:04:19.796> a<16:04:19.980> graphic<16:04:20.276> of<16:04:20.400> this 16:04:20.510 --> 16:04:20.520 align:start position:0% Lan and I'll show you a graphic of this 16:04:20.520 --> 16:04:23.210 align:start position:0% Lan and I'll show you a graphic of this in<16:04:20.700> just<16:04:20.820> a<16:04:20.936> second<16:04:21.540> once<16:04:22.500> the<16:04:22.616> extension<16:04:23.040> is 16:04:23.210 --> 16:04:23.220 align:start position:0% in just a second once the extension is 16:04:23.220 --> 16:04:27.650 align:start position:0% in just a second once the extension is made<16:04:23.520> a<16:04:24.416> dedicated<16:04:25.160> point-to-point<16:04:26.160> link 16:04:27.650 --> 16:04:27.660 align:start position:0% made a dedicated point-to-point link 16:04:27.660 --> 16:04:31.370 align:start position:0% made a dedicated point-to-point link point 16:04:31.370 --> 16:04:31.380 align:start position:0% 16:04:31.380 --> 16:04:33.890 align:start position:0% to<16:04:31.980> point<16:04:32.220> link<16:04:32.520> which<16:04:33.116> you<16:04:33.296> might<16:04:33.480> also<16:04:33.720> have 16:04:33.890 --> 16:04:33.900 align:start position:0% to point link which you might also have 16:04:33.900 --> 16:04:37.370 align:start position:0% to point link which you might also have seen<16:04:34.140> P2P<16:04:35.096> a<16:04:36.060> dedicated<16:04:36.480> point-to-point<16:04:37.140> link 16:04:37.370 --> 16:04:37.380 align:start position:0% seen P2P a dedicated point-to-point link 16:04:37.380 --> 16:04:39.766 align:start position:0% seen P2P a dedicated point-to-point link is<16:04:37.740> created<16:04:38.096> between<16:04:38.400> two<16:04:38.880> points<16:04:39.296> using<16:04:39.660> the 16:04:39.766 --> 16:04:39.776 align:start position:0% is created between two points using the 16:04:39.776 --> 16:04:42.586 align:start position:0% is created between two points using the same<16:04:39.900> IP<16:04:40.320> network<16:04:40.580> meaning<16:04:41.580> that<16:04:42.180> even<16:04:42.360> though 16:04:42.586 --> 16:04:42.596 align:start position:0% same IP network meaning that even though 16:04:42.596 --> 16:04:45.106 align:start position:0% same IP network meaning that even though we<16:04:42.840> are<16:04:42.956> on<16:04:43.256> two<16:04:43.500> very<16:04:43.796> different<16:04:44.096> IP<16:04:44.580> networks 16:04:45.106 --> 16:04:45.116 align:start position:0% we are on two very different IP networks 16:04:45.116 --> 16:04:47.086 align:start position:0% we are on two very different IP networks I<16:04:45.596> might<16:04:45.720> not<16:04:45.900> be<16:04:46.020> on<16:04:46.140> my<16:04:46.256> land<16:04:46.500> you<16:04:46.796> might<16:04:46.916> be 16:04:47.086 --> 16:04:47.096 align:start position:0% I might not be on my land you might be 16:04:47.096 --> 16:04:49.550 align:start position:0% I might not be on my land you might be on<16:04:47.220> yours<16:04:47.640> we<16:04:48.360> can<16:04:48.540> create<16:04:48.776> a<16:04:49.200> virtual 16:04:49.550 --> 16:04:49.560 align:start position:0% on yours we can create a virtual 16:04:49.560 --> 16:04:51.650 align:start position:0% on yours we can create a virtual point-to-point<16:04:50.456> connection<16:04:50.820> between<16:04:51.360> the 16:04:51.650 --> 16:04:51.660 align:start position:0% point-to-point connection between the 16:04:51.660 --> 16:04:53.926 align:start position:0% point-to-point connection between the two<16:04:51.840> using<16:04:52.320> tunneling<16:04:52.860> that<16:04:53.456> makes<16:04:53.640> it<16:04:53.820> as 16:04:53.926 --> 16:04:53.936 align:start position:0% two using tunneling that makes it as 16:04:53.936 --> 16:04:55.906 align:start position:0% two using tunneling that makes it as though<16:04:54.116> we<16:04:54.360> are<16:04:54.540> on<16:04:54.840> the<16:04:55.080> same<16:04:55.320> point-to-point 16:04:55.906 --> 16:04:55.916 align:start position:0% though we are on the same point-to-point 16:04:55.916 --> 16:04:58.310 align:start position:0% though we are on the same point-to-point network<16:04:56.160> the<16:04:57.000> same<16:04:57.180> IP<16:04:57.540> network<16:04:57.776> and<16:04:58.140> I'll 16:04:58.310 --> 16:04:58.320 align:start position:0% network the same IP network and I'll 16:04:58.320 --> 16:05:00.946 align:start position:0% network the same IP network and I'll show<16:04:58.860> you<16:04:58.980> that<16:04:59.096> in<16:04:59.220> just<16:04:59.340> a<16:04:59.456> second<16:04:59.640> now<16:05:00.596> the 16:05:00.946 --> 16:05:00.956 align:start position:0% show you that in just a second now the 16:05:00.956 --> 16:05:02.746 align:start position:0% show you that in just a second now the extension<16:05:01.380> of<16:05:01.500> the<16:05:01.680> Lan<16:05:01.916> are<16:05:02.160> sometimes<16:05:02.456> the 16:05:02.746 --> 16:05:02.756 align:start position:0% extension of the Lan are sometimes the 16:05:02.756 --> 16:05:05.446 align:start position:0% extension of the Lan are sometimes the linking<16:05:03.180> of<16:05:03.596> two<16:05:04.020> lands 16:05:05.446 --> 16:05:05.456 align:start position:0% linking of two lands 16:05:05.456 --> 16:05:08.446 align:start position:0% linking of two lands creates<16:05:06.240> a<16:05:06.596> new<16:05:06.776> wide<16:05:07.140> area<16:05:07.380> network<16:05:07.740> so<16:05:08.340> you 16:05:08.446 --> 16:05:08.456 align:start position:0% creates a new wide area network so you 16:05:08.456 --> 16:05:10.370 align:start position:0% creates a new wide area network so you could<16:05:08.580> say<16:05:08.700> that<16:05:08.880> anytime<16:05:09.296> a<16:05:09.540> VPN<16:05:10.020> is 16:05:10.370 --> 16:05:10.380 align:start position:0% could say that anytime a VPN is 16:05:10.380 --> 16:05:15.890 align:start position:0% could say that anytime a VPN is established 16:05:15.890 --> 16:05:15.900 align:start position:0% 16:05:15.900 --> 16:05:18.710 align:start position:0% and<16:05:16.436> a<16:05:16.740> new<16:05:16.860> land<16:05:17.040> sort<16:05:17.400> of<16:05:17.520> added<16:05:17.880> on<16:05:18.060> a<16:05:18.540> new 16:05:18.710 --> 16:05:18.720 align:start position:0% and a new land sort of added on a new 16:05:18.720 --> 16:05:21.050 align:start position:0% and a new land sort of added on a new Wan<16:05:19.140> is<16:05:19.500> created<16:05:19.916> don't<16:05:20.520> worry<16:05:20.700> too<16:05:20.880> much 16:05:21.050 --> 16:05:21.060 align:start position:0% Wan is created don't worry too much 16:05:21.060 --> 16:05:23.510 align:start position:0% Wan is created don't worry too much about<16:05:21.180> that<16:05:21.480> concept<16:05:21.840> but<16:05:22.140> the<16:05:22.380> idea<16:05:22.680> again<16:05:22.980> is 16:05:23.510 --> 16:05:23.520 align:start position:0% about that concept but the idea again is 16:05:23.520 --> 16:05:27.106 align:start position:0% about that concept but the idea again is if<16:05:23.756> I<16:05:23.936> have<16:05:24.180> the<16:05:25.020> office<16:05:25.200> slam 16:05:27.106 --> 16:05:27.116 align:start position:0% if I have the office slam 16:05:27.116 --> 16:05:30.286 align:start position:0% if I have the office slam and<16:05:27.956> let's<16:05:28.256> say<16:05:28.380> either<16:05:28.616> another<16:05:28.980> office 16:05:30.286 --> 16:05:30.296 align:start position:0% and let's say either another office 16:05:30.296 --> 16:05:35.230 align:start position:0% and let's say either another office and<16:05:30.840> then<16:05:30.956> perhaps<16:05:31.436> a<16:05:31.740> remote<16:05:31.860> user 16:05:35.230 --> 16:05:35.240 align:start position:0% 16:05:35.240 --> 16:05:38.570 align:start position:0% all<16:05:36.240> connecting<16:05:36.720> through<16:05:37.080> VPN 16:05:38.570 --> 16:05:38.580 align:start position:0% all connecting through VPN 16:05:38.580 --> 16:05:41.210 align:start position:0% all connecting through VPN over<16:05:39.360> the<16:05:40.140> internet 16:05:41.210 --> 16:05:41.220 align:start position:0% over the internet 16:05:41.220 --> 16:05:46.246 align:start position:0% over the internet I<16:05:41.700> now<16:05:41.880> have<16:05:42.060> created<16:05:42.416> an<16:05:43.140> effect 16:05:46.246 --> 16:05:46.256 align:start position:0% 16:05:46.256 --> 16:05:49.010 align:start position:0% a<16:05:46.796> wide<16:05:47.040> area<16:05:47.220> network<16:05:47.580> out<16:05:48.360> of<16:05:48.596> three<16:05:48.776> very 16:05:49.010 --> 16:05:49.020 align:start position:0% a wide area network out of three very 16:05:49.020 --> 16:05:51.530 align:start position:0% a wide area network out of three very distinct<16:05:49.500> local<16:05:49.796> area<16:05:50.160> networks<16:05:50.700> but<16:05:51.360> I 16:05:51.530 --> 16:05:51.540 align:start position:0% distinct local area networks but I 16:05:51.540 --> 16:05:52.606 align:start position:0% distinct local area networks but I haven't<16:05:51.596> used<16:05:51.900> any<16:05:52.320> different 16:05:52.606 --> 16:05:52.616 align:start position:0% haven't used any different 16:05:52.616 --> 16:05:54.350 align:start position:0% haven't used any different infrastructure<16:05:53.340> than<16:05:53.640> something<16:05:53.880> that<16:05:54.180> was 16:05:54.350 --> 16:05:54.360 align:start position:0% infrastructure than something that was 16:05:54.360 --> 16:05:55.786 align:start position:0% infrastructure than something that was already<16:05:54.720> there 16:05:55.786 --> 16:05:55.796 align:start position:0% already there 16:05:55.796 --> 16:05:58.550 align:start position:0% already there now<16:05:56.096> vpns<16:05:56.756> are<16:05:56.936> actually<16:05:57.240> a<16:05:57.900> type<16:05:58.140> of<16:05:58.380> remote 16:05:58.550 --> 16:05:58.560 align:start position:0% now vpns are actually a type of remote 16:05:58.560 --> 16:06:00.946 align:start position:0% now vpns are actually a type of remote access<16:05:58.980> probably<16:05:59.700> the<16:06:00.060> most<16:06:00.240> popular<16:06:00.540> one 16:06:00.946 --> 16:06:00.956 align:start position:0% access probably the most popular one 16:06:00.956 --> 16:06:02.926 align:start position:0% access probably the most popular one they<16:06:01.680> share<16:06:01.860> similarities<16:06:02.456> to<16:06:02.640> all<16:06:02.820> the 16:06:02.926 --> 16:06:02.936 align:start position:0% they share similarities to all the 16:06:02.936 --> 16:06:05.810 align:start position:0% they share similarities to all the different<16:06:03.060> remote<16:06:03.296> access<16:06:03.796> for<16:06:04.796> instance 16:06:05.810 --> 16:06:05.820 align:start position:0% different remote access for instance 16:06:05.820 --> 16:06:08.990 align:start position:0% different remote access for instance you<16:06:06.416> might<16:06:06.596> think<16:06:06.840> of<16:06:07.080> dialing<16:06:07.740> via<16:06:08.160> modem<16:06:08.580> but 16:06:08.990 --> 16:06:09.000 align:start position:0% you might think of dialing via modem but 16:06:09.000 --> 16:06:11.926 align:start position:0% you might think of dialing via modem but vpns<16:06:09.596> are<16:06:09.860> inexpensive<16:06:10.860> way<16:06:11.096> to<16:06:11.400> extend<16:06:11.700> your 16:06:11.926 --> 16:06:11.936 align:start position:0% vpns are inexpensive way to extend your 16:06:11.936 --> 16:06:13.670 align:start position:0% vpns are inexpensive way to extend your network<16:06:12.060> because<16:06:12.480> it<16:06:12.720> uses<16:06:12.956> the<16:06:13.200> internet<16:06:13.320> so 16:06:13.670 --> 16:06:13.680 align:start position:0% network because it uses the internet so 16:06:13.680 --> 16:06:15.470 align:start position:0% network because it uses the internet so you<16:06:13.796> don't<16:06:13.916> need<16:06:14.096> to<16:06:14.276> purchase<16:06:14.580> a<16:06:14.936> leased<16:06:15.296> line 16:06:15.470 --> 16:06:15.480 align:start position:0% you don't need to purchase a leased line 16:06:15.480 --> 16:06:17.926 align:start position:0% you don't need to purchase a leased line service<16:06:15.900> now<16:06:16.740> remote<16:06:16.916> users<16:06:17.456> just<16:06:17.700> Connect 16:06:17.926 --> 16:06:17.936 align:start position:0% service now remote users just Connect 16:06:17.936 --> 16:06:22.310 align:start position:0% service now remote users just Connect using<16:06:18.480> the<16:06:18.660> VPN<16:06:19.140> to<16:06:20.180> their<16:06:21.180> remote<16:06:21.596> office 16:06:22.310 --> 16:06:22.320 align:start position:0% using the VPN to their remote office 16:06:22.320 --> 16:06:24.106 align:start position:0% using the VPN to their remote office through<16:06:22.980> the<16:06:23.400> internet 16:06:24.106 --> 16:06:24.116 align:start position:0% through the internet 16:06:24.116 --> 16:06:26.810 align:start position:0% through the internet and<16:06:24.660> so<16:06:24.840> that's<16:06:25.080> really<16:06:25.320> the<16:06:25.560> key<16:06:25.740> here<16:06:26.040> is<16:06:26.640> it 16:06:26.810 --> 16:06:26.820 align:start position:0% and so that's really the key here is it 16:06:26.820 --> 16:06:30.890 align:start position:0% and so that's really the key here is it uses<16:06:27.240> the<16:06:27.596> internet<16:06:27.720> as<16:06:28.380> its<16:06:28.740> platform 16:06:30.890 --> 16:06:30.900 align:start position:0% uses the internet as its platform 16:06:30.900 --> 16:06:32.030 align:start position:0% uses the internet as its platform so 16:06:32.030 --> 16:06:32.040 align:start position:0% so 16:06:32.040 --> 16:06:34.906 align:start position:0% so this<16:06:32.700> is<16:06:32.820> what<16:06:33.116> access<16:06:33.416> through<16:06:33.840> a<16:06:34.140> VPN<16:06:34.616> might 16:06:34.906 --> 16:06:34.916 align:start position:0% this is what access through a VPN might 16:06:34.916 --> 16:06:38.510 align:start position:0% this is what access through a VPN might look<16:06:35.096> like<16:06:35.276> the<16:06:36.116> remote<16:06:36.296> users 16:06:38.510 --> 16:06:38.520 align:start position:0% look like the remote users 16:06:38.520 --> 16:06:41.330 align:start position:0% look like the remote users connect<16:06:39.000> let's<16:06:39.480> say<16:06:39.596> from<16:06:39.956> home<16:06:40.200> through<16:06:41.040> the 16:06:41.330 --> 16:06:41.340 align:start position:0% connect let's say from home through the 16:06:41.340 --> 16:06:44.946 align:start position:0% connect let's say from home through the internet<16:06:41.660> and<16:06:42.660> then<16:06:42.900> there<16:06:43.680> is<16:06:43.916> a 16:06:44.946 --> 16:06:44.956 align:start position:0% internet and then there is a 16:06:44.956 --> 16:06:48.106 align:start position:0% internet and then there is a authentication<16:06:45.956> server<16:06:46.500> that<16:06:46.860> verifies<16:06:47.520> that 16:06:48.106 --> 16:06:48.116 align:start position:0% authentication server that verifies that 16:06:48.116 --> 16:06:50.330 align:start position:0% authentication server that verifies that this<16:06:48.360> user<16:06:48.660> is<16:06:48.776> allowed<16:06:49.080> on<16:06:49.200> the<16:06:49.320> network<16:06:49.436> once 16:06:50.330 --> 16:06:50.340 align:start position:0% this user is allowed on the network once 16:06:50.340 --> 16:06:52.310 align:start position:0% this user is allowed on the network once you<16:06:50.400> pass<16:06:50.580> through<16:06:50.820> that<16:06:51.060> it<16:06:51.360> puts<16:06:51.596> you<16:06:51.660> into<16:06:51.956> a 16:06:52.310 --> 16:06:52.320 align:start position:0% you pass through that it puts you into a 16:06:52.320 --> 16:06:55.070 align:start position:0% you pass through that it puts you into a switch<16:06:52.500> which<16:06:53.220> then<16:06:53.520> makes<16:06:53.820> it<16:06:54.000> as<16:06:54.180> though 16:06:55.070 --> 16:06:55.080 align:start position:0% switch which then makes it as though 16:06:55.080 --> 16:06:57.830 align:start position:0% switch which then makes it as though both<16:06:55.740> of<16:06:55.916> these<16:06:56.160> computers 16:06:57.830 --> 16:06:57.840 align:start position:0% both of these computers 16:06:57.840 --> 16:07:00.890 align:start position:0% both of these computers are<16:06:58.560> on<16:06:58.860> this<16:06:59.340> LAN 16:07:00.890 --> 16:07:00.900 align:start position:0% are on this LAN 16:07:00.900 --> 16:07:05.210 align:start position:0% are on this LAN so<16:07:01.500> in<16:07:01.740> effect<16:07:01.916> I've<16:07:02.400> created<16:07:02.880> a<16:07:03.840> new<16:07:04.320> Wan 16:07:05.210 --> 16:07:05.220 align:start position:0% so in effect I've created a new Wan 16:07:05.220 --> 16:07:07.730 align:start position:0% so in effect I've created a new Wan without<16:07:06.116> having<16:07:06.480> to<16:07:06.660> lay<16:07:06.840> down<16:07:07.080> any<16:07:07.500> extra 16:07:07.730 --> 16:07:07.740 align:start position:0% without having to lay down any extra 16:07:07.740 --> 16:07:10.550 align:start position:0% without having to lay down any extra line<16:07:08.160> because<16:07:09.000> I'm<16:07:09.296> again<16:07:09.480> using<16:07:10.140> the 16:07:10.550 --> 16:07:10.560 align:start position:0% line because I'm again using the 16:07:10.560 --> 16:07:12.286 align:start position:0% line because I'm again using the internet<16:07:10.680> now 16:07:12.286 --> 16:07:12.296 align:start position:0% internet now 16:07:12.296 --> 16:07:15.830 align:start position:0% internet now say<16:07:12.660> that<16:07:12.840> this<16:07:13.080> was<16:07:13.320> an<16:07:13.680> office<16:07:13.796> building 16:07:15.830 --> 16:07:15.840 align:start position:0% say that this was an office building 16:07:15.840 --> 16:07:17.470 align:start position:0% say that this was an office building it<16:07:15.900> could<16:07:16.080> have<16:07:16.256> an<16:07:16.436> office<16:07:16.616> building<16:07:16.916> here 16:07:17.470 --> 16:07:17.480 align:start position:0% it could have an office building here 16:07:17.480 --> 16:07:20.390 align:start position:0% it could have an office building here perhaps<16:07:18.480> another<16:07:18.660> one<16:07:19.020> and<16:07:19.380> these<16:07:19.680> can<16:07:19.860> be<16:07:20.040> any 16:07:20.390 --> 16:07:20.400 align:start position:0% perhaps another one and these can be any 16:07:20.400 --> 16:07:23.746 align:start position:0% perhaps another one and these can be any place<16:07:20.700> in<16:07:20.936> the<16:07:21.116> world 16:07:23.746 --> 16:07:23.756 align:start position:0% 16:07:23.756 --> 16:07:26.690 align:start position:0% and<16:07:24.360> because<16:07:24.540> I'm<16:07:24.956> using<16:07:25.380> tunneling<16:07:26.276> through 16:07:26.690 --> 16:07:26.700 align:start position:0% and because I'm using tunneling through 16:07:26.700 --> 16:07:30.890 align:start position:0% and because I'm using tunneling through the<16:07:26.936> virtual<16:07:27.240> private<16:07:27.660> Network 16:07:30.890 --> 16:07:30.900 align:start position:0% 16:07:30.900 --> 16:07:34.606 align:start position:0% I<16:07:31.560> create<16:07:31.740> an<16:07:32.276> effect<16:07:32.456> a<16:07:32.936> tunnel<16:07:33.776> which<16:07:34.256> allows 16:07:34.606 --> 16:07:34.616 align:start position:0% I create an effect a tunnel which allows 16:07:34.616 --> 16:07:36.650 align:start position:0% I create an effect a tunnel which allows all<16:07:34.860> of<16:07:34.980> these<16:07:35.276> to<16:07:35.640> each<16:07:35.820> create<16:07:36.296> a 16:07:36.650 --> 16:07:36.660 align:start position:0% all of these to each create a 16:07:36.660 --> 16:07:38.926 align:start position:0% all of these to each create a point-to-point<16:07:37.140> connection 16:07:38.926 --> 16:07:38.936 align:start position:0% point-to-point connection 16:07:38.936 --> 16:07:41.330 align:start position:0% point-to-point connection between<16:07:39.360> themselves<16:07:40.040> and<16:07:41.040> this 16:07:41.330 --> 16:07:41.340 align:start position:0% between themselves and this 16:07:41.340 --> 16:07:43.426 align:start position:0% between themselves and this authentication<16:07:41.936> server<16:07:42.480> that<16:07:43.200> then 16:07:43.426 --> 16:07:43.436 align:start position:0% authentication server that then 16:07:43.436 --> 16:07:45.530 align:start position:0% authentication server that then basically<16:07:43.916> puts<16:07:44.340> them 16:07:45.530 --> 16:07:45.540 align:start position:0% basically puts them 16:07:45.540 --> 16:07:48.350 align:start position:0% basically puts them onto<16:07:46.140> this<16:07:46.320> Lan<16:07:46.680> so<16:07:47.340> any<16:07:47.756> one<16:07:48.000> of<16:07:48.180> these 16:07:48.350 --> 16:07:48.360 align:start position:0% onto this Lan so any one of these 16:07:48.360 --> 16:07:50.810 align:start position:0% onto this Lan so any one of these offices<16:07:48.720> is<16:07:49.140> now<16:07:49.380> part<16:07:49.796> of 16:07:50.810 --> 16:07:50.820 align:start position:0% offices is now part of 16:07:50.820 --> 16:07:53.266 align:start position:0% offices is now part of the<16:07:51.416> land<16:07:51.540> and<16:07:51.840> in<16:07:52.020> effect<16:07:52.200> then<16:07:52.560> making<16:07:52.860> a 16:07:53.266 --> 16:07:53.276 align:start position:0% the land and in effect then making a 16:07:53.276 --> 16:07:58.190 align:start position:0% the land and in effect then making a brand<16:07:53.400> new<16:07:53.640> Wan<16:07:54.416> or<16:07:54.660> wide<16:07:54.956> area<16:07:55.140> network 16:07:58.190 --> 16:07:58.200 align:start position:0% 16:07:58.200 --> 16:07:59.690 align:start position:0% now<16:07:58.560> there<16:07:58.740> are<16:07:58.860> a<16:07:58.916> lot<16:07:58.980> of<16:07:59.096> things<16:07:59.220> we<16:07:59.400> need<16:07:59.520> in 16:07:59.690 --> 16:07:59.700 align:start position:0% now there are a lot of things we need in 16:07:59.700 --> 16:08:02.446 align:start position:0% now there are a lot of things we need in order<16:07:59.880> to<16:08:00.116> set<16:08:00.416> up<16:08:00.660> a<16:08:00.900> VPN<16:08:01.380> connection<16:08:01.680> and 16:08:02.446 --> 16:08:02.456 align:start position:0% order to set up a VPN connection and 16:08:02.456 --> 16:08:04.070 align:start position:0% order to set up a VPN connection and some<16:08:02.640> of<16:08:02.756> them<16:08:02.936> are 16:08:04.070 --> 16:08:04.080 align:start position:0% some of them are 16:08:04.080 --> 16:08:05.926 align:start position:0% some of them are more<16:08:04.740> important<16:08:05.040> than<16:08:05.160> others<16:08:05.456> but<16:08:05.640> I'm<16:08:05.756> just 16:08:05.926 --> 16:08:05.936 align:start position:0% more important than others but I'm just 16:08:05.936 --> 16:08:08.630 align:start position:0% more important than others but I'm just going<16:08:06.116> to<16:08:06.296> key<16:08:06.660> in<16:08:06.900> on<16:08:07.080> the<16:08:07.200> the<16:08:07.380> main<16:08:08.340> things 16:08:08.630 --> 16:08:08.640 align:start position:0% going to key in on the the main things 16:08:08.640 --> 16:08:10.130 align:start position:0% going to key in on the the main things we<16:08:08.936> need 16:08:10.130 --> 16:08:10.140 align:start position:0% we need 16:08:10.140 --> 16:08:13.606 align:start position:0% we need first<16:08:10.680> we<16:08:11.160> need<16:08:11.276> a<16:08:11.520> VPN<16:08:12.116> client<16:08:12.900> now<16:08:13.436> the 16:08:13.606 --> 16:08:13.616 align:start position:0% first we need a VPN client now the 16:08:13.616 --> 16:08:16.310 align:start position:0% first we need a VPN client now the client<16:08:13.916> is<16:08:14.160> the<16:08:14.456> remote<16:08:14.640> access<16:08:15.116> user<16:08:15.900> without 16:08:16.310 --> 16:08:16.320 align:start position:0% client is the remote access user without 16:08:16.320 --> 16:08:18.286 align:start position:0% client is the remote access user without this<16:08:16.680> user<16:08:17.040> there's<16:08:17.276> no<16:08:17.520> point<16:08:17.756> in<16:08:17.936> setting<16:08:18.240> up 16:08:18.286 --> 16:08:18.296 align:start position:0% this user there's no point in setting up 16:08:18.296 --> 16:08:20.570 align:start position:0% this user there's no point in setting up a<16:08:18.416> VPN<16:08:18.840> so<16:08:19.080> why<16:08:19.256> bother<16:08:19.616> if<16:08:19.860> no<16:08:20.040> one<16:08:20.160> needs<16:08:20.456> to 16:08:20.570 --> 16:08:20.580 align:start position:0% a VPN so why bother if no one needs to 16:08:20.580 --> 16:08:23.210 align:start position:0% a VPN so why bother if no one needs to connect<16:08:21.020> they<16:08:22.020> are<16:08:22.380> one<16:08:22.796> of<16:08:22.916> the<16:08:23.040> most 16:08:23.210 --> 16:08:23.220 align:start position:0% connect they are one of the most 16:08:23.220 --> 16:08:25.810 align:start position:0% connect they are one of the most important<16:08:23.640> clients<16:08:24.116> or<16:08:24.540> the<16:08:24.776> ways<16:08:25.080> that<16:08:25.200> we 16:08:25.810 --> 16:08:25.820 align:start position:0% important clients or the ways that we 16:08:25.820 --> 16:08:28.310 align:start position:0% important clients or the ways that we components<16:08:26.820> rather<16:08:27.060> and<16:08:27.720> what's<16:08:27.956> interesting 16:08:28.310 --> 16:08:28.320 align:start position:0% components rather and what's interesting 16:08:28.320 --> 16:08:30.406 align:start position:0% components rather and what's interesting about<16:08:28.436> a<16:08:28.616> VPN<16:08:29.040> client<16:08:29.400> is<16:08:29.640> it<16:08:29.820> can<16:08:29.936> either<16:08:30.116> be 16:08:30.406 --> 16:08:30.416 align:start position:0% about a VPN client is it can either be 16:08:30.416 --> 16:08:32.990 align:start position:0% about a VPN client is it can either be software 16:08:32.990 --> 16:08:33.000 align:start position:0% software 16:08:33.000 --> 16:08:35.810 align:start position:0% software or<16:08:33.840> Hardware 16:08:35.810 --> 16:08:35.820 align:start position:0% or Hardware 16:08:35.820 --> 16:08:40.010 align:start position:0% or Hardware if<16:08:36.480> it's<16:08:36.720> software<16:08:37.320> then<16:08:38.160> it's 16:08:40.010 --> 16:08:40.020 align:start position:0% if it's software then it's 16:08:40.020 --> 16:08:41.690 align:start position:0% if it's software then it's built<16:08:40.616> into<16:08:40.680> the<16:08:40.980> operating<16:08:41.400> system 16:08:41.690 --> 16:08:41.700 align:start position:0% built into the operating system 16:08:41.700 --> 16:08:43.490 align:start position:0% built into the operating system generally<16:08:42.240> or<16:08:42.480> into<16:08:42.596> the<16:08:42.776> networking<16:08:43.200> package 16:08:43.490 --> 16:08:43.500 align:start position:0% generally or into the networking package 16:08:43.500 --> 16:08:46.906 align:start position:0% generally or into the networking package of<16:08:43.796> the<16:08:43.980> operating<16:08:44.276> system<16:08:44.640> if<16:08:45.416> it's<16:08:45.540> Hardware 16:08:46.906 --> 16:08:46.916 align:start position:0% of the operating system if it's Hardware 16:08:46.916 --> 16:08:49.730 align:start position:0% of the operating system if it's Hardware it's<16:08:47.096> generally<16:08:47.580> either<16:08:47.880> built 16:08:49.730 --> 16:08:49.740 align:start position:0% it's generally either built 16:08:49.740 --> 16:08:52.730 align:start position:0% it's generally either built into<16:08:50.096> the<16:08:50.400> router 16:08:52.730 --> 16:08:52.740 align:start position:0% into the router 16:08:52.740 --> 16:08:57.406 align:start position:0% into the router or<16:08:53.340> it's<16:08:53.700> a<16:08:53.936> separate<16:08:54.296> device 16:08:57.406 --> 16:08:57.416 align:start position:0% 16:08:57.416 --> 16:08:59.926 align:start position:0% which<16:08:57.900> is<16:08:58.080> generally<16:08:58.436> called 16:08:59.926 --> 16:08:59.936 align:start position:0% which is generally called 16:08:59.936 --> 16:09:03.946 align:start position:0% which is generally called VPN<16:09:00.776> concentrator 16:09:03.946 --> 16:09:03.956 align:start position:0% 16:09:03.956 --> 16:09:05.926 align:start position:0% now<16:09:04.320> the<16:09:04.500> benefit<16:09:04.680> is 16:09:05.926 --> 16:09:05.936 align:start position:0% now the benefit is 16:09:05.936 --> 16:09:10.906 align:start position:0% now the benefit is if<16:09:06.480> I<16:09:06.720> have<16:09:07.020> for<16:09:07.680> instance<16:09:07.980> two<16:09:08.936> offices 16:09:10.906 --> 16:09:10.916 align:start position:0% if I have for instance two offices 16:09:10.916 --> 16:09:12.650 align:start position:0% if I have for instance two offices we'll<16:09:11.400> call<16:09:11.580> them<16:09:11.756> office<16:09:11.936> one<16:09:12.240> and<16:09:12.480> office 16:09:12.650 --> 16:09:12.660 align:start position:0% we'll call them office one and office 16:09:12.660 --> 16:09:14.570 align:start position:0% we'll call them office one and office two<16:09:12.956> and<16:09:13.560> they<16:09:13.740> are<16:09:13.916> located<16:09:14.096> in<16:09:14.340> different 16:09:14.570 --> 16:09:14.580 align:start position:0% two and they are located in different 16:09:14.580 --> 16:09:15.890 align:start position:0% two and they are located in different parts<16:09:14.756> of<16:09:14.936> the<16:09:15.060> world 16:09:15.890 --> 16:09:15.900 align:start position:0% parts of the world 16:09:15.900 --> 16:09:18.586 align:start position:0% parts of the world but<16:09:16.380> they<16:09:16.616> both<16:09:16.796> connect<16:09:17.040> to<16:09:17.340> the<16:09:17.580> internet 16:09:18.586 --> 16:09:18.596 align:start position:0% but they both connect to the internet 16:09:18.596 --> 16:09:21.890 align:start position:0% but they both connect to the internet then<16:09:19.256> I<16:09:19.916> don't<16:09:20.040> want<16:09:20.276> each<16:09:20.820> so<16:09:21.360> let's<16:09:21.540> say<16:09:21.720> each 16:09:21.890 --> 16:09:21.900 align:start position:0% then I don't want each so let's say each 16:09:21.900 --> 16:09:24.050 align:start position:0% then I don't want each so let's say each of<16:09:22.020> these<16:09:22.140> offices<16:09:22.436> has<16:09:22.980> we'll<16:09:23.580> put<16:09:23.820> four 16:09:24.050 --> 16:09:24.060 align:start position:0% of these offices has we'll put four 16:09:24.060 --> 16:09:26.150 align:start position:0% of these offices has we'll put four users<16:09:24.416> for<16:09:24.596> now<16:09:24.840> but<16:09:25.380> let's<16:09:25.560> say<16:09:25.740> these<16:09:26.040> four 16:09:26.150 --> 16:09:26.160 align:start position:0% users for now but let's say these four 16:09:26.160 --> 16:09:29.266 align:start position:0% users for now but let's say these four really<16:09:26.456> represent<16:09:26.880> 4<16:09:27.776> 000<16:09:27.956> users<16:09:28.500> I<16:09:29.160> don't 16:09:29.266 --> 16:09:29.276 align:start position:0% really represent 4 000 users I don't 16:09:29.276 --> 16:09:31.970 align:start position:0% really represent 4 000 users I don't want<16:09:29.400> each<16:09:29.640> one<16:09:29.820> of<16:09:29.936> these<16:09:30.180> people<16:09:30.416> to<16:09:30.840> have<16:09:31.020> to 16:09:31.970 --> 16:09:31.980 align:start position:0% want each one of these people to have to 16:09:31.980 --> 16:09:34.730 align:start position:0% want each one of these people to have to set<16:09:32.580> up<16:09:32.756> on<16:09:33.360> their<16:09:33.540> computers<16:09:34.080> a<16:09:34.380> piece<16:09:34.616> of 16:09:34.730 --> 16:09:34.740 align:start position:0% set up on their computers a piece of 16:09:34.740 --> 16:09:36.406 align:start position:0% set up on their computers a piece of software<16:09:35.096> that's<16:09:35.340> going<16:09:35.520> to<16:09:35.640> allow<16:09:35.880> them<16:09:36.060> to 16:09:36.406 --> 16:09:36.416 align:start position:0% software that's going to allow them to 16:09:36.416 --> 16:09:38.446 align:start position:0% software that's going to allow them to connect 16:09:38.446 --> 16:09:38.456 align:start position:0% connect 16:09:38.456 --> 16:09:40.970 align:start position:0% connect through<16:09:39.000> this<16:09:39.240> tunnel<16:09:39.660> so<16:09:40.200> instead<16:09:40.560> what<16:09:40.796> I've 16:09:40.970 --> 16:09:40.980 align:start position:0% through this tunnel so instead what I've 16:09:40.980 --> 16:09:42.406 align:start position:0% through this tunnel so instead what I've done 16:09:42.406 --> 16:09:42.416 align:start position:0% done 16:09:42.416 --> 16:09:45.406 align:start position:0% done is<16:09:42.900> I<16:09:43.080> do<16:09:43.320> something<16:09:43.616> on<16:09:44.580> the<16:09:44.700> network<16:09:44.880> side<16:09:45.180> of 16:09:45.406 --> 16:09:45.416 align:start position:0% is I do something on the network side of 16:09:45.416 --> 16:09:47.570 align:start position:0% is I do something on the network side of the<16:09:45.596> office<16:09:45.720> for<16:09:46.500> instance<16:09:46.680> in<16:09:46.860> the<16:09:46.980> router<16:09:47.340> or 16:09:47.570 --> 16:09:47.580 align:start position:0% the office for instance in the router or 16:09:47.580 --> 16:09:50.990 align:start position:0% the office for instance in the router or with<16:09:47.820> a<16:09:48.116> device<16:09:48.740> that<16:09:49.740> automatically<16:09:50.400> creates 16:09:50.990 --> 16:09:51.000 align:start position:0% with a device that automatically creates 16:09:51.000 --> 16:09:53.926 align:start position:0% with a device that automatically creates this<16:09:51.240> tunnel<16:09:51.596> between<16:09:51.956> the<16:09:52.320> two<16:09:52.436> offices 16:09:53.926 --> 16:09:53.936 align:start position:0% this tunnel between the two offices 16:09:53.936 --> 16:09:56.746 align:start position:0% this tunnel between the two offices and<16:09:54.480> then<16:09:54.740> these<16:09:55.740> members<16:09:56.096> don't<16:09:56.340> have<16:09:56.520> to<16:09:56.580> do 16:09:56.746 --> 16:09:56.756 align:start position:0% and then these members don't have to do 16:09:56.756 --> 16:10:04.490 align:start position:0% and then these members don't have to do anything<16:09:57.020> now<16:09:58.020> if<16:09:58.320> I<16:09:58.560> am<16:09:58.796> a<16:09:59.700> lone<16:09:59.880> user<16:10:00.320> at<16:10:01.320> home 16:10:04.490 --> 16:10:04.500 align:start position:0% 16:10:04.500 --> 16:10:05.810 align:start position:0% then<16:10:04.916> I'm<16:10:05.160> probably<16:10:05.340> it's<16:10:05.520> going<16:10:05.700> to<16:10:05.700> be 16:10:05.810 --> 16:10:05.820 align:start position:0% then I'm probably it's going to be 16:10:05.820 --> 16:10:07.786 align:start position:0% then I'm probably it's going to be easier<16:10:06.180> for<16:10:06.416> me<16:10:06.540> instead<16:10:06.900> of<16:10:07.020> buying<16:10:07.380> a<16:10:07.616> device 16:10:07.786 --> 16:10:07.796 align:start position:0% easier for me instead of buying a device 16:10:07.796 --> 16:10:09.470 align:start position:0% easier for me instead of buying a device that's<16:10:08.160> going<16:10:08.340> to<16:10:08.520> allow<16:10:08.820> a<16:10:08.936> network<16:10:09.180> to 16:10:09.470 --> 16:10:09.480 align:start position:0% that's going to allow a network to 16:10:09.480 --> 16:10:12.106 align:start position:0% that's going to allow a network to always<16:10:09.660> set<16:10:09.900> up<16:10:10.080> to<16:10:10.616> just<16:10:10.860> plug<16:10:11.340> in<16:10:11.580> through<16:10:11.880> my 16:10:12.106 --> 16:10:12.116 align:start position:0% always set up to just plug in through my 16:10:12.116 --> 16:10:14.330 align:start position:0% always set up to just plug in through my computer<16:10:12.296> and<16:10:13.140> put<16:10:13.320> it<16:10:13.436> into<16:10:13.680> the<16:10:14.040> software 16:10:14.330 --> 16:10:14.340 align:start position:0% computer and put it into the software 16:10:14.340 --> 16:10:15.710 align:start position:0% computer and put it into the software whenever<16:10:14.700> I<16:10:14.936> need 16:10:15.710 --> 16:10:15.720 align:start position:0% whenever I need 16:10:15.720 --> 16:10:18.586 align:start position:0% whenever I need and<16:10:16.140> if<16:10:16.256> I<16:10:16.436> go<16:10:16.616> into<16:10:16.860> Windows<16:10:17.820> 7<16:10:17.936> real<16:10:18.240> quickly 16:10:18.586 --> 16:10:18.596 align:start position:0% and if I go into Windows 7 real quickly 16:10:18.596 --> 16:10:21.586 align:start position:0% and if I go into Windows 7 real quickly go<16:10:19.256> over<16:10:19.560> here<16:10:19.796> into 16:10:21.586 --> 16:10:21.596 align:start position:0% go over here into 16:10:21.596 --> 16:10:24.050 align:start position:0% go over here into our<16:10:22.256> Network<16:10:22.380> and<16:10:22.680> Sharing 16:10:24.050 --> 16:10:24.060 align:start position:0% our Network and Sharing 16:10:24.060 --> 16:10:26.570 align:start position:0% our Network and Sharing and<16:10:24.540> say<16:10:24.720> we<16:10:24.956> were<16:10:25.080> going<16:10:25.256> to<16:10:25.560> set<16:10:25.796> up<16:10:25.980> a<16:10:26.456> new 16:10:26.570 --> 16:10:26.580 align:start position:0% and say we were going to set up a new 16:10:26.580 --> 16:10:28.426 align:start position:0% and say we were going to set up a new network<16:10:26.936> you<16:10:27.360> can<16:10:27.480> see<16:10:27.596> right<16:10:27.776> here<16:10:28.020> it<16:10:28.200> says 16:10:28.426 --> 16:10:28.436 align:start position:0% network you can see right here it says 16:10:28.436 --> 16:10:30.890 align:start position:0% network you can see right here it says set<16:10:28.616> up<16:10:28.740> a<16:10:28.916> VPN<16:10:29.400> connection<16:10:29.700> and<16:10:30.480> if<16:10:30.596> we<16:10:30.720> go<16:10:30.776> and 16:10:30.890 --> 16:10:30.900 align:start position:0% set up a VPN connection and if we go and 16:10:30.900 --> 16:10:32.870 align:start position:0% set up a VPN connection and if we go and do<16:10:31.080> this<16:10:31.256> you<16:10:31.740> can<16:10:31.860> actually<16:10:31.980> connect<16:10:32.400> to<16:10:32.640> a 16:10:32.870 --> 16:10:32.880 align:start position:0% do this you can actually connect to a 16:10:32.880 --> 16:10:34.426 align:start position:0% do this you can actually connect to a workplace<16:10:33.240> now<16:10:33.540> connecting<16:10:33.900> to<16:10:34.020> a<16:10:34.200> workplace 16:10:34.426 --> 16:10:34.436 align:start position:0% workplace now connecting to a workplace 16:10:34.436 --> 16:10:35.926 align:start position:0% workplace now connecting to a workplace what<16:10:34.616> they<16:10:34.796> really<16:10:34.916> mean<16:10:35.160> is<16:10:35.400> setting<16:10:35.700> up<16:10:35.756> a 16:10:35.926 --> 16:10:35.936 align:start position:0% what they really mean is setting up a 16:10:35.936 --> 16:10:37.786 align:start position:0% what they really mean is setting up a VPN<16:10:36.360> connection<16:10:36.660> so<16:10:37.320> I'm<16:10:37.436> going<16:10:37.560> to<16:10:37.616> click 16:10:37.786 --> 16:10:37.796 align:start position:0% VPN connection so I'm going to click 16:10:37.796 --> 16:10:38.746 align:start position:0% VPN connection so I'm going to click next 16:10:38.746 --> 16:10:38.756 align:start position:0% next 16:10:38.756 --> 16:10:40.070 align:start position:0% next now<16:10:39.116> you<16:10:39.240> can<16:10:39.360> see<16:10:39.416> I<16:10:39.596> can<16:10:39.660> either<16:10:39.776> dial 16:10:40.070 --> 16:10:40.080 align:start position:0% now you can see I can either dial 16:10:40.080 --> 16:10:41.630 align:start position:0% now you can see I can either dial directly<16:10:40.680> which<16:10:41.096> is<16:10:41.220> something<16:10:41.400> that<16:10:41.580> we 16:10:41.630 --> 16:10:41.640 align:start position:0% directly which is something that we 16:10:41.640 --> 16:10:43.190 align:start position:0% directly which is something that we might<16:10:41.756> have<16:10:41.880> done<16:10:42.000> years<16:10:42.180> ago<16:10:42.416> or<16:10:42.720> one<16:10:42.956> the<16:10:43.140> one 16:10:43.190 --> 16:10:43.200 align:start position:0% might have done years ago or one the one 16:10:43.200 --> 16:10:45.106 align:start position:0% might have done years ago or one the one we're<16:10:43.320> going<16:10:43.436> to<16:10:43.500> use<16:10:43.560> more<16:10:43.796> likely<16:10:44.700> now<16:10:44.880> is 16:10:45.106 --> 16:10:45.116 align:start position:0% we're going to use more likely now is 16:10:45.116 --> 16:10:46.606 align:start position:0% we're going to use more likely now is the<16:10:45.416> through<16:10:45.900> the<16:10:46.140> internet<16:10:46.256> connection 16:10:46.606 --> 16:10:46.616 align:start position:0% the through the internet connection 16:10:46.616 --> 16:10:48.650 align:start position:0% the through the internet connection again<16:10:46.980> creating<16:10:47.400> that<16:10:47.520> VPN 16:10:48.650 --> 16:10:48.660 align:start position:0% again creating that VPN 16:10:48.660 --> 16:10:50.510 align:start position:0% again creating that VPN we<16:10:49.200> could<16:10:49.320> call<16:10:49.500> this<16:10:49.680> whatever<16:10:49.916> now<16:10:50.276> one 16:10:50.510 --> 16:10:50.520 align:start position:0% we could call this whatever now one 16:10:50.520 --> 16:10:52.606 align:start position:0% we could call this whatever now one thing<16:10:50.640> we<16:10:50.820> would<16:10:50.936> need<16:10:51.116> here<16:10:51.360> is<16:10:51.776> the<16:10:52.200> server 16:10:52.606 --> 16:10:52.616 align:start position:0% thing we would need here is the server 16:10:52.616 --> 16:10:55.490 align:start position:0% thing we would need here is the server address<16:10:52.916> we'll<16:10:53.340> talk<16:10:53.520> about<16:10:53.640> that<16:10:53.880> but<16:10:54.540> why<16:10:54.840> in 16:10:55.490 --> 16:10:55.500 align:start position:0% address we'll talk about that but why in 16:10:55.500 --> 16:10:56.926 align:start position:0% address we'll talk about that but why in just<16:10:55.560> a<16:10:55.740> second<16:10:55.796> but<16:10:56.040> we<16:10:56.220> are<16:10:56.340> the<16:10:56.456> client<16:10:56.756> and 16:10:56.926 --> 16:10:56.936 align:start position:0% just a second but we are the client and 16:10:56.936 --> 16:10:58.786 align:start position:0% just a second but we are the client and we<16:10:57.060> need<16:10:57.180> to<16:10:57.240> connect<16:10:57.360> to<16:10:57.596> a<16:10:57.776> server<16:10:58.140> so<16:10:58.616> this 16:10:58.786 --> 16:10:58.796 align:start position:0% we need to connect to a server so this 16:10:58.796 --> 16:11:02.746 align:start position:0% we need to connect to a server so this is<16:10:58.916> where<16:10:59.340> for<16:11:00.000> instance<16:11:00.296> that 16:11:02.746 --> 16:11:02.756 align:start position:0% is where for instance that 16:11:02.756 --> 16:11:04.730 align:start position:0% is where for instance that server<16:11:03.296> address<16:11:03.480> is<16:11:03.720> going<16:11:03.900> to<16:11:04.020> go<16:11:04.140> now<16:11:04.560> you 16:11:04.730 --> 16:11:04.740 align:start position:0% server address is going to go now you 16:11:04.740 --> 16:11:06.406 align:start position:0% server address is going to go now you know<16:11:04.916> this<16:11:05.220> IP<16:11:05.580> address<16:11:05.756> wouldn't<16:11:06.116> work 16:11:06.406 --> 16:11:06.416 align:start position:0% know this IP address wouldn't work 16:11:06.416 --> 16:11:08.746 align:start position:0% know this IP address wouldn't work because<16:11:06.776> this<16:11:07.200> is<16:11:07.380> a<16:11:07.616> private<16:11:07.980> IP<16:11:08.276> address<16:11:08.456> but 16:11:08.746 --> 16:11:08.756 align:start position:0% because this is a private IP address but 16:11:08.756 --> 16:11:10.786 align:start position:0% because this is a private IP address but we're<16:11:08.880> just<16:11:09.060> using<16:11:09.296> this<16:11:09.480> for<16:11:09.840> the<16:11:10.436> time<16:11:10.616> being 16:11:10.786 --> 16:11:10.796 align:start position:0% we're just using this for the time being 16:11:10.796 --> 16:11:14.210 align:start position:0% we're just using this for the time being right<16:11:11.096> here<16:11:11.340> you<16:11:12.060> can<16:11:12.180> use<16:11:12.360> sharing<16:11:13.560> Etc<16:11:13.680> but 16:11:14.210 --> 16:11:14.220 align:start position:0% right here you can use sharing Etc but 16:11:14.220 --> 16:11:15.286 align:start position:0% right here you can use sharing Etc but for<16:11:14.400> right<16:11:14.580> now<16:11:14.700> let's<16:11:14.880> just<16:11:15.000> go<16:11:15.116> ahead<16:11:15.240> and 16:11:15.286 --> 16:11:15.296 align:start position:0% for right now let's just go ahead and 16:11:15.296 --> 16:11:17.030 align:start position:0% for right now let's just go ahead and click<16:11:15.596> next 16:11:17.030 --> 16:11:17.040 align:start position:0% click next 16:11:17.040 --> 16:11:19.190 align:start position:0% click next let's<16:11:17.520> say<16:11:17.700> our<16:11:17.820> username 16:11:19.190 --> 16:11:19.200 align:start position:0% let's say our username 16:11:19.200 --> 16:11:21.710 align:start position:0% let's say our username so<16:11:19.740> let's<16:11:19.916> say<16:11:20.096> user<16:11:20.580> and<16:11:20.936> then<16:11:21.060> we<16:11:21.416> have<16:11:21.596> a 16:11:21.710 --> 16:11:21.720 align:start position:0% so let's say user and then we have a 16:11:21.720 --> 16:11:23.510 align:start position:0% so let's say user and then we have a password<16:11:21.956> I'm<16:11:22.436> just<16:11:22.616> going<16:11:22.796> to<16:11:22.860> do<16:11:23.220> password 16:11:23.510 --> 16:11:23.520 align:start position:0% password I'm just going to do password 16:11:23.520 --> 16:11:25.490 align:start position:0% password I'm just going to do password we<16:11:24.060> can<16:11:24.180> have<16:11:24.296> it<16:11:24.480> remember<16:11:24.596> the<16:11:24.956> password<16:11:25.140> or 16:11:25.490 --> 16:11:25.500 align:start position:0% we can have it remember the password or 16:11:25.500 --> 16:11:26.926 align:start position:0% we can have it remember the password or not<16:11:25.616> you<16:11:25.860> might<16:11:25.980> have<16:11:26.160> a<16:11:26.400> domain<16:11:26.640> if<16:11:26.820> you're 16:11:26.926 --> 16:11:26.936 align:start position:0% not you might have a domain if you're 16:11:26.936 --> 16:11:28.670 align:start position:0% not you might have a domain if you're connecting<16:11:27.240> to<16:11:27.360> a<16:11:27.540> Windows<16:11:27.776> computer<16:11:27.956> and 16:11:28.670 --> 16:11:28.680 align:start position:0% connecting to a Windows computer and 16:11:28.680 --> 16:11:30.406 align:start position:0% connecting to a Windows computer and then<16:11:28.796> you<16:11:28.980> click<16:11:29.276> connect 16:11:30.406 --> 16:11:30.416 align:start position:0% then you click connect 16:11:30.416 --> 16:11:32.150 align:start position:0% then you click connect the<16:11:30.840> next<16:11:30.900> thing<16:11:31.080> I<16:11:31.256> need<16:11:31.436> obviously<16:11:31.980> is 16:11:32.150 --> 16:11:32.160 align:start position:0% the next thing I need obviously is 16:11:32.160 --> 16:11:34.426 align:start position:0% the next thing I need obviously is something<16:11:32.340> for<16:11:32.640> the<16:11:33.000> VPN<16:11:33.596> client<16:11:34.020> to<16:11:34.320> connect 16:11:34.426 --> 16:11:34.436 align:start position:0% something for the VPN client to connect 16:11:34.436 --> 16:11:37.730 align:start position:0% something for the VPN client to connect to<16:11:34.740> and<16:11:35.096> this<16:11:35.276> is<16:11:35.400> the<16:11:35.580> VPN<16:11:36.060> server<16:11:36.720> the<16:11:37.320> VPN 16:11:37.730 --> 16:11:37.740 align:start position:0% to and this is the VPN server the VPN 16:11:37.740 --> 16:11:40.130 align:start position:0% to and this is the VPN server the VPN server<16:11:38.220> not<16:11:39.000> only<16:11:39.180> allows<16:11:39.596> the<16:11:39.720> connection<16:11:39.840> to 16:11:40.130 --> 16:11:40.140 align:start position:0% server not only allows the connection to 16:11:40.140 --> 16:11:43.310 align:start position:0% server not only allows the connection to take<16:11:40.320> place<16:11:40.616> but<16:11:41.400> is<16:11:41.640> also<16:11:42.060> going<16:11:42.776> to 16:11:43.310 --> 16:11:43.320 align:start position:0% take place but is also going to 16:11:43.320 --> 16:11:46.606 align:start position:0% take place but is also going to authenticate 16:11:46.606 --> 16:11:46.616 align:start position:0% 16:11:46.616 --> 16:11:51.406 align:start position:0% the<16:11:47.276> client<16:11:47.640> and<16:11:48.060> allow<16:11:48.296> them<16:11:48.480> to<16:11:48.720> connect 16:11:51.406 --> 16:11:51.416 align:start position:0% 16:11:51.416 --> 16:11:53.330 align:start position:0% now<16:11:52.020> this<16:11:52.256> might<16:11:52.436> be<16:11:52.560> done<16:11:52.796> through<16:11:53.040> again 16:11:53.330 --> 16:11:53.340 align:start position:0% now this might be done through again 16:11:53.340 --> 16:11:55.426 align:start position:0% now this might be done through again some<16:11:53.700> sort<16:11:53.880> of<16:11:53.936> device<16:11:54.180> like<16:11:54.660> this<16:11:54.840> VPN 16:11:55.426 --> 16:11:55.436 align:start position:0% some sort of device like this VPN 16:11:55.436 --> 16:11:58.070 align:start position:0% some sort of device like this VPN concentrator<16:11:56.040> I've<16:11:56.276> mentioned<16:11:56.700> or<16:11:57.416> through<16:11:57.840> a 16:11:58.070 --> 16:11:58.080 align:start position:0% concentrator I've mentioned or through a 16:11:58.080 --> 16:12:00.050 align:start position:0% concentrator I've mentioned or through a separate<16:11:58.320> server<16:11:58.680> that<16:11:58.980> has<16:11:59.220> software<16:11:59.700> hooked 16:12:00.050 --> 16:12:00.060 align:start position:0% separate server that has software hooked 16:12:00.060 --> 16:12:03.170 align:start position:0% separate server that has software hooked up<16:12:00.180> on<16:12:00.360> it<16:12:00.540> either<16:12:01.200> way<16:12:01.500> I<16:12:02.276> need<16:12:02.456> some<16:12:02.880> sort<16:12:03.060> of 16:12:03.170 --> 16:12:03.180 align:start position:0% up on it either way I need some sort of 16:12:03.180 --> 16:12:05.390 align:start position:0% up on it either way I need some sort of device 16:12:05.390 --> 16:12:05.400 align:start position:0% device 16:12:05.400 --> 16:12:08.390 align:start position:0% device that<16:12:05.936> allows 16:12:08.390 --> 16:12:08.400 align:start position:0% that allows 16:12:08.400 --> 16:12:11.266 align:start position:0% that allows outside 16:12:11.266 --> 16:12:11.276 align:start position:0% 16:12:11.276 --> 16:12:12.830 align:start position:0% clients 16:12:12.830 --> 16:12:12.840 align:start position:0% clients 16:12:12.840 --> 16:12:15.230 align:start position:0% clients to<16:12:13.256> connect<16:12:13.436> in<16:12:13.916> to<16:12:14.276> the<16:12:14.456> network<16:12:14.640> basically 16:12:15.230 --> 16:12:15.240 align:start position:0% to connect in to the network basically 16:12:15.240 --> 16:12:17.210 align:start position:0% to connect in to the network basically to<16:12:15.480> give<16:12:15.596> them<16:12:15.776> permission<16:12:16.140> act<16:12:16.380> as<16:12:16.616> sort<16:12:16.860> of<16:12:16.980> a 16:12:17.210 --> 16:12:17.220 align:start position:0% to give them permission act as sort of a 16:12:17.220 --> 16:12:20.230 align:start position:0% to give them permission act as sort of a a<16:12:17.640> controller<16:12:18.360> or<16:12:18.540> or<16:12:18.660> a<16:12:19.020> Gates<16:12:19.256> person 16:12:20.230 --> 16:12:20.240 align:start position:0% a controller or or a Gates person 16:12:20.240 --> 16:12:22.730 align:start position:0% a controller or or a Gates person uh<16:12:21.240> there<16:12:21.776> are<16:12:21.900> different<16:12:22.020> ways<16:12:22.320> of<16:12:22.380> setting 16:12:22.730 --> 16:12:22.740 align:start position:0% uh there are different ways of setting 16:12:22.740 --> 16:12:24.230 align:start position:0% uh there are different ways of setting this<16:12:22.860> up<16:12:22.980> and<16:12:23.160> you<16:12:23.340> remember<16:12:23.456> I<16:12:23.820> mentioned 16:12:24.230 --> 16:12:24.240 align:start position:0% this up and you remember I mentioned 16:12:24.240 --> 16:12:26.690 align:start position:0% this up and you remember I mentioned something<16:12:24.480> called<16:12:24.720> an<16:12:24.956> Ras<16:12:25.320> remote<16:12:26.160> access 16:12:26.690 --> 16:12:26.700 align:start position:0% something called an Ras remote access 16:12:26.700 --> 16:12:29.330 align:start position:0% something called an Ras remote access server<16:12:27.540> and<16:12:28.140> the<16:12:28.256> specific<16:12:28.500> one<16:12:28.740> we<16:12:28.916> mentioned 16:12:29.330 --> 16:12:29.340 align:start position:0% server and the specific one we mentioned 16:12:29.340 --> 16:12:33.170 align:start position:0% server and the specific one we mentioned previously<16:12:30.000> was<16:12:30.296> a<16:12:30.596> radius<16:12:30.956> server 16:12:33.170 --> 16:12:33.180 align:start position:0% previously was a radius server 16:12:33.180 --> 16:12:36.890 align:start position:0% previously was a radius server which<16:12:33.660> was<16:12:33.900> a<16:12:34.140> remote<16:12:34.380> access<16:12:34.980> dial-in<16:12:35.900> uh 16:12:36.890 --> 16:12:36.900 align:start position:0% which was a remote access dial-in uh 16:12:36.900 --> 16:12:39.230 align:start position:0% which was a remote access dial-in uh server<16:12:37.320> and 16:12:39.230 --> 16:12:39.240 align:start position:0% server and 16:12:39.240 --> 16:12:41.710 align:start position:0% server and although<16:12:39.840> this<16:12:40.080> was<16:12:40.200> for<16:12:40.436> dial<16:12:40.680> up<16:12:40.980> it<16:12:41.276> still 16:12:41.710 --> 16:12:41.720 align:start position:0% although this was for dial up it still 16:12:41.720 --> 16:12:44.210 align:start position:0% although this was for dial up it still does<16:12:42.720> the<16:12:43.020> same<16:12:43.140> thing<16:12:43.256> which<16:12:43.500> is<16:12:43.616> it<16:12:43.796> allows 16:12:44.210 --> 16:12:44.220 align:start position:0% does the same thing which is it allows 16:12:44.220 --> 16:12:47.510 align:start position:0% does the same thing which is it allows someone<16:12:44.456> to<16:12:45.180> remotely<16:12:45.596> access<16:12:46.380> the<16:12:47.340> local 16:12:47.510 --> 16:12:47.520 align:start position:0% someone to remotely access the local 16:12:47.520 --> 16:12:50.570 align:start position:0% someone to remotely access the local network<16:12:47.820> so<16:12:48.416> we<16:12:48.540> have<16:12:48.660> some<16:12:48.900> sort<16:12:49.080> of<16:12:49.140> Ras<16:12:49.680> and 16:12:50.570 --> 16:12:50.580 align:start position:0% network so we have some sort of Ras and 16:12:50.580 --> 16:12:53.150 align:start position:0% network so we have some sort of Ras and again<16:12:50.756> an<16:12:51.180> Ras<16:12:51.680> stands<16:12:52.680> for<16:12:52.796> let<16:12:52.980> me<16:12:53.040> just 16:12:53.150 --> 16:12:53.160 align:start position:0% again an Ras stands for let me just 16:12:53.160 --> 16:12:55.970 align:start position:0% again an Ras stands for let me just write<16:12:53.400> that<16:12:53.580> out<16:12:53.756> remote 16:12:55.970 --> 16:12:55.980 align:start position:0% write that out remote 16:12:55.980 --> 16:12:58.130 align:start position:0% write that out remote access 16:12:58.130 --> 16:12:58.140 align:start position:0% access 16:12:58.140 --> 16:13:01.786 align:start position:0% access server 16:13:01.786 --> 16:13:01.796 align:start position:0% 16:13:01.796 --> 16:13:04.730 align:start position:0% now<16:13:02.400> the<16:13:02.820> access<16:13:03.000> method<16:13:03.776> is<16:13:04.080> also<16:13:04.380> pretty 16:13:04.730 --> 16:13:04.740 align:start position:0% now the access method is also pretty 16:13:04.740 --> 16:13:07.490 align:start position:0% now the access method is also pretty important<16:13:05.480> without<16:13:06.480> a<16:13:06.900> connection<16:13:07.020> there's 16:13:07.490 --> 16:13:07.500 align:start position:0% important without a connection there's 16:13:07.500 --> 16:13:08.990 align:start position:0% important without a connection there's no<16:13:07.680> way<16:13:07.860> for<16:13:07.980> a<16:13:08.096> user<16:13:08.340> to<16:13:08.456> get<16:13:08.580> onto<16:13:08.880> the 16:13:08.990 --> 16:13:09.000 align:start position:0% no way for a user to get onto the 16:13:09.000 --> 16:13:10.786 align:start position:0% no way for a user to get onto the network<16:13:09.116> so<16:13:09.480> most<16:13:09.660> of<16:13:09.840> the<16:13:09.900> time<16:13:10.140> this 16:13:10.786 --> 16:13:10.796 align:start position:0% network so most of the time this 16:13:10.796 --> 16:13:12.470 align:start position:0% network so most of the time this connection<16:13:10.980> comes<16:13:11.520> from<16:13:11.580> the<16:13:11.756> internet<16:13:11.880> but 16:13:12.470 --> 16:13:12.480 align:start position:0% connection comes from the internet but 16:13:12.480 --> 16:13:14.150 align:start position:0% connection comes from the internet but it's<16:13:12.660> not<16:13:12.900> uncommon<16:13:13.380> for<16:13:13.616> a<16:13:13.740> VPN 16:13:14.150 --> 16:13:14.160 align:start position:0% it's not uncommon for a VPN 16:13:14.160 --> 16:13:15.650 align:start position:0% it's not uncommon for a VPN implementation<16:13:14.756> to<16:13:15.000> actually<16:13:15.240> come<16:13:15.480> through 16:13:15.650 --> 16:13:15.660 align:start position:0% implementation to actually come through 16:13:15.660 --> 16:13:18.890 align:start position:0% implementation to actually come through a<16:13:15.956> private<16:13:16.796> intranet<16:13:17.520> as<16:13:17.756> well<16:13:17.936> so<16:13:18.596> we<16:13:18.776> have 16:13:18.890 --> 16:13:18.900 align:start position:0% a private intranet as well so we have 16:13:18.900 --> 16:13:21.106 align:start position:0% a private intranet as well so we have the<16:13:19.200> internet<16:13:19.436> which<16:13:20.096> is<16:13:20.220> the<16:13:20.520> public<16:13:20.700> version 16:13:21.106 --> 16:13:21.116 align:start position:0% the internet which is the public version 16:13:21.116 --> 16:13:23.106 align:start position:0% the internet which is the public version but<16:13:21.840> there's<16:13:22.020> also<16:13:22.256> something<16:13:22.500> called<16:13:22.796> the 16:13:23.106 --> 16:13:23.116 align:start position:0% but there's also something called the 16:13:23.116 --> 16:13:25.490 align:start position:0% but there's also something called the intranet<16:13:24.116> if<16:13:24.360> you<16:13:24.480> recall<16:13:24.840> the<16:13:25.020> internet<16:13:25.140> is 16:13:25.490 --> 16:13:25.500 align:start position:0% intranet if you recall the internet is 16:13:25.500 --> 16:13:28.786 align:start position:0% intranet if you recall the internet is like<16:13:25.616> a<16:13:25.916> private<16:13:26.340> internet<16:13:26.720> and<16:13:27.720> sometimes<16:13:28.256> we 16:13:28.786 --> 16:13:28.796 align:start position:0% like a private internet and sometimes we 16:13:28.796 --> 16:13:31.070 align:start position:0% like a private internet and sometimes we might<16:13:28.980> actually<16:13:29.340> have<16:13:29.936> a<16:13:30.360> private<16:13:30.660> leased 16:13:31.070 --> 16:13:31.080 align:start position:0% might actually have a private leased 16:13:31.080 --> 16:13:33.470 align:start position:0% might actually have a private leased line<16:13:31.256> or<16:13:31.860> we<16:13:32.040> have<16:13:32.220> several<16:13:32.756> different<16:13:33.000> sub 16:13:33.470 --> 16:13:33.480 align:start position:0% line or we have several different sub 16:13:33.480 --> 16:13:35.926 align:start position:0% line or we have several different sub networks<16:13:34.020> within<16:13:34.380> a<16:13:34.560> larger<16:13:34.860> Network<16:13:35.160> and<16:13:35.756> so 16:13:35.926 --> 16:13:35.936 align:start position:0% networks within a larger Network and so 16:13:35.936 --> 16:13:37.670 align:start position:0% networks within a larger Network and so it's<16:13:36.116> important<16:13:36.480> to<16:13:36.660> know<16:13:36.840> where<16:13:37.380> your<16:13:37.560> people 16:13:37.670 --> 16:13:37.680 align:start position:0% it's important to know where your people 16:13:37.680 --> 16:13:39.830 align:start position:0% it's important to know where your people are<16:13:37.916> connecting<16:13:38.340> from<16:13:38.580> most<16:13:39.296> the<16:13:39.540> time<16:13:39.660> you're 16:13:39.830 --> 16:13:39.840 align:start position:0% are connecting from most the time you're 16:13:39.840 --> 16:13:41.446 align:start position:0% are connecting from most the time you're not<16:13:40.020> going<16:13:40.140> to<16:13:40.320> see<16:13:40.380> the<16:13:40.616> intranet<16:13:41.160> it's<16:13:41.340> all 16:13:41.446 --> 16:13:41.456 align:start position:0% not going to see the intranet it's all 16:13:41.456 --> 16:13:43.130 align:start position:0% not going to see the intranet it's all going<16:13:41.580> to<16:13:41.700> be<16:13:41.756> through<16:13:41.936> the<16:13:42.180> internet<16:13:42.416> and 16:13:43.130 --> 16:13:43.140 align:start position:0% going to be through the internet and 16:13:43.140 --> 16:13:43.970 align:start position:0% going to be through the internet and sometimes<16:13:43.380> you'll<16:13:43.560> also<16:13:43.740> have<16:13:43.796> people 16:13:43.970 --> 16:13:43.980 align:start position:0% sometimes you'll also have people 16:13:43.980 --> 16:13:46.130 align:start position:0% sometimes you'll also have people dialing<16:13:44.520> up<16:13:44.700> so<16:13:45.000> it's<16:13:45.180> all<16:13:45.360> important<16:13:45.776> to<16:13:45.956> know 16:13:46.130 --> 16:13:46.140 align:start position:0% dialing up so it's all important to know 16:13:46.140 --> 16:13:48.050 align:start position:0% dialing up so it's all important to know even<16:13:46.796> though<16:13:46.916> internet<16:13:47.096> is<16:13:47.456> the<16:13:47.640> most<16:13:47.820> popular 16:13:48.050 --> 16:13:48.060 align:start position:0% even though internet is the most popular 16:13:48.060 --> 16:13:49.370 align:start position:0% even though internet is the most popular sometimes<16:13:48.596> we're<16:13:48.776> going<16:13:48.900> to<16:13:48.956> be<16:13:49.020> doing<16:13:49.200> it 16:13:49.370 --> 16:13:49.380 align:start position:0% sometimes we're going to be doing it 16:13:49.380 --> 16:13:51.530 align:start position:0% sometimes we're going to be doing it internally<16:13:49.796> through<16:13:50.040> an<16:13:50.220> intranet<16:13:50.756> and 16:13:51.530 --> 16:13:51.540 align:start position:0% internally through an intranet and 16:13:51.540 --> 16:13:53.746 align:start position:0% internally through an intranet and finally<16:13:51.840> there<16:13:52.256> are<16:13:52.380> two<16:13:52.680> protocols<16:13:53.456> that<16:13:53.640> we 16:13:53.746 --> 16:13:53.756 align:start position:0% finally there are two protocols that we 16:13:53.756 --> 16:13:55.246 align:start position:0% finally there are two protocols that we need<16:13:53.880> to<16:13:54.000> know<16:13:54.116> about<16:13:54.296> and<16:13:54.596> the<16:13:54.776> generally<16:13:55.020> are 16:13:55.246 --> 16:13:55.256 align:start position:0% need to know about and the generally are 16:13:55.256 --> 16:13:57.350 align:start position:0% need to know about and the generally are set<16:13:55.436> up<16:13:55.560> on<16:13:56.096> the<16:13:56.220> server<16:13:56.520> side<16:13:56.700> and<16:13:56.936> the<16:13:57.116> client 16:13:57.350 --> 16:13:57.360 align:start position:0% set up on the server side and the client 16:13:57.360 --> 16:13:59.030 align:start position:0% set up on the server side and the client needs<16:13:57.660> to<16:13:57.720> be<16:13:57.840> configured<16:13:58.320> to<16:13:58.560> set<16:13:58.680> up<16:13:58.860> through 16:13:59.030 --> 16:13:59.040 align:start position:0% needs to be configured to set up through 16:13:59.040 --> 16:14:03.406 align:start position:0% needs to be configured to set up through the<16:13:59.756> first<16:13:59.956> is<16:14:00.956> PP<16:14:01.740> TP<16:14:02.580> which<16:14:03.116> we're<16:14:03.296> going<16:14:03.416> to 16:14:03.406 --> 16:14:03.416 align:start position:0% the first is PP TP which we're going to 16:14:03.416 --> 16:14:05.030 align:start position:0% the first is PP TP which we're going to talk<16:14:03.540> about<16:14:03.660> in<16:14:03.840> a<16:14:04.020> minute<16:14:04.140> and<16:14:04.436> this<16:14:04.616> stands 16:14:05.030 --> 16:14:05.040 align:start position:0% talk about in a minute and this stands 16:14:05.040 --> 16:14:06.230 align:start position:0% talk about in a minute and this stands for 16:14:06.230 --> 16:14:06.240 align:start position:0% for 16:14:06.240 --> 16:14:07.730 align:start position:0% for point 16:14:07.730 --> 16:14:07.740 align:start position:0% point 16:14:07.740 --> 16:14:10.370 align:start position:0% point two<16:14:08.220> point 16:14:10.370 --> 16:14:10.380 align:start position:0% two point 16:14:10.380 --> 16:14:13.190 align:start position:0% two point tunneling 16:14:13.190 --> 16:14:13.200 align:start position:0% 16:14:13.200 --> 16:14:15.286 align:start position:0% protocol 16:14:15.286 --> 16:14:15.296 align:start position:0% protocol 16:14:15.296 --> 16:14:17.946 align:start position:0% protocol the<16:14:16.020> other<16:14:16.220> is 16:14:17.946 --> 16:14:17.956 align:start position:0% the other is 16:14:17.956 --> 16:14:22.906 align:start position:0% the other is l2tp<16:14:18.956> which<16:14:19.740> stands<16:14:20.096> for<16:14:20.340> Layer<16:14:21.116> Two 16:14:22.906 --> 16:14:22.916 align:start position:0% l2tp which stands for Layer Two 16:14:22.916 --> 16:14:24.890 align:start position:0% l2tp which stands for Layer Two tunneling 16:14:24.890 --> 16:14:24.900 align:start position:0% tunneling 16:14:24.900 --> 16:14:26.210 align:start position:0% tunneling protocol 16:14:26.210 --> 16:14:26.220 align:start position:0% protocol 16:14:26.220 --> 16:14:28.190 align:start position:0% protocol and<16:14:26.640> if<16:14:26.756> you<16:14:26.880> remember<16:14:27.060> talking<16:14:27.480> about<16:14:27.660> the<16:14:27.840> OS 16:14:28.190 --> 16:14:28.200 align:start position:0% and if you remember talking about the OS 16:14:28.200 --> 16:14:31.010 align:start position:0% and if you remember talking about the OS and<16:14:28.380> I<16:14:28.680> and<16:14:28.916> the<16:14:29.096> tcpip<16:14:29.756> models<16:14:30.360> that's<16:14:30.776> what 16:14:31.010 --> 16:14:31.020 align:start position:0% and I and the tcpip models that's what 16:14:31.020 --> 16:14:33.050 align:start position:0% and I and the tcpip models that's what that<16:14:31.200> layer<16:14:31.436> 2<16:14:31.560> refers<16:14:31.980> to 16:14:33.050 --> 16:14:33.060 align:start position:0% that layer 2 refers to 16:14:33.060 --> 16:14:34.850 align:start position:0% that layer 2 refers to so<16:14:33.540> let's<16:14:33.776> talk<16:14:33.956> a<16:14:34.080> little<16:14:34.200> bit<16:14:34.320> more<16:14:34.560> about 16:14:34.850 --> 16:14:34.860 align:start position:0% so let's talk a little bit more about 16:14:34.860 --> 16:14:37.906 align:start position:0% so let's talk a little bit more about these<16:14:35.340> protocols<16:14:36.000> the<16:14:36.660> VPN<16:14:37.020> Protocols<16:14:37.616> are 16:14:37.906 --> 16:14:37.916 align:start position:0% these protocols the VPN Protocols are 16:14:37.916 --> 16:14:39.710 align:start position:0% these protocols the VPN Protocols are really<16:14:38.160> important<16:14:38.700> to<16:14:38.880> the<16:14:39.060> security<16:14:39.240> and 16:14:39.710 --> 16:14:39.720 align:start position:0% really important to the security and 16:14:39.720 --> 16:14:42.606 align:start position:0% really important to the security and efficiency<16:14:40.200> of<16:14:40.436> VPN<16:14:40.980> so<16:14:41.456> the<16:14:41.756> protocols 16:14:42.606 --> 16:14:42.616 align:start position:0% efficiency of VPN so the protocols 16:14:42.616 --> 16:14:46.786 align:start position:0% efficiency of VPN so the protocols manage<16:14:43.616> establish<16:14:44.480> and<16:14:45.480> secure<16:14:46.140> the<16:14:46.436> data 16:14:46.786 --> 16:14:46.796 align:start position:0% manage establish and secure the data 16:14:46.796 --> 16:14:48.710 align:start position:0% manage establish and secure the data that's<16:14:46.980> going<16:14:47.276> on<16:14:47.520> through<16:14:47.936> that<16:14:48.180> VPN 16:14:48.710 --> 16:14:48.720 align:start position:0% that's going on through that VPN 16:14:48.720 --> 16:14:53.570 align:start position:0% that's going on through that VPN connection<16:14:49.040> so<16:14:50.040> pptp<16:14:51.000> and<16:14:51.416> l2tp<16:14:52.320> are<16:14:53.160> the<16:14:53.340> two 16:14:53.570 --> 16:14:53.580 align:start position:0% connection so pptp and l2tp are the two 16:14:53.580 --> 16:14:56.266 align:start position:0% connection so pptp and l2tp are the two most<16:14:53.936> common<16:14:54.680> protocols<16:14:55.680> that<16:14:55.860> are<16:14:55.980> out<16:14:56.160> there 16:14:56.266 --> 16:14:56.276 align:start position:0% most common protocols that are out there 16:14:56.276 --> 16:14:58.010 align:start position:0% most common protocols that are out there they<16:14:56.820> function<16:14:57.116> pretty<16:14:57.416> differently<16:14:57.776> but 16:14:58.010 --> 16:14:58.020 align:start position:0% they function pretty differently but 16:14:58.020 --> 16:15:00.470 align:start position:0% they function pretty differently but their<16:14:58.256> jobs<16:14:58.380> are<16:14:58.680> fairly<16:14:58.980> similar<16:14:59.756> they 16:15:00.470 --> 16:15:00.480 align:start position:0% their jobs are fairly similar they 16:15:00.480 --> 16:15:03.350 align:start position:0% their jobs are fairly similar they enable 16:15:03.350 --> 16:15:03.360 align:start position:0% 16:15:03.360 --> 16:15:06.106 align:start position:0% encryption 16:15:06.106 --> 16:15:06.116 align:start position:0% encryption 16:15:06.116 --> 16:15:08.990 align:start position:0% encryption which<16:15:06.660> means<16:15:06.900> the<16:15:07.140> data<16:15:07.436> isn't<16:15:07.796> sent<16:15:08.096> in<16:15:08.700> its 16:15:08.990 --> 16:15:09.000 align:start position:0% which means the data isn't sent in its 16:15:09.000 --> 16:15:11.210 align:start position:0% which means the data isn't sent in its sort<16:15:09.116> of<16:15:09.180> plain<16:15:09.540> text<16:15:09.776> format<16:15:10.320> it's<16:15:10.616> sent<16:15:10.860> in<16:15:11.096> a 16:15:11.210 --> 16:15:11.220 align:start position:0% sort of plain text format it's sent in a 16:15:11.220 --> 16:15:12.830 align:start position:0% sort of plain text format it's sent in a way<16:15:11.276> that<16:15:11.520> if<16:15:11.700> you<16:15:11.880> were<16:15:11.936> just<16:15:12.116> to<16:15:12.296> see<16:15:12.480> it<16:15:12.660> it 16:15:12.830 --> 16:15:12.840 align:start position:0% way that if you were just to see it it 16:15:12.840 --> 16:15:14.630 align:start position:0% way that if you were just to see it it would<16:15:13.020> look<16:15:13.200> like<16:15:13.320> it's<16:15:13.560> all<16:15:13.740> gobbley 16:15:14.630 --> 16:15:14.640 align:start position:0% would look like it's all gobbley 16:15:14.640 --> 16:15:16.730 align:start position:0% would look like it's all gobbley and<16:15:15.180> so<16:15:15.296> what<16:15:15.540> happens<16:15:15.720> it's<16:15:16.080> set<16:15:16.256> on<16:15:16.380> one<16:15:16.560> end 16:15:16.730 --> 16:15:16.740 align:start position:0% and so what happens it's set on one end 16:15:16.740 --> 16:15:18.350 align:start position:0% and so what happens it's set on one end in<16:15:16.916> a<16:15:16.980> code<16:15:17.160> and<16:15:17.340> then<16:15:17.456> received<16:15:17.880> and<16:15:18.000> decode 16:15:18.350 --> 16:15:18.360 align:start position:0% in a code and then received and decode 16:15:18.360 --> 16:15:20.150 align:start position:0% in a code and then received and decode on<16:15:18.540> the<16:15:18.660> other<16:15:18.776> end<16:15:18.900> and<16:15:19.436> it<16:15:19.616> also<16:15:19.796> provides 16:15:20.150 --> 16:15:20.160 align:start position:0% on the other end and it also provides 16:15:20.160 --> 16:15:22.670 align:start position:0% on the other end and it also provides authentication<16:15:20.880> so<16:15:21.660> only<16:15:21.900> those<16:15:22.320> who<16:15:22.560> are 16:15:22.670 --> 16:15:22.680 align:start position:0% authentication so only those who are 16:15:22.680 --> 16:15:25.370 align:start position:0% authentication so only those who are allowed<16:15:23.040> on<16:15:23.160> the<16:15:23.340> network<16:15:23.456> actually<16:15:24.060> get<16:15:24.480> on 16:15:25.370 --> 16:15:25.380 align:start position:0% allowed on the network actually get on 16:15:25.380 --> 16:15:28.606 align:start position:0% allowed on the network actually get on the<16:15:25.796> authentication<16:15:26.660> it<16:15:27.660> also<16:15:27.956> establishes 16:15:28.606 --> 16:15:28.616 align:start position:0% the authentication it also establishes 16:15:28.616 --> 16:15:29.990 align:start position:0% the authentication it also establishes the<16:15:28.860> identities<16:15:29.220> of<16:15:29.456> the<16:15:29.580> people<16:15:29.700> in<16:15:29.880> the 16:15:29.990 --> 16:15:30.000 align:start position:0% the identities of the people in the 16:15:30.000 --> 16:15:32.150 align:start position:0% the identities of the people in the network<16:15:30.116> so<16:15:30.540> we<16:15:30.720> can<16:15:30.840> audit<16:15:31.200> them<16:15:31.380> it's<16:15:31.860> a<16:15:32.040> way 16:15:32.150 --> 16:15:32.160 align:start position:0% network so we can audit them it's a way 16:15:32.160 --> 16:15:34.370 align:start position:0% network so we can audit them it's a way for<16:15:32.340> the<16:15:32.520> clients<16:15:33.116> and<16:15:33.540> the<16:15:33.720> servers<16:15:34.020> to<16:15:34.200> be<16:15:34.320> on 16:15:34.370 --> 16:15:34.380 align:start position:0% for the clients and the servers to be on 16:15:34.380 --> 16:15:36.170 align:start position:0% for the clients and the servers to be on the<16:15:34.500> same<16:15:34.616> page<16:15:34.796> about<16:15:35.096> who<16:15:35.520> is<16:15:35.820> on<16:15:36.060> the 16:15:36.170 --> 16:15:36.180 align:start position:0% the same page about who is on the 16:15:36.180 --> 16:15:37.010 align:start position:0% the same page about who is on the network 16:15:37.010 --> 16:15:37.020 align:start position:0% network 16:15:37.020 --> 16:15:39.586 align:start position:0% network and<16:15:37.560> like<16:15:37.796> I<16:15:37.980> mentioned<16:15:38.276> encryption<16:15:38.936> is 16:15:39.586 --> 16:15:39.596 align:start position:0% and like I mentioned encryption is 16:15:39.596 --> 16:15:41.870 align:start position:0% and like I mentioned encryption is really<16:15:39.776> for<16:15:40.080> the<16:15:40.256> data<16:15:40.616> protection<16:15:40.980> so 16:15:41.870 --> 16:15:41.880 align:start position:0% really for the data protection so 16:15:41.880 --> 16:15:44.390 align:start position:0% really for the data protection so because<16:15:42.360> we're<16:15:43.200> going<16:15:43.500> through<16:15:43.916> the<16:15:44.276> internet 16:15:44.390 --> 16:15:44.400 align:start position:0% because we're going through the internet 16:15:44.400 --> 16:15:46.786 align:start position:0% because we're going through the internet which<16:15:44.820> is<16:15:44.936> public<16:15:45.240> this<16:15:46.020> is<16:15:46.140> really<16:15:46.320> at<16:15:46.500> risk 16:15:46.786 --> 16:15:46.796 align:start position:0% which is public this is really at risk 16:15:46.796 --> 16:15:48.586 align:start position:0% which is public this is really at risk for<16:15:46.980> attackers<16:15:47.456> and<16:15:47.700> so<16:15:47.880> the<16:15:48.180> encryption 16:15:48.586 --> 16:15:48.596 align:start position:0% for attackers and so the encryption 16:15:48.596 --> 16:15:50.630 align:start position:0% for attackers and so the encryption protects<16:15:49.140> that<16:15:49.380> data<16:15:49.740> that's<16:15:50.160> traveling 16:15:50.630 --> 16:15:50.640 align:start position:0% protects that data that's traveling 16:15:50.640 --> 16:15:51.946 align:start position:0% protects that data that's traveling through<16:15:50.820> the<16:15:51.000> network<16:15:51.116> and<16:15:51.416> prevents<16:15:51.776> these 16:15:51.946 --> 16:15:51.956 align:start position:0% through the network and prevents these 16:15:51.956 --> 16:15:54.350 align:start position:0% through the network and prevents these issues<16:15:52.200> from<16:15:52.380> happening<16:15:53.220> generally<16:15:53.820> speaking 16:15:54.350 --> 16:15:54.360 align:start position:0% issues from happening generally speaking 16:15:54.360 --> 16:15:58.190 align:start position:0% issues from happening generally speaking we're<16:15:54.840> going<16:15:55.020> to<16:15:55.140> prefer<16:15:55.520> l2tp<16:15:56.520> over<16:15:57.240> pptp 16:15:58.190 --> 16:15:58.200 align:start position:0% we're going to prefer l2tp over pptp 16:15:58.200 --> 16:16:00.286 align:start position:0% we're going to prefer l2tp over pptp just<16:15:59.096> because<16:15:59.276> it's<16:15:59.640> a<16:15:59.756> more<16:15:59.936> advanced 16:16:00.286 --> 16:16:00.296 align:start position:0% just because it's a more advanced 16:16:00.296 --> 16:16:01.970 align:start position:0% just because it's a more advanced protocol<16:16:00.660> and<16:16:01.020> uses<16:16:01.256> a<16:16:01.380> different<16:16:01.500> form<16:16:01.740> of 16:16:01.970 --> 16:16:01.980 align:start position:0% protocol and uses a different form of 16:16:01.980 --> 16:16:02.990 align:start position:0% protocol and uses a different form of encryption 16:16:02.990 --> 16:16:03.000 align:start position:0% encryption 16:16:03.000 --> 16:16:05.266 align:start position:0% encryption I<16:16:03.776> think<16:16:04.020> in<16:16:04.436> fact 16:16:05.266 --> 16:16:05.276 align:start position:0% I think in fact 16:16:05.276 --> 16:16:08.870 align:start position:0% I think in fact Windows<16:16:06.000> 7<16:16:06.116> and<16:16:06.416> Vista<16:16:06.900> only<16:16:07.560> allows<16:16:07.980> lttdp 16:16:08.870 --> 16:16:08.880 align:start position:0% Windows 7 and Vista only allows lttdp 16:16:08.880 --> 16:16:11.086 align:start position:0% Windows 7 and Vista only allows lttdp now<16:16:09.060> it<16:16:09.240> doesn't<16:16:09.360> even<16:16:09.540> allow<16:16:09.840> pptp<16:16:10.680> as<16:16:10.916> we 16:16:11.086 --> 16:16:11.096 align:start position:0% now it doesn't even allow pptp as we 16:16:11.096 --> 16:16:14.266 align:start position:0% now it doesn't even allow pptp as we just<16:16:11.276> saw<16:16:11.400> when<16:16:11.640> we<16:16:11.756> looked<16:16:12.000> into<16:16:12.060> windows 16:16:14.266 --> 16:16:14.276 align:start position:0% just saw when we looked into windows 16:16:14.276 --> 16:16:16.786 align:start position:0% just saw when we looked into windows all<16:16:14.820> right<16:16:15.000> so<16:16:15.416> just<16:16:15.840> to<16:16:16.080> recap<16:16:16.380> what<16:16:16.560> we<16:16:16.680> just 16:16:16.786 --> 16:16:16.796 align:start position:0% all right so just to recap what we just 16:16:16.796 --> 16:16:18.766 align:start position:0% all right so just to recap what we just talked<16:16:17.040> about<16:16:17.096> first<16:16:17.520> we<16:16:17.820> mentioned<16:16:18.240> virtual 16:16:18.766 --> 16:16:18.776 align:start position:0% talked about first we mentioned virtual 16:16:18.776 --> 16:16:20.390 align:start position:0% talked about first we mentioned virtual private<16:16:19.200> networks<16:16:19.560> which<16:16:19.740> you'll<16:16:20.040> never<16:16:20.220> see 16:16:20.390 --> 16:16:20.400 align:start position:0% private networks which you'll never see 16:16:20.400 --> 16:16:21.830 align:start position:0% private networks which you'll never see referred<16:16:20.756> to<16:16:20.820> as<16:16:20.936> virtual<16:16:21.180> private<16:16:21.480> networks 16:16:21.830 --> 16:16:21.840 align:start position:0% referred to as virtual private networks 16:16:21.840 --> 16:16:25.370 align:start position:0% referred to as virtual private networks you'll<16:16:22.256> see<16:16:22.436> them<16:16:22.560> referred<16:16:22.860> to<16:16:22.916> as<16:16:23.660> vpns<16:16:24.660> and 16:16:25.370 --> 16:16:25.380 align:start position:0% you'll see them referred to as vpns and 16:16:25.380 --> 16:16:29.266 align:start position:0% you'll see them referred to as vpns and those<16:16:25.740> basically<16:16:26.276> create<16:16:26.640> a<16:16:26.880> tunnel 16:16:29.266 --> 16:16:29.276 align:start position:0% those basically create a tunnel 16:16:29.276 --> 16:16:33.230 align:start position:0% those basically create a tunnel through<16:16:29.900> generally<16:16:31.160> the<16:16:32.160> internet<16:16:32.340> sometimes 16:16:33.230 --> 16:16:33.240 align:start position:0% through generally the internet sometimes 16:16:33.240 --> 16:16:35.746 align:start position:0% through generally the internet sometimes the<16:16:33.480> Intranet 16:16:35.746 --> 16:16:35.756 align:start position:0% the Intranet 16:16:35.756 --> 16:16:38.390 align:start position:0% the Intranet to<16:16:36.416> connect 16:16:38.390 --> 16:16:38.400 align:start position:0% to connect 16:16:38.400 --> 16:16:41.446 align:start position:0% to connect lands<16:16:39.240> together<16:16:39.616> and<16:16:40.616> in<16:16:40.796> effect<16:16:41.040> then 16:16:41.446 --> 16:16:41.456 align:start position:0% lands together and in effect then 16:16:41.456 --> 16:16:44.630 align:start position:0% lands together and in effect then creating<16:16:42.200> one<16:16:43.200> large<16:16:43.500> Wan<16:16:44.096> now<16:16:44.276> this<16:16:44.400> can<16:16:44.520> be 16:16:44.630 --> 16:16:44.640 align:start position:0% creating one large Wan now this can be 16:16:44.640 --> 16:16:47.390 align:start position:0% creating one large Wan now this can be done<16:16:44.820> between<16:16:45.180> office<16:16:45.660> and<16:16:45.956> office<16:16:46.256> or<16:16:47.040> say<16:16:47.220> a 16:16:47.390 --> 16:16:47.400 align:start position:0% done between office and office or say a 16:16:47.400 --> 16:16:49.906 align:start position:0% done between office and office or say a home<16:16:47.640> user<16:16:48.060> in<16:16:48.180> an<16:16:48.296> office<16:16:48.480> and<16:16:49.436> either<16:16:49.680> way 16:16:49.906 --> 16:16:49.916 align:start position:0% home user in an office and either way 16:16:49.916 --> 16:16:52.850 align:start position:0% home user in an office and either way you<16:16:50.276> have<16:16:50.400> a<16:16:50.520> VPN<16:16:51.000> client<16:16:51.720> which<16:16:52.320> would<16:16:52.500> be<16:16:52.616> the 16:16:52.850 --> 16:16:52.860 align:start position:0% you have a VPN client which would be the 16:16:52.860 --> 16:16:55.670 align:start position:0% you have a VPN client which would be the one<16:16:53.040> connecting<16:16:53.640> to<16:16:54.116> the<16:16:54.596> server<16:16:54.956> and 16:16:55.670 --> 16:16:55.680 align:start position:0% one connecting to the server and 16:16:55.680 --> 16:16:59.870 align:start position:0% one connecting to the server and remember<16:16:55.860> we<16:16:56.400> have<16:16:56.640> either<16:16:57.180> software 16:16:59.870 --> 16:16:59.880 align:start position:0% remember we have either software 16:16:59.880 --> 16:17:02.690 align:start position:0% remember we have either software or<16:17:00.720> Hardware<16:17:01.080> we<16:17:01.796> looked<16:17:02.160> at<16:17:02.160> the<16:17:02.340> software 16:17:02.690 --> 16:17:02.700 align:start position:0% or Hardware we looked at the software 16:17:02.700 --> 16:17:05.086 align:start position:0% or Hardware we looked at the software that<16:17:02.936> was<16:17:03.116> built<16:17:03.480> into<16:17:03.540> windows<16:17:04.380> we<16:17:04.740> also<16:17:04.980> have 16:17:05.086 --> 16:17:05.096 align:start position:0% that was built into windows we also have 16:17:05.096 --> 16:17:06.586 align:start position:0% that was built into windows we also have Hardware<16:17:05.276> the<16:17:05.756> generally<16:17:06.060> the<16:17:06.360> thing<16:17:06.480> that 16:17:06.586 --> 16:17:06.596 align:start position:0% Hardware the generally the thing that 16:17:06.596 --> 16:17:07.606 align:start position:0% Hardware the generally the thing that you'll<16:17:06.776> see<16:17:06.900> with<16:17:07.080> there<16:17:07.256> is<16:17:07.500> something 16:17:07.606 --> 16:17:07.616 align:start position:0% you'll see with there is something 16:17:07.616 --> 16:17:10.426 align:start position:0% you'll see with there is something called<16:17:07.860> a<16:17:08.096> VPN<16:17:08.580> concentrator<16:17:09.360> it<16:17:10.080> could<16:17:10.200> also 16:17:10.426 --> 16:17:10.436 align:start position:0% called a VPN concentrator it could also 16:17:10.436 --> 16:17:11.926 align:start position:0% called a VPN concentrator it could also be<16:17:10.560> for<16:17:10.796> instance<16:17:10.980> built<16:17:11.340> into<16:17:11.400> your<16:17:11.580> Soho 16:17:11.926 --> 16:17:11.936 align:start position:0% be for instance built into your Soho 16:17:11.936 --> 16:17:14.746 align:start position:0% be for instance built into your Soho router<16:17:12.416> or<16:17:13.140> be<16:17:13.380> built<16:17:13.680> into<16:17:13.740> a<16:17:14.096> Cisco<16:17:14.400> router 16:17:14.746 --> 16:17:14.756 align:start position:0% router or be built into a Cisco router 16:17:14.756 --> 16:17:16.730 align:start position:0% router or be built into a Cisco router of<16:17:14.820> some<16:17:15.000> sort<16:17:15.180> as<16:17:15.360> well<16:17:15.540> we<16:17:16.140> also<16:17:16.380> discussed 16:17:16.730 --> 16:17:16.740 align:start position:0% of some sort as well we also discussed 16:17:16.740 --> 16:17:19.970 align:start position:0% of some sort as well we also discussed the<16:17:16.980> two<16:17:17.276> VPN<16:17:17.880> protocols<16:17:18.720> remember<16:17:19.380> these 16:17:19.970 --> 16:17:19.980 align:start position:0% the two VPN protocols remember these 16:17:19.980 --> 16:17:21.890 align:start position:0% the two VPN protocols remember these were<16:17:20.096> the<16:17:20.340> point-to-point<16:17:21.180> tunneling 16:17:21.890 --> 16:17:21.900 align:start position:0% were the point-to-point tunneling 16:17:21.900 --> 16:17:23.990 align:start position:0% were the point-to-point tunneling protocol<16:17:22.200> and<16:17:22.860> the<16:17:23.040> layer<16:17:23.276> 2<16:17:23.456> tunneling 16:17:23.990 --> 16:17:24.000 align:start position:0% protocol and the layer 2 tunneling 16:17:24.000 --> 16:17:26.690 align:start position:0% protocol and the layer 2 tunneling protocol<16:17:24.360> notice<16:17:25.200> that<16:17:25.380> these<16:17:25.680> both<16:17:25.916> you<16:17:26.520> know 16:17:26.690 --> 16:17:26.700 align:start position:0% protocol notice that these both you know 16:17:26.700 --> 16:17:29.330 align:start position:0% protocol notice that these both you know are<16:17:26.936> VPN<16:17:27.360> protocols<16:17:27.840> because<16:17:28.080> of<16:17:28.320> this<16:17:28.500> T<16:17:28.796> the 16:17:29.330 --> 16:17:29.340 align:start position:0% are VPN protocols because of this T the 16:17:29.340 --> 16:17:31.310 align:start position:0% are VPN protocols because of this T the tunneling<16:17:29.880> protocol<16:17:30.180> generally<16:17:30.956> speaking 16:17:31.310 --> 16:17:31.320 align:start position:0% tunneling protocol generally speaking 16:17:31.320 --> 16:17:33.710 align:start position:0% tunneling protocol generally speaking we're<16:17:31.436> going<16:17:31.560> to<16:17:31.616> see<16:17:31.740> l2tp<16:17:32.580> used<16:17:32.820> more<16:17:33.180> than 16:17:33.710 --> 16:17:33.720 align:start position:0% we're going to see l2tp used more than 16:17:33.720 --> 16:17:36.230 align:start position:0% we're going to see l2tp used more than pptp<16:17:34.616> and<16:17:35.276> what<16:17:35.520> these<16:17:35.880> really<16:17:36.000> are 16:17:36.230 --> 16:17:36.240 align:start position:0% pptp and what these really are 16:17:36.240 --> 16:17:38.086 align:start position:0% pptp and what these really are responsible<16:17:36.596> for<16:17:36.776> is<16:17:37.080> defining<16:17:37.560> how 16:17:38.086 --> 16:17:38.096 align:start position:0% responsible for is defining how 16:17:38.096 --> 16:17:41.870 align:start position:0% responsible for is defining how encryption<16:17:39.060> takes<16:17:39.416> place 16:17:41.870 --> 16:17:41.880 align:start position:0% 16:17:41.880 --> 16:17:44.690 align:start position:0% and<16:17:42.660> authentication<16:17:43.436> which<16:17:44.220> is<16:17:44.340> something 16:17:44.690 --> 16:17:44.700 align:start position:0% and authentication which is something 16:17:44.700 --> 16:17:47.746 align:start position:0% and authentication which is something that<16:17:45.360> works<16:17:45.720> in<16:17:45.956> conjunction<16:17:46.320> with<16:17:47.160> the<16:17:47.400> VPN 16:17:47.746 --> 16:17:47.756 align:start position:0% that works in conjunction with the VPN 16:17:47.756 --> 16:17:52.220 align:start position:0% that works in conjunction with the VPN server<16:17:48.180> to<16:17:48.480> accomplish 16:17:52.220 --> 16:17:52.230 align:start position:0% 16:17:52.230 --> 16:18:08.150 align:start position:0% [Music] 16:18:08.150 --> 16:18:08.160 align:start position:0% 16:18:08.160 --> 16:18:11.990 align:start position:0% welcome<16:18:08.700> to<16:18:08.880> module<16:18:09.360> 10<16:18:09.480> lesson<16:18:10.080> 4<16:18:10.380> gra<16:18:11.340> SSL 16:18:11.990 --> 16:18:12.000 align:start position:0% welcome to module 10 lesson 4 gra SSL 16:18:12.000 --> 16:18:16.606 align:start position:0% welcome to module 10 lesson 4 gra SSL VPN<16:18:12.720> and<16:18:12.956> VPN<16:18:13.560> concentrators 16:18:16.606 --> 16:18:16.616 align:start position:0% 16:18:16.616 --> 16:18:18.470 align:start position:0% we<16:18:17.160> look<16:18:17.400> at<16:18:17.640> them 16:18:18.470 --> 16:18:18.480 align:start position:0% we look at them 16:18:18.480 --> 16:18:21.946 align:start position:0% we look at them secure<16:18:19.256> sockets<16:18:19.680> for<16:18:19.980> VPN<16:18:20.936> also 16:18:21.946 --> 16:18:21.956 align:start position:0% secure sockets for VPN also 16:18:21.956 --> 16:18:24.170 align:start position:0% secure sockets for VPN also what<16:18:22.436> is<16:18:22.616> SSL 16:18:24.170 --> 16:18:24.180 align:start position:0% what is SSL 16:18:24.180 --> 16:18:27.586 align:start position:0% what is SSL VPN<16:18:24.900> concentrators<16:18:25.616> ipsec<16:18:26.520> this<16:18:27.116> is<16:18:27.240> just<16:18:27.416> an 16:18:27.586 --> 16:18:27.596 align:start position:0% VPN concentrators ipsec this is just an 16:18:27.596 --> 16:18:28.786 align:start position:0% VPN concentrators ipsec this is just an overview 16:18:28.786 --> 16:18:28.796 align:start position:0% overview 16:18:28.796 --> 16:18:32.870 align:start position:0% overview as<16:18:29.340> usual<16:18:29.520> there's<16:18:29.880> a<16:18:30.060> whole<16:18:30.320> entire<16:18:31.740> um<16:18:31.880> exams 16:18:32.870 --> 16:18:32.880 align:start position:0% as usual there's a whole entire um exams 16:18:32.880 --> 16:18:34.670 align:start position:0% as usual there's a whole entire um exams for<16:18:33.180> security<16:18:33.360> stuff<16:18:33.840> like<16:18:34.080> this<16:18:34.256> in<16:18:34.500> more 16:18:34.670 --> 16:18:34.680 align:start position:0% for security stuff like this in more 16:18:34.680 --> 16:18:37.190 align:start position:0% for security stuff like this in more detail<16:18:34.980> like<16:18:35.220> the<16:18:36.116> CompTIA<16:18:36.596> Security<16:18:36.776> Plus 16:18:37.190 --> 16:18:37.200 align:start position:0% detail like the CompTIA Security Plus 16:18:37.200 --> 16:18:41.030 align:start position:0% detail like the CompTIA Security Plus which<16:18:37.680> we<16:18:37.860> host<16:18:38.220> on<16:18:38.640> howturnetwork.com<16:18:40.040> and 16:18:41.030 --> 16:18:41.040 align:start position:0% which we host on howturnetwork.com and 16:18:41.040 --> 16:18:43.606 align:start position:0% which we host on howturnetwork.com and the<16:18:41.400> CCNA<16:18:42.000> security<16:18:42.240> also 16:18:43.606 --> 16:18:43.616 align:start position:0% the CCNA security also 16:18:43.616 --> 16:18:45.650 align:start position:0% the CCNA security also GRE<16:18:44.096> stands<16:18:44.756> for<16:18:44.820> generic<16:18:45.240> routing 16:18:45.650 --> 16:18:45.660 align:start position:0% GRE stands for generic routing 16:18:45.660 --> 16:18:46.970 align:start position:0% GRE stands for generic routing encapsulation<16:18:46.256> and<16:18:46.616> it<16:18:46.740> was<16:18:46.860> actually 16:18:46.970 --> 16:18:46.980 align:start position:0% encapsulation and it was actually 16:18:46.980 --> 16:18:49.310 align:start position:0% encapsulation and it was actually developed<16:18:47.456> by<16:18:47.580> Cisco<16:18:48.060> Systems<16:18:48.596> as<16:18:48.956> a 16:18:49.310 --> 16:18:49.320 align:start position:0% developed by Cisco Systems as a 16:18:49.320 --> 16:18:51.890 align:start position:0% developed by Cisco Systems as a tunneling<16:18:50.096> protocol<16:18:50.580> and<16:18:51.360> I<16:18:51.540> totally<16:18:51.776> in 16:18:51.890 --> 16:18:51.900 align:start position:0% tunneling protocol and I totally in 16:18:51.900 --> 16:18:54.946 align:start position:0% tunneling protocol and I totally in protocol<16:18:52.580> tunnels<16:18:53.580> something<16:18:54.360> else<16:18:54.660> another 16:18:54.946 --> 16:18:54.956 align:start position:0% protocol tunnels something else another 16:18:54.956 --> 16:18:59.510 align:start position:0% protocol tunnels something else another Prodigy<16:18:55.680> call<16:18:56.116> within<16:18:57.116> a<16:18:57.360> protocol 16:18:59.510 --> 16:18:59.520 align:start position:0% Prodigy call within a protocol 16:18:59.520 --> 16:19:02.150 align:start position:0% Prodigy call within a protocol so<16:19:00.416> it<16:19:00.596> allows<16:19:00.956> Network<16:19:01.200> users<16:19:01.616> to<16:19:01.796> access<16:19:01.860> the 16:19:02.150 --> 16:19:02.160 align:start position:0% so it allows Network users to access the 16:19:02.160 --> 16:19:03.710 align:start position:0% so it allows Network users to access the network<16:19:02.340> service<16:19:02.640> it's<16:19:02.936> not<16:19:03.116> supported<16:19:03.540> by 16:19:03.710 --> 16:19:03.720 align:start position:0% network service it's not supported by 16:19:03.720 --> 16:19:05.330 align:start position:0% network service it's not supported by the<16:19:03.840> underlying<16:19:04.320> Network<16:19:04.436> so<16:19:05.040> you<16:19:05.276> can 16:19:05.330 --> 16:19:05.340 align:start position:0% the underlying Network so you can 16:19:05.340 --> 16:19:06.710 align:start position:0% the underlying Network so you can actually<16:19:05.520> tunnel 16:19:06.710 --> 16:19:06.720 align:start position:0% actually tunnel 16:19:06.720 --> 16:19:08.150 align:start position:0% actually tunnel um<16:19:06.776> lots<16:19:07.200> of<16:19:07.256> different<16:19:07.380> things<16:19:07.616> you<16:19:07.860> can<16:19:07.980> sort 16:19:08.150 --> 16:19:08.160 align:start position:0% um lots of different things you can sort 16:19:08.160 --> 16:19:14.330 align:start position:0% um lots of different things you can sort of<16:19:08.276> IP<16:19:08.700> version<16:19:09.596> 4<16:19:09.900> inside<16:19:10.700> IPv6<16:19:11.776> if<16:19:12.776> the<16:19:13.320> um 16:19:14.330 --> 16:19:14.340 align:start position:0% of IP version 4 inside IPv6 if the um 16:19:14.340 --> 16:19:17.990 align:start position:0% of IP version 4 inside IPv6 if the um hop<16:19:14.820> by<16:19:15.360> hot<16:19:15.596> pair<16:19:15.956> devices<16:19:16.320> don't<16:19:16.680> support<16:19:16.980> it 16:19:17.990 --> 16:19:18.000 align:start position:0% hop by hot pair devices don't support it 16:19:18.000 --> 16:19:20.926 align:start position:0% hop by hot pair devices don't support it here<16:19:18.660> is<16:19:18.956> an<16:19:19.200> image<16:19:19.436> of<16:19:19.560> a<16:19:19.740> GRE<16:19:19.860> tunnel<16:19:20.640> going 16:19:20.926 --> 16:19:20.936 align:start position:0% here is an image of a GRE tunnel going 16:19:20.936 --> 16:19:22.786 align:start position:0% here is an image of a GRE tunnel going across<16:19:21.596> an<16:19:21.776> internet 16:19:22.786 --> 16:19:22.796 align:start position:0% across an internet 16:19:22.796 --> 16:19:24.766 align:start position:0% across an internet Source<16:19:23.580> interface<16:19:24.060> or<16:19:24.296> IP<16:19:24.596> address 16:19:24.766 --> 16:19:24.776 align:start position:0% Source interface or IP address 16:19:24.776 --> 16:19:27.650 align:start position:0% Source interface or IP address destination<16:19:25.560> IP<16:19:25.980> address<16:19:26.160> of<16:19:26.456> the<16:19:26.640> tunnel<16:19:27.060> an 16:19:27.650 --> 16:19:27.660 align:start position:0% destination IP address of the tunnel an 16:19:27.660 --> 16:19:29.446 align:start position:0% destination IP address of the tunnel an IP<16:19:27.956> address<16:19:28.080> of<16:19:28.380> the<16:19:28.560> tunnel<16:19:28.860> that's<16:19:29.160> part<16:19:29.340> of 16:19:29.446 --> 16:19:29.456 align:start position:0% IP address of the tunnel that's part of 16:19:29.456 --> 16:19:30.946 align:start position:0% IP address of the tunnel that's part of the<16:19:29.580> configuration<16:19:30.116> you<16:19:30.480> don't<16:19:30.540> really<16:19:30.720> need 16:19:30.946 --> 16:19:30.956 align:start position:0% the configuration you don't really need 16:19:30.956 --> 16:19:32.446 align:start position:0% the configuration you don't really need to<16:19:31.080> worry<16:19:31.256> about<16:19:31.560> that 16:19:32.446 --> 16:19:32.456 align:start position:0% to worry about that 16:19:32.456 --> 16:19:34.490 align:start position:0% to worry about that but<16:19:33.000> the<16:19:33.240> traffic<16:19:33.596> will<16:19:33.900> pass<16:19:34.080> through<16:19:34.320> the 16:19:34.490 --> 16:19:34.500 align:start position:0% but the traffic will pass through the 16:19:34.500 --> 16:19:36.170 align:start position:0% but the traffic will pass through the GRE<16:19:34.680> to<16:19:35.220> Norm 16:19:36.170 --> 16:19:36.180 align:start position:0% GRE to Norm 16:19:36.180 --> 16:19:38.210 align:start position:0% GRE to Norm and<16:19:36.720> the<16:19:36.840> device<16:19:37.080> is<16:19:37.380> actually<16:19:37.560> sending<16:19:38.040> the 16:19:38.210 --> 16:19:38.220 align:start position:0% and the device is actually sending the 16:19:38.220 --> 16:19:41.266 align:start position:0% and the device is actually sending the traffic<16:19:38.456> will<16:19:39.296> only<16:19:39.540> examine<16:19:40.080> the<16:19:40.320> header<16:19:40.860> of 16:19:41.266 --> 16:19:41.276 align:start position:0% traffic will only examine the header of 16:19:41.276 --> 16:19:45.350 align:start position:0% traffic will only examine the header of the<16:19:41.520> GRE<16:19:42.020> packet<16:19:43.020> which<16:19:43.436> is<16:19:43.860> um<16:19:43.860> wrapping<16:19:44.520> the 16:19:45.350 --> 16:19:45.360 align:start position:0% the GRE packet which is um wrapping the 16:19:45.360 --> 16:19:49.070 align:start position:0% the GRE packet which is um wrapping the uh<16:19:45.596> the<16:19:46.080> traditional<16:19:46.500> IP<16:19:46.916> traffic 16:19:49.070 --> 16:19:49.080 align:start position:0% uh the traditional IP traffic 16:19:49.080 --> 16:19:51.470 align:start position:0% uh the traditional IP traffic so<16:19:49.740> we<16:19:50.160> already<16:19:50.400> know<16:19:50.640> we<16:19:50.820> can<16:19:50.880> run<16:19:51.060> a<16:19:51.180> protocol 16:19:51.470 --> 16:19:51.480 align:start position:0% so we already know we can run a protocol 16:19:51.480 --> 16:19:53.266 align:start position:0% so we already know we can run a protocol every<16:19:51.840> Network<16:19:52.140> you<16:19:52.616> can<16:19:52.740> actually<16:19:52.916> run 16:19:53.266 --> 16:19:53.276 align:start position:0% every Network you can actually run 16:19:53.276 --> 16:19:55.370 align:start position:0% every Network you can actually run non-routable<16:19:54.116> addresses<16:19:54.596> as<16:19:54.776> well<16:19:54.956> so<16:19:55.140> inside 16:19:55.370 --> 16:19:55.380 align:start position:0% non-routable addresses as well so inside 16:19:55.380 --> 16:19:57.890 align:start position:0% non-routable addresses as well so inside that<16:19:55.680> tunnel<16:19:56.096> you<16:19:56.700> could<16:19:56.820> have<16:19:56.936> a<16:19:57.116> 192<16:19:57.660> address 16:19:57.890 --> 16:19:57.900 align:start position:0% that tunnel you could have a 192 address 16:19:57.900 --> 16:20:00.230 align:start position:0% that tunnel you could have a 192 address and<16:19:58.740> as<16:19:58.860> long<16:19:58.980> as<16:19:59.040> the<16:19:59.220> tunnel<16:19:59.580> is<16:19:59.700> going<16:19:59.880> via 16:20:00.230 --> 16:20:00.240 align:start position:0% and as long as the tunnel is going via 16:20:00.240 --> 16:20:04.010 align:start position:0% and as long as the tunnel is going via routable<16:20:00.660> IP<16:20:01.020> addresses<16:20:01.500> you'll<16:20:02.276> be<16:20:02.456> fine 16:20:04.010 --> 16:20:04.020 align:start position:0% routable IP addresses you'll be fine 16:20:04.020 --> 16:20:06.286 align:start position:0% routable IP addresses you'll be fine a<16:20:04.500> gra<16:20:05.040> creates<16:20:05.276> a<16:20:05.456> virtual<16:20:05.756> point-to-point 16:20:06.286 --> 16:20:06.296 align:start position:0% a gra creates a virtual point-to-point 16:20:06.296 --> 16:20:08.030 align:start position:0% a gra creates a virtual point-to-point link<16:20:06.540> and<16:20:06.776> encapsulates<16:20:07.320> a<16:20:07.560> variety<16:20:07.796> of 16:20:08.030 --> 16:20:08.040 align:start position:0% link and encapsulates a variety of 16:20:08.040 --> 16:20:10.670 align:start position:0% link and encapsulates a variety of network<16:20:08.340> protocols 16:20:10.670 --> 16:20:10.680 align:start position:0% network protocols 16:20:10.680 --> 16:20:12.406 align:start position:0% network protocols uh 16:20:12.406 --> 16:20:12.416 align:start position:0% uh 16:20:12.416 --> 16:20:14.150 align:start position:0% uh yeah<16:20:12.776> I've<16:20:12.900> already<16:20:13.020> mentioned<16:20:13.380> the<16:20:13.500> private 16:20:14.150 --> 16:20:14.160 align:start position:0% yeah I've already mentioned the private 16:20:14.160 --> 16:20:16.190 align:start position:0% yeah I've already mentioned the private IP<16:20:14.400> addresses<16:20:14.936> it's<16:20:15.416> used<16:20:15.596> in<16:20:15.776> conjunction 16:20:16.190 --> 16:20:16.200 align:start position:0% IP addresses it's used in conjunction 16:20:16.200 --> 16:20:19.426 align:start position:0% IP addresses it's used in conjunction often<16:20:16.796> with<16:20:17.096> pptp<16:20:18.000> point-to-point<16:20:18.956> tunneling 16:20:19.426 --> 16:20:19.436 align:start position:0% often with pptp point-to-point tunneling 16:20:19.436 --> 16:20:22.490 align:start position:0% often with pptp point-to-point tunneling protocol<16:20:19.740> and<16:20:20.520> ipsec<16:20:21.296> if<16:20:21.900> you<16:20:22.020> want<16:20:22.200> to<16:20:22.320> create 16:20:22.490 --> 16:20:22.500 align:start position:0% protocol and ipsec if you want to create 16:20:22.500 --> 16:20:25.130 align:start position:0% protocol and ipsec if you want to create a<16:20:22.740> VPN<16:20:23.276> and<16:20:24.000> there's<16:20:24.180> an<16:20:24.480> image<16:20:24.776> there<16:20:24.956> for 16:20:25.130 --> 16:20:25.140 align:start position:0% a VPN and there's an image there for 16:20:25.140 --> 16:20:27.530 align:start position:0% a VPN and there's an image there for with<16:20:25.380> the<16:20:25.500> GRE<16:20:25.616> tunnel<16:20:26.400> also<16:20:27.000> working<16:20:27.180> with<16:20:27.416> an 16:20:27.530 --> 16:20:27.540 align:start position:0% with the GRE tunnel also working with an 16:20:27.540 --> 16:20:32.746 align:start position:0% with the GRE tunnel also working with an IP<16:20:27.840> sector<16:20:28.256> null<16:20:28.616> from<16:20:29.160> networkstraining.com 16:20:32.746 --> 16:20:32.756 align:start position:0% 16:20:32.756 --> 16:20:34.970 align:start position:0% uh<16:20:33.540> VPN 16:20:34.970 --> 16:20:34.980 align:start position:0% uh VPN 16:20:34.980 --> 16:20:37.426 align:start position:0% uh VPN a<16:20:35.580> virtual<16:20:36.000> Network<16:20:36.296> a<16:20:36.776> virtual<16:20:37.080> private 16:20:37.426 --> 16:20:37.436 align:start position:0% a virtual Network a virtual private 16:20:37.436 --> 16:20:39.586 align:start position:0% a virtual Network a virtual private network<16:20:37.560> is<16:20:37.916> a<16:20:38.096> full<16:20:38.276> term<16:20:38.456> it's<16:20:39.060> built<16:20:39.360> on<16:20:39.480> top 16:20:39.586 --> 16:20:39.596 align:start position:0% network is a full term it's built on top 16:20:39.596 --> 16:20:41.926 align:start position:0% network is a full term it's built on top of<16:20:39.776> an<16:20:39.900> existing<16:20:40.320> public<16:20:40.500> network<16:20:40.936> obviously 16:20:41.926 --> 16:20:41.936 align:start position:0% of an existing public network obviously 16:20:41.936 --> 16:20:43.730 align:start position:0% of an existing public network obviously very<16:20:42.240> handy<16:20:42.596> if<16:20:42.840> we<16:20:42.956> need<16:20:43.140> to<16:20:43.320> securely 16:20:43.730 --> 16:20:43.740 align:start position:0% very handy if we need to securely 16:20:43.740 --> 16:20:46.670 align:start position:0% very handy if we need to securely connect<16:20:44.040> over<16:20:44.456> the<16:20:44.640> internet<16:20:44.820> from 16:20:46.670 --> 16:20:46.680 align:start position:0% connect over the internet from 16:20:46.680 --> 16:20:49.246 align:start position:0% connect over the internet from um two<16:20:46.980> different<16:20:47.220> network<16:20:47.700> locations 16:20:49.246 --> 16:20:49.256 align:start position:0% um two different network locations 16:20:49.256 --> 16:20:51.766 align:start position:0% um two different network locations often<16:20:49.740> used<16:20:49.860> by<16:20:50.040> companies<16:20:50.520> because<16:20:50.880> they 16:20:51.766 --> 16:20:51.776 align:start position:0% often used by companies because they 16:20:51.776 --> 16:20:53.570 align:start position:0% often used by companies because they don't<16:20:51.900> want<16:20:52.080> to<16:20:52.200> buy<16:20:52.320> a<16:20:52.500> dedicated<16:20:52.916> lease<16:20:53.400> line 16:20:53.570 --> 16:20:53.580 align:start position:0% don't want to buy a dedicated lease line 16:20:53.580 --> 16:20:56.630 align:start position:0% don't want to buy a dedicated lease line so<16:20:54.180> they'll<16:20:54.480> just<16:20:54.660> use<16:20:54.916> existing<16:20:55.916> security 16:20:56.630 --> 16:20:56.640 align:start position:0% so they'll just use existing security 16:20:56.640 --> 16:20:58.490 align:start position:0% so they'll just use existing security technology 16:20:58.490 --> 16:20:58.500 align:start position:0% technology 16:20:58.500 --> 16:21:00.946 align:start position:0% technology you<16:20:59.096> have<16:20:59.276> a<16:20:59.520> secure<16:20:59.756> Communications<16:21:00.540> between 16:21:00.946 --> 16:21:00.956 align:start position:0% you have a secure Communications between 16:21:00.956 --> 16:21:02.810 align:start position:0% you have a secure Communications between two<16:21:01.256> private<16:21:01.740> Networks 16:21:02.810 --> 16:21:02.820 align:start position:0% two private Networks 16:21:02.820 --> 16:21:06.350 align:start position:0% two private Networks SSL<16:21:03.720> VPN<16:21:04.320> this<16:21:04.980> is<16:21:05.096> a<16:21:05.276> secure<16:21:05.520> sockets<16:21:05.936> layer 16:21:06.350 --> 16:21:06.360 align:start position:0% SSL VPN this is a secure sockets layer 16:21:06.360 --> 16:21:08.330 align:start position:0% SSL VPN this is a secure sockets layer virtual<16:21:06.900> private<16:21:07.256> Network 16:21:08.330 --> 16:21:08.340 align:start position:0% virtual private Network 16:21:08.340 --> 16:21:10.246 align:start position:0% virtual private Network it<16:21:08.880> provides<16:21:09.360> encrypted<16:21:09.840> communication 16:21:10.246 --> 16:21:10.256 align:start position:0% it provides encrypted communication 16:21:10.256 --> 16:21:13.190 align:start position:0% it provides encrypted communication between<16:21:10.680> a<16:21:11.040> clients<16:21:11.520> and<16:21:11.640> server<16:21:12.000> one<16:21:12.840> example 16:21:13.190 --> 16:21:13.200 align:start position:0% between a clients and server one example 16:21:13.200 --> 16:21:15.830 align:start position:0% between a clients and server one example is<16:21:13.436> SSL<16:21:14.040> equips<16:21:14.580> communication<16:21:15.180> between<16:21:15.480> a 16:21:15.830 --> 16:21:15.840 align:start position:0% is SSL equips communication between a 16:21:15.840 --> 16:21:18.710 align:start position:0% is SSL equips communication between a web<16:21:15.956> browser<16:21:16.500> and<16:21:17.096> a<16:21:17.276> web<16:21:17.400> server<16:21:17.880> and<16:21:18.480> your 16:21:18.710 --> 16:21:18.720 align:start position:0% web browser and a web server and your 16:21:18.720 --> 16:21:21.170 align:start position:0% web browser and a web server and your browser<16:21:19.080> will<16:21:19.320> be<16:21:19.500> a<16:21:20.340> Google<16:21:20.580> Chrome<16:21:20.936> or 16:21:21.170 --> 16:21:21.180 align:start position:0% browser will be a Google Chrome or 16:21:21.180 --> 16:21:22.730 align:start position:0% browser will be a Google Chrome or whatever<16:21:21.360> you're<16:21:21.596> running<16:21:21.776> on<16:21:22.080> your<16:21:22.380> laptop 16:21:22.730 --> 16:21:22.740 align:start position:0% whatever you're running on your laptop 16:21:22.740 --> 16:21:24.530 align:start position:0% whatever you're running on your laptop or<16:21:22.916> PC 16:21:24.530 --> 16:21:24.540 align:start position:0% or PC 16:21:24.540 --> 16:21:27.106 align:start position:0% or PC the<16:21:25.080> user<16:21:25.320> connects<16:21:25.680> to<16:21:25.740> VPN<16:21:26.160> devices<16:21:26.520> using 16:21:27.106 --> 16:21:27.116 align:start position:0% the user connects to VPN devices using 16:21:27.116 --> 16:21:29.446 align:start position:0% the user connects to VPN devices using their<16:21:27.296> web<16:21:27.540> browsers<16:21:28.020> traffic<16:21:28.860> between<16:21:29.220> the 16:21:29.446 --> 16:21:29.456 align:start position:0% their web browsers traffic between the 16:21:29.456 --> 16:21:31.130 align:start position:0% their web browsers traffic between the web<16:21:29.580> browser<16:21:29.936> and<16:21:30.060> the<16:21:30.180> VPN<16:21:30.480> is<16:21:30.660> encrypted 16:21:31.130 --> 16:21:31.140 align:start position:0% web browser and the VPN is encrypted 16:21:31.140 --> 16:21:35.390 align:start position:0% web browser and the VPN is encrypted with<16:21:31.320> the<16:21:31.500> SSL<16:21:31.916> protocol 16:21:35.390 --> 16:21:35.400 align:start position:0% 16:21:35.400 --> 16:21:37.190 align:start position:0% so<16:21:35.756> as<16:21:35.936> a<16:21:36.116> result<16:21:36.240> you've<16:21:36.540> got<16:21:36.660> a<16:21:36.840> secure 16:21:37.190 --> 16:21:37.200 align:start position:0% so as a result you've got a secure 16:21:37.200 --> 16:21:39.470 align:start position:0% so as a result you've got a secure access<16:21:37.740> to<16:21:38.096> web<16:21:38.276> applications<16:21:38.880> and<16:21:39.296> client 16:21:39.470 --> 16:21:39.480 align:start position:0% access to web applications and client 16:21:39.480 --> 16:21:41.570 align:start position:0% access to web applications and client server<16:21:39.956> applications 16:21:41.570 --> 16:21:41.580 align:start position:0% server applications 16:21:41.580 --> 16:21:43.850 align:start position:0% server applications you'll<16:21:42.180> see<16:21:42.360> this<16:21:42.596> working<16:21:42.776> with<16:21:43.256> the<16:21:43.796> um 16:21:43.850 --> 16:21:43.860 align:start position:0% you'll see this working with the um 16:21:43.860 --> 16:21:46.906 align:start position:0% you'll see this working with the um green<16:21:44.340> padlock<16:21:44.936> when<16:21:45.660> you're<16:21:45.916> browsing 16:21:46.906 --> 16:21:46.916 align:start position:0% green padlock when you're browsing 16:21:46.916 --> 16:21:49.130 align:start position:0% green padlock when you're browsing different<16:21:47.160> websites<16:21:47.936> built<16:21:48.776> into<16:21:48.840> all 16:21:49.130 --> 16:21:49.140 align:start position:0% different websites built into all 16:21:49.140 --> 16:21:51.050 align:start position:0% different websites built into all standard<16:21:49.500> web<16:21:49.680> browsers<16:21:50.160> you'd<16:21:50.640> have<16:21:50.756> to<16:21:50.880> add 16:21:51.050 --> 16:21:51.060 align:start position:0% standard web browsers you'd have to add 16:21:51.060 --> 16:21:53.086 align:start position:0% standard web browsers you'd have to add anything<16:21:51.240> extra<16:21:51.660> on<16:21:51.956> you<16:21:52.616> don't<16:21:52.740> have<16:21:52.860> to 16:21:53.086 --> 16:21:53.096 align:start position:0% anything extra on you don't have to 16:21:53.096 --> 16:21:55.010 align:start position:0% anything extra on you don't have to configure<16:21:53.580> or<16:21:53.756> install<16:21:53.880> any<16:21:54.296> client<16:21:54.596> software 16:21:55.010 --> 16:21:55.020 align:start position:0% configure or install any client software 16:21:55.020 --> 16:21:57.650 align:start position:0% configure or install any client software anymore<16:21:55.320> you<16:21:55.980> used<16:21:56.220> to<16:21:56.340> have<16:21:56.456> to<16:21:56.640> that<16:21:57.360> was<16:21:57.540> a 16:21:57.650 --> 16:21:57.660 align:start position:0% anymore you used to have to that was a 16:21:57.660 --> 16:21:59.150 align:start position:0% anymore you used to have to that was a few<16:21:57.776> years<16:21:57.900> ago<16:21:58.140> now<16:21:58.380> and<16:21:58.560> it's<16:21:58.680> all<16:21:58.796> built 16:21:59.150 --> 16:21:59.160 align:start position:0% few years ago now and it's all built 16:21:59.160 --> 16:22:01.310 align:start position:0% few years ago now and it's all built into<16:21:59.220> the<16:21:59.456> web<16:21:59.580> browsers 16:22:01.310 --> 16:22:01.320 align:start position:0% into the web browsers 16:22:01.320 --> 16:22:03.710 align:start position:0% into the web browsers uh<16:22:01.916> the<16:22:02.040> SSL<16:22:02.456> VPN<16:22:02.880> can<16:22:03.180> be<16:22:03.296> accessed<16:22:03.596> from 16:22:03.710 --> 16:22:03.720 align:start position:0% uh the SSL VPN can be accessed from 16:22:03.720 --> 16:22:05.746 align:start position:0% uh the SSL VPN can be accessed from anywhere<16:22:04.080> including<16:22:04.616> airport<16:22:04.796> hotel<16:22:05.276> rooms 16:22:05.746 --> 16:22:05.756 align:start position:0% anywhere including airport hotel rooms 16:22:05.756 --> 16:22:08.086 align:start position:0% anywhere including airport hotel rooms coffee<16:22:06.000> shops<16:22:06.416> as<16:22:06.596> long<16:22:07.020> as<16:22:07.140> you've<16:22:07.320> got<16:22:07.436> web 16:22:08.086 --> 16:22:08.096 align:start position:0% coffee shops as long as you've got web 16:22:08.096 --> 16:22:10.906 align:start position:0% coffee shops as long as you've got web connectivity<16:22:08.956> and<16:22:09.956> the<16:22:10.140> user<16:22:10.380> has<16:22:10.500> a<16:22:10.680> standard 16:22:10.906 --> 16:22:10.916 align:start position:0% connectivity and the user has a standard 16:22:10.916 --> 16:22:12.530 align:start position:0% connectivity and the user has a standard SSL<16:22:11.400> client<16:22:11.700> that's<16:22:11.936> used<16:22:12.116> with<16:22:12.360> that 16:22:12.530 --> 16:22:12.540 align:start position:0% SSL client that's used with that 16:22:12.540 --> 16:22:15.830 align:start position:0% SSL client that's used with that particular<16:22:12.916> SSL<16:22:13.916> VPN 16:22:15.830 --> 16:22:15.840 align:start position:0% particular SSL VPN 16:22:15.840 --> 16:22:19.070 align:start position:0% particular SSL VPN uh<16:22:16.680> SSL<16:22:17.220> VPN<16:22:17.756> products<16:22:18.116> usually<16:22:18.480> Standalone 16:22:19.070 --> 16:22:19.080 align:start position:0% uh SSL VPN products usually Standalone 16:22:19.080 --> 16:22:21.890 align:start position:0% uh SSL VPN products usually Standalone Hardware<16:22:19.380> Appliances<16:22:20.096> and<16:22:20.936> other<16:22:21.180> software 16:22:21.890 --> 16:22:21.900 align:start position:0% Hardware Appliances and other software 16:22:21.900 --> 16:22:25.010 align:start position:0% Hardware Appliances and other software Solutions<16:22:22.436> available<16:22:23.116> speak<16:22:24.116> to<16:22:24.360> uh<16:22:24.776> whatever 16:22:25.010 --> 16:22:25.020 align:start position:0% Solutions available speak to uh whatever 16:22:25.020 --> 16:22:27.286 align:start position:0% Solutions available speak to uh whatever the<16:22:25.380> whoever<16:22:25.796> the<16:22:25.980> sales<16:22:26.160> representative<16:22:26.936> is 16:22:27.286 --> 16:22:27.296 align:start position:0% the whoever the sales representative is 16:22:27.296 --> 16:22:29.870 align:start position:0% the whoever the sales representative is for<16:22:27.596> Cisco<16:22:28.080> or<16:22:28.320> whoever<16:22:28.680> you're<16:22:29.340> using<16:22:29.640> for 16:22:29.870 --> 16:22:29.880 align:start position:0% for Cisco or whoever you're using for 16:22:29.880 --> 16:22:31.730 align:start position:0% for Cisco or whoever you're using for the<16:22:30.116> technology 16:22:31.730 --> 16:22:31.740 align:start position:0% the technology 16:22:31.740 --> 16:22:33.530 align:start position:0% the technology you<16:22:32.096> also<16:22:32.276> get<16:22:32.456> common<16:22:32.640> security<16:22:33.000> services 16:22:33.530 --> 16:22:33.540 align:start position:0% you also get common security services 16:22:33.540 --> 16:22:36.586 align:start position:0% you also get common security services such<16:22:34.080> as<16:22:34.256> authentication<16:22:35.596> encryption 16:22:36.586 --> 16:22:36.596 align:start position:0% such as authentication encryption 16:22:36.596 --> 16:22:39.710 align:start position:0% such as authentication encryption Integrity<16:22:37.500> protection<16:22:38.040> Access<16:22:38.880> Control<16:22:39.296> who 16:22:39.710 --> 16:22:39.720 align:start position:0% Integrity protection Access Control who 16:22:39.720 --> 16:22:41.030 align:start position:0% Integrity protection Access Control who can<16:22:39.956> access 16:22:41.030 --> 16:22:41.040 align:start position:0% can access 16:22:41.040 --> 16:22:43.266 align:start position:0% can access even<16:22:41.580> how<16:22:41.880> long<16:22:42.000> they<16:22:42.240> can<16:22:42.360> access<16:22:42.540> for 16:22:43.266 --> 16:22:43.276 align:start position:0% even how long they can access for 16:22:43.276 --> 16:22:47.086 align:start position:0% even how long they can access for security<16:22:44.276> and<16:22:45.060> endpoint<16:22:45.480> security<16:22:45.776> controls 16:22:47.086 --> 16:22:47.096 align:start position:0% security and endpoint security controls 16:22:47.096 --> 16:22:51.786 align:start position:0% security and endpoint security controls in<16:22:47.580> choosing<16:22:48.000> prevention<16:22:48.416> IPS 16:22:51.786 --> 16:22:51.796 align:start position:0% 16:22:51.796 --> 16:22:54.286 align:start position:0% authentication<16:22:52.796> as<16:22:53.220> we<16:22:53.400> know<16:22:53.520> I'm<16:22:53.700> sure<16:22:53.936> is 16:22:54.286 --> 16:22:54.296 align:start position:0% authentication as we know I'm sure is 16:22:54.296 --> 16:22:55.850 align:start position:0% authentication as we know I'm sure is just<16:22:54.540> authenticating<16:22:55.200> that<16:22:55.560> particular 16:22:55.850 --> 16:22:55.860 align:start position:0% just authenticating that particular 16:22:55.860 --> 16:22:58.130 align:start position:0% just authenticating that particular person<16:22:56.096> to<16:22:56.520> verify<16:22:56.936> they<16:22:57.180> are<16:22:57.360> who<16:22:57.776> they<16:22:57.956> say 16:22:58.130 --> 16:22:58.140 align:start position:0% person to verify they are who they say 16:22:58.140 --> 16:23:00.830 align:start position:0% person to verify they are who they say they<16:22:58.380> are<16:22:58.980> encryption<16:22:59.756> encryption<16:23:00.296> protects 16:23:00.830 --> 16:23:00.840 align:start position:0% they are encryption encryption protects 16:23:00.840 --> 16:23:02.406 align:start position:0% they are encryption encryption protects the<16:23:01.080> con 16:23:02.406 --> 16:23:02.416 align:start position:0% the con 16:23:02.416 --> 16:23:05.330 align:start position:0% the con confidentiality<16:23:03.416> of<16:23:03.660> the<16:23:03.840> data<16:23:04.256> as<16:23:04.740> it<16:23:04.980> passes 16:23:05.330 --> 16:23:05.340 align:start position:0% confidentiality of the data as it passes 16:23:05.340 --> 16:23:08.570 align:start position:0% confidentiality of the data as it passes through<16:23:05.456> through<16:23:05.820> the<16:23:06.060> internet 16:23:08.570 --> 16:23:08.580 align:start position:0% 16:23:08.580 --> 16:23:10.670 align:start position:0% Integrity<16:23:09.296> ensures<16:23:09.840> that<16:23:10.020> the<16:23:10.140> data<16:23:10.436> is<16:23:10.500> not 16:23:10.670 --> 16:23:10.680 align:start position:0% Integrity ensures that the data is not 16:23:10.680 --> 16:23:12.350 align:start position:0% Integrity ensures that the data is not altered<16:23:11.096> so 16:23:12.350 --> 16:23:12.360 align:start position:0% altered so 16:23:12.360 --> 16:23:14.810 align:start position:0% altered so um there's<16:23:12.720> a<16:23:12.840> whole<16:23:13.436> bunch<16:23:13.680> of<16:23:13.796> ways<16:23:14.220> to<16:23:14.820> um 16:23:14.810 --> 16:23:14.820 align:start position:0% um there's a whole bunch of ways to um 16:23:14.820 --> 16:23:18.530 align:start position:0% um there's a whole bunch of ways to um showing<16:23:15.720> and<16:23:16.320> offer<16:23:16.680> Integrity<16:23:17.096> of<16:23:17.640> the<16:23:17.936> data 16:23:18.530 --> 16:23:18.540 align:start position:0% showing and offer Integrity of the data 16:23:18.540 --> 16:23:20.746 align:start position:0% showing and offer Integrity of the data as<16:23:18.660> it's<16:23:18.900> sent<16:23:19.436> from<16:23:19.796> the<16:23:20.276> source<16:23:20.640> and 16:23:20.746 --> 16:23:20.756 align:start position:0% as it's sent from the source and 16:23:20.756 --> 16:23:22.850 align:start position:0% as it's sent from the source and received<16:23:21.116> at<16:23:21.240> the<16:23:21.416> destination 16:23:22.850 --> 16:23:22.860 align:start position:0% received at the destination 16:23:22.860 --> 16:23:25.010 align:start position:0% received at the destination Access<16:23:23.456> Control<16:23:23.820> gives<16:23:24.240> restricted<16:23:24.776> access 16:23:25.010 --> 16:23:25.020 align:start position:0% Access Control gives restricted access 16:23:25.020 --> 16:23:27.050 align:start position:0% Access Control gives restricted access and<16:23:25.380> that<16:23:25.560> can<16:23:25.680> be<16:23:25.796> based<16:23:26.220> upon<16:23:26.456> a<16:23:26.756> number<16:23:26.880> of 16:23:27.050 --> 16:23:27.060 align:start position:0% and that can be based upon a number of 16:23:27.060 --> 16:23:29.470 align:start position:0% and that can be based upon a number of things<16:23:27.360> and<16:23:27.956> the<16:23:28.140> access<16:23:28.256> control<16:23:28.680> is<16:23:28.980> then 16:23:29.470 --> 16:23:29.480 align:start position:0% things and the access control is then 16:23:29.480 --> 16:23:31.786 align:start position:0% things and the access control is then associated<16:23:30.480> with<16:23:30.776> whatever<16:23:31.020> privilege<16:23:31.616> is 16:23:31.786 --> 16:23:31.796 align:start position:0% associated with whatever privilege is 16:23:31.796 --> 16:23:35.350 align:start position:0% associated with whatever privilege is you<16:23:32.400> wanted<16:23:32.520> to<16:23:32.756> give<16:23:32.936> that<16:23:33.240> particular<16:23:33.540> user 16:23:35.350 --> 16:23:35.360 align:start position:0% you wanted to give that particular user 16:23:35.360 --> 16:23:37.850 align:start position:0% you wanted to give that particular user the<16:23:36.360> endpoint<16:23:36.660> security<16:23:36.840> controls<16:23:37.500> checks 16:23:37.850 --> 16:23:37.860 align:start position:0% the endpoint security controls checks 16:23:37.860 --> 16:23:39.586 align:start position:0% the endpoint security controls checks the<16:23:37.916> user<16:23:38.220> system<16:23:38.400> for<16:23:38.700> compliance<16:23:39.180> whenever 16:23:39.586 --> 16:23:39.596 align:start position:0% the user system for compliance whenever 16:23:39.596 --> 16:23:45.286 align:start position:0% the user system for compliance whenever the<16:23:39.776> user<16:23:40.080> attempts<16:23:40.616> to<16:23:40.916> use<16:23:41.700> the<16:23:41.936> SSL<16:23:42.480> VPN 16:23:45.286 --> 16:23:45.296 align:start position:0% 16:23:45.296 --> 16:23:47.510 align:start position:0% intrusion<16:23:46.020> prevention<16:23:46.436> checks<16:23:47.096> the<16:23:47.160> data<16:23:47.400> for 16:23:47.510 --> 16:23:47.520 align:start position:0% intrusion prevention checks the data for 16:23:47.520 --> 16:23:49.070 align:start position:0% intrusion prevention checks the data for any<16:23:47.700> Potential<16:23:48.116> Threat<16:23:48.416> after<16:23:48.660> it's<16:23:48.900> been 16:23:49.070 --> 16:23:49.080 align:start position:0% any Potential Threat after it's been 16:23:49.080 --> 16:23:50.690 align:start position:0% any Potential Threat after it's been decrypted 16:23:50.690 --> 16:23:50.700 align:start position:0% decrypted 16:23:50.700 --> 16:23:54.050 align:start position:0% decrypted VPN<16:23:51.480> concentrators<16:23:52.256> these<16:23:52.980> were<16:23:53.400> supported 16:23:54.050 --> 16:23:54.060 align:start position:0% VPN concentrators these were supported 16:23:54.060 --> 16:23:56.510 align:start position:0% VPN concentrators these were supported originally<16:23:54.596> when<16:23:55.320> I<16:23:55.436> worked<16:23:55.680> at<16:23:55.740> Cisco<16:23:56.096> by<16:23:56.340> the 16:23:56.510 --> 16:23:56.520 align:start position:0% originally when I worked at Cisco by the 16:23:56.520 --> 16:23:57.830 align:start position:0% originally when I worked at Cisco by the security<16:23:56.700> team 16:23:57.830 --> 16:23:57.840 align:start position:0% security team 16:23:57.840 --> 16:23:59.870 align:start position:0% security team they<16:23:58.380> provide<16:23:58.680> a<16:23:58.796> remote<16:23:58.980> user<16:23:59.400> with<16:23:59.520> secure 16:23:59.870 --> 16:23:59.880 align:start position:0% they provide a remote user with secure 16:23:59.880 --> 16:24:02.086 align:start position:0% they provide a remote user with secure access<16:24:00.116> to<16:24:00.416> the<16:24:00.660> organization's<16:24:01.500> resources 16:24:02.086 --> 16:24:02.096 align:start position:0% access to the organization's resources 16:24:02.096 --> 16:24:04.246 align:start position:0% access to the organization's resources and<16:24:02.756> the<16:24:02.880> concentrator<16:24:03.480> is<16:24:03.720> basically<16:24:04.020> an 16:24:04.246 --> 16:24:04.256 align:start position:0% and the concentrator is basically an 16:24:04.256 --> 16:24:07.246 align:start position:0% and the concentrator is basically an endpoint<16:24:04.616> for<16:24:04.916> multiple<16:24:05.540> VPN<16:24:06.540> connections<16:24:07.080> so 16:24:07.246 --> 16:24:07.256 align:start position:0% endpoint for multiple VPN connections so 16:24:07.256 --> 16:24:08.990 align:start position:0% endpoint for multiple VPN connections so there's<16:24:07.436> maybe<16:24:07.680> lots<16:24:08.096> of<16:24:08.160> Home<16:24:08.400> users<16:24:08.820> or 16:24:08.990 --> 16:24:09.000 align:start position:0% there's maybe lots of Home users or 16:24:09.000 --> 16:24:12.170 align:start position:0% there's maybe lots of Home users or people<16:24:09.180> dialing<16:24:09.720> in<16:24:09.900> and 16:24:12.170 --> 16:24:12.180 align:start position:0% people dialing in and 16:24:12.180 --> 16:24:14.926 align:start position:0% people dialing in and Mobile<16:24:12.776> sales<16:24:13.200> people<16:24:13.616> that<16:24:14.520> need<16:24:14.700> to<16:24:14.820> connect 16:24:14.926 --> 16:24:14.936 align:start position:0% Mobile sales people that need to connect 16:24:14.936 --> 16:24:16.490 align:start position:0% Mobile sales people that need to connect from<16:24:15.240> certain<16:24:15.480> places<16:24:15.776> and<16:24:16.020> the<16:24:16.200> VPN 16:24:16.490 --> 16:24:16.500 align:start position:0% from certain places and the VPN 16:24:16.500 --> 16:24:18.406 align:start position:0% from certain places and the VPN concentrator<16:24:17.160> will<16:24:17.756> be<16:24:17.936> the<16:24:18.060> point<16:24:18.180> where 16:24:18.406 --> 16:24:18.416 align:start position:0% concentrator will be the point where 16:24:18.416 --> 16:24:22.490 align:start position:0% concentrator will be the point where their<16:24:18.596> connection<16:24:18.776> is<16:24:19.200> terminated 16:24:22.490 --> 16:24:22.500 align:start position:0% 16:24:22.500 --> 16:24:24.890 align:start position:0% all<16:24:23.096> right<16:24:23.276> uh<16:24:23.820> the<16:24:24.000> concentrate<16:24:24.416> is<16:24:24.596> a<16:24:24.776> device 16:24:24.890 --> 16:24:24.900 align:start position:0% all right uh the concentrate is a device 16:24:24.900 --> 16:24:28.550 align:start position:0% all right uh the concentrate is a device it<16:24:25.200> can<16:24:25.320> handle<16:24:25.616> multiple<16:24:25.916> tunnels<16:24:26.340> coming<16:24:26.580> in 16:24:28.550 --> 16:24:28.560 align:start position:0% it can handle multiple tunnels coming in 16:24:28.560 --> 16:24:31.730 align:start position:0% it can handle multiple tunnels coming in a<16:24:29.096> VPN<16:24:29.580> they<16:24:29.936> provide<16:24:30.296> VPN<16:24:31.080> encryption<16:24:31.500> either 16:24:31.730 --> 16:24:31.740 align:start position:0% a VPN they provide VPN encryption either 16:24:31.740 --> 16:24:34.550 align:start position:0% a VPN they provide VPN encryption either by<16:24:31.980> using<16:24:32.220> ipsec<16:24:33.060> or<16:24:33.296> SSL 16:24:34.550 --> 16:24:34.560 align:start position:0% by using ipsec or SSL 16:24:34.560 --> 16:24:37.310 align:start position:0% by using ipsec or SSL again<16:24:35.096> check<16:24:35.400> with<16:24:35.640> your<16:24:36.080> vendor<16:24:37.080> for 16:24:37.310 --> 16:24:37.320 align:start position:0% again check with your vendor for 16:24:37.320 --> 16:24:38.690 align:start position:0% again check with your vendor for documentation 16:24:38.690 --> 16:24:38.700 align:start position:0% documentation 16:24:38.700 --> 16:24:41.746 align:start position:0% documentation ipsec<16:24:39.660> is<16:24:39.840> IP<16:24:40.200> security<16:24:40.520> provides<16:24:41.520> a<16:24:41.640> high 16:24:41.746 --> 16:24:41.756 align:start position:0% ipsec is IP security provides a high 16:24:41.756 --> 16:24:44.570 align:start position:0% ipsec is IP security provides a high level<16:24:41.936> of<16:24:42.180> security<16:24:42.480> and<16:24:42.956> encryption<16:24:43.580> and 16:24:44.570 --> 16:24:44.580 align:start position:0% level of security and encryption and 16:24:44.580 --> 16:24:46.850 align:start position:0% level of security and encryption and because<16:24:44.936> client<16:24:45.360> software<16:24:45.776> to<16:24:46.020> establish<16:24:46.680> the 16:24:46.850 --> 16:24:46.860 align:start position:0% because client software to establish the 16:24:46.860 --> 16:24:50.030 align:start position:0% because client software to establish the VPN<16:24:47.340> tunnel 16:24:50.030 --> 16:24:50.040 align:start position:0% 16:24:50.040 --> 16:24:53.030 align:start position:0% ipsec<16:24:50.936> is<16:24:51.060> better<16:24:51.180> for<16:24:51.416> fixed<16:24:51.776> locations<16:24:52.380> SSR 16:24:53.030 --> 16:24:53.040 align:start position:0% ipsec is better for fixed locations SSR 16:24:53.040 --> 16:24:54.470 align:start position:0% ipsec is better for fixed locations SSR when<16:24:53.276> the<16:24:53.400> remote<16:24:53.520> users<16:24:54.000> need<16:24:54.180> to<16:24:54.296> connect 16:24:54.470 --> 16:24:54.480 align:start position:0% when the remote users need to connect 16:24:54.480 --> 16:24:57.106 align:start position:0% when the remote users need to connect from<16:24:54.956> various<16:24:55.580> locations<16:24:56.580> for<16:24:56.880> example 16:24:57.106 --> 16:24:57.116 align:start position:0% from various locations for example 16:24:57.116 --> 16:25:00.766 align:start position:0% from various locations for example they're<16:24:57.416> a<16:24:57.720> traveling<16:24:58.500> salesperson 16:25:00.766 --> 16:25:00.776 align:start position:0% they're a traveling salesperson 16:25:00.776 --> 16:25:03.650 align:start position:0% they're a traveling salesperson and<16:25:01.500> nowadays<16:25:02.096> VPN<16:25:02.580> concentrators<16:25:03.240> are<16:25:03.480> not 16:25:03.650 --> 16:25:03.660 align:start position:0% and nowadays VPN concentrators are not 16:25:03.660 --> 16:25:06.710 align:start position:0% and nowadays VPN concentrators are not manufactured<16:25:04.320> as<16:25:04.796> separate<16:25:05.520> devices<16:25:05.936> they 16:25:06.710 --> 16:25:06.720 align:start position:0% manufactured as separate devices they 16:25:06.720 --> 16:25:08.390 align:start position:0% manufactured as separate devices they normally<16:25:07.020> combined<16:25:07.436> with<16:25:07.500> devices<16:25:07.860> that<16:25:08.160> also 16:25:08.390 --> 16:25:08.400 align:start position:0% normally combined with devices that also 16:25:08.400 --> 16:25:10.670 align:start position:0% normally combined with devices that also provide<16:25:08.756> firewall<16:25:09.296> protection<16:25:09.720> if<16:25:10.380> you<16:25:10.500> go<16:25:10.616> to 16:25:10.670 --> 16:25:10.680 align:start position:0% provide firewall protection if you go to 16:25:10.680 --> 16:25:12.946 align:start position:0% provide firewall protection if you go to cisco.com<16:25:11.340> and<16:25:11.640> then<16:25:11.756> click<16:25:11.936> on<16:25:12.180> I<16:25:12.660> think<16:25:12.776> it's 16:25:12.946 --> 16:25:12.956 align:start position:0% cisco.com and then click on I think it's 16:25:12.956 --> 16:25:15.406 align:start position:0% cisco.com and then click on I think it's sales<16:25:13.256> or<16:25:13.616> products<16:25:14.220> you'll<16:25:14.820> see<16:25:15.000> the<16:25:15.180> type<16:25:15.296> of 16:25:15.406 --> 16:25:15.416 align:start position:0% sales or products you'll see the type of 16:25:15.416 --> 16:25:17.150 align:start position:0% sales or products you'll see the type of devices<16:25:15.720> that<16:25:16.080> are<16:25:16.200> available<16:25:16.380> and<16:25:16.796> what<16:25:16.980> they 16:25:17.150 --> 16:25:17.160 align:start position:0% devices that are available and what they 16:25:17.160 --> 16:25:18.470 align:start position:0% devices that are available and what they do 16:25:18.470 --> 16:25:18.480 align:start position:0% do 16:25:18.480 --> 16:25:20.150 align:start position:0% do all<16:25:18.956> right<16:25:19.080> so<16:25:19.140> we've<16:25:19.320> covered<16:25:19.560> a<16:25:19.740> fair<16:25:19.860> bit 16:25:20.150 --> 16:25:20.160 align:start position:0% all right so we've covered a fair bit 16:25:20.160 --> 16:25:25.970 align:start position:0% all right so we've covered a fair bit GRE<16:25:21.020> tunneling<16:25:22.020> VPN<16:25:22.796> SSL 16:25:25.970 --> 16:25:25.980 align:start position:0% 16:25:25.980 --> 16:25:29.510 align:start position:0% Security<16:25:26.700> Services<16:25:27.180> of<16:25:27.660> SSL<16:25:28.140> VPN<16:25:28.740> and<16:25:29.040> a<16:25:29.160> VPN 16:25:29.510 --> 16:25:29.520 align:start position:0% Security Services of SSL VPN and a VPN 16:25:29.520 --> 16:25:32.266 align:start position:0% Security Services of SSL VPN and a VPN concentrator<16:25:30.116> on<16:25:30.956> ipsec 16:25:32.266 --> 16:25:32.276 align:start position:0% concentrator on ipsec 16:25:32.276 --> 16:25:39.320 align:start position:0% concentrator on ipsec that's<16:25:32.640> all<16:25:32.880> for<16:25:33.060> now<16:25:33.180> thanks<16:25:33.596> for<16:25:33.776> watching 16:25:39.320 --> 16:25:39.330 align:start position:0% 16:25:39.330 --> 16:25:59.350 align:start position:0% [Music] 16:25:59.350 --> 16:25:59.360 align:start position:0% 16:25:59.360 --> 16:26:01.850 align:start position:0% Network<16:26:00.360> management<16:26:00.860> Network 16:26:01.850 --> 16:26:01.860 align:start position:0% Network management Network 16:26:01.860 --> 16:26:03.946 align:start position:0% Network management Network Administration 16:26:03.946 --> 16:26:03.956 align:start position:0% Administration 16:26:03.956 --> 16:26:05.630 align:start position:0% Administration in<16:26:04.380> the<16:26:04.436> previous<16:26:04.560> lessons<16:26:05.040> we've<16:26:05.400> talked 16:26:05.630 --> 16:26:05.640 align:start position:0% in the previous lessons we've talked 16:26:05.640 --> 16:26:08.086 align:start position:0% in the previous lessons we've talked about<16:26:05.756> a<16:26:06.000> lot<16:26:06.116> of<16:26:06.240> the<16:26:06.360> technical<16:26:06.720> aspects<16:26:07.500> of 16:26:08.086 --> 16:26:08.096 align:start position:0% about a lot of the technical aspects of 16:26:08.096 --> 16:26:10.310 align:start position:0% about a lot of the technical aspects of networking<16:26:08.640> including<16:26:09.296> remote<16:26:09.596> networking 16:26:10.310 --> 16:26:10.320 align:start position:0% networking including remote networking 16:26:10.320 --> 16:26:13.246 align:start position:0% networking including remote networking remote<16:26:10.680> access<16:26:11.296> virtual<16:26:12.296> private<16:26:12.776> networks 16:26:13.246 --> 16:26:13.256 align:start position:0% remote access virtual private networks 16:26:13.256 --> 16:26:15.350 align:start position:0% remote access virtual private networks local<16:26:13.500> area<16:26:13.796> networks<16:26:14.276> wide<16:26:14.520> area<16:26:14.756> networks 16:26:15.350 --> 16:26:15.360 align:start position:0% local area networks wide area networks 16:26:15.360 --> 16:26:17.390 align:start position:0% local area networks wide area networks and<16:26:15.480> so<16:26:15.660> on<16:26:15.840> there's<16:26:16.436> someone<16:26:16.680> who's<16:26:16.980> required 16:26:17.390 --> 16:26:17.400 align:start position:0% and so on there's someone who's required 16:26:17.400 --> 16:26:19.490 align:start position:0% and so on there's someone who's required to<16:26:17.520> sort<16:26:17.820> of<16:26:17.936> put<16:26:18.416> all<16:26:18.596> of<16:26:18.776> this<16:26:18.956> into<16:26:19.140> place 16:26:19.490 --> 16:26:19.500 align:start position:0% to sort of put all of this into place 16:26:19.500 --> 16:26:21.470 align:start position:0% to sort of put all of this into place and<16:26:19.980> that's<16:26:20.160> where<16:26:20.340> an<16:26:20.520> administrator<16:26:21.060> comes 16:26:21.470 --> 16:26:21.480 align:start position:0% and that's where an administrator comes 16:26:21.480 --> 16:26:23.926 align:start position:0% and that's where an administrator comes in<16:26:21.596> so<16:26:22.320> in<16:26:22.740> this<16:26:22.916> lesson<16:26:23.400> and<16:26:23.580> in<16:26:23.756> the 16:26:23.926 --> 16:26:23.936 align:start position:0% in so in this lesson and in the 16:26:23.936 --> 16:26:26.266 align:start position:0% in so in this lesson and in the following<16:26:24.296> modules<16:26:24.720> I<16:26:25.256> want<16:26:25.380> to<16:26:25.560> talk<16:26:25.796> about 16:26:26.266 --> 16:26:26.276 align:start position:0% following modules I want to talk about 16:26:26.276 --> 16:26:29.570 align:start position:0% following modules I want to talk about what<16:26:27.116> an<16:26:27.360> administrator<16:26:28.080> is<16:26:28.680> and<16:26:29.160> some<16:26:29.340> of<16:26:29.456> the 16:26:29.570 --> 16:26:29.580 align:start position:0% what an administrator is and some of the 16:26:29.580 --> 16:26:31.970 align:start position:0% what an administrator is and some of the tasks<16:26:30.000> they<16:26:30.180> have<16:26:30.360> to<16:26:30.480> do<16:26:30.660> in<16:26:31.380> this<16:26:31.560> module<16:26:31.860> in 16:26:31.970 --> 16:26:31.980 align:start position:0% tasks they have to do in this module in 16:26:31.980 --> 16:26:33.230 align:start position:0% tasks they have to do in this module in specific<16:26:32.340> we're<16:26:32.580> going<16:26:32.700> to<16:26:32.820> start<16:26:32.936> by 16:26:33.230 --> 16:26:33.240 align:start position:0% specific we're going to start by 16:26:33.240 --> 16:26:35.330 align:start position:0% specific we're going to start by defining<16:26:33.900> an<16:26:34.200> administrator<16:26:34.796> or<16:26:35.096> network 16:26:35.330 --> 16:26:35.340 align:start position:0% defining an administrator or network 16:26:35.340 --> 16:26:37.730 align:start position:0% defining an administrator or network administrator<16:26:36.180> now<16:26:36.776> there<16:26:37.080> can<16:26:37.200> be<16:26:37.380> several 16:26:37.730 --> 16:26:37.740 align:start position:0% administrator now there can be several 16:26:37.740 --> 16:26:39.406 align:start position:0% administrator now there can be several administrators<16:26:38.400> at<16:26:38.640> any<16:26:38.756> one's<16:26:39.060> site<16:26:39.240> but 16:26:39.406 --> 16:26:39.416 align:start position:0% administrators at any one's site but 16:26:39.416 --> 16:26:40.786 align:start position:0% administrators at any one's site but we're<16:26:39.540> going<16:26:39.660> to<16:26:39.720> give<16:26:39.840> an<16:26:40.020> overview<16:26:40.436> of<16:26:40.616> what 16:26:40.786 --> 16:26:40.796 align:start position:0% we're going to give an overview of what 16:26:40.796 --> 16:26:42.406 align:start position:0% we're going to give an overview of what an<16:26:40.980> administrator<16:26:41.456> no<16:26:41.756> matter<16:26:41.880> what<16:26:42.240> their 16:26:42.406 --> 16:26:42.416 align:start position:0% an administrator no matter what their 16:26:42.416 --> 16:26:44.810 align:start position:0% an administrator no matter what their specific<16:26:42.720> role<16:26:43.200> is<16:26:43.256> going<16:26:43.436> to<16:26:43.616> do<16:26:43.796> then<16:26:44.640> we're 16:26:44.810 --> 16:26:44.820 align:start position:0% specific role is going to do then we're 16:26:44.820 --> 16:26:46.850 align:start position:0% specific role is going to do then we're going<16:26:45.000> to<16:26:45.116> identify<16:26:45.540> some<16:26:45.840> of<16:26:45.956> the<16:26:46.080> key<16:26:46.380> admin 16:26:46.850 --> 16:26:46.860 align:start position:0% going to identify some of the key admin 16:26:46.860 --> 16:26:49.690 align:start position:0% going to identify some of the key admin duties<16:26:47.340> and<16:26:48.060> these<16:26:48.296> might<16:26:48.480> be<16:26:48.596> documentation 16:26:49.690 --> 16:26:49.700 align:start position:0% duties and these might be documentation 16:26:49.700 --> 16:26:52.490 align:start position:0% duties and these might be documentation and<16:26:50.700> monitoring<16:26:51.416> we'll<16:26:51.840> talk<16:26:52.020> more<16:26:52.320> about 16:26:52.490 --> 16:26:52.500 align:start position:0% and monitoring we'll talk more about 16:26:52.500 --> 16:26:54.286 align:start position:0% and monitoring we'll talk more about these<16:26:52.860> in<16:26:53.096> further<16:26:53.400> modules<16:26:53.820> and<16:26:54.060> we've 16:26:54.286 --> 16:26:54.296 align:start position:0% these in further modules and we've 16:26:54.296 --> 16:26:55.490 align:start position:0% these in further modules and we've probably<16:26:54.480> already<16:26:54.596> mentioned<16:26:55.080> already 16:26:55.490 --> 16:26:55.500 align:start position:0% probably already mentioned already 16:26:55.500 --> 16:26:58.246 align:start position:0% probably already mentioned already mentioned<16:26:56.276> these<16:26:56.640> to<16:26:57.060> some<16:26:57.240> degree<16:26:57.596> so<16:26:58.080> some 16:26:58.246 --> 16:26:58.256 align:start position:0% mentioned these to some degree so some 16:26:58.256 --> 16:27:00.890 align:start position:0% mentioned these to some degree so some of<16:26:58.380> this<16:26:58.560> might<16:26:58.860> be<16:26:59.040> recap<16:26:59.580> in<16:27:00.180> some<16:27:00.296> cases<16:27:00.596> it 16:27:00.890 --> 16:27:00.900 align:start position:0% of this might be recap in some cases it 16:27:00.900 --> 16:27:02.690 align:start position:0% of this might be recap in some cases it might<16:27:01.020> be<16:27:01.140> overview<16:27:01.560> but<16:27:02.040> a<16:27:02.160> lot<16:27:02.220> of<16:27:02.340> what's<16:27:02.456> on 16:27:02.690 --> 16:27:02.700 align:start position:0% might be overview but a lot of what's on 16:27:02.700 --> 16:27:04.906 align:start position:0% might be overview but a lot of what's on the<16:27:02.820> network<16:27:02.936> plus<16:27:03.240> exam<16:27:03.660> is<16:27:03.900> is<16:27:04.436> sort<16:27:04.796> of 16:27:04.906 --> 16:27:04.916 align:start position:0% the network plus exam is is sort of 16:27:04.916 --> 16:27:07.906 align:start position:0% the network plus exam is is sort of applying<16:27:05.756> not<16:27:06.720> just<16:27:06.900> having<16:27:07.256> knowledge<16:27:07.740> but 16:27:07.906 --> 16:27:07.916 align:start position:0% applying not just having knowledge but 16:27:07.916 --> 16:27:09.470 align:start position:0% applying not just having knowledge but applying<16:27:08.340> the<16:27:08.456> knowledge<16:27:08.820> in<16:27:09.360> certain 16:27:09.470 --> 16:27:09.480 align:start position:0% applying the knowledge in certain 16:27:09.480 --> 16:27:11.150 align:start position:0% applying the knowledge in certain administrator<16:27:10.140> roles<16:27:10.560> since<16:27:10.740> that's<16:27:10.916> what 16:27:11.150 --> 16:27:11.160 align:start position:0% administrator roles since that's what 16:27:11.160 --> 16:27:12.766 align:start position:0% administrator roles since that's what they<16:27:11.276> assume<16:27:11.700> you're<16:27:11.880> going<16:27:12.000> to<16:27:12.116> do<16:27:12.240> with<16:27:12.540> your 16:27:12.766 --> 16:27:12.776 align:start position:0% they assume you're going to do with your 16:27:12.776 --> 16:27:14.266 align:start position:0% they assume you're going to do with your certification 16:27:14.266 --> 16:27:14.276 align:start position:0% certification 16:27:14.276 --> 16:27:16.730 align:start position:0% certification so<16:27:14.756> there's<16:27:15.180> no<16:27:15.416> doubt<16:27:15.776> that<16:27:16.020> we<16:27:16.256> have<16:27:16.436> used 16:27:16.730 --> 16:27:16.740 align:start position:0% so there's no doubt that we have used 16:27:16.740 --> 16:27:21.470 align:start position:0% so there's no doubt that we have used administrator<16:27:17.580> or<16:27:18.360> admin<16:27:18.956> for<16:27:19.380> short 16:27:21.470 --> 16:27:21.480 align:start position:0% administrator or admin for short 16:27:21.480 --> 16:27:25.010 align:start position:0% administrator or admin for short in<16:27:22.256> uh<16:27:22.680> hundreds<16:27:23.096> of<16:27:23.220> times<16:27:23.456> by<16:27:24.000> now<16:27:24.180> so<16:27:24.540> it 16:27:25.010 --> 16:27:25.020 align:start position:0% in uh hundreds of times by now so it 16:27:25.020 --> 16:27:26.746 align:start position:0% in uh hundreds of times by now so it might<16:27:25.140> be<16:27:25.256> useful<16:27:25.560> to<16:27:25.860> stop<16:27:26.040> for<16:27:26.400> a<16:27:26.456> minute<16:27:26.580> and 16:27:26.746 --> 16:27:26.756 align:start position:0% might be useful to stop for a minute and 16:27:26.756 --> 16:27:28.670 align:start position:0% might be useful to stop for a minute and actually<16:27:27.000> take<16:27:27.660> time<16:27:27.840> to<16:27:28.020> talk<16:27:28.200> about<16:27:28.320> what 16:27:28.670 --> 16:27:28.680 align:start position:0% actually take time to talk about what 16:27:28.680 --> 16:27:30.766 align:start position:0% actually take time to talk about what this<16:27:28.796> term<16:27:28.980> means<16:27:29.456> so<16:27:30.060> the<16:27:30.180> administrator<16:27:30.596> of 16:27:30.766 --> 16:27:30.776 align:start position:0% this term means so the administrator of 16:27:30.776 --> 16:27:33.286 align:start position:0% this term means so the administrator of a<16:27:30.900> network<16:27:31.080> is<16:27:31.560> the<16:27:32.096> most<16:27:32.456> important<16:27:33.000> person 16:27:33.286 --> 16:27:33.296 align:start position:0% a network is the most important person 16:27:33.296 --> 16:27:36.170 align:start position:0% a network is the most important person involved<16:27:33.956> in<16:27:34.200> network<16:27:34.520> it<16:27:35.520> they<16:27:35.936> are<16:27:36.060> in 16:27:36.170 --> 16:27:36.180 align:start position:0% involved in network it they are in 16:27:36.180 --> 16:27:38.030 align:start position:0% involved in network it they are in charge<16:27:36.296> of<16:27:36.540> everything<16:27:36.900> that<16:27:37.380> happens<16:27:37.560> on<16:27:37.916> the 16:27:38.030 --> 16:27:38.040 align:start position:0% charge of everything that happens on the 16:27:38.040 --> 16:27:41.150 align:start position:0% charge of everything that happens on the network<16:27:38.480> and<16:27:39.480> know<16:27:39.776> what<16:27:40.320> all<16:27:40.616> of<16:27:40.740> the<16:27:40.860> users 16:27:41.150 --> 16:27:41.160 align:start position:0% network and know what all of the users 16:27:41.160 --> 16:27:43.370 align:start position:0% network and know what all of the users are<16:27:41.340> doing<16:27:41.580> in<16:27:42.116> charge<16:27:42.296> of<16:27:42.480> security<16:27:42.776> and<16:27:43.200> they 16:27:43.370 --> 16:27:43.380 align:start position:0% are doing in charge of security and they 16:27:43.380 --> 16:27:44.990 align:start position:0% are doing in charge of security and they can<16:27:43.500> be<16:27:43.616> held<16:27:43.916> responsible<16:27:44.456> for<16:27:44.820> everything 16:27:44.990 --> 16:27:45.000 align:start position:0% can be held responsible for everything 16:27:45.000 --> 16:27:47.086 align:start position:0% can be held responsible for everything that<16:27:45.240> happens<16:27:45.416> on<16:27:45.900> their<16:27:46.020> Network<16:27:46.256> so<16:27:46.916> not 16:27:47.086 --> 16:27:47.096 align:start position:0% that happens on their Network so not 16:27:47.096 --> 16:27:48.586 align:start position:0% that happens on their Network so not only<16:27:47.220> are<16:27:47.456> they<16:27:47.640> responsible<16:27:48.000> for<16:27:48.296> sort<16:27:48.480> of 16:27:48.586 --> 16:27:48.596 align:start position:0% only are they responsible for sort of 16:27:48.596 --> 16:27:50.510 align:start position:0% only are they responsible for sort of creating<16:27:48.900> the<16:27:49.140> network<16:27:49.320> but<16:27:50.040> if<16:27:50.276> someone 16:27:50.510 --> 16:27:50.520 align:start position:0% creating the network but if someone 16:27:50.520 --> 16:27:52.730 align:start position:0% creating the network but if someone misuses<16:27:51.296> the<16:27:51.416> network<16:27:51.596> the<16:27:52.080> really<16:27:52.256> acts<16:27:52.616> is 16:27:52.730 --> 16:27:52.740 align:start position:0% misuses the network the really acts is 16:27:52.740 --> 16:27:54.766 align:start position:0% misuses the network the really acts is going<16:27:52.860> to<16:27:52.980> fall<16:27:53.096> on<16:27:53.340> them<16:27:53.936> more<16:27:54.480> than<16:27:54.596> that 16:27:54.766 --> 16:27:54.776 align:start position:0% going to fall on them more than that 16:27:54.776 --> 16:27:56.570 align:start position:0% going to fall on them more than that they're<16:27:55.020> in<16:27:55.200> control<16:27:55.380> of<16:27:55.616> all<16:27:55.916> the<16:27:56.096> accounts 16:27:56.570 --> 16:27:56.580 align:start position:0% they're in control of all the accounts 16:27:56.580 --> 16:27:58.906 align:start position:0% they're in control of all the accounts the<16:27:56.880> resources<16:27:57.480> the<16:27:57.900> data<16:27:58.200> that<16:27:58.380> users<16:27:58.680> have 16:27:58.906 --> 16:27:58.916 align:start position:0% the resources the data that users have 16:27:58.916 --> 16:28:01.310 align:start position:0% the resources the data that users have access<16:27:59.096> to<16:27:59.520> the<16:28:00.296> administrator<16:28:00.720> is<16:28:00.900> the<16:28:01.200> only 16:28:01.310 --> 16:28:01.320 align:start position:0% access to the administrator is the only 16:28:01.320 --> 16:28:03.586 align:start position:0% access to the administrator is the only person<16:28:01.616> that<16:28:01.980> has<16:28:02.160> access<16:28:02.456> to<16:28:02.936> everything<16:28:03.296> in 16:28:03.586 --> 16:28:03.596 align:start position:0% person that has access to everything in 16:28:03.596 --> 16:28:05.510 align:start position:0% person that has access to everything in the<16:28:03.720> network<16:28:03.900> and<16:28:04.436> can<16:28:04.616> control<16:28:04.796> what<16:28:05.220> others 16:28:05.510 --> 16:28:05.520 align:start position:0% the network and can control what others 16:28:05.520 --> 16:28:07.906 align:start position:0% the network and can control what others can<16:28:05.700> access<16:28:05.880> even<16:28:06.660> if<16:28:06.900> they<16:28:07.080> give<16:28:07.200> access<16:28:07.500> to 16:28:07.906 --> 16:28:07.916 align:start position:0% can access even if they give access to 16:28:07.916 --> 16:28:10.310 align:start position:0% can access even if they give access to say<16:28:08.160> an<16:28:08.456> assistant<16:28:08.580> administrator<16:28:09.480> in<16:28:10.200> the 16:28:10.310 --> 16:28:10.320 align:start position:0% say an assistant administrator in the 16:28:10.320 --> 16:28:11.630 align:start position:0% say an assistant administrator in the end<16:28:10.436> if<16:28:10.680> that<16:28:10.860> assistant<16:28:10.980> administrator 16:28:11.630 --> 16:28:11.640 align:start position:0% end if that assistant administrator 16:28:11.640 --> 16:28:13.490 align:start position:0% end if that assistant administrator screws<16:28:12.116> something<16:28:12.240> up<16:28:12.596> it<16:28:13.080> was<16:28:13.256> the 16:28:13.490 --> 16:28:13.500 align:start position:0% screws something up it was the 16:28:13.500 --> 16:28:15.470 align:start position:0% screws something up it was the administrator<16:28:13.980> who<16:28:14.276> gave<16:28:14.456> them<16:28:14.640> access<16:28:14.936> in 16:28:15.470 --> 16:28:15.480 align:start position:0% administrator who gave them access in 16:28:15.480 --> 16:28:17.810 align:start position:0% administrator who gave them access in the<16:28:15.596> first<16:28:15.720> place<16:28:16.020> so<16:28:16.796> clearly<16:28:17.096> this<16:28:17.340> is<16:28:17.520> a 16:28:17.810 --> 16:28:17.820 align:start position:0% the first place so clearly this is a 16:28:17.820 --> 16:28:19.786 align:start position:0% the first place so clearly this is a really<16:28:18.000> important<16:28:18.596> person<16:28:18.956> and<16:28:19.616> are 16:28:19.786 --> 16:28:19.796 align:start position:0% really important person and are 16:28:19.796 --> 16:28:21.830 align:start position:0% really important person and are essential<16:28:20.276> to<16:28:20.580> managing<16:28:21.060> and<16:28:21.240> monitoring<16:28:21.660> the 16:28:21.830 --> 16:28:21.840 align:start position:0% essential to managing and monitoring the 16:28:21.840 --> 16:28:23.150 align:start position:0% essential to managing and monitoring the network<16:28:22.020> without<16:28:22.436> them<16:28:22.740> there<16:28:22.980> really 16:28:23.150 --> 16:28:23.160 align:start position:0% network without them there really 16:28:23.160 --> 16:28:26.150 align:start position:0% network without them there really wouldn't<16:28:23.456> be<16:28:24.200> anyone<16:28:25.200> with<16:28:25.500> enough<16:28:25.680> knowledge 16:28:26.150 --> 16:28:26.160 align:start position:0% wouldn't be anyone with enough knowledge 16:28:26.160 --> 16:28:28.670 align:start position:0% wouldn't be anyone with enough knowledge or<16:28:26.400> ability<16:28:26.700> to<16:28:27.060> manage<16:28:27.416> how<16:28:27.776> these<16:28:28.200> networks 16:28:28.670 --> 16:28:28.680 align:start position:0% or ability to manage how these networks 16:28:28.680 --> 16:28:30.830 align:start position:0% or ability to manage how these networks and<16:28:28.916> you<16:28:29.340> can<16:28:29.400> see<16:28:29.640> how<16:28:30.000> large<16:28:30.240> they<16:28:30.660> get 16:28:30.830 --> 16:28:30.840 align:start position:0% and you can see how large they get 16:28:30.840 --> 16:28:32.030 align:start position:0% and you can see how large they get sometimes 16:28:32.030 --> 16:28:32.040 align:start position:0% sometimes 16:28:32.040 --> 16:28:34.310 align:start position:0% sometimes so<16:28:32.640> here<16:28:32.936> is<16:28:33.116> essentially<16:28:33.540> what<16:28:33.956> an 16:28:34.310 --> 16:28:34.320 align:start position:0% so here is essentially what an 16:28:34.320 --> 16:28:37.130 align:start position:0% so here is essentially what an administrator's<16:28:35.040> view<16:28:35.276> might<16:28:36.000> be<16:28:36.240> like<16:28:36.480> they 16:28:37.130 --> 16:28:37.140 align:start position:0% administrator's view might be like they 16:28:37.140 --> 16:28:38.570 align:start position:0% administrator's view might be like they have<16:28:37.320> a<16:28:37.436> view<16:28:37.616> of<16:28:37.796> everything<16:28:38.096> that<16:28:38.400> happens 16:28:38.570 --> 16:28:38.580 align:start position:0% have a view of everything that happens 16:28:38.580 --> 16:28:41.030 align:start position:0% have a view of everything that happens going<16:28:39.180> in<16:28:39.360> right<16:28:39.596> they<16:28:39.840> know<16:28:40.020> all<16:28:40.616> of<16:28:40.796> the 16:28:41.030 --> 16:28:41.040 align:start position:0% going in right they know all of the 16:28:41.040 --> 16:28:43.490 align:start position:0% going in right they know all of the nodes<16:28:41.400> all<16:28:42.296> of<16:28:42.416> the<16:28:42.660> servers<16:28:43.020> and<16:28:43.200> this<16:28:43.320> is 16:28:43.490 --> 16:28:43.500 align:start position:0% nodes all of the servers and this is 16:28:43.500 --> 16:28:45.530 align:start position:0% nodes all of the servers and this is very<16:28:43.740> simplified<16:28:44.160> all<16:28:44.880> of<16:28:45.000> the<16:28:45.060> routers<16:28:45.416> and 16:28:45.530 --> 16:28:45.540 align:start position:0% very simplified all of the routers and 16:28:45.540 --> 16:28:46.850 align:start position:0% very simplified all of the routers and switches<16:28:45.900> this<16:28:46.080> is<16:28:46.140> what<16:28:46.256> we<16:28:46.380> might<16:28:46.500> call<16:28:46.680> a 16:28:46.850 --> 16:28:46.860 align:start position:0% switches this is what we might call a 16:28:46.860 --> 16:28:49.310 align:start position:0% switches this is what we might call a network<16:28:47.160> diagram<16:28:47.700> we<16:28:48.480> might<16:28:48.660> also<16:28:48.956> have 16:28:49.310 --> 16:28:49.320 align:start position:0% network diagram we might also have 16:28:49.320 --> 16:28:51.350 align:start position:0% network diagram we might also have printers 16:28:51.350 --> 16:28:51.360 align:start position:0% printers 16:28:51.360 --> 16:28:54.350 align:start position:0% printers and<16:28:51.956> if<16:28:52.200> this<16:28:52.436> is<16:28:52.616> a<16:28:52.916> cloud<16:28:53.096> environment<16:28:53.756> as<16:28:54.116> it 16:28:54.350 --> 16:28:54.360 align:start position:0% and if this is a cloud environment as it 16:28:54.360 --> 16:28:56.330 align:start position:0% and if this is a cloud environment as it seems<16:28:54.660> to<16:28:54.840> be<16:28:55.020> then<16:28:55.796> they're<16:28:56.040> going<16:28:56.160> to<16:28:56.276> be 16:28:56.330 --> 16:28:56.340 align:start position:0% seems to be then they're going to be 16:28:56.340 --> 16:28:58.490 align:start position:0% seems to be then they're going to be aware<16:28:56.580> of<16:28:56.756> all<16:28:56.936> the<16:28:57.116> virtual<16:28:57.596> sort<16:28:58.080> of<16:28:58.200> stuff 16:28:58.490 --> 16:28:58.500 align:start position:0% aware of all the virtual sort of stuff 16:28:58.500 --> 16:29:01.010 align:start position:0% aware of all the virtual sort of stuff that<16:28:58.980> is<16:28:59.096> set<16:28:59.340> up 16:29:01.010 --> 16:29:01.020 align:start position:0% that is set up 16:29:01.020 --> 16:29:04.130 align:start position:0% that is set up they're<16:29:01.436> going<16:29:01.616> to<16:29:01.796> beware<16:29:02.160> of<16:29:03.116> all<16:29:03.540> of<16:29:03.660> the 16:29:04.130 --> 16:29:04.140 align:start position:0% they're going to beware of all of the 16:29:04.140 --> 16:29:07.150 align:start position:0% they're going to beware of all of the user<16:29:04.740> accounts 16:29:07.150 --> 16:29:07.160 align:start position:0% user accounts 16:29:07.160 --> 16:29:11.210 align:start position:0% user accounts the<16:29:08.160> network<16:29:08.400> security 16:29:11.210 --> 16:29:11.220 align:start position:0% 16:29:11.220 --> 16:29:13.730 align:start position:0% they're<16:29:11.700> also<16:29:12.000> going<16:29:12.060> to<16:29:12.240> be<16:29:12.560> dealing<16:29:13.560> with 16:29:13.730 --> 16:29:13.740 align:start position:0% they're also going to be dealing with 16:29:13.740 --> 16:29:17.510 align:start position:0% they're also going to be dealing with all<16:29:14.040> the<16:29:14.220> remote<16:29:14.520> access 16:29:17.510 --> 16:29:17.520 align:start position:0% 16:29:17.520 --> 16:29:20.086 align:start position:0% if<16:29:18.116> there<16:29:18.416> is<16:29:18.660> this<16:29:18.956> going<16:29:19.200> out<16:29:19.436> to<16:29:19.740> the 16:29:20.086 --> 16:29:20.096 align:start position:0% if there is this going out to the 16:29:20.096 --> 16:29:24.106 align:start position:0% if there is this going out to the internet<16:29:20.340> are<16:29:21.060> there<16:29:21.296> firewalls 16:29:24.106 --> 16:29:24.116 align:start position:0% internet are there firewalls 16:29:24.116 --> 16:29:28.070 align:start position:0% internet are there firewalls are<16:29:24.596> there<16:29:24.776> intrusion<16:29:25.436> systems<16:29:26.456> etc<16:29:27.060> etc<16:29:27.240> so 16:29:28.070 --> 16:29:28.080 align:start position:0% are there intrusion systems etc etc so 16:29:28.080 --> 16:29:29.510 align:start position:0% are there intrusion systems etc etc so they<16:29:28.256> really<16:29:28.436> have<16:29:28.740> an<16:29:28.980> overview<16:29:29.340> of 16:29:29.510 --> 16:29:29.520 align:start position:0% they really have an overview of 16:29:29.520 --> 16:29:30.946 align:start position:0% they really have an overview of everything<16:29:29.880> they<16:29:30.180> have<16:29:30.416> to<16:29:30.540> maintain 16:29:30.946 --> 16:29:30.956 align:start position:0% everything they have to maintain 16:29:30.956 --> 16:29:32.690 align:start position:0% everything they have to maintain everything<16:29:31.256> as<16:29:31.560> well<16:29:31.740> you<16:29:32.220> can<16:29:32.340> see<16:29:32.456> how 16:29:32.690 --> 16:29:32.700 align:start position:0% everything as well you can see how 16:29:32.700 --> 16:29:34.070 align:start position:0% everything as well you can see how complicated<16:29:33.116> this<16:29:33.360> can<16:29:33.480> get<16:29:33.596> which<16:29:33.776> is<16:29:33.956> the 16:29:34.070 --> 16:29:34.080 align:start position:0% complicated this can get which is the 16:29:34.080 --> 16:29:35.630 align:start position:0% complicated this can get which is the reason<16:29:34.200> why<16:29:34.500> one<16:29:34.740> network<16:29:35.040> administrator 16:29:35.630 --> 16:29:35.640 align:start position:0% reason why one network administrator 16:29:35.640 --> 16:29:37.906 align:start position:0% reason why one network administrator might<16:29:35.880> have<16:29:36.060> several<16:29:36.416> under<16:29:36.916> administrators 16:29:37.906 --> 16:29:37.916 align:start position:0% might have several under administrators 16:29:37.916 --> 16:29:41.086 align:start position:0% might have several under administrators to<16:29:38.160> help<16:29:38.340> them<16:29:38.640> they<16:29:39.480> not<16:29:39.840> only<16:29:40.020> log<16:29:40.616> when 16:29:41.086 --> 16:29:41.096 align:start position:0% to help them they not only log when 16:29:41.096 --> 16:29:42.830 align:start position:0% to help them they not only log when someone<16:29:41.400> comes<16:29:41.820> in<16:29:41.936> or<16:29:42.060> out<16:29:42.240> they<16:29:42.540> can<16:29:42.660> see 16:29:42.830 --> 16:29:42.840 align:start position:0% someone comes in or out they can see 16:29:42.840 --> 16:29:45.106 align:start position:0% someone comes in or out they can see when<16:29:43.140> someone<16:29:43.436> visits<16:29:44.096> a<16:29:44.276> specific<16:29:44.520> website 16:29:45.106 --> 16:29:45.116 align:start position:0% when someone visits a specific website 16:29:45.116 --> 16:29:47.210 align:start position:0% when someone visits a specific website when<16:29:46.020> they're<16:29:46.320> sending<16:29:46.680> or<16:29:46.796> where<16:29:47.040> they're 16:29:47.210 --> 16:29:47.220 align:start position:0% when they're sending or where they're 16:29:47.220 --> 16:29:50.210 align:start position:0% when they're sending or where they're sending<16:29:47.580> data<16:29:47.880> what<16:29:48.180> the<16:29:48.360> type<16:29:48.660> of<16:29:48.776> data<16:29:49.140> is<16:29:49.320> we 16:29:50.210 --> 16:29:50.220 align:start position:0% sending data what the type of data is we 16:29:50.220 --> 16:29:52.370 align:start position:0% sending data what the type of data is we might<16:29:50.340> also<16:29:50.700> have<16:29:50.936> for<16:29:51.296> instance<16:29:51.540> an<16:29:51.956> exchange 16:29:52.370 --> 16:29:52.380 align:start position:0% might also have for instance an exchange 16:29:52.380 --> 16:29:54.710 align:start position:0% might also have for instance an exchange server<16:29:52.796> which<16:29:53.040> would<16:29:53.220> be<16:29:53.340> for<16:29:53.580> email<16:29:53.880> in<16:29:54.596> which 16:29:54.710 --> 16:29:54.720 align:start position:0% server which would be for email in which 16:29:54.720 --> 16:29:56.446 align:start position:0% server which would be for email in which case<16:29:54.900> we<16:29:55.200> need<16:29:55.320> someone<16:29:55.500> to<16:29:55.796> manage<16:29:56.040> that<16:29:56.276> as 16:29:56.446 --> 16:29:56.456 align:start position:0% case we need someone to manage that as 16:29:56.456 --> 16:29:58.786 align:start position:0% case we need someone to manage that as well<16:29:56.640> for<16:29:57.240> instance<16:29:57.416> what<16:29:57.720> if<16:29:57.900> someone<16:29:58.200> sends 16:29:58.786 --> 16:29:58.796 align:start position:0% well for instance what if someone sends 16:29:58.796 --> 16:30:01.606 align:start position:0% well for instance what if someone sends a<16:29:59.040> 50<16:29:59.220> megabyte<16:29:59.936> or<16:30:00.116> 50<16:30:00.296> gigabyte<16:30:00.900> file<16:30:01.200> by 16:30:01.606 --> 16:30:01.616 align:start position:0% a 50 megabyte or 50 gigabyte file by 16:30:01.616 --> 16:30:03.650 align:start position:0% a 50 megabyte or 50 gigabyte file by email<16:30:01.860> or<16:30:02.096> they<16:30:02.340> try<16:30:02.580> to<16:30:02.756> that's<16:30:03.296> going<16:30:03.480> to<16:30:03.540> log 16:30:03.650 --> 16:30:03.660 align:start position:0% email or they try to that's going to log 16:30:03.660 --> 16:30:05.570 align:start position:0% email or they try to that's going to log up<16:30:03.900> the<16:30:04.140> entire<16:30:04.436> network 16:30:05.570 --> 16:30:05.580 align:start position:0% up the entire network 16:30:05.580 --> 16:30:07.850 align:start position:0% up the entire network so<16:30:06.240> one<16:30:06.540> of<16:30:06.660> the<16:30:06.776> first<16:30:07.020> duties<16:30:07.500> of<16:30:07.740> an 16:30:07.850 --> 16:30:07.860 align:start position:0% so one of the first duties of an 16:30:07.860 --> 16:30:09.890 align:start position:0% so one of the first duties of an administrator<16:30:08.276> is<16:30:08.580> documentation<16:30:09.240> there's<16:30:09.720> a 16:30:09.890 --> 16:30:09.900 align:start position:0% administrator is documentation there's a 16:30:09.900 --> 16:30:12.170 align:start position:0% administrator is documentation there's a couple<16:30:10.020> reasons<16:30:10.500> why<16:30:10.860> this<16:30:11.220> is<16:30:11.400> so<16:30:11.700> important 16:30:12.170 --> 16:30:12.180 align:start position:0% couple reasons why this is so important 16:30:12.180 --> 16:30:15.650 align:start position:0% couple reasons why this is so important when<16:30:12.900> it<16:30:13.080> comes<16:30:13.380> to<16:30:13.680> managing<16:30:14.340> and<16:30:15.116> running<16:30:15.416> a 16:30:15.650 --> 16:30:15.660 align:start position:0% when it comes to managing and running a 16:30:15.660 --> 16:30:17.926 align:start position:0% when it comes to managing and running a network<16:30:15.840> it's<16:30:16.616> going<16:30:16.796> to<16:30:16.796> be<16:30:16.916> the<16:30:17.040> focus<16:30:17.400> of 16:30:17.926 --> 16:30:17.936 align:start position:0% network it's going to be the focus of 16:30:17.936 --> 16:30:19.786 align:start position:0% network it's going to be the focus of its<16:30:18.360> own<16:30:18.416> module<16:30:18.900> but<16:30:19.140> it's<16:30:19.256> good<16:30:19.436> to<16:30:19.560> get<16:30:19.680> a 16:30:19.786 --> 16:30:19.796 align:start position:0% its own module but it's good to get a 16:30:19.796 --> 16:30:21.530 align:start position:0% its own module but it's good to get a basic<16:30:20.096> understanding<16:30:20.580> right<16:30:20.820> now<16:30:21.000> because 16:30:21.530 --> 16:30:21.540 align:start position:0% basic understanding right now because 16:30:21.540 --> 16:30:23.150 align:start position:0% basic understanding right now because the<16:30:21.900> process<16:30:22.200> of<16:30:22.500> documenting<16:30:22.980> everything 16:30:23.150 --> 16:30:23.160 align:start position:0% the process of documenting everything 16:30:23.160 --> 16:30:25.246 align:start position:0% the process of documenting everything can<16:30:23.520> be<16:30:23.756> really<16:30:24.060> time<16:30:24.416> consuming<16:30:24.840> but<16:30:25.080> it's 16:30:25.246 --> 16:30:25.256 align:start position:0% can be really time consuming but it's 16:30:25.256 --> 16:30:27.286 align:start position:0% can be really time consuming but it's also<16:30:25.560> really<16:30:25.740> worth<16:30:26.040> it<16:30:26.220> can<16:30:26.640> save<16:30:26.880> you<16:30:27.000> a<16:30:27.180> lot 16:30:27.286 --> 16:30:27.296 align:start position:0% also really worth it can save you a lot 16:30:27.296 --> 16:30:29.266 align:start position:0% also really worth it can save you a lot of<16:30:27.416> time<16:30:27.596> trouble<16:30:28.020> and<16:30:28.320> money<16:30:28.560> when<16:30:29.096> things 16:30:29.266 --> 16:30:29.276 align:start position:0% of time trouble and money when things 16:30:29.276 --> 16:30:31.246 align:start position:0% of time trouble and money when things are<16:30:29.456> well<16:30:29.700> documented<16:30:30.360> and<16:30:30.480> no<16:30:30.660> one<16:30:30.776> has<16:30:30.956> to<16:30:31.140> go 16:30:31.246 --> 16:30:31.256 align:start position:0% are well documented and no one has to go 16:30:31.256 --> 16:30:33.710 align:start position:0% are well documented and no one has to go searching<16:30:31.740> for<16:30:32.040> them<16:30:32.240> especially<16:30:33.240> if<16:30:33.480> the 16:30:33.710 --> 16:30:33.720 align:start position:0% searching for them especially if the 16:30:33.720 --> 16:30:35.810 align:start position:0% searching for them especially if the administrator<16:30:34.140> is<16:30:34.380> out<16:30:34.616> of<16:30:34.740> town<16:30:34.916> or<16:30:35.456> if<16:30:35.640> we 16:30:35.810 --> 16:30:35.820 align:start position:0% administrator is out of town or if we 16:30:35.820 --> 16:30:37.190 align:start position:0% administrator is out of town or if we switch<16:30:36.000> administrators<16:30:36.720> we<16:30:36.900> want<16:30:37.020> to<16:30:37.140> make 16:30:37.190 --> 16:30:37.200 align:start position:0% switch administrators we want to make 16:30:37.200 --> 16:30:38.926 align:start position:0% switch administrators we want to make sure<16:30:37.320> that<16:30:37.560> the<16:30:37.740> network<16:30:37.916> can<16:30:38.340> still<16:30:38.520> live<16:30:38.756> on 16:30:38.926 --> 16:30:38.936 align:start position:0% sure that the network can still live on 16:30:38.936 --> 16:30:40.906 align:start position:0% sure that the network can still live on its<16:30:39.240> own<16:30:39.296> now<16:30:39.956> there<16:30:40.200> are<16:30:40.320> no<16:30:40.436> shortage<16:30:40.740> of 16:30:40.906 --> 16:30:40.916 align:start position:0% its own now there are no shortage of 16:30:40.916 --> 16:30:42.286 align:start position:0% its own now there are no shortage of things<16:30:41.040> to<16:30:41.276> handle<16:30:41.520> for<16:30:41.756> the<16:30:41.880> administrator 16:30:42.286 --> 16:30:42.296 align:start position:0% things to handle for the administrator 16:30:42.296 --> 16:30:45.286 align:start position:0% things to handle for the administrator and<16:30:42.540> documentation<16:30:43.200> is<16:30:43.560> OB<16:30:44.160> usually<16:30:45.060> the 16:30:45.286 --> 16:30:45.296 align:start position:0% and documentation is OB usually the 16:30:45.296 --> 16:30:47.150 align:start position:0% and documentation is OB usually the thing<16:30:45.540> that's<16:30:45.956> going<16:30:46.200> to<16:30:46.256> get<16:30:46.436> pushed<16:30:46.860> aside 16:30:47.150 --> 16:30:47.160 align:start position:0% thing that's going to get pushed aside 16:30:47.160 --> 16:30:49.010 align:start position:0% thing that's going to get pushed aside and<16:30:47.340> forgotten<16:30:47.820> about<16:30:48.000> but<16:30:48.660> there<16:30:48.840> are<16:30:48.956> some 16:30:49.010 --> 16:30:49.020 align:start position:0% and forgotten about but there are some 16:30:49.020 --> 16:30:51.586 align:start position:0% and forgotten about but there are some really<16:30:49.200> key<16:30:49.500> items<16:30:49.916> that<16:30:50.456> we<16:30:50.820> can<16:30:50.936> look<16:30:51.360> over 16:30:51.586 --> 16:30:51.596 align:start position:0% really key items that we can look over 16:30:51.596 --> 16:30:54.050 align:start position:0% really key items that we can look over that<16:30:51.900> are<16:30:52.080> helpful<16:30:52.380> to<16:30:52.560> be<16:30:52.680> dealt<16:30:53.276> with<16:30:53.340> first 16:30:54.050 --> 16:30:54.060 align:start position:0% that are helpful to be dealt with first 16:30:54.060 --> 16:30:55.926 align:start position:0% that are helpful to be dealt with first of<16:30:54.240> all<16:30:54.296> properly<16:30:54.776> documenting<16:30:55.560> information 16:30:55.926 --> 16:30:55.936 align:start position:0% of all properly documenting information 16:30:55.936 --> 16:30:59.446 align:start position:0% of all properly documenting information is<16:30:56.936> useful<16:30:57.360> when<16:30:57.660> training<16:30:58.140> new<16:30:58.380> admins<16:30:58.916> it's 16:30:59.446 --> 16:30:59.456 align:start position:0% is useful when training new admins it's 16:30:59.456 --> 16:31:00.890 align:start position:0% is useful when training new admins it's not<16:30:59.640> uncommon<16:31:00.000> for<16:31:00.180> the<16:31:00.296> old<16:31:00.416> administrator 16:31:00.890 --> 16:31:00.900 align:start position:0% not uncommon for the old administrator 16:31:00.900 --> 16:31:03.050 align:start position:0% not uncommon for the old administrator to<16:31:01.200> leave<16:31:01.380> and<16:31:01.980> then<16:31:02.096> have<16:31:02.340> to<16:31:02.520> train<16:31:02.700> a<16:31:02.880> new 16:31:03.050 --> 16:31:03.060 align:start position:0% to leave and then have to train a new 16:31:03.060 --> 16:31:04.730 align:start position:0% to leave and then have to train a new one<16:31:03.180> is<16:31:03.296> their<16:31:03.540> replacement<16:31:03.776> however<16:31:04.436> the<16:31:04.616> new 16:31:04.730 --> 16:31:04.740 align:start position:0% one is their replacement however the new 16:31:04.740 --> 16:31:06.050 align:start position:0% one is their replacement however the new admin<16:31:05.040> doesn't<16:31:05.160> have<16:31:05.276> time<16:31:05.400> to<16:31:05.520> learn<16:31:05.880> the 16:31:06.050 --> 16:31:06.060 align:start position:0% admin doesn't have time to learn the 16:31:06.060 --> 16:31:07.670 align:start position:0% admin doesn't have time to learn the topography<16:31:06.660> the<16:31:06.840> cable<16:31:07.080> connections 16:31:07.670 --> 16:31:07.680 align:start position:0% topography the cable connections 16:31:07.680 --> 16:31:09.050 align:start position:0% topography the cable connections everything<16:31:08.220> about<16:31:08.456> the<16:31:08.640> network<16:31:08.756> from 16:31:09.050 --> 16:31:09.060 align:start position:0% everything about the network from 16:31:09.060 --> 16:31:10.426 align:start position:0% everything about the network from scratch<16:31:09.296> so<16:31:09.540> this<16:31:09.720> is<16:31:09.776> where<16:31:10.020> proper 16:31:10.426 --> 16:31:10.436 align:start position:0% scratch so this is where proper 16:31:10.436 --> 16:31:12.710 align:start position:0% scratch so this is where proper documentation<16:31:11.040> is<16:31:11.340> really<16:31:11.580> helpful<16:31:12.000> it<16:31:12.540> can 16:31:12.710 --> 16:31:12.720 align:start position:0% documentation is really helpful it can 16:31:12.720 --> 16:31:14.446 align:start position:0% documentation is really helpful it can save<16:31:12.900> the<16:31:13.080> new<16:31:13.256> administrator<16:31:13.796> a<16:31:14.160> lot<16:31:14.220> of<16:31:14.340> time 16:31:14.446 --> 16:31:14.456 align:start position:0% save the new administrator a lot of time 16:31:14.456 --> 16:31:16.786 align:start position:0% save the new administrator a lot of time and<16:31:14.640> effort<16:31:14.936> especially<16:31:15.720> if<16:31:16.080> even<16:31:16.500> if<16:31:16.740> you're 16:31:16.786 --> 16:31:16.796 align:start position:0% and effort especially if even if you're 16:31:16.796 --> 16:31:18.586 align:start position:0% and effort especially if even if you're not<16:31:16.980> leaving<16:31:17.220> if<16:31:17.756> you<16:31:17.880> bring<16:31:18.060> on<16:31:18.180> someone<16:31:18.360> to 16:31:18.586 --> 16:31:18.596 align:start position:0% not leaving if you bring on someone to 16:31:18.596 --> 16:31:20.086 align:start position:0% not leaving if you bring on someone to assist<16:31:18.776> you<16:31:19.080> allowing<16:31:19.616> them<16:31:19.680> to<16:31:19.860> look<16:31:19.980> at 16:31:20.086 --> 16:31:20.096 align:start position:0% assist you allowing them to look at 16:31:20.096 --> 16:31:22.670 align:start position:0% assist you allowing them to look at documentation<16:31:20.640> is<16:31:20.936> going<16:31:21.060> to<16:31:21.116> save<16:31:21.296> the<16:31:22.080> super 16:31:22.670 --> 16:31:22.680 align:start position:0% documentation is going to save the super 16:31:22.680 --> 16:31:24.470 align:start position:0% documentation is going to save the super administrator<16:31:23.276> time<16:31:23.520> from<16:31:23.756> having<16:31:24.000> to<16:31:24.296> teach 16:31:24.470 --> 16:31:24.480 align:start position:0% administrator time from having to teach 16:31:24.480 --> 16:31:26.086 align:start position:0% administrator time from having to teach the<16:31:24.720> new<16:31:24.900> administrator 16:31:26.086 --> 16:31:26.096 align:start position:0% the new administrator 16:31:26.096 --> 16:31:28.850 align:start position:0% the new administrator it's<16:31:26.580> also<16:31:26.936> going<16:31:27.480> to<16:31:27.720> help<16:31:27.956> us<16:31:28.140> when<16:31:28.616> we 16:31:28.850 --> 16:31:28.860 align:start position:0% it's also going to help us when we 16:31:28.860 --> 16:31:31.190 align:start position:0% it's also going to help us when we troubleshoot<16:31:29.640> problems<16:31:30.180> on<16:31:30.360> the<16:31:30.480> network<16:31:30.596> it 16:31:31.190 --> 16:31:31.200 align:start position:0% troubleshoot problems on the network it 16:31:31.200 --> 16:31:32.810 align:start position:0% troubleshoot problems on the network it can<16:31:31.320> save<16:31:31.500> time<16:31:31.860> and<16:31:32.040> money<16:31:32.220> because<16:31:32.456> we<16:31:32.700> can 16:31:32.810 --> 16:31:32.820 align:start position:0% can save time and money because we can 16:31:32.820 --> 16:31:34.370 align:start position:0% can save time and money because we can eliminate<16:31:33.180> the<16:31:33.360> time<16:31:33.540> it<16:31:33.776> takes<16:31:33.900> to<16:31:34.200> test 16:31:34.370 --> 16:31:34.380 align:start position:0% eliminate the time it takes to test 16:31:34.380 --> 16:31:36.830 align:start position:0% eliminate the time it takes to test every<16:31:34.860> possible<16:31:35.276> problem<16:31:35.640> because<16:31:36.296> we<16:31:36.720> can 16:31:36.830 --> 16:31:36.840 align:start position:0% every possible problem because we can 16:31:36.840 --> 16:31:38.630 align:start position:0% every possible problem because we can now<16:31:37.080> isolate<16:31:37.616> where<16:31:37.796> the<16:31:37.980> potential<16:31:38.276> problems 16:31:38.630 --> 16:31:38.640 align:start position:0% now isolate where the potential problems 16:31:38.640 --> 16:31:40.970 align:start position:0% now isolate where the potential problems are<16:31:38.936> for<16:31:39.596> instance<16:31:39.840> if<16:31:40.080> I<16:31:40.256> have<16:31:40.380> an<16:31:40.616> overview 16:31:40.970 --> 16:31:40.980 align:start position:0% are for instance if I have an overview 16:31:40.980 --> 16:31:43.190 align:start position:0% are for instance if I have an overview of<16:31:41.276> where<16:31:41.640> things<16:31:41.880> are<16:31:42.296> set<16:31:42.776> on<16:31:43.020> the<16:31:43.080> network 16:31:43.190 --> 16:31:43.200 align:start position:0% of where things are set on the network 16:31:43.200 --> 16:31:44.690 align:start position:0% of where things are set on the network and<16:31:43.436> I<16:31:43.616> know<16:31:43.680> one<16:31:43.916> side<16:31:44.040> of<16:31:44.220> the<16:31:44.220> Network's<16:31:44.520> not 16:31:44.690 --> 16:31:44.700 align:start position:0% and I know one side of the Network's not 16:31:44.700 --> 16:31:46.786 align:start position:0% and I know one side of the Network's not working<16:31:44.880> then<16:31:45.480> I<16:31:45.720> can<16:31:45.840> automatically<16:31:46.436> sort<16:31:46.740> of 16:31:46.786 --> 16:31:46.796 align:start position:0% working then I can automatically sort of 16:31:46.796 --> 16:31:48.230 align:start position:0% working then I can automatically sort of go<16:31:46.980> to<16:31:47.096> that<16:31:47.276> side<16:31:47.456> of<16:31:47.640> the<16:31:47.700> network<16:31:47.820> and<16:31:48.116> not 16:31:48.230 --> 16:31:48.240 align:start position:0% go to that side of the network and not 16:31:48.240 --> 16:31:49.550 align:start position:0% go to that side of the network and not have<16:31:48.416> to<16:31:48.540> worry<16:31:48.660> about<16:31:48.840> the<16:31:49.140> other<16:31:49.256> side 16:31:49.550 --> 16:31:49.560 align:start position:0% have to worry about the other side 16:31:49.560 --> 16:31:52.606 align:start position:0% have to worry about the other side finally<16:31:50.520> it's<16:31:50.936> also<16:31:51.296> really<16:31:51.540> important<16:31:52.020> when 16:31:52.606 --> 16:31:52.616 align:start position:0% finally it's also really important when 16:31:52.616 --> 16:31:55.490 align:start position:0% finally it's also really important when I'm<16:31:53.000> bringing<16:31:54.000> in<16:31:54.116> outside<16:31:54.480> workers<16:31:55.080> to<16:31:55.320> make 16:31:55.490 --> 16:31:55.500 align:start position:0% I'm bringing in outside workers to make 16:31:55.500 --> 16:31:57.106 align:start position:0% I'm bringing in outside workers to make changes<16:31:55.916> to<16:31:56.096> the<16:31:56.220> network<16:31:56.340> they<16:31:56.936> need 16:31:57.106 --> 16:31:57.116 align:start position:0% changes to the network they need 16:31:57.116 --> 16:31:58.310 align:start position:0% changes to the network they need accurate<16:31:57.540> and<16:31:57.660> up-to-date<16:31:58.080> information 16:31:58.310 --> 16:31:58.320 align:start position:0% accurate and up-to-date information 16:31:58.320 --> 16:32:02.926 align:start position:0% accurate and up-to-date information about<16:31:59.276> the<16:31:59.640> network<16:31:59.820> its<16:32:00.660> layout<16:32:01.020> and<16:32:01.796> if 16:32:02.926 --> 16:32:02.936 align:start position:0% about the network its layout and if 16:32:02.936 --> 16:32:05.210 align:start position:0% about the network its layout and if they<16:32:03.720> don't<16:32:03.900> have<16:32:04.200> an<16:32:04.436> idea<16:32:04.680> of<16:32:04.796> how<16:32:05.040> my 16:32:05.210 --> 16:32:05.220 align:start position:0% they don't have an idea of how my 16:32:05.220 --> 16:32:06.946 align:start position:0% they don't have an idea of how my network<16:32:05.340> looks<16:32:05.936> and<16:32:06.180> I<16:32:06.296> just<16:32:06.480> start<16:32:06.660> to<16:32:06.776> tell 16:32:06.946 --> 16:32:06.956 align:start position:0% network looks and I just start to tell 16:32:06.956 --> 16:32:08.810 align:start position:0% network looks and I just start to tell them<16:32:07.080> to<16:32:07.436> fix<16:32:07.740> things<16:32:08.040> they're<16:32:08.400> going<16:32:08.580> to<16:32:08.700> have 16:32:08.810 --> 16:32:08.820 align:start position:0% them to fix things they're going to have 16:32:08.820 --> 16:32:10.130 align:start position:0% them to fix things they're going to have major<16:32:09.116> issues<16:32:09.540> and<16:32:09.720> one<16:32:09.900> of<16:32:10.020> the<16:32:10.080> things 16:32:10.130 --> 16:32:10.140 align:start position:0% major issues and one of the things 16:32:10.140 --> 16:32:12.710 align:start position:0% major issues and one of the things that's<16:32:10.320> really<16:32:10.616> big<16:32:10.860> these<16:32:11.276> days<16:32:11.400> is<16:32:12.060> having<16:32:12.296> a 16:32:12.710 --> 16:32:12.720 align:start position:0% that's really big these days is having a 16:32:12.720 --> 16:32:14.870 align:start position:0% that's really big these days is having a contractor<16:32:13.140> come<16:32:13.500> in<16:32:13.680> because<16:32:14.220> we're<16:32:14.580> sort<16:32:14.756> of 16:32:14.870 --> 16:32:14.880 align:start position:0% contractor come in because we're sort of 16:32:14.880 --> 16:32:16.730 align:start position:0% contractor come in because we're sort of going<16:32:15.000> to<16:32:15.180> Outsource<16:32:15.776> a<16:32:16.020> lot<16:32:16.200> of<16:32:16.380> our<16:32:16.560> network 16:32:16.730 --> 16:32:16.740 align:start position:0% going to Outsource a lot of our network 16:32:16.740 --> 16:32:18.830 align:start position:0% going to Outsource a lot of our network administrator<16:32:17.400> duties<16:32:17.880> or<16:32:18.296> sometimes<16:32:18.660> the 16:32:18.830 --> 16:32:18.840 align:start position:0% administrator duties or sometimes the 16:32:18.840 --> 16:32:21.650 align:start position:0% administrator duties or sometimes the administrator<16:32:19.380> is<16:32:19.796> not<16:32:20.096> a<16:32:20.880> specialist<16:32:21.480> in 16:32:21.650 --> 16:32:21.660 align:start position:0% administrator is not a specialist in 16:32:21.660 --> 16:32:23.330 align:start position:0% administrator is not a specialist in something<16:32:21.900> Sprints<16:32:22.560> in<16:32:22.616> security<16:32:22.796> and<16:32:23.220> so 16:32:23.330 --> 16:32:23.340 align:start position:0% something Sprints in security and so 16:32:23.340 --> 16:32:24.710 align:start position:0% something Sprints in security and so they<16:32:23.400> need<16:32:23.580> to<16:32:23.700> bring<16:32:23.756> in<16:32:23.936> contractors<16:32:24.480> to 16:32:24.710 --> 16:32:24.720 align:start position:0% they need to bring in contractors to 16:32:24.720 --> 16:32:27.170 align:start position:0% they need to bring in contractors to implement<16:32:25.020> a<16:32:25.256> better<16:32:25.436> security<16:32:25.740> plan 16:32:27.170 --> 16:32:27.180 align:start position:0% implement a better security plan 16:32:27.180 --> 16:32:29.330 align:start position:0% implement a better security plan now<16:32:27.660> monitoring<16:32:28.320> is<16:32:28.616> also<16:32:28.916> an<16:32:29.096> extremely 16:32:29.330 --> 16:32:29.340 align:start position:0% now monitoring is also an extremely 16:32:29.340 --> 16:32:30.946 align:start position:0% now monitoring is also an extremely important<16:32:29.456> job<16:32:29.820> for<16:32:30.060> the<16:32:30.180> administrator<16:32:30.660> it's 16:32:30.946 --> 16:32:30.956 align:start position:0% important job for the administrator it's 16:32:30.956 --> 16:32:32.926 align:start position:0% important job for the administrator it's necessary<16:32:31.436> to<16:32:31.680> monitor<16:32:31.980> a<16:32:32.160> network<16:32:32.340> for<16:32:32.640> a<16:32:32.820> lot 16:32:32.926 --> 16:32:32.936 align:start position:0% necessary to monitor a network for a lot 16:32:32.936 --> 16:32:34.606 align:start position:0% necessary to monitor a network for a lot of<16:32:33.060> reasons<16:32:33.480> and<16:32:33.776> again<16:32:33.956> we're<16:32:34.140> going<16:32:34.320> to<16:32:34.380> talk 16:32:34.606 --> 16:32:34.616 align:start position:0% of reasons and again we're going to talk 16:32:34.616 --> 16:32:36.710 align:start position:0% of reasons and again we're going to talk talk<16:32:34.916> about<16:32:35.160> this<16:32:35.456> in<16:32:35.756> its<16:32:36.060> own<16:32:36.116> module<16:32:36.540> but 16:32:36.710 --> 16:32:36.720 align:start position:0% talk about this in its own module but 16:32:36.720 --> 16:32:38.086 align:start position:0% talk about this in its own module but it's<16:32:36.840> good<16:32:37.080> to<16:32:37.200> understand<16:32:37.380> it<16:32:37.740> a<16:32:37.860> little<16:32:37.980> bit 16:32:38.086 --> 16:32:38.096 align:start position:0% it's good to understand it a little bit 16:32:38.096 --> 16:32:40.870 align:start position:0% it's good to understand it a little bit right<16:32:38.340> now<16:32:38.520> so<16:32:39.180> when<16:32:39.296> you<16:32:39.480> monitor<16:32:39.956> a<16:32:40.320> network 16:32:40.870 --> 16:32:40.880 align:start position:0% right now so when you monitor a network 16:32:40.880 --> 16:32:43.730 align:start position:0% right now so when you monitor a network the<16:32:41.880> administrator<16:32:42.480> can<16:32:42.720> almost<16:32:42.900> always<16:32:43.256> find 16:32:43.730 --> 16:32:43.740 align:start position:0% the administrator can almost always find 16:32:43.740 --> 16:32:45.650 align:start position:0% the administrator can almost always find faults<16:32:44.400> in<16:32:44.520> the<16:32:44.640> system<16:32:44.820> and<16:32:45.116> find<16:32:45.296> out<16:32:45.416> where 16:32:45.650 --> 16:32:45.660 align:start position:0% faults in the system and find out where 16:32:45.660 --> 16:32:47.446 align:start position:0% faults in the system and find out where they<16:32:45.900> are<16:32:46.140> there<16:32:46.680> are<16:32:46.860> tools<16:32:47.040> that<16:32:47.160> help<16:32:47.276> the 16:32:47.446 --> 16:32:47.456 align:start position:0% they are there are tools that help the 16:32:47.456 --> 16:32:49.550 align:start position:0% they are there are tools that help the administrator<16:32:47.936> check<16:32:48.240> all<16:32:48.416> the<16:32:48.596> devices<16:32:48.840> to 16:32:49.550 --> 16:32:49.560 align:start position:0% administrator check all the devices to 16:32:49.560 --> 16:32:50.690 align:start position:0% administrator check all the devices to find<16:32:49.680> out<16:32:49.796> where<16:32:49.980> the<16:32:50.096> faults<16:32:50.400> are<16:32:50.456> and<16:32:50.580> how 16:32:50.690 --> 16:32:50.700 align:start position:0% find out where the faults are and how 16:32:50.700 --> 16:32:51.890 align:start position:0% find out where the faults are and how they<16:32:50.820> can<16:32:50.936> be<16:32:51.060> fixed<16:32:51.296> and<16:32:51.360> I<16:32:51.540> think<16:32:51.660> we've 16:32:51.890 --> 16:32:51.900 align:start position:0% they can be fixed and I think we've 16:32:51.900 --> 16:32:53.210 align:start position:0% they can be fixed and I think we've looked<16:32:52.200> at<16:32:52.320> some<16:32:52.500> of<16:32:52.616> those<16:32:52.740> and<16:32:52.916> we<16:32:53.040> might 16:32:53.210 --> 16:32:53.220 align:start position:0% looked at some of those and we might 16:32:53.220 --> 16:32:55.190 align:start position:0% looked at some of those and we might look<16:32:53.340> at<16:32:53.456> it<16:32:53.580> a<16:32:53.756> couple<16:32:53.820> more<16:32:54.060> but<16:32:54.776> some<16:32:54.956> of<16:32:55.080> the 16:32:55.190 --> 16:32:55.200 align:start position:0% look at it a couple more but some of the 16:32:55.200 --> 16:32:58.070 align:start position:0% look at it a couple more but some of the tools<16:32:55.560> the<16:32:55.796> Ping<16:32:56.096> trace<16:32:56.580> route<16:32:57.240> Etc<16:32:57.416> looking 16:32:58.070 --> 16:32:58.080 align:start position:0% tools the Ping trace route Etc looking 16:32:58.080 --> 16:33:00.070 align:start position:0% tools the Ping trace route Etc looking at<16:32:58.256> routing<16:32:58.680> tables<16:32:59.040> looking<16:32:59.400> at<16:32:59.640> broadcast 16:33:00.070 --> 16:33:00.080 align:start position:0% at routing tables looking at broadcast 16:33:00.080 --> 16:33:02.926 align:start position:0% at routing tables looking at broadcast all<16:33:01.080> this<16:33:01.256> stuff<16:33:01.436> and<16:33:02.220> also<16:33:02.400> performance 16:33:02.926 --> 16:33:02.936 align:start position:0% all this stuff and also performance 16:33:02.936 --> 16:33:05.446 align:start position:0% all this stuff and also performance detection<16:33:03.416> is<16:33:03.956> very<16:33:04.380> important<16:33:04.860> when<16:33:05.340> we're 16:33:05.446 --> 16:33:05.456 align:start position:0% detection is very important when we're 16:33:05.456 --> 16:33:07.370 align:start position:0% detection is very important when we're involved<16:33:05.820> with<16:33:05.936> network<16:33:06.116> monitoring<16:33:06.720> when<16:33:07.200> an 16:33:07.370 --> 16:33:07.380 align:start position:0% involved with network monitoring when an 16:33:07.380 --> 16:33:08.870 align:start position:0% involved with network monitoring when an administrator<16:33:07.796> monitors<16:33:08.220> performance 16:33:08.870 --> 16:33:08.880 align:start position:0% administrator monitors performance 16:33:08.880 --> 16:33:10.730 align:start position:0% administrator monitors performance they're<16:33:09.240> able<16:33:09.480> to<16:33:09.596> find<16:33:09.720> some<16:33:10.140> very<16:33:10.380> useful 16:33:10.730 --> 16:33:10.740 align:start position:0% they're able to find some very useful 16:33:10.740 --> 16:33:12.710 align:start position:0% they're able to find some very useful data<16:33:11.160> they<16:33:11.520> can<16:33:11.640> discover<16:33:11.756> Network<16:33:12.180> usage 16:33:12.710 --> 16:33:12.720 align:start position:0% data they can discover Network usage 16:33:12.720 --> 16:33:14.926 align:start position:0% data they can discover Network usage data<16:33:13.080> how<16:33:13.320> each<16:33:13.560> user<16:33:13.980> has<16:33:14.160> been<16:33:14.340> using<16:33:14.756> the 16:33:14.926 --> 16:33:14.936 align:start position:0% data how each user has been using the 16:33:14.936 --> 16:33:16.850 align:start position:0% data how each user has been using the network<16:33:15.060> and<16:33:15.660> make<16:33:15.840> sure<16:33:15.956> that<16:33:16.200> the<16:33:16.380> bandwidth 16:33:16.850 --> 16:33:16.860 align:start position:0% network and make sure that the bandwidth 16:33:16.860 --> 16:33:20.446 align:start position:0% network and make sure that the bandwidth is<16:33:16.980> load<16:33:17.340> balanced<16:33:17.756> properly<16:33:18.320> a<16:33:19.320> term<16:33:19.740> that<16:33:20.096> we 16:33:20.446 --> 16:33:20.456 align:start position:0% is load balanced properly a term that we 16:33:20.456 --> 16:33:22.190 align:start position:0% is load balanced properly a term that we have<16:33:20.700> seen<16:33:21.000> a<16:33:21.180> bit<16:33:21.296> and<16:33:21.720> we're<16:33:21.900> probably<16:33:22.080> going 16:33:22.190 --> 16:33:22.200 align:start position:0% have seen a bit and we're probably going 16:33:22.200 --> 16:33:23.870 align:start position:0% have seen a bit and we're probably going to<16:33:22.320> see<16:33:22.436> a<16:33:22.560> little<16:33:22.616> more 16:33:23.870 --> 16:33:23.880 align:start position:0% to see a little more 16:33:23.880 --> 16:33:26.690 align:start position:0% to see a little more and<16:33:24.540> also<16:33:24.840> we<16:33:25.020> can<16:33:25.140> make<16:33:25.380> sure<16:33:25.680> that<16:33:26.400> nothing 16:33:26.690 --> 16:33:26.700 align:start position:0% and also we can make sure that nothing 16:33:26.700 --> 16:33:28.490 align:start position:0% and also we can make sure that nothing if<16:33:27.000> there's<16:33:27.180> not<16:33:27.360> too<16:33:27.596> much<16:33:27.720> traffic<16:33:28.020> on<16:33:28.380> the 16:33:28.490 --> 16:33:28.500 align:start position:0% if there's not too much traffic on the 16:33:28.500 --> 16:33:30.406 align:start position:0% if there's not too much traffic on the system<16:33:28.680> obviously<16:33:29.276> too<16:33:29.456> much<16:33:29.580> traffic<16:33:29.820> slows 16:33:30.406 --> 16:33:30.416 align:start position:0% system obviously too much traffic slows 16:33:30.416 --> 16:33:32.170 align:start position:0% system obviously too much traffic slows things<16:33:30.596> down<16:33:30.840> and<16:33:31.080> makes<16:33:31.320> everyone<16:33:31.560> miserable 16:33:32.170 --> 16:33:32.180 align:start position:0% things down and makes everyone miserable 16:33:32.180 --> 16:33:35.150 align:start position:0% things down and makes everyone miserable finally<16:33:33.180> security<16:33:33.660> monitoring<16:33:34.380> is<16:33:34.796> really 16:33:35.150 --> 16:33:35.160 align:start position:0% finally security monitoring is really 16:33:35.160 --> 16:33:38.446 align:start position:0% finally security monitoring is really essential<16:33:35.700> because<16:33:36.560> uh<16:33:37.560> one<16:33:37.916> thing<16:33:38.040> we<16:33:38.340> don't 16:33:38.446 --> 16:33:38.456 align:start position:0% essential because uh one thing we don't 16:33:38.456 --> 16:33:40.070 align:start position:0% essential because uh one thing we don't want<16:33:38.700> is<16:33:38.880> someone<16:33:39.180> outside<16:33:39.540> of<16:33:39.840> our<16:33:39.956> Network 16:33:40.070 --> 16:33:40.080 align:start position:0% want is someone outside of our Network 16:33:40.080 --> 16:33:41.630 align:start position:0% want is someone outside of our Network getting<16:33:40.380> access<16:33:40.616> to<16:33:40.916> all<16:33:41.096> the<16:33:41.220> stuff<16:33:41.340> we<16:33:41.456> set 16:33:41.630 --> 16:33:41.640 align:start position:0% getting access to all the stuff we set 16:33:41.640 --> 16:33:42.946 align:start position:0% getting access to all the stuff we set up<16:33:41.756> it's<16:33:41.880> really<16:33:42.060> going<16:33:42.180> to<16:33:42.296> make<16:33:42.416> your<16:33:42.540> bosses 16:33:42.946 --> 16:33:42.956 align:start position:0% up it's really going to make your bosses 16:33:42.956 --> 16:33:44.510 align:start position:0% up it's really going to make your bosses upset<16:33:43.380> too<16:33:43.560> and<16:33:43.916> we're<16:33:44.096> not<16:33:44.220> just<16:33:44.340> talking 16:33:44.510 --> 16:33:44.520 align:start position:0% upset too and we're not just talking 16:33:44.520 --> 16:33:45.650 align:start position:0% upset too and we're not just talking about<16:33:44.700> hackers<16:33:45.180> we're<16:33:45.296> talking<16:33:45.480> about 16:33:45.650 --> 16:33:45.660 align:start position:0% about hackers we're talking about 16:33:45.660 --> 16:33:48.406 align:start position:0% about hackers we're talking about viruses<16:33:46.256> attackers<16:33:46.860> any<16:33:47.520> of<16:33:47.700> this<16:33:47.820> stuff<16:33:48.060> so 16:33:48.406 --> 16:33:48.416 align:start position:0% viruses attackers any of this stuff so 16:33:48.416 --> 16:33:49.906 align:start position:0% viruses attackers any of this stuff so when<16:33:48.540> we're<16:33:48.720> monitoring<16:33:49.140> security<16:33:49.436> an 16:33:49.906 --> 16:33:49.916 align:start position:0% when we're monitoring security an 16:33:49.916 --> 16:33:51.766 align:start position:0% when we're monitoring security an administrator<16:33:50.400> can<16:33:50.700> find<16:33:50.880> holes<16:33:51.416> in<16:33:51.596> the 16:33:51.766 --> 16:33:51.776 align:start position:0% administrator can find holes in the 16:33:51.776 --> 16:33:53.390 align:start position:0% administrator can find holes in the system<16:33:51.956> and<16:33:52.560> then<16:33:52.680> take<16:33:52.860> preventative 16:33:53.390 --> 16:33:53.400 align:start position:0% system and then take preventative 16:33:53.400 --> 16:33:55.426 align:start position:0% system and then take preventative actions<16:33:54.060> in<16:33:54.240> order<16:33:54.416> to<16:33:54.660> stop<16:33:54.840> the<16:33:55.080> attacks 16:33:55.426 --> 16:33:55.436 align:start position:0% actions in order to stop the attacks 16:33:55.436 --> 16:33:56.990 align:start position:0% actions in order to stop the attacks before<16:33:55.560> they<16:33:55.916> happen<16:33:56.096> one<16:33:56.700> thing<16:33:56.880> that's 16:33:56.990 --> 16:33:57.000 align:start position:0% before they happen one thing that's 16:33:57.000 --> 16:33:58.550 align:start position:0% before they happen one thing that's going<16:33:57.180> to<16:33:57.240> help<16:33:57.360> with<16:33:57.540> this<16:33:57.720> are<16:33:58.140> two<16:33:58.320> devices 16:33:58.550 --> 16:33:58.560 align:start position:0% going to help with this are two devices 16:33:58.560 --> 16:34:05.266 align:start position:0% going to help with this are two devices called<16:33:58.916> an<16:33:59.096> IPS<16:33:59.456> or<16:33:59.820> an<16:34:00.060> IDs<16:34:00.660> an<16:34:01.560> intrusion 16:34:05.266 --> 16:34:05.276 align:start position:0% 16:34:05.276 --> 16:34:08.390 align:start position:0% detection<16:34:06.180> system 16:34:08.390 --> 16:34:08.400 align:start position:0% detection system 16:34:08.400 --> 16:34:12.230 align:start position:0% detection system and<16:34:09.000> then<16:34:09.116> an<16:34:09.416> intrusion 16:34:12.230 --> 16:34:12.240 align:start position:0% 16:34:12.240 --> 16:34:15.286 align:start position:0% prevention<16:34:13.080> system 16:34:15.286 --> 16:34:15.296 align:start position:0% prevention system 16:34:15.296 --> 16:34:17.030 align:start position:0% prevention system these<16:34:16.140> are<16:34:16.200> actually<16:34:16.380> two<16:34:16.616> different<16:34:16.796> things 16:34:17.030 --> 16:34:17.040 align:start position:0% these are actually two different things 16:34:17.040 --> 16:34:18.766 align:start position:0% these are actually two different things as<16:34:17.400> you<16:34:17.520> can<16:34:17.640> see<16:34:17.756> from<16:34:18.000> the<16:34:18.180> name<16:34:18.240> intrusion 16:34:18.766 --> 16:34:18.776 align:start position:0% as you can see from the name intrusion 16:34:18.776 --> 16:34:20.446 align:start position:0% as you can see from the name intrusion detection<16:34:19.140> just<16:34:19.560> detects<16:34:20.040> when<16:34:20.220> something 16:34:20.446 --> 16:34:20.456 align:start position:0% detection just detects when something 16:34:20.456 --> 16:34:22.550 align:start position:0% detection just detects when something happens<16:34:21.000> intrusion<16:34:21.900> prevention<16:34:22.256> is<16:34:22.380> actually 16:34:22.550 --> 16:34:22.560 align:start position:0% happens intrusion prevention is actually 16:34:22.560 --> 16:34:24.766 align:start position:0% happens intrusion prevention is actually going<16:34:22.740> to<16:34:22.860> stop<16:34:23.040> it<16:34:23.220> in<16:34:23.400> its<16:34:23.700> tracks<16:34:24.000> so<16:34:24.660> that 16:34:24.766 --> 16:34:24.776 align:start position:0% going to stop it in its tracks so that 16:34:24.776 --> 16:34:27.170 align:start position:0% going to stop it in its tracks so that was<16:34:24.900> just<16:34:25.080> a<16:34:25.380> broad<16:34:25.500> overview<16:34:26.040> of<16:34:26.700> defining 16:34:27.170 --> 16:34:27.180 align:start position:0% was just a broad overview of defining 16:34:27.180 --> 16:34:28.730 align:start position:0% was just a broad overview of defining what<16:34:27.416> an<16:34:27.540> administrator<16:34:27.956> does<16:34:28.256> the<16:34:28.560> person 16:34:28.730 --> 16:34:28.740 align:start position:0% what an administrator does the person 16:34:28.740 --> 16:34:32.390 align:start position:0% what an administrator does the person who<16:34:29.040> overview<16:34:29.520> who<16:34:30.180> has<16:34:30.296> a<16:34:30.540> complete<16:34:30.840> overview 16:34:32.390 --> 16:34:32.400 align:start position:0% who overview who has a complete overview 16:34:32.400 --> 16:34:34.070 align:start position:0% who overview who has a complete overview of<16:34:32.880> the<16:34:33.116> network 16:34:34.070 --> 16:34:34.080 align:start position:0% of the network 16:34:34.080 --> 16:34:35.990 align:start position:0% of the network and<16:34:34.500> then<16:34:34.616> we<16:34:34.860> looked<16:34:35.160> at<16:34:35.276> a<16:34:35.580> couple<16:34:35.700> of<16:34:35.820> the 16:34:35.990 --> 16:34:36.000 align:start position:0% and then we looked at a couple of the 16:34:36.000 --> 16:34:38.570 align:start position:0% and then we looked at a couple of the reasons<16:34:36.540> why<16:34:37.140> their<16:34:37.500> admin<16:34:37.860> duties<16:34:38.220> of<16:34:38.400> the 16:34:38.570 --> 16:34:38.580 align:start position:0% reasons why their admin duties of the 16:34:38.580 --> 16:34:39.946 align:start position:0% reasons why their admin duties of the documentation<16:34:39.116> monitoring<16:34:39.660> are<16:34:39.776> so 16:34:39.946 --> 16:34:39.956 align:start position:0% documentation monitoring are so 16:34:39.956 --> 16:34:43.010 align:start position:0% documentation monitoring are so important<16:34:40.456> documentation<16:34:41.456> for<16:34:42.240> training<16:34:42.776> new 16:34:43.010 --> 16:34:43.020 align:start position:0% important documentation for training new 16:34:43.020 --> 16:34:44.390 align:start position:0% important documentation for training new people 16:34:44.390 --> 16:34:44.400 align:start position:0% people 16:34:44.400 --> 16:34:48.310 align:start position:0% people tech<16:34:45.000> support 16:34:48.310 --> 16:34:48.320 align:start position:0% 16:34:48.320 --> 16:34:53.510 align:start position:0% uh<16:34:49.320> bringing<16:34:49.740> in<16:34:49.916> outside<16:34:50.160> resources 16:34:53.510 --> 16:34:53.520 align:start position:0% 16:34:53.520 --> 16:34:56.570 align:start position:0% and<16:34:53.936> also<16:34:54.180> monitoring<16:34:54.900> not<16:34:55.500> just<16:34:55.680> for<16:34:56.160> uh 16:34:56.570 --> 16:34:56.580 align:start position:0% and also monitoring not just for uh 16:34:56.580 --> 16:34:58.490 align:start position:0% and also monitoring not just for uh security<16:34:56.820> reasons 16:34:58.490 --> 16:34:58.500 align:start position:0% security reasons 16:34:58.500 --> 16:35:01.190 align:start position:0% security reasons but<16:34:59.160> also<16:34:59.456> for<16:34:59.756> performance 16:35:01.190 --> 16:35:01.200 align:start position:0% but also for performance 16:35:01.200 --> 16:35:02.630 align:start position:0% but also for performance because<16:35:01.500> obviously<16:35:01.980> if<16:35:02.096> we<16:35:02.220> have<16:35:02.340> a<16:35:02.520> slow 16:35:02.630 --> 16:35:02.640 align:start position:0% because obviously if we have a slow 16:35:02.640 --> 16:35:05.030 align:start position:0% because obviously if we have a slow Network<16:35:02.936> it's<16:35:03.480> going<16:35:03.660> to<16:35:03.840> result<16:35:04.320> in<16:35:04.740> everyone 16:35:05.030 --> 16:35:05.040 align:start position:0% Network it's going to result in everyone 16:35:05.040 --> 16:35:07.246 align:start position:0% Network it's going to result in everyone being<16:35:05.400> unhappy<16:35:05.936> and<16:35:06.296> your<16:35:06.480> boss<16:35:06.660> is<16:35:06.840> not<16:35:07.080> being 16:35:07.246 --> 16:35:07.256 align:start position:0% being unhappy and your boss is not being 16:35:07.256 --> 16:35:09.586 align:start position:0% being unhappy and your boss is not being able<16:35:07.560> to<16:35:07.680> be<16:35:08.276> able<16:35:08.820> to<16:35:08.880> accomplish<16:35:09.240> the<16:35:09.480> work 16:35:09.586 --> 16:35:09.596 align:start position:0% able to be able to accomplish the work 16:35:09.596 --> 16:35:11.746 align:start position:0% able to be able to accomplish the work they<16:35:09.840> need<16:35:09.956> not<16:35:10.320> to<16:35:10.500> mention<16:35:10.740> if<16:35:11.456> we<16:35:11.580> talk 16:35:11.746 --> 16:35:11.756 align:start position:0% they need not to mention if we talk 16:35:11.756 --> 16:35:13.906 align:start position:0% they need not to mention if we talk about<16:35:11.880> one<16:35:12.296> extra<16:35:12.480> minute<16:35:12.776> in<16:35:13.080> work<16:35:13.256> time<16:35:13.500> that 16:35:13.906 --> 16:35:13.916 align:start position:0% about one extra minute in work time that 16:35:13.916 --> 16:35:15.890 align:start position:0% about one extra minute in work time that can<16:35:14.096> actually<16:35:14.340> cost<16:35:15.116> us<16:35:15.296> quite<16:35:15.540> a<16:35:15.660> bit<16:35:15.776> of 16:35:15.890 --> 16:35:15.900 align:start position:0% can actually cost us quite a bit of 16:35:15.900 --> 16:35:17.870 align:start position:0% can actually cost us quite a bit of money<16:35:16.140> in<16:35:16.380> the<16:35:16.436> real<16:35:16.560> world<16:35:16.796> so<16:35:17.456> having<16:35:17.580> giving 16:35:17.870 --> 16:35:17.880 align:start position:0% money in the real world so having giving 16:35:17.880 --> 16:35:19.606 align:start position:0% money in the real world so having giving us<16:35:18.060> a<16:35:18.240> broad<16:35:18.360> overview<16:35:18.776> of<16:35:18.956> this<16:35:19.200> we're<16:35:19.500> going 16:35:19.606 --> 16:35:19.616 align:start position:0% us a broad overview of this we're going 16:35:19.616 --> 16:35:23.150 align:start position:0% us a broad overview of this we're going to<16:35:19.796> talk<16:35:19.980> more<16:35:20.276> about<16:35:20.900> uh<16:35:21.980> optimizing<16:35:22.980> a 16:35:23.150 --> 16:35:23.160 align:start position:0% to talk more about uh optimizing a 16:35:23.160 --> 16:35:24.650 align:start position:0% to talk more about uh optimizing a network<16:35:23.340> Performance<16:35:23.880> Based<16:35:24.360> on<16:35:24.480> the 16:35:24.650 --> 16:35:24.660 align:start position:0% network Performance Based on the 16:35:24.660 --> 16:35:29.720 align:start position:0% network Performance Based on the monitoring<16:35:25.080> that<16:35:25.320> we<16:35:25.500> do 16:35:29.720 --> 16:35:29.730 align:start position:0% 16:35:29.730 --> 16:35:38.406 align:start position:0% [Music] 16:35:38.406 --> 16:35:38.416 align:start position:0% [Music] 16:35:38.416 --> 16:35:49.426 align:start position:0% [Music] thank<16:35:39.416> you 16:35:49.426 --> 16:35:49.436 align:start position:0% 16:35:49.436 --> 16:35:52.426 align:start position:0% Network<16:35:50.276> management<16:35:51.080> optimizing<16:35:52.080> Network 16:35:52.426 --> 16:35:52.436 align:start position:0% Network management optimizing Network 16:35:52.436 --> 16:35:54.230 align:start position:0% Network management optimizing Network performance 16:35:54.230 --> 16:35:54.240 align:start position:0% performance 16:35:54.240 --> 16:35:55.606 align:start position:0% performance we're<16:35:54.540> going<16:35:54.660> to<16:35:54.720> be<16:35:54.776> covering<16:35:55.080> a<16:35:55.200> lot<16:35:55.320> in<16:35:55.500> this 16:35:55.606 --> 16:35:55.616 align:start position:0% we're going to be covering a lot in this 16:35:55.616 --> 16:35:57.710 align:start position:0% we're going to be covering a lot in this module<16:35:55.980> it's<16:35:56.096> all<16:35:56.276> about<16:35:56.400> the<16:35:57.000> optimization 16:35:57.710 --> 16:35:57.720 align:start position:0% module it's all about the optimization 16:35:57.720 --> 16:36:00.586 align:start position:0% module it's all about the optimization of<16:35:58.616> a<16:35:58.860> network<16:35:59.040> and<16:35:59.456> its<16:35:59.756> performance<16:36:00.060> and 16:36:00.586 --> 16:36:00.596 align:start position:0% of a network and its performance and 16:36:00.596 --> 16:36:02.086 align:start position:0% of a network and its performance and there's<16:36:00.776> a<16:36:00.956> lot<16:36:01.080> that<16:36:01.320> we<16:36:01.500> have<16:36:01.680> to<16:36:01.796> do<16:36:01.916> as 16:36:02.086 --> 16:36:02.096 align:start position:0% there's a lot that we have to do as 16:36:02.096 --> 16:36:03.530 align:start position:0% there's a lot that we have to do as administrators<16:36:02.700> when<16:36:02.880> it<16:36:03.000> comes<16:36:03.240> to<16:36:03.360> that 16:36:03.530 --> 16:36:03.540 align:start position:0% administrators when it comes to that 16:36:03.540 --> 16:36:06.106 align:start position:0% administrators when it comes to that we're<16:36:04.320> going<16:36:04.616> to<16:36:04.796> specifically<16:36:05.276> focus<16:36:05.700> on 16:36:06.106 --> 16:36:06.116 align:start position:0% we're going to specifically focus on 16:36:06.116 --> 16:36:09.710 align:start position:0% we're going to specifically focus on strategies<16:36:06.776> to<16:36:07.256> optimize<16:36:07.916> network<16:36:08.340> speed<16:36:08.820> and 16:36:09.710 --> 16:36:09.720 align:start position:0% strategies to optimize network speed and 16:36:09.720 --> 16:36:10.906 align:start position:0% strategies to optimize network speed and efficiency 16:36:10.906 --> 16:36:10.916 align:start position:0% efficiency 16:36:10.916 --> 16:36:13.426 align:start position:0% efficiency so<16:36:11.580> first<16:36:11.820> we're<16:36:12.180> going<16:36:12.360> to<16:36:12.596> give<16:36:12.900> an<16:36:13.080> overview 16:36:13.426 --> 16:36:13.436 align:start position:0% so first we're going to give an overview 16:36:13.436 --> 16:36:16.010 align:start position:0% so first we're going to give an overview of<16:36:13.560> what<16:36:13.860> network<16:36:14.040> optimization<16:36:14.820> is<16:36:15.180> and<16:36:15.900> then 16:36:16.010 --> 16:36:16.020 align:start position:0% of what network optimization is and then 16:36:16.020 --> 16:36:17.210 align:start position:0% of what network optimization is and then we're<16:36:16.140> going<16:36:16.256> to<16:36:16.320> define<16:36:16.436> something<16:36:16.860> called 16:36:17.210 --> 16:36:17.220 align:start position:0% we're going to define something called 16:36:17.220 --> 16:36:20.690 align:start position:0% we're going to define something called quality<16:36:18.000> of<16:36:18.596> service<16:36:18.840> qos<16:36:19.680> which<16:36:20.340> I<16:36:20.456> want<16:36:20.580> to 16:36:20.690 --> 16:36:20.700 align:start position:0% quality of service qos which I want to 16:36:20.700 --> 16:36:22.246 align:start position:0% quality of service qos which I want to point<16:36:20.756> out<16:36:20.936> right<16:36:21.240> now<16:36:21.480> you're<16:36:21.900> going<16:36:22.080> to<16:36:22.140> see 16:36:22.246 --> 16:36:22.256 align:start position:0% point out right now you're going to see 16:36:22.256 --> 16:36:25.190 align:start position:0% point out right now you're going to see anytime<16:36:22.740> we<16:36:22.980> talk<16:36:23.160> about<16:36:23.340> voice<16:36:23.756> over<16:36:24.060> IP<16:36:24.660> this 16:36:25.190 --> 16:36:25.200 align:start position:0% anytime we talk about voice over IP this 16:36:25.200 --> 16:36:27.230 align:start position:0% anytime we talk about voice over IP this is<16:36:25.320> the<16:36:25.436> name<16:36:25.560> implies<16:36:25.980> what<16:36:26.580> we're<16:36:26.700> doing<16:36:26.880> is 16:36:27.230 --> 16:36:27.240 align:start position:0% is the name implies what we're doing is 16:36:27.240 --> 16:36:29.990 align:start position:0% is the name implies what we're doing is trying<16:36:28.020> to<16:36:28.256> make<16:36:28.500> sure<16:36:28.740> the<16:36:29.276> service<16:36:29.456> provided 16:36:29.990 --> 16:36:30.000 align:start position:0% trying to make sure the service provided 16:36:30.000 --> 16:36:31.850 align:start position:0% trying to make sure the service provided on<16:36:30.180> our<16:36:30.360> network<16:36:30.540> has<16:36:31.080> a<16:36:31.256> high<16:36:31.380> degree<16:36:31.740> of 16:36:31.850 --> 16:36:31.860 align:start position:0% on our network has a high degree of 16:36:31.860 --> 16:36:33.830 align:start position:0% on our network has a high degree of quality<16:36:32.220> and<16:36:32.520> when<16:36:32.700> it<16:36:32.820> comes<16:36:33.000> to<16:36:33.116> voice<16:36:33.480> over 16:36:33.830 --> 16:36:33.840 align:start position:0% quality and when it comes to voice over 16:36:33.840 --> 16:36:35.870 align:start position:0% quality and when it comes to voice over IP<16:36:34.320> we<16:36:34.796> need<16:36:34.860> to<16:36:34.980> make<16:36:35.040> sure<16:36:35.160> the<16:36:35.340> quality<16:36:35.700> is 16:36:35.870 --> 16:36:35.880 align:start position:0% IP we need to make sure the quality is 16:36:35.880 --> 16:36:36.946 align:start position:0% IP we need to make sure the quality is pretty<16:36:36.116> high 16:36:36.946 --> 16:36:36.956 align:start position:0% pretty high 16:36:36.956 --> 16:36:39.170 align:start position:0% pretty high there<16:36:37.500> are<16:36:37.616> two<16:36:37.740> ways<16:36:37.980> to<16:36:38.096> do<16:36:38.220> this<16:36:38.400> one<16:36:39.000> is 16:36:39.170 --> 16:36:39.180 align:start position:0% there are two ways to do this one is 16:36:39.180 --> 16:36:41.390 align:start position:0% there are two ways to do this one is called<16:36:39.480> latency<16:36:40.200> sensitive<16:36:40.980> and<16:36:41.160> the<16:36:41.276> other 16:36:41.390 --> 16:36:41.400 align:start position:0% called latency sensitive and the other 16:36:41.400 --> 16:36:43.490 align:start position:0% called latency sensitive and the other is<16:36:41.580> latency<16:36:42.240> insensitive<16:36:43.020> and<16:36:43.200> we'll<16:36:43.320> Define 16:36:43.490 --> 16:36:43.500 align:start position:0% is latency insensitive and we'll Define 16:36:43.500 --> 16:36:44.810 align:start position:0% is latency insensitive and we'll Define that<16:36:43.796> a<16:36:43.980> bit<16:36:44.096> more 16:36:44.810 --> 16:36:44.820 align:start position:0% that a bit more 16:36:44.820 --> 16:36:46.190 align:start position:0% that a bit more we're<16:36:45.240> also<16:36:45.480> going<16:36:45.596> to<16:36:45.596> talk<16:36:45.720> about<16:36:45.840> something 16:36:46.190 --> 16:36:46.200 align:start position:0% we're also going to talk about something 16:36:46.200 --> 16:36:49.370 align:start position:0% we're also going to talk about something called<16:36:46.616> traffic<16:36:47.220> shaping<16:36:47.936> and<16:36:48.776> methods<16:36:49.256> in 16:36:49.370 --> 16:36:49.380 align:start position:0% called traffic shaping and methods in 16:36:49.380 --> 16:36:51.890 align:start position:0% called traffic shaping and methods in which<16:36:49.500> we<16:36:49.680> do<16:36:49.796> this<16:36:49.980> and<16:36:50.756> finally<16:36:51.060> caching 16:36:51.890 --> 16:36:51.900 align:start position:0% which we do this and finally caching 16:36:51.900 --> 16:36:54.170 align:start position:0% which we do this and finally caching engines<16:36:52.256> which<16:36:52.916> help<16:36:53.220> speed<16:36:53.580> up<16:36:53.820> Network 16:36:54.170 --> 16:36:54.180 align:start position:0% engines which help speed up Network 16:36:54.180 --> 16:36:56.210 align:start position:0% engines which help speed up Network performance<16:36:54.720> as<16:36:54.900> well 16:36:56.210 --> 16:36:56.220 align:start position:0% performance as well 16:36:56.220 --> 16:36:57.310 align:start position:0% performance as well so 16:36:57.310 --> 16:36:57.320 align:start position:0% so 16:36:57.320 --> 16:36:59.990 align:start position:0% so bandwidth<16:36:58.320> is<16:36:58.500> essentially<16:36:58.980> the<16:36:59.456> amount<16:36:59.756> of 16:36:59.990 --> 16:37:00.000 align:start position:0% bandwidth is essentially the amount of 16:37:00.000 --> 16:37:01.670 align:start position:0% bandwidth is essentially the amount of data<16:37:00.360> that<16:37:00.720> can<16:37:00.840> be<16:37:00.956> transferred<16:37:01.560> and 16:37:01.670 --> 16:37:01.680 align:start position:0% data that can be transferred and 16:37:01.680 --> 16:37:04.190 align:start position:0% data that can be transferred and utilized<16:37:02.276> at<16:37:02.400> any<16:37:02.580> given<16:37:02.936> time<16:37:03.180> this<16:37:03.900> amount 16:37:04.190 --> 16:37:04.200 align:start position:0% utilized at any given time this amount 16:37:04.200 --> 16:37:06.230 align:start position:0% utilized at any given time this amount is<16:37:04.380> usually<16:37:04.616> expressed<16:37:05.040> in<16:37:05.400> bits<16:37:05.820> per<16:37:06.000> second 16:37:06.230 --> 16:37:06.240 align:start position:0% is usually expressed in bits per second 16:37:06.240 --> 16:37:09.106 align:start position:0% is usually expressed in bits per second so<16:37:07.080> if<16:37:07.320> you<16:37:07.380> remember<16:37:07.560> we<16:37:08.096> see<16:37:08.340> for<16:37:08.936> instance 16:37:09.106 --> 16:37:09.116 align:start position:0% so if you remember we see for instance 16:37:09.116 --> 16:37:12.406 align:start position:0% so if you remember we see for instance mega<16:37:09.540> bits<16:37:10.140> per<16:37:10.320> second<16:37:10.560> with<16:37:11.400> the<16:37:11.700> small<16:37:12.116> B 16:37:12.406 --> 16:37:12.416 align:start position:0% mega bits per second with the small B 16:37:12.416 --> 16:37:14.030 align:start position:0% mega bits per second with the small B and<16:37:12.956> I<16:37:13.080> want<16:37:13.200> to<16:37:13.256> point<16:37:13.380> out<16:37:13.500> again<16:37:13.680> that<16:37:13.916> this 16:37:14.030 --> 16:37:14.040 align:start position:0% and I want to point out again that this 16:37:14.040 --> 16:37:16.246 align:start position:0% and I want to point out again that this is<16:37:14.160> not<16:37:14.276> megabytes<16:37:15.060> per<16:37:15.296> second<16:37:15.480> as<16:37:16.080> you 16:37:16.246 --> 16:37:16.256 align:start position:0% is not megabytes per second as you 16:37:16.256 --> 16:37:19.130 align:start position:0% is not megabytes per second as you recall<16:37:16.560> there<16:37:17.220> are<16:37:17.400> eight<16:37:17.700> bits 16:37:19.130 --> 16:37:19.140 align:start position:0% recall there are eight bits 16:37:19.140 --> 16:37:21.710 align:start position:0% recall there are eight bits in<16:37:19.796> every<16:37:20.040> bite 16:37:21.710 --> 16:37:21.720 align:start position:0% in every bite 16:37:21.720 --> 16:37:26.086 align:start position:0% in every bite so<16:37:22.320> we<16:37:22.796> would<16:37:22.916> really<16:37:23.096> need<16:37:23.456> eight 16:37:26.086 --> 16:37:26.096 align:start position:0% 16:37:26.096 --> 16:37:29.690 align:start position:0% mega<16:37:26.700> bits<16:37:27.060> per<16:37:27.180> second<16:37:27.416> to<16:37:28.320> equal<16:37:28.436> one 16:37:29.690 --> 16:37:29.700 align:start position:0% mega bits per second to equal one 16:37:29.700 --> 16:37:32.510 align:start position:0% mega bits per second to equal one megabyte<16:37:30.540> per<16:37:31.320> second<16:37:31.560> just<16:37:32.096> something<16:37:32.276> to 16:37:32.510 --> 16:37:32.520 align:start position:0% megabyte per second just something to 16:37:32.520 --> 16:37:35.746 align:start position:0% megabyte per second just something to keep<16:37:32.640> in<16:37:32.756> mind<16:37:32.936> as<16:37:33.840> you<16:37:34.256> purchase<16:37:34.980> uh<16:37:35.456> perhaps 16:37:35.746 --> 16:37:35.756 align:start position:0% keep in mind as you purchase uh perhaps 16:37:35.756 --> 16:37:38.330 align:start position:0% keep in mind as you purchase uh perhaps a<16:37:36.000> broadband<16:37:36.540> connection<16:37:36.980> now<16:37:37.980> how<16:37:38.160> the 16:37:38.330 --> 16:37:38.340 align:start position:0% a broadband connection now how the 16:37:38.340 --> 16:37:41.746 align:start position:0% a broadband connection now how the bandwidth<16:37:39.060> flows<16:37:39.900> is<16:37:40.320> dependent<16:37:40.916> on<16:37:41.456> how<16:37:41.640> many 16:37:41.746 --> 16:37:41.756 align:start position:0% bandwidth flows is dependent on how many 16:37:41.756 --> 16:37:43.606 align:start position:0% bandwidth flows is dependent on how many people<16:37:41.880> are<16:37:42.116> using<16:37:42.416> it<16:37:42.540> at<16:37:42.720> once<16:37:42.900> and<16:37:43.200> for<16:37:43.436> what 16:37:43.606 --> 16:37:43.616 align:start position:0% people are using it at once and for what 16:37:43.616 --> 16:37:45.710 align:start position:0% people are using it at once and for what purpose<16:37:43.980> so<16:37:44.640> everything<16:37:44.880> in<16:37:45.180> today's<16:37:45.360> world 16:37:45.710 --> 16:37:45.720 align:start position:0% purpose so everything in today's world 16:37:45.720 --> 16:37:47.926 align:start position:0% purpose so everything in today's world is<16:37:46.080> expected<16:37:46.500> to<16:37:46.680> be<16:37:46.796> fast<16:37:47.096> and<16:37:47.340> we<16:37:47.520> can<16:37:47.640> settle 16:37:47.926 --> 16:37:47.936 align:start position:0% is expected to be fast and we can settle 16:37:47.936 --> 16:37:50.266 align:start position:0% is expected to be fast and we can settle for<16:37:48.060> no<16:37:48.296> less<16:37:48.480> than<16:37:48.720> the<16:37:49.080> fastest<16:37:49.436> it<16:37:50.096> will 16:37:50.266 --> 16:37:50.276 align:start position:0% for no less than the fastest it will 16:37:50.276 --> 16:37:51.830 align:start position:0% for no less than the fastest it will become<16:37:50.520> really<16:37:50.880> impatient<16:37:51.360> with<16:37:51.660> network 16:37:51.830 --> 16:37:51.840 align:start position:0% become really impatient with network 16:37:51.840 --> 16:37:53.870 align:start position:0% become really impatient with network speeds<16:37:52.560> very<16:37:52.916> easily<16:37:53.220> and<16:37:53.520> unfortunately 16:37:53.870 --> 16:37:53.880 align:start position:0% speeds very easily and unfortunately 16:37:53.880 --> 16:37:55.370 align:start position:0% speeds very easily and unfortunately they<16:37:54.116> fluctuate<16:37:54.540> fairly<16:37:54.900> easily<16:37:55.200> too 16:37:55.370 --> 16:37:55.380 align:start position:0% they fluctuate fairly easily too 16:37:55.380 --> 16:37:57.586 align:start position:0% they fluctuate fairly easily too especially<16:37:56.276> in<16:37:56.580> a<16:37:56.756> corporate<16:37:57.060> environment 16:37:57.586 --> 16:37:57.596 align:start position:0% especially in a corporate environment 16:37:57.596 --> 16:37:59.390 align:start position:0% especially in a corporate environment where<16:37:58.200> there<16:37:58.380> are<16:37:58.500> a<16:37:58.616> lot<16:37:58.740> of<16:37:58.860> people<16:37:58.980> using 16:37:59.390 --> 16:37:59.400 align:start position:0% where there are a lot of people using 16:37:59.400 --> 16:38:01.426 align:start position:0% where there are a lot of people using and<16:37:59.580> taking<16:37:59.756> up<16:38:00.060> the<16:38:00.240> same<16:38:00.416> bandwidth<16:38:01.020> just 16:38:01.426 --> 16:38:01.436 align:start position:0% and taking up the same bandwidth just 16:38:01.436 --> 16:38:04.490 align:start position:0% and taking up the same bandwidth just imagine<16:38:01.740> how<16:38:02.700> frustrated<16:38:03.296> workers<16:38:03.840> are<16:38:04.320> going 16:38:04.490 --> 16:38:04.500 align:start position:0% imagine how frustrated workers are going 16:38:04.500 --> 16:38:07.246 align:start position:0% imagine how frustrated workers are going to<16:38:04.616> become<16:38:04.916> with<16:38:05.456> uh<16:38:05.820> when<16:38:06.660> they<16:38:06.900> can<16:38:07.080> access 16:38:07.246 --> 16:38:07.256 align:start position:0% to become with uh when they can access 16:38:07.256 --> 16:38:09.106 align:start position:0% to become with uh when they can access something<16:38:07.616> really<16:38:07.796> fast<16:38:08.040> one<16:38:08.456> second<16:38:08.700> and 16:38:09.106 --> 16:38:09.116 align:start position:0% something really fast one second and 16:38:09.116 --> 16:38:10.670 align:start position:0% something really fast one second and very<16:38:09.296> slow<16:38:09.480> the<16:38:09.720> next<16:38:09.840> you<16:38:10.080> can<16:38:10.200> imagine<16:38:10.380> this 16:38:10.670 --> 16:38:10.680 align:start position:0% very slow the next you can imagine this 16:38:10.680 --> 16:38:11.926 align:start position:0% very slow the next you can imagine this at<16:38:10.860> home<16:38:11.040> as<16:38:11.220> well 16:38:11.926 --> 16:38:11.936 align:start position:0% at home as well 16:38:11.936 --> 16:38:14.810 align:start position:0% at home as well so<16:38:12.596> the<16:38:13.140> purpose<16:38:13.500> of<16:38:13.860> network<16:38:14.040> optimization 16:38:14.810 --> 16:38:14.820 align:start position:0% so the purpose of network optimization 16:38:14.820 --> 16:38:17.510 align:start position:0% so the purpose of network optimization is<16:38:15.116> really<16:38:15.296> to<16:38:15.480> help<16:38:15.660> control<16:38:16.020> the<16:38:16.916> traffic<16:38:17.096> on 16:38:17.510 --> 16:38:17.520 align:start position:0% is really to help control the traffic on 16:38:17.520 --> 16:38:19.606 align:start position:0% is really to help control the traffic on a<16:38:17.700> network<16:38:17.820> the<16:38:18.596> large<16:38:18.840> group<16:38:19.020> of<16:38:19.200> people<16:38:19.380> are 16:38:19.606 --> 16:38:19.616 align:start position:0% a network the large group of people are 16:38:19.616 --> 16:38:21.470 align:start position:0% a network the large group of people are trying<16:38:19.860> to<16:38:20.040> enter<16:38:20.220> a<16:38:20.456> building<16:38:20.640> through<16:38:21.116> one 16:38:21.470 --> 16:38:21.480 align:start position:0% trying to enter a building through one 16:38:21.480 --> 16:38:22.970 align:start position:0% trying to enter a building through one door<16:38:21.660> the<16:38:22.200> flow<16:38:22.380> is<16:38:22.500> going<16:38:22.616> to<16:38:22.680> be<16:38:22.796> a<16:38:22.916> lot 16:38:22.970 --> 16:38:22.980 align:start position:0% door the flow is going to be a lot 16:38:22.980 --> 16:38:25.730 align:start position:0% door the flow is going to be a lot slower<16:38:23.520> than<16:38:24.000> if<16:38:24.180> there<16:38:24.416> are<16:38:24.596> multiple<16:38:25.320> doors 16:38:25.730 --> 16:38:25.740 align:start position:0% slower than if there are multiple doors 16:38:25.740 --> 16:38:27.946 align:start position:0% slower than if there are multiple doors and<16:38:26.456> the<16:38:26.756> same<16:38:26.880> principle<16:38:27.360> applies<16:38:27.776> to 16:38:27.946 --> 16:38:27.956 align:start position:0% and the same principle applies to 16:38:27.956 --> 16:38:30.050 align:start position:0% and the same principle applies to networks<16:38:28.320> if<16:38:28.500> the<16:38:28.740> network<16:38:28.916> is<16:38:29.276> laid<16:38:29.580> out<16:38:29.756> and 16:38:30.050 --> 16:38:30.060 align:start position:0% networks if the network is laid out and 16:38:30.060 --> 16:38:32.266 align:start position:0% networks if the network is laid out and run<16:38:30.240> in<16:38:30.480> an<16:38:30.660> optimal<16:38:31.140> way<16:38:31.320> there<16:38:31.980> is<16:38:32.096> less 16:38:32.266 --> 16:38:32.276 align:start position:0% run in an optimal way there is less 16:38:32.276 --> 16:38:35.210 align:start position:0% run in an optimal way there is less chance<16:38:32.640> of<16:38:33.060> blockage<16:38:33.540> so<16:38:34.380> in<16:38:34.560> addition<16:38:34.796> to 16:38:35.210 --> 16:38:35.220 align:start position:0% chance of blockage so in addition to 16:38:35.220 --> 16:38:37.670 align:start position:0% chance of blockage so in addition to network<16:38:35.640> traffic<16:38:36.200> optimization<16:38:37.200> Works<16:38:37.560> to 16:38:37.670 --> 16:38:37.680 align:start position:0% network traffic optimization Works to 16:38:37.680 --> 16:38:39.830 align:start position:0% network traffic optimization Works to utilize<16:38:38.096> bandwidth<16:38:38.820> in<16:38:39.000> the<16:38:39.240> best<16:38:39.416> possible 16:38:39.830 --> 16:38:39.840 align:start position:0% utilize bandwidth in the best possible 16:38:39.840 --> 16:38:42.350 align:start position:0% utilize bandwidth in the best possible way<16:38:40.080> so<16:38:40.680> that<16:38:40.860> everyone<16:38:41.040> can<16:38:41.340> use<16:38:41.580> it<16:38:41.756> at<16:38:42.180> the 16:38:42.350 --> 16:38:42.360 align:start position:0% way so that everyone can use it at the 16:38:42.360 --> 16:38:44.926 align:start position:0% way so that everyone can use it at the same<16:38:42.480> time<16:38:42.776> this<16:38:43.680> would<16:38:43.860> be<16:38:44.040> also<16:38:44.700> called 16:38:44.926 --> 16:38:44.936 align:start position:0% same time this would be also called 16:38:44.936 --> 16:38:46.670 align:start position:0% same time this would be also called throughput 16:38:46.670 --> 16:38:46.680 align:start position:0% throughput 16:38:46.680 --> 16:38:50.570 align:start position:0% throughput so<16:38:47.340> whereas<16:38:47.820> bandwidth 16:38:50.570 --> 16:38:50.580 align:start position:0% so whereas bandwidth 16:38:50.580 --> 16:38:56.150 align:start position:0% so whereas bandwidth is<16:38:51.360> our<16:38:51.660> ideal<16:38:52.256> or<16:38:52.796> possible 16:38:56.150 --> 16:38:56.160 align:start position:0% 16:38:56.160 --> 16:38:59.030 align:start position:0% throughput 16:38:59.030 --> 16:38:59.040 align:start position:0% 16:38:59.040 --> 16:39:00.830 align:start position:0% is<16:38:59.456> the<16:38:59.700> actual 16:39:00.830 --> 16:39:00.840 align:start position:0% is the actual 16:39:00.840 --> 16:39:03.106 align:start position:0% is the actual in<16:39:01.200> other<16:39:01.320> words<16:39:01.500> what<16:39:02.220> actually<16:39:02.520> makes<16:39:02.880> it 16:39:03.106 --> 16:39:03.116 align:start position:0% in other words what actually makes it 16:39:03.116 --> 16:39:04.606 align:start position:0% in other words what actually makes it through<16:39:03.296> the<16:39:03.540> bandwidth 16:39:04.606 --> 16:39:04.616 align:start position:0% through the bandwidth 16:39:04.616 --> 16:39:06.286 align:start position:0% through the bandwidth so<16:39:04.916> here's<16:39:05.160> a<16:39:05.276> representation<16:39:05.756> of<16:39:06.060> what 16:39:06.286 --> 16:39:06.296 align:start position:0% so here's a representation of what 16:39:06.296 --> 16:39:08.330 align:start position:0% so here's a representation of what bandwidth<16:39:06.840> might<16:39:07.020> look<16:39:07.256> like<16:39:07.380> imagine<16:39:08.040> the 16:39:08.330 --> 16:39:08.340 align:start position:0% bandwidth might look like imagine the 16:39:08.340 --> 16:39:11.030 align:start position:0% bandwidth might look like imagine the bandwidth<16:39:08.820> capabilities<16:39:09.360> are<16:39:09.956> like<16:39:10.500> tubes 16:39:11.030 --> 16:39:11.040 align:start position:0% bandwidth capabilities are like tubes 16:39:11.040 --> 16:39:13.246 align:start position:0% bandwidth capabilities are like tubes and<16:39:11.456> the<16:39:11.640> bigger<16:39:11.880> the<16:39:12.000> tube<16:39:12.360> the<16:39:12.720> more<16:39:12.840> that<16:39:13.080> is 16:39:13.246 --> 16:39:13.256 align:start position:0% and the bigger the tube the more that is 16:39:13.256 --> 16:39:15.890 align:start position:0% and the bigger the tube the more that is free<16:39:13.436> to<16:39:13.680> throw<16:39:13.860> flow<16:39:14.700> through<16:39:14.936> it<16:39:15.180> so<16:39:15.776> here 16:39:15.890 --> 16:39:15.900 align:start position:0% free to throw flow through it so here 16:39:15.900 --> 16:39:17.630 align:start position:0% free to throw flow through it so here you<16:39:16.020> can<16:39:16.140> see<16:39:16.256> there's<16:39:16.500> much<16:39:16.740> more<16:39:17.040> ability<16:39:17.340> to 16:39:17.630 --> 16:39:17.640 align:start position:0% you can see there's much more ability to 16:39:17.640 --> 16:39:19.010 align:start position:0% you can see there's much more ability to flow<16:39:17.880> through<16:39:18.240> the<16:39:18.416> tube<16:39:18.660> on<16:39:18.776> the<16:39:18.900> right 16:39:19.010 --> 16:39:19.020 align:start position:0% flow through the tube on the right 16:39:19.020 --> 16:39:21.470 align:start position:0% flow through the tube on the right because<16:39:19.256> it's<16:39:19.436> a<16:39:19.560> lot<16:39:19.680> bigger<16:39:20.040> than<16:39:20.700> the<16:39:21.180> tube 16:39:21.470 --> 16:39:21.480 align:start position:0% because it's a lot bigger than the tube 16:39:21.480 --> 16:39:24.470 align:start position:0% because it's a lot bigger than the tube on<16:39:21.720> the<16:39:21.776> left<16:39:21.900> that<16:39:22.860> being<16:39:23.040> said<16:39:23.340> only<16:39:24.180> because 16:39:24.470 --> 16:39:24.480 align:start position:0% on the left that being said only because 16:39:24.480 --> 16:39:27.050 align:start position:0% on the left that being said only because our<16:39:25.080> bandwidth<16:39:25.680> is<16:39:26.160> for<16:39:26.340> instance<16:39:26.580> 90 16:39:27.050 --> 16:39:27.060 align:start position:0% our bandwidth is for instance 90 16:39:27.060 --> 16:39:30.470 align:start position:0% our bandwidth is for instance 90 megabits<16:39:27.720> per<16:39:27.900> second<16:39:28.400> or<16:39:29.400> one<16:39:29.756> gigabit<16:39:30.240> per 16:39:30.470 --> 16:39:30.480 align:start position:0% megabits per second or one gigabit per 16:39:30.480 --> 16:39:32.746 align:start position:0% megabits per second or one gigabit per second<16:39:30.720> doesn't<16:39:31.680> mean<16:39:31.980> that<16:39:32.220> the<16:39:32.400> throughput 16:39:32.746 --> 16:39:32.756 align:start position:0% second doesn't mean that the throughput 16:39:32.756 --> 16:39:35.266 align:start position:0% second doesn't mean that the throughput is<16:39:33.240> actually<16:39:33.540> going<16:39:33.776> to<16:39:33.900> be<16:39:34.080> that<16:39:34.320> I'm<16:39:35.040> sure 16:39:35.266 --> 16:39:35.276 align:start position:0% is actually going to be that I'm sure 16:39:35.276 --> 16:39:39.650 align:start position:0% is actually going to be that I'm sure that<16:39:35.456> you<16:39:36.060> have<16:39:36.296> at<16:39:37.020> home<16:39:37.340> uh<16:39:38.340> bandwidth<16:39:39.000> or 16:39:39.650 --> 16:39:39.660 align:start position:0% that you have at home uh bandwidth or 16:39:39.660 --> 16:39:41.210 align:start position:0% that you have at home uh bandwidth or broadband<16:39:40.320> internet 16:39:41.210 --> 16:39:41.220 align:start position:0% broadband internet 16:39:41.220 --> 16:39:43.190 align:start position:0% broadband internet and<16:39:41.880> it<16:39:42.060> probably<16:39:42.180> says<16:39:42.480> it<16:39:42.660> has<16:39:42.776> up<16:39:43.020> to 16:39:43.190 --> 16:39:43.200 align:start position:0% and it probably says it has up to 16:39:43.200 --> 16:39:45.830 align:start position:0% and it probably says it has up to perhaps<16:39:43.680> maybe<16:39:43.916> 15<16:39:44.220> megabits<16:39:44.936> per<16:39:45.116> second<16:39:45.296> if 16:39:45.830 --> 16:39:45.840 align:start position:0% perhaps maybe 15 megabits per second if 16:39:45.840 --> 16:39:47.630 align:start position:0% perhaps maybe 15 megabits per second if you're<16:39:46.020> on<16:39:46.140> cable<16:39:46.436> but<16:39:47.096> sometimes<16:39:47.400> you're<16:39:47.520> not 16:39:47.630 --> 16:39:47.640 align:start position:0% you're on cable but sometimes you're not 16:39:47.640 --> 16:39:49.130 align:start position:0% you're on cable but sometimes you're not always<16:39:47.820> getting<16:39:48.000> 15<16:39:48.296> megabits<16:39:48.900> per<16:39:49.020> second 16:39:49.130 --> 16:39:49.140 align:start position:0% always getting 15 megabits per second 16:39:49.140 --> 16:39:51.650 align:start position:0% always getting 15 megabits per second you<16:39:49.436> might<16:39:49.616> be<16:39:49.740> getting<16:39:50.116> five<16:39:51.116> or<16:39:51.360> eight 16:39:51.650 --> 16:39:51.660 align:start position:0% you might be getting five or eight 16:39:51.660 --> 16:39:53.990 align:start position:0% you might be getting five or eight megabits<16:39:52.200> per<16:39:52.380> second<16:39:52.560> and<16:39:53.160> you<16:39:53.456> can<16:39:53.580> test 16:39:53.990 --> 16:39:54.000 align:start position:0% megabits per second and you can test 16:39:54.000 --> 16:39:55.550 align:start position:0% megabits per second and you can test this<16:39:54.240> using<16:39:54.596> different<16:39:54.776> sort<16:39:55.140> of<16:39:55.256> online 16:39:55.550 --> 16:39:55.560 align:start position:0% this using different sort of online 16:39:55.560 --> 16:39:59.510 align:start position:0% this using different sort of online speed<16:39:56.456> test<16:39:56.936> uh<16:39:57.720> utilities<16:39:58.140> but<16:39:59.096> only<16:39:59.276> because 16:39:59.510 --> 16:39:59.520 align:start position:0% speed test uh utilities but only because 16:39:59.520 --> 16:40:01.370 align:start position:0% speed test uh utilities but only because we<16:39:59.936> have<16:40:00.180> a<16:40:00.540> certain<16:40:00.660> amount<16:40:00.776> of<16:40:00.956> bandwidth 16:40:01.370 --> 16:40:01.380 align:start position:0% we have a certain amount of bandwidth 16:40:01.380 --> 16:40:03.106 align:start position:0% we have a certain amount of bandwidth doesn't<16:40:01.500> mean<16:40:01.740> our<16:40:01.916> throughput<16:40:02.340> is<16:40:02.756> going<16:40:02.936> to 16:40:03.106 --> 16:40:03.116 align:start position:0% doesn't mean our throughput is going to 16:40:03.116 --> 16:40:04.786 align:start position:0% doesn't mean our throughput is going to equal<16:40:03.296> that<16:40:03.596> which<16:40:04.140> is<16:40:04.256> an<16:40:04.500> important 16:40:04.786 --> 16:40:04.796 align:start position:0% equal that which is an important 16:40:04.796 --> 16:40:06.830 align:start position:0% equal that which is an important distinction 16:40:06.830 --> 16:40:06.840 align:start position:0% distinction 16:40:06.840 --> 16:40:11.446 align:start position:0% distinction to<16:40:07.380> make 16:40:11.446 --> 16:40:11.456 align:start position:0% 16:40:11.456 --> 16:40:13.970 align:start position:0% what<16:40:11.936> we<16:40:12.060> want<16:40:12.240> to<16:40:12.360> do<16:40:12.540> is<16:40:13.200> get<16:40:13.380> the<16:40:13.500> bandwidth 16:40:13.970 --> 16:40:13.980 align:start position:0% what we want to do is get the bandwidth 16:40:13.980 --> 16:40:15.586 align:start position:0% what we want to do is get the bandwidth and<16:40:14.096> throughput<16:40:14.456> to<16:40:14.640> equal<16:40:14.820> as<16:40:15.240> close<16:40:15.416> as 16:40:15.586 --> 16:40:15.596 align:start position:0% and throughput to equal as close as 16:40:15.596 --> 16:40:17.210 align:start position:0% and throughput to equal as close as possible<16:40:15.900> to<16:40:16.140> one<16:40:16.256> another 16:40:17.210 --> 16:40:17.220 align:start position:0% possible to one another 16:40:17.220 --> 16:40:20.030 align:start position:0% possible to one another so<16:40:17.936> there<16:40:18.540> are<16:40:18.720> strategies<16:40:19.256> used<16:40:19.560> to<16:40:19.860> increase 16:40:20.030 --> 16:40:20.040 align:start position:0% so there are strategies used to increase 16:40:20.040 --> 16:40:22.850 align:start position:0% so there are strategies used to increase the<16:40:20.400> use<16:40:20.640> and<16:40:21.000> optimization<16:40:21.596> of<16:40:21.840> bandwidth<16:40:22.380> on 16:40:22.850 --> 16:40:22.860 align:start position:0% the use and optimization of bandwidth on 16:40:22.860 --> 16:40:23.690 align:start position:0% the use and optimization of bandwidth on a<16:40:22.980> network 16:40:23.690 --> 16:40:23.700 align:start position:0% a network 16:40:23.700 --> 16:40:26.870 align:start position:0% a network these<16:40:24.360> strategies<16:40:24.776> are<16:40:25.200> called<16:40:25.700> quality<16:40:26.700> of 16:40:26.870 --> 16:40:26.880 align:start position:0% these strategies are called quality of 16:40:26.880 --> 16:40:30.286 align:start position:0% these strategies are called quality of service<16:40:27.116> or<16:40:28.080> short-term<16:40:28.616> qos 16:40:30.286 --> 16:40:30.296 align:start position:0% service or short-term qos 16:40:30.296 --> 16:40:32.510 align:start position:0% service or short-term qos now<16:40:30.660> they<16:40:30.840> have<16:40:31.020> a<16:40:31.320> lot<16:40:31.500> to<16:40:31.740> do<16:40:31.916> with 16:40:32.510 --> 16:40:32.520 align:start position:0% now they have a lot to do with 16:40:32.520 --> 16:40:35.690 align:start position:0% now they have a lot to do with information<16:40:33.320> and<16:40:34.320> helping<16:40:34.916> it<16:40:35.040> optimize<16:40:35.520> the 16:40:35.690 --> 16:40:35.700 align:start position:0% information and helping it optimize the 16:40:35.700 --> 16:40:38.926 align:start position:0% information and helping it optimize the network<16:40:35.880> so<16:40:36.660> qos<16:40:37.200> allows<16:40:37.796> administrators<16:40:38.640> to 16:40:38.926 --> 16:40:38.936 align:start position:0% network so qos allows administrators to 16:40:38.936 --> 16:40:40.786 align:start position:0% network so qos allows administrators to predict<16:40:39.360> the<16:40:39.720> bandwidth<16:40:40.256> use<16:40:40.436> on<16:40:40.680> their 16:40:40.786 --> 16:40:40.796 align:start position:0% predict the bandwidth use on their 16:40:40.796 --> 16:40:43.426 align:start position:0% predict the bandwidth use on their Network<16:40:41.180> monitor<16:40:42.180> the<16:40:42.360> use<16:40:42.540> of<16:40:42.720> it<16:40:42.840> and<16:40:43.320> then 16:40:43.426 --> 16:40:43.436 align:start position:0% Network monitor the use of it and then 16:40:43.436 --> 16:40:45.406 align:start position:0% Network monitor the use of it and then control<16:40:43.680> it<16:40:44.040> this<16:40:44.700> is<16:40:44.820> done<16:40:44.936> to<16:40:45.116> make<16:40:45.296> sure 16:40:45.406 --> 16:40:45.416 align:start position:0% control it this is done to make sure 16:40:45.416 --> 16:40:47.266 align:start position:0% control it this is done to make sure that<16:40:45.660> there<16:40:45.776> is<16:40:46.020> available<16:40:46.320> bandwidth<16:40:47.096> for 16:40:47.266 --> 16:40:47.276 align:start position:0% that there is available bandwidth for 16:40:47.276 --> 16:40:49.970 align:start position:0% that there is available bandwidth for any<16:40:47.456> one<16:40:47.700> application<16:40:48.180> that<16:40:48.596> requires<16:40:49.020> it<16:40:49.200> the 16:40:49.970 --> 16:40:49.980 align:start position:0% any one application that requires it the 16:40:49.980 --> 16:40:51.470 align:start position:0% any one application that requires it the applications<16:40:50.276> that<16:40:50.580> need<16:40:50.756> this<16:40:50.936> bandwidth 16:40:51.470 --> 16:40:51.480 align:start position:0% applications that need this bandwidth 16:40:51.480 --> 16:40:52.786 align:start position:0% applications that need this bandwidth are<16:40:51.776> generally<16:40:52.020> split<16:40:52.320> into<16:40:52.436> two<16:40:52.680> different 16:40:52.786 --> 16:40:52.796 align:start position:0% are generally split into two different 16:40:52.796 --> 16:40:54.010 align:start position:0% are generally split into two different categories 16:40:54.010 --> 16:40:54.020 align:start position:0% categories 16:40:54.020 --> 16:40:57.890 align:start position:0% categories latency<16:40:55.040> sensitive<16:40:56.456> and 16:40:57.890 --> 16:40:57.900 align:start position:0% latency sensitive and 16:40:57.900 --> 16:41:01.130 align:start position:0% latency sensitive and latency<16:40:58.680> insensitive<16:40:59.456> latency<16:41:00.416> sensitive 16:41:01.130 --> 16:41:01.140 align:start position:0% latency insensitive latency sensitive 16:41:01.140 --> 16:41:02.810 align:start position:0% latency insensitive latency sensitive applications<16:41:01.616> are<16:41:01.980> appropriately<16:41:02.400> named 16:41:02.810 --> 16:41:02.820 align:start position:0% applications are appropriately named 16:41:02.820 --> 16:41:05.210 align:start position:0% applications are appropriately named these<16:41:03.596> are<16:41:03.720> applications<16:41:04.200> that<16:41:04.616> are<16:41:04.740> affected 16:41:05.210 --> 16:41:05.220 align:start position:0% these are applications that are affected 16:41:05.220 --> 16:41:10.606 align:start position:0% these are applications that are affected by<16:41:05.756> latency<16:41:06.680> or<16:41:07.680> a<16:41:08.276> delay<16:41:08.520> caused<16:41:09.000> by<16:41:09.180> a<16:41:09.360> device 16:41:10.606 --> 16:41:10.616 align:start position:0% by latency or a delay caused by a device 16:41:10.616 --> 16:41:14.330 align:start position:0% by latency or a delay caused by a device so<16:41:11.160> latency<16:41:11.700> is<16:41:12.596> sort<16:41:12.840> of<16:41:13.020> the<16:41:13.436> slowness<16:41:13.980> with 16:41:14.330 --> 16:41:14.340 align:start position:0% so latency is sort of the slowness with 16:41:14.340 --> 16:41:17.210 align:start position:0% so latency is sort of the slowness with which<16:41:14.520> bandwidth<16:41:15.296> occurs<16:41:15.720> or<16:41:16.436> not<16:41:16.740> living<16:41:16.980> up 16:41:17.210 --> 16:41:17.220 align:start position:0% which bandwidth occurs or not living up 16:41:17.220 --> 16:41:18.890 align:start position:0% which bandwidth occurs or not living up to<16:41:17.340> its<16:41:17.580> full<16:41:17.640> potential 16:41:18.890 --> 16:41:18.900 align:start position:0% to its full potential 16:41:18.900 --> 16:41:21.406 align:start position:0% to its full potential so<16:41:19.796> an<16:41:20.096> application<16:41:20.456> that<16:41:20.700> needs<16:41:20.936> bandwidth 16:41:21.406 --> 16:41:21.416 align:start position:0% so an application that needs bandwidth 16:41:21.416 --> 16:41:24.170 align:start position:0% so an application that needs bandwidth because<16:41:21.660> of<16:41:21.900> its<16:41:22.256> Effectiveness<16:41:22.980> is<16:41:23.700> impacted 16:41:24.170 --> 16:41:24.180 align:start position:0% because of its Effectiveness is impacted 16:41:24.180 --> 16:41:26.446 align:start position:0% because of its Effectiveness is impacted by<16:41:24.416> lag<16:41:24.660> time<16:41:24.900> for<16:41:25.256> example<16:41:25.560> applications 16:41:26.446 --> 16:41:26.456 align:start position:0% by lag time for example applications 16:41:26.456 --> 16:41:29.330 align:start position:0% by lag time for example applications that<16:41:26.756> use<16:41:27.000> VoIP<16:41:27.596> fall<16:41:28.140> into<16:41:28.380> this<16:41:28.680> category<16:41:29.160> or 16:41:29.330 --> 16:41:29.340 align:start position:0% that use VoIP fall into this category or 16:41:29.340 --> 16:41:31.786 align:start position:0% that use VoIP fall into this category or voice<16:41:29.520> over<16:41:29.756> IP<16:41:30.240> they're<16:41:30.840> latency<16:41:31.200> sensitive 16:41:31.786 --> 16:41:31.796 align:start position:0% voice over IP they're latency sensitive 16:41:31.796 --> 16:41:34.130 align:start position:0% voice over IP they're latency sensitive because<16:41:32.040> lag<16:41:32.400> time<16:41:32.640> could<16:41:33.060> disrupt<16:41:33.596> a<16:41:33.840> video 16:41:34.130 --> 16:41:34.140 align:start position:0% because lag time could disrupt a video 16:41:34.140 --> 16:41:37.310 align:start position:0% because lag time could disrupt a video or<16:41:34.740> a<16:41:34.916> phone<16:41:35.096> call<16:41:35.416> latency<16:41:36.416> insensitive 16:41:37.310 --> 16:41:37.320 align:start position:0% or a phone call latency insensitive 16:41:37.320 --> 16:41:39.530 align:start position:0% or a phone call latency insensitive applications<16:41:37.860> still<16:41:38.640> require<16:41:38.820> bandwidth<16:41:39.416> but 16:41:39.530 --> 16:41:39.540 align:start position:0% applications still require bandwidth but 16:41:39.540 --> 16:41:41.330 align:start position:0% applications still require bandwidth but for<16:41:39.660> a<16:41:39.776> very<16:41:39.900> different<16:41:40.140> reason<16:41:40.380> these<16:41:41.220> don't 16:41:41.330 --> 16:41:41.340 align:start position:0% for a very different reason these don't 16:41:41.340 --> 16:41:44.030 align:start position:0% for a very different reason these don't have<16:41:41.580> video<16:41:42.060> or<16:41:42.540> voice<16:41:42.776> transfer<16:41:43.380> so<16:41:43.916> the 16:41:44.030 --> 16:41:44.040 align:start position:0% have video or voice transfer so the 16:41:44.040 --> 16:41:46.670 align:start position:0% have video or voice transfer so the bandwidth<16:41:44.640> is<16:41:44.936> just<16:41:45.240> as<16:41:45.720> important<16:41:46.320> to<16:41:46.560> them 16:41:46.670 --> 16:41:46.680 align:start position:0% bandwidth is just as important to them 16:41:46.680 --> 16:41:49.390 align:start position:0% bandwidth is just as important to them but<16:41:47.400> the<16:41:48.060> latency<16:41:48.480> doesn't<16:41:48.840> really<16:41:49.080> matter 16:41:49.390 --> 16:41:49.400 align:start position:0% but the latency doesn't really matter 16:41:49.400 --> 16:41:51.470 align:start position:0% but the latency doesn't really matter these<16:41:50.400> applications<16:41:50.700> are<16:41:50.936> those<16:41:51.116> that<16:41:51.360> are 16:41:51.470 --> 16:41:51.480 align:start position:0% these applications are those that are 16:41:51.480 --> 16:41:53.210 align:start position:0% these applications are those that are used<16:41:51.660> to<16:41:51.840> transfer<16:41:52.256> large<16:41:52.436> amount<16:41:52.740> of<16:41:52.860> data 16:41:53.210 --> 16:41:53.220 align:start position:0% used to transfer large amount of data 16:41:53.220 --> 16:41:56.390 align:start position:0% used to transfer large amount of data like<16:41:53.640> during<16:41:53.880> backup<16:41:54.416> or<16:41:55.140> FTP 16:41:56.390 --> 16:41:56.400 align:start position:0% like during backup or FTP 16:41:56.400 --> 16:41:58.670 align:start position:0% like during backup or FTP just<16:41:56.820> to<16:41:57.000> cover<16:41:57.116> this<16:41:57.360> one<16:41:57.596> more<16:41:57.776> time<16:41:58.020> and 16:41:58.670 --> 16:41:58.680 align:start position:0% just to cover this one more time and 16:41:58.680 --> 16:41:59.746 align:start position:0% just to cover this one more time and perhaps<16:41:58.916> say<16:41:59.040> it<16:41:59.220> in<16:41:59.276> a<16:41:59.400> different<16:41:59.520> way 16:41:59.746 --> 16:41:59.756 align:start position:0% perhaps say it in a different way 16:41:59.756 --> 16:42:02.630 align:start position:0% perhaps say it in a different way latency<16:42:00.720> sensitive<16:42:01.320> would<16:42:01.680> be<16:42:01.860> meaning<16:42:02.220> that 16:42:02.630 --> 16:42:02.640 align:start position:0% latency sensitive would be meaning that 16:42:02.640 --> 16:42:04.906 align:start position:0% latency sensitive would be meaning that if<16:42:03.116> something<16:42:03.480> for<16:42:03.840> some<16:42:04.020> reason<16:42:04.200> I<16:42:04.500> have<16:42:04.680> a 16:42:04.906 --> 16:42:04.916 align:start position:0% if something for some reason I have a 16:42:04.916 --> 16:42:08.150 align:start position:0% if something for some reason I have a huge<16:42:05.160> uh<16:42:05.880> amount<16:42:06.296> of<16:42:06.416> traffic<16:42:06.660> then<16:42:07.616> I'm<16:42:07.980> going 16:42:08.150 --> 16:42:08.160 align:start position:0% huge uh amount of traffic then I'm going 16:42:08.160 --> 16:42:10.246 align:start position:0% huge uh amount of traffic then I'm going to<16:42:08.340> start<16:42:08.580> seeing<16:42:09.000> a<16:42:09.240> degradation<16:42:09.776> in<16:42:10.020> service 16:42:10.246 --> 16:42:10.256 align:start position:0% to start seeing a degradation in service 16:42:10.256 --> 16:42:12.890 align:start position:0% to start seeing a degradation in service when<16:42:10.980> it<16:42:11.160> comes<16:42:11.400> to<16:42:11.580> my<16:42:11.820> latency<16:42:12.240> sensitive 16:42:12.890 --> 16:42:12.900 align:start position:0% when it comes to my latency sensitive 16:42:12.900 --> 16:42:15.406 align:start position:0% when it comes to my latency sensitive applications<16:42:13.320> such<16:42:13.860> as<16:42:13.980> VoIP<16:42:14.400> for<16:42:15.000> instance<16:42:15.180> I 16:42:15.406 --> 16:42:15.416 align:start position:0% applications such as VoIP for instance I 16:42:15.416 --> 16:42:17.330 align:start position:0% applications such as VoIP for instance I need<16:42:15.480> to<16:42:15.596> make<16:42:15.776> sure<16:42:16.080> that<16:42:16.680> no<16:42:16.916> matter<16:42:17.040> when 16:42:17.330 --> 16:42:17.340 align:start position:0% need to make sure that no matter when 16:42:17.340 --> 16:42:20.150 align:start position:0% need to make sure that no matter when I'm<16:42:17.520> talking<16:42:17.820> over<16:42:18.540> my<16:42:18.840> VoIP<16:42:19.200> phone<16:42:19.436> it's 16:42:20.150 --> 16:42:20.160 align:start position:0% I'm talking over my VoIP phone it's 16:42:20.160 --> 16:42:22.426 align:start position:0% I'm talking over my VoIP phone it's still<16:42:20.400> reaching<16:42:20.880> the<16:42:21.240> end<16:42:21.360> person<16:42:21.660> in<16:42:22.256> the 16:42:22.426 --> 16:42:22.436 align:start position:0% still reaching the end person in the 16:42:22.436 --> 16:42:24.470 align:start position:0% still reaching the end person in the same<16:42:22.616> degree<16:42:23.096> of<16:42:23.276> quality<16:42:23.700> it<16:42:24.180> can't<16:42:24.360> be 16:42:24.470 --> 16:42:24.480 align:start position:0% same degree of quality it can't be 16:42:24.480 --> 16:42:26.210 align:start position:0% same degree of quality it can't be dropping<16:42:24.900> a<16:42:25.020> lot<16:42:25.140> of<16:42:25.256> packets<16:42:25.616> because<16:42:25.860> if<16:42:26.096> it 16:42:26.210 --> 16:42:26.220 align:start position:0% dropping a lot of packets because if it 16:42:26.220 --> 16:42:27.350 align:start position:0% dropping a lot of packets because if it is<16:42:26.340> then<16:42:26.580> they're<16:42:26.756> not<16:42:26.880> going<16:42:27.000> to<16:42:27.060> be<16:42:27.180> able<16:42:27.296> to 16:42:27.350 --> 16:42:27.360 align:start position:0% is then they're not going to be able to 16:42:27.360 --> 16:42:29.690 align:start position:0% is then they're not going to be able to hear<16:42:27.540> my<16:42:27.776> voice<16:42:27.956> very<16:42:28.256> clearly<16:42:28.560> with<16:42:29.276> latency 16:42:29.690 --> 16:42:29.700 align:start position:0% hear my voice very clearly with latency 16:42:29.700 --> 16:42:32.150 align:start position:0% hear my voice very clearly with latency insensitive<16:42:30.480> the<16:42:31.080> traffic<16:42:31.256> can<16:42:31.616> modulate 16:42:32.150 --> 16:42:32.160 align:start position:0% insensitive the traffic can modulate 16:42:32.160 --> 16:42:34.606 align:start position:0% insensitive the traffic can modulate quite<16:42:32.456> a<16:42:32.700> degree<16:42:33.116> because<16:42:33.776> as<16:42:34.080> long<16:42:34.256> as<16:42:34.380> the 16:42:34.606 --> 16:42:34.616 align:start position:0% quite a degree because as long as the 16:42:34.616 --> 16:42:36.710 align:start position:0% quite a degree because as long as the files<16:42:34.980> get<16:42:35.160> from<16:42:35.400> one<16:42:35.580> end<16:42:35.700> to<16:42:35.880> the<16:42:36.060> other<16:42:36.180> if 16:42:36.710 --> 16:42:36.720 align:start position:0% files get from one end to the other if 16:42:36.720 --> 16:42:38.746 align:start position:0% files get from one end to the other if at<16:42:36.900> one<16:42:37.080> point<16:42:37.256> it's<16:42:37.500> transferring<16:42:38.040> at<16:42:38.220> 90 16:42:38.746 --> 16:42:38.756 align:start position:0% at one point it's transferring at 90 16:42:38.756 --> 16:42:40.310 align:start position:0% at one point it's transferring at 90 megabits<16:42:39.360> per<16:42:39.480> second<16:42:39.596> and<16:42:39.900> the<16:42:40.080> next<16:42:40.140> the 16:42:40.310 --> 16:42:40.320 align:start position:0% megabits per second and the next the 16:42:40.320 --> 16:42:42.230 align:start position:0% megabits per second and the next the transmit<16:42:40.740> one<16:42:40.916> gigabit<16:42:41.220> per<16:42:41.400> second<16:42:41.580> it's 16:42:42.230 --> 16:42:42.240 align:start position:0% transmit one gigabit per second it's 16:42:42.240 --> 16:42:44.266 align:start position:0% transmit one gigabit per second it's still<16:42:42.480> going<16:42:42.720> to<16:42:43.140> get<16:42:43.560> over<16:42:43.796> to<16:42:44.040> the<16:42:44.160> other 16:42:44.266 --> 16:42:44.276 align:start position:0% still going to get over to the other 16:42:44.276 --> 16:42:46.190 align:start position:0% still going to get over to the other place<16:42:44.580> but<16:42:45.116> it<16:42:45.240> doesn't<16:42:45.296> really<16:42:45.540> matter<16:42:45.776> if<16:42:46.020> I 16:42:46.190 --> 16:42:46.200 align:start position:0% place but it doesn't really matter if I 16:42:46.200 --> 16:42:47.990 align:start position:0% place but it doesn't really matter if I don't<16:42:46.320> receive<16:42:46.560> the<16:42:46.796> packets<16:42:47.160> in<16:42:47.580> a<16:42:47.756> sort<16:42:47.880> of 16:42:47.990 --> 16:42:48.000 align:start position:0% don't receive the packets in a sort of 16:42:48.000 --> 16:42:50.510 align:start position:0% don't receive the packets in a sort of steady<16:42:48.360> stream<16:42:48.720> so<16:42:49.380> in<16:42:49.616> this<16:42:49.740> case<16:42:49.980> the 16:42:50.510 --> 16:42:50.520 align:start position:0% steady stream so in this case the 16:42:50.520 --> 16:42:52.550 align:start position:0% steady stream so in this case the latency<16:42:50.820> doesn't<16:42:51.240> really<16:42:51.720> matter<16:42:51.956> as<16:42:52.320> much<16:42:52.436> as 16:42:52.550 --> 16:42:52.560 align:start position:0% latency doesn't really matter as much as 16:42:52.560 --> 16:42:54.106 align:start position:0% latency doesn't really matter as much as the<16:42:52.740> fact<16:42:52.916> that<16:42:53.160> it<16:42:53.276> simply<16:42:53.520> gets<16:42:53.820> from<16:42:53.936> one 16:42:54.106 --> 16:42:54.116 align:start position:0% the fact that it simply gets from one 16:42:54.116 --> 16:42:56.030 align:start position:0% the fact that it simply gets from one place<16:42:54.296> to<16:42:54.480> the<16:42:54.660> other<16:42:54.776> it<16:42:55.436> within<16:42:55.796> a<16:42:55.916> certain 16:42:56.030 --> 16:42:56.040 align:start position:0% place to the other it within a certain 16:42:56.040 --> 16:42:57.470 align:start position:0% place to the other it within a certain degree<16:42:56.160> of<16:42:56.340> time 16:42:57.470 --> 16:42:57.480 align:start position:0% degree of time 16:42:57.480 --> 16:43:01.730 align:start position:0% degree of time so<16:42:58.140> a<16:42:58.680> very<16:42:58.860> important<16:42:59.480> qos<16:43:00.480> strategy<16:43:01.140> to<16:43:01.616> help 16:43:01.730 --> 16:43:01.740 align:start position:0% so a very important qos strategy to help 16:43:01.740 --> 16:43:05.330 align:start position:0% so a very important qos strategy to help exist<16:43:02.660> to<16:43:03.660> help<16:43:03.776> control<16:43:04.200> the<16:43:04.616> flow<16:43:04.860> of<16:43:04.980> data 16:43:05.330 --> 16:43:05.340 align:start position:0% exist to help control the flow of data 16:43:05.340 --> 16:43:07.310 align:start position:0% exist to help control the flow of data through<16:43:05.520> a<16:43:05.700> network<16:43:05.820> is<16:43:06.660> called<16:43:06.956> traffic 16:43:07.310 --> 16:43:07.320 align:start position:0% through a network is called traffic 16:43:07.320 --> 16:43:08.510 align:start position:0% through a network is called traffic shaping 16:43:08.510 --> 16:43:08.520 align:start position:0% shaping 16:43:08.520 --> 16:43:11.210 align:start position:0% shaping its<16:43:09.060> main<16:43:09.180> purpose<16:43:09.596> is<16:43:09.900> to<16:43:10.140> reduce<16:43:10.436> latency 16:43:11.210 --> 16:43:11.220 align:start position:0% its main purpose is to reduce latency 16:43:11.220 --> 16:43:13.370 align:start position:0% its main purpose is to reduce latency which<16:43:11.756> it<16:43:11.880> does<16:43:12.060> by<16:43:12.296> controlling<16:43:12.900> the<16:43:13.140> amount 16:43:13.370 --> 16:43:13.380 align:start position:0% which it does by controlling the amount 16:43:13.380 --> 16:43:15.890 align:start position:0% which it does by controlling the amount of<16:43:13.500> data<16:43:13.860> passing<16:43:14.400> through<16:43:14.520> a<16:43:14.756> network<16:43:14.900> data 16:43:15.890 --> 16:43:15.900 align:start position:0% of data passing through a network data 16:43:15.900 --> 16:43:17.926 align:start position:0% of data passing through a network data traffic<16:43:16.020> is<16:43:16.616> sort<16:43:16.860> of<16:43:17.040> split<16:43:17.400> into<16:43:17.640> different 16:43:17.926 --> 16:43:17.936 align:start position:0% traffic is sort of split into different 16:43:17.936 --> 16:43:20.030 align:start position:0% traffic is sort of split into different categories<16:43:18.540> and<16:43:19.200> put<16:43:19.380> put<16:43:19.616> in<16:43:19.796> something 16:43:20.030 --> 16:43:20.040 align:start position:0% categories and put put in something 16:43:20.040 --> 16:43:23.510 align:start position:0% categories and put put in something called<16:43:20.456> a<16:43:21.060> queue<16:43:21.416> a<16:43:22.020> queue<16:43:22.320> by<16:43:22.436> the<16:43:22.616> way<16:43:22.680> would 16:43:23.510 --> 16:43:23.520 align:start position:0% called a queue a queue by the way would 16:43:23.520 --> 16:43:26.510 align:start position:0% called a queue a queue by the way would be<16:43:23.700> something<16:43:23.936> like<16:43:24.360> a<16:43:24.660> line<16:43:25.276> basically<16:43:26.276> I'm 16:43:26.510 --> 16:43:26.520 align:start position:0% be something like a line basically I'm 16:43:26.520 --> 16:43:27.946 align:start position:0% be something like a line basically I'm going<16:43:26.700> to<16:43:26.756> put<16:43:27.060> certain<16:43:27.480> types<16:43:27.840> of 16:43:27.946 --> 16:43:27.956 align:start position:0% going to put certain types of 16:43:27.956 --> 16:43:29.990 align:start position:0% going to put certain types of information<16:43:28.140> into<16:43:28.680> one<16:43:29.040> queue<16:43:29.456> and<16:43:29.820> certain 16:43:29.990 --> 16:43:30.000 align:start position:0% information into one queue and certain 16:43:30.000 --> 16:43:32.210 align:start position:0% information into one queue and certain it<16:43:30.180> to<16:43:30.360> another<16:43:30.480> and<16:43:31.200> those<16:43:31.380> cues<16:43:31.796> are<16:43:32.096> going 16:43:32.210 --> 16:43:32.220 align:start position:0% it to another and those cues are going 16:43:32.220 --> 16:43:34.010 align:start position:0% it to another and those cues are going to<16:43:32.340> be<16:43:32.456> given<16:43:32.756> priority 16:43:34.010 --> 16:43:34.020 align:start position:0% to be given priority 16:43:34.020 --> 16:43:36.050 align:start position:0% to be given priority so<16:43:34.560> my<16:43:34.796> voice<16:43:34.980> application<16:43:35.456> is<16:43:35.700> going<16:43:35.880> to<16:43:36.000> have 16:43:36.050 --> 16:43:36.060 align:start position:0% so my voice application is going to have 16:43:36.060 --> 16:43:38.390 align:start position:0% so my voice application is going to have the<16:43:36.296> highest<16:43:36.596> priority<16:43:36.956> whereas<16:43:37.796> maybe<16:43:38.160> my 16:43:38.390 --> 16:43:38.400 align:start position:0% the highest priority whereas maybe my 16:43:38.400 --> 16:43:40.970 align:start position:0% the highest priority whereas maybe my FTP<16:43:38.880> will<16:43:39.540> have<16:43:39.776> a<16:43:39.956> bit<16:43:40.020> of<16:43:40.140> a<16:43:40.256> lower<16:43:40.380> priority 16:43:40.970 --> 16:43:40.980 align:start position:0% FTP will have a bit of a lower priority 16:43:40.980 --> 16:43:43.310 align:start position:0% FTP will have a bit of a lower priority now<16:43:41.820> there<16:43:42.116> are<16:43:42.240> quite<16:43:42.360> a<16:43:42.480> few<16:43:42.596> different<16:43:42.776> ways 16:43:43.310 --> 16:43:43.320 align:start position:0% now there are quite a few different ways 16:43:43.320 --> 16:43:45.406 align:start position:0% now there are quite a few different ways to<16:43:43.500> use<16:43:43.740> traffic<16:43:44.040> shaping<16:43:44.580> and<16:43:44.880> each<16:43:45.060> method 16:43:45.406 --> 16:43:45.416 align:start position:0% to use traffic shaping and each method 16:43:45.416 --> 16:43:47.446 align:start position:0% to use traffic shaping and each method has<16:43:45.596> its<16:43:45.900> own<16:43:45.956> benefit<16:43:46.200> and<16:43:47.040> needs<16:43:47.276> to<16:43:47.340> be 16:43:47.446 --> 16:43:47.456 align:start position:0% has its own benefit and needs to be 16:43:47.456 --> 16:43:50.086 align:start position:0% has its own benefit and needs to be chosen<16:43:47.820> based<16:43:48.180> on<16:43:48.296> the<16:43:48.540> circumstances<16:43:49.200> of<16:43:49.916> the 16:43:50.086 --> 16:43:50.096 align:start position:0% chosen based on the circumstances of the 16:43:50.096 --> 16:43:52.490 align:start position:0% chosen based on the circumstances of the situation<16:43:50.520> now<16:43:51.180> here<16:43:51.480> are<16:43:51.660> a<16:43:51.840> couple<16:43:52.080> of<16:43:52.320> the 16:43:52.490 --> 16:43:52.500 align:start position:0% situation now here are a couple of the 16:43:52.500 --> 16:43:55.010 align:start position:0% situation now here are a couple of the common<16:43:53.276> methods<16:43:53.820> actually<16:43:53.936> three 16:43:55.010 --> 16:43:55.020 align:start position:0% common methods actually three 16:43:55.020 --> 16:43:57.830 align:start position:0% common methods actually three first<16:43:55.436> is<16:43:55.680> shaping<16:43:56.096> by<16:43:56.276> application 16:43:57.830 --> 16:43:57.840 align:start position:0% first is shaping by application 16:43:57.840 --> 16:43:59.746 align:start position:0% first is shaping by application this<16:43:58.380> is<16:43:58.436> a<16:43:58.616> strategy<16:43:58.916> that<16:43:59.220> involves<16:43:59.580> the 16:43:59.746 --> 16:43:59.756 align:start position:0% this is a strategy that involves the 16:43:59.756 --> 16:44:01.906 align:start position:0% this is a strategy that involves the administrator<16:44:00.360> allowing<16:44:01.020> only<16:44:01.500> a<16:44:01.796> certain 16:44:01.906 --> 16:44:01.916 align:start position:0% administrator allowing only a certain 16:44:01.916 --> 16:44:03.766 align:start position:0% administrator allowing only a certain amount<16:44:02.160> of<16:44:02.276> bandwidth<16:44:02.820> to<16:44:02.936> be<16:44:03.060> used<16:44:03.240> by<16:44:03.660> a 16:44:03.766 --> 16:44:03.776 align:start position:0% amount of bandwidth to be used by a 16:44:03.776 --> 16:44:05.870 align:start position:0% amount of bandwidth to be used by a certain<16:44:03.956> application<16:44:04.500> for<16:44:05.276> instance<16:44:05.520> an 16:44:05.870 --> 16:44:05.880 align:start position:0% certain application for instance an 16:44:05.880 --> 16:44:09.230 align:start position:0% certain application for instance an admin<16:44:06.296> only<16:44:06.540> allows<16:44:07.080> a<16:44:07.500> VoIP<16:44:07.796> application<16:44:08.340> to 16:44:09.230 --> 16:44:09.240 align:start position:0% admin only allows a VoIP application to 16:44:09.240 --> 16:44:11.570 align:start position:0% admin only allows a VoIP application to use<16:44:09.596> for<16:44:10.256> instance<16:44:10.436> six<16:44:10.740> megabits<16:44:11.276> per<16:44:11.400> second 16:44:11.570 --> 16:44:11.580 align:start position:0% use for instance six megabits per second 16:44:11.580 --> 16:44:13.906 align:start position:0% use for instance six megabits per second and<16:44:11.880> it<16:44:12.000> can't<16:44:12.180> use<16:44:12.416> any<16:44:12.720> more<16:44:12.900> than<16:44:13.080> that<16:44:13.256> so 16:44:13.906 --> 16:44:13.916 align:start position:0% and it can't use any more than that so 16:44:13.916 --> 16:44:17.390 align:start position:0% and it can't use any more than that so in<16:44:14.160> some<16:44:14.340> ways<16:44:14.936> we<16:44:15.180> set<16:44:15.416> a<16:44:16.080> limit 16:44:17.390 --> 16:44:17.400 align:start position:0% in some ways we set a limit 16:44:17.400 --> 16:44:20.690 align:start position:0% in some ways we set a limit to<16:44:17.936> the<16:44:18.116> bandwidth<16:44:18.660> that's<16:44:19.200> going<16:44:19.436> to<16:44:19.560> be<16:44:19.740> used 16:44:20.690 --> 16:44:20.700 align:start position:0% to the bandwidth that's going to be used 16:44:20.700 --> 16:44:22.906 align:start position:0% to the bandwidth that's going to be used by<16:44:21.240> a<16:44:21.416> certain<16:44:21.540> protocol<16:44:21.956> or<16:44:22.616> a<16:44:22.740> certain 16:44:22.906 --> 16:44:22.916 align:start position:0% by a certain protocol or a certain 16:44:22.916 --> 16:44:24.106 align:start position:0% by a certain protocol or a certain application 16:44:24.106 --> 16:44:24.116 align:start position:0% application 16:44:24.116 --> 16:44:26.926 align:start position:0% application the<16:44:24.596> next<16:44:24.720> which<16:44:25.256> is<16:44:25.436> called<16:44:25.680> shaping<16:44:26.520> Network 16:44:26.926 --> 16:44:26.936 align:start position:0% the next which is called shaping Network 16:44:26.936 --> 16:44:29.266 align:start position:0% the next which is called shaping Network traffic<16:44:27.296> per<16:44:27.720> user<16:44:28.200> allows<16:44:28.980> the 16:44:29.266 --> 16:44:29.276 align:start position:0% traffic per user allows the 16:44:29.276 --> 16:44:30.650 align:start position:0% traffic per user allows the administrator<16:44:29.756> to<16:44:29.936> limit<16:44:30.060> the<16:44:30.296> bandwidth 16:44:30.650 --> 16:44:30.660 align:start position:0% administrator to limit the bandwidth 16:44:30.660 --> 16:44:33.106 align:start position:0% administrator to limit the bandwidth that<16:44:30.840> any<16:44:31.020> individual<16:44:31.500> user<16:44:31.980> can<16:44:32.160> use<16:44:32.340> now 16:44:33.106 --> 16:44:33.116 align:start position:0% that any individual user can use now 16:44:33.116 --> 16:44:34.906 align:start position:0% that any individual user can use now shaving<16:44:33.540> by<16:44:33.660> application<16:44:34.200> is<16:44:34.560> something<16:44:34.680> that 16:44:34.906 --> 16:44:34.916 align:start position:0% shaving by application is something that 16:44:34.916 --> 16:44:36.710 align:start position:0% shaving by application is something that we're<16:44:34.980> going<16:44:35.096> to<16:44:35.220> be<16:44:35.276> seeing<16:44:35.700> a<16:44:35.880> lot<16:44:36.000> now<16:44:36.240> on 16:44:36.710 --> 16:44:36.720 align:start position:0% we're going to be seeing a lot now on 16:44:36.720 --> 16:44:39.766 align:start position:0% we're going to be seeing a lot now on airplanes<16:44:37.380> and<16:44:38.096> trains<16:44:38.700> we<16:44:39.296> don't<16:44:39.416> want<16:44:39.660> to 16:44:39.766 --> 16:44:39.776 align:start position:0% airplanes and trains we don't want to 16:44:39.776 --> 16:44:42.890 align:start position:0% airplanes and trains we don't want to let<16:44:40.020> for<16:44:40.740> instance<16:44:40.980> people<16:44:41.220> use<16:44:41.520> Netflix<16:44:41.900> and 16:44:42.890 --> 16:44:42.900 align:start position:0% let for instance people use Netflix and 16:44:42.900 --> 16:44:44.446 align:start position:0% let for instance people use Netflix and YouTube<16:44:43.200> on<16:44:43.560> the<16:44:43.740> plane<16:44:43.916> because<16:44:44.160> there<16:44:44.340> are 16:44:44.446 --> 16:44:44.456 align:start position:0% YouTube on the plane because there are 16:44:44.456 --> 16:44:45.710 align:start position:0% YouTube on the plane because there are other<16:44:44.520> people<16:44:44.640> who<16:44:44.820> need<16:44:45.000> to<16:44:45.116> be<16:44:45.180> using<16:44:45.480> email 16:44:45.710 --> 16:44:45.720 align:start position:0% other people who need to be using email 16:44:45.720 --> 16:44:47.510 align:start position:0% other people who need to be using email and<16:44:46.140> so<16:44:46.320> we're<16:44:46.436> just<16:44:46.560> going<16:44:46.680> to<16:44:46.740> say<16:44:46.916> if<16:44:47.400> you 16:44:47.510 --> 16:44:47.520 align:start position:0% and so we're just going to say if you 16:44:47.520 --> 16:44:49.670 align:start position:0% and so we're just going to say if you want<16:44:47.580> to<16:44:47.700> do<16:44:47.820> bandwidth<16:44:48.480> for<16:44:48.720> video<16:44:49.080> we're<16:44:49.560> not 16:44:49.670 --> 16:44:49.680 align:start position:0% want to do bandwidth for video we're not 16:44:49.680 --> 16:44:51.710 align:start position:0% want to do bandwidth for video we're not going<16:44:49.796> to<16:44:49.916> allow<16:44:50.220> that<16:44:50.400> as<16:44:50.756> much<16:44:50.880> as<16:44:51.116> bandwidth 16:44:51.710 --> 16:44:51.720 align:start position:0% going to allow that as much as bandwidth 16:44:51.720 --> 16:44:52.990 align:start position:0% going to allow that as much as bandwidth for<16:44:51.840> say 16:44:52.990 --> 16:44:53.000 align:start position:0% for say 16:44:53.000 --> 16:44:57.050 align:start position:0% for say email<16:44:54.000> or<16:44:54.776> for<16:44:55.200> text<16:44:55.616> messaging<16:44:56.520> for<16:44:56.820> instance 16:44:57.050 --> 16:44:57.060 align:start position:0% email or for text messaging for instance 16:44:57.060 --> 16:44:59.030 align:start position:0% email or for text messaging for instance but<16:44:57.776> when<16:44:58.020> I'm<16:44:58.320> talking<16:44:58.560> about<16:44:58.796> Network 16:44:59.030 --> 16:44:59.040 align:start position:0% but when I'm talking about Network 16:44:59.040 --> 16:45:01.906 align:start position:0% but when I'm talking about Network traffic<16:44:59.400> per<16:44:59.820> user<16:45:00.240> I'm<16:45:00.956> allowing<16:45:01.500> specific 16:45:01.906 --> 16:45:01.916 align:start position:0% traffic per user I'm allowing specific 16:45:01.916 --> 16:45:03.350 align:start position:0% traffic per user I'm allowing specific users<16:45:02.340> to<16:45:02.520> have<16:45:02.700> a<16:45:02.880> certain<16:45:03.000> amount<16:45:03.240> of 16:45:03.350 --> 16:45:03.360 align:start position:0% users to have a certain amount of 16:45:03.360 --> 16:45:05.446 align:start position:0% users to have a certain amount of bandwidth<16:45:03.900> so<16:45:04.436> some<16:45:04.680> users<16:45:04.980> might<16:45:05.160> use<16:45:05.276> more 16:45:05.446 --> 16:45:05.456 align:start position:0% bandwidth so some users might use more 16:45:05.456 --> 16:45:07.010 align:start position:0% bandwidth so some users might use more bandwidth<16:45:05.880> than<16:45:06.000> others<16:45:06.240> and<16:45:06.360> sometimes<16:45:06.720> it 16:45:07.010 --> 16:45:07.020 align:start position:0% bandwidth than others and sometimes it 16:45:07.020 --> 16:45:09.050 align:start position:0% bandwidth than others and sometimes it isn't<16:45:07.256> all<16:45:07.436> for<16:45:07.616> work<16:45:07.860> reasons<16:45:08.340> for<16:45:08.880> instance 16:45:09.050 --> 16:45:09.060 align:start position:0% isn't all for work reasons for instance 16:45:09.060 --> 16:45:10.670 align:start position:0% isn't all for work reasons for instance let's<16:45:09.240> say<16:45:09.416> that<16:45:09.540> Anthony<16:45:09.776> from<16:45:10.140> sales<16:45:10.320> is 16:45:10.670 --> 16:45:10.680 align:start position:0% let's say that Anthony from sales is 16:45:10.680 --> 16:45:12.286 align:start position:0% let's say that Anthony from sales is constantly<16:45:10.980> streaming<16:45:11.400> video<16:45:11.580> or<16:45:11.880> audio<16:45:12.060> to 16:45:12.286 --> 16:45:12.296 align:start position:0% constantly streaming video or audio to 16:45:12.296 --> 16:45:14.086 align:start position:0% constantly streaming video or audio to his<16:45:12.480> computer<16:45:12.720> this<16:45:13.436> is<16:45:13.560> using<16:45:13.796> a<16:45:13.916> lot<16:45:13.980> of 16:45:14.086 --> 16:45:14.096 align:start position:0% his computer this is using a lot of 16:45:14.096 --> 16:45:16.070 align:start position:0% his computer this is using a lot of bandwidth<16:45:14.640> so<16:45:15.000> now<16:45:15.116> the<16:45:15.296> discipline<16:45:15.596> part<16:45:15.900> of 16:45:16.070 --> 16:45:16.080 align:start position:0% bandwidth so now the discipline part of 16:45:16.080 --> 16:45:17.926 align:start position:0% bandwidth so now the discipline part of this<16:45:16.200> may<16:45:16.436> not<16:45:16.616> be<16:45:16.740> up<16:45:16.916> to<16:45:17.096> the<16:45:17.220> administrator 16:45:17.926 --> 16:45:17.936 align:start position:0% this may not be up to the administrator 16:45:17.936 --> 16:45:20.570 align:start position:0% this may not be up to the administrator but<16:45:18.360> he<16:45:18.956> or<16:45:19.140> she<16:45:19.320> can<16:45:19.616> certainly<16:45:19.980> limit<16:45:20.276> the 16:45:20.570 --> 16:45:20.580 align:start position:0% but he or she can certainly limit the 16:45:20.580 --> 16:45:22.246 align:start position:0% but he or she can certainly limit the amount<16:45:20.820> of<16:45:20.880> bandwidth<16:45:21.360> Anthony<16:45:21.540> is<16:45:21.900> allowed 16:45:22.246 --> 16:45:22.256 align:start position:0% amount of bandwidth Anthony is allowed 16:45:22.256 --> 16:45:25.550 align:start position:0% amount of bandwidth Anthony is allowed to<16:45:22.380> use<16:45:22.616> so<16:45:23.340> if<16:45:23.640> each<16:45:23.820> and<16:45:24.060> visual<16:45:24.720> for 16:45:25.550 --> 16:45:25.560 align:start position:0% to use so if each and visual for 16:45:25.560 --> 16:45:27.946 align:start position:0% to use so if each and visual for instance<16:45:25.740> Anthony<16:45:26.040> is<16:45:26.400> limited<16:45:26.880> to<16:45:27.116> 256 16:45:27.946 --> 16:45:27.956 align:start position:0% instance Anthony is limited to 256 16:45:27.956 --> 16:45:29.990 align:start position:0% instance Anthony is limited to 256 kilobits<16:45:28.560> per<16:45:28.680> second<16:45:28.916> it's<16:45:29.520> not<16:45:29.700> going<16:45:29.880> to 16:45:29.990 --> 16:45:30.000 align:start position:0% kilobits per second it's not going to 16:45:30.000 --> 16:45:32.446 align:start position:0% kilobits per second it's not going to access<16:45:30.240> what<16:45:30.956> he<16:45:31.140> can<16:45:31.320> access<16:45:31.500> just<16:45:32.040> how<16:45:32.276> fast 16:45:32.446 --> 16:45:32.456 align:start position:0% access what he can access just how fast 16:45:32.456 --> 16:45:34.730 align:start position:0% access what he can access just how fast he's<16:45:32.640> able<16:45:32.936> to<16:45:33.060> access<16:45:33.296> it<16:45:33.660> so<16:45:34.200> whereas<16:45:34.500> this 16:45:34.730 --> 16:45:34.740 align:start position:0% he's able to access it so whereas this 16:45:34.740 --> 16:45:36.106 align:start position:0% he's able to access it so whereas this is<16:45:34.796> really<16:45:35.040> doing<16:45:35.276> it<16:45:35.456> shipping<16:45:35.936> by 16:45:36.106 --> 16:45:36.116 align:start position:0% is really doing it shipping by 16:45:36.116 --> 16:45:37.786 align:start position:0% is really doing it shipping by application<16:45:36.480> based<16:45:36.956> on<16:45:37.080> the<16:45:37.380> type<16:45:37.616> of 16:45:37.786 --> 16:45:37.796 align:start position:0% application based on the type of 16:45:37.796 --> 16:45:39.710 align:start position:0% application based on the type of information<16:45:38.240> shaping<16:45:39.240> the<16:45:39.296> network<16:45:39.416> traffic 16:45:39.710 --> 16:45:39.720 align:start position:0% information shaping the network traffic 16:45:39.720 --> 16:45:41.086 align:start position:0% information shaping the network traffic per<16:45:40.080> user 16:45:41.086 --> 16:45:41.096 align:start position:0% per user 16:45:41.096 --> 16:45:44.030 align:start position:0% per user is<16:45:41.640> on<16:45:41.936> an<16:45:42.060> individual<16:45:42.480> basis<16:45:42.900> and<16:45:43.380> this<16:45:43.560> way<16:45:43.740> I 16:45:44.030 --> 16:45:44.040 align:start position:0% is on an individual basis and this way I 16:45:44.040 --> 16:45:46.550 align:start position:0% is on an individual basis and this way I can<16:45:44.160> give<16:45:44.340> each<16:45:44.580> user 16:45:46.550 --> 16:45:46.560 align:start position:0% can give each user 16:45:46.560 --> 16:45:51.190 align:start position:0% can give each user let's<16:45:46.916> say<16:45:47.096> Anthony<16:45:47.456> Maria 16:45:51.190 --> 16:45:51.200 align:start position:0% 16:45:51.200 --> 16:45:55.190 align:start position:0% Amy<16:45:52.220> each<16:45:53.220> a<16:45:53.580> certain<16:45:53.756> degree 16:45:55.190 --> 16:45:55.200 align:start position:0% Amy each a certain degree 16:45:55.200 --> 16:45:58.490 align:start position:0% Amy each a certain degree of<16:45:55.740> bandwidth 16:45:58.490 --> 16:45:58.500 align:start position:0% 16:45:58.500 --> 16:46:01.010 align:start position:0% so<16:45:58.916> that<16:45:59.040> no<16:45:59.276> person<16:45:59.580> can<16:46:00.360> use<16:46:00.540> one<16:46:00.720> more<16:46:00.900> than 16:46:01.010 --> 16:46:01.020 align:start position:0% so that no person can use one more than 16:46:01.020 --> 16:46:03.050 align:start position:0% so that no person can use one more than the<16:46:01.200> other<16:46:01.320> of<16:46:01.916> course<16:46:02.040> a<16:46:02.276> downside<16:46:02.700> with<16:46:02.936> this 16:46:03.050 --> 16:46:03.060 align:start position:0% the other of course a downside with this 16:46:03.060 --> 16:46:05.570 align:start position:0% the other of course a downside with this is<16:46:03.360> if<16:46:03.540> Amy's<16:46:03.900> only<16:46:04.140> using<16:46:04.680> let's<16:46:05.160> say<16:46:05.340> 10 16:46:05.570 --> 16:46:05.580 align:start position:0% is if Amy's only using let's say 10 16:46:05.580 --> 16:46:08.570 align:start position:0% is if Amy's only using let's say 10 kilobits<16:46:06.180> per<16:46:06.360> second<16:46:06.540> to<16:46:06.956> send<16:46:07.140> emails<16:46:07.680> and 16:46:08.570 --> 16:46:08.580 align:start position:0% kilobits per second to send emails and 16:46:08.580 --> 16:46:11.810 align:start position:0% kilobits per second to send emails and Maria<16:46:08.820> is<16:46:09.416> on<16:46:09.660> the<16:46:09.956> video<16:46:10.380> team<16:46:10.740> and<16:46:11.340> is<16:46:11.520> trying 16:46:11.810 --> 16:46:11.820 align:start position:0% Maria is on the video team and is trying 16:46:11.820 --> 16:46:15.470 align:start position:0% Maria is on the video team and is trying to<16:46:12.116> use<16:46:12.480> all<16:46:12.900> of<16:46:13.020> her<16:46:13.200> 256<16:46:14.060> she<16:46:15.060> might<16:46:15.240> be<16:46:15.360> able 16:46:15.470 --> 16:46:15.480 align:start position:0% to use all of her 256 she might be able 16:46:15.480 --> 16:46:16.970 align:start position:0% to use all of her 256 she might be able to<16:46:15.596> use<16:46:15.720> some<16:46:15.840> of<16:46:16.020> Amy's<16:46:16.320> but<16:46:16.560> because<16:46:16.680> of<16:46:16.916> the 16:46:16.970 --> 16:46:16.980 align:start position:0% to use some of Amy's but because of the 16:46:16.980 --> 16:46:19.310 align:start position:0% to use some of Amy's but because of the way<16:46:17.096> we've<16:46:17.276> shaped<16:46:17.640> this<16:46:17.756> per<16:46:18.180> user<16:46:18.596> Marie 16:46:19.310 --> 16:46:19.320 align:start position:0% way we've shaped this per user Marie 16:46:19.320 --> 16:46:21.350 align:start position:0% way we've shaped this per user Marie doesn't<16:46:19.500> get<16:46:19.680> any<16:46:19.860> more<16:46:20.096> and<16:46:20.820> sometimes<16:46:21.240> what 16:46:21.350 --> 16:46:21.360 align:start position:0% doesn't get any more and sometimes what 16:46:21.360 --> 16:46:23.990 align:start position:0% doesn't get any more and sometimes what we'll<16:46:21.540> do<16:46:21.720> is<16:46:21.776> give<16:46:22.080> people<16:46:22.320> in<16:46:22.860> certain<16:46:23.580> roles 16:46:23.990 --> 16:46:24.000 align:start position:0% we'll do is give people in certain roles 16:46:24.000 --> 16:46:26.870 align:start position:0% we'll do is give people in certain roles the<16:46:24.360> company<16:46:24.776> a<16:46:25.680> little<16:46:25.916> more<16:46:26.220> traffic<16:46:26.520> or 16:46:26.870 --> 16:46:26.880 align:start position:0% the company a little more traffic or 16:46:26.880 --> 16:46:29.086 align:start position:0% the company a little more traffic or bandwidth<16:46:27.296> allowability<16:46:27.840> than<16:46:28.616> some<16:46:28.916> of<16:46:28.980> the 16:46:29.086 --> 16:46:29.096 align:start position:0% bandwidth allowability than some of the 16:46:29.096 --> 16:46:30.586 align:start position:0% bandwidth allowability than some of the others<16:46:29.400> for<16:46:29.640> instance<16:46:29.820> accounting<16:46:30.360> probably 16:46:30.586 --> 16:46:30.596 align:start position:0% others for instance accounting probably 16:46:30.596 --> 16:46:32.810 align:start position:0% others for instance accounting probably doesn't<16:46:30.840> need<16:46:31.080> as<16:46:31.256> much<16:46:31.436> as<16:46:32.096> our<16:46:32.400> Graphics 16:46:32.810 --> 16:46:32.820 align:start position:0% doesn't need as much as our Graphics 16:46:32.820 --> 16:46:33.766 align:start position:0% doesn't need as much as our Graphics team 16:46:33.766 --> 16:46:33.776 align:start position:0% team 16:46:33.776 --> 16:46:35.330 align:start position:0% team finally<16:46:34.436> we<16:46:34.680> have<16:46:34.796> something<16:46:35.040> called 16:46:35.330 --> 16:46:35.340 align:start position:0% finally we have something called 16:46:35.340 --> 16:46:37.730 align:start position:0% finally we have something called priority<16:46:35.880> shaping<16:46:36.480> which<16:46:37.020> is<16:46:37.140> the<16:46:37.380> way<16:46:37.560> to 16:46:37.730 --> 16:46:37.740 align:start position:0% priority shaping which is the way to 16:46:37.740 --> 16:46:39.586 align:start position:0% priority shaping which is the way to allow<16:46:38.040> more<16:46:38.340> bandwidth<16:46:38.820> to<16:46:39.000> to<16:46:39.180> those<16:46:39.416> who 16:46:39.586 --> 16:46:39.596 align:start position:0% allow more bandwidth to to those who 16:46:39.596 --> 16:46:41.150 align:start position:0% allow more bandwidth to to those who require<16:46:39.840> it<16:46:40.140> most<16:46:40.320> sort<16:46:40.740> of<16:46:40.860> what<16:46:40.980> I'm 16:46:41.150 --> 16:46:41.160 align:start position:0% require it most sort of what I'm 16:46:41.160 --> 16:46:42.286 align:start position:0% require it most sort of what I'm referring<16:46:41.520> to 16:46:42.286 --> 16:46:42.296 align:start position:0% referring to 16:46:42.296 --> 16:46:44.630 align:start position:0% referring to here<16:46:42.776> for<16:46:43.436> example<16:46:43.680> in<16:46:43.916> a<16:46:44.040> school<16:46:44.160> system<16:46:44.400> the 16:46:44.630 --> 16:46:44.640 align:start position:0% here for example in a school system the 16:46:44.640 --> 16:46:46.130 align:start position:0% here for example in a school system the teachers<16:46:45.000> need<16:46:45.240> more<16:46:45.416> bandwidth<16:46:45.900> in<16:46:46.020> the 16:46:46.130 --> 16:46:46.140 align:start position:0% teachers need more bandwidth in the 16:46:46.140 --> 16:46:48.406 align:start position:0% teachers need more bandwidth in the students<16:46:46.436> so<16:46:46.860> the<16:46:46.980> network<16:46:47.096> admin<16:46:47.640> shapes<16:46:48.180> the 16:46:48.406 --> 16:46:48.416 align:start position:0% students so the network admin shapes the 16:46:48.416 --> 16:46:50.690 align:start position:0% students so the network admin shapes the traffic<16:46:48.660> again<16:46:49.616> we<16:46:49.916> have<16:46:50.040> that<16:46:50.220> great<16:46:50.456> term 16:46:50.690 --> 16:46:50.700 align:start position:0% traffic again we have that great term 16:46:50.700 --> 16:46:53.510 align:start position:0% traffic again we have that great term priority<16:46:51.540> shaping<16:46:52.256> so<16:46:52.796> that<16:46:52.916> it's<16:46:53.096> dedicated 16:46:53.510 --> 16:46:53.520 align:start position:0% priority shaping so that it's dedicated 16:46:53.520 --> 16:46:55.190 align:start position:0% priority shaping so that it's dedicated more<16:46:53.756> to<16:46:53.936> the<16:46:54.116> teachers<16:46:54.416> but<16:46:54.776> the<16:46:54.900> students 16:46:55.190 --> 16:46:55.200 align:start position:0% more to the teachers but the students 16:46:55.200 --> 16:46:57.230 align:start position:0% more to the teachers but the students can<16:46:55.380> still<16:46:55.500> use<16:46:55.680> it<16:46:55.796> at<16:46:55.916> a<16:46:56.096> slower<16:46:56.340> speed<16:46:56.580> so 16:46:57.230 --> 16:46:57.240 align:start position:0% can still use it at a slower speed so 16:46:57.240 --> 16:46:58.670 align:start position:0% can still use it at a slower speed so when<16:46:57.416> the<16:46:57.540> teachers<16:46:57.900> don't<16:46:58.256> need<16:46:58.500> the 16:46:58.670 --> 16:46:58.680 align:start position:0% when the teachers don't need the 16:46:58.680 --> 16:47:00.286 align:start position:0% when the teachers don't need the bandwidth<16:46:59.220> the<16:46:59.580> students<16:46:59.820> are<16:46:59.936> able<16:47:00.180> to 16:47:00.286 --> 16:47:00.296 align:start position:0% bandwidth the students are able to 16:47:00.296 --> 16:47:02.266 align:start position:0% bandwidth the students are able to access<16:47:00.416> it<16:47:00.720> at<16:47:00.900> faster<16:47:01.200> speeds<16:47:01.680> so<16:47:02.160> we're 16:47:02.266 --> 16:47:02.276 align:start position:0% access it at faster speeds so we're 16:47:02.276 --> 16:47:05.746 align:start position:0% access it at faster speeds so we're really<16:47:02.520> taking<16:47:02.756> this<16:47:03.540> sort<16:47:03.720> of<16:47:03.840> concept 16:47:05.746 --> 16:47:05.756 align:start position:0% really taking this sort of concept 16:47:05.756 --> 16:47:07.850 align:start position:0% really taking this sort of concept and<16:47:06.480> allowing<16:47:06.840> it<16:47:06.956> to<16:47:07.140> be<16:47:07.256> a<16:47:07.436> little<16:47:07.560> more 16:47:07.850 --> 16:47:07.860 align:start position:0% and allowing it to be a little more 16:47:07.860 --> 16:47:11.510 align:start position:0% and allowing it to be a little more flexible 16:47:11.510 --> 16:47:11.520 align:start position:0% 16:47:11.520 --> 16:47:13.190 align:start position:0% now<16:47:11.936> another<16:47:12.180> technique<16:47:12.540> used<16:47:12.776> is<16:47:13.020> something 16:47:13.190 --> 16:47:13.200 align:start position:0% now another technique used is something 16:47:13.200 --> 16:47:15.050 align:start position:0% now another technique used is something called<16:47:13.500> a<16:47:13.796> caching<16:47:14.220> engine 16:47:15.050 --> 16:47:15.060 align:start position:0% called a caching engine 16:47:15.060 --> 16:47:17.690 align:start position:0% called a caching engine caching<16:47:15.480> is<16:47:15.776> essentially<16:47:16.380> temporary<16:47:17.276> storage 16:47:17.690 --> 16:47:17.700 align:start position:0% caching is essentially temporary storage 16:47:17.700 --> 16:47:20.870 align:start position:0% caching is essentially temporary storage although<16:47:18.596> the<16:47:18.776> storing<16:47:19.140> of<16:47:19.500> what<16:47:19.980> is<16:47:20.400> changing 16:47:20.870 --> 16:47:20.880 align:start position:0% although the storing of what is changing 16:47:20.880 --> 16:47:22.310 align:start position:0% although the storing of what is changing every<16:47:21.240> single<16:47:21.540> time 16:47:22.310 --> 16:47:22.320 align:start position:0% every single time 16:47:22.320 --> 16:47:25.670 align:start position:0% every single time in<16:47:22.980> the<16:47:23.160> case<16:47:23.340> of<16:47:23.756> caching<16:47:24.240> engines<16:47:24.840> the 16:47:25.670 --> 16:47:25.680 align:start position:0% in the case of caching engines the 16:47:25.680 --> 16:47:28.070 align:start position:0% in the case of caching engines the temporarily<16:47:26.456> storage<16:47:26.880> of<16:47:27.240> data<16:47:27.596> is<16:47:27.900> actually 16:47:28.070 --> 16:47:28.080 align:start position:0% temporarily storage of data is actually 16:47:28.080 --> 16:47:30.170 align:start position:0% temporarily storage of data is actually web<16:47:28.436> data<16:47:28.860> that<16:47:28.980> can<16:47:29.096> be<16:47:29.276> used<16:47:29.456> in<16:47:29.936> the<16:47:30.000> future 16:47:30.170 --> 16:47:30.180 align:start position:0% web data that can be used in the future 16:47:30.180 --> 16:47:32.210 align:start position:0% web data that can be used in the future so<16:47:30.900> this<16:47:31.080> is<16:47:31.256> happening<16:47:31.680> through<16:47:31.916> something 16:47:32.210 --> 16:47:32.220 align:start position:0% so this is happening through something 16:47:32.220 --> 16:47:36.670 align:start position:0% so this is happening through something called<16:47:32.580> a<16:47:33.020> proxy<16:47:34.020> server 16:47:36.670 --> 16:47:36.680 align:start position:0% 16:47:36.680 --> 16:47:39.406 align:start position:0% basically<16:47:37.680> what's<16:47:37.916> happening<16:47:38.340> is<16:47:39.000> without 16:47:39.406 --> 16:47:39.416 align:start position:0% basically what's happening is without 16:47:39.416 --> 16:47:41.746 align:start position:0% basically what's happening is without going<16:47:39.720> too<16:47:40.020> far<16:47:40.200> in<16:47:40.320> depth<16:47:40.616> into<16:47:40.680> it<16:47:40.916> is<16:47:41.340> that<16:47:41.580> a 16:47:41.746 --> 16:47:41.756 align:start position:0% going too far in depth into it is that a 16:47:41.756 --> 16:47:43.970 align:start position:0% going too far in depth into it is that a proxy<16:47:42.116> server<16:47:42.480> caches<16:47:43.020> web<16:47:43.256> data<16:47:43.616> for<16:47:43.796> future 16:47:43.970 --> 16:47:43.980 align:start position:0% proxy server caches web data for future 16:47:43.980 --> 16:47:47.570 align:start position:0% proxy server caches web data for future uses<16:47:44.400> by<16:47:44.580> others<16:47:44.936> so<16:47:45.776> if<16:47:46.560> I<16:47:46.796> have<16:47:47.040> let's<16:47:47.400> say 16:47:47.570 --> 16:47:47.580 align:start position:0% uses by others so if I have let's say 16:47:47.580 --> 16:47:49.606 align:start position:0% uses by others so if I have let's say three<16:47:47.880> users 16:47:49.606 --> 16:47:49.616 align:start position:0% three users 16:47:49.616 --> 16:47:52.786 align:start position:0% three users and<16:47:50.340> the<16:47:50.640> first<16:47:50.756> user<16:47:51.240> and<16:47:51.840> I<16:47:51.956> have<16:47:52.080> a<16:47:52.320> proxy 16:47:52.786 --> 16:47:52.796 align:start position:0% and the first user and I have a proxy 16:47:52.796 --> 16:47:55.850 align:start position:0% and the first user and I have a proxy server<16:47:53.400> in<16:47:53.640> between<16:47:53.820> them<16:47:54.180> before<16:47:55.080> it<16:47:55.616> goes 16:47:55.850 --> 16:47:55.860 align:start position:0% server in between them before it goes 16:47:55.860 --> 16:48:00.530 align:start position:0% server in between them before it goes out<16:47:55.980> to<16:47:56.160> the<16:47:56.340> internet 16:48:00.530 --> 16:48:00.540 align:start position:0% 16:48:00.540 --> 16:48:03.766 align:start position:0% and<16:48:01.080> the<16:48:01.256> first<16:48:01.380> user<16:48:02.276> requests 16:48:03.766 --> 16:48:03.776 align:start position:0% and the first user requests 16:48:03.776 --> 16:48:05.210 align:start position:0% and the first user requests CNN 16:48:05.210 --> 16:48:05.220 align:start position:0% CNN 16:48:05.220 --> 16:48:08.690 align:start position:0% CNN the<16:48:05.700> proxy<16:48:06.116> server<16:48:06.480> which<16:48:06.900> holds<16:48:07.256> a<16:48:07.436> cache 16:48:08.690 --> 16:48:08.700 align:start position:0% the proxy server which holds a cache 16:48:08.700 --> 16:48:11.330 align:start position:0% the proxy server which holds a cache or<16:48:09.240> sort<16:48:09.540> of<16:48:09.660> copies<16:48:10.080> of<16:48:10.500> everything 16:48:11.330 --> 16:48:11.340 align:start position:0% or sort of copies of everything 16:48:11.340 --> 16:48:13.246 align:start position:0% or sort of copies of everything we'll<16:48:11.880> first<16:48:12.116> say<16:48:12.360> hey<16:48:12.596> I<16:48:12.840> have<16:48:12.956> the<16:48:13.140> latest 16:48:13.246 --> 16:48:13.256 align:start position:0% we'll first say hey I have the latest 16:48:13.256 --> 16:48:15.710 align:start position:0% we'll first say hey I have the latest CNN<16:48:13.680> or<16:48:13.860> I<16:48:13.980> don't<16:48:14.096> have<16:48:14.220> the<16:48:14.400> latest<16:48:14.520> CNN<16:48:15.000> it'll 16:48:15.710 --> 16:48:15.720 align:start position:0% CNN or I don't have the latest CNN it'll 16:48:15.720 --> 16:48:17.630 align:start position:0% CNN or I don't have the latest CNN it'll then<16:48:15.900> go<16:48:16.080> out<16:48:16.256> to<16:48:16.380> the<16:48:16.560> internet 16:48:17.630 --> 16:48:17.640 align:start position:0% then go out to the internet 16:48:17.640 --> 16:48:21.650 align:start position:0% then go out to the internet get<16:48:18.416> the<16:48:18.956> latest<16:48:19.140> CNN 16:48:21.650 --> 16:48:21.660 align:start position:0% get the latest CNN 16:48:21.660 --> 16:48:24.106 align:start position:0% get the latest CNN and<16:48:22.140> hold<16:48:22.320> that 16:48:24.106 --> 16:48:24.116 align:start position:0% and hold that 16:48:24.116 --> 16:48:26.926 align:start position:0% and hold that in<16:48:24.480> its<16:48:24.776> proxy<16:48:25.140> now<16:48:25.860> when<16:48:26.160> the<16:48:26.340> second<16:48:26.456> user 16:48:26.926 --> 16:48:26.936 align:start position:0% in its proxy now when the second user 16:48:26.936 --> 16:48:29.446 align:start position:0% in its proxy now when the second user five<16:48:27.240> seconds<16:48:27.480> later<16:48:27.776> says<16:48:28.200> Hey<16:48:28.380> I<16:48:29.096> want<16:48:29.220> the 16:48:29.446 --> 16:48:29.456 align:start position:0% five seconds later says Hey I want the 16:48:29.456 --> 16:48:31.550 align:start position:0% five seconds later says Hey I want the latest<16:48:29.640> CNN<16:48:30.180> the<16:48:30.480> proxy<16:48:30.776> server<16:48:31.140> does<16:48:31.380> not 16:48:31.550 --> 16:48:31.560 align:start position:0% latest CNN the proxy server does not 16:48:31.560 --> 16:48:33.286 align:start position:0% latest CNN the proxy server does not have<16:48:31.860> to<16:48:32.040> go<16:48:32.220> out<16:48:32.456> to<16:48:32.640> the<16:48:32.756> internet<16:48:32.880> we<16:48:33.180> can 16:48:33.286 --> 16:48:33.296 align:start position:0% have to go out to the internet we can 16:48:33.296 --> 16:48:36.586 align:start position:0% have to go out to the internet we can basically<16:48:33.596> cut<16:48:33.900> out<16:48:34.140> this<16:48:34.916> entire<16:48:35.276> process 16:48:36.586 --> 16:48:36.596 align:start position:0% basically cut out this entire process 16:48:36.596 --> 16:48:39.406 align:start position:0% basically cut out this entire process and<16:48:37.140> instead<16:48:37.436> it<16:48:37.680> just<16:48:37.860> Returns<16:48:38.400> what<16:48:39.060> it<16:48:39.240> is 16:48:39.406 --> 16:48:39.416 align:start position:0% and instead it just Returns what it is 16:48:39.416 --> 16:48:41.630 align:start position:0% and instead it just Returns what it is already<16:48:39.660> cached<16:48:40.616> it<16:48:40.980> can<16:48:41.096> do<16:48:41.220> this<16:48:41.340> with<16:48:41.520> as 16:48:41.630 --> 16:48:41.640 align:start position:0% already cached it can do this with as 16:48:41.640 --> 16:48:43.490 align:start position:0% already cached it can do this with as many<16:48:41.820> uses<16:48:42.180> as<16:48:42.360> possible<16:48:42.660> and<16:48:43.200> what<16:48:43.380> we'll 16:48:43.490 --> 16:48:43.500 align:start position:0% many uses as possible and what we'll 16:48:43.500 --> 16:48:46.190 align:start position:0% many uses as possible and what we'll generally<16:48:43.796> say<16:48:44.096> is<16:48:44.456> that<16:48:44.756> every<16:48:45.360> minute<16:48:45.840> or 16:48:46.190 --> 16:48:46.200 align:start position:0% generally say is that every minute or 16:48:46.200 --> 16:48:48.230 align:start position:0% generally say is that every minute or every<16:48:46.320> few<16:48:46.560> seconds<16:48:46.860> it's<16:48:47.456> going<16:48:47.700> to<16:48:47.820> update 16:48:48.230 --> 16:48:48.240 align:start position:0% every few seconds it's going to update 16:48:48.240 --> 16:48:49.906 align:start position:0% every few seconds it's going to update the<16:48:48.416> proxy<16:48:48.776> server<16:48:49.020> is<16:48:49.140> going<16:48:49.256> to<16:48:49.320> update<16:48:49.616> its 16:48:49.906 --> 16:48:49.916 align:start position:0% the proxy server is going to update its 16:48:49.916 --> 16:48:51.350 align:start position:0% the proxy server is going to update its information<16:48:50.040> that<16:48:50.640> way<16:48:50.820> we<16:48:50.936> can<16:48:51.060> make<16:48:51.240> sure 16:48:51.350 --> 16:48:51.360 align:start position:0% information that way we can make sure 16:48:51.360 --> 16:48:52.730 align:start position:0% information that way we can make sure that<16:48:51.540> it's<16:48:51.660> still<16:48:51.840> the<16:48:52.020> most<16:48:52.140> up-to-date 16:48:52.730 --> 16:48:52.740 align:start position:0% that it's still the most up-to-date 16:48:52.740 --> 16:48:54.530 align:start position:0% that it's still the most up-to-date information<16:48:53.040> which<16:48:53.880> is<16:48:54.060> one<16:48:54.360> of<16:48:54.416> the 16:48:54.530 --> 16:48:54.540 align:start position:0% information which is one of the 16:48:54.540 --> 16:48:56.390 align:start position:0% information which is one of the downsides<16:48:54.956> of<16:48:55.140> using<16:48:55.380> proxy<16:48:55.860> servers<16:48:56.220> and 16:48:56.390 --> 16:48:56.400 align:start position:0% downsides of using proxy servers and 16:48:56.400 --> 16:48:59.086 align:start position:0% downsides of using proxy servers and caching<16:48:56.820> is<16:48:57.360> that<16:48:57.540> sometimes 16:48:59.086 --> 16:48:59.096 align:start position:0% caching is that sometimes 16:48:59.096 --> 16:49:00.350 align:start position:0% caching is that sometimes um<16:48:59.160> it's<16:48:59.700> not<16:48:59.880> going<16:49:00.000> to<16:49:00.060> have<16:49:00.116> the<16:49:00.296> most 16:49:00.350 --> 16:49:00.360 align:start position:0% um it's not going to have the most 16:49:00.360 --> 16:49:02.150 align:start position:0% um it's not going to have the most up-to-date<16:49:00.840> information<16:49:01.080> but<16:49:01.796> it<16:49:01.916> certainly 16:49:02.150 --> 16:49:02.160 align:start position:0% up-to-date information but it certainly 16:49:02.160 --> 16:49:04.130 align:start position:0% up-to-date information but it certainly speeds<16:49:02.580> things<16:49:02.700> up<16:49:02.936> by<16:49:03.240> cutting<16:49:03.596> out<16:49:03.720> this 16:49:04.130 --> 16:49:04.140 align:start position:0% speeds things up by cutting out this 16:49:04.140 --> 16:49:05.446 align:start position:0% speeds things up by cutting out this whole<16:49:04.256> process<16:49:04.560> of<16:49:04.740> having<16:49:04.860> to<16:49:04.980> go<16:49:05.096> out<16:49:05.220> to<16:49:05.340> the 16:49:05.446 --> 16:49:05.456 align:start position:0% whole process of having to go out to the 16:49:05.456 --> 16:49:07.730 align:start position:0% whole process of having to go out to the Internet<16:49:05.520> by<16:49:06.000> keeping<16:49:06.296> it<16:49:06.416> locally 16:49:07.730 --> 16:49:07.740 align:start position:0% Internet by keeping it locally 16:49:07.740 --> 16:49:10.850 align:start position:0% Internet by keeping it locally now<16:49:08.456> this<16:49:08.700> all<16:49:08.880> saves<16:49:09.360> bandwidth<16:49:10.140> because 16:49:10.850 --> 16:49:10.860 align:start position:0% now this all saves bandwidth because 16:49:10.860 --> 16:49:12.586 align:start position:0% now this all saves bandwidth because obviously<16:49:11.580> I'm<16:49:11.756> not<16:49:11.936> having<16:49:12.116> to<16:49:12.240> go<16:49:12.360> out<16:49:12.480> to 16:49:12.586 --> 16:49:12.596 align:start position:0% obviously I'm not having to go out to 16:49:12.596 --> 16:49:14.746 align:start position:0% obviously I'm not having to go out to the<16:49:12.720> internet<16:49:12.840> and<16:49:13.500> therefore<16:49:13.796> I<16:49:14.096> can<16:49:14.220> reserve 16:49:14.746 --> 16:49:14.756 align:start position:0% the internet and therefore I can reserve 16:49:14.756 --> 16:49:16.606 align:start position:0% the internet and therefore I can reserve that<16:49:15.180> bandwidth<16:49:15.956> speed<16:49:16.140> that<16:49:16.380> would<16:49:16.500> have 16:49:16.606 --> 16:49:16.616 align:start position:0% that bandwidth speed that would have 16:49:16.616 --> 16:49:18.830 align:start position:0% that bandwidth speed that would have been<16:49:16.796> used<16:49:17.160> for<16:49:17.820> video<16:49:18.116> or<16:49:18.416> something<16:49:18.660> else 16:49:18.830 --> 16:49:18.840 align:start position:0% been used for video or something else 16:49:18.840 --> 16:49:21.170 align:start position:0% been used for video or something else that's<16:49:19.200> new<16:49:19.436> uh<16:49:20.340> instead<16:49:20.700> of<16:49:20.756> having<16:49:20.880> to<16:49:21.060> use 16:49:21.170 --> 16:49:21.180 align:start position:0% that's new uh instead of having to use 16:49:21.180 --> 16:49:22.730 align:start position:0% that's new uh instead of having to use it<16:49:21.296> for<16:49:21.480> information<16:49:21.660> that<16:49:22.140> I'm<16:49:22.256> gathering 16:49:22.730 --> 16:49:22.740 align:start position:0% it for information that I'm gathering 16:49:22.740 --> 16:49:25.010 align:start position:0% it for information that I'm gathering over<16:49:23.160> and<16:49:23.340> over<16:49:23.520> and<16:49:23.756> over<16:49:23.936> again<16:49:24.240> you<16:49:24.840> can 16:49:25.010 --> 16:49:25.020 align:start position:0% over and over and over again you can 16:49:25.020 --> 16:49:27.106 align:start position:0% over and over and over again you can imagine<16:49:25.140> in<16:49:25.500> a<16:49:25.680> corporation<16:49:26.040> of<16:49:26.400> thousands<16:49:26.936> or 16:49:27.106 --> 16:49:27.116 align:start position:0% imagine in a corporation of thousands or 16:49:27.116 --> 16:49:28.730 align:start position:0% imagine in a corporation of thousands or hundreds<16:49:27.480> of<16:49:27.596> thousands<16:49:27.900> of<16:49:28.020> people<16:49:28.140> this<16:49:28.560> is 16:49:28.730 --> 16:49:28.740 align:start position:0% hundreds of thousands of people this is 16:49:28.740 --> 16:49:32.446 align:start position:0% hundreds of thousands of people this is really<16:49:29.040> going<16:49:29.340> to<16:49:29.520> save<16:49:29.700> us<16:49:29.880> a<16:49:30.000> lot<16:49:30.116> of<16:49:30.240> time 16:49:32.446 --> 16:49:32.456 align:start position:0% 16:49:32.456 --> 16:49:34.670 align:start position:0% all<16:49:32.756> right<16:49:32.936> so<16:49:33.116> just<16:49:33.296> to<16:49:33.480> recap<16:49:33.840> we<16:49:34.436> talked 16:49:34.670 --> 16:49:34.680 align:start position:0% all right so just to recap we talked 16:49:34.680 --> 16:49:36.586 align:start position:0% all right so just to recap we talked about<16:49:34.740> Network<16:49:35.276> optimization<16:49:36.116> there<16:49:36.416> were<16:49:36.540> a 16:49:36.586 --> 16:49:36.596 align:start position:0% about Network optimization there were a 16:49:36.596 --> 16:49:38.510 align:start position:0% about Network optimization there were a couple<16:49:36.720> terms<16:49:37.020> we<16:49:37.140> mentioned<16:49:37.560> first<16:49:38.220> was 16:49:38.510 --> 16:49:38.520 align:start position:0% couple terms we mentioned first was 16:49:38.520 --> 16:49:41.030 align:start position:0% couple terms we mentioned first was bandwidth<16:49:39.360> bandwidth<16:49:40.140> is<16:49:40.380> the<16:49:40.680> highest 16:49:41.030 --> 16:49:41.040 align:start position:0% bandwidth bandwidth is the highest 16:49:41.040 --> 16:49:43.370 align:start position:0% bandwidth bandwidth is the highest possible<16:49:41.520> speed<16:49:42.000> that<16:49:42.480> we<16:49:42.660> have<16:49:42.776> on<16:49:42.900> our<16:49:43.080> data 16:49:43.370 --> 16:49:43.380 align:start position:0% possible speed that we have on our data 16:49:43.380 --> 16:49:44.990 align:start position:0% possible speed that we have on our data connection<16:49:43.500> we<16:49:44.456> also<16:49:44.700> talked<16:49:44.936> about 16:49:44.990 --> 16:49:45.000 align:start position:0% connection we also talked about 16:49:45.000 --> 16:49:47.390 align:start position:0% connection we also talked about something<16:49:45.296> called<16:49:45.660> throughput<16:49:46.400> whereas 16:49:47.390 --> 16:49:47.400 align:start position:0% something called throughput whereas 16:49:47.400 --> 16:49:48.890 align:start position:0% something called throughput whereas bandwidth 16:49:48.890 --> 16:49:48.900 align:start position:0% bandwidth 16:49:48.900 --> 16:49:52.310 align:start position:0% bandwidth is<16:49:49.560> the<16:49:49.860> ideal<16:49:50.276> or<16:49:51.000> potential 16:49:52.310 --> 16:49:52.320 align:start position:0% is the ideal or potential 16:49:52.320 --> 16:49:54.530 align:start position:0% is the ideal or potential speed 16:49:54.530 --> 16:49:54.540 align:start position:0% speed 16:49:54.540 --> 16:49:56.210 align:start position:0% speed throughput 16:49:56.210 --> 16:49:56.220 align:start position:0% throughput 16:49:56.220 --> 16:49:58.606 align:start position:0% throughput is<16:49:56.756> the<16:49:57.060> actual<16:49:57.360> speed<16:49:57.596> how<16:49:57.956> much<16:49:58.080> is<16:49:58.320> actually 16:49:58.606 --> 16:49:58.616 align:start position:0% is the actual speed how much is actually 16:49:58.616 --> 16:50:01.426 align:start position:0% is the actual speed how much is actually traveling<16:49:59.276> and<16:49:59.880> what<16:50:00.000> we<16:50:00.116> want<16:50:00.296> to<16:50:00.416> do<16:50:00.596> is<16:50:01.200> get 16:50:01.426 --> 16:50:01.436 align:start position:0% traveling and what we want to do is get 16:50:01.436 --> 16:50:03.406 align:start position:0% traveling and what we want to do is get these<16:50:01.680> two<16:50:01.796> to<16:50:02.040> equal<16:50:02.276> one<16:50:02.820> another<16:50:03.000> as<16:50:03.296> much 16:50:03.406 --> 16:50:03.416 align:start position:0% these two to equal one another as much 16:50:03.416 --> 16:50:06.106 align:start position:0% these two to equal one another as much as<16:50:03.540> possible<16:50:03.900> however<16:50:04.740> we<16:50:05.096> also<16:50:05.400> want<16:50:05.700> to<16:50:05.880> make 16:50:06.106 --> 16:50:06.116 align:start position:0% as possible however we also want to make 16:50:06.116 --> 16:50:08.390 align:start position:0% as possible however we also want to make sure<16:50:06.296> to<16:50:06.416> make<16:50:06.596> good<16:50:06.840> use<16:50:07.140> of<16:50:07.560> our<16:50:07.740> bandwidth 16:50:08.390 --> 16:50:08.400 align:start position:0% sure to make good use of our bandwidth 16:50:08.400 --> 16:50:10.070 align:start position:0% sure to make good use of our bandwidth so<16:50:08.820> that<16:50:08.936> everyone<16:50:09.116> can<16:50:09.480> get<16:50:09.720> information 16:50:10.070 --> 16:50:10.080 align:start position:0% so that everyone can get information 16:50:10.080 --> 16:50:12.350 align:start position:0% so that everyone can get information they<16:50:10.616> need<16:50:10.796> when<16:50:10.980> they<16:50:11.160> need<16:50:11.276> it<16:50:11.880> so<16:50:12.060> then<16:50:12.240> we 16:50:12.350 --> 16:50:12.360 align:start position:0% they need when they need it so then we 16:50:12.360 --> 16:50:14.150 align:start position:0% they need when they need it so then we talked<16:50:12.596> about<16:50:12.660> something<16:50:12.900> called<16:50:13.200> quality<16:50:13.860> of 16:50:14.150 --> 16:50:14.160 align:start position:0% talked about something called quality of 16:50:14.160 --> 16:50:16.490 align:start position:0% talked about something called quality of service<16:50:14.456> quality<16:50:15.240> of<16:50:15.416> service<16:50:15.660> make<16:50:16.256> sure 16:50:16.490 --> 16:50:16.500 align:start position:0% service quality of service make sure 16:50:16.500 --> 16:50:19.070 align:start position:0% service quality of service make sure that<16:50:16.740> we're<16:50:16.916> using<16:50:17.340> our<16:50:17.880> bandwidth<16:50:18.480> in<16:50:18.840> a<16:50:18.956> way 16:50:19.070 --> 16:50:19.080 align:start position:0% that we're using our bandwidth in a way 16:50:19.080 --> 16:50:21.586 align:start position:0% that we're using our bandwidth in a way that's<16:50:19.256> going<16:50:19.560> to<16:50:19.740> promote<16:50:20.096> good<16:50:20.520> quality<16:50:20.936> we 16:50:21.586 --> 16:50:21.596 align:start position:0% that's going to promote good quality we 16:50:21.596 --> 16:50:22.970 align:start position:0% that's going to promote good quality we talked<16:50:21.840> about<16:50:21.900> two<16:50:22.256> different<16:50:22.500> types<16:50:22.916> of 16:50:22.970 --> 16:50:22.980 align:start position:0% talked about two different types of 16:50:22.980 --> 16:50:25.550 align:start position:0% talked about two different types of applications<16:50:23.456> in<16:50:23.880> ways<16:50:24.180> that<16:50:24.360> we<16:50:24.660> use<16:50:25.140> quality 16:50:25.550 --> 16:50:25.560 align:start position:0% applications in ways that we use quality 16:50:25.560 --> 16:50:27.286 align:start position:0% applications in ways that we use quality of<16:50:25.680> service<16:50:25.860> first<16:50:26.400> we<16:50:26.580> look<16:50:26.756> at<16:50:26.880> latency 16:50:27.286 --> 16:50:27.296 align:start position:0% of service first we look at latency 16:50:27.296 --> 16:50:28.970 align:start position:0% of service first we look at latency sensitive<16:50:28.020> applications<16:50:28.436> these<16:50:28.796> are<16:50:28.860> the 16:50:28.970 --> 16:50:28.980 align:start position:0% sensitive applications these are the 16:50:28.980 --> 16:50:31.310 align:start position:0% sensitive applications these are the applications<16:50:29.456> that<16:50:30.360> where<16:50:30.540> there<16:50:30.720> is<16:50:30.900> latency 16:50:31.310 --> 16:50:31.320 align:start position:0% applications that where there is latency 16:50:31.320 --> 16:50:32.746 align:start position:0% applications that where there is latency or 16:50:32.746 --> 16:50:32.756 align:start position:0% or 16:50:32.756 --> 16:50:35.990 align:start position:0% or another<16:50:33.240> word<16:50:33.540> for<16:50:33.720> this<16:50:33.900> might<16:50:34.080> be<16:50:34.256> traffic 16:50:35.990 --> 16:50:36.000 align:start position:0% another word for this might be traffic 16:50:36.000 --> 16:50:37.606 align:start position:0% another word for this might be traffic it's<16:50:36.360> going<16:50:36.540> to<16:50:36.660> reduce<16:50:36.840> the<16:50:37.140> speed<16:50:37.320> on<16:50:37.500> the 16:50:37.606 --> 16:50:37.616 align:start position:0% it's going to reduce the speed on the 16:50:37.616 --> 16:50:40.426 align:start position:0% it's going to reduce the speed on the network<16:50:37.756> the<16:50:38.756> quality<16:50:39.180> of<16:50:39.540> the<16:50:39.840> service<16:50:40.080> is 16:50:40.426 --> 16:50:40.436 align:start position:0% network the quality of the service is 16:50:40.436 --> 16:50:42.350 align:start position:0% network the quality of the service is going<16:50:40.680> to<16:50:40.860> start<16:50:40.980> degrading<16:50:41.580> so<16:50:41.936> voice<16:50:42.180> over 16:50:42.350 --> 16:50:42.360 align:start position:0% going to start degrading so voice over 16:50:42.360 --> 16:50:44.330 align:start position:0% going to start degrading so voice over IP<16:50:42.720> is<16:50:42.900> a<16:50:43.020> great<16:50:43.140> example<16:50:43.436> of<16:50:43.616> this<16:50:43.796> if<16:50:44.220> there's 16:50:44.330 --> 16:50:44.340 align:start position:0% IP is a great example of this if there's 16:50:44.340 --> 16:50:45.890 align:start position:0% IP is a great example of this if there's a<16:50:44.520> lot<16:50:44.640> of<16:50:44.820> things<16:50:45.060> going<16:50:45.296> on<16:50:45.480> in<16:50:45.596> the<16:50:45.720> network 16:50:45.890 --> 16:50:45.900 align:start position:0% a lot of things going on in the network 16:50:45.900 --> 16:50:48.766 align:start position:0% a lot of things going on in the network then<16:50:46.740> our<16:50:47.220> voice<16:50:47.456> over<16:50:47.640> IP<16:50:48.116> isn't<16:50:48.540> going<16:50:48.660> to 16:50:48.766 --> 16:50:48.776 align:start position:0% then our voice over IP isn't going to 16:50:48.776 --> 16:50:50.630 align:start position:0% then our voice over IP isn't going to work<16:50:48.900> as<16:50:49.140> effectively<16:50:49.680> and<16:50:50.096> then<16:50:50.220> I<16:50:50.520> can't 16:50:50.630 --> 16:50:50.640 align:start position:0% work as effectively and then I can't 16:50:50.640 --> 16:50:52.370 align:start position:0% work as effectively and then I can't count<16:50:50.880> on<16:50:51.180> voice<16:50:51.296> over<16:50:51.540> IP<16:50:51.900> as<16:50:52.140> a<16:50:52.320> good 16:50:52.370 --> 16:50:52.380 align:start position:0% count on voice over IP as a good 16:50:52.380 --> 16:50:54.470 align:start position:0% count on voice over IP as a good technology<16:50:52.740> so<16:50:53.340> it's<16:50:53.456> important<16:50:53.820> that<16:50:54.060> I<16:50:54.296> make 16:50:54.470 --> 16:50:54.480 align:start position:0% technology so it's important that I make 16:50:54.480 --> 16:50:57.106 align:start position:0% technology so it's important that I make sure<16:50:54.596> Voiceover<16:50:55.200> IP<16:50:55.616> always<16:50:56.160> has<16:50:56.580> a<16:50:56.880> certain 16:50:57.106 --> 16:50:57.116 align:start position:0% sure Voiceover IP always has a certain 16:50:57.116 --> 16:51:00.530 align:start position:0% sure Voiceover IP always has a certain degree<16:50:57.560> of<16:50:58.560> say<16:50:58.796> bandwidth<16:50:59.520> with<16:51:00.116> latency 16:51:00.530 --> 16:51:00.540 align:start position:0% degree of say bandwidth with latency 16:51:00.540 --> 16:51:02.390 align:start position:0% degree of say bandwidth with latency insensitive<16:51:01.320> applications<16:51:01.860> we're<16:51:02.160> looking 16:51:02.390 --> 16:51:02.400 align:start position:0% insensitive applications we're looking 16:51:02.400 --> 16:51:04.786 align:start position:0% insensitive applications we're looking at<16:51:02.580> stuff<16:51:02.820> where<16:51:03.180> the<16:51:03.660> speed<16:51:03.900> although<16:51:04.616> it 16:51:04.786 --> 16:51:04.796 align:start position:0% at stuff where the speed although it 16:51:04.796 --> 16:51:06.350 align:start position:0% at stuff where the speed although it still<16:51:04.916> needs<16:51:05.160> to<16:51:05.220> be<16:51:05.276> fast<16:51:05.456> doesn't<16:51:05.820> matter<16:51:06.060> if 16:51:06.350 --> 16:51:06.360 align:start position:0% still needs to be fast doesn't matter if 16:51:06.360 --> 16:51:07.786 align:start position:0% still needs to be fast doesn't matter if there's<16:51:06.540> latency<16:51:06.900> one<16:51:07.200> second<16:51:07.436> and<16:51:07.616> no 16:51:07.786 --> 16:51:07.796 align:start position:0% there's latency one second and no 16:51:07.796 --> 16:51:09.946 align:start position:0% there's latency one second and no latency<16:51:08.096> the<16:51:08.400> next<16:51:08.520> when<16:51:09.180> we're<16:51:09.360> transferring 16:51:09.946 --> 16:51:09.956 align:start position:0% latency the next when we're transferring 16:51:09.956 --> 16:51:13.730 align:start position:0% latency the next when we're transferring high<16:51:10.520> high<16:51:11.520> or<16:51:12.180> large<16:51:12.480> files<16:51:13.256> such<16:51:13.436> as<16:51:13.560> through 16:51:13.730 --> 16:51:13.740 align:start position:0% high high or large files such as through 16:51:13.740 --> 16:51:16.730 align:start position:0% high high or large files such as through FTP<16:51:14.276> then<16:51:15.240> we<16:51:15.660> don't<16:51:15.776> need<16:51:15.956> to<16:51:16.140> make<16:51:16.320> sure<16:51:16.500> that 16:51:16.730 --> 16:51:16.740 align:start position:0% FTP then we don't need to make sure that 16:51:16.740 --> 16:51:18.586 align:start position:0% FTP then we don't need to make sure that we're<16:51:16.860> not<16:51:17.040> modulating<16:51:17.456> between<16:51:17.756> 90<16:51:18.000> kilobits 16:51:18.586 --> 16:51:18.596 align:start position:0% we're not modulating between 90 kilobits 16:51:18.596 --> 16:51:20.210 align:start position:0% we're not modulating between 90 kilobits per<16:51:18.720> second<16:51:18.840> and<16:51:19.080> 90<16:51:19.200> megabits<16:51:19.740> per<16:51:19.860> second<16:51:19.980> or 16:51:20.210 --> 16:51:20.220 align:start position:0% per second and 90 megabits per second or 16:51:20.220 --> 16:51:21.946 align:start position:0% per second and 90 megabits per second or one<16:51:20.400> gigabit<16:51:20.700> per<16:51:20.880> second<16:51:21.060> as<16:51:21.596> long<16:51:21.720> as<16:51:21.776> the 16:51:21.946 --> 16:51:21.956 align:start position:0% one gigabit per second as long as the 16:51:21.956 --> 16:51:23.990 align:start position:0% one gigabit per second as long as the data<16:51:22.256> gets<16:51:22.560> to<16:51:22.616> where<16:51:22.796> it<16:51:22.916> needs<16:51:23.160> to<16:51:23.220> go 16:51:23.990 --> 16:51:24.000 align:start position:0% data gets to where it needs to go 16:51:24.000 --> 16:51:25.850 align:start position:0% data gets to where it needs to go I<16:51:24.416> don't<16:51:24.540> need<16:51:24.660> to<16:51:24.776> make<16:51:24.956> sure<16:51:25.256> that<16:51:25.740> it's 16:51:25.850 --> 16:51:25.860 align:start position:0% I don't need to make sure that it's 16:51:25.860 --> 16:51:27.586 align:start position:0% I don't need to make sure that it's getting<16:51:26.096> there<16:51:26.276> at<16:51:26.520> the<16:51:26.640> exact<16:51:26.936> time<16:51:27.180> because 16:51:27.586 --> 16:51:27.596 align:start position:0% getting there at the exact time because 16:51:27.596 --> 16:51:29.926 align:start position:0% getting there at the exact time because for<16:51:27.956> instance<16:51:28.140> with<16:51:28.320> voice<16:51:28.500> over<16:51:28.680> IP<16:51:29.040> if<16:51:29.700> I'm 16:51:29.926 --> 16:51:29.936 align:start position:0% for instance with voice over IP if I'm 16:51:29.936 --> 16:51:31.730 align:start position:0% for instance with voice over IP if I'm talking<16:51:30.240> it<16:51:30.660> needs<16:51:30.900> to<16:51:30.956> be<16:51:31.020> able<16:51:31.140> to<16:51:31.320> reach<16:51:31.560> the 16:51:31.730 --> 16:51:31.740 align:start position:0% talking it needs to be able to reach the 16:51:31.740 --> 16:51:33.170 align:start position:0% talking it needs to be able to reach the person<16:51:31.980> sort<16:51:32.456> of<16:51:32.580> the<16:51:32.640> degree<16:51:32.756> that<16:51:33.060> I'm 16:51:33.170 --> 16:51:33.180 align:start position:0% person sort of the degree that I'm 16:51:33.180 --> 16:51:35.150 align:start position:0% person sort of the degree that I'm talking<16:51:33.360> but<16:51:33.900> with<16:51:34.080> FTP<16:51:34.616> it<16:51:34.860> doesn't<16:51:35.040> really 16:51:35.150 --> 16:51:35.160 align:start position:0% talking but with FTP it doesn't really 16:51:35.160 --> 16:51:37.246 align:start position:0% talking but with FTP it doesn't really matter<16:51:35.400> if<16:51:35.700> it's<16:51:35.880> getting<16:51:36.180> there<16:51:36.540> in<16:51:36.956> the<16:51:37.080> same 16:51:37.246 --> 16:51:37.256 align:start position:0% matter if it's getting there in the same 16:51:37.256 --> 16:51:38.210 align:start position:0% matter if it's getting there in the same instant 16:51:38.210 --> 16:51:38.220 align:start position:0% instant 16:51:38.220 --> 16:51:40.370 align:start position:0% instant we<16:51:38.580> also<16:51:38.756> talked<16:51:39.000> about<16:51:39.060> traffic<16:51:39.540> shaping 16:51:40.370 --> 16:51:40.380 align:start position:0% we also talked about traffic shaping 16:51:40.380 --> 16:51:42.230 align:start position:0% we also talked about traffic shaping which<16:51:40.916> is<16:51:41.040> one<16:51:41.276> of<16:51:41.400> the<16:51:41.456> ways<16:51:41.756> that<16:51:41.880> we<16:51:42.060> use 16:51:42.230 --> 16:51:42.240 align:start position:0% which is one of the ways that we use 16:51:42.240 --> 16:51:44.570 align:start position:0% which is one of the ways that we use quality<16:51:42.596> of<16:51:42.720> service<16:51:42.900> and<16:51:43.200> we<16:51:43.320> shape 16:51:44.570 --> 16:51:44.580 align:start position:0% quality of service and we shape 16:51:44.580 --> 16:51:48.230 align:start position:0% quality of service and we shape the<16:51:45.360> bandwidth<16:51:46.020> so<16:51:46.200> that<16:51:46.500> it<16:51:47.096> is<16:51:47.456> used<16:51:47.756> in<16:51:48.116> an 16:51:48.230 --> 16:51:48.240 align:start position:0% the bandwidth so that it is used in an 16:51:48.240 --> 16:51:50.330 align:start position:0% the bandwidth so that it is used in an appropriate<16:51:48.596> way<16:51:48.840> we<16:51:49.500> talked<16:51:49.740> about<16:51:49.860> three 16:51:50.330 --> 16:51:50.340 align:start position:0% appropriate way we talked about three 16:51:50.340 --> 16:51:52.490 align:start position:0% appropriate way we talked about three different<16:51:50.580> ways<16:51:51.000> of<16:51:51.296> doing<16:51:51.480> this 16:51:52.490 --> 16:51:52.500 align:start position:0% different ways of doing this 16:51:52.500 --> 16:51:55.010 align:start position:0% different ways of doing this the<16:51:53.040> first<16:51:53.220> we<16:51:53.456> talked<16:51:53.820> about<16:51:53.880> was<16:51:54.480> based<16:51:54.900> on 16:51:55.010 --> 16:51:55.020 align:start position:0% the first we talked about was based on 16:51:55.020 --> 16:51:57.650 align:start position:0% the first we talked about was based on application<16:51:55.616> so<16:51:56.580> for<16:51:56.820> instance<16:51:57.000> I'm<16:51:57.296> going<16:51:57.480> to 16:51:57.650 --> 16:51:57.660 align:start position:0% application so for instance I'm going to 16:51:57.660 --> 16:52:00.106 align:start position:0% application so for instance I'm going to give<16:51:57.840> a<16:51:58.256> certain<16:51:58.380> degree<16:51:58.740> of<16:51:58.916> bandwidth<16:51:59.520> to 16:52:00.106 --> 16:52:00.116 align:start position:0% give a certain degree of bandwidth to 16:52:00.116 --> 16:52:02.230 align:start position:0% give a certain degree of bandwidth to one<16:52:00.416> application<16:52:00.900> and<16:52:01.380> a<16:52:01.560> certain<16:52:01.680> to<16:52:01.916> another 16:52:02.230 --> 16:52:02.240 align:start position:0% one application and a certain to another 16:52:02.240 --> 16:52:05.510 align:start position:0% one application and a certain to another once<16:52:03.240> all<16:52:03.416> the<16:52:03.596> voice<16:52:03.720> over<16:52:03.956> IP<16:52:04.400> bandwidth<16:52:05.400> is 16:52:05.510 --> 16:52:05.520 align:start position:0% once all the voice over IP bandwidth is 16:52:05.520 --> 16:52:08.086 align:start position:0% once all the voice over IP bandwidth is used<16:52:05.756> that's<16:52:06.180> it<16:52:06.360> once<16:52:07.256> all<16:52:07.436> the<16:52:07.560> FTP 16:52:08.086 --> 16:52:08.096 align:start position:0% used that's it once all the FTP 16:52:08.096 --> 16:52:10.310 align:start position:0% used that's it once all the FTP bandwidth<16:52:08.936> is<16:52:09.000> used<16:52:09.180> I<16:52:09.720> don't<16:52:09.776> have<16:52:09.900> any<16:52:10.080> more 16:52:10.310 --> 16:52:10.320 align:start position:0% bandwidth is used I don't have any more 16:52:10.320 --> 16:52:12.830 align:start position:0% bandwidth is used I don't have any more and<16:52:10.796> so<16:52:10.980> I'm<16:52:11.160> only<16:52:11.340> giving<16:52:11.700> if<16:52:12.180> I<16:52:12.296> have<16:52:12.480> a<16:52:12.776> large 16:52:12.830 --> 16:52:12.840 align:start position:0% and so I'm only giving if I have a large 16:52:12.840 --> 16:52:14.690 align:start position:0% and so I'm only giving if I have a large bandwidth<16:52:13.380> let's<16:52:13.500> say<16:52:13.616> this<16:52:13.860> box<16:52:14.096> represents 16:52:14.690 --> 16:52:14.700 align:start position:0% bandwidth let's say this box represents 16:52:14.700 --> 16:52:16.190 align:start position:0% bandwidth let's say this box represents bandwidth 16:52:16.190 --> 16:52:16.200 align:start position:0% bandwidth 16:52:16.200 --> 16:52:18.766 align:start position:0% bandwidth then<16:52:16.680> I'm<16:52:16.860> going<16:52:17.096> to<16:52:17.340> sort<16:52:17.700> of<16:52:17.820> divide<16:52:18.480> this 16:52:18.766 --> 16:52:18.776 align:start position:0% then I'm going to sort of divide this 16:52:18.776 --> 16:52:20.150 align:start position:0% then I'm going to sort of divide this into<16:52:19.080> layers 16:52:20.150 --> 16:52:20.160 align:start position:0% into layers 16:52:20.160 --> 16:52:22.870 align:start position:0% into layers so<16:52:20.580> FTP<16:52:21.116> gets<16:52:21.480> some 16:52:22.870 --> 16:52:22.880 align:start position:0% so FTP gets some 16:52:22.880 --> 16:52:26.510 align:start position:0% so FTP gets some HTTP<16:52:23.880> gets<16:52:24.360> some<16:52:24.596> voice<16:52:25.200> over<16:52:25.380> IP<16:52:25.796> gets<16:52:26.160> some 16:52:26.510 --> 16:52:26.520 align:start position:0% HTTP gets some voice over IP gets some 16:52:26.520 --> 16:52:27.470 align:start position:0% HTTP gets some voice over IP gets some Etc 16:52:27.470 --> 16:52:27.480 align:start position:0% Etc 16:52:27.480 --> 16:52:30.106 align:start position:0% Etc we<16:52:27.900> also<16:52:28.140> talked<16:52:28.320> about<16:52:28.436> user<16:52:28.916> specific 16:52:30.106 --> 16:52:30.116 align:start position:0% we also talked about user specific 16:52:30.116 --> 16:52:32.086 align:start position:0% we also talked about user specific which<16:52:30.596> means<16:52:30.956> that<16:52:31.380> instead<16:52:31.616> of<16:52:31.680> dividing 16:52:32.086 --> 16:52:32.096 align:start position:0% which means that instead of dividing 16:52:32.096 --> 16:52:33.170 align:start position:0% which means that instead of dividing things<16:52:32.276> up 16:52:33.170 --> 16:52:33.180 align:start position:0% things up 16:52:33.180 --> 16:52:36.106 align:start position:0% things up based<16:52:34.140> on<16:52:34.436> the<16:52:35.160> application<16:52:35.580> I'm<16:52:35.880> going<16:52:36.060> to 16:52:36.106 --> 16:52:36.116 align:start position:0% based on the application I'm going to 16:52:36.116 --> 16:52:38.330 align:start position:0% based on the application I'm going to divide<16:52:36.480> it<16:52:36.596> up<16:52:36.720> based<16:52:37.020> on<16:52:37.080> the<16:52:37.256> individual 16:52:38.330 --> 16:52:38.340 align:start position:0% divide it up based on the individual 16:52:38.340 --> 16:52:41.330 align:start position:0% divide it up based on the individual so<16:52:39.000> Maria<16:52:39.360> gets<16:52:39.956> a<16:52:40.020> certain<16:52:40.140> amount 16:52:41.330 --> 16:52:41.340 align:start position:0% so Maria gets a certain amount 16:52:41.340 --> 16:52:44.030 align:start position:0% so Maria gets a certain amount Anthony<16:52:41.820> gets<16:52:42.296> a<16:52:42.360> certain<16:52:42.480> amount 16:52:44.030 --> 16:52:44.040 align:start position:0% Anthony gets a certain amount 16:52:44.040 --> 16:52:46.130 align:start position:0% Anthony gets a certain amount and<16:52:44.400> Amy<16:52:44.756> gets<16:52:45.000> a<16:52:45.060> certain<16:52:45.116> amount 16:52:46.130 --> 16:52:46.140 align:start position:0% and Amy gets a certain amount 16:52:46.140 --> 16:52:49.606 align:start position:0% and Amy gets a certain amount finally<16:52:46.980> we<16:52:47.520> looked<16:52:47.820> at<16:52:48.080> priority<16:52:49.080> shaping 16:52:49.606 --> 16:52:49.616 align:start position:0% finally we looked at priority shaping 16:52:49.616 --> 16:52:52.970 align:start position:0% finally we looked at priority shaping which<16:52:50.160> is<16:52:50.400> a<16:52:50.520> really<16:52:50.700> cool<16:52:50.880> term 16:52:52.970 --> 16:52:52.980 align:start position:0% which is a really cool term 16:52:52.980 --> 16:52:54.890 align:start position:0% which is a really cool term and<16:52:53.400> what<16:52:53.520> this<16:52:53.700> means<16:52:54.000> is<16:52:54.240> I<16:52:54.480> can<16:52:54.660> give 16:52:54.890 --> 16:52:54.900 align:start position:0% and what this means is I can give 16:52:54.900 --> 16:52:57.170 align:start position:0% and what this means is I can give certain<16:52:55.256> priority<16:52:55.796> to<16:52:56.340> certain<16:52:56.520> individuals 16:52:57.170 --> 16:52:57.180 align:start position:0% certain priority to certain individuals 16:52:57.180 --> 16:53:00.286 align:start position:0% certain priority to certain individuals or<16:52:57.596> groups<16:52:57.956> so<16:52:58.616> for<16:52:58.860> instance<16:52:59.040> we<16:52:59.276> use<16:52:59.456> the 16:53:00.286 --> 16:53:00.296 align:start position:0% or groups so for instance we use the 16:53:00.296 --> 16:53:02.746 align:start position:0% or groups so for instance we use the teachers<16:53:00.840> versus<16:53:01.020> students<16:53:01.756> comparison 16:53:02.746 --> 16:53:02.756 align:start position:0% teachers versus students comparison 16:53:02.756 --> 16:53:05.330 align:start position:0% teachers versus students comparison teachers<16:53:03.480> we<16:53:03.660> want<16:53:03.840> to<16:53:03.956> have<16:53:04.140> a<16:53:04.320> lot<16:53:04.436> more<16:53:04.740> than 16:53:05.330 --> 16:53:05.340 align:start position:0% teachers we want to have a lot more than 16:53:05.340 --> 16:53:07.370 align:start position:0% teachers we want to have a lot more than the<16:53:05.580> students<16:53:05.936> so<16:53:06.416> students<16:53:06.840> get<16:53:07.080> a<16:53:07.256> very 16:53:07.370 --> 16:53:07.380 align:start position:0% the students so students get a very 16:53:07.380 --> 16:53:09.230 align:start position:0% the students so students get a very small<16:53:07.616> amount<16:53:08.040> whereas<16:53:08.580> teachers<16:53:08.820> get<16:53:09.000> a<16:53:09.116> very 16:53:09.230 --> 16:53:09.240 align:start position:0% small amount whereas teachers get a very 16:53:09.240 --> 16:53:11.330 align:start position:0% small amount whereas teachers get a very large<16:53:09.360> amount<16:53:09.720> same<16:53:10.436> with<16:53:10.680> on<16:53:10.916> a<16:53:11.096> corporate 16:53:11.330 --> 16:53:11.340 align:start position:0% large amount same with on a corporate 16:53:11.340 --> 16:53:13.490 align:start position:0% large amount same with on a corporate Network<16:53:11.520> perhaps<16:53:12.000> I<16:53:12.180> want<16:53:12.296> a<16:53:12.480> management<16:53:12.660> or 16:53:13.490 --> 16:53:13.500 align:start position:0% Network perhaps I want a management or 16:53:13.500 --> 16:53:15.830 align:start position:0% Network perhaps I want a management or my<16:53:13.680> Graphics<16:53:14.096> team<16:53:14.276> to<16:53:14.700> have<16:53:14.820> a<16:53:15.000> lot<16:53:15.116> more<16:53:15.360> than 16:53:15.830 --> 16:53:15.840 align:start position:0% my Graphics team to have a lot more than 16:53:15.840 --> 16:53:17.630 align:start position:0% my Graphics team to have a lot more than say<16:53:16.080> my<16:53:16.256> accounting<16:53:16.680> team<16:53:16.916> or<16:53:17.276> lower 16:53:17.630 --> 16:53:17.640 align:start position:0% say my accounting team or lower 16:53:17.640 --> 16:53:20.390 align:start position:0% say my accounting team or lower management<16:53:17.936> or<16:53:18.360> the<16:53:18.596> secretaries<16:53:19.560> finally<16:53:20.220> we 16:53:20.390 --> 16:53:20.400 align:start position:0% management or the secretaries finally we 16:53:20.400 --> 16:53:22.426 align:start position:0% management or the secretaries finally we talked<16:53:20.700> about<16:53:20.756> caching<16:53:21.416> engines<16:53:21.840> and<16:53:22.140> we<16:53:22.320> use 16:53:22.426 --> 16:53:22.436 align:start position:0% talked about caching engines and we use 16:53:22.436 --> 16:53:25.070 align:start position:0% talked about caching engines and we use the<16:53:22.616> word<16:53:22.796> proxy<16:53:23.456> server<16:53:24.240> this<16:53:24.660> is<16:53:24.776> going<16:53:24.900> to 16:53:25.070 --> 16:53:25.080 align:start position:0% the word proxy server this is going to 16:53:25.080 --> 16:53:27.530 align:start position:0% the word proxy server this is going to save<16:53:25.256> us<16:53:25.436> time<16:53:25.740> because<16:53:26.456> whenever<16:53:27.116> I<16:53:27.360> go<16:53:27.480> out 16:53:27.530 --> 16:53:27.540 align:start position:0% save us time because whenever I go out 16:53:27.540 --> 16:53:29.570 align:start position:0% save us time because whenever I go out to<16:53:27.720> get<16:53:27.840> information<16:53:28.080> from<16:53:28.500> a<16:53:28.616> website<16:53:28.980> I 16:53:29.570 --> 16:53:29.580 align:start position:0% to get information from a website I 16:53:29.580 --> 16:53:30.766 align:start position:0% to get information from a website I don't<16:53:29.700> have<16:53:29.880> to<16:53:30.060> go<16:53:30.240> get<16:53:30.480> the<16:53:30.660> information 16:53:30.766 --> 16:53:30.776 align:start position:0% don't have to go get the information 16:53:30.776 --> 16:53:33.766 align:start position:0% don't have to go get the information fresh<16:53:31.436> every<16:53:31.916> time<16:53:32.220> instead<16:53:33.060> I'm<16:53:33.360> going<16:53:33.540> to 16:53:33.766 --> 16:53:33.776 align:start position:0% fresh every time instead I'm going to 16:53:33.776 --> 16:53:37.606 align:start position:0% fresh every time instead I'm going to use<16:53:33.900> the<16:53:34.080> proxy<16:53:34.500> server<16:53:34.860> to<16:53:35.700> hold<16:53:35.880> a<16:53:36.180> copy<16:53:36.540> or<16:53:37.200> a 16:53:37.606 --> 16:53:37.616 align:start position:0% use the proxy server to hold a copy or a 16:53:37.616 --> 16:53:41.030 align:start position:0% use the proxy server to hold a copy or a cached<16:53:38.276> version<16:53:38.720> of<16:53:39.720> my<16:53:39.956> website<16:53:40.320> and<16:53:40.916> that 16:53:41.030 --> 16:53:41.040 align:start position:0% cached version of my website and that 16:53:41.040 --> 16:53:42.106 align:start position:0% cached version of my website and that way<16:53:41.160> I<16:53:41.340> don't<16:53:41.400> have<16:53:41.580> to<16:53:41.640> go<16:53:41.756> out<16:53:41.880> to<16:53:42.000> the 16:53:42.106 --> 16:53:42.116 align:start position:0% way I don't have to go out to the 16:53:42.116 --> 16:53:43.670 align:start position:0% way I don't have to go out to the internet<16:53:42.240> every<16:53:42.540> time<16:53:42.776> and<16:53:43.020> I<16:53:43.140> can<16:53:43.256> reserve 16:53:43.670 --> 16:53:43.680 align:start position:0% internet every time and I can reserve 16:53:43.680 --> 16:53:45.406 align:start position:0% internet every time and I can reserve that<16:53:43.860> bandwidth<16:53:44.400> for<16:53:44.640> other<16:53:44.820> things<16:53:45.000> I<16:53:45.296> might 16:53:45.406 --> 16:53:45.416 align:start position:0% that bandwidth for other things I might 16:53:45.416 --> 16:53:49.590 align:start position:0% that bandwidth for other things I might need<16:53:45.540> to<16:53:45.720> use 16:53:49.590 --> 16:53:49.600 align:start position:0% 16:53:49.600 --> 16:53:58.210 align:start position:0% [Music] 16:53:58.210 --> 16:53:58.220 align:start position:0% [Music] 16:53:58.220 --> 16:54:05.570 align:start position:0% [Music] thank<16:53:59.220> you 16:54:05.570 --> 16:54:05.580 align:start position:0% 16:54:05.580 --> 16:54:07.850 align:start position:0% okay<16:54:06.000> welcome<16:54:06.240> to<16:54:06.540> module<16:54:06.900> 11<16:54:07.080> lesson<16:54:07.680> 3 16:54:07.850 --> 16:54:07.860 align:start position:0% okay welcome to module 11 lesson 3 16:54:07.860 --> 16:54:11.870 align:start position:0% okay welcome to module 11 lesson 3 Network<16:54:08.220> documentation<16:54:09.200> a<16:54:10.200> little<16:54:10.380> bit<16:54:11.040> um<16:54:11.040> of 16:54:11.870 --> 16:54:11.880 align:start position:0% Network documentation a little bit um of 16:54:11.880 --> 16:54:14.030 align:start position:0% Network documentation a little bit um of a<16:54:12.116> harder<16:54:12.416> on<16:54:12.596> this<16:54:12.720> it's<16:54:13.020> just<16:54:13.200> a<16:54:13.320> bit 16:54:14.030 --> 16:54:14.040 align:start position:0% a harder on this it's just a bit 16:54:14.040 --> 16:54:16.550 align:start position:0% a harder on this it's just a bit easier<16:54:14.700> Terry<16:54:14.880> can<16:54:15.116> wishy-washy 16:54:16.550 --> 16:54:16.560 align:start position:0% easier Terry can wishy-washy 16:54:16.560 --> 16:54:18.710 align:start position:0% easier Terry can wishy-washy um although<16:54:16.860> it's<16:54:17.040> obviously<16:54:17.520> important 16:54:18.710 --> 16:54:18.720 align:start position:0% um although it's obviously important 16:54:18.720 --> 16:54:21.586 align:start position:0% um although it's obviously important but<16:54:19.140> just<16:54:19.380> to<16:54:19.560> discuss<16:54:19.860> and<16:54:20.456> what<16:54:20.640> is<16:54:21.116> it<16:54:21.240> I'm 16:54:21.586 --> 16:54:21.596 align:start position:0% but just to discuss and what is it I'm 16:54:21.596 --> 16:54:22.850 align:start position:0% but just to discuss and what is it I'm sure<16:54:21.720> you<16:54:21.840> could<16:54:21.956> actually<16:54:22.140> work<16:54:22.380> out<16:54:22.616> well 16:54:22.850 --> 16:54:22.860 align:start position:0% sure you could actually work out well 16:54:22.860 --> 16:54:25.850 align:start position:0% sure you could actually work out well one<16:54:23.520> network<16:54:23.640> documentation<16:54:24.416> is<16:54:24.720> why<16:54:25.500> do<16:54:25.680> we 16:54:25.850 --> 16:54:25.860 align:start position:0% one network documentation is why do we 16:54:25.860 --> 16:54:28.906 align:start position:0% one network documentation is why do we why<16:54:26.160> do<16:54:26.340> we<16:54:26.456> have<16:54:26.640> it<16:54:26.820> importance<16:54:27.540> of<16:54:27.776> it 16:54:28.906 --> 16:54:28.916 align:start position:0% why do we have it importance of it 16:54:28.916 --> 16:54:30.766 align:start position:0% why do we have it importance of it parts<16:54:29.400> of<16:54:29.640> it 16:54:30.766 --> 16:54:30.776 align:start position:0% parts of it 16:54:30.776 --> 16:54:32.810 align:start position:0% parts of it and<16:54:31.436> many<16:54:31.616> General<16:54:31.860> assets<16:54:32.276> and<16:54:32.456> our<16:54:32.640> Network 16:54:32.810 --> 16:54:32.820 align:start position:0% and many General assets and our Network 16:54:32.820 --> 16:54:34.390 align:start position:0% and many General assets and our Network diagrams 16:54:34.390 --> 16:54:34.400 align:start position:0% diagrams 16:54:34.400 --> 16:54:37.390 align:start position:0% diagrams RFID<16:54:35.400> which<16:54:35.820> we<16:54:36.060> go<16:54:36.180> into 16:54:37.390 --> 16:54:37.400 align:start position:0% RFID which we go into 16:54:37.400 --> 16:54:39.766 align:start position:0% RFID which we go into tracking<16:54:38.400> our<16:54:38.520> IP<16:54:38.880> address<16:54:39.000> utilization 16:54:39.766 --> 16:54:39.776 align:start position:0% tracking our IP address utilization 16:54:39.776 --> 16:54:41.390 align:start position:0% tracking our IP address utilization which<16:54:40.200> is<16:54:40.320> quite<16:54:40.500> a<16:54:40.616> handy<16:54:40.860> thing<16:54:41.040> to<16:54:41.276> have 16:54:41.390 --> 16:54:41.400 align:start position:0% which is quite a handy thing to have 16:54:41.400 --> 16:54:43.906 align:start position:0% which is quite a handy thing to have actually<16:54:41.776> information<16:54:42.776> about<16:54:43.200> vendors<16:54:43.740> and 16:54:43.906 --> 16:54:43.916 align:start position:0% actually information about vendors and 16:54:43.916 --> 16:54:46.246 align:start position:0% actually information about vendors and contractors<16:54:44.456> and<16:54:44.820> all<16:54:44.936> of<16:54:45.060> our<16:54:45.240> policies<16:54:46.020> and 16:54:46.246 --> 16:54:46.256 align:start position:0% contractors and all of our policies and 16:54:46.256 --> 16:54:48.406 align:start position:0% contractors and all of our policies and procedures 16:54:48.406 --> 16:54:48.416 align:start position:0% procedures 16:54:48.416 --> 16:54:50.586 align:start position:0% procedures so<16:54:48.840> the<16:54:48.956> whole<16:54:49.140> principle<16:54:49.740> behind<16:54:50.096> Network 16:54:50.586 --> 16:54:50.596 align:start position:0% so the whole principle behind Network 16:54:50.596 --> 16:54:52.970 align:start position:0% so the whole principle behind Network documentation<16:54:51.596> is<16:54:51.840> professionalism<16:54:52.616> really 16:54:52.970 --> 16:54:52.980 align:start position:0% documentation is professionalism really 16:54:52.980 --> 16:54:55.970 align:start position:0% documentation is professionalism really and<16:54:53.276> business<16:54:53.520> continuity<16:54:54.416> and<16:54:55.080> it's<16:54:55.616> um<16:54:55.616> an 16:54:55.970 --> 16:54:55.980 align:start position:0% and business continuity and it's um an 16:54:55.980 --> 16:54:57.830 align:start position:0% and business continuity and it's um an emerging<16:54:56.456> field 16:54:57.830 --> 16:54:57.840 align:start position:0% emerging field 16:54:57.840 --> 16:55:00.650 align:start position:0% emerging field and<16:54:58.740> in<16:54:58.980> the<16:54:59.096> world<16:54:59.220> of<16:54:59.456> I.T<16:54:59.820> non-technical 16:55:00.650 --> 16:55:00.660 align:start position:0% and in the world of I.T non-technical 16:55:00.660 --> 16:55:05.390 align:start position:0% and in the world of I.T non-technical but<16:55:01.320> looking<16:55:01.560> at<16:55:01.860> audit<16:55:02.520> trails<16:55:03.060> and<16:55:04.380> um<16:55:04.860> yeah 16:55:05.390 --> 16:55:05.400 align:start position:0% but looking at audit trails and um yeah 16:55:05.400 --> 16:55:07.310 align:start position:0% but looking at audit trails and um yeah in<16:55:05.640> the<16:55:05.880> context<16:55:06.180> of<16:55:06.360> documentation<16:55:06.956> really 16:55:07.310 --> 16:55:07.320 align:start position:0% in the context of documentation really 16:55:07.320 --> 16:55:10.970 align:start position:0% in the context of documentation really and<16:55:07.560> all<16:55:07.740> of<16:55:07.860> our<16:55:07.980> procedures 16:55:10.970 --> 16:55:10.980 align:start position:0% 16:55:10.980 --> 16:55:13.730 align:start position:0% so<16:55:11.520> critical<16:55:11.936> role<16:55:12.480> and<16:55:13.020> especially<16:55:13.500> when 16:55:13.730 --> 16:55:13.740 align:start position:0% so critical role and especially when 16:55:13.740 --> 16:55:15.350 align:start position:0% so critical role and especially when there's<16:55:13.980> a<16:55:14.160> problem<16:55:14.340> because<16:55:14.756> people<16:55:15.116> start 16:55:15.350 --> 16:55:15.360 align:start position:0% there's a problem because people start 16:55:15.360 --> 16:55:18.586 align:start position:0% there's a problem because people start scrambling<16:55:15.840> looking<16:55:16.200> for<16:55:16.560> what<16:55:17.400> to<16:55:17.580> do<16:55:17.820> in 16:55:18.586 --> 16:55:18.596 align:start position:0% scrambling looking for what to do in 16:55:18.596 --> 16:55:21.050 align:start position:0% scrambling looking for what to do in terms<16:55:18.840> of<16:55:18.900> procedures<16:55:19.436> and<16:55:19.680> policies<16:55:20.160> who 16:55:21.050 --> 16:55:21.060 align:start position:0% terms of procedures and policies who 16:55:21.060 --> 16:55:22.850 align:start position:0% terms of procedures and policies who does<16:55:21.296> what 16:55:22.850 --> 16:55:22.860 align:start position:0% does what 16:55:22.860 --> 16:55:24.530 align:start position:0% does what um<16:55:22.916> where<16:55:23.276> to<16:55:23.400> find<16:55:23.580> them<16:55:23.820> how<16:55:24.240> to<16:55:24.296> contact 16:55:24.530 --> 16:55:24.540 align:start position:0% um where to find them how to contact 16:55:24.540 --> 16:55:26.690 align:start position:0% um where to find them how to contact them<16:55:25.020> and 16:55:26.690 --> 16:55:26.700 align:start position:0% them and 16:55:26.700 --> 16:55:28.550 align:start position:0% them and um where<16:55:27.240> the<16:55:27.416> technology<16:55:27.776> is<16:55:28.080> and<16:55:28.256> how<16:55:28.436> to 16:55:28.550 --> 16:55:28.560 align:start position:0% um where the technology is and how to 16:55:28.560 --> 16:55:30.010 align:start position:0% um where the technology is and how to fix<16:55:28.740> here<16:55:28.980> there's<16:55:29.220> a<16:55:29.340> whole<16:55:29.456> bunch<16:55:29.700> of 16:55:30.010 --> 16:55:30.020 align:start position:0% fix here there's a whole bunch of 16:55:30.020 --> 16:55:32.810 align:start position:0% fix here there's a whole bunch of procedures<16:55:31.020> and<16:55:31.560> documents<16:55:32.220> that<16:55:32.456> have<16:55:32.640> to 16:55:32.810 --> 16:55:32.820 align:start position:0% procedures and documents that have to 16:55:32.820 --> 16:55:34.850 align:start position:0% procedures and documents that have to all<16:55:33.116> be<16:55:33.720> easily<16:55:34.020> accessible<16:55:34.436> and<16:55:34.616> come 16:55:34.850 --> 16:55:34.860 align:start position:0% all be easily accessible and come 16:55:34.860 --> 16:55:37.606 align:start position:0% all be easily accessible and come together<16:55:35.040> and<16:55:35.756> bear<16:55:35.936> in<16:55:36.116> mind<16:55:36.296> that<16:55:37.080> um<16:55:37.080> the 16:55:37.606 --> 16:55:37.616 align:start position:0% together and bear in mind that um the 16:55:37.616 --> 16:55:39.230 align:start position:0% together and bear in mind that um the network<16:55:37.740> could<16:55:38.340> be<16:55:38.520> down<16:55:38.700> there<16:55:38.880> could<16:55:39.000> be<16:55:39.116> an 16:55:39.230 --> 16:55:39.240 align:start position:0% network could be down there could be an 16:55:39.240 --> 16:55:41.390 align:start position:0% network could be down there could be an outage<16:55:39.540> so<16:55:39.900> if<16:55:40.436> it's<16:55:40.560> contained<16:55:41.040> on<16:55:41.096> a<16:55:41.276> service 16:55:41.390 --> 16:55:41.400 align:start position:0% outage so if it's contained on a service 16:55:41.400 --> 16:55:43.850 align:start position:0% outage so if it's contained on a service somewhere<16:55:41.880> then<16:55:42.116> that<16:55:42.956> might<16:55:43.140> not<16:55:43.256> be<16:55:43.860> um 16:55:43.850 --> 16:55:43.860 align:start position:0% somewhere then that might not be um 16:55:43.860 --> 16:55:46.130 align:start position:0% somewhere then that might not be um ideal<16:55:44.700> if<16:55:44.936> it's<16:55:45.116> only<16:55:45.296> kept<16:55:45.596> on<16:55:45.720> the<16:55:45.840> server 16:55:46.130 --> 16:55:46.140 align:start position:0% ideal if it's only kept on the server 16:55:46.140 --> 16:55:47.330 align:start position:0% ideal if it's only kept on the server anyway 16:55:47.330 --> 16:55:47.340 align:start position:0% anyway 16:55:47.340 --> 16:55:49.310 align:start position:0% anyway so<16:55:48.360> um<16:55:48.360> you<16:55:48.596> can't<16:55:48.720> remember<16:55:48.900> everything 16:55:49.310 --> 16:55:49.320 align:start position:0% so um you can't remember everything 16:55:49.320 --> 16:55:51.530 align:start position:0% so um you can't remember everything especially<16:55:49.980> if<16:55:50.160> it's<16:55:50.276> a<16:55:50.456> large<16:55:50.580> Network<16:55:50.936> or 16:55:51.530 --> 16:55:51.540 align:start position:0% especially if it's a large Network or 16:55:51.540 --> 16:55:53.990 align:start position:0% especially if it's a large Network or even<16:55:51.776> worse<16:55:52.020> if<16:55:52.200> it's<16:55:52.380> a<16:55:52.560> small<16:55:52.740> company<16:55:53.000> and 16:55:53.990 --> 16:55:54.000 align:start position:0% even worse if it's a small company and 16:55:54.000 --> 16:55:56.086 align:start position:0% even worse if it's a small company and somebody<16:55:54.180> leaves<16:55:54.660> the<16:55:54.776> business<16:55:54.956> and<16:55:55.916> you 16:55:56.086 --> 16:55:56.096 align:start position:0% somebody leaves the business and you 16:55:56.096 --> 16:55:57.586 align:start position:0% somebody leaves the business and you take<16:55:56.340> over<16:55:56.520> from<16:55:56.820> them<16:55:57.000> if<16:55:57.240> there's<16:55:57.416> no 16:55:57.586 --> 16:55:57.596 align:start position:0% take over from them if there's no 16:55:57.596 --> 16:55:59.570 align:start position:0% take over from them if there's no documentation<16:55:58.200> then<16:55:58.436> it<16:55:58.680> causes<16:55:59.096> a<16:55:59.340> lot<16:55:59.456> of 16:55:59.570 --> 16:55:59.580 align:start position:0% documentation then it causes a lot of 16:55:59.580 --> 16:56:02.746 align:start position:0% documentation then it causes a lot of Heartache 16:56:02.746 --> 16:56:02.756 align:start position:0% 16:56:02.756 --> 16:56:04.906 align:start position:0% um<16:56:02.880> and<16:56:02.880> yeah<16:56:03.596> if<16:56:03.776> you're<16:56:03.956> the<16:56:04.140> one<16:56:04.256> to<16:56:04.680> have 16:56:04.906 --> 16:56:04.916 align:start position:0% um and yeah if you're the one to have 16:56:04.916 --> 16:56:06.650 align:start position:0% um and yeah if you're the one to have joined<16:56:05.276> it's<16:56:05.756> um<16:56:05.756> it's<16:56:06.240> pretty<16:56:06.360> difficult 16:56:06.650 --> 16:56:06.660 align:start position:0% joined it's um it's pretty difficult 16:56:06.660 --> 16:56:07.670 align:start position:0% joined it's um it's pretty difficult because<16:56:06.840> you've<16:56:07.080> got<16:56:07.140> to<16:56:07.256> learn<16:56:07.380> the<16:56:07.500> network 16:56:07.670 --> 16:56:07.680 align:start position:0% because you've got to learn the network 16:56:07.680 --> 16:56:10.130 align:start position:0% because you've got to learn the network from<16:56:08.160> scratch 16:56:10.130 --> 16:56:10.140 align:start position:0% from scratch 16:56:10.140 --> 16:56:11.990 align:start position:0% from scratch and<16:56:10.616> it's<16:56:10.796> not<16:56:10.916> possible<16:56:11.220> to<16:56:11.400> go<16:56:11.520> and<16:56:11.640> search<16:56:11.756> a 16:56:11.990 --> 16:56:12.000 align:start position:0% and it's not possible to go and search a 16:56:12.000 --> 16:56:13.730 align:start position:0% and it's not possible to go and search a network<16:56:12.180> organization<16:56:12.956> administrators 16:56:13.730 --> 16:56:13.740 align:start position:0% network organization administrators 16:56:13.740 --> 16:56:15.350 align:start position:0% network organization administrators who've<16:56:14.096> quit 16:56:15.350 --> 16:56:15.360 align:start position:0% who've quit 16:56:15.360 --> 16:56:16.730 align:start position:0% who've quit don't<16:56:15.840> believe<16:56:16.020> they<16:56:16.200> have<16:56:16.320> their<16:56:16.500> phones 16:56:16.730 --> 16:56:16.740 align:start position:0% don't believe they have their phones 16:56:16.740 --> 16:56:18.106 align:start position:0% don't believe they have their phones taken<16:56:17.040> off<16:56:17.160> them<16:56:17.340> or<16:56:17.456> they're<16:56:17.640> just<16:56:17.756> going<16:56:17.880> a 16:56:18.106 --> 16:56:18.116 align:start position:0% taken off them or they're just going a 16:56:18.116 --> 16:56:19.606 align:start position:0% taken off them or they're just going a long<16:56:18.240> vacation<16:56:18.596> so<16:56:18.956> you<16:56:19.020> don't<16:56:19.200> got<16:56:19.320> to<16:56:19.500> find 16:56:19.606 --> 16:56:19.616 align:start position:0% long vacation so you don't got to find 16:56:19.616 --> 16:56:20.990 align:start position:0% long vacation so you don't got to find them 16:56:20.990 --> 16:56:21.000 align:start position:0% them 16:56:21.000 --> 16:56:23.446 align:start position:0% them so<16:56:21.840> it<16:56:22.140> gives<16:56:22.436> Network<16:56:22.740> administrators 16:56:23.446 --> 16:56:23.456 align:start position:0% so it gives Network administrators 16:56:23.456 --> 16:56:26.630 align:start position:0% so it gives Network administrators information<16:56:23.880> about<16:56:24.660> the<16:56:25.140> network<16:56:25.640> appearance 16:56:26.630 --> 16:56:26.640 align:start position:0% information about the network appearance 16:56:26.640 --> 16:56:28.446 align:start position:0% information about the network appearance logical<16:56:27.116> versus<16:56:27.416> physical 16:56:28.446 --> 16:56:28.456 align:start position:0% logical versus physical 16:56:28.456 --> 16:56:30.710 align:start position:0% logical versus physical baselines<16:56:29.456> how<16:56:29.700> it's<16:56:29.880> performing<16:56:30.296> I<16:56:30.540> should 16:56:30.710 --> 16:56:30.720 align:start position:0% baselines how it's performing I should 16:56:30.720 --> 16:56:32.810 align:start position:0% baselines how it's performing I should perform<16:56:30.840> to<16:56:31.256> see<16:56:31.380> if<16:56:31.500> there's<16:56:31.616> anything 16:56:32.810 --> 16:56:32.820 align:start position:0% perform to see if there's anything 16:56:32.820 --> 16:56:34.730 align:start position:0% perform to see if there's anything um out<16:56:33.060> of<16:56:33.180> the<16:56:33.296> ordinary 16:56:34.730 --> 16:56:34.740 align:start position:0% um out of the ordinary 16:56:34.740 --> 16:56:36.946 align:start position:0% um out of the ordinary um<16:56:34.796> where<16:56:34.980> to<16:56:35.096> begin<16:56:35.220> troubleshooting 16:56:36.946 --> 16:56:36.956 align:start position:0% um where to begin troubleshooting 16:56:36.956 --> 16:56:38.746 align:start position:0% um where to begin troubleshooting so<16:56:37.380> the<16:56:37.500> main<16:56:37.680> purpose<16:56:38.040> is<16:56:38.276> to<16:56:38.456> keep<16:56:38.520> the 16:56:38.746 --> 16:56:38.756 align:start position:0% so the main purpose is to keep the 16:56:38.756 --> 16:56:40.246 align:start position:0% so the main purpose is to keep the network<16:56:38.880> running<16:56:39.240> smoothly<16:56:39.776> so<16:56:39.956> we've<16:56:40.140> got 16:56:40.246 --> 16:56:40.256 align:start position:0% network running smoothly so we've got 16:56:40.256 --> 16:56:41.830 align:start position:0% network running smoothly so we've got that<16:56:40.436> five<16:56:40.680> nines 16:56:41.830 --> 16:56:41.840 align:start position:0% that five nines 16:56:41.840 --> 16:56:45.530 align:start position:0% that five nines 99.99<16:56:43.040> uptime<16:56:44.040> ideally 16:56:45.530 --> 16:56:45.540 align:start position:0% 99.99 uptime ideally 16:56:45.540 --> 16:56:47.030 align:start position:0% 99.99 uptime ideally it's<16:56:46.080> important<16:56:46.436> to<16:56:46.616> maintain<16:56:46.860> the 16:56:47.030 --> 16:56:47.040 align:start position:0% it's important to maintain the 16:56:47.040 --> 16:56:49.370 align:start position:0% it's important to maintain the documentation<16:56:47.640> and<16:56:48.360> keep<16:56:48.900> it<16:56:49.080> while 16:56:49.370 --> 16:56:49.380 align:start position:0% documentation and keep it while 16:56:49.380 --> 16:56:51.050 align:start position:0% documentation and keep it while maintaining<16:56:49.860> means<16:56:50.220> keep<16:56:50.456> it<16:56:50.580> up<16:56:50.756> to<16:56:50.880> date 16:56:51.050 --> 16:56:51.060 align:start position:0% maintaining means keep it up to date 16:56:51.060 --> 16:56:53.266 align:start position:0% maintaining means keep it up to date because<16:56:51.360> out<16:56:52.320> of<16:56:52.500> date<16:56:52.680> documentation 16:56:53.266 --> 16:56:53.276 align:start position:0% because out of date documentation 16:56:53.276 --> 16:56:55.070 align:start position:0% because out of date documentation actually<16:56:53.580> causes<16:56:54.116> more<16:56:54.360> problems<16:56:54.720> than<16:56:54.956> it 16:56:55.070 --> 16:56:55.080 align:start position:0% actually causes more problems than it 16:56:55.080 --> 16:56:56.746 align:start position:0% actually causes more problems than it fixes<16:56:55.560> because<16:56:56.040> all<16:56:56.340> of<16:56:56.456> a<16:56:56.520> sudden<16:56:56.580> you're 16:56:56.746 --> 16:56:56.756 align:start position:0% fixes because all of a sudden you're 16:56:56.756 --> 16:56:58.246 align:start position:0% fixes because all of a sudden you're looking<16:56:56.880> at<16:56:57.060> the<16:56:57.240> wrong<16:56:57.360> devices<16:56:57.720> or<16:56:58.080> the 16:56:58.246 --> 16:56:58.256 align:start position:0% looking at the wrong devices or the 16:56:58.256 --> 16:56:59.926 align:start position:0% looking at the wrong devices or the wrong<16:56:58.380> ports<16:56:58.740> or<16:56:58.860> the<16:56:58.980> wrong<16:56:59.096> IP<16:56:59.456> addresses 16:56:59.926 --> 16:56:59.936 align:start position:0% wrong ports or the wrong IP addresses 16:56:59.936 --> 16:57:03.106 align:start position:0% wrong ports or the wrong IP addresses and<16:57:00.840> I've<16:57:00.956> been<16:57:01.200> there 16:57:03.106 --> 16:57:03.116 align:start position:0% and I've been there 16:57:03.116 --> 16:57:04.370 align:start position:0% and I've been there um so<16:57:03.540> yeah<16:57:03.660> that's<16:57:03.840> what<16:57:04.080> I've<16:57:04.200> said 16:57:04.370 --> 16:57:04.380 align:start position:0% um so yeah that's what I've said 16:57:04.380 --> 16:57:06.406 align:start position:0% um so yeah that's what I've said essential<16:57:04.916> Parts<16:57:05.160> include<16:57:05.580> Network<16:57:05.756> diagrams 16:57:06.406 --> 16:57:06.416 align:start position:0% essential Parts include Network diagrams 16:57:06.416 --> 16:57:09.406 align:start position:0% essential Parts include Network diagrams Asset<16:57:06.900> Management<16:57:07.080> IP<16:57:07.860> address<16:57:08.416> utilization 16:57:09.406 --> 16:57:09.416 align:start position:0% Asset Management IP address utilization 16:57:09.416 --> 16:57:11.690 align:start position:0% Asset Management IP address utilization you<16:57:10.256> could<16:57:10.320> have<16:57:10.500> more<16:57:10.740> or<16:57:10.860> less<16:57:11.040> depending<16:57:11.520> on 16:57:11.690 --> 16:57:11.700 align:start position:0% you could have more or less depending on 16:57:11.700 --> 16:57:14.330 align:start position:0% you could have more or less depending on your<16:57:11.880> organization<16:57:12.480> and<16:57:12.840> the<16:57:12.956> size<16:57:13.140> of<16:57:13.320> it<16:57:13.916> you 16:57:14.330 --> 16:57:14.340 align:start position:0% your organization and the size of it you 16:57:14.340 --> 16:57:16.190 align:start position:0% your organization and the size of it you did<16:57:14.456> information<16:57:14.820> about<16:57:15.240> the<16:57:15.540> vendors<16:57:15.900> and 16:57:16.190 --> 16:57:16.200 align:start position:0% did information about the vendors and 16:57:16.200 --> 16:57:19.786 align:start position:0% did information about the vendors and contractors<16:57:17.296> procedures<16:57:18.296> and<16:57:18.480> policies<16:57:19.080> who 16:57:19.786 --> 16:57:19.796 align:start position:0% contractors procedures and policies who 16:57:19.796 --> 16:57:22.130 align:start position:0% contractors procedures and policies who should<16:57:20.040> be<16:57:20.160> doing<16:57:20.340> what<16:57:20.580> and<16:57:20.820> when<16:57:21.000> and<16:57:21.900> also 16:57:22.130 --> 16:57:22.140 align:start position:0% should be doing what and when and also 16:57:22.140 --> 16:57:24.050 align:start position:0% should be doing what and when and also logical<16:57:22.616> and 16:57:24.050 --> 16:57:24.060 align:start position:0% logical and 16:57:24.060 --> 16:57:28.010 align:start position:0% logical and um<16:57:24.180> physical<16:57:24.980> this<16:57:25.980> is<16:57:26.160> a 16:57:28.010 --> 16:57:28.020 align:start position:0% um physical this is a 16:57:28.020 --> 16:57:30.946 align:start position:0% um physical this is a a<16:57:28.740> topology<16:57:29.340> diagram<16:57:29.936> of<16:57:30.416> all<16:57:30.540> the<16:57:30.720> hardware 16:57:30.946 --> 16:57:30.956 align:start position:0% a topology diagram of all the hardware 16:57:30.956 --> 16:57:32.990 align:start position:0% a topology diagram of all the hardware and<16:57:31.740> the<16:57:31.860> connections<16:57:32.340> we<16:57:32.520> haven't<16:57:32.580> named<16:57:32.936> the 16:57:32.990 --> 16:57:33.000 align:start position:0% and the connections we haven't named the 16:57:33.000 --> 16:57:35.210 align:start position:0% and the connections we haven't named the ports<16:57:33.360> on<16:57:33.480> this<16:57:33.660> particular<16:57:33.956> diagram<16:57:34.436> it's 16:57:35.210 --> 16:57:35.220 align:start position:0% ports on this particular diagram it's 16:57:35.220 --> 16:57:37.786 align:start position:0% ports on this particular diagram it's copyright<16:57:35.756> as<16:57:36.116> Scott<16:57:36.360> McDonald 16:57:37.786 --> 16:57:37.796 align:start position:0% copyright as Scott McDonald 16:57:37.796 --> 16:57:39.710 align:start position:0% copyright as Scott McDonald uh<16:57:38.400> just<16:57:38.520> to<16:57:38.700> give<16:57:38.756> you<16:57:38.880> an<16:57:39.000> idea<16:57:39.240> this<16:57:39.416> looks 16:57:39.710 --> 16:57:39.720 align:start position:0% uh just to give you an idea this looks 16:57:39.720 --> 16:57:41.746 align:start position:0% uh just to give you an idea this looks like<16:57:39.776> it<16:57:39.956> was<16:57:40.080> done<16:57:40.256> in<16:57:40.436> Vizio<16:57:40.916> which<16:57:41.340> is<16:57:41.456> a 16:57:41.746 --> 16:57:41.756 align:start position:0% like it was done in Vizio which is a 16:57:41.756 --> 16:57:44.390 align:start position:0% like it was done in Vizio which is a Cisco<16:57:42.296> Network<16:57:43.020> creation 16:57:44.390 --> 16:57:44.400 align:start position:0% Cisco Network creation 16:57:44.400 --> 16:57:46.310 align:start position:0% Cisco Network creation um<16:57:44.416> diagramming<16:57:45.416> tool<16:57:45.660> there's<16:57:45.840> others<16:57:46.200> out 16:57:46.310 --> 16:57:46.320 align:start position:0% um diagramming tool there's others out 16:57:46.320 --> 16:57:48.710 align:start position:0% um diagramming tool there's others out there<16:57:46.560> it's<16:57:47.276> a<16:57:47.520> free<16:57:47.700> to<16:57:47.880> troll<16:57:48.116> or<16:57:48.480> some<16:57:48.596> are 16:57:48.710 --> 16:57:48.720 align:start position:0% there it's a free to troll or some are 16:57:48.720 --> 16:57:50.086 align:start position:0% there it's a free to troll or some are free<16:57:48.840> to<16:57:49.080> use 16:57:50.086 --> 16:57:50.096 align:start position:0% free to use 16:57:50.096 --> 16:57:51.530 align:start position:0% free to use and<16:57:50.640> it<16:57:50.756> shows<16:57:51.000> you<16:57:51.060> all<16:57:51.180> your<16:57:51.296> different 16:57:51.530 --> 16:57:51.540 align:start position:0% and it shows you all your different 16:57:51.540 --> 16:57:53.570 align:start position:0% and it shows you all your different devices 16:57:53.570 --> 16:57:53.580 align:start position:0% devices 16:57:53.580 --> 16:57:56.210 align:start position:0% devices The<16:57:53.936> Logical<16:57:54.240> provides<16:57:55.020> the<16:57:55.436> logical<16:57:55.796> view<16:57:55.980> of 16:57:56.210 --> 16:57:56.220 align:start position:0% The Logical provides the logical view of 16:57:56.220 --> 16:57:58.786 align:start position:0% The Logical provides the logical view of how<16:57:56.400> the<16:57:56.580> network<16:57:56.756> sees<16:57:57.296> itself<16:57:57.596> not<16:57:58.380> how<16:57:58.680> we 16:57:58.786 --> 16:57:58.796 align:start position:0% how the network sees itself not how we 16:57:58.796 --> 16:58:00.406 align:start position:0% how the network sees itself not how we will<16:57:58.980> physically<16:57:59.340> see<16:57:59.520> the<16:57:59.756> network<16:57:59.880> in<16:58:00.240> the 16:58:00.406 --> 16:58:00.416 align:start position:0% will physically see the network in the 16:58:00.416 --> 16:58:02.690 align:start position:0% will physically see the network in the server<16:58:00.776> room 16:58:02.690 --> 16:58:02.700 align:start position:0% server room 16:58:02.700 --> 16:58:04.670 align:start position:0% server room uh<16:58:03.296> indicates<16:58:03.720> how<16:58:03.900> the<16:58:04.080> traffic<16:58:04.200> flows 16:58:04.670 --> 16:58:04.680 align:start position:0% uh indicates how the traffic flows 16:58:04.680 --> 16:58:06.586 align:start position:0% uh indicates how the traffic flows between<16:58:04.860> devices<16:58:05.276> in<16:58:05.640> the<16:58:05.820> network<16:58:05.936> so<16:58:06.360> you'll 16:58:06.586 --> 16:58:06.596 align:start position:0% between devices in the network so you'll 16:58:06.596 --> 16:58:09.010 align:start position:0% between devices in the network so you'll see<16:58:06.720> all<16:58:06.956> of<16:58:07.080> your<16:58:07.200> vlans<16:58:07.860> routing 16:58:09.010 --> 16:58:09.020 align:start position:0% see all of your vlans routing 16:58:09.020 --> 16:58:11.570 align:start position:0% see all of your vlans routing redistribution<16:58:10.040> all<16:58:11.040> these<16:58:11.220> kind<16:58:11.340> of<16:58:11.456> things 16:58:11.570 --> 16:58:11.580 align:start position:0% redistribution all these kind of things 16:58:11.580 --> 16:58:14.030 align:start position:0% redistribution all these kind of things bgp<16:58:12.240> if<16:58:12.480> you<16:58:12.660> have<16:58:12.776> it 16:58:14.030 --> 16:58:14.040 align:start position:0% bgp if you have it 16:58:14.040 --> 16:58:16.786 align:start position:0% bgp if you have it a<16:58:14.580> logical<16:58:14.936> net<16:58:15.180> Network<16:58:15.840> diagrams<16:58:16.436> include 16:58:16.786 --> 16:58:16.796 align:start position:0% a logical net Network diagrams include 16:58:16.796 --> 16:58:19.786 align:start position:0% a logical net Network diagrams include domain<16:58:17.220> names<16:58:17.400> IP<16:58:17.936> addresses<16:58:18.480> and<16:58:18.956> the<16:58:19.500> tasks 16:58:19.786 --> 16:58:19.796 align:start position:0% domain names IP addresses and the tasks 16:58:19.796 --> 16:58:22.786 align:start position:0% domain names IP addresses and the tasks performed<16:58:20.160> by<16:58:20.340> each<16:58:20.640> different<16:58:20.880> device 16:58:22.786 --> 16:58:22.796 align:start position:0% performed by each different device 16:58:22.796 --> 16:58:25.490 align:start position:0% performed by each different device logically<16:58:23.580> includes<16:58:24.540> how<16:58:24.956> devices 16:58:25.490 --> 16:58:25.500 align:start position:0% logically includes how devices 16:58:25.500 --> 16:58:27.530 align:start position:0% logically includes how devices communicate<16:58:26.096> with<16:58:26.276> each<16:58:26.520> other<16:58:26.700> which 16:58:27.530 --> 16:58:27.540 align:start position:0% communicate with each other which 16:58:27.540 --> 16:58:30.050 align:start position:0% communicate with each other which direction<16:58:27.776> the<16:58:28.140> traffic<16:58:28.320> flows 16:58:30.050 --> 16:58:30.060 align:start position:0% direction the traffic flows 16:58:30.060 --> 16:58:33.230 align:start position:0% direction the traffic flows and<16:58:30.596> how<16:58:30.776> all<16:58:30.956> these<16:58:31.200> devices<16:58:31.380> work<16:58:31.740> together 16:58:33.230 --> 16:58:33.240 align:start position:0% and how all these devices work together 16:58:33.240 --> 16:58:35.150 align:start position:0% and how all these devices work together the<16:58:33.720> physical<16:58:33.840> network<16:58:34.200> shows<16:58:34.740> the<16:58:34.860> actual 16:58:35.150 --> 16:58:35.160 align:start position:0% the physical network shows the actual 16:58:35.160 --> 16:58:36.830 align:start position:0% the physical network shows the actual physical<16:58:35.400> connection<16:58:35.880> so<16:58:36.296> you<16:58:36.416> can<16:58:36.540> look<16:58:36.660> at 16:58:36.830 --> 16:58:36.840 align:start position:0% physical connection so you can look at 16:58:36.840 --> 16:58:39.710 align:start position:0% physical connection so you can look at the<16:58:37.020> diagram<16:58:37.320> of<16:58:38.160> a<16:58:38.340> certain<16:58:38.456> router<16:58:39.116> and<16:58:39.596> you 16:58:39.710 --> 16:58:39.720 align:start position:0% the diagram of a certain router and you 16:58:39.720 --> 16:58:41.570 align:start position:0% the diagram of a certain router and you can<16:58:39.840> see<16:58:40.020> which<16:58:40.380> ports 16:58:41.570 --> 16:58:41.580 align:start position:0% can see which ports 16:58:41.580 --> 16:58:44.030 align:start position:0% can see which ports are<16:58:42.360> on<16:58:42.540> the<16:58:42.660> router<16:58:43.020> how<16:58:43.256> many<16:58:43.436> and<16:58:43.680> what<16:58:43.860> it's 16:58:44.030 --> 16:58:44.040 align:start position:0% are on the router how many and what it's 16:58:44.040 --> 16:58:46.906 align:start position:0% are on the router how many and what it's actually<16:58:44.220> physically<16:58:44.700> connected<16:58:45.480> to<16:58:46.200> and<16:58:46.740> a 16:58:46.906 --> 16:58:46.916 align:start position:0% actually physically connected to and a 16:58:46.916 --> 16:58:48.286 align:start position:0% actually physically connected to and a lot<16:58:46.980> of<16:58:47.096> companies<16:58:47.400> use<16:58:47.580> the<16:58:47.756> concept<16:58:48.060> of 16:58:48.286 --> 16:58:48.296 align:start position:0% lot of companies use the concept of 16:58:48.296 --> 16:58:50.510 align:start position:0% lot of companies use the concept of remote<16:58:48.596> hands<16:58:49.140> so<16:58:49.740> you<16:58:49.916> can<16:58:49.980> use<16:58:50.160> these 16:58:50.510 --> 16:58:50.520 align:start position:0% remote hands so you can use these 16:58:50.520 --> 16:58:52.850 align:start position:0% remote hands so you can use these diagrams<16:58:50.880> to<16:58:51.116> tell<16:58:51.240> the<16:58:51.416> remote<16:58:51.660> hands<16:58:52.256> where 16:58:52.850 --> 16:58:52.860 align:start position:0% diagrams to tell the remote hands where 16:58:52.860 --> 16:58:55.490 align:start position:0% diagrams to tell the remote hands where to<16:58:52.980> find<16:58:53.160> the<16:58:53.400> device<16:58:53.596> and<16:58:54.596> which<16:58:54.776> cable<16:58:55.140> to 16:58:55.490 --> 16:58:55.500 align:start position:0% to find the device and which cable to 16:58:55.500 --> 16:58:59.890 align:start position:0% to find the device and which cable to plug<16:58:56.400> unplug<16:58:57.296> Etc 16:58:59.890 --> 16:58:59.900 align:start position:0% 16:58:59.900 --> 16:59:02.510 align:start position:0% physical<16:59:00.900> network<16:59:01.256> is<16:59:01.616> the<16:59:01.796> physical<16:59:01.980> layout 16:59:02.510 --> 16:59:02.520 align:start position:0% physical network is the physical layout 16:59:02.520 --> 16:59:06.230 align:start position:0% physical network is the physical layout that<16:59:03.060> I've<16:59:03.240> mentioned<16:59:04.040> so<16:59:05.040> here's<16:59:05.820> a<16:59:05.936> typical 16:59:06.230 --> 16:59:06.240 align:start position:0% that I've mentioned so here's a typical 16:59:06.240 --> 16:59:08.870 align:start position:0% that I've mentioned so here's a typical diagram<16:59:06.776> above<16:59:07.616> is<16:59:07.796> the<16:59:08.040> physical<16:59:08.220> topology 16:59:08.870 --> 16:59:08.880 align:start position:0% diagram above is the physical topology 16:59:08.880 --> 16:59:12.170 align:start position:0% diagram above is the physical topology and<16:59:09.840> below<16:59:10.140> is<16:59:10.320> logical<16:59:10.740> topology 16:59:12.170 --> 16:59:12.180 align:start position:0% and below is logical topology 16:59:12.180 --> 16:59:15.406 align:start position:0% and below is logical topology so<16:59:12.840> you<16:59:13.020> might<16:59:13.200> not<16:59:13.380> necessarily<16:59:13.980> see<16:59:14.400> all<16:59:15.296> of 16:59:15.406 --> 16:59:15.416 align:start position:0% so you might not necessarily see all of 16:59:15.416 --> 16:59:17.030 align:start position:0% so you might not necessarily see all of the<16:59:15.540> hardware<16:59:15.660> devices<16:59:16.256> you're<16:59:16.680> going<16:59:16.796> to<16:59:16.916> see 16:59:17.030 --> 16:59:17.040 align:start position:0% the hardware devices you're going to see 16:59:17.040 --> 16:59:19.010 align:start position:0% the hardware devices you're going to see things<16:59:17.220> like<16:59:17.400> vlans<16:59:18.060> connections<16:59:18.660> going<16:59:18.840> out 16:59:19.010 --> 16:59:19.020 align:start position:0% things like vlans connections going out 16:59:19.020 --> 16:59:20.746 align:start position:0% things like vlans connections going out to<16:59:19.200> isps 16:59:20.746 --> 16:59:20.756 align:start position:0% to isps 16:59:20.756 --> 16:59:23.690 align:start position:0% to isps and<16:59:21.480> hot<16:59:21.720> standby<16:59:22.200> routing<16:59:22.680> protocol<16:59:23.160> all 16:59:23.690 --> 16:59:23.700 align:start position:0% and hot standby routing protocol all 16:59:23.700 --> 16:59:24.946 align:start position:0% and hot standby routing protocol all this<16:59:23.820> kind<16:59:24.060> of<16:59:24.180> thing 16:59:24.946 --> 16:59:24.956 align:start position:0% this kind of thing 16:59:24.956 --> 16:59:27.286 align:start position:0% this kind of thing uh<16:59:25.560> you<16:59:25.796> won't<16:59:25.916> generally<16:59:26.276> see<16:59:26.520> end<16:59:26.880> devices 16:59:27.286 --> 16:59:27.296 align:start position:0% uh you won't generally see end devices 16:59:27.296 --> 16:59:30.106 align:start position:0% uh you won't generally see end devices on<16:59:28.020> the<16:59:28.200> topology<16:59:28.680> diagram<16:59:29.220> so<16:59:29.580> this<16:59:29.756> is<16:59:29.936> a 16:59:30.106 --> 16:59:30.116 align:start position:0% on the topology diagram so this is a 16:59:30.116 --> 16:59:32.150 align:start position:0% on the topology diagram so this is a very<16:59:30.240> small<16:59:30.416> Network<16:59:30.776> or<16:59:31.500> unless<16:59:31.796> one<16:59:31.980> of<16:59:32.096> the 16:59:32.150 --> 16:59:32.160 align:start position:0% very small Network or unless one of the 16:59:32.160 --> 16:59:34.370 align:start position:0% very small Network or unless one of the end<16:59:32.276> devices<16:59:32.640> happens<16:59:33.416> to<16:59:33.660> be<16:59:33.840> your<16:59:34.200> network 16:59:34.370 --> 16:59:34.380 align:start position:0% end devices happens to be your network 16:59:34.380 --> 16:59:38.510 align:start position:0% end devices happens to be your network management<16:59:34.740> server<16:59:35.400> or<16:59:35.580> something<16:59:35.936> like<16:59:36.296> that 16:59:38.510 --> 16:59:38.520 align:start position:0% 16:59:38.520 --> 16:59:40.786 align:start position:0% so<16:59:39.060> your<16:59:39.360> documentation<16:59:39.900> should<16:59:40.320> include 16:59:40.786 --> 16:59:40.796 align:start position:0% so your documentation should include 16:59:40.796 --> 16:59:43.850 align:start position:0% so your documentation should include notes<16:59:41.580> about<16:59:41.700> Asset<16:59:42.180> Management<16:59:42.740> a<16:59:43.740> whole 16:59:43.850 --> 16:59:43.860 align:start position:0% notes about Asset Management a whole 16:59:43.860 --> 16:59:45.530 align:start position:0% notes about Asset Management a whole bunch<16:59:44.040> of<16:59:44.160> things<16:59:44.340> name<16:59:44.880> model<16:59:45.240> number 16:59:45.530 --> 16:59:45.540 align:start position:0% bunch of things name model number 16:59:45.540 --> 16:59:48.650 align:start position:0% bunch of things name model number manufacturer<16:59:46.500> data<16:59:47.040> purchase<16:59:47.456> a<16:59:48.240> version<16:59:48.480> of 16:59:48.650 --> 16:59:48.660 align:start position:0% manufacturer data purchase a version of 16:59:48.660 --> 16:59:50.650 align:start position:0% manufacturer data purchase a version of software<16:59:49.020> running<16:59:49.256> does<16:59:49.616> it<16:59:49.796> need<16:59:49.916> updating 16:59:50.650 --> 16:59:50.660 align:start position:0% software running does it need updating 16:59:50.660 --> 16:59:53.086 align:start position:0% software running does it need updating is<16:59:51.660> there<16:59:51.900> problems<16:59:52.200> of<16:59:52.380> that<16:59:52.616> particular 16:59:53.086 --> 16:59:53.096 align:start position:0% is there problems of that particular 16:59:53.096 --> 16:59:56.150 align:start position:0% is there problems of that particular release<16:59:53.456> of<16:59:53.880> software<16:59:54.660> updates<16:59:55.160> location 16:59:56.150 --> 16:59:56.160 align:start position:0% release of software updates location 16:59:56.160 --> 16:59:57.830 align:start position:0% release of software updates location warranty<16:59:56.936> and<16:59:57.116> who<16:59:57.296> has<16:59:57.480> it<16:59:57.596> who's 16:59:57.830 --> 16:59:57.840 align:start position:0% warranty and who has it who's 16:59:57.840 --> 16:59:59.870 align:start position:0% warranty and who has it who's responsible<16:59:58.380> for<16:59:58.680> it<16:59:58.796> if<16:59:59.456> you're<16:59:59.520> sitting 16:59:59.870 --> 16:59:59.880 align:start position:0% responsible for it if you're sitting 16:59:59.880 --> 17:00:01.850 align:start position:0% responsible for it if you're sitting under<17:00:00.000> some<17:00:00.596> under<17:00:00.900> somebody's<17:00:01.320> desk<17:00:01.560> and 17:00:01.850 --> 17:00:01.860 align:start position:0% under some under somebody's desk and 17:00:01.860 --> 17:00:03.350 align:start position:0% under some under somebody's desk and nobody<17:00:02.160> knows<17:00:02.456> and<17:00:02.640> it<17:00:02.756> doesn't<17:00:02.880> serve<17:00:03.180> any 17:00:03.350 --> 17:00:03.360 align:start position:0% nobody knows and it doesn't serve any 17:00:03.360 --> 17:00:04.490 align:start position:0% nobody knows and it doesn't serve any purpose 17:00:04.490 --> 17:00:04.500 align:start position:0% purpose 17:00:04.500 --> 17:00:06.470 align:start position:0% purpose so<17:00:05.040> you<17:00:05.220> should<17:00:05.400> keep<17:00:05.756> track<17:00:05.936> of<17:00:06.116> all<17:00:06.296> your 17:00:06.470 --> 17:00:06.480 align:start position:0% so you should keep track of all your 17:00:06.480 --> 17:00:08.870 align:start position:0% so you should keep track of all your assets<17:00:06.776> and<17:00:07.380> eventually<17:00:07.740> there's<17:00:08.096> normally<17:00:08.640> a 17:00:08.870 --> 17:00:08.880 align:start position:0% assets and eventually there's normally a 17:00:08.880 --> 17:00:09.890 align:start position:0% assets and eventually there's normally a disposal 17:00:09.890 --> 17:00:09.900 align:start position:0% disposal 17:00:09.900 --> 17:00:11.746 align:start position:0% disposal a<17:00:10.320> procedure<17:00:10.796> as<17:00:10.916> well<17:00:11.096> where<17:00:11.340> the<17:00:11.520> devices 17:00:11.746 --> 17:00:11.756 align:start position:0% a procedure as well where the devices 17:00:11.756 --> 17:00:16.550 align:start position:0% a procedure as well where the devices are<17:00:12.480> wiped<17:00:13.580> and<17:00:14.776> fragmented<17:00:15.776> defragmented 17:00:16.550 --> 17:00:16.560 align:start position:0% are wiped and fragmented defragmented 17:00:16.560 --> 17:00:20.630 align:start position:0% are wiped and fragmented defragmented whatever<17:00:16.796> and<17:00:17.640> whatever<17:00:17.880> type<17:00:18.660> of<17:00:19.140> um 17:00:20.630 --> 17:00:20.640 align:start position:0% whatever and whatever type of um 17:00:20.640 --> 17:00:22.606 align:start position:0% whatever and whatever type of um scrubbing<17:00:21.480> is<17:00:21.596> done<17:00:21.776> on<17:00:21.956> their<17:00:22.080> drives<17:00:22.436> if 17:00:22.606 --> 17:00:22.616 align:start position:0% scrubbing is done on their drives if 17:00:22.616 --> 17:00:24.830 align:start position:0% scrubbing is done on their drives if necessary<17:00:23.160> so<17:00:23.456> there's<17:00:23.700> no<17:00:23.880> data<17:00:24.660> that's 17:00:24.830 --> 17:00:24.840 align:start position:0% necessary so there's no data that's 17:00:24.840 --> 17:00:27.946 align:start position:0% necessary so there's no data that's important<17:00:25.640> devices<17:00:26.640> are<17:00:27.240> tagged<17:00:27.660> with<17:00:27.776> the 17:00:27.946 --> 17:00:27.956 align:start position:0% important devices are tagged with the 17:00:27.956 --> 17:00:31.190 align:start position:0% important devices are tagged with the barcodes<17:00:28.380> or<17:00:28.616> RFID<17:00:29.340> is<17:00:30.116> an<17:00:30.360> example<17:00:30.660> of<17:00:30.900> one 17:00:31.190 --> 17:00:31.200 align:start position:0% barcodes or RFID is an example of one 17:00:31.200 --> 17:00:33.766 align:start position:0% barcodes or RFID is an example of one here<17:00:31.560> these<17:00:32.276> are<17:00:32.400> normally<17:00:32.640> read<17:00:32.820> by<17:00:33.060> little 17:00:33.766 --> 17:00:33.776 align:start position:0% here these are normally read by little 17:00:33.776 --> 17:00:35.330 align:start position:0% here these are normally read by little um reader<17:00:34.500> gun<17:00:34.616> like<17:00:34.796> you<17:00:34.980> find<17:00:35.160> in 17:00:35.330 --> 17:00:35.340 align:start position:0% um reader gun like you find in 17:00:35.340 --> 17:00:37.670 align:start position:0% um reader gun like you find in supermarkets<17:00:36.060> if<17:00:36.840> it's<17:00:37.020> been<17:00:37.200> tagged<17:00:37.436> with<17:00:37.500> a 17:00:37.670 --> 17:00:37.680 align:start position:0% supermarkets if it's been tagged with a 17:00:37.680 --> 17:00:39.230 align:start position:0% supermarkets if it's been tagged with a barcode<17:00:38.096> a<17:00:38.340> barcode<17:00:38.700> scanner<17:00:39.000> will<17:00:39.116> help 17:00:39.230 --> 17:00:39.240 align:start position:0% barcode a barcode scanner will help 17:00:39.240 --> 17:00:41.150 align:start position:0% barcode a barcode scanner will help retrieve<17:00:39.596> information 17:00:41.150 --> 17:00:41.160 align:start position:0% retrieve information 17:00:41.160 --> 17:00:43.730 align:start position:0% retrieve information and<17:00:41.580> the<17:00:41.756> RFID<17:00:42.180> stands<17:00:42.840> for<17:00:42.956> radio<17:00:43.200> frequency 17:00:43.730 --> 17:00:43.740 align:start position:0% and the RFID stands for radio frequency 17:00:43.740 --> 17:00:46.246 align:start position:0% and the RFID stands for radio frequency ID<17:00:44.096> tags<17:00:44.936> that<17:00:45.060> normally<17:00:45.360> have<17:00:45.596> electrically 17:00:46.246 --> 17:00:46.256 align:start position:0% ID tags that normally have electrically 17:00:46.256 --> 17:00:48.830 align:start position:0% ID tags that normally have electrically stored<17:00:46.980> information<17:00:47.240> and<17:00:48.240> the<17:00:48.416> readers<17:00:48.720> are 17:00:48.830 --> 17:00:48.840 align:start position:0% stored information and the readers are 17:00:48.840 --> 17:00:50.510 align:start position:0% stored information and the readers are used<17:00:48.956> to<17:00:49.140> track<17:00:49.320> devices<17:00:49.740> this<17:00:50.400> would 17:00:50.510 --> 17:00:50.520 align:start position:0% used to track devices this would 17:00:50.520 --> 17:00:53.510 align:start position:0% used to track devices this would obviously<17:00:50.756> be<17:00:50.936> on<17:00:51.116> a<17:00:51.296> pretty<17:00:51.416> big<17:00:51.596> Network 17:00:53.510 --> 17:00:53.520 align:start position:0% obviously be on a pretty big Network 17:00:53.520 --> 17:00:54.530 align:start position:0% obviously be on a pretty big Network um 17:00:54.530 --> 17:00:54.540 align:start position:0% um 17:00:54.540 --> 17:00:56.746 align:start position:0% um yeah<17:00:55.080> Network<17:00:55.740> documentation<17:00:56.456> should 17:00:56.746 --> 17:00:56.756 align:start position:0% yeah Network documentation should 17:00:56.756 --> 17:00:58.786 align:start position:0% yeah Network documentation should include<17:00:57.116> your<17:00:57.480> IP<17:00:57.776> address<17:00:57.956> utilization 17:00:58.786 --> 17:00:58.796 align:start position:0% include your IP address utilization 17:00:58.796 --> 17:01:01.490 align:start position:0% include your IP address utilization there's<17:00:59.700> normally<17:01:00.000> one<17:01:00.296> or<17:01:00.480> two<17:01:00.660> people<17:01:00.900> in 17:01:01.490 --> 17:01:01.500 align:start position:0% there's normally one or two people in 17:01:01.500 --> 17:01:04.010 align:start position:0% there's normally one or two people in charge<17:01:01.616> of<17:01:01.916> allocating<17:01:02.520> addresses<17:01:03.360> or<17:01:03.596> blocks 17:01:04.010 --> 17:01:04.020 align:start position:0% charge of allocating addresses or blocks 17:01:04.020 --> 17:01:05.210 align:start position:0% charge of allocating addresses or blocks of<17:01:04.080> addresses 17:01:05.210 --> 17:01:05.220 align:start position:0% of addresses 17:01:05.220 --> 17:01:07.730 align:start position:0% of addresses because<17:01:05.700> they're<17:01:06.116> aware<17:01:06.540> of<17:01:06.900> which<17:01:07.200> addresses 17:01:07.730 --> 17:01:07.740 align:start position:0% because they're aware of which addresses 17:01:07.740 --> 17:01:10.070 align:start position:0% because they're aware of which addresses should<17:01:08.040> be<17:01:08.160> where<17:01:08.400> which<17:01:08.640> subnets<17:01:09.180> and<17:01:09.840> which 17:01:10.070 --> 17:01:10.080 align:start position:0% should be where which subnets and which 17:01:10.080 --> 17:01:12.230 align:start position:0% should be where which subnets and which addresses<17:01:10.560> are<17:01:10.980> summarized 17:01:12.230 --> 17:01:12.240 align:start position:0% addresses are summarized 17:01:12.240 --> 17:01:14.570 align:start position:0% addresses are summarized and<17:01:12.956> this<17:01:13.140> helps<17:01:13.680> with<17:01:13.740> all<17:01:13.980> of<17:01:14.096> our<17:01:14.220> routing 17:01:14.570 --> 17:01:14.580 align:start position:0% and this helps with all of our routing 17:01:14.580 --> 17:01:17.266 align:start position:0% and this helps with all of our routing updates<17:01:15.000> I<17:01:15.956> have<17:01:16.080> seen<17:01:16.320> problems<17:01:16.680> in<17:01:16.860> the<17:01:17.040> in 17:01:17.266 --> 17:01:17.276 align:start position:0% updates I have seen problems in the in 17:01:17.276 --> 17:01:19.310 align:start position:0% updates I have seen problems in the in the<17:01:17.456> past<17:01:17.820> and<17:01:18.360> people<17:01:18.596> should<17:01:18.900> know<17:01:19.080> better 17:01:19.310 --> 17:01:19.320 align:start position:0% the past and people should know better 17:01:19.320 --> 17:01:22.190 align:start position:0% the past and people should know better in<17:01:19.740> fact<17:01:19.860> have<17:01:20.700> manually<17:01:21.116> allocated<17:01:21.776> IP 17:01:22.190 --> 17:01:22.200 align:start position:0% in fact have manually allocated IP 17:01:22.200 --> 17:01:23.926 align:start position:0% in fact have manually allocated IP addresses<17:01:22.680> to<17:01:22.860> their<17:01:23.040> devices<17:01:23.220> for<17:01:23.700> whatever 17:01:23.926 --> 17:01:23.936 align:start position:0% addresses to their devices for whatever 17:01:23.936 --> 17:01:26.030 align:start position:0% addresses to their devices for whatever reason<17:01:24.540> and<17:01:25.380> it's<17:01:25.560> caused<17:01:25.916> Network 17:01:26.030 --> 17:01:26.040 align:start position:0% reason and it's caused Network 17:01:26.040 --> 17:01:27.890 align:start position:0% reason and it's caused Network instability 17:01:27.890 --> 17:01:27.900 align:start position:0% instability 17:01:27.900 --> 17:01:29.570 align:start position:0% instability so<17:01:28.140> Network<17:01:28.380> administrators<17:01:29.160> should<17:01:29.400> keep 17:01:29.570 --> 17:01:29.580 align:start position:0% so Network administrators should keep 17:01:29.580 --> 17:01:31.310 align:start position:0% so Network administrators should keep track<17:01:29.756> of<17:01:29.936> the<17:01:30.060> number<17:01:30.180> of<17:01:30.296> IP<17:01:30.596> addresses<17:01:31.140> that 17:01:31.310 --> 17:01:31.320 align:start position:0% track of the number of IP addresses that 17:01:31.320 --> 17:01:33.470 align:start position:0% track of the number of IP addresses that have<17:01:31.500> been<17:01:31.560> allocated<17:01:31.980> to<17:01:32.276> the<17:01:32.400> network<17:01:32.580> how 17:01:33.470 --> 17:01:33.480 align:start position:0% have been allocated to the network how 17:01:33.480 --> 17:01:34.906 align:start position:0% have been allocated to the network how many<17:01:33.596> have<17:01:33.776> been<17:01:33.956> in<17:01:34.080> user<17:01:34.436> it'll<17:01:34.740> normally 17:01:34.906 --> 17:01:34.916 align:start position:0% many have been in user it'll normally 17:01:34.916 --> 17:01:36.766 align:start position:0% many have been in user it'll normally Flagger<17:01:35.400> pay<17:01:35.520> alert<17:01:36.240> if<17:01:36.480> you're<17:01:36.596> running 17:01:36.766 --> 17:01:36.776 align:start position:0% Flagger pay alert if you're running 17:01:36.776 --> 17:01:38.330 align:start position:0% Flagger pay alert if you're running short 17:01:38.330 --> 17:01:38.340 align:start position:0% short 17:01:38.340 --> 17:01:40.606 align:start position:0% short if<17:01:38.700> a<17:01:38.880> subnet<17:01:39.240> grows<17:01:39.720> the<17:01:39.956> number<17:01:40.080> of<17:01:40.256> IP 17:01:40.606 --> 17:01:40.616 align:start position:0% if a subnet grows the number of IP 17:01:40.616 --> 17:01:42.406 align:start position:0% if a subnet grows the number of IP addresses<17:01:41.040> assigned<17:01:41.456> to<17:01:41.580> it<17:01:41.700> you're<17:01:42.116> likely 17:01:42.406 --> 17:01:42.416 align:start position:0% addresses assigned to it you're likely 17:01:42.416 --> 17:01:44.630 align:start position:0% addresses assigned to it you're likely to<17:01:42.540> have<17:01:42.660> a<17:01:42.840> problem 17:01:44.630 --> 17:01:44.640 align:start position:0% to have a problem 17:01:44.640 --> 17:01:47.330 align:start position:0% to have a problem okay<17:01:45.296> all<17:01:45.720> important<17:01:46.200> to<17:01:46.380> keep<17:01:46.560> uh<17:01:46.980> you<17:01:47.220> know 17:01:47.330 --> 17:01:47.340 align:start position:0% okay all important to keep uh you know 17:01:47.340 --> 17:01:49.190 align:start position:0% okay all important to keep uh you know the<17:01:47.580> utilization<17:01:48.116> as<17:01:48.416> I've<17:01:48.540> said<17:01:48.720> in<17:01:48.900> case<17:01:49.020> we 17:01:49.190 --> 17:01:49.200 align:start position:0% the utilization as I've said in case we 17:01:49.200 --> 17:01:50.690 align:start position:0% the utilization as I've said in case we need<17:01:49.320> to<17:01:49.436> run<17:01:49.560> out<17:01:49.680> or<17:01:49.860> buy<17:01:49.980> some<17:01:50.220> more<17:01:50.340> order 17:01:50.690 --> 17:01:50.700 align:start position:0% need to run out or buy some more order 17:01:50.700 --> 17:01:51.946 align:start position:0% need to run out or buy some more order them<17:01:50.936> in<17:01:51.116> advance 17:01:51.946 --> 17:01:51.956 align:start position:0% them in advance 17:01:51.956 --> 17:01:53.690 align:start position:0% them in advance you<17:01:52.320> should<17:01:52.436> also<17:01:52.740> have<17:01:52.916> information<17:01:53.160> about 17:01:53.690 --> 17:01:53.700 align:start position:0% you should also have information about 17:01:53.700 --> 17:01:59.210 align:start position:0% you should also have information about vendors<17:01:54.296> and<17:01:54.596> contractors 17:01:59.210 --> 17:01:59.220 align:start position:0% 17:01:59.220 --> 17:02:01.426 align:start position:0% that<17:02:00.116> should<17:02:00.296> include<17:02:00.540> vendor<17:02:00.956> names<17:02:01.080> their 17:02:01.426 --> 17:02:01.436 align:start position:0% that should include vendor names their 17:02:01.436 --> 17:02:03.710 align:start position:0% that should include vendor names their services<17:02:01.680> the<17:02:02.160> cost<17:02:02.340> contact<17:02:02.756> information<17:02:03.180> we 17:02:03.710 --> 17:02:03.720 align:start position:0% services the cost contact information we 17:02:03.720 --> 17:02:05.870 align:start position:0% services the cost contact information we normally<17:02:03.956> get<17:02:04.140> our<17:02:04.320> point<17:02:04.436> of<17:02:04.616> contact<17:02:04.880> and 17:02:05.870 --> 17:02:05.880 align:start position:0% normally get our point of contact and 17:02:05.880 --> 17:02:07.490 align:start position:0% normally get our point of contact and the<17:02:06.116> support<17:02:06.360> hours 17:02:07.490 --> 17:02:07.500 align:start position:0% the support hours 17:02:07.500 --> 17:02:09.170 align:start position:0% the support hours or<17:02:07.860> should<17:02:08.096> have<17:02:08.640> um 17:02:09.170 --> 17:02:09.180 align:start position:0% or should have um 17:02:09.180 --> 17:02:11.570 align:start position:0% or should have um documentation<17:02:10.020> about<17:02:10.256> all<17:02:10.616> of<17:02:10.740> our<17:02:10.916> policies 17:02:11.570 --> 17:02:11.580 align:start position:0% documentation about all of our policies 17:02:11.580 --> 17:02:14.266 align:start position:0% documentation about all of our policies and<17:02:11.756> standards<17:02:12.180> well<17:02:12.360> worth<17:02:12.596> looking<17:02:12.840> into<17:02:13.276> a 17:02:14.266 --> 17:02:14.276 align:start position:0% and standards well worth looking into a 17:02:14.276 --> 17:02:17.086 align:start position:0% and standards well worth looking into a project<17:02:14.520> management<17:02:14.880> and<17:02:15.416> also<17:02:15.720> ITIL<17:02:16.380> exams 17:02:17.086 --> 17:02:17.096 align:start position:0% project management and also ITIL exams 17:02:17.096 --> 17:02:19.606 align:start position:0% project management and also ITIL exams so<17:02:17.700> change<17:02:18.116> management<17:02:18.480> and<17:02:19.080> managing<17:02:19.436> all 17:02:19.606 --> 17:02:19.616 align:start position:0% so change management and managing all 17:02:19.616 --> 17:02:21.890 align:start position:0% so change management and managing all your<17:02:19.796> processes<17:02:20.340> and<17:02:20.580> procedures<17:02:21.060> and 17:02:21.890 --> 17:02:21.900 align:start position:0% your processes and procedures and 17:02:21.900 --> 17:02:25.330 align:start position:0% your processes and procedures and problems<17:02:22.380> and<17:02:22.796> on<17:02:22.980> the<17:02:23.160> network 17:02:25.330 --> 17:02:25.340 align:start position:0% problems and on the network 17:02:25.340 --> 17:02:27.650 align:start position:0% problems and on the network uh<17:02:26.340> provides<17:02:26.756> for<17:02:26.880> example<17:02:27.116> the<17:02:27.360> list<17:02:27.480> of 17:02:27.650 --> 17:02:27.660 align:start position:0% uh provides for example the list of 17:02:27.660 --> 17:02:29.570 align:start position:0% uh provides for example the list of people<17:02:27.776> who<17:02:28.020> should<17:02:28.200> be<17:02:28.320> contacted<17:02:28.860> certainly 17:02:29.570 --> 17:02:29.580 align:start position:0% people who should be contacted certainly 17:02:29.580 --> 17:02:31.190 align:start position:0% people who should be contacted certainly when<17:02:29.756> I<17:02:29.880> worked<17:02:30.180> on<17:02:30.296> a<17:02:30.480> pretty<17:02:30.660> large<17:02:30.840> Network 17:02:31.190 --> 17:02:31.200 align:start position:0% when I worked on a pretty large Network 17:02:31.200 --> 17:02:33.406 align:start position:0% when I worked on a pretty large Network there<17:02:31.616> was<17:02:31.796> a<17:02:31.980> number<17:02:32.160> of<17:02:32.340> key<17:02:32.640> people<17:02:32.880> so<17:02:33.180> you 17:02:33.406 --> 17:02:33.416 align:start position:0% there was a number of key people so you 17:02:33.416 --> 17:02:35.990 align:start position:0% there was a number of key people so you have<17:02:33.540> thousands<17:02:34.080> in<17:02:34.256> the<17:02:34.380> organization<17:02:35.000> that 17:02:35.990 --> 17:02:36.000 align:start position:0% have thousands in the organization that 17:02:36.000 --> 17:02:37.850 align:start position:0% have thousands in the organization that you<17:02:36.180> would<17:02:36.296> contact<17:02:36.540> four<17:02:37.020> or<17:02:37.256> five<17:02:37.436> or<17:02:37.616> six 17:02:37.850 --> 17:02:37.860 align:start position:0% you would contact four or five or six 17:02:37.860 --> 17:02:40.670 align:start position:0% you would contact four or five or six key<17:02:38.220> people<17:02:38.660> and<17:02:39.660> they<17:02:40.020> would<17:02:40.140> each<17:02:40.380> have<17:02:40.500> a 17:02:40.670 --> 17:02:40.680 align:start position:0% key people and they would each have a 17:02:40.680 --> 17:02:42.170 align:start position:0% key people and they would each have a role<17:02:40.916> of<17:02:40.980> who's<17:02:41.160> going<17:02:41.400> to<17:02:41.520> communicate<17:02:41.936> to 17:02:42.170 --> 17:02:42.180 align:start position:0% role of who's going to communicate to 17:02:42.180 --> 17:02:45.230 align:start position:0% role of who's going to communicate to who<17:02:42.480> who's<17:02:42.840> going<17:02:43.140> to<17:02:43.256> tell<17:02:43.380> the<17:02:43.560> boss<17:02:43.880> and<17:02:44.880> do 17:02:45.230 --> 17:02:45.240 align:start position:0% who who's going to tell the boss and do 17:02:45.240 --> 17:02:46.970 align:start position:0% who who's going to tell the boss and do the<17:02:45.360> does<17:02:45.720> the<17:02:45.956> press<17:02:46.080> or<17:02:46.320> other<17:02:46.500> customers 17:02:46.970 --> 17:02:46.980 align:start position:0% the does the press or other customers 17:02:46.980 --> 17:02:49.070 align:start position:0% the does the press or other customers need<17:02:47.220> to<17:02:47.340> be<17:02:47.520> informed<17:02:48.296> of<17:02:48.416> what's<17:02:48.596> going<17:02:48.840> on 17:02:49.070 --> 17:02:49.080 align:start position:0% need to be informed of what's going on 17:02:49.080 --> 17:02:51.766 align:start position:0% need to be informed of what's going on this<17:02:49.616> is<17:02:49.740> to<17:02:49.980> stop<17:02:50.220> uh<17:02:50.580> confusion<17:02:51.116> and<17:02:51.360> also 17:02:51.766 --> 17:02:51.776 align:start position:0% this is to stop uh confusion and also 17:02:51.776 --> 17:02:53.510 align:start position:0% this is to stop uh confusion and also track<17:02:52.380> back<17:02:52.616> as<17:02:52.796> to<17:02:52.980> who<17:02:53.096> should<17:02:53.276> have<17:02:53.400> been 17:02:53.510 --> 17:02:53.520 align:start position:0% track back as to who should have been 17:02:53.520 --> 17:02:55.070 align:start position:0% track back as to who should have been doing<17:02:53.700> what 17:02:55.070 --> 17:02:55.080 align:start position:0% doing what 17:02:55.080 --> 17:02:57.470 align:start position:0% doing what policies<17:02:55.916> require<17:02:56.160> compliance<17:02:56.880> and<17:02:57.116> in<17:02:57.296> their 17:02:57.470 --> 17:02:57.480 align:start position:0% policies require compliance and in their 17:02:57.480 --> 17:02:59.210 align:start position:0% policies require compliance and in their enforce<17:02:57.956> discipline<17:02:58.380> or<17:02:58.500> disciplinary 17:02:59.210 --> 17:02:59.220 align:start position:0% enforce discipline or disciplinary 17:02:59.220 --> 17:03:01.310 align:start position:0% enforce discipline or disciplinary actions<17:02:59.756> or<17:03:00.060> obviously<17:03:00.480> training<17:03:00.956> if<17:03:01.200> a 17:03:01.310 --> 17:03:01.320 align:start position:0% actions or obviously training if a 17:03:01.320 --> 17:03:03.106 align:start position:0% actions or obviously training if a person<17:03:01.500> hasn't<17:03:01.860> been<17:03:02.040> given<17:03:02.700> sufficient 17:03:03.106 --> 17:03:03.116 align:start position:0% person hasn't been given sufficient 17:03:03.116 --> 17:03:04.070 align:start position:0% person hasn't been given sufficient training 17:03:04.070 --> 17:03:04.080 align:start position:0% training 17:03:04.080 --> 17:03:05.990 align:start position:0% training and<17:03:04.436> normally<17:03:04.680> an<17:03:04.860> acceptable<17:03:05.220> use<17:03:05.456> policy 17:03:05.990 --> 17:03:06.000 align:start position:0% and normally an acceptable use policy 17:03:06.000 --> 17:03:08.086 align:start position:0% and normally an acceptable use policy which<17:03:06.240> new<17:03:06.540> people<17:03:06.776> will<17:03:07.080> sign<17:03:07.320> and<17:03:07.740> everyone 17:03:08.086 --> 17:03:08.096 align:start position:0% which new people will sign and everyone 17:03:08.096 --> 17:03:10.550 align:start position:0% which new people will sign and everyone has<17:03:08.340> to<17:03:08.456> sign<17:03:08.640> if<17:03:08.880> there's<17:03:09.000> any<17:03:09.180> changes<17:03:09.660> you 17:03:10.550 --> 17:03:10.560 align:start position:0% has to sign if there's any changes you 17:03:10.560 --> 17:03:13.070 align:start position:0% has to sign if there's any changes you standards<17:03:11.340> of<17:03:11.456> acceptable<17:03:11.936> behavior<17:03:12.776> on<17:03:12.956> the 17:03:13.070 --> 17:03:13.080 align:start position:0% standards of acceptable behavior on the 17:03:13.080 --> 17:03:15.106 align:start position:0% standards of acceptable behavior on the network 17:03:15.106 --> 17:03:15.116 align:start position:0% network 17:03:15.116 --> 17:03:17.870 align:start position:0% network for<17:03:15.840> example<17:03:16.080> creating<17:03:16.560> strong<17:03:16.820> passwords<17:03:17.820> is 17:03:17.870 --> 17:03:17.880 align:start position:0% for example creating strong passwords is 17:03:17.880 --> 17:03:19.786 align:start position:0% for example creating strong passwords is a<17:03:18.060> very<17:03:18.180> good<17:03:18.360> one<17:03:18.540> and<17:03:19.256> obviously<17:03:19.560> not 17:03:19.786 --> 17:03:19.796 align:start position:0% a very good one and obviously not 17:03:19.796 --> 17:03:21.230 align:start position:0% a very good one and obviously not putting<17:03:20.160> it<17:03:20.220> on<17:03:20.400> a<17:03:20.520> Post-It<17:03:20.820> note<17:03:21.000> and 17:03:21.230 --> 17:03:21.240 align:start position:0% putting it on a Post-It note and 17:03:21.240 --> 17:03:23.330 align:start position:0% putting it on a Post-It note and sticking<17:03:21.540> it<17:03:21.660> on<17:03:21.776> your<17:03:21.956> monitor 17:03:23.330 --> 17:03:23.340 align:start position:0% sticking it on your monitor 17:03:23.340 --> 17:03:25.370 align:start position:0% sticking it on your monitor so<17:03:23.820> we've<17:03:24.000> covered<17:03:24.360> Network<17:03:24.540> documentation 17:03:25.370 --> 17:03:25.380 align:start position:0% so we've covered Network documentation 17:03:25.380 --> 17:03:29.330 align:start position:0% so we've covered Network documentation why<17:03:26.040> the<17:03:26.456> importance<17:03:26.936> parts<17:03:27.900> of<17:03:28.140> it<17:03:28.340> diagrams 17:03:29.330 --> 17:03:29.340 align:start position:0% why the importance parts of it diagrams 17:03:29.340 --> 17:03:32.570 align:start position:0% why the importance parts of it diagrams Asset<17:03:29.880> Management<17:03:30.320> the<17:03:31.320> RFID 17:03:32.570 --> 17:03:32.580 align:start position:0% Asset Management the RFID 17:03:32.580 --> 17:03:35.390 align:start position:0% Asset Management the RFID and<17:03:33.060> monitoring<17:03:33.596> your<17:03:33.720> IP<17:03:33.956> addresses<17:03:34.500> vendors 17:03:35.390 --> 17:03:35.400 align:start position:0% and monitoring your IP addresses vendors 17:03:35.400 --> 17:03:37.426 align:start position:0% and monitoring your IP addresses vendors and<17:03:35.580> contractors<17:03:36.180> all<17:03:36.900> your<17:03:37.020> internal 17:03:37.426 --> 17:03:37.436 align:start position:0% and contractors all your internal 17:03:37.436 --> 17:03:39.230 align:start position:0% and contractors all your internal policies<17:03:37.916> and<17:03:38.160> procedures 17:03:39.230 --> 17:03:39.240 align:start position:0% policies and procedures 17:03:39.240 --> 17:03:41.266 align:start position:0% policies and procedures all<17:03:39.720> right<17:03:39.840> so<17:03:40.080> that's<17:03:40.256> all<17:03:40.680> for<17:03:40.860> now<17:03:41.040> thanks 17:03:41.266 --> 17:03:41.276 align:start position:0% all right so that's all for now thanks 17:03:41.276 --> 17:03:45.620 align:start position:0% all right so that's all for now thanks for<17:03:41.456> listening 17:03:45.620 --> 17:03:45.630 align:start position:0% 17:03:45.630 --> 17:04:01.490 align:start position:0% [Music] 17:04:01.490 --> 17:04:01.500 align:start position:0% 17:04:01.500 --> 17:04:04.266 align:start position:0% welcome<17:04:02.040> to<17:04:02.276> module<17:04:02.700> 11<17:04:02.820> lesson<17:04:03.416> 4<17:04:03.596> Network 17:04:04.266 --> 17:04:04.276 align:start position:0% welcome to module 11 lesson 4 Network 17:04:04.276 --> 17:04:06.650 align:start position:0% welcome to module 11 lesson 4 Network troubleshooting<17:04:05.276> model 17:04:06.650 --> 17:04:06.660 align:start position:0% troubleshooting model 17:04:06.660 --> 17:04:08.870 align:start position:0% troubleshooting model he'll<17:04:07.256> actually<17:04:07.500> develop<17:04:07.916> your<17:04:08.160> own<17:04:08.340> model<17:04:08.580> as 17:04:08.870 --> 17:04:08.880 align:start position:0% he'll actually develop your own model as 17:04:08.880 --> 17:04:11.266 align:start position:0% he'll actually develop your own model as you<17:04:09.060> get<17:04:09.240> some<17:04:09.480> experience<17:04:10.080> and<17:04:10.860> obviously 17:04:11.266 --> 17:04:11.276 align:start position:0% you get some experience and obviously 17:04:11.276 --> 17:04:14.390 align:start position:0% you get some experience and obviously depends<17:04:11.700> on<17:04:11.936> your<17:04:12.660> Network<17:04:13.380> whatever<17:04:13.860> your 17:04:14.390 --> 17:04:14.400 align:start position:0% depends on your Network whatever your 17:04:14.400 --> 17:04:16.070 align:start position:0% depends on your Network whatever your network<17:04:14.580> or<17:04:15.000> if<17:04:15.180> you're<17:04:15.296> managing<17:04:15.720> just<17:04:15.900> a 17:04:16.070 --> 17:04:16.080 align:start position:0% network or if you're managing just a 17:04:16.080 --> 17:04:18.350 align:start position:0% network or if you're managing just a small<17:04:16.200> part<17:04:16.436> of<17:04:16.616> the<17:04:16.740> network<17:04:17.000> and<17:04:18.000> if<17:04:18.240> you're 17:04:18.350 --> 17:04:18.360 align:start position:0% small part of the network and if you're 17:04:18.360 --> 17:04:21.230 align:start position:0% small part of the network and if you're managing<17:04:18.840> a<17:04:19.080> certain<17:04:19.456> OSI<17:04:20.456> layout<17:04:20.880> for 17:04:21.230 --> 17:04:21.240 align:start position:0% managing a certain OSI layout for 17:04:21.240 --> 17:04:23.570 align:start position:0% managing a certain OSI layout for example<17:04:21.416> firewalls<17:04:22.380> or<17:04:22.796> you're<17:04:23.220> a<17:04:23.400> hardware 17:04:23.570 --> 17:04:23.580 align:start position:0% example firewalls or you're a hardware 17:04:23.580 --> 17:04:25.730 align:start position:0% example firewalls or you're a hardware engineer<17:04:24.416> something<17:04:24.720> like<17:04:24.956> that<17:04:25.140> so<17:04:25.380> it<17:04:25.616> could 17:04:25.730 --> 17:04:25.740 align:start position:0% engineer something like that so it could 17:04:25.740 --> 17:04:28.970 align:start position:0% engineer something like that so it could vary<17:04:26.240> this<17:04:27.240> is<17:04:27.360> the<17:04:27.660> generic<17:04:28.140> kind<17:04:28.740> of<17:04:28.860> stuff 17:04:28.970 --> 17:04:28.980 align:start position:0% vary this is the generic kind of stuff 17:04:28.980 --> 17:04:31.426 align:start position:0% vary this is the generic kind of stuff that<17:04:29.220> CompTIA<17:04:29.756> want<17:04:30.000> you<17:04:30.180> to<17:04:30.360> know<17:04:31.200> and 17:04:31.426 --> 17:04:31.436 align:start position:0% that CompTIA want you to know and 17:04:31.436 --> 17:04:33.650 align:start position:0% that CompTIA want you to know and understand<17:04:31.616> and<17:04:31.980> follow<17:04:32.276> so<17:04:33.060> we'll<17:04:33.180> identify 17:04:33.650 --> 17:04:33.660 align:start position:0% understand and follow so we'll identify 17:04:33.660 --> 17:04:35.690 align:start position:0% understand and follow so we'll identify the<17:04:33.840> problem<17:04:34.096> establish<17:04:35.096> a<17:04:35.276> theory<17:04:35.580> of 17:04:35.690 --> 17:04:35.700 align:start position:0% the problem establish a theory of 17:04:35.700 --> 17:04:37.550 align:start position:0% the problem establish a theory of probable<17:04:36.060> cause 17:04:37.550 --> 17:04:37.560 align:start position:0% probable cause 17:04:37.560 --> 17:04:40.310 align:start position:0% probable cause normally<17:04:38.400> Whoever<17:04:38.820> has<17:04:39.540> just<17:04:39.776> made<17:04:39.956> a<17:04:40.140> change 17:04:40.310 --> 17:04:40.320 align:start position:0% normally Whoever has just made a change 17:04:40.320 --> 17:04:42.050 align:start position:0% normally Whoever has just made a change or<17:04:40.616> plugged<17:04:40.980> or<17:04:41.096> unplugged<17:04:41.640> something<17:04:41.756> has 17:04:42.050 --> 17:04:42.060 align:start position:0% or plugged or unplugged something has 17:04:42.060 --> 17:04:44.990 align:start position:0% or plugged or unplugged something has broken<17:04:42.296> it<17:04:42.596> in<17:04:43.200> my<17:04:43.380> experience 17:04:44.990 --> 17:04:45.000 align:start position:0% broken it in my experience 17:04:45.000 --> 17:04:46.850 align:start position:0% broken it in my experience test<17:04:45.480> the<17:04:45.720> theory<17:04:46.020> to<17:04:46.200> determine<17:04:46.500> the<17:04:46.680> cause 17:04:46.850 --> 17:04:46.860 align:start position:0% test the theory to determine the cause 17:04:46.860 --> 17:04:49.370 align:start position:0% test the theory to determine the cause establish<17:04:47.520> a<17:04:47.640> plan<17:04:47.820> of<17:04:48.000> action 17:04:49.370 --> 17:04:49.380 align:start position:0% establish a plan of action 17:04:49.380 --> 17:04:51.406 align:start position:0% establish a plan of action and<17:04:49.740> then<17:04:49.916> implement<17:04:50.276> the<17:04:50.456> solution<17:04:50.820> sort<17:04:51.240> of 17:04:51.406 --> 17:04:51.416 align:start position:0% and then implement the solution sort of 17:04:51.416 --> 17:04:53.690 align:start position:0% and then implement the solution sort of Common<17:04:51.540> Sense<17:04:51.840> stuff<17:04:52.080> really 17:04:53.690 --> 17:04:53.700 align:start position:0% Common Sense stuff really 17:04:53.700 --> 17:04:56.990 align:start position:0% Common Sense stuff really uh<17:04:54.180> verification<17:04:54.776> documentation 17:04:56.990 --> 17:04:57.000 align:start position:0% uh verification documentation 17:04:57.000 --> 17:04:58.426 align:start position:0% uh verification documentation all<17:04:57.416> right<17:04:57.540> so<17:04:57.720> we'll<17:04:57.900> normally<17:04:58.200> gather 17:04:58.426 --> 17:04:58.436 align:start position:0% all right so we'll normally gather 17:04:58.436 --> 17:05:00.230 align:start position:0% all right so we'll normally gather information 17:05:00.230 --> 17:05:00.240 align:start position:0% information 17:05:00.240 --> 17:05:02.870 align:start position:0% information duplicate<17:05:01.020> the<17:05:01.200> problem<17:05:01.380> if<17:05:01.680> possible<17:05:02.040> you'll 17:05:02.870 --> 17:05:02.880 align:start position:0% duplicate the problem if possible you'll 17:05:02.880 --> 17:05:04.850 align:start position:0% duplicate the problem if possible you'll normally<17:05:03.060> duplicate<17:05:03.660> it<17:05:03.840> if<17:05:04.140> it's<17:05:04.380> some<17:05:04.680> sort 17:05:04.850 --> 17:05:04.860 align:start position:0% normally duplicate it if it's some sort 17:05:04.860 --> 17:05:07.130 align:start position:0% normally duplicate it if it's some sort of<17:05:04.980> bug<17:05:05.276> and<17:05:05.700> you<17:05:05.880> want<17:05:06.060> to<17:05:06.180> recreate<17:05:06.840> it<17:05:06.956> so 17:05:07.130 --> 17:05:07.140 align:start position:0% of bug and you want to recreate it so 17:05:07.140 --> 17:05:10.010 align:start position:0% of bug and you want to recreate it so you<17:05:07.320> can<17:05:07.380> send<17:05:07.560> the<17:05:07.740> information<17:05:07.916> to<17:05:09.020> the 17:05:10.010 --> 17:05:10.020 align:start position:0% you can send the information to the 17:05:10.020 --> 17:05:14.210 align:start position:0% you can send the information to the vendor<17:05:10.560> to<17:05:11.456> release<17:05:11.700> some<17:05:12.060> sort<17:05:12.240> of<17:05:12.360> update 17:05:14.210 --> 17:05:14.220 align:start position:0% vendor to release some sort of update 17:05:14.220 --> 17:05:16.786 align:start position:0% vendor to release some sort of update uh<17:05:14.820> question<17:05:15.116> users<17:05:15.776> users<17:05:16.320> you've<17:05:16.560> got<17:05:16.616> to<17:05:16.740> be 17:05:16.786 --> 17:05:16.796 align:start position:0% uh question users users you've got to be 17:05:16.796 --> 17:05:18.230 align:start position:0% uh question users users you've got to be very<17:05:16.980> careful<17:05:17.276> obviously<17:05:17.700> because<17:05:17.820> they<17:05:18.060> can 17:05:18.230 --> 17:05:18.240 align:start position:0% very careful obviously because they can 17:05:18.240 --> 17:05:21.586 align:start position:0% very careful obviously because they can give<17:05:18.480> you<17:05:18.660> the<17:05:19.380> wrong<17:05:19.500> information<17:05:19.880> or<17:05:20.880> a<17:05:21.480> lot 17:05:21.586 --> 17:05:21.596 align:start position:0% give you the wrong information or a lot 17:05:21.596 --> 17:05:23.086 align:start position:0% give you the wrong information or a lot of<17:05:21.720> users<17:05:22.080> think<17:05:22.380> they<17:05:22.560> know<17:05:22.796> what<17:05:22.916> the 17:05:23.086 --> 17:05:23.096 align:start position:0% of users think they know what the 17:05:23.096 --> 17:05:24.586 align:start position:0% of users think they know what the solution<17:05:23.340> is<17:05:23.580> so<17:05:23.756> they'll<17:05:24.000> just<17:05:24.180> give<17:05:24.480> you 17:05:24.586 --> 17:05:24.596 align:start position:0% solution is so they'll just give you 17:05:24.596 --> 17:05:26.690 align:start position:0% solution is so they'll just give you answers<17:05:24.956> to<17:05:25.200> questions 17:05:26.690 --> 17:05:26.700 align:start position:0% answers to questions 17:05:26.700 --> 17:05:29.810 align:start position:0% answers to questions that<17:05:27.720> um<17:05:27.720> that<17:05:28.140> they<17:05:28.320> think<17:05:28.500> you<17:05:28.860> they<17:05:29.580> think 17:05:29.810 --> 17:05:29.820 align:start position:0% that um that they think you they think 17:05:29.820 --> 17:05:31.310 align:start position:0% that um that they think you they think will<17:05:30.000> direct<17:05:30.180> you<17:05:30.416> to<17:05:30.596> what<17:05:30.840> they<17:05:31.020> think<17:05:31.140> the 17:05:31.310 --> 17:05:31.320 align:start position:0% will direct you to what they think the 17:05:31.320 --> 17:05:33.890 align:start position:0% will direct you to what they think the issue<17:05:31.860> is<17:05:32.040> so<17:05:32.880> you'd<17:05:33.060> have<17:05:33.240> to<17:05:33.360> be<17:05:33.480> careful<17:05:33.720> and 17:05:33.890 --> 17:05:33.900 align:start position:0% issue is so you'd have to be careful and 17:05:33.900 --> 17:05:36.106 align:start position:0% issue is so you'd have to be careful and question<17:05:34.080> more<17:05:34.380> than<17:05:34.500> one<17:05:34.616> user<17:05:34.980> if<17:05:35.096> you<17:05:35.220> can 17:05:36.106 --> 17:05:36.116 align:start position:0% question more than one user if you can 17:05:36.116 --> 17:05:38.870 align:start position:0% question more than one user if you can identify<17:05:36.900> symptoms<17:05:37.520> determine<17:05:38.520> if<17:05:38.700> anything 17:05:38.870 --> 17:05:38.880 align:start position:0% identify symptoms determine if anything 17:05:38.880 --> 17:05:40.786 align:start position:0% identify symptoms determine if anything has<17:05:39.180> changed<17:05:39.596> normally<17:05:39.956> there<17:05:40.256> has<17:05:40.436> been<17:05:40.616> a 17:05:40.786 --> 17:05:40.796 align:start position:0% has changed normally there has been a 17:05:40.796 --> 17:05:43.606 align:start position:0% has changed normally there has been a change<17:05:40.980> almost<17:05:41.340> always<17:05:41.900> not<17:05:42.900> every<17:05:43.080> case<17:05:43.380> but 17:05:43.606 --> 17:05:43.616 align:start position:0% change almost always not every case but 17:05:43.616 --> 17:05:46.370 align:start position:0% change almost always not every case but almost<17:05:43.860> always<17:05:44.416> approach<17:05:45.416> multiple<17:05:45.956> problems 17:05:46.370 --> 17:05:46.380 align:start position:0% almost always approach multiple problems 17:05:46.380 --> 17:05:47.926 align:start position:0% almost always approach multiple problems individually 17:05:47.926 --> 17:05:47.936 align:start position:0% individually 17:05:47.936 --> 17:05:51.766 align:start position:0% individually so<17:05:48.416> dividing<17:05:48.900> conquer<17:05:49.320> kind<17:05:49.560> of<17:05:50.160> approach 17:05:51.766 --> 17:05:51.776 align:start position:0% so dividing conquer kind of approach 17:05:51.776 --> 17:05:54.050 align:start position:0% so dividing conquer kind of approach okay<17:05:52.380> question<17:05:52.796> the<17:05:53.096> obvious<17:05:53.400> it's<17:05:53.700> nearly 17:05:54.050 --> 17:05:54.060 align:start position:0% okay question the obvious it's nearly 17:05:54.060 --> 17:05:56.210 align:start position:0% okay question the obvious it's nearly always<17:05:54.240> something<17:05:54.596> that's<17:05:55.080> pretty<17:05:55.796> obvious 17:05:56.210 --> 17:05:56.220 align:start position:0% always something that's pretty obvious 17:05:56.220 --> 17:05:58.906 align:start position:0% always something that's pretty obvious I've<17:05:56.820> seen<17:05:57.540> people<17:05:57.776> waste<17:05:58.200> a<17:05:58.256> lot<17:05:58.380> of<17:05:58.500> time<17:05:58.680> and 17:05:58.906 --> 17:05:58.916 align:start position:0% I've seen people waste a lot of time and 17:05:58.916 --> 17:05:59.766 align:start position:0% I've seen people waste a lot of time and energy 17:05:59.766 --> 17:05:59.776 align:start position:0% energy 17:05:59.776 --> 17:06:02.330 align:start position:0% energy troubleshooting<17:06:00.776> less<17:06:01.320> likely<17:06:01.740> issues<17:06:02.160> when 17:06:02.330 --> 17:06:02.340 align:start position:0% troubleshooting less likely issues when 17:06:02.340 --> 17:06:04.786 align:start position:0% troubleshooting less likely issues when it's<17:06:02.640> almost<17:06:02.936> always<17:06:03.296> the<17:06:03.720> most<17:06:03.840> obvious 17:06:04.786 --> 17:06:04.796 align:start position:0% it's almost always the most obvious 17:06:04.796 --> 17:06:06.106 align:start position:0% it's almost always the most obvious thing<17:06:04.980> that's<17:06:05.160> wrong 17:06:06.106 --> 17:06:06.116 align:start position:0% thing that's wrong 17:06:06.116 --> 17:06:10.246 align:start position:0% thing that's wrong consider<17:06:06.776> multiple<17:06:07.200> approaches 17:06:10.246 --> 17:06:10.256 align:start position:0% 17:06:10.256 --> 17:06:12.710 align:start position:0% an<17:06:10.680> example<17:06:11.040> is<17:06:11.220> a<17:06:11.456> top<17:06:11.640> to<17:06:11.820> bottom<17:06:12.180> or<17:06:12.416> bottom 17:06:12.710 --> 17:06:12.720 align:start position:0% an example is a top to bottom or bottom 17:06:12.720 --> 17:06:14.810 align:start position:0% an example is a top to bottom or bottom to<17:06:12.776> top<17:06:12.956> using<17:06:13.320> the<17:06:13.436> OSI<17:06:13.916> is<17:06:14.520> it<17:06:14.700> an 17:06:14.810 --> 17:06:14.820 align:start position:0% to top using the OSI is it an 17:06:14.820 --> 17:06:16.730 align:start position:0% to top using the OSI is it an application<17:06:15.240> problem<17:06:15.596> and<17:06:15.900> then<17:06:16.080> moving<17:06:16.436> down 17:06:16.730 --> 17:06:16.740 align:start position:0% application problem and then moving down 17:06:16.740 --> 17:06:18.890 align:start position:0% application problem and then moving down or<17:06:17.220> is<17:06:17.340> it<17:06:17.520> a<17:06:17.640> physical<17:06:17.756> problem<17:06:18.180> moving<17:06:18.720> up 17:06:18.890 --> 17:06:18.900 align:start position:0% or is it a physical problem moving up 17:06:18.900 --> 17:06:20.690 align:start position:0% or is it a physical problem moving up and<17:06:19.380> it<17:06:19.500> depends<17:06:19.796> on<17:06:19.916> what<17:06:20.096> the<17:06:20.220> users<17:06:20.520> are 17:06:20.690 --> 17:06:20.700 align:start position:0% and it depends on what the users are 17:06:20.700 --> 17:06:22.130 align:start position:0% and it depends on what the users are telling<17:06:21.000> you<17:06:21.060> and<17:06:21.240> what<17:06:21.416> the<17:06:21.540> symptoms<17:06:21.720> are 17:06:22.130 --> 17:06:22.140 align:start position:0% telling you and what the symptoms are 17:06:22.140 --> 17:06:23.210 align:start position:0% telling you and what the symptoms are obviously 17:06:23.210 --> 17:06:23.220 align:start position:0% obviously 17:06:23.220 --> 17:06:25.670 align:start position:0% obviously I<17:06:23.700> mentioned<17:06:24.000> divide<17:06:24.360> and<17:06:24.480> conquer 17:06:25.670 --> 17:06:25.680 align:start position:0% I mentioned divide and conquer 17:06:25.680 --> 17:06:28.246 align:start position:0% I mentioned divide and conquer and<17:06:26.580> this<17:06:27.000> all<17:06:27.116> depends<17:06:27.660> on<17:06:27.840> your<17:06:28.020> network 17:06:28.246 --> 17:06:28.256 align:start position:0% and this all depends on your network 17:06:28.256 --> 17:06:30.530 align:start position:0% and this all depends on your network really<17:06:28.680> but<17:06:29.096> it<17:06:29.340> could<17:06:29.456> be<17:06:29.820> um<17:06:29.820> dividing<17:06:30.360> it 17:06:30.530 --> 17:06:30.540 align:start position:0% really but it could be um dividing it 17:06:30.540 --> 17:06:34.850 align:start position:0% really but it could be um dividing it into<17:06:30.720> Hardware<17:06:31.140> all<17:06:31.680> Hardware<17:06:32.480> or<17:06:33.480> and<17:06:34.020> all 17:06:34.850 --> 17:06:34.860 align:start position:0% into Hardware all Hardware or and all 17:06:34.860 --> 17:06:38.266 align:start position:0% into Hardware all Hardware or and all layer<17:06:35.340> 7<17:06:35.720> issues<17:06:36.720> or<17:06:37.080> all<17:06:37.436> cabling<17:06:37.860> issues 17:06:38.266 --> 17:06:38.276 align:start position:0% layer 7 issues or all cabling issues 17:06:38.276 --> 17:06:40.370 align:start position:0% layer 7 issues or all cabling issues something<17:06:38.456> like<17:06:38.820> that<17:06:39.000> it<17:06:39.540> just<17:06:39.660> depends<17:06:40.080> all 17:06:40.370 --> 17:06:40.380 align:start position:0% something like that it just depends all 17:06:40.380 --> 17:06:41.810 align:start position:0% something like that it just depends all the<17:06:40.740> Divine<17:06:41.040> and<17:06:41.220> concrete<17:06:41.580> could<17:06:41.700> be 17:06:41.810 --> 17:06:41.820 align:start position:0% the Divine and concrete could be 17:06:41.820 --> 17:06:44.210 align:start position:0% the Divine and concrete could be segments<17:06:42.296> in<17:06:42.416> your<17:06:42.540> network<17:06:42.776> so<17:06:43.500> looking<17:06:43.680> if<17:06:43.980> a 17:06:44.210 --> 17:06:44.220 align:start position:0% segments in your network so looking if a 17:06:44.220 --> 17:06:45.946 align:start position:0% segments in your network so looking if a particular<17:06:44.400> vlans<17:06:44.936> affected 17:06:45.946 --> 17:06:45.956 align:start position:0% particular vlans affected 17:06:45.956 --> 17:06:49.446 align:start position:0% particular vlans affected or<17:06:46.380> all<17:06:46.500> vlans<17:06:47.040> test<17:06:48.000> the<17:06:48.180> theory<17:06:48.540> once<17:06:49.020> it's 17:06:49.446 --> 17:06:49.456 align:start position:0% or all vlans test the theory once it's 17:06:49.456 --> 17:06:52.130 align:start position:0% or all vlans test the theory once it's confirmed<17:06:50.456> and<17:06:50.880> determine<17:06:51.480> the<17:06:51.596> next<17:06:51.776> steps 17:06:52.130 --> 17:06:52.140 align:start position:0% confirmed and determine the next steps 17:06:52.140 --> 17:06:54.170 align:start position:0% confirmed and determine the next steps to<17:06:52.256> resolve<17:06:52.616> the<17:06:52.680> problem<17:06:52.860> for<17:06:53.756> example<17:06:53.936> if 17:06:54.170 --> 17:06:54.180 align:start position:0% to resolve the problem for example if 17:06:54.180 --> 17:06:56.746 align:start position:0% to resolve the problem for example if it's<17:06:54.360> an<17:06:54.596> email<17:06:54.720> issue<17:06:55.200> then<17:06:55.500> try<17:06:56.160> sending<17:06:56.580> an 17:06:56.746 --> 17:06:56.756 align:start position:0% it's an email issue then try sending an 17:06:56.756 --> 17:06:59.926 align:start position:0% it's an email issue then try sending an email<17:06:56.936> try<17:06:57.360> it<17:06:57.540> from<17:06:57.660> a<17:06:57.900> different<17:06:58.020> users 17:06:59.926 --> 17:06:59.936 align:start position:0% email try it from a different users 17:06:59.936 --> 17:07:01.550 align:start position:0% email try it from a different users um device<17:07:00.416> to<17:07:00.776> see<17:07:00.956> if<17:07:01.140> there's<17:07:01.256> more<17:07:01.436> than 17:07:01.550 --> 17:07:01.560 align:start position:0% um device to see if there's more than 17:07:01.560 --> 17:07:04.130 align:start position:0% um device to see if there's more than one<17:07:01.740> person<17:07:01.860> affected<17:07:02.456> if<17:07:03.416> the<17:07:03.540> theory<17:07:03.840> is<17:07:03.956> not 17:07:04.130 --> 17:07:04.140 align:start position:0% one person affected if the theory is not 17:07:04.140 --> 17:07:06.650 align:start position:0% one person affected if the theory is not confirmed<17:07:04.616> you<17:07:04.796> start<17:07:05.040> at<17:07:05.160> the<17:07:05.276> beginning 17:07:06.650 --> 17:07:06.660 align:start position:0% confirmed you start at the beginning 17:07:06.660 --> 17:07:09.946 align:start position:0% confirmed you start at the beginning plan<17:07:07.200> of<17:07:07.500> action<17:07:07.796> obviously<17:07:08.700> and<17:07:09.540> if<17:07:09.720> you<17:07:09.840> can 17:07:09.946 --> 17:07:09.956 align:start position:0% plan of action obviously and if you can 17:07:09.956 --> 17:07:11.746 align:start position:0% plan of action obviously and if you can fix<17:07:10.140> it<17:07:10.320> there<17:07:10.500> and<17:07:10.680> then<17:07:10.860> fix<17:07:11.160> it<17:07:11.400> if<17:07:11.580> it's 17:07:11.746 --> 17:07:11.756 align:start position:0% fix it there and then fix it if it's 17:07:11.756 --> 17:07:14.446 align:start position:0% fix it there and then fix it if it's requiring<17:07:12.240> a<17:07:12.480> network<17:07:12.776> downtime<17:07:13.560> then<17:07:14.220> you're 17:07:14.446 --> 17:07:14.456 align:start position:0% requiring a network downtime then you're 17:07:14.456 --> 17:07:16.130 align:start position:0% requiring a network downtime then you're going<17:07:14.700> to<17:07:14.820> need<17:07:14.880> to<17:07:15.060> schedule<17:07:15.240> an<17:07:15.540> outage<17:07:15.900> if 17:07:16.130 --> 17:07:16.140 align:start position:0% going to need to schedule an outage if 17:07:16.140 --> 17:07:17.710 align:start position:0% going to need to schedule an outage if you're<17:07:16.256> working<17:07:16.380> on<17:07:16.680> a<17:07:16.796> production<17:07:17.096> Network 17:07:17.710 --> 17:07:17.720 align:start position:0% you're working on a production Network 17:07:17.720 --> 17:07:20.810 align:start position:0% you're working on a production Network again<17:07:18.796> and<17:07:19.796> generally<17:07:20.096> this<17:07:20.276> sort<17:07:20.456> of<17:07:20.520> issue 17:07:20.810 --> 17:07:20.820 align:start position:0% again and generally this sort of issue 17:07:20.820 --> 17:07:23.630 align:start position:0% again and generally this sort of issue is<17:07:20.936> decided<17:07:21.416> by<17:07:21.596> this<17:07:22.320> seniority<17:07:22.916> manager<17:07:23.456> or 17:07:23.630 --> 17:07:23.640 align:start position:0% is decided by this seniority manager or 17:07:23.640 --> 17:07:25.730 align:start position:0% is decided by this seniority manager or network<17:07:23.820> manager 17:07:25.730 --> 17:07:25.740 align:start position:0% network manager 17:07:25.740 --> 17:07:27.230 align:start position:0% network manager potential<17:07:26.220> effects<17:07:26.700> what's<17:07:26.820> going<17:07:27.060> to<17:07:27.116> happen 17:07:27.230 --> 17:07:27.240 align:start position:0% potential effects what's going to happen 17:07:27.240 --> 17:07:28.786 align:start position:0% potential effects what's going to happen is<17:07:27.540> it<17:07:27.660> going<17:07:27.776> to<17:07:27.956> cause<17:07:28.140> make<17:07:28.436> the<17:07:28.616> problem 17:07:28.786 --> 17:07:28.796 align:start position:0% is it going to cause make the problem 17:07:28.796 --> 17:07:30.530 align:start position:0% is it going to cause make the problem worse<17:07:29.276> is<17:07:29.400> it<17:07:29.580> going<17:07:29.700> to<17:07:29.820> fix<17:07:29.936> it<17:07:30.116> is<17:07:30.296> it<17:07:30.480> going 17:07:30.530 --> 17:07:30.540 align:start position:0% worse is it going to fix it is it going 17:07:30.540 --> 17:07:32.030 align:start position:0% worse is it going to fix it is it going to<17:07:30.660> cause<17:07:30.776> a<17:07:30.956> different<17:07:31.140> problem<17:07:31.436> somewhere 17:07:32.030 --> 17:07:32.040 align:start position:0% to cause a different problem somewhere 17:07:32.040 --> 17:07:33.170 align:start position:0% to cause a different problem somewhere else 17:07:33.170 --> 17:07:33.180 align:start position:0% else 17:07:33.180 --> 17:07:35.390 align:start position:0% else when<17:07:33.596> you<17:07:33.720> implement<17:07:34.020> the<17:07:34.256> solution<17:07:34.616> escalate 17:07:35.390 --> 17:07:35.400 align:start position:0% when you implement the solution escalate 17:07:35.400 --> 17:07:38.050 align:start position:0% when you implement the solution escalate is<17:07:35.580> necessary<17:07:36.140> again<17:07:37.140> you<17:07:37.380> normally<17:07:37.616> need 17:07:38.050 --> 17:07:38.060 align:start position:0% is necessary again you normally need 17:07:38.060 --> 17:07:40.970 align:start position:0% is necessary again you normally need verification<17:07:39.060> of<17:07:39.360> somebody<17:07:39.596> else<17:07:40.436> a<17:07:40.680> senior 17:07:40.970 --> 17:07:40.980 align:start position:0% verification of somebody else a senior 17:07:40.980 --> 17:07:43.246 align:start position:0% verification of somebody else a senior manager<17:07:41.400> that<17:07:41.936> this<17:07:42.180> is<17:07:42.660> um 17:07:43.246 --> 17:07:43.256 align:start position:0% manager that this is um 17:07:43.256 --> 17:07:45.946 align:start position:0% manager that this is um the<17:07:43.680> correct<17:07:43.916> course<17:07:44.160> of<17:07:44.340> action 17:07:45.946 --> 17:07:45.956 align:start position:0% the correct course of action 17:07:45.956 --> 17:07:49.130 align:start position:0% the correct course of action verifiable<17:07:46.916> system<17:07:47.340> functionality 17:07:49.130 --> 17:07:49.140 align:start position:0% verifiable system functionality 17:07:49.140 --> 17:07:51.286 align:start position:0% verifiable system functionality speak<17:07:49.796> to<17:07:49.980> the<17:07:50.160> user<17:07:50.520> who<17:07:50.700> actually<17:07:50.880> logged 17:07:51.286 --> 17:07:51.296 align:start position:0% speak to the user who actually logged 17:07:51.296 --> 17:07:53.330 align:start position:0% speak to the user who actually logged the<17:07:51.416> issue<17:07:51.720> and<17:07:52.140> see<17:07:52.560> if<17:07:52.680> it's<17:07:52.796> resolved<17:07:53.220> for 17:07:53.330 --> 17:07:53.340 align:start position:0% the issue and see if it's resolved for 17:07:53.340 --> 17:07:55.010 align:start position:0% the issue and see if it's resolved for them<17:07:53.456> and<17:07:53.756> whoever<17:07:54.180> else<17:07:54.360> was<17:07:54.540> experiencing 17:07:55.010 --> 17:07:55.020 align:start position:0% them and whoever else was experiencing 17:07:55.020 --> 17:07:57.830 align:start position:0% them and whoever else was experiencing it<17:07:55.740> if<17:07:56.096> applicable<17:07:56.640> Implement<17:07:57.180> preventative 17:07:57.830 --> 17:07:57.840 align:start position:0% it if applicable Implement preventative 17:07:57.840 --> 17:08:01.606 align:start position:0% it if applicable Implement preventative measures<17:07:58.700> document<17:07:59.700> the<17:08:00.000> outcomes<17:08:00.616> findings 17:08:01.606 --> 17:08:01.616 align:start position:0% measures document the outcomes findings 17:08:01.616 --> 17:08:04.070 align:start position:0% measures document the outcomes findings and<17:08:02.276> actions 17:08:04.070 --> 17:08:04.080 align:start position:0% and actions 17:08:04.080 --> 17:08:05.810 align:start position:0% and actions this<17:08:04.560> is<17:08:04.680> basically<17:08:04.980> useful<17:08:05.340> if<17:08:05.580> somebody 17:08:05.810 --> 17:08:05.820 align:start position:0% this is basically useful if somebody 17:08:05.820 --> 17:08:08.746 align:start position:0% this is basically useful if somebody else<17:08:06.240> deals<17:08:07.080> with<17:08:07.140> the<17:08:07.320> same<17:08:07.500> problem<17:08:07.740> I<17:08:08.580> know 17:08:08.746 --> 17:08:08.756 align:start position:0% else deals with the same problem I know 17:08:08.756 --> 17:08:10.426 align:start position:0% else deals with the same problem I know when<17:08:08.936> I<17:08:09.116> worked<17:08:09.360> at<17:08:09.416> Cisco<17:08:09.776> attack<17:08:09.956> you<17:08:10.380> could 17:08:10.426 --> 17:08:10.436 align:start position:0% when I worked at Cisco attack you could 17:08:10.436 --> 17:08:11.630 align:start position:0% when I worked at Cisco attack you could often<17:08:10.680> put<17:08:10.916> in 17:08:11.630 --> 17:08:11.640 align:start position:0% often put in 17:08:11.640 --> 17:08:14.870 align:start position:0% often put in error<17:08:12.416> messages<17:08:12.596> and<17:08:13.560> similar<17:08:14.400> things<17:08:14.640> or 17:08:14.870 --> 17:08:14.880 align:start position:0% error messages and similar things or 17:08:14.880 --> 17:08:16.786 align:start position:0% error messages and similar things or look<17:08:15.060> at<17:08:15.180> certain<17:08:15.360> model<17:08:15.596> numbers<17:08:15.956> and<17:08:16.616> you'd 17:08:16.786 --> 17:08:16.796 align:start position:0% look at certain model numbers and you'd 17:08:16.796 --> 17:08:18.286 align:start position:0% look at certain model numbers and you'd often<17:08:17.040> find<17:08:17.340> somebody<17:08:17.580> else<17:08:17.820> that<17:08:17.936> had<17:08:18.180> the 17:08:18.286 --> 17:08:18.296 align:start position:0% often find somebody else that had the 17:08:18.296 --> 17:08:20.746 align:start position:0% often find somebody else that had the same<17:08:18.480> problem<17:08:18.916> and<17:08:19.916> you<17:08:20.096> could<17:08:20.220> see<17:08:20.400> how<17:08:20.580> they 17:08:20.746 --> 17:08:20.756 align:start position:0% same problem and you could see how they 17:08:20.756 --> 17:08:22.426 align:start position:0% same problem and you could see how they fixed<17:08:21.116> it<17:08:21.240> or<17:08:21.416> if<17:08:21.540> they'd<17:08:21.776> established<17:08:22.140> that<17:08:22.256> a 17:08:22.426 --> 17:08:22.436 align:start position:0% fixed it or if they'd established that a 17:08:22.436 --> 17:08:24.530 align:start position:0% fixed it or if they'd established that a bug<17:08:22.680> had<17:08:23.520> been<17:08:23.700> found<17:08:23.880> and<17:08:24.116> then<17:08:24.240> if<17:08:24.416> that 17:08:24.530 --> 17:08:24.540 align:start position:0% bug had been found and then if that 17:08:24.540 --> 17:08:27.766 align:start position:0% bug had been found and then if that bug's<17:08:24.840> been<17:08:24.956> fixed<17:08:25.436> in<17:08:25.616> another<17:08:26.040> iOS 17:08:27.766 --> 17:08:27.776 align:start position:0% bug's been fixed in another iOS 17:08:27.776 --> 17:08:29.746 align:start position:0% bug's been fixed in another iOS all<17:08:28.320> right<17:08:28.500> so<17:08:28.680> pretty<17:08:28.980> Common<17:08:29.220> Sense<17:08:29.456> stuff 17:08:29.746 --> 17:08:29.756 align:start position:0% all right so pretty Common Sense stuff 17:08:29.756 --> 17:08:32.266 align:start position:0% all right so pretty Common Sense stuff hopefully<17:08:30.180> but<17:08:30.540> we've<17:08:30.840> put<17:08:31.080> it<17:08:31.200> into<17:08:31.436> writing 17:08:32.266 --> 17:08:32.276 align:start position:0% hopefully but we've put it into writing 17:08:32.276 --> 17:08:34.070 align:start position:0% hopefully but we've put it into writing now<17:08:32.400> so<17:08:32.640> you've<17:08:32.820> got<17:08:33.000> uh<17:08:33.296> some<17:08:33.540> sort<17:08:33.660> of<17:08:33.776> method 17:08:34.070 --> 17:08:34.080 align:start position:0% now so you've got uh some sort of method 17:08:34.080 --> 17:08:36.710 align:start position:0% now so you've got uh some sort of method to<17:08:34.256> follow<17:08:34.580> I'd<17:08:35.580> identify<17:08:36.416> the<17:08:36.596> problem 17:08:36.710 --> 17:08:36.720 align:start position:0% to follow I'd identify the problem 17:08:36.720 --> 17:08:39.586 align:start position:0% to follow I'd identify the problem establish<17:08:37.380> your<17:08:37.560> theory<17:08:37.916> test<17:08:38.276> it<17:08:38.520> plan<17:08:39.296> of 17:08:39.586 --> 17:08:39.596 align:start position:0% establish your theory test it plan of 17:08:39.596 --> 17:08:42.830 align:start position:0% establish your theory test it plan of action<17:08:40.096> implement<17:08:41.096> the<17:08:41.276> solution<17:08:41.840> verify 17:08:42.830 --> 17:08:42.840 align:start position:0% action implement the solution verify 17:08:42.840 --> 17:08:46.070 align:start position:0% action implement the solution verify document<17:08:44.000> you<17:08:45.000> need<17:08:45.240> to<17:08:45.360> write<17:08:45.480> that<17:08:45.660> down<17:08:45.840> a 17:08:46.070 --> 17:08:46.080 align:start position:0% document you need to write that down a 17:08:46.080 --> 17:08:47.570 align:start position:0% document you need to write that down a few<17:08:46.200> times<17:08:46.320> you<17:08:46.560> get<17:08:46.680> the<17:08:46.796> correct<17:08:46.980> order<17:08:47.220> in 17:08:47.570 --> 17:08:47.580 align:start position:0% few times you get the correct order in 17:08:47.580 --> 17:08:49.730 align:start position:0% few times you get the correct order in case<17:08:47.700> it's<17:08:47.880> a<17:08:48.180> drag<17:08:48.776> and<17:08:48.956> drop<17:08:49.080> type<17:08:49.380> question 17:08:49.730 --> 17:08:49.740 align:start position:0% case it's a drag and drop type question 17:08:49.740 --> 17:08:52.190 align:start position:0% case it's a drag and drop type question all<17:08:50.700> right<17:08:50.880> so<17:08:51.060> that's<17:08:51.240> the<17:08:51.416> end<17:08:51.596> thanks<17:08:51.956> for 17:08:52.190 --> 17:08:52.200 align:start position:0% all right so that's the end thanks for 17:08:52.200 --> 17:08:59.020 align:start position:0% all right so that's the end thanks for listening 17:08:59.020 --> 17:08:59.030 align:start position:0% 17:08:59.030 --> 17:09:07.746 align:start position:0% [Music] 17:09:07.746 --> 17:09:07.756 align:start position:0% [Music] 17:09:07.756 --> 17:09:18.230 align:start position:0% [Music] thank<17:09:08.756> you 17:09:18.230 --> 17:09:18.240 align:start position:0% 17:09:18.240 --> 17:09:19.606 align:start position:0% foreign 17:09:19.606 --> 17:09:19.616 align:start position:0% foreign 17:09:19.616 --> 17:09:24.170 align:start position:0% foreign network<17:09:20.400> security<17:09:21.020> security<17:09:22.020> fundamentals 17:09:24.170 --> 17:09:24.180 align:start position:0% network security security fundamentals 17:09:24.180 --> 17:09:26.810 align:start position:0% network security security fundamentals in<17:09:24.660> the<17:09:24.776> last<17:09:24.900> lesson<17:09:25.256> we<17:09:25.500> discussed<17:09:26.220> managing 17:09:26.810 --> 17:09:26.820 align:start position:0% in the last lesson we discussed managing 17:09:26.820 --> 17:09:28.490 align:start position:0% in the last lesson we discussed managing a<17:09:27.060> network<17:09:27.240> and<17:09:27.540> administering<17:09:28.140> a<17:09:28.256> network 17:09:28.490 --> 17:09:28.500 align:start position:0% a network and administering a network 17:09:28.500 --> 17:09:30.170 align:start position:0% a network and administering a network this<17:09:29.220> ranged<17:09:29.580> everywhere<17:09:29.880> from 17:09:30.170 --> 17:09:30.180 align:start position:0% this ranged everywhere from 17:09:30.180 --> 17:09:32.390 align:start position:0% this ranged everywhere from troubleshooting<17:09:30.900> to<17:09:31.320> speed<17:09:31.616> optimization 17:09:32.390 --> 17:09:32.400 align:start position:0% troubleshooting to speed optimization 17:09:32.400 --> 17:09:35.086 align:start position:0% troubleshooting to speed optimization and<17:09:33.296> in<17:09:33.596> this<17:09:33.720> lesson<17:09:34.140> in<17:09:34.560> the<17:09:34.740> next<17:09:34.860> four 17:09:35.086 --> 17:09:35.096 align:start position:0% and in this lesson in the next four 17:09:35.096 --> 17:09:36.890 align:start position:0% and in this lesson in the next four modules<17:09:35.580> we're<17:09:35.820> going<17:09:35.936> to<17:09:36.116> discuss<17:09:36.416> security 17:09:36.890 --> 17:09:36.900 align:start position:0% modules we're going to discuss security 17:09:36.900 --> 17:09:39.766 align:start position:0% modules we're going to discuss security now<17:09:37.860> just<17:09:38.160> like<17:09:38.340> with<17:09:38.700> a<17:09:38.880> plus<17:09:39.116> we<17:09:39.540> talked 17:09:39.766 --> 17:09:39.776 align:start position:0% now just like with a plus we talked 17:09:39.776 --> 17:09:43.246 align:start position:0% now just like with a plus we talked about<17:09:39.840> networking<17:09:40.680> and<17:09:41.400> Security<17:09:42.020> in<17:09:43.020> network 17:09:43.246 --> 17:09:43.256 align:start position:0% about networking and Security in network 17:09:43.256 --> 17:09:45.426 align:start position:0% about networking and Security in network plus<17:09:43.560> we're<17:09:43.916> going<17:09:44.040> to<17:09:44.160> talk<17:09:44.340> about<17:09:44.580> security 17:09:45.426 --> 17:09:45.436 align:start position:0% plus we're going to talk about security 17:09:45.436 --> 17:09:48.530 align:start position:0% plus we're going to talk about security with<17:09:46.436> the<17:09:46.680> understanding<17:09:47.400> that<17:09:47.936> there<17:09:48.180> is<17:09:48.360> a 17:09:48.530 --> 17:09:48.540 align:start position:0% with the understanding that there is a 17:09:48.540 --> 17:09:50.030 align:start position:0% with the understanding that there is a whole<17:09:48.660> other<17:09:48.840> certification<17:09:49.500> and<17:09:49.796> a<17:09:49.980> whole 17:09:50.030 --> 17:09:50.040 align:start position:0% whole other certification and a whole 17:09:50.040 --> 17:09:52.246 align:start position:0% whole other certification and a whole other<17:09:50.220> lesson<17:09:50.700> that<17:09:51.116> revolves<17:09:51.596> specifically 17:09:52.246 --> 17:09:52.256 align:start position:0% other lesson that revolves specifically 17:09:52.256 --> 17:09:56.086 align:start position:0% other lesson that revolves specifically around<17:09:52.880> this<17:09:53.880> uh<17:09:54.360> concept<17:09:54.840> so<17:09:55.616> we're<17:09:55.916> just 17:09:56.086 --> 17:09:56.096 align:start position:0% around this uh concept so we're just 17:09:56.096 --> 17:09:57.470 align:start position:0% around this uh concept so we're just going<17:09:56.276> to<17:09:56.400> sort<17:09:56.580> of<17:09:56.700> brush<17:09:57.060> over<17:09:57.240> the 17:09:57.470 --> 17:09:57.480 align:start position:0% going to sort of brush over the 17:09:57.480 --> 17:09:59.990 align:start position:0% going to sort of brush over the important<17:09:57.840> things<17:09:58.020> that<17:09:58.320> we<17:09:58.500> need<17:09:58.616> to<17:09:58.796> know<17:09:59.000> in 17:09:59.990 --> 17:10:00.000 align:start position:0% important things that we need to know in 17:10:00.000 --> 17:10:02.030 align:start position:0% important things that we need to know in a<17:10:00.296> network<17:10:00.416> Plus<17:10:00.776> or<17:10:01.080> network<17:10:01.380> Administration 17:10:02.030 --> 17:10:02.040 align:start position:0% a network Plus or network Administration 17:10:02.040 --> 17:10:04.970 align:start position:0% a network Plus or network Administration environment<17:10:02.776> so<17:10:03.776> to<17:10:04.140> start<17:10:04.320> us<17:10:04.500> off<17:10:04.680> we're 17:10:04.970 --> 17:10:04.980 align:start position:0% environment so to start us off we're 17:10:04.980 --> 17:10:07.190 align:start position:0% environment so to start us off we're going<17:10:05.160> to<17:10:05.276> talk<17:10:05.456> about<17:10:05.700> the<17:10:06.360> basis<17:10:06.776> of<17:10:07.020> network 17:10:07.190 --> 17:10:07.200 align:start position:0% going to talk about the basis of network 17:10:07.200 --> 17:10:09.170 align:start position:0% going to talk about the basis of network security<17:10:07.560> and<17:10:07.916> the<17:10:08.096> fundamentals<17:10:08.700> that<17:10:09.060> we're 17:10:09.170 --> 17:10:09.180 align:start position:0% security and the fundamentals that we're 17:10:09.180 --> 17:10:10.370 align:start position:0% security and the fundamentals that we're going<17:10:09.296> to<17:10:09.360> discuss<17:10:09.540> in<17:10:09.776> the<17:10:09.900> next<17:10:10.020> three 17:10:10.370 --> 17:10:10.380 align:start position:0% going to discuss in the next three 17:10:10.380 --> 17:10:11.510 align:start position:0% going to discuss in the next three modules 17:10:11.510 --> 17:10:11.520 align:start position:0% modules 17:10:11.520 --> 17:10:13.670 align:start position:0% modules so<17:10:12.116> this<17:10:12.416> involves<17:10:12.840> discussing<17:10:13.380> network 17:10:13.670 --> 17:10:13.680 align:start position:0% so this involves discussing network 17:10:13.680 --> 17:10:15.890 align:start position:0% so this involves discussing network security<17:10:14.040> and<17:10:14.456> identifying<17:10:15.116> exactly<17:10:15.540> what<17:10:15.776> it 17:10:15.890 --> 17:10:15.900 align:start position:0% security and identifying exactly what it 17:10:15.900 --> 17:10:18.230 align:start position:0% security and identifying exactly what it is<17:10:16.080> when<17:10:16.500> we<17:10:16.680> talk<17:10:16.796> about<17:10:16.916> the<17:10:17.220> basics<17:10:17.580> then 17:10:18.230 --> 17:10:18.240 align:start position:0% is when we talk about the basics then 17:10:18.240 --> 17:10:19.246 align:start position:0% is when we talk about the basics then we're<17:10:18.416> going<17:10:18.540> to<17:10:18.596> go<17:10:18.720> over<17:10:18.840> some<17:10:19.080> of<17:10:19.200> the 17:10:19.246 --> 17:10:19.256 align:start position:0% we're going to go over some of the 17:10:19.256 --> 17:10:21.406 align:start position:0% we're going to go over some of the things<17:10:19.436> that<17:10:19.740> are<17:10:19.860> fundamental<17:10:20.456> to<17:10:20.756> having<17:10:21.060> a 17:10:21.406 --> 17:10:21.416 align:start position:0% things that are fundamental to having a 17:10:21.416 --> 17:10:23.746 align:start position:0% things that are fundamental to having a secure<17:10:21.660> network<17:10:21.900> these<17:10:22.740> include<17:10:23.040> keeping<17:10:23.640> the 17:10:23.746 --> 17:10:23.756 align:start position:0% secure network these include keeping the 17:10:23.756 --> 17:10:25.670 align:start position:0% secure network these include keeping the network<17:10:23.880> up<17:10:24.240> to<17:10:24.360> date 17:10:25.670 --> 17:10:25.680 align:start position:0% network up to date 17:10:25.680 --> 17:10:27.890 align:start position:0% network up to date strong<17:10:26.340> passwords 17:10:27.890 --> 17:10:27.900 align:start position:0% strong passwords 17:10:27.900 --> 17:10:30.530 align:start position:0% strong passwords having<17:10:28.380> a<17:10:28.740> secure<17:10:29.096> VPN<17:10:29.700> virtual<17:10:30.180> private 17:10:30.530 --> 17:10:30.540 align:start position:0% having a secure VPN virtual private 17:10:30.540 --> 17:10:31.926 align:start position:0% having a secure VPN virtual private Network 17:10:31.926 --> 17:10:31.936 align:start position:0% Network 17:10:31.936 --> 17:10:35.150 align:start position:0% Network administrating<17:10:33.020> user<17:10:34.020> access<17:10:34.200> in<17:10:34.740> a<17:10:34.860> proper 17:10:35.150 --> 17:10:35.160 align:start position:0% administrating user access in a proper 17:10:35.160 --> 17:10:36.230 align:start position:0% administrating user access in a proper way 17:10:36.230 --> 17:10:36.240 align:start position:0% way 17:10:36.240 --> 17:10:39.106 align:start position:0% way and<17:10:36.900> making<17:10:37.380> sure<17:10:37.616> to<17:10:37.796> remove<17:10:37.980> any<17:10:38.580> inactive 17:10:39.106 --> 17:10:39.116 align:start position:0% and making sure to remove any inactive 17:10:39.116 --> 17:10:41.330 align:start position:0% and making sure to remove any inactive accounts<17:10:39.596> now<17:10:40.200> the<17:10:40.320> reason<17:10:40.500> I<17:10:40.680> focus<17:10:40.916> on<17:10:41.096> these 17:10:41.330 --> 17:10:41.340 align:start position:0% accounts now the reason I focus on these 17:10:41.340 --> 17:10:42.586 align:start position:0% accounts now the reason I focus on these fundamentals<17:10:41.880> are<17:10:42.000> these<17:10:42.180> are<17:10:42.296> the<17:10:42.416> things 17:10:42.586 --> 17:10:42.596 align:start position:0% fundamentals are these are the things 17:10:42.596 --> 17:10:45.406 align:start position:0% fundamentals are these are the things that<17:10:42.900> we'll<17:10:43.020> see<17:10:43.256> on<17:10:43.500> the<17:10:43.616> network<17:10:43.740> plus<17:10:44.040> exam 17:10:45.406 --> 17:10:45.416 align:start position:0% that we'll see on the network plus exam 17:10:45.416 --> 17:10:47.870 align:start position:0% that we'll see on the network plus exam now<17:10:45.956> the<17:10:46.320> word<17:10:46.436> security<17:10:46.796> means<17:10:47.520> the<17:10:47.756> same 17:10:47.870 --> 17:10:47.880 align:start position:0% now the word security means the same 17:10:47.880 --> 17:10:49.850 align:start position:0% now the word security means the same thing<17:10:48.060> just<17:10:48.296> about<17:10:48.480> anywhere<17:10:48.956> you<17:10:49.140> look<17:10:49.380> when 17:10:49.850 --> 17:10:49.860 align:start position:0% thing just about anywhere you look when 17:10:49.860 --> 17:10:52.190 align:start position:0% thing just about anywhere you look when it<17:10:50.040> comes<17:10:50.220> to<17:10:50.400> homes<17:10:50.640> it<17:10:51.180> may<17:10:51.296> refer<17:10:51.596> to<17:10:51.776> Locks 17:10:52.190 --> 17:10:52.200 align:start position:0% it comes to homes it may refer to Locks 17:10:52.200 --> 17:10:53.990 align:start position:0% it comes to homes it may refer to Locks and<17:10:52.256> alarm<17:10:52.436> systems<17:10:53.040> but<17:10:53.340> when<17:10:53.456> it<17:10:53.640> comes<17:10:53.820> to 17:10:53.990 --> 17:10:54.000 align:start position:0% and alarm systems but when it comes to 17:10:54.000 --> 17:10:55.786 align:start position:0% and alarm systems but when it comes to networks<17:10:54.480> it<17:10:54.660> refers<17:10:54.956> to<17:10:55.080> a<17:10:55.320> lot<17:10:55.436> of<17:10:55.560> different 17:10:55.786 --> 17:10:55.796 align:start position:0% networks it refers to a lot of different 17:10:55.796 --> 17:10:58.070 align:start position:0% networks it refers to a lot of different methods<17:10:56.400> but<17:10:56.700> the<17:10:56.936> concept<17:10:57.360> is<17:10:57.596> still<17:10:57.840> the 17:10:58.070 --> 17:10:58.080 align:start position:0% methods but the concept is still the 17:10:58.080 --> 17:11:00.350 align:start position:0% methods but the concept is still the same<17:10:58.200> the<17:10:58.916> point<17:10:59.040> of<17:10:59.220> security<17:10:59.400> regardless<17:11:00.060> of 17:11:00.350 --> 17:11:00.360 align:start position:0% same the point of security regardless of 17:11:00.360 --> 17:11:02.510 align:start position:0% same the point of security regardless of where<17:11:00.596> it<17:11:00.776> is<17:11:00.900> or<17:11:01.140> what<17:11:01.380> it's<17:11:01.500> protecting<17:11:01.916> is 17:11:02.510 --> 17:11:02.520 align:start position:0% where it is or what it's protecting is 17:11:02.520 --> 17:11:04.246 align:start position:0% where it is or what it's protecting is to<17:11:02.700> keep<17:11:02.820> the<17:11:03.000> threats<17:11:03.416> out<17:11:03.720> and<17:11:04.080> the 17:11:04.246 --> 17:11:04.256 align:start position:0% to keep the threats out and the 17:11:04.256 --> 17:11:06.586 align:start position:0% to keep the threats out and the valuables<17:11:04.680> in<17:11:04.916> think<17:11:05.456> of<17:11:05.640> a<17:11:05.756> bank<17:11:05.880> vault<17:11:06.240> the 17:11:06.586 --> 17:11:06.596 align:start position:0% valuables in think of a bank vault the 17:11:06.596 --> 17:11:09.586 align:start position:0% valuables in think of a bank vault the door<17:11:06.776> to<17:11:06.900> a<17:11:07.080> bank<17:11:07.256> fault<17:11:07.616> is<17:11:08.040> a<17:11:08.520> few<17:11:08.820> feet<17:11:09.116> thick 17:11:09.586 --> 17:11:09.596 align:start position:0% door to a bank fault is a few feet thick 17:11:09.596 --> 17:11:11.926 align:start position:0% door to a bank fault is a few feet thick it's<17:11:10.080> made<17:11:10.320> of<17:11:10.500> very<17:11:10.680> sturdy<17:11:11.040> metal<17:11:11.220> and<17:11:11.756> this 17:11:11.926 --> 17:11:11.936 align:start position:0% it's made of very sturdy metal and this 17:11:11.936 --> 17:11:14.446 align:start position:0% it's made of very sturdy metal and this is<17:11:12.000> because<17:11:12.240> the<17:11:13.200> bank<17:11:13.560> needs<17:11:13.980> to<17:11:14.040> keep<17:11:14.220> the 17:11:14.446 --> 17:11:14.456 align:start position:0% is because the bank needs to keep the 17:11:14.456 --> 17:11:17.030 align:start position:0% is because the bank needs to keep the money<17:11:14.580> invaluable<17:11:15.180> securely<17:11:15.900> inside<17:11:16.320> while 17:11:17.030 --> 17:11:17.040 align:start position:0% money invaluable securely inside while 17:11:17.040 --> 17:11:18.586 align:start position:0% money invaluable securely inside while also<17:11:17.340> keeping<17:11:17.580> the<17:11:17.756> potential<17:11:18.116> threats 17:11:18.586 --> 17:11:18.596 align:start position:0% also keeping the potential threats 17:11:18.596 --> 17:11:21.406 align:start position:0% also keeping the potential threats outside<17:11:19.200> now<17:11:20.096> if<17:11:20.400> someone<17:11:20.580> really<17:11:21.000> wants<17:11:21.360> to 17:11:21.406 --> 17:11:21.416 align:start position:0% outside now if someone really wants to 17:11:21.416 --> 17:11:22.850 align:start position:0% outside now if someone really wants to break<17:11:21.540> into<17:11:21.776> a<17:11:22.020> bank<17:11:22.140> and<17:11:22.320> steal<17:11:22.560> the<17:11:22.740> money 17:11:22.850 --> 17:11:22.860 align:start position:0% break into a bank and steal the money 17:11:22.860 --> 17:11:24.830 align:start position:0% break into a bank and steal the money they're<17:11:23.340> going<17:11:23.520> to<17:11:23.640> be<17:11:23.700> able<17:11:23.880> to<17:11:24.060> what<17:11:24.540> we<17:11:24.720> want 17:11:24.830 --> 17:11:24.840 align:start position:0% they're going to be able to what we want 17:11:24.840 --> 17:11:26.926 align:start position:0% they're going to be able to what we want to<17:11:24.956> do<17:11:25.020> is<17:11:25.140> make<17:11:25.380> it<17:11:25.500> as<17:11:25.680> hard<17:11:25.980> as<17:11:26.220> possible<17:11:26.640> for 17:11:26.926 --> 17:11:26.936 align:start position:0% to do is make it as hard as possible for 17:11:26.936 --> 17:11:28.246 align:start position:0% to do is make it as hard as possible for them<17:11:27.060> to<17:11:27.296> come<17:11:27.416> in<17:11:27.596> and<17:11:27.720> steal<17:11:27.956> the<17:11:28.140> money 17:11:28.246 --> 17:11:28.256 align:start position:0% them to come in and steal the money 17:11:28.256 --> 17:11:32.150 align:start position:0% them to come in and steal the money nothing<17:11:28.860> is<17:11:29.220> beyond<17:11:29.956> anyone's<17:11:30.956> purview<17:11:31.380> it's 17:11:32.150 --> 17:11:32.160 align:start position:0% nothing is beyond anyone's purview it's 17:11:32.160 --> 17:11:33.710 align:start position:0% nothing is beyond anyone's purview it's simply<17:11:32.520> that<17:11:32.880> we<17:11:33.060> want<17:11:33.180> to<17:11:33.296> make<17:11:33.416> it<17:11:33.596> as 17:11:33.710 --> 17:11:33.720 align:start position:0% simply that we want to make it as 17:11:33.720 --> 17:11:35.446 align:start position:0% simply that we want to make it as difficult<17:11:33.956> as<17:11:34.200> possible<17:11:34.560> for<17:11:34.860> these<17:11:35.160> thieves 17:11:35.446 --> 17:11:35.456 align:start position:0% difficult as possible for these thieves 17:11:35.456 --> 17:11:37.550 align:start position:0% difficult as possible for these thieves hackers<17:11:36.060> or<17:11:36.240> whoever<17:11:36.480> to<17:11:36.720> get<17:11:36.900> in<17:11:37.020> and<17:11:37.200> take<17:11:37.380> it 17:11:37.550 --> 17:11:37.560 align:start position:0% hackers or whoever to get in and take it 17:11:37.560 --> 17:11:39.350 align:start position:0% hackers or whoever to get in and take it now<17:11:38.096> the<17:11:38.276> same<17:11:38.400> principle<17:11:38.820> applies<17:11:39.180> to 17:11:39.350 --> 17:11:39.360 align:start position:0% now the same principle applies to 17:11:39.360 --> 17:11:41.870 align:start position:0% now the same principle applies to network<17:11:39.540> security<17:11:39.840> on<17:11:40.796> a<17:11:40.916> network<17:11:41.096> data<17:11:41.700> can 17:11:41.870 --> 17:11:41.880 align:start position:0% network security on a network data can 17:11:41.880 --> 17:11:44.510 align:start position:0% network security on a network data can sometimes<17:11:42.240> be<17:11:42.416> more<17:11:42.720> valuable<17:11:43.200> than<17:11:43.500> money<17:11:43.796> in 17:11:44.510 --> 17:11:44.520 align:start position:0% sometimes be more valuable than money in 17:11:44.520 --> 17:11:48.170 align:start position:0% sometimes be more valuable than money in fact<17:11:44.640> I<17:11:44.880> know<17:11:45.000> a<17:11:45.116> lot<17:11:45.240> of<17:11:45.416> CEO<17:11:46.380> cios<17:11:47.160> CFOs<17:11:47.880> out 17:11:48.170 --> 17:11:48.180 align:start position:0% fact I know a lot of CEO cios CFOs out 17:11:48.180 --> 17:11:49.670 align:start position:0% fact I know a lot of CEO cios CFOs out there<17:11:48.296> who<17:11:48.720> would<17:11:48.840> much<17:11:49.020> prefer<17:11:49.320> that<17:11:49.560> you 17:11:49.670 --> 17:11:49.680 align:start position:0% there who would much prefer that you 17:11:49.680 --> 17:11:51.350 align:start position:0% there who would much prefer that you steal<17:11:49.916> some<17:11:50.040> of<17:11:50.220> their<17:11:50.276> money<17:11:50.520> rather<17:11:51.240> than 17:11:51.350 --> 17:11:51.360 align:start position:0% steal some of their money rather than 17:11:51.360 --> 17:11:52.730 align:start position:0% steal some of their money rather than steal<17:11:51.776> their<17:11:51.900> data<17:11:52.200> especially<17:11:52.500> when<17:11:52.616> it 17:11:52.730 --> 17:11:52.740 align:start position:0% steal their data especially when it 17:11:52.740 --> 17:11:56.210 align:start position:0% steal their data especially when it comes<17:11:52.916> to<17:11:53.096> user<17:11:53.580> data<17:11:53.936> or<17:11:54.660> to<17:11:55.020> private<17:11:55.916> or 17:11:56.210 --> 17:11:56.220 align:start position:0% comes to user data or to private or 17:11:56.220 --> 17:11:58.426 align:start position:0% comes to user data or to private or privileged<17:11:56.700> information<17:11:57.020> because<17:11:58.020> this 17:11:58.426 --> 17:11:58.436 align:start position:0% privileged information because this 17:11:58.436 --> 17:12:00.710 align:start position:0% privileged information because this stuff<17:11:58.616> is<17:11:58.860> literally<17:11:59.160> Priceless<17:11:59.700> this<17:12:00.416> is<17:12:00.480> why 17:12:00.710 --> 17:12:00.720 align:start position:0% stuff is literally Priceless this is why 17:12:00.720 --> 17:12:02.510 align:start position:0% stuff is literally Priceless this is why it's<17:12:00.900> really<17:12:01.256> important<17:12:01.616> to<17:12:01.796> have<17:12:01.980> a<17:12:02.220> properly 17:12:02.510 --> 17:12:02.520 align:start position:0% it's really important to have a properly 17:12:02.520 --> 17:12:04.670 align:start position:0% it's really important to have a properly secured<17:12:03.000> Network<17:12:03.240> and<17:12:03.660> make<17:12:03.900> sure<17:12:04.140> that<17:12:04.380> it 17:12:04.670 --> 17:12:04.680 align:start position:0% secured Network and make sure that it 17:12:04.680 --> 17:12:06.286 align:start position:0% secured Network and make sure that it stays<17:12:05.096> that<17:12:05.276> way<17:12:05.400> and<17:12:05.880> these<17:12:06.116> are<17:12:06.180> two 17:12:06.286 --> 17:12:06.296 align:start position:0% stays that way and these are two 17:12:06.296 --> 17:12:07.970 align:start position:0% stays that way and these are two different<17:12:06.416> things<17:12:06.720> securing<17:12:07.436> it<17:12:07.560> and<17:12:07.860> then 17:12:07.970 --> 17:12:07.980 align:start position:0% different things securing it and then 17:12:07.980 --> 17:12:10.190 align:start position:0% different things securing it and then monitoring<17:12:08.456> it<17:12:08.640> to<17:12:08.820> make<17:12:09.000> sure<17:12:09.180> it<17:12:09.416> remains 17:12:10.190 --> 17:12:10.200 align:start position:0% monitoring it to make sure it remains 17:12:10.200 --> 17:12:11.510 align:start position:0% monitoring it to make sure it remains secured 17:12:11.510 --> 17:12:11.520 align:start position:0% secured 17:12:11.520 --> 17:12:12.890 align:start position:0% secured now<17:12:11.936> it's<17:12:12.060> very<17:12:12.240> important<17:12:12.480> to<17:12:12.660> make<17:12:12.776> sure 17:12:12.890 --> 17:12:12.900 align:start position:0% now it's very important to make sure 17:12:12.900 --> 17:12:14.990 align:start position:0% now it's very important to make sure that<17:12:13.080> everything<17:12:13.256> on<17:12:13.616> the<17:12:13.740> network<17:12:13.980> is<17:12:14.640> kept 17:12:14.990 --> 17:12:15.000 align:start position:0% that everything on the network is kept 17:12:15.000 --> 17:12:17.390 align:start position:0% that everything on the network is kept up<17:12:15.240> to<17:12:15.416> date<17:12:15.596> when<17:12:16.256> programs<17:12:16.796> and<17:12:17.040> patches 17:12:17.390 --> 17:12:17.400 align:start position:0% up to date when programs and patches 17:12:17.400 --> 17:12:19.130 align:start position:0% up to date when programs and patches have<17:12:17.640> been<17:12:17.820> used<17:12:17.936> for<17:12:18.296> a<17:12:18.416> long<17:12:18.540> time<17:12:18.776> and 17:12:19.130 --> 17:12:19.140 align:start position:0% have been used for a long time and 17:12:19.140 --> 17:12:21.286 align:start position:0% have been used for a long time and they're<17:12:19.320> well<17:12:19.500> known<17:12:19.740> the<17:12:20.456> attackers<17:12:20.936> who've 17:12:21.286 --> 17:12:21.296 align:start position:0% they're well known the attackers who've 17:12:21.296 --> 17:12:22.970 align:start position:0% they're well known the attackers who've had<17:12:21.416> an<17:12:21.596> opportunity<17:12:21.956> to<17:12:22.200> find<17:12:22.380> holes<17:12:22.796> with 17:12:22.970 --> 17:12:22.980 align:start position:0% had an opportunity to find holes with 17:12:22.980 --> 17:12:26.446 align:start position:0% had an opportunity to find holes with them<17:12:23.160> begin<17:12:24.060> to<17:12:24.840> make<17:12:25.436> use<17:12:25.680> of<17:12:25.860> those<17:12:26.040> holes 17:12:26.446 --> 17:12:26.456 align:start position:0% them begin to make use of those holes 17:12:26.456 --> 17:12:27.946 align:start position:0% them begin to make use of those holes and<17:12:26.700> hack<17:12:26.936> through<17:12:27.180> them 17:12:27.946 --> 17:12:27.956 align:start position:0% and hack through them 17:12:27.956 --> 17:12:29.746 align:start position:0% and hack through them so<17:12:28.436> the<17:12:28.616> longer<17:12:28.860> something<17:12:29.040> is<17:12:29.276> out<17:12:29.456> there<17:12:29.580> and 17:12:29.746 --> 17:12:29.756 align:start position:0% so the longer something is out there and 17:12:29.756 --> 17:12:32.210 align:start position:0% so the longer something is out there and being<17:12:30.000> used<17:12:30.296> without<17:12:30.776> a<17:12:31.140> new<17:12:31.256> version<17:12:31.500> the 17:12:32.210 --> 17:12:32.220 align:start position:0% being used without a new version the 17:12:32.220 --> 17:12:34.426 align:start position:0% being used without a new version the more<17:12:32.400> times<17:12:32.700> attackers<17:12:33.660> have<17:12:34.020> to<17:12:34.256> find 17:12:34.426 --> 17:12:34.436 align:start position:0% more times attackers have to find 17:12:34.436 --> 17:12:37.010 align:start position:0% more times attackers have to find exploits<17:12:35.160> within<17:12:35.580> the<17:12:35.820> program<17:12:36.000> or<17:12:36.416> the<17:12:36.596> patch 17:12:37.010 --> 17:12:37.020 align:start position:0% exploits within the program or the patch 17:12:37.020 --> 17:12:39.470 align:start position:0% exploits within the program or the patch this<17:12:37.560> is<17:12:37.616> why<17:12:37.860> as<17:12:38.160> Network<17:12:38.400> admins<17:12:39.000> we<17:12:39.240> need<17:12:39.360> to 17:12:39.470 --> 17:12:39.480 align:start position:0% this is why as Network admins we need to 17:12:39.480 --> 17:12:41.390 align:start position:0% this is why as Network admins we need to make<17:12:39.596> sure<17:12:39.900> that<17:12:40.436> all<17:12:40.616> the<17:12:40.796> programs<17:12:41.220> and 17:12:41.390 --> 17:12:41.400 align:start position:0% make sure that all the programs and 17:12:41.400 --> 17:12:43.786 align:start position:0% make sure that all the programs and patches<17:12:41.700> are<17:12:41.880> kept<17:12:42.180> up<17:12:42.296> to<17:12:42.416> date<17:12:42.796> programs 17:12:43.786 --> 17:12:43.796 align:start position:0% patches are kept up to date programs 17:12:43.796 --> 17:12:46.670 align:start position:0% patches are kept up to date programs that<17:12:43.980> get<17:12:44.220> used<17:12:44.520> often<17:12:45.180> should<17:12:45.540> be<17:12:45.720> updated<17:12:46.200> as 17:12:46.670 --> 17:12:46.680 align:start position:0% that get used often should be updated as 17:12:46.680 --> 17:12:48.946 align:start position:0% that get used often should be updated as soon<17:12:46.916> as<17:12:47.160> there<17:12:47.400> is<17:12:47.580> a<17:12:47.756> new<17:12:47.880> version<17:12:48.116> or<17:12:48.776> as 17:12:48.946 --> 17:12:48.956 align:start position:0% soon as there is a new version or as 17:12:48.956 --> 17:12:50.746 align:start position:0% soon as there is a new version or as soon<17:12:49.080> as<17:12:49.140> a<17:12:49.320> new<17:12:49.436> version<17:12:49.616> proves<17:12:50.096> to<17:12:50.276> not<17:12:50.520> be 17:12:50.746 --> 17:12:50.756 align:start position:0% soon as a new version proves to not be 17:12:50.756 --> 17:12:52.850 align:start position:0% soon as a new version proves to not be buggy<17:12:51.240> now<17:12:51.776> when<17:12:52.020> running<17:12:52.200> a<17:12:52.380> device<17:12:52.500> on 17:12:52.850 --> 17:12:52.860 align:start position:0% buggy now when running a device on 17:12:52.860 --> 17:12:55.010 align:start position:0% buggy now when running a device on Windows<17:12:53.220> the<17:12:53.700> admin<17:12:54.000> should<17:12:54.240> always<17:12:54.480> check<17:12:54.776> to 17:12:55.010 --> 17:12:55.020 align:start position:0% Windows the admin should always check to 17:12:55.020 --> 17:12:56.630 align:start position:0% Windows the admin should always check to see<17:12:55.140> if<17:12:55.256> there's<17:12:55.380> anything<17:12:55.560> available<17:12:55.980> in 17:12:56.630 --> 17:12:56.640 align:start position:0% see if there's anything available in 17:12:56.640 --> 17:12:58.786 align:start position:0% see if there's anything available in Windows<17:12:57.060> Live<17:12:57.296> update<17:12:57.720> or<17:12:57.900> Microsoft<17:12:58.320> update 17:12:58.786 --> 17:12:58.796 align:start position:0% Windows Live update or Microsoft update 17:12:58.796 --> 17:13:01.370 align:start position:0% Windows Live update or Microsoft update which<17:12:59.456> we<17:12:59.756> have<17:12:59.936> talked<17:13:00.480> about<17:13:00.596> in<17:13:00.956> a<17:13:01.200> plus 17:13:01.370 --> 17:13:01.380 align:start position:0% which we have talked about in a plus 17:13:01.380 --> 17:13:03.830 align:start position:0% which we have talked about in a plus quite<17:13:01.796> a<17:13:01.916> bit<17:13:02.040> now<17:13:02.880> usually<17:13:03.180> this<17:13:03.480> can<17:13:03.660> install 17:13:03.830 --> 17:13:03.840 align:start position:0% quite a bit now usually this can install 17:13:03.840 --> 17:13:05.510 align:start position:0% quite a bit now usually this can install new<17:13:04.200> drivers<17:13:04.560> in<17:13:04.740> patches<17:13:05.040> that<17:13:05.276> have<17:13:05.400> been 17:13:05.510 --> 17:13:05.520 align:start position:0% new drivers in patches that have been 17:13:05.520 --> 17:13:07.786 align:start position:0% new drivers in patches that have been updated<17:13:05.880> for<17:13:06.240> performance<17:13:06.660> and<17:13:06.840> security<17:13:07.140> but 17:13:07.786 --> 17:13:07.796 align:start position:0% updated for performance and security but 17:13:07.796 --> 17:13:09.350 align:start position:0% updated for performance and security but other<17:13:07.980> things<17:13:08.160> we<17:13:08.340> need<17:13:08.456> to<17:13:08.520> be<17:13:08.640> aware<17:13:08.820> of<17:13:09.000> are 17:13:09.350 --> 17:13:09.360 align:start position:0% other things we need to be aware of are 17:13:09.360 --> 17:13:11.746 align:start position:0% other things we need to be aware of are Adobe<17:13:09.776> products<17:13:10.256> Java<17:13:11.096> which<17:13:11.220> is<17:13:11.340> integrated 17:13:11.746 --> 17:13:11.756 align:start position:0% Adobe products Java which is integrated 17:13:11.756 --> 17:13:14.510 align:start position:0% Adobe products Java which is integrated into<17:13:12.000> a<17:13:12.416> lot<17:13:12.540> of<17:13:12.660> browsers<17:13:13.140> and<17:13:13.980> the<17:13:14.160> browsers 17:13:14.510 --> 17:13:14.520 align:start position:0% into a lot of browsers and the browsers 17:13:14.520 --> 17:13:16.190 align:start position:0% into a lot of browsers and the browsers themselves<17:13:15.000> to<17:13:15.360> make<17:13:15.480> sure<17:13:15.596> that<17:13:15.840> they're<17:13:15.956> all 17:13:16.190 --> 17:13:16.200 align:start position:0% themselves to make sure that they're all 17:13:16.200 --> 17:13:18.470 align:start position:0% themselves to make sure that they're all tight<17:13:16.500> and<17:13:16.616> secure<17:13:16.980> once<17:13:17.880> again<17:13:18.000> we<17:13:18.360> don't 17:13:18.470 --> 17:13:18.480 align:start position:0% tight and secure once again we don't 17:13:18.480 --> 17:13:19.730 align:start position:0% tight and secure once again we don't want<17:13:18.596> to<17:13:18.720> update<17:13:18.956> things<17:13:19.200> immediately 17:13:19.730 --> 17:13:19.740 align:start position:0% want to update things immediately 17:13:19.740 --> 17:13:21.650 align:start position:0% want to update things immediately because<17:13:20.276> maybe<17:13:20.640> they'll<17:13:21.000> bring<17:13:21.180> down<17:13:21.416> the 17:13:21.650 --> 17:13:21.660 align:start position:0% because maybe they'll bring down the 17:13:21.660 --> 17:13:23.690 align:start position:0% because maybe they'll bring down the system<17:13:21.840> but<17:13:22.740> we<17:13:22.916> need<17:13:23.040> to<17:13:23.160> weigh<17:13:23.400> this<17:13:23.520> against 17:13:23.690 --> 17:13:23.700 align:start position:0% system but we need to weigh this against 17:13:23.700 --> 17:13:25.730 align:start position:0% system but we need to weigh this against the<17:13:24.060> fact<17:13:24.180> that<17:13:24.660> if<17:13:24.776> a<17:13:24.956> patch<17:13:25.256> goes<17:13:25.500> out<17:13:25.560> there 17:13:25.730 --> 17:13:25.740 align:start position:0% the fact that if a patch goes out there 17:13:25.740 --> 17:13:29.990 align:start position:0% the fact that if a patch goes out there to<17:13:25.980> to<17:13:26.820> plug<17:13:27.540> up<17:13:27.900> a<17:13:28.500> security<17:13:28.680> flaw<17:13:29.340> that<17:13:29.820> as 17:13:29.990 --> 17:13:30.000 align:start position:0% to to plug up a security flaw that as 17:13:30.000 --> 17:13:31.850 align:start position:0% to to plug up a security flaw that as soon<17:13:30.116> as<17:13:30.240> it<17:13:30.360> goes<17:13:30.596> out<17:13:30.776> there<17:13:30.956> the<17:13:31.436> hackers 17:13:31.850 --> 17:13:31.860 align:start position:0% soon as it goes out there the hackers 17:13:31.860 --> 17:13:34.130 align:start position:0% soon as it goes out there the hackers now<17:13:32.220> know<17:13:32.640> oh<17:13:33.180> look<17:13:33.360> there<17:13:33.776> was<17:13:33.900> a<17:13:34.020> security 17:13:34.130 --> 17:13:34.140 align:start position:0% now know oh look there was a security 17:13:34.140 --> 17:13:36.946 align:start position:0% now know oh look there was a security flaw<17:13:34.616> and<17:13:35.096> now<17:13:35.220> they<17:13:35.456> can<17:13:35.640> begin<17:13:35.880> to<17:13:36.416> make<17:13:36.660> use 17:13:36.946 --> 17:13:36.956 align:start position:0% flaw and now they can begin to make use 17:13:36.956 --> 17:13:39.710 align:start position:0% flaw and now they can begin to make use of<17:13:37.140> that<17:13:37.320> security<17:13:37.436> flaw<17:13:37.980> until<17:13:38.400> you<17:13:39.296> update 17:13:39.710 --> 17:13:39.720 align:start position:0% of that security flaw until you update 17:13:39.720 --> 17:13:41.266 align:start position:0% of that security flaw until you update things<17:13:39.956> so<17:13:40.436> what<17:13:40.616> we're<17:13:40.740> really<17:13:40.860> looking<17:13:41.096> to 17:13:41.266 --> 17:13:41.276 align:start position:0% things so what we're really looking to 17:13:41.276 --> 17:13:45.470 align:start position:0% things so what we're really looking to do<17:13:41.456> is<17:13:42.296> balance 17:13:45.470 --> 17:13:45.480 align:start position:0% 17:13:45.480 --> 17:13:49.906 align:start position:0% updating<17:13:46.140> immediately 17:13:49.906 --> 17:13:49.916 align:start position:0% 17:13:49.916 --> 17:13:52.906 align:start position:0% versus 17:13:52.906 --> 17:13:52.916 align:start position:0% 17:13:52.916 --> 17:13:55.670 align:start position:0% buggy<17:13:53.580> Updates<17:13:53.900> this<17:13:54.900> is<17:13:55.020> an<17:13:55.140> important<17:13:55.500> thing 17:13:55.670 --> 17:13:55.680 align:start position:0% buggy Updates this is an important thing 17:13:55.680 --> 17:13:58.426 align:start position:0% buggy Updates this is an important thing to<17:13:55.860> keep<17:13:56.040> in<17:13:56.220> mind 17:13:58.426 --> 17:13:58.436 align:start position:0% 17:13:58.436 --> 17:14:01.906 align:start position:0% now<17:13:58.860> it's<17:13:59.160> very<17:13:59.640> important<17:14:00.360> that<17:14:01.140> we<17:14:01.740> keep 17:14:01.906 --> 17:14:01.916 align:start position:0% now it's very important that we keep 17:14:01.916 --> 17:14:04.786 align:start position:0% now it's very important that we keep another<17:14:02.340> aspect<17:14:03.116> of<17:14:03.660> security<17:14:04.080> in<17:14:04.436> mind<17:14:04.560> when 17:14:04.786 --> 17:14:04.796 align:start position:0% another aspect of security in mind when 17:14:04.796 --> 17:14:06.350 align:start position:0% another aspect of security in mind when it<17:14:04.916> comes<17:14:05.160> not<17:14:05.276> just<17:14:05.400> to<17:14:05.520> our<17:14:05.640> networks<17:14:06.060> but<17:14:06.180> to 17:14:06.350 --> 17:14:06.360 align:start position:0% it comes not just to our networks but to 17:14:06.360 --> 17:14:08.266 align:start position:0% it comes not just to our networks but to just<17:14:06.660> about<17:14:06.776> anything<17:14:07.436> we're<17:14:07.860> dealing<17:14:08.160> with 17:14:08.266 --> 17:14:08.276 align:start position:0% just about anything we're dealing with 17:14:08.276 --> 17:14:10.246 align:start position:0% just about anything we're dealing with on<17:14:08.456> devices<17:14:08.756> and<17:14:09.116> this<17:14:09.240> is<17:14:09.360> our<17:14:09.540> passport<17:14:09.956> our 17:14:10.246 --> 17:14:10.256 align:start position:0% on devices and this is our passport our 17:14:10.256 --> 17:14:12.286 align:start position:0% on devices and this is our passport our passwords<17:14:10.980> people<17:14:11.580> tend<17:14:11.820> to<17:14:11.936> think<17:14:12.000> that<17:14:12.116> just 17:14:12.286 --> 17:14:12.296 align:start position:0% passwords people tend to think that just 17:14:12.296 --> 17:14:13.786 align:start position:0% passwords people tend to think that just because<17:14:12.416> something<17:14:12.776> is<17:14:12.956> password<17:14:13.140> protected 17:14:13.786 --> 17:14:13.796 align:start position:0% because something is password protected 17:14:13.796 --> 17:14:16.070 align:start position:0% because something is password protected that<17:14:14.040> means<17:14:14.400> it's<17:14:14.580> safe<17:14:14.820> but<17:14:15.180> this<17:14:15.776> really 17:14:16.070 --> 17:14:16.080 align:start position:0% that means it's safe but this really 17:14:16.080 --> 17:14:18.170 align:start position:0% that means it's safe but this really isn't<17:14:16.560> true<17:14:16.796> something<17:14:17.340> that's<17:14:17.520> protected<17:14:18.000> by 17:14:18.170 --> 17:14:18.180 align:start position:0% isn't true something that's protected by 17:14:18.180 --> 17:14:20.510 align:start position:0% isn't true something that's protected by a<17:14:18.360> password<17:14:18.540> is<17:14:18.900> ultimately<17:14:19.340> safer<17:14:20.340> than 17:14:20.510 --> 17:14:20.520 align:start position:0% a password is ultimately safer than 17:14:20.520 --> 17:14:22.786 align:start position:0% a password is ultimately safer than something<17:14:20.756> that's<17:14:21.000> not<17:14:21.296> but<17:14:21.660> a<17:14:21.900> password<17:14:22.080> is 17:14:22.786 --> 17:14:22.796 align:start position:0% something that's not but a password is 17:14:22.796 --> 17:14:24.530 align:start position:0% something that's not but a password is nearly<17:14:23.096> useless<17:14:23.456> unless<17:14:23.756> it's<17:14:23.936> a<17:14:24.116> strong<17:14:24.296> one 17:14:24.530 --> 17:14:24.540 align:start position:0% nearly useless unless it's a strong one 17:14:24.540 --> 17:14:26.746 align:start position:0% nearly useless unless it's a strong one think<17:14:24.900> about<17:14:25.080> all<17:14:25.320> the<17:14:25.616> movies<17:14:26.340> in<17:14:26.640> which 17:14:26.746 --> 17:14:26.756 align:start position:0% think about all the movies in which 17:14:26.756 --> 17:14:28.010 align:start position:0% think about all the movies in which someone<17:14:26.936> has<17:14:27.180> to<17:14:27.296> figure<17:14:27.480> out<17:14:27.660> someone's 17:14:28.010 --> 17:14:28.020 align:start position:0% someone has to figure out someone's 17:14:28.020 --> 17:14:30.170 align:start position:0% someone has to figure out someone's password<17:14:28.256> looks<17:14:29.160> around<17:14:29.276> the<17:14:29.456> room<17:14:29.580> sees<17:14:30.060> a 17:14:30.170 --> 17:14:30.180 align:start position:0% password looks around the room sees a 17:14:30.180 --> 17:14:31.730 align:start position:0% password looks around the room sees a picture<17:14:30.296> types<17:14:30.840> in<17:14:30.956> the<17:14:31.080> name<17:14:31.200> of<17:14:31.380> that<17:14:31.500> person 17:14:31.730 --> 17:14:31.740 align:start position:0% picture types in the name of that person 17:14:31.740 --> 17:14:34.246 align:start position:0% picture types in the name of that person and<17:14:31.980> Bam<17:14:32.276> they're<17:14:32.520> in<17:14:32.840> attackers<17:14:33.840> can<17:14:34.080> use 17:14:34.246 --> 17:14:34.256 align:start position:0% and Bam they're in attackers can use 17:14:34.256 --> 17:14:37.906 align:start position:0% and Bam they're in attackers can use things<17:14:34.500> called<17:14:34.980> key<17:14:35.640> loggers<17:14:36.596> in<17:14:37.256> order<17:14:37.436> to 17:14:37.906 --> 17:14:37.916 align:start position:0% things called key loggers in order to 17:14:37.916 --> 17:14:41.150 align:start position:0% things called key loggers in order to log<17:14:38.220> uh<17:14:39.060> what<17:14:39.660> passwords<17:14:40.380> you<17:14:40.560> are<17:14:40.680> entering 17:14:41.150 --> 17:14:41.160 align:start position:0% log uh what passwords you are entering 17:14:41.160 --> 17:14:43.070 align:start position:0% log uh what passwords you are entering on<17:14:41.340> your<17:14:41.520> computer<17:14:41.640> and<17:14:42.180> then<17:14:42.360> send<17:14:42.596> that<17:14:42.840> over 17:14:43.070 --> 17:14:43.080 align:start position:0% on your computer and then send that over 17:14:43.080 --> 17:14:45.406 align:start position:0% on your computer and then send that over to<17:14:43.500> the<17:14:43.616> hacker<17:14:44.040> they<17:14:44.580> can<17:14:44.756> then<17:14:44.936> take<17:14:45.180> the 17:14:45.406 --> 17:14:45.416 align:start position:0% to the hacker they can then take the 17:14:45.416 --> 17:14:47.570 align:start position:0% to the hacker they can then take the letters<17:14:45.660> symbols<17:14:46.256> Etc<17:14:46.380> and<17:14:46.680> being<17:14:46.860> used<17:14:47.096> and 17:14:47.570 --> 17:14:47.580 align:start position:0% letters symbols Etc and being used and 17:14:47.580 --> 17:14:48.946 align:start position:0% letters symbols Etc and being used and try<17:14:47.756> to<17:14:47.880> piece<17:14:48.180> together<17:14:48.296> what<17:14:48.660> the<17:14:48.776> password 17:14:48.946 --> 17:14:48.956 align:start position:0% try to piece together what the password 17:14:48.956 --> 17:14:51.170 align:start position:0% try to piece together what the password could<17:14:49.380> be<17:14:49.560> depending<17:14:50.340> on<17:14:50.400> the<17:14:50.580> attacker<17:14:50.936> they 17:14:51.170 --> 17:14:51.180 align:start position:0% could be depending on the attacker they 17:14:51.180 --> 17:14:53.150 align:start position:0% could be depending on the attacker they might<17:14:51.480> be<17:14:51.840> really<17:14:52.140> successful<17:14:52.616> at<17:14:52.796> stealing 17:14:53.150 --> 17:14:53.160 align:start position:0% might be really successful at stealing 17:14:53.160 --> 17:14:55.490 align:start position:0% might be really successful at stealing your<17:14:53.276> password<17:14:53.456> simply<17:14:54.416> by<17:14:54.540> just<17:14:54.900> observing 17:14:55.490 --> 17:14:55.500 align:start position:0% your password simply by just observing 17:14:55.500 --> 17:14:58.246 align:start position:0% your password simply by just observing what<17:14:55.740> you<17:14:55.916> type<17:14:56.040> in<17:14:56.276> this<17:14:56.936> is<17:14:57.060> called<17:14:57.360> shoulder 17:14:58.246 --> 17:14:58.256 align:start position:0% what you type in this is called shoulder 17:14:58.256 --> 17:15:00.470 align:start position:0% what you type in this is called shoulder surfing 17:15:00.470 --> 17:15:00.480 align:start position:0% surfing 17:15:00.480 --> 17:15:02.630 align:start position:0% surfing and<17:15:00.956> it<17:15:01.320> is<17:15:01.500> a<17:15:01.796> big<17:15:01.860> problem<17:15:02.096> when<17:15:02.340> we<17:15:02.456> think 17:15:02.630 --> 17:15:02.640 align:start position:0% and it is a big problem when we think 17:15:02.640 --> 17:15:05.210 align:start position:0% and it is a big problem when we think about<17:15:02.756> ATMs<17:15:03.540> people<17:15:03.776> typing<17:15:04.256> at<17:15:04.560> their<17:15:05.040> office 17:15:05.210 --> 17:15:05.220 align:start position:0% about ATMs people typing at their office 17:15:05.220 --> 17:15:07.850 align:start position:0% about ATMs people typing at their office and<17:15:05.580> so<17:15:05.756> on<17:15:06.416> this<17:15:06.956> is<17:15:07.080> a<17:15:07.200> huge<17:15:07.436> problem<17:15:07.616> in 17:15:07.850 --> 17:15:07.860 align:start position:0% and so on this is a huge problem in 17:15:07.860 --> 17:15:09.946 align:start position:0% and so on this is a huge problem in general<17:15:08.040> but<17:15:08.340> it's<17:15:08.700> really<17:15:09.060> problematic<17:15:09.720> if 17:15:09.946 --> 17:15:09.956 align:start position:0% general but it's really problematic if 17:15:09.956 --> 17:15:11.690 align:start position:0% general but it's really problematic if you<17:15:10.080> use<17:15:10.256> the<17:15:10.560> same<17:15:10.740> password<17:15:11.040> for<17:15:11.400> more<17:15:11.520> than 17:15:11.690 --> 17:15:11.700 align:start position:0% you use the same password for more than 17:15:11.700 --> 17:15:14.210 align:start position:0% you use the same password for more than one<17:15:11.936> thing<17:15:12.116> think<17:15:12.776> about<17:15:12.956> it<17:15:13.200> as<17:15:13.796> soon<17:15:13.980> as<17:15:14.040> they 17:15:14.210 --> 17:15:14.220 align:start position:0% one thing think about it as soon as they 17:15:14.220 --> 17:15:15.946 align:start position:0% one thing think about it as soon as they get<17:15:14.340> one<17:15:14.520> password<17:15:14.756> they<17:15:15.180> have<17:15:15.296> access<17:15:15.540> to 17:15:15.946 --> 17:15:15.956 align:start position:0% get one password they have access to 17:15:15.956 --> 17:15:17.870 align:start position:0% get one password they have access to everything<17:15:16.200> especially<17:15:17.160> if<17:15:17.276> they<17:15:17.400> get<17:15:17.640> access 17:15:17.870 --> 17:15:17.880 align:start position:0% everything especially if they get access 17:15:17.880 --> 17:15:20.510 align:start position:0% everything especially if they get access to<17:15:18.296> your<17:15:18.480> email<17:15:18.840> they<17:15:19.436> now<17:15:19.560> have<17:15:19.796> access<17:15:20.096> to 17:15:20.510 --> 17:15:20.520 align:start position:0% to your email they now have access to 17:15:20.520 --> 17:15:22.310 align:start position:0% to your email they now have access to your<17:15:20.640> entire<17:15:20.936> life<17:15:21.180> because<17:15:21.540> they<17:15:21.776> can<17:15:21.900> reset 17:15:22.310 --> 17:15:22.320 align:start position:0% your entire life because they can reset 17:15:22.320 --> 17:15:24.530 align:start position:0% your entire life because they can reset everything<17:15:22.616> through<17:15:23.340> your<17:15:23.520> email<17:15:23.700> so<17:15:24.416> it's 17:15:24.530 --> 17:15:24.540 align:start position:0% everything through your email so it's 17:15:24.540 --> 17:15:25.970 align:start position:0% everything through your email so it's really<17:15:24.956> important<17:15:25.380> to<17:15:25.560> keep<17:15:25.680> different 17:15:25.970 --> 17:15:25.980 align:start position:0% really important to keep different 17:15:25.980 --> 17:15:29.210 align:start position:0% really important to keep different passwords<17:15:26.820> for<17:15:27.720> each<17:15:28.020> sort<17:15:28.380> of<17:15:28.500> service<17:15:28.796> that 17:15:29.210 --> 17:15:29.220 align:start position:0% passwords for each sort of service that 17:15:29.220 --> 17:15:31.606 align:start position:0% passwords for each sort of service that you<17:15:29.456> access<17:15:29.700> in<17:15:30.596> a<17:15:30.776> general<17:15:30.900> rule<17:15:31.320> you 17:15:31.606 --> 17:15:31.616 align:start position:0% you access in a general rule you 17:15:31.616 --> 17:15:33.230 align:start position:0% you access in a general rule you shouldn't<17:15:31.860> use<17:15:32.096> the<17:15:32.340> same<17:15:32.456> password<17:15:32.700> for<17:15:33.060> more 17:15:33.230 --> 17:15:33.240 align:start position:0% shouldn't use the same password for more 17:15:33.240 --> 17:15:35.150 align:start position:0% shouldn't use the same password for more than<17:15:33.360> one<17:15:33.596> thing<17:15:33.776> this<17:15:34.436> can<17:15:34.680> end<17:15:34.796> up<17:15:34.860> becoming 17:15:35.150 --> 17:15:35.160 align:start position:0% than one thing this can end up becoming 17:15:35.160 --> 17:15:36.766 align:start position:0% than one thing this can end up becoming really<17:15:35.340> confusing<17:15:35.936> if<17:15:36.360> you're<17:15:36.480> dealing<17:15:36.720> with 17:15:36.766 --> 17:15:36.776 align:start position:0% really confusing if you're dealing with 17:15:36.776 --> 17:15:38.030 align:start position:0% really confusing if you're dealing with a<17:15:36.900> lot<17:15:37.020> of<17:15:37.080> different<17:15:37.256> accounts<17:15:37.680> that<17:15:37.860> require 17:15:38.030 --> 17:15:38.040 align:start position:0% a lot of different accounts that require 17:15:38.040 --> 17:15:40.070 align:start position:0% a lot of different accounts that require many<17:15:38.400> different<17:15:38.640> passwords<17:15:39.240> so<17:15:39.720> there<17:15:39.900> are 17:15:40.070 --> 17:15:40.080 align:start position:0% many different passwords so there are 17:15:40.080 --> 17:15:42.286 align:start position:0% many different passwords so there are some<17:15:40.320> programs<17:15:40.796> that<17:15:41.040> act<17:15:41.276> as<17:15:41.580> basically 17:15:42.286 --> 17:15:42.296 align:start position:0% some programs that act as basically 17:15:42.296 --> 17:15:44.870 align:start position:0% some programs that act as basically password<17:15:42.596> vaults<17:15:43.380> and<17:15:43.860> they<17:15:44.096> require<17:15:44.276> one 17:15:44.870 --> 17:15:44.880 align:start position:0% password vaults and they require one 17:15:44.880 --> 17:15:47.210 align:start position:0% password vaults and they require one master<17:15:45.116> password<17:15:45.596> to<17:15:46.320> access<17:15:46.500> them<17:15:46.860> and<17:15:47.096> then 17:15:47.210 --> 17:15:47.220 align:start position:0% master password to access them and then 17:15:47.220 --> 17:15:48.946 align:start position:0% master password to access them and then you<17:15:47.400> have<17:15:47.580> all<17:15:47.880> of<17:15:48.000> your<17:15:48.116> information<17:15:48.296> stored 17:15:48.946 --> 17:15:48.956 align:start position:0% you have all of your information stored 17:15:48.956 --> 17:15:52.010 align:start position:0% you have all of your information stored inside<17:15:49.080> of<17:15:49.436> those<17:15:49.560> but<17:15:50.520> I<17:15:51.480> think<17:15:51.596> some<17:15:51.900> of 17:15:52.010 --> 17:15:52.020 align:start position:0% inside of those but I think some of 17:15:52.020 --> 17:15:53.746 align:start position:0% inside of those but I think some of those<17:15:52.200> just<17:15:52.680> have<17:15:52.796> as<17:15:52.980> many<17:15:53.160> problems<17:15:53.640> as 17:15:53.746 --> 17:15:53.756 align:start position:0% those just have as many problems as 17:15:53.756 --> 17:15:55.730 align:start position:0% those just have as many problems as regular<17:15:54.116> passwords<17:15:54.660> all<17:15:55.080> you<17:15:55.256> need<17:15:55.380> to<17:15:55.436> do<17:15:55.560> is 17:15:55.730 --> 17:15:55.740 align:start position:0% regular passwords all you need to do is 17:15:55.740 --> 17:15:58.490 align:start position:0% regular passwords all you need to do is get<17:15:55.980> access<17:15:56.160> to<17:15:56.580> the<17:15:56.880> one<17:15:57.296> program<17:15:57.660> and 17:15:58.490 --> 17:15:58.500 align:start position:0% get access to the one program and 17:15:58.500 --> 17:16:00.890 align:start position:0% get access to the one program and suddenly<17:15:58.860> you<17:15:59.400> have<17:15:59.580> access<17:15:59.820> to<17:16:00.240> all<17:16:00.596> of<17:16:00.720> the 17:16:00.890 --> 17:16:00.900 align:start position:0% suddenly you have access to all of the 17:16:00.900 --> 17:16:03.470 align:start position:0% suddenly you have access to all of the password<17:16:01.080> programs<17:16:01.860> so<17:16:02.640> it's<17:16:03.000> important 17:16:03.470 --> 17:16:03.480 align:start position:0% password programs so it's important 17:16:03.480 --> 17:16:05.630 align:start position:0% password programs so it's important sometimes<17:16:04.140> for<17:16:04.500> you<17:16:04.616> to<17:16:04.860> create<17:16:05.040> a<17:16:05.520> long 17:16:05.630 --> 17:16:05.640 align:start position:0% sometimes for you to create a long 17:16:05.640 --> 17:16:07.786 align:start position:0% sometimes for you to create a long random<17:16:06.060> password<17:16:06.360> word<17:16:06.840> that<17:16:07.320> can<17:16:07.500> contain 17:16:07.786 --> 17:16:07.796 align:start position:0% random password word that can contain 17:16:07.796 --> 17:16:09.530 align:start position:0% random password word that can contain special<17:16:08.096> characters<17:16:08.520> like<17:16:08.936> slashes 17:16:09.530 --> 17:16:09.540 align:start position:0% special characters like slashes 17:16:09.540 --> 17:16:11.810 align:start position:0% special characters like slashes ampersands<17:16:10.436> Etc<17:16:10.560> these<17:16:11.220> programs<17:16:11.580> can<17:16:11.700> do 17:16:11.810 --> 17:16:11.820 align:start position:0% ampersands Etc these programs can do 17:16:11.820 --> 17:16:13.426 align:start position:0% ampersands Etc these programs can do that<17:16:11.936> as<17:16:12.060> well<17:16:12.240> but<17:16:12.776> the<17:16:12.900> problem<17:16:13.020> with<17:16:13.200> that 17:16:13.426 --> 17:16:13.436 align:start position:0% that as well but the problem with that 17:16:13.436 --> 17:16:15.106 align:start position:0% that as well but the problem with that is<17:16:13.616> we're<17:16:14.276> also<17:16:14.580> not<17:16:14.700> going<17:16:14.820> to<17:16:14.880> be<17:16:14.936> able<17:16:15.000> to 17:16:15.106 --> 17:16:15.116 align:start position:0% is we're also not going to be able to 17:16:15.116 --> 17:16:16.370 align:start position:0% is we're also not going to be able to memorize<17:16:15.480> that 17:16:16.370 --> 17:16:16.380 align:start position:0% memorize that 17:16:16.380 --> 17:16:19.246 align:start position:0% memorize that so<17:16:16.980> and<17:16:17.520> another<17:16:17.756> important<17:16:18.720> aspect<17:16:19.080> of 17:16:19.246 --> 17:16:19.256 align:start position:0% so and another important aspect of 17:16:19.256 --> 17:16:21.530 align:start position:0% so and another important aspect of password<17:16:19.436> Corrections<17:16:20.276> uh<17:16:21.060> protection 17:16:21.530 --> 17:16:21.540 align:start position:0% password Corrections uh protection 17:16:21.540 --> 17:16:23.630 align:start position:0% password Corrections uh protection rather<17:16:21.956> when<17:16:22.140> it<17:16:22.320> comes<17:16:22.500> to<17:16:22.680> strong<17:16:22.916> passwords 17:16:23.630 --> 17:16:23.640 align:start position:0% rather when it comes to strong passwords 17:16:23.640 --> 17:16:27.766 align:start position:0% rather when it comes to strong passwords is<17:16:24.060> to<17:16:24.240> use<17:16:24.416> random<17:16:24.900> letters<17:16:25.320> symbols<17:16:26.700> Etc<17:16:26.880> and 17:16:27.766 --> 17:16:27.776 align:start position:0% is to use random letters symbols Etc and 17:16:27.776 --> 17:16:29.150 align:start position:0% is to use random letters symbols Etc and long<17:16:27.956> passwords<17:16:28.560> which<17:16:28.680> are<17:16:28.796> always<17:16:28.916> better 17:16:29.150 --> 17:16:29.160 align:start position:0% long passwords which are always better 17:16:29.160 --> 17:16:31.010 align:start position:0% long passwords which are always better than<17:16:29.456> short<17:16:29.756> ones 17:16:31.010 --> 17:16:31.020 align:start position:0% than short ones 17:16:31.020 --> 17:16:34.086 align:start position:0% than short ones for<17:16:31.500> instance<17:16:31.740> using<17:16:32.456> the<17:16:32.640> password 17:16:34.086 --> 17:16:34.096 align:start position:0% for instance using the password 17:16:34.096 --> 17:16:37.370 align:start position:0% for instance using the password password123<17:16:35.096> is<17:16:35.340> really<17:16:35.640> weak<17:16:36.240> whereas<17:16:36.956> this 17:16:37.370 --> 17:16:37.380 align:start position:0% password123 is really weak whereas this 17:16:37.380 --> 17:16:39.170 align:start position:0% password123 is really weak whereas this one<17:16:37.560> on<17:16:37.980> the<17:16:38.096> right<17:16:38.220> which<17:16:38.700> I<17:16:38.936> can't<17:16:39.060> even 17:16:39.170 --> 17:16:39.180 align:start position:0% one on the right which I can't even 17:16:39.180 --> 17:16:41.266 align:start position:0% one on the right which I can't even pronounce<17:16:39.540> is<17:16:39.776> really<17:16:40.080> strong<17:16:40.380> now<17:16:40.916> of<17:16:41.096> course 17:16:41.266 --> 17:16:41.276 align:start position:0% pronounce is really strong now of course 17:16:41.276 --> 17:16:43.550 align:start position:0% pronounce is really strong now of course the<17:16:41.756> problem<17:16:41.936> with<17:16:42.180> this<17:16:42.416> is<17:16:42.660> it's<17:16:43.200> difficult 17:16:43.550 --> 17:16:43.560 align:start position:0% the problem with this is it's difficult 17:16:43.560 --> 17:16:45.710 align:start position:0% the problem with this is it's difficult to<17:16:43.860> memorize<17:16:44.220> and<17:16:45.000> if<17:16:45.116> it's<17:16:45.240> difficult<17:16:45.540> to 17:16:45.710 --> 17:16:45.720 align:start position:0% to memorize and if it's difficult to 17:16:45.720 --> 17:16:47.086 align:start position:0% to memorize and if it's difficult to memorize<17:16:46.080> you're<17:16:46.436> probably<17:16:46.616> going<17:16:46.796> to<17:16:46.980> have 17:16:47.086 --> 17:16:47.096 align:start position:0% memorize you're probably going to have 17:16:47.096 --> 17:16:49.310 align:start position:0% memorize you're probably going to have to<17:16:47.340> write<17:16:47.640> it<17:16:47.880> down<17:16:48.116> if<17:16:48.660> you<17:16:48.840> write<17:16:48.956> it<17:16:49.140> down 17:16:49.310 --> 17:16:49.320 align:start position:0% to write it down if you write it down 17:16:49.320 --> 17:16:51.350 align:start position:0% to write it down if you write it down that<17:16:49.560> gives<17:16:49.680> someone<17:16:49.916> something<17:16:50.340> to<17:16:50.640> steal<17:16:50.936> or 17:16:51.350 --> 17:16:51.360 align:start position:0% that gives someone something to steal or 17:16:51.360 --> 17:16:53.390 align:start position:0% that gives someone something to steal or you<17:16:51.596> put<17:16:51.720> it<17:16:51.840> in<17:16:51.956> a<17:16:52.140> password<17:16:52.256> Vault<17:16:52.740> or<17:16:53.220> this 17:16:53.390 --> 17:16:53.400 align:start position:0% you put it in a password Vault or this 17:16:53.400 --> 17:16:56.210 align:start position:0% you put it in a password Vault or this is<17:16:53.580> maybe<17:16:53.936> made<17:16:54.296> up<17:16:54.480> automatically<17:16:55.200> but<17:16:55.980> in 17:16:56.210 --> 17:16:56.220 align:start position:0% is maybe made up automatically but in 17:16:56.220 --> 17:16:58.190 align:start position:0% is maybe made up automatically but in all<17:16:56.340> these<17:16:56.520> cases<17:16:56.880> one<17:16:57.360> password<17:16:57.596> can<17:16:58.020> get 17:16:58.190 --> 17:16:58.200 align:start position:0% all these cases one password can get 17:16:58.200 --> 17:17:00.710 align:start position:0% all these cases one password can get access<17:16:58.436> to<17:16:58.916> all<17:16:59.096> the<17:16:59.220> passwords<17:16:59.700> and<17:17:00.240> so<17:17:00.416> it's 17:17:00.710 --> 17:17:00.720 align:start position:0% access to all the passwords and so it's 17:17:00.720 --> 17:17:02.746 align:start position:0% access to all the passwords and so it's important<17:17:01.200> again<17:17:01.796> we<17:17:02.160> talked<17:17:02.456> in<17:17:02.580> the 17:17:02.746 --> 17:17:02.756 align:start position:0% important again we talked in the 17:17:02.756 --> 17:17:05.390 align:start position:0% important again we talked in the previous<17:17:02.820> one<17:17:03.116> about<17:17:03.416> we<17:17:03.900> sort<17:17:04.140> of<17:17:04.256> have<17:17:04.500> to 17:17:05.390 --> 17:17:05.400 align:start position:0% previous one about we sort of have to 17:17:05.400 --> 17:17:07.070 align:start position:0% previous one about we sort of have to decide<17:17:06.240> whether<17:17:06.416> we<17:17:06.660> want<17:17:06.720> to<17:17:06.840> update 17:17:07.070 --> 17:17:07.080 align:start position:0% decide whether we want to update 17:17:07.080 --> 17:17:09.050 align:start position:0% decide whether we want to update something<17:17:07.256> immediately<17:17:07.796> or<17:17:08.456> whether<17:17:08.640> we<17:17:08.880> want 17:17:09.050 --> 17:17:09.060 align:start position:0% something immediately or whether we want 17:17:09.060 --> 17:17:11.630 align:start position:0% something immediately or whether we want to<17:17:09.180> update<17:17:09.540> it<17:17:09.720> you<17:17:10.560> know<17:17:10.680> after<17:17:11.096> a<17:17:11.340> little<17:17:11.456> bit 17:17:11.630 --> 17:17:11.640 align:start position:0% to update it you know after a little bit 17:17:11.640 --> 17:17:13.130 align:start position:0% to update it you know after a little bit after<17:17:11.820> it's<17:17:12.000> been<17:17:12.180> tested<17:17:12.480> the<17:17:12.776> same<17:17:12.900> sort<17:17:13.080> of 17:17:13.130 --> 17:17:13.140 align:start position:0% after it's been tested the same sort of 17:17:13.140 --> 17:17:14.630 align:start position:0% after it's been tested the same sort of thing<17:17:13.256> with<17:17:13.436> passwords<17:17:13.980> we<17:17:14.340> don't<17:17:14.456> want 17:17:14.630 --> 17:17:14.640 align:start position:0% thing with passwords we don't want 17:17:14.640 --> 17:17:16.670 align:start position:0% thing with passwords we don't want something<17:17:14.820> too<17:17:15.180> weak<17:17:15.540> but<17:17:16.020> we<17:17:16.256> also<17:17:16.500> don't 17:17:16.670 --> 17:17:16.680 align:start position:0% something too weak but we also don't 17:17:16.680 --> 17:17:18.470 align:start position:0% something too weak but we also don't want<17:17:16.860> something<17:17:17.160> too<17:17:17.580> strong<17:17:17.756> that<17:17:18.060> we<17:17:18.360> can't 17:17:18.470 --> 17:17:18.480 align:start position:0% want something too strong that we can't 17:17:18.480 --> 17:17:21.286 align:start position:0% want something too strong that we can't remember<17:17:18.840> so<17:17:19.680> the<17:17:19.796> best<17:17:19.980> thing<17:17:20.220> I<17:17:20.520> think<17:17:20.700> is<17:17:21.116> to 17:17:21.286 --> 17:17:21.296 align:start position:0% remember so the best thing I think is to 17:17:21.296 --> 17:17:25.970 align:start position:0% remember so the best thing I think is to think<17:17:21.480> about<17:17:21.660> for<17:17:22.500> instance<17:17:22.796> a<17:17:23.700> pass<17:17:24.436> a<17:17:25.436> code 17:17:25.970 --> 17:17:25.980 align:start position:0% think about for instance a pass a code 17:17:25.980 --> 17:17:28.730 align:start position:0% think about for instance a pass a code that<17:17:26.340> for<17:17:26.580> yourself<17:17:26.820> so<17:17:27.720> for<17:17:27.956> instance<17:17:28.256> a 17:17:28.730 --> 17:17:28.740 align:start position:0% that for yourself so for instance a 17:17:28.740 --> 17:17:31.970 align:start position:0% that for yourself so for instance a common<17:17:28.916> one<17:17:29.160> with<17:17:29.520> the<17:17:29.820> term<17:17:30.000> password<17:17:30.616> is<17:17:31.616> to 17:17:31.970 --> 17:17:31.980 align:start position:0% common one with the term password is to 17:17:31.980 --> 17:17:34.190 align:start position:0% common one with the term password is to replace 17:17:34.190 --> 17:17:34.200 align:start position:0% 17:17:34.200 --> 17:17:37.850 align:start position:0% the<17:17:34.740> A's<17:17:35.160> with<17:17:35.340> ATS<17:17:35.756> and<17:17:36.540> the<17:17:36.956> O's<17:17:37.256> with<17:17:37.500> zeros 17:17:37.850 --> 17:17:37.860 align:start position:0% the A's with ATS and the O's with zeros 17:17:37.860 --> 17:17:40.190 align:start position:0% the A's with ATS and the O's with zeros if<17:17:38.400> you<17:17:38.520> think<17:17:38.700> about<17:17:38.880> creating<17:17:39.480> your<17:17:40.020> own 17:17:40.190 --> 17:17:40.200 align:start position:0% if you think about creating your own 17:17:40.200 --> 17:17:42.406 align:start position:0% if you think about creating your own password<17:17:40.500> we<17:17:40.916> could<17:17:41.096> do<17:17:41.276> this<17:17:41.456> for<17:17:42.180> instance 17:17:42.406 --> 17:17:42.416 align:start position:0% password we could do this for instance 17:17:42.416 --> 17:17:44.510 align:start position:0% password we could do this for instance let's<17:17:42.660> say<17:17:42.776> we<17:17:42.956> wanted<17:17:43.140> to<17:17:43.380> turn<17:17:43.616> this<17:17:44.040> secure 17:17:44.510 --> 17:17:44.520 align:start position:0% let's say we wanted to turn this secure 17:17:44.520 --> 17:17:47.630 align:start position:0% let's say we wanted to turn this secure and<17:17:44.700> organized<17:17:45.360> into<17:17:45.720> a<17:17:45.956> password<17:17:46.160> well<17:17:47.160> I 17:17:47.630 --> 17:17:47.640 align:start position:0% and organized into a password well I 17:17:47.640 --> 17:17:50.210 align:start position:0% and organized into a password well I could<17:17:47.820> replace<17:17:48.240> the<17:17:48.720> S<17:17:48.900> with<17:17:49.140> fives 17:17:50.210 --> 17:17:50.220 align:start position:0% could replace the S with fives 17:17:50.220 --> 17:17:54.830 align:start position:0% could replace the S with fives I<17:17:50.756> could<17:17:50.880> replace<17:17:51.060> the<17:17:51.360> ease<17:17:51.660> with<17:17:51.956> threes 17:17:54.830 --> 17:17:54.840 align:start position:0% 17:17:54.840 --> 17:17:57.350 align:start position:0% I<17:17:55.436> can<17:17:55.616> replace<17:17:55.860> the<17:17:56.456> A's<17:17:56.820> with<17:17:57.116> and 17:17:57.350 --> 17:17:57.360 align:start position:0% I can replace the A's with and 17:17:57.360 --> 17:18:00.650 align:start position:0% I can replace the A's with and ampersands 17:18:00.650 --> 17:18:00.660 align:start position:0% 17:18:00.660 --> 17:18:04.850 align:start position:0% and<17:18:01.140> so<17:18:01.320> on<17:18:01.560> and<17:18:01.980> so<17:18:02.160> forth 17:18:04.850 --> 17:18:04.860 align:start position:0% 17:18:04.860 --> 17:18:07.370 align:start position:0% even<17:18:05.400> an<17:18:05.700> I<17:18:05.936> replace<17:18:06.540> that<17:18:06.900> with<17:18:07.200> a 17:18:07.370 --> 17:18:07.380 align:start position:0% even an I replace that with a 17:18:07.380 --> 17:18:12.710 align:start position:0% even an I replace that with a exclamation<17:18:07.980> point<17:18:08.160> or<17:18:08.456> the<17:18:08.580> number<17:18:08.756> one 17:18:12.710 --> 17:18:12.720 align:start position:0% 17:18:12.720 --> 17:18:15.230 align:start position:0% and<17:18:13.020> voila<17:18:13.436> I've<17:18:13.860> just<17:18:14.040> created<17:18:14.400> what<17:18:14.820> looks 17:18:15.230 --> 17:18:15.240 align:start position:0% and voila I've just created what looks 17:18:15.240 --> 17:18:16.850 align:start position:0% and voila I've just created what looks to<17:18:15.360> the<17:18:15.660> plane<17:18:15.956> eye 17:18:16.850 --> 17:18:16.860 align:start position:0% to the plane eye 17:18:16.860 --> 17:18:21.170 align:start position:0% to the plane eye as<17:18:17.520> a<17:18:17.936> pretty<17:18:18.116> s<17:18:18.720> complex<17:18:19.560> password<17:18:19.980> that<17:18:20.936> a 17:18:21.170 --> 17:18:21.180 align:start position:0% as a pretty s complex password that a 17:18:21.180 --> 17:18:22.490 align:start position:0% as a pretty s complex password that a computer<17:18:21.296> wouldn't<17:18:21.596> be<17:18:21.840> able<17:18:21.956> to<17:18:22.140> necessarily 17:18:22.490 --> 17:18:22.500 align:start position:0% computer wouldn't be able to necessarily 17:18:22.500 --> 17:18:25.370 align:start position:0% computer wouldn't be able to necessarily break<17:18:22.796> but<17:18:23.756> you<17:18:24.360> remember<17:18:24.540> it<17:18:24.840> because<17:18:25.020> you've 17:18:25.370 --> 17:18:25.380 align:start position:0% break but you remember it because you've 17:18:25.380 --> 17:18:26.926 align:start position:0% break but you remember it because you've come<17:18:25.500> up<17:18:25.616> with<17:18:25.740> your<17:18:25.916> own<17:18:26.040> code<17:18:26.276> of<17:18:26.580> how<17:18:26.820> you're 17:18:26.926 --> 17:18:26.936 align:start position:0% come up with your own code of how you're 17:18:26.936 --> 17:18:29.446 align:start position:0% come up with your own code of how you're going<17:18:27.116> to<17:18:27.180> replace<17:18:27.416> certain<17:18:28.380> symbols<17:18:28.980> and 17:18:29.446 --> 17:18:29.456 align:start position:0% going to replace certain symbols and 17:18:29.456 --> 17:18:31.850 align:start position:0% going to replace certain symbols and numbers<17:18:29.640> and<17:18:30.596> it<17:18:30.840> wouldn't<17:18:30.956> hurt<17:18:31.200> to<17:18:31.500> throw<17:18:31.616> in 17:18:31.850 --> 17:18:31.860 align:start position:0% numbers and it wouldn't hurt to throw in 17:18:31.860 --> 17:18:35.086 align:start position:0% numbers and it wouldn't hurt to throw in a<17:18:32.220> couple<17:18:32.360> uppercase<17:18:33.360> letters<17:18:33.900> there<17:18:34.080> as<17:18:34.320> well 17:18:35.086 --> 17:18:35.096 align:start position:0% a couple uppercase letters there as well 17:18:35.096 --> 17:18:37.010 align:start position:0% a couple uppercase letters there as well now<17:18:35.580> with<17:18:35.820> virtual<17:18:36.180> private<17:18:36.596> networks 17:18:37.010 --> 17:18:37.020 align:start position:0% now with virtual private networks 17:18:37.020 --> 17:18:38.630 align:start position:0% now with virtual private networks there's<17:18:37.256> a<17:18:37.500> lot<17:18:37.616> that<17:18:37.796> can<17:18:37.980> go<17:18:38.096> wrong<17:18:38.276> security 17:18:38.630 --> 17:18:38.640 align:start position:0% there's a lot that can go wrong security 17:18:38.640 --> 17:18:41.330 align:start position:0% there's a lot that can go wrong security wise<17:18:39.180> because<17:18:39.660> it<17:18:39.956> travels<17:18:40.320> over<17:18:40.680> a<17:18:41.220> public 17:18:41.330 --> 17:18:41.340 align:start position:0% wise because it travels over a public 17:18:41.340 --> 17:18:43.246 align:start position:0% wise because it travels over a public network<17:18:41.640> in<17:18:41.936> order<17:18:42.116> to<17:18:42.296> collect<17:18:42.540> connect<17:18:42.776> to 17:18:43.246 --> 17:18:43.256 align:start position:0% network in order to collect connect to 17:18:43.256 --> 17:18:45.470 align:start position:0% network in order to collect connect to your<17:18:43.436> local<17:18:43.616> land<17:18:43.980> and<17:18:44.640> the<17:18:44.756> users<17:18:45.000> remotely 17:18:45.470 --> 17:18:45.480 align:start position:0% your local land and the users remotely 17:18:45.480 --> 17:18:47.390 align:start position:0% your local land and the users remotely connect<17:18:45.720> an<17:18:46.380> attack<17:18:46.560> can<17:18:46.860> happen<17:18:47.040> from 17:18:47.390 --> 17:18:47.400 align:start position:0% connect an attack can happen from 17:18:47.400 --> 17:18:49.670 align:start position:0% connect an attack can happen from literally<17:18:47.820> anywhere<17:18:48.416> so<17:18:49.140> in<17:18:49.256> order<17:18:49.380> to<17:18:49.560> help 17:18:49.670 --> 17:18:49.680 align:start position:0% literally anywhere so in order to help 17:18:49.680 --> 17:18:51.890 align:start position:0% literally anywhere so in order to help stop<17:18:49.916> attacks<17:18:50.520> the<17:18:50.700> admin<17:18:51.116> needs<17:18:51.416> to<17:18:51.540> require 17:18:51.890 --> 17:18:51.900 align:start position:0% stop attacks the admin needs to require 17:18:51.900 --> 17:18:54.586 align:start position:0% stop attacks the admin needs to require remote<17:18:52.380> users<17:18:52.980> to<17:18:53.456> have<17:18:53.700> multiple<17:18:54.116> points<17:18:54.540> of 17:18:54.586 --> 17:18:54.596 align:start position:0% remote users to have multiple points of 17:18:54.596 --> 17:18:58.010 align:start position:0% remote users to have multiple points of identification<17:18:55.456> remember<17:18:56.456> in<17:18:57.240> a<17:18:57.416> plus<17:18:57.596> we 17:18:58.010 --> 17:18:58.020 align:start position:0% identification remember in a plus we 17:18:58.020 --> 17:19:04.370 align:start position:0% identification remember in a plus we talked<17:18:58.320> about<17:18:58.380> having<17:18:58.796> multi-authentication 17:19:04.370 --> 17:19:04.380 align:start position:0% 17:19:04.380 --> 17:19:06.170 align:start position:0% and<17:19:04.860> remember<17:19:04.980> authentication<17:19:05.756> we<17:19:06.060> have 17:19:06.170 --> 17:19:06.180 align:start position:0% and remember authentication we have 17:19:06.180 --> 17:19:07.606 align:start position:0% and remember authentication we have three<17:19:06.416> different<17:19:06.596> things 17:19:07.606 --> 17:19:07.616 align:start position:0% three different things 17:19:07.616 --> 17:19:10.246 align:start position:0% three different things something<17:19:08.220> you<17:19:08.520> know 17:19:10.246 --> 17:19:10.256 align:start position:0% something you know 17:19:10.256 --> 17:19:12.406 align:start position:0% something you know something<17:19:10.860> you<17:19:11.160> have 17:19:12.406 --> 17:19:12.416 align:start position:0% something you have 17:19:12.416 --> 17:19:15.406 align:start position:0% something you have it's<17:19:12.900> something<17:19:13.200> you<17:19:13.740> are 17:19:15.406 --> 17:19:15.416 align:start position:0% it's something you are 17:19:15.416 --> 17:19:17.810 align:start position:0% it's something you are so<17:19:15.956> if<17:19:16.320> we're<17:19:16.380> going<17:19:16.616> to<17:19:16.680> use<17:19:16.860> multiple<17:19:17.456> forms 17:19:17.810 --> 17:19:17.820 align:start position:0% so if we're going to use multiple forms 17:19:17.820 --> 17:19:19.630 align:start position:0% so if we're going to use multiple forms of<17:19:17.936> identification 17:19:19.630 --> 17:19:19.640 align:start position:0% of identification 17:19:19.640 --> 17:19:22.130 align:start position:0% of identification maybe<17:19:20.640> one<17:19:20.936> thing<17:19:21.060> we<17:19:21.240> want<17:19:21.360> to<17:19:21.480> do<17:19:21.596> is<17:19:21.720> have<17:19:21.956> a 17:19:22.130 --> 17:19:22.140 align:start position:0% maybe one thing we want to do is have a 17:19:22.140 --> 17:19:24.050 align:start position:0% maybe one thing we want to do is have a standard<17:19:22.380> username<17:19:22.796> and<17:19:22.916> password<17:19:23.160> and<17:19:23.880> also 17:19:24.050 --> 17:19:24.060 align:start position:0% standard username and password and also 17:19:24.060 --> 17:19:26.030 align:start position:0% standard username and password and also a<17:19:24.240> pin<17:19:24.540> or<17:19:24.720> security<17:19:24.900> question<17:19:25.436> they<17:19:25.860> would 17:19:26.030 --> 17:19:26.040 align:start position:0% a pin or security question they would 17:19:26.040 --> 17:19:27.946 align:start position:0% a pin or security question they would have<17:19:26.220> to<17:19:26.456> answer<17:19:26.700> these<17:19:27.416> both<17:19:27.540> fall<17:19:27.720> under 17:19:27.946 --> 17:19:27.956 align:start position:0% have to answer these both fall under 17:19:27.956 --> 17:19:29.746 align:start position:0% have to answer these both fall under something<17:19:28.256> you<17:19:28.500> know<17:19:28.680> we<17:19:29.276> could<17:19:29.400> also<17:19:29.640> give 17:19:29.746 --> 17:19:29.756 align:start position:0% something you know we could also give 17:19:29.756 --> 17:19:31.786 align:start position:0% something you know we could also give them<17:19:29.936> a<17:19:30.180> fob<17:19:30.480> key<17:19:30.660> that<17:19:31.020> has<17:19:31.140> a<17:19:31.436> rotating 17:19:31.786 --> 17:19:31.796 align:start position:0% them a fob key that has a rotating 17:19:31.796 --> 17:19:33.286 align:start position:0% them a fob key that has a rotating password<17:19:32.160> on<17:19:32.520> it<17:19:32.640> this<17:19:32.880> would<17:19:33.060> be<17:19:33.116> something 17:19:33.286 --> 17:19:33.296 align:start position:0% password on it this would be something 17:19:33.296 --> 17:19:35.870 align:start position:0% password on it this would be something they<17:19:33.720> have<17:19:33.956> it<17:19:34.560> makes<17:19:34.740> it<17:19:34.916> more<17:19:35.096> difficult<17:19:35.400> if 17:19:35.870 --> 17:19:35.880 align:start position:0% they have it makes it more difficult if 17:19:35.880 --> 17:19:38.086 align:start position:0% they have it makes it more difficult if I<17:19:36.000> use<17:19:36.240> multiple<17:19:36.956> forms<17:19:37.500> of<17:19:37.916> this 17:19:38.086 --> 17:19:38.096 align:start position:0% I use multiple forms of this 17:19:38.096 --> 17:19:41.266 align:start position:0% I use multiple forms of this authentication<17:19:38.700> and<17:19:39.596> that<17:19:39.840> way<17:19:40.096> it's<17:19:41.096> not 17:19:41.266 --> 17:19:41.276 align:start position:0% authentication and that way it's not 17:19:41.276 --> 17:19:42.830 align:start position:0% authentication and that way it's not just<17:19:41.400> things<17:19:41.640> that<17:19:42.000> are<17:19:42.240> written<17:19:42.480> down<17:19:42.596> or 17:19:42.830 --> 17:19:42.840 align:start position:0% just things that are written down or 17:19:42.840 --> 17:19:45.050 align:start position:0% just things that are written down or known<17:19:43.020> it's<17:19:43.436> also<17:19:43.740> things<17:19:43.916> that<17:19:44.096> are<17:19:44.276> have<17:19:44.456> had 17:19:45.050 --> 17:19:45.060 align:start position:0% known it's also things that are have had 17:19:45.060 --> 17:19:47.630 align:start position:0% known it's also things that are have had or<17:19:45.776> even<17:19:46.020> better<17:19:46.200> things<17:19:46.616> that<17:19:46.916> you<17:19:47.096> are<17:19:47.276> for 17:19:47.630 --> 17:19:47.640 align:start position:0% or even better things that you are for 17:19:47.640 --> 17:19:49.606 align:start position:0% or even better things that you are for instance<17:19:47.820> a<17:19:48.000> retinal<17:19:48.296> scan<17:19:48.660> fingerprint 17:19:49.606 --> 17:19:49.616 align:start position:0% instance a retinal scan fingerprint 17:19:49.616 --> 17:19:51.350 align:start position:0% instance a retinal scan fingerprint voice<17:19:50.160> recognition 17:19:51.350 --> 17:19:51.360 align:start position:0% voice recognition 17:19:51.360 --> 17:19:53.926 align:start position:0% voice recognition Etc<17:19:51.480> the<17:19:52.320> point<17:19:52.500> is<17:19:52.680> the<17:19:53.040> more<17:19:53.276> of<17:19:53.400> these<17:19:53.700> you 17:19:53.926 --> 17:19:53.936 align:start position:0% Etc the point is the more of these you 17:19:53.936 --> 17:19:57.766 align:start position:0% Etc the point is the more of these you have<17:19:54.436> the<17:19:55.436> easier<17:19:55.916> it<17:19:56.220> is<17:19:56.340> for<17:19:57.180> you<17:19:57.416> to<17:19:57.596> keep 17:19:57.766 --> 17:19:57.776 align:start position:0% have the easier it is for you to keep 17:19:57.776 --> 17:20:01.010 align:start position:0% have the easier it is for you to keep your<17:19:57.956> stuff<17:19:58.140> secure<17:19:58.560> however<17:19:59.220> it's<17:19:59.756> also<17:20:00.180> more 17:20:01.010 --> 17:20:01.020 align:start position:0% your stuff secure however it's also more 17:20:01.020 --> 17:20:03.106 align:start position:0% your stuff secure however it's also more difficult<17:20:01.380> to<17:20:02.220> log<17:20:02.340> in<17:20:02.520> and<17:20:02.700> it's<17:20:02.880> going<17:20:03.000> to 17:20:03.106 --> 17:20:03.116 align:start position:0% difficult to log in and it's going to 17:20:03.116 --> 17:20:05.086 align:start position:0% difficult to log in and it's going to take<17:20:03.180> more<17:20:03.480> time<17:20:03.720> so<17:20:04.320> again<17:20:04.436> we're<17:20:04.796> dealing 17:20:05.086 --> 17:20:05.096 align:start position:0% take more time so again we're dealing 17:20:05.096 --> 17:20:06.406 align:start position:0% take more time so again we're dealing with<17:20:05.400> time 17:20:06.406 --> 17:20:06.416 align:start position:0% with time 17:20:06.416 --> 17:20:08.510 align:start position:0% with time and<17:20:07.140> ease 17:20:08.510 --> 17:20:08.520 align:start position:0% and ease 17:20:08.520 --> 17:20:11.086 align:start position:0% and ease versus<17:20:09.240> security<17:20:09.956> and<17:20:10.380> we<17:20:10.500> have<17:20:10.616> to<17:20:10.740> find<17:20:10.916> the 17:20:11.086 --> 17:20:11.096 align:start position:0% versus security and we have to find the 17:20:11.096 --> 17:20:12.170 align:start position:0% versus security and we have to find the right<17:20:11.220> balance 17:20:12.170 --> 17:20:12.180 align:start position:0% right balance 17:20:12.180 --> 17:20:13.730 align:start position:0% right balance because<17:20:12.540> we<17:20:12.776> don't<17:20:12.840> want<17:20:12.956> people<17:20:13.200> to<17:20:13.380> get<17:20:13.560> so 17:20:13.730 --> 17:20:13.740 align:start position:0% because we don't want people to get so 17:20:13.740 --> 17:20:15.946 align:start position:0% because we don't want people to get so turned<17:20:14.160> off<17:20:14.276> by<17:20:15.180> all<17:20:15.480> the<17:20:15.596> heightened 17:20:15.946 --> 17:20:15.956 align:start position:0% turned off by all the heightened 17:20:15.956 --> 17:20:17.870 align:start position:0% turned off by all the heightened security<17:20:16.200> that<17:20:16.980> then<17:20:17.096> they<17:20:17.276> can't<17:20:17.400> use<17:20:17.640> our 17:20:17.870 --> 17:20:17.880 align:start position:0% security that then they can't use our 17:20:17.880 --> 17:20:18.766 align:start position:0% security that then they can't use our product 17:20:18.766 --> 17:20:18.776 align:start position:0% product 17:20:18.776 --> 17:20:20.810 align:start position:0% product it<17:20:19.200> also<17:20:19.436> might<17:20:19.560> be<17:20:19.680> necessary<17:20:19.980> to<17:20:20.220> have<17:20:20.456> a 17:20:20.810 --> 17:20:20.820 align:start position:0% it also might be necessary to have a 17:20:20.820 --> 17:20:22.606 align:start position:0% it also might be necessary to have a firewall<17:20:21.296> between<17:20:21.660> the<17:20:21.956> VPN<17:20:22.320> and<17:20:22.500> the 17:20:22.606 --> 17:20:22.616 align:start position:0% firewall between the VPN and the 17:20:22.616 --> 17:20:24.946 align:start position:0% firewall between the VPN and the physical<17:20:22.740> Network<17:20:23.160> the<17:20:24.000> firewall<17:20:24.416> acts<17:20:24.776> as<17:20:24.840> a 17:20:24.946 --> 17:20:24.956 align:start position:0% physical Network the firewall acts as a 17:20:24.956 --> 17:20:26.690 align:start position:0% physical Network the firewall acts as a sort<17:20:25.140> of<17:20:25.200> last<17:20:25.436> line<17:20:25.680> of<17:20:25.916> defense<17:20:26.276> and<17:20:26.520> if 17:20:26.690 --> 17:20:26.700 align:start position:0% sort of last line of defense and if 17:20:26.700 --> 17:20:28.786 align:start position:0% sort of last line of defense and if somehow<17:20:27.060> an<17:20:27.296> attacker<17:20:27.956> manages<17:20:28.320> to<17:20:28.560> get 17:20:28.786 --> 17:20:28.796 align:start position:0% somehow an attacker manages to get 17:20:28.796 --> 17:20:31.310 align:start position:0% somehow an attacker manages to get through<17:20:29.040> the<17:20:29.580> points<17:20:29.880> of<17:20:29.936> identification<17:20:30.540> the 17:20:31.310 --> 17:20:31.320 align:start position:0% through the points of identification the 17:20:31.320 --> 17:20:32.926 align:start position:0% through the points of identification the firewall<17:20:31.680> might<17:20:31.916> be<17:20:32.040> able<17:20:32.160> to<17:20:32.276> stop<17:20:32.456> them<17:20:32.700> from 17:20:32.926 --> 17:20:32.936 align:start position:0% firewall might be able to stop them from 17:20:32.936 --> 17:20:34.670 align:start position:0% firewall might be able to stop them from connecting<17:20:33.360> to<17:20:33.596> the<17:20:33.776> network<17:20:33.900> based<17:20:34.380> on<17:20:34.436> where 17:20:34.670 --> 17:20:34.680 align:start position:0% connecting to the network based on where 17:20:34.680 --> 17:20:35.926 align:start position:0% connecting to the network based on where they<17:20:34.796> are<17:20:34.980> the<17:20:35.160> information<17:20:35.340> they're<17:20:35.756> trying 17:20:35.926 --> 17:20:35.936 align:start position:0% they are the information they're trying 17:20:35.936 --> 17:20:38.210 align:start position:0% they are the information they're trying to<17:20:36.116> transmit<17:20:36.596> if<17:20:37.256> they're<17:20:37.380> using<17:20:37.680> an<17:20:37.916> unknown 17:20:38.210 --> 17:20:38.220 align:start position:0% to transmit if they're using an unknown 17:20:38.220 --> 17:20:39.830 align:start position:0% to transmit if they're using an unknown or<17:20:38.520> untrusted 17:20:39.830 --> 17:20:39.840 align:start position:0% or untrusted 17:20:39.840 --> 17:20:42.406 align:start position:0% or untrusted IP<17:20:40.680> address<17:20:40.860> the<17:20:41.456> firewall<17:20:41.820> may<17:20:42.060> be<17:20:42.180> able<17:20:42.296> to 17:20:42.406 --> 17:20:42.416 align:start position:0% IP address the firewall may be able to 17:20:42.416 --> 17:20:44.330 align:start position:0% IP address the firewall may be able to stop<17:20:42.660> them<17:20:42.900> before<17:20:43.140> they<17:20:43.560> connect<17:20:43.680> the<17:20:44.160> local 17:20:44.330 --> 17:20:44.340 align:start position:0% stop them before they connect the local 17:20:44.340 --> 17:20:46.490 align:start position:0% stop them before they connect the local area<17:20:44.580> network 17:20:46.490 --> 17:20:46.500 align:start position:0% area network 17:20:46.500 --> 17:20:48.530 align:start position:0% area network now<17:20:46.916> it's<17:20:47.096> often<17:20:47.400> the<17:20:47.520> case<17:20:47.640> that<17:20:47.936> users<17:20:48.296> have 17:20:48.530 --> 17:20:48.540 align:start position:0% now it's often the case that users have 17:20:48.540 --> 17:20:50.510 align:start position:0% now it's often the case that users have to<17:20:48.776> access<17:20:48.956> things<17:20:49.436> that<17:20:49.740> they<17:20:49.916> have<17:20:50.220> no 17:20:50.510 --> 17:20:50.520 align:start position:0% to access things that they have no 17:20:50.520 --> 17:20:52.730 align:start position:0% to access things that they have no business<17:20:50.756> accessing<17:20:51.596> for<17:20:52.256> example<17:20:52.500> someone 17:20:52.730 --> 17:20:52.740 align:start position:0% business accessing for example someone 17:20:52.740 --> 17:20:54.106 align:start position:0% business accessing for example someone in<17:20:52.980> the<17:20:53.040> graphic<17:20:53.340> design<17:20:53.520> part<17:20:53.880> of<17:20:54.060> the 17:20:54.106 --> 17:20:54.116 align:start position:0% in the graphic design part of the 17:20:54.116 --> 17:20:55.786 align:start position:0% in the graphic design part of the company<17:20:54.296> has<17:20:54.596> no<17:20:54.840> need<17:20:55.080> to<17:20:55.320> access<17:20:55.436> the 17:20:55.786 --> 17:20:55.796 align:start position:0% company has no need to access the 17:20:55.796 --> 17:20:57.650 align:start position:0% company has no need to access the accounting<17:20:56.160> records<17:20:56.520> of<17:20:56.640> the<17:20:56.756> company<17:20:56.936> and 17:20:57.650 --> 17:20:57.660 align:start position:0% accounting records of the company and 17:20:57.660 --> 17:20:59.746 align:start position:0% accounting records of the company and sometimes<17:20:58.020> however<17:20:58.380> users<17:20:59.160> are<17:20:59.340> given 17:20:59.746 --> 17:20:59.756 align:start position:0% sometimes however users are given 17:20:59.756 --> 17:21:01.550 align:start position:0% sometimes however users are given permissions<17:21:00.296> to<17:21:00.596> access<17:21:00.720> data<17:21:01.256> like<17:21:01.380> this 17:21:01.550 --> 17:21:01.560 align:start position:0% permissions to access data like this 17:21:01.560 --> 17:21:03.286 align:start position:0% permissions to access data like this simply<17:21:01.860> because<17:21:02.040> it's<17:21:02.340> overlooked<17:21:02.936> by<17:21:03.116> the 17:21:03.286 --> 17:21:03.296 align:start position:0% simply because it's overlooked by the 17:21:03.296 --> 17:21:05.446 align:start position:0% simply because it's overlooked by the administrator<17:21:03.776> so<17:21:04.500> this<17:21:04.616> is<17:21:04.796> a<17:21:04.980> huge<17:21:05.276> security 17:21:05.446 --> 17:21:05.456 align:start position:0% administrator so this is a huge security 17:21:05.456 --> 17:21:07.606 align:start position:0% administrator so this is a huge security issue<17:21:06.000> and<17:21:06.116> one<17:21:06.360> that's<17:21:06.480> easy<17:21:06.776> to<17:21:07.020> fix<17:21:07.200> and 17:21:07.606 --> 17:21:07.616 align:start position:0% issue and one that's easy to fix and 17:21:07.616 --> 17:21:09.890 align:start position:0% issue and one that's easy to fix and needs<17:21:07.916> to<17:21:08.040> be<17:21:08.096> looked<17:21:08.400> after<17:21:08.456> with<17:21:08.756> care<17:21:09.060> the 17:21:09.890 --> 17:21:09.900 align:start position:0% needs to be looked after with care the 17:21:09.900 --> 17:21:11.926 align:start position:0% needs to be looked after with care the admin<17:21:10.256> should<17:21:10.500> only<17:21:10.740> make<17:21:11.276> sure<17:21:11.456> that<17:21:11.700> users 17:21:11.926 --> 17:21:11.936 align:start position:0% admin should only make sure that users 17:21:11.936 --> 17:21:14.926 align:start position:0% admin should only make sure that users are<17:21:12.060> given<17:21:12.416> only<17:21:13.200> access<17:21:13.680> to<17:21:14.040> the<17:21:14.276> data<17:21:14.640> they 17:21:14.926 --> 17:21:14.936 align:start position:0% are given only access to the data they 17:21:14.936 --> 17:21:17.390 align:start position:0% are given only access to the data they need<17:21:15.180> to<17:21:15.360> do<17:21:15.540> their<17:21:15.776> job<17:21:15.956> this<17:21:16.796> is<17:21:17.040> what<17:21:17.220> we 17:21:17.390 --> 17:21:17.400 align:start position:0% need to do their job this is what we 17:21:17.400 --> 17:21:22.246 align:start position:0% need to do their job this is what we call<17:21:17.720> the<17:21:18.720> principle<17:21:19.140> of<17:21:19.980> least 17:21:22.246 --> 17:21:22.256 align:start position:0% 17:21:22.256 --> 17:21:25.550 align:start position:0% privilege<17:21:23.160> now<17:21:23.820> this<17:21:24.060> change<17:21:24.240> can<17:21:24.596> be<17:21:24.776> made<17:21:25.020> by 17:21:25.550 --> 17:21:25.560 align:start position:0% privilege now this change can be made by 17:21:25.560 --> 17:21:28.730 align:start position:0% privilege now this change can be made by password<17:21:25.796> protecting 17:21:28.730 --> 17:21:28.740 align:start position:0% 17:21:28.740 --> 17:21:31.070 align:start position:0% or<17:21:29.400> it<17:21:29.700> can<17:21:29.820> be<17:21:30.000> made 17:21:31.070 --> 17:21:31.080 align:start position:0% or it can be made 17:21:31.080 --> 17:21:33.406 align:start position:0% or it can be made using<17:21:31.860> group<17:21:32.160> policy 17:21:33.406 --> 17:21:33.416 align:start position:0% using group policy 17:21:33.416 --> 17:21:36.586 align:start position:0% using group policy meaning<17:21:34.020> that<17:21:34.380> we<17:21:34.560> have<17:21:34.680> an<17:21:34.796> Accounting<17:21:35.220> Group 17:21:36.586 --> 17:21:36.596 align:start position:0% meaning that we have an Accounting Group 17:21:36.596 --> 17:21:39.470 align:start position:0% meaning that we have an Accounting Group and<17:21:37.140> we<17:21:37.436> have<17:21:37.740> a<17:21:38.276> Marketing<17:21:38.820> Group<17:21:39.000> if<17:21:39.360> you're 17:21:39.470 --> 17:21:39.480 align:start position:0% and we have a Marketing Group if you're 17:21:39.480 --> 17:21:41.446 align:start position:0% and we have a Marketing Group if you're placed<17:21:39.840> into<17:21:39.900> one<17:21:40.200> of<17:21:40.256> those<17:21:40.320> groups<17:21:40.860> then 17:21:41.446 --> 17:21:41.456 align:start position:0% placed into one of those groups then 17:21:41.456 --> 17:21:44.446 align:start position:0% placed into one of those groups then you're<17:21:41.756> not<17:21:41.936> going<17:21:42.060> to<17:21:42.180> be<17:21:42.296> able<17:21:42.480> to<17:21:43.040> uh<17:21:44.040> access 17:21:44.446 --> 17:21:44.456 align:start position:0% you're not going to be able to uh access 17:21:44.456 --> 17:21:46.426 align:start position:0% you're not going to be able to uh access anything<17:21:44.880> except<17:21:45.360> for<17:21:45.480> what<17:21:45.720> your<17:21:45.900> group<17:21:46.080> has 17:21:46.426 --> 17:21:46.436 align:start position:0% anything except for what your group has 17:21:46.436 --> 17:21:48.650 align:start position:0% anything except for what your group has access<17:21:46.680> to 17:21:48.650 --> 17:21:48.660 align:start position:0% access to 17:21:48.660 --> 17:21:50.086 align:start position:0% access to now<17:21:49.020> the<17:21:49.200> other<17:21:49.256> thing<17:21:49.436> we<17:21:49.616> want<17:21:49.740> to<17:21:49.860> do<17:21:49.916> is 17:21:50.086 --> 17:21:50.096 align:start position:0% now the other thing we want to do is 17:21:50.096 --> 17:21:52.426 align:start position:0% now the other thing we want to do is make<17:21:50.400> sure<17:21:50.640> to<17:21:50.936> clean<17:21:51.116> up<17:21:51.296> inactive<17:21:51.900> accounts 17:21:52.426 --> 17:21:52.436 align:start position:0% make sure to clean up inactive accounts 17:21:52.436 --> 17:21:54.890 align:start position:0% make sure to clean up inactive accounts when<17:21:53.096> a<17:21:53.276> worker<17:21:53.580> leaves<17:21:54.000> the<17:21:54.240> company<17:21:54.416> the 17:21:54.890 --> 17:21:54.900 align:start position:0% when a worker leaves the company the 17:21:54.900 --> 17:21:56.990 align:start position:0% when a worker leaves the company the first<17:21:55.080> thing<17:21:55.320> the<17:21:55.500> admin<17:21:55.796> needs<17:21:56.096> to<17:21:56.160> do<17:21:56.340> is<17:21:56.820> to 17:21:56.990 --> 17:21:57.000 align:start position:0% first thing the admin needs to do is to 17:21:57.000 --> 17:21:58.370 align:start position:0% first thing the admin needs to do is to change<17:21:57.180> the<17:21:57.416> password<17:21:57.540> to<17:21:57.900> the<17:21:58.020> user's 17:21:58.370 --> 17:21:58.380 align:start position:0% change the password to the user's 17:21:58.380 --> 17:22:01.490 align:start position:0% change the password to the user's account<17:21:58.500> or<17:21:59.400> what<17:21:59.820> we<17:21:59.936> call<17:22:00.256> deactivate<17:22:01.256> the 17:22:01.490 --> 17:22:01.500 align:start position:0% account or what we call deactivate the 17:22:01.500 --> 17:22:03.530 align:start position:0% account or what we call deactivate the account<17:22:01.680> it'll<17:22:02.456> be<17:22:02.520> a<17:22:02.640> very<17:22:02.756> bad<17:22:02.936> thing<17:22:03.116> if<17:22:03.360> a 17:22:03.530 --> 17:22:03.540 align:start position:0% account it'll be a very bad thing if a 17:22:03.540 --> 17:22:05.630 align:start position:0% account it'll be a very bad thing if a for<17:22:03.720> former<17:22:04.256> employee<17:22:04.680> were<17:22:04.916> to<17:22:05.096> access<17:22:05.276> the 17:22:05.630 --> 17:22:05.640 align:start position:0% for former employee were to access the 17:22:05.640 --> 17:22:07.550 align:start position:0% for former employee were to access the company's<17:22:06.000> files<17:22:06.416> and<17:22:06.660> who<17:22:07.080> knows<17:22:07.256> what<17:22:07.436> they 17:22:07.550 --> 17:22:07.560 align:start position:0% company's files and who knows what they 17:22:07.560 --> 17:22:08.990 align:start position:0% company's files and who knows what they could<17:22:07.680> do<17:22:07.796> with<17:22:07.980> those<17:22:08.160> especially<17:22:08.640> if<17:22:08.820> they 17:22:08.990 --> 17:22:09.000 align:start position:0% could do with those especially if they 17:22:09.000 --> 17:22:11.086 align:start position:0% could do with those especially if they were<17:22:09.180> fired<17:22:09.596> so<17:22:10.140> once<17:22:10.436> the<17:22:10.500> passwords<17:22:10.916> has 17:22:11.086 --> 17:22:11.096 align:start position:0% were fired so once the passwords has 17:22:11.096 --> 17:22:12.586 align:start position:0% were fired so once the passwords has been<17:22:11.220> changed<17:22:11.580> there's<17:22:11.820> no<17:22:12.000> way<17:22:12.116> for<17:22:12.296> them<17:22:12.360> to 17:22:12.586 --> 17:22:12.596 align:start position:0% been changed there's no way for them to 17:22:12.596 --> 17:22:14.330 align:start position:0% been changed there's no way for them to access<17:22:12.720> the<17:22:13.140> account<17:22:13.320> but<17:22:13.980> it's<17:22:14.160> not 17:22:14.330 --> 17:22:14.340 align:start position:0% access the account but it's not 17:22:14.340 --> 17:22:16.550 align:start position:0% access the account but it's not necessary<17:22:14.880> for<17:22:15.296> the<17:22:15.540> admin<17:22:16.020> to<17:22:16.200> delete<17:22:16.320> the 17:22:16.550 --> 17:22:16.560 align:start position:0% necessary for the admin to delete the 17:22:16.560 --> 17:22:18.830 align:start position:0% necessary for the admin to delete the account<17:22:16.680> right<17:22:17.040> away<17:22:17.220> if<17:22:17.936> the<17:22:18.180> employee<17:22:18.660> was 17:22:18.830 --> 17:22:18.840 align:start position:0% account right away if the employee was 17:22:18.840 --> 17:22:20.446 align:start position:0% account right away if the employee was to<17:22:19.020> come<17:22:19.140> back<17:22:19.320> to<17:22:19.436> the<17:22:19.616> company<17:22:19.796> soon<17:22:20.220> after 17:22:20.446 --> 17:22:20.456 align:start position:0% to come back to the company soon after 17:22:20.456 --> 17:22:21.946 align:start position:0% to come back to the company soon after and<17:22:20.700> needed<17:22:21.000> to<17:22:21.060> access<17:22:21.180> their<17:22:21.416> old<17:22:21.540> files 17:22:21.946 --> 17:22:21.956 align:start position:0% and needed to access their old files 17:22:21.956 --> 17:22:23.690 align:start position:0% and needed to access their old files they<17:22:22.320> could<17:22:22.500> be<17:22:22.616> given<17:22:22.860> a<17:22:23.040> temporary<17:22:23.400> password 17:22:23.690 --> 17:22:23.700 align:start position:0% they could be given a temporary password 17:22:23.700 --> 17:22:25.550 align:start position:0% they could be given a temporary password and<17:22:24.116> then<17:22:24.296> monitored<17:22:24.840> to<17:22:25.200> make<17:22:25.256> sure<17:22:25.380> they 17:22:25.550 --> 17:22:25.560 align:start position:0% and then monitored to make sure they 17:22:25.560 --> 17:22:28.130 align:start position:0% and then monitored to make sure they could<17:22:25.680> get<17:22:25.916> their<17:22:26.340> old<17:22:26.520> information<17:22:27.140> however 17:22:28.130 --> 17:22:28.140 align:start position:0% could get their old information however 17:22:28.140 --> 17:22:30.650 align:start position:0% could get their old information however if<17:22:28.680> an<17:22:28.860> account<17:22:29.040> has<17:22:29.340> been<17:22:29.520> inactive<17:22:30.240> for<17:22:30.540> a 17:22:30.650 --> 17:22:30.660 align:start position:0% if an account has been inactive for a 17:22:30.660 --> 17:22:33.470 align:start position:0% if an account has been inactive for a while<17:22:30.776> it<17:22:31.500> should<17:22:31.740> be<17:22:31.980> deleted<17:22:32.580> or 17:22:33.470 --> 17:22:33.480 align:start position:0% while it should be deleted or 17:22:33.480 --> 17:22:36.050 align:start position:0% while it should be deleted or discontinued<17:22:34.256> an<17:22:34.860> idle<17:22:35.160> account<17:22:35.340> is<17:22:35.756> really 17:22:36.050 --> 17:22:36.060 align:start position:0% discontinued an idle account is really 17:22:36.060 --> 17:22:37.426 align:start position:0% discontinued an idle account is really dangerous<17:22:36.480> thing<17:22:36.660> to<17:22:36.840> have<17:22:37.020> on<17:22:37.140> your<17:22:37.256> network 17:22:37.426 --> 17:22:37.436 align:start position:0% dangerous thing to have on your network 17:22:37.436 --> 17:22:39.710 align:start position:0% dangerous thing to have on your network if<17:22:37.980> an<17:22:38.160> attacker<17:22:38.520> is<17:22:38.700> about<17:22:38.820> to<17:22:39.060> access<17:22:39.360> this 17:22:39.710 --> 17:22:39.720 align:start position:0% if an attacker is about to access this 17:22:39.720 --> 17:22:41.266 align:start position:0% if an attacker is about to access this account<17:22:39.900> they<17:22:40.200> could<17:22:40.380> easily<17:22:40.740> slip<17:22:41.040> past 17:22:41.266 --> 17:22:41.276 align:start position:0% account they could easily slip past 17:22:41.276 --> 17:22:43.550 align:start position:0% account they could easily slip past unnoticed<17:22:42.060> on<17:22:42.116> the<17:22:42.296> network<17:22:42.416> until<17:22:43.200> something 17:22:43.550 --> 17:22:43.560 align:start position:0% unnoticed on the network until something 17:22:43.560 --> 17:22:45.170 align:start position:0% unnoticed on the network until something actually<17:22:43.916> happens<17:22:44.220> we<17:22:44.580> wouldn't<17:22:44.756> really<17:22:44.936> know 17:22:45.170 --> 17:22:45.180 align:start position:0% actually happens we wouldn't really know 17:22:45.180 --> 17:22:46.850 align:start position:0% actually happens we wouldn't really know that<17:22:45.360> there's<17:22:45.540> a<17:22:45.660> problem<17:22:45.900> so<17:22:46.560> in<17:22:46.616> order<17:22:46.796> to 17:22:46.850 --> 17:22:46.860 align:start position:0% that there's a problem so in order to 17:22:46.860 --> 17:22:48.050 align:start position:0% that there's a problem so in order to prevent<17:22:47.096> this<17:22:47.276> we<17:22:47.520> really<17:22:47.640> want<17:22:47.820> to<17:22:47.936> delete 17:22:48.050 --> 17:22:48.060 align:start position:0% prevent this we really want to delete 17:22:48.060 --> 17:22:50.690 align:start position:0% prevent this we really want to delete accounts<17:22:48.596> soon<17:22:49.320> as<17:22:49.796> the<17:22:49.980> users<17:22:50.220> do<17:22:50.400> not<17:22:50.580> need 17:22:50.690 --> 17:22:50.700 align:start position:0% accounts soon as the users do not need 17:22:50.700 --> 17:22:52.970 align:start position:0% accounts soon as the users do not need them<17:22:50.880> anymore<17:22:51.060> this<17:22:51.720> is<17:22:51.776> why<17:22:52.020> generally<17:22:52.436> HR 17:22:52.970 --> 17:22:52.980 align:start position:0% them anymore this is why generally HR 17:22:52.980 --> 17:22:54.946 align:start position:0% them anymore this is why generally HR and<17:22:53.160> IT<17:22:53.340> talk<17:22:53.700> to<17:22:53.880> one<17:22:54.000> another<17:22:54.180> so<17:22:54.660> we<17:22:54.776> can 17:22:54.946 --> 17:22:54.956 align:start position:0% and IT talk to one another so we can 17:22:54.956 --> 17:22:57.830 align:start position:0% and IT talk to one another so we can make<17:22:55.080> sure<17:22:55.320> once<17:22:55.860> we<17:22:56.040> let<17:22:56.400> a<17:22:56.756> person<17:22:57.180> go<17:22:57.540> or 17:22:57.830 --> 17:22:57.840 align:start position:0% make sure once we let a person go or 17:22:57.840 --> 17:23:00.530 align:start position:0% make sure once we let a person go or fire<17:22:58.020> someone<17:22:58.520> their<17:22:59.520> account<17:22:59.700> is<17:23:00.116> turned<17:23:00.416> off 17:23:00.530 --> 17:23:00.540 align:start position:0% fire someone their account is turned off 17:23:00.540 --> 17:23:02.510 align:start position:0% fire someone their account is turned off almost<17:23:00.776> immediately 17:23:02.510 --> 17:23:02.520 align:start position:0% almost immediately 17:23:02.520 --> 17:23:04.130 align:start position:0% almost immediately all<17:23:02.936> right<17:23:03.116> so<17:23:03.540> these<17:23:03.720> are<17:23:03.776> some<17:23:03.956> of<17:23:04.080> the 17:23:04.130 --> 17:23:04.140 align:start position:0% all right so these are some of the 17:23:04.140 --> 17:23:05.870 align:start position:0% all right so these are some of the fundamentals<17:23:04.796> we<17:23:05.040> talked<17:23:05.276> about<17:23:05.340> the 17:23:05.870 --> 17:23:05.880 align:start position:0% fundamentals we talked about the 17:23:05.880 --> 17:23:08.170 align:start position:0% fundamentals we talked about the necessity<17:23:06.360> of<17:23:06.540> network<17:23:06.776> security<17:23:07.140> remember 17:23:08.170 --> 17:23:08.180 align:start position:0% necessity of network security remember 17:23:08.180 --> 17:23:11.390 align:start position:0% necessity of network security remember data<17:23:09.180> can<17:23:09.956> sometimes<17:23:10.380> be<17:23:10.616> more<17:23:10.980> important 17:23:11.390 --> 17:23:11.400 align:start position:0% data can sometimes be more important 17:23:11.400 --> 17:23:13.850 align:start position:0% data can sometimes be more important than<17:23:11.880> money<17:23:12.180> because<17:23:12.840> it's<17:23:13.080> going<17:23:13.256> to<17:23:13.380> cost<17:23:13.560> a 17:23:13.850 --> 17:23:13.860 align:start position:0% than money because it's going to cost a 17:23:13.860 --> 17:23:16.070 align:start position:0% than money because it's going to cost a lot<17:23:13.916> of<17:23:14.096> money<17:23:14.340> in<17:23:14.936> order<17:23:15.000> to<17:23:15.296> recover<17:23:15.596> or<17:23:15.956> make 17:23:16.070 --> 17:23:16.080 align:start position:0% lot of money in order to recover or make 17:23:16.080 --> 17:23:18.350 align:start position:0% lot of money in order to recover or make up<17:23:16.256> for<17:23:16.500> the<17:23:16.616> loss<17:23:16.860> of<17:23:16.916> data<17:23:17.700> we<17:23:18.116> also 17:23:18.350 --> 17:23:18.360 align:start position:0% up for the loss of data we also 17:23:18.360 --> 17:23:19.786 align:start position:0% up for the loss of data we also identified<17:23:18.660> some<17:23:18.900> of<17:23:19.020> the<17:23:19.080> fundamentals<17:23:19.560> of<17:23:19.740> a 17:23:19.786 --> 17:23:19.796 align:start position:0% identified some of the fundamentals of a 17:23:19.796 --> 17:23:21.830 align:start position:0% identified some of the fundamentals of a secure<17:23:20.096> network<17:23:20.340> first<17:23:21.116> of<17:23:21.296> all<17:23:21.360> we<17:23:21.540> talked 17:23:21.830 --> 17:23:21.840 align:start position:0% secure network first of all we talked 17:23:21.840 --> 17:23:23.690 align:start position:0% secure network first of all we talked about<17:23:21.900> keeping<17:23:22.320> things<17:23:22.436> up<17:23:22.680> to<17:23:22.796> date<17:23:22.980> we 17:23:23.690 --> 17:23:23.700 align:start position:0% about keeping things up to date we 17:23:23.700 --> 17:23:25.550 align:start position:0% about keeping things up to date we talked<17:23:23.936> about<17:23:24.000> keeping<17:23:24.540> up<17:23:24.720> the<17:23:25.020> firmware 17:23:25.550 --> 17:23:25.560 align:start position:0% talked about keeping up the firmware 17:23:25.560 --> 17:23:29.150 align:start position:0% talked about keeping up the firmware drivers 17:23:29.150 --> 17:23:29.160 align:start position:0% 17:23:29.160 --> 17:23:31.606 align:start position:0% operating<17:23:30.060> systems 17:23:31.606 --> 17:23:31.616 align:start position:0% operating systems 17:23:31.616 --> 17:23:34.970 align:start position:0% operating systems patches<17:23:32.456> to<17:23:33.060> Software 17:23:34.970 --> 17:23:34.980 align:start position:0% patches to Software 17:23:34.980 --> 17:23:37.070 align:start position:0% patches to Software Etc<17:23:35.096> and<17:23:36.060> we're<17:23:36.296> always<17:23:36.416> dealing<17:23:36.720> with<17:23:36.900> a 17:23:37.070 --> 17:23:37.080 align:start position:0% Etc and we're always dealing with a 17:23:37.080 --> 17:23:39.766 align:start position:0% Etc and we're always dealing with a balancing<17:23:37.500> act<17:23:37.680> here<17:23:37.916> are<17:23:38.820> we 17:23:39.766 --> 17:23:39.776 align:start position:0% balancing act here are we 17:23:39.776 --> 17:23:45.470 align:start position:0% balancing act here are we doing<17:23:40.200> things<17:23:40.560> immediately 17:23:45.470 --> 17:23:45.480 align:start position:0% 17:23:45.480 --> 17:23:49.606 align:start position:0% or<17:23:46.140> are<17:23:46.560> we<17:23:46.680> going<17:23:46.796> to<17:23:46.980> wait<17:23:47.160> and<17:23:47.820> possibly<17:23:48.616> uh 17:23:49.606 --> 17:23:49.616 align:start position:0% or are we going to wait and possibly uh 17:23:49.616 --> 17:23:52.370 align:start position:0% or are we going to wait and possibly uh be<17:23:49.980> susceptible<17:23:50.456> but<17:23:51.116> we<17:23:51.540> might<17:23:51.660> have<17:23:51.840> buggy 17:23:52.370 --> 17:23:52.380 align:start position:0% be susceptible but we might have buggy 17:23:52.380 --> 17:23:54.230 align:start position:0% be susceptible but we might have buggy updates 17:23:54.230 --> 17:23:54.240 align:start position:0% updates 17:23:54.240 --> 17:23:57.230 align:start position:0% updates so<17:23:54.660> we<17:23:54.900> sort<17:23:55.140> of<17:23:55.256> want<17:23:55.500> to<17:23:55.680> find<17:23:55.980> a<17:23:56.520> good<17:23:56.700> medium 17:23:57.230 --> 17:23:57.240 align:start position:0% so we sort of want to find a good medium 17:23:57.240 --> 17:23:58.850 align:start position:0% so we sort of want to find a good medium middle<17:23:57.596> of<17:23:57.840> the<17:23:57.900> road<17:23:58.080> solution<17:23:58.616> there 17:23:58.850 --> 17:23:58.860 align:start position:0% middle of the road solution there 17:23:58.860 --> 17:24:01.370 align:start position:0% middle of the road solution there realizing<17:23:59.640> the<17:23:59.820> longer<17:24:00.116> we<17:24:00.240> wait<17:24:00.480> the<17:24:01.256> more 17:24:01.370 --> 17:24:01.380 align:start position:0% realizing the longer we wait the more 17:24:01.380 --> 17:24:03.830 align:start position:0% realizing the longer we wait the more susceptible<17:24:01.980> we<17:24:02.160> are<17:24:02.276> to<17:24:02.400> attacks<17:24:02.936> we<17:24:03.660> also 17:24:03.830 --> 17:24:03.840 align:start position:0% susceptible we are to attacks we also 17:24:03.840 --> 17:24:05.266 align:start position:0% susceptible we are to attacks we also want<17:24:03.956> to<17:24:04.080> make<17:24:04.140> sure<17:24:04.320> to<17:24:04.500> have<17:24:04.740> strong 17:24:05.266 --> 17:24:05.276 align:start position:0% want to make sure to have strong 17:24:05.276 --> 17:24:06.890 align:start position:0% want to make sure to have strong passwords 17:24:06.890 --> 17:24:06.900 align:start position:0% passwords 17:24:06.900 --> 17:24:09.530 align:start position:0% passwords remember<17:24:07.436> a<17:24:07.916> strong<17:24:08.096> password<17:24:08.540> generally 17:24:09.530 --> 17:24:09.540 align:start position:0% remember a strong password generally 17:24:09.540 --> 17:24:13.670 align:start position:0% remember a strong password generally means<17:24:10.340> it's<17:24:11.340> 15<17:24:12.000> characters<17:24:12.660> or<17:24:13.256> more<17:24:13.436> the 17:24:13.670 --> 17:24:13.680 align:start position:0% means it's 15 characters or more the 17:24:13.680 --> 17:24:15.230 align:start position:0% means it's 15 characters or more the longer<17:24:14.040> the<17:24:14.160> better 17:24:15.230 --> 17:24:15.240 align:start position:0% longer the better 17:24:15.240 --> 17:24:18.286 align:start position:0% longer the better we<17:24:15.840> have<17:24:16.140> numbers 17:24:18.286 --> 17:24:18.296 align:start position:0% we have numbers 17:24:18.296 --> 17:24:21.230 align:start position:0% we have numbers symbols 17:24:21.230 --> 17:24:21.240 align:start position:0% symbols 17:24:21.240 --> 17:24:23.510 align:start position:0% symbols lowercase<17:24:22.140> letters 17:24:23.510 --> 17:24:23.520 align:start position:0% lowercase letters 17:24:23.520 --> 17:24:26.390 align:start position:0% lowercase letters uppercase<17:24:24.240> letters 17:24:26.390 --> 17:24:26.400 align:start position:0% uppercase letters 17:24:26.400 --> 17:24:29.390 align:start position:0% uppercase letters and<17:24:27.060> we<17:24:27.660> want<17:24:27.776> to<17:24:27.900> use<17:24:28.080> them<17:24:28.380> in<17:24:28.860> a<17:24:29.040> varied 17:24:29.390 --> 17:24:29.400 align:start position:0% and we want to use them in a varied 17:24:29.400 --> 17:24:31.550 align:start position:0% and we want to use them in a varied random<17:24:29.820> combination 17:24:31.550 --> 17:24:31.560 align:start position:0% random combination 17:24:31.560 --> 17:24:34.190 align:start position:0% random combination we<17:24:31.980> also<17:24:32.220> want<17:24:32.400> to<17:24:32.520> make<17:24:32.700> sure<17:24:32.936> that<17:24:33.720> we're<17:24:33.956> not 17:24:34.190 --> 17:24:34.200 align:start position:0% we also want to make sure that we're not 17:24:34.200 --> 17:24:37.970 align:start position:0% we also want to make sure that we're not reusing<17:24:35.240> the<17:24:36.240> same<17:24:36.416> passwords 17:24:37.970 --> 17:24:37.980 align:start position:0% reusing the same passwords 17:24:37.980 --> 17:24:40.730 align:start position:0% reusing the same passwords and<17:24:38.936> don't<17:24:39.360> write<17:24:39.540> them<17:24:39.840> down<17:24:40.020> that's<17:24:40.500> always 17:24:40.730 --> 17:24:40.740 align:start position:0% and don't write them down that's always 17:24:40.740 --> 17:24:42.766 align:start position:0% and don't write them down that's always a<17:24:40.980> problem 17:24:42.766 --> 17:24:42.776 align:start position:0% a problem 17:24:42.776 --> 17:24:44.810 align:start position:0% a problem now<17:24:43.320> of<17:24:43.500> course<17:24:43.616> again<17:24:43.916> we<17:24:44.220> have<17:24:44.276> a<17:24:44.456> balancing 17:24:44.810 --> 17:24:44.820 align:start position:0% now of course again we have a balancing 17:24:44.820 --> 17:24:47.030 align:start position:0% now of course again we have a balancing act<17:24:45.000> here<17:24:45.240> because<17:24:45.840> the<17:24:46.256> more<17:24:46.380> difficult<17:24:46.796> it 17:24:47.030 --> 17:24:47.040 align:start position:0% act here because the more difficult it 17:24:47.040 --> 17:24:48.106 align:start position:0% act here because the more difficult it is 17:24:48.106 --> 17:24:48.116 align:start position:0% is 17:24:48.116 --> 17:24:50.350 align:start position:0% is the 17:24:50.350 --> 17:24:50.360 align:start position:0% the 17:24:50.360 --> 17:24:52.850 align:start position:0% the more<17:24:51.360> difficult<17:24:51.540> to<17:24:51.776> password<17:24:51.956> rather<17:24:52.436> than 17:24:52.850 --> 17:24:52.860 align:start position:0% more difficult to password rather than 17:24:52.860 --> 17:24:54.230 align:start position:0% more difficult to password rather than the<17:24:53.096> more<17:24:53.220> likely<17:24:53.520> someone's<17:24:53.880> going<17:24:54.060> to<17:24:54.116> write 17:24:54.230 --> 17:24:54.240 align:start position:0% the more likely someone's going to write 17:24:54.240 --> 17:24:56.810 align:start position:0% the more likely someone's going to write it<17:24:54.416> down<17:24:54.596> and<17:24:55.200> so<17:24:55.380> we<17:24:55.740> need<17:24:55.916> to<17:24:56.096> also<17:24:56.456> make<17:24:56.640> sure 17:24:56.810 --> 17:24:56.820 align:start position:0% it down and so we need to also make sure 17:24:56.820 --> 17:24:58.970 align:start position:0% it down and so we need to also make sure that<17:24:57.060> the<17:24:57.296> passwords<17:24:57.840> are<17:24:58.080> have<17:24:58.680> a<17:24:58.860> certain 17:24:58.970 --> 17:24:58.980 align:start position:0% that the passwords are have a certain 17:24:58.980 --> 17:25:00.766 align:start position:0% that the passwords are have a certain degree<17:24:59.276> of<17:24:59.400> ease<17:24:59.756> of<17:24:59.820> use 17:25:00.766 --> 17:25:00.776 align:start position:0% degree of ease of use 17:25:00.776 --> 17:25:02.266 align:start position:0% degree of ease of use we<17:25:01.200> also<17:25:01.436> are<17:25:01.560> probably<17:25:01.740> going<17:25:01.916> to<17:25:02.040> want<17:25:02.160> the 17:25:02.266 --> 17:25:02.276 align:start position:0% we also are probably going to want the 17:25:02.276 --> 17:25:04.130 align:start position:0% we also are probably going to want the passwords<17:25:02.700> to<17:25:02.880> expire<17:25:03.360> every<17:25:03.596> once<17:25:03.900> in<17:25:03.956> a 17:25:04.130 --> 17:25:04.140 align:start position:0% passwords to expire every once in a 17:25:04.140 --> 17:25:04.730 align:start position:0% passwords to expire every once in a while 17:25:04.730 --> 17:25:04.740 align:start position:0% while 17:25:04.740 --> 17:25:08.030 align:start position:0% while and<17:25:05.276> so<17:25:05.400> on<17:25:05.520> and<17:25:05.640> so<17:25:05.820> forth<17:25:06.416> with<17:25:06.840> a<17:25:07.020> VPN<17:25:07.436> we 17:25:08.030 --> 17:25:08.040 align:start position:0% and so on and so forth with a VPN we 17:25:08.040 --> 17:25:09.230 align:start position:0% and so on and so forth with a VPN we need<17:25:08.160> to<17:25:08.340> make<17:25:08.520> sure<17:25:08.700> that<17:25:08.936> there<17:25:09.116> are 17:25:09.230 --> 17:25:09.240 align:start position:0% need to make sure that there are 17:25:09.240 --> 17:25:14.330 align:start position:0% need to make sure that there are multiple<17:25:09.480> forms<17:25:09.776> of<17:25:09.956> Authentication 17:25:14.330 --> 17:25:14.340 align:start position:0% 17:25:14.340 --> 17:25:16.246 align:start position:0% remember<17:25:14.820> the<17:25:15.240> three<17:25:15.416> things<17:25:15.596> we<17:25:15.840> have<17:25:16.020> when 17:25:16.246 --> 17:25:16.256 align:start position:0% remember the three things we have when 17:25:16.256 --> 17:25:18.530 align:start position:0% remember the three things we have when it<17:25:16.380> comes<17:25:16.500> to<17:25:16.680> authentication<17:25:17.276> something<17:25:18.180> you 17:25:18.530 --> 17:25:18.540 align:start position:0% it comes to authentication something you 17:25:18.540 --> 17:25:19.850 align:start position:0% it comes to authentication something you have 17:25:19.850 --> 17:25:19.860 align:start position:0% have 17:25:19.860 --> 17:25:22.130 align:start position:0% have like<17:25:20.340> a<17:25:20.580> fob<17:25:20.936> something<17:25:21.240> you<17:25:21.540> know<17:25:21.660> like<17:25:21.956> a 17:25:22.130 --> 17:25:22.140 align:start position:0% like a fob something you know like a 17:25:22.140 --> 17:25:23.990 align:start position:0% like a fob something you know like a password<17:25:22.320> and<17:25:23.160> something<17:25:23.340> you<17:25:23.580> are<17:25:23.700> like<17:25:23.820> a 17:25:23.990 --> 17:25:24.000 align:start position:0% password and something you are like a 17:25:24.000 --> 17:25:27.286 align:start position:0% password and something you are like a retinal<17:25:24.296> scan<17:25:24.660> or<17:25:25.380> a<17:25:25.500> biometrics 17:25:27.286 --> 17:25:27.296 align:start position:0% retinal scan or a biometrics 17:25:27.296 --> 17:25:29.630 align:start position:0% retinal scan or a biometrics when<17:25:27.596> it<17:25:27.720> comes<17:25:27.900> to<17:25:28.020> user<17:25:28.380> access<17:25:28.560> we<17:25:29.276> want<17:25:29.456> to 17:25:29.630 --> 17:25:29.640 align:start position:0% when it comes to user access we want to 17:25:29.640 --> 17:25:31.690 align:start position:0% when it comes to user access we want to practice<17:25:29.880> the<17:25:30.660> principle<17:25:31.020> of<17:25:31.320> least 17:25:31.690 --> 17:25:31.700 align:start position:0% practice the principle of least 17:25:31.700 --> 17:25:34.246 align:start position:0% practice the principle of least privilege<17:25:32.700> meaning<17:25:33.296> you're<17:25:33.840> only<17:25:34.020> going<17:25:34.200> to 17:25:34.246 --> 17:25:34.256 align:start position:0% privilege meaning you're only going to 17:25:34.256 --> 17:25:36.766 align:start position:0% privilege meaning you're only going to be<17:25:34.380> given<17:25:34.680> access<17:25:35.000> to<17:25:36.000> that<17:25:36.180> which<17:25:36.416> you<17:25:36.660> need 17:25:36.766 --> 17:25:36.776 align:start position:0% be given access to that which you need 17:25:36.776 --> 17:25:38.926 align:start position:0% be given access to that which you need access<17:25:37.020> to<17:25:37.256> to<17:25:37.436> do<17:25:37.560> your<17:25:37.740> job<17:25:37.916> accounting<17:25:38.756> does 17:25:38.926 --> 17:25:38.936 align:start position:0% access to to do your job accounting does 17:25:38.936 --> 17:25:40.850 align:start position:0% access to to do your job accounting does not<17:25:39.116> need<17:25:39.296> access<17:25:39.596> to<17:25:40.020> marketing<17:25:40.380> and<17:25:40.616> vice 17:25:40.850 --> 17:25:40.860 align:start position:0% not need access to marketing and vice 17:25:40.860 --> 17:25:43.850 align:start position:0% not need access to marketing and vice versa<17:25:41.700> finally<17:25:42.480> we<17:25:42.900> want<17:25:43.020> to<17:25:43.200> make<17:25:43.380> sure<17:25:43.616> to 17:25:43.850 --> 17:25:43.860 align:start position:0% versa finally we want to make sure to 17:25:43.860 --> 17:25:44.810 align:start position:0% versa finally we want to make sure to disable 17:25:44.810 --> 17:25:44.820 align:start position:0% disable 17:25:44.820 --> 17:25:48.586 align:start position:0% disable or<17:25:45.660> delete<17:25:46.220> inactive<17:25:47.220> accounts<17:25:47.756> keeping<17:25:48.416> in 17:25:48.586 --> 17:25:48.596 align:start position:0% or delete inactive accounts keeping in 17:25:48.596 --> 17:25:50.690 align:start position:0% or delete inactive accounts keeping in mind<17:25:48.776> of<17:25:49.140> course<17:25:49.320> that<17:25:49.860> someone<17:25:50.160> who<17:25:50.456> leaves 17:25:50.690 --> 17:25:50.700 align:start position:0% mind of course that someone who leaves 17:25:50.700 --> 17:25:52.426 align:start position:0% mind of course that someone who leaves the<17:25:50.820> company<17:25:51.000> might<17:25:51.360> need<17:25:51.540> to<17:25:51.660> come<17:25:51.840> back<17:25:52.080> and 17:25:52.426 --> 17:25:52.436 align:start position:0% the company might need to come back and 17:25:52.436 --> 17:25:53.746 align:start position:0% the company might need to come back and therefore<17:25:52.680> we<17:25:53.040> might<17:25:53.160> want<17:25:53.276> to<17:25:53.400> make<17:25:53.456> it<17:25:53.580> easy 17:25:53.746 --> 17:25:53.756 align:start position:0% therefore we might want to make it easy 17:25:53.756 --> 17:25:55.246 align:start position:0% therefore we might want to make it easy for<17:25:54.000> them<17:25:54.116> to<17:25:54.296> have<17:25:54.416> access<17:25:54.660> to<17:25:54.900> their<17:25:55.080> old 17:25:55.246 --> 17:25:55.256 align:start position:0% for them to have access to their old 17:25:55.256 --> 17:26:01.020 align:start position:0% for them to have access to their old stuff 17:26:01.020 --> 17:26:01.030 align:start position:0% 17:26:01.030 --> 17:26:20.990 align:start position:0% [Music] 17:26:20.990 --> 17:26:21.000 align:start position:0% 17:26:21.000 --> 17:26:23.890 align:start position:0% network<17:26:21.840> security<17:26:22.756> authentication 17:26:23.890 --> 17:26:23.900 align:start position:0% network security authentication 17:26:23.900 --> 17:26:27.350 align:start position:0% network security authentication authorization<17:26:24.900> and<17:26:25.560> accounting 17:26:27.350 --> 17:26:27.360 align:start position:0% authorization and accounting 17:26:27.360 --> 17:26:29.390 align:start position:0% authorization and accounting in<17:26:27.900> the<17:26:28.020> last<17:26:28.140> module<17:26:28.560> we<17:26:28.740> started<17:26:29.040> off<17:26:29.160> this 17:26:29.390 --> 17:26:29.400 align:start position:0% in the last module we started off this 17:26:29.400 --> 17:26:31.850 align:start position:0% in the last module we started off this lesson<17:26:29.756> by<17:26:30.060> discussing<17:26:30.596> the<17:26:31.020> fundamentals<17:26:31.680> of 17:26:31.850 --> 17:26:31.860 align:start position:0% lesson by discussing the fundamentals of 17:26:31.860 --> 17:26:34.190 align:start position:0% lesson by discussing the fundamentals of network<17:26:32.040> security<17:26:32.400> Now<17:26:33.180> a<17:26:33.480> big<17:26:33.596> portion<17:26:34.080> of 17:26:34.190 --> 17:26:34.200 align:start position:0% network security Now a big portion of 17:26:34.200 --> 17:26:38.086 align:start position:0% network security Now a big portion of network<17:26:34.436> security<17:26:34.860> has<17:26:35.456> to<17:26:35.640> do<17:26:35.820> with<17:26:36.540> AAA<17:26:37.096> or 17:26:38.086 --> 17:26:38.096 align:start position:0% network security has to do with AAA or 17:26:38.096 --> 17:26:40.786 align:start position:0% network security has to do with AAA or authentication<17:26:39.080> authorization<17:26:40.080> and 17:26:40.786 --> 17:26:40.796 align:start position:0% authentication authorization and 17:26:40.796 --> 17:26:41.926 align:start position:0% authentication authorization and accounting 17:26:41.926 --> 17:26:41.936 align:start position:0% accounting 17:26:41.936 --> 17:26:44.630 align:start position:0% accounting AAA<17:26:42.596> server<17:26:43.080> on<17:26:43.256> a<17:26:43.436> network<17:26:43.560> is<17:26:44.096> probably<17:26:44.276> one 17:26:44.630 --> 17:26:44.640 align:start position:0% AAA server on a network is probably one 17:26:44.640 --> 17:26:46.426 align:start position:0% AAA server on a network is probably one of<17:26:44.756> the<17:26:44.756> most<17:26:45.000> important<17:26:45.660> things<17:26:45.956> when<17:26:46.256> it 17:26:46.426 --> 17:26:46.436 align:start position:0% of the most important things when it 17:26:46.436 --> 17:26:48.286 align:start position:0% of the most important things when it comes<17:26:46.616> to<17:26:46.796> security<17:26:46.980> and<17:26:47.640> it's<17:26:47.820> quite<17:26:48.060> a<17:26:48.180> bit 17:26:48.286 --> 17:26:48.296 align:start position:0% comes to security and it's quite a bit 17:26:48.296 --> 17:26:51.286 align:start position:0% comes to security and it's quite a bit of<17:26:48.416> work<17:26:48.596> so<17:26:49.560> in<17:26:49.916> this<17:26:50.096> module<17:26:50.520> we're<17:26:50.936> going<17:26:51.116> to 17:26:51.286 --> 17:26:51.296 align:start position:0% of work so in this module we're going to 17:26:51.296 --> 17:26:54.586 align:start position:0% of work so in this module we're going to Define<17:26:52.200> and<17:26:52.916> discuss<17:26:53.340> these<17:26:54.000> three<17:26:54.180> A's 17:26:54.586 --> 17:26:54.596 align:start position:0% Define and discuss these three A's 17:26:54.596 --> 17:26:56.650 align:start position:0% Define and discuss these three A's Authentication 17:26:56.650 --> 17:26:56.660 align:start position:0% Authentication 17:26:56.660 --> 17:26:58.310 align:start position:0% Authentication authorization 17:26:58.310 --> 17:26:58.320 align:start position:0% authorization 17:26:58.320 --> 17:27:01.670 align:start position:0% authorization and<17:26:59.040> accounting<17:26:59.640> in<17:27:00.360> further<17:27:00.660> detail<17:27:01.020> so<17:27:01.500> we 17:27:01.670 --> 17:27:01.680 align:start position:0% and accounting in further detail so we 17:27:01.680 --> 17:27:03.650 align:start position:0% and accounting in further detail so we know<17:27:01.860> not<17:27:02.160> just<17:27:02.340> what<17:27:02.640> they<17:27:02.820> are<17:27:03.000> but<17:27:03.416> how 17:27:03.650 --> 17:27:03.660 align:start position:0% know not just what they are but how 17:27:03.660 --> 17:27:05.086 align:start position:0% know not just what they are but how they're<17:27:03.840> implemented<17:27:04.380> in<17:27:04.616> a<17:27:04.740> very<17:27:04.860> general 17:27:05.086 --> 17:27:05.096 align:start position:0% they're implemented in a very general 17:27:05.096 --> 17:27:06.786 align:start position:0% they're implemented in a very general way 17:27:06.786 --> 17:27:06.796 align:start position:0% way 17:27:06.796 --> 17:27:10.070 align:start position:0% way authentication<17:27:07.796> is<17:27:08.096> the<17:27:08.340> first<17:27:08.520> a<17:27:08.880> it's<17:27:09.660> used 17:27:10.070 --> 17:27:10.080 align:start position:0% authentication is the first a it's used 17:27:10.080 --> 17:27:13.310 align:start position:0% authentication is the first a it's used to<17:27:10.860> identify<17:27:11.580> the<17:27:11.880> user<17:27:12.240> and<17:27:12.720> make<17:27:12.900> sure<17:27:13.020> that 17:27:13.310 --> 17:27:13.320 align:start position:0% to identify the user and make sure that 17:27:13.320 --> 17:27:15.586 align:start position:0% to identify the user and make sure that the<17:27:13.500> user<17:27:13.796> is<17:27:14.160> legitimate<17:27:14.700> sometimes 17:27:15.586 --> 17:27:15.596 align:start position:0% the user is legitimate sometimes 17:27:15.596 --> 17:27:18.830 align:start position:0% the user is legitimate sometimes attackers<17:27:16.200> and<17:27:16.740> Bots<17:27:17.220> will<17:27:17.880> try<17:27:18.180> to<17:27:18.416> access 17:27:18.830 --> 17:27:18.840 align:start position:0% attackers and Bots will try to access 17:27:18.840 --> 17:27:21.710 align:start position:0% attackers and Bots will try to access the<17:27:19.320> network<17:27:19.560> or<17:27:19.916> secure<17:27:20.276> data<17:27:20.756> by<17:27:21.296> acting 17:27:21.710 --> 17:27:21.720 align:start position:0% the network or secure data by acting 17:27:21.720 --> 17:27:24.230 align:start position:0% the network or secure data by acting like<17:27:22.140> they're<17:27:22.436> a<17:27:22.616> legitimate<17:27:23.040> user<17:27:23.456> this<17:27:24.116> is 17:27:24.230 --> 17:27:24.240 align:start position:0% like they're a legitimate user this is 17:27:24.240 --> 17:27:26.690 align:start position:0% like they're a legitimate user this is where<17:27:24.480> authentication<17:27:25.200> comes<17:27:25.680> into<17:27:25.740> play 17:27:26.690 --> 17:27:26.700 align:start position:0% where authentication comes into play 17:27:26.700 --> 17:27:28.926 align:start position:0% where authentication comes into play any<17:27:27.416> secure<17:27:27.776> network<17:27:28.020> is<17:27:28.380> going<17:27:28.500> to<17:27:28.680> require 17:27:28.926 --> 17:27:28.936 align:start position:0% any secure network is going to require 17:27:28.936 --> 17:27:31.606 align:start position:0% any secure network is going to require something<17:27:29.936> like<17:27:30.296> a<17:27:30.720> username<17:27:31.140> and<17:27:31.380> password 17:27:31.606 --> 17:27:31.616 align:start position:0% something like a username and password 17:27:31.616 --> 17:27:34.010 align:start position:0% something like a username and password to<17:27:31.980> log<17:27:32.160> in<17:27:32.400> and<17:27:33.000> any<17:27:33.180> data<17:27:33.540> that's<17:27:33.720> really 17:27:34.010 --> 17:27:34.020 align:start position:0% to log in and any data that's really 17:27:34.020 --> 17:27:35.990 align:start position:0% to log in and any data that's really important<17:27:34.500> or<17:27:34.796> secure<17:27:35.160> needs<17:27:35.820> to<17:27:35.880> be 17:27:35.990 --> 17:27:36.000 align:start position:0% important or secure needs to be 17:27:36.000 --> 17:27:37.906 align:start position:0% important or secure needs to be protected<17:27:36.416> now<17:27:37.020> there<17:27:37.256> are<17:27:37.380> ways<17:27:37.680> of<17:27:37.796> course 17:27:37.906 --> 17:27:37.916 align:start position:0% protected now there are ways of course 17:27:37.916 --> 17:27:39.766 align:start position:0% protected now there are ways of course for<17:27:38.276> these<17:27:38.456> attackers<17:27:38.880> to<17:27:39.240> gather<17:27:39.480> the 17:27:39.766 --> 17:27:39.776 align:start position:0% for these attackers to gather the 17:27:39.776 --> 17:27:41.870 align:start position:0% for these attackers to gather the password<17:27:40.020> and<17:27:40.320> username<17:27:40.740> information<17:27:40.980> but 17:27:41.870 --> 17:27:41.880 align:start position:0% password and username information but 17:27:41.880 --> 17:27:43.606 align:start position:0% password and username information but the<17:27:42.060> smart<17:27:42.240> thing<17:27:42.480> for<17:27:42.720> us<17:27:42.840> to<17:27:43.020> do<17:27:43.140> is<17:27:43.380> to 17:27:43.606 --> 17:27:43.616 align:start position:0% the smart thing for us to do is to 17:27:43.616 --> 17:27:45.890 align:start position:0% the smart thing for us to do is to change<17:27:43.860> passwords<17:27:44.580> for<17:27:44.820> all<17:27:45.000> users<17:27:45.416> on<17:27:45.776> a 17:27:45.890 --> 17:27:45.900 align:start position:0% change passwords for all users on a 17:27:45.900 --> 17:27:49.190 align:start position:0% change passwords for all users on a network<17:27:46.080> frequently<17:27:46.860> probably<17:27:47.700> every<17:27:48.240> 30<17:27:48.840> to 17:27:49.190 --> 17:27:49.200 align:start position:0% network frequently probably every 30 to 17:27:49.200 --> 17:27:52.130 align:start position:0% network frequently probably every 30 to 90<17:27:49.436> days<17:27:49.880> again<17:27:50.880> we<17:27:51.240> have<17:27:51.360> to<17:27:51.596> balance<17:27:51.900> that 17:27:52.130 --> 17:27:52.140 align:start position:0% 90 days again we have to balance that 17:27:52.140 --> 17:27:54.230 align:start position:0% 90 days again we have to balance that with<17:27:52.560> how<17:27:52.860> easy<17:27:53.160> it<17:27:53.400> is<17:27:53.520> for<17:27:53.756> someone<17:27:53.880> to<17:27:54.116> come 17:27:54.230 --> 17:27:54.240 align:start position:0% with how easy it is for someone to come 17:27:54.240 --> 17:27:56.390 align:start position:0% with how easy it is for someone to come up<17:27:54.360> with<17:27:54.480> a<17:27:54.660> new<17:27:54.776> password<17:27:55.020> and<17:27:55.980> they're<17:27:56.220> going 17:27:56.390 --> 17:27:56.400 align:start position:0% up with a new password and they're going 17:27:56.400 --> 17:27:57.710 align:start position:0% up with a new password and they're going to<17:27:56.456> remember<17:27:56.640> the<17:27:56.936> new<17:27:57.060> password<17:27:57.240> they<17:27:57.596> come 17:27:57.710 --> 17:27:57.720 align:start position:0% to remember the new password they come 17:27:57.720 --> 17:27:59.446 align:start position:0% to remember the new password they come up<17:27:57.840> with<17:27:57.956> we<17:27:58.616> need<17:27:58.796> to<17:27:58.860> make<17:27:58.980> sure<17:27:59.160> that<17:27:59.340> the 17:27:59.446 --> 17:27:59.456 align:start position:0% up with we need to make sure that the 17:27:59.456 --> 17:28:01.850 align:start position:0% up with we need to make sure that the passwords<17:27:59.880> are<17:28:00.000> documented<17:28:00.660> in<17:28:01.256> some<17:28:01.500> way 17:28:01.850 --> 17:28:01.860 align:start position:0% passwords are documented in some way 17:28:01.860 --> 17:28:03.650 align:start position:0% passwords are documented in some way although<17:28:02.640> we<17:28:02.756> want<17:28:02.936> to<17:28:03.060> be<17:28:03.116> careful<17:28:03.416> again 17:28:03.650 --> 17:28:03.660 align:start position:0% although we want to be careful again 17:28:03.660 --> 17:28:05.086 align:start position:0% although we want to be careful again because<17:28:03.956> when<17:28:04.256> we<17:28:04.436> write<17:28:04.616> them<17:28:04.796> down<17:28:04.916> and 17:28:05.086 --> 17:28:05.096 align:start position:0% because when we write them down and 17:28:05.096 --> 17:28:06.890 align:start position:0% because when we write them down and document<17:28:05.400> them<17:28:05.700> that<17:28:06.116> opens<17:28:06.416> up<17:28:06.480> another<17:28:06.596> way 17:28:06.890 --> 17:28:06.900 align:start position:0% document them that opens up another way 17:28:06.900 --> 17:28:08.570 align:start position:0% document them that opens up another way they<17:28:07.080> can<17:28:07.200> be<17:28:07.380> stolen<17:28:07.740> and<17:28:08.160> we<17:28:08.276> want<17:28:08.400> to<17:28:08.520> make 17:28:08.570 --> 17:28:08.580 align:start position:0% they can be stolen and we want to make 17:28:08.580 --> 17:28:10.310 align:start position:0% they can be stolen and we want to make sure<17:28:08.700> that<17:28:08.820> they're<17:28:09.000> all<17:28:09.180> secure<17:28:09.540> if<17:28:10.200> an 17:28:10.310 --> 17:28:10.320 align:start position:0% sure that they're all secure if an 17:28:10.320 --> 17:28:12.286 align:start position:0% sure that they're all secure if an attacker<17:28:10.740> has<17:28:10.916> an<17:28:11.160> outdated<17:28:11.520> password<17:28:11.936> it's 17:28:12.286 --> 17:28:12.296 align:start position:0% attacker has an outdated password it's 17:28:12.296 --> 17:28:15.406 align:start position:0% attacker has an outdated password it's going<17:28:12.480> to<17:28:12.660> do<17:28:12.776> them<17:28:13.020> no<17:28:13.500> good<17:28:13.820> so<17:28:14.820> if<17:28:15.060> we<17:28:15.296> can 17:28:15.406 --> 17:28:15.416 align:start position:0% going to do them no good so if we can 17:28:15.416 --> 17:28:16.926 align:start position:0% going to do them no good so if we can put<17:28:15.596> this<17:28:15.720> in<17:28:15.900> another<17:28:16.020> way 17:28:16.926 --> 17:28:16.936 align:start position:0% put this in another way 17:28:16.936 --> 17:28:21.530 align:start position:0% put this in another way authentication<17:28:18.320> verifies<17:28:19.400> identity<17:28:20.400> this<17:28:21.360> is 17:28:21.530 --> 17:28:21.540 align:start position:0% authentication verifies identity this is 17:28:21.540 --> 17:28:25.906 align:start position:0% authentication verifies identity this is sort<17:28:21.776> of<17:28:21.900> like<17:28:22.200> you<17:28:22.860> have<17:28:23.360> a<17:28:24.360> ID<17:28:25.020> card<17:28:25.436> or 17:28:25.906 --> 17:28:25.916 align:start position:0% sort of like you have a ID card or 17:28:25.916 --> 17:28:28.606 align:start position:0% sort of like you have a ID card or driver's<17:28:26.276> license<17:28:26.936> that<17:28:27.660> provides<17:28:28.200> your 17:28:28.606 --> 17:28:28.616 align:start position:0% driver's license that provides your 17:28:28.616 --> 17:28:30.406 align:start position:0% driver's license that provides your identity<17:28:28.980> and<17:28:29.276> authenticates<17:28:29.820> you<17:28:30.060> are<17:28:30.240> who 17:28:30.406 --> 17:28:30.416 align:start position:0% identity and authenticates you are who 17:28:30.416 --> 17:28:32.030 align:start position:0% identity and authenticates you are who you<17:28:30.540> are<17:28:30.720> one<17:28:31.256> of<17:28:31.380> the<17:28:31.436> reasons<17:28:31.740> we<17:28:31.860> have 17:28:32.030 --> 17:28:32.040 align:start position:0% you are one of the reasons we have 17:28:32.040 --> 17:28:33.890 align:start position:0% you are one of the reasons we have pictures<17:28:32.276> on<17:28:32.820> our<17:28:32.936> driver's<17:28:33.360> license<17:28:33.540> or 17:28:33.890 --> 17:28:33.900 align:start position:0% pictures on our driver's license or 17:28:33.900 --> 17:28:36.050 align:start position:0% pictures on our driver's license or government<17:28:34.200> issued<17:28:34.680> IDs<17:28:35.096> is<17:28:35.580> so<17:28:35.756> that<17:28:35.880> people 17:28:36.050 --> 17:28:36.060 align:start position:0% government issued IDs is so that people 17:28:36.060 --> 17:28:38.030 align:start position:0% government issued IDs is so that people can<17:28:36.296> look<17:28:36.540> at<17:28:36.720> it<17:28:36.840> and<17:28:37.020> guarantee<17:28:37.436> We<17:28:37.740> Are<17:28:37.860> Who 17:28:38.030 --> 17:28:38.040 align:start position:0% can look at it and guarantee We Are Who 17:28:38.040 --> 17:28:39.650 align:start position:0% can look at it and guarantee We Are Who We<17:28:38.220> Are<17:28:38.400> this<17:28:38.880> used<17:28:39.060> to<17:28:39.180> be<17:28:39.240> done<17:28:39.416> with 17:28:39.650 --> 17:28:39.660 align:start position:0% We Are this used to be done with 17:28:39.660 --> 17:28:41.446 align:start position:0% We Are this used to be done with signatures<17:28:40.200> they<17:28:40.616> would<17:28:40.796> look<17:28:40.980> at<17:28:41.160> two 17:28:41.446 --> 17:28:41.456 align:start position:0% signatures they would look at two 17:28:41.456 --> 17:28:43.246 align:start position:0% signatures they would look at two signatures<17:28:42.000> make<17:28:42.296> sure<17:28:42.416> they<17:28:42.660> were<17:28:42.776> identical 17:28:43.246 --> 17:28:43.256 align:start position:0% signatures make sure they were identical 17:28:43.256 --> 17:28:45.530 align:start position:0% signatures make sure they were identical and<17:28:43.860> then<17:28:43.980> we<17:28:44.276> could<17:28:44.400> authenticate<17:28:45.180> the 17:28:45.530 --> 17:28:45.540 align:start position:0% and then we could authenticate the 17:28:45.540 --> 17:28:47.746 align:start position:0% and then we could authenticate the person<17:28:45.720> was<17:28:46.140> actually<17:28:46.380> us<17:28:46.740> now<17:28:47.276> we've<17:28:47.456> moved 17:28:47.746 --> 17:28:47.756 align:start position:0% person was actually us now we've moved 17:28:47.756 --> 17:28:49.670 align:start position:0% person was actually us now we've moved way<17:28:48.000> past<17:28:48.240> this<17:28:48.540> now<17:28:48.720> we<17:28:48.956> can<17:28:49.080> even<17:28:49.256> use<17:28:49.436> things 17:28:49.670 --> 17:28:49.680 align:start position:0% way past this now we can even use things 17:28:49.680 --> 17:28:51.670 align:start position:0% way past this now we can even use things like<17:28:49.860> fingerprints<17:28:50.700> which<17:28:51.116> more<17:28:51.416> or<17:28:51.540> less 17:28:51.670 --> 17:28:51.680 align:start position:0% like fingerprints which more or less 17:28:51.680 --> 17:28:54.350 align:start position:0% like fingerprints which more or less authenticate<17:28:52.680> that<17:28:52.916> we<17:28:53.220> are<17:28:53.400> who<17:28:53.640> we<17:28:53.880> say<17:28:54.060> we 17:28:54.350 --> 17:28:54.360 align:start position:0% authenticate that we are who we say we 17:28:54.360 --> 17:28:55.310 align:start position:0% authenticate that we are who we say we are 17:28:55.310 --> 17:28:55.320 align:start position:0% are 17:28:55.320 --> 17:28:56.810 align:start position:0% are so<17:28:55.916> here<17:28:56.160> is<17:28:56.276> another<17:28:56.456> form<17:28:56.700> of 17:28:56.810 --> 17:28:56.820 align:start position:0% so here is another form of 17:28:56.820 --> 17:28:58.670 align:start position:0% so here is another form of authentication<17:28:57.480> you<17:28:57.840> may<17:28:57.956> have<17:28:58.140> encountered 17:28:58.670 --> 17:28:58.680 align:start position:0% authentication you may have encountered 17:28:58.680 --> 17:29:00.286 align:start position:0% authentication you may have encountered this<17:28:59.040> one<17:28:59.220> before<17:28:59.400> when<17:28:59.820> you're<17:28:59.936> trying<17:29:00.116> to 17:29:00.286 --> 17:29:00.296 align:start position:0% this one before when you're trying to 17:29:00.296 --> 17:29:02.266 align:start position:0% this one before when you're trying to access<17:29:00.480> things<17:29:00.840> on<17:29:01.080> the<17:29:01.200> internet<17:29:01.320> this<17:29:02.096> is 17:29:02.266 --> 17:29:02.276 align:start position:0% access things on the internet this is 17:29:02.276 --> 17:29:05.330 align:start position:0% access things on the internet this is called<17:29:02.580> or<17:29:02.820> looks<17:29:03.180> like<17:29:03.360> a<17:29:04.140> captcha<17:29:04.680> and<17:29:05.160> it's 17:29:05.330 --> 17:29:05.340 align:start position:0% called or looks like a captcha and it's 17:29:05.340 --> 17:29:07.786 align:start position:0% called or looks like a captcha and it's used<17:29:05.520> to<17:29:05.756> stop<17:29:06.000> Bots<17:29:06.480> from<17:29:06.776> accessing<17:29:07.380> secure 17:29:07.786 --> 17:29:07.796 align:start position:0% used to stop Bots from accessing secure 17:29:07.796 --> 17:29:09.586 align:start position:0% used to stop Bots from accessing secure data<17:29:08.220> or<17:29:08.520> infiltrating<17:29:08.936> someone's<17:29:09.416> account 17:29:09.586 --> 17:29:09.596 align:start position:0% data or infiltrating someone's account 17:29:09.596 --> 17:29:11.446 align:start position:0% data or infiltrating someone's account or<17:29:09.900> making<17:29:10.140> an<17:29:10.380> account<17:29:10.500> when<17:29:11.040> we<17:29:11.220> don't<17:29:11.276> want 17:29:11.446 --> 17:29:11.456 align:start position:0% or making an account when we don't want 17:29:11.456 --> 17:29:14.446 align:start position:0% or making an account when we don't want them<17:29:11.580> to<17:29:11.820> so<17:29:12.480> the<17:29:12.720> text<17:29:12.840> in<17:29:13.140> the<17:29:13.320> gray<17:29:13.436> box<17:29:13.740> is 17:29:14.446 --> 17:29:14.456 align:start position:0% them to so the text in the gray box is 17:29:14.456 --> 17:29:16.786 align:start position:0% them to so the text in the gray box is difficult<17:29:14.820> to<17:29:15.180> read<17:29:15.360> for<17:29:15.720> a<17:29:15.900> bot<17:29:16.200> it's 17:29:16.786 --> 17:29:16.796 align:start position:0% difficult to read for a bot it's 17:29:16.796 --> 17:29:19.490 align:start position:0% difficult to read for a bot it's actually<17:29:17.040> a<17:29:17.700> picture<17:29:17.880> and<17:29:18.840> it's<17:29:19.256> very 17:29:19.490 --> 17:29:19.500 align:start position:0% actually a picture and it's very 17:29:19.500 --> 17:29:22.670 align:start position:0% actually a picture and it's very difficult<17:29:19.796> for<17:29:20.160> robots<17:29:20.580> to<17:29:21.256> read<17:29:22.256> this<17:29:22.500> and 17:29:22.670 --> 17:29:22.680 align:start position:0% difficult for robots to read this and 17:29:22.680 --> 17:29:24.530 align:start position:0% difficult for robots to read this and know<17:29:22.860> exactly<17:29:23.276> what<17:29:23.456> to<17:29:23.640> type<17:29:23.756> in 17:29:24.530 --> 17:29:24.540 align:start position:0% know exactly what to type in 17:29:24.540 --> 17:29:26.810 align:start position:0% know exactly what to type in so<17:29:25.140> because<17:29:25.436> of<17:29:25.740> this<17:29:25.916> the<17:29:26.276> captcha<17:29:26.640> is 17:29:26.810 --> 17:29:26.820 align:start position:0% so because of this the captcha is 17:29:26.820 --> 17:29:29.030 align:start position:0% so because of this the captcha is usually<17:29:27.116> made<17:29:27.416> different<17:29:28.080> fonts<17:29:28.560> distorted 17:29:29.030 --> 17:29:29.040 align:start position:0% usually made different fonts distorted 17:29:29.040 --> 17:29:31.730 align:start position:0% usually made different fonts distorted text<17:29:29.276> pictures<17:29:30.116> Etc<17:29:30.240> and<17:29:30.956> it<17:29:31.080> can<17:29:31.200> be<17:29:31.380> slightly 17:29:31.730 --> 17:29:31.740 align:start position:0% text pictures Etc and it can be slightly 17:29:31.740 --> 17:29:34.190 align:start position:0% text pictures Etc and it can be slightly different<17:29:31.860> for<17:29:32.220> a<17:29:32.400> human<17:29:32.580> to<17:29:32.880> read<17:29:33.060> but<17:29:33.720> not<17:29:33.900> so 17:29:34.190 --> 17:29:34.200 align:start position:0% different for a human to read but not so 17:29:34.200 --> 17:29:36.170 align:start position:0% different for a human to read but not so difficult<17:29:34.560> for<17:29:35.276> them<17:29:35.456> that<17:29:35.700> they<17:29:35.936> can't 17:29:36.170 --> 17:29:36.180 align:start position:0% difficult for them that they can't 17:29:36.180 --> 17:29:38.390 align:start position:0% difficult for them that they can't actually<17:29:36.416> type<17:29:36.660> it<17:29:36.900> in<17:29:37.020> when<17:29:37.560> you<17:29:37.680> type<17:29:37.860> in<17:29:38.096> the 17:29:38.390 --> 17:29:38.400 align:start position:0% actually type it in when you type in the 17:29:38.400 --> 17:29:41.510 align:start position:0% actually type it in when you type in the image<17:29:38.700> into<17:29:39.000> here<17:29:39.296> is<17:29:39.540> text<17:29:39.860> then<17:29:40.860> you<17:29:41.400> can 17:29:41.510 --> 17:29:41.520 align:start position:0% image into here is text then you can 17:29:41.520 --> 17:29:44.086 align:start position:0% image into here is text then you can basically<17:29:42.000> ensure<17:29:42.776> that<17:29:43.320> you<17:29:43.500> are<17:29:43.680> who<17:29:43.916> you 17:29:44.086 --> 17:29:44.096 align:start position:0% basically ensure that you are who you 17:29:44.096 --> 17:29:46.670 align:start position:0% basically ensure that you are who you say<17:29:44.276> you<17:29:44.456> are<17:29:44.700> that<17:29:45.060> you<17:29:45.296> are<17:29:45.480> a<17:29:45.900> human<17:29:46.140> rather 17:29:46.670 --> 17:29:46.680 align:start position:0% say you are that you are a human rather 17:29:46.680 --> 17:29:49.850 align:start position:0% say you are that you are a human rather than<17:29:46.860> a<17:29:47.160> bot<17:29:47.340> now<17:29:48.180> authorization<17:29:48.956> is<17:29:49.436> the<17:29:49.740> next 17:29:49.850 --> 17:29:49.860 align:start position:0% than a bot now authorization is the next 17:29:49.860 --> 17:29:52.246 align:start position:0% than a bot now authorization is the next security<17:29:50.160> level<17:29:50.456> after<17:29:50.880> authentication<17:29:51.720> it's 17:29:52.246 --> 17:29:52.256 align:start position:0% security level after authentication it's 17:29:52.256 --> 17:29:54.710 align:start position:0% security level after authentication it's the<17:29:52.500> second<17:29:52.680> a<17:29:52.980> so<17:29:53.640> once<17:29:53.936> a<17:29:54.000> user<17:29:54.360> has<17:29:54.540> been 17:29:54.710 --> 17:29:54.720 align:start position:0% the second a so once a user has been 17:29:54.720 --> 17:29:57.530 align:start position:0% the second a so once a user has been determined<17:29:55.256> authentic<17:29:55.916> we've<17:29:56.640> authenticated 17:29:57.530 --> 17:29:57.540 align:start position:0% determined authentic we've authenticated 17:29:57.540 --> 17:29:59.630 align:start position:0% determined authentic we've authenticated their<17:29:58.320> identity<17:29:58.860> they're<17:29:59.340> going<17:29:59.456> to<17:29:59.520> be 17:29:59.630 --> 17:29:59.640 align:start position:0% their identity they're going to be 17:29:59.640 --> 17:30:01.670 align:start position:0% their identity they're going to be allowed<17:29:59.880> onto<17:30:00.116> the<17:30:00.296> network<17:30:00.416> but<17:30:01.256> they<17:30:01.560> can't 17:30:01.670 --> 17:30:01.680 align:start position:0% allowed onto the network but they can't 17:30:01.680 --> 17:30:03.286 align:start position:0% allowed onto the network but they can't just<17:30:01.860> have<17:30:02.096> free<17:30:02.340> reign<17:30:02.700> and<17:30:02.880> do<17:30:03.060> whatever 17:30:03.286 --> 17:30:03.296 align:start position:0% just have free reign and do whatever 17:30:03.296 --> 17:30:05.690 align:start position:0% just have free reign and do whatever they<17:30:03.900> want<17:30:04.140> we<17:30:04.680> want<17:30:04.796> to<17:30:04.980> make<17:30:05.096> sure<17:30:05.340> that<17:30:05.520> they 17:30:05.690 --> 17:30:05.700 align:start position:0% they want we want to make sure that they 17:30:05.700 --> 17:30:08.086 align:start position:0% they want we want to make sure that they can<17:30:05.820> only<17:30:06.000> access<17:30:06.360> specific<17:30:07.020> things<17:30:07.436> remember 17:30:08.086 --> 17:30:08.096 align:start position:0% can only access specific things remember 17:30:08.096 --> 17:30:11.030 align:start position:0% can only access specific things remember that<17:30:08.520> concept<17:30:09.116> of<17:30:09.416> least<17:30:09.660> privilege<17:30:10.200> well<17:30:10.740> we 17:30:11.030 --> 17:30:11.040 align:start position:0% that concept of least privilege well we 17:30:11.040 --> 17:30:12.766 align:start position:0% that concept of least privilege well we want<17:30:11.160> to<17:30:11.340> make<17:30:11.456> sure<17:30:11.700> that<17:30:11.936> the<17:30:12.180> person<17:30:12.360> who's 17:30:12.766 --> 17:30:12.776 align:start position:0% want to make sure that the person who's 17:30:12.776 --> 17:30:14.446 align:start position:0% want to make sure that the person who's on<17:30:13.020> there<17:30:13.200> is<17:30:13.380> only<17:30:13.560> going<17:30:13.740> to<17:30:13.860> access<17:30:13.980> stuff 17:30:14.446 --> 17:30:14.456 align:start position:0% on there is only going to access stuff 17:30:14.456 --> 17:30:16.670 align:start position:0% on there is only going to access stuff that<17:30:14.640> they<17:30:14.820> are<17:30:14.936> allowed<17:30:15.180> to<17:30:15.296> access<17:30:15.680> so 17:30:16.670 --> 17:30:16.680 align:start position:0% that they are allowed to access so 17:30:16.680 --> 17:30:19.606 align:start position:0% that they are allowed to access so you're<17:30:17.220> authorized<17:30:17.936> to<17:30:18.180> access<17:30:18.596> only<17:30:19.256> certain 17:30:19.606 --> 17:30:19.616 align:start position:0% you're authorized to access only certain 17:30:19.616 --> 17:30:23.690 align:start position:0% you're authorized to access only certain things<17:30:19.980> now<17:30:20.700> there<17:30:21.180> are<17:30:21.416> users<17:30:22.256> such<17:30:22.796> as<17:30:23.040> the 17:30:23.690 --> 17:30:23.700 align:start position:0% things now there are users such as the 17:30:23.700 --> 17:30:26.266 align:start position:0% things now there are users such as the admin<17:30:24.540> who<17:30:25.020> can<17:30:25.200> generally<17:30:25.500> access<17:30:25.796> a<17:30:26.160> quiet 17:30:26.266 --> 17:30:26.276 align:start position:0% admin who can generally access a quiet 17:30:26.276 --> 17:30:28.730 align:start position:0% admin who can generally access a quiet deal<17:30:26.580> more<17:30:26.880> but<17:30:27.360> we<17:30:27.596> don't<17:30:27.720> want<17:30:28.020> for<17:30:28.560> instance 17:30:28.730 --> 17:30:28.740 align:start position:0% deal more but we don't want for instance 17:30:28.740 --> 17:30:30.946 align:start position:0% deal more but we don't want for instance the<17:30:28.980> administrator<17:30:29.520> to<17:30:29.820> have<17:30:30.000> access<17:30:30.296> to<17:30:30.720> the 17:30:30.946 --> 17:30:30.956 align:start position:0% the administrator to have access to the 17:30:30.956 --> 17:30:33.170 align:start position:0% the administrator to have access to the partner's<17:30:31.436> private<17:30:31.916> email<17:30:32.096> in<17:30:32.456> a<17:30:32.640> law<17:30:32.820> firm 17:30:33.170 --> 17:30:33.180 align:start position:0% partner's private email in a law firm 17:30:33.180 --> 17:30:35.570 align:start position:0% partner's private email in a law firm and<17:30:33.596> we<17:30:33.840> don't<17:30:33.956> want<17:30:34.320> someone<17:30:34.740> who<17:30:35.160> works<17:30:35.456> in 17:30:35.570 --> 17:30:35.580 align:start position:0% and we don't want someone who works in 17:30:35.580 --> 17:30:37.370 align:start position:0% and we don't want someone who works in accounting<17:30:36.060> to<17:30:36.296> have<17:30:36.416> access<17:30:36.660> to<17:30:36.956> marketing 17:30:37.370 --> 17:30:37.380 align:start position:0% accounting to have access to marketing 17:30:37.380 --> 17:30:40.246 align:start position:0% accounting to have access to marketing so<17:30:37.796> authorization<17:30:38.580> basically<17:30:39.180> provides<17:30:39.720> the 17:30:40.246 --> 17:30:40.256 align:start position:0% so authorization basically provides the 17:30:40.256 --> 17:30:43.246 align:start position:0% so authorization basically provides the information<17:30:40.500> on<17:30:41.040> what<17:30:41.640> the<17:30:42.116> person<17:30:42.360> or<17:30:42.660> the<17:30:42.840> ID 17:30:43.246 --> 17:30:43.256 align:start position:0% information on what the person or the ID 17:30:43.256 --> 17:30:45.766 align:start position:0% information on what the person or the ID person<17:30:43.740> who<17:30:44.096> has<17:30:44.220> been<17:30:44.400> authenticated<17:30:45.060> is 17:30:45.766 --> 17:30:45.776 align:start position:0% person who has been authenticated is 17:30:45.776 --> 17:30:49.906 align:start position:0% person who has been authenticated is authorized<17:30:46.680> to<17:30:47.640> get<17:30:48.296> access<17:30:48.660> to<17:30:49.140> now 17:30:49.906 --> 17:30:49.916 align:start position:0% authorized to get access to now 17:30:49.916 --> 17:30:52.370 align:start position:0% authorized to get access to now authorization<17:30:50.520> procedures<17:30:51.240> can<17:30:51.720> stop<17:30:51.956> users 17:30:52.370 --> 17:30:52.380 align:start position:0% authorization procedures can stop users 17:30:52.380 --> 17:30:54.650 align:start position:0% authorization procedures can stop users from<17:30:52.616> accessing<17:30:53.096> certain<17:30:53.400> datas<17:30:53.880> Services 17:30:54.650 --> 17:30:54.660 align:start position:0% from accessing certain datas Services 17:30:54.660 --> 17:30:57.470 align:start position:0% from accessing certain datas Services programs<17:30:55.740> Etc<17:30:55.916> and<17:30:56.580> can<17:30:56.700> even<17:30:56.880> stop<17:30:57.116> users 17:30:57.470 --> 17:30:57.480 align:start position:0% programs Etc and can even stop users 17:30:57.480 --> 17:30:59.746 align:start position:0% programs Etc and can even stop users from<17:30:57.720> accessing<17:30:58.200> certain<17:30:58.436> web<17:30:58.680> pages<17:30:58.916> for 17:30:59.746 --> 17:30:59.756 align:start position:0% from accessing certain web pages for 17:30:59.756 --> 17:31:02.150 align:start position:0% from accessing certain web pages for instance<17:31:00.000> we<17:31:00.480> sometimes<17:31:00.956> have<17:31:01.256> filters<17:31:01.916> that 17:31:02.150 --> 17:31:02.160 align:start position:0% instance we sometimes have filters that 17:31:02.160 --> 17:31:04.850 align:start position:0% instance we sometimes have filters that make<17:31:02.276> sure<17:31:02.456> our<17:31:02.700> kids<17:31:02.936> don't<17:31:03.240> access<17:31:03.860> very 17:31:04.850 --> 17:31:04.860 align:start position:0% make sure our kids don't access very 17:31:04.860 --> 17:31:06.710 align:start position:0% make sure our kids don't access very specific<17:31:05.276> information<17:31:05.640> unless<17:31:06.416> they<17:31:06.596> can 17:31:06.710 --> 17:31:06.720 align:start position:0% specific information unless they can 17:31:06.720 --> 17:31:08.746 align:start position:0% specific information unless they can type<17:31:06.956> in<17:31:07.200> a<17:31:07.860> password<17:31:08.040> that<17:31:08.640> would 17:31:08.746 --> 17:31:08.756 align:start position:0% type in a password that would 17:31:08.756 --> 17:31:10.850 align:start position:0% type in a password that would authenticate<17:31:09.296> that<17:31:09.540> they're<17:31:09.720> an<17:31:09.840> adult<17:31:10.020> so 17:31:10.850 --> 17:31:10.860 align:start position:0% authenticate that they're an adult so 17:31:10.860 --> 17:31:13.190 align:start position:0% authenticate that they're an adult so here's<17:31:11.160> an<17:31:11.340> example<17:31:11.640> of<17:31:12.060> what<17:31:12.296> a<17:31:12.480> denied<17:31:12.840> web 17:31:13.190 --> 17:31:13.200 align:start position:0% here's an example of what a denied web 17:31:13.200 --> 17:31:15.530 align:start position:0% here's an example of what a denied web page<17:31:13.616> might<17:31:13.980> look<17:31:14.220> like<17:31:14.400> as<17:31:14.936> you<17:31:15.060> can<17:31:15.116> see<17:31:15.240> the 17:31:15.530 --> 17:31:15.540 align:start position:0% page might look like as you can see the 17:31:15.540 --> 17:31:17.990 align:start position:0% page might look like as you can see the user<17:31:15.840> is<17:31:15.900> being<17:31:16.080> told<17:31:16.200> that<17:31:16.500> an<17:31:16.680> error<17:31:17.040> 403<17:31:17.520> has 17:31:17.990 --> 17:31:18.000 align:start position:0% user is being told that an error 403 has 17:31:18.000 --> 17:31:21.406 align:start position:0% user is being told that an error 403 has occurred<17:31:18.416> other<17:31:19.020> words<17:31:19.256> the<17:31:20.096> web<17:31:20.400> page<17:31:20.880> has 17:31:21.406 --> 17:31:21.416 align:start position:0% occurred other words the web page has 17:31:21.416 --> 17:31:24.350 align:start position:0% occurred other words the web page has been<17:31:21.596> forbidden<17:31:22.200> it<17:31:22.796> requires<17:31:23.400> you<17:31:23.880> to<17:31:24.060> log<17:31:24.240> on 17:31:24.350 --> 17:31:24.360 align:start position:0% been forbidden it requires you to log on 17:31:24.360 --> 17:31:26.390 align:start position:0% been forbidden it requires you to log on and<17:31:24.480> you<17:31:24.900> have<17:31:25.020> not<17:31:25.200> logged<17:31:25.560> on<17:31:25.616> successfully 17:31:26.390 --> 17:31:26.400 align:start position:0% and you have not logged on successfully 17:31:26.400 --> 17:31:28.606 align:start position:0% and you have not logged on successfully so<17:31:27.000> you<17:31:27.180> have<17:31:27.360> not<17:31:27.480> authenticated<17:31:28.200> who<17:31:28.500> you 17:31:28.606 --> 17:31:28.616 align:start position:0% so you have not authenticated who you 17:31:28.616 --> 17:31:30.890 align:start position:0% so you have not authenticated who you are<17:31:28.796> and<17:31:29.340> therefore<17:31:29.640> you<17:31:29.880> are<17:31:30.060> not<17:31:30.240> authorized 17:31:30.890 --> 17:31:30.900 align:start position:0% are and therefore you are not authorized 17:31:30.900 --> 17:31:33.106 align:start position:0% are and therefore you are not authorized to<17:31:31.080> have<17:31:31.380> access<17:31:31.680> to<17:31:32.220> specific<17:31:32.580> degree<17:31:33.000> of 17:31:33.106 --> 17:31:33.116 align:start position:0% to have access to specific degree of 17:31:33.116 --> 17:31:34.310 align:start position:0% to have access to specific degree of information 17:31:34.310 --> 17:31:34.320 align:start position:0% information 17:31:34.320 --> 17:31:36.650 align:start position:0% information now<17:31:34.860> users<17:31:35.456> other<17:31:35.756> than<17:31:35.936> the<17:31:36.116> administrator 17:31:36.650 --> 17:31:36.660 align:start position:0% now users other than the administrator 17:31:36.660 --> 17:31:38.810 align:start position:0% now users other than the administrator will<17:31:37.020> most<17:31:37.256> likely<17:31:37.560> not<17:31:37.860> be<17:31:38.096> authorized<17:31:38.640> to 17:31:38.810 --> 17:31:38.820 align:start position:0% will most likely not be authorized to 17:31:38.820 --> 17:31:41.210 align:start position:0% will most likely not be authorized to run<17:31:39.060> commands<17:31:39.660> in<17:31:39.900> the<17:31:40.080> command<17:31:40.380> prompt<17:31:40.680> and 17:31:41.210 --> 17:31:41.220 align:start position:0% run commands in the command prompt and 17:31:41.220 --> 17:31:42.890 align:start position:0% run commands in the command prompt and we've<17:31:41.400> looked<17:31:41.640> at<17:31:41.700> this<17:31:41.880> with<17:31:42.060> a<17:31:42.240> plus<17:31:42.480> running 17:31:42.890 --> 17:31:42.900 align:start position:0% we've looked at this with a plus running 17:31:42.900 --> 17:31:45.586 align:start position:0% we've looked at this with a plus running things<17:31:43.320> in<17:31:43.680> an<17:31:43.860> administrator<17:31:44.400> mode<17:31:44.756> if<17:31:45.480> the 17:31:45.586 --> 17:31:45.596 align:start position:0% things in an administrator mode if the 17:31:45.596 --> 17:31:46.850 align:start position:0% things in an administrator mode if the user<17:31:45.900> does<17:31:46.080> they're<17:31:46.380> probably<17:31:46.616> going<17:31:46.796> to 17:31:46.850 --> 17:31:46.860 align:start position:0% user does they're probably going to 17:31:46.860 --> 17:31:48.650 align:start position:0% user does they're probably going to receive<17:31:47.096> an<17:31:47.276> error<17:31:47.580> that<17:31:47.880> looks<17:31:48.240> like<17:31:48.360> this 17:31:48.650 --> 17:31:48.660 align:start position:0% receive an error that looks like this 17:31:48.660 --> 17:31:51.170 align:start position:0% receive an error that looks like this this<17:31:49.320> command<17:31:49.680> prompt<17:31:49.980> has<17:31:50.160> been<17:31:50.400> disabled<17:31:50.936> by 17:31:51.170 --> 17:31:51.180 align:start position:0% this command prompt has been disabled by 17:31:51.180 --> 17:31:53.330 align:start position:0% this command prompt has been disabled by your<17:31:51.296> administrator<17:31:51.900> the<17:31:52.616> administrator<17:31:53.040> can 17:31:53.330 --> 17:31:53.340 align:start position:0% your administrator the administrator can 17:31:53.340 --> 17:31:55.370 align:start position:0% your administrator the administrator can deny<17:31:53.756> every<17:31:54.116> other<17:31:54.360> user<17:31:54.660> on<17:31:54.840> the<17:31:54.900> network<17:31:55.020> the 17:31:55.370 --> 17:31:55.380 align:start position:0% deny every other user on the network the 17:31:55.380 --> 17:31:56.926 align:start position:0% deny every other user on the network the ability<17:31:55.616> to<17:31:55.916> use<17:31:56.040> the<17:31:56.276> command<17:31:56.580> prompt 17:31:56.926 --> 17:31:56.936 align:start position:0% ability to use the command prompt 17:31:56.936 --> 17:31:58.426 align:start position:0% ability to use the command prompt because<17:31:57.360> they<17:31:57.596> could<17:31:57.776> do<17:31:57.900> something<17:31:58.140> that 17:31:58.426 --> 17:31:58.436 align:start position:0% because they could do something that 17:31:58.436 --> 17:32:00.890 align:start position:0% because they could do something that they<17:31:58.680> are<17:31:58.796> not<17:31:58.916> authorized<17:31:59.700> to<17:31:59.880> do<17:32:00.060> so<17:32:00.596> it's<17:32:00.720> up 17:32:00.890 --> 17:32:00.900 align:start position:0% they are not authorized to do so it's up 17:32:00.900 --> 17:32:02.390 align:start position:0% they are not authorized to do so it's up to<17:32:01.020> the<17:32:01.140> administrator<17:32:01.616> to<17:32:01.860> make<17:32:02.040> sure<17:32:02.160> that 17:32:02.390 --> 17:32:02.400 align:start position:0% to the administrator to make sure that 17:32:02.400 --> 17:32:04.850 align:start position:0% to the administrator to make sure that only<17:32:02.640> authorized<17:32:03.360> users<17:32:03.720> can<17:32:04.320> access<17:32:04.500> the 17:32:04.850 --> 17:32:04.860 align:start position:0% only authorized users can access the 17:32:04.860 --> 17:32:07.490 align:start position:0% only authorized users can access the command<17:32:05.220> prompt<17:32:05.640> or<17:32:06.116> do<17:32:06.480> other<17:32:06.720> things<17:32:07.020> on<17:32:07.380> the 17:32:07.490 --> 17:32:07.500 align:start position:0% command prompt or do other things on the 17:32:07.500 --> 17:32:09.350 align:start position:0% command prompt or do other things on the computer<17:32:07.680> or<17:32:07.980> on<17:32:08.096> the<17:32:08.220> network<17:32:08.400> for<17:32:09.116> instance 17:32:09.350 --> 17:32:09.360 align:start position:0% computer or on the network for instance 17:32:09.360 --> 17:32:11.690 align:start position:0% computer or on the network for instance rebooting<17:32:10.020> computers<17:32:10.500> accessing<17:32:11.220> servers 17:32:11.690 --> 17:32:11.700 align:start position:0% rebooting computers accessing servers 17:32:11.700 --> 17:32:13.246 align:start position:0% rebooting computers accessing servers and<17:32:12.000> so<17:32:12.180> on 17:32:13.246 --> 17:32:13.256 align:start position:0% and so on 17:32:13.256 --> 17:32:15.850 align:start position:0% and so on now<17:32:13.860> the<17:32:14.096> final<17:32:14.276> a<17:32:14.700> we<17:32:15.296> talked<17:32:15.596> about 17:32:15.850 --> 17:32:15.860 align:start position:0% now the final a we talked about 17:32:15.860 --> 17:32:19.266 align:start position:0% now the final a we talked about authorization<17:32:16.860> and<17:32:17.340> authentication<17:32:18.080> is 17:32:19.266 --> 17:32:19.276 align:start position:0% authorization and authentication is 17:32:19.276 --> 17:32:22.970 align:start position:0% authorization and authentication is accounting<17:32:20.480> accounting<17:32:21.480> is<17:32:21.956> not<17:32:22.256> the<17:32:22.560> same<17:32:22.680> as 17:32:22.970 --> 17:32:22.980 align:start position:0% accounting accounting is not the same as 17:32:22.980 --> 17:32:25.850 align:start position:0% accounting accounting is not the same as in<17:32:23.276> bookkeeping<17:32:24.060> it's<17:32:24.956> Accounting<17:32:25.616> in<17:32:25.740> the 17:32:25.850 --> 17:32:25.860 align:start position:0% in bookkeeping it's Accounting in the 17:32:25.860 --> 17:32:27.406 align:start position:0% in bookkeeping it's Accounting in the sense<17:32:26.040> that<17:32:26.220> everything<17:32:26.520> a<17:32:26.756> user<17:32:27.060> does<17:32:27.180> while 17:32:27.406 --> 17:32:27.416 align:start position:0% sense that everything a user does while 17:32:27.416 --> 17:32:29.266 align:start position:0% sense that everything a user does while on<17:32:27.596> the<17:32:27.776> network<17:32:27.900> has<17:32:28.256> to<17:32:28.436> be<17:32:28.560> accounted<17:32:29.096> for 17:32:29.266 --> 17:32:29.276 align:start position:0% on the network has to be accounted for 17:32:29.276 --> 17:32:31.670 align:start position:0% on the network has to be accounted for and<17:32:29.640> carefully<17:32:30.060> watched<17:32:30.540> this<17:32:31.140> is<17:32:31.320> sometimes 17:32:31.670 --> 17:32:31.680 align:start position:0% and carefully watched this is sometimes 17:32:31.680 --> 17:32:34.310 align:start position:0% and carefully watched this is sometimes also<17:32:32.096> called<17:32:32.400> auditing 17:32:34.310 --> 17:32:34.320 align:start position:0% also called auditing 17:32:34.320 --> 17:32:37.926 align:start position:0% also called auditing another<17:32:34.980> term<17:32:35.880> that<17:32:36.360> gets<17:32:37.020> back<17:32:37.200> to 17:32:37.926 --> 17:32:37.936 align:start position:0% another term that gets back to 17:32:37.936 --> 17:32:40.426 align:start position:0% another term that gets back to accounting<17:32:38.936> in<17:32:39.240> a<17:32:39.416> sort<17:32:39.596> of<17:32:39.720> financial<17:32:39.956> sense 17:32:40.426 --> 17:32:40.436 align:start position:0% accounting in a sort of financial sense 17:32:40.436 --> 17:32:42.530 align:start position:0% accounting in a sort of financial sense but<17:32:40.796> it<17:32:40.916> means<17:32:41.160> something<17:32:41.276> different<17:32:41.640> the 17:32:42.530 --> 17:32:42.540 align:start position:0% but it means something different the 17:32:42.540 --> 17:32:45.586 align:start position:0% but it means something different the users<17:32:42.840> on<17:32:43.080> a<17:32:43.200> network<17:32:43.520> uh<17:32:44.520> can<17:32:44.820> often<17:32:45.180> be<17:32:45.360> one 17:32:45.586 --> 17:32:45.596 align:start position:0% users on a network uh can often be one 17:32:45.596 --> 17:32:48.170 align:start position:0% users on a network uh can often be one of<17:32:45.720> the<17:32:45.900> biggest<17:32:46.140> of<17:32:46.796> our<17:32:47.220> security<17:32:47.400> concerns 17:32:48.170 --> 17:32:48.180 align:start position:0% of the biggest of our security concerns 17:32:48.180 --> 17:32:50.390 align:start position:0% of the biggest of our security concerns most<17:32:48.840> of<17:32:49.020> the<17:32:49.140> time<17:32:49.320> someone<17:32:49.796> is<17:32:50.096> going<17:32:50.276> to 17:32:50.390 --> 17:32:50.400 align:start position:0% most of the time someone is going to 17:32:50.400 --> 17:32:52.310 align:start position:0% most of the time someone is going to hack<17:32:50.580> our<17:32:50.756> network<17:32:50.936> from<17:32:51.360> inside<17:32:51.596> rather<17:32:52.140> than 17:32:52.310 --> 17:32:52.320 align:start position:0% hack our network from inside rather than 17:32:52.320 --> 17:32:54.766 align:start position:0% hack our network from inside rather than outside<17:32:52.740> and<17:32:53.640> so<17:32:53.820> keeping<17:32:54.180> track<17:32:54.360> of<17:32:54.540> how 17:32:54.766 --> 17:32:54.776 align:start position:0% outside and so keeping track of how 17:32:54.776 --> 17:32:56.390 align:start position:0% outside and so keeping track of how users<17:32:55.140> spend<17:32:55.500> their<17:32:55.616> time<17:32:55.796> is<17:32:56.040> one<17:32:56.220> of<17:32:56.340> the 17:32:56.390 --> 17:32:56.400 align:start position:0% users spend their time is one of the 17:32:56.400 --> 17:32:57.710 align:start position:0% users spend their time is one of the most<17:32:56.520> important<17:32:56.936> aspects<17:32:57.416> of<17:32:57.540> network 17:32:57.710 --> 17:32:57.720 align:start position:0% most important aspects of network 17:32:57.720 --> 17:33:00.230 align:start position:0% most important aspects of network security<17:32:58.160> the<17:32:59.160> accounting<17:32:59.580> function<17:32:59.880> of<17:33:00.116> the 17:33:00.230 --> 17:33:00.240 align:start position:0% security the accounting function of the 17:33:00.240 --> 17:33:02.510 align:start position:0% security the accounting function of the AAA<17:33:00.660> servers<17:33:01.020> to<17:33:01.200> do<17:33:01.320> exactly<17:33:01.680> that<17:33:01.916> it 17:33:02.510 --> 17:33:02.520 align:start position:0% AAA servers to do exactly that it 17:33:02.520 --> 17:33:04.370 align:start position:0% AAA servers to do exactly that it watches<17:33:03.000> all<17:33:03.360> of<17:33:03.480> the<17:33:03.596> users<17:33:03.840> and<17:33:04.020> monitors 17:33:04.370 --> 17:33:04.380 align:start position:0% watches all of the users and monitors 17:33:04.380 --> 17:33:06.530 align:start position:0% watches all of the users and monitors their<17:33:04.680> activity<17:33:05.096> as<17:33:05.756> well<17:33:05.936> as<17:33:06.116> all<17:33:06.360> the 17:33:06.530 --> 17:33:06.540 align:start position:0% their activity as well as all the 17:33:06.540 --> 17:33:09.106 align:start position:0% their activity as well as all the resources<17:33:07.256> they're<17:33:07.560> using<17:33:07.916> these<17:33:08.700> resources 17:33:09.106 --> 17:33:09.116 align:start position:0% resources they're using these resources 17:33:09.116 --> 17:33:11.150 align:start position:0% resources they're using these resources could<17:33:09.360> include<17:33:09.660> stuff<17:33:09.900> like<17:33:10.080> bandwidth<17:33:10.616> CPU 17:33:11.150 --> 17:33:11.160 align:start position:0% could include stuff like bandwidth CPU 17:33:11.160 --> 17:33:13.786 align:start position:0% could include stuff like bandwidth CPU usage<17:33:11.580> and<17:33:11.880> a<17:33:12.000> lot<17:33:12.116> more<17:33:12.360> not<17:33:12.900> to<17:33:13.080> mention<17:33:13.320> what 17:33:13.786 --> 17:33:13.796 align:start position:0% usage and a lot more not to mention what 17:33:13.796 --> 17:33:16.190 align:start position:0% usage and a lot more not to mention what websites<17:33:14.400> they're<17:33:14.580> accessing<17:33:15.060> and<17:33:15.360> so<17:33:15.480> on<17:33:15.660> now 17:33:16.190 --> 17:33:16.200 align:start position:0% websites they're accessing and so on now 17:33:16.200 --> 17:33:17.630 align:start position:0% websites they're accessing and so on now some<17:33:16.380> people<17:33:16.500> say<17:33:16.796> hey<17:33:17.096> wait<17:33:17.340> you're 17:33:17.630 --> 17:33:17.640 align:start position:0% some people say hey wait you're 17:33:17.640 --> 17:33:19.310 align:start position:0% some people say hey wait you're infringing<17:33:18.116> on<17:33:18.296> my<17:33:18.540> right<17:33:18.776> to<17:33:18.956> use<17:33:19.140> the 17:33:19.310 --> 17:33:19.320 align:start position:0% infringing on my right to use the 17:33:19.320 --> 17:33:21.286 align:start position:0% infringing on my right to use the internet<17:33:19.436> but<17:33:20.040> if<17:33:20.220> you<17:33:20.400> are<17:33:20.580> at<17:33:20.880> your<17:33:21.116> company 17:33:21.286 --> 17:33:21.296 align:start position:0% internet but if you are at your company 17:33:21.296 --> 17:33:23.810 align:start position:0% internet but if you are at your company using<17:33:21.776> your<17:33:21.956> company's<17:33:22.320> internet<17:33:22.560> then<17:33:23.400> you 17:33:23.810 --> 17:33:23.820 align:start position:0% using your company's internet then you 17:33:23.820 --> 17:33:25.490 align:start position:0% using your company's internet then you have<17:33:23.936> signed<17:33:24.480> most<17:33:24.720> likely<17:33:25.020> an<17:33:25.200> agreement 17:33:25.490 --> 17:33:25.500 align:start position:0% have signed most likely an agreement 17:33:25.500 --> 17:33:26.746 align:start position:0% have signed most likely an agreement saying<17:33:25.916> you're<17:33:26.040> only<17:33:26.160> going<17:33:26.276> to<17:33:26.340> use<17:33:26.456> it<17:33:26.640> for 17:33:26.746 --> 17:33:26.756 align:start position:0% saying you're only going to use it for 17:33:26.756 --> 17:33:28.310 align:start position:0% saying you're only going to use it for specific<17:33:27.000> purposes<17:33:27.540> and<17:33:27.956> you've<17:33:28.200> probably 17:33:28.310 --> 17:33:28.320 align:start position:0% specific purposes and you've probably 17:33:28.320 --> 17:33:29.990 align:start position:0% specific purposes and you've probably also<17:33:28.616> signed<17:33:28.916> an<17:33:29.096> agreement<17:33:29.580> whether<17:33:29.880> you 17:33:29.990 --> 17:33:30.000 align:start position:0% also signed an agreement whether you 17:33:30.000 --> 17:33:31.786 align:start position:0% also signed an agreement whether you know<17:33:30.116> it<17:33:30.296> or<17:33:30.416> not<17:33:30.540> that<17:33:31.020> allows<17:33:31.320> them<17:33:31.500> to 17:33:31.786 --> 17:33:31.796 align:start position:0% know it or not that allows them to 17:33:31.796 --> 17:33:33.470 align:start position:0% know it or not that allows them to monitor<17:33:32.160> you<17:33:32.400> while<17:33:32.820> you're<17:33:33.000> using<17:33:33.296> the 17:33:33.470 --> 17:33:33.480 align:start position:0% monitor you while you're using the 17:33:33.480 --> 17:33:34.670 align:start position:0% monitor you while you're using the internet 17:33:34.670 --> 17:33:34.680 align:start position:0% internet 17:33:34.680 --> 17:33:37.070 align:start position:0% internet so<17:33:35.340> here's<17:33:35.880> representation<17:33:36.416> of<17:33:36.720> what<17:33:36.956> the 17:33:37.070 --> 17:33:37.080 align:start position:0% so here's representation of what the 17:33:37.080 --> 17:33:39.050 align:start position:0% so here's representation of what the accounting<17:33:37.436> function<17:33:37.680> of<17:33:37.860> AAA<17:33:38.456> server<17:33:38.820> does 17:33:39.050 --> 17:33:39.060 align:start position:0% accounting function of AAA server does 17:33:39.060 --> 17:33:41.570 align:start position:0% accounting function of AAA server does it<17:33:39.660> oversees<17:33:40.200> everything<17:33:40.916> the<17:33:41.160> users<17:33:41.456> are 17:33:41.570 --> 17:33:41.580 align:start position:0% it oversees everything the users are 17:33:41.580 --> 17:33:43.190 align:start position:0% it oversees everything the users are doing<17:33:41.756> and<17:33:41.936> keeps<17:33:42.296> track<17:33:42.480> of<17:33:42.776> what<17:33:43.020> the 17:33:43.190 --> 17:33:43.200 align:start position:0% doing and keeps track of what the 17:33:43.200 --> 17:33:45.286 align:start position:0% doing and keeps track of what the resources<17:33:43.680> are<17:33:43.860> those<17:33:44.340> users<17:33:44.700> are<17:33:44.820> taking<17:33:45.000> up 17:33:45.286 --> 17:33:45.296 align:start position:0% resources are those users are taking up 17:33:45.296 --> 17:33:48.586 align:start position:0% resources are those users are taking up and<17:33:45.776> how<17:33:45.956> they're<17:33:46.140> spending<17:33:46.560> their<17:33:46.740> time 17:33:48.586 --> 17:33:48.596 align:start position:0% and how they're spending their time 17:33:48.596 --> 17:33:50.570 align:start position:0% and how they're spending their time now<17:33:49.020> this<17:33:49.320> was<17:33:49.500> a<17:33:49.740> short<17:33:49.860> module<17:33:50.276> but<17:33:50.456> it 17:33:50.570 --> 17:33:50.580 align:start position:0% now this was a short module but it 17:33:50.580 --> 17:33:52.606 align:start position:0% now this was a short module but it discussed<17:33:51.000> the<17:33:51.180> AAA<17:33:51.660> and<17:33:52.200> these<17:33:52.380> are<17:33:52.436> three 17:33:52.606 --> 17:33:52.616 align:start position:0% discussed the AAA and these are three 17:33:52.616 --> 17:33:54.350 align:start position:0% discussed the AAA and these are three really<17:33:52.980> important<17:33:53.340> Concepts<17:33:53.820> you<17:33:54.060> need<17:33:54.180> to 17:33:54.350 --> 17:33:54.360 align:start position:0% really important Concepts you need to 17:33:54.360 --> 17:33:55.850 align:start position:0% really important Concepts you need to know<17:33:54.540> and<17:33:54.776> understand<17:33:54.956> for<17:33:55.380> Network<17:33:55.560> plus 17:33:55.850 --> 17:33:55.860 align:start position:0% know and understand for Network plus 17:33:55.860 --> 17:33:58.266 align:start position:0% know and understand for Network plus first<17:33:56.756> we<17:33:57.000> looked<17:33:57.296> at<17:33:57.360> authentication 17:33:58.266 --> 17:33:58.276 align:start position:0% first we looked at authentication 17:33:58.276 --> 17:34:01.490 align:start position:0% first we looked at authentication authentication<17:33:59.276> make<17:34:00.060> sure<17:34:00.296> that<17:34:01.200> the 17:34:01.490 --> 17:34:01.500 align:start position:0% authentication make sure that the 17:34:01.500 --> 17:34:04.426 align:start position:0% authentication make sure that the identity<17:34:01.980> has<17:34:02.400> been<17:34:02.580> verified<17:34:03.020> this<17:34:04.020> is<17:34:04.140> just 17:34:04.426 --> 17:34:04.436 align:start position:0% identity has been verified this is just 17:34:04.436 --> 17:34:08.150 align:start position:0% identity has been verified this is just like<17:34:04.680> in<17:34:05.160> a<17:34:05.340> metaphor<17:34:05.720> your<17:34:06.720> driver's<17:34:07.140> license 17:34:08.150 --> 17:34:08.160 align:start position:0% like in a metaphor your driver's license 17:34:08.160 --> 17:34:13.130 align:start position:0% like in a metaphor your driver's license which<17:34:08.756> has<17:34:09.000> a<17:34:09.296> picture<17:34:09.416> ID 17:34:13.130 --> 17:34:13.140 align:start position:0% 17:34:13.140 --> 17:34:15.946 align:start position:0% next<17:34:13.680> we<17:34:13.916> talked<17:34:14.160> about<17:34:14.220> authorization<17:34:15.060> this 17:34:15.946 --> 17:34:15.956 align:start position:0% next we talked about authorization this 17:34:15.956 --> 17:34:20.570 align:start position:0% next we talked about authorization this is<17:34:16.200> what<17:34:16.796> you<17:34:17.040> are<17:34:17.220> allowed<17:34:17.756> to<17:34:18.720> do 17:34:20.570 --> 17:34:20.580 align:start position:0% is what you are allowed to do 17:34:20.580 --> 17:34:22.246 align:start position:0% is what you are allowed to do this<17:34:21.116> could<17:34:21.240> be<17:34:21.416> just<17:34:21.720> like<17:34:21.956> you're 17:34:22.246 --> 17:34:22.256 align:start position:0% this could be just like you're 17:34:22.256 --> 17:34:23.926 align:start position:0% this could be just like you're authorized<17:34:22.916> if<17:34:23.160> you<17:34:23.276> have<17:34:23.400> your<17:34:23.580> driver's 17:34:23.926 --> 17:34:23.936 align:start position:0% authorized if you have your driver's 17:34:23.936 --> 17:34:26.870 align:start position:0% authorized if you have your driver's license<17:34:24.180> and<17:34:24.900> you're<17:34:25.140> 21<17:34:25.320> and<17:34:25.796> up<17:34:25.980> in<17:34:26.756> the 17:34:26.870 --> 17:34:26.880 align:start position:0% license and you're 21 and up in the 17:34:26.880 --> 17:34:32.210 align:start position:0% license and you're 21 and up in the United<17:34:27.000> States<17:34:27.560> to<17:34:28.560> drink 17:34:32.210 --> 17:34:32.220 align:start position:0% 17:34:32.220 --> 17:34:33.710 align:start position:0% so 17:34:33.710 --> 17:34:33.720 align:start position:0% so 17:34:33.720 --> 17:34:35.510 align:start position:0% so authentication<17:34:34.616> is<17:34:34.860> provided<17:34:35.220> by<17:34:35.400> the 17:34:35.510 --> 17:34:35.520 align:start position:0% authentication is provided by the 17:34:35.520 --> 17:34:37.130 align:start position:0% authentication is provided by the driver's<17:34:35.880> license<17:34:36.060> you<17:34:36.296> are<17:34:36.480> who<17:34:36.660> you<17:34:36.776> say<17:34:36.956> you 17:34:37.130 --> 17:34:37.140 align:start position:0% driver's license you are who you say you 17:34:37.140 --> 17:34:39.050 align:start position:0% driver's license you are who you say you are<17:34:37.320> and<17:34:37.680> then<17:34:37.796> authorization<17:34:38.400> says<17:34:38.820> whether 17:34:39.050 --> 17:34:39.060 align:start position:0% are and then authorization says whether 17:34:39.060 --> 17:34:40.730 align:start position:0% are and then authorization says whether or<17:34:39.240> not<17:34:39.296> you're<17:34:39.540> allowed<17:34:39.776> to<17:34:39.900> drink<17:34:40.140> or<17:34:40.500> even 17:34:40.730 --> 17:34:40.740 align:start position:0% or not you're allowed to drink or even 17:34:40.740 --> 17:34:43.906 align:start position:0% or not you're allowed to drink or even drive<17:34:41.360> depending<17:34:42.360> on<17:34:42.660> your<17:34:43.140> age<17:34:43.380> and<17:34:43.740> a 17:34:43.906 --> 17:34:43.916 align:start position:0% drive depending on your age and a 17:34:43.916 --> 17:34:46.810 align:start position:0% drive depending on your age and a variety<17:34:44.160> of<17:34:44.276> other<17:34:44.756> circumstances<17:34:45.740> finally 17:34:46.810 --> 17:34:46.820 align:start position:0% variety of other circumstances finally 17:34:46.820 --> 17:34:50.086 align:start position:0% variety of other circumstances finally accounting<17:34:47.820> is<17:34:48.360> basically<17:34:48.720> a<17:34:49.140> log 17:34:50.086 --> 17:34:50.096 align:start position:0% accounting is basically a log 17:34:50.096 --> 17:34:53.390 align:start position:0% accounting is basically a log of<17:34:50.640> what<17:34:50.820> you<17:34:51.000> do 17:34:53.390 --> 17:34:53.400 align:start position:0% 17:34:53.400 --> 17:34:55.130 align:start position:0% if<17:34:53.936> you<17:34:54.060> get<17:34:54.240> in<17:34:54.360> trouble<17:34:54.540> with<17:34:54.840> the<17:34:54.956> law 17:34:55.130 --> 17:34:55.140 align:start position:0% if you get in trouble with the law 17:34:55.140 --> 17:34:57.350 align:start position:0% if you get in trouble with the law that's<17:34:55.616> put<17:34:55.796> on<17:34:55.980> a<17:34:56.096> record<17:34:56.220> that<17:34:56.936> way<17:34:57.116> if 17:34:57.350 --> 17:34:57.360 align:start position:0% that's put on a record that way if 17:34:57.360 --> 17:34:58.850 align:start position:0% that's put on a record that way if you're<17:34:57.416> pulled<17:34:57.776> over<17:34:57.840> by<17:34:58.140> a<17:34:58.320> policeman<17:34:58.616> let's 17:34:58.850 --> 17:34:58.860 align:start position:0% you're pulled over by a policeman let's 17:34:58.860 --> 17:35:01.070 align:start position:0% you're pulled over by a policeman let's say<17:34:59.040> for<17:34:59.220> speeding<17:34:59.700> they<17:35:00.180> can<17:35:00.416> scan<17:35:00.776> your 17:35:01.070 --> 17:35:01.080 align:start position:0% say for speeding they can scan your 17:35:01.080 --> 17:35:03.350 align:start position:0% say for speeding they can scan your driver's<17:35:01.436> license<17:35:01.616> and<17:35:02.456> see<17:35:02.580> if<17:35:02.756> you<17:35:02.936> have<17:35:03.116> any 17:35:03.350 --> 17:35:03.360 align:start position:0% driver's license and see if you have any 17:35:03.360 --> 17:35:05.210 align:start position:0% driver's license and see if you have any outstanding<17:35:03.900> warrants<17:35:04.320> or<17:35:04.680> if<17:35:04.916> you've<17:35:05.040> been 17:35:05.210 --> 17:35:05.220 align:start position:0% outstanding warrants or if you've been 17:35:05.220 --> 17:35:07.746 align:start position:0% outstanding warrants or if you've been pulled<17:35:05.580> over<17:35:05.640> in<17:35:05.936> the<17:35:06.116> past<17:35:06.240> in<17:35:07.140> this<17:35:07.256> way 17:35:07.746 --> 17:35:07.756 align:start position:0% pulled over in the past in this way 17:35:07.756 --> 17:35:10.310 align:start position:0% pulled over in the past in this way accounting<17:35:08.756> provides<17:35:09.416> a<17:35:09.776> background 17:35:10.310 --> 17:35:10.320 align:start position:0% accounting provides a background 17:35:10.320 --> 17:35:12.286 align:start position:0% accounting provides a background information<17:35:10.680> on<17:35:11.220> you<17:35:11.340> and<17:35:11.640> can<17:35:11.820> make<17:35:12.000> sure 17:35:12.286 --> 17:35:12.296 align:start position:0% information on you and can make sure 17:35:12.296 --> 17:35:13.850 align:start position:0% information on you and can make sure that<17:35:12.720> we<17:35:12.840> know<17:35:12.956> what<17:35:13.200> you're<17:35:13.320> doing<17:35:13.500> on<17:35:13.740> the 17:35:13.850 --> 17:35:13.860 align:start position:0% that we know what you're doing on the 17:35:13.860 --> 17:35:15.106 align:start position:0% that we know what you're doing on the network<17:35:13.980> what<17:35:14.456> information<17:35:14.700> you're 17:35:15.106 --> 17:35:15.116 align:start position:0% network what information you're 17:35:15.116 --> 17:35:17.570 align:start position:0% network what information you're accessing<17:35:15.660> and<17:35:16.256> also<17:35:16.500> make<17:35:16.740> sure<17:35:16.980> when<17:35:17.340> you're 17:35:17.570 --> 17:35:17.580 align:start position:0% accessing and also make sure when you're 17:35:17.580 --> 17:35:20.030 align:start position:0% accessing and also make sure when you're accessing<17:35:18.000> it<17:35:18.180> and<17:35:18.360> so<17:35:18.540> on<17:35:18.720> let's<17:35:19.256> say<17:35:19.436> that<17:35:19.740> we 17:35:20.030 --> 17:35:20.040 align:start position:0% accessing it and so on let's say that we 17:35:20.040 --> 17:35:23.390 align:start position:0% accessing it and so on let's say that we have<17:35:20.220> someone<17:35:20.520> rob<17:35:21.000> our<17:35:21.480> store<17:35:21.860> at<17:35:22.860> midnight 17:35:23.390 --> 17:35:23.400 align:start position:0% have someone rob our store at midnight 17:35:23.400 --> 17:35:26.510 align:start position:0% have someone rob our store at midnight and<17:35:24.240> the<17:35:24.416> store<17:35:24.596> is<17:35:24.776> closed<17:35:25.200> well<17:35:25.796> if<17:35:26.220> your 17:35:26.510 --> 17:35:26.520 align:start position:0% and the store is closed well if your 17:35:26.520 --> 17:35:28.906 align:start position:0% and the store is closed well if your security<17:35:26.756> card<17:35:27.180> was<17:35:27.660> used<17:35:27.840> to<17:35:28.140> get<17:35:28.320> access<17:35:28.560> to 17:35:28.906 --> 17:35:28.916 align:start position:0% security card was used to get access to 17:35:28.916 --> 17:35:30.946 align:start position:0% security card was used to get access to the<17:35:29.096> store<17:35:29.276> then<17:35:29.820> we<17:35:30.060> know<17:35:30.240> that<17:35:30.416> either<17:35:30.660> you 17:35:30.946 --> 17:35:30.956 align:start position:0% the store then we know that either you 17:35:30.956 --> 17:35:32.990 align:start position:0% the store then we know that either you rob<17:35:31.200> the<17:35:31.436> store<17:35:31.680> or<17:35:32.040> someone<17:35:32.276> who<17:35:32.520> stole<17:35:32.756> your 17:35:32.990 --> 17:35:33.000 align:start position:0% rob the store or someone who stole your 17:35:33.000 --> 17:35:38.890 align:start position:0% rob the store or someone who stole your security<17:35:33.240> card<17:35:33.596> robbed<17:35:34.080> your<17:35:34.200> store 17:35:38.890 --> 17:35:38.900 align:start position:0% 17:35:38.900 --> 17:35:47.530 align:start position:0% [Music] 17:35:47.530 --> 17:35:47.540 align:start position:0% [Music] 17:35:47.540 --> 17:36:00.230 align:start position:0% [Music] thank<17:35:48.540> you 17:36:00.230 --> 17:36:00.240 align:start position:0% 17:36:00.240 --> 17:36:04.606 align:start position:0% network<17:36:00.900> security<17:36:01.520> system<17:36:02.520> security<17:36:03.060> tools 17:36:04.606 --> 17:36:04.616 align:start position:0% network security system security tools 17:36:04.616 --> 17:36:06.946 align:start position:0% network security system security tools in<17:36:05.040> the<17:36:05.220> last<17:36:05.276> module<17:36:05.820> we<17:36:06.240> talked<17:36:06.480> about<17:36:06.596> the 17:36:06.946 --> 17:36:06.956 align:start position:0% in the last module we talked about the 17:36:06.956 --> 17:36:10.370 align:start position:0% in the last module we talked about the AAA<17:36:07.456> authentication<17:36:08.660> authorization<17:36:09.660> and 17:36:10.370 --> 17:36:10.380 align:start position:0% AAA authentication authorization and 17:36:10.380 --> 17:36:12.830 align:start position:0% AAA authentication authorization and accounting<17:36:10.860> there's<17:36:11.820> three<17:36:12.180> aspects<17:36:12.720> of 17:36:12.830 --> 17:36:12.840 align:start position:0% accounting there's three aspects of 17:36:12.840 --> 17:36:14.630 align:start position:0% accounting there's three aspects of security<17:36:13.140> are<17:36:13.680> really<17:36:13.980> important<17:36:14.276> to<17:36:14.456> running 17:36:14.630 --> 17:36:14.640 align:start position:0% security are really important to running 17:36:14.640 --> 17:36:16.906 align:start position:0% security are really important to running a<17:36:14.936> safe<17:36:15.060> and<17:36:15.240> secure<17:36:15.540> network<17:36:15.840> but<17:36:16.560> there<17:36:16.796> are 17:36:16.906 --> 17:36:16.916 align:start position:0% a safe and secure network but there are 17:36:16.916 --> 17:36:19.550 align:start position:0% a safe and secure network but there are also<17:36:17.160> some<17:36:17.520> security<17:36:17.880> tools<17:36:18.720> and<17:36:19.080> programs 17:36:19.550 --> 17:36:19.560 align:start position:0% also some security tools and programs 17:36:19.560 --> 17:36:21.406 align:start position:0% also some security tools and programs that<17:36:20.096> prove<17:36:20.456> really<17:36:20.640> useful<17:36:21.000> when<17:36:21.296> we're 17:36:21.406 --> 17:36:21.416 align:start position:0% that prove really useful when we're 17:36:21.416 --> 17:36:23.630 align:start position:0% that prove really useful when we're trying<17:36:21.596> to<17:36:21.776> put<17:36:21.900> these<17:36:22.080> into<17:36:22.256> action<17:36:22.740> most 17:36:23.630 --> 17:36:23.640 align:start position:0% trying to put these into action most 17:36:23.640 --> 17:36:26.390 align:start position:0% trying to put these into action most notably<17:36:24.116> we're<17:36:24.660> going<17:36:24.900> to<17:36:25.080> talk<17:36:25.380> in<17:36:26.096> this 17:36:26.390 --> 17:36:26.400 align:start position:0% notably we're going to talk in this 17:36:26.400 --> 17:36:29.210 align:start position:0% notably we're going to talk in this module<17:36:26.880> about<17:36:27.380> firewalls<17:36:28.380> and<17:36:28.616> antivirus 17:36:29.210 --> 17:36:29.220 align:start position:0% module about firewalls and antivirus 17:36:29.220 --> 17:36:31.130 align:start position:0% module about firewalls and antivirus software<17:36:29.580> there<17:36:30.180> are<17:36:30.296> a<17:36:30.296> lot<17:36:30.416> of<17:36:30.480> other<17:36:30.596> tools 17:36:31.130 --> 17:36:31.140 align:start position:0% software there are a lot of other tools 17:36:31.140 --> 17:36:33.230 align:start position:0% software there are a lot of other tools and<17:36:31.616> pieces<17:36:32.096> of<17:36:32.276> software<17:36:32.640> that<17:36:32.880> we<17:36:33.000> can<17:36:33.116> use 17:36:33.230 --> 17:36:33.240 align:start position:0% and pieces of software that we can use 17:36:33.240 --> 17:36:36.050 align:start position:0% and pieces of software that we can use and<17:36:33.540> we'll<17:36:33.660> talk<17:36:33.840> about<17:36:34.020> these<17:36:34.500> in<17:36:34.860> a<17:36:35.040> bit<17:36:35.160> but 17:36:36.050 --> 17:36:36.060 align:start position:0% and we'll talk about these in a bit but 17:36:36.060 --> 17:36:37.906 align:start position:0% and we'll talk about these in a bit but these<17:36:36.720> two<17:36:36.840> come<17:36:37.080> up<17:36:37.256> quite<17:36:37.436> a<17:36:37.560> bit<17:36:37.680> on<17:36:37.796> the 17:36:37.906 --> 17:36:37.916 align:start position:0% these two come up quite a bit on the 17:36:37.916 --> 17:36:39.530 align:start position:0% these two come up quite a bit on the network<17:36:37.980> plus<17:36:38.276> exam<17:36:38.756> especially<17:36:39.360> because 17:36:39.530 --> 17:36:39.540 align:start position:0% network plus exam especially because 17:36:39.540 --> 17:36:41.330 align:start position:0% network plus exam especially because they're<17:36:39.840> the<17:36:40.080> two<17:36:40.200> most<17:36:40.436> prevalent<17:36:40.980> that<17:36:41.160> we 17:36:41.330 --> 17:36:41.340 align:start position:0% they're the two most prevalent that we 17:36:41.340 --> 17:36:43.490 align:start position:0% they're the two most prevalent that we see<17:36:41.520> in<17:36:41.700> the<17:36:41.880> field<17:36:42.000> especially<17:36:42.956> from<17:36:43.256> a 17:36:43.490 --> 17:36:43.500 align:start position:0% see in the field especially from a 17:36:43.500 --> 17:36:45.050 align:start position:0% see in the field especially from a consumer's<17:36:44.040> point<17:36:44.160> of<17:36:44.340> view 17:36:45.050 --> 17:36:45.060 align:start position:0% consumer's point of view 17:36:45.060 --> 17:36:47.570 align:start position:0% consumer's point of view so<17:36:45.660> in<17:36:45.900> this<17:36:46.080> module<17:36:46.500> we're<17:36:46.860> going<17:36:47.096> to<17:36:47.340> Define 17:36:47.570 --> 17:36:47.580 align:start position:0% so in this module we're going to Define 17:36:47.580 --> 17:36:50.510 align:start position:0% so in this module we're going to Define what<17:36:48.060> a<17:36:48.240> firewall<17:36:48.596> is<17:36:48.900> and<17:36:49.320> then<17:36:49.436> identify<17:36:50.040> its 17:36:50.510 --> 17:36:50.520 align:start position:0% what a firewall is and then identify its 17:36:50.520 --> 17:36:52.730 align:start position:0% what a firewall is and then identify its importance<17:36:50.756> and<17:36:51.000> how<17:36:51.240> it<17:36:51.360> works<17:36:51.660> we're<17:36:52.436> also 17:36:52.730 --> 17:36:52.740 align:start position:0% importance and how it works we're also 17:36:52.740 --> 17:36:55.370 align:start position:0% importance and how it works we're also going<17:36:52.860> to<17:36:52.980> Define<17:36:53.180> anti-virus<17:36:54.180> software<17:36:54.596> and 17:36:55.370 --> 17:36:55.380 align:start position:0% going to Define anti-virus software and 17:36:55.380 --> 17:36:58.850 align:start position:0% going to Define anti-virus software and identify<17:36:55.916> its<17:36:56.400> importance<17:36:56.700> and<17:36:56.936> how<17:36:57.240> it<17:36:57.480> works 17:36:58.850 --> 17:36:58.860 align:start position:0% identify its importance and how it works 17:36:58.860 --> 17:37:00.946 align:start position:0% identify its importance and how it works so<17:36:59.276> let's<17:36:59.400> start<17:36:59.640> by<17:36:59.880> talking<17:37:00.116> about<17:37:00.416> a 17:37:00.946 --> 17:37:00.956 align:start position:0% so let's start by talking about a 17:37:00.956 --> 17:37:02.390 align:start position:0% so let's start by talking about a firewall<17:37:01.436> this<17:37:01.740> is<17:37:01.916> something<17:37:02.040> you've 17:37:02.390 --> 17:37:02.400 align:start position:0% firewall this is something you've 17:37:02.400 --> 17:37:04.246 align:start position:0% firewall this is something you've probably<17:37:02.520> heard<17:37:02.820> about<17:37:03.000> you<17:37:03.480> might<17:37:03.720> even<17:37:03.900> have 17:37:04.246 --> 17:37:04.256 align:start position:0% probably heard about you might even have 17:37:04.256 --> 17:37:06.170 align:start position:0% probably heard about you might even have on<17:37:04.796> your<17:37:04.980> computer<17:37:05.160> or<17:37:05.456> on<17:37:05.640> your<17:37:05.820> home<17:37:05.936> network 17:37:06.170 --> 17:37:06.180 align:start position:0% on your computer or on your home network 17:37:06.180 --> 17:37:09.230 align:start position:0% on your computer or on your home network a<17:37:07.020> firewall<17:37:07.380> is<17:37:07.616> an<17:37:07.796> essential<17:37:08.220> part<17:37:08.520> of<17:37:08.936> any 17:37:09.230 --> 17:37:09.240 align:start position:0% a firewall is an essential part of any 17:37:09.240 --> 17:37:11.210 align:start position:0% a firewall is an essential part of any secure<17:37:09.720> network<17:37:09.956> especially<17:37:10.560> in<17:37:10.680> today's<17:37:10.860> day 17:37:11.210 --> 17:37:11.220 align:start position:0% secure network especially in today's day 17:37:11.220 --> 17:37:13.370 align:start position:0% secure network especially in today's day and<17:37:11.340> age<17:37:11.520> and<17:37:12.000> a<17:37:12.180> network<17:37:12.240> would<17:37:12.540> just<17:37:12.720> be<17:37:12.840> at 17:37:13.370 --> 17:37:13.380 align:start position:0% and age and a network would just be at 17:37:13.380 --> 17:37:16.310 align:start position:0% and age and a network would just be at risk<17:37:13.740> almost<17:37:14.096> constantly<17:37:14.756> without<17:37:15.060> it<17:37:15.776> it's 17:37:16.310 --> 17:37:16.320 align:start position:0% risk almost constantly without it it's 17:37:16.320 --> 17:37:18.530 align:start position:0% risk almost constantly without it it's basically<17:37:16.680> a<17:37:16.980> security<17:37:17.160> system<17:37:17.700> that<17:37:18.240> serves 17:37:18.530 --> 17:37:18.540 align:start position:0% basically a security system that serves 17:37:18.540 --> 17:37:20.810 align:start position:0% basically a security system that serves as<17:37:18.660> a<17:37:18.900> barrier<17:37:19.320> between<17:37:19.916> the<17:37:20.400> local<17:37:20.520> network 17:37:20.810 --> 17:37:20.820 align:start position:0% as a barrier between the local network 17:37:20.820 --> 17:37:24.946 align:start position:0% as a barrier between the local network and<17:37:21.480> the<17:37:21.660> wide<17:37:21.900> Network<17:37:22.200> or<17:37:22.916> VPN<17:37:23.580> it<17:37:24.360> analyzes 17:37:24.946 --> 17:37:24.956 align:start position:0% and the wide Network or VPN it analyzes 17:37:24.956 --> 17:37:26.810 align:start position:0% and the wide Network or VPN it analyzes the<17:37:25.256> data<17:37:25.560> packets<17:37:25.916> that<17:37:26.160> are<17:37:26.340> trying<17:37:26.520> to 17:37:26.810 --> 17:37:26.820 align:start position:0% the data packets that are trying to 17:37:26.820 --> 17:37:29.150 align:start position:0% the data packets that are trying to enter<17:37:27.000> the<17:37:27.296> local<17:37:27.416> network<17:37:27.776> and<17:37:28.560> exit<17:37:28.980> the 17:37:29.150 --> 17:37:29.160 align:start position:0% enter the local network and exit the 17:37:29.160 --> 17:37:30.890 align:start position:0% enter the local network and exit the local<17:37:29.276> network<17:37:29.580> and<17:37:30.116> determines<17:37:30.596> whether 17:37:30.890 --> 17:37:30.900 align:start position:0% local network and determines whether 17:37:30.900 --> 17:37:33.406 align:start position:0% local network and determines whether it's<17:37:31.080> safe<17:37:31.256> to<17:37:31.500> let<17:37:31.616> them<17:37:31.796> in<17:37:32.040> or<17:37:32.700> out<17:37:32.880> or<17:37:33.240> not 17:37:33.406 --> 17:37:33.416 align:start position:0% it's safe to let them in or out or not 17:37:33.416 --> 17:37:36.710 align:start position:0% it's safe to let them in or out or not in<17:37:34.140> a<17:37:34.256> more<17:37:34.380> General<17:37:34.560> sense<17:37:34.980> a<17:37:35.400> firewall<17:37:35.936> is 17:37:36.710 --> 17:37:36.720 align:start position:0% in a more General sense a firewall is 17:37:36.720 --> 17:37:39.586 align:start position:0% in a more General sense a firewall is set<17:37:36.956> up<17:37:37.080> between<17:37:37.436> local<17:37:38.220> private<17:37:38.936> Network<17:37:39.116> and 17:37:39.586 --> 17:37:39.596 align:start position:0% set up between local private Network and 17:37:39.596 --> 17:37:42.170 align:start position:0% set up between local private Network and a<17:37:39.776> public<17:37:39.956> network<17:37:40.320> like<17:37:40.860> the<17:37:41.160> internet<17:37:41.340> so 17:37:42.170 --> 17:37:42.180 align:start position:0% a public network like the internet so 17:37:42.180 --> 17:37:44.030 align:start position:0% a public network like the internet so internet<17:37:42.360> protection<17:37:42.956> is<17:37:43.436> actually<17:37:43.616> a<17:37:43.916> large 17:37:44.030 --> 17:37:44.040 align:start position:0% internet protection is actually a large 17:37:44.040 --> 17:37:45.946 align:start position:0% internet protection is actually a large part<17:37:44.340> of<17:37:44.640> what<17:37:44.880> the<17:37:45.000> firewall<17:37:45.360> is<17:37:45.596> used<17:37:45.776> for 17:37:45.946 --> 17:37:45.956 align:start position:0% part of what the firewall is used for 17:37:45.956 --> 17:37:48.710 align:start position:0% part of what the firewall is used for now<17:37:46.680> the<17:37:46.980> reason<17:37:47.096> it's<17:37:47.400> called<17:37:47.700> a<17:37:48.060> firewall<17:37:48.540> is 17:37:48.710 --> 17:37:48.720 align:start position:0% now the reason it's called a firewall is 17:37:48.720 --> 17:37:50.870 align:start position:0% now the reason it's called a firewall is because<17:37:49.020> if<17:37:49.436> you<17:37:49.560> think<17:37:49.740> about<17:37:49.860> it<17:37:50.096> the<17:37:50.700> fire 17:37:50.870 --> 17:37:50.880 align:start position:0% because if you think about it the fire 17:37:50.880 --> 17:37:52.850 align:start position:0% because if you think about it the fire is<17:37:51.480> going<17:37:51.660> to<17:37:51.776> burn<17:37:51.900> up<17:37:52.080> all<17:37:52.320> the<17:37:52.436> bad<17:37:52.616> stuff 17:37:52.850 --> 17:37:52.860 align:start position:0% is going to burn up all the bad stuff 17:37:52.860 --> 17:37:54.470 align:start position:0% is going to burn up all the bad stuff but<17:37:53.160> not<17:37:53.276> the<17:37:53.520> good<17:37:53.640> stuff 17:37:54.470 --> 17:37:54.480 align:start position:0% but not the good stuff 17:37:54.480 --> 17:37:57.106 align:start position:0% but not the good stuff as<17:37:54.956> opposed<17:37:55.320> to<17:37:55.380> a<17:37:55.860> brick<17:37:56.160> wall<17:37:56.340> which 17:37:57.106 --> 17:37:57.116 align:start position:0% as opposed to a brick wall which 17:37:57.116 --> 17:37:59.030 align:start position:0% as opposed to a brick wall which wouldn't<17:37:57.360> let<17:37:57.720> anything<17:37:58.080> in<17:37:58.436> so<17:37:58.740> the<17:37:58.860> name 17:37:59.030 --> 17:37:59.040 align:start position:0% wouldn't let anything in so the name 17:37:59.040 --> 17:38:01.310 align:start position:0% wouldn't let anything in so the name sort<17:37:59.340> of<17:37:59.400> describes<17:37:59.820> what<17:38:00.060> it<17:38:00.240> does<17:38:00.416> people 17:38:01.310 --> 17:38:01.320 align:start position:0% sort of describes what it does people 17:38:01.320 --> 17:38:04.010 align:start position:0% sort of describes what it does people often<17:38:01.916> establish<17:38:02.456> firewalls<17:38:03.240> as<17:38:03.596> their<17:38:03.840> main 17:38:04.010 --> 17:38:04.020 align:start position:0% often establish firewalls as their main 17:38:04.020 --> 17:38:05.870 align:start position:0% often establish firewalls as their main line<17:38:04.256> of<17:38:04.436> defense<17:38:04.740> from<17:38:05.040> internet<17:38:05.220> attacks 17:38:05.870 --> 17:38:05.880 align:start position:0% line of defense from internet attacks 17:38:05.880 --> 17:38:08.570 align:start position:0% line of defense from internet attacks and<17:38:06.540> they<17:38:06.720> can<17:38:06.900> be<17:38:07.140> configured<17:38:07.740> to<17:38:08.096> not<17:38:08.276> allow 17:38:08.570 --> 17:38:08.580 align:start position:0% and they can be configured to not allow 17:38:08.580 --> 17:38:10.970 align:start position:0% and they can be configured to not allow access<17:38:08.880> to<17:38:09.240> certain<17:38:09.480> websites<17:38:10.200> as<17:38:10.680> well<17:38:10.916> as 17:38:10.970 --> 17:38:10.980 align:start position:0% access to certain websites as well as 17:38:10.980 --> 17:38:12.470 align:start position:0% access to certain websites as well as not<17:38:11.220> allow<17:38:11.520> downloads<17:38:12.116> from<17:38:12.296> certain 17:38:12.470 --> 17:38:12.480 align:start position:0% not allow downloads from certain 17:38:12.480 --> 17:38:14.746 align:start position:0% not allow downloads from certain websites<17:38:13.140> or<17:38:13.560> certain<17:38:13.860> ports<17:38:14.276> to<17:38:14.400> be<17:38:14.580> open 17:38:14.746 --> 17:38:14.756 align:start position:0% websites or certain ports to be open 17:38:14.756 --> 17:38:17.570 align:start position:0% websites or certain ports to be open we'll<17:38:15.720> use<17:38:16.020> something<17:38:16.320> called<17:38:16.916> a<17:38:17.400> port 17:38:17.570 --> 17:38:17.580 align:start position:0% we'll use something called a port 17:38:17.580 --> 17:38:20.210 align:start position:0% we'll use something called a port scanner<17:38:18.180> to<17:38:18.956> see<17:38:19.140> if<17:38:19.436> there<17:38:19.616> are<17:38:19.796> any<17:38:19.916> open 17:38:20.210 --> 17:38:20.220 align:start position:0% scanner to see if there are any open 17:38:20.220 --> 17:38:22.190 align:start position:0% scanner to see if there are any open ports<17:38:20.880> on<17:38:21.180> our<17:38:21.360> Network<17:38:21.540> that<17:38:21.840> are<17:38:21.956> going<17:38:22.080> to 17:38:22.190 --> 17:38:22.200 align:start position:0% ports on our Network that are going to 17:38:22.200 --> 17:38:25.606 align:start position:0% ports on our Network that are going to let<17:38:22.380> bad<17:38:23.276> stuff<17:38:23.580> in<17:38:24.000> and<17:38:24.596> what<17:38:24.776> we<17:38:24.900> can<17:38:25.080> do<17:38:25.256> is 17:38:25.606 --> 17:38:25.616 align:start position:0% let bad stuff in and what we can do is 17:38:25.616 --> 17:38:28.730 align:start position:0% let bad stuff in and what we can do is actually<17:38:25.980> set<17:38:26.580> the<17:38:26.880> firewall<17:38:27.360> to<17:38:28.256> allow 17:38:28.730 --> 17:38:28.740 align:start position:0% actually set the firewall to allow 17:38:28.740 --> 17:38:30.490 align:start position:0% actually set the firewall to allow inbound 17:38:30.490 --> 17:38:30.500 align:start position:0% inbound 17:38:30.500 --> 17:38:33.350 align:start position:0% inbound and<17:38:31.500> outbound<17:38:32.096> ports 17:38:33.350 --> 17:38:33.360 align:start position:0% and outbound ports 17:38:33.360 --> 17:38:36.766 align:start position:0% and outbound ports now<17:38:34.080> I<17:38:34.980> know<17:38:35.096> inbound<17:38:35.640> probably<17:38:36.060> makes<17:38:36.296> more 17:38:36.766 --> 17:38:36.776 align:start position:0% now I know inbound probably makes more 17:38:36.776 --> 17:38:39.710 align:start position:0% now I know inbound probably makes more sense<17:38:37.080> than<17:38:38.040> outbound<17:38:38.640> but<17:38:39.296> if<17:38:39.480> you<17:38:39.596> think 17:38:39.710 --> 17:38:39.720 align:start position:0% sense than outbound but if you think 17:38:39.720 --> 17:38:41.990 align:start position:0% sense than outbound but if you think about<17:38:39.840> it<17:38:40.080> if<17:38:40.320> somehow<17:38:40.680> I<17:38:40.980> get<17:38:41.096> a<17:38:41.276> virus<17:38:41.640> into 17:38:41.990 --> 17:38:42.000 align:start position:0% about it if somehow I get a virus into 17:38:42.000 --> 17:38:44.266 align:start position:0% about it if somehow I get a virus into my<17:38:42.240> computer<17:38:42.416> and<17:38:43.380> it<17:38:43.616> starts<17:38:43.980> sending 17:38:44.266 --> 17:38:44.276 align:start position:0% my computer and it starts sending 17:38:44.276 --> 17:38:46.246 align:start position:0% my computer and it starts sending information<17:38:44.456> out<17:38:45.240> I<17:38:45.660> want<17:38:45.776> to<17:38:45.900> make<17:38:45.956> sure<17:38:46.140> to 17:38:46.246 --> 17:38:46.256 align:start position:0% information out I want to make sure to 17:38:46.256 --> 17:38:48.766 align:start position:0% information out I want to make sure to keep<17:38:46.436> that<17:38:46.680> information<17:38:46.916> in<17:38:47.580> so<17:38:48.180> that<17:38:48.360> I<17:38:48.660> don't 17:38:48.766 --> 17:38:48.776 align:start position:0% keep that information in so that I don't 17:38:48.776 --> 17:38:50.990 align:start position:0% keep that information in so that I don't release<17:38:49.080> any<17:38:50.040> say<17:38:50.276> private<17:38:50.820> information 17:38:50.990 --> 17:38:51.000 align:start position:0% release any say private information 17:38:51.000 --> 17:38:52.426 align:start position:0% release any say private information about<17:38:51.416> my<17:38:51.720> network 17:38:52.426 --> 17:38:52.436 align:start position:0% about my network 17:38:52.436 --> 17:38:54.406 align:start position:0% about my network now<17:38:52.860> the<17:38:53.096> term<17:38:53.220> firewall<17:38:53.820> as<17:38:54.000> I<17:38:54.116> was<17:38:54.296> just 17:38:54.406 --> 17:38:54.416 align:start position:0% now the term firewall as I was just 17:38:54.416 --> 17:38:56.470 align:start position:0% now the term firewall as I was just talking<17:38:54.596> about<17:38:54.840> comes<17:38:55.380> from<17:38:55.560> the<17:38:56.220> physical 17:38:56.470 --> 17:38:56.480 align:start position:0% talking about comes from the physical 17:38:56.480 --> 17:38:58.550 align:start position:0% talking about comes from the physical firewalls<17:38:57.480> or<17:38:57.660> doors<17:38:57.956> that<17:38:58.140> a<17:38:58.320> lot<17:38:58.436> of 17:38:58.550 --> 17:38:58.560 align:start position:0% firewalls or doors that a lot of 17:38:58.560 --> 17:39:00.890 align:start position:0% firewalls or doors that a lot of buildings<17:38:59.040> contain<17:38:59.456> these<17:39:00.416> doors<17:39:00.720> are 17:39:00.890 --> 17:39:00.900 align:start position:0% buildings contain these doors are 17:39:00.900 --> 17:39:03.650 align:start position:0% buildings contain these doors are fireproof<17:39:01.500> and<17:39:01.616> they<17:39:01.860> contain<17:39:02.276> a<17:39:03.000> fire<17:39:03.180> to<17:39:03.416> one 17:39:03.650 --> 17:39:03.660 align:start position:0% fireproof and they contain a fire to one 17:39:03.660 --> 17:39:05.926 align:start position:0% fireproof and they contain a fire to one area<17:39:03.900> stop<17:39:04.616> it<17:39:04.796> from<17:39:04.916> spreading<17:39:05.400> elsewhere 17:39:05.926 --> 17:39:05.936 align:start position:0% area stop it from spreading elsewhere 17:39:05.936 --> 17:39:07.786 align:start position:0% area stop it from spreading elsewhere which<17:39:06.480> is<17:39:06.540> another<17:39:06.660> way<17:39:06.956> we<17:39:07.200> get<17:39:07.320> that<17:39:07.500> term 17:39:07.786 --> 17:39:07.796 align:start position:0% which is another way we get that term 17:39:07.796 --> 17:39:11.030 align:start position:0% which is another way we get that term they're<17:39:08.580> also<17:39:08.880> meant<17:39:09.060> to<17:39:09.240> block<17:39:09.416> out<17:39:09.840> fires<17:39:10.320> so 17:39:11.030 --> 17:39:11.040 align:start position:0% they're also meant to block out fires so 17:39:11.040 --> 17:39:13.426 align:start position:0% they're also meant to block out fires so this<17:39:11.220> is<17:39:11.340> what<17:39:11.520> a<17:39:11.700> network<17:39:11.880> firewall<17:39:12.480> does<17:39:12.900> but 17:39:13.426 --> 17:39:13.436 align:start position:0% this is what a network firewall does but 17:39:13.436 --> 17:39:15.530 align:start position:0% this is what a network firewall does but with<17:39:13.916> threats<17:39:14.276> from<17:39:14.456> outside<17:39:14.700> and<17:39:15.000> inside<17:39:15.240> of 17:39:15.530 --> 17:39:15.540 align:start position:0% with threats from outside and inside of 17:39:15.540 --> 17:39:16.310 align:start position:0% with threats from outside and inside of the<17:39:15.596> network 17:39:16.310 --> 17:39:16.320 align:start position:0% the network 17:39:16.320 --> 17:39:18.406 align:start position:0% the network so<17:39:16.796> think<17:39:16.980> about<17:39:17.096> a<17:39:17.340> firewall<17:39:17.700> if<17:39:18.000> we<17:39:18.116> can<17:39:18.240> use 17:39:18.406 --> 17:39:18.416 align:start position:0% so think about a firewall if we can use 17:39:18.416 --> 17:39:21.230 align:start position:0% so think about a firewall if we can use a<17:39:18.596> metaphor<17:39:18.956> as<17:39:19.740> the<17:39:20.040> moat<17:39:20.400> and<17:39:20.936> the<17:39:21.060> stone 17:39:21.230 --> 17:39:21.240 align:start position:0% a metaphor as the moat and the stone 17:39:21.240 --> 17:39:23.390 align:start position:0% a metaphor as the moat and the stone walls<17:39:21.660> around<17:39:21.776> a<17:39:22.080> castle<17:39:22.200> everything<17:39:22.980> within 17:39:23.390 --> 17:39:23.400 align:start position:0% walls around a castle everything within 17:39:23.400 --> 17:39:25.010 align:start position:0% walls around a castle everything within the<17:39:23.520> castle<17:39:23.640> walls<17:39:24.116> is<17:39:24.240> really<17:39:24.416> contained<17:39:24.900> and 17:39:25.010 --> 17:39:25.020 align:start position:0% the castle walls is really contained and 17:39:25.020 --> 17:39:27.106 align:start position:0% the castle walls is really contained and localized<17:39:25.680> outside<17:39:26.340> the<17:39:26.580> walls<17:39:26.880> however 17:39:27.106 --> 17:39:27.116 align:start position:0% localized outside the walls however 17:39:27.116 --> 17:39:29.330 align:start position:0% localized outside the walls however there's<17:39:27.360> a<17:39:27.596> public<17:39:27.720> domain<17:39:28.256> the<17:39:28.500> internet 17:39:29.330 --> 17:39:29.340 align:start position:0% there's a public domain the internet 17:39:29.340 --> 17:39:31.906 align:start position:0% there's a public domain the internet walls<17:39:30.060> in<17:39:30.180> the<17:39:30.296> mode<17:39:30.416> of<17:39:30.596> the<17:39:30.720> castle<17:39:30.900> are<17:39:31.616> the 17:39:31.906 --> 17:39:31.916 align:start position:0% walls in the mode of the castle are the 17:39:31.916 --> 17:39:33.766 align:start position:0% walls in the mode of the castle are the last<17:39:32.096> line<17:39:32.400> of<17:39:32.700> a<17:39:32.880> large-scale<17:39:33.360> defense 17:39:33.766 --> 17:39:33.776 align:start position:0% last line of a large-scale defense 17:39:33.776 --> 17:39:36.170 align:start position:0% last line of a large-scale defense before<17:39:34.200> an<17:39:34.560> attack<17:39:34.680> can<17:39:35.040> infiltrate<17:39:35.580> so<17:39:36.116> this 17:39:36.170 --> 17:39:36.180 align:start position:0% before an attack can infiltrate so this 17:39:36.180 --> 17:39:37.970 align:start position:0% before an attack can infiltrate so this is<17:39:36.360> exactly<17:39:36.660> what<17:39:36.776> a<17:39:36.956> firewall<17:39:37.256> does<17:39:37.436> it<17:39:37.680> keeps 17:39:37.970 --> 17:39:37.980 align:start position:0% is exactly what a firewall does it keeps 17:39:37.980 --> 17:39:39.530 align:start position:0% is exactly what a firewall does it keeps the<17:39:38.096> public<17:39:38.276> network<17:39:38.640> and<17:39:39.060> the<17:39:39.240> private 17:39:39.530 --> 17:39:39.540 align:start position:0% the public network and the private 17:39:39.540 --> 17:39:41.390 align:start position:0% the public network and the private Network<17:39:39.660> separate<17:39:40.200> from<17:39:40.320> each<17:39:40.500> other<17:39:40.616> now<17:39:41.276> the 17:39:41.390 --> 17:39:41.400 align:start position:0% Network separate from each other now the 17:39:41.400 --> 17:39:43.010 align:start position:0% Network separate from each other now the castle<17:39:41.580> much<17:39:41.936> like<17:39:42.116> a<17:39:42.240> firewall<17:39:42.596> does<17:39:42.776> allow 17:39:43.010 --> 17:39:43.020 align:start position:0% castle much like a firewall does allow 17:39:43.020 --> 17:39:45.050 align:start position:0% castle much like a firewall does allow certain<17:39:43.200> things<17:39:43.500> inside<17:39:43.916> this<17:39:44.400> is<17:39:44.520> like<17:39:44.756> the 17:39:45.050 --> 17:39:45.060 align:start position:0% certain things inside this is like the 17:39:45.060 --> 17:39:47.390 align:start position:0% certain things inside this is like the drawbridge<17:39:45.596> of<17:39:45.900> the<17:39:46.080> castle<17:39:46.256> so<17:39:47.040> when<17:39:47.220> the 17:39:47.390 --> 17:39:47.400 align:start position:0% drawbridge of the castle so when the 17:39:47.400 --> 17:39:49.310 align:start position:0% drawbridge of the castle so when the walls<17:39:47.700> and<17:39:47.880> the<17:39:48.000> moat<17:39:48.240> keep<17:39:48.540> unwanted<17:39:49.140> things 17:39:49.310 --> 17:39:49.320 align:start position:0% walls and the moat keep unwanted things 17:39:49.320 --> 17:39:51.830 align:start position:0% walls and the moat keep unwanted things out<17:39:49.560> but<17:39:50.276> then<17:39:50.456> things<17:39:50.700> are<17:39:50.936> trusted<17:39:51.416> so<17:39:51.660> they 17:39:51.830 --> 17:39:51.840 align:start position:0% out but then things are trusted so they 17:39:51.840 --> 17:39:54.946 align:start position:0% out but then things are trusted so they are<17:39:52.020> allowed<17:39:52.320> in<17:39:52.560> through<17:39:53.160> the<17:39:53.756> drawbridge<17:39:54.180> so 17:39:54.946 --> 17:39:54.956 align:start position:0% are allowed in through the drawbridge so 17:39:54.956 --> 17:39:56.510 align:start position:0% are allowed in through the drawbridge so firewalls<17:39:55.436> do<17:39:55.560> the<17:39:55.616> same<17:39:55.796> thing<17:39:55.860> with<17:39:56.096> packets 17:39:56.510 --> 17:39:56.520 align:start position:0% firewalls do the same thing with packets 17:39:56.520 --> 17:39:58.426 align:start position:0% firewalls do the same thing with packets of<17:39:56.700> data<17:39:57.000> they<17:39:57.480> only<17:39:57.596> allow<17:39:57.900> the<17:39:58.020> ones<17:39:58.256> that 17:39:58.426 --> 17:39:58.436 align:start position:0% of data they only allow the ones that 17:39:58.436 --> 17:40:00.650 align:start position:0% of data they only allow the ones that they<17:39:58.616> trust<17:39:58.916> to<17:39:59.220> enter<17:39:59.400> the<17:39:59.640> network<17:39:59.820> and<17:40:00.540> we 17:40:00.650 --> 17:40:00.660 align:start position:0% they trust to enter the network and we 17:40:00.660 --> 17:40:03.050 align:start position:0% they trust to enter the network and we do<17:40:00.900> this<17:40:01.080> again<17:40:01.436> by<17:40:02.220> allowing<17:40:02.640> or<17:40:02.820> not 17:40:03.050 --> 17:40:03.060 align:start position:0% do this again by allowing or not 17:40:03.060 --> 17:40:05.210 align:start position:0% do this again by allowing or not allowing<17:40:03.416> certain<17:40:03.720> ports<17:40:04.140> now<17:40:04.616> of<17:40:04.860> course<17:40:04.980> one 17:40:05.210 --> 17:40:05.220 align:start position:0% allowing certain ports now of course one 17:40:05.220 --> 17:40:08.030 align:start position:0% allowing certain ports now of course one of<17:40:05.400> the<17:40:05.456> downsides<17:40:05.936> of<17:40:06.116> a<17:40:06.240> firewall<17:40:06.660> is<17:40:07.436> it<17:40:07.860> can 17:40:08.030 --> 17:40:08.040 align:start position:0% of the downsides of a firewall is it can 17:40:08.040 --> 17:40:11.510 align:start position:0% of the downsides of a firewall is it can block<17:40:08.400> good<17:40:09.296> stuff 17:40:11.510 --> 17:40:11.520 align:start position:0% block good stuff 17:40:11.520 --> 17:40:15.050 align:start position:0% block good stuff so<17:40:12.360> for<17:40:12.540> instance<17:40:12.776> if<17:40:13.080> I<17:40:13.256> have<17:40:13.436> Quickbooks<17:40:14.160> on 17:40:15.050 --> 17:40:15.060 align:start position:0% so for instance if I have Quickbooks on 17:40:15.060 --> 17:40:16.730 align:start position:0% so for instance if I have Quickbooks on my<17:40:15.360> computer<17:40:15.660> and<17:40:16.020> it's<17:40:16.200> trying<17:40:16.380> to<17:40:16.560> access 17:40:16.730 --> 17:40:16.740 align:start position:0% my computer and it's trying to access 17:40:16.740 --> 17:40:19.010 align:start position:0% my computer and it's trying to access its<17:40:17.580> download<17:40:17.700> server<17:40:18.240> to<17:40:18.416> update<17:40:18.776> the 17:40:19.010 --> 17:40:19.020 align:start position:0% its download server to update the 17:40:19.020 --> 17:40:22.670 align:start position:0% its download server to update the program<17:40:19.500> I<17:40:20.456> could<17:40:20.700> block<17:40:21.416> the<17:40:22.020> inbound<17:40:22.380> Port 17:40:22.670 --> 17:40:22.680 align:start position:0% program I could block the inbound Port 17:40:22.680 --> 17:40:25.850 align:start position:0% program I could block the inbound Port by<17:40:23.040> accident<17:40:23.220> through<17:40:23.700> my<17:40:23.880> firewall<17:40:24.296> and 17:40:25.850 --> 17:40:25.860 align:start position:0% by accident through my firewall and 17:40:25.860 --> 17:40:27.946 align:start position:0% by accident through my firewall and um<17:40:26.400> then<17:40:27.000> it<17:40:27.240> wouldn't<17:40:27.360> be<17:40:27.596> able<17:40:27.720> to<17:40:27.840> get 17:40:27.946 --> 17:40:27.956 align:start position:0% um then it wouldn't be able to get 17:40:27.956 --> 17:40:30.946 align:start position:0% um then it wouldn't be able to get updates<17:40:28.436> so<17:40:29.096> this<17:40:29.276> is<17:40:29.456> one<17:40:29.820> of<17:40:29.936> the<17:40:30.060> issues<17:40:30.480> now 17:40:30.946 --> 17:40:30.956 align:start position:0% updates so this is one of the issues now 17:40:30.956 --> 17:40:34.370 align:start position:0% updates so this is one of the issues now firewalls<17:40:31.680> can<17:40:31.980> be<17:40:32.220> either<17:40:32.820> software 17:40:34.370 --> 17:40:34.380 align:start position:0% firewalls can be either software 17:40:34.380 --> 17:40:37.130 align:start position:0% firewalls can be either software or<17:40:35.040> Hardware 17:40:37.130 --> 17:40:37.140 align:start position:0% or Hardware 17:40:37.140 --> 17:40:39.050 align:start position:0% or Hardware you<17:40:37.796> probably<17:40:37.980> without<17:40:38.220> even<17:40:38.520> realizing<17:40:38.936> it 17:40:39.050 --> 17:40:39.060 align:start position:0% you probably without even realizing it 17:40:39.060 --> 17:40:41.390 align:start position:0% you probably without even realizing it or<17:40:39.240> maybe<17:40:39.360> you<17:40:39.540> do<17:40:39.720> have<17:40:40.140> a<17:40:40.500> software<17:40:40.796> firewall 17:40:41.390 --> 17:40:41.400 align:start position:0% or maybe you do have a software firewall 17:40:41.400 --> 17:40:45.106 align:start position:0% or maybe you do have a software firewall built<17:40:42.360> into<17:40:42.480> your<17:40:42.776> I<17:40:43.020> OS 17:40:45.106 --> 17:40:45.116 align:start position:0% built into your I OS 17:40:45.116 --> 17:40:47.446 align:start position:0% built into your I OS so<17:40:45.776> if<17:40:45.956> you<17:40:46.140> have<17:40:46.320> Windows<17:40:46.796> 7<17:40:46.916> Windows<17:40:47.340> 8 17:40:47.446 --> 17:40:47.456 align:start position:0% so if you have Windows 7 Windows 8 17:40:47.456 --> 17:40:49.850 align:start position:0% so if you have Windows 7 Windows 8 Windows<17:40:47.880> Vista<17:40:48.240> then<17:40:48.956> you<17:40:49.320> actually<17:40:49.436> have<17:40:49.680> a 17:40:49.850 --> 17:40:49.860 align:start position:0% Windows Vista then you actually have a 17:40:49.860 --> 17:40:52.310 align:start position:0% Windows Vista then you actually have a firewall<17:40:50.220> built<17:40:50.640> in<17:40:50.700> now<17:40:51.660> you<17:40:51.900> could<17:40:52.020> also 17:40:52.310 --> 17:40:52.320 align:start position:0% firewall built in now you could also 17:40:52.320 --> 17:40:55.130 align:start position:0% firewall built in now you could also have<17:40:52.560> a<17:40:52.980> hardware<17:40:53.160> firewall<17:40:53.880> which<17:40:54.660> if<17:40:54.956> we're 17:40:55.130 --> 17:40:55.140 align:start position:0% have a hardware firewall which if we're 17:40:55.140 --> 17:40:57.170 align:start position:0% have a hardware firewall which if we're talking<17:40:55.320> about<17:40:55.616> your<17:40:56.096> home<17:40:56.220> network<17:40:56.520> is 17:40:57.170 --> 17:40:57.180 align:start position:0% talking about your home network is 17:40:57.180 --> 17:40:59.266 align:start position:0% talking about your home network is generally<17:40:57.480> built<17:40:57.900> into<17:40:58.020> your<17:40:58.380> Soho<17:40:58.796> router 17:40:59.266 --> 17:40:59.276 align:start position:0% generally built into your Soho router 17:40:59.276 --> 17:41:02.746 align:start position:0% generally built into your Soho router that's<17:40:59.936> right<17:41:00.116> your<17:41:00.480> Soho<17:41:00.840> router<17:41:01.320> contains<17:41:01.980> a 17:41:02.746 --> 17:41:02.756 align:start position:0% that's right your Soho router contains a 17:41:02.756 --> 17:41:04.850 align:start position:0% that's right your Soho router contains a firewall<17:41:03.240> built<17:41:03.596> in<17:41:03.660> and<17:41:04.020> will<17:41:04.200> allow<17:41:04.500> or<17:41:04.680> not 17:41:04.850 --> 17:41:04.860 align:start position:0% firewall built in and will allow or not 17:41:04.860 --> 17:41:07.190 align:start position:0% firewall built in and will allow or not allow<17:41:05.096> certain<17:41:05.340> ports<17:41:05.820> to<17:41:06.000> come<17:41:06.180> in<17:41:06.360> this 17:41:07.190 --> 17:41:07.200 align:start position:0% allow certain ports to come in this 17:41:07.200 --> 17:41:08.510 align:start position:0% allow certain ports to come in this awfuls<17:41:07.740> us 17:41:08.510 --> 17:41:08.520 align:start position:0% awfuls us 17:41:08.520 --> 17:41:10.786 align:start position:0% awfuls us two<17:41:08.936> levels 17:41:10.786 --> 17:41:10.796 align:start position:0% two levels 17:41:10.796 --> 17:41:13.606 align:start position:0% two levels of<17:41:11.456> security 17:41:13.606 --> 17:41:13.616 align:start position:0% of security 17:41:13.616 --> 17:41:15.710 align:start position:0% of security one<17:41:14.160> through<17:41:14.456> the<17:41:14.640> hardware<17:41:14.820> and<17:41:15.416> once<17:41:15.660> it 17:41:15.710 --> 17:41:15.720 align:start position:0% one through the hardware and once it 17:41:15.720 --> 17:41:17.446 align:start position:0% one through the hardware and once it gets<17:41:15.956> through<17:41:16.080> indoor<17:41:16.560> Network<17:41:16.740> then<17:41:17.096> we<17:41:17.340> have 17:41:17.446 --> 17:41:17.456 align:start position:0% gets through indoor Network then we have 17:41:17.456 --> 17:41:19.550 align:start position:0% gets through indoor Network then we have one<17:41:17.756> on<17:41:18.060> our<17:41:18.240> computer 17:41:19.550 --> 17:41:19.560 align:start position:0% one on our computer 17:41:19.560 --> 17:41:22.550 align:start position:0% one on our computer now<17:41:20.456> like<17:41:20.700> we<17:41:20.820> said<17:41:20.936> before<17:41:21.200> firewalls<17:41:22.200> are 17:41:22.550 --> 17:41:22.560 align:start position:0% now like we said before firewalls are 17:41:22.560 --> 17:41:26.030 align:start position:0% now like we said before firewalls are mostly<17:41:23.160> used<17:41:23.456> to<17:41:23.880> block<17:41:24.180> uh<17:41:25.140> attacks<17:41:25.680> from<17:41:25.860> the 17:41:26.030 --> 17:41:26.040 align:start position:0% mostly used to block uh attacks from the 17:41:26.040 --> 17:41:28.850 align:start position:0% mostly used to block uh attacks from the outside<17:41:26.296> but<17:41:27.296> it's<17:41:27.480> not<17:41:27.660> the<17:41:27.900> only<17:41:28.080> use<17:41:28.380> see 17:41:28.850 --> 17:41:28.860 align:start position:0% outside but it's not the only use see 17:41:28.860 --> 17:41:30.586 align:start position:0% outside but it's not the only use see there<17:41:29.040> are<17:41:29.160> quite<17:41:29.276> a<17:41:29.456> few<17:41:29.580> actually<17:41:29.820> as<17:41:30.416> we 17:41:30.586 --> 17:41:30.596 align:start position:0% there are quite a few actually as we 17:41:30.596 --> 17:41:32.630 align:start position:0% there are quite a few actually as we already<17:41:30.720> talked<17:41:31.140> about<17:41:31.200> they<17:41:31.916> keep<17:41:32.160> attacks 17:41:32.630 --> 17:41:32.640 align:start position:0% already talked about they keep attacks 17:41:32.640 --> 17:41:34.606 align:start position:0% already talked about they keep attacks out<17:41:32.820> by<17:41:33.180> monitoring<17:41:33.660> everything<17:41:34.020> that<17:41:34.320> tries 17:41:34.606 --> 17:41:34.616 align:start position:0% out by monitoring everything that tries 17:41:34.616 --> 17:41:36.946 align:start position:0% out by monitoring everything that tries to<17:41:34.860> enter<17:41:35.040> if<17:41:35.700> something<17:41:35.936> isn't<17:41:36.296> trustworthy 17:41:36.946 --> 17:41:36.956 align:start position:0% to enter if something isn't trustworthy 17:41:36.956 --> 17:41:38.746 align:start position:0% to enter if something isn't trustworthy it's<17:41:37.140> not<17:41:37.320> going<17:41:37.436> to<17:41:37.500> let<17:41:37.616> it<17:41:37.796> through<17:41:37.980> now 17:41:38.746 --> 17:41:38.756 align:start position:0% it's not going to let it through now 17:41:38.756 --> 17:41:40.550 align:start position:0% it's not going to let it through now though<17:41:38.936> this<17:41:39.180> might<17:41:39.296> be<17:41:39.540> the<17:41:39.840> most<17:41:39.956> recognized 17:41:40.550 --> 17:41:40.560 align:start position:0% though this might be the most recognized 17:41:40.560 --> 17:41:41.990 align:start position:0% though this might be the most recognized use<17:41:40.740> there<17:41:41.040> are<17:41:41.160> some<17:41:41.400> other<17:41:41.520> important 17:41:41.990 --> 17:41:42.000 align:start position:0% use there are some other important 17:41:42.000 --> 17:41:44.690 align:start position:0% use there are some other important aspects<17:41:42.480> that<17:41:42.660> we<17:41:42.776> want<17:41:42.900> to<17:41:43.020> talk<17:41:43.140> about<17:41:43.700> for 17:41:44.690 --> 17:41:44.700 align:start position:0% aspects that we want to talk about for 17:41:44.700 --> 17:41:46.606 align:start position:0% aspects that we want to talk about for instance<17:41:44.936> the<17:41:45.296> firewall<17:41:45.660> acts<17:41:45.956> as<17:41:46.080> a<17:41:46.256> barrier 17:41:46.606 --> 17:41:46.616 align:start position:0% instance the firewall acts as a barrier 17:41:46.616 --> 17:41:48.350 align:start position:0% instance the firewall acts as a barrier which<17:41:46.796> not<17:41:46.980> only<17:41:47.096> keeps<17:41:47.456> things<17:41:47.640> out<17:41:47.880> but<17:41:48.240> it 17:41:48.350 --> 17:41:48.360 align:start position:0% which not only keeps things out but it 17:41:48.360 --> 17:41:50.266 align:start position:0% which not only keeps things out but it makes<17:41:48.540> sure<17:41:48.720> that<17:41:49.020> important<17:41:49.740> things<17:41:49.916> inside 17:41:50.266 --> 17:41:50.276 align:start position:0% makes sure that important things inside 17:41:50.276 --> 17:41:52.670 align:start position:0% makes sure that important things inside the<17:41:50.640> network<17:41:50.820> don't<17:41:51.240> get<17:41:51.416> out<17:41:51.596> which<17:41:52.436> in 17:41:52.670 --> 17:41:52.680 align:start position:0% the network don't get out which in 17:41:52.680 --> 17:41:54.710 align:start position:0% the network don't get out which in effect<17:41:52.860> keeps<17:41:53.340> the<17:41:53.400> data<17:41:53.756> secure<17:41:54.116> this<17:41:54.660> is 17:41:54.710 --> 17:41:54.720 align:start position:0% effect keeps the data secure this is 17:41:54.720 --> 17:41:58.130 align:start position:0% effect keeps the data secure this is what<17:41:54.900> I<17:41:55.080> was<17:41:55.140> talking<17:41:55.380> about<17:41:55.616> without<17:41:56.580> bound 17:41:58.130 --> 17:41:58.140 align:start position:0% what I was talking about without bound 17:41:58.140 --> 17:42:00.230 align:start position:0% what I was talking about without bound ports 17:42:00.230 --> 17:42:00.240 align:start position:0% ports 17:42:00.240 --> 17:42:03.470 align:start position:0% ports for<17:42:00.840> example<17:42:01.160> if<17:42:02.160> secure<17:42:02.520> data<17:42:03.000> is<17:42:03.296> being 17:42:03.470 --> 17:42:03.480 align:start position:0% for example if secure data is being 17:42:03.480 --> 17:42:05.086 align:start position:0% for example if secure data is being accessed<17:42:04.020> and<17:42:04.140> taken<17:42:04.436> from<17:42:04.500> someone<17:42:04.680> on<17:42:04.916> the 17:42:05.086 --> 17:42:05.096 align:start position:0% accessed and taken from someone on the 17:42:05.096 --> 17:42:08.086 align:start position:0% accessed and taken from someone on the outside<17:42:05.276> then<17:42:06.000> we<17:42:06.296> can<17:42:06.416> make<17:42:06.720> sure<17:42:06.956> that<17:42:07.796> the 17:42:08.086 --> 17:42:08.096 align:start position:0% outside then we can make sure that the 17:42:08.096 --> 17:42:10.010 align:start position:0% outside then we can make sure that the data<17:42:08.400> can't<17:42:08.580> get<17:42:08.880> out<17:42:09.296> through<17:42:09.660> our<17:42:09.840> Network 17:42:10.010 --> 17:42:10.020 align:start position:0% data can't get out through our Network 17:42:10.020 --> 17:42:11.446 align:start position:0% data can't get out through our Network it's<17:42:10.320> going<17:42:10.500> to<17:42:10.616> be<17:42:10.680> stopped<17:42:11.096> just<17:42:11.340> like 17:42:11.446 --> 17:42:11.456 align:start position:0% it's going to be stopped just like 17:42:11.456 --> 17:42:13.850 align:start position:0% it's going to be stopped just like containing<17:42:11.936> the<17:42:12.116> fire<17:42:12.296> within<17:42:13.256> the<17:42:13.680> building 17:42:13.850 --> 17:42:13.860 align:start position:0% containing the fire within the building 17:42:13.860 --> 17:42:15.830 align:start position:0% containing the fire within the building this<17:42:14.580> is<17:42:14.700> really<17:42:14.880> important<17:42:15.240> to<17:42:15.416> businesses 17:42:15.830 --> 17:42:15.840 align:start position:0% this is really important to businesses 17:42:15.840 --> 17:42:17.870 align:start position:0% this is really important to businesses and<17:42:15.956> organizations<17:42:16.500> where<17:42:17.276> data<17:42:17.700> really 17:42:17.870 --> 17:42:17.880 align:start position:0% and organizations where data really 17:42:17.880 --> 17:42:20.266 align:start position:0% and organizations where data really equals<17:42:18.360> money<17:42:18.540> or<17:42:18.776> more<17:42:18.956> than<17:42:19.080> money<17:42:19.740> now<17:42:20.040> for 17:42:20.266 --> 17:42:20.276 align:start position:0% equals money or more than money now for 17:42:20.276 --> 17:42:22.906 align:start position:0% equals money or more than money now for individuals<17:42:20.880> it<17:42:21.060> can<17:42:21.240> help<17:42:21.416> secure<17:42:21.916> important 17:42:22.906 --> 17:42:22.916 align:start position:0% individuals it can help secure important 17:42:22.916 --> 17:42:24.286 align:start position:0% individuals it can help secure important information<17:42:23.160> like<17:42:23.700> your<17:42:23.880> social<17:42:24.060> security 17:42:24.286 --> 17:42:24.296 align:start position:0% information like your social security 17:42:24.296 --> 17:42:26.086 align:start position:0% information like your social security number<17:42:24.720> credit<17:42:25.080> card<17:42:25.320> information 17:42:26.086 --> 17:42:26.096 align:start position:0% number credit card information 17:42:26.096 --> 17:42:28.426 align:start position:0% number credit card information Etc<17:42:26.296> these<17:42:27.296> aren't<17:42:27.416> things<17:42:27.776> that<17:42:28.020> you<17:42:28.200> want<17:42:28.320> in 17:42:28.426 --> 17:42:28.436 align:start position:0% Etc these aren't things that you want in 17:42:28.436 --> 17:42:30.710 align:start position:0% Etc these aren't things that you want in the<17:42:28.616> hands<17:42:28.796> of<17:42:28.860> attackers<17:42:29.340> so<17:42:29.936> a<17:42:30.116> firewall<17:42:30.480> can 17:42:30.710 --> 17:42:30.720 align:start position:0% the hands of attackers so a firewall can 17:42:30.720 --> 17:42:32.390 align:start position:0% the hands of attackers so a firewall can actually<17:42:30.900> prevent<17:42:31.256> these<17:42:31.560> problems<17:42:31.916> that<17:42:32.220> an 17:42:32.390 --> 17:42:32.400 align:start position:0% actually prevent these problems that an 17:42:32.400 --> 17:42:34.426 align:start position:0% actually prevent these problems that an attack<17:42:32.520> might<17:42:32.936> cause 17:42:34.426 --> 17:42:34.436 align:start position:0% attack might cause 17:42:34.436 --> 17:42:36.830 align:start position:0% attack might cause just<17:42:34.916> as<17:42:35.096> a<17:42:35.276> matter<17:42:35.340> of<17:42:35.520> example<17:42:35.936> I'm<17:42:36.480> here<17:42:36.720> in 17:42:36.830 --> 17:42:36.840 align:start position:0% just as a matter of example I'm here in 17:42:36.840 --> 17:42:39.170 align:start position:0% just as a matter of example I'm here in Windows<17:42:37.200> 7<17:42:37.320> and<17:42:38.096> let's<17:42:38.340> go<17:42:38.580> ahead<17:42:38.756> and<17:42:38.880> check 17:42:39.170 --> 17:42:39.180 align:start position:0% Windows 7 and let's go ahead and check 17:42:39.180 --> 17:42:41.266 align:start position:0% Windows 7 and let's go ahead and check out<17:42:39.416> the<17:42:39.660> Windows<17:42:40.020> firewall 17:42:41.266 --> 17:42:41.276 align:start position:0% out the Windows firewall 17:42:41.276 --> 17:42:43.070 align:start position:0% out the Windows firewall now<17:42:41.756> I<17:42:42.000> actually<17:42:42.116> have<17:42:42.296> two<17:42:42.416> options<17:42:42.720> here<17:42:42.900> one 17:42:43.070 --> 17:42:43.080 align:start position:0% now I actually have two options here one 17:42:43.080 --> 17:42:44.870 align:start position:0% now I actually have two options here one is<17:42:43.256> far<17:42:43.436> with<17:42:43.680> Advanced<17:42:44.160> security<17:42:44.340> and<17:42:44.756> the 17:42:44.870 --> 17:42:44.880 align:start position:0% is far with Advanced security and the 17:42:44.880 --> 17:42:46.670 align:start position:0% is far with Advanced security and the plain<17:42:45.060> old<17:42:45.180> Windows<17:42:45.596> firewall 17:42:46.670 --> 17:42:46.680 align:start position:0% plain old Windows firewall 17:42:46.680 --> 17:42:48.286 align:start position:0% plain old Windows firewall if<17:42:47.040> we<17:42:47.096> go<17:42:47.220> into<17:42:47.340> plan<17:42:47.580> we'll<17:42:47.820> win<17:42:47.936> this<17:42:48.116> far 17:42:48.286 --> 17:42:48.296 align:start position:0% if we go into plan we'll win this far 17:42:48.296 --> 17:42:50.990 align:start position:0% if we go into plan we'll win this far well<17:42:48.480> you<17:42:48.720> can<17:42:48.840> see<17:42:48.956> the<17:42:49.256> firewall<17:42:49.680> is<17:42:49.796> on<17:42:50.160> and 17:42:50.990 --> 17:42:51.000 align:start position:0% well you can see the firewall is on and 17:42:51.000 --> 17:42:53.626 align:start position:0% well you can see the firewall is on and it's<17:42:51.240> working<17:42:51.480> on<17:42:51.840> this<17:42:52.080> network<17:42:52.320> and<17:42:53.160> if<17:42:53.340> I<17:42:53.520> go 17:42:53.626 --> 17:42:53.636 align:start position:0% it's working on this network and if I go 17:42:53.636 --> 17:42:55.970 align:start position:0% it's working on this network and if I go over<17:42:53.820> here<17:42:54.180> I<17:42:54.900> can<17:42:55.020> choose<17:42:55.256> whether<17:42:55.560> or<17:42:55.740> not<17:42:55.740> to 17:42:55.970 --> 17:42:55.980 align:start position:0% over here I can choose whether or not to 17:42:55.980 --> 17:42:58.606 align:start position:0% over here I can choose whether or not to turn<17:42:56.160> the<17:42:56.340> firewall<17:42:56.756> off<17:42:57.180> or<17:42:57.776> on 17:42:58.606 --> 17:42:58.616 align:start position:0% turn the firewall off or on 17:42:58.616 --> 17:43:00.170 align:start position:0% turn the firewall off or on now<17:42:58.916> if<17:42:58.980> we<17:42:59.096> go<17:42:59.220> to<17:42:59.340> those<17:42:59.456> advanced<17:42:59.936> settings 17:43:00.170 --> 17:43:00.180 align:start position:0% now if we go to those advanced settings 17:43:00.180 --> 17:43:02.570 align:start position:0% now if we go to those advanced settings I<17:43:00.596> referred<17:43:01.020> to<17:43:01.136> earlier 17:43:02.570 --> 17:43:02.580 align:start position:0% I referred to earlier 17:43:02.580 --> 17:43:04.310 align:start position:0% I referred to earlier you<17:43:02.700> can<17:43:02.820> see<17:43:03.000> that<17:43:03.116> I<17:43:03.296> have<17:43:03.416> inbound<17:43:03.900> rules 17:43:04.310 --> 17:43:04.320 align:start position:0% you can see that I have inbound rules 17:43:04.320 --> 17:43:06.470 align:start position:0% you can see that I have inbound rules and<17:43:05.160> outbound<17:43:05.520> rules 17:43:06.470 --> 17:43:06.480 align:start position:0% and outbound rules 17:43:06.480 --> 17:43:09.106 align:start position:0% and outbound rules there<17:43:06.956> are<17:43:07.136> inbound<17:43:07.380> rules<17:43:07.796> that<17:43:08.276> allow<17:43:08.756> and 17:43:09.106 --> 17:43:09.116 align:start position:0% there are inbound rules that allow and 17:43:09.116 --> 17:43:11.266 align:start position:0% there are inbound rules that allow and disallow<17:43:09.596> certain<17:43:09.840> information 17:43:11.266 --> 17:43:11.276 align:start position:0% disallow certain information 17:43:11.276 --> 17:43:13.370 align:start position:0% disallow certain information for<17:43:11.756> instance<17:43:12.000> this<17:43:12.540> rule<17:43:12.840> which<17:43:12.956> says<17:43:13.200> file 17:43:13.370 --> 17:43:13.380 align:start position:0% for instance this rule which says file 17:43:13.380 --> 17:43:15.946 align:start position:0% for instance this rule which says file and<17:43:13.560> print<17:43:13.740> sharing<17:43:14.220> Echo<17:43:14.756> request<17:43:15.116> allows 17:43:15.946 --> 17:43:15.956 align:start position:0% and print sharing Echo request allows 17:43:15.956 --> 17:43:18.586 align:start position:0% and print sharing Echo request allows the<17:43:16.080> connection<17:43:16.256> to<17:43:16.680> be<17:43:16.796> made<17:43:17.040> for<17:43:17.756> icmp 17:43:18.586 --> 17:43:18.596 align:start position:0% the connection to be made for icmp 17:43:18.596 --> 17:43:21.286 align:start position:0% the connection to be made for icmp packets<17:43:19.080> which<17:43:19.500> is<17:43:19.680> basically<17:43:20.040> for<17:43:20.276> Ping<17:43:20.636> now 17:43:21.286 --> 17:43:21.296 align:start position:0% packets which is basically for Ping now 17:43:21.296 --> 17:43:24.470 align:start position:0% packets which is basically for Ping now I<17:43:21.480> can<17:43:21.596> choose<17:43:21.840> to<17:43:22.136> disable<17:43:22.500> a<17:43:22.860> rule<17:43:23.096> or<17:43:24.000> create 17:43:24.470 --> 17:43:24.480 align:start position:0% I can choose to disable a rule or create 17:43:24.480 --> 17:43:26.870 align:start position:0% I can choose to disable a rule or create a<17:43:24.720> new<17:43:24.840> rule<17:43:25.256> for<17:43:25.860> instance<17:43:26.096> if<17:43:26.340> I<17:43:26.520> have<17:43:26.636> a 17:43:26.870 --> 17:43:26.880 align:start position:0% a new rule for instance if I have a 17:43:26.880 --> 17:43:28.970 align:start position:0% a new rule for instance if I have a specific<17:43:27.116> program<17:43:27.540> or<17:43:28.136> Port<17:43:28.380> that<17:43:28.740> I<17:43:28.860> know 17:43:28.970 --> 17:43:28.980 align:start position:0% specific program or Port that I know 17:43:28.980 --> 17:43:31.426 align:start position:0% specific program or Port that I know needs<17:43:29.456> to<17:43:29.580> have<17:43:29.756> access 17:43:31.426 --> 17:43:31.436 align:start position:0% needs to have access 17:43:31.436 --> 17:43:33.406 align:start position:0% needs to have access you<17:43:31.860> remember<17:43:31.980> the<17:43:32.400> ports<17:43:32.820> that<17:43:33.000> we<17:43:33.116> talked 17:43:33.406 --> 17:43:33.416 align:start position:0% you remember the ports that we talked 17:43:33.416 --> 17:43:35.746 align:start position:0% you remember the ports that we talked about<17:43:33.540> previously<17:43:34.320> and<17:43:34.916> this<17:43:35.040> is<17:43:35.160> an<17:43:35.340> example 17:43:35.746 --> 17:43:35.756 align:start position:0% about previously and this is an example 17:43:35.756 --> 17:43:38.150 align:start position:0% about previously and this is an example of<17:43:36.296> how<17:43:36.540> you<17:43:36.720> would<17:43:36.900> use<17:43:37.080> that<17:43:37.320> now<17:43:37.796> I<17:43:37.980> also 17:43:38.150 --> 17:43:38.160 align:start position:0% of how you would use that now I also 17:43:38.160 --> 17:43:40.190 align:start position:0% of how you would use that now I also have<17:43:38.276> outbound<17:43:38.700> rules<17:43:39.116> so<17:43:39.660> for<17:43:39.900> instance 17:43:40.190 --> 17:43:40.200 align:start position:0% have outbound rules so for instance 17:43:40.200 --> 17:43:42.230 align:start position:0% have outbound rules so for instance instead<17:43:40.616> of<17:43:40.680> allowing<17:43:41.096> information<17:43:41.400> into<17:43:42.000> the 17:43:42.230 --> 17:43:42.240 align:start position:0% instead of allowing information into the 17:43:42.240 --> 17:43:43.606 align:start position:0% instead of allowing information into the system<17:43:42.360> I<17:43:42.776> want<17:43:42.840> to<17:43:43.020> talk<17:43:43.080> about<17:43:43.256> information 17:43:43.606 --> 17:43:43.616 align:start position:0% system I want to talk about information 17:43:43.616 --> 17:43:46.126 align:start position:0% system I want to talk about information I<17:43:44.160> want<17:43:44.276> to<17:43:44.400> let<17:43:44.520> out<17:43:44.756> so<17:43:45.660> for<17:43:45.900> instance 17:43:46.126 --> 17:43:46.136 align:start position:0% I want to let out so for instance 17:43:46.136 --> 17:43:48.710 align:start position:0% I want to let out so for instance Windows<17:43:46.616> Media<17:43:46.980> Player<17:43:47.400> has<17:43:48.060> a<17:43:48.416> number<17:43:48.540> of 17:43:48.710 --> 17:43:48.720 align:start position:0% Windows Media Player has a number of 17:43:48.720 --> 17:43:50.810 align:start position:0% Windows Media Player has a number of rules<17:43:49.080> that<17:43:49.320> are<17:43:49.436> here<17:43:49.616> notice<17:43:50.340> that<17:43:50.456> none<17:43:50.700> of 17:43:50.810 --> 17:43:50.820 align:start position:0% rules that are here notice that none of 17:43:50.820 --> 17:43:52.190 align:start position:0% rules that are here notice that none of them<17:43:50.936> are<17:43:51.180> enabled 17:43:52.190 --> 17:43:52.200 align:start position:0% them are enabled 17:43:52.200 --> 17:43:54.530 align:start position:0% them are enabled so<17:43:52.796> if<17:43:53.040> we<17:43:53.220> were<17:43:53.400> to<17:43:53.520> check<17:43:53.700> this<17:43:53.936> one<17:43:54.060> out<17:43:54.296> for 17:43:54.530 --> 17:43:54.540 align:start position:0% so if we were to check this one out for 17:43:54.540 --> 17:43:56.330 align:start position:0% so if we were to check this one out for instance<17:43:54.776> it<17:43:55.200> says<17:43:55.500> there's<17:43:55.680> an<17:43:55.980> outbound 17:43:56.330 --> 17:43:56.340 align:start position:0% instance it says there's an outbound 17:43:56.340 --> 17:43:59.990 align:start position:0% instance it says there's an outbound rule<17:43:56.756> to<17:43:57.416> allow<17:43:57.660> the<17:43:57.840> sharing<17:43:58.256> service<17:43:58.860> for<17:43:59.756> a 17:43:59.990 --> 17:44:00.000 align:start position:0% rule to allow the sharing service for a 17:44:00.000 --> 17:44:02.330 align:start position:0% rule to allow the sharing service for a Windows<17:44:00.360> Media<17:44:00.660> Player<17:44:00.956> now<17:44:01.616> I<17:44:01.980> could<17:44:02.040> enable 17:44:02.330 --> 17:44:02.340 align:start position:0% Windows Media Player now I could enable 17:44:02.340 --> 17:44:04.070 align:start position:0% Windows Media Player now I could enable this<17:44:02.636> and<17:44:02.820> that<17:44:03.000> would<17:44:03.116> allow<17:44:03.416> it<17:44:03.596> to<17:44:03.776> occur 17:44:04.070 --> 17:44:04.080 align:start position:0% this and that would allow it to occur 17:44:04.080 --> 17:44:06.106 align:start position:0% this and that would allow it to occur but<17:44:04.560> because<17:44:04.796> it<17:44:05.096> is<17:44:05.276> disabled<17:44:05.820> to<17:44:05.936> this 17:44:06.106 --> 17:44:06.116 align:start position:0% but because it is disabled to this 17:44:06.116 --> 17:44:07.730 align:start position:0% but because it is disabled to this moment<17:44:06.416> it's<17:44:06.776> actually<17:44:06.956> not<17:44:07.200> going<17:44:07.380> to<17:44:07.500> allow 17:44:07.730 --> 17:44:07.740 align:start position:0% moment it's actually not going to allow 17:44:07.740 --> 17:44:10.010 align:start position:0% moment it's actually not going to allow any<17:44:07.916> of<17:44:08.160> that<17:44:08.276> information<17:44:08.520> out<17:44:09.116> so<17:44:09.720> this<17:44:09.900> is 17:44:10.010 --> 17:44:10.020 align:start position:0% any of that information out so this is 17:44:10.020 --> 17:44:12.050 align:start position:0% any of that information out so this is how<17:44:10.436> very<17:44:11.096> quickly 17:44:12.050 --> 17:44:12.060 align:start position:0% how very quickly 17:44:12.060 --> 17:44:15.286 align:start position:0% how very quickly the<17:44:12.660> firewall<17:44:13.136> works<17:44:13.616> on<17:44:14.276> your<17:44:14.456> software<17:44:14.820> but 17:44:15.286 --> 17:44:15.296 align:start position:0% the firewall works on your software but 17:44:15.296 --> 17:44:16.850 align:start position:0% the firewall works on your software but it<17:44:15.416> would<17:44:15.540> also<17:44:15.776> work<17:44:15.956> the<17:44:16.200> same<17:44:16.380> way<17:44:16.500> if<17:44:16.680> you 17:44:16.850 --> 17:44:16.860 align:start position:0% it would also work the same way if you 17:44:16.860 --> 17:44:19.310 align:start position:0% it would also work the same way if you had<17:44:17.040> a<17:44:17.276> hardware<17:44:17.456> device<17:44:17.880> too<17:44:18.296> you<17:44:19.020> can<17:44:19.080> also 17:44:19.310 --> 17:44:19.320 align:start position:0% had a hardware device too you can also 17:44:19.320 --> 17:44:23.030 align:start position:0% had a hardware device too you can also have<17:44:19.616> it<17:44:19.860> monitor<17:44:20.820> what's<17:44:21.360> going<17:44:21.596> on<17:44:21.900> so<17:44:22.740> for 17:44:23.030 --> 17:44:23.040 align:start position:0% have it monitor what's going on so for 17:44:23.040 --> 17:44:24.586 align:start position:0% have it monitor what's going on so for instance<17:44:23.276> this<17:44:23.580> is<17:44:23.700> telling<17:44:24.000> me<17:44:24.116> that<17:44:24.360> the 17:44:24.586 --> 17:44:24.596 align:start position:0% instance this is telling me that the 17:44:24.596 --> 17:44:26.870 align:start position:0% instance this is telling me that the inbound<17:44:24.900> connections<17:44:25.560> aren't<17:44:25.860> matching<17:44:26.340> a 17:44:26.870 --> 17:44:26.880 align:start position:0% inbound connections aren't matching a 17:44:26.880 --> 17:44:28.906 align:start position:0% inbound connections aren't matching a rule<17:44:27.180> so<17:44:27.596> that<17:44:27.720> I<17:44:27.900> could<17:44:28.020> go<17:44:28.200> in<17:44:28.320> and<17:44:28.500> check<17:44:28.740> out 17:44:28.906 --> 17:44:28.916 align:start position:0% rule so that I could go in and check out 17:44:28.916 --> 17:44:30.946 align:start position:0% rule so that I could go in and check out exactly<17:44:29.456> what<17:44:29.820> that<17:44:30.060> is 17:44:30.946 --> 17:44:30.956 align:start position:0% exactly what that is 17:44:30.956 --> 17:44:33.530 align:start position:0% exactly what that is and<17:44:31.680> it's<17:44:31.916> also<17:44:32.220> telling<17:44:32.520> me<17:44:32.580> I<17:44:32.936> can<17:44:33.060> see<17:44:33.296> all 17:44:33.530 --> 17:44:33.540 align:start position:0% and it's also telling me I can see all 17:44:33.540 --> 17:44:36.650 align:start position:0% and it's also telling me I can see all the<17:44:33.776> active<17:44:34.400> rules<17:44:35.400> and<17:44:35.700> so<17:44:35.820> on<17:44:36.000> that<17:44:36.540> are 17:44:36.650 --> 17:44:36.660 align:start position:0% the active rules and so on that are 17:44:36.660 --> 17:44:38.810 align:start position:0% the active rules and so on that are going<17:44:36.900> on<17:44:37.136> here<17:44:37.380> now<17:44:37.916> here's<17:44:38.220> an<17:44:38.340> example<17:44:38.636> of 17:44:38.810 --> 17:44:38.820 align:start position:0% going on here now here's an example of 17:44:38.820 --> 17:44:40.906 align:start position:0% going on here now here's an example of what<17:44:39.000> a<17:44:39.116> fire<17:44:39.240> mole<17:44:39.720> might<17:44:39.840> do<17:44:40.020> as<17:44:40.436> you<17:44:40.616> can<17:44:40.680> see 17:44:40.906 --> 17:44:40.916 align:start position:0% what a fire mole might do as you can see 17:44:40.916 --> 17:44:45.946 align:start position:0% what a fire mole might do as you can see it's<17:44:41.756> separating<17:44:42.240> the<17:44:42.840> WAN<17:44:43.200> which<17:44:44.160> usually 17:44:45.946 --> 17:44:45.956 align:start position:0% it's separating the WAN which usually 17:44:45.956 --> 17:44:51.470 align:start position:0% it's separating the WAN which usually would<17:44:46.740> be<17:44:47.276> shown<17:44:48.116> by<17:44:49.080> a<17:44:49.320> cloud 17:44:51.470 --> 17:44:51.480 align:start position:0% would be shown by a cloud 17:44:51.480 --> 17:44:54.890 align:start position:0% would be shown by a cloud which<17:44:51.900> we<17:44:52.080> could<17:44:52.256> call<17:44:52.616> the<17:44:53.340> internet 17:44:54.890 --> 17:44:54.900 align:start position:0% which we could call the internet 17:44:54.900 --> 17:44:57.230 align:start position:0% which we could call the internet and<17:44:55.500> the<17:44:55.740> users<17:44:56.040> on<17:44:56.276> the<17:44:56.400> WAN<17:44:56.700> have<17:44:57.000> to<17:44:57.116> be 17:44:57.230 --> 17:44:57.240 align:start position:0% and the users on the WAN have to be 17:44:57.240 --> 17:44:59.570 align:start position:0% and the users on the WAN have to be authenticated<17:44:57.900> and<17:44:58.616> allowed<17:44:58.980> before<17:44:59.220> their 17:44:59.570 --> 17:44:59.580 align:start position:0% authenticated and allowed before their 17:44:59.580 --> 17:45:02.150 align:start position:0% authenticated and allowed before their go<17:44:59.820> past<17:45:00.116> this<17:45:00.540> firewall<17:45:01.080> this<17:45:01.796> is<17:45:01.860> useful 17:45:02.150 --> 17:45:02.160 align:start position:0% go past this firewall this is useful 17:45:02.160 --> 17:45:03.650 align:start position:0% go past this firewall this is useful because<17:45:02.276> an<17:45:02.580> attack<17:45:02.700> could<17:45:03.000> very<17:45:03.240> possibly 17:45:03.650 --> 17:45:03.660 align:start position:0% because an attack could very possibly 17:45:03.660 --> 17:45:05.810 align:start position:0% because an attack could very possibly infiltrate<17:45:04.320> the<17:45:04.560> WAN<17:45:04.860> and<17:45:05.276> try<17:45:05.400> to<17:45:05.520> get<17:45:05.700> access 17:45:05.810 --> 17:45:05.820 align:start position:0% infiltrate the WAN and try to get access 17:45:05.820 --> 17:45:07.850 align:start position:0% infiltrate the WAN and try to get access to<17:45:06.116> the<17:45:06.240> local<17:45:06.416> network<17:45:06.720> but<17:45:07.256> if<17:45:07.560> they're<17:45:07.680> not 17:45:07.850 --> 17:45:07.860 align:start position:0% to the local network but if they're not 17:45:07.860 --> 17:45:09.530 align:start position:0% to the local network but if they're not recognized<17:45:08.276> not<17:45:08.580> given<17:45:08.880> permission<17:45:09.180> by<17:45:09.360> the 17:45:09.530 --> 17:45:09.540 align:start position:0% recognized not given permission by the 17:45:09.540 --> 17:45:10.550 align:start position:0% recognized not given permission by the firewall<17:45:09.840> they're<17:45:10.020> not<17:45:10.136> going<17:45:10.256> to<17:45:10.320> be<17:45:10.380> able<17:45:10.436> to 17:45:10.550 --> 17:45:10.560 align:start position:0% firewall they're not going to be able to 17:45:10.560 --> 17:45:13.010 align:start position:0% firewall they're not going to be able to enter<17:45:10.740> the<17:45:10.980> land<17:45:11.636> sometimes<17:45:12.360> what<17:45:12.596> we'll<17:45:12.720> also 17:45:13.010 --> 17:45:13.020 align:start position:0% enter the land sometimes what we'll also 17:45:13.020 --> 17:45:14.810 align:start position:0% enter the land sometimes what we'll also have<17:45:13.256> is<17:45:13.616> a<17:45:13.796> separate<17:45:14.096> Network<17:45:14.276> that<17:45:14.636> they'll 17:45:14.810 --> 17:45:14.820 align:start position:0% have is a separate Network that they'll 17:45:14.820 --> 17:45:16.190 align:start position:0% have is a separate Network that they'll be<17:45:14.936> allowed<17:45:15.296> into 17:45:16.190 --> 17:45:16.200 align:start position:0% be allowed into 17:45:16.200 --> 17:45:18.650 align:start position:0% be allowed into that's<17:45:16.796> sort<17:45:17.220> of<17:45:17.340> not<17:45:17.580> between<17:45:17.880> the<17:45:18.240> firewall 17:45:18.650 --> 17:45:18.660 align:start position:0% that's sort of not between the firewall 17:45:18.660 --> 17:45:21.170 align:start position:0% that's sort of not between the firewall in<17:45:19.436> some<17:45:19.560> cases<17:45:19.860> even<17:45:20.096> if<17:45:20.340> I<17:45:20.456> erase<17:45:20.756> this<17:45:20.936> we'll 17:45:21.170 --> 17:45:21.180 align:start position:0% in some cases even if I erase this we'll 17:45:21.180 --> 17:45:22.670 align:start position:0% in some cases even if I erase this we'll actually<17:45:21.416> have 17:45:22.670 --> 17:45:22.680 align:start position:0% actually have 17:45:22.680 --> 17:45:26.266 align:start position:0% actually have two<17:45:23.160> firewalls 17:45:26.266 --> 17:45:26.276 align:start position:0% 17:45:26.276 --> 17:45:28.906 align:start position:0% one<17:45:27.000> which<17:45:27.240> allows<17:45:27.596> a<17:45:27.720> lot<17:45:27.840> of<17:45:28.020> stuff<17:45:28.136> in<17:45:28.380> and 17:45:28.906 --> 17:45:28.916 align:start position:0% one which allows a lot of stuff in and 17:45:28.916 --> 17:45:32.446 align:start position:0% one which allows a lot of stuff in and creates<17:45:29.276> sort<17:45:29.580> of<17:45:29.700> a<17:45:30.200> demilitarized<17:45:31.200> zone 17:45:32.446 --> 17:45:32.456 align:start position:0% creates sort of a demilitarized zone 17:45:32.456 --> 17:45:35.626 align:start position:0% creates sort of a demilitarized zone which<17:45:33.000> then<17:45:33.296> we<17:45:33.900> can<17:45:34.080> either<17:45:34.256> put<17:45:34.740> a<17:45:35.456> test 17:45:35.626 --> 17:45:35.636 align:start position:0% which then we can either put a test 17:45:35.636 --> 17:45:38.030 align:start position:0% which then we can either put a test server<17:45:36.060> on<17:45:36.240> or<17:45:36.480> a<17:45:36.596> test<17:45:36.720> computer<17:45:37.040> sometimes 17:45:38.030 --> 17:45:38.040 align:start position:0% server on or a test computer sometimes 17:45:38.040 --> 17:45:39.230 align:start position:0% server on or a test computer sometimes we'll<17:45:38.220> call<17:45:38.456> this 17:45:39.230 --> 17:45:39.240 align:start position:0% we'll call this 17:45:39.240 --> 17:45:42.530 align:start position:0% we'll call this a<17:45:39.776> Honeypot<17:45:40.320> will<17:45:41.160> allow<17:45:41.580> a<17:45:41.756> lot<17:45:41.880> of<17:45:42.000> stuff<17:45:42.240> in 17:45:42.530 --> 17:45:42.540 align:start position:0% a Honeypot will allow a lot of stuff in 17:45:42.540 --> 17:45:44.390 align:start position:0% a Honeypot will allow a lot of stuff in through<17:45:42.776> the<17:45:43.020> first<17:45:43.136> firewall 17:45:44.390 --> 17:45:44.400 align:start position:0% through the first firewall 17:45:44.400 --> 17:45:46.906 align:start position:0% through the first firewall and<17:45:45.000> then<17:45:45.240> when<17:45:45.776> the<17:45:45.956> hackers<17:45:46.320> find<17:45:46.616> stuff 17:45:46.906 --> 17:45:46.916 align:start position:0% and then when the hackers find stuff 17:45:46.916 --> 17:45:48.170 align:start position:0% and then when the hackers find stuff they're<17:45:47.220> going<17:45:47.400> to<17:45:47.520> start<17:45:47.580> attacking<17:45:48.000> this 17:45:48.170 --> 17:45:48.180 align:start position:0% they're going to start attacking this 17:45:48.180 --> 17:45:49.246 align:start position:0% they're going to start attacking this Honeypot 17:45:49.246 --> 17:45:49.256 align:start position:0% Honeypot 17:45:49.256 --> 17:45:51.650 align:start position:0% Honeypot Honeypot<17:45:50.096> being<17:45:50.340> sort<17:45:50.636> of<17:45:50.756> like<17:45:50.880> bees<17:45:51.296> go<17:45:51.540> into 17:45:51.650 --> 17:45:51.660 align:start position:0% Honeypot being sort of like bees go into 17:45:51.660 --> 17:45:53.746 align:start position:0% Honeypot being sort of like bees go into honey<17:45:51.900> we<17:45:52.740> can<17:45:52.860> then<17:45:52.980> see<17:45:53.276> what<17:45:53.636> they're 17:45:53.746 --> 17:45:53.756 align:start position:0% honey we can then see what they're 17:45:53.756 --> 17:45:55.070 align:start position:0% honey we can then see what they're looking<17:45:53.936> at<17:45:54.180> what<17:45:54.480> they're<17:45:54.660> trying<17:45:54.840> to<17:45:54.956> get 17:45:55.070 --> 17:45:55.080 align:start position:0% looking at what they're trying to get 17:45:55.080 --> 17:45:57.650 align:start position:0% looking at what they're trying to get access<17:45:55.256> to<17:45:55.860> Etc<17:45:56.040> and<17:45:56.636> this<17:45:56.756> gives<17:45:57.000> us<17:45:57.116> a<17:45:57.360> sense 17:45:57.650 --> 17:45:57.660 align:start position:0% access to Etc and this gives us a sense 17:45:57.660 --> 17:45:59.626 align:start position:0% access to Etc and this gives us a sense of<17:45:57.900> testing<17:45:58.256> the<17:45:58.436> network<17:45:58.560> security 17:45:59.626 --> 17:45:59.636 align:start position:0% of testing the network security 17:45:59.636 --> 17:46:01.490 align:start position:0% of testing the network security then<17:46:00.180> once<17:46:01.020> they<17:46:01.080> get<17:46:01.200> into<17:46:01.320> the 17:46:01.490 --> 17:46:01.500 align:start position:0% then once they get into the 17:46:01.500 --> 17:46:03.170 align:start position:0% then once they get into the demilitarized<17:46:02.276> zone<17:46:02.456> they<17:46:02.700> have<17:46:02.820> to<17:46:02.936> pass 17:46:03.170 --> 17:46:03.180 align:start position:0% demilitarized zone they have to pass 17:46:03.180 --> 17:46:05.446 align:start position:0% demilitarized zone they have to pass another<17:46:03.480> set<17:46:03.776> of<17:46:03.900> protocols<17:46:04.320> to<17:46:04.560> get<17:46:04.680> in<17:46:05.040> to 17:46:05.446 --> 17:46:05.456 align:start position:0% another set of protocols to get in to 17:46:05.456 --> 17:46:07.730 align:start position:0% another set of protocols to get in to our<17:46:05.636> Network<17:46:05.820> and<17:46:06.480> as<17:46:06.596> we<17:46:06.776> mentioned<17:46:07.200> there 17:46:07.730 --> 17:46:07.740 align:start position:0% our Network and as we mentioned there 17:46:07.740 --> 17:46:10.670 align:start position:0% our Network and as we mentioned there might<17:46:07.980> also<17:46:08.340> be<17:46:08.520> firewalls 17:46:10.670 --> 17:46:10.680 align:start position:0% might also be firewalls 17:46:10.680 --> 17:46:13.786 align:start position:0% might also be firewalls on<17:46:11.340> each<17:46:11.636> one<17:46:11.936> of<17:46:12.660> these<17:46:12.900> computers<17:46:13.320> if<17:46:13.680> you 17:46:13.786 --> 17:46:13.796 align:start position:0% on each one of these computers if you 17:46:13.796 --> 17:46:16.786 align:start position:0% on each one of these computers if you can<17:46:13.916> pardon<17:46:14.400> my<17:46:14.936> awful<17:46:15.240> drawing 17:46:16.786 --> 17:46:16.796 align:start position:0% can pardon my awful drawing 17:46:16.796 --> 17:46:18.530 align:start position:0% can pardon my awful drawing so<17:46:17.580> we're<17:46:17.756> going<17:46:17.880> to<17:46:17.936> have<17:46:18.116> software 17:46:18.530 --> 17:46:18.540 align:start position:0% so we're going to have software 17:46:18.540 --> 17:46:20.030 align:start position:0% so we're going to have software firewalls<17:46:19.200> just<17:46:19.320> like<17:46:19.436> we<17:46:19.616> have<17:46:19.740> Hardware 17:46:20.030 --> 17:46:20.040 align:start position:0% firewalls just like we have Hardware 17:46:20.040 --> 17:46:23.870 align:start position:0% firewalls just like we have Hardware firewalls<17:46:20.820> in<17:46:21.296> fact<17:46:21.416> this<17:46:21.720> might<17:46:21.956> be<17:46:22.080> a<17:46:22.436> device 17:46:23.870 --> 17:46:23.880 align:start position:0% firewalls in fact this might be a device 17:46:23.880 --> 17:46:26.626 align:start position:0% firewalls in fact this might be a device or<17:46:24.360> it<17:46:24.480> could<17:46:24.596> be<17:46:24.776> a<17:46:25.080> server 17:46:26.626 --> 17:46:26.636 align:start position:0% or it could be a server 17:46:26.636 --> 17:46:29.330 align:start position:0% or it could be a server with<17:46:27.240> firewall<17:46:27.776> software<17:46:28.200> built<17:46:28.616> in 17:46:29.330 --> 17:46:29.340 align:start position:0% with firewall software built in 17:46:29.340 --> 17:46:31.970 align:start position:0% with firewall software built in now<17:46:29.756> anti-virus<17:46:30.720> software<17:46:31.256> is<17:46:31.500> everywhere 17:46:31.970 --> 17:46:31.980 align:start position:0% now anti-virus software is everywhere 17:46:31.980 --> 17:46:33.170 align:start position:0% now anti-virus software is everywhere and<17:46:32.220> there<17:46:32.400> are<17:46:32.520> more<17:46:32.636> companies<17:46:32.936> and 17:46:33.170 --> 17:46:33.180 align:start position:0% and there are more companies and 17:46:33.180 --> 17:46:35.446 align:start position:0% and there are more companies and softwares<17:46:33.660> that<17:46:33.840> protect<17:46:34.200> against<17:46:34.740> attacks 17:46:35.446 --> 17:46:35.456 align:start position:0% softwares that protect against attacks 17:46:35.456 --> 17:46:37.370 align:start position:0% softwares that protect against attacks than<17:46:35.636> you<17:46:35.820> can<17:46:35.936> count<17:46:36.180> some<17:46:36.900> of<17:46:37.020> the<17:46:37.080> ones<17:46:37.256> you 17:46:37.370 --> 17:46:37.380 align:start position:0% than you can count some of the ones you 17:46:37.380 --> 17:46:41.510 align:start position:0% than you can count some of the ones you might<17:46:37.500> even<17:46:37.680> know<17:46:37.980> are<17:46:38.456> for<17:46:39.240> instance<17:46:39.596> McAfee 17:46:41.510 --> 17:46:41.520 align:start position:0% might even know are for instance McAfee 17:46:41.520 --> 17:46:45.586 align:start position:0% might even know are for instance McAfee and<17:46:42.416> Norton<17:46:43.080> two<17:46:43.500> big<17:46:43.740> ones<17:46:44.096> there's<17:46:44.700> also<17:46:45.000> AVG 17:46:45.586 --> 17:46:45.596 align:start position:0% and Norton two big ones there's also AVG 17:46:45.596 --> 17:46:48.946 align:start position:0% and Norton two big ones there's also AVG which<17:46:45.900> offers<17:46:46.200> a<17:46:46.436> free<17:46:46.560> one<17:46:47.000> Trend<17:46:48.000> and<17:46:48.776> the 17:46:48.946 --> 17:46:48.956 align:start position:0% which offers a free one Trend and the 17:46:48.956 --> 17:46:50.810 align:start position:0% which offers a free one Trend and the list<17:46:49.080> goes<17:46:49.436> on<17:46:49.500> and<17:46:49.680> on<17:46:49.860> and<17:46:49.980> on<17:46:50.160> now<17:46:50.636> in 17:46:50.810 --> 17:46:50.820 align:start position:0% list goes on and on and on now in 17:46:50.820 --> 17:46:52.426 align:start position:0% list goes on and on and on now in general<17:46:50.936> most<17:46:51.296> of<17:46:51.480> the<17:46:51.596> software<17:46:51.956> is<17:46:52.136> pretty 17:46:52.426 --> 17:46:52.436 align:start position:0% general most of the software is pretty 17:46:52.436 --> 17:46:54.350 align:start position:0% general most of the software is pretty similar<17:46:52.860> and<17:46:53.276> they<17:46:53.400> all<17:46:53.580> do<17:46:53.700> the<17:46:53.880> same<17:46:54.060> types 17:46:54.350 --> 17:46:54.360 align:start position:0% similar and they all do the same types 17:46:54.360 --> 17:46:55.850 align:start position:0% similar and they all do the same types of<17:46:54.480> things<17:46:54.660> some<17:46:54.956> more<17:46:55.200> expensive<17:46:55.616> than<17:46:55.740> the 17:46:55.850 --> 17:46:55.860 align:start position:0% of things some more expensive than the 17:46:55.860 --> 17:46:58.310 align:start position:0% of things some more expensive than the others<17:46:56.160> some<17:46:56.636> are<17:46:56.820> more<17:46:57.000> for<17:46:57.416> Enterprises 17:46:58.310 --> 17:46:58.320 align:start position:0% others some are more for Enterprises 17:46:58.320 --> 17:47:00.350 align:start position:0% others some are more for Enterprises they<17:46:58.740> have<17:46:58.916> a<17:46:59.096> server<17:46:59.400> set<17:46:59.636> up<17:46:59.820> so<17:47:00.060> you<17:47:00.240> could 17:47:00.350 --> 17:47:00.360 align:start position:0% they have a server set up so you could 17:47:00.360 --> 17:47:02.510 align:start position:0% they have a server set up so you could monitor<17:47:00.776> your<17:47:01.136> entire<17:47:01.380> network<17:47:01.740> without 17:47:02.510 --> 17:47:02.520 align:start position:0% monitor your entire network without 17:47:02.520 --> 17:47:04.786 align:start position:0% monitor your entire network without having<17:47:03.060> to<17:47:03.540> go<17:47:03.840> to<17:47:03.956> each<17:47:04.136> individual<17:47:04.560> computer 17:47:04.786 --> 17:47:04.796 align:start position:0% having to go to each individual computer 17:47:04.796 --> 17:47:07.126 align:start position:0% having to go to each individual computer but<17:47:05.400> in<17:47:05.520> effect<17:47:05.636> they<17:47:06.060> all<17:47:06.180> do<17:47:06.360> the<17:47:06.660> same<17:47:06.840> thing 17:47:07.126 --> 17:47:07.136 align:start position:0% but in effect they all do the same thing 17:47:07.136 --> 17:47:09.050 align:start position:0% but in effect they all do the same thing so<17:47:07.860> although<17:47:08.096> a<17:47:08.220> firewall<17:47:08.580> is<17:47:08.700> a<17:47:08.820> really<17:47:08.880> good 17:47:09.050 --> 17:47:09.060 align:start position:0% so although a firewall is a really good 17:47:09.060 --> 17:47:10.426 align:start position:0% so although a firewall is a really good resource<17:47:09.360> against<17:47:09.540> attacks<17:47:10.136> there's<17:47:10.256> nothing 17:47:10.426 --> 17:47:10.436 align:start position:0% resource against attacks there's nothing 17:47:10.436 --> 17:47:13.190 align:start position:0% resource against attacks there's nothing it<17:47:10.740> can<17:47:10.916> do<17:47:11.180> once<17:47:12.180> the<17:47:12.360> attack<17:47:12.540> has<17:47:13.020> already 17:47:13.190 --> 17:47:13.200 align:start position:0% it can do once the attack has already 17:47:13.200 --> 17:47:16.606 align:start position:0% it can do once the attack has already taken<17:47:13.616> place<17:47:13.860> once<17:47:14.820> the<17:47:15.136> system<17:47:16.136> is<17:47:16.436> already 17:47:16.606 --> 17:47:16.616 align:start position:0% taken place once the system is already 17:47:16.616 --> 17:47:19.010 align:start position:0% taken place once the system is already infiltrated<17:47:17.276> so<17:47:18.180> attacks<17:47:18.660> are<17:47:18.720> not<17:47:18.900> always 17:47:19.010 --> 17:47:19.020 align:start position:0% infiltrated so attacks are not always 17:47:19.020 --> 17:47:21.050 align:start position:0% infiltrated so attacks are not always obvious<17:47:19.560> and<17:47:19.916> sometimes<17:47:20.276> attacks<17:47:20.820> are<17:47:20.880> so 17:47:21.050 --> 17:47:21.060 align:start position:0% obvious and sometimes attacks are so 17:47:21.060 --> 17:47:22.850 align:start position:0% obvious and sometimes attacks are so subtle<17:47:21.360> they<17:47:21.480> happen<17:47:21.660> right<17:47:21.956> under<17:47:22.136> our<17:47:22.380> noses 17:47:22.850 --> 17:47:22.860 align:start position:0% subtle they happen right under our noses 17:47:22.860 --> 17:47:25.070 align:start position:0% subtle they happen right under our noses you<17:47:23.340> might<17:47:23.400> not<17:47:23.580> even<17:47:23.700> know<17:47:23.936> you<17:47:24.296> have<17:47:24.540> a<17:47:24.776> virus 17:47:25.070 --> 17:47:25.080 align:start position:0% you might not even know you have a virus 17:47:25.080 --> 17:47:27.350 align:start position:0% you might not even know you have a virus until<17:47:25.380> it's<17:47:25.680> already<17:47:25.796> done<17:47:26.040> damage<17:47:26.456> so<17:47:27.116> even 17:47:27.350 --> 17:47:27.360 align:start position:0% until it's already done damage so even 17:47:27.360 --> 17:47:29.390 align:start position:0% until it's already done damage so even though<17:47:27.540> firewall<17:47:27.956> protects<17:47:28.436> the<17:47:28.616> attack<17:47:28.796> it 17:47:29.390 --> 17:47:29.400 align:start position:0% though firewall protects the attack it 17:47:29.400 --> 17:47:30.586 align:start position:0% though firewall protects the attack it can't<17:47:29.520> get<17:47:29.700> rid<17:47:29.820> of<17:47:29.936> the<17:47:30.000> malicious<17:47:30.416> things 17:47:30.586 --> 17:47:30.596 align:start position:0% can't get rid of the malicious things 17:47:30.596 --> 17:47:32.086 align:start position:0% can't get rid of the malicious things that<17:47:30.776> have<17:47:30.900> gotten<17:47:31.200> through<17:47:31.320> this<17:47:31.860> is<17:47:31.980> where 17:47:32.086 --> 17:47:32.096 align:start position:0% that have gotten through this is where 17:47:32.096 --> 17:47:34.126 align:start position:0% that have gotten through this is where antivirus<17:47:32.756> comes<17:47:33.116> in 17:47:34.126 --> 17:47:34.136 align:start position:0% antivirus comes in 17:47:34.136 --> 17:47:37.010 align:start position:0% antivirus comes in this<17:47:34.916> software<17:47:35.276> has<17:47:35.456> many<17:47:35.700> functions<17:47:36.240> one<17:47:36.956> of 17:47:37.010 --> 17:47:37.020 align:start position:0% this software has many functions one of 17:47:37.020 --> 17:47:38.446 align:start position:0% this software has many functions one of the<17:47:37.080> more<17:47:37.256> important<17:47:37.616> ones<17:47:37.916> is<17:47:38.160> that<17:47:38.276> it 17:47:38.446 --> 17:47:38.456 align:start position:0% the more important ones is that it 17:47:38.456 --> 17:47:41.446 align:start position:0% the more important ones is that it offers<17:47:38.820> real-time<17:47:39.776> protection<17:47:40.436> the<17:47:41.096> software 17:47:41.446 --> 17:47:41.456 align:start position:0% offers real-time protection the software 17:47:41.456 --> 17:47:43.070 align:start position:0% offers real-time protection the software is<17:47:41.580> constantly<17:47:42.000> on<17:47:42.116> the<17:47:42.180> lookout<17:47:42.416> for<17:47:42.596> attacks 17:47:43.070 --> 17:47:43.080 align:start position:0% is constantly on the lookout for attacks 17:47:43.080 --> 17:47:44.446 align:start position:0% is constantly on the lookout for attacks and<17:47:43.136> malicious<17:47:43.560> things<17:47:43.796> software<17:47:44.340> that 17:47:44.446 --> 17:47:44.456 align:start position:0% and malicious things software that 17:47:44.456 --> 17:47:46.490 align:start position:0% and malicious things software that doesn't<17:47:44.636> look<17:47:44.880> right<17:47:45.116> and<17:47:45.720> firewalls<17:47:46.256> merely 17:47:46.490 --> 17:47:46.500 align:start position:0% doesn't look right and firewalls merely 17:47:46.500 --> 17:47:48.286 align:start position:0% doesn't look right and firewalls merely block<17:47:46.740> the<17:47:47.040> attacks<17:47:47.340> whereas<17:47:47.700> antivirus 17:47:48.286 --> 17:47:48.296 align:start position:0% block the attacks whereas antivirus 17:47:48.296 --> 17:47:50.510 align:start position:0% block the attacks whereas antivirus software<17:47:48.660> will<17:47:48.776> go<17:47:49.020> after<17:47:49.320> an<17:47:49.680> attack<17:47:49.860> before 17:47:50.510 --> 17:47:50.520 align:start position:0% software will go after an attack before 17:47:50.520 --> 17:47:53.330 align:start position:0% software will go after an attack before it<17:47:50.820> goes<17:47:51.136> before<17:47:52.136> it<17:47:52.560> can<17:47:52.680> get<17:47:52.916> through<17:47:53.096> the 17:47:53.330 --> 17:47:53.340 align:start position:0% it goes before it can get through the 17:47:53.340 --> 17:47:56.390 align:start position:0% it goes before it can get through the firewall<17:47:53.820> now<17:47:54.596> uh<17:47:55.320> this<17:47:55.616> software<17:47:55.916> can<17:47:56.096> also 17:47:56.390 --> 17:47:56.400 align:start position:0% firewall now uh this software can also 17:47:56.400 --> 17:47:58.370 align:start position:0% firewall now uh this software can also scan<17:47:56.756> for<17:47:56.936> viruses<17:47:57.416> and<17:47:57.660> remove<17:47:57.840> them<17:47:58.020> once 17:47:58.370 --> 17:47:58.380 align:start position:0% scan for viruses and remove them once 17:47:58.380 --> 17:48:00.106 align:start position:0% scan for viruses and remove them once they're<17:47:58.500> found<17:47:58.740> now<17:47:59.340> sometimes<17:47:59.700> this<17:47:59.880> can<17:48:00.000> be 17:48:00.106 --> 17:48:00.116 align:start position:0% they're found now sometimes this can be 17:48:00.116 --> 17:48:03.170 align:start position:0% they're found now sometimes this can be tricky<17:48:00.540> because<17:48:01.436> just<17:48:02.096> like<17:48:02.400> if<17:48:02.880> I<17:48:03.000> install 17:48:03.170 --> 17:48:03.180 align:start position:0% tricky because just like if I install 17:48:03.180 --> 17:48:05.926 align:start position:0% tricky because just like if I install the<17:48:03.596> antivirus<17:48:04.200> software 17:48:05.926 --> 17:48:05.936 align:start position:0% the antivirus software 17:48:05.936 --> 17:48:09.766 align:start position:0% the antivirus software after 17:48:09.766 --> 17:48:09.776 align:start position:0% 17:48:09.776 --> 17:48:11.926 align:start position:0% the<17:48:10.320> virus<17:48:10.560> has<17:48:10.740> infected<17:48:11.160> my<17:48:11.340> system<17:48:11.520> the 17:48:11.926 --> 17:48:11.936 align:start position:0% the virus has infected my system the 17:48:11.936 --> 17:48:13.850 align:start position:0% the virus has infected my system the viruses<17:48:12.416> might<17:48:12.720> not<17:48:12.900> be<17:48:12.956> found<17:48:13.200> by<17:48:13.380> the<17:48:13.560> virus 17:48:13.850 --> 17:48:13.860 align:start position:0% viruses might not be found by the virus 17:48:13.860 --> 17:48:16.370 align:start position:0% viruses might not be found by the virus software<17:48:14.276> it's<17:48:15.060> also<17:48:15.416> going<17:48:15.900> to<17:48:16.080> look<17:48:16.200> at 17:48:16.370 --> 17:48:16.380 align:start position:0% software it's also going to look at 17:48:16.380 --> 17:48:19.010 align:start position:0% software it's also going to look at suspicious<17:48:16.916> files<17:48:17.276> and<17:48:17.400> data<17:48:17.756> and<17:48:18.540> place<17:48:18.720> them 17:48:19.010 --> 17:48:19.020 align:start position:0% suspicious files and data and place them 17:48:19.020 --> 17:48:21.766 align:start position:0% suspicious files and data and place them into<17:48:19.380> what<17:48:19.740> we<17:48:19.916> call<17:48:20.096> the<17:48:20.636> quarantine 17:48:21.766 --> 17:48:21.776 align:start position:0% into what we call the quarantine 17:48:21.776 --> 17:48:24.650 align:start position:0% into what we call the quarantine the<17:48:22.200> quarantine<17:48:22.680> just<17:48:23.096> like<17:48:23.276> the<17:48:23.520> name<17:48:23.756> is<17:48:24.480> a 17:48:24.650 --> 17:48:24.660 align:start position:0% the quarantine just like the name is a 17:48:24.660 --> 17:48:25.730 align:start position:0% the quarantine just like the name is a place<17:48:24.840> where<17:48:25.080> we're<17:48:25.200> going<17:48:25.380> to<17:48:25.380> put<17:48:25.560> all<17:48:25.616> those 17:48:25.730 --> 17:48:25.740 align:start position:0% place where we're going to put all those 17:48:25.740 --> 17:48:27.830 align:start position:0% place where we're going to put all those files<17:48:26.096> that<17:48:26.340> might<17:48:26.520> be<17:48:26.636> infected<17:48:27.180> and<17:48:27.720> that 17:48:27.830 --> 17:48:27.840 align:start position:0% files that might be infected and that 17:48:27.840 --> 17:48:29.870 align:start position:0% files that might be infected and that way<17:48:28.020> we<17:48:28.200> can<17:48:28.380> make<17:48:28.616> sure<17:48:28.860> that<17:48:29.276> we<17:48:29.520> can<17:48:29.636> look 17:48:29.870 --> 17:48:29.880 align:start position:0% way we can make sure that we can look 17:48:29.880 --> 17:48:31.490 align:start position:0% way we can make sure that we can look over<17:48:30.060> them<17:48:30.240> as<17:48:30.416> an<17:48:30.596> administrators<17:48:31.136> see<17:48:31.320> if 17:48:31.490 --> 17:48:31.500 align:start position:0% over them as an administrators see if 17:48:31.500 --> 17:48:33.050 align:start position:0% over them as an administrators see if they're<17:48:31.616> infected<17:48:32.096> and<17:48:32.276> either<17:48:32.456> delete<17:48:32.700> them 17:48:33.050 --> 17:48:33.060 align:start position:0% they're infected and either delete them 17:48:33.060 --> 17:48:35.870 align:start position:0% they're infected and either delete them or<17:48:33.900> bring<17:48:34.136> them<17:48:34.320> back<17:48:34.500> into<17:48:34.616> the<17:48:34.860> network 17:48:35.870 --> 17:48:35.880 align:start position:0% or bring them back into the network 17:48:35.880 --> 17:48:37.730 align:start position:0% or bring them back into the network finally<17:48:36.540> antivirus<17:48:37.136> software<17:48:37.436> is<17:48:37.560> going<17:48:37.680> to 17:48:37.730 --> 17:48:37.740 align:start position:0% finally antivirus software is going to 17:48:37.740 --> 17:48:40.970 align:start position:0% finally antivirus software is going to update<17:48:38.096> itself<17:48:38.840> constantly<17:48:39.840> if<17:48:40.616> you<17:48:40.796> imagine 17:48:40.970 --> 17:48:40.980 align:start position:0% update itself constantly if you imagine 17:48:40.980 --> 17:48:43.850 align:start position:0% update itself constantly if you imagine that<17:48:41.936> viruses<17:48:42.840> and<17:48:43.020> hackers<17:48:43.320> are<17:48:43.560> constantly 17:48:43.850 --> 17:48:43.860 align:start position:0% that viruses and hackers are constantly 17:48:43.860 --> 17:48:45.530 align:start position:0% that viruses and hackers are constantly doing<17:48:44.040> their<17:48:44.340> work<17:48:44.520> to<17:48:44.820> keep<17:48:44.936> everything<17:48:45.180> up 17:48:45.530 --> 17:48:45.540 align:start position:0% doing their work to keep everything up 17:48:45.540 --> 17:48:47.746 align:start position:0% doing their work to keep everything up to<17:48:45.660> date<17:48:45.840> well<17:48:46.560> then<17:48:46.796> you<17:48:47.160> probably<17:48:47.340> have<17:48:47.580> an 17:48:47.746 --> 17:48:47.756 align:start position:0% to date well then you probably have an 17:48:47.756 --> 17:48:50.266 align:start position:0% to date well then you probably have an understanding<17:48:48.500> that<17:48:49.500> we<17:48:49.740> need<17:48:49.860> to<17:48:49.980> keep<17:48:50.096> the 17:48:50.266 --> 17:48:50.276 align:start position:0% understanding that we need to keep the 17:48:50.276 --> 17:48:52.606 align:start position:0% understanding that we need to keep the antivirus<17:48:50.880> software<17:48:51.240> up<17:48:51.416> to<17:48:51.596> date<17:48:51.776> just<17:48:52.436> like 17:48:52.606 --> 17:48:52.616 align:start position:0% antivirus software up to date just like 17:48:52.616 --> 17:48:55.786 align:start position:0% antivirus software up to date just like every<17:48:52.860> year<17:48:53.096> we<17:48:53.520> have<17:48:53.636> to<17:48:53.880> create<17:48:54.116> new<17:48:54.796> uh 17:48:55.786 --> 17:48:55.796 align:start position:0% every year we have to create new uh 17:48:55.796 --> 17:48:58.970 align:start position:0% every year we have to create new uh vaccines<17:48:56.340> for<17:48:57.060> the<17:48:57.296> flu<17:48:57.480> and<17:48:57.956> so<17:48:58.080> on<17:48:58.256> we<17:48:58.860> want 17:48:58.970 --> 17:48:58.980 align:start position:0% vaccines for the flu and so on we want 17:48:58.980 --> 17:49:00.470 align:start position:0% vaccines for the flu and so on we want to<17:48:59.096> make<17:48:59.160> sure<17:48:59.340> that<17:48:59.456> the<17:48:59.580> antivirus<17:49:00.116> software 17:49:00.470 --> 17:49:00.480 align:start position:0% to make sure that the antivirus software 17:49:00.480 --> 17:49:02.570 align:start position:0% to make sure that the antivirus software is<17:49:00.596> kept<17:49:00.840> to<17:49:00.956> date<17:49:01.320> this<17:49:01.916> is<17:49:02.040> generally<17:49:02.340> what's 17:49:02.570 --> 17:49:02.580 align:start position:0% is kept to date this is generally what's 17:49:02.580 --> 17:49:05.690 align:start position:0% is kept to date this is generally what's referred<17:49:02.936> to<17:49:03.060> as<17:49:03.360> data<17:49:03.956> files<17:49:04.320> or<17:49:04.616> dat<17:49:04.980> files 17:49:05.690 --> 17:49:05.700 align:start position:0% referred to as data files or dat files 17:49:05.700 --> 17:49:07.786 align:start position:0% referred to as data files or dat files and<17:49:06.296> you<17:49:06.596> used<17:49:06.776> to<17:49:06.900> have<17:49:07.020> to<17:49:07.256> download<17:49:07.436> these 17:49:07.786 --> 17:49:07.796 align:start position:0% and you used to have to download these 17:49:07.796 --> 17:49:09.946 align:start position:0% and you used to have to download these off<17:49:07.916> the<17:49:08.096> internet<17:49:08.220> and<17:49:08.756> install<17:49:08.936> them<17:49:09.296> now 17:49:09.946 --> 17:49:09.956 align:start position:0% off the internet and install them now 17:49:09.956 --> 17:49:12.830 align:start position:0% off the internet and install them now this<17:49:10.380> happens<17:49:10.616> usually<17:49:11.296> automatically<17:49:12.296> just 17:49:12.830 --> 17:49:12.840 align:start position:0% this happens usually automatically just 17:49:12.840 --> 17:49:15.350 align:start position:0% this happens usually automatically just like<17:49:13.020> Windows<17:49:13.560> update<17:49:13.980> but<17:49:14.756> we<17:49:15.000> need<17:49:15.116> to<17:49:15.240> make 17:49:15.350 --> 17:49:15.360 align:start position:0% like Windows update but we need to make 17:49:15.360 --> 17:49:17.446 align:start position:0% like Windows update but we need to make sure<17:49:15.540> the<17:49:15.776> setting<17:49:16.136> is<17:49:16.380> correct<17:49:16.796> so<17:49:17.040> that<17:49:17.276> it 17:49:17.446 --> 17:49:17.456 align:start position:0% sure the setting is correct so that it 17:49:17.456 --> 17:49:19.126 align:start position:0% sure the setting is correct so that it allows<17:49:18.180> itself<17:49:18.416> to<17:49:18.660> be<17:49:18.776> updated 17:49:19.126 --> 17:49:19.136 align:start position:0% allows itself to be updated 17:49:19.136 --> 17:49:21.830 align:start position:0% allows itself to be updated automatically 17:49:21.830 --> 17:49:21.840 align:start position:0% 17:49:21.840 --> 17:49:24.406 align:start position:0% so<17:49:22.560> just<17:49:22.916> to<17:49:23.096> recap<17:49:23.456> we<17:49:23.820> talked<17:49:24.060> about<17:49:24.116> a 17:49:24.406 --> 17:49:24.416 align:start position:0% so just to recap we talked about a 17:49:24.416 --> 17:49:29.470 align:start position:0% so just to recap we talked about a firewall<17:49:24.900> remember<17:49:25.560> it<17:49:26.400> works<17:49:26.700> with<17:49:27.000> inbound 17:49:29.470 --> 17:49:29.480 align:start position:0% firewall remember it works with inbound 17:49:29.480 --> 17:49:32.990 align:start position:0% firewall remember it works with inbound and<17:49:30.480> outbound<17:49:31.080> ports<17:49:31.740> it's<17:49:32.400> going<17:49:32.580> to<17:49:32.636> allow 17:49:32.990 --> 17:49:33.000 align:start position:0% and outbound ports it's going to allow 17:49:33.000 --> 17:49:35.926 align:start position:0% and outbound ports it's going to allow some<17:49:33.360> good<17:49:33.660> things<17:49:33.956> and<17:49:34.500> good<17:49:34.860> things<17:49:35.040> out<17:49:35.400> but 17:49:35.926 --> 17:49:35.936 align:start position:0% some good things and good things out but 17:49:35.936 --> 17:49:39.106 align:start position:0% some good things and good things out but it<17:49:36.060> keeps<17:49:36.360> the<17:49:36.540> ins<17:49:36.956> the<17:49:37.436> bad<17:49:37.796> stuff<17:49:38.096> out<17:49:38.580> and 17:49:39.106 --> 17:49:39.116 align:start position:0% it keeps the ins the bad stuff out and 17:49:39.116 --> 17:49:40.606 align:start position:0% it keeps the ins the bad stuff out and the<17:49:39.296> good<17:49:39.480> stuff<17:49:39.720> in 17:49:40.606 --> 17:49:40.616 align:start position:0% the good stuff in 17:49:40.616 --> 17:49:42.710 align:start position:0% the good stuff in we're<17:49:41.040> also<17:49:41.276> going<17:49:41.400> to<17:49:41.456> identify<17:49:42.060> we<17:49:42.540> also 17:49:42.710 --> 17:49:42.720 align:start position:0% we're also going to identify we also 17:49:42.720 --> 17:49:44.926 align:start position:0% we're also going to identify we also identified<17:49:43.080> rather<17:49:43.500> its<17:49:43.916> importance<17:49:44.276> talking 17:49:44.926 --> 17:49:44.936 align:start position:0% identified rather its importance talking 17:49:44.936 --> 17:49:49.426 align:start position:0% identified rather its importance talking about<17:49:45.180> how<17:49:45.596> we<17:49:45.776> can<17:49:46.256> have<17:49:46.500> several<17:49:47.096> Hardware 17:49:49.426 --> 17:49:49.436 align:start position:0% about how we can have several Hardware 17:49:49.436 --> 17:49:52.850 align:start position:0% about how we can have several Hardware and<17:49:50.160> software<17:49:50.636> firewall<17:49:51.180> Solutions 17:49:52.850 --> 17:49:52.860 align:start position:0% and software firewall Solutions 17:49:52.860 --> 17:49:56.210 align:start position:0% and software firewall Solutions and<17:49:53.700> again<17:49:53.880> we<17:49:54.360> might<17:49:54.540> have<17:49:54.776> to<17:49:55.080> manually<17:49:55.560> edit 17:49:56.210 --> 17:49:56.220 align:start position:0% and again we might have to manually edit 17:49:56.220 --> 17:49:59.926 align:start position:0% and again we might have to manually edit the<17:49:56.880> inbound<17:49:57.240> and<17:49:57.416> outbound<17:49:57.776> ports 17:49:59.926 --> 17:49:59.936 align:start position:0% the inbound and outbound ports 17:49:59.936 --> 17:50:02.626 align:start position:0% the inbound and outbound ports to<17:50:00.540> allow<17:50:00.840> for<17:50:01.200> instance<17:50:01.500> a<17:50:01.980> software<17:50:02.400> program 17:50:02.626 --> 17:50:02.636 align:start position:0% to allow for instance a software program 17:50:02.636 --> 17:50:04.606 align:start position:0% to allow for instance a software program that<17:50:03.000> uses<17:50:03.240> its<17:50:03.540> own<17:50:03.596> port<17:50:03.776> to<17:50:04.256> get<17:50:04.320> out<17:50:04.436> and 17:50:04.606 --> 17:50:04.616 align:start position:0% that uses its own port to get out and 17:50:04.616 --> 17:50:06.586 align:start position:0% that uses its own port to get out and get<17:50:04.740> updates<17:50:05.160> one<17:50:05.820> of<17:50:06.000> that<17:50:06.116> software<17:50:06.480> that 17:50:06.586 --> 17:50:06.596 align:start position:0% get updates one of that software that 17:50:06.596 --> 17:50:07.550 align:start position:0% get updates one of that software that might<17:50:06.720> need<17:50:06.840> to<17:50:06.900> go<17:50:07.020> out<17:50:07.080> and<17:50:07.136> get<17:50:07.256> updates 17:50:07.550 --> 17:50:07.560 align:start position:0% might need to go out and get updates 17:50:07.560 --> 17:50:09.710 align:start position:0% might need to go out and get updates would<17:50:07.860> be<17:50:07.980> our<17:50:08.340> antivirus<17:50:09.000> software<17:50:09.360> which<17:50:09.596> is 17:50:09.710 --> 17:50:09.720 align:start position:0% would be our antivirus software which is 17:50:09.720 --> 17:50:11.510 align:start position:0% would be our antivirus software which is what<17:50:09.840> we<17:50:09.956> talked<17:50:10.256> about<17:50:10.320> this<17:50:10.916> is<17:50:11.096> software 17:50:11.510 --> 17:50:11.520 align:start position:0% what we talked about this is software 17:50:11.520 --> 17:50:14.330 align:start position:0% what we talked about this is software that<17:50:11.820> does<17:50:12.000> not<17:50:12.180> it<17:50:12.596> can<17:50:13.080> prevent 17:50:14.330 --> 17:50:14.340 align:start position:0% that does not it can prevent 17:50:14.340 --> 17:50:17.510 align:start position:0% that does not it can prevent an<17:50:14.756> attack<17:50:15.000> but<17:50:15.900> it<17:50:16.740> can<17:50:16.860> sort<17:50:17.040> of<17:50:17.160> take<17:50:17.340> over 17:50:17.510 --> 17:50:17.520 align:start position:0% an attack but it can sort of take over 17:50:17.520 --> 17:50:20.990 align:start position:0% an attack but it can sort of take over from<17:50:17.880> where<17:50:18.060> the<17:50:18.240> firewall<17:50:18.860> stops<17:50:19.860> whereas<17:50:20.756> a 17:50:20.990 --> 17:50:21.000 align:start position:0% from where the firewall stops whereas a 17:50:21.000 --> 17:50:22.730 align:start position:0% from where the firewall stops whereas a firewall<17:50:21.360> can't<17:50:21.660> stop<17:50:22.020> it<17:50:22.200> once<17:50:22.500> it's<17:50:22.560> already 17:50:22.730 --> 17:50:22.740 align:start position:0% firewall can't stop it once it's already 17:50:22.740 --> 17:50:24.890 align:start position:0% firewall can't stop it once it's already started<17:50:23.160> an<17:50:23.520> antivirus<17:50:24.060> software<17:50:24.596> program 17:50:24.890 --> 17:50:24.900 align:start position:0% started an antivirus software program 17:50:24.900 --> 17:50:27.470 align:start position:0% started an antivirus software program can<17:50:25.256> go<17:50:25.436> a<17:50:25.616> little<17:50:25.740> more<17:50:25.916> in<17:50:26.096> depth<17:50:26.456> it<17:50:27.116> has<17:50:27.296> to 17:50:27.470 --> 17:50:27.480 align:start position:0% can go a little more in depth it has to 17:50:27.480 --> 17:50:30.766 align:start position:0% can go a little more in depth it has to be<17:50:27.596> kept<17:50:27.956> up<17:50:28.200> to<17:50:28.380> date 17:50:30.766 --> 17:50:30.776 align:start position:0% 17:50:30.776 --> 17:50:33.650 align:start position:0% and<17:50:31.436> it<17:50:31.680> might<17:50:31.916> not<17:50:32.220> necessarily<17:50:33.180> be<17:50:33.360> able<17:50:33.540> to 17:50:33.650 --> 17:50:33.660 align:start position:0% and it might not necessarily be able to 17:50:33.660 --> 17:50:35.926 align:start position:0% and it might not necessarily be able to remove<17:50:33.776> the<17:50:34.080> virus<17:50:34.436> but<17:50:34.796> it<17:50:35.160> will<17:50:35.400> put<17:50:35.700> the 17:50:35.926 --> 17:50:35.936 align:start position:0% remove the virus but it will put the 17:50:35.936 --> 17:50:38.210 align:start position:0% remove the virus but it will put the virus<17:50:36.360> and<17:50:36.776> the<17:50:36.956> files<17:50:37.256> that<17:50:37.436> it<17:50:37.560> has<17:50:37.740> infected 17:50:38.210 --> 17:50:38.220 align:start position:0% virus and the files that it has infected 17:50:38.220 --> 17:50:41.030 align:start position:0% virus and the files that it has infected into<17:50:39.060> a<17:50:39.360> quarantine 17:50:41.030 --> 17:50:41.040 align:start position:0% into a quarantine 17:50:41.040 --> 17:50:42.946 align:start position:0% into a quarantine so<17:50:41.520> that's<17:50:41.820> really<17:50:42.060> what's<17:50:42.296> important<17:50:42.720> about 17:50:42.946 --> 17:50:42.956 align:start position:0% so that's really what's important about 17:50:42.956 --> 17:50:44.746 align:start position:0% so that's really what's important about it<17:50:43.256> and<17:50:43.616> if<17:50:43.796> you've<17:50:44.040> been<17:50:44.160> working<17:50:44.400> on<17:50:44.580> a 17:50:44.746 --> 17:50:44.756 align:start position:0% it and if you've been working on a 17:50:44.756 --> 17:50:46.370 align:start position:0% it and if you've been working on a computer<17:50:44.880> at<17:50:45.180> all<17:50:45.296> in<17:50:45.416> the<17:50:45.596> past<17:50:45.660> 15<17:50:45.900> or<17:50:46.200> 20 17:50:46.370 --> 17:50:46.380 align:start position:0% computer at all in the past 15 or 20 17:50:46.380 --> 17:50:48.230 align:start position:0% computer at all in the past 15 or 20 years<17:50:46.616> you've<17:50:47.276> definitely<17:50:47.456> had<17:50:47.636> to<17:50:47.756> use<17:50:48.000> this 17:50:48.230 --> 17:50:48.240 align:start position:0% years you've definitely had to use this 17:50:48.240 --> 17:50:53.746 align:start position:0% years you've definitely had to use this and<17:50:48.480> nowadays<17:50:48.956> actually<17:50:49.200> Windows<17:50:49.796> requires 17:50:53.746 --> 17:50:53.756 align:start position:0% 17:50:53.756 --> 17:50:56.570 align:start position:0% that<17:50:54.360> you<17:50:54.660> have<17:50:54.956> a<17:50:55.320> virus<17:50:55.680> scan<17:50:55.860> on<17:50:56.096> or<17:50:56.276> it<17:50:56.456> will 17:50:56.570 --> 17:50:56.580 align:start position:0% that you have a virus scan on or it will 17:50:56.580 --> 17:50:58.126 align:start position:0% that you have a virus scan on or it will actually<17:50:56.756> bother<17:50:57.180> you<17:50:57.360> in<17:50:57.540> the<17:50:57.660> notification 17:50:58.126 --> 17:50:58.136 align:start position:0% actually bother you in the notification 17:50:58.136 --> 17:51:00.170 align:start position:0% actually bother you in the notification center<17:50:58.380> quite<17:50:58.860> often 17:51:00.170 --> 17:51:00.180 align:start position:0% center quite often 17:51:00.180 --> 17:51:01.906 align:start position:0% center quite often so<17:51:00.776> now<17:51:00.956> that<17:51:01.136> we've<17:51:01.320> talked<17:51:01.560> about<17:51:01.616> this 17:51:01.906 --> 17:51:01.916 align:start position:0% so now that we've talked about this 17:51:01.916 --> 17:51:04.906 align:start position:0% so now that we've talked about this let's<17:51:02.276> end<17:51:02.580> by<17:51:02.880> talking<17:51:03.116> about<17:51:03.416> how<17:51:04.080> we<17:51:04.256> can 17:51:04.906 --> 17:51:04.916 align:start position:0% let's end by talking about how we can 17:51:04.916 --> 17:51:07.126 align:start position:0% let's end by talking about how we can protect<17:51:05.520> our<17:51:05.636> data<17:51:06.000> in<17:51:06.240> a<17:51:06.360> very<17:51:06.480> raw<17:51:06.840> sense 17:51:07.126 --> 17:51:07.136 align:start position:0% protect our data in a very raw sense 17:51:07.136 --> 17:51:12.750 align:start position:0% protect our data in a very raw sense called<17:51:07.500> encryption<17:51:08.040> and<17:51:08.276> cryptography 17:51:12.750 --> 17:51:12.760 align:start position:0% 17:51:12.760 --> 17:51:32.710 align:start position:0% [Music] 17:51:32.710 --> 17:51:32.720 align:start position:0% 17:51:32.720 --> 17:51:35.990 align:start position:0% network<17:51:33.720> security<17:51:34.580> encryption<17:51:35.580> and 17:51:35.990 --> 17:51:36.000 align:start position:0% network security encryption and 17:51:36.000 --> 17:51:38.446 align:start position:0% network security encryption and cryptography<17:51:36.840> 101 17:51:38.446 --> 17:51:38.456 align:start position:0% cryptography 101 17:51:38.456 --> 17:51:41.150 align:start position:0% cryptography 101 so<17:51:38.936> to<17:51:39.180> round<17:51:39.360> up<17:51:39.596> our<17:51:40.136> discussion<17:51:40.680> of<17:51:40.916> network 17:51:41.150 --> 17:51:41.160 align:start position:0% so to round up our discussion of network 17:51:41.160 --> 17:51:43.246 align:start position:0% so to round up our discussion of network security<17:51:41.520> I<17:51:42.296> want<17:51:42.416> to<17:51:42.596> talk<17:51:42.660> about<17:51:42.840> the<17:51:43.136> way 17:51:43.246 --> 17:51:43.256 align:start position:0% security I want to talk about the way 17:51:43.256 --> 17:51:46.126 align:start position:0% security I want to talk about the way that<17:51:43.500> we<17:51:43.740> secure<17:51:44.096> data<17:51:44.636> at<17:51:45.060> the<17:51:45.180> source<17:51:45.596> and 17:51:46.126 --> 17:51:46.136 align:start position:0% that we secure data at the source and 17:51:46.136 --> 17:51:48.890 align:start position:0% that we secure data at the source and this<17:51:46.320> gets<17:51:46.616> to<17:51:46.740> basically<17:51:47.360> encoding<17:51:48.360> the<17:51:48.660> data 17:51:48.890 --> 17:51:48.900 align:start position:0% this gets to basically encoding the data 17:51:48.900 --> 17:51:52.070 align:start position:0% this gets to basically encoding the data that<17:51:49.020> we<17:51:49.200> send<17:51:49.380> so<17:51:49.916> even<17:51:50.220> if<17:51:50.456> it's<17:51:50.700> captured<17:51:51.296> or 17:51:52.070 --> 17:51:52.080 align:start position:0% that we send so even if it's captured or 17:51:52.080 --> 17:51:54.830 align:start position:0% that we send so even if it's captured or sniffed<17:51:52.616> we<17:51:53.276> can't<17:51:53.580> allow<17:51:54.060> the<17:51:54.296> hackers<17:51:54.660> to 17:51:54.830 --> 17:51:54.840 align:start position:0% sniffed we can't allow the hackers to 17:51:54.840 --> 17:51:56.086 align:start position:0% sniffed we can't allow the hackers to figure<17:51:55.020> out<17:51:55.200> what<17:51:55.436> it<17:51:55.560> is<17:51:55.680> that<17:51:55.860> we<17:51:55.980> were 17:51:56.086 --> 17:51:56.096 align:start position:0% figure out what it is that we were 17:51:56.096 --> 17:51:58.126 align:start position:0% figure out what it is that we were sending<17:51:56.400> in<17:51:56.580> the<17:51:56.756> first<17:51:56.880> place<17:51:57.116> and<17:51:57.776> so<17:51:57.956> this 17:51:58.126 --> 17:51:58.136 align:start position:0% sending in the first place and so this 17:51:58.136 --> 17:52:00.230 align:start position:0% sending in the first place and so this gets<17:51:58.436> to<17:51:58.560> encryption<17:51:58.980> and<17:51:59.096> cryptography<17:51:59.756> just 17:52:00.230 --> 17:52:00.240 align:start position:0% gets to encryption and cryptography just 17:52:00.240 --> 17:52:03.766 align:start position:0% gets to encryption and cryptography just like<17:52:00.416> code<17:52:00.840> breaking<17:52:01.436> from<17:52:02.220> World<17:52:02.700> War<17:52:02.936> II<17:52:03.360> or 17:52:03.766 --> 17:52:03.776 align:start position:0% like code breaking from World War II or 17:52:03.776 --> 17:52:06.406 align:start position:0% like code breaking from World War II or from<17:52:04.500> our<17:52:04.980> military<17:52:05.276> when<17:52:05.936> they<17:52:06.116> would<17:52:06.240> send 17:52:06.406 --> 17:52:06.416 align:start position:0% from our military when they would send 17:52:06.416 --> 17:52:08.390 align:start position:0% from our military when they would send encrypted<17:52:06.956> messages 17:52:08.390 --> 17:52:08.400 align:start position:0% encrypted messages 17:52:08.400 --> 17:52:11.030 align:start position:0% encrypted messages and<17:52:09.060> because<17:52:09.240> this<17:52:09.660> is<17:52:09.776> a<17:52:10.080> pretty<17:52:10.256> in-depth 17:52:11.030 --> 17:52:11.040 align:start position:0% and because this is a pretty in-depth 17:52:11.040 --> 17:52:12.586 align:start position:0% and because this is a pretty in-depth topic<17:52:11.456> we're<17:52:11.700> only<17:52:11.880> going<17:52:12.060> to<17:52:12.116> cover<17:52:12.296> this 17:52:12.586 --> 17:52:12.596 align:start position:0% topic we're only going to cover this 17:52:12.596 --> 17:52:14.690 align:start position:0% topic we're only going to cover this broadly<17:52:13.320> so<17:52:13.916> first<17:52:14.096> we're<17:52:14.340> going<17:52:14.456> to<17:52:14.520> Define 17:52:14.690 --> 17:52:14.700 align:start position:0% broadly so first we're going to Define 17:52:14.700 --> 17:52:17.266 align:start position:0% broadly so first we're going to Define and<17:52:15.060> discuss<17:52:15.416> cryptography 17:52:17.266 --> 17:52:17.276 align:start position:0% and discuss cryptography 17:52:17.276 --> 17:52:18.710 align:start position:0% and discuss cryptography and<17:52:17.756> then<17:52:17.880> we're<17:52:18.060> going<17:52:18.180> to<17:52:18.180> Define<17:52:18.416> and 17:52:18.710 --> 17:52:18.720 align:start position:0% and then we're going to Define and 17:52:18.720 --> 17:52:21.106 align:start position:0% and then we're going to Define and discuss<17:52:19.080> encryption<17:52:19.980> including<17:52:20.880> the 17:52:21.106 --> 17:52:21.116 align:start position:0% discuss encryption including the 17:52:21.116 --> 17:52:22.850 align:start position:0% discuss encryption including the difference<17:52:21.240> between<17:52:21.596> plain<17:52:22.200> text<17:52:22.436> and 17:52:22.850 --> 17:52:22.860 align:start position:0% difference between plain text and 17:52:22.860 --> 17:52:26.330 align:start position:0% difference between plain text and ciphertext<17:52:23.520> one<17:52:24.296> being<17:52:24.680> the<17:52:25.680> way<17:52:25.860> that<17:52:26.096> text 17:52:26.330 --> 17:52:26.340 align:start position:0% ciphertext one being the way that text 17:52:26.340 --> 17:52:28.730 align:start position:0% ciphertext one being the way that text is<17:52:26.636> sent<17:52:26.820> if<17:52:27.240> we<17:52:27.416> don't<17:52:27.660> add<17:52:28.020> any<17:52:28.200> encryption 17:52:28.730 --> 17:52:28.740 align:start position:0% is sent if we don't add any encryption 17:52:28.740 --> 17:52:30.586 align:start position:0% is sent if we don't add any encryption and<17:52:29.220> the<17:52:29.400> other<17:52:29.520> one<17:52:29.700> if<17:52:29.880> we<17:52:30.060> do<17:52:30.240> add 17:52:30.586 --> 17:52:30.596 align:start position:0% and the other one if we do add 17:52:30.596 --> 17:52:33.406 align:start position:0% and the other one if we do add encryption<17:52:31.136> and<17:52:31.980> then<17:52:32.096> public<17:52:32.580> and<17:52:32.936> private 17:52:33.406 --> 17:52:33.416 align:start position:0% encryption and then public and private 17:52:33.416 --> 17:52:36.710 align:start position:0% encryption and then public and private Keys<17:52:33.840> sort<17:52:34.616> of<17:52:34.680> like<17:52:34.860> decoder<17:52:35.580> rings<17:52:35.880> for<17:52:36.540> how 17:52:36.710 --> 17:52:36.720 align:start position:0% Keys sort of like decoder rings for how 17:52:36.720 --> 17:52:39.286 align:start position:0% Keys sort of like decoder rings for how we<17:52:37.020> can<17:52:37.136> read<17:52:37.380> the<17:52:37.616> ciphertext<17:52:38.276> the<17:52:39.116> public 17:52:39.286 --> 17:52:39.296 align:start position:0% we can read the ciphertext the public 17:52:39.296 --> 17:52:42.050 align:start position:0% we can read the ciphertext the public and<17:52:39.540> private<17:52:39.900> part<17:52:40.080> comes<17:52:40.616> about<17:52:40.860> in<17:52:41.700> the<17:52:41.820> way 17:52:42.050 --> 17:52:42.060 align:start position:0% and private part comes about in the way 17:52:42.060 --> 17:52:45.126 align:start position:0% and private part comes about in the way that<17:52:42.416> we<17:52:42.900> have<17:52:43.740> the<17:52:44.040> sender<17:52:44.456> and<17:52:44.580> the<17:52:44.756> receiver 17:52:45.126 --> 17:52:45.136 align:start position:0% that we have the sender and the receiver 17:52:45.136 --> 17:52:48.890 align:start position:0% that we have the sender and the receiver decode<17:52:46.136> and<17:52:46.436> encrypt<17:52:46.980> certain<17:52:47.276> messages 17:52:48.890 --> 17:52:48.900 align:start position:0% decode and encrypt certain messages 17:52:48.900 --> 17:52:51.650 align:start position:0% decode and encrypt certain messages finally<17:52:49.680> we'll<17:52:50.096> identify<17:52:50.636> examples<17:52:51.240> of<17:52:51.480> both 17:52:51.650 --> 17:52:51.660 align:start position:0% finally we'll identify examples of both 17:52:51.660 --> 17:52:54.370 align:start position:0% finally we'll identify examples of both and<17:52:51.900> how<17:52:52.136> they<17:52:52.320> work<17:52:52.560> now<17:52:53.220> this<17:52:53.580> entire 17:52:54.370 --> 17:52:54.380 align:start position:0% and how they work now this entire 17:52:54.380 --> 17:52:56.870 align:start position:0% and how they work now this entire subject<17:52:55.380> gets<17:52:55.860> a<17:52:55.916> lot<17:52:56.040> more<17:52:56.220> in<17:52:56.400> depth<17:52:56.636> if<17:52:56.756> you 17:52:56.870 --> 17:52:56.880 align:start position:0% subject gets a lot more in depth if you 17:52:56.880 --> 17:52:58.850 align:start position:0% subject gets a lot more in depth if you go<17:52:57.060> into<17:52:57.180> Security<17:52:57.540> Plus<17:52:57.956> and<17:52:58.320> the<17:52:58.436> CompTIA 17:52:58.850 --> 17:52:58.860 align:start position:0% go into Security Plus and the CompTIA 17:52:58.860 --> 17:53:01.070 align:start position:0% go into Security Plus and the CompTIA Security<17:52:59.096> Plus<17:52:59.456> certification<17:53:00.116> so<17:53:00.900> here 17:53:01.070 --> 17:53:01.080 align:start position:0% Security Plus certification so here 17:53:01.080 --> 17:53:02.446 align:start position:0% Security Plus certification so here we're<17:53:01.256> just<17:53:01.436> covering<17:53:01.740> this<17:53:01.916> in<17:53:02.096> a<17:53:02.220> sort<17:53:02.340> of 17:53:02.446 --> 17:53:02.456 align:start position:0% we're just covering this in a sort of 17:53:02.456 --> 17:53:04.850 align:start position:0% we're just covering this in a sort of very<17:53:02.636> broad<17:53:03.060> sense<17:53:03.416> there<17:53:04.020> are<17:53:04.200> people<17:53:04.256> whose 17:53:04.850 --> 17:53:04.860 align:start position:0% very broad sense there are people whose 17:53:04.860 --> 17:53:07.550 align:start position:0% very broad sense there are people whose entire<17:53:05.276> jobs<17:53:05.520> it<17:53:05.820> is<17:53:06.000> to<17:53:06.296> Simply<17:53:06.596> deal<17:53:06.900> with 17:53:07.550 --> 17:53:07.560 align:start position:0% entire jobs it is to Simply deal with 17:53:07.560 --> 17:53:09.830 align:start position:0% entire jobs it is to Simply deal with this<17:53:07.980> aspect<17:53:08.456> of<17:53:08.820> networking 17:53:09.830 --> 17:53:09.840 align:start position:0% this aspect of networking 17:53:09.840 --> 17:53:12.766 align:start position:0% this aspect of networking so<17:53:10.320> in<17:53:10.740> a<17:53:10.916> very<17:53:11.040> general<17:53:11.340> sense<17:53:11.776> cryptography 17:53:12.766 --> 17:53:12.776 align:start position:0% so in a very general sense cryptography 17:53:12.776 --> 17:53:15.310 align:start position:0% so in a very general sense cryptography is<17:53:13.080> the<17:53:13.380> practice<17:53:13.680> of<17:53:14.276> securing<17:53:14.756> information 17:53:15.310 --> 17:53:15.320 align:start position:0% is the practice of securing information 17:53:15.320 --> 17:53:18.830 align:start position:0% is the practice of securing information using<17:53:16.320> codes<17:53:16.680> in<17:53:17.400> order<17:53:17.520> to<17:53:17.756> keep<17:53:17.936> adversaries 17:53:18.830 --> 17:53:18.840 align:start position:0% using codes in order to keep adversaries 17:53:18.840 --> 17:53:20.746 align:start position:0% using codes in order to keep adversaries or<17:53:19.080> hackers<17:53:19.500> or<17:53:19.740> outside<17:53:19.916> folks<17:53:20.520> from 17:53:20.746 --> 17:53:20.756 align:start position:0% or hackers or outside folks from 17:53:20.756 --> 17:53:23.470 align:start position:0% or hackers or outside folks from understanding<17:53:21.296> it<17:53:21.480> now<17:53:22.020> the<17:53:22.200> word<17:53:22.436> adversary 17:53:23.470 --> 17:53:23.480 align:start position:0% understanding it now the word adversary 17:53:23.480 --> 17:53:26.390 align:start position:0% understanding it now the word adversary generally<17:53:24.480> means<17:53:24.900> an<17:53:25.200> enemy<17:53:25.616> or<17:53:25.796> an<17:53:25.980> opponent 17:53:26.390 --> 17:53:26.400 align:start position:0% generally means an enemy or an opponent 17:53:26.400 --> 17:53:28.426 align:start position:0% generally means an enemy or an opponent in<17:53:27.116> this<17:53:27.180> case<17:53:27.360> it<17:53:27.596> just<17:53:27.720> means<17:53:27.956> someone<17:53:28.200> who 17:53:28.426 --> 17:53:28.436 align:start position:0% in this case it just means someone who 17:53:28.436 --> 17:53:30.170 align:start position:0% in this case it just means someone who would<17:53:28.616> want<17:53:28.860> to<17:53:28.980> intercept<17:53:29.580> the<17:53:30.000> information 17:53:30.170 --> 17:53:30.180 align:start position:0% would want to intercept the information 17:53:30.180 --> 17:53:32.810 align:start position:0% would want to intercept the information you're<17:53:30.776> sending<17:53:31.200> it's<17:53:31.796> very<17:53:32.040> likely<17:53:32.456> that 17:53:32.810 --> 17:53:32.820 align:start position:0% you're sending it's very likely that 17:53:32.820 --> 17:53:34.970 align:start position:0% you're sending it's very likely that this<17:53:33.060> adversary<17:53:33.660> is<17:53:34.020> your<17:53:34.616> enemy 17:53:34.970 --> 17:53:34.980 align:start position:0% this adversary is your enemy 17:53:34.980 --> 17:53:37.490 align:start position:0% this adversary is your enemy quote-unquote<17:53:35.700> such<17:53:36.240> as<17:53:36.416> a<17:53:36.660> computer<17:53:36.900> hacker 17:53:37.490 --> 17:53:37.500 align:start position:0% quote-unquote such as a computer hacker 17:53:37.500 --> 17:53:40.730 align:start position:0% quote-unquote such as a computer hacker and<17:53:38.340> although<17:53:39.296> cryptography<17:53:40.136> is<17:53:40.380> not<17:53:40.616> only 17:53:40.730 --> 17:53:40.740 align:start position:0% and although cryptography is not only 17:53:40.740 --> 17:53:44.390 align:start position:0% and although cryptography is not only used<17:53:41.220> in<17:53:41.756> Computing<17:53:42.360> in<17:53:43.256> fact<17:53:43.436> it's<17:53:43.860> been<17:53:44.220> used 17:53:44.390 --> 17:53:44.400 align:start position:0% used in Computing in fact it's been used 17:53:44.400 --> 17:53:45.650 align:start position:0% used in Computing in fact it's been used throughout<17:53:44.756> the<17:53:44.880> world<17:53:45.060> even<17:53:45.296> in<17:53:45.480> the<17:53:45.540> United 17:53:45.650 --> 17:53:45.660 align:start position:0% throughout the world even in the United 17:53:45.660 --> 17:53:48.650 align:start position:0% throughout the world even in the United States<17:53:45.956> and<17:53:46.380> Military<17:53:46.980> Etc<17:53:47.160> it's<17:53:48.000> used<17:53:48.240> quite 17:53:48.650 --> 17:53:48.660 align:start position:0% States and Military Etc it's used quite 17:53:48.660 --> 17:53:51.586 align:start position:0% States and Military Etc it's used quite a<17:53:48.840> bit<17:53:49.020> here<17:53:49.560> in<17:53:49.860> networking<17:53:50.340> and<17:53:50.820> it's<17:53:50.936> used<17:53:51.180> a 17:53:51.586 --> 17:53:51.596 align:start position:0% a bit here in networking and it's used a 17:53:51.596 --> 17:53:54.710 align:start position:0% a bit here in networking and it's used a lot<17:53:51.720> in<17:53:52.080> how<17:53:52.256> we<17:53:52.436> package<17:53:52.860> data<17:53:53.340> into<17:53:53.820> packets 17:53:54.710 --> 17:53:54.720 align:start position:0% lot in how we package data into packets 17:53:54.720 --> 17:53:57.406 align:start position:0% lot in how we package data into packets so<17:53:55.320> cryptography<17:53:56.220> simply<17:53:56.580> means<17:53:56.880> writing 17:53:57.406 --> 17:53:57.416 align:start position:0% so cryptography simply means writing 17:53:57.416 --> 17:53:59.990 align:start position:0% so cryptography simply means writing speaking<17:53:57.956> communicating<17:53:58.560> in<17:53:59.040> code<17:53:59.276> this 17:53:59.990 --> 17:54:00.000 align:start position:0% speaking communicating in code this 17:54:00.000 --> 17:54:01.550 align:start position:0% speaking communicating in code this practice<17:54:00.240> dates<17:54:00.720> back<17:54:00.900> to<17:54:01.020> the<17:54:01.200> time<17:54:01.320> of 17:54:01.550 --> 17:54:01.560 align:start position:0% practice dates back to the time of 17:54:01.560 --> 17:54:03.586 align:start position:0% practice dates back to the time of Julius<17:54:01.916> Caesar<17:54:02.400> and<17:54:02.820> quite<17:54:03.116> possibly<17:54:03.416> even 17:54:03.586 --> 17:54:03.596 align:start position:0% Julius Caesar and quite possibly even 17:54:03.596 --> 17:54:05.690 align:start position:0% Julius Caesar and quite possibly even earlier<17:54:04.020> than<17:54:04.200> that<17:54:04.380> Caesar<17:54:05.220> used<17:54:05.400> something 17:54:05.690 --> 17:54:05.700 align:start position:0% earlier than that Caesar used something 17:54:05.700 --> 17:54:08.746 align:start position:0% earlier than that Caesar used something that's<17:54:06.060> referred<17:54:06.480> to<17:54:06.596> as<17:54:06.956> the<17:54:07.796> Caesar<17:54:08.276> Cipher 17:54:08.746 --> 17:54:08.756 align:start position:0% that's referred to as the Caesar Cipher 17:54:08.756 --> 17:54:10.850 align:start position:0% that's referred to as the Caesar Cipher which<17:54:09.000> we'll<17:54:09.116> look<17:54:09.240> at<17:54:09.360> in<17:54:09.480> just<17:54:09.660> a<17:54:09.840> second<17:54:10.020> a 17:54:10.850 --> 17:54:10.860 align:start position:0% which we'll look at in just a second a 17:54:10.860 --> 17:54:13.606 align:start position:0% which we'll look at in just a second a cipher<17:54:11.340> is<17:54:11.936> a<17:54:12.180> way<17:54:12.296> to<17:54:12.596> encode<17:54:13.020> and<17:54:13.200> decode 17:54:13.606 --> 17:54:13.616 align:start position:0% cipher is a way to encode and decode 17:54:13.616 --> 17:54:16.070 align:start position:0% cipher is a way to encode and decode data<17:54:14.096> so<17:54:14.456> Caesar<17:54:14.936> used<17:54:15.116> it<17:54:15.360> to<17:54:15.596> send<17:54:15.776> messages 17:54:16.070 --> 17:54:16.080 align:start position:0% data so Caesar used it to send messages 17:54:16.080 --> 17:54:17.810 align:start position:0% data so Caesar used it to send messages and<17:54:16.500> commands<17:54:16.860> that<17:54:17.096> needed<17:54:17.400> to<17:54:17.520> remain 17:54:17.810 --> 17:54:17.820 align:start position:0% and commands that needed to remain 17:54:17.820 --> 17:54:20.390 align:start position:0% and commands that needed to remain secret<17:54:18.320> we<17:54:19.320> were<17:54:19.500> also<17:54:19.740> used<17:54:19.860> it<17:54:20.160> in<17:54:20.276> the 17:54:20.390 --> 17:54:20.400 align:start position:0% secret we were also used it in the 17:54:20.400 --> 17:54:22.850 align:start position:0% secret we were also used it in the United<17:54:20.520> States<17:54:20.820> during<17:54:21.240> World<17:54:21.540> War<17:54:21.720> II<17:54:22.080> uh<17:54:22.680> the 17:54:22.850 --> 17:54:22.860 align:start position:0% United States during World War II uh the 17:54:22.860 --> 17:54:24.230 align:start position:0% United States during World War II uh the Japanese<17:54:23.040> used<17:54:23.456> there<17:54:23.700> have<17:54:23.880> been<17:54:23.936> a<17:54:24.180> whole 17:54:24.230 --> 17:54:24.240 align:start position:0% Japanese used there have been a whole 17:54:24.240 --> 17:54:26.446 align:start position:0% Japanese used there have been a whole bunch<17:54:24.360> of<17:54:24.480> movies<17:54:24.660> about<17:54:25.020> this<17:54:25.456> cryptography 17:54:26.446 --> 17:54:26.456 align:start position:0% bunch of movies about this cryptography 17:54:26.456 --> 17:54:28.070 align:start position:0% bunch of movies about this cryptography and<17:54:26.580> ciphers<17:54:27.000> play<17:54:27.240> a<17:54:27.480> large<17:54:27.660> role<17:54:28.020> in 17:54:28.070 --> 17:54:28.080 align:start position:0% and ciphers play a large role in 17:54:28.080 --> 17:54:29.390 align:start position:0% and ciphers play a large role in communication<17:54:28.500> especially<17:54:29.040> when<17:54:29.096> we<17:54:29.276> don't 17:54:29.390 --> 17:54:29.400 align:start position:0% communication especially when we don't 17:54:29.400 --> 17:54:30.530 align:start position:0% communication especially when we don't want<17:54:29.520> our<17:54:29.700> enemies<17:54:30.000> to<17:54:30.180> know<17:54:30.296> what<17:54:30.416> we're 17:54:30.530 --> 17:54:30.540 align:start position:0% want our enemies to know what we're 17:54:30.540 --> 17:54:31.670 align:start position:0% want our enemies to know what we're talking<17:54:30.720> about 17:54:31.670 --> 17:54:31.680 align:start position:0% talking about 17:54:31.680 --> 17:54:34.126 align:start position:0% talking about this<17:54:32.276> was<17:54:32.456> true<17:54:32.756> all<17:54:33.416> over<17:54:33.540> the<17:54:33.720> world<17:54:33.840> people 17:54:34.126 --> 17:54:34.136 align:start position:0% this was true all over the world people 17:54:34.136 --> 17:54:36.050 align:start position:0% this was true all over the world people began<17:54:34.500> speaking<17:54:34.916> over<17:54:35.040> the<17:54:35.220> radio<17:54:35.340> writing<17:54:35.936> in 17:54:36.050 --> 17:54:36.060 align:start position:0% began speaking over the radio writing in 17:54:36.060 --> 17:54:37.190 align:start position:0% began speaking over the radio writing in codes<17:54:36.240> in<17:54:36.540> order<17:54:36.660> to<17:54:36.840> keep<17:54:36.956> information 17:54:37.190 --> 17:54:37.200 align:start position:0% codes in order to keep information 17:54:37.200 --> 17:54:40.190 align:start position:0% codes in order to keep information secure<17:54:37.916> so<17:54:38.756> a<17:54:39.296> language<17:54:39.480> like<17:54:39.840> the<17:54:40.080> English 17:54:40.190 --> 17:54:40.200 align:start position:0% secure so a language like the English 17:54:40.200 --> 17:54:43.730 align:start position:0% secure so a language like the English language<17:54:40.580> might<17:54:41.580> be<17:54:41.820> a<17:54:42.296> form<17:54:42.660> of<17:54:42.900> cryptography 17:54:43.730 --> 17:54:43.740 align:start position:0% language might be a form of cryptography 17:54:43.740 --> 17:54:46.550 align:start position:0% language might be a form of cryptography to<17:54:44.040> someone<17:54:44.276> who<17:54:45.000> speaks<17:54:45.480> Spanish<17:54:45.720> if<17:54:46.380> they 17:54:46.550 --> 17:54:46.560 align:start position:0% to someone who speaks Spanish if they 17:54:46.560 --> 17:54:48.470 align:start position:0% to someone who speaks Spanish if they don't<17:54:46.740> understand<17:54:46.916> the<17:54:47.456> language<17:54:47.636> However 17:54:48.470 --> 17:54:48.480 align:start position:0% don't understand the language However 17:54:48.480 --> 17:54:51.170 align:start position:0% don't understand the language However the<17:54:48.956> fact<17:54:49.080> that<17:54:49.320> there<17:54:49.560> is<17:54:49.740> a<17:54:50.096> dictionary<17:54:50.820> out 17:54:51.170 --> 17:54:51.180 align:start position:0% the fact that there is a dictionary out 17:54:51.180 --> 17:54:52.786 align:start position:0% the fact that there is a dictionary out there<17:54:51.296> that<17:54:51.720> translates<17:54:52.200> everything<17:54:52.500> for 17:54:52.786 --> 17:54:52.796 align:start position:0% there that translates everything for 17:54:52.796 --> 17:54:54.710 align:start position:0% there that translates everything for them<17:54:53.040> means<17:54:53.456> that<17:54:53.580> the<17:54:53.756> code<17:54:53.936> is<17:54:54.240> pretty<17:54:54.480> easy 17:54:54.710 --> 17:54:54.720 align:start position:0% them means that the code is pretty easy 17:54:54.720 --> 17:54:56.390 align:start position:0% them means that the code is pretty easy to<17:54:54.956> break<17:54:55.136> so<17:54:55.680> what<17:54:55.860> we're<17:54:56.040> really<17:54:56.160> talking 17:54:56.390 --> 17:54:56.400 align:start position:0% to break so what we're really talking 17:54:56.400 --> 17:54:58.190 align:start position:0% to break so what we're really talking about<17:54:56.636> and<17:54:56.936> what<17:54:57.116> the<17:54:57.240> Caesar<17:54:57.540> code<17:54:57.720> did<17:54:57.956> for 17:54:58.190 --> 17:54:58.200 align:start position:0% about and what the Caesar code did for 17:54:58.200 --> 17:55:00.230 align:start position:0% about and what the Caesar code did for instance<17:54:58.500> is<17:54:58.680> replace 17:55:00.230 --> 17:55:00.240 align:start position:0% instance is replace 17:55:00.240 --> 17:55:03.766 align:start position:0% instance is replace um<17:55:00.296> every<17:55:00.900> a<17:55:01.320> went<17:55:02.040> down<17:55:02.340> three<17:55:02.880> numbers<17:55:03.296> and 17:55:03.766 --> 17:55:03.776 align:start position:0% um every a went down three numbers and 17:55:03.776 --> 17:55:06.106 align:start position:0% um every a went down three numbers and replace<17:55:03.956> it<17:55:04.256> with<17:55:04.380> a<17:55:04.616> d<17:55:04.796> so<17:55:05.276> whenever<17:55:05.580> you<17:55:05.936> saw 17:55:06.106 --> 17:55:06.116 align:start position:0% replace it with a d so whenever you saw 17:55:06.116 --> 17:55:08.870 align:start position:0% replace it with a d so whenever you saw for<17:55:06.540> instance<17:55:06.840> uh<17:55:07.560> the<17:55:07.796> word 17:55:08.870 --> 17:55:08.880 align:start position:0% for instance uh the word 17:55:08.880 --> 17:55:10.426 align:start position:0% for instance uh the word Apple 17:55:10.426 --> 17:55:10.436 align:start position:0% Apple 17:55:10.436 --> 17:55:12.766 align:start position:0% Apple we<17:55:11.340> would<17:55:11.636> add 17:55:12.766 --> 17:55:12.776 align:start position:0% we would add 17:55:12.776 --> 17:55:16.010 align:start position:0% we would add plus<17:55:13.380> 3<17:55:13.616> would<17:55:13.916> be<17:55:14.040> our<17:55:14.276> code<17:55:14.520> and<17:55:15.296> so<17:55:15.480> if<17:55:15.840> we 17:55:16.010 --> 17:55:16.020 align:start position:0% plus 3 would be our code and so if we 17:55:16.020 --> 17:55:17.926 align:start position:0% plus 3 would be our code and so if we went<17:55:16.200> down<17:55:16.500> three<17:55:16.860> if<17:55:17.160> we<17:55:17.276> wrote<17:55:17.520> this<17:55:17.756> out 17:55:17.926 --> 17:55:17.936 align:start position:0% went down three if we wrote this out 17:55:17.936 --> 17:55:20.990 align:start position:0% went down three if we wrote this out from<17:55:18.540> a<17:55:18.840> is<17:55:19.436> b<17:55:19.740> c<17:55:19.916> d 17:55:20.990 --> 17:55:21.000 align:start position:0% from a is b c d 17:55:21.000 --> 17:55:25.010 align:start position:0% from a is b c d from<17:55:21.540> p<17:55:21.776> is<17:55:22.256> QRS 17:55:25.010 --> 17:55:25.020 align:start position:0% from p is QRS 17:55:25.020 --> 17:55:30.830 align:start position:0% from p is QRS from<17:55:25.380> L<17:55:25.680> is<17:55:26.040> M<17:55:26.520> N<17:55:26.820> O<17:55:27.296> and<17:55:28.256> from<17:55:28.380> E<17:55:28.680> is<17:55:28.916> fgh<17:55:29.660> so<17:55:30.660> if 17:55:30.830 --> 17:55:30.840 align:start position:0% from L is M N O and from E is fgh so if 17:55:30.840 --> 17:55:32.990 align:start position:0% from L is M N O and from E is fgh so if we<17:55:30.956> were<17:55:31.080> to<17:55:31.200> write<17:55:31.320> Apple<17:55:31.740> in<17:55:32.456> the<17:55:32.636> Caesar 17:55:32.990 --> 17:55:33.000 align:start position:0% we were to write Apple in the Caesar 17:55:33.000 --> 17:55:35.266 align:start position:0% we were to write Apple in the Caesar code<17:55:33.240> this<17:55:33.596> is<17:55:33.660> what<17:55:33.840> it<17:55:33.956> would<17:55:34.080> look<17:55:34.256> like<17:55:34.436> and 17:55:35.266 --> 17:55:35.276 align:start position:0% code this is what it would look like and 17:55:35.276 --> 17:55:37.246 align:start position:0% code this is what it would look like and that's<17:55:35.400> because<17:55:35.636> if<17:55:35.936> we<17:55:36.116> went<17:55:36.360> back<17:55:36.720> three<17:55:36.956> for 17:55:37.246 --> 17:55:37.256 align:start position:0% that's because if we went back three for 17:55:37.256 --> 17:55:39.106 align:start position:0% that's because if we went back three for each<17:55:37.436> of<17:55:37.560> these<17:55:37.680> we<17:55:37.916> would<17:55:38.096> get<17:55:38.340> the<17:55:39.000> word 17:55:39.106 --> 17:55:39.116 align:start position:0% each of these we would get the word 17:55:39.116 --> 17:55:42.350 align:start position:0% each of these we would get the word Apple<17:55:39.480> now<17:55:40.436> there<17:55:40.740> was<17:55:40.860> only<17:55:41.220> one<17:55:41.580> code<17:55:41.936> that 17:55:42.350 --> 17:55:42.360 align:start position:0% Apple now there was only one code that 17:55:42.360 --> 17:55:45.050 align:start position:0% Apple now there was only one code that remained<17:55:42.776> unbreakable<17:55:43.380> in<17:55:43.796> World<17:55:43.980> War<17:55:44.220> II<17:55:44.580> and 17:55:45.050 --> 17:55:45.060 align:start position:0% remained unbreakable in World War II and 17:55:45.060 --> 17:55:47.510 align:start position:0% remained unbreakable in World War II and it<17:55:45.240> was<17:55:45.360> used<17:55:45.660> uh<17:55:46.136> by<17:55:46.436> the<17:55:46.560> US<17:55:46.740> so<17:55:47.160> the<17:55:47.340> Japanese 17:55:47.510 --> 17:55:47.520 align:start position:0% it was used uh by the US so the Japanese 17:55:47.520 --> 17:55:49.370 align:start position:0% it was used uh by the US so the Japanese could<17:55:48.000> not<17:55:48.180> intercept<17:55:48.540> messages<17:55:48.840> that<17:55:49.200> were 17:55:49.370 --> 17:55:49.380 align:start position:0% could not intercept messages that were 17:55:49.380 --> 17:55:51.530 align:start position:0% could not intercept messages that were being<17:55:49.616> sent<17:55:49.916> the<17:55:50.520> US<17:55:50.636> actually<17:55:50.936> Enlisted<17:55:51.416> the 17:55:51.530 --> 17:55:51.540 align:start position:0% being sent the US actually Enlisted the 17:55:51.540 --> 17:55:53.030 align:start position:0% being sent the US actually Enlisted the help<17:55:51.660> this<17:55:51.840> is<17:55:51.956> a<17:55:52.200> really<17:55:52.256> interesting<17:55:52.740> fact 17:55:53.030 --> 17:55:53.040 align:start position:0% help this is a really interesting fact 17:55:53.040 --> 17:55:57.170 align:start position:0% help this is a really interesting fact of<17:55:53.700> Navajo<17:55:54.436> Native<17:55:55.436> Americans<17:55:56.096> in<17:55:56.820> order<17:55:56.936> to 17:55:57.170 --> 17:55:57.180 align:start position:0% of Navajo Native Americans in order to 17:55:57.180 --> 17:55:59.150 align:start position:0% of Navajo Native Americans in order to help<17:55:57.296> them<17:55:57.480> transmit<17:55:58.080> messages<17:55:58.320> and<17:55:58.916> these 17:55:59.150 --> 17:55:59.160 align:start position:0% help them transmit messages and these 17:55:59.160 --> 17:56:01.550 align:start position:0% help them transmit messages and these Navajo<17:55:59.820> code<17:56:00.116> talkers<17:56:00.660> spoke<17:56:01.256> a<17:56:01.380> language 17:56:01.550 --> 17:56:01.560 align:start position:0% Navajo code talkers spoke a language 17:56:01.560 --> 17:56:03.830 align:start position:0% Navajo code talkers spoke a language that<17:56:01.916> was<17:56:02.040> so<17:56:02.220> dead<17:56:02.456> and<17:56:02.936> was<17:56:03.180> only<17:56:03.296> spoken<17:56:03.720> by 17:56:03.830 --> 17:56:03.840 align:start position:0% that was so dead and was only spoken by 17:56:03.840 --> 17:56:06.710 align:start position:0% that was so dead and was only spoken by very<17:56:04.080> few<17:56:04.320> people<17:56:04.616> that<17:56:05.580> every<17:56:06.060> U.S<17:56:06.480> major 17:56:06.710 --> 17:56:06.720 align:start position:0% very few people that every U.S major 17:56:06.720 --> 17:56:09.710 align:start position:0% very few people that every U.S major base<17:56:07.616> had<17:56:08.160> a<17:56:08.340> Navajo<17:56:08.756> code<17:56:08.936> Docker<17:56:09.416> with<17:56:09.596> them 17:56:09.710 --> 17:56:09.720 align:start position:0% base had a Navajo code Docker with them 17:56:09.720 --> 17:56:11.990 align:start position:0% base had a Navajo code Docker with them and<17:56:10.256> they<17:56:10.436> would<17:56:10.560> translate<17:56:10.916> messages<17:56:11.520> and 17:56:11.990 --> 17:56:12.000 align:start position:0% and they would translate messages and 17:56:12.000 --> 17:56:13.786 align:start position:0% and they would translate messages and send<17:56:12.116> them<17:56:12.296> over<17:56:12.480> to<17:56:12.720> each<17:56:12.900> other<17:56:13.080> it<17:56:13.616> was 17:56:13.786 --> 17:56:13.796 align:start position:0% send them over to each other it was 17:56:13.796 --> 17:56:15.530 align:start position:0% send them over to each other it was never<17:56:13.916> cracked<17:56:14.400> by<17:56:14.520> the<17:56:14.756> Japanese<17:56:14.880> there<17:56:15.416> was 17:56:15.530 --> 17:56:15.540 align:start position:0% never cracked by the Japanese there was 17:56:15.540 --> 17:56:19.190 align:start position:0% never cracked by the Japanese there was even<17:56:15.720> a<17:56:16.136> movie<17:56:16.916> about<17:56:17.276> this<17:56:17.700> so<17:56:18.360> this<17:56:18.776> is<17:56:18.956> how 17:56:19.190 --> 17:56:19.200 align:start position:0% even a movie about this so this is how 17:56:19.200 --> 17:56:21.406 align:start position:0% even a movie about this so this is how cryptography<17:56:20.040> worked<17:56:20.456> right<17:56:20.636> if<17:56:20.880> we<17:56:21.060> have<17:56:21.180> a 17:56:21.406 --> 17:56:21.416 align:start position:0% cryptography worked right if we have a 17:56:21.416 --> 17:56:22.606 align:start position:0% cryptography worked right if we have a language<17:56:21.596> that<17:56:21.900> someone<17:56:22.080> doesn't<17:56:22.320> understand 17:56:22.606 --> 17:56:22.616 align:start position:0% language that someone doesn't understand 17:56:22.616 --> 17:56:25.550 align:start position:0% language that someone doesn't understand then<17:56:23.456> that<17:56:23.700> is<17:56:23.880> a<17:56:24.180> form<17:56:24.296> of<17:56:24.480> cryptography<17:56:24.900> fee 17:56:25.550 --> 17:56:25.560 align:start position:0% then that is a form of cryptography fee 17:56:25.560 --> 17:56:27.650 align:start position:0% then that is a form of cryptography fee there's<17:56:25.740> no<17:56:25.980> dictionary<17:56:26.456> in<17:56:27.116> this<17:56:27.240> case<17:56:27.416> of 17:56:27.650 --> 17:56:27.660 align:start position:0% there's no dictionary in this case of 17:56:27.660 --> 17:56:30.230 align:start position:0% there's no dictionary in this case of the<17:56:27.776> Caesar<17:56:28.200> code<17:56:28.380> all<17:56:29.160> right<17:56:29.340> this<17:56:29.820> is<17:56:30.000> what 17:56:30.230 --> 17:56:30.240 align:start position:0% the Caesar code all right this is what 17:56:30.240 --> 17:56:32.330 align:start position:0% the Caesar code all right this is what he<17:56:30.416> did 17:56:32.330 --> 17:56:32.340 align:start position:0% he did 17:56:32.340 --> 17:56:34.550 align:start position:0% he did and<17:56:32.880> uh<17:56:33.116> if<17:56:33.416> we<17:56:33.540> want<17:56:33.720> to<17:56:33.900> look<17:56:34.136> a<17:56:34.320> little<17:56:34.380> bit 17:56:34.550 --> 17:56:34.560 align:start position:0% and uh if we want to look a little bit 17:56:34.560 --> 17:56:36.830 align:start position:0% and uh if we want to look a little bit closer<17:56:34.916> at<17:56:35.040> how<17:56:35.276> that<17:56:35.456> worked<17:56:35.880> we<17:56:36.360> can<17:56:36.480> see<17:56:36.660> the 17:56:36.830 --> 17:56:36.840 align:start position:0% closer at how that worked we can see the 17:56:36.840 --> 17:56:39.946 align:start position:0% closer at how that worked we can see the Caesar<17:56:37.256> Cipher<17:56:37.796> basically<17:56:38.580> every<17:56:39.296> letter<17:56:39.596> in 17:56:39.946 --> 17:56:39.956 align:start position:0% Caesar Cipher basically every letter in 17:56:39.956 --> 17:56:43.550 align:start position:0% Caesar Cipher basically every letter in this<17:56:40.136> case<17:56:40.256> we're<17:56:40.560> going<17:56:40.860> back<17:56:41.400> three 17:56:43.550 --> 17:56:43.560 align:start position:0% this case we're going back three 17:56:43.560 --> 17:56:46.070 align:start position:0% this case we're going back three uh<17:56:44.220> it<17:56:44.340> was<17:56:44.456> in<17:56:44.580> the<17:56:44.756> original<17:56:44.880> text<17:56:45.416> and<17:56:45.900> then 17:56:46.070 --> 17:56:46.080 align:start position:0% uh it was in the original text and then 17:56:46.080 --> 17:56:49.490 align:start position:0% uh it was in the original text and then you<17:56:46.436> would<17:56:46.680> go<17:56:47.220> back<17:56:47.580> and<17:56:48.116> so<17:56:48.240> a<17:56:48.480> became<17:56:48.900> x<17:56:49.200> b 17:56:49.490 --> 17:56:49.500 align:start position:0% you would go back and so a became x b 17:56:49.500 --> 17:56:51.406 align:start position:0% you would go back and so a became x b became<17:56:49.860> Y<17:56:50.040> and<17:56:50.276> so<17:56:50.400> on<17:56:50.520> what<17:56:50.756> we<17:56:50.936> did<17:56:51.116> earlier 17:56:51.406 --> 17:56:51.416 align:start position:0% became Y and so on what we did earlier 17:56:51.416 --> 17:56:53.626 align:start position:0% became Y and so on what we did earlier was<17:56:51.776> actually<17:56:52.020> go<17:56:52.256> forward<17:56:52.560> three<17:56:52.980> so 17:56:53.626 --> 17:56:53.636 align:start position:0% was actually go forward three so 17:56:53.636 --> 17:56:56.690 align:start position:0% was actually go forward three so whatever<17:56:53.820> it<17:56:54.180> was<17:56:54.680> we<17:56:55.680> could<17:56:55.860> figure<17:56:56.096> out<17:56:56.400> what 17:56:56.690 --> 17:56:56.700 align:start position:0% whatever it was we could figure out what 17:56:56.700 --> 17:56:59.570 align:start position:0% whatever it was we could figure out what the<17:56:56.820> code<17:56:57.000> would<17:56:57.296> be<17:56:57.480> simply<17:56:58.200> by<17:56:58.560> minusing<17:56:59.340> or 17:56:59.570 --> 17:56:59.580 align:start position:0% the code would be simply by minusing or 17:56:59.580 --> 17:57:02.210 align:start position:0% the code would be simply by minusing or adding<17:57:00.000> three<17:57:00.240> so<17:57:01.200> for<17:57:01.436> instance<17:57:01.740> if<17:57:01.980> we<17:57:02.096> were 17:57:02.210 --> 17:57:02.220 align:start position:0% adding three so for instance if we were 17:57:02.220 --> 17:57:04.730 align:start position:0% adding three so for instance if we were to<17:57:02.340> write<17:57:02.456> ABC<17:57:03.116> right<17:57:03.596> now<17:57:03.720> in<17:57:04.256> the<17:57:04.380> Caesar 17:57:04.730 --> 17:57:04.740 align:start position:0% to write ABC right now in the Caesar 17:57:04.740 --> 17:57:06.470 align:start position:0% to write ABC right now in the Caesar code<17:57:04.916> with<17:57:05.160> a<17:57:05.276> minus<17:57:05.636> three<17:57:05.756> it<17:57:06.180> would<17:57:06.296> turn 17:57:06.470 --> 17:57:06.480 align:start position:0% code with a minus three it would turn 17:57:06.480 --> 17:57:09.230 align:start position:0% code with a minus three it would turn into<17:57:06.660> x<17:57:07.080> y<17:57:07.320> z<17:57:07.560> this<17:57:08.220> is<17:57:08.276> a<17:57:08.520> really<17:57:08.636> simple<17:57:08.880> code 17:57:09.230 --> 17:57:09.240 align:start position:0% into x y z this is a really simple code 17:57:09.240 --> 17:57:11.510 align:start position:0% into x y z this is a really simple code which<17:57:09.480> is<17:57:09.596> why<17:57:09.776> it's<17:57:09.956> not<17:57:10.136> used<17:57:10.380> anymore<17:57:10.740> now 17:57:11.510 --> 17:57:11.520 align:start position:0% which is why it's not used anymore now 17:57:11.520 --> 17:57:13.370 align:start position:0% which is why it's not used anymore now we<17:57:11.700> have<17:57:11.880> a<17:57:12.116> much<17:57:12.296> more 17:57:13.370 --> 17:57:13.380 align:start position:0% we have a much more 17:57:13.380 --> 17:57:16.970 align:start position:0% we have a much more intense<17:57:14.340> codes<17:57:14.636> that<17:57:14.936> are<17:57:15.060> used<17:57:15.776> now<17:57:16.380> compared 17:57:16.970 --> 17:57:16.980 align:start position:0% intense codes that are used now compared 17:57:16.980 --> 17:57:18.650 align:start position:0% intense codes that are used now compared to<17:57:17.220> cryptography<17:57:17.936> encryption<17:57:18.360> is<17:57:18.540> the 17:57:18.650 --> 17:57:18.660 align:start position:0% to cryptography encryption is the 17:57:18.660 --> 17:57:19.850 align:start position:0% to cryptography encryption is the practice<17:57:18.840> of<17:57:19.080> putting<17:57:19.320> important<17:57:19.740> and 17:57:19.850 --> 17:57:19.860 align:start position:0% practice of putting important and 17:57:19.860 --> 17:57:22.490 align:start position:0% practice of putting important and confidential<17:57:20.400> information<17:57:21.116> into<17:57:22.020> a<17:57:22.320> code 17:57:22.490 --> 17:57:22.500 align:start position:0% confidential information into a code 17:57:22.500 --> 17:57:24.710 align:start position:0% confidential information into a code that<17:57:23.096> can't<17:57:23.220> be<17:57:23.400> accessed<17:57:23.820> by<17:57:24.000> unauthorized 17:57:24.710 --> 17:57:24.720 align:start position:0% that can't be accessed by unauthorized 17:57:24.720 --> 17:57:28.010 align:start position:0% that can't be accessed by unauthorized users<17:57:25.276> encryption<17:57:26.276> is<17:57:26.820> basically<17:57:27.116> the<17:57:27.360> use<17:57:27.596> of 17:57:28.010 --> 17:57:28.020 align:start position:0% users encryption is basically the use of 17:57:28.020 --> 17:57:30.946 align:start position:0% users encryption is basically the use of cryptography<17:57:28.860> as<17:57:29.400> you<17:57:29.580> can<17:57:29.700> see<17:57:29.936> by<17:57:30.596> the<17:57:30.840> word 17:57:30.946 --> 17:57:30.956 align:start position:0% cryptography as you can see by the word 17:57:30.956 --> 17:57:32.266 align:start position:0% cryptography as you can see by the word here 17:57:32.266 --> 17:57:32.276 align:start position:0% here 17:57:32.276 --> 17:57:34.550 align:start position:0% here so<17:57:33.060> encryption<17:57:33.776> is<17:57:33.900> usually<17:57:34.136> used<17:57:34.320> for 17:57:34.550 --> 17:57:34.560 align:start position:0% so encryption is usually used for 17:57:34.560 --> 17:57:36.230 align:start position:0% so encryption is usually used for information<17:57:34.740> that<17:57:35.096> we<17:57:35.276> want<17:57:35.400> to<17:57:35.520> keep<17:57:35.636> as<17:57:36.060> a 17:57:36.230 --> 17:57:36.240 align:start position:0% information that we want to keep as a 17:57:36.240 --> 17:57:38.446 align:start position:0% information that we want to keep as a secret<17:57:36.416> or<17:57:37.080> that's<17:57:37.256> someone<17:57:37.500> we<17:57:37.860> we<17:57:38.160> want<17:57:38.340> to 17:57:38.446 --> 17:57:38.456 align:start position:0% secret or that's someone we we want to 17:57:38.456 --> 17:57:39.890 align:start position:0% secret or that's someone we we want to make<17:57:38.520> sure<17:57:38.700> is<17:57:38.820> not<17:57:39.060> going<17:57:39.180> to<17:57:39.296> get<17:57:39.416> out<17:57:39.660> to 17:57:39.890 --> 17:57:39.900 align:start position:0% make sure is not going to get out to 17:57:39.900 --> 17:57:41.746 align:start position:0% make sure is not going to get out to other<17:57:40.080> people<17:57:40.320> now<17:57:41.096> a<17:57:41.276> lot<17:57:41.340> of<17:57:41.400> times<17:57:41.580> we're 17:57:41.746 --> 17:57:41.756 align:start position:0% other people now a lot of times we're 17:57:41.756 --> 17:57:42.830 align:start position:0% other people now a lot of times we're going<17:57:41.880> to<17:57:41.880> use<17:57:42.000> encryption<17:57:42.416> with<17:57:42.596> not<17:57:42.720> just 17:57:42.830 --> 17:57:42.840 align:start position:0% going to use encryption with not just 17:57:42.840 --> 17:57:45.050 align:start position:0% going to use encryption with not just regulate<17:57:43.256> and<17:57:43.500> we're<17:57:43.616> going<17:57:43.740> to<17:57:43.796> add<17:57:44.060> higher 17:57:45.050 --> 17:57:45.060 align:start position:0% regulate and we're going to add higher 17:57:45.060 --> 17:57:46.606 align:start position:0% regulate and we're going to add higher end<17:57:45.180> encryption<17:57:45.596> to<17:57:45.776> stuff<17:57:45.956> like<17:57:46.136> credit<17:57:46.380> card 17:57:46.606 --> 17:57:46.616 align:start position:0% end encryption to stuff like credit card 17:57:46.616 --> 17:57:48.286 align:start position:0% end encryption to stuff like credit card numbers<17:57:46.796> Social<17:57:47.220> Security<17:57:47.400> numbers<17:57:47.820> Bank 17:57:48.286 --> 17:57:48.296 align:start position:0% numbers Social Security numbers Bank 17:57:48.296 --> 17:57:49.370 align:start position:0% numbers Social Security numbers Bank information 17:57:49.370 --> 17:57:49.380 align:start position:0% information 17:57:49.380 --> 17:57:50.150 align:start position:0% information Etc 17:57:50.150 --> 17:57:50.160 align:start position:0% Etc 17:57:50.160 --> 17:57:52.310 align:start position:0% Etc so<17:57:50.820> encryption<17:57:51.360> is<17:57:51.540> really<17:57:51.720> just<17:57:51.900> a<17:57:52.020> part<17:57:52.200> of 17:57:52.310 --> 17:57:52.320 align:start position:0% so encryption is really just a part of 17:57:52.320 --> 17:57:54.830 align:start position:0% so encryption is really just a part of cryptography<17:57:53.116> cryptography<17:57:54.116> is<17:57:54.416> broader 17:57:54.830 --> 17:57:54.840 align:start position:0% cryptography cryptography is broader 17:57:54.840 --> 17:57:57.350 align:start position:0% cryptography cryptography is broader encryption<17:57:55.380> happens<17:57:55.740> with<17:57:56.580> the<17:57:56.820> data<17:57:57.060> that<17:57:57.240> is 17:57:57.350 --> 17:57:57.360 align:start position:0% encryption happens with the data that is 17:57:57.360 --> 17:57:59.330 align:start position:0% encryption happens with the data that is being<17:57:57.540> sent<17:57:57.840> through<17:57:58.136> a<17:57:58.320> network<17:57:58.500> so<17:57:59.160> like 17:57:59.330 --> 17:57:59.340 align:start position:0% being sent through a network so like 17:57:59.340 --> 17:58:01.906 align:start position:0% being sent through a network so like cryptography<17:58:00.116> and<17:58:00.596> encryption<17:58:01.136> encrypted 17:58:01.906 --> 17:58:01.916 align:start position:0% cryptography and encryption encrypted 17:58:01.916 --> 17:58:04.670 align:start position:0% cryptography and encryption encrypted message<17:58:02.220> is<17:58:02.700> coded<17:58:03.240> and<17:58:03.900> appears<17:58:04.320> to<17:58:04.500> be 17:58:04.670 --> 17:58:04.680 align:start position:0% message is coded and appears to be 17:58:04.680 --> 17:58:06.406 align:start position:0% message is coded and appears to be complete<17:58:05.160> nonsense<17:58:05.520> to<17:58:05.756> someone<17:58:05.936> who<17:58:06.296> doesn't 17:58:06.406 --> 17:58:06.416 align:start position:0% complete nonsense to someone who doesn't 17:58:06.416 --> 17:58:09.350 align:start position:0% complete nonsense to someone who doesn't know<17:58:06.720> what<17:58:07.080> the<17:58:07.320> code<17:58:07.500> is<17:58:07.916> now<17:58:08.756> the<17:58:08.936> data<17:58:09.240> is 17:58:09.350 --> 17:58:09.360 align:start position:0% know what the code is now the data is 17:58:09.360 --> 17:58:11.150 align:start position:0% know what the code is now the data is run<17:58:09.540> through<17:58:09.776> an<17:58:10.080> algorithm<17:58:10.560> in<17:58:10.740> order<17:58:10.916> to 17:58:11.150 --> 17:58:11.160 align:start position:0% run through an algorithm in order to 17:58:11.160 --> 17:58:13.670 align:start position:0% run through an algorithm in order to place<17:58:11.340> encryption<17:58:11.880> on<17:58:12.116> it<17:58:12.720> then<17:58:13.200> on<17:58:13.500> the<17:58:13.560> other 17:58:13.670 --> 17:58:13.680 align:start position:0% place encryption on it then on the other 17:58:13.680 --> 17:58:15.766 align:start position:0% place encryption on it then on the other side<17:58:13.916> the<17:58:14.520> reverse<17:58:14.880> of<17:58:15.000> the<17:58:15.116> algorithm<17:58:15.540> is 17:58:15.766 --> 17:58:15.776 align:start position:0% side the reverse of the algorithm is 17:58:15.776 --> 17:58:18.530 align:start position:0% side the reverse of the algorithm is used<17:58:16.020> to<17:58:16.200> decrypt<17:58:16.980> the<17:58:17.276> data<17:58:17.636> and<17:58:18.360> an 17:58:18.530 --> 17:58:18.540 align:start position:0% used to decrypt the data and an 17:58:18.540 --> 17:58:20.390 align:start position:0% used to decrypt the data and an algorithm<17:58:18.956> is<17:58:19.200> a<17:58:19.436> mathematical<17:58:19.980> equation 17:58:20.390 --> 17:58:20.400 align:start position:0% algorithm is a mathematical equation 17:58:20.400 --> 17:58:21.650 align:start position:0% algorithm is a mathematical equation that<17:58:20.700> can<17:58:20.756> be<17:58:20.880> used<17:58:21.000> for<17:58:21.180> several<17:58:21.480> different 17:58:21.650 --> 17:58:21.660 align:start position:0% that can be used for several different 17:58:21.660 --> 17:58:23.230 align:start position:0% that can be used for several different things<17:58:21.956> for<17:58:22.320> instance<17:58:22.500> in<17:58:22.616> the<17:58:22.740> Caesar<17:58:23.096> code 17:58:23.230 --> 17:58:23.240 align:start position:0% things for instance in the Caesar code 17:58:23.240 --> 17:58:28.670 align:start position:0% things for instance in the Caesar code the<17:58:24.240> mathematical<17:58:25.080> equation<17:58:25.560> if<17:58:26.400> we<17:58:26.580> had<17:58:26.880> X<17:58:27.900> as 17:58:28.670 --> 17:58:28.680 align:start position:0% the mathematical equation if we had X as 17:58:28.680 --> 17:58:31.606 align:start position:0% the mathematical equation if we had X as the<17:58:29.160> uh<17:58:30.116> plain<17:58:30.596> text 17:58:31.606 --> 17:58:31.616 align:start position:0% the uh plain text 17:58:31.616 --> 17:58:35.210 align:start position:0% the uh plain text and<17:58:32.400> Y<17:58:32.700> as<17:58:33.060> the<17:58:33.596> cipher<17:58:34.380> text<17:58:34.560> or<17:58:34.980> the<17:58:35.096> text 17:58:35.210 --> 17:58:35.220 align:start position:0% and Y as the cipher text or the text 17:58:35.220 --> 17:58:37.730 align:start position:0% and Y as the cipher text or the text that<17:58:35.520> had<17:58:35.636> a<17:58:35.820> code<17:58:36.000> added<17:58:36.480> to<17:58:36.596> it<17:58:36.776> we<17:58:37.380> could<17:58:37.500> say 17:58:37.730 --> 17:58:37.740 align:start position:0% that had a code added to it we could say 17:58:37.740 --> 17:58:40.310 align:start position:0% that had a code added to it we could say that<17:58:38.096> if<17:58:38.636> we<17:58:38.820> took<17:58:39.116> the<17:58:39.296> code<17:58:39.540> it<17:58:40.080> would<17:58:40.200> equal 17:58:40.310 --> 17:58:40.320 align:start position:0% that if we took the code it would equal 17:58:40.320 --> 17:58:45.170 align:start position:0% that if we took the code it would equal y<17:58:40.680> plus<17:58:40.980> 3.<17:58:41.520> so<17:58:41.820> if<17:58:42.296> we<17:58:42.480> had<17:58:42.720> x<17:58:43.436> y<17:58:43.916> z<17:58:44.220> and<17:58:45.000> that 17:58:45.170 --> 17:58:45.180 align:start position:0% y plus 3. so if we had x y z and that 17:58:45.180 --> 17:58:47.690 align:start position:0% y plus 3. so if we had x y z and that was<17:58:45.296> our<17:58:45.596> code 17:58:47.690 --> 17:58:47.700 align:start position:0% was our code 17:58:47.700 --> 17:58:51.586 align:start position:0% was our code and<17:58:48.180> we<17:58:48.360> added<17:58:48.840> 3<17:58:49.136> to<17:58:49.436> that 17:58:51.586 --> 17:58:51.596 align:start position:0% and we added 3 to that 17:58:51.596 --> 17:58:55.126 align:start position:0% and we added 3 to that then<17:58:52.136> we<17:58:52.320> would<17:58:52.560> end<17:58:52.796> up<17:58:52.980> with<17:58:53.400> a<17:58:53.820> b<17:58:54.240> c<17:58:54.480> and<17:58:54.956> so 17:58:55.126 --> 17:58:55.136 align:start position:0% then we would end up with a b c and so 17:58:55.136 --> 17:58:57.406 align:start position:0% then we would end up with a b c and so that's<17:58:55.380> how<17:58:55.616> that<17:58:55.860> all<17:58:55.980> sort<17:58:56.220> of<17:58:56.340> works<17:58:56.700> now 17:58:57.406 --> 17:58:57.416 align:start position:0% that's how that all sort of works now 17:58:57.416 --> 17:58:59.870 align:start position:0% that's how that all sort of works now encryption<17:58:58.020> in<17:58:58.380> an<17:58:58.560> algorithms<17:58:59.096> are<17:58:59.276> a<17:58:59.756> lot 17:58:59.870 --> 17:58:59.880 align:start position:0% encryption in an algorithms are a lot 17:58:59.880 --> 17:59:01.850 align:start position:0% encryption in an algorithms are a lot more<17:59:00.116> intense<17:59:00.660> than<17:59:00.900> the<17:59:01.080> one<17:59:01.136> I<17:59:01.380> just<17:59:01.560> sort<17:59:01.740> of 17:59:01.850 --> 17:59:01.860 align:start position:0% more intense than the one I just sort of 17:59:01.860 --> 17:59:03.710 align:start position:0% more intense than the one I just sort of laid<17:59:02.096> out<17:59:02.220> and<17:59:02.700> they're<17:59:02.820> used<17:59:03.000> not<17:59:03.296> only<17:59:03.360> to 17:59:03.710 --> 17:59:03.720 align:start position:0% laid out and they're used not only to 17:59:03.720 --> 17:59:06.286 align:start position:0% laid out and they're used not only to code<17:59:04.020> data<17:59:04.740> but<17:59:05.040> also<17:59:05.276> to<17:59:05.456> decrypt<17:59:05.936> it<17:59:06.116> or 17:59:06.286 --> 17:59:06.296 align:start position:0% code data but also to decrypt it or 17:59:06.296 --> 17:59:08.330 align:start position:0% code data but also to decrypt it or unencode<17:59:06.776> it<17:59:06.956> in<17:59:07.380> a<17:59:07.500> way<17:59:07.616> that<17:59:07.796> can't<17:59:07.980> be<17:59:08.160> read 17:59:08.330 --> 17:59:08.340 align:start position:0% unencode it in a way that can't be read 17:59:08.340 --> 17:59:11.446 align:start position:0% unencode it in a way that can't be read by<17:59:08.580> our<17:59:08.880> adversaries<17:59:09.596> or<17:59:09.776> people<17:59:10.020> outside<17:59:10.456> of 17:59:11.446 --> 17:59:11.456 align:start position:0% by our adversaries or people outside of 17:59:11.456 --> 17:59:13.730 align:start position:0% by our adversaries or people outside of of<17:59:12.296> ourselves 17:59:13.730 --> 17:59:13.740 align:start position:0% of ourselves 17:59:13.740 --> 17:59:16.246 align:start position:0% of ourselves so<17:59:14.400> through<17:59:14.820> the<17:59:15.000> encryption<17:59:15.480> process<17:59:15.900> we 17:59:16.246 --> 17:59:16.256 align:start position:0% so through the encryption process we 17:59:16.256 --> 17:59:18.050 align:start position:0% so through the encryption process we come<17:59:16.380> across<17:59:16.740> around<17:59:17.340> two<17:59:17.636> different<17:59:17.820> types 17:59:18.050 --> 17:59:18.060 align:start position:0% come across around two different types 17:59:18.060 --> 17:59:20.086 align:start position:0% come across around two different types of<17:59:18.180> text<17:59:18.296> that<17:59:18.596> I<17:59:18.720> just<17:59:18.840> pointed<17:59:19.136> out<17:59:19.256> first 17:59:20.086 --> 17:59:20.096 align:start position:0% of text that I just pointed out first 17:59:20.096 --> 17:59:22.070 align:start position:0% of text that I just pointed out first there's<17:59:20.520> plain<17:59:21.116> text<17:59:21.296> this<17:59:21.720> is<17:59:21.840> the 17:59:22.070 --> 17:59:22.080 align:start position:0% there's plain text this is the 17:59:22.080 --> 17:59:24.170 align:start position:0% there's plain text this is the unencrypted<17:59:22.740> data<17:59:23.096> at<17:59:23.456> this<17:59:23.636> point<17:59:23.756> anyone 17:59:24.170 --> 17:59:24.180 align:start position:0% unencrypted data at this point anyone 17:59:24.180 --> 17:59:25.850 align:start position:0% unencrypted data at this point anyone can<17:59:24.360> read<17:59:24.540> what<17:59:24.776> it<17:59:24.900> says<17:59:25.136> because<17:59:25.320> there's<17:59:25.616> no 17:59:25.850 --> 17:59:25.860 align:start position:0% can read what it says because there's no 17:59:25.860 --> 17:59:28.370 align:start position:0% can read what it says because there's no code<17:59:26.040> on<17:59:26.276> it<17:59:26.456> then<17:59:27.060> there's<17:59:27.360> ciphertext<17:59:28.080> which 17:59:28.370 --> 17:59:28.380 align:start position:0% code on it then there's ciphertext which 17:59:28.380 --> 17:59:30.830 align:start position:0% code on it then there's ciphertext which is<17:59:28.500> the<17:59:28.796> encrypted<17:59:29.340> data<17:59:29.756> the<17:59:30.180> data<17:59:30.480> that<17:59:30.660> can 17:59:30.830 --> 17:59:30.840 align:start position:0% is the encrypted data the data that can 17:59:30.840 --> 17:59:33.766 align:start position:0% is the encrypted data the data that can only<17:59:31.020> be<17:59:31.320> decrypted<17:59:31.980> using<17:59:32.400> a<17:59:32.580> special<17:59:32.756> key<17:59:33.180> or 17:59:33.766 --> 17:59:33.776 align:start position:0% only be decrypted using a special key or 17:59:33.776 --> 17:59:35.870 align:start position:0% only be decrypted using a special key or using<17:59:34.136> that<17:59:34.320> special<17:59:34.560> algorithm 17:59:35.870 --> 17:59:35.880 align:start position:0% using that special algorithm 17:59:35.880 --> 17:59:38.150 align:start position:0% using that special algorithm so<17:59:36.296> in<17:59:36.480> the<17:59:36.596> world<17:59:36.720> of<17:59:36.956> encryption<17:59:37.436> there<17:59:38.040> are 17:59:38.150 --> 17:59:38.160 align:start position:0% so in the world of encryption there are 17:59:38.160 --> 17:59:41.086 align:start position:0% so in the world of encryption there are normally<17:59:38.456> two<17:59:38.820> different<17:59:39.060> types<17:59:39.840> of<17:59:40.080> keys<17:59:40.616> or 17:59:41.086 --> 17:59:41.096 align:start position:0% normally two different types of keys or 17:59:41.096 --> 17:59:42.890 align:start position:0% normally two different types of keys or algorithms<17:59:41.756> in<17:59:42.060> other<17:59:42.116> words<17:59:42.296> that<17:59:42.596> come<17:59:42.776> into 17:59:42.890 --> 17:59:42.900 align:start position:0% algorithms in other words that come into 17:59:42.900 --> 17:59:44.746 align:start position:0% algorithms in other words that come into play<17:59:43.200> first<17:59:43.916> there<17:59:44.160> are<17:59:44.340> what<17:59:44.456> are<17:59:44.636> called 17:59:44.746 --> 17:59:44.756 align:start position:0% play first there are what are called 17:59:44.756 --> 17:59:47.570 align:start position:0% play first there are what are called public<17:59:45.296> Keys<17:59:45.900> these<17:59:46.616> are<17:59:46.740> generally<17:59:47.040> used<17:59:47.340> in 17:59:47.570 --> 17:59:47.580 align:start position:0% public Keys these are generally used in 17:59:47.580 --> 17:59:48.830 align:start position:0% public Keys these are generally used in some<17:59:47.820> cases 17:59:48.830 --> 17:59:48.840 align:start position:0% some cases 17:59:48.840 --> 17:59:52.490 align:start position:0% some cases to<17:59:49.436> encrypt<17:59:49.860> the<17:59:50.096> data<17:59:50.400> these<17:59:51.180> keys<17:59:51.596> are<17:59:52.200> known 17:59:52.490 --> 17:59:52.500 align:start position:0% to encrypt the data these keys are known 17:59:52.500 --> 17:59:55.190 align:start position:0% to encrypt the data these keys are known by<17:59:53.340> both<17:59:53.580> parties<17:59:54.116> that's<17:59:54.720> why<17:59:54.956> they're 17:59:55.190 --> 17:59:55.200 align:start position:0% by both parties that's why they're 17:59:55.200 --> 17:59:58.010 align:start position:0% by both parties that's why they're public<17:59:55.436> they're<17:59:55.796> put<17:59:56.040> out<17:59:56.360> on<17:59:57.360> the<17:59:57.480> web<17:59:57.660> or 17:59:58.010 --> 17:59:58.020 align:start position:0% public they're put out on the web or 17:59:58.020 --> 17:59:59.570 align:start position:0% public they're put out on the web or they're<17:59:58.256> sent<17:59:58.500> out<17:59:58.740> by<17:59:58.916> email<17:59:59.096> or<17:59:59.400> something 17:59:59.570 --> 17:59:59.580 align:start position:0% they're sent out by email or something 17:59:59.580 --> 18:00:02.086 align:start position:0% they're sent out by email or something so<18:00:00.060> everyone<18:00:00.360> has<18:00:00.840> it<18:00:01.080> and<18:00:01.616> these<18:00:01.796> keys<18:00:02.040> are 18:00:02.086 --> 18:00:02.096 align:start position:0% so everyone has it and these keys are 18:00:02.096 --> 18:00:04.310 align:start position:0% so everyone has it and these keys are known<18:00:02.276> by<18:00:02.456> both<18:00:02.636> parties<18:00:03.116> so<18:00:03.416> that<18:00:03.660> in<18:00:03.840> a<18:00:04.020> data 18:00:04.310 --> 18:00:04.320 align:start position:0% known by both parties so that in a data 18:00:04.320 --> 18:00:06.650 align:start position:0% known by both parties so that in a data transfer<18:00:04.740> they<18:00:05.160> can<18:00:05.340> be<18:00:05.520> used<18:00:05.700> to<18:00:06.060> encrypt<18:00:06.480> the 18:00:06.650 --> 18:00:06.660 align:start position:0% transfer they can be used to encrypt the 18:00:06.660 --> 18:00:09.406 align:start position:0% transfer they can be used to encrypt the data<18:00:07.020> now<18:00:07.436> in<18:00:07.616> most<18:00:07.796> cases<18:00:08.220> the<18:00:08.636> and<18:00:08.880> receiving 18:00:09.406 --> 18:00:09.416 align:start position:0% data now in most cases the and receiving 18:00:09.416 --> 18:00:12.470 align:start position:0% data now in most cases the and receiving the<18:00:09.720> data<18:00:10.020> receives<18:00:10.680> the<18:00:10.916> public<18:00:11.096> key<18:00:11.400> also<18:00:11.880> so 18:00:12.470 --> 18:00:12.480 align:start position:0% the data receives the public key also so 18:00:12.480 --> 18:00:15.650 align:start position:0% the data receives the public key also so if<18:00:12.660> I'm<18:00:12.900> sending<18:00:13.320> you<18:00:13.500> uh<18:00:14.400> an<18:00:14.936> encrypted<18:00:15.416> sort 18:00:15.650 --> 18:00:15.660 align:start position:0% if I'm sending you uh an encrypted sort 18:00:15.660 --> 18:00:17.086 align:start position:0% if I'm sending you uh an encrypted sort of<18:00:15.776> message<18:00:16.020> I'm<18:00:16.380> going<18:00:16.560> to<18:00:16.680> send<18:00:16.796> you<18:00:16.916> the 18:00:17.086 --> 18:00:17.096 align:start position:0% of message I'm going to send you the 18:00:17.096 --> 18:00:20.330 align:start position:0% of message I'm going to send you the public<18:00:17.220> key<18:00:17.520> along<18:00:18.296> with<18:00:18.776> my<18:00:19.136> data<18:00:19.560> now<18:00:20.160> the 18:00:20.330 --> 18:00:20.340 align:start position:0% public key along with my data now the 18:00:20.340 --> 18:00:21.766 align:start position:0% public key along with my data now the way<18:00:20.456> that<18:00:20.636> encryption<18:00:21.060> and<18:00:21.180> decryption<18:00:21.596> will 18:00:21.766 --> 18:00:21.776 align:start position:0% way that encryption and decryption will 18:00:21.776 --> 18:00:23.926 align:start position:0% way that encryption and decryption will work<18:00:22.020> is<18:00:22.436> the<18:00:22.616> same<18:00:22.740> way<18:00:22.916> these<18:00:23.340> public<18:00:23.520> Keys 18:00:23.926 --> 18:00:23.936 align:start position:0% work is the same way these public Keys 18:00:23.936 --> 18:00:25.970 align:start position:0% work is the same way these public Keys run<18:00:24.116> plain<18:00:24.540> text<18:00:24.720> through<18:00:25.380> the<18:00:25.560> encryption 18:00:25.970 --> 18:00:25.980 align:start position:0% run plain text through the encryption 18:00:25.980 --> 18:00:28.310 align:start position:0% run plain text through the encryption algorithm<18:00:26.580> and<18:00:27.180> they<18:00:27.360> Place<18:00:27.540> coding<18:00:27.956> on<18:00:28.136> it 18:00:28.310 --> 18:00:28.320 align:start position:0% algorithm and they Place coding on it 18:00:28.320 --> 18:00:30.766 align:start position:0% algorithm and they Place coding on it now<18:00:28.980> private<18:00:29.456> keys<18:00:29.820> on<18:00:29.936> the<18:00:30.000> other<18:00:30.116> hand<18:00:30.240> are 18:00:30.766 --> 18:00:30.776 align:start position:0% now private keys on the other hand are 18:00:30.776 --> 18:00:34.370 align:start position:0% now private keys on the other hand are usually<18:00:31.020> only<18:00:31.256> used<18:00:31.560> to<18:00:31.980> decrypt<18:00:32.520> the<18:00:32.756> data<18:00:33.116> so 18:00:34.370 --> 18:00:34.380 align:start position:0% usually only used to decrypt the data so 18:00:34.380 --> 18:00:37.190 align:start position:0% usually only used to decrypt the data so I<18:00:34.916> will<18:00:35.160> send<18:00:35.340> you<18:00:35.520> my<18:00:35.756> public<18:00:35.936> key<18:00:36.240> you<18:00:37.020> will 18:00:37.190 --> 18:00:37.200 align:start position:0% I will send you my public key you will 18:00:37.200 --> 18:00:39.890 align:start position:0% I will send you my public key you will encrypt<18:00:37.740> a<18:00:38.040> message<18:00:38.220> send<18:00:38.820> it<18:00:39.000> to<18:00:39.116> me<18:00:39.240> and<18:00:39.720> I 18:00:39.890 --> 18:00:39.900 align:start position:0% encrypt a message send it to me and I 18:00:39.900 --> 18:00:41.870 align:start position:0% encrypt a message send it to me and I can<18:00:40.020> only<18:00:40.200> decrypt<18:00:40.796> that<18:00:40.980> using<18:00:41.400> a<18:00:41.636> private 18:00:41.870 --> 18:00:41.880 align:start position:0% can only decrypt that using a private 18:00:41.880 --> 18:00:45.106 align:start position:0% can only decrypt that using a private key<18:00:42.000> which<18:00:42.416> only<18:00:42.840> I<18:00:43.380> have<18:00:43.616> and<18:00:44.520> so<18:00:44.636> this<18:00:44.936> is 18:00:45.106 --> 18:00:45.116 align:start position:0% key which only I have and so this is 18:00:45.116 --> 18:00:47.990 align:start position:0% key which only I have and so this is basically<18:00:45.540> how<18:00:46.080> the<18:00:46.680> whole<18:00:46.860> system<18:00:47.160> works<18:00:47.636> now 18:00:47.990 --> 18:00:48.000 align:start position:0% basically how the whole system works now 18:00:48.000 --> 18:00:50.810 align:start position:0% basically how the whole system works now there<18:00:48.360> are<18:00:48.480> different<18:00:48.776> types<18:00:49.436> of<18:00:49.916> uh 18:00:50.810 --> 18:00:50.820 align:start position:0% there are different types of uh 18:00:50.820 --> 18:00:52.850 align:start position:0% there are different types of uh encryption<18:00:51.360> systems<18:00:51.840> somewhere<18:00:52.256> both<18:00:52.500> sides 18:00:52.850 --> 18:00:52.860 align:start position:0% encryption systems somewhere both sides 18:00:52.860 --> 18:00:54.406 align:start position:0% encryption systems somewhere both sides have<18:00:53.040> to<18:00:53.160> have<18:00:53.340> public<18:00:53.520> keys<18:00:53.936> somewhere<18:00:54.296> we 18:00:54.406 --> 18:00:54.416 align:start position:0% have to have public keys somewhere we 18:00:54.416 --> 18:00:56.150 align:start position:0% have to have public keys somewhere we have<18:00:54.596> a<18:00:54.776> private<18:00:55.080> key<18:00:55.200> again<18:00:55.680> I'm<18:00:55.916> not<18:00:56.040> going 18:00:56.150 --> 18:00:56.160 align:start position:0% have a private key again I'm not going 18:00:56.160 --> 18:00:57.710 align:start position:0% have a private key again I'm not going to<18:00:56.276> get<18:00:56.400> too<18:00:56.580> in<18:00:56.756> depth<18:00:57.000> with<18:00:57.116> that<18:00:57.360> right<18:00:57.540> now 18:00:57.710 --> 18:00:57.720 align:start position:0% to get too in depth with that right now 18:00:57.720 --> 18:01:00.946 align:start position:0% to get too in depth with that right now because<18:00:58.020> this<18:00:58.380> really<18:00:58.616> gets<18:00:59.040> into<18:00:59.776> more<18:01:00.776> of 18:01:00.946 --> 18:01:00.956 align:start position:0% because this really gets into more of 18:01:00.956 --> 18:01:02.926 align:start position:0% because this really gets into more of security<18:01:01.136> and<18:01:01.500> Security<18:01:01.680> Plus<18:01:02.160> but<18:01:02.820> the 18:01:02.926 --> 18:01:02.936 align:start position:0% security and Security Plus but the 18:01:02.936 --> 18:01:04.370 align:start position:0% security and Security Plus but the important<18:01:03.240> thing<18:01:03.360> to<18:01:03.480> realize<18:01:03.776> is<18:01:03.900> that<18:01:04.136> the 18:01:04.370 --> 18:01:04.380 align:start position:0% important thing to realize is that the 18:01:04.380 --> 18:01:05.626 align:start position:0% important thing to realize is that the public<18:01:04.560> key 18:01:05.626 --> 18:01:05.636 align:start position:0% public key 18:01:05.636 --> 18:01:08.030 align:start position:0% public key goes<18:01:06.416> to<18:01:06.540> both<18:01:06.720> parties<18:01:07.080> whereas<18:01:07.500> the<18:01:07.680> private 18:01:08.030 --> 18:01:08.040 align:start position:0% goes to both parties whereas the private 18:01:08.040 --> 18:01:10.190 align:start position:0% goes to both parties whereas the private key<18:01:08.276> which<18:01:08.936> is<18:01:09.116> only<18:01:09.360> used<18:01:09.596> usually<18:01:09.956> to 18:01:10.190 --> 18:01:10.200 align:start position:0% key which is only used usually to 18:01:10.200 --> 18:01:12.530 align:start position:0% key which is only used usually to decrypt<18:01:10.680> the<18:01:10.860> data<18:01:11.096> is<18:01:11.340> only<18:01:11.520> held<18:01:11.936> on<18:01:12.000> to<18:01:12.240> one 18:01:12.530 --> 18:01:12.540 align:start position:0% decrypt the data is only held on to one 18:01:12.540 --> 18:01:15.106 align:start position:0% decrypt the data is only held on to one person<18:01:12.776> so<18:01:13.500> I<18:01:13.680> could<18:01:13.860> anyone<18:01:14.340> can<18:01:14.520> encrypt<18:01:14.936> the 18:01:15.106 --> 18:01:15.116 align:start position:0% person so I could anyone can encrypt the 18:01:15.116 --> 18:01:16.550 align:start position:0% person so I could anyone can encrypt the message<18:01:15.296> but<18:01:15.660> only<18:01:15.776> someone<18:01:16.080> with<18:01:16.320> the 18:01:16.550 --> 18:01:16.560 align:start position:0% message but only someone with the 18:01:16.560 --> 18:01:17.830 align:start position:0% message but only someone with the private<18:01:16.860> key<18:01:16.980> is<18:01:17.160> going<18:01:17.340> to<18:01:17.456> be<18:01:17.520> able<18:01:17.636> to 18:01:17.830 --> 18:01:17.840 align:start position:0% private key is going to be able to 18:01:17.840 --> 18:01:20.390 align:start position:0% private key is going to be able to decrypt<18:01:18.840> the<18:01:19.020> message 18:01:20.390 --> 18:01:20.400 align:start position:0% decrypt the message 18:01:20.400 --> 18:01:23.210 align:start position:0% decrypt the message so<18:01:20.700> if<18:01:20.756> we<18:01:20.880> take<18:01:21.000> a<18:01:21.116> look<18:01:21.180> at<18:01:21.296> how<18:01:21.540> this<18:01:21.776> works 18:01:23.210 --> 18:01:23.220 align:start position:0% so if we take a look at how this works 18:01:23.220 --> 18:01:26.446 align:start position:0% so if we take a look at how this works um<18:01:23.340> company<18:01:23.936> a<18:01:24.436> needs<18:01:25.436> to<18:01:25.560> send<18:01:25.860> data<18:01:26.340> to 18:01:26.446 --> 18:01:26.456 align:start position:0% um company a needs to send data to 18:01:26.456 --> 18:01:28.126 align:start position:0% um company a needs to send data to Company<18:01:26.636> B<18:01:27.000> but<18:01:27.480> it's<18:01:27.596> really<18:01:27.776> important 18:01:28.126 --> 18:01:28.136 align:start position:0% Company B but it's really important 18:01:28.136 --> 18:01:29.746 align:start position:0% Company B but it's really important information<18:01:28.320> that<18:01:28.796> needs<18:01:28.980> to<18:01:29.096> be<18:01:29.276> secure<18:01:29.636> and 18:01:29.746 --> 18:01:29.756 align:start position:0% information that needs to be secure and 18:01:29.756 --> 18:01:35.330 align:start position:0% information that needs to be secure and encrypted<18:01:30.296> so<18:01:31.080> Company<18:01:31.740> B<18:01:32.720> sends<18:01:33.980> the<18:01:34.980> public 18:01:35.330 --> 18:01:35.340 align:start position:0% encrypted so Company B sends the public 18:01:35.340 --> 18:01:38.086 align:start position:0% encrypted so Company B sends the public key<18:01:35.756> to<18:01:36.720> company<18:01:36.956> a 18:01:38.086 --> 18:01:38.096 align:start position:0% key to company a 18:01:38.096 --> 18:01:40.490 align:start position:0% key to company a company<18:01:38.636> be<18:01:38.936> created<18:01:39.296> this<18:01:39.660> public<18:01:39.956> key<18:01:40.256> so 18:01:40.490 --> 18:01:40.500 align:start position:0% company be created this public key so 18:01:40.500 --> 18:01:42.286 align:start position:0% company be created this public key so that<18:01:40.680> the<18:01:40.796> encryption<18:01:41.160> and<18:01:41.276> decryption<18:01:41.880> would 18:01:42.286 --> 18:01:42.296 align:start position:0% that the encryption and decryption would 18:01:42.296 --> 18:01:44.746 align:start position:0% that the encryption and decryption would work<18:01:42.540> with<18:01:42.720> each<18:01:42.956> other<18:01:43.080> now<18:01:43.680> company<18:01:43.916> a<18:01:44.276> uses 18:01:44.746 --> 18:01:44.756 align:start position:0% work with each other now company a uses 18:01:44.756 --> 18:01:46.850 align:start position:0% work with each other now company a uses this<18:01:44.936> key<18:01:45.116> to<18:01:45.296> encrypt<18:01:45.720> the<18:01:45.840> data<18:01:46.136> then<18:01:46.436> sends 18:01:46.850 --> 18:01:46.860 align:start position:0% this key to encrypt the data then sends 18:01:46.860 --> 18:01:50.086 align:start position:0% this key to encrypt the data then sends it<18:01:46.980> to<18:01:47.096> Company<18:01:47.220> B<18:01:47.580> and<18:01:48.296> Company<18:01:48.480> B<18:01:48.956> uses<18:01:49.796> the 18:01:50.086 --> 18:01:50.096 align:start position:0% it to Company B and Company B uses the 18:01:50.096 --> 18:01:52.970 align:start position:0% it to Company B and Company B uses the private<18:01:50.400> key<18:01:50.580> that<18:01:51.116> only<18:01:51.480> they<18:01:52.020> have 18:01:52.970 --> 18:01:52.980 align:start position:0% private key that only they have 18:01:52.980 --> 18:01:55.786 align:start position:0% private key that only they have in<18:01:53.400> order<18:01:53.580> to<18:01:54.000> decrypt<18:01:54.540> the<18:01:54.720> data<18:01:55.080> now<18:01:55.436> you<18:01:55.680> can 18:01:55.786 --> 18:01:55.796 align:start position:0% in order to decrypt the data now you can 18:01:55.796 --> 18:01:59.266 align:start position:0% in order to decrypt the data now you can only<18:01:56.240> encrypt<18:01:57.240> in<18:01:57.660> this<18:01:57.776> case<18:01:58.020> with<18:01:58.916> the 18:01:59.266 --> 18:01:59.276 align:start position:0% only encrypt in this case with the 18:01:59.276 --> 18:02:02.150 align:start position:0% only encrypt in this case with the public<18:01:59.400> key<18:01:59.776> and<18:02:00.776> you<18:02:01.020> need<18:02:01.256> the<18:02:01.560> private<18:02:01.916> key 18:02:02.150 --> 18:02:02.160 align:start position:0% public key and you need the private key 18:02:02.160 --> 18:02:04.190 align:start position:0% public key and you need the private key in<18:02:02.520> order<18:02:02.700> to<18:02:03.000> decrypt<18:02:03.416> that's<18:02:03.720> how<18:02:03.956> this 18:02:04.190 --> 18:02:04.200 align:start position:0% in order to decrypt that's how this 18:02:04.200 --> 18:02:07.190 align:start position:0% in order to decrypt that's how this works<18:02:04.680> but<18:02:05.456> the<18:02:05.880> way<18:02:06.000> that<18:02:06.180> company<18:02:06.416> a<18:02:06.720> got<18:02:07.020> it 18:02:07.190 --> 18:02:07.200 align:start position:0% works but the way that company a got it 18:02:07.200 --> 18:02:10.246 align:start position:0% works but the way that company a got it is<18:02:07.436> because<18:02:07.616> Company<18:02:08.096> B<18:02:08.580> sent<18:02:09.416> the<18:02:09.840> public<18:02:09.956> key 18:02:10.246 --> 18:02:10.256 align:start position:0% is because Company B sent the public key 18:02:10.256 --> 18:02:11.990 align:start position:0% is because Company B sent the public key over<18:02:10.560> to<18:02:10.916> them 18:02:11.990 --> 18:02:12.000 align:start position:0% over to them 18:02:12.000 --> 18:02:14.086 align:start position:0% over to them all<18:02:12.480> right<18:02:12.596> so<18:02:12.720> just<18:02:12.900> to<18:02:13.080> recap<18:02:13.380> we<18:02:13.680> began<18:02:13.860> by 18:02:14.086 --> 18:02:14.096 align:start position:0% all right so just to recap we began by 18:02:14.096 --> 18:02:15.906 align:start position:0% all right so just to recap we began by defining<18:02:14.520> And<18:02:14.700> discussing<18:02:15.060> cryptography 18:02:15.906 --> 18:02:15.916 align:start position:0% defining And discussing cryptography 18:02:15.916 --> 18:02:19.070 align:start position:0% defining And discussing cryptography cryptography<18:02:16.916> again<18:02:17.220> is<18:02:17.700> basically<18:02:18.116> having<18:02:18.596> a 18:02:19.070 --> 18:02:19.080 align:start position:0% cryptography again is basically having a 18:02:19.080 --> 18:02:22.070 align:start position:0% cryptography again is basically having a code<18:02:19.256> of<18:02:19.616> some<18:02:19.860> sort<18:02:20.096> uh<18:02:21.060> we<18:02:21.296> use<18:02:21.416> codes<18:02:21.660> in<18:02:21.900> all 18:02:22.070 --> 18:02:22.080 align:start position:0% code of some sort uh we use codes in all 18:02:22.080 --> 18:02:24.230 align:start position:0% code of some sort uh we use codes in all sorts<18:02:22.320> of<18:02:22.380> ways<18:02:22.740> we<18:02:22.980> talked<18:02:23.276> about<18:02:23.340> the<18:02:23.700> Navajo 18:02:24.230 --> 18:02:24.240 align:start position:0% sorts of ways we talked about the Navajo 18:02:24.240 --> 18:02:26.266 align:start position:0% sorts of ways we talked about the Navajo Indians<18:02:24.720> using<18:02:25.020> codes<18:02:25.200> during<18:02:25.560> World<18:02:25.740> War<18:02:25.916> II 18:02:26.266 --> 18:02:26.276 align:start position:0% Indians using codes during World War II 18:02:26.276 --> 18:02:28.370 align:start position:0% Indians using codes during World War II and<18:02:26.820> we<18:02:27.000> also<18:02:27.240> talked<18:02:27.540> about<18:02:27.660> the<18:02:27.956> Caesar 18:02:28.370 --> 18:02:28.380 align:start position:0% and we also talked about the Caesar 18:02:28.380 --> 18:02:30.530 align:start position:0% and we also talked about the Caesar Cipher<18:02:28.860> which<18:02:29.040> basically<18:02:29.400> just<18:02:29.520> means<18:02:29.880> adding 18:02:30.530 --> 18:02:30.540 align:start position:0% Cipher which basically just means adding 18:02:30.540 --> 18:02:32.870 align:start position:0% Cipher which basically just means adding a<18:02:31.320> certain<18:02:31.616> number 18:02:32.870 --> 18:02:32.880 align:start position:0% a certain number 18:02:32.880 --> 18:02:35.926 align:start position:0% a certain number two<18:02:33.360> uh<18:02:33.776> letters<18:02:34.136> so<18:02:34.320> for<18:02:34.560> instance<18:02:34.860> if<18:02:35.456> I<18:02:35.636> have 18:02:35.926 --> 18:02:35.936 align:start position:0% two uh letters so for instance if I have 18:02:35.936 --> 18:02:38.810 align:start position:0% two uh letters so for instance if I have plus<18:02:36.416> 2<18:02:36.776> as<18:02:37.080> my<18:02:37.256> Caesar<18:02:37.616> Cipher<18:02:38.096> and<18:02:38.456> I<18:02:38.580> want<18:02:38.700> to 18:02:38.810 --> 18:02:38.820 align:start position:0% plus 2 as my Caesar Cipher and I want to 18:02:38.820 --> 18:02:40.850 align:start position:0% plus 2 as my Caesar Cipher and I want to write<18:02:38.936> the<18:02:39.116> letter<18:02:39.296> A<18:02:39.660> instead<18:02:40.436> I'm<18:02:40.680> going<18:02:40.796> to 18:02:40.850 --> 18:02:40.860 align:start position:0% write the letter A instead I'm going to 18:02:40.860 --> 18:02:44.810 align:start position:0% write the letter A instead I'm going to write<18:02:40.980> the<18:02:41.160> letter<18:02:41.276> c<18:02:42.000> because<18:02:42.480> it<18:02:42.956> goes<18:02:43.256> a<18:02:43.680> b<18:02:44.456> c 18:02:44.810 --> 18:02:44.820 align:start position:0% write the letter c because it goes a b c 18:02:44.820 --> 18:02:49.310 align:start position:0% write the letter c because it goes a b c right<18:02:45.660> there<18:02:46.136> are<18:02:46.456> two<18:02:47.456> added<18:02:48.296> so<18:02:48.776> then<18:02:48.900> if<18:02:49.136> I 18:02:49.310 --> 18:02:49.320 align:start position:0% right there are two added so then if I 18:02:49.320 --> 18:02:52.606 align:start position:0% right there are two added so then if I sent<18:02:49.616> this<18:02:49.916> C<18:02:50.220> to<18:02:50.880> someone<18:02:51.116> they<18:02:51.776> know<18:02:51.956> oh<18:02:52.256> I 18:02:52.606 --> 18:02:52.616 align:start position:0% sent this C to someone they know oh I 18:02:52.616 --> 18:02:54.170 align:start position:0% sent this C to someone they know oh I can<18:02:52.740> subtract<18:02:53.160> two<18:02:53.400> from<18:02:53.580> it<18:02:53.756> and<18:02:53.880> that's<18:02:54.000> my 18:02:54.170 --> 18:02:54.180 align:start position:0% can subtract two from it and that's my 18:02:54.180 --> 18:02:56.330 align:start position:0% can subtract two from it and that's my Caesar<18:02:54.480> Cipher<18:02:54.900> now<18:02:55.500> we<18:02:55.680> also<18:02:55.916> defined 18:02:56.330 --> 18:02:56.340 align:start position:0% Caesar Cipher now we also defined 18:02:56.340 --> 18:02:58.670 align:start position:0% Caesar Cipher now we also defined encryption<18:02:57.240> and<18:02:57.776> encryption<18:02:58.256> is<18:02:58.500> actually 18:02:58.670 --> 18:02:58.680 align:start position:0% encryption and encryption is actually 18:02:58.680 --> 18:03:00.946 align:start position:0% encryption and encryption is actually the<18:02:58.980> process<18:02:59.400> of<18:02:59.820> doing<18:03:00.060> all<18:03:00.360> this<18:03:00.480> we<18:03:00.776> have 18:03:00.946 --> 18:03:00.956 align:start position:0% the process of doing all this we have 18:03:00.956 --> 18:03:03.106 align:start position:0% the process of doing all this we have the<18:03:01.200> code<18:03:01.320> we<18:03:01.616> have<18:03:01.740> the<18:03:01.980> cryptography<18:03:02.636> and 18:03:03.106 --> 18:03:03.116 align:start position:0% the code we have the cryptography and 18:03:03.116 --> 18:03:04.126 align:start position:0% the code we have the cryptography and then<18:03:03.240> what<18:03:03.360> we<18:03:03.480> want<18:03:03.596> to<18:03:03.720> do<18:03:03.776> is<18:03:03.956> actually 18:03:04.126 --> 18:03:04.136 align:start position:0% then what we want to do is actually 18:03:04.136 --> 18:03:06.470 align:start position:0% then what we want to do is actually encrypt<18:03:04.680> the<18:03:04.860> data<18:03:05.160> using<18:03:05.520> it<18:03:05.636> now<18:03:06.060> we<18:03:06.296> talked 18:03:06.470 --> 18:03:06.480 align:start position:0% encrypt the data using it now we talked 18:03:06.480 --> 18:03:07.850 align:start position:0% encrypt the data using it now we talked about<18:03:06.540> two<18:03:06.776> different<18:03:06.956> things<18:03:07.200> plain<18:03:07.680> text 18:03:07.850 --> 18:03:07.860 align:start position:0% about two different things plain text 18:03:07.860 --> 18:03:10.550 align:start position:0% about two different things plain text and<18:03:08.096> ciphertext<18:03:08.636> plain<18:03:09.416> text<18:03:09.596> is<18:03:09.956> the<18:03:10.200> data 18:03:10.550 --> 18:03:10.560 align:start position:0% and ciphertext plain text is the data 18:03:10.560 --> 18:03:12.126 align:start position:0% and ciphertext plain text is the data before<18:03:10.796> we<18:03:11.160> apply<18:03:11.400> the<18:03:11.580> code<18:03:11.756> to<18:03:12.000> it 18:03:12.126 --> 18:03:12.136 align:start position:0% before we apply the code to it 18:03:12.136 --> 18:03:15.286 align:start position:0% before we apply the code to it ciphertext<18:03:13.136> is<18:03:13.380> after<18:03:13.616> we've<18:03:14.096> applied<18:03:15.000> it<18:03:15.116> to 18:03:15.286 --> 18:03:15.296 align:start position:0% ciphertext is after we've applied it to 18:03:15.296 --> 18:03:17.390 align:start position:0% ciphertext is after we've applied it to it<18:03:15.480> so<18:03:16.136> plain<18:03:16.500> text<18:03:16.680> anyone<18:03:17.096> can<18:03:17.220> read 18:03:17.390 --> 18:03:17.400 align:start position:0% it so plain text anyone can read 18:03:17.400 --> 18:03:19.426 align:start position:0% it so plain text anyone can read ciphertext<18:03:18.060> only<18:03:18.240> those<18:03:18.480> people<18:03:18.720> with<18:03:19.136> the 18:03:19.426 --> 18:03:19.436 align:start position:0% ciphertext only those people with the 18:03:19.436 --> 18:03:22.070 align:start position:0% ciphertext only those people with the code<18:03:19.616> breaker<18:03:20.096> can<18:03:20.276> read<18:03:20.456> or<18:03:20.820> the<18:03:21.116> keys<18:03:21.480> we 18:03:22.070 --> 18:03:22.080 align:start position:0% code breaker can read or the keys we 18:03:22.080 --> 18:03:23.626 align:start position:0% code breaker can read or the keys we also<18:03:22.256> talked<18:03:22.380> about<18:03:22.436> that<18:03:22.616> in<18:03:22.796> a<18:03:23.220> public<18:03:23.340> and 18:03:23.626 --> 18:03:23.636 align:start position:0% also talked about that in a public and 18:03:23.636 --> 18:03:26.990 align:start position:0% also talked about that in a public and private<18:03:24.000> key<18:03:24.180> public<18:03:25.020> keys<18:03:25.616> are<18:03:26.160> sent<18:03:26.456> to 18:03:26.990 --> 18:03:27.000 align:start position:0% private key public keys are sent to 18:03:27.000 --> 18:03:29.926 align:start position:0% private key public keys are sent to everyone<18:03:27.240> so<18:03:27.900> everyone<18:03:28.136> has<18:03:28.560> access<18:03:28.916> to<18:03:29.276> them 18:03:29.926 --> 18:03:29.936 align:start position:0% everyone so everyone has access to them 18:03:29.936 --> 18:03:32.990 align:start position:0% everyone so everyone has access to them private<18:03:30.720> keys<18:03:31.136> are<18:03:31.616> only<18:03:31.860> held<18:03:32.276> by<18:03:32.520> one<18:03:32.756> party 18:03:32.990 --> 18:03:33.000 align:start position:0% private keys are only held by one party 18:03:33.000 --> 18:03:36.350 align:start position:0% private keys are only held by one party they<18:03:33.840> are<18:03:34.020> private<18:03:34.796> now<18:03:35.340> generally<18:03:35.880> speaking 18:03:36.350 --> 18:03:36.360 align:start position:0% they are private now generally speaking 18:03:36.360 --> 18:03:40.550 align:start position:0% they are private now generally speaking public<18:03:36.660> keys<18:03:37.136> are<18:03:37.500> used<18:03:37.740> to<18:03:38.160> encrypt 18:03:40.550 --> 18:03:40.560 align:start position:0% public keys are used to encrypt 18:03:40.560 --> 18:03:42.946 align:start position:0% public keys are used to encrypt whereas<18:03:41.220> private<18:03:41.636> keys<18:03:41.936> are<18:03:42.116> used<18:03:42.240> to<18:03:42.480> decrypt 18:03:42.946 --> 18:03:42.956 align:start position:0% whereas private keys are used to decrypt 18:03:42.956 --> 18:03:46.850 align:start position:0% whereas private keys are used to decrypt so<18:03:43.560> anyone<18:03:43.916> can<18:03:44.276> make<18:03:44.840> uh<18:03:45.840> a<18:03:46.020> message<18:03:46.380> that<18:03:46.740> is 18:03:46.850 --> 18:03:46.860 align:start position:0% so anyone can make uh a message that is 18:03:46.860 --> 18:03:48.586 align:start position:0% so anyone can make uh a message that is in<18:03:46.980> ciphertext<18:03:47.580> but<18:03:47.820> only<18:03:47.936> the<18:03:48.180> people<18:03:48.360> with 18:03:48.586 --> 18:03:48.596 align:start position:0% in ciphertext but only the people with 18:03:48.596 --> 18:03:50.626 align:start position:0% in ciphertext but only the people with the<18:03:48.776> private<18:03:49.020> keys<18:03:49.320> can<18:03:49.560> actually<18:03:49.740> decipher 18:03:50.626 --> 18:03:50.636 align:start position:0% the private keys can actually decipher 18:03:50.636 --> 18:03:51.350 align:start position:0% the private keys can actually decipher it 18:03:51.350 --> 18:03:51.360 align:start position:0% it 18:03:51.360 --> 18:03:52.970 align:start position:0% it and<18:03:51.776> then<18:03:51.840> we<18:03:52.020> talked<18:03:52.320> about<18:03:52.436> some<18:03:52.740> like 18:03:52.970 --> 18:03:52.980 align:start position:0% and then we talked about some like 18:03:52.980 --> 18:03:55.310 align:start position:0% and then we talked about some like examples<18:03:53.456> of<18:03:53.700> using<18:03:54.060> this<18:03:54.180> for<18:03:54.840> instance<18:03:55.080> not 18:03:55.310 --> 18:03:55.320 align:start position:0% examples of using this for instance not 18:03:55.320 --> 18:03:57.230 align:start position:0% examples of using this for instance not only<18:03:55.436> the<18:03:55.560> Caesar<18:03:55.916> and<18:03:56.040> the<18:03:56.160> Navajo<18:03:56.580> but<18:03:57.060> we 18:03:57.230 --> 18:03:57.240 align:start position:0% only the Caesar and the Navajo but we 18:03:57.240 --> 18:03:58.850 align:start position:0% only the Caesar and the Navajo but we also<18:03:57.540> talked<18:03:57.840> about<18:03:57.900> wanting<18:03:58.320> to<18:03:58.436> use<18:03:58.500> it<18:03:58.680> for 18:03:58.850 --> 18:03:58.860 align:start position:0% also talked about wanting to use it for 18:03:58.860 --> 18:04:01.426 align:start position:0% also talked about wanting to use it for Social<18:03:59.096> Security<18:03:59.340> numbers<18:04:00.136> passwords<18:04:01.136> are<18:04:01.256> a 18:04:01.426 --> 18:04:01.436 align:start position:0% Social Security numbers passwords are a 18:04:01.436 --> 18:04:02.626 align:start position:0% Social Security numbers passwords are a big<18:04:01.616> one 18:04:02.626 --> 18:04:02.636 align:start position:0% big one 18:04:02.636 --> 18:04:04.906 align:start position:0% big one and<18:04:03.116> of<18:04:03.240> course<18:04:03.360> today's<18:04:03.720> market<18:04:04.436> with<18:04:04.740> all 18:04:04.906 --> 18:04:04.916 align:start position:0% and of course today's market with all 18:04:04.916 --> 18:04:07.310 align:start position:0% and of course today's market with all the<18:04:05.040> finances<18:04:05.456> going<18:04:05.756> on<18:04:05.936> bank<18:04:06.660> and<18:04:07.020> credit 18:04:07.310 --> 18:04:07.320 align:start position:0% the finances going on bank and credit 18:04:07.320 --> 18:04:14.190 align:start position:0% the finances going on bank and credit card<18:04:07.680> information 18:04:14.190 --> 18:04:14.200 align:start position:0% 18:04:14.200 --> 18:04:34.210 align:start position:0% [Music] 18:04:34.210 --> 18:04:34.220 align:start position:0% 18:04:34.220 --> 18:04:40.070 align:start position:0% network<18:04:35.220> security<18:04:36.080> IDs<18:04:37.080> IPS<18:04:37.796> implementation 18:04:40.070 --> 18:04:40.080 align:start position:0% network security IDs IPS implementation 18:04:40.080 --> 18:04:41.870 align:start position:0% network security IDs IPS implementation in<18:04:40.616> the<18:04:40.740> previous<18:04:40.860> lesson<18:04:41.340> we<18:04:41.520> talked<18:04:41.820> about 18:04:41.870 --> 18:04:41.880 align:start position:0% in the previous lesson we talked about 18:04:41.880 --> 18:04:43.670 align:start position:0% in the previous lesson we talked about different<18:04:42.180> aspects<18:04:42.900> of<18:04:43.080> network<18:04:43.320> security 18:04:43.670 --> 18:04:43.680 align:start position:0% different aspects of network security 18:04:43.680 --> 18:04:46.126 align:start position:0% different aspects of network security now<18:04:44.520> because<18:04:44.820> this<18:04:45.360> topic<18:04:45.720> is<18:04:45.956> so 18:04:46.126 --> 18:04:46.136 align:start position:0% now because this topic is so 18:04:46.136 --> 18:04:48.050 align:start position:0% now because this topic is so encompassing<18:04:46.616> we're<18:04:46.916> going<18:04:47.040> to<18:04:47.220> continue<18:04:47.520> on 18:04:48.050 --> 18:04:48.060 align:start position:0% encompassing we're going to continue on 18:04:48.060 --> 18:04:50.510 align:start position:0% encompassing we're going to continue on with<18:04:48.660> this<18:04:48.900> network<18:04:49.200> security<18:04:49.560> in<18:04:50.340> this 18:04:50.510 --> 18:04:50.520 align:start position:0% with this network security in this 18:04:50.520 --> 18:04:51.830 align:start position:0% with this network security in this lesson<18:04:50.820> where<18:04:51.180> we're<18:04:51.360> going<18:04:51.480> to<18:04:51.540> focus 18:04:51.830 --> 18:04:51.840 align:start position:0% lesson where we're going to focus 18:04:51.840 --> 18:04:54.170 align:start position:0% lesson where we're going to focus specifically<18:04:52.500> on<18:04:53.160> two<18:04:53.456> types<18:04:53.820> of<18:04:53.936> security 18:04:54.170 --> 18:04:54.180 align:start position:0% specifically on two types of security 18:04:54.180 --> 18:04:56.570 align:start position:0% specifically on two types of security one<18:04:54.900> is<18:04:55.136> IP<18:04:55.500> security<18:04:55.796> which<18:04:56.220> we'll<18:04:56.400> talk 18:04:56.570 --> 18:04:56.580 align:start position:0% one is IP security which we'll talk 18:04:56.580 --> 18:04:59.086 align:start position:0% one is IP security which we'll talk about<18:04:56.756> in<18:04:57.360> the<18:04:57.596> next<18:04:57.776> module<18:04:58.320> and<18:04:58.796> in<18:04:58.916> this 18:04:59.086 --> 18:04:59.096 align:start position:0% about in the next module and in this 18:04:59.096 --> 18:04:59.870 align:start position:0% about in the next module and in this module<18:04:59.340> we're<18:04:59.456> going<18:04:59.580> to<18:04:59.636> talk<18:04:59.756> about 18:04:59.870 --> 18:04:59.880 align:start position:0% module we're going to talk about 18:04:59.880 --> 18:05:02.266 align:start position:0% module we're going to talk about intrusion<18:05:00.660> detection<18:05:01.020> prevention<18:05:01.680> systems 18:05:02.266 --> 18:05:02.276 align:start position:0% intrusion detection prevention systems 18:05:02.276 --> 18:05:06.230 align:start position:0% intrusion detection prevention systems otherwise<18:05:02.936> known<18:05:03.180> as<18:05:03.416> IDs<18:05:04.136> and<18:05:04.680> IPS<18:05:05.116> these<18:05:06.116> are 18:05:06.230 --> 18:05:06.240 align:start position:0% otherwise known as IDs and IPS these are 18:05:06.240 --> 18:05:07.670 align:start position:0% otherwise known as IDs and IPS these are pretty<18:05:06.416> important<18:05:06.776> and<18:05:06.900> come<18:05:07.136> up<18:05:07.256> a<18:05:07.380> bit<18:05:07.500> on 18:05:07.670 --> 18:05:07.680 align:start position:0% pretty important and come up a bit on 18:05:07.680 --> 18:05:09.170 align:start position:0% pretty important and come up a bit on the<18:05:07.740> network<18:05:07.860> plus<18:05:08.220> exam<18:05:08.580> which<18:05:08.756> is<18:05:08.880> why<18:05:09.060> I 18:05:09.170 --> 18:05:09.180 align:start position:0% the network plus exam which is why I 18:05:09.180 --> 18:05:11.086 align:start position:0% the network plus exam which is why I want<18:05:09.360> to<18:05:09.480> commit<18:05:09.776> an<18:05:10.020> entire<18:05:10.320> module<18:05:10.680> to<18:05:10.916> them 18:05:11.086 --> 18:05:11.096 align:start position:0% want to commit an entire module to them 18:05:11.096 --> 18:05:13.670 align:start position:0% want to commit an entire module to them so<18:05:12.060> we're<18:05:12.360> going<18:05:12.480> to<18:05:12.596> begin<18:05:12.720> by<18:05:13.080> talking<18:05:13.320> about 18:05:13.670 --> 18:05:13.680 align:start position:0% so we're going to begin by talking about 18:05:13.680 --> 18:05:18.606 align:start position:0% so we're going to begin by talking about an<18:05:14.160> IDs<18:05:14.756> or<18:05:15.480> intrusion 18:05:18.606 --> 18:05:18.616 align:start position:0% 18:05:18.616 --> 18:05:22.246 align:start position:0% detection<18:05:19.616> system 18:05:22.246 --> 18:05:22.256 align:start position:0% 18:05:22.256 --> 18:05:24.710 align:start position:0% notice<18:05:23.040> the<18:05:23.400> D<18:05:23.700> there<18:05:24.060> and<18:05:24.480> we're<18:05:24.596> going<18:05:24.720> to 18:05:24.710 --> 18:05:24.720 align:start position:0% notice the D there and we're going to 18:05:24.720 --> 18:05:26.266 align:start position:0% notice the D there and we're going to talk<18:05:24.900> about<18:05:25.020> the<18:05:25.320> two<18:05:25.500> different<18:05:25.616> types<18:05:26.096> of 18:05:26.266 --> 18:05:26.276 align:start position:0% talk about the two different types of 18:05:26.276 --> 18:05:30.106 align:start position:0% talk about the two different types of IDs<18:05:26.756> that<18:05:27.116> exist<18:05:27.360> one<18:05:28.080> is<18:05:28.256> behavior<18:05:28.860> based<18:05:29.700> and 18:05:30.106 --> 18:05:30.116 align:start position:0% IDs that exist one is behavior based and 18:05:30.116 --> 18:05:32.210 align:start position:0% IDs that exist one is behavior based and one<18:05:30.296> is<18:05:30.416> signature<18:05:30.956> based<18:05:31.320> we'll<18:05:31.916> discuss 18:05:32.210 --> 18:05:32.220 align:start position:0% one is signature based we'll discuss 18:05:32.220 --> 18:05:34.370 align:start position:0% one is signature based we'll discuss what<18:05:32.456> this<18:05:32.636> means<18:05:32.936> in<18:05:33.116> a<18:05:33.296> bit<18:05:33.416> we're<18:05:34.136> also 18:05:34.370 --> 18:05:34.380 align:start position:0% what this means in a bit we're also 18:05:34.380 --> 18:05:37.010 align:start position:0% what this means in a bit we're also going<18:05:34.500> to<18:05:34.560> Define<18:05:34.740> and<18:05:35.096> discuss<18:05:35.596> ips's<18:05:36.596> the 18:05:37.010 --> 18:05:37.020 align:start position:0% going to Define and discuss ips's the 18:05:37.020 --> 18:05:39.170 align:start position:0% going to Define and discuss ips's the difference<18:05:37.136> between<18:05:37.380> an<18:05:37.616> IPS<18:05:37.916> and<18:05:38.220> an<18:05:38.340> IDs<18:05:38.820> is 18:05:39.170 --> 18:05:39.180 align:start position:0% difference between an IPS and an IDs is 18:05:39.180 --> 18:05:41.330 align:start position:0% difference between an IPS and an IDs is where<18:05:39.360> an<18:05:39.540> IDs<18:05:40.020> is<18:05:40.200> an<18:05:40.320> intrusion<18:05:40.796> detection 18:05:41.330 --> 18:05:41.340 align:start position:0% where an IDs is an intrusion detection 18:05:41.340 --> 18:05:44.946 align:start position:0% where an IDs is an intrusion detection system<18:05:41.756> and<18:05:42.596> IPS<18:05:43.020> is<18:05:43.916> an<18:05:44.160> intrusion 18:05:44.946 --> 18:05:44.956 align:start position:0% system and IPS is an intrusion 18:05:44.956 --> 18:05:48.106 align:start position:0% system and IPS is an intrusion prevention<18:05:45.956> system<18:05:46.740> notice<18:05:47.700> the<18:05:47.936> difference 18:05:48.106 --> 18:05:48.116 align:start position:0% prevention system notice the difference 18:05:48.116 --> 18:05:50.446 align:start position:0% prevention system notice the difference between<18:05:48.540> the<18:05:48.776> D<18:05:48.900> and<18:05:49.136> the<18:05:49.256> P<18:05:49.436> one<18:05:50.040> simply 18:05:50.446 --> 18:05:50.456 align:start position:0% between the D and the P one simply 18:05:50.456 --> 18:05:52.190 align:start position:0% between the D and the P one simply notifies<18:05:51.060> you<18:05:51.240> the<18:05:51.540> other<18:05:51.660> will<18:05:51.956> actually 18:05:52.190 --> 18:05:52.200 align:start position:0% notifies you the other will actually 18:05:52.200 --> 18:05:54.890 align:start position:0% notifies you the other will actually prevent<18:05:52.860> we're<18:05:53.700> then<18:05:53.936> going<18:05:54.180> to<18:05:54.360> discuss<18:05:54.596> the 18:05:54.890 --> 18:05:54.900 align:start position:0% prevent we're then going to discuss the 18:05:54.900 --> 18:05:57.766 align:start position:0% prevent we're then going to discuss the importance<18:05:55.200> of<18:05:55.436> having<18:05:55.616> an<18:05:55.980> IDs<18:05:56.456> IPS<18:05:56.936> and<18:05:57.660> in 18:05:57.766 --> 18:05:57.776 align:start position:0% importance of having an IDs IPS and in 18:05:57.776 --> 18:05:59.990 align:start position:0% importance of having an IDs IPS and in some<18:05:57.956> cases<18:05:58.200> we<18:05:58.500> will<18:05:58.680> have<18:05:58.916> devices<18:05:59.340> that<18:05:59.820> do 18:05:59.990 --> 18:06:00.000 align:start position:0% some cases we will have devices that do 18:06:00.000 --> 18:06:01.246 align:start position:0% some cases we will have devices that do both 18:06:01.246 --> 18:06:01.256 align:start position:0% both 18:06:01.256 --> 18:06:03.286 align:start position:0% both and<18:06:01.980> we're<18:06:02.220> then<18:06:02.400> going<18:06:02.580> to<18:06:02.636> discuss<18:06:03.000> very 18:06:03.286 --> 18:06:03.296 align:start position:0% and we're then going to discuss very 18:06:03.296 --> 18:06:05.810 align:start position:0% and we're then going to discuss very briefly<18:06:03.720> implementation<18:06:04.436> now<18:06:05.340> of<18:06:05.636> course 18:06:05.810 --> 18:06:05.820 align:start position:0% briefly implementation now of course 18:06:05.820 --> 18:06:07.550 align:start position:0% briefly implementation now of course just<18:06:06.296> like<18:06:06.480> anything<18:06:06.720> we're<18:06:07.080> going<18:06:07.200> to<18:06:07.320> look 18:06:07.550 --> 18:06:07.560 align:start position:0% just like anything we're going to look 18:06:07.560 --> 18:06:09.890 align:start position:0% just like anything we're going to look at<18:06:07.680> this<18:06:07.860> from<18:06:08.160> a<18:06:08.456> mile<18:06:08.756> high<18:06:09.116> view<18:06:09.360> so<18:06:09.660> this 18:06:09.890 --> 18:06:09.900 align:start position:0% at this from a mile high view so this 18:06:09.900 --> 18:06:11.570 align:start position:0% at this from a mile high view so this isn't<18:06:10.136> the<18:06:10.380> in-depth<18:06:10.860> the<18:06:10.980> detailed<18:06:11.400> version 18:06:11.570 --> 18:06:11.580 align:start position:0% isn't the in-depth the detailed version 18:06:11.580 --> 18:06:14.870 align:start position:0% isn't the in-depth the detailed version this<18:06:12.116> is<18:06:12.180> the<18:06:12.416> broad<18:06:12.660> overview<18:06:13.456> now<18:06:14.456> an 18:06:14.870 --> 18:06:14.880 align:start position:0% this is the broad overview now an 18:06:14.880 --> 18:06:17.210 align:start position:0% this is the broad overview now an intrusion<18:06:15.360> detection<18:06:15.660> system<18:06:16.080> is<18:06:16.616> software 18:06:17.210 --> 18:06:17.220 align:start position:0% intrusion detection system is software 18:06:17.220 --> 18:06:20.690 align:start position:0% intrusion detection system is software or<18:06:17.756> network<18:06:18.060> device<18:06:18.416> that's<18:06:19.200> used<18:06:19.560> to<18:06:19.796> detect 18:06:20.690 --> 18:06:20.700 align:start position:0% or network device that's used to detect 18:06:20.700 --> 18:06:22.990 align:start position:0% or network device that's used to detect again<18:06:21.060> remember<18:06:21.360> that<18:06:21.660> word<18:06:21.900> d<18:06:22.256> detect 18:06:22.990 --> 18:06:23.000 align:start position:0% again remember that word d detect 18:06:23.000 --> 18:06:25.490 align:start position:0% again remember that word d detect attacks<18:06:24.000> or<18:06:24.416> intrusions<18:06:24.900> that<18:06:25.080> are<18:06:25.200> made<18:06:25.320> on 18:06:25.490 --> 18:06:25.500 align:start position:0% attacks or intrusions that are made on 18:06:25.500 --> 18:06:27.890 align:start position:0% attacks or intrusions that are made on the<18:06:25.616> network<18:06:25.820> the<18:06:26.820> attacks<18:06:27.240> that<18:06:27.360> it<18:06:27.480> detects 18:06:27.890 --> 18:06:27.900 align:start position:0% the network the attacks that it detects 18:06:27.900 --> 18:06:29.690 align:start position:0% the network the attacks that it detects are<18:06:28.136> then<18:06:28.320> reported<18:06:28.916> to<18:06:29.160> either<18:06:29.340> the 18:06:29.690 --> 18:06:29.700 align:start position:0% are then reported to either the 18:06:29.700 --> 18:06:33.350 align:start position:0% are then reported to either the administrator<18:06:30.240> or<18:06:31.200> to<18:06:31.796> a<18:06:32.040> threat<18:06:32.400> log<18:06:32.700> sort<18:06:33.296> of 18:06:33.350 --> 18:06:33.360 align:start position:0% administrator or to a threat log sort of 18:06:33.360 --> 18:06:36.050 align:start position:0% administrator or to a threat log sort of like<18:06:33.480> the<18:06:33.720> Event<18:06:33.840> Viewer<18:06:34.320> if<18:06:35.040> it<18:06:35.340> logs<18:06:35.880> the 18:06:36.050 --> 18:06:36.060 align:start position:0% like the Event Viewer if it logs the 18:06:36.060 --> 18:06:38.446 align:start position:0% like the Event Viewer if it logs the information<18:06:36.240> first<18:06:36.956> it<18:06:37.560> then<18:06:37.740> alerts<18:06:38.276> the 18:06:38.446 --> 18:06:38.456 align:start position:0% information first it then alerts the 18:06:38.456 --> 18:06:41.086 align:start position:0% information first it then alerts the administrator<18:06:39.020> so<18:06:40.020> the<18:06:40.380> administrator<18:06:40.796> can 18:06:41.086 --> 18:06:41.096 align:start position:0% administrator so the administrator can 18:06:41.096 --> 18:06:44.266 align:start position:0% administrator so the administrator can look<18:06:41.276> into<18:06:41.580> the<18:06:41.936> issue<18:06:42.240> now<18:06:42.956> while<18:06:43.200> IDs<18:06:43.796> are<18:06:44.096> up 18:06:44.266 --> 18:06:44.276 align:start position:0% look into the issue now while IDs are up 18:06:44.276 --> 18:06:46.246 align:start position:0% look into the issue now while IDs are up to<18:06:44.400> date<18:06:44.520> and<18:06:44.756> make<18:06:45.000> alerts<18:06:45.480> as<18:06:45.720> soon<18:06:45.956> as<18:06:46.080> an 18:06:46.246 --> 18:06:46.256 align:start position:0% to date and make alerts as soon as an 18:06:46.256 --> 18:06:48.350 align:start position:0% to date and make alerts as soon as an attack<18:06:46.436> occurs<18:06:47.040> they<18:06:47.520> are<18:06:47.700> still<18:06:47.820> referred<18:06:48.180> to 18:06:48.350 --> 18:06:48.360 align:start position:0% attack occurs they are still referred to 18:06:48.360 --> 18:06:51.586 align:start position:0% attack occurs they are still referred to as<18:06:48.860> passive<18:06:49.860> the<18:06:50.400> reason<18:06:50.580> they<18:06:50.820> are<18:06:51.000> called<18:06:51.180> a 18:06:51.586 --> 18:06:51.596 align:start position:0% as passive the reason they are called a 18:06:51.596 --> 18:06:53.266 align:start position:0% as passive the reason they are called a passive<18:06:52.020> security<18:06:52.256> system<18:06:52.616> is<18:06:52.860> because<18:06:53.040> they 18:06:53.266 --> 18:06:53.276 align:start position:0% passive security system is because they 18:06:53.276 --> 18:06:55.670 align:start position:0% passive security system is because they don't<18:06:53.456> do<18:06:53.936> anything<18:06:54.240> to<18:06:54.720> actually<18:06:54.900> prevent 18:06:55.670 --> 18:06:55.680 align:start position:0% don't do anything to actually prevent 18:06:55.680 --> 18:06:58.850 align:start position:0% don't do anything to actually prevent the<18:06:56.520> intrusion<18:06:57.060> from<18:06:57.596> stopping<18:06:58.080> all<18:06:58.436> they<18:06:58.616> do 18:06:58.850 --> 18:06:58.860 align:start position:0% the intrusion from stopping all they do 18:06:58.860 --> 18:07:02.150 align:start position:0% the intrusion from stopping all they do is<18:06:59.756> they<18:07:00.240> passively<18:07:01.200> notice<18:07:01.860> that<18:07:01.980> it's 18:07:02.150 --> 18:07:02.160 align:start position:0% is they passively notice that it's 18:07:02.160 --> 18:07:04.370 align:start position:0% is they passively notice that it's occurring<18:07:02.580> this<18:07:03.116> is<18:07:03.240> because<18:07:03.480> again<18:07:03.900> they 18:07:04.370 --> 18:07:04.380 align:start position:0% occurring this is because again they 18:07:04.380 --> 18:07:06.530 align:start position:0% occurring this is because again they merely<18:07:04.740> a<18:07:04.916> detect<18:07:05.220> the<18:07:05.400> attack<18:07:05.700> they<18:07:06.296> don't<18:07:06.416> do 18:07:06.530 --> 18:07:06.540 align:start position:0% merely a detect the attack they don't do 18:07:06.540 --> 18:07:08.570 align:start position:0% merely a detect the attack they don't do anything<18:07:06.720> to<18:07:06.956> prevent<18:07:07.256> or<18:07:07.500> combat<18:07:07.860> it<18:07:08.040> now 18:07:08.570 --> 18:07:08.580 align:start position:0% anything to prevent or combat it now 18:07:08.580 --> 18:07:10.010 align:start position:0% anything to prevent or combat it now there<18:07:08.756> are<18:07:08.880> a<18:07:08.936> few<18:07:09.000> different<18:07:09.180> types<18:07:09.776> of 18:07:10.010 --> 18:07:10.020 align:start position:0% there are a few different types of 18:07:10.020 --> 18:07:11.990 align:start position:0% there are a few different types of intrusion<18:07:10.560> detection<18:07:10.916> systems<18:07:11.456> but<18:07:11.756> I<18:07:11.880> want 18:07:11.990 --> 18:07:12.000 align:start position:0% intrusion detection systems but I want 18:07:12.000 --> 18:07:13.606 align:start position:0% intrusion detection systems but I want to<18:07:12.116> focus<18:07:12.360> specifically<18:07:12.956> on<18:07:13.256> two<18:07:13.436> different 18:07:13.606 --> 18:07:13.616 align:start position:0% to focus specifically on two different 18:07:13.616 --> 18:07:15.970 align:start position:0% to focus specifically on two different types<18:07:14.096> the<18:07:14.820> first<18:07:14.936> is<18:07:15.296> called<18:07:15.480> a 18:07:15.970 --> 18:07:15.980 align:start position:0% types the first is called a 18:07:15.980 --> 18:07:19.010 align:start position:0% types the first is called a behavior-based<18:07:16.980> system<18:07:17.296> this<18:07:18.296> makes<18:07:18.480> alerts 18:07:19.010 --> 18:07:19.020 align:start position:0% behavior-based system this makes alerts 18:07:19.020 --> 18:07:21.670 align:start position:0% behavior-based system this makes alerts and<18:07:19.136> reports<18:07:19.500> of<18:07:19.680> attacks<18:07:20.160> based<18:07:20.880> on<18:07:21.116> the 18:07:21.670 --> 18:07:21.680 align:start position:0% and reports of attacks based on the 18:07:21.680 --> 18:07:25.010 align:start position:0% and reports of attacks based on the behavior<18:07:22.756> that<18:07:23.756> they<18:07:23.936> deem<18:07:24.180> to<18:07:24.296> be<18:07:24.480> suspicious 18:07:25.010 --> 18:07:25.020 align:start position:0% behavior that they deem to be suspicious 18:07:25.020 --> 18:07:27.470 align:start position:0% behavior that they deem to be suspicious or<18:07:25.436> out<18:07:25.616> of<18:07:25.796> the<18:07:25.860> ordinary<18:07:26.276> these<18:07:27.060> unusual 18:07:27.470 --> 18:07:27.480 align:start position:0% or out of the ordinary these unusual 18:07:27.480 --> 18:07:30.650 align:start position:0% or out of the ordinary these unusual behaviors<18:07:28.080> can<18:07:28.436> include<18:07:29.000> large<18:07:30.000> amounts<18:07:30.480> of 18:07:30.650 --> 18:07:30.660 align:start position:0% behaviors can include large amounts of 18:07:30.660 --> 18:07:35.030 align:start position:0% behaviors can include large amounts of traffic<18:07:31.340> policies<18:07:32.340> being<18:07:32.756> violated 18:07:35.030 --> 18:07:35.040 align:start position:0% traffic policies being violated 18:07:35.040 --> 18:07:37.906 align:start position:0% traffic policies being violated um<18:07:35.096> and<18:07:35.636> even<18:07:35.820> people<18:07:36.180> attempting<18:07:36.900> to<18:07:37.380> access 18:07:37.906 --> 18:07:37.916 align:start position:0% um and even people attempting to access 18:07:37.916 --> 18:07:42.286 align:start position:0% um and even people attempting to access things<18:07:38.636> that<18:07:39.116> they're<18:07:39.240> not<18:07:39.480> supposed<18:07:39.660> to 18:07:42.286 --> 18:07:42.296 align:start position:0% 18:07:42.296 --> 18:07:45.170 align:start position:0% now<18:07:43.136> a<18:07:43.380> signature-based<18:07:44.160> system<18:07:44.340> detects<18:07:45.000> the 18:07:45.170 --> 18:07:45.180 align:start position:0% now a signature-based system detects the 18:07:45.180 --> 18:07:47.990 align:start position:0% now a signature-based system detects the Rest<18:07:45.360> by<18:07:46.020> reading<18:07:46.796> their<18:07:47.040> attack<18:07:47.220> signatures 18:07:47.990 --> 18:07:48.000 align:start position:0% Rest by reading their attack signatures 18:07:48.000 --> 18:07:51.946 align:start position:0% Rest by reading their attack signatures just<18:07:48.720> like<18:07:48.956> a<18:07:49.500> virus<18:07:50.040> scan<18:07:50.400> program<18:07:50.820> has<18:07:51.660> a 18:07:51.946 --> 18:07:51.956 align:start position:0% just like a virus scan program has a 18:07:51.956 --> 18:07:54.710 align:start position:0% just like a virus scan program has a signature<18:07:52.436> remember<18:07:52.796> those<18:07:53.400> data<18:07:54.180> files<18:07:54.480> we 18:07:54.710 --> 18:07:54.720 align:start position:0% signature remember those data files we 18:07:54.720 --> 18:07:56.446 align:start position:0% signature remember those data files we talked<18:07:55.020> about<18:07:55.080> that<18:07:55.680> tells<18:07:55.980> it<18:07:56.040> what<18:07:56.220> to<18:07:56.340> look 18:07:56.446 --> 18:07:56.456 align:start position:0% talked about that tells it what to look 18:07:56.456 --> 18:07:59.746 align:start position:0% talked about that tells it what to look for<18:07:56.636> in<18:07:56.820> a<18:07:57.000> virus<18:07:57.796> intrusion<18:07:58.796> or<18:07:59.456> attack 18:07:59.746 --> 18:07:59.756 align:start position:0% for in a virus intrusion or attack 18:07:59.756 --> 18:08:04.010 align:start position:0% for in a virus intrusion or attack systems<18:08:00.540> have<18:08:01.136> a<18:08:01.320> signature<18:08:01.880> and<18:08:02.880> a<18:08:03.360> signature 18:08:04.010 --> 18:08:04.020 align:start position:0% systems have a signature and a signature 18:08:04.020 --> 18:08:07.190 align:start position:0% systems have a signature and a signature file<18:08:04.380> that<18:08:04.860> they<18:08:05.400> can<18:08:05.580> look<18:08:05.880> at<18:08:06.060> that<18:08:06.660> lines<18:08:07.020> up 18:08:07.190 --> 18:08:07.200 align:start position:0% file that they can look at that lines up 18:08:07.200 --> 18:08:09.830 align:start position:0% file that they can look at that lines up with<18:08:07.740> the<18:08:07.980> signature<18:08:08.456> of<18:08:09.060> an<18:08:09.240> attack<18:08:09.416> or<18:08:09.720> an 18:08:09.830 --> 18:08:09.840 align:start position:0% with the signature of an attack or an 18:08:09.840 --> 18:08:10.906 align:start position:0% with the signature of an attack or an intrusion 18:08:10.906 --> 18:08:10.916 align:start position:0% intrusion 18:08:10.916 --> 18:08:13.550 align:start position:0% intrusion so<18:08:11.636> signature<18:08:12.240> based<18:08:12.596> systems<18:08:13.020> scan<18:08:13.380> the 18:08:13.550 --> 18:08:13.560 align:start position:0% so signature based systems scan the 18:08:13.560 --> 18:08:15.766 align:start position:0% so signature based systems scan the signatures<18:08:13.980> of<18:08:14.276> known<18:08:14.520> attacks<18:08:15.116> and<18:08:15.480> when<18:08:15.660> it 18:08:15.766 --> 18:08:15.776 align:start position:0% signatures of known attacks and when it 18:08:15.776 --> 18:08:17.210 align:start position:0% signatures of known attacks and when it detects<18:08:16.136> one<18:08:16.256> of<18:08:16.436> these<18:08:16.680> signatures 18:08:17.210 --> 18:08:17.220 align:start position:0% detects one of these signatures 18:08:17.220 --> 18:08:19.550 align:start position:0% detects one of these signatures attacking<18:08:17.936> its<18:08:18.240> system<18:08:18.360> it<18:08:18.956> makes<18:08:19.136> an<18:08:19.320> alert 18:08:19.550 --> 18:08:19.560 align:start position:0% attacking its system it makes an alert 18:08:19.560 --> 18:08:21.350 align:start position:0% attacking its system it makes an alert to<18:08:19.740> the<18:08:19.860> administrator<18:08:20.340> or<18:08:20.580> reports<18:08:20.936> it<18:08:21.060> to<18:08:21.180> a 18:08:21.350 --> 18:08:21.360 align:start position:0% to the administrator or reports it to a 18:08:21.360 --> 18:08:24.170 align:start position:0% to the administrator or reports it to a log<18:08:21.480> so<18:08:22.200> again<18:08:22.380> the<18:08:22.916> signature<18:08:23.340> is<18:08:23.636> based<18:08:24.000> on 18:08:24.170 --> 18:08:24.180 align:start position:0% log so again the signature is based on 18:08:24.180 --> 18:08:26.926 align:start position:0% log so again the signature is based on more<18:08:24.540> or<18:08:24.660> less<18:08:24.776> a<18:08:25.080> history<18:08:25.380> whereas<18:08:26.276> behavior 18:08:26.926 --> 18:08:26.936 align:start position:0% more or less a history whereas behavior 18:08:26.936 --> 18:08:28.850 align:start position:0% more or less a history whereas behavior is<18:08:27.360> based<18:08:27.660> on<18:08:27.776> what<18:08:28.020> we<18:08:28.200> see 18:08:28.850 --> 18:08:28.860 align:start position:0% is based on what we see 18:08:28.860 --> 18:08:30.530 align:start position:0% is based on what we see they're<18:08:29.276> looking<18:08:29.580> at<18:08:29.756> two<18:08:29.936> different<18:08:30.060> types 18:08:30.530 --> 18:08:30.540 align:start position:0% they're looking at two different types 18:08:30.540 --> 18:08:32.030 align:start position:0% they're looking at two different types of<18:08:30.596> attacks<18:08:31.020> and<18:08:31.136> there<18:08:31.256> are<18:08:31.380> the<18:08:31.500> pluses<18:08:31.860> and 18:08:32.030 --> 18:08:32.040 align:start position:0% of attacks and there are the pluses and 18:08:32.040 --> 18:08:34.190 align:start position:0% of attacks and there are the pluses and benefits<18:08:32.520> pluses<18:08:33.060> and<18:08:33.240> minuses<18:08:33.660> rather<18:08:33.956> of 18:08:34.190 --> 18:08:34.200 align:start position:0% benefits pluses and minuses rather of 18:08:34.200 --> 18:08:36.650 align:start position:0% benefits pluses and minuses rather of both<18:08:34.380> but<18:08:35.096> you<18:08:35.276> can<18:08:35.400> see<18:08:35.580> Behavior<18:08:36.180> again<18:08:36.416> is 18:08:36.650 --> 18:08:36.660 align:start position:0% both but you can see Behavior again is 18:08:36.660 --> 18:08:38.086 align:start position:0% both but you can see Behavior again is looking<18:08:36.776> at<18:08:37.020> a<18:08:37.136> more<18:08:37.320> all-encompassing 18:08:38.086 --> 18:08:38.096 align:start position:0% looking at a more all-encompassing 18:08:38.096 --> 18:08:40.010 align:start position:0% looking at a more all-encompassing General<18:08:38.400> sort<18:08:38.820> of<18:08:38.936> view<18:08:39.060> where<18:08:39.540> a<18:08:39.720> signature 18:08:40.010 --> 18:08:40.020 align:start position:0% General sort of view where a signature 18:08:40.020 --> 18:08:42.170 align:start position:0% General sort of view where a signature based<18:08:40.380> is<18:08:40.500> looking<18:08:40.680> at<18:08:40.916> previous<18:08:41.340> histories 18:08:42.170 --> 18:08:42.180 align:start position:0% based is looking at previous histories 18:08:42.180 --> 18:08:44.926 align:start position:0% based is looking at previous histories of<18:08:42.360> attacks<18:08:42.776> and<18:08:43.256> aligning<18:08:43.796> the<18:08:44.160> upcoming<18:08:44.756> or 18:08:44.926 --> 18:08:44.936 align:start position:0% of attacks and aligning the upcoming or 18:08:44.936 --> 18:08:46.906 align:start position:0% of attacks and aligning the upcoming or current<18:08:45.116> attack<18:08:45.416> with<18:08:45.776> that 18:08:46.906 --> 18:08:46.916 align:start position:0% current attack with that 18:08:46.916 --> 18:08:50.926 align:start position:0% current attack with that so<18:08:47.820> here's<18:08:48.296> how<18:08:48.480> an<18:08:48.660> IDs<18:08:49.080> Works<18:08:49.500> an<18:08:50.340> attacker 18:08:50.926 --> 18:08:50.936 align:start position:0% so here's how an IDs Works an attacker 18:08:50.936 --> 18:08:52.786 align:start position:0% so here's how an IDs Works an attacker shown<18:08:51.240> on<18:08:51.416> the<18:08:51.540> left<18:08:51.660> sends<18:08:52.500> an<18:08:52.616> attack 18:08:52.786 --> 18:08:52.796 align:start position:0% shown on the left sends an attack 18:08:52.796 --> 18:08:54.830 align:start position:0% shown on the left sends an attack through<18:08:53.160> the<18:08:53.456> internet<18:08:53.580> in<18:08:53.936> order<18:08:54.060> to<18:08:54.480> access 18:08:54.830 --> 18:08:54.840 align:start position:0% through the internet in order to access 18:08:54.840 --> 18:08:57.170 align:start position:0% through the internet in order to access the<18:08:55.500> network<18:08:55.680> of<18:08:55.980> the<18:08:56.160> local<18:08:56.276> app 18:08:57.170 --> 18:08:57.180 align:start position:0% the network of the local app 18:08:57.180 --> 18:08:59.810 align:start position:0% the network of the local app area<18:08:57.596> network<18:08:57.956> the<18:08:58.796> attacks<18:08:59.160> go<18:08:59.340> through<18:08:59.520> the 18:08:59.810 --> 18:08:59.820 align:start position:0% area network the attacks go through the 18:08:59.820 --> 18:09:02.150 align:start position:0% area network the attacks go through the internet<18:09:00.020> towards<18:09:01.020> the<18:09:01.136> network<18:09:01.320> now<18:09:01.916> in 18:09:02.150 --> 18:09:02.160 align:start position:0% internet towards the network now in 18:09:02.160 --> 18:09:04.310 align:start position:0% internet towards the network now in between<18:09:02.276> the<18:09:02.580> internet<18:09:02.700> and<18:09:03.000> the<18:09:03.180> firewall<18:09:03.596> is 18:09:04.310 --> 18:09:04.320 align:start position:0% between the internet and the firewall is 18:09:04.320 --> 18:09:07.906 align:start position:0% between the internet and the firewall is this<18:09:04.616> IDs<18:09:05.360> and<18:09:06.360> what<18:09:06.720> it<18:09:06.900> does<18:09:07.080> is<18:09:07.320> it<18:09:07.500> detects 18:09:07.906 --> 18:09:07.916 align:start position:0% this IDs and what it does is it detects 18:09:07.916 --> 18:09:09.710 align:start position:0% this IDs and what it does is it detects the<18:09:08.096> attacks<18:09:08.456> being<18:09:08.580> made<18:09:08.820> and<18:09:09.060> sends<18:09:09.480> an 18:09:09.710 --> 18:09:09.720 align:start position:0% the attacks being made and sends an 18:09:09.720 --> 18:09:12.406 align:start position:0% the attacks being made and sends an alert<18:09:10.080> to<18:09:10.796> the<18:09:10.980> administrator 18:09:12.406 --> 18:09:12.416 align:start position:0% alert to the administrator 18:09:12.416 --> 18:09:14.626 align:start position:0% alert to the administrator though<18:09:13.320> it<18:09:13.500> doesn't<18:09:13.680> do<18:09:13.860> anything<18:09:14.160> to<18:09:14.456> block 18:09:14.626 --> 18:09:14.636 align:start position:0% though it doesn't do anything to block 18:09:14.636 --> 18:09:16.550 align:start position:0% though it doesn't do anything to block the<18:09:14.936> attack<18:09:15.116> this<18:09:15.480> is<18:09:15.596> okay<18:09:15.720> because<18:09:16.080> the 18:09:16.550 --> 18:09:16.560 align:start position:0% the attack this is okay because the 18:09:16.560 --> 18:09:18.586 align:start position:0% the attack this is okay because the firewall<18:09:17.040> is<18:09:17.340> still<18:09:17.580> set<18:09:17.756> up<18:09:17.880> to<18:09:18.180> handle<18:09:18.416> the 18:09:18.586 --> 18:09:18.596 align:start position:0% firewall is still set up to handle the 18:09:18.596 --> 18:09:21.710 align:start position:0% firewall is still set up to handle the attack<18:09:18.840> so<18:09:19.680> the<18:09:20.040> attacker<18:09:20.456> comes<18:09:20.820> in<18:09:20.936> isn't 18:09:21.710 --> 18:09:21.720 align:start position:0% attack so the attacker comes in isn't 18:09:21.720 --> 18:09:23.746 align:start position:0% attack so the attacker comes in isn't able<18:09:21.956> to<18:09:22.080> access<18:09:22.200> the<18:09:22.616> information 18:09:23.746 --> 18:09:23.756 align:start position:0% able to access the information 18:09:23.756 --> 18:09:26.266 align:start position:0% able to access the information but<18:09:24.540> the<18:09:24.956> administrator<18:09:25.380> is<18:09:25.680> still<18:09:25.860> alerted 18:09:26.266 --> 18:09:26.276 align:start position:0% but the administrator is still alerted 18:09:26.276 --> 18:09:28.670 align:start position:0% but the administrator is still alerted that<18:09:26.456> there<18:09:26.700> is<18:09:26.936> an<18:09:27.296> issue<18:09:27.596> going<18:09:27.776> on<18:09:28.020> and<18:09:28.500> in 18:09:28.670 --> 18:09:28.680 align:start position:0% that there is an issue going on and in 18:09:28.680 --> 18:09:30.710 align:start position:0% that there is an issue going on and in case<18:09:28.796> the<18:09:29.096> attacker<18:09:29.580> begins<18:09:30.000> to<18:09:30.180> double<18:09:30.360> their 18:09:30.710 --> 18:09:30.720 align:start position:0% case the attacker begins to double their 18:09:30.720 --> 18:09:33.106 align:start position:0% case the attacker begins to double their efforts<18:09:31.136> the<18:09:31.916> administrator<18:09:32.456> can<18:09:32.820> sort<18:09:33.000> of 18:09:33.106 --> 18:09:33.116 align:start position:0% efforts the administrator can sort of 18:09:33.116 --> 18:09:35.030 align:start position:0% efforts the administrator can sort of get<18:09:33.360> on<18:09:33.540> it<18:09:33.720> and<18:09:33.956> make<18:09:34.136> sure<18:09:34.320> that<18:09:34.560> nothing<18:09:34.740> is 18:09:35.030 --> 18:09:35.040 align:start position:0% get on it and make sure that nothing is 18:09:35.040 --> 18:09:37.370 align:start position:0% get on it and make sure that nothing is going<18:09:35.220> to<18:09:35.340> get<18:09:35.580> through<18:09:35.756> now<18:09:36.416> similar<18:09:36.840> to<18:09:37.020> the 18:09:37.370 --> 18:09:37.380 align:start position:0% going to get through now similar to the 18:09:37.380 --> 18:09:39.586 align:start position:0% going to get through now similar to the intrusion<18:09:37.860> detection<18:09:38.340> system<18:09:38.756> and<18:09:39.116> intrusion 18:09:39.586 --> 18:09:39.596 align:start position:0% intrusion detection system and intrusion 18:09:39.596 --> 18:09:41.926 align:start position:0% intrusion detection system and intrusion prevention<18:09:40.020> system<18:09:40.436> also<18:09:40.916> detects<18:09:41.456> attacks 18:09:41.926 --> 18:09:41.936 align:start position:0% prevention system also detects attacks 18:09:41.936 --> 18:09:43.990 align:start position:0% prevention system also detects attacks that<18:09:42.180> are<18:09:42.296> targeting<18:09:42.720> the<18:09:42.840> network<18:09:43.020> however 18:09:43.990 --> 18:09:44.000 align:start position:0% that are targeting the network however 18:09:44.000 --> 18:09:46.606 align:start position:0% that are targeting the network however intrusion<18:09:45.000> prevention<18:09:45.660> systems<18:09:46.256> not<18:09:46.436> only 18:09:46.606 --> 18:09:46.616 align:start position:0% intrusion prevention systems not only 18:09:46.616 --> 18:09:50.150 align:start position:0% intrusion prevention systems not only detect<18:09:47.040> the<18:09:47.340> attack<18:09:47.520> they<18:09:48.000> also<18:09:48.860> prevent<18:09:49.860> it 18:09:50.150 --> 18:09:50.160 align:start position:0% detect the attack they also prevent it 18:09:50.160 --> 18:09:52.490 align:start position:0% detect the attack they also prevent it from<18:09:50.700> happening<18:09:51.116> and<18:09:51.660> causing<18:09:52.020> more<18:09:52.200> issues 18:09:52.490 --> 18:09:52.500 align:start position:0% from happening and causing more issues 18:09:52.500 --> 18:09:54.890 align:start position:0% from happening and causing more issues on<18:09:52.680> the<18:09:52.860> network<18:09:52.980> these<18:09:53.820> are<18:09:53.936> considered<18:09:54.480> more 18:09:54.890 --> 18:09:54.900 align:start position:0% on the network these are considered more 18:09:54.900 --> 18:09:56.890 align:start position:0% on the network these are considered more reactive 18:09:56.890 --> 18:09:56.900 align:start position:0% reactive 18:09:56.900 --> 18:10:00.050 align:start position:0% reactive or<18:09:57.900> proactive 18:10:00.050 --> 18:10:00.060 align:start position:0% or proactive 18:10:00.060 --> 18:10:04.010 align:start position:0% or proactive software<18:10:00.900> or<18:10:01.380> Hardware<18:10:01.820> because<18:10:02.820> ips's<18:10:03.660> do<18:10:03.840> a 18:10:04.010 --> 18:10:04.020 align:start position:0% software or Hardware because ips's do a 18:10:04.020 --> 18:10:06.586 align:start position:0% software or Hardware because ips's do a lot<18:10:04.080> more<18:10:04.256> than<18:10:04.500> ids's<18:10:05.340> do<18:10:05.580> they're<18:10:06.116> reactive 18:10:06.586 --> 18:10:06.596 align:start position:0% lot more than ids's do they're reactive 18:10:06.596 --> 18:10:07.906 align:start position:0% lot more than ids's do they're reactive in<18:10:06.720> the<18:10:06.900> sense<18:10:07.020> that<18:10:07.200> if<18:10:07.380> an<18:10:07.500> attack<18:10:07.680> is 18:10:07.906 --> 18:10:07.916 align:start position:0% in the sense that if an attack is 18:10:07.916 --> 18:10:09.286 align:start position:0% in the sense that if an attack is attempted<18:10:08.340> they're<18:10:08.520> going<18:10:08.700> to<18:10:08.756> block<18:10:08.936> it<18:10:09.180> from 18:10:09.286 --> 18:10:09.296 align:start position:0% attempted they're going to block it from 18:10:09.296 --> 18:10:11.926 align:start position:0% attempted they're going to block it from entering<18:10:09.660> the<18:10:09.840> network<18:10:10.020> just<18:10:10.860> like<18:10:11.160> uh<18:10:11.580> a 18:10:11.926 --> 18:10:11.936 align:start position:0% entering the network just like uh a 18:10:11.936 --> 18:10:14.446 align:start position:0% entering the network just like uh a breaker<18:10:12.360> box<18:10:12.540> is<18:10:13.320> going<18:10:13.500> to 18:10:14.446 --> 18:10:14.456 align:start position:0% breaker box is going to 18:10:14.456 --> 18:10:18.170 align:start position:0% breaker box is going to sort<18:10:14.936> of<18:10:15.116> kill<18:10:15.660> the<18:10:15.956> circuit<18:10:16.796> by<18:10:17.400> breaking<18:10:17.880> by 18:10:18.170 --> 18:10:18.180 align:start position:0% sort of kill the circuit by breaking by 18:10:18.180 --> 18:10:19.906 align:start position:0% sort of kill the circuit by breaking by switching<18:10:18.660> the<18:10:18.776> breaker<18:10:19.136> before<18:10:19.436> the 18:10:19.906 --> 18:10:19.916 align:start position:0% switching the breaker before the 18:10:19.916 --> 18:10:21.766 align:start position:0% switching the breaker before the electricity<18:10:20.456> can<18:10:20.700> do<18:10:20.880> any<18:10:21.000> damage<18:10:21.360> to<18:10:21.596> the 18:10:21.766 --> 18:10:21.776 align:start position:0% electricity can do any damage to the 18:10:21.776 --> 18:10:24.766 align:start position:0% electricity can do any damage to the wall<18:10:21.956> a<18:10:22.860> ips's<18:10:23.636> might<18:10:23.936> even<18:10:24.116> kill<18:10:24.480> the 18:10:24.766 --> 18:10:24.776 align:start position:0% wall a ips's might even kill the 18:10:24.776 --> 18:10:26.626 align:start position:0% wall a ips's might even kill the connection<18:10:24.956> out<18:10:25.256> to<18:10:25.436> the<18:10:25.616> internet<18:10:25.740> to<18:10:26.400> stop 18:10:26.626 --> 18:10:26.636 align:start position:0% connection out to the internet to stop 18:10:26.636 --> 18:10:28.730 align:start position:0% connection out to the internet to stop anything<18:10:26.936> from<18:10:27.296> happening<18:10:27.720> they're<18:10:28.380> also 18:10:28.730 --> 18:10:28.740 align:start position:0% anything from happening they're also 18:10:28.740 --> 18:10:30.586 align:start position:0% anything from happening they're also proactive<18:10:29.276> because<18:10:29.456> certain<18:10:29.756> ips's<18:10:30.416> are 18:10:30.586 --> 18:10:30.596 align:start position:0% proactive because certain ips's are 18:10:30.596 --> 18:10:32.570 align:start position:0% proactive because certain ips's are going<18:10:30.660> to<18:10:30.840> seek<18:10:31.256> out<18:10:31.436> attacks<18:10:31.980> and<18:10:32.160> stop<18:10:32.400> them 18:10:32.570 --> 18:10:32.580 align:start position:0% going to seek out attacks and stop them 18:10:32.580 --> 18:10:34.550 align:start position:0% going to seek out attacks and stop them before<18:10:32.880> they<18:10:33.480> even<18:10:33.596> make<18:10:33.840> an<18:10:33.956> attempt<18:10:34.200> on<18:10:34.380> the 18:10:34.550 --> 18:10:34.560 align:start position:0% before they even make an attempt on the 18:10:34.560 --> 18:10:37.730 align:start position:0% before they even make an attempt on the network<18:10:35.000> uh<18:10:36.000> for<18:10:36.240> instance<18:10:36.540> scanning<18:10:37.436> for 18:10:37.730 --> 18:10:37.740 align:start position:0% network uh for instance scanning for 18:10:37.740 --> 18:10:39.586 align:start position:0% network uh for instance scanning for ports<18:10:38.220> in<18:10:38.820> this<18:10:38.936> way<18:10:39.060> an<18:10:39.240> intrusion 18:10:39.586 --> 18:10:39.596 align:start position:0% ports in this way an intrusion 18:10:39.596 --> 18:10:41.990 align:start position:0% ports in this way an intrusion prevention<18:10:40.020> system<18:10:40.380> is<18:10:40.860> more<18:10:41.160> expensive<18:10:41.700> than 18:10:41.990 --> 18:10:42.000 align:start position:0% prevention system is more expensive than 18:10:42.000 --> 18:10:44.030 align:start position:0% prevention system is more expensive than an<18:10:42.180> IDs<18:10:42.596> but<18:10:43.020> this<18:10:43.136> is<18:10:43.200> because<18:10:43.380> it<18:10:43.560> does<18:10:43.740> a<18:10:43.916> lot 18:10:44.030 --> 18:10:44.040 align:start position:0% an IDs but this is because it does a lot 18:10:44.040 --> 18:10:46.070 align:start position:0% an IDs but this is because it does a lot more<18:10:44.340> to<18:10:44.700> provide<18:10:45.116> safety<18:10:45.596> for<18:10:45.776> the<18:10:45.900> network 18:10:46.070 --> 18:10:46.080 align:start position:0% more to provide safety for the network 18:10:46.080 --> 18:10:48.106 align:start position:0% more to provide safety for the network rather<18:10:46.916> than<18:10:47.040> leaving<18:10:47.220> the<18:10:47.456> job<18:10:47.580> in<18:10:47.756> the<18:10:47.880> hands 18:10:48.106 --> 18:10:48.116 align:start position:0% rather than leaving the job in the hands 18:10:48.116 --> 18:10:50.030 align:start position:0% rather than leaving the job in the hands of<18:10:48.180> administrator<18:10:48.840> who<18:10:49.320> perhaps<18:10:49.680> isn't<18:10:49.980> even 18:10:50.030 --> 18:10:50.040 align:start position:0% of administrator who perhaps isn't even 18:10:50.040 --> 18:10:52.550 align:start position:0% of administrator who perhaps isn't even on<18:10:50.340> site<18:10:50.520> at<18:10:50.820> three<18:10:51.000> in<18:10:51.180> the<18:10:51.296> morning<18:10:51.416> the<18:10:52.200> IPS 18:10:52.550 --> 18:10:52.560 align:start position:0% on site at three in the morning the IPS 18:10:52.560 --> 18:10:54.766 align:start position:0% on site at three in the morning the IPS is<18:10:53.160> going<18:10:53.340> to<18:10:53.520> handle<18:10:53.756> the<18:10:53.936> attack<18:10:54.116> and 18:10:54.766 --> 18:10:54.776 align:start position:0% is going to handle the attack and 18:10:54.776 --> 18:10:56.626 align:start position:0% is going to handle the attack and prevent<18:10:55.136> the<18:10:55.560> attacker<18:10:55.980> from<18:10:56.160> connecting<18:10:56.520> to 18:10:56.626 --> 18:10:56.636 align:start position:0% prevent the attacker from connecting to 18:10:56.636 --> 18:10:59.266 align:start position:0% prevent the attacker from connecting to the<18:10:56.820> network<18:10:56.936> and<18:10:57.900> IDs<18:10:58.436> only<18:10:58.680> alerts<18:10:59.160> the 18:10:59.266 --> 18:10:59.276 align:start position:0% the network and IDs only alerts the 18:10:59.276 --> 18:11:01.126 align:start position:0% the network and IDs only alerts the administrator<18:10:59.820> and<18:11:00.240> does<18:11:00.416> nothing<18:11:00.596> about<18:11:00.900> it 18:11:01.126 --> 18:11:01.136 align:start position:0% administrator and does nothing about it 18:11:01.136 --> 18:11:03.830 align:start position:0% administrator and does nothing about it for<18:11:01.860> this<18:11:01.980> reason<18:11:02.220> ips's<18:11:03.060> are<18:11:03.240> more<18:11:03.360> expensive 18:11:03.830 --> 18:11:03.840 align:start position:0% for this reason ips's are more expensive 18:11:03.840 --> 18:11:06.586 align:start position:0% for this reason ips's are more expensive neither<18:11:04.680> system<18:11:04.916> is<18:11:05.220> exactly<18:11:05.636> cheap<18:11:06.060> and 18:11:06.586 --> 18:11:06.596 align:start position:0% neither system is exactly cheap and 18:11:06.596 --> 18:11:09.946 align:start position:0% neither system is exactly cheap and ips's<18:11:07.380> can<18:11:07.680> sell<18:11:07.916> for<18:11:08.276> maybe<18:11:08.520> even<18:11:08.956> fifty 18:11:09.946 --> 18:11:09.956 align:start position:0% ips's can sell for maybe even fifty 18:11:09.956 --> 18:11:12.190 align:start position:0% ips's can sell for maybe even fifty thousand<18:11:10.380> dollars<18:11:10.740> depending<18:11:11.220> on<18:11:11.456> how 18:11:12.190 --> 18:11:12.200 align:start position:0% thousand dollars depending on how 18:11:12.200 --> 18:11:15.286 align:start position:0% thousand dollars depending on how versatile<18:11:13.200> it<18:11:13.380> is<18:11:13.560> so<18:11:14.400> here's<18:11:15.000> what<18:11:15.116> an 18:11:15.286 --> 18:11:15.296 align:start position:0% versatile it is so here's what an 18:11:15.296 --> 18:11:17.170 align:start position:0% versatile it is so here's what an intrusion<18:11:15.720> prevention<18:11:16.136> system<18:11:16.560> looks<18:11:17.096> like 18:11:17.170 --> 18:11:17.180 align:start position:0% intrusion prevention system looks like 18:11:17.180 --> 18:11:19.606 align:start position:0% intrusion prevention system looks like as<18:11:18.180> you<18:11:18.360> can<18:11:18.480> see<18:11:18.596> it's<18:11:18.900> pretty<18:11:19.136> similar<18:11:19.436> to 18:11:19.606 --> 18:11:19.616 align:start position:0% as you can see it's pretty similar to 18:11:19.616 --> 18:11:21.406 align:start position:0% as you can see it's pretty similar to the<18:11:19.796> IDS<18:11:20.276> but<18:11:20.456> with<18:11:20.636> one<18:11:20.880> major<18:11:21.060> difference 18:11:21.406 --> 18:11:21.416 align:start position:0% the IDS but with one major difference 18:11:21.416 --> 18:11:23.330 align:start position:0% the IDS but with one major difference it's<18:11:22.380> that 18:11:23.330 --> 18:11:23.340 align:start position:0% it's that 18:11:23.340 --> 18:11:25.370 align:start position:0% it's that the<18:11:23.700> intrusion<18:11:24.060> prevention<18:11:24.480> system<18:11:24.720> is 18:11:25.370 --> 18:11:25.380 align:start position:0% the intrusion prevention system is 18:11:25.380 --> 18:11:29.086 align:start position:0% the intrusion prevention system is actually<18:11:25.740> going<18:11:26.520> to<18:11:27.000> stop<18:11:27.416> the<18:11:28.136> attack<18:11:28.500> from 18:11:29.086 --> 18:11:29.096 align:start position:0% actually going to stop the attack from 18:11:29.096 --> 18:11:32.210 align:start position:0% actually going to stop the attack from taking<18:11:29.456> place<18:11:29.936> it<18:11:30.776> still<18:11:30.956> sends<18:11:31.500> an<18:11:31.680> alert<18:11:31.980> out 18:11:32.210 --> 18:11:32.220 align:start position:0% taking place it still sends an alert out 18:11:32.220 --> 18:11:33.350 align:start position:0% taking place it still sends an alert out to<18:11:32.400> the<18:11:32.520> administrator<18:11:33.000> so<18:11:33.240> the 18:11:33.350 --> 18:11:33.360 align:start position:0% to the administrator so the 18:11:33.360 --> 18:11:35.086 align:start position:0% to the administrator so the administrator<18:11:33.776> can<18:11:34.080> take<18:11:34.256> care<18:11:34.436> of<18:11:34.560> this<18:11:34.680> but 18:11:35.086 --> 18:11:35.096 align:start position:0% administrator can take care of this but 18:11:35.096 --> 18:11:36.830 align:start position:0% administrator can take care of this but it<18:11:35.276> actually<18:11:35.400> stops<18:11:35.936> the<18:11:36.116> attack<18:11:36.240> in<18:11:36.540> its 18:11:36.830 --> 18:11:36.840 align:start position:0% it actually stops the attack in its 18:11:36.840 --> 18:11:38.746 align:start position:0% it actually stops the attack in its place<18:11:36.956> and<18:11:37.560> makes<18:11:37.680> sure<18:11:37.860> that<18:11:38.160> nothing<18:11:38.456> is 18:11:38.746 --> 18:11:38.756 align:start position:0% place and makes sure that nothing is 18:11:38.756 --> 18:11:41.810 align:start position:0% place and makes sure that nothing is going<18:11:38.936> to<18:11:39.116> occur<18:11:39.416> whereas<18:11:40.256> the<18:11:40.680> IDS<18:11:41.340> is<18:11:41.580> going 18:11:41.810 --> 18:11:41.820 align:start position:0% going to occur whereas the IDS is going 18:11:41.820 --> 18:11:45.170 align:start position:0% going to occur whereas the IDS is going to<18:11:42.000> rely<18:11:42.416> mostly<18:11:43.256> on<18:11:43.860> the<18:11:44.040> firewall<18:11:44.520> to<18:11:44.936> add 18:11:45.170 --> 18:11:45.180 align:start position:0% to rely mostly on the firewall to add 18:11:45.180 --> 18:11:47.390 align:start position:0% to rely mostly on the firewall to add Prevention<18:11:45.660> Services<18:11:46.136> again<18:11:46.796> this<18:11:47.096> is<18:11:47.220> a<18:11:47.340> lot 18:11:47.390 --> 18:11:47.400 align:start position:0% Prevention Services again this is a lot 18:11:47.400 --> 18:11:49.786 align:start position:0% Prevention Services again this is a lot more<18:11:47.580> expensive<18:11:48.180> but<18:11:48.596> if<18:11:48.900> my<18:11:49.136> network<18:11:49.320> has<18:11:49.680> a 18:11:49.786 --> 18:11:49.796 align:start position:0% more expensive but if my network has a 18:11:49.796 --> 18:11:51.350 align:start position:0% more expensive but if my network has a lot<18:11:49.916> of<18:11:50.040> stuff<18:11:50.160> going<18:11:50.400> on<18:11:50.580> in<18:11:50.756> it<18:11:50.936> I<18:11:51.180> probably 18:11:51.350 --> 18:11:51.360 align:start position:0% lot of stuff going on in it I probably 18:11:51.360 --> 18:11:53.690 align:start position:0% lot of stuff going on in it I probably want<18:11:51.956> to<18:11:52.136> spend<18:11:52.320> the<18:11:52.560> money<18:11:52.740> in<18:11:53.276> order<18:11:53.400> to 18:11:53.690 --> 18:11:53.700 align:start position:0% want to spend the money in order to 18:11:53.700 --> 18:11:55.850 align:start position:0% want to spend the money in order to provide<18:11:54.000> more<18:11:54.360> security<18:11:54.540> for<18:11:54.956> my<18:11:55.136> network 18:11:55.850 --> 18:11:55.860 align:start position:0% provide more security for my network 18:11:55.860 --> 18:11:57.650 align:start position:0% provide more security for my network now<18:11:56.340> there<18:11:56.456> are<18:11:56.580> a<18:11:56.636> few<18:11:56.756> reasons<18:11:57.240> why 18:11:57.650 --> 18:11:57.660 align:start position:0% now there are a few reasons why 18:11:57.660 --> 18:12:00.170 align:start position:0% now there are a few reasons why implementing<18:11:58.500> an<18:11:58.616> IDs<18:11:59.040> or<18:11:59.160> IPS<18:11:59.456> is<18:11:59.756> beneficial 18:12:00.170 --> 18:12:00.180 align:start position:0% implementing an IDs or IPS is beneficial 18:12:00.180 --> 18:12:01.730 align:start position:0% implementing an IDs or IPS is beneficial first<18:12:00.840> they're<18:12:01.020> going<18:12:01.200> to<18:12:01.256> help<18:12:01.380> provide 18:12:01.730 --> 18:12:01.740 align:start position:0% first they're going to help provide 18:12:01.740 --> 18:12:03.650 align:start position:0% first they're going to help provide additional<18:12:02.160> security<18:12:02.456> to<18:12:02.880> a<18:12:03.000> network<18:12:03.116> the 18:12:03.650 --> 18:12:03.660 align:start position:0% additional security to a network the 18:12:03.660 --> 18:12:06.530 align:start position:0% additional security to a network the more<18:12:03.776> security<18:12:04.020> we<18:12:04.500> have<18:12:04.740> the<18:12:05.520> more<18:12:05.700> one<18:12:06.360> of 18:12:06.530 --> 18:12:06.540 align:start position:0% more security we have the more one of 18:12:06.540 --> 18:12:08.390 align:start position:0% more security we have the more one of the<18:12:06.660> important<18:12:06.956> words<18:12:07.136> we<18:12:07.436> see<18:12:07.680> a<18:12:07.916> lot<18:12:08.040> in 18:12:08.390 --> 18:12:08.400 align:start position:0% the important words we see a lot in 18:12:08.400 --> 18:12:11.690 align:start position:0% the important words we see a lot in computers<18:12:08.880> the<18:12:09.540> more<18:12:09.720> redundancy<18:12:10.560> we<18:12:11.340> have 18:12:11.690 --> 18:12:11.700 align:start position:0% computers the more redundancy we have 18:12:11.700 --> 18:12:14.626 align:start position:0% computers the more redundancy we have the<18:12:12.240> better<18:12:12.416> adding<18:12:13.256> layers<18:12:13.680> of<18:12:13.916> security<18:12:14.160> and 18:12:14.626 --> 18:12:14.636 align:start position:0% the better adding layers of security and 18:12:14.636 --> 18:12:17.090 align:start position:0% the better adding layers of security and IPS<18:12:15.000> and<18:12:15.596> a<18:12:15.776> firewall<18:12:16.196> for<18:12:16.500> instance<18:12:16.744> is<18:12:16.920> like 18:12:17.090 --> 18:12:17.100 align:start position:0% IPS and a firewall for instance is like 18:12:17.100 --> 18:12:18.950 align:start position:0% IPS and a firewall for instance is like wearing<18:12:17.460> multiple<18:12:17.756> layers<18:12:18.064> of<18:12:18.244> clothing<18:12:18.540> in 18:12:18.950 --> 18:12:18.960 align:start position:0% wearing multiple layers of clothing in 18:12:18.960 --> 18:12:20.686 align:start position:0% wearing multiple layers of clothing in the<18:12:19.080> cold<18:12:19.256> the<18:12:19.920> more<18:12:20.040> layers<18:12:20.336> the<18:12:20.580> more 18:12:20.686 --> 18:12:20.696 align:start position:0% the cold the more layers the more 18:12:20.696 --> 18:12:23.090 align:start position:0% the cold the more layers the more protected<18:12:21.180> you<18:12:21.360> are<18:12:21.540> now<18:12:22.376> firewalls<18:12:22.976> and 18:12:23.090 --> 18:12:23.100 align:start position:0% protected you are now firewalls and 18:12:23.100 --> 18:12:26.450 align:start position:0% protected you are now firewalls and Antivirus<18:12:23.640> systems<18:12:24.000> are<18:12:24.180> great<18:12:24.360> but<18:12:24.720> they<18:12:25.140> are 18:12:26.450 --> 18:12:26.460 align:start position:0% Antivirus systems are great but they are 18:12:26.460 --> 18:12:28.554 align:start position:0% Antivirus systems are great but they are flawed<18:12:27.420> in<18:12:27.720> that<18:12:27.900> they're<18:12:28.080> not<18:12:28.256> able<18:12:28.436> to 18:12:28.554 --> 18:12:28.564 align:start position:0% flawed in that they're not able to 18:12:28.564 --> 18:12:31.366 align:start position:0% flawed in that they're not able to handle<18:12:28.860> every<18:12:29.040> type<18:12:29.280> of<18:12:29.460> threat<18:12:30.256> ids's<18:12:31.256> and 18:12:31.366 --> 18:12:31.376 align:start position:0% handle every type of threat ids's and 18:12:31.376 --> 18:12:33.710 align:start position:0% handle every type of threat ids's and ips's<18:12:31.976> can<18:12:32.220> detect<18:12:32.516> and<18:12:32.876> take<18:12:33.064> care<18:12:33.420> of 18:12:33.710 --> 18:12:33.720 align:start position:0% ips's can detect and take care of 18:12:33.720 --> 18:12:35.926 align:start position:0% ips's can detect and take care of threats<18:12:34.680> that<18:12:34.920> might<18:12:35.100> not<18:12:35.280> otherwise<18:12:35.640> be 18:12:35.926 --> 18:12:35.936 align:start position:0% threats that might not otherwise be 18:12:35.936 --> 18:12:38.390 align:start position:0% threats that might not otherwise be found<18:12:36.180> by<18:12:36.540> the<18:12:36.720> firewall<18:12:37.196> or<18:12:37.744> by<18:12:37.920> the<18:12:38.100> virus 18:12:38.390 --> 18:12:38.400 align:start position:0% found by the firewall or by the virus 18:12:38.400 --> 18:12:40.246 align:start position:0% found by the firewall or by the virus scan<18:12:38.640> program<18:12:38.876> so<18:12:39.476> there's<18:12:39.656> really<18:12:39.900> not<18:12:40.080> a 18:12:40.246 --> 18:12:40.256 align:start position:0% scan program so there's really not a 18:12:40.256 --> 18:12:41.450 align:start position:0% scan program so there's really not a single<18:12:40.500> system<18:12:40.680> or<18:12:40.920> program<18:12:41.100> that<18:12:41.336> can 18:12:41.450 --> 18:12:41.460 align:start position:0% single system or program that can 18:12:41.460 --> 18:12:43.554 align:start position:0% single system or program that can protect<18:12:41.756> against<18:12:41.936> all<18:12:42.476> attacks<18:12:42.960> but<18:12:43.376> the 18:12:43.554 --> 18:12:43.564 align:start position:0% protect against all attacks but the 18:12:43.564 --> 18:12:44.990 align:start position:0% protect against all attacks but the protection<18:12:43.920> features<18:12:44.336> of<18:12:44.640> multiple 18:12:44.990 --> 18:12:45.000 align:start position:0% protection features of multiple 18:12:45.000 --> 18:12:47.030 align:start position:0% protection features of multiple different<18:12:45.244> types<18:12:45.720> of<18:12:45.780> systems<18:12:46.256> can<18:12:46.860> actually 18:12:47.030 --> 18:12:47.040 align:start position:0% different types of systems can actually 18:12:47.040 --> 18:12:49.366 align:start position:0% different types of systems can actually add<18:12:47.336> up<18:12:47.516> to<18:12:47.936> very<18:12:48.296> thick<18:12:48.780> layers<18:12:49.080> of 18:12:49.366 --> 18:12:49.376 align:start position:0% add up to very thick layers of 18:12:49.376 --> 18:12:52.130 align:start position:0% add up to very thick layers of protection<18:12:49.744> for<18:12:50.156> an<18:12:50.336> attack<18:12:50.460> finally<18:12:51.420> the<18:12:51.720> IDS 18:12:52.130 --> 18:12:52.140 align:start position:0% protection for an attack finally the IDS 18:12:52.140 --> 18:12:54.590 align:start position:0% protection for an attack finally the IDS IPS<18:12:52.616> keeps<18:12:53.280> a<18:12:53.400> record<18:12:53.580> of<18:12:53.820> all<18:12:54.064> the<18:12:54.244> attacks 18:12:54.590 --> 18:12:54.600 align:start position:0% IPS keeps a record of all the attacks 18:12:54.600 --> 18:12:56.506 align:start position:0% IPS keeps a record of all the attacks they<18:12:54.780> detect<18:12:55.140> this<18:12:55.680> comes<18:12:55.976> in<18:12:56.100> handy<18:12:56.336> because 18:12:56.506 --> 18:12:56.516 align:start position:0% they detect this comes in handy because 18:12:56.516 --> 18:12:58.366 align:start position:0% they detect this comes in handy because it<18:12:56.696> lets<18:12:57.000> the<18:12:57.116> administrator<18:12:57.656> see<18:12:57.960> where<18:12:58.196> on 18:12:58.366 --> 18:12:58.376 align:start position:0% it lets the administrator see where on 18:12:58.376 --> 18:12:59.810 align:start position:0% it lets the administrator see where on the<18:12:58.500> network<18:12:58.564> they're<18:12:58.860> being<18:12:59.040> targeted<18:12:59.516> most 18:12:59.810 --> 18:12:59.820 align:start position:0% the network they're being targeted most 18:12:59.820 --> 18:13:01.554 align:start position:0% the network they're being targeted most and<18:13:00.360> then<18:13:00.476> allows<18:13:00.836> the<18:13:00.960> administrator<18:13:01.376> to 18:13:01.554 --> 18:13:01.564 align:start position:0% and then allows the administrator to 18:13:01.564 --> 18:13:03.410 align:start position:0% and then allows the administrator to make<18:13:01.744> changes<18:13:02.280> add<18:13:02.640> protection<18:13:03.000> of<18:13:03.296> the 18:13:03.410 --> 18:13:03.420 align:start position:0% make changes add protection of the 18:13:03.420 --> 18:13:05.686 align:start position:0% make changes add protection of the places<18:13:03.600> that<18:13:03.900> are<18:13:04.016> attacked<18:13:04.376> most<18:13:04.616> often<18:13:05.040> and 18:13:05.686 --> 18:13:05.696 align:start position:0% places that are attacked most often and 18:13:05.696 --> 18:13:07.246 align:start position:0% places that are attacked most often and most<18:13:05.876> importantly<18:13:06.180> create<18:13:06.476> new<18:13:06.780> policies 18:13:07.246 --> 18:13:07.256 align:start position:0% most importantly create new policies 18:13:07.256 --> 18:13:08.450 align:start position:0% most importantly create new policies that<18:13:07.500> are<18:13:07.616> going<18:13:07.744> to<18:13:07.796> prevent<18:13:08.100> security 18:13:08.450 --> 18:13:08.460 align:start position:0% that are going to prevent security 18:13:08.460 --> 18:13:10.910 align:start position:0% that are going to prevent security breaches<18:13:09.180> in<18:13:09.360> the<18:13:09.476> future<18:13:09.600> now<18:13:10.376> while<18:13:10.616> I'm<18:13:10.796> not 18:13:10.910 --> 18:13:10.920 align:start position:0% breaches in the future now while I'm not 18:13:10.920 --> 18:13:12.530 align:start position:0% breaches in the future now while I'm not going<18:13:11.040> to<18:13:11.156> get<18:13:11.220> into<18:13:11.336> the<18:13:11.580> technical<18:13:11.936> aspects 18:13:12.530 --> 18:13:12.540 align:start position:0% going to get into the technical aspects 18:13:12.540 --> 18:13:14.270 align:start position:0% going to get into the technical aspects of<18:13:12.720> implementing<18:13:13.256> these<18:13:13.500> systems<18:13:13.860> as<18:13:13.976> I<18:13:14.156> said 18:13:14.270 --> 18:13:14.280 align:start position:0% of implementing these systems as I said 18:13:14.280 --> 18:13:16.130 align:start position:0% of implementing these systems as I said I<18:13:14.516> want<18:13:14.640> to<18:13:14.756> talk<18:13:14.936> about<18:13:15.180> what<18:13:15.656> we<18:13:15.836> need<18:13:15.960> to 18:13:16.130 --> 18:13:16.140 align:start position:0% I want to talk about what we need to 18:13:16.140 --> 18:13:18.950 align:start position:0% I want to talk about what we need to consider<18:13:16.616> while<18:13:17.400> we're<18:13:17.580> considering<18:13:18.180> putting 18:13:18.950 --> 18:13:18.960 align:start position:0% consider while we're considering putting 18:13:18.960 --> 18:13:22.070 align:start position:0% consider while we're considering putting in<18:13:19.140> an<18:13:19.680> IPS<18:13:19.920> or<18:13:20.220> IDs<18:13:20.696> first<18:13:21.476> we<18:13:21.720> need<18:13:21.900> to<18:13:21.960> figure 18:13:22.070 --> 18:13:22.080 align:start position:0% in an IPS or IDs first we need to figure 18:13:22.080 --> 18:13:24.710 align:start position:0% in an IPS or IDs first we need to figure out<18:13:22.256> the<18:13:22.616> ideal<18:13:22.976> placement<18:13:23.460> of<18:13:23.696> the<18:13:23.876> IDS<18:13:24.296> IPS 18:13:24.710 --> 18:13:24.720 align:start position:0% out the ideal placement of the IDS IPS 18:13:24.720 --> 18:13:26.686 align:start position:0% out the ideal placement of the IDS IPS on<18:13:25.196> the<18:13:25.320> network<18:13:25.500> this<18:13:26.040> means<18:13:26.220> figure<18:13:26.400> figure 18:13:26.686 --> 18:13:26.696 align:start position:0% on the network this means figure figure 18:13:26.696 --> 18:13:28.310 align:start position:0% on the network this means figure figure out<18:13:26.936> where<18:13:27.180> the<18:13:27.360> sensors<18:13:27.720> are<18:13:27.900> that<18:13:28.080> are<18:13:28.256> going 18:13:28.310 --> 18:13:28.320 align:start position:0% out where the sensors are that are going 18:13:28.320 --> 18:13:30.826 align:start position:0% out where the sensors are that are going to<18:13:28.436> provide<18:13:28.680> the<18:13:28.860> most<18:13:28.976> coverage<18:13:29.400> an<18:13:30.064> IDs<18:13:30.540> IPS 18:13:30.826 --> 18:13:30.836 align:start position:0% to provide the most coverage an IDs IPS 18:13:30.836 --> 18:13:33.350 align:start position:0% to provide the most coverage an IDs IPS needs<18:13:31.256> to<18:13:31.320> be<18:13:31.376> set<18:13:31.564> up<18:13:31.680> where<18:13:32.220> choke<18:13:32.756> points 18:13:33.350 --> 18:13:33.360 align:start position:0% needs to be set up where choke points 18:13:33.360 --> 18:13:37.310 align:start position:0% needs to be set up where choke points are<18:13:33.780> available<18:13:33.976> a<18:13:34.976> choke<18:13:35.280> point<18:13:35.780> is<18:13:36.780> a 18:13:37.310 --> 18:13:37.320 align:start position:0% are available a choke point is a 18:13:37.320 --> 18:13:39.826 align:start position:0% are available a choke point is a strategy<18:13:37.860> that<18:13:38.580> involves<18:13:39.064> narrowing<18:13:39.656> down 18:13:39.826 --> 18:13:39.836 align:start position:0% strategy that involves narrowing down 18:13:39.836 --> 18:13:41.926 align:start position:0% strategy that involves narrowing down the<18:13:40.196> physical<18:13:40.436> space<18:13:40.920> that<18:13:41.280> an<18:13:41.460> attacker<18:13:41.820> is 18:13:41.926 --> 18:13:41.936 align:start position:0% the physical space that an attacker is 18:13:41.936 --> 18:13:44.450 align:start position:0% the physical space that an attacker is able<18:13:42.180> to<18:13:42.296> utilize<18:13:42.780> and<18:13:43.376> The<18:13:43.564> Logical<18:13:43.860> space<18:13:44.156> as 18:13:44.450 --> 18:13:44.460 align:start position:0% able to utilize and The Logical space as 18:13:44.460 --> 18:13:47.090 align:start position:0% able to utilize and The Logical space as well<18:13:44.696> this<18:13:45.476> way<18:13:45.656> the<18:13:45.900> defenses<18:13:46.376> must<18:13:46.616> easier 18:13:47.090 --> 18:13:47.100 align:start position:0% well this way the defenses must easier 18:13:47.100 --> 18:13:50.746 align:start position:0% well this way the defenses must easier so<18:13:47.756> we're<18:13:47.936> really<18:13:48.180> limiting<18:13:48.720> the<18:13:49.016> area 18:13:50.746 --> 18:13:50.756 align:start position:0% so we're really limiting the area 18:13:50.756 --> 18:13:53.506 align:start position:0% so we're really limiting the area of<18:13:51.180> our<18:13:51.296> vulnerability<18:13:51.960> much<18:13:52.500> like 18:13:53.506 --> 18:13:53.516 align:start position:0% of our vulnerability much like 18:13:53.516 --> 18:13:56.090 align:start position:0% of our vulnerability much like Achilles<18:13:54.296> heel<18:13:54.720> using<18:13:55.376> choke<18:13:55.680> points<18:13:56.040> is 18:13:56.090 --> 18:13:56.100 align:start position:0% Achilles heel using choke points is 18:13:56.100 --> 18:13:57.170 align:start position:0% Achilles heel using choke points is actually<18:13:56.280> something<18:13:56.580> that's<18:13:56.820> been<18:13:57.000> in 18:13:57.170 --> 18:13:57.180 align:start position:0% actually something that's been in 18:13:57.180 --> 18:13:59.866 align:start position:0% actually something that's been in militaries<18:13:57.656> throughout<18:13:58.016> history<18:13:58.400> notable<18:13:59.400> is 18:13:59.866 --> 18:13:59.876 align:start position:0% militaries throughout history notable is 18:13:59.876 --> 18:14:02.270 align:start position:0% militaries throughout history notable is like<18:14:00.180> the<18:14:00.540> Spartan<18:14:00.960> Army<18:14:01.256> of<18:14:01.436> 300<18:14:01.744> men<18:14:01.976> which 18:14:02.270 --> 18:14:02.280 align:start position:0% like the Spartan Army of 300 men which 18:14:02.280 --> 18:14:03.890 align:start position:0% like the Spartan Army of 300 men which it<18:14:02.400> used<18:14:02.580> against<18:14:02.820> the<18:14:03.116> Persians<18:14:03.656> when<18:14:03.780> they 18:14:03.890 --> 18:14:03.900 align:start position:0% it used against the Persians when they 18:14:03.900 --> 18:14:06.054 align:start position:0% it used against the Persians when they were<18:14:04.080> greatly<18:14:04.376> outnumbered<18:14:04.920> by<18:14:05.400> forcing<18:14:05.820> all 18:14:06.054 --> 18:14:06.064 align:start position:0% were greatly outnumbered by forcing all 18:14:06.064 --> 18:14:10.670 align:start position:0% were greatly outnumbered by forcing all of<18:14:06.180> the<18:14:06.360> attackers<18:14:06.836> into<18:14:07.196> a<18:14:07.680> smaller<18:14:08.100> path 18:14:10.670 --> 18:14:10.680 align:start position:0% 18:14:10.680 --> 18:14:13.006 align:start position:0% so<18:14:11.100> if<18:14:11.220> we<18:14:11.400> had<18:14:11.516> a<18:14:11.696> mountain<18:14:11.876> right 18:14:13.006 --> 18:14:13.016 align:start position:0% so if we had a mountain right 18:14:13.016 --> 18:14:15.234 align:start position:0% so if we had a mountain right and<18:14:13.616> we<18:14:13.796> make<18:14:14.156> sure<18:14:14.336> that<18:14:14.640> everyone's<18:14:15.000> coming 18:14:15.234 --> 18:14:15.244 align:start position:0% and we make sure that everyone's coming 18:14:15.244 --> 18:14:17.686 align:start position:0% and we make sure that everyone's coming up<18:14:15.600> through<18:14:16.016> this<18:14:16.256> path<18:14:16.500> then<18:14:17.040> we<18:14:17.280> can<18:14:17.460> really 18:14:17.686 --> 18:14:17.696 align:start position:0% up through this path then we can really 18:14:17.696 --> 18:14:19.670 align:start position:0% up through this path then we can really attack<18:14:18.116> them<18:14:18.420> a<18:14:18.656> lot<18:14:18.720> easier<18:14:18.960> from<18:14:19.196> Atop<18:14:19.564> The 18:14:19.670 --> 18:14:19.680 align:start position:0% attack them a lot easier from Atop The 18:14:19.680 --> 18:14:21.106 align:start position:0% attack them a lot easier from Atop The Mountain<18:14:19.860> rather<18:14:20.220> than<18:14:20.336> having<18:14:20.580> them<18:14:20.820> come 18:14:21.106 --> 18:14:21.116 align:start position:0% Mountain rather than having them come 18:14:21.116 --> 18:14:23.866 align:start position:0% Mountain rather than having them come all<18:14:21.900> around<18:14:22.140> the<18:14:22.564> mountain 18:14:23.866 --> 18:14:23.876 align:start position:0% all around the mountain 18:14:23.876 --> 18:14:26.270 align:start position:0% all around the mountain next<18:14:24.296> the<18:14:24.600> administrator<18:14:25.196> needs<18:14:26.100> to 18:14:26.270 --> 18:14:26.280 align:start position:0% next the administrator needs to 18:14:26.280 --> 18:14:28.426 align:start position:0% next the administrator needs to fine-tune<18:14:26.936> the<18:14:27.064> alerts<18:14:27.360> the<18:14:27.540> IDS<18:14:27.960> and<18:14:28.140> IPS 18:14:28.426 --> 18:14:28.436 align:start position:0% fine-tune the alerts the IDS and IPS 18:14:28.436 --> 18:14:32.146 align:start position:0% fine-tune the alerts the IDS and IPS outputs<18:14:29.156> so<18:14:29.820> that<18:14:30.116> they<18:14:30.540> are<18:14:30.836> more<18:14:31.140> useful<18:14:31.564> if 18:14:32.146 --> 18:14:32.156 align:start position:0% outputs so that they are more useful if 18:14:32.156 --> 18:14:34.006 align:start position:0% outputs so that they are more useful if the<18:14:32.336> alert<18:14:32.580> merely<18:14:33.064> says<18:14:33.420> an<18:14:33.540> attack<18:14:33.720> is 18:14:34.006 --> 18:14:34.016 align:start position:0% the alert merely says an attack is 18:14:34.016 --> 18:14:35.326 align:start position:0% the alert merely says an attack is taking<18:14:34.256> place<18:14:34.564> this<18:14:34.796> doesn't<18:14:35.040> give<18:14:35.220> the 18:14:35.326 --> 18:14:35.336 align:start position:0% taking place this doesn't give the 18:14:35.336 --> 18:14:37.366 align:start position:0% taking place this doesn't give the administrator<18:14:35.820> anything<18:14:36.116> to<18:14:36.360> go<18:14:36.540> off<18:14:36.720> of<18:14:36.900> the 18:14:37.366 --> 18:14:37.376 align:start position:0% administrator anything to go off of the 18:14:37.376 --> 18:14:39.106 align:start position:0% administrator anything to go off of the alerts<18:14:37.744> really<18:14:37.860> need<18:14:38.040> to<18:14:38.156> be<18:14:38.280> detailed<18:14:38.820> and 18:14:39.106 --> 18:14:39.116 align:start position:0% alerts really need to be detailed and 18:14:39.116 --> 18:14:40.606 align:start position:0% alerts really need to be detailed and tailored<18:14:39.540> to<18:14:39.720> exactly<18:14:40.196> what<18:14:40.500> the 18:14:40.606 --> 18:14:40.616 align:start position:0% tailored to exactly what the 18:14:40.616 --> 18:14:42.466 align:start position:0% tailored to exactly what the administrator<18:14:41.100> needs<18:14:41.516> to<18:14:41.580> know<18:14:41.756> this<18:14:42.360> is 18:14:42.466 --> 18:14:42.476 align:start position:0% administrator needs to know this is 18:14:42.476 --> 18:14:43.670 align:start position:0% administrator needs to know this is something<18:14:42.600> that<18:14:42.780> has<18:14:42.900> to<18:14:43.080> be<18:14:43.140> set<18:14:43.320> up<18:14:43.500> and 18:14:43.670 --> 18:14:43.680 align:start position:0% something that has to be set up and 18:14:43.680 --> 18:14:45.350 align:start position:0% something that has to be set up and tested<18:14:44.040> by<18:14:44.280> the<18:14:44.400> administrator<18:14:44.876> once<18:14:45.296> the 18:14:45.350 --> 18:14:45.360 align:start position:0% tested by the administrator once the 18:14:45.360 --> 18:14:47.146 align:start position:0% tested by the administrator once the alerts<18:14:45.720> have<18:14:45.836> been<18:14:46.016> configured<18:14:46.500> and<18:14:46.920> once 18:14:47.146 --> 18:14:47.156 align:start position:0% alerts have been configured and once 18:14:47.156 --> 18:14:49.490 align:start position:0% alerts have been configured and once attacks<18:14:47.580> start<18:14:47.696> taking<18:14:48.000> place<18:14:48.296> next<18:14:49.196> the 18:14:49.490 --> 18:14:49.500 align:start position:0% attacks start taking place next the 18:14:49.500 --> 18:14:50.866 align:start position:0% attacks start taking place next the monitoring<18:14:49.920> of<18:14:50.040> the<18:14:50.156> alerts<18:14:50.516> needs<18:14:50.756> to<18:14:50.820> be 18:14:50.866 --> 18:14:50.876 align:start position:0% monitoring of the alerts needs to be 18:14:50.876 --> 18:14:53.210 align:start position:0% monitoring of the alerts needs to be handled<18:14:51.244> what<18:14:51.960> use<18:14:52.140> are<18:14:52.376> the<18:14:52.500> alerts<18:14:52.796> if<18:14:52.976> no 18:14:53.210 --> 18:14:53.220 align:start position:0% handled what use are the alerts if no 18:14:53.220 --> 18:14:55.006 align:start position:0% handled what use are the alerts if no one's<18:14:53.516> seeing<18:14:53.820> them<18:14:54.000> the<18:14:54.600> administrator 18:14:55.006 --> 18:14:55.016 align:start position:0% one's seeing them the administrator 18:14:55.016 --> 18:14:56.326 align:start position:0% one's seeing them the administrator can't<18:14:55.376> always<18:14:55.616> be<18:14:55.860> on<18:14:56.040> the<18:14:56.156> network 18:14:56.326 --> 18:14:56.336 align:start position:0% can't always be on the network 18:14:56.336 --> 18:14:58.130 align:start position:0% can't always be on the network constantly<18:14:57.064> looking<18:14:57.296> out<18:14:57.476> for<18:14:57.656> the<18:14:57.780> alerts 18:14:58.130 --> 18:14:58.140 align:start position:0% constantly looking out for the alerts 18:14:58.140 --> 18:15:00.530 align:start position:0% constantly looking out for the alerts they're<18:14:58.320> sent<18:14:58.564> so<18:14:59.336> it's<18:14:59.580> their<18:14:59.820> job<18:15:00.064> however 18:15:00.530 --> 18:15:00.540 align:start position:0% they're sent so it's their job however 18:15:00.540 --> 18:15:02.570 align:start position:0% they're sent so it's their job however to<18:15:00.900> set<18:15:01.080> up<18:15:01.320> a<18:15:01.500> way<18:15:01.680> for<18:15:01.860> the<18:15:02.040> alerts<18:15:02.336> to<18:15:02.516> be 18:15:02.570 --> 18:15:02.580 align:start position:0% to set up a way for the alerts to be 18:15:02.580 --> 18:15:05.810 align:start position:0% to set up a way for the alerts to be monitored<18:15:03.064> this<18:15:03.600> might<18:15:03.780> involve<18:15:04.196> hiring<18:15:05.100> an 18:15:05.810 --> 18:15:05.820 align:start position:0% monitored this might involve hiring an 18:15:05.820 --> 18:15:07.310 align:start position:0% monitored this might involve hiring an employee<18:15:06.116> to<18:15:06.360> monitor<18:15:06.656> it<18:15:06.836> constantly 18:15:07.310 --> 18:15:07.320 align:start position:0% employee to monitor it constantly 18:15:07.320 --> 18:15:09.710 align:start position:0% employee to monitor it constantly something<18:15:07.616> we<18:15:07.860> used<18:15:07.976> to<18:15:08.100> call<18:15:08.220> beeper<18:15:08.696> Duty 18:15:09.710 --> 18:15:09.720 align:start position:0% something we used to call beeper Duty 18:15:09.720 --> 18:15:13.210 align:start position:0% something we used to call beeper Duty where<18:15:10.256> someone<18:15:10.500> was<18:15:10.744> always<18:15:11.100> on<18:15:12.064> 24-hour<18:15:12.720> call 18:15:13.210 --> 18:15:13.220 align:start position:0% where someone was always on 24-hour call 18:15:13.220 --> 18:15:15.350 align:start position:0% where someone was always on 24-hour call or<18:15:14.220> configuring<18:15:14.820> a<18:15:14.936> way<18:15:15.064> for<18:15:15.244> the 18:15:15.350 --> 18:15:15.360 align:start position:0% or configuring a way for the 18:15:15.360 --> 18:15:17.686 align:start position:0% or configuring a way for the administrator<18:15:15.720> to<18:15:15.900> get<18:15:16.080> alerts<18:15:16.500> remotely<18:15:16.860> say 18:15:17.686 --> 18:15:17.696 align:start position:0% administrator to get alerts remotely say 18:15:17.696 --> 18:15:19.366 align:start position:0% administrator to get alerts remotely say a<18:15:18.116> text<18:15:18.360> message 18:15:19.366 --> 18:15:19.376 align:start position:0% a text message 18:15:19.376 --> 18:15:21.350 align:start position:0% a text message finally<18:15:19.860> procedures<18:15:20.460> need<18:15:20.696> to<18:15:20.820> be<18:15:20.876> put<18:15:21.180> in 18:15:21.350 --> 18:15:21.360 align:start position:0% finally procedures need to be put in 18:15:21.360 --> 18:15:23.090 align:start position:0% finally procedures need to be put in place<18:15:21.600> for<18:15:22.140> what's<18:15:22.320> going<18:15:22.500> to<18:15:22.564> happen<18:15:22.680> in<18:15:22.976> the 18:15:23.090 --> 18:15:23.100 align:start position:0% place for what's going to happen in the 18:15:23.100 --> 18:15:25.366 align:start position:0% place for what's going to happen in the event<18:15:23.220> of<18:15:23.516> an<18:15:23.696> attack<18:15:24.116> the<18:15:24.780> question<18:15:25.080> what's 18:15:25.366 --> 18:15:25.376 align:start position:0% event of an attack the question what's 18:15:25.376 --> 18:15:28.910 align:start position:0% event of an attack the question what's our<18:15:25.564> plan<18:15:25.744> of<18:15:25.976> action<18:15:26.336> needs<18:15:27.296> to<18:15:27.476> be<18:15:27.656> asked 18:15:28.910 --> 18:15:28.920 align:start position:0% our plan of action needs to be asked 18:15:28.920 --> 18:15:31.606 align:start position:0% our plan of action needs to be asked just<18:15:29.400> in<18:15:29.516> case<18:15:29.696> an<18:15:30.116> attack<18:15:30.296> goes<18:15:30.960> on<18:15:31.140> so<18:15:31.436> we 18:15:31.606 --> 18:15:31.616 align:start position:0% just in case an attack goes on so we 18:15:31.616 --> 18:15:34.246 align:start position:0% just in case an attack goes on so we know<18:15:31.796> what<18:15:32.040> is<18:15:32.220> going<18:15:32.460> to<18:15:33.000> uh<18:15:33.720> what<18:15:33.960> programs 18:15:34.246 --> 18:15:34.256 align:start position:0% know what is going to uh what programs 18:15:34.256 --> 18:15:37.070 align:start position:0% know what is going to uh what programs are<18:15:34.376> we<18:15:34.500> going<18:15:34.564> to<18:15:34.680> deploy<18:15:35.040> what<18:15:36.000> Hardware<18:15:36.476> do 18:15:37.070 --> 18:15:37.080 align:start position:0% are we going to deploy what Hardware do 18:15:37.080 --> 18:15:38.746 align:start position:0% are we going to deploy what Hardware do we<18:15:37.256> shut<18:15:37.436> off<18:15:37.616> our<18:15:38.100> connection<18:15:38.336> to<18:15:38.640> the 18:15:38.746 --> 18:15:38.756 align:start position:0% we shut off our connection to the 18:15:38.756 --> 18:15:41.090 align:start position:0% we shut off our connection to the network<18:15:39.360> Etc<18:15:39.476> if<18:15:40.080> an<18:15:40.320> attack<18:15:40.436> happens<18:15:40.796> it's 18:15:41.090 --> 18:15:41.100 align:start position:0% network Etc if an attack happens it's 18:15:41.100 --> 18:15:42.530 align:start position:0% network Etc if an attack happens it's really<18:15:41.280> up<18:15:41.460> to<18:15:41.580> the<18:15:41.756> administrator<18:15:42.180> to<18:15:42.360> lead 18:15:42.530 --> 18:15:42.540 align:start position:0% really up to the administrator to lead 18:15:42.540 --> 18:15:44.390 align:start position:0% really up to the administrator to lead the<18:15:42.720> defense<18:15:43.016> and<18:15:43.256> the<18:15:43.436> strategy<18:15:43.796> around<18:15:44.040> that 18:15:44.390 --> 18:15:44.400 align:start position:0% the defense and the strategy around that 18:15:44.400 --> 18:15:46.310 align:start position:0% the defense and the strategy around that defense 18:15:46.310 --> 18:15:46.320 align:start position:0% defense 18:15:46.320 --> 18:15:49.070 align:start position:0% defense so<18:15:47.040> just<18:15:47.400> to<18:15:47.580> recap<18:15:48.000> we<18:15:48.476> first<18:15:48.600> talked<18:15:48.960> about 18:15:49.070 --> 18:15:49.080 align:start position:0% so just to recap we first talked about 18:15:49.080 --> 18:15:51.890 align:start position:0% so just to recap we first talked about an<18:15:49.680> intrusion<18:15:50.220> detection<18:15:50.876> system<18:15:51.296> and 18:15:51.890 --> 18:15:51.900 align:start position:0% an intrusion detection system and 18:15:51.900 --> 18:15:53.926 align:start position:0% an intrusion detection system and remember<18:15:52.080> that<18:15:52.616> D<18:15:52.860> is<18:15:53.156> really<18:15:53.460> important 18:15:53.926 --> 18:15:53.936 align:start position:0% remember that D is really important 18:15:53.936 --> 18:15:57.234 align:start position:0% remember that D is really important which<18:15:54.540> is<18:15:54.780> a<18:15:55.436> passive<18:15:55.860> system<18:15:56.156> because<18:15:56.876> it 18:15:57.234 --> 18:15:57.244 align:start position:0% which is a passive system because it 18:15:57.244 --> 18:15:59.746 align:start position:0% which is a passive system because it simply<18:15:57.744> detects<18:15:58.744> an<18:15:58.976> intrusion<18:15:59.400> as<18:15:59.580> it's 18:15:59.746 --> 18:15:59.756 align:start position:0% simply detects an intrusion as it's 18:15:59.756 --> 18:16:02.506 align:start position:0% simply detects an intrusion as it's occurring<18:16:00.180> and<18:16:00.836> notifies 18:16:02.506 --> 18:16:02.516 align:start position:0% occurring and notifies 18:16:02.516 --> 18:16:06.286 align:start position:0% occurring and notifies an<18:16:02.936> administrator 18:16:06.286 --> 18:16:06.296 align:start position:0% 18:16:06.296 --> 18:16:07.910 align:start position:0% we<18:16:06.780> also<18:16:06.960> talked<18:16:07.256> about<18:16:07.320> the<18:16:07.564> two<18:16:07.744> different 18:16:07.910 --> 18:16:07.920 align:start position:0% we also talked about the two different 18:16:07.920 --> 18:16:10.966 align:start position:0% we also talked about the two different types<18:16:08.516> of<18:16:08.640> IDs<18:16:09.116> as<18:16:09.296> there<18:16:09.476> are<18:16:09.976> behavior-based 18:16:10.966 --> 18:16:10.976 align:start position:0% types of IDs as there are behavior-based 18:16:10.976 --> 18:16:14.210 align:start position:0% types of IDs as there are behavior-based and<18:16:11.400> signature<18:16:11.820> based<18:16:12.616> behavior-based<18:16:13.616> looks 18:16:14.210 --> 18:16:14.220 align:start position:0% and signature based behavior-based looks 18:16:14.220 --> 18:16:15.826 align:start position:0% and signature based behavior-based looks at<18:16:14.400> behaviors 18:16:15.826 --> 18:16:15.836 align:start position:0% at behaviors 18:16:15.836 --> 18:16:19.426 align:start position:0% at behaviors such<18:16:16.616> as<18:16:16.920> high<18:16:17.756> traffic 18:16:19.426 --> 18:16:19.436 align:start position:0% such as high traffic 18:16:19.436 --> 18:16:22.006 align:start position:0% such as high traffic people<18:16:20.040> accessing<18:16:20.820> things<18:16:21.116> they<18:16:21.600> shouldn't 18:16:22.006 --> 18:16:22.016 align:start position:0% people accessing things they shouldn't 18:16:22.016 --> 18:16:24.170 align:start position:0% people accessing things they shouldn't be<18:16:22.196> or<18:16:22.680> areas<18:16:23.040> being<18:16:23.336> accessed<18:16:23.756> that<18:16:24.000> aren't 18:16:24.170 --> 18:16:24.180 align:start position:0% be or areas being accessed that aren't 18:16:24.180 --> 18:16:26.146 align:start position:0% be or areas being accessed that aren't normally<18:16:24.476> accessed<18:16:25.080> whereas<18:16:25.744> signature 18:16:26.146 --> 18:16:26.156 align:start position:0% normally accessed whereas signature 18:16:26.156 --> 18:16:29.990 align:start position:0% normally accessed whereas signature based<18:16:26.516> looks<18:16:27.180> at<18:16:27.500> historical<18:16:28.500> data<18:16:29.156> in<18:16:29.876> the 18:16:29.990 --> 18:16:30.000 align:start position:0% based looks at historical data in the 18:16:30.000 --> 18:16:31.966 align:start position:0% based looks at historical data in the form<18:16:30.116> of<18:16:30.296> signature<18:16:30.780> files 18:16:31.966 --> 18:16:31.976 align:start position:0% form of signature files 18:16:31.976 --> 18:16:35.810 align:start position:0% form of signature files and<18:16:32.400> tries<18:16:32.696> to<18:16:33.116> match<18:16:33.720> these<18:16:34.196> up 18:16:35.810 --> 18:16:35.820 align:start position:0% and tries to match these up 18:16:35.820 --> 18:16:38.866 align:start position:0% and tries to match these up with<18:16:36.476> known<18:16:36.720> attacks 18:16:38.866 --> 18:16:38.876 align:start position:0% with known attacks 18:16:38.876 --> 18:16:41.450 align:start position:0% with known attacks of<18:16:39.244> course<18:16:39.420> if<18:16:39.836> the<18:16:40.080> attack<18:16:40.196> isn't<18:16:40.744> known<18:16:40.920> then 18:16:41.450 --> 18:16:41.460 align:start position:0% of course if the attack isn't known then 18:16:41.460 --> 18:16:42.950 align:start position:0% of course if the attack isn't known then it's<18:16:41.640> not<18:16:41.876> going<18:16:42.000> to<18:16:42.116> be<18:16:42.244> available<18:16:42.420> in<18:16:42.836> the 18:16:42.950 --> 18:16:42.960 align:start position:0% it's not going to be available in the 18:16:42.960 --> 18:16:44.570 align:start position:0% it's not going to be available in the signature<18:16:43.376> and<18:16:43.796> so<18:16:43.920> this<18:16:44.100> is<18:16:44.220> where<18:16:44.460> a 18:16:44.570 --> 18:16:44.580 align:start position:0% signature and so this is where a 18:16:44.580 --> 18:16:46.246 align:start position:0% signature and so this is where a behavior<18:16:45.000> would<18:16:45.244> come<18:16:45.360> in<18:16:45.540> play 18:16:46.246 --> 18:16:46.256 align:start position:0% behavior would come in play 18:16:46.256 --> 18:16:49.866 align:start position:0% behavior would come in play we<18:16:46.796> also<18:16:47.040> talked<18:16:47.336> about<18:16:47.836> ips's<18:16:48.836> or<18:16:49.320> intrusion 18:16:49.866 --> 18:16:49.876 align:start position:0% we also talked about ips's or intrusion 18:16:49.876 --> 18:16:52.130 align:start position:0% we also talked about ips's or intrusion prevention<18:16:50.876> systems 18:16:52.130 --> 18:16:52.140 align:start position:0% prevention systems 18:16:52.140 --> 18:16:56.090 align:start position:0% prevention systems which<18:16:52.860> are<18:16:53.720> proactive<18:16:54.720> because<18:16:55.320> they<18:16:55.860> might 18:16:56.090 --> 18:16:56.100 align:start position:0% which are proactive because they might 18:16:56.100 --> 18:16:58.606 align:start position:0% which are proactive because they might search<18:16:56.516> for<18:16:56.820> vulnerabilities 18:16:58.606 --> 18:16:58.616 align:start position:0% search for vulnerabilities 18:16:58.616 --> 18:17:00.890 align:start position:0% search for vulnerabilities in<18:16:59.100> the<18:16:59.220> system<18:16:59.400> such<18:16:59.820> as<18:17:00.000> looking<18:17:00.360> for<18:17:00.656> open 18:17:00.890 --> 18:17:00.900 align:start position:0% in the system such as looking for open 18:17:00.900 --> 18:17:04.850 align:start position:0% in the system such as looking for open ports<18:17:01.976> and<18:17:02.696> reactive 18:17:04.850 --> 18:17:04.860 align:start position:0% ports and reactive 18:17:04.860 --> 18:17:08.570 align:start position:0% ports and reactive because<18:17:05.400> they<18:17:06.064> actually<18:17:06.256> stop<18:17:07.256> an<18:17:07.976> attack<18:17:08.156> in 18:17:08.570 --> 18:17:08.580 align:start position:0% because they actually stop an attack in 18:17:08.580 --> 18:17:11.410 align:start position:0% because they actually stop an attack in its<18:17:08.876> tracks<18:17:09.244> or<18:17:09.656> at<18:17:09.836> least<18:17:10.016> they<18:17:10.436> attempt<18:17:10.744> to 18:17:11.410 --> 18:17:11.420 align:start position:0% its tracks or at least they attempt to 18:17:11.420 --> 18:17:15.234 align:start position:0% its tracks or at least they attempt to now<18:17:12.420> the<18:17:12.656> importance<18:17:12.960> of<18:17:13.080> IDs<18:17:13.564> and<18:17:13.860> ips's<18:17:14.516> is 18:17:15.234 --> 18:17:15.244 align:start position:0% now the importance of IDs and ips's is 18:17:15.244 --> 18:17:19.366 align:start position:0% now the importance of IDs and ips's is added<18:17:15.836> or<18:17:16.616> extra<18:17:16.976> security 18:17:19.366 --> 18:17:19.376 align:start position:0% 18:17:19.376 --> 18:17:21.466 align:start position:0% just<18:17:20.100> like<18:17:20.336> as<18:17:20.640> we<18:17:20.820> mentioned<18:17:21.180> having 18:17:21.466 --> 18:17:21.476 align:start position:0% just like as we mentioned having 18:17:21.476 --> 18:17:23.270 align:start position:0% just like as we mentioned having multiple<18:17:21.960> layers<18:17:22.320> if<18:17:22.500> you're<18:17:22.680> going<18:17:22.860> out<18:17:23.100> and 18:17:23.270 --> 18:17:23.280 align:start position:0% multiple layers if you're going out and 18:17:23.280 --> 18:17:24.826 align:start position:0% multiple layers if you're going out and it's<18:17:23.460> cold<18:17:23.756> outside 18:17:24.826 --> 18:17:24.836 align:start position:0% it's cold outside 18:17:24.836 --> 18:17:27.234 align:start position:0% it's cold outside it's<18:17:25.320> also<18:17:25.616> important<18:17:26.040> because<18:17:26.580> we<18:17:26.936> want<18:17:27.064> to 18:17:27.234 --> 18:17:27.244 align:start position:0% it's also important because we want to 18:17:27.244 --> 18:17:30.950 align:start position:0% it's also important because we want to know<18:17:27.420> how<18:17:28.016> to<18:17:28.256> alter 18:17:30.950 --> 18:17:30.960 align:start position:0% know how to alter 18:17:30.960 --> 18:17:33.590 align:start position:0% know how to alter our<18:17:31.436> security<18:17:31.680> policies<18:17:32.460> over<18:17:32.756> time<18:17:33.064> to<18:17:33.476> make 18:17:33.590 --> 18:17:33.600 align:start position:0% our security policies over time to make 18:17:33.600 --> 18:17:37.070 align:start position:0% our security policies over time to make them<18:17:33.900> more<18:17:34.320> secure 18:17:37.070 --> 18:17:37.080 align:start position:0% 18:17:37.080 --> 18:17:38.866 align:start position:0% and<18:17:37.436> when<18:17:37.564> we<18:17:37.744> talked<18:17:37.976> about<18:17:38.100> implementation 18:17:38.866 --> 18:17:38.876 align:start position:0% and when we talked about implementation 18:17:38.876 --> 18:17:40.910 align:start position:0% and when we talked about implementation from<18:17:39.244> a<18:17:39.420> very<18:17:39.540> Broad<18:17:39.836> View<18:17:40.140> some<18:17:40.744> of<18:17:40.860> the 18:17:40.910 --> 18:17:40.920 align:start position:0% from a very Broad View some of the 18:17:40.920 --> 18:17:43.554 align:start position:0% from a very Broad View some of the things<18:17:40.976> we<18:17:41.220> talked<18:17:41.516> about<18:17:41.580> is<18:17:42.000> placement 18:17:43.554 --> 18:17:43.564 align:start position:0% things we talked about is placement 18:17:43.564 --> 18:17:46.786 align:start position:0% things we talked about is placement we<18:17:44.100> want<18:17:44.220> them<18:17:44.460> remember<18:17:45.140> in<18:17:46.140> areas<18:17:46.500> called 18:17:46.786 --> 18:17:46.796 align:start position:0% we want them remember in areas called 18:17:46.796 --> 18:17:49.686 align:start position:0% we want them remember in areas called choke<18:17:47.756> points 18:17:49.686 --> 18:17:49.696 align:start position:0% choke points 18:17:49.696 --> 18:17:52.186 align:start position:0% choke points meaning<18:17:50.696> we<18:17:51.000> want<18:17:51.116> to<18:17:51.296> limit<18:17:51.420> the<18:17:51.780> amount<18:17:52.016> of 18:17:52.186 --> 18:17:52.196 align:start position:0% meaning we want to limit the amount of 18:17:52.196 --> 18:17:55.554 align:start position:0% meaning we want to limit the amount of areas<18:17:52.616> that<18:17:53.100> are<18:17:53.516> outside<18:17:54.476> network<18:17:55.016> has 18:17:55.554 --> 18:17:55.564 align:start position:0% areas that are outside network has 18:17:55.564 --> 18:17:58.606 align:start position:0% areas that are outside network has access<18:17:55.860> to<18:17:56.220> to<18:17:56.640> the<18:17:56.876> inside<18:17:57.080> we<18:17:58.080> also<18:17:58.320> talked 18:17:58.606 --> 18:17:58.616 align:start position:0% access to to the inside we also talked 18:17:58.616 --> 18:18:00.890 align:start position:0% access to to the inside we also talked about<18:17:58.680> monitoring 18:18:00.890 --> 18:18:00.900 align:start position:0% about monitoring 18:18:00.900 --> 18:18:04.186 align:start position:0% about monitoring and<18:18:01.564> how<18:18:01.860> we<18:18:02.040> get<18:18:02.220> notifications<18:18:03.116> which<18:18:03.900> in 18:18:04.186 --> 18:18:04.196 align:start position:0% and how we get notifications which in 18:18:04.196 --> 18:18:07.246 align:start position:0% and how we get notifications which in some<18:18:04.320> cases<18:18:04.796> needs<18:18:05.756> to<18:18:05.876> be<18:18:06.116> through<18:18:06.900> text 18:18:07.246 --> 18:18:07.256 align:start position:0% some cases needs to be through text 18:18:07.256 --> 18:18:10.246 align:start position:0% some cases needs to be through text messaging<18:18:07.976> or<18:18:08.640> email 18:18:10.246 --> 18:18:10.256 align:start position:0% messaging or email 18:18:10.256 --> 18:18:13.426 align:start position:0% messaging or email or<18:18:10.860> anything<18:18:11.040> else<18:18:11.540> finally<18:18:12.540> we<18:18:12.960> needed<18:18:13.256> to 18:18:13.426 --> 18:18:13.436 align:start position:0% or anything else finally we needed to 18:18:13.436 --> 18:18:18.170 align:start position:0% or anything else finally we needed to talk<18:18:13.616> about<18:18:13.796> what<18:18:14.156> we<18:18:14.336> do<18:18:14.516> a<18:18:14.876> plan<18:18:15.116> of<18:18:15.360> action 18:18:18.170 --> 18:18:18.180 align:start position:0% 18:18:18.180 --> 18:18:20.326 align:start position:0% in<18:18:18.900> case<18:18:19.080> we<18:18:19.436> actually<18:18:19.616> have<18:18:19.976> an<18:18:20.220> attack 18:18:20.326 --> 18:18:20.336 align:start position:0% in case we actually have an attack 18:18:20.336 --> 18:18:25.320 align:start position:0% in case we actually have an attack occurring 18:18:25.320 --> 18:18:25.330 align:start position:0% 18:18:25.330 --> 18:18:34.030 align:start position:0% [Music] 18:18:34.030 --> 18:18:34.040 align:start position:0% [Music] 18:18:34.040 --> 18:18:45.170 align:start position:0% [Music] thank<18:18:35.040> you 18:18:45.170 --> 18:18:45.180 align:start position:0% 18:18:45.180 --> 18:18:46.926 align:start position:0% network<18:18:45.960> security 18:18:46.926 --> 18:18:46.936 align:start position:0% network security 18:18:46.936 --> 18:18:51.234 align:start position:0% network security ipsec<18:18:47.936> and<18:18:48.296> ipsec<18:18:49.140> policies 18:18:51.234 --> 18:18:51.244 align:start position:0% ipsec and ipsec policies 18:18:51.244 --> 18:18:53.570 align:start position:0% ipsec and ipsec policies having<18:18:51.656> discussed<18:18:52.140> intrusion<18:18:52.680> detection<18:18:53.156> and 18:18:53.570 --> 18:18:53.580 align:start position:0% having discussed intrusion detection and 18:18:53.580 --> 18:18:55.426 align:start position:0% having discussed intrusion detection and prevention<18:18:54.064> systems<18:18:54.600> which<18:18:54.836> are<18:18:55.016> mostly 18:18:55.426 --> 18:18:55.436 align:start position:0% prevention systems which are mostly 18:18:55.436 --> 18:18:58.130 align:start position:0% prevention systems which are mostly having<18:18:55.976> to<18:18:56.156> do<18:18:56.280> with<18:18:56.516> keeping<18:18:57.064> attacks<18:18:57.836> and 18:18:58.130 --> 18:18:58.140 align:start position:0% having to do with keeping attacks and 18:18:58.140 --> 18:19:00.234 align:start position:0% having to do with keeping attacks and malicious<18:18:58.616> software<18:18:58.976> off<18:18:59.156> our<18:18:59.400> Network<18:18:59.640> I 18:19:00.234 --> 18:19:00.244 align:start position:0% malicious software off our Network I 18:19:00.244 --> 18:19:01.670 align:start position:0% malicious software off our Network I want<18:19:00.360> to<18:19:00.476> talk<18:19:00.656> about<18:19:00.960> something<18:19:01.320> called 18:19:01.670 --> 18:19:01.680 align:start position:0% want to talk about something called 18:19:01.680 --> 18:19:07.426 align:start position:0% want to talk about something called ipsec<18:19:02.580> or<18:19:03.320> IP<18:19:04.320> security<18:19:04.920> which<18:19:05.876> is<18:19:06.116> a<18:19:06.960> sort<18:19:07.256> of 18:19:07.426 --> 18:19:07.436 align:start position:0% ipsec or IP security which is a sort of 18:19:07.436 --> 18:19:10.966 align:start position:0% ipsec or IP security which is a sort of group<18:19:08.156> of<18:19:08.400> protocols<18:19:09.180> and<18:19:09.540> policies<18:19:10.080> that<18:19:10.860> are 18:19:10.966 --> 18:19:10.976 align:start position:0% group of protocols and policies that are 18:19:10.976 --> 18:19:13.246 align:start position:0% group of protocols and policies that are used<18:19:11.280> to<18:19:11.640> keep<18:19:11.876> the<18:19:12.296> data<18:19:12.600> that<18:19:12.836> we<18:19:13.016> have 18:19:13.246 --> 18:19:13.256 align:start position:0% used to keep the data that we have 18:19:13.256 --> 18:19:15.826 align:start position:0% used to keep the data that we have secure<18:19:13.976> on<18:19:14.280> a<18:19:14.400> network<18:19:14.580> whenever<18:19:15.540> we<18:19:15.720> talk 18:19:15.826 --> 18:19:15.836 align:start position:0% secure on a network whenever we talk 18:19:15.836 --> 18:19:17.746 align:start position:0% secure on a network whenever we talk about<18:19:16.016> security<18:19:16.436> there's<18:19:17.220> something<18:19:17.460> called 18:19:17.746 --> 18:19:17.756 align:start position:0% about security there's something called 18:19:17.756 --> 18:19:20.030 align:start position:0% about security there's something called CIA<18:19:18.244> the<18:19:18.600> CIA<18:19:18.900> Triad<18:19:19.376> that<18:19:19.616> we<18:19:19.744> need<18:19:19.860> to<18:19:19.920> keep 18:19:20.030 --> 18:19:20.040 align:start position:0% CIA the CIA Triad that we need to keep 18:19:20.040 --> 18:19:23.530 align:start position:0% CIA the CIA Triad that we need to keep in<18:19:20.220> mind<18:19:20.400> C<18:19:21.296> stands<18:19:21.780> for 18:19:23.530 --> 18:19:23.540 align:start position:0% in mind C stands for 18:19:23.540 --> 18:19:26.326 align:start position:0% in mind C stands for confidentiality<18:19:24.540> meaning<18:19:25.436> only<18:19:25.920> the<18:19:26.156> people 18:19:26.326 --> 18:19:26.336 align:start position:0% confidentiality meaning only the people 18:19:26.336 --> 18:19:29.030 align:start position:0% confidentiality meaning only the people we<18:19:26.820> want<18:19:27.116> to<18:19:27.296> see<18:19:27.476> something<18:19:27.780> actually<18:19:28.140> see<18:19:28.436> it 18:19:29.030 --> 18:19:29.040 align:start position:0% we want to see something actually see it 18:19:29.040 --> 18:19:33.530 align:start position:0% we want to see something actually see it the<18:19:29.756> I<18:19:29.936> stands<18:19:30.540> for<18:19:30.744> integrity<18:19:31.756> meaning<18:19:32.756> what 18:19:33.530 --> 18:19:33.540 align:start position:0% the I stands for integrity meaning what 18:19:33.540 --> 18:19:35.686 align:start position:0% the I stands for integrity meaning what we<18:19:33.720> send<18:19:33.960> is<18:19:34.320> what<18:19:34.564> the<18:19:34.744> other<18:19:34.860> party<18:19:35.156> receives 18:19:35.686 --> 18:19:35.696 align:start position:0% we send is what the other party receives 18:19:35.696 --> 18:19:38.210 align:start position:0% we send is what the other party receives it<18:19:36.064> hasn't<18:19:36.360> been<18:19:36.476> tampered<18:19:36.900> with<18:19:37.080> and<18:19:37.920> finally 18:19:38.210 --> 18:19:38.220 align:start position:0% it hasn't been tampered with and finally 18:19:38.220 --> 18:19:40.186 align:start position:0% it hasn't been tampered with and finally we<18:19:38.756> have<18:19:38.820> to<18:19:39.000> balance<18:19:39.296> all<18:19:39.540> of<18:19:39.720> this<18:19:39.836> against 18:19:40.186 --> 18:19:40.196 align:start position:0% we have to balance all of this against 18:19:40.196 --> 18:19:42.590 align:start position:0% we have to balance all of this against availability<18:19:41.040> it<18:19:41.820> doesn't<18:19:41.936> matter<18:19:42.296> if 18:19:42.590 --> 18:19:42.600 align:start position:0% availability it doesn't matter if 18:19:42.600 --> 18:19:44.810 align:start position:0% availability it doesn't matter if something<18:19:42.780> is<18:19:43.080> super<18:19:43.256> secure<18:19:43.680> if<18:19:43.920> no<18:19:44.156> one<18:19:44.336> can 18:19:44.810 --> 18:19:44.820 align:start position:0% something is super secure if no one can 18:19:44.820 --> 18:19:48.234 align:start position:0% something is super secure if no one can access<18:19:45.064> it<18:19:45.476> so<18:19:46.436> broadening<18:19:47.336> out<18:19:47.516> into<18:19:48.000> this 18:19:48.234 --> 18:19:48.244 align:start position:0% access it so broadening out into this 18:19:48.244 --> 18:19:50.990 align:start position:0% access it so broadening out into this that's<18:19:48.540> where<18:19:48.780> ipsec<18:19:49.500> comes<18:19:49.744> into<18:19:49.860> play<18:19:50.100> so 18:19:50.990 --> 18:19:51.000 align:start position:0% that's where ipsec comes into play so 18:19:51.000 --> 18:19:54.234 align:start position:0% that's where ipsec comes into play so we're<18:19:51.180> going<18:19:51.360> to<18:19:51.540> talk<18:19:51.780> about<18:19:52.640> ipsec<18:19:53.640> defining 18:19:54.234 --> 18:19:54.244 align:start position:0% we're going to talk about ipsec defining 18:19:54.244 --> 18:19:56.146 align:start position:0% we're going to talk about ipsec defining And<18:19:54.420> discussing<18:19:54.836> what<18:19:55.080> it<18:19:55.196> is<18:19:55.376> and<18:19:55.860> then<18:19:55.976> talk 18:19:56.146 --> 18:19:56.156 align:start position:0% And discussing what it is and then talk 18:19:56.156 --> 18:19:58.786 align:start position:0% And discussing what it is and then talk about<18:19:56.400> two<18:19:56.820> protocols<18:19:57.540> that<18:19:58.140> we<18:19:58.376> focus<18:19:58.680> on 18:19:58.786 --> 18:19:58.796 align:start position:0% about two protocols that we focus on 18:19:58.796 --> 18:20:02.270 align:start position:0% about two protocols that we focus on with<18:19:59.040> ipsec<18:19:59.756> ah<18:20:00.540> and<18:20:01.080> ESP 18:20:02.270 --> 18:20:02.280 align:start position:0% with ipsec ah and ESP 18:20:02.280 --> 18:20:04.246 align:start position:0% with ipsec ah and ESP we're<18:20:02.820> also<18:20:03.116> going<18:20:03.244> to<18:20:03.360> discuss<18:20:03.720> three 18:20:04.246 --> 18:20:04.256 align:start position:0% we're also going to discuss three 18:20:04.256 --> 18:20:06.590 align:start position:0% we're also going to discuss three different<18:20:04.564> services<18:20:04.976> that<18:20:05.400> ipsec<18:20:06.000> uses<18:20:06.420> or 18:20:06.590 --> 18:20:06.600 align:start position:0% different services that ipsec uses or 18:20:06.600 --> 18:20:10.186 align:start position:0% different services that ipsec uses or serves<18:20:06.960> one<18:20:07.744> is<18:20:07.920> data<18:20:08.460> verification 18:20:10.186 --> 18:20:10.196 align:start position:0% serves one is data verification 18:20:10.196 --> 18:20:12.530 align:start position:0% serves one is data verification protection<18:20:10.860> from<18:20:11.280> data<18:20:11.756> tampering<18:20:12.244> again 18:20:12.530 --> 18:20:12.540 align:start position:0% protection from data tampering again 18:20:12.540 --> 18:20:15.170 align:start position:0% protection from data tampering again getting<18:20:12.900> into<18:20:13.140> that<18:20:13.436> integrity 18:20:15.170 --> 18:20:15.180 align:start position:0% getting into that integrity 18:20:15.180 --> 18:20:18.350 align:start position:0% getting into that integrity and<18:20:15.960> private<18:20:16.796> transactions<18:20:17.516> going<18:20:18.116> along 18:20:18.350 --> 18:20:18.360 align:start position:0% and private transactions going along 18:20:18.360 --> 18:20:21.234 align:start position:0% and private transactions going along with<18:20:18.720> that<18:20:18.976> confidentiality<18:20:19.976> all<18:20:20.936> of<18:20:21.116> this 18:20:21.234 --> 18:20:21.244 align:start position:0% with that confidentiality all of this 18:20:21.244 --> 18:20:23.810 align:start position:0% with that confidentiality all of this supports<18:20:21.900> availability<18:20:22.796> and<18:20:23.336> the<18:20:23.460> reason<18:20:23.580> we 18:20:23.810 --> 18:20:23.820 align:start position:0% supports availability and the reason we 18:20:23.820 --> 18:20:26.390 align:start position:0% supports availability and the reason we have<18:20:24.000> ipsec<18:20:24.720> is<18:20:24.900> to<18:20:25.080> make<18:20:25.256> sure<18:20:25.436> that<18:20:25.744> in<18:20:26.220> our 18:20:26.390 --> 18:20:26.400 align:start position:0% have ipsec is to make sure that in our 18:20:26.400 --> 18:20:30.466 align:start position:0% have ipsec is to make sure that in our security<18:20:26.656> we<18:20:27.656> have<18:20:28.016> available<18:20:28.680> data<18:20:29.820> finally 18:20:30.466 --> 18:20:30.476 align:start position:0% security we have available data finally 18:20:30.476 --> 18:20:31.850 align:start position:0% security we have available data finally I<18:20:30.656> want<18:20:30.780> to<18:20:30.900> talk<18:20:31.016> about<18:20:31.256> some<18:20:31.616> of<18:20:31.744> the 18:20:31.850 --> 18:20:31.860 align:start position:0% I want to talk about some of the 18:20:31.860 --> 18:20:35.450 align:start position:0% I want to talk about some of the policies<18:20:32.400> the<18:20:32.820> ways<18:20:33.116> that<18:20:33.244> we<18:20:33.420> use<18:20:33.600> ipsec 18:20:35.450 --> 18:20:35.460 align:start position:0% policies the ways that we use ipsec 18:20:35.460 --> 18:20:37.490 align:start position:0% policies the ways that we use ipsec so<18:20:36.064> as<18:20:36.244> I<18:20:36.420> mentioned<18:20:36.656> a<18:20:36.836> good<18:20:37.016> amount<18:20:37.256> of<18:20:37.376> the 18:20:37.490 --> 18:20:37.500 align:start position:0% so as I mentioned a good amount of the 18:20:37.500 --> 18:20:39.106 align:start position:0% so as I mentioned a good amount of the security<18:20:37.680> measures<18:20:38.220> that<18:20:38.516> we<18:20:38.640> use<18:20:38.756> on<18:20:39.000> a 18:20:39.106 --> 18:20:39.116 align:start position:0% security measures that we use on a 18:20:39.116 --> 18:20:41.146 align:start position:0% security measures that we use on a network<18:20:39.296> are<18:20:39.836> used<18:20:40.016> to<18:20:40.256> prevent<18:20:40.564> attacks<18:20:41.040> and 18:20:41.146 --> 18:20:41.156 align:start position:0% network are used to prevent attacks and 18:20:41.156 --> 18:20:43.186 align:start position:0% network are used to prevent attacks and shield<18:20:41.400> the<18:20:41.640> network<18:20:41.876> from<18:20:42.476> viruses<18:20:43.016> and 18:20:43.186 --> 18:20:43.196 align:start position:0% shield the network from viruses and 18:20:43.196 --> 18:20:45.466 align:start position:0% shield the network from viruses and other<18:20:43.376> malicious<18:20:43.860> software<18:20:44.280> but<18:20:45.000> not<18:20:45.244> all 18:20:45.466 --> 18:20:45.476 align:start position:0% other malicious software but not all 18:20:45.476 --> 18:20:47.390 align:start position:0% other malicious software but not all security<18:20:45.780> measures<18:20:46.376> are<18:20:46.680> used<18:20:46.860> for<18:20:47.156> the 18:20:47.390 --> 18:20:47.400 align:start position:0% security measures are used for the 18:20:47.400 --> 18:20:50.686 align:start position:0% security measures are used for the preventions<18:20:48.000> of<18:20:48.780> this<18:20:49.140> malicious<18:20:49.680> stuff<18:20:50.040> some 18:20:50.686 --> 18:20:50.696 align:start position:0% preventions of this malicious stuff some 18:20:50.696 --> 18:20:52.246 align:start position:0% preventions of this malicious stuff some are<18:20:51.000> intended<18:20:51.360> to<18:20:51.540> keep<18:20:51.656> data<18:20:52.140> and 18:20:52.246 --> 18:20:52.256 align:start position:0% are intended to keep data and 18:20:52.256 --> 18:20:54.106 align:start position:0% are intended to keep data and Communications<18:20:52.796> secure<18:20:53.580> within<18:20:53.876> a<18:20:54.000> network 18:20:54.106 --> 18:20:54.116 align:start position:0% Communications secure within a network 18:20:54.116 --> 18:20:56.270 align:start position:0% Communications secure within a network while<18:20:54.836> preventing<18:20:55.320> attacks<18:20:55.744> is<18:20:55.860> certainly<18:20:56.156> a 18:20:56.270 --> 18:20:56.280 align:start position:0% while preventing attacks is certainly a 18:20:56.280 --> 18:20:57.950 align:start position:0% while preventing attacks is certainly a part<18:20:56.400> of<18:20:56.580> this<18:20:56.696> there<18:20:57.420> are<18:20:57.540> some<18:20:57.780> security 18:20:57.950 --> 18:20:57.960 align:start position:0% part of this there are some security 18:20:57.960 --> 18:21:01.006 align:start position:0% part of this there are some security measures<18:20:58.564> that<18:20:58.796> exist<18:20:59.100> to<18:20:59.820> establish<18:21:00.360> secure 18:21:01.006 --> 18:21:01.016 align:start position:0% measures that exist to establish secure 18:21:01.016 --> 18:21:03.890 align:start position:0% measures that exist to establish secure and<18:21:01.140> safe<18:21:01.376> communication<18:21:02.156> paths<18:21:02.756> between<18:21:03.360> two 18:21:03.890 --> 18:21:03.900 align:start position:0% and safe communication paths between two 18:21:03.900 --> 18:21:06.826 align:start position:0% and safe communication paths between two parties<18:21:04.320> this<18:21:05.220> is<18:21:05.280> what<18:21:05.580> IP<18:21:06.064> security<18:21:06.420> or 18:21:06.826 --> 18:21:06.836 align:start position:0% parties this is what IP security or 18:21:06.836 --> 18:21:08.866 align:start position:0% parties this is what IP security or ipsec<18:21:07.500> protocols<18:21:08.040> do 18:21:08.866 --> 18:21:08.876 align:start position:0% ipsec protocols do 18:21:08.876 --> 18:21:11.450 align:start position:0% ipsec protocols do they're<18:21:09.476> used<18:21:09.656> to<18:21:09.900> provide<18:21:10.196> a<18:21:10.744> secure<18:21:11.100> channel 18:21:11.450 --> 18:21:11.460 align:start position:0% they're used to provide a secure channel 18:21:11.460 --> 18:21:14.506 align:start position:0% they're used to provide a secure channel of<18:21:11.820> communication<18:21:12.360> between<18:21:12.780> two<18:21:13.196> systems<18:21:13.744> or 18:21:14.506 --> 18:21:14.516 align:start position:0% of communication between two systems or 18:21:14.516 --> 18:21:17.030 align:start position:0% of communication between two systems or more<18:21:14.936> systems<18:21:15.476> these<18:21:16.140> systems<18:21:16.436> can<18:21:16.616> be<18:21:16.744> within 18:21:17.030 --> 18:21:17.040 align:start position:0% more systems these systems can be within 18:21:17.040 --> 18:21:18.770 align:start position:0% more systems these systems can be within a<18:21:17.156> local<18:21:17.336> network<18:21:17.640> within<18:21:18.296> a<18:21:18.476> wide<18:21:18.600> area 18:21:18.770 --> 18:21:18.780 align:start position:0% a local network within a wide area 18:21:18.780 --> 18:21:20.686 align:start position:0% a local network within a wide area network<18:21:19.140> perhaps<18:21:19.744> even<18:21:19.920> over<18:21:20.156> a<18:21:20.460> virtual 18:21:20.686 --> 18:21:20.696 align:start position:0% network perhaps even over a virtual 18:21:20.696 --> 18:21:23.270 align:start position:0% network perhaps even over a virtual private<18:21:21.116> Network<18:21:21.296> now<18:21:22.196> some<18:21:22.616> people<18:21:22.860> might 18:21:23.270 --> 18:21:23.280 align:start position:0% private Network now some people might 18:21:23.280 --> 18:21:25.310 align:start position:0% private Network now some people might think<18:21:23.460> that<18:21:23.756> data<18:21:24.180> traveling<18:21:24.600> within<18:21:25.016> a<18:21:25.196> local 18:21:25.310 --> 18:21:25.320 align:start position:0% think that data traveling within a local 18:21:25.320 --> 18:21:27.466 align:start position:0% think that data traveling within a local network<18:21:25.616> is<18:21:25.920> secure<18:21:26.220> but<18:21:26.516> this<18:21:27.180> is<18:21:27.360> only 18:21:27.466 --> 18:21:27.476 align:start position:0% network is secure but this is only 18:21:27.476 --> 18:21:30.646 align:start position:0% network is secure but this is only sometimes<18:21:28.140> true<18:21:28.376> imagine<18:21:29.280> that<18:21:29.696> someone<18:21:30.000> has 18:21:30.646 --> 18:21:30.656 align:start position:0% sometimes true imagine that someone has 18:21:30.656 --> 18:21:32.030 align:start position:0% sometimes true imagine that someone has hacked<18:21:31.140> into<18:21:31.196> our<18:21:31.436> Network<18:21:31.616> and<18:21:31.920> we're 18:21:32.030 --> 18:21:32.040 align:start position:0% hacked into our Network and we're 18:21:32.040 --> 18:21:34.490 align:start position:0% hacked into our Network and we're sending<18:21:32.460> data<18:21:32.876> across<18:21:33.360> it<18:21:33.540> well<18:21:34.080> now<18:21:34.196> we<18:21:34.376> want 18:21:34.490 --> 18:21:34.500 align:start position:0% sending data across it well now we want 18:21:34.500 --> 18:21:35.926 align:start position:0% sending data across it well now we want to<18:21:34.564> make<18:21:34.680> sure<18:21:34.796> that<18:21:34.976> the<18:21:35.156> data<18:21:35.400> itself<18:21:35.696> is 18:21:35.926 --> 18:21:35.936 align:start position:0% to make sure that the data itself is 18:21:35.936 --> 18:21:38.390 align:start position:0% to make sure that the data itself is secure<18:21:36.244> so<18:21:37.016> while<18:21:37.196> the<18:21:37.500> entire<18:21:37.744> network<18:21:37.976> might 18:21:38.390 --> 18:21:38.400 align:start position:0% secure so while the entire network might 18:21:38.400 --> 18:21:41.390 align:start position:0% secure so while the entire network might be<18:21:38.580> protected<18:21:39.064> by<18:21:39.296> firewalls<18:21:39.960> antivirus<18:21:40.616> IDs 18:21:41.390 --> 18:21:41.400 align:start position:0% be protected by firewalls antivirus IDs 18:21:41.400 --> 18:21:43.966 align:start position:0% be protected by firewalls antivirus IDs IPS<18:21:41.836> there<18:21:42.836> might<18:21:43.080> be<18:21:43.140> nothing<18:21:43.376> protecting 18:21:43.966 --> 18:21:43.976 align:start position:0% IPS there might be nothing protecting 18:21:43.976 --> 18:21:45.590 align:start position:0% IPS there might be nothing protecting the<18:21:44.156> actual<18:21:44.460> connection<18:21:44.696> between<18:21:45.116> the<18:21:45.420> two 18:21:45.590 --> 18:21:45.600 align:start position:0% the actual connection between the two 18:21:45.600 --> 18:21:48.710 align:start position:0% the actual connection between the two users<18:21:46.040> generally<18:21:47.040> the<18:21:47.820> data<18:21:48.180> that<18:21:48.296> gets<18:21:48.600> sent 18:21:48.710 --> 18:21:48.720 align:start position:0% users generally the data that gets sent 18:21:48.720 --> 18:21:51.590 align:start position:0% users generally the data that gets sent across<18:21:49.140> the<18:21:49.196> network<18:21:49.436> is<18:21:50.336> not<18:21:50.696> really<18:21:50.936> heavily 18:21:51.590 --> 18:21:51.600 align:start position:0% across the network is not really heavily 18:21:51.600 --> 18:21:53.686 align:start position:0% across the network is not really heavily protected<18:21:52.080> or<18:21:52.256> didn't<18:21:52.436> used<18:21:52.744> to<18:21:52.920> be<18:21:52.976> so<18:21:53.580> people 18:21:53.686 --> 18:21:53.696 align:start position:0% protected or didn't used to be so people 18:21:53.696 --> 18:21:55.130 align:start position:0% protected or didn't used to be so people tend<18:21:54.000> to<18:21:54.116> think<18:21:54.244> that<18:21:54.360> just<18:21:54.600> because<18:21:54.720> their 18:21:55.130 --> 18:21:55.140 align:start position:0% tend to think that just because their 18:21:55.140 --> 18:21:56.746 align:start position:0% tend to think that just because their network<18:21:55.436> has<18:21:55.796> a<18:21:56.040> shield<18:21:56.156> around<18:21:56.460> it 18:21:56.746 --> 18:21:56.756 align:start position:0% network has a shield around it 18:21:56.756 --> 18:21:59.210 align:start position:0% network has a shield around it everything<18:21:57.360> inside<18:21:57.656> it<18:21:57.960> is<18:21:58.140> safe<18:21:58.320> as<18:21:58.500> well<18:21:58.680> but 18:21:59.210 --> 18:21:59.220 align:start position:0% everything inside it is safe as well but 18:21:59.220 --> 18:22:01.366 align:start position:0% everything inside it is safe as well but this<18:21:59.460> isn't<18:21:59.696> the<18:21:59.936> case<18:22:00.180> it's<18:22:00.780> important<18:22:01.140> to 18:22:01.366 --> 18:22:01.376 align:start position:0% this isn't the case it's important to 18:22:01.376 --> 18:22:04.490 align:start position:0% this isn't the case it's important to have<18:22:01.500> ipsec<18:22:02.336> protocols<18:22:02.936> in<18:22:03.244> place<18:22:03.420> to<18:22:04.196> secure 18:22:04.490 --> 18:22:04.500 align:start position:0% have ipsec protocols in place to secure 18:22:04.500 --> 18:22:06.410 align:start position:0% have ipsec protocols in place to secure the<18:22:04.796> data<18:22:05.100> sent<18:22:05.280> and<18:22:05.580> the<18:22:05.756> connections<18:22:06.180> made 18:22:06.410 --> 18:22:06.420 align:start position:0% the data sent and the connections made 18:22:06.420 --> 18:22:09.770 align:start position:0% the data sent and the connections made over<18:22:06.720> a<18:22:07.016> network<18:22:07.196> both<18:22:07.680> local<18:22:08.040> and<18:22:08.400> wide<18:22:08.580> area 18:22:09.770 --> 18:22:09.780 align:start position:0% over a network both local and wide area 18:22:09.780 --> 18:22:11.990 align:start position:0% over a network both local and wide area now<18:22:10.320> there<18:22:10.616> are<18:22:10.744> two<18:22:10.920> main<18:22:11.156> protocols<18:22:11.756> that 18:22:11.990 --> 18:22:12.000 align:start position:0% now there are two main protocols that 18:22:12.000 --> 18:22:16.310 align:start position:0% now there are two main protocols that are<18:22:12.116> categorized<18:22:12.720> in<18:22:12.836> ipsec<18:22:13.976> they<18:22:14.580> are<18:22:15.180> ah<18:22:16.016> or 18:22:16.310 --> 18:22:16.320 align:start position:0% are categorized in ipsec they are ah or 18:22:16.320 --> 18:22:19.554 align:start position:0% are categorized in ipsec they are ah or authentication<18:22:17.040> header<18:22:17.580> and<18:22:18.360> ESP<18:22:18.600> the 18:22:19.554 --> 18:22:19.564 align:start position:0% authentication header and ESP the 18:22:19.564 --> 18:22:22.366 align:start position:0% authentication header and ESP the encapsulating<18:22:20.280> security<18:22:20.936> payload<18:22:21.780> let's 18:22:22.366 --> 18:22:22.376 align:start position:0% encapsulating security payload let's 18:22:22.376 --> 18:22:23.926 align:start position:0% encapsulating security payload let's talk<18:22:22.616> a<18:22:22.860> little<18:22:22.976> bit<18:22:23.100> more<18:22:23.220> about<18:22:23.400> what<18:22:23.696> these 18:22:23.926 --> 18:22:23.936 align:start position:0% talk a little bit more about what these 18:22:23.936 --> 18:22:24.826 align:start position:0% talk a little bit more about what these are 18:22:24.826 --> 18:22:24.836 align:start position:0% are 18:22:24.836 --> 18:22:28.554 align:start position:0% are as<18:22:25.140> the<18:22:25.320> name<18:22:25.436> States<18:22:25.744> ah<18:22:26.780> or<18:22:27.780> authentication 18:22:28.554 --> 18:22:28.564 align:start position:0% as the name States ah or authentication 18:22:28.564 --> 18:22:31.450 align:start position:0% as the name States ah or authentication header<18:22:29.100> is<18:22:29.756> used<18:22:30.000> to<18:22:30.376> authenticate 18:22:31.450 --> 18:22:31.460 align:start position:0% header is used to authenticate 18:22:31.460 --> 18:22:34.786 align:start position:0% header is used to authenticate connections<18:22:32.460> made<18:22:33.180> over<18:22:33.360> a<18:22:33.600> network<18:22:33.720> it<18:22:34.616> does 18:22:34.786 --> 18:22:34.796 align:start position:0% connections made over a network it does 18:22:34.796 --> 18:22:39.234 align:start position:0% connections made over a network it does this<18:22:34.976> by<18:22:35.400> checking<18:22:35.876> the<18:22:36.180> IP<18:22:36.540> address 18:22:39.234 --> 18:22:39.244 align:start position:0% 18:22:39.244 --> 18:22:40.910 align:start position:0% of<18:22:39.780> the<18:22:39.960> users<18:22:40.256> that<18:22:40.436> are<18:22:40.564> trying<18:22:40.744> to 18:22:40.910 --> 18:22:40.920 align:start position:0% of the users that are trying to 18:22:40.920 --> 18:22:42.410 align:start position:0% of the users that are trying to communicate<18:22:41.400> and<18:22:41.756> make<18:22:41.876> sure<18:22:42.064> that<18:22:42.296> they're 18:22:42.410 --> 18:22:42.420 align:start position:0% communicate and make sure that they're 18:22:42.420 --> 18:22:46.734 align:start position:0% communicate and make sure that they're trusted<18:22:42.900> it<18:22:43.860> also<18:22:44.156> checks<18:22:44.580> the<18:22:45.296> Integrity<18:22:45.836> of 18:22:46.734 --> 18:22:46.744 align:start position:0% trusted it also checks the Integrity of 18:22:46.744 --> 18:22:48.890 align:start position:0% trusted it also checks the Integrity of the<18:22:46.920> data<18:22:47.156> packets<18:22:47.516> that<18:22:47.696> are<18:22:47.820> being<18:22:48.000> sent<18:22:48.296> in 18:22:48.890 --> 18:22:48.900 align:start position:0% the data packets that are being sent in 18:22:48.900 --> 18:22:50.926 align:start position:0% the data packets that are being sent in other<18:22:48.960> words<18:22:49.140> is<18:22:49.860> this<18:22:50.040> the<18:22:50.220> data<18:22:50.516> that<18:22:50.696> we 18:22:50.926 --> 18:22:50.936 align:start position:0% other words is this the data that we 18:22:50.936 --> 18:22:52.734 align:start position:0% other words is this the data that we actually<18:22:51.116> intended<18:22:51.656> and<18:22:52.016> was<18:22:52.140> it<18:22:52.320> received 18:22:52.734 --> 18:22:52.744 align:start position:0% actually intended and was it received 18:22:52.744 --> 18:22:53.990 align:start position:0% actually intended and was it received properly 18:22:53.990 --> 18:22:54.000 align:start position:0% properly 18:22:54.000 --> 18:22:56.326 align:start position:0% properly the<18:22:54.540> other<18:22:54.656> one<18:22:54.920> encapsulating<18:22:55.920> security 18:22:56.326 --> 18:22:56.336 align:start position:0% the other one encapsulating security 18:22:56.336 --> 18:22:59.866 align:start position:0% the other one encapsulating security payload<18:22:57.064> or<18:22:57.420> ESP<18:22:57.680> is<18:22:58.680> used<18:22:58.920> for<18:22:59.220> encryption 18:22:59.866 --> 18:22:59.876 align:start position:0% payload or ESP is used for encryption 18:22:59.876 --> 18:23:01.670 align:start position:0% payload or ESP is used for encryption Services<18:23:00.116> which<18:23:00.780> I<18:23:01.016> think<18:23:01.140> we've<18:23:01.376> talked 18:23:01.670 --> 18:23:01.680 align:start position:0% Services which I think we've talked 18:23:01.680 --> 18:23:03.890 align:start position:0% Services which I think we've talked about<18:23:01.744> it<18:23:02.580> encrypts<18:23:02.936> data<18:23:03.244> that's<18:23:03.360> being<18:23:03.600> sent 18:23:03.890 --> 18:23:03.900 align:start position:0% about it encrypts data that's being sent 18:23:03.900 --> 18:23:07.554 align:start position:0% about it encrypts data that's being sent over<18:23:04.256> a<18:23:04.564> network<18:23:04.820> using<18:23:05.820> ah<18:23:06.600> to<18:23:07.016> authenticate 18:23:07.554 --> 18:23:07.564 align:start position:0% over a network using ah to authenticate 18:23:07.564 --> 18:23:10.910 align:start position:0% over a network using ah to authenticate the<18:23:07.744> users<18:23:08.156> ESP<18:23:08.780> will<18:23:09.780> only<18:23:09.960> give<18:23:10.196> the<18:23:10.500> keys<18:23:10.796> to 18:23:10.910 --> 18:23:10.920 align:start position:0% the users ESP will only give the keys to 18:23:10.920 --> 18:23:13.210 align:start position:0% the users ESP will only give the keys to the<18:23:11.100> users<18:23:11.400> that<18:23:11.640> have<18:23:11.820> been<18:23:12.196> authenticated 18:23:13.210 --> 18:23:13.220 align:start position:0% the users that have been authenticated 18:23:13.220 --> 18:23:18.530 align:start position:0% the users that have been authenticated so<18:23:14.220> I<18:23:14.756> make<18:23:15.000> sure<18:23:15.180> to<18:23:15.780> authenticate<18:23:16.564> using<18:23:17.280> ah 18:23:18.530 --> 18:23:18.540 align:start position:0% so I make sure to authenticate using ah 18:23:18.540 --> 18:23:20.270 align:start position:0% so I make sure to authenticate using ah that<18:23:19.196> this<18:23:19.376> is<18:23:19.500> the<18:23:19.616> user<18:23:19.860> I<18:23:19.976> want<18:23:20.100> to<18:23:20.220> give 18:23:20.270 --> 18:23:20.280 align:start position:0% that this is the user I want to give 18:23:20.280 --> 18:23:24.170 align:start position:0% that this is the user I want to give something<18:23:20.516> to<18:23:20.820> and<18:23:21.540> then<18:23:21.720> the<18:23:21.900> ESP 18:23:24.170 --> 18:23:24.180 align:start position:0% 18:23:24.180 --> 18:23:26.466 align:start position:0% does<18:23:24.720> the<18:23:24.960> encryption 18:23:26.466 --> 18:23:26.476 align:start position:0% does the encryption 18:23:26.476 --> 18:23:28.670 align:start position:0% does the encryption for<18:23:27.476> the<18:23:27.836> people<18:23:28.080> who<18:23:28.376> have<18:23:28.500> been 18:23:28.670 --> 18:23:28.680 align:start position:0% for the people who have been 18:23:28.680 --> 18:23:32.630 align:start position:0% for the people who have been authenticated<18:23:29.360> providing<18:23:30.564> Keys<18:23:31.564> only<18:23:32.280> to<18:23:32.516> the 18:23:32.630 --> 18:23:32.640 align:start position:0% authenticated providing Keys only to the 18:23:32.640 --> 18:23:35.146 align:start position:0% authenticated providing Keys only to the people<18:23:32.820> who<18:23:33.360> meet<18:23:33.540> the<18:23:33.720> first<18:23:33.900> condition<18:23:34.156> now 18:23:35.146 --> 18:23:35.156 align:start position:0% people who meet the first condition now 18:23:35.156 --> 18:23:36.826 align:start position:0% people who meet the first condition now if<18:23:35.280> this<18:23:35.400> seems<18:23:35.696> like<18:23:35.876> a<18:23:36.116> broad<18:23:36.244> overview<18:23:36.720> of 18:23:36.826 --> 18:23:36.836 align:start position:0% if this seems like a broad overview of 18:23:36.836 --> 18:23:38.990 align:start position:0% if this seems like a broad overview of these<18:23:37.140> two<18:23:37.256> it<18:23:37.744> is<18:23:37.920> we're<18:23:38.460> not<18:23:38.640> going<18:23:38.756> to<18:23:38.876> see 18:23:38.990 --> 18:23:39.000 align:start position:0% these two it is we're not going to see 18:23:39.000 --> 18:23:41.030 align:start position:0% these two it is we're not going to see this<18:23:39.296> a<18:23:39.720> whole<18:23:39.900> lot<18:23:40.080> on<18:23:40.500> the<18:23:40.616> network<18:23:40.744> plus 18:23:41.030 --> 18:23:41.040 align:start position:0% this a whole lot on the network plus 18:23:41.040 --> 18:23:44.270 align:start position:0% this a whole lot on the network plus exam<18:23:41.516> maybe<18:23:42.296> one<18:23:42.720> question<18:23:42.960> but<18:23:43.860> it's<18:23:44.100> not 18:23:44.270 --> 18:23:44.280 align:start position:0% exam maybe one question but it's not 18:23:44.280 --> 18:23:45.890 align:start position:0% exam maybe one question but it's not really<18:23:44.516> worth<18:23:44.756> going<18:23:45.064> into<18:23:45.296> depth<18:23:45.720> because 18:23:45.890 --> 18:23:45.900 align:start position:0% really worth going into depth because 18:23:45.900 --> 18:23:47.926 align:start position:0% really worth going into depth because that's<18:23:46.256> what<18:23:46.500> Security<18:23:46.796> Plus<18:23:47.220> is<18:23:47.516> going<18:23:47.696> to<18:23:47.820> do 18:23:47.926 --> 18:23:47.936 align:start position:0% that's what Security Plus is going to do 18:23:47.936 --> 18:23:49.670 align:start position:0% that's what Security Plus is going to do and<18:23:48.420> when<18:23:48.600> you<18:23:48.656> talk<18:23:48.836> about<18:23:48.960> Security<18:23:49.320> Plus 18:23:49.670 --> 18:23:49.680 align:start position:0% and when you talk about Security Plus 18:23:49.680 --> 18:23:51.530 align:start position:0% and when you talk about Security Plus you're<18:23:50.040> really<18:23:50.220> going<18:23:50.336> to<18:23:50.460> talk<18:23:50.580> about<18:23:50.756> these 18:23:51.530 --> 18:23:51.540 align:start position:0% you're really going to talk about these 18:23:51.540 --> 18:23:55.186 align:start position:0% you're really going to talk about these nip<18:23:51.960> Security<18:23:52.376> in<18:23:53.156> more<18:23:53.280> depth<18:23:53.640> then 18:23:55.186 --> 18:23:55.196 align:start position:0% nip Security in more depth then 18:23:55.196 --> 18:23:56.686 align:start position:0% nip Security in more depth then and<18:23:55.616> there<18:23:55.744> are<18:23:55.920> a<18:23:55.976> few<18:23:56.040> benefits<18:23:56.516> and 18:23:56.686 --> 18:23:56.696 align:start position:0% and there are a few benefits and 18:23:56.696 --> 18:23:59.146 align:start position:0% and there are a few benefits and services<18:23:56.936> that<18:23:57.540> ipsec<18:23:58.196> protocols<18:23:58.796> provide 18:23:59.146 --> 18:23:59.156 align:start position:0% services that ipsec protocols provide 18:23:59.156 --> 18:24:02.990 align:start position:0% services that ipsec protocols provide the<18:24:00.064> first<18:24:00.244> service<18:24:00.476> is<18:24:01.016> data<18:24:01.616> verification 18:24:02.990 --> 18:24:03.000 align:start position:0% the first service is data verification 18:24:03.000 --> 18:24:06.170 align:start position:0% the first service is data verification this<18:24:03.656> service<18:24:03.836> ensures<18:24:04.320> that<18:24:04.680> the<18:24:04.920> data<18:24:05.336> that 18:24:06.170 --> 18:24:06.180 align:start position:0% this service ensures that the data that 18:24:06.180 --> 18:24:08.270 align:start position:0% this service ensures that the data that is<18:24:06.296> being<18:24:06.540> sent<18:24:06.836> across<18:24:07.436> the<18:24:07.500> network<18:24:07.680> is 18:24:08.270 --> 18:24:08.280 align:start position:0% is being sent across the network is 18:24:08.280 --> 18:24:10.910 align:start position:0% is being sent across the network is coming<18:24:08.516> from<18:24:08.936> a<18:24:09.540> legitimate<18:24:10.016> Source<18:24:10.500> or 18:24:10.910 --> 18:24:10.920 align:start position:0% coming from a legitimate Source or 18:24:10.920 --> 18:24:12.770 align:start position:0% coming from a legitimate Source or legitimate<18:24:11.460> place 18:24:12.770 --> 18:24:12.780 align:start position:0% legitimate place 18:24:12.780 --> 18:24:15.826 align:start position:0% legitimate place they<18:24:13.436> make<18:24:13.616> sure<18:24:13.976> that<18:24:14.756> the<18:24:14.936> end<18:24:15.116> users<18:24:15.540> are 18:24:15.826 --> 18:24:15.836 align:start position:0% they make sure that the end users are 18:24:15.836 --> 18:24:17.810 align:start position:0% they make sure that the end users are the<18:24:16.080> intended<18:24:16.616> users<18:24:16.920> and<18:24:17.156> to<18:24:17.336> keep<18:24:17.460> an<18:24:17.580> eye<18:24:17.696> on 18:24:17.810 --> 18:24:17.820 align:start position:0% the intended users and to keep an eye on 18:24:17.820 --> 18:24:19.490 align:start position:0% the intended users and to keep an eye on packets<18:24:18.180> as<18:24:18.420> they<18:24:18.656> travel<18:24:18.836> across<18:24:19.376> the 18:24:19.490 --> 18:24:19.500 align:start position:0% packets as they travel across the 18:24:19.500 --> 18:24:20.450 align:start position:0% packets as they travel across the network 18:24:20.450 --> 18:24:20.460 align:start position:0% network 18:24:20.460 --> 18:24:22.850 align:start position:0% network the<18:24:20.936> next<18:24:21.064> service<18:24:21.360> that<18:24:21.720> ipsec<18:24:22.436> is<18:24:22.564> going<18:24:22.744> to 18:24:22.850 --> 18:24:22.860 align:start position:0% the next service that ipsec is going to 18:24:22.860 --> 18:24:25.186 align:start position:0% the next service that ipsec is going to provide<18:24:23.100> is<18:24:23.820> protection<18:24:24.244> from<18:24:24.720> data 18:24:25.186 --> 18:24:25.196 align:start position:0% provide is protection from data 18:24:25.196 --> 18:24:28.734 align:start position:0% provide is protection from data tampering<18:24:25.680> again<18:24:26.280> that<18:24:26.936> integrity 18:24:28.734 --> 18:24:28.744 align:start position:0% tampering again that integrity 18:24:28.744 --> 18:24:30.826 align:start position:0% tampering again that integrity service<18:24:29.220> make<18:24:29.580> sure<18:24:29.696> that<18:24:29.876> while<18:24:30.064> data<18:24:30.476> is<18:24:30.656> in 18:24:30.826 --> 18:24:30.836 align:start position:0% service make sure that while data is in 18:24:30.836 --> 18:24:33.234 align:start position:0% service make sure that while data is in transit<18:24:31.256> nothing<18:24:31.564> changes<18:24:32.100> this<18:24:32.640> could<18:24:33.064> mean 18:24:33.234 --> 18:24:33.244 align:start position:0% transit nothing changes this could mean 18:24:33.244 --> 18:24:35.746 align:start position:0% transit nothing changes this could mean the<18:24:33.780> data<18:24:34.016> somehow<18:24:34.320> becomes<18:24:34.744> corrupted<18:24:35.220> or 18:24:35.746 --> 18:24:35.756 align:start position:0% the data somehow becomes corrupted or 18:24:35.756 --> 18:24:37.606 align:start position:0% the data somehow becomes corrupted or that<18:24:35.936> someone<18:24:36.180> literally<18:24:36.720> tampers<18:24:37.196> with<18:24:37.436> it 18:24:37.606 --> 18:24:37.616 align:start position:0% that someone literally tampers with it 18:24:37.616 --> 18:24:40.246 align:start position:0% that someone literally tampers with it again<18:24:38.156> while<18:24:38.580> ipsec<18:24:39.296> protocols<18:24:39.900> provide 18:24:40.246 --> 18:24:40.256 align:start position:0% again while ipsec protocols provide 18:24:40.256 --> 18:24:42.106 align:start position:0% again while ipsec protocols provide secure<18:24:40.744> Communications<18:24:41.280> within<18:24:41.820> the<18:24:41.936> network 18:24:42.106 --> 18:24:42.116 align:start position:0% secure Communications within the network 18:24:42.116 --> 18:24:44.090 align:start position:0% secure Communications within the network they<18:24:42.780> don't<18:24:42.960> actually<18:24:43.140> stop<18:24:43.500> an<18:24:43.744> attacker 18:24:44.090 --> 18:24:44.100 align:start position:0% they don't actually stop an attacker 18:24:44.100 --> 18:24:46.006 align:start position:0% they don't actually stop an attacker from<18:24:44.336> entering<18:24:44.756> the<18:24:44.876> network<18:24:45.064> so<18:24:45.720> while<18:24:45.900> there 18:24:46.006 --> 18:24:46.016 align:start position:0% from entering the network so while there 18:24:46.016 --> 18:24:47.570 align:start position:0% from entering the network so while there is<18:24:46.196> a<18:24:46.320> chance<18:24:46.500> of<18:24:46.796> an<18:24:46.976> attacker<18:24:47.336> on<18:24:47.460> the 18:24:47.570 --> 18:24:47.580 align:start position:0% is a chance of an attacker on the 18:24:47.580 --> 18:24:49.966 align:start position:0% is a chance of an attacker on the network<18:24:47.696> they<18:24:48.656> can't<18:24:48.836> tamper<18:24:49.320> with<18:24:49.500> the<18:24:49.744> data 18:24:49.966 --> 18:24:49.976 align:start position:0% network they can't tamper with the data 18:24:49.976 --> 18:24:52.310 align:start position:0% network they can't tamper with the data as<18:24:50.156> it<18:24:50.400> travels<18:24:50.696> through<18:24:50.876> because<18:24:51.296> ipsec<18:24:52.140> is 18:24:52.310 --> 18:24:52.320 align:start position:0% as it travels through because ipsec is 18:24:52.320 --> 18:24:54.054 align:start position:0% as it travels through because ipsec is going<18:24:52.436> to<18:24:52.500> make<18:24:52.616> sure<18:24:52.744> that<18:24:52.920> doesn't<18:24:53.040> happen 18:24:54.054 --> 18:24:54.064 align:start position:0% going to make sure that doesn't happen 18:24:54.064 --> 18:24:57.466 align:start position:0% going to make sure that doesn't happen finally<18:24:55.040> ipsec<18:24:56.040> provides<18:24:56.640> private 18:24:57.466 --> 18:24:57.476 align:start position:0% finally ipsec provides private 18:24:57.476 --> 18:24:59.990 align:start position:0% finally ipsec provides private transactions<18:24:58.256> over<18:24:58.500> the<18:24:58.744> network<18:24:58.860> this<18:24:59.756> means 18:24:59.990 --> 18:25:00.000 align:start position:0% transactions over the network this means 18:25:00.000 --> 18:25:02.390 align:start position:0% transactions over the network this means that<18:25:00.244> data<18:25:00.720> is<18:25:01.196> unreadable<18:25:01.860> by<18:25:02.156> everyone 18:25:02.390 --> 18:25:02.400 align:start position:0% that data is unreadable by everyone 18:25:02.400 --> 18:25:05.030 align:start position:0% that data is unreadable by everyone except<18:25:03.244> the<18:25:03.600> end<18:25:03.720> users<18:25:04.140> this<18:25:04.616> is<18:25:04.680> where<18:25:04.860> that 18:25:05.030 --> 18:25:05.040 align:start position:0% except the end users this is where that 18:25:05.040 --> 18:25:07.186 align:start position:0% except the end users this is where that authentication<18:25:05.696> comes<18:25:06.180> in<18:25:06.296> and<18:25:07.016> where 18:25:07.186 --> 18:25:07.196 align:start position:0% authentication comes in and where 18:25:07.196 --> 18:25:10.130 align:start position:0% authentication comes in and where confidentiality<18:25:08.100> comes<18:25:08.460> into<18:25:08.580> play 18:25:10.130 --> 18:25:10.140 align:start position:0% confidentiality comes into play 18:25:10.140 --> 18:25:12.170 align:start position:0% confidentiality comes into play for<18:25:10.564> example<18:25:10.744> if<18:25:11.040> Mike<18:25:11.280> and<18:25:11.516> Steve<18:25:11.696> have<18:25:12.000> to 18:25:12.170 --> 18:25:12.180 align:start position:0% for example if Mike and Steve have to 18:25:12.180 --> 18:25:13.966 align:start position:0% for example if Mike and Steve have to send<18:25:12.360> some<18:25:12.600> private<18:25:12.900> banking<18:25:13.256> information<18:25:13.500> to 18:25:13.966 --> 18:25:13.976 align:start position:0% send some private banking information to 18:25:13.976 --> 18:25:15.890 align:start position:0% send some private banking information to each<18:25:14.156> other<18:25:14.336> the<18:25:15.000> service<18:25:15.180> makes<18:25:15.540> sure<18:25:15.720> that 18:25:15.890 --> 18:25:15.900 align:start position:0% each other the service makes sure that 18:25:15.900 --> 18:25:17.810 align:start position:0% each other the service makes sure that Mike<18:25:16.140> and<18:25:16.320> Steve<18:25:16.500> were<18:25:16.796> the<18:25:17.040> only<18:25:17.280> people<18:25:17.516> who 18:25:17.810 --> 18:25:17.820 align:start position:0% Mike and Steve were the only people who 18:25:17.820 --> 18:25:19.910 align:start position:0% Mike and Steve were the only people who can<18:25:17.936> read<18:25:18.116> it<18:25:18.296> this<18:25:18.960> isn't<18:25:19.256> happening<18:25:19.616> at<18:25:19.796> any 18:25:19.910 --> 18:25:19.920 align:start position:0% can read it this isn't happening at any 18:25:19.920 --> 18:25:22.310 align:start position:0% can read it this isn't happening at any level<18:25:20.100> that<18:25:20.460> you<18:25:20.696> can<18:25:20.820> see<18:25:21.180> it's<18:25:22.016> happening 18:25:22.310 --> 18:25:22.320 align:start position:0% level that you can see it's happening 18:25:22.320 --> 18:25:24.106 align:start position:0% level that you can see it's happening all<18:25:22.564> within<18:25:22.920> the<18:25:23.100> protocols<18:25:23.580> that<18:25:23.936> already 18:25:24.106 --> 18:25:24.116 align:start position:0% all within the protocols that already 18:25:24.116 --> 18:25:27.426 align:start position:0% all within the protocols that already exist<18:25:24.720> when<18:25:25.564> we<18:25:25.680> talked<18:25:26.040> much<18:25:26.280> earlier<18:25:26.640> about 18:25:27.426 --> 18:25:27.436 align:start position:0% exist when we talked much earlier about 18:25:27.436 --> 18:25:29.950 align:start position:0% exist when we talked much earlier about ipv4<18:25:28.436> versus 18:25:29.950 --> 18:25:29.960 align:start position:0% ipv4 versus 18:25:29.960 --> 18:25:33.530 align:start position:0% ipv4 versus IPv6<18:25:30.960> one<18:25:31.680> of<18:25:31.744> the<18:25:31.860> great<18:25:32.040> benefits<18:25:32.516> of<18:25:32.696> IPv6 18:25:33.530 --> 18:25:33.540 align:start position:0% IPv6 one of the great benefits of IPv6 18:25:33.540 --> 18:25:36.410 align:start position:0% IPv6 one of the great benefits of IPv6 is<18:25:34.080> it<18:25:34.196> has<18:25:34.376> all<18:25:34.616> the<18:25:34.744> ipsec<18:25:35.580> stuff<18:25:35.876> built<18:25:36.360> in 18:25:36.410 --> 18:25:36.420 align:start position:0% is it has all the ipsec stuff built in 18:25:36.420 --> 18:25:38.530 align:start position:0% is it has all the ipsec stuff built in so<18:25:37.140> all<18:25:37.376> of<18:25:37.500> this<18:25:37.680> is<18:25:37.920> happening 18:25:38.530 --> 18:25:38.540 align:start position:0% so all of this is happening 18:25:38.540 --> 18:25:41.286 align:start position:0% so all of this is happening automatically<18:25:39.540> within<18:25:40.256> our<18:25:40.616> new<18:25:40.796> version<18:25:41.040> of 18:25:41.286 --> 18:25:41.296 align:start position:0% automatically within our new version of 18:25:41.296 --> 18:25:43.850 align:start position:0% automatically within our new version of IPv6<18:25:42.296> it's<18:25:42.900> not<18:25:43.140> even<18:25:43.256> something<18:25:43.436> we<18:25:43.616> need<18:25:43.744> to 18:25:43.850 --> 18:25:43.860 align:start position:0% IPv6 it's not even something we need to 18:25:43.860 --> 18:25:45.466 align:start position:0% IPv6 it's not even something we need to really<18:25:43.976> worry<18:25:44.336> about<18:25:44.516> just<18:25:45.064> something<18:25:45.244> we 18:25:45.466 --> 18:25:45.476 align:start position:0% really worry about just something we 18:25:45.476 --> 18:25:47.326 align:start position:0% really worry about just something we need<18:25:45.600> to<18:25:45.720> know<18:25:45.780> is<18:25:46.016> taking<18:25:46.256> place<18:25:46.564> so<18:25:47.040> we<18:25:47.156> can 18:25:47.326 --> 18:25:47.336 align:start position:0% need to know is taking place so we can 18:25:47.336 --> 18:25:49.186 align:start position:0% need to know is taking place so we can be<18:25:47.400> a<18:25:47.516> little<18:25:47.640> more<18:25:47.820> sure<18:25:48.064> that<18:25:48.600> our<18:25:48.720> data<18:25:49.080> is 18:25:49.186 --> 18:25:49.196 align:start position:0% be a little more sure that our data is 18:25:49.196 --> 18:25:51.286 align:start position:0% be a little more sure that our data is actually<18:25:49.376> being<18:25:49.616> secured 18:25:51.286 --> 18:25:51.296 align:start position:0% actually being secured 18:25:51.296 --> 18:25:54.710 align:start position:0% actually being secured so<18:25:51.960> here<18:25:52.376> is<18:25:52.564> what<18:25:52.744> ipsec<18:25:53.460> might<18:25:53.756> look<18:25:54.000> like<18:25:54.116> if 18:25:54.710 --> 18:25:54.720 align:start position:0% so here is what ipsec might look like if 18:25:54.720 --> 18:25:56.810 align:start position:0% so here is what ipsec might look like if they<18:25:54.900> were<18:25:55.016> connecting<18:25:55.436> two<18:25:55.680> lands<18:25:56.100> to<18:25:56.336> make<18:25:56.460> a 18:25:56.810 --> 18:25:56.820 align:start position:0% they were connecting two lands to make a 18:25:56.820 --> 18:25:57.710 align:start position:0% they were connecting two lands to make a Wan 18:25:57.710 --> 18:25:57.720 align:start position:0% Wan 18:25:57.720 --> 18:25:59.746 align:start position:0% Wan though<18:25:58.320> the<18:25:58.564> two<18:25:58.680> networks<18:25:59.100> have<18:25:59.280> their<18:25:59.580> own 18:25:59.746 --> 18:25:59.756 align:start position:0% though the two networks have their own 18:25:59.756 --> 18:26:01.966 align:start position:0% though the two networks have their own firewalls<18:26:00.476> and<18:26:00.540> Protection<18:26:00.900> Systems<18:26:01.500> they 18:26:01.966 --> 18:26:01.976 align:start position:0% firewalls and Protection Systems they 18:26:01.976 --> 18:26:03.170 align:start position:0% firewalls and Protection Systems they still<18:26:02.156> have<18:26:02.336> to<18:26:02.460> connect<18:26:02.640> the<18:26:03.000> Republic 18:26:03.170 --> 18:26:03.180 align:start position:0% still have to connect the Republic 18:26:03.180 --> 18:26:05.030 align:start position:0% still have to connect the Republic Network<18:26:03.656> which<18:26:04.016> we<18:26:04.140> know<18:26:04.256> isn't<18:26:04.616> the<18:26:04.744> safest 18:26:05.030 --> 18:26:05.040 align:start position:0% Network which we know isn't the safest 18:26:05.040 --> 18:26:07.186 align:start position:0% Network which we know isn't the safest thing<18:26:05.280> this<18:26:05.936> is<18:26:06.064> especially<18:26:06.476> true<18:26:06.720> in<18:26:07.016> the 18:26:07.186 --> 18:26:07.196 align:start position:0% thing this is especially true in the 18:26:07.196 --> 18:26:10.246 align:start position:0% thing this is especially true in the public<18:26:07.376> network<18:26:07.744> is<18:26:08.516> the<18:26:09.000> internet 18:26:10.246 --> 18:26:10.256 align:start position:0% public network is the internet 18:26:10.256 --> 18:26:13.310 align:start position:0% public network is the internet Now<18:26:10.680> using<18:26:11.156> ipsec<18:26:12.000> the<18:26:12.420> two<18:26:12.600> lands<18:26:13.016> are<18:26:13.196> going 18:26:13.310 --> 18:26:13.320 align:start position:0% Now using ipsec the two lands are going 18:26:13.320 --> 18:26:14.926 align:start position:0% Now using ipsec the two lands are going to<18:26:13.436> create<18:26:13.564> a<18:26:14.040> tunnel<18:26:14.336> of<18:26:14.460> communication 18:26:14.926 --> 18:26:14.936 align:start position:0% to create a tunnel of communication 18:26:14.936 --> 18:26:16.670 align:start position:0% to create a tunnel of communication through<18:26:15.244> the<18:26:15.476> network<18:26:15.600> or<18:26:16.196> through<18:26:16.436> the 18:26:16.670 --> 18:26:16.680 align:start position:0% through the network or through the 18:26:16.680 --> 18:26:19.130 align:start position:0% through the network or through the internet<18:26:16.796> this<18:26:17.696> tunnel<18:26:18.064> is<18:26:18.180> secure<18:26:18.600> and<18:26:18.836> only 18:26:19.130 --> 18:26:19.140 align:start position:0% internet this tunnel is secure and only 18:26:19.140 --> 18:26:21.054 align:start position:0% internet this tunnel is secure and only accessible<18:26:19.616> by<18:26:19.920> people<18:26:20.156> inside<18:26:20.640> their 18:26:21.054 --> 18:26:21.064 align:start position:0% accessible by people inside their 18:26:21.064 --> 18:26:24.234 align:start position:0% accessible by people inside their Network<18:26:21.244> the<18:26:21.836> is<18:26:22.256> ipsec<18:26:22.860> tunnel<18:26:23.220> by<18:26:23.336> the<18:26:23.460> way 18:26:24.234 --> 18:26:24.244 align:start position:0% Network the is ipsec tunnel by the way 18:26:24.244 --> 18:26:26.210 align:start position:0% Network the is ipsec tunnel by the way is<18:26:24.720> what<18:26:24.900> we're<18:26:25.016> referring<18:26:25.436> to<18:26:25.616> when<18:26:25.920> we<18:26:26.100> talk 18:26:26.210 --> 18:26:26.220 align:start position:0% is what we're referring to when we talk 18:26:26.220 --> 18:26:29.746 align:start position:0% is what we're referring to when we talk about<18:26:26.400> VPN<18:26:27.000> or<18:26:27.180> virtual<18:26:27.476> private<18:26:27.900> Networks 18:26:29.746 --> 18:26:29.756 align:start position:0% about VPN or virtual private Networks 18:26:29.756 --> 18:26:32.390 align:start position:0% about VPN or virtual private Networks so<18:26:30.180> when<18:26:30.296> we<18:26:30.540> set<18:26:30.780> up<18:26:31.016> ipsec<18:26:31.976> the<18:26:32.220> service 18:26:32.390 --> 18:26:32.400 align:start position:0% so when we set up ipsec the service 18:26:32.400 --> 18:26:34.746 align:start position:0% so when we set up ipsec the service doesn't<18:26:32.756> just<18:26:33.064> configure<18:26:33.720> itself 18:26:34.746 --> 18:26:34.756 align:start position:0% doesn't just configure itself 18:26:34.756 --> 18:26:37.130 align:start position:0% doesn't just configure itself necessarily<18:26:35.756> there's<18:26:36.476> some<18:26:36.780> things<18:26:36.900> that 18:26:37.130 --> 18:26:37.140 align:start position:0% necessarily there's some things that 18:26:37.140 --> 18:26:38.506 align:start position:0% necessarily there's some things that have<18:26:37.256> to<18:26:37.376> be<18:26:37.500> put<18:26:37.680> into<18:26:37.796> place<18:26:38.100> for<18:26:38.400> the 18:26:38.506 --> 18:26:38.516 align:start position:0% have to be put into place for the 18:26:38.516 --> 18:26:40.426 align:start position:0% have to be put into place for the services<18:26:38.696> to<18:26:39.064> run<18:26:39.244> properly<18:26:39.600> these<18:26:40.320> are 18:26:40.426 --> 18:26:40.436 align:start position:0% services to run properly these are 18:26:40.436 --> 18:26:45.170 align:start position:0% services to run properly these are called<18:26:40.876> policies<18:26:42.080> and<18:26:43.100> policies<18:26:44.100> is<18:26:44.936> what 18:26:45.170 --> 18:26:45.180 align:start position:0% called policies and policies is what 18:26:45.180 --> 18:26:47.270 align:start position:0% called policies and policies is what configures<18:26:45.720> the<18:26:46.016> services<18:26:46.196> that<18:26:46.616> ipsec 18:26:47.270 --> 18:26:47.280 align:start position:0% configures the services that ipsec 18:26:47.280 --> 18:26:49.070 align:start position:0% configures the services that ipsec provides<18:26:47.820> they're<18:26:48.540> used<18:26:48.720> to<18:26:48.836> provide 18:26:49.070 --> 18:26:49.080 align:start position:0% provides they're used to provide 18:26:49.080 --> 18:26:51.590 align:start position:0% provides they're used to provide different<18:26:49.376> levels<18:26:49.920> of<18:26:50.100> protection<18:26:50.540> data<18:26:51.540> and 18:26:51.590 --> 18:26:51.600 align:start position:0% different levels of protection data and 18:26:51.600 --> 18:26:53.270 align:start position:0% different levels of protection data and connections<18:26:52.140> based<18:26:52.744> on<18:26:52.796> what<18:26:52.976> in<18:26:53.100> getting 18:26:53.270 --> 18:26:53.280 align:start position:0% connections based on what in getting 18:26:53.280 --> 18:26:55.606 align:start position:0% connections based on what in getting what<18:26:53.580> is<18:26:53.696> getting<18:26:53.820> passed<18:26:54.244> through<18:26:54.420> them<18:26:55.140> in 18:26:55.606 --> 18:26:55.616 align:start position:0% what is getting passed through them in 18:26:55.616 --> 18:26:58.246 align:start position:0% what is getting passed through them in other<18:26:55.796> words<18:26:55.976> just<18:26:56.580> like<18:26:56.820> with<18:26:57.116> passwords<18:26:57.720> we 18:26:58.246 --> 18:26:58.256 align:start position:0% other words just like with passwords we 18:26:58.256 --> 18:26:59.570 align:start position:0% other words just like with passwords we have<18:26:58.376> the<18:26:58.616> passwords<18:26:58.976> and<18:26:59.100> we<18:26:59.280> know<18:26:59.400> they're 18:26:59.570 --> 18:26:59.580 align:start position:0% have the passwords and we know they're 18:26:59.580 --> 18:27:02.146 align:start position:0% have the passwords and we know they're built<18:26:59.876> into<18:26:59.936> windows<18:27:00.476> but<18:27:01.140> unless<18:27:01.744> we<18:27:01.976> set 18:27:02.146 --> 18:27:02.156 align:start position:0% built into windows but unless we set 18:27:02.156 --> 18:27:05.390 align:start position:0% built into windows but unless we set some<18:27:02.516> sort<18:27:02.756> of<18:27:02.936> policy<18:27:03.720> that<18:27:04.080> tells<18:27:04.564> the<18:27:05.040> users 18:27:05.390 --> 18:27:05.400 align:start position:0% some sort of policy that tells the users 18:27:05.400 --> 18:27:07.070 align:start position:0% some sort of policy that tells the users how<18:27:05.876> their<18:27:06.000> passwords<18:27:06.476> have<18:27:06.656> to<18:27:06.836> function 18:27:07.070 --> 18:27:07.080 align:start position:0% how their passwords have to function 18:27:07.080 --> 18:27:09.466 align:start position:0% how their passwords have to function they<18:27:08.040> may<18:27:08.220> not<18:27:08.400> be<18:27:08.516> used<18:27:08.696> very<18:27:09.064> well<18:27:09.180> someone 18:27:09.466 --> 18:27:09.476 align:start position:0% they may not be used very well someone 18:27:09.476 --> 18:27:11.210 align:start position:0% they may not be used very well someone might<18:27:09.720> just<18:27:09.836> use<18:27:10.016> the<18:27:10.376> password<18:27:10.680> password 18:27:11.210 --> 18:27:11.220 align:start position:0% might just use the password password 18:27:11.220 --> 18:27:13.910 align:start position:0% might just use the password password which<18:27:11.820> isn't<18:27:12.116> even<18:27:12.180> a<18:27:12.420> safe<18:27:12.540> password<18:27:12.836> so<18:27:13.680> we 18:27:13.910 --> 18:27:13.920 align:start position:0% which isn't even a safe password so we 18:27:13.920 --> 18:27:16.490 align:start position:0% which isn't even a safe password so we have<18:27:14.040> a<18:27:14.280> password<18:27:14.516> policy<18:27:15.420> that<18:27:15.900> ensures<18:27:16.196> that 18:27:16.490 --> 18:27:16.500 align:start position:0% have a password policy that ensures that 18:27:16.500 --> 18:27:19.310 align:start position:0% have a password policy that ensures that people<18:27:16.680> have<18:27:17.040> a<18:27:17.280> certain<18:27:17.400> length<18:27:17.936> uh<18:27:18.900> history 18:27:19.310 --> 18:27:19.320 align:start position:0% people have a certain length uh history 18:27:19.320 --> 18:27:21.646 align:start position:0% people have a certain length uh history and<18:27:20.156> certain<18:27:20.400> characters<18:27:20.696> included<18:27:21.420> in<18:27:21.540> their 18:27:21.646 --> 18:27:21.656 align:start position:0% and certain characters included in their 18:27:21.656 --> 18:27:23.450 align:start position:0% and certain characters included in their passwords<18:27:22.080> the<18:27:22.564> same<18:27:22.680> thing<18:27:22.860> sort<18:27:23.100> of<18:27:23.220> goes 18:27:23.450 --> 18:27:23.460 align:start position:0% passwords the same thing sort of goes 18:27:23.460 --> 18:27:24.890 align:start position:0% passwords the same thing sort of goes with<18:27:23.580> ipsec 18:27:24.890 --> 18:27:24.900 align:start position:0% with ipsec 18:27:24.900 --> 18:27:27.170 align:start position:0% with ipsec now<18:27:25.376> there<18:27:25.500> are<18:27:25.616> some<18:27:25.920> important<18:27:26.460> elements 18:27:27.170 --> 18:27:27.180 align:start position:0% now there are some important elements 18:27:27.180 --> 18:27:29.866 align:start position:0% now there are some important elements that<18:27:27.960> we<18:27:28.256> have<18:27:28.500> to<18:27:28.796> address<18:27:28.976> when<18:27:29.516> setting<18:27:29.820> up 18:27:29.866 --> 18:27:29.876 align:start position:0% that we have to address when setting up 18:27:29.876 --> 18:27:33.170 align:start position:0% that we have to address when setting up ipsec<18:27:30.540> policies<18:27:31.080> first<18:27:31.976> we<18:27:32.336> have<18:27:32.516> filters 18:27:33.170 --> 18:27:33.180 align:start position:0% ipsec policies first we have filters 18:27:33.180 --> 18:27:35.210 align:start position:0% ipsec policies first we have filters that<18:27:33.420> are<18:27:33.540> put<18:27:33.720> into<18:27:33.836> place<18:27:34.140> the<18:27:34.920> filters 18:27:35.210 --> 18:27:35.220 align:start position:0% that are put into place the filters 18:27:35.220 --> 18:27:38.746 align:start position:0% that are put into place the filters determine<18:27:35.820> which<18:27:36.296> packets<18:27:36.780> should<18:27:37.376> be<18:27:37.616> secure 18:27:38.746 --> 18:27:38.756 align:start position:0% determine which packets should be secure 18:27:38.756 --> 18:27:41.990 align:start position:0% determine which packets should be secure and<18:27:39.656> which<18:27:40.016> can<18:27:40.436> be<18:27:40.616> left<18:27:40.796> alone 18:27:41.990 --> 18:27:42.000 align:start position:0% and which can be left alone 18:27:42.000 --> 18:27:43.966 align:start position:0% and which can be left alone now<18:27:42.540> every<18:27:42.836> filter<18:27:43.080> addresses<18:27:43.616> a<18:27:43.796> different 18:27:43.966 --> 18:27:43.976 align:start position:0% now every filter addresses a different 18:27:43.976 --> 18:27:46.310 align:start position:0% now every filter addresses a different type<18:27:44.280> of<18:27:44.460> packet<18:27:44.820> so<18:27:45.000> there's<18:27:45.296> generally<18:27:46.080> a 18:27:46.310 --> 18:27:46.320 align:start position:0% type of packet so there's generally a 18:27:46.320 --> 18:27:47.630 align:start position:0% type of packet so there's generally a good<18:27:46.500> amount<18:27:46.796> of<18:27:46.920> different<18:27:47.100> types<18:27:47.516> of 18:27:47.630 --> 18:27:47.640 align:start position:0% good amount of different types of 18:27:47.640 --> 18:27:50.746 align:start position:0% good amount of different types of filters<18:27:48.080> all<18:27:49.080> of<18:27:49.256> these<18:27:49.616> filters<18:27:50.460> get 18:27:50.746 --> 18:27:50.756 align:start position:0% filters all of these filters get 18:27:50.756 --> 18:27:52.966 align:start position:0% filters all of these filters get compiled<18:27:51.244> into<18:27:51.360> a<18:27:51.656> filter<18:27:51.780> list<18:27:52.196> where<18:27:52.796> the 18:27:52.966 --> 18:27:52.976 align:start position:0% compiled into a filter list where the 18:27:52.976 --> 18:27:54.710 align:start position:0% compiled into a filter list where the administrator<18:27:53.400> can<18:27:53.696> easily<18:27:54.000> change<18:27:54.360> and 18:27:54.710 --> 18:27:54.720 align:start position:0% administrator can easily change and 18:27:54.720 --> 18:27:56.630 align:start position:0% administrator can easily change and reconfigure<18:27:55.256> the<18:27:55.436> filters<18:27:55.744> to<18:27:56.100> address<18:27:56.220> the 18:27:56.630 --> 18:27:56.640 align:start position:0% reconfigure the filters to address the 18:27:56.640 --> 18:27:58.734 align:start position:0% reconfigure the filters to address the needs<18:27:56.820> of<18:27:56.936> their<18:27:57.064> Network<18:27:57.256> now<18:27:58.256> again<18:27:58.436> the 18:27:58.734 --> 18:27:58.744 align:start position:0% needs of their Network now again the 18:27:58.744 --> 18:27:59.746 align:start position:0% needs of their Network now again the reason<18:27:58.920> we're<18:27:59.156> going<18:27:59.336> to<18:27:59.460> want<18:27:59.516> to<18:27:59.640> have 18:27:59.746 --> 18:27:59.756 align:start position:0% reason we're going to want to have 18:27:59.756 --> 18:28:05.686 align:start position:0% reason we're going to want to have filters<18:28:00.180> is<18:28:00.836> because<18:28:01.080> the<18:28:01.920> more<18:28:02.040> security 18:28:05.686 --> 18:28:05.696 align:start position:0% 18:28:05.696 --> 18:28:08.630 align:start position:0% just<18:28:06.244> like<18:28:06.476> the<18:28:06.900> more<18:28:07.140> layers<18:28:07.616> you<18:28:07.860> have<18:28:08.100> on<18:28:08.460> if 18:28:08.630 --> 18:28:08.640 align:start position:0% just like the more layers you have on if 18:28:08.640 --> 18:28:11.810 align:start position:0% just like the more layers you have on if it's<18:28:08.820> cold<18:28:09.064> outside 18:28:11.810 --> 18:28:11.820 align:start position:0% 18:28:11.820 --> 18:28:14.210 align:start position:0% the<18:28:12.360> more<18:28:12.476> data<18:28:12.836> it<18:28:12.960> takes<18:28:13.196> up 18:28:14.210 --> 18:28:14.220 align:start position:0% the more data it takes up 18:28:14.220 --> 18:28:17.630 align:start position:0% the more data it takes up and<18:28:14.820> the<18:28:14.936> longer<18:28:15.244> it<18:28:15.420> takes<18:28:15.600> to<18:28:15.836> decode<18:28:16.280> so<18:28:17.280> the 18:28:17.630 --> 18:28:17.640 align:start position:0% and the longer it takes to decode so the 18:28:17.640 --> 18:28:19.910 align:start position:0% and the longer it takes to decode so the less<18:28:17.756> security<18:28:18.000> we<18:28:18.540> have<18:28:18.780> the<18:28:19.436> faster<18:28:19.616> the 18:28:19.910 --> 18:28:19.920 align:start position:0% less security we have the faster the 18:28:19.920 --> 18:28:22.366 align:start position:0% less security we have the faster the data<18:28:20.156> is<18:28:20.220> going<18:28:20.400> to<18:28:20.516> travel<18:28:20.656> but<18:28:21.656> the<18:28:22.256> more 18:28:22.366 --> 18:28:22.376 align:start position:0% data is going to travel but the more 18:28:22.376 --> 18:28:25.490 align:start position:0% data is going to travel but the more security<18:28:22.820> uh<18:28:23.820> the<18:28:24.600> less<18:28:24.720> easy<18:28:24.960> it<18:28:25.140> is<18:28:25.320> to 18:28:25.490 --> 18:28:25.500 align:start position:0% security uh the less easy it is to 18:28:25.500 --> 18:28:27.106 align:start position:0% security uh the less easy it is to tamper<18:28:25.796> with<18:28:25.976> so<18:28:26.400> we<18:28:26.516> need<18:28:26.640> to<18:28:26.696> weigh<18:28:26.936> this 18:28:27.106 --> 18:28:27.116 align:start position:0% tamper with so we need to weigh this 18:28:27.116 --> 18:28:28.734 align:start position:0% tamper with so we need to weigh this stuff<18:28:27.656> like<18:28:27.836> browsing<18:28:28.376> on<18:28:28.500> the<18:28:28.680> internet 18:28:28.734 --> 18:28:28.744 align:start position:0% stuff like browsing on the internet 18:28:28.744 --> 18:28:30.410 align:start position:0% stuff like browsing on the internet might<18:28:29.100> not<18:28:29.280> be<18:28:29.400> something<18:28:29.580> we<18:28:29.820> need<18:28:30.000> to<18:28:30.116> secure 18:28:30.410 --> 18:28:30.420 align:start position:0% might not be something we need to secure 18:28:30.420 --> 18:28:33.246 align:start position:0% might not be something we need to secure a<18:28:30.656> lot<18:28:30.796> whereas<18:28:31.796> we<18:28:32.220> probably<18:28:32.400> want<18:28:32.696> to<18:28:32.820> secure 18:28:33.246 --> 18:28:33.256 align:start position:0% a lot whereas we probably want to secure 18:28:33.256 --> 18:28:36.590 align:start position:0% a lot whereas we probably want to secure uh<18:28:34.256> for<18:28:34.500> instance<18:28:34.744> email<18:28:35.100> a<18:28:35.580> lot<18:28:35.696> more<18:28:35.876> or<18:28:36.420> even 18:28:36.590 --> 18:28:36.600 align:start position:0% uh for instance email a lot more or even 18:28:36.600 --> 18:28:38.810 align:start position:0% uh for instance email a lot more or even Bank<18:28:36.960> Social<18:28:37.376> Security<18:28:37.564> numbers 18:28:38.810 --> 18:28:38.820 align:start position:0% Bank Social Security numbers 18:28:38.820 --> 18:28:40.366 align:start position:0% Bank Social Security numbers etc<18:28:39.244> etc 18:28:40.366 --> 18:28:40.376 align:start position:0% etc etc 18:28:40.376 --> 18:28:43.366 align:start position:0% etc etc next<18:28:41.156> policies<18:28:41.936> have<18:28:42.116> to<18:28:42.244> be<18:28:42.360> provided<18:28:42.836> the 18:28:43.366 --> 18:28:43.376 align:start position:0% next policies have to be provided the 18:28:43.376 --> 18:28:46.186 align:start position:0% next policies have to be provided the proper<18:28:43.796> Network<18:28:44.040> information<18:28:44.836> this<18:28:45.836> involves 18:28:46.186 --> 18:28:46.196 align:start position:0% proper Network information this involves 18:28:46.196 --> 18:28:48.054 align:start position:0% proper Network information this involves what<18:28:46.564> security<18:28:46.796> map<18:28:47.220> methods<18:28:47.756> connection 18:28:48.054 --> 18:28:48.064 align:start position:0% what security map methods connection 18:28:48.064 --> 18:28:50.630 align:start position:0% what security map methods connection types<18:28:48.720> and<18:28:49.320> tunnel<18:28:49.680> settings<18:28:49.860> are<18:28:50.156> being<18:28:50.336> used 18:28:50.630 --> 18:28:50.640 align:start position:0% types and tunnel settings are being used 18:28:50.640 --> 18:28:53.286 align:start position:0% types and tunnel settings are being used the<18:28:51.540> security<18:28:51.720> methods<18:28:52.320> are<18:28:52.500> basically 18:28:53.286 --> 18:28:53.296 align:start position:0% the security methods are basically 18:28:53.296 --> 18:28:58.606 align:start position:0% the security methods are basically algorithms<18:28:54.296> that<18:28:54.960> are<18:28:55.256> used<18:28:55.680> in<18:28:56.460> encrypting 18:28:58.606 --> 18:28:58.616 align:start position:0% algorithms that are used in encrypting 18:28:58.616 --> 18:29:01.426 align:start position:0% algorithms that are used in encrypting and<18:28:59.280> authenticating<18:28:59.936> the<18:29:00.180> data<18:29:00.900> connection 18:29:01.426 --> 18:29:01.436 align:start position:0% and authenticating the data connection 18:29:01.436 --> 18:29:04.310 align:start position:0% and authenticating the data connection types<18:29:02.220> determine<18:29:03.180> whether<18:29:03.476> the<18:29:03.656> policies<18:29:04.080> are 18:29:04.310 --> 18:29:04.320 align:start position:0% types determine whether the policies are 18:29:04.320 --> 18:29:05.926 align:start position:0% types determine whether the policies are going<18:29:04.500> to<18:29:04.680> handle 18:29:05.926 --> 18:29:05.936 align:start position:0% going to handle 18:29:05.936 --> 18:29:08.270 align:start position:0% going to handle a<18:29:06.476> local<18:29:06.600> area<18:29:06.960> network 18:29:08.270 --> 18:29:08.280 align:start position:0% a local area network 18:29:08.280 --> 18:29:11.210 align:start position:0% a local area network a<18:29:08.876> Wan<18:29:09.244> or<18:29:10.080> a<18:29:10.196> VPN 18:29:11.210 --> 18:29:11.220 align:start position:0% a Wan or a VPN 18:29:11.220 --> 18:29:14.326 align:start position:0% a Wan or a VPN in<18:29:11.640> other<18:29:11.696> words<18:29:11.876> ipsec<18:29:12.600> needs<18:29:12.900> to<18:29:13.016> know<18:29:13.336> what 18:29:14.326 --> 18:29:14.336 align:start position:0% in other words ipsec needs to know what 18:29:14.336 --> 18:29:17.506 align:start position:0% in other words ipsec needs to know what type<18:29:14.756> of<18:29:15.476> connection<18:29:15.720> I<18:29:16.256> have<18:29:16.436> here<18:29:16.744> so<18:29:17.280> it 18:29:17.506 --> 18:29:17.516 align:start position:0% type of connection I have here so it 18:29:17.516 --> 18:29:19.606 align:start position:0% type of connection I have here so it knows<18:29:17.820> what<18:29:18.116> level<18:29:18.360> of<18:29:18.656> security<18:29:18.900> to<18:29:19.320> put<18:29:19.436> into 18:29:19.606 --> 18:29:19.616 align:start position:0% knows what level of security to put into 18:29:19.616 --> 18:29:22.366 align:start position:0% knows what level of security to put into place<18:29:19.976> you<18:29:20.756> can<18:29:20.876> imagine<18:29:21.064> that<18:29:21.836> with<18:29:22.080> a<18:29:22.256> wide 18:29:22.366 --> 18:29:22.376 align:start position:0% place you can imagine that with a wide 18:29:22.376 --> 18:29:24.770 align:start position:0% place you can imagine that with a wide area<18:29:22.564> network<18:29:22.860> or<18:29:23.100> VPN<18:29:23.640> we<18:29:24.360> need<18:29:24.476> more 18:29:24.770 --> 18:29:24.780 align:start position:0% area network or VPN we need more 18:29:24.780 --> 18:29:28.130 align:start position:0% area network or VPN we need more security<18:29:25.080> than<18:29:25.744> with<18:29:25.976> a<18:29:26.156> lan 18:29:28.130 --> 18:29:28.140 align:start position:0% security than with a lan 18:29:28.140 --> 18:29:30.234 align:start position:0% security than with a lan all<18:29:28.616> right<18:29:28.744> so<18:29:29.040> although<18:29:29.460> this<18:29:29.820> might<18:29:30.000> have 18:29:30.234 --> 18:29:30.244 align:start position:0% all right so although this might have 18:29:30.244 --> 18:29:32.326 align:start position:0% all right so although this might have been<18:29:30.540> short<18:29:30.836> duration<18:29:31.376> we<18:29:31.616> covered<18:29:31.976> a<18:29:32.156> lot<18:29:32.220> of 18:29:32.326 --> 18:29:32.336 align:start position:0% been short duration we covered a lot of 18:29:32.336 --> 18:29:34.850 align:start position:0% been short duration we covered a lot of important<18:29:32.756> things<18:29:33.000> first<18:29:33.836> we<18:29:34.436> talked<18:29:34.744> about 18:29:34.850 --> 18:29:34.860 align:start position:0% important things first we talked about 18:29:34.860 --> 18:29:37.686 align:start position:0% important things first we talked about the<18:29:35.220> fact<18:29:35.336> that<18:29:35.580> ipsec<18:29:36.420> exists<18:29:36.900> remember 18:29:37.686 --> 18:29:37.696 align:start position:0% the fact that ipsec exists remember 18:29:37.696 --> 18:29:42.170 align:start position:0% the fact that ipsec exists remember ipsec<18:29:38.696> stands<18:29:39.064> for<18:29:39.180> IP<18:29:39.656> security<18:29:40.756> and<18:29:41.756> it's 18:29:42.170 --> 18:29:42.180 align:start position:0% ipsec stands for IP security and it's 18:29:42.180 --> 18:29:45.826 align:start position:0% ipsec stands for IP security and it's really<18:29:42.360> not<18:29:42.656> its<18:29:43.140> own<18:29:43.500> protocol<18:29:44.100> what<18:29:44.640> it<18:29:44.756> is 18:29:45.826 --> 18:29:45.836 align:start position:0% really not its own protocol what it is 18:29:45.836 --> 18:29:49.426 align:start position:0% really not its own protocol what it is is<18:29:46.500> a<18:29:46.680> series<18:29:46.920> or<18:29:47.580> a<18:29:47.876> group<18:29:48.116> of<18:29:48.720> protocols 18:29:49.426 --> 18:29:49.436 align:start position:0% is a series or a group of protocols 18:29:49.436 --> 18:29:51.530 align:start position:0% is a series or a group of protocols Services 18:29:51.530 --> 18:29:51.540 align:start position:0% Services 18:29:51.540 --> 18:29:56.270 align:start position:0% Services Etc<18:29:51.860> that<18:29:52.860> ensure<18:29:53.280> security<18:29:54.080> over<18:29:55.080> the<18:29:55.796> IP 18:29:56.270 --> 18:29:56.280 align:start position:0% Etc that ensure security over the IP 18:29:56.280 --> 18:29:59.990 align:start position:0% Etc that ensure security over the IP protocol<18:29:57.064> or<18:29:57.360> the<18:29:57.476> Internet<18:29:57.656> Protocol 18:29:59.990 --> 18:30:00.000 align:start position:0% protocol or the Internet Protocol 18:30:00.000 --> 18:30:02.450 align:start position:0% protocol or the Internet Protocol we<18:30:00.476> also<18:30:00.720> talked<18:30:01.016> about<18:30:01.140> two<18:30:01.564> of<18:30:01.796> the<18:30:01.976> ways<18:30:02.280> we 18:30:02.450 --> 18:30:02.460 align:start position:0% we also talked about two of the ways we 18:30:02.460 --> 18:30:05.090 align:start position:0% we also talked about two of the ways we do<18:30:02.580> this<18:30:02.820> one<18:30:03.600> is<18:30:03.780> the<18:30:03.960> ah<18:30:04.256> protocol<18:30:04.680> and<18:30:04.920> one 18:30:05.090 --> 18:30:05.100 align:start position:0% do this one is the ah protocol and one 18:30:05.100 --> 18:30:09.410 align:start position:0% do this one is the ah protocol and one is<18:30:05.220> the<18:30:05.400> ESP<18:30:05.580> protocol<18:30:06.360> remember<18:30:07.460> ah<18:30:08.460> stands 18:30:09.410 --> 18:30:09.420 align:start position:0% is the ESP protocol remember ah stands 18:30:09.420 --> 18:30:12.170 align:start position:0% is the ESP protocol remember ah stands for<18:30:09.796> authentication<18:30:10.796> header 18:30:12.170 --> 18:30:12.180 align:start position:0% for authentication header 18:30:12.180 --> 18:30:15.170 align:start position:0% for authentication header as<18:30:12.656> the<18:30:12.836> name<18:30:12.960> implies<18:30:13.436> it's<18:30:13.796> a<18:30:13.976> header<18:30:14.336> in<18:30:14.936> the 18:30:15.170 --> 18:30:15.180 align:start position:0% as the name implies it's a header in the 18:30:15.180 --> 18:30:19.490 align:start position:0% as the name implies it's a header in the IP<18:30:15.780> packet<18:30:16.516> that<18:30:17.516> authenticates 18:30:19.490 --> 18:30:19.500 align:start position:0% IP packet that authenticates 18:30:19.500 --> 18:30:22.006 align:start position:0% IP packet that authenticates to<18:30:20.100> make<18:30:20.280> sure<18:30:20.460> the<18:30:20.756> users<18:30:21.116> who<18:30:21.540> are<18:30:21.656> about<18:30:21.780> to 18:30:22.006 --> 18:30:22.016 align:start position:0% to make sure the users who are about to 18:30:22.016 --> 18:30:23.746 align:start position:0% to make sure the users who are about to communicate<18:30:22.500> are<18:30:22.796> the<18:30:22.976> ones<18:30:23.220> for<18:30:23.400> whom<18:30:23.580> it's 18:30:23.746 --> 18:30:23.756 align:start position:0% communicate are the ones for whom it's 18:30:23.756 --> 18:30:25.670 align:start position:0% communicate are the ones for whom it's intended<18:30:24.244> and<18:30:24.360> who<18:30:24.540> are<18:30:24.720> sending 18:30:25.670 --> 18:30:25.680 align:start position:0% intended and who are sending 18:30:25.680 --> 18:30:28.670 align:start position:0% intended and who are sending ESP<18:30:26.220> on<18:30:26.820> the<18:30:26.936> other<18:30:27.064> hand<18:30:27.296> which<18:30:28.080> stands<18:30:28.436> for 18:30:28.670 --> 18:30:28.680 align:start position:0% ESP on the other hand which stands for 18:30:28.680 --> 18:30:34.246 align:start position:0% ESP on the other hand which stands for encapsulating 18:30:34.246 --> 18:30:34.256 align:start position:0% 18:30:34.256 --> 18:30:39.466 align:start position:0% security<18:30:34.796> payload 18:30:39.466 --> 18:30:39.476 align:start position:0% 18:30:39.476 --> 18:30:42.234 align:start position:0% is<18:30:39.900> literally<18:30:40.196> going<18:30:40.564> to<18:30:40.796> encapsulate<18:30:41.640> the 18:30:42.234 --> 18:30:42.244 align:start position:0% is literally going to encapsulate the 18:30:42.244 --> 18:30:45.410 align:start position:0% is literally going to encapsulate the data<18:30:43.016> in<18:30:43.500> an<18:30:43.616> encrypted<18:30:44.100> form 18:30:45.410 --> 18:30:45.420 align:start position:0% data in an encrypted form 18:30:45.420 --> 18:30:47.450 align:start position:0% data in an encrypted form and<18:30:45.720> it'll<18:30:45.960> only<18:30:46.140> release<18:30:46.500> this<18:30:46.920> encrypted 18:30:47.450 --> 18:30:47.460 align:start position:0% and it'll only release this encrypted 18:30:47.460 --> 18:30:49.966 align:start position:0% and it'll only release this encrypted information<18:30:47.960> to<18:30:48.960> someone<18:30:49.256> who<18:30:49.616> has<18:30:49.796> been 18:30:49.966 --> 18:30:49.976 align:start position:0% information to someone who has been 18:30:49.976 --> 18:30:52.426 align:start position:0% information to someone who has been authenticated<18:30:50.820> to<18:30:51.180> receive<18:30:51.476> it<18:30:51.600> and<18:30:52.256> remember 18:30:52.426 --> 18:30:52.436 align:start position:0% authenticated to receive it and remember 18:30:52.436 --> 18:30:56.390 align:start position:0% authenticated to receive it and remember to<18:30:52.796> do<18:30:52.920> this<18:30:53.100> we<18:30:53.460> use<18:30:53.720> Keys<18:30:54.720> both<18:30:55.196> public<18:30:55.564> and 18:30:56.390 --> 18:30:56.400 align:start position:0% to do this we use Keys both public and 18:30:56.400 --> 18:31:01.186 align:start position:0% to do this we use Keys both public and private 18:31:01.186 --> 18:31:01.196 align:start position:0% 18:31:01.196 --> 18:31:03.286 align:start position:0% we<18:31:01.920> also<18:31:02.156> discussed<18:31:02.640> the<18:31:02.876> three<18:31:03.116> different 18:31:03.286 --> 18:31:03.296 align:start position:0% we also discussed the three different 18:31:03.296 --> 18:31:05.646 align:start position:0% we also discussed the three different ipsec<18:31:04.140> services<18:31:04.436> that<18:31:04.976> are<18:31:05.100> provided 18:31:05.646 --> 18:31:05.656 align:start position:0% ipsec services that are provided 18:31:05.656 --> 18:31:08.686 align:start position:0% ipsec services that are provided including<18:31:06.656> data<18:31:07.140> verification<18:31:07.696> which 18:31:08.686 --> 18:31:08.696 align:start position:0% including data verification which 18:31:08.696 --> 18:31:12.170 align:start position:0% including data verification which ensures<18:31:09.296> that<18:31:10.256> the<18:31:10.744> data<18:31:11.040> packets<18:31:11.516> being<18:31:11.876> sent 18:31:12.170 --> 18:31:12.180 align:start position:0% ensures that the data packets being sent 18:31:12.180 --> 18:31:17.270 align:start position:0% ensures that the data packets being sent are<18:31:13.016> coming<18:31:13.196> from<18:31:13.616> legitimate<18:31:14.580> places 18:31:17.270 --> 18:31:17.280 align:start position:0% 18:31:17.280 --> 18:31:19.910 align:start position:0% protection<18:31:17.936> from<18:31:18.296> tampering<18:31:18.960> which<18:31:19.500> ensures 18:31:19.910 --> 18:31:19.920 align:start position:0% protection from tampering which ensures 18:31:19.920 --> 18:31:21.890 align:start position:0% protection from tampering which ensures the<18:31:20.460> integrity 18:31:21.890 --> 18:31:21.900 align:start position:0% the integrity 18:31:21.900 --> 18:31:23.686 align:start position:0% the integrity of<18:31:22.376> our<18:31:22.436> data<18:31:22.796> that<18:31:22.976> it<18:31:23.156> has<18:31:23.336> not<18:31:23.460> been 18:31:23.686 --> 18:31:23.696 align:start position:0% of our data that it has not been 18:31:23.696 --> 18:31:26.746 align:start position:0% of our data that it has not been tampered<18:31:24.180> with<18:31:24.720> either 18:31:26.746 --> 18:31:26.756 align:start position:0% tampered with either 18:31:26.756 --> 18:31:30.710 align:start position:0% tampered with either tampered<18:31:27.420> with<18:31:27.600> from<18:31:28.196> say<18:31:29.100> an<18:31:29.696> attacker 18:31:30.710 --> 18:31:30.720 align:start position:0% tampered with from say an attacker 18:31:30.720 --> 18:31:32.990 align:start position:0% tampered with from say an attacker or<18:31:31.256> the<18:31:31.436> data<18:31:31.796> might<18:31:32.336> have<18:31:32.460> just<18:31:32.640> become 18:31:32.990 --> 18:31:33.000 align:start position:0% or the data might have just become 18:31:33.000 --> 18:31:35.090 align:start position:0% or the data might have just become corrupted 18:31:35.090 --> 18:31:35.100 align:start position:0% corrupted 18:31:35.100 --> 18:31:37.130 align:start position:0% corrupted finally<18:31:35.820> we<18:31:36.244> ensure<18:31:36.476> that<18:31:36.720> we're<18:31:36.900> having 18:31:37.130 --> 18:31:37.140 align:start position:0% finally we ensure that we're having 18:31:37.140 --> 18:31:40.554 align:start position:0% finally we ensure that we're having private<18:31:38.000> transactions<18:31:39.000> meaning<18:31:39.900> that<18:31:40.376> the 18:31:40.554 --> 18:31:40.564 align:start position:0% private transactions meaning that the 18:31:40.564 --> 18:31:43.310 align:start position:0% private transactions meaning that the data<18:31:40.860> is<18:31:41.100> confidential<18:31:42.000> between<18:31:42.720> only<18:31:43.080> the 18:31:43.310 --> 18:31:43.320 align:start position:0% data is confidential between only the 18:31:43.320 --> 18:31:45.286 align:start position:0% data is confidential between only the people<18:31:43.500> who<18:31:43.860> need<18:31:43.976> to<18:31:44.100> be<18:31:44.220> having<18:31:44.400> it<18:31:44.696> and 18:31:45.286 --> 18:31:45.296 align:start position:0% people who need to be having it and 18:31:45.296 --> 18:31:48.170 align:start position:0% people who need to be having it and lastly<18:31:45.656> we<18:31:46.140> discussed<18:31:46.564> ipsec<18:31:47.336> policies<18:31:47.876> some 18:31:48.170 --> 18:31:48.180 align:start position:0% lastly we discussed ipsec policies some 18:31:48.180 --> 18:31:50.866 align:start position:0% lastly we discussed ipsec policies some of<18:31:48.296> the<18:31:48.420> things<18:31:48.656> that<18:31:49.436> we<18:31:49.744> need<18:31:49.976> to<18:31:50.280> have<18:31:50.460> when 18:31:50.866 --> 18:31:50.876 align:start position:0% of the things that we need to have when 18:31:50.876 --> 18:31:53.326 align:start position:0% of the things that we need to have when we're<18:31:51.180> creating<18:31:52.080> our<18:31:52.376> policies<18:31:52.744> for<18:31:52.976> IP 18:31:53.326 --> 18:31:53.336 align:start position:0% we're creating our policies for IP 18:31:53.336 --> 18:31:55.670 align:start position:0% we're creating our policies for IP security<18:31:53.720> for<18:31:54.720> instance<18:31:54.900> we<18:31:55.256> need<18:31:55.376> to<18:31:55.500> know 18:31:55.670 --> 18:31:55.680 align:start position:0% security for instance we need to know 18:31:55.680 --> 18:32:00.410 align:start position:0% security for instance we need to know the<18:31:56.220> type<18:31:56.460> of<18:31:56.580> network<18:31:56.876> we're<18:31:57.656> on 18:32:00.410 --> 18:32:00.420 align:start position:0% 18:32:00.420 --> 18:32:02.270 align:start position:0% and<18:32:00.960> also<18:32:01.256> filters 18:32:02.270 --> 18:32:02.280 align:start position:0% and also filters 18:32:02.280 --> 18:32:04.786 align:start position:0% and also filters so<18:32:02.820> that<18:32:03.000> the<18:32:03.244> appropriate<18:32:03.836> level<18:32:04.196> of 18:32:04.786 --> 18:32:04.796 align:start position:0% so that the appropriate level of 18:32:04.796 --> 18:32:06.170 align:start position:0% so that the appropriate level of security<18:32:04.976> can<18:32:05.400> be<18:32:05.580> applied<18:32:05.820> to<18:32:06.064> the 18:32:06.170 --> 18:32:06.180 align:start position:0% security can be applied to the 18:32:06.180 --> 18:32:11.350 align:start position:0% security can be applied to the appropriate<18:32:06.600> type<18:32:06.960> of<18:32:07.376> data 18:32:11.350 --> 18:32:11.360 align:start position:0% 18:32:11.360 --> 18:32:27.646 align:start position:0% [Music] 18:32:27.646 --> 18:32:27.656 align:start position:0% 18:32:27.656 --> 18:32:30.890 align:start position:0% welcome<18:32:28.080> to<18:32:28.376> module<18:32:28.920> 14<18:32:29.156> lesson<18:32:30.000> 1<18:32:30.180> denial<18:32:30.720> of 18:32:30.890 --> 18:32:30.900 align:start position:0% welcome to module 14 lesson 1 denial of 18:32:30.900 --> 18:32:34.130 align:start position:0% welcome to module 14 lesson 1 denial of service 18:32:34.130 --> 18:32:34.140 align:start position:0% 18:32:34.140 --> 18:32:35.990 align:start position:0% so<18:32:34.616> we're<18:32:34.744> going<18:32:34.860> to<18:32:34.920> look<18:32:35.100> at<18:32:35.220> what<18:32:35.516> is<18:32:35.640> denial 18:32:35.990 --> 18:32:36.000 align:start position:0% so we're going to look at what is denial 18:32:36.000 --> 18:32:38.810 align:start position:0% so we're going to look at what is denial of<18:32:36.180> service<18:32:36.360> by<18:32:36.836> the<18:32:36.960> way<18:32:37.016> this<18:32:37.320> is<18:32:37.500> a<18:32:37.796> small<18:32:38.156> uh 18:32:38.810 --> 18:32:38.820 align:start position:0% of service by the way this is a small uh 18:32:38.820 --> 18:32:40.554 align:start position:0% of service by the way this is a small uh subset<18:32:39.244> of<18:32:39.420> what<18:32:39.600> you<18:32:39.720> would<18:32:39.836> get<18:32:40.016> in<18:32:40.376> the 18:32:40.554 --> 18:32:40.564 align:start position:0% subset of what you would get in the 18:32:40.564 --> 18:32:44.506 align:start position:0% subset of what you would get in the competitive<18:32:41.220> Security<18:32:41.460> Plus<18:32:42.296> exam<18:32:43.100> and<18:32:44.100> and 18:32:44.506 --> 18:32:44.516 align:start position:0% competitive Security Plus exam and and 18:32:44.516 --> 18:32:46.006 align:start position:0% competitive Security Plus exam and and the<18:32:44.820> network<18:32:44.936> plus 18:32:46.006 --> 18:32:46.016 align:start position:0% the network plus 18:32:46.016 --> 18:32:48.826 align:start position:0% the network plus um<18:32:46.080> sorry<18:32:46.376> the<18:32:46.680> CCNA<18:32:47.280> security<18:32:47.460> exam<18:32:48.116> those 18:32:48.826 --> 18:32:48.836 align:start position:0% um sorry the CCNA security exam those 18:32:48.836 --> 18:32:50.450 align:start position:0% um sorry the CCNA security exam those are<18:32:49.016> the<18:32:49.196> vendors<18:32:49.436> do<18:32:49.680> security<18:32:49.920> as<18:32:50.280> well 18:32:50.450 --> 18:32:50.460 align:start position:0% are the vendors do security as well 18:32:50.460 --> 18:32:53.390 align:start position:0% are the vendors do security as well obviously<18:32:50.876> like<18:32:51.116> a<18:32:51.360> juniper<18:32:51.836> but<18:32:53.100> um<18:32:53.100> company 18:32:53.390 --> 18:32:53.400 align:start position:0% obviously like a juniper but um company 18:32:53.400 --> 18:32:55.966 align:start position:0% obviously like a juniper but um company is<18:32:53.696> a<18:32:53.876> good<18:32:53.936> foundation<18:32:54.360> and<18:32:54.720> then<18:32:54.900> in<18:32:55.376> Vendor 18:32:55.966 --> 18:32:55.976 align:start position:0% is a good foundation and then in Vendor 18:32:55.976 --> 18:32:58.850 align:start position:0% is a good foundation and then in Vendor specific<18:32:56.420> Cisco<18:32:57.420> CCNA<18:32:58.140> security<18:32:58.320> is 18:32:58.850 --> 18:32:58.860 align:start position:0% specific Cisco CCNA security is 18:32:58.860 --> 18:33:01.246 align:start position:0% specific Cisco CCNA security is excellent<18:32:59.400> you<18:33:00.296> probably<18:33:00.476> I<18:33:00.720> think<18:33:00.900> you<18:33:01.080> need 18:33:01.246 --> 18:33:01.256 align:start position:0% excellent you probably I think you need 18:33:01.256 --> 18:33:03.590 align:start position:0% excellent you probably I think you need to<18:33:01.320> do<18:33:01.436> the<18:33:01.680> CC<18:33:02.040> and<18:33:02.336> a<18:33:02.580> first<18:33:02.820> or<18:33:03.064> at<18:33:03.244> least<18:33:03.360> one 18:33:03.590 --> 18:33:03.600 align:start position:0% to do the CC and a first or at least one 18:33:03.600 --> 18:33:08.090 align:start position:0% to do the CC and a first or at least one of<18:33:03.720> the<18:33:03.900> CCNA<18:33:04.616> exams<18:33:05.156> the<18:33:06.420> um<18:33:06.420> icnd<18:33:07.196> one<18:33:07.500> would 18:33:08.090 --> 18:33:08.100 align:start position:0% of the CCNA exams the um icnd one would 18:33:08.100 --> 18:33:10.966 align:start position:0% of the CCNA exams the um icnd one would do<18:33:08.280> check<18:33:08.516> so<18:33:09.296> what<18:33:09.476> is<18:33:09.656> it<18:33:09.836> bandwidth<18:33:10.436> attacks 18:33:10.966 --> 18:33:10.976 align:start position:0% do check so what is it bandwidth attacks 18:33:10.976 --> 18:33:13.366 align:start position:0% do check so what is it bandwidth attacks connectivity<18:33:11.580> attacks<18:33:12.244> common<18:33:12.900> types<18:33:13.320> of 18:33:13.366 --> 18:33:13.376 align:start position:0% connectivity attacks common types of 18:33:13.376 --> 18:33:16.090 align:start position:0% connectivity attacks common types of denial<18:33:13.744> of<18:33:13.976> service<18:33:14.156> attacks<18:33:14.836> what<18:33:15.836> is 18:33:16.090 --> 18:33:16.100 align:start position:0% denial of service attacks what is 18:33:16.100 --> 18:33:20.210 align:start position:0% denial of service attacks what is distributed<18:33:17.100> denial<18:33:18.000> of<18:33:18.180> service 18:33:20.210 --> 18:33:20.220 align:start position:0% distributed denial of service 18:33:20.220 --> 18:33:23.450 align:start position:0% distributed denial of service types<18:33:21.064> of<18:33:21.180> those<18:33:21.420> difference<18:33:21.836> between<18:33:22.460> a 18:33:23.450 --> 18:33:23.460 align:start position:0% types of those difference between a 18:33:23.460 --> 18:33:25.990 align:start position:0% types of those difference between a denial<18:33:23.876> of<18:33:24.000> service<18:33:24.244> and<18:33:24.540> distributed 18:33:25.990 --> 18:33:26.000 align:start position:0% denial of service and distributed 18:33:26.000 --> 18:33:29.866 align:start position:0% denial of service and distributed reflective<18:33:27.000> dos<18:33:27.960> attack<18:33:28.280> and<18:33:29.280> then<18:33:29.400> types<18:33:29.756> of 18:33:29.866 --> 18:33:29.876 align:start position:0% reflective dos attack and then types of 18:33:29.876 --> 18:33:31.540 align:start position:0% reflective dos attack and then types of reflective<18:33:30.476> unintentional 18:33:31.540 --> 18:33:31.550 align:start position:0% reflective unintentional 18:33:31.550 --> 18:33:32.926 align:start position:0% reflective unintentional [Music] 18:33:32.926 --> 18:33:32.936 align:start position:0% [Music] 18:33:32.936 --> 18:33:35.570 align:start position:0% [Music] physical<18:33:33.656> infrastructure<18:33:34.256> attacks<18:33:34.920> and<18:33:35.400> how 18:33:35.570 --> 18:33:35.580 align:start position:0% physical infrastructure attacks and how 18:33:35.580 --> 18:33:38.630 align:start position:0% physical infrastructure attacks and how to<18:33:35.756> prevent<18:33:36.436> how<18:33:37.436> to<18:33:37.564> identify<18:33:37.976> denial<18:33:38.516> of 18:33:38.630 --> 18:33:38.640 align:start position:0% to prevent how to identify denial of 18:33:38.640 --> 18:33:40.606 align:start position:0% to prevent how to identify denial of service<18:33:38.820> attack<18:33:39.116> just<18:33:39.836> bear<18:33:40.016> in<18:33:40.196> mind<18:33:40.320> this<18:33:40.500> is 18:33:40.606 --> 18:33:40.616 align:start position:0% service attack just bear in mind this is 18:33:40.616 --> 18:33:42.466 align:start position:0% service attack just bear in mind this is an<18:33:40.796> overview<18:33:41.100> so<18:33:41.460> you<18:33:41.640> need<18:33:41.820> some<18:33:42.000> fairly 18:33:42.466 --> 18:33:42.476 align:start position:0% an overview so you need some fairly 18:33:42.476 --> 18:33:45.950 align:start position:0% an overview so you need some fairly specific<18:33:43.320> training<18:33:44.040> on<18:33:45.064> um<18:33:45.064> hardening<18:33:45.780> your 18:33:45.950 --> 18:33:45.960 align:start position:0% specific training on um hardening your 18:33:45.960 --> 18:33:48.646 align:start position:0% specific training on um hardening your network<18:33:46.220> and<18:33:47.220> also<18:33:47.400> identifying<18:33:48.180> and 18:33:48.646 --> 18:33:48.656 align:start position:0% network and also identifying and 18:33:48.656 --> 18:33:51.890 align:start position:0% network and also identifying and troubleshooting<18:33:49.500> and<18:33:50.460> resolving<18:33:51.000> the<18:33:51.420> denial 18:33:51.890 --> 18:33:51.900 align:start position:0% troubleshooting and resolving the denial 18:33:51.900 --> 18:33:53.570 align:start position:0% troubleshooting and resolving the denial service<18:33:52.256> attack 18:33:53.570 --> 18:33:53.580 align:start position:0% service attack 18:33:53.580 --> 18:33:56.326 align:start position:0% service attack so<18:33:54.064> what<18:33:54.244> is<18:33:54.476> it<18:33:54.744> basically<18:33:55.744> refers<18:33:56.040> to<18:33:56.220> an 18:33:56.326 --> 18:33:56.336 align:start position:0% so what is it basically refers to an 18:33:56.336 --> 18:33:58.606 align:start position:0% so what is it basically refers to an attack<18:33:56.460> on<18:33:56.696> a<18:33:56.876> computer<18:33:57.000> network<18:33:57.420> to<18:33:58.140> make<18:33:58.256> its 18:33:58.606 --> 18:33:58.616 align:start position:0% attack on a computer network to make its 18:33:58.616 --> 18:34:02.506 align:start position:0% attack on a computer network to make its services<18:33:58.756> unavailable<18:33:59.756> to<18:34:00.540> legitimate<18:34:01.080> users 18:34:02.506 --> 18:34:02.516 align:start position:0% services unavailable to legitimate users 18:34:02.516 --> 18:34:05.926 align:start position:0% services unavailable to legitimate users you've<18:34:03.000> heard<18:34:03.180> of<18:34:03.296> it<18:34:03.420> I'm<18:34:03.600> sure<18:34:03.780> in<18:34:04.256> the<18:34:04.376> Press 18:34:05.926 --> 18:34:05.936 align:start position:0% you've heard of it I'm sure in the Press 18:34:05.936 --> 18:34:07.310 align:start position:0% you've heard of it I'm sure in the Press um 18:34:07.310 --> 18:34:07.320 align:start position:0% um 18:34:07.320 --> 18:34:09.770 align:start position:0% um before<18:34:07.976> some<18:34:08.460> big<18:34:08.696> big<18:34:09.180> companies<18:34:09.540> have<18:34:09.656> been 18:34:09.770 --> 18:34:09.780 align:start position:0% before some big big companies have been 18:34:09.780 --> 18:34:11.810 align:start position:0% before some big big companies have been attacked<18:34:10.080> before<18:34:10.640> Delilah<18:34:11.640> service 18:34:11.810 --> 18:34:11.820 align:start position:0% attacked before Delilah service 18:34:11.820 --> 18:34:13.734 align:start position:0% attacked before Delilah service basically<18:34:12.360> attacks<18:34:12.780> the<18:34:13.016> network<18:34:13.256> with 18:34:13.734 --> 18:34:13.744 align:start position:0% basically attacks the network with 18:34:13.744 --> 18:34:16.070 align:start position:0% basically attacks the network with useless<18:34:14.156> traffic 18:34:16.070 --> 18:34:16.080 align:start position:0% useless traffic 18:34:16.080 --> 18:34:19.554 align:start position:0% useless traffic it's<18:34:16.500> a<18:34:16.796> type<18:34:16.976> of<18:34:17.100> cyber<18:34:17.516> threat 18:34:19.554 --> 18:34:19.564 align:start position:0% it's a type of cyber threat 18:34:19.564 --> 18:34:21.890 align:start position:0% it's a type of cyber threat so<18:34:20.040> what<18:34:20.280> do<18:34:20.516> the<18:34:20.696> denial<18:34:21.116> attackers<18:34:21.656> actually 18:34:21.890 --> 18:34:21.900 align:start position:0% so what do the denial attackers actually 18:34:21.900 --> 18:34:25.186 align:start position:0% so what do the denial attackers actually put<18:34:22.140> their<18:34:22.256> effort<18:34:22.500> into<18:34:22.920> doing<18:34:23.336> preventing 18:34:25.186 --> 18:34:25.196 align:start position:0% put their effort into doing preventing 18:34:25.196 --> 18:34:27.170 align:start position:0% put their effort into doing preventing um<18:34:25.256> legitimate<18:34:25.976> users<18:34:26.336> such<18:34:26.580> as<18:34:26.696> members<18:34:27.064> of 18:34:27.170 --> 18:34:27.180 align:start position:0% um legitimate users such as members of 18:34:27.180 --> 18:34:30.710 align:start position:0% um legitimate users such as members of the<18:34:27.360> public<18:34:27.476> or<18:34:27.900> employees<18:34:28.696> from<18:34:29.720> accessing 18:34:30.710 --> 18:34:30.720 align:start position:0% the public or employees from accessing 18:34:30.720 --> 18:34:32.170 align:start position:0% the public or employees from accessing Network<18:34:31.196> Services 18:34:32.170 --> 18:34:32.180 align:start position:0% Network Services 18:34:32.180 --> 18:34:37.686 align:start position:0% Network Services emails<18:34:33.180> websites<18:34:33.960> online<18:34:34.320> banking<18:34:35.280> Etc 18:34:37.686 --> 18:34:37.696 align:start position:0% 18:34:37.696 --> 18:34:41.030 align:start position:0% usually<18:34:38.836> the<18:34:39.836> denial<18:34:40.256> of<18:34:40.376> service<18:34:40.500> attacks 18:34:41.030 --> 18:34:41.040 align:start position:0% usually the denial of service attacks 18:34:41.040 --> 18:34:42.826 align:start position:0% usually the denial of service attacks occur<18:34:41.336> when<18:34:41.516> the<18:34:41.696> attacker<18:34:42.064> floods<18:34:42.600> a 18:34:42.826 --> 18:34:42.836 align:start position:0% occur when the attacker floods a 18:34:42.836 --> 18:34:44.810 align:start position:0% occur when the attacker floods a particular<18:34:43.256> network<18:34:43.564> with<18:34:44.100> a<18:34:44.280> huge<18:34:44.516> amount<18:34:44.696> of 18:34:44.810 --> 18:34:44.820 align:start position:0% particular network with a huge amount of 18:34:44.820 --> 18:34:46.186 align:start position:0% particular network with a huge amount of traffic 18:34:46.186 --> 18:34:46.196 align:start position:0% traffic 18:34:46.196 --> 18:34:48.170 align:start position:0% traffic so<18:34:46.616> for<18:34:46.796> example<18:34:47.040> to<18:34:47.220> access<18:34:47.400> a<18:34:47.696> website<18:34:47.936> we 18:34:48.170 --> 18:34:48.180 align:start position:0% so for example to access a website we 18:34:48.180 --> 18:34:50.326 align:start position:0% so for example to access a website we type<18:34:48.360> in<18:34:48.540> the<18:34:48.656> URL<18:34:49.080> you<18:34:49.500> send<18:34:49.680> a<18:34:49.860> request<18:34:50.100> to 18:34:50.326 --> 18:34:50.336 align:start position:0% type in the URL you send a request to 18:34:50.336 --> 18:34:52.246 align:start position:0% type in the URL you send a request to the<18:34:50.516> web<18:34:51.116> server 18:34:52.246 --> 18:34:52.256 align:start position:0% the web server 18:34:52.256 --> 18:34:54.590 align:start position:0% the web server web<18:34:52.564> server<18:34:52.976> can<18:34:53.156> only<18:34:53.336> process<18:34:53.756> a<18:34:54.180> limited 18:34:54.590 --> 18:34:54.600 align:start position:0% web server can only process a limited 18:34:54.600 --> 18:34:57.170 align:start position:0% web server can only process a limited number<18:34:54.836> of<18:34:55.016> requests<18:34:55.500> at<18:34:55.616> a<18:34:55.796> given<18:34:56.100> time<18:34:56.280> now 18:34:57.170 --> 18:34:57.180 align:start position:0% number of requests at a given time now 18:34:57.180 --> 18:34:58.606 align:start position:0% number of requests at a given time now there's<18:34:57.360> a<18:34:57.540> whole<18:34:57.656> bunch<18:34:57.780> of<18:34:57.900> things<18:34:58.140> that<18:34:58.436> can 18:34:58.606 --> 18:34:58.616 align:start position:0% there's a whole bunch of things that can 18:34:58.616 --> 18:35:02.686 align:start position:0% there's a whole bunch of things that can go<18:34:58.860> on<18:34:59.100> for<18:34:59.460> example<18:34:59.836> uh<18:35:00.836> load<18:35:01.140> balancing<18:35:01.696> and 18:35:02.686 --> 18:35:02.696 align:start position:0% go on for example uh load balancing and 18:35:02.696 --> 18:35:06.770 align:start position:0% go on for example uh load balancing and then<18:35:03.000> CDN<18:35:03.780> cloning<18:35:04.320> the<18:35:04.976> uh<18:35:05.820> website<18:35:06.296> copies 18:35:06.770 --> 18:35:06.780 align:start position:0% then CDN cloning the uh website copies 18:35:06.780 --> 18:35:08.826 align:start position:0% then CDN cloning the uh website copies all<18:35:07.016> over<18:35:07.140> the<18:35:07.320> web<18:35:07.436> but<18:35:07.680> even<18:35:07.920> so 18:35:08.826 --> 18:35:08.836 align:start position:0% all over the web but even so 18:35:08.836 --> 18:35:11.746 align:start position:0% all over the web but even so and<18:35:09.836> there's<18:35:10.564> only<18:35:10.744> a<18:35:10.920> finite<18:35:11.280> amount<18:35:11.640> of 18:35:11.746 --> 18:35:11.756 align:start position:0% and there's only a finite amount of 18:35:11.756 --> 18:35:14.686 align:start position:0% and there's only a finite amount of resources<18:35:12.500> dedicated<18:35:13.500> to<18:35:14.220> all<18:35:14.400> these 18:35:14.686 --> 18:35:14.696 align:start position:0% resources dedicated to all these 18:35:14.696 --> 18:35:18.890 align:start position:0% resources dedicated to all these Solutions<18:35:15.064> and<18:35:15.656> they<18:35:16.016> can<18:35:16.140> be<18:35:16.256> used<18:35:16.436> up 18:35:18.890 --> 18:35:18.900 align:start position:0% 18:35:18.900 --> 18:35:20.630 align:start position:0% when<18:35:19.376> the<18:35:19.500> attacker<18:35:19.860> burdens<18:35:20.220> the<18:35:20.400> server 18:35:20.630 --> 18:35:20.640 align:start position:0% when the attacker burdens the server 18:35:20.640 --> 18:35:22.186 align:start position:0% when the attacker burdens the server we're<18:35:20.820> too<18:35:20.936> many<18:35:21.116> requests<18:35:21.600> the<18:35:21.720> web<18:35:21.900> server 18:35:22.186 --> 18:35:22.196 align:start position:0% we're too many requests the web server 18:35:22.196 --> 18:35:24.590 align:start position:0% we're too many requests the web server is<18:35:22.256> unable<18:35:22.564> to<18:35:22.744> process<18:35:23.220> the<18:35:23.640> legitimate<18:35:24.244> ones 18:35:24.590 --> 18:35:24.600 align:start position:0% is unable to process the legitimate ones 18:35:24.600 --> 18:35:27.350 align:start position:0% is unable to process the legitimate ones as<18:35:25.436> a<18:35:25.564> result<18:35:25.616> you<18:35:26.040> can't<18:35:26.220> access<18:35:26.640> it<18:35:27.064> and 18:35:27.350 --> 18:35:27.360 align:start position:0% as a result you can't access it and 18:35:27.360 --> 18:35:29.926 align:start position:0% as a result you can't access it and that's<18:35:27.780> called<18:35:28.016> the<18:35:28.196> denial<18:35:28.616> of<18:35:28.744> service 18:35:29.926 --> 18:35:29.936 align:start position:0% that's called the denial of service 18:35:29.936 --> 18:35:32.090 align:start position:0% that's called the denial of service good<18:35:30.296> you<18:35:30.600> can<18:35:30.720> then<18:35:30.900> Google<18:35:31.376> denial<18:35:31.920> of 18:35:32.090 --> 18:35:32.100 align:start position:0% good you can then Google denial of 18:35:32.100 --> 18:35:33.646 align:start position:0% good you can then Google denial of service<18:35:32.280> attacks<18:35:32.756> and<18:35:32.876> look<18:35:33.000> at<18:35:33.116> all<18:35:33.244> the<18:35:33.420> news 18:35:33.646 --> 18:35:33.656 align:start position:0% service attacks and look at all the news 18:35:33.656 --> 18:35:38.410 align:start position:0% service attacks and look at all the news stories<18:35:34.016> over<18:35:34.196> the<18:35:34.436> past<18:35:34.616> few<18:35:35.460> years 18:35:38.410 --> 18:35:38.420 align:start position:0% 18:35:38.420 --> 18:35:41.326 align:start position:0% and<18:35:39.420> messages<18:35:39.960> to<18:35:40.436> establish<18:35:40.796> a<18:35:40.976> similar 18:35:41.326 --> 18:35:41.336 align:start position:0% and messages to establish a similar 18:35:41.336 --> 18:35:44.030 align:start position:0% and messages to establish a similar attack<18:35:41.516> only<18:35:42.420> limited<18:35:43.080> the<18:35:43.256> number<18:35:43.436> of<18:35:43.616> emails 18:35:44.030 --> 18:35:44.040 align:start position:0% attack only limited the number of emails 18:35:44.040 --> 18:35:45.890 align:start position:0% attack only limited the number of emails are<18:35:44.100> allowed<18:35:44.460> in<18:35:44.696> your<18:35:44.876> corporate<18:35:45.360> accounts 18:35:45.890 --> 18:35:45.900 align:start position:0% are allowed in your corporate accounts 18:35:45.900 --> 18:35:49.006 align:start position:0% are allowed in your corporate accounts usually<18:35:46.140> mind<18:35:46.500> you<18:35:46.680> even<18:35:46.920> large 18:35:49.006 --> 18:35:49.016 align:start position:0% usually mind you even large 18:35:49.016 --> 18:35:52.426 align:start position:0% usually mind you even large um<18:35:49.080> free<18:35:49.564> providers<18:35:50.040> like<18:35:50.420> Gmail<18:35:51.420> have<18:35:52.196> got<18:35:52.376> a 18:35:52.426 --> 18:35:52.436 align:start position:0% um free providers like Gmail have got a 18:35:52.436 --> 18:35:56.390 align:start position:0% um free providers like Gmail have got a limited<18:35:52.860> amount<18:35:53.460> of<18:35:54.000> um<18:35:54.064> storage 18:35:56.390 --> 18:35:56.400 align:start position:0% limited amount of um storage 18:35:56.400 --> 18:35:58.734 align:start position:0% limited amount of um storage so<18:35:56.876> as<18:35:57.064> a<18:35:57.244> result<18:35:57.360> the<18:35:57.720> attacker<18:35:58.196> can<18:35:58.436> stop<18:35:58.564> the 18:35:58.734 --> 18:35:58.744 align:start position:0% so as a result the attacker can stop the 18:35:58.744 --> 18:36:01.606 align:start position:0% so as a result the attacker can stop the users<18:35:59.040> getting<18:35:59.336> legitimate<18:36:00.180> access<18:36:00.420> to<18:36:01.320> their 18:36:01.606 --> 18:36:01.616 align:start position:0% users getting legitimate access to their 18:36:01.616 --> 18:36:02.990 align:start position:0% users getting legitimate access to their account 18:36:02.990 --> 18:36:03.000 align:start position:0% account 18:36:03.000 --> 18:36:05.326 align:start position:0% account and<18:36:03.540> in<18:36:03.836> an<18:36:04.016> email<18:36:04.140> bomb<18:36:04.564> the<18:36:04.860> denial<18:36:05.220> of 18:36:05.326 --> 18:36:05.336 align:start position:0% and in an email bomb the denial of 18:36:05.336 --> 18:36:07.130 align:start position:0% and in an email bomb the denial of service<18:36:05.640> attack<18:36:05.936> the<18:36:06.360> attacker<18:36:06.656> send<18:36:06.836> a<18:36:07.080> lot 18:36:07.130 --> 18:36:07.140 align:start position:0% service attack the attacker send a lot 18:36:07.140 --> 18:36:08.810 align:start position:0% service attack the attacker send a lot of<18:36:07.320> spam<18:36:07.500> emails<18:36:08.040> and<18:36:08.156> they<18:36:08.336> disable<18:36:08.580> the 18:36:08.810 --> 18:36:08.820 align:start position:0% of spam emails and they disable the 18:36:08.820 --> 18:36:11.146 align:start position:0% of spam emails and they disable the actual<18:36:09.180> email<18:36:09.656> server<18:36:10.196> rather<18:36:10.564> than<18:36:10.744> just<18:36:10.976> an 18:36:11.146 --> 18:36:11.156 align:start position:0% actual email server rather than just an 18:36:11.156 --> 18:36:14.146 align:start position:0% actual email server rather than just an account<18:36:11.336> on<18:36:12.296> the<18:36:12.476> server 18:36:14.146 --> 18:36:14.156 align:start position:0% account on the server 18:36:14.156 --> 18:36:16.366 align:start position:0% account on the server generally<18:36:15.000> not<18:36:15.296> concerned<18:36:15.780> with<18:36:15.960> stealing 18:36:16.366 --> 18:36:16.376 align:start position:0% generally not concerned with stealing 18:36:16.376 --> 18:36:17.746 align:start position:0% generally not concerned with stealing information<18:36:16.616> it's<18:36:17.220> just<18:36:17.460> quite<18:36:17.580> an 18:36:17.746 --> 18:36:17.756 align:start position:0% information it's just quite an 18:36:17.756 --> 18:36:19.310 align:start position:0% information it's just quite an aggressive<18:36:18.180> way<18:36:18.360> of<18:36:18.540> bringing<18:36:18.900> down<18:36:19.016> a 18:36:19.310 --> 18:36:19.320 align:start position:0% aggressive way of bringing down a 18:36:19.320 --> 18:36:21.106 align:start position:0% aggressive way of bringing down a particular<18:36:19.564> service 18:36:21.106 --> 18:36:21.116 align:start position:0% particular service 18:36:21.116 --> 18:36:23.630 align:start position:0% particular service it<18:36:21.244> could<18:36:21.420> be<18:36:21.600> a<18:36:21.780> person<18:36:22.016> a<18:36:22.680> business<18:36:23.040> or<18:36:23.460> an 18:36:23.630 --> 18:36:23.640 align:start position:0% it could be a person a business or an 18:36:23.640 --> 18:36:25.426 align:start position:0% it could be a person a business or an entire<18:36:23.936> company 18:36:25.426 --> 18:36:25.436 align:start position:0% entire company 18:36:25.436 --> 18:36:27.234 align:start position:0% entire company they<18:36:25.920> can<18:36:26.100> attack<18:36:26.220> and<18:36:26.460> Destroy<18:36:26.820> files<18:36:27.116> in 18:36:27.234 --> 18:36:27.244 align:start position:0% they can attack and Destroy files in 18:36:27.244 --> 18:36:30.710 align:start position:0% they can attack and Destroy files in affected<18:36:27.720> computer<18:36:28.140> system<18:36:28.976> or<18:36:29.220> Network 18:36:30.710 --> 18:36:30.720 align:start position:0% affected computer system or Network 18:36:30.720 --> 18:36:33.054 align:start position:0% affected computer system or Network and<18:36:31.256> some<18:36:31.500> situations<18:36:32.040> the<18:36:32.400> Denali<18:36:32.820> service 18:36:33.054 --> 18:36:33.064 align:start position:0% and some situations the Denali service 18:36:33.064 --> 18:36:35.506 align:start position:0% and some situations the Denali service stack<18:36:33.476> actually<18:36:33.656> affects<18:36:34.140> the<18:36:34.256> website 18:36:35.506 --> 18:36:35.516 align:start position:0% stack actually affects the website 18:36:35.516 --> 18:36:38.506 align:start position:0% stack actually affects the website um accessed<18:36:36.064> by<18:36:36.244> the<18:36:36.476> users 18:36:38.506 --> 18:36:38.516 align:start position:0% um accessed by the users 18:36:38.516 --> 18:36:40.910 align:start position:0% um accessed by the users most<18:36:39.296> uh<18:36:39.600> denial<18:36:40.016> of<18:36:40.196> service<18:36:40.320> attacks<18:36:40.796> are 18:36:40.910 --> 18:36:40.920 align:start position:0% most uh denial of service attacks are 18:36:40.920 --> 18:36:43.246 align:start position:0% most uh denial of service attacks are aimed<18:36:41.280> at<18:36:41.400> the<18:36:41.820> computers<18:36:42.244> Network<18:36:42.476> bandwidth 18:36:43.246 --> 18:36:43.256 align:start position:0% aimed at the computers Network bandwidth 18:36:43.256 --> 18:36:44.686 align:start position:0% aimed at the computers Network bandwidth connectivity 18:36:44.686 --> 18:36:44.696 align:start position:0% connectivity 18:36:44.696 --> 18:36:49.606 align:start position:0% connectivity our<18:36:45.420> resources<18:36:46.016> also<18:36:46.500> server<18:36:47.460> resources 18:36:49.606 --> 18:36:49.616 align:start position:0% our resources also server resources 18:36:49.616 --> 18:36:51.826 align:start position:0% our resources also server resources bandwidth<18:36:50.336> attacks<18:36:50.696> on<18:36:50.876> the<18:36:51.116> computer<18:36:51.420> or 18:36:51.826 --> 18:36:51.836 align:start position:0% bandwidth attacks on the computer or 18:36:51.836 --> 18:36:53.450 align:start position:0% bandwidth attacks on the computer or network<18:36:52.080> with<18:36:52.376> a<18:36:52.564> huge<18:36:52.796> amount<18:36:53.040> of<18:36:53.156> traffic 18:36:53.450 --> 18:36:53.460 align:start position:0% network with a huge amount of traffic 18:36:53.460 --> 18:36:56.686 align:start position:0% network with a huge amount of traffic huge<18:36:54.244> burst<18:36:54.600> of<18:36:54.720> traffic<18:36:55.336> legitimate<18:36:56.336> users 18:36:56.686 --> 18:36:56.696 align:start position:0% huge burst of traffic legitimate users 18:36:56.696 --> 18:37:01.186 align:start position:0% huge burst of traffic legitimate users can't<18:36:56.936> access<18:36:57.360> every<18:36:58.080> network<18:36:58.436> resources 18:37:01.186 --> 18:37:01.196 align:start position:0% 18:37:01.196 --> 18:37:03.106 align:start position:0% the<18:37:01.744> connectivity<18:37:02.280> attacks<18:37:02.756> harm<18:37:02.936> the 18:37:03.106 --> 18:37:03.116 align:start position:0% the connectivity attacks harm the 18:37:03.116 --> 18:37:04.966 align:start position:0% the connectivity attacks harm the computer<18:37:03.296> with<18:37:03.656> a<18:37:03.836> large<18:37:04.016> amount<18:37:04.796> of 18:37:04.966 --> 18:37:04.976 align:start position:0% computer with a large amount of 18:37:04.976 --> 18:37:07.310 align:start position:0% computer with a large amount of connection<18:37:05.280> requests 18:37:07.310 --> 18:37:07.320 align:start position:0% connection requests 18:37:07.320 --> 18:37:09.950 align:start position:0% connection requests available<18:37:07.860> operating<18:37:08.460> system<18:37:08.820> resources<18:37:09.720> are 18:37:09.950 --> 18:37:09.960 align:start position:0% available operating system resources are 18:37:09.960 --> 18:37:11.926 align:start position:0% available operating system resources are quickly<18:37:10.256> consumed<18:37:10.860> and<18:37:11.400> the<18:37:11.580> computers 18:37:11.926 --> 18:37:11.936 align:start position:0% quickly consumed and the computers 18:37:11.936 --> 18:37:14.390 align:start position:0% quickly consumed and the computers enable<18:37:12.244> once<18:37:12.720> again<18:37:12.836> to<18:37:13.500> perform<18:37:13.616> legitimate 18:37:14.390 --> 18:37:14.400 align:start position:0% enable once again to perform legitimate 18:37:14.400 --> 18:37:16.186 align:start position:0% enable once again to perform legitimate requests 18:37:16.186 --> 18:37:16.196 align:start position:0% requests 18:37:16.196 --> 18:37:18.350 align:start position:0% requests another<18:37:16.796> common<18:37:17.156> type<18:37:17.460> of<18:37:17.640> denial<18:37:18.064> of<18:37:18.180> service 18:37:18.350 --> 18:37:18.360 align:start position:0% another common type of denial of service 18:37:18.360 --> 18:37:20.990 align:start position:0% another common type of denial of service attack<18:37:18.600> is<18:37:18.836> a<18:37:19.016> buffer<18:37:19.320> overflow<18:37:19.920> all<18:37:20.696> devices 18:37:20.990 --> 18:37:21.000 align:start position:0% attack is a buffer overflow all devices 18:37:21.000 --> 18:37:24.286 align:start position:0% attack is a buffer overflow all devices routers<18:37:21.836> switches<18:37:22.616> have<18:37:23.580> buffers<18:37:24.064> that 18:37:24.286 --> 18:37:24.296 align:start position:0% routers switches have buffers that 18:37:24.296 --> 18:37:26.234 align:start position:0% routers switches have buffers that manage<18:37:24.836> a<18:37:25.080> temporary 18:37:26.234 --> 18:37:26.244 align:start position:0% manage a temporary 18:37:26.244 --> 18:37:29.090 align:start position:0% manage a temporary excess<18:37:27.244> amount<18:37:27.600> of<18:37:27.720> traffic 18:37:29.090 --> 18:37:29.100 align:start position:0% excess amount of traffic 18:37:29.100 --> 18:37:31.426 align:start position:0% excess amount of traffic send<18:37:29.696> and<18:37:29.876> receive<18:37:30.180> buffers<18:37:30.656> and<18:37:31.016> if<18:37:31.196> these 18:37:31.426 --> 18:37:31.436 align:start position:0% send and receive buffers and if these 18:37:31.436 --> 18:37:32.810 align:start position:0% send and receive buffers and if these buffers<18:37:31.744> are<18:37:31.920> actually<18:37:32.040> overflowed<18:37:32.640> then 18:37:32.810 --> 18:37:32.820 align:start position:0% buffers are actually overflowed then 18:37:32.820 --> 18:37:34.850 align:start position:0% buffers are actually overflowed then depending<18:37:33.780> on<18:37:33.836> how<18:37:34.016> the<18:37:34.196> devices<18:37:34.500> are 18:37:34.850 --> 18:37:34.860 align:start position:0% depending on how the devices are 18:37:34.860 --> 18:37:36.410 align:start position:0% depending on how the devices are configured<18:37:35.220> and<18:37:35.336> what<18:37:35.516> it<18:37:35.640> is<18:37:35.820> then<18:37:36.180> it's 18:37:36.410 --> 18:37:36.420 align:start position:0% configured and what it is then it's 18:37:36.420 --> 18:37:38.990 align:start position:0% configured and what it is then it's going<18:37:36.656> to<18:37:36.720> cause<18:37:36.900> problems<18:37:37.564> and<18:37:37.744> packet<18:37:38.100> loss 18:37:38.990 --> 18:37:39.000 align:start position:0% going to cause problems and packet loss 18:37:39.000 --> 18:37:43.186 align:start position:0% going to cause problems and packet loss the<18:37:39.600> sin<18:37:39.836> attacks<18:37:40.460> teardrop<18:37:41.460> attack 18:37:43.186 --> 18:37:43.196 align:start position:0% the sin attacks teardrop attack 18:37:43.196 --> 18:37:46.606 align:start position:0% the sin attacks teardrop attack Smurf<18:37:44.040> attacks<18:37:44.780> viruses<18:37:45.780> a<18:37:46.256> whole<18:37:46.376> bunch 18:37:46.606 --> 18:37:46.616 align:start position:0% Smurf attacks viruses a whole bunch 18:37:46.616 --> 18:37:47.686 align:start position:0% Smurf attacks viruses a whole bunch actually 18:37:47.686 --> 18:37:47.696 align:start position:0% actually 18:37:47.696 --> 18:37:49.926 align:start position:0% actually the<18:37:48.064> buffer<18:37:48.420> overflow<18:37:48.900> is<18:37:49.016> the<18:37:49.256> most<18:37:49.436> used 18:37:49.926 --> 18:37:49.936 align:start position:0% the buffer overflow is the most used 18:37:49.936 --> 18:37:51.950 align:start position:0% the buffer overflow is the most used distributes<18:37:50.936> of<18:37:51.064> a<18:37:51.244> huge<18:37:51.420> led<18:37:51.600> to<18:37:51.656> a<18:37:51.836> network 18:37:51.950 --> 18:37:51.960 align:start position:0% distributes of a huge led to a network 18:37:51.960 --> 18:37:55.734 align:start position:0% distributes of a huge led to a network more<18:37:52.860> than<18:37:53.040> the<18:37:53.640> um<18:37:53.640> buffer<18:37:54.116> is<18:37:54.780> um<18:37:54.780> able<18:37:55.680> to 18:37:55.734 --> 18:37:55.744 align:start position:0% more than the um buffer is um able to 18:37:55.744 --> 18:37:57.234 align:start position:0% more than the um buffer is um able to handle 18:37:57.234 --> 18:37:57.244 align:start position:0% handle 18:37:57.244 --> 18:37:58.786 align:start position:0% handle when<18:37:57.600> the<18:37:57.780> attacker<18:37:58.080> has<18:37:58.256> awareness<18:37:58.680> about 18:37:58.786 --> 18:37:58.796 align:start position:0% when the attacker has awareness about 18:37:58.796 --> 18:38:00.590 align:start position:0% when the attacker has awareness about the<18:37:59.040> weaknesses<18:37:59.460> of<18:37:59.580> the<18:37:59.696> target<18:37:59.876> system<18:38:00.296> or 18:38:00.590 --> 18:38:00.600 align:start position:0% the weaknesses of the target system or 18:38:00.600 --> 18:38:02.210 align:start position:0% the weaknesses of the target system or network<18:38:00.780> that's<18:38:01.140> when<18:38:01.320> you'll<18:38:01.500> get<18:38:01.680> a<18:38:01.796> buffer 18:38:02.210 --> 18:38:02.220 align:start position:0% network that's when you'll get a buffer 18:38:02.220 --> 18:38:05.506 align:start position:0% network that's when you'll get a buffer overflow<18:38:02.936> attack<18:38:03.180> and<18:38:03.960> they<18:38:04.140> can<18:38:04.516> Target 18:38:05.506 --> 18:38:05.516 align:start position:0% overflow attack and they can Target 18:38:05.516 --> 18:38:08.866 align:start position:0% overflow attack and they can Target certain<18:38:06.476> vendors<18:38:07.256> or<18:38:07.564> certain<18:38:07.796> devices<18:38:08.280> such 18:38:08.866 --> 18:38:08.876 align:start position:0% certain vendors or certain devices such 18:38:08.876 --> 18:38:12.106 align:start position:0% certain vendors or certain devices such as<18:38:09.116> Cisco<18:38:09.540> routers<18:38:10.080> or<18:38:10.744> uh<18:38:11.336> the<18:38:11.756> vendors 18:38:12.106 --> 18:38:12.116 align:start position:0% as Cisco routers or uh the vendors 18:38:12.116 --> 18:38:14.270 align:start position:0% as Cisco routers or uh the vendors firewalls<18:38:13.196> Etc 18:38:14.270 --> 18:38:14.280 align:start position:0% firewalls Etc 18:38:14.280 --> 18:38:16.006 align:start position:0% firewalls Etc once<18:38:14.820> when<18:38:15.000> the<18:38:15.116> attacker<18:38:15.420> simply<18:38:15.656> tries<18:38:15.900> to 18:38:16.006 --> 18:38:16.016 align:start position:0% once when the attacker simply tries to 18:38:16.016 --> 18:38:17.390 align:start position:0% once when the attacker simply tries to attack<18:38:16.140> not<18:38:16.436> knowing<18:38:16.796> whether<18:38:16.976> it's<18:38:17.156> going<18:38:17.336> to 18:38:17.390 --> 18:38:17.400 align:start position:0% attack not knowing whether it's going to 18:38:17.400 --> 18:38:19.670 align:start position:0% attack not knowing whether it's going to work<18:38:17.516> so<18:38:17.756> it's<18:38:18.000> a<18:38:18.244> quite<18:38:18.540> a<18:38:18.836> Brute<18:38:19.376> Force 18:38:19.670 --> 18:38:19.680 align:start position:0% work so it's a quite a Brute Force 18:38:19.680 --> 18:38:20.506 align:start position:0% work so it's a quite a Brute Force attack 18:38:20.506 --> 18:38:20.516 align:start position:0% attack 18:38:20.516 --> 18:38:22.246 align:start position:0% attack but<18:38:20.820> for<18:38:21.064> attacks<18:38:21.476> are<18:38:21.540> based<18:38:21.836> on<18:38:21.900> the<18:38:22.080> system 18:38:22.246 --> 18:38:22.256 align:start position:0% but for attacks are based on the system 18:38:22.256 --> 18:38:26.746 align:start position:0% but for attacks are based on the system or<18:38:22.680> programs<18:38:23.220> above<18:38:23.580> their<18:38:23.876> characteristics 18:38:26.746 --> 18:38:26.756 align:start position:0% 18:38:26.756 --> 18:38:28.910 align:start position:0% and<18:38:27.180> other<18:38:27.420> way<18:38:27.656> distribute<18:38:28.320> emails 18:38:28.910 --> 18:38:28.920 align:start position:0% and other way distribute emails 18:38:28.920 --> 18:38:31.790 align:start position:0% and other way distribute emails including<18:38:29.424> 256<18:38:30.424> character<18:38:30.960> file<18:38:31.192> names<18:38:31.504> which 18:38:31.790 --> 18:38:31.800 align:start position:0% including 256 character file names which 18:38:31.800 --> 18:38:33.950 align:start position:0% including 256 character file names which all<18:38:32.040> take<18:38:32.336> a<18:38:32.760> matter<18:38:33.000> of<18:38:33.120> amount<18:38:33.480> of<18:38:33.600> time<18:38:33.720> to 18:38:33.950 --> 18:38:33.960 align:start position:0% all take a matter of amount of time to 18:38:33.960 --> 18:38:38.774 align:start position:0% all take a matter of amount of time to process<18:38:34.440> so<18:38:35.336> the<18:38:35.576> huge<18:38:35.936> icmp<18:38:36.656> packets 18:38:38.774 --> 18:38:38.784 align:start position:0% process so the huge icmp packets 18:38:38.784 --> 18:38:41.094 align:start position:0% process so the huge icmp packets email<18:38:39.784> messages<18:38:40.144> including<18:38:40.800> a<18:38:40.976> from 18:38:41.094 --> 18:38:41.104 align:start position:0% email messages including a from 18:38:41.104 --> 18:38:43.454 align:start position:0% email messages including a from statement<18:38:41.640> that<18:38:42.176> is<18:38:42.296> more<18:38:42.536> characters<18:38:42.784> than 18:38:43.454 --> 18:38:43.464 align:start position:0% statement that is more characters than 18:38:43.464 --> 18:38:50.390 align:start position:0% statement that is more characters than 256<18:38:44.480> seems<18:38:45.480> to<18:38:45.536> be<18:38:45.656> the<18:38:45.896> limit<18:38:46.080> for<18:38:46.440> emails 18:38:50.390 --> 18:38:50.400 align:start position:0% 18:38:50.400 --> 18:38:52.734 align:start position:0% now<18:38:50.936> this<18:38:51.360> is<18:38:51.480> a<18:38:51.656> sin<18:38:51.832> and<18:38:52.016> synark<18:38:52.376> which<18:38:52.616> you 18:38:52.734 --> 18:38:52.744 align:start position:0% now this is a sin and synark which you 18:38:52.744 --> 18:38:55.366 align:start position:0% now this is a sin and synark which you should<18:38:52.856> be<18:38:53.040> familiar<18:38:53.400> with<18:38:53.576> from<18:38:54.176> the<18:38:54.656> network 18:38:55.366 --> 18:38:55.376 align:start position:0% should be familiar with from the network 18:38:55.376 --> 18:38:58.486 align:start position:0% should be familiar with from the network of<18:38:56.216> a<18:38:56.824> plus<18:38:57.064> and<18:38:57.480> and<18:38:57.896> the<18:38:58.144> other<18:38:58.256> network 18:38:58.486 --> 18:38:58.496 align:start position:0% of a plus and and the other network 18:38:58.496 --> 18:38:59.926 align:start position:0% of a plus and and the other network research<18:38:59.040> you've<18:38:59.280> done<18:38:59.400> this<18:38:59.640> is<18:38:59.760> what 18:38:59.926 --> 18:38:59.936 align:start position:0% research you've done this is what 18:38:59.936 --> 18:39:02.030 align:start position:0% research you've done this is what happens<18:39:00.120> before<18:39:00.480> a<18:39:00.784> connection<18:39:00.960> can<18:39:01.856> actually 18:39:02.030 --> 18:39:02.040 align:start position:0% happens before a connection can actually 18:39:02.040 --> 18:39:05.094 align:start position:0% happens before a connection can actually take<18:39:02.336> place<18:39:02.576> if<18:39:02.872> you're<18:39:03.000> using<18:39:03.296> TCP 18:39:05.094 --> 18:39:05.104 align:start position:0% take place if you're using TCP 18:39:05.104 --> 18:39:07.494 align:start position:0% take place if you're using TCP so<18:39:05.696> with<18:39:05.936> a<18:39:06.176> cell<18:39:06.360> attack<18:39:06.536> the<18:39:06.832> attacker<18:39:07.144> sends 18:39:07.494 --> 18:39:07.504 align:start position:0% so with a cell attack the attacker sends 18:39:07.504 --> 18:39:09.774 align:start position:0% so with a cell attack the attacker sends a<18:39:07.616> TCP<18:39:08.104> connection<18:39:08.280> request<18:39:08.872> faster<18:39:09.296> than<18:39:09.536> the 18:39:09.774 --> 18:39:09.784 align:start position:0% a TCP connection request faster than the 18:39:09.784 --> 18:39:13.182 align:start position:0% a TCP connection request faster than the Target<18:39:09.960> computers<18:39:10.936> processing<18:39:11.936> speed<18:39:12.192> using 18:39:13.182 --> 18:39:13.192 align:start position:0% Target computers processing speed using 18:39:13.192 --> 18:39:15.822 align:start position:0% Target computers processing speed using client<18:39:13.504> server<18:39:13.920> technology<18:39:14.336> it<18:39:15.120> begins<18:39:15.720> to 18:39:15.822 --> 18:39:15.832 align:start position:0% client server technology it begins to 18:39:15.832 --> 18:39:18.286 align:start position:0% client server technology it begins to establish<18:39:16.320> a<18:39:16.680> three-way<18:39:17.040> handshake 18:39:18.286 --> 18:39:18.296 align:start position:0% establish a three-way handshake 18:39:18.296 --> 18:39:21.590 align:start position:0% establish a three-way handshake so<18:39:18.896> you'd<18:39:19.144> have<18:39:19.320> a<18:39:19.504> sin<18:39:19.680> sinach<18:39:20.280> sin<18:39:21.176> and<18:39:21.360> there 18:39:21.590 --> 18:39:21.600 align:start position:0% so you'd have a sin sinach sin and there 18:39:21.600 --> 18:39:23.206 align:start position:0% so you'd have a sin sinach sin and there should<18:39:21.784> be<18:39:21.960> an<18:39:22.256> acknowledgment<18:39:22.800> happens 18:39:23.206 --> 18:39:23.216 align:start position:0% should be an acknowledgment happens 18:39:23.216 --> 18:39:26.030 align:start position:0% should be an acknowledgment happens before<18:39:24.176> the<18:39:24.720> data<18:39:25.080> sent 18:39:26.030 --> 18:39:26.040 align:start position:0% before the data sent 18:39:26.040 --> 18:39:28.670 align:start position:0% before the data sent that<18:39:26.512> doesn't<18:39:26.640> actually<18:39:26.872> happen 18:39:28.670 --> 18:39:28.680 align:start position:0% that doesn't actually happen 18:39:28.680 --> 18:39:30.166 align:start position:0% that doesn't actually happen so<18:39:29.160> client<18:39:29.400> sends<18:39:29.872> a<18:39:29.936> collection 18:39:30.166 --> 18:39:30.176 align:start position:0% so client sends a collection 18:39:30.176 --> 18:39:32.326 align:start position:0% so client sends a collection establishment<18:39:30.784> using<18:39:31.192> the<18:39:31.440> sin<18:39:31.744> synchronized 18:39:32.326 --> 18:39:32.336 align:start position:0% establishment using the sin synchronized 18:39:32.336 --> 18:39:33.470 align:start position:0% establishment using the sin synchronized message 18:39:33.470 --> 18:39:33.480 align:start position:0% message 18:39:33.480 --> 18:39:36.230 align:start position:0% message a<18:39:33.896> server<18:39:34.320> can<18:39:35.104> then<18:39:35.336> send<18:39:35.696> a<18:39:35.936> sin 18:39:36.230 --> 18:39:36.240 align:start position:0% a server can then send a sin 18:39:36.240 --> 18:39:38.926 align:start position:0% a server can then send a sin synchronization<18:39:37.192> acknowledgment<18:39:38.104> client 18:39:38.926 --> 18:39:38.936 align:start position:0% synchronization acknowledgment client 18:39:38.936 --> 18:39:41.326 align:start position:0% synchronization acknowledgment client responds<18:39:39.360> with<18:39:39.480> an<18:39:39.656> act<18:39:39.896> an<18:39:40.192> act<18:39:40.376> message<18:39:40.680> and 18:39:41.326 --> 18:39:41.336 align:start position:0% responds with an act an act message and 18:39:41.336 --> 18:39:43.430 align:start position:0% responds with an act an act message and the<18:39:41.464> connection<18:39:41.576> is<18:39:41.936> then<18:39:42.120> established 18:39:43.430 --> 18:39:43.440 align:start position:0% the connection is then established 18:39:43.440 --> 18:39:46.734 align:start position:0% the connection is then established if<18:39:43.976> the<18:39:44.160> attacker<18:39:44.896> sends<18:39:45.896> repetitive<18:39:46.376> sin 18:39:46.734 --> 18:39:46.744 align:start position:0% if the attacker sends repetitive sin 18:39:46.744 --> 18:39:49.494 align:start position:0% if the attacker sends repetitive sin packets<18:39:47.104> to<18:39:47.280> every<18:39:47.464> port<18:39:47.832> using<18:39:48.832> a<18:39:49.016> fake<18:39:49.144> IP 18:39:49.494 --> 18:39:49.504 align:start position:0% packets to every port using a fake IP 18:39:49.504 --> 18:39:51.470 align:start position:0% packets to every port using a fake IP address<18:39:49.744> the<18:39:50.512> server<18:39:50.824> establishes 18:39:51.470 --> 18:39:51.480 align:start position:0% address the server establishes 18:39:51.480 --> 18:39:53.326 align:start position:0% address the server establishes Communications 18:39:53.326 --> 18:39:53.336 align:start position:0% Communications 18:39:53.336 --> 18:39:55.494 align:start position:0% Communications and<18:39:53.872> responds<18:39:54.360> to<18:39:54.424> all<18:39:54.536> requests<18:39:55.016> and<18:39:55.192> what<18:39:55.376> it 18:39:55.494 --> 18:39:55.504 align:start position:0% and responds to all requests and what it 18:39:55.504 --> 18:39:57.886 align:start position:0% and responds to all requests and what it also<18:39:55.744> does<18:39:55.920> is<18:39:56.104> it<18:39:56.576> leaves<18:39:56.936> a 18:39:57.886 --> 18:39:57.896 align:start position:0% also does is it leaves a 18:39:57.896 --> 18:40:00.134 align:start position:0% also does is it leaves a a<18:39:58.376> window<18:39:58.800> open<18:39:59.104> for<18:39:59.400> the<18:39:59.576> actual 18:40:00.134 --> 18:40:00.144 align:start position:0% a window open for the actual 18:40:00.144 --> 18:40:03.110 align:start position:0% a window open for the actual Communications<18:40:01.144> to<18:40:01.440> take<18:40:01.680> place<18:40:01.856> so<18:40:02.216> for<18:40:02.824> each 18:40:03.110 --> 18:40:03.120 align:start position:0% Communications to take place so for each 18:40:03.120 --> 18:40:05.630 align:start position:0% Communications to take place so for each request<18:40:03.656> in<18:40:03.960> request<18:40:04.376> for<18:40:04.976> a<18:40:05.104> certain<18:40:05.280> period 18:40:05.630 --> 18:40:05.640 align:start position:0% request in request for a certain period 18:40:05.640 --> 18:40:08.630 align:start position:0% request in request for a certain period of<18:40:05.760> time<18:40:06.000> depending<18:40:06.720> on<18:40:06.896> the<18:40:07.016> traffic<18:40:07.192> it<18:40:08.160> will 18:40:08.630 --> 18:40:08.640 align:start position:0% of time depending on the traffic it will 18:40:08.640 --> 18:40:11.030 align:start position:0% of time depending on the traffic it will um Reserve<18:40:09.360> resources 18:40:11.030 --> 18:40:11.040 align:start position:0% um Reserve resources 18:40:11.040 --> 18:40:13.070 align:start position:0% um Reserve resources replies<18:40:11.576> to<18:40:11.760> each<18:40:11.936> attempt<18:40:12.360> with<18:40:12.536> a<18:40:12.720> synap 18:40:13.070 --> 18:40:13.080 align:start position:0% replies to each attempt with a synap 18:40:13.080 --> 18:40:16.006 align:start position:0% replies to each attempt with a synap packet<18:40:13.440> from<18:40:13.680> every<18:40:13.920> open<18:40:14.160> port 18:40:16.006 --> 18:40:16.016 align:start position:0% packet from every open port 18:40:16.016 --> 18:40:18.950 align:start position:0% packet from every open port okay<18:40:16.496> teardrop<18:40:17.216> account<18:40:17.400> attack<18:40:18.360> sends 18:40:18.950 --> 18:40:18.960 align:start position:0% okay teardrop account attack sends 18:40:18.960 --> 18:40:22.366 align:start position:0% okay teardrop account attack sends fragmented<18:40:19.440> packets<18:40:19.800> to<18:40:20.040> a<18:40:20.216> Target<18:40:20.464> computer 18:40:22.366 --> 18:40:22.376 align:start position:0% fragmented packets to a Target computer 18:40:22.376 --> 18:40:24.230 align:start position:0% fragmented packets to a Target computer when<18:40:22.856> the<18:40:22.976> computer<18:40:23.160> receives<18:40:23.696> the<18:40:23.872> packets 18:40:24.230 --> 18:40:24.240 align:start position:0% when the computer receives the packets 18:40:24.240 --> 18:40:25.966 align:start position:0% when the computer receives the packets it's<18:40:24.480> enabled<18:40:24.960> to<18:40:25.080> reassemble<18:40:25.616> them<18:40:25.744> because 18:40:25.966 --> 18:40:25.976 align:start position:0% it's enabled to reassemble them because 18:40:25.976 --> 18:40:27.230 align:start position:0% it's enabled to reassemble them because of<18:40:26.160> the<18:40:26.336> following 18:40:27.230 --> 18:40:27.240 align:start position:0% of the following 18:40:27.240 --> 18:40:31.182 align:start position:0% of the following a<18:40:27.784> bug<18:40:27.960> in<18:40:28.144> the<18:40:28.320> TCP<18:40:28.744> fragment<18:40:29.464> reassembly 18:40:31.182 --> 18:40:31.192 align:start position:0% a bug in the TCP fragment reassembly 18:40:31.192 --> 18:40:33.286 align:start position:0% a bug in the TCP fragment reassembly overlapping<18:40:32.104> packets 18:40:33.286 --> 18:40:33.296 align:start position:0% overlapping packets 18:40:33.296 --> 18:40:36.110 align:start position:0% overlapping packets crashing<18:40:34.016> of<18:40:34.192> network<18:40:34.560> devices 18:40:36.110 --> 18:40:36.120 align:start position:0% crashing of network devices 18:40:36.120 --> 18:40:38.094 align:start position:0% crashing of network devices can<18:40:36.480> usually<18:40:36.832> happen<18:40:37.016> on<18:40:37.440> older<18:40:37.800> operating 18:40:38.094 --> 18:40:38.104 align:start position:0% can usually happen on older operating 18:40:38.104 --> 18:40:40.606 align:start position:0% can usually happen on older operating systems<18:40:38.696> some<18:40:39.480> of<18:40:39.656> you<18:40:39.656> might<18:40:39.832> remember<18:40:40.192> these 18:40:40.606 --> 18:40:40.616 align:start position:0% systems some of you might remember these 18:40:40.616 --> 18:40:45.166 align:start position:0% systems some of you might remember these three<18:40:40.856> Windows<18:40:41.696> 3.1<18:40:42.504> Windows<18:40:43.504> 95 18:40:45.166 --> 18:40:45.176 align:start position:0% three Windows 3.1 Windows 95 18:40:45.176 --> 18:40:48.230 align:start position:0% three Windows 3.1 Windows 95 Windows<18:40:45.896> NT<18:40:46.320> and<18:40:47.160> some<18:40:47.336> versions<18:40:47.760> of<18:40:47.872> fair 18:40:48.230 --> 18:40:48.240 align:start position:0% Windows NT and some versions of fair 18:40:48.240 --> 18:40:51.166 align:start position:0% Windows NT and some versions of fair Linux 18:40:51.166 --> 18:40:51.176 align:start position:0% 18:40:51.176 --> 18:40:52.910 align:start position:0% some<18:40:51.480> Earth<18:40:51.720> attacks<18:40:52.192> is<18:40:52.256> where<18:40:52.440> the<18:40:52.560> attacker 18:40:52.910 --> 18:40:52.920 align:start position:0% some Earth attacks is where the attacker 18:40:52.920 --> 18:40:54.646 align:start position:0% some Earth attacks is where the attacker fluids<18:40:53.280> the<18:40:53.336> victim's<18:40:53.760> computer<18:40:53.936> with<18:40:54.296> ping 18:40:54.646 --> 18:40:54.656 align:start position:0% fluids the victim's computer with ping 18:40:54.656 --> 18:40:57.286 align:start position:0% fluids the victim's computer with ping packets<18:40:55.104> the<18:40:56.104> attack<18:40:56.216> initiates<18:40:56.872> the<18:40:57.176> attack 18:40:57.286 --> 18:40:57.296 align:start position:0% packets the attack initiates the attack 18:40:57.296 --> 18:40:59.630 align:start position:0% packets the attack initiates the attack by<18:40:57.656> sending<18:40:57.960> a<18:40:58.080> ping<18:40:58.256> request<18:40:58.680> and<18:40:59.512> then 18:40:59.630 --> 18:40:59.640 align:start position:0% by sending a ping request and then 18:40:59.640 --> 18:41:01.910 align:start position:0% by sending a ping request and then spoofs<18:41:00.120> the<18:41:00.296> destination<18:41:00.720> address<18:41:01.080> ping 18:41:01.910 --> 18:41:01.920 align:start position:0% spoofs the destination address ping 18:41:01.920 --> 18:41:03.526 align:start position:0% spoofs the destination address ping replies<18:41:02.280> are<18:41:02.512> sent<18:41:02.640> to<18:41:02.824> the<18:41:03.000> victim's 18:41:03.526 --> 18:41:03.536 align:start position:0% replies are sent to the victim's 18:41:03.536 --> 18:41:07.606 align:start position:0% replies are sent to the victim's computer<18:41:03.784> address 18:41:07.606 --> 18:41:07.616 align:start position:0% 18:41:07.616 --> 18:41:09.774 align:start position:0% since<18:41:08.280> the<18:41:08.512> Ping<18:41:08.824> request<18:41:09.120> is<18:41:09.296> addressed<18:41:09.720> to 18:41:09.774 --> 18:41:09.784 align:start position:0% since the Ping request is addressed to 18:41:09.784 --> 18:41:11.566 align:start position:0% since the Ping request is addressed to the<18:41:09.896> broadcast<18:41:10.144> address<18:41:10.560> all<18:41:10.920> computers<18:41:11.400> in 18:41:11.566 --> 18:41:11.576 align:start position:0% the broadcast address all computers in 18:41:11.576 --> 18:41:14.454 align:start position:0% the broadcast address all computers in the<18:41:11.760> network<18:41:11.872> have<18:41:12.424> to<18:41:12.600> respond<18:41:12.960> and 18:41:14.454 --> 18:41:14.464 align:start position:0% the network have to respond and 18:41:14.464 --> 18:41:17.270 align:start position:0% the network have to respond and um each<18:41:15.240> packet<18:41:15.600> is<18:41:15.832> opened<18:41:16.320> and<18:41:16.560> checked<18:41:17.104> and 18:41:17.270 --> 18:41:17.280 align:start position:0% um each packet is opened and checked and 18:41:17.280 --> 18:41:20.750 align:start position:0% um each packet is opened and checked and to<18:41:17.696> see<18:41:17.824> if<18:41:17.936> it's<18:41:18.176> the<18:41:18.424> destination 18:41:20.750 --> 18:41:20.760 align:start position:0% to see if it's the destination 18:41:20.760 --> 18:41:22.790 align:start position:0% to see if it's the destination as<18:41:21.120> a<18:41:21.240> result<18:41:21.296> the<18:41:21.600> victim<18:41:21.784> can't<18:41:22.016> receive<18:41:22.440> any 18:41:22.790 --> 18:41:22.800 align:start position:0% as a result the victim can't receive any 18:41:22.800 --> 18:41:24.286 align:start position:0% as a result the victim can't receive any genuine<18:41:23.280> traffic<18:41:23.464> because<18:41:23.824> it's<18:41:24.064> already 18:41:24.286 --> 18:41:24.296 align:start position:0% genuine traffic because it's already 18:41:24.296 --> 18:41:28.182 align:start position:0% genuine traffic because it's already flooded<18:41:24.896> with<18:41:25.080> ping<18:41:25.376> packets 18:41:28.182 --> 18:41:28.192 align:start position:0% 18:41:28.192 --> 18:41:29.926 align:start position:0% uh<18:41:28.800> technique<18:41:29.104> of<18:41:29.280> assigning<18:41:29.696> a<18:41:29.824> network 18:41:29.926 --> 18:41:29.936 align:start position:0% uh technique of assigning a network 18:41:29.936 --> 18:41:31.910 align:start position:0% uh technique of assigning a network packet<18:41:30.424> with<18:41:30.600> a<18:41:30.720> file<18:41:30.832> side<18:41:31.080> P<18:41:31.256> address<18:41:31.504> is 18:41:31.910 --> 18:41:31.920 align:start position:0% packet with a file side P address is 18:41:31.920 --> 18:41:36.350 align:start position:0% packet with a file side P address is called<18:41:32.160> spoofing 18:41:36.350 --> 18:41:36.360 align:start position:0% 18:41:36.360 --> 18:41:38.630 align:start position:0% computer<18:41:36.832> viruses<18:41:37.560> these<18:41:37.976> are<18:41:38.104> distributed 18:41:38.630 --> 18:41:38.640 align:start position:0% computer viruses these are distributed 18:41:38.640 --> 18:41:40.550 align:start position:0% computer viruses these are distributed and<18:41:38.872> spread<18:41:39.240> throughout<18:41:39.536> the<18:41:39.720> network<18:41:39.896> in<18:41:40.376> a 18:41:40.550 --> 18:41:40.560 align:start position:0% and spread throughout the network in a 18:41:40.560 --> 18:41:44.750 align:start position:0% and spread throughout the network in a number<18:41:40.800> of<18:41:40.976> ways 18:41:44.750 --> 18:41:44.760 align:start position:0% 18:41:44.760 --> 18:41:46.550 align:start position:0% the<18:41:45.296> attacker<18:41:45.720> uses<18:41:46.016> and<18:41:46.144> controls<18:41:46.440> the 18:41:46.550 --> 18:41:46.560 align:start position:0% the attacker uses and controls the 18:41:46.560 --> 18:41:48.054 align:start position:0% the attacker uses and controls the victim's<18:41:46.920> computer<18:41:47.160> to<18:41:47.576> attack<18:41:47.696> somebody 18:41:48.054 --> 18:41:48.064 align:start position:0% victim's computer to attack somebody 18:41:48.064 --> 18:41:51.822 align:start position:0% victim's computer to attack somebody else's<18:41:48.744> low<18:41:49.744> and<18:41:49.976> weak<18:41:50.400> uh<18:41:50.760> security<18:41:51.000> network 18:41:51.822 --> 18:41:51.832 align:start position:0% else's low and weak uh security network 18:41:51.832 --> 18:41:54.230 align:start position:0% else's low and weak uh security network security<18:41:52.192> and<18:41:53.104> some<18:41:53.216> device<18:41:53.464> some<18:41:54.000> devices 18:41:54.230 --> 18:41:54.240 align:start position:0% security and some device some devices 18:41:54.240 --> 18:41:56.750 align:start position:0% security and some device some devices you're<18:41:54.600> waiting<18:41:55.016> to<18:41:55.192> have<18:41:55.920> patches<18:41:56.336> applied 18:41:56.750 --> 18:41:56.760 align:start position:0% you're waiting to have patches applied 18:41:56.760 --> 18:41:59.566 align:start position:0% you're waiting to have patches applied to<18:41:56.936> or<18:41:57.176> they<18:41:57.360> haven't<18:41:57.480> rebooted<18:41:58.080> after<18:41:58.320> up<18:41:59.160> and 18:41:59.566 --> 18:41:59.576 align:start position:0% to or they haven't rebooted after up and 18:41:59.576 --> 18:42:01.310 align:start position:0% to or they haven't rebooted after up and downloading<18:42:00.176> some<18:42:00.360> updates<18:42:00.720> or<18:42:00.896> whatever<18:42:01.016> and 18:42:01.310 --> 18:42:01.320 align:start position:0% downloading some updates or whatever and 18:42:01.320 --> 18:42:03.710 align:start position:0% downloading some updates or whatever and this<18:42:01.440> is<18:42:01.560> when<18:42:01.680> they<18:42:01.800> become<18:42:02.104> vulnerable 18:42:03.710 --> 18:42:03.720 align:start position:0% this is when they become vulnerable 18:42:03.720 --> 18:42:05.502 align:start position:0% this is when they become vulnerable attacker<18:42:04.376> floods<18:42:04.744> they<18:42:04.856> target<18:42:05.040> competes 18:42:05.502 --> 18:42:05.512 align:start position:0% attacker floods they target competes 18:42:05.512 --> 18:42:06.950 align:start position:0% attacker floods they target competes with<18:42:05.640> a<18:42:05.696> huge<18:42:05.872> amount<18:42:06.120> of<18:42:06.240> data<18:42:06.536> to<18:42:06.784> a 18:42:06.950 --> 18:42:06.960 align:start position:0% with a huge amount of data to a 18:42:06.960 --> 18:42:09.774 align:start position:0% with a huge amount of data to a particular<18:42:07.256> site<18:42:07.560> or<18:42:07.976> spam<18:42:08.280> emails<18:42:08.872> using<18:42:09.600> a 18:42:09.774 --> 18:42:09.784 align:start position:0% particular site or spam emails using a 18:42:09.784 --> 18:42:11.926 align:start position:0% particular site or spam emails using a victim's<18:42:10.192> computer<18:42:10.640> so<18:42:11.640> the<18:42:11.824> name 18:42:11.926 --> 18:42:11.936 align:start position:0% victim's computer so the name 18:42:11.936 --> 18:42:14.566 align:start position:0% victim's computer so the name distributed<18:42:12.720> indicates<18:42:13.616> the<18:42:13.800> attacker<18:42:14.216> uses 18:42:14.566 --> 18:42:14.576 align:start position:0% distributed indicates the attacker uses 18:42:14.576 --> 18:42:16.734 align:start position:0% distributed indicates the attacker uses multiple<18:42:15.000> host<18:42:15.240> computers 18:42:16.734 --> 18:42:16.744 align:start position:0% multiple host computers 18:42:16.744 --> 18:42:18.886 align:start position:0% multiple host computers uh<18:42:17.400> this<18:42:17.640> is<18:42:17.760> to<18:42:18.000> throw 18:42:18.886 --> 18:42:18.896 align:start position:0% uh this is to throw 18:42:18.896 --> 18:42:21.166 align:start position:0% uh this is to throw um<18:42:19.376> others<18:42:20.040> off<18:42:20.160> the<18:42:20.336> trail<18:42:20.512> and<18:42:20.824> make<18:42:21.000> it 18:42:21.166 --> 18:42:21.176 align:start position:0% um others off the trail and make it 18:42:21.176 --> 18:42:23.326 align:start position:0% um others off the trail and make it harder<18:42:21.720> to<18:42:22.080> actually<18:42:22.320> identify<18:42:22.920> the<18:42:23.160> attack 18:42:23.326 --> 18:42:23.336 align:start position:0% harder to actually identify the attack 18:42:23.336 --> 18:42:25.606 align:start position:0% harder to actually identify the attack because<18:42:24.000> the<18:42:24.600> um<18:42:24.600> victims<18:42:25.144> are<18:42:25.504> actually 18:42:25.606 --> 18:42:25.616 align:start position:0% because the um victims are actually 18:42:25.616 --> 18:42:28.790 align:start position:0% because the um victims are actually legitimate<18:42:26.400> systems<18:42:27.240> on<18:42:27.424> the<18:42:27.600> hosts 18:42:28.790 --> 18:42:28.800 align:start position:0% legitimate systems on the hosts 18:42:28.800 --> 18:42:30.230 align:start position:0% legitimate systems on the hosts the<18:42:29.216> attacker<18:42:29.640> can<18:42:29.824> increase<18:42:29.936> the 18:42:30.230 --> 18:42:30.240 align:start position:0% the attacker can increase the 18:42:30.240 --> 18:42:31.966 align:start position:0% the attacker can increase the effectiveness<18:42:30.784> using<18:42:31.320> client<18:42:31.560> server 18:42:31.966 --> 18:42:31.976 align:start position:0% effectiveness using client server 18:42:31.976 --> 18:42:33.526 align:start position:0% effectiveness using client server technology 18:42:33.526 --> 18:42:33.536 align:start position:0% technology 18:42:33.536 --> 18:42:36.230 align:start position:0% technology in<18:42:34.144> distributed<18:42:34.616> denial<18:42:34.976> of<18:42:35.160> service 18:42:36.230 --> 18:42:36.240 align:start position:0% in distributed denial of service 18:42:36.240 --> 18:42:38.390 align:start position:0% in distributed denial of service master<18:42:36.896> program<18:42:37.256> or<18:42:37.560> software<18:42:37.920> is<18:42:38.040> installed 18:42:38.390 --> 18:42:38.400 align:start position:0% master program or software is installed 18:42:38.400 --> 18:42:41.454 align:start position:0% master program or software is installed on<18:42:38.464> one<18:42:38.696> computer<18:42:39.256> normally<18:42:40.256> they<18:42:41.040> use<18:42:41.216> a 18:42:41.454 --> 18:42:41.464 align:start position:0% on one computer normally they use a 18:42:41.464 --> 18:42:44.814 align:start position:0% on one computer normally they use a stolen<18:42:41.872> login<18:42:42.120> credentials 18:42:44.814 --> 18:42:44.824 align:start position:0% stolen login credentials 18:42:44.824 --> 18:42:47.926 align:start position:0% stolen login credentials now<18:42:45.424> it<18:42:45.656> may<18:42:46.080> not<18:42:46.192> happen<18:42:46.376> immediately<18:42:47.104> but<18:42:47.576> at 18:42:47.926 --> 18:42:47.936 align:start position:0% now it may not happen immediately but at 18:42:47.936 --> 18:42:49.686 align:start position:0% now it may not happen immediately but at some<18:42:48.176> particular<18:42:48.536> time<18:42:48.784> the<18:42:49.016> master<18:42:49.144> program 18:42:49.686 --> 18:42:49.696 align:start position:0% some particular time the master program 18:42:49.696 --> 18:42:51.774 align:start position:0% some particular time the master program communicates<18:42:50.696> with<18:42:50.872> other<18:42:51.064> agent<18:42:51.480> programs 18:42:51.774 --> 18:42:51.784 align:start position:0% communicates with other agent programs 18:42:51.784 --> 18:42:53.630 align:start position:0% communicates with other agent programs that<18:42:51.960> install<18:42:52.256> the<18:42:52.560> computers<18:42:52.976> anywhere<18:42:53.464> on 18:42:53.630 --> 18:42:53.640 align:start position:0% that install the computers anywhere on 18:42:53.640 --> 18:42:54.646 align:start position:0% that install the computers anywhere on the<18:42:53.824> internet 18:42:54.646 --> 18:42:54.656 align:start position:0% the internet 18:42:54.656 --> 18:42:56.750 align:start position:0% the internet when<18:42:55.144> the<18:42:55.320> ages<18:42:55.616> receive<18:42:55.976> their<18:42:56.160> command<18:42:56.512> they 18:42:56.750 --> 18:42:56.760 align:start position:0% when the ages receive their command they 18:42:56.760 --> 18:42:59.270 align:start position:0% when the ages receive their command they start<18:42:56.936> to<18:42:57.120> attack 18:42:59.270 --> 18:42:59.280 align:start position:0% start to attack 18:42:59.280 --> 18:43:01.494 align:start position:0% start to attack the<18:42:59.760> master<18:42:59.872> program<18:43:00.296> is<18:43:00.784> able<18:43:01.016> to<18:43:01.144> spread 18:43:01.494 --> 18:43:01.504 align:start position:0% the master program is able to spread 18:43:01.504 --> 18:43:03.230 align:start position:0% the master program is able to spread thousands<18:43:01.920> of<18:43:02.104> agent<18:43:02.464> programs<18:43:02.872> within 18:43:03.230 --> 18:43:03.240 align:start position:0% thousands of agent programs within 18:43:03.240 --> 18:43:10.246 align:start position:0% thousands of agent programs within seconds<18:43:03.480> using<18:43:04.016> client<18:43:04.320> server<18:43:04.744> technology 18:43:10.246 --> 18:43:10.256 align:start position:0% 18:43:10.256 --> 18:43:13.070 align:start position:0% so<18:43:10.800> some<18:43:11.040> characteristics<18:43:11.760> of<18:43:12.176> distributed 18:43:13.070 --> 18:43:13.080 align:start position:0% so some characteristics of distributed 18:43:13.080 --> 18:43:15.774 align:start position:0% so some characteristics of distributed denial<18:43:13.440> of<18:43:13.616> service<18:43:13.800> attacks<18:43:14.400> a<18:43:15.120> botnet 18:43:15.774 --> 18:43:15.784 align:start position:0% denial of service attacks a botnet 18:43:15.784 --> 18:43:20.814 align:start position:0% denial of service attacks a botnet traffic<18:43:16.256> spite<18:43:17.064> coordinated<18:43:18.064> attack 18:43:20.814 --> 18:43:20.824 align:start position:0% 18:43:20.824 --> 18:43:22.486 align:start position:0% so<18:43:21.296> if<18:43:21.424> you<18:43:21.536> can<18:43:21.656> see<18:43:21.784> that<18:43:21.960> there's<18:43:22.320> a 18:43:22.486 --> 18:43:22.496 align:start position:0% so if you can see that there's a 18:43:22.496 --> 18:43:24.166 align:start position:0% so if you can see that there's a attacking<18:43:22.920> machine<18:43:23.104> at<18:43:23.400> the<18:43:23.512> top<18:43:23.640> there<18:43:23.872> and 18:43:24.166 --> 18:43:24.176 align:start position:0% attacking machine at the top there and 18:43:24.176 --> 18:43:28.134 align:start position:0% attacking machine at the top there and handlers<18:43:25.144> and<18:43:25.320> compromise<18:43:25.800> systems 18:43:28.134 --> 18:43:28.144 align:start position:0% handlers and compromise systems 18:43:28.144 --> 18:43:29.750 align:start position:0% handlers and compromise systems um going<18:43:28.496> down<18:43:28.744> to<18:43:28.856> the<18:43:28.976> targeted<18:43:29.512> services 18:43:29.750 --> 18:43:29.760 align:start position:0% um going down to the targeted services 18:43:29.760 --> 18:43:32.454 align:start position:0% um going down to the targeted services or<18:43:30.424> servers<18:43:31.016> on<18:43:31.144> the<18:43:31.256> bottom<18:43:31.504> there 18:43:32.454 --> 18:43:32.464 align:start position:0% or servers on the bottom there 18:43:32.464 --> 18:43:34.790 align:start position:0% or servers on the bottom there so<18:43:32.696> botnet<18:43:33.296> refers<18:43:33.720> to<18:43:33.896> a<18:43:34.016> group<18:43:34.192> of<18:43:34.320> computers 18:43:34.790 --> 18:43:34.800 align:start position:0% so botnet refers to a group of computers 18:43:34.800 --> 18:43:37.366 align:start position:0% so botnet refers to a group of computers that<18:43:35.104> can<18:43:35.464> cooperate 18:43:37.366 --> 18:43:37.376 align:start position:0% that can cooperate 18:43:37.376 --> 18:43:41.990 align:start position:0% that can cooperate also<18:43:37.976> known<18:43:38.104> as<18:43:38.336> zombies<18:43:38.696> in<18:43:38.936> this<18:43:39.120> context 18:43:41.990 --> 18:43:42.000 align:start position:0% 18:43:42.000 --> 18:43:43.790 align:start position:0% at<18:43:42.296> the<18:43:42.360> botnet<18:43:42.720> owners<18:43:43.016> also<18:43:43.376> known<18:43:43.560> as 18:43:43.790 --> 18:43:43.800 align:start position:0% at the botnet owners also known as 18:43:43.800 --> 18:43:45.774 align:start position:0% at the botnet owners also known as herders<18:43:44.336> they<18:43:44.576> manage<18:43:44.936> computers<18:43:45.360> in<18:43:45.656> their 18:43:45.774 --> 18:43:45.784 align:start position:0% herders they manage computers in their 18:43:45.784 --> 18:43:48.822 align:start position:0% herders they manage computers in their botnet<18:43:46.320> botners<18:43:47.216> used<18:43:47.464> to<18:43:47.696> send<18:43:47.872> spam<18:43:48.296> emails 18:43:48.822 --> 18:43:48.832 align:start position:0% botnet botners used to send spam emails 18:43:48.832 --> 18:43:50.926 align:start position:0% botnet botners used to send spam emails or<18:43:49.080> to<18:43:49.256> participate<18:43:49.744> in<18:43:49.920> distributed<18:43:50.512> denial 18:43:50.926 --> 18:43:50.936 align:start position:0% or to participate in distributed denial 18:43:50.936 --> 18:43:52.366 align:start position:0% or to participate in distributed denial of<18:43:51.120> service<18:43:51.296> attack 18:43:52.366 --> 18:43:52.376 align:start position:0% of service attack 18:43:52.376 --> 18:43:54.526 align:start position:0% of service attack so<18:43:52.800> this<18:43:52.920> is<18:43:53.040> why<18:43:53.576> it<18:43:53.824> can<18:43:53.936> be<18:43:54.064> so<18:43:54.240> difficult 18:43:54.526 --> 18:43:54.536 align:start position:0% so this is why it can be so difficult 18:43:54.536 --> 18:43:57.470 align:start position:0% so this is why it can be so difficult because<18:43:54.832> all<18:43:55.080> these<18:43:55.376> legitimate<18:43:55.920> devices<18:43:56.480> at 18:43:57.470 --> 18:43:57.480 align:start position:0% because all these legitimate devices at 18:43:57.480 --> 18:43:58.846 align:start position:0% because all these legitimate devices at some<18:43:57.656> point<18:43:57.832> of<18:43:58.080> time<18:43:58.192> when<18:43:58.496> there's<18:43:58.680> a 18:43:58.846 --> 18:43:58.856 align:start position:0% some point of time when there's a 18:43:58.856 --> 18:44:01.846 align:start position:0% some point of time when there's a trigger<18:43:59.216> it's<18:43:59.512> a<18:43:59.760> like<18:44:00.240> a<18:44:00.360> timer<18:44:00.600> or<18:44:01.560> it's<18:44:01.680> time 18:44:01.846 --> 18:44:01.856 align:start position:0% trigger it's a like a timer or it's time 18:44:01.856 --> 18:44:04.182 align:start position:0% trigger it's a like a timer or it's time when<18:44:02.040> everyone's<18:44:02.400> off<18:44:02.576> work<18:44:02.832> or<18:44:03.832> on<18:44:04.080> a 18:44:04.182 --> 18:44:04.192 align:start position:0% when everyone's off work or on a 18:44:04.192 --> 18:44:06.886 align:start position:0% when everyone's off work or on a Saturday<18:44:04.616> night<18:44:05.040> on<18:44:05.640> a<18:44:05.760> bank<18:44:05.872> holiday<18:44:06.120> they'll 18:44:06.886 --> 18:44:06.896 align:start position:0% Saturday night on a bank holiday they'll 18:44:06.896 --> 18:44:09.590 align:start position:0% Saturday night on a bank holiday they'll start<18:44:07.080> their<18:44:07.320> attack 18:44:09.590 --> 18:44:09.600 align:start position:0% 18:44:09.600 --> 18:44:11.686 align:start position:0% traffic<18:44:10.192> spy<18:44:10.744> overloads<18:44:11.216> the<18:44:11.400> victim's 18:44:11.686 --> 18:44:11.696 align:start position:0% traffic spy overloads the victim's 18:44:11.696 --> 18:44:13.790 align:start position:0% traffic spy overloads the victim's Network<18:44:11.936> or<18:44:12.240> server<18:44:12.600> in<18:44:13.016> order<18:44:13.144> to 18:44:13.790 --> 18:44:13.800 align:start position:0% Network or server in order to 18:44:13.800 --> 18:44:15.822 align:start position:0% Network or server in order to its<18:44:14.040> services<18:44:14.160> and<18:44:14.640> resources 18:44:15.822 --> 18:44:15.832 align:start position:0% its services and resources 18:44:15.832 --> 18:44:18.110 align:start position:0% its services and resources as<18:44:16.256> a<18:44:16.440> result<18:44:16.496> the<18:44:16.856> legitimate<18:44:17.336> user<18:44:17.696> will<18:44:17.872> not 18:44:18.110 --> 18:44:18.120 align:start position:0% as a result the legitimate user will not 18:44:18.120 --> 18:44:21.470 align:start position:0% as a result the legitimate user will not be<18:44:18.360> able<18:44:18.720> to<18:44:18.896> access<18:44:19.080> the<18:44:19.504> service 18:44:21.470 --> 18:44:21.480 align:start position:0% be able to access the service 18:44:21.480 --> 18:44:23.630 align:start position:0% be able to access the service they<18:44:21.896> use<18:44:22.080> when<18:44:22.320> people<18:44:22.560> are<18:44:22.856> coordinated<18:44:23.400> to 18:44:23.630 --> 18:44:23.640 align:start position:0% they use when people are coordinated to 18:44:23.640 --> 18:44:25.606 align:start position:0% they use when people are coordinated to carry<18:44:23.936> out<18:44:24.000> the<18:44:24.176> attack<18:44:24.360> on<18:44:24.720> a<18:44:24.832> site<18:44:25.016> or<18:44:25.376> site 18:44:25.606 --> 18:44:25.616 align:start position:0% carry out the attack on a site or site 18:44:25.616 --> 18:44:27.470 align:start position:0% carry out the attack on a site or site at<18:44:25.920> the<18:44:26.104> same<18:44:26.216> time 18:44:27.470 --> 18:44:27.480 align:start position:0% at the same time 18:44:27.480 --> 18:44:29.390 align:start position:0% at the same time when<18:44:27.832> many<18:44:28.016> people<18:44:28.256> attack<18:44:28.496> the<18:44:28.744> server<18:44:29.104> the 18:44:29.390 --> 18:44:29.400 align:start position:0% when many people attack the server the 18:44:29.400 --> 18:44:32.270 align:start position:0% when many people attack the server the web<18:44:29.576> Server<18:44:29.936> slows<18:44:30.360> down<18:44:30.536> or<18:44:30.784> gets<18:44:31.080> overloaded 18:44:32.270 --> 18:44:32.280 align:start position:0% web Server slows down or gets overloaded 18:44:32.280 --> 18:44:34.182 align:start position:0% web Server slows down or gets overloaded it's<18:44:32.696> difficult<18:44:33.000> to<18:44:33.240> differentiate<18:44:33.896> such 18:44:34.182 --> 18:44:34.192 align:start position:0% it's difficult to differentiate such 18:44:34.192 --> 18:44:37.606 align:start position:0% it's difficult to differentiate such attacks<18:44:34.680> from<18:44:34.920> the<18:44:35.160> normal<18:44:35.336> traffic 18:44:37.606 --> 18:44:37.616 align:start position:0% attacks from the normal traffic 18:44:37.616 --> 18:44:39.646 align:start position:0% attacks from the normal traffic where<18:44:38.400> many<18:44:38.640> people<18:44:38.824> do<18:44:39.064> this<18:44:39.176> at<18:44:39.296> a<18:44:39.424> similar 18:44:39.646 --> 18:44:39.656 align:start position:0% where many people do this at a similar 18:44:39.656 --> 18:44:41.926 align:start position:0% where many people do this at a similar time<18:44:39.832> the<18:44:40.080> web<18:44:40.192> Server<18:44:40.560> slows<18:44:40.976> down<18:44:41.160> or<18:44:41.576> gets 18:44:41.926 --> 18:44:41.936 align:start position:0% time the web Server slows down or gets 18:44:41.936 --> 18:44:43.430 align:start position:0% time the web Server slows down or gets overloaded 18:44:43.430 --> 18:44:43.440 align:start position:0% overloaded 18:44:43.440 --> 18:44:46.910 align:start position:0% overloaded uh<18:44:44.160> it's<18:44:44.400> difficult<18:44:44.760> to<18:44:45.176> identify<18:44:45.784> this<18:44:46.744> a 18:44:46.910 --> 18:44:46.920 align:start position:0% uh it's difficult to identify this a 18:44:46.920 --> 18:44:48.710 align:start position:0% uh it's difficult to identify this a type<18:44:47.104> of<18:44:47.216> attack<18:44:47.400> from<18:44:47.696> normal<18:44:47.936> traffic<18:44:48.296> that 18:44:48.710 --> 18:44:48.720 align:start position:0% type of attack from normal traffic that 18:44:48.720 --> 18:44:50.030 align:start position:0% type of attack from normal traffic that can<18:44:48.832> happen<18:44:48.960> and<18:44:49.192> obviously<18:44:49.616> you<18:44:49.744> do<18:44:49.856> get 18:44:50.030 --> 18:44:50.040 align:start position:0% can happen and obviously you do get 18:44:50.040 --> 18:44:53.030 align:start position:0% can happen and obviously you do get spikes<18:44:50.640> on<18:44:51.424> networks<18:44:52.080> and<18:44:52.376> then<18:44:52.560> if<18:44:52.856> there's 18:44:53.030 --> 18:44:53.040 align:start position:0% spikes on networks and then if there's 18:44:53.040 --> 18:44:54.822 align:start position:0% spikes on networks and then if there's updates<18:44:53.400> been<18:44:53.640> applied 18:44:54.822 --> 18:44:54.832 align:start position:0% updates been applied 18:44:54.832 --> 18:44:58.070 align:start position:0% updates been applied to<18:44:55.376> the<18:44:55.560> servers<18:44:56.160> again<18:44:56.872> it<18:44:57.296> can 18:44:58.070 --> 18:44:58.080 align:start position:0% to the servers again it can 18:44:58.080 --> 18:45:02.686 align:start position:0% to the servers again it can um<18:44:58.144> appear<18:44:58.800> to<18:44:59.336> be<18:44:59.464> slow<18:44:59.824> legitimately<18:45:00.656> slow 18:45:02.686 --> 18:45:02.696 align:start position:0% um appear to be slow legitimately slow 18:45:02.696 --> 18:45:04.734 align:start position:0% um appear to be slow legitimately slow difference<18:45:03.240> between<18:45:03.480> denial<18:45:04.016> of<18:45:04.192> service<18:45:04.376> and 18:45:04.734 --> 18:45:04.744 align:start position:0% difference between denial of service and 18:45:04.744 --> 18:45:06.166 align:start position:0% difference between denial of service and distributed 18:45:06.166 --> 18:45:06.176 align:start position:0% distributed 18:45:06.176 --> 18:45:08.030 align:start position:0% distributed and<18:45:06.784> using<18:45:07.144> a<18:45:07.256> single<18:45:07.440> internet<18:45:07.552> connection 18:45:08.030 --> 18:45:08.040 align:start position:0% and using a single internet connection 18:45:08.040 --> 18:45:10.486 align:start position:0% and using a single internet connection an<18:45:08.400> attacker<18:45:08.760> can<18:45:08.936> harm<18:45:09.176> a<18:45:09.360> network<18:45:09.536> in<18:45:10.080> a<18:45:10.192> Dos 18:45:10.486 --> 18:45:10.496 align:start position:0% an attacker can harm a network in a Dos 18:45:10.496 --> 18:45:11.566 align:start position:0% an attacker can harm a network in a Dos attack 18:45:11.566 --> 18:45:11.576 align:start position:0% attack 18:45:11.576 --> 18:45:13.734 align:start position:0% attack launching<18:45:12.480> multiple<18:45:12.832> connected<18:45:13.320> devices 18:45:13.734 --> 18:45:13.744 align:start position:0% launching multiple connected devices 18:45:13.744 --> 18:45:16.366 align:start position:0% launching multiple connected devices that<18:45:14.280> are<18:45:14.512> distributed<18:45:15.056> is<18:45:15.480> a<18:45:15.720> distributed 18:45:16.366 --> 18:45:16.376 align:start position:0% that are distributed is a distributed 18:45:16.376 --> 18:45:19.494 align:start position:0% that are distributed is a distributed denial<18:45:16.920> of<18:45:17.040> service<18:45:17.336> attack 18:45:19.494 --> 18:45:19.504 align:start position:0% denial of service attack 18:45:19.504 --> 18:45:22.910 align:start position:0% denial of service attack uh<18:45:20.336> the<18:45:20.760> distributed<18:45:21.424> another<18:45:22.016> service<18:45:22.440> also 18:45:22.910 --> 18:45:22.920 align:start position:0% uh the distributed another service also 18:45:22.920 --> 18:45:24.590 align:start position:0% uh the distributed another service also differs<18:45:23.336> in<18:45:23.640> the<18:45:24.000> attacks<18:45:24.360> that<18:45:24.480> perform 18:45:24.590 --> 18:45:24.600 align:start position:0% differs in the attacks that perform 18:45:24.600 --> 18:45:27.646 align:start position:0% differs in the attacks that perform using<18:45:25.080> botnets 18:45:27.646 --> 18:45:27.656 align:start position:0% 18:45:27.656 --> 18:45:30.350 align:start position:0% um<18:45:27.720> including<18:45:28.256> mobile<18:45:28.552> phones<18:45:29.104> routers<18:45:29.576> PCS 18:45:30.350 --> 18:45:30.360 align:start position:0% um including mobile phones routers PCS 18:45:30.360 --> 18:45:31.966 align:start position:0% um including mobile phones routers PCS Etc 18:45:31.966 --> 18:45:31.976 align:start position:0% Etc 18:45:31.976 --> 18:45:34.182 align:start position:0% Etc Denali<18:45:32.760> service<18:45:32.936> attacks<18:45:33.424> can<18:45:33.536> harm<18:45:33.784> a<18:45:33.960> single 18:45:34.182 --> 18:45:34.192 align:start position:0% Denali service attacks can harm a single 18:45:34.192 --> 18:45:36.286 align:start position:0% Denali service attacks can harm a single machine<18:45:34.376> or<18:45:34.976> they<18:45:35.400> can<18:45:35.512> attack<18:45:35.696> an<18:45:36.000> entire 18:45:36.286 --> 18:45:36.296 align:start position:0% machine or they can attack an entire 18:45:36.296 --> 18:45:38.630 align:start position:0% machine or they can attack an entire network 18:45:38.630 --> 18:45:38.640 align:start position:0% network 18:45:38.640 --> 18:45:41.390 align:start position:0% network moving<18:45:39.536> on<18:45:39.656> to<18:45:39.832> the<18:45:40.016> reflective<18:45:40.744> Amplified 18:45:41.390 --> 18:45:41.400 align:start position:0% moving on to the reflective Amplified 18:45:41.400 --> 18:45:43.734 align:start position:0% moving on to the reflective Amplified denial<18:45:41.936> of<18:45:42.120> service 18:45:43.734 --> 18:45:43.744 align:start position:0% denial of service 18:45:43.744 --> 18:45:45.822 align:start position:0% denial of service the<18:45:44.216> reflective<18:45:44.640> user<18:45:45.000> third-party<18:45:45.536> machines 18:45:45.822 --> 18:45:45.832 align:start position:0% the reflective user third-party machines 18:45:45.832 --> 18:45:48.414 align:start position:0% the reflective user third-party machines to<18:45:46.192> attack<18:45:46.376> a<18:45:46.856> targeted<18:45:47.336> computer<18:45:47.640> so 18:45:48.414 --> 18:45:48.424 align:start position:0% to attack a targeted computer so 18:45:48.424 --> 18:45:50.566 align:start position:0% to attack a targeted computer so basically<18:45:48.720> the<18:45:49.080> is<18:45:49.320> one<18:45:49.616> way<18:45:49.856> for<18:45:50.400> the 18:45:50.566 --> 18:45:50.576 align:start position:0% basically the is one way for the 18:45:50.576 --> 18:45:53.926 align:start position:0% basically the is one way for the attacker<18:45:51.000> to<18:45:51.176> mask<18:45:51.424> their<18:45:51.832> identity 18:45:53.926 --> 18:45:53.936 align:start position:0% attacker to mask their identity 18:45:53.936 --> 18:45:56.150 align:start position:0% attacker to mask their identity reflective<18:45:54.832> denial<18:45:55.320> service<18:45:55.552> attacks<18:45:56.040> use 18:45:56.150 --> 18:45:56.160 align:start position:0% reflective denial service attacks use 18:45:56.160 --> 18:45:58.486 align:start position:0% reflective denial service attacks use third-party<18:45:56.824> servers<18:45:57.240> for<18:45:57.536> example<18:45:57.832> DNS 18:45:58.486 --> 18:45:58.496 align:start position:0% third-party servers for example DNS 18:45:58.496 --> 18:46:01.790 align:start position:0% third-party servers for example DNS servers<18:45:58.976> to<18:45:59.576> attack<18:45:59.824> a<18:46:00.120> targeted<18:46:00.536> computer 18:46:01.790 --> 18:46:01.800 align:start position:0% servers to attack a targeted computer 18:46:01.800 --> 18:46:03.350 align:start position:0% servers to attack a targeted computer the<18:46:02.160> attacker<18:46:02.464> sends<18:46:02.760> a<18:46:02.824> requested<18:46:03.176> the 18:46:03.350 --> 18:46:03.360 align:start position:0% the attacker sends a requested the 18:46:03.360 --> 18:46:05.566 align:start position:0% the attacker sends a requested the reflector<18:46:03.720> server<18:46:04.256> or<18:46:04.496> servers<18:46:04.976> with<18:46:05.104> the<18:46:05.280> IP 18:46:05.566 --> 18:46:05.576 align:start position:0% reflector server or servers with the IP 18:46:05.576 --> 18:46:07.070 align:start position:0% reflector server or servers with the IP address<18:46:05.760> of<18:46:06.000> the<18:46:06.176> target 18:46:07.070 --> 18:46:07.080 align:start position:0% address of the target 18:46:07.080 --> 18:46:09.046 align:start position:0% address of the target and<18:46:07.376> what<18:46:07.552> it<18:46:07.680> does<18:46:07.856> is<18:46:07.976> overpowers<18:46:08.640> the 18:46:09.046 --> 18:46:09.056 align:start position:0% and what it does is overpowers the 18:46:09.056 --> 18:46:12.886 align:start position:0% and what it does is overpowers the target<18:46:09.296> using<18:46:10.080> response<18:46:10.976> packets 18:46:12.886 --> 18:46:12.896 align:start position:0% target using response packets 18:46:12.896 --> 18:46:19.134 align:start position:0% target using response packets an<18:46:13.320> example<18:46:13.680> is<18:46:13.920> a<18:46:14.160> DNS<18:46:14.576> response 18:46:19.134 --> 18:46:19.144 align:start position:0% 18:46:19.144 --> 18:46:20.862 align:start position:0% type<18:46:19.552> of<18:46:19.744> reflective<18:46:20.216> denial<18:46:20.576> of<18:46:20.760> service 18:46:20.862 --> 18:46:20.872 align:start position:0% type of reflective denial of service 18:46:20.872 --> 18:46:24.166 align:start position:0% type of reflective denial of service attacks<18:46:21.424> DNS<18:46:21.960> amplification<18:46:22.872> Network<18:46:23.872> time 18:46:24.166 --> 18:46:24.176 align:start position:0% attacks DNS amplification Network time 18:46:24.176 --> 18:46:27.110 align:start position:0% attacks DNS amplification Network time protocol<18:46:24.784> smurfing 18:46:27.110 --> 18:46:27.120 align:start position:0% protocol smurfing 18:46:27.120 --> 18:46:30.774 align:start position:0% protocol smurfing mentioned<18:46:27.832> DNS<18:46:28.256> amplification<18:46:29.296> the<18:46:30.296> attack 18:46:30.774 --> 18:46:30.784 align:start position:0% mentioned DNS amplification the attack 18:46:30.784 --> 18:46:33.590 align:start position:0% mentioned DNS amplification the attack explicit<18:46:31.504> DNS<18:46:31.976> server<18:46:32.336> to<18:46:32.512> make 18:46:33.590 --> 18:46:33.600 align:start position:0% explicit DNS server to make 18:46:33.600 --> 18:46:35.326 align:start position:0% explicit DNS server to make um<18:46:33.656> change<18:46:34.376> small<18:46:34.744> requests<18:46:35.160> into 18:46:35.326 --> 18:46:35.336 align:start position:0% um change small requests into 18:46:35.336 --> 18:46:38.862 align:start position:0% um change small requests into considerably<18:46:36.440> larger<18:46:37.440> payloads<18:46:38.104> this<18:46:38.576> can<18:46:38.760> be 18:46:38.862 --> 18:46:38.872 align:start position:0% considerably larger payloads this can be 18:46:38.872 --> 18:46:43.134 align:start position:0% considerably larger payloads this can be used<18:46:39.056> to<18:46:39.296> overthrow<18:46:39.720> the<18:46:40.080> victim's<18:46:40.552> servers 18:46:43.134 --> 18:46:43.144 align:start position:0% used to overthrow the victim's servers 18:46:43.144 --> 18:46:46.006 align:start position:0% used to overthrow the victim's servers Network<18:46:43.616> time<18:46:44.104> the<18:46:44.936> attacker<18:46:45.296> exploits<18:46:45.832> a 18:46:46.006 --> 18:46:46.016 align:start position:0% Network time the attacker exploits a 18:46:46.016 --> 18:46:47.926 align:start position:0% Network time the attacker exploits a widely<18:46:46.376> accessible<18:46:46.744> Network<18:46:46.976> time<18:46:47.400> servers 18:46:47.926 --> 18:46:47.936 align:start position:0% widely accessible Network time servers 18:46:47.936 --> 18:46:50.630 align:start position:0% widely accessible Network time servers and<18:46:48.896> destroys<18:46:49.320> the<18:46:49.504> targeted<18:46:49.856> computer<18:46:50.040> with 18:46:50.630 --> 18:46:50.640 align:start position:0% and destroys the targeted computer with 18:46:50.640 --> 18:46:54.886 align:start position:0% and destroys the targeted computer with UDP<18:46:51.000> traffic<18:46:51.296> which<18:46:51.960> is<18:46:52.080> what<18:46:52.256> ntp<18:46:52.744> uses 18:46:54.886 --> 18:46:54.896 align:start position:0% UDP traffic which is what ntp uses 18:46:54.896 --> 18:46:57.414 align:start position:0% UDP traffic which is what ntp uses uh<18:46:55.680> can<18:46:55.976> they're<18:46:56.280> not<18:46:56.512> all<18:46:56.640> intentional<18:46:57.120> they 18:46:57.414 --> 18:46:57.424 align:start position:0% uh can they're not all intentional they 18:46:57.424 --> 18:46:59.150 align:start position:0% uh can they're not all intentional they can<18:46:57.536> be<18:46:57.656> unintentional<18:46:58.320> this<18:46:58.680> is<18:46:58.800> when<18:46:58.976> a 18:46:59.150 --> 18:46:59.160 align:start position:0% can be unintentional this is when a 18:46:59.160 --> 18:47:01.734 align:start position:0% can be unintentional this is when a server<18:46:59.400> crashes<18:46:59.824> for<18:47:00.000> example<18:47:00.296> can't<18:47:01.192> provide 18:47:01.734 --> 18:47:01.744 align:start position:0% server crashes for example can't provide 18:47:01.744 --> 18:47:03.710 align:start position:0% server crashes for example can't provide services<18:47:02.400> because<18:47:02.936> of<18:47:03.120> traffic<18:47:03.360> from 18:47:03.710 --> 18:47:03.720 align:start position:0% services because of traffic from 18:47:03.720 --> 18:47:05.454 align:start position:0% services because of traffic from legitimate<18:47:04.320> users 18:47:05.454 --> 18:47:05.464 align:start position:0% legitimate users 18:47:05.464 --> 18:47:07.734 align:start position:0% legitimate users uh<18:47:06.056> again<18:47:06.240> have<18:47:06.536> a<18:47:06.720> look<18:47:06.784> there's<18:47:07.256> a<18:47:07.552> whole 18:47:07.734 --> 18:47:07.744 align:start position:0% uh again have a look there's a whole 18:47:07.744 --> 18:47:09.886 align:start position:0% uh again have a look there's a whole bunch<18:47:07.976> of<18:47:08.216> quite 18:47:09.886 --> 18:47:09.896 align:start position:0% bunch of quite 18:47:09.896 --> 18:47:11.630 align:start position:0% bunch of quite um<18:47:10.016> well<18:47:10.320> reported<18:47:10.920> and<18:47:11.104> embarrassing 18:47:11.630 --> 18:47:11.640 align:start position:0% um well reported and embarrassing 18:47:11.640 --> 18:47:13.606 align:start position:0% um well reported and embarrassing examples<18:47:12.056> for<18:47:12.360> government<18:47:12.656> and<18:47:13.080> private 18:47:13.606 --> 18:47:13.616 align:start position:0% examples for government and private 18:47:13.616 --> 18:47:15.886 align:start position:0% examples for government and private companies<18:47:14.104> large<18:47:14.512> companies 18:47:15.886 --> 18:47:15.896 align:start position:0% companies large companies 18:47:15.896 --> 18:47:18.710 align:start position:0% companies large companies so<18:47:16.320> in<18:47:16.440> a<18:47:16.616> popular<18:47:16.744> website<18:47:17.216> hosted<18:47:17.696> news<18:47:18.000> on<18:47:18.424> a 18:47:18.710 --> 18:47:18.720 align:start position:0% so in a popular website hosted news on a 18:47:18.720 --> 18:47:20.750 align:start position:0% so in a popular website hosted news on a less<18:47:19.080> equipped<18:47:19.552> secondary<18:47:19.976> site<18:47:20.216> the<18:47:20.464> server 18:47:20.750 --> 18:47:20.760 align:start position:0% less equipped secondary site the server 18:47:20.760 --> 18:47:22.846 align:start position:0% less equipped secondary site the server on<18:47:21.000> that<18:47:21.240> side<18:47:21.424> won't<18:47:22.080> be<18:47:22.256> able<18:47:22.320> to<18:47:22.440> handle<18:47:22.680> the 18:47:22.846 --> 18:47:22.856 align:start position:0% on that side won't be able to handle the 18:47:22.856 --> 18:47:24.230 align:start position:0% on that side won't be able to handle the traffic<18:47:23.040> especially<18:47:23.640> if<18:47:23.760> there's<18:47:23.936> a<18:47:24.120> big 18:47:24.230 --> 18:47:24.240 align:start position:0% traffic especially if there's a big 18:47:24.240 --> 18:47:28.006 align:start position:0% traffic especially if there's a big breaking<18:47:24.656> news<18:47:24.832> story<18:47:25.256> going<18:47:25.616> on 18:47:28.006 --> 18:47:28.016 align:start position:0% 18:47:28.016 --> 18:47:29.630 align:start position:0% a<18:47:28.376> person<18:47:28.552> physically<18:47:29.040> attacks<18:47:29.464> the 18:47:29.630 --> 18:47:29.640 align:start position:0% a person physically attacks the 18:47:29.640 --> 18:47:31.366 align:start position:0% a person physically attacks the infrastructure<18:47:30.176> of<18:47:30.360> an<18:47:30.536> organization<18:47:31.080> when 18:47:31.366 --> 18:47:31.376 align:start position:0% infrastructure of an organization when 18:47:31.376 --> 18:47:33.350 align:start position:0% infrastructure of an organization when it's<18:47:31.552> a<18:47:31.744> physical<18:47:31.920> attack 18:47:33.350 --> 18:47:33.360 align:start position:0% it's a physical attack 18:47:33.360 --> 18:47:36.046 align:start position:0% it's a physical attack example<18:47:34.144> is<18:47:34.376> they<18:47:34.680> snip<18:47:35.104> or<18:47:35.216> destroy<18:47:35.640> a<18:47:35.760> fiber 18:47:36.046 --> 18:47:36.056 align:start position:0% example is they snip or destroy a fiber 18:47:36.056 --> 18:47:37.606 align:start position:0% example is they snip or destroy a fiber optic<18:47:36.360> cable 18:47:37.606 --> 18:47:37.616 align:start position:0% optic cable 18:47:37.616 --> 18:47:39.774 align:start position:0% optic cable again<18:47:38.104> these<18:47:38.576> I<18:47:38.760> suppose<18:47:38.936> these<18:47:39.296> could<18:47:39.424> be<18:47:39.784> um 18:47:39.774 --> 18:47:39.784 align:start position:0% again these I suppose these could be um 18:47:39.784 --> 18:47:42.710 align:start position:0% again these I suppose these could be um malicious<18:47:40.320> or<18:47:40.552> accidental<18:47:41.280> or<18:47:41.512> known<18:47:41.760> quite<18:47:42.600> a 18:47:42.710 --> 18:47:42.720 align:start position:0% malicious or accidental or known quite a 18:47:42.720 --> 18:47:44.926 align:start position:0% malicious or accidental or known quite a few<18:47:42.832> cases<18:47:43.680> of<18:47:43.856> work<18:47:44.040> people<18:47:44.336> cutting<18:47:44.760> through 18:47:44.926 --> 18:47:44.936 align:start position:0% few cases of work people cutting through 18:47:44.936 --> 18:47:48.286 align:start position:0% few cases of work people cutting through cables<18:47:45.424> by<18:47:45.600> accident 18:47:48.286 --> 18:47:48.296 align:start position:0% 18:47:48.296 --> 18:47:49.846 align:start position:0% if<18:47:48.720> the<18:47:48.832> attack<18:47:48.960> is<18:47:49.144> able<18:47:49.376> to<18:47:49.440> access<18:47:49.552> the 18:47:49.846 --> 18:47:49.856 align:start position:0% if the attack is able to access the 18:47:49.856 --> 18:47:51.470 align:start position:0% if the attack is able to access the compute<18:47:50.280> system 18:47:51.470 --> 18:47:51.480 align:start position:0% compute system 18:47:51.480 --> 18:47:53.326 align:start position:0% compute system then<18:47:51.832> they<18:47:52.016> can<18:47:52.144> obtain<18:47:52.440> information<18:47:52.680> on<18:47:53.216> the 18:47:53.326 --> 18:47:53.336 align:start position:0% then they can obtain information on the 18:47:53.336 --> 18:47:55.070 align:start position:0% then they can obtain information on the computers<18:47:53.640> obviously 18:47:55.070 --> 18:47:55.080 align:start position:0% computers obviously 18:47:55.080 --> 18:47:59.566 align:start position:0% computers obviously there's<18:47:55.680> no<18:47:56.104> set<18:47:57.056> way<18:47:57.536> to<18:47:58.256> rescue<18:47:59.160> computers 18:47:59.566 --> 18:47:59.576 align:start position:0% there's no set way to rescue computers 18:47:59.576 --> 18:48:02.094 align:start position:0% there's no set way to rescue computers or<18:47:59.824> a<18:47:59.936> network<18:48:00.056> from<18:48:00.600> these<18:48:01.320> type<18:48:01.440> of<18:48:01.552> attacks 18:48:02.094 --> 18:48:02.104 align:start position:0% or a network from these type of attacks 18:48:02.104 --> 18:48:05.270 align:start position:0% or a network from these type of attacks you<18:48:03.000> can<18:48:03.176> put<18:48:03.720> into<18:48:03.896> place<18:48:04.144> certain<18:48:04.440> steps<18:48:04.920> to 18:48:05.270 --> 18:48:05.280 align:start position:0% you can put into place certain steps to 18:48:05.280 --> 18:48:07.310 align:start position:0% you can put into place certain steps to reduce<18:48:05.936> the<18:48:06.296> likelihood 18:48:07.310 --> 18:48:07.320 align:start position:0% reduce the likelihood 18:48:07.320 --> 18:48:10.606 align:start position:0% reduce the likelihood install<18:48:07.856> to<18:48:08.280> maintain<18:48:08.576> an<18:48:08.872> antivirus<18:48:09.720> on<18:48:10.320> your 18:48:10.606 --> 18:48:10.616 align:start position:0% install to maintain an antivirus on your 18:48:10.616 --> 18:48:12.950 align:start position:0% install to maintain an antivirus on your end<18:48:11.040> devices<18:48:11.400> you<18:48:11.872> can<18:48:11.936> also<18:48:12.176> have<18:48:12.296> antivirus 18:48:12.950 --> 18:48:12.960 align:start position:0% end devices you can also have antivirus 18:48:12.960 --> 18:48:13.846 align:start position:0% end devices you can also have antivirus on<18:48:13.144> your 18:48:13.846 --> 18:48:13.856 align:start position:0% on your 18:48:13.856 --> 18:48:17.206 align:start position:0% on your mobile<18:48:14.696> phones<18:48:15.616> firewalls<18:48:16.616> and<18:48:16.744> computers 18:48:17.206 --> 18:48:17.216 align:start position:0% mobile phones firewalls and computers 18:48:17.216 --> 18:48:19.006 align:start position:0% mobile phones firewalls and computers and<18:48:17.824> configure<18:48:18.176> them<18:48:18.360> to<18:48:18.536> control<18:48:18.720> the 18:48:19.006 --> 18:48:19.016 align:start position:0% and configure them to control the 18:48:19.016 --> 18:48:22.430 align:start position:0% and configure them to control the incoming<18:48:19.376> an<18:48:19.552> outgoing<18:48:20.040> traffic 18:48:22.430 --> 18:48:22.440 align:start position:0% 18:48:22.440 --> 18:48:24.886 align:start position:0% protect<18:48:23.160> emails<18:48:23.576> from<18:48:23.824> spam<18:48:24.296> they're<18:48:24.656> just 18:48:24.886 --> 18:48:24.896 align:start position:0% protect emails from spam they're just 18:48:24.896 --> 18:48:27.886 align:start position:0% protect emails from spam they're just the<18:48:25.144> latest<18:48:25.376> uh<18:48:25.920> hacking<18:48:26.280> on<18:48:26.464> the<18:48:26.896> Democratic 18:48:27.886 --> 18:48:27.896 align:start position:0% the latest uh hacking on the Democratic 18:48:27.896 --> 18:48:30.110 align:start position:0% the latest uh hacking on the Democratic National<18:48:28.144> Party<18:48:28.552> actually<18:48:28.976> where<18:48:29.824> a<18:48:30.056> guy 18:48:30.110 --> 18:48:30.120 align:start position:0% National Party actually where a guy 18:48:30.120 --> 18:48:33.046 align:start position:0% National Party actually where a guy received<18:48:30.656> a<18:48:30.896> link<18:48:31.440> telling<18:48:32.280> him<18:48:32.464> to<18:48:32.640> reset<18:48:32.936> his 18:48:33.046 --> 18:48:33.056 align:start position:0% received a link telling him to reset his 18:48:33.056 --> 18:48:35.030 align:start position:0% received a link telling him to reset his password<18:48:33.360> and<18:48:34.192> that<18:48:34.376> went<18:48:34.496> off<18:48:34.616> to<18:48:34.856> some 18:48:35.030 --> 18:48:35.040 align:start position:0% password and that went off to some 18:48:35.040 --> 18:48:37.734 align:start position:0% password and that went off to some Russian<18:48:35.464> site<18:48:35.824> allegedly<18:48:36.480> somewhere<18:48:36.960> who 18:48:37.734 --> 18:48:37.744 align:start position:0% Russian site allegedly somewhere who 18:48:37.744 --> 18:48:41.094 align:start position:0% Russian site allegedly somewhere who then<18:48:37.976> got<18:48:38.696> into<18:48:38.872> his<18:48:39.176> system<18:48:39.360> and<18:48:39.896> read<18:48:40.744> all<18:48:40.976> of 18:48:41.094 --> 18:48:41.104 align:start position:0% then got into his system and read all of 18:48:41.104 --> 18:48:42.822 align:start position:0% then got into his system and read all of his<18:48:41.216> emails<18:48:41.640> and<18:48:41.824> all<18:48:42.000> the<18:48:42.120> other<18:48:42.240> emails<18:48:42.656> for 18:48:42.822 --> 18:48:42.832 align:start position:0% his emails and all the other emails for 18:48:42.832 --> 18:48:45.774 align:start position:0% his emails and all the other emails for all<18:48:43.016> of<18:48:43.192> the<18:48:43.376> people<18:48:43.976> on<18:48:44.280> the<18:48:44.400> site 18:48:45.774 --> 18:48:45.784 align:start position:0% all of the people on the site 18:48:45.784 --> 18:48:47.926 align:start position:0% all of the people on the site and<18:48:46.496> it<18:48:46.680> will<18:48:46.856> manage<18:48:47.040> unwanted<18:48:47.576> traffic<18:48:47.696> and 18:48:47.926 --> 18:48:47.936 align:start position:0% and it will manage unwanted traffic and 18:48:47.936 --> 18:48:50.862 align:start position:0% and it will manage unwanted traffic and send<18:48:48.056> alerts<18:48:48.480> for<18:48:48.600> spam<18:48:48.896> email<18:48:49.080> messages 18:48:50.862 --> 18:48:50.872 align:start position:0% send alerts for spam email messages 18:48:50.872 --> 18:48:53.814 align:start position:0% send alerts for spam email messages you<18:48:51.424> can<18:48:51.536> install<18:48:51.800> a<18:48:52.800> intrusion<18:48:53.400> detection 18:48:53.814 --> 18:48:53.824 align:start position:0% you can install a intrusion detection 18:48:53.824 --> 18:48:57.526 align:start position:0% you can install a intrusion detection system<18:48:54.240> an<18:48:54.536> IDs<18:48:55.080> that<18:48:56.040> will<18:48:56.576> protect<18:48:57.000> systems 18:48:57.526 --> 18:48:57.536 align:start position:0% system an IDs that will protect systems 18:48:57.536 --> 18:49:00.350 align:start position:0% system an IDs that will protect systems from<18:48:57.896> the<18:48:58.800> distributed<18:48:59.576> denial<18:49:00.000> of<18:49:00.176> service 18:49:00.350 --> 18:49:00.360 align:start position:0% from the distributed denial of service 18:49:00.360 --> 18:49:03.166 align:start position:0% from the distributed denial of service attacks 18:49:03.166 --> 18:49:03.176 align:start position:0% 18:49:03.176 --> 18:49:05.630 align:start position:0% the<18:49:03.960> RDS<18:49:04.320> uses<18:49:04.680> collection<18:49:05.040> verification 18:49:05.630 --> 18:49:05.640 align:start position:0% the RDS uses collection verification 18:49:05.640 --> 18:49:07.134 align:start position:0% the RDS uses collection verification methods 18:49:07.134 --> 18:49:07.144 align:start position:0% methods 18:49:07.144 --> 18:49:09.230 align:start position:0% methods and<18:49:07.504> speak<18:49:07.744> to<18:49:07.920> whatever<18:49:08.216> your<18:49:08.824> network 18:49:09.230 --> 18:49:09.240 align:start position:0% and speak to whatever your network 18:49:09.240 --> 18:49:12.350 align:start position:0% and speak to whatever your network equipment<18:49:09.960> vendor<18:49:10.440> is<18:49:10.552> for<18:49:10.800> more<18:49:11.040> information 18:49:12.350 --> 18:49:12.360 align:start position:0% equipment vendor is for more information 18:49:12.360 --> 18:49:14.686 align:start position:0% equipment vendor is for more information you<18:49:12.832> can<18:49:12.960> disable<18:49:13.440> and<18:49:13.680> use<18:49:13.856> networks<18:49:14.512> or 18:49:14.686 --> 18:49:14.696 align:start position:0% you can disable and use networks or 18:49:14.696 --> 18:49:17.414 align:start position:0% you can disable and use networks or segments<18:49:15.296> or<18:49:15.536> devices<18:49:15.896> or<18:49:16.320> ports<18:49:16.744> on<18:49:16.856> switches 18:49:17.414 --> 18:49:17.424 align:start position:0% segments or devices or ports on switches 18:49:17.424 --> 18:49:21.526 align:start position:0% segments or devices or ports on switches regular<18:49:18.424> system<18:49:18.600> performance 18:49:21.526 --> 18:49:21.536 align:start position:0% 18:49:21.536 --> 18:49:23.862 align:start position:0% and<18:49:22.192> now<18:49:22.440> you<18:49:22.616> can<18:49:22.744> have<18:49:22.856> legitimate<18:49:23.512> issues 18:49:23.862 --> 18:49:23.872 align:start position:0% and now you can have legitimate issues 18:49:23.872 --> 18:49:25.790 align:start position:0% and now you can have legitimate issues that<18:49:24.120> represent<18:49:24.424> denial<18:49:24.896> of<18:49:25.080> service<18:49:25.256> like<18:49:25.616> a 18:49:25.790 --> 18:49:25.800 align:start position:0% that represent denial of service like a 18:49:25.800 --> 18:49:28.486 align:start position:0% that represent denial of service like a fonty<18:49:26.160> faulty<18:49:26.576> network<18:49:26.760> card<18:49:27.120> a<18:49:28.080> spanning 18:49:28.486 --> 18:49:28.496 align:start position:0% fonty faulty network card a spanning 18:49:28.496 --> 18:49:29.686 align:start position:0% fonty faulty network card a spanning tree<18:49:28.680> issue 18:49:29.686 --> 18:49:29.696 align:start position:0% tree issue 18:49:29.696 --> 18:49:31.910 align:start position:0% tree issue a<18:49:30.176> routing<18:49:30.480> protocol<18:49:30.832> convergence<18:49:31.616> when 18:49:31.910 --> 18:49:31.920 align:start position:0% a routing protocol convergence when 18:49:31.920 --> 18:49:33.646 align:start position:0% a routing protocol convergence when you're<18:49:32.040> either<18:49:32.280> booty<18:49:32.824> devices<18:49:33.056> or<18:49:33.424> a<18:49:33.536> network 18:49:33.646 --> 18:49:33.656 align:start position:0% you're either booty devices or a network 18:49:33.656 --> 18:49:35.566 align:start position:0% you're either booty devices or a network has<18:49:33.960> gone<18:49:34.144> down<18:49:34.376> or<18:49:34.680> up 18:49:35.566 --> 18:49:35.576 align:start position:0% has gone down or up 18:49:35.576 --> 18:49:38.326 align:start position:0% has gone down or up and<18:49:36.240> large<18:49:36.480> file<18:49:36.832> download<18:49:37.144> by<18:49:37.616> a<18:49:37.800> user<18:49:38.104> on<18:49:38.216> the 18:49:38.326 --> 18:49:38.336 align:start position:0% and large file download by a user on the 18:49:38.336 --> 18:49:40.542 align:start position:0% and large file download by a user on the network<18:49:38.464> who<18:49:38.936> doesn't<18:49:39.240> have<18:49:39.480> a<18:49:39.656> limit 18:49:40.542 --> 18:49:40.552 align:start position:0% network who doesn't have a limit 18:49:40.552 --> 18:49:42.886 align:start position:0% network who doesn't have a limit a<18:49:40.976> bulk<18:49:41.280> email<18:49:41.400> sent<18:49:41.824> for<18:49:42.056> marketing<18:49:42.600> for 18:49:42.886 --> 18:49:42.896 align:start position:0% a bulk email sent for marketing for 18:49:42.896 --> 18:49:45.846 align:start position:0% a bulk email sent for marketing for example 18:49:45.846 --> 18:49:45.856 align:start position:0% 18:49:45.856 --> 18:49:49.494 align:start position:0% unusually<18:49:46.856> slow<18:49:47.104> Network<18:49:47.464> I<18:49:48.120> know<18:49:48.296> and<18:49:49.256> some 18:49:49.494 --> 18:49:49.504 align:start position:0% unusually slow Network I know and some 18:49:49.504 --> 18:49:52.430 align:start position:0% unusually slow Network I know and some networks<18:49:49.976> I've<18:49:50.104> worked<18:49:50.512> up<18:49:50.696> at<18:49:51.536> for<18:49:51.960> example<18:49:52.192> a 18:49:52.430 --> 18:49:52.440 align:start position:0% networks I've worked up at for example a 18:49:52.440 --> 18:49:53.926 align:start position:0% networks I've worked up at for example a Friday<18:49:52.552> afternoon<18:49:52.856> there<18:49:53.280> was<18:49:53.400> a<18:49:53.512> big<18:49:53.576> backup 18:49:53.926 --> 18:49:53.936 align:start position:0% Friday afternoon there was a big backup 18:49:53.936 --> 18:49:56.206 align:start position:0% Friday afternoon there was a big backup and<18:49:54.120> the<18:49:54.296> whole<18:49:54.424> network<18:49:54.600> went<18:49:55.080> slow<18:49:55.320> but<18:49:56.040> if 18:49:56.206 --> 18:49:56.216 align:start position:0% and the whole network went slow but if 18:49:56.216 --> 18:49:57.774 align:start position:0% and the whole network went slow but if that<18:49:56.336> happened<18:49:56.512> on<18:49:56.824> another<18:49:57.000> time<18:49:57.480> of<18:49:57.656> the 18:49:57.774 --> 18:49:57.784 align:start position:0% that happened on another time of the 18:49:57.784 --> 18:50:00.606 align:start position:0% that happened on another time of the week<18:49:57.896> then<18:49:58.256> it<18:49:58.976> could<18:49:59.104> be<18:49:59.280> a<18:49:59.400> warning<18:49:59.760> sign 18:50:00.606 --> 18:50:00.616 align:start position:0% week then it could be a warning sign 18:50:00.616 --> 18:50:02.814 align:start position:0% week then it could be a warning sign unreachability<18:50:01.616> of<18:50:01.856> a<18:50:01.976> particular<18:50:02.280> website 18:50:02.814 --> 18:50:02.824 align:start position:0% unreachability of a particular website 18:50:02.824 --> 18:50:05.686 align:start position:0% unreachability of a particular website High<18:50:03.720> numbers<18:50:03.896> of<18:50:04.192> spam<18:50:04.440> messages<18:50:04.744> received 18:50:05.686 --> 18:50:05.696 align:start position:0% High numbers of spam messages received 18:50:05.696 --> 18:50:08.390 align:start position:0% High numbers of spam messages received on<18:50:05.872> an<18:50:06.056> email<18:50:06.296> account 18:50:08.390 --> 18:50:08.400 align:start position:0% on an email account 18:50:08.400 --> 18:50:10.910 align:start position:0% on an email account denial<18:50:09.360> of<18:50:09.600> service<18:50:09.784> oh<18:50:10.376> we've<18:50:10.680> just 18:50:10.910 --> 18:50:10.920 align:start position:0% denial of service oh we've just 18:50:10.920 --> 18:50:12.166 align:start position:0% denial of service oh we've just summarizing<18:50:11.400> what<18:50:11.512> we've<18:50:11.696> covered<18:50:12.000> is 18:50:12.166 --> 18:50:12.176 align:start position:0% summarizing what we've covered is 18:50:12.176 --> 18:50:14.686 align:start position:0% summarizing what we've covered is deniala<18:50:12.784> service<18:50:13.216> bandwidth<18:50:14.216> attacks 18:50:14.686 --> 18:50:14.696 align:start position:0% deniala service bandwidth attacks 18:50:14.696 --> 18:50:17.390 align:start position:0% deniala service bandwidth attacks connectivity<18:50:15.360> attacks<18:50:16.016> common<18:50:16.800> types<18:50:17.280> of 18:50:17.390 --> 18:50:17.400 align:start position:0% connectivity attacks common types of 18:50:17.400 --> 18:50:19.606 align:start position:0% connectivity attacks common types of deniala<18:50:18.056> service<18:50:18.240> and<18:50:18.720> what<18:50:18.896> is<18:50:19.080> distributed 18:50:19.606 --> 18:50:19.616 align:start position:0% deniala service and what is distributed 18:50:19.616 --> 18:50:21.646 align:start position:0% deniala service and what is distributed to<18:50:19.856> Denali<18:50:20.512> service 18:50:21.646 --> 18:50:21.656 align:start position:0% to Denali service 18:50:21.656 --> 18:50:24.590 align:start position:0% to Denali service types<18:50:22.376> of<18:50:22.496> distributed<18:50:23.160> attacks<18:50:23.696> the 18:50:24.590 --> 18:50:24.600 align:start position:0% types of distributed attacks the 18:50:24.600 --> 18:50:27.230 align:start position:0% types of distributed attacks the difference<18:50:24.784> differences<18:50:25.376> between<18:50:25.744> the<18:50:26.104> two 18:50:27.230 --> 18:50:27.240 align:start position:0% difference differences between the two 18:50:27.240 --> 18:50:30.350 align:start position:0% difference differences between the two reflective<18:50:28.080> denial<18:50:28.552> of<18:50:28.680> service<18:50:29.240> types<18:50:30.240> of 18:50:30.350 --> 18:50:30.360 align:start position:0% reflective denial of service types of 18:50:30.360 --> 18:50:33.470 align:start position:0% reflective denial of service types of reflective<18:50:30.896> unintentional 18:50:33.470 --> 18:50:33.480 align:start position:0% reflective unintentional 18:50:33.480 --> 18:50:35.454 align:start position:0% reflective unintentional attacks<18:50:34.320> on<18:50:34.376> our<18:50:34.552> physical<18:50:34.744> infrastructure 18:50:35.454 --> 18:50:35.464 align:start position:0% attacks on our physical infrastructure 18:50:35.464 --> 18:50:37.182 align:start position:0% attacks on our physical infrastructure and<18:50:35.760> then<18:50:35.872> preventing<18:50:36.360> denial<18:50:36.784> of<18:50:36.960> service 18:50:37.182 --> 18:50:37.192 align:start position:0% and then preventing denial of service 18:50:37.192 --> 18:50:40.134 align:start position:0% and then preventing denial of service and<18:50:37.920> identifying<18:50:38.576> one<18:50:38.760> when<18:50:38.936> it<18:50:39.120> happens<18:50:39.240> so 18:50:40.134 --> 18:50:40.144 align:start position:0% and identifying one when it happens so 18:50:40.144 --> 18:50:44.640 align:start position:0% and identifying one when it happens so that's<18:50:40.376> all<18:50:40.552> for<18:50:40.800> now<18:50:40.976> thanks<18:50:41.464> for<18:50:41.696> watching 18:50:44.640 --> 18:50:44.650 align:start position:0% 18:50:44.650 --> 18:51:01.790 align:start position:0% [Music] 18:51:01.790 --> 18:51:01.800 align:start position:0% 18:51:01.800 --> 18:51:04.606 align:start position:0% welcome<18:51:02.280> to<18:51:02.512> module<18:51:02.872> 14<18:51:03.176> lesson<18:51:03.896> 1A<18:51:04.320> common 18:51:04.606 --> 18:51:04.616 align:start position:0% welcome to module 14 lesson 1A common 18:51:04.616 --> 18:51:07.070 align:start position:0% welcome to module 14 lesson 1A common networking<18:51:05.216> attacks<18:51:05.760> we've<18:51:06.600> heard<18:51:06.784> earlier 18:51:07.070 --> 18:51:07.080 align:start position:0% networking attacks we've heard earlier 18:51:07.080 --> 18:51:09.286 align:start position:0% networking attacks we've heard earlier about<18:51:07.256> a<18:51:07.440> few<18:51:07.552> attacks<18:51:08.040> but<18:51:08.216> we<18:51:08.512> need<18:51:08.696> to<18:51:09.000> just 18:51:09.286 --> 18:51:09.296 align:start position:0% about a few attacks but we need to just 18:51:09.296 --> 18:51:11.926 align:start position:0% about a few attacks but we need to just update<18:51:09.720> the<18:51:10.080> list<18:51:10.440> because<18:51:11.104> of<18:51:11.400> the<18:51:11.576> new<18:51:11.760> stuff 18:51:11.926 --> 18:51:11.936 align:start position:0% update the list because of the new stuff 18:51:11.936 --> 18:51:15.590 align:start position:0% update the list because of the new stuff in<18:51:12.176> the<18:51:12.296> syllabus 18:51:15.590 --> 18:51:15.600 align:start position:0% 18:51:15.600 --> 18:51:18.470 align:start position:0% you<18:51:15.960> can<18:51:16.080> look<18:51:16.256> at<18:51:16.376> Social<18:51:16.552> Engineering 18:51:18.470 --> 18:51:18.480 align:start position:0% you can look at Social Engineering 18:51:18.480 --> 18:51:21.414 align:start position:0% you can look at Social Engineering Insider<18:51:19.320> threats<18:51:19.800> a<18:51:20.216> logic<18:51:20.576> bomb 18:51:21.414 --> 18:51:21.424 align:start position:0% Insider threats a logic bomb 18:51:21.424 --> 18:51:24.470 align:start position:0% Insider threats a logic bomb Rogue<18:51:22.144> access<18:51:22.256> point<18:51:22.680> Wireless 18:51:24.470 --> 18:51:24.480 align:start position:0% Rogue access point Wireless 18:51:24.480 --> 18:51:26.862 align:start position:0% Rogue access point Wireless evil<18:51:25.080> twin 18:51:26.862 --> 18:51:26.872 align:start position:0% evil twin 18:51:26.872 --> 18:51:29.094 align:start position:0% evil twin War<18:51:27.480> driving<18:51:27.784> could<18:51:28.192> love<18:51:28.440> to<18:51:28.552> know<18:51:28.680> who<18:51:28.856> comes 18:51:29.094 --> 18:51:29.104 align:start position:0% War driving could love to know who comes 18:51:29.104 --> 18:51:31.310 align:start position:0% War driving could love to know who comes up<18:51:29.280> with<18:51:29.760> all<18:51:29.936> of<18:51:30.056> these<18:51:30.296> names 18:51:31.310 --> 18:51:31.320 align:start position:0% up with all of these names 18:51:31.320 --> 18:51:33.590 align:start position:0% up with all of these names uh<18:51:31.744> fishing 18:51:33.590 --> 18:51:33.600 align:start position:0% uh fishing 18:51:33.600 --> 18:51:36.646 align:start position:0% uh fishing around<18:51:33.960> somewhere<18:51:34.616> DNS<18:51:35.280> poisoning<18:51:36.000> ARP 18:51:36.646 --> 18:51:36.656 align:start position:0% around somewhere DNS poisoning ARP 18:51:36.656 --> 18:51:38.822 align:start position:0% around somewhere DNS poisoning ARP poisoning<18:51:37.256> spoofing 18:51:38.822 --> 18:51:38.832 align:start position:0% poisoning spoofing 18:51:38.832 --> 18:51:42.166 align:start position:0% poisoning spoofing de-authentication<18:51:39.920> Brute<18:51:40.920> Force 18:51:42.166 --> 18:51:42.176 align:start position:0% de-authentication Brute Force 18:51:42.176 --> 18:51:45.590 align:start position:0% de-authentication Brute Force VLAN<18:51:42.784> hopping<18:51:43.256> man<18:51:43.920> in<18:51:44.216> the<18:51:44.400> middle 18:51:45.590 --> 18:51:45.600 align:start position:0% VLAN hopping man in the middle 18:51:45.600 --> 18:51:47.206 align:start position:0% VLAN hopping man in the middle and<18:51:46.192> then<18:51:46.320> some<18:51:46.552> exploits<18:51:47.104> and 18:51:47.206 --> 18:51:47.216 align:start position:0% and then some exploits and 18:51:47.216 --> 18:51:50.270 align:start position:0% and then some exploits and vulnerabilities<18:51:47.960> social<18:51:48.960> engineering<18:51:49.744> the 18:51:50.270 --> 18:51:50.280 align:start position:0% vulnerabilities social engineering the 18:51:50.280 --> 18:51:52.134 align:start position:0% vulnerabilities social engineering the funny<18:51:50.400> thing<18:51:50.696> about<18:51:50.824> this<18:51:51.120> threat<18:51:51.480> is<18:51:51.656> it 18:51:52.134 --> 18:51:52.144 align:start position:0% funny thing about this threat is it 18:51:52.144 --> 18:51:55.366 align:start position:0% funny thing about this threat is it isn't<18:51:53.040> um<18:51:53.160> electronically<18:51:53.960> detectable<18:51:54.960> so<18:51:55.192> we 18:51:55.366 --> 18:51:55.376 align:start position:0% isn't um electronically detectable so we 18:51:55.376 --> 18:51:58.006 align:start position:0% isn't um electronically detectable so we don't<18:51:55.504> have<18:51:55.680> a<18:51:55.976> little<18:51:56.512> alarm<18:51:56.872> go<18:51:57.832> off 18:51:58.006 --> 18:51:58.016 align:start position:0% don't have a little alarm go off 18:51:58.016 --> 18:52:00.590 align:start position:0% don't have a little alarm go off somewhere<18:51:58.552> it's<18:51:59.512> um<18:51:59.512> normally<18:51:59.936> when<18:52:00.176> an 18:52:00.590 --> 18:52:00.600 align:start position:0% somewhere it's um normally when an 18:52:00.600 --> 18:52:02.926 align:start position:0% somewhere it's um normally when an attacker<18:52:01.016> convinces<18:52:01.552> an<18:52:01.800> employee<18:52:02.160> to 18:52:02.926 --> 18:52:02.936 align:start position:0% attacker convinces an employee to 18:52:02.936 --> 18:52:05.686 align:start position:0% attacker convinces an employee to disclose<18:52:03.480> confidential<18:52:04.144> information<18:52:04.696> so 18:52:05.686 --> 18:52:05.696 align:start position:0% disclose confidential information so 18:52:05.696 --> 18:52:10.134 align:start position:0% disclose confidential information so what<18:52:05.872> happens<18:52:06.176> is<18:52:06.600> uh<18:52:07.376> perhaps<18:52:08.336> they<18:52:08.640> could<18:52:09.120> um 18:52:10.134 --> 18:52:10.144 align:start position:0% what happens is uh perhaps they could um 18:52:10.144 --> 18:52:12.286 align:start position:0% what happens is uh perhaps they could um say<18:52:10.552> they<18:52:10.744> make<18:52:10.920> a<18:52:11.104> phone<18:52:11.280> call<18:52:11.512> that<18:52:11.760> it<18:52:11.936> goes 18:52:12.286 --> 18:52:12.296 align:start position:0% say they make a phone call that it goes 18:52:12.296 --> 18:52:13.734 align:start position:0% say they make a phone call that it goes through<18:52:12.480> to 18:52:13.734 --> 18:52:13.744 align:start position:0% through to 18:52:13.744 --> 18:52:15.246 align:start position:0% through to um 18:52:15.246 --> 18:52:15.256 align:start position:0% um 18:52:15.256 --> 18:52:18.646 align:start position:0% um headquarters<18:52:16.256> office<18:52:16.496> and<18:52:17.400> then<18:52:17.512> they 18:52:18.646 --> 18:52:18.656 align:start position:0% headquarters office and then they 18:52:18.656 --> 18:52:20.862 align:start position:0% headquarters office and then they um<18:52:18.720> they<18:52:19.320> asked<18:52:19.552> to<18:52:19.616> be<18:52:19.744> put<18:52:19.920> through<18:52:20.160> to<18:52:20.464> your 18:52:20.862 --> 18:52:20.872 align:start position:0% um they asked to be put through to your 18:52:20.872 --> 18:52:23.566 align:start position:0% um they asked to be put through to your office<18:52:21.192> so<18:52:22.192> what<18:52:22.440> you'll<18:52:22.680> probably<18:52:22.856> see<18:52:23.160> on 18:52:23.566 --> 18:52:23.576 align:start position:0% office so what you'll probably see on 18:52:23.576 --> 18:52:27.886 align:start position:0% office so what you'll probably see on your<18:52:24.424> phone<18:52:25.016> is<18:52:25.376> the<18:52:25.616> extension<18:52:26.600> one<18:52:27.600> two 18:52:27.886 --> 18:52:27.896 align:start position:0% your phone is the extension one two 18:52:27.896 --> 18:52:29.750 align:start position:0% your phone is the extension one two three<18:52:28.192> four<18:52:28.440> as<18:52:28.744> if<18:52:28.920> it's<18:52:28.976> coming<18:52:29.216> from<18:52:29.512> here 18:52:29.750 --> 18:52:29.760 align:start position:0% three four as if it's coming from here 18:52:29.760 --> 18:52:32.326 align:start position:0% three four as if it's coming from here so<18:52:30.240> you<18:52:30.424> think<18:52:30.536> it's<18:52:30.600> an<18:52:30.784> internal<18:52:31.192> call<18:52:31.504> and 18:52:32.326 --> 18:52:32.336 align:start position:0% so you think it's an internal call and 18:52:32.336 --> 18:52:35.030 align:start position:0% so you think it's an internal call and but<18:52:32.640> really<18:52:32.824> it's<18:52:33.056> coming<18:52:33.296> from<18:52:33.784> outside<18:52:34.496> here 18:52:35.030 --> 18:52:35.040 align:start position:0% but really it's coming from outside here 18:52:35.040 --> 18:52:37.670 align:start position:0% but really it's coming from outside here in<18:52:35.400> the<18:52:35.872> um<18:52:36.000> the<18:52:36.536> EU<18:52:36.896> the<18:52:37.192> hackers<18:52:37.504> house 18:52:37.670 --> 18:52:37.680 align:start position:0% in the um the EU the hackers house 18:52:37.680 --> 18:52:40.846 align:start position:0% in the um the EU the hackers house wherever<18:52:38.040> they<18:52:38.216> may<18:52:38.464> be<18:52:38.656> so<18:52:39.656> it<18:52:40.016> looks<18:52:40.256> like<18:52:40.856> um 18:52:40.846 --> 18:52:40.856 align:start position:0% wherever they may be so it looks like um 18:52:40.856 --> 18:52:43.430 align:start position:0% wherever they may be so it looks like um uh<18:52:41.512> the<18:52:41.760> legitimate<18:52:42.176> call 18:52:43.430 --> 18:52:43.440 align:start position:0% uh the legitimate call 18:52:43.440 --> 18:52:46.006 align:start position:0% uh the legitimate call they<18:52:43.920> pretend<18:52:44.336> to<18:52:44.512> be<18:52:44.696> a<18:52:45.056> senior<18:52:45.424> manager<18:52:45.784> or 18:52:46.006 --> 18:52:46.016 align:start position:0% they pretend to be a senior manager or 18:52:46.016 --> 18:52:47.326 align:start position:0% they pretend to be a senior manager or someone<18:52:46.256> inside<18:52:46.680> the<18:52:46.920> tech<18:52:47.104> support 18:52:47.326 --> 18:52:47.336 align:start position:0% someone inside the tech support 18:52:47.336 --> 18:52:48.774 align:start position:0% someone inside the tech support department 18:52:48.774 --> 18:52:48.784 align:start position:0% department 18:52:48.784 --> 18:52:51.286 align:start position:0% department and<18:52:50.040> um<18:52:50.104> they'll<18:52:50.512> access<18:52:50.760> some<18:52:51.120> information 18:52:51.286 --> 18:52:51.296 align:start position:0% and um they'll access some information 18:52:51.296 --> 18:52:53.566 align:start position:0% and um they'll access some information they'll<18:52:51.784> ask<18:52:51.960> you<18:52:52.080> for<18:52:52.320> passcodes<18:52:53.160> or<18:52:53.400> say 18:52:53.566 --> 18:52:53.576 align:start position:0% they'll ask you for passcodes or say 18:52:53.576 --> 18:52:56.030 align:start position:0% they'll ask you for passcodes or say there's<18:52:53.760> a<18:52:53.936> problem<18:52:54.056> with<18:52:54.240> your<18:52:54.424> account<18:52:54.600> and 18:52:56.030 --> 18:52:56.040 align:start position:0% there's a problem with your account and 18:52:56.040 --> 18:52:57.950 align:start position:0% there's a problem with your account and um this<18:52:56.336> is<18:52:56.464> a<18:52:56.640> pretty<18:52:56.760> successful<18:52:57.176> way<18:52:57.480> of<18:52:57.656> of 18:52:57.950 --> 18:52:57.960 align:start position:0% um this is a pretty successful way of of 18:52:57.960 --> 18:53:00.286 align:start position:0% um this is a pretty successful way of of getting<18:52:58.744> information 18:53:00.286 --> 18:53:00.296 align:start position:0% getting information 18:53:00.296 --> 18:53:02.094 align:start position:0% getting information the<18:53:00.784> other<18:53:00.896> thing<18:53:01.192> is 18:53:02.094 --> 18:53:02.104 align:start position:0% the other thing is 18:53:02.104 --> 18:53:04.734 align:start position:0% the other thing is um<18:53:02.160> or<18:53:02.576> accounts<18:53:03.120> are<18:53:03.176> social<18:53:03.360> engineering<18:53:04.080> is 18:53:04.734 --> 18:53:04.744 align:start position:0% um or accounts are social engineering is 18:53:04.744 --> 18:53:08.030 align:start position:0% um or accounts are social engineering is somebody<18:53:05.464> Who<18:53:05.872> Walks<18:53:06.240> Behind<18:53:06.656> the<18:53:07.552> employee 18:53:08.030 --> 18:53:08.040 align:start position:0% somebody Who Walks Behind the employee 18:53:08.040 --> 18:53:10.542 align:start position:0% somebody Who Walks Behind the employee who's<18:53:08.280> already<18:53:08.576> entered<18:53:09.000> the<18:53:09.424> security<18:53:10.192> guard 18:53:10.542 --> 18:53:10.552 align:start position:0% who's already entered the security guard 18:53:10.552 --> 18:53:14.326 align:start position:0% who's already entered the security guard for<18:53:10.800> a<18:53:10.976> door<18:53:11.104> also<18:53:11.696> known<18:53:11.824> as<18:53:12.000> tailgating 18:53:14.326 --> 18:53:14.336 align:start position:0% for a door also known as tailgating 18:53:14.336 --> 18:53:16.790 align:start position:0% for a door also known as tailgating also<18:53:15.120> another<18:53:15.360> way<18:53:15.656> is<18:53:15.784> leaving<18:53:16.080> the<18:53:16.320> USB 18:53:16.790 --> 18:53:16.800 align:start position:0% also another way is leaving the USB 18:53:16.800 --> 18:53:19.670 align:start position:0% also another way is leaving the USB ground<18:53:17.160> on<18:53:17.576> the<18:53:18.192> USB<18:53:19.192> on<18:53:19.376> the<18:53:19.552> ground 18:53:19.670 --> 18:53:19.680 align:start position:0% ground on the USB on the ground 18:53:19.680 --> 18:53:22.734 align:start position:0% ground on the USB on the ground somewhere<18:53:20.400> this<18:53:21.176> is<18:53:21.360> quite<18:53:21.600> common<18:53:21.896> sometimes 18:53:22.734 --> 18:53:22.744 align:start position:0% somewhere this is quite common sometimes 18:53:22.744 --> 18:53:25.070 align:start position:0% somewhere this is quite common sometimes this<18:53:23.104> these<18:53:23.512> USB<18:53:23.936> sticks<18:53:24.360> have<18:53:24.536> actually<18:53:24.720> got 18:53:25.070 --> 18:53:25.080 align:start position:0% this these USB sticks have actually got 18:53:25.080 --> 18:53:27.590 align:start position:0% this these USB sticks have actually got a<18:53:25.320> battery<18:53:25.800> in<18:53:26.160> and<18:53:26.824> it's<18:53:27.000> designed<18:53:27.360> whatever 18:53:27.590 --> 18:53:27.600 align:start position:0% a battery in and it's designed whatever 18:53:27.600 --> 18:53:29.990 align:start position:0% a battery in and it's designed whatever whatever<18:53:28.080> device<18:53:28.496> you<18:53:28.856> plug<18:53:29.040> it<18:53:29.216> into<18:53:29.336> sends 18:53:29.990 --> 18:53:30.000 align:start position:0% whatever device you plug it into sends 18:53:30.000 --> 18:53:32.326 align:start position:0% whatever device you plug it into sends an<18:53:30.056> electrical<18:53:30.600> current<18:53:30.784> through<18:53:31.192> it<18:53:31.440> and<18:53:32.040> it 18:53:32.326 --> 18:53:32.336 align:start position:0% an electrical current through it and it 18:53:32.336 --> 18:53:34.246 align:start position:0% an electrical current through it and it fries<18:53:32.760> your<18:53:33.056> circuit<18:53:33.480> board<18:53:33.600> and<18:53:33.832> Fries<18:53:34.080> your 18:53:34.246 --> 18:53:34.256 align:start position:0% fries your circuit board and Fries your 18:53:34.256 --> 18:53:37.134 align:start position:0% fries your circuit board and Fries your hard<18:53:34.440> drive<18:53:34.696> or<18:53:35.696> it<18:53:36.120> can<18:53:36.296> actually<18:53:36.424> plant<18:53:36.832> some 18:53:37.134 --> 18:53:37.144 align:start position:0% hard drive or it can actually plant some 18:53:37.144 --> 18:53:40.910 align:start position:0% hard drive or it can actually plant some lines<18:53:37.440> of<18:53:37.680> code 18:53:40.910 --> 18:53:40.920 align:start position:0% 18:53:40.920 --> 18:53:43.670 align:start position:0% Insider<18:53:41.824> threats<18:53:42.176> normally<18:53:42.536> an<18:53:42.720> employee<18:53:43.192> or 18:53:43.670 --> 18:53:43.680 align:start position:0% Insider threats normally an employee or 18:53:43.680 --> 18:53:44.990 align:start position:0% Insider threats normally an employee or a<18:53:43.856> contractor 18:53:44.990 --> 18:53:45.000 align:start position:0% a contractor 18:53:45.000 --> 18:53:47.326 align:start position:0% a contractor they<18:53:45.536> could<18:53:45.720> be<18:53:45.896> under<18:53:46.080> duress<18:53:46.552> working<18:53:46.976> for<18:53:47.216> a 18:53:47.326 --> 18:53:47.336 align:start position:0% they could be under duress working for a 18:53:47.336 --> 18:53:50.990 align:start position:0% they could be under duress working for a competitor<18:53:48.016> or<18:53:49.016> a<18:53:49.192> blackmailer<18:53:50.040> looking<18:53:50.760> to 18:53:50.990 --> 18:53:51.000 align:start position:0% competitor or a blackmailer looking to 18:53:51.000 --> 18:53:53.030 align:start position:0% competitor or a blackmailer looking to get<18:53:51.176> information 18:53:53.030 --> 18:53:53.040 align:start position:0% get information 18:53:53.040 --> 18:53:55.966 align:start position:0% get information and<18:53:53.640> most<18:53:53.936> security<18:53:54.424> focuses<18:53:55.192> on<18:53:55.440> external 18:53:55.966 --> 18:53:55.976 align:start position:0% and most security focuses on external 18:53:55.976 --> 18:53:59.926 align:start position:0% and most security focuses on external threats<18:53:56.464> so<18:53:57.440> it's<18:53:58.440> looking<18:53:58.680> at 18:53:59.926 --> 18:53:59.936 align:start position:0% threats so it's looking at 18:53:59.936 --> 18:54:02.206 align:start position:0% threats so it's looking at incoming<18:54:00.896> attacks 18:54:02.206 --> 18:54:02.216 align:start position:0% incoming attacks 18:54:02.216 --> 18:54:04.542 align:start position:0% incoming attacks malware<18:54:03.000> Trojans<18:54:03.656> all<18:54:03.896> that<18:54:04.016> kind<18:54:04.192> of<18:54:04.376> stuff 18:54:04.542 --> 18:54:04.552 align:start position:0% malware Trojans all that kind of stuff 18:54:04.552 --> 18:54:07.246 align:start position:0% malware Trojans all that kind of stuff but<18:54:05.160> inside<18:54:05.400> your<18:54:05.824> organization<18:54:06.656> obviously 18:54:07.246 --> 18:54:07.256 align:start position:0% but inside your organization obviously 18:54:07.256 --> 18:54:09.110 align:start position:0% but inside your organization obviously you<18:54:07.856> could<18:54:07.920> have<18:54:08.104> people<18:54:08.336> that<18:54:08.640> are<18:54:08.760> posing 18:54:09.110 --> 18:54:09.120 align:start position:0% you could have people that are posing 18:54:09.120 --> 18:54:10.542 align:start position:0% you could have people that are posing the<18:54:09.240> threat 18:54:10.542 --> 18:54:10.552 align:start position:0% the threat 18:54:10.552 --> 18:54:13.182 align:start position:0% the threat so<18:54:11.160> people<18:54:11.760> who<18:54:12.056> work<18:54:12.424> for<18:54:12.600> your<18:54:12.720> organization 18:54:13.182 --> 18:54:13.192 align:start position:0% so people who work for your organization 18:54:13.192 --> 18:54:14.750 align:start position:0% so people who work for your organization should<18:54:13.504> know<18:54:13.680> your<18:54:13.920> systems<18:54:14.336> policies 18:54:14.750 --> 18:54:14.760 align:start position:0% should know your systems policies 18:54:14.760 --> 18:54:17.390 align:start position:0% should know your systems policies procedures<18:54:15.360> and<18:54:15.720> weaknesses<18:54:16.256> and<18:54:17.216> they 18:54:17.390 --> 18:54:17.400 align:start position:0% procedures and weaknesses and they 18:54:17.400 --> 18:54:19.134 align:start position:0% procedures and weaknesses and they should<18:54:17.576> know<18:54:17.696> how<18:54:18.000> to<18:54:18.240> spot<18:54:18.480> somebody<18:54:18.832> Who's 18:54:19.134 --> 18:54:19.144 align:start position:0% should know how to spot somebody Who's 18:54:19.144 --> 18:54:21.230 align:start position:0% should know how to spot somebody Who's acting<18:54:19.552> suspiciously<18:54:20.216> or<18:54:20.696> acting<18:54:21.056> for 18:54:21.230 --> 18:54:21.240 align:start position:0% acting suspiciously or acting for 18:54:21.240 --> 18:54:23.150 align:start position:0% acting suspiciously or acting for suspicious<18:54:21.720> information 18:54:23.150 --> 18:54:23.160 align:start position:0% suspicious information 18:54:23.160 --> 18:54:24.774 align:start position:0% suspicious information as<18:54:23.696> you've<18:54:23.936> probably<18:54:24.000> seen<18:54:24.240> in<18:54:24.480> the<18:54:24.600> movies 18:54:24.774 --> 18:54:24.784 align:start position:0% as you've probably seen in the movies 18:54:24.784 --> 18:54:28.430 align:start position:0% as you've probably seen in the movies you<18:54:25.192> could<18:54:25.320> have<18:54:25.440> what's<18:54:25.920> known<18:54:26.160> as<18:54:26.280> a<18:54:26.512> sleeper 18:54:28.430 --> 18:54:28.440 align:start position:0% you could have what's known as a sleeper 18:54:28.440 --> 18:54:30.822 align:start position:0% you could have what's known as a sleeper so<18:54:28.856> we<18:54:29.040> normally<18:54:29.280> uh 18:54:30.822 --> 18:54:30.832 align:start position:0% so we normally uh 18:54:30.832 --> 18:54:34.246 align:start position:0% so we normally uh associate<18:54:31.744> this<18:54:31.976> with<18:54:32.280> spies<18:54:32.896> sleeper<18:54:33.896> agents 18:54:34.246 --> 18:54:34.256 align:start position:0% associate this with spies sleeper agents 18:54:34.256 --> 18:54:35.566 align:start position:0% associate this with spies sleeper agents let's<18:54:34.440> sleep<18:54:34.680> with<18:54:34.856> somebody<18:54:34.976> who<18:54:35.280> could<18:54:35.400> be 18:54:35.566 --> 18:54:35.576 align:start position:0% let's sleep with somebody who could be 18:54:35.576 --> 18:54:37.966 align:start position:0% let's sleep with somebody who could be waiting<18:54:36.296> to<18:54:36.424> be<18:54:36.600> activated 18:54:37.966 --> 18:54:37.976 align:start position:0% waiting to be activated 18:54:37.976 --> 18:54:39.166 align:start position:0% waiting to be activated obviously<18:54:38.512> they<18:54:38.696> could<18:54:38.824> easily<18:54:39.056> go 18:54:39.166 --> 18:54:39.176 align:start position:0% obviously they could easily go 18:54:39.176 --> 18:54:42.046 align:start position:0% obviously they could easily go undetected<18:54:39.784> and<18:54:40.256> they<18:54:40.440> could<18:54:40.552> be<18:54:40.680> doing 18:54:42.046 --> 18:54:42.056 align:start position:0% undetected and they could be doing 18:54:42.056 --> 18:54:43.542 align:start position:0% undetected and they could be doing um<18:54:42.120> things<18:54:42.424> to<18:54:42.600> your<18:54:42.784> network<18:54:42.960> or<18:54:43.192> passing 18:54:43.542 --> 18:54:43.552 align:start position:0% um things to your network or passing 18:54:43.552 --> 18:54:47.030 align:start position:0% um things to your network or passing information<18:54:43.744> for<18:54:44.216> some<18:54:44.400> time 18:54:47.030 --> 18:54:47.040 align:start position:0% 18:54:47.040 --> 18:54:49.846 align:start position:0% a<18:54:47.400> logic<18:54:47.760> bomb<18:54:48.000> is<18:54:48.240> a<18:54:48.424> type<18:54:48.600> of<18:54:48.784> malware 18:54:49.846 --> 18:54:49.856 align:start position:0% a logic bomb is a type of malware 18:54:49.856 --> 18:54:52.134 align:start position:0% a logic bomb is a type of malware it<18:54:50.400> does<18:54:50.512> damage<18:54:51.240> after<18:54:51.424> a<18:54:51.720> certain<18:54:51.896> condition 18:54:52.134 --> 18:54:52.144 align:start position:0% it does damage after a certain condition 18:54:52.144 --> 18:54:54.774 align:start position:0% it does damage after a certain condition is<18:54:52.552> met<18:54:52.800> so<18:54:53.280> an<18:54:53.464> example<18:54:53.824> is 18:54:54.774 --> 18:54:54.784 align:start position:0% is met so an example is 18:54:54.784 --> 18:54:56.990 align:start position:0% is met so an example is um<18:54:54.832> the<18:54:55.256> spyware<18:54:55.680> or<18:54:56.040> the<18:54:56.216> the<18:54:56.336> malware<18:54:56.760> sorry 18:54:56.990 --> 18:54:57.000 align:start position:0% um the spyware or the the malware sorry 18:54:57.000 --> 18:54:58.846 align:start position:0% um the spyware or the the malware sorry is<18:54:57.240> on<18:54:57.480> your<18:54:57.720> device 18:54:58.846 --> 18:54:58.856 align:start position:0% is on your device 18:54:58.856 --> 18:55:01.134 align:start position:0% is on your device and<18:54:59.400> then<18:54:59.512> when<18:54:59.696> the<18:54:59.872> clock<18:55:00.000> ticks<18:55:00.480> over<18:55:00.656> to 18:55:01.134 --> 18:55:01.144 align:start position:0% and then when the clock ticks over to 18:55:01.144 --> 18:55:05.150 align:start position:0% and then when the clock ticks over to the<18:55:01.920> first<18:55:02.040> of<18:55:02.336> the<18:55:02.576> first<18:55:02.896> say<18:55:03.896> 2019<18:55:04.744> or 18:55:05.150 --> 18:55:05.160 align:start position:0% the first of the first say 2019 or 18:55:05.160 --> 18:55:09.822 align:start position:0% the first of the first say 2019 or whatever<18:55:05.336> it<18:55:06.176> then<18:55:06.424> executes<18:55:07.192> the 18:55:09.822 --> 18:55:09.832 align:start position:0% 18:55:09.832 --> 18:55:11.862 align:start position:0% it<18:55:10.192> executes<18:55:10.744> the<18:55:10.920> code<18:55:11.040> and<18:55:11.336> then<18:55:11.464> does<18:55:11.640> the 18:55:11.862 --> 18:55:11.872 align:start position:0% it executes the code and then does the 18:55:11.872 --> 18:55:13.790 align:start position:0% it executes the code and then does the damage 18:55:13.790 --> 18:55:13.800 align:start position:0% damage 18:55:13.800 --> 18:55:15.590 align:start position:0% damage it<18:55:14.160> can<18:55:14.280> be<18:55:14.336> left<18:55:14.464> behind<18:55:14.760> after<18:55:14.936> attack<18:55:15.296> and 18:55:15.590 --> 18:55:15.600 align:start position:0% it can be left behind after attack and 18:55:15.600 --> 18:55:17.390 align:start position:0% it can be left behind after attack and what<18:55:15.784> it<18:55:15.832> could<18:55:15.960> do<18:55:16.080> is<18:55:16.192> destroy<18:55:16.744> any<18:55:17.040> evidence 18:55:17.390 --> 18:55:17.400 align:start position:0% what it could do is destroy any evidence 18:55:17.400 --> 18:55:19.430 align:start position:0% what it could do is destroy any evidence that<18:55:18.120> is<18:55:18.240> taking<18:55:18.424> place<18:55:18.656> so<18:55:18.832> it<18:55:19.016> could<18:55:19.144> destroy 18:55:19.430 --> 18:55:19.440 align:start position:0% that is taking place so it could destroy 18:55:19.440 --> 18:55:21.110 align:start position:0% that is taking place so it could destroy whatever<18:55:19.680> fires<18:55:20.216> it's<18:55:20.400> actually<18:55:20.576> put<18:55:20.760> on<18:55:20.936> your 18:55:21.110 --> 18:55:21.120 align:start position:0% whatever fires it's actually put on your 18:55:21.120 --> 18:55:23.326 align:start position:0% whatever fires it's actually put on your system<18:55:21.360> making<18:55:22.256> it<18:55:22.440> harder<18:55:22.744> for<18:55:22.920> you<18:55:22.976> to<18:55:23.104> do<18:55:23.216> a 18:55:23.326 --> 18:55:23.336 align:start position:0% system making it harder for you to do a 18:55:23.336 --> 18:55:25.430 align:start position:0% system making it harder for you to do a forensic<18:55:23.696> analysis 18:55:25.430 --> 18:55:25.440 align:start position:0% forensic analysis 18:55:25.440 --> 18:55:27.470 align:start position:0% forensic analysis you<18:55:25.920> may<18:55:26.040> remember<18:55:26.216> the<18:55:26.512> Chernobyl<18:55:27.056> virus 18:55:27.470 --> 18:55:27.480 align:start position:0% you may remember the Chernobyl virus 18:55:27.480 --> 18:55:30.646 align:start position:0% you may remember the Chernobyl virus this<18:55:27.832> was<18:55:27.960> an<18:55:28.144> example<18:55:28.440> of<18:55:28.680> a<18:55:28.920> logic<18:55:29.400> bomb 18:55:30.646 --> 18:55:30.656 align:start position:0% this was an example of a logic bomb 18:55:30.656 --> 18:55:33.286 align:start position:0% this was an example of a logic bomb they<18:55:31.256> wrote<18:55:31.680> to<18:55:31.800> the<18:55:31.976> boot<18:55:32.464> sector<18:55:32.696> of<18:55:32.872> discs 18:55:33.286 --> 18:55:33.296 align:start position:0% they wrote to the boot sector of discs 18:55:33.296 --> 18:55:35.326 align:start position:0% they wrote to the boot sector of discs swipe<18:55:33.720> the<18:55:33.832> bias<18:55:34.192> on<18:55:34.440> the<18:55:34.552> hard<18:55:34.744> drives<18:55:35.104> and 18:55:35.326 --> 18:55:35.336 align:start position:0% swipe the bias on the hard drives and 18:55:35.336 --> 18:55:37.966 align:start position:0% swipe the bias on the hard drives and left<18:55:35.512> the<18:55:35.824> devices<18:55:36.536> unusable 18:55:37.966 --> 18:55:37.976 align:start position:0% left the devices unusable 18:55:37.976 --> 18:55:39.526 align:start position:0% left the devices unusable so<18:55:38.336> pretty<18:55:38.576> bad 18:55:39.526 --> 18:55:39.536 align:start position:0% so pretty bad 18:55:39.536 --> 18:55:42.350 align:start position:0% so pretty bad uh<18:55:40.080> Rogue<18:55:40.976> access<18:55:41.104> points<18:55:41.696> so<18:55:42.000> we're<18:55:42.176> talking 18:55:42.350 --> 18:55:42.360 align:start position:0% uh Rogue access points so we're talking 18:55:42.360 --> 18:55:45.590 align:start position:0% uh Rogue access points so we're talking about<18:55:42.656> the<18:55:43.616> um<18:55:43.616> waps<18:55:44.216> wireless<18:55:44.576> access<18:55:45.000> points 18:55:45.590 --> 18:55:45.600 align:start position:0% about the um waps wireless access points 18:55:45.600 --> 18:55:47.630 align:start position:0% about the um waps wireless access points major<18:55:46.256> concern<18:55:46.680> especially<18:55:47.160> in<18:55:47.400> large 18:55:47.630 --> 18:55:47.640 align:start position:0% major concern especially in large 18:55:47.640 --> 18:55:49.134 align:start position:0% major concern especially in large environments 18:55:49.134 --> 18:55:49.144 align:start position:0% environments 18:55:49.144 --> 18:55:51.230 align:start position:0% environments so<18:55:49.440> somebody's<18:55:49.976> brought<18:55:50.216> in<18:55:50.400> a<18:55:50.640> third-party 18:55:51.230 --> 18:55:51.240 align:start position:0% so somebody's brought in a third-party 18:55:51.240 --> 18:55:54.350 align:start position:0% so somebody's brought in a third-party access<18:55:51.424> point<18:55:51.832> by<18:55:52.440> Network<18:55:52.744> user<18:55:53.336> often<18:55:54.056> this 18:55:54.350 --> 18:55:54.360 align:start position:0% access point by Network user often this 18:55:54.360 --> 18:55:56.150 align:start position:0% access point by Network user often this can<18:55:54.720> happen<18:55:54.896> when<18:55:55.192> somebody's<18:55:55.616> complaining 18:55:56.150 --> 18:55:56.160 align:start position:0% can happen when somebody's complaining 18:55:56.160 --> 18:55:57.166 align:start position:0% can happen when somebody's complaining about 18:55:57.166 --> 18:55:57.176 align:start position:0% about 18:55:57.176 --> 18:55:59.270 align:start position:0% about their<18:55:57.832> signals<18:55:58.320> you've<18:55:58.616> got<18:55:58.744> you<18:55:59.040> know<18:55:59.104> you've 18:55:59.270 --> 18:55:59.280 align:start position:0% their signals you've got you know you've 18:55:59.280 --> 18:56:02.030 align:start position:0% their signals you've got you know you've got<18:55:59.400> bars<18:55:59.936> on<18:56:00.176> your<18:56:00.360> device<18:56:00.832> so<18:56:01.616> you've<18:56:01.856> got 18:56:02.030 --> 18:56:02.040 align:start position:0% got bars on your device so you've got 18:56:02.040 --> 18:56:05.454 align:start position:0% got bars on your device so you've got one<18:56:02.640> or<18:56:02.872> two<18:56:03.120> bars<18:56:03.600> then<18:56:04.320> I've<18:56:04.744> seen<18:56:04.976> instances 18:56:05.454 --> 18:56:05.464 align:start position:0% one or two bars then I've seen instances 18:56:05.464 --> 18:56:07.606 align:start position:0% one or two bars then I've seen instances where<18:56:05.872> people<18:56:06.176> have<18:56:06.424> brought<18:56:06.600> in<18:56:06.784> their<18:56:07.016> own 18:56:07.606 --> 18:56:07.616 align:start position:0% where people have brought in their own 18:56:07.616 --> 18:56:10.134 align:start position:0% where people have brought in their own access<18:56:07.856> points<18:56:08.512> and<18:56:09.296> somehow<18:56:09.656> managed<18:56:10.016> to 18:56:10.134 --> 18:56:10.144 align:start position:0% access points and somehow managed to 18:56:10.144 --> 18:56:12.590 align:start position:0% access points and somehow managed to connect<18:56:10.320> to<18:56:10.616> the<18:56:10.920> network<18:56:11.400> and<18:56:12.240> they<18:56:12.424> get 18:56:12.590 --> 18:56:12.600 align:start position:0% connect to the network and they get 18:56:12.600 --> 18:56:16.070 align:start position:0% connect to the network and they get obviously<18:56:13.080> a<18:56:13.640> higher<18:56:14.640> connection<18:56:14.824> or<18:56:15.784> faster 18:56:16.070 --> 18:56:16.080 align:start position:0% obviously a higher connection or faster 18:56:16.080 --> 18:56:17.150 align:start position:0% obviously a higher connection or faster connection 18:56:17.150 --> 18:56:17.160 align:start position:0% connection 18:56:17.160 --> 18:56:20.030 align:start position:0% connection so<18:56:17.872> gives<18:56:18.176> a<18:56:18.424> network<18:56:18.600> access<18:56:18.896> to<18:56:19.256> anybody<18:56:19.616> in 18:56:20.030 --> 18:56:20.040 align:start position:0% so gives a network access to anybody in 18:56:20.040 --> 18:56:21.590 align:start position:0% so gives a network access to anybody in range<18:56:20.280> of<18:56:20.400> the<18:56:20.512> Rogue<18:56:20.872> access<18:56:20.936> point<18:56:21.240> so<18:56:21.424> this 18:56:21.590 --> 18:56:21.600 align:start position:0% range of the Rogue access point so this 18:56:21.600 --> 18:56:24.886 align:start position:0% range of the Rogue access point so this is<18:56:21.720> the<18:56:21.896> the<18:56:22.080> danger<18:56:22.376> of<18:56:22.616> people<18:56:22.936> who<18:56:23.936> uh<18:56:24.656> on 18:56:24.886 --> 18:56:24.896 align:start position:0% is the the danger of people who uh on 18:56:24.896 --> 18:56:26.990 align:start position:0% is the the danger of people who uh on purpose<18:56:25.256> or<18:56:25.552> just<18:56:26.280> accidentally<18:56:26.696> they<18:56:26.872> don't 18:56:26.990 --> 18:56:27.000 align:start position:0% purpose or just accidentally they don't 18:56:27.000 --> 18:56:29.030 align:start position:0% purpose or just accidentally they don't know<18:56:27.120> how<18:56:27.240> the<18:56:27.360> technology<18:56:27.656> works<18:56:28.256> a<18:56:28.800> lot<18:56:28.920> of 18:56:29.030 --> 18:56:29.040 align:start position:0% know how the technology works a lot of 18:56:29.040 --> 18:56:31.006 align:start position:0% know how the technology works a lot of other<18:56:29.160> devices<18:56:29.512> will<18:56:29.936> be<18:56:30.120> associating<18:56:30.656> with 18:56:31.006 --> 18:56:31.016 align:start position:0% other devices will be associating with 18:56:31.016 --> 18:56:32.814 align:start position:0% other devices will be associating with this<18:56:31.144> access<18:56:31.320> point<18:56:31.744> here<18:56:32.104> when<18:56:32.512> it<18:56:32.696> should 18:56:32.814 --> 18:56:32.824 align:start position:0% this access point here when it should 18:56:32.824 --> 18:56:34.310 align:start position:0% this access point here when it should have<18:56:32.936> actually<18:56:33.120> gone<18:56:33.296> off<18:56:33.480> to<18:56:33.656> the<18:56:33.832> corporate 18:56:34.310 --> 18:56:34.320 align:start position:0% have actually gone off to the corporate 18:56:34.320 --> 18:56:35.862 align:start position:0% have actually gone off to the corporate one 18:56:35.862 --> 18:56:35.872 align:start position:0% one 18:56:35.872 --> 18:56:37.670 align:start position:0% one you<18:56:36.296> mitigate<18:56:36.784> this<18:56:36.896> for<18:56:37.080> regular<18:56:37.376> site 18:56:37.670 --> 18:56:37.680 align:start position:0% you mitigate this for regular site 18:56:37.680 --> 18:56:39.286 align:start position:0% you mitigate this for regular site surveys<18:56:38.160> basically<18:56:38.576> you're<18:56:38.760> walking<18:56:38.936> around 18:56:39.286 --> 18:56:39.296 align:start position:0% surveys basically you're walking around 18:56:39.296 --> 18:56:42.950 align:start position:0% surveys basically you're walking around with<18:56:40.192> um<18:56:40.400> your<18:56:41.400> wireless<18:56:41.696> wireless<18:56:42.536> device 18:56:42.950 --> 18:56:42.960 align:start position:0% with um your wireless wireless device 18:56:42.960 --> 18:56:46.790 align:start position:0% with um your wireless wireless device checking<18:56:43.504> for<18:56:43.616> legitimate<18:56:44.464> devices 18:56:46.790 --> 18:56:46.800 align:start position:0% checking for legitimate devices 18:56:46.800 --> 18:56:49.494 align:start position:0% checking for legitimate devices uh<18:56:47.640> you<18:56:47.872> can<18:56:48.000> force<18:56:48.424> users<18:56:48.832> to<18:56:49.016> authenticate 18:56:49.494 --> 18:56:49.504 align:start position:0% uh you can force users to authenticate 18:56:49.504 --> 18:56:52.542 align:start position:0% uh you can force users to authenticate user<18:56:49.976> NATO<18:56:50.160> 2.1x 18:56:52.542 --> 18:56:52.552 align:start position:0% user NATO 2.1x 18:56:52.552 --> 18:56:55.070 align:start position:0% user NATO 2.1x uh<18:56:53.160> also<18:56:53.512> can<18:56:53.824> happen<18:56:53.936> if<18:56:54.240> you<18:56:54.360> enable<18:56:54.656> Wi-Fi 18:56:55.070 --> 18:56:55.080 align:start position:0% uh also can happen if you enable Wi-Fi 18:56:55.080 --> 18:56:58.070 align:start position:0% uh also can happen if you enable Wi-Fi sharing<18:56:55.552> on<18:56:55.800> your<18:56:56.040> phone<18:56:56.240> so<18:56:57.240> if<18:56:57.480> you're<18:56:57.656> stuck 18:56:58.070 --> 18:56:58.080 align:start position:0% sharing on your phone so if you're stuck 18:56:58.080 --> 18:56:59.990 align:start position:0% sharing on your phone so if you're stuck somewhere<18:56:58.496> you've<18:56:58.976> got<18:56:59.160> your<18:56:59.512> smartphone 18:56:59.990 --> 18:57:00.000 align:start position:0% somewhere you've got your smartphone 18:57:00.000 --> 18:57:01.734 align:start position:0% somewhere you've got your smartphone there's<18:57:00.784> a<18:57:00.960> little 18:57:01.734 --> 18:57:01.744 align:start position:0% there's a little 18:57:01.744 --> 18:57:03.470 align:start position:0% there's a little um app<18:57:02.160> in<18:57:02.400> there<18:57:02.576> where<18:57:02.760> you<18:57:02.872> can<18:57:03.000> let<18:57:03.240> the 18:57:03.470 --> 18:57:03.480 align:start position:0% um app in there where you can let the 18:57:03.480 --> 18:57:06.286 align:start position:0% um app in there where you can let the devices<18:57:03.896> say<18:57:04.320> for<18:57:04.440> example<18:57:04.744> your<18:57:05.104> laptop<18:57:05.512> if 18:57:06.286 --> 18:57:06.296 align:start position:0% devices say for example your laptop if 18:57:06.296 --> 18:57:09.230 align:start position:0% devices say for example your laptop if that<18:57:06.424> doesn't<18:57:06.600> have<18:57:07.016> a<18:57:07.552> capability<18:57:08.280> it<18:57:09.120> can 18:57:09.230 --> 18:57:09.240 align:start position:0% that doesn't have a capability it can 18:57:09.240 --> 18:57:12.046 align:start position:0% that doesn't have a capability it can actually<18:57:09.360> piggyback<18:57:09.960> onto<18:57:10.440> your 18:57:12.046 --> 18:57:12.056 align:start position:0% actually piggyback onto your 18:57:12.056 --> 18:57:14.390 align:start position:0% actually piggyback onto your um<18:57:12.176> phone<18:57:12.536> with<18:57:12.784> a<18:57:12.896> wireless<18:57:13.016> signal 18:57:14.390 --> 18:57:14.400 align:start position:0% um phone with a wireless signal 18:57:14.400 --> 18:57:16.846 align:start position:0% um phone with a wireless signal and<18:57:14.824> then<18:57:14.936> connect<18:57:15.176> to<18:57:15.424> the<18:57:15.600> network<18:57:15.856> so 18:57:16.846 --> 18:57:16.856 align:start position:0% and then connect to the network so 18:57:16.856 --> 18:57:18.710 align:start position:0% and then connect to the network so you've<18:57:16.976> got<18:57:17.040> to<18:57:17.160> be<18:57:17.280> careful<18:57:17.512> of<18:57:17.696> that 18:57:18.710 --> 18:57:18.720 align:start position:0% you've got to be careful of that 18:57:18.720 --> 18:57:22.182 align:start position:0% you've got to be careful of that Wireless<18:57:19.440> evil<18:57:20.104> twins<18:57:20.464> this<18:57:21.176> is<18:57:21.360> uh<18:57:21.720> configure 18:57:22.182 --> 18:57:22.192 align:start position:0% Wireless evil twins this is uh configure 18:57:22.192 --> 18:57:24.950 align:start position:0% Wireless evil twins this is uh configure an<18:57:22.376> external<18:57:22.800> access<18:57:23.040> point<18:57:23.512> to<18:57:24.296> behave<18:57:24.784> as 18:57:24.950 --> 18:57:24.960 align:start position:0% an external access point to behave as 18:57:24.960 --> 18:57:27.286 align:start position:0% an external access point to behave as The<18:57:25.080> Trusted<18:57:25.504> access<18:57:25.744> points 18:57:27.286 --> 18:57:27.296 align:start position:0% The Trusted access points 18:57:27.296 --> 18:57:32.926 align:start position:0% The Trusted access points it<18:57:27.832> used<18:57:28.144> the<18:57:28.376> same<18:57:28.496> SSID 18:57:32.926 --> 18:57:32.936 align:start position:0% 18:57:32.936 --> 18:57:36.046 align:start position:0% and<18:57:33.600> their<18:57:33.784> security<18:57:34.016> settings 18:57:36.046 --> 18:57:36.056 align:start position:0% and their security settings 18:57:36.056 --> 18:57:38.094 align:start position:0% and their security settings so<18:57:36.536> it'll<18:57:36.656> all<18:57:36.832> look<18:57:37.080> the<18:57:37.320> same 18:57:38.094 --> 18:57:38.104 align:start position:0% so it'll all look the same 18:57:38.104 --> 18:57:40.310 align:start position:0% so it'll all look the same and<18:57:38.576> the<18:57:38.696> user<18:57:39.056> connects<18:57:39.600> you<18:57:39.784> can<18:57:39.896> see<18:57:40.016> the 18:57:40.310 --> 18:57:40.320 align:start position:0% and the user connects you can see the 18:57:40.320 --> 18:57:42.110 align:start position:0% and the user connects you can see the the<18:57:40.552> legitimate<18:57:41.160> one<18:57:41.336> is<18:57:41.512> here<18:57:41.696> but<18:57:41.936> the 18:57:42.110 --> 18:57:42.120 align:start position:0% the legitimate one is here but the 18:57:42.120 --> 18:57:44.862 align:start position:0% the legitimate one is here but the signal<18:57:42.360> is<18:57:42.480> pretty<18:57:42.720> weak<18:57:43.144> the<18:57:43.744> signal<18:57:44.040> here<18:57:44.336> is 18:57:44.862 --> 18:57:44.872 align:start position:0% signal is pretty weak the signal here is 18:57:44.872 --> 18:57:47.390 align:start position:0% signal is pretty weak the signal here is much<18:57:45.120> stronger<18:57:45.600> so<18:57:46.256> you'll<18:57:46.680> more<18:57:47.160> likely 18:57:47.390 --> 18:57:47.400 align:start position:0% much stronger so you'll more likely 18:57:47.400 --> 18:57:49.926 align:start position:0% much stronger so you'll more likely connect<18:57:47.576> to<18:57:47.824> the<18:57:47.936> Rogue<18:57:48.296> access<18:57:48.424> point 18:57:49.926 --> 18:57:49.936 align:start position:0% connect to the Rogue access point 18:57:49.936 --> 18:57:53.270 align:start position:0% connect to the Rogue access point this<18:57:50.936> device<18:57:51.120> normally<18:57:51.720> will<18:57:52.440> have<18:57:52.680> a<18:57:52.920> quite<18:57:53.104> a 18:57:53.270 --> 18:57:53.280 align:start position:0% this device normally will have a quite a 18:57:53.280 --> 18:57:56.750 align:start position:0% this device normally will have a quite a strong<18:57:53.872> signal<18:57:54.360> on<18:57:54.600> purpose<18:57:55.016> so<18:57:55.504> it<18:57:56.040> is<18:57:56.400> chosen 18:57:56.750 --> 18:57:56.760 align:start position:0% strong signal on purpose so it is chosen 18:57:56.760 --> 18:57:58.670 align:start position:0% strong signal on purpose so it is chosen of<18:57:56.936> the<18:57:57.120> legitimate<18:57:57.656> one 18:57:58.670 --> 18:57:58.680 align:start position:0% of the legitimate one 18:57:58.680 --> 18:58:00.470 align:start position:0% of the legitimate one again<18:57:59.216> this<18:57:59.512> can<18:57:59.640> be<18:57:59.760> brought<18:57:59.936> in<18:58:00.176> by<18:58:00.296> Network 18:58:00.470 --> 18:58:00.480 align:start position:0% again this can be brought in by Network 18:58:00.480 --> 18:58:02.814 align:start position:0% again this can be brought in by Network users<18:58:01.080> innocently<18:58:01.800> or<18:58:02.336> it<18:58:02.464> can<18:58:02.576> be<18:58:02.696> done 18:58:02.814 --> 18:58:02.824 align:start position:0% users innocently or it can be done 18:58:02.824 --> 18:58:03.886 align:start position:0% users innocently or it can be done maliciously 18:58:03.886 --> 18:58:03.896 align:start position:0% maliciously 18:58:03.896 --> 18:58:10.182 align:start position:0% maliciously mitigate<18:58:04.680> with<18:58:04.920> https<18:58:05.824> or<18:58:06.424> VPN<18:58:06.960> tunnels 18:58:10.182 --> 18:58:10.192 align:start position:0% 18:58:10.192 --> 18:58:12.414 align:start position:0% while<18:58:10.616> driving<18:58:10.920> is<18:58:11.280> just<18:58:11.512> simply<18:58:11.824> this 18:58:12.414 --> 18:58:12.424 align:start position:0% while driving is just simply this 18:58:12.424 --> 18:58:13.846 align:start position:0% while driving is just simply this happened<18:58:12.656> when<18:58:12.896> Wireless<18:58:13.080> first<18:58:13.504> came<18:58:13.680> out 18:58:13.846 --> 18:58:13.856 align:start position:0% happened when Wireless first came out 18:58:13.856 --> 18:58:16.134 align:start position:0% happened when Wireless first came out and<18:58:14.040> nobody<18:58:14.336> had<18:58:14.576> security<18:58:14.824> or<18:58:15.360> it<18:58:15.536> was<18:58:15.720> just<18:58:15.960> a 18:58:16.134 --> 18:58:16.144 align:start position:0% and nobody had security or it was just a 18:58:16.144 --> 18:58:18.710 align:start position:0% and nobody had security or it was just a very<18:58:16.496> weak<18:58:16.800> security<18:58:17.056> people<18:58:18.056> drove<18:58:18.536> around 18:58:18.710 --> 18:58:18.720 align:start position:0% very weak security people drove around 18:58:18.720 --> 18:58:20.270 align:start position:0% very weak security people drove around trying<18:58:19.144> to<18:58:19.320> find<18:58:19.440> some<18:58:19.744> wireless<18:58:19.920> access 18:58:20.270 --> 18:58:20.280 align:start position:0% trying to find some wireless access 18:58:20.280 --> 18:58:22.606 align:start position:0% trying to find some wireless access somewhere<18:58:20.936> and 18:58:22.606 --> 18:58:22.616 align:start position:0% somewhere and 18:58:22.616 --> 18:58:23.150 align:start position:0% somewhere and um 18:58:23.150 --> 18:58:23.160 align:start position:0% um 18:58:23.160 --> 18:58:24.710 align:start position:0% um if<18:58:23.576> they<18:58:23.696> could<18:58:23.872> see<18:58:24.000> your<18:58:24.176> device<18:58:24.424> and 18:58:24.710 --> 18:58:24.720 align:start position:0% if they could see your device and 18:58:24.720 --> 18:58:27.414 align:start position:0% if they could see your device and connect<18:58:24.896> to<18:58:25.144> it<18:58:25.320> even<18:58:26.160> when<18:58:26.400> I<18:58:26.640> it<18:58:27.056> wasn't<18:58:27.240> too 18:58:27.414 --> 18:58:27.424 align:start position:0% connect to it even when I it wasn't too 18:58:27.424 --> 18:58:29.566 align:start position:0% connect to it even when I it wasn't too many<18:58:27.600> years<18:58:27.832> ago<18:58:28.080> and<18:58:28.440> my<18:58:28.680> my<18:58:28.920> internet<18:58:29.160> went 18:58:29.566 --> 18:58:29.576 align:start position:0% many years ago and my my internet went 18:58:29.576 --> 18:58:34.734 align:start position:0% many years ago and my my internet went down<18:58:29.936> and<18:58:30.784> I<18:58:31.376> um<18:58:31.376> I<18:58:31.976> could<18:58:32.104> see<18:58:32.216> on<18:58:32.400> my<18:58:32.640> wireless 18:58:34.734 --> 18:58:34.744 align:start position:0% down and I um I could see on my wireless 18:58:34.744 --> 18:58:38.030 align:start position:0% down and I um I could see on my wireless um<18:58:35.176> if<18:58:36.176> you<18:58:36.296> do<18:58:36.424> a<18:58:36.536> wireless<18:58:36.720> search<18:58:37.192> you'll 18:58:38.030 --> 18:58:38.040 align:start position:0% um if you do a wireless search you'll 18:58:38.040 --> 18:58:38.862 align:start position:0% um if you do a wireless search you'll see 18:58:38.862 --> 18:58:38.872 align:start position:0% see 18:58:38.872 --> 18:58:40.542 align:start position:0% see a<18:58:39.120> few<18:58:39.296> padlocks 18:58:40.542 --> 18:58:40.552 align:start position:0% a few padlocks 18:58:40.552 --> 18:58:44.326 align:start position:0% a few padlocks and<18:58:41.216> then<18:58:41.760> um<18:58:41.760> you'd<18:58:42.600> have<18:58:42.720> one<18:58:42.960> with<18:58:43.256> a<18:58:43.920> open 18:58:44.326 --> 18:58:44.336 align:start position:0% and then um you'd have one with a open 18:58:44.336 --> 18:58:46.542 align:start position:0% and then um you'd have one with a open padlock<18:58:44.872> and<18:58:45.656> you<18:58:45.784> can<18:58:45.832> just<18:58:46.016> you<18:58:46.320> could 18:58:46.542 --> 18:58:46.552 align:start position:0% padlock and you can just you could 18:58:46.552 --> 18:58:49.006 align:start position:0% padlock and you can just you could connect<18:58:46.800> to<18:58:47.040> that<18:58:47.280> so<18:58:48.056> you<18:58:48.360> see<18:58:48.536> it<18:58:48.656> less<18:58:48.832> now 18:58:49.006 --> 18:58:49.016 align:start position:0% connect to that so you see it less now 18:58:49.016 --> 18:58:50.390 align:start position:0% connect to that so you see it less now because<18:58:49.256> most<18:58:49.616> of<18:58:49.744> them<18:58:49.856> are<18:58:49.976> configured 18:58:50.390 --> 18:58:50.400 align:start position:0% because most of them are configured 18:58:50.400 --> 18:58:53.814 align:start position:0% because most of them are configured quite<18:58:50.640> easily<18:58:50.936> for<18:58:51.240> security 18:58:53.814 --> 18:58:53.824 align:start position:0% 18:58:53.824 --> 18:58:56.094 align:start position:0% fishing<18:58:54.424> email<18:58:54.784> sent<18:58:55.080> which<18:58:55.376> is<18:58:55.504> looks 18:58:56.094 --> 18:58:56.104 align:start position:0% fishing email sent which is looks 18:58:56.104 --> 18:58:58.606 align:start position:0% fishing email sent which is looks legitimate<18:58:56.872> usually<18:58:57.360> appears<18:58:57.896> to<18:58:58.144> be<18:58:58.192> from<18:58:58.496> an 18:58:58.606 --> 18:58:58.616 align:start position:0% legitimate usually appears to be from an 18:58:58.616 --> 18:59:00.950 align:start position:0% legitimate usually appears to be from an official<18:58:58.976> website<18:58:59.464> and<18:59:00.240> it<18:59:00.360> asks<18:59:00.720> you<18:59:00.720> to 18:59:00.950 --> 18:59:00.960 align:start position:0% official website and it asks you to 18:59:00.960 --> 18:59:04.542 align:start position:0% official website and it asks you to click<18:59:01.192> on<18:59:01.440> the<18:59:01.680> URL<18:59:02.216> so<18:59:02.760> you<18:59:02.936> click<18:59:03.176> here<18:59:03.552> the 18:59:04.542 --> 18:59:04.552 align:start position:0% click on the URL so you click here the 18:59:04.552 --> 18:59:07.310 align:start position:0% click on the URL so you click here the sort<18:59:04.744> of<18:59:04.800> things<18:59:04.976> I'll<18:59:05.280> see<18:59:05.512> are 18:59:07.310 --> 18:59:07.320 align:start position:0% sort of things I'll see are 18:59:07.320 --> 18:59:11.094 align:start position:0% sort of things I'll see are it'll<18:59:08.104> say<18:59:08.280> Amazon<18:59:08.600> or<18:59:09.896> um 18:59:11.094 --> 18:59:11.104 align:start position:0% it'll say Amazon or um 18:59:11.104 --> 18:59:13.790 align:start position:0% it'll say Amazon or um text<18:59:11.760> message 18:59:13.790 --> 18:59:13.800 align:start position:0% text message 18:59:13.800 --> 18:59:15.886 align:start position:0% text message and<18:59:14.280> even<18:59:14.464> smarter<18:59:15.000> people<18:59:15.120> have<18:59:15.480> been<18:59:15.656> caught 18:59:15.886 --> 18:59:15.896 align:start position:0% and even smarter people have been caught 18:59:15.896 --> 18:59:18.646 align:start position:0% and even smarter people have been caught out<18:59:16.256> say<18:59:16.976> for<18:59:17.216> example<18:59:17.512> if<18:59:18.176> you're<18:59:18.296> like<18:59:18.480> me 18:59:18.646 --> 18:59:18.656 align:start position:0% out say for example if you're like me 18:59:18.656 --> 18:59:21.110 align:start position:0% out say for example if you're like me maybe<18:59:19.016> every<18:59:19.320> three<18:59:19.616> days<18:59:20.040> you've<18:59:20.824> got<18:59:20.936> an 18:59:21.110 --> 18:59:21.120 align:start position:0% maybe every three days you've got an 18:59:21.120 --> 18:59:23.926 align:start position:0% maybe every three days you've got an Amazon<18:59:21.240> delivery<18:59:21.832> coming<18:59:22.080> or<18:59:23.216> um<18:59:23.216> or 18:59:23.926 --> 18:59:23.936 align:start position:0% Amazon delivery coming or um or 18:59:23.936 --> 18:59:26.326 align:start position:0% Amazon delivery coming or um or something<18:59:24.176> from<18:59:24.720> eBay<18:59:24.832> so<18:59:25.616> if<18:59:25.800> you're<18:59:25.920> busy 18:59:26.326 --> 18:59:26.336 align:start position:0% something from eBay so if you're busy 18:59:26.336 --> 18:59:28.366 align:start position:0% something from eBay so if you're busy you'll<18:59:27.000> see<18:59:27.120> it<18:59:27.240> I<18:59:27.360> think<18:59:27.480> oh<18:59:27.656> no<18:59:27.784> I've<18:59:28.144> missed 18:59:28.366 --> 18:59:28.376 align:start position:0% you'll see it I think oh no I've missed 18:59:28.376 --> 18:59:30.646 align:start position:0% you'll see it I think oh no I've missed my<18:59:28.440> Amazon<18:59:28.552> delivery<18:59:29.280> too<18:59:30.000> late<18:59:30.176> you've 18:59:30.646 --> 18:59:30.656 align:start position:0% my Amazon delivery too late you've 18:59:30.656 --> 18:59:32.566 align:start position:0% my Amazon delivery too late you've clicked<18:59:30.960> on<18:59:31.080> it<18:59:31.256> and<18:59:31.744> um<18:59:31.744> the<18:59:31.976> damage<18:59:32.216> has<18:59:32.400> been 18:59:32.566 --> 18:59:32.576 align:start position:0% clicked on it and um the damage has been 18:59:32.576 --> 18:59:33.526 align:start position:0% clicked on it and um the damage has been done 18:59:33.526 --> 18:59:33.536 align:start position:0% done 18:59:33.536 --> 18:59:36.350 align:start position:0% done fishing<18:59:34.256> can<18:59:34.376> be<18:59:34.496> phone<18:59:34.680> based<18:59:35.104> also<18:59:35.464> you<18:59:36.120> come 18:59:36.350 --> 18:59:36.360 align:start position:0% fishing can be phone based also you come 18:59:36.360 --> 18:59:38.686 align:start position:0% fishing can be phone based also you come to<18:59:36.536> this<18:59:36.720> with<18:59:36.896> email<18:59:37.144> security<18:59:37.504> systems<18:59:38.280> spun 18:59:38.686 --> 18:59:38.696 align:start position:0% to this with email security systems spun 18:59:38.696 --> 18:59:41.814 align:start position:0% to this with email security systems spun viruses<18:59:39.296> fishing<18:59:40.016> Etc 18:59:41.814 --> 18:59:41.824 align:start position:0% viruses fishing Etc 18:59:41.824 --> 18:59:44.094 align:start position:0% viruses fishing Etc ransomware<18:59:42.784> has<18:59:43.016> really<18:59:43.320> been<18:59:43.552> in<18:59:43.744> the<18:59:43.920> news 18:59:44.094 --> 18:59:44.104 align:start position:0% ransomware has really been in the news 18:59:44.104 --> 18:59:46.790 align:start position:0% ransomware has really been in the news lately<18:59:44.696> because<18:59:45.536> even<18:59:45.832> the<18:59:46.144> law<18:59:46.320> enforcement 18:59:46.790 --> 18:59:46.800 align:start position:0% lately because even the law enforcement 18:59:46.800 --> 18:59:48.590 align:start position:0% lately because even the law enforcement agencies<18:59:47.216> have<18:59:47.464> been<18:59:47.576> caught<18:59:47.824> it's<18:59:48.120> taken<18:59:48.480> out 18:59:48.590 --> 18:59:48.600 align:start position:0% agencies have been caught it's taken out 18:59:48.600 --> 18:59:51.350 align:start position:0% agencies have been caught it's taken out large<18:59:48.976> areas<18:59:49.976> of<18:59:50.512> um<18:59:50.512> the<18:59:50.936> National<18:59:51.056> Health 18:59:51.350 --> 18:59:51.360 align:start position:0% large areas of um the National Health 18:59:51.360 --> 18:59:53.030 align:start position:0% large areas of um the National Health Service<18:59:51.656> in<18:59:51.960> the<18:59:52.144> UK 18:59:53.030 --> 18:59:53.040 align:start position:0% Service in the UK 18:59:53.040 --> 18:59:55.910 align:start position:0% Service in the UK it<18:59:53.576> limits<18:59:53.936> all<18:59:54.176> of<18:59:54.360> some<18:59:54.536> system<18:59:54.720> access<18:59:55.080> and 18:59:55.910 --> 18:59:55.920 align:start position:0% it limits all of some system access and 18:59:55.920 --> 18:59:57.646 align:start position:0% it limits all of some system access and it<18:59:56.040> locks<18:59:56.336> your<18:59:56.464> screen<18:59:56.696> as<18:59:57.056> it<18:59:57.240> does<18:59:57.360> here 18:59:57.646 --> 18:59:57.656 align:start position:0% it locks your screen as it does here 18:59:57.656 --> 19:00:03.046 align:start position:0% it locks your screen as it does here until<18:59:58.440> you've<18:59:59.216> paid<18:59:59.400> money<18:59:59.832> to<19:00:00.832> the<19:00:01.192> extorters 19:00:03.046 --> 19:00:03.056 align:start position:0% until you've paid money to the extorters 19:00:03.056 --> 19:00:05.326 align:start position:0% until you've paid money to the extorters offers<19:00:03.720> threatens<19:00:04.080> to<19:00:04.320> publish<19:00:04.552> your<19:00:04.800> data 19:00:05.326 --> 19:00:05.336 align:start position:0% offers threatens to publish your data 19:00:05.336 --> 19:00:07.606 align:start position:0% offers threatens to publish your data and<19:00:05.640> if<19:00:05.824> in<19:00:06.176> the<19:00:06.360> case<19:00:06.480> of<19:00:06.832> uh 19:00:07.606 --> 19:00:07.616 align:start position:0% and if in the case of uh 19:00:07.616 --> 19:00:09.470 align:start position:0% and if in the case of uh I<19:00:08.040> can't<19:00:08.160> remember<19:00:08.336> what<19:00:08.640> it<19:00:09.000> was<19:00:09.176> some<19:00:09.360> sort 19:00:09.470 --> 19:00:09.480 align:start position:0% I can't remember what it was some sort 19:00:09.480 --> 19:00:11.270 align:start position:0% I can't remember what it was some sort of<19:00:09.600> police<19:00:09.784> department<19:00:10.080> anyway<19:00:10.616> but<19:00:11.040> it 19:00:11.270 --> 19:00:11.280 align:start position:0% of police department anyway but it 19:00:11.280 --> 19:00:12.710 align:start position:0% of police department anyway but it accessed<19:00:11.760> all<19:00:11.872> of<19:00:12.056> their<19:00:12.176> systems<19:00:12.600> somebody 19:00:12.710 --> 19:00:12.720 align:start position:0% accessed all of their systems somebody 19:00:12.720 --> 19:00:16.670 align:start position:0% accessed all of their systems somebody downloaded<19:00:13.440> or<19:00:13.920> somebody<19:00:14.160> got<19:00:14.512> an<19:00:14.760> email<19:00:15.680> uh 19:00:16.670 --> 19:00:16.680 align:start position:0% downloaded or somebody got an email uh 19:00:16.680 --> 19:00:18.414 align:start position:0% downloaded or somebody got an email uh opened<19:00:17.576> it<19:00:17.696> up 19:00:18.414 --> 19:00:18.424 align:start position:0% opened it up 19:00:18.424 --> 19:00:21.886 align:start position:0% opened it up and<19:00:19.744> um<19:00:19.800> they<19:00:20.640> downloaded<19:00:21.056> the<19:00:21.240> software<19:00:21.600> and 19:00:21.886 --> 19:00:21.896 align:start position:0% and um they downloaded the software and 19:00:21.896 --> 19:00:23.814 align:start position:0% and um they downloaded the software and it<19:00:22.192> spread<19:00:22.800> through<19:00:22.920> all<19:00:23.040> the<19:00:23.216> all<19:00:23.576> the 19:00:23.814 --> 19:00:23.824 align:start position:0% it spread through all the all the 19:00:23.824 --> 19:00:25.246 align:start position:0% it spread through all the all the devices 19:00:25.246 --> 19:00:25.256 align:start position:0% devices 19:00:25.256 --> 19:00:27.350 align:start position:0% devices often<19:00:25.856> uses<19:00:26.104> cryptocurrencies<19:00:26.936> for<19:00:27.120> payment 19:00:27.350 --> 19:00:27.360 align:start position:0% often uses cryptocurrencies for payment 19:00:27.360 --> 19:00:30.230 align:start position:0% often uses cryptocurrencies for payment so<19:00:27.784> it's<19:00:27.896> hard<19:00:28.192> to<19:00:28.440> trace<19:00:28.976> the<19:00:29.216> money 19:00:30.230 --> 19:00:30.240 align:start position:0% so it's hard to trace the money 19:00:30.240 --> 19:00:33.886 align:start position:0% so it's hard to trace the money I<19:00:30.536> often<19:00:30.832> uses<19:00:31.144> Trojans<19:00:31.680> uh<19:00:32.216> wannacry<19:00:32.760> the<19:00:33.600> uh 19:00:33.886 --> 19:00:33.896 align:start position:0% I often uses Trojans uh wannacry the uh 19:00:33.896 --> 19:00:36.046 align:start position:0% I often uses Trojans uh wannacry the uh one<19:00:34.192> of<19:00:34.320> the<19:00:34.376> latest<19:00:34.552> ransomware 19:00:36.046 --> 19:00:36.056 align:start position:0% one of the latest ransomware 19:00:36.056 --> 19:00:38.030 align:start position:0% one of the latest ransomware that<19:00:36.600> uh<19:00:36.832> malware 19:00:38.030 --> 19:00:38.040 align:start position:0% that uh malware 19:00:38.040 --> 19:00:40.246 align:start position:0% that uh malware um<19:00:38.160> software<19:00:39.120> packages<19:00:39.600> that<19:00:39.832> came<19:00:40.080> out 19:00:40.246 --> 19:00:40.256 align:start position:0% um software packages that came out 19:00:40.256 --> 19:00:42.166 align:start position:0% um software packages that came out automatically<19:00:41.160> transferred<19:00:41.760> it<19:00:41.824> didn't<19:00:42.000> use 19:00:42.166 --> 19:00:42.176 align:start position:0% automatically transferred it didn't use 19:00:42.176 --> 19:00:43.846 align:start position:0% automatically transferred it didn't use a<19:00:42.360> Trojan 19:00:43.846 --> 19:00:43.856 align:start position:0% a Trojan 19:00:43.856 --> 19:00:45.822 align:start position:0% a Trojan DNS<19:00:44.640> poisoning<19:00:45.176> we've<19:00:45.424> already<19:00:45.536> learned 19:00:45.822 --> 19:00:45.832 align:start position:0% DNS poisoning we've already learned 19:00:45.832 --> 19:00:50.502 align:start position:0% DNS poisoning we've already learned about<19:00:46.016> DNS<19:00:46.616> this<19:00:47.336> is<19:00:47.640> a<19:00:48.056> fake<19:00:48.536> DNS<19:00:49.144> cache<19:00:50.104> entry 19:00:50.502 --> 19:00:50.512 align:start position:0% about DNS this is a fake DNS cache entry 19:00:50.512 --> 19:00:53.566 align:start position:0% about DNS this is a fake DNS cache entry it<19:00:51.424> cropsy<19:00:51.960> data<19:00:52.440> inserted<19:00:52.920> into<19:00:53.104> your<19:00:53.336> system 19:00:53.566 --> 19:00:53.576 align:start position:0% it cropsy data inserted into your system 19:00:53.576 --> 19:00:56.862 align:start position:0% it cropsy data inserted into your system and<19:00:54.536> the<19:00:54.656> name<19:00:54.832> server<19:00:55.320> returns<19:00:56.216> a<19:00:56.464> false 19:00:56.862 --> 19:00:56.872 align:start position:0% and the name server returns a false 19:00:56.872 --> 19:00:59.454 align:start position:0% and the name server returns a false result<19:00:57.056> so<19:00:57.656> you'll<19:00:57.784> do<19:00:58.016> a<19:00:58.144> DNS<19:00:58.552> lookup<19:00:58.976> it<19:00:59.216> goes 19:00:59.454 --> 19:00:59.464 align:start position:0% result so you'll do a DNS lookup it goes 19:00:59.464 --> 19:01:01.366 align:start position:0% result so you'll do a DNS lookup it goes to<19:00:59.512> your<19:00:59.640> DNS<19:01:00.120> server<19:01:00.536> but<19:01:01.080> for<19:01:01.192> whatever 19:01:01.366 --> 19:01:01.376 align:start position:0% to your DNS server but for whatever 19:01:01.376 --> 19:01:03.526 align:start position:0% to your DNS server but for whatever reason<19:01:01.744> this<19:01:02.640> attacker<19:01:03.056> has<19:01:03.176> somehow 19:01:03.526 --> 19:01:03.536 align:start position:0% reason this attacker has somehow 19:01:03.536 --> 19:01:05.862 align:start position:0% reason this attacker has somehow injected<19:01:04.080> this<19:01:04.256> fake<19:01:04.552> entry<19:01:04.920> and<19:01:05.512> instead<19:01:05.824> of 19:01:05.862 --> 19:01:05.872 align:start position:0% injected this fake entry and instead of 19:01:05.872 --> 19:01:08.326 align:start position:0% injected this fake entry and instead of going<19:01:06.056> off<19:01:06.240> to<19:01:06.424> the<19:01:06.600> real<19:01:06.784> server<19:01:07.320> here<19:01:07.616> it 19:01:08.326 --> 19:01:08.336 align:start position:0% going off to the real server here it 19:01:08.336 --> 19:01:11.270 align:start position:0% going off to the real server here it queries<19:01:08.696> the<19:01:08.936> fake<19:01:09.360> one<19:01:09.480> and<19:01:10.144> it<19:01:10.320> just<19:01:10.552> for<19:01:11.104> all 19:01:11.270 --> 19:01:11.280 align:start position:0% queries the fake one and it just for all 19:01:11.280 --> 19:01:13.670 align:start position:0% queries the fake one and it just for all intents<19:01:11.760> and<19:01:11.824> purposes<19:01:12.240> to<19:01:13.016> you<19:01:13.192> looks<19:01:13.552> like 19:01:13.670 --> 19:01:13.680 align:start position:0% intents and purposes to you looks like 19:01:13.680 --> 19:01:16.790 align:start position:0% intents and purposes to you looks like you're<19:01:13.856> actually<19:01:14.040> on<19:01:14.216> the<19:01:14.400> correct<19:01:14.640> site 19:01:16.790 --> 19:01:16.800 align:start position:0% you're actually on the correct site 19:01:16.800 --> 19:01:18.414 align:start position:0% you're actually on the correct site obviously<19:01:17.512> then<19:01:17.696> it'll<19:01:18.056> try<19:01:18.176> and<19:01:18.296> get 19:01:18.414 --> 19:01:18.424 align:start position:0% obviously then it'll try and get 19:01:18.424 --> 19:01:20.270 align:start position:0% obviously then it'll try and get passwords<19:01:19.016> usernames<19:01:19.616> or<19:01:19.800> credit<19:01:20.040> card 19:01:20.270 --> 19:01:20.280 align:start position:0% passwords usernames or credit card 19:01:20.280 --> 19:01:23.150 align:start position:0% passwords usernames or credit card information<19:01:20.896> and<19:01:21.896> again<19:01:22.144> this<19:01:22.496> false<19:01:22.856> entry 19:01:23.150 --> 19:01:23.160 align:start position:0% information and again this false entry 19:01:23.160 --> 19:01:25.430 align:start position:0% information and again this false entry here<19:01:23.400> if<19:01:23.576> you've<19:01:23.760> got<19:01:23.872> a<19:01:24.000> DNS<19:01:24.360> server<19:01:24.784> it<19:01:25.256> can 19:01:25.430 --> 19:01:25.440 align:start position:0% here if you've got a DNS server it can 19:01:25.440 --> 19:01:28.134 align:start position:0% here if you've got a DNS server it can actually<19:01:25.616> propagate<19:01:26.336> within<19:01:27.296> your<19:01:27.656> depending 19:01:28.134 --> 19:01:28.144 align:start position:0% actually propagate within your depending 19:01:28.144 --> 19:01:29.990 align:start position:0% actually propagate within your depending on<19:01:28.256> the<19:01:28.440> authority<19:01:28.800> of<19:01:28.976> This<19:01:29.104> Server<19:01:29.464> it'll 19:01:29.990 --> 19:01:30.000 align:start position:0% on the authority of This Server it'll 19:01:30.000 --> 19:01:33.110 align:start position:0% on the authority of This Server it'll propagate<19:01:30.480> to<19:01:30.720> other<19:01:31.080> servers 19:01:33.110 --> 19:01:33.120 align:start position:0% propagate to other servers 19:01:33.120 --> 19:01:35.990 align:start position:0% propagate to other servers up<19:01:33.656> poisoning 19:01:35.990 --> 19:01:36.000 align:start position:0% up poisoning 19:01:36.000 --> 19:01:38.814 align:start position:0% up poisoning requires<19:01:36.896> the<19:01:37.256> attacker<19:01:38.104> to<19:01:38.280> have<19:01:38.464> access<19:01:38.576> to 19:01:38.814 --> 19:01:38.824 align:start position:0% requires the attacker to have access to 19:01:38.824 --> 19:01:40.606 align:start position:0% requires the attacker to have access to the<19:01:39.000> victim's<19:01:39.424> local<19:01:39.600> area<19:01:39.832> network<19:01:40.192> again 19:01:40.606 --> 19:01:40.616 align:start position:0% the victim's local area network again 19:01:40.616 --> 19:01:43.070 align:start position:0% the victim's local area network again this<19:01:40.920> could<19:01:41.104> be<19:01:41.216> a<19:01:41.400> contractor<19:01:41.872> or<19:01:42.832> somebody 19:01:43.070 --> 19:01:43.080 align:start position:0% this could be a contractor or somebody 19:01:43.080 --> 19:01:46.486 align:start position:0% this could be a contractor or somebody who's<19:01:43.680> managed<19:01:44.040> to<19:01:44.160> get<19:01:44.936> in<19:01:45.120> somehow<19:01:46.016> it 19:01:46.486 --> 19:01:46.496 align:start position:0% who's managed to get in somehow it 19:01:46.496 --> 19:01:47.862 align:start position:0% who's managed to get in somehow it provides<19:01:46.800> a<19:01:46.920> host<19:01:47.040> of<19:01:47.216> the<19:01:47.400> wrong<19:01:47.464> Mac<19:01:47.640> address 19:01:47.862 --> 19:01:47.872 align:start position:0% provides a host of the wrong Mac address 19:01:47.872 --> 19:01:52.006 align:start position:0% provides a host of the wrong Mac address for<19:01:48.240> hosts<19:01:48.832> the<19:01:49.320> host<19:01:49.552> IP<19:01:49.920> address<19:01:50.160> so 19:01:52.006 --> 19:01:52.016 align:start position:0% for hosts the host IP address so 19:01:52.016 --> 19:01:53.630 align:start position:0% for hosts the host IP address so um if<19:01:52.256> we<19:01:52.440> go<19:01:52.552> down<19:01:52.680> here<19:01:52.920> this<19:01:53.216> host<19:01:53.336> is 19:01:53.630 --> 19:01:53.640 align:start position:0% um if we go down here this host is 19:01:53.640 --> 19:01:55.846 align:start position:0% um if we go down here this host is looking<19:01:53.824> for<19:01:54.120> the<19:01:54.424> you<19:01:55.192> can't<19:01:55.320> say<19:01:55.504> it<19:01:55.616> can't 19:01:55.846 --> 19:01:55.856 align:start position:0% looking for the you can't say it can't 19:01:55.856 --> 19:01:57.526 align:start position:0% looking for the you can't say it can't encapsulate<19:01:56.400> the<19:01:56.576> packet<19:01:56.936> as<19:01:57.240> we<19:01:57.424> already 19:01:57.526 --> 19:01:57.536 align:start position:0% encapsulate the packet as we already 19:01:57.536 --> 19:02:01.734 align:start position:0% encapsulate the packet as we already know<19:01:58.040> until<19:01:59.040> it<19:01:59.512> knows<19:01:59.872> the<19:02:00.176> MAC<19:02:00.960> address<19:02:01.192> so 19:02:01.734 --> 19:02:01.744 align:start position:0% know until it knows the MAC address so 19:02:01.744 --> 19:02:04.790 align:start position:0% know until it knows the MAC address so there's<19:02:02.160> a<19:02:02.336> field<19:02:02.464> here<19:02:02.760> for<19:02:03.056> layer<19:02:03.480> three<19:02:03.896> and 19:02:04.790 --> 19:02:04.800 align:start position:0% there's a field here for layer three and 19:02:04.800 --> 19:02:07.454 align:start position:0% there's a field here for layer three and then<19:02:04.976> but<19:02:05.280> for<19:02:05.576> Layer<19:02:05.936> Two<19:02:06.120> in<19:02:06.600> order<19:02:06.720> to<19:02:06.896> send 19:02:07.454 --> 19:02:07.464 align:start position:0% then but for Layer Two in order to send 19:02:07.464 --> 19:02:11.150 align:start position:0% then but for Layer Two in order to send the<19:02:08.464> packet<19:02:08.872> out<19:02:09.056> it<19:02:09.360> needs<19:02:09.600> to<19:02:09.720> know<19:02:09.832> the<19:02:10.080> Mac 19:02:11.150 --> 19:02:11.160 align:start position:0% the packet out it needs to know the Mac 19:02:11.160 --> 19:02:14.206 align:start position:0% the packet out it needs to know the Mac and<19:02:12.120> if<19:02:12.536> it's<19:02:12.720> got<19:02:12.896> a<19:02:13.080> the<19:02:13.256> false<19:02:13.680> entry<19:02:14.040> here 19:02:14.206 --> 19:02:14.216 align:start position:0% and if it's got a the false entry here 19:02:14.216 --> 19:02:16.134 align:start position:0% and if it's got a the false entry here from<19:02:14.512> the<19:02:14.640> attacker<19:02:15.176> then<19:02:15.600> it<19:02:15.720> will<19:02:15.832> send<19:02:16.016> it 19:02:16.134 --> 19:02:16.144 align:start position:0% from the attacker then it will send it 19:02:16.144 --> 19:02:18.886 align:start position:0% from the attacker then it will send it to<19:02:16.320> the<19:02:16.496> wrong<19:02:16.616> host<19:02:16.976> it'll<19:02:17.400> send<19:02:17.512> it<19:02:17.696> to<19:02:17.936> here 19:02:18.886 --> 19:02:18.896 align:start position:0% to the wrong host it'll send it to here 19:02:18.896 --> 19:02:22.006 align:start position:0% to the wrong host it'll send it to here instead<19:02:19.616> of<19:02:19.680> here<19:02:19.976> or<19:02:20.216> vice<19:02:20.512> versa 19:02:22.006 --> 19:02:22.016 align:start position:0% instead of here or vice versa 19:02:22.016 --> 19:02:24.822 align:start position:0% instead of here or vice versa you<19:02:22.920> combat<19:02:23.576> this<19:02:23.760> with<19:02:24.000> Dynamic<19:02:24.480> harp 19:02:24.822 --> 19:02:24.832 align:start position:0% you combat this with Dynamic harp 19:02:24.832 --> 19:02:27.230 align:start position:0% you combat this with Dynamic harp inspection<19:02:25.192> which<19:02:25.744> is<19:02:25.920> you<19:02:26.512> will<19:02:26.640> enable<19:02:26.936> this 19:02:27.230 --> 19:02:27.240 align:start position:0% inspection which is you will enable this 19:02:27.240 --> 19:02:28.966 align:start position:0% inspection which is you will enable this on<19:02:27.600> switches 19:02:28.966 --> 19:02:28.976 align:start position:0% on switches 19:02:28.976 --> 19:02:33.286 align:start position:0% on switches our<19:02:29.576> and<19:02:29.872> DHCP<19:02:30.720> snooping 19:02:33.286 --> 19:02:33.296 align:start position:0% our and DHCP snooping 19:02:33.296 --> 19:02:34.670 align:start position:0% our and DHCP snooping there's<19:02:33.784> a<19:02:33.896> lot<19:02:34.016> of<19:02:34.144> different<19:02:34.256> type<19:02:34.496> of 19:02:34.670 --> 19:02:34.680 align:start position:0% there's a lot of different type of 19:02:34.680 --> 19:02:37.606 align:start position:0% there's a lot of different type of spoofing<19:02:35.336> when<19:02:35.640> it<19:02:35.760> comes<19:02:36.000> to<19:02:36.360> hacking<19:02:36.896> this 19:02:37.606 --> 19:02:37.616 align:start position:0% spoofing when it comes to hacking this 19:02:37.616 --> 19:02:39.414 align:start position:0% spoofing when it comes to hacking this is<19:02:37.744> pretending<19:02:38.216> to<19:02:38.336> be<19:02:38.464> someone<19:02:38.760> or<19:02:39.240> something 19:02:39.414 --> 19:02:39.424 align:start position:0% is pretending to be someone or something 19:02:39.424 --> 19:02:40.910 align:start position:0% is pretending to be someone or something you<19:02:39.784> want 19:02:40.910 --> 19:02:40.920 align:start position:0% you want 19:02:40.920 --> 19:02:43.070 align:start position:0% you want and<19:02:41.280> one<19:02:41.512> type<19:02:41.696> of<19:02:41.824> spoofing<19:02:42.240> is<19:02:42.360> DHCP 19:02:43.070 --> 19:02:43.080 align:start position:0% and one type of spoofing is DHCP 19:02:43.080 --> 19:02:46.134 align:start position:0% and one type of spoofing is DHCP spoofing<19:02:43.744> the<19:02:44.336> idea<19:02:44.640> is<19:02:44.872> the<19:02:45.424> software 19:02:46.134 --> 19:02:46.144 align:start position:0% spoofing the idea is the software 19:02:46.144 --> 19:02:48.774 align:start position:0% spoofing the idea is the software exhausts<19:02:46.800> the<19:02:46.976> pool<19:02:47.160> of<19:02:47.400> addresses<19:02:47.936> so<19:02:48.536> you'll 19:02:48.774 --> 19:02:48.784 align:start position:0% exhausts the pool of addresses so you'll 19:02:48.784 --> 19:02:50.566 align:start position:0% exhausts the pool of addresses so you'll have<19:02:48.960> a<19:02:49.080> pool<19:02:49.256> of<19:02:49.552> say 19:02:50.566 --> 19:02:50.576 align:start position:0% have a pool of say 19:02:50.576 --> 19:02:54.166 align:start position:0% have a pool of say 10<19:02:51.480> 000<19:02:51.536> addresses<19:02:52.192> and<19:02:52.920> it<19:02:53.104> will<19:02:53.216> spoof<19:02:53.640> keep 19:02:54.166 --> 19:02:54.176 align:start position:0% 10 000 addresses and it will spoof keep 19:02:54.176 --> 19:02:56.990 align:start position:0% 10 000 addresses and it will spoof keep requesting<19:02:55.104> the<19:02:56.104> addresses<19:02:56.760> until 19:02:56.990 --> 19:02:57.000 align:start position:0% requesting the addresses until 19:02:57.000 --> 19:02:59.862 align:start position:0% requesting the addresses until eventually<19:02:57.600> there's<19:02:58.552> zero<19:02:58.976> left<19:02:59.160> at<19:02:59.640> which 19:02:59.862 --> 19:02:59.872 align:start position:0% eventually there's zero left at which 19:02:59.872 --> 19:03:02.814 align:start position:0% eventually there's zero left at which point<19:03:00.056> in<19:03:00.240> the<19:03:00.360> DHCP<19:03:01.256> server<19:03:01.680> can't<19:03:02.336> allocate 19:03:02.814 --> 19:03:02.824 align:start position:0% point in the DHCP server can't allocate 19:03:02.824 --> 19:03:04.182 align:start position:0% point in the DHCP server can't allocate information<19:03:03.056> and<19:03:03.536> then<19:03:03.656> hosts<19:03:03.960> on<19:03:04.080> your 19:03:04.182 --> 19:03:04.192 align:start position:0% information and then hosts on your 19:03:04.192 --> 19:03:07.006 align:start position:0% information and then hosts on your network<19:03:04.376> can't<19:03:04.976> join<19:03:05.336> the<19:03:05.464> network 19:03:07.006 --> 19:03:07.016 align:start position:0% network can't join the network 19:03:07.016 --> 19:03:10.926 align:start position:0% network can't join the network uh<19:03:07.744> the<19:03:08.104> Mac<19:03:08.600> impersonates<19:03:09.600> house<19:03:09.960> or<19:03:10.320> device 19:03:10.926 --> 19:03:10.936 align:start position:0% uh the Mac impersonates house or device 19:03:10.936 --> 19:03:14.990 align:start position:0% uh the Mac impersonates house or device on<19:03:11.936> Two<19:03:12.360> Hosts<19:03:12.720> on<19:03:12.832> one<19:03:13.016> switch<19:03:13.320> Port<19:03:13.696> so<19:03:14.696> this 19:03:14.990 --> 19:03:15.000 align:start position:0% on Two Hosts on one switch Port so this 19:03:15.000 --> 19:03:17.270 align:start position:0% on Two Hosts on one switch Port so this is<19:03:15.120> actually<19:03:15.480> poisoning<19:03:16.192> it<19:03:16.376> looks<19:03:16.616> like<19:03:16.744> the 19:03:17.270 --> 19:03:17.280 align:start position:0% is actually poisoning it looks like the 19:03:17.280 --> 19:03:19.910 align:start position:0% is actually poisoning it looks like the port<19:03:17.824> on<19:03:18.120> the<19:03:18.240> switch<19:03:18.424> here<19:03:18.784> it<19:03:19.552> should<19:03:19.800> have 19:03:19.910 --> 19:03:19.920 align:start position:0% port on the switch here it should have 19:03:19.920 --> 19:03:22.366 align:start position:0% port on the switch here it should have one<19:03:20.160> Mac<19:03:20.336> address<19:03:20.576> per<19:03:21.056> port 19:03:22.366 --> 19:03:22.376 align:start position:0% one Mac address per port 19:03:22.376 --> 19:03:23.566 align:start position:0% one Mac address per port but 19:03:23.566 --> 19:03:23.576 align:start position:0% but 19:03:23.576 --> 19:03:26.990 align:start position:0% but it's<19:03:24.120> got<19:03:24.424> two<19:03:24.832> associated<19:03:25.616> with<19:03:26.040> the<19:03:26.280> uh<19:03:26.576> Port 19:03:26.990 --> 19:03:27.000 align:start position:0% it's got two associated with the uh Port 19:03:27.000 --> 19:03:28.846 align:start position:0% it's got two associated with the uh Port which<19:03:28.192> um 19:03:28.846 --> 19:03:28.856 align:start position:0% which um 19:03:28.856 --> 19:03:31.790 align:start position:0% which um it<19:03:29.464> can<19:03:29.576> it<19:03:29.824> can<19:03:30.000> happen<19:03:30.240> if<19:03:30.896> you've<19:03:31.080> got<19:03:31.320> a<19:03:31.800> um 19:03:31.790 --> 19:03:31.800 align:start position:0% it can it can happen if you've got a um 19:03:31.800 --> 19:03:33.886 align:start position:0% it can it can happen if you've got a um Hub<19:03:32.160> plugged<19:03:32.512> in<19:03:32.576> but<19:03:32.824> it<19:03:33.424> would<19:03:33.600> you<19:03:33.784> would 19:03:33.886 --> 19:03:33.896 align:start position:0% Hub plugged in but it would you would 19:03:33.896 --> 19:03:36.350 align:start position:0% Hub plugged in but it would you would normally<19:03:34.144> have<19:03:34.256> this<19:03:34.440> on<19:03:34.616> your<19:03:34.744> network 19:03:36.350 --> 19:03:36.360 align:start position:0% normally have this on your network 19:03:36.360 --> 19:03:38.150 align:start position:0% normally have this on your network however<19:03:36.960> the<19:03:37.192> ARP<19:03:37.504> Source<19:03:37.800> the<19:03:37.856> MAC<19:03:37.976> address 19:03:38.150 --> 19:03:38.160 align:start position:0% however the ARP Source the MAC address 19:03:38.160 --> 19:03:40.006 align:start position:0% however the ARP Source the MAC address is<19:03:38.464> disguised<19:03:39.056> and<19:03:39.240> the<19:03:39.360> arc<19:03:39.600> cache<19:03:39.960> is 19:03:40.006 --> 19:03:40.016 align:start position:0% is disguised and the arc cache is 19:03:40.016 --> 19:03:42.606 align:start position:0% is disguised and the arc cache is poisoned 19:03:42.606 --> 19:03:42.616 align:start position:0% poisoned 19:03:42.616 --> 19:03:45.286 align:start position:0% poisoned de-authentication<19:03:43.616> this<19:03:44.280> is<19:03:44.464> used<19:03:44.640> on<19:03:45.000> Wi-Fi 19:03:45.286 --> 19:03:45.296 align:start position:0% de-authentication this is used on Wi-Fi 19:03:45.296 --> 19:03:47.094 align:start position:0% de-authentication this is used on Wi-Fi networks<19:03:45.832> this<19:03:46.144> is<19:03:46.256> more<19:03:46.440> of<19:03:46.552> a<19:03:46.744> pain<19:03:46.856> than 19:03:47.094 --> 19:03:47.104 align:start position:0% networks this is more of a pain than 19:03:47.104 --> 19:03:49.734 align:start position:0% networks this is more of a pain than anything<19:03:47.336> it<19:03:48.176> sends<19:03:48.600> a<19:03:48.784> de-authentication 19:03:49.734 --> 19:03:49.744 align:start position:0% anything it sends a de-authentication 19:03:49.744 --> 19:03:53.150 align:start position:0% anything it sends a de-authentication frame<19:03:50.696> to<19:03:51.176> the<19:03:51.296> host<19:03:51.424> to<19:03:51.720> end<19:03:51.896> the<19:03:52.080> session<19:03:52.256> the 19:03:53.150 --> 19:03:53.160 align:start position:0% frame to the host to end the session the 19:03:53.160 --> 19:03:54.470 align:start position:0% frame to the host to end the session the attackers<19:03:53.512> boosts<19:03:53.872> the<19:03:53.936> victim's<19:03:54.296> Mac 19:03:54.470 --> 19:03:54.480 align:start position:0% attackers boosts the victim's Mac 19:03:54.480 --> 19:03:56.094 align:start position:0% attackers boosts the victim's Mac address<19:03:54.720> which<19:03:55.192> you<19:03:55.320> could<19:03:55.504> attain<19:03:55.800> by 19:03:56.094 --> 19:03:56.104 align:start position:0% address which you could attain by 19:03:56.104 --> 19:03:58.542 align:start position:0% address which you could attain by sniffing<19:03:56.576> while<19:03:56.760> a<19:03:57.000> sniffing<19:03:57.360> now<19:03:58.192> there's<19:03:58.376> no 19:03:58.542 --> 19:03:58.552 align:start position:0% sniffing while a sniffing now there's no 19:03:58.552 --> 19:04:01.134 align:start position:0% sniffing while a sniffing now there's no need<19:03:58.744> for<19:03:58.920> encryption<19:03:59.536> so<19:04:00.536> even<19:04:00.896> though 19:04:01.134 --> 19:04:01.144 align:start position:0% need for encryption so even though 19:04:01.144 --> 19:04:05.150 align:start position:0% need for encryption so even though you've<19:04:01.504> got<19:04:01.744> an<19:04:02.160> encrypted<19:04:02.824> uh<19:04:03.480> connection 19:04:05.150 --> 19:04:05.160 align:start position:0% you've got an encrypted uh connection 19:04:05.160 --> 19:04:07.966 align:start position:0% you've got an encrypted uh connection so<19:04:05.464> or<19:04:05.760> your<19:04:06.000> device<19:04:06.296> or<19:04:07.016> all<19:04:07.256> your<19:04:07.376> traffic<19:04:07.680> is 19:04:07.966 --> 19:04:07.976 align:start position:0% so or your device or all your traffic is 19:04:07.976 --> 19:04:10.542 align:start position:0% so or your device or all your traffic is encrypted<19:04:08.512> the<19:04:09.360> de-authentication<19:04:10.192> frame 19:04:10.542 --> 19:04:10.552 align:start position:0% encrypted the de-authentication frame 19:04:10.552 --> 19:04:12.774 align:start position:0% encrypted the de-authentication frame doesn't<19:04:10.856> have<19:04:11.160> to<19:04:11.336> be 19:04:12.774 --> 19:04:12.784 align:start position:0% doesn't have to be 19:04:12.784 --> 19:04:17.454 align:start position:0% doesn't have to be so<19:04:13.256> whatever<19:04:13.440> that<19:04:13.976> frame<19:04:14.512> will<19:04:14.760> say 19:04:17.454 --> 19:04:17.464 align:start position:0% 19:04:17.464 --> 19:04:19.070 align:start position:0% whatever<19:04:17.872> whatever<19:04:18.240> it<19:04:18.536> says<19:04:18.720> in<19:04:18.784> the<19:04:18.896> frame 19:04:19.070 --> 19:04:19.080 align:start position:0% whatever whatever it says in the frame 19:04:19.080 --> 19:04:21.046 align:start position:0% whatever whatever it says in the frame to<19:04:19.256> tell<19:04:19.440> it<19:04:19.552> to<19:04:19.680> terminate<19:04:20.040> the<19:04:20.216> session<19:04:20.400> that 19:04:21.046 --> 19:04:21.056 align:start position:0% to tell it to terminate the session that 19:04:21.056 --> 19:04:23.454 align:start position:0% to tell it to terminate the session that doesn't<19:04:21.240> have<19:04:21.536> to<19:04:21.656> be<19:04:21.784> so<19:04:22.616> it's<19:04:22.800> a<19:04:22.976> floor<19:04:23.160> in 19:04:23.454 --> 19:04:23.464 align:start position:0% doesn't have to be so it's a floor in 19:04:23.464 --> 19:04:25.734 align:start position:0% doesn't have to be so it's a floor in the<19:04:23.640> technology 19:04:25.734 --> 19:04:25.744 align:start position:0% the technology 19:04:25.744 --> 19:04:28.134 align:start position:0% the technology brute<19:04:26.280> force<19:04:26.640> uh<19:04:27.424> this<19:04:27.600> is<19:04:27.720> a<19:04:27.832> type<19:04:28.016> of 19:04:28.134 --> 19:04:28.144 align:start position:0% brute force uh this is a type of 19:04:28.144 --> 19:04:29.750 align:start position:0% brute force uh this is a type of password<19:04:28.320> attack<19:04:28.744> the<19:04:29.040> other<19:04:29.216> type<19:04:29.400> is<19:04:29.576> a 19:04:29.750 --> 19:04:29.760 align:start position:0% password attack the other type is a 19:04:29.760 --> 19:04:33.046 align:start position:0% password attack the other type is a dictionary<19:04:30.120> attack<19:04:30.504> so<19:04:31.504> what<19:04:31.920> the<19:04:32.216> Brute 19:04:33.046 --> 19:04:33.056 align:start position:0% dictionary attack so what the Brute 19:04:33.056 --> 19:04:34.910 align:start position:0% dictionary attack so what the Brute Force<19:04:33.360> attack<19:04:33.480> does<19:04:33.784> it<19:04:34.080> just<19:04:34.192> keeps<19:04:34.496> guessing 19:04:34.910 --> 19:04:34.920 align:start position:0% Force attack does it just keeps guessing 19:04:34.920 --> 19:04:36.774 align:start position:0% Force attack does it just keeps guessing over<19:04:35.280> and<19:04:35.576> over 19:04:36.774 --> 19:04:36.784 align:start position:0% over and over 19:04:36.784 --> 19:04:39.166 align:start position:0% over and over to<19:04:37.192> try<19:04:37.320> and<19:04:37.440> find<19:04:37.616> the<19:04:37.800> password 19:04:39.166 --> 19:04:39.176 align:start position:0% to try and find the password 19:04:39.176 --> 19:04:40.846 align:start position:0% to try and find the password typically<19:04:39.784> the<19:04:40.080> username<19:04:40.440> would<19:04:40.616> have<19:04:40.744> been 19:04:40.846 --> 19:04:40.856 align:start position:0% typically the username would have been 19:04:40.856 --> 19:04:43.134 align:start position:0% typically the username would have been installed<19:04:41.216> and 19:04:43.134 --> 19:04:43.144 align:start position:0% installed and 19:04:43.144 --> 19:04:44.862 align:start position:0% installed and um yeah<19:04:43.376> you'll<19:04:43.800> have<19:04:43.920> a<19:04:44.104> hashed<19:04:44.400> version<19:04:44.576> of 19:04:44.862 --> 19:04:44.872 align:start position:0% um yeah you'll have a hashed version of 19:04:44.872 --> 19:04:46.486 align:start position:0% um yeah you'll have a hashed version of the<19:04:45.120> password<19:04:45.296> this<19:04:45.784> is<19:04:45.896> what<19:04:46.016> it's<19:04:46.144> trying<19:04:46.320> to 19:04:46.486 --> 19:04:46.496 align:start position:0% the password this is what it's trying to 19:04:46.496 --> 19:04:47.862 align:start position:0% the password this is what it's trying to guess 19:04:47.862 --> 19:04:47.872 align:start position:0% guess 19:04:47.872 --> 19:04:50.150 align:start position:0% guess the<19:04:48.424> same<19:04:48.600> hashing<19:04:49.080> algorithm<19:04:49.552> is<19:04:49.800> used<19:04:49.976> for 19:04:50.150 --> 19:04:50.160 align:start position:0% the same hashing algorithm is used for 19:04:50.160 --> 19:04:53.150 align:start position:0% the same hashing algorithm is used for example<19:04:50.720> md5<19:04:51.720> is<19:04:52.080> used 19:04:53.150 --> 19:04:53.160 align:start position:0% example md5 is used 19:04:53.160 --> 19:04:55.430 align:start position:0% example md5 is used and<19:04:53.936> it<19:04:54.296> will<19:04:54.424> use<19:04:54.600> this<19:04:54.784> to<19:04:54.960> try<19:04:55.144> and<19:04:55.256> send 19:04:55.430 --> 19:04:55.440 align:start position:0% and it will use this to try and send 19:04:55.440 --> 19:04:56.926 align:start position:0% and it will use this to try and send hash<19:04:55.800> values 19:04:56.926 --> 19:04:56.936 align:start position:0% hash values 19:04:56.936 --> 19:04:58.790 align:start position:0% hash values you'll<19:04:57.360> combat<19:04:57.720> it<19:04:57.960> using<19:04:58.256> Advanced 19:04:58.790 --> 19:04:58.800 align:start position:0% you'll combat it using Advanced 19:04:58.800 --> 19:05:01.246 align:start position:0% you'll combat it using Advanced algorithms<19:04:59.512> so<19:05:00.000> you'd<19:05:00.360> have<19:05:00.480> like<19:05:00.784> millions 19:05:01.246 --> 19:05:01.256 align:start position:0% algorithms so you'd have like millions 19:05:01.256 --> 19:05:03.950 align:start position:0% algorithms so you'd have like millions or<19:05:01.440> billions<19:05:01.744> of<19:05:01.920> combinations 19:05:03.950 --> 19:05:03.960 align:start position:0% or billions of combinations 19:05:03.960 --> 19:05:05.862 align:start position:0% or billions of combinations um<19:05:04.016> for<19:05:04.320> example<19:05:04.552> RSA<19:05:05.216> or<19:05:05.400> public<19:05:05.640> key 19:05:05.862 --> 19:05:05.872 align:start position:0% um for example RSA or public key 19:05:05.872 --> 19:05:09.526 align:start position:0% um for example RSA or public key encryption 19:05:09.526 --> 19:05:09.536 align:start position:0% 19:05:09.536 --> 19:05:12.590 align:start position:0% VLAN<19:05:10.192> hop<19:05:10.320> in<19:05:10.552> uh<19:05:10.976> host<19:05:11.160> typically<19:05:11.512> require<19:05:12.240> a 19:05:12.590 --> 19:05:12.600 align:start position:0% VLAN hop in uh host typically require a 19:05:12.600 --> 19:05:14.862 align:start position:0% VLAN hop in uh host typically require a layer<19:05:12.832> 3<19:05:12.960> device<19:05:13.376> to<19:05:13.744> reach<19:05:13.920> under<19:05:14.160> the<19:05:14.464> VLAN 19:05:14.862 --> 19:05:14.872 align:start position:0% layer 3 device to reach under the VLAN 19:05:14.872 --> 19:05:16.966 align:start position:0% layer 3 device to reach under the VLAN and<19:05:15.536> if<19:05:15.720> I've<19:05:15.832> got<19:05:16.016> a<19:05:16.192> picture<19:05:16.552> of<19:05:16.856> this 19:05:16.966 --> 19:05:16.976 align:start position:0% and if I've got a picture of this 19:05:16.976 --> 19:05:19.606 align:start position:0% and if I've got a picture of this actually<19:05:17.216> but<19:05:18.056> we've<19:05:18.296> seen<19:05:18.832> before<19:05:19.016> if<19:05:19.376> you've 19:05:19.606 --> 19:05:19.616 align:start position:0% actually but we've seen before if you've 19:05:19.616 --> 19:05:21.414 align:start position:0% actually but we've seen before if you've got<19:05:19.800> a<19:05:20.216> hosts 19:05:21.414 --> 19:05:21.424 align:start position:0% got a hosts 19:05:21.424 --> 19:05:23.326 align:start position:0% got a hosts in<19:05:22.016> this<19:05:22.192> VLAN 19:05:23.326 --> 19:05:23.336 align:start position:0% in this VLAN 19:05:23.336 --> 19:05:25.734 align:start position:0% in this VLAN and<19:05:23.872> they<19:05:24.000> will<19:05:24.120> connect<19:05:24.296> to<19:05:24.536> a<19:05:24.720> switch<19:05:24.960> and 19:05:25.734 --> 19:05:25.744 align:start position:0% and they will connect to a switch and 19:05:25.744 --> 19:05:28.966 align:start position:0% and they will connect to a switch and then<19:05:25.856> hosts<19:05:26.936> in<19:05:27.480> this<19:05:27.656> VLAN 19:05:28.966 --> 19:05:28.976 align:start position:0% then hosts in this VLAN 19:05:28.976 --> 19:05:32.094 align:start position:0% then hosts in this VLAN so<19:05:29.336> VLAN<19:05:29.872> 10<19:05:30.176> VLAN<19:05:30.832> 20<19:05:31.080> and<19:05:31.744> they'll<19:05:31.976> be 19:05:32.094 --> 19:05:32.104 align:start position:0% so VLAN 10 VLAN 20 and they'll be 19:05:32.104 --> 19:05:34.542 align:start position:0% so VLAN 10 VLAN 20 and they'll be they'll<19:05:32.336> have<19:05:32.464> different<19:05:32.640> IP<19:05:33.056> addresses<19:05:33.600> but 19:05:34.542 --> 19:05:34.552 align:start position:0% they'll have different IP addresses but 19:05:34.552 --> 19:05:36.710 align:start position:0% they'll have different IP addresses but uh<19:05:34.744> these<19:05:35.104> do<19:05:35.216> these<19:05:35.696> devices<19:05:36.120> can't<19:05:36.480> connect 19:05:36.710 --> 19:05:36.720 align:start position:0% uh these do these devices can't connect 19:05:36.720 --> 19:05:38.990 align:start position:0% uh these do these devices can't connect to<19:05:36.960> one<19:05:37.192> another<19:05:37.400> unless<19:05:38.400> the<19:05:38.576> switch<19:05:38.760> is 19:05:38.990 --> 19:05:39.000 align:start position:0% to one another unless the switch is 19:05:39.000 --> 19:05:41.926 align:start position:0% to one another unless the switch is connected<19:05:39.424> to<19:05:39.656> a<19:05:39.960> layer<19:05:40.320> 3<19:05:40.440> device<19:05:40.800> now<19:05:41.760> this 19:05:41.926 --> 19:05:41.936 align:start position:0% connected to a layer 3 device now this 19:05:41.936 --> 19:05:43.910 align:start position:0% connected to a layer 3 device now this can<19:05:42.120> actually<19:05:42.240> be<19:05:42.480> built<19:05:42.832> into<19:05:42.960> the<19:05:43.256> switch<19:05:43.552> it 19:05:43.910 --> 19:05:43.920 align:start position:0% can actually be built into the switch it 19:05:43.920 --> 19:05:45.950 align:start position:0% can actually be built into the switch it could<19:05:44.040> be<19:05:44.280> a<19:05:44.400> multi-layer<19:05:44.936> switch<19:05:45.120> but<19:05:45.720> it<19:05:45.832> has 19:05:45.950 --> 19:05:45.960 align:start position:0% could be a multi-layer switch but it has 19:05:45.960 --> 19:05:48.646 align:start position:0% could be a multi-layer switch but it has to<19:05:46.144> have<19:05:46.256> this<19:05:46.496> layer<19:05:46.976> 3<19:05:47.104> capability 19:05:48.646 --> 19:05:48.656 align:start position:0% to have this layer 3 capability 19:05:48.656 --> 19:05:50.862 align:start position:0% to have this layer 3 capability well<19:05:49.080> VLAN<19:05:49.552> hopping<19:05:49.856> the<19:05:49.976> attacker<19:05:50.400> attempts 19:05:50.862 --> 19:05:50.872 align:start position:0% well VLAN hopping the attacker attempts 19:05:50.872 --> 19:05:52.910 align:start position:0% well VLAN hopping the attacker attempts to<19:05:50.936> bypass<19:05:51.360> the<19:05:51.536> layer<19:05:51.832> 3<19:05:51.960> device<19:05:52.256> to<19:05:52.616> com 19:05:52.910 --> 19:05:52.920 align:start position:0% to bypass the layer 3 device to com 19:05:52.920 --> 19:05:55.430 align:start position:0% to bypass the layer 3 device to com compromise<19:05:53.576> another<19:05:53.824> device<19:05:54.240> and<19:05:55.144> you<19:05:55.320> could 19:05:55.430 --> 19:05:55.440 align:start position:0% compromise another device and you could 19:05:55.440 --> 19:05:57.646 align:start position:0% compromise another device and you could have<19:05:55.680> all<19:05:55.976> your<19:05:56.160> security 19:05:57.646 --> 19:05:57.656 align:start position:0% have all your security 19:05:57.656 --> 19:06:00.414 align:start position:0% have all your security or<19:05:58.552> some<19:05:58.856> of<19:05:59.104> your<19:05:59.216> security<19:05:59.464> built<19:06:00.000> into<19:06:00.120> this 19:06:00.414 --> 19:06:00.424 align:start position:0% or some of your security built into this 19:06:00.424 --> 19:06:02.454 align:start position:0% or some of your security built into this layer<19:06:00.720> 3<19:06:00.832> device 19:06:02.454 --> 19:06:02.464 align:start position:0% layer 3 device 19:06:02.464 --> 19:06:05.206 align:start position:0% layer 3 device here<19:06:03.480> it's<19:06:03.832> done<19:06:04.016> by<19:06:04.256> a<19:06:04.376> switch<19:06:04.496> spoofing<19:06:05.040> or 19:06:05.206 --> 19:06:05.216 align:start position:0% here it's done by a switch spoofing or 19:06:05.216 --> 19:06:07.670 align:start position:0% here it's done by a switch spoofing or double<19:06:05.400> tagging 19:06:07.670 --> 19:06:07.680 align:start position:0% double tagging 19:06:07.680 --> 19:06:09.166 align:start position:0% double tagging so<19:06:07.920> switch<19:06:08.216> spoofing<19:06:08.824> the<19:06:09.000> device 19:06:09.166 --> 19:06:09.176 align:start position:0% so switch spoofing the device 19:06:09.176 --> 19:06:11.990 align:start position:0% so switch spoofing the device impersonates<19:06:10.080> a<19:06:10.376> switch<19:06:10.616> whatever<19:06:11.512> this 19:06:11.990 --> 19:06:12.000 align:start position:0% impersonates a switch whatever this 19:06:12.000 --> 19:06:14.326 align:start position:0% impersonates a switch whatever this Rogue<19:06:12.480> device<19:06:12.656> is<19:06:12.960> it's<19:06:13.320> pretending<19:06:13.800> to<19:06:13.920> be<19:06:14.160> a 19:06:14.326 --> 19:06:14.336 align:start position:0% Rogue device is it's pretending to be a 19:06:14.336 --> 19:06:17.030 align:start position:0% Rogue device is it's pretending to be a switch<19:06:14.784> so<19:06:15.784> probably<19:06:16.080> we'll<19:06:16.376> need<19:06:16.552> a<19:06:16.800> trunk 19:06:17.030 --> 19:06:17.040 align:start position:0% switch so probably we'll need a trunk 19:06:17.040 --> 19:06:19.542 align:start position:0% switch so probably we'll need a trunk link<19:06:17.216> here 19:06:19.542 --> 19:06:19.552 align:start position:0% 19:06:19.552 --> 19:06:21.710 align:start position:0% you<19:06:20.104> combat<19:06:20.464> it<19:06:20.640> by<19:06:20.760> disabling<19:06:21.240> trunking 19:06:21.710 --> 19:06:21.720 align:start position:0% you combat it by disabling trunking 19:06:21.720 --> 19:06:24.886 align:start position:0% you combat it by disabling trunking where<19:06:22.016> not<19:06:22.320> required 19:06:24.886 --> 19:06:24.896 align:start position:0% 19:06:24.896 --> 19:06:28.070 align:start position:0% to<19:06:25.256> say<19:06:25.504> this<19:06:25.744> is<19:06:25.920> your<19:06:26.216> frame<19:06:26.760> here<19:06:27.056> and<19:06:27.960> you 19:06:28.070 --> 19:06:28.080 align:start position:0% to say this is your frame here and you 19:06:28.080 --> 19:06:31.006 align:start position:0% to say this is your frame here and you would<19:06:28.144> have<19:06:28.320> your<19:06:28.496> VLAN 19:06:31.006 --> 19:06:31.016 align:start position:0% would have your VLAN 19:06:31.016 --> 19:06:36.046 align:start position:0% would have your VLAN uh<19:06:31.856> 10<19:06:32.104> here<19:06:32.536> and<19:06:33.616> say<19:06:34.616> 20<19:06:34.976> here<19:06:35.336> well<19:06:35.760> normally 19:06:36.046 --> 19:06:36.056 align:start position:0% uh 10 here and say 20 here well normally 19:06:36.056 --> 19:06:38.454 align:start position:0% uh 10 here and say 20 here well normally when<19:06:36.296> the<19:06:36.480> frame<19:06:36.720> reaches<19:06:37.080> the<19:06:37.256> destination 19:06:38.454 --> 19:06:38.464 align:start position:0% when the frame reaches the destination 19:06:38.464 --> 19:06:40.790 align:start position:0% when the frame reaches the destination the<19:06:39.120> VLAN<19:06:39.600> tag<19:06:39.896> is<19:06:40.016> removed<19:06:40.440> because<19:06:40.552> the 19:06:40.790 --> 19:06:40.800 align:start position:0% the VLAN tag is removed because the 19:06:40.800 --> 19:06:42.110 align:start position:0% the VLAN tag is removed because the hosts<19:06:41.104> don't<19:06:41.216> really<19:06:41.400> care<19:06:41.576> that<19:06:41.824> they're<19:06:41.936> in 19:06:42.110 --> 19:06:42.120 align:start position:0% hosts don't really care that they're in 19:06:42.120 --> 19:06:44.206 align:start position:0% hosts don't really care that they're in a<19:06:42.240> VLAN<19:06:42.656> but<19:06:43.192> what<19:06:43.376> they<19:06:43.552> can<19:06:43.616> do<19:06:43.744> with<19:06:43.856> VLAN 19:06:44.206 --> 19:06:44.216 align:start position:0% a VLAN but what they can do with VLAN 19:06:44.216 --> 19:06:47.926 align:start position:0% a VLAN but what they can do with VLAN hopping<19:06:44.576> is<19:06:44.696> they<19:06:44.936> can<19:06:45.120> add<19:06:45.240> an<19:06:45.424> extra<19:06:45.536> one 19:06:47.926 --> 19:06:47.936 align:start position:0% 19:06:47.936 --> 19:06:50.502 align:start position:0% um<19:06:48.056> here<19:06:48.656> in<19:06:49.256> order<19:06:49.376> to<19:06:49.552> gain<19:06:49.800> access<19:06:50.104> to<19:06:50.400> a 19:06:50.502 --> 19:06:50.512 align:start position:0% um here in order to gain access to a 19:06:50.512 --> 19:06:53.094 align:start position:0% um here in order to gain access to a VLAN<19:06:51.000> when<19:06:51.656> this<19:06:52.144> device<19:06:52.320> might<19:06:52.616> be<19:06:52.744> over<19:06:52.920> here 19:06:53.094 --> 19:06:53.104 align:start position:0% VLAN when this device might be over here 19:06:53.104 --> 19:06:55.910 align:start position:0% VLAN when this device might be over here on<19:06:53.280> VLAN<19:06:53.760> 20. 19:06:55.910 --> 19:06:55.920 align:start position:0% on VLAN 20. 19:06:55.920 --> 19:06:58.670 align:start position:0% on VLAN 20. so<19:06:56.336> that's<19:06:56.400> double<19:06:56.640> tagging 19:06:58.670 --> 19:06:58.680 align:start position:0% so that's double tagging 19:06:58.680 --> 19:07:01.182 align:start position:0% so that's double tagging combat<19:06:59.280> by<19:06:59.512> using<19:06:59.760> a<19:06:59.936> dedicated<19:07:00.296> VLAN<19:07:00.832> for<19:07:01.016> all 19:07:01.182 --> 19:07:01.192 align:start position:0% combat by using a dedicated VLAN for all 19:07:01.192 --> 19:07:02.686 align:start position:0% combat by using a dedicated VLAN for all trunk<19:07:01.504> links 19:07:02.686 --> 19:07:02.696 align:start position:0% trunk links 19:07:02.696 --> 19:07:05.566 align:start position:0% trunk links so<19:07:03.480> your<19:07:03.720> trunk<19:07:03.960> link<19:07:04.192> between<19:07:05.040> this<19:07:05.336> switch 19:07:05.566 --> 19:07:05.576 align:start position:0% so your trunk link between this switch 19:07:05.576 --> 19:07:07.006 align:start position:0% so your trunk link between this switch here 19:07:07.006 --> 19:07:07.016 align:start position:0% here 19:07:07.016 --> 19:07:10.310 align:start position:0% here is<19:07:07.504> switch<19:07:07.744> here<19:07:08.104> this<19:07:08.696> switch<19:07:08.872> here<19:07:09.656> you've 19:07:10.310 --> 19:07:10.320 align:start position:0% is switch here this switch here you've 19:07:10.320 --> 19:07:13.966 align:start position:0% is switch here this switch here you've got<19:07:10.616> a<19:07:11.464> special<19:07:12.176> VLAN<19:07:12.784> only<19:07:13.192> used<19:07:13.504> between 19:07:13.966 --> 19:07:13.976 align:start position:0% got a special VLAN only used between 19:07:13.976 --> 19:07:19.862 align:start position:0% got a special VLAN only used between these<19:07:14.464> trunk<19:07:14.760> links<19:07:15.120> so<19:07:15.656> save<19:07:16.080> VLAN<19:07:16.744> 101<19:07:18.080> 102 19:07:19.862 --> 19:07:19.872 align:start position:0% these trunk links so save VLAN 101 102 19:07:19.872 --> 19:07:22.606 align:start position:0% these trunk links so save VLAN 101 102 103.<19:07:20.872> these<19:07:21.480> these<19:07:21.784> numbers<19:07:21.896> aren't<19:07:22.320> used 19:07:22.606 --> 19:07:22.616 align:start position:0% 103. these these numbers aren't used 19:07:22.616 --> 19:07:24.286 align:start position:0% 103. these these numbers aren't used anywhere<19:07:23.160> else<19:07:23.400> on<19:07:23.640> the<19:07:23.760> network<19:07:23.872> they're 19:07:24.286 --> 19:07:24.296 align:start position:0% anywhere else on the network they're 19:07:24.296 --> 19:07:29.454 align:start position:0% anywhere else on the network they're just<19:07:24.480> used<19:07:24.656> for<19:07:24.896> the<19:07:25.016> trunk<19:07:25.376> links 19:07:29.454 --> 19:07:29.464 align:start position:0% 19:07:29.464 --> 19:07:32.750 align:start position:0% uh<19:07:29.936> this<19:07:30.120> is<19:07:30.176> just<19:07:30.360> a<19:07:30.536> diagram<19:07:30.784> showing<19:07:31.376> you<19:07:31.920> um 19:07:32.750 --> 19:07:32.760 align:start position:0% uh this is just a diagram showing you um 19:07:32.760 --> 19:07:35.270 align:start position:0% uh this is just a diagram showing you um the<19:07:33.176> double<19:07:33.424> tag<19:07:33.784> frame<19:07:34.080> here<19:07:34.320> so<19:07:34.976> the<19:07:35.160> switch 19:07:35.270 --> 19:07:35.280 align:start position:0% the double tag frame here so the switch 19:07:35.280 --> 19:07:37.070 align:start position:0% the double tag frame here so the switch arm<19:07:35.512> removes<19:07:35.936> the<19:07:36.056> first<19:07:36.176> tagging<19:07:36.656> forwards 19:07:37.070 --> 19:07:37.080 align:start position:0% arm removes the first tagging forwards 19:07:37.080 --> 19:07:39.414 align:start position:0% arm removes the first tagging forwards to<19:07:37.192> switch<19:07:37.320> to<19:07:37.552> and<19:07:38.216> this<19:07:38.400> time 19:07:39.414 --> 19:07:39.424 align:start position:0% to switch to and this time 19:07:39.424 --> 19:07:45.046 align:start position:0% to switch to and this time the<19:07:40.080> tag<19:07:40.256> is<19:07:40.440> still<19:07:40.616> attached<19:07:41.040> to<19:07:41.104> it 19:07:45.046 --> 19:07:45.056 align:start position:0% 19:07:45.056 --> 19:07:47.270 align:start position:0% man<19:07:45.536> in<19:07:45.832> the<19:07:45.960> middle<19:07:46.080> attack<19:07:46.320> uh<19:07:46.856> convinces 19:07:47.270 --> 19:07:47.280 align:start position:0% man in the middle attack uh convinces 19:07:47.280 --> 19:07:48.822 align:start position:0% man in the middle attack uh convinces the<19:07:47.464> sender<19:07:47.824> and<19:07:47.936> receiver<19:07:48.296> that<19:07:48.656> the 19:07:48.822 --> 19:07:48.832 align:start position:0% the sender and receiver that the 19:07:48.832 --> 19:07:50.206 align:start position:0% the sender and receiver that the computer<19:07:49.016> in<19:07:49.320> the<19:07:49.504> middle<19:07:49.616> is<19:07:49.856> the<19:07:50.040> actual 19:07:50.206 --> 19:07:50.216 align:start position:0% computer in the middle is the actual 19:07:50.216 --> 19:07:52.366 align:start position:0% computer in the middle is the actual host<19:07:50.464> so<19:07:50.696> this<19:07:50.936> host<19:07:51.176> here<19:07:51.424> thinks<19:07:52.016> it<19:07:52.192> says 19:07:52.366 --> 19:07:52.376 align:start position:0% host so this host here thinks it says 19:07:52.376 --> 19:07:54.414 align:start position:0% host so this host here thinks it says speaking<19:07:52.744> to<19:07:52.800> the<19:07:52.976> server<19:07:53.336> the<19:07:53.824> server<19:07:54.120> thinks 19:07:54.414 --> 19:07:54.424 align:start position:0% speaking to the server the server thinks 19:07:54.424 --> 19:07:55.846 align:start position:0% speaking to the server the server thinks he's<19:07:54.536> speaking<19:07:54.832> to<19:07:55.016> this<19:07:55.144> host<19:07:55.320> over<19:07:55.616> here 19:07:55.846 --> 19:07:55.856 align:start position:0% he's speaking to this host over here 19:07:55.856 --> 19:07:58.366 align:start position:0% he's speaking to this host over here really<19:07:56.824> it's<19:07:57.240> going<19:07:57.536> between<19:07:58.016> this 19:07:58.366 --> 19:07:58.376 align:start position:0% really it's going between this 19:07:58.376 --> 19:08:00.110 align:start position:0% really it's going between this intermediary<19:07:58.976> device<19:07:59.216> here<19:07:59.512> which<19:07:59.760> is<19:07:59.872> the 19:08:00.110 --> 19:08:00.120 align:start position:0% intermediary device here which is the 19:08:00.120 --> 19:08:02.094 align:start position:0% intermediary device here which is the attacker 19:08:02.094 --> 19:08:02.104 align:start position:0% attacker 19:08:02.104 --> 19:08:04.430 align:start position:0% attacker you<19:08:02.512> normally<19:08:02.824> accompany<19:08:03.240> this<19:08:03.536> with<19:08:03.784> DNS<19:08:04.192> or 19:08:04.430 --> 19:08:04.440 align:start position:0% you normally accompany this with DNS or 19:08:04.440 --> 19:08:06.526 align:start position:0% you normally accompany this with DNS or ARP<19:08:04.800> spoofing<19:08:05.280> so<19:08:05.400> there'd<19:08:05.576> be<19:08:05.640> an<19:08:05.824> ARP<19:08:06.120> cache 19:08:06.526 --> 19:08:06.536 align:start position:0% ARP spoofing so there'd be an ARP cache 19:08:06.536 --> 19:08:09.590 align:start position:0% ARP spoofing so there'd be an ARP cache here 19:08:09.590 --> 19:08:09.600 align:start position:0% 19:08:09.600 --> 19:08:12.886 align:start position:0% and<19:08:10.440> here<19:08:10.920> and<19:08:11.464> it<19:08:11.696> would<19:08:11.872> say<19:08:12.120> the<19:08:12.720> back 19:08:12.886 --> 19:08:12.896 align:start position:0% and here and it would say the back 19:08:12.896 --> 19:08:15.414 align:start position:0% and here and it would say the back address<19:08:13.144> for<19:08:13.440> this<19:08:13.616> particular<19:08:13.976> host<19:08:14.424> but 19:08:15.414 --> 19:08:15.424 align:start position:0% address for this particular host but 19:08:15.424 --> 19:08:17.030 align:start position:0% address for this particular host but really<19:08:15.656> it's<19:08:15.832> injected<19:08:16.320> a<19:08:16.440> false<19:08:16.680> Mac<19:08:16.856> address 19:08:17.030 --> 19:08:17.040 align:start position:0% really it's injected a false Mac address 19:08:17.040 --> 19:08:18.526 align:start position:0% really it's injected a false Mac address here 19:08:18.526 --> 19:08:18.536 align:start position:0% here 19:08:18.536 --> 19:08:20.566 align:start position:0% here and<19:08:19.016> it<19:08:19.192> and<19:08:19.440> the<19:08:19.680> messages<19:08:20.040> are<19:08:20.400> actually 19:08:20.566 --> 19:08:20.576 align:start position:0% and it and the messages are actually 19:08:20.576 --> 19:08:22.606 align:start position:0% and it and the messages are actually sent<19:08:20.872> and<19:08:21.120> received 19:08:22.606 --> 19:08:22.616 align:start position:0% sent and received 19:08:22.616 --> 19:08:25.430 align:start position:0% sent and received so<19:08:23.040> there's<19:08:23.160> acknowledgment<19:08:23.696> it<19:08:24.240> sends<19:08:24.720> and 19:08:25.430 --> 19:08:25.440 align:start position:0% so there's acknowledgment it sends and 19:08:25.440 --> 19:08:27.166 align:start position:0% so there's acknowledgment it sends and then<19:08:25.616> this<19:08:26.040> device<19:08:26.216> here<19:08:26.512> will<19:08:26.696> send<19:08:26.872> out<19:08:27.000> an 19:08:27.166 --> 19:08:27.176 align:start position:0% then this device here will send out an 19:08:27.176 --> 19:08:28.606 align:start position:0% then this device here will send out an acknowledgment<19:08:27.656> but<19:08:27.960> really<19:08:28.144> it's<19:08:28.376> going 19:08:28.606 --> 19:08:28.616 align:start position:0% acknowledgment but really it's going 19:08:28.616 --> 19:08:30.230 align:start position:0% acknowledgment but really it's going through<19:08:28.976> the<19:08:29.160> middle<19:08:29.280> here 19:08:30.230 --> 19:08:30.240 align:start position:0% through the middle here 19:08:30.240 --> 19:08:33.110 align:start position:0% through the middle here type<19:08:30.600> of<19:08:30.784> spoofing<19:08:31.192> attack 19:08:33.110 --> 19:08:33.120 align:start position:0% type of spoofing attack 19:08:33.120 --> 19:08:35.326 align:start position:0% type of spoofing attack I've<19:08:33.424> renderability<19:08:34.016> scanning 19:08:35.326 --> 19:08:35.336 align:start position:0% I've renderability scanning 19:08:35.336 --> 19:08:36.350 align:start position:0% I've renderability scanning um 19:08:36.350 --> 19:08:36.360 align:start position:0% um 19:08:36.360 --> 19:08:38.270 align:start position:0% um this<19:08:36.784> should<19:08:36.960> have<19:08:37.080> appeared<19:08:37.440> in<19:08:37.552> a<19:08:38.104> moment 19:08:38.270 --> 19:08:38.280 align:start position:0% this should have appeared in a moment 19:08:38.280 --> 19:08:40.182 align:start position:0% this should have appeared in a moment sorry<19:08:38.512> it<19:08:39.120> probes<19:08:39.424> the<19:08:39.536> host<19:08:39.720> in<19:08:39.896> order<19:08:40.080> to 19:08:40.182 --> 19:08:40.192 align:start position:0% sorry it probes the host in order to 19:08:40.192 --> 19:08:43.246 align:start position:0% sorry it probes the host in order to find<19:08:40.440> an<19:08:40.680> explode<19:08:41.040> exploitable<19:08:41.960> service<19:08:42.960> or 19:08:43.246 --> 19:08:43.256 align:start position:0% find an explode exploitable service or 19:08:43.256 --> 19:08:45.710 align:start position:0% find an explode exploitable service or process<19:08:43.696> so<19:08:44.696> you've<19:08:44.872> got<19:08:45.000> your<19:08:45.120> server<19:08:45.480> here 19:08:45.710 --> 19:08:45.720 align:start position:0% process so you've got your server here 19:08:45.720 --> 19:08:49.366 align:start position:0% process so you've got your server here and<19:08:46.496> obviously<19:08:46.856> there's<19:08:47.280> ports<19:08:48.424> permitted<19:08:49.256> or 19:08:49.366 --> 19:08:49.376 align:start position:0% and obviously there's ports permitted or 19:08:49.376 --> 19:08:52.542 align:start position:0% and obviously there's ports permitted or denied<19:08:49.744> but<19:08:50.216> it<19:08:50.336> will<19:08:50.512> keep<19:08:50.760> probing<19:08:51.656> until<19:08:52.192> it 19:08:52.542 --> 19:08:52.552 align:start position:0% denied but it will keep probing until it 19:08:52.552 --> 19:08:55.134 align:start position:0% denied but it will keep probing until it finally<19:08:52.800> finds<19:08:53.216> one<19:08:53.464> that's<19:08:54.000> open<19:08:54.296> and<19:08:55.016> then 19:08:55.134 --> 19:08:55.144 align:start position:0% finally finds one that's open and then 19:08:55.144 --> 19:08:57.646 align:start position:0% finally finds one that's open and then it<19:08:55.320> will<19:08:55.504> try<19:08:55.744> and<19:08:55.920> do<19:08:56.040> some<19:08:56.216> damage 19:08:57.646 --> 19:08:57.656 align:start position:0% it will try and do some damage 19:08:57.656 --> 19:08:59.502 align:start position:0% it will try and do some damage there's<19:08:58.080> a<19:08:58.192> whole<19:08:58.320> bunch<19:08:58.496> of<19:08:58.616> tools<19:08:58.976> if<19:08:59.216> you<19:08:59.336> do 19:08:59.502 --> 19:08:59.512 align:start position:0% there's a whole bunch of tools if you do 19:08:59.512 --> 19:09:01.246 align:start position:0% there's a whole bunch of tools if you do an<19:08:59.640> ethical<19:08:59.872> hacking<19:09:00.360> course<19:09:00.656> for<19:09:00.960> example 19:09:01.246 --> 19:09:01.256 align:start position:0% an ethical hacking course for example 19:09:01.256 --> 19:09:04.310 align:start position:0% an ethical hacking course for example you<19:09:02.160> can<19:09:02.280> download<19:09:02.872> there's<19:09:03.480> a<19:09:03.784> ton<19:09:03.960> of<19:09:04.144> free 19:09:04.310 --> 19:09:04.320 align:start position:0% you can download there's a ton of free 19:09:04.320 --> 19:09:08.270 align:start position:0% you can download there's a ton of free tools<19:09:04.856> that<19:09:05.936> um<19:09:05.936> the<19:09:06.360> idea<19:09:06.656> is<19:09:06.976> you're<19:09:07.976> trying 19:09:08.270 --> 19:09:08.280 align:start position:0% tools that um the idea is you're trying 19:09:08.280 --> 19:09:10.134 align:start position:0% tools that um the idea is you're trying to<19:09:08.400> learn<19:09:08.576> how<19:09:08.760> to<19:09:08.872> protect<19:09:09.120> your<19:09:09.424> system<19:09:09.600> but 19:09:10.134 --> 19:09:10.144 align:start position:0% to learn how to protect your system but 19:09:10.144 --> 19:09:11.862 align:start position:0% to learn how to protect your system but they're<19:09:10.256> obviously<19:09:10.680> available<19:09:11.104> for<19:09:11.512> use<19:09:11.696> by 19:09:11.862 --> 19:09:11.872 align:start position:0% they're obviously available for use by 19:09:11.872 --> 19:09:13.366 align:start position:0% they're obviously available for use by hackers 19:09:13.366 --> 19:09:13.376 align:start position:0% hackers 19:09:13.376 --> 19:09:15.774 align:start position:0% hackers now<19:09:14.104> say<19:09:14.464> there's<19:09:14.696> a<19:09:14.872> particular<19:09:15.120> Port<19:09:15.480> open 19:09:15.774 --> 19:09:15.784 align:start position:0% now say there's a particular Port open 19:09:15.784 --> 19:09:18.414 align:start position:0% now say there's a particular Port open or<19:09:16.256> a<19:09:16.552> service<19:09:16.856> so 19:09:18.414 --> 19:09:18.424 align:start position:0% or a service so 19:09:18.424 --> 19:09:20.206 align:start position:0% or a service so um like<19:09:18.720> an<19:09:18.832> instant<19:09:19.144> messenger<19:09:19.552> Port<19:09:19.920> has 19:09:20.206 --> 19:09:20.216 align:start position:0% um like an instant messenger Port has 19:09:20.216 --> 19:09:21.646 align:start position:0% um like an instant messenger Port has been<19:09:20.336> left<19:09:20.512> open 19:09:21.646 --> 19:09:21.656 align:start position:0% been left open 19:09:21.656 --> 19:09:23.750 align:start position:0% been left open this<19:09:22.320> will<19:09:22.496> then<19:09:22.680> tell<19:09:22.920> the<19:09:23.104> attacker<19:09:23.464> the 19:09:23.750 --> 19:09:23.760 align:start position:0% this will then tell the attacker the 19:09:23.760 --> 19:09:25.494 align:start position:0% this will then tell the attacker the hacker<19:09:24.120> what<19:09:24.424> type<19:09:24.600> of<19:09:24.720> attack<19:09:24.896> will<19:09:25.256> work 19:09:25.494 --> 19:09:25.504 align:start position:0% hacker what type of attack will work 19:09:25.504 --> 19:09:27.774 align:start position:0% hacker what type of attack will work best<19:09:25.744> on<19:09:25.976> this<19:09:26.160> particular<19:09:26.464> Port<19:09:26.824> so<19:09:27.424> it<19:09:27.600> may 19:09:27.774 --> 19:09:27.784 align:start position:0% best on this particular Port so it may 19:09:27.784 --> 19:09:29.566 align:start position:0% best on this particular Port so it may not<19:09:27.896> use<19:09:28.080> that<19:09:28.320> specific<19:09:28.680> pool<19:09:28.920> but<19:09:29.216> it<19:09:29.400> may 19:09:29.566 --> 19:09:29.576 align:start position:0% not use that specific pool but it may 19:09:29.576 --> 19:09:31.670 align:start position:0% not use that specific pool but it may then<19:09:29.824> be<19:09:30.000> able<19:09:30.176> to<19:09:30.240> Target<19:09:30.600> a<19:09:31.144> vulnerability 19:09:31.670 --> 19:09:31.680 align:start position:0% then be able to Target a vulnerability 19:09:31.680 --> 19:09:33.350 align:start position:0% then be able to Target a vulnerability in<19:09:31.856> the<19:09:31.976> application 19:09:33.350 --> 19:09:33.360 align:start position:0% in the application 19:09:33.360 --> 19:09:36.710 align:start position:0% in the application one<19:09:33.784> of<19:09:33.896> the<19:09:34.016> tools<19:09:34.320> you<19:09:34.440> could<19:09:34.616> use<19:09:34.856> is<19:09:35.464> a<19:09:35.640> nmap 19:09:36.710 --> 19:09:36.720 align:start position:0% one of the tools you could use is a nmap 19:09:36.720 --> 19:09:38.502 align:start position:0% one of the tools you could use is a nmap you<19:09:37.144> obviously<19:09:37.440> counteract<19:09:37.920> all<19:09:38.104> of<19:09:38.216> this<19:09:38.336> by 19:09:38.502 --> 19:09:38.512 align:start position:0% you obviously counteract all of this by 19:09:38.512 --> 19:09:40.486 align:start position:0% you obviously counteract all of this by doing<19:09:38.696> some<19:09:38.872> penetration<19:09:39.424> testing<19:09:39.896> or<19:09:40.144> paying 19:09:40.486 --> 19:09:40.496 align:start position:0% doing some penetration testing or paying 19:09:40.496 --> 19:09:41.630 align:start position:0% doing some penetration testing or paying for<19:09:40.616> it 19:09:41.630 --> 19:09:41.640 align:start position:0% for it 19:09:41.640 --> 19:09:45.110 align:start position:0% for it and<19:09:42.120> here's<19:09:42.720> a<19:09:43.192> result<19:09:43.920> from<19:09:44.216> the<19:09:44.400> nmap<19:09:44.760> tool 19:09:45.110 --> 19:09:45.120 align:start position:0% and here's a result from the nmap tool 19:09:45.120 --> 19:09:47.206 align:start position:0% and here's a result from the nmap tool here 19:09:47.206 --> 19:09:47.216 align:start position:0% here 19:09:47.216 --> 19:09:49.134 align:start position:0% here and<19:09:47.696> then<19:09:47.824> it's<19:09:48.056> giving<19:09:48.480> you<19:09:48.720> your<19:09:48.896> your 19:09:49.134 --> 19:09:49.144 align:start position:0% and then it's giving you your your 19:09:49.144 --> 19:09:50.926 align:start position:0% and then it's giving you your your outputs<19:09:49.744> you'll<19:09:50.160> learn<19:09:50.280> more<19:09:50.464> if<19:09:50.640> you<19:09:50.760> do 19:09:50.926 --> 19:09:50.936 align:start position:0% outputs you'll learn more if you do 19:09:50.936 --> 19:09:52.670 align:start position:0% outputs you'll learn more if you do penetration<19:09:51.656> testing<19:09:52.144> which<19:09:52.320> isn't<19:09:52.552> really 19:09:52.670 --> 19:09:52.680 align:start position:0% penetration testing which isn't really 19:09:52.680 --> 19:09:55.134 align:start position:0% penetration testing which isn't really covered<19:09:52.976> in<19:09:53.216> the<19:09:53.512> syllabus 19:09:55.134 --> 19:09:55.144 align:start position:0% covered in the syllabus 19:09:55.144 --> 19:09:56.990 align:start position:0% covered in the syllabus all<19:09:55.616> right<19:09:55.800> so<19:09:55.920> we've<19:09:56.160> covered<19:09:56.512> a<19:09:56.760> lot<19:09:56.872> of 19:09:56.990 --> 19:09:57.000 align:start position:0% all right so we've covered a lot of 19:09:57.000 --> 19:10:00.110 align:start position:0% all right so we've covered a lot of stuff<19:09:57.176> social<19:09:57.536> engineering<19:09:58.320> Insider<19:09:59.216> threats 19:10:00.110 --> 19:10:00.120 align:start position:0% stuff social engineering Insider threats 19:10:00.120 --> 19:10:02.686 align:start position:0% stuff social engineering Insider threats logic<19:10:00.832> bombs<19:10:01.320> the<19:10:01.680> Rogue<19:10:01.976> access<19:10:02.104> point<19:10:02.464> that 19:10:02.686 --> 19:10:02.696 align:start position:0% logic bombs the Rogue access point that 19:10:02.696 --> 19:10:05.390 align:start position:0% logic bombs the Rogue access point that somebody<19:10:02.872> brings<19:10:03.360> in<19:10:03.600> evil<19:10:04.496> twin<19:10:04.800> driving 19:10:05.390 --> 19:10:05.400 align:start position:0% somebody brings in evil twin driving 19:10:05.400 --> 19:10:07.246 align:start position:0% somebody brings in evil twin driving around<19:10:05.696> looking<19:10:06.000> for<19:10:06.296> a<19:10:06.480> free<19:10:06.720> wireless 19:10:07.246 --> 19:10:07.256 align:start position:0% around looking for a free wireless 19:10:07.256 --> 19:10:09.886 align:start position:0% around looking for a free wireless fishing 19:10:09.886 --> 19:10:09.896 align:start position:0% fishing 19:10:09.896 --> 19:10:13.430 align:start position:0% fishing uh<19:10:10.440> ransomware<19:10:11.360> poisoning<19:10:12.360> the<19:10:12.536> DNS<19:10:12.896> entries 19:10:13.430 --> 19:10:13.440 align:start position:0% uh ransomware poisoning the DNS entries 19:10:13.440 --> 19:10:16.606 align:start position:0% uh ransomware poisoning the DNS entries the<19:10:14.280> ARP<19:10:14.696> cache<19:10:15.120> spoofing<19:10:15.960> is<19:10:16.144> pretending<19:10:16.496> to 19:10:16.606 --> 19:10:16.616 align:start position:0% the ARP cache spoofing is pretending to 19:10:16.616 --> 19:10:19.070 align:start position:0% the ARP cache spoofing is pretending to be<19:10:16.800> something<19:10:17.160> or<19:10:17.464> someone<19:10:17.640> you're<19:10:17.936> not 19:10:19.070 --> 19:10:19.080 align:start position:0% be something or someone you're not 19:10:19.080 --> 19:10:22.790 align:start position:0% be something or someone you're not D<19:10:19.680> authentication<19:10:20.576> the<19:10:21.424> frames<19:10:21.896> got 19:10:22.790 --> 19:10:22.800 align:start position:0% D authentication the frames got 19:10:22.800 --> 19:10:25.790 align:start position:0% D authentication the frames got um<19:10:22.856> it<19:10:23.576> can<19:10:23.760> be<19:10:23.872> in<19:10:24.000> clear<19:10:24.120> text<19:10:24.504> Brute<19:10:25.504> Force 19:10:25.790 --> 19:10:25.800 align:start position:0% um it can be in clear text Brute Force 19:10:25.800 --> 19:10:28.542 align:start position:0% um it can be in clear text Brute Force attacks<19:10:26.296> VLAN<19:10:27.296> hopping<19:10:27.720> man<19:10:28.080> in<19:10:28.320> the<19:10:28.440> middle 19:10:28.542 --> 19:10:28.552 align:start position:0% attacks VLAN hopping man in the middle 19:10:28.552 --> 19:10:30.950 align:start position:0% attacks VLAN hopping man in the middle and<19:10:28.976> then<19:10:29.160> exploits<19:10:29.872> versus<19:10:30.120> vulnerabilities 19:10:30.950 --> 19:10:30.960 align:start position:0% and then exploits versus vulnerabilities 19:10:30.960 --> 19:10:36.590 align:start position:0% and then exploits versus vulnerabilities that's<19:10:31.856> all<19:10:32.104> for<19:10:32.280> now<19:10:32.464> thanks<19:10:32.872> for<19:10:33.000> listening 19:10:36.590 --> 19:10:36.600 align:start position:0% 19:10:36.600 --> 19:10:45.134 align:start position:0% [Music] 19:10:45.134 --> 19:10:45.144 align:start position:0% [Music] 19:10:45.144 --> 19:10:56.270 align:start position:0% [Music] thank<19:10:46.144> you 19:10:56.270 --> 19:10:56.280 align:start position:0% 19:10:56.280 --> 19:11:00.166 align:start position:0% network<19:10:57.176> security<19:10:57.800> threat<19:10:58.800> mitigation<19:10:59.400> and 19:11:00.166 --> 19:11:00.176 align:start position:0% network security threat mitigation and 19:11:00.176 --> 19:11:02.926 align:start position:0% network security threat mitigation and user<19:11:00.656> education 19:11:02.926 --> 19:11:02.936 align:start position:0% user education 19:11:02.936 --> 19:11:04.846 align:start position:0% user education we've<19:11:03.480> now<19:11:03.656> talked<19:11:04.080> about<19:11:04.256> a<19:11:04.496> lot<19:11:04.616> of<19:11:04.744> the 19:11:04.846 --> 19:11:04.856 align:start position:0% we've now talked about a lot of the 19:11:04.856 --> 19:11:06.822 align:start position:0% we've now talked about a lot of the different<19:11:05.104> types<19:11:05.760> of<19:11:05.872> attacks<19:11:06.424> and<19:11:06.600> security 19:11:06.822 --> 19:11:06.832 align:start position:0% different types of attacks and security 19:11:06.832 --> 19:11:09.286 align:start position:0% different types of attacks and security threats<19:11:07.680> that<19:11:07.920> you<19:11:08.040> encounter<19:11:08.576> in<19:11:09.176> today's 19:11:09.286 --> 19:11:09.296 align:start position:0% threats that you encounter in today's 19:11:09.296 --> 19:11:11.630 align:start position:0% threats that you encounter in today's world<19:11:09.656> when<19:11:09.960> it<19:11:10.080> comes<19:11:10.320> to<19:11:10.440> your<19:11:10.552> network<19:11:10.744> and 19:11:11.630 --> 19:11:11.640 align:start position:0% world when it comes to your network and 19:11:11.640 --> 19:11:14.502 align:start position:0% world when it comes to your network and we've<19:11:11.936> talked<19:11:12.176> about<19:11:12.240> ways<19:11:12.960> to<19:11:13.504> protect<19:11:14.160> from 19:11:14.502 --> 19:11:14.512 align:start position:0% we've talked about ways to protect from 19:11:14.512 --> 19:11:18.414 align:start position:0% we've talked about ways to protect from these<19:11:14.760> threats<19:11:15.496> from<19:11:16.496> attacks<19:11:17.104> to<19:11:17.760> antivirus 19:11:18.414 --> 19:11:18.424 align:start position:0% these threats from attacks to antivirus 19:11:18.424 --> 19:11:20.862 align:start position:0% these threats from attacks to antivirus software<19:11:18.784> and<19:11:19.016> so<19:11:19.192> on<19:11:19.376> but<19:11:20.216> let's<19:11:20.512> talk<19:11:20.696> a 19:11:20.862 --> 19:11:20.872 align:start position:0% software and so on but let's talk a 19:11:20.872 --> 19:11:23.326 align:start position:0% software and so on but let's talk a little<19:11:21.000> further<19:11:21.360> about<19:11:21.600> how<19:11:21.960> we<19:11:22.192> can<19:11:22.440> mitigate 19:11:23.326 --> 19:11:23.336 align:start position:0% little further about how we can mitigate 19:11:23.336 --> 19:11:26.270 align:start position:0% little further about how we can mitigate these<19:11:23.872> threats<19:11:24.240> and<19:11:25.080> if<19:11:25.320> that<19:11:25.552> word<19:11:25.680> is<19:11:25.920> new<19:11:26.104> to 19:11:26.270 --> 19:11:26.280 align:start position:0% these threats and if that word is new to 19:11:26.280 --> 19:11:27.710 align:start position:0% these threats and if that word is new to you<19:11:26.400> the<19:11:26.872> first<19:11:27.000> thing<19:11:27.176> we're<19:11:27.296> going<19:11:27.480> to<19:11:27.536> talk 19:11:27.710 --> 19:11:27.720 align:start position:0% you the first thing we're going to talk 19:11:27.720 --> 19:11:31.542 align:start position:0% you the first thing we're going to talk about<19:11:27.896> is<19:11:28.320> what<19:11:28.744> threat<19:11:29.280> mitigation<19:11:29.936> means 19:11:31.542 --> 19:11:31.552 align:start position:0% about is what threat mitigation means 19:11:31.552 --> 19:11:33.590 align:start position:0% about is what threat mitigation means we're<19:11:32.040> then<19:11:32.216> going<19:11:32.400> to<19:11:32.512> identify<19:11:32.936> some<19:11:33.240> of<19:11:33.360> the 19:11:33.590 --> 19:11:33.600 align:start position:0% we're then going to identify some of the 19:11:33.600 --> 19:11:36.414 align:start position:0% we're then going to identify some of the steps<19:11:34.016> in<19:11:34.320> a<19:11:34.552> good<19:11:34.744> protection<19:11:35.512> strategy 19:11:36.414 --> 19:11:36.424 align:start position:0% steps in a good protection strategy 19:11:36.424 --> 19:11:40.246 align:start position:0% steps in a good protection strategy these<19:11:37.320> include<19:11:37.640> developing<19:11:38.640> strong<19:11:39.480> security 19:11:40.246 --> 19:11:40.256 align:start position:0% these include developing strong security 19:11:40.256 --> 19:11:43.430 align:start position:0% these include developing strong security policies<19:11:41.656> monitoring<19:11:42.656> the<19:11:42.832> threats<19:11:43.144> on<19:11:43.256> your 19:11:43.430 --> 19:11:43.440 align:start position:0% policies monitoring the threats on your 19:11:43.440 --> 19:11:44.566 align:start position:0% policies monitoring the threats on your network<19:11:43.552> something<19:11:43.976> that<19:11:44.160> we've<19:11:44.336> talked 19:11:44.566 --> 19:11:44.576 align:start position:0% network something that we've talked 19:11:44.576 --> 19:11:47.030 align:start position:0% network something that we've talked about<19:11:44.640> in<19:11:44.824> the<19:11:45.000> past<19:11:45.120> a<19:11:46.016> hugely<19:11:46.320> important<19:11:46.800> one 19:11:47.030 --> 19:11:47.040 align:start position:0% about in the past a hugely important one 19:11:47.040 --> 19:11:50.270 align:start position:0% about in the past a hugely important one educating<19:11:47.936> users<19:11:48.480> since<19:11:49.320> almost<19:11:49.744> all<19:11:50.160> the 19:11:50.270 --> 19:11:50.280 align:start position:0% educating users since almost all the 19:11:50.280 --> 19:11:52.606 align:start position:0% educating users since almost all the threats<19:11:50.640> we've<19:11:50.936> talked<19:11:51.176> about<19:11:51.296> in<19:11:52.192> some<19:11:52.376> way 19:11:52.606 --> 19:11:52.616 align:start position:0% threats we've talked about in some way 19:11:52.616 --> 19:11:55.070 align:start position:0% threats we've talked about in some way shape<19:11:53.040> or<19:11:53.280> form<19:11:53.464> have<19:11:54.240> to<19:11:54.424> do<19:11:54.480> with<19:11:54.656> what<19:11:54.896> we 19:11:55.070 --> 19:11:55.080 align:start position:0% shape or form have to do with what we 19:11:55.080 --> 19:11:56.990 align:start position:0% shape or form have to do with what we call<19:11:55.256> social<19:11:55.744> engineering 19:11:56.990 --> 19:11:57.000 align:start position:0% call social engineering 19:11:57.000 --> 19:11:58.846 align:start position:0% call social engineering in<19:11:57.480> other<19:11:57.600> words<19:11:57.720> getting<19:11:58.192> someone<19:11:58.440> to<19:11:58.680> do 19:11:58.846 --> 19:11:58.856 align:start position:0% in other words getting someone to do 19:11:58.856 --> 19:12:00.414 align:start position:0% in other words getting someone to do what<19:11:59.040> you<19:11:59.160> want<19:11:59.336> them<19:11:59.464> to<19:11:59.640> do<19:11:59.760> for<19:12:00.176> instance 19:12:00.414 --> 19:12:00.424 align:start position:0% what you want them to do for instance 19:12:00.424 --> 19:12:02.206 align:start position:0% what you want them to do for instance give<19:12:00.896> them<19:12:01.080> your<19:12:01.376> password 19:12:02.206 --> 19:12:02.216 align:start position:0% give them your password 19:12:02.216 --> 19:12:05.502 align:start position:0% give them your password automating<19:12:03.120> scanning<19:12:03.896> and<19:12:04.376> updates<19:12:04.856> both 19:12:05.502 --> 19:12:05.512 align:start position:0% automating scanning and updates both 19:12:05.512 --> 19:12:07.734 align:start position:0% automating scanning and updates both from<19:12:05.936> uh<19:12:06.360> updates<19:12:06.720> of<19:12:07.016> the<19:12:07.144> operating<19:12:07.440> system 19:12:07.734 --> 19:12:07.744 align:start position:0% from uh updates of the operating system 19:12:07.744 --> 19:12:10.366 align:start position:0% from uh updates of the operating system and<19:12:08.104> from<19:12:08.336> the<19:12:08.464> virus<19:12:08.760> scan<19:12:09.000> program<19:12:09.376> and 19:12:10.366 --> 19:12:10.376 align:start position:0% and from the virus scan program and 19:12:10.376 --> 19:12:13.134 align:start position:0% and from the virus scan program and patches<19:12:10.976> and<19:12:11.160> updates<19:12:11.512> for<19:12:12.296> our<19:12:12.480> operating 19:12:13.134 --> 19:12:13.144 align:start position:0% patches and updates for our operating 19:12:13.144 --> 19:12:15.822 align:start position:0% patches and updates for our operating systems<19:12:13.552> and<19:12:13.744> our<19:12:13.920> software 19:12:15.822 --> 19:12:15.832 align:start position:0% systems and our software 19:12:15.832 --> 19:12:19.734 align:start position:0% systems and our software so<19:12:16.496> what<19:12:17.400> is<19:12:17.576> mitigation<19:12:18.240> one<19:12:19.080> of<19:12:19.192> the<19:12:19.320> only 19:12:19.734 --> 19:12:19.744 align:start position:0% so what is mitigation one of the only 19:12:19.744 --> 19:12:22.134 align:start position:0% so what is mitigation one of the only ways<19:12:20.216> that<19:12:20.400> a<19:12:20.512> network<19:12:20.640> can<19:12:20.872> stand<19:12:21.120> a<19:12:21.424> chance 19:12:22.134 --> 19:12:22.144 align:start position:0% ways that a network can stand a chance 19:12:22.144 --> 19:12:24.470 align:start position:0% ways that a network can stand a chance against<19:12:22.616> attacks<19:12:23.336> is<19:12:23.872> to<19:12:24.056> do<19:12:24.240> something 19:12:24.470 --> 19:12:24.480 align:start position:0% against attacks is to do something 19:12:24.480 --> 19:12:27.526 align:start position:0% against attacks is to do something before<19:12:24.832> the<19:12:25.256> attack<19:12:25.440> is<19:12:25.856> made<19:12:26.176> isn't<19:12:27.176> it<19:12:27.296> said 19:12:27.526 --> 19:12:27.536 align:start position:0% before the attack is made isn't it said 19:12:27.536 --> 19:12:29.326 align:start position:0% before the attack is made isn't it said that<19:12:27.784> an<19:12:28.256> ounce<19:12:28.256> of<19:12:28.496> prevention<19:12:28.800> is<19:12:28.976> worth<19:12:29.160> a 19:12:29.326 --> 19:12:29.336 align:start position:0% that an ounce of prevention is worth a 19:12:29.336 --> 19:12:31.606 align:start position:0% that an ounce of prevention is worth a pound<19:12:29.512> of<19:12:29.760> cure<19:12:30.000> well<19:12:30.784> this<19:12:31.016> means<19:12:31.256> more<19:12:31.440> than 19:12:31.606 --> 19:12:31.616 align:start position:0% pound of cure well this means more than 19:12:31.616 --> 19:12:34.070 align:start position:0% pound of cure well this means more than just<19:12:31.856> having<19:12:32.104> anti-virus<19:12:33.056> and<19:12:33.296> firewalls<19:12:33.896> in 19:12:34.070 --> 19:12:34.080 align:start position:0% just having anti-virus and firewalls in 19:12:34.080 --> 19:12:36.046 align:start position:0% just having anti-virus and firewalls in place<19:12:34.256> those<19:12:34.856> things<19:12:35.040> are<19:12:35.280> great<19:12:35.464> but<19:12:35.824> they 19:12:36.046 --> 19:12:36.056 align:start position:0% place those things are great but they 19:12:36.056 --> 19:12:38.150 align:start position:0% place those things are great but they can<19:12:36.296> only<19:12:36.536> stop<19:12:37.080> an<19:12:37.376> attack<19:12:37.552> that's<19:12:37.920> already 19:12:38.150 --> 19:12:38.160 align:start position:0% can only stop an attack that's already 19:12:38.160 --> 19:12:40.310 align:start position:0% can only stop an attack that's already being<19:12:38.512> made<19:12:38.760> really<19:12:39.480> the<19:12:39.720> best<19:12:39.896> way<19:12:40.144> to 19:12:40.310 --> 19:12:40.320 align:start position:0% being made really the best way to 19:12:40.320 --> 19:12:42.470 align:start position:0% being made really the best way to protect<19:12:40.616> a<19:12:40.976> network<19:12:41.160> is<19:12:41.936> to<19:12:42.176> set<19:12:42.296> up 19:12:42.470 --> 19:12:42.480 align:start position:0% protect a network is to set up 19:12:42.480 --> 19:12:45.230 align:start position:0% protect a network is to set up prevention<19:12:43.080> measures<19:12:43.920> before<19:12:44.336> an<19:12:44.760> attack<19:12:44.872> can 19:12:45.230 --> 19:12:45.240 align:start position:0% prevention measures before an attack can 19:12:45.240 --> 19:12:46.310 align:start position:0% prevention measures before an attack can happen 19:12:46.310 --> 19:12:46.320 align:start position:0% happen 19:12:46.320 --> 19:12:49.006 align:start position:0% happen the<19:12:46.800> idiom<19:12:47.216> of<19:12:47.824> an<19:12:48.296> ounce<19:12:48.296> prevention<19:12:48.784> is 19:12:49.006 --> 19:12:49.016 align:start position:0% the idiom of an ounce prevention is 19:12:49.016 --> 19:12:51.046 align:start position:0% the idiom of an ounce prevention is worth<19:12:49.144> a<19:12:49.376> pound<19:12:49.504> of<19:12:49.744> cure<19:12:49.976> means<19:12:50.824> that<19:12:50.936> you 19:12:51.046 --> 19:12:51.056 align:start position:0% worth a pound of cure means that you 19:12:51.056 --> 19:12:53.750 align:start position:0% worth a pound of cure means that you save<19:12:51.296> a<19:12:51.656> huge<19:12:52.080> amount<19:12:52.320> of<19:12:52.440> trouble<19:12:52.760> by 19:12:53.750 --> 19:12:53.760 align:start position:0% save a huge amount of trouble by 19:12:53.760 --> 19:12:55.310 align:start position:0% save a huge amount of trouble by preventing<19:12:54.296> the<19:12:54.536> trouble<19:12:54.720> from<19:12:55.080> even 19:12:55.310 --> 19:12:55.320 align:start position:0% preventing the trouble from even 19:12:55.320 --> 19:12:57.822 align:start position:0% preventing the trouble from even happening<19:12:55.920> so<19:12:56.512> one<19:12:56.760> of<19:12:56.824> the<19:12:56.936> best<19:12:57.056> ways<19:12:57.480> to<19:12:57.656> do 19:12:57.822 --> 19:12:57.832 align:start position:0% happening so one of the best ways to do 19:12:57.832 --> 19:13:00.350 align:start position:0% happening so one of the best ways to do that<19:12:58.016> is<19:12:58.440> to<19:12:58.856> mitigate<19:12:59.464> the<19:12:59.824> threats<19:13:00.056> that<19:13:00.240> are 19:13:00.350 --> 19:13:00.360 align:start position:0% that is to mitigate the threats that are 19:13:00.360 --> 19:13:03.286 align:start position:0% that is to mitigate the threats that are made<19:13:00.480> on<19:13:00.656> your<19:13:00.784> network<19:13:01.464> mitigation<19:13:02.464> is<19:13:03.120> a 19:13:03.286 --> 19:13:03.296 align:start position:0% made on your network mitigation is a 19:13:03.296 --> 19:13:04.366 align:start position:0% made on your network mitigation is a word<19:13:03.424> that<19:13:03.600> doesn't<19:13:03.720> just<19:13:03.896> apply<19:13:04.192> to 19:13:04.366 --> 19:13:04.376 align:start position:0% word that doesn't just apply to 19:13:04.376 --> 19:13:06.414 align:start position:0% word that doesn't just apply to networking<19:13:04.856> but<19:13:05.160> in<19:13:05.280> this<19:13:05.464> case<19:13:05.696> we're 19:13:06.414 --> 19:13:06.424 align:start position:0% networking but in this case we're 19:13:06.424 --> 19:13:07.606 align:start position:0% networking but in this case we're talking<19:13:06.600> about<19:13:06.832> it<19:13:07.016> in<19:13:07.144> the<19:13:07.320> sense<19:13:07.440> of 19:13:07.606 --> 19:13:07.616 align:start position:0% talking about it in the sense of 19:13:07.616 --> 19:13:10.486 align:start position:0% talking about it in the sense of lessening<19:13:08.216> of<19:13:08.400> a<19:13:08.512> chance<19:13:08.760> of<19:13:09.176> an<19:13:09.360> attack<19:13:09.536> by 19:13:10.486 --> 19:13:10.496 align:start position:0% lessening of a chance of an attack by 19:13:10.496 --> 19:13:12.470 align:start position:0% lessening of a chance of an attack by using<19:13:10.856> mitigation<19:13:11.400> you're<19:13:11.760> taking<19:13:12.000> measures 19:13:12.470 --> 19:13:12.480 align:start position:0% using mitigation you're taking measures 19:13:12.480 --> 19:13:15.350 align:start position:0% using mitigation you're taking measures to<19:13:12.832> reduce<19:13:13.080> the<19:13:13.552> frequency<19:13:13.976> of<19:13:14.280> attacks<19:13:14.696> the 19:13:15.350 --> 19:13:15.360 align:start position:0% to reduce the frequency of attacks the 19:13:15.360 --> 19:13:17.206 align:start position:0% to reduce the frequency of attacks the size<19:13:15.536> of<19:13:15.784> those<19:13:15.960> attacks<19:13:16.376> when<19:13:16.616> and<19:13:16.856> if<19:13:17.040> they 19:13:17.206 --> 19:13:17.216 align:start position:0% size of those attacks when and if they 19:13:17.216 --> 19:13:20.454 align:start position:0% size of those attacks when and if they take<19:13:17.400> place<19:13:17.896> how<19:13:18.896> severely<19:13:19.376> most<19:13:20.040> importantly 19:13:20.454 --> 19:13:20.464 align:start position:0% take place how severely most importantly 19:13:20.464 --> 19:13:22.486 align:start position:0% take place how severely most importantly they're<19:13:20.696> going<19:13:20.872> to<19:13:21.000> impact<19:13:21.296> your<19:13:21.600> network<19:13:21.784> we 19:13:22.486 --> 19:13:22.496 align:start position:0% they're going to impact your network we 19:13:22.496 --> 19:13:24.526 align:start position:0% they're going to impact your network we need<19:13:22.616> to<19:13:22.800> have<19:13:22.920> a<19:13:23.216> strategy<19:13:23.640> in<19:13:24.000> place<19:13:24.176> in 19:13:24.526 --> 19:13:24.536 align:start position:0% need to have a strategy in place in 19:13:24.536 --> 19:13:27.230 align:start position:0% need to have a strategy in place in order<19:13:24.784> to<19:13:25.144> mitigate<19:13:25.616> threats<19:13:26.160> and<19:13:26.760> make<19:13:26.936> life 19:13:27.230 --> 19:13:27.240 align:start position:0% order to mitigate threats and make life 19:13:27.240 --> 19:13:29.814 align:start position:0% order to mitigate threats and make life on<19:13:27.600> the<19:13:27.784> network<19:13:27.960> easier 19:13:29.814 --> 19:13:29.824 align:start position:0% on the network easier 19:13:29.824 --> 19:13:33.286 align:start position:0% on the network easier so<19:13:30.536> step<19:13:31.376> one<19:13:31.680> of<19:13:32.216> the<19:13:32.336> mitigation<19:13:32.760> strategy 19:13:33.286 --> 19:13:33.296 align:start position:0% so step one of the mitigation strategy 19:13:33.296 --> 19:13:35.926 align:start position:0% so step one of the mitigation strategy needs<19:13:33.656> to<19:13:33.784> be<19:13:33.832> to<19:13:34.080> set<19:13:34.256> up<19:13:34.376> rules<19:13:34.920> and<19:13:35.400> policies 19:13:35.926 --> 19:13:35.936 align:start position:0% needs to be to set up rules and policies 19:13:35.936 --> 19:13:38.566 align:start position:0% needs to be to set up rules and policies within<19:13:36.424> a<19:13:36.600> network<19:13:36.744> users<19:13:37.744> are<19:13:37.920> set<19:13:38.104> up<19:13:38.216> by<19:13:38.464> the 19:13:38.566 --> 19:13:38.576 align:start position:0% within a network users are set up by the 19:13:38.576 --> 19:13:40.486 align:start position:0% within a network users are set up by the administrator<19:13:39.120> and<19:13:39.360> need<19:13:39.536> to<19:13:39.656> be<19:13:39.784> agreed<19:13:40.192> upon 19:13:40.486 --> 19:13:40.496 align:start position:0% administrator and need to be agreed upon 19:13:40.496 --> 19:13:42.494 align:start position:0% administrator and need to be agreed upon by<19:13:40.920> all<19:13:41.104> the<19:13:41.216> high<19:13:41.400> up<19:13:41.576> people<19:13:41.824> on<19:13:42.120> the<19:13:42.240> network 19:13:42.494 --> 19:13:42.504 align:start position:0% by all the high up people on the network 19:13:42.504 --> 19:13:44.990 align:start position:0% by all the high up people on the network and<19:13:43.504> all<19:13:43.976> the<19:13:44.104> high<19:13:44.216> up<19:13:44.400> people<19:13:44.576> in<19:13:44.824> your 19:13:44.990 --> 19:13:45.000 align:start position:0% and all the high up people in your 19:13:45.000 --> 19:13:48.414 align:start position:0% and all the high up people in your corporation<19:13:45.744> they<19:13:46.744> then<19:13:46.920> need<19:13:47.104> to<19:13:47.216> be<19:13:47.464> told<19:13:47.824> to 19:13:48.414 --> 19:13:48.424 align:start position:0% corporation they then need to be told to 19:13:48.424 --> 19:13:50.814 align:start position:0% corporation they then need to be told to all<19:13:48.720> of<19:13:48.832> the<19:13:49.016> users<19:13:49.376> these<19:13:50.280> rules<19:13:50.464> should<19:13:50.696> be 19:13:50.814 --> 19:13:50.824 align:start position:0% all of the users these rules should be 19:13:50.824 --> 19:13:52.790 align:start position:0% all of the users these rules should be standard<19:13:51.296> throughout<19:13:51.784> the<19:13:52.016> network<19:13:52.192> with 19:13:52.790 --> 19:13:52.800 align:start position:0% standard throughout the network with 19:13:52.800 --> 19:13:54.822 align:start position:0% standard throughout the network with very<19:13:52.976> few<19:13:53.216> exceptions<19:13:53.824> because<19:13:54.424> these 19:13:54.822 --> 19:13:54.832 align:start position:0% very few exceptions because these 19:13:54.832 --> 19:13:56.814 align:start position:0% very few exceptions because these exceptions<19:13:55.256> easily<19:13:55.856> lead<19:13:56.040> to<19:13:56.280> a<19:13:56.400> breach<19:13:56.640> in 19:13:56.814 --> 19:13:56.824 align:start position:0% exceptions easily lead to a breach in 19:13:56.824 --> 19:13:57.774 align:start position:0% exceptions easily lead to a breach in security 19:13:57.774 --> 19:13:57.784 align:start position:0% security 19:13:57.784 --> 19:13:59.750 align:start position:0% security one<19:13:58.320> of<19:13:58.440> the<19:13:58.552> rules<19:13:58.856> that<19:13:59.040> needs<19:13:59.216> to<19:13:59.280> be<19:13:59.464> set<19:13:59.640> up 19:13:59.750 --> 19:13:59.760 align:start position:0% one of the rules that needs to be set up 19:13:59.760 --> 19:14:02.094 align:start position:0% one of the rules that needs to be set up for<19:14:00.056> instance<19:14:00.296> is<19:14:00.720> what<19:14:01.192> can<19:14:01.376> users<19:14:01.800> download 19:14:02.094 --> 19:14:02.104 align:start position:0% for instance is what can users download 19:14:02.104 --> 19:14:04.734 align:start position:0% for instance is what can users download such<19:14:02.576> as<19:14:02.760> applications<19:14:03.360> can<19:14:04.320> they<19:14:04.496> download 19:14:04.734 --> 19:14:04.744 align:start position:0% such as applications can they download 19:14:04.744 --> 19:14:07.070 align:start position:0% such as applications can they download stuff<19:14:05.104> like<19:14:05.400> browsers<19:14:06.176> well<19:14:06.536> some<19:14:06.832> of<19:14:06.960> them 19:14:07.070 --> 19:14:07.080 align:start position:0% stuff like browsers well some of them 19:14:07.080 --> 19:14:09.110 align:start position:0% stuff like browsers well some of them are<19:14:07.256> trustable<19:14:07.680> but<19:14:08.216> are<19:14:08.400> we<19:14:08.512> going<19:14:08.640> to<19:14:08.824> trust 19:14:09.110 --> 19:14:09.120 align:start position:0% are trustable but are we going to trust 19:14:09.120 --> 19:14:11.454 align:start position:0% are trustable but are we going to trust people<19:14:09.600> on<19:14:10.192> our<19:14:10.320> Network<19:14:10.496> to<19:14:10.976> choose<19:14:11.216> the 19:14:11.454 --> 19:14:11.464 align:start position:0% people on our Network to choose the 19:14:11.464 --> 19:14:13.366 align:start position:0% people on our Network to choose the browsers<19:14:11.824> that<19:14:12.296> are<19:14:12.536> actually<19:14:12.832> worth 19:14:13.366 --> 19:14:13.376 align:start position:0% browsers that are actually worth 19:14:13.376 --> 19:14:14.454 align:start position:0% browsers that are actually worth trusting 19:14:14.454 --> 19:14:14.464 align:start position:0% trusting 19:14:14.464 --> 19:14:16.606 align:start position:0% trusting the<19:14:15.000> administrator<19:14:15.424> needs<19:14:15.832> to<19:14:15.896> be<19:14:16.080> wary<19:14:16.440> of 19:14:16.606 --> 19:14:16.616 align:start position:0% the administrator needs to be wary of 19:14:16.616 --> 19:14:18.590 align:start position:0% the administrator needs to be wary of just<19:14:16.800> about<19:14:16.920> any<19:14:17.280> program<19:14:17.576> that<19:14:17.936> a<19:14:18.056> user<19:14:18.360> could 19:14:18.590 --> 19:14:18.600 align:start position:0% just about any program that a user could 19:14:18.600 --> 19:14:20.630 align:start position:0% just about any program that a user could download<19:14:18.960> and<19:14:19.744> as<19:14:19.856> we<19:14:19.976> learned<19:14:20.216> in<19:14:20.336> the<19:14:20.512> last 19:14:20.630 --> 19:14:20.640 align:start position:0% download and as we learned in the last 19:14:20.640 --> 19:14:23.502 align:start position:0% download and as we learned in the last module<19:14:21.080> viruses<19:14:22.080> can<19:14:22.320> hide<19:14:22.496> within<19:14:22.976> programs 19:14:23.502 --> 19:14:23.512 align:start position:0% module viruses can hide within programs 19:14:23.512 --> 19:14:26.094 align:start position:0% module viruses can hide within programs they<19:14:23.696> don't<19:14:23.872> just<19:14:24.056> attack<19:14:24.600> out<19:14:24.960> of<19:14:25.144> nowhere<19:14:25.440> a 19:14:26.094 --> 19:14:26.104 align:start position:0% they don't just attack out of nowhere a 19:14:26.104 --> 19:14:27.350 align:start position:0% they don't just attack out of nowhere a user<19:14:26.336> on<19:14:26.512> your<19:14:26.640> network<19:14:26.760> could<19:14:27.056> easily 19:14:27.350 --> 19:14:27.360 align:start position:0% user on your network could easily 19:14:27.360 --> 19:14:28.846 align:start position:0% user on your network could easily download<19:14:27.536> a<19:14:27.784> virus<19:14:28.016> without<19:14:28.080> even<19:14:28.376> knowing<19:14:28.744> it 19:14:28.846 --> 19:14:28.856 align:start position:0% download a virus without even knowing it 19:14:28.856 --> 19:14:30.710 align:start position:0% download a virus without even knowing it and<19:14:29.040> then<19:14:29.160> they<19:14:29.512> end<19:14:29.760> up<19:14:29.872> infecting<19:14:30.360> not<19:14:30.536> just 19:14:30.710 --> 19:14:30.720 align:start position:0% and then they end up infecting not just 19:14:30.720 --> 19:14:33.350 align:start position:0% and then they end up infecting not just their<19:14:30.960> computer<19:14:31.144> but<19:14:31.856> the<19:14:32.040> entire<19:14:32.336> network<19:14:32.576> so 19:14:33.350 --> 19:14:33.360 align:start position:0% their computer but the entire network so 19:14:33.360 --> 19:14:34.910 align:start position:0% their computer but the entire network so a<19:14:33.536> rule<19:14:33.832> needs<19:14:34.080> to<19:14:34.080> be<19:14:34.192> put<19:14:34.320> in<19:14:34.440> place<19:14:34.680> that 19:14:34.910 --> 19:14:34.920 align:start position:0% a rule needs to be put in place that 19:14:34.920 --> 19:14:36.470 align:start position:0% a rule needs to be put in place that says<19:14:35.160> whether<19:14:35.464> or<19:14:35.640> not<19:14:35.696> downloading<19:14:36.360> of 19:14:36.470 --> 19:14:36.480 align:start position:0% says whether or not downloading of 19:14:36.480 --> 19:14:38.686 align:start position:0% says whether or not downloading of applications<19:14:36.960> is<19:14:37.440> allowed<19:14:37.856> and<19:14:38.336> if<19:14:38.464> it<19:14:38.576> is 19:14:38.686 --> 19:14:38.696 align:start position:0% applications is allowed and if it is 19:14:38.696 --> 19:14:41.030 align:start position:0% applications is allowed and if it is from<19:14:38.936> what<19:14:39.176> sources<19:14:39.656> you<19:14:40.320> may<19:14:40.440> even<19:14:40.616> want<19:14:40.856> to 19:14:41.030 --> 19:14:41.040 align:start position:0% from what sources you may even want to 19:14:41.040 --> 19:14:43.134 align:start position:0% from what sources you may even want to limit<19:14:41.216> the<19:14:41.696> fact<19:14:41.936> that<19:14:42.296> people<19:14:42.600> can<19:14:42.896> download 19:14:43.134 --> 19:14:43.144 align:start position:0% limit the fact that people can download 19:14:43.144 --> 19:14:45.774 align:start position:0% limit the fact that people can download by<19:14:43.680> shutting<19:14:44.160> off<19:14:44.464> their<19:14:44.824> user<19:14:45.176> rights<19:14:45.536> to 19:14:45.774 --> 19:14:45.784 align:start position:0% by shutting off their user rights to 19:14:45.784 --> 19:14:48.166 align:start position:0% by shutting off their user rights to download<19:14:45.960> or<19:14:46.496> to<19:14:46.744> install<19:14:47.160> programs<19:14:47.936> on<19:14:48.056> their 19:14:48.166 --> 19:14:48.176 align:start position:0% download or to install programs on their 19:14:48.176 --> 19:14:50.030 align:start position:0% download or to install programs on their network<19:14:48.360> if<19:14:49.144> they<19:14:49.256> can't<19:14:49.376> install<19:14:49.680> anything 19:14:50.030 --> 19:14:50.040 align:start position:0% network if they can't install anything 19:14:50.040 --> 19:14:52.606 align:start position:0% network if they can't install anything they<19:14:50.512> can<19:14:50.696> install<19:14:50.872> a<19:14:51.240> virus<19:14:51.536> another<19:14:52.256> major 19:14:52.606 --> 19:14:52.616 align:start position:0% they can install a virus another major 19:14:52.616 --> 19:14:54.526 align:start position:0% they can install a virus another major Rule<19:14:52.976> and<19:14:53.104> this<19:14:53.216> is<19:14:53.336> really<19:14:53.512> important<19:14:53.936> is<19:14:54.360> are 19:14:54.526 --> 19:14:54.536 align:start position:0% Rule and this is really important is are 19:14:54.536 --> 19:14:56.150 align:start position:0% Rule and this is really important is are they<19:14:54.656> allowed<19:14:54.960> to<19:14:55.016> use<19:14:55.192> outside<19:14:55.616> storage 19:14:56.150 --> 19:14:56.160 align:start position:0% they allowed to use outside storage 19:14:56.160 --> 19:15:00.950 align:start position:0% they allowed to use outside storage devices<19:14:56.824> such<19:14:57.480> as<19:14:58.160> uh<19:14:59.160> removable<19:15:00.056> hard<19:15:00.536> drives 19:15:00.950 --> 19:15:00.960 align:start position:0% devices such as uh removable hard drives 19:15:00.960 --> 19:15:04.246 align:start position:0% devices such as uh removable hard drives thumb<19:15:01.440> drives<19:15:01.976> flash<19:15:02.576> drives<19:15:03.176> and<19:15:04.016> storage 19:15:04.246 --> 19:15:04.256 align:start position:0% thumb drives flash drives and storage 19:15:04.256 --> 19:15:07.670 align:start position:0% thumb drives flash drives and storage CDs<19:15:05.296> any<19:15:06.296> one<19:15:06.600> of<19:15:06.784> these<19:15:07.016> media<19:15:07.504> storage 19:15:07.670 --> 19:15:07.680 align:start position:0% CDs any one of these media storage 19:15:07.680 --> 19:15:11.094 align:start position:0% CDs any one of these media storage devices<19:15:08.216> can<19:15:08.696> contain<19:15:09.056> malware<19:15:09.744> one<19:15:10.744> of<19:15:10.856> the 19:15:11.094 --> 19:15:11.104 align:start position:0% devices can contain malware one of the 19:15:11.104 --> 19:15:14.814 align:start position:0% devices can contain malware one of the uh<19:15:11.536> classic<19:15:12.536> examples<19:15:13.320> is 19:15:14.814 --> 19:15:14.824 align:start position:0% uh classic examples is 19:15:14.824 --> 19:15:17.206 align:start position:0% uh classic examples is someone<19:15:15.480> leaves<19:15:16.016> flash<19:15:16.376> drives<19:15:16.856> in<19:15:17.040> the 19:15:17.206 --> 19:15:17.216 align:start position:0% someone leaves flash drives in the 19:15:17.216 --> 19:15:19.606 align:start position:0% someone leaves flash drives in the parking<19:15:17.512> lot<19:15:18.176> when<19:15:18.832> you<19:15:19.080> find<19:15:19.256> the<19:15:19.504> flash 19:15:19.606 --> 19:15:19.616 align:start position:0% parking lot when you find the flash 19:15:19.616 --> 19:15:20.990 align:start position:0% parking lot when you find the flash drive<19:15:19.856> what's<19:15:20.160> the<19:15:20.400> first<19:15:20.464> thing<19:15:20.640> you<19:15:20.824> do<19:15:20.872> oh 19:15:20.990 --> 19:15:21.000 align:start position:0% drive what's the first thing you do oh 19:15:21.000 --> 19:15:22.430 align:start position:0% drive what's the first thing you do oh you<19:15:21.240> say<19:15:21.360> it's<19:15:21.480> a<19:15:21.656> brand<19:15:21.784> new<19:15:21.896> flash<19:15:22.080> drive<19:15:22.320> I'm 19:15:22.430 --> 19:15:22.440 align:start position:0% you say it's a brand new flash drive I'm 19:15:22.440 --> 19:15:24.286 align:start position:0% you say it's a brand new flash drive I'm going<19:15:22.552> to<19:15:22.616> put<19:15:22.800> it<19:15:22.856> in<19:15:22.976> my<19:15:23.104> computer<19:15:23.336> I<19:15:24.000> want<19:15:24.176> to 19:15:24.286 --> 19:15:24.296 align:start position:0% going to put it in my computer I want to 19:15:24.296 --> 19:15:26.030 align:start position:0% going to put it in my computer I want to test<19:15:24.424> it<19:15:24.600> out<19:15:24.784> see<19:15:25.080> what's<19:15:25.192> on<19:15:25.440> there<19:15:25.616> see<19:15:25.800> if<19:15:25.920> I 19:15:26.030 --> 19:15:26.040 align:start position:0% test it out see what's on there see if I 19:15:26.040 --> 19:15:28.070 align:start position:0% test it out see what's on there see if I can<19:15:26.104> find<19:15:26.216> the<19:15:26.464> owner<19:15:26.936> well<19:15:27.480> the<19:15:27.656> minute<19:15:27.832> they 19:15:28.070 --> 19:15:28.080 align:start position:0% can find the owner well the minute they 19:15:28.080 --> 19:15:29.862 align:start position:0% can find the owner well the minute they do<19:15:28.256> that<19:15:28.440> they've<19:15:28.856> just<19:15:28.976> infected<19:15:29.640> your 19:15:29.862 --> 19:15:29.872 align:start position:0% do that they've just infected your 19:15:29.872 --> 19:15:34.430 align:start position:0% do that they've just infected your system<19:15:30.296> and<19:15:31.144> your<19:15:31.440> network<19:15:31.760> with<19:15:32.760> a<19:15:33.056> virus<19:15:33.480> so 19:15:34.430 --> 19:15:34.440 align:start position:0% system and your network with a virus so 19:15:34.440 --> 19:15:36.526 align:start position:0% system and your network with a virus so we<19:15:34.800> need<19:15:34.920> to<19:15:35.040> make<19:15:35.336> sure<19:15:35.576> that<19:15:36.120> even<19:15:36.296> though 19:15:36.526 --> 19:15:36.536 align:start position:0% we need to make sure that even though 19:15:36.536 --> 19:15:38.206 align:start position:0% we need to make sure that even though the<19:15:36.784> person<19:15:36.896> might<19:15:37.256> not<19:15:37.440> be 19:15:38.206 --> 19:15:38.216 align:start position:0% the person might not be 19:15:38.216 --> 19:15:40.486 align:start position:0% the person might not be trying<19:15:38.760> or<19:15:39.296> mean<19:15:39.536> to<19:15:39.832> infect<19:15:40.144> the<19:15:40.320> network 19:15:40.486 --> 19:15:40.496 align:start position:0% trying or mean to infect the network 19:15:40.496 --> 19:15:42.526 align:start position:0% trying or mean to infect the network they<19:15:41.160> could<19:15:41.336> do<19:15:41.576> it<19:15:41.696> simply<19:15:42.056> because<19:15:42.176> they 19:15:42.526 --> 19:15:42.536 align:start position:0% they could do it simply because they 19:15:42.536 --> 19:15:44.326 align:start position:0% they could do it simply because they don't<19:15:42.656> understand<19:15:42.896> the<19:15:43.320> risks<19:15:43.920> that<19:15:44.160> are 19:15:44.326 --> 19:15:44.336 align:start position:0% don't understand the risks that are 19:15:44.336 --> 19:15:46.542 align:start position:0% don't understand the risks that are associated<19:15:44.824> with<19:15:45.176> flash<19:15:45.424> drives<19:15:45.960> and<19:15:46.320> outside 19:15:46.542 --> 19:15:46.552 align:start position:0% associated with flash drives and outside 19:15:46.552 --> 19:15:48.526 align:start position:0% associated with flash drives and outside storage<19:15:46.920> media<19:15:47.512> they<19:15:48.056> might<19:15:48.176> also<19:15:48.424> be 19:15:48.526 --> 19:15:48.536 align:start position:0% storage media they might also be 19:15:48.536 --> 19:15:49.846 align:start position:0% storage media they might also be bringing<19:15:48.832> stuff<19:15:49.016> from<19:15:49.256> their<19:15:49.376> home<19:15:49.552> computer 19:15:49.846 --> 19:15:49.856 align:start position:0% bringing stuff from their home computer 19:15:49.856 --> 19:15:52.542 align:start position:0% bringing stuff from their home computer which<19:15:50.400> very<19:15:50.576> well<19:15:50.760> could<19:15:50.936> have<19:15:51.176> a<19:15:51.424> virus<19:15:51.784> on<19:15:52.080> it 19:15:52.542 --> 19:15:52.552 align:start position:0% which very well could have a virus on it 19:15:52.552 --> 19:15:55.670 align:start position:0% which very well could have a virus on it so<19:15:52.976> storage<19:15:53.280> devices<19:15:53.896> could<19:15:54.896> contain<19:15:55.256> malware 19:15:55.670 --> 19:15:55.680 align:start position:0% so storage devices could contain malware 19:15:55.680 --> 19:15:57.526 align:start position:0% so storage devices could contain malware without<19:15:55.976> the<19:15:56.216> user<19:15:56.464> even<19:15:56.576> knowing<19:15:57.000> it<19:15:57.176> and 19:15:57.526 --> 19:15:57.536 align:start position:0% without the user even knowing it and 19:15:57.536 --> 19:15:59.326 align:start position:0% without the user even knowing it and this<19:15:57.784> isn't<19:15:58.080> something<19:15:58.256> you<19:15:58.552> want<19:15:58.680> to<19:15:58.800> risk<19:15:59.104> so 19:15:59.326 --> 19:15:59.336 align:start position:0% this isn't something you want to risk so 19:15:59.336 --> 19:16:01.366 align:start position:0% this isn't something you want to risk so a<19:15:59.576> policy<19:16:00.000> is<19:16:00.120> really<19:16:00.360> important 19:16:01.366 --> 19:16:01.376 align:start position:0% a policy is really important 19:16:01.376 --> 19:16:03.590 align:start position:0% a policy is really important other<19:16:01.920> things<19:16:02.160> such<19:16:02.512> as<19:16:02.640> this<19:16:02.872> would<19:16:03.176> include 19:16:03.590 --> 19:16:03.600 align:start position:0% other things such as this would include 19:16:03.600 --> 19:16:07.310 align:start position:0% other things such as this would include stuff<19:16:04.256> like<19:16:04.640> tailgating<19:16:05.640> when<19:16:06.296> someone<19:16:06.536> logs 19:16:07.310 --> 19:16:07.320 align:start position:0% stuff like tailgating when someone logs 19:16:07.320 --> 19:16:08.862 align:start position:0% stuff like tailgating when someone logs in 19:16:08.862 --> 19:16:08.872 align:start position:0% in 19:16:08.872 --> 19:16:11.630 align:start position:0% in uh<19:16:09.536> swipes<19:16:10.376> their<19:16:10.552> card<19:16:10.744> to<19:16:10.976> get<19:16:11.160> into<19:16:11.336> a 19:16:11.630 --> 19:16:11.640 align:start position:0% uh swipes their card to get into a 19:16:11.640 --> 19:16:13.310 align:start position:0% uh swipes their card to get into a building<19:16:11.824> in<19:16:12.120> the<19:16:12.240> morning<19:16:12.360> if<19:16:12.896> they<19:16:13.016> open<19:16:13.144> the 19:16:13.310 --> 19:16:13.320 align:start position:0% building in the morning if they open the 19:16:13.320 --> 19:16:15.526 align:start position:0% building in the morning if they open the door<19:16:13.504> for<19:16:13.680> someone<19:16:13.920> else<19:16:14.336> well<19:16:15.000> now<19:16:15.240> that 19:16:15.526 --> 19:16:15.536 align:start position:0% door for someone else well now that 19:16:15.536 --> 19:16:17.630 align:start position:0% door for someone else well now that person<19:16:15.784> just<19:16:16.192> got<19:16:16.376> in<19:16:16.552> without<19:16:16.800> being<19:16:17.216> audited 19:16:17.630 --> 19:16:17.640 align:start position:0% person just got in without being audited 19:16:17.640 --> 19:16:19.134 align:start position:0% person just got in without being audited we<19:16:17.872> didn't<19:16:18.056> have<19:16:18.240> they<19:16:18.424> didn't<19:16:18.600> have<19:16:18.720> to<19:16:18.784> swipe 19:16:19.134 --> 19:16:19.144 align:start position:0% we didn't have they didn't have to swipe 19:16:19.144 --> 19:16:21.110 align:start position:0% we didn't have they didn't have to swipe their<19:16:19.256> card<19:16:19.504> so<19:16:20.040> that's<19:16:20.216> a<19:16:20.512> pretty<19:16:20.696> major 19:16:21.110 --> 19:16:21.120 align:start position:0% their card so that's a pretty major 19:16:21.120 --> 19:16:23.470 align:start position:0% their card so that's a pretty major concern<19:16:21.656> when<19:16:21.960> it<19:16:22.144> comes<19:16:22.376> to<19:16:22.680> security 19:16:23.470 --> 19:16:23.480 align:start position:0% concern when it comes to security 19:16:23.480 --> 19:16:26.750 align:start position:0% concern when it comes to security another<19:16:24.480> one<19:16:24.856> uh<19:16:25.856> is<19:16:26.160> something<19:16:26.512> like 19:16:26.750 --> 19:16:26.760 align:start position:0% another one uh is something like 19:16:26.760 --> 19:16:28.430 align:start position:0% another one uh is something like shoulder<19:16:27.240> surfing<19:16:27.600> or<19:16:27.784> giving<19:16:27.960> out<19:16:28.192> your 19:16:28.430 --> 19:16:28.440 align:start position:0% shoulder surfing or giving out your 19:16:28.440 --> 19:16:30.286 align:start position:0% shoulder surfing or giving out your password<19:16:28.744> we<19:16:29.512> need<19:16:29.696> to<19:16:29.824> make<19:16:29.936> sure<19:16:30.056> the 19:16:30.286 --> 19:16:30.296 align:start position:0% password we need to make sure the 19:16:30.296 --> 19:16:32.862 align:start position:0% password we need to make sure the policies<19:16:30.720> of<19:16:30.960> how<19:16:31.192> passwords<19:16:31.856> are<19:16:32.040> reset<19:16:32.512> when 19:16:32.862 --> 19:16:32.872 align:start position:0% policies of how passwords are reset when 19:16:32.872 --> 19:16:34.542 align:start position:0% policies of how passwords are reset when they're<19:16:33.056> reset<19:16:33.480> and<19:16:33.896> who<19:16:34.016> you<19:16:34.144> can<19:16:34.256> give<19:16:34.440> them 19:16:34.542 --> 19:16:34.552 align:start position:0% they're reset and who you can give them 19:16:34.552 --> 19:16:37.366 align:start position:0% they're reset and who you can give them to<19:16:34.856> is<19:16:35.512> fairly<19:16:35.872> important<19:16:36.240> if<19:16:36.832> I<19:16:37.016> give<19:16:37.192> my 19:16:37.366 --> 19:16:37.376 align:start position:0% to is fairly important if I give my 19:16:37.376 --> 19:16:39.414 align:start position:0% to is fairly important if I give my password<19:16:37.680> to<19:16:38.104> my<19:16:38.336> wife<19:16:38.464> and<19:16:38.760> suddenly<19:16:39.056> my<19:16:39.296> wife 19:16:39.414 --> 19:16:39.424 align:start position:0% password to my wife and suddenly my wife 19:16:39.424 --> 19:16:41.630 align:start position:0% password to my wife and suddenly my wife becomes<19:16:39.832> my<19:16:40.144> ex-wife<19:16:40.680> she<19:16:41.104> could<19:16:41.280> do<19:16:41.400> some 19:16:41.630 --> 19:16:41.640 align:start position:0% becomes my ex-wife she could do some 19:16:41.640 --> 19:16:44.502 align:start position:0% becomes my ex-wife she could do some major<19:16:41.824> damage<19:16:42.360> to<19:16:42.896> me<19:16:43.016> and<19:16:43.192> to<19:16:43.376> my<19:16:43.552> company<19:16:43.800> by 19:16:44.502 --> 19:16:44.512 align:start position:0% major damage to me and to my company by 19:16:44.512 --> 19:16:46.846 align:start position:0% major damage to me and to my company by using<19:16:44.824> that<19:16:45.000> password<19:16:45.240> to<19:16:45.832> get<19:16:46.016> access<19:16:46.256> to 19:16:46.846 --> 19:16:46.856 align:start position:0% using that password to get access to 19:16:46.856 --> 19:16:49.606 align:start position:0% using that password to get access to private<19:16:47.280> information 19:16:49.606 --> 19:16:49.616 align:start position:0% 19:16:49.616 --> 19:16:53.526 align:start position:0% so<19:16:50.400> step<19:16:50.824> two<19:16:51.176> is<19:16:52.080> a<19:16:52.376> mitigation<19:16:52.856> strategy 19:16:53.526 --> 19:16:53.536 align:start position:0% so step two is a mitigation strategy 19:16:53.536 --> 19:16:56.862 align:start position:0% so step two is a mitigation strategy which<19:16:54.536> is<19:16:54.832> to<19:16:55.256> constantly<19:16:55.680> monitor<19:16:56.280> virus 19:16:56.862 --> 19:16:56.872 align:start position:0% which is to constantly monitor virus 19:16:56.872 --> 19:16:58.790 align:start position:0% which is to constantly monitor virus threats<19:16:57.360> as<19:16:57.960> you<19:16:58.144> might<19:16:58.320> already<19:16:58.496> know 19:16:58.790 --> 19:16:58.800 align:start position:0% threats as you might already know 19:16:58.800 --> 19:17:01.366 align:start position:0% threats as you might already know attackers<19:16:59.400> and<19:16:59.640> computer<19:16:59.872> hackers<19:17:00.600> are<19:17:01.080> very 19:17:01.366 --> 19:17:01.376 align:start position:0% attackers and computer hackers are very 19:17:01.376 --> 19:17:03.822 align:start position:0% attackers and computer hackers are very well<19:17:01.680> educated<19:17:02.160> when<19:17:02.576> it<19:17:02.760> comes<19:17:03.120> to<19:17:03.656> getting 19:17:03.822 --> 19:17:03.832 align:start position:0% well educated when it comes to getting 19:17:03.832 --> 19:17:06.950 align:start position:0% well educated when it comes to getting around<19:17:04.192> security<19:17:05.040> systems<19:17:05.872> This<19:17:06.424> Is<19:17:06.600> How<19:17:06.784> They 19:17:06.950 --> 19:17:06.960 align:start position:0% around security systems This Is How They 19:17:06.960 --> 19:17:09.230 align:start position:0% around security systems This Is How They infect<19:17:07.256> networks<19:17:07.856> and<19:17:08.400> when<19:17:08.576> their<19:17:08.760> attacks 19:17:09.230 --> 19:17:09.240 align:start position:0% infect networks and when their attacks 19:17:09.240 --> 19:17:11.270 align:start position:0% infect networks and when their attacks are<19:17:09.480> blocked<19:17:09.896> most<19:17:10.192> of<19:17:10.320> them<19:17:10.440> just<19:17:10.680> update<19:17:11.040> the 19:17:11.270 --> 19:17:11.280 align:start position:0% are blocked most of them just update the 19:17:11.280 --> 19:17:13.070 align:start position:0% are blocked most of them just update the attack<19:17:11.464> and<19:17:11.872> try<19:17:12.056> a<19:17:12.240> new<19:17:12.360> version<19:17:12.536> they<19:17:12.896> don't 19:17:13.070 --> 19:17:13.080 align:start position:0% attack and try a new version they don't 19:17:13.080 --> 19:17:14.750 align:start position:0% attack and try a new version they don't just<19:17:13.256> stop<19:17:13.552> so<19:17:14.216> this<19:17:14.336> is<19:17:14.464> why<19:17:14.576> the 19:17:14.750 --> 19:17:14.760 align:start position:0% just stop so this is why the 19:17:14.760 --> 19:17:16.910 align:start position:0% just stop so this is why the administrator<19:17:15.240> needs<19:17:15.656> to<19:17:15.720> be<19:17:15.832> as<19:17:16.080> on<19:17:16.320> top<19:17:16.496> of 19:17:16.910 --> 19:17:16.920 align:start position:0% administrator needs to be as on top of 19:17:16.920 --> 19:17:19.310 align:start position:0% administrator needs to be as on top of the<19:17:17.464> virus<19:17:17.824> versions<19:17:18.176> and<19:17:18.424> attackers<19:17:18.896> and<19:17:19.144> the 19:17:19.310 --> 19:17:19.320 align:start position:0% the virus versions and attackers and the 19:17:19.320 --> 19:17:21.110 align:start position:0% the virus versions and attackers and the threats<19:17:19.616> that<19:17:19.744> are<19:17:19.920> out<19:17:20.104> there<19:17:20.216> it's<19:17:20.760> up<19:17:20.936> to 19:17:21.110 --> 19:17:21.120 align:start position:0% threats that are out there it's up to 19:17:21.120 --> 19:17:22.670 align:start position:0% threats that are out there it's up to the<19:17:21.296> administrator<19:17:21.832> to<19:17:22.144> make<19:17:22.256> sure<19:17:22.440> that 19:17:22.670 --> 19:17:22.680 align:start position:0% the administrator to make sure that 19:17:22.680 --> 19:17:24.646 align:start position:0% the administrator to make sure that they're<19:17:22.976> up<19:17:23.400> to<19:17:23.576> date<19:17:23.696> and<19:17:23.872> research<19:17:24.296> is<19:17:24.424> being 19:17:24.646 --> 19:17:24.656 align:start position:0% they're up to date and research is being 19:17:24.656 --> 19:17:26.206 align:start position:0% they're up to date and research is being done<19:17:24.896> and<19:17:25.192> they're<19:17:25.376> knowledgeable<19:17:25.800> at<19:17:26.040> the 19:17:26.206 --> 19:17:26.216 align:start position:0% done and they're knowledgeable at the 19:17:26.216 --> 19:17:27.886 align:start position:0% done and they're knowledgeable at the newest<19:17:26.512> attacks<19:17:27.000> that<19:17:27.240> could<19:17:27.360> be<19:17:27.480> coming<19:17:27.656> to 19:17:27.886 --> 19:17:27.896 align:start position:0% newest attacks that could be coming to 19:17:27.896 --> 19:17:30.046 align:start position:0% newest attacks that could be coming to their<19:17:28.080> Network<19:17:28.320> again<19:17:29.216> it's<19:17:29.576> no<19:17:29.760> one<19:17:29.936> else 19:17:30.046 --> 19:17:30.056 align:start position:0% their Network again it's no one else 19:17:30.056 --> 19:17:31.606 align:start position:0% their Network again it's no one else that's<19:17:30.360> going<19:17:30.536> to<19:17:30.600> get<19:17:30.720> blamed<19:17:31.144> except<19:17:31.440> for 19:17:31.606 --> 19:17:31.616 align:start position:0% that's going to get blamed except for 19:17:31.616 --> 19:17:33.350 align:start position:0% that's going to get blamed except for the<19:17:31.800> administrator<19:17:32.280> when<19:17:32.640> someone<19:17:32.824> hacks<19:17:33.296> to 19:17:33.350 --> 19:17:33.360 align:start position:0% the administrator when someone hacks to 19:17:33.360 --> 19:17:35.206 align:start position:0% the administrator when someone hacks to the<19:17:33.536> network<19:17:33.720> so<19:17:34.376> not<19:17:34.552> only<19:17:34.680> do<19:17:34.856> we<19:17:34.976> need<19:17:35.104> to 19:17:35.206 --> 19:17:35.216 align:start position:0% the network so not only do we need to 19:17:35.216 --> 19:17:37.494 align:start position:0% the network so not only do we need to monitor<19:17:35.576> our<19:17:35.824> Network<19:17:36.056> we<19:17:36.784> need<19:17:36.896> to<19:17:37.080> monitor 19:17:37.494 --> 19:17:37.504 align:start position:0% monitor our Network we need to monitor 19:17:37.504 --> 19:17:40.246 align:start position:0% monitor our Network we need to monitor the<19:17:38.216> threats<19:17:38.640> that<19:17:38.872> are<19:17:39.056> out<19:17:39.360> there<19:17:39.480> and<19:17:40.080> this 19:17:40.246 --> 19:17:40.256 align:start position:0% the threats that are out there and this 19:17:40.256 --> 19:17:42.774 align:start position:0% the threats that are out there and this really<19:17:40.496> involves<19:17:41.040> doing<19:17:41.640> research<19:17:42.296> on<19:17:42.600> what 19:17:42.774 --> 19:17:42.784 align:start position:0% really involves doing research on what 19:17:42.784 --> 19:17:44.686 align:start position:0% really involves doing research on what the<19:17:42.960> latest<19:17:43.192> and<19:17:43.680> greatest<19:17:43.856> techniques<19:17:44.512> are 19:17:44.686 --> 19:17:44.696 align:start position:0% the latest and greatest techniques are 19:17:44.696 --> 19:17:47.030 align:start position:0% the latest and greatest techniques are to<19:17:45.000> hack<19:17:45.120> into<19:17:45.296> a<19:17:45.600> network 19:17:47.030 --> 19:17:47.040 align:start position:0% to hack into a network 19:17:47.040 --> 19:17:49.606 align:start position:0% to hack into a network step<19:17:47.512> three<19:17:47.824> is<19:17:48.000> user<19:17:48.480> education<19:17:48.896> which<19:17:49.320> is 19:17:49.606 --> 19:17:49.616 align:start position:0% step three is user education which is 19:17:49.616 --> 19:17:52.686 align:start position:0% step three is user education which is really<19:17:50.160> I<19:17:50.464> think<19:17:50.640> the<19:17:51.600> most<19:17:51.784> important<19:17:52.376> step 19:17:52.686 --> 19:17:52.696 align:start position:0% really I think the most important step 19:17:52.696 --> 19:17:55.670 align:start position:0% really I think the most important step that<19:17:53.696> we<19:17:53.872> have<19:17:54.056> out<19:17:54.480> there<19:17:54.656> it's<19:17:55.144> critical<19:17:55.504> to 19:17:55.670 --> 19:17:55.680 align:start position:0% that we have out there it's critical to 19:17:55.680 --> 19:17:57.646 align:start position:0% that we have out there it's critical to have<19:17:55.800> Network<19:17:56.040> users<19:17:56.512> educated<19:17:57.056> in<19:17:57.480> this 19:17:57.646 --> 19:17:57.656 align:start position:0% have Network users educated in this 19:17:57.656 --> 19:18:00.046 align:start position:0% have Network users educated in this field<19:17:57.960> so<19:17:58.320> that<19:17:58.440> they<19:17:58.680> know<19:17:58.920> exactly<19:17:59.640> what 19:18:00.046 --> 19:18:00.056 align:start position:0% field so that they know exactly what 19:18:00.056 --> 19:18:01.966 align:start position:0% field so that they know exactly what sort<19:18:00.240> of<19:18:00.360> threats<19:18:00.656> are<19:18:00.784> out<19:18:00.960> there<19:18:01.144> and<19:18:01.744> what 19:18:01.966 --> 19:18:01.976 align:start position:0% sort of threats are out there and what 19:18:01.976 --> 19:18:04.366 align:start position:0% sort of threats are out there and what safety<19:18:02.400> habits<19:18:02.872> are<19:18:03.000> there<19:18:03.176> as<19:18:03.424> well<19:18:03.600> there's 19:18:04.366 --> 19:18:04.376 align:start position:0% safety habits are there as well there's 19:18:04.376 --> 19:18:06.414 align:start position:0% safety habits are there as well there's some<19:18:04.616> safety<19:18:04.976> habits<19:18:05.336> that<19:18:05.512> are<19:18:05.696> obvious<19:18:06.120> like 19:18:06.414 --> 19:18:06.424 align:start position:0% some safety habits that are obvious like 19:18:06.424 --> 19:18:08.030 align:start position:0% some safety habits that are obvious like locking<19:18:06.960> a<19:18:07.080> device<19:18:07.256> and<19:18:07.552> keeping<19:18:07.920> your 19:18:08.030 --> 19:18:08.040 align:start position:0% locking a device and keeping your 19:18:08.040 --> 19:18:10.006 align:start position:0% locking a device and keeping your password<19:18:08.280> secure<19:18:08.872> but<19:18:09.240> there<19:18:09.720> are<19:18:09.896> other 19:18:10.006 --> 19:18:10.016 align:start position:0% password secure but there are other 19:18:10.016 --> 19:18:12.166 align:start position:0% password secure but there are other security<19:18:10.320> measures<19:18:10.976> and<19:18:11.400> knowledge<19:18:11.824> that's 19:18:12.166 --> 19:18:12.176 align:start position:0% security measures and knowledge that's 19:18:12.176 --> 19:18:14.094 align:start position:0% security measures and knowledge that's less<19:18:12.536> obvious<19:18:12.960> but<19:18:13.256> just<19:18:13.440> as<19:18:13.616> important 19:18:14.094 --> 19:18:14.104 align:start position:0% less obvious but just as important 19:18:14.104 --> 19:18:16.006 align:start position:0% less obvious but just as important Network<19:18:14.872> users<19:18:15.296> need<19:18:15.480> to<19:18:15.600> be<19:18:15.656> knowledgeable 19:18:16.006 --> 19:18:16.016 align:start position:0% Network users need to be knowledgeable 19:18:16.016 --> 19:18:17.390 align:start position:0% Network users need to be knowledgeable on<19:18:16.192> how<19:18:16.376> to<19:18:16.496> protect<19:18:16.744> themselves<19:18:17.104> from 19:18:17.390 --> 19:18:17.400 align:start position:0% on how to protect themselves from 19:18:17.400 --> 19:18:19.670 align:start position:0% on how to protect themselves from viruses<19:18:17.936> and<19:18:18.120> how<19:18:18.360> to<19:18:18.536> recognize<19:18:19.016> them<19:18:19.320> so 19:18:19.670 --> 19:18:19.680 align:start position:0% viruses and how to recognize them so 19:18:19.680 --> 19:18:21.470 align:start position:0% viruses and how to recognize them so they<19:18:19.856> don't<19:18:20.040> just<19:18:20.216> click<19:18:20.696> on<19:18:20.872> something<19:18:21.120> when 19:18:21.470 --> 19:18:21.480 align:start position:0% they don't just click on something when 19:18:21.480 --> 19:18:24.110 align:start position:0% they don't just click on something when it<19:18:21.656> pops<19:18:22.016> up<19:18:22.144> on<19:18:22.376> their<19:18:22.552> browser<19:18:22.976> first<19:18:23.696> they 19:18:24.110 --> 19:18:24.120 align:start position:0% it pops up on their browser first they 19:18:24.120 --> 19:18:25.734 align:start position:0% it pops up on their browser first they personally<19:18:24.720> need<19:18:25.016> to<19:18:25.144> back<19:18:25.256> up<19:18:25.440> their 19:18:25.734 --> 19:18:25.744 align:start position:0% personally need to back up their 19:18:25.744 --> 19:18:27.886 align:start position:0% personally need to back up their important<19:18:26.160> data<19:18:26.640> because<19:18:27.000> in<19:18:27.360> the<19:18:27.480> event<19:18:27.600> of 19:18:27.886 --> 19:18:27.896 align:start position:0% important data because in the event of 19:18:27.896 --> 19:18:30.414 align:start position:0% important data because in the event of an<19:18:28.080> attack<19:18:28.336> perhaps<19:18:29.336> are 19:18:30.414 --> 19:18:30.424 align:start position:0% an attack perhaps are 19:18:30.424 --> 19:18:33.886 align:start position:0% an attack perhaps are major<19:18:31.320> system<19:18:31.744> goes<19:18:32.576> down<19:18:32.896> alternatively 19:18:33.886 --> 19:18:33.896 align:start position:0% major system goes down alternatively 19:18:33.896 --> 19:18:37.542 align:start position:0% major system goes down alternatively they<19:18:34.552> need<19:18:34.744> to<19:18:34.976> know<19:18:35.280> that<19:18:35.824> they<19:18:36.056> should<19:18:36.360> be 19:18:37.542 --> 19:18:37.552 align:start position:0% they need to know that they should be 19:18:37.552 --> 19:18:40.910 align:start position:0% they need to know that they should be um<19:18:37.640> backing<19:18:38.640> up<19:18:38.824> their<19:18:39.176> data<19:18:39.536> to<19:18:40.144> perhaps<19:18:40.496> a 19:18:40.910 --> 19:18:40.920 align:start position:0% um backing up their data to perhaps a 19:18:40.920 --> 19:18:42.470 align:start position:0% um backing up their data to perhaps a central<19:18:41.104> location<19:18:41.464> or<19:18:41.936> they<19:18:42.120> need<19:18:42.240> to<19:18:42.360> be 19:18:42.470 --> 19:18:42.480 align:start position:0% central location or they need to be 19:18:42.480 --> 19:18:44.686 align:start position:0% central location or they need to be taught<19:18:42.720> where<19:18:43.192> to<19:18:43.440> back<19:18:43.616> up<19:18:43.744> their<19:18:43.976> data<19:18:44.280> for 19:18:44.686 --> 19:18:44.696 align:start position:0% taught where to back up their data for 19:18:44.696 --> 19:18:46.966 align:start position:0% taught where to back up their data for instance<19:18:44.936> to<19:18:45.176> the<19:18:45.360> network<19:18:45.480> share<19:18:46.016> and<19:18:46.496> not<19:18:46.680> to 19:18:46.966 --> 19:18:46.976 align:start position:0% instance to the network share and not to 19:18:46.976 --> 19:18:48.646 align:start position:0% instance to the network share and not to removable<19:18:47.400> hard<19:18:47.696> drive<19:18:47.872> or<19:18:48.240> not<19:18:48.360> on<19:18:48.536> their 19:18:48.646 --> 19:18:48.656 align:start position:0% removable hard drive or not on their 19:18:48.656 --> 19:18:50.990 align:start position:0% removable hard drive or not on their desktop<19:18:49.080> because<19:18:49.552> if<19:18:49.856> they<19:18:50.160> back<19:18:50.576> it<19:18:50.760> up<19:18:50.872> to 19:18:50.990 --> 19:18:51.000 align:start position:0% desktop because if they back it up to 19:18:51.000 --> 19:18:52.542 align:start position:0% desktop because if they back it up to their<19:18:51.176> desktop<19:18:51.536> then<19:18:51.832> what<19:18:52.016> happens<19:18:52.192> when 19:18:52.542 --> 19:18:52.552 align:start position:0% their desktop then what happens when 19:18:52.552 --> 19:18:54.230 align:start position:0% their desktop then what happens when their<19:18:52.744> computer<19:18:52.920> gets<19:18:53.400> broken<19:18:53.576> now<19:18:53.936> they've 19:18:54.230 --> 19:18:54.240 align:start position:0% their computer gets broken now they've 19:18:54.240 --> 19:18:56.710 align:start position:0% their computer gets broken now they've lost<19:18:54.424> all<19:18:54.784> the<19:18:54.896> work<19:18:55.080> they<19:18:55.680> didn't<19:18:55.856> back<19:18:56.160> up 19:18:56.710 --> 19:18:56.720 align:start position:0% lost all the work they didn't back up 19:18:56.720 --> 19:19:00.350 align:start position:0% lost all the work they didn't back up automatically<19:18:57.720> to<19:18:58.440> the<19:18:58.856> server<19:18:59.336> they<19:19:00.120> also 19:19:00.350 --> 19:19:00.360 align:start position:0% automatically to the server they also 19:19:00.360 --> 19:19:01.910 align:start position:0% automatically to the server they also need<19:19:00.480> to<19:19:00.536> be<19:19:00.656> diligent<19:19:01.080> about<19:19:01.256> web<19:19:01.504> browsing 19:19:01.910 --> 19:19:01.920 align:start position:0% need to be diligent about web browsing 19:19:01.920 --> 19:19:03.822 align:start position:0% need to be diligent about web browsing what<19:19:02.280> they<19:19:02.464> download<19:19:02.696> what<19:19:03.176> they<19:19:03.296> click<19:19:03.600> and 19:19:03.822 --> 19:19:03.832 align:start position:0% what they download what they click and 19:19:03.832 --> 19:19:06.166 align:start position:0% what they download what they click and so<19:19:04.016> on<19:19:04.192> if<19:19:04.680> they're<19:19:04.800> administrator<19:19:05.464> is<19:19:05.936> going 19:19:06.166 --> 19:19:06.176 align:start position:0% so on if they're administrator is going 19:19:06.176 --> 19:19:07.670 align:start position:0% so on if they're administrator is going to<19:19:06.240> allow<19:19:06.480> them<19:19:06.656> to<19:19:06.832> download<19:19:07.016> programs<19:19:07.552> they 19:19:07.670 --> 19:19:07.680 align:start position:0% to allow them to download programs they 19:19:07.680 --> 19:19:08.862 align:start position:0% to allow them to download programs they need<19:19:07.856> to<19:19:07.976> be<19:19:08.040> careful<19:19:08.280> about<19:19:08.400> where<19:19:08.696> they 19:19:08.862 --> 19:19:08.872 align:start position:0% need to be careful about where they 19:19:08.872 --> 19:19:11.030 align:start position:0% need to be careful about where they downloaded<19:19:09.360> them<19:19:09.536> from<19:19:09.784> again<19:19:10.496> we<19:19:10.920> always 19:19:11.030 --> 19:19:11.040 align:start position:0% downloaded them from again we always 19:19:11.040 --> 19:19:13.070 align:start position:0% downloaded them from again we always have<19:19:11.400> this 19:19:13.070 --> 19:19:13.080 align:start position:0% have this 19:19:13.080 --> 19:19:18.110 align:start position:0% have this interval<19:19:14.040> between<19:19:14.640> responsibility 19:19:18.110 --> 19:19:18.120 align:start position:0% 19:19:18.120 --> 19:19:20.630 align:start position:0% and<19:19:18.656> power<19:19:18.896> the<19:19:19.552> more<19:19:19.744> powerful<19:19:20.104> you<19:19:20.280> are<19:19:20.464> the 19:19:20.630 --> 19:19:20.640 align:start position:0% and power the more powerful you are the 19:19:20.640 --> 19:19:23.454 align:start position:0% and power the more powerful you are the more<19:19:20.872> responsible<19:19:21.360> you<19:19:21.784> have<19:19:21.896> to<19:19:22.080> be<19:19:22.256> if<19:19:23.104> I<19:19:23.336> can 19:19:23.454 --> 19:19:23.464 align:start position:0% more responsible you have to be if I can 19:19:23.464 --> 19:19:25.070 align:start position:0% more responsible you have to be if I can install<19:19:23.640> things<19:19:23.936> on<19:19:24.176> my<19:19:24.296> computer<19:19:24.480> that<19:19:24.832> also 19:19:25.070 --> 19:19:25.080 align:start position:0% install things on my computer that also 19:19:25.080 --> 19:19:26.566 align:start position:0% install things on my computer that also means<19:19:25.256> a<19:19:25.440> hacker<19:19:25.744> could<19:19:25.920> use<19:19:26.160> my<19:19:26.400> information 19:19:26.566 --> 19:19:26.576 align:start position:0% means a hacker could use my information 19:19:26.576 --> 19:19:28.790 align:start position:0% means a hacker could use my information to<19:19:27.056> install<19:19:27.240> something<19:19:27.536> on<19:19:27.784> the<19:19:27.896> computer<19:19:28.080> as 19:19:28.790 --> 19:19:28.800 align:start position:0% to install something on the computer as 19:19:28.800 --> 19:19:31.670 align:start position:0% to install something on the computer as well<19:19:28.976> and<19:19:29.872> finally<19:19:30.176> if<19:19:30.536> a<19:19:30.720> if<19:19:31.144> they<19:19:31.192> download<19:19:31.376> a 19:19:31.670 --> 19:19:31.680 align:start position:0% well and finally if a if they download a 19:19:31.680 --> 19:19:34.006 align:start position:0% well and finally if a if they download a program<19:19:31.800> that<19:19:32.104> seems<19:19:32.464> illegitimate<19:19:33.176> or<19:19:33.832> they 19:19:34.006 --> 19:19:34.016 align:start position:0% program that seems illegitimate or they 19:19:34.016 --> 19:19:36.286 align:start position:0% program that seems illegitimate or they think<19:19:34.192> they've<19:19:34.440> been<19:19:34.616> attacked<19:19:35.400> they<19:19:36.000> need<19:19:36.176> to 19:19:36.286 --> 19:19:36.296 align:start position:0% think they've been attacked they need to 19:19:36.296 --> 19:19:38.326 align:start position:0% think they've been attacked they need to be<19:19:36.424> able<19:19:36.536> to<19:19:36.656> spot<19:19:36.896> the<19:19:37.144> issue<19:19:37.440> and<19:19:37.800> report<19:19:38.040> it 19:19:38.326 --> 19:19:38.336 align:start position:0% be able to spot the issue and report it 19:19:38.336 --> 19:19:40.310 align:start position:0% be able to spot the issue and report it to<19:19:38.464> the<19:19:38.640> administrator<19:19:39.120> before<19:19:39.480> the<19:19:39.896> risky 19:19:40.310 --> 19:19:40.320 align:start position:0% to the administrator before the risky 19:19:40.320 --> 19:19:43.070 align:start position:0% to the administrator before the risky program<19:19:40.552> has<19:19:40.976> a<19:19:41.160> chance<19:19:41.336> to<19:19:41.640> damage<19:19:42.080> sometimes 19:19:43.070 --> 19:19:43.080 align:start position:0% program has a chance to damage sometimes 19:19:43.080 --> 19:19:44.502 align:start position:0% program has a chance to damage sometimes they<19:19:43.376> don't<19:19:43.552> want<19:19:43.744> to<19:19:43.856> say<19:19:44.040> anything<19:19:44.216> because 19:19:44.502 --> 19:19:44.512 align:start position:0% they don't want to say anything because 19:19:44.512 --> 19:19:46.182 align:start position:0% they don't want to say anything because they<19:19:44.640> don't<19:19:44.760> want<19:19:44.824> to<19:19:44.936> get<19:19:45.000> in<19:19:45.176> trouble<19:19:45.360> but<19:19:46.016> if 19:19:46.182 --> 19:19:46.192 align:start position:0% they don't want to get in trouble but if 19:19:46.192 --> 19:19:47.750 align:start position:0% they don't want to get in trouble but if they<19:19:46.320> had<19:19:46.440> said<19:19:46.680> something<19:19:46.856> earlier<19:19:47.336> we<19:19:47.640> could 19:19:47.750 --> 19:19:47.760 align:start position:0% they had said something earlier we could 19:19:47.760 --> 19:19:50.150 align:start position:0% they had said something earlier we could have<19:19:47.872> prevented<19:19:48.424> more<19:19:48.720> damage<19:19:49.144> it's<19:19:49.856> really 19:19:50.150 --> 19:19:50.160 align:start position:0% have prevented more damage it's really 19:19:50.160 --> 19:19:52.542 align:start position:0% have prevented more damage it's really important<19:19:50.576> for<19:19:50.824> them<19:19:50.936> to<19:19:51.176> know<19:19:51.424> when<19:19:52.192> they<19:19:52.440> are 19:19:52.542 --> 19:19:52.552 align:start position:0% important for them to know when they are 19:19:52.552 --> 19:19:54.230 align:start position:0% important for them to know when they are being<19:19:52.744> deceived<19:19:53.280> by<19:19:53.400> something<19:19:53.640> and<19:19:54.056> when 19:19:54.230 --> 19:19:54.240 align:start position:0% being deceived by something and when 19:19:54.240 --> 19:19:56.926 align:start position:0% being deceived by something and when something<19:19:54.536> is<19:19:54.784> legitimate<19:19:55.320> so<19:19:56.104> I<19:19:56.640> see<19:19:56.760> this 19:19:56.926 --> 19:19:56.936 align:start position:0% something is legitimate so I see this 19:19:56.936 --> 19:19:58.430 align:start position:0% something is legitimate so I see this all<19:19:57.056> the<19:19:57.176> time<19:19:57.240> people<19:19:57.424> send<19:19:57.656> up<19:19:57.832> these<19:19:58.080> emails 19:19:58.430 --> 19:19:58.440 align:start position:0% all the time people send up these emails 19:19:58.440 --> 19:20:01.134 align:start position:0% all the time people send up these emails saying<19:19:58.800> beware<19:19:59.400> of<19:19:59.640> this<19:19:59.936> and<19:20:00.536> an<19:20:00.720> easy<19:20:00.896> Google 19:20:01.134 --> 19:20:01.144 align:start position:0% saying beware of this and an easy Google 19:20:01.144 --> 19:20:02.814 align:start position:0% saying beware of this and an easy Google search<19:20:01.440> would<19:20:01.800> show<19:20:02.040> that<19:20:02.280> the<19:20:02.512> thing<19:20:02.640> that 19:20:02.814 --> 19:20:02.824 align:start position:0% search would show that the thing that 19:20:02.824 --> 19:20:04.846 align:start position:0% search would show that the thing that they're<19:20:03.056> actually<19:20:03.296> being<19:20:03.536> aware<19:20:03.832> of<19:20:04.016> isn't 19:20:04.846 --> 19:20:04.856 align:start position:0% they're actually being aware of isn't 19:20:04.856 --> 19:20:07.366 align:start position:0% they're actually being aware of isn't real<19:20:05.216> it's<19:20:05.872> something<19:20:06.120> fake<19:20:06.600> and<19:20:06.896> they've 19:20:07.366 --> 19:20:07.376 align:start position:0% real it's something fake and they've 19:20:07.376 --> 19:20:08.990 align:start position:0% real it's something fake and they've spent<19:20:07.616> time<19:20:07.856> and<19:20:08.104> energy<19:20:08.280> everyone's<19:20:08.824> time 19:20:08.990 --> 19:20:09.000 align:start position:0% spent time and energy everyone's time 19:20:09.000 --> 19:20:10.182 align:start position:0% spent time and energy everyone's time and<19:20:09.120> energy<19:20:09.240> getting<19:20:09.656> worried<19:20:10.016> about 19:20:10.182 --> 19:20:10.192 align:start position:0% and energy getting worried about 19:20:10.192 --> 19:20:11.686 align:start position:0% and energy getting worried about something<19:20:10.496> that<19:20:10.800> actually<19:20:11.040> is<19:20:11.216> not<19:20:11.464> going<19:20:11.576> to 19:20:11.686 --> 19:20:11.696 align:start position:0% something that actually is not going to 19:20:11.696 --> 19:20:13.910 align:start position:0% something that actually is not going to affect<19:20:11.936> them<19:20:12.176> on<19:20:12.784> the<19:20:12.896> other<19:20:13.016> hand<19:20:13.256> they<19:20:13.800> don't 19:20:13.910 --> 19:20:13.920 align:start position:0% affect them on the other hand they don't 19:20:13.920 --> 19:20:16.310 align:start position:0% affect them on the other hand they don't seem<19:20:14.216> to<19:20:14.336> recognize<19:20:14.824> when<19:20:15.240> someone's<19:20:15.720> account 19:20:16.310 --> 19:20:16.320 align:start position:0% seem to recognize when someone's account 19:20:16.320 --> 19:20:18.046 align:start position:0% seem to recognize when someone's account has<19:20:16.680> been<19:20:16.856> hacked<19:20:17.216> and<19:20:17.400> is<19:20:17.512> asking<19:20:17.760> for<19:20:17.872> money 19:20:18.046 --> 19:20:18.056 align:start position:0% has been hacked and is asking for money 19:20:18.056 --> 19:20:20.454 align:start position:0% has been hacked and is asking for money money<19:20:18.480> when<19:20:19.440> that<19:20:19.680> person<19:20:19.800> would<19:20:20.104> never<19:20:20.216> do 19:20:20.454 --> 19:20:20.464 align:start position:0% money when that person would never do 19:20:20.464 --> 19:20:23.390 align:start position:0% money when that person would never do that<19:20:20.576> it's<19:20:20.824> not<19:20:21.480> characteristic<19:20:22.256> most<19:20:23.104> of<19:20:23.280> all 19:20:23.390 --> 19:20:23.400 align:start position:0% that it's not characteristic most of all 19:20:23.400 --> 19:20:25.606 align:start position:0% that it's not characteristic most of all they<19:20:23.872> have<19:20:24.120> to<19:20:24.296> check<19:20:24.784> and<19:20:25.192> double<19:20:25.376> check 19:20:25.606 --> 19:20:25.616 align:start position:0% they have to check and double check 19:20:25.616 --> 19:20:28.966 align:start position:0% they have to check and double check stuff<19:20:25.920> and<19:20:26.160> be<19:20:26.336> willing<19:20:26.576> to<19:20:26.696> ask<19:20:26.936> questions 19:20:28.966 --> 19:20:28.976 align:start position:0% stuff and be willing to ask questions 19:20:28.976 --> 19:20:30.822 align:start position:0% stuff and be willing to ask questions so<19:20:29.400> here's<19:20:29.640> an<19:20:29.760> example<19:20:30.056> of<19:20:30.296> an<19:20:30.480> extremely 19:20:30.822 --> 19:20:30.832 align:start position:0% so here's an example of an extremely 19:20:30.832 --> 19:20:33.046 align:start position:0% so here's an example of an extremely common<19:20:31.192> virus<19:20:31.800> that's<19:20:32.160> intended<19:20:32.640> to<19:20:32.760> scam 19:20:33.046 --> 19:20:33.056 align:start position:0% common virus that's intended to scam 19:20:33.056 --> 19:20:34.670 align:start position:0% common virus that's intended to scam people<19:20:33.240> out<19:20:33.536> of<19:20:33.656> money<19:20:33.896> on<19:20:34.192> the<19:20:34.320> on<19:20:34.496> the 19:20:34.670 --> 19:20:34.680 align:start position:0% people out of money on the on the 19:20:34.680 --> 19:20:36.590 align:start position:0% people out of money on the on the computer<19:20:34.800> that's<19:20:35.104> being<19:20:35.280> infected<19:20:35.760> the<19:20:36.240> virus 19:20:36.590 --> 19:20:36.600 align:start position:0% computer that's being infected the virus 19:20:36.600 --> 19:20:38.390 align:start position:0% computer that's being infected the virus takes<19:20:36.832> over<19:20:36.960> your<19:20:37.144> computer<19:20:37.320> and<19:20:37.920> only<19:20:38.104> lets 19:20:38.390 --> 19:20:38.400 align:start position:0% takes over your computer and only lets 19:20:38.400 --> 19:20:40.430 align:start position:0% takes over your computer and only lets you<19:20:38.464> see<19:20:38.696> this<19:20:39.000> screen<19:20:39.240> or<19:20:39.536> one<19:20:39.784> very<19:20:40.016> similar 19:20:40.430 --> 19:20:40.440 align:start position:0% you see this screen or one very similar 19:20:40.440 --> 19:20:43.070 align:start position:0% you see this screen or one very similar to<19:20:40.680> it<19:20:40.856> it<19:20:41.576> claims<19:20:41.936> that<19:20:42.120> the<19:20:42.296> IP<19:20:42.536> address<19:20:42.720> has 19:20:43.070 --> 19:20:43.080 align:start position:0% to it it claims that the IP address has 19:20:43.080 --> 19:20:45.950 align:start position:0% to it it claims that the IP address has been<19:20:43.256> used<19:20:43.440> to<19:20:43.680> do<19:20:43.856> very<19:20:44.216> illegal<19:20:44.760> things<19:20:45.120> and 19:20:45.950 --> 19:20:45.960 align:start position:0% been used to do very illegal things and 19:20:45.960 --> 19:20:48.046 align:start position:0% been used to do very illegal things and the<19:20:46.144> FBI<19:20:46.496> sees<19:20:46.976> the<19:20:47.104> computer<19:20:47.280> and<19:20:47.696> in<19:20:47.872> order 19:20:48.046 --> 19:20:48.056 align:start position:0% the FBI sees the computer and in order 19:20:48.056 --> 19:20:49.910 align:start position:0% the FBI sees the computer and in order to<19:20:48.176> unlock<19:20:48.424> the<19:20:48.720> computer<19:20:48.832> you<19:20:49.256> have<19:20:49.376> to<19:20:49.504> pay<19:20:49.680> a 19:20:49.910 --> 19:20:49.920 align:start position:0% to unlock the computer you have to pay a 19:20:49.920 --> 19:20:53.206 align:start position:0% to unlock the computer you have to pay a fine<19:20:50.104> or<19:20:50.512> purchase<19:20:51.120> a<19:20:51.296> code<19:20:51.480> now<19:20:52.440> this<19:20:52.856> virus 19:20:53.206 --> 19:20:53.216 align:start position:0% fine or purchase a code now this virus 19:20:53.216 --> 19:20:57.414 align:start position:0% fine or purchase a code now this virus is<19:20:53.512> extremely<19:20:54.360> intrusive<19:20:55.192> and<19:20:55.744> obviously<19:20:56.424> uh 19:20:57.414 --> 19:20:57.424 align:start position:0% is extremely intrusive and obviously uh 19:20:57.424 --> 19:20:58.966 align:start position:0% is extremely intrusive and obviously uh quite 19:20:58.966 --> 19:20:58.976 align:start position:0% quite 19:20:58.976 --> 19:21:00.350 align:start position:0% quite you<19:20:59.696> know 19:21:00.350 --> 19:21:00.360 align:start position:0% you know 19:21:00.360 --> 19:21:01.206 align:start position:0% you know um 19:21:01.206 --> 19:21:01.216 align:start position:0% um 19:21:01.216 --> 19:21:04.454 align:start position:0% um successfully<19:21:02.600> convincing<19:21:03.600> look<19:21:03.832> at<19:21:04.016> all<19:21:04.192> the 19:21:04.454 --> 19:21:04.464 align:start position:0% successfully convincing look at all the 19:21:04.464 --> 19:21:07.790 align:start position:0% successfully convincing look at all the 7-Eleven<19:21:05.464> CVS<19:21:06.176> Rite<19:21:06.656> Aid<19:21:06.832> all<19:21:07.016> the<19:21:07.192> logos<19:21:07.616> at 19:21:07.790 --> 19:21:07.800 align:start position:0% 7-Eleven CVS Rite Aid all the logos at 19:21:07.800 --> 19:21:11.150 align:start position:0% 7-Eleven CVS Rite Aid all the logos at the<19:21:07.920> bottom<19:21:08.160> Department<19:21:08.696> of<19:21:09.056> Justice<19:21:10.016> Etc<19:21:10.192> and 19:21:11.150 --> 19:21:11.160 align:start position:0% the bottom Department of Justice Etc and 19:21:11.160 --> 19:21:13.182 align:start position:0% the bottom Department of Justice Etc and the<19:21:11.464> reason<19:21:11.576> they're<19:21:11.824> gonna<19:21:12.000> make<19:21:12.240> you<19:21:12.480> pay 19:21:13.182 --> 19:21:13.192 align:start position:0% the reason they're gonna make you pay 19:21:13.192 --> 19:21:16.070 align:start position:0% the reason they're gonna make you pay through<19:21:13.440> money<19:21:13.680> pack<19:21:13.920> it<19:21:14.336> looks<19:21:14.696> so<19:21:15.120> real<19:21:15.424> is 19:21:16.070 --> 19:21:16.080 align:start position:0% through money pack it looks so real is 19:21:16.080 --> 19:21:17.990 align:start position:0% through money pack it looks so real is because<19:21:16.336> that<19:21:17.336> way<19:21:17.464> they<19:21:17.696> know<19:21:17.824> they're 19:21:17.990 --> 19:21:18.000 align:start position:0% because that way they know they're 19:21:18.000 --> 19:21:20.094 align:start position:0% because that way they know they're getting<19:21:18.176> the<19:21:18.424> money<19:21:18.536> on<19:21:18.896> the<19:21:19.080> other<19:21:19.144> end<19:21:19.376> so 19:21:20.094 --> 19:21:20.104 align:start position:0% getting the money on the other end so 19:21:20.104 --> 19:21:22.310 align:start position:0% getting the money on the other end so it's<19:21:20.336> important<19:21:20.824> for<19:21:21.120> someone<19:21:21.360> to<19:21:21.784> recognize 19:21:22.310 --> 19:21:22.320 align:start position:0% it's important for someone to recognize 19:21:22.320 --> 19:21:25.070 align:start position:0% it's important for someone to recognize that<19:21:23.160> this<19:21:23.512> is<19:21:23.872> actually<19:21:24.120> fake<19:21:24.536> look<19:21:24.784> on<19:21:24.896> here 19:21:25.070 --> 19:21:25.080 align:start position:0% that this is actually fake look on here 19:21:25.080 --> 19:21:27.590 align:start position:0% that this is actually fake look on here it<19:21:25.256> even<19:21:25.504> scares<19:21:25.976> people<19:21:26.160> by<19:21:26.576> saying<19:21:27.000> you<19:21:27.424> have 19:21:27.590 --> 19:21:27.600 align:start position:0% it even scares people by saying you have 19:21:27.600 --> 19:21:29.270 align:start position:0% it even scares people by saying you have 72<19:21:27.960> hours<19:21:28.080> to<19:21:28.376> pay<19:21:28.496> the<19:21:28.680> fine<19:21:28.800> or<19:21:29.040> you're<19:21:29.104> going 19:21:29.270 --> 19:21:29.280 align:start position:0% 72 hours to pay the fine or you're going 19:21:29.280 --> 19:21:30.590 align:start position:0% 72 hours to pay the fine or you're going to<19:21:29.336> be<19:21:29.464> arrested 19:21:30.590 --> 19:21:30.600 align:start position:0% to be arrested 19:21:30.600 --> 19:21:32.862 align:start position:0% to be arrested now<19:21:31.440> someone<19:21:32.040> might<19:21:32.280> have<19:21:32.464> been<19:21:32.640> doing 19:21:32.862 --> 19:21:32.872 align:start position:0% now someone might have been doing 19:21:32.872 --> 19:21:35.750 align:start position:0% now someone might have been doing something<19:21:33.176> like<19:21:33.600> downloading<19:21:34.320> uh<19:21:35.216> a<19:21:35.400> torrent 19:21:35.750 --> 19:21:35.760 align:start position:0% something like downloading uh a torrent 19:21:35.760 --> 19:21:37.790 align:start position:0% something like downloading uh a torrent off<19:21:36.056> the<19:21:36.240> internet<19:21:36.360> and<19:21:36.784> so<19:21:37.016> they<19:21:37.256> think<19:21:37.440> oh<19:21:37.616> my 19:21:37.790 --> 19:21:37.800 align:start position:0% off the internet and so they think oh my 19:21:37.800 --> 19:21:39.230 align:start position:0% off the internet and so they think oh my God<19:21:37.856> I'm<19:21:37.976> gonna<19:21:38.104> be<19:21:38.216> in<19:21:38.336> trouble<19:21:38.512> and<19:21:39.120> they 19:21:39.230 --> 19:21:39.240 align:start position:0% God I'm gonna be in trouble and they 19:21:39.240 --> 19:21:40.134 align:start position:0% God I'm gonna be in trouble and they don't<19:21:39.360> want<19:21:39.480> to<19:21:39.600> tell<19:21:39.656> you<19:21:39.832> because<19:21:39.960> they 19:21:40.134 --> 19:21:40.144 align:start position:0% don't want to tell you because they 19:21:40.144 --> 19:21:40.966 align:start position:0% don't want to tell you because they think<19:21:40.256> they're<19:21:40.376> going<19:21:40.496> to<19:21:40.552> get<19:21:40.680> in<19:21:40.800> trouble 19:21:40.966 --> 19:21:40.976 align:start position:0% think they're going to get in trouble 19:21:40.976 --> 19:21:42.886 align:start position:0% think they're going to get in trouble with<19:21:41.160> you<19:21:41.336> as<19:21:41.512> well<19:21:41.696> we<19:21:42.296> need<19:21:42.480> to<19:21:42.600> make<19:21:42.720> sure 19:21:42.886 --> 19:21:42.896 align:start position:0% with you as well we need to make sure 19:21:42.896 --> 19:21:44.630 align:start position:0% with you as well we need to make sure that<19:21:43.080> they<19:21:43.256> have<19:21:43.376> a<19:21:43.616> judge-free<19:21:44.160> Zone<19:21:44.464> in 19:21:44.630 --> 19:21:44.640 align:start position:0% that they have a judge-free Zone in 19:21:44.640 --> 19:21:47.030 align:start position:0% that they have a judge-free Zone in which<19:21:44.824> they<19:21:45.000> can<19:21:45.176> come<19:21:45.424> tell<19:21:46.320> someone<19:21:46.616> and 19:21:47.030 --> 19:21:47.040 align:start position:0% which they can come tell someone and 19:21:47.040 --> 19:21:49.366 align:start position:0% which they can come tell someone and that<19:21:47.216> way<19:21:47.400> you<19:21:47.872> could<19:21:48.000> remove<19:21:48.296> the<19:21:48.656> virus<19:21:49.016> and 19:21:49.366 --> 19:21:49.376 align:start position:0% that way you could remove the virus and 19:21:49.376 --> 19:21:50.502 align:start position:0% that way you could remove the virus and they<19:21:49.504> could<19:21:49.616> go<19:21:49.800> on<19:21:49.920> on<19:21:50.104> their<19:21:50.216> way<19:21:50.336> and 19:21:50.502 --> 19:21:50.512 align:start position:0% they could go on on their way and 19:21:50.512 --> 19:21:52.606 align:start position:0% they could go on on their way and continue<19:21:50.696> to<19:21:51.056> work 19:21:52.606 --> 19:21:52.616 align:start position:0% continue to work 19:21:52.616 --> 19:21:54.950 align:start position:0% continue to work now<19:21:52.976> as<19:21:53.216> viruses<19:21:53.824> and<19:21:54.176> malware<19:21:54.536> attacks 19:21:54.950 --> 19:21:54.960 align:start position:0% now as viruses and malware attacks 19:21:54.960 --> 19:21:57.286 align:start position:0% now as viruses and malware attacks become<19:21:55.192> more<19:21:55.320> and<19:21:55.440> more<19:21:55.616> advanced<19:21:56.296> anti-virus 19:21:57.286 --> 19:21:57.296 align:start position:0% become more and more advanced anti-virus 19:21:57.296 --> 19:21:59.814 align:start position:0% become more and more advanced anti-virus software<19:21:57.656> improves<19:21:58.256> to<19:21:58.496> combat<19:21:58.856> them<19:21:59.104> there 19:21:59.814 --> 19:21:59.824 align:start position:0% software improves to combat them there 19:21:59.824 --> 19:22:02.270 align:start position:0% software improves to combat them there are<19:21:59.936> thousands<19:22:00.480> of<19:22:00.600> antivirus<19:22:01.320> software<19:22:01.744> and 19:22:02.270 --> 19:22:02.280 align:start position:0% are thousands of antivirus software and 19:22:02.280 --> 19:22:04.134 align:start position:0% are thousands of antivirus software and some<19:22:02.760> are<19:22:02.936> more<19:22:03.176> advanced<19:22:03.536> than<19:22:03.784> you<19:22:03.960> could 19:22:04.134 --> 19:22:04.144 align:start position:0% some are more advanced than you could 19:22:04.144 --> 19:22:06.350 align:start position:0% some are more advanced than you could possibly<19:22:04.496> even<19:22:04.680> imagine<19:22:05.040> it's<19:22:05.824> not<19:22:06.000> at<19:22:06.176> the 19:22:06.350 --> 19:22:06.360 align:start position:0% possibly even imagine it's not at the 19:22:06.360 --> 19:22:08.566 align:start position:0% possibly even imagine it's not at the ordinary<19:22:06.720> however<19:22:07.144> for<19:22:07.376> antivirus<19:22:08.160> software 19:22:08.566 --> 19:22:08.576 align:start position:0% ordinary however for antivirus software 19:22:08.576 --> 19:22:11.750 align:start position:0% ordinary however for antivirus software to<19:22:08.824> have<19:22:09.056> automatic<19:22:09.784> features<19:22:10.320> so<19:22:11.280> step<19:22:11.512> four 19:22:11.750 --> 19:22:11.760 align:start position:0% to have automatic features so step four 19:22:11.760 --> 19:22:13.494 align:start position:0% to have automatic features so step four in<19:22:11.936> the<19:22:12.056> mitigation<19:22:12.480> strategy<19:22:13.016> needs<19:22:13.320> to<19:22:13.440> be 19:22:13.494 --> 19:22:13.504 align:start position:0% in the mitigation strategy needs to be 19:22:13.504 --> 19:22:16.790 align:start position:0% in the mitigation strategy needs to be to<19:22:13.744> make<19:22:13.976> sure<19:22:14.216> that<19:22:14.872> antivirus<19:22:15.600> systems<19:22:16.496> and 19:22:16.790 --> 19:22:16.800 align:start position:0% to make sure that antivirus systems and 19:22:16.800 --> 19:22:19.030 align:start position:0% to make sure that antivirus systems and software<19:22:17.216> are<19:22:17.512> configured<19:22:18.000> to<19:22:18.240> do<19:22:18.424> things 19:22:19.030 --> 19:22:19.040 align:start position:0% software are configured to do things 19:22:19.040 --> 19:22:21.774 align:start position:0% software are configured to do things automatically<19:22:20.040> this<19:22:20.760> means<19:22:21.056> they<19:22:21.296> have<19:22:21.536> to 19:22:21.774 --> 19:22:21.784 align:start position:0% automatically this means they have to 19:22:21.784 --> 19:22:24.774 align:start position:0% automatically this means they have to automatically<19:22:22.440> scan<19:22:23.104> the<19:22:23.280> computer<19:22:23.600> scan<19:22:24.600> the 19:22:24.774 --> 19:22:24.784 align:start position:0% automatically scan the computer scan the 19:22:24.784 --> 19:22:27.590 align:start position:0% automatically scan the computer scan the network<19:22:25.040> and<19:22:26.040> update<19:22:26.512> themselves<19:22:27.000> we<19:22:27.480> don't 19:22:27.590 --> 19:22:27.600 align:start position:0% network and update themselves we don't 19:22:27.600 --> 19:22:29.750 align:start position:0% network and update themselves we don't want<19:22:27.720> to<19:22:27.832> rely<19:22:28.144> on<19:22:28.256> a<19:22:28.440> human<19:22:28.552> to<19:22:28.920> do<19:22:29.040> this<19:22:29.280> very 19:22:29.750 --> 19:22:29.760 align:start position:0% want to rely on a human to do this very 19:22:29.760 --> 19:22:31.310 align:start position:0% want to rely on a human to do this very often<19:22:30.056> when<19:22:30.296> it<19:22:30.424> comes<19:22:30.600> to<19:22:30.720> virus<19:22:31.080> scan 19:22:31.310 --> 19:22:31.320 align:start position:0% often when it comes to virus scan 19:22:31.320 --> 19:22:32.454 align:start position:0% often when it comes to virus scan nothing's<19:22:31.744> going<19:22:31.856> to<19:22:31.920> be<19:22:31.976> rolled<19:22:32.336> out 19:22:32.454 --> 19:22:32.464 align:start position:0% nothing's going to be rolled out 19:22:32.464 --> 19:22:33.886 align:start position:0% nothing's going to be rolled out automatically<19:22:32.936> that's<19:22:33.176> going<19:22:33.360> to<19:22:33.424> damage<19:22:33.720> our 19:22:33.886 --> 19:22:33.896 align:start position:0% automatically that's going to damage our 19:22:33.896 --> 19:22:36.110 align:start position:0% automatically that's going to damage our computer<19:22:34.144> so<19:22:35.104> this<19:22:35.464> stuff<19:22:35.576> needs<19:22:35.936> to<19:22:36.000> happen 19:22:36.110 --> 19:22:36.120 align:start position:0% computer so this stuff needs to happen 19:22:36.120 --> 19:22:38.862 align:start position:0% computer so this stuff needs to happen automatically<19:22:36.784> when<19:22:37.744> are<19:22:38.040> we<19:22:38.160> going<19:22:38.336> to<19:22:38.512> scan 19:22:38.862 --> 19:22:38.872 align:start position:0% automatically when are we going to scan 19:22:38.872 --> 19:22:41.814 align:start position:0% automatically when are we going to scan the<19:22:39.832> network<19:22:40.016> well<19:22:40.800> we<19:22:41.040> want<19:22:41.216> it<19:22:41.336> to<19:22:41.464> scan<19:22:41.640> when 19:22:41.814 --> 19:22:41.824 align:start position:0% the network well we want it to scan when 19:22:41.824 --> 19:22:44.030 align:start position:0% the network well we want it to scan when no<19:22:42.000> one's<19:22:42.240> doing<19:22:42.424> anything<19:22:42.720> so<19:22:43.504> we<19:22:43.616> want<19:22:43.800> to<19:22:43.920> do 19:22:44.030 --> 19:22:44.040 align:start position:0% no one's doing anything so we want to do 19:22:44.040 --> 19:22:46.790 align:start position:0% no one's doing anything so we want to do it<19:22:44.160> for<19:22:44.464> instance<19:22:44.696> at<19:22:45.000> 2<19:22:45.176> am<19:22:45.360> not<19:22:45.896> at<19:22:46.080> 2PM<19:22:46.616> when 19:22:46.790 --> 19:22:46.800 align:start position:0% it for instance at 2 am not at 2PM when 19:22:46.800 --> 19:22:48.350 align:start position:0% it for instance at 2 am not at 2PM when people<19:22:46.976> are<19:22:47.160> busy<19:22:47.464> opening<19:22:47.936> things<19:22:48.120> and 19:22:48.350 --> 19:22:48.360 align:start position:0% people are busy opening things and 19:22:48.360 --> 19:22:50.686 align:start position:0% people are busy opening things and closing<19:22:48.784> things<19:22:49.016> and<19:22:49.744> that's<19:22:49.920> when<19:22:50.160> the<19:22:50.336> virus 19:22:50.686 --> 19:22:50.696 align:start position:0% closing things and that's when the virus 19:22:50.696 --> 19:22:52.070 align:start position:0% closing things and that's when the virus scan<19:22:50.936> program<19:22:51.176> won't<19:22:51.424> be<19:22:51.600> able<19:22:51.720> to<19:22:51.784> get<19:22:51.896> access 19:22:52.070 --> 19:22:52.080 align:start position:0% scan program won't be able to get access 19:22:52.080 --> 19:22:54.350 align:start position:0% scan program won't be able to get access to<19:22:52.552> fifty<19:22:53.216> percent<19:22:53.280> of<19:22:53.512> the<19:22:53.640> network<19:22:53.824> and 19:22:54.350 --> 19:22:54.360 align:start position:0% to fifty percent of the network and 19:22:54.360 --> 19:22:56.030 align:start position:0% to fifty percent of the network and therefore<19:22:54.600> something<19:22:54.896> could<19:22:55.192> be<19:22:55.376> hiding<19:22:55.800> out 19:22:56.030 --> 19:22:56.040 align:start position:0% therefore something could be hiding out 19:22:56.040 --> 19:22:59.150 align:start position:0% therefore something could be hiding out this<19:22:57.000> eliminates<19:22:57.536> all<19:22:57.896> this<19:22:58.016> eliminates<19:22:58.616> the 19:22:59.150 --> 19:22:59.160 align:start position:0% this eliminates all this eliminates the 19:22:59.160 --> 19:23:01.494 align:start position:0% this eliminates all this eliminates the human<19:22:59.280> element<19:22:59.640> it<19:23:00.120> allows<19:23:00.424> for<19:23:00.600> more<19:23:01.016> regular 19:23:01.494 --> 19:23:01.504 align:start position:0% human element it allows for more regular 19:23:01.504 --> 19:23:03.526 align:start position:0% human element it allows for more regular and<19:23:01.800> controlled<19:23:02.400> updates<19:23:02.824> in<19:23:03.056> the<19:23:03.240> process 19:23:03.526 --> 19:23:03.536 align:start position:0% and controlled updates in the process 19:23:03.536 --> 19:23:05.502 align:start position:0% and controlled updates in the process which<19:23:04.144> is<19:23:04.256> important<19:23:04.616> because<19:23:04.920> when<19:23:05.160> we<19:23:05.280> allow 19:23:05.502 --> 19:23:05.512 align:start position:0% which is important because when we allow 19:23:05.512 --> 19:23:08.686 align:start position:0% which is important because when we allow humans<19:23:05.872> in<19:23:06.056> that's<19:23:06.600> when<19:23:06.784> errors<19:23:07.144> occur 19:23:08.686 --> 19:23:08.696 align:start position:0% humans in that's when errors occur 19:23:08.696 --> 19:23:10.606 align:start position:0% humans in that's when errors occur finally<19:23:09.176> when<19:23:09.424> an<19:23:09.656> update<19:23:09.896> to<19:23:10.080> a<19:23:10.256> program<19:23:10.376> is 19:23:10.606 --> 19:23:10.616 align:start position:0% finally when an update to a program is 19:23:10.616 --> 19:23:12.950 align:start position:0% finally when an update to a program is released<19:23:10.976> it's<19:23:11.400> generally<19:23:11.760> to<19:23:12.000> address<19:23:12.176> bugs 19:23:12.950 --> 19:23:12.960 align:start position:0% released it's generally to address bugs 19:23:12.960 --> 19:23:14.566 align:start position:0% released it's generally to address bugs that<19:23:13.080> were<19:23:13.256> found<19:23:13.504> within<19:23:14.040> a<19:23:14.400> previous 19:23:14.566 --> 19:23:14.576 align:start position:0% that were found within a previous 19:23:14.576 --> 19:23:17.030 align:start position:0% that were found within a previous version<19:23:15.120> along<19:23:15.960> with<19:23:16.256> these<19:23:16.440> bugs<19:23:16.800> there 19:23:17.030 --> 19:23:17.040 align:start position:0% version along with these bugs there 19:23:17.040 --> 19:23:18.822 align:start position:0% version along with these bugs there might<19:23:17.160> have<19:23:17.280> been<19:23:17.400> some<19:23:17.696> security<19:23:17.936> weaknesses 19:23:18.822 --> 19:23:18.832 align:start position:0% might have been some security weaknesses 19:23:18.832 --> 19:23:20.094 align:start position:0% might have been some security weaknesses in<19:23:19.080> the<19:23:19.256> software<19:23:19.552> that<19:23:19.744> need<19:23:19.920> to<19:23:19.976> be 19:23:20.094 --> 19:23:20.104 align:start position:0% in the software that need to be 19:23:20.104 --> 19:23:22.734 align:start position:0% in the software that need to be addressed<19:23:20.576> but<19:23:21.056> program<19:23:21.424> updates<19:23:22.144> don't<19:23:22.496> come 19:23:22.734 --> 19:23:22.744 align:start position:0% addressed but program updates don't come 19:23:22.744 --> 19:23:26.630 align:start position:0% addressed but program updates don't come out<19:23:22.920> very<19:23:23.280> often<19:23:23.760> in<19:23:24.600> between<19:23:25.216> uh<19:23:26.216> updates 19:23:26.630 --> 19:23:26.640 align:start position:0% out very often in between uh updates 19:23:26.640 --> 19:23:29.270 align:start position:0% out very often in between uh updates patches<19:23:27.296> and<19:23:27.656> so<19:23:27.832> on<19:23:28.016> there<19:23:28.680> might<19:23:28.800> be<19:23:28.920> a 19:23:29.270 --> 19:23:29.280 align:start position:0% patches and so on there might be a 19:23:29.280 --> 19:23:31.966 align:start position:0% patches and so on there might be a temporary<19:23:29.640> fix<19:23:30.000> that's<19:23:30.360> released<19:23:30.960> or<19:23:31.504> a<19:23:31.800> fix 19:23:31.966 --> 19:23:31.976 align:start position:0% temporary fix that's released or a fix 19:23:31.976 --> 19:23:35.390 align:start position:0% temporary fix that's released or a fix that<19:23:32.280> is<19:23:32.512> manual<19:23:33.000> that<19:23:33.424> have<19:23:33.600> been<19:23:33.832> found<19:23:34.192> so<19:23:35.040> a 19:23:35.390 --> 19:23:35.400 align:start position:0% that is manual that have been found so a 19:23:35.400 --> 19:23:36.886 align:start position:0% that is manual that have been found so a patch<19:23:35.760> does<19:23:35.936> exactly<19:23:36.296> what<19:23:36.480> you<19:23:36.600> think<19:23:36.784> it 19:23:36.886 --> 19:23:36.896 align:start position:0% patch does exactly what you think it 19:23:36.896 --> 19:23:39.230 align:start position:0% patch does exactly what you think it does<19:23:37.144> it<19:23:37.744> basically<19:23:38.040> covers<19:23:38.400> a<19:23:38.640> hole<19:23:39.000> in<19:23:39.056> the 19:23:39.230 --> 19:23:39.240 align:start position:0% does it basically covers a hole in the 19:23:39.240 --> 19:23:40.910 align:start position:0% does it basically covers a hole in the software<19:23:39.536> and<19:23:39.784> temporarily<19:23:40.320> repairs<19:23:40.800> it 19:23:40.910 --> 19:23:40.920 align:start position:0% software and temporarily repairs it 19:23:40.920 --> 19:23:43.070 align:start position:0% software and temporarily repairs it until<19:23:41.104> an<19:23:41.512> update<19:23:41.872> or<19:23:42.120> a<19:23:42.296> new<19:23:42.424> revision<19:23:42.720> of<19:23:42.960> the 19:23:43.070 --> 19:23:43.080 align:start position:0% until an update or a new revision of the 19:23:43.080 --> 19:23:45.646 align:start position:0% until an update or a new revision of the software<19:23:43.320> can<19:23:43.552> come<19:23:43.744> out<19:23:43.920> so<19:23:44.824> as<19:23:45.120> soon<19:23:45.360> as 19:23:45.646 --> 19:23:45.656 align:start position:0% software can come out so as soon as 19:23:45.656 --> 19:23:47.686 align:start position:0% software can come out so as soon as patches<19:23:46.144> or<19:23:46.320> updates<19:23:46.616> are<19:23:46.856> released<19:23:47.216> the 19:23:47.686 --> 19:23:47.696 align:start position:0% patches or updates are released the 19:23:47.696 --> 19:23:49.246 align:start position:0% patches or updates are released the network<19:23:47.824> admin<19:23:48.296> needs<19:23:48.536> to<19:23:48.600> look<19:23:48.784> at<19:23:48.896> them<19:23:49.016> and 19:23:49.246 --> 19:23:49.256 align:start position:0% network admin needs to look at them and 19:23:49.256 --> 19:23:50.502 align:start position:0% network admin needs to look at them and think<19:23:49.376> about<19:23:49.552> installing<19:23:50.104> them<19:23:50.216> on<19:23:50.400> the 19:23:50.502 --> 19:23:50.512 align:start position:0% think about installing them on the 19:23:50.512 --> 19:23:52.966 align:start position:0% think about installing them on the network<19:23:50.696> now<19:23:51.600> notice<19:23:52.016> that<19:23:52.256> I<19:23:52.744> don't 19:23:52.966 --> 19:23:52.976 align:start position:0% network now notice that I don't 19:23:52.976 --> 19:23:56.094 align:start position:0% network now notice that I don't necessarily<19:23:53.760> want<19:23:54.360> you<19:23:54.536> to<19:23:54.784> just<19:23:55.144> install<19:23:55.680> it 19:23:56.094 --> 19:23:56.104 align:start position:0% necessarily want you to just install it 19:23:56.104 --> 19:23:57.526 align:start position:0% necessarily want you to just install it right<19:23:56.336> away 19:23:57.526 --> 19:23:57.536 align:start position:0% right away 19:23:57.536 --> 19:23:59.990 align:start position:0% right away I<19:23:58.080> want<19:23:58.192> you<19:23:58.376> to<19:23:58.496> test<19:23:58.744> it 19:23:59.990 --> 19:24:00.000 align:start position:0% I want you to test it 19:24:00.000 --> 19:24:02.270 align:start position:0% I want you to test it and<19:24:00.480> think<19:24:00.656> about<19:24:00.832> it 19:24:02.270 --> 19:24:02.280 align:start position:0% and think about it 19:24:02.280 --> 19:24:06.590 align:start position:0% and think about it because<19:24:03.144> the<19:24:04.144> patch<19:24:04.680> or<19:24:04.744> update<19:24:05.216> could<19:24:06.056> very 19:24:06.590 --> 19:24:06.600 align:start position:0% because the patch or update could very 19:24:06.600 --> 19:24:08.750 align:start position:0% because the patch or update could very well<19:24:06.896> cause<19:24:07.320> another<19:24:07.800> problem<19:24:08.216> on<19:24:08.640> the 19:24:08.750 --> 19:24:08.760 align:start position:0% well cause another problem on the 19:24:08.760 --> 19:24:10.486 align:start position:0% well cause another problem on the computer<19:24:08.936> and<19:24:09.536> one<19:24:09.656> thing<19:24:09.832> we<19:24:10.016> don't<19:24:10.144> want<19:24:10.376> to 19:24:10.486 --> 19:24:10.496 align:start position:0% computer and one thing we don't want to 19:24:10.496 --> 19:24:12.710 align:start position:0% computer and one thing we don't want to do<19:24:10.616> is<19:24:11.160> bring<19:24:11.400> down<19:24:11.576> our<19:24:11.824> system<19:24:12.000> because<19:24:12.360> we 19:24:12.710 --> 19:24:12.720 align:start position:0% do is bring down our system because we 19:24:12.720 --> 19:24:14.862 align:start position:0% do is bring down our system because we put<19:24:13.016> in<19:24:13.144> a<19:24:13.320> new<19:24:13.440> update<19:24:13.744> that<19:24:13.976> suddenly<19:24:14.400> stops 19:24:14.862 --> 19:24:14.872 align:start position:0% put in a new update that suddenly stops 19:24:14.872 --> 19:24:16.182 align:start position:0% put in a new update that suddenly stops our<19:24:15.000> printers<19:24:15.360> from<19:24:15.480> working<19:24:15.720> or<19:24:16.016> something 19:24:16.182 --> 19:24:16.192 align:start position:0% our printers from working or something 19:24:16.192 --> 19:24:20.814 align:start position:0% our printers from working or something so<19:24:17.104> we<19:24:17.464> need<19:24:17.640> to<19:24:18.056> balance<19:24:18.536> this<19:24:18.920> with<19:24:19.920> the<19:24:20.464> idea 19:24:20.814 --> 19:24:20.824 align:start position:0% so we need to balance this with the idea 19:24:20.824 --> 19:24:22.846 align:start position:0% so we need to balance this with the idea that<19:24:21.000> once<19:24:21.296> the<19:24:21.480> patch<19:24:21.832> and<19:24:22.016> the<19:24:22.144> update<19:24:22.440> is 19:24:22.846 --> 19:24:22.856 align:start position:0% that once the patch and the update is 19:24:22.856 --> 19:24:26.030 align:start position:0% that once the patch and the update is released<19:24:23.280> the<19:24:24.176> hacker<19:24:24.536> now<19:24:24.784> knows<19:24:25.256> that<19:24:25.856> this 19:24:26.030 --> 19:24:26.040 align:start position:0% released the hacker now knows that this 19:24:26.040 --> 19:24:28.006 align:start position:0% released the hacker now knows that this is<19:24:26.160> something<19:24:26.400> that<19:24:26.640> they<19:24:26.824> can<19:24:26.936> exploit<19:24:27.480> and 19:24:28.006 --> 19:24:28.016 align:start position:0% is something that they can exploit and 19:24:28.016 --> 19:24:29.990 align:start position:0% is something that they can exploit and so<19:24:28.192> the<19:24:28.440> longer<19:24:28.744> you<19:24:28.920> wait<19:24:29.104> to<19:24:29.336> update<19:24:29.640> it<19:24:29.824> the 19:24:29.990 --> 19:24:30.000 align:start position:0% so the longer you wait to update it the 19:24:30.000 --> 19:24:33.526 align:start position:0% so the longer you wait to update it the longer<19:24:30.360> you're<19:24:30.536> at<19:24:30.656> risk<19:24:30.896> of<19:24:31.080> being<19:24:31.320> exploited 19:24:33.526 --> 19:24:33.536 align:start position:0% longer you're at risk of being exploited 19:24:33.536 --> 19:24:35.566 align:start position:0% longer you're at risk of being exploited all<19:24:34.016> right<19:24:34.192> so<19:24:34.376> we<19:24:34.744> talked<19:24:34.976> about<19:24:35.040> a<19:24:35.280> bunch<19:24:35.464> of 19:24:35.566 --> 19:24:35.576 align:start position:0% all right so we talked about a bunch of 19:24:35.576 --> 19:24:37.310 align:start position:0% all right so we talked about a bunch of things<19:24:35.824> in<19:24:36.120> this<19:24:36.240> module<19:24:36.656> some<19:24:36.896> of<19:24:37.016> this<19:24:37.144> is 19:24:37.310 --> 19:24:37.320 align:start position:0% things in this module some of this is 19:24:37.320 --> 19:24:38.926 align:start position:0% things in this module some of this is common<19:24:37.552> sense<19:24:37.856> but<19:24:38.216> these<19:24:38.464> are<19:24:38.512> things<19:24:38.760> that 19:24:38.926 --> 19:24:38.936 align:start position:0% common sense but these are things that 19:24:38.936 --> 19:24:40.910 align:start position:0% common sense but these are things that pop<19:24:39.120> up<19:24:39.240> on<19:24:39.424> the<19:24:39.536> network<19:24:39.600> plus<19:24:39.896> exam 19:24:40.910 --> 19:24:40.920 align:start position:0% pop up on the network plus exam 19:24:40.920 --> 19:24:42.526 align:start position:0% pop up on the network plus exam first<19:24:41.280> we<19:24:41.512> want<19:24:41.640> to<19:24:41.824> Define<19:24:41.936> Network 19:24:42.526 --> 19:24:42.536 align:start position:0% first we want to Define Network 19:24:42.536 --> 19:24:45.470 align:start position:0% first we want to Define Network mitigation<19:24:43.336> mitigation<19:24:44.336> the<19:24:44.696> word<19:24:44.872> literally 19:24:45.470 --> 19:24:45.480 align:start position:0% mitigation mitigation the word literally 19:24:45.480 --> 19:24:47.686 align:start position:0% mitigation mitigation the word literally means<19:24:46.016> to<19:24:46.496> lessen 19:24:47.686 --> 19:24:47.696 align:start position:0% means to lessen 19:24:47.696 --> 19:24:49.182 align:start position:0% means to lessen and<19:24:48.056> so<19:24:48.240> what<19:24:48.360> we're<19:24:48.480> doing<19:24:48.656> is<19:24:48.960> we're 19:24:49.182 --> 19:24:49.192 align:start position:0% and so what we're doing is we're 19:24:49.192 --> 19:24:52.070 align:start position:0% and so what we're doing is we're lessening<19:24:49.800> the<19:24:50.216> threats<19:24:50.576> that<19:24:50.824> can<19:24:51.000> hit<19:24:51.240> us 19:24:52.070 --> 19:24:52.080 align:start position:0% lessening the threats that can hit us 19:24:52.080 --> 19:24:54.286 align:start position:0% lessening the threats that can hit us some<19:24:52.552> of<19:24:52.680> the<19:24:52.800> steps<19:24:53.160> that<19:24:53.400> we<19:24:53.576> identified<19:24:54.000> in 19:24:54.286 --> 19:24:54.296 align:start position:0% some of the steps that we identified in 19:24:54.296 --> 19:24:56.270 align:start position:0% some of the steps that we identified in this<19:24:54.480> strategy<19:24:54.832> were<19:24:55.504> first<19:24:55.744> to<19:24:55.976> develop 19:24:56.270 --> 19:24:56.280 align:start position:0% this strategy were first to develop 19:24:56.280 --> 19:24:59.094 align:start position:0% this strategy were first to develop strong<19:24:56.640> policies<19:24:57.360> for<19:24:58.192> instance<19:24:58.440> a<19:24:58.976> password 19:24:59.094 --> 19:24:59.104 align:start position:0% strong policies for instance a password 19:24:59.104 --> 19:25:01.134 align:start position:0% strong policies for instance a password policy<19:24:59.872> is<19:25:00.056> important 19:25:01.134 --> 19:25:01.144 align:start position:0% policy is important 19:25:01.144 --> 19:25:04.734 align:start position:0% policy is important download<19:25:01.856> policies 19:25:04.734 --> 19:25:04.744 align:start position:0% 19:25:04.744 --> 19:25:08.206 align:start position:0% internet<19:25:05.400> use<19:25:05.936> policies 19:25:08.206 --> 19:25:08.216 align:start position:0% internet use policies 19:25:08.216 --> 19:25:11.094 align:start position:0% internet use policies and<19:25:08.824> so<19:25:08.936> on<19:25:09.120> and<19:25:09.240> so<19:25:09.424> forth<19:25:09.784> we<19:25:10.552> also<19:25:10.744> need<19:25:10.856> to 19:25:11.094 --> 19:25:11.104 align:start position:0% and so on and so forth we also need to 19:25:11.104 --> 19:25:14.566 align:start position:0% and so on and so forth we also need to monitor<19:25:11.464> threats<19:25:12.000> not<19:25:12.720> just<19:25:12.896> internal 19:25:14.566 --> 19:25:14.576 align:start position:0% monitor threats not just internal 19:25:14.576 --> 19:25:17.326 align:start position:0% monitor threats not just internal but<19:25:15.056> we<19:25:15.240> need<19:25:15.424> to<19:25:15.784> research<19:25:16.496> what's<19:25:16.856> going<19:25:17.104> on 19:25:17.326 --> 19:25:17.336 align:start position:0% but we need to research what's going on 19:25:17.336 --> 19:25:19.134 align:start position:0% but we need to research what's going on around<19:25:17.640> the<19:25:18.000> world<19:25:18.120> so<19:25:18.480> we<19:25:18.656> know<19:25:18.784> what<19:25:18.960> the 19:25:19.134 --> 19:25:19.144 align:start position:0% around the world so we know what the 19:25:19.144 --> 19:25:20.566 align:start position:0% around the world so we know what the latest<19:25:19.256> things<19:25:19.552> are<19:25:19.744> that<19:25:19.920> are<19:25:20.040> attacking<19:25:20.400> our 19:25:20.566 --> 19:25:20.576 align:start position:0% latest things are that are attacking our 19:25:20.576 --> 19:25:22.070 align:start position:0% latest things are that are attacking our systems 19:25:22.070 --> 19:25:22.080 align:start position:0% systems 19:25:22.080 --> 19:25:24.286 align:start position:0% systems the<19:25:22.616> most<19:25:22.856> important<19:25:23.400> one<19:25:23.640> I<19:25:23.872> think<19:25:24.000> is 19:25:24.286 --> 19:25:24.296 align:start position:0% the most important one I think is 19:25:24.296 --> 19:25:27.286 align:start position:0% the most important one I think is educating<19:25:24.784> users<19:25:25.320> social<19:25:26.216> engineering<19:25:26.936> is 19:25:27.286 --> 19:25:27.296 align:start position:0% educating users social engineering is 19:25:27.296 --> 19:25:30.774 align:start position:0% educating users social engineering is how<19:25:27.600> hackers<19:25:28.144> and<19:25:28.320> attackers<19:25:28.800> get<19:25:29.640> around<19:25:30.056> the 19:25:30.774 --> 19:25:30.784 align:start position:0% how hackers and attackers get around the 19:25:30.784 --> 19:25:32.150 align:start position:0% how hackers and attackers get around the human<19:25:30.960> element<19:25:31.320> when<19:25:31.744> there's<19:25:31.856> a<19:25:32.040> human 19:25:32.150 --> 19:25:32.160 align:start position:0% human element when there's a human 19:25:32.160 --> 19:25:35.030 align:start position:0% human element when there's a human element<19:25:32.464> there's<19:25:33.176> a<19:25:33.424> flaw<19:25:33.784> and<19:25:34.496> so<19:25:34.616> we<19:25:34.744> need<19:25:34.920> to 19:25:35.030 --> 19:25:35.040 align:start position:0% element there's a flaw and so we need to 19:25:35.040 --> 19:25:38.686 align:start position:0% element there's a flaw and so we need to educate<19:25:35.464> users<19:25:35.872> so<19:25:36.240> they<19:25:36.536> don't<19:25:36.896> click<19:25:37.320> things 19:25:38.686 --> 19:25:38.696 align:start position:0% educate users so they don't click things 19:25:38.696 --> 19:25:42.886 align:start position:0% educate users so they don't click things that<19:25:39.296> look<19:25:39.480> bad<19:25:39.720> and<19:25:40.552> they<19:25:41.104> know 19:25:42.886 --> 19:25:42.896 align:start position:0% that look bad and they know 19:25:42.896 --> 19:25:45.774 align:start position:0% that look bad and they know when<19:25:43.744> to<19:25:43.920> ask<19:25:44.280> questions<19:25:44.760> since<19:25:45.424> this<19:25:45.656> can 19:25:45.774 --> 19:25:45.784 align:start position:0% when to ask questions since this can 19:25:45.784 --> 19:25:47.206 align:start position:0% when to ask questions since this can help<19:25:45.960> them<19:25:46.192> as<19:25:46.376> well 19:25:47.206 --> 19:25:47.216 align:start position:0% help them as well 19:25:47.216 --> 19:25:49.006 align:start position:0% help them as well we<19:25:47.640> also<19:25:47.824> want<19:25:47.936> to<19:25:48.056> automate<19:25:48.360> scanning<19:25:48.832> and 19:25:49.006 --> 19:25:49.016 align:start position:0% we also want to automate scanning and 19:25:49.016 --> 19:25:51.710 align:start position:0% we also want to automate scanning and updates<19:25:49.376> from<19:25:49.856> virus<19:25:50.336> scan<19:25:50.576> programs<19:25:51.176> and 19:25:51.710 --> 19:25:51.720 align:start position:0% updates from virus scan programs and 19:25:51.720 --> 19:25:53.990 align:start position:0% updates from virus scan programs and perhaps<19:25:52.016> our<19:25:52.192> firewall<19:25:52.744> this<19:25:53.640> should<19:25:53.824> all 19:25:53.990 --> 19:25:54.000 align:start position:0% perhaps our firewall this should all 19:25:54.000 --> 19:25:58.182 align:start position:0% perhaps our firewall this should all happen<19:25:54.296> automatically 19:25:58.182 --> 19:25:58.192 align:start position:0% 19:25:58.192 --> 19:26:01.030 align:start position:0% because<19:25:58.744> if<19:25:59.464> we<19:25:59.760> remove<19:26:00.176> the<19:26:00.536> human<19:26:00.720> element 19:26:01.030 --> 19:26:01.040 align:start position:0% because if we remove the human element 19:26:01.040 --> 19:26:03.710 align:start position:0% because if we remove the human element then<19:26:02.040> there's<19:26:02.280> not<19:26:02.464> going<19:26:02.576> to<19:26:02.696> be<19:26:02.760> an<19:26:02.872> issue<19:26:03.176> we 19:26:03.710 --> 19:26:03.720 align:start position:0% then there's not going to be an issue we 19:26:03.720 --> 19:26:06.046 align:start position:0% then there's not going to be an issue we also<19:26:03.960> want 19:26:06.046 --> 19:26:06.056 align:start position:0% also want 19:26:06.056 --> 19:26:07.670 align:start position:0% also want scans<19:26:06.600> to<19:26:06.784> happen<19:26:06.960> in<19:26:07.192> the<19:26:07.320> middle<19:26:07.440> of<19:26:07.616> the 19:26:07.670 --> 19:26:07.680 align:start position:0% scans to happen in the middle of the 19:26:07.680 --> 19:26:10.070 align:start position:0% scans to happen in the middle of the night<19:26:07.856> when<19:26:08.464> no<19:26:08.640> one<19:26:08.760> else<19:26:08.936> is<19:26:09.120> using<19:26:09.536> it<19:26:09.600> for 19:26:10.070 --> 19:26:10.080 align:start position:0% night when no one else is using it for 19:26:10.080 --> 19:26:12.710 align:start position:0% night when no one else is using it for instance<19:26:10.256> 2<19:26:10.552> am<19:26:10.680> or<19:26:11.040> 1<19:26:11.216> am<19:26:11.400> make<19:26:12.240> sure<19:26:12.424> that<19:26:12.536> you 19:26:12.710 --> 19:26:12.720 align:start position:0% instance 2 am or 1 am make sure that you 19:26:12.720 --> 19:26:14.750 align:start position:0% instance 2 am or 1 am make sure that you give<19:26:12.832> enough<19:26:13.016> time<19:26:13.440> for<19:26:13.856> the<19:26:13.976> scanner<19:26:14.400> to 19:26:14.750 --> 19:26:14.760 align:start position:0% give enough time for the scanner to 19:26:14.760 --> 19:26:17.094 align:start position:0% give enough time for the scanner to actually<19:26:14.936> scan<19:26:15.360> the<19:26:15.656> entire<19:26:15.896> system 19:26:17.094 --> 19:26:17.104 align:start position:0% actually scan the entire system 19:26:17.104 --> 19:26:19.910 align:start position:0% actually scan the entire system finally<19:26:17.824> we<19:26:18.120> need<19:26:18.240> patches<19:26:18.784> and<19:26:18.960> updates<19:26:19.320> and 19:26:19.910 --> 19:26:19.920 align:start position:0% finally we need patches and updates and 19:26:19.920 --> 19:26:21.822 align:start position:0% finally we need patches and updates and we<19:26:20.104> want<19:26:20.280> to<19:26:20.464> balance 19:26:21.822 --> 19:26:21.832 align:start position:0% we want to balance 19:26:21.832 --> 19:26:25.734 align:start position:0% we want to balance the<19:26:22.320> patches<19:26:22.680> and<19:26:22.856> the<19:26:22.976> updates<19:26:23.600> with<19:26:24.600> uh<19:26:25.144> the 19:26:25.734 --> 19:26:25.744 align:start position:0% the patches and the updates with uh the 19:26:25.744 --> 19:26:29.862 align:start position:0% the patches and the updates with uh the patch<19:26:26.104> actually<19:26:26.280> doing<19:26:26.576> harm 19:26:29.862 --> 19:26:29.872 align:start position:0% 19:26:29.872 --> 19:26:33.286 align:start position:0% versus<19:26:30.536> the<19:26:31.320> weakness 19:26:33.286 --> 19:26:33.296 align:start position:0% versus the weakness 19:26:33.296 --> 19:26:37.606 align:start position:0% versus the weakness or<19:26:33.832> exploit<19:26:34.376> that<19:26:34.856> it's<19:26:35.040> correcting 19:26:37.606 --> 19:26:37.616 align:start position:0% or exploit that it's correcting 19:26:37.616 --> 19:26:40.846 align:start position:0% or exploit that it's correcting the<19:26:38.160> longer<19:26:38.512> we<19:26:38.760> wait 19:26:40.846 --> 19:26:40.856 align:start position:0% the longer we wait 19:26:40.856 --> 19:26:44.030 align:start position:0% the longer we wait to<19:26:41.336> employ<19:26:41.640> a<19:26:42.176> new<19:26:42.296> patch<19:26:42.720> or<19:26:42.784> update 19:26:44.030 --> 19:26:44.040 align:start position:0% to employ a new patch or update 19:26:44.040 --> 19:26:50.240 align:start position:0% to employ a new patch or update the<19:26:44.824> longer<19:26:45.424> we're<19:26:45.784> at<19:26:46.016> risk 19:26:50.240 --> 19:26:50.250 align:start position:0% 19:26:50.250 --> 19:26:59.590 align:start position:0% [Music] 19:26:59.590 --> 19:26:59.600 align:start position:0% [Music] 19:26:59.600 --> 19:27:06.886 align:start position:0% [Music] thank<19:27:00.600> you 19:27:06.886 --> 19:27:06.896 align:start position:0% 19:27:06.896 --> 19:27:10.910 align:start position:0% welcome<19:27:07.320> to<19:27:07.504> module<19:27:07.920> 14<19:27:08.040> lesson<19:27:08.824> 2A<19:27:09.920> Advanced 19:27:10.910 --> 19:27:10.920 align:start position:0% welcome to module 14 lesson 2A Advanced 19:27:10.920 --> 19:27:13.182 align:start position:0% welcome to module 14 lesson 2A Advanced threat<19:27:11.336> mitigation 19:27:13.182 --> 19:27:13.192 align:start position:0% threat mitigation 19:27:13.192 --> 19:27:16.366 align:start position:0% threat mitigation so<19:27:13.552> this<19:27:13.744> is<19:27:13.856> new<19:27:14.160> stuff<19:27:14.400> for<19:27:14.760> the<19:27:15.600> um<19:27:15.656> double 19:27:16.366 --> 19:27:16.376 align:start position:0% so this is new stuff for the um double 19:27:16.376 --> 19:27:20.686 align:start position:0% so this is new stuff for the um double 07<19:27:16.936> version<19:27:17.936> of<19:27:18.296> the<19:27:18.480> com2<19:27:18.960> exam<19:27:19.856> managing 19:27:20.686 --> 19:27:20.696 align:start position:0% 07 version of the com2 exam managing 19:27:20.696 --> 19:27:23.350 align:start position:0% 07 version of the com2 exam managing your<19:27:20.824> signatures<19:27:21.616> hardening<19:27:22.616> your<19:27:22.800> devices 19:27:23.350 --> 19:27:23.360 align:start position:0% your signatures hardening your devices 19:27:23.360 --> 19:27:26.502 align:start position:0% your signatures hardening your devices in<19:27:24.360> terms<19:27:24.536> of<19:27:24.600> security<19:27:24.832> that<19:27:25.320> is<19:27:25.512> changing 19:27:26.502 --> 19:27:26.512 align:start position:0% in terms of security that is changing 19:27:26.512 --> 19:27:28.790 align:start position:0% in terms of security that is changing your<19:27:26.760> native<19:27:27.056> VLAN 19:27:28.790 --> 19:27:28.800 align:start position:0% your native VLAN 19:27:28.800 --> 19:27:31.846 align:start position:0% your native VLAN switch<19:27:29.512> Port<19:27:29.872> protection 19:27:31.846 --> 19:27:31.856 align:start position:0% switch Port protection 19:27:31.856 --> 19:27:34.310 align:start position:0% switch Port protection restricting<19:27:32.576> access<19:27:32.824> with<19:27:33.424> access<19:27:33.720> lists 19:27:34.310 --> 19:27:34.320 align:start position:0% restricting access with access lists 19:27:34.320 --> 19:27:37.670 align:start position:0% restricting access with access lists Honeypot<19:27:35.160> and<19:27:35.336> honey<19:27:35.512> net<19:27:36.192> uh<19:27:37.192> penetration 19:27:37.670 --> 19:27:37.680 align:start position:0% Honeypot and honey net uh penetration 19:27:37.680 --> 19:27:40.910 align:start position:0% Honeypot and honey net uh penetration testing<19:27:38.280> so<19:27:39.176> signatures<19:27:39.832> in<19:27:40.744> terms<19:27:40.856> of 19:27:40.910 --> 19:27:40.920 align:start position:0% testing so signatures in terms of 19:27:40.920 --> 19:27:42.414 align:start position:0% testing so signatures in terms of signature<19:27:41.400> management<19:27:41.640> we're<19:27:42.000> talking<19:27:42.176> about 19:27:42.414 --> 19:27:42.424 align:start position:0% signature management we're talking about 19:27:42.424 --> 19:27:45.774 align:start position:0% signature management we're talking about IDs<19:27:43.016> and<19:27:43.192> IPS<19:27:43.504> which<19:27:44.040> we've<19:27:44.280> covered<19:27:44.576> earlier 19:27:45.774 --> 19:27:45.784 align:start position:0% IDs and IPS which we've covered earlier 19:27:45.784 --> 19:27:48.046 align:start position:0% IDs and IPS which we've covered earlier the<19:27:46.440> signature-based<19:27:47.216> detection<19:27:47.464> examines 19:27:48.046 --> 19:27:48.056 align:start position:0% the signature-based detection examines 19:27:48.056 --> 19:27:50.094 align:start position:0% the signature-based detection examines Network<19:27:48.424> traffic<19:27:48.784> for<19:27:49.192> pre-configured<19:27:49.856> and 19:27:50.094 --> 19:27:50.104 align:start position:0% Network traffic for pre-configured and 19:27:50.104 --> 19:27:52.430 align:start position:0% Network traffic for pre-configured and predetermined<19:27:50.824> attacks<19:27:51.296> so<19:27:51.784> the<19:27:51.960> signature 19:27:52.430 --> 19:27:52.440 align:start position:0% predetermined attacks so the signature 19:27:52.440 --> 19:27:55.246 align:start position:0% predetermined attacks so the signature is<19:27:52.552> the<19:27:52.744> thing<19:27:52.920> that<19:27:53.336> is<19:27:53.784> matched<19:27:54.784> against<19:27:54.896> in 19:27:55.246 --> 19:27:55.256 align:start position:0% is the thing that is matched against in 19:27:55.256 --> 19:27:57.470 align:start position:0% is the thing that is matched against in these<19:27:55.552> devices<19:27:55.856> the<19:27:56.512> threat<19:27:56.824> the<19:27:57.120> threat 19:27:57.470 --> 19:27:57.480 align:start position:0% these devices the threat the threat 19:27:57.480 --> 19:27:58.606 align:start position:0% these devices the threat the threat signature 19:27:58.606 --> 19:27:58.616 align:start position:0% signature 19:27:58.616 --> 19:28:01.966 align:start position:0% signature these<19:27:59.336> are<19:27:59.464> known<19:27:59.640> as<19:27:59.824> signatures<19:28:00.656> attacker 19:28:01.966 --> 19:28:01.976 align:start position:0% these are known as signatures attacker 19:28:01.976 --> 19:28:03.910 align:start position:0% these are known as signatures attacker um<19:28:02.040> convinces<19:28:02.936> employee<19:28:03.360> to<19:28:03.480> disclose 19:28:03.910 --> 19:28:03.920 align:start position:0% um convinces employee to disclose 19:28:03.920 --> 19:28:06.646 align:start position:0% um convinces employee to disclose confidential<19:28:04.920> information 19:28:06.646 --> 19:28:06.656 align:start position:0% confidential information 19:28:06.656 --> 19:28:08.630 align:start position:0% confidential information if<19:28:07.080> adult<19:28:07.256> signature<19:28:07.744> is<19:28:07.856> identified<19:28:08.216> by<19:28:08.464> the 19:28:08.630 --> 19:28:08.640 align:start position:0% if adult signature is identified by the 19:28:08.640 --> 19:28:10.846 align:start position:0% if adult signature is identified by the system<19:28:08.824> an<19:28:09.176> alarm<19:28:09.360> is<19:28:09.720> triggered<19:28:10.192> or<19:28:10.680> the 19:28:10.846 --> 19:28:10.856 align:start position:0% system an alarm is triggered or the 19:28:10.856 --> 19:28:12.710 align:start position:0% system an alarm is triggered or the traffic<19:28:11.040> will<19:28:11.400> be<19:28:11.640> blocked<19:28:12.056> this<19:28:12.240> it<19:28:12.424> depends 19:28:12.710 --> 19:28:12.720 align:start position:0% traffic will be blocked this it depends 19:28:12.720 --> 19:28:15.646 align:start position:0% traffic will be blocked this it depends on<19:28:12.832> how<19:28:13.144> you've<19:28:13.376> configured<19:28:13.920> your 19:28:15.646 --> 19:28:15.656 align:start position:0% on how you've configured your 19:28:15.656 --> 19:28:19.134 align:start position:0% on how you've configured your um<19:28:15.720> IDs<19:28:16.320> and<19:28:16.440> IPS<19:28:16.872> so<19:28:17.872> it<19:28:18.176> will<19:28:18.296> either 19:28:19.134 --> 19:28:19.144 align:start position:0% um IDs and IPS so it will either 19:28:19.144 --> 19:28:22.966 align:start position:0% um IDs and IPS so it will either um<19:28:19.192> send<19:28:19.920> an<19:28:20.104> SNMP<19:28:20.696> alert<19:28:21.440> or<19:28:22.440> create<19:28:22.744> some 19:28:22.966 --> 19:28:22.976 align:start position:0% um send an SNMP alert or create some 19:28:22.976 --> 19:28:25.070 align:start position:0% um send an SNMP alert or create some sort<19:28:23.160> of<19:28:23.280> log<19:28:23.400> message<19:28:23.760> or<19:28:24.600> whatever<19:28:24.784> you've 19:28:25.070 --> 19:28:25.080 align:start position:0% sort of log message or whatever you've 19:28:25.080 --> 19:28:28.070 align:start position:0% sort of log message or whatever you've designed<19:28:25.552> it<19:28:25.856> to<19:28:26.104> do<19:28:26.480> the<19:28:27.480> signature<19:28:27.896> codes 19:28:28.070 --> 19:28:28.080 align:start position:0% designed it to do the signature codes 19:28:28.080 --> 19:28:29.630 align:start position:0% designed it to do the signature codes are<19:28:28.320> updated<19:28:28.616> or<19:28:28.920> they<19:28:29.040> should<19:28:29.160> be<19:28:29.280> updated 19:28:29.630 --> 19:28:29.640 align:start position:0% are updated or they should be updated 19:28:29.640 --> 19:28:32.630 align:start position:0% are updated or they should be updated regularly<19:28:30.176> for<19:28:30.600> new<19:28:30.896> or<19:28:31.616> false<19:28:32.040> patterns<19:28:32.464> you 19:28:32.630 --> 19:28:32.640 align:start position:0% regularly for new or false patterns you 19:28:32.640 --> 19:28:33.950 align:start position:0% regularly for new or false patterns you don't<19:28:32.760> you<19:28:33.176> really<19:28:33.296> don't<19:28:33.480> want<19:28:33.600> false 19:28:33.950 --> 19:28:33.960 align:start position:0% don't you really don't want false 19:28:33.960 --> 19:28:35.390 align:start position:0% don't you really don't want false positives<19:28:34.376> either<19:28:34.552> because<19:28:34.856> it's<19:28:35.040> just<19:28:35.216> going 19:28:35.390 --> 19:28:35.400 align:start position:0% positives either because it's just going 19:28:35.400 --> 19:28:37.606 align:start position:0% positives either because it's just going to<19:28:35.576> be<19:28:36.056> in<19:28:36.240> traffic's<19:28:37.016> blocked<19:28:37.256> when<19:28:37.440> it 19:28:37.606 --> 19:28:37.616 align:start position:0% to be in traffic's blocked when it 19:28:37.616 --> 19:28:38.862 align:start position:0% to be in traffic's blocked when it shouldn't<19:28:37.856> be 19:28:38.862 --> 19:28:38.872 align:start position:0% shouldn't be 19:28:38.872 --> 19:28:41.470 align:start position:0% shouldn't be uh<19:28:39.480> there's<19:28:39.784> a<19:28:39.960> website<19:28:40.496> called<19:28:40.680> threat 19:28:41.470 --> 19:28:41.480 align:start position:0% uh there's a website called threat 19:28:41.480 --> 19:28:43.734 align:start position:0% uh there's a website called threat threatconnect.com<19:28:42.480> they<19:28:42.960> offer<19:28:43.376> some<19:28:43.552> sort 19:28:43.734 --> 19:28:43.744 align:start position:0% threatconnect.com they offer some sort 19:28:43.744 --> 19:28:47.270 align:start position:0% threatconnect.com they offer some sort of<19:28:43.856> signature<19:28:44.824> management<19:28:45.440> uh<19:28:46.440> system<19:28:46.744> for 19:28:47.270 --> 19:28:47.280 align:start position:0% of signature management uh system for 19:28:47.280 --> 19:28:48.414 align:start position:0% of signature management uh system for for<19:28:47.512> you<19:28:47.640> to<19:28:47.760> look<19:28:47.872> after<19:28:48.000> all<19:28:48.240> your 19:28:48.414 --> 19:28:48.424 align:start position:0% for you to look after all your 19:28:48.424 --> 19:28:51.046 align:start position:0% for you to look after all your signatures<19:28:49.040> uh<19:28:50.040> I<19:28:50.216> I<19:28:50.336> only<19:28:50.512> suggest<19:28:50.872> it 19:28:51.046 --> 19:28:51.056 align:start position:0% signatures uh I I only suggest it 19:28:51.056 --> 19:28:53.150 align:start position:0% signatures uh I I only suggest it because<19:28:51.176> I<19:28:51.424> use<19:28:51.600> their<19:28:51.832> graphic<19:28:52.256> and<19:28:52.496> I<19:28:52.744> wanted 19:28:53.150 --> 19:28:53.160 align:start position:0% because I use their graphic and I wanted 19:28:53.160 --> 19:28:55.134 align:start position:0% because I use their graphic and I wanted to<19:28:53.400> credit<19:28:53.576> them<19:28:53.872> for<19:28:54.056> that<19:28:54.240> but<19:28:54.656> this<19:28:54.832> is<19:28:54.896> what 19:28:55.134 --> 19:28:55.144 align:start position:0% to credit them for that but this is what 19:28:55.144 --> 19:28:57.166 align:start position:0% to credit them for that but this is what came<19:28:55.320> up<19:28:55.440> when<19:28:55.616> I<19:28:55.800> was<19:28:55.920> researching<19:28:56.760> threat 19:28:57.166 --> 19:28:57.176 align:start position:0% came up when I was researching threat 19:28:57.176 --> 19:28:58.966 align:start position:0% came up when I was researching threat signatures 19:28:58.966 --> 19:28:58.976 align:start position:0% signatures 19:28:58.976 --> 19:29:01.494 align:start position:0% signatures device<19:28:59.464> hardening<19:29:00.120> this<19:29:00.424> is<19:29:00.600> part<19:29:00.832> of<19:29:01.080> your 19:29:01.494 --> 19:29:01.504 align:start position:0% device hardening this is part of your 19:29:01.504 --> 19:29:05.630 align:start position:0% device hardening this is part of your daily<19:29:02.280> weekly<19:29:02.872> monthly<19:29:03.616> admin<19:29:04.616> task 19:29:05.630 --> 19:29:05.640 align:start position:0% daily weekly monthly admin task 19:29:05.640 --> 19:29:07.366 align:start position:0% daily weekly monthly admin task especially<19:29:06.424> if<19:29:06.656> you're<19:29:06.832> in<19:29:07.016> charge<19:29:07.192> of 19:29:07.366 --> 19:29:07.376 align:start position:0% especially if you're in charge of 19:29:07.376 --> 19:29:08.166 align:start position:0% especially if you're in charge of security 19:29:08.166 --> 19:29:08.176 align:start position:0% security 19:29:08.176 --> 19:29:11.030 align:start position:0% security for<19:29:09.176> uh<19:29:09.536> looking<19:29:09.656> after<19:29:09.896> your<19:29:10.144> network 19:29:11.030 --> 19:29:11.040 align:start position:0% for uh looking after your network 19:29:11.040 --> 19:29:13.134 align:start position:0% for uh looking after your network you'll<19:29:11.640> Pat<19:29:11.824> your<19:29:12.056> update<19:29:12.424> software<19:29:12.896> or 19:29:13.134 --> 19:29:13.144 align:start position:0% you'll Pat your update software or 19:29:13.144 --> 19:29:16.310 align:start position:0% you'll Pat your update software or firmware<19:29:13.616> in<19:29:13.920> your<19:29:14.336> Hardware<19:29:14.576> devices 19:29:16.310 --> 19:29:16.320 align:start position:0% firmware in your Hardware devices 19:29:16.320 --> 19:29:19.430 align:start position:0% firmware in your Hardware devices check<19:29:16.800> for<19:29:16.976> non-compliant<19:29:17.640> passwords<19:29:18.440> this 19:29:19.430 --> 19:29:19.440 align:start position:0% check for non-compliant passwords this 19:29:19.440 --> 19:29:20.454 align:start position:0% check for non-compliant passwords this will<19:29:19.616> obviously<19:29:19.856> part<19:29:20.040> of<19:29:20.160> your<19:29:20.280> password 19:29:20.454 --> 19:29:20.464 align:start position:0% will obviously part of your password 19:29:20.464 --> 19:29:23.454 align:start position:0% will obviously part of your password policy<19:29:21.120> but<19:29:21.424> I'm<19:29:22.016> sure<19:29:22.192> you've<19:29:22.616> logged<19:29:23.336> into 19:29:23.454 --> 19:29:23.464 align:start position:0% policy but I'm sure you've logged into 19:29:23.464 --> 19:29:26.750 align:start position:0% policy but I'm sure you've logged into something<19:29:23.872> or<19:29:24.480> had<19:29:24.784> an<19:29:24.960> email<19:29:25.144> updating<19:29:25.680> you 19:29:26.750 --> 19:29:26.760 align:start position:0% something or had an email updating you 19:29:26.760 --> 19:29:29.150 align:start position:0% something or had an email updating you saying<19:29:27.424> that<19:29:27.536> your<19:29:27.784> current<19:29:27.896> password<19:29:28.192> isn't 19:29:29.150 --> 19:29:29.160 align:start position:0% saying that your current password isn't 19:29:29.160 --> 19:29:30.590 align:start position:0% saying that your current password isn't um strong<19:29:29.336> enough<19:29:29.576> and<19:29:29.872> you<19:29:30.000> need<19:29:30.176> to<19:29:30.240> update 19:29:30.590 --> 19:29:30.600 align:start position:0% um strong enough and you need to update 19:29:30.600 --> 19:29:31.670 align:start position:0% um strong enough and you need to update it 19:29:31.670 --> 19:29:31.680 align:start position:0% it 19:29:31.680 --> 19:29:33.822 align:start position:0% it removing<19:29:32.280> redundant<19:29:32.872> networks<19:29:33.360> and<19:29:33.536> IP 19:29:33.822 --> 19:29:33.832 align:start position:0% removing redundant networks and IP 19:29:33.832 --> 19:29:36.526 align:start position:0% removing redundant networks and IP addresses<19:29:34.376> strangely<19:29:35.040> enough<19:29:35.240> I've<19:29:36.240> known 19:29:36.526 --> 19:29:36.536 align:start position:0% addresses strangely enough I've known 19:29:36.536 --> 19:29:39.950 align:start position:0% addresses strangely enough I've known equipment<19:29:37.504> found<19:29:37.920> years<19:29:38.512> after<19:29:38.960> people 19:29:39.950 --> 19:29:39.960 align:start position:0% equipment found years after people 19:29:39.960 --> 19:29:41.502 align:start position:0% equipment found years after people thought<19:29:40.192> it<19:29:40.376> had<19:29:40.496> been<19:29:40.680> decommissioned<19:29:41.336> it's 19:29:41.502 --> 19:29:41.512 align:start position:0% thought it had been decommissioned it's 19:29:41.512 --> 19:29:43.430 align:start position:0% thought it had been decommissioned it's sitting<19:29:41.872> in<19:29:42.000> a<19:29:42.240> office<19:29:42.536> somewhere<19:29:43.016> plugged 19:29:43.430 --> 19:29:43.440 align:start position:0% sitting in a office somewhere plugged 19:29:43.440 --> 19:29:45.886 align:start position:0% sitting in a office somewhere plugged into<19:29:43.552> the<19:29:43.800> network<19:29:44.040> and<19:29:45.000> nobody<19:29:45.360> knew<19:29:45.600> it<19:29:45.720> was 19:29:45.886 --> 19:29:45.896 align:start position:0% into the network and nobody knew it was 19:29:45.896 --> 19:29:48.166 align:start position:0% into the network and nobody knew it was there<19:29:46.144> and<19:29:46.552> this<19:29:46.800> can<19:29:46.976> then<19:29:47.280> be<19:29:47.640> a<19:29:47.824> back<19:29:47.936> door 19:29:48.166 --> 19:29:48.176 align:start position:0% there and this can then be a back door 19:29:48.176 --> 19:29:50.814 align:start position:0% there and this can then be a back door for<19:29:49.016> hackers<19:29:49.440> to<19:29:49.616> find<19:29:49.800> and<19:29:50.104> get<19:29:50.464> into<19:29:50.640> your 19:29:50.814 --> 19:29:50.824 align:start position:0% for hackers to find and get into your 19:29:50.824 --> 19:29:54.350 align:start position:0% for hackers to find and get into your network<19:29:51.192> changing<19:29:52.192> security<19:29:52.496> keys 19:29:54.350 --> 19:29:54.360 align:start position:0% network changing security keys 19:29:54.360 --> 19:29:56.862 align:start position:0% network changing security keys are<19:29:54.960> changing<19:29:55.504> the<19:29:55.616> native<19:29:55.800> VLAN<19:29:56.400> so<19:29:56.760> the 19:29:56.862 --> 19:29:56.872 align:start position:0% are changing the native VLAN so the 19:29:56.872 --> 19:29:59.862 align:start position:0% are changing the native VLAN so the native<19:29:57.080> VLAN<19:29:58.080> is<19:29:58.256> used<19:29:58.440> for<19:29:58.680> any<19:29:58.976> untagged 19:29:59.862 --> 19:29:59.872 align:start position:0% native VLAN is used for any untagged 19:29:59.872 --> 19:30:02.454 align:start position:0% native VLAN is used for any untagged traffic<19:30:00.600> on<19:30:01.144> your<19:30:01.320> network<19:30:01.552> you'll<19:30:02.336> be 19:30:02.454 --> 19:30:02.464 align:start position:0% traffic on your network you'll be 19:30:02.464 --> 19:30:03.886 align:start position:0% traffic on your network you'll be familiar<19:30:02.760> with<19:30:02.872> this<19:30:03.000> when<19:30:03.296> you<19:30:03.424> start<19:30:03.600> doing 19:30:03.886 --> 19:30:03.896 align:start position:0% familiar with this when you start doing 19:30:03.896 --> 19:30:06.950 align:start position:0% familiar with this when you start doing Cisco<19:30:04.824> configuration<19:30:05.824> or<19:30:06.360> any<19:30:06.536> type<19:30:06.784> of 19:30:06.950 --> 19:30:06.960 align:start position:0% Cisco configuration or any type of 19:30:06.960 --> 19:30:10.606 align:start position:0% Cisco configuration or any type of juniper<19:30:07.552> or<19:30:07.920> the<19:30:08.216> other<19:30:08.512> network<19:30:09.240> management 19:30:10.606 --> 19:30:10.616 align:start position:0% juniper or the other network management 19:30:10.616 --> 19:30:13.310 align:start position:0% juniper or the other network management big<19:30:11.040> security<19:30:11.280> vulnerability<19:30:12.176> your<19:30:13.080> native 19:30:13.310 --> 19:30:13.320 align:start position:0% big security vulnerability your native 19:30:13.320 --> 19:30:16.310 align:start position:0% big security vulnerability your native VLAN<19:30:13.856> is<19:30:14.576> passes<19:30:15.480> important<19:30:16.144> information 19:30:16.310 --> 19:30:16.320 align:start position:0% VLAN is passes important information 19:30:16.320 --> 19:30:18.414 align:start position:0% VLAN is passes important information such<19:30:17.040> as 19:30:18.414 --> 19:30:18.424 align:start position:0% such as 19:30:18.424 --> 19:30:21.046 align:start position:0% such as um<19:30:18.480> your<19:30:19.192> Cisco<19:30:19.552> Discovery<19:30:20.104> protocol<19:30:20.512> or<19:30:20.872> the 19:30:21.046 --> 19:30:21.056 align:start position:0% um your Cisco Discovery protocol or the 19:30:21.056 --> 19:30:24.646 align:start position:0% um your Cisco Discovery protocol or the equivalent<19:30:21.536> which<19:30:22.144> is<19:30:22.256> device<19:30:22.616> information 19:30:24.646 --> 19:30:24.656 align:start position:0% equivalent which is device information 19:30:24.656 --> 19:30:26.286 align:start position:0% equivalent which is device information foreign 19:30:26.286 --> 19:30:26.296 align:start position:0% foreign 19:30:26.296 --> 19:30:29.030 align:start position:0% foreign your<19:30:27.296> operating<19:30:27.600> system<19:30:27.896> that<19:30:28.256> it's<19:30:28.376> running 19:30:29.030 --> 19:30:29.040 align:start position:0% your operating system that it's running 19:30:29.040 --> 19:30:31.670 align:start position:0% your operating system that it's running etc<19:30:29.336> etc<19:30:29.512> a<19:30:30.360> dynamic<19:30:30.656> drinking<19:30:31.016> protocol<19:30:31.376> is 19:30:31.670 --> 19:30:31.680 align:start position:0% etc etc a dynamic drinking protocol is 19:30:31.680 --> 19:30:35.990 align:start position:0% etc etc a dynamic drinking protocol is for<19:30:32.040> uh<19:30:32.512> trunking<19:30:33.320> so<19:30:34.320> your<19:30:34.920> native<19:30:35.216> VLAN<19:30:35.760> will 19:30:35.990 --> 19:30:36.000 align:start position:0% for uh trunking so your native VLAN will 19:30:36.000 --> 19:30:39.350 align:start position:0% for uh trunking so your native VLAN will normally<19:30:36.360> go<19:30:37.016> across<19:30:37.440> a<19:30:38.280> trunk<19:30:38.872> link<19:30:39.056> and 19:30:39.350 --> 19:30:39.360 align:start position:0% normally go across a trunk link and 19:30:39.360 --> 19:30:40.542 align:start position:0% normally go across a trunk link and you've<19:30:39.536> got<19:30:39.656> all<19:30:39.832> of<19:30:39.960> this<19:30:40.144> important 19:30:40.542 --> 19:30:40.552 align:start position:0% you've got all of this important 19:30:40.552 --> 19:30:41.470 align:start position:0% you've got all of this important information 19:30:41.470 --> 19:30:41.480 align:start position:0% information 19:30:41.480 --> 19:30:44.206 align:start position:0% information on<19:30:42.480> The<19:30:42.656> Cisco<19:30:43.144> devices<19:30:43.504> certainly<19:30:43.976> and 19:30:44.206 --> 19:30:44.216 align:start position:0% on The Cisco devices certainly and 19:30:44.216 --> 19:30:46.430 align:start position:0% on The Cisco devices certainly and probably<19:30:44.400> a<19:30:44.824> lot<19:30:44.936> of<19:30:45.000> other<19:30:45.120> vendors<19:30:45.656> the 19:30:46.430 --> 19:30:46.440 align:start position:0% probably a lot of other vendors the 19:30:46.440 --> 19:30:49.494 align:start position:0% probably a lot of other vendors the native<19:30:46.744> VLAN<19:30:47.280> is<19:30:47.464> VLAN<19:30:47.936> one<19:30:48.176> and<19:30:48.960> if<19:30:49.144> you<19:30:49.320> leave 19:30:49.494 --> 19:30:49.504 align:start position:0% native VLAN is VLAN one and if you leave 19:30:49.504 --> 19:30:53.390 align:start position:0% native VLAN is VLAN one and if you leave this<19:30:49.856> as<19:30:50.216> the<19:30:50.512> VLAN<19:30:51.240> that<19:30:51.496> the<19:30:52.496> switches<19:30:53.040> can 19:30:53.390 --> 19:30:53.400 align:start position:0% this as the VLAN that the switches can 19:30:53.400 --> 19:30:55.606 align:start position:0% this as the VLAN that the switches can communicate<19:30:54.000> with<19:30:54.296> you've<19:30:54.896> left<19:30:55.016> a<19:30:55.256> possible 19:30:55.606 --> 19:30:55.616 align:start position:0% communicate with you've left a possible 19:30:55.616 --> 19:30:58.070 align:start position:0% communicate with you've left a possible security<19:30:55.920> vulnerability 19:30:58.070 --> 19:30:58.080 align:start position:0% security vulnerability 19:30:58.080 --> 19:30:59.686 align:start position:0% security vulnerability because<19:30:58.616> this<19:30:58.976> traffic<19:30:59.160> is<19:30:59.464> actually 19:30:59.686 --> 19:30:59.696 align:start position:0% because this traffic is actually 19:30:59.696 --> 19:31:01.182 align:start position:0% because this traffic is actually untagged 19:31:01.182 --> 19:31:01.192 align:start position:0% untagged 19:31:01.192 --> 19:31:03.822 align:start position:0% untagged so<19:31:01.680> what<19:31:01.856> you<19:31:01.976> want<19:31:02.104> to<19:31:02.216> do<19:31:02.336> is<19:31:02.696> on<19:31:03.360> any<19:31:03.480> drunk 19:31:03.822 --> 19:31:03.832 align:start position:0% so what you want to do is on any drunk 19:31:03.832 --> 19:31:06.774 align:start position:0% so what you want to do is on any drunk leg<19:31:04.080> trunk<19:31:04.744> link<19:31:04.920> you<19:31:05.640> change<19:31:05.872> it<19:31:06.120> to<19:31:06.424> an 19:31:06.774 --> 19:31:06.784 align:start position:0% leg trunk link you change it to an 19:31:06.784 --> 19:31:09.590 align:start position:0% leg trunk link you change it to an unused<19:31:07.256> VLAN 19:31:09.590 --> 19:31:09.600 align:start position:0% unused VLAN 19:31:09.600 --> 19:31:12.286 align:start position:0% unused VLAN so<19:31:10.080> this<19:31:10.192> is<19:31:10.320> one<19:31:10.496> that<19:31:10.680> isn't<19:31:10.976> been<19:31:11.160> used<19:31:11.512> on 19:31:12.286 --> 19:31:12.296 align:start position:0% so this is one that isn't been used on 19:31:12.296 --> 19:31:13.182 align:start position:0% so this is one that isn't been used on um 19:31:13.182 --> 19:31:13.192 align:start position:0% um 19:31:13.192 --> 19:31:16.734 align:start position:0% um so<19:31:13.616> you've<19:31:13.800> got<19:31:13.856> to<19:31:14.040> VLAN<19:31:14.512> 10<19:31:14.696> 20 19:31:16.734 --> 19:31:16.744 align:start position:0% so you've got to VLAN 10 20 19:31:16.744 --> 19:31:20.454 align:start position:0% so you've got to VLAN 10 20 30<19:31:17.280> and<19:31:17.760> 40.<19:31:18.424> you<19:31:18.896> would<19:31:19.080> use<19:31:19.256> your<19:31:19.552> an<19:31:20.040> unused 19:31:20.454 --> 19:31:20.464 align:start position:0% 30 and 40. you would use your an unused 19:31:20.464 --> 19:31:23.094 align:start position:0% 30 and 40. you would use your an unused VLAN<19:31:20.824> on<19:31:21.056> your<19:31:21.176> trunk<19:31:21.424> links<19:31:21.832> for<19:31:22.016> example 19:31:23.094 --> 19:31:23.104 align:start position:0% VLAN on your trunk links for example 19:31:23.104 --> 19:31:24.046 align:start position:0% VLAN on your trunk links for example um 19:31:24.046 --> 19:31:24.056 align:start position:0% um 19:31:24.056 --> 19:31:26.990 align:start position:0% um two<19:31:24.960> two<19:31:25.144> two<19:31:25.440> just<19:31:26.104> something<19:31:26.216> fairly<19:31:26.824> high 19:31:26.990 --> 19:31:27.000 align:start position:0% two two two just something fairly high 19:31:27.000 --> 19:31:29.502 align:start position:0% two two two just something fairly high and<19:31:27.832> then<19:31:27.960> another<19:31:28.616> trunk<19:31:28.976> link<19:31:29.160> to<19:31:29.336> another 19:31:29.502 --> 19:31:29.512 align:start position:0% and then another trunk link to another 19:31:29.512 --> 19:31:31.430 align:start position:0% and then another trunk link to another switch 19:31:31.430 --> 19:31:31.440 align:start position:0% switch 19:31:31.440 --> 19:31:34.006 align:start position:0% switch you'd<19:31:32.040> have<19:31:32.160> another<19:31:32.280> VLAN<19:31:32.824> for<19:31:33.056> example<19:31:33.360> two 19:31:34.006 --> 19:31:34.016 align:start position:0% you'd have another VLAN for example two 19:31:34.016 --> 19:31:35.270 align:start position:0% you'd have another VLAN for example two two<19:31:34.080> three 19:31:35.270 --> 19:31:35.280 align:start position:0% two three 19:31:35.280 --> 19:31:38.270 align:start position:0% two three Etc 19:31:38.270 --> 19:31:38.280 align:start position:0% 19:31:38.280 --> 19:31:41.326 align:start position:0% is<19:31:38.640> the<19:31:39.000> output<19:31:39.360> for<19:31:39.600> a<19:31:39.720> Cisco<19:31:40.080> device<19:31:40.376> and<19:31:41.216> you 19:31:41.326 --> 19:31:41.336 align:start position:0% is the output for a Cisco device and you 19:31:41.336 --> 19:31:43.846 align:start position:0% is the output for a Cisco device and you can<19:31:41.464> see<19:31:41.760> this<19:31:42.176> is<19:31:42.296> trunk<19:31:42.720> in<19:31:42.896> so<19:31:43.144> it's<19:31:43.256> passing 19:31:43.846 --> 19:31:43.856 align:start position:0% can see this is trunk in so it's passing 19:31:43.856 --> 19:31:46.966 align:start position:0% can see this is trunk in so it's passing multiple<19:31:44.216> vlans<19:31:44.824> on<19:31:45.120> this<19:31:45.296> link<19:31:45.680> but<19:31:46.680> the 19:31:46.966 --> 19:31:46.976 align:start position:0% multiple vlans on this link but the 19:31:46.976 --> 19:31:51.646 align:start position:0% multiple vlans on this link but the native<19:31:47.216> VLAN<19:31:47.760> is<19:31:48.240> uh<19:31:48.424> VLAN<19:31:48.960> one 19:31:51.646 --> 19:31:51.656 align:start position:0% 19:31:51.656 --> 19:31:53.502 align:start position:0% so<19:31:51.896> I've<19:31:52.144> wiped<19:31:52.496> over<19:31:52.552> it<19:31:52.800> there<19:31:52.976> the<19:31:53.336> native 19:31:53.502 --> 19:31:53.512 align:start position:0% so I've wiped over it there the native 19:31:53.512 --> 19:31:56.150 align:start position:0% so I've wiped over it there the native VLAN<19:31:54.000> is<19:31:54.120> VLAN<19:31:54.536> one<19:31:54.720> which<19:31:54.960> you<19:31:55.144> don't<19:31:55.320> want<19:31:55.616> so 19:31:56.150 --> 19:31:56.160 align:start position:0% VLAN is VLAN one which you don't want so 19:31:56.160 --> 19:31:59.094 align:start position:0% VLAN is VLAN one which you don't want so what<19:31:56.464> I<19:31:56.696> did<19:31:56.936> I<19:31:57.296> went<19:31:57.536> to<19:31:57.720> the<19:31:58.144> trunk<19:31:58.552> interface 19:31:59.094 --> 19:31:59.104 align:start position:0% what I did I went to the trunk interface 19:31:59.104 --> 19:32:01.310 align:start position:0% what I did I went to the trunk interface here<19:31:59.400> I<19:32:00.056> issued<19:32:00.480> the<19:32:00.536> command<19:32:00.784> switchbot 19:32:01.310 --> 19:32:01.320 align:start position:0% here I issued the command switchbot 19:32:01.320 --> 19:32:04.910 align:start position:0% here I issued the command switchbot trunk<19:32:01.744> native<19:32:02.400> VLAN<19:32:03.056> five 19:32:04.910 --> 19:32:04.920 align:start position:0% trunk native VLAN five 19:32:04.920 --> 19:32:06.710 align:start position:0% trunk native VLAN five you'll<19:32:05.576> probably<19:32:05.696> use<19:32:05.872> something<19:32:06.056> higher 19:32:06.710 --> 19:32:06.720 align:start position:0% you'll probably use something higher 19:32:06.720 --> 19:32:08.750 align:start position:0% you'll probably use something higher like<19:32:07.016> I<19:32:07.144> said<19:32:07.256> like<19:32:07.552> two<19:32:07.800> two<19:32:08.040> but<19:32:08.512> it's<19:32:08.640> just 19:32:08.750 --> 19:32:08.760 align:start position:0% like I said like two two but it's just 19:32:08.760 --> 19:32:11.270 align:start position:0% like I said like two two but it's just to<19:32:08.872> illustrate<19:32:09.240> the<19:32:09.424> point<19:32:09.600> so<19:32:10.320> this<19:32:11.104> traffic 19:32:11.270 --> 19:32:11.280 align:start position:0% to illustrate the point so this traffic 19:32:11.280 --> 19:32:14.750 align:start position:0% to illustrate the point so this traffic that<19:32:11.576> passes<19:32:12.000> over<19:32:12.240> uh<19:32:13.192> the<19:32:13.320> native<19:32:13.504> VLAN<19:32:14.040> will 19:32:14.750 --> 19:32:14.760 align:start position:0% that passes over uh the native VLAN will 19:32:14.760 --> 19:32:18.110 align:start position:0% that passes over uh the native VLAN will use<19:32:15.000> VLAN<19:32:15.656> F5<19:32:16.192> it<19:32:16.496> won't<19:32:16.680> use<19:32:16.856> VLAN<19:32:17.336> one<19:32:17.576> and 19:32:18.110 --> 19:32:18.120 align:start position:0% use VLAN F5 it won't use VLAN one and 19:32:18.120 --> 19:32:19.430 align:start position:0% use VLAN F5 it won't use VLAN one and you've<19:32:18.296> got<19:32:18.424> to<19:32:18.536> be<19:32:18.600> careful<19:32:18.896> because<19:32:19.144> you 19:32:19.430 --> 19:32:19.440 align:start position:0% you've got to be careful because you 19:32:19.440 --> 19:32:22.542 align:start position:0% you've got to be careful because you can't<19:32:19.552> delete<19:32:20.056> a<19:32:21.056> VLAN<19:32:21.480> one<19:32:21.656> it's<19:32:21.960> there<19:32:22.256> all 19:32:22.542 --> 19:32:22.552 align:start position:0% can't delete a VLAN one it's there all 19:32:22.552 --> 19:32:24.646 align:start position:0% can't delete a VLAN one it's there all the<19:32:22.744> time<19:32:22.976> you<19:32:23.576> just<19:32:23.696> don't<19:32:23.872> have<19:32:24.120> to<19:32:24.296> use<19:32:24.480> it 19:32:24.646 --> 19:32:24.656 align:start position:0% the time you just don't have to use it 19:32:24.656 --> 19:32:26.990 align:start position:0% the time you just don't have to use it to<19:32:24.832> pass<19:32:24.960> any<19:32:25.192> traffic<19:32:25.504> and<19:32:26.280> now<19:32:26.464> you<19:32:26.696> can<19:32:26.824> see 19:32:26.990 --> 19:32:27.000 align:start position:0% to pass any traffic and now you can see 19:32:27.000 --> 19:32:29.270 align:start position:0% to pass any traffic and now you can see it's<19:32:27.240> changed<19:32:27.720> from<19:32:27.896> VLAN<19:32:28.376> one<19:32:28.552> as<19:32:28.800> a<19:32:28.976> default 19:32:29.270 --> 19:32:29.280 align:start position:0% it's changed from VLAN one as a default 19:32:29.280 --> 19:32:36.182 align:start position:0% it's changed from VLAN one as a default to<19:32:29.936> VLAN<19:32:30.480> 5. 19:32:36.182 --> 19:32:36.192 align:start position:0% 19:32:36.192 --> 19:32:39.046 align:start position:0% I've<19:32:37.192> already<19:32:37.376> mentioned<19:32:37.800> all<19:32:37.920> this<19:32:38.104> sorry<19:32:38.280> so 19:32:39.046 --> 19:32:39.056 align:start position:0% I've already mentioned all this sorry so 19:32:39.056 --> 19:32:42.430 align:start position:0% I've already mentioned all this sorry so another<19:32:39.536> thing<19:32:39.896> mentioned<19:32:40.440> is<19:32:40.936> bpdu<19:32:41.936> guard 19:32:42.430 --> 19:32:42.440 align:start position:0% another thing mentioned is bpdu guard 19:32:42.440 --> 19:32:45.350 align:start position:0% another thing mentioned is bpdu guard this<19:32:43.440> is<19:32:43.552> arrived<19:32:43.920> in<19:32:44.040> the<19:32:44.160> syllabus 19:32:45.350 --> 19:32:45.360 align:start position:0% this is arrived in the syllabus 19:32:45.360 --> 19:32:48.774 align:start position:0% this is arrived in the syllabus a<19:32:45.896> bpdu<19:32:46.496> guard<19:32:46.800> it's<19:32:47.104> on<19:32:47.280> an<19:32:47.464> interface<19:32:48.000> the 19:32:48.774 --> 19:32:48.784 align:start position:0% a bpdu guard it's on an interface the 19:32:48.784 --> 19:32:51.526 align:start position:0% a bpdu guard it's on an interface the port<19:32:49.016> is<19:32:49.256> every<19:32:49.440> disabled<19:32:49.920> when<19:32:50.104> a<19:32:50.400> bpdu<19:32:51.360> is 19:32:51.526 --> 19:32:51.536 align:start position:0% port is every disabled when a bpdu is 19:32:51.536 --> 19:32:54.470 align:start position:0% port is every disabled when a bpdu is received<19:32:52.496> so<19:32:52.856> Bridge<19:32:53.040> protocol<19:32:53.512> data<19:32:54.000> unit<19:32:54.176> we 19:32:54.470 --> 19:32:54.480 align:start position:0% received so Bridge protocol data unit we 19:32:54.480 --> 19:32:57.166 align:start position:0% received so Bridge protocol data unit we talked<19:32:54.784> about<19:32:54.832> earlier<19:32:55.376> this<19:32:56.280> is<19:32:56.464> uh<19:32:56.696> used<19:32:56.936> for 19:32:57.166 --> 19:32:57.176 align:start position:0% talked about earlier this is uh used for 19:32:57.176 --> 19:32:59.566 align:start position:0% talked about earlier this is uh used for spanning<19:32:57.720> tree<19:32:57.896> traffic 19:32:59.566 --> 19:32:59.576 align:start position:0% spanning tree traffic 19:32:59.576 --> 19:33:01.246 align:start position:0% spanning tree traffic and<19:32:59.936> it<19:33:00.056> can<19:33:00.176> actually<19:33:00.296> change<19:33:00.600> your<19:33:00.832> layer<19:33:01.144> 2 19:33:01.246 --> 19:33:01.256 align:start position:0% and it can actually change your layer 2 19:33:01.256 --> 19:33:04.670 align:start position:0% and it can actually change your layer 2 topologies<19:33:01.976> for<19:33:02.336> example<19:33:02.696> let's<19:33:03.656> say<19:33:03.832> this 19:33:04.670 --> 19:33:04.680 align:start position:0% topologies for example let's say this 19:33:04.680 --> 19:33:06.822 align:start position:0% topologies for example let's say this switch<19:33:04.976> is<19:33:05.280> the<19:33:05.512> root<19:33:05.696> you've<19:33:05.936> got<19:33:06.056> a<19:33:06.176> high<19:33:06.360> a 19:33:06.822 --> 19:33:06.832 align:start position:0% switch is the root you've got a high a 19:33:06.832 --> 19:33:09.166 align:start position:0% switch is the root you've got a high a high-powered<19:33:07.616> switch<19:33:07.800> here<19:33:08.160> and<19:33:08.936> it<19:33:09.056> would 19:33:09.166 --> 19:33:09.176 align:start position:0% high-powered switch here and it would 19:33:09.176 --> 19:33:12.366 align:start position:0% high-powered switch here and it would normally<19:33:09.480> be<19:33:09.832> a<19:33:10.320> multi-layer<19:33:11.160> switch<19:33:11.464> here 19:33:12.366 --> 19:33:12.376 align:start position:0% normally be a multi-layer switch here 19:33:12.376 --> 19:33:15.710 align:start position:0% normally be a multi-layer switch here and<19:33:13.376> all<19:33:13.616> of<19:33:13.800> your<19:33:14.104> traffic<19:33:14.760> is<19:33:15.056> pointing<19:33:15.480> to 19:33:15.710 --> 19:33:15.720 align:start position:0% and all of your traffic is pointing to 19:33:15.720 --> 19:33:18.526 align:start position:0% and all of your traffic is pointing to this<19:33:15.960> device<19:33:16.192> but<19:33:17.040> what<19:33:17.216> will<19:33:17.400> happen<19:33:17.576> is<19:33:17.936> this 19:33:18.526 --> 19:33:18.536 align:start position:0% this device but what will happen is this 19:33:18.536 --> 19:33:21.046 align:start position:0% this device but what will happen is this device<19:33:18.720> will<19:33:19.080> announce<19:33:19.440> a<19:33:19.920> number 19:33:21.046 --> 19:33:21.056 align:start position:0% device will announce a number 19:33:21.056 --> 19:33:24.046 align:start position:0% device will announce a number to<19:33:21.600> say<19:33:21.784> I<19:33:21.960> am<19:33:22.144> the<19:33:22.320> boss<19:33:22.496> and<19:33:23.336> say<19:33:23.512> for<19:33:23.760> example 19:33:24.046 --> 19:33:24.056 align:start position:0% to say I am the boss and say for example 19:33:24.056 --> 19:33:27.710 align:start position:0% to say I am the boss and say for example this<19:33:24.784> is<19:33:25.144> number<19:33:25.376> 99.<19:33:26.760> this<19:33:27.296> is<19:33:27.424> the<19:33:27.600> number 19:33:27.710 --> 19:33:27.720 align:start position:0% this is number 99. this is the number 19:33:27.720 --> 19:33:29.502 align:start position:0% this is number 99. this is the number that<19:33:28.080> determines<19:33:28.496> the<19:33:28.744> root<19:33:29.104> of<19:33:29.216> all<19:33:29.400> your 19:33:29.502 --> 19:33:29.512 align:start position:0% that determines the root of all your 19:33:29.512 --> 19:33:31.670 align:start position:0% that determines the root of all your spanning<19:33:30.000> tree<19:33:30.120> traffic<19:33:30.424> well<19:33:31.256> what<19:33:31.504> happens 19:33:31.670 --> 19:33:31.680 align:start position:0% spanning tree traffic well what happens 19:33:31.680 --> 19:33:34.006 align:start position:0% spanning tree traffic well what happens is<19:33:31.976> if<19:33:32.216> this<19:33:32.512> device<19:33:32.696> uh<19:33:33.480> connects<19:33:33.832> to<19:33:33.896> the 19:33:34.006 --> 19:33:34.016 align:start position:0% is if this device uh connects to the 19:33:34.016 --> 19:33:35.502 align:start position:0% is if this device uh connects to the network<19:33:34.144> say<19:33:34.496> you've<19:33:34.800> bought<19:33:34.976> you've<19:33:35.336> found 19:33:35.502 --> 19:33:35.512 align:start position:0% network say you've bought you've found 19:33:35.512 --> 19:33:38.390 align:start position:0% network say you've bought you've found it<19:33:35.696> on<19:33:35.872> a<19:33:36.000> Shelf<19:33:36.176> at<19:33:36.536> work<19:33:36.784> and<19:33:37.744> for<19:33:37.976> some<19:33:38.160> crazy 19:33:38.390 --> 19:33:38.400 align:start position:0% it on a Shelf at work and for some crazy 19:33:38.400 --> 19:33:40.846 align:start position:0% it on a Shelf at work and for some crazy reason<19:33:38.760> all<19:33:39.056> you've<19:33:39.240> done<19:33:39.424> is<19:33:39.536> plug<19:33:39.784> it<19:33:39.960> in<19:33:40.144> and 19:33:40.846 --> 19:33:40.856 align:start position:0% reason all you've done is plug it in and 19:33:40.856 --> 19:33:42.230 align:start position:0% reason all you've done is plug it in and this<19:33:41.040> has<19:33:41.104> happened<19:33:41.336> by<19:33:41.576> the<19:33:41.696> way<19:33:41.760> I've<19:33:42.000> seen 19:33:42.230 --> 19:33:42.240 align:start position:0% this has happened by the way I've seen 19:33:42.240 --> 19:33:44.686 align:start position:0% this has happened by the way I've seen it<19:33:42.360> happen<19:33:42.680> well<19:33:43.680> this<19:33:44.160> device<19:33:44.336> could 19:33:44.686 --> 19:33:44.696 align:start position:0% it happen well this device could 19:33:44.696 --> 19:33:47.030 align:start position:0% it happen well this device could actually<19:33:44.936> be<19:33:45.424> configured<19:33:45.896> with<19:33:46.320> the<19:33:46.920> number 19:33:47.030 --> 19:33:47.040 align:start position:0% actually be configured with the number 19:33:47.040 --> 19:33:48.470 align:start position:0% actually be configured with the number 100 19:33:48.470 --> 19:33:48.480 align:start position:0% 100 19:33:48.480 --> 19:33:51.230 align:start position:0% 100 in<19:33:49.080> terms<19:33:49.376> of<19:33:49.856> um<19:33:49.856> spanning<19:33:50.400> tree<19:33:50.576> and<19:33:51.056> what 19:33:51.230 --> 19:33:51.240 align:start position:0% in terms of um spanning tree and what 19:33:51.240 --> 19:33:53.390 align:start position:0% in terms of um spanning tree and what could<19:33:51.424> happen<19:33:51.536> is<19:33:51.784> then<19:33:52.080> or<19:33:52.552> this<19:33:52.856> could<19:33:52.976> be<19:33:53.160> a 19:33:53.390 --> 19:33:53.400 align:start position:0% could happen is then or this could be a 19:33:53.400 --> 19:33:56.030 align:start position:0% could happen is then or this could be a really<19:33:53.576> low<19:33:53.872> switch<19:33:54.176> is<19:33:54.536> worth<19:33:54.784> about<19:33:55.080> say<19:33:55.800> a 19:33:56.030 --> 19:33:56.040 align:start position:0% really low switch is worth about say a 19:33:56.040 --> 19:33:57.950 align:start position:0% really low switch is worth about say a hundred<19:33:56.280> dollars<19:33:56.640> and<19:33:57.056> it's<19:33:57.176> just<19:33:57.360> got<19:33:57.480> a<19:33:57.656> tiny 19:33:57.950 --> 19:33:57.960 align:start position:0% hundred dollars and it's just got a tiny 19:33:57.960 --> 19:34:00.790 align:start position:0% hundred dollars and it's just got a tiny amount<19:33:58.192> of<19:33:58.320> process<19:33:58.616> and<19:33:58.856> power<19:33:59.120> all<19:34:00.120> of<19:34:00.360> your 19:34:00.790 --> 19:34:00.800 align:start position:0% amount of process and power all of your 19:34:00.800 --> 19:34:03.110 align:start position:0% amount of process and power all of your spanning<19:34:01.800> tree<19:34:01.920> traffic<19:34:02.216> all<19:34:02.640> of<19:34:02.760> a<19:34:02.872> sudden 19:34:03.110 --> 19:34:03.120 align:start position:0% spanning tree traffic all of a sudden 19:34:03.120 --> 19:34:06.166 align:start position:0% spanning tree traffic all of a sudden will<19:34:03.832> be<19:34:04.016> converging<19:34:04.744> onto<19:34:05.512> this<19:34:05.760> tiny<19:34:06.056> little 19:34:06.166 --> 19:34:06.176 align:start position:0% will be converging onto this tiny little 19:34:06.176 --> 19:34:08.630 align:start position:0% will be converging onto this tiny little switch<19:34:06.536> the<19:34:07.320> CPU<19:34:07.800> will<19:34:08.040> go<19:34:08.216> from<19:34:08.400> almost 19:34:08.630 --> 19:34:08.640 align:start position:0% switch the CPU will go from almost 19:34:08.640 --> 19:34:11.094 align:start position:0% switch the CPU will go from almost nothing<19:34:09.120> through<19:34:09.536> the<19:34:09.784> roof<19:34:10.080> it'll<19:34:10.976> probably 19:34:11.094 --> 19:34:11.104 align:start position:0% nothing through the roof it'll probably 19:34:11.104 --> 19:34:12.822 align:start position:0% nothing through the roof it'll probably crash<19:34:11.512> bring<19:34:11.760> you<19:34:11.936> down<19:34:12.120> your<19:34:12.296> entire<19:34:12.600> local 19:34:12.822 --> 19:34:12.832 align:start position:0% crash bring you down your entire local 19:34:12.832 --> 19:34:14.926 align:start position:0% crash bring you down your entire local area<19:34:13.144> network<19:34:13.504> and<19:34:14.216> at<19:34:14.400> that<19:34:14.512> point<19:34:14.696> you'll 19:34:14.926 --> 19:34:14.936 align:start position:0% area network and at that point you'll 19:34:14.936 --> 19:34:17.862 align:start position:0% area network and at that point you'll probably<19:34:15.056> be<19:34:15.176> out<19:34:15.360> of<19:34:15.480> a<19:34:15.600> job<19:34:15.720> to<19:34:15.896> be<19:34:16.080> honest 19:34:17.862 --> 19:34:17.872 align:start position:0% probably be out of a job to be honest 19:34:17.872 --> 19:34:20.566 align:start position:0% probably be out of a job to be honest so<19:34:18.536> what<19:34:18.720> happens<19:34:18.896> is<19:34:19.144> with<19:34:19.376> bpdu<19:34:20.104> guard<19:34:20.280> you 19:34:20.566 --> 19:34:20.576 align:start position:0% so what happens is with bpdu guard you 19:34:20.576 --> 19:34:22.542 align:start position:0% so what happens is with bpdu guard you configure<19:34:21.000> it<19:34:21.176> on<19:34:21.360> this<19:34:21.536> interface<19:34:21.960> here<19:34:22.320> for 19:34:22.542 --> 19:34:22.552 align:start position:0% configure it on this interface here for 19:34:22.552 --> 19:34:26.502 align:start position:0% configure it on this interface here for example<19:34:22.856> fast<19:34:23.336> ethernet<19:34:23.824> and<19:34:24.720> 10<19:34:25.080> and<19:34:25.744> if<19:34:25.920> a<19:34:26.104> BP 19:34:26.502 --> 19:34:26.512 align:start position:0% example fast ethernet and 10 and if a BP 19:34:26.512 --> 19:34:30.774 align:start position:0% example fast ethernet and 10 and if a BP do<19:34:27.120> you<19:34:27.616> frame<19:34:28.616> is<19:34:29.216> seen<19:34:29.696> coming<19:34:30.000> in<19:34:30.240> onto<19:34:30.600> this 19:34:30.774 --> 19:34:30.784 align:start position:0% do you frame is seen coming in onto this 19:34:30.784 --> 19:34:32.814 align:start position:0% do you frame is seen coming in onto this particular<19:34:31.080> interface<19:34:31.616> it<19:34:32.216> will<19:34:32.400> error 19:34:32.814 --> 19:34:32.824 align:start position:0% particular interface it will error 19:34:32.824 --> 19:34:33.822 align:start position:0% particular interface it will error disable 19:34:33.822 --> 19:34:33.832 align:start position:0% disable 19:34:33.832 --> 19:34:35.990 align:start position:0% disable um<19:34:33.896> it<19:34:34.192> will<19:34:34.256> error<19:34:34.616> disable<19:34:34.920> it<19:34:35.160> and<19:34:35.696> it<19:34:35.872> won't 19:34:35.990 --> 19:34:36.000 align:start position:0% um it will error disable it and it won't 19:34:36.000 --> 19:34:37.734 align:start position:0% um it will error disable it and it won't pass<19:34:36.240> traffic<19:34:36.536> until<19:34:36.896> you<19:34:37.320> the<19:34:37.616> network 19:34:37.734 --> 19:34:37.744 align:start position:0% pass traffic until you the network 19:34:37.744 --> 19:34:40.430 align:start position:0% pass traffic until you the network administrator 19:34:40.430 --> 19:34:40.440 align:start position:0% administrator 19:34:40.440 --> 19:34:44.206 align:start position:0% administrator um<19:34:40.552> what<19:34:41.336> come<19:34:41.696> comes<19:34:42.360> shuts<19:34:43.192> it<19:34:43.320> manually<19:34:43.920> and 19:34:44.206 --> 19:34:44.216 align:start position:0% um what come comes shuts it manually and 19:34:44.216 --> 19:34:46.670 align:start position:0% um what come comes shuts it manually and then<19:34:44.400> manually<19:34:44.936> no<19:34:45.600> shits<19:34:46.016> the<19:34:46.144> interface<19:34:46.496> so 19:34:46.670 --> 19:34:46.680 align:start position:0% then manually no shits the interface so 19:34:46.680 --> 19:34:48.590 align:start position:0% then manually no shits the interface so you<19:34:46.800> have<19:34:46.920> to<19:34:46.976> re-enable<19:34:47.464> it 19:34:48.590 --> 19:34:48.600 align:start position:0% you have to re-enable it 19:34:48.600 --> 19:34:51.526 align:start position:0% you have to re-enable it uh<19:34:49.376> root<19:34:49.800> guard 19:34:51.526 --> 19:34:51.536 align:start position:0% uh root guard 19:34:51.536 --> 19:34:54.230 align:start position:0% uh root guard so<19:34:52.080> I<19:34:52.192> mentioned<19:34:52.680> uh<19:34:52.976> if<19:34:53.400> this<19:34:53.696> is<19:34:53.760> a<19:34:53.936> topology 19:34:54.230 --> 19:34:54.240 align:start position:0% so I mentioned uh if this is a topology 19:34:54.240 --> 19:34:56.926 align:start position:0% so I mentioned uh if this is a topology where<19:34:54.784> it's<19:34:55.192> actually<19:34:55.376> I<19:34:55.680> think<19:34:55.800> from<19:34:56.040> my<19:34:56.280> CCNA 19:34:56.926 --> 19:34:56.936 align:start position:0% where it's actually I think from my CCNA 19:34:56.936 --> 19:34:59.150 align:start position:0% where it's actually I think from my CCNA book<19:34:57.176> where<19:34:57.960> I'm<19:34:58.144> telling<19:34:58.496> you<19:34:58.552> on<19:34:58.920> what 19:34:59.150 --> 19:34:59.160 align:start position:0% book where I'm telling you on what 19:34:59.160 --> 19:35:01.310 align:start position:0% book where I'm telling you on what interfaces<19:34:59.760> depending<19:35:00.424> on<19:35:00.480> the<19:35:00.656> topology<19:35:01.016> you 19:35:01.310 --> 19:35:01.320 align:start position:0% interfaces depending on the topology you 19:35:01.320 --> 19:35:04.134 align:start position:0% interfaces depending on the topology you would<19:35:01.440> add<19:35:01.616> bpdu<19:35:02.280> guard<19:35:02.656> root<19:35:03.656> guard<19:35:03.784> you 19:35:04.134 --> 19:35:04.144 align:start position:0% would add bpdu guard root guard you 19:35:04.144 --> 19:35:06.646 align:start position:0% would add bpdu guard root guard you would<19:35:04.320> add<19:35:04.496> down<19:35:04.920> here 19:35:06.646 --> 19:35:06.656 align:start position:0% would add down here 19:35:06.656 --> 19:35:09.590 align:start position:0% would add down here on<19:35:07.144> these<19:35:07.256> level<19:35:07.440> of<19:35:07.680> interfaces<19:35:08.280> so<19:35:08.760> these 19:35:09.590 --> 19:35:09.600 align:start position:0% on these level of interfaces so these 19:35:09.600 --> 19:35:12.526 align:start position:0% on these level of interfaces so these are<19:35:09.656> your<19:35:09.896> layer<19:35:10.192> 3<19:35:10.376> switches<19:35:11.000> and<19:35:12.000> these<19:35:12.480> are 19:35:12.526 --> 19:35:12.536 align:start position:0% are your layer 3 switches and these are 19:35:12.536 --> 19:35:14.566 align:start position:0% are your layer 3 switches and these are your<19:35:12.720> these<19:35:13.256> images<19:35:13.376> here<19:35:13.744> represent<19:35:14.160> Layer 19:35:14.566 --> 19:35:14.576 align:start position:0% your these images here represent Layer 19:35:14.576 --> 19:35:15.590 align:start position:0% your these images here represent Layer Two 19:35:15.590 --> 19:35:15.600 align:start position:0% Two 19:35:15.600 --> 19:35:17.990 align:start position:0% Two uh<19:35:16.080> root<19:35:16.376> guard<19:35:16.496> is<19:35:16.744> configured<19:35:17.160> per<19:35:17.400> Port<19:35:17.696> so 19:35:17.990 --> 19:35:18.000 align:start position:0% uh root guard is configured per Port so 19:35:18.000 --> 19:35:19.670 align:start position:0% uh root guard is configured per Port so you<19:35:18.240> wouldn't<19:35:18.424> configure<19:35:18.896> it<19:35:19.080> on<19:35:19.320> a<19:35:19.504> device 19:35:19.670 --> 19:35:19.680 align:start position:0% you wouldn't configure it on a device 19:35:19.680 --> 19:35:21.774 align:start position:0% you wouldn't configure it on a device and<19:35:20.160> expect<19:35:20.336> the<19:35:20.824> configuration<19:35:21.296> to<19:35:21.600> be 19:35:21.774 --> 19:35:21.784 align:start position:0% and expect the configuration to be 19:35:21.784 --> 19:35:23.686 align:start position:0% and expect the configuration to be passed<19:35:22.144> out<19:35:22.192> through<19:35:22.440> your<19:35:22.616> network 19:35:23.686 --> 19:35:23.696 align:start position:0% passed out through your network 19:35:23.696 --> 19:35:27.414 align:start position:0% passed out through your network and<19:35:24.480> like<19:35:25.192> um<19:35:25.192> other<19:35:25.680> configurations<19:35:26.424> root 19:35:27.414 --> 19:35:27.424 align:start position:0% and like um other configurations root 19:35:27.424 --> 19:35:29.150 align:start position:0% and like um other configurations root ports<19:35:27.656> are<19:35:27.832> the<19:35:27.960> closest<19:35:28.144> to<19:35:28.496> the<19:35:28.680> spanning 19:35:29.150 --> 19:35:29.160 align:start position:0% ports are the closest to the spanning 19:35:29.160 --> 19:35:32.326 align:start position:0% ports are the closest to the spanning tree<19:35:29.336> master<19:35:29.960> these<19:35:30.960> ports<19:35:31.376> are<19:35:31.800> furthest 19:35:32.326 --> 19:35:32.336 align:start position:0% tree master these ports are furthest 19:35:32.336 --> 19:35:35.150 align:start position:0% tree master these ports are furthest away<19:35:32.576> if<19:35:33.176> this<19:35:33.360> is<19:35:33.480> the<19:35:33.656> master<19:35:33.832> here<19:35:34.256> in<19:35:34.920> my 19:35:35.150 --> 19:35:35.160 align:start position:0% away if this is the master here in my 19:35:35.160 --> 19:35:36.670 align:start position:0% away if this is the master here in my topology 19:35:36.670 --> 19:35:36.680 align:start position:0% topology 19:35:36.680 --> 19:35:39.526 align:start position:0% topology these<19:35:37.680> are<19:35:38.104> the<19:35:38.216> ports<19:35:38.640> that<19:35:38.824> would<19:35:39.120> normally 19:35:39.526 --> 19:35:39.536 align:start position:0% these are the ports that would normally 19:35:39.536 --> 19:35:41.862 align:start position:0% these are the ports that would normally you<19:35:40.016> would<19:35:40.256> want<19:35:40.496> to<19:35:40.976> be<19:35:41.104> root<19:35:41.464> and<19:35:41.640> it's 19:35:41.862 --> 19:35:41.872 align:start position:0% you would want to be root and it's 19:35:41.872 --> 19:35:45.046 align:start position:0% you would want to be root and it's basically<19:35:42.240> saying<19:35:42.720> the<19:35:43.440> root<19:35:43.680> equals 19:35:45.046 --> 19:35:45.056 align:start position:0% basically saying the root equals 19:35:45.056 --> 19:35:46.486 align:start position:0% basically saying the root equals um<19:35:45.120> best 19:35:46.486 --> 19:35:46.496 align:start position:0% um best 19:35:46.496 --> 19:35:50.686 align:start position:0% um best path<19:35:47.160> to<19:35:47.824> take<19:35:48.056> to<19:35:48.536> the<19:35:48.720> master<19:35:49.216> this<19:35:50.216> is<19:35:50.464> not 19:35:50.686 --> 19:35:50.696 align:start position:0% path to take to the master this is not 19:35:50.696 --> 19:35:53.206 align:start position:0% path to take to the master this is not the<19:35:50.936> best<19:35:51.056> path<19:35:51.360> to<19:35:51.832> take<19:35:52.016> to<19:35:52.320> the<19:35:52.496> master<19:35:52.680> this 19:35:53.206 --> 19:35:53.216 align:start position:0% the best path to take to the master this 19:35:53.216 --> 19:35:55.070 align:start position:0% the best path to take to the master this would<19:35:53.400> cause<19:35:53.576> you<19:35:53.760> a<19:35:53.936> lot<19:35:54.000> of<19:35:54.120> problems<19:35:54.480> this 19:35:55.070 --> 19:35:55.080 align:start position:0% would cause you a lot of problems this 19:35:55.080 --> 19:35:57.350 align:start position:0% would cause you a lot of problems this is<19:35:55.144> why<19:35:55.320> you<19:35:55.504> would<19:35:55.552> enable<19:35:55.856> root<19:35:56.336> guard<19:35:56.464> on 19:35:57.350 --> 19:35:57.360 align:start position:0% is why you would enable root guard on 19:35:57.360 --> 19:35:59.390 align:start position:0% is why you would enable root guard on these<19:35:57.536> ports<19:35:57.896> here 19:35:59.390 --> 19:35:59.400 align:start position:0% these ports here 19:35:59.400 --> 19:36:01.790 align:start position:0% these ports here so<19:36:00.056> Modesto<19:36:00.720> for<19:36:00.832> incoming<19:36:01.144> Bridge<19:36:01.376> protocol 19:36:01.790 --> 19:36:01.800 align:start position:0% so Modesto for incoming Bridge protocol 19:36:01.800 --> 19:36:03.646 align:start position:0% so Modesto for incoming Bridge protocol data<19:36:02.400> units 19:36:03.646 --> 19:36:03.656 align:start position:0% data units 19:36:03.656 --> 19:36:05.630 align:start position:0% data units and<19:36:04.192> it<19:36:04.320> prevents<19:36:04.616> support<19:36:04.800> from<19:36:05.104> becoming<19:36:05.464> a 19:36:05.630 --> 19:36:05.640 align:start position:0% and it prevents support from becoming a 19:36:05.640 --> 19:36:08.094 align:start position:0% and it prevents support from becoming a root<19:36:05.936> Port<19:36:06.120> how<19:36:07.080> it<19:36:07.256> does<19:36:07.376> it<19:36:07.552> yeah<19:36:07.744> you<19:36:07.976> can 19:36:08.094 --> 19:36:08.104 align:start position:0% root Port how it does it yeah you can 19:36:08.104 --> 19:36:10.846 align:start position:0% root Port how it does it yeah you can learn<19:36:08.280> a<19:36:08.640> bit<19:36:08.760> more<19:36:08.872> when<19:36:09.056> you<19:36:09.240> do<19:36:09.360> Cisco<19:36:09.856> CCNA 19:36:10.846 --> 19:36:10.856 align:start position:0% learn a bit more when you do Cisco CCNA 19:36:10.856 --> 19:36:12.910 align:start position:0% learn a bit more when you do Cisco CCNA and<19:36:10.976> ccmp<19:36:11.696> Etc 19:36:12.910 --> 19:36:12.920 align:start position:0% and ccmp Etc 19:36:12.920 --> 19:36:18.414 align:start position:0% and ccmp Etc DHCP<19:36:13.920> snooping<19:36:15.144> this<19:36:16.144> is<19:36:16.320> the<19:36:16.744> uh<19:36:17.464> legitimate 19:36:18.414 --> 19:36:18.424 align:start position:0% DHCP snooping this is the uh legitimate 19:36:18.424 --> 19:36:19.430 align:start position:0% DHCP snooping this is the uh legitimate one 19:36:19.430 --> 19:36:19.440 align:start position:0% one 19:36:19.440 --> 19:36:22.246 align:start position:0% one here<19:36:19.976> this<19:36:20.640> is<19:36:20.760> the<19:36:21.056> Rogue<19:36:21.480> that<19:36:21.656> somebody's 19:36:22.246 --> 19:36:22.256 align:start position:0% here this is the Rogue that somebody's 19:36:22.256 --> 19:36:24.286 align:start position:0% here this is the Rogue that somebody's either<19:36:22.856> somebody's<19:36:23.464> attached<19:36:23.872> it<19:36:24.000> to<19:36:24.120> your 19:36:24.286 --> 19:36:24.296 align:start position:0% either somebody's attached it to your 19:36:24.296 --> 19:36:27.910 align:start position:0% either somebody's attached it to your network<19:36:24.480> or<19:36:25.016> they've<19:36:25.376> downloaded<19:36:25.800> some<19:36:26.160> code 19:36:27.910 --> 19:36:27.920 align:start position:0% network or they've downloaded some code 19:36:27.920 --> 19:36:31.430 align:start position:0% network or they've downloaded some code accidentally<19:36:28.920> onto<19:36:29.696> their<19:36:30.000> device<19:36:30.320> and<19:36:31.320> it's 19:36:31.430 --> 19:36:31.440 align:start position:0% accidentally onto their device and it's 19:36:31.440 --> 19:36:34.070 align:start position:0% accidentally onto their device and it's trying<19:36:31.680> to<19:36:31.800> take<19:36:31.976> over<19:36:32.216> as<19:36:32.464> a<19:36:32.696> DHCP<19:36:33.360> server<19:36:33.832> for 19:36:34.070 --> 19:36:34.080 align:start position:0% trying to take over as a DHCP server for 19:36:34.080 --> 19:36:36.526 align:start position:0% trying to take over as a DHCP server for this<19:36:34.400> segment<19:36:35.400> of<19:36:35.576> your<19:36:35.760> network<19:36:35.936> which<19:36:36.360> you 19:36:36.526 --> 19:36:36.536 align:start position:0% this segment of your network which you 19:36:36.536 --> 19:36:38.206 align:start position:0% this segment of your network which you don't<19:36:36.656> want<19:36:36.832> to<19:36:36.960> happen 19:36:38.206 --> 19:36:38.216 align:start position:0% don't want to happen 19:36:38.216 --> 19:36:41.390 align:start position:0% don't want to happen it<19:36:38.760> forces<19:36:39.240> the<19:36:39.480> switch<19:36:39.720> here<19:36:40.192> to<19:36:40.552> examine<19:36:41.040> and 19:36:41.390 --> 19:36:41.400 align:start position:0% it forces the switch here to examine and 19:36:41.400 --> 19:36:44.990 align:start position:0% it forces the switch here to examine and filter<19:36:41.640> inappropriate<19:36:42.480> DHCP<19:36:43.320> messages<19:36:43.744> so<19:36:44.696> if 19:36:44.990 --> 19:36:45.000 align:start position:0% filter inappropriate DHCP messages so if 19:36:45.000 --> 19:36:47.270 align:start position:0% filter inappropriate DHCP messages so if this<19:36:45.240> port<19:36:45.480> if<19:36:46.144> this<19:36:46.320> switch<19:36:46.496> detects<19:36:47.160> it 19:36:47.270 --> 19:36:47.280 align:start position:0% this port if this switch detects it 19:36:47.280 --> 19:36:49.606 align:start position:0% this port if this switch detects it coming<19:36:47.464> on<19:36:47.760> this<19:36:47.936> port<19:36:48.176> you've<19:36:49.080> configured 19:36:49.606 --> 19:36:49.616 align:start position:0% coming on this port you've configured 19:36:49.616 --> 19:36:55.366 align:start position:0% coming on this port you've configured this<19:36:49.920> port<19:36:50.104> here<19:36:50.464> as<19:36:51.000> interested 19:36:55.366 --> 19:36:55.376 align:start position:0% 19:36:55.376 --> 19:36:57.110 align:start position:0% and<19:36:55.744> you<19:36:55.856> know<19:36:56.040> which<19:36:56.280> ports<19:36:56.696> you<19:36:56.760> trust 19:36:57.110 --> 19:36:57.120 align:start position:0% and you know which ports you trust 19:36:57.120 --> 19:36:58.454 align:start position:0% and you know which ports you trust because<19:36:57.240> you're<19:36:57.424> the<19:36:57.600> network<19:36:57.720> administrator 19:36:58.454 --> 19:36:58.464 align:start position:0% because you're the network administrator 19:36:58.464 --> 19:37:03.590 align:start position:0% because you're the network administrator this<19:36:59.464> port 19:37:03.590 --> 19:37:03.600 align:start position:0% 19:37:03.600 --> 19:37:06.230 align:start position:0% so<19:37:04.192> it<19:37:04.320> comes<19:37:04.680> in<19:37:04.800> and<19:37:05.104> that<19:37:05.336> is<19:37:05.512> permitted 19:37:06.230 --> 19:37:06.240 align:start position:0% so it comes in and that is permitted 19:37:06.240 --> 19:37:09.710 align:start position:0% so it comes in and that is permitted through<19:37:06.920> untrusted<19:37:07.920> it<19:37:08.576> comes<19:37:08.872> in<19:37:09.056> and 19:37:09.710 --> 19:37:09.720 align:start position:0% through untrusted it comes in and 19:37:09.720 --> 19:37:12.166 align:start position:0% through untrusted it comes in and blocked<19:37:10.496> and<19:37:11.160> then<19:37:11.280> you<19:37:11.464> would<19:37:11.576> normally<19:37:11.872> get 19:37:12.166 --> 19:37:12.176 align:start position:0% blocked and then you would normally get 19:37:12.176 --> 19:37:14.686 align:start position:0% blocked and then you would normally get notified<19:37:12.784> as<19:37:13.504> the<19:37:13.680> administrator<19:37:14.160> that<19:37:14.512> hang 19:37:14.686 --> 19:37:14.696 align:start position:0% notified as the administrator that hang 19:37:14.696 --> 19:37:17.030 align:start position:0% notified as the administrator that hang on<19:37:14.872> something's<19:37:15.424> not<19:37:15.600> quite<19:37:15.832> right<19:37:16.080> here<19:37:16.320> with 19:37:17.030 --> 19:37:17.040 align:start position:0% on something's not quite right here with 19:37:17.040 --> 19:37:21.350 align:start position:0% on something's not quite right here with a<19:37:17.216> text<19:37:17.400> phone<19:37:17.824> call<19:37:18.120> or<19:37:18.424> other<19:37:18.784> type<19:37:19.080> of<19:37:19.192> alert 19:37:21.350 --> 19:37:21.360 align:start position:0% a text phone call or other type of alert 19:37:21.360 --> 19:37:23.926 align:start position:0% a text phone call or other type of alert uh<19:37:21.896> vlans<19:37:22.496> these<19:37:23.040> separate<19:37:23.336> your<19:37:23.512> host<19:37:23.696> into 19:37:23.926 --> 19:37:23.936 align:start position:0% uh vlans these separate your host into 19:37:23.936 --> 19:37:25.430 align:start position:0% uh vlans these separate your host into function<19:37:24.296> so<19:37:24.600> here<19:37:24.784> you've<19:37:25.016> got<19:37:25.080> the<19:37:25.256> sales 19:37:25.430 --> 19:37:25.440 align:start position:0% function so here you've got the sales 19:37:25.440 --> 19:37:29.454 align:start position:0% function so here you've got the sales team<19:37:25.856> you're<19:37:26.696> accounting<19:37:27.296> uh<19:37:28.080> Team<19:37:28.376> the<19:37:29.216> IT 19:37:29.454 --> 19:37:29.464 align:start position:0% team you're accounting uh Team the IT 19:37:29.464 --> 19:37:32.502 align:start position:0% team you're accounting uh Team the IT team<19:37:29.936> and<19:37:30.656> then<19:37:30.784> your<19:37:31.016> human<19:37:31.192> resources<19:37:31.920> and 19:37:32.502 --> 19:37:32.512 align:start position:0% team and then your human resources and 19:37:32.512 --> 19:37:34.670 align:start position:0% team and then your human resources and what<19:37:32.760> this<19:37:33.000> does<19:37:33.240> and<19:37:33.784> it<19:37:33.960> depends<19:37:34.320> on<19:37:34.440> the 19:37:34.670 --> 19:37:34.680 align:start position:0% what this does and it depends on the 19:37:34.680 --> 19:37:37.310 align:start position:0% what this does and it depends on the design<19:37:34.872> methodology<19:37:35.872> you're<19:37:36.784> following<19:37:37.144> by 19:37:37.310 --> 19:37:37.320 align:start position:0% design methodology you're following by 19:37:37.320 --> 19:37:39.110 align:start position:0% design methodology you're following by the<19:37:37.440> way<19:37:37.504> there's<19:37:37.744> a<19:37:37.920> whole<19:37:38.040> bunch<19:37:38.280> of<19:37:38.400> ways<19:37:38.824> to 19:37:39.110 --> 19:37:39.120 align:start position:0% the way there's a whole bunch of ways to 19:37:39.120 --> 19:37:41.206 align:start position:0% the way there's a whole bunch of ways to design<19:37:39.960> your<19:37:40.256> network<19:37:40.440> depending<19:37:40.976> on<19:37:41.040> which 19:37:41.206 --> 19:37:41.216 align:start position:0% design your network depending on which 19:37:41.216 --> 19:37:43.494 align:start position:0% design your network depending on which vendor<19:37:41.640> you're<19:37:41.760> speaking<19:37:42.176> to<19:37:42.360> but<19:37:43.192> we've 19:37:43.494 --> 19:37:43.504 align:start position:0% vendor you're speaking to but we've 19:37:43.504 --> 19:37:46.790 align:start position:0% vendor you're speaking to but we've separated<19:37:43.920> ours<19:37:44.464> into<19:37:44.760> functions 19:37:46.790 --> 19:37:46.800 align:start position:0% separated ours into functions 19:37:46.800 --> 19:37:49.182 align:start position:0% separated ours into functions now<19:37:47.464> if<19:37:47.824> there's<19:37:47.936> a<19:37:48.120> broadcast<19:37:48.296> say<19:37:48.656> there's<19:37:48.960> a 19:37:49.182 --> 19:37:49.192 align:start position:0% now if there's a broadcast say there's a 19:37:49.192 --> 19:37:51.774 align:start position:0% now if there's a broadcast say there's a a<19:37:49.616> fault<19:37:50.104> on<19:37:50.512> the<19:37:50.640> network<19:37:50.872> card<19:37:51.296> for<19:37:51.600> this 19:37:51.774 --> 19:37:51.784 align:start position:0% a fault on the network card for this 19:37:51.784 --> 19:37:53.454 align:start position:0% a fault on the network card for this device<19:37:52.016> here 19:37:53.454 --> 19:37:53.464 align:start position:0% device here 19:37:53.464 --> 19:37:56.502 align:start position:0% device here then<19:37:54.784> um<19:37:54.832> the<19:37:55.376> broadcast<19:37:55.552> traffic<19:37:55.976> because 19:37:56.502 --> 19:37:56.512 align:start position:0% then um the broadcast traffic because 19:37:56.512 --> 19:38:00.414 align:start position:0% then um the broadcast traffic because each<19:37:57.616> VLAN<19:37:58.616> has<19:37:58.856> its<19:37:59.216> own<19:37:59.280> network<19:37:59.696> address<19:38:00.056> so 19:38:00.414 --> 19:38:00.424 align:start position:0% each VLAN has its own network address so 19:38:00.424 --> 19:38:03.526 align:start position:0% each VLAN has its own network address so say<19:38:00.896> that's<19:38:01.144> in<19:38:01.376> 10.10 19:38:03.526 --> 19:38:03.536 align:start position:0% say that's in 10.10 19:38:03.536 --> 19:38:06.822 align:start position:0% say that's in 10.10 uh<19:38:04.144> 10.20 19:38:06.822 --> 19:38:06.832 align:start position:0% uh 10.20 19:38:06.832 --> 19:38:10.006 align:start position:0% uh 10.20 10.30 19:38:10.006 --> 19:38:10.016 align:start position:0% 19:38:10.016 --> 19:38:11.686 align:start position:0% and<19:38:10.744> uh 19:38:11.686 --> 19:38:11.696 align:start position:0% and uh 19:38:11.696 --> 19:38:14.150 align:start position:0% and uh 10.40 19:38:14.150 --> 19:38:14.160 align:start position:0% 10.40 19:38:14.160 --> 19:38:16.486 align:start position:0% 10.40 so<19:38:14.512> these<19:38:14.760> are<19:38:14.824> all<19:38:14.936> different 19:38:16.486 --> 19:38:16.496 align:start position:0% so these are all different 19:38:16.496 --> 19:38:19.430 align:start position:0% so these are all different um<19:38:16.640> subnets<19:38:17.640> and<19:38:18.360> in<19:38:18.536> order<19:38:18.784> for<19:38:19.016> these<19:38:19.256> to 19:38:19.430 --> 19:38:19.440 align:start position:0% um subnets and in order for these to 19:38:19.440 --> 19:38:21.350 align:start position:0% um subnets and in order for these to communicate<19:38:19.920> you'd<19:38:20.576> either<19:38:20.696> have<19:38:20.936> to<19:38:21.056> have<19:38:21.176> a 19:38:21.350 --> 19:38:21.360 align:start position:0% communicate you'd either have to have a 19:38:21.360 --> 19:38:24.350 align:start position:0% communicate you'd either have to have a layer<19:38:21.600> 3<19:38:21.720> module<19:38:22.192> in<19:38:22.376> this<19:38:22.552> switch<19:38:22.872> or<19:38:23.872> the 19:38:24.350 --> 19:38:24.360 align:start position:0% layer 3 module in this switch or the 19:38:24.360 --> 19:38:26.206 align:start position:0% layer 3 module in this switch or the switch<19:38:24.536> would<19:38:24.832> be<19:38:24.960> connected<19:38:25.320> to<19:38:25.552> a<19:38:25.744> router<19:38:26.040> as 19:38:26.206 --> 19:38:26.216 align:start position:0% switch would be connected to a router as 19:38:26.216 --> 19:38:28.366 align:start position:0% switch would be connected to a router as we've<19:38:26.464> spoke<19:38:26.640> about<19:38:26.760> earlier<19:38:27.240> if<19:38:27.960> there's<19:38:28.144> a 19:38:28.366 --> 19:38:28.376 align:start position:0% we've spoke about earlier if there's a 19:38:28.376 --> 19:38:30.046 align:start position:0% we've spoke about earlier if there's a broadcast<19:38:28.552> through<19:38:29.160> this<19:38:29.400> faulty<19:38:29.872> network 19:38:30.046 --> 19:38:30.056 align:start position:0% broadcast through this faulty network 19:38:30.056 --> 19:38:33.414 align:start position:0% broadcast through this faulty network card<19:38:30.424> here<19:38:30.784> it's<19:38:31.616> basically<19:38:31.976> restricted<19:38:32.760> to 19:38:33.414 --> 19:38:33.424 align:start position:0% card here it's basically restricted to 19:38:33.424 --> 19:38:36.286 align:start position:0% card here it's basically restricted to all<19:38:33.656> devices<19:38:34.080> on<19:38:35.040> this<19:38:35.216> VLAN 19:38:36.286 --> 19:38:36.296 align:start position:0% all devices on this VLAN 19:38:36.296 --> 19:38:38.206 align:start position:0% all devices on this VLAN and<19:38:36.784> then<19:38:36.896> what<19:38:37.080> would<19:38:37.192> happen<19:38:37.376> is<19:38:37.680> the<19:38:37.976> the 19:38:38.206 --> 19:38:38.216 align:start position:0% and then what would happen is the the 19:38:38.216 --> 19:38:40.366 align:start position:0% and then what would happen is the the your<19:38:38.576> phone<19:38:38.824> would<19:38:39.120> go<19:38:39.296> somebody<19:38:39.896> would<19:38:40.192> call 19:38:40.366 --> 19:38:40.376 align:start position:0% your phone would go somebody would call 19:38:40.376 --> 19:38:42.414 align:start position:0% your phone would go somebody would call tech<19:38:40.616> support<19:38:40.920> and 19:38:42.414 --> 19:38:42.424 align:start position:0% tech support and 19:38:42.424 --> 19:38:43.494 align:start position:0% tech support and um it<19:38:42.784> would<19:38:42.832> help<19:38:43.016> you<19:38:43.192> in<19:38:43.376> your 19:38:43.494 --> 19:38:43.504 align:start position:0% um it would help you in your 19:38:43.504 --> 19:38:45.486 align:start position:0% um it would help you in your troubleshooting<19:38:44.160> because<19:38:44.400> the<19:38:45.296> broadcast 19:38:45.486 --> 19:38:45.496 align:start position:0% troubleshooting because the broadcast 19:38:45.496 --> 19:38:48.590 align:start position:0% troubleshooting because the broadcast isn't<19:38:46.496> affecting<19:38:46.976> everyone<19:38:47.216> here<19:38:47.640> but 19:38:48.590 --> 19:38:48.600 align:start position:0% isn't affecting everyone here but 19:38:48.600 --> 19:38:51.166 align:start position:0% isn't affecting everyone here but basically<19:38:48.960> you're<19:38:49.144> told<19:38:49.440> that<19:38:50.464> um<19:38:50.464> everyone 19:38:51.166 --> 19:38:51.176 align:start position:0% basically you're told that um everyone 19:38:51.176 --> 19:38:53.270 align:start position:0% basically you're told that um everyone in<19:38:51.536> the<19:38:51.720> sales<19:38:51.896> team<19:38:52.256> is<19:38:52.496> getting<19:38:52.744> a<19:38:53.040> really 19:38:53.270 --> 19:38:53.280 align:start position:0% in the sales team is getting a really 19:38:53.280 --> 19:38:56.566 align:start position:0% in the sales team is getting a really slow<19:38:53.512> Network<19:38:53.824> response<19:38:54.600> and<19:38:55.376> then<19:38:55.504> this<19:38:55.800> this 19:38:56.566 --> 19:38:56.576 align:start position:0% slow Network response and then this this 19:38:56.576 --> 19:38:58.070 align:start position:0% slow Network response and then this this um this<19:38:57.000> is<19:38:57.120> known<19:38:57.296> as<19:38:57.424> the<19:38:57.600> divide<19:38:57.960> and 19:38:58.070 --> 19:38:58.080 align:start position:0% um this is known as the divide and 19:38:58.080 --> 19:39:00.414 align:start position:0% um this is known as the divide and conquer<19:38:58.440> method<19:38:58.800> of<19:38:58.920> troubleshooting<19:38:59.696> you 19:39:00.414 --> 19:39:00.424 align:start position:0% conquer method of troubleshooting you 19:39:00.424 --> 19:39:02.390 align:start position:0% conquer method of troubleshooting you know<19:39:00.536> that<19:39:00.720> everyone<19:39:00.832> here<19:39:01.144> is<19:39:01.320> affected 19:39:02.390 --> 19:39:02.400 align:start position:0% know that everyone here is affected 19:39:02.400 --> 19:39:04.790 align:start position:0% know that everyone here is affected and<19:39:03.000> then<19:39:03.120> so<19:39:03.424> you'd<19:39:03.960> be<19:39:03.960> looking<19:39:04.192> at<19:39:04.440> these 19:39:04.790 --> 19:39:04.800 align:start position:0% and then so you'd be looking at these 19:39:04.800 --> 19:39:07.182 align:start position:0% and then so you'd be looking at these ports<19:39:05.216> on<19:39:05.336> the<19:39:05.512> switch<19:39:05.696> you<19:39:06.480> could<19:39:06.536> use<19:39:06.784> a<19:39:06.960> the 19:39:07.182 --> 19:39:07.192 align:start position:0% ports on the switch you could use a the 19:39:07.192 --> 19:39:10.734 align:start position:0% ports on the switch you could use a the sniffer<19:39:08.176> the<19:39:09.176> network<19:39:09.360> sniffer<19:39:10.016> and<19:39:10.496> you'd 19:39:10.734 --> 19:39:10.744 align:start position:0% sniffer the network sniffer and you'd 19:39:10.744 --> 19:39:12.110 align:start position:0% sniffer the network sniffer and you'd probably<19:39:10.856> quite<19:39:11.104> quickly<19:39:11.400> see<19:39:11.640> the<19:39:11.824> IP 19:39:12.110 --> 19:39:12.120 align:start position:0% probably quite quickly see the IP 19:39:12.120 --> 19:39:14.926 align:start position:0% probably quite quickly see the IP address<19:39:12.440> dot<19:39:13.440> one<19:39:13.616> is<19:39:14.216> sending<19:39:14.576> out<19:39:14.696> normal 19:39:14.926 --> 19:39:14.936 align:start position:0% address dot one is sending out normal 19:39:14.936 --> 19:39:16.606 align:start position:0% address dot one is sending out normal about<19:39:15.176> traffic<19:39:15.600> and<19:39:15.960> then<19:39:16.080> it's<19:39:16.192> gone<19:39:16.376> through 19:39:16.606 --> 19:39:16.616 align:start position:0% about traffic and then it's gone through 19:39:16.616 --> 19:39:18.822 align:start position:0% about traffic and then it's gone through the<19:39:16.856> roof<19:39:17.160> whereas<19:39:18.120> all<19:39:18.296> the<19:39:18.424> other<19:39:18.536> devices 19:39:18.822 --> 19:39:18.832 align:start position:0% the roof whereas all the other devices 19:39:18.832 --> 19:39:21.590 align:start position:0% the roof whereas all the other devices on<19:39:19.320> this<19:39:19.504> particular<19:39:19.856> and<19:39:20.824> segment<19:39:21.240> of 19:39:21.590 --> 19:39:21.600 align:start position:0% on this particular and segment of 19:39:21.600 --> 19:39:27.526 align:start position:0% on this particular and segment of sending<19:39:22.144> a<19:39:22.256> normal<19:39:22.496> amount<19:39:22.920> of<19:39:23.104> traffic 19:39:27.526 --> 19:39:27.536 align:start position:0% 19:39:27.536 --> 19:39:31.182 align:start position:0% access<19:39:28.496> lists<19:39:29.160> and<19:39:29.872> these<19:39:30.424> can<19:39:30.720> be<19:39:30.896> used<19:39:31.016> to 19:39:31.182 --> 19:39:31.192 align:start position:0% access lists and these can be used to 19:39:31.192 --> 19:39:34.430 align:start position:0% access lists and these can be used to block<19:39:31.440> an<19:39:31.800> entire<19:39:32.104> network<19:39:32.464> or<19:39:33.240> subnet<19:39:33.656> one 19:39:34.430 --> 19:39:34.440 align:start position:0% block an entire network or subnet one 19:39:34.440 --> 19:39:37.182 align:start position:0% block an entire network or subnet one particular<19:39:34.800> host<19:39:35.104> or<19:39:35.512> a<19:39:35.640> number<19:39:35.760> of<19:39:35.936> hosts<19:39:36.424> a 19:39:37.182 --> 19:39:37.192 align:start position:0% particular host or a number of hosts a 19:39:37.192 --> 19:39:40.734 align:start position:0% particular host or a number of hosts a particular<19:39:37.504> port<19:39:37.800> number<19:39:38.104> or<19:39:38.512> a<19:39:38.696> protocol<19:39:39.056> so 19:39:40.734 --> 19:39:40.744 align:start position:0% particular port number or a protocol so 19:39:40.744 --> 19:39:43.734 align:start position:0% particular port number or a protocol so um<19:39:41.120> icmp<19:39:42.120> or 19:39:43.734 --> 19:39:43.744 align:start position:0% um icmp or 19:39:43.744 --> 19:39:44.270 align:start position:0% um icmp or um 19:39:44.270 --> 19:39:44.280 align:start position:0% um 19:39:44.280 --> 19:39:47.206 align:start position:0% um whatever<19:39:44.936> you<19:39:45.176> want 19:39:47.206 --> 19:39:47.216 align:start position:0% whatever you want 19:39:47.216 --> 19:39:49.670 align:start position:0% whatever you want airport<19:39:47.640> numbers<19:39:48.056> could<19:39:48.360> be<19:39:48.480> anything<19:39:48.680> dhep 19:39:49.670 --> 19:39:49.680 align:start position:0% airport numbers could be anything dhep 19:39:49.680 --> 19:39:55.366 align:start position:0% airport numbers could be anything dhep DNS<19:39:50.512> host<19:39:51.296> dot<19:39:51.960> one<19:39:52.144> and<19:39:52.616> then<19:39:52.744> obviously 19:39:55.366 --> 19:39:55.376 align:start position:0% 19:39:55.376 --> 19:39:57.470 align:start position:0% entire<19:39:56.040> Networks 19:39:57.470 --> 19:39:57.480 align:start position:0% entire Networks 19:39:57.480 --> 19:39:59.862 align:start position:0% entire Networks so<19:39:58.080> it's<19:39:58.192> a<19:39:58.440> list<19:39:58.552> of<19:39:58.744> permitted<19:39:59.216> or<19:39:59.512> denied 19:39:59.862 --> 19:39:59.872 align:start position:0% so it's a list of permitted or denied 19:39:59.872 --> 19:40:02.750 align:start position:0% so it's a list of permitted or denied traffic<19:40:00.320> so<19:40:01.320> if<19:40:01.680> you<19:40:01.920> don't<19:40:02.104> worry<19:40:02.216> about<19:40:02.336> the 19:40:02.750 --> 19:40:02.760 align:start position:0% traffic so if you don't worry about the 19:40:02.760 --> 19:40:04.606 align:start position:0% traffic so if you don't worry about the uh<19:40:03.056> text<19:40:03.424> here<19:40:03.720> because<19:40:03.896> you're<19:40:04.080> not<19:40:04.192> expected 19:40:04.606 --> 19:40:04.616 align:start position:0% uh text here because you're not expected 19:40:04.616 --> 19:40:06.646 align:start position:0% uh text here because you're not expected to<19:40:04.744> know<19:40:04.920> this<19:40:05.104> for<19:40:05.336> the<19:40:05.464> exam<19:40:05.760> you've<19:40:06.536> give 19:40:06.646 --> 19:40:06.656 align:start position:0% to know this for the exam you've give 19:40:06.656 --> 19:40:08.926 align:start position:0% to know this for the exam you've give you've<19:40:07.016> created<19:40:07.192> an<19:40:07.320> access<19:40:07.504> list<19:40:07.976> and<19:40:08.640> you've 19:40:08.926 --> 19:40:08.936 align:start position:0% you've created an access list and you've 19:40:08.936 --> 19:40:12.110 align:start position:0% you've created an access list and you've said<19:40:09.120> do<19:40:09.656> you<19:40:09.832> know<19:40:09.896> this<19:40:10.144> traffic<19:40:10.512> icmp<19:40:11.512> and 19:40:12.110 --> 19:40:12.120 align:start position:0% said do you know this traffic icmp and 19:40:12.120 --> 19:40:15.046 align:start position:0% said do you know this traffic icmp and permits<19:40:12.656> IP<19:40:13.016> traffic<19:40:13.512> and<19:40:14.512> what<19:40:14.640> happens<19:40:14.760> is 19:40:15.046 --> 19:40:15.056 align:start position:0% permits IP traffic and what happens is 19:40:15.056 --> 19:40:17.750 align:start position:0% permits IP traffic and what happens is the<19:40:15.296> access<19:40:15.424> list<19:40:15.832> always<19:40:16.320> processed<19:40:17.160> top<19:40:17.576> to 19:40:17.750 --> 19:40:17.760 align:start position:0% the access list always processed top to 19:40:17.760 --> 19:40:20.150 align:start position:0% the access list always processed top to bottom<19:40:18.176> I've<19:40:18.720> only<19:40:18.960> got<19:40:19.144> two<19:40:19.320> two<19:40:19.552> entries<19:40:19.920> on 19:40:20.150 --> 19:40:20.160 align:start position:0% bottom I've only got two two entries on 19:40:20.160 --> 19:40:21.950 align:start position:0% bottom I've only got two two entries on this<19:40:20.400> so<19:40:20.824> it'll<19:40:21.056> be<19:40:21.176> pretty<19:40:21.360> quick<19:40:21.656> actually 19:40:21.950 --> 19:40:21.960 align:start position:0% this so it'll be pretty quick actually 19:40:21.960 --> 19:40:24.414 align:start position:0% this so it'll be pretty quick actually but<19:40:22.920> as<19:40:23.216> soon<19:40:23.336> as<19:40:23.464> the<19:40:23.576> access<19:40:23.696> to<19:40:23.936> this<19:40:24.120> reach 19:40:24.414 --> 19:40:24.424 align:start position:0% but as soon as the access to this reach 19:40:24.424 --> 19:40:27.774 align:start position:0% but as soon as the access to this reach is<19:40:24.832> aligned<19:40:25.552> so<19:40:25.744> say<19:40:25.856> it's<19:40:25.976> icmp<19:40:26.640> traffic<19:40:26.936> it 19:40:27.774 --> 19:40:27.784 align:start position:0% is aligned so say it's icmp traffic it 19:40:27.784 --> 19:40:29.926 align:start position:0% is aligned so say it's icmp traffic it would<19:40:27.896> reach<19:40:28.256> this<19:40:28.680> particular<19:40:28.976> line 19:40:29.926 --> 19:40:29.936 align:start position:0% would reach this particular line 19:40:29.936 --> 19:40:32.030 align:start position:0% would reach this particular line and<19:40:30.536> then<19:40:30.656> it<19:40:30.896> would<19:40:31.016> be<19:40:31.144> a<19:40:31.376> match<19:40:31.552> and<19:40:31.920> it 19:40:32.030 --> 19:40:32.040 align:start position:0% and then it would be a match and it 19:40:32.040 --> 19:40:34.246 align:start position:0% and then it would be a match and it would<19:40:32.216> be<19:40:32.400> denied<19:40:32.872> the<19:40:33.536> access<19:40:33.720> this<19:40:34.080> wouldn't 19:40:34.246 --> 19:40:34.256 align:start position:0% would be denied the access this wouldn't 19:40:34.256 --> 19:40:36.646 align:start position:0% would be denied the access this wouldn't go<19:40:34.440> all<19:40:34.616> the<19:40:34.744> way<19:40:34.744> to<19:40:34.920> the<19:40:35.104> bottom<19:40:35.936> if<19:40:36.360> it's<19:40:36.480> not 19:40:36.646 --> 19:40:36.656 align:start position:0% go all the way to the bottom if it's not 19:40:36.656 --> 19:40:38.814 align:start position:0% go all the way to the bottom if it's not icmp<19:40:37.320> traffic<19:40:37.616> it<19:40:38.040> would<19:40:38.160> reach<19:40:38.464> the<19:40:38.640> next 19:40:38.814 --> 19:40:38.824 align:start position:0% icmp traffic it would reach the next 19:40:38.824 --> 19:40:41.326 align:start position:0% icmp traffic it would reach the next item<19:40:39.240> on<19:40:39.424> your<19:40:39.600> list<19:40:39.784> and<19:40:40.552> the<19:40:40.744> chances<19:40:41.104> are 19:40:41.326 --> 19:40:41.336 align:start position:0% item on your list and the chances are 19:40:41.336 --> 19:40:44.206 align:start position:0% item on your list and the chances are it's<19:40:42.000> going<19:40:42.240> to<19:40:42.424> be<19:40:42.656> some<19:40:43.376> other<19:40:43.552> sort<19:40:43.800> of<19:40:43.920> Ip 19:40:44.206 --> 19:40:44.216 align:start position:0% it's going to be some other sort of Ip 19:40:44.216 --> 19:40:49.966 align:start position:0% it's going to be some other sort of Ip traffic<19:40:44.512> and<19:40:45.360> it<19:40:45.480> would<19:40:45.656> be<19:40:45.896> permitted 19:40:49.966 --> 19:40:49.976 align:start position:0% 19:40:49.976 --> 19:40:52.486 align:start position:0% honey<19:40:50.336> pot<19:40:50.696> honey<19:40:51.000> net<19:40:51.424> honey<19:40:51.960> pots<19:40:52.320> attract 19:40:52.486 --> 19:40:52.496 align:start position:0% honey pot honey net honey pots attract 19:40:52.496 --> 19:40:54.286 align:start position:0% honey pot honey net honey pots attract possible<19:40:52.920> attackers<19:40:53.400> into<19:40:53.640> an<19:40:53.872> isolated 19:40:54.286 --> 19:40:54.296 align:start position:0% possible attackers into an isolated 19:40:54.296 --> 19:40:56.454 align:start position:0% possible attackers into an isolated environment 19:40:56.454 --> 19:40:56.464 align:start position:0% environment 19:40:56.464 --> 19:40:58.790 align:start position:0% environment so<19:40:56.872> this<19:40:57.056> is<19:40:57.176> your<19:40:57.424> attacker<19:40:58.016> and<19:40:58.496> it's<19:40:58.616> a 19:40:58.790 --> 19:40:58.800 align:start position:0% so this is your attacker and it's a 19:40:58.800 --> 19:41:00.822 align:start position:0% so this is your attacker and it's a potential<19:40:59.160> victim<19:40:59.640> and<19:41:00.240> what<19:41:00.424> they<19:41:00.656> don't 19:41:00.822 --> 19:41:00.832 align:start position:0% potential victim and what they don't 19:41:00.832 --> 19:41:02.630 align:start position:0% potential victim and what they don't know<19:41:01.016> or<19:41:01.256> they<19:41:01.440> should<19:41:01.552> know<19:41:01.744> is<19:41:02.040> they've 19:41:02.630 --> 19:41:02.640 align:start position:0% know or they should know is they've 19:41:02.640 --> 19:41:04.670 align:start position:0% know or they should know is they've actually<19:41:02.760> been<19:41:03.056> fooled<19:41:03.784> into<19:41:03.960> redirecting 19:41:04.670 --> 19:41:04.680 align:start position:0% actually been fooled into redirecting 19:41:04.680 --> 19:41:05.814 align:start position:0% actually been fooled into redirecting into<19:41:04.920> this 19:41:05.814 --> 19:41:05.824 align:start position:0% into this 19:41:05.824 --> 19:41:08.814 align:start position:0% into this um<19:41:05.872> new<19:41:06.600> net<19:41:06.784> system<19:41:07.104> they<19:41:08.104> can't<19:41:08.280> do<19:41:08.464> any<19:41:08.576> harm 19:41:08.814 --> 19:41:08.824 align:start position:0% um new net system they can't do any harm 19:41:08.824 --> 19:41:12.470 align:start position:0% um new net system they can't do any harm in<19:41:09.056> this<19:41:09.240> place<19:41:09.480> and<19:41:10.080> what<19:41:10.320> you<19:41:10.552> can<19:41:10.744> do 19:41:12.470 --> 19:41:12.480 align:start position:0% in this place and what you can do 19:41:12.480 --> 19:41:15.470 align:start position:0% in this place and what you can do is<19:41:13.376> this<19:41:14.040> is<19:41:14.104> a<19:41:14.280> pair<19:41:14.400> of<19:41:14.512> binoculars<19:41:15.120> I<19:41:15.360> know 19:41:15.470 --> 19:41:15.480 align:start position:0% is this is a pair of binoculars I know 19:41:15.480 --> 19:41:17.862 align:start position:0% is this is a pair of binoculars I know it's<19:41:15.720> absolutely<19:41:16.256> Dreadful<19:41:16.744> isn't<19:41:17.104> it 19:41:17.862 --> 19:41:17.872 align:start position:0% it's absolutely Dreadful isn't it 19:41:17.872 --> 19:41:20.230 align:start position:0% it's absolutely Dreadful isn't it this<19:41:18.296> is<19:41:18.480> you<19:41:18.656> as<19:41:18.832> the<19:41:19.016> network<19:41:19.144> administrator 19:41:20.230 --> 19:41:20.240 align:start position:0% this is you as the network administrator 19:41:20.240 --> 19:41:23.206 align:start position:0% this is you as the network administrator watching<19:41:21.240> what<19:41:21.600> they<19:41:21.832> do<19:41:22.016> you'll<19:41:22.976> obviously 19:41:23.206 --> 19:41:23.216 align:start position:0% watching what they do you'll obviously 19:41:23.216 --> 19:41:24.710 align:start position:0% watching what they do you'll obviously be<19:41:23.336> doing<19:41:23.512> it<19:41:23.640> via<19:41:23.872> whatever<19:41:24.056> software<19:41:24.536> and 19:41:24.710 --> 19:41:24.720 align:start position:0% be doing it via whatever software and 19:41:24.720 --> 19:41:26.454 align:start position:0% be doing it via whatever software and you<19:41:24.832> can<19:41:24.960> see<19:41:25.080> what<19:41:25.256> commands<19:41:25.744> are<19:41:25.800> executing 19:41:26.454 --> 19:41:26.464 align:start position:0% you can see what commands are executing 19:41:26.464 --> 19:41:29.030 align:start position:0% you can see what commands are executing and<19:41:27.056> trying<19:41:27.240> to<19:41:27.360> inject<19:41:27.656> pieces<19:41:28.016> of<19:41:28.256> code<19:41:28.496> and 19:41:29.030 --> 19:41:29.040 align:start position:0% and trying to inject pieces of code and 19:41:29.040 --> 19:41:31.606 align:start position:0% and trying to inject pieces of code and this<19:41:29.280> whole<19:41:29.464> environment<19:41:29.936> here<19:41:30.296> is<19:41:31.616> um 19:41:31.606 --> 19:41:31.616 align:start position:0% this whole environment here is um 19:41:31.616 --> 19:41:33.286 align:start position:0% this whole environment here is um protected<19:41:32.160> is<19:41:32.336> segmented<19:41:32.760> off<19:41:32.936> from<19:41:33.120> your 19:41:33.286 --> 19:41:33.296 align:start position:0% protected is segmented off from your 19:41:33.296 --> 19:41:35.630 align:start position:0% protected is segmented off from your network<19:41:33.536> and<19:41:34.376> then<19:41:34.552> that<19:41:34.800> that<19:41:35.104> lets<19:41:35.576> you 19:41:35.630 --> 19:41:35.640 align:start position:0% network and then that that lets you 19:41:35.640 --> 19:41:38.926 align:start position:0% network and then that that lets you design<19:41:36.536> a<19:41:36.832> series<19:41:37.256> of<19:41:37.504> steps<19:41:37.920> to<19:41:38.464> protect<19:41:38.696> your 19:41:38.926 --> 19:41:38.936 align:start position:0% design a series of steps to protect your 19:41:38.936 --> 19:41:41.094 align:start position:0% design a series of steps to protect your network<19:41:39.120> so<19:41:39.960> you're<19:41:40.144> analyzing<19:41:40.616> the<19:41:40.800> behavior 19:41:41.094 --> 19:41:41.104 align:start position:0% network so you're analyzing the behavior 19:41:41.104 --> 19:41:43.734 align:start position:0% network so you're analyzing the behavior and<19:41:41.336> Gathering<19:41:41.696> the<19:41:41.872> information<19:41:42.376> if<19:41:43.376> it's<19:41:43.552> a 19:41:43.734 --> 19:41:43.744 align:start position:0% and Gathering the information if it's a 19:41:43.744 --> 19:41:45.646 align:start position:0% and Gathering the information if it's a honey<19:41:43.920> net<19:41:44.336> it's<19:41:44.760> basically<19:41:45.000> a<19:41:45.296> chain<19:41:45.424> of 19:41:45.646 --> 19:41:45.656 align:start position:0% honey net it's basically a chain of 19:41:45.656 --> 19:41:47.926 align:start position:0% honey net it's basically a chain of Honey<19:41:45.832> pots<19:41:46.496> so<19:41:47.104> you've<19:41:47.336> got<19:41:47.464> you've<19:41:47.696> got<19:41:47.824> your 19:41:47.926 --> 19:41:47.936 align:start position:0% Honey pots so you've got you've got your 19:41:47.936 --> 19:41:50.206 align:start position:0% Honey pots so you've got you've got your honey<19:41:48.056> pot<19:41:48.480> here<19:41:48.784> and<19:41:49.504> but<19:41:49.680> what<19:41:49.856> you've<19:41:50.104> done 19:41:50.206 --> 19:41:50.216 align:start position:0% honey pot here and but what you've done 19:41:50.216 --> 19:41:53.150 align:start position:0% honey pot here and but what you've done is<19:41:50.464> you've<19:41:51.120> chained<19:41:51.480> them<19:41:51.536> together<19:41:51.784> for 19:41:53.150 --> 19:41:53.160 align:start position:0% is you've chained them together for 19:41:53.160 --> 19:41:55.246 align:start position:0% is you've chained them together for whatever<19:41:53.760> reason 19:41:55.246 --> 19:41:55.256 align:start position:0% whatever reason 19:41:55.256 --> 19:41:58.070 align:start position:0% whatever reason I<19:41:55.744> usually<19:41:56.040> place<19:41:56.280> in<19:41:56.936> um<19:41:56.936> Network<19:41:57.480> segments 19:41:58.070 --> 19:41:58.080 align:start position:0% I usually place in um Network segments 19:41:58.080 --> 19:42:00.470 align:start position:0% I usually place in um Network segments this<19:41:58.552> will<19:41:58.680> this<19:41:59.040> will<19:41:59.160> be<19:41:59.336> isolated<19:41:59.824> by<19:42:00.240> your 19:42:00.470 --> 19:42:00.480 align:start position:0% this will this will be isolated by your 19:42:00.480 --> 19:42:03.110 align:start position:0% this will this will be isolated by your firewall<19:42:00.960> so<19:42:01.616> they're<19:42:01.800> coming<19:42:02.040> in<19:42:02.336> and<19:42:03.000> they 19:42:03.110 --> 19:42:03.120 align:start position:0% firewall so they're coming in and they 19:42:03.120 --> 19:42:05.270 align:start position:0% firewall so they're coming in and they get<19:42:03.240> redirected<19:42:03.784> to<19:42:03.960> your<19:42:04.080> firewall<19:42:04.552> this<19:42:05.160> is 19:42:05.270 --> 19:42:05.280 align:start position:0% get redirected to your firewall this is 19:42:05.280 --> 19:42:07.494 align:start position:0% get redirected to your firewall this is actually<19:42:05.576> your<19:42:06.360> local<19:42:06.480> area<19:42:06.784> network<19:42:07.144> over 19:42:07.494 --> 19:42:07.504 align:start position:0% actually your local area network over 19:42:07.504 --> 19:42:11.390 align:start position:0% actually your local area network over here 19:42:11.390 --> 19:42:11.400 align:start position:0% 19:42:11.400 --> 19:42:13.430 align:start position:0% sting<19:42:11.936> uh<19:42:12.296> comment<19:42:12.600> here<19:42:12.784> have<19:42:12.960> actually<19:42:13.080> got 19:42:13.430 --> 19:42:13.440 align:start position:0% sting uh comment here have actually got 19:42:13.440 --> 19:42:15.646 align:start position:0% sting uh comment here have actually got the<19:42:14.160> um 19:42:15.646 --> 19:42:15.656 align:start position:0% the um 19:42:15.656 --> 19:42:18.822 align:start position:0% the um the<19:42:16.192> pen<19:42:16.320> test<19:42:16.552> certification<19:42:17.216> out<19:42:17.832> I'm 19:42:18.822 --> 19:42:18.832 align:start position:0% the pen test certification out I'm 19:42:18.832 --> 19:42:21.350 align:start position:0% the pen test certification out I'm looking<19:42:19.016> into<19:42:19.256> adding<19:42:19.920> it<19:42:20.040> now 19:42:21.350 --> 19:42:21.360 align:start position:0% looking into adding it now 19:42:21.360 --> 19:42:24.350 align:start position:0% looking into adding it now um<19:42:21.480> so<19:42:21.960> keep<19:42:22.144> your<19:42:22.320> eyes<19:42:22.440> open<19:42:22.744> it<19:42:23.640> scans<19:42:24.000> your 19:42:24.350 --> 19:42:24.360 align:start position:0% um so keep your eyes open it scans your 19:42:24.360 --> 19:42:25.966 align:start position:0% um so keep your eyes open it scans your network<19:42:24.600> in<19:42:24.832> order<19:42:25.016> to<19:42:25.192> find<19:42:25.504> ports<19:42:25.920> or 19:42:25.966 --> 19:42:25.976 align:start position:0% network in order to find ports or 19:42:25.976 --> 19:42:27.950 align:start position:0% network in order to find ports or protocols<19:42:26.576> with<19:42:26.696> floors<19:42:27.120> I've<19:42:27.424> talked<19:42:27.896> about 19:42:27.950 --> 19:42:27.960 align:start position:0% protocols with floors I've talked about 19:42:27.960 --> 19:42:30.046 align:start position:0% protocols with floors I've talked about this<19:42:28.256> kind<19:42:28.376> of<19:42:28.496> stuff<19:42:28.616> before<19:42:28.920> part<19:42:29.696> of<19:42:29.872> your 19:42:30.046 --> 19:42:30.056 align:start position:0% this kind of stuff before part of your 19:42:30.056 --> 19:42:32.566 align:start position:0% this kind of stuff before part of your regular<19:42:30.424> security<19:42:30.896> ordering<19:42:31.856> and<19:42:32.216> audition 19:42:32.566 --> 19:42:32.576 align:start position:0% regular security ordering and audition 19:42:32.576 --> 19:42:36.230 align:start position:0% regular security ordering and audition process<19:42:33.120> so<19:42:33.720> say<19:42:34.016> every<19:42:34.376> every<19:42:34.744> Monday<19:42:35.240> you 19:42:36.230 --> 19:42:36.240 align:start position:0% process so say every every Monday you 19:42:36.240 --> 19:42:38.030 align:start position:0% process so say every every Monday you carry<19:42:36.656> out<19:42:36.784> this<19:42:37.080> particular 19:42:38.030 --> 19:42:38.040 align:start position:0% carry out this particular 19:42:38.040 --> 19:42:39.710 align:start position:0% carry out this particular um test<19:42:38.336> on<19:42:38.576> your<19:42:38.760> network 19:42:39.710 --> 19:42:39.720 align:start position:0% um test on your network 19:42:39.720 --> 19:42:43.310 align:start position:0% um test on your network it<19:42:40.256> can<19:42:40.376> simulate<19:42:40.800> a<19:42:41.040> type<19:42:41.216> of<19:42:41.336> attack<19:42:41.576> and 19:42:43.310 --> 19:42:43.320 align:start position:0% it can simulate a type of attack and 19:42:43.320 --> 19:42:45.166 align:start position:0% it can simulate a type of attack and um<19:42:43.376> it's<19:42:43.616> well<19:42:43.856> recommended<19:42:44.336> that<19:42:44.576> you<19:42:44.696> you<19:42:44.872> do 19:42:45.166 --> 19:42:45.176 align:start position:0% um it's well recommended that you you do 19:42:45.176 --> 19:42:47.150 align:start position:0% um it's well recommended that you you do this<19:42:45.424> so<19:42:46.192> we've<19:42:46.320> covered<19:42:46.616> a<19:42:46.744> lot<19:42:46.856> of<19:42:46.976> stuff 19:42:47.150 --> 19:42:47.160 align:start position:0% this so we've covered a lot of stuff 19:42:47.160 --> 19:42:48.350 align:start position:0% this so we've covered a lot of stuff here 19:42:48.350 --> 19:42:48.360 align:start position:0% here 19:42:48.360 --> 19:42:50.030 align:start position:0% here um<19:42:48.480> managing<19:42:49.144> your<19:42:49.320> signatures<19:42:49.800> device 19:42:50.030 --> 19:42:50.040 align:start position:0% um managing your signatures device 19:42:50.040 --> 19:42:52.734 align:start position:0% um managing your signatures device hardening<19:42:50.696> changing<19:42:51.480> your<19:42:51.656> native<19:42:51.896> VLAN<19:42:52.440> must 19:42:52.734 --> 19:42:52.744 align:start position:0% hardening changing your native VLAN must 19:42:52.744 --> 19:42:55.430 align:start position:0% hardening changing your native VLAN must do<19:42:52.976> protecting<19:42:53.824> your<19:42:54.120> ports 19:42:55.430 --> 19:42:55.440 align:start position:0% do protecting your ports 19:42:55.440 --> 19:42:58.006 align:start position:0% do protecting your ports we<19:42:56.280> looked<19:42:56.824> at<19:42:57.240> um 19:42:58.006 --> 19:42:58.016 align:start position:0% we looked at um 19:42:58.016 --> 19:43:00.774 align:start position:0% we looked at um protecting<19:42:58.680> it<19:42:58.920> from<19:42:59.216> the<19:42:59.760> STP<19:43:00.296> packets 19:43:00.774 --> 19:43:00.784 align:start position:0% protecting it from the STP packets 19:43:00.784 --> 19:43:04.366 align:start position:0% protecting it from the STP packets coming<19:43:01.016> in<19:43:01.256> the<19:43:01.504> bridge<19:43:02.056> protocol<19:43:03.056> data<19:43:03.896> units 19:43:04.366 --> 19:43:04.376 align:start position:0% coming in the bridge protocol data units 19:43:04.376 --> 19:43:08.270 align:start position:0% coming in the bridge protocol data units so<19:43:05.040> we<19:43:05.336> don't<19:43:05.512> it<19:43:06.176> doesn't<19:43:06.296> become<19:43:06.720> a<19:43:07.016> root 19:43:08.270 --> 19:43:08.280 align:start position:0% so we don't it doesn't become a root 19:43:08.280 --> 19:43:11.150 align:start position:0% so we don't it doesn't become a root or<19:43:09.240> um<19:43:09.240> and<19:43:09.424> it<19:43:09.536> doesn't<19:43:09.720> change<19:43:10.080> the 19:43:11.150 --> 19:43:11.160 align:start position:0% or um and it doesn't change the 19:43:11.160 --> 19:43:13.494 align:start position:0% or um and it doesn't change the um<19:43:11.216> it<19:43:11.936> doesn't<19:43:12.056> become<19:43:12.360> a<19:43:12.480> report<19:43:12.656> and<19:43:13.376> it 19:43:13.494 --> 19:43:13.504 align:start position:0% um it doesn't become a report and it 19:43:13.504 --> 19:43:15.646 align:start position:0% um it doesn't become a report and it doesn't<19:43:13.616> become<19:43:13.920> the<19:43:14.104> STP 19:43:15.646 --> 19:43:15.656 align:start position:0% doesn't become the STP 19:43:15.656 --> 19:43:18.166 align:start position:0% doesn't become the STP um<19:43:15.784> root<19:43:16.192> either<19:43:16.376> both<19:43:17.336> very<19:43:17.640> bad<19:43:17.824> things<19:43:18.000> for 19:43:18.166 --> 19:43:18.176 align:start position:0% um root either both very bad things for 19:43:18.176 --> 19:43:19.542 align:start position:0% um root either both very bad things for your<19:43:18.296> network 19:43:19.542 --> 19:43:19.552 align:start position:0% your network 19:43:19.552 --> 19:43:23.030 align:start position:0% your network access<19:43:20.280> lists<19:43:21.016> Honeypot<19:43:22.016> and<19:43:22.192> honey<19:43:22.320> Nets<19:43:22.856> and 19:43:23.030 --> 19:43:23.040 align:start position:0% access lists Honeypot and honey Nets and 19:43:23.040 --> 19:43:25.246 align:start position:0% access lists Honeypot and honey Nets and then<19:43:23.160> penetration<19:43:23.696> testing<19:43:24.240> so<19:43:24.832> that's<19:43:25.080> all 19:43:25.246 --> 19:43:25.256 align:start position:0% then penetration testing so that's all 19:43:25.256 --> 19:43:37.600 align:start position:0% then penetration testing so that's all for<19:43:25.440> now<19:43:25.616> thanks<19:43:26.160> for<19:43:26.336> watching 19:43:37.600 --> 19:43:37.610 align:start position:0% 19:43:37.610 --> 19:43:54.526 align:start position:0% [Music] 19:43:54.526 --> 19:43:54.536 align:start position:0% 19:43:54.536 --> 19:43:57.070 align:start position:0% welcome<19:43:54.960> to<19:43:55.144> module<19:43:55.552> 14<19:43:55.744> lesson<19:43:56.464> three 19:43:57.070 --> 19:43:57.080 align:start position:0% welcome to module 14 lesson three 19:43:57.080 --> 19:44:02.270 align:start position:0% welcome to module 14 lesson three policies<19:43:58.080> and<19:43:58.496> best<19:43:58.744> practices 19:44:02.270 --> 19:44:02.280 align:start position:0% 19:44:02.280 --> 19:44:04.246 align:start position:0% a<19:44:02.760> few<19:44:02.872> things<19:44:03.056> we<19:44:03.240> want<19:44:03.424> to<19:44:03.536> cover<19:44:03.600> here<19:44:03.896> the 19:44:04.246 --> 19:44:04.256 align:start position:0% a few things we want to cover here the 19:44:04.256 --> 19:44:06.526 align:start position:0% a few things we want to cover here the privileged<19:44:04.680> user<19:44:05.160> agreement<19:44:05.576> your<19:44:06.360> password 19:44:06.526 --> 19:44:06.536 align:start position:0% privileged user agreement your password 19:44:06.536 --> 19:44:07.910 align:start position:0% privileged user agreement your password policy 19:44:07.910 --> 19:44:07.920 align:start position:0% policy 19:44:07.920 --> 19:44:10.366 align:start position:0% policy on<19:44:08.464> off-boarding 19:44:10.366 --> 19:44:10.376 align:start position:0% on off-boarding 19:44:10.376 --> 19:44:12.350 align:start position:0% on off-boarding which<19:44:10.856> is<19:44:10.976> when<19:44:11.160> people<19:44:11.400> join<19:44:11.936> your<19:44:12.120> business 19:44:12.350 --> 19:44:12.360 align:start position:0% which is when people join your business 19:44:12.360 --> 19:44:14.926 align:start position:0% which is when people join your business and<19:44:12.832> leave<19:44:13.080> whatever<19:44:13.504> reason 19:44:14.926 --> 19:44:14.936 align:start position:0% and leave whatever reason 19:44:14.936 --> 19:44:17.686 align:start position:0% and leave whatever reason your<19:44:15.480> licensing<19:44:15.896> restrictions<19:44:16.696> restrictions 19:44:17.686 --> 19:44:17.696 align:start position:0% your licensing restrictions restrictions 19:44:17.696 --> 19:44:21.134 align:start position:0% your licensing restrictions restrictions International<19:44:18.360> export<19:44:19.080> controls 19:44:21.134 --> 19:44:21.144 align:start position:0% International export controls 19:44:21.144 --> 19:44:24.046 align:start position:0% International export controls preventing<19:44:22.144> data<19:44:22.744> loss<19:44:23.104> and<19:44:23.464> remote<19:44:23.640> access 19:44:24.046 --> 19:44:24.056 align:start position:0% preventing data loss and remote access 19:44:24.056 --> 19:44:26.502 align:start position:0% preventing data loss and remote access policies 19:44:26.502 --> 19:44:26.512 align:start position:0% policies 19:44:26.512 --> 19:44:29.454 align:start position:0% policies incident<19:44:27.176> response<19:44:27.720> policies<19:44:28.256> bring<19:44:29.216> your 19:44:29.454 --> 19:44:29.464 align:start position:0% incident response policies bring your 19:44:29.464 --> 19:44:33.350 align:start position:0% incident response policies bring your own<19:44:29.640> device 19:44:33.350 --> 19:44:33.360 align:start position:0% 19:44:33.360 --> 19:44:35.814 align:start position:0% acceptable<19:44:34.256> use<19:44:34.552> policy<19:44:35.216> your 19:44:35.814 --> 19:44:35.824 align:start position:0% acceptable use policy your 19:44:35.824 --> 19:44:37.966 align:start position:0% acceptable use policy your non-disclosure<19:44:36.600> agreement 19:44:37.966 --> 19:44:37.976 align:start position:0% non-disclosure agreement 19:44:37.976 --> 19:44:41.630 align:start position:0% non-disclosure agreement uh<19:44:38.696> system<19:44:38.872> life<19:44:39.296> cycle<19:44:39.680> and<19:44:40.680> safety 19:44:41.630 --> 19:44:41.640 align:start position:0% uh system life cycle and safety 19:44:41.640 --> 19:44:44.454 align:start position:0% uh system life cycle and safety so<19:44:42.056> your<19:44:42.240> privileged<19:44:42.720> user<19:44:43.144> the<19:44:44.040> privileged 19:44:44.454 --> 19:44:44.464 align:start position:0% so your privileged user the privileged 19:44:44.464 --> 19:44:45.886 align:start position:0% so your privileged user the privileged users<19:44:44.760> are<19:44:44.936> people<19:44:45.120> you<19:44:45.536> could<19:44:45.600> call<19:44:45.784> them 19:44:45.886 --> 19:44:45.896 align:start position:0% users are people you could call them 19:44:45.896 --> 19:44:49.006 align:start position:0% users are people you could call them super<19:44:46.256> users<19:44:46.856> or<19:44:47.160> administrators<19:44:47.872> whatever 19:44:49.006 --> 19:44:49.016 align:start position:0% super users or administrators whatever 19:44:49.016 --> 19:44:51.774 align:start position:0% super users or administrators whatever this<19:44:50.104> um<19:44:50.104> agreement<19:44:50.872> should<19:44:51.240> be<19:44:51.360> signed<19:44:51.720> by 19:44:51.774 --> 19:44:51.784 align:start position:0% this um agreement should be signed by 19:44:51.784 --> 19:44:53.270 align:start position:0% this um agreement should be signed by administrators 19:44:53.270 --> 19:44:53.280 align:start position:0% administrators 19:44:53.280 --> 19:44:55.966 align:start position:0% administrators so<19:44:54.120> the<19:44:54.784> Crux<19:44:55.080> of<19:44:55.256> it<19:44:55.376> is<19:44:55.504> that<19:44:55.680> they<19:44:55.856> should 19:44:55.966 --> 19:44:55.976 align:start position:0% so the Crux of it is that they should 19:44:55.976 --> 19:44:58.070 align:start position:0% so the Crux of it is that they should only<19:44:56.104> be<19:44:56.216> using<19:44:56.464> the<19:44:56.640> networking<19:44:57.056> tools<19:44:57.480> for 19:44:58.070 --> 19:44:58.080 align:start position:0% only be using the networking tools for 19:44:58.080 --> 19:45:01.182 align:start position:0% only be using the networking tools for job<19:44:58.256> purposes<19:44:58.800> I<19:44:59.640> know<19:44:59.760> where<19:45:00.000> I<19:45:00.240> where<19:45:00.960> I 19:45:01.182 --> 19:45:01.192 align:start position:0% job purposes I know where I where I 19:45:01.192 --> 19:45:04.430 align:start position:0% job purposes I know where I where I worked<19:45:01.504> at<19:45:01.680> this<19:45:02.336> um<19:45:02.336> ISP<19:45:03.176> we<19:45:03.424> all<19:45:03.896> worked<19:45:04.192> in 19:45:04.430 --> 19:45:04.440 align:start position:0% worked at this um ISP we all worked in 19:45:04.440 --> 19:45:05.950 align:start position:0% worked at this um ISP we all worked in the<19:45:04.920> um 19:45:05.950 --> 19:45:05.960 align:start position:0% the um 19:45:05.960 --> 19:45:08.390 align:start position:0% the um the<19:45:06.960> admin<19:45:07.376> team<19:45:07.616> we<19:45:07.856> were<19:45:07.920> doing<19:45:08.104> the<19:45:08.280> network 19:45:08.390 --> 19:45:08.400 align:start position:0% the admin team we were doing the network 19:45:08.400 --> 19:45:10.734 align:start position:0% the admin team we were doing the network support<19:45:08.760> for<19:45:09.120> large<19:45:09.296> customers<19:45:09.832> and<19:45:10.552> then 19:45:10.734 --> 19:45:10.744 align:start position:0% support for large customers and then 19:45:10.744 --> 19:45:12.310 align:start position:0% support for large customers and then obviously<19:45:11.040> there<19:45:11.280> was<19:45:11.400> a<19:45:11.512> whole<19:45:11.696> bunch<19:45:11.936> of 19:45:12.310 --> 19:45:12.320 align:start position:0% obviously there was a whole bunch of 19:45:12.320 --> 19:45:15.526 align:start position:0% obviously there was a whole bunch of teams<19:45:13.320> under<19:45:13.616> us<19:45:13.976> here 19:45:15.526 --> 19:45:15.536 align:start position:0% teams under us here 19:45:15.536 --> 19:45:20.990 align:start position:0% teams under us here like<19:45:16.192> a<19:45:16.496> HR 19:45:20.990 --> 19:45:21.000 align:start position:0% 19:45:21.000 --> 19:45:24.110 align:start position:0% Finance<19:45:22.144> Etc<19:45:22.256> but<19:45:23.160> none<19:45:23.336> of<19:45:23.512> these<19:45:23.696> could<19:45:23.872> get 19:45:24.110 --> 19:45:24.120 align:start position:0% Finance Etc but none of these could get 19:45:24.120 --> 19:45:27.470 align:start position:0% Finance Etc but none of these could get out<19:45:24.296> to<19:45:24.720> their<19:45:25.192> social<19:45:25.504> media<19:45:26.040> this<19:45:27.000> is<19:45:27.240> say 19:45:27.470 --> 19:45:27.480 align:start position:0% out to their social media this is say 19:45:27.480 --> 19:45:29.814 align:start position:0% out to their social media this is say for<19:45:27.656> example<19:45:27.960> Facebook<19:45:28.376> that<19:45:29.160> was<19:45:29.336> blocked 19:45:29.814 --> 19:45:29.824 align:start position:0% for example Facebook that was blocked 19:45:29.824 --> 19:45:32.030 align:start position:0% for example Facebook that was blocked but<19:45:30.600> the<19:45:30.832> admin<19:45:31.144> team<19:45:31.320> they<19:45:31.552> could<19:45:31.800> obviously 19:45:32.030 --> 19:45:32.040 align:start position:0% but the admin team they could obviously 19:45:32.040 --> 19:45:33.710 align:start position:0% but the admin team they could obviously decide<19:45:32.400> what<19:45:32.760> went<19:45:33.000> in<19:45:33.176> and<19:45:33.296> out<19:45:33.480> of<19:45:33.600> the 19:45:33.710 --> 19:45:33.720 align:start position:0% decide what went in and out of the 19:45:33.720 --> 19:45:35.502 align:start position:0% decide what went in and out of the network<19:45:33.832> so<19:45:34.256> they<19:45:34.496> let<19:45:34.744> themselves<19:45:35.160> get<19:45:35.400> out 19:45:35.502 --> 19:45:35.512 align:start position:0% network so they let themselves get out 19:45:35.512 --> 19:45:39.590 align:start position:0% network so they let themselves get out on<19:45:35.760> Facebook<19:45:36.056> eBay<19:45:36.720> whatever<19:45:37.680> they<19:45:38.104> wanted<19:45:38.280> so 19:45:39.590 --> 19:45:39.600 align:start position:0% on Facebook eBay whatever they wanted so 19:45:39.600 --> 19:45:41.094 align:start position:0% on Facebook eBay whatever they wanted so um we<19:45:39.896> didn't<19:45:40.080> actually<19:45:40.376> have<19:45:40.680> a<19:45:40.856> user 19:45:41.094 --> 19:45:41.104 align:start position:0% um we didn't actually have a user 19:45:41.104 --> 19:45:42.710 align:start position:0% um we didn't actually have a user agreement<19:45:41.400> there<19:45:41.576> we<19:45:41.824> just<19:45:41.936> got<19:45:42.056> hired<19:45:42.480> and<19:45:42.600> we 19:45:42.710 --> 19:45:42.720 align:start position:0% agreement there we just got hired and we 19:45:42.720 --> 19:45:44.750 align:start position:0% agreement there we just got hired and we started<19:45:43.016> working<19:45:43.320> but<19:45:44.040> really<19:45:44.280> the<19:45:44.512> point<19:45:44.640> of 19:45:44.750 --> 19:45:44.760 align:start position:0% started working but really the point of 19:45:44.760 --> 19:45:46.134 align:start position:0% started working but really the point of a<19:45:44.872> user<19:45:45.056> agreement<19:45:45.360> is<19:45:45.600> you're<19:45:45.720> not<19:45:45.896> doing 19:45:46.134 --> 19:45:46.144 align:start position:0% a user agreement is you're not doing 19:45:46.144 --> 19:45:48.590 align:start position:0% a user agreement is you're not doing things<19:45:46.376> for<19:45:46.552> the<19:45:46.744> network<19:45:46.976> or<19:45:47.464> giving<19:45:47.760> people 19:45:48.590 --> 19:45:48.600 align:start position:0% things for the network or giving people 19:45:48.600 --> 19:45:50.454 align:start position:0% things for the network or giving people access<19:45:48.896> to<19:45:49.552> things<19:45:49.744> that<19:45:49.920> aren't<19:45:50.104> really<19:45:50.216> work 19:45:50.454 --> 19:45:50.464 align:start position:0% access to things that aren't really work 19:45:50.464 --> 19:45:51.710 align:start position:0% access to things that aren't really work related 19:45:51.710 --> 19:45:51.720 align:start position:0% related 19:45:51.720 --> 19:45:54.286 align:start position:0% related so<19:45:52.376> access<19:45:52.680> only<19:45:53.040> areas<19:45:53.576> that<19:45:53.760> are<19:45:53.872> under<19:45:54.056> your 19:45:54.286 --> 19:45:54.296 align:start position:0% so access only areas that are under your 19:45:54.296 --> 19:45:57.350 align:start position:0% so access only areas that are under your purview<19:45:54.856> so<19:45:55.856> as<19:45:55.976> the<19:45:56.216> administrator<19:45:56.696> you<19:45:57.000> may 19:45:57.350 --> 19:45:57.360 align:start position:0% purview so as the administrator you may 19:45:57.360 --> 19:45:59.326 align:start position:0% purview so as the administrator you may or<19:45:57.600> may<19:45:57.832> not<19:45:58.016> be<19:45:58.144> able<19:45:58.320> to<19:45:58.440> configure<19:45:58.856> ways<19:45:59.280> of 19:45:59.326 --> 19:45:59.336 align:start position:0% or may not be able to configure ways of 19:45:59.336 --> 19:46:01.182 align:start position:0% or may not be able to configure ways of you<19:45:59.512> getting<19:45:59.824> into<19:46:00.120> firewalls<19:46:00.832> and<19:46:01.016> other 19:46:01.182 --> 19:46:01.192 align:start position:0% you getting into firewalls and other 19:46:01.192 --> 19:46:03.470 align:start position:0% you getting into firewalls and other devices<19:46:01.680> that<19:46:02.040> you<19:46:02.160> might<19:46:02.336> not<19:46:02.464> manage<19:46:02.824> but 19:46:03.470 --> 19:46:03.480 align:start position:0% devices that you might not manage but 19:46:03.480 --> 19:46:05.094 align:start position:0% devices that you might not manage but the<19:46:03.720> agreement<19:46:04.080> that<19:46:04.320> you've<19:46:04.552> signed<19:46:04.920> should 19:46:05.094 --> 19:46:05.104 align:start position:0% the agreement that you've signed should 19:46:05.104 --> 19:46:06.950 align:start position:0% the agreement that you've signed should prevent<19:46:05.576> you<19:46:05.696> from<19:46:05.872> doing<19:46:06.056> that 19:46:06.950 --> 19:46:06.960 align:start position:0% prevent you from doing that 19:46:06.960 --> 19:46:09.822 align:start position:0% prevent you from doing that user<19:46:07.744> accounts<19:46:08.216> only<19:46:08.512> changed<19:46:09.120> under<19:46:09.424> company 19:46:09.822 --> 19:46:09.832 align:start position:0% user accounts only changed under company 19:46:09.832 --> 19:46:13.182 align:start position:0% user accounts only changed under company policy<19:46:10.552> and<19:46:10.744> with<19:46:10.976> correct<19:46:11.480> authorization<19:46:12.480> so 19:46:13.182 --> 19:46:13.192 align:start position:0% policy and with correct authorization so 19:46:13.192 --> 19:46:14.750 align:start position:0% policy and with correct authorization so this<19:46:13.376> would<19:46:13.504> be<19:46:13.680> something<19:46:13.856> like<19:46:14.160> a<19:46:14.400> friend<19:46:14.512> of 19:46:14.750 --> 19:46:14.760 align:start position:0% this would be something like a friend of 19:46:14.760 --> 19:46:17.750 align:start position:0% this would be something like a friend of yours<19:46:15.120> that's<19:46:15.360> asked<19:46:15.832> to<19:46:16.552> to<19:46:16.800> get<19:46:16.976> out<19:46:17.216> on<19:46:17.512> some 19:46:17.750 --> 19:46:17.760 align:start position:0% yours that's asked to to get out on some 19:46:17.760 --> 19:46:20.502 align:start position:0% yours that's asked to to get out on some device<19:46:18.000> or<19:46:18.424> they're<19:46:18.600> asking<19:46:18.896> if<19:46:19.080> they<19:46:19.256> can<19:46:19.512> and 19:46:20.502 --> 19:46:20.512 align:start position:0% device or they're asking if they can and 19:46:20.512 --> 19:46:22.246 align:start position:0% device or they're asking if they can and access<19:46:20.872> their<19:46:21.176> emails<19:46:21.600> from<19:46:21.832> their<19:46:22.016> home 19:46:22.246 --> 19:46:22.256 align:start position:0% access their emails from their home 19:46:22.256 --> 19:46:24.774 align:start position:0% access their emails from their home computer<19:46:22.824> these<19:46:23.824> things<19:46:24.000> that<19:46:24.360> you<19:46:24.536> might<19:46:24.656> be 19:46:24.774 --> 19:46:24.784 align:start position:0% computer these things that you might be 19:46:24.784 --> 19:46:26.502 align:start position:0% computer these things that you might be asked<19:46:25.016> to<19:46:25.144> do<19:46:25.256> but<19:46:25.504> you<19:46:25.680> you<19:46:25.920> shouldn't<19:46:26.336> be 19:46:26.502 --> 19:46:26.512 align:start position:0% asked to do but you you shouldn't be 19:46:26.512 --> 19:46:28.070 align:start position:0% asked to do but you you shouldn't be allowed<19:46:27.056> to<19:46:27.176> do 19:46:28.070 --> 19:46:28.080 align:start position:0% allowed to do 19:46:28.080 --> 19:46:31.182 align:start position:0% allowed to do your<19:46:28.552> password<19:46:28.856> policy<19:46:29.576> uh<19:46:30.296> I've<19:46:30.600> actually 19:46:31.182 --> 19:46:31.192 align:start position:0% your password policy uh I've actually 19:46:31.192 --> 19:46:32.454 align:start position:0% your password policy uh I've actually seen<19:46:31.504> a<19:46:31.744> few 19:46:32.454 --> 19:46:32.464 align:start position:0% seen a few 19:46:32.464 --> 19:46:34.966 align:start position:0% seen a few um News<19:46:32.872> interviews<19:46:33.536> especially<19:46:34.496> in<19:46:34.680> the 19:46:34.966 --> 19:46:34.976 align:start position:0% um News interviews especially in the 19:46:34.976 --> 19:46:36.710 align:start position:0% um News interviews especially in the last<19:46:35.216> couple<19:46:35.464> of<19:46:35.640> years 19:46:36.710 --> 19:46:36.720 align:start position:0% last couple of years 19:46:36.720 --> 19:46:39.046 align:start position:0% last couple of years of<19:46:37.320> people<19:46:37.680> giving<19:46:37.920> interviews<19:46:38.576> when<19:46:38.872> they're 19:46:39.046 --> 19:46:39.056 align:start position:0% of people giving interviews when they're 19:46:39.056 --> 19:46:41.094 align:start position:0% of people giving interviews when they're at<19:46:39.176> work<19:46:39.360> and<19:46:39.536> you<19:46:39.720> can<19:46:39.832> actually<19:46:40.016> see<19:46:40.496> a 19:46:41.094 --> 19:46:41.104 align:start position:0% at work and you can actually see a 19:46:41.104 --> 19:46:43.790 align:start position:0% at work and you can actually see a Post-It<19:46:41.512> note<19:46:41.760> on<19:46:42.656> their<19:46:42.832> monitor<19:46:43.256> yeah 19:46:43.790 --> 19:46:43.800 align:start position:0% Post-It note on their monitor yeah 19:46:43.800 --> 19:46:46.486 align:start position:0% Post-It note on their monitor yeah saying<19:46:44.336> what<19:46:44.464> their<19:46:44.640> password<19:46:44.824> is 19:46:46.486 --> 19:46:46.496 align:start position:0% saying what their password is 19:46:46.496 --> 19:46:49.246 align:start position:0% saying what their password is so<19:46:46.856> this<19:46:46.976> is<19:46:47.104> obviously<19:46:47.400> a<19:46:47.576> big<19:46:47.640> No-No<19:46:48.240> some<19:46:49.144> of 19:46:49.246 --> 19:46:49.256 align:start position:0% so this is obviously a big No-No some of 19:46:49.256 --> 19:46:51.166 align:start position:0% so this is obviously a big No-No some of the<19:46:49.376> things<19:46:49.616> that<19:46:50.104> you<19:46:50.576> maybe<19:46:50.760> maybe 19:46:51.166 --> 19:46:51.176 align:start position:0% the things that you maybe maybe 19:46:51.176 --> 19:46:53.814 align:start position:0% the things that you maybe maybe implemented<19:46:51.832> are<19:46:52.016> they're<19:46:52.320> no<19:46:52.496> reuse<19:46:52.976> or 19:46:53.814 --> 19:46:53.824 align:start position:0% implemented are they're no reuse or 19:46:53.824 --> 19:46:56.926 align:start position:0% implemented are they're no reuse or changing<19:46:54.240> the<19:46:54.480> last<19:46:54.600> character<19:46:55.280> such<19:46:56.280> as<19:46:56.400> a<19:46:56.640> if 19:46:56.926 --> 19:46:56.936 align:start position:0% changing the last character such as a if 19:46:56.936 --> 19:47:02.270 align:start position:0% changing the last character such as a if your<19:46:57.056> password<19:46:57.240> is<19:46:57.744> a<19:46:58.744> b<19:46:58.920> c<19:46:59.216> d<19:46:59.760> e<19:47:00.056> f<19:47:00.600> g<19:47:00.960> one<19:47:01.376> you 19:47:02.270 --> 19:47:02.280 align:start position:0% your password is a b c d e f g one you 19:47:02.280 --> 19:47:04.070 align:start position:0% your password is a b c d e f g one you wouldn't<19:47:02.400> be<19:47:02.576> allowed<19:47:02.936> to<19:47:03.056> change<19:47:03.360> it<19:47:03.600> to<19:47:03.832> all 19:47:04.070 --> 19:47:04.080 align:start position:0% wouldn't be allowed to change it to all 19:47:04.080 --> 19:47:06.166 align:start position:0% wouldn't be allowed to change it to all be<19:47:04.256> the<19:47:04.496> same<19:47:04.616> and<19:47:04.856> then<19:47:05.040> two<19:47:05.160> on<19:47:05.400> the<19:47:05.576> end 19:47:06.166 --> 19:47:06.176 align:start position:0% be the same and then two on the end 19:47:06.176 --> 19:47:08.990 align:start position:0% be the same and then two on the end obviously<19:47:06.896> for<19:47:07.016> the<19:47:07.192> work<19:47:07.376> Network 19:47:08.990 --> 19:47:09.000 align:start position:0% obviously for the work Network 19:47:09.000 --> 19:47:11.862 align:start position:0% obviously for the work Network no<19:47:09.424> writing<19:47:09.832> on<19:47:10.016> Post-it<19:47:10.376> notes<19:47:10.920> expiry 19:47:11.862 --> 19:47:11.872 align:start position:0% no writing on Post-it notes expiry 19:47:11.872 --> 19:47:13.734 align:start position:0% no writing on Post-it notes expiry length<19:47:12.240> again<19:47:12.360> this<19:47:12.720> is<19:47:12.832> all<19:47:13.080> a<19:47:13.320> pain<19:47:13.504> because 19:47:13.734 --> 19:47:13.744 align:start position:0% length again this is all a pain because 19:47:13.744 --> 19:47:15.166 align:start position:0% length again this is all a pain because people<19:47:14.040> are<19:47:14.216> going<19:47:14.336> to<19:47:14.464> be<19:47:14.512> forgetting<19:47:15.000> their 19:47:15.166 --> 19:47:15.176 align:start position:0% people are going to be forgetting their 19:47:15.176 --> 19:47:17.326 align:start position:0% people are going to be forgetting their passwords<19:47:15.656> and<19:47:15.832> logging<19:47:16.192> tickets<19:47:16.376> it<19:47:17.216> just 19:47:17.326 --> 19:47:17.336 align:start position:0% passwords and logging tickets it just 19:47:17.336 --> 19:47:19.910 align:start position:0% passwords and logging tickets it just depends<19:47:17.640> how<19:47:17.824> secure<19:47:18.176> your<19:47:18.360> environment<19:47:18.832> is 19:47:19.910 --> 19:47:19.920 align:start position:0% depends how secure your environment is 19:47:19.920 --> 19:47:22.542 align:start position:0% depends how secure your environment is upper<19:47:20.696> lower<19:47:20.936> case<19:47:21.240> is<19:47:21.480> pretty<19:47:21.784> common<19:47:22.080> plus 19:47:22.542 --> 19:47:22.552 align:start position:0% upper lower case is pretty common plus 19:47:22.552 --> 19:47:25.150 align:start position:0% upper lower case is pretty common plus special<19:47:22.920> characters<19:47:23.280> and<19:47:23.760> numbers 19:47:25.150 --> 19:47:25.160 align:start position:0% special characters and numbers 19:47:25.160 --> 19:47:28.670 align:start position:0% special characters and numbers non-dictionary<19:47:26.160> words<19:47:26.824> so<19:47:27.600> again<19:47:28.080> you<19:47:28.496> could 19:47:28.670 --> 19:47:28.680 align:start position:0% non-dictionary words so again you could 19:47:28.680 --> 19:47:30.774 align:start position:0% non-dictionary words so again you could be<19:47:29.336> just<19:47:29.696> looking<19:47:29.872> at 19:47:30.774 --> 19:47:30.784 align:start position:0% be just looking at 19:47:30.784 --> 19:47:32.454 align:start position:0% be just looking at and<19:47:31.144> people<19:47:31.376> choose<19:47:31.800> things<19:47:32.040> they're<19:47:32.280> going 19:47:32.454 --> 19:47:32.464 align:start position:0% and people choose things they're going 19:47:32.464 --> 19:47:37.606 align:start position:0% and people choose things they're going to<19:47:32.640> remember<19:47:32.760> like<19:47:33.656> um 19:47:37.606 --> 19:47:37.616 align:start position:0% 19:47:37.616 --> 19:47:39.646 align:start position:0% I<19:47:38.104> think<19:47:38.280> there's<19:47:38.400> only<19:47:38.512> one<19:47:38.760> Ellen<19:47:39.176> Bloom<19:47:39.536> but 19:47:39.646 --> 19:47:39.656 align:start position:0% I think there's only one Ellen Bloom but 19:47:39.656 --> 19:47:42.646 align:start position:0% I think there's only one Ellen Bloom but you<19:47:39.720> know<19:47:39.832> what<19:47:39.896> I<19:47:40.016> mean<19:47:40.192> balloon<19:47:41.000> kite<19:47:42.000> teacup 19:47:42.646 --> 19:47:42.656 align:start position:0% you know what I mean balloon kite teacup 19:47:42.656 --> 19:47:45.230 align:start position:0% you know what I mean balloon kite teacup all<19:47:43.376> these<19:47:43.616> kind<19:47:43.744> of<19:47:43.856> things<19:47:44.056> are<19:47:45.056> they 19:47:45.230 --> 19:47:45.240 align:start position:0% all these kind of things are they 19:47:45.240 --> 19:47:46.606 align:start position:0% all these kind of things are they allowed<19:47:45.480> to<19:47:45.536> use<19:47:45.656> passive<19:47:46.080> password 19:47:46.606 --> 19:47:46.616 align:start position:0% allowed to use passive password 19:47:46.616 --> 19:47:49.070 align:start position:0% allowed to use passive password management<19:47:47.040> software<19:47:47.576> I've<19:47:48.360> got<19:47:48.656> password 19:47:49.070 --> 19:47:49.080 align:start position:0% management software I've got password 19:47:49.080 --> 19:47:53.206 align:start position:0% management software I've got password management<19:47:49.504> because<19:47:49.920> I've<19:47:50.280> got<19:47:50.784> maybe<19:47:52.216> 150 19:47:53.206 --> 19:47:53.216 align:start position:0% management because I've got maybe 150 19:47:53.216 --> 19:47:56.686 align:start position:0% management because I've got maybe 150 different<19:47:53.512> types<19:47:54.480> of<19:47:54.656> software<19:47:55.552> and<19:47:56.464> service 19:47:56.686 --> 19:47:56.696 align:start position:0% different types of software and service 19:47:56.696 --> 19:47:59.862 align:start position:0% different types of software and service I<19:47:57.176> use<19:47:57.424> I've<19:47:57.896> managed<19:47:58.376> about<19:47:58.512> I've<19:47:59.512> got<19:47:59.760> about 19:47:59.862 --> 19:47:59.872 align:start position:0% I use I've managed about I've got about 19:47:59.872 --> 19:48:03.350 align:start position:0% I use I've managed about I've got about 14<19:48:00.424> 15<19:48:00.784> websites<19:48:01.680> some<19:48:02.336> I'm<19:48:02.576> on<19:48:02.760> every<19:48:02.936> day<19:48:03.120> and 19:48:03.350 --> 19:48:03.360 align:start position:0% 14 15 websites some I'm on every day and 19:48:03.360 --> 19:48:06.166 align:start position:0% 14 15 websites some I'm on every day and some<19:48:03.480> I<19:48:03.720> only<19:48:03.784> check<19:48:04.016> in<19:48:04.256> once<19:48:04.552> a<19:48:04.680> year<19:48:04.800> maybe 19:48:06.166 --> 19:48:06.176 align:start position:0% some I only check in once a year maybe 19:48:06.176 --> 19:48:08.326 align:start position:0% some I only check in once a year maybe but<19:48:06.784> I<19:48:07.016> mean<19:48:07.144> just<19:48:07.320> to<19:48:07.440> try<19:48:07.552> to<19:48:07.680> imagine<19:48:07.856> you 19:48:08.326 --> 19:48:08.336 align:start position:0% but I mean just to try to imagine you 19:48:08.336 --> 19:48:09.710 align:start position:0% but I mean just to try to imagine you can't<19:48:08.400> have<19:48:08.576> the<19:48:08.760> same<19:48:08.872> password<19:48:09.120> for<19:48:09.480> all<19:48:09.600> of 19:48:09.710 --> 19:48:09.720 align:start position:0% can't have the same password for all of 19:48:09.720 --> 19:48:11.566 align:start position:0% can't have the same password for all of these<19:48:09.896> or<19:48:10.080> you<19:48:10.256> shouldn't<19:48:10.552> so<19:48:10.920> try<19:48:11.160> to<19:48:11.280> manage 19:48:11.566 --> 19:48:11.576 align:start position:0% these or you shouldn't so try to manage 19:48:11.576 --> 19:48:13.846 align:start position:0% these or you shouldn't so try to manage them<19:48:11.824> this<19:48:12.000> is<19:48:12.120> a<19:48:12.240> bit<19:48:12.296> too<19:48:12.480> difficult<19:48:12.832> it's<19:48:13.680> a 19:48:13.846 --> 19:48:13.856 align:start position:0% them this is a bit too difficult it's a 19:48:13.856 --> 19:48:15.950 align:start position:0% them this is a bit too difficult it's a robo<19:48:14.280> form<19:48:14.576> I<19:48:14.824> think<19:48:15.000> it's<19:48:15.120> called 19:48:15.950 --> 19:48:15.960 align:start position:0% robo form I think it's called 19:48:15.960 --> 19:48:18.414 align:start position:0% robo form I think it's called on<19:48:16.496> off-boarding<19:48:17.216> so<19:48:17.400> policy<19:48:17.872> for<19:48:18.056> hiring 19:48:18.414 --> 19:48:18.424 align:start position:0% on off-boarding so policy for hiring 19:48:18.424 --> 19:48:20.862 align:start position:0% on off-boarding so policy for hiring people<19:48:18.720> and<19:48:19.144> then<19:48:19.320> terminating<19:48:19.856> this<19:48:20.696> should 19:48:20.862 --> 19:48:20.872 align:start position:0% people and then terminating this should 19:48:20.872 --> 19:48:22.910 align:start position:0% people and then terminating this should obviously<19:48:21.296> go<19:48:21.480> through<19:48:21.600> the<19:48:21.784> HR<19:48:22.256> team<19:48:22.440> as<19:48:22.744> well 19:48:22.910 --> 19:48:22.920 align:start position:0% obviously go through the HR team as well 19:48:22.920 --> 19:48:24.822 align:start position:0% obviously go through the HR team as well because<19:48:23.576> the<19:48:23.872> chances<19:48:24.240> are<19:48:24.360> if<19:48:24.480> it's<19:48:24.656> a<19:48:24.720> big 19:48:24.822 --> 19:48:24.832 align:start position:0% because the chances are if it's a big 19:48:24.832 --> 19:48:26.990 align:start position:0% because the chances are if it's a big company<19:48:25.016> you<19:48:25.376> may<19:48:25.552> not<19:48:25.744> know<19:48:26.040> who's<19:48:26.696> coming 19:48:26.990 --> 19:48:27.000 align:start position:0% company you may not know who's coming 19:48:27.000 --> 19:48:29.454 align:start position:0% company you may not know who's coming who's<19:48:27.424> gone<19:48:27.720> and<19:48:28.016> and<19:48:28.616> obviously<19:48:28.976> sometimes 19:48:29.454 --> 19:48:29.464 align:start position:0% who's gone and and obviously sometimes 19:48:29.464 --> 19:48:31.846 align:start position:0% who's gone and and obviously sometimes people<19:48:29.760> will<19:48:30.056> give<19:48:30.296> notice 19:48:31.846 --> 19:48:31.856 align:start position:0% people will give notice 19:48:31.856 --> 19:48:35.150 align:start position:0% people will give notice and<19:48:32.464> they're<19:48:33.056> for<19:48:33.960> um<19:48:33.960> privacy<19:48:34.680> or<19:48:34.976> whatever 19:48:35.150 --> 19:48:35.160 align:start position:0% and they're for um privacy or whatever 19:48:35.160 --> 19:48:37.910 align:start position:0% and they're for um privacy or whatever other<19:48:35.464> reasons<19:48:36.256> uh<19:48:37.256> they're<19:48:37.440> not<19:48:37.552> allowed<19:48:37.800> to 19:48:37.910 --> 19:48:37.920 align:start position:0% other reasons uh they're not allowed to 19:48:37.920 --> 19:48:39.526 align:start position:0% other reasons uh they're not allowed to work<19:48:38.104> at<19:48:38.336> the<19:48:38.512> company<19:48:38.696> anymore<19:48:38.936> they're 19:48:39.526 --> 19:48:39.536 align:start position:0% work at the company anymore they're 19:48:39.536 --> 19:48:41.206 align:start position:0% work at the company anymore they're basically<19:48:39.896> in<19:48:40.320> in<19:48:40.552> the<19:48:40.744> UK<19:48:40.920> it's<19:48:41.040> called 19:48:41.206 --> 19:48:41.216 align:start position:0% basically in in the UK it's called 19:48:41.216 --> 19:48:43.310 align:start position:0% basically in in the UK it's called gardening<19:48:41.824> leave<19:48:42.000> they're<19:48:42.784> told<19:48:43.016> to<19:48:43.192> leave 19:48:43.310 --> 19:48:43.320 align:start position:0% gardening leave they're told to leave 19:48:43.320 --> 19:48:45.230 align:start position:0% gardening leave they're told to leave immediately<19:48:43.800> but<19:48:44.464> they're<19:48:44.640> paid<19:48:44.872> for<19:48:45.056> the 19:48:45.230 --> 19:48:45.240 align:start position:0% immediately but they're paid for the 19:48:45.240 --> 19:48:47.030 align:start position:0% immediately but they're paid for the rest<19:48:45.360> of<19:48:45.600> their<19:48:45.832> contract 19:48:47.030 --> 19:48:47.040 align:start position:0% rest of their contract 19:48:47.040 --> 19:48:49.006 align:start position:0% rest of their contract what<19:48:47.576> access<19:48:47.824> and<19:48:48.056> privilege<19:48:48.480> levels<19:48:48.784> they're 19:48:49.006 --> 19:48:49.016 align:start position:0% what access and privilege levels they're 19:48:49.016 --> 19:48:51.166 align:start position:0% what access and privilege levels they're given<19:48:49.320> and<19:48:50.216> when<19:48:50.464> are<19:48:50.576> they<19:48:50.696> given<19:48:50.936> email 19:48:51.166 --> 19:48:51.176 align:start position:0% given and when are they given email 19:48:51.176 --> 19:48:53.814 align:start position:0% given and when are they given email access<19:48:51.656> and<19:48:52.376> access<19:48:52.856> to<19:48:53.104> Shared<19:48:53.464> directories 19:48:53.814 --> 19:48:53.824 align:start position:0% access and access to Shared directories 19:48:53.824 --> 19:48:55.910 align:start position:0% access and access to Shared directories and<19:48:54.056> files<19:48:54.424> are<19:48:55.080> they<19:48:55.256> given<19:48:55.504> best<19:48:55.680> practice 19:48:55.910 --> 19:48:55.920 align:start position:0% and files are they given best practice 19:48:55.920 --> 19:48:58.606 align:start position:0% and files are they given best practice training<19:48:56.576> this<19:48:57.240> is<19:48:57.360> normally 19:48:58.606 --> 19:48:58.616 align:start position:0% training this is normally 19:48:58.616 --> 19:49:01.494 align:start position:0% training this is normally um<19:48:58.680> in<19:48:58.976> the<19:48:59.104> form<19:48:59.280> of<19:48:59.464> CBT<19:49:00.360> and<19:49:01.080> then<19:49:01.192> they<19:49:01.376> get 19:49:01.494 --> 19:49:01.504 align:start position:0% um in the form of CBT and then they get 19:49:01.504 --> 19:49:03.886 align:start position:0% um in the form of CBT and then they get a<19:49:01.680> certificate<19:49:02.216> maybe<19:49:02.576> and<19:49:03.296> then<19:49:03.424> that<19:49:03.600> goes 19:49:03.886 --> 19:49:03.896 align:start position:0% a certificate maybe and then that goes 19:49:03.896 --> 19:49:06.166 align:start position:0% a certificate maybe and then that goes off<19:49:03.960> to<19:49:04.192> the<19:49:04.376> manager<19:49:04.976> for<19:49:05.216> filing 19:49:06.166 --> 19:49:06.176 align:start position:0% off to the manager for filing 19:49:06.176 --> 19:49:08.390 align:start position:0% off to the manager for filing just<19:49:06.656> to<19:49:06.832> prove<19:49:07.192> they've<19:49:07.920> been<19:49:08.040> shown<19:49:08.216> what 19:49:08.390 --> 19:49:08.400 align:start position:0% just to prove they've been shown what 19:49:08.400 --> 19:49:10.430 align:start position:0% just to prove they've been shown what they<19:49:08.576> should<19:49:08.760> and<19:49:08.872> shouldn't<19:49:09.240> do<19:49:09.360> do<19:49:10.016> they<19:49:10.256> get 19:49:10.430 --> 19:49:10.440 align:start position:0% they should and shouldn't do do they get 19:49:10.440 --> 19:49:12.470 align:start position:0% they should and shouldn't do do they get a<19:49:10.616> smartphone<19:49:11.040> another<19:49:11.696> what<19:49:12.296> are<19:49:12.360> they 19:49:12.470 --> 19:49:12.480 align:start position:0% a smartphone another what are they 19:49:12.480 --> 19:49:14.990 align:start position:0% a smartphone another what are they allowed<19:49:12.656> to<19:49:12.720> use<19:49:12.832> this<19:49:13.016> Smartphone<19:49:13.440> for 19:49:14.990 --> 19:49:15.000 align:start position:0% allowed to use this Smartphone for 19:49:15.000 --> 19:49:17.686 align:start position:0% allowed to use this Smartphone for uh<19:49:15.720> licensing<19:49:16.320> use<19:49:16.920> of<19:49:17.160> corporate<19:49:17.512> hardware 19:49:17.686 --> 19:49:17.696 align:start position:0% uh licensing use of corporate hardware 19:49:17.696 --> 19:49:19.790 align:start position:0% uh licensing use of corporate hardware and<19:49:18.056> software<19:49:18.480> and<19:49:18.960> I<19:49:19.144> remember<19:49:19.320> when<19:49:19.552> I 19:49:19.790 --> 19:49:19.800 align:start position:0% and software and I remember when I 19:49:19.800 --> 19:49:22.246 align:start position:0% and software and I remember when I worked<19:49:20.104> at<19:49:20.216> a<19:49:20.400> large<19:49:20.576> company<19:49:20.824> I<19:49:21.120> won't<19:49:21.360> say<19:49:21.600> uh 19:49:22.246 --> 19:49:22.256 align:start position:0% worked at a large company I won't say uh 19:49:22.256 --> 19:49:24.350 align:start position:0% worked at a large company I won't say uh who<19:49:22.440> they<19:49:23.216> had 19:49:24.350 --> 19:49:24.360 align:start position:0% who they had 19:49:24.360 --> 19:49:26.630 align:start position:0% who they had um<19:49:24.424> they<19:49:25.080> had<19:49:25.192> a<19:49:25.376> few<19:49:25.552> servers<19:49:26.160> that<19:49:26.400> we<19:49:26.512> could 19:49:26.630 --> 19:49:26.640 align:start position:0% um they had a few servers that we could 19:49:26.640 --> 19:49:28.910 align:start position:0% um they had a few servers that we could use<19:49:26.824> for<19:49:27.056> internal<19:49:27.480> files<19:49:27.832> but<19:49:28.440> people<19:49:28.616> would 19:49:28.910 --> 19:49:28.920 align:start position:0% use for internal files but people would 19:49:28.920 --> 19:49:34.966 align:start position:0% use for internal files but people would download<19:49:29.216> it<19:49:30.000> was<19:49:30.240> cracked<19:49:31.080> software 19:49:34.966 --> 19:49:34.976 align:start position:0% 19:49:34.976 --> 19:49:37.990 align:start position:0% crack<19:49:35.576> software<19:49:36.120> and<19:49:36.480> it<19:49:36.656> was<19:49:36.784> video<19:49:37.080> videos 19:49:37.990 --> 19:49:38.000 align:start position:0% crack software and it was video videos 19:49:38.000 --> 19:49:40.134 align:start position:0% crack software and it was video videos exams<19:49:39.000> and<19:49:39.176> a<19:49:39.360> whole<19:49:39.424> bunch<19:49:39.600> of<19:49:39.720> other<19:49:39.832> stuff 19:49:40.134 --> 19:49:40.144 align:start position:0% exams and a whole bunch of other stuff 19:49:40.144 --> 19:49:42.166 align:start position:0% exams and a whole bunch of other stuff that<19:49:40.856> technically<19:49:41.160> should<19:49:41.512> have<19:49:41.696> been<19:49:41.824> paid 19:49:42.166 --> 19:49:42.176 align:start position:0% that technically should have been paid 19:49:42.176 --> 19:49:45.774 align:start position:0% that technically should have been paid for<19:49:42.360> with<19:49:43.680> um<19:49:43.680> hard-earned<19:49:44.576> dollars<19:49:44.936> but<19:49:45.784> um 19:49:45.774 --> 19:49:45.784 align:start position:0% for with um hard-earned dollars but um 19:49:45.784 --> 19:49:48.886 align:start position:0% for with um hard-earned dollars but um it<19:49:46.016> was<19:49:46.144> all<19:49:46.256> put<19:49:46.376> on<19:49:46.496> there<19:49:46.680> for<19:49:46.920> free<19:49:47.104> now 19:49:48.886 --> 19:49:48.896 align:start position:0% it was all put on there for free now 19:49:48.896 --> 19:49:51.166 align:start position:0% it was all put on there for free now the<19:49:49.744> um<19:49:49.744> I'm<19:49:50.336> sure<19:49:50.464> the<19:49:50.640> man<19:49:50.760> at<19:49:50.936> the<19:49:51.120> top 19:49:51.166 --> 19:49:51.176 align:start position:0% the um I'm sure the man at the top 19:49:51.176 --> 19:49:52.966 align:start position:0% the um I'm sure the man at the top managers<19:49:51.656> didn't<19:49:51.832> know<19:49:52.080> but<19:49:52.320> some<19:49:52.496> managers 19:49:52.966 --> 19:49:52.976 align:start position:0% managers didn't know but some managers 19:49:52.976 --> 19:49:54.822 align:start position:0% managers didn't know but some managers knew<19:49:53.216> what<19:49:53.336> was<19:49:53.464> going<19:49:53.640> on<19:49:53.872> and<19:49:54.424> this<19:49:54.536> is<19:49:54.720> going 19:49:54.822 --> 19:49:54.832 align:start position:0% knew what was going on and this is going 19:49:54.832 --> 19:49:57.350 align:start position:0% knew what was going on and this is going to<19:49:54.960> leave<19:49:55.080> your<19:49:55.320> your<19:49:55.680> company<19:49:55.920> uh<19:49:56.336> legally<19:49:56.760> a 19:49:57.350 --> 19:49:57.360 align:start position:0% to leave your your company uh legally a 19:49:57.360 --> 19:50:00.310 align:start position:0% to leave your your company uh legally a light<19:49:57.536> bulb<19:49:58.320> download<19:49:58.800> and<19:49:59.160> sharing<19:49:59.576> policy 19:50:00.310 --> 19:50:00.320 align:start position:0% light bulb download and sharing policy 19:50:00.320 --> 19:50:02.326 align:start position:0% light bulb download and sharing policy training<19:50:01.320> with<19:50:01.440> a<19:50:01.616> sign<19:50:01.800> off<19:50:01.976> which<19:50:02.216> I've 19:50:02.326 --> 19:50:02.336 align:start position:0% training with a sign off which I've 19:50:02.336 --> 19:50:04.326 align:start position:0% training with a sign off which I've already<19:50:02.464> mentioned<19:50:02.936> mentioned<19:50:03.600> could<19:50:03.960> be 19:50:04.326 --> 19:50:04.336 align:start position:0% already mentioned mentioned could be 19:50:04.336 --> 19:50:07.006 align:start position:0% already mentioned mentioned could be computer-based<19:50:05.336> training<19:50:05.696> end<19:50:06.480> of<19:50:06.656> training 19:50:07.006 --> 19:50:07.016 align:start position:0% computer-based training end of training 19:50:07.016 --> 19:50:09.166 align:start position:0% computer-based training end of training exam<19:50:07.440> I<19:50:07.976> had<19:50:08.160> to<19:50:08.336> do<19:50:08.464> all<19:50:08.696> sorts<19:50:09.000> of<19:50:09.000> things 19:50:09.166 --> 19:50:09.176 align:start position:0% exam I had to do all sorts of things 19:50:09.176 --> 19:50:11.774 align:start position:0% exam I had to do all sorts of things health<19:50:09.600> and<19:50:09.832> safety<19:50:10.320> and<19:50:10.744> harassment 19:50:11.774 --> 19:50:11.784 align:start position:0% health and safety and harassment 19:50:11.784 --> 19:50:13.846 align:start position:0% health and safety and harassment all<19:50:12.784> this<19:50:12.960> kind<19:50:13.080> of<19:50:13.144> stuff<19:50:13.320> when<19:50:13.504> I<19:50:13.616> worked 19:50:13.846 --> 19:50:13.856 align:start position:0% all this kind of stuff when I worked 19:50:13.856 --> 19:50:16.734 align:start position:0% all this kind of stuff when I worked even<19:50:13.976> when<19:50:14.160> I<19:50:14.336> was<19:50:14.400> a<19:50:14.512> contractor 19:50:16.734 --> 19:50:16.744 align:start position:0% even when I was a contractor 19:50:16.744 --> 19:50:19.606 align:start position:0% even when I was a contractor International<19:50:17.400> export<19:50:18.256> certainly<19:50:19.256> in<19:50:19.440> terms 19:50:19.606 --> 19:50:19.616 align:start position:0% International export certainly in terms 19:50:19.616 --> 19:50:22.006 align:start position:0% International export certainly in terms of<19:50:19.680> hardware<19:50:19.976> and<19:50:20.280> software<19:50:20.696> say<19:50:21.424> for<19:50:21.656> example 19:50:22.006 --> 19:50:22.016 align:start position:0% of hardware and software say for example 19:50:22.016 --> 19:50:24.166 align:start position:0% of hardware and software say for example the<19:50:22.976> USA 19:50:24.166 --> 19:50:24.176 align:start position:0% the USA 19:50:24.176 --> 19:50:28.070 align:start position:0% the USA when<19:50:24.784> they<19:50:24.960> developed<19:50:25.440> the<19:50:25.976> um<19:50:25.976> GPS<19:50:26.400> software 19:50:28.070 --> 19:50:28.080 align:start position:0% when they developed the um GPS software 19:50:28.080 --> 19:50:30.646 align:start position:0% when they developed the um GPS software the<19:50:28.800> it<19:50:29.040> was<19:50:29.216> only<19:50:29.400> allowed<19:50:29.824> a<19:50:30.000> thing<19:50:30.176> within 19:50:30.646 --> 19:50:30.656 align:start position:0% the it was only allowed a thing within 19:50:30.656 --> 19:50:33.774 align:start position:0% the it was only allowed a thing within something<19:50:30.960> like<19:50:31.320> 100<19:50:31.680> meters<19:50:32.400> accuracy<19:50:33.120> the 19:50:33.774 --> 19:50:33.784 align:start position:0% something like 100 meters accuracy the 19:50:33.784 --> 19:50:35.630 align:start position:0% something like 100 meters accuracy the soft<19:50:33.896> the<19:50:34.192> software<19:50:34.552> you<19:50:34.800> they<19:50:35.040> could<19:50:35.216> drop<19:50:35.400> a 19:50:35.630 --> 19:50:35.640 align:start position:0% soft the software you they could drop a 19:50:35.640 --> 19:50:38.814 align:start position:0% soft the software you they could drop a bomb<19:50:35.896> then<19:50:36.896> within<19:50:37.856> a<19:50:37.976> window<19:50:38.104> of<19:50:38.336> a<19:50:38.464> moving 19:50:38.814 --> 19:50:38.824 align:start position:0% bomb then within a window of a moving 19:50:38.824 --> 19:50:40.734 align:start position:0% bomb then within a window of a moving car 19:50:40.734 --> 19:50:40.744 align:start position:0% car 19:50:40.744 --> 19:50:42.286 align:start position:0% car um<19:50:40.856> but<19:50:41.280> um<19:50:41.280> that<19:50:41.512> was<19:50:41.576> not<19:50:41.760> allowed<19:50:42.000> out<19:50:42.120> to 19:50:42.286 --> 19:50:42.296 align:start position:0% um but um that was not allowed out to 19:50:42.296 --> 19:50:44.030 align:start position:0% um but um that was not allowed out to the<19:50:42.424> public<19:50:42.536> and<19:50:42.896> now<19:50:43.016> it's<19:50:43.320> I<19:50:43.616> think<19:50:43.744> it's<19:50:43.800> in 19:50:44.030 --> 19:50:44.040 align:start position:0% the public and now it's I think it's in 19:50:44.040 --> 19:50:47.030 align:start position:0% the public and now it's I think it's in in<19:50:44.216> the<19:50:44.400> range<19:50:44.576> of<19:50:44.696> around<19:50:44.872> 10<19:50:45.240> meters<19:50:46.040> the 19:50:47.030 --> 19:50:47.040 align:start position:0% in the range of around 10 meters the 19:50:47.040 --> 19:50:49.606 align:start position:0% in the range of around 10 meters the other<19:50:47.160> thing<19:50:47.400> is<19:50:47.640> obviously<19:50:48.616> encrypted 19:50:49.606 --> 19:50:49.616 align:start position:0% other thing is obviously encrypted 19:50:49.616 --> 19:50:53.206 align:start position:0% other thing is obviously encrypted software<19:50:50.536> is<19:50:51.536> uh<19:50:52.192> restricted<19:50:52.856> because 19:50:53.206 --> 19:50:53.216 align:start position:0% software is uh restricted because 19:50:53.216 --> 19:50:55.134 align:start position:0% software is uh restricted because depending<19:50:54.120> on<19:50:54.176> the<19:50:54.360> level<19:50:54.480> of<19:50:54.656> encryption 19:50:55.134 --> 19:50:55.144 align:start position:0% depending on the level of encryption 19:50:55.144 --> 19:50:58.030 align:start position:0% depending on the level of encryption issues<19:50:55.552> by<19:50:55.856> uh<19:50:56.464> for<19:50:56.760> terrorist<19:50:57.120> organizations 19:50:58.030 --> 19:50:58.040 align:start position:0% issues by uh for terrorist organizations 19:50:58.040 --> 19:51:02.502 align:start position:0% issues by uh for terrorist organizations so<19:50:59.040> if<19:50:59.696> you<19:50:59.872> buy<19:51:00.176> any<19:51:00.536> software<19:51:01.400> say<19:51:02.400> for 19:51:02.502 --> 19:51:02.512 align:start position:0% so if you buy any software say for 19:51:02.512 --> 19:51:05.390 align:start position:0% so if you buy any software say for example<19:51:02.824> for<19:51:03.176> from<19:51:03.536> Cisco<19:51:04.192> if<19:51:04.976> it's<19:51:05.104> a<19:51:05.280> high 19:51:05.390 --> 19:51:05.400 align:start position:0% example for from Cisco if it's a high 19:51:05.400 --> 19:51:07.182 align:start position:0% example for from Cisco if it's a high level<19:51:05.576> encryption<19:51:06.296> you'll<19:51:06.656> normally<19:51:06.896> need 19:51:07.182 --> 19:51:07.192 align:start position:0% level encryption you'll normally need 19:51:07.192 --> 19:51:09.710 align:start position:0% level encryption you'll normally need some<19:51:07.440> sort<19:51:07.616> of<19:51:07.744> license<19:51:08.240> uh<19:51:09.240> you<19:51:09.424> can<19:51:09.480> get<19:51:09.600> it 19:51:09.710 --> 19:51:09.720 align:start position:0% some sort of license uh you can get it 19:51:09.720 --> 19:51:11.454 align:start position:0% some sort of license uh you can get it from<19:51:09.832> the<19:51:10.016> government<19:51:10.144> or<19:51:11.040> um<19:51:11.040> you<19:51:11.216> know<19:51:11.336> just 19:51:11.454 --> 19:51:11.464 align:start position:0% from the government or um you know just 19:51:11.464 --> 19:51:13.430 align:start position:0% from the government or um you know just to<19:51:11.576> do<19:51:11.824> your<19:51:11.936> own<19:51:12.056> research<19:51:12.424> and<19:51:12.600> see<19:51:12.832> how<19:51:13.320> your 19:51:13.430 --> 19:51:13.440 align:start position:0% to do your own research and see how your 19:51:13.440 --> 19:51:15.414 align:start position:0% to do your own research and see how your government<19:51:13.616> deals<19:51:14.040> with<19:51:14.160> it<19:51:14.424> satellite 19:51:15.414 --> 19:51:15.424 align:start position:0% government deals with it satellite 19:51:15.424 --> 19:51:18.734 align:start position:0% government deals with it satellite satellite<19:51:15.960> technology<19:51:16.440> and<19:51:17.040> images<19:51:17.696> that<19:51:18.424> are 19:51:18.734 --> 19:51:18.744 align:start position:0% satellite technology and images that are 19:51:18.744 --> 19:51:21.286 align:start position:0% satellite technology and images that are protected<19:51:19.744> or<19:51:19.976> sensitive 19:51:21.286 --> 19:51:21.296 align:start position:0% protected or sensitive 19:51:21.296 --> 19:51:23.862 align:start position:0% protected or sensitive uh<19:51:21.832> there<19:51:22.080> could<19:51:22.192> be<19:51:22.320> Financial<19:51:22.680> penalties<19:51:23.512> or 19:51:23.862 --> 19:51:23.872 align:start position:0% uh there could be Financial penalties or 19:51:23.872 --> 19:51:26.150 align:start position:0% uh there could be Financial penalties or you<19:51:24.120> could<19:51:24.240> be<19:51:24.424> criminally<19:51:24.832> liable<19:51:25.256> for<19:51:25.680> uh 19:51:26.150 --> 19:51:26.160 align:start position:0% you could be criminally liable for uh 19:51:26.160 --> 19:51:28.366 align:start position:0% you could be criminally liable for uh what<19:51:26.824> goes<19:51:27.176> on<19:51:27.296> so 19:51:28.366 --> 19:51:28.376 align:start position:0% what goes on so 19:51:28.376 --> 19:51:31.070 align:start position:0% what goes on so just<19:51:28.680> be<19:51:28.856> careful<19:51:29.360> data<19:51:30.360> loss<19:51:30.720> could<19:51:30.896> be 19:51:31.070 --> 19:51:31.080 align:start position:0% just be careful data loss could be 19:51:31.080 --> 19:51:33.774 align:start position:0% just be careful data loss could be accidental<19:51:31.744> or<19:51:32.040> malicious<19:51:32.576> I've<19:51:33.296> even<19:51:33.480> heard 19:51:33.774 --> 19:51:33.784 align:start position:0% accidental or malicious I've even heard 19:51:33.784 --> 19:51:37.670 align:start position:0% accidental or malicious I've even heard instances<19:51:34.440> of<19:51:35.040> and<19:51:35.464> the<19:51:36.192> talk<19:51:37.192> about<19:51:37.376> this 19:51:37.670 --> 19:51:37.680 align:start position:0% instances of and the talk about this 19:51:37.680 --> 19:51:40.846 align:start position:0% instances of and the talk about this elsewhere<19:51:38.104> but<19:51:38.696> the<19:51:38.936> word<19:51:39.120> computer<19:51:39.856> gets 19:51:40.846 --> 19:51:40.856 align:start position:0% elsewhere but the word computer gets 19:51:40.856 --> 19:51:43.606 align:start position:0% elsewhere but the word computer gets decommissioned<19:51:41.576> sent<19:51:42.240> off<19:51:42.480> for<19:51:42.720> sale<19:51:42.896> in<19:51:43.504> a 19:51:43.606 --> 19:51:43.616 align:start position:0% decommissioned sent off for sale in a 19:51:43.616 --> 19:51:46.006 align:start position:0% decommissioned sent off for sale in a shop<19:51:43.800> somewhere<19:51:44.336> and<19:51:45.000> then<19:51:45.120> somebody<19:51:45.360> can<19:51:45.784> see 19:51:46.006 --> 19:51:46.016 align:start position:0% shop somewhere and then somebody can see 19:51:46.016 --> 19:51:50.862 align:start position:0% shop somewhere and then somebody can see all<19:51:46.552> the<19:51:46.800> data<19:51:47.216> I've<19:51:48.056> actually<19:51:48.296> on<19:51:49.192> um<19:51:49.192> eBay<19:51:49.872> I 19:51:50.862 --> 19:51:50.872 align:start position:0% all the data I've actually on um eBay I 19:51:50.872 --> 19:51:53.206 align:start position:0% all the data I've actually on um eBay I bought<19:51:51.056> a<19:51:51.296> Cisco<19:51:51.720> router<19:51:52.256> I'll<19:51:52.552> do<19:51:52.800> this<19:51:52.976> image 19:51:53.206 --> 19:51:53.216 align:start position:0% bought a Cisco router I'll do this image 19:51:53.216 --> 19:51:55.910 align:start position:0% bought a Cisco router I'll do this image here<19:51:53.336> bought<19:51:53.640> a<19:51:53.760> Cisco<19:51:54.056> router<19:51:54.536> I<19:51:55.320> booted<19:51:55.744> it 19:51:55.910 --> 19:51:55.920 align:start position:0% here bought a Cisco router I booted it 19:51:55.920 --> 19:51:59.110 align:start position:0% here bought a Cisco router I booted it up<19:51:56.104> and<19:51:56.824> I<19:51:57.000> had<19:51:57.240> a<19:51:57.480> load<19:51:57.720> of<19:51:58.016> um<19:51:58.016> IP<19:51:58.496> information 19:51:59.110 --> 19:51:59.120 align:start position:0% up and I had a load of um IP information 19:51:59.120 --> 19:52:02.230 align:start position:0% up and I had a load of um IP information password<19:52:00.120> information 19:52:02.230 --> 19:52:02.240 align:start position:0% password information 19:52:02.240 --> 19:52:08.206 align:start position:0% password information usernames<19:52:03.656> and<19:52:04.192> this<19:52:04.320> was<19:52:04.440> for<19:52:04.680> a<19:52:04.856> large<19:52:05.040> ISP 19:52:08.206 --> 19:52:08.216 align:start position:0% 19:52:08.216 --> 19:52:11.270 align:start position:0% um<19:52:08.336> an<19:52:09.176> internationally<19:52:09.600> known<19:52:10.080> ISP<19:52:10.744> so 19:52:11.270 --> 19:52:11.280 align:start position:0% um an internationally known ISP so 19:52:11.280 --> 19:52:12.886 align:start position:0% um an internationally known ISP so heaven<19:52:11.696> knows<19:52:12.000> who<19:52:12.120> was<19:52:12.240> decommissioning 19:52:12.886 --> 19:52:12.896 align:start position:0% heaven knows who was decommissioning 19:52:12.896 --> 19:52:14.990 align:start position:0% heaven knows who was decommissioning their<19:52:13.144> equipment<19:52:13.504> but<19:52:14.160> it<19:52:14.336> wasn't<19:52:14.464> being<19:52:14.760> done 19:52:14.990 --> 19:52:15.000 align:start position:0% their equipment but it wasn't being done 19:52:15.000 --> 19:52:17.150 align:start position:0% their equipment but it wasn't being done very<19:52:15.360> professionally 19:52:17.150 --> 19:52:17.160 align:start position:0% very professionally 19:52:17.160 --> 19:52:19.542 align:start position:0% very professionally have<19:52:17.512> a<19:52:17.696> policy<19:52:18.056> for<19:52:18.296> your<19:52:18.480> clients<19:52:19.016> devices 19:52:19.542 --> 19:52:19.552 align:start position:0% have a policy for your clients devices 19:52:19.552 --> 19:52:21.470 align:start position:0% have a policy for your clients devices your<19:52:19.920> network<19:52:20.104> devices<19:52:20.576> and<19:52:21.056> any<19:52:21.176> storage 19:52:21.470 --> 19:52:21.480 align:start position:0% your network devices and any storage 19:52:21.480 --> 19:52:24.166 align:start position:0% your network devices and any storage devices<19:52:22.016> and<19:52:22.800> there's<19:52:22.976> normally 19:52:24.166 --> 19:52:24.176 align:start position:0% devices and there's normally 19:52:24.176 --> 19:52:26.454 align:start position:0% devices and there's normally um software<19:52:24.832> that<19:52:25.144> you<19:52:25.256> can<19:52:25.376> wipe<19:52:26.160> off<19:52:26.216> hard 19:52:26.454 --> 19:52:26.464 align:start position:0% um software that you can wipe off hard 19:52:26.464 --> 19:52:27.886 align:start position:0% um software that you can wipe off hard drives<19:52:26.824> or<19:52:27.056> sometimes<19:52:27.360> they<19:52:27.536> have<19:52:27.656> to<19:52:27.784> be 19:52:27.886 --> 19:52:27.896 align:start position:0% drives or sometimes they have to be 19:52:27.896 --> 19:52:29.030 align:start position:0% drives or sometimes they have to be destroyed 19:52:29.030 --> 19:52:29.040 align:start position:0% destroyed 19:52:29.040 --> 19:52:31.502 align:start position:0% destroyed identify<19:52:29.872> what's<19:52:30.176> most<19:52:30.480> sensitive<19:52:30.960> normally 19:52:31.502 --> 19:52:31.512 align:start position:0% identify what's most sensitive normally 19:52:31.512 --> 19:52:34.734 align:start position:0% identify what's most sensitive normally addresses<19:52:32.512> credit<19:52:33.296> card<19:52:33.536> information<19:52:33.832> emails 19:52:34.734 --> 19:52:34.744 align:start position:0% addresses credit card information emails 19:52:34.744 --> 19:52:37.006 align:start position:0% addresses credit card information emails make<19:52:35.512> sure<19:52:35.640> people<19:52:35.872> are<19:52:36.120> trained<19:52:36.536> and<19:52:36.832> review 19:52:37.006 --> 19:52:37.016 align:start position:0% make sure people are trained and review 19:52:37.016 --> 19:52:39.110 align:start position:0% make sure people are trained and review the<19:52:37.320> training 19:52:39.110 --> 19:52:39.120 align:start position:0% the training 19:52:39.120 --> 19:52:40.686 align:start position:0% the training I've<19:52:39.656> talked<19:52:39.896> about<19:52:39.960> remote<19:52:40.320> access 19:52:40.686 --> 19:52:40.696 align:start position:0% I've talked about remote access 19:52:40.696 --> 19:52:44.206 align:start position:0% I've talked about remote access equipment<19:52:41.696> you<19:52:42.360> need<19:52:42.600> to<19:52:42.720> also<19:52:43.016> work<19:52:43.256> out<19:52:43.504> who 19:52:44.206 --> 19:52:44.216 align:start position:0% equipment you need to also work out who 19:52:44.216 --> 19:52:47.750 align:start position:0% equipment you need to also work out who is<19:52:44.576> allowed<19:52:45.000> remote<19:52:45.176> access<19:52:45.600> this<19:52:46.496> can<19:52:46.680> be 19:52:47.750 --> 19:52:47.760 align:start position:0% is allowed remote access this can be 19:52:47.760 --> 19:52:49.246 align:start position:0% is allowed remote access this can be um 19:52:49.246 --> 19:52:49.256 align:start position:0% um 19:52:49.256 --> 19:52:51.526 align:start position:0% um this<19:52:50.104> could<19:52:50.216> be<19:52:50.336> sales<19:52:50.640> if<19:52:51.056> they're<19:52:51.240> on<19:52:51.424> the 19:52:51.526 --> 19:52:51.536 align:start position:0% this could be sales if they're on the 19:52:51.536 --> 19:52:53.502 align:start position:0% this could be sales if they're on the road<19:52:51.720> it<19:52:52.552> could<19:52:52.680> be 19:52:53.502 --> 19:52:53.512 align:start position:0% road it could be 19:52:53.512 --> 19:52:57.710 align:start position:0% road it could be um 19:52:57.710 --> 19:52:57.720 align:start position:0% 19:52:57.720 --> 19:53:01.454 align:start position:0% Telly<19:52:58.376> see 19:53:01.454 --> 19:53:01.464 align:start position:0% 19:53:01.464 --> 19:53:03.414 align:start position:0% telecomuters 19:53:03.414 --> 19:53:03.424 align:start position:0% telecomuters 19:53:03.424 --> 19:53:05.686 align:start position:0% telecomuters that<19:53:04.376> kind<19:53:04.552> of<19:53:04.616> thing<19:53:04.800> people<19:53:05.104> who<19:53:05.336> work<19:53:05.512> from 19:53:05.686 --> 19:53:05.696 align:start position:0% that kind of thing people who work from 19:53:05.696 --> 19:53:07.006 align:start position:0% that kind of thing people who work from home 19:53:07.006 --> 19:53:07.016 align:start position:0% home 19:53:07.016 --> 19:53:08.990 align:start position:0% home what<19:53:07.552> VPN<19:53:08.040> software<19:53:08.400> are<19:53:08.464> they<19:53:08.640> allowed<19:53:08.936> to 19:53:08.990 --> 19:53:09.000 align:start position:0% what VPN software are they allowed to 19:53:09.000 --> 19:53:11.326 align:start position:0% what VPN software are they allowed to use<19:53:09.240> are<19:53:09.600> they<19:53:09.720> allowed<19:53:10.080> through<19:53:10.336> SSH 19:53:11.326 --> 19:53:11.336 align:start position:0% use are they allowed through SSH 19:53:11.336 --> 19:53:14.630 align:start position:0% use are they allowed through SSH software<19:53:12.056> or<19:53:12.896> if<19:53:13.192> they<19:53:13.376> don't<19:53:13.552> have<19:53:13.800> a<19:53:14.160> good 19:53:14.630 --> 19:53:14.640 align:start position:0% software or if they don't have a good 19:53:14.640 --> 19:53:16.542 align:start position:0% software or if they don't have a good internet<19:53:14.824> connection<19:53:15.320> probably<19:53:16.320> people 19:53:16.542 --> 19:53:16.552 align:start position:0% internet connection probably people 19:53:16.552 --> 19:53:19.070 align:start position:0% internet connection probably people won't<19:53:16.800> use<19:53:16.976> modems<19:53:17.464> anymore<19:53:17.576> but 19:53:19.070 --> 19:53:19.080 align:start position:0% won't use modems anymore but 19:53:19.080 --> 19:53:22.070 align:start position:0% won't use modems anymore but uh<19:53:19.616> disable<19:53:20.040> HTTP<19:53:21.000> access<19:53:21.296> I've<19:53:21.720> talked<19:53:21.960> about 19:53:22.070 --> 19:53:22.080 align:start position:0% uh disable HTTP access I've talked about 19:53:22.080 --> 19:53:25.966 align:start position:0% uh disable HTTP access I've talked about this<19:53:22.376> elsewhere<19:53:22.744> https<19:53:23.600> but<19:53:24.600> when<19:53:25.080> you<19:53:25.320> have<19:53:25.800> a 19:53:25.966 --> 19:53:25.976 align:start position:0% this elsewhere https but when you have a 19:53:25.976 --> 19:53:27.470 align:start position:0% this elsewhere https but when you have a device<19:53:26.104> a<19:53:26.400> lot<19:53:26.464> of<19:53:26.576> the<19:53:26.640> time<19:53:26.760> you<19:53:26.936> can<19:53:27.120> put<19:53:27.240> an 19:53:27.470 --> 19:53:27.480 align:start position:0% device a lot of the time you can put an 19:53:27.480 --> 19:53:31.246 align:start position:0% device a lot of the time you can put an IP<19:53:27.832> address<19:53:28.016> into<19:53:28.800> a<19:53:29.040> browser<19:53:29.464> and<19:53:30.176> manage<19:53:30.480> it 19:53:31.246 --> 19:53:31.256 align:start position:0% IP address into a browser and manage it 19:53:31.256 --> 19:53:33.774 align:start position:0% IP address into a browser and manage it what's<19:53:31.800> your<19:53:32.040> favorite<19:53:32.280> VPN<19:53:33.056> client<19:53:33.424> software 19:53:33.774 --> 19:53:33.784 align:start position:0% what's your favorite VPN client software 19:53:33.784 --> 19:53:35.862 align:start position:0% what's your favorite VPN client software what<19:53:34.320> are<19:53:34.496> they<19:53:34.616> allowed<19:53:34.920> to<19:53:35.040> download<19:53:35.464> if 19:53:35.862 --> 19:53:35.872 align:start position:0% what are they allowed to download if 19:53:35.872 --> 19:53:38.502 align:start position:0% what are they allowed to download if anything<19:53:36.120> onto<19:53:36.960> Works<19:53:37.320> laptops 19:53:38.502 --> 19:53:38.512 align:start position:0% anything onto Works laptops 19:53:38.512 --> 19:53:40.966 align:start position:0% anything onto Works laptops are<19:53:39.240> they<19:53:39.424> allowed<19:53:39.656> the<19:53:39.784> intranet<19:53:40.496> what<19:53:40.856> can 19:53:40.966 --> 19:53:40.976 align:start position:0% are they allowed the intranet what can 19:53:40.976 --> 19:53:42.286 align:start position:0% are they allowed the intranet what can they<19:53:41.160> see<19:53:41.280> on<19:53:41.464> the<19:53:41.576> internet<19:53:41.640> and<19:53:42.000> where<19:53:42.176> can 19:53:42.286 --> 19:53:42.296 align:start position:0% they see on the internet and where can 19:53:42.296 --> 19:53:44.926 align:start position:0% they see on the internet and where can they<19:53:42.424> access<19:53:42.536> it<19:53:42.896> from<19:53:43.160> Works<19:53:44.160> emails<19:53:44.576> a<19:53:44.824> big 19:53:44.926 --> 19:53:44.936 align:start position:0% they access it from Works emails a big 19:53:44.936 --> 19:53:46.966 align:start position:0% they access it from Works emails a big one<19:53:45.120> especially<19:53:45.536> with<19:53:45.960> the<19:53:46.256> uh<19:53:46.496> the<19:53:46.800> latest 19:53:46.966 --> 19:53:46.976 align:start position:0% one especially with the uh the latest 19:53:46.976 --> 19:53:49.790 align:start position:0% one especially with the uh the latest presidential<19:53:47.640> campaign<19:53:48.176> as<19:53:48.784> you<19:53:48.960> know 19:53:49.790 --> 19:53:49.800 align:start position:0% presidential campaign as you know 19:53:49.800 --> 19:53:52.310 align:start position:0% presidential campaign as you know um<19:53:50.336> one<19:53:50.824> of<19:53:51.000> the<19:53:51.056> candidates<19:53:51.480> was<19:53:51.784> accused<19:53:52.192> of 19:53:52.310 --> 19:53:52.320 align:start position:0% um one of the candidates was accused of 19:53:52.320 --> 19:53:54.414 align:start position:0% um one of the candidates was accused of download<19:53:52.616> insensitive<19:53:53.336> email<19:53:53.576> onto<19:53:54.176> their 19:53:54.414 --> 19:53:54.424 align:start position:0% download insensitive email onto their 19:53:54.424 --> 19:53:56.750 align:start position:0% download insensitive email onto their from<19:53:54.720> The<19:53:54.832> Works<19:53:55.256> servers<19:53:56.104> onto<19:53:56.400> their<19:53:56.512> home 19:53:56.750 --> 19:53:56.760 align:start position:0% from The Works servers onto their home 19:53:56.760 --> 19:53:59.502 align:start position:0% from The Works servers onto their home servers 19:53:59.502 --> 19:53:59.512 align:start position:0% 19:53:59.512 --> 19:54:01.182 align:start position:0% what<19:54:00.120> happens<19:54:00.240> when<19:54:00.600> there's<19:54:00.784> an<19:54:00.960> incident 19:54:01.182 --> 19:54:01.192 align:start position:0% what happens when there's an incident 19:54:01.192 --> 19:54:04.006 align:start position:0% what happens when there's an incident there<19:54:01.552> should<19:54:01.744> be<19:54:01.920> a<19:54:02.464> policy<19:54:03.000> because<19:54:03.360> some 19:54:04.006 --> 19:54:04.016 align:start position:0% there should be a policy because some 19:54:04.016 --> 19:54:06.110 align:start position:0% there should be a policy because some places<19:54:04.192> have<19:54:04.552> worked<19:54:04.920> people<19:54:05.336> are<19:54:05.576> blaming 19:54:06.110 --> 19:54:06.120 align:start position:0% places have worked people are blaming 19:54:06.120 --> 19:54:08.454 align:start position:0% places have worked people are blaming each<19:54:06.240> other<19:54:06.360> finger<19:54:06.832> pointing<19:54:07.256> nobody<19:54:08.104> knows 19:54:08.454 --> 19:54:08.464 align:start position:0% each other finger pointing nobody knows 19:54:08.464 --> 19:54:10.790 align:start position:0% each other finger pointing nobody knows who's<19:54:08.696> responsible<19:54:09.296> for<19:54:09.720> what<19:54:09.960> so<19:54:10.616> there 19:54:10.790 --> 19:54:10.800 align:start position:0% who's responsible for what so there 19:54:10.800 --> 19:54:11.822 align:start position:0% who's responsible for what so there should<19:54:10.976> be 19:54:11.822 --> 19:54:11.832 align:start position:0% should be 19:54:11.832 --> 19:54:13.430 align:start position:0% should be written 19:54:13.430 --> 19:54:13.440 align:start position:0% written 19:54:13.440 --> 19:54:15.286 align:start position:0% written procedures<19:54:14.280> and<19:54:14.512> also<19:54:14.696> training<19:54:15.120> so 19:54:15.286 --> 19:54:15.296 align:start position:0% procedures and also training so 19:54:15.296 --> 19:54:17.502 align:start position:0% procedures and also training so everybody<19:54:15.536> knows<19:54:16.016> who's<19:54:16.256> responsible<19:54:16.920> and 19:54:17.502 --> 19:54:17.512 align:start position:0% everybody knows who's responsible and 19:54:17.512 --> 19:54:20.270 align:start position:0% everybody knows who's responsible and what<19:54:17.696> the<19:54:17.824> procedure<19:54:18.296> is<19:54:18.536> for<19:54:19.744> um<19:54:19.744> escalating 19:54:20.270 --> 19:54:20.280 align:start position:0% what the procedure is for um escalating 19:54:20.280 --> 19:54:23.630 align:start position:0% what the procedure is for um escalating it<19:54:20.512> who<19:54:20.640> gets<19:54:20.936> called<19:54:21.056> who<19:54:21.424> gets<19:54:21.720> paged 19:54:23.630 --> 19:54:23.640 align:start position:0% it who gets called who gets paged 19:54:23.640 --> 19:54:27.470 align:start position:0% it who gets called who gets paged uh<19:54:24.120> who<19:54:24.360> are<19:54:24.536> the<19:54:24.656> stakeholders<19:54:25.320> so<19:54:26.696> um<19:54:26.696> you 19:54:27.470 --> 19:54:27.480 align:start position:0% uh who are the stakeholders so um you 19:54:27.480 --> 19:54:29.814 align:start position:0% uh who are the stakeholders so um you know<19:54:27.536> your<19:54:28.016> Chief<19:54:28.256> technology<19:54:28.744> officer<19:54:29.464> your 19:54:29.814 --> 19:54:29.824 align:start position:0% know your Chief technology officer your 19:54:29.824 --> 19:54:32.814 align:start position:0% know your Chief technology officer your network<19:54:30.056> manager<19:54:30.784> security<19:54:31.376> manager<19:54:32.216> all 19:54:32.814 --> 19:54:32.824 align:start position:0% network manager security manager all 19:54:32.824 --> 19:54:33.886 align:start position:0% network manager security manager all these<19:54:33.000> kind<19:54:33.120> of<19:54:33.240> people<19:54:33.360> who<19:54:33.656> are<19:54:33.784> they 19:54:33.886 --> 19:54:33.896 align:start position:0% these kind of people who are they 19:54:33.896 --> 19:54:35.270 align:start position:0% these kind of people who are they involved<19:54:34.256> depending<19:54:34.744> on<19:54:34.800> what<19:54:34.976> the<19:54:35.104> problem 19:54:35.270 --> 19:54:35.280 align:start position:0% involved depending on what the problem 19:54:35.280 --> 19:54:36.470 align:start position:0% involved depending on what the problem is 19:54:36.470 --> 19:54:36.480 align:start position:0% is 19:54:36.480 --> 19:54:38.990 align:start position:0% is so<19:54:36.960> identify<19:54:37.552> the<19:54:37.744> start<19:54:37.920> procedures<19:54:38.512> the 19:54:38.990 --> 19:54:39.000 align:start position:0% so identify the start procedures the 19:54:39.000 --> 19:54:40.670 align:start position:0% so identify the start procedures the start<19:54:39.176> the<19:54:39.480> procedures<19:54:39.960> and<19:54:40.144> the<19:54:40.320> steps<19:54:40.552> that 19:54:40.670 --> 19:54:40.680 align:start position:0% start the procedures and the steps that 19:54:40.680 --> 19:54:42.822 align:start position:0% start the procedures and the steps that take<19:54:40.920> place<19:54:41.160> you're<19:54:41.936> normally<19:54:42.176> work<19:54:42.480> in<19:54:42.656> some 19:54:42.822 --> 19:54:42.832 align:start position:0% take place you're normally work in some 19:54:42.832 --> 19:54:44.926 align:start position:0% take place you're normally work in some sort<19:54:43.016> of<19:54:43.144> framework<19:54:43.616> like 19:54:44.926 --> 19:54:44.936 align:start position:0% sort of framework like 19:54:44.936 --> 19:54:48.822 align:start position:0% sort of framework like ITIL<19:54:45.784> it<19:54:46.464> infrastructure<19:54:47.464> Library 19:54:48.822 --> 19:54:48.832 align:start position:0% ITIL it infrastructure Library 19:54:48.832 --> 19:54:50.750 align:start position:0% ITIL it infrastructure Library they<19:54:49.320> have<19:54:49.440> qualifications<19:54:50.040> on<19:54:50.576> them 19:54:50.750 --> 19:54:50.760 align:start position:0% they have qualifications on them 19:54:50.760 --> 19:54:52.846 align:start position:0% they have qualifications on them procedures<19:54:51.360> you<19:54:51.600> should<19:54:51.720> be<19:54:51.832> using 19:54:52.846 --> 19:54:52.856 align:start position:0% procedures you should be using 19:54:52.856 --> 19:54:55.790 align:start position:0% procedures you should be using who<19:54:53.400> declares<19:54:53.760> it's<19:54:53.872> an<19:54:54.120> incident<19:54:54.440> uh<19:54:55.440> within 19:54:55.790 --> 19:54:55.800 align:start position:0% who declares it's an incident uh within 19:54:55.800 --> 19:54:58.966 align:start position:0% who declares it's an incident uh within ITIL<19:54:56.216> you've<19:54:56.576> got<19:54:57.176> um 19:54:58.966 --> 19:54:58.976 align:start position:0% ITIL you've got um 19:54:58.976 --> 19:55:05.390 align:start position:0% ITIL you've got um you've<19:54:59.576> got<19:54:59.696> different<19:55:00.056> streams<19:55:00.832> problem 19:55:05.390 --> 19:55:05.400 align:start position:0% 19:55:05.400 --> 19:55:07.430 align:start position:0% you've<19:55:05.872> got<19:55:06.000> the<19:55:06.240> problem<19:55:06.424> manager<19:55:07.016> normally 19:55:07.430 --> 19:55:07.440 align:start position:0% you've got the problem manager normally 19:55:07.440 --> 19:55:10.430 align:start position:0% you've got the problem manager normally on<19:55:07.744> any<19:55:07.920> team<19:55:08.216> that's<19:55:08.824> one<19:55:09.176> person<19:55:09.480> who 19:55:10.430 --> 19:55:10.440 align:start position:0% on any team that's one person who 19:55:10.440 --> 19:55:13.134 align:start position:0% on any team that's one person who everyone<19:55:10.856> reports<19:55:11.696> a<19:55:12.000> problem<19:55:12.176> to 19:55:13.134 --> 19:55:13.144 align:start position:0% everyone reports a problem to 19:55:13.144 --> 19:55:15.950 align:start position:0% everyone reports a problem to instead<19:55:13.920> of<19:55:14.040> basically<19:55:14.576> everyone<19:55:15.536> in<19:55:15.832> the 19:55:15.950 --> 19:55:15.960 align:start position:0% instead of basically everyone in the 19:55:15.960 --> 19:55:17.326 align:start position:0% instead of basically everyone in the team<19:55:16.080> being<19:55:16.376> told<19:55:16.616> through<19:55:16.856> help<19:55:17.104> desk 19:55:17.326 --> 19:55:17.336 align:start position:0% team being told through help desk 19:55:17.336 --> 19:55:19.494 align:start position:0% team being told through help desk tickets<19:55:17.696> and<19:55:18.424> then<19:55:18.536> they<19:55:18.784> tell<19:55:18.960> other<19:55:19.144> people 19:55:19.494 --> 19:55:19.504 align:start position:0% tickets and then they tell other people 19:55:19.504 --> 19:55:22.310 align:start position:0% tickets and then they tell other people the<19:55:20.160> problem<19:55:20.336> manager<19:55:21.000> will<19:55:21.656> receive<19:55:22.016> all<19:55:22.192> of 19:55:22.310 --> 19:55:22.320 align:start position:0% the problem manager will receive all of 19:55:22.320 --> 19:55:23.926 align:start position:0% the problem manager will receive all of the<19:55:22.440> reports<19:55:22.744> of<19:55:22.856> the<19:55:23.040> problems<19:55:23.400> and<19:55:23.824> then 19:55:23.926 --> 19:55:23.936 align:start position:0% the reports of the problems and then 19:55:23.936 --> 19:55:25.846 align:start position:0% the reports of the problems and then they<19:55:24.176> will<19:55:24.296> escalate<19:55:24.832> it<19:55:25.016> when<19:55:25.504> there's<19:55:25.680> a 19:55:25.846 --> 19:55:25.856 align:start position:0% they will escalate it when there's a 19:55:25.856 --> 19:55:27.646 align:start position:0% they will escalate it when there's a resolution<19:55:26.216> it'll<19:55:27.120> go<19:55:27.240> through<19:55:27.360> the<19:55:27.480> problem 19:55:27.646 --> 19:55:27.656 align:start position:0% resolution it'll go through the problem 19:55:27.656 --> 19:55:29.630 align:start position:0% resolution it'll go through the problem manager<19:55:28.256> and<19:55:28.680> they<19:55:28.800> will<19:55:28.976> communicate<19:55:29.464> it 19:55:29.630 --> 19:55:29.640 align:start position:0% manager and they will communicate it 19:55:29.640 --> 19:55:31.966 align:start position:0% manager and they will communicate it through<19:55:29.872> group<19:55:30.120> email<19:55:30.424> phone<19:55:31.376> calls<19:55:31.800> or 19:55:31.966 --> 19:55:31.976 align:start position:0% through group email phone calls or 19:55:31.976 --> 19:55:33.590 align:start position:0% through group email phone calls or whatever 19:55:33.590 --> 19:55:33.600 align:start position:0% whatever 19:55:33.600 --> 19:55:36.646 align:start position:0% whatever uh<19:55:34.080> can<19:55:34.320> their<19:55:34.496> damage<19:55:34.800> be<19:55:35.040> isolated 19:55:36.646 --> 19:55:36.656 align:start position:0% uh can their damage be isolated 19:55:36.656 --> 19:55:38.502 align:start position:0% uh can their damage be isolated um<19:55:36.720> can<19:55:36.960> it<19:55:37.144> be<19:55:37.256> who's<19:55:37.504> who's<19:55:37.920> in<19:55:38.216> charge<19:55:38.336> of 19:55:38.502 --> 19:55:38.512 align:start position:0% um can it be who's who's in charge of 19:55:38.512 --> 19:55:40.606 align:start position:0% um can it be who's who's in charge of actually<19:55:38.760> removing<19:55:39.360> it<19:55:39.536> who<19:55:40.016> will<19:55:40.192> they<19:55:40.320> speak 19:55:40.606 --> 19:55:40.616 align:start position:0% actually removing it who will they speak 19:55:40.616 --> 19:55:43.366 align:start position:0% actually removing it who will they speak to<19:55:40.800> can<19:55:41.640> they<19:55:42.120> um<19:55:42.120> who's<19:55:42.600> got<19:55:42.784> the<19:55:42.896> authority 19:55:43.366 --> 19:55:43.376 align:start position:0% to can they um who's got the authority 19:55:43.376 --> 19:55:47.502 align:start position:0% to can they um who's got the authority to<19:55:44.400> um<19:55:44.512> to<19:55:45.176> escalate<19:55:45.656> it<19:55:45.896> to<19:55:46.192> say 19:55:47.502 --> 19:55:47.512 align:start position:0% to um to escalate it to say 19:55:47.512 --> 19:55:52.606 align:start position:0% to um to escalate it to say um<19:55:47.576> Cisco<19:55:48.424> attack<19:55:48.976> or<19:55:50.216> um<19:55:50.280> the<19:55:50.512> AWS<19:55:51.320> uh<19:55:52.320> Senior 19:55:52.606 --> 19:55:52.616 align:start position:0% um Cisco attack or um the AWS uh Senior 19:55:52.616 --> 19:55:54.046 align:start position:0% um Cisco attack or um the AWS uh Senior Team<19:55:52.800> if<19:55:52.976> you've<19:55:53.160> got<19:55:53.280> a<19:55:53.400> support<19:55:53.576> contract 19:55:54.046 --> 19:55:54.056 align:start position:0% Team if you've got a support contract 19:55:54.056 --> 19:55:55.670 align:start position:0% Team if you've got a support contract with<19:55:54.240> Amazon 19:55:55.670 --> 19:55:55.680 align:start position:0% with Amazon 19:55:55.680 --> 19:55:57.470 align:start position:0% with Amazon uh<19:55:56.464> then<19:55:56.696> eventually<19:55:57.056> hopefully<19:55:57.360> it's 19:55:57.470 --> 19:55:57.480 align:start position:0% uh then eventually hopefully it's 19:55:57.480 --> 19:55:59.206 align:start position:0% uh then eventually hopefully it's recovered<19:55:57.896> Network<19:55:58.080> restored<19:55:58.800> to<19:55:58.920> normal 19:55:59.206 --> 19:55:59.216 align:start position:0% recovered Network restored to normal 19:55:59.216 --> 19:56:02.566 align:start position:0% recovered Network restored to normal function<19:56:00.016> there'll<19:56:01.016> be<19:56:01.080> a<19:56:01.320> debrief<19:56:01.856> after<19:56:02.104> if 19:56:02.566 --> 19:56:02.576 align:start position:0% function there'll be a debrief after if 19:56:02.576 --> 19:56:05.206 align:start position:0% function there'll be a debrief after if you<19:56:02.696> go<19:56:02.872> through<19:56:03.120> the<19:56:03.424> idle<19:56:04.216> procedures 19:56:05.206 --> 19:56:05.216 align:start position:0% you go through the idle procedures 19:56:05.216 --> 19:56:07.606 align:start position:0% you go through the idle procedures there's<19:56:05.576> a<19:56:05.760> normally<19:56:06.056> a<19:56:06.296> meeting<19:56:06.896> a 19:56:07.606 --> 19:56:07.616 align:start position:0% there's a normally a meeting a 19:56:07.616 --> 19:56:08.990 align:start position:0% there's a normally a meeting a resolution<19:56:07.976> and<19:56:08.336> then<19:56:08.512> something<19:56:08.760> will 19:56:08.990 --> 19:56:09.000 align:start position:0% resolution and then something will 19:56:09.000 --> 19:56:10.910 align:start position:0% resolution and then something will happen<19:56:09.296> to 19:56:10.910 --> 19:56:10.920 align:start position:0% happen to 19:56:10.920 --> 19:56:12.886 align:start position:0% happen to um change<19:56:11.336> the<19:56:11.576> procedures<19:56:12.176> so<19:56:12.600> it<19:56:12.720> doesn't 19:56:12.886 --> 19:56:12.896 align:start position:0% um change the procedures so it doesn't 19:56:12.896 --> 19:56:14.326 align:start position:0% um change the procedures so it doesn't happen<19:56:13.192> again 19:56:14.326 --> 19:56:14.336 align:start position:0% happen again 19:56:14.336 --> 19:56:17.150 align:start position:0% happen again the<19:56:15.056> training<19:56:15.600> or<19:56:16.320> there<19:56:16.616> could<19:56:16.744> be<19:56:16.856> some<19:56:16.976> sort 19:56:17.150 --> 19:56:17.160 align:start position:0% the training or there could be some sort 19:56:17.160 --> 19:56:19.430 align:start position:0% the training or there could be some sort of<19:56:17.280> consequence<19:56:17.824> if<19:56:18.600> somebody's<19:56:19.016> made<19:56:19.192> a 19:56:19.430 --> 19:56:19.440 align:start position:0% of consequence if somebody's made a 19:56:19.440 --> 19:56:20.454 align:start position:0% of consequence if somebody's made a mistake<19:56:19.744> that<19:56:19.856> they<19:56:20.040> should<19:56:20.160> have<19:56:20.280> known 19:56:20.454 --> 19:56:20.464 align:start position:0% mistake that they should have known 19:56:20.464 --> 19:56:21.590 align:start position:0% mistake that they should have known better 19:56:21.590 --> 19:56:21.600 align:start position:0% better 19:56:21.600 --> 19:56:24.710 align:start position:0% better BYOD<19:56:22.496> bring<19:56:22.920> your<19:56:23.104> own<19:56:23.280> device<19:56:23.512> normally<19:56:24.240> and 19:56:24.710 --> 19:56:24.720 align:start position:0% BYOD bring your own device normally and 19:56:24.720 --> 19:56:27.350 align:start position:0% BYOD bring your own device normally and not<19:56:24.960> allowed<19:56:25.320> in<19:56:25.856> fact<19:56:26.040> most<19:56:26.400> places<19:56:26.640> really 19:56:27.350 --> 19:56:27.360 align:start position:0% not allowed in fact most places really 19:56:27.360 --> 19:56:31.246 align:start position:0% not allowed in fact most places really should<19:56:28.144> have<19:56:28.320> the<19:56:28.496> USB<19:56:28.920> ports<19:56:29.336> disabled 19:56:31.246 --> 19:56:31.256 align:start position:0% should have the USB ports disabled 19:56:31.256 --> 19:56:34.846 align:start position:0% should have the USB ports disabled um<19:56:31.376> and<19:56:31.920> decided<19:56:32.640> who<19:56:32.872> can<19:56:33.056> use<19:56:33.240> what<19:56:33.600> where 19:56:34.846 --> 19:56:34.856 align:start position:0% um and decided who can use what where 19:56:34.856 --> 19:56:38.150 align:start position:0% um and decided who can use what where the<19:56:34.976> policy<19:56:35.576> per<19:56:35.824> device<19:56:36.176> so<19:56:36.656> for<19:56:36.960> example 19:56:38.150 --> 19:56:38.160 align:start position:0% the policy per device so for example 19:56:38.160 --> 19:56:40.670 align:start position:0% the policy per device so for example um<19:56:38.696> can<19:56:39.120> they<19:56:39.296> bring<19:56:39.480> a<19:56:39.600> whap<19:56:39.896> in<19:56:40.016> probably<19:56:40.376> not 19:56:40.670 --> 19:56:40.680 align:start position:0% um can they bring a whap in probably not 19:56:40.680 --> 19:56:44.814 align:start position:0% um can they bring a whap in probably not could<19:56:41.336> they<19:56:41.512> bring<19:56:41.696> a<19:56:41.936> USB<19:56:42.536> device<19:56:43.440> in 19:56:44.814 --> 19:56:44.824 align:start position:0% could they bring a USB device in 19:56:44.824 --> 19:56:46.910 align:start position:0% could they bring a USB device in even<19:56:45.480> phones<19:56:46.016> are<19:56:46.192> they<19:56:46.376> allowed<19:56:46.616> to<19:56:46.744> bring 19:56:46.910 --> 19:56:46.920 align:start position:0% even phones are they allowed to bring 19:56:46.920 --> 19:56:48.526 align:start position:0% even phones are they allowed to bring phones<19:56:47.336> in<19:56:47.512> could<19:56:47.760> they<19:56:47.936> try<19:56:48.120> and<19:56:48.176> pig<19:56:48.296> you 19:56:48.526 --> 19:56:48.536 align:start position:0% phones in could they try and pig you 19:56:48.536 --> 19:56:50.686 align:start position:0% phones in could they try and pig you back<19:56:48.656> onto<19:56:48.896> the<19:56:49.016> wireless<19:56:49.144> network<19:56:49.616> all<19:56:50.464> these 19:56:50.686 --> 19:56:50.696 align:start position:0% back onto the wireless network all these 19:56:50.696 --> 19:56:52.006 align:start position:0% back onto the wireless network all these kind<19:56:50.824> of<19:56:50.936> things<19:56:51.056> there<19:56:51.240> should<19:56:51.424> be<19:56:51.536> a<19:56:51.656> policy 19:56:52.006 --> 19:56:52.016 align:start position:0% kind of things there should be a policy 19:56:52.016 --> 19:56:54.046 align:start position:0% kind of things there should be a policy for 19:56:54.046 --> 19:56:54.056 align:start position:0% for 19:56:54.056 --> 19:56:55.670 align:start position:0% for and<19:56:54.424> who<19:56:54.656> owns<19:56:54.896> what<19:56:55.016> data<19:56:55.440> if<19:56:55.552> somebody 19:56:55.670 --> 19:56:55.680 align:start position:0% and who owns what data if somebody 19:56:55.680 --> 19:56:58.846 align:start position:0% and who owns what data if somebody brings<19:56:56.104> in<19:56:56.280> their<19:56:56.512> device<19:56:56.960> and<19:56:57.960> but<19:56:58.440> they're 19:56:58.846 --> 19:56:58.856 align:start position:0% brings in their device and but they're 19:56:58.856 --> 19:57:00.710 align:start position:0% brings in their device and but they're using<19:56:59.104> it<19:56:59.216> for<19:56:59.400> work<19:56:59.640> you<19:57:00.176> know<19:57:00.296> who<19:57:00.424> entered 19:57:00.710 --> 19:57:00.720 align:start position:0% using it for work you know who entered 19:57:00.720 --> 19:57:02.630 align:start position:0% using it for work you know who entered data<19:57:00.960> this<19:57:01.144> all<19:57:01.256> needs<19:57:01.552> to<19:57:01.616> be<19:57:01.744> clear<19:57:01.976> what 19:57:02.630 --> 19:57:02.640 align:start position:0% data this all needs to be clear what 19:57:02.640 --> 19:57:04.670 align:start position:0% data this all needs to be clear what applications<19:57:03.120> can<19:57:03.536> they<19:57:03.784> use 19:57:04.670 --> 19:57:04.680 align:start position:0% applications can they use 19:57:04.680 --> 19:57:06.822 align:start position:0% applications can they use and<19:57:05.104> what<19:57:05.280> can<19:57:05.400> be<19:57:05.576> taken<19:57:05.936> off-site<19:57:06.424> as<19:57:06.720> well 19:57:06.822 --> 19:57:06.832 align:start position:0% and what can be taken off-site as well 19:57:06.832 --> 19:57:08.686 align:start position:0% and what can be taken off-site as well you<19:57:07.440> need<19:57:07.616> to<19:57:07.744> decide<19:57:07.976> what<19:57:08.216> hardware<19:57:08.400> and 19:57:08.686 --> 19:57:08.696 align:start position:0% you need to decide what hardware and 19:57:08.696 --> 19:57:10.670 align:start position:0% you need to decide what hardware and software<19:57:09.000> can<19:57:09.240> be<19:57:09.360> taken<19:57:09.656> off<19:57:09.784> site 19:57:10.670 --> 19:57:10.680 align:start position:0% software can be taken off site 19:57:10.680 --> 19:57:13.182 align:start position:0% software can be taken off site the<19:57:11.160> acceptable<19:57:11.576> use<19:57:11.824> policy<19:57:12.360> uh<19:57:12.784> stop<19:57:12.960> and 19:57:13.182 --> 19:57:13.192 align:start position:0% the acceptable use policy uh stop and 19:57:13.192 --> 19:57:15.526 align:start position:0% the acceptable use policy uh stop and search<19:57:13.696> depends<19:57:14.696> where<19:57:14.872> you<19:57:15.056> are<19:57:15.176> and<19:57:15.360> how 19:57:15.526 --> 19:57:15.536 align:start position:0% search depends where you are and how 19:57:15.536 --> 19:57:17.326 align:start position:0% search depends where you are and how secure<19:57:15.784> the<19:57:15.960> site<19:57:16.080> is<19:57:16.320> but<19:57:16.552> people<19:57:16.744> can<19:57:17.040> search 19:57:17.326 --> 19:57:17.336 align:start position:0% secure the site is but people can search 19:57:17.336 --> 19:57:18.710 align:start position:0% secure the site is but people can search your<19:57:17.640> bag 19:57:18.710 --> 19:57:18.720 align:start position:0% your bag 19:57:18.720 --> 19:57:20.926 align:start position:0% your bag uh<19:57:19.256> speaking<19:57:19.744> of<19:57:19.800> which<19:57:20.040> I<19:57:20.400> already<19:57:20.576> mentioned 19:57:20.926 --> 19:57:20.936 align:start position:0% uh speaking of which I already mentioned 19:57:20.936 --> 19:57:22.910 align:start position:0% uh speaking of which I already mentioned the<19:57:21.120> acceptable<19:57:21.536> use<19:57:21.832> policy<19:57:22.320> there<19:57:22.744> should 19:57:22.910 --> 19:57:22.920 align:start position:0% the acceptable use policy there should 19:57:22.920 --> 19:57:25.246 align:start position:0% the acceptable use policy there should be<19:57:23.040> a<19:57:23.160> security<19:57:23.336> policy<19:57:24.000> included 19:57:25.246 --> 19:57:25.256 align:start position:0% be a security policy included 19:57:25.256 --> 19:57:27.350 align:start position:0% be a security policy included how<19:57:25.856> the<19:57:26.040> network<19:57:26.160> should<19:57:26.640> and<19:57:26.872> shouldn't<19:57:27.240> be 19:57:27.350 --> 19:57:27.360 align:start position:0% how the network should and shouldn't be 19:57:27.360 --> 19:57:28.846 align:start position:0% how the network should and shouldn't be used<19:57:27.536> what<19:57:27.832> you're<19:57:27.960> allowed<19:57:28.256> to<19:57:28.376> do<19:57:28.496> it<19:57:28.680> should 19:57:28.846 --> 19:57:28.856 align:start position:0% used what you're allowed to do it should 19:57:28.856 --> 19:57:30.414 align:start position:0% used what you're allowed to do it should be<19:57:28.976> clearly<19:57:29.280> spelled<19:57:29.640> out<19:57:29.760> and<19:57:30.000> signed 19:57:30.414 --> 19:57:30.424 align:start position:0% be clearly spelled out and signed 19:57:30.424 --> 19:57:33.110 align:start position:0% be clearly spelled out and signed websites<19:57:31.376> you<19:57:31.552> can<19:57:31.680> access<19:57:31.856> I<19:57:32.576> know<19:57:32.760> when<19:57:32.936> I 19:57:33.110 --> 19:57:33.120 align:start position:0% websites you can access I know when I 19:57:33.120 --> 19:57:36.710 align:start position:0% websites you can access I know when I worked<19:57:33.536> at<19:57:33.832> this<19:57:34.496> particular<19:57:34.744> ISP 19:57:36.710 --> 19:57:36.720 align:start position:0% worked at this particular ISP 19:57:36.720 --> 19:57:38.926 align:start position:0% worked at this particular ISP at<19:57:37.192> the<19:57:37.320> end<19:57:37.376> of<19:57:37.504> every<19:57:37.680> month<19:57:37.976> the<19:57:38.400> manager 19:57:38.926 --> 19:57:38.936 align:start position:0% at the end of every month the manager 19:57:38.936 --> 19:57:41.206 align:start position:0% at the end of every month the manager would<19:57:39.360> per<19:57:39.720> employee 19:57:41.206 --> 19:57:41.216 align:start position:0% would per employee 19:57:41.216 --> 19:57:43.134 align:start position:0% would per employee they<19:57:41.640> would<19:57:41.760> have<19:57:41.936> a<19:57:42.120> list<19:57:42.296> of<19:57:42.600> every<19:57:42.896> single 19:57:43.134 --> 19:57:43.144 align:start position:0% they would have a list of every single 19:57:43.144 --> 19:57:45.950 align:start position:0% they would have a list of every single website<19:57:43.552> you<19:57:43.920> went<19:57:44.104> to<19:57:44.360> and<19:57:45.360> how<19:57:45.600> many<19:57:45.720> minutes 19:57:45.950 --> 19:57:45.960 align:start position:0% website you went to and how many minutes 19:57:45.960 --> 19:57:48.710 align:start position:0% website you went to and how many minutes you<19:57:46.320> spent<19:57:46.552> on<19:57:46.976> the<19:57:47.216> website<19:57:48.120> so<19:57:48.360> if<19:57:48.536> you've 19:57:48.710 --> 19:57:48.720 align:start position:0% you spent on the website so if you've 19:57:48.720 --> 19:57:51.774 align:start position:0% you spent on the website so if you've spent<19:57:48.896> 60<19:57:49.144> Minutes<19:57:49.696> on<19:57:50.696> whatever<19:57:51.000> say<19:57:51.480> eBay 19:57:51.774 --> 19:57:51.784 align:start position:0% spent 60 Minutes on whatever say eBay 19:57:51.784 --> 19:57:53.390 align:start position:0% spent 60 Minutes on whatever say eBay even<19:57:52.144> though<19:57:52.376> and<19:57:52.744> we<19:57:52.920> couldn't<19:57:52.976> do<19:57:53.216> it<19:57:53.280> but 19:57:53.390 --> 19:57:53.400 align:start position:0% even though and we couldn't do it but 19:57:53.400 --> 19:57:55.134 align:start position:0% even though and we couldn't do it but say<19:57:53.640> you<19:57:53.760> were<19:57:53.872> found<19:57:54.056> to<19:57:54.240> be<19:57:54.360> on<19:57:54.480> eBay<19:57:54.656> for<19:57:54.960> 60 19:57:55.134 --> 19:57:55.144 align:start position:0% say you were found to be on eBay for 60 19:57:55.144 --> 19:57:57.414 align:start position:0% say you were found to be on eBay for 60 minutes<19:57:55.440> then<19:57:56.160> obviously<19:57:56.640> there's<19:57:57.176> going<19:57:57.360> to 19:57:57.414 --> 19:57:57.424 align:start position:0% minutes then obviously there's going to 19:57:57.424 --> 19:57:58.790 align:start position:0% minutes then obviously there's going to be<19:57:57.480> a<19:57:57.600> consequence<19:57:58.080> you'd<19:57:58.320> either<19:57:58.440> be<19:57:58.616> told 19:57:58.790 --> 19:57:58.800 align:start position:0% be a consequence you'd either be told 19:57:58.800 --> 19:58:01.246 align:start position:0% be a consequence you'd either be told off<19:57:59.040> written<19:57:59.512> or<19:57:59.696> an<19:57:59.824> invariable<19:58:00.296> warning<19:58:00.720> or 19:58:01.246 --> 19:58:01.256 align:start position:0% off written or an invariable warning or 19:58:01.256 --> 19:58:03.590 align:start position:0% off written or an invariable warning or you<19:58:01.376> could<19:58:01.504> be<19:58:01.616> sacked 19:58:03.590 --> 19:58:03.600 align:start position:0% you could be sacked 19:58:03.600 --> 19:58:06.470 align:start position:0% you could be sacked and<19:58:04.080> what<19:58:04.256> you<19:58:04.376> can<19:58:04.496> and<19:58:04.680> can't<19:58:04.920> download<19:58:05.480> a 19:58:06.470 --> 19:58:06.480 align:start position:0% and what you can and can't download a 19:58:06.480 --> 19:58:08.206 align:start position:0% and what you can and can't download a social<19:58:06.784> media<19:58:07.192> again<19:58:07.376> this<19:58:07.680> is<19:58:07.800> a<19:58:07.920> killer 19:58:08.206 --> 19:58:08.216 align:start position:0% social media again this is a killer 19:58:08.216 --> 19:58:10.310 align:start position:0% social media again this is a killer you're<19:58:08.336> not<19:58:08.464> really<19:58:08.576> being<19:58:08.760> paid<19:58:09.120> at<19:58:09.784> work<19:58:10.016> to 19:58:10.310 --> 19:58:10.320 align:start position:0% you're not really being paid at work to 19:58:10.320 --> 19:58:11.990 align:start position:0% you're not really being paid at work to social<19:58:10.680> media<19:58:11.040> unless<19:58:11.336> it's<19:58:11.512> part<19:58:11.696> of<19:58:11.872> your 19:58:11.990 --> 19:58:12.000 align:start position:0% social media unless it's part of your 19:58:12.000 --> 19:58:16.070 align:start position:0% social media unless it's part of your job<19:58:12.240> for<19:58:12.600> example<19:58:12.832> digital<19:58:13.744> marketing<19:58:14.784> NDA<19:58:15.784> as 19:58:16.070 --> 19:58:16.080 align:start position:0% job for example digital marketing NDA as 19:58:16.080 --> 19:58:17.686 align:start position:0% job for example digital marketing NDA as well<19:58:16.256> these<19:58:16.616> are<19:58:16.680> these<19:58:17.040> are<19:58:17.160> huge<19:58:17.464> in<19:58:17.576> the 19:58:17.686 --> 19:58:17.696 align:start position:0% well these are these are huge in the 19:58:17.696 --> 19:58:19.366 align:start position:0% well these are these are huge in the corporate<19:58:18.056> environment 19:58:19.366 --> 19:58:19.376 align:start position:0% corporate environment 19:58:19.376 --> 19:58:22.310 align:start position:0% corporate environment protects<19:58:20.280> non-public<19:58:20.696> information<19:58:21.320> so 19:58:22.310 --> 19:58:22.320 align:start position:0% protects non-public information so 19:58:22.320 --> 19:58:24.230 align:start position:0% protects non-public information so you're<19:58:22.680> you're<19:58:22.976> learning<19:58:23.464> about<19:58:23.640> customers 19:58:24.230 --> 19:58:24.240 align:start position:0% you're you're learning about customers 19:58:24.240 --> 19:58:27.646 align:start position:0% you're you're learning about customers names<19:58:24.536> phone<19:58:25.192> phone<19:58:25.744> details<19:58:26.512> uh<19:58:27.176> who<19:58:27.480> are<19:58:27.600> the 19:58:27.646 --> 19:58:27.656 align:start position:0% names phone phone details uh who are the 19:58:27.656 --> 19:58:29.094 align:start position:0% names phone phone details uh who are the key<19:58:27.832> contacts<19:58:28.376> all<19:58:28.552> of<19:58:28.744> this<19:58:28.856> kind<19:58:28.976> of 19:58:29.094 --> 19:58:29.104 align:start position:0% key contacts all of this kind of 19:58:29.104 --> 19:58:31.542 align:start position:0% key contacts all of this kind of information<19:58:29.536> what<19:58:30.536> are<19:58:30.656> the<19:58:30.832> consequences<19:58:31.256> of 19:58:31.542 --> 19:58:31.552 align:start position:0% information what are the consequences of 19:58:31.552 --> 19:58:33.950 align:start position:0% information what are the consequences of the<19:58:31.680> breach<19:58:31.976> this<19:58:32.696> could<19:58:32.872> be 19:58:33.950 --> 19:58:33.960 align:start position:0% the breach this could be 19:58:33.960 --> 19:58:37.366 align:start position:0% the breach this could be um<19:58:34.016> Criminal 19:58:37.366 --> 19:58:37.376 align:start position:0% 19:58:37.376 --> 19:58:40.070 align:start position:0% or<19:58:38.216> it<19:58:38.400> could<19:58:38.512> be<19:58:38.640> civil<19:58:39.120> so<19:58:39.424> you<19:58:39.600> could<19:58:39.720> have 19:58:40.070 --> 19:58:40.080 align:start position:0% or it could be civil so you could have 19:58:40.080 --> 19:58:44.502 align:start position:0% or it could be civil so you could have to<19:58:40.256> pay<19:58:40.440> Financial<19:58:40.744> penalties 19:58:44.502 --> 19:58:44.512 align:start position:0% 19:58:44.512 --> 19:58:45.950 align:start position:0% and<19:58:44.936> this<19:58:45.056> creates<19:58:45.360> a<19:58:45.480> confidential 19:58:45.950 --> 19:58:45.960 align:start position:0% and this creates a confidential 19:58:45.960 --> 19:58:48.166 align:start position:0% and this creates a confidential relationship<19:58:46.496> between<19:58:47.040> the<19:58:47.576> disclosing 19:58:48.166 --> 19:58:48.176 align:start position:0% relationship between the disclosing 19:58:48.176 --> 19:58:49.246 align:start position:0% relationship between the disclosing party 19:58:49.246 --> 19:58:49.256 align:start position:0% party 19:58:49.256 --> 19:58:51.414 align:start position:0% party and<19:58:49.744> the<19:58:49.856> receiving<19:58:50.160> party 19:58:51.414 --> 19:58:51.424 align:start position:0% and the receiving party 19:58:51.424 --> 19:58:54.470 align:start position:0% and the receiving party your<19:58:52.080> boss<19:58:52.320> or<19:58:52.552> your<19:58:52.800> company<19:58:52.976> and<19:58:53.640> you<19:58:53.872> which 19:58:54.470 --> 19:58:54.480 align:start position:0% your boss or your company and you which 19:58:54.480 --> 19:58:56.686 align:start position:0% your boss or your company and you which is<19:58:54.656> fair 19:58:56.686 --> 19:58:56.696 align:start position:0% is fair 19:58:56.696 --> 19:58:59.270 align:start position:0% is fair uh<19:58:57.424> the<19:58:57.536> system<19:58:57.656> life<19:58:58.080> cycle<19:58:58.320> which<19:58:58.680> is<19:58:58.800> asset 19:58:59.270 --> 19:58:59.280 align:start position:0% uh the system life cycle which is asset 19:58:59.280 --> 19:59:01.542 align:start position:0% uh the system life cycle which is asset disposal<19:58:59.824> something<19:59:00.240> is<19:59:00.536> brought<19:59:00.784> into 19:59:01.542 --> 19:59:01.552 align:start position:0% disposal something is brought into 19:59:01.552 --> 19:59:04.246 align:start position:0% disposal something is brought into um<19:59:01.616> Commission 19:59:04.246 --> 19:59:04.256 align:start position:0% um Commission 19:59:04.256 --> 19:59:06.774 align:start position:0% um Commission oh<19:59:04.744> sorry<19:59:04.920> I<19:59:05.040> did<19:59:05.160> this<19:59:05.280> in<19:59:05.464> a<19:59:05.640> weird<19:59:05.824> way<19:59:06.176> so 19:59:06.774 --> 19:59:06.784 align:start position:0% oh sorry I did this in a weird way so 19:59:06.784 --> 19:59:08.686 align:start position:0% oh sorry I did this in a weird way so integrate<19:59:07.256> devices<19:59:07.616> some<19:59:08.040> something<19:59:08.336> is 19:59:08.686 --> 19:59:08.696 align:start position:0% integrate devices some something is 19:59:08.696 --> 19:59:10.846 align:start position:0% integrate devices some something is brought<19:59:08.936> into<19:59:09.296> the<19:59:09.536> network<19:59:09.784> and<19:59:10.552> then<19:59:10.680> it 19:59:10.846 --> 19:59:10.856 align:start position:0% brought into the network and then it 19:59:10.856 --> 19:59:12.110 align:start position:0% brought into the network and then it would<19:59:10.976> have<19:59:11.104> to<19:59:11.216> go<19:59:11.336> through<19:59:11.512> a<19:59:11.760> chain<19:59:11.872> of 19:59:12.110 --> 19:59:12.120 align:start position:0% would have to go through a chain of 19:59:12.120 --> 19:59:14.990 align:start position:0% would have to go through a chain of events<19:59:12.480> for<19:59:12.656> example<19:59:12.960> a<19:59:13.800> router<19:59:14.216> would<19:59:14.824> all 19:59:14.990 --> 19:59:15.000 align:start position:0% events for example a router would all 19:59:15.000 --> 19:59:17.206 align:start position:0% events for example a router would all have<19:59:15.176> to<19:59:15.296> be<19:59:15.424> cabled<19:59:15.960> up<19:59:16.080> then<19:59:16.552> it'd<19:59:16.800> be<19:59:16.856> passed 19:59:17.206 --> 19:59:17.216 align:start position:0% have to be cabled up then it'd be passed 19:59:17.216 --> 19:59:20.094 align:start position:0% have to be cabled up then it'd be passed on<19:59:17.280> to<19:59:17.512> another<19:59:17.696> team<19:59:18.120> to<19:59:19.080> do 19:59:20.094 --> 19:59:20.104 align:start position:0% on to another team to do 19:59:20.104 --> 19:59:22.790 align:start position:0% on to another team to do um<19:59:20.640> username<19:59:21.600> and<19:59:21.784> passwords<19:59:22.320> for<19:59:22.496> example 19:59:22.790 --> 19:59:22.800 align:start position:0% um username and passwords for example 19:59:22.800 --> 19:59:25.182 align:start position:0% um username and passwords for example then<19:59:23.512> it<19:59:23.696> might<19:59:23.872> go<19:59:24.056> to<19:59:24.240> the<19:59:24.480> security<19:59:24.720> team 19:59:25.182 --> 19:59:25.192 align:start position:0% then it might go to the security team 19:59:25.192 --> 19:59:27.166 align:start position:0% then it might go to the security team for<19:59:25.504> configuration 19:59:27.166 --> 19:59:27.176 align:start position:0% for configuration 19:59:27.176 --> 19:59:30.166 align:start position:0% for configuration then<19:59:27.656> it<19:59:27.832> might<19:59:28.016> go<19:59:28.144> to<19:59:28.320> the<19:59:28.496> backup<19:59:28.856> team<19:59:29.176> to 19:59:30.166 --> 19:59:30.176 align:start position:0% then it might go to the backup team to 19:59:30.176 --> 19:59:32.686 align:start position:0% then it might go to the backup team to make<19:59:30.360> sure<19:59:30.536> that<19:59:30.784> it<19:59:30.896> could<19:59:31.144> and<19:59:31.504> they<19:59:31.856> can 19:59:32.686 --> 19:59:32.696 align:start position:0% make sure that it could and they can 19:59:32.696 --> 19:59:35.750 align:start position:0% make sure that it could and they can download<19:59:33.656> files<19:59:34.256> and<19:59:34.376> configurations<19:59:34.976> and 19:59:35.750 --> 19:59:35.760 align:start position:0% download files and configurations and 19:59:35.760 --> 19:59:37.966 align:start position:0% download files and configurations and recover<19:59:36.000> it<19:59:36.176> if<19:59:36.296> there's<19:59:36.424> a<19:59:36.656> problem 19:59:37.966 --> 19:59:37.976 align:start position:0% recover it if there's a problem 19:59:37.976 --> 19:59:40.182 align:start position:0% recover it if there's a problem and<19:59:38.464> procedure<19:59:39.056> to<19:59:39.176> decommission<19:59:39.784> what 19:59:40.182 --> 19:59:40.192 align:start position:0% and procedure to decommission what 19:59:40.192 --> 19:59:43.606 align:start position:0% and procedure to decommission what happens<19:59:40.576> uh<19:59:41.576> does<19:59:42.056> it<19:59:42.176> go<19:59:42.296> in<19:59:42.480> the<19:59:42.600> bin<19:59:42.896> does<19:59:43.376> it 19:59:43.606 --> 19:59:43.616 align:start position:0% happens uh does it go in the bin does it 19:59:43.616 --> 19:59:46.310 align:start position:0% happens uh does it go in the bin does it go<19:59:43.744> to<19:59:43.976> a<19:59:44.216> shop<19:59:44.400> for<19:59:44.760> sale 19:59:46.310 --> 19:59:46.320 align:start position:0% go to a shop for sale 19:59:46.320 --> 19:59:48.414 align:start position:0% go to a shop for sale and<19:59:46.800> as<19:59:46.920> I've<19:59:47.104> already<19:59:47.280> said<19:59:47.576> and<19:59:48.056> if<19:59:48.240> it's 19:59:48.414 --> 19:59:48.424 align:start position:0% and as I've already said and if it's 19:59:48.424 --> 19:59:49.734 align:start position:0% and as I've already said and if it's going<19:59:48.480> to<19:59:48.536> go<19:59:48.720> for<19:59:48.832> sale<19:59:48.960> then<19:59:49.144> all<19:59:49.376> the<19:59:49.504> date 19:59:49.734 --> 19:59:49.744 align:start position:0% going to go for sale then all the date 19:59:49.744 --> 19:59:52.734 align:start position:0% going to go for sale then all the date all<19:59:50.104> the<19:59:50.216> data<19:59:50.696> needs<19:59:50.872> to<19:59:50.936> be<19:59:51.056> removed<19:59:51.744> hard 19:59:52.734 --> 19:59:52.744 align:start position:0% all the data needs to be removed hard 19:59:52.744 --> 19:59:54.166 align:start position:0% all the data needs to be removed hard drives<19:59:52.976> are<19:59:53.160> they<19:59:53.336> going<19:59:53.400> to<19:59:53.512> be<19:59:53.576> scrubbed<19:59:54.000> are 19:59:54.166 --> 19:59:54.176 align:start position:0% drives are they going to be scrubbed are 19:59:54.176 --> 19:59:56.454 align:start position:0% drives are they going to be scrubbed are they<19:59:54.360> going<19:59:54.424> to<19:59:54.600> be<19:59:54.720> physically<19:59:55.680> destroyed<19:59:56.216> in 19:59:56.454 --> 19:59:56.464 align:start position:0% they going to be physically destroyed in 19:59:56.464 --> 19:59:59.750 align:start position:0% they going to be physically destroyed in a<19:59:56.640> furnace<19:59:57.000> or<19:59:57.480> some<19:59:57.896> other<19:59:58.144> device<19:59:58.576> what<19:59:59.576> are 19:59:59.750 --> 19:59:59.760 align:start position:0% a furnace or some other device what are 19:59:59.760 --> 20:00:01.430 align:start position:0% a furnace or some other device what are the<19:59:59.872> laws<20:00:00.176> for<20:00:00.360> recycling<20:00:00.720> a<20:00:01.256> lot<20:00:01.376> of 20:00:01.430 --> 20:00:01.440 align:start position:0% the laws for recycling a lot of 20:00:01.440 --> 20:00:04.134 align:start position:0% the laws for recycling a lot of countries<20:00:02.040> now<20:00:02.280> are<20:00:02.464> really<20:00:02.696> hot<20:00:03.000> on<20:00:03.240> and 20:00:04.134 --> 20:00:04.144 align:start position:0% countries now are really hot on and 20:00:04.144 --> 20:00:05.990 align:start position:0% countries now are really hot on and non-recyclable<20:00:04.800> stuff<20:00:05.160> so<20:00:05.400> if<20:00:05.640> you<20:00:05.872> can't 20:00:05.990 --> 20:00:06.000 align:start position:0% non-recyclable stuff so if you can't 20:00:06.000 --> 20:00:08.454 align:start position:0% non-recyclable stuff so if you can't destroy<20:00:06.600> it<20:00:06.784> how<20:00:07.504> are<20:00:07.616> you<20:00:07.744> going<20:00:07.920> to<20:00:08.040> render 20:00:08.454 --> 20:00:08.464 align:start position:0% destroy it how are you going to render 20:00:08.464 --> 20:00:11.630 align:start position:0% destroy it how are you going to render it<20:00:08.760> and<20:00:09.120> usable<20:00:09.720> or<20:00:09.960> the<20:00:10.144> data<20:00:10.440> on<20:00:10.552> it<20:00:10.744> unusable 20:00:11.630 --> 20:00:11.640 align:start position:0% it and usable or the data on it unusable 20:00:11.640 --> 20:00:13.790 align:start position:0% it and usable or the data on it unusable certainly 20:00:13.790 --> 20:00:13.800 align:start position:0% certainly 20:00:13.800 --> 20:00:16.134 align:start position:0% certainly safety<20:00:14.640> procedures 20:00:16.134 --> 20:00:16.144 align:start position:0% safety procedures 20:00:16.144 --> 20:00:18.886 align:start position:0% safety procedures um 20:00:18.886 --> 20:00:18.896 align:start position:0% 20:00:18.896 --> 20:00:20.886 align:start position:0% so<20:00:19.376> who<20:00:19.552> can<20:00:19.744> troubleshoot<20:00:20.216> the<20:00:20.400> equipment 20:00:20.886 --> 20:00:20.896 align:start position:0% so who can troubleshoot the equipment 20:00:20.896 --> 20:00:23.390 align:start position:0% so who can troubleshoot the equipment people<20:00:21.896> need<20:00:22.192> to<20:00:22.376> know<20:00:22.496> what<20:00:22.800> air<20:00:22.976> their<20:00:23.280> job 20:00:23.390 --> 20:00:23.400 align:start position:0% people need to know what air their job 20:00:23.400 --> 20:00:25.670 align:start position:0% people need to know what air their job is<20:00:23.640> you<20:00:23.872> could<20:00:24.296> um 20:00:25.670 --> 20:00:25.680 align:start position:0% is you could um 20:00:25.680 --> 20:00:28.134 align:start position:0% is you could um ignore<20:00:26.280> that<20:00:26.464> sorry<20:00:26.656> authorized<20:00:27.656> Personnel 20:00:28.134 --> 20:00:28.144 align:start position:0% ignore that sorry authorized Personnel 20:00:28.144 --> 20:00:30.350 align:start position:0% ignore that sorry authorized Personnel who<20:00:28.496> can<20:00:28.680> cable<20:00:28.976> stuff<20:00:29.336> who's<20:00:29.760> been<20:00:30.056> trained 20:00:30.350 --> 20:00:30.360 align:start position:0% who can cable stuff who's been trained 20:00:30.360 --> 20:00:33.046 align:start position:0% who can cable stuff who's been trained who's<20:00:30.656> insured<20:00:31.256> monitors<20:00:32.216> as<20:00:32.464> well<20:00:32.640> certainly 20:00:33.046 --> 20:00:33.056 align:start position:0% who's insured monitors as well certainly 20:00:33.056 --> 20:00:35.862 align:start position:0% who's insured monitors as well certainly the<20:00:33.240> old<20:00:33.680> cathode<20:00:34.680> ray<20:00:34.976> monitors<20:00:35.464> there<20:00:35.696> was 20:00:35.862 --> 20:00:35.872 align:start position:0% the old cathode ray monitors there was 20:00:35.872 --> 20:00:38.390 align:start position:0% the old cathode ray monitors there was the<20:00:36.000> back<20:00:36.120> of<20:00:36.296> them<20:00:36.480> and<20:00:37.256> the<20:00:37.440> front 20:00:38.390 --> 20:00:38.400 align:start position:0% the back of them and the front 20:00:38.400 --> 20:00:41.390 align:start position:0% the back of them and the front uh<20:00:39.176> just<20:00:40.144> massive<20:00:40.496> things<20:00:40.680> it<20:00:40.920> would<20:00:41.040> take<20:00:41.216> two 20:00:41.390 --> 20:00:41.400 align:start position:0% uh just massive things it would take two 20:00:41.400 --> 20:00:43.606 align:start position:0% uh just massive things it would take two people<20:00:41.640> to<20:00:41.936> carry<20:00:42.240> them<20:00:42.424> and<20:00:43.016> they'd<20:00:43.256> have<20:00:43.376> a 20:00:43.606 --> 20:00:43.616 align:start position:0% people to carry them and they'd have a 20:00:43.616 --> 20:00:45.350 align:start position:0% people to carry them and they'd have a massive<20:00:43.856> electricity<20:00:44.336> electrical<20:00:45.176> current 20:00:45.350 --> 20:00:45.360 align:start position:0% massive electricity electrical current 20:00:45.360 --> 20:00:47.750 align:start position:0% massive electricity electrical current going<20:00:45.720> in<20:00:46.016> through<20:00:46.192> them<20:00:46.440> as<20:00:46.616> well<20:00:46.744> even<20:00:47.400> when 20:00:47.750 --> 20:00:47.760 align:start position:0% going in through them as well even when 20:00:47.760 --> 20:00:49.430 align:start position:0% going in through them as well even when unplugged 20:00:49.430 --> 20:00:49.440 align:start position:0% unplugged 20:00:49.440 --> 20:00:52.366 align:start position:0% unplugged um<20:00:49.504> it<20:00:49.744> still<20:00:49.920> held<20:00:50.280> a<20:00:50.400> massive<20:00:50.760> uh<20:00:51.056> current 20:00:52.366 --> 20:00:52.376 align:start position:0% um it still held a massive uh current 20:00:52.376 --> 20:00:54.110 align:start position:0% um it still held a massive uh current and<20:00:53.040> could<20:00:53.280> have<20:00:53.400> shocked<20:00:53.760> somebody<20:00:53.872> or 20:00:54.110 --> 20:00:54.120 align:start position:0% and could have shocked somebody or 20:00:54.120 --> 20:00:55.790 align:start position:0% and could have shocked somebody or killed<20:00:54.424> them 20:00:55.790 --> 20:00:55.800 align:start position:0% killed them 20:00:55.800 --> 20:00:59.270 align:start position:0% killed them who<20:00:56.464> can<20:00:56.640> move<20:00:56.824> what<20:00:57.176> uh<20:00:57.656> heavy<20:00:57.960> lifting<20:00:58.552> so<20:00:59.104> I 20:00:59.270 --> 20:00:59.280 align:start position:0% who can move what uh heavy lifting so I 20:00:59.280 --> 20:01:02.502 align:start position:0% who can move what uh heavy lifting so I work<20:00:59.512> for<20:00:59.824> as<20:01:00.120> I<20:01:00.296> said<20:01:00.360> an<20:01:00.656> ISP<20:01:01.192> and<20:01:01.920> I<20:01:02.104> work<20:01:02.280> for 20:01:02.502 --> 20:01:02.512 align:start position:0% work for as I said an ISP and I work for 20:01:02.512 --> 20:01:05.326 align:start position:0% work for as I said an ISP and I work for the<20:01:02.696> network<20:01:02.872> support<20:01:03.296> team<20:01:03.720> I<20:01:04.616> remotely 20:01:05.326 --> 20:01:05.336 align:start position:0% the network support team I remotely 20:01:05.336 --> 20:01:08.862 align:start position:0% the network support team I remotely accessed<20:01:06.000> routers<20:01:06.720> and<20:01:07.440> switches<20:01:07.976> firewalls 20:01:08.862 --> 20:01:08.872 align:start position:0% accessed routers and switches firewalls 20:01:08.872 --> 20:01:12.166 align:start position:0% accessed routers and switches firewalls load<20:01:09.240> balances<20:01:09.744> and<20:01:10.744> one<20:01:10.976> day<20:01:11.216> uh<20:01:11.760> one<20:01:12.000> of<20:01:12.120> the 20:01:12.166 --> 20:01:12.176 align:start position:0% load balances and one day uh one of the 20:01:12.176 --> 20:01:14.686 align:start position:0% load balances and one day uh one of the one<20:01:12.600> of<20:01:12.720> my<20:01:12.784> bosses<20:01:13.256> asked<20:01:14.160> you<20:01:14.336> know<20:01:14.464> you've 20:01:14.686 --> 20:01:14.696 align:start position:0% one of my bosses asked you know you've 20:01:14.696 --> 20:01:16.846 align:start position:0% one of my bosses asked you know you've got<20:01:14.824> racks<20:01:15.424> these<20:01:16.016> big<20:01:16.144> racks<20:01:16.496> that<20:01:16.616> are<20:01:16.800> full 20:01:16.846 --> 20:01:16.856 align:start position:0% got racks these big racks that are full 20:01:16.856 --> 20:01:19.366 align:start position:0% got racks these big racks that are full of<20:01:17.040> really<20:01:17.336> heavy<20:01:17.696> equipment<20:01:18.120> and<20:01:18.960> some<20:01:19.080> of<20:01:19.256> it 20:01:19.366 --> 20:01:19.376 align:start position:0% of really heavy equipment and some of it 20:01:19.376 --> 20:01:21.470 align:start position:0% of really heavy equipment and some of it can<20:01:19.552> take<20:01:19.744> up<20:01:19.920> a<20:01:20.040> half<20:01:20.216> rack<20:01:20.576> a<20:01:20.760> massive<20:01:21.056> Cisco 20:01:21.470 --> 20:01:21.480 align:start position:0% can take up a half rack a massive Cisco 20:01:21.480 --> 20:01:23.862 align:start position:0% can take up a half rack a massive Cisco switch<20:01:22.256> and<20:01:22.680> he<20:01:22.856> came<20:01:23.040> and<20:01:23.160> asked<20:01:23.400> me<20:01:23.464> if<20:01:23.640> I 20:01:23.862 --> 20:01:23.872 align:start position:0% switch and he came and asked me if I 20:01:23.872 --> 20:01:26.750 align:start position:0% switch and he came and asked me if I could<20:01:24.000> remove<20:01:24.360> one<20:01:24.784> of<20:01:24.960> the<20:01:25.080> switches<20:01:25.616> and<20:01:26.400> put 20:01:26.750 --> 20:01:26.760 align:start position:0% could remove one of the switches and put 20:01:26.760 --> 20:01:29.454 align:start position:0% could remove one of the switches and put a<20:01:26.936> new<20:01:27.056> one<20:01:27.240> in<20:01:27.480> now<20:01:28.376> I<20:01:28.800> wasn't<20:01:28.920> actually<20:01:29.160> there 20:01:29.454 --> 20:01:29.464 align:start position:0% a new one in now I wasn't actually there 20:01:29.464 --> 20:01:31.246 align:start position:0% a new one in now I wasn't actually there for<20:01:29.640> that<20:01:29.824> this<20:01:30.120> is<20:01:30.240> down<20:01:30.536> to<20:01:30.784> the<20:01:31.016> hardware 20:01:31.246 --> 20:01:31.256 align:start position:0% for that this is down to the hardware 20:01:31.256 --> 20:01:34.310 align:start position:0% for that this is down to the hardware team<20:01:31.744> at<20:01:32.640> the<20:01:32.760> time<20:01:32.936> this<20:01:33.600> stuff<20:01:33.832> weighed 20:01:34.310 --> 20:01:34.320 align:start position:0% team at the time this stuff weighed 20:01:34.320 --> 20:01:36.470 align:start position:0% team at the time this stuff weighed something<20:01:34.552> likes 20:01:36.470 --> 20:01:36.480 align:start position:0% something likes 20:01:36.480 --> 20:01:37.310 align:start position:0% something likes um 20:01:37.310 --> 20:01:37.320 align:start position:0% um 20:01:37.320 --> 20:01:40.790 align:start position:0% um say<20:01:37.680> 150<20:01:38.576> kilos<20:01:39.120> and<20:01:39.960> he<20:01:40.080> was<20:01:40.192> asking<20:01:40.496> me<20:01:40.552> to 20:01:40.790 --> 20:01:40.800 align:start position:0% say 150 kilos and he was asking me to 20:01:40.800 --> 20:01:42.710 align:start position:0% say 150 kilos and he was asking me to somehow<20:01:41.216> pull<20:01:41.640> it<20:01:41.760> out 20:01:42.710 --> 20:01:42.720 align:start position:0% somehow pull it out 20:01:42.720 --> 20:01:45.646 align:start position:0% somehow pull it out put<20:01:43.144> it<20:01:43.376> somewhere<20:01:43.800> and<20:01:44.872> um<20:01:44.872> put<20:01:45.176> the<20:01:45.360> new<20:01:45.536> one 20:01:45.646 --> 20:01:45.656 align:start position:0% put it somewhere and um put the new one 20:01:45.656 --> 20:01:48.166 align:start position:0% put it somewhere and um put the new one in<20:01:45.832> I<20:01:46.320> wasn't<20:01:46.552> actually<20:01:46.856> trained<20:01:47.512> to<20:01:47.872> install 20:01:48.166 --> 20:01:48.176 align:start position:0% in I wasn't actually trained to install 20:01:48.176 --> 20:01:50.454 align:start position:0% in I wasn't actually trained to install this<20:01:48.536> heavy<20:01:48.832> equipment<20:01:49.144> I<20:01:49.504> I<20:01:49.744> didn't<20:01:49.976> have<20:01:50.280> any 20:01:50.454 --> 20:01:50.464 align:start position:0% this heavy equipment I I didn't have any 20:01:50.464 --> 20:01:53.646 align:start position:0% this heavy equipment I I didn't have any safety<20:01:51.000> equipment<20:01:51.360> I<20:01:52.192> couldn't<20:01:52.376> move<20:01:52.744> it 20:01:53.646 --> 20:01:53.656 align:start position:0% safety equipment I couldn't move it 20:01:53.656 --> 20:01:57.110 align:start position:0% safety equipment I couldn't move it and<20:01:55.016> um<20:01:55.080> maybe<20:01:55.552> he<20:01:55.856> just<20:01:56.040> didn't<20:01:56.280> care<20:01:56.640> or<20:01:56.936> he 20:01:57.110 --> 20:01:57.120 align:start position:0% and um maybe he just didn't care or he 20:01:57.120 --> 20:01:58.366 align:start position:0% and um maybe he just didn't care or he was<20:01:57.240> just<20:01:57.360> ignorant<20:01:57.720> but<20:01:57.896> I<20:01:58.080> had<20:01:58.144> to<20:01:58.256> turn 20:01:58.366 --> 20:01:58.376 align:start position:0% was just ignorant but I had to turn 20:01:58.376 --> 20:01:59.590 align:start position:0% was just ignorant but I had to turn around<20:01:58.552> and<20:01:58.744> say<20:01:58.856> well<20:01:59.040> I'm<20:01:59.216> not<20:01:59.336> actually 20:01:59.590 --> 20:01:59.600 align:start position:0% around and say well I'm not actually 20:01:59.600 --> 20:02:03.230 align:start position:0% around and say well I'm not actually qualified<20:02:00.600> to<20:02:01.440> move<20:02:01.680> this<20:02:02.216> equipment<20:02:02.640> but<20:02:03.000> I 20:02:03.230 --> 20:02:03.240 align:start position:0% qualified to move this equipment but I 20:02:03.240 --> 20:02:06.230 align:start position:0% qualified to move this equipment but I am<20:02:03.536> qualified<20:02:03.896> to<20:02:04.192> support<20:02:04.976> it<20:02:05.336> but<20:02:06.000> I<20:02:06.176> can 20:02:06.230 --> 20:02:06.240 align:start position:0% am qualified to support it but I can 20:02:06.240 --> 20:02:08.630 align:start position:0% am qualified to support it but I can only<20:02:06.360> connect<20:02:06.536> to<20:02:06.720> it<20:02:06.832> over<20:02:07.016> the<20:02:07.192> network 20:02:08.630 --> 20:02:08.640 align:start position:0% only connect to it over the network 20:02:08.640 --> 20:02:10.910 align:start position:0% only connect to it over the network um<20:02:08.760> he<20:02:09.176> wasn't<20:02:09.360> very<20:02:09.600> happy<20:02:09.832> but<20:02:10.256> it's<20:02:10.744> better 20:02:10.910 --> 20:02:10.920 align:start position:0% um he wasn't very happy but it's better 20:02:10.920 --> 20:02:13.494 align:start position:0% um he wasn't very happy but it's better than<20:02:11.104> me<20:02:11.216> breaking<20:02:11.640> my<20:02:11.760> leg<20:02:11.872> or<20:02:12.056> whatever<20:02:12.504> is 20:02:13.494 --> 20:02:13.504 align:start position:0% than me breaking my leg or whatever is 20:02:13.504 --> 20:02:15.646 align:start position:0% than me breaking my leg or whatever is there<20:02:13.616> any<20:02:13.744> safety<20:02:14.160> equipment<20:02:14.656> required 20:02:15.646 --> 20:02:15.656 align:start position:0% there any safety equipment required 20:02:15.656 --> 20:02:17.270 align:start position:0% there any safety equipment required normally<20:02:16.080> when<20:02:16.320> you're<20:02:16.440> installing<20:02:16.800> heavy 20:02:17.270 --> 20:02:17.280 align:start position:0% normally when you're installing heavy 20:02:17.280 --> 20:02:19.966 align:start position:0% normally when you're installing heavy stuff<20:02:17.400> you<20:02:17.696> need<20:02:17.872> a<20:02:18.120> hard<20:02:18.360> hat 20:02:19.966 --> 20:02:19.976 align:start position:0% stuff you need a hard hat 20:02:19.976 --> 20:02:22.790 align:start position:0% stuff you need a hard hat so<20:02:20.640> you<20:02:20.760> you<20:02:21.056> need<20:02:21.360> your<20:02:21.536> hat<20:02:21.896> you<20:02:22.376> need<20:02:22.552> your 20:02:22.790 --> 20:02:22.800 align:start position:0% so you you need your hat you need your 20:02:22.800 --> 20:02:25.134 align:start position:0% so you you need your hat you need your boots<20:02:23.176> uh<20:02:24.176> you've<20:02:24.424> you've<20:02:24.600> got<20:02:24.720> to<20:02:24.832> have<20:02:24.960> read 20:02:25.134 --> 20:02:25.144 align:start position:0% boots uh you've you've got to have read 20:02:25.144 --> 20:02:27.526 align:start position:0% boots uh you've you've got to have read the<20:02:25.256> training<20:02:25.680> manuals 20:02:27.526 --> 20:02:27.536 align:start position:0% the training manuals 20:02:27.536 --> 20:02:30.286 align:start position:0% the training manuals um are<20:02:27.784> you<20:02:28.016> insured<20:02:28.760> and<20:02:29.760> there's<20:02:30.000> a<20:02:30.176> whole 20:02:30.286 --> 20:02:30.296 align:start position:0% um are you insured and there's a whole 20:02:30.296 --> 20:02:32.390 align:start position:0% um are you insured and there's a whole bunch<20:02:30.480> of<20:02:30.600> stuff<20:02:30.896> yeah<20:02:31.616> normally<20:02:31.976> it<20:02:32.160> would<20:02:32.280> go 20:02:32.390 --> 20:02:32.400 align:start position:0% bunch of stuff yeah normally it would go 20:02:32.400 --> 20:02:34.910 align:start position:0% bunch of stuff yeah normally it would go in<20:02:32.576> a<20:02:32.696> trolley<20:02:33.056> again<20:02:33.240> who's<20:02:34.144> who<20:02:34.616> can<20:02:34.800> use 20:02:34.910 --> 20:02:34.920 align:start position:0% in a trolley again who's who can use 20:02:34.920 --> 20:02:36.590 align:start position:0% in a trolley again who's who can use this<20:02:35.160> trolley 20:02:36.590 --> 20:02:36.600 align:start position:0% this trolley 20:02:36.600 --> 20:02:39.710 align:start position:0% this trolley uh<20:02:37.192> electrical<20:02:37.680> circuits<20:02:38.280> certainly<20:02:38.936> in<20:02:39.296> many 20:02:39.710 --> 20:02:39.720 align:start position:0% uh electrical circuits certainly in many 20:02:39.720 --> 20:02:41.206 align:start position:0% uh electrical circuits certainly in many countries<20:02:40.144> for<20:02:40.376> example<20:02:40.552> Germany<20:02:41.104> and 20:02:41.206 --> 20:02:41.216 align:start position:0% countries for example Germany and 20:02:41.216 --> 20:02:43.790 align:start position:0% countries for example Germany and Australia<20:02:41.696> you<20:02:42.600> can't<20:02:42.784> even<20:02:43.016> change<20:02:43.376> a<20:02:43.616> plug 20:02:43.790 --> 20:02:43.800 align:start position:0% Australia you can't even change a plug 20:02:43.800 --> 20:02:46.790 align:start position:0% Australia you can't even change a plug you<20:02:44.576> have<20:02:44.760> to<20:02:45.056> be<20:02:45.480> a<20:02:45.656> qualified<20:02:46.016> electrician 20:02:46.790 --> 20:02:46.800 align:start position:0% you have to be a qualified electrician 20:02:46.800 --> 20:02:51.286 align:start position:0% you have to be a qualified electrician to<20:02:47.280> access<20:02:47.464> electronic<20:02:48.360> equipment 20:02:51.286 --> 20:02:51.296 align:start position:0% 20:02:51.296 --> 20:02:52.430 align:start position:0% all<20:02:51.480> right<20:02:51.536> so<20:02:51.720> we've<20:02:51.832> covered<20:02:52.144> a<20:02:52.256> lot<20:02:52.320> of 20:02:52.430 --> 20:02:52.440 align:start position:0% all right so we've covered a lot of 20:02:52.440 --> 20:02:54.526 align:start position:0% all right so we've covered a lot of stuff<20:02:52.616> your<20:02:53.040> user<20:02:53.464> agreement<20:02:53.824> your<20:02:54.360> password 20:02:54.526 --> 20:02:54.536 align:start position:0% stuff your user agreement your password 20:02:54.536 --> 20:02:56.862 align:start position:0% stuff your user agreement your password policy<20:02:55.320> and<20:02:56.104> the<20:02:56.216> levels<20:02:56.576> of<20:02:56.696> password 20:02:56.862 --> 20:02:56.872 align:start position:0% policy and the levels of password 20:02:56.872 --> 20:02:59.990 align:start position:0% policy and the levels of password leaving<20:02:57.656> the<20:02:58.016> company<20:02:58.192> so<20:02:58.744> joining<20:02:59.336> leaving 20:02:59.990 --> 20:03:00.000 align:start position:0% leaving the company so joining leaving 20:03:00.000 --> 20:03:04.670 align:start position:0% leaving the company so joining leaving the<20:03:00.360> company<20:03:00.480> any<20:03:01.376> licensing<20:03:02.480> uh<20:03:03.480> export<20:03:04.256> for 20:03:04.670 --> 20:03:04.680 align:start position:0% the company any licensing uh export for 20:03:04.680 --> 20:03:07.966 align:start position:0% the company any licensing uh export for example<20:03:04.920> security<20:03:05.400> images<20:03:05.936> and<20:03:07.192> um 20:03:07.966 --> 20:03:07.976 align:start position:0% example security images and um 20:03:07.976 --> 20:03:09.710 align:start position:0% example security images and um all<20:03:08.512> this<20:03:08.760> kind<20:03:08.936> of<20:03:09.056> stuff<20:03:09.240> what's<20:03:09.536> it 20:03:09.710 --> 20:03:09.720 align:start position:0% all this kind of stuff what's it 20:03:09.720 --> 20:03:11.270 align:start position:0% all this kind of stuff what's it protected<20:03:10.144> by<20:03:10.320> and<20:03:10.440> what<20:03:10.680> you<20:03:10.800> can<20:03:10.920> explore 20:03:11.270 --> 20:03:11.280 align:start position:0% protected by and what you can explore 20:03:11.280 --> 20:03:14.150 align:start position:0% protected by and what you can explore and<20:03:11.464> import<20:03:11.960> what<20:03:12.960> happens<20:03:13.192> to<20:03:13.504> prevent<20:03:13.800> data 20:03:14.150 --> 20:03:14.160 align:start position:0% and import what happens to prevent data 20:03:14.160 --> 20:03:16.310 align:start position:0% and import what happens to prevent data loss<20:03:14.464> of<20:03:14.512> remote<20:03:14.696> access 20:03:16.310 --> 20:03:16.320 align:start position:0% loss of remote access 20:03:16.320 --> 20:03:17.862 align:start position:0% loss of remote access what<20:03:16.744> happens<20:03:16.856> was<20:03:17.160> that<20:03:17.336> when<20:03:17.512> there's<20:03:17.640> an 20:03:17.862 --> 20:03:17.872 align:start position:0% what happens was that when there's an 20:03:17.872 --> 20:03:20.030 align:start position:0% what happens was that when there's an incident<20:03:18.176> can<20:03:19.144> you<20:03:19.256> bring<20:03:19.440> your<20:03:19.616> own<20:03:19.800> device 20:03:20.030 --> 20:03:20.040 align:start position:0% incident can you bring your own device 20:03:20.040 --> 20:03:21.774 align:start position:0% incident can you bring your own device hopefully<20:03:20.760> not 20:03:21.774 --> 20:03:21.784 align:start position:0% hopefully not 20:03:21.784 --> 20:03:24.646 align:start position:0% hopefully not sign<20:03:22.320> in<20:03:22.552> the<20:03:22.680> acceptable<20:03:23.040> use<20:03:23.336> policy 20:03:24.646 --> 20:03:24.656 align:start position:0% sign in the acceptable use policy 20:03:24.656 --> 20:03:26.566 align:start position:0% sign in the acceptable use policy your<20:03:25.080> non-disclosure 20:03:26.566 --> 20:03:26.576 align:start position:0% your non-disclosure 20:03:26.576 --> 20:03:28.670 align:start position:0% your non-disclosure system<20:03:27.056> life<20:03:27.480> cycle<20:03:27.720> and<20:03:28.144> then<20:03:28.320> finally 20:03:28.670 --> 20:03:28.680 align:start position:0% system life cycle and then finally 20:03:28.680 --> 20:03:30.822 align:start position:0% system life cycle and then finally keeping<20:03:29.160> keeping<20:03:29.824> safe 20:03:30.822 --> 20:03:30.832 align:start position:0% keeping keeping safe 20:03:30.832 --> 20:03:41.360 align:start position:0% keeping keeping safe that's<20:03:31.192> all<20:03:31.376> for<20:03:31.552> now<20:03:31.744> thanks<20:03:32.160> for<20:03:32.336> listening 20:03:41.360 --> 20:03:41.370 align:start position:0% 20:03:41.370 --> 20:03:45.606 align:start position:0% [Music] 20:03:45.606 --> 20:03:45.616 align:start position:0% 20:03:45.616 --> 20:03:52.454 align:start position:0% thank<20:03:46.616> you 20:03:52.454 --> 20:03:52.464 align:start position:0% 20:03:52.464 --> 20:03:56.326 align:start position:0% welcome<20:03:53.464> to<20:03:53.696> module<20:03:54.536> 14<20:03:54.720> lesson<20:03:55.376> 4<20:03:55.616> securing 20:03:56.326 --> 20:03:56.336 align:start position:0% welcome to module 14 lesson 4 securing 20:03:56.336 --> 20:03:59.502 align:start position:0% welcome to module 14 lesson 4 securing the<20:03:56.464> wireless<20:03:56.576> network 20:03:59.502 --> 20:03:59.512 align:start position:0% 20:03:59.512 --> 20:04:01.430 align:start position:0% a<20:03:59.760> few<20:03:59.872> things<20:04:00.120> we<20:04:00.296> want<20:04:00.480> to<20:04:00.600> cover<20:04:00.720> syllabus 20:04:01.430 --> 20:04:01.440 align:start position:0% a few things we want to cover syllabus 20:04:01.440 --> 20:04:07.670 align:start position:0% a few things we want to cover syllabus items<20:04:01.976> uh<20:04:02.336> WPA<20:04:03.016> WPA2<20:04:04.512> tkip<20:04:05.512> rc4 20:04:07.670 --> 20:04:07.680 align:start position:0% items uh WPA WPA2 tkip rc4 20:04:07.680 --> 20:04:10.310 align:start position:0% items uh WPA WPA2 tkip rc4 ccmp<20:04:08.640> AES 20:04:10.310 --> 20:04:10.320 align:start position:0% ccmp AES 20:04:10.320 --> 20:04:11.814 align:start position:0% ccmp AES EAP 20:04:11.814 --> 20:04:11.824 align:start position:0% EAP 20:04:11.824 --> 20:04:18.110 align:start position:0% EAP lots<20:04:12.296> of<20:04:12.360> abbreviations<20:04:12.960> gfn<20:04:13.920> sync 20:04:18.110 --> 20:04:18.120 align:start position:0% 20:04:18.120 --> 20:04:19.966 align:start position:0% if<20:04:18.480> you've<20:04:18.600> been<20:04:18.784> using<20:04:19.080> wireless<20:04:19.320> routers 20:04:19.966 --> 20:04:19.976 align:start position:0% if you've been using wireless routers 20:04:19.976 --> 20:04:21.590 align:start position:0% if you've been using wireless routers for<20:04:20.160> any<20:04:20.280> period<20:04:20.760> of<20:04:20.872> time<20:04:21.000> you've<20:04:21.480> probably 20:04:21.590 --> 20:04:21.600 align:start position:0% for any period of time you've probably 20:04:21.600 --> 20:04:24.230 align:start position:0% for any period of time you've probably heard<20:04:22.016> of<20:04:22.256> WEP<20:04:22.744> which<20:04:23.464> was<20:04:23.640> the<20:04:24.000> first 20:04:24.230 --> 20:04:24.240 align:start position:0% heard of WEP which was the first 20:04:24.240 --> 20:04:26.814 align:start position:0% heard of WEP which was the first protocol<20:04:25.144> used 20:04:26.814 --> 20:04:26.824 align:start position:0% protocol used 20:04:26.824 --> 20:04:29.502 align:start position:0% protocol used um<20:04:26.872> to<20:04:27.296> secure<20:04:27.784> your<20:04:27.960> wireless<20:04:28.144> network<20:04:28.512> it 20:04:29.502 --> 20:04:29.512 align:start position:0% um to secure your wireless network it 20:04:29.512 --> 20:04:31.246 align:start position:0% um to secure your wireless network it was<20:04:30.120> um<20:04:30.120> it's<20:04:30.480> pretty<20:04:30.600> much<20:04:30.784> better<20:04:31.016> than 20:04:31.246 --> 20:04:31.256 align:start position:0% was um it's pretty much better than 20:04:31.256 --> 20:04:34.846 align:start position:0% was um it's pretty much better than nothing<20:04:31.440> I<20:04:31.800> guess<20:04:32.176> but<20:04:33.176> it<20:04:34.080> was<20:04:34.192> flawed<20:04:34.552> very 20:04:34.846 --> 20:04:34.856 align:start position:0% nothing I guess but it was flawed very 20:04:34.856 --> 20:04:37.006 align:start position:0% nothing I guess but it was flawed very easily<20:04:35.160> crackable<20:04:35.640> and<20:04:36.296> quite<20:04:36.600> quickly<20:04:36.832> after 20:04:37.006 --> 20:04:37.016 align:start position:0% easily crackable and quite quickly after 20:04:37.016 --> 20:04:38.750 align:start position:0% easily crackable and quite quickly after it<20:04:37.256> came<20:04:37.504> out<20:04:37.616> they<20:04:37.856> realized<20:04:38.160> they<20:04:38.336> had<20:04:38.512> to 20:04:38.750 --> 20:04:38.760 align:start position:0% it came out they realized they had to 20:04:38.760 --> 20:04:40.734 align:start position:0% it came out they realized they had to upgrade<20:04:39.536> it<20:04:39.720> and<20:04:39.896> replace<20:04:40.016> it<20:04:40.320> with<20:04:40.496> something 20:04:40.734 --> 20:04:40.744 align:start position:0% upgrade it and replace it with something 20:04:40.744 --> 20:04:41.750 align:start position:0% upgrade it and replace it with something better 20:04:41.750 --> 20:04:41.760 align:start position:0% better 20:04:41.760 --> 20:04:45.350 align:start position:0% better and<20:04:42.536> then<20:04:42.784> it's<20:04:42.960> upgraded<20:04:43.504> uh<20:04:44.160> replace<20:04:44.336> with<20:04:44.824> a 20:04:45.350 --> 20:04:45.360 align:start position:0% and then it's upgraded uh replace with a 20:04:45.360 --> 20:04:47.566 align:start position:0% and then it's upgraded uh replace with a Wi-Fi<20:04:45.784> protected<20:04:46.256> access<20:04:46.496> as<20:04:46.920> you<20:04:47.160> can<20:04:47.400> see 20:04:47.566 --> 20:04:47.576 align:start position:0% Wi-Fi protected access as you can see 20:04:47.576 --> 20:04:49.966 align:start position:0% Wi-Fi protected access as you can see the<20:04:47.760> title<20:04:48.120> at<20:04:48.296> the<20:04:48.424> top<20:04:48.536> web<20:04:49.320> is<20:04:49.616> a<20:04:49.800> wireless 20:04:49.966 --> 20:04:49.976 align:start position:0% the title at the top web is a wireless 20:04:49.976 --> 20:04:53.686 align:start position:0% the title at the top web is a wireless equivalent<20:04:50.824> privacy<20:04:51.600> I<20:04:51.832> think<20:04:51.960> it<20:04:52.016> stands<20:04:52.376> for 20:04:53.686 --> 20:04:53.696 align:start position:0% equivalent privacy I think it stands for 20:04:53.696 --> 20:04:59.094 align:start position:0% equivalent privacy I think it stands for from<20:04:54.376> 2003<20:04:55.464> WPA<20:04:56.464> was<20:04:56.824> available<20:04:57.144> it<20:04:58.144> uses<20:04:58.552> as<20:04:58.856> a 20:04:59.094 --> 20:04:59.104 align:start position:0% from 2003 WPA was available it uses as a 20:04:59.104 --> 20:05:01.734 align:start position:0% from 2003 WPA was available it uses as a dynamic<20:04:59.512> key<20:04:59.696> management<20:05:00.080> and<20:05:01.080> it's<20:05:01.256> based<20:05:01.680> on 20:05:01.734 --> 20:05:01.744 align:start position:0% dynamic key management and it's based on 20:05:01.744 --> 20:05:03.846 align:start position:0% dynamic key management and it's based on EAP 20:05:03.846 --> 20:05:03.856 align:start position:0% EAP 20:05:03.856 --> 20:05:07.430 align:start position:0% EAP WPA<20:05:04.856> uses<20:05:05.216> temporal<20:05:05.936> key<20:05:06.120> Integrity<20:05:06.896> protocol 20:05:07.430 --> 20:05:07.440 align:start position:0% WPA uses temporal key Integrity protocol 20:05:07.440 --> 20:05:10.006 align:start position:0% WPA uses temporal key Integrity protocol so<20:05:07.744> I'm<20:05:07.920> glad<20:05:08.104> they<20:05:08.280> do<20:05:08.464> abbreviate<20:05:09.176> it<20:05:09.424> so 20:05:10.006 --> 20:05:10.016 align:start position:0% so I'm glad they do abbreviate it so 20:05:10.016 --> 20:05:11.566 align:start position:0% so I'm glad they do abbreviate it so you've<20:05:10.192> got<20:05:10.320> something<20:05:10.552> like<20:05:10.856> 50<20:05:11.104> trillion 20:05:11.566 --> 20:05:11.576 align:start position:0% you've got something like 50 trillion 20:05:11.576 --> 20:05:14.814 align:start position:0% you've got something like 50 trillion key<20:05:11.824> compilations<20:05:12.424> which<20:05:12.896> is<20:05:13.080> quite<20:05:13.440> a<20:05:13.616> lot 20:05:14.814 --> 20:05:14.824 align:start position:0% key compilations which is quite a lot 20:05:14.824 --> 20:05:16.846 align:start position:0% key compilations which is quite a lot you<20:05:15.424> can<20:05:15.536> use<20:05:15.720> it<20:05:15.896> with<20:05:16.080> radius<20:05:16.496> in<20:05:16.744> the 20:05:16.846 --> 20:05:16.856 align:start position:0% you can use it with radius in the 20:05:16.856 --> 20:05:18.710 align:start position:0% you can use it with radius in the Enterprise<20:05:16.976> we've<20:05:17.512> talked<20:05:17.760> about<20:05:17.760> radius<20:05:18.424> and 20:05:18.710 --> 20:05:18.720 align:start position:0% Enterprise we've talked about radius and 20:05:18.720 --> 20:05:21.230 align:start position:0% Enterprise we've talked about radius and radius<20:05:19.144> servers<20:05:19.744> elsewhere<20:05:20.696> in<20:05:20.872> the<20:05:21.056> course 20:05:21.230 --> 20:05:21.240 align:start position:0% radius servers elsewhere in the course 20:05:21.240 --> 20:05:23.862 align:start position:0% radius servers elsewhere in the course so<20:05:22.080> this<20:05:22.320> basically<20:05:22.856> offloads<20:05:23.512> all<20:05:23.640> of<20:05:23.760> the 20:05:23.862 --> 20:05:23.872 align:start position:0% so this basically offloads all of the 20:05:23.872 --> 20:05:26.206 align:start position:0% so this basically offloads all of the management<20:05:24.120> and<20:05:25.320> um 20:05:26.206 --> 20:05:26.216 align:start position:0% management and um 20:05:26.216 --> 20:05:28.966 align:start position:0% management and um and<20:05:26.600> authorization<20:05:27.600> onto<20:05:28.440> another<20:05:28.552> device 20:05:28.966 --> 20:05:28.976 align:start position:0% and authorization onto another device 20:05:28.976 --> 20:05:32.326 align:start position:0% and authorization onto another device that's<20:05:30.176> um<20:05:30.176> designed<20:05:30.656> for<20:05:30.784> that<20:05:30.960> purpose 20:05:32.326 --> 20:05:32.336 align:start position:0% that's um designed for that purpose 20:05:32.336 --> 20:05:35.454 align:start position:0% that's um designed for that purpose he<20:05:32.824> uses<20:05:33.120> an<20:05:33.360> encrypted<20:05:33.896> hash 20:05:35.454 --> 20:05:35.464 align:start position:0% he uses an encrypted hash 20:05:35.464 --> 20:05:40.790 align:start position:0% he uses an encrypted hash each<20:05:35.872> packet<20:05:36.240> has<20:05:36.480> a<20:05:36.720> unique<20:05:37.016> encryption<20:05:37.744> key 20:05:40.790 --> 20:05:40.800 align:start position:0% 20:05:40.800 --> 20:05:44.566 align:start position:0% a<20:05:41.160> WPA2<20:05:42.120> is<20:05:42.424> based<20:05:42.784> on<20:05:42.896> the<20:05:43.576> 802.11i 20:05:44.566 --> 20:05:44.576 align:start position:0% a WPA2 is based on the 802.11i 20:05:44.576 --> 20:05:47.030 align:start position:0% a WPA2 is based on the 802.11i architecture<20:05:45.240> if<20:05:45.720> you<20:05:45.960> want<20:05:46.376> to<20:05:46.496> prove<20:05:46.856> that 20:05:47.030 --> 20:05:47.040 align:start position:0% architecture if you want to prove that 20:05:47.040 --> 20:05:50.470 align:start position:0% architecture if you want to prove that documentation<20:05:47.960> it<20:05:48.960> can<20:05:49.144> integrate<20:05:49.680> with<20:05:49.856> ATO 20:05:50.470 --> 20:05:50.480 align:start position:0% documentation it can integrate with ATO 20:05:50.480 --> 20:05:53.862 align:start position:0% documentation it can integrate with ATO 2.1<20:05:51.480> x<20:05:51.896> there<20:05:52.680> is<20:05:52.800> they<20:05:53.040> do<20:05:53.104> allude<20:05:53.464> to<20:05:53.576> this<20:05:53.696> I 20:05:53.862 --> 20:05:53.872 align:start position:0% 2.1 x there is they do allude to this I 20:05:53.872 --> 20:05:55.670 align:start position:0% 2.1 x there is they do allude to this I think<20:05:54.000> in<20:05:54.176> these<20:05:54.424> syllabus<20:05:54.784> actually<20:05:55.016> and 20:05:55.670 --> 20:05:55.680 align:start position:0% think in these syllabus actually and 20:05:55.680 --> 20:05:57.774 align:start position:0% think in these syllabus actually and it's<20:05:55.856> a<20:05:56.040> method<20:05:56.280> of<20:05:56.512> authentication<20:05:57.480> and 20:05:57.774 --> 20:05:57.784 align:start position:0% it's a method of authentication and 20:05:57.784 --> 20:06:00.590 align:start position:0% it's a method of authentication and authorization<20:05:58.496> running<20:05:59.464> on<20:05:59.936> their<20:06:00.176> layer<20:06:00.480> 2 20:06:00.590 --> 20:06:00.600 align:start position:0% authorization running on their layer 2 20:06:00.600 --> 20:06:02.502 align:start position:0% authorization running on their layer 2 networks<20:06:01.144> it's<20:06:01.744> covered<20:06:02.104> in<20:06:02.160> quite<20:06:02.336> some 20:06:02.502 --> 20:06:02.512 align:start position:0% networks it's covered in quite some 20:06:02.512 --> 20:06:05.990 align:start position:0% networks it's covered in quite some detail<20:06:02.872> in<20:06:03.056> the<20:06:03.176> Cisco<20:06:03.656> CCNA<20:06:04.376> actually 20:06:05.990 --> 20:06:06.000 align:start position:0% detail in the Cisco CCNA actually 20:06:06.000 --> 20:06:08.566 align:start position:0% detail in the Cisco CCNA actually this<20:06:06.656> allows<20:06:07.080> users<20:06:07.552> and<20:06:07.920> devices<20:06:08.280> to 20:06:08.566 --> 20:06:08.576 align:start position:0% this allows users and devices to 20:06:08.576 --> 20:06:11.326 align:start position:0% this allows users and devices to authenticate<20:06:09.176> with<20:06:09.536> EAP<20:06:09.960> plus<20:06:10.800> it<20:06:11.040> uses 20:06:11.326 --> 20:06:11.336 align:start position:0% authenticate with EAP plus it uses 20:06:11.336 --> 20:06:14.326 align:start position:0% authenticate with EAP plus it uses tacaxa<20:06:12.240> radius<20:06:12.600> so<20:06:13.440> just<20:06:13.680> take<20:06:13.856> a<20:06:14.040> little<20:06:14.160> bit 20:06:14.326 --> 20:06:14.336 align:start position:0% tacaxa radius so just take a little bit 20:06:14.336 --> 20:06:16.430 align:start position:0% tacaxa radius so just take a little bit of<20:06:14.464> setting<20:06:14.824> up<20:06:15.000> but<20:06:15.600> you'll<20:06:15.960> certainly<20:06:16.256> find 20:06:16.430 --> 20:06:16.440 align:start position:0% of setting up but you'll certainly find 20:06:16.440 --> 20:06:20.926 align:start position:0% of setting up but you'll certainly find this<20:06:16.680> in<20:06:16.920> Enterprise<20:06:17.216> level<20:06:17.640> Networks 20:06:20.926 --> 20:06:20.936 align:start position:0% 20:06:20.936 --> 20:06:23.926 align:start position:0% the<20:06:21.480> rc4<20:06:21.896> was<20:06:22.192> replaced<20:06:22.744> by<20:06:22.976> Advanced 20:06:23.926 --> 20:06:23.936 align:start position:0% the rc4 was replaced by Advanced 20:06:23.936 --> 20:06:27.646 align:start position:0% the rc4 was replaced by Advanced encryption<20:06:24.480> standard<20:06:24.896> AES<20:06:25.376> this<20:06:25.976> is<20:06:26.104> 256<20:06:27.056> bits 20:06:27.646 --> 20:06:27.656 align:start position:0% encryption standard AES this is 256 bits 20:06:27.656 --> 20:06:30.590 align:start position:0% encryption standard AES this is 256 bits as<20:06:28.256> a<20:06:28.440> minimum<20:06:28.856> and<20:06:29.216> Beyond 20:06:30.590 --> 20:06:30.600 align:start position:0% as a minimum and Beyond 20:06:30.600 --> 20:06:33.470 align:start position:0% as a minimum and Beyond a<20:06:31.080> TK<20:06:31.504> IP<20:06:31.920> was<20:06:32.160> replaced<20:06:32.576> by<20:06:32.760> computer<20:06:33.056> mode 20:06:33.470 --> 20:06:33.480 align:start position:0% a TK IP was replaced by computer mode 20:06:33.480 --> 20:06:39.910 align:start position:0% a TK IP was replaced by computer mode with<20:06:33.896> Cipher<20:06:34.496> block<20:06:34.744> chaining<20:06:35.464> ccmp 20:06:39.910 --> 20:06:39.920 align:start position:0% 20:06:39.920 --> 20:06:42.710 align:start position:0% uh<20:06:40.920> and<20:06:41.104> I've<20:06:41.216> already<20:06:41.336> mentioned<20:06:41.824> uses<20:06:42.424> uh 20:06:42.710 --> 20:06:42.720 align:start position:0% uh and I've already mentioned uses uh 20:06:42.720 --> 20:06:45.710 align:start position:0% uh and I've already mentioned uses uh encrypted<20:06:43.320> hash 20:06:45.710 --> 20:06:45.720 align:start position:0% encrypted hash 20:06:45.720 --> 20:06:48.590 align:start position:0% encrypted hash each<20:06:46.256> packet<20:06:46.616> has<20:06:46.800> a<20:06:46.976> unique<20:06:47.216> encryption<20:06:47.760> key 20:06:48.590 --> 20:06:48.600 align:start position:0% each packet has a unique encryption key 20:06:48.600 --> 20:06:50.990 align:start position:0% each packet has a unique encryption key um again<20:06:48.832> I<20:06:49.080> mentioned<20:06:49.440> this<20:06:49.552> earlier 20:06:50.990 --> 20:06:51.000 align:start position:0% um again I mentioned this earlier 20:06:51.000 --> 20:06:54.046 align:start position:0% um again I mentioned this earlier MAC<20:06:51.480> address<20:06:51.656> filtering<20:06:52.496> I've<20:06:53.160> just<20:06:53.336> found<20:06:53.760> a 20:06:54.046 --> 20:06:54.056 align:start position:0% MAC address filtering I've just found a 20:06:54.056 --> 20:06:57.230 align:start position:0% MAC address filtering I've just found a basic<20:06:54.480> uh<20:06:55.016> router<20:06:55.552> here<20:06:55.856> and<20:06:56.512> even<20:06:56.696> this<20:06:57.000> cheap 20:06:57.230 --> 20:06:57.240 align:start position:0% basic uh router here and even this cheap 20:06:57.240 --> 20:06:59.862 align:start position:0% basic uh router here and even this cheap one<20:06:57.536> and<20:06:57.960> looks<20:06:58.320> like<20:06:58.856> um<20:06:58.856> maybe<20:06:59.216> it<20:06:59.464> Linksys 20:06:59.862 --> 20:06:59.872 align:start position:0% one and looks like um maybe it Linksys 20:06:59.872 --> 20:07:02.630 align:start position:0% one and looks like um maybe it Linksys one<20:07:00.120> at<20:07:00.536> the<20:07:00.720> looking<20:07:00.960> at<20:07:01.144> the<20:07:01.320> colors<20:07:01.680> you<20:07:02.512> can 20:07:02.630 --> 20:07:02.640 align:start position:0% one at the looking at the colors you can 20:07:02.640 --> 20:07:04.966 align:start position:0% one at the looking at the colors you can use<20:07:02.872> their<20:07:03.120> filtering<20:07:03.656> enable<20:07:04.016> prevents 20:07:04.966 --> 20:07:04.976 align:start position:0% use their filtering enable prevents 20:07:04.976 --> 20:07:06.166 align:start position:0% use their filtering enable prevents clients 20:07:06.166 --> 20:07:06.176 align:start position:0% clients 20:07:06.176 --> 20:07:08.502 align:start position:0% clients um<20:07:06.296> listed<20:07:07.016> from<20:07:07.192> accessing<20:07:07.744> the<20:07:07.920> network<20:07:08.104> if 20:07:08.502 --> 20:07:08.512 align:start position:0% um listed from accessing the network if 20:07:08.512 --> 20:07:10.734 align:start position:0% um listed from accessing the network if you<20:07:08.640> want<20:07:08.760> to<20:07:08.936> stop<20:07:09.240> certain<20:07:09.480> clients<20:07:10.016> or<20:07:10.616> you 20:07:10.734 --> 20:07:10.744 align:start position:0% you want to stop certain clients or you 20:07:10.744 --> 20:07:13.246 align:start position:0% you want to stop certain clients or you can<20:07:10.856> have<20:07:11.040> a<20:07:11.280> permit<20:07:11.576> only<20:07:11.872> list<20:07:12.240> whereas<20:07:13.144> you 20:07:13.246 --> 20:07:13.256 align:start position:0% can have a permit only list whereas you 20:07:13.256 --> 20:07:16.606 align:start position:0% can have a permit only list whereas you manually<20:07:13.616> and<20:07:14.576> decide<20:07:15.240> which<20:07:15.600> packets<20:07:16.144> go<20:07:16.376> and 20:07:16.606 --> 20:07:16.616 align:start position:0% manually and decide which packets go and 20:07:16.616 --> 20:07:20.630 align:start position:0% manually and decide which packets go and which<20:07:17.120> Mac<20:07:18.120> addresses<20:07:18.600> are<20:07:18.784> allowed 20:07:20.630 --> 20:07:20.640 align:start position:0% which Mac addresses are allowed 20:07:20.640 --> 20:07:22.366 align:start position:0% which Mac addresses are allowed uh<20:07:21.240> should<20:07:21.480> be<20:07:21.600> used<20:07:21.720> with<20:07:21.896> other<20:07:22.080> security 20:07:22.366 --> 20:07:22.376 align:start position:0% uh should be used with other security 20:07:22.376 --> 20:07:24.822 align:start position:0% uh should be used with other security features<20:07:22.920> in<20:07:23.280> case<20:07:23.400> of<20:07:23.576> Max<20:07:23.872> spoofing<20:07:24.536> and 20:07:24.822 --> 20:07:24.832 align:start position:0% features in case of Max spoofing and 20:07:24.832 --> 20:07:26.454 align:start position:0% features in case of Max spoofing and it's<20:07:25.192> quite<20:07:25.376> easy<20:07:25.552> certainly<20:07:26.040> on<20:07:26.160> devices 20:07:26.454 --> 20:07:26.464 align:start position:0% it's quite easy certainly on devices 20:07:26.464 --> 20:07:29.390 align:start position:0% it's quite easy certainly on devices I've<20:07:26.824> managed<20:07:27.240> to<20:07:27.832> log<20:07:28.016> in<20:07:28.256> and<20:07:29.040> manually 20:07:29.390 --> 20:07:29.400 align:start position:0% I've managed to log in and manually 20:07:29.400 --> 20:07:32.030 align:start position:0% I've managed to log in and manually change<20:07:29.696> the<20:07:30.000> MAC<20:07:30.240> address<20:07:30.424> of<20:07:30.784> your<20:07:30.960> device 20:07:32.030 --> 20:07:32.040 align:start position:0% change the MAC address of your device 20:07:32.040 --> 20:07:35.630 align:start position:0% change the MAC address of your device and<20:07:32.464> here's<20:07:32.824> a<20:07:33.000> permit<20:07:33.784> list<20:07:34.216> for<20:07:35.216> just<20:07:35.464> a 20:07:35.630 --> 20:07:35.640 align:start position:0% and here's a permit list for just a 20:07:35.640 --> 20:07:40.606 align:start position:0% and here's a permit list for just a random<20:07:36.240> device<20:07:36.424> a<20:07:36.784> random<20:07:37.080> device<20:07:37.320> I<20:07:37.680> found 20:07:40.606 --> 20:07:40.616 align:start position:0% 20:07:40.616 --> 20:07:43.310 align:start position:0% EAP<20:07:41.280> extensible<20:07:42.120> Authentication<20:07:42.784> Protocol 20:07:43.310 --> 20:07:43.320 align:start position:0% EAP extensible Authentication Protocol 20:07:43.320 --> 20:07:45.110 align:start position:0% EAP extensible Authentication Protocol it's<20:07:44.040> a<20:07:44.280> framework<20:07:44.576> used<20:07:44.824> in<20:07:45.000> wireless 20:07:45.110 --> 20:07:45.120 align:start position:0% it's a framework used in wireless 20:07:45.120 --> 20:07:47.566 align:start position:0% it's a framework used in wireless networks<20:07:45.832> they've<20:07:46.144> got<20:07:46.256> an<20:07:46.376> RFC<20:07:46.920> for<20:07:47.160> it<20:07:47.336> if 20:07:47.566 --> 20:07:47.576 align:start position:0% networks they've got an RFC for it if 20:07:47.576 --> 20:07:49.734 align:start position:0% networks they've got an RFC for it if you<20:07:47.824> have<20:07:48.296> the<20:07:48.480> time<20:07:48.656> to<20:07:48.896> look 20:07:49.734 --> 20:07:49.744 align:start position:0% you have the time to look 20:07:49.744 --> 20:07:52.910 align:start position:0% you have the time to look 100<20:07:50.336> plus<20:07:50.696> types<20:07:51.176> available<20:07:51.360> so<20:07:52.016> I<20:07:52.800> think 20:07:52.910 --> 20:07:52.920 align:start position:0% 100 plus types available so I think 20:07:52.920 --> 20:07:54.230 align:start position:0% 100 plus types available so I think they're<20:07:53.104> only<20:07:53.280> list<20:07:53.464> three<20:07:53.640> or<20:07:53.824> four<20:07:53.936> in<20:07:54.120> the 20:07:54.230 --> 20:07:54.240 align:start position:0% they're only list three or four in the 20:07:54.240 --> 20:07:55.494 align:start position:0% they're only list three or four in the syllabus 20:07:55.494 --> 20:07:55.504 align:start position:0% syllabus 20:07:55.504 --> 20:07:58.910 align:start position:0% syllabus EAP<20:07:56.160> md5<20:07:56.872> uses<20:07:57.480> a<20:07:57.656> series<20:07:57.896> of<20:07:58.144> challenges<20:07:58.680> and 20:07:58.910 --> 20:07:58.920 align:start position:0% EAP md5 uses a series of challenges and 20:07:58.920 --> 20:08:00.350 align:start position:0% EAP md5 uses a series of challenges and responses 20:08:00.350 --> 20:08:00.360 align:start position:0% responses 20:08:00.360 --> 20:08:02.814 align:start position:0% responses TLS<20:08:01.080> this<20:08:01.440> was<20:08:01.552> designed<20:08:01.920> by<20:08:02.160> Microsoft<20:08:02.576> and 20:08:02.814 --> 20:08:02.824 align:start position:0% TLS this was designed by Microsoft and 20:08:02.824 --> 20:08:05.454 align:start position:0% TLS this was designed by Microsoft and uses<20:08:03.240> a<20:08:03.480> certificate<20:08:04.080> system 20:08:05.454 --> 20:08:05.464 align:start position:0% uses a certificate system 20:08:05.464 --> 20:08:08.326 align:start position:0% uses a certificate system fast<20:08:05.872> is<20:08:06.240> a<20:08:06.536> designed<20:08:06.896> by<20:08:07.016> Cisco<20:08:07.552> and<20:08:07.856> it<20:08:07.976> uses 20:08:08.326 --> 20:08:08.336 align:start position:0% fast is a designed by Cisco and it uses 20:08:08.336 --> 20:08:12.046 align:start position:0% fast is a designed by Cisco and it uses a<20:08:08.760> TLS<20:08:09.240> tunnel<20:08:09.656> with<20:08:09.832> a<20:08:10.144> secure<20:08:10.376> socket<20:08:10.856> layers 20:08:12.046 --> 20:08:12.056 align:start position:0% a TLS tunnel with a secure socket layers 20:08:12.056 --> 20:08:14.686 align:start position:0% a TLS tunnel with a secure socket layers and<20:08:12.424> on<20:08:12.536> that<20:08:12.720> node<20:08:13.016> it<20:08:13.504> also<20:08:13.744> uses<20:08:14.104> shared 20:08:14.686 --> 20:08:14.696 align:start position:0% and on that node it also uses shared 20:08:14.696 --> 20:08:16.790 align:start position:0% and on that node it also uses shared secret<20:08:14.872> Keys<20:08:15.424> these<20:08:16.144> are<20:08:16.192> unique<20:08:16.496> to<20:08:16.616> each 20:08:16.790 --> 20:08:16.800 align:start position:0% secret Keys these are unique to each 20:08:16.800 --> 20:08:18.886 align:start position:0% secret Keys these are unique to each user<20:08:17.336> and<20:08:17.872> they<20:08:18.056> have<20:08:18.176> protected<20:08:18.720> access 20:08:18.886 --> 20:08:18.896 align:start position:0% user and they have protected access 20:08:18.896 --> 20:08:21.734 align:start position:0% user and they have protected access credentials 20:08:21.734 --> 20:08:21.744 align:start position:0% credentials 20:08:21.744 --> 20:08:25.790 align:start position:0% credentials ttls<20:08:22.744> uses<20:08:23.160> the<20:08:23.336> secure<20:08:23.760> TLS<20:08:24.480> tunnel 20:08:25.790 --> 20:08:25.800 align:start position:0% ttls uses the secure TLS tunnel 20:08:25.800 --> 20:08:28.310 align:start position:0% ttls uses the secure TLS tunnel and<20:08:26.336> then<20:08:26.464> finally<20:08:26.760> this<20:08:27.600> is<20:08:27.656> also<20:08:27.896> in<20:08:27.960> a<20:08:28.192> new 20:08:28.310 --> 20:08:28.320 align:start position:0% and then finally this is also in a new 20:08:28.320 --> 20:08:31.542 align:start position:0% and then finally this is also in a new one<20:08:28.440> in<20:08:28.552> the<20:08:28.680> syllabus<20:08:29.104> uh<20:08:30.000> PE<20:08:30.296> AP<20:08:30.656> increases 20:08:31.542 --> 20:08:31.552 align:start position:0% one in the syllabus uh PE AP increases 20:08:31.552 --> 20:08:34.134 align:start position:0% one in the syllabus uh PE AP increases the<20:08:31.744> protection<20:08:32.040> of<20:08:32.216> authentications<20:08:33.144> by 20:08:34.134 --> 20:08:34.144 align:start position:0% the protection of authentications by 20:08:34.144 --> 20:08:38.094 align:start position:0% the protection of authentications by creating<20:08:34.800> a<20:08:34.976> protected<20:08:35.464> TLS<20:08:36.360> tunnel 20:08:38.094 --> 20:08:38.104 align:start position:0% creating a protected TLS tunnel 20:08:38.104 --> 20:08:39.950 align:start position:0% creating a protected TLS tunnel and<20:08:38.464> within<20:08:38.760> the<20:08:38.872> tunnel<20:08:39.240> on<20:08:39.424> Authentication 20:08:39.950 --> 20:08:39.960 align:start position:0% and within the tunnel on Authentication 20:08:39.960 --> 20:08:43.494 align:start position:0% and within the tunnel on Authentication Protocol<20:08:40.616> such<20:08:41.336> as<20:08:41.512> Ms<20:08:42.120> chat<20:08:42.480> version<20:08:42.720> 2<20:08:43.080> can 20:08:43.494 --> 20:08:43.504 align:start position:0% Protocol such as Ms chat version 2 can 20:08:43.504 --> 20:08:46.814 align:start position:0% Protocol such as Ms chat version 2 can then<20:08:43.680> be<20:08:43.856> used 20:08:46.814 --> 20:08:46.824 align:start position:0% 20:08:46.824 --> 20:08:49.494 align:start position:0% geofencing<20:08:47.824> is<20:08:48.296> a<20:08:48.480> feature<20:08:48.832> that<20:08:49.192> is<20:08:49.320> actually 20:08:49.494 --> 20:08:49.504 align:start position:0% geofencing is a feature that is actually 20:08:49.504 --> 20:08:51.230 align:start position:0% geofencing is a feature that is actually built<20:08:49.976> inside<20:08:50.104> software<20:08:50.696> so<20:08:50.936> you<20:08:51.120> don't 20:08:51.230 --> 20:08:51.240 align:start position:0% built inside software so you don't 20:08:51.240 --> 20:08:54.286 align:start position:0% built inside software so you don't actually<20:08:51.424> have<20:08:51.784> it<20:08:52.016> running<20:08:52.680> on<20:08:53.040> its<20:08:53.280> own<20:08:53.336> it 20:08:54.286 --> 20:08:54.296 align:start position:0% actually have it running on its own it 20:08:54.296 --> 20:08:56.926 align:start position:0% actually have it running on its own it uses<20:08:54.600> GPS<20:08:54.896> or<20:08:55.376> radio<20:08:55.616> to<20:08:56.104> Define<20:08:56.216> geographical 20:08:56.926 --> 20:08:56.936 align:start position:0% uses GPS or radio to Define geographical 20:08:56.936 --> 20:08:59.990 align:start position:0% uses GPS or radio to Define geographical boundaries<20:08:57.536> I.E<20:08:58.440> who's<20:08:58.680> allowed<20:08:59.104> in<20:08:59.696> and<20:08:59.824> out 20:08:59.990 --> 20:09:00.000 align:start position:0% boundaries I.E who's allowed in and out 20:09:00.000 --> 20:09:02.750 align:start position:0% boundaries I.E who's allowed in and out of<20:09:00.176> your<20:09:00.480> network<20:09:01.320> or<20:09:01.680> device 20:09:02.750 --> 20:09:02.760 align:start position:0% of your network or device 20:09:02.760 --> 20:09:05.094 align:start position:0% of your network or device uh<20:09:03.360> triggers<20:09:03.896> this<20:09:04.376> default<20:09:04.680> the<20:09:04.856> triggers 20:09:05.094 --> 20:09:05.104 align:start position:0% uh triggers this default the triggers 20:09:05.104 --> 20:09:07.910 align:start position:0% uh triggers this default the triggers defined<20:09:05.576> for<20:09:05.760> devices<20:09:06.320> entering<20:09:07.320> or<20:09:07.504> exiting 20:09:07.910 --> 20:09:07.920 align:start position:0% defined for devices entering or exiting 20:09:07.920 --> 20:09:10.486 align:start position:0% defined for devices entering or exiting the<20:09:08.104> network<20:09:08.216> boundaries 20:09:10.486 --> 20:09:10.496 align:start position:0% the network boundaries 20:09:10.496 --> 20:09:12.110 align:start position:0% the network boundaries all<20:09:10.856> right<20:09:10.920> so<20:09:11.104> just<20:09:11.400> some<20:09:11.640> of<20:09:11.760> the<20:09:11.824> we're 20:09:12.110 --> 20:09:12.120 align:start position:0% all right so just some of the we're 20:09:12.120 --> 20:09:13.366 align:start position:0% all right so just some of the we're basically<20:09:12.360> hitting<20:09:12.656> some<20:09:12.784> of<20:09:12.896> the<20:09:13.016> syllabus 20:09:13.366 --> 20:09:13.376 align:start position:0% basically hitting some of the syllabus 20:09:13.376 --> 20:09:14.990 align:start position:0% basically hitting some of the syllabus items<20:09:13.856> so<20:09:14.040> this<20:09:14.280> is<20:09:14.400> why<20:09:14.512> we<20:09:14.696> went<20:09:14.824> through 20:09:14.990 --> 20:09:15.000 align:start position:0% items so this is why we went through 20:09:15.000 --> 20:09:19.566 align:start position:0% items so this is why we went through pretty<20:09:15.296> quick<20:09:15.744> uh<20:09:16.744> WPA<20:09:17.832> tkip 20:09:19.566 --> 20:09:19.576 align:start position:0% pretty quick uh WPA tkip 20:09:19.576 --> 20:09:24.886 align:start position:0% pretty quick uh WPA tkip ccmp<20:09:20.720> EAP<20:09:21.720> and<20:09:22.680> GF<20:09:23.160> and<20:09:23.336> Tim 20:09:24.886 --> 20:09:24.896 align:start position:0% ccmp EAP and GF and Tim 20:09:24.896 --> 20:09:26.454 align:start position:0% ccmp EAP and GF and Tim okay<20:09:25.144> that's<20:09:25.440> all<20:09:25.616> for<20:09:25.744> now<20:09:25.920> thanks<20:09:26.336> for 20:09:26.454 --> 20:09:26.464 align:start position:0% okay that's all for now thanks for 20:09:26.464 --> 20:09:30.190 align:start position:0% okay that's all for now thanks for watching 20:09:30.190 --> 20:09:30.200 align:start position:0% 20:09:30.200 --> 20:09:49.990 align:start position:0% [Music] 20:09:49.990 --> 20:09:50.000 align:start position:0% 20:09:50.000 --> 20:09:53.630 align:start position:0% Network<20:09:51.000> Tools<20:09:51.720> hardware<20:09:52.640> troubleshooting 20:09:53.630 --> 20:09:53.640 align:start position:0% Network Tools hardware troubleshooting 20:09:53.640 --> 20:09:55.246 align:start position:0% Network Tools hardware troubleshooting tools 20:09:55.246 --> 20:09:55.256 align:start position:0% tools 20:09:55.256 --> 20:09:57.710 align:start position:0% tools in<20:09:55.800> all<20:09:55.976> the<20:09:56.160> previous<20:09:56.336> lessons<20:09:57.000> we've<20:09:57.424> talked 20:09:57.710 --> 20:09:57.720 align:start position:0% in all the previous lessons we've talked 20:09:57.720 --> 20:09:59.566 align:start position:0% in all the previous lessons we've talked about<20:09:57.784> a<20:09:58.144> lot<20:09:58.256> of<20:09:58.376> different<20:09:58.552> things<20:09:58.856> and<20:09:59.464> in 20:09:59.566 --> 20:09:59.576 align:start position:0% about a lot of different things and in 20:09:59.576 --> 20:10:00.886 align:start position:0% about a lot of different things and in the<20:09:59.760> very<20:09:59.872> previous<20:10:00.056> lesson<20:10:00.480> we<20:10:00.600> talked<20:10:00.832> about 20:10:00.886 --> 20:10:00.896 align:start position:0% the very previous lesson we talked about 20:10:00.896 --> 20:10:02.926 align:start position:0% the very previous lesson we talked about network<20:10:01.192> security<20:10:01.616> and<20:10:02.104> how<20:10:02.280> important<20:10:02.576> it<20:10:02.824> is 20:10:02.926 --> 20:10:02.936 align:start position:0% network security and how important it is 20:10:02.936 --> 20:10:05.566 align:start position:0% network security and how important it is so<20:10:03.720> in<20:10:03.960> this<20:10:04.192> final<20:10:04.440> lesson<20:10:04.920> I<20:10:05.104> want<20:10:05.216> to<20:10:05.400> talk 20:10:05.566 --> 20:10:05.576 align:start position:0% so in this final lesson I want to talk 20:10:05.576 --> 20:10:08.206 align:start position:0% so in this final lesson I want to talk briefly<20:10:06.176> about<20:10:06.720> some<20:10:07.080> of<20:10:07.192> the<20:10:07.440> network<20:10:07.616> tools 20:10:08.206 --> 20:10:08.216 align:start position:0% briefly about some of the network tools 20:10:08.216 --> 20:10:09.590 align:start position:0% briefly about some of the network tools that<20:10:08.512> were<20:10:08.640> going<20:10:08.760> to<20:10:08.872> be<20:10:08.936> useful<20:10:09.240> when<20:10:09.480> we're 20:10:09.590 --> 20:10:09.600 align:start position:0% that were going to be useful when we're 20:10:09.600 --> 20:10:12.166 align:start position:0% that were going to be useful when we're running<20:10:09.784> a<20:10:10.016> network<20:10:10.400> specifically<20:10:11.400> in<20:10:12.000> this 20:10:12.166 --> 20:10:12.176 align:start position:0% running a network specifically in this 20:10:12.176 --> 20:10:14.030 align:start position:0% running a network specifically in this module<20:10:12.536> about<20:10:12.832> some<20:10:13.144> of<20:10:13.192> the<20:10:13.320> troubleshooting 20:10:14.030 --> 20:10:14.040 align:start position:0% module about some of the troubleshooting 20:10:14.040 --> 20:10:16.310 align:start position:0% module about some of the troubleshooting tools<20:10:14.400> we're<20:10:15.120> going<20:10:15.296> to<20:10:15.360> start<20:10:15.536> off<20:10:15.784> by 20:10:16.310 --> 20:10:16.320 align:start position:0% tools we're going to start off by 20:10:16.320 --> 20:10:19.494 align:start position:0% tools we're going to start off by discussing<20:10:17.104> the<20:10:17.760> general<20:10:17.936> top<20:10:18.480> topic<20:10:19.192> of 20:10:19.494 --> 20:10:19.504 align:start position:0% discussing the general top topic of 20:10:19.504 --> 20:10:22.134 align:start position:0% discussing the general top topic of Hardware<20:10:20.120> diagnosis<20:10:21.120> and<20:10:21.424> troubleshooting 20:10:22.134 --> 20:10:22.144 align:start position:0% Hardware diagnosis and troubleshooting 20:10:22.144 --> 20:10:23.750 align:start position:0% Hardware diagnosis and troubleshooting and<20:10:22.616> then<20:10:22.744> we're<20:10:22.856> going<20:10:22.976> to<20:10:23.040> move<20:10:23.160> on<20:10:23.336> to<20:10:23.512> talk 20:10:23.750 --> 20:10:23.760 align:start position:0% and then we're going to move on to talk 20:10:23.760 --> 20:10:26.814 align:start position:0% and then we're going to move on to talk about<20:10:23.936> four<20:10:24.896> common<20:10:25.376> tools<20:10:25.856> that<20:10:26.104> are<20:10:26.280> used<20:10:26.464> in 20:10:26.814 --> 20:10:26.824 align:start position:0% about four common tools that are used in 20:10:26.824 --> 20:10:29.926 align:start position:0% about four common tools that are used in troubleshooting<20:10:27.480> software<20:10:28.280> these<20:10:29.280> are<20:10:29.696> the 20:10:29.926 --> 20:10:29.936 align:start position:0% troubleshooting software these are the 20:10:29.936 --> 20:10:33.590 align:start position:0% troubleshooting software these are the diagnostic<20:10:30.600> disk<20:10:31.280> multimeter<20:10:32.280> cable<20:10:33.056> testers 20:10:33.590 --> 20:10:33.600 align:start position:0% diagnostic disk multimeter cable testers 20:10:33.600 --> 20:10:36.590 align:start position:0% diagnostic disk multimeter cable testers and<20:10:34.376> a<20:10:34.552> postcard<20:10:34.920> there<20:10:35.760> are<20:10:35.872> of<20:10:36.000> course<20:10:36.120> other 20:10:36.590 --> 20:10:36.600 align:start position:0% and a postcard there are of course other 20:10:36.600 --> 20:10:38.862 align:start position:0% and a postcard there are of course other tools<20:10:37.144> however<20:10:38.040> these<20:10:38.400> are<20:10:38.464> some<20:10:38.696> of<20:10:38.824> the 20:10:38.862 --> 20:10:38.872 align:start position:0% tools however these are some of the 20:10:38.872 --> 20:10:40.814 align:start position:0% tools however these are some of the major<20:10:39.120> ones<20:10:39.536> that<20:10:39.896> we<20:10:40.144> want<20:10:40.256> to<20:10:40.440> know 20:10:40.814 --> 20:10:40.824 align:start position:0% major ones that we want to know 20:10:40.824 --> 20:10:45.230 align:start position:0% major ones that we want to know specifically<20:10:42.016> for<20:10:43.104> this<20:10:44.104> network<20:10:44.464> plus<20:10:44.760> exam 20:10:45.230 --> 20:10:45.240 align:start position:0% specifically for this network plus exam 20:10:45.240 --> 20:10:47.566 align:start position:0% specifically for this network plus exam if<20:10:45.960> you<20:10:46.144> recall<20:10:46.440> very<20:10:46.680> early<20:10:46.856> we<20:10:47.216> talked<20:10:47.512> about 20:10:47.566 --> 20:10:47.576 align:start position:0% if you recall very early we talked about 20:10:47.576 --> 20:10:49.494 align:start position:0% if you recall very early we talked about some<20:10:47.872> of<20:10:48.000> the<20:10:48.120> cable<20:10:48.360> tools<20:10:48.784> as<20:10:48.896> well<20:10:49.080> such<20:10:49.376> as 20:10:49.494 --> 20:10:49.504 align:start position:0% some of the cable tools as well such as 20:10:49.504 --> 20:10:53.326 align:start position:0% some of the cable tools as well such as toner<20:10:49.976> probes<20:10:50.424> and<20:10:51.424> punch<20:10:51.784> down<20:10:52.080> tools<20:10:52.552> and 20:10:53.326 --> 20:10:53.336 align:start position:0% toner probes and punch down tools and 20:10:53.336 --> 20:10:55.734 align:start position:0% toner probes and punch down tools and those<20:10:53.760> sort<20:10:54.296> of<20:10:54.424> fall<20:10:54.600> into<20:10:54.784> here<20:10:55.016> but<20:10:55.192> those 20:10:55.734 --> 20:10:55.744 align:start position:0% those sort of fall into here but those 20:10:55.744 --> 20:10:57.414 align:start position:0% those sort of fall into here but those are<20:10:55.920> more<20:10:56.104> tools<20:10:56.464> that<20:10:56.576> we<20:10:56.696> use<20:10:56.872> to<20:10:57.240> create 20:10:57.414 --> 20:10:57.424 align:start position:0% are more tools that we use to create 20:10:57.424 --> 20:10:59.390 align:start position:0% are more tools that we use to create cables<20:10:58.016> rather<20:10:58.496> than<20:10:58.680> ones<20:10:59.040> that<20:10:59.216> we're<20:10:59.280> going 20:10:59.390 --> 20:10:59.400 align:start position:0% cables rather than ones that we're going 20:10:59.400 --> 20:11:01.182 align:start position:0% cables rather than ones that we're going to<20:10:59.512> do<20:10:59.640> troubleshooting<20:11:00.240> with 20:11:01.182 --> 20:11:01.192 align:start position:0% to do troubleshooting with 20:11:01.192 --> 20:11:03.590 align:start position:0% to do troubleshooting with so<20:11:01.552> we've<20:11:01.856> briefly<20:11:02.104> discussed<20:11:02.640> Hardware<20:11:03.056> in 20:11:03.590 --> 20:11:03.600 align:start position:0% so we've briefly discussed Hardware in 20:11:03.600 --> 20:11:05.094 align:start position:0% so we've briefly discussed Hardware in the<20:11:03.720> past<20:11:03.896> but<20:11:04.256> we<20:11:04.376> need<20:11:04.440> to<20:11:04.552> take<20:11:04.616> a<20:11:04.800> closer 20:11:05.094 --> 20:11:05.104 align:start position:0% the past but we need to take a closer 20:11:05.104 --> 20:11:07.430 align:start position:0% the past but we need to take a closer look<20:11:05.216> at<20:11:05.400> it<20:11:05.512> for<20:11:05.824> the<20:11:05.936> sake<20:11:06.120> of<20:11:06.296> this<20:11:06.536> module 20:11:07.430 --> 20:11:07.440 align:start position:0% look at it for the sake of this module 20:11:07.440 --> 20:11:10.182 align:start position:0% look at it for the sake of this module Hardware<20:11:07.976> is<20:11:08.336> a<20:11:08.512> term<20:11:08.696> that<20:11:09.480> refers<20:11:09.832> to<20:11:10.016> the 20:11:10.182 --> 20:11:10.192 align:start position:0% Hardware is a term that refers to the 20:11:10.192 --> 20:11:12.182 align:start position:0% Hardware is a term that refers to the physical<20:11:10.440> components<20:11:11.216> of<20:11:11.336> a<20:11:11.512> computer<20:11:11.696> system 20:11:12.182 --> 20:11:12.192 align:start position:0% physical components of a computer system 20:11:12.192 --> 20:11:14.862 align:start position:0% physical components of a computer system including<20:11:13.192> hard<20:11:13.440> drives<20:11:13.800> power<20:11:14.160> supplies<20:11:14.576> RAM 20:11:14.862 --> 20:11:14.872 align:start position:0% including hard drives power supplies RAM 20:11:14.872 --> 20:11:17.454 align:start position:0% including hard drives power supplies RAM and<20:11:15.120> other<20:11:15.360> stuff<20:11:16.080> Hardware<20:11:16.496> unlike<20:11:17.104> software 20:11:17.454 --> 20:11:17.464 align:start position:0% and other stuff Hardware unlike software 20:11:17.464 --> 20:11:19.734 align:start position:0% and other stuff Hardware unlike software it's<20:11:17.640> not<20:11:17.824> a<20:11:18.056> program<20:11:18.176> it<20:11:18.656> can't<20:11:18.960> be<20:11:19.144> installed 20:11:19.734 --> 20:11:19.744 align:start position:0% it's not a program it can't be installed 20:11:19.744 --> 20:11:22.310 align:start position:0% it's not a program it can't be installed it<20:11:20.336> can<20:11:20.464> however<20:11:20.760> be<20:11:21.000> physically<20:11:21.480> placed<20:11:22.192> or 20:11:22.310 --> 20:11:22.320 align:start position:0% it can however be physically placed or 20:11:22.320 --> 20:11:25.006 align:start position:0% it can however be physically placed or installed<20:11:22.920> or<20:11:23.216> changed<20:11:23.696> in<20:11:23.872> some<20:11:24.056> cases<20:11:24.424> but 20:11:25.006 --> 20:11:25.016 align:start position:0% installed or changed in some cases but 20:11:25.016 --> 20:11:26.686 align:start position:0% installed or changed in some cases but this<20:11:25.192> generally<20:11:25.440> requires<20:11:25.920> taking<20:11:26.160> apart<20:11:26.512> the 20:11:26.686 --> 20:11:26.696 align:start position:0% this generally requires taking apart the 20:11:26.696 --> 20:11:28.246 align:start position:0% this generally requires taking apart the unit<20:11:26.872> and<20:11:27.176> physically<20:11:27.536> installing<20:11:28.016> something 20:11:28.246 --> 20:11:28.256 align:start position:0% unit and physically installing something 20:11:28.256 --> 20:11:31.182 align:start position:0% unit and physically installing something new<20:11:28.552> on<20:11:28.800> it<20:11:28.976> and<20:11:29.576> when<20:11:29.760> we're<20:11:29.936> talking<20:11:30.176> about<20:11:30.960> a 20:11:31.182 --> 20:11:31.192 align:start position:0% new on it and when we're talking about a 20:11:31.192 --> 20:11:32.926 align:start position:0% new on it and when we're talking about a computer<20:11:31.320> I<20:11:31.744> just<20:11:31.856> want<20:11:32.040> to<20:11:32.104> point<20:11:32.216> out<20:11:32.400> that<20:11:32.696> a 20:11:32.926 --> 20:11:32.936 align:start position:0% computer I just want to point out that a 20:11:32.936 --> 20:11:35.206 align:start position:0% computer I just want to point out that a router<20:11:33.360> a<20:11:33.600> switch<20:11:33.784> these<20:11:34.376> are<20:11:34.496> types<20:11:35.104> of 20:11:35.206 --> 20:11:35.216 align:start position:0% router a switch these are types of 20:11:35.216 --> 20:11:37.310 align:start position:0% router a switch these are types of computers<20:11:35.640> a<20:11:35.936> printer<20:11:36.240> they<20:11:36.784> do<20:11:36.960> have 20:11:37.310 --> 20:11:37.320 align:start position:0% computers a printer they do have 20:11:37.320 --> 20:11:39.886 align:start position:0% computers a printer they do have Hardware<20:11:37.856> inside<20:11:38.400> of<20:11:38.760> them<20:11:38.872> so<20:11:39.296> important 20:11:39.886 --> 20:11:39.896 align:start position:0% Hardware inside of them so important 20:11:39.896 --> 20:11:41.454 align:start position:0% Hardware inside of them so important that<20:11:40.016> we<20:11:40.144> realize<20:11:40.440> this<20:11:40.800> term<20:11:40.920> is<20:11:41.216> really 20:11:41.454 --> 20:11:41.464 align:start position:0% that we realize this term is really 20:11:41.464 --> 20:11:44.630 align:start position:0% that we realize this term is really all-encompassing<20:11:42.720> and<20:11:43.320> because<20:11:43.616> Hardware<20:11:44.160> is 20:11:44.630 --> 20:11:44.640 align:start position:0% all-encompassing and because Hardware is 20:11:44.640 --> 20:11:47.206 align:start position:0% all-encompassing and because Hardware is made<20:11:44.872> up<20:11:45.000> of<20:11:45.360> physical<20:11:45.832> components<20:11:46.680> it 20:11:47.206 --> 20:11:47.216 align:start position:0% made up of physical components it 20:11:47.216 --> 20:11:48.950 align:start position:0% made up of physical components it generally<20:11:47.512> takes<20:11:47.824> physical<20:11:48.120> tools<20:11:48.720> to 20:11:48.950 --> 20:11:48.960 align:start position:0% generally takes physical tools to 20:11:48.960 --> 20:11:50.750 align:start position:0% generally takes physical tools to troubleshoot<20:11:49.440> them<20:11:49.616> by<20:11:50.280> saying<20:11:50.576> physical 20:11:50.750 --> 20:11:50.760 align:start position:0% troubleshoot them by saying physical 20:11:50.760 --> 20:11:52.790 align:start position:0% troubleshoot them by saying physical tools<20:11:51.240> this<20:11:51.424> means<20:11:51.656> tools<20:11:52.016> that<20:11:52.256> physically 20:11:52.790 --> 20:11:52.800 align:start position:0% tools this means tools that physically 20:11:52.800 --> 20:11:55.366 align:start position:0% tools this means tools that physically come<20:11:53.280> into<20:11:53.512> contact<20:11:53.872> with<20:11:54.424> the<20:11:54.656> hardware<20:11:54.832> in 20:11:55.366 --> 20:11:55.376 align:start position:0% come into contact with the hardware in 20:11:55.376 --> 20:11:57.710 align:start position:0% come into contact with the hardware in order<20:11:55.504> to<20:11:55.680> test<20:11:55.920> it<20:11:56.104> now<20:11:57.056> some<20:11:57.296> of<20:11:57.480> the 20:11:57.710 --> 20:11:57.720 align:start position:0% order to test it now some of the 20:11:57.720 --> 20:11:59.270 align:start position:0% order to test it now some of the hardware<20:11:57.896> troubleshooting<20:11:58.744> tools<20:11:59.040> can 20:11:59.270 --> 20:11:59.280 align:start position:0% hardware troubleshooting tools can 20:11:59.280 --> 20:12:00.886 align:start position:0% hardware troubleshooting tools can actually<20:11:59.464> be<20:11:59.696> programs<20:12:00.240> that<20:12:00.360> run<20:12:00.536> on<20:12:00.720> the 20:12:00.886 --> 20:12:00.896 align:start position:0% actually be programs that run on the 20:12:00.896 --> 20:12:02.926 align:start position:0% actually be programs that run on the computer<20:12:01.016> and<20:12:01.976> one<20:12:02.280> of<20:12:02.400> those<20:12:02.464> I'm<20:12:02.696> going<20:12:02.872> to 20:12:02.926 --> 20:12:02.936 align:start position:0% computer and one of those I'm going to 20:12:02.936 --> 20:12:05.094 align:start position:0% computer and one of those I'm going to talk<20:12:03.120> about<20:12:03.296> in<20:12:03.656> this<20:12:03.832> module 20:12:05.094 --> 20:12:05.104 align:start position:0% talk about in this module 20:12:05.104 --> 20:12:08.270 align:start position:0% talk about in this module so<20:12:05.760> this<20:12:06.536> non-physical<20:12:07.440> troubleshooting 20:12:08.270 --> 20:12:08.280 align:start position:0% so this non-physical troubleshooting 20:12:08.280 --> 20:12:11.454 align:start position:0% so this non-physical troubleshooting tool<20:12:08.640> is<20:12:09.176> commonly<20:12:09.536> called<20:12:09.832> a<20:12:10.144> diagnostic<20:12:10.976> or 20:12:11.454 --> 20:12:11.464 align:start position:0% tool is commonly called a diagnostic or 20:12:11.464 --> 20:12:14.750 align:start position:0% tool is commonly called a diagnostic or diagnosis<20:12:12.176> disk<20:12:12.656> this<20:12:13.504> is<20:12:13.680> common<20:12:14.104> software 20:12:14.750 --> 20:12:14.760 align:start position:0% diagnosis disk this is common software 20:12:14.760 --> 20:12:16.670 align:start position:0% diagnosis disk this is common software that's<20:12:15.056> used<20:12:15.360> to<20:12:15.600> test<20:12:15.960> the<20:12:16.192> system's 20:12:16.670 --> 20:12:16.680 align:start position:0% that's used to test the system's 20:12:16.680 --> 20:12:19.366 align:start position:0% that's used to test the system's Hardware<20:12:16.920> or<20:12:17.872> in<20:12:18.056> some<20:12:18.240> cases<20:12:18.600> the<20:12:18.960> router's 20:12:19.366 --> 20:12:19.376 align:start position:0% Hardware or in some cases the router's 20:12:19.376 --> 20:12:21.774 align:start position:0% Hardware or in some cases the router's hardware<20:12:19.504> and<20:12:19.856> so<20:12:20.040> on<20:12:20.216> it<20:12:21.000> runs<20:12:21.296> a<20:12:21.360> series<20:12:21.536> of 20:12:21.774 --> 20:12:21.784 align:start position:0% hardware and so on it runs a series of 20:12:21.784 --> 20:12:23.454 align:start position:0% hardware and so on it runs a series of tests<20:12:22.192> on<20:12:22.440> different<20:12:22.616> pieces<20:12:23.104> of<20:12:23.280> the 20:12:23.454 --> 20:12:23.464 align:start position:0% tests on different pieces of the 20:12:23.464 --> 20:12:25.494 align:start position:0% tests on different pieces of the hardware<20:12:23.640> in<20:12:24.000> the<20:12:24.176> system<20:12:24.360> and<20:12:25.080> if<20:12:25.256> there<20:12:25.376> are 20:12:25.494 --> 20:12:25.504 align:start position:0% hardware in the system and if there are 20:12:25.504 --> 20:12:26.990 align:start position:0% hardware in the system and if there are issues<20:12:25.800> that<20:12:25.920> need<20:12:26.104> to<20:12:26.160> be<20:12:26.280> fixed<20:12:26.640> it'll 20:12:26.990 --> 20:12:27.000 align:start position:0% issues that need to be fixed it'll 20:12:27.000 --> 20:12:29.206 align:start position:0% issues that need to be fixed it'll notify<20:12:27.424> you<20:12:27.600> you<20:12:28.256> might<20:12:28.440> be<20:12:28.616> thinking<20:12:28.856> if<20:12:29.040> the 20:12:29.206 --> 20:12:29.216 align:start position:0% notify you you might be thinking if the 20:12:29.216 --> 20:12:30.470 align:start position:0% notify you you might be thinking if the hardware<20:12:29.336> of<20:12:29.640> the<20:12:29.760> computer<20:12:29.872> is<20:12:30.120> meant 20:12:30.470 --> 20:12:30.480 align:start position:0% hardware of the computer is meant 20:12:30.480 --> 20:12:33.110 align:start position:0% hardware of the computer is meant malfunctioning<20:12:31.320> how<20:12:32.104> can<20:12:32.280> you<20:12:32.400> run<20:12:32.576> a<20:12:32.760> disk 20:12:33.110 --> 20:12:33.120 align:start position:0% malfunctioning how can you run a disk 20:12:33.120 --> 20:12:35.270 align:start position:0% malfunctioning how can you run a disk well<20:12:33.720> as<20:12:33.896> long<20:12:34.080> as<20:12:34.192> the<20:12:34.440> system's<20:12:34.920> clock 20:12:35.270 --> 20:12:35.280 align:start position:0% well as long as the system's clock 20:12:35.280 --> 20:12:38.326 align:start position:0% well as long as the system's clock circuits<20:12:36.056> disk<20:12:36.896> drive<20:12:37.016> and<20:12:37.616> CPU<20:12:38.160> are 20:12:38.326 --> 20:12:38.336 align:start position:0% circuits disk drive and CPU are 20:12:38.336 --> 20:12:41.030 align:start position:0% circuits disk drive and CPU are functioning<20:12:39.080> diagnostic<20:12:40.080> disk<20:12:40.440> can<20:12:40.616> be<20:12:40.800> used 20:12:41.030 --> 20:12:41.040 align:start position:0% functioning diagnostic disk can be used 20:12:41.040 --> 20:12:46.542 align:start position:0% functioning diagnostic disk can be used so<20:12:41.872> again<20:12:42.056> it<20:12:42.480> does<20:12:42.656> require<20:12:43.080> CPU 20:12:46.542 --> 20:12:46.552 align:start position:0% 20:12:46.552 --> 20:12:48.710 align:start position:0% the<20:12:47.336> disk<20:12:47.696> drive 20:12:48.710 --> 20:12:48.720 align:start position:0% the disk drive 20:12:48.720 --> 20:12:52.430 align:start position:0% the disk drive or<20:12:49.440> the<20:12:49.744> USB<20:12:50.216> contact<20:12:50.576> whatever<20:12:51.176> it<20:12:51.536> is<20:12:51.720> that 20:12:52.430 --> 20:12:52.440 align:start position:0% or the USB contact whatever it is that 20:12:52.440 --> 20:12:54.590 align:start position:0% or the USB contact whatever it is that is<20:12:52.616> going<20:12:52.856> to 20:12:54.590 --> 20:12:54.600 align:start position:0% is going to 20:12:54.600 --> 20:12:57.166 align:start position:0% is going to contain<20:12:55.256> the<20:12:55.440> disk<20:12:55.856> or<20:12:56.696> we<20:12:56.824> should<20:12:57.000> say 20:12:57.166 --> 20:12:57.176 align:start position:0% contain the disk or we should say 20:12:57.176 --> 20:12:59.990 align:start position:0% contain the disk or we should say perhaps<20:12:57.720> disk<20:12:58.256> in<20:12:58.496> some<20:12:58.616> cases 20:12:59.990 --> 20:13:00.000 align:start position:0% perhaps disk in some cases 20:13:00.000 --> 20:13:02.630 align:start position:0% perhaps disk in some cases and 20:13:02.630 --> 20:13:02.640 align:start position:0% and 20:13:02.640 --> 20:13:05.566 align:start position:0% and clock<20:13:03.120> circuits 20:13:05.566 --> 20:13:05.576 align:start position:0% clock circuits 20:13:05.576 --> 20:13:07.494 align:start position:0% clock circuits which<20:13:06.056> are<20:13:06.296> the<20:13:06.536> circuits<20:13:06.960> that<20:13:07.080> allow<20:13:07.376> the 20:13:07.494 --> 20:13:07.504 align:start position:0% which are the circuits that allow the 20:13:07.504 --> 20:13:09.230 align:start position:0% which are the circuits that allow the CPU<20:13:08.040> to<20:13:08.400> run 20:13:09.230 --> 20:13:09.240 align:start position:0% CPU to run 20:13:09.240 --> 20:13:11.150 align:start position:0% CPU to run now<20:13:09.600> I<20:13:09.720> just<20:13:09.832> made<20:13:10.016> the<20:13:10.144> C<20:13:10.320> right<20:13:10.552> here<20:13:10.800> because 20:13:11.150 --> 20:13:11.160 align:start position:0% now I just made the C right here because 20:13:11.160 --> 20:13:14.454 align:start position:0% now I just made the C right here because a<20:13:11.512> disk<20:13:11.872> with<20:13:12.600> a<20:13:12.832> K<20:13:13.016> it's<20:13:13.504> like<20:13:13.680> a<20:13:13.856> hard<20:13:13.976> disk 20:13:14.454 --> 20:13:14.464 align:start position:0% a disk with a K it's like a hard disk 20:13:14.464 --> 20:13:17.630 align:start position:0% a disk with a K it's like a hard disk like<20:13:15.120> USB<20:13:15.600> drives<20:13:15.960> flash<20:13:16.192> drives<20:13:16.616> a<20:13:17.216> disk<20:13:17.464> with 20:13:17.630 --> 20:13:17.640 align:start position:0% like USB drives flash drives a disk with 20:13:17.640 --> 20:13:19.134 align:start position:0% like USB drives flash drives a disk with a<20:13:17.824> C 20:13:19.134 --> 20:13:19.144 align:start position:0% a C 20:13:19.144 --> 20:13:23.502 align:start position:0% a C is<20:13:19.616> Optical 20:13:23.502 --> 20:13:23.512 align:start position:0% 20:13:23.512 --> 20:13:26.454 align:start position:0% now<20:13:24.176> in<20:13:24.656> general<20:13:24.784> these<20:13:25.744> disks<20:13:26.040> aren't<20:13:26.336> going 20:13:26.454 --> 20:13:26.464 align:start position:0% now in general these disks aren't going 20:13:26.464 --> 20:13:29.030 align:start position:0% now in general these disks aren't going to<20:13:26.640> State<20:13:26.824> what<20:13:27.240> the<20:13:27.480> problem<20:13:27.720> is<20:13:28.256> they're 20:13:29.030 --> 20:13:29.040 align:start position:0% to State what the problem is they're 20:13:29.040 --> 20:13:30.230 align:start position:0% to State what the problem is they're just<20:13:29.216> going<20:13:29.336> to<20:13:29.464> say<20:13:29.576> that<20:13:29.824> there<20:13:30.056> is 20:13:30.230 --> 20:13:30.240 align:start position:0% just going to say that there is 20:13:30.240 --> 20:13:31.910 align:start position:0% just going to say that there is something<20:13:30.536> malfunctioning<20:13:31.376> and<20:13:31.616> then<20:13:31.800> it's 20:13:31.910 --> 20:13:31.920 align:start position:0% something malfunctioning and then it's 20:13:31.920 --> 20:13:33.526 align:start position:0% something malfunctioning and then it's your<20:13:32.216> job<20:13:32.400> to<20:13:32.696> actually<20:13:32.872> take<20:13:33.240> that 20:13:33.526 --> 20:13:33.536 align:start position:0% your job to actually take that 20:13:33.536 --> 20:13:35.630 align:start position:0% your job to actually take that information<20:13:33.744> and<20:13:34.744> relate<20:13:35.104> it<20:13:35.216> into<20:13:35.336> something 20:13:35.630 --> 20:13:35.640 align:start position:0% information and relate it into something 20:13:35.640 --> 20:13:37.246 align:start position:0% information and relate it into something useful 20:13:37.246 --> 20:13:37.256 align:start position:0% useful 20:13:37.256 --> 20:13:39.822 align:start position:0% useful they<20:13:37.680> usually<20:13:37.976> do<20:13:38.280> this<20:13:38.464> by<20:13:38.824> producing<20:13:39.296> a<20:13:39.600> list 20:13:39.822 --> 20:13:39.832 align:start position:0% they usually do this by producing a list 20:13:39.832 --> 20:13:42.110 align:start position:0% they usually do this by producing a list of<20:13:40.552> all<20:13:40.800> the<20:13:40.920> different<20:13:41.040> Hardware<20:13:41.336> components 20:13:42.110 --> 20:13:42.120 align:start position:0% of all the different Hardware components 20:13:42.120 --> 20:13:43.910 align:start position:0% of all the different Hardware components and<20:13:42.536> basically<20:13:42.896> saying<20:13:43.256> which<20:13:43.440> of<20:13:43.616> them<20:13:43.744> is 20:13:43.910 --> 20:13:43.920 align:start position:0% and basically saying which of them is 20:13:43.920 --> 20:13:46.134 align:start position:0% and basically saying which of them is malfunctioning<20:13:44.640> the<20:13:45.296> course<20:13:45.424> of<20:13:45.656> action<20:13:45.896> is 20:13:46.134 --> 20:13:46.144 align:start position:0% malfunctioning the course of action is 20:13:46.144 --> 20:13:47.686 align:start position:0% malfunctioning the course of action is then<20:13:46.320> up<20:13:46.496> to<20:13:46.616> whomever<20:13:47.040> is<20:13:47.336> going<20:13:47.512> to 20:13:47.686 --> 20:13:47.696 align:start position:0% then up to whomever is going to 20:13:47.696 --> 20:13:49.734 align:start position:0% then up to whomever is going to physically<20:13:48.056> make<20:13:48.240> repairs<20:13:48.784> or<20:13:48.960> test<20:13:49.192> for<20:13:49.552> more 20:13:49.734 --> 20:13:49.744 align:start position:0% physically make repairs or test for more 20:13:49.744 --> 20:13:52.134 align:start position:0% physically make repairs or test for more this<20:13:50.640> person<20:13:50.872> is<20:13:51.176> usually<20:13:51.424> the<20:13:51.600> administrator 20:13:52.134 --> 20:13:52.144 align:start position:0% this person is usually the administrator 20:13:52.144 --> 20:13:54.886 align:start position:0% this person is usually the administrator or<20:13:52.440> an<20:13:52.552> I.T<20:13:52.800> consultant<20:13:53.400> or<20:13:54.296> specifically 20:13:54.886 --> 20:13:54.896 align:start position:0% or an I.T consultant or specifically 20:13:54.896 --> 20:13:57.166 align:start position:0% or an I.T consultant or specifically someone<20:13:55.192> who's<20:13:55.552> been<20:13:55.800> sent<20:13:56.104> out<20:13:56.336> by<20:13:56.936> the 20:13:57.166 --> 20:13:57.176 align:start position:0% someone who's been sent out by the 20:13:57.176 --> 20:13:59.150 align:start position:0% someone who's been sent out by the manufacturer<20:13:57.896> there<20:13:58.440> are<20:13:58.552> a<20:13:58.616> number<20:13:58.744> of<20:13:58.800> tools 20:13:59.150 --> 20:13:59.160 align:start position:0% manufacturer there are a number of tools 20:13:59.160 --> 20:14:01.542 align:start position:0% manufacturer there are a number of tools that<20:13:59.280> they<20:13:59.400> can<20:13:59.512> use<20:13:59.696> to<20:13:59.936> diagnose<20:14:00.536> once<20:14:01.440> they 20:14:01.542 --> 20:14:01.552 align:start position:0% that they can use to diagnose once they 20:14:01.552 --> 20:14:04.430 align:start position:0% that they can use to diagnose once they know<20:14:01.680> what<20:14:02.040> part<20:14:02.336> is<20:14:02.824> malfunctioning<20:14:03.536> a 20:14:04.430 --> 20:14:04.440 align:start position:0% know what part is malfunctioning a 20:14:04.440 --> 20:14:06.230 align:start position:0% know what part is malfunctioning a multimeter<20:14:05.104> is<20:14:05.512> one<20:14:05.640> of<20:14:05.760> the<20:14:05.824> most<20:14:05.936> common 20:14:06.230 --> 20:14:06.240 align:start position:0% multimeter is one of the most common 20:14:06.240 --> 20:14:07.790 align:start position:0% multimeter is one of the most common tools<20:14:06.720> that<20:14:06.896> we<20:14:07.016> see<20:14:07.144> in<20:14:07.320> the<20:14:07.440> field<20:14:07.552> of 20:14:07.790 --> 20:14:07.800 align:start position:0% tools that we see in the field of 20:14:07.800 --> 20:14:09.350 align:start position:0% tools that we see in the field of electrical<20:14:08.336> work<20:14:08.576> and<20:14:09.000> hardware 20:14:09.350 --> 20:14:09.360 align:start position:0% electrical work and hardware 20:14:09.360 --> 20:14:11.326 align:start position:0% electrical work and hardware troubleshooting 20:14:11.326 --> 20:14:11.336 align:start position:0% troubleshooting 20:14:11.336 --> 20:14:14.390 align:start position:0% troubleshooting it's<20:14:11.936> used<20:14:12.176> to<20:14:12.424> test<20:14:12.600> circuits<20:14:13.320> outlets<20:14:13.976> and 20:14:14.390 --> 20:14:14.400 align:start position:0% it's used to test circuits outlets and 20:14:14.400 --> 20:14:16.134 align:start position:0% it's used to test circuits outlets and other<20:14:14.576> electrical<20:14:15.120> components<20:14:15.720> of<20:14:15.960> most 20:14:16.134 --> 20:14:16.144 align:start position:0% other electrical components of most 20:14:16.144 --> 20:14:18.110 align:start position:0% other electrical components of most devices<20:14:16.616> now<20:14:17.400> there<20:14:17.576> are<20:14:17.760> very<20:14:17.872> different 20:14:18.110 --> 20:14:18.120 align:start position:0% devices now there are very different 20:14:18.120 --> 20:14:20.630 align:start position:0% devices now there are very different types<20:14:18.656> of<20:14:18.784> multimeters<20:14:19.504> out<20:14:19.680> there<20:14:19.856> but<20:14:20.400> they 20:14:20.630 --> 20:14:20.640 align:start position:0% types of multimeters out there but they 20:14:20.640 --> 20:14:23.566 align:start position:0% types of multimeters out there but they all<20:14:20.824> generally<20:14:21.240> test<20:14:21.536> for<20:14:21.832> the<20:14:22.016> same<20:14:22.144> thing 20:14:23.566 --> 20:14:23.576 align:start position:0% all generally test for the same thing 20:14:23.576 --> 20:14:25.862 align:start position:0% all generally test for the same thing they<20:14:24.056> measure<20:14:24.360> electrical<20:14:25.080> current 20:14:25.862 --> 20:14:25.872 align:start position:0% they measure electrical current 20:14:25.872 --> 20:14:29.630 align:start position:0% they measure electrical current resistance<20:14:26.872> and<20:14:27.720> wattage<20:14:28.144> or<20:14:28.376> voltage<20:14:28.800> rather 20:14:29.630 --> 20:14:29.640 align:start position:0% resistance and wattage or voltage rather 20:14:29.640 --> 20:14:31.990 align:start position:0% resistance and wattage or voltage rather current<20:14:30.176> is<20:14:30.656> generally<20:14:31.016> going<20:14:31.376> to<20:14:31.680> be 20:14:31.990 --> 20:14:32.000 align:start position:0% current is generally going to be 20:14:32.000 --> 20:14:34.134 align:start position:0% current is generally going to be measured<20:14:33.000> in<20:14:33.120> watts 20:14:34.134 --> 20:14:34.144 align:start position:0% measured in watts 20:14:34.144 --> 20:14:36.526 align:start position:0% measured in watts resistance<20:14:35.040> in<20:14:35.512> ohms 20:14:36.526 --> 20:14:36.536 align:start position:0% resistance in ohms 20:14:36.536 --> 20:14:39.110 align:start position:0% resistance in ohms and<20:14:37.144> voltage 20:14:39.110 --> 20:14:39.120 align:start position:0% and voltage 20:14:39.120 --> 20:14:40.486 align:start position:0% and voltage in<20:14:39.600> volts 20:14:40.486 --> 20:14:40.496 align:start position:0% in volts 20:14:40.496 --> 20:14:41.750 align:start position:0% in volts in<20:14:41.040> the<20:14:41.104> case<20:14:41.216> of<20:14:41.400> a<20:14:41.576> hardware 20:14:41.750 --> 20:14:41.760 align:start position:0% in the case of a hardware 20:14:41.760 --> 20:14:43.846 align:start position:0% in the case of a hardware troubleshooting<20:14:42.600> the<20:14:43.080> voltage<20:14:43.440> and 20:14:43.846 --> 20:14:43.856 align:start position:0% troubleshooting the voltage and 20:14:43.856 --> 20:14:46.246 align:start position:0% troubleshooting the voltage and resistance<20:14:44.464> functions<20:14:45.056> are<20:14:45.832> actually<20:14:46.016> going 20:14:46.246 --> 20:14:46.256 align:start position:0% resistance functions are actually going 20:14:46.256 --> 20:14:48.166 align:start position:0% resistance functions are actually going to<20:14:46.376> matter<20:14:46.496> the<20:14:46.920> most 20:14:48.166 --> 20:14:48.176 align:start position:0% to matter the most 20:14:48.176 --> 20:14:50.990 align:start position:0% to matter the most may<20:14:48.832> tell<20:14:49.016> us<20:14:49.192> information<20:14:49.464> about<20:14:50.464> say<20:14:50.760> the 20:14:50.990 --> 20:14:51.000 align:start position:0% may tell us information about say the 20:14:51.000 --> 20:14:54.526 align:start position:0% may tell us information about say the power<20:14:51.176> supply<20:14:51.976> or<20:14:52.976> the<20:14:53.760> wall<20:14:53.936> socket<20:14:54.424> that's 20:14:54.526 --> 20:14:54.536 align:start position:0% power supply or the wall socket that's 20:14:54.536 --> 20:14:55.846 align:start position:0% power supply or the wall socket that's plugging<20:14:55.016> into 20:14:55.846 --> 20:14:55.856 align:start position:0% plugging into 20:14:55.856 --> 20:14:57.710 align:start position:0% plugging into now<20:14:56.336> the<20:14:56.640> only<20:14:56.760> times<20:14:57.000> that<20:14:57.360> you're<20:14:57.536> really 20:14:57.710 --> 20:14:57.720 align:start position:0% now the only times that you're really 20:14:57.720 --> 20:15:01.310 align:start position:0% now the only times that you're really going<20:14:57.960> to<20:14:58.144> see<20:14:58.320> or<20:14:58.680> use<20:14:59.040> a<20:14:59.872> Multimeter 20:15:01.310 --> 20:15:01.320 align:start position:0% going to see or use a Multimeter 20:15:01.320 --> 20:15:02.926 align:start position:0% going to see or use a Multimeter to<20:15:01.680> be<20:15:01.800> helpful<20:15:02.040> for<20:15:02.280> troubleshooting<20:15:02.824> is 20:15:02.926 --> 20:15:02.936 align:start position:0% to be helpful for troubleshooting is 20:15:02.936 --> 20:15:04.814 align:start position:0% to be helpful for troubleshooting is when<20:15:03.056> we're<20:15:03.176> talking<20:15:03.360> about<20:15:03.536> power<20:15:03.960> supplies 20:15:04.814 --> 20:15:04.824 align:start position:0% when we're talking about power supplies 20:15:04.824 --> 20:15:09.110 align:start position:0% when we're talking about power supplies and<20:15:05.824> fuses<20:15:06.480> which<20:15:07.080> are<20:15:07.256> also<20:15:07.552> related 20:15:09.110 --> 20:15:09.120 align:start position:0% and fuses which are also related 20:15:09.120 --> 20:15:10.910 align:start position:0% and fuses which are also related anything<20:15:09.600> that<20:15:09.832> has<20:15:09.960> to<20:15:10.144> do<20:15:10.256> directly<20:15:10.616> with 20:15:10.910 --> 20:15:10.920 align:start position:0% anything that has to do directly with 20:15:10.920 --> 20:15:13.182 align:start position:0% anything that has to do directly with the<20:15:11.216> electrical<20:15:11.696> on<20:15:12.176> the<20:15:12.296> OSI<20:15:12.656> model<20:15:12.896> what 20:15:13.182 --> 20:15:13.192 align:start position:0% the electrical on the OSI model what 20:15:13.192 --> 20:15:15.526 align:start position:0% the electrical on the OSI model what we're<20:15:13.320> looking<20:15:13.440> at<20:15:13.616> here<20:15:13.856> is<20:15:14.160> layer<20:15:14.872> one<20:15:15.000> the 20:15:15.526 --> 20:15:15.536 align:start position:0% we're looking at here is layer one the 20:15:15.536 --> 20:15:17.206 align:start position:0% we're looking at here is layer one the physical<20:15:15.720> layer 20:15:17.206 --> 20:15:17.216 align:start position:0% physical layer 20:15:17.216 --> 20:15:19.366 align:start position:0% physical layer voltage<20:15:18.000> tests<20:15:18.480> are<20:15:18.656> important<20:15:18.960> because<20:15:19.144> they 20:15:19.366 --> 20:15:19.376 align:start position:0% voltage tests are important because they 20:15:19.376 --> 20:15:21.646 align:start position:0% voltage tests are important because they can<20:15:19.504> see<20:15:19.744> if<20:15:20.464> the<20:15:20.696> power<20:15:20.824> supply<20:15:21.120> of<20:15:21.480> a 20:15:21.646 --> 20:15:21.656 align:start position:0% can see if the power supply of a 20:15:21.656 --> 20:15:23.630 align:start position:0% can see if the power supply of a computer<20:15:21.832> or<20:15:22.192> device<20:15:22.496> is<20:15:22.976> actually<20:15:23.160> receiving 20:15:23.630 --> 20:15:23.640 align:start position:0% computer or device is actually receiving 20:15:23.640 --> 20:15:25.846 align:start position:0% computer or device is actually receiving power<20:15:24.000> the<20:15:24.720> multimeter<20:15:25.320> shows<20:15:25.504> there's<20:15:25.680> no 20:15:25.846 --> 20:15:25.856 align:start position:0% power the multimeter shows there's no 20:15:25.856 --> 20:15:28.006 align:start position:0% power the multimeter shows there's no voltage<20:15:26.336> and<20:15:26.872> the<20:15:27.056> power<20:15:27.176> supply<20:15:27.480> is<20:15:27.784> probably 20:15:28.006 --> 20:15:28.016 align:start position:0% voltage and the power supply is probably 20:15:28.016 --> 20:15:30.414 align:start position:0% voltage and the power supply is probably malfunctioning<20:15:28.856> the<20:15:29.576> resistance<20:15:30.000> function 20:15:30.414 --> 20:15:30.424 align:start position:0% malfunctioning the resistance function 20:15:30.424 --> 20:15:33.166 align:start position:0% malfunctioning the resistance function is<20:15:30.656> used<20:15:30.832> to<20:15:31.080> test<20:15:31.256> fuses<20:15:31.976> if<20:15:32.640> the<20:15:32.760> fuse<20:15:33.000> is 20:15:33.166 --> 20:15:33.176 align:start position:0% is used to test fuses if the fuse is 20:15:33.176 --> 20:15:35.502 align:start position:0% is used to test fuses if the fuse is blown<20:15:33.536> or<20:15:33.720> faulty<20:15:34.080> needs<20:15:34.440> to<20:15:34.496> be<20:15:34.616> replaced<20:15:35.104> the 20:15:35.502 --> 20:15:35.512 align:start position:0% blown or faulty needs to be replaced the 20:15:35.512 --> 20:15:37.366 align:start position:0% blown or faulty needs to be replaced the multimeter<20:15:36.120> is<20:15:36.176> going<20:15:36.296> to<20:15:36.424> tell<20:15:36.536> us<20:15:36.720> this<20:15:37.080> by 20:15:37.366 --> 20:15:37.376 align:start position:0% multimeter is going to tell us this by 20:15:37.376 --> 20:15:39.110 align:start position:0% multimeter is going to tell us this by the<20:15:37.552> resistance 20:15:39.110 --> 20:15:39.120 align:start position:0% the resistance 20:15:39.120 --> 20:15:42.166 align:start position:0% the resistance so<20:15:39.720> this<20:15:40.080> is<20:15:40.256> sort<20:15:40.496> of<20:15:40.616> what<20:15:41.280> a<20:15:41.512> multimeter 20:15:42.166 --> 20:15:42.176 align:start position:0% so this is sort of what a multimeter 20:15:42.176 --> 20:15:44.454 align:start position:0% so this is sort of what a multimeter looks<20:15:42.536> like<20:15:42.720> this<20:15:43.552> one<20:15:43.680> would<20:15:43.856> be<20:15:44.040> considered 20:15:44.454 --> 20:15:44.464 align:start position:0% looks like this one would be considered 20:15:44.464 --> 20:15:47.454 align:start position:0% looks like this one would be considered analog<20:15:45.056> because<20:15:45.424> you<20:15:45.656> can<20:15:45.784> see<20:15:45.960> right<20:15:46.256> here<20:15:46.496> it 20:15:47.454 --> 20:15:47.464 align:start position:0% analog because you can see right here it 20:15:47.464 --> 20:15:49.566 align:start position:0% analog because you can see right here it has<20:15:47.896> a 20:15:49.566 --> 20:15:49.576 align:start position:0% has a 20:15:49.576 --> 20:15:52.150 align:start position:0% has a basically<20:15:50.576> a<20:15:50.760> doesn't<20:15:51.120> have<20:15:51.360> a<20:15:51.656> digital 20:15:52.150 --> 20:15:52.160 align:start position:0% basically a doesn't have a digital 20:15:52.160 --> 20:15:54.646 align:start position:0% basically a doesn't have a digital output<20:15:53.160> it's<20:15:53.576> going<20:15:53.824> to<20:15:53.936> measure<20:15:54.240> it<20:15:54.360> with 20:15:54.646 --> 20:15:54.656 align:start position:0% output it's going to measure it with 20:15:54.656 --> 20:15:55.846 align:start position:0% output it's going to measure it with this 20:15:55.846 --> 20:15:55.856 align:start position:0% this 20:15:55.856 --> 20:15:58.486 align:start position:0% this um arm<20:15:56.400> here<20:15:56.696> that<20:15:57.120> will<20:15:57.296> move<20:15:57.600> and<20:15:58.192> then<20:15:58.320> you 20:15:58.486 --> 20:15:58.496 align:start position:0% um arm here that will move and then you 20:15:58.496 --> 20:16:00.350 align:start position:0% um arm here that will move and then you can<20:15:58.552> read<20:15:58.800> it<20:15:58.976> based<20:15:59.336> on<20:15:59.400> the<20:15:59.576> numbers<20:15:59.824> that 20:16:00.350 --> 20:16:00.360 align:start position:0% can read it based on the numbers that 20:16:00.360 --> 20:16:03.070 align:start position:0% can read it based on the numbers that are<20:16:00.600> above<20:16:01.080> there<20:16:01.744> are<20:16:01.920> as<20:16:02.104> well<20:16:02.280> digital 20:16:03.070 --> 20:16:03.080 align:start position:0% are above there are as well digital 20:16:03.080 --> 20:16:06.414 align:start position:0% are above there are as well digital multimeters<20:16:04.080> but<20:16:04.856> either<20:16:05.400> way<20:16:05.640> they're<20:16:06.240> all 20:16:06.414 --> 20:16:06.424 align:start position:0% multimeters but either way they're all 20:16:06.424 --> 20:16:08.454 align:start position:0% multimeters but either way they're all going<20:16:06.600> to<20:16:06.784> have<20:16:07.016> two<20:16:07.440> probes<20:16:07.976> which<20:16:08.280> are 20:16:08.454 --> 20:16:08.464 align:start position:0% going to have two probes which are 20:16:08.464 --> 20:16:10.990 align:start position:0% going to have two probes which are generally<20:16:08.760> black<20:16:09.120> and<20:16:09.360> red<20:16:09.536> the<20:16:10.376> black<20:16:10.616> road 20:16:10.990 --> 20:16:11.000 align:start position:0% generally black and red the black road 20:16:11.000 --> 20:16:13.542 align:start position:0% generally black and red the black road probe<20:16:12.000> rather<20:16:12.296> is<20:16:12.536> usually<20:16:12.832> either<20:16:13.080> for<20:16:13.376> the 20:16:13.542 --> 20:16:13.552 align:start position:0% probe rather is usually either for the 20:16:13.552 --> 20:16:16.310 align:start position:0% probe rather is usually either for the ground<20:16:13.872> or<20:16:14.872> the<20:16:15.176> negative 20:16:16.310 --> 20:16:16.320 align:start position:0% ground or the negative 20:16:16.320 --> 20:16:18.822 align:start position:0% ground or the negative and<20:16:17.160> the<20:16:17.400> red<20:16:17.576> just<20:16:17.824> like<20:16:17.936> on<20:16:18.120> your<20:16:18.296> car<20:16:18.480> is 20:16:18.822 --> 20:16:18.832 align:start position:0% and the red just like on your car is 20:16:18.832 --> 20:16:20.630 align:start position:0% and the red just like on your car is going<20:16:19.144> to<20:16:19.320> be 20:16:20.630 --> 20:16:20.640 align:start position:0% going to be 20:16:20.640 --> 20:16:24.414 align:start position:0% going to be for<20:16:21.240> positive<20:16:21.832> the<20:16:22.744> dial<20:16:22.920> in<20:16:23.336> the<20:16:23.464> middle<20:16:23.640> is 20:16:24.414 --> 20:16:24.424 align:start position:0% for positive the dial in the middle is 20:16:24.424 --> 20:16:27.046 align:start position:0% for positive the dial in the middle is going<20:16:24.600> to<20:16:24.784> be<20:16:24.896> to<20:16:25.376> test<20:16:25.616> to<20:16:26.464> determine<20:16:26.824> what 20:16:27.046 --> 20:16:27.056 align:start position:0% going to be to test to determine what 20:16:27.056 --> 20:16:28.910 align:start position:0% going to be to test to determine what you're<20:16:27.120> going<20:16:27.296> to<20:16:27.360> test<20:16:27.600> for<20:16:27.896> are<20:16:28.744> you<20:16:28.856> going 20:16:28.910 --> 20:16:28.920 align:start position:0% you're going to test for are you going 20:16:28.920 --> 20:16:30.710 align:start position:0% you're going to test for are you going to<20:16:28.976> test<20:16:29.104> your<20:16:29.280> voltage<20:16:29.760> are<20:16:30.360> you<20:16:30.600> going<20:16:30.656> to 20:16:30.710 --> 20:16:30.720 align:start position:0% to test your voltage are you going to 20:16:30.720 --> 20:16:33.590 align:start position:0% to test your voltage are you going to test<20:16:30.832> for<20:16:31.080> ohms<20:16:31.744> are<20:16:32.640> you<20:16:32.760> going<20:16:32.824> to<20:16:32.936> test<20:16:33.120> for 20:16:33.590 --> 20:16:33.600 align:start position:0% test for ohms are you going to test for 20:16:33.600 --> 20:16:36.286 align:start position:0% test for ohms are you going to test for wattage<20:16:34.856> etc<20:16:35.400> etc 20:16:36.286 --> 20:16:36.296 align:start position:0% wattage etc etc 20:16:36.296 --> 20:16:38.094 align:start position:0% wattage etc etc by<20:16:36.656> the<20:16:36.832> way<20:16:36.896> the<20:16:37.256> reason<20:16:37.376> it's<20:16:37.552> called<20:16:37.800> a 20:16:38.094 --> 20:16:38.104 align:start position:0% by the way the reason it's called a 20:16:38.104 --> 20:16:41.094 align:start position:0% by the way the reason it's called a multimeter<20:16:38.872> is<20:16:39.296> because<20:16:39.480> it<20:16:39.832> has<20:16:40.080> a<20:16:40.680> volt 20:16:41.094 --> 20:16:41.104 align:start position:0% multimeter is because it has a volt 20:16:41.104 --> 20:16:42.950 align:start position:0% multimeter is because it has a volt meter<20:16:41.400> in<20:16:41.824> it 20:16:42.950 --> 20:16:42.960 align:start position:0% meter in it 20:16:42.960 --> 20:16:45.230 align:start position:0% meter in it it<20:16:43.616> has<20:16:43.920> a 20:16:45.230 --> 20:16:45.240 align:start position:0% it has a 20:16:45.240 --> 20:16:48.590 align:start position:0% it has a ohm<20:16:46.016> meter<20:16:46.192> in<20:16:46.440> it<20:16:46.920> Etc 20:16:48.590 --> 20:16:48.600 align:start position:0% ohm meter in it Etc 20:16:48.600 --> 20:16:51.046 align:start position:0% ohm meter in it Etc so<20:16:49.080> we<20:16:49.256> combine<20:16:49.616> all<20:16:49.920> of<20:16:50.040> these<20:16:50.336> into<20:16:50.760> one 20:16:51.046 --> 20:16:51.056 align:start position:0% so we combine all of these into one 20:16:51.056 --> 20:16:53.206 align:start position:0% so we combine all of these into one device<20:16:51.240> which<20:16:51.600> is<20:16:51.720> called<20:16:51.960> a<20:16:52.192> multimeter<20:16:52.856> this 20:16:53.206 --> 20:16:53.216 align:start position:0% device which is called a multimeter this 20:16:53.216 --> 20:16:55.670 align:start position:0% device which is called a multimeter this probably<20:16:53.400> looks<20:16:53.696> familiar<20:16:54.000> if<20:16:54.656> you<20:16:55.016> have 20:16:55.670 --> 20:16:55.680 align:start position:0% probably looks familiar if you have 20:16:55.680 --> 20:16:57.950 align:start position:0% probably looks familiar if you have already<20:16:55.800> taken<20:16:56.216> the<20:16:56.336> a<20:16:56.464> plus<20:16:56.696> exam 20:16:57.950 --> 20:16:57.960 align:start position:0% already taken the a plus exam 20:16:57.960 --> 20:16:59.862 align:start position:0% already taken the a plus exam now<20:16:58.376> out<20:16:58.616> of<20:16:58.744> all<20:16:58.920> the<20:16:59.040> hardware<20:16:59.216> failures 20:16:59.862 --> 20:16:59.872 align:start position:0% now out of all the hardware failures 20:16:59.872 --> 20:17:01.182 align:start position:0% now out of all the hardware failures that<20:17:00.056> can<20:17:00.176> happen<20:17:00.360> the<20:17:00.656> one<20:17:00.784> that's<20:17:00.960> most 20:17:01.182 --> 20:17:01.192 align:start position:0% that can happen the one that's most 20:17:01.192 --> 20:17:02.926 align:start position:0% that can happen the one that's most common<20:17:01.440> has<20:17:01.856> the<20:17:02.104> biggest<20:17:02.216> effect<20:17:02.512> on<20:17:02.760> the 20:17:02.926 --> 20:17:02.936 align:start position:0% common has the biggest effect on the 20:17:02.936 --> 20:17:05.390 align:start position:0% common has the biggest effect on the network<20:17:03.056> is<20:17:03.784> cable<20:17:04.144> failure<20:17:04.616> this<20:17:05.160> type<20:17:05.280> of 20:17:05.390 --> 20:17:05.400 align:start position:0% network is cable failure this type of 20:17:05.400 --> 20:17:06.774 align:start position:0% network is cable failure this type of thing<20:17:05.512> happens<20:17:05.696> all<20:17:06.000> the<20:17:06.120> time<20:17:06.240> and<20:17:06.480> there<20:17:06.656> are 20:17:06.774 --> 20:17:06.784 align:start position:0% thing happens all the time and there are 20:17:06.784 --> 20:17:08.502 align:start position:0% thing happens all the time and there are tools<20:17:07.144> that<20:17:07.320> are<20:17:07.440> created<20:17:07.744> to<20:17:07.976> help<20:17:08.104> with<20:17:08.336> this 20:17:08.502 --> 20:17:08.512 align:start position:0% tools that are created to help with this 20:17:08.512 --> 20:17:09.350 align:start position:0% tools that are created to help with this problem 20:17:09.350 --> 20:17:09.360 align:start position:0% problem 20:17:09.360 --> 20:17:12.470 align:start position:0% problem cable<20:17:09.896> testers<20:17:10.496> are<20:17:10.856> generally<20:17:11.216> hand<20:17:11.824> held 20:17:12.470 --> 20:17:12.480 align:start position:0% cable testers are generally hand held 20:17:12.480 --> 20:17:15.110 align:start position:0% cable testers are generally hand held devices<20:17:13.016> that<20:17:13.744> are<20:17:13.856> meant<20:17:14.160> to<20:17:14.400> test<20:17:14.640> cable 20:17:15.110 --> 20:17:15.120 align:start position:0% devices that are meant to test cable 20:17:15.120 --> 20:17:17.862 align:start position:0% devices that are meant to test cable connectivity<20:17:15.832> they<20:17:16.680> test<20:17:16.920> to<20:17:17.160> make<20:17:17.400> sure<20:17:17.640> that 20:17:17.862 --> 20:17:17.872 align:start position:0% connectivity they test to make sure that 20:17:17.872 --> 20:17:19.734 align:start position:0% connectivity they test to make sure that the<20:17:18.056> data<20:17:18.424> is<20:17:18.656> being<20:17:18.896> communicated<20:17:19.440> through 20:17:19.734 --> 20:17:19.744 align:start position:0% the data is being communicated through 20:17:19.744 --> 20:17:22.070 align:start position:0% the data is being communicated through these<20:17:19.920> cables<20:17:20.336> properly 20:17:22.070 --> 20:17:22.080 align:start position:0% these cables properly 20:17:22.080 --> 20:17:24.886 align:start position:0% these cables properly and<20:17:22.856> there<20:17:23.160> are<20:17:23.280> a<20:17:23.336> few<20:17:23.464> main<20:17:23.696> types<20:17:24.176> of<20:17:24.536> cable 20:17:24.886 --> 20:17:24.896 align:start position:0% and there are a few main types of cable 20:17:24.896 --> 20:17:26.110 align:start position:0% and there are a few main types of cable testers 20:17:26.110 --> 20:17:26.120 align:start position:0% testers 20:17:26.120 --> 20:17:28.790 align:start position:0% testers continuity<20:17:27.120> testers<20:17:27.656> are<20:17:28.376> the<20:17:28.616> least 20:17:28.790 --> 20:17:28.800 align:start position:0% continuity testers are the least 20:17:28.800 --> 20:17:31.542 align:start position:0% continuity testers are the least expensive<20:17:29.512> kind<20:17:29.936> and<20:17:30.480> all<20:17:30.720> they<20:17:30.896> do<20:17:31.080> is<20:17:31.320> test 20:17:31.542 --> 20:17:31.552 align:start position:0% expensive kind and all they do is test 20:17:31.552 --> 20:17:34.182 align:start position:0% expensive kind and all they do is test for<20:17:31.920> a<20:17:32.160> broken<20:17:32.280> cable<20:17:32.784> basically<20:17:33.784> they<20:17:34.016> tell 20:17:34.182 --> 20:17:34.192 align:start position:0% for a broken cable basically they tell 20:17:34.192 --> 20:17:37.494 align:start position:0% for a broken cable basically they tell you<20:17:34.376> if<20:17:35.104> there<20:17:35.280> is<20:17:35.400> continuity<20:17:36.056> in<20:17:36.424> the<20:17:36.600> line 20:17:37.494 --> 20:17:37.504 align:start position:0% you if there is continuity in the line 20:17:37.504 --> 20:17:40.366 align:start position:0% you if there is continuity in the line data<20:17:38.336> cabling<20:17:38.696> testers<20:17:39.240> are<20:17:39.784> a<20:17:40.016> bit<20:17:40.144> more 20:17:40.366 --> 20:17:40.376 align:start position:0% data cabling testers are a bit more 20:17:40.376 --> 20:17:42.710 align:start position:0% data cabling testers are a bit more expensive<20:17:40.920> they<20:17:41.576> can<20:17:41.760> actually<20:17:41.936> test<20:17:42.360> broken 20:17:42.710 --> 20:17:42.720 align:start position:0% expensive they can actually test broken 20:17:42.720 --> 20:17:45.110 align:start position:0% expensive they can actually test broken cables<20:17:43.320> and<20:17:43.680> properly<20:17:44.040> Twisted<20:17:44.576> cables 20:17:45.110 --> 20:17:45.120 align:start position:0% cables and properly Twisted cables 20:17:45.120 --> 20:17:47.686 align:start position:0% cables and properly Twisted cables shorted<20:17:46.016> connections<20:17:46.552> and<20:17:46.680> more<20:17:46.856> they'll 20:17:47.686 --> 20:17:47.696 align:start position:0% shorted connections and more they'll 20:17:47.696 --> 20:17:52.134 align:start position:0% shorted connections and more they'll tell<20:17:47.872> you<20:17:48.000> what<20:17:48.424> pins<20:17:48.832> within<20:17:49.744> the<20:17:49.920> cable 20:17:52.134 --> 20:17:52.144 align:start position:0% tell you what pins within the cable 20:17:52.144 --> 20:17:56.030 align:start position:0% tell you what pins within the cable are<20:17:52.680> faulty 20:17:56.030 --> 20:17:56.040 align:start position:0% 20:17:56.040 --> 20:17:58.006 align:start position:0% finally<20:17:56.760> there<20:17:57.000> are<20:17:57.120> things<20:17:57.296> called<20:17:57.536> time 20:17:58.006 --> 20:17:58.016 align:start position:0% finally there are things called time 20:17:58.016 --> 20:18:01.006 align:start position:0% finally there are things called time domain<20:17:58.496> reflectors<20:17:59.040> or<20:17:59.400> tdrs<20:18:00.120> they're<20:18:00.656> the 20:18:01.006 --> 20:18:01.016 align:start position:0% domain reflectors or tdrs they're the 20:18:01.016 --> 20:18:04.366 align:start position:0% domain reflectors or tdrs they're the most<20:18:01.256> expensive<20:18:02.104> out<20:18:02.512> of<20:18:02.696> the<20:18:02.824> three<20:18:03.120> so<20:18:04.016> as<20:18:04.192> we 20:18:04.366 --> 20:18:04.376 align:start position:0% most expensive out of the three so as we 20:18:04.376 --> 20:18:06.470 align:start position:0% most expensive out of the three so as we move<20:18:04.616> we're<20:18:05.040> going<20:18:05.216> from 20:18:06.470 --> 20:18:06.480 align:start position:0% move we're going from 20:18:06.480 --> 20:18:09.230 align:start position:0% move we're going from less 20:18:09.230 --> 20:18:09.240 align:start position:0% less 20:18:09.240 --> 20:18:11.990 align:start position:0% less to<20:18:09.656> more<20:18:09.832> they<20:18:10.552> test<20:18:10.744> exactly<20:18:11.336> where<20:18:11.576> a<20:18:11.824> break 20:18:11.990 --> 20:18:12.000 align:start position:0% to more they test exactly where a break 20:18:12.000 --> 20:18:14.150 align:start position:0% to more they test exactly where a break or<20:18:12.240> issue<20:18:12.600> is<20:18:12.832> and<20:18:13.080> the<20:18:13.192> cable<20:18:13.320> can<20:18:13.800> be<20:18:13.920> found 20:18:14.150 --> 20:18:14.160 align:start position:0% or issue is and the cable can be found 20:18:14.160 --> 20:18:16.182 align:start position:0% or issue is and the cable can be found so<20:18:14.824> they<20:18:14.936> do<20:18:15.056> this<20:18:15.176> by<20:18:15.360> sending<20:18:15.720> basically<20:18:16.016> out 20:18:16.182 --> 20:18:16.192 align:start position:0% so they do this by sending basically out 20:18:16.192 --> 20:18:18.470 align:start position:0% so they do this by sending basically out a<20:18:16.376> signal<20:18:16.680> and<20:18:17.040> they<20:18:17.216> wait<20:18:17.400> to<20:18:17.576> see<20:18:17.824> how<20:18:18.240> long 20:18:18.470 --> 20:18:18.480 align:start position:0% a signal and they wait to see how long 20:18:18.480 --> 20:18:21.590 align:start position:0% a signal and they wait to see how long that<20:18:19.320> signal<20:18:19.744> if<20:18:20.216> I<20:18:20.336> have<20:18:20.464> a<20:18:20.576> signal 20:18:21.590 --> 20:18:21.600 align:start position:0% that signal if I have a signal 20:18:21.600 --> 20:18:24.710 align:start position:0% that signal if I have a signal let's<20:18:22.016> say<20:18:22.144> we<20:18:22.320> make<20:18:22.552> a<20:18:22.800> little<20:18:22.856> chord<20:18:23.160> here 20:18:24.710 --> 20:18:24.720 align:start position:0% let's say we make a little chord here 20:18:24.720 --> 20:18:26.750 align:start position:0% let's say we make a little chord here and<20:18:25.192> I<20:18:25.320> have<20:18:25.440> my<20:18:25.616> time<20:18:25.800> domain<20:18:26.336> reflector 20:18:26.750 --> 20:18:26.760 align:start position:0% and I have my time domain reflector 20:18:26.760 --> 20:18:29.206 align:start position:0% and I have my time domain reflector connected<20:18:27.480> over<20:18:27.656> here<20:18:27.896> it's<20:18:28.496> going<20:18:28.744> to<20:18:28.856> send<20:18:29.040> a 20:18:29.206 --> 20:18:29.216 align:start position:0% connected over here it's going to send a 20:18:29.216 --> 20:18:30.526 align:start position:0% connected over here it's going to send a signal<20:18:29.576> out 20:18:30.526 --> 20:18:30.536 align:start position:0% signal out 20:18:30.536 --> 20:18:35.270 align:start position:0% signal out and<20:18:31.080> it's<20:18:31.320> going<20:18:31.552> to<20:18:31.800> wait<20:18:32.400> and<20:18:33.120> see 20:18:35.270 --> 20:18:35.280 align:start position:0% and it's going to wait and see 20:18:35.280 --> 20:18:37.734 align:start position:0% and it's going to wait and see how<20:18:35.936> long<20:18:36.056> it<20:18:36.296> takes<20:18:36.536> before<20:18:36.832> it's<20:18:37.144> reflected 20:18:37.734 --> 20:18:37.744 align:start position:0% how long it takes before it's reflected 20:18:37.744 --> 20:18:40.734 align:start position:0% how long it takes before it's reflected back 20:18:40.734 --> 20:18:40.744 align:start position:0% 20:18:40.744 --> 20:18:42.710 align:start position:0% then<20:18:41.160> they<20:18:41.400> convert<20:18:41.760> this<20:18:41.936> time<20:18:42.120> into<20:18:42.424> a 20:18:42.710 --> 20:18:42.720 align:start position:0% then they convert this time into a 20:18:42.720 --> 20:18:45.046 align:start position:0% then they convert this time into a distance<20:18:42.832> so<20:18:43.192> they<20:18:43.376> know<20:18:43.504> how<20:18:44.040> far<20:18:44.400> along<20:18:44.696> the 20:18:45.046 --> 20:18:45.056 align:start position:0% distance so they know how far along the 20:18:45.056 --> 20:18:47.270 align:start position:0% distance so they know how far along the cable<20:18:45.240> error<20:18:45.656> was<20:18:45.784> found<20:18:45.960> this<20:18:46.744> way<20:18:46.976> they<20:18:47.160> can 20:18:47.270 --> 20:18:47.280 align:start position:0% cable error was found this way they can 20:18:47.280 --> 20:18:49.790 align:start position:0% cable error was found this way they can literally<20:18:47.576> tell<20:18:47.872> us<20:18:48.056> where 20:18:49.790 --> 20:18:49.800 align:start position:0% literally tell us where 20:18:49.800 --> 20:18:52.486 align:start position:0% literally tell us where the<20:18:50.216> problem<20:18:50.336> took<20:18:50.696> place<20:18:51.000> and<20:18:51.784> help<20:18:52.016> us<20:18:52.144> fix 20:18:52.486 --> 20:18:52.496 align:start position:0% the problem took place and help us fix 20:18:52.496 --> 20:18:54.886 align:start position:0% the problem took place and help us fix the<20:18:52.800> problem<20:18:53.040> at<20:18:53.464> its<20:18:53.760> source<20:18:54.056> as<20:18:54.600> opposed<20:18:54.896> to 20:18:54.886 --> 20:18:54.896 align:start position:0% the problem at its source as opposed to 20:18:54.896 --> 20:18:57.046 align:start position:0% the problem at its source as opposed to us<20:18:55.144> having<20:18:55.440> to<20:18:55.856> sort<20:18:56.216> of<20:18:56.280> try<20:18:56.464> to<20:18:56.576> find<20:18:56.760> this 20:18:57.046 --> 20:18:57.056 align:start position:0% us having to sort of try to find this 20:18:57.056 --> 20:18:59.926 align:start position:0% us having to sort of try to find this blindly<20:18:58.016> the<20:18:58.976> last<20:18:59.104> thing<20:18:59.400> I<20:18:59.576> want<20:18:59.696> to<20:18:59.824> talk 20:18:59.926 --> 20:18:59.936 align:start position:0% blindly the last thing I want to talk 20:18:59.936 --> 20:19:01.670 align:start position:0% blindly the last thing I want to talk about<20:19:00.056> we<20:19:00.424> talked<20:19:00.656> about<20:19:00.720> this<20:19:00.960> in<20:19:01.080> a<20:19:01.256> plus<20:19:01.440> as 20:19:01.670 --> 20:19:01.680 align:start position:0% about we talked about this in a plus as 20:19:01.680 --> 20:19:05.686 align:start position:0% about we talked about this in a plus as well<20:19:01.856> is<20:19:02.512> postcards<20:19:03.480> post<20:19:04.440> stands<20:19:05.040> for<20:19:05.280> power 20:19:05.686 --> 20:19:05.696 align:start position:0% well is postcards post stands for power 20:19:05.696 --> 20:19:07.006 align:start position:0% well is postcards post stands for power on 20:19:07.006 --> 20:19:07.016 align:start position:0% on 20:19:07.016 --> 20:19:09.526 align:start position:0% on self-test<20:19:08.464> and<20:19:08.872> you<20:19:09.000> might<20:19:09.120> remember<20:19:09.240> this 20:19:09.526 --> 20:19:09.536 align:start position:0% self-test and you might remember this 20:19:09.536 --> 20:19:11.502 align:start position:0% self-test and you might remember this from<20:19:09.832> the<20:19:10.080> beep<20:19:10.376> that<20:19:10.680> you<20:19:10.800> get<20:19:10.920> at<20:19:11.280> the<20:19:11.400> very 20:19:11.502 --> 20:19:11.512 align:start position:0% from the beep that you get at the very 20:19:11.512 --> 20:19:14.030 align:start position:0% from the beep that you get at the very beginning<20:19:11.824> when<20:19:12.296> your<20:19:12.480> computer<20:19:12.656> starts<20:19:13.320> up 20:19:14.030 --> 20:19:14.040 align:start position:0% beginning when your computer starts up 20:19:14.040 --> 20:19:17.454 align:start position:0% beginning when your computer starts up this<20:19:14.760> card<20:19:15.000> is<20:19:15.424> inserted<20:19:16.016> into<20:19:16.192> a<20:19:16.552> slot<20:19:16.920> of<20:19:17.280> a 20:19:17.454 --> 20:19:17.464 align:start position:0% this card is inserted into a slot of a 20:19:17.464 --> 20:19:21.046 align:start position:0% this card is inserted into a slot of a device<20:19:17.640> and<20:19:18.600> it<20:19:18.784> can<20:19:19.016> tell<20:19:19.320> us<20:19:19.576> what<20:19:20.576> is<20:19:20.824> not 20:19:21.046 --> 20:19:21.056 align:start position:0% device and it can tell us what is not 20:19:21.056 --> 20:19:24.414 align:start position:0% device and it can tell us what is not working<20:19:21.480> in<20:19:22.376> the<20:19:22.552> in<20:19:23.040> the<20:19:23.336> system<20:19:23.512> by<20:19:24.176> giving 20:19:24.414 --> 20:19:24.424 align:start position:0% working in the in the system by giving 20:19:24.424 --> 20:19:28.486 align:start position:0% working in the in the system by giving us<20:19:24.656> generally<20:19:25.216> a<20:19:26.216> sort<20:19:26.640> of<20:19:26.824> code<20:19:27.360> called<20:19:28.144> a 20:19:28.486 --> 20:19:28.496 align:start position:0% us generally a sort of code called a 20:19:28.496 --> 20:19:31.966 align:start position:0% us generally a sort of code called a postcode<20:19:29.424> sometimes<20:19:30.424> this<20:19:31.080> is<20:19:31.192> a<20:19:31.440> beep<20:19:31.744> code 20:19:31.966 --> 20:19:31.976 align:start position:0% postcode sometimes this is a beep code 20:19:31.976 --> 20:19:33.110 align:start position:0% postcode sometimes this is a beep code as<20:19:32.336> well 20:19:33.110 --> 20:19:33.120 align:start position:0% as well 20:19:33.120 --> 20:19:35.566 align:start position:0% as well generally<20:19:33.832> speaking<20:19:34.320> you<20:19:34.744> have<20:19:34.920> to<20:19:35.160> relate 20:19:35.566 --> 20:19:35.576 align:start position:0% generally speaking you have to relate 20:19:35.576 --> 20:19:39.590 align:start position:0% generally speaking you have to relate the<20:19:36.000> code<20:19:36.504> to<20:19:37.504> a<20:19:37.800> manual<20:19:38.400> to<20:19:38.872> figure<20:19:39.000> out<20:19:39.296> what 20:19:39.590 --> 20:19:39.600 align:start position:0% the code to a manual to figure out what 20:19:39.600 --> 20:19:41.206 align:start position:0% the code to a manual to figure out what it's<20:19:39.720> telling<20:19:40.144> us 20:19:41.206 --> 20:19:41.216 align:start position:0% it's telling us 20:19:41.216 --> 20:19:42.886 align:start position:0% it's telling us these<20:19:41.872> cards<20:19:42.120> are<20:19:42.240> really<20:19:42.360> beneficial 20:19:42.886 --> 20:19:42.896 align:start position:0% these cards are really beneficial 20:19:42.896 --> 20:19:45.046 align:start position:0% these cards are really beneficial because<20:19:43.320> they<20:19:43.744> allow<20:19:44.040> us<20:19:44.160> to<20:19:44.400> test<20:19:44.640> a 20:19:45.046 --> 20:19:45.056 align:start position:0% because they allow us to test a 20:19:45.056 --> 20:19:47.390 align:start position:0% because they allow us to test a non-starting<20:19:45.720> system<20:19:45.960> without<20:19:46.744> having<20:19:47.104> to 20:19:47.390 --> 20:19:47.400 align:start position:0% non-starting system without having to 20:19:47.400 --> 20:19:48.950 align:start position:0% non-starting system without having to start<20:19:47.640> from<20:19:47.936> scratch<20:19:48.176> and<20:19:48.424> restore<20:19:48.784> the 20:19:48.950 --> 20:19:48.960 align:start position:0% start from scratch and restore the 20:19:48.960 --> 20:19:50.990 align:start position:0% start from scratch and restore the entire<20:19:49.256> thing<20:19:49.552> in<20:19:50.280> other<20:19:50.400> words<20:19:50.576> they<20:19:50.872> can 20:19:50.990 --> 20:19:51.000 align:start position:0% entire thing in other words they can 20:19:51.000 --> 20:19:52.790 align:start position:0% entire thing in other words they can test<20:19:51.120> the<20:19:51.360> system<20:19:51.600> that<20:19:52.256> would<20:19:52.440> otherwise 20:19:52.790 --> 20:19:52.800 align:start position:0% test the system that would otherwise 20:19:52.800 --> 20:19:54.590 align:start position:0% test the system that would otherwise have<20:19:53.280> to<20:19:53.400> be<20:19:53.576> restored<20:19:54.000> to<20:19:54.240> a<20:19:54.480> previous 20:19:54.590 --> 20:19:54.600 align:start position:0% have to be restored to a previous 20:19:54.600 --> 20:19:57.822 align:start position:0% have to be restored to a previous version<20:19:55.144> or<20:19:55.800> which<20:19:56.104> we'd<20:19:56.400> have<20:19:56.512> to<20:19:56.640> rebuild<20:19:57.056> so 20:19:57.822 --> 20:19:57.832 align:start position:0% version or which we'd have to rebuild so 20:19:57.832 --> 20:19:59.814 align:start position:0% version or which we'd have to rebuild so the<20:19:58.016> cards<20:19:58.320> run<20:19:58.496> the<20:19:58.744> tests<20:19:59.104> while<20:19:59.400> the<20:19:59.640> system 20:19:59.814 --> 20:19:59.824 align:start position:0% the cards run the tests while the system 20:19:59.824 --> 20:20:02.326 align:start position:0% the cards run the tests while the system is<20:20:00.056> attempting<20:20:00.480> to<20:20:00.656> start<20:20:00.832> up<20:20:01.144> and<20:20:01.920> gives<20:20:02.160> us 20:20:02.326 --> 20:20:02.336 align:start position:0% is attempting to start up and gives us 20:20:02.336 --> 20:20:05.270 align:start position:0% is attempting to start up and gives us this<20:20:02.760> beep<20:20:03.240> code<20:20:03.480> or<20:20:03.720> this<20:20:04.080> error<20:20:04.496> code 20:20:05.270 --> 20:20:05.280 align:start position:0% this beep code or this error code 20:20:05.280 --> 20:20:07.734 align:start position:0% this beep code or this error code then<20:20:05.760> we<20:20:06.056> can<20:20:06.176> go<20:20:06.424> to<20:20:06.600> the<20:20:06.832> code 20:20:07.734 --> 20:20:07.744 align:start position:0% then we can go to the code 20:20:07.744 --> 20:20:09.774 align:start position:0% then we can go to the code look<20:20:08.216> at<20:20:08.400> a<20:20:08.576> list<20:20:08.760> and<20:20:09.000> determine<20:20:09.360> where<20:20:09.600> the 20:20:09.774 --> 20:20:09.784 align:start position:0% look at a list and determine where the 20:20:09.784 --> 20:20:11.814 align:start position:0% look at a list and determine where the problem<20:20:10.016> is<20:20:10.256> for<20:20:10.856> instance<20:20:11.104> perhaps<20:20:11.464> the<20:20:11.696> ram 20:20:11.814 --> 20:20:11.824 align:start position:0% problem is for instance perhaps the ram 20:20:11.824 --> 20:20:14.454 align:start position:0% problem is for instance perhaps the ram is<20:20:12.120> bad<20:20:12.424> or<20:20:13.192> is<20:20:13.552> not<20:20:13.800> just<20:20:13.920> not<20:20:14.104> seated 20:20:14.454 --> 20:20:14.464 align:start position:0% is bad or is not just not seated 20:20:14.464 --> 20:20:16.310 align:start position:0% is bad or is not just not seated properly<20:20:14.872> or<20:20:15.360> perhaps<20:20:15.656> it's<20:20:15.832> not<20:20:15.960> able<20:20:16.192> to 20:20:16.310 --> 20:20:16.320 align:start position:0% properly or perhaps it's not able to 20:20:16.320 --> 20:20:18.950 align:start position:0% properly or perhaps it's not able to find<20:20:16.496> its<20:20:16.856> firmware 20:20:18.950 --> 20:20:18.960 align:start position:0% find its firmware 20:20:18.960 --> 20:20:20.686 align:start position:0% find its firmware so<20:20:19.440> just<20:20:19.552> to<20:20:19.744> recap<20:20:20.040> we<20:20:20.336> talked<20:20:20.640> about 20:20:20.686 --> 20:20:20.696 align:start position:0% so just to recap we talked about 20:20:20.696 --> 20:20:22.606 align:start position:0% so just to recap we talked about hardware<20:20:21.176> troubleshooting<20:20:22.016> again<20:20:22.192> Hardware 20:20:22.606 --> 20:20:22.616 align:start position:0% hardware troubleshooting again Hardware 20:20:22.616 --> 20:20:25.606 align:start position:0% hardware troubleshooting again Hardware is<20:20:23.040> the<20:20:23.216> hard<20:20:23.400> stuff<20:20:23.696> not<20:20:24.360> software<20:20:24.832> we 20:20:25.606 --> 20:20:25.616 align:start position:0% is the hard stuff not software we 20:20:25.616 --> 20:20:28.006 align:start position:0% is the hard stuff not software we physically<20:20:25.976> have<20:20:26.280> to<20:20:26.400> deal<20:20:26.576> with<20:20:26.824> it<20:20:27.000> and<20:20:27.832> some 20:20:28.006 --> 20:20:28.016 align:start position:0% physically have to deal with it and some 20:20:28.016 --> 20:20:29.862 align:start position:0% physically have to deal with it and some of<20:20:28.144> the<20:20:28.256> common<20:20:28.376> tools<20:20:28.800> we<20:20:28.976> looked<20:20:29.280> at<20:20:29.336> were<20:20:29.640> a 20:20:29.862 --> 20:20:29.872 align:start position:0% of the common tools we looked at were a 20:20:29.872 --> 20:20:32.454 align:start position:0% of the common tools we looked at were a diagnostic<20:20:30.480> disk<20:20:30.960> which<20:20:31.616> generally<20:20:31.976> is<20:20:32.280> just 20:20:32.454 --> 20:20:32.464 align:start position:0% diagnostic disk which generally is just 20:20:32.464 --> 20:20:37.790 align:start position:0% diagnostic disk which generally is just going<20:20:32.640> to<20:20:32.824> tell<20:20:32.936> us<20:20:33.144> which<20:20:34.144> item 20:20:37.790 --> 20:20:37.800 align:start position:0% 20:20:37.800 --> 20:20:41.750 align:start position:0% is<20:20:38.160> malfunctioning 20:20:41.750 --> 20:20:41.760 align:start position:0% 20:20:41.760 --> 20:20:44.326 align:start position:0% and<20:20:42.176> remember<20:20:42.360> a<20:20:42.720> diagnostic<20:20:43.320> disk<20:20:43.680> is<20:20:44.040> in 20:20:44.326 --> 20:20:44.336 align:start position:0% and remember a diagnostic disk is in 20:20:44.336 --> 20:20:46.430 align:start position:0% and remember a diagnostic disk is in effect 20:20:46.430 --> 20:20:46.440 align:start position:0% effect 20:20:46.440 --> 20:20:48.590 align:start position:0% effect piece<20:20:47.040> of<20:20:47.104> software 20:20:48.590 --> 20:20:48.600 align:start position:0% piece of software 20:20:48.600 --> 20:20:51.110 align:start position:0% piece of software we<20:20:49.016> also<20:20:49.320> looked<20:20:49.504> at<20:20:49.552> a<20:20:49.680> multimeter 20:20:51.110 --> 20:20:51.120 align:start position:0% we also looked at a multimeter 20:20:51.120 --> 20:20:54.950 align:start position:0% we also looked at a multimeter which<20:20:51.656> is<20:20:51.832> for<20:20:52.192> electrical<20:20:53.400> things<20:20:53.936> this<20:20:54.896> is 20:20:54.950 --> 20:20:54.960 align:start position:0% which is for electrical things this is 20:20:54.960 --> 20:20:57.350 align:start position:0% which is for electrical things this is going<20:20:55.144> to<20:20:55.192> test<20:20:55.440> volts 20:20:57.350 --> 20:20:57.360 align:start position:0% going to test volts 20:20:57.360 --> 20:21:00.110 align:start position:0% going to test volts resistance 20:21:00.110 --> 20:21:00.120 align:start position:0% resistance 20:21:00.120 --> 20:21:04.790 align:start position:0% resistance and<20:21:00.600> current 20:21:04.790 --> 20:21:04.800 align:start position:0% 20:21:04.800 --> 20:21:07.182 align:start position:0% faults<20:21:05.400> and<20:21:05.464> resistance<20:21:05.936> are<20:21:06.424> perhaps<20:21:06.896> the 20:21:07.182 --> 20:21:07.192 align:start position:0% faults and resistance are perhaps the 20:21:07.192 --> 20:21:09.710 align:start position:0% faults and resistance are perhaps the most<20:21:07.320> important<20:21:07.744> ones<20:21:08.040> resistance<20:21:09.000> for<20:21:09.296> fuses 20:21:09.710 --> 20:21:09.720 align:start position:0% most important ones resistance for fuses 20:21:09.720 --> 20:21:11.206 align:start position:0% most important ones resistance for fuses or<20:21:09.960> Breakers 20:21:11.206 --> 20:21:11.216 align:start position:0% or Breakers 20:21:11.216 --> 20:21:15.886 align:start position:0% or Breakers Volts<20:21:11.872> for<20:21:12.056> power<20:21:12.296> supplies 20:21:15.886 --> 20:21:15.896 align:start position:0% 20:21:15.896 --> 20:21:18.286 align:start position:0% we<20:21:16.256> also<20:21:16.440> looked<20:21:16.616> at<20:21:16.744> cable<20:21:17.040> testers<20:21:17.512> remember 20:21:18.286 --> 20:21:18.296 align:start position:0% we also looked at cable testers remember 20:21:18.296 --> 20:21:19.670 align:start position:0% we also looked at cable testers remember there<20:21:18.656> are<20:21:18.784> three<20:21:18.896> different<20:21:19.080> ones<20:21:19.376> that<20:21:19.552> we 20:21:19.670 --> 20:21:19.680 align:start position:0% there are three different ones that we 20:21:19.680 --> 20:21:22.734 align:start position:0% there are three different ones that we looked<20:21:19.920> at<20:21:20.360> continuity<20:21:21.360> testers<20:21:21.896> are<20:21:22.552> just 20:21:22.734 --> 20:21:22.744 align:start position:0% looked at continuity testers are just 20:21:22.744 --> 20:21:23.926 align:start position:0% looked at continuity testers are just going<20:21:22.856> to<20:21:22.976> tell<20:21:23.040> us<20:21:23.216> whether<20:21:23.512> or<20:21:23.696> not<20:21:23.760> the 20:21:23.926 --> 20:21:23.936 align:start position:0% going to tell us whether or not the 20:21:23.936 --> 20:21:25.846 align:start position:0% going to tell us whether or not the cable<20:21:24.240> works 20:21:25.846 --> 20:21:25.856 align:start position:0% cable works 20:21:25.856 --> 20:21:28.134 align:start position:0% cable works cabling<20:21:26.696> testers 20:21:28.134 --> 20:21:28.144 align:start position:0% cabling testers 20:21:28.144 --> 20:21:30.526 align:start position:0% cabling testers otherwise<20:21:28.744> known<20:21:28.976> as<20:21:29.160> data<20:21:29.696> cabling<20:21:30.056> testers 20:21:30.526 --> 20:21:30.536 align:start position:0% otherwise known as data cabling testers 20:21:30.536 --> 20:21:33.414 align:start position:0% otherwise known as data cabling testers will<20:21:31.376> tell<20:21:31.616> us<20:21:31.800> actually<20:21:32.040> which<20:21:32.464> pins<20:21:32.936> aren't 20:21:33.414 --> 20:21:33.424 align:start position:0% will tell us actually which pins aren't 20:21:33.424 --> 20:21:34.606 align:start position:0% will tell us actually which pins aren't working 20:21:34.606 --> 20:21:34.616 align:start position:0% working 20:21:34.616 --> 20:21:36.166 align:start position:0% working and 20:21:36.166 --> 20:21:36.176 align:start position:0% and 20:21:36.176 --> 20:21:40.790 align:start position:0% and time<20:21:37.080> domain<20:21:37.920> reflectometers 20:21:40.790 --> 20:21:40.800 align:start position:0% time domain reflectometers 20:21:40.800 --> 20:21:49.790 align:start position:0% time domain reflectometers let<20:21:41.280> me<20:21:41.400> write<20:21:41.640> that<20:21:41.872> out 20:21:49.790 --> 20:21:49.800 align:start position:0% 20:21:49.800 --> 20:21:54.166 align:start position:0% will<20:21:50.216> tell<20:21:50.464> us<20:21:50.640> where 20:21:54.166 --> 20:21:54.176 align:start position:0% 20:21:54.176 --> 20:21:56.030 align:start position:0% the<20:21:54.720> error<20:21:54.960> is<20:21:55.016> occurring 20:21:56.030 --> 20:21:56.040 align:start position:0% the error is occurring 20:21:56.040 --> 20:21:58.070 align:start position:0% the error is occurring finally<20:21:56.760> we<20:21:57.000> have<20:21:57.120> our<20:21:57.296> postcard<20:21:57.784> remember 20:21:58.070 --> 20:21:58.080 align:start position:0% finally we have our postcard remember 20:21:58.080 --> 20:22:01.846 align:start position:0% finally we have our postcard remember post<20:21:58.552> stands<20:21:59.104> for<20:21:59.280> power<20:22:00.056> on 20:22:01.846 --> 20:22:01.856 align:start position:0% post stands for power on 20:22:01.856 --> 20:22:03.414 align:start position:0% post stands for power on self 20:22:03.414 --> 20:22:03.424 align:start position:0% self 20:22:03.424 --> 20:22:04.910 align:start position:0% self test 20:22:04.910 --> 20:22:04.920 align:start position:0% test 20:22:04.920 --> 20:22:07.182 align:start position:0% test and<20:22:05.336> this<20:22:05.464> is<20:22:05.512> going<20:22:05.696> to<20:22:05.824> tell<20:22:05.936> us<20:22:06.176> in<20:22:06.960> a 20:22:07.182 --> 20:22:07.192 align:start position:0% and this is going to tell us in a 20:22:07.192 --> 20:22:10.846 align:start position:0% and this is going to tell us in a non-functioning 20:22:10.846 --> 20:22:10.856 align:start position:0% 20:22:10.856 --> 20:22:17.454 align:start position:0% or<20:22:11.336> non-starting<20:22:12.240> system 20:22:17.454 --> 20:22:17.464 align:start position:0% 20:22:17.464 --> 20:22:22.606 align:start position:0% where<20:22:18.120> the<20:22:18.424> error<20:22:18.720> is 20:22:22.606 --> 20:22:22.616 align:start position:0% 20:22:22.616 --> 20:22:24.950 align:start position:0% it's<20:22:23.040> very<20:22:23.400> much<20:22:23.576> like<20:22:23.872> a<20:22:24.176> diagnostic<20:22:24.784> disc 20:22:24.950 --> 20:22:24.960 align:start position:0% it's very much like a diagnostic disc 20:22:24.960 --> 20:22:28.846 align:start position:0% it's very much like a diagnostic disc however<20:22:25.744> the<20:22:25.976> diagnostic<20:22:26.576> disc<20:22:26.824> does 20:22:28.846 --> 20:22:28.856 align:start position:0% however the diagnostic disc does 20:22:28.856 --> 20:22:31.966 align:start position:0% however the diagnostic disc does require<20:22:29.640> the<20:22:30.600> CPU 20:22:31.966 --> 20:22:31.976 align:start position:0% require the CPU 20:22:31.976 --> 20:22:33.350 align:start position:0% require the CPU clock 20:22:33.350 --> 20:22:33.360 align:start position:0% clock 20:22:33.360 --> 20:22:39.110 align:start position:0% clock and<20:22:34.192> the<20:22:34.680> disk<20:22:35.160> interface 20:22:39.110 --> 20:22:39.120 align:start position:0% 20:22:39.120 --> 20:22:41.686 align:start position:0% is<20:22:39.600> functioning<20:22:40.616> the<20:22:40.920> postcard<20:22:41.400> it's 20:22:41.686 --> 20:22:41.696 align:start position:0% is functioning the postcard it's 20:22:41.696 --> 20:22:44.030 align:start position:0% is functioning the postcard it's literally<20:22:42.056> a<20:22:42.240> card<20:22:42.360> we<20:22:42.600> insert<20:22:43.016> and<20:22:43.744> it'll 20:22:44.030 --> 20:22:44.040 align:start position:0% literally a card we insert and it'll 20:22:44.040 --> 20:22:46.486 align:start position:0% literally a card we insert and it'll tell<20:22:44.216> us<20:22:44.400> itself<20:22:44.640> it<20:22:45.600> does<20:22:45.720> this<20:22:45.960> again<20:22:46.192> by 20:22:46.486 --> 20:22:46.496 align:start position:0% tell us itself it does this again by 20:22:46.496 --> 20:22:48.774 align:start position:0% tell us itself it does this again by giving<20:22:46.744> us<20:22:47.040> a<20:22:47.400> code<20:22:47.696> that<20:22:48.424> we<20:22:48.536> can<20:22:48.656> then 20:22:48.774 --> 20:22:48.784 align:start position:0% giving us a code that we can then 20:22:48.784 --> 20:22:54.050 align:start position:0% giving us a code that we can then reference<20:22:49.256> on<20:22:49.744> a<20:22:49.856> list 20:22:54.050 --> 20:22:54.060 align:start position:0% 20:22:54.060 --> 20:23:09.846 align:start position:0% [Music] 20:23:09.846 --> 20:23:09.856 align:start position:0% 20:23:09.856 --> 20:23:13.134 align:start position:0% welcome<20:23:10.856> to<20:23:11.160> module<20:23:11.640> 15<20:23:11.824> lesson<20:23:12.424> 1A<20:23:12.784> physical 20:23:13.134 --> 20:23:13.144 align:start position:0% welcome to module 15 lesson 1A physical 20:23:13.144 --> 20:23:18.710 align:start position:0% welcome to module 15 lesson 1A physical testing<20:23:13.680> tools<20:23:14.120> just<20:23:15.120> updated<20:23:16.160> the<20:23:17.176> uh<20:23:18.176> from 20:23:18.710 --> 20:23:18.720 align:start position:0% testing tools just updated the uh from 20:23:18.720 --> 20:23:20.454 align:start position:0% testing tools just updated the uh from the<20:23:18.832> last<20:23:18.960> presentation<20:23:19.504> really<20:23:19.920> there's<20:23:20.280> a 20:23:20.454 --> 20:23:20.464 align:start position:0% the last presentation really there's a 20:23:20.464 --> 20:23:23.270 align:start position:0% the last presentation really there's a few<20:23:20.576> extra<20:23:20.760> little<20:23:21.120> things<20:23:22.016> slipped<20:23:22.552> into<20:23:22.744> the 20:23:23.270 --> 20:23:23.280 align:start position:0% few extra little things slipped into the 20:23:23.280 --> 20:23:25.790 align:start position:0% few extra little things slipped into the syllabus<20:23:23.936> which<20:23:24.296> I<20:23:24.536> I<20:23:24.832> think<20:23:25.080> is<20:23:25.192> important<20:23:25.616> to 20:23:25.790 --> 20:23:25.800 align:start position:0% syllabus which I I think is important to 20:23:25.800 --> 20:23:26.814 align:start position:0% syllabus which I I think is important to cover 20:23:26.814 --> 20:23:26.824 align:start position:0% cover 20:23:26.824 --> 20:23:29.094 align:start position:0% cover the<20:23:27.296> cable<20:23:27.424> crimper<20:23:27.960> the<20:23:28.256> punch<20:23:28.376> down<20:23:28.680> Tool 20:23:29.094 --> 20:23:29.104 align:start position:0% the cable crimper the punch down Tool 20:23:29.104 --> 20:23:30.646 align:start position:0% the cable crimper the punch down Tool The<20:23:29.216> Wire<20:23:29.336> Strippers 20:23:30.646 --> 20:23:30.656 align:start position:0% The Wire Strippers 20:23:30.656 --> 20:23:33.590 align:start position:0% The Wire Strippers otdr<20:23:31.256> cable<20:23:32.160> certifier<20:23:32.824> we<20:23:33.296> may<20:23:33.480> have 20:23:33.590 --> 20:23:33.600 align:start position:0% otdr cable certifier we may have 20:23:33.600 --> 20:23:35.502 align:start position:0% otdr cable certifier we may have actually<20:23:33.784> mentioned<20:23:34.144> these<20:23:34.440> in<20:23:34.616> other<20:23:34.800> areas 20:23:35.502 --> 20:23:35.512 align:start position:0% actually mentioned these in other areas 20:23:35.512 --> 20:23:38.270 align:start position:0% actually mentioned these in other areas of<20:23:36.056> the<20:23:36.480> presentation<20:23:37.320> but<20:23:37.616> I<20:23:37.800> just<20:23:37.920> wanted<20:23:38.104> to 20:23:38.270 --> 20:23:38.280 align:start position:0% of the presentation but I just wanted to 20:23:38.280 --> 20:23:42.166 align:start position:0% of the presentation but I just wanted to specifically<20:23:38.824> address<20:23:39.720> each<20:23:40.256> one 20:23:42.166 --> 20:23:42.176 align:start position:0% specifically address each one 20:23:42.176 --> 20:23:44.990 align:start position:0% specifically address each one cable<20:23:42.784> crimpa<20:23:43.440> also<20:23:43.744> known<20:23:43.800> as<20:23:43.976> a<20:23:44.160> y<20:23:44.280> crimp<20:23:44.824> hat 20:23:44.990 --> 20:23:45.000 align:start position:0% cable crimpa also known as a y crimp hat 20:23:45.000 --> 20:23:47.326 align:start position:0% cable crimpa also known as a y crimp hat you'll<20:23:45.480> be<20:23:45.600> familiar<20:23:45.960> with<20:23:46.080> this<20:23:46.256> tool<20:23:46.616> if 20:23:47.326 --> 20:23:47.336 align:start position:0% you'll be familiar with this tool if 20:23:47.336 --> 20:23:49.134 align:start position:0% you'll be familiar with this tool if you've<20:23:47.576> created<20:23:47.872> your<20:23:48.176> own<20:23:48.296> cables<20:23:48.784> a<20:23:48.960> lot<20:23:49.016> of 20:23:49.134 --> 20:23:49.144 align:start position:0% you've created your own cables a lot of 20:23:49.144 --> 20:23:51.110 align:start position:0% you've created your own cables a lot of people<20:23:49.192> do<20:23:49.440> at<20:23:49.680> home<20:23:49.856> just<20:23:50.512> to<20:23:50.696> save<20:23:50.824> money 20:23:51.110 --> 20:23:51.120 align:start position:0% people do at home just to save money 20:23:51.120 --> 20:23:52.910 align:start position:0% people do at home just to save money because<20:23:51.360> they're<20:23:51.656> so<20:23:51.896> expensive<20:23:52.376> if<20:23:52.616> you<20:23:52.744> buy 20:23:52.910 --> 20:23:52.920 align:start position:0% because they're so expensive if you buy 20:23:52.920 --> 20:23:55.966 align:start position:0% because they're so expensive if you buy them<20:23:53.104> from<20:23:53.400> the<20:23:54.176> electronic<20:23:54.784> shops<20:23:55.256> for<20:23:55.856> some 20:23:55.966 --> 20:23:55.976 align:start position:0% them from the electronic shops for some 20:23:55.976 --> 20:23:56.990 align:start position:0% them from the electronic shops for some reason 20:23:56.990 --> 20:23:57.000 align:start position:0% reason 20:23:57.000 --> 20:24:00.110 align:start position:0% reason and<20:23:57.656> also<20:23:58.376> if<20:23:58.744> for<20:23:59.464> any<20:23:59.576> reason<20:23:59.760> something 20:24:00.110 --> 20:24:00.120 align:start position:0% and also if for any reason something 20:24:00.120 --> 20:24:01.670 align:start position:0% and also if for any reason something goes<20:24:00.600> wrong<20:24:00.720> with<20:24:01.080> the<20:24:01.192> end<20:24:01.256> of<20:24:01.376> one<20:24:01.504> of<20:24:01.616> your 20:24:01.670 --> 20:24:01.680 align:start position:0% goes wrong with the end of one of your 20:24:01.680 --> 20:24:04.910 align:start position:0% goes wrong with the end of one of your cables<20:24:02.216> you<20:24:03.000> could<20:24:03.056> just<20:24:03.240> snip<20:24:03.656> off<20:24:03.832> the<20:24:04.680> end 20:24:04.910 --> 20:24:04.920 align:start position:0% cables you could just snip off the end 20:24:04.920 --> 20:24:07.246 align:start position:0% cables you could just snip off the end and<20:24:05.160> just<20:24:05.872> um<20:24:05.872> create<20:24:06.120> your<20:24:06.480> own 20:24:07.246 --> 20:24:07.256 align:start position:0% and just um create your own 20:24:07.256 --> 20:24:10.542 align:start position:0% and just um create your own a<20:24:07.800> cable<20:24:08.104> it's<20:24:08.824> fairly<20:24:09.480> easy<20:24:09.600> to<20:24:09.896> do<20:24:10.016> well<20:24:10.376> with 20:24:10.542 --> 20:24:10.552 align:start position:0% a cable it's fairly easy to do well with 20:24:10.552 --> 20:24:12.182 align:start position:0% a cable it's fairly easy to do well with a<20:24:10.680> little<20:24:10.800> bit<20:24:10.976> of<20:24:11.104> practice<20:24:11.400> like<20:24:11.872> anything 20:24:12.182 --> 20:24:12.192 align:start position:0% a little bit of practice like anything 20:24:12.192 --> 20:24:14.814 align:start position:0% a little bit of practice like anything so<20:24:13.192> you'll<20:24:13.440> need<20:24:13.552> a<20:24:13.744> cable<20:24:13.920> crimpo<20:24:14.512> which<20:24:14.696> you 20:24:14.814 --> 20:24:14.824 align:start position:0% so you'll need a cable crimpo which you 20:24:14.824 --> 20:24:17.326 align:start position:0% so you'll need a cable crimpo which you also<20:24:15.056> buy<20:24:15.240> from<20:24:15.480> the<20:24:15.656> electronic<20:24:16.144> shop<20:24:16.376> use<20:24:17.040> to 20:24:17.326 --> 20:24:17.336 align:start position:0% also buy from the electronic shop use to 20:24:17.336 --> 20:24:18.950 align:start position:0% also buy from the electronic shop use to connect<20:24:17.464> the<20:24:17.824> end<20:24:17.936> of<20:24:18.120> a<20:24:18.296> cable<20:24:18.480> to<20:24:18.720> a 20:24:18.950 --> 20:24:18.960 align:start position:0% connect the end of a cable to a 20:24:18.960 --> 20:24:21.774 align:start position:0% connect the end of a cable to a connector<20:24:19.504> it<20:24:20.400> can<20:24:20.576> depending<20:24:21.424> on<20:24:21.480> which<20:24:21.600> one 20:24:21.774 --> 20:24:21.784 align:start position:0% connector it can depending on which one 20:24:21.784 --> 20:24:23.454 align:start position:0% connector it can depending on which one you<20:24:21.960> buy<20:24:22.144> you<20:24:22.320> can<20:24:22.496> actually<20:24:22.616> strip<20:24:22.920> the<20:24:23.216> cable 20:24:23.454 --> 20:24:23.464 align:start position:0% you buy you can actually strip the cable 20:24:23.464 --> 20:24:27.526 align:start position:0% you buy you can actually strip the cable you<20:24:24.296> separate<20:24:24.656> the<20:24:24.832> wires<20:24:25.320> and<20:24:26.040> then<20:24:26.160> you<20:24:26.576> can 20:24:27.526 --> 20:24:27.536 align:start position:0% you separate the wires and then you can 20:24:27.536 --> 20:24:31.366 align:start position:0% you separate the wires and then you can um insert<20:24:28.440> into<20:24:28.976> inside<20:24:29.336> here<20:24:29.872> the 20:24:31.366 --> 20:24:31.376 align:start position:0% um insert into inside here the 20:24:31.376 --> 20:24:34.246 align:start position:0% um insert into inside here the connector<20:24:32.280> the<20:24:32.640> plastic<20:24:32.936> connector<20:24:33.536> pop<20:24:34.080> the 20:24:34.246 --> 20:24:34.256 align:start position:0% connector the plastic connector pop the 20:24:34.256 --> 20:24:36.526 align:start position:0% connector the plastic connector pop the ends<20:24:34.496> of<20:24:34.552> the<20:24:34.680> cable<20:24:34.856> in<20:24:35.216> which<20:24:35.936> you've<20:24:36.240> also 20:24:36.526 --> 20:24:36.536 align:start position:0% ends of the cable in which you've also 20:24:36.536 --> 20:24:39.526 align:start position:0% ends of the cable in which you've also stripped<20:24:37.256> With<20:24:37.440> a<20:24:37.616> Stripper<20:24:38.000> and<20:24:39.000> uh<20:24:39.176> and<20:24:39.424> then 20:24:39.526 --> 20:24:39.536 align:start position:0% stripped With a Stripper and uh and then 20:24:39.536 --> 20:24:41.454 align:start position:0% stripped With a Stripper and uh and then clamp<20:24:39.832> it<20:24:40.016> closed<20:24:40.440> and<20:24:40.616> that<20:24:40.800> clamps<20:24:41.160> down<20:24:41.280> on 20:24:41.454 --> 20:24:41.464 align:start position:0% clamp it closed and that clamps down on 20:24:41.464 --> 20:24:43.430 align:start position:0% clamp it closed and that clamps down on the<20:24:41.576> wires<20:24:41.872> in<20:24:42.176> the<20:24:42.296> correct<20:24:42.480> door<20:24:42.656> down 20:24:43.430 --> 20:24:43.440 align:start position:0% the wires in the correct door down 20:24:43.440 --> 20:24:45.414 align:start position:0% the wires in the correct door down different<20:24:43.920> types<20:24:44.216> of<20:24:44.280> cable<20:24:44.512> crimples<20:24:45.056> for 20:24:45.414 --> 20:24:45.424 align:start position:0% different types of cable crimples for 20:24:45.424 --> 20:24:47.926 align:start position:0% different types of cable crimples for different<20:24:45.720> connectors 20:24:47.926 --> 20:24:47.936 align:start position:0% different connectors 20:24:47.936 --> 20:24:50.750 align:start position:0% different connectors the<20:24:48.424> punch<20:24:48.600> down<20:24:48.896> tool<20:24:49.376> is<20:24:49.920> known<20:24:50.160> as<20:24:50.336> a<20:24:50.576> chrome 20:24:50.750 --> 20:24:50.760 align:start position:0% the punch down tool is known as a chrome 20:24:50.760 --> 20:24:54.526 align:start position:0% the punch down tool is known as a chrome tool<20:24:51.360> also<20:24:52.160> used<20:24:53.160> to<20:24:53.400> connect<20:24:53.512> wires<20:24:54.176> into 20:24:54.526 --> 20:24:54.536 align:start position:0% tool also used to connect wires into 20:24:54.536 --> 20:25:01.182 align:start position:0% tool also used to connect wires into punch<20:24:54.960> down<20:24:55.192> blocks 20:25:01.182 --> 20:25:01.192 align:start position:0% 20:25:01.192 --> 20:25:03.774 align:start position:0% it<20:25:01.976> strips<20:25:02.400> off<20:25:02.576> the<20:25:02.696> insulation<20:25:03.360> on<20:25:03.536> The<20:25:03.656> Wire 20:25:03.774 --> 20:25:03.784 align:start position:0% it strips off the insulation on The Wire 20:25:03.784 --> 20:25:06.230 align:start position:0% it strips off the insulation on The Wire before<20:25:04.016> inserting<20:25:04.552> it<20:25:04.680> into<20:25:04.800> a<20:25:04.976> punch<20:25:05.160> block 20:25:06.230 --> 20:25:06.240 align:start position:0% before inserting it into a punch block 20:25:06.240 --> 20:25:08.502 align:start position:0% before inserting it into a punch block not<20:25:06.784> something<20:25:06.960> I've<20:25:07.320> used<20:25:07.504> before<20:25:07.744> because<20:25:08.104> I 20:25:08.502 --> 20:25:08.512 align:start position:0% not something I've used before because I 20:25:08.512 --> 20:25:09.166 align:start position:0% not something I've used before because I didn't 20:25:09.166 --> 20:25:09.176 align:start position:0% didn't 20:25:09.176 --> 20:25:09.710 align:start position:0% didn't um 20:25:09.710 --> 20:25:09.720 align:start position:0% um 20:25:09.720 --> 20:25:12.542 align:start position:0% um didn't<20:25:10.376> use<20:25:10.616> any<20:25:10.856> of<20:25:11.040> the<20:25:11.160> punch<20:25:11.512> down<20:25:11.824> blocks 20:25:12.542 --> 20:25:12.552 align:start position:0% didn't use any of the punch down blocks 20:25:12.552 --> 20:25:15.470 align:start position:0% didn't use any of the punch down blocks uh<20:25:13.552> I<20:25:13.800> did<20:25:14.040> some<20:25:14.216> cabling<20:25:14.576> but<20:25:14.872> didn't<20:25:15.056> use<20:25:15.296> a 20:25:15.470 --> 20:25:15.480 align:start position:0% uh I did some cabling but didn't use a 20:25:15.480 --> 20:25:16.542 align:start position:0% uh I did some cabling but didn't use a punch<20:25:15.656> down 20:25:16.542 --> 20:25:16.552 align:start position:0% punch down 20:25:16.552 --> 20:25:18.526 align:start position:0% punch down not<20:25:16.920> something<20:25:17.104> I<20:25:17.400> was<20:25:17.464> interested<20:25:17.824> in<20:25:17.936> wire 20:25:18.526 --> 20:25:18.536 align:start position:0% not something I was interested in wire 20:25:18.536 --> 20:25:20.814 align:start position:0% not something I was interested in wire strippers<20:25:19.080> used<20:25:19.800> to<20:25:20.040> remove<20:25:20.216> electrical 20:25:20.814 --> 20:25:20.824 align:start position:0% strippers used to remove electrical 20:25:20.824 --> 20:25:22.910 align:start position:0% strippers used to remove electrical insulation<20:25:21.240> from<20:25:21.536> my<20:25:21.784> wire<20:25:22.016> on<20:25:22.744> this 20:25:22.910 --> 20:25:22.920 align:start position:0% insulation from my wire on this 20:25:22.920 --> 20:25:24.470 align:start position:0% insulation from my wire on this particular<20:25:23.216> figure<20:25:23.512> you<20:25:24.000> can<20:25:24.056> see<20:25:24.240> the 20:25:24.470 --> 20:25:24.480 align:start position:0% particular figure you can see the 20:25:24.480 --> 20:25:26.814 align:start position:0% particular figure you can see the difference<20:25:24.784> and<20:25:25.616> sizes 20:25:26.814 --> 20:25:26.824 align:start position:0% difference and sizes 20:25:26.824 --> 20:25:28.846 align:start position:0% difference and sizes so<20:25:27.240> you<20:25:27.360> choose<20:25:27.600> the<20:25:27.784> correct<20:25:28.080> size<20:25:28.320> for<20:25:28.680> the 20:25:28.846 --> 20:25:28.856 align:start position:0% so you choose the correct size for the 20:25:28.856 --> 20:25:31.670 align:start position:0% so you choose the correct size for the cable<20:25:29.104> type<20:25:29.400> and<20:25:29.696> that<20:25:29.936> strips<20:25:30.240> out<20:25:30.424> the 20:25:31.670 --> 20:25:31.680 align:start position:0% cable type and that strips out the 20:25:31.680 --> 20:25:33.286 align:start position:0% cable type and that strips out the um<20:25:31.744> housing<20:25:32.216> of<20:25:32.400> the<20:25:32.576> wire<20:25:32.760> the<20:25:33.056> plastic 20:25:33.286 --> 20:25:33.296 align:start position:0% um housing of the wire the plastic 20:25:33.296 --> 20:25:36.470 align:start position:0% um housing of the wire the plastic covering<20:25:34.104> and<20:25:35.104> exposes<20:25:35.640> the<20:25:35.872> actual<20:25:36.120> cable 20:25:36.470 --> 20:25:36.480 align:start position:0% covering and exposes the actual cable 20:25:36.480 --> 20:25:38.150 align:start position:0% covering and exposes the actual cable itself 20:25:38.150 --> 20:25:38.160 align:start position:0% itself 20:25:38.160 --> 20:25:41.150 align:start position:0% itself it<20:25:38.760> has<20:25:38.936> a<20:25:39.120> center<20:25:39.240> notch 20:25:41.150 --> 20:25:41.160 align:start position:0% it has a center notch 20:25:41.160 --> 20:25:44.166 align:start position:0% it has a center notch otdr<20:25:41.760> this<20:25:42.176> stands<20:25:42.536> for<20:25:42.656> optical<20:25:43.192> time<20:25:43.552> domain 20:25:44.166 --> 20:25:44.176 align:start position:0% otdr this stands for optical time domain 20:25:44.176 --> 20:25:46.182 align:start position:0% otdr this stands for optical time domain reflectometer<20:25:45.176> I'm<20:25:45.480> not<20:25:45.720> saying<20:25:45.960> that<20:25:46.080> again 20:25:46.182 --> 20:25:46.192 align:start position:0% reflectometer I'm not saying that again 20:25:46.192 --> 20:25:48.526 align:start position:0% reflectometer I'm not saying that again used<20:25:46.920> to<20:25:47.160> locate<20:25:47.464> faults<20:25:47.872> on<20:25:48.000> networking 20:25:48.526 --> 20:25:48.536 align:start position:0% used to locate faults on networking 20:25:48.536 --> 20:25:49.542 align:start position:0% used to locate faults on networking cable 20:25:49.542 --> 20:25:49.552 align:start position:0% cable 20:25:49.552 --> 20:25:51.526 align:start position:0% cable I<20:25:49.920> mean<20:25:50.040> there's<20:25:50.280> a<20:25:50.512> argument<20:25:50.872> that<20:25:51.240> you<20:25:51.360> if 20:25:51.526 --> 20:25:51.536 align:start position:0% I mean there's a argument that you if 20:25:51.536 --> 20:25:52.790 align:start position:0% I mean there's a argument that you if you<20:25:51.784> just<20:25:51.832> think<20:25:52.016> there's<20:25:52.144> a<20:25:52.320> fault<20:25:52.496> in<20:25:52.680> a 20:25:52.790 --> 20:25:52.800 align:start position:0% you just think there's a fault in a 20:25:52.800 --> 20:25:55.006 align:start position:0% you just think there's a fault in a cable<20:25:52.976> you<20:25:53.216> just<20:25:53.400> swap<20:25:53.640> it<20:25:53.760> out<20:25:53.872> anyway<20:25:54.120> it'd 20:25:55.006 --> 20:25:55.016 align:start position:0% cable you just swap it out anyway it'd 20:25:55.016 --> 20:25:56.750 align:start position:0% cable you just swap it out anyway it'd be<20:25:55.080> cheaper<20:25:55.504> but<20:25:55.744> it's<20:25:55.976> available<20:25:56.216> tool 20:25:56.750 --> 20:25:56.760 align:start position:0% be cheaper but it's available tool 20:25:56.760 --> 20:25:59.502 align:start position:0% be cheaper but it's available tool anyway<20:25:56.936> it<20:25:57.896> sends<20:25:58.256> light<20:25:58.440> into<20:25:58.616> the<20:25:58.856> fiber<20:25:59.216> and 20:25:59.502 --> 20:25:59.512 align:start position:0% anyway it sends light into the fiber and 20:25:59.512 --> 20:26:00.886 align:start position:0% anyway it sends light into the fiber and based<20:25:59.760> on<20:25:59.824> the<20:25:59.936> quality<20:26:00.176> of<20:26:00.360> the<20:26:00.424> reflected 20:26:00.886 --> 20:26:00.896 align:start position:0% based on the quality of the reflected 20:26:00.896 --> 20:26:03.230 align:start position:0% based on the quality of the reflected light<20:26:01.080> it<20:26:01.744> can<20:26:01.856> determine<20:26:02.280> the<20:26:02.400> following 20:26:03.230 --> 20:26:03.240 align:start position:0% light it can determine the following 20:26:03.240 --> 20:26:05.166 align:start position:0% light it can determine the following thought<20:26:03.720> location<20:26:04.080> length<20:26:04.744> of<20:26:04.856> the<20:26:05.040> cable 20:26:05.166 --> 20:26:05.176 align:start position:0% thought location length of the cable 20:26:05.176 --> 20:26:08.630 align:start position:0% thought location length of the cable loss<20:26:06.176> of<20:26:06.296> signal<20:26:06.656> if<20:26:07.144> applicable 20:26:08.630 --> 20:26:08.640 align:start position:0% loss of signal if applicable 20:26:08.640 --> 20:26:11.630 align:start position:0% loss of signal if applicable a<20:26:09.240> cable<20:26:09.536> certifier<20:26:10.256> it's<20:26:10.800> used<20:26:10.976> to<20:26:11.216> carry<20:26:11.512> out 20:26:11.630 --> 20:26:11.640 align:start position:0% a cable certifier it's used to carry out 20:26:11.640 --> 20:26:13.134 align:start position:0% a cable certifier it's used to carry out tests<20:26:12.056> it<20:26:12.296> can<20:26:12.424> test<20:26:12.600> the<20:26:12.784> following 20:26:13.134 --> 20:26:13.144 align:start position:0% tests it can test the following 20:26:13.144 --> 20:26:15.430 align:start position:0% tests it can test the following conductors<20:26:14.104> in<20:26:14.336> the<20:26:14.464> ethernet<20:26:14.760> cable 20:26:15.430 --> 20:26:15.440 align:start position:0% conductors in the ethernet cable 20:26:15.440 --> 20:26:18.470 align:start position:0% conductors in the ethernet cable continuity<20:26:16.440> in<20:26:16.680> the<20:26:16.856> wires<20:26:17.280> proper<20:26:18.120> pairing 20:26:18.470 --> 20:26:18.480 align:start position:0% continuity in the wires proper pairing 20:26:18.480 --> 20:26:19.966 align:start position:0% continuity in the wires proper pairing of<20:26:18.600> the<20:26:18.784> wires<20:26:19.080> as<20:26:19.192> well<20:26:19.376> it's<20:26:19.552> quite<20:26:19.680> handy 20:26:19.966 --> 20:26:19.976 align:start position:0% of the wires as well it's quite handy 20:26:19.976 --> 20:26:21.350 align:start position:0% of the wires as well it's quite handy you<20:26:20.104> just<20:26:20.216> plug<20:26:20.400> it<20:26:20.640> in 20:26:21.350 --> 20:26:21.360 align:start position:0% you just plug it in 20:26:21.360 --> 20:26:22.734 align:start position:0% you just plug it in and<20:26:21.656> it<20:26:21.832> will<20:26:21.960> give<20:26:22.144> you<20:26:22.256> lots<20:26:22.552> of<20:26:22.616> different 20:26:22.734 --> 20:26:22.744 align:start position:0% and it will give you lots of different 20:26:22.744 --> 20:26:24.470 align:start position:0% and it will give you lots of different reading<20:26:23.160> depending<20:26:23.576> on<20:26:23.640> the<20:26:23.872> model<20:26:24.056> you<20:26:24.296> have 20:26:24.470 --> 20:26:24.480 align:start position:0% reading depending on the model you have 20:26:24.480 --> 20:26:26.206 align:start position:0% reading depending on the model you have and<20:26:24.600> how<20:26:24.784> much<20:26:24.896> you've<20:26:25.192> spent 20:26:26.206 --> 20:26:26.216 align:start position:0% and how much you've spent 20:26:26.216 --> 20:26:29.630 align:start position:0% and how much you've spent proper<20:26:26.760> termination<20:26:27.240> of<20:26:27.536> cat<20:26:27.720> cables 20:26:29.630 --> 20:26:29.640 align:start position:0% proper termination of cat cables 20:26:29.640 --> 20:26:32.030 align:start position:0% proper termination of cat cables so<20:26:30.000> they're<20:26:30.120> covered<20:26:30.720> in<20:26:30.832> the<20:26:31.080> syllabus<20:26:31.800> which 20:26:32.030 --> 20:26:32.040 align:start position:0% so they're covered in the syllabus which 20:26:32.040 --> 20:26:34.542 align:start position:0% so they're covered in the syllabus which is<20:26:32.104> why<20:26:32.336> I<20:26:32.512> give<20:26:32.696> them<20:26:32.872> specific<20:26:33.480> slide<20:26:34.376> each 20:26:34.542 --> 20:26:34.552 align:start position:0% is why I give them specific slide each 20:26:34.552 --> 20:26:36.286 align:start position:0% is why I give them specific slide each instead<20:26:34.976> of<20:26:35.104> just<20:26:35.216> mentioning<20:26:35.576> them<20:26:35.760> in 20:26:36.286 --> 20:26:36.296 align:start position:0% instead of just mentioning them in 20:26:36.296 --> 20:26:38.270 align:start position:0% instead of just mentioning them in passing<20:26:36.600> as<20:26:36.784> we<20:26:36.896> may<20:26:37.016> have<20:26:37.144> done<20:26:37.320> elsewhere<20:26:37.680> so 20:26:38.270 --> 20:26:38.280 align:start position:0% passing as we may have done elsewhere so 20:26:38.280 --> 20:26:40.182 align:start position:0% passing as we may have done elsewhere so the<20:26:38.400> cable<20:26:38.512> crimp<20:26:39.056> are<20:26:39.240> the<20:26:39.360> punch<20:26:39.600> down<20:26:39.832> Tool 20:26:40.182 --> 20:26:40.192 align:start position:0% the cable crimp are the punch down Tool 20:26:40.192 --> 20:26:43.310 align:start position:0% the cable crimp are the punch down Tool The<20:26:40.376> Wire<20:26:40.552> Strippers<20:26:41.464> otdr<20:26:42.000> cable<20:26:42.656> certifier 20:26:43.310 --> 20:26:43.320 align:start position:0% The Wire Strippers otdr cable certifier 20:26:43.320 --> 20:26:45.414 align:start position:0% The Wire Strippers otdr cable certifier all<20:26:44.160> right<20:26:44.336> so<20:26:44.512> that's<20:26:44.696> all<20:26:44.872> thanks<20:26:45.240> for 20:26:45.414 --> 20:26:45.424 align:start position:0% all right so that's all thanks for 20:26:45.424 --> 20:26:49.570 align:start position:0% all right so that's all thanks for watching 20:26:49.570 --> 20:26:49.580 align:start position:0% 20:26:49.580 --> 20:26:58.814 align:start position:0% [Music] 20:26:58.814 --> 20:26:58.824 align:start position:0% [Music] 20:26:58.824 --> 20:27:05.950 align:start position:0% [Music] thank<20:26:59.824> you 20:27:05.950 --> 20:27:05.960 align:start position:0% 20:27:05.960 --> 20:27:09.606 align:start position:0% welcome<20:27:06.960> to<20:27:07.192> module<20:27:07.680> 15<20:27:08.160> a<20:27:08.576> lesson<20:27:08.936> 1B 20:27:09.606 --> 20:27:09.616 align:start position:0% welcome to module 15 a lesson 1B 20:27:09.616 --> 20:27:13.542 align:start position:0% welcome to module 15 a lesson 1B software<20:27:10.616> testing<20:27:11.280> tools 20:27:13.542 --> 20:27:13.552 align:start position:0% software testing tools 20:27:13.552 --> 20:27:15.046 align:start position:0% software testing tools I'm<20:27:13.856> not<20:27:14.040> going<20:27:14.160> to<20:27:14.160> cover<20:27:14.336> stuff<20:27:14.696> that<20:27:14.872> has 20:27:15.046 --> 20:27:15.056 align:start position:0% I'm not going to cover stuff that has 20:27:15.056 --> 20:27:16.430 align:start position:0% I'm not going to cover stuff that has already<20:27:15.240> been<20:27:15.424> covered<20:27:15.720> unless<20:27:16.080> there's<20:27:16.192> a 20:27:16.430 --> 20:27:16.440 align:start position:0% already been covered unless there's a 20:27:16.440 --> 20:27:17.630 align:start position:0% already been covered unless there's a new<20:27:16.616> point 20:27:17.630 --> 20:27:17.640 align:start position:0% new point 20:27:17.640 --> 20:27:19.910 align:start position:0% new point or<20:27:18.120> some<20:27:18.296> of<20:27:18.424> the<20:27:18.536> reason<20:27:18.656> for<20:27:18.896> doing<20:27:19.080> it 20:27:19.910 --> 20:27:19.920 align:start position:0% or some of the reason for doing it 20:27:19.920 --> 20:27:21.822 align:start position:0% or some of the reason for doing it uh<20:27:20.400> packet<20:27:20.760> sniffers 20:27:21.822 --> 20:27:21.832 align:start position:0% uh packet sniffers 20:27:21.832 --> 20:27:25.814 align:start position:0% uh packet sniffers Wi-Fi<20:27:22.496> analyzer<20:27:23.280> bandwidth<20:27:24.176> speed<20:27:24.296> tester 20:27:25.814 --> 20:27:25.824 align:start position:0% Wi-Fi analyzer bandwidth speed tester 20:27:25.824 --> 20:27:30.230 align:start position:0% Wi-Fi analyzer bandwidth speed tester CLI<20:27:26.824> tools<20:27:27.176> command<20:27:27.600> line<20:27:28.040> tools<20:27:29.040> uh<20:27:29.696> not 20:27:30.230 --> 20:27:30.240 align:start position:0% CLI tools command line tools uh not 20:27:30.240 --> 20:27:32.094 align:start position:0% CLI tools command line tools uh not already<20:27:30.424> covered<20:27:30.896> because<20:27:31.552> of<20:27:31.744> the<20:27:31.856> way<20:27:31.976> the 20:27:32.094 --> 20:27:32.104 align:start position:0% already covered because of the way the 20:27:32.104 --> 20:27:33.590 align:start position:0% already covered because of the way the syllabus<20:27:32.464> is<20:27:32.576> set<20:27:32.760> out<20:27:32.936> we<20:27:33.120> have<20:27:33.296> to<20:27:33.424> cover 20:27:33.590 --> 20:27:33.600 align:start position:0% syllabus is set out we have to cover 20:27:33.600 --> 20:27:35.566 align:start position:0% syllabus is set out we have to cover some<20:27:33.832> stuff<20:27:34.080> earlier<20:27:34.496> in<20:27:34.744> later<20:27:34.976> and<20:27:35.280> in<20:27:35.464> the 20:27:35.566 --> 20:27:35.576 align:start position:0% some stuff earlier in later and in the 20:27:35.576 --> 20:27:37.542 align:start position:0% some stuff earlier in later and in the middle<20:27:35.760> because<20:27:36.656> it's<20:27:36.832> relevant<20:27:37.256> to<20:27:37.376> that 20:27:37.542 --> 20:27:37.552 align:start position:0% middle because it's relevant to that 20:27:37.552 --> 20:27:39.670 align:start position:0% middle because it's relevant to that particular<20:27:37.920> subject<20:27:38.336> for<20:27:38.640> example<20:27:38.872> security 20:27:39.670 --> 20:27:39.680 align:start position:0% particular subject for example security 20:27:39.680 --> 20:27:43.006 align:start position:0% particular subject for example security or<20:27:40.680> troubleshooting 20:27:43.006 --> 20:27:43.016 align:start position:0% or troubleshooting 20:27:43.016 --> 20:27:46.542 align:start position:0% or troubleshooting I<20:27:43.504> put<20:27:43.680> an<20:27:43.856> image<20:27:44.104> here<20:27:44.400> for<20:27:44.872> Wireshark 20:27:46.542 --> 20:27:46.552 align:start position:0% I put an image here for Wireshark 20:27:46.552 --> 20:27:51.950 align:start position:0% I put an image here for Wireshark um<20:27:46.616> Wireshark<20:27:47.512> I'm<20:27:48.056> going<20:27:48.240> to<20:27:48.424> say<20:27:48.600> a<20:27:49.552> must<20:27:50.160> no 20:27:51.950 --> 20:27:51.960 align:start position:0% um Wireshark I'm going to say a must no 20:27:51.960 --> 20:27:55.734 align:start position:0% um Wireshark I'm going to say a must no missed 20:27:55.734 --> 20:27:55.744 align:start position:0% 20:27:55.744 --> 20:27:58.310 align:start position:0% now<20:27:56.336> you<20:27:56.512> must<20:27:56.640> know<20:27:56.824> sniffing<20:27:57.424> and<20:27:58.016> uh 20:27:58.310 --> 20:27:58.320 align:start position:0% now you must know sniffing and uh 20:27:58.320 --> 20:28:00.286 align:start position:0% now you must know sniffing and uh Wireshark<20:27:58.920> is<20:27:59.160> just<20:27:59.336> the<20:27:59.464> industry<20:27:59.760> leader 20:28:00.286 --> 20:28:00.296 align:start position:0% Wireshark is just the industry leader 20:28:00.296 --> 20:28:03.110 align:start position:0% Wireshark is just the industry leader and<20:28:01.144> the<20:28:01.320> good<20:28:01.504> news<20:28:01.680> is<20:28:01.920> it's<20:28:02.640> free<20:28:02.872> to 20:28:03.110 --> 20:28:03.120 align:start position:0% and the good news is it's free to 20:28:03.120 --> 20:28:05.390 align:start position:0% and the good news is it's free to download<20:28:03.296> you<20:28:04.192> could<20:28:04.320> have<20:28:04.552> a<20:28:04.800> virtual 20:28:05.390 --> 20:28:05.400 align:start position:0% download you could have a virtual 20:28:05.400 --> 20:28:09.230 align:start position:0% download you could have a virtual Network<20:28:05.696> on<20:28:06.656> my<20:28:06.832> Cisco<20:28:07.504> virtual<20:28:08.040> rack<20:28:08.400> which 20:28:09.230 --> 20:28:09.240 align:start position:0% Network on my Cisco virtual rack which 20:28:09.240 --> 20:28:12.166 align:start position:0% Network on my Cisco virtual rack which is<20:28:09.296> free<20:28:09.536> on<20:28:09.784> howturnetwork.com<20:28:11.000> it<20:28:12.000> actually 20:28:12.166 --> 20:28:12.176 align:start position:0% is free on howturnetwork.com it actually 20:28:12.176 --> 20:28:13.910 align:start position:0% is free on howturnetwork.com it actually you<20:28:12.480> booted<20:28:12.896> up<20:28:13.016> you've<20:28:13.440> got<20:28:13.552> to<20:28:13.680> find<20:28:13.744> your 20:28:13.910 --> 20:28:13.920 align:start position:0% you booted up you've got to find your 20:28:13.920 --> 20:28:16.134 align:start position:0% you booted up you've got to find your own<20:28:14.040> Cisco<20:28:14.464> image<20:28:14.872> because<20:28:15.296> Cisco<20:28:15.784> don't<20:28:15.960> give 20:28:16.134 --> 20:28:16.144 align:start position:0% own Cisco image because Cisco don't give 20:28:16.144 --> 20:28:18.414 align:start position:0% own Cisco image because Cisco don't give them<20:28:16.256> away<20:28:16.440> but<20:28:17.040> I<20:28:17.216> wonder<20:28:17.400> why<20:28:17.824> sharks<20:28:18.240> you 20:28:18.414 --> 20:28:18.424 align:start position:0% them away but I wonder why sharks you 20:28:18.424 --> 20:28:20.862 align:start position:0% them away but I wonder why sharks you can<20:28:18.536> actually<20:28:18.656> see<20:28:19.080> traffic<20:28:19.744> live<20:28:20.280> passing 20:28:20.862 --> 20:28:20.872 align:start position:0% can actually see traffic live passing 20:28:20.872 --> 20:28:23.414 align:start position:0% can actually see traffic live passing between<20:28:21.000> your<20:28:21.360> routers<20:28:21.856> and<20:28:22.856> other<20:28:23.040> devices 20:28:23.414 --> 20:28:23.424 align:start position:0% between your routers and other devices 20:28:23.424 --> 20:28:26.454 align:start position:0% between your routers and other devices this<20:28:24.424> is<20:28:24.536> an<20:28:24.720> essential<20:28:25.080> tool<20:28:25.552> and<20:28:26.160> you<20:28:26.280> need 20:28:26.454 --> 20:28:26.464 align:start position:0% this is an essential tool and you need 20:28:26.464 --> 20:28:30.134 align:start position:0% this is an essential tool and you need to<20:28:26.640> understand<20:28:26.760> it<20:28:27.176> for<20:28:27.424> troubleshooting 20:28:30.134 --> 20:28:30.144 align:start position:0% to understand it for troubleshooting 20:28:30.144 --> 20:28:33.286 align:start position:0% to understand it for troubleshooting so<20:28:31.144> uh<20:28:31.504> really<20:28:31.800> important<20:28:32.280> you<20:28:32.872> can<20:28:33.000> see<20:28:33.056> all 20:28:33.286 --> 20:28:33.296 align:start position:0% so uh really important you can see all 20:28:33.296 --> 20:28:35.686 align:start position:0% so uh really important you can see all your<20:28:33.616> protocols<20:28:34.616> and<20:28:34.800> packets<20:28:35.216> and<20:28:35.400> all<20:28:35.576> that 20:28:35.686 --> 20:28:35.696 align:start position:0% your protocols and packets and all that 20:28:35.696 --> 20:28:37.734 align:start position:0% your protocols and packets and all that kind<20:28:35.872> of<20:28:36.000> stuff<20:28:36.240> so 20:28:37.734 --> 20:28:37.744 align:start position:0% kind of stuff so 20:28:37.744 --> 20:28:40.310 align:start position:0% kind of stuff so um<20:28:37.800> you'd<20:28:38.336> you'd<20:28:38.824> normally<20:28:39.056> load<20:28:39.536> this<20:28:39.832> uh 20:28:40.310 --> 20:28:40.320 align:start position:0% um you'd you'd normally load this uh 20:28:40.320 --> 20:28:41.862 align:start position:0% um you'd you'd normally load this uh software 20:28:41.862 --> 20:28:41.872 align:start position:0% software 20:28:41.872 --> 20:28:44.094 align:start position:0% software all<20:28:42.296> right<20:28:42.360> the<20:28:42.656> Wireshark<20:28:43.080> it'd<20:28:43.744> be<20:28:43.800> loaded 20:28:44.094 --> 20:28:44.104 align:start position:0% all right the Wireshark it'd be loaded 20:28:44.104 --> 20:28:45.950 align:start position:0% all right the Wireshark it'd be loaded onto<20:28:44.400> your<20:28:44.640> laptop<20:28:45.000> if<20:28:45.784> you're 20:28:45.950 --> 20:28:45.960 align:start position:0% onto your laptop if you're 20:28:45.960 --> 20:28:47.390 align:start position:0% onto your laptop if you're troubleshooting<20:28:46.680> you<20:28:46.920> would<20:28:47.040> leave<20:28:47.160> it 20:28:47.390 --> 20:28:47.400 align:start position:0% troubleshooting you would leave it 20:28:47.400 --> 20:28:49.910 align:start position:0% troubleshooting you would leave it running<20:28:47.784> say<20:28:48.784> for<20:28:49.016> example<20:28:49.256> you'd<20:28:49.616> leave<20:28:49.744> it 20:28:49.910 --> 20:28:49.920 align:start position:0% running say for example you'd leave it 20:28:49.920 --> 20:28:51.822 align:start position:0% running say for example you'd leave it running<20:28:50.040> for<20:28:50.400> an<20:28:50.512> hour 20:28:51.822 --> 20:28:51.832 align:start position:0% running for an hour 20:28:51.832 --> 20:28:54.166 align:start position:0% running for an hour and<20:28:52.376> and<20:28:52.552> then<20:28:52.800> you<20:28:52.976> could<20:28:53.104> analyze<20:28:53.760> the 20:28:54.166 --> 20:28:54.176 align:start position:0% and and then you could analyze the 20:28:54.176 --> 20:28:55.542 align:start position:0% and and then you could analyze the output 20:28:55.542 --> 20:28:55.552 align:start position:0% output 20:28:55.552 --> 20:28:57.590 align:start position:0% output and<20:28:56.104> see<20:28:56.400> where<20:28:56.576> a<20:28:56.760> particular<20:28:57.000> problems 20:28:57.590 --> 20:28:57.600 align:start position:0% and see where a particular problems 20:28:57.600 --> 20:29:00.286 align:start position:0% and see where a particular problems happening<20:28:58.192> is<20:28:58.800> it<20:28:58.920> is<20:28:59.160> it<20:28:59.336> happening<20:28:59.696> for<20:29:00.056> the 20:29:00.286 --> 20:29:00.296 align:start position:0% happening is it is it happening for the 20:29:00.296 --> 20:29:03.166 align:start position:0% happening is it is it happening for the the<20:29:00.480> whole<20:29:00.784> hour<20:29:01.016> is<20:29:01.680> there<20:29:01.920> some<20:29:02.216> sort<20:29:02.464> of 20:29:03.166 --> 20:29:03.176 align:start position:0% the whole hour is there some sort of 20:29:03.176 --> 20:29:04.006 align:start position:0% the whole hour is there some sort of um 20:29:04.006 --> 20:29:04.016 align:start position:0% um 20:29:04.016 --> 20:29:07.606 align:start position:0% um issue<20:29:04.976> spikes<20:29:05.696> and<20:29:06.480> then<20:29:06.656> or<20:29:06.960> does<20:29:07.192> the<20:29:07.376> issue 20:29:07.606 --> 20:29:07.616 align:start position:0% issue spikes and then or does the issue 20:29:07.616 --> 20:29:09.470 align:start position:0% issue spikes and then or does the issue sort<20:29:07.856> of<20:29:07.920> happen<20:29:08.280> over<20:29:08.576> this<20:29:08.824> period<20:29:09.176> of<20:29:09.360> time 20:29:09.470 --> 20:29:09.480 align:start position:0% sort of happen over this period of time 20:29:09.480 --> 20:29:12.526 align:start position:0% sort of happen over this period of time that<20:29:09.784> kind<20:29:09.960> of<20:29:10.080> thing<20:29:10.336> so<20:29:11.336> the<20:29:11.936> traffic<20:29:12.176> is 20:29:12.526 --> 20:29:12.536 align:start position:0% that kind of thing so the traffic is 20:29:12.536 --> 20:29:14.326 align:start position:0% that kind of thing so the traffic is going<20:29:12.720> into<20:29:12.960> your<20:29:13.144> switch<20:29:13.320> from<20:29:13.744> the<20:29:13.920> server 20:29:14.326 --> 20:29:14.336 align:start position:0% going into your switch from the server 20:29:14.336 --> 20:29:17.094 align:start position:0% going into your switch from the server and<20:29:15.056> you<20:29:15.240> will<20:29:15.360> configure 20:29:17.094 --> 20:29:17.104 align:start position:0% and you will configure 20:29:17.104 --> 20:29:18.822 align:start position:0% and you will configure um the<20:29:17.696> switch<20:29:17.936> over<20:29:18.176> here<20:29:18.424> you<20:29:18.536> would<20:29:18.656> do<20:29:18.784> a 20:29:18.822 --> 20:29:18.832 align:start position:0% um the switch over here you would do a 20:29:18.832 --> 20:29:20.814 align:start position:0% um the switch over here you would do a configuration<20:29:19.256> command<20:29:19.680> on<20:29:19.856> the<20:29:19.976> switch<20:29:20.160> to 20:29:20.814 --> 20:29:20.824 align:start position:0% configuration command on the switch to 20:29:20.824 --> 20:29:23.206 align:start position:0% configuration command on the switch to send<20:29:21.000> the<20:29:21.240> traffic<20:29:21.424> out<20:29:22.256> on<20:29:22.440> whichever<20:29:22.976> Port 20:29:23.206 --> 20:29:23.216 align:start position:0% send the traffic out on whichever Port 20:29:23.216 --> 20:29:26.030 align:start position:0% send the traffic out on whichever Port you've<20:29:23.464> connected<20:29:23.760> your<20:29:24.000> laptop<20:29:24.360> to 20:29:26.030 --> 20:29:26.040 align:start position:0% you've connected your laptop to 20:29:26.040 --> 20:29:28.734 align:start position:0% you've connected your laptop to um you've<20:29:26.464> just<20:29:26.576> got<20:29:26.760> to<20:29:27.000> be<20:29:27.296> aware<20:29:27.536> of<20:29:27.832> I'm 20:29:28.734 --> 20:29:28.744 align:start position:0% um you've just got to be aware of I'm 20:29:28.744 --> 20:29:30.166 align:start position:0% um you've just got to be aware of I'm just<20:29:28.920> telling<20:29:29.160> you<20:29:29.216> this<20:29:29.400> because<20:29:29.576> of<20:29:29.760> the 20:29:30.166 --> 20:29:30.176 align:start position:0% just telling you this because of the 20:29:30.176 --> 20:29:32.390 align:start position:0% just telling you this because of the real<20:29:30.360> world<20:29:30.600> you've<20:29:31.192> got<20:29:31.256> to<20:29:31.376> be<20:29:31.504> aware<20:29:31.616> of<20:29:31.856> CPU 20:29:32.390 --> 20:29:32.400 align:start position:0% real world you've got to be aware of CPU 20:29:32.400 --> 20:29:33.886 align:start position:0% real world you've got to be aware of CPU and<20:29:32.696> you've<20:29:32.824> got<20:29:32.872> to<20:29:33.000> make<20:29:33.120> sure<20:29:33.296> that<20:29:33.536> you<20:29:33.720> get 20:29:33.886 --> 20:29:33.896 align:start position:0% and you've got to make sure that you get 20:29:33.896 --> 20:29:36.470 align:start position:0% and you've got to make sure that you get permission<20:29:34.256> off<20:29:34.552> whoever<20:29:35.464> the 20:29:36.470 --> 20:29:36.480 align:start position:0% permission off whoever the 20:29:36.480 --> 20:29:39.166 align:start position:0% permission off whoever the um<20:29:36.536> person<20:29:36.832> in<20:29:37.144> charge<20:29:37.376> is<20:29:37.616> when<20:29:38.464> I've<20:29:38.936> worked 20:29:39.166 --> 20:29:39.176 align:start position:0% um person in charge is when I've worked 20:29:39.176 --> 20:29:40.846 align:start position:0% um person in charge is when I've worked on<20:29:39.240> network<20:29:39.360> teams<20:29:40.016> and 20:29:40.846 --> 20:29:40.856 align:start position:0% on network teams and 20:29:40.856 --> 20:29:43.006 align:start position:0% on network teams and um<20:29:40.976> I<20:29:41.760> knew<20:29:41.936> the<20:29:42.056> procedures<20:29:42.424> and<20:29:42.600> policies 20:29:43.006 --> 20:29:43.016 align:start position:0% um I knew the procedures and policies 20:29:43.016 --> 20:29:45.166 align:start position:0% um I knew the procedures and policies which<20:29:43.256> we've<20:29:43.440> already<20:29:43.616> talked<20:29:43.920> about<20:29:44.000> what<20:29:45.000> I 20:29:45.166 --> 20:29:45.176 align:start position:0% which we've already talked about what I 20:29:45.176 --> 20:29:47.454 align:start position:0% which we've already talked about what I can<20:29:45.360> and<20:29:45.536> can't<20:29:45.720> do<20:29:46.016> but<20:29:46.976> if<20:29:47.104> it<20:29:47.216> could<20:29:47.336> be 20:29:47.454 --> 20:29:47.464 align:start position:0% can and can't do but if it could be 20:29:47.464 --> 20:29:50.454 align:start position:0% can and can't do but if it could be Network<20:29:47.696> effect<20:29:48.056> in<20:29:48.424> for<20:29:48.720> example<20:29:48.960> the<20:29:49.192> CPU 20:29:50.454 --> 20:29:50.464 align:start position:0% Network effect in for example the CPU 20:29:50.464 --> 20:29:53.686 align:start position:0% Network effect in for example the CPU then<20:29:51.424> you've<20:29:52.080> got<20:29:52.192> to<20:29:52.440> make<20:29:52.856> sure<20:29:53.040> it<20:29:53.336> is<20:29:53.464> done 20:29:53.686 --> 20:29:53.696 align:start position:0% then you've got to make sure it is done 20:29:53.696 --> 20:29:56.862 align:start position:0% then you've got to make sure it is done out<20:29:53.872> of<20:29:54.000> hours<20:29:54.176> or<20:29:54.480> you've<20:29:54.656> got<20:29:54.720> permission 20:29:56.862 --> 20:29:56.872 align:start position:0% out of hours or you've got permission 20:29:56.872 --> 20:29:58.790 align:start position:0% out of hours or you've got permission so<20:29:57.240> you'll<20:29:57.424> check<20:29:57.600> for<20:29:57.784> traffic<20:29:57.960> patterns<20:29:58.496> of 20:29:58.790 --> 20:29:58.800 align:start position:0% so you'll check for traffic patterns of 20:29:58.800 --> 20:30:00.286 align:start position:0% so you'll check for traffic patterns of Base<20:29:58.976> a<20:29:59.216> traffic<20:29:59.464> Baseline<20:30:00.000> any 20:30:00.286 --> 20:30:00.296 align:start position:0% Base a traffic Baseline any 20:30:00.296 --> 20:30:03.110 align:start position:0% Base a traffic Baseline any irregularities<20:30:01.016> they<20:30:01.320> will<20:30:01.504> pop<20:30:01.680> up 20:30:03.110 --> 20:30:03.120 align:start position:0% irregularities they will pop up 20:30:03.120 --> 20:30:05.750 align:start position:0% irregularities they will pop up you'll<20:30:03.784> be<20:30:03.896> mirroring<20:30:04.376> a<20:30:04.744> port 20:30:05.750 --> 20:30:05.760 align:start position:0% you'll be mirroring a port 20:30:05.760 --> 20:30:07.790 align:start position:0% you'll be mirroring a port just<20:30:06.424> be<20:30:06.536> aware<20:30:06.656> the<20:30:06.896> package<20:30:07.192> slippers<20:30:07.616> can 20:30:07.790 --> 20:30:07.800 align:start position:0% just be aware the package slippers can 20:30:07.800 --> 20:30:09.950 align:start position:0% just be aware the package slippers can be<20:30:07.920> used<20:30:08.104> for<20:30:08.464> good<20:30:08.696> and<20:30:08.872> bad<20:30:09.056> so<20:30:09.360> they<20:30:09.536> cannot 20:30:09.950 --> 20:30:09.960 align:start position:0% be used for good and bad so they cannot 20:30:09.960 --> 20:30:12.350 align:start position:0% be used for good and bad so they cannot also<20:30:10.256> be<20:30:10.496> used<20:30:10.744> by<20:30:11.104> hackers<20:30:11.576> so<20:30:12.056> whenever 20:30:12.350 --> 20:30:12.360 align:start position:0% also be used by hackers so whenever 20:30:12.360 --> 20:30:13.734 align:start position:0% also be used by hackers so whenever possible<20:30:12.720> if<20:30:12.896> you're<20:30:13.016> connecting<20:30:13.320> over<20:30:13.504> the 20:30:13.734 --> 20:30:13.744 align:start position:0% possible if you're connecting over the 20:30:13.744 --> 20:30:17.710 align:start position:0% possible if you're connecting over the network<20:30:13.856> use<20:30:14.824> a<20:30:15.056> secure<20:30:15.360> shell<20:30:15.800> this<20:30:16.800> is<20:30:17.040> a 20:30:17.710 --> 20:30:17.720 align:start position:0% network use a secure shell this is a 20:30:17.720 --> 20:30:20.390 align:start position:0% network use a secure shell this is a Wireshark<20:30:18.720> we<20:30:19.192> and<20:30:19.552> they<20:30:19.744> call<20:30:19.856> it<20:30:19.976> captures 20:30:20.390 --> 20:30:20.400 align:start position:0% Wireshark we and they call it captures 20:30:20.400 --> 20:30:22.542 align:start position:0% Wireshark we and they call it captures as<20:30:20.576> well<20:30:20.696> it's<20:30:20.872> handy<20:30:21.240> to<20:30:21.360> know<20:30:21.600> the<20:30:22.144> uh<20:30:22.256> the 20:30:22.542 --> 20:30:22.552 align:start position:0% as well it's handy to know the uh the 20:30:22.552 --> 20:30:23.990 align:start position:0% as well it's handy to know the uh the vernaculars 20:30:23.990 --> 20:30:24.000 align:start position:0% vernaculars 20:30:24.000 --> 20:30:26.566 align:start position:0% vernaculars um<20:30:24.056> ethernet<20:30:24.536> zero<20:30:24.960> looks<20:30:25.320> like<20:30:25.440> the<20:30:25.616> port 20:30:26.566 --> 20:30:26.576 align:start position:0% um ethernet zero looks like the port 20:30:26.576 --> 20:30:28.966 align:start position:0% um ethernet zero looks like the port uh<20:30:27.296> you'll<20:30:27.656> you'll<20:30:28.016> this<20:30:28.192> is<20:30:28.320> the<20:30:28.552> dashboard 20:30:28.966 --> 20:30:28.976 align:start position:0% uh you'll you'll this is the dashboard 20:30:28.976 --> 20:30:30.710 align:start position:0% uh you'll you'll this is the dashboard all<20:30:29.336> around<20:30:29.512> here 20:30:30.710 --> 20:30:30.720 align:start position:0% all around here 20:30:30.720 --> 20:30:32.326 align:start position:0% all around here and<20:30:31.144> in<20:30:31.320> this<20:30:31.504> part<20:30:31.616> here<20:30:31.800> you<20:30:32.104> can<20:30:32.160> actually 20:30:32.326 --> 20:30:32.336 align:start position:0% and in this part here you can actually 20:30:32.336 --> 20:30:35.390 align:start position:0% and in this part here you can actually click<20:30:32.824> on<20:30:33.000> these<20:30:33.424> uh<20:30:34.192> little<20:30:34.376> arrows<20:30:34.856> and<20:30:35.280> it 20:30:35.390 --> 20:30:35.400 align:start position:0% click on these uh little arrows and it 20:30:35.400 --> 20:30:38.270 align:start position:0% click on these uh little arrows and it will<20:30:35.576> expand<20:30:36.000> so<20:30:36.960> you'll<20:30:37.192> see<20:30:37.440> the<20:30:37.856> layer<20:30:38.160> one 20:30:38.270 --> 20:30:38.280 align:start position:0% will expand so you'll see the layer one 20:30:38.280 --> 20:30:40.134 align:start position:0% will expand so you'll see the layer one which<20:30:38.824> probably<20:30:39.056> won't<20:30:39.240> be<20:30:39.360> of<20:30:39.656> interest<20:30:39.832> to 20:30:40.134 --> 20:30:40.144 align:start position:0% which probably won't be of interest to 20:30:40.144 --> 20:30:42.886 align:start position:0% which probably won't be of interest to you<20:30:40.320> then<20:30:41.104> layer<20:30:41.512> two<20:30:41.696> and<20:30:42.536> then<20:30:42.656> you<20:30:42.784> can 20:30:42.886 --> 20:30:42.896 align:start position:0% you then layer two and then you can 20:30:42.896 --> 20:30:45.110 align:start position:0% you then layer two and then you can click<20:30:43.080> on<20:30:43.192> this<20:30:43.376> and<20:30:43.616> you<20:30:43.800> will<20:30:43.920> see<20:30:44.216> that<20:30:44.872> it's 20:30:45.110 --> 20:30:45.120 align:start position:0% click on this and you will see that it's 20:30:45.120 --> 20:30:49.606 align:start position:0% click on this and you will see that it's an<20:30:45.720> ARP<20:30:46.144> packet<20:30:46.680> you<20:30:47.400> will<20:30:47.576> see<20:30:47.760> source 20:30:49.606 --> 20:30:49.616 align:start position:0% an ARP packet you will see source 20:30:49.616 --> 20:30:52.182 align:start position:0% an ARP packet you will see source uh<20:30:50.216> destination<20:30:50.824> all<20:30:51.296> and<20:30:51.600> all<20:30:51.784> this<20:30:51.896> kind<20:30:52.080> of 20:30:52.182 --> 20:30:52.192 align:start position:0% uh destination all and all this kind of 20:30:52.192 --> 20:30:54.470 align:start position:0% uh destination all and all this kind of stuff<20:30:52.376> and<20:30:52.856> then<20:30:52.976> down<20:30:53.160> here<20:30:53.512> is<20:30:54.056> all<20:30:54.296> your 20:30:54.470 --> 20:30:54.480 align:start position:0% stuff and then down here is all your 20:30:54.480 --> 20:30:57.470 align:start position:0% stuff and then down here is all your ones<20:30:54.832> and<20:30:54.960> zeros<20:30:55.440> and<20:30:56.160> hex<20:30:56.576> which<20:30:57.176> you 20:30:57.470 --> 20:30:57.480 align:start position:0% ones and zeros and hex which you 20:30:57.480 --> 20:30:59.270 align:start position:0% ones and zeros and hex which you probably<20:30:57.656> generally<20:30:58.440> won't<20:30:58.616> be<20:30:58.800> interested 20:30:59.270 --> 20:30:59.280 align:start position:0% probably generally won't be interested 20:30:59.280 --> 20:31:02.686 align:start position:0% probably generally won't be interested this<20:31:00.240> looks<20:31:00.536> like<20:31:00.656> it's<20:31:00.960> uh<20:31:01.256> some<20:31:01.552> sort<20:31:01.800> of<20:31:01.976> uh 20:31:02.686 --> 20:31:02.696 align:start position:0% this looks like it's uh some sort of uh 20:31:02.696 --> 20:31:04.734 align:start position:0% this looks like it's uh some sort of uh pattern<20:31:03.120> over<20:31:03.360> time<20:31:03.720> and<20:31:04.376> you<20:31:04.496> can<20:31:04.616> see 20:31:04.734 --> 20:31:04.744 align:start position:0% pattern over time and you can see 20:31:04.744 --> 20:31:08.686 align:start position:0% pattern over time and you can see there's<20:31:04.976> a<20:31:05.216> spike<20:31:05.512> here<20:31:05.824> that's<20:31:06.360> more<20:31:06.720> on<20:31:06.960> here 20:31:08.686 --> 20:31:08.696 align:start position:0% there's a spike here that's more on here 20:31:08.696 --> 20:31:10.910 align:start position:0% there's a spike here that's more on here and<20:31:09.240> here<20:31:09.480> you<20:31:09.720> can<20:31:09.832> decide<20:31:10.144> exactly<20:31:10.616> what 20:31:10.910 --> 20:31:10.920 align:start position:0% and here you can decide exactly what 20:31:10.920 --> 20:31:13.182 align:start position:0% and here you can decide exactly what traffic<20:31:11.160> you're<20:31:11.576> you're<20:31:11.824> monitoring<20:31:12.480> this<20:31:13.080> is 20:31:13.182 --> 20:31:13.192 align:start position:0% traffic you're you're monitoring this is 20:31:13.192 --> 20:31:16.606 align:start position:0% traffic you're you're monitoring this is SS<20:31:13.800> H<20:31:14.280> telnet<20:31:15.000> and<20:31:15.720> whatever<20:31:15.960> you<20:31:16.192> wanted<20:31:16.320> to 20:31:16.606 --> 20:31:16.616 align:start position:0% SS H telnet and whatever you wanted to 20:31:16.616 --> 20:31:18.950 align:start position:0% SS H telnet and whatever you wanted to Monitor<20:31:17.040> and<20:31:17.512> then<20:31:17.696> it's<20:31:17.872> a<20:31:18.176> in<20:31:18.480> a<20:31:18.600> pie<20:31:18.720> chart 20:31:18.950 --> 20:31:18.960 align:start position:0% Monitor and then it's a in a pie chart 20:31:18.960 --> 20:31:21.710 align:start position:0% Monitor and then it's a in a pie chart here<20:31:19.376> and<20:31:20.104> obviously<20:31:20.576> a<20:31:20.936> graph<20:31:21.240> form<20:31:21.480> here 20:31:21.710 --> 20:31:21.720 align:start position:0% here and obviously a graph form here 20:31:21.720 --> 20:31:24.526 align:start position:0% here and obviously a graph form here really<20:31:22.440> handy<20:31:22.856> so<20:31:23.040> you<20:31:23.280> can<20:31:23.336> go<20:31:23.760> to<20:31:24.360> your 20:31:24.526 --> 20:31:24.536 align:start position:0% really handy so you can go to your 20:31:24.536 --> 20:31:27.526 align:start position:0% really handy so you can go to your customer<20:31:24.784> or<20:31:25.744> your<20:31:25.856> boss<20:31:26.160> uh<20:31:26.936> with<20:31:27.120> all<20:31:27.296> of<20:31:27.424> the 20:31:27.526 --> 20:31:27.536 align:start position:0% customer or your boss uh with all of the 20:31:27.536 --> 20:31:30.590 align:start position:0% customer or your boss uh with all of the facts<20:31:27.896> and<20:31:28.080> say<20:31:28.320> when<20:31:28.976> this<20:31:29.280> happens<20:31:29.600> that 20:31:30.590 --> 20:31:30.600 align:start position:0% facts and say when this happens that 20:31:30.600 --> 20:31:33.822 align:start position:0% facts and say when this happens that happens<20:31:30.976> when<20:31:31.976> this<20:31:32.336> happens<20:31:32.576> such<20:31:33.480> and<20:31:33.656> such 20:31:33.822 --> 20:31:33.832 align:start position:0% happens when this happens such and such 20:31:33.832 --> 20:31:35.814 align:start position:0% happens when this happens such and such Doesn't<20:31:34.144> happen<20:31:34.440> and<20:31:34.920> you<20:31:35.104> can<20:31:35.160> prove<20:31:35.464> what<20:31:35.640> is 20:31:35.814 --> 20:31:35.824 align:start position:0% Doesn't happen and you can prove what is 20:31:35.824 --> 20:31:39.286 align:start position:0% Doesn't happen and you can prove what is or<20:31:36.056> isn't<20:31:36.424> the<20:31:36.960> issue<20:31:37.376> on<20:31:37.440> the<20:31:37.616> network<20:31:37.744> so<20:31:39.240> um 20:31:39.286 --> 20:31:39.296 align:start position:0% or isn't the issue on the network so um 20:31:39.296 --> 20:31:42.590 align:start position:0% or isn't the issue on the network so um please<20:31:39.960> do<20:31:40.440> check<20:31:41.040> out<20:31:41.280> the<20:31:41.824> Wireshark 20:31:42.590 --> 20:31:42.600 align:start position:0% please do check out the Wireshark 20:31:42.600 --> 20:31:45.526 align:start position:0% please do check out the Wireshark certified<20:31:43.192> network<20:31:44.104> analysis 20:31:45.526 --> 20:31:45.536 align:start position:0% certified network analysis 20:31:45.536 --> 20:31:46.686 align:start position:0% certified network analysis um 20:31:46.686 --> 20:31:46.696 align:start position:0% um 20:31:46.696 --> 20:31:49.150 align:start position:0% um the<20:31:47.696> network<20:31:47.872> associate<20:31:48.480> sorry 20:31:49.150 --> 20:31:49.160 align:start position:0% the network associate sorry 20:31:49.160 --> 20:31:51.886 align:start position:0% the network associate sorry qualifications<20:31:50.160> really<20:31:50.760> important<20:31:51.240> we've 20:31:51.886 --> 20:31:51.896 align:start position:0% qualifications really important we've 20:31:51.896 --> 20:31:56.326 align:start position:0% qualifications really important we've got<20:31:52.016> it<20:31:52.256> on<20:31:52.856> um<20:31:52.856> how<20:31:53.696> to<20:31:54.296> net 20:31:56.326 --> 20:31:56.336 align:start position:0% got it on um how to net 20:31:56.336 --> 20:31:59.814 align:start position:0% got it on um how to net work.com 20:31:59.814 --> 20:31:59.824 align:start position:0% 20:31:59.824 --> 20:32:01.734 align:start position:0% um<20:31:59.936> I<20:32:00.600> think<20:32:00.960> there's<20:32:01.080> maybe<20:32:01.320> other<20:32:01.552> people 20:32:01.734 --> 20:32:01.744 align:start position:0% um I think there's maybe other people 20:32:01.744 --> 20:32:03.710 align:start position:0% um I think there's maybe other people offered<20:32:02.216> the<20:32:02.280> course<20:32:02.400> but<20:32:02.760> most<20:32:03.176> people<20:32:03.424> just 20:32:03.710 --> 20:32:03.720 align:start position:0% offered the course but most people just 20:32:03.720 --> 20:32:06.046 align:start position:0% offered the course but most people just seem<20:32:04.080> to<20:32:04.144> just<20:32:04.376> Skip<20:32:04.552> by<20:32:04.800> but<20:32:05.104> this<20:32:05.640> this<20:32:05.824> will 20:32:06.046 --> 20:32:06.056 align:start position:0% seem to just Skip by but this this will 20:32:06.056 --> 20:32:07.846 align:start position:0% seem to just Skip by but this this will be<20:32:06.120> a<20:32:06.240> lifesaver<20:32:06.720> if<20:32:07.376> you're<20:32:07.504> looking<20:32:07.680> at 20:32:07.846 --> 20:32:07.856 align:start position:0% be a lifesaver if you're looking at 20:32:07.856 --> 20:32:10.246 align:start position:0% be a lifesaver if you're looking at being<20:32:08.104> a<20:32:08.336> network<20:32:08.576> engineer 20:32:10.246 --> 20:32:10.256 align:start position:0% being a network engineer 20:32:10.256 --> 20:32:13.734 align:start position:0% being a network engineer anyway<20:32:11.056> Wi-Fi<20:32:12.056> analyzer<20:32:12.896> this<20:32:13.144> is<20:32:13.320> obviously 20:32:13.734 --> 20:32:13.744 align:start position:0% anyway Wi-Fi analyzer this is obviously 20:32:13.744 --> 20:32:17.750 align:start position:0% anyway Wi-Fi analyzer this is obviously a<20:32:14.336> graphical 20:32:17.750 --> 20:32:17.760 align:start position:0% 20:32:17.760 --> 20:32:20.926 align:start position:0% output<20:32:18.656> that<20:32:19.016> has<20:32:19.256> been<20:32:19.504> discovered<20:32:19.976> with<20:32:20.696> the 20:32:20.926 --> 20:32:20.936 align:start position:0% output that has been discovered with the 20:32:20.936 --> 20:32:23.566 align:start position:0% output that has been discovered with the piece<20:32:21.360> of<20:32:21.424> software<20:32:21.784> it<20:32:22.616> reports<20:32:23.160> on<20:32:23.336> your 20:32:23.566 --> 20:32:23.576 align:start position:0% piece of software it reports on your 20:32:23.576 --> 20:32:26.390 align:start position:0% piece of software it reports on your SSID<20:32:24.176> which<20:32:24.784> you<20:32:24.960> can<20:32:25.080> see<20:32:25.256> here 20:32:26.390 --> 20:32:26.400 align:start position:0% SSID which you can see here 20:32:26.400 --> 20:32:28.966 align:start position:0% SSID which you can see here and<20:32:26.936> Mac<20:32:27.176> addresses<20:32:27.720> channels<20:32:28.320> use<20:32:28.552> you<20:32:28.800> can 20:32:28.966 --> 20:32:28.976 align:start position:0% and Mac addresses channels use you can 20:32:28.976 --> 20:32:31.494 align:start position:0% and Mac addresses channels use you can see<20:32:29.040> the<20:32:29.160> Mac<20:32:29.336> addresses<20:32:29.824> of<20:32:30.056> devices<20:32:30.424> here 20:32:31.494 --> 20:32:31.504 align:start position:0% see the Mac addresses of devices here 20:32:31.504 --> 20:32:34.006 align:start position:0% see the Mac addresses of devices here uh<20:32:32.040> challenge<20:32:32.336> use<20:32:32.760> speed<20:32:33.296> that<20:32:33.720> kind<20:32:33.896> of 20:32:34.006 --> 20:32:34.016 align:start position:0% uh challenge use speed that kind of 20:32:34.016 --> 20:32:35.206 align:start position:0% uh challenge use speed that kind of thing 20:32:35.206 --> 20:32:35.216 align:start position:0% thing 20:32:35.216 --> 20:32:37.182 align:start position:0% thing and<20:32:35.824> it<20:32:36.000> represents<20:32:36.480> the<20:32:36.600> output<20:32:36.896> in<20:32:37.080> the 20:32:37.182 --> 20:32:37.192 align:start position:0% and it represents the output in the 20:32:37.192 --> 20:32:39.414 align:start position:0% and it represents the output in the graphical<20:32:37.440> form<20:32:37.680> as<20:32:37.976> you<20:32:38.160> can<20:32:38.280> see<20:32:38.464> it<20:32:39.120> tells 20:32:39.414 --> 20:32:39.424 align:start position:0% graphical form as you can see it tells 20:32:39.424 --> 20:32:41.390 align:start position:0% graphical form as you can see it tells you<20:32:39.480> the<20:32:39.656> security<20:32:39.784> protocols<20:32:40.744> and<20:32:41.160> more 20:32:41.390 --> 20:32:41.400 align:start position:0% you the security protocols and more 20:32:41.400 --> 20:32:44.390 align:start position:0% you the security protocols and more importantly<20:32:41.824> lack<20:32:42.176> of<20:32:42.480> so<20:32:43.144> you<20:32:43.440> could<20:32:44.040> um<20:32:44.104> we 20:32:44.390 --> 20:32:44.400 align:start position:0% importantly lack of so you could um we 20:32:44.400 --> 20:32:46.070 align:start position:0% importantly lack of so you could um we talked<20:32:44.576> about<20:32:44.696> Rogue<20:32:45.240> access<20:32:45.424> points<20:32:45.960> and 20:32:46.070 --> 20:32:46.080 align:start position:0% talked about Rogue access points and 20:32:46.080 --> 20:32:48.230 align:start position:0% talked about Rogue access points and bring<20:32:46.192> your<20:32:46.376> own<20:32:46.552> device<20:32:46.744> earlier<20:32:47.280> you<20:32:48.120> could 20:32:48.230 --> 20:32:48.240 align:start position:0% bring your own device earlier you could 20:32:48.240 --> 20:32:50.094 align:start position:0% bring your own device earlier you could be<20:32:48.360> doing<20:32:48.536> this<20:32:48.784> in<20:32:48.960> work<20:32:49.192> or<20:32:49.552> you<20:32:49.744> could<20:32:49.856> do<20:32:49.976> it 20:32:50.094 --> 20:32:50.104 align:start position:0% be doing this in work or you could do it 20:32:50.104 --> 20:32:52.206 align:start position:0% be doing this in work or you could do it as<20:32:50.216> part<20:32:50.400> of<20:32:50.512> a<20:32:50.640> security<20:32:50.824> survey 20:32:52.206 --> 20:32:52.216 align:start position:0% as part of a security survey 20:32:52.216 --> 20:32:55.846 align:start position:0% as part of a security survey and<20:32:53.216> here's<20:32:53.576> another<20:32:53.760> image<20:32:54.720> from<20:32:55.256> the<20:32:55.552> same 20:32:55.846 --> 20:32:55.856 align:start position:0% and here's another image from the same 20:32:55.856 --> 20:32:59.454 align:start position:0% and here's another image from the same sort<20:32:56.040> of<20:32:56.104> piece<20:32:56.464> of<20:32:56.512> software 20:32:59.454 --> 20:32:59.464 align:start position:0% 20:32:59.464 --> 20:33:01.542 align:start position:0% all<20:33:00.000> right<20:33:00.176> bandwidth<20:33:00.784> speed<20:33:00.896> test<20:33:01.144> damage 20:33:01.542 --> 20:33:01.552 align:start position:0% all right bandwidth speed test damage 20:33:01.552 --> 20:33:03.526 align:start position:0% all right bandwidth speed test damage we've<20:33:01.856> all<20:33:02.040> used<20:33:02.216> these<20:33:02.576> because<20:33:02.824> if<20:33:03.120> we've 20:33:03.526 --> 20:33:03.536 align:start position:0% we've all used these because if we've 20:33:03.536 --> 20:33:05.862 align:start position:0% we've all used these because if we've got<20:33:03.720> problems<20:33:04.080> with<20:33:04.256> our<20:33:04.496> speed<20:33:04.920> at<20:33:05.280> home 20:33:05.862 --> 20:33:05.872 align:start position:0% got problems with our speed at home 20:33:05.872 --> 20:33:08.094 align:start position:0% got problems with our speed at home moving<20:33:06.240> at<20:33:06.424> work<20:33:06.600> maybe<20:33:06.832> known<20:33:07.552> as<20:33:07.680> throughput 20:33:08.094 --> 20:33:08.104 align:start position:0% moving at work maybe known as throughput 20:33:08.104 --> 20:33:10.310 align:start position:0% moving at work maybe known as throughput testers<20:33:08.576> they<20:33:09.296> can<20:33:09.424> be<20:33:09.600> Hardware<20:33:09.720> software 20:33:10.310 --> 20:33:10.320 align:start position:0% testers they can be Hardware software 20:33:10.320 --> 20:33:12.526 align:start position:0% testers they can be Hardware software based<20:33:10.800> it's<20:33:11.040> easier<20:33:11.400> for<20:33:11.696> us<20:33:11.824> obviously<20:33:12.240> to 20:33:12.526 --> 20:33:12.536 align:start position:0% based it's easier for us obviously to 20:33:12.536 --> 20:33:14.630 align:start position:0% based it's easier for us obviously to use<20:33:12.832> the<20:33:13.016> piece<20:33:13.256> of<20:33:13.376> software<20:33:13.744> which<20:33:14.400> will 20:33:14.630 --> 20:33:14.640 align:start position:0% use the piece of software which will 20:33:14.640 --> 20:33:16.670 align:start position:0% use the piece of software which will send<20:33:15.120> a<20:33:15.656> certain<20:33:15.720> amount<20:33:16.080> of<20:33:16.192> packets 20:33:16.670 --> 20:33:16.680 align:start position:0% send a certain amount of packets 20:33:16.680 --> 20:33:20.270 align:start position:0% send a certain amount of packets upstream<20:33:17.576> and<20:33:18.056> give<20:33:18.240> you<20:33:18.360> a<20:33:18.536> report<20:33:18.832> of<20:33:19.192> x 20:33:20.270 --> 20:33:20.280 align:start position:0% upstream and give you a report of x 20:33:20.280 --> 20:33:22.790 align:start position:0% upstream and give you a report of x megabits<20:33:21.120> per<20:33:21.296> second<20:33:21.480> then<20:33:21.896> the<20:33:22.144> downstream 20:33:22.790 --> 20:33:22.800 align:start position:0% megabits per second then the downstream 20:33:22.800 --> 20:33:25.134 align:start position:0% megabits per second then the downstream then<20:33:23.400> the<20:33:23.760> same<20:33:23.872> sort<20:33:24.056> of<20:33:24.176> value 20:33:25.134 --> 20:33:25.144 align:start position:0% then the same sort of value 20:33:25.144 --> 20:33:26.814 align:start position:0% then the same sort of value so<20:33:25.552> it<20:33:25.680> injects<20:33:26.104> traffic<20:33:26.216> into<20:33:26.464> the<20:33:26.696> network 20:33:26.814 --> 20:33:26.824 align:start position:0% so it injects traffic into the network 20:33:26.824 --> 20:33:28.790 align:start position:0% so it injects traffic into the network you<20:33:27.360> could<20:33:27.480> actually<20:33:27.600> use<20:33:27.832> this<20:33:28.080> on<20:33:28.256> your<20:33:28.496> Lan 20:33:28.790 --> 20:33:28.800 align:start position:0% you could actually use this on your Lan 20:33:28.800 --> 20:33:31.070 align:start position:0% you could actually use this on your Lan one<20:33:29.464> or<20:33:30.120> for<20:33:30.296> your<20:33:30.480> home<20:33:30.600> broadband 20:33:31.070 --> 20:33:31.080 align:start position:0% one or for your home broadband 20:33:31.080 --> 20:33:33.046 align:start position:0% one or for your home broadband connection<20:33:31.320> the<20:33:32.216> handy<20:33:32.576> thing<20:33:32.696> is<20:33:32.824> you'll 20:33:33.046 --> 20:33:33.056 align:start position:0% connection the handy thing is you'll 20:33:33.056 --> 20:33:35.750 align:start position:0% connection the handy thing is you'll normally<20:33:33.296> get<20:33:33.536> a<20:33:33.784> graph<20:33:34.192> saying<20:33:35.336> um<20:33:35.336> you<20:33:35.696> know 20:33:35.750 --> 20:33:35.760 align:start position:0% normally get a graph saying um you know 20:33:35.760 --> 20:33:38.566 align:start position:0% normally get a graph saying um you know how<20:33:35.936> fast<20:33:36.360> or<20:33:36.600> slow<20:33:36.784> it<20:33:37.080> is 20:33:38.566 --> 20:33:38.576 align:start position:0% how fast or slow it is 20:33:38.576 --> 20:33:41.110 align:start position:0% how fast or slow it is free<20:33:39.056> to<20:33:39.296> download<20:33:39.480> if<20:33:39.896> you<20:33:40.016> want<20:33:40.144> super<20:33:40.376> duper 20:33:41.110 --> 20:33:41.120 align:start position:0% free to download if you want super duper 20:33:41.120 --> 20:33:43.910 align:start position:0% free to download if you want super duper uh<20:33:42.120> outputs<20:33:42.960> and<20:33:43.144> charts<20:33:43.504> and<20:33:43.616> that<20:33:43.744> kind<20:33:43.856> of 20:33:43.910 --> 20:33:43.920 align:start position:0% uh outputs and charts and that kind of 20:33:43.920 --> 20:33:45.774 align:start position:0% uh outputs and charts and that kind of stuff<20:33:44.040> it'd<20:33:44.336> normally<20:33:44.576> be<20:33:44.824> paid 20:33:45.774 --> 20:33:45.784 align:start position:0% stuff it'd normally be paid 20:33:45.784 --> 20:33:48.110 align:start position:0% stuff it'd normally be paid CLI<20:33:46.616> this<20:33:46.976> is<20:33:47.040> where<20:33:47.280> the<20:33:47.400> rubber<20:33:47.696> meets<20:33:48.000> a 20:33:48.110 --> 20:33:48.120 align:start position:0% CLI this is where the rubber meets a 20:33:48.120 --> 20:33:50.814 align:start position:0% CLI this is where the rubber meets a road<20:33:48.296> and<20:33:48.656> most<20:33:48.960> Network<20:33:49.192> Engineers<20:33:49.920> kind<20:33:50.640> of 20:33:50.814 --> 20:33:50.824 align:start position:0% road and most Network Engineers kind of 20:33:50.824 --> 20:33:53.454 align:start position:0% road and most Network Engineers kind of worry<20:33:51.480> about<20:33:52.256> using<20:33:52.680> these<20:33:52.856> color<20:33:52.976> commands 20:33:53.454 --> 20:33:53.464 align:start position:0% worry about using these color commands 20:33:53.464 --> 20:33:55.790 align:start position:0% worry about using these color commands like<20:33:53.640> even<20:33:53.872> something<20:33:54.296> simple<20:33:54.600> like<20:33:54.832> ipconfig 20:33:55.790 --> 20:33:55.800 align:start position:0% like even something simple like ipconfig 20:33:55.800 --> 20:33:57.710 align:start position:0% like even something simple like ipconfig gives<20:33:56.400> you<20:33:56.512> all<20:33:56.760> of<20:33:56.872> this<20:33:57.056> useful<20:33:57.480> information 20:33:57.710 --> 20:33:57.720 align:start position:0% gives you all of this useful information 20:33:57.720 --> 20:34:00.646 align:start position:0% gives you all of this useful information here<20:33:58.576> that<20:33:59.576> help<20:33:59.824> you<20:34:00.056> will<20:34:00.296> help<20:34:00.536> you 20:34:00.646 --> 20:34:00.656 align:start position:0% here that help you will help you 20:34:00.656 --> 20:34:04.182 align:start position:0% here that help you will help you troubleshoot<20:34:01.192> now<20:34:01.800> you<20:34:02.160> can<20:34:02.280> use<20:34:02.576> the<20:34:02.872> GUI<20:34:03.296> but 20:34:04.182 --> 20:34:04.192 align:start position:0% troubleshoot now you can use the GUI but 20:34:04.192 --> 20:34:05.566 align:start position:0% troubleshoot now you can use the GUI but it's<20:34:04.320> just<20:34:04.552> a<20:34:04.680> little<20:34:04.800> bit<20:34:04.920> more<20:34:05.104> clunky 20:34:05.566 --> 20:34:05.576 align:start position:0% it's just a little bit more clunky 20:34:05.576 --> 20:34:07.246 align:start position:0% it's just a little bit more clunky you've<20:34:05.760> got<20:34:05.872> to<20:34:06.000> go<20:34:06.120> through<20:34:06.296> a<20:34:06.536> menu<20:34:06.720> to<20:34:07.080> get 20:34:07.246 --> 20:34:07.256 align:start position:0% you've got to go through a menu to get 20:34:07.256 --> 20:34:09.414 align:start position:0% you've got to go through a menu to get to<20:34:07.376> another<20:34:07.552> menu<20:34:07.976> and<20:34:08.760> then<20:34:08.872> it's<20:34:09.056> only<20:34:09.240> going 20:34:09.414 --> 20:34:09.424 align:start position:0% to another menu and then it's only going 20:34:09.424 --> 20:34:12.526 align:start position:0% to another menu and then it's only going to<20:34:09.600> show<20:34:09.720> you<20:34:09.960> maybe<20:34:10.744> 50<20:34:11.104> of<20:34:12.056> what<20:34:12.240> you<20:34:12.360> could 20:34:12.526 --> 20:34:12.536 align:start position:0% to show you maybe 50 of what you could 20:34:12.536 --> 20:34:14.750 align:start position:0% to show you maybe 50 of what you could actually<20:34:12.656> see<20:34:12.960> if<20:34:13.192> you<20:34:13.320> use<20:34:13.504> the 20:34:14.750 --> 20:34:14.760 align:start position:0% actually see if you use the 20:34:14.760 --> 20:34:16.606 align:start position:0% actually see if you use the um command<20:34:15.120> line<20:34:15.296> and<20:34:15.960> if<20:34:16.080> you're<20:34:16.192> doing<20:34:16.376> some 20:34:16.606 --> 20:34:16.616 align:start position:0% um command line and if you're doing some 20:34:16.616 --> 20:34:18.646 align:start position:0% um command line and if you're doing some sort<20:34:16.744> of<20:34:16.856> emergency<20:34:17.104> recovery<20:34:17.936> you're 20:34:18.646 --> 20:34:18.656 align:start position:0% sort of emergency recovery you're 20:34:18.656 --> 20:34:20.502 align:start position:0% sort of emergency recovery you're probably<20:34:18.832> only<20:34:19.376> got<20:34:19.616> command<20:34:20.104> line<20:34:20.216> available 20:34:20.502 --> 20:34:20.512 align:start position:0% probably only got command line available 20:34:20.512 --> 20:34:22.734 align:start position:0% probably only got command line available anyway 20:34:22.734 --> 20:34:22.744 align:start position:0% anyway 20:34:22.744 --> 20:34:25.454 align:start position:0% anyway a<20:34:23.576> typical<20:34:23.936> exam<20:34:24.296> question 20:34:25.454 --> 20:34:25.464 align:start position:0% a typical exam question 20:34:25.464 --> 20:34:27.822 align:start position:0% a typical exam question ipconfig<20:34:26.464> will<20:34:26.872> give<20:34:27.056> you<20:34:27.176> the<20:34:27.360> TCP 20:34:27.822 --> 20:34:27.832 align:start position:0% ipconfig will give you the TCP 20:34:27.832 --> 20:34:29.950 align:start position:0% ipconfig will give you the TCP information<20:34:28.080> on<20:34:28.744> Linux<20:34:29.160> devices<20:34:29.512> this 20:34:29.950 --> 20:34:29.960 align:start position:0% information on Linux devices this 20:34:29.960 --> 20:34:33.526 align:start position:0% information on Linux devices this ifconfig<20:34:30.960> classic<20:34:31.616> exam<20:34:32.160> question<20:34:32.400> that<20:34:32.824> is 20:34:33.526 --> 20:34:33.536 align:start position:0% ifconfig classic exam question that is 20:34:33.536 --> 20:34:35.686 align:start position:0% ifconfig classic exam question that is IP<20:34:34.080> information<20:34:34.256> for<20:34:34.680> your<20:34:34.800> local<20:34:34.920> interfaces 20:34:35.686 --> 20:34:35.696 align:start position:0% IP information for your local interfaces 20:34:35.696 --> 20:34:39.950 align:start position:0% IP information for your local interfaces including<20:34:36.424> your<20:34:37.376> wireless<20:34:37.552> adapter<20:34:38.336> any 20:34:39.950 --> 20:34:39.960 align:start position:0% including your wireless adapter any 20:34:39.960 --> 20:34:42.710 align:start position:0% including your wireless adapter any um<20:34:40.016> virtual<20:34:40.616> adapters 20:34:42.710 --> 20:34:42.720 align:start position:0% um virtual adapters 20:34:42.720 --> 20:34:45.790 align:start position:0% um virtual adapters virtual<20:34:43.504> land<20:34:43.800> cards<20:34:44.336> Wireless 20:34:45.790 --> 20:34:45.800 align:start position:0% virtual land cards Wireless 20:34:45.800 --> 20:34:48.790 align:start position:0% virtual land cards Wireless or<20:34:46.800> ethernet 20:34:48.790 --> 20:34:48.800 align:start position:0% or ethernet 20:34:48.800 --> 20:34:51.470 align:start position:0% or ethernet uh<20:34:49.800> you<20:34:49.976> can<20:34:50.216> use<20:34:50.336> switches<20:34:50.824> to<20:34:51.056> drill<20:34:51.296> down 20:34:51.470 --> 20:34:51.480 align:start position:0% uh you can use switches to drill down 20:34:51.480 --> 20:34:54.886 align:start position:0% uh you can use switches to drill down for<20:34:51.784> example<20:34:52.040> ipconfig<20:34:53.040> forward<20:34:53.872> slash<20:34:54.424> all 20:34:54.886 --> 20:34:54.896 align:start position:0% for example ipconfig forward slash all 20:34:54.896 --> 20:34:56.630 align:start position:0% for example ipconfig forward slash all there's<20:34:55.376> a<20:34:55.552> whole<20:34:55.616> bunch<20:34:55.856> of<20:34:56.040> switches 20:34:56.630 --> 20:34:56.640 align:start position:0% there's a whole bunch of switches 20:34:56.640 --> 20:34:59.814 align:start position:0% there's a whole bunch of switches actually<20:34:57.256> uh<20:34:58.256> most 20:34:59.814 --> 20:34:59.824 align:start position:0% actually uh most 20:34:59.824 --> 20:35:01.734 align:start position:0% actually uh most um command<20:35:00.176> line<20:35:00.360> tools<20:35:00.784> will<20:35:00.960> let<20:35:01.144> you<20:35:01.256> issue 20:35:01.734 --> 20:35:01.744 align:start position:0% um command line tools will let you issue 20:35:01.744 --> 20:35:03.470 align:start position:0% um command line tools will let you issue the<20:35:02.040> question<20:35:02.336> mark<20:35:02.640> and<20:35:02.872> then<20:35:03.000> it<20:35:03.176> will<20:35:03.296> save 20:35:03.470 --> 20:35:03.480 align:start position:0% the question mark and then it will save 20:35:03.480 --> 20:35:06.110 align:start position:0% the question mark and then it will save these<20:35:03.784> year<20:35:03.960> options 20:35:06.110 --> 20:35:06.120 align:start position:0% these year options 20:35:06.120 --> 20:35:09.646 align:start position:0% these year options IP<20:35:06.832> tables<20:35:07.320> this<20:35:07.616> is<20:35:07.744> a<20:35:07.920> Unix<20:35:08.216> command<20:35:08.696> a<20:35:09.296> lot<20:35:09.536> a 20:35:09.646 --> 20:35:09.656 align:start position:0% IP tables this is a Unix command a lot a 20:35:09.656 --> 20:35:11.822 align:start position:0% IP tables this is a Unix command a lot a lot<20:35:09.784> of<20:35:09.832> people<20:35:10.016> it's<20:35:10.496> you'll<20:35:10.976> either<20:35:11.160> you<20:35:11.464> you 20:35:11.822 --> 20:35:11.832 align:start position:0% lot of people it's you'll either you you 20:35:11.832 --> 20:35:15.110 align:start position:0% lot of people it's you'll either you you use<20:35:12.832> Unix<20:35:13.376> a<20:35:13.616> lot<20:35:13.744> because<20:35:13.920> it's<20:35:14.160> your<20:35:14.336> job<20:35:14.576> or 20:35:15.110 --> 20:35:15.120 align:start position:0% use Unix a lot because it's your job or 20:35:15.120 --> 20:35:16.606 align:start position:0% use Unix a lot because it's your job or you've<20:35:15.360> probably<20:35:15.480> never<20:35:15.656> touched<20:35:16.016> it<20:35:16.144> at<20:35:16.320> all 20:35:16.606 --> 20:35:16.616 align:start position:0% you've probably never touched it at all 20:35:16.616 --> 20:35:19.182 align:start position:0% you've probably never touched it at all but<20:35:17.400> it<20:35:17.576> configures<20:35:18.000> the<20:35:18.240> kernel<20:35:18.832> firewall 20:35:19.182 --> 20:35:19.192 align:start position:0% but it configures the kernel firewall 20:35:19.192 --> 20:35:20.990 align:start position:0% but it configures the kernel firewall the<20:35:19.680> only<20:35:19.744> reason<20:35:19.920> I<20:35:20.216> mentioned<20:35:20.512> this<20:35:20.696> command 20:35:20.990 --> 20:35:21.000 align:start position:0% the only reason I mentioned this command 20:35:21.000 --> 20:35:24.166 align:start position:0% the only reason I mentioned this command is<20:35:21.240> because<20:35:21.656> it's<20:35:22.144> in<20:35:22.376> the 20:35:24.166 --> 20:35:24.176 align:start position:0% is because it's in the 20:35:24.176 --> 20:35:27.886 align:start position:0% is because it's in the the<20:35:24.536> dreaded<20:35:25.144> syllabus<20:35:25.616> oops<20:35:26.336> syllabus 20:35:27.886 --> 20:35:27.896 align:start position:0% the dreaded syllabus oops syllabus 20:35:27.896 --> 20:35:28.966 align:start position:0% the dreaded syllabus oops syllabus so 20:35:28.966 --> 20:35:28.976 align:start position:0% so 20:35:28.976 --> 20:35:30.886 align:start position:0% so um I<20:35:29.512> think<20:35:29.640> just<20:35:29.824> know<20:35:30.056> this<20:35:30.296> command<20:35:30.656> and 20:35:30.886 --> 20:35:30.896 align:start position:0% um I think just know this command and 20:35:30.896 --> 20:35:33.286 align:start position:0% um I think just know this command and what<20:35:31.144> it<20:35:31.320> does<20:35:31.504> known<20:35:31.976> all<20:35:32.280> this<20:35:32.464> stuff<20:35:32.696> I've 20:35:33.286 --> 20:35:33.296 align:start position:0% what it does known all this stuff I've 20:35:33.296 --> 20:35:34.790 align:start position:0% what it does known all this stuff I've put<20:35:33.480> it<20:35:33.600> here<20:35:33.784> so<20:35:33.960> you<20:35:34.080> can<20:35:34.192> just<20:35:34.320> see<20:35:34.440> some<20:35:34.680> of 20:35:34.790 --> 20:35:34.800 align:start position:0% put it here so you can just see some of 20:35:34.800 --> 20:35:37.006 align:start position:0% put it here so you can just see some of the<20:35:34.920> options<20:35:35.160> but<20:35:35.400> I<20:35:35.696> really<20:35:35.872> doubt<20:35:36.360> that<20:35:36.896> you 20:35:37.006 --> 20:35:37.016 align:start position:0% the options but I really doubt that you 20:35:37.016 --> 20:35:38.630 align:start position:0% the options but I really doubt that you would<20:35:37.144> need<20:35:37.256> to<20:35:37.376> know<20:35:37.552> it 20:35:38.630 --> 20:35:38.640 align:start position:0% would need to know it 20:35:38.640 --> 20:35:42.310 align:start position:0% would need to know it um<20:35:38.696> I<20:35:38.872> took<20:35:39.176> this<20:35:39.360> uh<20:35:40.080> lot<20:35:40.920> here<20:35:41.160> from 20:35:42.310 --> 20:35:42.320 align:start position:0% um I took this uh lot here from 20:35:42.320 --> 20:35:44.630 align:start position:0% um I took this uh lot here from tutorialspoint.com<20:35:43.320> if<20:35:44.160> you're<20:35:44.280> nowhere 20:35:44.630 --> 20:35:44.640 align:start position:0% tutorialspoint.com if you're nowhere 20:35:44.640 --> 20:35:46.134 align:start position:0% tutorialspoint.com if you're nowhere look<20:35:44.824> at<20:35:44.936> that<20:35:45.056> URL 20:35:46.134 --> 20:35:46.144 align:start position:0% look at that URL 20:35:46.144 --> 20:35:48.286 align:start position:0% look at that URL net<20:35:46.744> starts<20:35:47.216> a<20:35:47.280> handy<20:35:47.512> command<20:35:47.824> basically 20:35:48.286 --> 20:35:48.296 align:start position:0% net starts a handy command basically 20:35:48.296 --> 20:35:50.206 align:start position:0% net starts a handy command basically short<20:35:48.536> for<20:35:48.784> Network<20:35:48.960> statistics<20:35:49.680> thankfully 20:35:50.206 --> 20:35:50.216 align:start position:0% short for Network statistics thankfully 20:35:50.216 --> 20:35:52.486 align:start position:0% short for Network statistics thankfully so<20:35:50.464> it's<20:35:50.576> easy<20:35:50.760> to<20:35:51.000> work<20:35:51.240> that<20:35:51.480> out<20:35:51.656> shows<20:35:52.376> your 20:35:52.486 --> 20:35:52.496 align:start position:0% so it's easy to work that out shows your 20:35:52.496 --> 20:35:54.590 align:start position:0% so it's easy to work that out shows your active<20:35:52.800> connections<20:35:53.336> tells<20:35:54.000> you<20:35:54.056> the<20:35:54.240> type<20:35:54.424> of 20:35:54.590 --> 20:35:54.600 align:start position:0% active connections tells you the type of 20:35:54.600 --> 20:35:56.630 align:start position:0% active connections tells you the type of services<20:35:54.784> you're<20:35:55.256> running<20:35:55.440> and<20:35:56.216> you<20:35:56.336> could<20:35:56.512> be 20:35:56.630 --> 20:35:56.640 align:start position:0% services you're running and you could be 20:35:56.640 --> 20:35:58.734 align:start position:0% services you're running and you could be in<20:35:56.760> for<20:35:56.936> a<20:35:57.120> surprise 20:35:58.734 --> 20:35:58.744 align:start position:0% in for a surprise 20:35:58.744 --> 20:36:00.526 align:start position:0% in for a surprise um if<20:35:59.040> you<20:35:59.160> see<20:35:59.336> things<20:35:59.696> running<20:35:59.936> on<20:36:00.296> your 20:36:00.526 --> 20:36:00.536 align:start position:0% um if you see things running on your 20:36:00.536 --> 20:36:02.686 align:start position:0% um if you see things running on your device<20:36:00.720> that<20:36:01.192> you<20:36:01.744> you<20:36:02.040> didn't<20:36:02.216> think<20:36:02.464> should 20:36:02.686 --> 20:36:02.696 align:start position:0% device that you you didn't think should 20:36:02.696 --> 20:36:04.070 align:start position:0% device that you you didn't think should be<20:36:02.872> there 20:36:04.070 --> 20:36:04.080 align:start position:0% be there 20:36:04.080 --> 20:36:07.494 align:start position:0% be there there's<20:36:04.440> a<20:36:04.680> few<20:36:04.800> switches<20:36:05.424> let's<20:36:06.424> start<20:36:06.720> minus 20:36:07.494 --> 20:36:07.504 align:start position:0% there's a few switches let's start minus 20:36:07.504 --> 20:36:11.566 align:start position:0% there's a few switches let's start minus n<20:36:07.800> minus<20:36:08.400> a<20:36:08.896> minus<20:36:09.896> B<20:36:10.080> I'm<20:36:10.976> not<20:36:11.216> sure<20:36:11.336> you'll 20:36:11.566 --> 20:36:11.576 align:start position:0% n minus a minus B I'm not sure you'll 20:36:11.576 --> 20:36:12.950 align:start position:0% n minus a minus B I'm not sure you'll need<20:36:11.696> to<20:36:11.760> know<20:36:11.872> the<20:36:12.056> switches<20:36:12.424> although<20:36:12.832> I 20:36:12.950 --> 20:36:12.960 align:start position:0% need to know the switches although I 20:36:12.960 --> 20:36:15.470 align:start position:0% need to know the switches although I can't<20:36:13.144> guarantee<20:36:13.616> it<20:36:13.856> active<20:36:14.824> connections 20:36:15.470 --> 20:36:15.480 align:start position:0% can't guarantee it active connections 20:36:15.480 --> 20:36:17.990 align:start position:0% can't guarantee it active connections the<20:36:15.960> applications<20:36:16.496> the<20:36:17.336> connections<20:36:17.824> without 20:36:17.990 --> 20:36:18.000 align:start position:0% the applications the connections without 20:36:18.000 --> 20:36:20.990 align:start position:0% the applications the connections without doing<20:36:18.296> a<20:36:18.480> DNS<20:36:18.896> resolution 20:36:20.990 --> 20:36:21.000 align:start position:0% doing a DNS resolution 20:36:21.000 --> 20:36:25.246 align:start position:0% doing a DNS resolution uh<20:36:21.720> here's<20:36:22.080> a<20:36:22.144> net<20:36:22.320> start<20:36:22.616> from<20:36:23.832> uh<20:36:24.832> this<20:36:25.192> is 20:36:25.246 --> 20:36:25.256 align:start position:0% uh here's a net start from uh this is 20:36:25.256 --> 20:36:26.630 align:start position:0% uh here's a net start from uh this is from<20:36:25.440> one<20:36:25.680> of<20:36:25.744> my<20:36:25.800> authors<20:36:26.160> actually<20:36:26.400> I 20:36:26.630 --> 20:36:26.640 align:start position:0% from one of my authors actually I 20:36:26.640 --> 20:36:28.846 align:start position:0% from one of my authors actually I recognize<20:36:27.000> the<20:36:27.240> name<20:36:27.424> from<20:36:27.784> his<20:36:27.960> device<20:36:28.144> he's 20:36:28.846 --> 20:36:28.856 align:start position:0% recognize the name from his device he's 20:36:28.856 --> 20:36:31.070 align:start position:0% recognize the name from his device he's obviously<20:36:29.280> named<20:36:29.640> his<20:36:29.824> device<20:36:30.176> after<20:36:30.600> himself 20:36:31.070 --> 20:36:31.080 align:start position:0% obviously named his device after himself 20:36:31.080 --> 20:36:33.590 align:start position:0% obviously named his device after himself let's<20:36:31.800> start<20:36:32.040> mine<20:36:32.336> is<20:36:32.512> a<20:36:32.696> and<20:36:33.176> you<20:36:33.360> can<20:36:33.480> see 20:36:33.590 --> 20:36:33.600 align:start position:0% let's start mine is a and you can see 20:36:33.600 --> 20:36:35.926 align:start position:0% let's start mine is a and you can see the<20:36:33.784> state<20:36:33.960> of<20:36:34.144> all<20:36:34.320> of<20:36:34.496> these<20:36:35.336> um<20:36:35.400> ports 20:36:35.926 --> 20:36:35.936 align:start position:0% the state of all of these um ports 20:36:35.936 --> 20:36:38.454 align:start position:0% the state of all of these um ports there's<20:36:36.424> an<20:36:36.656> established<20:36:37.192> Port<20:36:37.440> here 20:36:38.454 --> 20:36:38.464 align:start position:0% there's an established Port here 20:36:38.464 --> 20:36:41.566 align:start position:0% there's an established Port here and<20:36:39.056> then<20:36:39.176> you<20:36:39.536> could<20:36:39.656> obviously<20:36:40.216> do<20:36:41.216> a<20:36:41.400> search 20:36:41.566 --> 20:36:41.576 align:start position:0% and then you could obviously do a search 20:36:41.576 --> 20:36:43.846 align:start position:0% and then you could obviously do a search and<20:36:41.824> find<20:36:42.000> out<20:36:42.176> what<20:36:42.480> this<20:36:42.656> is<20:36:42.832> he<20:36:43.440> may<20:36:43.680> what 20:36:43.846 --> 20:36:43.856 align:start position:0% and find out what this is he may what 20:36:43.856 --> 20:36:45.886 align:start position:0% and find out what this is he may what may<20:36:44.104> well<20:36:44.280> be<20:36:44.464> connected<20:36:45.000> to<20:36:45.176> a<20:36:45.360> Remote<20:36:45.480> device 20:36:45.886 --> 20:36:45.896 align:start position:0% may well be connected to a Remote device 20:36:45.896 --> 20:36:49.006 align:start position:0% may well be connected to a Remote device he<20:36:46.616> may<20:36:46.800> be<20:36:46.976> chatting<20:36:47.336> on<20:36:47.512> MSN<20:36:48.120> or<20:36:48.784> Facebook 20:36:49.006 --> 20:36:49.016 align:start position:0% he may be chatting on MSN or Facebook 20:36:49.016 --> 20:36:51.166 align:start position:0% he may be chatting on MSN or Facebook Messenger<20:36:49.744> or<20:36:50.040> and<20:36:50.464> you<20:36:50.576> could<20:36:50.696> quite<20:36:50.872> easily 20:36:51.166 --> 20:36:51.176 align:start position:0% Messenger or and you could quite easily 20:36:51.176 --> 20:36:54.366 align:start position:0% Messenger or and you could quite easily find<20:36:51.360> out<20:36:51.536> what<20:36:51.720> all<20:36:51.832> these<20:36:52.080> ports<20:36:52.376> are<20:36:52.496> for 20:36:54.366 --> 20:36:54.376 align:start position:0% find out what all these ports are for 20:36:54.376 --> 20:36:58.542 align:start position:0% find out what all these ports are for TCP<20:36:55.376> dump<20:36:55.744> and<20:36:55.976> here's<20:36:56.400> the<20:36:56.512> output<20:36:57.000> here 20:36:58.542 --> 20:36:58.552 align:start position:0% TCP dump and here's the output here 20:36:58.552 --> 20:37:01.542 align:start position:0% TCP dump and here's the output here it's<20:36:59.104> a<20:36:59.280> Unix<20:36:59.576> command<20:37:00.000> it's<20:37:00.720> a<20:37:00.896> sniffing<20:37:01.256> tool 20:37:01.542 --> 20:37:01.552 align:start position:0% it's a Unix command it's a sniffing tool 20:37:01.552 --> 20:37:04.006 align:start position:0% it's a Unix command it's a sniffing tool so<20:37:01.680> what<20:37:01.856> you<20:37:01.976> can<20:37:02.104> do<20:37:02.216> is<20:37:02.336> use<20:37:02.576> it<20:37:02.760> to<20:37:02.936> Snoop 20:37:04.006 --> 20:37:04.016 align:start position:0% so what you can do is use it to Snoop 20:37:04.016 --> 20:37:06.590 align:start position:0% so what you can do is use it to Snoop um<20:37:04.144> the<20:37:04.680> if<20:37:05.040> you're<20:37:05.576> if<20:37:06.000> you<20:37:06.120> want<20:37:06.240> to<20:37:06.360> do<20:37:06.480> the 20:37:06.590 --> 20:37:06.600 align:start position:0% um the if you're if you want to do the 20:37:06.600 --> 20:37:08.862 align:start position:0% um the if you're if you want to do the snooping<20:37:06.960> it's<20:37:07.256> the<20:37:07.504> Snoop<20:37:07.856> command<20:37:08.216> if 20:37:08.862 --> 20:37:08.872 align:start position:0% snooping it's the Snoop command if 20:37:08.872 --> 20:37:11.094 align:start position:0% snooping it's the Snoop command if you're<20:37:09.000> using<20:37:09.360> Solaris 20:37:11.094 --> 20:37:11.104 align:start position:0% you're using Solaris 20:37:11.104 --> 20:37:13.542 align:start position:0% you're using Solaris um<20:37:11.160> pretty<20:37:11.576> specialized<20:37:12.360> a<20:37:12.960> bit<20:37:13.192> of<20:37:13.320> software 20:37:13.542 --> 20:37:13.552 align:start position:0% um pretty specialized a bit of software 20:37:13.552 --> 20:37:15.470 align:start position:0% um pretty specialized a bit of software but<20:37:13.856> I've<20:37:14.280> seen<20:37:14.400> some<20:37:14.760> of<20:37:14.872> the<20:37:14.936> network<20:37:15.056> teams 20:37:15.470 --> 20:37:15.480 align:start position:0% but I've seen some of the network teams 20:37:15.480 --> 20:37:17.686 align:start position:0% but I've seen some of the network teams using<20:37:15.720> Evernote<20:37:16.192> menu<20:37:16.440> you<20:37:17.336> can<20:37:17.400> view<20:37:17.512> the 20:37:17.686 --> 20:37:17.696 align:start position:0% using Evernote menu you can view the 20:37:17.696 --> 20:37:19.366 align:start position:0% using Evernote menu you can view the packets<20:37:18.000> on<20:37:18.240> the<20:37:18.424> Y<20:37:18.480> app 20:37:19.366 --> 20:37:19.376 align:start position:0% packets on the Y app 20:37:19.376 --> 20:37:23.686 align:start position:0% packets on the Y app pathping 20:37:23.686 --> 20:37:23.696 align:start position:0% 20:37:23.696 --> 20:37:25.542 align:start position:0% now<20:37:24.120> this<20:37:24.360> is<20:37:24.424> a<20:37:24.600> tracer<20:37:24.960> command<20:37:25.376> actually 20:37:25.542 --> 20:37:25.552 align:start position:0% now this is a tracer command actually 20:37:25.552 --> 20:37:29.150 align:start position:0% now this is a tracer command actually it's<20:37:26.512> a<20:37:26.696> TCP<20:37:27.192> tool<20:37:28.192> it<20:37:28.496> provides<20:37:28.920> information 20:37:29.150 --> 20:37:29.160 align:start position:0% it's a TCP tool it provides information 20:37:29.160 --> 20:37:32.270 align:start position:0% it's a TCP tool it provides information about<20:37:29.576> Network<20:37:30.000> latency<20:37:30.720> and<20:37:31.320> sends<20:37:31.616> icmp 20:37:32.270 --> 20:37:32.280 align:start position:0% about Network latency and sends icmp 20:37:32.280 --> 20:37:35.150 align:start position:0% about Network latency and sends icmp Echo<20:37:32.824> requests 20:37:35.150 --> 20:37:35.160 align:start position:0% Echo requests 20:37:35.160 --> 20:37:37.070 align:start position:0% Echo requests and<20:37:35.760> map<20:37:36.000> I<20:37:36.240> think<20:37:36.360> I<20:37:36.480> mentioned<20:37:36.720> this<20:37:36.896> before 20:37:37.070 --> 20:37:37.080 align:start position:0% and map I think I mentioned this before 20:37:37.080 --> 20:37:39.414 align:start position:0% and map I think I mentioned this before actually<20:37:37.440> she<20:37:38.280> used<20:37:38.400> to<20:37:38.576> discover<20:37:38.696> computers 20:37:39.414 --> 20:37:39.424 align:start position:0% actually she used to discover computers 20:37:39.424 --> 20:37:41.990 align:start position:0% actually she used to discover computers and<20:37:39.656> services<20:37:39.960> on<20:37:40.376> a<20:37:40.552> computer<20:37:40.744> network<20:37:41.160> in 20:37:41.990 --> 20:37:42.000 align:start position:0% and services on a computer network in 20:37:42.000 --> 20:37:44.270 align:start position:0% and services on a computer network in order<20:37:42.176> to<20:37:42.424> create<20:37:42.600> a<20:37:42.960> map 20:37:44.270 --> 20:37:44.280 align:start position:0% order to create a map 20:37:44.280 --> 20:37:45.950 align:start position:0% order to create a map and<20:37:44.824> you<20:37:44.936> can<20:37:45.056> see 20:37:45.950 --> 20:37:45.960 align:start position:0% and you can see 20:37:45.960 --> 20:37:47.750 align:start position:0% and you can see there's<20:37:46.440> a<20:37:46.616> whole<20:37:46.744> bunch<20:37:46.976> of<20:37:47.160> services<20:37:47.336> here 20:37:47.750 --> 20:37:47.760 align:start position:0% there's a whole bunch of services here 20:37:47.760 --> 20:37:49.310 align:start position:0% there's a whole bunch of services here many<20:37:48.056> of<20:37:48.240> them<20:37:48.360> probably<20:37:48.480> look<20:37:48.720> familiar<20:37:49.144> to 20:37:49.310 --> 20:37:49.320 align:start position:0% many of them probably look familiar to 20:37:49.320 --> 20:37:51.710 align:start position:0% many of them probably look familiar to you 20:37:51.710 --> 20:37:51.720 align:start position:0% 20:37:51.720 --> 20:37:53.990 align:start position:0% and<20:37:52.144> at<20:37:52.440> the<20:37:52.552> end<20:37:52.616> it<20:37:52.800> says<20:37:52.976> Two<20:37:53.216> Hosts<20:37:53.640> up<20:37:53.760> and 20:37:53.990 --> 20:37:54.000 align:start position:0% and at the end it says Two Hosts up and 20:37:54.000 --> 20:37:56.630 align:start position:0% and at the end it says Two Hosts up and how<20:37:54.120> long<20:37:54.240> it<20:37:54.480> took<20:37:54.960> to<20:37:55.144> scan<20:37:55.376> it 20:37:56.630 --> 20:37:56.640 align:start position:0% how long it took to scan it 20:37:56.640 --> 20:37:58.966 align:start position:0% how long it took to scan it uh<20:37:56.936> vulnerability<20:37:57.656> scanning<20:37:58.192> Tool<20:37:58.496> uh<20:37:58.800> just 20:37:58.966 --> 20:37:58.976 align:start position:0% uh vulnerability scanning Tool uh just 20:37:58.976 --> 20:38:01.734 align:start position:0% uh vulnerability scanning Tool uh just bear<20:37:59.216> that<20:37:59.464> in<20:37:59.576> mind<20:37:59.824> again<20:38:00.536> typical<20:38:01.016> type<20:38:01.616> of 20:38:01.734 --> 20:38:01.744 align:start position:0% bear that in mind again typical type of 20:38:01.744 --> 20:38:03.166 align:start position:0% bear that in mind again typical type of question<20:38:01.920> they'll<20:38:02.216> ask<20:38:02.400> you<20:38:02.512> what's<20:38:02.696> nmap 20:38:03.166 --> 20:38:03.176 align:start position:0% question they'll ask you what's nmap 20:38:03.176 --> 20:38:05.094 align:start position:0% question they'll ask you what's nmap used<20:38:03.360> for<20:38:03.600> or 20:38:05.094 --> 20:38:05.104 align:start position:0% used for or 20:38:05.104 --> 20:38:06.646 align:start position:0% used for or um tick<20:38:05.464> the<20:38:05.696> relevant<20:38:06.056> vulnerability 20:38:06.646 --> 20:38:06.656 align:start position:0% um tick the relevant vulnerability 20:38:06.656 --> 20:38:09.350 align:start position:0% um tick the relevant vulnerability scanning<20:38:07.192> tools<20:38:07.552> used<20:38:08.216> for<20:38:08.400> auditing<20:38:08.936> by<20:38:09.176> you 20:38:09.350 --> 20:38:09.360 align:start position:0% scanning tools used for auditing by you 20:38:09.360 --> 20:38:11.454 align:start position:0% scanning tools used for auditing by you or<20:38:09.656> obviously<20:38:10.144> whatever<20:38:10.680> can<20:38:11.040> be<20:38:11.160> used<20:38:11.280> for 20:38:11.454 --> 20:38:11.464 align:start position:0% or obviously whatever can be used for 20:38:11.464 --> 20:38:13.366 align:start position:0% or obviously whatever can be used for good<20:38:11.576> can<20:38:11.824> be<20:38:11.936> used<20:38:12.056> for<20:38:12.240> bad<20:38:12.480> and<20:38:13.016> it<20:38:13.144> can<20:38:13.256> be 20:38:13.366 --> 20:38:13.376 align:start position:0% good can be used for bad and it can be 20:38:13.376 --> 20:38:16.734 align:start position:0% good can be used for bad and it can be used<20:38:13.504> by<20:38:13.744> hackers 20:38:16.734 --> 20:38:16.744 align:start position:0% 20:38:16.744 --> 20:38:19.006 align:start position:0% dig<20:38:17.640> and<20:38:17.872> he<20:38:18.056> said<20:38:18.176> the<20:38:18.296> command<20:38:18.720> has<20:38:18.832> been 20:38:19.006 --> 20:38:19.016 align:start position:0% dig and he said the command has been 20:38:19.016 --> 20:38:20.206 align:start position:0% dig and he said the command has been used<20:38:19.192> here 20:38:20.206 --> 20:38:20.216 align:start position:0% used here 20:38:20.216 --> 20:38:23.030 align:start position:0% used here domain<20:38:21.000> information<20:38:21.296> growth<20:38:22.192> it<20:38:22.800> basically 20:38:23.030 --> 20:38:23.040 align:start position:0% domain information growth it basically 20:38:23.040 --> 20:38:26.630 align:start position:0% domain information growth it basically sends<20:38:23.400> off<20:38:23.464> a<20:38:23.640> query<20:38:23.872> to<20:38:24.176> DNS<20:38:24.856> servers<20:38:25.856> it's 20:38:26.630 --> 20:38:26.640 align:start position:0% sends off a query to DNS servers it's 20:38:26.640 --> 20:38:29.150 align:start position:0% sends off a query to DNS servers it's the<20:38:26.824> same<20:38:27.000> as<20:38:27.120> the<20:38:27.296> NS<20:38:27.600> lookup<20:38:28.016> tool<20:38:28.376> but<20:38:28.856> this 20:38:29.150 --> 20:38:29.160 align:start position:0% the same as the NS lookup tool but this 20:38:29.160 --> 20:38:35.566 align:start position:0% the same as the NS lookup tool but this particular<20:38:29.400> one<20:38:29.760> is<20:38:30.176> used<20:38:30.480> for<20:38:30.896> Linux<20:38:31.680> devices 20:38:35.566 --> 20:38:35.576 align:start position:0% 20:38:35.576 --> 20:38:38.150 align:start position:0% now<20:38:35.936> you<20:38:36.120> can<20:38:36.240> see<20:38:36.360> it's<20:38:36.784> done<20:38:37.016> a<20:38:37.320> search<20:38:37.976> for 20:38:38.150 --> 20:38:38.160 align:start position:0% now you can see it's done a search for 20:38:38.160 --> 20:38:39.886 align:start position:0% now you can see it's done a search for example.com 20:38:39.886 --> 20:38:39.896 align:start position:0% example.com 20:38:39.896 --> 20:38:45.646 align:start position:0% example.com and<20:38:40.440> you<20:38:40.552> can<20:38:40.680> see<20:38:40.976> uh<20:38:41.824> the<20:38:42.000> name<20:38:42.424> servers<20:38:42.960> here 20:38:45.646 --> 20:38:45.656 align:start position:0% 20:38:45.656 --> 20:38:48.646 align:start position:0% IP<20:38:46.192> address<20:38:46.376> DNS<20:38:47.104> servers<20:38:47.512> cash<20:38:47.872> timers<20:38:48.424> that 20:38:48.646 --> 20:38:48.656 align:start position:0% IP address DNS servers cash timers that 20:38:48.656 --> 20:38:51.166 align:start position:0% IP address DNS servers cash timers that kind<20:38:48.832> of<20:38:48.960> thing 20:38:51.166 --> 20:38:51.176 align:start position:0% 20:38:51.176 --> 20:38:53.990 align:start position:0% that<20:38:51.784> looks<20:38:52.080> like<20:38:52.192> a<20:38:52.800> um<20:38:52.800> that<20:38:53.640> looks<20:38:53.936> like 20:38:53.990 --> 20:38:54.000 align:start position:0% that looks like a um that looks like 20:38:54.000 --> 20:38:56.094 align:start position:0% that looks like a um that looks like Google<20:38:54.296> actually 20:38:56.094 --> 20:38:56.104 align:start position:0% Google actually 20:38:56.104 --> 20:38:58.310 align:start position:0% Google actually from<20:38:56.640> if<20:38:57.176> my<20:38:57.360> memory<20:38:57.536> says<20:38:57.896> I<20:38:58.016> think<20:38:58.144> they've 20:38:58.310 --> 20:38:58.320 align:start position:0% from if my memory says I think they've 20:38:58.320 --> 20:39:00.470 align:start position:0% from if my memory says I think they've got<20:38:58.496> eight<20:38:58.744> eight<20:38:59.040> eight<20:38:59.120> and<20:39:00.120> eight<20:39:00.240> eight 20:39:00.470 --> 20:39:00.480 align:start position:0% got eight eight eight and eight eight 20:39:00.480 --> 20:39:03.950 align:start position:0% got eight eight eight and eight eight four<20:39:00.720> four<20:39:00.960> you<20:39:01.680> can<20:39:01.856> check<20:39:02.280> for<20:39:02.464> yourself<20:39:02.960> all 20:39:03.950 --> 20:39:03.960 align:start position:0% four four you can check for yourself all 20:39:03.960 --> 20:39:05.814 align:start position:0% four four you can check for yourself all right<20:39:04.080> so<20:39:04.256> looked<20:39:04.616> at<20:39:04.744> some<20:39:04.856> cool<20:39:05.040> stuff<20:39:05.464> uh 20:39:05.814 --> 20:39:05.824 align:start position:0% right so looked at some cool stuff uh 20:39:05.824 --> 20:39:08.750 align:start position:0% right so looked at some cool stuff uh package<20:39:06.176> sniffer<20:39:06.600> Wi-Fi<20:39:06.960> analyzer<20:39:07.856> bandwidth 20:39:08.750 --> 20:39:08.760 align:start position:0% package sniffer Wi-Fi analyzer bandwidth 20:39:08.760 --> 20:39:10.606 align:start position:0% package sniffer Wi-Fi analyzer bandwidth speed<20:39:08.872> taster<20:39:09.176> and<20:39:09.720> some<20:39:09.896> important<20:39:10.256> command 20:39:10.606 --> 20:39:10.616 align:start position:0% speed taster and some important command 20:39:10.616 --> 20:39:12.774 align:start position:0% speed taster and some important command line<20:39:10.744> tools<20:39:11.216> remember<20:39:11.760> we're<20:39:12.176> covering<20:39:12.536> this 20:39:12.774 --> 20:39:12.784 align:start position:0% line tools remember we're covering this 20:39:12.784 --> 20:39:14.926 align:start position:0% line tools remember we're covering this in<20:39:13.080> in<20:39:13.256> other<20:39:13.504> presentations<20:39:14.104> too<20:39:14.464> so<20:39:14.696> this 20:39:14.926 --> 20:39:14.936 align:start position:0% in in other presentations too so this 20:39:14.936 --> 20:39:17.326 align:start position:0% in in other presentations too so this was<20:39:15.120> just<20:39:15.480> a<20:39:16.016> subset<20:39:16.376> of<20:39:16.552> all<20:39:16.744> the<20:39:16.856> stuff<20:39:17.040> that 20:39:17.326 --> 20:39:17.336 align:start position:0% was just a subset of all the stuff that 20:39:17.336 --> 20:39:18.590 align:start position:0% was just a subset of all the stuff that you<20:39:17.400> need<20:39:17.640> to<20:39:17.760> know 20:39:18.590 --> 20:39:18.600 align:start position:0% you need to know 20:39:18.600 --> 20:39:20.566 align:start position:0% you need to know so<20:39:19.256> that's<20:39:19.680> the<20:39:19.856> end<20:39:19.920> of<20:39:20.104> the<20:39:20.160> presentation 20:39:20.566 --> 20:39:20.576 align:start position:0% so that's the end of the presentation 20:39:20.576 --> 20:39:25.020 align:start position:0% so that's the end of the presentation thanks<20:39:21.120> for<20:39:21.240> watching 20:39:25.020 --> 20:39:25.030 align:start position:0% 20:39:25.030 --> 20:39:33.430 align:start position:0% [Music] 20:39:33.430 --> 20:39:33.440 align:start position:0% [Music] 20:39:33.440 --> 20:39:41.206 align:start position:0% [Music] thank<20:39:34.440> you 20:39:41.206 --> 20:39:41.216 align:start position:0% 20:39:41.216 --> 20:39:43.910 align:start position:0% welcome<20:39:41.696> to<20:39:41.872> module<20:39:42.240> 15<20:39:42.424> lesson<20:39:43.016> 2<20:39:43.192> height 20:39:43.910 --> 20:39:43.920 align:start position:0% welcome to module 15 lesson 2 height 20:39:43.920 --> 20:39:46.366 align:start position:0% welcome to module 15 lesson 2 height availability<20:39:44.576> and<20:39:45.000> low<20:39:45.176> balancing<20:39:45.720> we're 20:39:46.366 --> 20:39:46.376 align:start position:0% availability and low balancing we're 20:39:46.376 --> 20:39:49.494 align:start position:0% availability and low balancing we're just<20:39:46.552> hitting<20:39:46.856> another<20:39:46.976> syllabus<20:39:47.640> topic<20:39:48.120> here 20:39:49.494 --> 20:39:49.504 align:start position:0% just hitting another syllabus topic here 20:39:49.504 --> 20:39:52.134 align:start position:0% just hitting another syllabus topic here um just<20:39:49.856> a<20:39:49.976> brief<20:39:50.216> overview<20:39:50.640> really<20:39:51.360> high 20:39:52.134 --> 20:39:52.144 align:start position:0% um just a brief overview really high 20:39:52.144 --> 20:39:52.810 align:start position:0% um just a brief overview really high availability 20:39:52.810 --> 20:39:52.820 align:start position:0% availability 20:39:52.820 --> 20:39:54.006 align:start position:0% availability [Music] 20:39:54.006 --> 20:39:54.016 align:start position:0% [Music] 20:39:54.016 --> 20:39:59.926 align:start position:0% [Music] vrrp<20:39:55.104> hsrp<20:39:56.360> load<20:39:57.360> balancing<20:39:58.280> and<20:39:59.280> high 20:39:59.926 --> 20:39:59.936 align:start position:0% vrrp hsrp load balancing and high 20:39:59.936 --> 20:40:02.750 align:start position:0% vrrp hsrp load balancing and high availability<20:40:00.504> this<20:40:01.504> refers<20:40:01.856> to<20:40:02.040> the<20:40:02.464> ability 20:40:02.750 --> 20:40:02.760 align:start position:0% availability this refers to the ability 20:40:02.760 --> 20:40:05.390 align:start position:0% availability this refers to the ability of<20:40:03.120> a<20:40:03.296> user<20:40:03.600> to<20:40:03.784> access<20:40:03.960> the<20:40:04.320> service<20:40:04.616> no 20:40:05.390 --> 20:40:05.400 align:start position:0% of a user to access the service no 20:40:05.400 --> 20:40:06.414 align:start position:0% of a user to access the service no surprise 20:40:06.414 --> 20:40:06.424 align:start position:0% surprise 20:40:06.424 --> 20:40:09.822 align:start position:0% surprise High<20:40:06.960> availability<20:40:07.376> is<20:40:08.160> a<20:40:08.576> common<20:40:09.000> networking 20:40:09.822 --> 20:40:09.832 align:start position:0% High availability is a common networking 20:40:09.832 --> 20:40:12.046 align:start position:0% High availability is a common networking term<20:40:10.080> it<20:40:10.616> refers<20:40:10.920> to<20:40:11.104> the<20:40:11.576> continuous 20:40:12.046 --> 20:40:12.056 align:start position:0% term it refers to the continuous 20:40:12.056 --> 20:40:14.326 align:start position:0% term it refers to the continuous availability<20:40:12.536> of<20:40:12.960> a<20:40:13.144> service 20:40:14.326 --> 20:40:14.336 align:start position:0% availability of a service 20:40:14.336 --> 20:40:17.750 align:start position:0% availability of a service for<20:40:15.296> a<20:40:15.424> higher<20:40:15.720> period<20:40:16.016> than<20:40:16.440> normal<20:40:16.800> now 20:40:17.750 --> 20:40:17.760 align:start position:0% for a higher period than normal now 20:40:17.760 --> 20:40:20.150 align:start position:0% for a higher period than normal now obviously<20:40:18.296> we're<20:40:18.480> looking<20:40:18.600> for<20:40:18.832> the<20:40:19.160> 99.99 20:40:20.150 --> 20:40:20.160 align:start position:0% obviously we're looking for the 99.99 20:40:20.160 --> 20:40:21.646 align:start position:0% obviously we're looking for the 99.99 percent 20:40:21.646 --> 20:40:21.656 align:start position:0% percent 20:40:21.656 --> 20:40:23.990 align:start position:0% percent in<20:40:22.440> order<20:40:22.552> to<20:40:22.800> get<20:40:22.976> the<20:40:23.216> highest<20:40:23.576> possible 20:40:23.990 --> 20:40:24.000 align:start position:0% in order to get the highest possible 20:40:24.000 --> 20:40:26.502 align:start position:0% in order to get the highest possible availability<20:40:24.536> we<20:40:25.440> usually<20:40:25.744> need<20:40:26.040> more<20:40:26.336> than 20:40:26.502 --> 20:40:26.512 align:start position:0% availability we usually need more than 20:40:26.512 --> 20:40:29.150 align:start position:0% availability we usually need more than one<20:40:26.872> other<20:40:27.600> thing 20:40:29.150 --> 20:40:29.160 align:start position:0% one other thing 20:40:29.160 --> 20:40:31.966 align:start position:0% one other thing for<20:40:29.640> example<20:40:30.424> um<20:40:30.424> some<20:40:30.784> Cisco<20:40:31.192> switches<20:40:31.680> come 20:40:31.966 --> 20:40:31.976 align:start position:0% for example um some Cisco switches come 20:40:31.976 --> 20:40:32.886 align:start position:0% for example um some Cisco switches come with 20:40:32.886 --> 20:40:32.896 align:start position:0% with 20:40:32.896 --> 20:40:35.862 align:start position:0% with to<20:40:33.896> power<20:40:34.680> supplies 20:40:35.862 --> 20:40:35.872 align:start position:0% to power supplies 20:40:35.872 --> 20:40:37.910 align:start position:0% to power supplies and<20:40:36.600> even 20:40:37.910 --> 20:40:37.920 align:start position:0% and even 20:40:37.920 --> 20:40:40.846 align:start position:0% and even even<20:40:38.640> this<20:40:39.000> has<20:40:39.424> been<20:40:39.656> improved<20:40:40.016> upon<20:40:40.376> so<20:40:40.552> they 20:40:40.846 --> 20:40:40.856 align:start position:0% even this has been improved upon so they 20:40:40.856 --> 20:40:42.886 align:start position:0% even this has been improved upon so they have<20:40:41.040> not<20:40:41.872> just<20:40:42.000> the<20:40:42.176> fact<20:40:42.360> they've<20:40:42.480> got<20:40:42.720> two 20:40:42.886 --> 20:40:42.896 align:start position:0% have not just the fact they've got two 20:40:42.896 --> 20:40:44.886 align:start position:0% have not just the fact they've got two power<20:40:43.144> supplies<20:40:43.616> but<20:40:43.856> they're<20:40:44.040> hot<20:40:44.216> swappable 20:40:44.886 --> 20:40:44.896 align:start position:0% power supplies but they're hot swappable 20:40:44.896 --> 20:40:47.390 align:start position:0% power supplies but they're hot swappable so<20:40:45.896> what<20:40:46.320> that<20:40:46.496> means<20:40:46.744> is<20:40:46.800> you<20:40:46.976> don't<20:40:47.104> need<20:40:47.280> to 20:40:47.390 --> 20:40:47.400 align:start position:0% so what that means is you don't need to 20:40:47.400 --> 20:40:49.734 align:start position:0% so what that means is you don't need to reboot<20:40:47.872> the<20:40:48.000> switch<20:40:48.176> you<20:40:48.536> can<20:40:48.720> pull<20:40:49.256> one<20:40:49.504> out 20:40:49.734 --> 20:40:49.744 align:start position:0% reboot the switch you can pull one out 20:40:49.744 --> 20:40:52.486 align:start position:0% reboot the switch you can pull one out the<20:40:50.216> inactive<20:40:50.936> one<20:40:51.120> and<20:40:51.896> then<20:40:52.016> slot<20:40:52.376> another 20:40:52.486 --> 20:40:52.496 align:start position:0% the inactive one and then slot another 20:40:52.496 --> 20:40:54.590 align:start position:0% the inactive one and then slot another one<20:40:52.800> in<20:40:53.040> and<20:40:53.464> then<20:40:53.576> you've<20:40:53.760> got<20:40:53.872> two<20:40:54.120> active 20:40:54.590 --> 20:40:54.600 align:start position:0% one in and then you've got two active 20:40:54.600 --> 20:40:59.750 align:start position:0% one in and then you've got two active power<20:40:54.960> supply<20:40:55.440> units<20:40:56.160> and<20:40:57.056> in<20:40:57.296> case<20:40:57.480> one<20:40:57.720> fails 20:40:59.750 --> 20:40:59.760 align:start position:0% power supply units and in case one fails 20:40:59.760 --> 20:41:01.734 align:start position:0% power supply units and in case one fails so<20:41:00.120> measured<20:41:00.536> as<20:41:00.656> a<20:41:00.832> percentage<20:41:01.144> of<20:41:01.320> uptime 20:41:01.734 --> 20:41:01.744 align:start position:0% so measured as a percentage of uptime 20:41:01.744 --> 20:41:04.862 align:start position:0% so measured as a percentage of uptime which<20:41:02.104> is<20:41:02.216> five<20:41:02.512> minutes<20:41:02.824> a<20:41:03.296> year 20:41:04.862 --> 20:41:04.872 align:start position:0% which is five minutes a year 20:41:04.872 --> 20:41:06.886 align:start position:0% which is five minutes a year uh<20:41:05.872> for<20:41:06.056> a<20:41:06.176> network<20:41:06.296> to<20:41:06.536> be<20:41:06.656> highly 20:41:06.886 --> 20:41:06.896 align:start position:0% uh for a network to be highly 20:41:06.896 --> 20:41:09.710 align:start position:0% uh for a network to be highly availability<20:41:07.376> it<20:41:07.856> should<20:41:08.040> survive<20:41:08.464> any<20:41:08.936> kind 20:41:09.710 --> 20:41:09.720 align:start position:0% availability it should survive any kind 20:41:09.720 --> 20:41:10.846 align:start position:0% availability it should survive any kind of<20:41:09.832> failure 20:41:10.846 --> 20:41:10.856 align:start position:0% of failure 20:41:10.856 --> 20:41:13.606 align:start position:0% of failure I'm<20:41:11.576> not<20:41:11.824> saying<20:41:12.296> there's<20:41:13.016> such<20:41:13.320> a<20:41:13.504> thing 20:41:13.606 --> 20:41:13.616 align:start position:0% I'm not saying there's such a thing 20:41:13.616 --> 20:41:16.070 align:start position:0% I'm not saying there's such a thing doesn't<20:41:13.856> exist<20:41:14.336> but<20:41:14.576> even<20:41:14.824> the<20:41:15.120> most<20:41:15.296> robust 20:41:16.070 --> 20:41:16.080 align:start position:0% doesn't exist but even the most robust 20:41:16.080 --> 20:41:18.230 align:start position:0% doesn't exist but even the most robust networks<20:41:16.496> there<20:41:16.680> was<20:41:16.856> a<20:41:16.976> recent<20:41:17.216> outage<20:41:17.696> due 20:41:18.230 --> 20:41:18.240 align:start position:0% networks there was a recent outage due 20:41:18.240 --> 20:41:19.070 align:start position:0% networks there was a recent outage due to 20:41:19.070 --> 20:41:19.080 align:start position:0% to 20:41:19.080 --> 20:41:22.182 align:start position:0% to um severe<20:41:20.040> flooding<20:41:20.576> in<20:41:21.424> Australia<20:41:21.896> I<20:41:22.080> think 20:41:22.182 --> 20:41:22.192 align:start position:0% um severe flooding in Australia I think 20:41:22.192 --> 20:41:23.630 align:start position:0% um severe flooding in Australia I think it<20:41:22.320> was<20:41:22.440> just<20:41:22.552> a<20:41:22.680> few<20:41:22.800> months<20:41:23.104> ago<20:41:23.336> where<20:41:23.464> it 20:41:23.630 --> 20:41:23.640 align:start position:0% it was just a few months ago where it 20:41:23.640 --> 20:41:27.590 align:start position:0% it was just a few months ago where it took<20:41:23.872> out<20:41:24.056> Amazon<20:41:25.336> uh<20:41:26.336> S3 20:41:27.590 --> 20:41:27.600 align:start position:0% took out Amazon uh S3 20:41:27.600 --> 20:41:30.166 align:start position:0% took out Amazon uh S3 service<20:41:28.256> so<20:41:29.104> which<20:41:29.400> you<20:41:29.640> would<20:41:29.824> think<20:41:30.000> would 20:41:30.166 --> 20:41:30.176 align:start position:0% service so which you would think would 20:41:30.176 --> 20:41:31.966 align:start position:0% service so which you would think would be<20:41:30.296> one<20:41:30.480> of<20:41:30.600> the<20:41:30.656> most<20:41:30.832> available<20:41:31.144> and<20:41:31.552> secure 20:41:31.966 --> 20:41:31.976 align:start position:0% be one of the most available and secure 20:41:31.976 --> 20:41:35.094 align:start position:0% be one of the most available and secure and<20:41:32.824> robust<20:41:33.296> uh<20:41:33.832> hosting<20:41:34.376> Platforms<20:41:34.800> in<20:41:34.920> the 20:41:35.094 --> 20:41:35.104 align:start position:0% and robust uh hosting Platforms in the 20:41:35.104 --> 20:41:36.526 align:start position:0% and robust uh hosting Platforms in the world<20:41:35.160> but<20:41:35.400> even<20:41:35.576> some<20:41:35.824> of<20:41:35.936> those<20:41:36.000> customers 20:41:36.526 --> 20:41:36.536 align:start position:0% world but even some of those customers 20:41:36.536 --> 20:41:38.094 align:start position:0% world but even some of those customers were<20:41:36.720> taken<20:41:37.080> out 20:41:38.094 --> 20:41:38.104 align:start position:0% were taken out 20:41:38.104 --> 20:41:40.734 align:start position:0% were taken out so<20:41:38.640> high<20:41:38.936> availability<20:41:39.720> can<20:41:40.080> be<20:41:40.192> achieved<20:41:40.552> by 20:41:40.734 --> 20:41:40.744 align:start position:0% so high availability can be achieved by 20:41:40.744 --> 20:41:42.350 align:start position:0% so high availability can be achieved by configuring<20:41:41.160> redundant<20:41:41.576> components<20:41:42.056> so<20:41:42.176> if 20:41:42.350 --> 20:41:42.360 align:start position:0% configuring redundant components so if 20:41:42.360 --> 20:41:44.566 align:start position:0% configuring redundant components so if one<20:41:42.536> one<20:41:42.784> part<20:41:43.016> of<20:41:43.144> it<20:41:43.256> fails<20:41:43.680> the<20:41:44.216> other<20:41:44.336> part 20:41:44.566 --> 20:41:44.576 align:start position:0% one one part of it fails the other part 20:41:44.576 --> 20:41:47.750 align:start position:0% one one part of it fails the other part takes<20:41:45.000> over 20:41:47.750 --> 20:41:47.760 align:start position:0% 20:41:47.760 --> 20:41:51.230 align:start position:0% now<20:41:48.360> in<20:41:48.600> the<20:41:48.784> context<20:41:49.080> of<20:41:49.504> a<20:41:49.800> routing<20:41:50.336> we've 20:41:51.230 --> 20:41:51.240 align:start position:0% now in the context of a routing we've 20:41:51.240 --> 20:41:54.166 align:start position:0% now in the context of a routing we've got<20:41:51.360> protocols<20:41:52.144> such<20:41:52.320> as<20:41:52.640> vrrp<20:41:53.640> Virtual 20:41:54.166 --> 20:41:54.176 align:start position:0% got protocols such as vrrp Virtual 20:41:54.176 --> 20:41:57.166 align:start position:0% got protocols such as vrrp Virtual Router<20:41:54.656> redundancy<20:41:55.192> protocol<20:41:55.552> and<20:41:56.464> hsrp 20:41:57.166 --> 20:41:57.176 align:start position:0% Router redundancy protocol and hsrp 20:41:57.176 --> 20:41:59.862 align:start position:0% Router redundancy protocol and hsrp which<20:41:57.480> is<20:41:57.536> done<20:41:58.016> by<20:41:58.256> router<20:41:58.680> protocol 20:41:59.862 --> 20:41:59.872 align:start position:0% which is done by router protocol 20:41:59.872 --> 20:42:03.046 align:start position:0% which is done by router protocol these<20:42:00.720> are<20:42:01.016> what<20:42:01.320> are<20:42:01.680> what<20:42:02.040> is<20:42:02.160> known<20:42:02.400> as<20:42:03.056> um 20:42:03.046 --> 20:42:03.056 align:start position:0% these are what are what is known as um 20:42:03.056 --> 20:42:07.006 align:start position:0% these are what are what is known as um High<20:42:03.656> availability<20:42:04.080> protocols 20:42:07.006 --> 20:42:07.016 align:start position:0% High availability protocols 20:42:07.016 --> 20:42:10.246 align:start position:0% High availability protocols these<20:42:07.680> enable<20:42:07.976> multiple<20:42:08.872> multiple<20:42:09.656> routers 20:42:10.246 --> 20:42:10.256 align:start position:0% these enable multiple multiple routers 20:42:10.256 --> 20:42:13.366 align:start position:0% these enable multiple multiple routers oral<20:42:11.160> layer<20:42:11.400> 3<20:42:11.512> switches<20:42:12.056> in<20:42:12.240> fact<20:42:12.424> to<20:42:12.960> act<20:42:13.192> as 20:42:13.366 --> 20:42:13.376 align:start position:0% oral layer 3 switches in fact to act as 20:42:13.376 --> 20:42:17.862 align:start position:0% oral layer 3 switches in fact to act as Virtual<20:42:13.800> Router<20:42:14.216> with<20:42:14.400> a<20:42:14.512> virtual<20:42:14.824> IP<20:42:15.120> address 20:42:17.862 --> 20:42:17.872 align:start position:0% 20:42:17.872 --> 20:42:19.910 align:start position:0% a<20:42:18.360> default<20:42:18.720> gateway<20:42:19.080> is<20:42:19.376> configured<20:42:19.744> with 20:42:19.910 --> 20:42:19.920 align:start position:0% a default gateway is configured with 20:42:19.920 --> 20:42:22.486 align:start position:0% a default gateway is configured with this<20:42:20.104> virtual<20:42:20.400> IP<20:42:20.696> address<20:42:20.936> so<20:42:21.832> one<20:42:22.080> router 20:42:22.486 --> 20:42:22.496 align:start position:0% this virtual IP address so one router 20:42:22.496 --> 20:42:24.230 align:start position:0% this virtual IP address so one router will<20:42:22.680> be<20:42:22.800> active<20:42:23.104> and<20:42:23.280> this<20:42:23.464> handles<20:42:23.824> all<20:42:24.056> the 20:42:24.230 --> 20:42:24.240 align:start position:0% will be active and this handles all the 20:42:24.240 --> 20:42:26.454 align:start position:0% will be active and this handles all the requests<20:42:24.536> to<20:42:24.656> the<20:42:24.832> default<20:42:25.144> gateway<20:42:25.616> and<20:42:26.280> the 20:42:26.454 --> 20:42:26.464 align:start position:0% requests to the default gateway and the 20:42:26.464 --> 20:42:28.366 align:start position:0% requests to the default gateway and the other<20:42:26.512> router<20:42:26.872> will<20:42:27.056> be<20:42:27.176> a<20:42:27.296> standby<20:42:27.656> so<20:42:28.192> the 20:42:28.366 --> 20:42:28.376 align:start position:0% other router will be a standby so the 20:42:28.376 --> 20:42:30.350 align:start position:0% other router will be a standby so the other<20:42:28.496> router<20:42:28.976> actually<20:42:29.160> takes<20:42:29.576> over<20:42:29.760> if<20:42:30.176> the 20:42:30.350 --> 20:42:30.360 align:start position:0% other router actually takes over if the 20:42:30.360 --> 20:42:32.390 align:start position:0% other router actually takes over if the main<20:42:30.424> router<20:42:30.832> goes<20:42:31.192> down<20:42:31.320> now<20:42:31.920> this<20:42:32.160> isn't 20:42:32.390 --> 20:42:32.400 align:start position:0% main router goes down now this isn't 20:42:32.400 --> 20:42:34.670 align:start position:0% main router goes down now this isn't load<20:42:32.696> balancing<20:42:33.176> because<20:42:34.016> um<20:42:34.016> you've<20:42:34.320> got<20:42:34.440> one 20:42:34.670 --> 20:42:34.680 align:start position:0% load balancing because um you've got one 20:42:34.680 --> 20:42:37.070 align:start position:0% load balancing because um you've got one master<20:42:34.856> router<20:42:35.576> and<20:42:36.240> the<20:42:36.424> other<20:42:36.536> one<20:42:36.720> is<20:42:36.832> a 20:42:37.070 --> 20:42:37.080 align:start position:0% master router and the other one is a 20:42:37.080 --> 20:42:39.286 align:start position:0% master router and the other one is a slave<20:42:37.376> or<20:42:37.616> backup<20:42:37.976> depending<20:42:38.576> on<20:42:38.824> the 20:42:39.286 --> 20:42:39.296 align:start position:0% slave or backup depending on the 20:42:39.296 --> 20:42:41.326 align:start position:0% slave or backup depending on the protocol<20:42:39.600> you<20:42:39.960> use<20:42:40.144> they<20:42:40.920> have<20:42:41.040> different 20:42:41.326 --> 20:42:41.336 align:start position:0% protocol you use they have different 20:42:41.336 --> 20:42:45.230 align:start position:0% protocol you use they have different terms<20:42:41.872> so<20:42:42.832> here's<20:42:43.320> an<20:42:43.440> image<20:42:43.744> of<20:42:44.040> uh<20:42:44.512> the<20:42:44.824> Cisco 20:42:45.230 --> 20:42:45.240 align:start position:0% terms so here's an image of uh the Cisco 20:42:45.240 --> 20:42:47.566 align:start position:0% terms so here's an image of uh the Cisco hot<20:42:45.600> standby<20:42:45.960> router<20:42:46.376> protocol 20:42:47.566 --> 20:42:47.576 align:start position:0% hot standby router protocol 20:42:47.576 --> 20:42:50.326 align:start position:0% hot standby router protocol at<20:42:48.240> the<20:42:48.360> top<20:42:48.536> you<20:42:48.896> with<20:42:49.320> the<20:42:49.504> red<20:42:49.680> and<20:42:49.976> the<20:42:50.160> blue 20:42:50.326 --> 20:42:50.336 align:start position:0% at the top you with the red and the blue 20:42:50.336 --> 20:42:53.150 align:start position:0% at the top you with the red and the blue you<20:42:50.576> got<20:42:50.824> a<20:42:51.000> layer<20:42:51.360> 3<20:42:51.480> switch 20:42:53.150 --> 20:42:53.160 align:start position:0% you got a layer 3 switch 20:42:53.160 --> 20:42:56.502 align:start position:0% you got a layer 3 switch it<20:42:53.640> should<20:42:53.824> be<20:42:53.936> another<20:42:54.056> there<20:42:54.480> we<20:42:54.720> go 20:42:56.502 --> 20:42:56.512 align:start position:0% it should be another there we go 20:42:56.512 --> 20:43:00.046 align:start position:0% it should be another there we go so<20:42:57.296> uh<20:42:58.080> we'll<20:42:58.256> see<20:42:58.496> you<20:42:59.216> see<20:42:59.464> the<20:42:59.576> host<20:42:59.696> on<20:42:59.936> the 20:43:00.046 --> 20:43:00.056 align:start position:0% so uh we'll see you see the host on the 20:43:00.056 --> 20:43:02.814 align:start position:0% so uh we'll see you see the host on the bottom<20:43:00.360> they<20:43:00.960> both<20:43:01.080> have<20:43:01.320> the<20:43:01.552> same<20:43:01.680> default 20:43:02.814 --> 20:43:02.824 align:start position:0% bottom they both have the same default 20:43:02.824 --> 20:43:07.814 align:start position:0% bottom they both have the same default Gateway<20:43:03.536> the<20:43:04.144> Gateway<20:43:04.440> is<20:43:05.120> 10.10.10.1<20:43:06.120> now 20:43:07.814 --> 20:43:07.824 align:start position:0% Gateway the Gateway is 10.10.10.1 now 20:43:07.824 --> 20:43:11.206 align:start position:0% Gateway the Gateway is 10.10.10.1 now 10.10.10.1<20:43:08.824> is<20:43:09.240> configured<20:43:09.784> as<20:43:09.960> a<20:43:10.256> virtual<20:43:10.680> IP 20:43:11.206 --> 20:43:11.216 align:start position:0% 10.10.10.1 is configured as a virtual IP 20:43:11.216 --> 20:43:14.094 align:start position:0% 10.10.10.1 is configured as a virtual IP address<20:43:11.600> on<20:43:12.600> the<20:43:12.720> two<20:43:12.960> layer<20:43:13.376> three<20:43:13.552> devices 20:43:14.094 --> 20:43:14.104 align:start position:0% address on the two layer three devices 20:43:14.104 --> 20:43:15.526 align:start position:0% address on the two layer three devices on<20:43:14.464> the<20:43:14.576> top 20:43:15.526 --> 20:43:15.536 align:start position:0% on the top 20:43:15.536 --> 20:43:18.414 align:start position:0% on the top these<20:43:16.192> two<20:43:16.320> devices<20:43:16.744> are<20:43:17.400> connected<20:43:17.872> and<20:43:18.240> they 20:43:18.414 --> 20:43:18.424 align:start position:0% these two devices are connected and they 20:43:18.424 --> 20:43:20.630 align:start position:0% these two devices are connected and they monitor<20:43:18.832> each<20:43:19.016> other<20:43:19.192> so<20:43:19.856> if<20:43:20.104> one<20:43:20.280> goes<20:43:20.576> down 20:43:20.630 --> 20:43:20.640 align:start position:0% monitor each other so if one goes down 20:43:20.640 --> 20:43:23.502 align:start position:0% monitor each other so if one goes down the<20:43:20.936> other<20:43:21.056> one<20:43:21.240> takes<20:43:21.600> over<20:43:21.976> you<20:43:22.976> see<20:43:23.160> the 20:43:23.502 --> 20:43:23.512 align:start position:0% the other one takes over you see the 20:43:23.512 --> 20:43:26.326 align:start position:0% the other one takes over you see the priority<20:43:23.936> on<20:43:24.424> the<20:43:24.720> right<20:43:25.256> hand<20:43:25.440> switch<20:43:25.680> is<20:43:25.976> 100 20:43:26.326 --> 20:43:26.336 align:start position:0% priority on the right hand switch is 100 20:43:26.336 --> 20:43:29.326 align:start position:0% priority on the right hand switch is 100 the<20:43:27.176> priority<20:43:27.536> on<20:43:27.960> the<20:43:28.144> left<20:43:28.320> hand<20:43:28.496> switch<20:43:28.856> is 20:43:29.326 --> 20:43:29.336 align:start position:0% the priority on the left hand switch is 20:43:29.336 --> 20:43:32.502 align:start position:0% the priority on the left hand switch is 105<20:43:29.936> so<20:43:30.424> it's<20:43:30.536> got<20:43:30.720> a<20:43:30.896> higher<20:43:31.192> priority<20:43:31.552> so 20:43:32.502 --> 20:43:32.512 align:start position:0% 105 so it's got a higher priority so 20:43:32.512 --> 20:43:35.094 align:start position:0% 105 so it's got a higher priority so this<20:43:32.760> one<20:43:32.936> in<20:43:33.360> the<20:43:33.480> case<20:43:33.600> of<20:43:33.784> hsrp<20:43:34.440> will<20:43:34.744> be<20:43:34.920> the 20:43:35.094 --> 20:43:35.104 align:start position:0% this one in the case of hsrp will be the 20:43:35.104 --> 20:43:37.734 align:start position:0% this one in the case of hsrp will be the primary<20:43:35.512> router 20:43:37.734 --> 20:43:37.744 align:start position:0% primary router 20:43:37.744 --> 20:43:40.910 align:start position:0% primary router uh<20:43:38.336> all<20:43:38.512> traffic<20:43:38.760> will<20:43:39.176> go<20:43:39.536> via<20:43:40.144> this<20:43:40.440> router 20:43:40.910 --> 20:43:40.920 align:start position:0% uh all traffic will go via this router 20:43:40.920 --> 20:43:43.366 align:start position:0% uh all traffic will go via this router until<20:43:41.872> there's<20:43:42.360> an<20:43:42.480> issue<20:43:42.720> with<20:43:42.896> it<20:43:43.016> if<20:43:43.192> it 20:43:43.366 --> 20:43:43.376 align:start position:0% until there's an issue with it if it 20:43:43.376 --> 20:43:45.046 align:start position:0% until there's an issue with it if it goes<20:43:43.616> down<20:43:43.744> then<20:43:43.976> all<20:43:44.216> traffic<20:43:44.400> immediately 20:43:45.046 --> 20:43:45.056 align:start position:0% goes down then all traffic immediately 20:43:45.056 --> 20:43:48.470 align:start position:0% goes down then all traffic immediately in<20:43:45.360> a<20:43:45.784> split<20:43:46.016> second<20:43:46.464> swaps<20:43:47.464> to<20:43:47.640> the<20:43:47.824> standby 20:43:48.470 --> 20:43:48.480 align:start position:0% in a split second swaps to the standby 20:43:48.480 --> 20:43:50.990 align:start position:0% in a split second swaps to the standby router<20:43:48.960> which<20:43:49.144> is<20:43:49.256> on<20:43:49.440> the<20:43:49.552> rides<20:43:50.400> they<20:43:50.824> both 20:43:50.990 --> 20:43:51.000 align:start position:0% router which is on the rides they both 20:43:51.000 --> 20:43:53.206 align:start position:0% router which is on the rides they both run<20:43:51.240> a<20:43:51.600> virtual<20:43:51.896> Mac<20:43:52.080> address<20:43:52.320> we<20:43:52.920> don't<20:43:53.040> need 20:43:53.206 --> 20:43:53.216 align:start position:0% run a virtual Mac address we don't need 20:43:53.216 --> 20:43:54.166 align:start position:0% run a virtual Mac address we don't need to<20:43:53.280> worry<20:43:53.400> about<20:43:53.512> that<20:43:53.760> because<20:43:53.936> I<20:43:54.056> don't 20:43:54.166 --> 20:43:54.176 align:start position:0% to worry about that because I don't 20:43:54.176 --> 20:43:55.430 align:start position:0% to worry about that because I don't think<20:43:54.296> it'd<20:43:54.600> be<20:43:54.656> asked<20:43:54.896> but<20:43:55.016> they<20:43:55.144> run<20:43:55.256> a 20:43:55.430 --> 20:43:55.440 align:start position:0% think it'd be asked but they run a 20:43:55.440 --> 20:43:58.790 align:start position:0% think it'd be asked but they run a virtual<20:43:55.616> Mac<20:43:55.856> address<20:43:56.120> so<20:43:57.120> that<20:43:57.896> um<20:43:57.960> a<20:43:58.376> layer<20:43:58.616> 2 20:43:58.790 --> 20:43:58.800 align:start position:0% virtual Mac address so that um a layer 2 20:43:58.800 --> 20:44:01.390 align:start position:0% virtual Mac address so that um a layer 2 connectivity<20:43:59.280> works<20:43:59.760> also 20:44:01.390 --> 20:44:01.400 align:start position:0% connectivity works also 20:44:01.400 --> 20:44:03.646 align:start position:0% connectivity works also I<20:44:02.400> think<20:44:02.576> that's<20:44:02.696> all<20:44:02.936> we<20:44:03.056> need<20:44:03.240> to<20:44:03.360> know<20:44:03.536> about 20:44:03.646 --> 20:44:03.656 align:start position:0% I think that's all we need to know about 20:44:03.656 --> 20:44:06.646 align:start position:0% I think that's all we need to know about this<20:44:04.080> diagram 20:44:06.646 --> 20:44:06.656 align:start position:0% 20:44:06.656 --> 20:44:10.246 align:start position:0% load<20:44:07.320> balancing<20:44:07.744> is<20:44:08.400> a<20:44:09.120> distribution<20:44:09.720> of<20:44:09.960> work 20:44:10.246 --> 20:44:10.256 align:start position:0% load balancing is a distribution of work 20:44:10.256 --> 20:44:13.070 align:start position:0% load balancing is a distribution of work across<20:44:11.104> two<20:44:11.640> or<20:44:11.824> more<20:44:12.000> resources<20:44:12.536> such<20:44:12.832> as 20:44:13.070 --> 20:44:13.080 align:start position:0% across two or more resources such as 20:44:13.080 --> 20:44:15.710 align:start position:0% across two or more resources such as servers<20:44:13.616> and<20:44:14.216> networks<20:44:14.760> if<20:44:15.296> you<20:44:15.424> have<20:44:15.600> a 20:44:15.710 --> 20:44:15.720 align:start position:0% servers and networks if you have a 20:44:15.720 --> 20:44:17.502 align:start position:0% servers and networks if you have a server<20:44:16.016> overloaded<20:44:16.680> with<20:44:16.856> requests<20:44:17.216> then<20:44:17.336> we 20:44:17.502 --> 20:44:17.512 align:start position:0% server overloaded with requests then we 20:44:17.512 --> 20:44:19.246 align:start position:0% server overloaded with requests then we can<20:44:17.640> have<20:44:17.760> several<20:44:18.120> servers<20:44:18.600> share<20:44:18.896> the 20:44:19.246 --> 20:44:19.256 align:start position:0% can have several servers share the 20:44:19.256 --> 20:44:21.414 align:start position:0% can have several servers share the burden<20:44:19.552> of<20:44:19.680> that<20:44:19.856> single<20:44:20.216> server<20:44:20.576> in<20:44:21.296> fact 20:44:21.414 --> 20:44:21.424 align:start position:0% burden of that single server in fact 20:44:21.424 --> 20:44:23.862 align:start position:0% burden of that single server in fact even<20:44:21.720> better<20:44:21.896> than<20:44:22.144> that<20:44:22.320> you<20:44:22.616> can 20:44:23.862 --> 20:44:23.872 align:start position:0% even better than that you can 20:44:23.872 --> 20:44:26.926 align:start position:0% even better than that you can um<20:44:24.000> it<20:44:24.600> will<20:44:24.960> it<20:44:25.144> can<20:44:25.320> work<20:44:25.552> so<20:44:25.920> that<20:44:26.216> the<20:44:26.512> load 20:44:26.926 --> 20:44:26.936 align:start position:0% um it will it can work so that the load 20:44:26.936 --> 20:44:28.790 align:start position:0% um it will it can work so that the load is<20:44:27.056> balanced<20:44:27.536> automatically<20:44:28.256> so<20:44:28.552> you<20:44:28.680> don't 20:44:28.790 --> 20:44:28.800 align:start position:0% is balanced automatically so you don't 20:44:28.800 --> 20:44:30.286 align:start position:0% is balanced automatically so you don't have<20:44:28.920> to<20:44:29.040> wait<20:44:29.216> till<20:44:29.400> one<20:44:29.640> server<20:44:30.000> to<20:44:30.176> be 20:44:30.286 --> 20:44:30.296 align:start position:0% have to wait till one server to be 20:44:30.296 --> 20:44:33.166 align:start position:0% have to wait till one server to be overloaded<20:44:30.896> the<20:44:31.552> load<20:44:31.920> is<20:44:32.040> shared<20:44:32.696> over<20:44:32.824> two 20:44:33.166 --> 20:44:33.176 align:start position:0% overloaded the load is shared over two 20:44:33.176 --> 20:44:36.230 align:start position:0% overloaded the load is shared over two or<20:44:33.360> more<20:44:33.536> servers 20:44:36.230 --> 20:44:36.240 align:start position:0% 20:44:36.240 --> 20:44:38.030 align:start position:0% now<20:44:36.784> the<20:44:37.016> other<20:44:37.144> thing<20:44:37.376> is<20:44:37.504> just<20:44:37.744> going<20:44:37.856> back 20:44:38.030 --> 20:44:38.040 align:start position:0% now the other thing is just going back 20:44:38.040 --> 20:44:39.886 align:start position:0% now the other thing is just going back to<20:44:38.160> that<20:44:38.336> last<20:44:38.464> point<20:44:38.760> the<20:44:39.360> servers<20:44:39.784> are 20:44:39.886 --> 20:44:39.896 align:start position:0% to that last point the servers are 20:44:39.896 --> 20:44:41.750 align:start position:0% to that last point the servers are acting<20:44:40.192> as<20:44:40.440> a<20:44:40.552> single<20:44:40.800> server<20:44:41.160> so<20:44:41.336> devices 20:44:41.750 --> 20:44:41.760 align:start position:0% acting as a single server so devices 20:44:41.760 --> 20:44:43.670 align:start position:0% acting as a single server so devices don't<20:44:42.120> realize<20:44:42.536> that<20:44:42.784> load<20:44:43.080> balancing<20:44:43.440> is 20:44:43.670 --> 20:44:43.680 align:start position:0% don't realize that load balancing is 20:44:43.680 --> 20:44:46.486 align:start position:0% don't realize that load balancing is taking<20:44:43.856> place<20:44:44.216> the<20:44:45.176> servers<20:44:45.536> are<20:44:45.656> acting<20:44:45.960> as<20:44:46.256> a 20:44:46.486 --> 20:44:46.496 align:start position:0% taking place the servers are acting as a 20:44:46.496 --> 20:44:48.822 align:start position:0% taking place the servers are acting as a group<20:44:46.744> of<20:44:46.976> servers<20:44:47.464> with<20:44:47.936> the<20:44:48.120> actual<20:44:48.360> hosts 20:44:48.822 --> 20:44:48.832 align:start position:0% group of servers with the actual hosts 20:44:48.832 --> 20:44:50.390 align:start position:0% group of servers with the actual hosts that<20:44:48.960> are<20:44:49.080> contacting<20:44:49.504> their<20:44:49.744> services<20:44:49.920> on 20:44:50.390 --> 20:44:50.400 align:start position:0% that are contacting their services on 20:44:50.400 --> 20:44:52.670 align:start position:0% that are contacting their services on these<20:44:50.576> servers<20:44:50.936> for<20:44:51.176> example 20:44:52.670 --> 20:44:52.680 align:start position:0% these servers for example 20:44:52.680 --> 20:44:55.542 align:start position:0% these servers for example um surfing<20:44:53.160> a<20:44:53.336> web<20:44:53.512> site<20:44:54.176> and<20:44:54.960> doesn't<20:44:55.192> don't 20:44:55.542 --> 20:44:55.552 align:start position:0% um surfing a web site and doesn't don't 20:44:55.552 --> 20:44:57.414 align:start position:0% um surfing a web site and doesn't don't realize<20:44:55.976> then<20:44:56.336> load<20:44:56.696> balancing<20:44:57.056> is<20:44:57.176> taking 20:44:57.414 --> 20:44:57.424 align:start position:0% realize then load balancing is taking 20:44:57.424 --> 20:44:58.486 align:start position:0% realize then load balancing is taking place 20:44:58.486 --> 20:44:58.496 align:start position:0% place 20:44:58.496 --> 20:45:00.350 align:start position:0% place so<20:44:58.856> here's<20:44:59.104> an<20:44:59.216> image<20:44:59.464> of<20:44:59.640> load<20:45:00.000> balancing 20:45:00.350 --> 20:45:00.360 align:start position:0% so here's an image of load balancing 20:45:00.360 --> 20:45:03.414 align:start position:0% so here's an image of load balancing you've<20:45:00.656> got<20:45:00.720> two<20:45:01.016> load<20:45:01.440> balances<20:45:01.856> here<20:45:02.160> so<20:45:03.120> one 20:45:03.414 --> 20:45:03.424 align:start position:0% you've got two load balances here so one 20:45:03.424 --> 20:45:04.542 align:start position:0% you've got two load balances here so one would<20:45:03.656> be 20:45:04.542 --> 20:45:04.552 align:start position:0% would be 20:45:04.552 --> 20:45:07.670 align:start position:0% would be um<20:45:04.616> redundant<20:45:05.576> or<20:45:05.936> possibly<20:45:06.360> taking<20:45:06.720> a<20:45:07.376> part 20:45:07.670 --> 20:45:07.680 align:start position:0% um redundant or possibly taking a part 20:45:07.680 --> 20:45:09.526 align:start position:0% um redundant or possibly taking a part of<20:45:07.800> the<20:45:07.920> load<20:45:08.216> from<20:45:08.400> the<20:45:08.576> other<20:45:08.696> one 20:45:09.526 --> 20:45:09.536 align:start position:0% of the load from the other one 20:45:09.536 --> 20:45:12.646 align:start position:0% of the load from the other one and<20:45:10.376> then<20:45:10.552> we've<20:45:11.160> got<20:45:11.336> an<20:45:11.760> array<20:45:12.056> of<20:45:12.240> servers 20:45:12.646 --> 20:45:12.656 align:start position:0% and then we've got an array of servers 20:45:12.656 --> 20:45:14.686 align:start position:0% and then we've got an array of servers providing<20:45:13.192> whichever<20:45:13.616> Services<20:45:13.976> they<20:45:14.512> they 20:45:14.686 --> 20:45:14.696 align:start position:0% providing whichever Services they they 20:45:14.696 --> 20:45:18.414 align:start position:0% providing whichever Services they they may<20:45:14.936> be<20:45:15.192> FTP<20:45:16.192> or<20:45:16.616> web<20:45:16.976> services 20:45:18.414 --> 20:45:18.424 align:start position:0% may be FTP or web services 20:45:18.424 --> 20:45:22.366 align:start position:0% may be FTP or web services so<20:45:19.144> load<20:45:19.976> is<20:45:20.104> distributed<20:45:20.760> uh<20:45:21.536> across<20:45:22.256> the 20:45:22.366 --> 20:45:22.376 align:start position:0% so load is distributed uh across the 20:45:22.376 --> 20:45:24.526 align:start position:0% so load is distributed uh across the servers<20:45:22.800> they'll<20:45:23.104> all<20:45:23.216> have<20:45:23.464> the<20:45:23.640> same<20:45:23.824> IP 20:45:24.526 --> 20:45:24.536 align:start position:0% servers they'll all have the same IP 20:45:24.536 --> 20:45:25.606 align:start position:0% servers they'll all have the same IP address 20:45:25.606 --> 20:45:25.616 align:start position:0% address 20:45:25.616 --> 20:45:27.886 align:start position:0% address and<20:45:26.576> if<20:45:26.696> there's<20:45:26.936> a<20:45:27.120> problem<20:45:27.240> with<20:45:27.480> one<20:45:27.656> of<20:45:27.832> the 20:45:27.886 --> 20:45:27.896 align:start position:0% and if there's a problem with one of the 20:45:27.896 --> 20:45:29.566 align:start position:0% and if there's a problem with one of the servers<20:45:28.320> that<20:45:28.440> will<20:45:28.680> be<20:45:28.856> removed<20:45:29.336> from 20:45:29.566 --> 20:45:29.576 align:start position:0% servers that will be removed from 20:45:29.576 --> 20:45:32.390 align:start position:0% servers that will be removed from rotation<20:45:30.056> if<20:45:30.784> they're<20:45:30.960> not<20:45:31.144> responding<20:45:31.680> I 20:45:32.390 --> 20:45:32.400 align:start position:0% rotation if they're not responding I 20:45:32.400 --> 20:45:33.470 align:start position:0% rotation if they're not responding I presume<20:45:32.760> you'll<20:45:32.872> have<20:45:33.000> some<20:45:33.176> sort<20:45:33.360> of 20:45:33.470 --> 20:45:33.480 align:start position:0% presume you'll have some sort of 20:45:33.480 --> 20:45:35.030 align:start position:0% presume you'll have some sort of reporting<20:45:33.896> software<20:45:34.320> that<20:45:34.496> will<20:45:34.680> send<20:45:34.856> a 20:45:35.030 --> 20:45:35.040 align:start position:0% reporting software that will send a 20:45:35.040 --> 20:45:37.310 align:start position:0% reporting software that will send a message<20:45:35.160> to<20:45:35.464> the<20:45:35.576> administrator<20:45:36.056> saying<20:45:36.656> one 20:45:37.310 --> 20:45:37.320 align:start position:0% message to the administrator saying one 20:45:37.320 --> 20:45:38.814 align:start position:0% message to the administrator saying one of<20:45:37.440> the<20:45:37.552> servers<20:45:37.920> has<20:45:38.104> been<20:45:38.280> taken<20:45:38.512> out<20:45:38.640> of 20:45:38.814 --> 20:45:38.824 align:start position:0% of the servers has been taken out of 20:45:38.824 --> 20:45:41.390 align:start position:0% of the servers has been taken out of rotation<20:45:39.240> so<20:45:39.832> that<20:45:39.960> can<20:45:40.144> be<20:45:40.192> looked<20:45:40.552> into 20:45:41.390 --> 20:45:41.400 align:start position:0% rotation so that can be looked into 20:45:41.400 --> 20:45:44.094 align:start position:0% rotation so that can be looked into some<20:45:41.936> of<20:45:42.056> the<20:45:42.176> benefits<20:45:42.856> optimization<20:45:43.856> of 20:45:44.094 --> 20:45:44.104 align:start position:0% some of the benefits optimization of 20:45:44.104 --> 20:45:46.606 align:start position:0% some of the benefits optimization of resources<20:45:44.696> you<20:45:45.600> get<20:45:45.720> faster<20:45:46.016> throughput 20:45:46.606 --> 20:45:46.616 align:start position:0% resources you get faster throughput 20:45:46.616 --> 20:45:48.710 align:start position:0% resources you get faster throughput obviously<20:45:47.216> requires<20:45:47.640> careful<20:45:48.000> planning<20:45:48.424> for 20:45:48.710 --> 20:45:48.720 align:start position:0% obviously requires careful planning for 20:45:48.720 --> 20:45:52.006 align:start position:0% obviously requires careful planning for all<20:45:48.896> your<20:45:49.080> bandwidth<20:45:49.920> efficiency 20:45:52.006 --> 20:45:52.016 align:start position:0% all your bandwidth efficiency 20:45:52.016 --> 20:45:53.862 align:start position:0% all your bandwidth efficiency High<20:45:52.496> availability<20:45:52.920> which<20:45:53.400> is<20:45:53.512> the<20:45:53.696> whole 20:45:53.862 --> 20:45:53.872 align:start position:0% High availability which is the whole 20:45:53.872 --> 20:45:55.966 align:start position:0% High availability which is the whole point<20:45:54.120> of<20:45:54.296> the<20:45:54.480> presentation<20:45:54.896> so<20:45:55.800> we've 20:45:55.966 --> 20:45:55.976 align:start position:0% point of the presentation so we've 20:45:55.976 --> 20:45:58.430 align:start position:0% point of the presentation so we've looked<20:45:56.216> at<20:45:56.280> high<20:45:56.512> availability<20:45:57.000> two<20:45:57.960> types<20:45:58.320> of 20:45:58.430 --> 20:45:58.440 align:start position:0% looked at high availability two types of 20:45:58.440 --> 20:46:02.206 align:start position:0% looked at high availability two types of protocols<20:45:59.656> vrrp<20:46:00.656> and<20:46:00.832> hsrp 20:46:02.206 --> 20:46:02.216 align:start position:0% protocols vrrp and hsrp 20:46:02.216 --> 20:46:04.734 align:start position:0% protocols vrrp and hsrp low<20:46:02.696> balancing<20:46:03.240> all<20:46:04.016> right<20:46:04.144> that's<20:46:04.320> all<20:46:04.552> for 20:46:04.734 --> 20:46:04.744 align:start position:0% low balancing all right that's all for 20:46:04.744 --> 20:46:11.190 align:start position:0% low balancing all right that's all for now<20:46:04.856> thanks<20:46:05.160> for<20:46:05.336> watching 20:46:11.190 --> 20:46:11.200 align:start position:0% 20:46:11.200 --> 20:46:20.526 align:start position:0% [Music] 20:46:20.526 --> 20:46:20.536 align:start position:0% 20:46:20.536 --> 20:46:27.414 align:start position:0% thank<20:46:21.536> you 20:46:27.414 --> 20:46:27.424 align:start position:0% 20:46:27.424 --> 20:46:29.990 align:start position:0% welcome<20:46:27.960> to<20:46:28.192> module<20:46:28.552> 15<20:46:28.744> lesson<20:46:29.464> 3<20:46:29.640> we're 20:46:29.990 --> 20:46:30.000 align:start position:0% welcome to module 15 lesson 3 we're 20:46:30.000 --> 20:46:34.966 align:start position:0% welcome to module 15 lesson 3 we're looking<20:46:30.120> at<20:46:30.360> SNMP<20:46:31.016> syslog<20:46:31.800> and<20:46:32.104> s-i-e-m 20:46:34.966 --> 20:46:34.976 align:start position:0% looking at SNMP syslog and s-i-e-m 20:46:34.976 --> 20:46:38.814 align:start position:0% looking at SNMP syslog and s-i-e-m these<20:46:35.824> are<20:46:36.000> exam<20:46:36.600> objectives 20:46:38.814 --> 20:46:38.824 align:start position:0% these are exam objectives 20:46:38.824 --> 20:46:40.542 align:start position:0% these are exam objectives you<20:46:39.296> could<20:46:39.360> go<20:46:39.480> into<20:46:39.600> each<20:46:39.832> of<20:46:40.016> these<20:46:40.144> subjects 20:46:40.542 --> 20:46:40.552 align:start position:0% you could go into each of these subjects 20:46:40.552 --> 20:46:41.926 align:start position:0% you could go into each of these subjects in<20:46:40.680> quite<20:46:40.856> a<20:46:41.040> lot<20:46:41.160> of<20:46:41.280> detail<20:46:41.640> actually 20:46:41.926 --> 20:46:41.936 align:start position:0% in quite a lot of detail actually 20:46:41.936 --> 20:46:45.414 align:start position:0% in quite a lot of detail actually there's<20:46:42.536> the<20:46:42.784> entire<20:46:42.960> book<20:46:43.144> so<20:46:43.376> that's<20:46:43.616> an<20:46:43.800> MP 20:46:45.414 --> 20:46:45.424 align:start position:0% there's the entire book so that's an MP 20:46:45.424 --> 20:46:48.886 align:start position:0% there's the entire book so that's an MP which<20:46:46.552> um<20:46:46.552> we<20:46:47.104> won't<20:46:47.280> we'll<20:46:47.640> only<20:46:47.696> be<20:46:47.936> doing<20:46:48.240> an 20:46:48.886 --> 20:46:48.896 align:start position:0% which um we won't we'll only be doing an 20:46:48.896 --> 20:46:50.990 align:start position:0% which um we won't we'll only be doing an overview<20:46:49.320> so<20:46:49.616> you're<20:46:49.800> familiar<20:46:50.104> with<20:46:50.280> the 20:46:50.990 --> 20:46:51.000 align:start position:0% overview so you're familiar with the 20:46:51.000 --> 20:46:54.646 align:start position:0% overview so you're familiar with the the<20:46:51.552> terms<20:46:52.552> used<20:46:53.104> we'll<20:46:53.872> talk<20:46:54.120> about<20:46:54.240> these 20:46:54.646 --> 20:46:54.656 align:start position:0% the terms used we'll talk about these 20:46:54.656 --> 20:46:56.454 align:start position:0% the terms used we'll talk about these services 20:46:56.454 --> 20:46:56.464 align:start position:0% services 20:46:56.464 --> 20:46:59.990 align:start position:0% services Harrison<20:46:57.240> MP<20:46:57.600> Works<20:46:58.016> email<20:46:58.192> Cinemas<20:46:59.040> SMS 20:46:59.990 --> 20:47:00.000 align:start position:0% Harrison MP Works email Cinemas SMS 20:47:00.000 --> 20:47:01.094 align:start position:0% Harrison MP Works email Cinemas SMS alerting 20:47:01.094 --> 20:47:01.104 align:start position:0% alerting 20:47:01.104 --> 20:47:04.846 align:start position:0% alerting syslogs<20:47:02.104> and<20:47:02.160> the<20:47:02.280> benefits<20:47:02.760> and<20:47:02.936> Siem<20:47:03.856> SNMP 20:47:04.846 --> 20:47:04.856 align:start position:0% syslogs and the benefits and Siem SNMP 20:47:04.856 --> 20:47:08.150 align:start position:0% syslogs and the benefits and Siem SNMP you'll<20:47:05.400> be<20:47:05.640> referring<20:47:06.600> to<20:47:06.832> a<20:47:07.016> fair<20:47:07.320> amount<20:47:07.680> as 20:47:08.150 --> 20:47:08.160 align:start position:0% you'll be referring to a fair amount as 20:47:08.160 --> 20:47:10.670 align:start position:0% you'll be referring to a fair amount as a<20:47:08.464> network<20:47:08.576> engineer<20:47:09.176> a<20:47:09.424> guess<20:47:09.600> I<20:47:09.896> get<20:47:10.080> it<20:47:10.496> just 20:47:10.670 --> 20:47:10.680 align:start position:0% a network engineer a guess I get it just 20:47:10.680 --> 20:47:12.710 align:start position:0% a network engineer a guess I get it just depends<20:47:10.920> on<20:47:11.104> your<20:47:11.216> network<20:47:11.480> some<20:47:12.480> of<20:47:12.656> the 20:47:12.710 --> 20:47:12.720 align:start position:0% depends on your network some of the 20:47:12.720 --> 20:47:17.502 align:start position:0% depends on your network some of the larger<20:47:13.016> networks<20:47:13.552> I've<20:47:14.040> worked<20:47:14.760> uh<20:47:15.720> on<20:47:17.104> you 20:47:17.502 --> 20:47:17.512 align:start position:0% larger networks I've worked uh on you 20:47:17.512 --> 20:47:19.790 align:start position:0% larger networks I've worked uh on you actually<20:47:17.696> have<20:47:18.000> a<20:47:18.240> team<20:47:18.424> that<20:47:18.784> deals<20:47:19.144> with<20:47:19.504> any 20:47:19.790 --> 20:47:19.800 align:start position:0% actually have a team that deals with any 20:47:19.800 --> 20:47:23.454 align:start position:0% actually have a team that deals with any SNMP<20:47:20.640> reporting<20:47:21.360> and<20:47:22.080> any<20:47:22.256> configurations<20:47:22.976> or 20:47:23.454 --> 20:47:23.464 align:start position:0% SNMP reporting and any configurations or 20:47:23.464 --> 20:47:26.150 align:start position:0% SNMP reporting and any configurations or perhaps<20:47:23.696> as<20:47:23.872> a<20:47:24.120> network<20:47:24.240> engineer<20:47:24.976> you'd<20:47:25.976> have 20:47:26.150 --> 20:47:26.160 align:start position:0% perhaps as a network engineer you'd have 20:47:26.160 --> 20:47:29.566 align:start position:0% perhaps as a network engineer you'd have to<20:47:26.280> enable<20:47:26.656> SNMP<20:47:27.856> reporting<20:47:28.856> on<20:47:29.104> a<20:47:29.280> particular 20:47:29.566 --> 20:47:29.576 align:start position:0% to enable SNMP reporting on a particular 20:47:29.576 --> 20:47:30.774 align:start position:0% to enable SNMP reporting on a particular device 20:47:30.774 --> 20:47:30.784 align:start position:0% device 20:47:30.784 --> 20:47:33.230 align:start position:0% device do<20:47:31.376> some<20:47:31.616> testing<20:47:32.040> to<20:47:32.280> make<20:47:32.464> sure<20:47:32.640> that<20:47:32.936> the 20:47:33.230 --> 20:47:33.240 align:start position:0% do some testing to make sure that the 20:47:33.240 --> 20:47:35.502 align:start position:0% do some testing to make sure that the receiving<20:47:34.016> station<20:47:34.440> the<20:47:34.920> network<20:47:35.104> management 20:47:35.502 --> 20:47:35.512 align:start position:0% receiving station the network management 20:47:35.512 --> 20:47:39.230 align:start position:0% receiving station the network management station<20:47:36.000> can<20:47:36.960> receive<20:47:37.376> information<20:47:38.056> which<20:47:39.056> we 20:47:39.230 --> 20:47:39.240 align:start position:0% station can receive information which we 20:47:39.240 --> 20:47:41.990 align:start position:0% station can receive information which we refer<20:47:39.536> to<20:47:39.600> as<20:47:39.784> traps<20:47:40.192> from<20:47:40.496> the<20:47:40.744> device<20:47:41.000> and 20:47:41.990 --> 20:47:42.000 align:start position:0% refer to as traps from the device and 20:47:42.000 --> 20:47:44.094 align:start position:0% refer to as traps from the device and then<20:47:42.120> you<20:47:42.360> will<20:47:42.536> sign<20:47:43.080> off<20:47:43.320> that<20:47:43.552> device<20:47:43.744> as 20:47:44.094 --> 20:47:44.104 align:start position:0% then you will sign off that device as 20:47:44.104 --> 20:47:46.606 align:start position:0% then you will sign off that device as compatible 20:47:46.606 --> 20:47:46.616 align:start position:0% compatible 20:47:46.616 --> 20:47:49.366 align:start position:0% compatible so<20:47:47.104> SNMP<20:47:47.760> is<20:47:47.936> an<20:47:48.120> application<20:47:48.480> layer<20:47:48.960> protocol 20:47:49.366 --> 20:47:49.376 align:start position:0% so SNMP is an application layer protocol 20:47:49.376 --> 20:47:51.774 align:start position:0% so SNMP is an application layer protocol and<20:47:50.160> the<20:47:50.576> idea<20:47:50.760> is<20:47:50.936> it<20:47:51.176> Exchange<20:47:51.480> Management 20:47:51.774 --> 20:47:51.784 align:start position:0% and the idea is it Exchange Management 20:47:51.784 --> 20:47:54.166 align:start position:0% and the idea is it Exchange Management data<20:47:52.496> between<20:47:52.744> the<20:47:53.216> devices<20:47:53.464> on<20:47:53.936> the<20:47:54.056> network 20:47:54.166 --> 20:47:54.176 align:start position:0% data between the devices on the network 20:47:54.176 --> 20:47:57.286 align:start position:0% data between the devices on the network or<20:47:54.656> from<20:47:54.960> a<20:47:55.144> certain<20:47:55.320> device<20:47:55.824> to<20:47:56.824> the<20:47:57.056> network 20:47:57.286 --> 20:47:57.296 align:start position:0% or from a certain device to the network 20:47:57.296 --> 20:47:59.862 align:start position:0% or from a certain device to the network management<20:47:57.896> station 20:47:59.862 --> 20:47:59.872 align:start position:0% management station 20:47:59.872 --> 20:48:02.150 align:start position:0% management station issues<20:48:00.600> to<20:48:00.784> Monitor<20:48:01.080> and<20:48:01.192> manage<20:48:01.504> devices<20:48:01.800> on 20:48:02.150 --> 20:48:02.160 align:start position:0% issues to Monitor and manage devices on 20:48:02.160 --> 20:48:03.950 align:start position:0% issues to Monitor and manage devices on the<20:48:02.280> network<20:48:02.400> such<20:48:02.824> as<20:48:03.000> router<20:48:03.424> switches 20:48:03.950 --> 20:48:03.960 align:start position:0% the network such as router switches 20:48:03.960 --> 20:48:06.286 align:start position:0% the network such as router switches servers<20:48:04.496> and<20:48:04.976> it<20:48:05.104> even<20:48:05.280> drills<20:48:05.696> down<20:48:05.936> to 20:48:06.286 --> 20:48:06.296 align:start position:0% servers and it even drills down to 20:48:06.296 --> 20:48:08.454 align:start position:0% servers and it even drills down to individual<20:48:06.896> ports<20:48:07.440> for<20:48:07.744> example<20:48:07.920> if<20:48:08.216> you<20:48:08.336> have 20:48:08.454 --> 20:48:08.464 align:start position:0% individual ports for example if you have 20:48:08.464 --> 20:48:09.774 align:start position:0% individual ports for example if you have a<20:48:08.640> switch 20:48:09.774 --> 20:48:09.784 align:start position:0% a switch 20:48:09.784 --> 20:48:13.494 align:start position:0% a switch with<20:48:10.320> 24<20:48:10.552> ports<20:48:11.280> the<20:48:11.464> SNMP<20:48:12.176> manager<20:48:12.784> depending 20:48:13.494 --> 20:48:13.504 align:start position:0% with 24 ports the SNMP manager depending 20:48:13.504 --> 20:48:14.926 align:start position:0% with 24 ports the SNMP manager depending on<20:48:13.616> the<20:48:13.800> software<20:48:14.040> you<20:48:14.280> have<20:48:14.400> some<20:48:14.640> of<20:48:14.824> it's 20:48:14.926 --> 20:48:14.936 align:start position:0% on the software you have some of it's 20:48:14.936 --> 20:48:18.230 align:start position:0% on the software you have some of it's free<20:48:15.120> and<20:48:15.360> some<20:48:15.536> of<20:48:15.656> it's<20:48:15.832> quite<20:48:16.744> expensive 20:48:18.230 --> 20:48:18.240 align:start position:0% free and some of it's quite expensive 20:48:18.240 --> 20:48:21.110 align:start position:0% free and some of it's quite expensive and<20:48:19.144> it<20:48:19.616> can<20:48:19.744> drill<20:48:20.040> down<20:48:20.216> and<20:48:20.464> show<20:48:20.696> you<20:48:20.824> a 20:48:21.110 --> 20:48:21.120 align:start position:0% and it can drill down and show you a 20:48:21.120 --> 20:48:23.926 align:start position:0% and it can drill down and show you a pictorial<20:48:21.656> view<20:48:22.016> of<20:48:22.856> each<20:48:23.104> port<20:48:23.400> on<20:48:23.824> the 20:48:23.926 --> 20:48:23.936 align:start position:0% pictorial view of each port on the 20:48:23.936 --> 20:48:27.286 align:start position:0% pictorial view of each port on the switch<20:48:24.056> including<20:48:24.720> the<20:48:24.960> power<20:48:25.640> and<20:48:26.640> power 20:48:27.286 --> 20:48:27.296 align:start position:0% switch including the power and power 20:48:27.296 --> 20:48:31.542 align:start position:0% switch including the power and power button<20:48:27.784> and<20:48:28.376> you<20:48:28.616> can<20:48:28.744> enable<20:48:29.336> or<20:48:29.760> disable<20:48:30.552> and 20:48:31.542 --> 20:48:31.552 align:start position:0% button and you can enable or disable and 20:48:31.552 --> 20:48:33.526 align:start position:0% button and you can enable or disable and monitor<20:48:31.920> and<20:48:32.104> manage<20:48:32.464> individual<20:48:32.872> ports<20:48:33.360> so 20:48:33.526 --> 20:48:33.536 align:start position:0% monitor and manage individual ports so 20:48:33.536 --> 20:48:35.990 align:start position:0% monitor and manage individual ports so it's<20:48:33.656> very<20:48:33.832> handy<20:48:34.192> and<20:48:34.376> very<20:48:34.616> powerful 20:48:35.990 --> 20:48:36.000 align:start position:0% it's very handy and very powerful 20:48:36.000 --> 20:48:38.814 align:start position:0% it's very handy and very powerful SNMP<20:48:36.896> implementation<20:48:37.616> consists<20:48:38.400> of<20:48:38.464> a 20:48:38.814 --> 20:48:38.824 align:start position:0% SNMP implementation consists of a 20:48:38.824 --> 20:48:40.430 align:start position:0% SNMP implementation consists of a managed<20:48:39.176> device 20:48:40.430 --> 20:48:40.440 align:start position:0% managed device 20:48:40.440 --> 20:48:42.950 align:start position:0% managed device the<20:48:41.040> SNMP<20:48:41.696> agent 20:48:42.950 --> 20:48:42.960 align:start position:0% the SNMP agent 20:48:42.960 --> 20:48:45.590 align:start position:0% the SNMP agent little<20:48:43.504> piece<20:48:43.800> of<20:48:43.920> software<20:48:44.280> the<20:48:44.936> SNMP 20:48:45.590 --> 20:48:45.600 align:start position:0% little piece of software the SNMP 20:48:45.600 --> 20:48:49.494 align:start position:0% little piece of software the SNMP manager<20:48:46.192> which<20:48:46.552> is<20:48:46.680> normally<20:48:47.040> a<20:48:47.824> PC<20:48:48.720> or<20:48:49.080> server 20:48:49.494 --> 20:48:49.504 align:start position:0% manager which is normally a PC or server 20:48:49.504 --> 20:48:51.646 align:start position:0% manager which is normally a PC or server that<20:48:49.976> monitors<20:48:50.336> the<20:48:50.640> network<20:48:50.872> and<20:48:51.424> then 20:48:51.646 --> 20:48:51.656 align:start position:0% that monitors the network and then 20:48:51.656 --> 20:48:54.230 align:start position:0% that monitors the network and then reporting<20:48:52.440> is<20:48:52.680> done<20:48:53.216> on<20:48:53.400> there<20:48:53.576> pictorially 20:48:54.230 --> 20:48:54.240 align:start position:0% reporting is done on there pictorially 20:48:54.240 --> 20:48:55.734 align:start position:0% reporting is done on there pictorially usually 20:48:55.734 --> 20:48:55.744 align:start position:0% usually 20:48:55.744 --> 20:48:58.182 align:start position:0% usually the<20:48:56.104> graphical<20:48:56.576> user<20:48:57.000> interface 20:48:58.182 --> 20:48:58.192 align:start position:0% the graphical user interface 20:48:58.192 --> 20:49:00.110 align:start position:0% the graphical user interface the<20:48:58.496> manage<20:48:58.800> device<20:48:58.976> on<20:48:59.280> the<20:48:59.464> network<20:48:59.576> it 20:49:00.110 --> 20:49:00.120 align:start position:0% the manage device on the network it 20:49:00.120 --> 20:49:02.094 align:start position:0% the manage device on the network it requires<20:49:00.424> some<20:49:00.784> kind<20:49:00.960> of<20:49:01.080> monitoring<20:49:01.680> and<20:49:01.920> it 20:49:02.094 --> 20:49:02.104 align:start position:0% requires some kind of monitoring and it 20:49:02.104 --> 20:49:02.990 align:start position:0% requires some kind of monitoring and it can<20:49:02.280> be 20:49:02.990 --> 20:49:03.000 align:start position:0% can be 20:49:03.000 --> 20:49:05.150 align:start position:0% can be it<20:49:03.424> would<20:49:03.656> be<20:49:03.784> your<20:49:04.016> servers<20:49:04.552> switches 20:49:05.150 --> 20:49:05.160 align:start position:0% it would be your servers switches 20:49:05.160 --> 20:49:08.270 align:start position:0% it would be your servers switches routers<20:49:05.696> firewalls<20:49:06.480> that<20:49:06.720> kind<20:49:06.896> of<20:49:07.016> thing 20:49:08.270 --> 20:49:08.280 align:start position:0% routers firewalls that kind of thing 20:49:08.280 --> 20:49:11.590 align:start position:0% routers firewalls that kind of thing an<20:49:08.872> example<20:49:09.240> is<20:49:09.424> a<20:49:09.656> storage<20:49:09.832> array 20:49:11.590 --> 20:49:11.600 align:start position:0% an example is a storage array 20:49:11.600 --> 20:49:14.926 align:start position:0% an example is a storage array SNMP<20:49:12.600> agent<20:49:13.016> is<20:49:13.440> a<20:49:13.680> program<20:49:13.856> that<20:49:14.280> runs<20:49:14.576> on<20:49:14.824> the 20:49:14.926 --> 20:49:14.936 align:start position:0% SNMP agent is a program that runs on the 20:49:14.936 --> 20:49:16.366 align:start position:0% SNMP agent is a program that runs on the manage<20:49:15.240> device<20:49:15.480> so<20:49:15.720> these<20:49:15.960> need<20:49:16.144> to<20:49:16.192> be 20:49:16.366 --> 20:49:16.376 align:start position:0% manage device so these need to be 20:49:16.376 --> 20:49:17.326 align:start position:0% manage device so these need to be written 20:49:17.326 --> 20:49:17.336 align:start position:0% written 20:49:17.336 --> 20:49:21.230 align:start position:0% written by<20:49:18.000> whoever<20:49:18.480> the<20:49:18.784> vendor<20:49:19.144> is<20:49:19.320> usually<20:49:19.936> so<20:49:20.936> it 20:49:21.230 --> 20:49:21.240 align:start position:0% by whoever the vendor is usually so it 20:49:21.240 --> 20:49:25.182 align:start position:0% by whoever the vendor is usually so it can<20:49:21.616> comply<20:49:22.616> with<20:49:22.800> the<20:49:23.160> RFC 20:49:25.182 --> 20:49:25.192 align:start position:0% can comply with the RFC 20:49:25.192 --> 20:49:27.166 align:start position:0% can comply with the RFC the<20:49:25.552> SNMP<20:49:26.040> collects<20:49:26.400> information<20:49:26.576> from<20:49:27.056> the 20:49:27.166 --> 20:49:27.176 align:start position:0% the SNMP collects information from the 20:49:27.176 --> 20:49:31.070 align:start position:0% the SNMP collects information from the device<20:49:27.360> and<20:49:27.656> sends<20:49:28.016> it<20:49:28.144> to<20:49:28.320> the<20:49:28.440> SNMP<20:49:29.104> manager 20:49:31.070 --> 20:49:31.080 align:start position:0% device and sends it to the SNMP manager 20:49:31.080 --> 20:49:33.886 align:start position:0% device and sends it to the SNMP manager the<20:49:31.800> SNMP<20:49:32.336> manager<20:49:32.824> is<20:49:32.936> typically<20:49:33.240> a<20:49:33.600> computer 20:49:33.886 --> 20:49:33.896 align:start position:0% the SNMP manager is typically a computer 20:49:33.896 --> 20:49:37.134 align:start position:0% the SNMP manager is typically a computer that<20:49:34.800> has<20:49:35.336> the<20:49:35.696> software<20:49:36.296> running<20:49:36.536> for<20:49:36.832> us<20:49:36.960> in 20:49:37.134 --> 20:49:37.144 align:start position:0% that has the software running for us in 20:49:37.144 --> 20:49:40.182 align:start position:0% that has the software running for us in mp<20:49:37.576> and<20:49:38.576> a<20:49:39.120> lot<20:49:39.176> of<20:49:39.296> the<20:49:39.360> time<20:49:39.480> it's<20:49:39.784> graphical 20:49:40.182 --> 20:49:40.192 align:start position:0% mp and a lot of the time it's graphical 20:49:40.192 --> 20:49:42.286 align:start position:0% mp and a lot of the time it's graphical user<20:49:40.680> interface<20:49:41.104> you'll<20:49:41.464> see<20:49:41.640> different 20:49:42.286 --> 20:49:42.296 align:start position:0% user interface you'll see different 20:49:42.296 --> 20:49:44.862 align:start position:0% user interface you'll see different images<20:49:42.656> and<20:49:43.144> diagrams<20:49:43.800> and<20:49:43.976> Reporting<20:49:44.576> pie 20:49:44.862 --> 20:49:44.872 align:start position:0% images and diagrams and Reporting pie 20:49:44.872 --> 20:49:47.270 align:start position:0% images and diagrams and Reporting pie charts<20:49:45.424> and<20:49:45.656> that<20:49:46.192> kind<20:49:46.376> of<20:49:46.496> thing 20:49:47.270 --> 20:49:47.280 align:start position:0% charts and that kind of thing 20:49:47.280 --> 20:49:50.926 align:start position:0% charts and that kind of thing this<20:49:47.872> communicates<20:49:48.360> with<20:49:48.536> the<20:49:48.656> SNMP<20:49:49.256> agent 20:49:50.926 --> 20:49:50.936 align:start position:0% this communicates with the SNMP agent 20:49:50.936 --> 20:49:52.846 align:start position:0% this communicates with the SNMP agent management<20:49:51.424> information<20:49:51.896> base<20:49:52.376> we<20:49:52.680> call 20:49:52.846 --> 20:49:52.856 align:start position:0% management information base we call 20:49:52.856 --> 20:49:54.966 align:start position:0% management information base we call these<20:49:53.104> mibs<20:49:53.512> we<20:49:53.760> don't<20:49:53.872> normally<20:49:54.176> say<20:49:54.424> MIB 20:49:54.966 --> 20:49:54.976 align:start position:0% these mibs we don't normally say MIB 20:49:54.976 --> 20:49:58.366 align:start position:0% these mibs we don't normally say MIB when<20:49:55.976> we<20:49:56.160> speak<20:49:56.280> to<20:49:56.464> Engineers<20:49:56.936> the<20:49:57.784> maybe<20:49:58.080> is 20:49:58.366 --> 20:49:58.376 align:start position:0% when we speak to Engineers the maybe is 20:49:58.376 --> 20:50:03.414 align:start position:0% when we speak to Engineers the maybe is a<20:49:58.552> database<20:49:58.976> maintained<20:49:59.696> by<20:49:59.936> the<20:50:00.120> SNMP<20:50:00.784> agent 20:50:03.414 --> 20:50:03.424 align:start position:0% 20:50:03.424 --> 20:50:04.910 align:start position:0% it<20:50:03.784> contains<20:50:04.144> information<20:50:04.320> about<20:50:04.744> the 20:50:04.910 --> 20:50:04.920 align:start position:0% it contains information about the 20:50:04.920 --> 20:50:06.590 align:start position:0% it contains information about the managed<20:50:05.280> device<20:50:05.400> which<20:50:05.760> is<20:50:05.872> shared<20:50:06.240> by<20:50:06.424> both 20:50:06.590 --> 20:50:06.600 align:start position:0% managed device which is shared by both 20:50:06.600 --> 20:50:10.430 align:start position:0% managed device which is shared by both the<20:50:06.832> SNMP<20:50:07.440> agent<20:50:07.856> and<20:50:08.216> the<20:50:08.400> manager 20:50:10.430 --> 20:50:10.440 align:start position:0% the SNMP agent and the manager 20:50:10.440 --> 20:50:13.246 align:start position:0% the SNMP agent and the manager so<20:50:10.976> SNMP<20:50:11.824> is<20:50:12.176> typically<20:50:12.536> enabled<20:50:12.960> when<20:50:13.080> you 20:50:13.246 --> 20:50:13.256 align:start position:0% so SNMP is typically enabled when you 20:50:13.256 --> 20:50:14.926 align:start position:0% so SNMP is typically enabled when you have<20:50:13.376> a<20:50:13.504> storage<20:50:13.744> system 20:50:14.926 --> 20:50:14.936 align:start position:0% have a storage system 20:50:14.936 --> 20:50:18.590 align:start position:0% have a storage system again<20:50:15.536> it<20:50:15.784> depends<20:50:16.144> on<20:50:16.320> your<20:50:16.680> setup 20:50:18.590 --> 20:50:18.600 align:start position:0% again it depends on your setup 20:50:18.600 --> 20:50:20.630 align:start position:0% again it depends on your setup whenever<20:50:19.376> whenever<20:50:19.920> a<20:50:20.104> specific<20:50:20.336> event 20:50:20.630 --> 20:50:20.640 align:start position:0% whenever whenever a specific event 20:50:20.640 --> 20:50:22.542 align:start position:0% whenever whenever a specific event occurs<20:50:21.240> in<20:50:21.360> the<20:50:21.480> storage<20:50:21.600> system<20:50:21.960> this<20:50:22.320> is<20:50:22.440> an 20:50:22.542 --> 20:50:22.552 align:start position:0% occurs in the storage system this is an 20:50:22.552 --> 20:50:24.886 align:start position:0% occurs in the storage system this is an MP<20:50:22.800> agent<20:50:23.160> running<20:50:23.336> on<20:50:23.576> it<20:50:23.760> will<20:50:24.240> notify<20:50:24.656> the 20:50:24.886 --> 20:50:24.896 align:start position:0% MP agent running on it will notify the 20:50:24.896 --> 20:50:26.926 align:start position:0% MP agent running on it will notify the manager<20:50:25.256> and<20:50:25.376> it<20:50:25.504> sends<20:50:25.744> a<20:50:25.856> message<20:50:26.040> now<20:50:26.760> what 20:50:26.926 --> 20:50:26.936 align:start position:0% manager and it sends a message now what 20:50:26.936 --> 20:50:28.670 align:start position:0% manager and it sends a message now what happens<20:50:27.120> after<20:50:27.424> that<20:50:27.720> depends<20:50:28.192> on<20:50:28.320> how<20:50:28.496> you've 20:50:28.670 --> 20:50:28.680 align:start position:0% happens after that depends on how you've 20:50:28.680 --> 20:50:30.166 align:start position:0% happens after that depends on how you've configured<20:50:29.104> it<20:50:29.216> it<20:50:29.336> could<20:50:29.576> trigger<20:50:29.872> a<20:50:30.000> number 20:50:30.166 --> 20:50:30.176 align:start position:0% configured it it could trigger a number 20:50:30.176 --> 20:50:32.326 align:start position:0% configured it it could trigger a number of<20:50:30.360> events 20:50:32.326 --> 20:50:32.336 align:start position:0% of events 20:50:32.336 --> 20:50:36.822 align:start position:0% of events or<20:50:33.056> just<20:50:33.424> be<20:50:33.656> stored<20:50:34.016> so<20:50:34.800> you<20:50:35.040> can<20:50:35.160> see<20:50:35.400> the 20:50:36.822 --> 20:50:36.832 align:start position:0% or just be stored so you can see the 20:50:36.832 --> 20:50:39.590 align:start position:0% or just be stored so you can see the act<20:50:37.256> I<20:50:37.504> will<20:50:37.680> act<20:50:37.920> now<20:50:38.104> by<20:50:38.400> the<20:50:38.512> SNMP<20:50:39.120> manager 20:50:39.590 --> 20:50:39.600 align:start position:0% act I will act now by the SNMP manager 20:50:39.600 --> 20:50:42.350 align:start position:0% act I will act now by the SNMP manager what<20:50:39.960> actually<20:50:40.144> happens 20:50:42.350 --> 20:50:42.360 align:start position:0% what actually happens 20:50:42.360 --> 20:50:44.814 align:start position:0% what actually happens the<20:50:42.960> Trap<20:50:43.440> is<20:50:43.552> in<20:50:43.744> the<20:50:43.856> is<20:50:44.160> an<20:50:44.336> event<20:50:44.464> that's 20:50:44.814 --> 20:50:44.824 align:start position:0% the Trap is in the is an event that's 20:50:44.824 --> 20:50:47.502 align:start position:0% the Trap is in the is an event that's reported<20:50:45.480> the<20:50:46.016> SNMP<20:50:46.680> manager<20:50:47.104> will<20:50:47.216> receive 20:50:47.502 --> 20:50:47.512 align:start position:0% reported the SNMP manager will receive 20:50:47.512 --> 20:50:50.030 align:start position:0% reported the SNMP manager will receive the<20:50:47.696> event<20:50:47.824> and<20:50:48.120> take<20:50:48.360> action<20:50:48.800> type<20:50:49.800> of 20:50:50.030 --> 20:50:50.040 align:start position:0% the event and take action type of 20:50:50.040 --> 20:50:51.590 align:start position:0% the event and take action type of actions<20:50:50.464> could<20:50:50.696> be 20:50:51.590 --> 20:50:51.600 align:start position:0% actions could be 20:50:51.600 --> 20:50:54.230 align:start position:0% actions could be um<20:50:51.656> an<20:50:52.144> email<20:50:52.336> you<20:50:53.336> can<20:50:53.400> configure<20:50:53.760> it<20:50:53.936> to<20:50:54.120> send 20:50:54.230 --> 20:50:54.240 align:start position:0% um an email you can configure it to send 20:50:54.240 --> 20:50:57.646 align:start position:0% um an email you can configure it to send an<20:50:54.424> SMS<20:50:54.960> to<20:50:55.552> the<20:50:56.280> network<20:50:56.464> engineer<20:50:57.176> or<20:50:57.480> a 20:50:57.646 --> 20:50:57.656 align:start position:0% an SMS to the network engineer or a 20:50:57.656 --> 20:50:59.686 align:start position:0% an SMS to the network engineer or a number<20:50:57.832> of<20:50:58.016> people 20:50:59.686 --> 20:50:59.696 align:start position:0% number of people 20:50:59.696 --> 20:51:02.094 align:start position:0% number of people you<20:51:00.296> can<20:51:00.480> even<20:51:00.656> have<20:51:01.320> um 20:51:02.094 --> 20:51:02.104 align:start position:0% you can even have um 20:51:02.104 --> 20:51:04.310 align:start position:0% you can even have um an<20:51:02.640> automatic<20:51:03.720> um 20:51:04.310 --> 20:51:04.320 align:start position:0% an automatic um 20:51:04.320 --> 20:51:06.414 align:start position:0% an automatic um phone<20:51:04.856> number<20:51:05.040> dialed<20:51:05.696> or<20:51:05.824> number<20:51:06.000> of<20:51:06.176> numbers 20:51:06.414 --> 20:51:06.424 align:start position:0% phone number dialed or number of numbers 20:51:06.424 --> 20:51:09.286 align:start position:0% phone number dialed or number of numbers dialed<20:51:07.192> voice<20:51:07.800> message<20:51:08.104> is<20:51:08.400> sent<20:51:08.640> it<20:51:09.176> just 20:51:09.286 --> 20:51:09.296 align:start position:0% dialed voice message is sent it just 20:51:09.296 --> 20:51:11.686 align:start position:0% dialed voice message is sent it just depends<20:51:09.656> on<20:51:09.896> how<20:51:10.256> you<20:51:10.496> how<20:51:11.104> you<20:51:11.280> configure<20:51:11.576> it 20:51:11.686 --> 20:51:11.696 align:start position:0% depends on how you how you configure it 20:51:11.696 --> 20:51:13.070 align:start position:0% depends on how you how you configure it and<20:51:11.872> how<20:51:11.936> important<20:51:12.424> this<20:51:12.720> particular 20:51:13.070 --> 20:51:13.080 align:start position:0% and how important this particular 20:51:13.080 --> 20:51:14.502 align:start position:0% and how important this particular message<20:51:13.440> is 20:51:14.502 --> 20:51:14.512 align:start position:0% message is 20:51:14.512 --> 20:51:16.454 align:start position:0% message is quote<20:51:14.872> from<20:51:15.120> Wikipedia 20:51:16.454 --> 20:51:16.464 align:start position:0% quote from Wikipedia 20:51:16.464 --> 20:51:19.846 align:start position:0% quote from Wikipedia SNMP<20:51:17.464> agent<20:51:18.056> receives<20:51:18.480> requests<20:51:18.896> on<20:51:19.256> UDP<20:51:19.616> Port 20:51:19.846 --> 20:51:19.856 align:start position:0% SNMP agent receives requests on UDP Port 20:51:19.856 --> 20:51:21.590 align:start position:0% SNMP agent receives requests on UDP Port 161 20:51:21.590 --> 20:51:21.600 align:start position:0% 161 20:51:21.600 --> 20:51:23.814 align:start position:0% 161 it<20:51:22.320> can<20:51:22.496> send<20:51:22.680> requests<20:51:23.160> from<20:51:23.336> any<20:51:23.576> available 20:51:23.814 --> 20:51:23.824 align:start position:0% it can send requests from any available 20:51:23.824 --> 20:51:27.526 align:start position:0% it can send requests from any available Source<20:51:24.424> port<20:51:24.600> to<20:51:24.832> port<20:51:25.440> 161.<20:51:26.696> the<20:51:27.240> age<20:51:27.360> of 20:51:27.526 --> 20:51:27.536 align:start position:0% Source port to port 161. the age of 20:51:27.536 --> 20:51:30.046 align:start position:0% Source port to port 161. the age of response<20:51:28.016> is<20:51:28.144> generally<20:51:28.496> set<20:51:28.800> back<20:51:29.104> send<20:51:29.824> back 20:51:30.046 --> 20:51:30.056 align:start position:0% response is generally set back send back 20:51:30.056 --> 20:51:32.270 align:start position:0% response is generally set back send back to<20:51:30.176> the<20:51:30.360> source<20:51:30.600> port<20:51:30.720> on<20:51:30.960> the<20:51:31.016> manager<20:51:31.800> the 20:51:32.270 --> 20:51:32.280 align:start position:0% to the source port on the manager the 20:51:32.280 --> 20:51:34.542 align:start position:0% to the source port on the manager the manager<20:51:32.696> receives<20:51:33.000> notifications<20:51:33.832> these<20:51:34.440> are 20:51:34.542 --> 20:51:34.552 align:start position:0% manager receives notifications these are 20:51:34.552 --> 20:51:36.470 align:start position:0% manager receives notifications these are known<20:51:34.680> as<20:51:34.920> traps<20:51:35.336> and<20:51:35.576> inform<20:51:35.936> requests 20:51:36.470 --> 20:51:36.480 align:start position:0% known as traps and inform requests 20:51:36.480 --> 20:51:38.990 align:start position:0% known as traps and inform requests there's<20:51:36.720> other<20:51:36.960> types<20:51:37.256> of<20:51:37.440> messages<20:51:38.000> these 20:51:38.990 --> 20:51:39.000 align:start position:0% there's other types of messages these 20:51:39.000 --> 20:51:42.646 align:start position:0% there's other types of messages these are<20:51:39.056> on<20:51:39.176> Port<20:51:39.424> 162.<20:51:40.856> so<20:51:41.280> basically<20:51:41.872> UDP<20:51:42.240> ports 20:51:42.646 --> 20:51:42.656 align:start position:0% are on Port 162. so basically UDP ports 20:51:42.656 --> 20:51:47.686 align:start position:0% are on Port 162. so basically UDP ports 161<20:51:43.192> and<20:51:43.376> 162<20:51:43.920> is<20:51:44.104> used<20:51:44.280> by<20:51:44.464> SNMP 20:51:47.686 --> 20:51:47.696 align:start position:0% 20:51:47.696 --> 20:51:50.862 align:start position:0% moving<20:51:48.240> on<20:51:48.360> to<20:51:48.480> a<20:51:48.744> syslog<20:51:49.744> which<20:51:50.104> has<20:51:50.640> got 20:51:50.862 --> 20:51:50.872 align:start position:0% moving on to a syslog which has got 20:51:50.872 --> 20:51:53.710 align:start position:0% moving on to a syslog which has got quite<20:51:51.120> a<20:51:51.296> lot<20:51:51.424> of<20:51:51.536> prominence<20:51:52.080> in<20:51:52.376> the<20:51:52.552> Cisco 20:51:53.710 --> 20:51:53.720 align:start position:0% quite a lot of prominence in the Cisco 20:51:53.720 --> 20:51:56.206 align:start position:0% quite a lot of prominence in the Cisco CCNA<20:51:54.720> exams 20:51:56.206 --> 20:51:56.216 align:start position:0% CCNA exams 20:51:56.216 --> 20:51:58.486 align:start position:0% CCNA exams it's<20:51:56.872> a<20:51:57.120> protocol<20:51:57.536> for<20:51:57.832> exchanging<20:51:58.256> log 20:51:58.486 --> 20:51:58.496 align:start position:0% it's a protocol for exchanging log 20:51:58.496 --> 20:52:01.790 align:start position:0% it's a protocol for exchanging log messages<20:51:58.800> so<20:51:59.216> syslog<20:51:59.872> generally<20:52:00.720> sits<20:52:01.320> on<20:52:01.504> a 20:52:01.790 --> 20:52:01.800 align:start position:0% messages so syslog generally sits on a 20:52:01.800 --> 20:52:04.486 align:start position:0% messages so syslog generally sits on a syslog<20:52:02.576> server<20:52:03.056> although<20:52:03.720> you<20:52:03.896> can<20:52:04.016> configure 20:52:04.486 --> 20:52:04.496 align:start position:0% syslog server although you can configure 20:52:04.496 --> 20:52:08.454 align:start position:0% syslog server although you can configure it<20:52:04.744> a<20:52:05.696> router<20:52:06.176> to<20:52:06.424> be<20:52:06.536> a<20:52:06.656> syslog<20:52:07.016> server<20:52:07.504> the 20:52:08.454 --> 20:52:08.464 align:start position:0% it a router to be a syslog server the 20:52:08.464 --> 20:52:11.094 align:start position:0% it a router to be a syslog server the general<20:52:08.576> rule<20:52:09.056> is<20:52:09.176> leave<20:52:09.656> these<20:52:10.320> devices<20:52:10.616> like 20:52:11.094 --> 20:52:11.104 align:start position:0% general rule is leave these devices like 20:52:11.104 --> 20:52:12.710 align:start position:0% general rule is leave these devices like a<20:52:11.280> router<20:52:11.640> to<20:52:11.760> do<20:52:11.936> the<20:52:12.056> main<20:52:12.240> job<20:52:12.480> it's 20:52:12.710 --> 20:52:12.720 align:start position:0% a router to do the main job it's 20:52:12.720 --> 20:52:13.966 align:start position:0% a router to do the main job it's designed<20:52:13.192> for 20:52:13.966 --> 20:52:13.976 align:start position:0% designed for 20:52:13.976 --> 20:52:17.686 align:start position:0% designed for instead<20:52:14.824> of<20:52:15.296> um<20:52:15.296> using<20:52:16.192> it<20:52:16.320> to<20:52:16.440> allocate<20:52:16.856> DHCP 20:52:17.686 --> 20:52:17.696 align:start position:0% instead of um using it to allocate DHCP 20:52:17.696 --> 20:52:20.094 align:start position:0% instead of um using it to allocate DHCP addresses<20:52:18.296> and<20:52:18.784> record<20:52:19.192> syslog<20:52:19.856> messages 20:52:20.094 --> 20:52:20.104 align:start position:0% addresses and record syslog messages 20:52:20.104 --> 20:52:22.734 align:start position:0% addresses and record syslog messages although<20:52:20.936> it<20:52:21.120> can<20:52:21.296> do<20:52:21.480> these<20:52:22.192> and<20:52:22.320> a<20:52:22.496> lot<20:52:22.552> more 20:52:22.734 --> 20:52:22.744 align:start position:0% although it can do these and a lot more 20:52:22.744 --> 20:52:23.750 align:start position:0% although it can do these and a lot more things 20:52:23.750 --> 20:52:23.760 align:start position:0% things 20:52:23.760 --> 20:52:26.094 align:start position:0% things it<20:52:24.240> can<20:52:24.296> be<20:52:24.424> used<20:52:24.536> by<20:52:24.896> devices<20:52:25.440> on<20:52:25.744> the<20:52:25.920> network 20:52:26.094 --> 20:52:26.104 align:start position:0% it can be used by devices on the network 20:52:26.104 --> 20:52:29.454 align:start position:0% it can be used by devices on the network to<20:52:27.056> move<20:52:27.656> all<20:52:27.896> the<20:52:28.080> audit<20:52:28.680> logs<20:52:29.040> to<20:52:29.160> a<20:52:29.336> central 20:52:29.454 --> 20:52:29.464 align:start position:0% to move all the audit logs to a central 20:52:29.464 --> 20:52:31.790 align:start position:0% to move all the audit logs to a central login<20:52:29.760> server<20:52:30.360> again<20:52:31.080> this<20:52:31.320> is<20:52:31.504> called<20:52:31.616> the 20:52:31.790 --> 20:52:31.800 align:start position:0% login server again this is called the 20:52:31.800 --> 20:52:34.606 align:start position:0% login server again this is called the syslog<20:52:32.336> server 20:52:34.606 --> 20:52:34.616 align:start position:0% syslog server 20:52:34.616 --> 20:52:36.774 align:start position:0% syslog server why<20:52:35.160> would<20:52:35.280> you<20:52:35.464> do<20:52:35.640> it<20:52:35.824> it<20:52:36.296> allows<20:52:36.656> the 20:52:36.774 --> 20:52:36.784 align:start position:0% why would you do it it allows the 20:52:36.784 --> 20:52:38.990 align:start position:0% why would you do it it allows the consolidation<20:52:37.376> of<20:52:37.616> audit<20:52:38.104> logs<20:52:38.512> from 20:52:38.990 --> 20:52:39.000 align:start position:0% consolidation of audit logs from 20:52:39.000 --> 20:52:40.790 align:start position:0% consolidation of audit logs from multiple<20:52:39.600> devices<20:52:39.960> to<20:52:40.256> a<20:52:40.376> single<20:52:40.680> place 20:52:40.790 --> 20:52:40.800 align:start position:0% multiple devices to a single place 20:52:40.800 --> 20:52:44.230 align:start position:0% multiple devices to a single place basically<20:52:41.760> it's<20:52:42.600> for<20:52:42.960> to<20:52:43.256> give<20:52:43.440> you<20:52:43.616> usable 20:52:44.230 --> 20:52:44.240 align:start position:0% basically it's for to give you usable 20:52:44.240 --> 20:52:47.862 align:start position:0% basically it's for to give you usable information<20:52:45.240> and<20:52:45.960> data<20:52:46.440> you<20:52:47.400> can<20:52:47.512> have 20:52:47.862 --> 20:52:47.872 align:start position:0% information and data you can have 20:52:47.872 --> 20:52:50.326 align:start position:0% information and data you can have different<20:52:48.240> levels<20:52:48.784> of<20:52:48.960> syslog<20:52:49.376> messaging 20:52:50.326 --> 20:52:50.336 align:start position:0% different levels of syslog messaging 20:52:50.336 --> 20:52:52.910 align:start position:0% different levels of syslog messaging from<20:52:51.000> urgent<20:52:51.176> messages<20:52:51.376> to<20:52:52.376> just<20:52:52.616> general 20:52:52.910 --> 20:52:52.920 align:start position:0% from urgent messages to just general 20:52:52.920 --> 20:52:56.750 align:start position:0% from urgent messages to just general reporting<20:52:53.760> and<20:52:54.720> how<20:52:55.144> and<20:52:55.320> what<20:52:55.920> it<20:52:56.512> actually 20:52:56.750 --> 20:52:56.760 align:start position:0% reporting and how and what it actually 20:52:56.760 --> 20:52:58.926 align:start position:0% reporting and how and what it actually does<20:52:57.056> is<20:52:57.240> down<20:52:57.480> to<20:52:57.720> you<20:52:57.896> to<20:52:58.440> configure 20:52:58.926 --> 20:52:58.936 align:start position:0% does is down to you to configure 20:52:58.936 --> 20:53:01.182 align:start position:0% does is down to you to configure depending<20:52:59.936> on<20:53:00.000> your<20:53:00.360> particular<20:53:00.656> needs<20:53:01.080> on 20:53:01.182 --> 20:53:01.192 align:start position:0% depending on your particular needs on 20:53:01.192 --> 20:53:03.526 align:start position:0% depending on your particular needs on the<20:53:01.376> network 20:53:03.526 --> 20:53:03.536 align:start position:0% the network 20:53:03.536 --> 20:53:06.590 align:start position:0% the network okay<20:53:04.144> lastly<20:53:04.640> s-i-e-m<20:53:05.640> security<20:53:06.120> information 20:53:06.590 --> 20:53:06.600 align:start position:0% okay lastly s-i-e-m security information 20:53:06.600 --> 20:53:08.686 align:start position:0% okay lastly s-i-e-m security information and<20:53:07.256> event<20:53:07.440> manager 20:53:08.686 --> 20:53:08.696 align:start position:0% and event manager 20:53:08.696 --> 20:53:11.206 align:start position:0% and event manager it's<20:53:09.480> a<20:53:09.720> set<20:53:10.144> of<20:53:10.320> software<20:53:10.616> products<20:53:11.040> and 20:53:11.206 --> 20:53:11.216 align:start position:0% it's a set of software products and 20:53:11.216 --> 20:53:12.950 align:start position:0% it's a set of software products and services<20:53:11.464> that<20:53:11.872> are<20:53:12.000> used<20:53:12.120> to<20:53:12.360> monitor<20:53:12.720> a 20:53:12.950 --> 20:53:12.960 align:start position:0% services that are used to monitor a 20:53:12.960 --> 20:53:14.030 align:start position:0% services that are used to monitor a network 20:53:14.030 --> 20:53:14.040 align:start position:0% network 20:53:14.040 --> 20:53:16.182 align:start position:0% network what<20:53:14.464> it<20:53:14.640> gives<20:53:14.760> you<20:53:14.872> is<20:53:15.056> a<20:53:15.240> real-time<20:53:15.656> output 20:53:16.182 --> 20:53:16.192 align:start position:0% what it gives you is a real-time output 20:53:16.192 --> 20:53:18.526 align:start position:0% what it gives you is a real-time output of<20:53:16.496> security<20:53:16.800> alerts<20:53:17.576> generated<20:53:18.000> by<20:53:18.296> Network 20:53:18.526 --> 20:53:18.536 align:start position:0% of security alerts generated by Network 20:53:18.536 --> 20:53:20.990 align:start position:0% of security alerts generated by Network and<20:53:18.960> network<20:53:19.440> Hardware<20:53:19.856> so<20:53:20.640> it's<20:53:20.760> definitely 20:53:20.990 --> 20:53:21.000 align:start position:0% and network Hardware so it's definitely 20:53:21.000 --> 20:53:23.630 align:start position:0% and network Hardware so it's definitely got<20:53:21.176> a<20:53:21.360> security<20:53:21.536> bias 20:53:23.630 --> 20:53:23.640 align:start position:0% got a security bias 20:53:23.640 --> 20:53:26.206 align:start position:0% got a security bias It's<20:53:24.056> a<20:53:24.176> combination<20:53:24.536> of<20:53:24.896> sem<20:53:25.552> security<20:53:25.856> event 20:53:26.206 --> 20:53:26.216 align:start position:0% It's a combination of sem security event 20:53:26.216 --> 20:53:29.030 align:start position:0% It's a combination of sem security event manager<20:53:26.824> and<20:53:27.176> Sim<20:53:27.720> security<20:53:28.552> information 20:53:29.030 --> 20:53:29.040 align:start position:0% manager and Sim security information 20:53:29.040 --> 20:53:32.814 align:start position:0% manager and Sim security information management 20:53:32.814 --> 20:53:32.824 align:start position:0% 20:53:32.824 --> 20:53:34.910 align:start position:0% the<20:53:33.480> security<20:53:33.656> event<20:53:33.896> management<20:53:34.192> deals<20:53:34.800> with 20:53:34.910 --> 20:53:34.920 align:start position:0% the security event management deals with 20:53:34.920 --> 20:53:36.166 align:start position:0% the security event management deals with the<20:53:35.040> real-time<20:53:35.400> monitoring<20:53:36.000> and 20:53:36.166 --> 20:53:36.176 align:start position:0% the real-time monitoring and 20:53:36.176 --> 20:53:38.566 align:start position:0% the real-time monitoring and notification<20:53:36.784> of<20:53:37.016> security<20:53:37.256> events 20:53:38.566 --> 20:53:38.576 align:start position:0% notification of security events 20:53:38.576 --> 20:53:40.670 align:start position:0% notification of security events the<20:53:39.056> Sim<20:53:39.240> deals<20:53:39.896> with<20:53:39.960> the<20:53:40.080> collection<20:53:40.320> of<20:53:40.552> the 20:53:40.670 --> 20:53:40.680 align:start position:0% the Sim deals with the collection of the 20:53:40.680 --> 20:53:44.502 align:start position:0% the Sim deals with the collection of the log<20:53:40.800> files<20:53:41.280> into<20:53:41.512> a<20:53:41.936> central<20:53:42.176> Repository 20:53:44.502 --> 20:53:44.512 align:start position:0% log files into a central Repository 20:53:44.512 --> 20:53:46.182 align:start position:0% log files into a central Repository a<20:53:45.000> lot<20:53:45.056> of<20:53:45.176> the<20:53:45.296> time<20:53:45.424> as<20:53:45.832> with<20:53:46.016> other 20:53:46.182 --> 20:53:46.192 align:start position:0% a lot of the time as with other 20:53:46.192 --> 20:53:48.110 align:start position:0% a lot of the time as with other protocols<20:53:46.920> like<20:53:47.040> this<20:53:47.160> you<20:53:47.464> would<20:53:47.576> have<20:53:47.824> a 20:53:48.110 --> 20:53:48.120 align:start position:0% protocols like this you would have a 20:53:48.120 --> 20:53:50.862 align:start position:0% protocols like this you would have a graphical<20:53:48.744> analysis<20:53:49.744> giving<20:53:50.104> you<20:53:50.336> some<20:53:50.760> sort 20:53:50.862 --> 20:53:50.872 align:start position:0% graphical analysis giving you some sort 20:53:50.872 --> 20:53:52.734 align:start position:0% graphical analysis giving you some sort of<20:53:51.000> meaningful<20:53:51.424> data<20:53:51.960> that<20:53:52.496> you<20:53:52.616> can 20:53:52.734 --> 20:53:52.744 align:start position:0% of meaningful data that you can 20:53:52.744 --> 20:53:54.470 align:start position:0% of meaningful data that you can interpret 20:53:54.470 --> 20:53:54.480 align:start position:0% interpret 20:53:54.480 --> 20:53:56.990 align:start position:0% interpret the<20:53:54.832> Siem<20:53:55.504> Solutions<20:53:56.160> are<20:53:56.512> used<20:53:56.640> to<20:53:56.824> log 20:53:56.990 --> 20:53:57.000 align:start position:0% the Siem Solutions are used to log 20:53:57.000 --> 20:54:00.470 align:start position:0% the Siem Solutions are used to log security<20:53:57.240> data<20:53:57.832> and<20:53:58.144> generate<20:53:58.760> reports<20:53:59.760> a<20:54:00.360> lot 20:54:00.470 --> 20:54:00.480 align:start position:0% security data and generate reports a lot 20:54:00.480 --> 20:54:01.966 align:start position:0% security data and generate reports a lot of<20:54:00.600> the<20:54:00.656> time<20:54:00.784> for<20:54:01.016> compliance<20:54:01.552> and<20:54:01.744> security 20:54:01.966 --> 20:54:01.976 align:start position:0% of the time for compliance and security 20:54:01.976 --> 20:54:04.670 align:start position:0% of the time for compliance and security compliance<20:54:02.760> is<20:54:03.120> a<20:54:03.424> whole 20:54:04.670 --> 20:54:04.680 align:start position:0% compliance is a whole 20:54:04.680 --> 20:54:07.430 align:start position:0% compliance is a whole new<20:54:05.336> and<20:54:05.512> expanded<20:54:06.000> area 20:54:07.430 --> 20:54:07.440 align:start position:0% new and expanded area 20:54:07.440 --> 20:54:10.670 align:start position:0% new and expanded area a<20:54:07.920> lot<20:54:08.040> of<20:54:08.160> the<20:54:08.216> time<20:54:08.400> for<20:54:08.696> you<20:54:08.824> to<20:54:09.120> comply<20:54:09.656> with 20:54:10.670 --> 20:54:10.680 align:start position:0% a lot of the time for you to comply with 20:54:10.680 --> 20:54:13.790 align:start position:0% a lot of the time for you to comply with and<20:54:11.336> National<20:54:11.640> standards<20:54:12.424> and<20:54:12.832> requirements 20:54:13.790 --> 20:54:13.800 align:start position:0% and National standards and requirements 20:54:13.800 --> 20:54:16.070 align:start position:0% and National standards and requirements for<20:54:14.040> security 20:54:16.070 --> 20:54:16.080 align:start position:0% for security 20:54:16.080 --> 20:54:18.350 align:start position:0% for security one<20:54:16.616> example<20:54:16.920> is<20:54:17.160> checkpoint<20:54:17.640> event<20:54:18.000> here 20:54:18.350 --> 20:54:18.360 align:start position:0% one example is checkpoint event here 20:54:18.360 --> 20:54:20.454 align:start position:0% one example is checkpoint event here which<20:54:18.720> you<20:54:19.080> can<20:54:19.192> Google<20:54:19.680> and<20:54:19.976> look<20:54:20.160> at<20:54:20.280> some 20:54:20.454 --> 20:54:20.464 align:start position:0% which you can Google and look at some 20:54:20.464 --> 20:54:22.094 align:start position:0% which you can Google and look at some more<20:54:20.640> information<20:54:20.824> if<20:54:21.176> you<20:54:21.296> want<20:54:21.424> to<20:54:21.536> do<20:54:21.656> some 20:54:22.094 --> 20:54:22.104 align:start position:0% more information if you want to do some 20:54:22.104 --> 20:54:25.246 align:start position:0% more information if you want to do some research<20:54:23.104> but<20:54:23.696> that's<20:54:24.360> um<20:54:24.360> for<20:54:24.656> now<20:54:24.784> summary 20:54:25.246 --> 20:54:25.256 align:start position:0% research but that's um for now summary 20:54:25.256 --> 20:54:28.734 align:start position:0% research but that's um for now summary is<20:54:25.504> SNMP<20:54:26.480> components<20:54:27.480> manage<20:54:27.960> devices<20:54:28.320> and 20:54:28.734 --> 20:54:28.744 align:start position:0% is SNMP components manage devices and 20:54:28.744 --> 20:54:30.710 align:start position:0% is SNMP components manage devices and agents<20:54:29.216> and<20:54:29.336> managers 20:54:30.710 --> 20:54:30.720 align:start position:0% agents and managers 20:54:30.720 --> 20:54:34.862 align:start position:0% agents and managers mibs<20:54:31.552> we've<20:54:31.856> talked<20:54:32.160> about<20:54:32.424> how<20:54:33.424> SNMP<20:54:34.080> works 20:54:34.862 --> 20:54:34.872 align:start position:0% mibs we've talked about how SNMP works 20:54:34.872 --> 20:54:38.206 align:start position:0% mibs we've talked about how SNMP works alerting<20:54:35.872> syslog 20:54:38.206 --> 20:54:38.216 align:start position:0% alerting syslog 20:54:38.216 --> 20:54:41.454 align:start position:0% alerting syslog and<20:54:38.760> why<20:54:38.872> we<20:54:39.056> use<20:54:39.240> this<20:54:39.424> log<20:54:39.656> and<20:54:39.960> Siem<20:54:40.680> okay 20:54:41.454 --> 20:54:41.464 align:start position:0% and why we use this log and Siem okay 20:54:41.464 --> 20:54:47.590 align:start position:0% and why we use this log and Siem okay that's<20:54:41.760> all<20:54:42.000> for<20:54:42.176> now<20:54:42.360> thanks<20:54:42.784> for<20:54:42.960> watching 20:54:47.590 --> 20:54:47.600 align:start position:0% 20:54:47.600 --> 20:54:56.286 align:start position:0% [Music] 20:54:56.286 --> 20:54:56.296 align:start position:0% [Music] 20:54:56.296 --> 20:55:03.710 align:start position:0% [Music] thank<20:54:57.296> you 20:55:03.710 --> 20:55:03.720 align:start position:0% 20:55:03.720 --> 20:55:06.526 align:start position:0% welcome<20:55:04.080> to<20:55:04.376> module<20:55:04.680> 16<20:55:04.920> lesson<20:55:05.760> one<20:55:05.936> web 20:55:06.526 --> 20:55:06.536 align:start position:0% welcome to module 16 lesson one web 20:55:06.536 --> 20:55:07.966 align:start position:0% welcome to module 16 lesson one web services 20:55:07.966 --> 20:55:07.976 align:start position:0% services 20:55:07.976 --> 20:55:10.366 align:start position:0% services this<20:55:08.576> would<20:55:08.696> obviously<20:55:09.120> uh<20:55:09.536> be<20:55:09.896> a<20:55:10.080> massive 20:55:10.366 --> 20:55:10.376 align:start position:0% this would obviously uh be a massive 20:55:10.376 --> 20:55:12.414 align:start position:0% this would obviously uh be a massive area<20:55:10.616> we're<20:55:11.104> just<20:55:11.336> touching<20:55:11.872> on<20:55:12.000> the<20:55:12.176> things 20:55:12.414 --> 20:55:12.424 align:start position:0% area we're just touching on the things 20:55:12.424 --> 20:55:15.646 align:start position:0% area we're just touching on the things that<20:55:12.720> are<20:55:12.832> covered<20:55:13.192> in<20:55:13.376> the<20:55:13.680> syllabus<20:55:14.656> what 20:55:15.646 --> 20:55:15.656 align:start position:0% that are covered in the syllabus what 20:55:15.656 --> 20:55:19.150 align:start position:0% that are covered in the syllabus what are<20:55:15.896> web<20:55:16.080> services<20:55:16.376> XML 20:55:19.150 --> 20:55:19.160 align:start position:0% are web services XML 20:55:19.160 --> 20:55:21.486 align:start position:0% are web services XML programming<20:55:20.160> languages<20:55:20.512> and<20:55:20.760> web<20:55:21.000> services 20:55:21.486 --> 20:55:21.496 align:start position:0% programming languages and web services 20:55:21.496 --> 20:55:24.430 align:start position:0% programming languages and web services their<20:55:22.496> components<20:55:23.160> used<20:55:23.336> by<20:55:23.576> web<20:55:23.824> services 20:55:24.430 --> 20:55:24.440 align:start position:0% their components used by web services 20:55:24.440 --> 20:55:27.822 align:start position:0% their components used by web services how<20:55:25.440> are<20:55:25.552> web<20:55:25.800> service<20:55:26.040> works 20:55:27.822 --> 20:55:27.832 align:start position:0% how are web service works 20:55:27.832 --> 20:55:30.350 align:start position:0% how are web service works I<20:55:28.440> think<20:55:28.616> uh<20:55:28.920> this<20:55:29.280> has<20:55:29.400> probably<20:55:29.576> been<20:55:29.872> put<20:55:30.176> in 20:55:30.350 --> 20:55:30.360 align:start position:0% I think uh this has probably been put in 20:55:30.360 --> 20:55:32.926 align:start position:0% I think uh this has probably been put in in<20:55:31.192> as<20:55:31.440> much<20:55:31.616> as<20:55:31.800> you<20:55:32.104> probably<20:55:32.216> you<20:55:32.512> may<20:55:32.760> be 20:55:32.926 --> 20:55:32.936 align:start position:0% in as much as you probably you may be 20:55:32.936 --> 20:55:34.734 align:start position:0% in as much as you probably you may be asked<20:55:33.176> to<20:55:33.240> do<20:55:33.424> some<20:55:33.600> sort<20:55:33.784> of<20:55:33.832> troubleshooting 20:55:34.734 --> 20:55:34.744 align:start position:0% asked to do some sort of troubleshooting 20:55:34.744 --> 20:55:38.566 align:start position:0% asked to do some sort of troubleshooting not<20:55:35.464> uh<20:55:36.120> in<20:55:36.720> the<20:55:36.832> respective<20:55:37.376> web<20:55:37.744> programming 20:55:38.566 --> 20:55:38.576 align:start position:0% not uh in the respective web programming 20:55:38.576 --> 20:55:43.006 align:start position:0% not uh in the respective web programming but<20:55:39.536> perhaps<20:55:40.216> accessor<20:55:41.216> through<20:55:41.576> the<20:55:41.760> network 20:55:43.006 --> 20:55:43.016 align:start position:0% but perhaps accessor through the network 20:55:43.016 --> 20:55:44.926 align:start position:0% but perhaps accessor through the network or<20:55:43.504> firewalls<20:55:44.216> or<20:55:44.464> some<20:55:44.640> sort<20:55:44.824> of 20:55:44.926 --> 20:55:44.936 align:start position:0% or firewalls or some sort of 20:55:44.936 --> 20:55:47.094 align:start position:0% or firewalls or some sort of troubleshooting<20:55:45.896> so<20:55:46.256> you<20:55:46.616> may<20:55:46.744> need<20:55:46.920> to 20:55:47.094 --> 20:55:47.104 align:start position:0% troubleshooting so you may need to 20:55:47.104 --> 20:55:49.430 align:start position:0% troubleshooting so you may need to communicate<20:55:47.576> with<20:55:47.936> the<20:55:48.176> web<20:55:48.480> programmers<20:55:49.144> at 20:55:49.430 --> 20:55:49.440 align:start position:0% communicate with the web programmers at 20:55:49.440 --> 20:55:50.990 align:start position:0% communicate with the web programmers at some<20:55:49.552> point 20:55:50.990 --> 20:55:51.000 align:start position:0% some point 20:55:51.000 --> 20:55:52.910 align:start position:0% some point what<20:55:51.720> are<20:55:51.832> they<20:55:52.016> there's<20:55:52.320> a<20:55:52.440> whole<20:55:52.552> bunch<20:55:52.744> of 20:55:52.910 --> 20:55:52.920 align:start position:0% what are they there's a whole bunch of 20:55:52.920 --> 20:55:55.310 align:start position:0% what are they there's a whole bunch of applications<20:55:53.464> that<20:55:54.000> use<20:55:54.176> Open<20:55:54.480> Standards 20:55:55.310 --> 20:55:55.320 align:start position:0% applications that use Open Standards 20:55:55.320 --> 20:55:58.310 align:start position:0% applications that use Open Standards such<20:55:56.040> as<20:55:56.216> Excel 20:55:58.310 --> 20:55:58.320 align:start position:0% such as Excel 20:55:58.320 --> 20:56:02.150 align:start position:0% such as Excel soap<20:55:59.216> wsdl 20:56:02.150 --> 20:56:02.160 align:start position:0% soap wsdl 20:56:02.160 --> 20:56:04.542 align:start position:0% soap wsdl uddi 20:56:04.542 --> 20:56:04.552 align:start position:0% uddi 20:56:04.552 --> 20:56:06.822 align:start position:0% uddi uses<20:56:05.464> they<20:56:05.696> used<20:56:05.872> to<20:56:06.056> exchange<20:56:06.296> data<20:56:06.720> between 20:56:06.822 --> 20:56:06.832 align:start position:0% uses they used to exchange data between 20:56:06.832 --> 20:56:09.950 align:start position:0% uses they used to exchange data between the<20:56:07.144> web-based<20:56:07.616> applications<20:56:08.240> over<20:56:09.240> an<20:56:09.600> IP 20:56:09.950 --> 20:56:09.960 align:start position:0% the web-based applications over an IP 20:56:09.960 --> 20:56:12.966 align:start position:0% the web-based applications over an IP network<20:56:10.336> and<20:56:11.336> this<20:56:11.576> is<20:56:11.696> just<20:56:11.936> a<20:56:12.176> massively 20:56:12.966 --> 20:56:12.976 align:start position:0% network and this is just a massively 20:56:12.976 --> 20:56:16.150 align:start position:0% network and this is just a massively expanded<20:56:13.976> area<20:56:14.216> and<20:56:14.576> always<20:56:14.760> has<20:56:15.000> been<20:56:15.240> since 20:56:16.150 --> 20:56:16.160 align:start position:0% expanded area and always has been since 20:56:16.160 --> 20:56:20.862 align:start position:0% expanded area and always has been since HTTP<20:56:17.160> was<20:56:17.576> first<20:56:17.872> used<20:56:18.296> to<20:56:19.016> display<20:56:19.616> web<20:56:20.512> pages 20:56:20.862 --> 20:56:20.872 align:start position:0% HTTP was first used to display web pages 20:56:20.872 --> 20:56:23.502 align:start position:0% HTTP was first used to display web pages it's<20:56:21.296> been<20:56:21.480> improved<20:56:22.016> upon<20:56:22.376> over<20:56:23.104> and<20:56:23.280> over 20:56:23.502 --> 20:56:23.512 align:start position:0% it's been improved upon over and over 20:56:23.512 --> 20:56:26.814 align:start position:0% it's been improved upon over and over again<20:56:23.824> to<20:56:24.296> deal<20:56:24.480> with<20:56:24.784> them<20:56:25.336> issues<20:56:26.336> speed 20:56:26.814 --> 20:56:26.824 align:start position:0% again to deal with them issues speed 20:56:26.824 --> 20:56:27.910 align:start position:0% again to deal with them issues speed security 20:56:27.910 --> 20:56:27.920 align:start position:0% security 20:56:27.920 --> 20:56:31.606 align:start position:0% security usability<20:56:29.120> mobile<20:56:30.120> devices<20:56:30.600> it's<20:56:31.256> just<20:56:31.440> never 20:56:31.606 --> 20:56:31.616 align:start position:0% usability mobile devices it's just never 20:56:31.616 --> 20:56:34.910 align:start position:0% usability mobile devices it's just never ending 20:56:34.910 --> 20:56:34.920 align:start position:0% 20:56:34.920 --> 20:56:37.910 align:start position:0% so<20:56:35.872> in<20:56:36.240> a<20:56:36.424> web<20:56:36.480> service<20:56:36.784> we<20:56:37.320> already<20:56:37.440> know<20:56:37.680> the 20:56:37.910 --> 20:56:37.920 align:start position:0% so in a web service we already know the 20:56:37.920 --> 20:56:41.502 align:start position:0% so in a web service we already know the HTTP<20:56:38.872> is<20:56:39.656> used<20:56:39.832> to<20:56:40.144> transfer 20:56:41.502 --> 20:56:41.512 align:start position:0% HTTP is used to transfer 20:56:41.512 --> 20:56:43.670 align:start position:0% HTTP is used to transfer um<20:56:41.576> machine<20:56:41.936> readable<20:56:42.480> formats<20:56:43.144> such<20:56:43.256> as<20:56:43.504> the 20:56:43.670 --> 20:56:43.680 align:start position:0% um machine readable formats such as the 20:56:43.680 --> 20:56:48.286 align:start position:0% um machine readable formats such as the following<20:56:44.536> XML<20:56:45.536> Json 20:56:48.286 --> 20:56:48.296 align:start position:0% following XML Json 20:56:48.296 --> 20:56:51.414 align:start position:0% following XML Json and<20:56:48.784> Jason<20:56:49.280> when<20:56:50.280> different<20:56:50.512> software 20:56:51.414 --> 20:56:51.424 align:start position:0% and Jason when different software 20:56:51.424 --> 20:56:53.094 align:start position:0% and Jason when different software Services<20:56:51.656> onto<20:56:52.192> stage<20:56:52.552> dates<20:56:52.800> with<20:56:52.976> each 20:56:53.094 --> 20:56:53.104 align:start position:0% Services onto stage dates with each 20:56:53.104 --> 20:56:54.886 align:start position:0% Services onto stage dates with each other<20:56:53.280> a<20:56:53.576> web<20:56:53.760> service<20:56:53.936> allows<20:56:54.480> them<20:56:54.600> to<20:56:54.784> do 20:56:54.886 --> 20:56:54.896 align:start position:0% other a web service allows them to do 20:56:54.896 --> 20:56:58.430 align:start position:0% other a web service allows them to do this<20:56:55.144> over<20:56:55.552> the<20:56:56.464> internet 20:56:58.430 --> 20:56:58.440 align:start position:0% this over the internet 20:56:58.440 --> 20:57:00.414 align:start position:0% this over the internet software<20:56:59.160> application<20:56:59.512> that<20:56:59.760> requests<20:57:00.176> the 20:57:00.414 --> 20:57:00.424 align:start position:0% software application that requests the 20:57:00.424 --> 20:57:02.750 align:start position:0% software application that requests the data<20:57:01.016> is<20:57:01.144> called<20:57:01.320> a<20:57:01.552> service<20:57:01.856> and<20:57:02.400> you<20:57:02.640> can 20:57:02.750 --> 20:57:02.760 align:start position:0% data is called a service and you can 20:57:02.760 --> 20:57:05.814 align:start position:0% data is called a service and you can tweak<20:57:03.240> these<20:57:04.016> way<20:57:04.256> in<20:57:04.800> most<20:57:04.976> of<20:57:05.104> your<20:57:05.280> browsers 20:57:05.814 --> 20:57:05.824 align:start position:0% tweak these way in most of your browsers 20:57:05.824 --> 20:57:08.750 align:start position:0% tweak these way in most of your browsers such<20:57:06.240> as<20:57:06.424> their<20:57:06.784> Google<20:57:07.504> Chrome<20:57:07.920> or<20:57:08.216> Firefox 20:57:08.750 --> 20:57:08.760 align:start position:0% such as their Google Chrome or Firefox 20:57:08.760 --> 20:57:11.094 align:start position:0% such as their Google Chrome or Firefox they<20:57:09.120> normally<20:57:09.424> have<20:57:09.656> ways<20:57:10.552> you<20:57:10.680> can<20:57:10.744> manage 20:57:11.094 --> 20:57:11.104 align:start position:0% they normally have ways you can manage 20:57:11.104 --> 20:57:15.046 align:start position:0% they normally have ways you can manage extensions<20:57:11.824> or<20:57:13.144> um<20:57:13.192> the<20:57:13.920> back<20:57:14.104> end 20:57:15.046 --> 20:57:15.056 align:start position:0% extensions or um the back end 20:57:15.056 --> 20:57:18.166 align:start position:0% extensions or um the back end to<20:57:15.896> a<20:57:16.080> grade<20:57:16.256> to<20:57:16.376> a<20:57:16.552> lesser<20:57:16.800> extent 20:57:18.166 --> 20:57:18.176 align:start position:0% to a grade to a lesser extent 20:57:18.176 --> 20:57:20.150 align:start position:0% to a grade to a lesser extent software<20:57:18.832> application<20:57:19.256> that<20:57:19.616> serves<20:57:19.976> the 20:57:20.150 --> 20:57:20.160 align:start position:0% software application that serves the 20:57:20.160 --> 20:57:23.094 align:start position:0% software application that serves the data<20:57:20.512> is<20:57:20.696> called<20:57:21.000> a<20:57:21.240> service<20:57:21.424> provider 20:57:23.094 --> 20:57:23.104 align:start position:0% data is called a service provider 20:57:23.104 --> 20:57:25.814 align:start position:0% data is called a service provider and<20:57:23.512> web<20:57:23.696> services<20:57:23.872> are<20:57:24.360> a<20:57:24.480> means<20:57:24.720> of<20:57:25.256> um 20:57:25.814 --> 20:57:25.824 align:start position:0% and web services are a means of um 20:57:25.824 --> 20:57:27.526 align:start position:0% and web services are a means of um interoperating<20:57:26.824> between<20:57:27.120> different 20:57:27.526 --> 20:57:27.536 align:start position:0% interoperating between different 20:57:27.536 --> 20:57:31.606 align:start position:0% interoperating between different software<20:57:28.440> systems 20:57:31.606 --> 20:57:31.616 align:start position:0% 20:57:31.616 --> 20:57:34.246 align:start position:0% the<20:57:32.160> software<20:57:32.576> applications<20:57:33.056> develop<20:57:33.720> using 20:57:34.246 --> 20:57:34.256 align:start position:0% the software applications develop using 20:57:34.256 --> 20:57:37.134 align:start position:0% the software applications develop using a<20:57:34.680> whole<20:57:34.800> variety<20:57:35.280> of<20:57:35.872> programmer<20:57:36.832> languages 20:57:37.134 --> 20:57:37.144 align:start position:0% a whole variety of programmer languages 20:57:37.144 --> 20:57:38.774 align:start position:0% a whole variety of programmer languages and<20:57:37.856> normally<20:57:38.160> you'll<20:57:38.400> have<20:57:38.512> somebody 20:57:38.774 --> 20:57:38.784 align:start position:0% and normally you'll have somebody 20:57:38.784 --> 20:57:41.630 align:start position:0% and normally you'll have somebody specializes<20:57:39.784> in<20:57:40.016> one<20:57:40.320> or<20:57:40.496> more<20:57:40.680> and<20:57:41.400> you<20:57:41.512> can 20:57:41.630 --> 20:57:41.640 align:start position:0% specializes in one or more and you can 20:57:41.640 --> 20:57:44.270 align:start position:0% specializes in one or more and you can see<20:57:41.824> a<20:57:42.000> few<20:57:42.176> in<20:57:42.600> the<20:57:42.720> Fig<20:57:42.960> there<20:57:43.320> some<20:57:44.040> have 20:57:44.270 --> 20:57:44.280 align:start position:0% see a few in the Fig there some have 20:57:44.280 --> 20:57:47.750 align:start position:0% see a few in the Fig there some have been<20:57:44.464> depreciated<20:57:45.176> such<20:57:45.832> as<20:57:46.016> Flash<20:57:46.440> and<20:57:47.400> due 20:57:47.750 --> 20:57:47.760 align:start position:0% been depreciated such as Flash and due 20:57:47.760 --> 20:57:51.822 align:start position:0% been depreciated such as Flash and due to<20:57:47.872> security<20:57:48.120> issues 20:57:51.822 --> 20:57:51.832 align:start position:0% 20:57:51.832 --> 20:57:54.166 align:start position:0% season<20:57:52.376> for<20:57:52.744> applications<20:57:53.216> want<20:57:53.576> to<20:57:53.824> exchange 20:57:54.166 --> 20:57:54.176 align:start position:0% season for applications want to exchange 20:57:54.176 --> 20:57:56.030 align:start position:0% season for applications want to exchange data<20:57:54.656> they<20:57:54.896> should<20:57:55.144> be<20:57:55.320> able<20:57:55.376> to<20:57:55.504> communicate 20:57:56.030 --> 20:57:56.040 align:start position:0% data they should be able to communicate 20:57:56.040 --> 20:57:59.270 align:start position:0% data they should be able to communicate with<20:57:56.280> each<20:57:56.464> other<20:57:56.656> this<20:57:57.656> may<20:57:57.960> possibly<20:57:58.552> be 20:57:59.270 --> 20:57:59.280 align:start position:0% with each other this may possibly be 20:57:59.280 --> 20:58:01.542 align:start position:0% with each other this may possibly be where<20:57:59.512> you<20:57:59.872> have<20:58:00.536> become<20:58:00.784> involved<20:58:01.192> as<20:58:01.376> the 20:58:01.542 --> 20:58:01.552 align:start position:0% where you have become involved as the 20:58:01.552 --> 20:58:03.646 align:start position:0% where you have become involved as the network<20:58:01.744> engineer 20:58:03.646 --> 20:58:03.656 align:start position:0% network engineer 20:58:03.656 --> 20:58:05.750 align:start position:0% network engineer data<20:58:04.256> exchange<20:58:04.744> shouldn't<20:58:05.104> depend<20:58:05.400> on<20:58:05.512> any 20:58:05.750 --> 20:58:05.760 align:start position:0% data exchange shouldn't depend on any 20:58:05.760 --> 20:58:08.094 align:start position:0% data exchange shouldn't depend on any particular<20:58:06.176> programming<20:58:06.896> language 20:58:08.094 --> 20:58:08.104 align:start position:0% particular programming language 20:58:08.104 --> 20:58:09.350 align:start position:0% particular programming language so<20:58:08.280> there's<20:58:08.464> a<20:58:08.640> need<20:58:08.696> for<20:58:08.872> a<20:58:09.000> common<20:58:09.056> language 20:58:09.350 --> 20:58:09.360 align:start position:0% so there's a need for a common language 20:58:09.360 --> 20:58:10.734 align:start position:0% so there's a need for a common language that<20:58:09.784> allow<20:58:10.016> different<20:58:10.256> software 20:58:10.734 --> 20:58:10.744 align:start position:0% that allow different software 20:58:10.744 --> 20:58:12.710 align:start position:0% that allow different software applications<20:58:11.216> to<20:58:11.576> send<20:58:11.760> and<20:58:11.936> receive<20:58:12.296> data 20:58:12.710 --> 20:58:12.720 align:start position:0% applications to send and receive data 20:58:12.720 --> 20:58:14.502 align:start position:0% applications to send and receive data over<20:58:12.896> the<20:58:13.144> web 20:58:14.502 --> 20:58:14.512 align:start position:0% over the web 20:58:14.512 --> 20:58:17.270 align:start position:0% over the web most<20:58:15.120> types<20:58:15.480> of<20:58:15.536> software<20:58:15.960> can<20:58:16.496> interpret 20:58:17.270 --> 20:58:17.280 align:start position:0% most types of software can interpret 20:58:17.280 --> 20:58:20.094 align:start position:0% most types of software can interpret what's<20:58:17.512> known<20:58:17.760> as<20:58:17.936> XML<20:58:18.832> tags 20:58:20.094 --> 20:58:20.104 align:start position:0% what's known as XML tags 20:58:20.104 --> 20:58:22.006 align:start position:0% what's known as XML tags this<20:58:20.640> stands<20:58:21.000> for<20:58:21.120> extensible<20:58:21.656> Market 20:58:22.006 --> 20:58:22.016 align:start position:0% this stands for extensible Market 20:58:22.016 --> 20:58:24.230 align:start position:0% this stands for extensible Market bandwidge<20:58:22.920> which<20:58:23.336> you<20:58:23.464> can<20:58:23.576> learn<20:58:23.760> if<20:58:23.936> you<20:58:24.120> so 20:58:24.230 --> 20:58:24.240 align:start position:0% bandwidge which you can learn if you so 20:58:24.240 --> 20:58:25.734 align:start position:0% bandwidge which you can learn if you so choose 20:58:25.734 --> 20:58:25.744 align:start position:0% choose 20:58:25.744 --> 20:58:27.526 align:start position:0% choose it's<20:58:26.040> a<20:58:26.280> standard<20:58:26.512> language<20:58:26.696> for<20:58:27.000> web-based 20:58:27.526 --> 20:58:27.536 align:start position:0% it's a standard language for web-based 20:58:27.536 --> 20:58:29.630 align:start position:0% it's a standard language for web-based applications<20:58:27.960> to<20:58:28.552> communicate<20:58:29.104> with<20:58:29.464> one 20:58:29.630 --> 20:58:29.640 align:start position:0% applications to communicate with one 20:58:29.640 --> 20:58:30.646 align:start position:0% applications to communicate with one another 20:58:30.646 --> 20:58:30.656 align:start position:0% another 20:58:30.656 --> 20:58:33.646 align:start position:0% another the<20:58:31.080> exchange<20:58:31.320> of<20:58:31.552> data<20:58:31.976> happens<20:58:32.160> through<20:58:32.760> XML 20:58:33.646 --> 20:58:33.656 align:start position:0% the exchange of data happens through XML 20:58:33.656 --> 20:58:36.230 align:start position:0% the exchange of data happens through XML files 20:58:36.230 --> 20:58:36.240 align:start position:0% 20:58:36.240 --> 20:58:38.990 align:start position:0% XML<20:58:37.016> is<20:58:37.320> a<20:58:37.504> markup<20:58:37.856> language<20:58:38.160> it<20:58:38.512> defines<20:58:38.872> a 20:58:38.990 --> 20:58:39.000 align:start position:0% XML is a markup language it defines a 20:58:39.000 --> 20:58:40.910 align:start position:0% XML is a markup language it defines a set<20:58:39.120> of<20:58:39.240> rules<20:58:39.480> for<20:58:39.656> encoding<20:58:40.144> documents<20:58:40.616> in<20:58:40.744> a 20:58:40.910 --> 20:58:40.920 align:start position:0% set of rules for encoding documents in a 20:58:40.920 --> 20:58:43.366 align:start position:0% set of rules for encoding documents in a format<20:58:41.280> that<20:58:41.512> we<20:58:41.696> can<20:58:41.824> read<20:58:42.056> as<20:58:42.720> humans 20:58:43.366 --> 20:58:43.376 align:start position:0% format that we can read as humans 20:58:43.376 --> 20:58:45.470 align:start position:0% format that we can read as humans generally<20:58:44.216> you<20:58:44.400> need<20:58:44.576> to<20:58:44.640> be<20:58:44.760> a<20:58:44.936> programmer<20:58:45.360> to 20:58:45.470 --> 20:58:45.480 align:start position:0% generally you need to be a programmer to 20:58:45.480 --> 20:58:47.390 align:start position:0% generally you need to be a programmer to understand<20:58:45.720> what<20:58:46.144> they<20:58:46.320> mean<20:58:46.496> but<20:58:47.040> it<20:58:47.216> could 20:58:47.390 --> 20:58:47.400 align:start position:0% understand what they mean but it could 20:58:47.400 --> 20:58:51.430 align:start position:0% understand what they mean but it could also<20:58:47.696> be<20:58:47.824> read<20:58:48.144> by<20:58:49.144> the<20:58:49.256> machines 20:58:51.430 --> 20:58:51.440 align:start position:0% also be read by the machines 20:58:51.440 --> 20:58:54.886 align:start position:0% also be read by the machines so<20:58:52.440> here's<20:58:52.744> an<20:58:52.800> example<20:58:53.160> of<20:58:53.464> an<20:58:53.640> XML<20:58:54.176> file<20:58:54.656> you 20:58:54.886 --> 20:58:54.896 align:start position:0% so here's an example of an XML file you 20:58:54.896 --> 20:58:56.990 align:start position:0% so here's an example of an XML file you can<20:58:55.080> see<20:58:55.192> it's<20:58:55.376> marked<20:58:55.856> as<20:58:55.976> XML<20:58:56.512> at<20:58:56.760> the<20:58:56.872> top 20:58:56.990 --> 20:58:57.000 align:start position:0% can see it's marked as XML at the top 20:58:57.000 --> 20:59:00.526 align:start position:0% can see it's marked as XML at the top the<20:58:57.960> version<20:58:58.192> and<20:58:59.040> then<20:58:59.160> there's<20:58:59.400> various 20:59:00.526 --> 20:59:00.536 align:start position:0% the version and then there's various 20:59:00.536 --> 20:59:03.646 align:start position:0% the version and then there's various um prompts<20:59:01.080> within<20:59:01.696> the<20:59:02.696> greater<20:59:03.240> than<20:59:03.360> and 20:59:03.646 --> 20:59:03.656 align:start position:0% um prompts within the greater than and 20:59:03.656 --> 20:59:07.494 align:start position:0% um prompts within the greater than and less<20:59:03.896> than<20:59:04.080> markers<20:59:05.040> and<20:59:06.000> also<20:59:06.360> the<20:59:07.256> actual 20:59:07.494 --> 20:59:07.504 align:start position:0% less than markers and also the actual 20:59:07.504 --> 20:59:11.414 align:start position:0% less than markers and also the actual text<20:59:07.744> in<20:59:08.040> between<20:59:08.480> Network<20:59:09.480> 100<20:59:10.144> status<20:59:10.800> pass 20:59:11.414 --> 20:59:11.424 align:start position:0% text in between Network 100 status pass 20:59:11.424 --> 20:59:17.390 align:start position:0% text in between Network 100 status pass subject<20:59:12.424> Hardware<20:59:12.784> Mach<20:59:13.256> 100 20:59:17.390 --> 20:59:17.400 align:start position:0% 20:59:17.400 --> 20:59:19.542 align:start position:0% so<20:59:17.824> you've<20:59:17.936> seen<20:59:18.056> an<20:59:18.240> example<20:59:18.480> easy<20:59:19.080> to<20:59:19.376> read 20:59:19.542 --> 20:59:19.552 align:start position:0% so you've seen an example easy to read 20:59:19.552 --> 20:59:21.886 align:start position:0% so you've seen an example easy to read it<20:59:19.976> once<20:59:20.336> obviously<20:59:21.120> once<20:59:21.360> you've<20:59:21.480> learned 20:59:21.886 --> 20:59:21.896 align:start position:0% it once obviously once you've learned 20:59:21.896 --> 20:59:23.630 align:start position:0% it once obviously once you've learned what<20:59:22.376> it<20:59:22.496> all<20:59:22.616> means<20:59:22.920> and<20:59:23.040> how<20:59:23.216> it<20:59:23.336> works<20:59:23.512> but 20:59:23.630 --> 20:59:23.640 align:start position:0% what it all means and how it works but 20:59:23.640 --> 20:59:26.390 align:start position:0% what it all means and how it works but it's<20:59:23.824> also<20:59:24.000> easy<20:59:24.296> for<20:59:24.536> the<20:59:24.720> machine<20:59:24.896> to<20:59:25.504> read 20:59:26.390 --> 20:59:26.400 align:start position:0% it's also easy for the machine to read 20:59:26.400 --> 20:59:28.182 align:start position:0% it's also easy for the machine to read also 20:59:28.182 --> 20:59:28.192 align:start position:0% also 20:59:28.192 --> 20:59:29.814 align:start position:0% also allows<20:59:28.920> you<20:59:28.920> to<20:59:29.104> see<20:59:29.216> what's<20:59:29.400> been<20:59:29.576> sent 20:59:29.814 --> 20:59:29.824 align:start position:0% allows you to see what's been sent 20:59:29.824 --> 20:59:33.822 align:start position:0% allows you to see what's been sent between<20:59:30.120> the<20:59:30.480> web-based<20:59:31.080> applications 20:59:33.822 --> 20:59:33.832 align:start position:0% 20:59:33.832 --> 20:59:36.414 align:start position:0% web<20:59:34.376> services<20:59:34.616> web<20:59:35.280> applications<20:59:35.824> can<20:59:36.240> send 20:59:36.414 --> 20:59:36.424 align:start position:0% web services web applications can send 20:59:36.424 --> 20:59:38.862 align:start position:0% web services web applications can send data<20:59:36.832> using<20:59:37.080> the<20:59:37.320> XML<20:59:37.744> format<20:59:38.216> they<20:59:38.464> can<20:59:38.640> also 20:59:38.862 --> 20:59:38.872 align:start position:0% data using the XML format they can also 20:59:38.872 --> 20:59:42.414 align:start position:0% data using the XML format they can also retrieve<20:59:39.424> data<20:59:39.784> from<20:59:39.960> an<20:59:40.144> XML<20:59:40.552> file 20:59:42.414 --> 20:59:42.424 align:start position:0% retrieve data from an XML file 20:59:42.424 --> 20:59:44.502 align:start position:0% retrieve data from an XML file a<20:59:42.832> standard<20:59:43.192> web<20:59:43.320> service<20:59:43.616> uses<20:59:44.336> the 20:59:44.502 --> 20:59:44.512 align:start position:0% a standard web service uses the 20:59:44.512 --> 20:59:47.270 align:start position:0% a standard web service uses the following<20:59:44.824> components<20:59:45.480> soap 20:59:47.270 --> 20:59:47.280 align:start position:0% following components soap 20:59:47.280 --> 20:59:50.150 align:start position:0% following components soap this<20:59:47.696> stands<20:59:48.056> for<20:59:48.296> a<20:59:48.832> simple<20:59:49.320> object<20:59:49.800> access 20:59:50.150 --> 20:59:50.160 align:start position:0% this stands for a simple object access 20:59:50.160 --> 20:59:51.710 align:start position:0% this stands for a simple object access protocol 20:59:51.710 --> 20:59:51.720 align:start position:0% protocol 20:59:51.720 --> 20:59:53.686 align:start position:0% protocol this<20:59:52.192> is<20:59:52.320> actually<20:59:52.496> used<20:59:52.800> to<20:59:52.976> transfer<20:59:53.464> the 20:59:53.686 --> 20:59:53.696 align:start position:0% this is actually used to transfer the 20:59:53.696 --> 20:59:56.750 align:start position:0% this is actually used to transfer the data 20:59:56.750 --> 20:59:56.760 align:start position:0% 20:59:56.760 --> 20:59:59.326 align:start position:0% uddi<20:59:57.424> stands<20:59:58.144> for<20:59:58.192> Universal<20:59:58.856> description 20:59:59.326 --> 20:59:59.336 align:start position:0% uddi stands for Universal description 20:59:59.336 --> 21:00:01.790 align:start position:0% uddi stands for Universal description Discovery<21:00:00.000> and<21:00:00.296> integration 21:00:01.790 --> 21:00:01.800 align:start position:0% Discovery and integration 21:00:01.800 --> 21:00:03.886 align:start position:0% Discovery and integration directory<21:00:02.640> that<21:00:02.760> defines<21:00:03.176> which<21:00:03.480> Software 21:00:03.886 --> 21:00:03.896 align:start position:0% directory that defines which Software 21:00:03.896 --> 21:00:05.990 align:start position:0% directory that defines which Software System<21:00:04.144> should<21:00:04.744> be<21:00:04.920> contacted<21:00:05.336> for<21:00:05.696> which 21:00:05.990 --> 21:00:06.000 align:start position:0% System should be contacted for which 21:00:06.000 --> 21:00:09.430 align:start position:0% System should be contacted for which type<21:00:06.240> of<21:00:06.424> data 21:00:09.430 --> 21:00:09.440 align:start position:0% 21:00:09.440 --> 21:00:12.886 align:start position:0% wsdl<21:00:10.512> stands<21:00:11.512> for<21:00:11.576> web<21:00:11.872> services<21:00:12.056> description 21:00:12.886 --> 21:00:12.896 align:start position:0% wsdl stands for web services description 21:00:12.896 --> 21:00:14.150 align:start position:0% wsdl stands for web services description language 21:00:14.150 --> 21:00:14.160 align:start position:0% language 21:00:14.160 --> 21:00:15.774 align:start position:0% language used<21:00:14.640> for<21:00:14.824> describing<21:00:15.360> the<21:00:15.600> services 21:00:15.774 --> 21:00:15.784 align:start position:0% used for describing the services 21:00:15.784 --> 21:00:18.710 align:start position:0% used for describing the services available 21:00:18.710 --> 21:00:18.720 align:start position:0% 21:00:18.720 --> 21:00:22.134 align:start position:0% how<21:00:19.080> are<21:00:19.256> web<21:00:19.440> service<21:00:19.616> works<21:00:20.280> it<21:00:21.056> uses<21:00:21.424> XML<21:00:22.016> to 21:00:22.134 --> 21:00:22.144 align:start position:0% how are web service works it uses XML to 21:00:22.144 --> 21:00:24.710 align:start position:0% how are web service works it uses XML to tag<21:00:22.320> the<21:00:22.552> data<21:00:22.976> soap<21:00:23.512> to<21:00:23.696> transfer<21:00:24.056> the<21:00:24.296> data 21:00:24.710 --> 21:00:24.720 align:start position:0% tag the data soap to transfer the data 21:00:24.720 --> 21:00:27.350 align:start position:0% tag the data soap to transfer the data and<21:00:25.256> then<21:00:25.640> wsdl<21:00:26.640> to<21:00:26.872> describe<21:00:27.240> the 21:00:27.350 --> 21:00:27.360 align:start position:0% and then wsdl to describe the 21:00:27.360 --> 21:00:29.710 align:start position:0% and then wsdl to describe the availability<21:00:27.784> of<21:00:28.144> a<21:00:28.256> service<21:00:28.464> it's<21:00:29.464> worth 21:00:29.710 --> 21:00:29.720 align:start position:0% availability of a service it's worth 21:00:29.720 --> 21:00:31.734 align:start position:0% availability of a service it's worth writing<21:00:30.720> this<21:00:30.832> out<21:00:31.016> if<21:00:31.192> you<21:00:31.376> haven't<21:00:31.504> already 21:00:31.734 --> 21:00:31.744 align:start position:0% writing this out if you haven't already 21:00:31.744 --> 21:00:33.710 align:start position:0% writing this out if you haven't already if<21:00:32.104> you're<21:00:32.216> not<21:00:32.336> making<21:00:32.464> notes<21:00:33.000> so<21:00:33.536> you 21:00:33.710 --> 21:00:33.720 align:start position:0% if you're not making notes so you 21:00:33.720 --> 21:00:35.454 align:start position:0% if you're not making notes so you understand<21:00:33.896> which 21:00:35.454 --> 21:00:35.464 align:start position:0% understand which 21:00:35.464 --> 21:00:38.390 align:start position:0% understand which um part<21:00:36.144> performs<21:00:37.144> which<21:00:37.440> service<21:00:37.800> because 21:00:38.390 --> 21:00:38.400 align:start position:0% um part performs which service because 21:00:38.400 --> 21:00:39.710 align:start position:0% um part performs which service because this<21:00:38.696> is<21:00:38.824> the<21:00:39.000> most<21:00:39.120> likely<21:00:39.424> thing<21:00:39.536> you're 21:00:39.710 --> 21:00:39.720 align:start position:0% this is the most likely thing you're 21:00:39.720 --> 21:00:43.606 align:start position:0% this is the most likely thing you're going<21:00:39.896> to<21:00:40.016> be<21:00:40.144> asked<21:00:41.040> a<21:00:41.104> question<21:00:41.280> about 21:00:43.606 --> 21:00:43.616 align:start position:0% going to be asked a question about 21:00:43.616 --> 21:00:45.542 align:start position:0% going to be asked a question about so<21:00:44.040> we've<21:00:44.216> looked<21:00:44.400> briefly<21:00:44.760> at<21:00:44.872> web<21:00:45.056> services 21:00:45.542 --> 21:00:45.552 align:start position:0% so we've looked briefly at web services 21:00:45.552 --> 21:00:47.990 align:start position:0% so we've looked briefly at web services XML<21:00:46.552> programming<21:00:47.216> languages<21:00:47.512> and<21:00:47.824> web 21:00:47.990 --> 21:00:48.000 align:start position:0% XML programming languages and web 21:00:48.000 --> 21:00:48.966 align:start position:0% XML programming languages and web services 21:00:48.966 --> 21:00:48.976 align:start position:0% services 21:00:48.976 --> 21:00:52.542 align:start position:0% services components<21:00:49.976> how<21:00:50.824> web<21:00:51.056> service<21:00:51.296> works<21:00:51.896> that's 21:00:52.542 --> 21:00:52.552 align:start position:0% components how web service works that's 21:00:52.552 --> 21:00:58.690 align:start position:0% components how web service works that's all<21:00:52.744> for<21:00:52.976> now<21:00:53.160> thanks<21:00:53.512> for<21:00:53.696> listening 21:00:58.690 --> 21:00:58.700 align:start position:0% 21:00:58.700 --> 21:01:14.566 align:start position:0% [Music] 21:01:14.566 --> 21:01:14.576 align:start position:0% 21:01:14.576 --> 21:01:17.454 align:start position:0% welcome<21:01:15.056> to<21:01:15.296> module<21:01:15.720> 16<21:01:15.896> lesson<21:01:16.680> 2<21:01:16.800> unified 21:01:17.454 --> 21:01:17.464 align:start position:0% welcome to module 16 lesson 2 unified 21:01:17.464 --> 21:01:19.542 align:start position:0% welcome to module 16 lesson 2 unified communication 21:01:19.542 --> 21:01:19.552 align:start position:0% communication 21:01:19.552 --> 21:01:23.206 align:start position:0% communication just<21:01:20.040> call<21:01:20.280> this<21:01:20.512> UC<21:01:20.936> usually<21:01:21.720> to<21:01:22.256> save<21:01:22.856> a<21:01:23.104> lot 21:01:23.206 --> 21:01:23.216 align:start position:0% just call this UC usually to save a lot 21:01:23.216 --> 21:01:25.846 align:start position:0% just call this UC usually to save a lot of<21:01:23.336> breath<21:01:23.640> as<21:01:24.424> with<21:01:24.656> everything 21:01:25.846 --> 21:01:25.856 align:start position:0% of breath as with everything 21:01:25.856 --> 21:01:27.710 align:start position:0% of breath as with everything uh<21:01:26.576> different<21:01:26.824> media<21:01:27.240> the<21:01:27.536> same 21:01:27.710 --> 21:01:27.720 align:start position:0% uh different media the same 21:01:27.720 --> 21:01:30.350 align:start position:0% uh different media the same communication<21:01:28.616> we<21:01:28.976> look<21:01:29.160> at<21:01:29.400> and<21:01:29.824> presence 21:01:30.350 --> 21:01:30.360 align:start position:0% communication we look at and presence 21:01:30.360 --> 21:01:34.966 align:start position:0% communication we look at and presence this<21:01:30.896> is<21:01:31.016> a<21:01:31.256> real<21:01:31.920> snapshot<21:01:32.760> of<21:01:33.056> a<21:01:33.536> pretty<21:01:34.080> huge 21:01:34.966 --> 21:01:34.976 align:start position:0% this is a real snapshot of a pretty huge 21:01:34.976 --> 21:01:39.110 align:start position:0% this is a real snapshot of a pretty huge subject<21:01:35.824> area<21:01:36.192> so<21:01:37.192> as<21:01:37.744> with<21:01:37.976> a<21:01:38.160> lot<21:01:38.280> of<21:01:38.464> network 21:01:39.110 --> 21:01:39.120 align:start position:0% subject area so as with a lot of network 21:01:39.120 --> 21:01:41.270 align:start position:0% subject area so as with a lot of network plus<21:01:39.480> stuff<21:01:39.832> especially<21:01:40.552> the<21:01:40.744> new<21:01:40.856> stuff<21:01:41.104> in 21:01:41.270 --> 21:01:41.280 align:start position:0% plus stuff especially the new stuff in 21:01:41.280 --> 21:01:43.310 align:start position:0% plus stuff especially the new stuff in the<21:01:41.336> syllabus<21:01:41.760> you<21:01:42.360> just<21:01:42.536> expect<21:01:42.784> it<21:01:43.080> to<21:01:43.192> have 21:01:43.310 --> 21:01:43.320 align:start position:0% the syllabus you just expect it to have 21:01:43.320 --> 21:01:45.526 align:start position:0% the syllabus you just expect it to have an<21:01:43.504> awareness<21:01:43.856> of<21:01:44.040> it 21:01:45.526 --> 21:01:45.536 align:start position:0% an awareness of it 21:01:45.536 --> 21:01:48.230 align:start position:0% an awareness of it you<21:01:46.144> see<21:01:46.440> is<21:01:46.744> the<21:01:46.856> integration<21:01:47.280> of<21:01:47.760> a<21:01:48.000> whole 21:01:48.230 --> 21:01:48.240 align:start position:0% you see is the integration of a whole 21:01:48.240 --> 21:01:50.230 align:start position:0% you see is the integration of a whole bunch<21:01:48.600> of<21:01:48.832> communication 21:01:50.230 --> 21:01:50.240 align:start position:0% bunch of communication 21:01:50.240 --> 21:01:53.686 align:start position:0% bunch of communication methods<21:01:51.240> including<21:01:51.656> voice<21:01:51.896> video<21:01:52.320> and<21:01:53.216> data 21:01:53.686 --> 21:01:53.696 align:start position:0% methods including voice video and data 21:01:53.696 --> 21:01:56.454 align:start position:0% methods including voice video and data all<21:01:54.424> goes<21:01:54.720> into<21:01:54.784> your<21:01:55.016> IP<21:01:55.376> network<21:01:55.680> which<21:01:56.280> is 21:01:56.454 --> 21:01:56.464 align:start position:0% all goes into your IP network which is 21:01:56.464 --> 21:01:59.206 align:start position:0% all goes into your IP network which is kind<21:01:56.760> of<21:01:56.872> tied<21:01:57.120> in<21:01:57.296> with<21:01:57.656> the<21:01:58.256> cloud<21:01:58.440> now<21:01:58.800> and 21:01:59.206 --> 21:01:59.216 align:start position:0% kind of tied in with the cloud now and 21:01:59.216 --> 21:02:00.886 align:start position:0% kind of tied in with the cloud now and how<21:01:59.464> everything<21:01:59.576> would<21:02:00.176> be<21:02:00.296> you'd<21:02:00.720> expect 21:02:00.886 --> 21:02:00.896 align:start position:0% how everything would be you'd expect 21:02:00.896 --> 21:02:03.470 align:start position:0% how everything would be you'd expect everything<21:02:01.192> to<21:02:01.552> be<21:02:01.680> working<21:02:01.920> over<21:02:02.216> IP 21:02:03.470 --> 21:02:03.480 align:start position:0% everything to be working over IP 21:02:03.480 --> 21:02:06.286 align:start position:0% everything to be working over IP and<21:02:04.080> over<21:02:04.256> multiple<21:02:04.800> devices<21:02:05.280> depending<21:02:06.000> on 21:02:06.286 --> 21:02:06.296 align:start position:0% and over multiple devices depending on 21:02:06.296 --> 21:02:08.094 align:start position:0% and over multiple devices depending on where<21:02:06.656> you<21:02:06.832> are<21:02:07.016> and<21:02:07.192> how<21:02:07.440> you<21:02:07.552> want<21:02:07.680> things<21:02:07.856> to 21:02:08.094 --> 21:02:08.104 align:start position:0% where you are and how you want things to 21:02:08.104 --> 21:02:09.110 align:start position:0% where you are and how you want things to work 21:02:09.110 --> 21:02:09.120 align:start position:0% work 21:02:09.120 --> 21:02:11.350 align:start position:0% work the<21:02:09.536> idea<21:02:09.784> is<21:02:09.896> it<21:02:10.080> simplifies<21:02:10.552> real-time 21:02:11.350 --> 21:02:11.360 align:start position:0% the idea is it simplifies real-time 21:02:11.360 --> 21:02:15.230 align:start position:0% the idea is it simplifies real-time Communications<21:02:12.360> at<21:02:12.720> an<21:02:12.960> Enterprise<21:02:13.144> level 21:02:15.230 --> 21:02:15.240 align:start position:0% Communications at an Enterprise level 21:02:15.240 --> 21:02:17.990 align:start position:0% Communications at an Enterprise level including<21:02:16.144> it<21:02:16.800> can<21:02:16.976> work<21:02:17.160> it<21:02:17.400> doesn't<21:02:17.640> have<21:02:17.872> to 21:02:17.990 --> 21:02:18.000 align:start position:0% including it can work it doesn't have to 21:02:18.000 --> 21:02:19.494 align:start position:0% including it can work it doesn't have to be<21:02:18.120> Enterprise<21:02:18.296> by<21:02:18.784> the<21:02:18.896> way<21:02:18.960> it<21:02:19.144> can<21:02:19.256> be<21:02:19.440> any 21:02:19.494 --> 21:02:19.504 align:start position:0% be Enterprise by the way it can be any 21:02:19.504 --> 21:02:21.822 align:start position:0% be Enterprise by the way it can be any small<21:02:19.800> Network<21:02:20.104> including<21:02:20.824> homes 21:02:21.822 --> 21:02:21.832 align:start position:0% small Network including homes 21:02:21.832 --> 21:02:24.886 align:start position:0% small Network including homes making<21:02:22.440> calls<21:02:22.976> instant<21:02:23.400> messages<21:02:23.696> having<21:02:24.600> a 21:02:24.886 --> 21:02:24.896 align:start position:0% making calls instant messages having a 21:02:24.896 --> 21:02:28.134 align:start position:0% making calls instant messages having a video<21:02:25.192> or<21:02:25.976> audio<21:02:26.216> conference<21:02:27.056> sharing<21:02:27.960> your 21:02:28.134 --> 21:02:28.144 align:start position:0% video or audio conference sharing your 21:02:28.144 --> 21:02:30.230 align:start position:0% video or audio conference sharing your desktop<21:02:28.496> with<21:02:28.800> whoever<21:02:29.104> needs<21:02:29.464> to<21:02:29.576> log<21:02:29.872> in<21:02:30.056> and 21:02:30.230 --> 21:02:30.240 align:start position:0% desktop with whoever needs to log in and 21:02:30.240 --> 21:02:31.910 align:start position:0% desktop with whoever needs to log in and troubleshoot 21:02:31.910 --> 21:02:31.920 align:start position:0% troubleshoot 21:02:31.920 --> 21:02:34.734 align:start position:0% troubleshoot presence<21:02:32.872> information 21:02:34.734 --> 21:02:34.744 align:start position:0% presence information 21:02:34.744 --> 21:02:37.326 align:start position:0% presence information so<21:02:35.464> you<21:02:35.760> see<21:02:36.056> it's<21:02:36.536> all<21:02:36.784> forms<21:02:37.080> of 21:02:37.326 --> 21:02:37.336 align:start position:0% so you see it's all forms of 21:02:37.336 --> 21:02:41.230 align:start position:0% so you see it's all forms of communications<21:02:38.336> are<21:02:38.760> exchanged<21:02:39.296> over<21:02:39.976> IP 21:02:41.230 --> 21:02:41.240 align:start position:0% communications are exchanged over IP 21:02:41.240 --> 21:02:44.094 align:start position:0% communications are exchanged over IP integrates<21:02:42.240> real-time<21:02:42.832> Communications<21:02:43.616> with 21:02:44.094 --> 21:02:44.104 align:start position:0% integrates real-time Communications with 21:02:44.104 --> 21:02:46.734 align:start position:0% integrates real-time Communications with non-real<21:02:44.640> time<21:02:44.824> such<21:02:45.176> as<21:02:45.552> accessing<21:02:46.552> your 21:02:46.734 --> 21:02:46.744 align:start position:0% non-real time such as accessing your 21:02:46.744 --> 21:02:48.246 align:start position:0% non-real time such as accessing your voicemail<21:02:47.160> if<21:02:47.576> you're<21:02:47.696> not<21:02:47.872> available 21:02:48.246 --> 21:02:48.256 align:start position:0% voicemail if you're not available 21:02:48.256 --> 21:02:51.910 align:start position:0% voicemail if you're not available accessing<21:02:49.256> your<21:02:49.440> email<21:02:50.056> text<21:02:51.056> messages 21:02:51.910 --> 21:02:51.920 align:start position:0% accessing your email text messages 21:02:51.920 --> 21:02:54.414 align:start position:0% accessing your email text messages faxes<21:02:52.920> I<21:02:53.280> don't<21:02:53.464> even<21:02:53.576> know<21:02:53.760> who<21:02:53.936> uses<21:02:54.240> those 21:02:54.414 --> 21:02:54.424 align:start position:0% faxes I don't even know who uses those 21:02:54.424 --> 21:02:56.094 align:start position:0% faxes I don't even know who uses those now 21:02:56.094 --> 21:02:56.104 align:start position:0% now 21:02:56.104 --> 21:02:58.430 align:start position:0% now it<21:02:56.576> allows<21:02:57.120> you<21:02:57.176> to<21:02:57.360> send<21:02:57.656> messages<21:02:57.896> on<21:02:58.256> one 21:02:58.430 --> 21:02:58.440 align:start position:0% it allows you to send messages on one 21:02:58.440 --> 21:03:00.246 align:start position:0% it allows you to send messages on one medium<21:02:58.800> but<21:02:58.976> receive<21:02:59.400> a<21:02:59.512> response<21:02:59.936> to<21:03:00.056> another 21:03:00.246 --> 21:03:00.256 align:start position:0% medium but receive a response to another 21:03:00.256 --> 21:03:02.862 align:start position:0% medium but receive a response to another an<21:03:01.256> example<21:03:01.552> is<21:03:01.800> when<21:03:02.040> you<21:03:02.160> send<21:03:02.400> somebody<21:03:02.640> a 21:03:02.862 --> 21:03:02.872 align:start position:0% an example is when you send somebody a 21:03:02.872 --> 21:03:04.366 align:start position:0% an example is when you send somebody a voicemail<21:03:03.296> you've<21:03:03.896> probably<21:03:04.016> had<21:03:04.192> this 21:03:04.366 --> 21:03:04.376 align:start position:0% voicemail you've probably had this 21:03:04.376 --> 21:03:06.526 align:start position:0% voicemail you've probably had this happen<21:03:04.552> before<21:03:04.920> or<21:03:05.824> you've<21:03:06.000> left<21:03:06.120> a<21:03:06.296> voicemail 21:03:06.526 --> 21:03:06.536 align:start position:0% happen before or you've left a voicemail 21:03:06.536 --> 21:03:08.686 align:start position:0% happen before or you've left a voicemail and<21:03:06.784> it<21:03:06.960> says<21:03:07.192> it<21:03:07.320> will<21:03:07.440> send<21:03:07.616> the<21:03:07.800> user<21:03:08.216> a<21:03:08.464> text 21:03:08.686 --> 21:03:08.696 align:start position:0% and it says it will send the user a text 21:03:08.696 --> 21:03:11.150 align:start position:0% and it says it will send the user a text or<21:03:09.000> email 21:03:11.150 --> 21:03:11.160 align:start position:0% or email 21:03:11.160 --> 21:03:13.310 align:start position:0% or email you<21:03:11.824> can<21:03:11.936> retrieve 21:03:13.310 --> 21:03:13.320 align:start position:0% you can retrieve 21:03:13.320 --> 21:03:15.110 align:start position:0% you can retrieve um<21:03:13.376> check<21:03:14.104> and<21:03:14.280> retrieve<21:03:14.640> emails<21:03:15.056> or 21:03:15.110 --> 21:03:15.120 align:start position:0% um check and retrieve emails or 21:03:15.120 --> 21:03:17.030 align:start position:0% um check and retrieve emails or voicemails<21:03:15.600> using<21:03:15.896> any<21:03:16.080> Communications<21:03:16.616> at 21:03:17.030 --> 21:03:17.040 align:start position:0% voicemails using any Communications at 21:03:17.040 --> 21:03:18.166 align:start position:0% voicemails using any Communications at any<21:03:17.216> time 21:03:18.166 --> 21:03:18.176 align:start position:0% any time 21:03:18.176 --> 21:03:22.006 align:start position:0% any time our<21:03:18.656> presence<21:03:19.080> is<21:03:19.320> a<21:03:19.552> component<21:03:20.040> of<21:03:20.464> UC<21:03:21.016> shows 21:03:22.006 --> 21:03:22.016 align:start position:0% our presence is a component of UC shows 21:03:22.016 --> 21:03:23.862 align:start position:0% our presence is a component of UC shows the<21:03:22.080> present<21:03:22.376> status<21:03:22.616> of<21:03:23.040> a<21:03:23.216> user<21:03:23.464> in<21:03:23.696> real 21:03:23.862 --> 21:03:23.872 align:start position:0% the present status of a user in real 21:03:23.872 --> 21:03:26.270 align:start position:0% the present status of a user in real time<21:03:24.120> whether<21:03:25.080> they<21:03:25.320> are<21:03:25.504> available<21:03:25.680> and 21:03:26.270 --> 21:03:26.280 align:start position:0% time whether they are available and 21:03:26.280 --> 21:03:28.542 align:start position:0% time whether they are available and available<21:03:26.576> where<21:03:27.240> they<21:03:27.424> are<21:03:27.536> located<21:03:27.784> if<21:03:28.376> if 21:03:28.542 --> 21:03:28.552 align:start position:0% available where they are located if if 21:03:28.552 --> 21:03:31.910 align:start position:0% available where they are located if if you've<21:03:28.920> enabled<21:03:29.656> geoip<21:03:30.656> tracking 21:03:31.910 --> 21:03:31.920 align:start position:0% you've enabled geoip tracking 21:03:31.920 --> 21:03:34.910 align:start position:0% you've enabled geoip tracking or<21:03:32.280> Geo<21:03:32.576> tracking<21:03:32.936> sorry 21:03:34.910 --> 21:03:34.920 align:start position:0% or Geo tracking sorry 21:03:34.920 --> 21:03:37.134 align:start position:0% or Geo tracking sorry allows<21:03:35.512> users<21:03:35.824> to<21:03:36.056> communicate<21:03:36.480> seamlessly 21:03:37.134 --> 21:03:37.144 align:start position:0% allows users to communicate seamlessly 21:03:37.144 --> 21:03:39.182 align:start position:0% allows users to communicate seamlessly even<21:03:37.504> if<21:03:37.680> they're<21:03:37.800> in<21:03:37.976> different<21:03:38.216> locations 21:03:39.182 --> 21:03:39.192 align:start position:0% even if they're in different locations 21:03:39.192 --> 21:03:42.350 align:start position:0% even if they're in different locations you<21:03:40.192> can<21:03:40.320> look<21:03:40.440> at<21:03:40.616> a<21:03:40.800> person<21:03:40.976> by<21:03:41.464> accessing<21:03:42.176> an 21:03:42.350 --> 21:03:42.360 align:start position:0% you can look at a person by accessing an 21:03:42.360 --> 21:03:44.862 align:start position:0% you can look at a person by accessing an interactive<21:03:43.144> directory<21:03:43.856> and<21:03:44.464> engaging 21:03:44.862 --> 21:03:44.872 align:start position:0% interactive directory and engaging 21:03:44.872 --> 21:03:47.502 align:start position:0% interactive directory and engaging communication<21:03:45.536> through<21:03:45.960> text<21:03:46.320> voice<21:03:47.160> or 21:03:47.502 --> 21:03:47.512 align:start position:0% communication through text voice or 21:03:47.512 --> 21:03:48.886 align:start position:0% communication through text voice or video 21:03:48.886 --> 21:03:48.896 align:start position:0% video 21:03:48.896 --> 21:03:50.454 align:start position:0% video so<21:03:49.376> that's<21:03:49.552> the<21:03:49.744> summary<21:03:49.976> of<21:03:50.104> what<21:03:50.216> we've 21:03:50.454 --> 21:03:50.464 align:start position:0% so that's the summary of what we've 21:03:50.464 --> 21:03:52.430 align:start position:0% so that's the summary of what we've covered<21:03:50.760> just<21:03:51.056> wanted<21:03:51.240> to<21:03:51.480> go<21:03:51.720> and<21:03:51.960> show<21:03:52.256> you 21:03:52.430 --> 21:03:52.440 align:start position:0% covered just wanted to go and show you 21:03:52.440 --> 21:03:53.886 align:start position:0% covered just wanted to go and show you just<21:03:52.800> for<21:03:52.976> more 21:03:53.886 --> 21:03:53.896 align:start position:0% just for more 21:03:53.896 --> 21:03:56.750 align:start position:0% just for more context<21:03:54.896> really<21:03:55.160> Cisco's<21:03:56.160> unified 21:03:56.750 --> 21:03:56.760 align:start position:0% context really Cisco's unified 21:03:56.760 --> 21:03:58.542 align:start position:0% context really Cisco's unified Communications 21:03:58.542 --> 21:03:58.552 align:start position:0% Communications 21:03:58.552 --> 21:04:00.646 align:start position:0% Communications I'm<21:03:59.280> just<21:03:59.512> going<21:03:59.640> to<21:03:59.696> play<21:03:59.872> a<21:04:00.000> video<21:04:00.176> this 21:04:00.646 --> 21:04:00.656 align:start position:0% I'm just going to play a video this 21:04:00.656 --> 21:04:02.814 align:start position:0% I'm just going to play a video this video<21:04:00.832> is<21:04:01.080> copyright<21:04:01.552> Cisco<21:04:02.104> system<21:04:02.336> so<21:04:02.696> if 21:04:02.814 --> 21:04:02.824 align:start position:0% video is copyright Cisco system so if 21:04:02.824 --> 21:04:04.910 align:start position:0% video is copyright Cisco system so if you<21:04:02.936> want<21:04:03.056> to<21:04:03.176> learn<21:04:03.296> more 21:04:04.910 --> 21:04:04.920 align:start position:0% you want to learn more 21:04:04.920 --> 21:04:07.134 align:start position:0% you want to learn more um<21:04:04.976> all<21:04:05.160> you<21:04:05.336> do<21:04:05.512> is<21:04:05.640> go<21:04:05.824> to<21:04:05.936> Cisco<21:04:06.360> or<21:04:06.720> in<21:04:07.016> fact 21:04:07.134 --> 21:04:07.144 align:start position:0% um all you do is go to Cisco or in fact 21:04:07.144 --> 21:04:10.966 align:start position:0% um all you do is go to Cisco or in fact type<21:04:07.376> Cisco<21:04:07.856> unified<21:04:08.216> Communications 21:04:10.966 --> 21:04:10.976 align:start position:0% type Cisco unified Communications 21:04:10.976 --> 21:04:14.206 align:start position:0% type Cisco unified Communications I'll<21:04:11.464> just<21:04:11.696> put<21:04:11.824> a<21:04:12.000> video<21:04:12.240> on<21:04:12.536> now 21:04:14.206 --> 21:04:14.216 align:start position:0% I'll just put a video on now 21:04:14.216 --> 21:06:28.850 align:start position:0% I'll just put a video on now foreign 21:06:28.850 --> 21:06:28.860 align:start position:0% 21:06:28.860 --> 21:06:37.566 align:start position:0% [Music] 21:06:37.566 --> 21:06:37.576 align:start position:0% [Music] 21:06:37.576 --> 21:06:44.566 align:start position:0% [Music] thank<21:06:38.576> you 21:06:44.566 --> 21:06:44.576 align:start position:0% 21:06:44.576 --> 21:06:47.030 align:start position:0% welcome<21:06:45.360> to<21:06:45.536> module<21:06:45.960> 17<21:06:46.144> lesson<21:06:46.856> one 21:06:47.030 --> 21:06:47.040 align:start position:0% welcome to module 17 lesson one 21:06:47.040 --> 21:06:49.734 align:start position:0% welcome to module 17 lesson one introduction<21:06:47.760> to<21:06:48.000> virtualization<21:06:48.720> this<21:06:49.680> is 21:06:49.734 --> 21:06:49.744 align:start position:0% introduction to virtualization this is 21:06:49.744 --> 21:06:52.670 align:start position:0% introduction to virtualization this is one<21:06:50.040> of<21:06:50.160> the<21:06:50.336> few<21:06:50.600> new<21:06:51.600> topics<21:06:52.192> that<21:06:52.440> have<21:06:52.552> been 21:06:52.670 --> 21:06:52.680 align:start position:0% one of the few new topics that have been 21:06:52.680 --> 21:06:54.414 align:start position:0% one of the few new topics that have been added<21:06:52.976> to<21:06:53.104> the<21:06:53.280> syllabus 21:06:54.414 --> 21:06:54.424 align:start position:0% added to the syllabus 21:06:54.424 --> 21:06:57.110 align:start position:0% added to the syllabus surrounding<21:06:55.192> virtualization<21:06:56.104> and<21:06:56.760> cloud 21:06:57.110 --> 21:06:57.120 align:start position:0% surrounding virtualization and cloud 21:06:57.120 --> 21:06:59.350 align:start position:0% surrounding virtualization and cloud computing 21:06:59.350 --> 21:06:59.360 align:start position:0% computing 21:06:59.360 --> 21:07:01.846 align:start position:0% computing and<21:07:00.360> come<21:07:00.600> to<21:07:00.720> your<21:07:00.896> offer<21:07:01.192> a<21:07:01.320> cloud 21:07:01.846 --> 21:07:01.856 align:start position:0% and come to your offer a cloud 21:07:01.856 --> 21:07:04.310 align:start position:0% and come to your offer a cloud certification<21:07:02.696> actually<21:07:03.120> there's<21:07:04.016> a<21:07:04.192> cloud 21:07:04.310 --> 21:07:04.320 align:start position:0% certification actually there's a cloud 21:07:04.320 --> 21:07:06.110 align:start position:0% certification actually there's a cloud Essentials<21:07:05.040> and<21:07:05.216> I<21:07:05.400> think<21:07:05.512> there<21:07:05.696> might<21:07:05.872> be<21:07:05.936> a 21:07:06.110 --> 21:07:06.120 align:start position:0% Essentials and I think there might be a 21:07:06.120 --> 21:07:07.670 align:start position:0% Essentials and I think there might be a cloud<21:07:06.296> Plus 21:07:07.670 --> 21:07:07.680 align:start position:0% cloud Plus 21:07:07.680 --> 21:07:09.710 align:start position:0% cloud Plus definitely<21:07:08.216> a<21:07:08.400> cloud<21:07:08.512> Essentials<21:07:09.240> because<21:07:09.424> we 21:07:09.710 --> 21:07:09.720 align:start position:0% definitely a cloud Essentials because we 21:07:09.720 --> 21:07:12.414 align:start position:0% definitely a cloud Essentials because we host<21:07:09.960> uh<21:07:10.496> host<21:07:10.856> that<21:07:11.040> course 21:07:12.414 --> 21:07:12.424 align:start position:0% host uh host that course 21:07:12.424 --> 21:07:14.094 align:start position:0% host uh host that course all<21:07:12.656> right<21:07:12.784> module<21:07:13.192> objective<21:07:13.680> is<21:07:13.856> the 21:07:14.094 --> 21:07:14.104 align:start position:0% all right module objective is the 21:07:14.104 --> 21:07:16.182 align:start position:0% all right module objective is the definition<21:07:14.216> of<21:07:14.576> virtualization<21:07:15.424> what<21:07:15.896> is<21:07:16.080> a 21:07:16.182 --> 21:07:16.192 align:start position:0% definition of virtualization what is a 21:07:16.192 --> 21:07:19.134 align:start position:0% definition of virtualization what is a virtual<21:07:16.552> machine<21:07:16.800> and<21:07:17.160> the<21:07:17.336> software 21:07:19.134 --> 21:07:19.144 align:start position:0% virtual machine and the software 21:07:19.144 --> 21:07:20.390 align:start position:0% virtual machine and the software I'm<21:07:19.440> sure<21:07:19.552> you've<21:07:19.744> heard<21:07:19.920> of<21:07:20.040> it<21:07:20.216> actually 21:07:20.390 --> 21:07:20.400 align:start position:0% I'm sure you've heard of it actually 21:07:20.400 --> 21:07:22.606 align:start position:0% I'm sure you've heard of it actually it's<21:07:20.760> the<21:07:21.056> new<21:07:21.240> or<21:07:21.536> one<21:07:21.832> of<21:07:21.960> the<21:07:22.080> very<21:07:22.256> new<21:07:22.440> and 21:07:22.606 --> 21:07:22.616 align:start position:0% it's the new or one of the very new and 21:07:22.616 --> 21:07:26.094 align:start position:0% it's the new or one of the very new and exciting<21:07:23.296> emerging<21:07:24.296> Technologies<21:07:25.104> that's 21:07:26.094 --> 21:07:26.104 align:start position:0% exciting emerging Technologies that's 21:07:26.104 --> 21:07:27.710 align:start position:0% exciting emerging Technologies that's made<21:07:26.336> alive<21:07:26.576> a<21:07:26.936> lot<21:07:27.000> easier<21:07:27.296> for<21:07:27.480> Network 21:07:27.710 --> 21:07:27.720 align:start position:0% made alive a lot easier for Network 21:07:27.720 --> 21:07:30.286 align:start position:0% made alive a lot easier for Network engineers 21:07:30.286 --> 21:07:30.296 align:start position:0% engineers 21:07:30.296 --> 21:07:33.110 align:start position:0% engineers um<21:07:30.440> companies<21:07:31.440> from<21:07:32.104> a<21:07:32.336> financial<21:07:32.640> and 21:07:33.110 --> 21:07:33.120 align:start position:0% um companies from a financial and 21:07:33.120 --> 21:07:35.862 align:start position:0% um companies from a financial and operations<21:07:33.832> standpoint<21:07:34.496> and<21:07:35.336> also<21:07:35.640> home 21:07:35.862 --> 21:07:35.872 align:start position:0% operations standpoint and also home 21:07:35.872 --> 21:07:37.846 align:start position:0% operations standpoint and also home users<21:07:36.296> who<21:07:36.480> can<21:07:36.600> do<21:07:36.784> a<21:07:36.896> lot<21:07:37.016> more<21:07:37.144> interesting 21:07:37.846 --> 21:07:37.856 align:start position:0% users who can do a lot more interesting 21:07:37.856 --> 21:07:39.710 align:start position:0% users who can do a lot more interesting things<21:07:38.160> on<21:07:38.872> their 21:07:39.710 --> 21:07:39.720 align:start position:0% things on their 21:07:39.720 --> 21:07:41.926 align:start position:0% things on their um systems<21:07:40.192> at<21:07:40.376> home 21:07:41.926 --> 21:07:41.936 align:start position:0% um systems at home 21:07:41.936 --> 21:07:43.966 align:start position:0% um systems at home so<21:07:42.424> it<21:07:42.536> refers<21:07:42.896> to<21:07:43.080> the<21:07:43.320> technologies<21:07:43.744> that 21:07:43.966 --> 21:07:43.976 align:start position:0% so it refers to the technologies that 21:07:43.976 --> 21:07:46.486 align:start position:0% so it refers to the technologies that allow<21:07:44.216> a<21:07:44.336> single<21:07:44.640> physical<21:07:44.824> computer<21:07:45.536> or<21:07:46.496> or 21:07:46.486 --> 21:07:46.496 align:start position:0% allow a single physical computer or or 21:07:46.496 --> 21:07:49.246 align:start position:0% allow a single physical computer or or server<21:07:47.104> obviously<21:07:47.784> environment<21:07:48.784> to<21:07:48.960> operate 21:07:49.246 --> 21:07:49.256 align:start position:0% server obviously environment to operate 21:07:49.256 --> 21:07:50.750 align:start position:0% server obviously environment to operate as<21:07:49.440> multiple<21:07:49.976> virtual<21:07:50.400> machines 21:07:50.750 --> 21:07:50.760 align:start position:0% as multiple virtual machines 21:07:50.760 --> 21:07:53.454 align:start position:0% as multiple virtual machines simultaneously<21:07:52.104> transforms<21:07:53.104> the<21:07:53.280> physical 21:07:53.454 --> 21:07:53.464 align:start position:0% simultaneously transforms the physical 21:07:53.464 --> 21:07:55.966 align:start position:0% simultaneously transforms the physical Hardware<21:07:53.824> resources<21:07:54.536> into<21:07:55.016> virtual<21:07:55.616> Hardware 21:07:55.966 --> 21:07:55.976 align:start position:0% Hardware resources into virtual Hardware 21:07:55.976 --> 21:07:57.526 align:start position:0% Hardware resources into virtual Hardware resources 21:07:57.526 --> 21:07:57.536 align:start position:0% resources 21:07:57.536 --> 21:07:59.814 align:start position:0% resources so<21:07:58.080> what<21:07:58.320> you<21:07:58.440> normally<21:07:58.744> have<21:07:58.976> one<21:07:59.576> device 21:07:59.814 --> 21:07:59.824 align:start position:0% so what you normally have one device 21:07:59.824 --> 21:08:02.150 align:start position:0% so what you normally have one device running<21:08:00.296> one<21:08:00.656> operating<21:08:01.080> system<21:08:01.504> you<21:08:02.040> can 21:08:02.150 --> 21:08:02.160 align:start position:0% running one operating system you can 21:08:02.160 --> 21:08:04.134 align:start position:0% running one operating system you can have<21:08:02.336> depending<21:08:03.056> on<21:08:03.176> how<21:08:03.480> much<21:08:03.536> Hardware<21:08:03.784> you 21:08:04.134 --> 21:08:04.144 align:start position:0% have depending on how much Hardware you 21:08:04.144 --> 21:08:07.310 align:start position:0% have depending on how much Hardware you have<21:08:04.256> and<21:08:04.440> how<21:08:04.680> you<21:08:04.856> apportion<21:08:05.464> it<21:08:05.784> and<21:08:06.784> two<21:08:07.144> or 21:08:07.310 --> 21:08:07.320 align:start position:0% have and how you apportion it and two or 21:08:07.320 --> 21:08:10.366 align:start position:0% have and how you apportion it and two or more<21:08:07.616> virtual<21:08:08.512> machines 21:08:10.366 --> 21:08:10.376 align:start position:0% more virtual machines 21:08:10.376 --> 21:08:12.350 align:start position:0% more virtual machines a<21:08:10.856> virtual<21:08:11.216> machine<21:08:11.400> is<21:08:11.824> an<21:08:12.000> isolated 21:08:12.350 --> 21:08:12.360 align:start position:0% a virtual machine is an isolated 21:08:12.360 --> 21:08:13.910 align:start position:0% a virtual machine is an isolated software<21:08:12.896> replica<21:08:13.320> of<21:08:13.616> the<21:08:13.800> original 21:08:13.910 --> 21:08:13.920 align:start position:0% software replica of the original 21:08:13.920 --> 21:08:16.670 align:start position:0% software replica of the original computer<21:08:14.464> so<21:08:15.296> for<21:08:15.536> all<21:08:15.720> intents<21:08:16.144> and<21:08:16.192> purposes 21:08:16.670 --> 21:08:16.680 align:start position:0% computer so for all intents and purposes 21:08:16.680 --> 21:08:20.150 align:start position:0% computer so for all intents and purposes it<21:08:17.216> appears<21:08:17.640> as<21:08:18.120> a<21:08:18.960> machine<21:08:19.256> in<21:08:19.552> its<21:08:19.856> own<21:08:19.920> right 21:08:20.150 --> 21:08:20.160 align:start position:0% it appears as a machine in its own right 21:08:20.160 --> 21:08:22.734 align:start position:0% it appears as a machine in its own right with<21:08:20.576> all<21:08:20.760> processor<21:08:21.240> instructions<21:08:21.896> and 21:08:22.734 --> 21:08:22.744 align:start position:0% with all processor instructions and 21:08:22.744 --> 21:08:24.590 align:start position:0% with all processor instructions and system<21:08:22.920> resources 21:08:24.590 --> 21:08:24.600 align:start position:0% system resources 21:08:24.600 --> 21:08:27.230 align:start position:0% system resources so<21:08:25.016> you'll<21:08:25.144> often<21:08:25.504> see<21:08:25.680> an<21:08:26.576> image<21:08:26.760> like<21:08:27.056> this 21:08:27.230 --> 21:08:27.240 align:start position:0% so you'll often see an image like this 21:08:27.240 --> 21:08:28.910 align:start position:0% so you'll often see an image like this where<21:08:27.424> you<21:08:27.600> have<21:08:27.720> a<21:08:27.896> physical<21:08:28.080> computer<21:08:28.552> or 21:08:28.910 --> 21:08:28.920 align:start position:0% where you have a physical computer or 21:08:28.920 --> 21:08:32.270 align:start position:0% where you have a physical computer or server<21:08:29.400> and<21:08:30.240> inside<21:08:30.720> and<21:08:31.440> it<21:08:31.744> will<21:08:31.856> represent 21:08:32.270 --> 21:08:32.280 align:start position:0% server and inside and it will represent 21:08:32.280 --> 21:08:35.686 align:start position:0% server and inside and it will represent a<21:08:32.512> number<21:08:32.640> of<21:08:32.760> virtual<21:08:33.176> machines 21:08:35.686 --> 21:08:35.696 align:start position:0% 21:08:35.696 --> 21:08:37.966 align:start position:0% much<21:08:36.176> in<21:08:36.360> the<21:08:36.480> same<21:08:36.600> way<21:08:36.784> as<21:08:37.080> their<21:08:37.256> vlans<21:08:37.800> they 21:08:37.966 --> 21:08:37.976 align:start position:0% much in the same way as their vlans they 21:08:37.976 --> 21:08:40.542 align:start position:0% much in the same way as their vlans they operate<21:08:38.400> in<21:08:38.696> their<21:08:38.872> own<21:08:39.056> right 21:08:40.542 --> 21:08:40.552 align:start position:0% operate in their own right 21:08:40.552 --> 21:08:43.966 align:start position:0% operate in their own right as<21:08:41.104> if<21:08:41.400> they're<21:08:41.696> an<21:08:42.536> actual<21:08:42.832> machine 21:08:43.966 --> 21:08:43.976 align:start position:0% as if they're an actual machine 21:08:43.976 --> 21:08:45.526 align:start position:0% as if they're an actual machine a<21:08:44.400> virtual<21:08:44.760> machines<21:08:45.056> are<21:08:45.296> completely 21:08:45.526 --> 21:08:45.536 align:start position:0% a virtual machines are completely 21:08:45.536 --> 21:08:49.006 align:start position:0% a virtual machines are completely separate<21:08:45.960> and<21:08:46.144> independent 21:08:49.006 --> 21:08:49.016 align:start position:0% 21:08:49.016 --> 21:08:50.926 align:start position:0% by<21:08:49.440> running<21:08:49.616> good<21:08:49.976> operating<21:08:50.216> system<21:08:50.512> in<21:08:50.760> each 21:08:50.926 --> 21:08:50.936 align:start position:0% by running good operating system in each 21:08:50.936 --> 21:08:52.790 align:start position:0% by running good operating system in each one<21:08:51.120> it<21:08:51.296> becomes<21:08:51.600> possible<21:08:51.960> to<21:08:52.192> run<21:08:52.376> several 21:08:52.790 --> 21:08:52.800 align:start position:0% one it becomes possible to run several 21:08:52.800 --> 21:08:54.646 align:start position:0% one it becomes possible to run several guest<21:08:53.040> operating<21:08:53.464> systems<21:08:53.872> at<21:08:54.120> the<21:08:54.240> same<21:08:54.360> time 21:08:54.646 --> 21:08:54.656 align:start position:0% guest operating systems at the same time 21:08:54.656 --> 21:08:56.862 align:start position:0% guest operating systems at the same time so<21:08:55.504> you<21:08:55.680> could<21:08:55.800> have 21:08:56.862 --> 21:08:56.872 align:start position:0% so you could have 21:08:56.872 --> 21:09:01.006 align:start position:0% so you could have um<21:08:56.936> a<21:08:57.360> Microsoft<21:08:58.280> Linux<21:08:59.280> and<21:09:00.000> other<21:09:00.600> operating 21:09:01.006 --> 21:09:01.016 align:start position:0% um a Microsoft Linux and other operating 21:09:01.016 --> 21:09:03.046 align:start position:0% um a Microsoft Linux and other operating systems<21:09:01.552> running<21:09:01.856> on<21:09:02.576> the<21:09:02.696> same<21:09:02.824> physical 21:09:03.046 --> 21:09:03.056 align:start position:0% systems running on the same physical 21:09:03.056 --> 21:09:07.310 align:start position:0% systems running on the same physical device<21:09:03.536> but<21:09:04.320> different<21:09:04.552> virtual<21:09:05.040> devices 21:09:07.310 --> 21:09:07.320 align:start position:0% device but different virtual devices 21:09:07.320 --> 21:09:09.590 align:start position:0% device but different virtual devices a<21:09:07.800> whole<21:09:07.976> bunch<21:09:08.280> of<21:09:08.400> virtualization<21:09:09.056> software 21:09:09.590 --> 21:09:09.600 align:start position:0% a whole bunch of virtualization software 21:09:09.600 --> 21:09:12.710 align:start position:0% a whole bunch of virtualization software around<21:09:10.144> some<21:09:10.616> free<21:09:10.920> some<21:09:11.824> um<21:09:11.824> you<21:09:12.296> have<21:09:12.424> to<21:09:12.536> pay 21:09:12.710 --> 21:09:12.720 align:start position:0% around some free some um you have to pay 21:09:12.720 --> 21:09:15.166 align:start position:0% around some free some um you have to pay for<21:09:12.896> and<21:09:13.080> you<21:09:13.192> get<21:09:13.320> different<21:09:13.504> levels<21:09:13.920> of 21:09:15.166 --> 21:09:15.176 align:start position:0% for and you get different levels of 21:09:15.176 --> 21:09:15.774 align:start position:0% for and you get different levels of um 21:09:15.774 --> 21:09:15.784 align:start position:0% um 21:09:15.784 --> 21:09:18.230 align:start position:0% um software<21:09:16.496> up<21:09:16.680> to<21:09:16.856> Enterprise<21:09:17.104> and<21:09:17.872> obviously 21:09:18.230 --> 21:09:18.240 align:start position:0% software up to Enterprise and obviously 21:09:18.240 --> 21:09:19.846 align:start position:0% software up to Enterprise and obviously support<21:09:18.480> contracts 21:09:19.846 --> 21:09:19.856 align:start position:0% support contracts 21:09:19.856 --> 21:09:22.134 align:start position:0% support contracts the<21:09:20.336> software<21:09:20.640> transforms<21:09:21.176> the<21:09:21.296> hardware<21:09:21.536> of 21:09:22.134 --> 21:09:22.144 align:start position:0% the software transforms the hardware of 21:09:22.144 --> 21:09:23.862 align:start position:0% the software transforms the hardware of the<21:09:22.256> computer<21:09:22.376> including<21:09:22.976> the<21:09:23.104> CPU<21:09:23.512> memory 21:09:23.862 --> 21:09:23.872 align:start position:0% the computer including the CPU memory 21:09:23.872 --> 21:09:26.686 align:start position:0% the computer including the CPU memory Network<21:09:24.120> adapting<21:09:24.656> to<21:09:24.960> Virtual<21:09:25.320> resources 21:09:26.686 --> 21:09:26.696 align:start position:0% Network adapting to Virtual resources 21:09:26.696 --> 21:09:28.670 align:start position:0% Network adapting to Virtual resources these<21:09:27.120> are<21:09:27.296> shared<21:09:27.536> amongst<21:09:28.192> virtual 21:09:28.670 --> 21:09:28.680 align:start position:0% these are shared amongst virtual 21:09:28.680 --> 21:09:31.006 align:start position:0% these are shared amongst virtual machines 21:09:31.006 --> 21:09:31.016 align:start position:0% machines 21:09:31.016 --> 21:09:33.590 align:start position:0% machines it<21:09:31.376> basically<21:09:31.744> provides<21:09:32.104> a<21:09:32.280> layer<21:09:32.576> of<21:09:32.640> layer 21:09:33.590 --> 21:09:33.600 align:start position:0% it basically provides a layer of layer 21:09:33.600 --> 21:09:35.926 align:start position:0% it basically provides a layer of layer of<21:09:33.720> abstraction<21:09:34.552> so<21:09:35.040> for<21:09:35.280> all<21:09:35.464> intents<21:09:35.872> and 21:09:35.926 --> 21:09:35.936 align:start position:0% of abstraction so for all intents and 21:09:35.936 --> 21:09:38.270 align:start position:0% of abstraction so for all intents and purposes<21:09:36.360> there's<21:09:36.896> a<21:09:37.144> divide<21:09:37.552> a<21:09:37.920> virtual 21:09:38.270 --> 21:09:38.280 align:start position:0% purposes there's a divide a virtual 21:09:38.280 --> 21:09:39.774 align:start position:0% purposes there's a divide a virtual divide<21:09:38.696> between<21:09:38.872> all<21:09:39.240> of<21:09:39.360> these<21:09:39.536> different 21:09:39.774 --> 21:09:39.784 align:start position:0% divide between all of these different 21:09:39.784 --> 21:09:42.822 align:start position:0% divide between all of these different machines 21:09:42.822 --> 21:09:42.832 align:start position:0% 21:09:42.832 --> 21:09:44.862 align:start position:0% the<21:09:43.256> labor<21:09:43.552> of<21:09:43.680> abstraction<21:09:44.104> is<21:09:44.512> basically 21:09:44.862 --> 21:09:44.872 align:start position:0% the labor of abstraction is basically 21:09:44.872 --> 21:09:46.430 align:start position:0% the labor of abstraction is basically there<21:09:45.176> to<21:09:45.424> hide<21:09:45.656> what's<21:09:46.016> happening 21:09:46.430 --> 21:09:46.440 align:start position:0% there to hide what's happening 21:09:46.440 --> 21:09:49.246 align:start position:0% there to hide what's happening underneath<21:09:47.336> what<21:09:47.640> you<21:09:47.824> can<21:09:48.000> see 21:09:49.246 --> 21:09:49.256 align:start position:0% underneath what you can see 21:09:49.256 --> 21:09:51.046 align:start position:0% underneath what you can see foreign 21:09:51.046 --> 21:09:51.056 align:start position:0% foreign 21:09:51.056 --> 21:09:53.390 align:start position:0% foreign as<21:09:51.600> a<21:09:51.720> result<21:09:51.832> the<21:09:52.256> abstraction<21:09:52.616> provided<21:09:53.160> by 21:09:53.390 --> 21:09:53.400 align:start position:0% as a result the abstraction provided by 21:09:53.400 --> 21:09:55.790 align:start position:0% as a result the abstraction provided by the<21:09:53.696> software<21:09:54.240> the<21:09:54.656> guest<21:09:54.832> operating<21:09:55.192> systems 21:09:55.790 --> 21:09:55.800 align:start position:0% the software the guest operating systems 21:09:55.800 --> 21:09:57.646 align:start position:0% the software the guest operating systems are<21:09:55.976> not<21:09:56.160> tied<21:09:56.464> to<21:09:56.640> the<21:09:56.872> underlying<21:09:57.480> physical 21:09:57.646 --> 21:09:57.656 align:start position:0% are not tied to the underlying physical 21:09:57.656 --> 21:09:59.390 align:start position:0% are not tied to the underlying physical Hardware<21:09:58.080> so<21:09:58.496> this<21:09:58.680> is<21:09:58.744> how<21:09:58.976> we<21:09:59.160> can<21:09:59.216> actually 21:09:59.390 --> 21:09:59.400 align:start position:0% Hardware so this is how we can actually 21:09:59.400 --> 21:10:03.886 align:start position:0% Hardware so this is how we can actually get<21:09:59.696> it<21:09:59.824> all<21:10:00.000> to<21:10:00.176> run 21:10:03.886 --> 21:10:03.896 align:start position:0% 21:10:03.896 --> 21:10:05.686 align:start position:0% so<21:10:04.320> you<21:10:04.496> have<21:10:04.616> a<21:10:04.744> portability<21:10:05.104> of<21:10:05.336> moving 21:10:05.686 --> 21:10:05.696 align:start position:0% so you have a portability of moving 21:10:05.696 --> 21:10:07.070 align:start position:0% so you have a portability of moving virtual<21:10:06.056> machines<21:10:06.424> from<21:10:06.656> one<21:10:06.896> physical 21:10:07.070 --> 21:10:07.080 align:start position:0% virtual machines from one physical 21:10:07.080 --> 21:10:09.710 align:start position:0% virtual machines from one physical computer<21:10:07.552> to<21:10:08.040> another<21:10:08.216> physical<21:10:08.576> computer<21:10:09.176> if 21:10:09.710 --> 21:10:09.720 align:start position:0% computer to another physical computer if 21:10:09.720 --> 21:10:12.110 align:start position:0% computer to another physical computer if you<21:10:09.784> so<21:10:09.960> wish<21:10:10.256> great<21:10:11.216> if<21:10:11.512> you<21:10:11.640> want<21:10:11.760> to<21:10:12.000> do 21:10:12.110 --> 21:10:12.120 align:start position:0% you so wish great if you want to do 21:10:12.120 --> 21:10:15.230 align:start position:0% you so wish great if you want to do testing<21:10:12.832> interoperability<21:10:13.744> stress<21:10:14.696> testing 21:10:15.230 --> 21:10:15.240 align:start position:0% testing interoperability stress testing 21:10:15.240 --> 21:10:18.046 align:start position:0% testing interoperability stress testing or<21:10:16.192> just<21:10:16.440> practicing<21:10:16.976> even<21:10:17.216> if<21:10:17.640> you<21:10:17.760> want<21:10:17.872> to 21:10:18.046 --> 21:10:18.056 align:start position:0% or just practicing even if you want to 21:10:18.056 --> 21:10:20.502 align:start position:0% or just practicing even if you want to do<21:10:18.176> some<21:10:18.480> install<21:10:19.256> various<21:10:19.976> operating 21:10:20.502 --> 21:10:20.512 align:start position:0% do some install various operating 21:10:20.512 --> 21:10:23.270 align:start position:0% do some install various operating systems<21:10:21.000> onto<21:10:21.360> one<21:10:21.656> device<21:10:21.920> in<21:10:22.920> order<21:10:23.040> to 21:10:23.270 --> 21:10:23.280 align:start position:0% systems onto one device in order to 21:10:23.280 --> 21:10:26.390 align:start position:0% systems onto one device in order to practice<21:10:23.464> free<21:10:23.824> exams<21:10:24.296> or<21:10:24.480> job<21:10:24.656> interviews 21:10:26.390 --> 21:10:26.400 align:start position:0% practice free exams or job interviews 21:10:26.400 --> 21:10:28.366 align:start position:0% practice free exams or job interviews so<21:10:26.936> this<21:10:27.176> is<21:10:27.296> just<21:10:27.480> an<21:10:27.600> overview<21:10:27.896> we've<21:10:28.192> got 21:10:28.366 --> 21:10:28.376 align:start position:0% so this is just an overview we've got 21:10:28.376 --> 21:10:29.926 align:start position:0% so this is just an overview we've got more<21:10:28.552> to<21:10:28.800> cover<21:10:28.976> in<21:10:29.400> the<21:10:29.576> following 21:10:29.926 --> 21:10:29.936 align:start position:0% more to cover in the following 21:10:29.936 --> 21:10:33.166 align:start position:0% more to cover in the following presentations<21:10:30.480> what<21:10:31.144> is<21:10:31.320> virtualization<21:10:32.176> the 21:10:33.166 --> 21:10:33.176 align:start position:0% presentations what is virtualization the 21:10:33.176 --> 21:10:35.630 align:start position:0% presentations what is virtualization the virtual<21:10:33.536> machine<21:10:33.832> the<21:10:34.320> software<21:10:34.680> that's<21:10:35.400> all 21:10:35.630 --> 21:10:35.640 align:start position:0% virtual machine the software that's all 21:10:35.640 --> 21:10:41.990 align:start position:0% virtual machine the software that's all for<21:10:35.824> now<21:10:36.000> thanks<21:10:36.296> for<21:10:36.480> watching 21:10:41.990 --> 21:10:42.000 align:start position:0% 21:10:42.000 --> 21:10:57.886 align:start position:0% [Music] 21:10:57.886 --> 21:10:57.896 align:start position:0% 21:10:57.896 --> 21:11:00.494 align:start position:0% welcome<21:10:58.320> to<21:10:58.552> module<21:10:58.920> 17<21:10:59.104> lesson<21:10:59.824> 2 21:11:00.494 --> 21:11:00.504 align:start position:0% welcome to module 17 lesson 2 21:11:00.504 --> 21:11:02.750 align:start position:0% welcome to module 17 lesson 2 virtualization<21:11:01.504> components<21:11:02.400> and 21:11:02.750 --> 21:11:02.760 align:start position:0% virtualization components and 21:11:02.760 --> 21:11:06.166 align:start position:0% virtualization components and software-defined<21:11:03.600> networking<21:11:04.144> or<21:11:04.496> sdn 21:11:06.166 --> 21:11:06.176 align:start position:0% software-defined networking or sdn 21:11:06.176 --> 21:11:08.206 align:start position:0% software-defined networking or sdn for<21:11:06.832> short 21:11:08.206 --> 21:11:08.216 align:start position:0% for short 21:11:08.216 --> 21:11:10.542 align:start position:0% for short looking<21:11:08.760> at<21:11:09.000> virtual<21:11:09.296> networking<21:11:09.960> virtual 21:11:10.542 --> 21:11:10.552 align:start position:0% looking at virtual networking virtual 21:11:10.552 --> 21:11:13.670 align:start position:0% looking at virtual networking virtual network<21:11:11.240> adapters<21:11:12.240> a<21:11:12.960> virtual<21:11:13.376> switch 21:11:13.670 --> 21:11:13.680 align:start position:0% network adapters a virtual switch 21:11:13.680 --> 21:11:16.542 align:start position:0% network adapters a virtual switch Virtual<21:11:14.400> Router 21:11:16.542 --> 21:11:16.552 align:start position:0% Virtual Router 21:11:16.552 --> 21:11:20.326 align:start position:0% Virtual Router Virtual<21:11:17.160> Router<21:11:17.576> via<21:11:18.296> vrrp 21:11:20.326 --> 21:11:20.336 align:start position:0% Virtual Router via vrrp 21:11:20.336 --> 21:11:24.286 align:start position:0% Virtual Router via vrrp the<21:11:20.824> virtual<21:11:21.120> firewall<21:11:21.656> and<21:11:22.552> sdn 21:11:24.286 --> 21:11:24.296 align:start position:0% the virtual firewall and sdn 21:11:24.296 --> 21:11:29.326 align:start position:0% the virtual firewall and sdn and<21:11:24.720> while<21:11:25.016> we<21:11:25.256> why<21:11:25.744> would<21:11:25.920> want<21:11:26.160> to<21:11:26.280> use<21:11:26.400> sdn 21:11:29.326 --> 21:11:29.336 align:start position:0% 21:11:29.336 --> 21:11:31.430 align:start position:0% so<21:11:29.824> a<21:11:29.936> virtual<21:11:30.240> network<21:11:30.480> is<21:11:30.784> a<21:11:30.960> system<21:11:31.144> in 21:11:31.430 --> 21:11:31.440 align:start position:0% so a virtual network is a system in 21:11:31.440 --> 21:11:33.286 align:start position:0% so a virtual network is a system in which<21:11:31.680> the<21:11:32.104> following<21:11:32.400> is<21:11:32.576> true<21:11:32.824> you've<21:11:33.240> got 21:11:33.286 --> 21:11:33.296 align:start position:0% which the following is true you've got 21:11:33.296 --> 21:11:35.150 align:start position:0% which the following is true you've got two<21:11:33.536> or<21:11:33.656> more<21:11:33.784> virtual<21:11:34.144> machines<21:11:34.552> connected 21:11:35.150 --> 21:11:35.160 align:start position:0% two or more virtual machines connected 21:11:35.160 --> 21:11:37.790 align:start position:0% two or more virtual machines connected logically<21:11:35.760> to<21:11:36.296> one<21:11:36.480> another<21:11:36.656> they<21:11:37.504> could<21:11:37.680> each 21:11:37.790 --> 21:11:37.800 align:start position:0% logically to one another they could each 21:11:37.800 --> 21:11:40.606 align:start position:0% logically to one another they could each just<21:11:38.040> send<21:11:38.216> received<21:11:38.760> data<21:11:39.120> as<21:11:39.424> if<21:11:39.656> they<21:11:39.960> were 21:11:40.606 --> 21:11:40.616 align:start position:0% just send received data as if they were 21:11:40.616 --> 21:11:44.094 align:start position:0% just send received data as if they were operating<21:11:41.040> as<21:11:41.464> physical<21:11:42.000> devices 21:11:44.094 --> 21:11:44.104 align:start position:0% operating as physical devices 21:11:44.104 --> 21:11:47.030 align:start position:0% operating as physical devices I've<21:11:44.576> got<21:11:44.824> an<21:11:44.936> example<21:11:45.240> here<21:11:45.496> esxi<21:11:46.496> which<21:11:46.920> is 21:11:47.030 --> 21:11:47.040 align:start position:0% I've got an example here esxi which is 21:11:47.040 --> 21:11:50.454 align:start position:0% I've got an example here esxi which is software<21:11:47.512> available<21:11:47.936> from<21:11:48.784> VMware<21:11:49.616> I<21:11:50.336> think 21:11:50.454 --> 21:11:50.464 align:start position:0% software available from VMware I think 21:11:50.464 --> 21:11:52.310 align:start position:0% software available from VMware I think they<21:11:50.760> do<21:11:50.936> offer<21:11:51.176> some<21:11:51.360> free<21:11:51.600> software<21:11:52.080> I 21:11:52.310 --> 21:11:52.320 align:start position:0% they do offer some free software I 21:11:52.320 --> 21:11:54.774 align:start position:0% they do offer some free software I haven't<21:11:52.496> checked<21:11:52.744> as<21:11:53.104> to<21:11:53.280> which 21:11:54.774 --> 21:11:54.784 align:start position:0% haven't checked as to which 21:11:54.784 --> 21:11:57.646 align:start position:0% haven't checked as to which um is<21:11:55.376> free<21:11:55.680> for<21:11:56.336> home<21:11:56.760> use<21:11:57.000> or<21:11:57.424> commercial 21:11:57.646 --> 21:11:57.656 align:start position:0% um is free for home use or commercial 21:11:57.656 --> 21:12:01.366 align:start position:0% um is free for home use or commercial use<21:11:58.336> and<21:11:59.336> I<21:11:59.872> recommend<21:12:00.240> you<21:12:00.360> check<21:12:00.656> out<21:12:00.896> the 21:12:01.366 --> 21:12:01.376 align:start position:0% use and I recommend you check out the 21:12:01.376 --> 21:12:03.470 align:start position:0% use and I recommend you check out the VMware<21:12:01.856> certifications<21:12:02.824> on 21:12:03.470 --> 21:12:03.480 align:start position:0% VMware certifications on 21:12:03.480 --> 21:12:06.110 align:start position:0% VMware certifications on howturnetwork.com 21:12:06.110 --> 21:12:06.120 align:start position:0% howturnetwork.com 21:12:06.120 --> 21:12:08.454 align:start position:0% howturnetwork.com they're<21:12:06.720> very<21:12:07.192> relevant<21:12:07.552> for<21:12:07.856> modern<21:12:08.160> day 21:12:08.454 --> 21:12:08.464 align:start position:0% they're very relevant for modern day 21:12:08.464 --> 21:12:10.246 align:start position:0% they're very relevant for modern day networking 21:12:10.246 --> 21:12:10.256 align:start position:0% networking 21:12:10.256 --> 21:12:12.646 align:start position:0% networking so<21:12:10.920> they<21:12:11.104> can<21:12:11.280> send<21:12:11.464> to<21:12:11.640> receive<21:12:11.872> data<21:12:12.480> from 21:12:12.646 --> 21:12:12.656 align:start position:0% so they can send to receive data from 21:12:12.656 --> 21:12:14.990 align:start position:0% so they can send to receive data from each<21:12:12.832> other<21:12:13.440> the<21:12:13.920> virtual<21:12:14.216> network<21:12:14.464> adapter 21:12:14.990 --> 21:12:15.000 align:start position:0% each other the virtual network adapter 21:12:15.000 --> 21:12:16.910 align:start position:0% each other the virtual network adapter is<21:12:15.120> a<21:12:15.296> software<21:12:15.600> implementation<21:12:16.320> of<21:12:16.744> a 21:12:16.910 --> 21:12:16.920 align:start position:0% is a software implementation of a 21:12:16.920 --> 21:12:18.950 align:start position:0% is a software implementation of a physical<21:12:17.160> network<21:12:17.512> adapter<21:12:18.176> which<21:12:18.656> I'm<21:12:18.832> sure 21:12:18.950 --> 21:12:18.960 align:start position:0% physical network adapter which I'm sure 21:12:18.960 --> 21:12:20.630 align:start position:0% physical network adapter which I'm sure comes<21:12:19.320> as<21:12:19.440> no<21:12:19.616> surprise 21:12:20.630 --> 21:12:20.640 align:start position:0% comes as no surprise 21:12:20.640 --> 21:12:22.606 align:start position:0% comes as no surprise so<21:12:21.176> you<21:12:21.296> have<21:12:21.424> a<21:12:21.600> physical<21:12:21.720> adapter<21:12:22.256> but<21:12:22.496> the 21:12:22.606 --> 21:12:22.616 align:start position:0% so you have a physical adapter but the 21:12:22.616 --> 21:12:24.646 align:start position:0% so you have a physical adapter but the virtual<21:12:22.920> one<21:12:23.160> is<21:12:23.336> acting<21:12:23.696> in<21:12:23.872> exactly<21:12:24.480> the 21:12:24.646 --> 21:12:24.656 align:start position:0% virtual one is acting in exactly the 21:12:24.656 --> 21:12:27.710 align:start position:0% virtual one is acting in exactly the same<21:12:24.832> mother<21:12:25.080> and<21:12:25.616> same<21:12:26.040> manner<21:12:26.400> sorry 21:12:27.710 --> 21:12:27.720 align:start position:0% same mother and same manner sorry 21:12:27.720 --> 21:12:30.286 align:start position:0% same mother and same manner sorry and<21:12:28.376> you've<21:12:28.744> got<21:12:28.800> a<21:12:28.976> diagram<21:12:29.696> here<21:12:29.936> of<21:12:30.120> a 21:12:30.286 --> 21:12:30.296 align:start position:0% and you've got a diagram here of a 21:12:30.296 --> 21:12:32.814 align:start position:0% and you've got a diagram here of a physical<21:12:30.424> network<21:12:31.256> card 21:12:32.814 --> 21:12:32.824 align:start position:0% physical network card 21:12:32.824 --> 21:12:35.990 align:start position:0% physical network card um<21:12:32.936> and<21:12:33.240> then<21:12:33.360> you're<21:12:33.832> working<21:12:34.440> as<21:12:35.280> a<21:12:35.464> subset 21:12:35.990 --> 21:12:36.000 align:start position:0% um and then you're working as a subset 21:12:36.000 --> 21:12:38.150 align:start position:0% um and then you're working as a subset of<21:12:36.120> this<21:12:36.360> is<21:12:36.480> your<21:12:36.656> virtual<21:12:37.016> machine<21:12:37.320> they're 21:12:38.150 --> 21:12:38.160 align:start position:0% of this is your virtual machine they're 21:12:38.160 --> 21:12:40.734 align:start position:0% of this is your virtual machine they're running<21:12:38.400> virtual<21:12:38.872> network<21:12:39.056> cards<21:12:39.784> and 21:12:40.734 --> 21:12:40.744 align:start position:0% running virtual network cards and 21:12:40.744 --> 21:12:42.886 align:start position:0% running virtual network cards and virtual<21:12:41.160> machines<21:12:41.512> on<21:12:41.760> top<21:12:41.872> of<21:12:42.000> that 21:12:42.886 --> 21:12:42.896 align:start position:0% virtual machines on top of that 21:12:42.896 --> 21:12:45.230 align:start position:0% virtual machines on top of that the<21:12:43.376> virtual<21:12:43.744> network<21:12:44.040> card<21:12:44.336> interface<21:12:44.872> is<21:12:45.056> a 21:12:45.230 --> 21:12:45.240 align:start position:0% the virtual network card interface is a 21:12:45.240 --> 21:12:47.814 align:start position:0% the virtual network card interface is a virtual<21:12:45.536> machine<21:12:45.784> to<21:12:46.144> the<21:12:46.320> network<21:12:46.640> they<21:12:47.640> can 21:12:47.814 --> 21:12:47.824 align:start position:0% virtual machine to the network they can 21:12:47.824 --> 21:12:51.590 align:start position:0% virtual machine to the network they can have<21:12:48.000> one<21:12:48.832> or<21:12:48.960> more<21:12:49.144> virtual<21:12:49.696> Nic<21:12:50.696> next<21:12:51.240> or 21:12:51.590 --> 21:12:51.600 align:start position:0% have one or more virtual Nic next or 21:12:51.600 --> 21:12:53.150 align:start position:0% have one or more virtual Nic next or v-nix 21:12:53.150 --> 21:12:53.160 align:start position:0% v-nix 21:12:53.160 --> 21:12:55.310 align:start position:0% v-nix eat<21:12:53.760> such<21:12:54.000> Phoenix<21:12:54.240> has<21:12:54.600> its<21:12:54.832> own<21:12:54.896> Mac<21:12:55.080> address 21:12:55.310 --> 21:12:55.320 align:start position:0% eat such Phoenix has its own Mac address 21:12:55.320 --> 21:12:56.926 align:start position:0% eat such Phoenix has its own Mac address it<21:12:55.680> needs<21:12:55.856> to<21:12:55.976> follow<21:12:56.104> the<21:12:56.336> same<21:12:56.464> rules<21:12:56.824> as 21:12:56.926 --> 21:12:56.936 align:start position:0% it needs to follow the same rules as 21:12:56.936 --> 21:12:58.486 align:start position:0% it needs to follow the same rules as physical<21:12:57.176> networking<21:12:57.896> so<21:12:58.080> it'll<21:12:58.256> need<21:12:58.440> to 21:12:58.486 --> 21:12:58.496 align:start position:0% physical networking so it'll need to 21:12:58.496 --> 21:13:00.110 align:start position:0% physical networking so it'll need to have<21:12:58.616> a<21:12:58.744> unique<21:12:58.976> Mac 21:13:00.110 --> 21:13:00.120 align:start position:0% have a unique Mac 21:13:00.120 --> 21:13:04.070 align:start position:0% have a unique Mac a<21:13:00.536> virtual<21:13:01.080> network<21:13:01.552> card<21:13:02.040> in<21:13:02.760> a<21:13:03.424> um<21:13:03.536> virtual 21:13:04.070 --> 21:13:04.080 align:start position:0% a virtual network card in a um virtual 21:13:04.080 --> 21:13:06.110 align:start position:0% a virtual network card in a um virtual machine<21:13:04.256> you<21:13:05.104> still<21:13:05.216> have<21:13:05.400> to<21:13:05.512> configure<21:13:05.936> it 21:13:06.110 --> 21:13:06.120 align:start position:0% machine you still have to configure it 21:13:06.120 --> 21:13:08.390 align:start position:0% machine you still have to configure it all<21:13:06.424> the<21:13:06.600> same<21:13:06.784> rules<21:13:07.080> apply<21:13:07.504> it's<21:13:08.040> just<21:13:08.216> the 21:13:08.390 --> 21:13:08.400 align:start position:0% all the same rules apply it's just the 21:13:08.400 --> 21:13:10.366 align:start position:0% all the same rules apply it's just the fact<21:13:08.512> that<21:13:08.760> it<21:13:08.936> isn't<21:13:09.240> operating<21:13:09.720> uh 21:13:10.366 --> 21:13:10.376 align:start position:0% fact that it isn't operating uh 21:13:10.376 --> 21:13:11.566 align:start position:0% fact that it isn't operating uh physically 21:13:11.566 --> 21:13:11.576 align:start position:0% physically 21:13:11.576 --> 21:13:13.494 align:start position:0% physically so<21:13:11.824> you<21:13:11.936> can<21:13:12.120> go<21:13:12.360> and<21:13:12.536> see<21:13:12.832> and<21:13:13.144> physically 21:13:13.494 --> 21:13:13.504 align:start position:0% so you can go and see and physically 21:13:13.504 --> 21:13:15.774 align:start position:0% so you can go and see and physically plug<21:13:13.800> and<21:13:13.976> unplug<21:13:14.336> cables 21:13:15.774 --> 21:13:15.784 align:start position:0% plug and unplug cables 21:13:15.784 --> 21:13:18.350 align:start position:0% plug and unplug cables virtual<21:13:16.680> switch<21:13:16.856> or<21:13:17.104> v-switch<21:13:17.640> is<21:13:17.824> a<21:13:18.056> software 21:13:18.350 --> 21:13:18.360 align:start position:0% virtual switch or v-switch is a software 21:13:18.360 --> 21:13:21.110 align:start position:0% virtual switch or v-switch is a software version<21:13:18.784> of<21:13:19.192> a<21:13:19.440> physical<21:13:19.552> switch<21:13:19.976> it's<21:13:20.936> got 21:13:21.110 --> 21:13:21.120 align:start position:0% version of a physical switch it's got 21:13:21.120 --> 21:13:23.566 align:start position:0% version of a physical switch it's got Network<21:13:21.424> ports<21:13:22.016> similar<21:13:22.376> to<21:13:22.496> the<21:13:22.680> RJ45 21:13:23.566 --> 21:13:23.576 align:start position:0% Network ports similar to the RJ45 21:13:23.576 --> 21:13:27.006 align:start position:0% Network ports similar to the RJ45 connectors<21:13:24.120> you<21:13:24.360> have<21:13:24.616> and<21:13:25.616> one 21:13:27.006 --> 21:13:27.016 align:start position:0% connectors you have and one 21:13:27.016 --> 21:13:29.990 align:start position:0% connectors you have and one 1016<21:13:28.016> virtual<21:13:28.616> ports<21:13:29.040> this<21:13:29.336> all<21:13:29.512> depends<21:13:29.872> on 21:13:29.990 --> 21:13:30.000 align:start position:0% 1016 virtual ports this all depends on 21:13:30.000 --> 21:13:31.606 align:start position:0% 1016 virtual ports this all depends on your<21:13:30.240> software<21:13:30.600> and<21:13:30.832> Hardware<21:13:31.016> platform 21:13:31.606 --> 21:13:31.616 align:start position:0% your software and Hardware platform 21:13:31.616 --> 21:13:34.630 align:start position:0% your software and Hardware platform you're<21:13:31.920> putting<21:13:32.696> it<21:13:32.824> on<21:13:33.000> there's<21:13:33.720> a<21:13:33.832> limit<21:13:33.960> of 21:13:34.630 --> 21:13:34.640 align:start position:0% you're putting it on there's a limit of 21:13:34.640 --> 21:13:38.206 align:start position:0% you're putting it on there's a limit of 4088<21:13:35.640> ports<21:13:36.176> on<21:13:36.360> all<21:13:36.536> virtual<21:13:36.896> switches<21:13:37.376> on 21:13:38.206 --> 21:13:38.216 align:start position:0% 4088 ports on all virtual switches on 21:13:38.216 --> 21:13:40.910 align:start position:0% 4088 ports on all virtual switches on the<21:13:38.400> VMware<21:13:38.872> esxi<21:13:39.832> host 21:13:40.910 --> 21:13:40.920 align:start position:0% the VMware esxi host 21:13:40.920 --> 21:13:43.182 align:start position:0% the VMware esxi host different<21:13:41.512> vendors<21:13:42.056> May<21:13:42.480> well<21:13:42.960> have 21:13:43.182 --> 21:13:43.192 align:start position:0% different vendors May well have 21:13:43.192 --> 21:13:46.606 align:start position:0% different vendors May well have different<21:13:43.976> um<21:13:43.976> capabilities<21:13:44.696> and<21:13:45.440> rules<21:13:46.440> to 21:13:46.606 --> 21:13:46.616 align:start position:0% different um capabilities and rules to 21:13:46.616 --> 21:13:47.814 align:start position:0% different um capabilities and rules to follow 21:13:47.814 --> 21:13:47.824 align:start position:0% follow 21:13:47.824 --> 21:13:50.926 align:start position:0% follow a<21:13:48.240> virtual<21:13:48.536> send<21:13:48.832> switch<21:13:49.504> can<21:13:49.856> send<21:13:50.160> Network 21:13:50.926 --> 21:13:50.936 align:start position:0% a virtual send switch can send Network 21:13:50.936 --> 21:13:52.846 align:start position:0% a virtual send switch can send Network traffic<21:13:51.240> between<21:13:51.536> virtual<21:13:52.080> machines<21:13:52.376> on<21:13:52.744> the 21:13:52.846 --> 21:13:52.856 align:start position:0% traffic between virtual machines on the 21:13:52.856 --> 21:13:55.182 align:start position:0% traffic between virtual machines on the same<21:13:52.976> host<21:13:53.280> or<21:13:54.056> from<21:13:54.240> virtual<21:13:54.536> machines<21:13:54.832> to<21:13:55.080> an 21:13:55.182 --> 21:13:55.192 align:start position:0% same host or from virtual machines to an 21:13:55.192 --> 21:13:57.230 align:start position:0% same host or from virtual machines to an external<21:13:55.680> network<21:13:55.856> that's<21:13:56.640> outside<21:13:56.872> the 21:13:57.230 --> 21:13:57.240 align:start position:0% external network that's outside the 21:13:57.240 --> 21:14:00.774 align:start position:0% external network that's outside the virtual<21:13:57.744> virtualized<21:13:58.744> hosts<21:13:59.216> you<21:14:00.000> can<21:14:00.120> go<21:14:00.656> to 21:14:00.774 --> 21:14:00.784 align:start position:0% virtual virtualized hosts you can go to 21:14:00.784 --> 21:14:02.502 align:start position:0% virtual virtualized hosts you can go to YouTube<21:14:00.960> and<21:14:01.256> check<21:14:01.440> on<21:14:01.616> videos<21:14:01.856> on<21:14:02.216> how<21:14:02.400> to 21:14:02.502 --> 21:14:02.512 align:start position:0% YouTube and check on videos on how to 21:14:02.512 --> 21:14:06.286 align:start position:0% YouTube and check on videos on how to check<21:14:02.696> a<21:14:03.000> virtual<21:14:03.360> air<21:14:04.256> device<21:14:04.552> to<21:14:04.920> a<21:14:05.296> live 21:14:06.286 --> 21:14:06.296 align:start position:0% check a virtual air device to a live 21:14:06.296 --> 21:14:08.862 align:start position:0% check a virtual air device to a live Network<21:14:06.976> and<21:14:07.976> a<21:14:08.160> lot<21:14:08.280> of<21:14:08.336> the<21:14:08.400> time<21:14:08.512> you<21:14:08.640> do<21:14:08.824> it 21:14:08.862 --> 21:14:08.872 align:start position:0% Network and a lot of the time you do it 21:14:08.872 --> 21:14:11.390 align:start position:0% Network and a lot of the time you do it for<21:14:09.000> home<21:14:09.240> use<21:14:09.480> to<21:14:10.192> overcome 21:14:11.390 --> 21:14:11.400 align:start position:0% for home use to overcome 21:14:11.400 --> 21:14:13.734 align:start position:0% for home use to overcome um<21:14:11.480> limitations<21:14:12.480> when<21:14:12.896> you're<21:14:13.016> trying<21:14:13.256> to<21:14:13.440> get 21:14:13.734 --> 21:14:13.744 align:start position:0% um limitations when you're trying to get 21:14:13.744 --> 21:14:15.110 align:start position:0% um limitations when you're trying to get different<21:14:13.976> bits<21:14:14.336> of<21:14:14.464> software<21:14:14.824> and<21:14:14.936> Hardware 21:14:15.110 --> 21:14:15.120 align:start position:0% different bits of software and Hardware 21:14:15.120 --> 21:14:18.350 align:start position:0% different bits of software and Hardware to<21:14:15.480> work<21:14:15.720> for<21:14:16.216> certification<21:14:17.216> exams<21:14:17.936> it's 21:14:18.350 --> 21:14:18.360 align:start position:0% to work for certification exams it's 21:14:18.360 --> 21:14:19.790 align:start position:0% to work for certification exams it's quite<21:14:18.600> common 21:14:19.790 --> 21:14:19.800 align:start position:0% quite common 21:14:19.800 --> 21:14:21.950 align:start position:0% quite common virtual<21:14:20.512> switch<21:14:20.640> joins<21:14:21.120> the<21:14:21.240> network<21:14:21.360> with<21:14:21.784> a 21:14:21.950 --> 21:14:21.960 align:start position:0% virtual switch joins the network with a 21:14:21.960 --> 21:14:23.326 align:start position:0% virtual switch joins the network with a physical<21:14:22.080> Network<21:14:22.440> when<21:14:22.856> it<21:14:22.976> when<21:14:23.216> it 21:14:23.326 --> 21:14:23.336 align:start position:0% physical Network when it when it 21:14:23.336 --> 21:14:26.206 align:start position:0% physical Network when it when it connects<21:14:23.640> to<21:14:23.760> a<21:14:24.000> physical<21:14:24.360> switch<21:14:24.784> using<21:14:26.216> um 21:14:26.206 --> 21:14:26.216 align:start position:0% connects to a physical switch using um 21:14:26.216 --> 21:14:28.910 align:start position:0% connects to a physical switch using um physical<21:14:26.640> network<21:14:27.000> adapters 21:14:28.910 --> 21:14:28.920 align:start position:0% physical network adapters 21:14:28.920 --> 21:14:31.430 align:start position:0% physical network adapters uh<21:14:29.400> you<21:14:29.512> can<21:14:29.640> also<21:14:30.056> get<21:14:30.176> virtual<21:14:30.536> routers<21:14:31.080> a 21:14:31.430 --> 21:14:31.440 align:start position:0% uh you can also get virtual routers a 21:14:31.440 --> 21:14:33.230 align:start position:0% uh you can also get virtual routers a software<21:14:31.744> version<21:14:31.976> of<21:14:32.216> a<21:14:32.400> physical<21:14:32.696> router 21:14:33.230 --> 21:14:33.240 align:start position:0% software version of a physical router 21:14:33.240 --> 21:14:35.630 align:start position:0% software version of a physical router obviously<21:14:33.656> performs<21:14:34.496> your<21:14:34.680> layer<21:14:34.976> 3<21:14:35.104> packet 21:14:35.630 --> 21:14:35.640 align:start position:0% obviously performs your layer 3 packet 21:14:35.640 --> 21:14:37.454 align:start position:0% obviously performs your layer 3 packet forward<21:14:35.824> in<21:14:36.120> between 21:14:37.454 --> 21:14:37.464 align:start position:0% forward in between 21:14:37.464 --> 21:14:42.886 align:start position:0% forward in between your<21:14:38.464> subnets<21:14:39.424> or<21:14:39.896> lands<21:14:40.800> and<21:14:42.120> um<21:14:42.176> vlans 21:14:42.886 --> 21:14:42.896 align:start position:0% your subnets or lands and um vlans 21:14:42.896 --> 21:14:45.350 align:start position:0% your subnets or lands and um vlans obviously<21:14:43.320> you<21:14:43.920> need<21:14:44.040> layer<21:14:44.400> three 21:14:45.350 --> 21:14:45.360 align:start position:0% obviously you need layer three 21:14:45.360 --> 21:14:48.710 align:start position:0% obviously you need layer three capability<21:14:46.144> of<21:14:46.496> some<21:14:46.680> sort<21:14:47.400> a<21:14:47.936> virtual<21:14:48.296> router 21:14:48.710 --> 21:14:48.720 align:start position:0% capability of some sort a virtual router 21:14:48.720 --> 21:14:51.230 align:start position:0% capability of some sort a virtual router via<21:14:49.016> vrrp<21:14:49.976> which<21:14:50.280> we<21:14:50.400> covered<21:14:50.760> that<21:14:50.872> protocol 21:14:51.230 --> 21:14:51.240 align:start position:0% via vrrp which we covered that protocol 21:14:51.240 --> 21:14:52.366 align:start position:0% via vrrp which we covered that protocol earlier 21:14:52.366 --> 21:14:52.376 align:start position:0% earlier 21:14:52.376 --> 21:14:55.134 align:start position:0% earlier uh<21:14:53.040> it's<21:14:53.280> a<21:14:53.512> virtual<21:14:54.240> route<21:14:54.424> is<21:14:54.656> implemented 21:14:55.134 --> 21:14:55.144 align:start position:0% uh it's a virtual route is implemented 21:14:55.144 --> 21:14:58.246 align:start position:0% uh it's a virtual route is implemented when<21:14:55.376> you<21:14:55.504> use<21:14:55.680> vrp<21:14:56.400> to<21:14:57.240> provide<21:14:57.480> redundancy 21:14:58.246 --> 21:14:58.256 align:start position:0% when you use vrp to provide redundancy 21:14:58.256 --> 21:15:00.526 align:start position:0% when you use vrp to provide redundancy of<21:14:58.680> the<21:14:58.920> default<21:14:59.216> gateway<21:14:59.640> so<21:14:59.824> all<21:15:00.056> the<21:15:00.176> hosts 21:15:00.526 --> 21:15:00.536 align:start position:0% of the default gateway so all the hosts 21:15:00.536 --> 21:15:03.590 align:start position:0% of the default gateway so all the hosts still<21:15:01.192> have<21:15:01.440> IP<21:15:01.856> connectivity 21:15:03.590 --> 21:15:03.600 align:start position:0% still have IP connectivity 21:15:03.600 --> 21:15:04.966 align:start position:0% still have IP connectivity it's<21:15:03.832> back<21:15:04.080> by<21:15:04.320> two<21:15:04.496> or<21:15:04.616> more<21:15:04.744> physical 21:15:04.966 --> 21:15:04.976 align:start position:0% it's back by two or more physical 21:15:04.976 --> 21:15:07.006 align:start position:0% it's back by two or more physical routers<21:15:05.576> depending<21:15:06.056> on<21:15:06.176> the<21:15:06.296> protocol<21:15:06.656> you 21:15:07.006 --> 21:15:07.016 align:start position:0% routers depending on the protocol you 21:15:07.016 --> 21:15:09.110 align:start position:0% routers depending on the protocol you can<21:15:07.144> have<21:15:07.256> two<21:15:07.680> or<21:15:08.104> three 21:15:09.110 --> 21:15:09.120 align:start position:0% can have two or three 21:15:09.120 --> 21:15:10.790 align:start position:0% can have two or three I'm<21:15:09.536> not<21:15:09.720> sure<21:15:09.832> what<21:15:09.960> the<21:15:10.080> limit<21:15:10.192> is<21:15:10.496> actually 21:15:10.790 --> 21:15:10.800 align:start position:0% I'm not sure what the limit is actually 21:15:10.800 --> 21:15:12.886 align:start position:0% I'm not sure what the limit is actually depends<21:15:11.464> on<21:15:11.576> the<21:15:11.760> protocol<21:15:12.120> and<21:15:12.480> it<21:15:12.656> does 21:15:12.886 --> 21:15:12.896 align:start position:0% depends on the protocol and it does 21:15:12.896 --> 21:15:15.230 align:start position:0% depends on the protocol and it does change 21:15:15.230 --> 21:15:15.240 align:start position:0% 21:15:15.240 --> 21:15:17.990 align:start position:0% uh<21:15:15.896> why<21:15:16.016> use<21:15:16.256> a<21:15:16.440> Virtual<21:15:16.744> Router<21:15:17.216> provides<21:15:17.824> the 21:15:17.990 --> 21:15:18.000 align:start position:0% uh why use a Virtual Router provides the 21:15:18.000 --> 21:15:20.926 align:start position:0% uh why use a Virtual Router provides the same<21:15:18.176> routing<21:15:18.656> function<21:15:19.280> functionality<21:15:20.280> but 21:15:20.926 --> 21:15:20.936 align:start position:0% same routing function functionality but 21:15:20.936 --> 21:15:22.182 align:start position:0% same routing function functionality but it's<21:15:21.120> virtual<21:15:21.536> so<21:15:21.720> you've<21:15:21.896> got<21:15:22.016> all<21:15:22.080> the 21:15:22.182 --> 21:15:22.192 align:start position:0% it's virtual so you've got all the 21:15:22.192 --> 21:15:24.734 align:start position:0% it's virtual so you've got all the advantages<21:15:22.552> of<21:15:22.976> costs 21:15:24.734 --> 21:15:24.744 align:start position:0% advantages of costs 21:15:24.744 --> 21:15:28.246 align:start position:0% advantages of costs uh<21:15:25.744> virtual<21:15:26.216> firewalls<21:15:27.000> they're<21:15:27.656> mentioned 21:15:28.246 --> 21:15:28.256 align:start position:0% uh virtual firewalls they're mentioned 21:15:28.256 --> 21:15:30.822 align:start position:0% uh virtual firewalls they're mentioned again<21:15:28.856> in<21:15:29.216> the<21:15:29.336> Cisco<21:15:29.696> syllabus<21:15:30.240> probably 21:15:30.822 --> 21:15:30.832 align:start position:0% again in the Cisco syllabus probably 21:15:30.832 --> 21:15:34.006 align:start position:0% again in the Cisco syllabus probably definitely<21:15:31.616> the<21:15:31.856> CCNA<21:15:32.464> routing<21:15:32.936> briefly<21:15:33.832> but 21:15:34.006 --> 21:15:34.016 align:start position:0% definitely the CCNA routing briefly but 21:15:34.016 --> 21:15:36.110 align:start position:0% definitely the CCNA routing briefly but I<21:15:34.192> would<21:15:34.376> imagine<21:15:34.496> in<21:15:34.856> the<21:15:34.976> CCNA<21:15:35.512> Security<21:15:35.760> in 21:15:36.110 --> 21:15:36.120 align:start position:0% I would imagine in the CCNA Security in 21:15:36.120 --> 21:15:37.430 align:start position:0% I would imagine in the CCNA Security in a<21:15:36.240> lot<21:15:36.296> more<21:15:36.480> detail 21:15:37.430 --> 21:15:37.440 align:start position:0% a lot more detail 21:15:37.440 --> 21:15:39.286 align:start position:0% a lot more detail so<21:15:37.744> it's<21:15:37.856> a<21:15:38.040> virtual<21:15:38.336> version<21:15:38.576> of<21:15:38.872> an<21:15:39.056> actual 21:15:39.286 --> 21:15:39.296 align:start position:0% so it's a virtual version of an actual 21:15:39.296 --> 21:15:40.486 align:start position:0% so it's a virtual version of an actual firewall 21:15:40.486 --> 21:15:40.496 align:start position:0% firewall 21:15:40.496 --> 21:15:42.166 align:start position:0% firewall so<21:15:40.800> they're<21:15:41.040> implemented<21:15:41.512> as<21:15:41.696> a<21:15:41.872> follower 21:15:42.166 --> 21:15:42.176 align:start position:0% so they're implemented as a follower 21:15:42.176 --> 21:15:44.390 align:start position:0% so they're implemented as a follower within<21:15:42.656> a<21:15:42.832> virtual<21:15:43.080> machine<21:15:43.376> or<21:15:44.040> as<21:15:44.216> an 21:15:44.390 --> 21:15:44.400 align:start position:0% within a virtual machine or as an 21:15:44.400 --> 21:15:46.366 align:start position:0% within a virtual machine or as an appliance<21:15:44.824> it<21:15:45.056> provides<21:15:45.480> security<21:15:45.656> to<21:15:46.192> your 21:15:46.366 --> 21:15:46.376 align:start position:0% appliance it provides security to your 21:15:46.376 --> 21:15:48.710 align:start position:0% appliance it provides security to your virtual<21:15:46.920> environment 21:15:48.710 --> 21:15:48.720 align:start position:0% virtual environment 21:15:48.720 --> 21:15:51.166 align:start position:0% virtual environment does<21:15:49.144> exactly<21:15:49.616> the<21:15:49.744> same<21:15:49.920> job<21:15:50.216> as<21:15:50.640> a<21:15:50.936> hardware 21:15:51.166 --> 21:15:51.176 align:start position:0% does exactly the same job as a hardware 21:15:51.176 --> 21:15:53.270 align:start position:0% does exactly the same job as a hardware firewall 21:15:53.270 --> 21:15:53.280 align:start position:0% firewall 21:15:53.280 --> 21:15:57.286 align:start position:0% firewall just<21:15:53.936> moving<21:15:54.176> on<21:15:54.360> to<21:15:54.536> sdn<21:15:55.016> now<21:15:55.320> it's<21:15:56.640> um 21:15:57.286 --> 21:15:57.296 align:start position:0% just moving on to sdn now it's um 21:15:57.296 --> 21:15:59.686 align:start position:0% just moving on to sdn now it's um a<21:15:57.960> big<21:15:58.144> topic<21:15:58.496> and<21:15:58.680> it's<21:15:58.856> been<21:15:59.104> introduced 21:15:59.686 --> 21:15:59.696 align:start position:0% a big topic and it's been introduced 21:15:59.696 --> 21:16:03.822 align:start position:0% a big topic and it's been introduced into<21:15:59.872> the<21:16:00.176> new<21:16:00.616> Cisco<21:16:01.616> CCNA<21:16:02.464> exam<21:16:02.824> and<21:16:03.600> I<21:16:03.720> would 21:16:03.822 --> 21:16:03.832 align:start position:0% into the new Cisco CCNA exam and I would 21:16:03.832 --> 21:16:04.790 align:start position:0% into the new Cisco CCNA exam and I would imagine 21:16:04.790 --> 21:16:04.800 align:start position:0% imagine 21:16:04.800 --> 21:16:05.454 align:start position:0% imagine um 21:16:05.454 --> 21:16:05.464 align:start position:0% um 21:16:05.464 --> 21:16:06.822 align:start position:0% um it's<21:16:05.936> going<21:16:06.120> to<21:16:06.240> have<21:16:06.296> more<21:16:06.536> and<21:16:06.656> more 21:16:06.822 --> 21:16:06.832 align:start position:0% it's going to have more and more 21:16:06.832 --> 21:16:08.030 align:start position:0% it's going to have more and more prominence<21:16:07.192> over<21:16:07.376> the<21:16:07.552> years<21:16:07.616> to<21:16:07.856> come 21:16:08.030 --> 21:16:08.040 align:start position:0% prominence over the years to come 21:16:08.040 --> 21:16:11.150 align:start position:0% prominence over the years to come because<21:16:08.216> Cisco<21:16:08.824> have<21:16:09.480> invested<21:16:10.016> heavily<21:16:10.496> in 21:16:11.150 --> 21:16:11.160 align:start position:0% because Cisco have invested heavily in 21:16:11.160 --> 21:16:14.390 align:start position:0% because Cisco have invested heavily in sdn<21:16:11.760> and<21:16:12.480> there's<21:16:12.896> a<21:16:13.080> lot<21:16:13.192> of<21:16:13.800> um<21:16:13.920> some<21:16:14.216> Open 21:16:14.390 --> 21:16:14.400 align:start position:0% sdn and there's a lot of um some Open 21:16:14.400 --> 21:16:16.966 align:start position:0% sdn and there's a lot of um some Open Standards<21:16:15.056> that<21:16:15.360> have<21:16:15.480> had<21:16:15.896> a<21:16:16.144> huge<21:16:16.376> uptake<21:16:16.744> as 21:16:16.966 --> 21:16:16.976 align:start position:0% Standards that have had a huge uptake as 21:16:16.976 --> 21:16:18.166 align:start position:0% Standards that have had a huge uptake as well 21:16:18.166 --> 21:16:18.176 align:start position:0% well 21:16:18.176 --> 21:16:20.686 align:start position:0% well it<21:16:18.656> provides<21:16:19.680> um<21:16:19.680> a<21:16:20.336> high<21:16:20.512> level 21:16:20.686 --> 21:16:20.696 align:start position:0% it provides um a high level 21:16:20.696 --> 21:16:23.390 align:start position:0% it provides um a high level Administration<21:16:21.744> capability<21:16:22.744> to<21:16:23.160> network 21:16:23.390 --> 21:16:23.400 align:start position:0% Administration capability to network 21:16:23.400 --> 21:16:26.094 align:start position:0% Administration capability to network admins<21:16:24.056> it<21:16:24.784> allows<21:16:25.144> you<21:16:25.192> to<21:16:25.504> manage<21:16:25.856> your 21:16:26.094 --> 21:16:26.104 align:start position:0% admins it allows you to manage your 21:16:26.104 --> 21:16:28.310 align:start position:0% admins it allows you to manage your entire<21:16:26.336> network<21:16:26.640> through<21:16:27.120> a<21:16:27.480> user<21:16:27.784> interface 21:16:28.310 --> 21:16:28.320 align:start position:0% entire network through a user interface 21:16:28.320 --> 21:16:32.390 align:start position:0% entire network through a user interface that<21:16:29.104> abstracts<21:16:29.576> a<21:16:29.760> com<21:16:29.936> complexity<21:16:30.680> so<21:16:31.680> you 21:16:32.390 --> 21:16:32.400 align:start position:0% that abstracts a com complexity so you 21:16:32.400 --> 21:16:33.950 align:start position:0% that abstracts a com complexity so you wouldn't<21:16:32.696> necessarily<21:16:33.296> need<21:16:33.536> to<21:16:33.784> understand 21:16:33.950 --> 21:16:33.960 align:start position:0% wouldn't necessarily need to understand 21:16:33.960 --> 21:16:35.926 align:start position:0% wouldn't necessarily need to understand all<21:16:34.496> the<21:16:34.744> underlying<21:16:35.216> commands<21:16:35.640> that<21:16:35.760> have 21:16:35.926 --> 21:16:35.936 align:start position:0% all the underlying commands that have 21:16:35.936 --> 21:16:40.246 align:start position:0% all the underlying commands that have been<21:16:36.056> executed<21:16:36.720> and<21:16:37.680> how<21:16:37.920> it<21:16:38.104> all<21:16:38.216> works 21:16:40.246 --> 21:16:40.256 align:start position:0% been executed and how it all works 21:16:40.256 --> 21:16:43.134 align:start position:0% been executed and how it all works um<21:16:40.680> just<21:16:41.400> to<21:16:41.512> manage<21:16:41.760> it<21:16:41.936> if<21:16:42.120> you're<21:16:42.240> using<21:16:42.536> sdn 21:16:43.134 --> 21:16:43.144 align:start position:0% um just to manage it if you're using sdn 21:16:43.144 --> 21:16:45.110 align:start position:0% um just to manage it if you're using sdn obviously<21:16:43.920> it<21:16:43.976> helps<21:16:44.280> if<21:16:44.464> you<21:16:44.576> to<21:16:44.824> be<21:16:44.936> a 21:16:45.110 --> 21:16:45.120 align:start position:0% obviously it helps if you to be a 21:16:45.120 --> 21:16:46.246 align:start position:0% obviously it helps if you to be a network<21:16:45.296> engineer<21:16:45.832> that<21:16:45.960> you<21:16:46.080> actually 21:16:46.246 --> 21:16:46.256 align:start position:0% network engineer that you actually 21:16:46.256 --> 21:16:47.862 align:start position:0% network engineer that you actually understand<21:16:46.496> what's<21:16:46.920> happening 21:16:47.862 --> 21:16:47.872 align:start position:0% understand what's happening 21:16:47.872 --> 21:16:51.414 align:start position:0% understand what's happening but<21:16:48.960> um<21:16:49.016> now<21:16:49.680> I<21:16:49.856> suppose<21:16:50.104> it's<21:16:50.280> like<21:16:50.512> managing 21:16:51.414 --> 21:16:51.424 align:start position:0% but um now I suppose it's like managing 21:16:51.424 --> 21:16:52.486 align:start position:0% but um now I suppose it's like managing your<21:16:51.784> car 21:16:52.486 --> 21:16:52.496 align:start position:0% your car 21:16:52.496 --> 21:16:53.862 align:start position:0% your car they've<21:16:52.976> got<21:16:53.104> all<21:16:53.280> these<21:16:53.464> different<21:16:53.640> settings 21:16:53.862 --> 21:16:53.872 align:start position:0% they've got all these different settings 21:16:53.872 --> 21:16:56.150 align:start position:0% they've got all these different settings on<21:16:54.240> the<21:16:54.360> onboard<21:16:54.656> computers<21:16:55.440> that<21:16:55.856> change 21:16:56.150 --> 21:16:56.160 align:start position:0% on the onboard computers that change 21:16:56.160 --> 21:16:58.246 align:start position:0% on the onboard computers that change your<21:16:56.576> handling<21:16:57.480> and<21:16:57.832> your<21:16:58.016> engine 21:16:58.246 --> 21:16:58.256 align:start position:0% your handling and your engine 21:16:58.256 --> 21:17:00.046 align:start position:0% your handling and your engine performance<21:16:58.976> and<21:16:59.336> all<21:16:59.464> that<21:16:59.640> kind<21:16:59.824> of<21:16:59.936> thing 21:17:00.046 --> 21:17:00.056 align:start position:0% performance and all that kind of thing 21:17:00.056 --> 21:17:02.502 align:start position:0% performance and all that kind of thing you<21:17:00.360> can<21:17:00.536> turn<21:17:00.720> different<21:17:01.552> controls<21:17:02.160> on<21:17:02.336> or 21:17:02.502 --> 21:17:02.512 align:start position:0% you can turn different controls on or 21:17:02.512 --> 21:17:05.390 align:start position:0% you can turn different controls on or off<21:17:02.640> like<21:17:02.872> traction<21:17:03.296> control<21:17:03.976> and<21:17:04.976> you<21:17:05.216> don't 21:17:05.390 --> 21:17:05.400 align:start position:0% off like traction control and you don't 21:17:05.400 --> 21:17:07.134 align:start position:0% off like traction control and you don't necessarily<21:17:05.872> need<21:17:06.176> to<21:17:06.360> worry<21:17:06.536> about<21:17:06.720> how<21:17:07.016> it 21:17:07.134 --> 21:17:07.144 align:start position:0% necessarily need to worry about how it 21:17:07.144 --> 21:17:11.206 align:start position:0% necessarily need to worry about how it all<21:17:07.320> works 21:17:11.206 --> 21:17:11.216 align:start position:0% 21:17:11.216 --> 21:17:13.494 align:start position:0% all<21:17:11.640> right<21:17:11.760> sdns<21:17:12.536> are<21:17:12.784> used<21:17:12.960> to<21:17:13.144> control<21:17:13.256> the 21:17:13.494 --> 21:17:13.504 align:start position:0% all right sdns are used to control the 21:17:13.504 --> 21:17:15.886 align:start position:0% all right sdns are used to control the operation<21:17:13.800> and<21:17:14.040> network<21:17:14.216> devices 21:17:15.886 --> 21:17:15.896 align:start position:0% operation and network devices 21:17:15.896 --> 21:17:19.430 align:start position:0% operation and network devices um<21:17:15.960> look<21:17:16.744> into<21:17:17.280> more<21:17:17.576> I<21:17:17.936> think<21:17:18.120> Cisco<21:17:18.720> I'm<21:17:19.256> not 21:17:19.430 --> 21:17:19.440 align:start position:0% um look into more I think Cisco I'm not 21:17:19.440 --> 21:17:22.006 align:start position:0% um look into more I think Cisco I'm not sure<21:17:19.552> which<21:17:19.920> CCNA<21:17:20.872> version<21:17:21.056> maybe<21:17:21.424> data 21:17:22.006 --> 21:17:22.016 align:start position:0% sure which CCNA version maybe data 21:17:22.016 --> 21:17:23.990 align:start position:0% sure which CCNA version maybe data center<21:17:22.144> that<21:17:22.856> looks<21:17:23.104> interesting<21:17:23.576> any<21:17:23.824> more 21:17:23.990 --> 21:17:24.000 align:start position:0% center that looks interesting any more 21:17:24.000 --> 21:17:26.686 align:start position:0% center that looks interesting any more details<21:17:24.536> but<21:17:25.144> there's<21:17:25.376> a<21:17:25.504> whole<21:17:25.616> bunch<21:17:25.856> of<21:17:26.640> um 21:17:26.686 --> 21:17:26.696 align:start position:0% details but there's a whole bunch of um 21:17:26.696 --> 21:17:29.750 align:start position:0% details but there's a whole bunch of um controls<21:17:27.600> and<21:17:28.256> formats<21:17:28.800> that<21:17:28.920> have<21:17:29.104> to<21:17:29.280> manage 21:17:29.750 --> 21:17:29.760 align:start position:0% controls and formats that have to manage 21:17:29.760 --> 21:17:31.310 align:start position:0% controls and formats that have to manage your 21:17:31.310 --> 21:17:31.320 align:start position:0% your 21:17:31.320 --> 21:17:34.486 align:start position:0% your um<21:17:31.856> interface<21:17:32.824> between<21:17:33.120> your<21:17:33.480> network<21:17:33.720> the 21:17:34.486 --> 21:17:34.496 align:start position:0% um interface between your network the 21:17:34.496 --> 21:17:38.390 align:start position:0% um interface between your network the user<21:17:34.920> and<21:17:35.104> all<21:17:35.280> of<21:17:35.400> your<21:17:35.512> devices<21:17:36.144> and<21:17:37.144> apis<21:17:37.856> to 21:17:38.390 --> 21:17:38.400 align:start position:0% user and all of your devices and apis to 21:17:38.400 --> 21:17:40.366 align:start position:0% user and all of your devices and apis to name<21:17:38.576> one 21:17:40.366 --> 21:17:40.376 align:start position:0% name one 21:17:40.376 --> 21:17:43.070 align:start position:0% name one so<21:17:40.920> examples<21:17:41.400> of<21:17:41.640> sdns<21:17:42.424> or<21:17:42.480> Cisco<21:17:42.832> open 21:17:43.070 --> 21:17:43.080 align:start position:0% so examples of sdns or Cisco open 21:17:43.080 --> 21:17:44.774 align:start position:0% so examples of sdns or Cisco open network<21:17:43.376> environments 21:17:44.774 --> 21:17:44.784 align:start position:0% network environments 21:17:44.784 --> 21:17:47.350 align:start position:0% network environments nikira's<21:17:45.784> Network<21:17:45.896> virtualization<21:17:46.744> platform 21:17:47.350 --> 21:17:47.360 align:start position:0% nikira's Network virtualization platform 21:17:47.360 --> 21:17:50.454 align:start position:0% nikira's Network virtualization platform why<21:17:48.360> bother<21:17:48.784> it<21:17:49.552> basically<21:17:49.800> makes<21:17:50.040> your<21:17:50.280> life 21:17:50.454 --> 21:17:50.464 align:start position:0% why bother it basically makes your life 21:17:50.464 --> 21:17:51.774 align:start position:0% why bother it basically makes your life a<21:17:50.696> lot<21:17:50.824> easier<21:17:51.056> as<21:17:51.296> the<21:17:51.600> network 21:17:51.774 --> 21:17:51.784 align:start position:0% a lot easier as the network 21:17:51.784 --> 21:17:54.350 align:start position:0% a lot easier as the network administrator<21:17:52.552> you<21:17:53.400> can<21:17:53.512> interact<21:17:53.936> with<21:17:54.176> your 21:17:54.350 --> 21:17:54.360 align:start position:0% administrator you can interact with your 21:17:54.360 --> 21:17:56.390 align:start position:0% administrator you can interact with your entire<21:17:54.600> network<21:17:54.960> without<21:17:55.744> having<21:17:56.104> to 21:17:56.390 --> 21:17:56.400 align:start position:0% entire network without having to 21:17:56.400 --> 21:17:59.390 align:start position:0% entire network without having to actually<21:17:56.640> connect<21:17:57.680> via<21:17:58.680> telnet<21:17:59.216> or 21:17:59.390 --> 21:17:59.400 align:start position:0% actually connect via telnet or 21:17:59.400 --> 21:18:01.606 align:start position:0% actually connect via telnet or physically<21:17:59.696> connect<21:18:00.000> to<21:18:00.656> your<21:18:00.832> devices<21:18:01.144> or 21:18:01.606 --> 21:18:01.616 align:start position:0% physically connect to your devices or 21:18:01.616 --> 21:18:03.646 align:start position:0% physically connect to your devices or even<21:18:01.744> understand<21:18:02.040> all<21:18:02.696> of<21:18:02.824> the<21:18:03.056> different 21:18:03.646 --> 21:18:03.656 align:start position:0% even understand all of the different 21:18:03.656 --> 21:18:06.366 align:start position:0% even understand all of the different commands<21:18:04.320> so<21:18:04.800> if<21:18:05.040> you're<21:18:05.280> using 21:18:06.366 --> 21:18:06.376 align:start position:0% commands so if you're using 21:18:06.376 --> 21:18:09.774 align:start position:0% commands so if you're using Juniper<21:18:07.376> Hardware<21:18:07.616> it's<21:18:08.104> got<21:18:08.336> one<21:18:08.696> type<21:18:08.936> of 21:18:09.774 --> 21:18:09.784 align:start position:0% Juniper Hardware it's got one type of 21:18:09.784 --> 21:18:10.966 align:start position:0% Juniper Hardware it's got one type of um 21:18:10.966 --> 21:18:10.976 align:start position:0% um 21:18:10.976 --> 21:18:14.270 align:start position:0% um command<21:18:11.696> line<21:18:11.824> interface<21:18:12.480> for<21:18:13.504> um<21:18:13.504> copyright 21:18:14.270 --> 21:18:14.280 align:start position:0% command line interface for um copyright 21:18:14.280 --> 21:18:19.670 align:start position:0% command line interface for um copyright reasons<21:18:15.120> your<21:18:15.896> Huawei<21:18:16.640> and<21:18:17.640> Cisco<21:18:18.536> all<21:18:19.504> got 21:18:19.670 --> 21:18:19.680 align:start position:0% reasons your Huawei and Cisco all got 21:18:19.680 --> 21:18:21.110 align:start position:0% reasons your Huawei and Cisco all got different<21:18:19.920> command<21:18:20.336> lines<21:18:20.640> different 21:18:21.110 --> 21:18:21.120 align:start position:0% different command lines different 21:18:21.120 --> 21:18:23.150 align:start position:0% different command lines different commands<21:18:21.720> all<21:18:22.080> to<21:18:22.320> achieve<21:18:22.680> the<21:18:22.800> same<21:18:22.976> thing 21:18:23.150 --> 21:18:23.160 align:start position:0% commands all to achieve the same thing 21:18:23.160 --> 21:18:24.470 align:start position:0% commands all to achieve the same thing so<21:18:23.400> you<21:18:23.576> don't<21:18:23.696> you<21:18:23.936> don't<21:18:24.056> need<21:18:24.240> to<21:18:24.296> worry 21:18:24.470 --> 21:18:24.480 align:start position:0% so you don't you don't need to worry 21:18:24.480 --> 21:18:27.470 align:start position:0% so you don't you don't need to worry about<21:18:24.656> that<21:18:24.832> if<21:18:25.016> you're<21:18:25.144> using<21:18:25.376> SDM 21:18:27.470 --> 21:18:27.480 align:start position:0% about that if you're using SDM 21:18:27.480 --> 21:18:30.526 align:start position:0% about that if you're using SDM so<21:18:27.960> get<21:18:28.144> get<21:18:28.376> rid<21:18:28.552> of<21:18:28.744> the<21:18:28.920> command<21:18:29.512> line<21:18:29.760> some 21:18:30.526 --> 21:18:30.536 align:start position:0% so get get rid of the command line some 21:18:30.536 --> 21:18:32.926 align:start position:0% so get get rid of the command line some of<21:18:30.720> the<21:18:30.832> benefits<21:18:31.256> again<21:18:31.504> the<21:18:32.104> graphical<21:18:32.464> user 21:18:32.926 --> 21:18:32.936 align:start position:0% of the benefits again the graphical user 21:18:32.936 --> 21:18:35.030 align:start position:0% of the benefits again the graphical user interface<21:18:33.424> provides<21:18:34.144> information<21:18:34.616> about 21:18:35.030 --> 21:18:35.040 align:start position:0% interface provides information about 21:18:35.040 --> 21:18:37.494 align:start position:0% interface provides information about what's<21:18:35.336> going<21:18:35.512> on<21:18:35.640> with<21:18:35.872> your<21:18:36.000> network 21:18:37.494 --> 21:18:37.504 align:start position:0% what's going on with your network 21:18:37.504 --> 21:18:40.246 align:start position:0% what's going on with your network it<21:18:37.920> allows<21:18:38.216> you<21:18:38.280> to<21:18:38.464> specify<21:18:38.872> changes<21:18:39.480> and 21:18:40.246 --> 21:18:40.256 align:start position:0% it allows you to specify changes and 21:18:40.256 --> 21:18:41.390 align:start position:0% it allows you to specify changes and behind<21:18:40.616> the<21:18:40.744> scenes<21:18:40.976> the<21:18:41.160> actual 21:18:41.390 --> 21:18:41.400 align:start position:0% behind the scenes the actual 21:18:41.400 --> 21:18:43.182 align:start position:0% behind the scenes the actual configurations<21:18:41.936> are<21:18:42.296> done<21:18:42.536> with<21:18:43.016> the 21:18:43.182 --> 21:18:43.192 align:start position:0% configurations are done with the 21:18:43.192 --> 21:18:45.886 align:start position:0% configurations are done with the interface<21:18:43.552> one<21:18:43.856> of<21:18:44.040> the<21:18:44.160> apis<21:18:44.640> between<21:18:45.176> the 21:18:45.886 --> 21:18:45.896 align:start position:0% interface one of the apis between the 21:18:45.896 --> 21:18:48.710 align:start position:0% interface one of the apis between the software<21:18:46.192> and<21:18:46.440> the<21:18:46.680> hardware 21:18:48.710 --> 21:18:48.720 align:start position:0% software and the hardware 21:18:48.720 --> 21:18:50.206 align:start position:0% software and the hardware all<21:18:49.192> right<21:18:49.376> so<21:18:49.504> it's<21:18:49.680> just<21:18:49.680> an<21:18:49.920> overview 21:18:50.206 --> 21:18:50.216 align:start position:0% all right so it's just an overview 21:18:50.216 --> 21:18:52.366 align:start position:0% all right so it's just an overview looked<21:18:50.760> at<21:18:50.872> virtual<21:18:51.176> networking<21:18:51.784> the<21:18:52.080> virtual 21:18:52.366 --> 21:18:52.376 align:start position:0% looked at virtual networking the virtual 21:18:52.376 --> 21:18:54.846 align:start position:0% looked at virtual networking the virtual adapters<21:18:52.976> virtual<21:18:53.512> switches<21:18:54.000> and<21:18:54.240> routers 21:18:54.846 --> 21:18:54.856 align:start position:0% adapters virtual switches and routers 21:18:54.856 --> 21:18:57.230 align:start position:0% adapters virtual switches and routers the<21:18:55.856> RRP 21:18:57.230 --> 21:18:57.240 align:start position:0% the RRP 21:18:57.240 --> 21:18:59.206 align:start position:0% the RRP firewalls<21:18:58.144> and<21:18:58.376> software-defined 21:18:59.206 --> 21:18:59.216 align:start position:0% firewalls and software-defined 21:18:59.216 --> 21:19:01.310 align:start position:0% firewalls and software-defined networking<21:18:59.760> and<21:19:00.176> why<21:19:00.360> why<21:19:00.720> would<21:19:01.016> we<21:19:01.144> be 21:19:01.310 --> 21:19:01.320 align:start position:0% networking and why why would we be 21:19:01.320 --> 21:19:02.990 align:start position:0% networking and why why would we be interested<21:19:01.680> in<21:19:01.856> using<21:19:02.336> it 21:19:02.990 --> 21:19:03.000 align:start position:0% interested in using it 21:19:03.000 --> 21:19:09.860 align:start position:0% interested in using it so<21:19:03.176> that's<21:19:03.296> all<21:19:03.536> thanks<21:19:03.896> for<21:19:04.080> watching 21:19:09.860 --> 21:19:09.870 align:start position:0% 21:19:09.870 --> 21:19:25.846 align:start position:0% [Music] 21:19:25.846 --> 21:19:25.856 align:start position:0% 21:19:25.856 --> 21:19:28.966 align:start position:0% welcome<21:19:26.464> to<21:19:26.640> module<21:19:27.056> 17<21:19:27.296> lesson<21:19:28.080> 3<21:19:28.256> the 21:19:28.966 --> 21:19:28.976 align:start position:0% welcome to module 17 lesson 3 the 21:19:28.976 --> 21:19:31.494 align:start position:0% welcome to module 17 lesson 3 the storage<21:19:29.280> area<21:19:29.824> network 21:19:31.494 --> 21:19:31.504 align:start position:0% storage area network 21:19:31.504 --> 21:19:34.246 align:start position:0% storage area network I<21:19:32.216> think<21:19:32.512> come<21:19:32.824> to<21:19:33.056> your<21:19:33.240> actually<21:19:33.424> have<21:19:34.080> a 21:19:34.246 --> 21:19:34.256 align:start position:0% I think come to your actually have a 21:19:34.256 --> 21:19:37.006 align:start position:0% I think come to your actually have a qualification<21:19:34.976> uh<21:19:35.696> storage<21:19:35.936> area<21:19:36.176> networking 21:19:37.006 --> 21:19:37.016 align:start position:0% qualification uh storage area networking 21:19:37.016 --> 21:19:38.750 align:start position:0% qualification uh storage area networking engineer<21:19:37.552> Plus 21:19:38.750 --> 21:19:38.760 align:start position:0% engineer Plus 21:19:38.760 --> 21:19:42.110 align:start position:0% engineer Plus and<21:19:39.296> we<21:19:39.960> actually<21:19:40.080> have<21:19:40.976> um<21:19:40.976> such<21:19:41.576> a<21:19:41.760> course<21:19:41.936> on 21:19:42.110 --> 21:19:42.120 align:start position:0% and we actually have um such a course on 21:19:42.120 --> 21:19:44.686 align:start position:0% and we actually have um such a course on howturnetwork.com<21:19:43.280> this<21:19:44.280> is<21:19:44.400> just<21:19:44.512> an 21:19:44.686 --> 21:19:44.696 align:start position:0% howturnetwork.com this is just an 21:19:44.696 --> 21:19:46.542 align:start position:0% howturnetwork.com this is just an overview<21:19:45.000> touching<21:19:45.656> on<21:19:45.832> some<21:19:46.144> of<21:19:46.256> the 21:19:46.542 --> 21:19:46.552 align:start position:0% overview touching on some of the 21:19:46.552 --> 21:19:49.910 align:start position:0% overview touching on some of the subjects<21:19:47.280> they<21:19:47.512> mentioned<21:19:48.080> in<21:19:49.080> the<21:19:49.376> exam 21:19:49.910 --> 21:19:49.920 align:start position:0% subjects they mentioned in the exam 21:19:49.920 --> 21:19:53.270 align:start position:0% subjects they mentioned in the exam syllabus 21:19:53.270 --> 21:19:53.280 align:start position:0% 21:19:53.280 --> 21:19:55.990 align:start position:0% looking<21:19:53.824> at<21:19:54.000> storage<21:19:54.176> area<21:19:54.480> networks<21:19:55.144> direct 21:19:55.990 --> 21:19:56.000 align:start position:0% looking at storage area networks direct 21:19:56.000 --> 21:19:58.846 align:start position:0% looking at storage area networks direct attached<21:19:57.000> storage<21:19:57.240> network<21:19:58.192> attached 21:19:58.846 --> 21:19:58.856 align:start position:0% attached storage network attached 21:19:58.856 --> 21:20:00.246 align:start position:0% attached storage network attached storage 21:20:00.246 --> 21:20:00.256 align:start position:0% storage 21:20:00.256 --> 21:20:03.414 align:start position:0% storage sanvi<21:20:01.256> Das 21:20:03.414 --> 21:20:03.424 align:start position:0% sanvi Das 21:20:03.424 --> 21:20:05.270 align:start position:0% sanvi Das Sun<21:20:03.896> media 21:20:05.270 --> 21:20:05.280 align:start position:0% Sun media 21:20:05.280 --> 21:20:06.846 align:start position:0% Sun media fiber<21:20:05.872> channel 21:20:06.846 --> 21:20:06.856 align:start position:0% fiber channel 21:20:06.856 --> 21:20:09.230 align:start position:0% fiber channel iSCSI<21:20:07.856> San 21:20:09.230 --> 21:20:09.240 align:start position:0% iSCSI San 21:20:09.240 --> 21:20:12.110 align:start position:0% iSCSI San Jose<21:20:09.680> architecture<21:20:10.680> and<21:20:11.400> components<21:20:12.000> of 21:20:12.110 --> 21:20:12.120 align:start position:0% Jose architecture and components of 21:20:12.120 --> 21:20:15.230 align:start position:0% Jose architecture and components of voice<21:20:12.240> guzzy<21:20:12.896> also<21:20:13.616> jumbo<21:20:14.104> frames 21:20:15.230 --> 21:20:15.240 align:start position:0% voice guzzy also jumbo frames 21:20:15.240 --> 21:20:17.094 align:start position:0% voice guzzy also jumbo frames Sun<21:20:15.720> as<21:20:16.016> we<21:20:16.144> already<21:20:16.256> know<21:20:16.496> stands<21:20:17.040> for 21:20:17.094 --> 21:20:17.104 align:start position:0% Sun as we already know stands for 21:20:17.104 --> 21:20:19.310 align:start position:0% Sun as we already know stands for storage<21:20:17.512> area<21:20:17.824> network<21:20:18.240> it's<21:20:18.720> a<21:20:18.960> high<21:20:19.080> speed 21:20:19.310 --> 21:20:19.320 align:start position:0% storage area network it's a high speed 21:20:19.320 --> 21:20:22.366 align:start position:0% storage area network it's a high speed Network<21:20:19.760> the<21:20:20.760> idea<21:20:21.056> is<21:20:21.176> it<21:20:21.424> allows 21:20:22.366 --> 21:20:22.376 align:start position:0% Network the idea is it allows 21:20:22.376 --> 21:20:24.166 align:start position:0% Network the idea is it allows um transfer<21:20:23.040> between<21:20:23.216> the<21:20:23.464> computer<21:20:23.640> systems 21:20:24.166 --> 21:20:24.176 align:start position:0% um transfer between the computer systems 21:20:24.176 --> 21:20:26.862 align:start position:0% um transfer between the computer systems and<21:20:24.424> the<21:20:24.600> storage<21:20:24.784> devices<21:20:25.320> it's<21:20:26.104> optimized 21:20:26.862 --> 21:20:26.872 align:start position:0% and the storage devices it's optimized 21:20:26.872 --> 21:20:29.926 align:start position:0% and the storage devices it's optimized for<21:20:27.176> this<21:20:27.480> type<21:20:27.720> of<21:20:28.336> Technology<21:20:29.336> as<21:20:29.760> well 21:20:29.926 --> 21:20:29.936 align:start position:0% for this type of Technology as well 21:20:29.936 --> 21:20:31.966 align:start position:0% for this type of Technology as well we'll<21:20:30.176> see<21:20:30.296> this<21:20:30.480> as<21:20:30.656> we<21:20:30.832> go<21:20:30.960> along 21:20:31.966 --> 21:20:31.976 align:start position:0% we'll see this as we go along 21:20:31.976 --> 21:20:35.030 align:start position:0% we'll see this as we go along and<21:20:32.640> here's<21:20:33.176> an<21:20:33.240> example<21:20:33.600> which<21:20:34.496> will<21:20:35.040> um 21:20:35.030 --> 21:20:35.040 align:start position:0% and here's an example which will um 21:20:35.040 --> 21:20:38.206 align:start position:0% and here's an example which will um you'll<21:20:35.512> see<21:20:35.640> in<21:20:35.824> a<21:20:35.936> few<21:20:36.056> slides 21:20:38.206 --> 21:20:38.216 align:start position:0% you'll see in a few slides 21:20:38.216 --> 21:20:40.134 align:start position:0% you'll see in a few slides so<21:20:38.640> why<21:20:38.824> bother<21:20:39.176> at<21:20:39.296> all<21:20:39.424> why<21:20:39.656> do<21:20:39.784> we<21:20:39.896> need<21:20:40.016> a 21:20:40.134 --> 21:20:40.144 align:start position:0% so why bother at all why do we need a 21:20:40.144 --> 21:20:42.950 align:start position:0% so why bother at all why do we need a storage<21:20:40.320> area<21:20:40.744> network<21:20:41.512> again<21:20:41.960> everything 21:20:42.950 --> 21:20:42.960 align:start position:0% storage area network again everything 21:20:42.960 --> 21:20:45.110 align:start position:0% storage area network again everything covered<21:20:43.856> really<21:20:43.976> in<21:20:44.160> the<21:20:44.280> network<21:20:44.400> plus<21:20:44.760> was 21:20:45.110 --> 21:20:45.120 align:start position:0% covered really in the network plus was 21:20:45.120 --> 21:20:48.646 align:start position:0% covered really in the network plus was created<21:20:45.960> in<21:20:46.744> order<21:20:46.920> to<21:20:47.040> solve<21:20:47.576> some<21:20:47.872> specific 21:20:48.646 --> 21:20:48.656 align:start position:0% created in order to solve some specific 21:20:48.656 --> 21:20:51.230 align:start position:0% created in order to solve some specific or<21:20:49.016> general<21:20:49.256> networking<21:20:50.040> problem 21:20:51.230 --> 21:20:51.240 align:start position:0% or general networking problem 21:20:51.240 --> 21:20:53.094 align:start position:0% or general networking problem it's<21:20:51.656> the<21:20:51.832> evolution<21:20:52.192> in<21:20:52.552> data<21:20:52.920> storage 21:20:53.094 --> 21:20:53.104 align:start position:0% it's the evolution in data storage 21:20:53.104 --> 21:20:55.182 align:start position:0% it's the evolution in data storage technology<21:20:53.760> and<21:20:54.000> we'll<21:20:54.176> look<21:20:54.360> at<21:20:54.480> some<21:20:54.656> Legacy 21:20:55.182 --> 21:20:55.192 align:start position:0% technology and we'll look at some Legacy 21:20:55.192 --> 21:20:57.774 align:start position:0% technology and we'll look at some Legacy ideas<21:20:55.856> in<21:20:56.216> a<21:20:56.336> moment 21:20:57.774 --> 21:20:57.784 align:start position:0% ideas in a moment 21:20:57.784 --> 21:21:00.822 align:start position:0% ideas in a moment so<21:20:58.856> um<21:20:58.920> unfortunately<21:20:59.760> this<21:21:00.120> I'll<21:21:00.600> put<21:21:00.720> the 21:21:00.822 --> 21:21:00.832 align:start position:0% so um unfortunately this I'll put the 21:21:00.832 --> 21:21:02.150 align:start position:0% so um unfortunately this I'll put the wrong<21:21:01.016> order<21:21:01.192> here<21:21:01.440> so<21:21:01.552> the<21:21:01.800> lines<21:21:01.976> are 21:21:02.150 --> 21:21:02.160 align:start position:0% wrong order here so the lines are 21:21:02.160 --> 21:21:03.822 align:start position:0% wrong order here so the lines are appearing<21:21:02.464> in<21:21:02.576> the<21:21:02.640> wrong<21:21:02.760> order<21:21:02.936> there's 21:21:03.822 --> 21:21:03.832 align:start position:0% appearing in the wrong order there's 21:21:03.832 --> 21:21:05.150 align:start position:0% appearing in the wrong order there's been<21:21:04.016> progress<21:21:04.376> in<21:21:04.552> the<21:21:04.680> data<21:21:04.976> storage 21:21:05.150 --> 21:21:05.160 align:start position:0% been progress in the data storage 21:21:05.160 --> 21:21:09.350 align:start position:0% been progress in the data storage technology<21:21:05.872> from<21:21:06.480> Das<21:21:07.376> to<21:21:07.920> Sam<21:21:08.360> direct 21:21:09.350 --> 21:21:09.360 align:start position:0% technology from Das to Sam direct 21:21:09.360 --> 21:21:12.470 align:start position:0% technology from Das to Sam direct attached<21:21:09.896> storage<21:21:10.080> is<21:21:10.552> the<21:21:10.920> traditional 21:21:12.470 --> 21:21:12.480 align:start position:0% attached storage is the traditional 21:21:12.480 --> 21:21:15.230 align:start position:0% attached storage is the traditional way<21:21:13.320> and<21:21:13.856> it's<21:21:14.160> I'm<21:21:14.464> sure<21:21:14.640> many<21:21:14.872> companies 21:21:15.230 --> 21:21:15.240 align:start position:0% way and it's I'm sure many companies 21:21:15.240 --> 21:21:18.110 align:start position:0% way and it's I'm sure many companies still<21:21:15.480> use<21:21:15.720> it<21:21:15.896> those<21:21:16.256> who<21:21:16.496> don't<21:21:16.680> use<21:21:16.976> uh<21:21:17.872> San 21:21:18.110 --> 21:21:18.120 align:start position:0% still use it those who don't use uh San 21:21:18.120 --> 21:21:20.454 align:start position:0% still use it those who don't use uh San as<21:21:18.536> a<21:21:18.720> solution<21:21:19.016> for<21:21:19.320> storage 21:21:20.454 --> 21:21:20.464 align:start position:0% as a solution for storage 21:21:20.464 --> 21:21:22.790 align:start position:0% as a solution for storage so<21:21:21.000> a<21:21:21.240> traditional<21:21:21.600> client<21:21:21.896> server<21:21:22.320> systems 21:21:22.790 --> 21:21:22.800 align:start position:0% so a traditional client server systems 21:21:22.800 --> 21:21:24.822 align:start position:0% so a traditional client server systems each<21:21:23.400> sort<21:21:23.640> of<21:21:23.760> server<21:21:24.120> having<21:21:24.360> its<21:21:24.784> own 21:21:24.822 --> 21:21:24.832 align:start position:0% each sort of server having its own 21:21:24.832 --> 21:21:27.350 align:start position:0% each sort of server having its own storage<21:21:25.216> and<21:21:26.216> the<21:21:26.400> storage<21:21:26.576> is<21:21:26.872> directly 21:21:27.350 --> 21:21:27.360 align:start position:0% storage and the storage is directly 21:21:27.360 --> 21:21:29.630 align:start position:0% storage and the storage is directly attached<21:21:27.784> to<21:21:27.960> the<21:21:28.192> server<21:21:28.640> internally 21:21:29.630 --> 21:21:29.640 align:start position:0% attached to the server internally 21:21:29.640 --> 21:21:32.686 align:start position:0% attached to the server internally usually<21:21:30.176> or<21:21:30.480> it<21:21:30.600> could<21:21:30.720> be<21:21:30.832> external 21:21:32.686 --> 21:21:32.696 align:start position:0% usually or it could be external 21:21:32.696 --> 21:21:34.206 align:start position:0% usually or it could be external search 21:21:34.206 --> 21:21:34.216 align:start position:0% search 21:21:34.216 --> 21:21:37.182 align:start position:0% search a<21:21:35.216> technology<21:21:35.640> is<21:21:36.296> referred<21:21:36.720> to<21:21:36.784> as<21:21:36.960> direct 21:21:37.182 --> 21:21:37.192 align:start position:0% a technology is referred to as direct 21:21:37.192 --> 21:21:40.006 align:start position:0% a technology is referred to as direct attached<21:21:38.160> storage<21:21:38.400> or<21:21:38.696> Das 21:21:40.006 --> 21:21:40.016 align:start position:0% attached storage or Das 21:21:40.016 --> 21:21:41.990 align:start position:0% attached storage or Das so<21:21:40.616> there<21:21:40.920> obviously<21:21:41.216> has<21:21:41.336> to<21:21:41.464> be<21:21:41.576> advantages 21:21:41.990 --> 21:21:42.000 align:start position:0% so there obviously has to be advantages 21:21:42.000 --> 21:21:44.094 align:start position:0% so there obviously has to be advantages it's<21:21:42.536> high<21:21:42.832> speed<21:21:43.080> and<21:21:43.440> it's<21:21:43.616> exclusive 21:21:44.094 --> 21:21:44.104 align:start position:0% it's high speed and it's exclusive 21:21:44.104 --> 21:21:48.350 align:start position:0% it's high speed and it's exclusive access<21:21:44.400> to<21:21:44.872> the<21:21:45.000> storage<21:21:45.176> so<21:21:45.600> it's<21:21:45.784> not<21:21:45.960> shared 21:21:48.350 --> 21:21:48.360 align:start position:0% access to the storage so it's not shared 21:21:48.360 --> 21:21:50.630 align:start position:0% access to the storage so it's not shared preferred<21:21:49.320> by<21:21:49.440> small<21:21:49.616> companies<21:21:50.104> just 21:21:50.630 --> 21:21:50.640 align:start position:0% preferred by small companies just 21:21:50.640 --> 21:21:52.990 align:start position:0% preferred by small companies just cheaper<21:21:51.120> to<21:21:51.240> implement<21:21:51.656> easier<21:21:52.192> to<21:21:52.376> implement 21:21:52.990 --> 21:21:53.000 align:start position:0% cheaper to implement easier to implement 21:21:53.000 --> 21:21:55.494 align:start position:0% cheaper to implement easier to implement easier<21:21:54.000> to<21:21:54.960> um 21:21:55.494 --> 21:21:55.504 align:start position:0% easier to um 21:21:55.504 --> 21:21:58.430 align:start position:0% easier to um troubleshoot<21:21:56.464> maintain 21:21:58.430 --> 21:21:58.440 align:start position:0% troubleshoot maintain 21:21:58.440 --> 21:22:00.414 align:start position:0% troubleshoot maintain obviously<21:21:59.040> there<21:21:59.280> are<21:21:59.400> disadvantages<21:22:00.000> which 21:22:00.414 --> 21:22:00.424 align:start position:0% obviously there are disadvantages which 21:22:00.424 --> 21:22:02.390 align:start position:0% obviously there are disadvantages which is<21:22:00.536> why<21:22:00.832> it's<21:22:01.376> been 21:22:02.390 --> 21:22:02.400 align:start position:0% is why it's been 21:22:02.400 --> 21:22:03.046 align:start position:0% is why it's been um 21:22:03.046 --> 21:22:03.056 align:start position:0% um 21:22:03.056 --> 21:22:06.350 align:start position:0% um superseded<21:22:03.896> by<21:22:04.192> many<21:22:04.376> companies<21:22:05.000> so<21:22:06.000> what<21:22:06.240> you 21:22:06.350 --> 21:22:06.360 align:start position:0% superseded by many companies so what you 21:22:06.360 --> 21:22:08.454 align:start position:0% superseded by many companies so what you get<21:22:06.480> is<21:22:06.656> a<21:22:06.832> pocket<21:22:07.080> of<21:22:07.256> isolated<21:22:07.680> storage<21:22:08.040> it's 21:22:08.454 --> 21:22:08.464 align:start position:0% get is a pocket of isolated storage it's 21:22:08.464 --> 21:22:11.566 align:start position:0% get is a pocket of isolated storage it's not<21:22:08.824> officially<21:22:09.656> utilized<21:22:10.440> and<21:22:11.104> this<21:22:11.280> ties 21:22:11.566 --> 21:22:11.576 align:start position:0% not officially utilized and this ties 21:22:11.576 --> 21:22:13.606 align:start position:0% not officially utilized and this ties into<21:22:11.760> virtualization<21:22:12.656> really<21:22:12.960> where<21:22:13.320> you 21:22:13.606 --> 21:22:13.616 align:start position:0% into virtualization really where you 21:22:13.616 --> 21:22:16.134 align:start position:0% into virtualization really where you we've<21:22:13.976> got<21:22:14.104> this<21:22:14.336> whole<21:22:14.576> amount<21:22:15.536> of<21:22:15.656> resources 21:22:16.134 --> 21:22:16.144 align:start position:0% we've got this whole amount of resources 21:22:16.144 --> 21:22:17.926 align:start position:0% we've got this whole amount of resources but<21:22:16.440> we<21:22:16.616> may<21:22:16.800> only<21:22:16.976> be<21:22:17.160> using<21:22:17.576> a<21:22:17.824> certain 21:22:17.926 --> 21:22:17.936 align:start position:0% but we may only be using a certain 21:22:17.936 --> 21:22:21.310 align:start position:0% but we may only be using a certain percentage<21:22:18.424> of<21:22:18.720> it<21:22:18.832> which<21:22:19.376> is<21:22:19.504> a<21:22:19.744> waste 21:22:21.310 --> 21:22:21.320 align:start position:0% percentage of it which is a waste 21:22:21.320 --> 21:22:23.630 align:start position:0% percentage of it which is a waste so<21:22:22.320> for<21:22:22.496> example<21:22:22.744> when<21:22:22.976> one<21:22:23.160> server<21:22:23.512> has 21:22:23.630 --> 21:22:23.640 align:start position:0% so for example when one server has 21:22:23.640 --> 21:22:25.734 align:start position:0% so for example when one server has plenty<21:22:24.000> of<21:22:24.056> C<21:22:24.296> uh<21:22:24.784> free<21:22:24.960> storage<21:22:25.256> and<21:22:25.616> the 21:22:25.734 --> 21:22:25.744 align:start position:0% plenty of C uh free storage and the 21:22:25.744 --> 21:22:27.230 align:start position:0% plenty of C uh free storage and the other<21:22:25.856> one<21:22:25.976> has<21:22:26.216> almost<21:22:26.464> ran<21:22:26.824> out<21:22:26.936> of<21:22:27.056> space 21:22:27.230 --> 21:22:27.240 align:start position:0% other one has almost ran out of space 21:22:27.240 --> 21:22:29.926 align:start position:0% other one has almost ran out of space then<21:22:27.960> we've<21:22:28.256> got<21:22:28.440> a<21:22:28.616> disparity 21:22:29.926 --> 21:22:29.936 align:start position:0% then we've got a disparity 21:22:29.936 --> 21:22:32.150 align:start position:0% then we've got a disparity this<21:22:30.480> is<21:22:30.600> where<21:22:31.376> um<21:22:31.376> Network<21:22:31.616> attaches 21:22:32.150 --> 21:22:32.160 align:start position:0% this is where um Network attaches 21:22:32.160 --> 21:22:34.310 align:start position:0% this is where um Network attaches storage<21:22:32.280> will<21:22:32.824> help<21:22:33.000> direct<21:22:33.784> attached 21:22:34.310 --> 21:22:34.320 align:start position:0% storage will help direct attached 21:22:34.320 --> 21:22:36.230 align:start position:0% storage will help direct attached storage<21:22:34.440> design<21:22:34.976> doesn't<21:22:35.336> allow<21:22:35.696> the<21:22:35.936> free 21:22:36.230 --> 21:22:36.240 align:start position:0% storage design doesn't allow the free 21:22:36.240 --> 21:22:39.950 align:start position:0% storage design doesn't allow the free capacity<21:22:37.016> of<21:22:37.256> the<21:22:37.376> servers<21:22:37.744> to<21:22:37.920> be<21:22:38.040> shared 21:22:39.950 --> 21:22:39.960 align:start position:0% capacity of the servers to be shared 21:22:39.960 --> 21:22:42.230 align:start position:0% capacity of the servers to be shared so<21:22:40.616> when<21:22:40.800> a<21:22:41.040> business<21:22:41.160> deploys<21:22:41.640> more<21:22:41.872> servers 21:22:42.230 --> 21:22:42.240 align:start position:0% so when a business deploys more servers 21:22:42.240 --> 21:22:44.630 align:start position:0% so when a business deploys more servers in<21:22:42.360> the<21:22:42.480> network<21:22:42.656> the<21:22:43.016> following<21:22:43.440> occurs 21:22:44.630 --> 21:22:44.640 align:start position:0% in the network the following occurs 21:22:44.640 --> 21:22:46.182 align:start position:0% in the network the following occurs there's<21:22:45.056> an<21:22:45.240> increase<21:22:45.360> in<21:22:45.600> the<21:22:45.784> wastage 21:22:46.182 --> 21:22:46.192 align:start position:0% there's an increase in the wastage 21:22:46.192 --> 21:22:48.710 align:start position:0% there's an increase in the wastage increase<21:22:47.040> in<21:22:47.336> the<21:22:47.512> complexity<21:22:48.000> of<21:22:48.296> managing 21:22:48.710 --> 21:22:48.720 align:start position:0% increase in the complexity of managing 21:22:48.720 --> 21:22:51.046 align:start position:0% increase in the complexity of managing all<21:22:48.960> of<21:22:49.080> these<21:22:49.192> isolated<21:22:49.760> storage<21:22:50.760> because 21:22:51.046 --> 21:22:51.056 align:start position:0% all of these isolated storage because 21:22:51.056 --> 21:22:53.094 align:start position:0% all of these isolated storage because usually<21:22:51.424> you've<21:22:51.656> got<21:22:51.784> raid<21:22:52.256> so<21:22:52.616> you've<21:22:52.856> got<21:22:52.920> to 21:22:53.094 --> 21:22:53.104 align:start position:0% usually you've got raid so you've got to 21:22:53.104 --> 21:22:57.110 align:start position:0% usually you've got raid so you've got to insert<21:22:53.640> and<21:22:53.824> pull<21:22:54.056> out<21:22:54.240> various<21:22:54.832> disks 21:22:57.110 --> 21:22:57.120 align:start position:0% insert and pull out various disks 21:22:57.120 --> 21:22:59.150 align:start position:0% insert and pull out various disks and<21:22:57.600> network<21:22:57.784> attached<21:22:58.320> storage<21:22:58.496> another 21:22:59.150 --> 21:22:59.160 align:start position:0% and network attached storage another 21:22:59.160 --> 21:23:01.670 align:start position:0% and network attached storage another image<21:22:59.640> there<21:22:59.936> it<21:23:00.784> decouples<21:23:01.256> the<21:23:01.504> storage 21:23:01.670 --> 21:23:01.680 align:start position:0% image there it decouples the storage 21:23:01.680 --> 21:23:03.590 align:start position:0% image there it decouples the storage from<21:23:02.160> the<21:23:02.336> servers<21:23:02.760> so<21:23:03.000> the<21:23:03.120> servers<21:23:03.480> are 21:23:03.590 --> 21:23:03.600 align:start position:0% from the servers so the servers are 21:23:03.600 --> 21:23:06.526 align:start position:0% from the servers so the servers are still<21:23:03.784> there<21:23:04.016> but<21:23:04.744> we<21:23:05.640> um<21:23:05.640> remove<21:23:05.936> the<21:23:06.296> storage 21:23:06.526 --> 21:23:06.536 align:start position:0% still there but we um remove the storage 21:23:06.536 --> 21:23:10.846 align:start position:0% still there but we um remove the storage as<21:23:07.016> another<21:23:07.696> feature<21:23:08.696> makes<21:23:09.600> the<21:23:09.832> storage<21:23:10.016> a 21:23:10.846 --> 21:23:10.856 align:start position:0% as another feature makes the storage a 21:23:10.856 --> 21:23:13.966 align:start position:0% as another feature makes the storage a centralized<21:23:11.400> pool<21:23:11.576> of<21:23:11.872> shed<21:23:12.680> devices<21:23:13.680> that 21:23:13.966 --> 21:23:13.976 align:start position:0% centralized pool of shed devices that 21:23:13.976 --> 21:23:15.470 align:start position:0% centralized pool of shed devices that can<21:23:14.160> be<21:23:14.216> accessed<21:23:14.576> by<21:23:14.760> all<21:23:15.000> the<21:23:15.120> servers 21:23:15.470 --> 21:23:15.480 align:start position:0% can be accessed by all the servers 21:23:15.480 --> 21:23:18.774 align:start position:0% can be accessed by all the servers connected<21:23:15.832> to<21:23:16.016> the<21:23:16.192> network 21:23:18.774 --> 21:23:18.784 align:start position:0% 21:23:18.784 --> 21:23:20.454 align:start position:0% now<21:23:19.144> network<21:23:19.376> attached<21:23:19.800> storage<21:23:19.920> is<21:23:20.216> not<21:23:20.336> a 21:23:20.454 --> 21:23:20.464 align:start position:0% now network attached storage is not a 21:23:20.464 --> 21:23:22.006 align:start position:0% now network attached storage is not a network<21:23:20.640> in<21:23:20.936> its<21:23:21.240> own<21:23:21.296> right<21:23:21.424> but<21:23:21.656> a<21:23:21.832> storage 21:23:22.006 --> 21:23:22.016 align:start position:0% network in its own right but a storage 21:23:22.016 --> 21:23:26.454 align:start position:0% network in its own right but a storage array<21:23:22.552> hooked<21:23:23.400> up<21:23:23.464> to<21:23:23.640> an<21:23:23.824> existing<21:23:24.176> Network 21:23:26.454 --> 21:23:26.464 align:start position:0% array hooked up to an existing Network 21:23:26.464 --> 21:23:29.150 align:start position:0% array hooked up to an existing Network here's<21:23:27.056> an<21:23:27.120> example<21:23:27.360> of<21:23:27.656> a<21:23:27.896> Nas<21:23:28.256> server 21:23:29.150 --> 21:23:29.160 align:start position:0% here's an example of a Nas server 21:23:29.160 --> 21:23:31.790 align:start position:0% here's an example of a Nas server that's<21:23:29.760> a<21:23:30.000> Netgear<21:23:30.360> by<21:23:30.424> looks<21:23:30.784> of<21:23:30.832> it<21:23:31.016> it<21:23:31.616> can 21:23:31.790 --> 21:23:31.800 align:start position:0% that's a Netgear by looks of it it can 21:23:31.800 --> 21:23:33.166 align:start position:0% that's a Netgear by looks of it it can provide<21:23:32.104> centralized 21:23:33.166 --> 21:23:33.176 align:start position:0% provide centralized 21:23:33.176 --> 21:23:34.966 align:start position:0% provide centralized um<21:23:33.240> shared<21:23:33.960> stories<21:23:34.256> of<21:23:34.376> terabytes<21:23:34.856> of 21:23:34.966 --> 21:23:34.976 align:start position:0% um shared stories of terabytes of 21:23:34.976 --> 21:23:37.606 align:start position:0% um shared stories of terabytes of storage<21:23:35.160> you<21:23:35.872> get<21:23:36.056> enough<21:23:36.600> servers<21:23:37.080> for<21:23:37.320> home 21:23:37.606 --> 21:23:37.616 align:start position:0% storage you get enough servers for home 21:23:37.616 --> 21:23:39.526 align:start position:0% storage you get enough servers for home users<21:23:38.104> as<21:23:38.336> well<21:23:38.464> wherever<21:23:38.872> everyone<21:23:39.176> can 21:23:39.526 --> 21:23:39.536 align:start position:0% users as well wherever everyone can 21:23:39.536 --> 21:23:42.350 align:start position:0% users as well wherever everyone can connect<21:23:39.720> to<21:23:40.496> this<21:23:40.744> particular<21:23:41.040> device<21:23:41.400> and 21:23:42.350 --> 21:23:42.360 align:start position:0% connect to this particular device and 21:23:42.360 --> 21:23:44.566 align:start position:0% connect to this particular device and hopefully<21:23:42.656> that<21:23:43.016> device<21:23:43.144> then<21:23:43.616> in<21:23:43.920> turn<21:23:44.104> backs 21:23:44.566 --> 21:23:44.576 align:start position:0% hopefully that device then in turn backs 21:23:44.576 --> 21:23:46.910 align:start position:0% hopefully that device then in turn backs up<21:23:44.696> somewhere<21:23:45.240> over<21:23:45.784> to<21:23:46.080> the<21:23:46.256> cloud<21:23:46.440> or 21:23:46.910 --> 21:23:46.920 align:start position:0% up somewhere over to the cloud or 21:23:46.920 --> 21:23:49.910 align:start position:0% up somewhere over to the cloud or somewhere<21:23:47.512> like<21:23:47.696> that<21:23:48.144> disadvantage<21:23:49.144> is 21:23:49.910 --> 21:23:49.920 align:start position:0% somewhere like that disadvantage is 21:23:49.920 --> 21:23:52.006 align:start position:0% somewhere like that disadvantage is doesn't<21:23:50.336> provide<21:23:50.696> the<21:23:50.824> high<21:23:50.936> speed<21:23:51.296> data 21:23:52.006 --> 21:23:52.016 align:start position:0% doesn't provide the high speed data 21:23:52.016 --> 21:23:53.390 align:start position:0% doesn't provide the high speed data protection<21:23:52.320> needed<21:23:53.040> in<21:23:53.160> Enterprise 21:23:53.390 --> 21:23:53.400 align:start position:0% protection needed in Enterprise 21:23:53.400 --> 21:23:55.734 align:start position:0% protection needed in Enterprise environments<21:23:54.240> because<21:23:54.720> it<21:23:54.960> typically<21:23:55.320> sits 21:23:55.734 --> 21:23:55.744 align:start position:0% environments because it typically sits 21:23:55.744 --> 21:23:59.862 align:start position:0% environments because it typically sits on<21:23:55.856> an<21:23:56.104> existing<21:23:56.640> shed<21:23:57.000> corporate<21:23:57.960> Network 21:23:59.862 --> 21:23:59.872 align:start position:0% on an existing shed corporate Network 21:23:59.872 --> 21:24:02.390 align:start position:0% on an existing shed corporate Network um<21:23:59.936> complete<21:24:00.360> data<21:24:00.784> backup<21:24:01.616> takes<21:24:01.976> a<21:24:02.160> lot<21:24:02.280> of 21:24:02.390 --> 21:24:02.400 align:start position:0% um complete data backup takes a lot of 21:24:02.400 --> 21:24:04.070 align:start position:0% um complete data backup takes a lot of time<21:24:02.576> and<21:24:03.176> obviously<21:24:03.480> takes<21:24:03.656> up<21:24:03.784> a<21:24:03.896> lot<21:24:03.960> of 21:24:04.070 --> 21:24:04.080 align:start position:0% time and obviously takes up a lot of 21:24:04.080 --> 21:24:06.182 align:start position:0% time and obviously takes up a lot of bandwidth 21:24:06.182 --> 21:24:06.192 align:start position:0% bandwidth 21:24:06.192 --> 21:24:08.814 align:start position:0% bandwidth so<21:24:07.192> sun<21:24:07.504> is<21:24:07.800> a<21:24:07.920> dedicated<21:24:08.280> Network<21:24:08.464> that 21:24:08.814 --> 21:24:08.824 align:start position:0% so sun is a dedicated Network that 21:24:08.824 --> 21:24:10.542 align:start position:0% so sun is a dedicated Network that transfers<21:24:09.120> blocks<21:24:09.600> of<21:24:09.656> data<21:24:09.960> at<21:24:10.144> a<21:24:10.256> high<21:24:10.376> speed 21:24:10.542 --> 21:24:10.552 align:start position:0% transfers blocks of data at a high speed 21:24:10.552 --> 21:24:12.950 align:start position:0% transfers blocks of data at a high speed to<21:24:10.920> a<21:24:11.280> storage<21:24:11.512> device 21:24:12.950 --> 21:24:12.960 align:start position:0% to a storage device 21:24:12.960 --> 21:24:15.350 align:start position:0% to a storage device a<21:24:13.376> low<21:24:13.616> latency<21:24:14.104> for<21:24:14.464> the<21:24:14.640> input<21:24:14.936> output 21:24:15.350 --> 21:24:15.360 align:start position:0% a low latency for the input output 21:24:15.360 --> 21:24:21.166 align:start position:0% a low latency for the input output request<21:24:15.784> to<21:24:16.440> the<21:24:16.616> storage<21:24:17.104> device 21:24:21.166 --> 21:24:21.176 align:start position:0% 21:24:21.176 --> 21:24:23.750 align:start position:0% uh<21:24:21.720> what<21:24:22.080> you<21:24:22.256> what<21:24:22.920> sound<21:24:23.104> gives<21:24:23.400> you<21:24:23.512> is 21:24:23.750 --> 21:24:23.760 align:start position:0% uh what you what sound gives you is 21:24:23.760 --> 21:24:26.206 align:start position:0% uh what you what sound gives you is access<21:24:23.936> to<21:24:24.360> several<21:24:24.720> servers<21:24:25.256> that<21:24:25.920> connect 21:24:26.206 --> 21:24:26.216 align:start position:0% access to several servers that connect 21:24:26.216 --> 21:24:28.606 align:start position:0% access to several servers that connect to<21:24:26.464> several<21:24:26.936> several<21:24:27.424> storage<21:24:27.656> devices<21:24:28.256> you 21:24:28.606 --> 21:24:28.616 align:start position:0% to several several storage devices you 21:24:28.616 --> 21:24:30.710 align:start position:0% to several several storage devices you can<21:24:28.744> see<21:24:28.800> we've<21:24:29.040> got<21:24:29.216> a<21:24:29.640> in<21:24:30.360> this<21:24:30.480> instance 21:24:30.710 --> 21:24:30.720 align:start position:0% can see we've got a in this instance 21:24:30.720 --> 21:24:32.862 align:start position:0% can see we've got a in this instance we've<21:24:31.080> got<21:24:31.192> a<21:24:31.320> full<21:24:31.504> mesh<21:24:31.976> connection<21:24:32.464> between 21:24:32.862 --> 21:24:32.872 align:start position:0% we've got a full mesh connection between 21:24:32.872 --> 21:24:35.030 align:start position:0% we've got a full mesh connection between the<21:24:33.240> servers<21:24:33.656> the<21:24:33.960> switches<21:24:34.440> and<21:24:34.680> the<21:24:34.856> storage 21:24:35.030 --> 21:24:35.040 align:start position:0% the servers the switches and the storage 21:24:35.040 --> 21:24:38.030 align:start position:0% the servers the switches and the storage array<21:24:35.640> there 21:24:38.030 --> 21:24:38.040 align:start position:0% 21:24:38.040 --> 21:24:40.134 align:start position:0% also<21:24:38.760> allows<21:24:39.000> the<21:24:39.120> storage<21:24:39.296> devices<21:24:39.784> to 21:24:40.134 --> 21:24:40.144 align:start position:0% also allows the storage devices to 21:24:40.144 --> 21:24:43.910 align:start position:0% also allows the storage devices to communicate<21:24:40.616> with<21:24:40.976> each<21:24:41.104> other 21:24:43.910 --> 21:24:43.920 align:start position:0% 21:24:43.920 --> 21:24:46.182 align:start position:0% limitations<21:24:44.872> going<21:24:45.296> back<21:24:45.480> to<21:24:45.656> direct<21:24:45.896> access 21:24:46.182 --> 21:24:46.192 align:start position:0% limitations going back to direct access 21:24:46.192 --> 21:24:47.926 align:start position:0% limitations going back to direct access storage 21:24:47.926 --> 21:24:47.936 align:start position:0% storage 21:24:47.936 --> 21:24:50.150 align:start position:0% storage this<21:24:48.480> is<21:24:48.656> the<21:24:48.960> challenge<21:24:49.440> we<21:24:49.680> have<21:24:49.856> with<21:24:49.976> the 21:24:50.150 --> 21:24:50.160 align:start position:0% this is the challenge we have with the 21:24:50.160 --> 21:24:53.030 align:start position:0% this is the challenge we have with the traditional<21:24:50.656> server<21:24:51.656> attached<21:24:52.080> storage<21:24:52.256> you 21:24:53.030 --> 21:24:53.040 align:start position:0% traditional server attached storage you 21:24:53.040 --> 21:24:54.822 align:start position:0% traditional server attached storage you can't<21:24:53.160> satisfy<21:24:53.576> the<21:24:53.760> ever<21:24:53.872> crease<21:24:54.296> in<21:24:54.424> demands 21:24:54.822 --> 21:24:54.832 align:start position:0% can't satisfy the ever crease in demands 21:24:54.832 --> 21:24:57.230 align:start position:0% can't satisfy the ever crease in demands for<21:24:54.960> storage<21:24:55.144> and<21:24:55.504> we<21:24:55.680> obviously<21:24:55.976> have<21:24:56.696> more 21:24:57.230 --> 21:24:57.240 align:start position:0% for storage and we obviously have more 21:24:57.240 --> 21:24:58.750 align:start position:0% for storage and we obviously have more and<21:24:57.296> more<21:24:57.536> complex<21:24:57.832> information 21:24:58.750 --> 21:24:58.760 align:start position:0% and more complex information 21:24:58.760 --> 21:25:02.750 align:start position:0% and more complex information including<21:24:59.760> video<21:25:00.056> and<21:25:00.360> voice 21:25:02.750 --> 21:25:02.760 align:start position:0% 21:25:02.760 --> 21:25:04.790 align:start position:0% not<21:25:03.176> scalable<21:25:03.600> due<21:25:03.832> to<21:25:03.960> the<21:25:04.080> restrictions<21:25:04.552> and 21:25:04.790 --> 21:25:04.800 align:start position:0% not scalable due to the restrictions and 21:25:04.800 --> 21:25:07.246 align:start position:0% not scalable due to the restrictions and how<21:25:05.104> many<21:25:05.216> devices<21:25:06.000> you<21:25:06.360> can<21:25:06.536> add<21:25:06.784> physically 21:25:07.246 --> 21:25:07.256 align:start position:0% how many devices you can add physically 21:25:07.256 --> 21:25:08.390 align:start position:0% how many devices you can add physically to 21:25:08.390 --> 21:25:08.400 align:start position:0% to 21:25:08.400 --> 21:25:11.454 align:start position:0% to um servers<21:25:09.056> sun<21:25:09.832> is<21:25:10.144> scalable<21:25:10.552> so<21:25:11.216> you<21:25:11.336> can 21:25:11.454 --> 21:25:11.464 align:start position:0% um servers sun is scalable so you can 21:25:11.464 --> 21:25:13.494 align:start position:0% um servers sun is scalable so you can add<21:25:11.576> a<21:25:11.760> lot<21:25:11.824> of<21:25:11.936> new<21:25:12.056> devices<21:25:12.360> and<21:25:12.832> and<21:25:13.016> without 21:25:13.494 --> 21:25:13.504 align:start position:0% add a lot of new devices and and without 21:25:13.504 --> 21:25:15.710 align:start position:0% add a lot of new devices and and without having<21:25:13.800> to<21:25:13.920> add<21:25:14.160> new<21:25:14.512> servers 21:25:15.710 --> 21:25:15.720 align:start position:0% having to add new servers 21:25:15.720 --> 21:25:19.006 align:start position:0% having to add new servers you<21:25:16.256> can<21:25:16.440> aggregate<21:25:16.976> the<21:25:17.640> devices<21:25:18.240> into<21:25:18.784> a 21:25:19.006 --> 21:25:19.016 align:start position:0% you can aggregate the devices into a 21:25:19.016 --> 21:25:21.110 align:start position:0% you can aggregate the devices into a central<21:25:19.144> pool<21:25:19.440> that<21:25:20.216> can<21:25:20.336> be<21:25:20.464> accessed<21:25:20.824> by<21:25:20.936> the 21:25:21.110 --> 21:25:21.120 align:start position:0% central pool that can be accessed by the 21:25:21.120 --> 21:25:25.134 align:start position:0% central pool that can be accessed by the servers 21:25:25.134 --> 21:25:25.144 align:start position:0% 21:25:25.144 --> 21:25:27.046 align:start position:0% the<21:25:25.744> server<21:25:26.104> attached<21:25:26.464> storage<21:25:26.640> doesn't 21:25:27.046 --> 21:25:27.056 align:start position:0% the server attached storage doesn't 21:25:27.056 --> 21:25:29.206 align:start position:0% the server attached storage doesn't provide<21:25:27.480> High<21:25:27.784> availability<21:25:28.376> because<21:25:28.800> if<21:25:28.976> a 21:25:29.206 --> 21:25:29.216 align:start position:0% provide High availability because if a 21:25:29.216 --> 21:25:30.950 align:start position:0% provide High availability because if a server<21:25:29.464> goes<21:25:29.696> down<21:25:29.824> then<21:25:30.056> you<21:25:30.176> lose<21:25:30.360> the<21:25:30.600> data 21:25:30.950 --> 21:25:30.960 align:start position:0% server goes down then you lose the data 21:25:30.960 --> 21:25:34.790 align:start position:0% server goes down then you lose the data since<21:25:31.504> the<21:25:31.744> data<21:25:32.040> is<21:25:32.160> tied<21:25:32.400> to<21:25:32.576> the<21:25:32.760> server 21:25:34.790 --> 21:25:34.800 align:start position:0% since the data is tied to the server 21:25:34.800 --> 21:25:36.286 align:start position:0% since the data is tied to the server so<21:25:34.976> obviously 21:25:36.286 --> 21:25:36.296 align:start position:0% so obviously 21:25:36.296 --> 21:25:38.390 align:start position:0% so obviously um overcomes<21:25:36.896> this<21:25:37.016> problem<21:25:37.256> because<21:25:37.800> you 21:25:38.390 --> 21:25:38.400 align:start position:0% um overcomes this problem because you 21:25:38.400 --> 21:25:42.414 align:start position:0% um overcomes this problem because you remove<21:25:39.000> the<21:25:39.784> storage<21:25:40.552> from<21:25:40.976> the<21:25:41.160> servers<21:25:41.576> if<21:25:42.240> a 21:25:42.414 --> 21:25:42.424 align:start position:0% remove the storage from the servers if a 21:25:42.424 --> 21:25:46.006 align:start position:0% remove the storage from the servers if a server<21:25:42.720> goes<21:25:43.080> down<21:25:43.256> in<21:25:43.856> the<21:25:44.240> topology<21:25:45.240> then 21:25:46.006 --> 21:25:46.016 align:start position:0% server goes down in the topology then 21:25:46.016 --> 21:25:48.286 align:start position:0% server goes down in the topology then the<21:25:46.256> data<21:25:46.552> is<21:25:46.680> still<21:25:46.856> accessible<21:25:47.336> so<21:25:48.056> you've 21:25:48.286 --> 21:25:48.296 align:start position:0% the data is still accessible so you've 21:25:48.296 --> 21:25:50.814 align:start position:0% the data is still accessible so you've removed<21:25:48.600> that<21:25:48.720> as<21:25:48.896> a<21:25:49.080> point<21:25:49.256> of<21:25:49.504> failure 21:25:50.814 --> 21:25:50.824 align:start position:0% removed that as a point of failure 21:25:50.824 --> 21:25:53.454 align:start position:0% removed that as a point of failure and<21:25:51.480> though<21:25:51.784> the<21:25:51.960> sun<21:25:52.192> connects<21:25:52.800> multitude<21:25:53.280> of 21:25:53.454 --> 21:25:53.464 align:start position:0% and though the sun connects multitude of 21:25:53.464 --> 21:25:55.070 align:start position:0% and though the sun connects multitude of servers<21:25:53.824> and<21:25:53.936> storage<21:25:54.120> devices<21:25:54.600> the 21:25:55.070 --> 21:25:55.080 align:start position:0% servers and storage devices the 21:25:55.080 --> 21:25:57.286 align:start position:0% servers and storage devices the performance<21:25:55.440> doesn't<21:25:55.680> so<21:25:56.040> far<21:25:56.280> because<21:25:57.000> the 21:25:57.286 --> 21:25:57.296 align:start position:0% performance doesn't so far because the 21:25:57.296 --> 21:25:59.326 align:start position:0% performance doesn't so far because the network<21:25:57.480> is<21:25:57.832> characterized<21:25:58.440> by<21:25:58.680> high<21:25:59.040> speed 21:25:59.326 --> 21:25:59.336 align:start position:0% network is characterized by high speed 21:25:59.336 --> 21:26:01.606 align:start position:0% network is characterized by high speed and<21:26:00.120> low<21:26:00.296> latency<21:26:00.720> you've<21:26:01.016> got<21:26:01.144> the<21:26:01.256> best<21:26:01.376> of 21:26:01.606 --> 21:26:01.616 align:start position:0% and low latency you've got the best of 21:26:01.616 --> 21:26:03.414 align:start position:0% and low latency you've got the best of two<21:26:01.856> different<21:26:02.040> worlds<21:26:02.576> there 21:26:03.414 --> 21:26:03.424 align:start position:0% two different worlds there 21:26:03.424 --> 21:26:05.686 align:start position:0% two different worlds there the<21:26:03.896> high<21:26:04.016> speed<21:26:04.256> data<21:26:05.104> transfer<21:26:05.336> the<21:26:05.640> low 21:26:05.686 --> 21:26:05.696 align:start position:0% the high speed data transfer the low 21:26:05.696 --> 21:26:08.390 align:start position:0% the high speed data transfer the low latency<21:26:06.440> can<21:26:07.440> be<21:26:07.552> compared<21:26:07.856> to<21:26:07.920> the<21:26:08.160> high 21:26:08.390 --> 21:26:08.400 align:start position:0% latency can be compared to the high 21:26:08.400 --> 21:26:10.966 align:start position:0% latency can be compared to the high performance<21:26:08.872> of<21:26:09.176> storage<21:26:09.616> directly<21:26:10.616> attached 21:26:10.966 --> 21:26:10.976 align:start position:0% performance of storage directly attached 21:26:10.976 --> 21:26:14.814 align:start position:0% performance of storage directly attached to<21:26:11.040> a<21:26:11.280> server 21:26:14.814 --> 21:26:14.824 align:start position:0% 21:26:14.824 --> 21:26:16.734 align:start position:0% so<21:26:15.176> your<21:26:15.360> storage<21:26:15.536> area<21:26:15.784> network<21:26:16.192> is<21:26:16.552> a 21:26:16.734 --> 21:26:16.744 align:start position:0% so your storage area network is a 21:26:16.744 --> 21:26:18.774 align:start position:0% so your storage area network is a dedicated<21:26:17.104> Network<21:26:17.464> it's<21:26:18.000> scalable<21:26:18.480> and 21:26:18.774 --> 21:26:18.784 align:start position:0% dedicated Network it's scalable and 21:26:18.784 --> 21:26:20.326 align:start position:0% dedicated Network it's scalable and highly<21:26:19.080> available<21:26:19.320> as<21:26:19.744> we've<21:26:19.976> already<21:26:20.040> said 21:26:20.326 --> 21:26:20.336 align:start position:0% highly available as we've already said 21:26:20.336 --> 21:26:22.910 align:start position:0% highly available as we've already said primary<21:26:21.120> purpose<21:26:21.480> is<21:26:21.720> providing<21:26:22.440> the<21:26:22.744> high 21:26:22.910 --> 21:26:22.920 align:start position:0% primary purpose is providing the high 21:26:22.920 --> 21:26:23.862 align:start position:0% primary purpose is providing the high speed 21:26:23.862 --> 21:26:23.872 align:start position:0% speed 21:26:23.872 --> 21:26:26.326 align:start position:0% speed and<21:26:24.360> the<21:26:24.536> low<21:26:24.656> latency 21:26:26.326 --> 21:26:26.336 align:start position:0% and the low latency 21:26:26.336 --> 21:26:29.502 align:start position:0% and the low latency Sun<21:26:27.120> media<21:26:27.656> it's<21:26:28.616> the<21:26:28.800> actual<21:26:28.976> cables<21:26:29.400> and 21:26:29.502 --> 21:26:29.512 align:start position:0% Sun media it's the actual cables and 21:26:29.512 --> 21:26:30.886 align:start position:0% Sun media it's the actual cables and physical<21:26:29.696> wiring 21:26:30.886 --> 21:26:30.896 align:start position:0% physical wiring 21:26:30.896 --> 21:26:33.350 align:start position:0% physical wiring It's<21:26:31.504> associated<21:26:31.920> with<21:26:32.216> the<21:26:32.400> unique<21:26:32.640> protocol 21:26:33.350 --> 21:26:33.360 align:start position:0% It's associated with the unique protocol 21:26:33.360 --> 21:26:35.990 align:start position:0% It's associated with the unique protocol and<21:26:33.720> is<21:26:33.832> always<21:26:34.016> managed<21:26:34.376> by<21:26:34.552> that<21:26:34.744> protocol 21:26:35.990 --> 21:26:36.000 align:start position:0% and is always managed by that protocol 21:26:36.000 --> 21:26:37.910 align:start position:0% and is always managed by that protocol the<21:26:36.424> protocol<21:26:36.720> is<21:26:37.080> responsible<21:26:37.504> for<21:26:37.744> the 21:26:37.910 --> 21:26:37.920 align:start position:0% the protocol is responsible for the 21:26:37.920 --> 21:26:40.070 align:start position:0% the protocol is responsible for the format<21:26:38.336> and<21:26:38.464> sequence<21:26:38.760> of<21:26:38.936> data<21:26:39.360> exchange<21:26:39.720> on 21:26:40.070 --> 21:26:40.080 align:start position:0% format and sequence of data exchange on 21:26:40.080 --> 21:26:42.590 align:start position:0% format and sequence of data exchange on the<21:26:40.256> storage<21:26:40.496> area<21:26:40.856> network<21:26:41.360> now<21:26:42.360> you're 21:26:42.590 --> 21:26:42.600 align:start position:0% the storage area network now you're 21:26:42.600 --> 21:26:44.454 align:start position:0% the storage area network now you're almost<21:26:42.832> always<21:26:43.144> going<21:26:43.376> to<21:26:43.504> have 21:26:44.454 --> 21:26:44.464 align:start position:0% almost always going to have 21:26:44.464 --> 21:26:46.310 align:start position:0% almost always going to have um<21:26:44.512> fiber<21:26:45.120> channel 21:26:46.310 --> 21:26:46.320 align:start position:0% um fiber channel 21:26:46.320 --> 21:26:50.206 align:start position:0% um fiber channel and<21:26:46.800> because<21:26:47.040> of<21:26:47.280> the<21:26:47.464> speed<21:26:47.696> requirements 21:26:50.206 --> 21:26:50.216 align:start position:0% and because of the speed requirements 21:26:50.216 --> 21:26:52.366 align:start position:0% and because of the speed requirements different<21:26:50.936> types<21:26:51.360> of<21:26:51.480> optical<21:26:51.832> electrical 21:26:52.366 --> 21:26:52.376 align:start position:0% different types of optical electrical 21:26:52.376 --> 21:26:54.470 align:start position:0% different types of optical electrical transmission<21:26:52.680> meter<21:26:53.336> that<21:26:53.936> you<21:26:54.176> cannot 21:26:54.470 --> 21:26:54.480 align:start position:0% transmission meter that you cannot 21:26:54.480 --> 21:26:56.862 align:start position:0% transmission meter that you cannot follow<21:26:54.720> that<21:26:55.016> and<21:26:55.504> you<21:26:55.744> can<21:26:55.856> have<21:26:55.976> copper<21:26:56.464> the 21:26:56.862 --> 21:26:56.872 align:start position:0% follow that and you can have copper the 21:26:56.872 --> 21:26:59.502 align:start position:0% follow that and you can have copper the fibers<21:26:57.240> of<21:26:57.424> preferred<21:26:57.832> connection<21:26:58.192> type 21:26:59.502 --> 21:26:59.512 align:start position:0% fibers of preferred connection type 21:26:59.512 --> 21:27:01.494 align:start position:0% fibers of preferred connection type uh<21:27:00.000> the<21:27:00.176> sounds<21:27:00.296> are<21:27:00.536> typically<21:27:00.784> typically 21:27:01.494 --> 21:27:01.504 align:start position:0% uh the sounds are typically typically 21:27:01.504 --> 21:27:04.542 align:start position:0% uh the sounds are typically typically built<21:27:01.856> using<21:27:02.104> fiber<21:27:02.512> channel 21:27:04.542 --> 21:27:04.552 align:start position:0% built using fiber channel 21:27:04.552 --> 21:27:06.950 align:start position:0% built using fiber channel uh<21:27:05.464> the<21:27:05.760> standards<21:27:06.056> you<21:27:06.176> define<21:27:06.296> a<21:27:06.536> high-speed 21:27:06.950 --> 21:27:06.960 align:start position:0% uh the standards you define a high-speed 21:27:06.960 --> 21:27:09.110 align:start position:0% uh the standards you define a high-speed Network<21:27:07.144> that<21:27:07.856> transfer<21:27:08.464> dates<21:27:08.760> at<21:27:08.936> around 21:27:09.110 --> 21:27:09.120 align:start position:0% Network that transfer dates at around 21:27:09.120 --> 21:27:11.750 align:start position:0% Network that transfer dates at around two<21:27:09.480> gigs<21:27:09.896> per<21:27:10.192> second 21:27:11.750 --> 21:27:11.760 align:start position:0% two gigs per second 21:27:11.760 --> 21:27:13.494 align:start position:0% two gigs per second the<21:27:12.120> standards<21:27:12.600> also<21:27:12.784> define<21:27:12.960> the<21:27:13.256> properties 21:27:13.494 --> 21:27:13.504 align:start position:0% the standards also define the properties 21:27:13.504 --> 21:27:15.710 align:start position:0% the standards also define the properties of<21:27:13.744> the<21:27:13.856> media<21:27:14.160> and<21:27:14.336> how<21:27:14.464> data<21:27:14.936> is<21:27:15.120> transmitted 21:27:15.710 --> 21:27:15.720 align:start position:0% of the media and how data is transmitted 21:27:15.720 --> 21:27:18.230 align:start position:0% of the media and how data is transmitted which<21:27:16.320> I<21:27:16.496> mentioned<21:27:16.856> earlier 21:27:18.230 --> 21:27:18.240 align:start position:0% which I mentioned earlier 21:27:18.240 --> 21:27:22.542 align:start position:0% which I mentioned earlier fiber<21:27:18.720> channel<21:27:18.896> is<21:27:19.080> a<21:27:19.192> de<21:27:19.320> facto<21:27:19.744> standard 21:27:22.542 --> 21:27:22.552 align:start position:0% 21:27:22.552 --> 21:27:26.094 align:start position:0% the<21:27:23.400> storage<21:27:23.696> area<21:27:24.000> network<21:27:24.424> using<21:27:25.376> is<21:27:25.800> built 21:27:26.094 --> 21:27:26.104 align:start position:0% the storage area network using is built 21:27:26.104 --> 21:27:28.134 align:start position:0% the storage area network using is built using<21:27:26.336> fiber<21:27:26.760> channel<21:27:27.056> technology<21:27:27.600> is<21:27:27.896> called 21:27:28.134 --> 21:27:28.144 align:start position:0% using fiber channel technology is called 21:27:28.144 --> 21:27:33.646 align:start position:0% using fiber channel technology is called the<21:27:28.320> fiber<21:27:28.680> channel<21:27:28.856> or<21:27:29.576> FC<21:27:30.176> San 21:27:33.646 --> 21:27:33.656 align:start position:0% 21:27:33.656 --> 21:27:36.286 align:start position:0% uh<21:27:34.320> the<21:27:34.552> whole<21:27:34.680> idea<21:27:34.976> is<21:27:35.160> to<21:27:35.400> increase<21:27:35.576> access 21:27:36.286 --> 21:27:36.296 align:start position:0% uh the whole idea is to increase access 21:27:36.296 --> 21:27:39.110 align:start position:0% uh the whole idea is to increase access to<21:27:36.656> all<21:27:36.784> the<21:27:36.960> data<21:27:37.320> and<21:27:38.160> since<21:27:38.336> organizations 21:27:39.110 --> 21:27:39.120 align:start position:0% to all the data and since organizations 21:27:39.120 --> 21:27:41.150 align:start position:0% to all the data and since organizations have<21:27:39.480> a<21:27:39.720> heterogeneous<21:27:40.320> combination<21:27:40.920> of 21:27:41.150 --> 21:27:41.160 align:start position:0% have a heterogeneous combination of 21:27:41.160 --> 21:27:44.686 align:start position:0% have a heterogeneous combination of operating<21:27:41.760> systems<21:27:42.376> fiber<21:27:43.376> channel<21:27:43.552> was 21:27:44.686 --> 21:27:44.696 align:start position:0% operating systems fiber channel was 21:27:44.696 --> 21:27:46.606 align:start position:0% operating systems fiber channel was um designed<21:27:45.296> to<21:27:45.360> cater<21:27:46.016> for<21:27:46.144> all<21:27:46.320> of<21:27:46.440> these 21:27:46.606 --> 21:27:46.616 align:start position:0% um designed to cater for all of these 21:27:46.616 --> 21:27:48.286 align:start position:0% um designed to cater for all of these different<21:27:46.800> applications<21:27:47.464> and<21:27:47.872> operating 21:27:48.286 --> 21:27:48.296 align:start position:0% different applications and operating 21:27:48.296 --> 21:27:51.414 align:start position:0% different applications and operating systems 21:27:51.414 --> 21:27:51.424 align:start position:0% 21:27:51.424 --> 21:27:53.926 align:start position:0% the<21:27:51.896> fiber<21:27:52.256> channels<21:27:52.744> solve<21:27:53.464> the<21:27:53.512> fundamental 21:27:53.926 --> 21:27:53.936 align:start position:0% the fiber channels solve the fundamental 21:27:53.936 --> 21:27:56.686 align:start position:0% the fiber channels solve the fundamental problem<21:27:54.176> of<21:27:54.536> reliably<21:27:55.016> making<21:27:55.512> terabytes<21:27:56.512> of 21:27:56.686 --> 21:27:56.696 align:start position:0% problem of reliably making terabytes of 21:27:56.696 --> 21:27:58.366 align:start position:0% problem of reliably making terabytes of information<21:27:56.936> available<21:27:57.480> to<21:27:57.896> hundreds<21:27:58.320> of 21:27:58.366 --> 21:27:58.376 align:start position:0% information available to hundreds of 21:27:58.376 --> 21:28:00.646 align:start position:0% information available to hundreds of servers<21:27:58.856> more<21:27:59.824> than<21:27:59.936> likely<21:28:00.240> at<21:28:00.424> the<21:28:00.536> same 21:28:00.646 --> 21:28:00.656 align:start position:0% servers more than likely at the same 21:28:00.656 --> 21:28:02.454 align:start position:0% servers more than likely at the same time<21:28:00.896> as<21:28:01.192> well<21:28:01.320> so<21:28:01.552> serving<21:28:02.104> multiple 21:28:02.454 --> 21:28:02.464 align:start position:0% time as well so serving multiple 21:28:02.464 --> 21:28:04.926 align:start position:0% time as well so serving multiple requests 21:28:04.926 --> 21:28:04.936 align:start position:0% requests 21:28:04.936 --> 21:28:07.366 align:start position:0% requests uh<21:28:05.936> while<21:28:06.120> direct<21:28:06.360> attached<21:28:06.832> storage<21:28:07.016> and 21:28:07.366 --> 21:28:07.376 align:start position:0% uh while direct attached storage and 21:28:07.376 --> 21:28:08.686 align:start position:0% uh while direct attached storage and network<21:28:07.552> attached<21:28:08.040> storage<21:28:08.216> may<21:28:08.576> be 21:28:08.686 --> 21:28:08.696 align:start position:0% network attached storage may be 21:28:08.696 --> 21:28:10.966 align:start position:0% network attached storage may be appropriate<21:28:09.056> for<21:28:09.240> small<21:28:09.424> networks<21:28:10.016> the<21:28:10.616> fiber 21:28:10.966 --> 21:28:10.976 align:start position:0% appropriate for small networks the fiber 21:28:10.976 --> 21:28:14.326 align:start position:0% appropriate for small networks the fiber channel<21:28:11.240> San<21:28:12.240> is<21:28:12.656> used<21:28:12.896> generally<21:28:13.256> for<21:28:13.744> large 21:28:14.326 --> 21:28:14.336 align:start position:0% channel San is used generally for large 21:28:14.336 --> 21:28:19.846 align:start position:0% channel San is used generally for large storage<21:28:14.696> networks<21:28:15.424> and<21:28:15.600> Enterprise<21:28:15.832> Networks 21:28:19.846 --> 21:28:19.856 align:start position:0% 21:28:19.856 --> 21:28:22.430 align:start position:0% um<21:28:19.976> con<21:28:20.216> the<21:28:20.760> concept<21:28:21.296> of<21:28:21.480> sand<21:28:21.784> isn't<21:28:22.144> tied<21:28:22.320> to 21:28:22.430 --> 21:28:22.440 align:start position:0% um con the concept of sand isn't tied to 21:28:22.440 --> 21:28:25.366 align:start position:0% um con the concept of sand isn't tied to any<21:28:22.680> particular<21:28:23.160> technology<21:28:23.872> or<21:28:24.424> vendor<21:28:24.896> so 21:28:25.366 --> 21:28:25.376 align:start position:0% any particular technology or vendor so 21:28:25.376 --> 21:28:27.710 align:start position:0% any particular technology or vendor so it<21:28:25.552> can<21:28:25.680> be<21:28:25.744> used<21:28:25.856> by<21:28:26.040> a<21:28:26.160> multitude<21:28:26.696> it<21:28:27.600> can 21:28:27.710 --> 21:28:27.720 align:start position:0% it can be used by a multitude it can 21:28:27.720 --> 21:28:29.502 align:start position:0% it can be used by a multitude it can also<21:28:27.896> be<21:28:28.016> built<21:28:28.320> using<21:28:28.616> other<21:28:28.856> Technologies 21:28:29.502 --> 21:28:29.512 align:start position:0% also be built using other Technologies 21:28:29.512 --> 21:28:30.774 align:start position:0% also be built using other Technologies such 21:28:30.774 --> 21:28:30.784 align:start position:0% such 21:28:30.784 --> 21:28:35.110 align:start position:0% such um as<21:28:31.440> Internet<21:28:31.616> Security<21:28:32.160> or<21:28:32.760> iSCSI 21:28:35.110 --> 21:28:35.120 align:start position:0% um as Internet Security or iSCSI 21:28:35.120 --> 21:28:37.734 align:start position:0% um as Internet Security or iSCSI is<21:28:36.120> a<21:28:36.240> storage<21:28:36.360> area<21:28:36.600> network<21:28:36.960> implemented 21:28:37.734 --> 21:28:37.744 align:start position:0% is a storage area network implemented 21:28:37.744 --> 21:28:40.366 align:start position:0% is a storage area network implemented over<21:28:38.040> an<21:28:38.280> IP<21:28:38.576> and<21:28:38.872> it<21:28:39.056> uses<21:28:39.360> the<21:28:39.656> iSCSI 21:28:40.366 --> 21:28:40.376 align:start position:0% over an IP and it uses the iSCSI 21:28:40.376 --> 21:28:43.734 align:start position:0% over an IP and it uses the iSCSI protocol 21:28:43.734 --> 21:28:43.744 align:start position:0% 21:28:43.744 --> 21:28:45.950 align:start position:0% it's<21:28:44.336> a<21:28:44.576> mapping<21:28:44.936> of<21:28:45.120> the<21:28:45.176> scuzzy<21:28:45.656> protocol 21:28:45.950 --> 21:28:45.960 align:start position:0% it's a mapping of the scuzzy protocol 21:28:45.960 --> 21:28:49.366 align:start position:0% it's a mapping of the scuzzy protocol over<21:28:46.552> TCP<21:28:47.824> not<21:28:48.176> sure<21:28:48.360> if<21:28:48.480> there's<21:28:48.600> an<21:28:48.720> RFC<21:28:49.192> for 21:28:49.366 --> 21:28:49.376 align:start position:0% over TCP not sure if there's an RFC for 21:28:49.376 --> 21:28:51.822 align:start position:0% over TCP not sure if there's an RFC for this<21:28:49.552> actually<21:28:49.744> but<21:28:50.104> you<21:28:50.336> can<21:28:50.464> Google<21:28:50.760> the<21:28:51.656> ice 21:28:51.822 --> 21:28:51.832 align:start position:0% this actually but you can Google the ice 21:28:51.832 --> 21:28:54.886 align:start position:0% this actually but you can Google the ice cozy<21:28:52.376> for<21:28:52.496> yourself<21:28:52.760> and<21:28:53.760> see<21:28:54.360> um<21:28:54.360> where<21:28:54.784> the 21:28:54.886 --> 21:28:54.896 align:start position:0% cozy for yourself and see um where the 21:28:54.896 --> 21:28:57.110 align:start position:0% cozy for yourself and see um where the proposal<21:28:55.320> started 21:28:57.110 --> 21:28:57.120 align:start position:0% proposal started 21:28:57.120 --> 21:28:59.454 align:start position:0% proposal started carries<21:28:58.016> Block<21:28:58.192> Level<21:28:58.440> data<21:28:58.856> over<21:28:58.976> the<21:28:59.160> IP 21:28:59.454 --> 21:28:59.464 align:start position:0% carries Block Level data over the IP 21:28:59.464 --> 21:29:01.846 align:start position:0% carries Block Level data over the IP network<21:28:59.696> and<21:29:00.536> block<21:29:00.832> storage<21:29:01.376> can<21:29:01.680> be 21:29:01.846 --> 21:29:01.856 align:start position:0% network and block storage can be 21:29:01.856 --> 21:29:03.774 align:start position:0% network and block storage can be accessed<21:29:02.160> over<21:29:02.336> the<21:29:02.576> network<21:29:02.696> as<21:29:03.360> if<21:29:03.536> it<21:29:03.656> was 21:29:03.774 --> 21:29:03.784 align:start position:0% accessed over the network as if it was 21:29:03.784 --> 21:29:06.670 align:start position:0% accessed over the network as if it was directly<21:29:04.080> attached<21:29:04.440> to<21:29:04.552> the<21:29:04.800> server 21:29:06.670 --> 21:29:06.680 align:start position:0% directly attached to the server 21:29:06.680 --> 21:29:09.110 align:start position:0% directly attached to the server is<21:29:07.680> because<21:29:07.920> the<21:29:08.160> architecture<21:29:08.576> is<21:29:08.696> based<21:29:09.056> on 21:29:09.110 --> 21:29:09.120 align:start position:0% is because the architecture is based on 21:29:09.120 --> 21:29:12.286 align:start position:0% is because the architecture is based on the<21:29:09.240> client<21:29:09.536> server<21:29:09.896> model<21:29:10.144> of<21:29:10.496> scuzzy 21:29:12.286 --> 21:29:12.296 align:start position:0% the client server model of scuzzy 21:29:12.296 --> 21:29:14.814 align:start position:0% the client server model of scuzzy it's<21:29:12.832> because<21:29:13.144> the<21:29:13.376> parlance<21:29:14.160> is<21:29:14.280> referred<21:29:14.760> to 21:29:14.814 --> 21:29:14.824 align:start position:0% it's because the parlance is referred to 21:29:14.824 --> 21:29:17.990 align:start position:0% it's because the parlance is referred to as<21:29:15.176> the<21:29:15.600> initiator<21:29:16.256> target<21:29:16.680> model<21:29:17.104> which<21:29:17.760> may 21:29:17.990 --> 21:29:18.000 align:start position:0% as the initiator target model which may 21:29:18.000 --> 21:29:20.326 align:start position:0% as the initiator target model which may be<21:29:18.120> you<21:29:18.424> may<21:29:18.600> expect<21:29:18.784> a<21:29:19.192> question<21:29:19.336> on 21:29:20.326 --> 21:29:20.336 align:start position:0% be you may expect a question on 21:29:20.336 --> 21:29:22.750 align:start position:0% be you may expect a question on something<21:29:20.512> along<21:29:20.760> those<21:29:21.120> lines<21:29:21.424> for<21:29:21.832> the<21:29:22.144> exam 21:29:22.750 --> 21:29:22.760 align:start position:0% something along those lines for the exam 21:29:22.760 --> 21:29:25.310 align:start position:0% something along those lines for the exam the<21:29:23.760> iscosity<21:29:24.424> sign<21:29:24.600> consists<21:29:24.960> of<21:29:25.080> three 21:29:25.310 --> 21:29:25.320 align:start position:0% the iscosity sign consists of three 21:29:25.320 --> 21:29:27.166 align:start position:0% the iscosity sign consists of three components 21:29:27.166 --> 21:29:27.176 align:start position:0% components 21:29:27.176 --> 21:29:32.750 align:start position:0% components initiator<21:29:28.016> the<21:29:28.920> Target<21:29:29.160> and<21:29:30.000> the<21:29:30.176> IP<21:29:30.424> network 21:29:32.750 --> 21:29:32.760 align:start position:0% 21:29:32.760 --> 21:29:34.486 align:start position:0% the<21:29:33.120> initiators<21:29:33.656> the<21:29:33.832> system<21:29:34.016> that<21:29:34.256> first 21:29:34.486 --> 21:29:34.496 align:start position:0% the initiators the system that first 21:29:34.496 --> 21:29:36.526 align:start position:0% the initiators the system that first initiates<21:29:34.976> a<21:29:35.280> read<21:29:35.400> or<21:29:35.640> write<21:29:35.824> request<21:29:36.176> over 21:29:36.526 --> 21:29:36.536 align:start position:0% initiates a read or write request over 21:29:36.536 --> 21:29:38.630 align:start position:0% initiates a read or write request over the<21:29:36.832> IP<21:29:37.144> network 21:29:38.630 --> 21:29:38.640 align:start position:0% the IP network 21:29:38.640 --> 21:29:42.350 align:start position:0% the IP network example<21:29:39.240> of<21:29:39.360> a<21:29:39.536> device<21:29:39.720> is<21:29:40.016> the<21:29:40.320> server 21:29:42.350 --> 21:29:42.360 align:start position:0% example of a device is the server 21:29:42.360 --> 21:29:44.502 align:start position:0% example of a device is the server Target<21:29:42.960> system<21:29:43.376> is<21:29:43.920> the<21:29:44.104> system<21:29:44.216> that 21:29:44.502 --> 21:29:44.512 align:start position:0% Target system is the system that 21:29:44.512 --> 21:29:46.606 align:start position:0% Target system is the system that responds<21:29:44.936> to<21:29:45.120> the<21:29:45.240> requests 21:29:46.606 --> 21:29:46.616 align:start position:0% responds to the requests 21:29:46.616 --> 21:29:50.926 align:start position:0% responds to the requests so<21:29:47.104> an<21:29:47.336> example<21:29:47.696> is<21:29:48.000> the<21:29:48.296> storage<21:29:48.536> array 21:29:50.926 --> 21:29:50.936 align:start position:0% so an example is the storage array 21:29:50.936 --> 21:29:53.686 align:start position:0% so an example is the storage array initiates<21:29:51.832> initiators<21:29:52.744> and<21:29:52.976> targets<21:29:53.464> need 21:29:53.686 --> 21:29:53.696 align:start position:0% initiates initiators and targets need 21:29:53.696 --> 21:29:56.566 align:start position:0% initiates initiators and targets need the<21:29:53.936> physical<21:29:54.120> is<21:29:54.600> because<21:29:54.832> the<21:29:55.080> interface<21:29:55.576> to 21:29:56.566 --> 21:29:56.576 align:start position:0% the physical is because the interface to 21:29:56.576 --> 21:29:59.502 align:start position:0% the physical is because the interface to connect<21:29:56.760> to<21:29:57.000> the<21:29:57.176> IP<21:29:57.600> network 21:29:59.502 --> 21:29:59.512 align:start position:0% connect to the IP network 21:29:59.512 --> 21:30:01.966 align:start position:0% connect to the IP network the<21:29:59.936> Isis<21:30:00.296> interface<21:30:00.832> is<21:30:00.960> available<21:30:01.192> as<21:30:01.504> a<21:30:01.680> PCI 21:30:01.966 --> 21:30:01.976 align:start position:0% the Isis interface is available as a PCI 21:30:01.976 --> 21:30:03.646 align:start position:0% the Isis interface is available as a PCI expansion<21:30:02.464> card<21:30:02.696> or<21:30:03.000> it<21:30:03.176> can<21:30:03.296> actually<21:30:03.480> be 21:30:03.646 --> 21:30:03.656 align:start position:0% expansion card or it can actually be 21:30:03.656 --> 21:30:05.990 align:start position:0% expansion card or it can actually be built<21:30:04.016> into<21:30:04.144> the<21:30:04.376> motherboard<21:30:04.920> again<21:30:05.696> you 21:30:05.990 --> 21:30:06.000 align:start position:0% built into the motherboard again you 21:30:06.000 --> 21:30:08.150 align:start position:0% built into the motherboard again you need<21:30:06.120> to<21:30:06.176> speak<21:30:06.424> to<21:30:06.600> the<21:30:06.784> vendor<21:30:07.256> and<21:30:07.504> look<21:30:07.976> at 21:30:08.150 --> 21:30:08.160 align:start position:0% need to speak to the vendor and look at 21:30:08.160 --> 21:30:10.310 align:start position:0% need to speak to the vendor and look at your<21:30:08.576> particular<21:30:09.240> specifications<21:30:09.960> and 21:30:10.310 --> 21:30:10.320 align:start position:0% your particular specifications and 21:30:10.320 --> 21:30:11.630 align:start position:0% your particular specifications and requirements 21:30:11.630 --> 21:30:11.640 align:start position:0% requirements 21:30:11.640 --> 21:30:13.966 align:start position:0% requirements jumbo<21:30:12.240> frames<21:30:12.600> you<21:30:12.784> may<21:30:12.896> heard<21:30:13.144> of<21:30:13.320> before<21:30:13.552> in 21:30:13.966 --> 21:30:13.976 align:start position:0% jumbo frames you may heard of before in 21:30:13.976 --> 21:30:16.006 align:start position:0% jumbo frames you may heard of before in network<21:30:14.216> parlance 21:30:16.006 --> 21:30:16.016 align:start position:0% network parlance 21:30:16.016 --> 21:30:18.350 align:start position:0% network parlance it's<21:30:16.616> an<21:30:16.744> Ethernet<21:30:16.976> frame<21:30:17.576> it's<21:30:18.000> got<21:30:18.240> a 21:30:18.350 --> 21:30:18.360 align:start position:0% it's an Ethernet frame it's got a 21:30:18.360 --> 21:30:21.046 align:start position:0% it's an Ethernet frame it's got a payload<21:30:18.656> greater<21:30:19.144> than<21:30:19.256> 1500<21:30:19.856> bytes<21:30:20.336> and<21:30:20.872> it 21:30:21.046 --> 21:30:21.056 align:start position:0% payload greater than 1500 bytes and it 21:30:21.056 --> 21:30:23.030 align:start position:0% payload greater than 1500 bytes and it can<21:30:21.176> carry<21:30:21.480> a<21:30:21.536> payload<21:30:21.960> payload<21:30:22.616> of<21:30:22.744> up<21:30:22.856> to 21:30:23.030 --> 21:30:23.040 align:start position:0% can carry a payload payload of up to 21:30:23.040 --> 21:30:25.246 align:start position:0% can carry a payload payload of up to 9000<21:30:23.576> bytes 21:30:25.246 --> 21:30:25.256 align:start position:0% 9000 bytes 21:30:25.256 --> 21:30:28.006 align:start position:0% 9000 bytes so<21:30:26.216> on<21:30:26.640> the<21:30:26.760> contrary<21:30:27.000> an<21:30:27.240> Ethernet<21:30:27.600> standard 21:30:28.006 --> 21:30:28.016 align:start position:0% so on the contrary an Ethernet standard 21:30:28.016 --> 21:30:29.686 align:start position:0% so on the contrary an Ethernet standard frame<21:30:28.320> a<21:30:28.680> standard<21:30:28.976> ethernet<21:30:29.216> frame<21:30:29.576> sorry 21:30:29.686 --> 21:30:29.696 align:start position:0% frame a standard ethernet frame sorry 21:30:29.696 --> 21:30:32.926 align:start position:0% frame a standard ethernet frame sorry can<21:30:30.000> carry<21:30:30.240> a<21:30:30.424> payload<21:30:30.832> of<21:30:31.144> 1500<21:30:31.744> bytes 21:30:32.926 --> 21:30:32.936 align:start position:0% can carry a payload of 1500 bytes 21:30:32.936 --> 21:30:35.206 align:start position:0% can carry a payload of 1500 bytes the<21:30:33.360> payload<21:30:33.784> or<21:30:34.256> the<21:30:34.376> size<21:30:34.552> of<21:30:34.744> the<21:30:34.920> largest 21:30:35.206 --> 21:30:35.216 align:start position:0% the payload or the size of the largest 21:30:35.216 --> 21:30:37.134 align:start position:0% the payload or the size of the largest data<21:30:35.696> that<21:30:35.824> an<21:30:35.936> Ethernet<21:30:36.120> frame<21:30:36.536> can<21:30:36.720> carry<21:30:36.960> is 21:30:37.134 --> 21:30:37.144 align:start position:0% data that an Ethernet frame can carry is 21:30:37.144 --> 21:30:40.134 align:start position:0% data that an Ethernet frame can carry is referred<21:30:37.552> to<21:30:37.616> as<21:30:37.856> the<21:30:38.216> MTU<21:30:38.872> and<21:30:39.720> if<21:30:39.832> you<21:30:39.960> ever 21:30:40.134 --> 21:30:40.144 align:start position:0% referred to as the MTU and if you ever 21:30:40.144 --> 21:30:42.774 align:start position:0% referred to as the MTU and if you ever use<21:30:40.440> a<21:30:40.616> package<21:30:40.920> sniffer<21:30:41.400> you'll<21:30:41.696> see<21:30:41.936> you 21:30:42.774 --> 21:30:42.784 align:start position:0% use a package sniffer you'll see you 21:30:42.784 --> 21:30:45.110 align:start position:0% use a package sniffer you'll see you should<21:30:42.960> see<21:30:43.080> for<21:30:43.256> ethernet<21:30:43.800> and<21:30:44.160> MTU<21:30:44.936> field 21:30:45.110 --> 21:30:45.120 align:start position:0% should see for ethernet and MTU field 21:30:45.120 --> 21:30:48.166 align:start position:0% should see for ethernet and MTU field the<21:30:45.424> maximum<21:30:45.896> transmission<21:30:46.552> unit 21:30:48.166 --> 21:30:48.176 align:start position:0% the maximum transmission unit 21:30:48.176 --> 21:30:50.566 align:start position:0% the maximum transmission unit since<21:30:48.480> jumbo<21:30:48.960> frames<21:30:49.256> have<21:30:49.440> larger<21:30:49.744> mtus<21:30:50.216> they 21:30:50.566 --> 21:30:50.576 align:start position:0% since jumbo frames have larger mtus they 21:30:50.576 --> 21:30:52.966 align:start position:0% since jumbo frames have larger mtus they can<21:30:50.760> carry<21:30:51.056> more<21:30:51.240> data 21:30:52.966 --> 21:30:52.976 align:start position:0% can carry more data 21:30:52.976 --> 21:30:54.950 align:start position:0% can carry more data each<21:30:53.464> transmitted<21:30:54.056> frame<21:30:54.360> and<21:30:54.480> a<21:30:54.784> network 21:30:54.950 --> 21:30:54.960 align:start position:0% each transmitted frame and a network 21:30:54.960 --> 21:30:57.350 align:start position:0% each transmitted frame and a network requires<21:30:55.680> a<21:30:55.920> network<21:30:56.160> hardware<21:30:56.512> and<21:30:56.936> software 21:30:57.350 --> 21:30:57.360 align:start position:0% requires a network hardware and software 21:30:57.360 --> 21:30:59.814 align:start position:0% requires a network hardware and software to<21:30:57.536> process<21:30:57.784> it<21:30:58.080> so<21:30:58.744> we<21:30:58.920> have<21:30:59.040> the<21:30:59.280> more<21:30:59.464> frames 21:30:59.814 --> 21:30:59.824 align:start position:0% to process it so we have the more frames 21:30:59.824 --> 21:31:02.390 align:start position:0% to process it so we have the more frames we<21:30:59.936> have<21:31:00.176> the<21:31:00.720> more<21:31:00.896> CPU<21:31:01.440> Cycles<21:31:01.856> are<21:31:02.104> required 21:31:02.390 --> 21:31:02.400 align:start position:0% we have the more CPU Cycles are required 21:31:02.400 --> 21:31:04.366 align:start position:0% we have the more CPU Cycles are required to<21:31:02.512> process<21:31:02.824> them 21:31:04.366 --> 21:31:04.376 align:start position:0% to process them 21:31:04.376 --> 21:31:06.950 align:start position:0% to process them so<21:31:04.920> if<21:31:05.040> we<21:31:05.216> use<21:31:05.400> jumbo<21:31:06.000> frames<21:31:06.424> it<21:31:06.832> only 21:31:06.950 --> 21:31:06.960 align:start position:0% so if we use jumbo frames it only 21:31:06.960 --> 21:31:09.710 align:start position:0% so if we use jumbo frames it only requires<21:31:07.440> a<21:31:07.616> few<21:31:08.040> we<21:31:08.872> require<21:31:09.000> less<21:31:09.296> frames 21:31:09.710 --> 21:31:09.720 align:start position:0% requires a few we require less frames 21:31:09.720 --> 21:31:12.230 align:start position:0% requires a few we require less frames because<21:31:09.896> of<21:31:10.144> the<21:31:10.320> bigger<21:31:10.552> MTU<21:31:11.160> size<21:31:11.400> as<21:31:12.120> a 21:31:12.230 --> 21:31:12.240 align:start position:0% because of the bigger MTU size as a 21:31:12.240 --> 21:31:15.774 align:start position:0% because of the bigger MTU size as a result<21:31:12.360> we<21:31:12.656> get<21:31:12.832> less<21:31:13.280> CPU<21:31:14.280> utilization<21:31:15.000> but 21:31:15.774 --> 21:31:15.784 align:start position:0% result we get less CPU utilization but 21:31:15.784 --> 21:31:20.030 align:start position:0% result we get less CPU utilization but we<21:31:15.960> get<21:31:16.080> the<21:31:16.192> bonus<21:31:16.552> of<21:31:16.744> increased<21:31:17.336> throughput 21:31:20.030 --> 21:31:20.040 align:start position:0% we get the bonus of increased throughput 21:31:20.040 --> 21:31:22.310 align:start position:0% we get the bonus of increased throughput uh<21:31:20.576> we<21:31:20.696> can<21:31:20.824> use<21:31:20.936> jumbo<21:31:21.360> frames<21:31:21.720> when<21:31:21.896> fiber 21:31:22.310 --> 21:31:22.320 align:start position:0% uh we can use jumbo frames when fiber 21:31:22.320 --> 21:31:24.230 align:start position:0% uh we can use jumbo frames when fiber channel<21:31:22.496> frames<21:31:23.104> are<21:31:23.400> to<21:31:23.512> be<21:31:23.696> transmitted 21:31:24.230 --> 21:31:24.240 align:start position:0% channel frames are to be transmitted 21:31:24.240 --> 21:31:25.966 align:start position:0% channel frames are to be transmitted over<21:31:24.480> the<21:31:24.656> ethernet 21:31:25.966 --> 21:31:25.976 align:start position:0% over the ethernet 21:31:25.976 --> 21:31:28.246 align:start position:0% over the ethernet the<21:31:26.400> size<21:31:26.576> of<21:31:26.872> the<21:31:27.056> fiber<21:31:27.480> channel<21:31:27.656> frames<21:31:28.080> are 21:31:28.246 --> 21:31:28.256 align:start position:0% the size of the fiber channel frames are 21:31:28.256 --> 21:31:30.774 align:start position:0% the size of the fiber channel frames are over<21:31:28.440> 2K<21:31:28.976> so<21:31:29.512> it<21:31:29.640> becomes<21:31:29.936> necessary<21:31:30.360> through 21:31:30.774 --> 21:31:30.784 align:start position:0% over 2K so it becomes necessary through 21:31:30.784 --> 21:31:33.414 align:start position:0% over 2K so it becomes necessary through the<21:31:31.552> adapters<21:31:31.920> and<21:31:32.104> switches<21:31:32.576> to<21:31:33.296> support 21:31:33.414 --> 21:31:33.424 align:start position:0% the adapters and switches to support 21:31:33.424 --> 21:31:36.286 align:start position:0% the adapters and switches to support baby<21:31:33.784> jumbo<21:31:34.320> frames<21:31:34.744> in<21:31:35.464> order<21:31:35.576> to<21:31:35.760> prevent 21:31:36.286 --> 21:31:36.296 align:start position:0% baby jumbo frames in order to prevent 21:31:36.296 --> 21:31:38.454 align:start position:0% baby jumbo frames in order to prevent the<21:31:36.536> segmentation<21:31:37.144> I<21:31:37.856> think<21:31:37.976> we<21:31:38.160> covered 21:31:38.454 --> 21:31:38.464 align:start position:0% the segmentation I think we covered 21:31:38.464 --> 21:31:40.366 align:start position:0% the segmentation I think we covered segmentation<21:31:39.000> early<21:31:39.296> it's<21:31:39.600> when<21:31:39.784> the<21:31:40.016> frame 21:31:40.366 --> 21:31:40.376 align:start position:0% segmentation early it's when the frame 21:31:40.376 --> 21:31:42.590 align:start position:0% segmentation early it's when the frame is<21:31:41.160> chopped<21:31:41.512> up<21:31:41.576> into<21:31:41.824> different<21:31:42.120> pieces 21:31:42.590 --> 21:31:42.600 align:start position:0% is chopped up into different pieces 21:31:42.600 --> 21:31:45.590 align:start position:0% is chopped up into different pieces numbered<21:31:43.256> and<21:31:43.856> then<21:31:43.976> transmitted<21:31:44.760> and<21:31:45.360> each 21:31:45.590 --> 21:31:45.600 align:start position:0% numbered and then transmitted and each 21:31:45.600 --> 21:31:47.326 align:start position:0% numbered and then transmitted and each frame<21:31:46.016> has<21:31:46.616> to 21:31:47.326 --> 21:31:47.336 align:start position:0% frame has to 21:31:47.336 --> 21:31:49.246 align:start position:0% frame has to um<21:31:47.400> has<21:31:47.760> to<21:31:47.872> have<21:31:48.000> an<21:31:48.120> acknowledgments<21:31:48.896> so 21:31:49.246 --> 21:31:49.256 align:start position:0% um has to have an acknowledgments so 21:31:49.256 --> 21:31:53.030 align:start position:0% um has to have an acknowledgments so you've<21:31:49.504> got<21:31:49.552> a<21:31:50.160> lot<21:31:50.216> of<21:31:50.336> overhead<21:31:50.760> associated 21:31:53.030 --> 21:31:53.040 align:start position:0% you've got a lot of overhead associated 21:31:53.040 --> 21:31:54.886 align:start position:0% you've got a lot of overhead associated all<21:31:53.576> right<21:31:53.696> so<21:31:53.872> we've<21:31:54.056> looked<21:31:54.360> in<21:31:54.424> brief<21:31:54.720> at 21:31:54.886 --> 21:31:54.896 align:start position:0% all right so we've looked in brief at 21:31:54.896 --> 21:31:57.046 align:start position:0% all right so we've looked in brief at storage<21:31:55.144> area<21:31:55.440> networks<21:31:56.160> direct<21:31:56.464> attached 21:31:57.046 --> 21:31:57.056 align:start position:0% storage area networks direct attached 21:31:57.056 --> 21:31:58.966 align:start position:0% storage area networks direct attached storage<21:31:57.296> Nas 21:31:58.966 --> 21:31:58.976 align:start position:0% storage Nas 21:31:58.976 --> 21:32:02.926 align:start position:0% storage Nas uh<21:31:59.696> Sun<21:31:59.936> versus<21:32:00.240> Das<21:32:00.832> Sun<21:32:01.616> media 21:32:02.926 --> 21:32:02.936 align:start position:0% uh Sun versus Das Sun media 21:32:02.936 --> 21:32:06.166 align:start position:0% uh Sun versus Das Sun media fiber<21:32:03.600> channel<21:32:03.832> and<21:32:04.192> iscs<21:32:04.872> architecture<21:32:05.872> and 21:32:06.166 --> 21:32:06.176 align:start position:0% fiber channel and iscs architecture and 21:32:06.176 --> 21:32:07.006 align:start position:0% fiber channel and iscs architecture and Sam 21:32:07.006 --> 21:32:07.016 align:start position:0% Sam 21:32:07.016 --> 21:32:09.950 align:start position:0% Sam the<21:32:07.440> components<21:32:07.920> of<21:32:08.104> Isco<21:32:08.640> Z<21:32:08.872> and<21:32:09.536> jumbo 21:32:09.950 --> 21:32:09.960 align:start position:0% the components of Isco Z and jumbo 21:32:09.960 --> 21:32:11.030 align:start position:0% the components of Isco Z and jumbo frames 21:32:11.030 --> 21:32:11.040 align:start position:0% frames 21:32:11.040 --> 21:32:15.460 align:start position:0% frames thanks<21:32:11.400> for<21:32:11.576> watching 21:32:15.460 --> 21:32:15.470 align:start position:0% 21:32:15.470 --> 21:32:31.310 align:start position:0% [Music] 21:32:31.310 --> 21:32:31.320 align:start position:0% 21:32:31.320 --> 21:32:33.886 align:start position:0% welcome<21:32:31.856> to<21:32:32.040> module<21:32:32.464> 17<21:32:32.696> lesson<21:32:33.424> 4<21:32:33.600> Cloud 21:32:33.886 --> 21:32:33.896 align:start position:0% welcome to module 17 lesson 4 Cloud 21:32:33.896 --> 21:32:36.470 align:start position:0% welcome to module 17 lesson 4 Cloud Concepts<21:32:34.680> I've<21:32:35.336> mentioned<21:32:35.696> earlier<21:32:36.000> well 21:32:36.470 --> 21:32:36.480 align:start position:0% Concepts I've mentioned earlier well 21:32:36.480 --> 21:32:39.046 align:start position:0% Concepts I've mentioned earlier well worth<21:32:36.720> doing<21:32:37.144> the<21:32:37.504> CompTIA<21:32:38.040> Cloud<21:32:38.280> Essentials 21:32:39.046 --> 21:32:39.056 align:start position:0% worth doing the CompTIA Cloud Essentials 21:32:39.056 --> 21:32:42.822 align:start position:0% worth doing the CompTIA Cloud Essentials exam<21:32:39.680> because<21:32:40.680> uh<21:32:41.336> cloud<21:32:41.696> computing<21:32:42.424> is<21:32:42.720> just 21:32:42.822 --> 21:32:42.832 align:start position:0% exam because uh cloud computing is just 21:32:42.832 --> 21:32:45.414 align:start position:0% exam because uh cloud computing is just one<21:32:43.080> of<21:32:43.192> the<21:32:43.376> core<21:32:43.936> subjects<21:32:44.936> that<21:32:45.120> you<21:32:45.296> need 21:32:45.414 --> 21:32:45.424 align:start position:0% one of the core subjects that you need 21:32:45.424 --> 21:32:47.470 align:start position:0% one of the core subjects that you need to<21:32:45.536> understand<21:32:45.720> as<21:32:46.192> a<21:32:46.440> network<21:32:46.552> engineer 21:32:47.470 --> 21:32:47.480 align:start position:0% to understand as a network engineer 21:32:47.480 --> 21:32:50.390 align:start position:0% to understand as a network engineer among<21:32:48.480> us<21:32:48.656> a<21:32:48.960> few<21:32:49.080> others<21:32:49.440> including<21:32:49.800> routing 21:32:50.390 --> 21:32:50.400 align:start position:0% among us a few others including routing 21:32:50.400 --> 21:32:53.390 align:start position:0% among us a few others including routing virtualization 21:32:53.390 --> 21:32:53.400 align:start position:0% virtualization 21:32:53.400 --> 21:32:54.286 align:start position:0% virtualization um 21:32:54.286 --> 21:32:54.296 align:start position:0% um 21:32:54.296 --> 21:32:56.710 align:start position:0% um probably<21:32:55.192> Amazon<21:32:55.504> storage 21:32:56.710 --> 21:32:56.720 align:start position:0% probably Amazon storage 21:32:56.720 --> 21:32:59.862 align:start position:0% probably Amazon storage uh<21:32:57.720> routing<21:32:58.144> and<21:32:58.256> switching<21:32:58.744> for<21:32:59.464> example<21:32:59.640> the 21:32:59.862 --> 21:32:59.872 align:start position:0% uh routing and switching for example the 21:32:59.872 --> 21:33:03.774 align:start position:0% uh routing and switching for example the CCNA<21:33:00.536> IPv6 21:33:03.774 --> 21:33:03.784 align:start position:0% 21:33:03.784 --> 21:33:07.494 align:start position:0% so<21:33:04.744> this<21:33:04.976> is<21:33:05.104> just<21:33:05.280> a<21:33:05.512> real<21:33:05.640> uh<21:33:05.936> brief<21:33:06.360> taster 21:33:07.494 --> 21:33:07.504 align:start position:0% so this is just a real uh brief taster 21:33:07.504 --> 21:33:08.926 align:start position:0% so this is just a real uh brief taster looking<21:33:07.920> at<21:33:08.104> cloud<21:33:08.336> computing 21:33:08.926 --> 21:33:08.936 align:start position:0% looking at cloud computing 21:33:08.936 --> 21:33:11.814 align:start position:0% looking at cloud computing characteristics<21:33:10.160> on-demand<21:33:11.160> self-service 21:33:11.814 --> 21:33:11.824 align:start position:0% characteristics on-demand self-service 21:33:11.824 --> 21:33:15.230 align:start position:0% characteristics on-demand self-service broad<21:33:12.296> network<21:33:12.600> access<21:33:13.016> resource<21:33:13.976> pooling 21:33:15.230 --> 21:33:15.240 align:start position:0% broad network access resource pooling 21:33:15.240 --> 21:33:19.070 align:start position:0% broad network access resource pooling elasticity<21:33:16.216> measured<21:33:17.216> service<21:33:17.896> software<21:33:18.896> as 21:33:19.070 --> 21:33:19.080 align:start position:0% elasticity measured service software as 21:33:19.080 --> 21:33:21.542 align:start position:0% elasticity measured service software as a<21:33:19.256> service<21:33:19.504> platform<21:33:20.400> as<21:33:20.696> a<21:33:20.872> service 21:33:21.542 --> 21:33:21.552 align:start position:0% a service platform as a service 21:33:21.552 --> 21:33:23.990 align:start position:0% a service platform as a service infrastructure<21:33:22.552> as<21:33:22.800> a<21:33:22.976> service 21:33:23.990 --> 21:33:24.000 align:start position:0% infrastructure as a service 21:33:24.000 --> 21:33:26.630 align:start position:0% infrastructure as a service and<21:33:24.424> then<21:33:24.600> private<21:33:25.192> community<21:33:25.856> and<21:33:26.400> public 21:33:26.630 --> 21:33:26.640 align:start position:0% and then private community and public 21:33:26.640 --> 21:33:30.230 align:start position:0% and then private community and public clouds<21:33:27.240> on<21:33:27.720> hybrid<21:33:28.144> clouds 21:33:30.230 --> 21:33:30.240 align:start position:0% clouds on hybrid clouds 21:33:30.240 --> 21:33:32.270 align:start position:0% clouds on hybrid clouds so<21:33:30.896> best<21:33:31.256> thing<21:33:31.440> is<21:33:31.552> to<21:33:31.800> start<21:33:31.920> with<21:33:32.104> the 21:33:32.270 --> 21:33:32.280 align:start position:0% so best thing is to start with the 21:33:32.280 --> 21:33:34.790 align:start position:0% so best thing is to start with the definition<21:33:32.536> so<21:33:33.536> we<21:33:33.784> can<21:33:33.960> kind<21:33:34.320> of<21:33:34.376> have<21:33:34.552> an 21:33:34.790 --> 21:33:34.800 align:start position:0% definition so we can kind of have an 21:33:34.800 --> 21:33:36.646 align:start position:0% definition so we can kind of have an agreed<21:33:35.280> kicking<21:33:35.640> off<21:33:35.760> point<21:33:36.000> of<21:33:36.176> what<21:33:36.424> cloud 21:33:36.646 --> 21:33:36.656 align:start position:0% agreed kicking off point of what cloud 21:33:36.656 --> 21:33:39.790 align:start position:0% agreed kicking off point of what cloud computing<21:33:37.320> actually<21:33:37.920> is 21:33:39.790 --> 21:33:39.800 align:start position:0% computing actually is 21:33:39.800 --> 21:33:42.590 align:start position:0% computing actually is now<21:33:40.800> cloud<21:33:41.104> computing<21:33:41.696> from<21:33:42.296> the<21:33:42.424> definition 21:33:42.590 --> 21:33:42.600 align:start position:0% now cloud computing from the definition 21:33:42.600 --> 21:33:45.542 align:start position:0% now cloud computing from the definition is<21:33:43.320> a<21:33:43.440> model<21:33:43.616> for<21:33:44.040> enabling<21:33:44.512> ubiquitous 21:33:45.542 --> 21:33:45.552 align:start position:0% is a model for enabling ubiquitous 21:33:45.552 --> 21:33:48.414 align:start position:0% is a model for enabling ubiquitous convenient<21:33:46.552> on-demand<21:33:47.216> network<21:33:47.464> access<21:33:47.824> to<21:33:48.240> a 21:33:48.414 --> 21:33:48.424 align:start position:0% convenient on-demand network access to a 21:33:48.424 --> 21:33:50.926 align:start position:0% convenient on-demand network access to a shared<21:33:48.784> pool<21:33:49.616> of<21:33:49.856> configurable<21:33:50.400> computing 21:33:50.926 --> 21:33:50.936 align:start position:0% shared pool of configurable computing 21:33:50.936 --> 21:33:53.990 align:start position:0% shared pool of configurable computing resources<21:33:51.680> examples<21:33:52.680> are<21:33:52.856> network<21:33:53.160> servers 21:33:53.990 --> 21:33:54.000 align:start position:0% resources examples are network servers 21:33:54.000 --> 21:33:57.230 align:start position:0% resources examples are network servers storage<21:33:54.680> application<21:33:55.680> and<21:33:55.976> services<21:33:56.336> that 21:33:57.230 --> 21:33:57.240 align:start position:0% storage application and services that 21:33:57.240 --> 21:33:58.846 align:start position:0% storage application and services that can<21:33:57.424> be<21:33:57.536> rapidly<21:33:57.896> provisioned<21:33:58.440> and<21:33:58.552> released 21:33:58.846 --> 21:33:58.856 align:start position:0% can be rapidly provisioned and released 21:33:58.856 --> 21:34:01.246 align:start position:0% can be rapidly provisioned and released with<21:33:59.040> minimal<21:33:59.464> management<21:33:59.640> effort<21:34:00.256> or 21:34:01.246 --> 21:34:01.256 align:start position:0% with minimal management effort or 21:34:01.256 --> 21:34:03.886 align:start position:0% with minimal management effort or service<21:34:01.680> provider<21:34:02.280> interaction<21:34:02.784> we've<21:34:03.784> all 21:34:03.886 --> 21:34:03.896 align:start position:0% service provider interaction we've all 21:34:03.896 --> 21:34:05.566 align:start position:0% service provider interaction we've all used<21:34:04.080> the<21:34:04.256> cloud<21:34:04.440> already<21:34:04.744> if<21:34:05.280> you've<21:34:05.400> used 21:34:05.566 --> 21:34:05.576 align:start position:0% used the cloud already if you've used 21:34:05.576 --> 21:34:08.950 align:start position:0% used the cloud already if you've used any<21:34:05.872> storage<21:34:06.176> for<21:34:06.720> example<21:34:06.960> Dropbox 21:34:08.950 --> 21:34:08.960 align:start position:0% any storage for example Dropbox 21:34:08.960 --> 21:34:12.230 align:start position:0% any storage for example Dropbox box.com<21:34:09.960> I<21:34:10.256> think<21:34:10.376> the<21:34:10.496> call<21:34:10.680> for<21:34:10.920> storage<21:34:11.240> any 21:34:12.230 --> 21:34:12.240 align:start position:0% box.com I think the call for storage any 21:34:12.240 --> 21:34:14.750 align:start position:0% box.com I think the call for storage any Google<21:34:12.600> services<21:34:13.016> for<21:34:13.504> example<21:34:13.800> Gmail<21:34:14.216> or 21:34:14.750 --> 21:34:14.760 align:start position:0% Google services for example Gmail or 21:34:14.760 --> 21:34:17.926 align:start position:0% Google services for example Gmail or Google<21:34:14.936> documents<21:34:16.216> and<21:34:17.216> things<21:34:17.640> like<21:34:17.824> that 21:34:17.926 --> 21:34:17.936 align:start position:0% Google documents and things like that 21:34:17.936 --> 21:34:19.750 align:start position:0% Google documents and things like that there's<21:34:18.240> many<21:34:18.480> many<21:34:18.656> others 21:34:19.750 --> 21:34:19.760 align:start position:0% there's many many others 21:34:19.760 --> 21:34:24.286 align:start position:0% there's many many others and<21:34:20.760> are<21:34:21.056> all<21:34:21.240> based<21:34:21.600> on<21:34:21.656> the<21:34:21.832> cloud 21:34:24.286 --> 21:34:24.296 align:start position:0% 21:34:24.296 --> 21:34:27.414 align:start position:0% so<21:34:24.832> some<21:34:25.080> characteristics<21:34:25.856> that<21:34:26.512> you<21:34:26.760> need<21:34:27.296> to 21:34:27.414 --> 21:34:27.424 align:start position:0% so some characteristics that you need to 21:34:27.424 --> 21:34:28.966 align:start position:0% so some characteristics that you need to remember<21:34:27.536> these<21:34:28.016> so<21:34:28.192> make<21:34:28.440> sure<21:34:28.616> you<21:34:28.744> note 21:34:28.966 --> 21:34:28.976 align:start position:0% remember these so make sure you note 21:34:28.976 --> 21:34:31.606 align:start position:0% remember these so make sure you note them<21:34:29.216> down<21:34:29.480> there's<21:34:30.480> five<21:34:30.896> characteristics 21:34:31.606 --> 21:34:31.616 align:start position:0% them down there's five characteristics 21:34:31.616 --> 21:34:33.950 align:start position:0% them down there's five characteristics of<21:34:31.800> cloud<21:34:32.040> computing<21:34:32.696> on<21:34:33.600> demand 21:34:33.950 --> 21:34:33.960 align:start position:0% of cloud computing on demand 21:34:33.960 --> 21:34:36.822 align:start position:0% of cloud computing on demand self-service<21:34:35.176> broader<21:34:36.176> network<21:34:36.424> access 21:34:36.822 --> 21:34:36.832 align:start position:0% self-service broader network access 21:34:36.832 --> 21:34:38.630 align:start position:0% self-service broader network access we'll<21:34:37.504> go<21:34:37.680> into<21:34:37.800> all<21:34:37.976> of<21:34:38.104> these<21:34:38.280> in<21:34:38.512> more 21:34:38.630 --> 21:34:38.640 align:start position:0% we'll go into all of these in more 21:34:38.640 --> 21:34:42.414 align:start position:0% we'll go into all of these in more detail<21:34:39.144> resource<21:34:40.144> pooling<21:34:40.616> rapid<21:34:41.576> elastis 21:34:42.414 --> 21:34:42.424 align:start position:0% detail resource pooling rapid elastis 21:34:42.424 --> 21:34:44.686 align:start position:0% detail resource pooling rapid elastis elasticity 21:34:44.686 --> 21:34:44.696 align:start position:0% elasticity 21:34:44.696 --> 21:34:46.966 align:start position:0% elasticity a<21:34:45.176> measured<21:34:45.536> service 21:34:46.966 --> 21:34:46.976 align:start position:0% a measured service 21:34:46.976 --> 21:34:49.246 align:start position:0% a measured service so<21:34:47.464> on<21:34:47.640> demand<21:34:48.056> basically<21:34:48.536> means<21:34:48.832> the<21:34:48.960> user 21:34:49.246 --> 21:34:49.256 align:start position:0% so on demand basically means the user 21:34:49.256 --> 21:34:51.886 align:start position:0% so on demand basically means the user can<21:34:49.440> provision<21:34:50.176> resources<21:34:51.176> as<21:34:51.600> and<21:34:51.784> when 21:34:51.886 --> 21:34:51.896 align:start position:0% can provision resources as and when 21:34:51.896 --> 21:34:53.630 align:start position:0% can provision resources as and when they're<21:34:52.080> needed<21:34:52.376> without<21:34:52.680> getting<21:34:53.040> any<21:34:53.336> human 21:34:53.630 --> 21:34:53.640 align:start position:0% they're needed without getting any human 21:34:53.640 --> 21:34:56.502 align:start position:0% they're needed without getting any human assistance<21:34:54.480> so<21:34:55.192> you<21:34:55.504> if<21:34:55.976> you<21:34:56.040> needed<21:34:56.336> more 21:34:56.502 --> 21:34:56.512 align:start position:0% assistance so you if you needed more 21:34:56.512 --> 21:34:58.246 align:start position:0% assistance so you if you needed more memory<21:34:56.872> you<21:34:57.056> wouldn't<21:34:57.176> have<21:34:57.424> to<21:34:57.656> log<21:34:57.832> a<21:34:58.080> ticket 21:34:58.246 --> 21:34:58.256 align:start position:0% memory you wouldn't have to log a ticket 21:34:58.256 --> 21:34:59.926 align:start position:0% memory you wouldn't have to log a ticket and<21:34:59.104> you<21:34:59.280> wouldn't<21:34:59.336> have<21:34:59.576> to<21:34:59.640> have<21:34:59.760> an 21:34:59.926 --> 21:34:59.936 align:start position:0% and you wouldn't have to have an 21:34:59.936 --> 21:35:01.430 align:start position:0% and you wouldn't have to have an engineer<21:35:00.296> somewhere 21:35:01.430 --> 21:35:01.440 align:start position:0% engineer somewhere 21:35:01.440 --> 21:35:03.822 align:start position:0% engineer somewhere turn<21:35:02.040> off<21:35:02.280> the<21:35:02.512> server<21:35:02.872> or<21:35:03.120> whatever<21:35:03.536> the 21:35:03.822 --> 21:35:03.832 align:start position:0% turn off the server or whatever the 21:35:03.832 --> 21:35:05.950 align:start position:0% turn off the server or whatever the device<21:35:04.080> is<21:35:04.320> adds<21:35:04.920> more<21:35:05.040> physical<21:35:05.280> memory 21:35:05.950 --> 21:35:05.960 align:start position:0% device is adds more physical memory 21:35:05.960 --> 21:35:08.814 align:start position:0% device is adds more physical memory reboot<21:35:06.960> it<21:35:07.080> and<21:35:07.192> then<21:35:07.376> answer<21:35:07.552> the<21:35:07.856> ticket<21:35:07.976> as 21:35:08.814 --> 21:35:08.824 align:start position:0% reboot it and then answer the ticket as 21:35:08.824 --> 21:35:10.366 align:start position:0% reboot it and then answer the ticket as you<21:35:08.936> may<21:35:09.056> well<21:35:09.240> have<21:35:09.424> had<21:35:09.600> to<21:35:09.720> do<21:35:09.896> in<21:35:10.080> the<21:35:10.256> not 21:35:10.366 --> 21:35:10.376 align:start position:0% you may well have had to do in the not 21:35:10.376 --> 21:35:13.134 align:start position:0% you may well have had to do in the not too<21:35:10.552> distance<21:35:10.744> past<21:35:11.280> you<21:35:11.936> click<21:35:12.240> a<21:35:12.360> button<21:35:12.720> and 21:35:13.134 --> 21:35:13.144 align:start position:0% too distance past you click a button and 21:35:13.144 --> 21:35:15.046 align:start position:0% too distance past you click a button and more<21:35:13.320> is<21:35:13.552> available 21:35:15.046 --> 21:35:15.056 align:start position:0% more is available 21:35:15.056 --> 21:35:17.686 align:start position:0% more is available we<21:35:15.960> can<21:35:16.192> do<21:35:16.320> when<21:35:16.616> consumers<21:35:17.040> provision<21:35:17.464> the 21:35:17.686 --> 21:35:17.696 align:start position:0% we can do when consumers provision the 21:35:17.696 --> 21:35:19.734 align:start position:0% we can do when consumers provision the resources<21:35:18.240> based<21:35:18.656> on<21:35:18.720> their<21:35:18.896> needs<21:35:19.256> those 21:35:19.734 --> 21:35:19.744 align:start position:0% resources based on their needs those 21:35:19.744 --> 21:35:22.182 align:start position:0% resources based on their needs those resources<21:35:20.280> are<21:35:20.464> automatically<21:35:21.192> allocated 21:35:22.182 --> 21:35:22.192 align:start position:0% resources are automatically allocated 21:35:22.192 --> 21:35:24.350 align:start position:0% resources are automatically allocated from<21:35:22.976> a<21:35:23.160> shared<21:35:23.464> pool 21:35:24.350 --> 21:35:24.360 align:start position:0% from a shared pool 21:35:24.360 --> 21:35:26.390 align:start position:0% from a shared pool and<21:35:24.832> their<21:35:24.960> schedules<21:35:25.376> provided<21:35:26.040> by<21:35:26.216> the 21:35:26.390 --> 21:35:26.400 align:start position:0% and their schedules provided by the 21:35:26.400 --> 21:35:28.310 align:start position:0% and their schedules provided by the cloud<21:35:26.576> service<21:35:26.936> provider 21:35:28.310 --> 21:35:28.320 align:start position:0% cloud service provider 21:35:28.320 --> 21:35:31.430 align:start position:0% cloud service provider broad<21:35:28.800> network<21:35:29.104> access<21:35:29.400> means<21:35:30.056> that<21:35:30.424> when<21:35:31.144> the 21:35:31.430 --> 21:35:31.440 align:start position:0% broad network access means that when the 21:35:31.440 --> 21:35:34.134 align:start position:0% broad network access means that when the consumers<21:35:32.160> have<21:35:32.336> provisioned<21:35:32.936> the<21:35:33.656> resources 21:35:34.134 --> 21:35:34.144 align:start position:0% consumers have provisioned the resources 21:35:34.144 --> 21:35:36.646 align:start position:0% consumers have provisioned the resources they<21:35:34.376> can<21:35:34.552> access<21:35:34.680> these<21:35:35.216> from<21:35:35.640> a<21:35:36.296> number<21:35:36.480> of 21:35:36.646 --> 21:35:36.656 align:start position:0% they can access these from a number of 21:35:36.656 --> 21:35:39.166 align:start position:0% they can access these from a number of devices<21:35:36.960> workstations<21:35:37.744> laptops<21:35:38.512> tablets<21:35:39.056> and 21:35:39.166 --> 21:35:39.176 align:start position:0% devices workstations laptops tablets and 21:35:39.176 --> 21:35:42.590 align:start position:0% devices workstations laptops tablets and mobile<21:35:39.360> devices<21:35:39.784> and<21:35:40.616> mobile<21:35:40.920> phones 21:35:42.590 --> 21:35:42.600 align:start position:0% mobile devices and mobile phones 21:35:42.600 --> 21:35:44.926 align:start position:0% mobile devices and mobile phones resource<21:35:43.504> pooling<21:35:43.920> and<21:35:44.512> the<21:35:44.824> service 21:35:44.926 --> 21:35:44.936 align:start position:0% resource pooling and the service 21:35:44.936 --> 21:35:47.990 align:start position:0% resource pooling and the service providers<21:35:45.656> resources<21:35:46.440> are<21:35:46.976> shared<21:35:47.400> and<21:35:47.824> when 21:35:47.990 --> 21:35:48.000 align:start position:0% providers resources are shared and when 21:35:48.000 --> 21:35:50.326 align:start position:0% providers resources are shared and when the<21:35:48.176> consumers<21:35:48.656> on<21:35:49.320> a<21:35:49.504> multi-tenant<21:35:50.104> Model 21:35:50.326 --> 21:35:50.336 align:start position:0% the consumers on a multi-tenant Model 21:35:50.336 --> 21:35:52.846 align:start position:0% the consumers on a multi-tenant Model where<21:35:51.240> consumers<21:35:51.720> get<21:35:51.896> a<21:35:52.016> dynamic<21:35:52.440> allocation 21:35:52.846 --> 21:35:52.856 align:start position:0% where consumers get a dynamic allocation 21:35:52.856 --> 21:35:55.790 align:start position:0% where consumers get a dynamic allocation resources<21:35:53.576> based<21:35:54.424> upon<21:35:54.600> their<21:35:54.832> needs 21:35:55.790 --> 21:35:55.800 align:start position:0% resources based upon their needs 21:35:55.800 --> 21:35:58.542 align:start position:0% resources based upon their needs so<21:35:56.216> sometimes<21:35:56.832> consumers<21:35:57.832> may<21:35:58.080> need<21:35:58.256> more 21:35:58.542 --> 21:35:58.552 align:start position:0% so sometimes consumers may need more 21:35:58.552 --> 21:36:01.366 align:start position:0% so sometimes consumers may need more Computer<21:35:58.936> Resources<21:35:59.936> and<21:36:00.600> other<21:36:00.784> times<21:36:01.080> they 21:36:01.366 --> 21:36:01.376 align:start position:0% Computer Resources and other times they 21:36:01.376 --> 21:36:04.310 align:start position:0% Computer Resources and other times they need<21:36:01.616> need<21:36:02.336> less<21:36:02.640> so<21:36:03.240> it<21:36:03.360> has<21:36:03.536> to<21:36:03.656> adapt<21:36:04.080> for 21:36:04.310 --> 21:36:04.320 align:start position:0% need need less so it has to adapt for 21:36:04.320 --> 21:36:06.950 align:start position:0% need need less so it has to adapt for this<21:36:04.496> particular<21:36:04.856> requirement<21:36:05.336> it's 21:36:06.950 --> 21:36:06.960 align:start position:0% this particular requirement it's 21:36:06.960 --> 21:36:07.734 align:start position:0% this particular requirement it's um 21:36:07.734 --> 21:36:07.744 align:start position:0% um 21:36:07.744 --> 21:36:12.230 align:start position:0% um resource<21:36:08.640> allocation<21:36:09.176> based<21:36:09.656> upon<21:36:09.896> demand 21:36:12.230 --> 21:36:12.240 align:start position:0% resource allocation based upon demand 21:36:12.240 --> 21:36:14.862 align:start position:0% resource allocation based upon demand rapid<21:36:12.832> elasticity<21:36:13.552> I<21:36:14.280> can't<21:36:14.464> say<21:36:14.640> that<21:36:14.760> word 21:36:14.862 --> 21:36:14.872 align:start position:0% rapid elasticity I can't say that word 21:36:14.872 --> 21:36:16.310 align:start position:0% rapid elasticity I can't say that word elasticity 21:36:16.310 --> 21:36:16.320 align:start position:0% elasticity 21:36:16.320 --> 21:36:17.206 align:start position:0% elasticity foreign 21:36:17.206 --> 21:36:17.216 align:start position:0% foreign 21:36:17.216 --> 21:36:19.846 align:start position:0% foreign now<21:36:17.872> a<21:36:18.056> consumer<21:36:18.480> can<21:36:18.656> be<21:36:18.784> allocated<21:36:19.192> more<21:36:19.552> res 21:36:19.846 --> 21:36:19.856 align:start position:0% now a consumer can be allocated more res 21:36:19.856 --> 21:36:23.326 align:start position:0% now a consumer can be allocated more res me<21:36:20.512> more<21:36:21.000> more<21:36:21.240> resources<21:36:21.832> if<21:36:22.080> needed<21:36:22.496> at<21:36:23.160> the 21:36:23.326 --> 21:36:23.336 align:start position:0% me more more resources if needed at the 21:36:23.336 --> 21:36:25.070 align:start position:0% me more more resources if needed at the same<21:36:23.464> time<21:36:23.640> if<21:36:23.936> for<21:36:24.120> any<21:36:24.296> reason<21:36:24.536> they<21:36:24.896> need 21:36:25.070 --> 21:36:25.080 align:start position:0% same time if for any reason they need 21:36:25.080 --> 21:36:26.990 align:start position:0% same time if for any reason they need less<21:36:25.320> because<21:36:25.744> the<21:36:26.040> more<21:36:26.216> you<21:36:26.400> the<21:36:26.696> more<21:36:26.824> you 21:36:26.990 --> 21:36:27.000 align:start position:0% less because the more you the more you 21:36:27.000 --> 21:36:29.270 align:start position:0% less because the more you the more you need<21:36:27.120> the<21:36:27.296> more<21:36:27.424> you<21:36:27.600> pay<21:36:27.784> obviously<21:36:28.216> if<21:36:29.216> you 21:36:29.270 --> 21:36:29.280 align:start position:0% need the more you pay obviously if you 21:36:29.280 --> 21:36:31.606 align:start position:0% need the more you pay obviously if you need<21:36:29.464> less<21:36:29.696> then<21:36:29.936> they<21:36:30.120> can<21:36:30.296> be<21:36:30.424> downsized<21:36:31.144> to 21:36:31.606 --> 21:36:31.616 align:start position:0% need less then they can be downsized to 21:36:31.616 --> 21:36:34.846 align:start position:0% need less then they can be downsized to provide<21:36:32.280> whatever<21:36:32.784> model<21:36:33.784> you<21:36:34.080> need<21:36:34.256> the 21:36:34.846 --> 21:36:34.856 align:start position:0% provide whatever model you need the 21:36:34.856 --> 21:36:36.590 align:start position:0% provide whatever model you need the resources<21:36:35.336> you<21:36:35.576> need 21:36:36.590 --> 21:36:36.600 align:start position:0% resources you need 21:36:36.600 --> 21:36:38.990 align:start position:0% resources you need so<21:36:37.144> it<21:36:37.256> appears<21:36:37.616> to<21:36:37.744> the<21:36:37.856> consumer<21:36:38.400> that<21:36:38.576> there 21:36:38.990 --> 21:36:39.000 align:start position:0% so it appears to the consumer that there 21:36:39.000 --> 21:36:41.390 align:start position:0% so it appears to the consumer that there there's<21:36:39.240> an<21:36:39.480> actual<21:36:39.976> unlimited<21:36:40.976> amount<21:36:41.280> of 21:36:41.390 --> 21:36:41.400 align:start position:0% there's an actual unlimited amount of 21:36:41.400 --> 21:36:45.430 align:start position:0% there's an actual unlimited amount of resources<21:36:41.760> for<21:36:42.000> them<21:36:42.120> at<21:36:42.296> any<21:36:42.480> given<21:36:42.832> time 21:36:45.430 --> 21:36:45.440 align:start position:0% 21:36:45.440 --> 21:36:47.502 align:start position:0% elasticity<21:36:46.440> provides<21:36:46.920> a<21:36:46.976> lot<21:36:47.104> of<21:36:47.216> savings 21:36:47.502 --> 21:36:47.512 align:start position:0% elasticity provides a lot of savings 21:36:47.512 --> 21:36:49.846 align:start position:0% elasticity provides a lot of savings because<21:36:47.872> it's<21:36:48.056> not<21:36:48.240> possible<21:36:48.720> when<21:36:49.504> you<21:36:49.680> have 21:36:49.846 --> 21:36:49.856 align:start position:0% because it's not possible when you have 21:36:49.856 --> 21:36:51.774 align:start position:0% because it's not possible when you have a<21:36:50.040> traditional<21:36:50.464> data<21:36:50.936> center<21:36:51.056> that<21:36:51.536> you've 21:36:51.774 --> 21:36:51.784 align:start position:0% a traditional data center that you've 21:36:51.784 --> 21:36:54.230 align:start position:0% a traditional data center that you've built<21:36:52.144> and<21:36:52.376> you<21:36:52.552> own<21:36:52.744> you<21:36:53.512> can't<21:36:53.576> grow<21:36:53.824> it<21:36:54.056> and 21:36:54.230 --> 21:36:54.240 align:start position:0% built and you own you can't grow it and 21:36:54.240 --> 21:36:57.414 align:start position:0% built and you own you can't grow it and shrink<21:36:54.480> it<21:36:54.656> as<21:36:54.896> and<21:36:55.016> when<21:36:55.192> needed 21:36:57.414 --> 21:36:57.424 align:start position:0% shrink it as and when needed 21:36:57.424 --> 21:37:00.230 align:start position:0% shrink it as and when needed obviously<21:36:58.256> is<21:36:58.440> measured<21:36:58.920> just<21:36:59.576> like<21:36:59.760> a<21:36:59.936> meter 21:37:00.230 --> 21:37:00.240 align:start position:0% obviously is measured just like a meter 21:37:00.240 --> 21:37:02.862 align:start position:0% obviously is measured just like a meter so<21:37:00.424> you're<21:37:00.656> charged<21:37:01.080> based<21:37:01.376> upon<21:37:01.616> your 21:37:02.862 --> 21:37:02.872 align:start position:0% so you're charged based upon your 21:37:02.872 --> 21:37:04.846 align:start position:0% so you're charged based upon your um<21:37:02.936> a<21:37:03.296> number<21:37:03.424> of<21:37:03.600> things<21:37:03.720> such<21:37:04.080> as 21:37:04.846 --> 21:37:04.856 align:start position:0% um a number of things such as 21:37:04.856 --> 21:37:08.990 align:start position:0% um a number of things such as um<21:37:04.920> memory<21:37:05.760> you<21:37:06.000> need<21:37:06.256> uh<21:37:07.256> storage<21:37:07.616> and<21:37:08.576> uh 21:37:08.990 --> 21:37:09.000 align:start position:0% um memory you need uh storage and uh 21:37:09.000 --> 21:37:13.366 align:start position:0% um memory you need uh storage and uh bandwidth 21:37:13.366 --> 21:37:13.376 align:start position:0% 21:37:13.376 --> 21:37:14.926 align:start position:0% so<21:37:13.800> you<21:37:13.920> get<21:37:14.040> what<21:37:14.160> you<21:37:14.280> pay<21:37:14.400> for<21:37:14.576> which<21:37:14.760> you've 21:37:14.926 --> 21:37:14.936 align:start position:0% so you get what you pay for which you've 21:37:14.936 --> 21:37:18.526 align:start position:0% so you get what you pay for which you've already<21:37:15.056> said<21:37:15.360> is<21:37:16.376> um<21:37:16.400> uh<21:37:17.400> tracked<21:37:17.824> normally 21:37:18.526 --> 21:37:18.536 align:start position:0% already said is um uh tracked normally 21:37:18.536 --> 21:37:20.814 align:start position:0% already said is um uh tracked normally you<21:37:18.832> can<21:37:18.896> log<21:37:19.144> in<21:37:19.376> and<21:37:19.680> you<21:37:19.920> can<21:37:20.040> track<21:37:20.336> your 21:37:20.814 --> 21:37:20.824 align:start position:0% you can log in and you can track your 21:37:20.824 --> 21:37:23.686 align:start position:0% you can log in and you can track your use<21:37:20.936> of<21:37:21.176> resources<21:37:21.720> in<21:37:22.080> real<21:37:22.256> time<21:37:22.552> as<21:37:23.400> well<21:37:23.576> as 21:37:23.686 --> 21:37:23.696 align:start position:0% use of resources in real time as well as 21:37:23.696 --> 21:37:26.390 align:start position:0% use of resources in real time as well as historical<21:37:24.376> data<21:37:25.376> looking<21:37:25.552> at 21:37:26.390 --> 21:37:26.400 align:start position:0% historical data looking at 21:37:26.400 --> 21:37:28.134 align:start position:0% historical data looking at um<21:37:26.464> how<21:37:27.056> much<21:37:27.240> you've<21:37:27.480> used<21:37:27.656> and<21:37:27.960> the 21:37:28.134 --> 21:37:28.144 align:start position:0% um how much you've used and the 21:37:28.144 --> 21:37:31.070 align:start position:0% um how much you've used and the projected<21:37:29.240> requirements<21:37:30.240> based<21:37:30.600> on<21:37:30.720> previous 21:37:31.070 --> 21:37:31.080 align:start position:0% projected requirements based on previous 21:37:31.080 --> 21:37:33.470 align:start position:0% projected requirements based on previous usage<21:37:31.744> and<21:37:32.216> you<21:37:32.336> can<21:37:32.464> see<21:37:32.576> how<21:37:32.872> much<21:37:33.056> you're 21:37:33.470 --> 21:37:33.480 align:start position:0% usage and you can see how much you're 21:37:33.480 --> 21:37:35.750 align:start position:0% usage and you can see how much you're going<21:37:34.016> to<21:37:34.144> have<21:37:34.320> to<21:37:34.440> pay<21:37:34.616> how<21:37:35.280> much<21:37:35.464> you<21:37:35.576> paid 21:37:35.750 --> 21:37:35.760 align:start position:0% going to have to pay how much you paid 21:37:35.760 --> 21:37:37.182 align:start position:0% going to have to pay how much you paid in<21:37:35.936> the<21:37:36.120> past 21:37:37.182 --> 21:37:37.192 align:start position:0% in the past 21:37:37.192 --> 21:37:39.110 align:start position:0% in the past there's<21:37:37.800> three<21:37:38.040> service<21:37:38.216> models<21:37:38.760> you<21:37:38.872> need<21:37:39.000> to 21:37:39.110 --> 21:37:39.120 align:start position:0% there's three service models you need to 21:37:39.120 --> 21:37:41.414 align:start position:0% there's three service models you need to be<21:37:39.240> familiar<21:37:39.600> with<21:37:39.784> software<21:37:40.744> as<21:37:40.920> a<21:37:41.104> service 21:37:41.414 --> 21:37:41.424 align:start position:0% be familiar with software as a service 21:37:41.424 --> 21:37:44.454 align:start position:0% be familiar with software as a service platform<21:37:42.424> as<21:37:42.656> a<21:37:42.832> service<21:37:43.160> infrastructure<21:37:44.160> as 21:37:44.454 --> 21:37:44.464 align:start position:0% platform as a service infrastructure as 21:37:44.464 --> 21:37:46.150 align:start position:0% platform as a service infrastructure as a<21:37:44.640> service 21:37:46.150 --> 21:37:46.160 align:start position:0% a service 21:37:46.160 --> 21:37:48.526 align:start position:0% a service providers<21:37:47.160> provide<21:37:47.512> the<21:37:47.696> services<21:37:47.936> to 21:37:48.526 --> 21:37:48.536 align:start position:0% providers provide the services to 21:37:48.536 --> 21:37:51.230 align:start position:0% providers provide the services to Consumers<21:37:49.144> based<21:37:49.616> on<21:37:49.744> these<21:37:50.160> three<21:37:50.464> service 21:37:51.230 --> 21:37:51.240 align:start position:0% Consumers based on these three service 21:37:51.240 --> 21:37:57.110 align:start position:0% Consumers based on these three service models<21:37:51.896> so<21:37:52.800> SAS<21:37:53.960> swas<21:37:54.960> or<21:37:55.440> SAS 21:37:57.110 --> 21:37:57.120 align:start position:0% models so SAS swas or SAS 21:37:57.120 --> 21:37:59.206 align:start position:0% models so SAS swas or SAS consumers<21:37:57.960> can<21:37:58.192> use<21:37:58.320> the<21:37:58.496> service<21:37:58.680> provider 21:37:59.206 --> 21:37:59.216 align:start position:0% consumers can use the service provider 21:37:59.216 --> 21:38:01.366 align:start position:0% consumers can use the service provider software<21:37:59.576> applications<21:38:00.056> and<21:38:00.536> databases<21:38:01.144> over 21:38:01.366 --> 21:38:01.376 align:start position:0% software applications and databases over 21:38:01.376 --> 21:38:03.350 align:start position:0% software applications and databases over a<21:38:01.680> network<21:38:01.800> without<21:38:02.696> the<21:38:02.936> need<21:38:03.120> to<21:38:03.240> install 21:38:03.350 --> 21:38:03.360 align:start position:0% a network without the need to install 21:38:03.360 --> 21:38:06.710 align:start position:0% a network without the need to install any<21:38:03.720> software<21:38:04.192> except<21:38:05.104> for<21:38:05.336> a<21:38:05.872> web<21:38:06.296> browser 21:38:06.710 --> 21:38:06.720 align:start position:0% any software except for a web browser 21:38:06.720 --> 21:38:08.526 align:start position:0% any software except for a web browser you<21:38:06.832> need<21:38:07.016> to<21:38:07.192> access 21:38:08.526 --> 21:38:08.536 align:start position:0% you need to access 21:38:08.536 --> 21:38:11.326 align:start position:0% you need to access these<21:38:09.536> uh<21:38:09.720> software<21:38:10.080> applications<21:38:10.552> databases 21:38:11.326 --> 21:38:11.336 align:start position:0% these uh software applications databases 21:38:11.336 --> 21:38:13.070 align:start position:0% these uh software applications databases run<21:38:11.576> on<21:38:11.824> the<21:38:11.872> cloud<21:38:12.000> so<21:38:12.240> imagine<21:38:12.480> you're 21:38:13.070 --> 21:38:13.080 align:start position:0% run on the cloud so imagine you're 21:38:13.080 --> 21:38:15.286 align:start position:0% run on the cloud so imagine you're trying<21:38:13.616> to<21:38:13.856> program 21:38:15.286 --> 21:38:15.296 align:start position:0% trying to program 21:38:15.296 --> 21:38:18.230 align:start position:0% trying to program um<21:38:15.360> some<21:38:15.656> application<21:38:16.280> for<21:38:17.280> example<21:38:17.640> or<21:38:18.120> just 21:38:18.230 --> 21:38:18.240 align:start position:0% um some application for example or just 21:38:18.240 --> 21:38:19.846 align:start position:0% um some application for example or just use<21:38:18.360> a<21:38:18.536> huge<21:38:18.720> amount<21:38:18.832> of<21:38:19.080> resources<21:38:19.552> or 21:38:19.846 --> 21:38:19.856 align:start position:0% use a huge amount of resources or 21:38:19.856 --> 21:38:21.822 align:start position:0% use a huge amount of resources or develop<21:38:20.160> a<21:38:20.400> program<21:38:20.576> you<21:38:21.360> can<21:38:21.424> use<21:38:21.600> the 21:38:21.822 --> 21:38:21.832 align:start position:0% develop a program you can use the 21:38:21.832 --> 21:38:23.862 align:start position:0% develop a program you can use the provider's<21:38:22.320> resources<21:38:22.856> and<21:38:23.216> scale<21:38:23.464> it<21:38:23.640> as<21:38:23.760> and 21:38:23.862 --> 21:38:23.872 align:start position:0% provider's resources and scale it as and 21:38:23.872 --> 21:38:25.134 align:start position:0% provider's resources and scale it as and when<21:38:24.000> needed 21:38:25.134 --> 21:38:25.144 align:start position:0% when needed 21:38:25.144 --> 21:38:27.414 align:start position:0% when needed it's<21:38:25.680> provided<21:38:26.160> as<21:38:26.464> a<21:38:26.640> shared<21:38:27.000> Computing 21:38:27.414 --> 21:38:27.424 align:start position:0% it's provided as a shared Computing 21:38:27.424 --> 21:38:29.630 align:start position:0% it's provided as a shared Computing resource<21:38:27.832> to<21:38:28.016> the<21:38:28.192> consumers 21:38:29.630 --> 21:38:29.640 align:start position:0% resource to the consumers 21:38:29.640 --> 21:38:31.366 align:start position:0% resource to the consumers it's<21:38:29.936> essentially<21:38:30.424> the<21:38:30.536> aggregation<21:38:31.080> of 21:38:31.366 --> 21:38:31.376 align:start position:0% it's essentially the aggregation of 21:38:31.376 --> 21:38:32.990 align:start position:0% it's essentially the aggregation of hardware<21:38:31.616> and<21:38:31.976> software 21:38:32.990 --> 21:38:33.000 align:start position:0% hardware and software 21:38:33.000 --> 21:38:36.230 align:start position:0% hardware and software used<21:38:33.656> to<21:38:33.832> support<21:38:33.960> the<21:38:34.256> cloud<21:38:34.440> services<21:38:35.056> a<21:38:36.056> few 21:38:36.230 --> 21:38:36.240 align:start position:0% used to support the cloud services a few 21:38:36.240 --> 21:38:37.846 align:start position:0% used to support the cloud services a few examples<21:38:36.600> you<21:38:36.896> can<21:38:37.016> see<21:38:37.144> there<21:38:37.376> are<21:38:37.616> Twitter 21:38:37.846 --> 21:38:37.856 align:start position:0% examples you can see there are Twitter 21:38:37.856 --> 21:38:39.350 align:start position:0% examples you can see there are Twitter and<21:38:38.160> Facebook<21:38:38.336> there's<21:38:38.824> a<21:38:39.000> whole<21:38:39.056> bunch<21:38:39.240> of 21:38:39.350 --> 21:38:39.360 align:start position:0% and Facebook there's a whole bunch of 21:38:39.360 --> 21:38:41.454 align:start position:0% and Facebook there's a whole bunch of others<21:38:39.720> you<21:38:39.896> can<21:38:40.016> look<21:38:40.552> into<21:38:40.744> if<21:38:41.104> you<21:38:41.216> wish 21:38:41.454 --> 21:38:41.464 align:start position:0% others you can look into if you wish 21:38:41.464 --> 21:38:45.286 align:start position:0% others you can look into if you wish though<21:38:41.832> in<21:38:42.832> the<21:38:43.016> SAS<21:38:43.376> model<21:38:44.056> consumers<21:38:45.056> access 21:38:45.286 --> 21:38:45.296 align:start position:0% though in the SAS model consumers access 21:38:45.296 --> 21:38:47.030 align:start position:0% though in the SAS model consumers access the<21:38:45.600> shared<21:38:45.896> applications<21:38:46.320> over<21:38:46.616> a<21:38:46.920> network 21:38:47.030 --> 21:38:47.040 align:start position:0% the shared applications over a network 21:38:47.040 --> 21:38:50.390 align:start position:0% the shared applications over a network from<21:38:47.512> various<21:38:48.000> client<21:38:48.784> devices 21:38:50.390 --> 21:38:50.400 align:start position:0% from various client devices 21:38:50.400 --> 21:38:52.182 align:start position:0% from various client devices it<21:38:50.872> doesn't<21:38:51.000> give<21:38:51.240> you<21:38:51.360> the<21:38:51.600> ability<21:38:51.832> to 21:38:52.182 --> 21:38:52.192 align:start position:0% it doesn't give you the ability to 21:38:52.192 --> 21:38:53.926 align:start position:0% it doesn't give you the ability to control<21:38:52.376> and<21:38:52.744> manage<21:38:53.040> in<21:38:53.160> the<21:38:53.336> manage<21:38:53.760> the 21:38:53.926 --> 21:38:53.936 align:start position:0% control and manage in the manage the 21:38:53.936 --> 21:38:56.630 align:start position:0% control and manage in the manage the underlying<21:38:54.600> Cloud<21:38:54.832> infrastructure<21:38:55.616> so<21:38:56.512> you 21:38:56.630 --> 21:38:56.640 align:start position:0% underlying Cloud infrastructure so you 21:38:56.640 --> 21:38:57.886 align:start position:0% underlying Cloud infrastructure so you can't<21:38:56.760> manage<21:38:57.056> the<21:38:57.240> operating<21:38:57.536> system 21:38:57.886 --> 21:38:57.896 align:start position:0% can't manage the operating system 21:38:57.896 --> 21:39:01.846 align:start position:0% can't manage the operating system servers<21:38:58.856> the<21:38:59.760> network<21:38:59.936> or<21:39:00.296> storage<21:39:00.616> and<21:39:01.616> you 21:39:01.846 --> 21:39:01.856 align:start position:0% servers the network or storage and you 21:39:01.856 --> 21:39:03.230 align:start position:0% servers the network or storage and you don't<21:39:01.976> you<21:39:02.216> don't<21:39:02.280> want<21:39:02.400> to<21:39:02.512> anywhere<21:39:02.936> you 21:39:03.230 --> 21:39:03.240 align:start position:0% don't you don't want to anywhere you 21:39:03.240 --> 21:39:08.094 align:start position:0% don't you don't want to anywhere you just<21:39:03.424> want<21:39:03.896> to<21:39:04.256> um<21:39:04.256> use<21:39:04.856> it<21:39:04.976> as<21:39:05.160> is 21:39:08.094 --> 21:39:08.104 align:start position:0% 21:39:08.104 --> 21:39:10.070 align:start position:0% platform<21:39:08.640> as<21:39:08.872> a<21:39:09.056> service<21:39:09.240> there's<21:39:09.600> an<21:39:09.784> example 21:39:10.070 --> 21:39:10.080 align:start position:0% platform as a service there's an example 21:39:10.080 --> 21:39:11.862 align:start position:0% platform as a service there's an example there<21:39:10.320> Windows<21:39:10.856> Azure<21:39:11.216> which<21:39:11.512> you<21:39:11.640> could<21:39:11.760> look 21:39:11.862 --> 21:39:11.872 align:start position:0% there Windows Azure which you could look 21:39:11.872 --> 21:39:14.630 align:start position:0% there Windows Azure which you could look into<21:39:12.056> in<21:39:12.360> your<21:39:12.536> own<21:39:12.656> time<21:39:12.976> in<21:39:13.976> the<21:39:14.160> platform<21:39:14.400> as 21:39:14.630 --> 21:39:14.640 align:start position:0% into in your own time in the platform as 21:39:14.640 --> 21:39:16.606 align:start position:0% into in your own time in the platform as a<21:39:14.824> service<21:39:14.936> model<21:39:15.320> consumers<21:39:16.320> have<21:39:16.496> the 21:39:16.606 --> 21:39:16.616 align:start position:0% a service model consumers have the 21:39:16.616 --> 21:39:18.414 align:start position:0% a service model consumers have the ability<21:39:16.856> to<21:39:17.280> develop<21:39:17.512> and<21:39:17.696> deploy<21:39:18.000> software 21:39:18.414 --> 21:39:18.424 align:start position:0% ability to develop and deploy software 21:39:18.424 --> 21:39:20.862 align:start position:0% ability to develop and deploy software applications<21:39:18.896> on<21:39:19.856> the<21:39:20.040> service<21:39:20.280> providers 21:39:20.862 --> 21:39:20.872 align:start position:0% applications on the service providers 21:39:20.872 --> 21:39:23.030 align:start position:0% applications on the service providers Cloud<21:39:21.120> infrastructure 21:39:23.030 --> 21:39:23.040 align:start position:0% Cloud infrastructure 21:39:23.040 --> 21:39:24.822 align:start position:0% Cloud infrastructure uh<21:39:23.760> the<21:39:23.872> service<21:39:24.056> provider<21:39:24.536> typically 21:39:24.822 --> 21:39:24.832 align:start position:0% uh the service provider typically 21:39:24.832 --> 21:39:27.470 align:start position:0% uh the service provider typically provides<21:39:25.504> a<21:39:25.680> competing<21:39:26.160> platform<21:39:26.640> comprised 21:39:27.470 --> 21:39:27.480 align:start position:0% provides a competing platform comprised 21:39:27.480 --> 21:39:29.270 align:start position:0% provides a competing platform comprised of<21:39:27.536> the<21:39:27.656> operating<21:39:27.960> system<21:39:28.256> and<21:39:29.104> the 21:39:29.270 --> 21:39:29.280 align:start position:0% of the operating system and the 21:39:29.280 --> 21:39:31.734 align:start position:0% of the operating system and the application<21:39:29.696> development<21:39:30.296> environment 21:39:31.734 --> 21:39:31.744 align:start position:0% application development environment 21:39:31.744 --> 21:39:33.414 align:start position:0% application development environment this<21:39:32.216> includes<21:39:32.576> programming<21:39:33.056> languages 21:39:33.414 --> 21:39:33.424 align:start position:0% this includes programming languages 21:39:33.424 --> 21:39:35.454 align:start position:0% this includes programming languages libraries<21:39:34.080> tools<21:39:34.440> databases<21:39:35.104> and<21:39:35.280> web 21:39:35.454 --> 21:39:35.464 align:start position:0% libraries tools databases and web 21:39:35.464 --> 21:39:37.494 align:start position:0% libraries tools databases and web servers<21:39:35.936> I<21:39:36.424> recommend<21:39:36.720> you<21:39:36.896> look<21:39:37.080> at<21:39:37.192> the 21:39:37.494 --> 21:39:37.504 align:start position:0% servers I recommend you look at the 21:39:37.504 --> 21:39:38.414 align:start position:0% servers I recommend you look at the Amazon 21:39:38.414 --> 21:39:38.424 align:start position:0% Amazon 21:39:38.424 --> 21:39:41.030 align:start position:0% Amazon AWS<21:39:39.424> qualifications<21:39:40.144> for<21:39:40.616> more<21:39:40.800> information 21:39:41.030 --> 21:39:41.040 align:start position:0% AWS qualifications for more information 21:39:41.040 --> 21:39:42.526 align:start position:0% AWS qualifications for more information on<21:39:41.512> these 21:39:42.526 --> 21:39:42.536 align:start position:0% on these 21:39:42.536 --> 21:39:45.470 align:start position:0% on these in<21:39:43.016> the<21:39:43.192> paas<21:39:43.976> model 21:39:45.470 --> 21:39:45.480 align:start position:0% in the paas model 21:39:45.480 --> 21:39:47.270 align:start position:0% in the paas model consumers<21:39:46.320> can<21:39:46.496> develop<21:39:46.744> and<21:39:46.920> deploy 21:39:47.270 --> 21:39:47.280 align:start position:0% consumers can develop and deploy 21:39:47.280 --> 21:39:48.646 align:start position:0% consumers can develop and deploy software<21:39:47.576> without<21:39:47.824> the<21:39:48.056> need<21:39:48.240> to<21:39:48.360> maintain 21:39:48.646 --> 21:39:48.656 align:start position:0% software without the need to maintain 21:39:48.656 --> 21:39:50.150 align:start position:0% software without the need to maintain the<21:39:48.784> operating<21:39:49.080> system<21:39:49.320> so<21:39:49.856> you<21:39:49.976> can<21:39:50.040> imagine 21:39:50.150 --> 21:39:50.160 align:start position:0% the operating system so you can imagine 21:39:50.160 --> 21:39:52.734 align:start position:0% the operating system so you can imagine how<21:39:50.512> convenient<21:39:50.936> this<21:39:51.176> is<21:39:51.296> to<21:39:51.480> fire<21:39:51.656> up<21:39:51.896> an 21:39:52.734 --> 21:39:52.744 align:start position:0% how convenient this is to fire up an 21:39:52.744 --> 21:39:54.414 align:start position:0% how convenient this is to fire up an instance<21:39:53.160> for<21:39:53.512> example<21:39:53.696> if<21:39:53.872> you<21:39:54.056> logged<21:39:54.296> into 21:39:54.414 --> 21:39:54.424 align:start position:0% instance for example if you logged into 21:39:54.424 --> 21:39:57.414 align:start position:0% instance for example if you logged into the<21:39:54.832> Amazon<21:39:54.960> or<21:39:55.376> the<21:39:55.504> Google<21:39:55.680> cloud<21:39:56.240> and<21:39:57.240> start 21:39:57.414 --> 21:39:57.424 align:start position:0% the Amazon or the Google cloud and start 21:39:57.424 --> 21:39:59.814 align:start position:0% the Amazon or the Google cloud and start doing<21:39:57.720> your<21:39:57.960> developing<21:39:58.496> it's<21:39:59.280> just<21:39:59.464> so<21:39:59.640> easy 21:39:59.814 --> 21:39:59.824 align:start position:0% doing your developing it's just so easy 21:39:59.824 --> 21:40:01.134 align:start position:0% doing your developing it's just so easy and<21:40:00.120> quick 21:40:01.134 --> 21:40:01.144 align:start position:0% and quick 21:40:01.144 --> 21:40:04.246 align:start position:0% and quick consumers<21:40:02.104> have<21:40:02.280> control<21:40:02.512> over<21:40:03.000> the<21:40:03.536> deployed 21:40:04.246 --> 21:40:04.256 align:start position:0% consumers have control over the deployed 21:40:04.256 --> 21:40:05.926 align:start position:0% consumers have control over the deployed software<21:40:04.616> application<21:40:05.104> and<21:40:05.824> the 21:40:05.926 --> 21:40:05.936 align:start position:0% software application and the 21:40:05.936 --> 21:40:08.150 align:start position:0% software application and the configuration<21:40:06.480> settings 21:40:08.150 --> 21:40:08.160 align:start position:0% configuration settings 21:40:08.160 --> 21:40:11.110 align:start position:0% configuration settings and<21:40:08.576> it<21:40:08.640> doesn't<21:40:08.824> give<21:40:09.056> you<21:40:09.176> to<21:40:09.832> again 21:40:11.110 --> 21:40:11.120 align:start position:0% and it doesn't give you to again 21:40:11.120 --> 21:40:14.270 align:start position:0% and it doesn't give you to again manage<21:40:12.120> the<21:40:12.896> controller<21:40:13.376> manager<21:40:13.800> underlying 21:40:14.270 --> 21:40:14.280 align:start position:0% manage the controller manager underlying 21:40:14.280 --> 21:40:17.030 align:start position:0% manage the controller manager underlying infrastructure 21:40:17.030 --> 21:40:17.040 align:start position:0% 21:40:17.040 --> 21:40:19.310 align:start position:0% infrastructure<21:40:17.760> as<21:40:18.000> a<21:40:18.176> service<21:40:18.360> one<21:40:18.960> example 21:40:19.310 --> 21:40:19.320 align:start position:0% infrastructure as a service one example 21:40:19.320 --> 21:40:23.926 align:start position:0% infrastructure as a service one example is<21:40:19.504> Amazon<21:40:19.800> ec2<21:40:20.640> web<21:40:21.000> services 21:40:23.926 --> 21:40:23.936 align:start position:0% 21:40:23.936 --> 21:40:26.326 align:start position:0% here<21:40:24.480> consumers<21:40:25.016> access<21:40:25.256> a<21:40:25.616> dedicated 21:40:26.326 --> 21:40:26.336 align:start position:0% here consumers access a dedicated 21:40:26.336 --> 21:40:28.966 align:start position:0% here consumers access a dedicated physical<21:40:26.760> or<21:40:27.720> in<21:40:27.896> most<21:40:28.080> cases<21:40:28.440> a<21:40:28.744> virtual 21:40:28.966 --> 21:40:28.976 align:start position:0% physical or in most cases a virtual 21:40:28.976 --> 21:40:31.366 align:start position:0% physical or in most cases a virtual machine<21:40:29.216> running<21:40:29.576> on<21:40:30.000> the<21:40:30.240> service<21:40:30.720> providers 21:40:31.366 --> 21:40:31.376 align:start position:0% machine running on the service providers 21:40:31.376 --> 21:40:33.822 align:start position:0% machine running on the service providers Cloud<21:40:31.616> infrastructure 21:40:33.822 --> 21:40:33.832 align:start position:0% Cloud infrastructure 21:40:33.832 --> 21:40:37.734 align:start position:0% Cloud infrastructure a<21:40:34.440> lot<21:40:34.616> of<21:40:34.744> people<21:40:34.856> use<21:40:35.104> this<21:40:35.336> for<21:40:35.576> web<21:40:35.824> hosting 21:40:37.734 --> 21:40:37.744 align:start position:0% a lot of people use this for web hosting 21:40:37.744 --> 21:40:39.590 align:start position:0% a lot of people use this for web hosting especially<21:40:38.400> WordPress<21:40:38.872> is<21:40:39.056> quite<21:40:39.240> easy<21:40:39.424> to 21:40:39.590 --> 21:40:39.600 align:start position:0% especially WordPress is quite easy to 21:40:39.600 --> 21:40:40.966 align:start position:0% especially WordPress is quite easy to fire<21:40:39.720> up<21:40:39.960> an<21:40:40.080> instance<21:40:40.376> and<21:40:40.616> get<21:40:40.744> it<21:40:40.856> all 21:40:40.966 --> 21:40:40.976 align:start position:0% fire up an instance and get it all 21:40:40.976 --> 21:40:41.990 align:start position:0% fire up an instance and get it all working 21:40:41.990 --> 21:40:42.000 align:start position:0% working 21:40:42.000 --> 21:40:43.910 align:start position:0% working virtual<21:40:42.656> machine<21:40:42.832> typically<21:40:43.256> comes<21:40:43.552> with<21:40:43.744> a 21:40:43.910 --> 21:40:43.920 align:start position:0% virtual machine typically comes with a 21:40:43.920 --> 21:40:46.246 align:start position:0% virtual machine typically comes with a server<21:40:44.280> operating<21:40:44.640> system<21:40:45.256> consumers 21:40:46.246 --> 21:40:46.256 align:start position:0% server operating system consumers 21:40:46.256 --> 21:40:48.414 align:start position:0% server operating system consumers complete<21:40:46.920> complete<21:40:47.464> control<21:40:47.576> over<21:40:47.872> the<21:40:48.120> OS 21:40:48.414 --> 21:40:48.424 align:start position:0% complete complete control over the OS 21:40:48.424 --> 21:40:53.206 align:start position:0% complete complete control over the OS and<21:40:48.656> can<21:40:48.960> control<21:40:49.192> the<21:40:49.552> updates 21:40:53.206 --> 21:40:53.216 align:start position:0% 21:40:53.216 --> 21:40:55.366 align:start position:0% um<21:40:53.336> you<21:40:54.120> have<21:40:54.480> control<21:40:54.656> over<21:40:54.960> the<21:40:55.144> operating 21:40:55.366 --> 21:40:55.376 align:start position:0% um you have control over the operating 21:40:55.376 --> 21:40:57.950 align:start position:0% um you have control over the operating system<21:40:55.680> application<21:40:56.464> storage<21:40:56.936> you<21:40:57.784> have 21:40:57.950 --> 21:40:57.960 align:start position:0% system application storage you have 21:40:57.960 --> 21:40:59.774 align:start position:0% system application storage you have limited<21:40:58.440> control<21:40:58.616> over<21:40:58.920> the<21:40:59.160> selected 21:40:59.774 --> 21:40:59.784 align:start position:0% limited control over the selected 21:40:59.784 --> 21:41:02.270 align:start position:0% limited control over the selected networking<21:41:00.784> components<21:41:01.376> such<21:41:01.856> as<21:41:02.040> the 21:41:02.270 --> 21:41:02.280 align:start position:0% networking components such as the 21:41:02.280 --> 21:41:03.710 align:start position:0% networking components such as the firewall<21:41:02.696> that's<21:41:02.936> protecting<21:41:03.480> your 21:41:03.710 --> 21:41:03.720 align:start position:0% firewall that's protecting your 21:41:03.720 --> 21:41:06.414 align:start position:0% firewall that's protecting your particular<21:41:04.192> virtual<21:41:05.160> device 21:41:06.414 --> 21:41:06.424 align:start position:0% particular virtual device 21:41:06.424 --> 21:41:08.630 align:start position:0% particular virtual device again<21:41:07.016> you<21:41:07.376> can't<21:41:07.504> control<21:41:07.744> the<21:41:08.104> underlying 21:41:08.630 --> 21:41:08.640 align:start position:0% again you can't control the underlying 21:41:08.640 --> 21:41:10.966 align:start position:0% again you can't control the underlying Cloud<21:41:08.824> infrastructure<21:41:09.424> probably 21:41:10.966 --> 21:41:10.976 align:start position:0% Cloud infrastructure probably 21:41:10.976 --> 21:41:13.910 align:start position:0% Cloud infrastructure probably um<21:41:11.040> neither<21:41:11.464> would<21:41:11.576> you<21:41:11.760> want<21:41:11.936> to 21:41:13.910 --> 21:41:13.920 align:start position:0% um neither would you want to 21:41:13.920 --> 21:41:15.710 align:start position:0% um neither would you want to infrastructure<21:41:14.760> as<21:41:14.936> a<21:41:15.056> service<21:41:15.240> you've<21:41:15.656> got 21:41:15.710 --> 21:41:15.720 align:start position:0% infrastructure as a service you've got 21:41:15.720 --> 21:41:20.862 align:start position:0% infrastructure as a service you've got four<21:41:16.016> models<21:41:16.616> to<21:41:16.920> choose<21:41:17.160> from<21:41:17.464> for<21:41:17.936> iaas 21:41:20.862 --> 21:41:20.872 align:start position:0% four models to choose from for iaas 21:41:20.872 --> 21:41:22.366 align:start position:0% four models to choose from for iaas you've<21:41:21.240> got<21:41:21.296> the<21:41:21.480> private<21:41:21.784> Cloud<21:41:21.960> the 21:41:22.366 --> 21:41:22.376 align:start position:0% you've got the private Cloud the 21:41:22.376 --> 21:41:25.494 align:start position:0% you've got the private Cloud the community<21:41:22.616> Cloud<21:41:23.040> public<21:41:23.696> and<21:41:24.176> hybrid 21:41:25.494 --> 21:41:25.504 align:start position:0% community Cloud public and hybrid 21:41:25.504 --> 21:41:27.414 align:start position:0% community Cloud public and hybrid for<21:41:25.856> private<21:41:26.280> Cloud<21:41:26.464> the<21:41:27.240> cloud 21:41:27.414 --> 21:41:27.424 align:start position:0% for private Cloud the cloud 21:41:27.424 --> 21:41:28.790 align:start position:0% for private Cloud the cloud infrastructure<21:41:28.144> is<21:41:28.256> provisioned 21:41:28.790 --> 21:41:28.800 align:start position:0% infrastructure is provisioned 21:41:28.800 --> 21:41:31.670 align:start position:0% infrastructure is provisioned exclusively<21:41:29.400> for<21:41:29.640> a<21:41:29.760> single<21:41:30.000> organization 21:41:31.670 --> 21:41:31.680 align:start position:0% exclusively for a single organization 21:41:31.680 --> 21:41:34.182 align:start position:0% exclusively for a single organization so<21:41:32.160> you<21:41:32.280> get<21:41:32.512> exclusive<21:41:33.120> use<21:41:33.360> of<21:41:33.600> this<21:41:33.784> you've 21:41:34.182 --> 21:41:34.192 align:start position:0% so you get exclusive use of this you've 21:41:34.192 --> 21:41:35.750 align:start position:0% so you get exclusive use of this you've probably<21:41:34.256> hired<21:41:34.744> a<21:41:34.800> company 21:41:35.750 --> 21:41:35.760 align:start position:0% probably hired a company 21:41:35.760 --> 21:41:37.910 align:start position:0% probably hired a company to<21:41:36.424> create<21:41:36.600> all<21:41:36.896> of<21:41:36.960> the<21:41:37.080> infrastructure<21:41:37.616> for 21:41:37.910 --> 21:41:37.920 align:start position:0% to create all of the infrastructure for 21:41:37.920 --> 21:41:40.366 align:start position:0% to create all of the infrastructure for you<21:41:38.160> and<21:41:38.936> nobody<21:41:39.240> else<21:41:39.424> can<21:41:39.656> have<21:41:39.896> access<21:41:40.080> to 21:41:40.366 --> 21:41:40.376 align:start position:0% you and nobody else can have access to 21:41:40.376 --> 21:41:43.246 align:start position:0% you and nobody else can have access to it<21:41:40.496> and<21:41:40.680> all<21:41:40.800> of<21:41:40.976> your<21:41:41.576> offices<21:41:42.424> and<21:41:42.960> remote 21:41:43.246 --> 21:41:43.256 align:start position:0% it and all of your offices and remote 21:41:43.256 --> 21:41:46.246 align:start position:0% it and all of your offices and remote offices<21:41:44.216> will<21:41:44.512> have<21:41:44.696> access 21:41:46.246 --> 21:41:46.256 align:start position:0% offices will have access 21:41:46.256 --> 21:41:48.286 align:start position:0% offices will have access owned<21:41:47.216> operated<21:41:47.512> and<21:41:47.760> managed<21:41:48.000> by<21:41:48.176> the 21:41:48.286 --> 21:41:48.296 align:start position:0% owned operated and managed by the 21:41:48.296 --> 21:41:50.094 align:start position:0% owned operated and managed by the organization<21:41:48.832> itself 21:41:50.094 --> 21:41:50.104 align:start position:0% organization itself 21:41:50.104 --> 21:41:53.566 align:start position:0% organization itself very<21:41:50.576> third<21:41:50.872> party<21:41:51.120> or<21:41:51.424> a<21:41:51.600> combination 21:41:53.566 --> 21:41:53.576 align:start position:0% very third party or a combination 21:41:53.576 --> 21:41:55.670 align:start position:0% very third party or a combination a<21:41:54.056> physical<21:41:54.296> location<21:41:54.720> could<21:41:55.144> be<21:41:55.256> within<21:41:55.504> your 21:41:55.670 --> 21:41:55.680 align:start position:0% a physical location could be within your 21:41:55.680 --> 21:41:57.046 align:start position:0% a physical location could be within your premises<21:41:56.040> or<21:41:56.336> it<21:41:56.464> could<21:41:56.640> be<21:41:56.760> located 21:41:57.046 --> 21:41:57.056 align:start position:0% premises or it could be located 21:41:57.056 --> 21:41:59.502 align:start position:0% premises or it could be located Elsewhere<21:41:57.784> on<21:41:58.440> the<21:41:58.616> cloud 21:41:59.502 --> 21:41:59.512 align:start position:0% Elsewhere on the cloud 21:41:59.512 --> 21:42:02.862 align:start position:0% Elsewhere on the cloud Community<21:42:00.080> it's<21:42:01.376> um<21:42:01.376> Provisions<21:42:01.976> for<21:42:02.760> a 21:42:02.862 --> 21:42:02.872 align:start position:0% Community it's um Provisions for a 21:42:02.872 --> 21:42:05.206 align:start position:0% Community it's um Provisions for a specific<21:42:03.120> community<21:42:03.424> of<21:42:03.832> consumers<21:42:04.496> from 21:42:05.206 --> 21:42:05.216 align:start position:0% specific community of consumers from 21:42:05.216 --> 21:42:07.606 align:start position:0% specific community of consumers from organizations<21:42:05.936> that<21:42:06.240> share<21:42:06.536> common<21:42:06.832> concerns 21:42:07.606 --> 21:42:07.616 align:start position:0% organizations that share common concerns 21:42:07.616 --> 21:42:09.710 align:start position:0% organizations that share common concerns such<21:42:07.856> as<21:42:08.040> security<21:42:08.336> compliance 21:42:09.710 --> 21:42:09.720 align:start position:0% such as security compliance 21:42:09.720 --> 21:42:12.166 align:start position:0% such as security compliance jurisdiction<21:42:10.680> and<21:42:10.976> so<21:42:11.160> on<21:42:11.280> for<21:42:11.696> example<21:42:11.936> would 21:42:12.166 --> 21:42:12.176 align:start position:0% jurisdiction and so on for example would 21:42:12.176 --> 21:42:14.094 align:start position:0% jurisdiction and so on for example would be<21:42:12.360> law<21:42:12.536> reinforcement 21:42:14.094 --> 21:42:14.104 align:start position:0% be law reinforcement 21:42:14.104 --> 21:42:15.822 align:start position:0% be law reinforcement in<21:42:14.576> this<21:42:14.760> model<21:42:14.872> the<21:42:15.176> cloud<21:42:15.360> infrastructure 21:42:15.822 --> 21:42:15.832 align:start position:0% in this model the cloud infrastructure 21:42:15.832 --> 21:42:17.630 align:start position:0% in this model the cloud infrastructure may<21:42:16.144> be<21:42:16.256> owned<21:42:16.496> operated<21:42:16.856> by<21:42:17.160> one<21:42:17.336> or<21:42:17.512> more 21:42:17.630 --> 21:42:17.640 align:start position:0% may be owned operated by one or more 21:42:17.640 --> 21:42:20.566 align:start position:0% may be owned operated by one or more organizations<21:42:18.504> by<21:42:19.504> a<21:42:19.680> third<21:42:19.800> party<21:42:20.040> or<21:42:20.464> you 21:42:20.566 --> 21:42:20.576 align:start position:0% organizations by a third party or you 21:42:20.576 --> 21:42:22.734 align:start position:0% organizations by a third party or you could<21:42:20.696> have<21:42:20.824> a<21:42:21.000> combination 21:42:22.734 --> 21:42:22.744 align:start position:0% could have a combination 21:42:22.744 --> 21:42:25.366 align:start position:0% could have a combination the<21:42:23.160> physical<21:42:23.336> location<21:42:23.872> and<21:42:24.720> may<21:42:24.960> be<21:42:25.080> within 21:42:25.366 --> 21:42:25.376 align:start position:0% the physical location and may be within 21:42:25.376 --> 21:42:27.230 align:start position:0% the physical location and may be within your<21:42:25.552> premises<21:42:26.040> or<21:42:26.576> it<21:42:26.760> could<21:42:26.872> be<21:42:27.000> located 21:42:27.230 --> 21:42:27.240 align:start position:0% your premises or it could be located 21:42:27.240 --> 21:42:29.094 align:start position:0% your premises or it could be located elsewhere 21:42:29.094 --> 21:42:29.104 align:start position:0% elsewhere 21:42:29.104 --> 21:42:31.182 align:start position:0% elsewhere in<21:42:29.512> public<21:42:29.640> Cloud<21:42:29.936> it's<21:42:30.296> provision<21:42:30.720> for<21:42:30.960> the 21:42:31.182 --> 21:42:31.192 align:start position:0% in public Cloud it's provision for the 21:42:31.192 --> 21:42:33.470 align:start position:0% in public Cloud it's provision for the general<21:42:31.320> public<21:42:31.744> so<21:42:32.104> it<21:42:32.280> can<21:42:32.464> be<21:42:32.576> used<21:42:32.824> by<21:42:33.296> the 21:42:33.470 --> 21:42:33.480 align:start position:0% general public so it can be used by the 21:42:33.480 --> 21:42:36.046 align:start position:0% general public so it can be used by the general<21:42:33.600> public<21:42:34.040> over<21:42:35.040> a<21:42:35.336> network<21:42:35.512> such<21:42:35.872> as 21:42:36.046 --> 21:42:36.056 align:start position:0% general public over a network such as 21:42:36.056 --> 21:42:38.862 align:start position:0% general public over a network such as the<21:42:36.296> internet 21:42:38.862 --> 21:42:38.872 align:start position:0% 21:42:38.872 --> 21:42:40.790 align:start position:0% um<21:42:39.000> the<21:42:39.656> cloud<21:42:39.832> infrastructure<21:42:40.376> could<21:42:40.680> be 21:42:40.790 --> 21:42:40.800 align:start position:0% um the cloud infrastructure could be 21:42:40.800 --> 21:42:42.470 align:start position:0% um the cloud infrastructure could be managed<21:42:41.104> by<21:42:41.280> the<21:42:41.464> government<21:42:41.640> businesses 21:42:42.470 --> 21:42:42.480 align:start position:0% managed by the government businesses 21:42:42.480 --> 21:42:46.182 align:start position:0% managed by the government businesses Academia<21:42:43.320> or<21:42:43.976> a<21:42:44.216> combination 21:42:46.182 --> 21:42:46.192 align:start position:0% Academia or a combination 21:42:46.192 --> 21:42:49.542 align:start position:0% Academia or a combination foreign<21:42:46.976> physical<21:42:47.696> location<21:42:48.536> is<21:42:49.144> within<21:42:49.440> the 21:42:49.542 --> 21:42:49.552 align:start position:0% foreign physical location is within the 21:42:49.552 --> 21:42:51.886 align:start position:0% foreign physical location is within the premise<21:42:49.856> of<21:42:50.040> the<21:42:50.160> service<21:42:50.336> provider<21:42:51.056> now<21:42:51.720> a 21:42:51.886 --> 21:42:51.896 align:start position:0% premise of the service provider now a 21:42:51.896 --> 21:42:56.030 align:start position:0% premise of the service provider now a hybrid<21:42:52.192> is<21:42:52.440> a<21:42:52.680> mixture<21:42:52.976> of<21:42:53.160> any<21:42:53.464> of<21:42:53.640> these 21:42:56.030 --> 21:42:56.040 align:start position:0% 21:42:56.040 --> 21:42:57.950 align:start position:0% separate<21:42:56.824> entities<21:42:57.120> but<21:42:57.424> are<21:42:57.600> integrated 21:42:57.950 --> 21:42:57.960 align:start position:0% separate entities but are integrated 21:42:57.960 --> 21:43:00.046 align:start position:0% separate entities but are integrated into<21:42:58.144> the<21:42:58.440> benefits<21:42:58.920> for<21:42:59.216> the<21:42:59.640> um<21:42:59.640> of<21:42:59.936> the 21:43:00.046 --> 21:43:00.056 align:start position:0% into the benefits for the um of the 21:43:00.056 --> 21:43:02.630 align:start position:0% into the benefits for the um of the multiple<21:43:00.480> deployed<21:43:00.960> models 21:43:02.630 --> 21:43:02.640 align:start position:0% multiple deployed models 21:43:02.640 --> 21:43:05.206 align:start position:0% multiple deployed models example<21:43:03.240> is<21:43:03.424> when<21:43:03.600> the<21:43:03.784> it<21:43:03.960> organization<21:43:04.744> uses 21:43:05.206 --> 21:43:05.216 align:start position:0% example is when the it organization uses 21:43:05.216 --> 21:43:07.966 align:start position:0% example is when the it organization uses a<21:43:05.464> public<21:43:05.576> card<21:43:05.872> as<21:43:06.120> a<21:43:06.360> temporary<21:43:06.720> solution<21:43:07.080> to 21:43:07.966 --> 21:43:07.976 align:start position:0% a public card as a temporary solution to 21:43:07.976 --> 21:43:10.734 align:start position:0% a public card as a temporary solution to meet<21:43:08.640> um<21:43:08.640> an<21:43:09.000> excess<21:43:09.296> capacity<21:43:09.832> demand<21:43:10.320> that 21:43:10.734 --> 21:43:10.744 align:start position:0% meet um an excess capacity demand that 21:43:10.744 --> 21:43:15.110 align:start position:0% meet um an excess capacity demand that can't<21:43:10.920> be<21:43:11.104> met<21:43:11.280> by<21:43:12.056> their<21:43:12.296> private<21:43:12.720> setup 21:43:15.110 --> 21:43:15.120 align:start position:0% can't be met by their private setup 21:43:15.120 --> 21:43:16.606 align:start position:0% can't be met by their private setup so<21:43:15.480> I've<21:43:15.656> looked<21:43:15.960> at<21:43:16.016> quite<21:43:16.144> a<21:43:16.256> few<21:43:16.376> things 21:43:16.606 --> 21:43:16.616 align:start position:0% so I've looked at quite a few things 21:43:16.616 --> 21:43:18.470 align:start position:0% so I've looked at quite a few things here<21:43:16.976> you<21:43:17.512> need<21:43:17.696> to<21:43:17.824> make<21:43:17.936> some<21:43:18.176> notes 21:43:18.470 --> 21:43:18.480 align:start position:0% here you need to make some notes 21:43:18.480 --> 21:43:19.734 align:start position:0% here you need to make some notes obviously<21:43:18.832> because<21:43:19.016> there's<21:43:19.256> a<21:43:19.440> few<21:43:19.552> things 21:43:19.734 --> 21:43:19.744 align:start position:0% obviously because there's a few things 21:43:19.744 --> 21:43:23.030 align:start position:0% obviously because there's a few things to<21:43:19.920> remember<21:43:20.040> for<21:43:20.336> the<21:43:20.512> exam 21:43:23.030 --> 21:43:23.040 align:start position:0% 21:43:23.040 --> 21:43:26.326 align:start position:0% service<21:43:23.760> models<21:43:24.856> software<21:43:25.856> as<21:43:25.976> a<21:43:26.160> service 21:43:26.326 --> 21:43:26.336 align:start position:0% service models software as a service 21:43:26.336 --> 21:43:29.206 align:start position:0% service models software as a service platform<21:43:27.016> infrastructure<21:43:28.216> private 21:43:29.206 --> 21:43:29.216 align:start position:0% platform infrastructure private 21:43:29.216 --> 21:43:32.206 align:start position:0% platform infrastructure private community<21:43:29.512> and<21:43:30.000> public<21:43:30.176> cloud<21:43:30.536> and<21:43:31.256> hybrid 21:43:32.206 --> 21:43:32.216 align:start position:0% community and public cloud and hybrid 21:43:32.216 --> 21:43:33.822 align:start position:0% community and public cloud and hybrid okay<21:43:32.576> that's<21:43:32.824> all<21:43:33.000> for<21:43:33.176> now<21:43:33.360> thanks<21:43:33.720> for 21:43:33.822 --> 21:43:33.832 align:start position:0% okay that's all for now thanks for 21:43:33.832 --> 21:43:37.560 align:start position:0% okay that's all for now thanks for watching 21:43:37.560 --> 21:43:37.570 align:start position:0% 21:43:37.570 --> 21:43:53.686 align:start position:0% [Music] 21:43:53.686 --> 21:43:53.696 align:start position:0% 21:43:53.696 --> 21:43:56.094 align:start position:0% welcome<21:43:54.176> to<21:43:54.424> module<21:43:54.784> 18<21:43:54.896> lesson<21:43:55.552> one<21:43:55.680> physical 21:43:56.094 --> 21:43:56.104 align:start position:0% welcome to module 18 lesson one physical 21:43:56.104 --> 21:43:58.846 align:start position:0% welcome to module 18 lesson one physical security<21:43:56.656> controls<21:43:57.656> I'm<21:43:58.256> going<21:43:58.440> to<21:43:58.496> whisk 21:43:58.846 --> 21:43:58.856 align:start position:0% security controls I'm going to whisk 21:43:58.856 --> 21:44:00.166 align:start position:0% security controls I'm going to whisk through<21:43:58.920> this<21:43:59.104> pretty<21:43:59.280> quickly<21:43:59.640> because<21:43:59.872> most 21:44:00.166 --> 21:44:00.176 align:start position:0% through this pretty quickly because most 21:44:00.176 --> 21:44:03.310 align:start position:0% through this pretty quickly because most of<21:44:00.360> it<21:44:00.480> is<21:44:00.656> pretty<21:44:01.016> self-explanatory 21:44:03.310 --> 21:44:03.320 align:start position:0% of it is pretty self-explanatory 21:44:03.320 --> 21:44:06.710 align:start position:0% of it is pretty self-explanatory and<21:44:04.320> Common<21:44:05.280> Sense<21:44:05.696> really<21:44:05.872> physical 21:44:06.710 --> 21:44:06.720 align:start position:0% and Common Sense really physical 21:44:06.720 --> 21:44:10.486 align:start position:0% and Common Sense really physical security<21:44:07.440> man<21:44:07.976> traps<21:44:08.464> Network<21:44:08.760> closets<21:44:09.496> video 21:44:10.486 --> 21:44:10.496 align:start position:0% security man traps Network closets video 21:44:10.496 --> 21:44:12.846 align:start position:0% security man traps Network closets video monitoring<21:44:11.216> door<21:44:11.640> access<21:44:11.872> controls 21:44:12.846 --> 21:44:12.856 align:start position:0% monitoring door access controls 21:44:12.856 --> 21:44:15.886 align:start position:0% monitoring door access controls proximity<21:44:13.856> readers<21:44:14.400> biometrics 21:44:15.886 --> 21:44:15.896 align:start position:0% proximity readers biometrics 21:44:15.896 --> 21:44:20.390 align:start position:0% proximity readers biometrics Cipher<21:44:16.616> locks<21:44:16.920> and<21:44:17.280> a<21:44:17.576> security<21:44:17.824> guard 21:44:20.390 --> 21:44:20.400 align:start position:0% 21:44:20.400 --> 21:44:23.030 align:start position:0% so<21:44:20.760> the<21:44:20.872> physical<21:44:21.056> security<21:44:21.600> control<21:44:22.080> is<21:44:22.744> the 21:44:23.030 --> 21:44:23.040 align:start position:0% so the physical security control is the 21:44:23.040 --> 21:44:25.542 align:start position:0% so the physical security control is the measures<21:44:23.464> we<21:44:23.872> take<21:44:24.120> from<21:44:24.656> physical<21:44:24.960> threats 21:44:25.542 --> 21:44:25.552 align:start position:0% measures we take from physical threats 21:44:25.552 --> 21:44:28.734 align:start position:0% measures we take from physical threats basically<21:44:26.104> people<21:44:27.016> trying<21:44:28.016> to<21:44:28.144> get<21:44:28.256> into<21:44:28.440> our 21:44:28.734 --> 21:44:28.744 align:start position:0% basically people trying to get into our 21:44:28.744 --> 21:44:30.590 align:start position:0% basically people trying to get into our data<21:44:29.160> center 21:44:30.590 --> 21:44:30.600 align:start position:0% data center 21:44:30.600 --> 21:44:32.630 align:start position:0% data center I<21:44:31.080> guess<21:44:31.256> Ram<21:44:31.440> radio<21:44:31.744> might<21:44:32.104> be<21:44:32.216> included 21:44:32.630 --> 21:44:32.640 align:start position:0% I guess Ram radio might be included 21:44:32.640 --> 21:44:34.734 align:start position:0% I guess Ram radio might be included because<21:44:32.936> I've<21:44:33.240> never<21:44:33.360> heard<21:44:33.600> of<21:44:33.784> that<21:44:33.960> but<21:44:34.552> uh 21:44:34.734 --> 21:44:34.744 align:start position:0% because I've never heard of that but uh 21:44:34.744 --> 21:44:38.166 align:start position:0% because I've never heard of that but uh yeah<21:44:34.976> physical<21:44:35.280> security 21:44:38.166 --> 21:44:38.176 align:start position:0% 21:44:38.176 --> 21:44:40.734 align:start position:0% examples<21:44:39.176> I've<21:44:39.536> already<21:44:39.656> mentioned<21:44:40.192> the<21:44:40.552> man 21:44:40.734 --> 21:44:40.744 align:start position:0% examples I've already mentioned the man 21:44:40.744 --> 21:44:43.070 align:start position:0% examples I've already mentioned the man traps<21:44:41.216> the<21:44:41.336> network<21:44:41.512> closets 21:44:43.070 --> 21:44:43.080 align:start position:0% traps the network closets 21:44:43.080 --> 21:44:45.414 align:start position:0% traps the network closets they<21:44:43.744> reduce<21:44:43.920> the<21:44:44.216> risk<21:44:44.464> of<21:44:44.512> damage<21:44:44.872> or<21:44:45.120> loss 21:44:45.414 --> 21:44:45.424 align:start position:0% they reduce the risk of damage or loss 21:44:45.424 --> 21:44:47.030 align:start position:0% they reduce the risk of damage or loss by<21:44:45.600> preventing<21:44:46.080> or<21:44:46.256> slowing<21:44:46.616> down<21:44:46.800> physical 21:44:47.030 --> 21:44:47.040 align:start position:0% by preventing or slowing down physical 21:44:47.040 --> 21:44:50.502 align:start position:0% by preventing or slowing down physical attack<21:44:47.464> I've<21:44:48.296> actually<21:44:48.480> been<21:44:48.896> a<21:44:49.256> worked<21:44:49.680> uh<21:44:50.400> or 21:44:50.502 --> 21:44:50.512 align:start position:0% attack I've actually been a worked uh or 21:44:50.512 --> 21:44:53.862 align:start position:0% attack I've actually been a worked uh or been<21:44:50.760> to<21:44:50.936> a<21:44:51.120> few<21:44:51.240> networks<21:44:51.720> Consulting<21:44:52.872> where 21:44:53.862 --> 21:44:53.872 align:start position:0% been to a few networks Consulting where 21:44:53.872 --> 21:44:57.182 align:start position:0% been to a few networks Consulting where they<21:44:54.296> don't<21:44:54.480> have<21:44:54.960> any<21:44:55.376> security<21:44:56.216> whatsoever 21:44:57.182 --> 21:44:57.192 align:start position:0% they don't have any security whatsoever 21:44:57.192 --> 21:44:59.326 align:start position:0% they don't have any security whatsoever everything's<21:44:58.192> shoved<21:44:58.496> in<21:44:58.616> a<21:44:58.744> Cupboard<21:44:59.040> and 21:44:59.326 --> 21:44:59.336 align:start position:0% everything's shoved in a Cupboard and 21:44:59.336 --> 21:45:01.846 align:start position:0% everything's shoved in a Cupboard and the<21:44:59.640> entire<21:45:00.536> company<21:45:00.832> website<21:45:01.504> the 21:45:01.846 --> 21:45:01.856 align:start position:0% the entire company website the 21:45:01.856 --> 21:45:05.150 align:start position:0% the entire company website the financials<21:45:02.640> the<21:45:03.240> accounting<21:45:03.960> all<21:45:04.376> stuck<21:45:04.976> on 21:45:05.150 --> 21:45:05.160 align:start position:0% financials the accounting all stuck on 21:45:05.160 --> 21:45:06.774 align:start position:0% financials the accounting all stuck on the<21:45:05.280> server<21:45:05.576> hanging<21:45:05.936> off<21:45:06.056> a<21:45:06.240> cable<21:45:06.360> in<21:45:06.656> a 21:45:06.774 --> 21:45:06.784 align:start position:0% the server hanging off a cable in a 21:45:06.784 --> 21:45:08.862 align:start position:0% the server hanging off a cable in a Cupboard<21:45:07.016> and<21:45:07.256> I'm<21:45:07.376> sure<21:45:07.504> you've<21:45:07.744> seen<21:45:08.040> the 21:45:08.862 --> 21:45:08.872 align:start position:0% Cupboard and I'm sure you've seen the 21:45:08.872 --> 21:45:10.182 align:start position:0% Cupboard and I'm sure you've seen the pictures<21:45:09.056> or<21:45:09.424> may<21:45:09.536> have<21:45:09.720> seen<21:45:09.784> it<21:45:10.016> yourself 21:45:10.182 --> 21:45:10.192 align:start position:0% pictures or may have seen it yourself 21:45:10.192 --> 21:45:11.454 align:start position:0% pictures or may have seen it yourself for<21:45:10.552> real 21:45:11.454 --> 21:45:11.464 align:start position:0% for real 21:45:11.464 --> 21:45:13.246 align:start position:0% for real and<21:45:12.056> it's<21:45:12.176> pretty<21:45:12.424> easy<21:45:12.656> to<21:45:12.832> do<21:45:12.960> it<21:45:13.080> doesn't 21:45:13.246 --> 21:45:13.256 align:start position:0% and it's pretty easy to do it doesn't 21:45:13.256 --> 21:45:15.886 align:start position:0% and it's pretty easy to do it doesn't have<21:45:13.440> to<21:45:13.552> be<21:45:13.680> expensive<21:45:14.280> a<21:45:15.176> man<21:45:15.360> trap<21:45:15.720> I've 21:45:15.886 --> 21:45:15.896 align:start position:0% have to be expensive a man trap I've 21:45:15.896 --> 21:45:18.886 align:start position:0% have to be expensive a man trap I've experienced<21:45:16.616> in<21:45:17.216> a<21:45:17.696> internet<21:45:18.480> service 21:45:18.886 --> 21:45:18.896 align:start position:0% experienced in a internet service 21:45:18.896 --> 21:45:20.862 align:start position:0% experienced in a internet service provider<21:45:19.552> that<21:45:19.800> used<21:45:19.920> to<21:45:20.104> host<21:45:20.336> some<21:45:20.576> of<21:45:20.760> my 21:45:20.862 --> 21:45:20.872 align:start position:0% provider that used to host some of my 21:45:20.872 --> 21:45:22.486 align:start position:0% provider that used to host some of my equipment 21:45:22.486 --> 21:45:22.496 align:start position:0% equipment 21:45:22.496 --> 21:45:26.030 align:start position:0% equipment basically<21:45:23.400> it's<21:45:23.872> a<21:45:24.120> space<21:45:24.360> it's<21:45:24.784> a<21:45:25.016> door 21:45:26.030 --> 21:45:26.040 align:start position:0% basically it's a space it's a door 21:45:26.040 --> 21:45:28.366 align:start position:0% basically it's a space it's a door um<21:45:26.104> within<21:45:26.576> a<21:45:26.760> door<21:45:26.936> so<21:45:27.720> you<21:45:27.832> go<21:45:27.960> through<21:45:28.144> one 21:45:28.366 --> 21:45:28.376 align:start position:0% um within a door so you go through one 21:45:28.376 --> 21:45:29.926 align:start position:0% um within a door so you go through one set<21:45:28.552> of<21:45:28.744> doors<21:45:28.976> which<21:45:29.160> it<21:45:29.336> normally<21:45:29.576> has<21:45:29.760> got 21:45:29.926 --> 21:45:29.936 align:start position:0% set of doors which it normally has got 21:45:29.936 --> 21:45:32.326 align:start position:0% set of doors which it normally has got some<21:45:30.176> type<21:45:30.360> of<21:45:30.536> security<21:45:31.216> keypads<21:45:32.216> or 21:45:32.326 --> 21:45:32.336 align:start position:0% some type of security keypads or 21:45:32.336 --> 21:45:33.950 align:start position:0% some type of security keypads or whatever<21:45:32.464> and<21:45:33.240> then<21:45:33.360> you've<21:45:33.536> got<21:45:33.656> a<21:45:33.832> second 21:45:33.950 --> 21:45:33.960 align:start position:0% whatever and then you've got a second 21:45:33.960 --> 21:45:36.350 align:start position:0% whatever and then you've got a second set<21:45:34.256> of<21:45:34.376> doors<21:45:34.680> you<21:45:34.800> have<21:45:34.976> to<21:45:35.104> go<21:45:35.216> through<21:45:35.512> if 21:45:36.350 --> 21:45:36.360 align:start position:0% set of doors you have to go through if 21:45:36.360 --> 21:45:38.150 align:start position:0% set of doors you have to go through if it's<21:45:36.480> a<21:45:36.656> manual<21:45:36.896> Man<21:45:37.144> Trap<21:45:37.504> or<21:45:37.616> security<21:45:37.800> guard 21:45:38.150 --> 21:45:38.160 align:start position:0% it's a manual Man Trap or security guard 21:45:38.160 --> 21:45:39.710 align:start position:0% it's a manual Man Trap or security guard locks<21:45:38.576> and<21:45:38.640> unlocks<21:45:39.120> each<21:45:39.240> doors<21:45:39.600> and 21:45:39.710 --> 21:45:39.720 align:start position:0% locks and unlocks each doors and 21:45:39.720 --> 21:45:42.350 align:start position:0% locks and unlocks each doors and sequence<21:45:40.160> if<21:45:41.160> it's<21:45:41.336> automatic<21:45:41.824> the<21:45:42.000> doors<21:45:42.240> are 21:45:42.350 --> 21:45:42.360 align:start position:0% sequence if it's automatic the doors are 21:45:42.360 --> 21:45:43.846 align:start position:0% sequence if it's automatic the doors are only<21:45:42.536> opened<21:45:42.960> after<21:45:43.080> getting<21:45:43.376> an 21:45:43.846 --> 21:45:43.856 align:start position:0% only opened after getting an 21:45:43.856 --> 21:45:46.486 align:start position:0% only opened after getting an identification<21:45:44.512> from<21:45:45.176> the<21:45:45.600> person 21:45:46.486 --> 21:45:46.496 align:start position:0% identification from the person 21:45:46.496 --> 21:45:48.470 align:start position:0% identification from the person uh<21:45:46.976> the<21:45:47.160> one<21:45:47.280> I<21:45:47.464> went<21:45:47.640> to<21:45:47.696> you<21:45:47.936> had<21:45:48.056> to<21:45:48.176> do<21:45:48.296> a 21:45:48.470 --> 21:45:48.480 align:start position:0% uh the one I went to you had to do a 21:45:48.480 --> 21:45:50.454 align:start position:0% uh the one I went to you had to do a keypad<21:45:48.832> to<21:45:49.016> get<21:45:49.144> through<21:45:49.320> the<21:45:49.504> front<21:45:49.680> door<21:45:49.920> and 21:45:50.454 --> 21:45:50.464 align:start position:0% keypad to get through the front door and 21:45:50.464 --> 21:45:52.006 align:start position:0% keypad to get through the front door and then<21:45:50.576> actually<21:45:50.760> pick<21:45:51.056> up<21:45:51.176> a<21:45:51.360> phone<21:45:51.480> and<21:45:51.720> speak 21:45:52.006 --> 21:45:52.016 align:start position:0% then actually pick up a phone and speak 21:45:52.016 --> 21:45:55.070 align:start position:0% then actually pick up a phone and speak to<21:45:52.320> the<21:45:53.104> on-call<21:45:53.464> engineer<21:45:54.000> to<21:45:54.784> get<21:45:54.896> through 21:45:55.070 --> 21:45:55.080 align:start position:0% to the on-call engineer to get through 21:45:55.080 --> 21:45:56.502 align:start position:0% to the on-call engineer to get through the<21:45:55.320> second<21:45:55.440> door 21:45:56.502 --> 21:45:56.512 align:start position:0% the second door 21:45:56.512 --> 21:45:59.390 align:start position:0% the second door and<21:45:56.872> it<21:45:57.000> all<21:45:57.120> had<21:45:57.296> to<21:45:57.424> be<21:45:57.536> done<21:45:57.656> by<21:45:57.896> appointment 21:45:59.390 --> 21:45:59.400 align:start position:0% and it all had to be done by appointment 21:45:59.400 --> 21:46:01.606 align:start position:0% and it all had to be done by appointment our<21:45:59.760> Network<21:45:59.872> closet<21:46:00.480> is<21:46:00.656> is<21:46:00.960> a<21:46:01.192> room<21:46:01.320> where 21:46:01.606 --> 21:46:01.616 align:start position:0% our Network closet is is a room where 21:46:01.616 --> 21:46:03.590 align:start position:0% our Network closet is is a room where Network<21:46:01.856> hardware<21:46:02.160> switches<21:46:02.936> switches<21:46:03.424> and 21:46:03.590 --> 21:46:03.600 align:start position:0% Network hardware switches switches and 21:46:03.600 --> 21:46:06.046 align:start position:0% Network hardware switches switches and routers<21:46:03.960> are<21:46:04.144> installed<21:46:04.552> physical<21:46:05.464> access<21:46:05.760> to 21:46:06.046 --> 21:46:06.056 align:start position:0% routers are installed physical access to 21:46:06.056 --> 21:46:07.790 align:start position:0% routers are installed physical access to the<21:46:06.176> closet<21:46:06.536> is<21:46:06.656> normally<21:46:06.960> restricted<21:46:07.552> by 21:46:07.790 --> 21:46:07.800 align:start position:0% the closet is normally restricted by 21:46:07.800 --> 21:46:10.734 align:start position:0% the closet is normally restricted by having<21:46:08.104> some<21:46:08.400> sort<21:46:08.576> of<21:46:08.696> security<21:46:08.936> control 21:46:10.734 --> 21:46:10.744 align:start position:0% having some sort of security control 21:46:10.744 --> 21:46:12.710 align:start position:0% having some sort of security control videos 21:46:12.710 --> 21:46:12.720 align:start position:0% videos 21:46:12.720 --> 21:46:15.646 align:start position:0% videos um<21:46:12.784> normally<21:46:13.376> record<21:46:13.856> who<21:46:14.696> comes<21:46:15.000> in<21:46:15.120> who<21:46:15.360> goes 21:46:15.646 --> 21:46:15.656 align:start position:0% um normally record who comes in who goes 21:46:15.656 --> 21:46:18.230 align:start position:0% um normally record who comes in who goes out<21:46:15.784> who<21:46:16.016> accesses<21:46:16.552> what<21:46:16.856> and<21:46:17.104> where<21:46:17.280> and<21:46:18.056> it's 21:46:18.230 --> 21:46:18.240 align:start position:0% out who accesses what and where and it's 21:46:18.240 --> 21:46:21.286 align:start position:0% out who accesses what and where and it's recorded<21:46:18.720> for<21:46:19.016> a<21:46:19.256> set<21:46:19.440> period<21:46:19.800> of<21:46:19.976> time<21:46:20.296> this 21:46:21.286 --> 21:46:21.296 align:start position:0% recorded for a set period of time this 21:46:21.296 --> 21:46:25.366 align:start position:0% recorded for a set period of time this can<21:46:21.480> be<21:46:21.600> CCTV<21:46:22.440> or<21:46:23.280> video<21:46:23.512> over<21:46:23.936> IP 21:46:25.366 --> 21:46:25.376 align:start position:0% can be CCTV or video over IP 21:46:25.376 --> 21:46:27.846 align:start position:0% can be CCTV or video over IP foreign 21:46:27.846 --> 21:46:27.856 align:start position:0% foreign 21:46:27.856 --> 21:46:30.286 align:start position:0% foreign electronic<21:46:28.856> system<21:46:29.104> I'm<21:46:29.696> sure<21:46:29.872> you've<21:46:30.120> used 21:46:30.286 --> 21:46:30.296 align:start position:0% electronic system I'm sure you've used 21:46:30.296 --> 21:46:31.790 align:start position:0% electronic system I'm sure you've used these<21:46:30.600> in<21:46:30.720> a<21:46:30.832> lot<21:46:30.960> of<21:46:31.016> different<21:46:31.144> places<21:46:31.440> to 21:46:31.790 --> 21:46:31.800 align:start position:0% these in a lot of different places to 21:46:31.800 --> 21:46:33.950 align:start position:0% these in a lot of different places to get<21:46:31.920> in<21:46:32.040> and<21:46:32.216> out<21:46:32.400> of<21:46:32.576> different<21:46:33.296> rooms<21:46:33.720> and 21:46:33.950 --> 21:46:33.960 align:start position:0% get in and out of different rooms and 21:46:33.960 --> 21:46:37.734 align:start position:0% get in and out of different rooms and buildings<21:46:34.320> and<21:46:34.616> floors<21:46:35.424> and<21:46:36.424> use<21:46:37.080> a<21:46:37.376> granted 21:46:37.734 --> 21:46:37.744 align:start position:0% buildings and floors and use a granted 21:46:37.744 --> 21:46:39.590 align:start position:0% buildings and floors and use a granted access<21:46:37.920> door<21:46:38.336> if<21:46:38.640> the<21:46:38.760> door<21:46:38.872> is<21:46:39.056> open<21:46:39.176> for<21:46:39.480> a 21:46:39.590 --> 21:46:39.600 align:start position:0% access door if the door is open for a 21:46:39.600 --> 21:46:41.750 align:start position:0% access door if the door is open for a predetermined<21:46:40.256> amount<21:46:40.440> of<21:46:40.552> time<21:46:40.744> and<21:46:41.576> the 21:46:41.750 --> 21:46:41.760 align:start position:0% predetermined amount of time and the 21:46:41.760 --> 21:46:44.270 align:start position:0% predetermined amount of time and the entry<21:46:42.000> is<21:46:42.120> recorded<21:46:42.656> the<21:46:43.440> door<21:46:43.616> remains 21:46:44.270 --> 21:46:44.280 align:start position:0% entry is recorded the door remains 21:46:44.280 --> 21:46:46.542 align:start position:0% entry is recorded the door remains closed<21:46:44.760> when<21:46:45.000> the<21:46:45.176> users<21:46:45.424> denied<21:46:45.784> access<21:46:46.016> that 21:46:46.542 --> 21:46:46.552 align:start position:0% closed when the users denied access that 21:46:46.552 --> 21:46:48.646 align:start position:0% closed when the users denied access that attempt<21:46:46.856> is<21:46:47.040> still<21:46:47.216> recorded 21:46:48.646 --> 21:46:48.656 align:start position:0% attempt is still recorded 21:46:48.656 --> 21:46:51.526 align:start position:0% attempt is still recorded if<21:46:49.080> the<21:46:49.192> doors<21:46:49.440> held<21:46:49.856> open<21:46:50.464> for<21:46:50.872> too<21:46:51.000> long<21:46:51.176> then 21:46:51.526 --> 21:46:51.536 align:start position:0% if the doors held open for too long then 21:46:51.536 --> 21:46:53.814 align:start position:0% if the doors held open for too long then it<21:46:51.720> should<21:46:51.832> trigger<21:46:52.256> some<21:46:52.496> sort<21:46:52.744> of<21:46:52.856> action<21:46:53.512> or 21:46:53.814 --> 21:46:53.824 align:start position:0% it should trigger some sort of action or 21:46:53.824 --> 21:46:54.950 align:start position:0% it should trigger some sort of action or alarm 21:46:54.950 --> 21:46:54.960 align:start position:0% alarm 21:46:54.960 --> 21:46:58.670 align:start position:0% alarm proximity<21:46:56.120> reader<21:46:57.120> is<21:46:57.296> basically<21:46:57.832> electronic 21:46:58.670 --> 21:46:58.680 align:start position:0% proximity reader is basically electronic 21:46:58.680 --> 21:47:00.526 align:start position:0% proximity reader is basically electronic access<21:46:58.856> where<21:46:59.400> you<21:46:59.576> have<21:46:59.872> some<21:47:00.056> sort<21:47:00.240> of<21:47:00.360> smart 21:47:00.526 --> 21:47:00.536 align:start position:0% access where you have some sort of smart 21:47:00.536 --> 21:47:03.710 align:start position:0% access where you have some sort of smart card<21:47:00.896> and<21:47:01.744> you<21:47:01.920> swipe<21:47:02.280> your<21:47:02.464> way<21:47:02.696> in<21:47:03.176> and 21:47:03.710 --> 21:47:03.720 align:start position:0% card and you swipe your way in and 21:47:03.720 --> 21:47:05.926 align:start position:0% card and you swipe your way in and possibly<21:47:04.080> out<21:47:04.320> again<21:47:04.616> as<21:47:04.920> well<21:47:05.104> you'll 21:47:05.926 --> 21:47:05.936 align:start position:0% possibly out again as well you'll 21:47:05.936 --> 21:47:08.502 align:start position:0% possibly out again as well you'll normally<21:47:06.176> hold<21:47:06.536> the<21:47:06.832> card<21:47:07.192> on<21:47:07.800> or<21:47:08.104> in<21:47:08.336> the 21:47:08.502 --> 21:47:08.512 align:start position:0% normally hold the card on or in the 21:47:08.512 --> 21:47:09.710 align:start position:0% normally hold the card on or in the reader 21:47:09.710 --> 21:47:09.720 align:start position:0% reader 21:47:09.720 --> 21:47:12.350 align:start position:0% reader proximity<21:47:10.552> read<21:47:10.800> normally<21:47:11.216> bleeps<21:47:11.760> or<21:47:12.000> beeps 21:47:12.350 --> 21:47:12.360 align:start position:0% proximity read normally bleeps or beeps 21:47:12.360 --> 21:47:15.166 align:start position:0% proximity read normally bleeps or beeps when<21:47:12.536> it<21:47:12.784> has<21:47:12.960> red<21:47:13.552> your<21:47:13.920> smart<21:47:14.160> card<21:47:14.464> if<21:47:15.000> it 21:47:15.166 --> 21:47:15.176 align:start position:0% when it has red your smart card if it 21:47:15.176 --> 21:47:16.670 align:start position:0% when it has red your smart card if it doesn't<21:47:15.296> read<21:47:15.536> it<21:47:15.784> you<21:47:15.960> may<21:47:16.080> hear<21:47:16.256> a<21:47:16.552> different 21:47:16.670 --> 21:47:16.680 align:start position:0% doesn't read it you may hear a different 21:47:16.680 --> 21:47:19.606 align:start position:0% doesn't read it you may hear a different type<21:47:16.976> of<21:47:17.160> beep<21:47:18.000> and<21:47:18.600> you<21:47:18.960> may<21:47:19.080> have<21:47:19.192> to<21:47:19.320> go<21:47:19.504> and 21:47:19.606 --> 21:47:19.616 align:start position:0% type of beep and you may have to go and 21:47:19.616 --> 21:47:22.366 align:start position:0% type of beep and you may have to go and get<21:47:20.040> your<21:47:20.160> car<21:47:20.336> checked<21:47:20.760> or<21:47:20.936> renewed 21:47:22.366 --> 21:47:22.376 align:start position:0% get your car checked or renewed 21:47:22.376 --> 21:47:23.926 align:start position:0% get your car checked or renewed when<21:47:22.680> the<21:47:22.800> user's<21:47:23.160> granted<21:47:23.400> access<21:47:23.576> to<21:47:23.824> the 21:47:23.926 --> 21:47:23.936 align:start position:0% when the user's granted access to the 21:47:23.936 --> 21:47:25.790 align:start position:0% when the user's granted access to the door<21:47:24.056> will<21:47:24.240> open<21:47:24.480> otherwise<21:47:25.192> it<21:47:25.376> remains 21:47:25.790 --> 21:47:25.800 align:start position:0% door will open otherwise it remains 21:47:25.800 --> 21:47:27.230 align:start position:0% door will open otherwise it remains closed 21:47:27.230 --> 21:47:27.240 align:start position:0% closed 21:47:27.240 --> 21:47:29.566 align:start position:0% closed it's<21:47:27.296> pretty<21:47:27.600> obvious<21:47:27.896> to<21:47:28.144> be<21:47:28.256> honest 21:47:29.566 --> 21:47:29.576 align:start position:0% it's pretty obvious to be honest 21:47:29.576 --> 21:47:32.326 align:start position:0% it's pretty obvious to be honest Biometrics<21:47:30.480> refers<21:47:30.832> to<21:47:30.976> remetrics<21:47:31.976> related 21:47:32.326 --> 21:47:32.336 align:start position:0% Biometrics refers to remetrics related 21:47:32.336 --> 21:47:35.030 align:start position:0% Biometrics refers to remetrics related to<21:47:32.640> human<21:47:32.936> characteristics<21:47:34.040> fingerprint 21:47:35.030 --> 21:47:35.040 align:start position:0% to human characteristics fingerprint 21:47:35.040 --> 21:47:38.270 align:start position:0% to human characteristics fingerprint face<21:47:35.400> Iris<21:47:36.056> retina<21:47:36.656> and<21:47:37.080> so<21:47:37.192> on<21:47:37.376> and<21:47:37.680> so<21:47:37.856> forth 21:47:38.270 --> 21:47:38.280 align:start position:0% face Iris retina and so on and so forth 21:47:38.280 --> 21:47:40.134 align:start position:0% face Iris retina and so on and so forth if<21:47:38.824> you've<21:47:39.056> seen<21:47:39.296> it<21:47:39.424> if<21:47:39.600> you've<21:47:39.720> watched<21:47:40.016> any 21:47:40.134 --> 21:47:40.144 align:start position:0% if you've seen it if you've watched any 21:47:40.144 --> 21:47:44.390 align:start position:0% if you've seen it if you've watched any of<21:47:40.320> the<21:47:40.856> um<21:47:40.856> Mission<21:47:41.576> Impossible<21:47:42.176> movies 21:47:44.390 --> 21:47:44.400 align:start position:0% of the um Mission Impossible movies 21:47:44.400 --> 21:47:46.310 align:start position:0% of the um Mission Impossible movies uh<21:47:44.872> since<21:47:45.120> Biometrics<21:47:45.832> are<21:47:45.960> unique<21:47:46.192> to 21:47:46.310 --> 21:47:46.320 align:start position:0% uh since Biometrics are unique to 21:47:46.320 --> 21:47:47.750 align:start position:0% uh since Biometrics are unique to individuals<21:47:46.800> they're<21:47:46.976> used<21:47:47.160> to<21:47:47.280> verify<21:47:47.640> the 21:47:47.750 --> 21:47:47.760 align:start position:0% individuals they're used to verify the 21:47:47.760 --> 21:47:49.182 align:start position:0% individuals they're used to verify the identity<21:47:48.120> of<21:47:48.424> an<21:47:48.600> individual<21:47:48.960> before 21:47:49.182 --> 21:47:49.192 align:start position:0% identity of an individual before 21:47:49.192 --> 21:47:52.246 align:start position:0% identity of an individual before granting<21:47:49.800> access<21:47:50.056> the<21:47:51.056> biometric<21:47:51.656> locks 21:47:52.246 --> 21:47:52.256 align:start position:0% granting access the biometric locks 21:47:52.256 --> 21:47:54.646 align:start position:0% granting access the biometric locks Grant<21:47:53.040> access<21:47:53.216> only<21:47:53.640> if<21:47:53.872> the<21:47:54.056> biometric 21:47:54.646 --> 21:47:54.656 align:start position:0% Grant access only if the biometric 21:47:54.656 --> 21:47:57.646 align:start position:0% Grant access only if the biometric feature<21:47:55.192> is<21:47:55.744> validated<21:47:56.360> for<21:47:57.360> example 21:47:57.646 --> 21:47:57.656 align:start position:0% feature is validated for example 21:47:57.656 --> 21:48:01.246 align:start position:0% feature is validated for example scanning<21:47:58.320> your<21:47:58.440> fingerprint 21:48:01.246 --> 21:48:01.256 align:start position:0% 21:48:01.256 --> 21:48:04.134 align:start position:0% keypad<21:48:01.920> and<21:48:02.216> Cipher<21:48:02.696> locks<21:48:03.056> the<21:48:03.656> cipher<21:48:04.016> lock 21:48:04.134 --> 21:48:04.144 align:start position:0% keypad and Cipher locks the cipher lock 21:48:04.144 --> 21:48:07.182 align:start position:0% keypad and Cipher locks the cipher lock uses<21:48:04.496> a<21:48:04.680> keypad<21:48:05.160> in<21:48:05.512> place<21:48:05.696> of<21:48:05.872> a<21:48:06.056> keyhole 21:48:07.182 --> 21:48:07.192 align:start position:0% uses a keypad in place of a keyhole 21:48:07.192 --> 21:48:10.006 align:start position:0% uses a keypad in place of a keyhole use<21:48:07.504> us<21:48:07.744> to<21:48:07.920> provide<21:48:08.160> the<21:48:08.336> correct<21:48:09.120> numerical 21:48:10.006 --> 21:48:10.016 align:start position:0% use us to provide the correct numerical 21:48:10.016 --> 21:48:12.470 align:start position:0% use us to provide the correct numerical pin<21:48:10.496> code<21:48:10.800> by<21:48:11.464> pressing<21:48:11.760> buttons<21:48:12.240> on<21:48:12.360> the 21:48:12.470 --> 21:48:12.480 align:start position:0% pin code by pressing buttons on the 21:48:12.480 --> 21:48:15.286 align:start position:0% pin code by pressing buttons on the keypad<21:48:13.376> cypherlock<21:48:14.336> could<21:48:14.640> have<21:48:14.872> four<21:48:15.056> or 21:48:15.286 --> 21:48:15.296 align:start position:0% keypad cypherlock could have four or 21:48:15.296 --> 21:48:17.502 align:start position:0% keypad cypherlock could have four or five<21:48:15.480> push<21:48:15.784> button<21:48:16.144> combination<21:48:16.616> in<21:48:17.104> order<21:48:17.216> to 21:48:17.502 --> 21:48:17.512 align:start position:0% five push button combination in order to 21:48:17.512 --> 21:48:19.206 align:start position:0% five push button combination in order to get<21:48:17.696> in 21:48:19.206 --> 21:48:19.216 align:start position:0% get in 21:48:19.216 --> 21:48:22.366 align:start position:0% get in uh<21:48:20.216> Cipher<21:48:20.936> code<21:48:21.056> is<21:48:21.296> created<21:48:21.656> at<21:48:22.016> the<21:48:22.192> initial 21:48:22.366 --> 21:48:22.376 align:start position:0% uh Cipher code is created at the initial 21:48:22.376 --> 21:48:23.814 align:start position:0% uh Cipher code is created at the initial setup<21:48:22.744> but<21:48:22.920> obviously<21:48:23.216> can<21:48:23.336> be<21:48:23.464> changed 21:48:23.814 --> 21:48:23.824 align:start position:0% setup but obviously can be changed 21:48:23.824 --> 21:48:25.494 align:start position:0% setup but obviously can be changed usually<21:48:24.176> changed<21:48:24.600> every<21:48:24.784> week<21:48:25.016> or<21:48:25.256> every 21:48:25.494 --> 21:48:25.504 align:start position:0% usually changed every week or every 21:48:25.504 --> 21:48:26.814 align:start position:0% usually changed every week or every month 21:48:26.814 --> 21:48:26.824 align:start position:0% month 21:48:26.824 --> 21:48:29.750 align:start position:0% month and<21:48:27.424> the<21:48:27.600> security<21:48:27.784> guard<21:48:28.256> is<21:48:28.680> the<21:48:29.160> whoever's 21:48:29.750 --> 21:48:29.760 align:start position:0% and the security guard is the whoever's 21:48:29.760 --> 21:48:30.710 align:start position:0% and the security guard is the whoever's been 21:48:30.710 --> 21:48:30.720 align:start position:0% been 21:48:30.720 --> 21:48:34.310 align:start position:0% been uh<21:48:31.192> got<21:48:31.320> on<21:48:31.504> the<21:48:31.680> course<21:48:31.800> got<21:48:32.160> qualified<21:48:32.696> and 21:48:34.310 --> 21:48:34.320 align:start position:0% uh got on the course got qualified and 21:48:34.320 --> 21:48:37.606 align:start position:0% uh got on the course got qualified and um<21:48:34.440> it<21:48:34.744> has<21:48:34.976> become<21:48:35.280> the<21:48:35.640> security<21:48:36.056> person<21:48:36.616> it 21:48:37.606 --> 21:48:37.616 align:start position:0% um it has become the security person it 21:48:37.616 --> 21:48:40.606 align:start position:0% um it has become the security person it has<21:48:37.920> a<21:48:38.160> legal<21:48:38.336> or<21:48:38.512> inappropriate<21:48:39.056> actions 21:48:40.606 --> 21:48:40.616 align:start position:0% has a legal or inappropriate actions 21:48:40.616 --> 21:48:43.134 align:start position:0% has a legal or inappropriate actions all<21:48:41.160> right<21:48:41.280> so<21:48:41.576> covered<21:48:42.296> some 21:48:43.134 --> 21:48:43.144 align:start position:0% all right so covered some 21:48:43.144 --> 21:48:45.646 align:start position:0% all right so covered some following<21:48:43.856> items<21:48:44.336> all<21:48:44.696> fairly<21:48:45.120> obvious<21:48:45.424> I 21:48:45.646 --> 21:48:45.656 align:start position:0% following items all fairly obvious I 21:48:45.656 --> 21:48:48.822 align:start position:0% following items all fairly obvious I think<21:48:45.832> just<21:48:46.616> to<21:48:46.800> make<21:48:46.976> a<21:48:47.160> few<21:48:47.280> notes<21:48:47.760> for<21:48:48.480> the 21:48:48.822 --> 21:48:48.832 align:start position:0% think just to make a few notes for the 21:48:48.832 --> 21:48:50.750 align:start position:0% think just to make a few notes for the exam<21:48:49.744> and<21:48:50.104> I'll<21:48:50.160> see<21:48:50.336> you<21:48:50.464> on<21:48:50.512> the<21:48:50.640> next 21:48:50.750 --> 21:48:50.760 align:start position:0% exam and I'll see you on the next 21:48:50.760 --> 21:48:58.420 align:start position:0% exam and I'll see you on the next presentation<21:48:51.240> thanks<21:48:51.896> for<21:48:52.080> watching 21:48:58.420 --> 21:48:58.430 align:start position:0% 21:48:58.430 --> 21:49:08.414 align:start position:0% [Music] 21:49:08.414 --> 21:49:08.424 align:start position:0% [Music] 21:49:08.424 --> 21:49:12.046 align:start position:0% [Music] welcome<21:49:09.424> to<21:49:09.656> module<21:49:10.192> 18<21:49:10.376> lesson<21:49:11.040> 2<21:49:11.216> basic 21:49:12.046 --> 21:49:12.056 align:start position:0% welcome to module 18 lesson 2 basic 21:49:12.056 --> 21:49:14.390 align:start position:0% welcome to module 18 lesson 2 basic forensic<21:49:12.896> Concepts 21:49:14.390 --> 21:49:14.400 align:start position:0% forensic Concepts 21:49:14.400 --> 21:49:16.790 align:start position:0% forensic Concepts this<21:49:14.872> is<21:49:15.056> one<21:49:15.296> of<21:49:15.424> the<21:49:15.480> new<21:49:15.656> additions<21:49:16.144> to<21:49:16.440> the 21:49:16.790 --> 21:49:16.800 align:start position:0% this is one of the new additions to the 21:49:16.800 --> 21:49:19.966 align:start position:0% this is one of the new additions to the network<21:49:17.576> plus<21:49:17.936> syllabus<21:49:18.784> and<21:49:19.504> it's<21:49:19.680> basically 21:49:19.966 --> 21:49:19.976 align:start position:0% network plus syllabus and it's basically 21:49:19.976 --> 21:49:21.526 align:start position:0% network plus syllabus and it's basically because<21:49:20.216> of<21:49:20.464> the<21:49:20.640> increased<21:49:21.000> scope<21:49:21.296> for 21:49:21.526 --> 21:49:21.536 align:start position:0% because of the increased scope for 21:49:21.536 --> 21:49:23.094 align:start position:0% because of the increased scope for Network<21:49:21.720> engineers 21:49:23.094 --> 21:49:23.104 align:start position:0% Network engineers 21:49:23.104 --> 21:49:26.566 align:start position:0% Network engineers and<21:49:23.936> the<21:49:24.296> more<21:49:24.600> formal<21:49:25.192> proceedings<21:49:25.856> we<21:49:26.336> have 21:49:26.566 --> 21:49:26.576 align:start position:0% and the more formal proceedings we have 21:49:26.576 --> 21:49:29.814 align:start position:0% and the more formal proceedings we have in<21:49:28.016> um<21:49:28.016> respective<21:49:28.680> Cube<21:49:29.160> and<21:49:29.400> computer 21:49:29.814 --> 21:49:29.824 align:start position:0% in um respective Cube and computer 21:49:29.824 --> 21:49:31.494 align:start position:0% in um respective Cube and computer forensics 21:49:31.494 --> 21:49:31.504 align:start position:0% forensics 21:49:31.504 --> 21:49:33.414 align:start position:0% forensics so<21:49:31.920> this<21:49:32.104> is<21:49:32.280> quite<21:49:32.872> um 21:49:33.414 --> 21:49:33.424 align:start position:0% so this is quite um 21:49:33.424 --> 21:49:36.110 align:start position:0% so this is quite um an<21:49:33.960> emerging<21:49:34.440> field<21:49:35.040> of 21:49:36.110 --> 21:49:36.120 align:start position:0% an emerging field of 21:49:36.120 --> 21:49:37.734 align:start position:0% an emerging field of um<21:49:36.176> law 21:49:37.734 --> 21:49:37.744 align:start position:0% um law 21:49:37.744 --> 21:49:41.094 align:start position:0% um law and<21:49:38.280> evidence<21:49:38.832> and<21:49:39.832> obviously<21:49:40.320> we've<21:49:40.552> got<21:49:40.800> uh 21:49:41.094 --> 21:49:41.104 align:start position:0% and evidence and obviously we've got uh 21:49:41.104 --> 21:49:44.502 align:start position:0% and evidence and obviously we've got uh forensic<21:49:41.760> investigations<21:49:42.600> going<21:49:43.080> on<21:49:43.320> now<21:49:44.216> in 21:49:44.502 --> 21:49:44.512 align:start position:0% forensic investigations going on now in 21:49:44.512 --> 21:49:47.454 align:start position:0% forensic investigations going on now in terms<21:49:44.760> of<21:49:45.360> um<21:49:45.424> terrorism<21:49:46.080> and<21:49:46.496> other 21:49:47.454 --> 21:49:47.464 align:start position:0% terms of um terrorism and other 21:49:47.464 --> 21:49:50.750 align:start position:0% terms of um terrorism and other threats<21:49:48.176> and<21:49:48.424> crimes<21:49:48.896> and<21:49:49.920> um<21:49:49.976> we<21:49:50.280> need<21:49:50.464> to<21:49:50.576> be 21:49:50.750 --> 21:49:50.760 align:start position:0% threats and crimes and um we need to be 21:49:50.760 --> 21:49:52.846 align:start position:0% threats and crimes and um we need to be familiar<21:49:51.000> with<21:49:51.120> some<21:49:51.296> of<21:49:51.424> the<21:49:51.536> basics 21:49:52.846 --> 21:49:52.856 align:start position:0% familiar with some of the basics 21:49:52.856 --> 21:49:54.774 align:start position:0% familiar with some of the basics so<21:49:53.280> what<21:49:53.464> are<21:49:53.640> forensics<21:49:54.120> and<21:49:54.480> computer 21:49:54.774 --> 21:49:54.784 align:start position:0% so what are forensics and computer 21:49:54.784 --> 21:49:58.206 align:start position:0% so what are forensics and computer forensics<21:49:55.552> the<21:49:55.976> First<21:49:56.160> Responders<21:49:56.824> job 21:49:58.206 --> 21:49:58.216 align:start position:0% forensics the First Responders job 21:49:58.216 --> 21:50:01.070 align:start position:0% forensics the First Responders job electronic<21:49:59.216> discovery 21:50:01.070 --> 21:50:01.080 align:start position:0% electronic discovery 21:50:01.080 --> 21:50:03.350 align:start position:0% electronic discovery chain<21:50:01.680> of<21:50:01.976> custody 21:50:03.350 --> 21:50:03.360 align:start position:0% chain of custody 21:50:03.360 --> 21:50:07.246 align:start position:0% chain of custody legal<21:50:04.080> holds<21:50:04.824> securing<21:50:05.824> the<21:50:06.000> crime<21:50:06.240> scene 21:50:07.246 --> 21:50:07.256 align:start position:0% legal holds securing the crime scene 21:50:07.256 --> 21:50:09.774 align:start position:0% legal holds securing the crime scene high<21:50:07.744> level<21:50:07.920> View 21:50:09.774 --> 21:50:09.784 align:start position:0% high level View 21:50:09.784 --> 21:50:12.414 align:start position:0% high level View some<21:50:10.192> steps<21:50:10.552> in<21:50:10.744> basic<21:50:11.160> forensic<21:50:11.872> process 21:50:12.414 --> 21:50:12.424 align:start position:0% some steps in basic forensic process 21:50:12.424 --> 21:50:14.710 align:start position:0% some steps in basic forensic process including<21:50:13.080> collection<21:50:13.440> examination 21:50:14.710 --> 21:50:14.720 align:start position:0% including collection examination 21:50:14.720 --> 21:50:17.390 align:start position:0% including collection examination analysis<21:50:15.720> and<21:50:15.960> Reporting 21:50:17.390 --> 21:50:17.400 align:start position:0% analysis and Reporting 21:50:17.400 --> 21:50:19.430 align:start position:0% analysis and Reporting so<21:50:17.824> what<21:50:18.000> is<21:50:18.176> forensics<21:50:18.784> or<21:50:19.080> what<21:50:19.320> are 21:50:19.430 --> 21:50:19.440 align:start position:0% so what is forensics or what are 21:50:19.440 --> 21:50:22.734 align:start position:0% so what is forensics or what are forensics<21:50:20.240> is<21:50:21.240> the<21:50:21.656> scientific<21:50:22.016> methods<21:50:22.552> and 21:50:22.734 --> 21:50:22.744 align:start position:0% forensics is the scientific methods and 21:50:22.744 --> 21:50:25.542 align:start position:0% forensics is the scientific methods and techniques<21:50:23.216> for<21:50:23.464> collecting<21:50:24.320> analyzing<21:50:25.320> and 21:50:25.542 --> 21:50:25.552 align:start position:0% techniques for collecting analyzing and 21:50:25.552 --> 21:50:27.286 align:start position:0% techniques for collecting analyzing and preserving<21:50:26.040> evidence<21:50:26.464> that's<21:50:26.872> the 21:50:27.286 --> 21:50:27.296 align:start position:0% preserving evidence that's the 21:50:27.296 --> 21:50:29.862 align:start position:0% preserving evidence that's the definition 21:50:29.862 --> 21:50:29.872 align:start position:0% definition 21:50:29.872 --> 21:50:31.966 align:start position:0% definition can<21:50:30.480> be<21:50:30.656> used<21:50:30.784> in<21:50:30.960> the<21:50:31.080> court<21:50:31.256> of<21:50:31.504> law<21:50:31.616> and<21:50:31.856> if 21:50:31.966 --> 21:50:31.976 align:start position:0% can be used in the court of law and if 21:50:31.976 --> 21:50:33.350 align:start position:0% can be used in the court of law and if anything's<21:50:32.464> going<21:50:32.576> to<21:50:32.576> be<21:50:32.640> used<21:50:32.760> in<21:50:32.936> a<21:50:33.056> quarter 21:50:33.350 --> 21:50:33.360 align:start position:0% anything's going to be used in a quarter 21:50:33.360 --> 21:50:35.630 align:start position:0% anything's going to be used in a quarter law<21:50:33.536> it<21:50:33.832> normally<21:50:34.080> has<21:50:34.256> to<21:50:34.376> follow<21:50:34.552> a<21:50:35.512> certain 21:50:35.630 --> 21:50:35.640 align:start position:0% law it normally has to follow a certain 21:50:35.640 --> 21:50:38.390 align:start position:0% law it normally has to follow a certain amount<21:50:36.000> of<21:50:36.536> um<21:50:36.536> procedures<21:50:37.320> in<21:50:37.920> order<21:50:38.040> to 21:50:38.390 --> 21:50:38.400 align:start position:0% amount of um procedures in order to 21:50:38.400 --> 21:50:41.502 align:start position:0% amount of um procedures in order to qualify<21:50:38.872> as<21:50:39.176> evidence<21:50:39.536> as<21:50:39.896> we'll<21:50:40.080> see 21:50:41.502 --> 21:50:41.512 align:start position:0% qualify as evidence as we'll see 21:50:41.512 --> 21:50:45.110 align:start position:0% qualify as evidence as we'll see the<21:50:42.600> um<21:50:42.656> computer<21:50:43.016> forensics<21:50:43.800> U.S<21:50:44.464> government 21:50:45.110 --> 21:50:45.120 align:start position:0% the um computer forensics U.S government 21:50:45.120 --> 21:50:47.990 align:start position:0% the um computer forensics U.S government organization<21:50:45.832> states<21:50:46.320> are<21:50:46.680> following 21:50:47.990 --> 21:50:48.000 align:start position:0% organization states are following 21:50:48.000 --> 21:50:50.206 align:start position:0% organization states are following computer<21:50:48.600> forensics<21:50:49.256> is<21:50:49.552> defined<21:50:49.920> as<21:50:50.040> the 21:50:50.206 --> 21:50:50.216 align:start position:0% computer forensics is defined as the 21:50:50.216 --> 21:50:52.006 align:start position:0% computer forensics is defined as the discipline<21:50:50.576> that<21:50:50.824> combines<21:50:51.176> elements<21:50:51.720> of<21:50:51.832> law 21:50:52.006 --> 21:50:52.016 align:start position:0% discipline that combines elements of law 21:50:52.016 --> 21:50:54.110 align:start position:0% discipline that combines elements of law on<21:50:52.256> computer<21:50:52.496> science<21:50:52.920> to<21:50:53.576> collect<21:50:53.936> and 21:50:54.110 --> 21:50:54.120 align:start position:0% on computer science to collect and 21:50:54.120 --> 21:50:56.150 align:start position:0% on computer science to collect and analyze<21:50:54.656> data<21:50:54.960> from<21:50:55.144> computer<21:50:55.440> systems 21:50:56.150 --> 21:50:56.160 align:start position:0% analyze data from computer systems 21:50:56.160 --> 21:50:58.790 align:start position:0% analyze data from computer systems networks<21:50:56.760> Wireless<21:50:57.656> comms<21:50:58.440> and<21:50:58.616> storage 21:50:58.790 --> 21:50:58.800 align:start position:0% networks Wireless comms and storage 21:50:58.800 --> 21:51:01.006 align:start position:0% networks Wireless comms and storage devices<21:50:59.400> in<21:50:59.872> a<21:51:00.000> way<21:51:00.120> that's<21:51:00.296> admissible<21:51:00.784> as 21:51:01.006 --> 21:51:01.016 align:start position:0% devices in a way that's admissible as 21:51:01.016 --> 21:51:02.862 align:start position:0% devices in a way that's admissible as evidence<21:51:01.320> in<21:51:01.616> accord<21:51:01.744> to<21:51:02.104> law 21:51:02.862 --> 21:51:02.872 align:start position:0% evidence in accord to law 21:51:02.872 --> 21:51:04.846 align:start position:0% evidence in accord to law and<21:51:03.360> it<21:51:03.536> all<21:51:03.600> hinges<21:51:03.960> on<21:51:04.144> that<21:51:04.256> last<21:51:04.440> sentence 21:51:04.846 --> 21:51:04.856 align:start position:0% and it all hinges on that last sentence 21:51:04.856 --> 21:51:07.430 align:start position:0% and it all hinges on that last sentence really<21:51:05.104> it<21:51:05.400> has<21:51:05.512> to<21:51:05.696> be<21:51:05.824> admissible<21:51:06.424> and<21:51:07.256> we'll 21:51:07.430 --> 21:51:07.440 align:start position:0% really it has to be admissible and we'll 21:51:07.440 --> 21:51:10.310 align:start position:0% really it has to be admissible and we'll go<21:51:07.616> into<21:51:07.744> the<21:51:08.216> chain<21:51:08.336> custody<21:51:08.936> in<21:51:09.176> a<21:51:09.360> bit<21:51:09.424> this 21:51:10.310 --> 21:51:10.320 align:start position:0% go into the chain custody in a bit this 21:51:10.320 --> 21:51:11.750 align:start position:0% go into the chain custody in a bit this uh<21:51:10.496> when<21:51:10.744> I<21:51:10.856> worked<21:51:11.160> in<21:51:11.216> the<21:51:11.336> police<21:51:11.464> it 21:51:11.750 --> 21:51:11.760 align:start position:0% uh when I worked in the police it 21:51:11.760 --> 21:51:14.270 align:start position:0% uh when I worked in the police it applied<21:51:12.120> to<21:51:12.296> physical<21:51:12.600> evidence<21:51:13.144> in<21:51:13.920> as<21:51:14.104> much 21:51:14.270 --> 21:51:14.280 align:start position:0% applied to physical evidence in as much 21:51:14.280 --> 21:51:15.950 align:start position:0% applied to physical evidence in as much as<21:51:14.400> we<21:51:14.576> had<21:51:14.696> to<21:51:14.872> know 21:51:15.950 --> 21:51:15.960 align:start position:0% as we had to know 21:51:15.960 --> 21:51:18.710 align:start position:0% as we had to know who<21:51:16.616> first<21:51:16.800> sees<21:51:17.216> the<21:51:17.336> evidence<21:51:17.640> who<21:51:18.424> do<21:51:18.600> they 21:51:18.710 --> 21:51:18.720 align:start position:0% who first sees the evidence who do they 21:51:18.720 --> 21:51:21.286 align:start position:0% who first sees the evidence who do they hand<21:51:18.960> it<21:51:19.192> to<21:51:19.440> who<21:51:20.216> examined<21:51:20.696> it<21:51:20.824> after<21:51:21.000> that 21:51:21.286 --> 21:51:21.296 align:start position:0% hand it to who examined it after that 21:51:21.296 --> 21:51:23.326 align:start position:0% hand it to who examined it after that and<21:51:21.536> so<21:51:21.720> on<21:51:21.896> and<21:51:22.496> we<21:51:22.680> have<21:51:22.856> to<21:51:22.976> have<21:51:23.104> this 21:51:23.326 --> 21:51:23.336 align:start position:0% and so on and we have to have this 21:51:23.336 --> 21:51:24.710 align:start position:0% and so on and we have to have this continuity 21:51:24.710 --> 21:51:24.720 align:start position:0% continuity 21:51:24.720 --> 21:51:26.926 align:start position:0% continuity and<21:51:25.192> it's<21:51:25.320> the<21:51:25.504> same<21:51:25.680> in<21:51:25.920> regards<21:51:26.280> of<21:51:26.576> computer 21:51:26.926 --> 21:51:26.936 align:start position:0% and it's the same in regards of computer 21:51:26.936 --> 21:51:30.166 align:start position:0% and it's the same in regards of computer forensics 21:51:30.166 --> 21:51:30.176 align:start position:0% 21:51:30.176 --> 21:51:32.270 align:start position:0% computer<21:51:30.784> forensics<21:51:31.376> help<21:51:31.616> organizations 21:51:32.270 --> 21:51:32.280 align:start position:0% computer forensics help organizations 21:51:32.280 --> 21:51:34.310 align:start position:0% computer forensics help organizations deal<21:51:32.576> with<21:51:32.824> security<21:51:33.000> incidents<21:51:33.896> that<21:51:34.080> have 21:51:34.310 --> 21:51:34.320 align:start position:0% deal with security incidents that have 21:51:34.320 --> 21:51:36.886 align:start position:0% deal with security incidents that have an<21:51:34.496> adverse<21:51:34.856> impact<21:51:35.104> on<21:51:35.280> their<21:51:35.464> business<21:51:35.896> so 21:51:36.886 --> 21:51:36.896 align:start position:0% an adverse impact on their business so 21:51:36.896 --> 21:51:38.686 align:start position:0% an adverse impact on their business so it<21:51:37.192> could<21:51:37.320> be<21:51:37.376> for<21:51:37.680> internal<21:51:38.040> investigations 21:51:38.686 --> 21:51:38.696 align:start position:0% it could be for internal investigations 21:51:38.696 --> 21:51:40.134 align:start position:0% it could be for internal investigations also 21:51:40.134 --> 21:51:40.144 align:start position:0% also 21:51:40.144 --> 21:51:42.350 align:start position:0% also security<21:51:40.920> incidents<21:51:41.640> are<21:51:41.824> events<21:51:42.240> that 21:51:42.350 --> 21:51:42.360 align:start position:0% security incidents are events that 21:51:42.360 --> 21:51:44.206 align:start position:0% security incidents are events that violate<21:51:42.720> the<21:51:42.832> security<21:51:43.080> policies<21:51:43.800> of<21:51:44.040> the 21:51:44.206 --> 21:51:44.216 align:start position:0% violate the security policies of the 21:51:44.216 --> 21:51:46.246 align:start position:0% violate the security policies of the organization<21:51:44.824> so<21:51:45.424> obviously<21:51:45.720> some<21:51:46.016> things 21:51:46.246 --> 21:51:46.256 align:start position:0% organization so obviously some things 21:51:46.256 --> 21:51:48.950 align:start position:0% organization so obviously some things may<21:51:46.552> not<21:51:46.680> be<21:51:46.856> a<21:51:47.040> crime<21:51:47.400> however<21:51:48.360> sharing 21:51:48.950 --> 21:51:48.960 align:start position:0% may not be a crime however sharing 21:51:48.960 --> 21:51:51.822 align:start position:0% may not be a crime however sharing sensitive<21:51:49.504> information<21:51:49.856> as<21:51:50.760> regards<21:51:51.240> of<21:51:51.480> your 21:51:51.822 --> 21:51:51.832 align:start position:0% sensitive information as regards of your 21:51:51.832 --> 21:51:54.822 align:start position:0% sensitive information as regards of your company<21:51:52.336> or<21:51:53.336> take<21:51:53.640> over<21:51:53.824> bids<21:51:54.424> or<21:51:54.720> other 21:51:54.822 --> 21:51:54.832 align:start position:0% company or take over bids or other 21:51:54.832 --> 21:51:56.926 align:start position:0% company or take over bids or other information<21:51:55.192> about<21:51:55.744> people<21:51:56.104> at<21:51:56.400> work<21:51:56.640> there 21:51:56.926 --> 21:51:56.936 align:start position:0% information about people at work there 21:51:56.936 --> 21:51:59.862 align:start position:0% information about people at work there can<21:51:57.896> be<21:51:58.080> a<21:51:58.256> breach<21:51:58.552> even<21:51:58.800> though<21:51:58.976> it<21:51:59.160> hasn't<21:51:59.872> um 21:51:59.862 --> 21:51:59.872 align:start position:0% can be a breach even though it hasn't um 21:51:59.872 --> 21:52:02.030 align:start position:0% can be a breach even though it hasn't um it<21:52:00.480> isn't<21:52:00.720> officially<21:52:01.080> a<21:52:01.320> crime<21:52:01.616> for<21:52:01.856> whatever 21:52:02.030 --> 21:52:02.040 align:start position:0% it isn't officially a crime for whatever 21:52:02.040 --> 21:52:03.414 align:start position:0% it isn't officially a crime for whatever reason 21:52:03.414 --> 21:52:03.424 align:start position:0% reason 21:52:03.424 --> 21:52:06.710 align:start position:0% reason here's<21:52:04.144> a<21:52:04.376> screen<21:52:04.616> grab<21:52:05.160> if<21:52:05.400> you<21:52:05.512> search<21:52:05.760> for 21:52:06.710 --> 21:52:06.720 align:start position:0% here's a screen grab if you search for 21:52:06.720 --> 21:52:09.950 align:start position:0% here's a screen grab if you search for um computer<21:52:06.960> forensic<21:52:07.680> certifications<21:52:08.960> the 21:52:09.950 --> 21:52:09.960 align:start position:0% um computer forensic certifications the 21:52:09.960 --> 21:52:14.094 align:start position:0% um computer forensic certifications the website<21:52:10.256> Tom's<21:52:10.800> it<21:52:11.040> pro<21:52:11.576> has<21:52:12.424> listed<21:52:12.896> what<21:52:13.616> uh 21:52:14.094 --> 21:52:14.104 align:start position:0% website Tom's it pro has listed what uh 21:52:14.104 --> 21:52:17.502 align:start position:0% website Tom's it pro has listed what uh for<21:52:14.400> 2017<21:52:14.872> are<21:52:15.536> the<21:52:15.832> top<21:52:16.080> five 21:52:17.502 --> 21:52:17.512 align:start position:0% for 2017 are the top five 21:52:17.512 --> 21:52:20.990 align:start position:0% for 2017 are the top five uh<21:52:18.240> computer<21:52:18.480> forensic<21:52:19.144> qualifications<21:52:20.000> the 21:52:20.990 --> 21:52:21.000 align:start position:0% uh computer forensic qualifications the 21:52:21.000 --> 21:52:23.326 align:start position:0% uh computer forensic qualifications the certified<21:52:21.424> computer<21:52:21.784> examiner<21:52:22.680> in<21:52:23.104> case 21:52:23.326 --> 21:52:23.336 align:start position:0% certified computer examiner in case 21:52:23.336 --> 21:52:27.046 align:start position:0% certified computer examiner in case which<21:52:23.936> is<21:52:24.176> a<21:52:24.960> um<21:52:25.016> vendor<21:52:25.920> specific<21:52:26.640> the<21:52:26.936> other 21:52:27.046 --> 21:52:27.056 align:start position:0% which is a um vendor specific the other 21:52:27.056 --> 21:52:28.846 align:start position:0% which is a um vendor specific the other ones<21:52:27.240> are<21:52:27.424> vendor<21:52:27.720> neutral<21:52:28.080> I<21:52:28.256> think 21:52:28.846 --> 21:52:28.856 align:start position:0% ones are vendor neutral I think 21:52:28.856 --> 21:52:32.326 align:start position:0% ones are vendor neutral I think certified<21:52:29.640> forensic<21:52:30.360> computer<21:52:30.536> examiner 21:52:32.326 --> 21:52:32.336 align:start position:0% certified forensic computer examiner 21:52:32.336 --> 21:52:33.606 align:start position:0% certified forensic computer examiner um 21:52:33.606 --> 21:52:33.616 align:start position:0% um 21:52:33.616 --> 21:52:37.006 align:start position:0% um gcfa<21:52:34.616> and<21:52:34.920> gcfe 21:52:37.006 --> 21:52:37.016 align:start position:0% gcfa and gcfe 21:52:37.016 --> 21:52:38.926 align:start position:0% gcfa and gcfe I'm<21:52:37.440> not<21:52:37.616> sure<21:52:37.744> that<21:52:37.976> stands<21:52:38.336> for<21:52:38.464> cyber 21:52:38.926 --> 21:52:38.936 align:start position:0% I'm not sure that stands for cyber 21:52:38.936 --> 21:52:41.454 align:start position:0% I'm not sure that stands for cyber security<21:52:39.120> forensics<21:52:39.896> so<21:52:41.040> um<21:52:41.040> if<21:52:41.336> you're 21:52:41.454 --> 21:52:41.464 align:start position:0% security forensics so um if you're 21:52:41.464 --> 21:52:43.670 align:start position:0% security forensics so um if you're interested<21:52:41.824> in<21:52:42.056> this<21:52:42.240> particular<21:52:42.536> field<21:52:42.896> then 21:52:43.670 --> 21:52:43.680 align:start position:0% interested in this particular field then 21:52:43.680 --> 21:52:45.110 align:start position:0% interested in this particular field then there's<21:52:43.920> certainly<21:52:44.216> other<21:52:44.336> certifications 21:52:45.110 --> 21:52:45.120 align:start position:0% there's certainly other certifications 21:52:45.120 --> 21:52:46.966 align:start position:0% there's certainly other certifications you<21:52:45.600> can<21:52:45.656> follow 21:52:46.966 --> 21:52:46.976 align:start position:0% you can follow 21:52:46.976 --> 21:52:50.150 align:start position:0% you can follow uh<21:52:47.576> just<21:52:47.760> do<21:52:47.936> some<21:52:48.120> research<21:52:48.536> and<21:52:48.720> see<21:52:48.960> what<21:52:49.256> uh 21:52:50.150 --> 21:52:50.160 align:start position:0% uh just do some research and see what uh 21:52:50.160 --> 21:52:52.670 align:start position:0% uh just do some research and see what uh the<21:52:50.936> employment<21:52:51.360> prospects<21:52:51.960> are 21:52:52.670 --> 21:52:52.680 align:start position:0% the employment prospects are 21:52:52.680 --> 21:52:54.774 align:start position:0% the employment prospects are so<21:52:53.216> examples<21:52:53.576> of<21:52:53.760> security<21:52:54.056> incidents 21:52:54.774 --> 21:52:54.784 align:start position:0% so examples of security incidents 21:52:54.784 --> 21:52:57.710 align:start position:0% so examples of security incidents include<21:52:55.256> unauthorized<21:52:56.104> access<21:52:56.280> to<21:52:56.640> data 21:52:57.710 --> 21:52:57.720 align:start position:0% include unauthorized access to data 21:52:57.720 --> 21:52:59.990 align:start position:0% include unauthorized access to data attacks<21:52:58.440> through<21:52:58.552> malware<21:52:59.040> or<21:52:59.336> denial<21:52:59.824> of 21:52:59.990 --> 21:53:00.000 align:start position:0% attacks through malware or denial of 21:53:00.000 --> 21:53:01.494 align:start position:0% attacks through malware or denial of service 21:53:01.494 --> 21:53:01.504 align:start position:0% service 21:53:01.504 --> 21:53:03.110 align:start position:0% service it's<21:53:01.856> important<21:53:02.160> to<21:53:02.336> understand<21:53:02.464> the 21:53:03.110 --> 21:53:03.120 align:start position:0% it's important to understand the 21:53:03.120 --> 21:53:05.150 align:start position:0% it's important to understand the technical<21:53:03.600> and<21:53:03.784> legal<21:53:04.144> aspects<21:53:04.616> in<21:53:04.744> order<21:53:04.920> to 21:53:05.150 --> 21:53:05.160 align:start position:0% technical and legal aspects in order to 21:53:05.160 --> 21:53:08.390 align:start position:0% technical and legal aspects in order to gather<21:53:05.336> information<21:53:06.080> because<21:53:07.080> you<21:53:07.976> could<21:53:08.216> be 21:53:08.390 --> 21:53:08.400 align:start position:0% gather information because you could be 21:53:08.400 --> 21:53:10.734 align:start position:0% gather information because you could be will<21:53:08.936> cover<21:53:09.296> first<21:53:09.656> responder<21:53:10.192> in<21:53:10.320> a<21:53:10.440> bit<21:53:10.552> but 21:53:10.734 --> 21:53:10.744 align:start position:0% will cover first responder in a bit but 21:53:10.744 --> 21:53:12.950 align:start position:0% will cover first responder in a bit but you<21:53:10.920> that<21:53:11.280> could<21:53:11.400> be<21:53:11.576> you 21:53:12.950 --> 21:53:12.960 align:start position:0% you that could be you 21:53:12.960 --> 21:53:15.350 align:start position:0% you that could be you could<21:53:13.504> be<21:53:13.616> contacted<21:53:14.160> by<21:53:14.464> a<21:53:14.640> law<21:53:14.824> enforcement 21:53:15.350 --> 21:53:15.360 align:start position:0% could be contacted by a law enforcement 21:53:15.360 --> 21:53:20.502 align:start position:0% could be contacted by a law enforcement agency<21:53:16.280> told<21:53:17.280> us<21:53:17.512> some<21:53:17.824> sort<21:53:18.000> of<21:53:18.480> um<21:53:18.480> data<21:53:19.856> or 21:53:20.502 --> 21:53:20.512 align:start position:0% agency told us some sort of um data or 21:53:20.512 --> 21:53:23.566 align:start position:0% agency told us some sort of um data or even<21:53:20.640> their<21:53:21.000> Hardware<21:53:21.320> that's<21:53:22.320> been<21:53:22.856> involved 21:53:23.566 --> 21:53:23.576 align:start position:0% even their Hardware that's been involved 21:53:23.576 --> 21:53:25.430 align:start position:0% even their Hardware that's been involved in<21:53:23.640> the<21:53:23.824> commission<21:53:24.056> of<21:53:24.296> a<21:53:24.424> crime<21:53:24.720> and<21:53:25.256> be 21:53:25.430 --> 21:53:25.440 align:start position:0% in the commission of a crime and be 21:53:25.440 --> 21:53:27.950 align:start position:0% in the commission of a crime and be asked<21:53:25.680> to<21:53:25.856> take<21:53:26.160> certain<21:53:26.824> steps<21:53:27.296> or<21:53:27.480> be<21:53:27.656> served 21:53:27.950 --> 21:53:27.960 align:start position:0% asked to take certain steps or be served 21:53:27.960 --> 21:53:30.646 align:start position:0% asked to take certain steps or be served with<21:53:28.016> the<21:53:28.192> legal<21:53:28.496> notice<21:53:29.464> for<21:53:30.000> criminal<21:53:30.424> or 21:53:30.646 --> 21:53:30.656 align:start position:0% with the legal notice for criminal or 21:53:30.656 --> 21:53:32.094 align:start position:0% with the legal notice for criminal or civil<21:53:31.016> court 21:53:32.094 --> 21:53:32.104 align:start position:0% civil court 21:53:32.104 --> 21:53:34.246 align:start position:0% civil court the<21:53:32.640> risk<21:53:32.936> is<21:53:33.056> if<21:53:33.424> you<21:53:33.536> don't<21:53:33.656> have<21:53:33.832> these 21:53:34.246 --> 21:53:34.256 align:start position:0% the risk is if you don't have these 21:53:34.256 --> 21:53:37.366 align:start position:0% the risk is if you don't have these forensic<21:53:34.976> processes<21:53:35.576> you<21:53:36.000> could<21:53:36.056> lose<21:53:36.424> your 21:53:37.366 --> 21:53:37.376 align:start position:0% forensic processes you could lose your 21:53:37.376 --> 21:53:39.166 align:start position:0% forensic processes you could lose your um evidence<21:53:37.800> or<21:53:38.576> it<21:53:38.760> could<21:53:38.872> become 21:53:39.166 --> 21:53:39.176 align:start position:0% um evidence or it could become 21:53:39.176 --> 21:53:40.686 align:start position:0% um evidence or it could become inadmissible<21:53:39.832> which<21:53:40.080> can<21:53:40.320> be<21:53:40.440> quite 21:53:40.686 --> 21:53:40.696 align:start position:0% inadmissible which can be quite 21:53:40.696 --> 21:53:42.646 align:start position:0% inadmissible which can be quite embarrassing<21:53:41.696> because 21:53:42.646 --> 21:53:42.656 align:start position:0% embarrassing because 21:53:42.656 --> 21:53:45.286 align:start position:0% embarrassing because um<21:53:42.720> it<21:53:43.144> could<21:53:43.256> I<21:53:43.504> mean<21:53:43.616> the<21:53:43.800> cases<21:53:44.040> last 21:53:45.286 --> 21:53:45.296 align:start position:0% um it could I mean the cases last 21:53:45.296 --> 21:53:47.990 align:start position:0% um it could I mean the cases last the<21:53:46.080> security<21:53:46.256> professional<21:53:47.040> needs<21:53:47.760> to<21:53:47.872> know 21:53:47.990 --> 21:53:48.000 align:start position:0% the security professional needs to know 21:53:48.000 --> 21:53:49.670 align:start position:0% the security professional needs to know the<21:53:48.120> legal<21:53:48.424> aspects 21:53:49.670 --> 21:53:49.680 align:start position:0% the legal aspects 21:53:49.680 --> 21:53:52.134 align:start position:0% the legal aspects so<21:53:50.104> U.S<21:53:50.512> law<21:53:50.640> mandates<21:53:51.120> proper<21:53:51.600> authorization 21:53:52.134 --> 21:53:52.144 align:start position:0% so U.S law mandates proper authorization 21:53:52.144 --> 21:53:54.526 align:start position:0% so U.S law mandates proper authorization must<21:53:52.552> be<21:53:52.800> acquired<21:53:53.696> before<21:53:54.176> Security 21:53:54.526 --> 21:53:54.536 align:start position:0% must be acquired before Security 21:53:54.536 --> 21:53:56.390 align:start position:0% must be acquired before Security Professionals<21:53:55.504> can<21:53:55.744> monitor<21:53:56.104> and<21:53:56.216> gather 21:53:56.390 --> 21:53:56.400 align:start position:0% Professionals can monitor and gather 21:53:56.400 --> 21:53:58.734 align:start position:0% Professionals can monitor and gather information<21:53:56.960> so<21:53:57.960> it<21:53:58.080> depends<21:53:58.320> what<21:53:58.496> it<21:53:58.616> is 21:53:58.734 --> 21:53:58.744 align:start position:0% information so it depends what it is 21:53:58.744 --> 21:54:00.886 align:start position:0% information so it depends what it is you'd<21:53:59.104> be<21:53:59.160> certain<21:53:59.464> sort<21:53:59.824> of<21:53:59.936> court<21:54:00.120> order<21:54:00.424> or 21:54:00.886 --> 21:54:00.896 align:start position:0% you'd be certain sort of court order or 21:54:00.896 --> 21:54:02.094 align:start position:0% you'd be certain sort of court order or warrant 21:54:02.094 --> 21:54:02.104 align:start position:0% warrant 21:54:02.104 --> 21:54:05.454 align:start position:0% warrant and<21:54:02.872> in<21:54:03.120> the<21:54:03.296> form<21:54:03.480> of<21:54:03.656> a<21:54:03.896> paperwork<21:54:04.440> in<21:54:05.336> order 21:54:05.454 --> 21:54:05.464 align:start position:0% and in the form of a paperwork in order 21:54:05.464 --> 21:54:08.566 align:start position:0% and in the form of a paperwork in order to<21:54:06.176> um<21:54:06.176> take<21:54:06.480> certain<21:54:06.720> action<21:54:07.144> or<21:54:07.440> preserve<21:54:07.920> a 21:54:08.566 --> 21:54:08.576 align:start position:0% to um take certain action or preserve a 21:54:08.576 --> 21:54:10.006 align:start position:0% to um take certain action or preserve a certain<21:54:08.640> amount<21:54:08.872> of<21:54:09.056> evidence<21:54:09.360> or<21:54:09.600> hand<21:54:09.832> it 21:54:10.006 --> 21:54:10.016 align:start position:0% certain amount of evidence or hand it 21:54:10.016 --> 21:54:11.326 align:start position:0% certain amount of evidence or hand it over 21:54:11.326 --> 21:54:11.336 align:start position:0% over 21:54:11.336 --> 21:54:13.134 align:start position:0% over uh<21:54:11.824> organization<21:54:12.424> should<21:54:12.656> have<21:54:12.896> a<21:54:13.016> computer 21:54:13.134 --> 21:54:13.144 align:start position:0% uh organization should have a computer 21:54:13.144 --> 21:54:15.414 align:start position:0% uh organization should have a computer forensic<21:54:13.856> competence<21:54:14.400> established<21:54:15.056> as<21:54:15.240> part 21:54:15.414 --> 21:54:15.424 align:start position:0% forensic competence established as part 21:54:15.424 --> 21:54:19.070 align:start position:0% forensic competence established as part of<21:54:15.536> its<21:54:15.896> security<21:54:16.400> policy<21:54:17.536> and<21:54:18.536> you<21:54:18.656> may<21:54:18.896> need 21:54:19.070 --> 21:54:19.080 align:start position:0% of its security policy and you may need 21:54:19.080 --> 21:54:21.822 align:start position:0% of its security policy and you may need to<21:54:19.320> have<21:54:19.504> it<21:54:19.744> in<21:54:20.160> respect<21:54:20.512> of<21:54:20.760> having<21:54:21.056> audits 21:54:21.822 --> 21:54:21.832 align:start position:0% to have it in respect of having audits 21:54:21.832 --> 21:54:24.526 align:start position:0% to have it in respect of having audits for<21:54:22.080> compliance<21:54:22.680> or<21:54:23.400> certification<21:54:24.056> to<21:54:24.360> work 21:54:24.526 --> 21:54:24.536 align:start position:0% for compliance or certification to work 21:54:24.536 --> 21:54:26.502 align:start position:0% for compliance or certification to work with<21:54:24.832> certain<21:54:25.016> vendors<21:54:25.616> or<21:54:26.280> government 21:54:26.502 --> 21:54:26.512 align:start position:0% with certain vendors or government 21:54:26.512 --> 21:54:28.910 align:start position:0% with certain vendors or government departments 21:54:28.910 --> 21:54:28.920 align:start position:0% departments 21:54:28.920 --> 21:54:31.366 align:start position:0% departments so<21:54:29.336> the<21:54:29.512> first<21:54:29.640> responder<21:54:30.240> is<21:54:30.360> a<21:54:30.536> person<21:54:30.784> first 21:54:31.366 --> 21:54:31.376 align:start position:0% so the first responder is a person first 21:54:31.376 --> 21:54:32.926 align:start position:0% so the first responder is a person first to<21:54:31.616> be<21:54:31.744> present<21:54:32.040> on<21:54:32.216> the<21:54:32.336> scene<21:54:32.464> after<21:54:32.760> the 21:54:32.926 --> 21:54:32.936 align:start position:0% to be present on the scene after the 21:54:32.936 --> 21:54:34.846 align:start position:0% to be present on the scene after the occurrence<21:54:33.296> of<21:54:33.424> a<21:54:33.600> security<21:54:33.720> incident<21:54:34.320> which 21:54:34.846 --> 21:54:34.856 align:start position:0% occurrence of a security incident which 21:54:34.856 --> 21:54:37.670 align:start position:0% occurrence of a security incident which if<21:54:35.040> you're<21:54:35.216> the<21:54:35.464> duty<21:54:35.824> network<21:54:36.536> engineer<21:54:37.192> then 21:54:37.670 --> 21:54:37.680 align:start position:0% if you're the duty network engineer then 21:54:37.680 --> 21:54:40.542 align:start position:0% if you're the duty network engineer then that<21:54:37.920> could<21:54:38.104> well<21:54:38.280> mean<21:54:38.576> you 21:54:40.542 --> 21:54:40.552 align:start position:0% that could well mean you 21:54:40.552 --> 21:54:42.110 align:start position:0% that could well mean you um you<21:54:40.800> control<21:54:40.920> the<21:54:41.216> damage<21:54:41.512> caused<21:54:41.872> by<21:54:42.000> the 21:54:42.110 --> 21:54:42.120 align:start position:0% um you control the damage caused by the 21:54:42.120 --> 21:54:44.150 align:start position:0% um you control the damage caused by the incident<21:54:42.480> and<21:54:43.016> ensure<21:54:43.504> none<21:54:43.680> of<21:54:43.856> the<21:54:43.920> evidence 21:54:44.150 --> 21:54:44.160 align:start position:0% incident and ensure none of the evidence 21:54:44.160 --> 21:54:47.206 align:start position:0% incident and ensure none of the evidence is<21:54:44.464> spoiled<21:54:45.000> to<21:54:45.656> the<21:54:45.896> best<21:54:45.960> durability 21:54:47.206 --> 21:54:47.216 align:start position:0% is spoiled to the best durability 21:54:47.216 --> 21:54:49.430 align:start position:0% is spoiled to the best durability first<21:54:47.760> responder<21:54:48.296> initiates<21:54:48.784> the<21:54:49.016> escalation 21:54:49.430 --> 21:54:49.440 align:start position:0% first responder initiates the escalation 21:54:49.440 --> 21:54:52.734 align:start position:0% first responder initiates the escalation procedure<21:54:50.104> so<21:54:50.872> you'd<21:54:51.296> inform<21:54:52.144> um 21:54:52.734 --> 21:54:52.744 align:start position:0% procedure so you'd inform um 21:54:52.744 --> 21:54:54.822 align:start position:0% procedure so you'd inform um the<21:54:53.216> legal<21:54:53.512> authorities<21:54:53.936> whoever<21:54:54.360> that<21:54:54.600> may 21:54:54.822 --> 21:54:54.832 align:start position:0% the legal authorities whoever that may 21:54:54.832 --> 21:54:57.950 align:start position:0% the legal authorities whoever that may be<21:54:55.016> and<21:54:56.512> um<21:54:56.512> internal<21:54:57.240> company<21:54:57.536> management 21:54:57.950 --> 21:54:57.960 align:start position:0% be and um internal company management 21:54:57.960 --> 21:55:01.630 align:start position:0% be and um internal company management and<21:54:58.440> bosses 21:55:01.630 --> 21:55:01.640 align:start position:0% 21:55:01.640 --> 21:55:03.886 align:start position:0% e-discovery<21:55:02.640> or<21:55:02.872> electronic<21:55:03.424> Discovery 21:55:03.886 --> 21:55:03.896 align:start position:0% e-discovery or electronic Discovery 21:55:03.896 --> 21:55:06.350 align:start position:0% e-discovery or electronic Discovery refers<21:55:04.256> to<21:55:04.440> a<21:55:04.616> pre-trial<21:55:05.040> procedure<21:55:05.640> where 21:55:06.350 --> 21:55:06.360 align:start position:0% refers to a pre-trial procedure where 21:55:06.360 --> 21:55:08.566 align:start position:0% refers to a pre-trial procedure where the<21:55:06.536> parties<21:55:06.960> exchange<21:55:07.504> the<21:55:07.856> electronically 21:55:08.566 --> 21:55:08.576 align:start position:0% the parties exchange the electronically 21:55:08.576 --> 21:55:10.790 align:start position:0% the parties exchange the electronically installed<21:55:09.000> information<21:55:09.440> this<21:55:10.440> could<21:55:10.616> be 21:55:10.790 --> 21:55:10.800 align:start position:0% installed information this could be 21:55:10.800 --> 21:55:13.542 align:start position:0% installed information this could be emails<21:55:11.696> exchanged<21:55:12.424> between<21:55:12.784> different 21:55:13.542 --> 21:55:13.552 align:start position:0% emails exchanged between different 21:55:13.552 --> 21:55:17.094 align:start position:0% emails exchanged between different employees<21:55:14.216> it<21:55:15.000> could<21:55:15.120> be<21:55:15.296> spreadsheets<21:55:16.144> a 21:55:17.094 --> 21:55:17.104 align:start position:0% employees it could be spreadsheets a 21:55:17.104 --> 21:55:18.886 align:start position:0% employees it could be spreadsheets a video<21:55:17.400> conference<21:55:18.000> calls<21:55:18.424> that<21:55:18.536> have<21:55:18.720> been 21:55:18.886 --> 21:55:18.896 align:start position:0% video conference calls that have been 21:55:18.896 --> 21:55:20.750 align:start position:0% video conference calls that have been recorded 21:55:20.750 --> 21:55:20.760 align:start position:0% recorded 21:55:20.760 --> 21:55:22.670 align:start position:0% recorded um anything<21:55:21.056> electronically<21:55:21.896> really<21:55:22.192> that's 21:55:22.670 --> 21:55:22.680 align:start position:0% um anything electronically really that's 21:55:22.680 --> 21:55:24.822 align:start position:0% um anything electronically really that's pertinent<21:55:23.336> to<21:55:23.464> the<21:55:23.640> case 21:55:24.822 --> 21:55:24.832 align:start position:0% pertinent to the case 21:55:24.832 --> 21:55:26.630 align:start position:0% pertinent to the case and<21:55:25.192> it's<21:55:25.320> different<21:55:25.552> from<21:55:25.800> paper<21:55:25.976> documents 21:55:26.630 --> 21:55:26.640 align:start position:0% and it's different from paper documents 21:55:26.640 --> 21:55:29.094 align:start position:0% and it's different from paper documents because<21:55:26.824> it's<21:55:27.056> not<21:55:27.296> actually<21:55:27.424> tangible 21:55:29.094 --> 21:55:29.104 align:start position:0% because it's not actually tangible 21:55:29.104 --> 21:55:31.246 align:start position:0% because it's not actually tangible um<21:55:29.160> and<21:55:29.400> it<21:55:29.576> could<21:55:29.696> obviously<21:55:30.240> be<21:55:30.784> saved<21:55:31.144> in 21:55:31.246 --> 21:55:31.256 align:start position:0% um and it could obviously be saved in 21:55:31.256 --> 21:55:33.286 align:start position:0% um and it could obviously be saved in one<21:55:31.504> place<21:55:31.744> or<21:55:32.104> saved<21:55:32.512> in<21:55:32.760> multiple<21:55:33.000> places 21:55:33.286 --> 21:55:33.296 align:start position:0% one place or saved in multiple places 21:55:33.296 --> 21:55:35.150 align:start position:0% one place or saved in multiple places over<21:55:33.656> the<21:55:33.896> cloud<21:55:34.080> and<21:55:34.680> have<21:55:34.920> different 21:55:35.150 --> 21:55:35.160 align:start position:0% over the cloud and have different 21:55:35.160 --> 21:55:37.134 align:start position:0% over the cloud and have different versions<21:55:35.640> of<21:55:35.936> it 21:55:37.134 --> 21:55:37.144 align:start position:0% versions of it 21:55:37.144 --> 21:55:40.246 align:start position:0% versions of it some<21:55:37.552> examples<21:55:38.040> for<21:55:38.720> electronically<21:55:39.720> stalled 21:55:40.246 --> 21:55:40.256 align:start position:0% some examples for electronically stalled 21:55:40.256 --> 21:55:43.966 align:start position:0% some examples for electronically stalled information<21:55:40.440> are<21:55:41.160> as<21:55:41.400> follows 21:55:43.966 --> 21:55:43.976 align:start position:0% 21:55:43.976 --> 21:55:46.006 align:start position:0% emails<21:55:44.760> voicemails<21:55:45.480> documents 21:55:46.006 --> 21:55:46.016 align:start position:0% emails voicemails documents 21:55:46.016 --> 21:55:49.006 align:start position:0% emails voicemails documents presentations<21:55:46.640> databases<21:55:47.640> websites<21:55:48.296> and<21:55:48.832> it 21:55:49.006 --> 21:55:49.016 align:start position:0% presentations databases websites and it 21:55:49.016 --> 21:55:51.950 align:start position:0% presentations databases websites and it could<21:55:49.192> be<21:55:49.760> for<21:55:50.760> a<21:55:50.936> certain<21:55:51.120> period<21:55:51.480> like<21:55:51.720> a 21:55:51.950 --> 21:55:51.960 align:start position:0% could be for a certain period like a 21:55:51.960 --> 21:55:55.246 align:start position:0% could be for a certain period like a database<21:55:52.440> copy<21:55:53.400> of<21:55:53.512> a<21:55:53.640> database<21:55:54.056> from<21:55:54.600> a<21:55:55.144> month 21:55:55.246 --> 21:55:55.256 align:start position:0% database copy of a database from a month 21:55:55.256 --> 21:55:58.246 align:start position:0% database copy of a database from a month ago<21:55:55.616> or<21:55:55.920> a<21:55:56.104> year<21:55:56.280> ago<21:55:56.640> or<21:55:57.296> whatever<21:55:57.480> it 21:55:58.246 --> 21:55:58.256 align:start position:0% ago or a year ago or whatever it 21:55:58.256 --> 21:56:00.046 align:start position:0% ago or a year ago or whatever it obviously<21:55:58.680> varies 21:56:00.046 --> 21:56:00.056 align:start position:0% obviously varies 21:56:00.056 --> 21:56:02.814 align:start position:0% obviously varies the<21:56:00.600> electronic<21:56:01.192> Discovery<21:56:01.920> process<21:56:02.336> this 21:56:02.814 --> 21:56:02.824 align:start position:0% the electronic Discovery process this 21:56:02.824 --> 21:56:05.150 align:start position:0% the electronic Discovery process this involves<21:56:03.616> identifying<21:56:04.616> preserving 21:56:05.150 --> 21:56:05.160 align:start position:0% involves identifying preserving 21:56:05.160 --> 21:56:07.006 align:start position:0% involves identifying preserving collecting<21:56:05.760> processing<21:56:06.424> reviewing<21:56:06.896> and 21:56:07.006 --> 21:56:07.016 align:start position:0% collecting processing reviewing and 21:56:07.016 --> 21:56:09.590 align:start position:0% collecting processing reviewing and producing<21:56:07.552> the<21:56:08.280> document<21:56:08.576> to<21:56:08.824> the<21:56:09.056> opposing 21:56:09.590 --> 21:56:09.600 align:start position:0% producing the document to the opposing 21:56:09.600 --> 21:56:10.846 align:start position:0% producing the document to the opposing Council 21:56:10.846 --> 21:56:10.856 align:start position:0% Council 21:56:10.856 --> 21:56:12.950 align:start position:0% Council you<21:56:11.280> could<21:56:11.464> actually<21:56:11.640> have<21:56:12.000> to<21:56:12.120> produce<21:56:12.720> it 21:56:12.950 --> 21:56:12.960 align:start position:0% you could actually have to produce it 21:56:12.960 --> 21:56:15.470 align:start position:0% you could actually have to produce it for<21:56:13.144> your<21:56:13.376> own<21:56:13.552> lawyers<21:56:14.216> as<21:56:14.512> well<21:56:14.640> and<21:56:15.240> to 21:56:15.470 --> 21:56:15.480 align:start position:0% for your own lawyers as well and to 21:56:15.480 --> 21:56:18.646 align:start position:0% for your own lawyers as well and to prove<21:56:15.784> your<21:56:15.960> case 21:56:18.646 --> 21:56:18.656 align:start position:0% 21:56:18.656 --> 21:56:21.470 align:start position:0% now<21:56:19.016> the<21:56:19.144> gender<21:56:19.320> custody<21:56:19.856> is<21:56:20.040> a<21:56:20.280> document<21:56:20.576> and 21:56:21.470 --> 21:56:21.480 align:start position:0% now the gender custody is a document and 21:56:21.480 --> 21:56:23.862 align:start position:0% now the gender custody is a document and you<21:56:21.784> could<21:56:21.832> have<21:56:22.016> evidence<21:56:22.376> labels<21:56:23.040> if<21:56:23.464> it's<21:56:23.576> a 21:56:23.862 --> 21:56:23.872 align:start position:0% you could have evidence labels if it's a 21:56:23.872 --> 21:56:26.630 align:start position:0% you could have evidence labels if it's a physical<21:56:24.360> hard<21:56:24.784> drive<21:56:24.960> for<21:56:25.320> example<21:56:25.616> and<21:56:26.512> this 21:56:26.630 --> 21:56:26.640 align:start position:0% physical hard drive for example and this 21:56:26.640 --> 21:56:28.310 align:start position:0% physical hard drive for example and this would<21:56:26.824> include<21:56:27.056> the<21:56:27.240> person<21:56:27.480> who<21:56:27.784> seized<21:56:28.256> it 21:56:28.310 --> 21:56:28.320 align:start position:0% would include the person who seized it 21:56:28.320 --> 21:56:30.590 align:start position:0% would include the person who seized it who<21:56:28.616> they<21:56:28.744> handed<21:56:29.104> it<21:56:29.216> to 21:56:30.590 --> 21:56:30.600 align:start position:0% who they handed it to 21:56:30.600 --> 21:56:31.966 align:start position:0% who they handed it to um I'll<21:56:30.720> go<21:56:30.896> into<21:56:31.016> some<21:56:31.256> of<21:56:31.376> the<21:56:31.504> stuff<21:56:31.616> on<21:56:31.856> the 21:56:31.966 --> 21:56:31.976 align:start position:0% um I'll go into some of the stuff on the 21:56:31.976 --> 21:56:33.470 align:start position:0% um I'll go into some of the stuff on the next<21:56:32.104> slide 21:56:33.470 --> 21:56:33.480 align:start position:0% next slide 21:56:33.480 --> 21:56:35.990 align:start position:0% next slide let's<21:56:34.440> um<21:56:34.440> let<21:56:34.744> you<21:56:34.856> know<21:56:34.976> the<21:56:35.280> location<21:56:35.576> of 21:56:35.990 --> 21:56:36.000 align:start position:0% let's um let you know the location of 21:56:36.000 --> 21:56:37.430 align:start position:0% let's um let you know the location of the<21:56:36.056> evidence<21:56:36.296> so<21:56:36.480> if<21:56:36.600> it's<21:56:36.720> finally<21:56:37.016> handed 21:56:37.430 --> 21:56:37.440 align:start position:0% the evidence so if it's finally handed 21:56:37.440 --> 21:56:40.310 align:start position:0% the evidence so if it's finally handed to<21:56:37.616> a<21:56:38.280> and<21:56:39.000> property 21:56:40.310 --> 21:56:40.320 align:start position:0% to a and property 21:56:40.320 --> 21:56:42.646 align:start position:0% to a and property retention<21:56:40.976> department<21:56:41.400> like<21:56:42.176> in<21:56:42.296> the<21:56:42.536> police 21:56:42.646 --> 21:56:42.656 align:start position:0% retention department like in the police 21:56:42.656 --> 21:56:44.686 align:start position:0% retention department like in the police property<21:56:43.376> area 21:56:44.686 --> 21:56:44.696 align:start position:0% property area 21:56:44.696 --> 21:56:46.846 align:start position:0% property area then<21:56:45.424> um<21:56:45.424> that<21:56:45.784> would<21:56:45.832> be<21:56:45.960> the<21:56:46.144> last<21:56:46.256> person<21:56:46.552> to 21:56:46.846 --> 21:56:46.856 align:start position:0% then um that would be the last person to 21:56:46.856 --> 21:56:49.366 align:start position:0% then um that would be the last person to have<21:56:47.104> signed<21:56:47.464> for<21:56:47.640> possession 21:56:49.366 --> 21:56:49.376 align:start position:0% have signed for possession 21:56:49.376 --> 21:56:51.966 align:start position:0% have signed for possession starts<21:56:49.976> when<21:56:50.104> it<21:56:50.280> was<21:56:50.400> collected 21:56:51.966 --> 21:56:51.976 align:start position:0% starts when it was collected 21:56:51.976 --> 21:56:54.710 align:start position:0% starts when it was collected requires<21:56:52.976> who<21:56:53.216> collected<21:56:53.696> it<21:56:53.872> the<21:56:54.240> date<21:56:54.480> and 21:56:54.710 --> 21:56:54.720 align:start position:0% requires who collected it the date and 21:56:54.720 --> 21:56:57.646 align:start position:0% requires who collected it the date and time<21:56:55.040> description<21:56:56.040> where<21:56:57.000> the<21:56:57.176> evidence<21:56:57.424> was 21:56:57.646 --> 21:56:57.656 align:start position:0% time description where the evidence was 21:56:57.656 --> 21:56:59.326 align:start position:0% time description where the evidence was stored<21:56:57.960> it's<21:56:58.080> not<21:56:58.256> only<21:56:58.376> given<21:56:58.680> an<21:56:58.800> exhibit 21:56:59.326 --> 21:56:59.336 align:start position:0% stored it's not only given an exhibit 21:56:59.336 --> 21:57:01.494 align:start position:0% stored it's not only given an exhibit reference<21:56:59.696> as<21:57:00.000> well<21:57:00.240> certainly<21:57:01.192> if<21:57:01.320> it's 21:57:01.494 --> 21:57:01.504 align:start position:0% reference as well certainly if it's 21:57:01.504 --> 21:57:03.414 align:start position:0% reference as well certainly if it's collected<21:57:01.856> by<21:57:02.040> an<21:57:02.216> experienced 21:57:03.414 --> 21:57:03.424 align:start position:0% collected by an experienced 21:57:03.424 --> 21:57:05.270 align:start position:0% collected by an experienced um forensics<21:57:03.960> person<21:57:04.256> it'll<21:57:04.744> have<21:57:04.976> some 21:57:05.270 --> 21:57:05.280 align:start position:0% um forensics person it'll have some 21:57:05.280 --> 21:57:09.230 align:start position:0% um forensics person it'll have some reference<21:57:05.936> number<21:57:06.120> on<21:57:06.424> it 21:57:09.230 --> 21:57:09.240 align:start position:0% 21:57:09.240 --> 21:57:11.094 align:start position:0% um how<21:57:09.536> it<21:57:09.720> was<21:57:09.896> initially<21:57:10.256> secured<21:57:10.800> which 21:57:11.094 --> 21:57:11.104 align:start position:0% um how it was initially secured which 21:57:11.104 --> 21:57:13.246 align:start position:0% um how it was initially secured which software<21:57:11.464> can<21:57:11.696> be<21:57:11.824> used<21:57:11.936> to<21:57:12.120> view<21:57:12.296> it 21:57:13.246 --> 21:57:13.256 align:start position:0% software can be used to view it 21:57:13.256 --> 21:57:15.350 align:start position:0% software can be used to view it the<21:57:13.680> transfer<21:57:14.040> history<21:57:14.216> the<21:57:14.512> evidence<21:57:14.824> and 21:57:15.350 --> 21:57:15.360 align:start position:0% the transfer history the evidence and 21:57:15.360 --> 21:57:17.926 align:start position:0% the transfer history the evidence and here's<21:57:15.784> some<21:57:15.960> evidence<21:57:16.440> labels 21:57:17.926 --> 21:57:17.936 align:start position:0% here's some evidence labels 21:57:17.936 --> 21:57:20.990 align:start position:0% here's some evidence labels and<21:57:18.480> not<21:57:18.720> necessarily<21:57:19.192> just<21:57:19.552> for<21:57:20.336> um 21:57:20.990 --> 21:57:21.000 align:start position:0% and not necessarily just for um 21:57:21.000 --> 21:57:23.270 align:start position:0% and not necessarily just for um Okay<21:57:21.296> computer<21:57:21.720> forensics<21:57:22.376> if<21:57:22.856> you<21:57:22.976> can<21:57:23.160> see 21:57:23.270 --> 21:57:23.280 align:start position:0% Okay computer forensics if you can see 21:57:23.280 --> 21:57:25.846 align:start position:0% Okay computer forensics if you can see on<21:57:23.464> the<21:57:23.576> left<21:57:23.696> it's<21:57:24.056> received<21:57:25.016> from<21:57:25.192> and<21:57:25.616> by 21:57:25.846 --> 21:57:25.856 align:start position:0% on the left it's received from and by 21:57:25.856 --> 21:57:29.094 align:start position:0% on the left it's received from and by date<21:57:26.280> time<21:57:26.576> the<21:57:27.120> agency<21:57:27.536> the<21:57:28.376> case<21:57:28.496> number<21:57:28.800> the 21:57:29.094 --> 21:57:29.104 align:start position:0% date time the agency the case number the 21:57:29.104 --> 21:57:31.006 align:start position:0% date time the agency the case number the badge<21:57:29.512> number 21:57:31.006 --> 21:57:31.016 align:start position:0% badge number 21:57:31.016 --> 21:57:33.046 align:start position:0% badge number and<21:57:31.616> then<21:57:31.744> on<21:57:31.976> the<21:57:32.104> right<21:57:32.216> the<21:57:32.512> submitting 21:57:33.046 --> 21:57:33.056 align:start position:0% and then on the right the submitting 21:57:33.056 --> 21:57:38.454 align:start position:0% and then on the right the submitting agency<21:57:33.536> again<21:57:33.960> and<21:57:34.552> chain<21:57:34.744> of<21:57:34.976> custody 21:57:38.454 --> 21:57:38.464 align:start position:0% 21:57:38.464 --> 21:57:40.430 align:start position:0% so<21:57:38.936> the<21:57:39.120> child<21:57:39.296> across<21:57:39.784> today<21:57:39.896> is<21:57:40.256> the 21:57:40.430 --> 21:57:40.440 align:start position:0% so the child across today is the 21:57:40.440 --> 21:57:41.750 align:start position:0% so the child across today is the transfer<21:57:40.744> history<21:57:40.920> showing<21:57:41.464> the<21:57:41.576> information 21:57:41.750 --> 21:57:41.760 align:start position:0% transfer history showing the information 21:57:41.760 --> 21:57:45.646 align:start position:0% transfer history showing the information every<21:57:42.720> person<21:57:43.552> or<21:57:43.920> every<21:57:44.296> normally<21:57:45.296> person 21:57:45.646 --> 21:57:45.656 align:start position:0% every person or every normally person 21:57:45.656 --> 21:57:47.990 align:start position:0% every person or every normally person could<21:57:46.016> be<21:57:46.144> a<21:57:46.256> department<21:57:46.512> and<21:57:47.512> along<21:57:47.696> with<21:57:47.872> the 21:57:47.990 --> 21:57:48.000 align:start position:0% could be a department and along with the 21:57:48.000 --> 21:57:50.686 align:start position:0% could be a department and along with the names<21:57:48.176> and<21:57:48.480> the<21:57:48.720> person<21:57:48.832> signed<21:57:49.440> in<21:57:49.552> the<21:57:50.464> dates 21:57:50.686 --> 21:57:50.696 align:start position:0% names and the person signed in the dates 21:57:50.696 --> 21:57:52.246 align:start position:0% names and the person signed in the dates and<21:57:50.936> where<21:57:51.120> the<21:57:51.296> evidence<21:57:51.480> was<21:57:51.784> stored<21:57:52.144> and 21:57:52.246 --> 21:57:52.256 align:start position:0% and where the evidence was stored and 21:57:52.256 --> 21:57:54.470 align:start position:0% and where the evidence was stored and secured 21:57:54.470 --> 21:57:54.480 align:start position:0% secured 21:57:54.480 --> 21:57:58.966 align:start position:0% secured now<21:57:55.016> if<21:57:55.320> there's<21:57:55.504> a<21:57:55.744> problem<21:57:56.040> if<21:57:56.464> person<21:57:57.320> a<21:57:58.320> has 21:57:58.966 --> 21:57:58.976 align:start position:0% now if there's a problem if person a has 21:57:58.976 --> 21:58:01.606 align:start position:0% now if there's a problem if person a has signed<21:57:59.336> it<21:57:59.400> person<21:57:59.696> B<21:58:00.056> assigned<21:58:00.656> it<21:58:00.832> and<21:58:01.504> then 21:58:01.606 --> 21:58:01.616 align:start position:0% signed it person B assigned it and then 21:58:01.616 --> 21:58:04.430 align:start position:0% signed it person B assigned it and then person<21:58:01.976> D<21:58:02.400> signs<21:58:02.936> a<21:58:03.056> label<21:58:03.424> we've<21:58:04.080> missed<21:58:04.320> out 21:58:04.430 --> 21:58:04.440 align:start position:0% person D signs a label we've missed out 21:58:04.440 --> 21:58:06.950 align:start position:0% person D signs a label we've missed out what<21:58:04.680> happened<21:58:04.920> one<21:58:05.336> person<21:58:05.512> C<21:58:06.000> held<21:58:06.832> that 21:58:06.950 --> 21:58:06.960 align:start position:0% what happened one person C held that 21:58:06.960 --> 21:58:09.230 align:start position:0% what happened one person C held that evidence<21:58:07.256> and<21:58:07.504> if<21:58:07.680> the<21:58:07.920> chain<21:58:08.104> of<21:58:08.280> custody<21:58:08.696> is 21:58:09.230 --> 21:58:09.240 align:start position:0% evidence and if the chain of custody is 21:58:09.240 --> 21:58:11.814 align:start position:0% evidence and if the chain of custody is like<21:58:09.600> broken<21:58:10.040> it<21:58:11.040> means<21:58:11.216> the<21:58:11.336> evidence<21:58:11.576> could 21:58:11.814 --> 21:58:11.824 align:start position:0% like broken it means the evidence could 21:58:11.824 --> 21:58:13.670 align:start position:0% like broken it means the evidence could be<21:58:11.936> tampered<21:58:12.424> with<21:58:12.536> and<21:58:12.960> then<21:58:13.144> it'll<21:58:13.320> be<21:58:13.504> down 21:58:13.670 --> 21:58:13.680 align:start position:0% be tampered with and then it'll be down 21:58:13.680 --> 21:58:15.886 align:start position:0% be tampered with and then it'll be down to<21:58:13.856> a<21:58:14.400> court<21:58:14.576> to<21:58:14.936> determine<21:58:15.296> whether<21:58:15.600> or<21:58:15.832> not 21:58:15.886 --> 21:58:15.896 align:start position:0% to a court to determine whether or not 21:58:15.896 --> 21:58:19.846 align:start position:0% to a court to determine whether or not that<21:58:16.856> evidence<21:58:17.160> is<21:58:17.464> still<21:58:17.640> admissible 21:58:19.846 --> 21:58:19.856 align:start position:0% that evidence is still admissible 21:58:19.856 --> 21:58:21.470 align:start position:0% that evidence is still admissible and<21:58:20.336> the<21:58:20.512> evidence 21:58:21.470 --> 21:58:21.480 align:start position:0% and the evidence 21:58:21.480 --> 21:58:23.030 align:start position:0% and the evidence um but<21:58:22.016> I've<21:58:22.192> just<21:58:22.256> said<21:58:22.440> that<21:58:22.552> it<21:58:22.680> may<21:58:22.800> not<21:58:22.920> be 21:58:23.030 --> 21:58:23.040 align:start position:0% um but I've just said that it may not be 21:58:23.040 --> 21:58:25.070 align:start position:0% um but I've just said that it may not be admissible<21:58:23.464> it<21:58:23.640> could<21:58:23.824> be<21:58:23.936> useless<21:58:24.176> in<21:58:24.424> court 21:58:25.070 --> 21:58:25.080 align:start position:0% admissible it could be useless in court 21:58:25.080 --> 21:58:27.110 align:start position:0% admissible it could be useless in court all<21:58:25.552> right<21:58:25.552> there's<21:58:25.856> a<21:58:26.040> document<21:58:26.336> or<21:58:26.936> a 21:58:27.110 --> 21:58:27.120 align:start position:0% all right there's a document or a 21:58:27.120 --> 21:58:29.862 align:start position:0% all right there's a document or a process<21:58:27.536> called<21:58:28.016> Legal<21:58:28.496> holds<21:58:29.040> used<21:58:29.696> in 21:58:29.862 --> 21:58:29.872 align:start position:0% process called Legal holds used in 21:58:29.872 --> 21:58:31.494 align:start position:0% process called Legal holds used in litigation<21:58:30.360> but<21:58:30.720> it<21:58:30.832> could<21:58:30.960> also<21:58:31.192> be<21:58:31.320> a 21:58:31.494 --> 21:58:31.504 align:start position:0% litigation but it could also be a 21:58:31.504 --> 21:58:34.246 align:start position:0% litigation but it could also be a preservation<21:58:31.976> order<21:58:32.600> basically<21:58:33.600> requires<21:58:34.080> an 21:58:34.246 --> 21:58:34.256 align:start position:0% preservation order basically requires an 21:58:34.256 --> 21:58:37.134 align:start position:0% preservation order basically requires an individual<21:58:34.744> or<21:58:34.976> organization<21:58:35.824> to<21:58:36.296> preserve 21:58:37.134 --> 21:58:37.144 align:start position:0% individual or organization to preserve 21:58:37.144 --> 21:58:39.774 align:start position:0% individual or organization to preserve all<21:58:37.376> information<21:58:37.616> that<21:58:38.160> may<21:58:38.280> be<21:58:38.464> required<21:58:39.000> by 21:58:39.774 --> 21:58:39.784 align:start position:0% all information that may be required by 21:58:39.784 --> 21:58:42.526 align:start position:0% all information that may be required by an<21:58:39.960> opposing<21:58:40.440> party<21:58:40.744> because<21:58:41.512> of<21:58:41.824> anticipated 21:58:42.526 --> 21:58:42.536 align:start position:0% an opposing party because of anticipated 21:58:42.536 --> 21:58:46.366 align:start position:0% an opposing party because of anticipated litigation 21:58:46.366 --> 21:58:46.376 align:start position:0% 21:58:46.376 --> 21:58:49.670 align:start position:0% data<21:58:46.976> should<21:58:47.160> be<21:58:47.280> preserved<21:58:47.872> such<21:58:48.176> as<21:58:48.296> emails 21:58:49.670 --> 21:58:49.680 align:start position:0% data should be preserved such as emails 21:58:49.680 --> 21:58:52.246 align:start position:0% data should be preserved such as emails um<21:58:49.760> preventing<21:58:50.760> things<21:58:51.424> being<21:58:51.656> deleted 21:58:52.246 --> 21:58:52.256 align:start position:0% um preventing things being deleted 21:58:52.256 --> 21:58:55.606 align:start position:0% um preventing things being deleted because<21:58:52.976> of<21:58:53.760> um<21:58:53.760> a<21:58:54.360> certain<21:58:54.960> period<21:58:55.320> of<21:58:55.440> time 21:58:55.606 --> 21:58:55.616 align:start position:0% because of um a certain period of time 21:58:55.616 --> 21:58:59.686 align:start position:0% because of um a certain period of time has<21:58:57.000> um<21:58:57.000> transpired<21:58:57.720> or<21:58:57.896> expired<21:58:58.376> sorry 21:58:59.686 --> 21:58:59.696 align:start position:0% has um transpired or expired sorry 21:58:59.696 --> 21:59:01.846 align:start position:0% has um transpired or expired sorry and<21:59:00.424> there's<21:59:00.600> an<21:59:00.832> Interventional<21:59:01.440> hold<21:59:01.616> on 21:59:01.846 --> 21:59:01.856 align:start position:0% and there's an Interventional hold on 21:59:01.856 --> 21:59:03.710 align:start position:0% and there's an Interventional hold on the<21:59:02.040> routine<21:59:02.400> destruction<21:59:02.760> until<21:59:03.424> the 21:59:03.710 --> 21:59:03.720 align:start position:0% the routine destruction until the 21:59:03.720 --> 21:59:06.526 align:start position:0% the routine destruction until the litigation<21:59:04.144> end<21:59:04.440> so<21:59:04.800> you<21:59:05.640> know<21:59:05.696> as<21:59:06.000> backups 21:59:06.526 --> 21:59:06.536 align:start position:0% litigation end so you know as backups 21:59:06.536 --> 21:59:08.326 align:start position:0% litigation end so you know as backups normally<21:59:06.784> get<21:59:07.080> wiped 21:59:08.326 --> 21:59:08.336 align:start position:0% normally get wiped 21:59:08.336 --> 21:59:11.926 align:start position:0% normally get wiped and<21:59:09.360> um<21:59:09.360> replaced<21:59:10.256> with<21:59:10.440> fresher<21:59:11.400> backups 21:59:11.926 --> 21:59:11.936 align:start position:0% and um replaced with fresher backups 21:59:11.936 --> 21:59:13.670 align:start position:0% and um replaced with fresher backups then<21:59:12.656> um<21:59:12.656> you<21:59:12.896> wouldn't<21:59:13.144> be<21:59:13.256> able<21:59:13.376> to<21:59:13.440> do<21:59:13.552> that 21:59:13.670 --> 21:59:13.680 align:start position:0% then um you wouldn't be able to do that 21:59:13.680 --> 21:59:16.486 align:start position:0% then um you wouldn't be able to do that you'd<21:59:13.920> have<21:59:14.040> to<21:59:14.104> keep<21:59:14.216> hold<21:59:14.400> of<21:59:14.576> the<21:59:14.696> evidence 21:59:16.486 --> 21:59:16.496 align:start position:0% you'd have to keep hold of the evidence 21:59:16.496 --> 21:59:18.166 align:start position:0% you'd have to keep hold of the evidence if<21:59:16.856> a<21:59:16.976> crime<21:59:17.104> scene<21:59:17.400> is<21:59:17.576> a<21:59:17.696> physical<21:59:17.824> location 21:59:18.166 --> 21:59:18.176 align:start position:0% if a crime scene is a physical location 21:59:18.176 --> 21:59:20.326 align:start position:0% if a crime scene is a physical location then<21:59:18.656> the<21:59:18.896> area<21:59:19.080> should<21:59:19.440> be<21:59:19.552> first<21:59:19.744> secured 21:59:20.326 --> 21:59:20.336 align:start position:0% then the area should be first secured 21:59:20.336 --> 21:59:22.310 align:start position:0% then the area should be first secured once<21:59:21.120> the<21:59:21.240> area<21:59:21.360> is<21:59:21.536> secured<21:59:21.832> is<21:59:22.016> important 21:59:22.310 --> 21:59:22.320 align:start position:0% once the area is secured is important 21:59:22.320 --> 21:59:24.950 align:start position:0% once the area is secured is important together<21:59:22.496> as<21:59:22.800> much<21:59:22.976> evidence<21:59:23.280> as<21:59:23.576> possible 21:59:24.950 --> 21:59:24.960 align:start position:0% together as much evidence as possible 21:59:24.960 --> 21:59:27.046 align:start position:0% together as much evidence as possible normally<21:59:25.552> this<21:59:25.856> person<21:59:26.040> will<21:59:26.336> be<21:59:26.512> properly 21:59:27.046 --> 21:59:27.056 align:start position:0% normally this person will be properly 21:59:27.056 --> 21:59:30.046 align:start position:0% normally this person will be properly trained<21:59:27.536> and<21:59:27.656> qualified<21:59:28.464> and<21:59:29.464> just<21:59:29.760> to<21:59:29.872> go 21:59:30.046 --> 21:59:30.056 align:start position:0% trained and qualified and just to go 21:59:30.056 --> 21:59:32.166 align:start position:0% trained and qualified and just to go through<21:59:30.240> how<21:59:30.480> the<21:59:30.656> evidence<21:59:30.896> is<21:59:31.192> collected 21:59:32.166 --> 21:59:32.176 align:start position:0% through how the evidence is collected 21:59:32.176 --> 21:59:34.246 align:start position:0% through how the evidence is collected photographed<21:59:33.176> preserved<21:59:33.784> and<21:59:33.960> who<21:59:34.144> it's 21:59:34.246 --> 21:59:34.256 align:start position:0% photographed preserved and who it's 21:59:34.256 --> 21:59:37.366 align:start position:0% photographed preserved and who it's handed<21:59:34.552> on<21:59:34.744> to<21:59:34.920> and<21:59:35.216> in<21:59:35.464> what<21:59:35.640> manner<21:59:36.536> and<21:59:37.144> some 21:59:37.366 --> 21:59:37.376 align:start position:0% handed on to and in what manner and some 21:59:37.376 --> 21:59:39.230 align:start position:0% handed on to and in what manner and some types<21:59:37.680> of<21:59:37.800> evidence<21:59:38.160> and<21:59:38.760> not<21:59:38.936> that<21:59:39.056> it 21:59:39.230 --> 21:59:39.240 align:start position:0% types of evidence and not that it 21:59:39.240 --> 21:59:41.926 align:start position:0% types of evidence and not that it applies<21:59:39.536> to<21:59:39.784> computers<21:59:40.616> but 21:59:41.926 --> 21:59:41.936 align:start position:0% applies to computers but 21:59:41.936 --> 21:59:44.590 align:start position:0% applies to computers but um<21:59:42.000> say<21:59:42.176> blood<21:59:42.480> on<21:59:42.960> clothing<21:59:43.192> that<21:59:43.744> has<21:59:43.856> to<21:59:44.040> be 21:59:44.590 --> 21:59:44.600 align:start position:0% um say blood on clothing that has to be 21:59:44.600 --> 21:59:47.630 align:start position:0% um say blood on clothing that has to be dried<21:59:45.600> in<21:59:46.016> a<21:59:46.144> certain<21:59:46.256> way<21:59:46.552> in<21:59:47.160> order<21:59:47.216> for<21:59:47.512> it 21:59:47.630 --> 21:59:47.640 align:start position:0% dried in a certain way in order for it 21:59:47.640 --> 21:59:51.046 align:start position:0% dried in a certain way in order for it not<21:59:47.824> to<21:59:48.600> um<21:59:48.656> all<21:59:49.552> go<21:59:49.800> stale<21:59:50.216> and<21:59:50.464> lose<21:59:50.696> all<21:59:50.872> the 21:59:51.046 --> 21:59:51.056 align:start position:0% not to um all go stale and lose all the 21:59:51.056 --> 21:59:54.710 align:start position:0% not to um all go stale and lose all the DNA<21:59:51.424> evidence 21:59:54.710 --> 21:59:54.720 align:start position:0% 21:59:54.720 --> 21:59:56.926 align:start position:0% if<21:59:55.144> the<21:59:55.192> crimes<21:59:55.504> are<21:59:55.680> cyber<21:59:56.040> crime<21:59:56.400> and<21:59:56.760> then 21:59:56.926 --> 21:59:56.936 align:start position:0% if the crimes are cyber crime and then 21:59:56.936 --> 21:59:59.454 align:start position:0% if the crimes are cyber crime and then the<21:59:57.120> location<21:59:57.360> should<21:59:58.144> be<21:59:58.320> secured<21:59:58.744> to<21:59:59.280> stop 21:59:59.454 --> 21:59:59.464 align:start position:0% the location should be secured to stop 21:59:59.464 --> 22:00:01.734 align:start position:0% the location should be secured to stop the<21:59:59.576> evidence<21:59:59.824> being<22:00:00.056> tampered<22:00:00.600> with 22:00:01.734 --> 22:00:01.744 align:start position:0% the evidence being tampered with 22:00:01.744 --> 22:00:03.414 align:start position:0% the evidence being tampered with it<22:00:01.800> doesn't<22:00:02.400> mention<22:00:02.640> there<22:00:02.936> but<22:00:03.120> obviously 22:00:03.414 --> 22:00:03.424 align:start position:0% it doesn't mention there but obviously 22:00:03.424 --> 22:00:05.270 align:start position:0% it doesn't mention there but obviously if<22:00:03.600> there's<22:00:03.784> remote<22:00:04.080> access<22:00:04.440> available<22:00:04.856> to 22:00:05.270 --> 22:00:05.280 align:start position:0% if there's remote access available to 22:00:05.280 --> 22:00:07.182 align:start position:0% if there's remote access available to the<22:00:05.464> device<22:00:05.640> that<22:00:06.056> has<22:00:06.176> to<22:00:06.296> be<22:00:06.480> born<22:00:06.784> in<22:00:07.016> mind 22:00:07.182 --> 22:00:07.192 align:start position:0% the device that has to be born in mind 22:00:07.192 --> 22:00:08.710 align:start position:0% the device that has to be born in mind as<22:00:07.376> well<22:00:07.552> in<22:00:07.744> case<22:00:07.856> somebody<22:00:08.040> can 22:00:08.710 --> 22:00:08.720 align:start position:0% as well in case somebody can 22:00:08.720 --> 22:00:10.846 align:start position:0% as well in case somebody can inadvertently<22:00:09.720> log<22:00:09.960> in<22:00:10.192> and<22:00:10.440> wipe<22:00:10.800> the 22:00:10.846 --> 22:00:10.856 align:start position:0% inadvertently log in and wipe the 22:00:10.856 --> 22:00:13.310 align:start position:0% inadvertently log in and wipe the information 22:00:13.310 --> 22:00:13.320 align:start position:0% 22:00:13.320 --> 22:00:15.414 align:start position:0% a<22:00:13.856> hard<22:00:14.040> drive<22:00:14.216> should<22:00:14.512> be<22:00:14.640> kept<22:00:14.936> in<22:00:15.000> a<22:00:15.176> secure 22:00:15.414 --> 22:00:15.424 align:start position:0% a hard drive should be kept in a secure 22:00:15.424 --> 22:00:17.270 align:start position:0% a hard drive should be kept in a secure Drive<22:00:15.784> is<22:00:16.080> probably<22:00:16.256> going<22:00:16.496> to<22:00:16.616> become<22:00:16.800> harder 22:00:17.270 --> 22:00:17.280 align:start position:0% Drive is probably going to become harder 22:00:17.280 --> 22:00:18.230 align:start position:0% Drive is probably going to become harder and<22:00:17.400> harder 22:00:18.230 --> 22:00:18.240 align:start position:0% and harder 22:00:18.240 --> 22:00:22.070 align:start position:0% and harder now<22:00:18.784> we're<22:00:18.896> using<22:00:19.256> cloud<22:00:19.616> computing 22:00:22.070 --> 22:00:22.080 align:start position:0% now we're using cloud computing 22:00:22.080 --> 22:00:24.470 align:start position:0% now we're using cloud computing uh<22:00:22.976> collect<22:00:23.464> all 22:00:24.470 --> 22:00:24.480 align:start position:0% uh collect all 22:00:24.480 --> 22:00:26.270 align:start position:0% uh collect all um<22:00:24.536> digital<22:00:25.080> evidence<22:00:25.376> in<22:00:25.856> a<22:00:25.976> manner 22:00:26.270 --> 22:00:26.280 align:start position:0% um digital evidence in a manner 22:00:26.280 --> 22:00:28.366 align:start position:0% um digital evidence in a manner permissible<22:00:26.824> to<22:00:27.056> the<22:00:27.240> court<22:00:27.360> it<22:00:28.080> depends<22:00:28.320> on 22:00:28.366 --> 22:00:28.376 align:start position:0% permissible to the court it depends on 22:00:28.376 --> 22:00:30.286 align:start position:0% permissible to the court it depends on the<22:00:28.496> court<22:00:28.680> obviously 22:00:30.286 --> 22:00:30.296 align:start position:0% the court obviously 22:00:30.296 --> 22:00:31.910 align:start position:0% the court obviously when<22:00:30.656> Crumbs<22:00:31.080> are<22:00:31.144> committed<22:00:31.504> the<22:00:31.744> first 22:00:31.910 --> 22:00:31.920 align:start position:0% when Crumbs are committed the first 22:00:31.920 --> 22:00:34.910 align:start position:0% when Crumbs are committed the first responder<22:00:32.464> at<22:00:32.696> the<22:00:33.056> scene<22:00:33.832> controls<22:00:34.800> the 22:00:34.910 --> 22:00:34.920 align:start position:0% responder at the scene controls the 22:00:34.920 --> 22:00:36.950 align:start position:0% responder at the scene controls the damage<22:00:35.336> this<22:00:35.872> could<22:00:36.056> well<22:00:36.240> be<22:00:36.424> you<22:00:36.600> as<22:00:36.784> I've 22:00:36.950 --> 22:00:36.960 align:start position:0% damage this could well be you as I've 22:00:36.960 --> 22:00:38.750 align:start position:0% damage this could well be you as I've said<22:00:37.192> so<22:00:37.552> down<22:00:37.920> to<22:00:38.160> you<22:00:38.280> to<22:00:38.400> use<22:00:38.512> your 22:00:38.750 --> 22:00:38.760 align:start position:0% said so down to you to use your 22:00:38.760 --> 22:00:41.150 align:start position:0% said so down to you to use your technical<22:00:39.056> know-how<22:00:39.536> to<22:00:40.256> preserve<22:00:40.680> data<22:00:41.040> as 22:00:41.150 --> 22:00:41.160 align:start position:0% technical know-how to preserve data as 22:00:41.160 --> 22:00:42.950 align:start position:0% technical know-how to preserve data as much<22:00:41.280> as<22:00:41.464> possible 22:00:42.950 --> 22:00:42.960 align:start position:0% much as possible 22:00:42.960 --> 22:00:44.094 align:start position:0% much as possible foreign 22:00:44.094 --> 22:00:44.104 align:start position:0% foreign 22:00:44.104 --> 22:00:46.910 align:start position:0% foreign ensure<22:00:44.760> nobody<22:00:45.120> else<22:00:45.296> tampers<22:00:45.832> with<22:00:46.080> it<22:00:46.192> again 22:00:46.910 --> 22:00:46.920 align:start position:0% ensure nobody else tampers with it again 22:00:46.920 --> 22:00:49.606 align:start position:0% ensure nobody else tampers with it again you'll<22:00:47.280> be<22:00:47.400> advised<22:00:47.824> by<22:00:48.056> law<22:00:48.360> enforcement<22:00:49.320> as 22:00:49.606 --> 22:00:49.616 align:start position:0% you'll be advised by law enforcement as 22:00:49.616 --> 22:00:51.590 align:start position:0% you'll be advised by law enforcement as and<22:00:49.744> when<22:00:49.920> they<22:00:50.040> arrive<22:00:50.400> but<22:00:50.696> down<22:00:51.176> to<22:00:51.360> you<22:00:51.480> to 22:00:51.590 --> 22:00:51.600 align:start position:0% and when they arrive but down to you to 22:00:51.600 --> 22:00:54.350 align:start position:0% and when they arrive but down to you to stop<22:00:51.784> people<22:00:52.336> walking<22:00:53.336> all<22:00:53.640> over<22:00:53.824> things<22:00:54.120> or 22:00:54.350 --> 22:00:54.360 align:start position:0% stop people walking all over things or 22:00:54.360 --> 22:00:55.910 align:start position:0% stop people walking all over things or picking<22:00:54.656> them<22:00:54.832> up<22:00:54.960> or<22:00:55.192> moving<22:00:55.504> them<22:00:55.680> which 22:00:55.910 --> 22:00:55.920 align:start position:0% picking them up or moving them which 22:00:55.920 --> 22:00:58.070 align:start position:0% picking them up or moving them which have<22:00:56.216> seen<22:00:56.936> happen<22:00:57.176> when<22:00:57.536> I<22:00:57.656> was<22:00:57.784> in<22:00:57.896> the 22:00:58.070 --> 22:00:58.080 align:start position:0% have seen happen when I was in the 22:00:58.080 --> 22:01:01.134 align:start position:0% have seen happen when I was in the police 22:01:01.134 --> 22:01:01.144 align:start position:0% 22:01:01.144 --> 22:01:02.750 align:start position:0% during<22:01:01.680> the<22:01:01.800> course<22:01:01.976> of<22:01:02.160> the<22:01:02.216> investigation 22:01:02.750 --> 22:01:02.760 align:start position:0% during the course of the investigation 22:01:02.760 --> 22:01:05.150 align:start position:0% during the course of the investigation the<22:01:03.720> investigators<22:01:04.440> collect<22:01:04.744> as<22:01:04.976> much 22:01:05.150 --> 22:01:05.160 align:start position:0% the investigators collect as much 22:01:05.160 --> 22:01:07.134 align:start position:0% the investigators collect as much evidence<22:01:05.464> as<22:01:05.696> possible 22:01:07.134 --> 22:01:07.144 align:start position:0% evidence as possible 22:01:07.144 --> 22:01:08.862 align:start position:0% evidence as possible the<22:01:07.440> technical<22:01:07.856> city<22:01:08.104> is<22:01:08.336> established<22:01:08.760> from 22:01:08.862 --> 22:01:08.872 align:start position:0% the technical city is established from 22:01:08.872 --> 22:01:10.366 align:start position:0% the technical city is established from the<22:01:09.056> moment<22:01:09.296> of<22:01:09.656> the<22:01:09.784> initial<22:01:10.016> collection 22:01:10.366 --> 22:01:10.376 align:start position:0% the moment of the initial collection 22:01:10.376 --> 22:01:13.366 align:start position:0% the moment of the initial collection until<22:01:10.856> the<22:01:11.400> investigation<22:01:11.936> finally<22:01:12.480> ends<22:01:12.832> if 22:01:13.366 --> 22:01:13.376 align:start position:0% until the investigation finally ends if 22:01:13.376 --> 22:01:16.006 align:start position:0% until the investigation finally ends if it<22:01:13.552> has<22:01:13.680> to<22:01:13.856> be<22:01:13.976> transported<22:01:14.824> the<22:01:15.360> data<22:01:15.784> in 22:01:16.006 --> 22:01:16.016 align:start position:0% it has to be transported the data in 22:01:16.016 --> 22:01:18.166 align:start position:0% it has to be transported the data in some<22:01:16.256> way<22:01:16.496> it<22:01:17.040> should<22:01:17.216> be<22:01:17.336> done<22:01:17.512> so<22:01:17.696> securely 22:01:18.166 --> 22:01:18.176 align:start position:0% some way it should be done so securely 22:01:18.176 --> 22:01:20.030 align:start position:0% some way it should be done so securely to<22:01:18.480> prevent<22:01:18.720> tampering<22:01:19.376> again<22:01:19.552> this<22:01:19.800> is<22:01:19.920> the 22:01:20.030 --> 22:01:20.040 align:start position:0% to prevent tampering again this is the 22:01:20.040 --> 22:01:22.246 align:start position:0% to prevent tampering again this is the chain<22:01:20.216> of<22:01:20.400> custody 22:01:22.246 --> 22:01:22.256 align:start position:0% chain of custody 22:01:22.256 --> 22:01:24.350 align:start position:0% chain of custody uh<22:01:22.920> when<22:01:23.160> the<22:01:23.400> investigations<22:01:23.872> finally 22:01:24.350 --> 22:01:24.360 align:start position:0% uh when the investigations finally 22:01:24.360 --> 22:01:26.094 align:start position:0% uh when the investigations finally complete<22:01:24.784> the<22:01:24.960> forensic<22:01:25.376> report<22:01:25.616> is<22:01:25.920> made 22:01:26.094 --> 22:01:26.104 align:start position:0% complete the forensic report is made 22:01:26.104 --> 22:01:28.486 align:start position:0% complete the forensic report is made available<22:01:26.536> in<22:01:27.536> a<22:01:27.720> format<22:01:28.080> that<22:01:28.192> can<22:01:28.320> be 22:01:28.486 --> 22:01:28.496 align:start position:0% available in a format that can be 22:01:28.496 --> 22:01:31.542 align:start position:0% available in a format that can be understood<22:01:29.280> by<22:01:29.640> non-technical<22:01:30.296> person<22:01:30.600> and 22:01:31.542 --> 22:01:31.552 align:start position:0% understood by non-technical person and 22:01:31.552 --> 22:01:32.990 align:start position:0% understood by non-technical person and normally<22:01:31.800> because<22:01:31.976> it's<22:01:32.216> been<22:01:32.400> presented<22:01:32.824> to 22:01:32.990 --> 22:01:33.000 align:start position:0% normally because it's been presented to 22:01:33.000 --> 22:01:35.630 align:start position:0% normally because it's been presented to the<22:01:33.176> jewelry<22:01:33.600> if<22:01:33.960> it<22:01:34.144> goes<22:01:34.440> to<22:01:35.040> um<22:01:35.040> a<22:01:35.400> jury 22:01:35.630 --> 22:01:35.640 align:start position:0% the jewelry if it goes to um a jury 22:01:35.640 --> 22:01:37.966 align:start position:0% the jewelry if it goes to um a jury trial 22:01:37.966 --> 22:01:37.976 align:start position:0% trial 22:01:37.976 --> 22:01:40.310 align:start position:0% trial okay<22:01:38.336> we've<22:01:38.696> mentioned<22:01:39.536> um<22:01:39.536> the<22:01:39.832> legal<22:01:40.144> hold 22:01:40.310 --> 22:01:40.320 align:start position:0% okay we've mentioned um the legal hold 22:01:40.320 --> 22:01:42.526 align:start position:0% okay we've mentioned um the legal hold must<22:01:40.744> keep<22:01:40.976> that<22:01:41.280> information<22:01:41.760> into<22:01:42.296> the 22:01:42.526 --> 22:01:42.536 align:start position:0% must keep that information into the 22:01:42.536 --> 22:01:44.502 align:start position:0% must keep that information into the litigation<22:01:43.080> ends 22:01:44.502 --> 22:01:44.512 align:start position:0% litigation ends 22:01:44.512 --> 22:01:46.966 align:start position:0% litigation ends just<22:01:44.872> a<22:01:45.056> few<22:01:45.240> steps<22:01:45.600> in<22:01:45.784> the<22:01:46.016> basic<22:01:46.376> forensic 22:01:46.966 --> 22:01:46.976 align:start position:0% just a few steps in the basic forensic 22:01:46.976 --> 22:01:49.182 align:start position:0% just a few steps in the basic forensic process 22:01:49.182 --> 22:01:49.192 align:start position:0% process 22:01:49.192 --> 22:01:51.470 align:start position:0% process this<22:01:49.856> should<22:01:50.040> be<22:01:50.216> a<22:01:50.512> process<22:01:51.000> in<22:01:51.296> place 22:01:51.470 --> 22:01:51.480 align:start position:0% this should be a process in place 22:01:51.480 --> 22:01:53.390 align:start position:0% this should be a process in place according<22:01:52.080> to<22:01:52.144> National<22:01:52.496> Institute<22:01:53.216> of 22:01:53.390 --> 22:01:53.400 align:start position:0% according to National Institute of 22:01:53.400 --> 22:01:55.542 align:start position:0% according to National Institute of Standards<22:01:53.872> and<22:01:54.000> Technology 22:01:55.542 --> 22:01:55.552 align:start position:0% Standards and Technology 22:01:55.552 --> 22:01:57.774 align:start position:0% Standards and Technology the<22:01:56.160> following<22:01:56.512> steps<22:01:56.936> collection 22:01:57.774 --> 22:01:57.784 align:start position:0% the following steps collection 22:01:57.784 --> 22:02:02.630 align:start position:0% the following steps collection examination<22:01:58.760> analysis<22:01:59.760> and<22:02:00.360> Reporting 22:02:02.630 --> 22:02:02.640 align:start position:0% examination analysis and Reporting 22:02:02.640 --> 22:02:04.966 align:start position:0% examination analysis and Reporting collection<22:02:03.240> is<22:02:03.536> the<22:02:03.720> first<22:02:03.832> phase<22:02:04.192> where<22:02:04.440> data 22:02:04.966 --> 22:02:04.976 align:start position:0% collection is the first phase where data 22:02:04.976 --> 22:02:07.966 align:start position:0% collection is the first phase where data is<22:02:05.104> identified<22:02:05.576> labels<22:02:06.296> and<22:02:07.192> recorded<22:02:07.744> and 22:02:07.966 --> 22:02:07.976 align:start position:0% is identified labels and recorded and 22:02:07.976 --> 22:02:09.414 align:start position:0% is identified labels and recorded and gathered 22:02:09.414 --> 22:02:09.424 align:start position:0% gathered 22:02:09.424 --> 22:02:12.246 align:start position:0% gathered could<22:02:09.832> well<22:02:10.256> be<22:02:10.440> photographed<22:02:10.976> in<22:02:11.104> situ<22:02:11.512> also 22:02:12.246 --> 22:02:12.256 align:start position:0% could well be photographed in situ also 22:02:12.256 --> 22:02:15.350 align:start position:0% could well be photographed in situ also examination<22:02:13.576> uh<22:02:14.576> it's<22:02:14.760> the<22:02:15.000> data's 22:02:15.350 --> 22:02:15.360 align:start position:0% examination uh it's the data's 22:02:15.360 --> 22:02:17.630 align:start position:0% examination uh it's the data's forensically<22:02:15.832> process<22:02:16.256> using<22:02:16.856> automated<22:02:17.400> or 22:02:17.630 --> 22:02:17.640 align:start position:0% forensically process using automated or 22:02:17.640 --> 22:02:19.246 align:start position:0% forensically process using automated or manual<22:02:18.000> methods 22:02:19.246 --> 22:02:19.256 align:start position:0% manual methods 22:02:19.256 --> 22:02:22.310 align:start position:0% manual methods analysis<22:02:20.216> the<22:02:20.872> results<22:02:21.000> of<22:02:21.296> the<22:02:21.480> examination 22:02:22.310 --> 22:02:22.320 align:start position:0% analysis the results of the examination 22:02:22.320 --> 22:02:24.886 align:start position:0% analysis the results of the examination are<22:02:22.744> analyzed<22:02:23.216> to<22:02:23.400> get<22:02:23.512> answers 22:02:24.886 --> 22:02:24.896 align:start position:0% are analyzed to get answers 22:02:24.896 --> 22:02:27.886 align:start position:0% are analyzed to get answers and<22:02:25.376> then<22:02:25.552> reporting<22:02:26.424> the<22:02:27.424> results<22:02:27.536> are 22:02:27.886 --> 22:02:27.896 align:start position:0% and then reporting the results are 22:02:27.896 --> 22:02:29.590 align:start position:0% and then reporting the results are reported 22:02:29.590 --> 22:02:29.600 align:start position:0% reported 22:02:29.600 --> 22:02:32.094 align:start position:0% reported details<22:02:30.600> the<22:02:30.960> actions<22:02:31.320> carried<22:02:31.680> out<22:02:31.800> the 22:02:32.094 --> 22:02:32.104 align:start position:0% details the actions carried out the 22:02:32.104 --> 22:02:34.246 align:start position:0% details the actions carried out the tools<22:02:32.336> and<22:02:32.464> procedure<22:02:32.936> used<22:02:33.240> who<22:02:33.720> did<22:02:33.896> it<22:02:34.016> and 22:02:34.246 --> 22:02:34.256 align:start position:0% tools and procedure used who did it and 22:02:34.256 --> 22:02:36.526 align:start position:0% tools and procedure used who did it and when<22:02:34.440> and<22:02:34.616> why 22:02:36.526 --> 22:02:36.536 align:start position:0% when and why 22:02:36.536 --> 22:02:38.502 align:start position:0% when and why Okay<22:02:37.016> so<22:02:37.192> we've<22:02:37.440> covered<22:02:37.680> a<22:02:37.800> lot<22:02:37.920> here<22:02:38.104> so<22:02:38.336> just 22:02:38.502 --> 22:02:38.512 align:start position:0% Okay so we've covered a lot here so just 22:02:38.512 --> 22:02:40.606 align:start position:0% Okay so we've covered a lot here so just to<22:02:38.640> recap<22:02:39.000> we've<22:02:39.424> looked<22:02:39.600> at<22:02:39.720> forensics<22:02:40.376> and 22:02:40.606 --> 22:02:40.616 align:start position:0% to recap we've looked at forensics and 22:02:40.616 --> 22:02:42.166 align:start position:0% to recap we've looked at forensics and computer<22:02:40.856> forensics 22:02:42.166 --> 22:02:42.176 align:start position:0% computer forensics 22:02:42.176 --> 22:02:44.166 align:start position:0% computer forensics the<22:02:42.720> first<22:02:42.896> responder 22:02:44.166 --> 22:02:44.176 align:start position:0% the first responder 22:02:44.176 --> 22:02:46.670 align:start position:0% the first responder electronic<22:02:45.176> Discovery<22:02:45.960> in<22:02:46.144> the<22:02:46.320> chain<22:02:46.440> of 22:02:46.670 --> 22:02:46.680 align:start position:0% electronic Discovery in the chain of 22:02:46.680 --> 22:02:47.814 align:start position:0% electronic Discovery in the chain of custody 22:02:47.814 --> 22:02:47.824 align:start position:0% custody 22:02:47.824 --> 22:02:51.646 align:start position:0% custody legal<22:02:48.480> holes<22:02:49.280> securing<22:02:50.280> the<22:02:50.400> crime<22:02:50.696> scene 22:02:51.646 --> 22:02:51.656 align:start position:0% legal holes securing the crime scene 22:02:51.656 --> 22:02:54.286 align:start position:0% legal holes securing the crime scene the<22:02:52.080> high<22:02:52.256> level<22:02:52.440> View 22:02:54.286 --> 22:02:54.296 align:start position:0% the high level View 22:02:54.296 --> 22:02:57.526 align:start position:0% the high level View steps<22:02:55.080> in<22:02:55.192> basic<22:02:55.800> uh<22:02:56.336> forensics<22:02:56.872> collection 22:02:57.526 --> 22:02:57.536 align:start position:0% steps in basic uh forensics collection 22:02:57.536 --> 22:03:00.774 align:start position:0% steps in basic uh forensics collection examination<22:02:58.376> analysis<22:02:59.104> and<22:02:59.336> Reporting<22:02:59.936> so 22:03:00.774 --> 22:03:00.784 align:start position:0% examination analysis and Reporting so 22:03:00.784 --> 22:03:09.120 align:start position:0% examination analysis and Reporting so that's<22:03:01.016> all<22:03:01.256> for<22:03:01.504> now<22:03:01.680> thanks<22:03:02.104> for<22:03:02.280> watching 22:03:09.120 --> 22:03:09.130 align:start position:0% 22:03:09.130 --> 22:03:17.822 align:start position:0% [Music] 22:03:17.822 --> 22:03:17.832 align:start position:0% [Music] 22:03:17.832 --> 22:03:25.366 align:start position:0% [Music] thank<22:03:18.832> you 22:03:25.366 --> 22:03:25.376 align:start position:0% 22:03:25.376 --> 22:03:28.542 align:start position:0% welcome<22:03:25.856> to<22:03:26.104> module<22:03:26.640> 18<22:03:26.824> lesson<22:03:27.656> 3<22:03:27.832> safety 22:03:28.542 --> 22:03:28.552 align:start position:0% welcome to module 18 lesson 3 safety 22:03:28.552 --> 22:03:30.166 align:start position:0% welcome to module 18 lesson 3 safety practices 22:03:30.166 --> 22:03:30.176 align:start position:0% practices 22:03:30.176 --> 22:03:34.134 align:start position:0% practices another<22:03:30.960> new<22:03:31.696> addition<22:03:32.696> to<22:03:32.936> the<22:03:33.176> topic<22:03:33.600> and 22:03:34.134 --> 22:03:34.144 align:start position:0% another new addition to the topic and 22:03:34.144 --> 22:03:36.350 align:start position:0% another new addition to the topic and it's<22:03:34.376> something<22:03:34.616> that<22:03:35.280> has<22:03:35.760> been<22:03:35.936> growing 22:03:36.350 --> 22:03:36.360 align:start position:0% it's something that has been growing 22:03:36.360 --> 22:03:38.094 align:start position:0% it's something that has been growing over<22:03:36.536> the<22:03:36.720> past<22:03:36.896> few<22:03:37.080> years<22:03:37.320> and<22:03:37.552> so<22:03:37.744> this<22:03:37.920> has 22:03:38.094 --> 22:03:38.104 align:start position:0% over the past few years and so this has 22:03:38.104 --> 22:03:41.502 align:start position:0% over the past few years and so this has become<22:03:38.512> a<22:03:39.360> recognized<22:03:39.960> area<22:03:40.376> where<22:03:41.160> you<22:03:41.336> go 22:03:41.502 --> 22:03:41.512 align:start position:0% become a recognized area where you go 22:03:41.512 --> 22:03:44.326 align:start position:0% become a recognized area where you go and<22:03:41.640> get<22:03:41.824> qualified<22:03:42.320> in<22:03:43.320> a<22:03:43.504> risk<22:03:43.920> assessment 22:03:44.326 --> 22:03:44.336 align:start position:0% and get qualified in a risk assessment 22:03:44.336 --> 22:03:46.006 align:start position:0% and get qualified in a risk assessment or<22:03:44.824> whatever<22:03:45.120> it's<22:03:45.360> called<22:03:45.536> in<22:03:45.832> your 22:03:46.006 --> 22:03:46.016 align:start position:0% or whatever it's called in your 22:03:46.016 --> 22:03:47.686 align:start position:0% or whatever it's called in your respective<22:03:46.440> countries 22:03:47.686 --> 22:03:47.696 align:start position:0% respective countries 22:03:47.696 --> 22:03:49.910 align:start position:0% respective countries in<22:03:48.360> respect<22:03:48.784> of 22:03:49.910 --> 22:03:49.920 align:start position:0% in respect of 22:03:49.920 --> 22:03:52.182 align:start position:0% in respect of um<22:03:49.976> certainly<22:03:50.824> data<22:03:51.296> centers<22:03:51.656> the<22:03:52.016> safe 22:03:52.182 --> 22:03:52.192 align:start position:0% um certainly data centers the safe 22:03:52.192 --> 22:03:54.470 align:start position:0% um certainly data centers the safe storage 22:03:54.470 --> 22:03:54.480 align:start position:0% storage 22:03:54.480 --> 22:03:57.414 align:start position:0% storage um manual<22:03:55.440> handling<22:03:55.920> what<22:03:56.872> to<22:03:57.000> do<22:03:57.120> in<22:03:57.296> the 22:03:57.414 --> 22:03:57.424 align:start position:0% um manual handling what to do in the 22:03:57.424 --> 22:03:59.502 align:start position:0% um manual handling what to do in the event<22:03:57.536> of<22:03:57.832> an<22:03:58.016> emergency<22:03:58.192> a<22:03:58.800> fire<22:03:59.040> or<22:03:59.336> other 22:03:59.502 --> 22:03:59.512 align:start position:0% event of an emergency a fire or other 22:03:59.512 --> 22:04:02.270 align:start position:0% event of an emergency a fire or other disaster<22:04:00.424> how<22:04:01.256> to<22:04:01.504> keep 22:04:02.270 --> 22:04:02.280 align:start position:0% disaster how to keep 22:04:02.280 --> 22:04:05.686 align:start position:0% disaster how to keep um<22:04:02.336> the<22:04:02.696> equipment<22:04:03.056> safe<22:04:03.600> and<22:04:04.512> comply<22:04:05.512> with 22:04:05.686 --> 22:04:05.696 align:start position:0% um the equipment safe and comply with 22:04:05.696 --> 22:04:07.430 align:start position:0% um the equipment safe and comply with all<22:04:05.936> of<22:04:06.176> the 22:04:07.430 --> 22:04:07.440 align:start position:0% all of the 22:04:07.440 --> 22:04:09.886 align:start position:0% all of the um<22:04:07.504> different<22:04:07.744> certifications<22:04:08.600> and<22:04:09.600> if<22:04:09.832> you 22:04:09.886 --> 22:04:09.896 align:start position:0% um different certifications and if you 22:04:09.896 --> 22:04:11.470 align:start position:0% um different certifications and if you want<22:04:10.016> to<22:04:10.080> be<22:04:10.192> a<22:04:10.320> Data<22:04:10.680> Center 22:04:11.470 --> 22:04:11.480 align:start position:0% want to be a Data Center 22:04:11.480 --> 22:04:15.526 align:start position:0% want to be a Data Center and<22:04:12.480> keep<22:04:13.320> people<22:04:13.504> safe<22:04:13.856> also 22:04:15.526 --> 22:04:15.536 align:start position:0% and keep people safe also 22:04:15.536 --> 22:04:18.286 align:start position:0% and keep people safe also so<22:04:16.376> look<22:04:16.976> at<22:04:17.104> the<22:04:17.280> data<22:04:17.640> center<22:04:17.760> and<22:04:18.056> the<22:04:18.176> need 22:04:18.286 --> 22:04:18.296 align:start position:0% so look at the data center and the need 22:04:18.296 --> 22:04:21.110 align:start position:0% so look at the data center and the need the<22:04:18.720> environment<22:04:19.256> heating<22:04:20.216> ventilation<22:04:20.760> and 22:04:21.110 --> 22:04:21.120 align:start position:0% the environment heating ventilation and 22:04:21.120 --> 22:04:23.150 align:start position:0% the environment heating ventilation and cooling<22:04:21.536> HVAC 22:04:23.150 --> 22:04:23.160 align:start position:0% cooling HVAC 22:04:23.160 --> 22:04:25.734 align:start position:0% cooling HVAC how<22:04:23.696> HVAC<22:04:24.424> works 22:04:25.734 --> 22:04:25.744 align:start position:0% how HVAC works 22:04:25.744 --> 22:04:28.910 align:start position:0% how HVAC works typical<22:04:26.464> hot<22:04:26.936> cold<22:04:27.296> oil<22:04:27.656> conditions 22:04:28.910 --> 22:04:28.920 align:start position:0% typical hot cold oil conditions 22:04:28.920 --> 22:04:32.150 align:start position:0% typical hot cold oil conditions rack<22:04:29.576> mount<22:04:29.760> servers<22:04:30.360> rack<22:04:31.016> loading 22:04:32.150 --> 22:04:32.160 align:start position:0% rack mount servers rack loading 22:04:32.160 --> 22:04:35.630 align:start position:0% rack mount servers rack loading power<22:04:32.696> distribution<22:04:33.424> and<22:04:34.144> fire<22:04:34.440> risk 22:04:35.630 --> 22:04:35.640 align:start position:0% power distribution and fire risk 22:04:35.640 --> 22:04:38.150 align:start position:0% power distribution and fire risk the<22:04:36.056> impact<22:04:36.296> of<22:04:36.536> Fire 22:04:38.150 --> 22:04:38.160 align:start position:0% the impact of Fire 22:04:38.160 --> 22:04:40.366 align:start position:0% the impact of Fire types<22:04:38.824> of<22:04:38.872> their<22:04:39.056> suppressant<22:04:39.600> agents<22:04:40.144> you've 22:04:40.366 --> 22:04:40.376 align:start position:0% types of their suppressant agents you've 22:04:40.376 --> 22:04:43.910 align:start position:0% types of their suppressant agents you've got<22:04:40.496> available<22:04:40.824> to<22:04:41.824> install<22:04:42.376> wet<22:04:43.376> pipe<22:04:43.800> dry 22:04:43.910 --> 22:04:43.920 align:start position:0% got available to install wet pipe dry 22:04:43.920 --> 22:04:45.646 align:start position:0% got available to install wet pipe dry pipe<22:04:44.400> and<22:04:44.512> gas 22:04:45.646 --> 22:04:45.656 align:start position:0% pipe and gas 22:04:45.656 --> 22:04:47.566 align:start position:0% pipe and gas how<22:04:46.144> to<22:04:46.320> lift<22:04:46.552> stuff<22:04:46.680> up<22:04:46.920> without<22:04:47.160> getting 22:04:47.566 --> 22:04:47.576 align:start position:0% how to lift stuff up without getting 22:04:47.576 --> 22:04:50.390 align:start position:0% how to lift stuff up without getting injured<22:04:48.440> anti-static<22:04:49.440> it's<22:04:49.856> funnily<22:04:50.280> enough 22:04:50.390 --> 22:04:50.400 align:start position:0% injured anti-static it's funnily enough 22:04:50.400 --> 22:04:52.542 align:start position:0% injured anti-static it's funnily enough anti-static<22:04:51.120> if<22:04:51.360> people<22:04:51.536> laugh<22:04:51.784> about<22:04:51.960> it<22:04:52.256> and 22:04:52.542 --> 22:04:52.552 align:start position:0% anti-static if people laugh about it and 22:04:52.552 --> 22:04:54.230 align:start position:0% anti-static if people laugh about it and don't<22:04:53.040> think<22:04:53.216> about<22:04:53.400> it<22:04:53.576> but<22:04:53.824> it<22:04:53.936> can<22:04:54.056> actually 22:04:54.230 --> 22:04:54.240 align:start position:0% don't think about it but it can actually 22:04:54.240 --> 22:04:58.182 align:start position:0% don't think about it but it can actually fry<22:04:55.256> vital<22:04:55.856> components<22:04:56.640> in<22:04:56.760> your<22:04:57.000> devices 22:04:58.182 --> 22:04:58.192 align:start position:0% fry vital components in your devices 22:04:58.192 --> 22:05:00.646 align:start position:0% fry vital components in your devices stabilizing<22:04:59.104> the<22:04:59.280> Iraq<22:04:59.640> and<22:05:00.000> the<22:05:00.176> material 22:05:00.646 --> 22:05:00.656 align:start position:0% stabilizing the Iraq and the material 22:05:00.656 --> 22:05:03.070 align:start position:0% stabilizing the Iraq and the material safety<22:05:01.192> data<22:05:01.616> sheet<22:05:01.856> which<22:05:02.160> is<22:05:02.280> another 22:05:03.070 --> 22:05:03.080 align:start position:0% safety data sheet which is another 22:05:03.080 --> 22:05:07.430 align:start position:0% safety data sheet which is another item<22:05:04.080> added<22:05:04.496> to<22:05:04.680> the<22:05:04.920> syllabus<22:05:05.464> the<22:05:05.696> MSDS 22:05:07.430 --> 22:05:07.440 align:start position:0% item added to the syllabus the MSDS 22:05:07.440 --> 22:05:09.110 align:start position:0% item added to the syllabus the MSDS all<22:05:07.856> right<22:05:08.040> I'm<22:05:08.104> sure<22:05:08.280> you've<22:05:08.464> heard<22:05:08.576> the<22:05:08.760> data 22:05:09.110 --> 22:05:09.120 align:start position:0% all right I'm sure you've heard the data 22:05:09.120 --> 22:05:10.910 align:start position:0% all right I'm sure you've heard the data centers<22:05:09.424> and<22:05:09.656> if<22:05:09.832> you're<22:05:09.960> very<22:05:10.192> lucky<22:05:10.376> you've 22:05:10.910 --> 22:05:10.920 align:start position:0% centers and if you're very lucky you've 22:05:10.920 --> 22:05:13.006 align:start position:0% centers and if you're very lucky you've actually<22:05:11.040> got<22:05:11.512> to<22:05:11.640> work<22:05:11.872> in<22:05:12.120> one<22:05:12.296> or<22:05:12.600> will<22:05:12.832> be 22:05:13.006 --> 22:05:13.016 align:start position:0% actually got to work in one or will be 22:05:13.016 --> 22:05:16.846 align:start position:0% actually got to work in one or will be working<22:05:13.192> in<22:05:13.504> one<22:05:13.744> great<22:05:14.400> place<22:05:14.696> to<22:05:15.240> work 22:05:16.846 --> 22:05:16.856 align:start position:0% working in one great place to work 22:05:16.856 --> 22:05:19.670 align:start position:0% working in one great place to work there's<22:05:17.576> a<22:05:17.696> definition<22:05:17.872> on<22:05:18.296> Wikipedia<22:05:19.016> it's<22:05:19.504> a 22:05:19.670 --> 22:05:19.680 align:start position:0% there's a definition on Wikipedia it's a 22:05:19.680 --> 22:05:21.590 align:start position:0% there's a definition on Wikipedia it's a facilities<22:05:20.040> used<22:05:20.336> to<22:05:20.872> house<22:05:21.240> computer 22:05:21.590 --> 22:05:21.600 align:start position:0% facilities used to house computer 22:05:21.600 --> 22:05:23.750 align:start position:0% facilities used to house computer systems<22:05:22.256> and<22:05:22.496> Associated<22:05:22.920> components<22:05:23.512> such 22:05:23.750 --> 22:05:23.760 align:start position:0% systems and Associated components such 22:05:23.760 --> 22:05:26.566 align:start position:0% systems and Associated components such as<22:05:23.936> telecoms<22:05:24.600> and<22:05:25.440> Storage 22:05:26.566 --> 22:05:26.576 align:start position:0% as telecoms and Storage 22:05:26.576 --> 22:05:28.670 align:start position:0% as telecoms and Storage generally<22:05:27.296> includes<22:05:27.656> redundant<22:05:28.192> backup 22:05:28.670 --> 22:05:28.680 align:start position:0% generally includes redundant backup 22:05:28.680 --> 22:05:30.710 align:start position:0% generally includes redundant backup power<22:05:28.856> supplies<22:05:29.720> Communications 22:05:30.710 --> 22:05:30.720 align:start position:0% power supplies Communications 22:05:30.720 --> 22:05:33.046 align:start position:0% power supplies Communications environmental<22:05:31.616> controls 22:05:33.046 --> 22:05:33.056 align:start position:0% environmental controls 22:05:33.056 --> 22:05:35.686 align:start position:0% environmental controls EG<22:05:33.600> air<22:05:34.080> conditioning<22:05:34.440> fire<22:05:34.800> suppression<22:05:35.216> and 22:05:35.686 --> 22:05:35.696 align:start position:0% EG air conditioning fire suppression and 22:05:35.696 --> 22:05:40.134 align:start position:0% EG air conditioning fire suppression and various<22:05:36.056> security<22:05:36.656> devices 22:05:40.134 --> 22:05:40.144 align:start position:0% 22:05:40.144 --> 22:05:41.862 align:start position:0% why<22:05:40.552> do<22:05:40.744> we<22:05:40.800> bother<22:05:41.104> it<22:05:41.336> basically<22:05:41.640> helps 22:05:41.862 --> 22:05:41.872 align:start position:0% why do we bother it basically helps 22:05:41.872 --> 22:05:44.110 align:start position:0% why do we bother it basically helps organization<22:05:42.600> centralize<22:05:43.256> the<22:05:43.552> entire 22:05:44.110 --> 22:05:44.120 align:start position:0% organization centralize the entire 22:05:44.120 --> 22:05:47.502 align:start position:0% organization centralize the entire Computing<22:05:45.120> resources<22:05:45.720> into<22:05:46.280> one<22:05:47.280> location 22:05:47.502 --> 22:05:47.512 align:start position:0% Computing resources into one location 22:05:47.512 --> 22:05:51.286 align:start position:0% Computing resources into one location where<22:05:48.176> they<22:05:48.360> can<22:05:48.536> have<22:05:48.720> a<22:05:48.960> uniform<22:05:49.504> procedure 22:05:51.286 --> 22:05:51.296 align:start position:0% where they can have a uniform procedure 22:05:51.296 --> 22:05:55.670 align:start position:0% where they can have a uniform procedure for<22:05:51.896> insulation<22:05:52.744> upgrades<22:05:53.696> out<22:05:54.056> of<22:05:54.176> hours<22:05:54.680> a 22:05:55.670 --> 22:05:55.680 align:start position:0% for insulation upgrades out of hours a 22:05:55.680 --> 22:05:58.486 align:start position:0% for insulation upgrades out of hours a redundancy<22:05:56.336> a<22:05:56.512> whole<22:05:56.696> bunch<22:05:56.872> of<22:05:57.056> stuff 22:05:58.486 --> 22:05:58.496 align:start position:0% redundancy a whole bunch of stuff 22:05:58.496 --> 22:06:02.094 align:start position:0% redundancy a whole bunch of stuff uh<22:05:59.104> reduces<22:05:59.696> the<22:06:00.120> TCO<22:06:00.720> by<22:06:01.256> consolidating<22:06:01.800> all 22:06:02.094 --> 22:06:02.104 align:start position:0% uh reduces the TCO by consolidating all 22:06:02.104 --> 22:06:03.646 align:start position:0% uh reduces the TCO by consolidating all your<22:06:02.280> power<22:06:02.464> and<22:06:02.640> cooling<22:06:03.000> otherwise<22:06:03.480> you'd 22:06:03.646 --> 22:06:03.656 align:start position:0% your power and cooling otherwise you'd 22:06:03.656 --> 22:06:07.134 align:start position:0% your power and cooling otherwise you'd have<22:06:03.832> to<22:06:03.960> have<22:06:04.192> 10<22:06:05.104> 20<22:06:05.400> 30<22:06:05.760> 40<22:06:06.120> racks<22:06:06.784> spread 22:06:07.134 --> 22:06:07.144 align:start position:0% have to have 10 20 30 40 racks spread 22:06:07.144 --> 22:06:09.166 align:start position:0% have to have 10 20 30 40 racks spread among<22:06:07.504> different<22:06:08.040> departments<22:06:08.760> or<22:06:08.936> different 22:06:09.166 --> 22:06:09.176 align:start position:0% among different departments or different 22:06:09.176 --> 22:06:10.966 align:start position:0% among different departments or different buildings<22:06:09.656> or<22:06:09.960> different<22:06:10.192> cities<22:06:10.496> making 22:06:10.966 --> 22:06:10.976 align:start position:0% buildings or different cities making 22:06:10.976 --> 22:06:15.110 align:start position:0% buildings or different cities making things<22:06:11.400> pretty<22:06:12.240> difficult<22:06:12.656> to<22:06:13.320> control 22:06:15.110 --> 22:06:15.120 align:start position:0% things pretty difficult to control 22:06:15.120 --> 22:06:17.566 align:start position:0% things pretty difficult to control racks<22:06:15.960> and<22:06:16.080> rackmatic<22:06:16.744> servers<22:06:17.160> are<22:06:17.280> used<22:06:17.400> in 22:06:17.566 --> 22:06:17.576 align:start position:0% racks and rackmatic servers are used in 22:06:17.576 --> 22:06:20.502 align:start position:0% racks and rackmatic servers are used in data<22:06:17.936> centers<22:06:18.360> at<22:06:18.784> the<22:06:18.896> moment<22:06:19.144> I'm<22:06:20.104> sure<22:06:20.336> the 22:06:20.502 --> 22:06:20.512 align:start position:0% data centers at the moment I'm sure the 22:06:20.512 --> 22:06:22.310 align:start position:0% data centers at the moment I'm sure the future<22:06:20.696> will<22:06:21.056> uh<22:06:21.296> have<22:06:21.536> something<22:06:21.784> completely 22:06:22.310 --> 22:06:22.320 align:start position:0% future will uh have something completely 22:06:22.320 --> 22:06:24.774 align:start position:0% future will uh have something completely different<22:06:22.760> you've<22:06:23.760> got<22:06:23.824> the<22:06:24.056> servers<22:06:24.480> storage 22:06:24.774 --> 22:06:24.784 align:start position:0% different you've got the servers storage 22:06:24.784 --> 22:06:27.822 align:start position:0% different you've got the servers storage arrays<22:06:25.320> and<22:06:25.440> power<22:06:25.616> distribution<22:06:26.216> units<22:06:27.000> all 22:06:27.822 --> 22:06:27.832 align:start position:0% arrays and power distribution units all 22:06:27.832 --> 22:06:30.110 align:start position:0% arrays and power distribution units all the<22:06:27.960> other<22:06:28.080> devices<22:06:28.496> and<22:06:29.216> internal 22:06:30.110 --> 22:06:30.120 align:start position:0% the other devices and internal 22:06:30.120 --> 22:06:34.366 align:start position:0% the other devices and internal components<22:06:31.080> generate<22:06:31.680> a<22:06:32.280> lot<22:06:32.400> of<22:06:32.640> heat 22:06:34.366 --> 22:06:34.376 align:start position:0% components generate a lot of heat 22:06:34.376 --> 22:06:36.286 align:start position:0% components generate a lot of heat the<22:06:34.920> heat<22:06:35.104> needs<22:06:35.464> to<22:06:35.512> be<22:06:35.576> removed<22:06:35.936> because<22:06:36.056> it 22:06:36.286 --> 22:06:36.296 align:start position:0% the heat needs to be removed because it 22:06:36.296 --> 22:06:38.206 align:start position:0% the heat needs to be removed because it obviously<22:06:36.600> affects<22:06:36.960> the<22:06:37.080> electric<22:06:37.256> equipment 22:06:38.206 --> 22:06:38.216 align:start position:0% obviously affects the electric equipment 22:06:38.216 --> 22:06:40.670 align:start position:0% obviously affects the electric equipment to<22:06:38.464> the<22:06:38.696> point<22:06:38.872> where<22:06:39.296> it<22:06:39.896> reaches<22:06:40.320> a 22:06:40.670 --> 22:06:40.680 align:start position:0% to the point where it reaches a 22:06:40.680 --> 22:06:43.390 align:start position:0% to the point where it reaches a threshold<22:06:41.512> that<22:06:42.240> it<22:06:42.360> can<22:06:42.536> no<22:06:42.656> longer<22:06:42.960> function 22:06:43.390 --> 22:06:43.400 align:start position:0% threshold that it can no longer function 22:06:43.400 --> 22:06:46.182 align:start position:0% threshold that it can no longer function and<22:06:44.400> then<22:06:44.512> the<22:06:44.760> device<22:06:44.936> will<22:06:45.240> fail<22:06:45.536> and<22:06:46.080> you 22:06:46.182 --> 22:06:46.192 align:start position:0% and then the device will fail and you 22:06:46.192 --> 22:06:47.686 align:start position:0% and then the device will fail and you may<22:06:46.320> have<22:06:46.440> had<22:06:46.552> this<22:06:46.800> on<22:06:47.104> your<22:06:47.280> home<22:06:47.464> computer 22:06:47.686 --> 22:06:47.696 align:start position:0% may have had this on your home computer 22:06:47.696 --> 22:06:49.910 align:start position:0% may have had this on your home computer if<22:06:48.120> your<22:06:48.296> CPU<22:06:48.784> fan 22:06:49.910 --> 22:06:49.920 align:start position:0% if your CPU fan 22:06:49.920 --> 22:06:52.246 align:start position:0% if your CPU fan has<22:06:50.280> stopped<22:06:50.696> working<22:06:50.824> or<22:06:51.176> this<22:06:51.360> tumors<22:06:51.784> dust 22:06:52.246 --> 22:06:52.256 align:start position:0% has stopped working or this tumors dust 22:06:52.256 --> 22:06:55.670 align:start position:0% has stopped working or this tumors dust or<22:06:52.440> dirt<22:06:52.744> inside<22:06:52.976> your<22:06:53.336> equipment<22:06:53.832> then<22:06:54.832> it 22:06:55.670 --> 22:06:55.680 align:start position:0% or dirt inside your equipment then it 22:06:55.680 --> 22:06:59.326 align:start position:0% or dirt inside your equipment then it starts<22:06:56.040> to<22:06:56.464> lock<22:06:57.296> up<22:06:57.536> and<22:06:58.144> finally<22:06:58.552> fail<22:06:58.856> I 22:06:59.326 --> 22:06:59.336 align:start position:0% starts to lock up and finally fail I 22:06:59.336 --> 22:07:02.270 align:start position:0% starts to lock up and finally fail I know<22:06:59.464> that's<22:06:59.640> happened<22:06:59.824> to<22:07:00.120> me 22:07:02.270 --> 22:07:02.280 align:start position:0% 22:07:02.280 --> 22:07:04.182 align:start position:0% since<22:07:02.696> heat<22:07:02.936> effects<22:07:03.296> of<22:07:03.360> reliability<22:07:03.832> we 22:07:04.182 --> 22:07:04.192 align:start position:0% since heat effects of reliability we 22:07:04.192 --> 22:07:06.526 align:start position:0% since heat effects of reliability we need<22:07:04.320> to<22:07:04.376> keep<22:07:04.496> it<22:07:04.680> cool<22:07:04.872> this<22:07:05.872> requires 22:07:06.526 --> 22:07:06.536 align:start position:0% need to keep it cool this requires 22:07:06.536 --> 22:07:09.950 align:start position:0% need to keep it cool this requires removing<22:07:07.376> the<22:07:07.800> hot<22:07:08.760> air<22:07:08.936> and<22:07:09.240> moving<22:07:09.600> in<22:07:09.720> cold 22:07:09.950 --> 22:07:09.960 align:start position:0% removing the hot air and moving in cold 22:07:09.960 --> 22:07:12.470 align:start position:0% removing the hot air and moving in cold air<22:07:10.192> just<22:07:10.496> like<22:07:10.616> your<22:07:10.800> PC<22:07:11.160> chassis<22:07:11.696> but<22:07:12.120> on<22:07:12.296> a 22:07:12.470 --> 22:07:12.480 align:start position:0% air just like your PC chassis but on a 22:07:12.480 --> 22:07:13.790 align:start position:0% air just like your PC chassis but on a much<22:07:12.600> larger<22:07:12.896> scale 22:07:13.790 --> 22:07:13.800 align:start position:0% much larger scale 22:07:13.800 --> 22:07:15.646 align:start position:0% much larger scale I'll<22:07:14.216> turn<22:07:14.464> cold<22:07:14.760> air<22:07:15.000> within<22:07:15.240> the<22:07:15.296> data 22:07:15.646 --> 22:07:15.656 align:start position:0% I'll turn cold air within the data 22:07:15.656 --> 22:07:17.926 align:start position:0% I'll turn cold air within the data center<22:07:16.192> shouldn't<22:07:16.744> be<22:07:16.856> mixed<22:07:17.216> and<22:07:17.640> for<22:07:17.824> this 22:07:17.926 --> 22:07:17.936 align:start position:0% center shouldn't be mixed and for this 22:07:17.936 --> 22:07:19.606 align:start position:0% center shouldn't be mixed and for this reason<22:07:18.120> you've<22:07:18.536> got<22:07:18.600> the<22:07:18.784> hot<22:07:18.960> oil<22:07:19.144> and<22:07:19.440> the 22:07:19.606 --> 22:07:19.616 align:start position:0% reason you've got the hot oil and the 22:07:19.616 --> 22:07:22.366 align:start position:0% reason you've got the hot oil and the cold<22:07:19.744> oil<22:07:20.160> Arrangement<22:07:20.824> this<22:07:21.720> is<22:07:21.832> for<22:07:22.080> your 22:07:22.366 --> 22:07:22.376 align:start position:0% cold oil Arrangement this is for your 22:07:22.376 --> 22:07:25.006 align:start position:0% cold oil Arrangement this is for your ventilation 22:07:25.006 --> 22:07:25.016 align:start position:0% ventilation 22:07:25.016 --> 22:07:26.814 align:start position:0% ventilation if<22:07:25.440> the<22:07:25.552> cold<22:07:25.744> air<22:07:25.920> mixes<22:07:26.280> with<22:07:26.400> a<22:07:26.512> hot<22:07:26.640> air 22:07:26.814 --> 22:07:26.824 align:start position:0% if the cold air mixes with a hot air 22:07:26.824 --> 22:07:28.134 align:start position:0% if the cold air mixes with a hot air without<22:07:27.056> going<22:07:27.296> through<22:07:27.480> the<22:07:27.600> equipment<22:07:27.896> then 22:07:28.134 --> 22:07:28.144 align:start position:0% without going through the equipment then 22:07:28.144 --> 22:07:31.846 align:start position:0% without going through the equipment then it<22:07:28.320> becomes<22:07:28.680> useless 22:07:31.846 --> 22:07:31.856 align:start position:0% 22:07:31.856 --> 22:07:34.182 align:start position:0% so<22:07:32.336> HVAC<22:07:32.936> stands<22:07:33.240> for<22:07:33.360> heating<22:07:33.656> ventilation 22:07:34.182 --> 22:07:34.192 align:start position:0% so HVAC stands for heating ventilation 22:07:34.192 --> 22:07:36.774 align:start position:0% so HVAC stands for heating ventilation and<22:07:34.440> cooling<22:07:34.856> which<22:07:35.104> is<22:07:35.280> an<22:07:35.464> entire<22:07:35.824> set<22:07:36.656> of 22:07:36.774 --> 22:07:36.784 align:start position:0% and cooling which is an entire set of 22:07:36.784 --> 22:07:39.470 align:start position:0% and cooling which is an entire set of systems<22:07:37.376> procedures<22:07:38.040> best<22:07:38.576> practices<22:07:39.056> and 22:07:39.470 --> 22:07:39.480 align:start position:0% systems procedures best practices and 22:07:39.480 --> 22:07:41.390 align:start position:0% systems procedures best practices and companies<22:07:39.784> that<22:07:39.960> will<22:07:40.080> help<22:07:40.256> you<22:07:40.496> plan<22:07:41.160> and 22:07:41.390 --> 22:07:41.400 align:start position:0% companies that will help you plan and 22:07:41.400 --> 22:07:43.542 align:start position:0% companies that will help you plan and manage<22:07:41.760> and<22:07:41.936> install<22:07:42.120> all<22:07:42.600> of<22:07:42.720> this 22:07:43.542 --> 22:07:43.552 align:start position:0% manage and install all of this 22:07:43.552 --> 22:07:45.646 align:start position:0% manage and install all of this provides<22:07:44.216> the<22:07:44.400> optimum<22:07:44.824> temperature<22:07:45.120> and 22:07:45.646 --> 22:07:45.656 align:start position:0% provides the optimum temperature and 22:07:45.656 --> 22:07:47.926 align:start position:0% provides the optimum temperature and indoor<22:07:46.080> air<22:07:46.256> quality<22:07:46.744> so<22:07:47.464> you've<22:07:47.696> obviously 22:07:47.926 --> 22:07:47.936 align:start position:0% indoor air quality so you've obviously 22:07:47.936 --> 22:07:49.494 align:start position:0% indoor air quality so you've obviously got<22:07:48.120> to<22:07:48.296> have<22:07:48.424> an<22:07:48.536> environment<22:07:48.896> that<22:07:49.192> works 22:07:49.494 --> 22:07:49.504 align:start position:0% got to have an environment that works 22:07:49.504 --> 22:07:51.950 align:start position:0% got to have an environment that works best<22:07:49.800> for<22:07:49.976> the<22:07:50.104> equipment<22:07:50.400> but<22:07:50.760> also<22:07:51.056> the 22:07:51.950 --> 22:07:51.960 align:start position:0% best for the equipment but also the 22:07:51.960 --> 22:07:53.926 align:start position:0% best for the equipment but also the engineers<22:07:52.440> can<22:07:52.800> go<22:07:53.040> in<22:07:53.216> and<22:07:53.400> manage<22:07:53.760> and 22:07:53.926 --> 22:07:53.936 align:start position:0% engineers can go in and manage and 22:07:53.936 --> 22:07:55.430 align:start position:0% engineers can go in and manage and survive<22:07:54.296> in 22:07:55.430 --> 22:07:55.440 align:start position:0% survive in 22:07:55.440 --> 22:07:57.350 align:start position:0% survive in the<22:07:55.920> HVAC<22:07:56.336> system<22:07:56.512> not<22:07:56.824> only<22:07:56.936> keeps<22:07:57.240> things 22:07:57.350 --> 22:07:57.360 align:start position:0% the HVAC system not only keeps things 22:07:57.360 --> 22:07:59.686 align:start position:0% the HVAC system not only keeps things cool<22:07:57.720> and<22:07:58.144> keeps<22:07:58.496> things<22:07:58.552> humid<22:07:59.104> obviously 22:07:59.686 --> 22:07:59.696 align:start position:0% cool and keeps things humid obviously 22:07:59.696 --> 22:08:01.734 align:start position:0% cool and keeps things humid obviously not<22:08:00.056> too<22:08:00.600> humid<22:08:00.960> but<22:08:01.192> there<22:08:01.256> has<22:08:01.440> to<22:08:01.552> be<22:08:01.616> a 22:08:01.734 --> 22:08:01.744 align:start position:0% not too humid but there has to be a 22:08:01.744 --> 22:08:04.366 align:start position:0% not too humid but there has to be a certain<22:08:01.920> level<22:08:02.160> of<22:08:02.336> humidity<22:08:02.824> in<22:08:03.120> there<22:08:03.376> and 22:08:04.366 --> 22:08:04.376 align:start position:0% certain level of humidity in there and 22:08:04.376 --> 22:08:08.862 align:start position:0% certain level of humidity in there and removes<22:08:04.856> contaminants<22:08:05.400> from<22:08:05.640> the<22:08:05.824> air<22:08:05.936> also 22:08:08.862 --> 22:08:08.872 align:start position:0% 22:08:08.872 --> 22:08:11.150 align:start position:0% cold<22:08:09.296> air<22:08:09.600> is<22:08:09.720> pumped<22:08:10.016> from<22:08:10.080> the<22:08:10.256> HVAC<22:08:10.976> system 22:08:11.150 --> 22:08:11.160 align:start position:0% cold air is pumped from the HVAC system 22:08:11.160 --> 22:08:13.966 align:start position:0% cold air is pumped from the HVAC system into<22:08:11.464> the<22:08:11.640> cold<22:08:11.824> aisle<22:08:12.296> as<22:08:12.960> an<22:08:13.144> as<22:08:13.504> an<22:08:13.680> input 22:08:13.966 --> 22:08:13.976 align:start position:0% into the cold aisle as an as an input 22:08:13.976 --> 22:08:15.710 align:start position:0% into the cold aisle as an as an input for<22:08:14.576> the<22:08:14.696> servers 22:08:15.710 --> 22:08:15.720 align:start position:0% for the servers 22:08:15.720 --> 22:08:17.566 align:start position:0% for the servers the<22:08:16.080> server<22:08:16.376> is<22:08:16.440> pulling<22:08:16.800> cold<22:08:16.976> air<22:08:17.216> from<22:08:17.400> the 22:08:17.566 --> 22:08:17.576 align:start position:0% the server is pulling cold air from the 22:08:17.576 --> 22:08:19.494 align:start position:0% the server is pulling cold air from the front<22:08:17.696> to<22:08:17.936> cool<22:08:18.120> themselves<22:08:18.536> and<22:08:19.256> they 22:08:19.494 --> 22:08:19.504 align:start position:0% front to cool themselves and they 22:08:19.504 --> 22:08:21.886 align:start position:0% front to cool themselves and they exhaust<22:08:19.856> hot<22:08:20.216> air<22:08:20.400> which<22:08:21.000> goes<22:08:21.296> into<22:08:21.424> the<22:08:21.656> hot 22:08:21.886 --> 22:08:21.896 align:start position:0% exhaust hot air which goes into the hot 22:08:21.896 --> 22:08:23.030 align:start position:0% exhaust hot air which goes into the hot tile 22:08:23.030 --> 22:08:23.040 align:start position:0% tile 22:08:23.040 --> 22:08:25.542 align:start position:0% tile now<22:08:23.576> my<22:08:23.872> experience<22:08:24.296> when<22:08:24.656> I've<22:08:24.832> gone<22:08:25.016> to<22:08:25.144> Data 22:08:25.542 --> 22:08:25.552 align:start position:0% now my experience when I've gone to Data 22:08:25.552 --> 22:08:28.542 align:start position:0% now my experience when I've gone to Data Centers<22:08:25.856> is<22:08:26.040> the<22:08:26.336> the<22:08:26.464> better<22:08:27.176> ones<22:08:27.656> I've<22:08:28.320> got 22:08:28.542 --> 22:08:28.552 align:start position:0% Centers is the the better ones I've got 22:08:28.552 --> 22:08:31.134 align:start position:0% Centers is the the better ones I've got doors<22:08:29.160> to<22:08:29.824> get<22:08:30.120> in<22:08:30.296> and<22:08:30.536> out<22:08:30.720> of<22:08:30.832> the<22:08:31.016> cool 22:08:31.134 --> 22:08:31.144 align:start position:0% doors to get in and out of the cool 22:08:31.144 --> 22:08:32.150 align:start position:0% doors to get in and out of the cool aisle 22:08:32.150 --> 22:08:32.160 align:start position:0% aisle 22:08:32.160 --> 22:08:33.710 align:start position:0% aisle the<22:08:32.696> Hostile 22:08:33.710 --> 22:08:33.720 align:start position:0% the Hostile 22:08:33.720 --> 22:08:34.910 align:start position:0% the Hostile um<22:08:33.784> they're<22:08:34.080> certainly<22:08:34.320> the<22:08:34.376> ones<22:08:34.552> I've<22:08:34.744> been 22:08:34.910 --> 22:08:34.920 align:start position:0% um they're certainly the ones I've been 22:08:34.920 --> 22:08:37.366 align:start position:0% um they're certainly the ones I've been to<22:08:35.040> don't<22:08:35.400> have<22:08:35.640> the<22:08:35.936> doors<22:08:36.240> so<22:08:36.960> you'll<22:08:37.256> be 22:08:37.366 --> 22:08:37.376 align:start position:0% to don't have the doors so you'll be 22:08:37.376 --> 22:08:38.990 align:start position:0% to don't have the doors so you'll be walking<22:08:37.552> through<22:08:37.800> an<22:08:38.040> area<22:08:38.160> that<22:08:38.464> feels<22:08:38.760> quite 22:08:38.990 --> 22:08:39.000 align:start position:0% walking through an area that feels quite 22:08:39.000 --> 22:08:41.094 align:start position:0% walking through an area that feels quite warm<22:08:39.360> you'll<22:08:39.960> open<22:08:40.144> the<22:08:40.320> door<22:08:40.440> to<22:08:40.680> go<22:08:40.800> to<22:08:40.920> the 22:08:41.094 --> 22:08:41.104 align:start position:0% warm you'll open the door to go to the 22:08:41.104 --> 22:08:43.542 align:start position:0% warm you'll open the door to go to the front<22:08:41.216> of<22:08:41.464> the<22:08:41.760> servers<22:08:42.720> to<22:08:42.896> connect<22:08:43.016> or<22:08:43.376> do 22:08:43.542 --> 22:08:43.552 align:start position:0% front of the servers to connect or do 22:08:43.552 --> 22:08:44.990 align:start position:0% front of the servers to connect or do whatever<22:08:43.800> obviously<22:08:44.400> shooting<22:08:44.640> the<22:08:44.872> door 22:08:44.990 --> 22:08:45.000 align:start position:0% whatever obviously shooting the door 22:08:45.000 --> 22:08:47.990 align:start position:0% whatever obviously shooting the door behind<22:08:45.296> you<22:08:45.480> and<22:08:46.016> it'll<22:08:46.320> be<22:08:46.552> very<22:08:47.336> cool<22:08:47.640> in 22:08:47.990 --> 22:08:48.000 align:start position:0% behind you and it'll be very cool in 22:08:48.000 --> 22:08:49.182 align:start position:0% behind you and it'll be very cool in fact<22:08:48.120> you'll<22:08:48.360> probably<22:08:48.480> need<22:08:48.720> to<22:08:48.832> wear<22:08:49.016> a 22:08:49.182 --> 22:08:49.192 align:start position:0% fact you'll probably need to wear a 22:08:49.192 --> 22:08:51.470 align:start position:0% fact you'll probably need to wear a couple<22:08:49.256> of<22:08:49.440> layers<22:08:49.744> of<22:08:49.856> clothing 22:08:51.470 --> 22:08:51.480 align:start position:0% couple of layers of clothing 22:08:51.480 --> 22:08:53.926 align:start position:0% couple of layers of clothing the<22:08:52.080> AC<22:08:52.192> duct<22:08:52.680> carries<22:08:53.040> the<22:08:53.216> hot<22:08:53.336> air<22:08:53.512> from<22:08:53.760> the 22:08:53.926 --> 22:08:53.936 align:start position:0% the AC duct carries the hot air from the 22:08:53.936 --> 22:08:56.862 align:start position:0% the AC duct carries the hot air from the hotel<22:08:54.120> to<22:08:54.656> the<22:08:54.784> HVAC<22:08:55.440> to<22:08:55.976> cool<22:08:56.160> it<22:08:56.400> again<22:08:56.576> and 22:08:56.862 --> 22:08:56.872 align:start position:0% hotel to the HVAC to cool it again and 22:08:56.872 --> 22:09:00.286 align:start position:0% hotel to the HVAC to cool it again and exhaust<22:08:57.240> it<22:08:57.480> elsewhere 22:09:00.286 --> 22:09:00.296 align:start position:0% 22:09:00.296 --> 22:09:03.710 align:start position:0% typical<22:09:01.016> hot<22:09:01.320> cold<22:09:01.616> oil<22:09:01.920> conditions<22:09:02.536> the<22:09:03.536> cold 22:09:03.710 --> 22:09:03.720 align:start position:0% typical hot cold oil conditions the cold 22:09:03.720 --> 22:09:06.166 align:start position:0% typical hot cold oil conditions the cold air<22:09:03.960> temperatures<22:09:04.256> range<22:09:04.680> from<22:09:04.856> 55<22:09:05.400> to<22:09:05.640> 78 22:09:06.166 --> 22:09:06.176 align:start position:0% air temperatures range from 55 to 78 22:09:06.176 --> 22:09:08.390 align:start position:0% air temperatures range from 55 to 78 Fahrenheit<22:09:06.784> they<22:09:07.504> haven't<22:09:07.744> listed<22:09:08.104> this<22:09:08.216> in 22:09:08.390 --> 22:09:08.400 align:start position:0% Fahrenheit they haven't listed this in 22:09:08.400 --> 22:09:10.366 align:start position:0% Fahrenheit they haven't listed this in Celsius<22:09:08.576> so<22:09:09.120> I<22:09:09.296> presume<22:09:09.600> this<22:09:09.720> is<22:09:09.832> for<22:09:10.016> the 22:09:10.366 --> 22:09:10.376 align:start position:0% Celsius so I presume this is for the 22:09:10.376 --> 22:09:12.950 align:start position:0% Celsius so I presume this is for the American<22:09:10.872> viewers<22:09:11.872> the<22:09:12.360> hot<22:09:12.536> oil<22:09:12.720> temperature 22:09:12.950 --> 22:09:12.960 align:start position:0% American viewers the hot oil temperature 22:09:12.960 --> 22:09:16.846 align:start position:0% American viewers the hot oil temperature goes<22:09:13.440> from<22:09:13.552> 73<22:09:14.160> to<22:09:14.576> 96<22:09:15.240> Fahrenheit 22:09:16.846 --> 22:09:16.856 align:start position:0% goes from 73 to 96 Fahrenheit 22:09:16.856 --> 22:09:18.590 align:start position:0% goes from 73 to 96 Fahrenheit and<22:09:17.400> the<22:09:17.576> amount<22:09:17.760> of<22:09:17.872> heat<22:09:18.000> carried<22:09:18.296> by<22:09:18.424> the 22:09:18.590 --> 22:09:18.600 align:start position:0% and the amount of heat carried by the 22:09:18.600 --> 22:09:20.566 align:start position:0% and the amount of heat carried by the stream<22:09:18.720> of<22:09:18.960> air<22:09:19.192> exiting<22:09:19.800> the<22:09:20.104> heat<22:09:20.216> load 22:09:20.566 --> 22:09:20.576 align:start position:0% stream of air exiting the heat load 22:09:20.576 --> 22:09:24.046 align:start position:0% stream of air exiting the heat load should<22:09:20.760> be<22:09:20.936> 15<22:09:21.176> to<22:09:21.480> 20<22:09:21.720> degrees<22:09:22.016> Fahrenheit 22:09:24.046 --> 22:09:24.056 align:start position:0% should be 15 to 20 degrees Fahrenheit 22:09:24.056 --> 22:09:26.390 align:start position:0% should be 15 to 20 degrees Fahrenheit rack<22:09:24.600> mount<22:09:24.784> servers<22:09:25.376> I<22:09:26.040> don't<22:09:26.160> know<22:09:26.280> if 22:09:26.390 --> 22:09:26.400 align:start position:0% rack mount servers I don't know if 22:09:26.400 --> 22:09:27.822 align:start position:0% rack mount servers I don't know if you've<22:09:26.576> seen<22:09:26.696> many<22:09:26.872> of<22:09:27.056> these<22:09:27.240> I've<22:09:27.424> seen<22:09:27.656> a 22:09:27.822 --> 22:09:27.832 align:start position:0% you've seen many of these I've seen a 22:09:27.832 --> 22:09:31.070 align:start position:0% you've seen many of these I've seen a lot<22:09:27.960> over<22:09:28.192> the<22:09:28.440> years<22:09:29.296> the<22:09:30.296> rack<22:09:30.480> contains<22:09:30.960> the 22:09:31.070 --> 22:09:31.080 align:start position:0% lot over the years the rack contains the 22:09:31.080 --> 22:09:32.750 align:start position:0% lot over the years the rack contains the servers<22:09:31.504> the<22:09:31.856> servers<22:09:32.280> have<22:09:32.400> a<22:09:32.576> different 22:09:32.750 --> 22:09:32.760 align:start position:0% servers the servers have a different 22:09:32.760 --> 22:09:34.750 align:start position:0% servers the servers have a different form<22:09:33.000> factor<22:09:33.480> than<22:09:33.600> your<22:09:33.784> normal<22:09:33.960> desktop 22:09:34.750 --> 22:09:34.760 align:start position:0% form factor than your normal desktop 22:09:34.760 --> 22:09:37.430 align:start position:0% form factor than your normal desktop servers<22:09:35.760> these<22:09:36.480> are<22:09:36.536> these<22:09:37.016> obviously<22:09:37.256> need 22:09:37.430 --> 22:09:37.440 align:start position:0% servers these are these obviously need 22:09:37.440 --> 22:09:38.414 align:start position:0% servers these are these obviously need to<22:09:37.552> be 22:09:38.414 --> 22:09:38.424 align:start position:0% to be 22:09:38.424 --> 22:09:42.230 align:start position:0% to be compliant<22:09:39.424> to<22:09:40.016> fit<22:09:40.256> into<22:09:40.440> a<22:09:41.160> rack<22:09:41.576> taking<22:09:41.824> over 22:09:42.230 --> 22:09:42.240 align:start position:0% compliant to fit into a rack taking over 22:09:42.240 --> 22:09:43.790 align:start position:0% compliant to fit into a rack taking over so<22:09:43.016> many 22:09:43.790 --> 22:09:43.800 align:start position:0% so many 22:09:43.800 --> 22:09:46.606 align:start position:0% so many um<22:09:43.856> units<22:09:44.576> uh<22:09:45.240> use<22:09:45.480> they<22:09:45.784> call<22:09:45.960> it<22:09:46.144> sometimes 22:09:46.606 --> 22:09:46.616 align:start position:0% um units uh use they call it sometimes 22:09:46.616 --> 22:09:49.366 align:start position:0% um units uh use they call it sometimes one<22:09:47.040> two<22:09:47.336> and<22:09:48.296> so<22:09:48.480> on 22:09:49.366 --> 22:09:49.376 align:start position:0% one two and so on 22:09:49.376 --> 22:09:52.246 align:start position:0% one two and so on they<22:09:49.976> need<22:09:50.216> to<22:09:50.280> have<22:09:50.464> the<22:09:50.640> correct<22:09:50.936> eyes<22:09:51.600> so 22:09:52.246 --> 22:09:52.256 align:start position:0% they need to have the correct eyes so 22:09:52.256 --> 22:09:54.046 align:start position:0% they need to have the correct eyes so you<22:09:52.440> can<22:09:52.552> screw<22:09:52.920> in<22:09:53.040> the<22:09:53.280> screws<22:09:53.576> to<22:09:53.760> hold<22:09:53.872> it 22:09:54.046 --> 22:09:54.056 align:start position:0% you can screw in the screws to hold it 22:09:54.056 --> 22:09:56.750 align:start position:0% you can screw in the screws to hold it into<22:09:54.176> place<22:09:54.424> securely<22:09:54.896> front<22:09:55.256> and<22:09:55.440> back<22:09:55.760> and 22:09:56.750 --> 22:09:56.760 align:start position:0% into place securely front and back and 22:09:56.760 --> 22:09:59.926 align:start position:0% into place securely front and back and most<22:09:57.296> of<22:09:57.480> them<22:09:57.600> actually<22:09:57.832> you<22:09:58.496> can<22:09:58.616> pull<22:09:58.936> open 22:09:59.926 --> 22:09:59.936 align:start position:0% most of them actually you can pull open 22:09:59.936 --> 22:10:02.862 align:start position:0% most of them actually you can pull open so<22:10:00.656> it<22:10:00.832> pulls<22:10:01.144> out<22:10:01.320> from<22:10:01.552> the<22:10:01.744> rest<22:10:01.920> and<22:10:02.696> you 22:10:02.862 --> 22:10:02.872 align:start position:0% so it pulls out from the rest and you 22:10:02.872 --> 22:10:04.486 align:start position:0% so it pulls out from the rest and you can<22:10:03.000> do<22:10:03.240> various<22:10:03.536> things<22:10:03.720> without<22:10:03.896> having<22:10:04.256> to 22:10:04.486 --> 22:10:04.496 align:start position:0% can do various things without having to 22:10:04.496 --> 22:10:07.246 align:start position:0% can do various things without having to shut<22:10:04.976> down<22:10:05.216> the<22:10:05.512> server<22:10:05.872> or<22:10:06.720> the<22:10:06.896> cables 22:10:07.246 --> 22:10:07.256 align:start position:0% shut down the server or the cables 22:10:07.256 --> 22:10:09.710 align:start position:0% shut down the server or the cables coming<22:10:07.376> loose<22:10:07.856> larger<22:10:08.760> up<22:10:09.000> Mount<22:10:09.120> servers<22:10:09.600> and 22:10:09.710 --> 22:10:09.720 align:start position:0% coming loose larger up Mount servers and 22:10:09.720 --> 22:10:11.150 align:start position:0% coming loose larger up Mount servers and Equipment<22:10:09.960> are<22:10:10.144> stored<22:10:10.440> at<22:10:10.496> the<22:10:10.680> bottom<22:10:10.920> so 22:10:11.150 --> 22:10:11.160 align:start position:0% Equipment are stored at the bottom so 22:10:11.160 --> 22:10:12.886 align:start position:0% Equipment are stored at the bottom so the<22:10:11.280> heavier<22:10:11.512> stuff<22:10:11.696> at<22:10:11.872> the<22:10:12.056> bottom<22:10:12.360> to 22:10:12.886 --> 22:10:12.896 align:start position:0% the heavier stuff at the bottom to 22:10:12.896 --> 22:10:15.110 align:start position:0% the heavier stuff at the bottom to ensure<22:10:13.192> the<22:10:13.320> rack<22:10:13.552> doesn't<22:10:13.800> tip<22:10:14.160> over 22:10:15.110 --> 22:10:15.120 align:start position:0% ensure the rack doesn't tip over 22:10:15.120 --> 22:10:17.814 align:start position:0% ensure the rack doesn't tip over Rock<22:10:15.656> loading<22:10:16.192> should<22:10:16.376> not<22:10:16.552> only<22:10:16.680> seed<22:10:17.104> the 22:10:17.814 --> 22:10:17.824 align:start position:0% Rock loading should not only seed the 22:10:17.824 --> 22:10:20.454 align:start position:0% Rock loading should not only seed the weight<22:10:18.080> rated<22:10:19.080> capacity<22:10:19.616> of<22:10:19.976> the<22:10:20.104> raised 22:10:20.454 --> 22:10:20.464 align:start position:0% weight rated capacity of the raised 22:10:20.464 --> 22:10:22.182 align:start position:0% weight rated capacity of the raised floor<22:10:20.576> to<22:10:21.176> ensure<22:10:21.424> that<22:10:21.600> the<22:10:21.720> race<22:10:21.896> floor 22:10:22.182 --> 22:10:22.192 align:start position:0% floor to ensure that the race floor 22:10:22.192 --> 22:10:23.454 align:start position:0% floor to ensure that the race floor doesn't<22:10:22.496> collapse<22:10:22.920> because<22:10:23.160> it's 22:10:23.454 --> 22:10:23.464 align:start position:0% doesn't collapse because it's 22:10:23.464 --> 22:10:25.542 align:start position:0% doesn't collapse because it's overweighted<22:10:24.176> everything<22:10:24.832> has<22:10:25.256> to<22:10:25.376> be 22:10:25.542 --> 22:10:25.552 align:start position:0% overweighted everything has to be 22:10:25.552 --> 22:10:28.246 align:start position:0% overweighted everything has to be documented<22:10:26.336> planned<22:10:27.296> and<22:10:27.424> measured<22:10:27.784> so<22:10:28.016> you 22:10:28.246 --> 22:10:28.256 align:start position:0% documented planned and measured so you 22:10:28.256 --> 22:10:31.846 align:start position:0% documented planned and measured so you spread<22:10:28.800> load<22:10:29.576> over<22:10:29.936> inside<22:10:30.536> one<22:10:30.896> rack<22:10:31.320> and 22:10:31.846 --> 22:10:31.856 align:start position:0% spread load over inside one rack and 22:10:31.856 --> 22:10:34.670 align:start position:0% spread load over inside one rack and among<22:10:32.160> a<22:10:32.512> multitude<22:10:33.000> of<22:10:33.240> racks<22:10:33.784> so<22:10:34.440> you<22:10:34.616> can 22:10:34.670 --> 22:10:34.680 align:start position:0% among a multitude of racks so you can 22:10:34.680 --> 22:10:36.230 align:start position:0% among a multitude of racks so you can have<22:10:34.800> the<22:10:34.920> heavier<22:10:35.216> stuff<22:10:35.400> going<22:10:35.696> at<22:10:36.056> the 22:10:36.230 --> 22:10:36.240 align:start position:0% have the heavier stuff going at the 22:10:36.240 --> 22:10:38.686 align:start position:0% have the heavier stuff going at the bottom<22:10:36.536> of<22:10:36.896> 10<22:10:37.080> different<22:10:37.320> racks<22:10:37.920> the<22:10:38.464> next 22:10:38.686 --> 22:10:38.696 align:start position:0% bottom of 10 different racks the next 22:10:38.696 --> 22:10:41.094 align:start position:0% bottom of 10 different racks the next heaviest<22:10:39.120> goes<22:10:39.656> on<22:10:39.832> top<22:10:40.016> on<22:10:40.680> 10<22:10:40.856> different 22:10:41.094 --> 22:10:41.104 align:start position:0% heaviest goes on top on 10 different 22:10:41.104 --> 22:10:43.846 align:start position:0% heaviest goes on top on 10 different racks<22:10:41.576> and<22:10:42.120> so<22:10:42.296> on<22:10:42.536> rather<22:10:43.144> than<22:10:43.256> having<22:10:43.552> one 22:10:43.846 --> 22:10:43.856 align:start position:0% racks and so on rather than having one 22:10:43.856 --> 22:10:45.822 align:start position:0% racks and so on rather than having one rack<22:10:44.160> with<22:10:44.336> all<22:10:44.512> the<22:10:44.640> heavier<22:10:44.936> stuff<22:10:45.240> because 22:10:45.822 --> 22:10:45.832 align:start position:0% rack with all the heavier stuff because 22:10:45.832 --> 22:10:47.814 align:start position:0% rack with all the heavier stuff because it<22:10:46.144> could<22:10:46.256> if<22:10:46.744> it<22:10:46.856> breaches<22:10:47.160> a<22:10:47.336> loading<22:10:47.640> it's 22:10:47.814 --> 22:10:47.824 align:start position:0% it could if it breaches a loading it's 22:10:47.824 --> 22:10:48.822 align:start position:0% it could if it breaches a loading it's obviously<22:10:48.056> going<22:10:48.176> to<22:10:48.296> break<22:10:48.424> through<22:10:48.600> the 22:10:48.822 --> 22:10:48.832 align:start position:0% obviously going to break through the 22:10:48.832 --> 22:10:50.862 align:start position:0% obviously going to break through the floor 22:10:50.862 --> 22:10:50.872 align:start position:0% floor 22:10:50.872 --> 22:10:52.910 align:start position:0% floor uh<22:10:51.424> the<22:10:51.600> power<22:10:51.720> distribution<22:10:52.256> your<22:10:52.552> data 22:10:52.910 --> 22:10:52.920 align:start position:0% uh the power distribution your data 22:10:52.920 --> 22:10:54.414 align:start position:0% uh the power distribution your data center<22:10:52.976> is<22:10:53.160> normally<22:10:53.400> connected<22:10:53.824> to<22:10:54.000> multiple 22:10:54.414 --> 22:10:54.424 align:start position:0% center is normally connected to multiple 22:10:54.424 --> 22:10:55.790 align:start position:0% center is normally connected to multiple power<22:10:54.720> grids 22:10:55.790 --> 22:10:55.800 align:start position:0% power grids 22:10:55.800 --> 22:10:57.646 align:start position:0% power grids um<22:10:55.856> and<22:10:56.160> even<22:10:56.336> after<22:10:56.696> that<22:10:57.000> you<22:10:57.296> could<22:10:57.480> have 22:10:57.646 --> 22:10:57.656 align:start position:0% um and even after that you could have 22:10:57.656 --> 22:10:59.326 align:start position:0% um and even after that you could have the<22:10:57.960> one<22:10:58.080> the<22:10:58.320> one<22:10:58.496> I<22:10:58.680> used<22:10:58.920> to<22:10:59.040> have<22:10:59.160> my 22:10:59.326 --> 22:10:59.336 align:start position:0% the one the one I used to have my 22:10:59.336 --> 22:11:01.366 align:start position:0% the one the one I used to have my equipment<22:10:59.696> at<22:11:00.000> had 22:11:01.366 --> 22:11:01.376 align:start position:0% equipment at had 22:11:01.376 --> 22:11:02.030 align:start position:0% equipment at had um 22:11:02.030 --> 22:11:02.040 align:start position:0% um 22:11:02.040 --> 22:11:04.182 align:start position:0% um massive<22:11:02.760> generators<22:11:03.360> that<22:11:03.656> would<22:11:03.784> take<22:11:03.960> over 22:11:04.182 --> 22:11:04.192 align:start position:0% massive generators that would take over 22:11:04.192 --> 22:11:05.814 align:start position:0% massive generators that would take over and<22:11:04.496> it<22:11:04.680> wasn't<22:11:04.744> one<22:11:05.040> generator<22:11:05.464> the 22:11:05.814 --> 22:11:05.824 align:start position:0% and it wasn't one generator the 22:11:05.824 --> 22:11:07.910 align:start position:0% and it wasn't one generator the generator<22:11:06.176> had<22:11:06.480> a<22:11:06.656> backup<22:11:06.896> generator<22:11:07.376> as<22:11:07.744> well 22:11:07.910 --> 22:11:07.920 align:start position:0% generator had a backup generator as well 22:11:07.920 --> 22:11:11.030 align:start position:0% generator had a backup generator as well so<22:11:08.640> there's<22:11:08.872> three<22:11:09.120> levels<22:11:09.536> of<22:11:09.784> redundancy<22:11:10.680> in 22:11:11.030 --> 22:11:11.040 align:start position:0% so there's three levels of redundancy in 22:11:11.040 --> 22:11:12.950 align:start position:0% so there's three levels of redundancy in case<22:11:11.160> there<22:11:11.400> was<22:11:11.576> a<22:11:11.824> power<22:11:12.360> cut<22:11:12.600> for<22:11:12.832> whatever 22:11:12.950 --> 22:11:12.960 align:start position:0% case there was a power cut for whatever 22:11:12.960 --> 22:11:14.390 align:start position:0% case there was a power cut for whatever reason 22:11:14.390 --> 22:11:14.400 align:start position:0% reason 22:11:14.400 --> 22:11:16.486 align:start position:0% reason if<22:11:14.936> you've<22:11:15.120> got<22:11:15.176> two<22:11:15.360> grids<22:11:15.784> if<22:11:15.896> power<22:11:16.080> is<22:11:16.320> lost 22:11:16.486 --> 22:11:16.496 align:start position:0% if you've got two grids if power is lost 22:11:16.496 --> 22:11:18.350 align:start position:0% if you've got two grids if power is lost on<22:11:16.680> one<22:11:16.920> grid<22:11:17.216> and<22:11:17.464> certainly<22:11:17.760> where<22:11:18.000> I<22:11:18.176> live 22:11:18.350 --> 22:11:18.360 align:start position:0% on one grid and certainly where I live 22:11:18.360 --> 22:11:21.046 align:start position:0% on one grid and certainly where I live in<22:11:18.720> Australia<22:11:19.144> you<22:11:19.440> get<22:11:19.616> power<22:11:19.856> Cuts<22:11:20.336> quite 22:11:21.046 --> 22:11:21.056 align:start position:0% in Australia you get power Cuts quite 22:11:21.056 --> 22:11:25.182 align:start position:0% in Australia you get power Cuts quite regularly<22:11:21.896> which<22:11:22.192> is<22:11:22.320> a<22:11:22.496> strange<22:11:22.856> phenomenon 22:11:25.182 --> 22:11:25.192 align:start position:0% regularly which is a strange phenomenon 22:11:25.192 --> 22:11:27.166 align:start position:0% regularly which is a strange phenomenon now<22:11:25.744> to<22:11:26.040> experience 22:11:27.166 --> 22:11:27.176 align:start position:0% now to experience 22:11:27.176 --> 22:11:29.926 align:start position:0% now to experience nowadays<22:11:28.080> for<22:11:28.496> devices<22:11:29.280> with<22:11:29.576> redundant 22:11:29.926 --> 22:11:29.936 align:start position:0% nowadays for devices with redundant 22:11:29.936 --> 22:11:31.790 align:start position:0% nowadays for devices with redundant power<22:11:30.176> supplies<22:11:30.536> power<22:11:30.832> comes<22:11:31.192> from<22:11:31.376> separate 22:11:31.790 --> 22:11:31.800 align:start position:0% power supplies power comes from separate 22:11:31.800 --> 22:11:34.790 align:start position:0% power supplies power comes from separate circuits<22:11:32.400> providing<22:11:33.360> redundancy 22:11:34.790 --> 22:11:34.800 align:start position:0% circuits providing redundancy 22:11:34.800 --> 22:11:37.310 align:start position:0% circuits providing redundancy so<22:11:35.400> it<22:11:35.824> would<22:11:35.936> be 22:11:37.310 --> 22:11:37.320 align:start position:0% so it would be 22:11:37.320 --> 22:11:39.046 align:start position:0% so it would be um it<22:11:37.744> wouldn't<22:11:37.856> be<22:11:38.040> great<22:11:38.216> redundancy<22:11:38.872> to 22:11:39.046 --> 22:11:39.056 align:start position:0% um it wouldn't be great redundancy to 22:11:39.056 --> 22:11:40.542 align:start position:0% um it wouldn't be great redundancy to have<22:11:39.176> your<22:11:39.296> redundant<22:11:39.720> power<22:11:39.960> supply<22:11:40.144> both 22:11:40.542 --> 22:11:40.552 align:start position:0% have your redundant power supply both 22:11:40.552 --> 22:11:43.430 align:start position:0% have your redundant power supply both connected<22:11:41.160> to<22:11:42.000> the<22:11:42.296> same<22:11:42.720> extension<22:11:43.256> lead 22:11:43.430 --> 22:11:43.440 align:start position:0% connected to the same extension lead 22:11:43.440 --> 22:11:45.110 align:start position:0% connected to the same extension lead because<22:11:43.800> if<22:11:44.280> the 22:11:45.110 --> 22:11:45.120 align:start position:0% because if the 22:11:45.120 --> 22:11:47.326 align:start position:0% because if the extension<22:11:45.896> lead<22:11:46.080> goes<22:11:46.496> down<22:11:46.616> or<22:11:46.976> the<22:11:47.160> power 22:11:47.326 --> 22:11:47.336 align:start position:0% extension lead goes down or the power 22:11:47.336 --> 22:11:49.790 align:start position:0% extension lead goes down or the power supply<22:11:47.720> providing<22:11:48.720> power<22:11:49.080> to<22:11:49.320> the<22:11:49.504> extension 22:11:49.790 --> 22:11:49.800 align:start position:0% supply providing power to the extension 22:11:49.800 --> 22:11:51.350 align:start position:0% supply providing power to the extension lead<22:11:49.976> then<22:11:50.280> you<22:11:50.464> lose<22:11:50.640> both<22:11:50.936> your<22:11:51.120> power 22:11:51.350 --> 22:11:51.360 align:start position:0% lead then you lose both your power 22:11:51.360 --> 22:11:54.470 align:start position:0% lead then you lose both your power supplies<22:11:51.976> redundant<22:11:52.976> and<22:11:53.104> Main 22:11:54.470 --> 22:11:54.480 align:start position:0% supplies redundant and Main 22:11:54.480 --> 22:11:57.526 align:start position:0% supplies redundant and Main as<22:11:55.256> a<22:11:55.504> data<22:11:55.856> centers<22:11:56.216> power<22:11:56.400> requirements<22:11:57.120> are 22:11:57.526 --> 22:11:57.536 align:start position:0% as a data centers power requirements are 22:11:57.536 --> 22:11:59.270 align:start position:0% as a data centers power requirements are determined<22:11:58.016> by<22:11:58.192> taking<22:11:58.376> into<22:11:58.680> account<22:11:58.920> the 22:11:59.270 --> 22:11:59.280 align:start position:0% determined by taking into account the 22:11:59.280 --> 22:12:01.670 align:start position:0% determined by taking into account the power<22:11:59.936> requirements<22:12:00.480> of<22:12:00.720> all<22:12:01.016> the<22:12:01.256> equipment 22:12:01.670 --> 22:12:01.680 align:start position:0% power requirements of all the equipment 22:12:01.680 --> 22:12:04.366 align:start position:0% power requirements of all the equipment and<22:12:02.400> you've<22:12:02.576> got<22:12:02.760> a<22:12:03.000> feature 22:12:04.366 --> 22:12:04.376 align:start position:0% and you've got a feature 22:12:04.376 --> 22:12:06.822 align:start position:0% and you've got a feature um<22:12:04.440> future<22:12:04.856> growth<22:12:05.464> so<22:12:06.056> you<22:12:06.240> can't<22:12:06.360> just<22:12:06.600> plan 22:12:06.822 --> 22:12:06.832 align:start position:0% um future growth so you can't just plan 22:12:06.832 --> 22:12:09.526 align:start position:0% um future growth so you can't just plan for<22:12:07.144> what<22:12:07.376> you<22:12:07.744> need<22:12:08.280> now<22:12:08.872> you<22:12:09.056> need<22:12:09.240> to<22:12:09.360> plan 22:12:09.526 --> 22:12:09.536 align:start position:0% for what you need now you need to plan 22:12:09.536 --> 22:12:12.590 align:start position:0% for what you need now you need to plan for<22:12:10.016> however<22:12:10.744> many<22:12:11.040> years<22:12:11.760> in<22:12:12.056> the<22:12:12.176> future<22:12:12.296> in 22:12:12.590 --> 22:12:12.600 align:start position:0% for however many years in the future in 22:12:12.600 --> 22:12:15.110 align:start position:0% for however many years in the future in the<22:12:12.784> company's<22:12:13.016> business<22:12:13.320> plan 22:12:15.110 --> 22:12:15.120 align:start position:0% the company's business plan 22:12:15.120 --> 22:12:17.150 align:start position:0% the company's business plan uh<22:12:15.832> you<22:12:16.016> need<22:12:16.192> to<22:12:16.320> ground<22:12:16.496> all<22:12:16.744> equipment 22:12:17.150 --> 22:12:17.160 align:start position:0% uh you need to ground all equipment 22:12:17.160 --> 22:12:18.950 align:start position:0% uh you need to ground all equipment separate<22:12:17.760> to 22:12:18.950 --> 22:12:18.960 align:start position:0% separate to 22:12:18.960 --> 22:12:22.006 align:start position:0% separate to um<22:12:19.016> other<22:12:19.504> grounds 22:12:22.006 --> 22:12:22.016 align:start position:0% um other grounds 22:12:22.016 --> 22:12:25.006 align:start position:0% um other grounds fire<22:12:22.680> and<22:12:23.464> demand<22:12:23.872> for<22:12:24.056> the<22:12:24.240> power<22:12:24.480> increases 22:12:25.006 --> 22:12:25.016 align:start position:0% fire and demand for the power increases 22:12:25.016 --> 22:12:26.326 align:start position:0% fire and demand for the power increases with<22:12:25.376> the 22:12:26.326 --> 22:12:26.336 align:start position:0% with the 22:12:26.336 --> 22:12:28.966 align:start position:0% with the um<22:12:26.464> amount<22:12:27.240> of<22:12:27.360> equipment<22:12:27.784> a<22:12:28.680> lot<22:12:28.800> of<22:12:28.856> the 22:12:28.966 --> 22:12:28.976 align:start position:0% um amount of equipment a lot of the 22:12:28.976 --> 22:12:30.606 align:start position:0% um amount of equipment a lot of the cream<22:12:29.160> equipment<22:12:29.696> with<22:12:30.000> increased<22:12:30.360> power 22:12:30.606 --> 22:12:30.616 align:start position:0% cream equipment with increased power 22:12:30.616 --> 22:12:34.182 align:start position:0% cream equipment with increased power consumption<22:12:31.616> I<22:12:32.336> can<22:12:32.576> find<22:12:32.760> a<22:12:33.056> small<22:12:33.656> spaces 22:12:34.182 --> 22:12:34.192 align:start position:0% consumption I can find a small spaces 22:12:34.192 --> 22:12:37.182 align:start position:0% consumption I can find a small spaces and<22:12:34.440> susceptible<22:12:34.856> to<22:12:35.104> fire<22:12:35.336> accidents 22:12:37.182 --> 22:12:37.192 align:start position:0% and susceptible to fire accidents 22:12:37.192 --> 22:12:39.246 align:start position:0% and susceptible to fire accidents again<22:12:37.552> this<22:12:37.856> is<22:12:37.976> down<22:12:38.216> there<22:12:38.576> due<22:12:38.936> to<22:12:39.056> heat 22:12:39.246 --> 22:12:39.256 align:start position:0% again this is down there due to heat 22:12:39.256 --> 22:12:44.270 align:start position:0% again this is down there due to heat obviously<22:12:40.256> fire<22:12:40.496> will<22:12:40.920> be<22:12:41.464> catastrophic 22:12:44.270 --> 22:12:44.280 align:start position:0% 22:12:44.280 --> 22:12:46.670 align:start position:0% data<22:12:45.176> centers<22:12:45.424> are<22:12:45.600> fire<22:12:45.784> detection<22:12:46.144> systems 22:12:46.670 --> 22:12:46.680 align:start position:0% data centers are fire detection systems 22:12:46.680 --> 22:12:48.414 align:start position:0% data centers are fire detection systems that<22:12:46.800> detect<22:12:47.216> the<22:12:47.336> fires<22:12:47.696> where<22:12:48.000> they<22:12:48.120> detect 22:12:48.414 --> 22:12:48.424 align:start position:0% that detect the fires where they detect 22:12:48.424 --> 22:12:50.502 align:start position:0% that detect the fires where they detect smoke<22:12:48.656> I<22:12:48.960> think<22:12:49.080> before<22:12:49.376> the<22:12:49.680> fire 22:12:50.502 --> 22:12:50.512 align:start position:0% smoke I think before the fire 22:12:50.512 --> 22:12:52.606 align:start position:0% smoke I think before the fire you've<22:12:51.120> got<22:12:51.176> portable<22:12:51.600> fire<22:12:51.896> extinguishers 22:12:52.606 --> 22:12:52.616 align:start position:0% you've got portable fire extinguishers 22:12:52.616 --> 22:12:55.310 align:start position:0% you've got portable fire extinguishers for<22:12:53.040> engineers<22:12:53.576> to<22:12:53.872> use<22:12:54.056> if<22:12:54.296> they 22:12:55.310 --> 22:12:55.320 align:start position:0% for engineers to use if they 22:12:55.320 --> 22:12:57.950 align:start position:0% for engineers to use if they somehow<22:12:56.104> set<22:12:56.464> something<22:12:56.696> on<22:12:57.000> fire<22:12:57.176> or<22:12:57.600> see<22:12:57.784> a 22:12:57.950 --> 22:12:57.960 align:start position:0% somehow set something on fire or see a 22:12:57.960 --> 22:12:59.206 align:start position:0% somehow set something on fire or see a small<22:12:58.080> fire 22:12:59.206 --> 22:12:59.216 align:start position:0% small fire 22:12:59.216 --> 22:13:01.430 align:start position:0% small fire data<22:12:59.872> centers<22:13:00.176> have<22:13:00.360> emergency<22:13:00.656> power<22:13:01.192> off 22:13:01.430 --> 22:13:01.440 align:start position:0% data centers have emergency power off 22:13:01.440 --> 22:13:03.286 align:start position:0% data centers have emergency power off switches<22:13:01.856> which<22:13:02.104> are<22:13:02.216> big<22:13:02.336> red<22:13:02.512> patents<22:13:03.120> on 22:13:03.286 --> 22:13:03.296 align:start position:0% switches which are big red patents on 22:13:03.296 --> 22:13:08.094 align:start position:0% switches which are big red patents on the<22:13:03.360> wall<22:13:03.480> that<22:13:04.144> cut<22:13:04.320> off<22:13:04.496> all<22:13:04.856> power 22:13:08.094 --> 22:13:08.104 align:start position:0% 22:13:08.104 --> 22:13:11.526 align:start position:0% obviously<22:13:08.576> if<22:13:08.696> you<22:13:08.872> do<22:13:09.056> that<22:13:09.240> it's<22:13:10.256> um<22:13:10.256> a 22:13:11.526 --> 22:13:11.536 align:start position:0% obviously if you do that it's um a 22:13:11.536 --> 22:13:14.094 align:start position:0% obviously if you do that it's um a constitutes<22:13:12.536> an<22:13:12.656> emergency<22:13:12.960> because<22:13:13.504> all<22:13:13.920> the 22:13:14.094 --> 22:13:14.104 align:start position:0% constitutes an emergency because all the 22:13:14.104 --> 22:13:17.206 align:start position:0% constitutes an emergency because all the servers<22:13:14.512> don't<22:13:15.056> really<22:13:15.832> um<22:13:15.832> deal<22:13:16.744> with<22:13:17.040> hard 22:13:17.206 --> 22:13:17.216 align:start position:0% servers don't really um deal with hard 22:13:17.216 --> 22:13:18.950 align:start position:0% servers don't really um deal with hard power<22:13:17.464> shutdowns<22:13:18.120> very<22:13:18.296> well<22:13:18.480> they<22:13:18.656> normally 22:13:18.950 --> 22:13:18.960 align:start position:0% power shutdowns very well they normally 22:13:18.960 --> 22:13:21.430 align:start position:0% power shutdowns very well they normally need<22:13:19.616> to<22:13:19.744> be<22:13:19.920> correctly<22:13:20.824> um<22:13:20.824> shut<22:13:21.176> down 22:13:21.430 --> 22:13:21.440 align:start position:0% need to be correctly um shut down 22:13:21.440 --> 22:13:24.414 align:start position:0% need to be correctly um shut down following<22:13:22.440> procedures<22:13:23.176> faster<22:13:24.176> person 22:13:24.414 --> 22:13:24.424 align:start position:0% following procedures faster person 22:13:24.424 --> 22:13:26.326 align:start position:0% following procedures faster person agents<22:13:24.896> put<22:13:25.144> out<22:13:25.320> the<22:13:25.504> fire 22:13:26.326 --> 22:13:26.336 align:start position:0% agents put out the fire 22:13:26.336 --> 22:13:28.366 align:start position:0% agents put out the fire you've<22:13:26.872> got<22:13:26.936> to<22:13:27.120> choose<22:13:27.296> the<22:13:27.536> correct<22:13:27.832> one 22:13:28.366 --> 22:13:28.376 align:start position:0% you've got to choose the correct one 22:13:28.376 --> 22:13:30.414 align:start position:0% you've got to choose the correct one obviously<22:13:29.336> if<22:13:29.464> you<22:13:29.576> even<22:13:29.696> if<22:13:29.936> you<22:13:30.000> go<22:13:30.120> to<22:13:30.240> a 22:13:30.414 --> 22:13:30.424 align:start position:0% obviously if you even if you go to a 22:13:30.424 --> 22:13:32.270 align:start position:0% obviously if you even if you go to a local<22:13:30.536> hardware<22:13:30.832> store<22:13:31.256> and<22:13:31.744> choose<22:13:32.040> a<22:13:32.160> fire 22:13:32.270 --> 22:13:32.280 align:start position:0% local hardware store and choose a fire 22:13:32.280 --> 22:13:34.966 align:start position:0% local hardware store and choose a fire extinguisher<22:13:32.936> there's<22:13:33.896> some<22:13:34.080> for<22:13:34.616> um<22:13:34.616> the 22:13:34.966 --> 22:13:34.976 align:start position:0% extinguisher there's some for um the 22:13:34.976 --> 22:13:37.734 align:start position:0% extinguisher there's some for um the kitchen<22:13:35.160> some<22:13:35.576> for<22:13:35.760> papers<22:13:36.296> and<22:13:37.080> some<22:13:37.320> for<22:13:37.504> car 22:13:37.734 --> 22:13:37.744 align:start position:0% kitchen some for papers and some for car 22:13:37.744 --> 22:13:40.134 align:start position:0% kitchen some for papers and some for car fires 22:13:40.134 --> 22:13:40.144 align:start position:0% fires 22:13:40.144 --> 22:13:42.414 align:start position:0% fires there<22:13:40.552> are<22:13:40.680> three<22:13:40.800> types<22:13:41.104> wet<22:13:41.400> pipe<22:13:41.760> dry<22:13:42.000> pipe 22:13:42.414 --> 22:13:42.424 align:start position:0% there are three types wet pipe dry pipe 22:13:42.424 --> 22:13:43.846 align:start position:0% there are three types wet pipe dry pipe and<22:13:42.600> gas 22:13:43.846 --> 22:13:43.856 align:start position:0% and gas 22:13:43.856 --> 22:13:46.670 align:start position:0% and gas the<22:13:44.280> wet<22:13:44.400> pipe<22:13:44.824> is<22:13:44.936> basically<22:13:45.360> a<22:13:45.784> water<22:13:46.016> that's 22:13:46.670 --> 22:13:46.680 align:start position:0% the wet pipe is basically a water that's 22:13:46.680 --> 22:13:49.606 align:start position:0% the wet pipe is basically a water that's held<22:13:47.040> within<22:13:47.280> the<22:13:47.400> pipe<22:13:47.760> under<22:13:48.240> pressure<22:13:48.616> and 22:13:49.606 --> 22:13:49.616 align:start position:0% held within the pipe under pressure and 22:13:49.616 --> 22:13:51.166 align:start position:0% held within the pipe under pressure and it<22:13:49.744> breaks<22:13:50.104> a<22:13:50.216> little<22:13:50.336> seal<22:13:50.640> which<22:13:50.872> you<22:13:51.056> can 22:13:51.166 --> 22:13:51.176 align:start position:0% it breaks a little seal which you can 22:13:51.176 --> 22:13:53.454 align:start position:0% it breaks a little seal which you can see<22:13:51.360> in<22:13:51.896> the<22:13:52.192> picture<22:13:52.616> there<22:13:52.920> the<22:13:53.104> little<22:13:53.280> red 22:13:53.454 --> 22:13:53.464 align:start position:0% see in the picture there the little red 22:13:53.464 --> 22:13:56.206 align:start position:0% see in the picture there the little red seal<22:13:53.872> and<22:13:54.536> that<22:13:55.016> um<22:13:55.016> when<22:13:55.552> that<22:13:55.680> breaks<22:13:56.040> it 22:13:56.206 --> 22:13:56.216 align:start position:0% seal and that um when that breaks it 22:13:56.216 --> 22:13:58.246 align:start position:0% seal and that um when that breaks it lets<22:13:56.576> the<22:13:56.696> water<22:13:56.936> come<22:13:57.296> out 22:13:58.246 --> 22:13:58.256 align:start position:0% lets the water come out 22:13:58.256 --> 22:14:00.590 align:start position:0% lets the water come out and<22:13:58.800> obviously<22:13:59.216> soaks<22:14:00.120> everything<22:14:00.296> with 22:14:00.590 --> 22:14:00.600 align:start position:0% and obviously soaks everything with 22:14:00.600 --> 22:14:02.150 align:start position:0% and obviously soaks everything with water<22:14:00.832> and<22:14:01.320> that's<22:14:01.440> the<22:14:01.680> end<22:14:01.856> of<22:14:02.040> your 22:14:02.150 --> 22:14:02.160 align:start position:0% water and that's the end of your 22:14:02.160 --> 22:14:03.646 align:start position:0% water and that's the end of your equipment 22:14:03.646 --> 22:14:03.656 align:start position:0% equipment 22:14:03.656 --> 22:14:05.814 align:start position:0% equipment and<22:14:04.320> it<22:14:04.552> will<22:14:04.680> bring<22:14:04.856> your<22:14:04.976> data<22:14:05.280> center<22:14:05.464> down 22:14:05.814 --> 22:14:05.824 align:start position:0% and it will bring your data center down 22:14:05.824 --> 22:14:08.150 align:start position:0% and it will bring your data center down the<22:14:06.536> drive<22:14:06.656> pipe<22:14:07.080> is<22:14:07.144> the<22:14:07.320> same<22:14:07.440> as<22:14:07.552> a<22:14:07.680> wet<22:14:07.800> pipe 22:14:08.150 --> 22:14:08.160 align:start position:0% the drive pipe is the same as a wet pipe 22:14:08.160 --> 22:14:10.606 align:start position:0% the drive pipe is the same as a wet pipe but<22:14:08.280> the<22:14:08.400> water's<22:14:08.696> not<22:14:08.872> kept<22:14:09.176> in<22:14:09.296> the<22:14:09.480> pipes 22:14:10.606 --> 22:14:10.616 align:start position:0% but the water's not kept in the pipes 22:14:10.616 --> 22:14:12.470 align:start position:0% but the water's not kept in the pipes and<22:14:11.280> the<22:14:11.512> reason<22:14:11.576> is<22:14:11.824> it<22:14:12.000> accumulates 22:14:12.470 --> 22:14:12.480 align:start position:0% and the reason is it accumulates 22:14:12.480 --> 22:14:15.046 align:start position:0% and the reason is it accumulates moisture<22:14:13.016> and<22:14:13.552> if<22:14:14.104> there's<22:14:14.216> a<22:14:14.400> drape<22:14:14.696> it<22:14:14.872> can 22:14:15.046 --> 22:14:15.056 align:start position:0% moisture and if there's a drape it can 22:14:15.056 --> 22:14:18.046 align:start position:0% moisture and if there's a drape it can damage<22:14:15.424> the<22:14:15.600> equipment<22:14:15.896> and<22:14:16.856> obviously 22:14:18.046 --> 22:14:18.056 align:start position:0% damage the equipment and obviously 22:14:18.056 --> 22:14:20.206 align:start position:0% damage the equipment and obviously um could<22:14:18.600> cause<22:14:18.832> rust 22:14:20.206 --> 22:14:20.216 align:start position:0% um could cause rust 22:14:20.216 --> 22:14:22.006 align:start position:0% um could cause rust since<22:14:20.576> the<22:14:20.824> dry<22:14:20.936> pipe<22:14:21.296> is<22:14:21.360> a<22:14:21.536> water-based 22:14:22.006 --> 22:14:22.016 align:start position:0% since the dry pipe is a water-based 22:14:22.016 --> 22:14:23.862 align:start position:0% since the dry pipe is a water-based system<22:14:22.144> the<22:14:22.496> disadvantage<22:14:23.104> is<22:14:23.336> the<22:14:23.576> same<22:14:23.696> as 22:14:23.862 --> 22:14:23.872 align:start position:0% system the disadvantage is the same as 22:14:23.872 --> 22:14:25.070 align:start position:0% system the disadvantage is the same as the<22:14:24.000> wet<22:14:24.176> pipe 22:14:25.070 --> 22:14:25.080 align:start position:0% the wet pipe 22:14:25.080 --> 22:14:26.686 align:start position:0% the wet pipe now<22:14:25.552> you've<22:14:25.744> got<22:14:25.856> gas<22:14:26.104> suppression 22:14:26.686 --> 22:14:26.696 align:start position:0% now you've got gas suppression 22:14:26.696 --> 22:14:29.454 align:start position:0% now you've got gas suppression suppression<22:14:27.600> which<22:14:27.832> is<22:14:28.016> the<22:14:28.496> norm<22:14:28.680> in<22:14:29.160> your 22:14:29.454 --> 22:14:29.464 align:start position:0% suppression which is the norm in your 22:14:29.464 --> 22:14:32.350 align:start position:0% suppression which is the norm in your data<22:14:29.824> centers<22:14:30.176> it<22:14:30.896> basically<22:14:31.192> starves<22:14:31.800> the 22:14:32.350 --> 22:14:32.360 align:start position:0% data centers it basically starves the 22:14:32.360 --> 22:14:36.166 align:start position:0% data centers it basically starves the fire<22:14:33.360> of<22:14:33.896> oxygen<22:14:34.744> and<22:14:35.104> the<22:14:35.216> fires<22:14:35.576> need<22:14:35.696> oxygen 22:14:36.166 --> 22:14:36.176 align:start position:0% fire of oxygen and the fires need oxygen 22:14:36.176 --> 22:14:39.110 align:start position:0% fire of oxygen and the fires need oxygen in<22:14:36.424> order<22:14:36.600> to<22:14:37.080> generate<22:14:37.920> the<22:14:38.040> Heat 22:14:39.110 --> 22:14:39.120 align:start position:0% in order to generate the Heat 22:14:39.120 --> 22:14:41.686 align:start position:0% in order to generate the Heat clean<22:14:39.720> agents<22:14:40.144> such<22:14:40.320> as<22:14:40.496> fm200<22:14:41.104> remove<22:14:41.464> the 22:14:41.686 --> 22:14:41.696 align:start position:0% clean agents such as fm200 remove the 22:14:41.696 --> 22:14:43.910 align:start position:0% clean agents such as fm200 remove the heat<22:14:41.824> from<22:14:42.000> the<22:14:42.176> fire<22:14:42.296> and<22:14:43.192> here's<22:14:43.552> some<22:14:43.680> large 22:14:43.910 --> 22:14:43.920 align:start position:0% heat from the fire and here's some large 22:14:43.920 --> 22:14:47.686 align:start position:0% heat from the fire and here's some large industrially<22:14:44.512> scale<22:14:45.016> heat<22:14:46.016> agents 22:14:47.686 --> 22:14:47.696 align:start position:0% industrially scale heat agents 22:14:47.696 --> 22:14:50.150 align:start position:0% industrially scale heat agents and<22:14:48.296> inert<22:14:48.656> gases<22:14:49.080> such<22:14:49.256> as<22:14:49.376> carbon<22:14:49.744> dioxide 22:14:50.150 --> 22:14:50.160 align:start position:0% and inert gases such as carbon dioxide 22:14:50.160 --> 22:14:52.734 align:start position:0% and inert gases such as carbon dioxide deprive<22:14:50.824> the<22:14:51.000> fire<22:14:51.176> of<22:14:51.360> oxygen 22:14:52.734 --> 22:14:52.744 align:start position:0% deprive the fire of oxygen 22:14:52.744 --> 22:14:54.590 align:start position:0% deprive the fire of oxygen you<22:14:53.400> do<22:14:53.512> get<22:14:53.696> immediate<22:14:54.120> recovery<22:14:54.480> of 22:14:54.590 --> 22:14:54.600 align:start position:0% you do get immediate recovery of 22:14:54.600 --> 22:14:56.206 align:start position:0% you do get immediate recovery of business<22:14:54.784> operations<22:14:55.376> you've<22:14:55.856> obviously<22:14:56.104> got 22:14:56.206 --> 22:14:56.216 align:start position:0% business operations you've obviously got 22:14:56.216 --> 22:14:58.366 align:start position:0% business operations you've obviously got to<22:14:56.400> vent<22:14:56.640> the<22:14:57.240> area<22:14:57.424> before<22:14:57.784> people<22:14:58.144> are 22:14:58.366 --> 22:14:58.376 align:start position:0% to vent the area before people are 22:14:58.376 --> 22:15:00.046 align:start position:0% to vent the area before people are allowed<22:14:58.744> back<22:14:58.856> in<22:14:59.040> otherwise<22:14:59.696> they'll<22:14:59.936> just 22:15:00.046 --> 22:15:00.056 align:start position:0% allowed back in otherwise they'll just 22:15:00.056 --> 22:15:01.246 align:start position:0% allowed back in otherwise they'll just pass<22:15:00.240> out 22:15:01.246 --> 22:15:01.256 align:start position:0% pass out 22:15:01.256 --> 22:15:03.470 align:start position:0% pass out and<22:15:01.800> and<22:15:01.800> you've<22:15:02.280> got<22:15:02.336> to<22:15:02.512> have<22:15:02.640> training<22:15:03.120> for 22:15:03.470 --> 22:15:03.480 align:start position:0% and and you've got to have training for 22:15:03.480 --> 22:15:04.734 align:start position:0% and and you've got to have training for the<22:15:03.656> staff 22:15:04.734 --> 22:15:04.744 align:start position:0% the staff 22:15:04.744 --> 22:15:06.526 align:start position:0% the staff it<22:15:05.216> doesn't<22:15:05.400> actually<22:15:05.640> mention<22:15:05.936> I<22:15:06.240> didn't<22:15:06.424> put 22:15:06.526 --> 22:15:06.536 align:start position:0% it doesn't actually mention I didn't put 22:15:06.536 --> 22:15:08.270 align:start position:0% it doesn't actually mention I didn't put in<22:15:06.720> here<22:15:06.896> but<22:15:07.080> you<22:15:07.192> obviously<22:15:07.552> need<22:15:07.856> an 22:15:08.270 --> 22:15:08.280 align:start position:0% in here but you obviously need an 22:15:08.280 --> 22:15:11.926 align:start position:0% in here but you obviously need an evacuation<22:15:08.936> plan<22:15:09.440> so<22:15:10.440> that<22:15:10.856> there's<22:15:11.696> normally 22:15:11.926 --> 22:15:11.936 align:start position:0% evacuation plan so that there's normally 22:15:11.936 --> 22:15:14.686 align:start position:0% evacuation plan so that there's normally a<22:15:12.120> diagram<22:15:12.424> in<22:15:13.144> several<22:15:13.440> key<22:15:13.744> places<22:15:13.976> and<22:15:14.464> and 22:15:14.686 --> 22:15:14.696 align:start position:0% a diagram in several key places and and 22:15:14.696 --> 22:15:16.790 align:start position:0% a diagram in several key places and and signed<22:15:15.360> exits 22:15:16.790 --> 22:15:16.800 align:start position:0% signed exits 22:15:16.800 --> 22:15:18.822 align:start position:0% signed exits as<22:15:17.336> mentioned<22:15:17.760> in<22:15:17.872> the<22:15:18.000> syllabus<22:15:18.424> but<22:15:18.600> I<22:15:18.720> just 22:15:18.822 --> 22:15:18.832 align:start position:0% as mentioned in the syllabus but I just 22:15:18.832 --> 22:15:20.390 align:start position:0% as mentioned in the syllabus but I just thought<22:15:18.960> it<22:15:19.144> was<22:15:19.256> so<22:15:19.440> obvious<22:15:19.680> because<22:15:19.976> we<22:15:20.280> all 22:15:20.390 --> 22:15:20.400 align:start position:0% thought it was so obvious because we all 22:15:20.400 --> 22:15:22.366 align:start position:0% thought it was so obvious because we all see<22:15:20.576> them<22:15:20.760> wherever<22:15:21.176> we<22:15:21.480> go<22:15:21.784> even<22:15:22.080> coffee 22:15:22.366 --> 22:15:22.376 align:start position:0% see them wherever we go even coffee 22:15:22.376 --> 22:15:25.006 align:start position:0% see them wherever we go even coffee shops<22:15:22.744> have<22:15:22.920> got<22:15:23.104> fire<22:15:23.536> exits<22:15:24.536> of<22:15:24.656> fire<22:15:24.832> escape 22:15:25.006 --> 22:15:25.016 align:start position:0% shops have got fire exits of fire escape 22:15:25.016 --> 22:15:26.326 align:start position:0% shops have got fire exits of fire escape plans 22:15:26.326 --> 22:15:26.336 align:start position:0% plans 22:15:26.336 --> 22:15:28.670 align:start position:0% plans lifting<22:15:27.120> techniques<22:15:27.656> well<22:15:27.960> you<22:15:28.144> can<22:15:28.256> see<22:15:28.376> this 22:15:28.670 --> 22:15:28.680 align:start position:0% lifting techniques well you can see this 22:15:28.680 --> 22:15:31.134 align:start position:0% lifting techniques well you can see this guy<22:15:28.856> here<22:15:29.216> is<22:15:29.576> bending<22:15:30.120> his<22:15:30.296> back<22:15:30.536> not<22:15:30.896> his 22:15:31.134 --> 22:15:31.144 align:start position:0% guy here is bending his back not his 22:15:31.144 --> 22:15:33.774 align:start position:0% guy here is bending his back not his knees<22:15:31.440> which<22:15:31.744> isn't<22:15:32.040> a<22:15:32.160> recommended<22:15:32.760> way<22:15:33.536> to 22:15:33.774 --> 22:15:33.784 align:start position:0% knees which isn't a recommended way to 22:15:33.784 --> 22:15:35.030 align:start position:0% knees which isn't a recommended way to do<22:15:33.960> things 22:15:35.030 --> 22:15:35.040 align:start position:0% do things 22:15:35.040 --> 22:15:37.366 align:start position:0% do things easiest<22:15:35.696> way<22:15:35.936> is<22:15:36.240> to<22:15:36.480> adjust<22:15:36.656> houses<22:15:37.016> through 22:15:37.366 --> 22:15:37.376 align:start position:0% easiest way is to adjust houses through 22:15:37.376 --> 22:15:39.414 align:start position:0% easiest way is to adjust houses through improper<22:15:37.800> lifting<22:15:38.160> don't<22:15:38.760> really<22:15:39.056> lift<22:15:39.296> the 22:15:39.414 --> 22:15:39.424 align:start position:0% improper lifting don't really lift the 22:15:39.424 --> 22:15:40.846 align:start position:0% improper lifting don't really lift the equipment<22:15:39.656> if<22:15:39.896> it<22:15:40.016> weighs<22:15:40.440> more<22:15:40.552> than<22:15:40.680> a 22:15:40.846 --> 22:15:40.856 align:start position:0% equipment if it weighs more than a 22:15:40.856 --> 22:15:42.886 align:start position:0% equipment if it weighs more than a quarter<22:15:41.104> of<22:15:41.216> your<22:15:41.400> weight<22:15:41.656> lift<22:15:42.656> with<22:15:42.784> your 22:15:42.886 --> 22:15:42.896 align:start position:0% quarter of your weight lift with your 22:15:42.896 --> 22:15:44.390 align:start position:0% quarter of your weight lift with your legs<22:15:43.144> with<22:15:43.256> a<22:15:43.440> straight<22:15:43.504> back<22:15:43.744> obviously<22:15:44.280> if 22:15:44.390 --> 22:15:44.400 align:start position:0% legs with a straight back obviously if 22:15:44.400 --> 22:15:46.134 align:start position:0% legs with a straight back obviously if you<22:15:44.576> have<22:15:44.696> injuries<22:15:45.360> especially<22:15:45.896> back 22:15:46.134 --> 22:15:46.144 align:start position:0% you have injuries especially back 22:15:46.144 --> 22:15:49.134 align:start position:0% you have injuries especially back injuries<22:15:46.744> then<22:15:47.336> don't<22:15:47.512> attempt<22:15:48.056> it<22:15:48.240> and<22:15:48.960> a<22:15:49.080> lot 22:15:49.134 --> 22:15:49.144 align:start position:0% injuries then don't attempt it and a lot 22:15:49.144 --> 22:15:51.526 align:start position:0% injuries then don't attempt it and a lot of<22:15:49.256> the<22:15:49.320> time<22:15:49.504> there's<22:15:49.744> lifted<22:15:50.216> equipments 22:15:51.526 --> 22:15:51.536 align:start position:0% of the time there's lifted equipments 22:15:51.536 --> 22:15:54.110 align:start position:0% of the time there's lifted equipments there<22:15:52.192> that<22:15:52.496> will<22:15:52.680> oyster<22:15:53.160> for<22:15:53.512> you<22:15:53.696> or<22:15:53.936> hold 22:15:54.110 --> 22:15:54.120 align:start position:0% there that will oyster for you or hold 22:15:54.120 --> 22:15:57.110 align:start position:0% there that will oyster for you or hold it<22:15:54.296> in<22:15:54.480> place<22:15:54.600> while<22:15:54.960> you<22:15:55.192> screw<22:15:55.976> things<22:15:56.216> or 22:15:57.110 --> 22:15:57.120 align:start position:0% it in place while you screw things or 22:15:57.120 --> 22:15:59.286 align:start position:0% it in place while you screw things or unscrew<22:15:57.656> them<22:15:57.784> and<22:15:57.960> Slot<22:15:58.192> them<22:15:58.320> in 22:15:59.286 --> 22:15:59.296 align:start position:0% unscrew them and Slot them in 22:15:59.296 --> 22:16:01.734 align:start position:0% unscrew them and Slot them in anti-static<22:16:00.296> static<22:16:00.832> electricity<22:16:01.256> as<22:16:01.552> I 22:16:01.734 --> 22:16:01.744 align:start position:0% anti-static static electricity as I 22:16:01.744 --> 22:16:03.950 align:start position:0% anti-static static electricity as I mentioned<22:16:01.856> at<22:16:02.040> the<22:16:02.216> start<22:16:02.336> will<22:16:02.640> fry<22:16:03.120> various 22:16:03.950 --> 22:16:03.960 align:start position:0% mentioned at the start will fry various 22:16:03.960 --> 22:16:05.502 align:start position:0% mentioned at the start will fry various components<22:16:04.616> and<22:16:04.800> that's<22:16:04.976> happened<22:16:05.160> to<22:16:05.400> me 22:16:05.502 --> 22:16:05.512 align:start position:0% components and that's happened to me 22:16:05.512 --> 22:16:07.846 align:start position:0% components and that's happened to me when<22:16:05.760> I've<22:16:05.872> installed<22:16:06.744> motherboards<22:16:07.744> and 22:16:07.846 --> 22:16:07.856 align:start position:0% when I've installed motherboards and 22:16:07.856 --> 22:16:09.646 align:start position:0% when I've installed motherboards and other<22:16:08.040> devices<22:16:08.464> I've<22:16:08.936> just<22:16:09.176> heard<22:16:09.296> a<22:16:09.536> Little 22:16:09.646 --> 22:16:09.656 align:start position:0% other devices I've just heard a Little 22:16:09.656 --> 22:16:11.814 align:start position:0% other devices I've just heard a Little Fizz<22:16:10.080> and<22:16:10.800> some<22:16:11.040> things 22:16:11.814 --> 22:16:11.824 align:start position:0% Fizz and some things 22:16:11.824 --> 22:16:14.750 align:start position:0% Fizz and some things um something's<22:16:12.600> broken<22:16:12.832> so<22:16:13.800> use<22:16:13.976> anti-static 22:16:14.750 --> 22:16:14.760 align:start position:0% um something's broken so use anti-static 22:16:14.760 --> 22:16:16.486 align:start position:0% um something's broken so use anti-static devices 22:16:16.486 --> 22:16:16.496 align:start position:0% devices 22:16:16.496 --> 22:16:19.070 align:start position:0% devices there's<22:16:17.216> anti-static<22:16:17.936> bags<22:16:18.296> and<22:16:18.536> also<22:16:18.784> wrist 22:16:19.070 --> 22:16:19.080 align:start position:0% there's anti-static bags and also wrist 22:16:19.080 --> 22:16:21.886 align:start position:0% there's anti-static bags and also wrist straps<22:16:19.552> that<22:16:19.920> you<22:16:20.216> can<22:16:20.480> connect<22:16:21.480> to<22:16:21.720> your 22:16:21.886 --> 22:16:21.896 align:start position:0% straps that you can connect to your 22:16:21.896 --> 22:16:23.814 align:start position:0% straps that you can connect to your wrist<22:16:22.192> and<22:16:22.856> then<22:16:22.976> connect<22:16:23.280> to<22:16:23.512> an<22:16:23.640> earth 22:16:23.814 --> 22:16:23.824 align:start position:0% wrist and then connect to an earth 22:16:23.824 --> 22:16:26.390 align:start position:0% wrist and then connect to an earth somewhere<22:16:24.240> that<22:16:24.536> will<22:16:24.720> prevent<22:16:25.144> the 22:16:26.390 --> 22:16:26.400 align:start position:0% somewhere that will prevent the 22:16:26.400 --> 22:16:27.110 align:start position:0% somewhere that will prevent the um 22:16:27.110 --> 22:16:27.120 align:start position:0% um 22:16:27.120 --> 22:16:29.502 align:start position:0% um causing<22:16:27.896> the<22:16:28.016> spark<22:16:28.256> somewhere<22:16:28.800> because<22:16:29.216> as 22:16:29.502 --> 22:16:29.512 align:start position:0% causing the spark somewhere because as 22:16:29.512 --> 22:16:30.774 align:start position:0% causing the spark somewhere because as we<22:16:29.696> walk<22:16:29.936> around<22:16:30.120> we're<22:16:30.424> generating 22:16:30.774 --> 22:16:30.784 align:start position:0% we walk around we're generating 22:16:30.784 --> 22:16:33.710 align:start position:0% we walk around we're generating electricity<22:16:31.440> static<22:16:32.040> electricity 22:16:33.710 --> 22:16:33.720 align:start position:0% electricity static electricity 22:16:33.720 --> 22:16:35.862 align:start position:0% electricity static electricity stabilizing<22:16:34.552> Iraq<22:16:34.920> is<22:16:35.160> important<22:16:35.512> to<22:16:35.640> have<22:16:35.760> a 22:16:35.862 --> 22:16:35.872 align:start position:0% stabilizing Iraq is important to have a 22:16:35.872 --> 22:16:38.454 align:start position:0% stabilizing Iraq is important to have a correctly<22:16:36.176> stabilized<22:16:37.016> rack<22:16:37.680> with<22:16:37.920> the<22:16:38.464> um 22:16:38.454 --> 22:16:38.464 align:start position:0% correctly stabilized rack with the um 22:16:38.464 --> 22:16:41.454 align:start position:0% correctly stabilized rack with the um fate<22:16:38.936> which<22:16:39.600> are<22:16:39.720> all<22:16:39.832> adjustable<22:16:40.336> racks<22:16:41.336> are 22:16:41.454 --> 22:16:41.464 align:start position:0% fate which are all adjustable racks are 22:16:41.464 --> 22:16:43.182 align:start position:0% fate which are all adjustable racks are not<22:16:41.576> stable<22:16:41.936> or<22:16:42.120> likely<22:16:42.424> to<22:16:42.536> collapse<22:16:42.832> at<22:16:43.016> any 22:16:43.182 --> 22:16:43.192 align:start position:0% not stable or likely to collapse at any 22:16:43.192 --> 22:16:44.990 align:start position:0% not stable or likely to collapse at any time 22:16:44.990 --> 22:16:45.000 align:start position:0% time 22:16:45.000 --> 22:16:46.734 align:start position:0% time um<22:16:45.120> you<22:16:45.296> put<22:16:45.480> your<22:16:45.720> large<22:16:45.896> equipment<22:16:46.320> in<22:16:46.496> at 22:16:46.734 --> 22:16:46.744 align:start position:0% um you put your large equipment in at 22:16:46.744 --> 22:16:47.814 align:start position:0% um you put your large equipment in at the<22:16:46.856> bottom 22:16:47.814 --> 22:16:47.824 align:start position:0% the bottom 22:16:47.824 --> 22:16:50.750 align:start position:0% the bottom and<22:16:48.176> the<22:16:48.296> lighter<22:16:48.656> at<22:16:48.832> the<22:16:49.016> top<22:16:49.376> there 22:16:50.750 --> 22:16:50.760 align:start position:0% and the lighter at the top there 22:16:50.760 --> 22:16:53.630 align:start position:0% and the lighter at the top there and<22:16:51.056> moving<22:16:51.424> on<22:16:51.536> to<22:16:51.720> another<22:16:51.976> syllabus<22:16:52.976> item 22:16:53.630 --> 22:16:53.640 align:start position:0% and moving on to another syllabus item 22:16:53.640 --> 22:16:56.862 align:start position:0% and moving on to another syllabus item is<22:16:53.872> the<22:16:54.376> MSDS<22:16:55.376> the<22:16:55.680> material<22:16:56.040> safety<22:16:56.464> data 22:16:56.862 --> 22:16:56.872 align:start position:0% is the MSDS the material safety data 22:16:56.872 --> 22:16:59.686 align:start position:0% is the MSDS the material safety data sheet<22:16:57.176> which<22:16:57.832> you'll<22:16:58.144> go<22:16:58.320> into<22:16:58.464> this<22:16:59.464> is<22:16:59.576> a 22:16:59.686 --> 22:16:59.696 align:start position:0% sheet which you'll go into this is a 22:16:59.696 --> 22:17:01.494 align:start position:0% sheet which you'll go into this is a document<22:17:00.000> that<22:17:00.240> contains<22:17:00.720> information<22:17:01.016> about 22:17:01.494 --> 22:17:01.504 align:start position:0% document that contains information about 22:17:01.504 --> 22:17:03.350 align:start position:0% document that contains information about hazardous<22:17:02.216> chemicals 22:17:03.350 --> 22:17:03.360 align:start position:0% hazardous chemicals 22:17:03.360 --> 22:17:05.630 align:start position:0% hazardous chemicals used<22:17:04.016> as<22:17:04.256> a<22:17:04.440> primary<22:17:04.680> means<22:17:04.976> to<22:17:05.104> communicate 22:17:05.630 --> 22:17:05.640 align:start position:0% used as a primary means to communicate 22:17:05.640 --> 22:17:08.814 align:start position:0% used as a primary means to communicate and<22:17:06.360> the<22:17:06.656> chemical<22:17:06.960> hazards<22:17:07.504> to<22:17:07.616> staff<22:17:07.976> I 22:17:08.814 --> 22:17:08.824 align:start position:0% and the chemical hazards to staff I 22:17:08.824 --> 22:17:10.006 align:start position:0% and the chemical hazards to staff I presume<22:17:09.176> you'd<22:17:09.360> go<22:17:09.480> in<22:17:09.656> some<22:17:09.784> sort<22:17:09.960> of 22:17:10.006 --> 22:17:10.016 align:start position:0% presume you'd go in some sort of 22:17:10.016 --> 22:17:13.246 align:start position:0% presume you'd go in some sort of training<22:17:10.440> course<22:17:10.616> for<22:17:11.104> for<22:17:11.696> this<22:17:12.000> not<22:17:12.600> um 22:17:13.246 --> 22:17:13.256 align:start position:0% training course for for this not um 22:17:13.256 --> 22:17:14.926 align:start position:0% training course for for this not um not<22:17:13.680> just<22:17:13.920> read<22:17:14.040> something<22:17:14.280> on<22:17:14.576> a<22:17:14.760> wall 22:17:14.926 --> 22:17:14.936 align:start position:0% not just read something on a wall 22:17:14.936 --> 22:17:16.790 align:start position:0% not just read something on a wall preferred<22:17:15.832> by<22:17:15.960> the<22:17:16.144> manufacturer<22:17:16.744> or 22:17:16.790 --> 22:17:16.800 align:start position:0% preferred by the manufacturer or 22:17:16.800 --> 22:17:19.366 align:start position:0% preferred by the manufacturer or supplier<22:17:17.160> of<22:17:17.400> the<22:17:17.512> chemical 22:17:19.366 --> 22:17:19.376 align:start position:0% supplier of the chemical 22:17:19.376 --> 22:17:21.950 align:start position:0% supplier of the chemical you<22:17:19.920> have<22:17:20.040> to<22:17:20.216> make<22:17:20.400> the<22:17:20.576> MSDS<22:17:21.240> available<22:17:21.480> in 22:17:21.950 --> 22:17:21.960 align:start position:0% you have to make the MSDS available in 22:17:21.960 --> 22:17:23.390 align:start position:0% you have to make the MSDS available in your<22:17:22.080> workplace<22:17:22.440> for<22:17:22.744> each<22:17:22.920> hazardous 22:17:23.390 --> 22:17:23.400 align:start position:0% your workplace for each hazardous 22:17:23.400 --> 22:17:26.030 align:start position:0% your workplace for each hazardous chemical<22:17:23.760> or<22:17:24.536> a<22:17:24.720> mixture<22:17:25.016> of<22:17:25.256> such<22:17:25.440> hazardous 22:17:26.030 --> 22:17:26.040 align:start position:0% chemical or a mixture of such hazardous 22:17:26.040 --> 22:17:27.166 align:start position:0% chemical or a mixture of such hazardous chemicals 22:17:27.166 --> 22:17:27.176 align:start position:0% chemicals 22:17:27.176 --> 22:17:28.910 align:start position:0% chemicals it<22:17:27.600> should<22:17:27.784> be<22:17:27.896> ready<22:17:28.016> available<22:17:28.320> to<22:17:28.744> all 22:17:28.910 --> 22:17:28.920 align:start position:0% it should be ready available to all 22:17:28.920 --> 22:17:30.414 align:start position:0% it should be ready available to all those<22:17:29.104> who<22:17:29.280> may<22:17:29.464> come<22:17:29.640> into<22:17:29.824> contact<22:17:30.056> with 22:17:30.414 --> 22:17:30.424 align:start position:0% those who may come into contact with 22:17:30.424 --> 22:17:34.182 align:start position:0% those who may come into contact with such<22:17:30.680> hazardous<22:17:31.680> chemicals 22:17:34.182 --> 22:17:34.192 align:start position:0% such hazardous chemicals 22:17:34.192 --> 22:17:36.414 align:start position:0% such hazardous chemicals the<22:17:34.744> occupational<22:17:35.216> safety<22:17:36.120> and<22:17:36.240> health 22:17:36.414 --> 22:17:36.424 align:start position:0% the occupational safety and health 22:17:36.424 --> 22:17:38.502 align:start position:0% the occupational safety and health administration<22:17:37.080> and<22:17:37.744> I<22:17:37.856> presume<22:17:38.216> these<22:17:38.400> are 22:17:38.502 --> 22:17:38.512 align:start position:0% administration and I presume these are 22:17:38.512 --> 22:17:39.950 align:start position:0% administration and I presume these are American<22:17:38.760> different<22:17:39.176> countries<22:17:39.536> will<22:17:39.784> have 22:17:39.950 --> 22:17:39.960 align:start position:0% American different countries will have 22:17:39.960 --> 22:17:41.926 align:start position:0% American different countries will have different<22:17:40.512> organizations<22:17:41.512> or 22:17:41.926 --> 22:17:41.936 align:start position:0% different organizations or 22:17:41.936 --> 22:17:43.310 align:start position:0% different organizations or Administrations 22:17:43.310 --> 22:17:43.320 align:start position:0% Administrations 22:17:43.320 --> 22:17:45.230 align:start position:0% Administrations they're<22:17:43.976> part<22:17:44.216> of<22:17:44.336> the<22:17:44.400> US<22:17:44.576> Department<22:17:44.936> of 22:17:45.230 --> 22:17:45.240 align:start position:0% they're part of the US Department of 22:17:45.240 --> 22:17:47.862 align:start position:0% they're part of the US Department of Labor<22:17:45.656> create<22:17:46.376> the<22:17:46.744> hazard<22:17:47.160> communication 22:17:47.862 --> 22:17:47.872 align:start position:0% Labor create the hazard communication 22:17:47.872 --> 22:17:50.566 align:start position:0% Labor create the hazard communication standard<22:17:48.536> to<22:17:49.192> ensure<22:17:49.440> that<22:17:49.744> all 22:17:50.566 --> 22:17:50.576 align:start position:0% standard to ensure that all 22:17:50.576 --> 22:17:52.006 align:start position:0% standard to ensure that all um chemicals<22:17:51.176> that<22:17:51.296> are<22:17:51.480> hazardous<22:17:51.832> are 22:17:52.006 --> 22:17:52.016 align:start position:0% um chemicals that are hazardous are 22:17:52.016 --> 22:17:54.166 align:start position:0% um chemicals that are hazardous are evaluated<22:17:52.496> and<22:17:53.280> the<22:17:53.464> information<22:17:53.640> is 22:17:54.166 --> 22:17:54.176 align:start position:0% evaluated and the information is 22:17:54.176 --> 22:17:56.326 align:start position:0% evaluated and the information is correctly<22:17:54.600> passed 22:17:56.326 --> 22:17:56.336 align:start position:0% correctly passed 22:17:56.336 --> 22:17:58.070 align:start position:0% correctly passed should<22:17:56.824> be<22:17:57.000> in<22:17:57.120> English<22:17:57.296> this<22:17:57.832> should<22:17:57.960> be 22:17:58.070 --> 22:17:58.080 align:start position:0% should be in English this should be 22:17:58.080 --> 22:18:00.350 align:start position:0% should be in English this should be include<22:17:58.376> 12<22:17:58.552> items<22:17:59.040> mandated<22:17:59.576> which<22:17:59.936> will<22:18:00.120> go 22:18:00.350 --> 22:18:00.360 align:start position:0% include 12 items mandated which will go 22:18:00.360 --> 22:18:01.734 align:start position:0% include 12 items mandated which will go through<22:18:00.536> briefly 22:18:01.734 --> 22:18:01.744 align:start position:0% through briefly 22:18:01.744 --> 22:18:03.710 align:start position:0% through briefly the<22:18:02.216> name<22:18:02.336> of<22:18:02.576> the<22:18:02.640> chemical<22:18:03.000> the<22:18:03.424> physically 22:18:03.710 --> 22:18:03.720 align:start position:0% the name of the chemical the physically 22:18:03.720 --> 22:18:06.350 align:start position:0% the name of the chemical the physically chemical<22:18:04.256> pop<22:18:04.616> and<22:18:05.040> properties<22:18:05.576> such<22:18:06.240> as 22:18:06.350 --> 22:18:06.360 align:start position:0% chemical pop and properties such as 22:18:06.360 --> 22:18:08.686 align:start position:0% chemical pop and properties such as color<22:18:06.536> and<22:18:06.832> odor<22:18:07.256> so<22:18:07.376> you<22:18:07.552> can<22:18:07.680> recognize<22:18:08.512> it 22:18:08.686 --> 22:18:08.696 align:start position:0% color and odor so you can recognize it 22:18:08.696 --> 22:18:10.670 align:start position:0% color and odor so you can recognize it if<22:18:08.872> it<22:18:09.056> does<22:18:09.176> have<22:18:09.360> a<22:18:09.536> color<22:18:09.720> a<22:18:10.440> lot<22:18:10.496> of<22:18:10.552> them 22:18:10.670 --> 22:18:10.680 align:start position:0% if it does have a color a lot of them 22:18:10.680 --> 22:18:12.470 align:start position:0% if it does have a color a lot of them have<22:18:10.856> odors<22:18:11.400> added 22:18:12.470 --> 22:18:12.480 align:start position:0% have odors added 22:18:12.480 --> 22:18:14.814 align:start position:0% have odors added such<22:18:13.080> as<22:18:13.256> their<22:18:13.440> natural<22:18:13.680> gas<22:18:13.976> has<22:18:14.280> an<22:18:14.464> odor 22:18:14.814 --> 22:18:14.824 align:start position:0% such as their natural gas has an odor 22:18:14.824 --> 22:18:17.750 align:start position:0% such as their natural gas has an odor added<22:18:15.240> certainly<22:18:16.016> did<22:18:16.256> in<22:18:16.440> the<22:18:16.552> UK<22:18:16.856> so<22:18:17.280> you 22:18:17.750 --> 22:18:17.760 align:start position:0% added certainly did in the UK so you 22:18:17.760 --> 22:18:20.094 align:start position:0% added certainly did in the UK so you could<22:18:17.872> smell<22:18:18.056> it<22:18:18.296> if<22:18:18.424> there<22:18:18.536> was<22:18:18.720> a<22:18:18.784> leak<22:18:19.552> and 22:18:20.094 --> 22:18:20.104 align:start position:0% could smell it if there was a leak and 22:18:20.104 --> 22:18:22.006 align:start position:0% could smell it if there was a leak and before<22:18:20.336> that<22:18:20.696> and<22:18:21.000> people<22:18:21.240> didn't<22:18:21.600> know<22:18:21.784> that 22:18:22.006 --> 22:18:22.016 align:start position:0% before that and people didn't know that 22:18:22.016 --> 22:18:24.590 align:start position:0% before that and people didn't know that the<22:18:22.192> house<22:18:22.376> was<22:18:22.552> full<22:18:22.744> of<22:18:22.920> gas<22:18:23.104> and<22:18:23.400> uh<22:18:23.824> lit<22:18:24.480> a 22:18:24.590 --> 22:18:24.600 align:start position:0% the house was full of gas and uh lit a 22:18:24.600 --> 22:18:26.390 align:start position:0% the house was full of gas and uh lit a cigarette<22:18:24.896> and<22:18:25.016> that<22:18:25.192> was<22:18:25.320> the<22:18:25.440> end<22:18:25.552> of<22:18:25.744> them 22:18:26.390 --> 22:18:26.400 align:start position:0% cigarette and that was the end of them 22:18:26.400 --> 22:18:28.734 align:start position:0% cigarette and that was the end of them physical<22:18:26.872> hundreds<22:18:27.656> uh<22:18:28.080> hazards<22:18:28.496> such<22:18:28.616> as 22:18:28.734 --> 22:18:28.744 align:start position:0% physical hundreds uh hazards such as 22:18:28.744 --> 22:18:30.774 align:start position:0% physical hundreds uh hazards such as explosiveness<22:18:29.464> or<22:18:29.872> could<22:18:30.176> it<22:18:30.360> react<22:18:30.600> with 22:18:30.774 --> 22:18:30.784 align:start position:0% explosiveness or could it react with 22:18:30.784 --> 22:18:32.566 align:start position:0% explosiveness or could it react with something 22:18:32.566 --> 22:18:32.576 align:start position:0% something 22:18:32.576 --> 22:18:34.790 align:start position:0% something uh<22:18:33.240> health<22:18:33.424> hazards<22:18:33.960> such<22:18:34.080> as<22:18:34.192> corrosive<22:18:34.680> to 22:18:34.790 --> 22:18:34.800 align:start position:0% uh health hazards such as corrosive to 22:18:34.800 --> 22:18:37.006 align:start position:0% uh health hazards such as corrosive to eyes<22:18:35.040> or<22:18:35.336> skin<22:18:35.576> you<22:18:35.872> normally<22:18:36.240> have<22:18:36.600> that<22:18:36.784> in<22:18:36.896> a 22:18:37.006 --> 22:18:37.016 align:start position:0% eyes or skin you normally have that in a 22:18:37.016 --> 22:18:38.326 align:start position:0% eyes or skin you normally have that in a diagram<22:18:37.256> as<22:18:37.552> well 22:18:38.326 --> 22:18:38.336 align:start position:0% diagram as well 22:18:38.336 --> 22:18:40.182 align:start position:0% diagram as well primary<22:18:38.936> ways<22:18:39.360> you<22:18:39.480> can<22:18:39.600> enter<22:18:39.784> your<22:18:40.016> body 22:18:40.182 --> 22:18:40.192 align:start position:0% primary ways you can enter your body 22:18:40.192 --> 22:18:43.366 align:start position:0% primary ways you can enter your body such<22:18:40.552> as<22:18:40.744> always<22:18:40.976> breathing 22:18:43.366 --> 22:18:43.376 align:start position:0% such as always breathing 22:18:43.376 --> 22:18:46.182 align:start position:0% such as always breathing allowable<22:18:44.104> limits<22:18:44.512> of<22:18:44.640> exposure<22:18:45.176> before<22:18:45.896> you 22:18:46.182 --> 22:18:46.192 align:start position:0% allowable limits of exposure before you 22:18:46.192 --> 22:18:49.134 align:start position:0% allowable limits of exposure before you get<22:18:46.496> seriously<22:18:47.216> injured<22:18:47.640> or<22:18:47.760> die 22:18:49.134 --> 22:18:49.144 align:start position:0% get seriously injured or die 22:18:49.144 --> 22:18:54.710 align:start position:0% get seriously injured or die carcinogen 22:18:54.710 --> 22:18:54.720 align:start position:0% 22:18:54.720 --> 22:18:57.886 align:start position:0% precautions<22:18:55.680> before<22:18:56.104> you<22:18:56.576> use<22:18:56.936> it<22:18:57.176> masks<22:18:57.720> or 22:18:57.886 --> 22:18:57.896 align:start position:0% precautions before you use it masks or 22:18:57.896 --> 22:19:00.822 align:start position:0% precautions before you use it masks or goggles<22:18:58.496> special<22:18:59.280> equipment 22:19:00.822 --> 22:19:00.832 align:start position:0% goggles special equipment 22:19:00.832 --> 22:19:03.046 align:start position:0% goggles special equipment and<22:19:01.376> do<22:19:01.504> you<22:19:01.616> need<22:19:01.744> any<22:19:01.920> gloves 22:19:03.046 --> 22:19:03.056 align:start position:0% and do you need any gloves 22:19:03.056 --> 22:19:05.686 align:start position:0% and do you need any gloves protection 22:19:05.686 --> 22:19:05.696 align:start position:0% protection 22:19:05.696 --> 22:19:09.166 align:start position:0% protection and<22:19:06.240> Engineering<22:19:06.896> controls 22:19:09.166 --> 22:19:09.176 align:start position:0% and Engineering controls 22:19:09.176 --> 22:19:11.630 align:start position:0% and Engineering controls first<22:19:09.832> aid<22:19:10.192> if<22:19:10.376> it<22:19:10.496> all<22:19:10.616> goes<22:19:10.920> wrong<22:19:11.040> normally 22:19:11.630 --> 22:19:11.640 align:start position:0% first aid if it all goes wrong normally 22:19:11.640 --> 22:19:13.566 align:start position:0% first aid if it all goes wrong normally as<22:19:12.000> the<22:19:12.240> number<22:19:12.360> of<22:19:12.536> the<22:19:12.720> Emergency<22:19:12.896> Services 22:19:13.566 --> 22:19:13.576 align:start position:0% as the number of the Emergency Services 22:19:13.576 --> 22:19:16.486 align:start position:0% as the number of the Emergency Services the<22:19:14.576> date<22:19:14.760> when<22:19:14.936> it<22:19:15.176> was<22:19:15.360> prepared<22:19:15.832> the 22:19:16.486 --> 22:19:16.496 align:start position:0% the date when it was prepared the 22:19:16.496 --> 22:19:19.430 align:start position:0% the date when it was prepared the document<22:19:16.976> and<22:19:17.824> the<22:19:18.000> last<22:19:18.120> revision 22:19:19.430 --> 22:19:19.440 align:start position:0% document and the last revision 22:19:19.440 --> 22:19:21.710 align:start position:0% document and the last revision contact<22:19:19.856> details<22:19:20.464> of<22:19:20.696> the<22:19:20.872> person<22:19:21.120> who's 22:19:21.710 --> 22:19:21.720 align:start position:0% contact details of the person who's 22:19:21.720 --> 22:19:24.134 align:start position:0% contact details of the person who's responsible 22:19:24.134 --> 22:19:24.144 align:start position:0% responsible 22:19:24.144 --> 22:19:26.454 align:start position:0% responsible all<22:19:25.144> right<22:19:25.256> we've<22:19:25.504> covered<22:19:25.800> a<22:19:25.976> lot<22:19:26.104> here<22:19:26.280> and 22:19:26.454 --> 22:19:26.464 align:start position:0% all right we've covered a lot here and 22:19:26.464 --> 22:19:27.886 align:start position:0% all right we've covered a lot here and it's<22:19:26.576> all<22:19:26.760> your<22:19:26.936> health<22:19:27.120> and<22:19:27.296> safety<22:19:27.656> stuff 22:19:27.886 --> 22:19:27.896 align:start position:0% it's all your health and safety stuff 22:19:27.896 --> 22:19:30.710 align:start position:0% it's all your health and safety stuff your<22:19:28.256> data<22:19:28.680> center<22:19:28.800> your<22:19:29.336> HVAC 22:19:30.710 --> 22:19:30.720 align:start position:0% your data center your HVAC 22:19:30.720 --> 22:19:33.166 align:start position:0% your data center your HVAC hot<22:19:31.256> and<22:19:31.440> cold<22:19:31.800> aisles<22:19:32.280> and<22:19:32.640> a<22:19:32.824> correct 22:19:33.166 --> 22:19:33.176 align:start position:0% hot and cold aisles and a correct 22:19:33.176 --> 22:19:35.990 align:start position:0% hot and cold aisles and a correct loading<22:19:33.720> of<22:19:33.960> your<22:19:34.192> racks 22:19:35.990 --> 22:19:36.000 align:start position:0% loading of your racks 22:19:36.000 --> 22:19:38.750 align:start position:0% loading of your racks fire<22:19:36.600> risk<22:19:37.144> fire<22:19:37.744> suppression<22:19:38.400> and<22:19:38.576> the 22:19:38.750 --> 22:19:38.760 align:start position:0% fire risk fire suppression and the 22:19:38.760 --> 22:19:41.926 align:start position:0% fire risk fire suppression and the impact<22:19:39.120> your<22:19:40.080> type<22:19:40.256> of<22:19:40.440> Agents 22:19:41.926 --> 22:19:41.936 align:start position:0% impact your type of Agents 22:19:41.936 --> 22:19:44.270 align:start position:0% impact your type of Agents lifting<22:19:42.720> without<22:19:43.016> injuring<22:19:43.744> yourself<22:19:43.856> or 22:19:44.270 --> 22:19:44.280 align:start position:0% lifting without injuring yourself or 22:19:44.280 --> 22:19:45.350 align:start position:0% lifting without injuring yourself or others 22:19:45.350 --> 22:19:45.360 align:start position:0% others 22:19:45.360 --> 22:19:47.030 align:start position:0% others you're<22:19:45.784> anti-static<22:19:46.496> and<22:19:46.680> rack 22:19:47.030 --> 22:19:47.040 align:start position:0% you're anti-static and rack 22:19:47.040 --> 22:19:50.630 align:start position:0% you're anti-static and rack stabilization<22:19:47.936> and<22:19:48.480> your<22:19:48.720> MSDS<22:19:49.616> so<22:19:50.512> that's 22:19:50.630 --> 22:19:50.640 align:start position:0% stabilization and your MSDS so that's 22:19:50.640 --> 22:19:55.520 align:start position:0% stabilization and your MSDS so that's all<22:19:51.000> thanks<22:19:51.424> for<22:19:51.600> watching 22:19:55.520 --> 22:19:55.530 align:start position:0% 22:19:55.530 --> 22:20:03.286 align:start position:0% [Music] 22:20:03.286 --> 22:20:03.296 align:start position:0% [Music] 22:20:03.296 --> 22:20:12.790 align:start position:0% [Music] foreign 22:20:12.790 --> 22:20:12.800 align:start position:0% 22:20:12.800 --> 22:20:17.390 align:start position:0% lesson<22:20:13.800> one<22:20:13.920> common<22:20:14.336> wireless<22:20:14.640> issues 22:20:17.390 --> 22:20:17.400 align:start position:0% 22:20:17.400 --> 22:20:19.542 align:start position:0% and<22:20:17.696> we<22:20:17.936> look<22:20:18.056> at<22:20:18.176> signal<22:20:18.536> loss<22:20:18.896> interference 22:20:19.542 --> 22:20:19.552 align:start position:0% and we look at signal loss interference 22:20:19.552 --> 22:20:22.094 align:start position:0% and we look at signal loss interference signal<22:20:20.104> to<22:20:20.280> noise<22:20:20.576> device<22:20:21.296> saturation 22:20:22.094 --> 22:20:22.104 align:start position:0% signal to noise device saturation 22:20:22.104 --> 22:20:24.774 align:start position:0% signal to noise device saturation bandwidth<22:20:23.104> saturation 22:20:24.774 --> 22:20:24.784 align:start position:0% bandwidth saturation 22:20:24.784 --> 22:20:28.846 align:start position:0% bandwidth saturation untested<22:20:25.616> updates<22:20:25.976> getting<22:20:26.512> your<22:20:26.824> SSID<22:20:27.536> wrong 22:20:28.846 --> 22:20:28.856 align:start position:0% untested updates getting your SSID wrong 22:20:28.856 --> 22:20:31.246 align:start position:0% untested updates getting your SSID wrong so<22:20:29.216> you<22:20:29.336> can<22:20:29.464> guess<22:20:29.576> how<22:20:29.760> to<22:20:29.936> fix<22:20:30.056> that<22:20:30.360> one 22:20:31.246 --> 22:20:31.256 align:start position:0% so you can guess how to fix that one 22:20:31.256 --> 22:20:34.366 align:start position:0% so you can guess how to fix that one power<22:20:31.856> levels<22:20:32.336> open<22:20:32.640> networks<22:20:33.424> Rogue<22:20:34.192> access 22:20:34.366 --> 22:20:34.376 align:start position:0% power levels open networks Rogue access 22:20:34.376 --> 22:20:36.414 align:start position:0% power levels open networks Rogue access points 22:20:36.414 --> 22:20:36.424 align:start position:0% points 22:20:36.424 --> 22:20:39.542 align:start position:0% points wrong<22:20:36.960> antenna<22:20:37.616> for<22:20:37.976> your<22:20:38.336> device 22:20:39.542 --> 22:20:39.552 align:start position:0% wrong antenna for your device 22:20:39.552 --> 22:20:43.006 align:start position:0% wrong antenna for your device incompatibilities<22:20:40.552> wrong<22:20:41.160> encryption<22:20:42.016> and 22:20:43.006 --> 22:20:43.016 align:start position:0% incompatibilities wrong encryption and 22:20:43.016 --> 22:20:46.246 align:start position:0% incompatibilities wrong encryption and bounce<22:20:44.424> most<22:20:45.424> of<22:20:45.600> these<22:20:45.720> are<22:20:45.896> pretty<22:20:46.080> Common 22:20:46.246 --> 22:20:46.256 align:start position:0% bounce most of these are pretty Common 22:20:46.256 --> 22:20:49.006 align:start position:0% bounce most of these are pretty Common Sense<22:20:46.616> actually<22:20:47.040> but<22:20:47.576> I've<22:20:48.296> put<22:20:48.536> these<22:20:48.832> in 22:20:49.006 --> 22:20:49.016 align:start position:0% Sense actually but I've put these in 22:20:49.016 --> 22:20:49.966 align:start position:0% Sense actually but I've put these in because 22:20:49.966 --> 22:20:49.976 align:start position:0% because 22:20:49.976 --> 22:20:52.246 align:start position:0% because um<22:20:50.040> it's<22:20:50.336> on<22:20:50.464> the<22:20:50.640> syllabus<22:20:51.120> and<22:20:51.960> if<22:20:52.144> you've 22:20:52.246 --> 22:20:52.256 align:start position:0% um it's on the syllabus and if you've 22:20:52.256 --> 22:20:55.246 align:start position:0% um it's on the syllabus and if you've got<22:20:52.440> a<22:20:52.680> home<22:20:53.120> wireless<22:20:54.120> device<22:20:54.600> or<22:20:55.016> even 22:20:55.246 --> 22:20:55.256 align:start position:0% got a home wireless device or even 22:20:55.256 --> 22:20:57.950 align:start position:0% got a home wireless device or even you've<22:20:55.616> used<22:20:55.800> Wireless<22:20:56.040> on<22:20:56.512> your<22:20:57.000> mobile 22:20:57.950 --> 22:20:57.960 align:start position:0% you've used Wireless on your mobile 22:20:57.960 --> 22:21:00.166 align:start position:0% you've used Wireless on your mobile phone<22:20:58.376> you<22:20:59.160> probably<22:20:59.336> have<22:20:59.512> to<22:20:59.696> troubleshoot 22:21:00.166 --> 22:21:00.176 align:start position:0% phone you probably have to troubleshoot 22:21:00.176 --> 22:21:02.326 align:start position:0% phone you probably have to troubleshoot most<22:21:00.480> of<22:21:00.656> these<22:21:00.960> issues 22:21:02.326 --> 22:21:02.336 align:start position:0% most of these issues 22:21:02.336 --> 22:21:04.182 align:start position:0% most of these issues um but<22:21:02.576> we'll<22:21:03.000> cover<22:21:03.176> them<22:21:03.360> nonetheless<22:21:03.832> just 22:21:04.182 --> 22:21:04.192 align:start position:0% um but we'll cover them nonetheless just 22:21:04.192 --> 22:21:07.134 align:start position:0% um but we'll cover them nonetheless just in<22:21:04.376> case<22:21:04.760> signal<22:21:05.760> loss<22:21:06.120> you've<22:21:06.360> got<22:21:06.424> no<22:21:06.656> signal 22:21:07.134 --> 22:21:07.144 align:start position:0% in case signal loss you've got no signal 22:21:07.144 --> 22:21:08.814 align:start position:0% in case signal loss you've got no signal or<22:21:07.504> low<22:21:07.856> signal 22:21:08.814 --> 22:21:08.824 align:start position:0% or low signal 22:21:08.824 --> 22:21:11.862 align:start position:0% or low signal there's<22:21:09.360> connectivity<22:21:10.280> and<22:21:11.280> there's<22:21:11.696> no 22:21:11.862 --> 22:21:11.872 align:start position:0% there's connectivity and there's no 22:21:11.872 --> 22:21:14.454 align:start position:0% there's connectivity and there's no connectivity<22:21:12.296> when<22:21:12.656> there's<22:21:12.832> no<22:21:12.960> signal 22:21:14.454 --> 22:21:14.464 align:start position:0% connectivity when there's no signal 22:21:14.464 --> 22:21:16.182 align:start position:0% connectivity when there's no signal there's<22:21:14.872> latency<22:21:15.360> and<22:21:15.656> inconsistent 22:21:16.182 --> 22:21:16.192 align:start position:0% there's latency and inconsistent 22:21:16.192 --> 22:21:18.230 align:start position:0% there's latency and inconsistent connectivity<22:21:16.744> when<22:21:17.160> the<22:21:17.336> signal<22:21:17.576> strength<22:21:18.000> is 22:21:18.230 --> 22:21:18.240 align:start position:0% connectivity when the signal strength is 22:21:18.240 --> 22:21:20.686 align:start position:0% connectivity when the signal strength is low 22:21:20.686 --> 22:21:20.696 align:start position:0% 22:21:20.696 --> 22:21:23.030 align:start position:0% client<22:21:21.600> devices<22:21:22.016> closer<22:21:22.616> to<22:21:22.800> the<22:21:22.920> access 22:21:23.030 --> 22:21:23.040 align:start position:0% client devices closer to the access 22:21:23.040 --> 22:21:24.526 align:start position:0% client devices closer to the access point<22:21:23.400> especially<22:21:23.872> when<22:21:24.056> you're<22:21:24.176> at<22:21:24.360> home 22:21:24.526 --> 22:21:24.536 align:start position:0% point especially when you're at home 22:21:24.536 --> 22:21:26.094 align:start position:0% point especially when you're at home actually 22:21:26.094 --> 22:21:26.104 align:start position:0% actually 22:21:26.104 --> 22:21:28.486 align:start position:0% actually if<22:21:26.760> you've<22:21:27.056> got<22:21:27.296> a<22:21:27.784> your<22:21:27.896> wireless<22:21:28.144> access 22:21:28.486 --> 22:21:28.496 align:start position:0% if you've got a your wireless access 22:21:28.496 --> 22:21:32.390 align:start position:0% if you've got a your wireless access point<22:21:28.920> in<22:21:29.640> a<22:21:30.240> different<22:21:30.600> room<22:21:31.016> and<22:21:31.976> if<22:21:32.160> you've 22:21:32.390 --> 22:21:32.400 align:start position:0% point in a different room and if you've 22:21:32.400 --> 22:21:34.246 align:start position:0% point in a different room and if you've got<22:21:32.576> an<22:21:32.872> older<22:21:33.176> house<22:21:33.296> certainly<22:21:33.720> in<22:21:33.832> the<22:21:33.960> UK 22:21:34.246 --> 22:21:34.256 align:start position:0% got an older house certainly in the UK 22:21:34.256 --> 22:21:36.646 align:start position:0% got an older house certainly in the UK most<22:21:34.616> of<22:21:34.800> the<22:21:34.920> walls<22:21:35.216> were<22:21:35.400> made<22:21:35.696> of 22:21:36.646 --> 22:21:36.656 align:start position:0% most of the walls were made of 22:21:36.656 --> 22:21:39.646 align:start position:0% most of the walls were made of um thick<22:21:37.504> concrete 22:21:39.646 --> 22:21:39.656 align:start position:0% um thick concrete 22:21:39.656 --> 22:21:42.590 align:start position:0% um thick concrete and<22:21:40.552> uh<22:21:40.920> they<22:21:41.336> built<22:21:41.760> the<22:21:41.824> houses<22:21:42.000> to<22:21:42.424> last 22:21:42.590 --> 22:21:42.600 align:start position:0% and uh they built the houses to last 22:21:42.600 --> 22:21:45.822 align:start position:0% and uh they built the houses to last there<22:21:42.832> was<22:21:43.016> no<22:21:43.464> or<22:21:44.464> very<22:21:44.760> few<22:21:44.936> false<22:21:45.480> walls 22:21:45.822 --> 22:21:45.832 align:start position:0% there was no or very few false walls 22:21:45.832 --> 22:21:47.926 align:start position:0% there was no or very few false walls inside<22:21:46.016> houses<22:21:46.440> with<22:21:46.856> just<22:21:47.104> plasterboard<22:21:47.576> or 22:21:47.926 --> 22:21:47.936 align:start position:0% inside houses with just plasterboard or 22:21:47.936 --> 22:21:49.846 align:start position:0% inside houses with just plasterboard or wood 22:21:49.846 --> 22:21:49.856 align:start position:0% wood 22:21:49.856 --> 22:21:51.774 align:start position:0% wood um<22:21:49.920> obviously<22:21:50.464> you<22:21:50.576> can<22:21:50.696> install 22:21:51.774 --> 22:21:51.784 align:start position:0% um obviously you can install 22:21:51.784 --> 22:21:53.630 align:start position:0% um obviously you can install um<22:21:51.832> a<22:21:52.376> booster<22:21:52.744> as<22:21:52.920> well<22:21:53.040> you<22:21:53.280> can<22:21:53.464> install 22:21:53.630 --> 22:21:53.640 align:start position:0% um a booster as well you can install 22:21:53.640 --> 22:21:57.526 align:start position:0% um a booster as well you can install something<22:21:54.056> in<22:21:54.424> your<22:21:54.656> power<22:21:55.376> unit<22:21:56.120> and<22:21:57.120> it<22:21:57.424> will 22:21:57.526 --> 22:21:57.536 align:start position:0% something in your power unit and it will 22:21:57.536 --> 22:22:00.886 align:start position:0% something in your power unit and it will boost<22:21:57.784> the<22:21:57.960> signal<22:21:58.376> or<22:21:58.744> act<22:21:58.976> as<22:21:59.104> a<22:21:59.280> repeater 22:22:00.886 --> 22:22:00.896 align:start position:0% boost the signal or act as a repeater 22:22:00.896 --> 22:22:03.046 align:start position:0% boost the signal or act as a repeater ensure<22:22:01.376> there's<22:22:01.616> minimal<22:22:02.056> obstructions 22:22:03.046 --> 22:22:03.056 align:start position:0% ensure there's minimal obstructions 22:22:03.056 --> 22:22:05.502 align:start position:0% ensure there's minimal obstructions metal<22:22:04.016> studs<22:22:04.552> is<22:22:04.616> another<22:22:04.800> one<22:22:05.040> that<22:22:05.336> will 22:22:05.502 --> 22:22:05.512 align:start position:0% metal studs is another one that will 22:22:05.512 --> 22:22:08.270 align:start position:0% metal studs is another one that will reduce<22:22:06.000> your<22:22:07.016> um 22:22:08.270 --> 22:22:08.280 align:start position:0% reduce your um 22:22:08.280 --> 22:22:11.030 align:start position:0% reduce your um connectivity<22:22:09.176> or<22:22:09.536> signal<22:22:09.960> ensure<22:22:10.920> the 22:22:11.030 --> 22:22:11.040 align:start position:0% connectivity or signal ensure the 22:22:11.040 --> 22:22:12.822 align:start position:0% connectivity or signal ensure the antennas<22:22:11.464> allow<22:22:11.824> communication<22:22:12.360> as<22:22:12.656> well 22:22:12.822 --> 22:22:12.832 align:start position:0% antennas allow communication as well 22:22:12.832 --> 22:22:16.134 align:start position:0% antennas allow communication as well sometimes<22:22:13.440> the<22:22:14.336> antennas<22:22:14.760> come<22:22:15.000> in<22:22:15.120> a<22:22:15.296> box 22:22:16.134 --> 22:22:16.144 align:start position:0% sometimes the antennas come in a box 22:22:16.144 --> 22:22:19.070 align:start position:0% sometimes the antennas come in a box or<22:22:17.216> um<22:22:17.216> they're<22:22:17.576> not<22:22:17.760> attached<22:22:18.424> or<22:22:18.896> they're 22:22:19.070 --> 22:22:19.080 align:start position:0% or um they're not attached or they're 22:22:19.080 --> 22:22:22.270 align:start position:0% or um they're not attached or they're just<22:22:19.256> pointed<22:22:19.552> in<22:22:19.680> the<22:22:19.800> wrong<22:22:19.976> direction 22:22:22.270 --> 22:22:22.280 align:start position:0% 22:22:22.280 --> 22:22:24.950 align:start position:0% interference<22:22:23.280> other<22:22:23.872> wireless<22:22:24.120> devices<22:22:24.656> are 22:22:24.950 --> 22:22:24.960 align:start position:0% interference other wireless devices are 22:22:24.960 --> 22:22:27.526 align:start position:0% interference other wireless devices are using<22:22:25.320> the<22:22:25.440> same<22:22:25.616> frequency<22:22:26.104> uh<22:22:27.000> you<22:22:27.240> can<22:22:27.296> also 22:22:27.526 --> 22:22:27.536 align:start position:0% using the same frequency uh you can also 22:22:27.536 --> 22:22:29.390 align:start position:0% using the same frequency uh you can also have<22:22:27.656> interference<22:22:28.256> from<22:22:28.496> microwave<22:22:28.920> ovens 22:22:29.390 --> 22:22:29.400 align:start position:0% have interference from microwave ovens 22:22:29.400 --> 22:22:31.846 align:start position:0% have interference from microwave ovens and<22:22:29.576> cordless<22:22:29.936> phones<22:22:30.480> it<22:22:31.144> tells<22:22:31.440> you<22:22:31.504> this<22:22:31.680> in 22:22:31.846 --> 22:22:31.856 align:start position:0% and cordless phones it tells you this in 22:22:31.856 --> 22:22:33.710 align:start position:0% and cordless phones it tells you this in the<22:22:31.976> documentation<22:22:32.576> but<22:22:32.936> most<22:22:33.176> people<22:22:33.424> don't 22:22:33.710 --> 22:22:33.720 align:start position:0% the documentation but most people don't 22:22:33.720 --> 22:22:36.470 align:start position:0% the documentation but most people don't read<22:22:34.016> it<22:22:34.744> when<22:22:35.216> you're<22:22:35.400> installing<22:22:36.056> your 22:22:36.470 --> 22:22:36.480 align:start position:0% read it when you're installing your 22:22:36.480 --> 22:22:38.814 align:start position:0% read it when you're installing your wireless<22:22:36.720> router<22:22:37.376> it'll<22:22:37.680> have<22:22:37.920> a<22:22:38.104> pictures<22:22:38.464> of 22:22:38.814 --> 22:22:38.824 align:start position:0% wireless router it'll have a pictures of 22:22:38.824 --> 22:22:40.686 align:start position:0% wireless router it'll have a pictures of the<22:22:39.056> kind<22:22:39.296> of<22:22:39.424> things<22:22:39.600> that<22:22:39.896> will<22:22:40.016> interfere 22:22:40.686 --> 22:22:40.696 align:start position:0% the kind of things that will interfere 22:22:40.696 --> 22:22:42.774 align:start position:0% the kind of things that will interfere with<22:22:41.696> your<22:22:41.872> signal 22:22:42.774 --> 22:22:42.784 align:start position:0% with your signal 22:22:42.784 --> 22:22:45.822 align:start position:0% with your signal you'll<22:22:43.376> get<22:22:43.552> latency<22:22:44.400> and<22:22:44.832> inconsistent 22:22:45.822 --> 22:22:45.832 align:start position:0% you'll get latency and inconsistent 22:22:45.832 --> 22:22:49.006 align:start position:0% you'll get latency and inconsistent connectivity<22:22:46.936> avoid<22:22:47.936> interference<22:22:48.600> pretty 22:22:49.006 --> 22:22:49.016 align:start position:0% connectivity avoid interference pretty 22:22:49.016 --> 22:22:52.542 align:start position:0% connectivity avoid interference pretty obvious<22:22:49.376> as<22:22:49.744> I<22:22:49.920> said<22:22:50.176> and<22:22:51.176> but<22:22:51.480> you<22:22:51.656> can<22:22:51.832> avoid 22:22:52.542 --> 22:22:52.552 align:start position:0% obvious as I said and but you can avoid 22:22:52.552 --> 22:22:54.414 align:start position:0% obvious as I said and but you can avoid having<22:22:52.800> your<22:22:53.040> devices<22:22:53.336> near<22:22:53.824> to<22:22:54.056> these<22:22:54.296> things 22:22:54.414 --> 22:22:54.424 align:start position:0% having your devices near to these things 22:22:54.424 --> 22:22:57.950 align:start position:0% having your devices near to these things like<22:22:54.720> your<22:22:54.960> ovens<22:22:55.440> or<22:22:56.104> cordless<22:22:56.512> phones 22:22:57.950 --> 22:22:57.960 align:start position:0% like your ovens or cordless phones 22:22:57.960 --> 22:22:59.270 align:start position:0% like your ovens or cordless phones um<22:22:58.016> you<22:22:58.440> may<22:22:58.496> be<22:22:58.616> able<22:22:58.744> to<22:22:58.800> change<22:22:59.104> your 22:22:59.270 --> 22:22:59.280 align:start position:0% um you may be able to change your 22:22:59.280 --> 22:23:00.646 align:start position:0% um you may be able to change your channel<22:22:59.464> as<22:22:59.696> well<22:22:59.872> if<22:23:00.000> it's<22:23:00.120> got<22:23:00.296> the<22:23:00.480> same 22:23:00.646 --> 22:23:00.656 align:start position:0% channel as well if it's got the same 22:23:00.656 --> 22:23:03.542 align:start position:0% channel as well if it's got the same channel<22:23:00.896> as<22:23:01.680> your<22:23:01.856> cordless<22:23:02.216> phone<22:23:02.400> uses 22:23:03.542 --> 22:23:03.552 align:start position:0% channel as your cordless phone uses 22:23:03.552 --> 22:23:05.686 align:start position:0% channel as your cordless phone uses overlapping<22:23:04.552> channels<22:23:05.040> because<22:23:05.336> of<22:23:05.576> the 22:23:05.686 --> 22:23:05.696 align:start position:0% overlapping channels because of the 22:23:05.696 --> 22:23:07.670 align:start position:0% overlapping channels because of the wireless<22:23:05.824> access<22:23:06.192> points<22:23:07.192> are<22:23:07.256> used<22:23:07.440> in<22:23:07.552> the 22:23:07.670 --> 22:23:07.680 align:start position:0% wireless access points are used in the 22:23:07.680 --> 22:23:09.886 align:start position:0% wireless access points are used in the same<22:23:07.800> frequency<22:23:08.280> there's<22:23:09.176> automatic<22:23:09.720> channel 22:23:09.886 --> 22:23:09.896 align:start position:0% same frequency there's automatic channel 22:23:09.896 --> 22:23:12.710 align:start position:0% same frequency there's automatic channel selection<22:23:10.440> normally<22:23:10.976> on<22:23:11.216> your<22:23:11.400> devices<22:23:11.760> but 22:23:12.710 --> 22:23:12.720 align:start position:0% selection normally on your devices but 22:23:12.720 --> 22:23:14.150 align:start position:0% selection normally on your devices but if<22:23:12.960> you<22:23:13.080> have<22:23:13.192> any 22:23:14.150 --> 22:23:14.160 align:start position:0% if you have any 22:23:14.160 --> 22:23:16.070 align:start position:0% if you have any reasonable<22:23:14.936> amount<22:23:15.240> of<22:23:15.296> ability<22:23:15.656> you<22:23:15.960> should 22:23:16.070 --> 22:23:16.080 align:start position:0% reasonable amount of ability you should 22:23:16.080 --> 22:23:17.686 align:start position:0% reasonable amount of ability you should be<22:23:16.192> able<22:23:16.320> to<22:23:16.496> log<22:23:16.744> in<22:23:16.920> and<22:23:17.160> change<22:23:17.464> your 22:23:17.686 --> 22:23:17.696 align:start position:0% be able to log in and change your 22:23:17.696 --> 22:23:20.390 align:start position:0% be able to log in and change your channels 22:23:20.390 --> 22:23:20.400 align:start position:0% 22:23:20.400 --> 22:23:23.326 align:start position:0% uh<22:23:21.176> avoid<22:23:21.656> uh<22:23:22.192> you<22:23:22.376> can<22:23:22.496> correct<22:23:23.104> it<22:23:23.216> by 22:23:23.326 --> 22:23:23.336 align:start position:0% uh avoid uh you can correct it by 22:23:23.336 --> 22:23:24.910 align:start position:0% uh avoid uh you can correct it by avoiding<22:23:23.760> the<22:23:23.872> manual<22:23:24.120> selection<22:23:24.536> of 22:23:24.910 --> 22:23:24.920 align:start position:0% avoiding the manual selection of 22:23:24.920 --> 22:23:27.286 align:start position:0% avoiding the manual selection of non-overlapping<22:23:25.920> channels 22:23:27.286 --> 22:23:27.296 align:start position:0% non-overlapping channels 22:23:27.296 --> 22:23:29.990 align:start position:0% non-overlapping channels signal<22:23:27.784> to<22:23:27.896> noise<22:23:28.144> ratio<22:23:28.744> it's<22:23:29.400> the<22:23:29.640> ratio<22:23:29.872> of 22:23:29.990 --> 22:23:30.000 align:start position:0% signal to noise ratio it's the ratio of 22:23:30.000 --> 22:23:31.246 align:start position:0% signal to noise ratio it's the ratio of the<22:23:30.120> Wi-Fi<22:23:30.424> signal<22:23:30.832> to<22:23:31.016> the<22:23:31.144> outside 22:23:31.246 --> 22:23:31.256 align:start position:0% the Wi-Fi signal to the outside 22:23:31.256 --> 22:23:34.070 align:start position:0% the Wi-Fi signal to the outside interference<22:23:32.160> or<22:23:32.400> noise<22:23:32.640> noise<22:23:33.480> is<22:23:33.784> in 22:23:34.070 --> 22:23:34.080 align:start position:0% interference or noise noise is in 22:23:34.080 --> 22:23:36.414 align:start position:0% interference or noise noise is in respect<22:23:34.320> of<22:23:34.496> Wireless<22:23:34.936> have<22:23:35.936> a<22:23:36.120> negative 22:23:36.414 --> 22:23:36.424 align:start position:0% respect of Wireless have a negative 22:23:36.424 --> 22:23:38.750 align:start position:0% respect of Wireless have a negative impact<22:23:36.784> on<22:23:37.016> your<22:23:37.144> wireless<22:23:37.320> signal<22:23:37.856> other 22:23:38.750 --> 22:23:38.760 align:start position:0% impact on your wireless signal other 22:23:38.760 --> 22:23:41.814 align:start position:0% impact on your wireless signal other Wi-Fi<22:23:39.176> signals<22:23:39.720> don't<22:23:40.080> count<22:23:40.440> as<22:23:40.680> noise 22:23:41.814 --> 22:23:41.824 align:start position:0% Wi-Fi signals don't count as noise 22:23:41.824 --> 22:23:43.846 align:start position:0% Wi-Fi signals don't count as noise this<22:23:42.536> again<22:23:42.656> will<22:23:42.960> give<22:23:43.144> you<22:23:43.256> connectivity 22:23:43.846 --> 22:23:43.856 align:start position:0% this again will give you connectivity 22:23:43.856 --> 22:23:46.486 align:start position:0% this again will give you connectivity issues<22:23:44.464> or<22:23:44.696> latency 22:23:46.486 --> 22:23:46.496 align:start position:0% issues or latency 22:23:46.496 --> 22:23:49.246 align:start position:0% issues or latency signal<22:23:47.280> levels<22:23:48.240> and<22:23:48.424> noise<22:23:48.600> levels<22:23:49.016> can<22:23:49.144> be 22:23:49.246 --> 22:23:49.256 align:start position:0% signal levels and noise levels can be 22:23:49.256 --> 22:23:51.470 align:start position:0% signal levels and noise levels can be visualized<22:23:49.744> as<22:23:49.856> heat<22:23:50.104> Maps 22:23:51.470 --> 22:23:51.480 align:start position:0% visualized as heat Maps 22:23:51.480 --> 22:23:53.686 align:start position:0% visualized as heat Maps the<22:23:51.896> ratio<22:23:52.192> of<22:23:52.376> 10<22:23:52.496> to<22:23:52.680> 15<22:23:52.800> decibels<22:23:53.464> is 22:23:53.686 --> 22:23:53.696 align:start position:0% the ratio of 10 to 15 decibels is 22:23:53.696 --> 22:23:57.230 align:start position:0% the ratio of 10 to 15 decibels is considered<22:23:54.240> unreliable 22:23:57.230 --> 22:23:57.240 align:start position:0% 22:23:57.240 --> 22:23:59.814 align:start position:0% 16<22:23:57.720> to<22:23:58.016> 24<22:23:58.256> is<22:23:58.680> weak 22:23:59.814 --> 22:23:59.824 align:start position:0% 16 to 24 is weak 22:23:59.824 --> 22:24:02.150 align:start position:0% 16 to 24 is weak issues<22:24:00.424> can<22:24:00.720> be<22:24:00.896> avoided<22:24:01.376> by<22:24:01.552> increasing<22:24:01.976> your 22:24:02.150 --> 22:24:02.160 align:start position:0% issues can be avoided by increasing your 22:24:02.160 --> 22:24:04.734 align:start position:0% issues can be avoided by increasing your signal<22:24:02.512> strength<22:24:02.872> and<22:24:03.120> decreasing<22:24:03.600> the<22:24:03.832> noise 22:24:04.734 --> 22:24:04.744 align:start position:0% signal strength and decreasing the noise 22:24:04.744 --> 22:24:06.046 align:start position:0% signal strength and decreasing the noise I<22:24:04.856> told<22:24:05.040> you<22:24:05.216> all<22:24:05.336> this<22:24:05.464> stuff<22:24:05.576> was<22:24:05.760> obvious 22:24:06.046 --> 22:24:06.056 align:start position:0% I told you all this stuff was obvious 22:24:06.056 --> 22:24:08.630 align:start position:0% I told you all this stuff was obvious device<22:24:06.832> saturation<22:24:07.552> is<22:24:07.976> when<22:24:08.160> more<22:24:08.400> wireless 22:24:08.630 --> 22:24:08.640 align:start position:0% device saturation is when more wireless 22:24:08.640 --> 22:24:10.270 align:start position:0% device saturation is when more wireless devices<22:24:09.120> are<22:24:09.424> connected<22:24:09.720> to<22:24:09.896> your<22:24:10.080> network 22:24:10.270 --> 22:24:10.280 align:start position:0% devices are connected to your network 22:24:10.280 --> 22:24:13.246 align:start position:0% devices are connected to your network you'll<22:24:11.280> get<22:24:11.464> a<22:24:11.576> decrease<22:24:11.760> throughput<22:24:12.480> that's 22:24:13.246 --> 22:24:13.256 align:start position:0% you'll get a decrease throughput that's 22:24:13.256 --> 22:24:14.502 align:start position:0% you'll get a decrease throughput that's probably<22:24:13.504> your<22:24:13.680> fault<22:24:13.920> for<22:24:14.104> letting<22:24:14.400> your 22:24:14.502 --> 22:24:14.512 align:start position:0% probably your fault for letting your 22:24:14.512 --> 22:24:17.094 align:start position:0% probably your fault for letting your kids<22:24:14.696> have<22:24:15.000> access<22:24:15.240> to<22:24:15.656> phones<22:24:16.320> at<22:24:16.496> home<22:24:16.680> or 22:24:17.094 --> 22:24:17.104 align:start position:0% kids have access to phones at home or 22:24:17.104 --> 22:24:20.326 align:start position:0% kids have access to phones at home or other<22:24:17.576> wireless<22:24:18.424> devices<22:24:19.336> bandwidth 22:24:20.326 --> 22:24:20.336 align:start position:0% other wireless devices bandwidth 22:24:20.336 --> 22:24:22.310 align:start position:0% other wireless devices bandwidth saturation<22:24:20.696> is<22:24:21.000> when<22:24:21.176> one<22:24:21.784> or<22:24:21.896> more<22:24:22.080> devices 22:24:22.310 --> 22:24:22.320 align:start position:0% saturation is when one or more devices 22:24:22.320 --> 22:24:24.526 align:start position:0% saturation is when one or more devices transmit<22:24:22.976> a<22:24:23.160> large<22:24:23.280> quality<22:24:23.696> of<22:24:23.872> quantity<22:24:24.360> of 22:24:24.526 --> 22:24:24.536 align:start position:0% transmit a large quality of quantity of 22:24:24.536 --> 22:24:26.502 align:start position:0% transmit a large quality of quantity of data 22:24:26.502 --> 22:24:26.512 align:start position:0% data 22:24:26.512 --> 22:24:28.366 align:start position:0% data um<22:24:26.576> I<22:24:26.760> would<22:24:26.936> imagine<22:24:27.056> received<22:24:27.720> also<22:24:28.016> so<22:24:28.256> if 22:24:28.366 --> 22:24:28.376 align:start position:0% um I would imagine received also so if 22:24:28.376 --> 22:24:31.070 align:start position:0% um I would imagine received also so if somebody<22:24:28.616> in<22:24:29.280> is<22:24:29.640> there<22:24:29.824> watching<22:24:30.296> YouTube<22:24:30.480> in 22:24:31.070 --> 22:24:31.080 align:start position:0% somebody in is there watching YouTube in 22:24:31.080 --> 22:24:31.910 align:start position:0% somebody in is there watching YouTube in another 22:24:31.910 --> 22:24:31.920 align:start position:0% another 22:24:31.920 --> 22:24:35.206 align:start position:0% another room<22:24:32.336> in<22:24:32.576> the<22:24:32.696> house<22:24:32.824> and<22:24:33.056> that'll<22:24:33.424> do<22:24:33.536> it 22:24:35.206 --> 22:24:35.216 align:start position:0% room in the house and that'll do it 22:24:35.216 --> 22:24:37.006 align:start position:0% room in the house and that'll do it untested<22:24:36.000> updates 22:24:37.006 --> 22:24:37.016 align:start position:0% untested updates 22:24:37.016 --> 22:24:39.046 align:start position:0% untested updates um<22:24:37.144> updates<22:24:37.552> can<22:24:37.856> obviously<22:24:38.160> break<22:24:38.464> things<22:24:38.760> if 22:24:39.046 --> 22:24:39.056 align:start position:0% um updates can obviously break things if 22:24:39.056 --> 22:24:41.150 align:start position:0% um updates can obviously break things if they<22:24:39.176> haven't<22:24:39.360> been<22:24:39.656> uh<22:24:40.192> correctly<22:24:40.744> tested 22:24:41.150 --> 22:24:41.160 align:start position:0% they haven't been uh correctly tested 22:24:41.160 --> 22:24:44.454 align:start position:0% they haven't been uh correctly tested especially<22:24:42.000> with<22:24:42.600> regards<22:24:43.016> firmware<22:24:43.616> I've 22:24:44.454 --> 22:24:44.464 align:start position:0% especially with regards firmware I've 22:24:44.464 --> 22:24:47.862 align:start position:0% especially with regards firmware I've even<22:24:44.640> recently<22:24:45.424> installed<22:24:45.832> a<22:24:46.104> an<22:24:47.104> SSD<22:24:47.576> drive 22:24:47.862 --> 22:24:47.872 align:start position:0% even recently installed a an SSD drive 22:24:47.872 --> 22:24:49.006 align:start position:0% even recently installed a an SSD drive in<22:24:48.240> my 22:24:49.006 --> 22:24:49.016 align:start position:0% in my 22:24:49.016 --> 22:24:51.950 align:start position:0% in my home<22:24:49.800> computer<22:24:50.176> and<22:24:51.176> while<22:24:51.360> I<22:24:51.536> was<22:24:51.656> just 22:24:51.950 --> 22:24:51.960 align:start position:0% home computer and while I was just 22:24:51.960 --> 22:24:54.110 align:start position:0% home computer and while I was just researching<22:24:52.552> it<22:24:52.744> I<22:24:52.920> found<22:24:53.160> that<22:24:53.760> the<22:24:54.000> latest 22:24:54.110 --> 22:24:54.120 align:start position:0% researching it I found that the latest 22:24:54.120 --> 22:24:56.166 align:start position:0% researching it I found that the latest firmware<22:24:54.720> drive<22:24:55.016> from<22:24:55.320> the<22:24:55.504> manufacturer 22:24:56.166 --> 22:24:56.176 align:start position:0% firmware drive from the manufacturer 22:24:56.176 --> 22:24:59.270 align:start position:0% firmware drive from the manufacturer actually<22:24:57.176> was<22:24:57.536> wiping<22:24:58.016> everyone's<22:24:58.552> data 22:24:59.270 --> 22:24:59.280 align:start position:0% actually was wiping everyone's data 22:24:59.280 --> 22:25:02.326 align:start position:0% actually was wiping everyone's data which<22:24:59.936> is<22:25:00.056> catastrophic<22:25:00.832> for<22:25:01.080> most<22:25:01.256> of<22:25:01.440> us<22:25:01.552> and 22:25:02.326 --> 22:25:02.336 align:start position:0% which is catastrophic for most of us and 22:25:02.336 --> 22:25:04.070 align:start position:0% which is catastrophic for most of us and the<22:25:02.464> manufacturer<22:25:03.056> was<22:25:03.296> aware<22:25:03.600> and<22:25:03.784> they<22:25:03.896> said 22:25:04.070 --> 22:25:04.080 align:start position:0% the manufacturer was aware and they said 22:25:04.080 --> 22:25:06.046 align:start position:0% the manufacturer was aware and they said they<22:25:04.256> were<22:25:04.376> releasing<22:25:04.856> an<22:25:05.040> update<22:25:05.400> but<22:25:05.872> the 22:25:06.046 --> 22:25:06.056 align:start position:0% they were releasing an update but the 22:25:06.056 --> 22:25:07.966 align:start position:0% they were releasing an update but the problem<22:25:06.176> is<22:25:06.424> if<22:25:06.656> you<22:25:06.832> downloaded<22:25:07.376> the<22:25:07.552> update 22:25:07.966 --> 22:25:07.976 align:start position:0% problem is if you downloaded the update 22:25:07.976 --> 22:25:11.030 align:start position:0% problem is if you downloaded the update it<22:25:08.640> was<22:25:08.760> too<22:25:09.056> late<22:25:09.296> for<22:25:09.600> you 22:25:11.030 --> 22:25:11.040 align:start position:0% it was too late for you 22:25:11.040 --> 22:25:13.606 align:start position:0% it was too late for you back<22:25:11.512> up<22:25:11.696> your<22:25:11.872> last<22:25:12.056> working<22:25:12.240> config<22:25:12.960> not 22:25:13.606 --> 22:25:13.616 align:start position:0% back up your last working config not 22:25:13.616 --> 22:25:15.046 align:start position:0% back up your last working config not sure<22:25:13.744> how<22:25:13.920> you<22:25:14.040> do<22:25:14.216> that<22:25:14.336> with<22:25:14.512> your<22:25:14.640> firmware 22:25:15.046 --> 22:25:15.056 align:start position:0% sure how you do that with your firmware 22:25:15.056 --> 22:25:16.790 align:start position:0% sure how you do that with your firmware actually<22:25:15.360> but<22:25:15.896> you<22:25:16.080> can<22:25:16.192> research<22:25:16.616> that 22:25:16.790 --> 22:25:16.800 align:start position:0% actually but you can research that 22:25:16.800 --> 22:25:20.630 align:start position:0% actually but you can research that yourself<22:25:17.056> wrong<22:25:18.056> SSID<22:25:18.976> all<22:25:19.976> you<22:25:20.104> need<22:25:20.280> to<22:25:20.464> do 22:25:20.630 --> 22:25:20.640 align:start position:0% yourself wrong SSID all you need to do 22:25:20.640 --> 22:25:22.542 align:start position:0% yourself wrong SSID all you need to do because<22:25:20.936> they're<22:25:21.424> case<22:25:21.720> sensitive<22:25:22.192> you<22:25:22.440> could 22:25:22.542 --> 22:25:22.552 align:start position:0% because they're case sensitive you could 22:25:22.552 --> 22:25:24.774 align:start position:0% because they're case sensitive you could have<22:25:22.680> the<22:25:22.920> wrong<22:25:23.104> case<22:25:23.400> or<22:25:24.056> just<22:25:24.240> mistype 22:25:24.774 --> 22:25:24.784 align:start position:0% have the wrong case or just mistype 22:25:24.784 --> 22:25:26.206 align:start position:0% have the wrong case or just mistype something 22:25:26.206 --> 22:25:26.216 align:start position:0% something 22:25:26.216 --> 22:25:27.646 align:start position:0% something a<22:25:26.512> lot<22:25:26.640> of<22:25:26.760> the<22:25:26.824> time<22:25:26.936> when<22:25:27.120> you<22:25:27.240> type<22:25:27.360> these 22:25:27.646 --> 22:25:27.656 align:start position:0% a lot of the time when you type these 22:25:27.656 --> 22:25:29.150 align:start position:0% a lot of the time when you type these out<22:25:27.784> you<22:25:28.144> can't<22:25:28.192> actually<22:25:28.376> see<22:25:28.616> the<22:25:28.856> letters 22:25:29.150 --> 22:25:29.160 align:start position:0% out you can't actually see the letters 22:25:29.160 --> 22:25:31.366 align:start position:0% out you can't actually see the letters you're<22:25:29.336> typing<22:25:29.824> unless<22:25:30.296> there's<22:25:30.480> a<22:25:30.784> an<22:25:31.080> option 22:25:31.366 --> 22:25:31.376 align:start position:0% you're typing unless there's a an option 22:25:31.376 --> 22:25:33.350 align:start position:0% you're typing unless there's a an option for<22:25:31.680> you<22:25:31.856> to<22:25:31.976> do<22:25:32.160> that<22:25:32.400> so<22:25:32.936> you<22:25:33.120> could<22:25:33.176> well 22:25:33.350 --> 22:25:33.360 align:start position:0% for you to do that so you could well 22:25:33.360 --> 22:25:34.542 align:start position:0% for you to do that so you could well have<22:25:33.480> typed<22:25:33.784> out<22:25:33.896> the<22:25:34.016> incorrect<22:25:34.376> password 22:25:34.542 --> 22:25:34.552 align:start position:0% have typed out the incorrect password 22:25:34.552 --> 22:25:37.494 align:start position:0% have typed out the incorrect password but<22:25:34.976> you<22:25:35.160> can't<22:25:35.280> see<22:25:35.512> it 22:25:37.494 --> 22:25:37.504 align:start position:0% but you can't see it 22:25:37.504 --> 22:25:39.414 align:start position:0% but you can't see it avoid<22:25:38.040> having<22:25:38.280> the<22:25:38.464> client<22:25:38.696> device<22:25:38.872> and<22:25:39.296> the 22:25:39.414 --> 22:25:39.424 align:start position:0% avoid having the client device and the 22:25:39.424 --> 22:25:44.094 align:start position:0% avoid having the client device and the access<22:25:39.600> point<22:25:40.496> set<22:25:40.976> to<22:25:41.216> use<22:25:41.336> the<22:25:41.576> same<22:25:41.696> SSID 22:25:44.094 --> 22:25:44.104 align:start position:0% access point set to use the same SSID 22:25:44.104 --> 22:25:46.734 align:start position:0% access point set to use the same SSID power<22:25:44.696> levels<22:25:45.240> uh<22:25:45.784> users<22:25:46.080> will<22:25:46.192> experience<22:25:46.616> a 22:25:46.734 --> 22:25:46.744 align:start position:0% power levels uh users will experience a 22:25:46.744 --> 22:25:48.846 align:start position:0% power levels uh users will experience a big<22:25:46.920> coverage<22:25:47.216> area<22:25:47.464> or<22:25:47.872> small 22:25:48.846 --> 22:25:48.856 align:start position:0% big coverage area or small 22:25:48.856 --> 22:25:51.046 align:start position:0% big coverage area or small coverage<22:25:49.856> area<22:25:50.040> because<22:25:50.400> of<22:25:50.640> low<22:25:50.824> power 22:25:51.046 --> 22:25:51.056 align:start position:0% coverage area because of low power 22:25:51.056 --> 22:25:53.750 align:start position:0% coverage area because of low power levels<22:25:51.480> and<22:25:51.656> access<22:25:51.832> points<22:25:52.976> big<22:25:53.400> coverage 22:25:53.750 --> 22:25:53.760 align:start position:0% levels and access points big coverage 22:25:53.760 --> 22:25:56.566 align:start position:0% levels and access points big coverage areas<22:25:54.176> occur<22:25:54.536> because<22:25:54.784> of<22:25:55.144> high<22:25:55.680> power<22:25:55.976> levels 22:25:56.566 --> 22:25:56.576 align:start position:0% areas occur because of high power levels 22:25:56.576 --> 22:25:58.134 align:start position:0% areas occur because of high power levels and<22:25:56.696> access<22:25:56.872> points 22:25:58.134 --> 22:25:58.144 align:start position:0% and access points 22:25:58.144 --> 22:26:00.166 align:start position:0% and access points and<22:25:58.680> avoid<22:25:59.104> it<22:25:59.280> by<22:25:59.464> adjusting<22:25:59.872> the<22:26:00.000> power 22:26:00.166 --> 22:26:00.176 align:start position:0% and avoid it by adjusting the power 22:26:00.176 --> 22:26:03.710 align:start position:0% and avoid it by adjusting the power levels<22:26:00.656> for<22:26:00.896> a<22:26:01.016> good<22:26:01.144> coverage<22:26:01.552> area 22:26:03.710 --> 22:26:03.720 align:start position:0% levels for a good coverage area 22:26:03.720 --> 22:26:05.686 align:start position:0% levels for a good coverage area open<22:26:04.320> network<22:26:04.616> is<22:26:04.920> an<22:26:05.104> unsecured<22:26:05.512> wireless 22:26:05.686 --> 22:26:05.696 align:start position:0% open network is an unsecured wireless 22:26:05.696 --> 22:26:07.366 align:start position:0% open network is an unsecured wireless network<22:26:06.120> you<22:26:06.536> used<22:26:06.720> to<22:26:06.832> see<22:26:06.960> a<22:26:07.080> lot<22:26:07.192> of<22:26:07.256> those 22:26:07.366 --> 22:26:07.376 align:start position:0% network you used to see a lot of those 22:26:07.376 --> 22:26:09.710 align:start position:0% network you used to see a lot of those around<22:26:07.616> but<22:26:07.976> most<22:26:08.160> people<22:26:08.464> now<22:26:08.824> have<22:26:09.424> become 22:26:09.710 --> 22:26:09.720 align:start position:0% around but most people now have become 22:26:09.720 --> 22:26:13.070 align:start position:0% around but most people now have become Savvy<22:26:10.376> or<22:26:11.104> the<22:26:11.464> default<22:26:12.176> settings<22:26:12.480> on<22:26:12.960> the 22:26:13.070 --> 22:26:13.080 align:start position:0% Savvy or the default settings on the 22:26:13.080 --> 22:26:16.734 align:start position:0% Savvy or the default settings on the home<22:26:13.256> routers<22:26:13.856> I've<22:26:14.760> got<22:26:14.936> security<22:26:15.744> chosen 22:26:16.734 --> 22:26:16.744 align:start position:0% home routers I've got security chosen 22:26:16.744 --> 22:26:18.286 align:start position:0% home routers I've got security chosen automatically 22:26:18.286 --> 22:26:18.296 align:start position:0% automatically 22:26:18.296 --> 22:26:20.454 align:start position:0% automatically unauthorized<22:26:19.256> devices<22:26:19.552> May<22:26:19.856> connect<22:26:20.040> to<22:26:20.280> the 22:26:20.454 --> 22:26:20.464 align:start position:0% unauthorized devices May connect to the 22:26:20.464 --> 22:26:22.966 align:start position:0% unauthorized devices May connect to the network<22:26:20.576> if<22:26:20.936> it's<22:26:21.176> insecure<22:26:21.896> so<22:26:22.552> obviously 22:26:22.966 --> 22:26:22.976 align:start position:0% network if it's insecure so obviously 22:26:22.976 --> 22:26:24.886 align:start position:0% network if it's insecure so obviously change<22:26:23.216> the<22:26:23.512> security<22:26:23.760> settings<22:26:24.176> if<22:26:24.600> this<22:26:24.784> is 22:26:24.886 --> 22:26:24.896 align:start position:0% change the security settings if this is 22:26:24.896 --> 22:26:25.846 align:start position:0% change the security settings if this is the<22:26:25.144> case 22:26:25.846 --> 22:26:25.856 align:start position:0% the case 22:26:25.856 --> 22:26:29.150 align:start position:0% the case Rogue<22:26:26.640> access<22:26:26.824> points<22:26:27.536> as<22:26:28.144> an<22:26:28.440> authorized 22:26:29.150 --> 22:26:29.160 align:start position:0% Rogue access points as an authorized 22:26:29.160 --> 22:26:30.910 align:start position:0% Rogue access points as an authorized access<22:26:29.280> point<22:26:29.640> installed<22:26:30.120> on<22:26:30.240> the<22:26:30.360> network 22:26:30.910 --> 22:26:30.920 align:start position:0% access point installed on the network 22:26:30.920 --> 22:26:34.134 align:start position:0% access point installed on the network normally<22:26:31.920> employees<22:26:32.696> uh<22:26:33.296> just<22:26:33.600> for<22:26:33.784> a<22:26:33.896> bit<22:26:34.016> of 22:26:34.134 --> 22:26:34.144 align:start position:0% normally employees uh just for a bit of 22:26:34.144 --> 22:26:36.414 align:start position:0% normally employees uh just for a bit of convenience<22:26:34.496> will<22:26:34.800> go<22:26:34.976> into<22:26:35.104> their<22:26:35.400> desk<22:26:35.696> and 22:26:36.414 --> 22:26:36.424 align:start position:0% convenience will go into their desk and 22:26:36.424 --> 22:26:38.950 align:start position:0% convenience will go into their desk and plug<22:26:36.720> something<22:26:37.016> in<22:26:37.376> to<22:26:38.040> get<22:26:38.216> wireless<22:26:38.400> access 22:26:38.950 --> 22:26:38.960 align:start position:0% plug something in to get wireless access 22:26:38.960 --> 22:26:41.390 align:start position:0% plug something in to get wireless access malicious<22:26:39.960> attacker<22:26:40.496> can<22:26:40.616> install<22:26:40.800> Rogue 22:26:41.390 --> 22:26:41.400 align:start position:0% malicious attacker can install Rogue 22:26:41.400 --> 22:26:43.966 align:start position:0% malicious attacker can install Rogue access<22:26:41.512> points<22:26:42.256> uh<22:26:43.256> thus<22:26:43.552> getting<22:26:43.744> them 22:26:43.966 --> 22:26:43.976 align:start position:0% access points uh thus getting them 22:26:43.976 --> 22:26:46.846 align:start position:0% access points uh thus getting them access<22:26:44.160> to<22:26:44.824> the<22:26:45.296> network 22:26:46.846 --> 22:26:46.856 align:start position:0% access to the network 22:26:46.856 --> 22:26:49.310 align:start position:0% access to the network wrong<22:26:47.336> antenna<22:26:48.056> type<22:26:48.240> signal<22:26:49.016> coverage 22:26:49.310 --> 22:26:49.320 align:start position:0% wrong antenna type signal coverage 22:26:49.320 --> 22:26:51.646 align:start position:0% wrong antenna type signal coverage depends<22:26:49.744> on<22:26:49.856> your<22:26:50.040> type<22:26:50.216> of<22:26:50.400> antenna<22:26:50.936> so<22:26:51.536> you 22:26:51.646 --> 22:26:51.656 align:start position:0% depends on your type of antenna so you 22:26:51.656 --> 22:26:55.910 align:start position:0% depends on your type of antenna so you could<22:26:51.784> have<22:26:51.960> no<22:26:52.440> signal<22:26:52.976> or<22:26:53.400> poor<22:26:53.760> signal<22:26:54.120> or 22:26:55.910 --> 22:26:55.920 align:start position:0% could have no signal or poor signal or 22:26:55.920 --> 22:26:58.134 align:start position:0% could have no signal or poor signal or um<22:26:55.976> a<22:26:56.640> good<22:26:56.760> signal<22:26:57.120> but<22:26:57.360> far<22:26:57.600> away<22:26:57.784> from<22:26:57.960> the 22:26:58.134 --> 22:26:58.144 align:start position:0% um a good signal but far away from the 22:26:58.144 --> 22:27:00.822 align:start position:0% um a good signal but far away from the access<22:26:58.320> point 22:27:00.822 --> 22:27:00.832 align:start position:0% 22:27:00.832 --> 22:27:01.862 align:start position:0% okay 22:27:01.862 --> 22:27:01.872 align:start position:0% okay 22:27:01.872 --> 22:27:04.134 align:start position:0% okay omnidirectional<22:27:02.872> and<22:27:03.360> directional<22:27:03.832> are<22:27:03.896> two 22:27:04.134 --> 22:27:04.144 align:start position:0% omnidirectional and directional are two 22:27:04.144 --> 22:27:06.590 align:start position:0% omnidirectional and directional are two main<22:27:04.320> types<22:27:04.616> of<22:27:04.744> antenna<22:27:05.640> omnidirectional 22:27:06.590 --> 22:27:06.600 align:start position:0% main types of antenna omnidirectional 22:27:06.600 --> 22:27:11.950 align:start position:0% main types of antenna omnidirectional gives<22:27:06.832> you<22:27:06.960> 360<22:27:07.376> degree<22:27:08.216> degree<22:27:09.120> patterns 22:27:11.950 --> 22:27:11.960 align:start position:0% gives you 360 degree degree patterns 22:27:11.960 --> 22:27:15.230 align:start position:0% gives you 360 degree degree patterns suitable<22:27:12.960> for<22:27:13.440> inside<22:27:13.800> an<22:27:14.336> office<22:27:14.512> conference 22:27:15.230 --> 22:27:15.240 align:start position:0% suitable for inside an office conference 22:27:15.240 --> 22:27:16.670 align:start position:0% suitable for inside an office conference area 22:27:16.670 --> 22:27:16.680 align:start position:0% area 22:27:16.680 --> 22:27:18.950 align:start position:0% area directional<22:27:17.464> will<22:27:17.640> give<22:27:17.824> you<22:27:17.936> a<22:27:18.240> signal<22:27:18.480> in<22:27:18.832> a 22:27:18.950 --> 22:27:18.960 align:start position:0% directional will give you a signal in a 22:27:18.960 --> 22:27:21.774 align:start position:0% directional will give you a signal in a particular<22:27:19.256> direction<22:27:19.552> so<22:27:20.216> your<22:27:20.824> coverage<22:27:21.536> is 22:27:21.774 --> 22:27:21.784 align:start position:0% particular direction so your coverage is 22:27:21.784 --> 22:27:25.430 align:start position:0% particular direction so your coverage is limited<22:27:22.320> to<22:27:22.744> that<22:27:22.976> One<22:27:23.216> Direction 22:27:25.430 --> 22:27:25.440 align:start position:0% limited to that One Direction 22:27:25.440 --> 22:27:27.846 align:start position:0% limited to that One Direction you<22:27:25.920> got<22:27:26.104> a<22:27:26.576> yagi 22:27:27.846 --> 22:27:27.856 align:start position:0% you got a yagi 22:27:27.856 --> 22:27:32.990 align:start position:0% you got a yagi parabolic<22:27:28.856> grid<22:27:29.280> patch<22:27:30.240> and<22:27:30.832> panel<22:27:31.256> antennas 22:27:32.990 --> 22:27:33.000 align:start position:0% parabolic grid patch and panel antennas 22:27:33.000 --> 22:27:36.886 align:start position:0% parabolic grid patch and panel antennas the<22:27:33.784> jaegi<22:27:34.616> and<22:27:34.800> parabolic<22:27:35.424> grid<22:27:36.424> are<22:27:36.600> used<22:27:36.720> to 22:27:36.886 --> 22:27:36.896 align:start position:0% the jaegi and parabolic grid are used to 22:27:36.896 --> 22:27:38.926 align:start position:0% the jaegi and parabolic grid are used to connect<22:27:37.016> one<22:27:37.256> building<22:27:37.552> to<22:27:37.856> another<22:27:38.040> you<22:27:38.760> must 22:27:38.926 --> 22:27:38.936 align:start position:0% connect one building to another you must 22:27:38.936 --> 22:27:41.502 align:start position:0% connect one building to another you must have<22:27:39.056> line<22:27:39.296> of<22:27:39.600> sight<22:27:39.720> so<22:27:39.960> if<22:27:40.144> somebody's<22:27:40.680> got 22:27:41.502 --> 22:27:41.512 align:start position:0% have line of sight so if somebody's got 22:27:41.512 --> 22:27:44.030 align:start position:0% have line of sight so if somebody's got a<22:27:41.696> tree<22:27:41.872> there<22:27:42.240> or<22:27:42.600> something<22:27:43.144> else<22:27:43.376> temporary 22:27:44.030 --> 22:27:44.040 align:start position:0% a tree there or something else temporary 22:27:44.040 --> 22:27:45.470 align:start position:0% a tree there or something else temporary or<22:27:44.336> permanent<22:27:44.696> then<22:27:44.936> it's<22:27:45.056> going<22:27:45.176> to<22:27:45.296> cause 22:27:45.470 --> 22:27:45.480 align:start position:0% or permanent then it's going to cause 22:27:45.480 --> 22:27:48.110 align:start position:0% or permanent then it's going to cause you<22:27:45.800> issues<22:27:46.800> that<22:27:47.160> you'll<22:27:47.464> have<22:27:47.936> to 22:27:48.110 --> 22:27:48.120 align:start position:0% you issues that you'll have to 22:27:48.120 --> 22:27:49.542 align:start position:0% you issues that you'll have to troubleshoot 22:27:49.542 --> 22:27:49.552 align:start position:0% troubleshoot 22:27:49.552 --> 22:27:50.814 align:start position:0% troubleshoot and<22:27:49.920> if<22:27:50.040> you<22:27:50.216> see<22:27:50.336> if<22:27:50.696> there's 22:27:50.814 --> 22:27:50.824 align:start position:0% and if you see if there's 22:27:50.824 --> 22:27:52.910 align:start position:0% and if you see if there's incompatibilities<22:27:51.720> users<22:27:52.320> may<22:27:52.496> not<22:27:52.616> be<22:27:52.800> able 22:27:52.910 --> 22:27:52.920 align:start position:0% incompatibilities users may not be able 22:27:52.920 --> 22:27:55.310 align:start position:0% incompatibilities users may not be able to<22:27:53.040> get<22:27:53.216> access<22:27:53.400> to<22:27:53.760> the<22:27:53.872> WAP<22:27:54.240> the<22:27:55.144> settings 22:27:55.310 --> 22:27:55.320 align:start position:0% to get access to the WAP the settings 22:27:55.320 --> 22:27:58.542 align:start position:0% to get access to the WAP the settings may<22:27:55.856> be<22:27:56.040> incompatible<22:27:57.144> standard<22:27:58.144> supporting 22:27:58.542 --> 22:27:58.552 align:start position:0% may be incompatible standard supporting 22:27:58.552 --> 22:28:01.134 align:start position:0% may be incompatible standard supporting if<22:27:58.744> you've<22:27:58.920> got<22:27:59.104> a<22:27:59.280> very<22:27:59.464> old 22:28:01.134 --> 22:28:01.144 align:start position:0% if you've got a very old 22:28:01.144 --> 22:28:03.110 align:start position:0% if you've got a very old um<22:28:01.256> Wireless<22:28:01.856> car<22:28:02.280> that<22:28:02.576> you've<22:28:02.696> got<22:28:02.824> on<22:28:03.000> your 22:28:03.110 --> 22:28:03.120 align:start position:0% um Wireless car that you've got on your 22:28:03.120 --> 22:28:06.646 align:start position:0% um Wireless car that you've got on your device<22:28:03.360> a<22:28:03.656> PCI<22:28:04.192> card<22:28:04.440> or<22:28:04.744> USB<22:28:05.280> it<22:28:06.120> might<22:28:06.296> not<22:28:06.424> be 22:28:06.646 --> 22:28:06.656 align:start position:0% device a PCI card or USB it might not be 22:28:06.656 --> 22:28:09.646 align:start position:0% device a PCI card or USB it might not be compatible<22:28:07.080> with<22:28:07.376> your<22:28:07.552> other<22:28:07.744> device 22:28:09.646 --> 22:28:09.656 align:start position:0% compatible with your other device 22:28:09.656 --> 22:28:13.310 align:start position:0% compatible with your other device so<22:28:10.576> 802.11a<22:28:11.576> is<22:28:11.760> not<22:28:12.000> compatible<22:28:12.360> with<22:28:12.600> 11b 22:28:13.310 --> 22:28:13.320 align:start position:0% so 802.11a is not compatible with 11b 22:28:13.320 --> 22:28:15.886 align:start position:0% so 802.11a is not compatible with 11b and<22:28:13.800> 11g 22:28:15.886 --> 22:28:15.896 align:start position:0% and 11g 22:28:15.896 --> 22:28:17.566 align:start position:0% and 11g you've<22:28:16.376> got<22:28:16.376> to<22:28:16.496> look<22:28:16.616> at<22:28:16.744> what<22:28:16.920> is<22:28:17.040> compatible 22:28:17.566 --> 22:28:17.576 align:start position:0% you've got to look at what is compatible 22:28:17.576 --> 22:28:20.206 align:start position:0% you've got to look at what is compatible so<22:28:17.936> B<22:28:18.176> is<22:28:18.360> compatible<22:28:18.784> with<22:28:19.080> G<22:28:19.256> and<22:28:19.504> vice<22:28:19.744> versa 22:28:20.206 --> 22:28:20.216 align:start position:0% so B is compatible with G and vice versa 22:28:20.216 --> 22:28:22.750 align:start position:0% so B is compatible with G and vice versa some<22:28:21.056> are<22:28:21.360> backward<22:28:21.720> compatibility 22:28:22.750 --> 22:28:22.760 align:start position:0% some are backward compatibility 22:28:22.760 --> 22:28:26.454 align:start position:0% some are backward compatibility compatible<22:28:23.960> others<22:28:24.960> aren't 22:28:26.454 --> 22:28:26.464 align:start position:0% compatible others aren't 22:28:26.464 --> 22:28:29.206 align:start position:0% compatible others aren't uh<22:28:27.000> wrong<22:28:27.176> encryption<22:28:27.832> you<22:28:28.376> may<22:28:28.552> not<22:28:28.680> be<22:28:28.856> uh 22:28:29.206 --> 22:28:29.216 align:start position:0% uh wrong encryption you may not be uh 22:28:29.216 --> 22:28:30.950 align:start position:0% uh wrong encryption you may not be uh get<22:28:29.512> a<22:28:29.696> connection<22:28:30.000> with<22:28:30.536> the<22:28:30.720> wireless 22:28:30.950 --> 22:28:30.960 align:start position:0% get a connection with the wireless 22:28:30.960 --> 22:28:32.862 align:start position:0% get a connection with the wireless access<22:28:31.256> points 22:28:32.862 --> 22:28:32.872 align:start position:0% access points 22:28:32.872 --> 22:28:34.430 align:start position:0% access points the<22:28:33.296> client<22:28:33.480> device<22:28:33.720> and<22:28:33.960> wireless<22:28:34.144> access 22:28:34.430 --> 22:28:34.440 align:start position:0% the client device and wireless access 22:28:34.440 --> 22:28:35.990 align:start position:0% the client device and wireless access may<22:28:34.920> have<22:28:35.040> different<22:28:35.216> encryption<22:28:35.824> settings 22:28:35.990 --> 22:28:36.000 align:start position:0% may have different encryption settings 22:28:36.000 --> 22:28:38.750 align:start position:0% may have different encryption settings so<22:28:36.360> you<22:28:36.536> need<22:28:36.720> to<22:28:36.832> check<22:28:37.144> that 22:28:38.750 --> 22:28:38.760 align:start position:0% so you need to check that 22:28:38.760 --> 22:28:40.246 align:start position:0% so you need to check that um what's<22:28:39.296> configured<22:28:39.784> on<22:28:39.960> your<22:28:40.080> access 22:28:40.246 --> 22:28:40.256 align:start position:0% um what's configured on your access 22:28:40.256 --> 22:28:43.734 align:start position:0% um what's configured on your access point<22:28:40.616> is<22:28:41.336> matching<22:28:41.824> on<22:28:42.176> your<22:28:42.536> wireless<22:28:43.192> card 22:28:43.734 --> 22:28:43.744 align:start position:0% point is matching on your wireless card 22:28:43.744 --> 22:28:46.182 align:start position:0% point is matching on your wireless card or<22:28:43.976> wireless<22:28:44.160> device<22:28:44.512> whatever<22:28:44.872> you're<22:28:45.176> using 22:28:46.182 --> 22:28:46.192 align:start position:0% or wireless device whatever you're using 22:28:46.192 --> 22:28:48.774 align:start position:0% or wireless device whatever you're using so<22:28:46.744> do<22:28:46.976> configure<22:28:47.400> it<22:28:47.576> correctly<22:28:47.936> examples 22:28:48.774 --> 22:28:48.784 align:start position:0% so do configure it correctly examples 22:28:48.784 --> 22:28:52.790 align:start position:0% so do configure it correctly examples are<22:28:49.016> web<22:28:49.256> WPA<22:28:50.160> and<22:28:50.336> WPA2 22:28:52.790 --> 22:28:52.800 align:start position:0% are web WPA and WPA2 22:28:52.800 --> 22:28:54.774 align:start position:0% are web WPA and WPA2 bounce<22:28:53.336> is<22:28:53.576> when<22:28:53.696> your<22:28:53.824> signal<22:28:54.120> bounces<22:28:54.536> off 22:28:54.774 --> 22:28:54.784 align:start position:0% bounce is when your signal bounces off 22:28:54.784 --> 22:28:56.990 align:start position:0% bounce is when your signal bounces off an<22:28:55.104> obstacle<22:28:56.104> without<22:28:56.400> reaching<22:28:56.872> the 22:28:56.990 --> 22:28:57.000 align:start position:0% an obstacle without reaching the 22:28:57.000 --> 22:28:59.454 align:start position:0% an obstacle without reaching the destination<22:28:57.616> you<22:28:58.616> can<22:28:58.680> get<22:28:58.800> weak<22:28:59.160> or<22:28:59.280> no 22:28:59.454 --> 22:28:59.464 align:start position:0% destination you can get weak or no 22:28:59.464 --> 22:29:01.430 align:start position:0% destination you can get weak or no connectivity<22:29:00.056> you<22:29:00.896> need<22:29:00.960> to<22:29:01.080> remove<22:29:01.192> the 22:29:01.430 --> 22:29:01.440 align:start position:0% connectivity you need to remove the 22:29:01.440 --> 22:29:03.414 align:start position:0% connectivity you need to remove the obstacle<22:29:01.920> obviously<22:29:02.824> sometimes<22:29:03.240> that's 22:29:03.414 --> 22:29:03.424 align:start position:0% obstacle obviously sometimes that's 22:29:03.424 --> 22:29:05.270 align:start position:0% obstacle obviously sometimes that's easier<22:29:03.832> said<22:29:04.016> than<22:29:04.192> done<22:29:04.376> so<22:29:04.680> if<22:29:04.856> it's<22:29:05.040> a<22:29:05.160> big 22:29:05.270 --> 22:29:05.280 align:start position:0% easier said than done so if it's a big 22:29:05.280 --> 22:29:07.006 align:start position:0% easier said than done so if it's a big thick<22:29:05.512> concrete<22:29:05.936> wall<22:29:06.056> in<22:29:06.360> your<22:29:06.536> house<22:29:06.720> don't 22:29:07.006 --> 22:29:07.016 align:start position:0% thick concrete wall in your house don't 22:29:07.016 --> 22:29:08.926 align:start position:0% thick concrete wall in your house don't don't<22:29:07.256> knock<22:29:07.552> it<22:29:07.744> down<22:29:07.920> because<22:29:08.400> your<22:29:08.696> roof 22:29:08.926 --> 22:29:08.936 align:start position:0% don't knock it down because your roof 22:29:08.936 --> 22:29:10.910 align:start position:0% don't knock it down because your roof will<22:29:09.120> fall<22:29:09.240> down<22:29:09.480> you<22:29:10.144> need<22:29:10.256> to<22:29:10.440> either<22:29:10.552> get 22:29:10.910 --> 22:29:10.920 align:start position:0% will fall down you need to either get 22:29:10.920 --> 22:29:12.590 align:start position:0% will fall down you need to either get some<22:29:11.104> sort<22:29:11.280> of<22:29:11.400> booster 22:29:12.590 --> 22:29:12.600 align:start position:0% some sort of booster 22:29:12.600 --> 22:29:15.590 align:start position:0% some sort of booster or<22:29:13.856> um<22:29:13.856> move<22:29:14.336> where<22:29:14.760> you're<22:29:14.872> connecting<22:29:15.296> from 22:29:15.590 --> 22:29:15.600 align:start position:0% or um move where you're connecting from 22:29:15.600 --> 22:29:17.502 align:start position:0% or um move where you're connecting from or<22:29:16.016> just<22:29:16.192> find<22:29:16.440> a<22:29:16.744> alternative<22:29:17.216> connection 22:29:17.502 --> 22:29:17.512 align:start position:0% or just find a alternative connection 22:29:17.512 --> 22:29:18.774 align:start position:0% or just find a alternative connection type 22:29:18.774 --> 22:29:18.784 align:start position:0% type 22:29:18.784 --> 22:29:21.110 align:start position:0% type such<22:29:19.376> as<22:29:19.616> connecting<22:29:20.040> through<22:29:20.336> the<22:29:21.120> um 22:29:21.110 --> 22:29:21.120 align:start position:0% such as connecting through the um 22:29:21.120 --> 22:29:23.030 align:start position:0% such as connecting through the um ethernet<22:29:21.832> devices<22:29:22.256> that<22:29:22.552> were<22:29:22.680> plugged<22:29:22.976> into 22:29:23.030 --> 22:29:23.040 align:start position:0% ethernet devices that were plugged into 22:29:23.040 --> 22:29:24.286 align:start position:0% ethernet devices that were plugged into your<22:29:23.280> power 22:29:24.286 --> 22:29:24.296 align:start position:0% your power 22:29:24.296 --> 22:29:26.206 align:start position:0% your power all<22:29:24.656> right<22:29:24.832> so<22:29:24.960> we've<22:29:25.144> covered<22:29:25.440> a<22:29:25.616> lot<22:29:25.744> a 22:29:26.206 --> 22:29:26.216 align:start position:0% all right so we've covered a lot a 22:29:26.216 --> 22:29:29.350 align:start position:0% all right so we've covered a lot a signal<22:29:26.640> loss<22:29:27.056> interference<22:29:27.720> signal<22:29:28.144> to<22:29:28.320> noise 22:29:29.350 --> 22:29:29.360 align:start position:0% signal loss interference signal to noise 22:29:29.360 --> 22:29:33.046 align:start position:0% signal loss interference signal to noise saturation<22:29:30.376> bandwidth<22:29:31.376> saturation 22:29:33.046 --> 22:29:33.056 align:start position:0% saturation bandwidth saturation 22:29:33.056 --> 22:29:36.886 align:start position:0% saturation bandwidth saturation untested<22:29:33.896> updates<22:29:34.320> wrong<22:29:35.280> SSID<22:29:36.056> and<22:29:36.720> your 22:29:36.886 --> 22:29:36.896 align:start position:0% untested updates wrong SSID and your 22:29:36.896 --> 22:29:37.790 align:start position:0% untested updates wrong SSID and your power 22:29:37.790 --> 22:29:37.800 align:start position:0% power 22:29:37.800 --> 22:29:41.814 align:start position:0% power open<22:29:38.216> networks<22:29:39.056> Rogue<22:29:39.720> access<22:29:39.832> points 22:29:41.814 --> 22:29:41.824 align:start position:0% open networks Rogue access points 22:29:41.824 --> 22:29:44.526 align:start position:0% open networks Rogue access points the<22:29:42.176> wrong<22:29:42.296> antenna<22:29:42.896> type<22:29:43.336> incompatibilities 22:29:44.526 --> 22:29:44.536 align:start position:0% the wrong antenna type incompatibilities 22:29:44.536 --> 22:29:48.414 align:start position:0% the wrong antenna type incompatibilities are<22:29:45.536> on<22:29:45.784> encryption<22:29:46.320> and<22:29:46.856> bounce<22:29:47.176> that's<22:29:48.176> all 22:29:48.414 --> 22:29:48.424 align:start position:0% are on encryption and bounce that's all 22:29:48.424 --> 22:29:53.090 align:start position:0% are on encryption and bounce that's all for<22:29:48.600> now<22:29:48.784> thanks<22:29:49.080> for<22:29:49.192> watching 22:29:53.090 --> 22:29:53.100 align:start position:0% 22:29:53.100 --> 22:30:01.502 align:start position:0% [Music] 22:30:01.502 --> 22:30:01.512 align:start position:0% [Music] 22:30:01.512 --> 22:30:08.990 align:start position:0% [Music] thank<22:30:02.512> you 22:30:08.990 --> 22:30:09.000 align:start position:0% 22:30:09.000 --> 22:30:11.814 align:start position:0% welcome<22:30:09.424> to<22:30:09.720> module<22:30:10.080> 19<22:30:10.256> lesson<22:30:10.856> 2<22:30:11.040> Common 22:30:11.814 --> 22:30:11.824 align:start position:0% welcome to module 19 lesson 2 Common 22:30:11.824 --> 22:30:15.350 align:start position:0% welcome to module 19 lesson 2 Common copper<22:30:12.536> cable<22:30:12.960> issues<22:30:13.680> that's<22:30:14.216> a<22:30:14.464> mouthful 22:30:15.350 --> 22:30:15.360 align:start position:0% copper cable issues that's a mouthful 22:30:15.360 --> 22:30:17.326 align:start position:0% copper cable issues that's a mouthful so<22:30:15.832> some<22:30:16.080> of<22:30:16.192> the<22:30:16.320> common<22:30:16.496> issues<22:30:17.040> you'll 22:30:17.326 --> 22:30:17.336 align:start position:0% so some of the common issues you'll 22:30:17.336 --> 22:30:20.030 align:start position:0% so some of the common issues you'll experience<22:30:17.824> as<22:30:18.120> a<22:30:18.360> network<22:30:18.536> engineer 22:30:20.030 --> 22:30:20.040 align:start position:0% experience as a network engineer 22:30:20.040 --> 22:30:23.230 align:start position:0% experience as a network engineer our<22:30:20.576> shorts<22:30:21.176> opens<22:30:21.896> incorrect<22:30:22.552> termination 22:30:23.230 --> 22:30:23.240 align:start position:0% our shorts opens incorrect termination 22:30:23.240 --> 22:30:24.734 align:start position:0% our shorts opens incorrect termination crosstalk 22:30:24.734 --> 22:30:24.744 align:start position:0% crosstalk 22:30:24.744 --> 22:30:29.270 align:start position:0% crosstalk Emi<22:30:25.744> distance<22:30:26.400> limitations<22:30:27.192> attenuation<22:30:28.280> the 22:30:29.270 --> 22:30:29.280 align:start position:0% Emi distance limitations attenuation the 22:30:29.280 --> 22:30:31.494 align:start position:0% Emi distance limitations attenuation the cable<22:30:29.760> issues 22:30:31.494 --> 22:30:31.504 align:start position:0% cable issues 22:30:31.504 --> 22:30:34.182 align:start position:0% cable issues shorts<22:30:32.336> is<22:30:32.464> basically<22:30:32.824> short<22:30:33.120> for<22:30:33.480> a<22:30:33.960> short 22:30:34.182 --> 22:30:34.192 align:start position:0% shorts is basically short for a short 22:30:34.192 --> 22:30:36.286 align:start position:0% shorts is basically short for a short circuit<22:30:34.744> it<22:30:35.280> allows<22:30:35.576> the<22:30:35.696> current<22:30:35.824> to<22:30:36.120> travel 22:30:36.286 --> 22:30:36.296 align:start position:0% circuit it allows the current to travel 22:30:36.296 --> 22:30:39.774 align:start position:0% circuit it allows the current to travel in<22:30:36.600> a<22:30:36.896> path<22:30:37.800> that<22:30:38.040> wasn't<22:30:38.216> intended<22:30:38.872> and<22:30:39.600> the 22:30:39.774 --> 22:30:39.784 align:start position:0% in a path that wasn't intended and the 22:30:39.784 --> 22:30:42.590 align:start position:0% in a path that wasn't intended and the cable<22:30:40.256> wasn't<22:30:40.496> designed<22:30:40.976> for<22:30:41.160> a<22:30:42.120> couple<22:30:42.240> was 22:30:42.590 --> 22:30:42.600 align:start position:0% cable wasn't designed for a couple was 22:30:42.600 --> 22:30:44.750 align:start position:0% cable wasn't designed for a couple was in<22:30:42.832> the<22:30:42.960> cables<22:30:43.376> are<22:30:43.744> insulated<22:30:44.216> so<22:30:44.512> they 22:30:44.750 --> 22:30:44.760 align:start position:0% in the cables are insulated so they 22:30:44.760 --> 22:30:46.182 align:start position:0% in the cables are insulated so they don't<22:30:44.872> come<22:30:45.176> into<22:30:45.296> contact<22:30:45.536> with<22:30:45.832> each<22:30:46.080> other 22:30:46.182 --> 22:30:46.192 align:start position:0% don't come into contact with each other 22:30:46.192 --> 22:30:47.750 align:start position:0% don't come into contact with each other if 22:30:47.750 --> 22:30:47.760 align:start position:0% if 22:30:47.760 --> 22:30:49.246 align:start position:0% if um there's<22:30:48.056> some<22:30:48.240> sort<22:30:48.424> of<22:30:48.536> issue<22:30:48.832> a<22:30:49.144> lot<22:30:49.192> of 22:30:49.246 --> 22:30:49.256 align:start position:0% um there's some sort of issue a lot of 22:30:49.256 --> 22:30:50.502 align:start position:0% um there's some sort of issue a lot of the<22:30:49.376> time<22:30:49.440> it's<22:30:49.680> because<22:30:49.856> it's<22:30:50.040> frayed 22:30:50.502 --> 22:30:50.512 align:start position:0% the time it's because it's frayed 22:30:50.512 --> 22:30:53.206 align:start position:0% the time it's because it's frayed somebody's<22:30:51.000> bent<22:30:51.240> the<22:30:51.424> cable<22:30:51.656> around<22:30:52.552> a<22:30:52.920> Bend 22:30:53.206 --> 22:30:53.216 align:start position:0% somebody's bent the cable around a Bend 22:30:53.216 --> 22:30:55.846 align:start position:0% somebody's bent the cable around a Bend or<22:30:53.464> just<22:30:53.872> done<22:30:54.176> something<22:30:54.424> with<22:30:54.784> it<22:30:54.960> or<22:30:55.504> folded 22:30:55.846 --> 22:30:55.856 align:start position:0% or just done something with it or folded 22:30:55.856 --> 22:30:58.182 align:start position:0% or just done something with it or folded it<22:30:56.040> too<22:30:56.160> many<22:30:56.336> times<22:30:56.576> and<22:30:56.872> unfolded<22:30:57.424> it<22:30:57.600> then 22:30:58.182 --> 22:30:58.192 align:start position:0% it too many times and unfolded it then 22:30:58.192 --> 22:31:00.414 align:start position:0% it too many times and unfolded it then the<22:30:58.440> cables<22:30:58.800> can<22:30:58.920> touch<22:30:59.104> each<22:30:59.336> other<22:30:59.512> and<22:31:00.296> then 22:31:00.414 --> 22:31:00.424 align:start position:0% the cables can touch each other and then 22:31:00.424 --> 22:31:03.350 align:start position:0% the cables can touch each other and then you've<22:31:00.600> got<22:31:00.720> a<22:31:00.896> short<22:31:01.080> circuit<22:31:02.160> you<22:31:02.872> depended 22:31:03.350 --> 22:31:03.360 align:start position:0% you've got a short circuit you depended 22:31:03.360 --> 22:31:04.542 align:start position:0% you've got a short circuit you depended on<22:31:03.424> how<22:31:03.720> bad<22:31:03.896> it<22:31:04.080> is<22:31:04.192> you'll<22:31:04.440> have 22:31:04.542 --> 22:31:04.552 align:start position:0% on how bad it is you'll have 22:31:04.552 --> 22:31:07.310 align:start position:0% on how bad it is you'll have intermittent<22:31:05.104> connectivity<22:31:05.824> issues<22:31:06.424> you 22:31:07.310 --> 22:31:07.320 align:start position:0% intermittent connectivity issues you 22:31:07.320 --> 22:31:09.646 align:start position:0% intermittent connectivity issues you could<22:31:07.376> use<22:31:07.552> a<22:31:07.800> TDR<22:31:08.400> that<22:31:08.872> will<22:31:09.056> locate<22:31:09.480> the 22:31:09.646 --> 22:31:09.656 align:start position:0% could use a TDR that will locate the 22:31:09.656 --> 22:31:12.646 align:start position:0% could use a TDR that will locate the short<22:31:09.896> in<22:31:10.256> the<22:31:10.496> cable<22:31:11.216> this<22:31:12.176> is<22:31:12.296> one<22:31:12.480> of<22:31:12.600> your 22:31:12.646 --> 22:31:12.656 align:start position:0% short in the cable this is one of your 22:31:12.656 --> 22:31:16.486 align:start position:0% short in the cable this is one of your troubleshooting<22:31:13.376> tools<22:31:13.744> that<22:31:13.856> you<22:31:14.040> could<22:31:14.160> use 22:31:16.486 --> 22:31:16.496 align:start position:0% 22:31:16.496 --> 22:31:18.350 align:start position:0% an<22:31:16.920> open<22:31:17.104> refers<22:31:17.576> to<22:31:17.760> an<22:31:17.872> incomplete 22:31:18.350 --> 22:31:18.360 align:start position:0% an open refers to an incomplete 22:31:18.360 --> 22:31:20.030 align:start position:0% an open refers to an incomplete electrical<22:31:18.832> circuit<22:31:19.256> in<22:31:19.504> which<22:31:19.680> there's<22:31:19.800> no 22:31:20.030 --> 22:31:20.040 align:start position:0% electrical circuit in which there's no 22:31:20.040 --> 22:31:22.606 align:start position:0% electrical circuit in which there's no current<22:31:20.216> if<22:31:21.056> one<22:31:21.296> of<22:31:21.480> the<22:31:21.600> copper<22:31:22.256> wires 22:31:22.606 --> 22:31:22.616 align:start position:0% current if one of the copper wires 22:31:22.616 --> 22:31:24.710 align:start position:0% current if one of the copper wires inside<22:31:22.800> the<22:31:23.104> cable<22:31:23.280> is<22:31:23.512> cut<22:31:23.824> or<22:31:24.120> just<22:31:24.424> broken 22:31:24.710 --> 22:31:24.720 align:start position:0% inside the cable is cut or just broken 22:31:24.720 --> 22:31:27.286 align:start position:0% inside the cable is cut or just broken for<22:31:25.080> some<22:31:25.256> reason<22:31:25.440> then<22:31:26.216> you've<22:31:26.464> got<22:31:26.640> an<22:31:27.176> open 22:31:27.286 --> 22:31:27.296 align:start position:0% for some reason then you've got an open 22:31:27.296 --> 22:31:29.686 align:start position:0% for some reason then you've got an open circuit<22:31:27.960> you<22:31:28.496> would<22:31:28.680> normally<22:31:28.920> then<22:31:29.104> have<22:31:29.400> no 22:31:29.686 --> 22:31:29.696 align:start position:0% circuit you would normally then have no 22:31:29.696 --> 22:31:31.430 align:start position:0% circuit you would normally then have no connectivity 22:31:31.430 --> 22:31:31.440 align:start position:0% connectivity 22:31:31.440 --> 22:31:34.430 align:start position:0% connectivity again<22:31:32.280> you<22:31:32.640> can<22:31:32.760> use<22:31:32.872> a<22:31:33.120> TDR<22:31:33.656> that<22:31:34.080> can<22:31:34.192> be<22:31:34.320> used 22:31:34.430 --> 22:31:34.440 align:start position:0% again you can use a TDR that can be used 22:31:34.440 --> 22:31:37.182 align:start position:0% again you can use a TDR that can be used to<22:31:34.680> locate<22:31:35.104> openings<22:31:35.936> in<22:31:36.120> the<22:31:36.240> cable 22:31:37.182 --> 22:31:37.192 align:start position:0% to locate openings in the cable 22:31:37.192 --> 22:31:39.950 align:start position:0% to locate openings in the cable incorrect<22:31:38.104> termination<22:31:38.656> generally<22:31:39.656> happens 22:31:39.950 --> 22:31:39.960 align:start position:0% incorrect termination generally happens 22:31:39.960 --> 22:31:42.710 align:start position:0% incorrect termination generally happens when<22:31:40.320> you've<22:31:40.616> made<22:31:40.744> your<22:31:40.976> own<22:31:41.160> cables<22:31:41.824> or<22:31:42.536> your 22:31:42.710 --> 22:31:42.720 align:start position:0% when you've made your own cables or your 22:31:42.720 --> 22:31:45.286 align:start position:0% when you've made your own cables or your cable<22:31:43.016> engineer<22:31:43.552> has<22:31:43.800> done<22:31:44.040> it<22:31:44.216> and<22:31:44.400> just<22:31:44.760> made 22:31:45.286 --> 22:31:45.296 align:start position:0% cable engineer has done it and just made 22:31:45.296 --> 22:31:47.270 align:start position:0% cable engineer has done it and just made a<22:31:45.480> mistake<22:31:45.784> or<22:31:45.960> done<22:31:46.144> it<22:31:46.320> too<22:31:46.496> quickly<22:31:46.856> or<22:31:47.104> just 22:31:47.270 --> 22:31:47.280 align:start position:0% a mistake or done it too quickly or just 22:31:47.280 --> 22:31:48.046 align:start position:0% a mistake or done it too quickly or just not 22:31:48.046 --> 22:31:48.056 align:start position:0% not 22:31:48.056 --> 22:31:50.094 align:start position:0% not and<22:31:48.600> been<22:31:48.896> watching<22:31:49.192> what<22:31:49.376> they're<22:31:49.552> doing<22:31:49.744> and 22:31:50.094 --> 22:31:50.104 align:start position:0% and been watching what they're doing and 22:31:50.104 --> 22:31:52.070 align:start position:0% and been watching what they're doing and it's<22:31:50.280> obviously<22:31:50.640> human<22:31:51.000> error<22:31:51.424> then<22:31:51.600> don't 22:31:52.070 --> 22:31:52.080 align:start position:0% it's obviously human error then don't 22:31:52.080 --> 22:31:54.350 align:start position:0% it's obviously human error then don't happen<22:31:52.496> it<22:31:52.744> doesn't<22:31:52.920> happen<22:31:53.104> as<22:31:53.400> much<22:31:53.696> in<22:31:54.360> um 22:31:54.350 --> 22:31:54.360 align:start position:0% happen it doesn't happen as much in um 22:31:54.360 --> 22:31:56.814 align:start position:0% happen it doesn't happen as much in um professionally<22:31:55.016> made<22:31:55.256> cables<22:31:55.856> so<22:31:56.640> you 22:31:56.814 --> 22:31:56.824 align:start position:0% professionally made cables so you 22:31:56.824 --> 22:31:59.030 align:start position:0% professionally made cables so you haven't<22:31:57.000> properly<22:31:57.480> terminated<22:31:58.080> as<22:31:58.680> per<22:31:58.856> the 22:31:59.030 --> 22:31:59.040 align:start position:0% haven't properly terminated as per the 22:31:59.040 --> 22:32:00.230 align:start position:0% haven't properly terminated as per the standards<22:31:59.464> you<22:31:59.512> could<22:31:59.640> have<22:31:59.760> got<22:31:59.872> the<22:32:00.000> wires 22:32:00.230 --> 22:32:00.240 align:start position:0% standards you could have got the wires 22:32:00.240 --> 22:32:05.030 align:start position:0% standards you could have got the wires mixed<22:32:00.600> up<22:32:00.656> or<22:32:01.016> not<22:32:01.336> squash<22:32:02.336> the<22:32:03.056> um<22:32:03.656> the<22:32:04.144> RJ45 22:32:05.030 --> 22:32:05.040 align:start position:0% mixed up or not squash the um the RJ45 22:32:05.040 --> 22:32:07.734 align:start position:0% mixed up or not squash the um the RJ45 connector<22:32:05.640> onto<22:32:05.936> the<22:32:06.056> wires<22:32:06.424> correctly<22:32:06.896> and 22:32:07.734 --> 22:32:07.744 align:start position:0% connector onto the wires correctly and 22:32:07.744 --> 22:32:09.774 align:start position:0% connector onto the wires correctly and it's<22:32:07.856> a<22:32:07.976> bit<22:32:08.104> of<22:32:08.216> an<22:32:08.336> art<22:32:08.464> to<22:32:08.696> it<22:32:08.872> so<22:32:09.480> you<22:32:09.600> could 22:32:09.774 --> 22:32:09.784 align:start position:0% it's a bit of an art to it so you could 22:32:09.784 --> 22:32:11.926 align:start position:0% it's a bit of an art to it so you could have<22:32:09.960> no<22:32:10.376> connection<22:32:10.616> or<22:32:11.280> intermittent 22:32:11.926 --> 22:32:11.936 align:start position:0% have no connection or intermittent 22:32:11.936 --> 22:32:15.286 align:start position:0% have no connection or intermittent connection<22:32:12.296> issues 22:32:15.286 --> 22:32:15.296 align:start position:0% 22:32:15.296 --> 22:32:16.846 align:start position:0% straight<22:32:15.832> through<22:32:16.016> cables<22:32:16.552> should<22:32:16.744> be 22:32:16.846 --> 22:32:16.856 align:start position:0% straight through cables should be 22:32:16.856 --> 22:32:19.990 align:start position:0% straight through cables should be terminated<22:32:17.400> either<22:32:18.360> using 22:32:19.990 --> 22:32:20.000 align:start position:0% terminated either using 22:32:20.000 --> 22:32:23.270 align:start position:0% terminated either using t568<22:32:21.000> a<22:32:21.424> or<22:32:21.720> b 22:32:23.270 --> 22:32:23.280 align:start position:0% t568 a or b 22:32:23.280 --> 22:32:25.966 align:start position:0% t568 a or b crossover<22:32:23.936> cable<22:32:24.360> has<22:32:24.656> got<22:32:24.896> a<22:32:25.144> on<22:32:25.440> one<22:32:25.616> end<22:32:25.744> and 22:32:25.966 --> 22:32:25.976 align:start position:0% crossover cable has got a on one end and 22:32:25.976 --> 22:32:28.734 align:start position:0% crossover cable has got a on one end and B<22:32:26.104> on<22:32:26.280> the<22:32:26.400> other<22:32:26.512> so<22:32:26.824> pins<22:32:27.120> one<22:32:27.440> goes<22:32:28.440> to<22:32:28.496> three 22:32:28.734 --> 22:32:28.744 align:start position:0% B on the other so pins one goes to three 22:32:28.744 --> 22:32:31.734 align:start position:0% B on the other so pins one goes to three and<22:32:28.976> two<22:32:29.104> goes<22:32:29.464> to<22:32:29.512> six<22:32:29.696> on<22:32:29.936> the<22:32:30.056> other<22:32:30.176> end 22:32:31.734 --> 22:32:31.744 align:start position:0% and two goes to six on the other end 22:32:31.744 --> 22:32:34.246 align:start position:0% and two goes to six on the other end use<22:32:32.104> the<22:32:32.336> cable<22:32:32.824> tester<22:32:33.296> to<22:32:33.600> check<22:32:33.896> if<22:32:34.080> your 22:32:34.246 --> 22:32:34.256 align:start position:0% use the cable tester to check if your 22:32:34.256 --> 22:32:36.646 align:start position:0% use the cable tester to check if your Cable's<22:32:34.744> properly<22:32:35.240> terminated<22:32:36.240> and<22:32:36.480> what 22:32:36.646 --> 22:32:36.656 align:start position:0% Cable's properly terminated and what 22:32:36.656 --> 22:32:37.846 align:start position:0% Cable's properly terminated and what type<22:32:36.832> it<22:32:37.080> is 22:32:37.846 --> 22:32:37.856 align:start position:0% type it is 22:32:37.856 --> 22:32:39.710 align:start position:0% type it is crosstalk<22:32:38.400> is<22:32:38.696> when<22:32:38.936> the<22:32:39.120> signal<22:32:39.296> from<22:32:39.480> The 22:32:39.710 --> 22:32:39.720 align:start position:0% crosstalk is when the signal from The 22:32:39.720 --> 22:32:41.206 align:start position:0% crosstalk is when the signal from The Wire<22:32:39.832> interferes<22:32:40.552> with<22:32:40.616> the<22:32:40.744> signal<22:32:40.976> on 22:32:41.206 --> 22:32:41.216 align:start position:0% Wire interferes with the signal on 22:32:41.216 --> 22:32:42.350 align:start position:0% Wire interferes with the signal on another<22:32:41.336> wire 22:32:42.350 --> 22:32:42.360 align:start position:0% another wire 22:32:42.360 --> 22:32:45.110 align:start position:0% another wire less<22:32:42.896> of<22:32:43.080> an<22:32:43.256> issue<22:32:43.504> now<22:32:43.616> with<22:32:43.920> modern 22:32:45.110 --> 22:32:45.120 align:start position:0% less of an issue now with modern 22:32:45.120 --> 22:32:47.454 align:start position:0% less of an issue now with modern um<22:32:45.240> shielded<22:32:46.080> twisted<22:32:46.552> pair 22:32:47.454 --> 22:32:47.464 align:start position:0% um shielded twisted pair 22:32:47.464 --> 22:32:50.326 align:start position:0% um shielded twisted pair uh<22:32:48.176> cables 22:32:50.326 --> 22:32:50.336 align:start position:0% uh cables 22:32:50.336 --> 22:32:53.502 align:start position:0% uh cables you<22:32:51.056> measure<22:32:51.296> with<22:32:51.424> the<22:32:51.600> cable<22:32:51.784> tester<22:32:52.496> or<22:32:52.976> TDR 22:32:53.502 --> 22:32:53.512 align:start position:0% you measure with the cable tester or TDR 22:32:53.512 --> 22:32:56.206 align:start position:0% you measure with the cable tester or TDR again<22:32:53.760> the<22:32:54.656> issues<22:32:54.960> avoided<22:32:55.440> if<22:32:55.616> you<22:32:55.800> buy<22:32:56.040> a 22:32:56.206 --> 22:32:56.216 align:start position:0% again the issues avoided if you buy a 22:32:56.216 --> 22:32:57.886 align:start position:0% again the issues avoided if you buy a professional<22:32:56.696> cable<22:32:57.056> basically<22:32:57.480> because<22:32:57.720> it 22:32:57.886 --> 22:32:57.896 align:start position:0% professional cable basically because it 22:32:57.896 --> 22:32:59.814 align:start position:0% professional cable basically because it will<22:32:58.016> be<22:32:58.144> twisted<22:32:58.496> properly 22:32:59.814 --> 22:32:59.824 align:start position:0% will be twisted properly 22:32:59.824 --> 22:33:02.326 align:start position:0% will be twisted properly two<22:33:00.240> types<22:33:00.600> of<22:33:00.720> crosstalk<22:33:01.080> that<22:33:01.616> you<22:33:01.856> may<22:33:02.104> be 22:33:02.326 --> 22:33:02.336 align:start position:0% two types of crosstalk that you may be 22:33:02.336 --> 22:33:04.966 align:start position:0% two types of crosstalk that you may be asked<22:33:02.696> about<22:33:02.760> in<22:33:03.056> the<22:33:03.176> exam<22:33:03.480> near<22:33:04.192> end<22:33:04.552> and<22:33:04.744> far 22:33:04.966 --> 22:33:04.976 align:start position:0% asked about in the exam near end and far 22:33:04.976 --> 22:33:06.110 align:start position:0% asked about in the exam near end and far end 22:33:06.110 --> 22:33:06.120 align:start position:0% end 22:33:06.120 --> 22:33:08.390 align:start position:0% end and<22:33:06.480> near<22:33:06.720> end<22:33:06.960> is<22:33:07.192> refers<22:33:07.616> to<22:33:07.744> the<22:33:07.976> crosstalk 22:33:08.390 --> 22:33:08.400 align:start position:0% and near end is refers to the crosstalk 22:33:08.400 --> 22:33:10.310 align:start position:0% and near end is refers to the crosstalk that<22:33:08.696> occurs<22:33:09.000> at<22:33:09.120> the<22:33:09.296> terminated<22:33:09.720> end<22:33:10.016> of<22:33:10.192> the 22:33:10.310 --> 22:33:10.320 align:start position:0% that occurs at the terminated end of the 22:33:10.320 --> 22:33:12.230 align:start position:0% that occurs at the terminated end of the cable<22:33:10.552> where<22:33:11.160> the<22:33:11.400> crosstalk<22:33:11.696> has<22:33:12.056> been 22:33:12.230 --> 22:33:12.240 align:start position:0% cable where the crosstalk has been 22:33:12.240 --> 22:33:14.030 align:start position:0% cable where the crosstalk has been measured<22:33:12.720> so<22:33:13.144> this<22:33:13.376> is<22:33:13.504> where<22:33:13.680> you're<22:33:13.800> doing 22:33:14.030 --> 22:33:14.040 align:start position:0% measured so this is where you're doing 22:33:14.040 --> 22:33:15.774 align:start position:0% measured so this is where you're doing the<22:33:14.160> measuring 22:33:15.774 --> 22:33:15.784 align:start position:0% the measuring 22:33:15.784 --> 22:33:17.750 align:start position:0% the measuring occurs<22:33:16.552> near<22:33:16.680> the<22:33:16.856> connectors<22:33:17.280> terminating 22:33:17.750 --> 22:33:17.760 align:start position:0% occurs near the connectors terminating 22:33:17.760 --> 22:33:20.862 align:start position:0% occurs near the connectors terminating the<22:33:18.056> cable<22:33:18.320> far<22:33:19.320> end<22:33:19.552> is 22:33:20.862 --> 22:33:20.872 align:start position:0% the cable far end is 22:33:20.872 --> 22:33:22.966 align:start position:0% the cable far end is um<22:33:20.936> on<22:33:21.656> the<22:33:21.784> far<22:33:21.896> end<22:33:22.080> of<22:33:22.256> the<22:33:22.376> cable<22:33:22.552> from 22:33:22.966 --> 22:33:22.976 align:start position:0% um on the far end of the cable from 22:33:22.976 --> 22:33:25.006 align:start position:0% um on the far end of the cable from where<22:33:23.216> you're<22:33:23.336> doing<22:33:23.576> the<22:33:23.824> measurements 22:33:25.006 --> 22:33:25.016 align:start position:0% where you're doing the measurements 22:33:25.016 --> 22:33:27.110 align:start position:0% where you're doing the measurements occurs<22:33:25.920> near<22:33:26.104> the<22:33:26.280> connectors<22:33:26.640> terminating 22:33:27.110 --> 22:33:27.120 align:start position:0% occurs near the connectors terminating 22:33:27.120 --> 22:33:29.646 align:start position:0% occurs near the connectors terminating the<22:33:27.424> far<22:33:27.536> end<22:33:27.784> of<22:33:27.960> the<22:33:28.080> cable 22:33:29.646 --> 22:33:29.656 align:start position:0% the far end of the cable 22:33:29.656 --> 22:33:31.734 align:start position:0% the far end of the cable electromagnetic<22:33:30.656> efference<22:33:31.192> is<22:33:31.504> normally 22:33:31.734 --> 22:33:31.744 align:start position:0% electromagnetic efference is normally 22:33:31.744 --> 22:33:34.606 align:start position:0% electromagnetic efference is normally when<22:33:32.104> you've<22:33:32.512> laid<22:33:32.760> the<22:33:32.936> cable<22:33:33.176> yourself<22:33:33.616> and 22:33:34.606 --> 22:33:34.616 align:start position:0% when you've laid the cable yourself and 22:33:34.616 --> 22:33:35.862 align:start position:0% when you've laid the cable yourself and it's<22:33:34.800> gone 22:33:35.862 --> 22:33:35.872 align:start position:0% it's gone 22:33:35.872 --> 22:33:39.230 align:start position:0% it's gone through<22:33:36.424> or<22:33:36.896> near<22:33:37.192> some<22:33:37.856> device<22:33:38.160> that<22:33:38.512> emits<22:33:39.120> a 22:33:39.230 --> 22:33:39.240 align:start position:0% through or near some device that emits a 22:33:39.240 --> 22:33:41.990 align:start position:0% through or near some device that emits a strong<22:33:39.600> error<22:33:40.496> signal 22:33:41.990 --> 22:33:42.000 align:start position:0% strong error signal 22:33:42.000 --> 22:33:45.046 align:start position:0% strong error signal an<22:33:42.896> emo<22:33:43.376> signal<22:33:43.744> also<22:33:44.576> called<22:33:44.760> radio 22:33:45.046 --> 22:33:45.056 align:start position:0% an emo signal also called radio 22:33:45.056 --> 22:33:47.206 align:start position:0% an emo signal also called radio frequency<22:33:45.656> interference 22:33:47.206 --> 22:33:47.216 align:start position:0% frequency interference 22:33:47.216 --> 22:33:49.606 align:start position:0% frequency interference generate<22:33:47.936> generated 22:33:49.606 --> 22:33:49.616 align:start position:0% generate generated 22:33:49.616 --> 22:33:50.502 align:start position:0% generate generated um 22:33:50.502 --> 22:33:50.512 align:start position:0% um 22:33:50.512 --> 22:33:53.686 align:start position:0% um by<22:33:51.000> fluorescent<22:33:51.600> lights<22:33:51.976> electric<22:33:52.976> motors 22:33:53.686 --> 22:33:53.696 align:start position:0% by fluorescent lights electric motors 22:33:53.696 --> 22:33:56.094 align:start position:0% by fluorescent lights electric motors dynamos<22:33:54.480> things<22:33:54.896> like<22:33:55.192> that<22:33:55.440> so<22:33:55.856> it<22:33:55.976> could 22:33:56.094 --> 22:33:56.104 align:start position:0% dynamos things like that so it could 22:33:56.104 --> 22:33:59.046 align:start position:0% dynamos things like that so it could happen<22:33:56.280> in<22:33:56.576> a<22:33:56.760> workshop<22:33:57.320> or<22:33:58.320> when<22:33:58.552> you<22:33:58.744> haven't 22:33:59.046 --> 22:33:59.056 align:start position:0% happen in a workshop or when you haven't 22:33:59.056 --> 22:34:01.846 align:start position:0% happen in a workshop or when you haven't properly<22:34:00.056> housed<22:34:00.896> your<22:34:01.016> cable<22:34:01.256> or<22:34:01.552> it's<22:34:01.744> not 22:34:01.846 --> 22:34:01.856 align:start position:0% properly housed your cable or it's not 22:34:01.856 --> 22:34:03.470 align:start position:0% properly housed your cable or it's not running<22:34:02.040> under<22:34:02.336> the<22:34:02.576> floor<22:34:02.760> and<22:34:03.360> you're 22:34:03.470 --> 22:34:03.480 align:start position:0% running under the floor and you're 22:34:03.480 --> 22:34:04.790 align:start position:0% running under the floor and you're running<22:34:03.600> it<22:34:03.832> through<22:34:03.960> the<22:34:04.144> ceiling<22:34:04.496> and<22:34:04.616> it's 22:34:04.790 --> 22:34:04.800 align:start position:0% running it through the ceiling and it's 22:34:04.800 --> 22:34:06.590 align:start position:0% running it through the ceiling and it's going<22:34:04.976> through<22:34:05.216> the 22:34:06.590 --> 22:34:06.600 align:start position:0% going through the 22:34:06.600 --> 22:34:07.630 align:start position:0% going through the um 22:34:07.630 --> 22:34:07.640 align:start position:0% um 22:34:07.640 --> 22:34:11.630 align:start position:0% um fluorescent<22:34:08.640> lights 22:34:11.630 --> 22:34:11.640 align:start position:0% 22:34:11.640 --> 22:34:14.270 align:start position:0% data<22:34:12.360> transmission<22:34:12.480> of<22:34:12.896> copper<22:34:13.192> cables<22:34:13.552> is<22:34:14.216> um 22:34:14.270 --> 22:34:14.280 align:start position:0% data transmission of copper cables is um 22:34:14.280 --> 22:34:16.542 align:start position:0% data transmission of copper cables is um obviously<22:34:14.640> disrupted<22:34:15.600> when<22:34:15.784> it's<22:34:16.016> exposed 22:34:16.542 --> 22:34:16.552 align:start position:0% obviously disrupted when it's exposed 22:34:16.552 --> 22:34:18.526 align:start position:0% obviously disrupted when it's exposed and<22:34:17.104> it<22:34:17.216> could<22:34:17.336> be<22:34:17.464> intermittent<22:34:18.056> it<22:34:18.296> could<22:34:18.424> be 22:34:18.526 --> 22:34:18.536 align:start position:0% and it could be intermittent it could be 22:34:18.536 --> 22:34:20.814 align:start position:0% and it could be intermittent it could be fine<22:34:18.720> during<22:34:19.080> the<22:34:19.376> day<22:34:19.552> and<22:34:20.160> then<22:34:20.280> later<22:34:20.464> on<22:34:20.640> in 22:34:20.814 --> 22:34:20.824 align:start position:0% fine during the day and then later on in 22:34:20.824 --> 22:34:22.366 align:start position:0% fine during the day and then later on in the<22:34:20.936> evening<22:34:21.000> when<22:34:21.296> somebody<22:34:21.536> starts<22:34:22.016> turning 22:34:22.366 --> 22:34:22.376 align:start position:0% the evening when somebody starts turning 22:34:22.376 --> 22:34:25.790 align:start position:0% the evening when somebody starts turning the<22:34:22.552> lights<22:34:22.680> on<22:34:22.976> it<22:34:23.464> could<22:34:23.576> be<22:34:23.696> affected 22:34:25.790 --> 22:34:25.800 align:start position:0% the lights on it could be affected 22:34:25.800 --> 22:34:27.710 align:start position:0% the lights on it could be affected avoid<22:34:26.400> if<22:34:26.576> you<22:34:26.696> separate<22:34:27.000> the<22:34:27.176> power<22:34:27.296> source 22:34:27.710 --> 22:34:27.720 align:start position:0% avoid if you separate the power source 22:34:27.720 --> 22:34:29.686 align:start position:0% avoid if you separate the power source from<22:34:27.832> the<22:34:28.016> cables<22:34:28.440> or<22:34:28.680> by<22:34:28.856> using<22:34:29.160> shielded 22:34:29.686 --> 22:34:29.696 align:start position:0% from the cables or by using shielded 22:34:29.696 --> 22:34:30.774 align:start position:0% from the cables or by using shielded cabling 22:34:30.774 --> 22:34:30.784 align:start position:0% cabling 22:34:30.784 --> 22:34:32.566 align:start position:0% cabling you<22:34:31.320> may<22:34:31.440> have<22:34:31.552> to<22:34:31.680> buy<22:34:31.800> a<22:34:31.976> special<22:34:32.104> type<22:34:32.400> of 22:34:32.566 --> 22:34:32.576 align:start position:0% you may have to buy a special type of 22:34:32.576 --> 22:34:34.734 align:start position:0% you may have to buy a special type of cabling<22:34:32.936> if<22:34:33.240> you're<22:34:33.480> running<22:34:34.016> your<22:34:34.320> cables 22:34:34.734 --> 22:34:34.744 align:start position:0% cabling if you're running your cables 22:34:34.744 --> 22:34:36.230 align:start position:0% cabling if you're running your cables through<22:34:34.920> devices<22:34:35.400> with<22:34:35.760> a<22:34:35.872> lot<22:34:35.936> of<22:34:36.056> very 22:34:36.230 --> 22:34:36.240 align:start position:0% through devices with a lot of very 22:34:36.240 --> 22:34:37.734 align:start position:0% through devices with a lot of very powerful 22:34:37.734 --> 22:34:37.744 align:start position:0% powerful 22:34:37.744 --> 22:34:40.006 align:start position:0% powerful um electrical<22:34:38.336> signals 22:34:40.006 --> 22:34:40.016 align:start position:0% um electrical signals 22:34:40.016 --> 22:34:41.990 align:start position:0% um electrical signals obviously<22:34:40.744> there's<22:34:40.976> distance<22:34:41.216> limitations 22:34:41.990 --> 22:34:42.000 align:start position:0% obviously there's distance limitations 22:34:42.000 --> 22:34:44.814 align:start position:0% obviously there's distance limitations per<22:34:42.784> cable<22:34:43.192> lost<22:34:43.976> the<22:34:44.216> signal<22:34:44.464> when<22:34:44.640> it 22:34:44.814 --> 22:34:44.824 align:start position:0% per cable lost the signal when it 22:34:44.824 --> 22:34:46.486 align:start position:0% per cable lost the signal when it travels<22:34:45.056> over<22:34:45.240> a<22:34:45.480> long<22:34:45.600> distance<22:34:45.832> you<22:34:46.376> could 22:34:46.486 --> 22:34:46.496 align:start position:0% travels over a long distance you could 22:34:46.496 --> 22:34:48.470 align:start position:0% travels over a long distance you could then<22:34:46.744> have<22:34:47.160> connectivity<22:34:47.760> issues<22:34:48.176> so<22:34:48.296> if 22:34:48.470 --> 22:34:48.480 align:start position:0% then have connectivity issues so if 22:34:48.480 --> 22:34:50.286 align:start position:0% then have connectivity issues so if you're<22:34:48.600> running<22:34:48.784> your<22:34:49.016> cable<22:34:49.256> over 22:34:50.286 --> 22:34:50.296 align:start position:0% you're running your cable over 22:34:50.296 --> 22:34:53.390 align:start position:0% you're running your cable over 120<22:34:51.296> meters<22:34:51.600> when<22:34:51.832> it's<22:34:52.016> recommended<22:34:52.616> 110 22:34:53.390 --> 22:34:53.400 align:start position:0% 120 meters when it's recommended 110 22:34:53.400 --> 22:34:57.590 align:start position:0% 120 meters when it's recommended 110 then<22:34:54.000> you<22:34:54.176> may<22:34:54.296> well<22:34:54.480> have<22:34:54.720> issues 22:34:57.590 --> 22:34:57.600 align:start position:0% 22:34:57.600 --> 22:35:00.646 align:start position:0% attenuation<22:34:58.552> or<22:34:59.104> DB<22:34:59.512> loss<22:34:59.872> refers<22:35:00.240> to<22:35:00.360> a<22:35:00.480> loss 22:35:00.646 --> 22:35:00.656 align:start position:0% attenuation or DB loss refers to a loss 22:35:00.656 --> 22:35:02.750 align:start position:0% attenuation or DB loss refers to a loss of<22:35:00.720> signal<22:35:01.080> strength<22:35:01.504> the<22:35:02.104> signal<22:35:02.464> strength 22:35:02.750 --> 22:35:02.760 align:start position:0% of signal strength the signal strength 22:35:02.760 --> 22:35:04.846 align:start position:0% of signal strength the signal strength is<22:35:02.872> measured<22:35:03.296> in<22:35:03.600> decibels 22:35:04.846 --> 22:35:04.856 align:start position:0% is measured in decibels 22:35:04.856 --> 22:35:07.182 align:start position:0% is measured in decibels uses<22:35:05.512> experience<22:35:06.000> degradation<22:35:06.656> in<22:35:06.960> network 22:35:07.182 --> 22:35:07.192 align:start position:0% uses experience degradation in network 22:35:07.192 --> 22:35:10.486 align:start position:0% uses experience degradation in network performance<22:35:07.936> you<22:35:08.936> can<22:35:09.000> avoid<22:35:09.360> it<22:35:09.536> by 22:35:10.486 --> 22:35:10.496 align:start position:0% performance you can avoid it by 22:35:10.496 --> 22:35:13.070 align:start position:0% performance you can avoid it by um<22:35:10.976> using<22:35:11.760> cable<22:35:11.872> runs<22:35:12.360> within<22:35:12.600> the<22:35:12.720> maximum 22:35:13.070 --> 22:35:13.080 align:start position:0% um using cable runs within the maximum 22:35:13.080 --> 22:35:15.646 align:start position:0% um using cable runs within the maximum supported<22:35:13.616> distance<22:35:14.176> using<22:35:15.176> a<22:35:15.360> signal 22:35:15.646 --> 22:35:15.656 align:start position:0% supported distance using a signal 22:35:15.656 --> 22:35:17.862 align:start position:0% supported distance using a signal booster<22:35:16.144> you<22:35:16.976> probably<22:35:17.104> need<22:35:17.336> specialized 22:35:17.862 --> 22:35:17.872 align:start position:0% booster you probably need specialized 22:35:17.872 --> 22:35:19.734 align:start position:0% booster you probably need specialized advice<22:35:18.176> for<22:35:18.424> this<22:35:18.536> to<22:35:18.720> be<22:35:18.832> honest<22:35:19.080> if<22:35:19.504> you're 22:35:19.734 --> 22:35:19.744 align:start position:0% advice for this to be honest if you're 22:35:19.744 --> 22:35:22.246 align:start position:0% advice for this to be honest if you're installing<22:35:20.696> in<22:35:21.000> a<22:35:21.480> commercial<22:35:21.656> premises 22:35:22.246 --> 22:35:22.256 align:start position:0% installing in a commercial premises 22:35:22.256 --> 22:35:25.846 align:start position:0% installing in a commercial premises remove<22:35:23.216> broken<22:35:23.640> or<22:35:24.000> damaged<22:35:24.360> cables 22:35:25.846 --> 22:35:25.856 align:start position:0% remove broken or damaged cables 22:35:25.856 --> 22:35:28.670 align:start position:0% remove broken or damaged cables and<22:35:26.216> miscellaneous<22:35:27.000> of<22:35:27.240> the<22:35:27.424> problems<22:35:27.896> uh 22:35:28.670 --> 22:35:28.680 align:start position:0% and miscellaneous of the problems uh 22:35:28.680 --> 22:35:30.414 align:start position:0% and miscellaneous of the problems uh verify<22:35:29.400> the<22:35:29.464> cables<22:35:29.872> are<22:35:30.000> present<22:35:30.240> and 22:35:30.414 --> 22:35:30.424 align:start position:0% verify the cables are present and 22:35:30.424 --> 22:35:32.390 align:start position:0% verify the cables are present and plugged<22:35:30.784> in<22:35:30.896> yes<22:35:31.320> I've<22:35:31.744> been<22:35:32.104> asked<22:35:32.280> to 22:35:32.390 --> 22:35:32.400 align:start position:0% plugged in yes I've been asked to 22:35:32.400 --> 22:35:34.990 align:start position:0% plugged in yes I've been asked to troubleshoot<22:35:32.936> devices<22:35:33.440> when<22:35:34.440> somebody 22:35:34.990 --> 22:35:35.000 align:start position:0% troubleshoot devices when somebody 22:35:35.000 --> 22:35:37.846 align:start position:0% troubleshoot devices when somebody hasn't<22:35:36.000> actually<22:35:36.656> put<22:35:36.960> the<22:35:37.080> cable<22:35:37.320> in<22:35:37.552> yet<22:35:37.680> it 22:35:37.846 --> 22:35:37.856 align:start position:0% hasn't actually put the cable in yet it 22:35:37.856 --> 22:35:40.246 align:start position:0% hasn't actually put the cable in yet it hasn't<22:35:38.104> been<22:35:38.216> installed<22:35:38.696> at<22:35:39.296> all<22:35:39.480> or 22:35:40.246 --> 22:35:40.256 align:start position:0% hasn't been installed at all or 22:35:40.256 --> 22:35:41.926 align:start position:0% hasn't been installed at all or somebody's<22:35:40.744> removed<22:35:41.104> the<22:35:41.216> cable<22:35:41.400> for<22:35:41.760> some 22:35:41.926 --> 22:35:41.936 align:start position:0% somebody's removed the cable for some 22:35:41.936 --> 22:35:43.070 align:start position:0% somebody's removed the cable for some reason<22:35:42.120> because<22:35:42.424> they<22:35:42.600> want<22:35:42.720> to<22:35:42.832> use<22:35:42.960> it 22:35:43.070 --> 22:35:43.080 align:start position:0% reason because they want to use it 22:35:43.080 --> 22:35:45.470 align:start position:0% reason because they want to use it somewhere<22:35:43.440> else<22:35:43.640> and<22:35:44.640> not<22:35:44.872> realized<22:35:45.296> that 22:35:45.470 --> 22:35:45.480 align:start position:0% somewhere else and not realized that 22:35:45.480 --> 22:35:48.166 align:start position:0% somewhere else and not realized that that<22:35:45.656> is<22:35:45.832> connecting<22:35:46.376> to<22:35:46.800> an<22:35:47.160> end<22:35:47.280> user<22:35:47.696> or<22:35:47.936> a 22:35:48.166 --> 22:35:48.176 align:start position:0% that is connecting to an end user or a 22:35:48.176 --> 22:35:49.070 align:start position:0% that is connecting to an end user or a server 22:35:49.070 --> 22:35:49.080 align:start position:0% server 22:35:49.080 --> 22:35:50.926 align:start position:0% server or<22:35:49.616> some<22:35:49.856> of<22:35:49.976> the<22:35:50.104> device 22:35:50.926 --> 22:35:50.936 align:start position:0% or some of the device 22:35:50.936 --> 22:35:53.030 align:start position:0% or some of the device make<22:35:51.424> sure<22:35:51.536> the<22:35:51.720> network<22:35:51.896> adapter<22:35:52.376> is<22:35:52.552> enabled 22:35:53.030 --> 22:35:53.040 align:start position:0% make sure the network adapter is enabled 22:35:53.040 --> 22:35:55.502 align:start position:0% make sure the network adapter is enabled and<22:35:53.280> it<22:35:53.464> has<22:35:53.576> a<22:35:53.696> valid<22:35:53.936> addressing<22:35:54.480> sometimes 22:35:55.502 --> 22:35:55.512 align:start position:0% and it has a valid addressing sometimes 22:35:55.512 --> 22:35:59.150 align:start position:0% and it has a valid addressing sometimes devices<22:35:56.512> have<22:35:56.936> been<22:35:57.120> up<22:35:57.360> for<22:35:57.832> years 22:35:59.150 --> 22:35:59.160 align:start position:0% devices have been up for years 22:35:59.160 --> 22:36:00.822 align:start position:0% devices have been up for years and 22:36:00.822 --> 22:36:00.832 align:start position:0% and 22:36:00.832 --> 22:36:03.350 align:start position:0% and um<22:36:00.896> millions<22:36:01.616> of<22:36:01.800> packets<22:36:02.160> have<22:36:02.400> been<22:36:02.872> passed 22:36:03.350 --> 22:36:03.360 align:start position:0% um millions of packets have been passed 22:36:03.360 --> 22:36:05.814 align:start position:0% um millions of packets have been passed in<22:36:03.784> in<22:36:03.960> and<22:36:04.192> out<22:36:04.320> and<22:36:05.160> it<22:36:05.336> just<22:36:05.512> needs 22:36:05.814 --> 22:36:05.824 align:start position:0% in in and out and it just needs 22:36:05.824 --> 22:36:08.206 align:start position:0% in in and out and it just needs resetting<22:36:06.480> or<22:36:06.720> rebooting<22:36:07.320> or<22:36:07.920> the<22:36:08.104> address 22:36:08.206 --> 22:36:08.216 align:start position:0% resetting or rebooting or the address 22:36:08.216 --> 22:36:11.150 align:start position:0% resetting or rebooting or the address needs<22:36:08.824> and<22:36:09.120> refreshing<22:36:09.832> on<22:36:10.192> it<22:36:10.320> it<22:36:10.920> just 22:36:11.150 --> 22:36:11.160 align:start position:0% needs and refreshing on it it just 22:36:11.160 --> 22:36:14.094 align:start position:0% needs and refreshing on it it just happens<22:36:11.400> sometimes<22:36:12.120> every<22:36:12.424> period<22:36:12.896> of<22:36:13.016> time 22:36:14.094 --> 22:36:14.104 align:start position:0% happens sometimes every period of time 22:36:14.104 --> 22:36:16.366 align:start position:0% happens sometimes every period of time make<22:36:14.576> sure<22:36:14.760> disabled<22:36:15.296> ports<22:36:15.656> are<22:36:15.784> enabled<22:36:16.192> for 22:36:16.366 --> 22:36:16.376 align:start position:0% make sure disabled ports are enabled for 22:36:16.376 --> 22:36:18.110 align:start position:0% make sure disabled ports are enabled for connectivity<22:36:16.920> sometimes<22:36:17.512> ports<22:36:18.000> are 22:36:18.110 --> 22:36:18.120 align:start position:0% connectivity sometimes ports are 22:36:18.120 --> 22:36:20.862 align:start position:0% connectivity sometimes ports are disabled<22:36:18.600> for<22:36:18.784> security<22:36:19.160> and<22:36:20.160> you<22:36:20.400> could<22:36:20.464> plug 22:36:20.862 --> 22:36:20.872 align:start position:0% disabled for security and you could plug 22:36:20.872 --> 22:36:24.414 align:start position:0% disabled for security and you could plug in<22:36:21.120> a<22:36:22.080> new<22:36:22.376> user<22:36:22.800> into<22:36:23.040> a<22:36:23.400> certain<22:36:23.576> port<22:36:24.056> on<22:36:24.296> a 22:36:24.414 --> 22:36:24.424 align:start position:0% in a new user into a certain port on a 22:36:24.424 --> 22:36:26.390 align:start position:0% in a new user into a certain port on a switch<22:36:24.600> for<22:36:24.896> example<22:36:25.192> but<22:36:25.800> that<22:36:25.976> Port<22:36:26.160> has 22:36:26.390 --> 22:36:26.400 align:start position:0% switch for example but that Port has 22:36:26.400 --> 22:36:28.910 align:start position:0% switch for example but that Port has been<22:36:26.576> disabled 22:36:28.910 --> 22:36:28.920 align:start position:0% been disabled 22:36:28.920 --> 22:36:31.542 align:start position:0% been disabled you<22:36:29.464> can<22:36:29.576> have<22:36:29.696> bad<22:36:29.936> cables<22:36:30.536> again<22:36:31.016> sometimes 22:36:31.542 --> 22:36:31.552 align:start position:0% you can have bad cables again sometimes 22:36:31.552 --> 22:36:34.366 align:start position:0% you can have bad cables again sometimes we<22:36:31.800> bend<22:36:32.104> them<22:36:32.400> or<22:36:33.176> just<22:36:33.480> over<22:36:33.784> time<22:36:34.080> for 22:36:34.366 --> 22:36:34.376 align:start position:0% we bend them or just over time for 22:36:34.376 --> 22:36:38.454 align:start position:0% we bend them or just over time for whatever<22:36:34.616> reason<22:36:35.040> the<22:36:35.872> cable<22:36:36.120> goes<22:36:36.536> bad 22:36:38.454 --> 22:36:38.464 align:start position:0% whatever reason the cable goes bad 22:36:38.464 --> 22:36:40.486 align:start position:0% whatever reason the cable goes bad misconfigured<22:36:39.424> switch<22:36:39.656> Port<22:36:39.960> it<22:36:40.256> could<22:36:40.376> be 22:36:40.486 --> 22:36:40.496 align:start position:0% misconfigured switch Port it could be 22:36:40.496 --> 22:36:41.686 align:start position:0% misconfigured switch Port it could be the<22:36:40.744> wrong 22:36:41.686 --> 22:36:41.696 align:start position:0% the wrong 22:36:41.696 --> 22:36:43.846 align:start position:0% the wrong um duplex<22:36:42.176> setting<22:36:42.656> or<22:36:42.896> speed<22:36:43.144> setting<22:36:43.616> or 22:36:43.846 --> 22:36:43.856 align:start position:0% um duplex setting or speed setting or 22:36:43.856 --> 22:36:46.430 align:start position:0% um duplex setting or speed setting or something<22:36:44.104> else<22:36:44.400> on<22:36:44.696> there<22:36:44.872> and<22:36:45.784> it<22:36:46.016> may<22:36:46.256> not 22:36:46.430 --> 22:36:46.440 align:start position:0% something else on there and it may not 22:36:46.440 --> 22:36:47.414 align:start position:0% something else on there and it may not work 22:36:47.414 --> 22:36:47.424 align:start position:0% work 22:36:47.424 --> 22:36:50.502 align:start position:0% work misconfigured<22:36:48.424> network<22:36:48.832> card<22:36:49.256> or<22:36:49.744> a<22:36:50.160> network 22:36:50.502 --> 22:36:50.512 align:start position:0% misconfigured network card or a network 22:36:50.512 --> 22:36:52.966 align:start position:0% misconfigured network card or a network card<22:36:50.824> that's<22:36:51.056> failing<22:36:51.536> or<22:36:51.784> failed 22:36:52.966 --> 22:36:52.976 align:start position:0% card that's failing or failed 22:36:52.976 --> 22:36:54.590 align:start position:0% card that's failing or failed software<22:36:53.640> drivers<22:36:54.056> I've<22:36:54.240> mentioned 22:36:54.590 --> 22:36:54.600 align:start position:0% software drivers I've mentioned 22:36:54.600 --> 22:36:56.990 align:start position:0% software drivers I've mentioned elsewhere<22:36:55.080> that<22:36:55.616> can<22:36:55.800> cause<22:36:56.040> huge<22:36:56.512> problems 22:36:56.990 --> 22:36:57.000 align:start position:0% elsewhere that can cause huge problems 22:36:57.000 --> 22:36:58.862 align:start position:0% elsewhere that can cause huge problems and<22:36:57.536> it's<22:36:57.656> not<22:36:57.784> a<22:36:57.960> problem<22:36:58.080> you<22:36:58.376> can<22:36:58.552> actually 22:36:58.862 --> 22:36:58.872 align:start position:0% and it's not a problem you can actually 22:36:58.872 --> 22:37:01.246 align:start position:0% and it's not a problem you can actually easily<22:36:59.872> see<22:37:00.056> until<22:37:00.360> you<22:37:00.600> start<22:37:00.784> doing<22:37:01.016> a<22:37:01.144> bit 22:37:01.246 --> 22:37:01.256 align:start position:0% easily see until you start doing a bit 22:37:01.256 --> 22:37:04.070 align:start position:0% easily see until you start doing a bit more<22:37:01.376> research 22:37:04.070 --> 22:37:04.080 align:start position:0% 22:37:04.080 --> 22:37:06.470 align:start position:0% all<22:37:04.616> right<22:37:04.744> so<22:37:04.856> we've<22:37:05.104> covered<22:37:05.464> shorts<22:37:05.872> opens 22:37:06.470 --> 22:37:06.480 align:start position:0% all right so we've covered shorts opens 22:37:06.480 --> 22:37:10.486 align:start position:0% all right so we've covered shorts opens termination<22:37:07.576> crosstalk<22:37:08.600> Emi<22:37:09.600> distance 22:37:10.486 --> 22:37:10.496 align:start position:0% termination crosstalk Emi distance 22:37:10.496 --> 22:37:13.310 align:start position:0% termination crosstalk Emi distance attenuation<22:37:11.336> and<22:37:12.120> other<22:37:12.240> problems 22:37:13.310 --> 22:37:13.320 align:start position:0% attenuation and other problems 22:37:13.320 --> 22:37:20.060 align:start position:0% attenuation and other problems that's<22:37:13.744> all<22:37:13.920> for<22:37:14.104> now<22:37:14.216> thanks<22:37:14.512> for<22:37:14.640> watching 22:37:20.060 --> 22:37:20.070 align:start position:0% 22:37:20.070 --> 22:37:36.046 align:start position:0% [Music] 22:37:36.046 --> 22:37:36.056 align:start position:0% 22:37:36.056 --> 22:37:38.862 align:start position:0% welcome<22:37:36.536> to<22:37:36.832> module<22:37:37.192> 19<22:37:37.376> lesson<22:37:38.040> 3<22:37:38.216> common 22:37:38.862 --> 22:37:38.872 align:start position:0% welcome to module 19 lesson 3 common 22:37:38.872 --> 22:37:42.886 align:start position:0% welcome to module 19 lesson 3 common fiber<22:37:39.656> cable<22:37:40.016> issues 22:37:42.886 --> 22:37:42.896 align:start position:0% 22:37:42.896 --> 22:37:45.350 align:start position:0% so<22:37:43.504> look<22:37:43.800> it's<22:37:44.040> troubleshooting<22:37:44.936> uh 22:37:45.350 --> 22:37:45.360 align:start position:0% so look it's troubleshooting uh 22:37:45.360 --> 22:37:47.454 align:start position:0% so look it's troubleshooting uh supported<22:37:45.784> distances<22:37:46.376> categories<22:37:47.216> of 22:37:47.454 --> 22:37:47.464 align:start position:0% supported distances categories of 22:37:47.464 --> 22:37:51.110 align:start position:0% supported distances categories of multi-mode<22:37:48.000> fiber<22:37:48.600> the<22:37:49.144> bend<22:37:49.376> radius 22:37:51.110 --> 22:37:51.120 align:start position:0% multi-mode fiber the bend radius 22:37:51.120 --> 22:37:53.206 align:start position:0% multi-mode fiber the bend radius dirty<22:37:51.896> connectors<22:37:52.376> I<22:37:52.744> think<22:37:52.856> you<22:37:52.976> can<22:37:53.104> guess 22:37:53.206 --> 22:37:53.216 align:start position:0% dirty connectors I think you can guess 22:37:53.216 --> 22:37:56.686 align:start position:0% dirty connectors I think you can guess what<22:37:53.400> that<22:37:53.576> one's<22:37:54.056> about<22:37:54.680> attenuation<22:37:55.696> a 22:37:56.686 --> 22:37:56.696 align:start position:0% what that one's about attenuation a 22:37:56.696 --> 22:38:00.230 align:start position:0% what that one's about attenuation a wavelength<22:37:57.240> mismatch<22:37:57.832> fiber<22:37:58.440> type<22:37:58.616> mismatch 22:38:00.230 --> 22:38:00.240 align:start position:0% wavelength mismatch fiber type mismatch 22:38:00.240 --> 22:38:03.710 align:start position:0% wavelength mismatch fiber type mismatch so<22:38:01.016> the<22:38:01.800> bottom<22:38:02.040> line<22:38:02.216> with<22:38:02.464> fiber<22:38:02.872> cables<22:38:03.424> is 22:38:03.710 --> 22:38:03.720 align:start position:0% so the bottom line with fiber cables is 22:38:03.720 --> 22:38:06.110 align:start position:0% so the bottom line with fiber cables is uh<22:38:04.256> if<22:38:04.496> it's<22:38:04.616> faulty<22:38:05.104> it<22:38:05.464> can't<22:38:05.640> transport 22:38:06.110 --> 22:38:06.120 align:start position:0% uh if it's faulty it can't transport 22:38:06.120 --> 22:38:09.166 align:start position:0% uh if it's faulty it can't transport data<22:38:06.656> it<22:38:06.784> tends<22:38:07.016> to<22:38:07.144> be<22:38:07.256> either<22:38:07.512> a<22:38:08.512> working<22:38:08.760> or 22:38:09.166 --> 22:38:09.176 align:start position:0% data it tends to be either a working or 22:38:09.176 --> 22:38:11.094 align:start position:0% data it tends to be either a working or not<22:38:09.360> working<22:38:09.600> situation<22:38:10.440> whereas<22:38:10.920> with 22:38:11.094 --> 22:38:11.104 align:start position:0% not working situation whereas with 22:38:11.104 --> 22:38:13.734 align:start position:0% not working situation whereas with copper<22:38:11.512> you<22:38:12.424> may<22:38:12.536> well<22:38:12.720> have<22:38:13.016> a<22:38:13.256> period<22:38:13.552> of 22:38:13.734 --> 22:38:13.744 align:start position:0% copper you may well have a period of 22:38:13.744 --> 22:38:15.710 align:start position:0% copper you may well have a period of time<22:38:13.920> where<22:38:14.336> the<22:38:14.512> the<22:38:14.696> performance<22:38:15.424> just 22:38:15.710 --> 22:38:15.720 align:start position:0% time where the the performance just 22:38:15.720 --> 22:38:18.710 align:start position:0% time where the the performance just deteriorates<22:38:16.512> when<22:38:17.512> you<22:38:17.640> get<22:38:17.824> in<22:38:17.936> packet<22:38:18.360> loss 22:38:18.710 --> 22:38:18.720 align:start position:0% deteriorates when you get in packet loss 22:38:18.720 --> 22:38:22.310 align:start position:0% deteriorates when you get in packet loss or<22:38:18.896> intermittent<22:38:20.040> um<22:38:20.104> connectivity<22:38:21.080> and<22:38:22.080> you 22:38:22.310 --> 22:38:22.320 align:start position:0% or intermittent um connectivity and you 22:38:22.320 --> 22:38:23.990 align:start position:0% or intermittent um connectivity and you normally<22:38:22.616> easily<22:38:23.104> troubleshoot<22:38:23.640> that<22:38:23.760> by 22:38:23.990 --> 22:38:24.000 align:start position:0% normally easily troubleshoot that by 22:38:24.000 --> 22:38:26.150 align:start position:0% normally easily troubleshoot that by just<22:38:24.176> swapping<22:38:24.536> the<22:38:24.656> cable<22:38:24.832> out<22:38:25.080> if<22:38:25.800> it<22:38:26.040> all 22:38:26.150 --> 22:38:26.160 align:start position:0% just swapping the cable out if it all 22:38:26.160 --> 22:38:27.646 align:start position:0% just swapping the cable out if it all works<22:38:26.464> then<22:38:26.640> it<22:38:26.824> points<22:38:27.056> to<22:38:27.176> the<22:38:27.296> fact<22:38:27.424> that 22:38:27.646 --> 22:38:27.656 align:start position:0% works then it points to the fact that 22:38:27.656 --> 22:38:29.630 align:start position:0% works then it points to the fact that the<22:38:27.784> cable<22:38:27.960> was<22:38:28.256> faulty<22:38:28.744> and<22:38:29.280> they're<22:38:29.464> so 22:38:29.630 --> 22:38:29.640 align:start position:0% the cable was faulty and they're so 22:38:29.640 --> 22:38:31.734 align:start position:0% the cable was faulty and they're so cheap<22:38:29.824> you<22:38:30.000> just<22:38:30.240> throw<22:38:30.360> them<22:38:30.600> away 22:38:31.734 --> 22:38:31.744 align:start position:0% cheap you just throw them away 22:38:31.744 --> 22:38:34.790 align:start position:0% cheap you just throw them away obviously<22:38:33.056> um<22:38:33.120> fiber<22:38:33.832> cables<22:38:34.192> are<22:38:34.376> not<22:38:34.552> so 22:38:34.790 --> 22:38:34.800 align:start position:0% obviously um fiber cables are not so 22:38:34.800 --> 22:38:35.750 align:start position:0% obviously um fiber cables are not so cheap 22:38:35.750 --> 22:38:35.760 align:start position:0% cheap 22:38:35.760 --> 22:38:38.750 align:start position:0% cheap first<22:38:36.424> place<22:38:36.832> to<22:38:37.016> look<22:38:37.192> will<22:38:37.552> often<22:38:37.920> be<22:38:38.160> the 22:38:38.750 --> 22:38:38.760 align:start position:0% first place to look will often be the 22:38:38.760 --> 22:38:40.670 align:start position:0% first place to look will often be the LED<22:38:39.120> next<22:38:39.600> to<22:38:39.784> the<22:38:39.896> ports<22:38:40.256> where<22:38:40.496> you've 22:38:40.670 --> 22:38:40.680 align:start position:0% LED next to the ports where you've 22:38:40.680 --> 22:38:42.646 align:start position:0% LED next to the ports where you've plugged<22:38:40.976> the<22:38:41.104> cable<22:38:41.336> in<22:38:41.576> if<22:38:42.120> it<22:38:42.240> doesn't<22:38:42.424> light 22:38:42.646 --> 22:38:42.656 align:start position:0% plugged the cable in if it doesn't light 22:38:42.656 --> 22:38:45.310 align:start position:0% plugged the cable in if it doesn't light up<22:38:42.896> then<22:38:43.192> you've<22:38:43.552> got<22:38:43.744> a<22:38:44.104> number<22:38:44.216> of<22:38:44.464> possible 22:38:45.310 --> 22:38:45.320 align:start position:0% up then you've got a number of possible 22:38:45.320 --> 22:38:48.526 align:start position:0% up then you've got a number of possible reasons<22:38:46.320> the<22:38:46.976> cable's<22:38:47.464> not<22:38:48.056> um<22:38:48.120> plugged<22:38:48.480> in 22:38:48.526 --> 22:38:48.536 align:start position:0% reasons the cable's not um plugged in 22:38:48.536 --> 22:38:50.862 align:start position:0% reasons the cable's not um plugged in properly<22:38:48.896> at<22:38:49.080> both<22:38:49.320> ends<22:38:49.744> the<22:38:50.160> cable<22:38:50.400> could<22:38:50.760> be 22:38:50.862 --> 22:38:50.872 align:start position:0% properly at both ends the cable could be 22:38:50.872 --> 22:38:52.670 align:start position:0% properly at both ends the cable could be broken<22:38:51.120> somewhere 22:38:52.670 --> 22:38:52.680 align:start position:0% broken somewhere 22:38:52.680 --> 22:38:54.774 align:start position:0% broken somewhere now<22:38:53.216> here's<22:38:54.000> um 22:38:54.774 --> 22:38:54.784 align:start position:0% now here's um 22:38:54.784 --> 22:38:57.950 align:start position:0% now here's um the<22:38:55.320> troubleshooting<22:38:56.104> flow<22:38:56.640> chart<22:38:56.872> for<22:38:57.424> fiber 22:38:57.950 --> 22:38:57.960 align:start position:0% the troubleshooting flow chart for fiber 22:38:57.960 --> 22:38:59.926 align:start position:0% the troubleshooting flow chart for fiber cable 22:38:59.926 --> 22:38:59.936 align:start position:0% cable 22:38:59.936 --> 22:39:01.790 align:start position:0% cable um<22:39:00.056> well<22:39:00.240> worth<22:39:00.480> maybe<22:39:00.832> just<22:39:01.192> printing<22:39:01.616> the 22:39:01.790 --> 22:39:01.800 align:start position:0% um well worth maybe just printing the 22:39:01.800 --> 22:39:03.230 align:start position:0% um well worth maybe just printing the screen<22:39:02.040> and<22:39:02.464> just<22:39:02.576> following<22:39:02.936> it<22:39:03.120> through 22:39:03.230 --> 22:39:03.240 align:start position:0% screen and just following it through 22:39:03.240 --> 22:39:05.566 align:start position:0% screen and just following it through plug<22:39:03.536> it<22:39:03.720> into<22:39:03.832> a<22:39:04.080> different<22:39:04.192> port<22:39:04.552> does<22:39:05.400> that 22:39:05.566 --> 22:39:05.576 align:start position:0% plug it into a different port does that 22:39:05.576 --> 22:39:07.606 align:start position:0% plug it into a different port does that Port<22:39:05.760> light<22:39:06.056> up<22:39:06.296> then<22:39:06.600> and<22:39:07.144> it<22:39:07.256> shows<22:39:07.440> you<22:39:07.504> it's 22:39:07.606 --> 22:39:07.616 align:start position:0% Port light up then and it shows you it's 22:39:07.616 --> 22:39:10.366 align:start position:0% Port light up then and it shows you it's a<22:39:07.800> problem<22:39:07.920> with<22:39:08.216> the<22:39:08.400> port 22:39:10.366 --> 22:39:10.376 align:start position:0% a problem with the port 22:39:10.376 --> 22:39:11.862 align:start position:0% a problem with the port um just<22:39:10.616> a<22:39:10.800> few<22:39:10.920> simple<22:39:11.104> troubleshooting 22:39:11.862 --> 22:39:11.872 align:start position:0% um just a few simple troubleshooting 22:39:11.872 --> 22:39:13.430 align:start position:0% um just a few simple troubleshooting steps<22:39:12.296> really 22:39:13.430 --> 22:39:13.440 align:start position:0% steps really 22:39:13.440 --> 22:39:15.950 align:start position:0% steps really all<22:39:13.856> right<22:39:14.040> don't<22:39:14.400> look<22:39:14.640> into<22:39:14.936> the<22:39:15.480> cable<22:39:15.600> when 22:39:15.950 --> 22:39:15.960 align:start position:0% all right don't look into the cable when 22:39:15.960 --> 22:39:17.150 align:start position:0% all right don't look into the cable when you've<22:39:16.080> got<22:39:16.192> the<22:39:16.376> other<22:39:16.440> end<22:39:16.680> plugged<22:39:17.104> in 22:39:17.150 --> 22:39:17.160 align:start position:0% you've got the other end plugged in 22:39:17.160 --> 22:39:19.182 align:start position:0% you've got the other end plugged in because<22:39:17.464> the<22:39:18.000> laser<22:39:18.424> will<22:39:18.600> go<22:39:18.720> directly<22:39:19.016> into 22:39:19.182 --> 22:39:19.192 align:start position:0% because the laser will go directly into 22:39:19.192 --> 22:39:22.246 align:start position:0% because the laser will go directly into your<22:39:19.440> light<22:39:19.680> and<22:39:20.464> it<22:39:20.640> could<22:39:20.760> cause<22:39:21.000> damage<22:39:21.536> so 22:39:22.246 --> 22:39:22.256 align:start position:0% your light and it could cause damage so 22:39:22.256 --> 22:39:24.110 align:start position:0% your light and it could cause damage so use<22:39:23.040> um<22:39:23.104> you<22:39:23.216> could<22:39:23.400> well<22:39:23.640> you<22:39:23.824> could<22:39:23.936> actually 22:39:24.110 --> 22:39:24.120 align:start position:0% use um you could well you could actually 22:39:24.120 --> 22:39:27.470 align:start position:0% use um you could well you could actually point<22:39:24.424> it<22:39:24.656> at<22:39:25.320> um<22:39:25.320> a<22:39:26.280> white<22:39:26.400> object<22:39:26.872> or<22:39:27.176> a<22:39:27.360> wall 22:39:27.470 --> 22:39:27.480 align:start position:0% point it at um a white object or a wall 22:39:27.480 --> 22:39:29.390 align:start position:0% point it at um a white object or a wall or<22:39:27.656> at<22:39:27.896> your<22:39:28.016> hand 22:39:29.390 --> 22:39:29.400 align:start position:0% or at your hand 22:39:29.400 --> 22:39:31.182 align:start position:0% or at your hand um<22:39:29.464> but<22:39:29.696> read<22:39:29.936> the<22:39:30.120> documentation<22:39:30.656> that<22:39:30.960> comes 22:39:31.182 --> 22:39:31.192 align:start position:0% um but read the documentation that comes 22:39:31.192 --> 22:39:33.470 align:start position:0% um but read the documentation that comes with<22:39:31.320> the<22:39:31.504> cable<22:39:31.800> to<22:39:32.640> make<22:39:32.760> sure<22:39:33.000> you're<22:39:33.240> doing 22:39:33.470 --> 22:39:33.480 align:start position:0% with the cable to make sure you're doing 22:39:33.480 --> 22:39:35.814 align:start position:0% with the cable to make sure you're doing the<22:39:33.960> correct<22:39:34.496> thing<22:39:34.680> there<22:39:35.216> are<22:39:35.400> obviously 22:39:35.814 --> 22:39:35.824 align:start position:0% the correct thing there are obviously 22:39:35.824 --> 22:39:38.686 align:start position:0% the correct thing there are obviously electronic<22:39:36.536> devices<22:39:36.896> that<22:39:37.256> you<22:39:37.376> can<22:39:37.504> also<22:39:37.744> use 22:39:38.686 --> 22:39:38.696 align:start position:0% electronic devices that you can also use 22:39:38.696 --> 22:39:41.454 align:start position:0% electronic devices that you can also use when<22:39:39.240> you<22:39:39.424> can<22:39:39.600> connect<22:39:39.784> two<22:39:40.256> devices<22:39:40.856> such<22:39:41.336> as 22:39:41.454 --> 22:39:41.464 align:start position:0% when you can connect two devices such as 22:39:41.464 --> 22:39:43.910 align:start position:0% when you can connect two devices such as a<22:39:41.640> server<22:39:41.936> adapter<22:39:42.360> to<22:39:42.536> a<22:39:42.720> switch<22:39:42.896> using<22:39:43.800> a 22:39:43.910 --> 22:39:43.920 align:start position:0% a server adapter to a switch using a 22:39:43.920 --> 22:39:46.670 align:start position:0% a server adapter to a switch using a fiber<22:39:44.280> cable<22:39:44.576> the<22:39:45.424> TX<22:39:45.784> Porter<22:39:46.144> one<22:39:46.320> end<22:39:46.496> should 22:39:46.670 --> 22:39:46.680 align:start position:0% fiber cable the TX Porter one end should 22:39:46.680 --> 22:39:48.774 align:start position:0% fiber cable the TX Porter one end should always<22:39:46.856> be<22:39:47.104> connected<22:39:47.400> to<22:39:47.640> the<22:39:47.760> RX<22:39:48.120> Porter<22:39:48.536> the 22:39:48.774 --> 22:39:48.784 align:start position:0% always be connected to the RX Porter the 22:39:48.784 --> 22:39:51.774 align:start position:0% always be connected to the RX Porter the opposite<22:39:49.144> end<22:39:49.256> normally<22:39:50.216> you'll<22:39:50.576> get<22:39:50.872> a 22:39:51.774 --> 22:39:51.784 align:start position:0% opposite end normally you'll get a 22:39:51.784 --> 22:39:52.846 align:start position:0% opposite end normally you'll get a housing 22:39:52.846 --> 22:39:52.856 align:start position:0% housing 22:39:52.856 --> 22:39:54.950 align:start position:0% housing that<22:39:53.464> both<22:39:53.760> ends<22:39:54.056> of<22:39:54.120> the<22:39:54.240> cable<22:39:54.480> will<22:39:54.784> connect 22:39:54.950 --> 22:39:54.960 align:start position:0% that both ends of the cable will connect 22:39:54.960 --> 22:39:58.366 align:start position:0% that both ends of the cable will connect to<22:39:55.320> and<22:39:55.856> that<22:39:55.976> can<22:39:56.160> only<22:39:56.336> plug<22:39:56.576> in<22:39:56.824> one<22:39:57.176> way<22:39:57.424> to 22:39:58.366 --> 22:39:58.376 align:start position:0% to and that can only plug in one way to 22:39:58.376 --> 22:40:00.046 align:start position:0% to and that can only plug in one way to the<22:39:58.616> device 22:40:00.046 --> 22:40:00.056 align:start position:0% the device 22:40:00.056 --> 22:40:02.454 align:start position:0% the device not<22:40:00.536> always<22:40:00.784> the<22:40:01.144> case<22:40:01.320> and<22:40:02.104> obviously 22:40:02.454 --> 22:40:02.464 align:start position:0% not always the case and obviously 22:40:02.464 --> 22:40:04.246 align:start position:0% not always the case and obviously there's<22:40:02.760> different<22:40:03.120> cable<22:40:03.480> types<22:40:03.960> all<22:40:04.080> over 22:40:04.246 --> 22:40:04.256 align:start position:0% there's different cable types all over 22:40:04.256 --> 22:40:07.790 align:start position:0% there's different cable types all over the<22:40:04.440> world<22:40:04.552> but<22:40:05.336> um<22:40:05.336> normally<22:40:06.080> you'll 22:40:07.790 --> 22:40:07.800 align:start position:0% the world but um normally you'll 22:40:07.800 --> 22:40:08.814 align:start position:0% the world but um normally you'll um 22:40:08.814 --> 22:40:08.824 align:start position:0% um 22:40:08.824 --> 22:40:11.270 align:start position:0% um it'll<22:40:09.296> be<22:40:09.480> designed<22:40:10.080> to<22:40:10.192> be<22:40:10.440> idiot<22:40:10.800> proof<22:40:11.104> so 22:40:11.270 --> 22:40:11.280 align:start position:0% it'll be designed to be idiot proof so 22:40:11.280 --> 22:40:13.734 align:start position:0% it'll be designed to be idiot proof so we<22:40:11.512> don't<22:40:12.056> um<22:40:12.056> cause<22:40:12.360> that<22:40:12.656> issue<22:40:13.016> if<22:40:13.680> you 22:40:13.734 --> 22:40:13.744 align:start position:0% we don't um cause that issue if you 22:40:13.744 --> 22:40:15.166 align:start position:0% we don't um cause that issue if you connect<22:40:13.920> it<22:40:14.280> the<22:40:14.400> other<22:40:14.512> way<22:40:14.640> around<22:40:14.760> you'll 22:40:15.166 --> 22:40:15.176 align:start position:0% connect it the other way around you'll 22:40:15.176 --> 22:40:18.590 align:start position:0% connect it the other way around you'll have<22:40:15.360> no<22:40:15.536> connectivity<22:40:16.144> and<22:40:17.040> then<22:40:17.696> um<22:40:17.760> it'll 22:40:18.590 --> 22:40:18.600 align:start position:0% have no connectivity and then um it'll 22:40:18.600 --> 22:40:20.326 align:start position:0% have no connectivity and then um it'll show<22:40:18.720> no<22:40:18.896> connection 22:40:20.326 --> 22:40:20.336 align:start position:0% show no connection 22:40:20.336 --> 22:40:22.910 align:start position:0% show no connection as<22:40:20.824> supported<22:40:21.296> distances<22:40:21.784> multi-mod<22:40:22.496> fibers 22:40:22.910 --> 22:40:22.920 align:start position:0% as supported distances multi-mod fibers 22:40:22.920 --> 22:40:26.030 align:start position:0% as supported distances multi-mod fibers with<22:40:23.160> 50<22:40:23.336> microns<22:40:24.000> and<22:40:24.480> 62<22:40:24.832> microns<22:40:25.440> can 22:40:26.030 --> 22:40:26.040 align:start position:0% with 50 microns and 62 microns can 22:40:26.040 --> 22:40:29.630 align:start position:0% with 50 microns and 62 microns can support<22:40:26.280> data<22:40:26.824> up<22:40:27.000> to<22:40:27.176> 500<22:40:27.600> meters<22:40:28.080> and<22:40:28.744> 175 22:40:29.630 --> 22:40:29.640 align:start position:0% support data up to 500 meters and 175 22:40:29.640 --> 22:40:32.454 align:start position:0% support data up to 500 meters and 175 respectively<22:40:30.296> again<22:40:31.192> read<22:40:31.800> the<22:40:32.040> label<22:40:32.280> it 22:40:32.454 --> 22:40:32.464 align:start position:0% respectively again read the label it 22:40:32.464 --> 22:40:35.686 align:start position:0% respectively again read the label it comes<22:40:32.696> with<22:40:32.936> your<22:40:33.296> cable<22:40:34.256> in 22:40:35.686 --> 22:40:35.696 align:start position:0% comes with your cable in 22:40:35.696 --> 22:40:36.950 align:start position:0% comes with your cable in um you<22:40:36.000> might<22:40:36.120> you<22:40:36.296> may<22:40:36.424> well<22:40:36.600> be<22:40:36.784> lucky 22:40:36.950 --> 22:40:36.960 align:start position:0% um you might you may well be lucky 22:40:36.960 --> 22:40:39.230 align:start position:0% um you might you may well be lucky enough<22:40:37.144> to<22:40:37.320> have<22:40:37.504> a<22:40:37.744> professional<22:40:38.240> company 22:40:39.230 --> 22:40:39.240 align:start position:0% enough to have a professional company 22:40:39.240 --> 22:40:41.926 align:start position:0% enough to have a professional company coming<22:40:39.600> into<22:40:39.832> your<22:40:40.144> cabling<22:40:40.680> for<22:40:40.976> you<22:40:41.216> and 22:40:41.926 --> 22:40:41.936 align:start position:0% coming into your cabling for you and 22:40:41.936 --> 22:40:43.966 align:start position:0% coming into your cabling for you and then<22:40:42.000> again<22:40:42.176> you<22:40:42.536> may<22:40:42.656> have<22:40:42.784> to<22:40:42.896> go<22:40:43.144> and<22:40:43.376> swap 22:40:43.966 --> 22:40:43.976 align:start position:0% then again you may have to go and swap 22:40:43.976 --> 22:40:45.822 align:start position:0% then again you may have to go and swap some<22:40:44.160> cable<22:40:44.464> out<22:40:44.696> or<22:40:44.936> install<22:40:45.120> a<22:40:45.424> new<22:40:45.600> device 22:40:45.822 --> 22:40:45.832 align:start position:0% some cable out or install a new device 22:40:45.832 --> 22:40:47.990 align:start position:0% some cable out or install a new device without<22:40:46.616> the<22:40:46.920> aid<22:40:47.160> of<22:40:47.280> this<22:40:47.400> company<22:40:47.576> so<22:40:47.872> you 22:40:47.990 --> 22:40:48.000 align:start position:0% without the aid of this company so you 22:40:48.000 --> 22:40:49.270 align:start position:0% without the aid of this company so you do<22:40:48.120> need<22:40:48.296> to<22:40:48.424> know 22:40:49.270 --> 22:40:49.280 align:start position:0% do need to know 22:40:49.280 --> 22:40:52.486 align:start position:0% do need to know multi-mad<22:40:50.280> fibers<22:40:51.056> are<22:40:51.360> categorized<22:40:52.080> further 22:40:52.486 --> 22:40:52.496 align:start position:0% multi-mad fibers are categorized further 22:40:52.496 --> 22:40:56.454 align:start position:0% multi-mad fibers are categorized further by<22:40:52.856> Optical<22:40:53.336> multi-mode<22:40:54.056> or<22:40:54.296> om<22:40:54.600> designator 22:40:56.454 --> 22:40:56.464 align:start position:0% by Optical multi-mode or om designator 22:40:56.464 --> 22:40:59.926 align:start position:0% by Optical multi-mode or om designator these<22:40:56.936> are<22:40:57.056> labeled<22:40:57.360> from<22:40:57.536> om1<22:40:58.192> to<22:40:58.496> om4<22:40:59.216> just 22:40:59.926 --> 22:40:59.936 align:start position:0% these are labeled from om1 to om4 just 22:40:59.936 --> 22:41:04.606 align:start position:0% these are labeled from om1 to om4 just check<22:41:00.296> the<22:41:01.192> uh<22:41:02.160> table<22:41:03.056> and 22:41:04.606 --> 22:41:04.616 align:start position:0% check the uh table and 22:41:04.616 --> 22:41:06.526 align:start position:0% check the uh table and um<22:41:04.680> you've<22:41:05.640> let<22:41:05.824> you've<22:41:06.056> normally<22:41:06.176> got<22:41:06.424> a 22:41:06.526 --> 22:41:06.536 align:start position:0% um you've let you've normally got a 22:41:06.536 --> 22:41:08.566 align:start position:0% um you've let you've normally got a label<22:41:06.784> on<22:41:06.960> your<22:41:07.080> cable<22:41:07.320> as<22:41:07.616> well<22:41:07.800> to<22:41:08.280> see<22:41:08.400> what 22:41:08.566 --> 22:41:08.576 align:start position:0% label on your cable as well to see what 22:41:08.576 --> 22:41:10.182 align:start position:0% label on your cable as well to see what you<22:41:08.696> do<22:41:08.824> however<22:41:09.176> it's<22:41:09.424> stamped<22:41:09.720> on<22:41:09.832> the<22:41:10.016> side 22:41:10.182 --> 22:41:10.192 align:start position:0% you do however it's stamped on the side 22:41:10.192 --> 22:41:12.646 align:start position:0% you do however it's stamped on the side and<22:41:10.920> just<22:41:11.104> check<22:41:11.280> the<22:41:11.576> specifications<22:41:12.296> and 22:41:12.646 --> 22:41:12.656 align:start position:0% and just check the specifications and 22:41:12.656 --> 22:41:13.966 align:start position:0% and just check the specifications and allowances 22:41:13.966 --> 22:41:13.976 align:start position:0% allowances 22:41:13.976 --> 22:41:16.070 align:start position:0% allowances when<22:41:14.464> you<22:41:14.640> troubleshoot<22:41:15.240> in<22:41:15.424> check<22:41:15.832> whether 22:41:16.070 --> 22:41:16.080 align:start position:0% when you troubleshoot in check whether 22:41:16.080 --> 22:41:18.350 align:start position:0% when you troubleshoot in check whether the<22:41:16.440> cable<22:41:17.216> supports<22:41:17.760> the<22:41:17.872> speed<22:41:18.120> and 22:41:18.350 --> 22:41:18.360 align:start position:0% the cable supports the speed and 22:41:18.360 --> 22:41:22.846 align:start position:0% the cable supports the speed and distance<22:41:18.600> of<22:41:19.320> the<22:41:19.504> link<22:41:19.616> between<22:41:19.920> the<22:41:20.280> devices 22:41:22.846 --> 22:41:22.856 align:start position:0% 22:41:22.856 --> 22:41:25.846 align:start position:0% Bend<22:41:23.464> radius<22:41:24.000> most<22:41:24.784> fiber<22:41:25.192> optic<22:41:25.504> cables<22:41:25.744> are 22:41:25.846 --> 22:41:25.856 align:start position:0% Bend radius most fiber optic cables are 22:41:25.856 --> 22:41:26.990 align:start position:0% Bend radius most fiber optic cables are made<22:41:25.976> of<22:41:26.160> glass 22:41:26.990 --> 22:41:27.000 align:start position:0% made of glass 22:41:27.000 --> 22:41:29.030 align:start position:0% made of glass a<22:41:27.480> sharp<22:41:27.832> Bend<22:41:28.016> at<22:41:28.256> some<22:41:28.440> point<22:41:28.616> they<22:41:28.856> are 22:41:29.030 --> 22:41:29.040 align:start position:0% a sharp Bend at some point they are 22:41:29.040 --> 22:41:30.710 align:start position:0% a sharp Bend at some point they are pretty<22:41:29.280> flexible<22:41:29.640> but<22:41:29.936> if<22:41:30.056> you<22:41:30.176> bend<22:41:30.360> it<22:41:30.536> too 22:41:30.710 --> 22:41:30.720 align:start position:0% pretty flexible but if you bend it too 22:41:30.720 --> 22:41:32.686 align:start position:0% pretty flexible but if you bend it too much<22:41:30.832> it<22:41:31.080> will<22:41:31.256> break<22:41:31.440> the<22:41:31.616> glass<22:41:31.800> the<22:41:32.576> bend 22:41:32.686 --> 22:41:32.696 align:start position:0% much it will break the glass the bend 22:41:32.696 --> 22:41:35.390 align:start position:0% much it will break the glass the bend radius<22:41:33.176> refers<22:41:33.480> to<22:41:33.656> the<22:41:33.832> smallest<22:41:34.192> bend<22:41:34.616> a 22:41:35.390 --> 22:41:35.400 align:start position:0% radius refers to the smallest bend a 22:41:35.400 --> 22:41:37.846 align:start position:0% radius refers to the smallest bend a cable<22:41:35.696> can<22:41:35.936> withstand<22:41:36.480> again<22:41:37.256> if<22:41:37.552> you<22:41:37.680> start 22:41:37.846 --> 22:41:37.856 align:start position:0% cable can withstand again if you start 22:41:37.856 --> 22:41:40.182 align:start position:0% cable can withstand again if you start wrapping<22:41:38.400> this<22:41:38.576> Cable<22:41:38.872> Round<22:41:39.296> and<22:41:39.600> Round<22:41:39.832> a 22:41:40.182 --> 22:41:40.192 align:start position:0% wrapping this Cable Round and Round a 22:41:40.192 --> 22:41:43.134 align:start position:0% wrapping this Cable Round and Round a pole<22:41:40.552> in<22:41:41.160> order<22:41:41.280> to<22:41:41.464> take<22:41:41.760> up<22:41:41.936> the<22:41:42.120> slack<22:41:42.424> then 22:41:43.134 --> 22:41:43.144 align:start position:0% pole in order to take up the slack then 22:41:43.144 --> 22:41:45.710 align:start position:0% pole in order to take up the slack then you<22:41:43.552> could<22:41:43.680> well<22:41:44.040> check<22:41:44.576> and<22:41:44.824> break<22:41:45.120> the<22:41:45.424> bend 22:41:45.710 --> 22:41:45.720 align:start position:0% you could well check and break the bend 22:41:45.720 --> 22:41:48.230 align:start position:0% you could well check and break the bend radius<22:41:46.192> and<22:41:46.856> rendering<22:41:47.336> the<22:41:47.464> cable 22:41:48.230 --> 22:41:48.240 align:start position:0% radius and rendering the cable 22:41:48.240 --> 22:41:51.590 align:start position:0% radius and rendering the cable um unserviceable 22:41:51.590 --> 22:41:51.600 align:start position:0% 22:41:51.600 --> 22:41:53.814 align:start position:0% to<22:41:52.496> avoid<22:41:52.800> issues<22:41:53.160> don't<22:41:53.336> bend<22:41:53.640> them 22:41:53.814 --> 22:41:53.824 align:start position:0% to avoid issues don't bend them 22:41:53.824 --> 22:41:56.326 align:start position:0% to avoid issues don't bend them obviously<22:41:54.296> or<22:41:54.480> more<22:41:54.656> than<22:41:54.832> you<22:41:55.016> have<22:41:55.144> to<22:41:55.256> the 22:41:56.326 --> 22:41:56.336 align:start position:0% obviously or more than you have to the 22:41:56.336 --> 22:41:58.006 align:start position:0% obviously or more than you have to the otdr<22:41:56.824> can<22:41:57.000> be<22:41:57.120> used<22:41:57.240> to<22:41:57.360> check<22:41:57.536> whether<22:41:57.720> the 22:41:58.006 --> 22:41:58.016 align:start position:0% otdr can be used to check whether the 22:41:58.016 --> 22:41:59.750 align:start position:0% otdr can be used to check whether the cable<22:41:58.144> is<22:41:58.496> damaged 22:41:59.750 --> 22:41:59.760 align:start position:0% cable is damaged 22:41:59.760 --> 22:42:02.030 align:start position:0% cable is damaged damage<22:42:00.480> cable<22:42:00.784> obviously<22:42:01.440> needs<22:42:01.800> to<22:42:01.856> be 22:42:02.030 --> 22:42:02.040 align:start position:0% damage cable obviously needs to be 22:42:02.040 --> 22:42:03.414 align:start position:0% damage cable obviously needs to be replaced<22:42:02.576> hopefully<22:42:02.872> that<22:42:03.056> goes<22:42:03.360> without 22:42:03.414 --> 22:42:03.424 align:start position:0% replaced hopefully that goes without 22:42:03.424 --> 22:42:04.734 align:start position:0% replaced hopefully that goes without saying 22:42:04.734 --> 22:42:04.744 align:start position:0% saying 22:42:04.744 --> 22:42:07.310 align:start position:0% saying um<22:42:04.800> the<22:42:05.160> broken<22:42:05.336> cable<22:42:05.824> some<22:42:06.656> people<22:42:06.832> put<22:42:07.192> them 22:42:07.310 --> 22:42:07.320 align:start position:0% um the broken cable some people put them 22:42:07.320 --> 22:42:09.646 align:start position:0% um the broken cable some people put them in<22:42:07.504> a<22:42:07.616> cable<22:42:07.856> box<22:42:08.160> if<22:42:08.640> it's<22:42:08.824> broken<22:42:09.056> make<22:42:09.536> sure 22:42:09.646 --> 22:42:09.656 align:start position:0% in a cable box if it's broken make sure 22:42:09.656 --> 22:42:13.134 align:start position:0% in a cable box if it's broken make sure you<22:42:09.832> dispose<22:42:10.192> of<22:42:10.376> it<22:42:10.552> in<22:42:11.760> um<22:42:11.760> the<22:42:12.056> legal<22:42:12.480> the 22:42:13.134 --> 22:42:13.144 align:start position:0% you dispose of it in um the legal the 22:42:13.144 --> 22:42:14.750 align:start position:0% you dispose of it in um the legal the legal<22:42:13.440> manner<22:42:13.800> so<22:42:13.976> you<22:42:14.104> can't<22:42:14.216> throw<22:42:14.336> it<22:42:14.512> onto 22:42:14.750 --> 22:42:14.760 align:start position:0% legal manner so you can't throw it onto 22:42:14.760 --> 22:42:16.910 align:start position:0% legal manner so you can't throw it onto a<22:42:14.936> fire<22:42:15.120> usually<22:42:15.656> you'd<22:42:16.376> have<22:42:16.496> to<22:42:16.616> have<22:42:16.800> it 22:42:16.910 --> 22:42:16.920 align:start position:0% a fire usually you'd have to have it 22:42:16.920 --> 22:42:19.846 align:start position:0% a fire usually you'd have to have it professionally<22:42:17.824> uh<22:42:18.176> destroyed<22:42:18.784> or<22:42:19.080> every 22:42:19.846 --> 22:42:19.856 align:start position:0% professionally uh destroyed or every 22:42:19.856 --> 22:42:22.734 align:start position:0% professionally uh destroyed or every cycled<22:42:20.640> if<22:42:21.480> you've<22:42:21.656> got<22:42:21.784> dirt<22:42:22.016> because<22:42:22.440> it 22:42:22.734 --> 22:42:22.744 align:start position:0% cycled if you've got dirt because it 22:42:22.744 --> 22:42:25.134 align:start position:0% cycled if you've got dirt because it uses<22:42:23.040> light<22:42:23.336> on<22:42:23.640> the<22:42:23.760> fiber<22:42:24.120> cables<22:42:24.600> if<22:42:24.960> you've 22:42:25.134 --> 22:42:25.144 align:start position:0% uses light on the fiber cables if you've 22:42:25.144 --> 22:42:27.286 align:start position:0% uses light on the fiber cables if you've got<22:42:25.192> dirt<22:42:25.504> on<22:42:25.744> one<22:42:25.920> end<22:42:26.040> it<22:42:26.216> will<22:42:26.336> cause 22:42:27.286 --> 22:42:27.296 align:start position:0% got dirt on one end it will cause 22:42:27.296 --> 22:42:27.822 align:start position:0% got dirt on one end it will cause um 22:42:27.822 --> 22:42:27.832 align:start position:0% um 22:42:27.832 --> 22:42:31.246 align:start position:0% um problems<22:42:28.680> High<22:42:28.976> loss<22:42:29.336> and<22:42:29.600> reflectance<22:42:30.600> clean 22:42:31.246 --> 22:42:31.256 align:start position:0% problems High loss and reflectance clean 22:42:31.256 --> 22:42:34.246 align:start position:0% problems High loss and reflectance clean it<22:42:31.552> using<22:42:31.976> the<22:42:32.280> cleaning<22:42:33.016> methods<22:42:34.016> and 22:42:34.246 --> 22:42:34.256 align:start position:0% it using the cleaning methods and 22:42:34.256 --> 22:42:36.646 align:start position:0% it using the cleaning methods and supplies<22:42:34.680> provided<22:42:35.216> with<22:42:35.512> the<22:42:35.640> cables<22:42:36.120> don't 22:42:36.646 --> 22:42:36.656 align:start position:0% supplies provided with the cables don't 22:42:36.656 --> 22:42:38.502 align:start position:0% supplies provided with the cables don't wipe<22:42:37.080> at<22:42:37.192> the<22:42:37.320> end<22:42:37.440> of<22:42:37.552> it<22:42:37.680> on<22:42:37.976> on<22:42:38.336> your 22:42:38.502 --> 22:42:38.512 align:start position:0% wipe at the end of it on on your 22:42:38.512 --> 22:42:40.926 align:start position:0% wipe at the end of it on on your trousers 22:42:40.926 --> 22:42:40.936 align:start position:0% trousers 22:42:40.936 --> 22:42:43.430 align:start position:0% trousers attenuation<22:42:41.936> signal<22:42:42.600> loss<22:42:42.960> over<22:42:43.192> the 22:42:43.430 --> 22:42:43.440 align:start position:0% attenuation signal loss over the 22:42:43.440 --> 22:42:46.134 align:start position:0% attenuation signal loss over the fireball<22:42:43.856> optic<22:42:44.336> cable<22:42:44.832> following<22:42:45.832> could<22:42:46.016> be 22:42:46.134 --> 22:42:46.144 align:start position:0% fireball optic cable following could be 22:42:46.144 --> 22:42:47.862 align:start position:0% fireball optic cable following could be the<22:42:46.320> reasons<22:42:46.800> it<22:42:47.280> could<22:42:47.400> have<22:42:47.512> been<22:42:47.696> over 22:42:47.862 --> 22:42:47.872 align:start position:0% the reasons it could have been over 22:42:47.872 --> 22:42:50.326 align:start position:0% the reasons it could have been over stressed<22:42:48.360> during<22:42:48.480> installation<22:42:49.336> improper 22:42:50.326 --> 22:42:50.336 align:start position:0% stressed during installation improper 22:42:50.336 --> 22:42:53.326 align:start position:0% stressed during installation improper termination<22:42:51.144> improper<22:42:52.144> splicing<22:42:52.744> if<22:42:53.160> it's 22:42:53.326 --> 22:42:53.336 align:start position:0% termination improper splicing if it's 22:42:53.336 --> 22:42:55.366 align:start position:0% termination improper splicing if it's been<22:42:53.512> spliced<22:42:54.000> somewhere<22:42:54.296> could<22:42:55.080> be<22:42:55.192> broken 22:42:55.366 --> 22:42:55.376 align:start position:0% been spliced somewhere could be broken 22:42:55.376 --> 22:42:59.750 align:start position:0% been spliced somewhere could be broken fiber<22:42:56.216> again<22:42:56.936> you<22:42:57.296> can<22:42:57.424> use<22:42:57.600> the<22:42:58.256> otdr<22:42:58.856> to 22:42:59.750 --> 22:42:59.760 align:start position:0% fiber again you can use the otdr to 22:42:59.760 --> 22:43:01.790 align:start position:0% fiber again you can use the otdr to locate<22:43:00.424> the<22:43:00.656> faults 22:43:01.790 --> 22:43:01.800 align:start position:0% locate the faults 22:43:01.800 --> 22:43:04.182 align:start position:0% locate the faults wavelength<22:43:02.640> mismatch 22:43:04.182 --> 22:43:04.192 align:start position:0% wavelength mismatch 22:43:04.192 --> 22:43:06.590 align:start position:0% wavelength mismatch fiber<22:43:04.800> cable<22:43:05.040> uses<22:43:05.464> wavelengths<22:43:06.120> longer<22:43:06.480> than 22:43:06.590 --> 22:43:06.600 align:start position:0% fiber cable uses wavelengths longer than 22:43:06.600 --> 22:43:09.950 align:start position:0% fiber cable uses wavelengths longer than a<22:43:06.896> normal<22:43:07.192> light<22:43:07.552> it's<22:43:08.336> usually<22:43:08.640> around<22:43:08.960> 850 22:43:09.950 --> 22:43:09.960 align:start position:0% a normal light it's usually around 850 22:43:09.960 --> 22:43:14.150 align:start position:0% a normal light it's usually around 850 1300<22:43:10.800> or<22:43:11.104> 1550<22:43:11.872> newton<22:43:12.600> meters 22:43:14.150 --> 22:43:14.160 align:start position:0% 1300 or 1550 newton meters 22:43:14.160 --> 22:43:16.182 align:start position:0% 1300 or 1550 newton meters multi-mode<22:43:15.000> fiber<22:43:15.296> is<22:43:15.480> designed<22:43:15.784> to<22:43:15.896> operate 22:43:16.182 --> 22:43:16.192 align:start position:0% multi-mode fiber is designed to operate 22:43:16.192 --> 22:43:18.950 align:start position:0% multi-mode fiber is designed to operate at<22:43:16.440> 850<22:43:16.920> to<22:43:17.280> 1300 22:43:18.950 --> 22:43:18.960 align:start position:0% at 850 to 1300 22:43:18.960 --> 22:43:23.862 align:start position:0% at 850 to 1300 single<22:43:19.680> mode<22:43:19.800> 13<22:43:20.400> 10<22:43:20.936> or<22:43:21.480> 1550 22:43:23.862 --> 22:43:23.872 align:start position:0% single mode 13 10 or 1550 22:43:23.872 --> 22:43:25.310 align:start position:0% single mode 13 10 or 1550 the<22:43:24.240> wavelength<22:43:24.720> is<22:43:24.784> used<22:43:24.896> for<22:43:25.080> transmission 22:43:25.310 --> 22:43:25.320 align:start position:0% the wavelength is used for transmission 22:43:25.320 --> 22:43:27.110 align:start position:0% the wavelength is used for transmission on<22:43:25.800> the<22:43:25.976> wavelengths<22:43:26.464> that<22:43:26.576> must<22:43:26.696> be<22:43:26.824> tested 22:43:27.110 --> 22:43:27.120 align:start position:0% on the wavelengths that must be tested 22:43:27.120 --> 22:43:32.326 align:start position:0% on the wavelengths that must be tested for<22:43:27.296> Signal<22:43:27.656> losses<22:43:28.016> in<22:43:28.440> the<22:43:28.680> cable<22:43:28.856> plants 22:43:32.326 --> 22:43:32.336 align:start position:0% 22:43:32.336 --> 22:43:34.310 align:start position:0% now<22:43:32.640> when<22:43:32.824> the<22:43:33.000> mismatch<22:43:33.360> fiber<22:43:33.832> cables<22:43:34.192> are 22:43:34.310 --> 22:43:34.320 align:start position:0% now when the mismatch fiber cables are 22:43:34.320 --> 22:43:36.166 align:start position:0% now when the mismatch fiber cables are coupled<22:43:34.616> the<22:43:34.856> incompatibility<22:43:35.576> of<22:43:35.872> the<22:43:36.056> core 22:43:36.166 --> 22:43:36.176 align:start position:0% coupled the incompatibility of the core 22:43:36.176 --> 22:43:39.046 align:start position:0% coupled the incompatibility of the core sizes<22:43:36.656> results<22:43:37.080> in<22:43:37.440> signal<22:43:37.920> loss 22:43:39.046 --> 22:43:39.056 align:start position:0% sizes results in signal loss 22:43:39.056 --> 22:43:40.542 align:start position:0% sizes results in signal loss now<22:43:39.424> there's<22:43:39.600> no<22:43:39.832> problem<22:43:40.080> if<22:43:40.440> you're 22:43:40.542 --> 22:43:40.552 align:start position:0% now there's no problem if you're 22:43:40.552 --> 22:43:42.414 align:start position:0% now there's no problem if you're transmitting<22:43:41.104> light<22:43:41.280> from<22:43:41.512> a<22:43:41.696> smaller<22:43:42.000> fiber 22:43:42.414 --> 22:43:42.424 align:start position:0% transmitting light from a smaller fiber 22:43:42.424 --> 22:43:44.686 align:start position:0% transmitting light from a smaller fiber core<22:43:42.656> to<22:43:42.896> a<22:43:43.080> larger<22:43:43.320> one<22:43:43.552> but<22:43:44.216> the<22:43:44.400> other<22:43:44.512> way 22:43:44.686 --> 22:43:44.696 align:start position:0% core to a larger one but the other way 22:43:44.696 --> 22:43:48.350 align:start position:0% core to a larger one but the other way around<22:43:45.256> and<22:43:46.256> you'll<22:43:46.496> have<22:43:46.680> signal<22:43:47.040> loss 22:43:48.350 --> 22:43:48.360 align:start position:0% around and you'll have signal loss 22:43:48.360 --> 22:43:51.774 align:start position:0% around and you'll have signal loss the<22:43:48.896> signal<22:43:49.192> loss<22:43:49.504> can<22:43:49.680> be<22:43:49.800> around<22:43:49.976> 20<22:43:50.512> DB<22:43:51.360> when 22:43:51.774 --> 22:43:51.784 align:start position:0% the signal loss can be around 20 DB when 22:43:51.784 --> 22:43:54.350 align:start position:0% the signal loss can be around 20 DB when a<22:43:52.320> couple<22:43:52.680> when<22:43:53.336> we<22:43:53.464> could<22:43:53.576> pull<22:43:53.760> a<22:43:53.936> multi-mode 22:43:54.350 --> 22:43:54.360 align:start position:0% a couple when we could pull a multi-mode 22:43:54.360 --> 22:43:56.990 align:start position:0% a couple when we could pull a multi-mode fiber<22:43:54.720> to<22:43:54.896> a<22:43:55.080> single<22:43:55.376> mode<22:43:55.552> again<22:43:56.512> read<22:43:56.824> the 22:43:56.990 --> 22:43:57.000 align:start position:0% fiber to a single mode again read the 22:43:57.000 --> 22:43:59.326 align:start position:0% fiber to a single mode again read the documentation<22:43:57.680> that<22:43:58.680> comes<22:43:58.920> with<22:43:58.976> all<22:43:59.160> your 22:43:59.326 --> 22:43:59.336 align:start position:0% documentation that comes with all your 22:43:59.336 --> 22:44:00.590 align:start position:0% documentation that comes with all your cable<22:43:59.696> in 22:44:00.590 --> 22:44:00.600 align:start position:0% cable in 22:44:00.600 --> 22:44:02.990 align:start position:0% cable in so<22:44:00.960> I've<22:44:01.080> looked<22:44:01.376> at<22:44:01.440> fiber<22:44:01.856> cable<22:44:02.160> supported 22:44:02.990 --> 22:44:03.000 align:start position:0% so I've looked at fiber cable supported 22:44:03.000 --> 22:44:06.230 align:start position:0% so I've looked at fiber cable supported distances<22:44:03.480> and<22:44:03.784> categories<22:44:04.320> the<22:44:04.744> bend<22:44:04.920> radius 22:44:06.230 --> 22:44:06.240 align:start position:0% distances and categories the bend radius 22:44:06.240 --> 22:44:09.822 align:start position:0% distances and categories the bend radius dirt<22:44:06.656> on<22:44:06.960> your<22:44:07.144> connectors<22:44:08.000> attenuation<22:44:09.000> and 22:44:09.822 --> 22:44:09.832 align:start position:0% dirt on your connectors attenuation and 22:44:09.832 --> 22:44:11.750 align:start position:0% dirt on your connectors attenuation and wavelength<22:44:10.496> mismatch<22:44:10.920> and<22:44:11.160> fiber<22:44:11.576> type 22:44:11.750 --> 22:44:11.760 align:start position:0% wavelength mismatch and fiber type 22:44:11.760 --> 22:44:14.094 align:start position:0% wavelength mismatch and fiber type mismatch<22:44:12.240> that's<22:44:13.144> all<22:44:13.320> for<22:44:13.504> now<22:44:13.616> thanks<22:44:13.920> for 22:44:14.094 --> 22:44:14.104 align:start position:0% mismatch that's all for now thanks for 22:44:14.104 --> 22:44:19.890 align:start position:0% mismatch that's all for now thanks for watching 22:44:19.890 --> 22:44:19.900 align:start position:0% 22:44:19.900 --> 22:44:28.246 align:start position:0% [Music] 22:44:28.246 --> 22:44:28.256 align:start position:0% [Music] 22:44:28.256 --> 22:44:36.246 align:start position:0% [Music] foreign 22:44:36.246 --> 22:44:36.256 align:start position:0% 22:44:36.256 --> 22:44:39.414 align:start position:0% 19<22:44:37.256> lesson<22:44:37.744> 4<22:44:37.976> common<22:44:38.336> network<22:44:38.696> issues 22:44:39.414 --> 22:44:39.424 align:start position:0% 19 lesson 4 common network issues 22:44:39.424 --> 22:44:41.926 align:start position:0% 19 lesson 4 common network issues there's<22:44:40.376> actually<22:44:40.552> entire<22:44:41.104> books<22:44:41.696> been 22:44:41.926 --> 22:44:41.936 align:start position:0% there's actually entire books been 22:44:41.936 --> 22:44:45.046 align:start position:0% there's actually entire books been written<22:44:42.296> about<22:44:42.536> troubleshooting<22:44:43.440> Networks 22:44:45.046 --> 22:44:45.056 align:start position:0% written about troubleshooting Networks 22:44:45.056 --> 22:44:48.286 align:start position:0% written about troubleshooting Networks and<22:44:45.784> from<22:44:46.080> PC<22:44:46.680> switches<22:44:47.336> and<22:44:47.512> routers<22:44:47.936> and 22:44:48.286 --> 22:44:48.296 align:start position:0% and from PC switches and routers and 22:44:48.296 --> 22:44:50.630 align:start position:0% and from PC switches and routers and it's<22:44:48.600> something<22:44:49.256> that<22:44:49.680> requires<22:44:50.280> a<22:44:50.400> bit<22:44:50.464> of 22:44:50.630 --> 22:44:50.640 align:start position:0% it's something that requires a bit of 22:44:50.640 --> 22:44:52.910 align:start position:0% it's something that requires a bit of experience<22:44:51.176> common<22:44:51.720> sense 22:44:52.910 --> 22:44:52.920 align:start position:0% experience common sense 22:44:52.920 --> 22:44:55.606 align:start position:0% experience common sense and<22:44:53.512> often<22:44:53.824> a<22:44:54.000> plan<22:44:54.176> and<22:44:54.656> sometimes<22:44:55.080> a<22:44:55.320> bit<22:44:55.440> of 22:44:55.606 --> 22:44:55.616 align:start position:0% and often a plan and sometimes a bit of 22:44:55.616 --> 22:44:59.150 align:start position:0% and often a plan and sometimes a bit of good<22:44:56.160> luck<22:44:56.336> as<22:44:56.512> well<22:44:56.696> and<22:44:56.872> guesswork 22:44:59.150 --> 22:44:59.160 align:start position:0% good luck as well and guesswork 22:44:59.160 --> 22:45:01.734 align:start position:0% good luck as well and guesswork we're<22:44:59.696> going<22:44:59.872> to<22:45:00.000> look<22:45:00.120> at<22:45:00.320> common<22:45:01.320> things 22:45:01.734 --> 22:45:01.744 align:start position:0% we're going to look at common things 22:45:01.744 --> 22:45:03.950 align:start position:0% we're going to look at common things that<22:45:02.280> normally<22:45:02.760> go<22:45:03.000> wrong<22:45:03.240> day<22:45:03.600> to<22:45:03.784> day 22:45:03.950 --> 22:45:03.960 align:start position:0% that normally go wrong day to day 22:45:03.960 --> 22:45:06.166 align:start position:0% that normally go wrong day to day incorrect<22:45:04.800> default<22:45:05.104> gateway 22:45:06.166 --> 22:45:06.176 align:start position:0% incorrect default gateway 22:45:06.176 --> 22:45:09.230 align:start position:0% incorrect default gateway broad<22:45:06.720> Customs<22:45:07.440> duplicate<22:45:08.104> IP<22:45:08.464> address<22:45:08.640> your 22:45:09.230 --> 22:45:09.240 align:start position:0% broad Customs duplicate IP address your 22:45:09.240 --> 22:45:11.750 align:start position:0% broad Customs duplicate IP address your duplex<22:45:09.656> and<22:45:09.896> speed<22:45:10.144> mismatches 22:45:11.750 --> 22:45:11.760 align:start position:0% duplex and speed mismatches 22:45:11.760 --> 22:45:14.990 align:start position:0% duplex and speed mismatches incorrect<22:45:12.480> vlans<22:45:13.104> Hardware<22:45:14.104> failures<22:45:14.760> and 22:45:14.990 --> 22:45:15.000 align:start position:0% incorrect vlans Hardware failures and 22:45:15.000 --> 22:45:17.566 align:start position:0% incorrect vlans Hardware failures and DHCP<22:45:15.896> DNS 22:45:17.566 --> 22:45:17.576 align:start position:0% DHCP DNS 22:45:17.576 --> 22:45:20.270 align:start position:0% DHCP DNS interface<22:45:18.424> misconfiguration<22:45:19.376> cable 22:45:20.270 --> 22:45:20.280 align:start position:0% interface misconfiguration cable 22:45:20.280 --> 22:45:21.774 align:start position:0% interface misconfiguration cable placements 22:45:21.774 --> 22:45:21.784 align:start position:0% placements 22:45:21.784 --> 22:45:24.886 align:start position:0% placements power<22:45:22.192> failures<22:45:22.800> and<22:45:23.216> then<22:45:23.400> less<22:45:23.640> common<22:45:23.896> MTU 22:45:24.886 --> 22:45:24.896 align:start position:0% power failures and then less common MTU 22:45:24.896 --> 22:45:28.486 align:start position:0% power failures and then less common MTU black<22:45:25.192> hole<22:45:25.680> Nick<22:45:26.464> teaming<22:45:27.056> issues 22:45:28.486 --> 22:45:28.496 align:start position:0% black hole Nick teaming issues 22:45:28.496 --> 22:45:31.246 align:start position:0% black hole Nick teaming issues so<22:45:28.976> you<22:45:29.216> can<22:45:29.280> create<22:45:29.400> default<22:45:29.824> gateway 22:45:31.246 --> 22:45:31.256 align:start position:0% so you can create default gateway 22:45:31.256 --> 22:45:33.526 align:start position:0% so you can create default gateway um<22:45:31.320> it<22:45:31.976> depends<22:45:32.400> if<22:45:32.760> there's<22:45:32.872> been<22:45:33.120> a<22:45:33.296> change 22:45:33.526 --> 22:45:33.536 align:start position:0% um it depends if there's been a change 22:45:33.536 --> 22:45:35.630 align:start position:0% um it depends if there's been a change of<22:45:34.016> default<22:45:34.440> gateway 22:45:35.630 --> 22:45:35.640 align:start position:0% of default gateway 22:45:35.640 --> 22:45:37.790 align:start position:0% of default gateway if<22:45:36.176> the<22:45:36.424> device 22:45:37.790 --> 22:45:37.800 align:start position:0% if the device 22:45:37.800 --> 22:45:38.502 align:start position:0% if the device um 22:45:38.502 --> 22:45:38.512 align:start position:0% um 22:45:38.512 --> 22:45:41.094 align:start position:0% um that<22:45:39.240> is<22:45:39.480> experiencing<22:45:40.080> the<22:45:40.320> problems<22:45:40.744> has 22:45:41.094 --> 22:45:41.104 align:start position:0% that is experiencing the problems has 22:45:41.104 --> 22:45:42.822 align:start position:0% that is experiencing the problems has had<22:45:41.280> any<22:45:41.464> changes 22:45:42.822 --> 22:45:42.832 align:start position:0% had any changes 22:45:42.832 --> 22:45:46.070 align:start position:0% had any changes or<22:45:43.856> um<22:45:43.920> somebody's<22:45:44.824> gone<22:45:45.296> in<22:45:45.480> and<22:45:45.656> configured 22:45:46.070 --> 22:45:46.080 align:start position:0% or um somebody's gone in and configured 22:45:46.080 --> 22:45:47.566 align:start position:0% or um somebody's gone in and configured something<22:45:46.320> so<22:45:46.744> it<22:45:46.856> all<22:45:46.976> depends<22:45:47.280> on<22:45:47.400> the 22:45:47.566 --> 22:45:47.576 align:start position:0% something so it all depends on the 22:45:47.576 --> 22:45:49.182 align:start position:0% something so it all depends on the questions<22:45:47.696> you've<22:45:48.120> asked<22:45:48.360> really 22:45:49.182 --> 22:45:49.192 align:start position:0% questions you've asked really 22:45:49.192 --> 22:45:50.630 align:start position:0% questions you've asked really but<22:45:49.440> if<22:45:49.616> you've<22:45:49.744> got<22:45:49.800> the<22:45:49.920> incorrect<22:45:50.280> default 22:45:50.630 --> 22:45:50.640 align:start position:0% but if you've got the incorrect default 22:45:50.640 --> 22:45:53.526 align:start position:0% but if you've got the incorrect default gateway<22:45:51.056> then<22:45:51.480> all<22:45:52.080> traffic<22:45:52.320> from<22:45:52.856> your<22:45:53.104> host 22:45:53.526 --> 22:45:53.536 align:start position:0% gateway then all traffic from your host 22:45:53.536 --> 22:45:56.206 align:start position:0% gateway then all traffic from your host device<22:45:54.536> is<22:45:55.192> going<22:45:55.440> to<22:45:55.616> the<22:45:55.800> wrong<22:45:55.920> location 22:45:56.206 --> 22:45:56.216 align:start position:0% device is going to the wrong location 22:45:56.216 --> 22:45:59.206 align:start position:0% device is going to the wrong location and<22:45:57.176> Layer<22:45:57.536> Two<22:45:57.656> devices<22:45:58.016> such<22:45:58.440> as<22:45:58.616> switches 22:45:59.206 --> 22:45:59.216 align:start position:0% and Layer Two devices such as switches 22:45:59.216 --> 22:46:01.310 align:start position:0% and Layer Two devices such as switches also<22:45:59.696> are<22:46:00.240> normally<22:46:00.536> configured<22:46:00.960> with<22:46:01.144> the 22:46:01.310 --> 22:46:01.320 align:start position:0% also are normally configured with the 22:46:01.320 --> 22:46:03.590 align:start position:0% also are normally configured with the default<22:46:01.552> gateway<22:46:02.040> but<22:46:03.000> you<22:46:03.120> should<22:46:03.296> be<22:46:03.424> able 22:46:03.590 --> 22:46:03.600 align:start position:0% default gateway but you should be able 22:46:03.600 --> 22:46:07.366 align:start position:0% default gateway but you should be able to<22:46:03.720> Ping<22:46:04.144> from<22:46:04.800> the<22:46:05.760> um<22:46:05.760> switch<22:46:06.176> whatever<22:46:07.080> the 22:46:07.366 --> 22:46:07.376 align:start position:0% to Ping from the um switch whatever the 22:46:07.376 --> 22:46:09.350 align:start position:0% to Ping from the um switch whatever the VLAN<22:46:07.744> is<22:46:07.976> to<22:46:08.160> the<22:46:08.336> default<22:46:08.640> gateway<22:46:09.056> when 22:46:09.350 --> 22:46:09.360 align:start position:0% VLAN is to the default gateway when 22:46:09.360 --> 22:46:10.910 align:start position:0% VLAN is to the default gateway when you're<22:46:09.536> installing<22:46:09.960> it<22:46:10.192> just<22:46:10.376> to<22:46:10.552> check<22:46:10.680> it's 22:46:10.910 --> 22:46:10.920 align:start position:0% you're installing it just to check it's 22:46:10.920 --> 22:46:12.350 align:start position:0% you're installing it just to check it's working 22:46:12.350 --> 22:46:12.360 align:start position:0% working 22:46:12.360 --> 22:46:14.566 align:start position:0% working so<22:46:12.960> the<22:46:13.192> IP<22:46:13.552> address<22:46:13.800> assigned<22:46:14.336> to<22:46:14.400> the 22:46:14.566 --> 22:46:14.576 align:start position:0% so the IP address assigned to the 22:46:14.576 --> 22:46:16.182 align:start position:0% so the IP address assigned to the default<22:46:14.824> gateway<22:46:15.176> may<22:46:15.480> be<22:46:15.600> correct<22:46:15.832> and<22:46:16.016> you 22:46:16.182 --> 22:46:16.192 align:start position:0% default gateway may be correct and you 22:46:16.192 --> 22:46:19.006 align:start position:0% default gateway may be correct and you can<22:46:16.320> check<22:46:16.552> your<22:46:17.160> IP<22:46:17.936> configuration<22:46:18.536> settings 22:46:19.006 --> 22:46:19.016 align:start position:0% can check your IP configuration settings 22:46:19.016 --> 22:46:22.006 align:start position:0% can check your IP configuration settings on<22:46:19.800> your<22:46:19.976> windows<22:46:20.512> or<22:46:20.936> Linux 22:46:22.006 --> 22:46:22.016 align:start position:0% on your windows or Linux 22:46:22.016 --> 22:46:24.046 align:start position:0% on your windows or Linux um<22:46:22.080> device 22:46:24.046 --> 22:46:24.056 align:start position:0% um device 22:46:24.056 --> 22:46:26.094 align:start position:0% um device obviously<22:46:24.720> to<22:46:24.832> fix<22:46:25.080> it<22:46:25.256> put<22:46:25.440> in<22:46:25.552> the<22:46:25.744> correct 22:46:26.094 --> 22:46:26.104 align:start position:0% obviously to fix it put in the correct 22:46:26.104 --> 22:46:27.886 align:start position:0% obviously to fix it put in the correct default<22:46:26.576> gateway<22:46:26.936> and<22:46:27.240> make<22:46:27.360> sure<22:46:27.480> nothing's 22:46:27.886 --> 22:46:27.896 align:start position:0% default gateway and make sure nothing's 22:46:27.896 --> 22:46:29.990 align:start position:0% default gateway and make sure nothing's changed<22:46:28.192> on<22:46:28.320> the<22:46:28.496> default<22:46:28.800> gateway 22:46:29.990 --> 22:46:30.000 align:start position:0% changed on the default gateway 22:46:30.000 --> 22:46:33.134 align:start position:0% changed on the default gateway broadcast<22:46:30.536> storms<22:46:31.256> users<22:46:31.856> can<22:46:32.160> experience<22:46:32.696> a 22:46:33.134 --> 22:46:33.144 align:start position:0% broadcast storms users can experience a 22:46:33.144 --> 22:46:36.350 align:start position:0% broadcast storms users can experience a degradation<22:46:34.144> and<22:46:34.440> network<22:46:34.616> performance<22:46:35.360> and 22:46:36.350 --> 22:46:36.360 align:start position:0% degradation and network performance and 22:46:36.360 --> 22:46:37.734 align:start position:0% degradation and network performance and it<22:46:36.480> can<22:46:36.600> actually<22:46:36.720> bring<22:46:37.016> down<22:46:37.192> the<22:46:37.440> entire 22:46:37.734 --> 22:46:37.744 align:start position:0% it can actually bring down the entire 22:46:37.744 --> 22:46:39.350 align:start position:0% it can actually bring down the entire network 22:46:39.350 --> 22:46:39.360 align:start position:0% network 22:46:39.360 --> 22:46:41.270 align:start position:0% network so<22:46:39.784> the<22:46:39.896> network<22:46:40.080> is<22:46:40.376> flooded<22:46:40.800> with<22:46:40.976> broadcast 22:46:41.270 --> 22:46:41.280 align:start position:0% so the network is flooded with broadcast 22:46:41.280 --> 22:46:44.686 align:start position:0% so the network is flooded with broadcast traffic<22:46:41.696> could<22:46:42.600> be<22:46:42.832> a<22:46:43.320> switching<22:46:43.856> Loop<22:46:44.216> it 22:46:44.686 --> 22:46:44.696 align:start position:0% traffic could be a switching Loop it 22:46:44.696 --> 22:46:46.966 align:start position:0% traffic could be a switching Loop it could<22:46:44.872> also<22:46:45.240> be<22:46:45.480> a<22:46:45.832> faulty<22:46:46.256> network<22:46:46.440> card 22:46:46.966 --> 22:46:46.976 align:start position:0% could also be a faulty network card 22:46:46.976 --> 22:46:49.542 align:start position:0% could also be a faulty network card that's<22:46:47.760> just<22:46:48.056> sending<22:46:48.784> a<22:46:48.960> huge<22:46:49.192> amount<22:46:49.440> of 22:46:49.542 --> 22:46:49.552 align:start position:0% that's just sending a huge amount of 22:46:49.552 --> 22:46:50.862 align:start position:0% that's just sending a huge amount of traffic<22:46:49.744> out 22:46:50.862 --> 22:46:50.872 align:start position:0% traffic out 22:46:50.872 --> 22:46:52.846 align:start position:0% traffic out and<22:46:51.536> you<22:46:51.720> could<22:46:51.896> troubleshoot<22:46:52.496> it<22:46:52.616> with 22:46:52.846 --> 22:46:52.856 align:start position:0% and you could troubleshoot it with 22:46:52.856 --> 22:46:55.542 align:start position:0% and you could troubleshoot it with Wireshark<22:46:53.400> and<22:46:53.760> other<22:46:53.936> programs<22:46:54.600> and<22:46:55.144> Cisco 22:46:55.542 --> 22:46:55.552 align:start position:0% Wireshark and other programs and Cisco 22:46:55.552 --> 22:46:58.486 align:start position:0% Wireshark and other programs and Cisco provide<22:46:56.400> um<22:46:56.400> a<22:46:56.696> whole<22:46:56.824> raft<22:46:57.000> of<22:46:57.240> tools 22:46:58.486 --> 22:46:58.496 align:start position:0% provide um a whole raft of tools 22:46:58.496 --> 22:47:00.414 align:start position:0% provide um a whole raft of tools uh<22:46:59.040> obviously<22:46:59.464> having<22:46:59.640> spanning<22:47:00.120> training 22:47:00.414 --> 22:47:00.424 align:start position:0% uh obviously having spanning training 22:47:00.424 --> 22:47:02.206 align:start position:0% uh obviously having spanning training switches<22:47:01.016> will<22:47:01.320> help<22:47:01.552> solve<22:47:01.976> the<22:47:02.040> problem 22:47:02.206 --> 22:47:02.216 align:start position:0% switches will help solve the problem 22:47:02.216 --> 22:47:04.846 align:start position:0% switches will help solve the problem it's<22:47:03.056> normally<22:47:03.360> there<22:47:03.656> it's<22:47:04.440> normally<22:47:04.680> on 22:47:04.846 --> 22:47:04.856 align:start position:0% it's normally there it's normally on 22:47:04.856 --> 22:47:06.350 align:start position:0% it's normally there it's normally on their<22:47:04.976> body<22:47:05.104> faults 22:47:06.350 --> 22:47:06.360 align:start position:0% their body faults 22:47:06.360 --> 22:47:09.046 align:start position:0% their body faults duplicate<22:47:07.080> IP<22:47:07.504> sometimes<22:47:08.280> somebody<22:47:08.640> doesn't 22:47:09.046 --> 22:47:09.056 align:start position:0% duplicate IP sometimes somebody doesn't 22:47:09.056 --> 22:47:11.502 align:start position:0% duplicate IP sometimes somebody doesn't release<22:47:09.360> their<22:47:09.784> DHCP<22:47:10.496> address<22:47:10.800> it's<22:47:11.160> been<22:47:11.336> on 22:47:11.502 --> 22:47:11.512 align:start position:0% release their DHCP address it's been on 22:47:11.512 --> 22:47:13.326 align:start position:0% release their DHCP address it's been on there<22:47:11.696> too<22:47:11.936> long<22:47:12.120> or<22:47:12.424> stuck<22:47:12.656> for<22:47:12.832> some<22:47:13.080> reason 22:47:13.326 --> 22:47:13.336 align:start position:0% there too long or stuck for some reason 22:47:13.336 --> 22:47:16.430 align:start position:0% there too long or stuck for some reason or<22:47:14.336> I've<22:47:14.640> seen<22:47:14.872> people<22:47:15.296> manually<22:47:15.784> configure 22:47:16.430 --> 22:47:16.440 align:start position:0% or I've seen people manually configure 22:47:16.440 --> 22:47:18.886 align:start position:0% or I've seen people manually configure an<22:47:16.976> IP<22:47:17.280> address<22:47:17.464> on<22:47:17.824> their<22:47:18.000> system<22:47:18.240> for<22:47:18.720> some 22:47:18.886 --> 22:47:18.896 align:start position:0% an IP address on their system for some 22:47:18.896 --> 22:47:20.270 align:start position:0% an IP address on their system for some crazy<22:47:19.144> reason 22:47:20.270 --> 22:47:20.280 align:start position:0% crazy reason 22:47:20.280 --> 22:47:22.134 align:start position:0% crazy reason I<22:47:20.760> don't<22:47:20.872> know<22:47:21.000> why<22:47:21.120> they<22:47:21.360> did<22:47:21.536> it<22:47:21.656> and<22:47:21.960> it's 22:47:22.134 --> 22:47:22.144 align:start position:0% I don't know why they did it and it's 22:47:22.144 --> 22:47:25.246 align:start position:0% I don't know why they did it and it's caused<22:47:22.680> a<22:47:23.104> mismatch 22:47:25.246 --> 22:47:25.256 align:start position:0% caused a mismatch 22:47:25.256 --> 22:47:27.414 align:start position:0% caused a mismatch to<22:47:25.856> avoid<22:47:26.104> it<22:47:26.336> you<22:47:26.640> can<22:47:26.696> change<22:47:26.872> the<22:47:27.120> IP 22:47:27.414 --> 22:47:27.424 align:start position:0% to avoid it you can change the IP 22:47:27.424 --> 22:47:30.822 align:start position:0% to avoid it you can change the IP address<22:47:27.656> of<22:47:28.016> both<22:47:28.256> or<22:47:28.976> one<22:47:29.464> of<22:47:29.576> the<22:47:29.640> hosts<22:47:30.120> and 22:47:30.822 --> 22:47:30.832 align:start position:0% address of both or one of the hosts and 22:47:30.832 --> 22:47:31.910 align:start position:0% address of both or one of the hosts and normally 22:47:31.910 --> 22:47:31.920 align:start position:0% normally 22:47:31.920 --> 22:47:34.430 align:start position:0% normally um<22:47:31.976> asking<22:47:32.400> for<22:47:32.576> it<22:47:32.760> to<22:47:32.872> be<22:47:33.000> provided<22:47:33.360> by<22:47:33.656> DHCP 22:47:34.430 --> 22:47:34.440 align:start position:0% um asking for it to be provided by DHCP 22:47:34.440 --> 22:47:36.886 align:start position:0% um asking for it to be provided by DHCP which<22:47:34.856> most<22:47:35.336> devices<22:47:35.760> use 22:47:36.886 --> 22:47:36.896 align:start position:0% which most devices use 22:47:36.896 --> 22:47:39.774 align:start position:0% which most devices use speed<22:47:37.440> and<22:47:37.616> duplex<22:47:38.040> mismatch<22:47:38.760> you<22:47:39.600> can<22:47:39.656> have 22:47:39.774 --> 22:47:39.784 align:start position:0% speed and duplex mismatch you can have 22:47:39.784 --> 22:47:42.822 align:start position:0% speed and duplex mismatch you can have on<22:47:39.960> your<22:47:40.144> host<22:47:40.440> or<22:47:41.040> on<22:47:41.336> a<22:47:41.576> switch<22:47:41.824> in<22:47:42.360> fact<22:47:42.536> on<22:47:42.720> a 22:47:42.822 --> 22:47:42.832 align:start position:0% on your host or on a switch in fact on a 22:47:42.832 --> 22:47:44.150 align:start position:0% on your host or on a switch in fact on a router<22:47:43.192> as<22:47:43.320> well 22:47:44.150 --> 22:47:44.160 align:start position:0% router as well 22:47:44.160 --> 22:47:46.430 align:start position:0% router as well you'll<22:47:44.576> have<22:47:44.760> slow<22:47:45.120> or<22:47:45.656> degraded<22:47:46.144> Network 22:47:46.430 --> 22:47:46.440 align:start position:0% you'll have slow or degraded Network 22:47:46.440 --> 22:47:48.646 align:start position:0% you'll have slow or degraded Network performance<22:47:47.104> or<22:47:47.576> no<22:47:47.824> connection<22:47:48.120> no 22:47:48.646 --> 22:47:48.656 align:start position:0% performance or no connection no 22:47:48.656 --> 22:47:50.566 align:start position:0% performance or no connection no connectivity<22:47:49.144> at<22:47:49.552> all 22:47:50.566 --> 22:47:50.576 align:start position:0% connectivity at all 22:47:50.576 --> 22:47:52.486 align:start position:0% connectivity at all and<22:47:51.176> you<22:47:51.424> could<22:47:51.536> have<22:47:51.656> different<22:47:51.896> port<22:47:52.256> and 22:47:52.486 --> 22:47:52.496 align:start position:0% and you could have different port and 22:47:52.496 --> 22:47:55.134 align:start position:0% and you could have different port and speed<22:47:52.744> settings<22:47:53.040> you<22:47:53.512> could<22:47:53.640> have<22:47:53.760> 100<22:47:54.240> full 22:47:55.134 --> 22:47:55.144 align:start position:0% speed settings you could have 100 full 22:47:55.144 --> 22:47:58.670 align:start position:0% speed settings you could have 100 full duplex<22:47:55.616> on<22:47:55.976> one<22:47:56.216> side<22:47:56.480> and<22:47:57.480> 10<22:47:58.016> Meg<22:47:58.496> half 22:47:58.670 --> 22:47:58.680 align:start position:0% duplex on one side and 10 Meg half 22:47:58.680 --> 22:48:00.590 align:start position:0% duplex on one side and 10 Meg half duplex<22:47:59.160> on<22:47:59.400> the<22:47:59.512> other<22:47:59.576> side<22:47:59.824> and<22:48:00.536> you're 22:48:00.590 --> 22:48:00.600 align:start position:0% duplex on the other side and you're 22:48:00.600 --> 22:48:02.206 align:start position:0% duplex on the other side and you're going<22:48:00.784> to<22:48:00.832> have<22:48:00.960> problems<22:48:01.504> normally<22:48:01.920> you'll 22:48:02.206 --> 22:48:02.216 align:start position:0% going to have problems normally you'll 22:48:02.216 --> 22:48:05.326 align:start position:0% going to have problems normally you'll see<22:48:02.400> issues<22:48:03.056> on<22:48:03.296> the<22:48:03.480> LED<22:48:03.856> of<22:48:04.856> the<22:48:05.040> network 22:48:05.326 --> 22:48:05.336 align:start position:0% see issues on the LED of the network 22:48:05.336 --> 22:48:08.390 align:start position:0% see issues on the LED of the network card<22:48:05.696> as<22:48:05.936> well<22:48:06.120> and<22:48:06.536> you<22:48:06.656> could<22:48:06.832> have<22:48:07.440> um 22:48:08.390 --> 22:48:08.400 align:start position:0% card as well and you could have um 22:48:08.400 --> 22:48:10.734 align:start position:0% card as well and you could have um error<22:48:09.176> messages<22:48:09.296> coming<22:48:09.720> up<22:48:09.896> on<22:48:10.080> your<22:48:10.320> router 22:48:10.734 --> 22:48:10.744 align:start position:0% error messages coming up on your router 22:48:10.744 --> 22:48:15.774 align:start position:0% error messages coming up on your router or<22:48:10.920> switch<22:48:11.424> console<22:48:12.424> and<22:48:13.016> on<22:48:13.256> your<22:48:13.552> PC 22:48:15.774 --> 22:48:15.784 align:start position:0% or switch console and on your PC 22:48:15.784 --> 22:48:17.926 align:start position:0% or switch console and on your PC so<22:48:16.144> common<22:48:16.376> causes<22:48:16.800> when<22:48:16.976> negotiation<22:48:17.640> is 22:48:17.926 --> 22:48:17.936 align:start position:0% so common causes when negotiation is 22:48:17.936 --> 22:48:19.846 align:start position:0% so common causes when negotiation is enabled<22:48:18.360> on<22:48:18.480> one<22:48:18.656> side<22:48:18.832> and<22:48:19.144> disabled<22:48:19.616> on<22:48:19.744> the 22:48:19.846 --> 22:48:19.856 align:start position:0% enabled on one side and disabled on the 22:48:19.856 --> 22:48:22.246 align:start position:0% enabled on one side and disabled on the other 22:48:22.246 --> 22:48:22.256 align:start position:0% 22:48:22.256 --> 22:48:24.414 align:start position:0% it's<22:48:22.800> reliable<22:48:23.576> to<22:48:23.760> manually<22:48:24.000> configure 22:48:24.414 --> 22:48:24.424 align:start position:0% it's reliable to manually configure 22:48:24.424 --> 22:48:26.150 align:start position:0% it's reliable to manually configure network<22:48:24.600> speed<22:48:24.960> and<22:48:25.144> duplex<22:48:25.504> settings<22:48:25.800> for 22:48:26.150 --> 22:48:26.160 align:start position:0% network speed and duplex settings for 22:48:26.160 --> 22:48:28.966 align:start position:0% network speed and duplex settings for the<22:48:26.336> server<22:48:26.640> and<22:48:26.824> other<22:48:27.000> critical<22:48:27.480> links<22:48:28.016> now 22:48:28.966 --> 22:48:28.976 align:start position:0% the server and other critical links now 22:48:28.976 --> 22:48:31.542 align:start position:0% the server and other critical links now you<22:48:29.400> may<22:48:29.512> use<22:48:29.760> Auto<22:48:30.016> negotiation<22:48:31.016> the 22:48:31.542 --> 22:48:31.552 align:start position:0% you may use Auto negotiation the 22:48:31.552 --> 22:48:33.414 align:start position:0% you may use Auto negotiation the networks<22:48:31.920> I've<22:48:32.104> worked<22:48:32.464> out<22:48:32.576> they<22:48:33.000> they 22:48:33.414 --> 22:48:33.424 align:start position:0% networks I've worked out they they 22:48:33.424 --> 22:48:35.030 align:start position:0% networks I've worked out they they generally<22:48:33.832> didn't 22:48:35.030 --> 22:48:35.040 align:start position:0% generally didn't 22:48:35.040 --> 22:48:39.110 align:start position:0% generally didn't they<22:48:35.576> had<22:48:36.144> hard-coded<22:48:37.280> and<22:48:38.280> speed<22:48:38.640> and<22:48:38.760> duplex 22:48:39.110 --> 22:48:39.120 align:start position:0% they had hard-coded and speed and duplex 22:48:39.120 --> 22:48:41.150 align:start position:0% they had hard-coded and speed and duplex settings<22:48:39.424> for<22:48:39.784> all<22:48:39.896> devices 22:48:41.150 --> 22:48:41.160 align:start position:0% settings for all devices 22:48:41.160 --> 22:48:43.310 align:start position:0% settings for all devices uh<22:48:41.640> incorrect<22:48:42.120> VLAN<22:48:42.536> if<22:48:42.832> you're<22:48:42.960> on<22:48:43.080> the<22:48:43.192> wrong 22:48:43.310 --> 22:48:43.320 align:start position:0% uh incorrect VLAN if you're on the wrong 22:48:43.320 --> 22:48:45.886 align:start position:0% uh incorrect VLAN if you're on the wrong VLAN<22:48:43.800> you<22:48:43.976> may<22:48:44.160> have<22:48:44.336> no<22:48:44.640> connectivity<22:48:45.240> or<22:48:45.720> not 22:48:45.886 --> 22:48:45.896 align:start position:0% VLAN you may have no connectivity or not 22:48:45.896 --> 22:48:48.350 align:start position:0% VLAN you may have no connectivity or not be<22:48:46.016> able<22:48:46.144> to<22:48:46.256> access<22:48:46.496> the<22:48:46.920> resources<22:48:47.872> that<22:48:48.176> you 22:48:48.350 --> 22:48:48.360 align:start position:0% be able to access the resources that you 22:48:48.360 --> 22:48:51.310 align:start position:0% be able to access the resources that you need<22:48:48.536> because<22:48:48.960> it's<22:48:49.256> in<22:48:49.440> a<22:48:49.552> different<22:48:49.680> VLAN 22:48:51.310 --> 22:48:51.320 align:start position:0% need because it's in a different VLAN 22:48:51.320 --> 22:48:53.502 align:start position:0% need because it's in a different VLAN configuring<22:48:52.320> devices<22:48:52.616> is<22:48:53.040> normally<22:48:53.336> the 22:48:53.502 --> 22:48:53.512 align:start position:0% configuring devices is normally the 22:48:53.512 --> 22:48:55.606 align:start position:0% configuring devices is normally the switch<22:48:53.696> Port<22:48:54.056> the<22:48:54.480> end<22:48:54.536> devices<22:48:54.896> don't<22:48:55.320> have 22:48:55.606 --> 22:48:55.616 align:start position:0% switch Port the end devices don't have 22:48:55.616 --> 22:48:58.670 align:start position:0% switch Port the end devices don't have VLAN<22:48:56.400> settings<22:48:56.936> as<22:48:57.360> a<22:48:57.600> general<22:48:57.720> rule<22:48:58.192> you 22:48:58.670 --> 22:48:58.680 align:start position:0% VLAN settings as a general rule you 22:48:58.680 --> 22:49:00.774 align:start position:0% VLAN settings as a general rule you would<22:48:58.800> configure<22:48:59.160> the<22:48:59.280> switch<22:48:59.512> port<22:48:59.872> to<22:49:00.480> be<22:49:00.656> in 22:49:00.774 --> 22:49:00.784 align:start position:0% would configure the switch port to be in 22:49:00.784 --> 22:49:02.926 align:start position:0% would configure the switch port to be in the<22:49:00.896> corrective<22:49:01.192> VLAN<22:49:01.680> and<22:49:02.512> make<22:49:02.696> sure<22:49:02.824> it's 22:49:02.926 --> 22:49:02.936 align:start position:0% the corrective VLAN and make sure it's 22:49:02.936 --> 22:49:04.966 align:start position:0% the corrective VLAN and make sure it's not<22:49:03.120> blocked<22:49:03.600> that<22:49:03.832> VLAN<22:49:04.256> is<22:49:04.440> unblocked<22:49:04.800> for 22:49:04.966 --> 22:49:04.976 align:start position:0% not blocked that VLAN is unblocked for 22:49:04.976 --> 22:49:07.246 align:start position:0% not blocked that VLAN is unblocked for security<22:49:05.104> reasons<22:49:05.824> on<22:49:06.480> the<22:49:06.600> switch<22:49:06.784> trunk 22:49:07.246 --> 22:49:07.256 align:start position:0% security reasons on the switch trunk 22:49:07.256 --> 22:49:08.094 align:start position:0% security reasons on the switch trunk port 22:49:08.094 --> 22:49:08.104 align:start position:0% port 22:49:08.104 --> 22:49:10.606 align:start position:0% port Hardware<22:49:08.696> failure<22:49:09.360> this<22:49:09.720> is<22:49:09.832> a<22:49:10.016> whole<22:49:10.144> raft<22:49:10.440> of 22:49:10.606 --> 22:49:10.616 align:start position:0% Hardware failure this is a whole raft of 22:49:10.616 --> 22:49:11.814 align:start position:0% Hardware failure this is a whole raft of things<22:49:10.856> that<22:49:11.160> could<22:49:11.336> go<22:49:11.576> wrong 22:49:11.814 --> 22:49:11.824 align:start position:0% things that could go wrong 22:49:11.824 --> 22:49:14.750 align:start position:0% things that could go wrong intermittently<22:49:12.656> or<22:49:12.960> just<22:49:13.192> completely<22:49:13.616> break 22:49:14.750 --> 22:49:14.760 align:start position:0% intermittently or just completely break 22:49:14.760 --> 22:49:16.486 align:start position:0% intermittently or just completely break and<22:49:15.176> one<22:49:15.360> of<22:49:15.536> the<22:49:15.536> components<22:49:16.080> of<22:49:16.256> a<22:49:16.376> device 22:49:16.486 --> 22:49:16.496 align:start position:0% and one of the components of a device 22:49:16.496 --> 22:49:19.134 align:start position:0% and one of the components of a device may<22:49:16.856> have<22:49:17.040> failed<22:49:17.336> or<22:49:17.464> an<22:49:17.640> entire<22:49:17.936> device<22:49:18.176> you 22:49:19.134 --> 22:49:19.144 align:start position:0% may have failed or an entire device you 22:49:19.144 --> 22:49:20.750 align:start position:0% may have failed or an entire device you identify<22:49:19.616> it<22:49:19.800> with<22:49:19.976> your<22:49:20.104> troubleshooting 22:49:20.750 --> 22:49:20.760 align:start position:0% identify it with your troubleshooting 22:49:20.760 --> 22:49:23.862 align:start position:0% identify it with your troubleshooting methodology<22:49:21.440> and<22:49:22.440> you<22:49:22.680> can<22:49:22.800> replace<22:49:23.336> the 22:49:23.862 --> 22:49:23.872 align:start position:0% methodology and you can replace the 22:49:23.872 --> 22:49:27.486 align:start position:0% methodology and you can replace the faulty<22:49:24.296> device<22:49:24.600> or<22:49:25.016> the<22:49:25.144> faulty<22:49:25.552> interface 22:49:27.486 --> 22:49:27.496 align:start position:0% faulty device or the faulty interface 22:49:27.496 --> 22:49:30.110 align:start position:0% faulty device or the faulty interface DHCP<22:49:28.496> if<22:49:28.920> this<22:49:29.040> server<22:49:29.336> has<22:49:29.464> been<22:49:29.576> incorrectly 22:49:30.110 --> 22:49:30.120 align:start position:0% DHCP if this server has been incorrectly 22:49:30.120 --> 22:49:31.966 align:start position:0% DHCP if this server has been incorrectly configured 22:49:31.966 --> 22:49:31.976 align:start position:0% configured 22:49:31.976 --> 22:49:33.590 align:start position:0% configured then<22:49:32.696> you're<22:49:32.872> obviously<22:49:33.240> going<22:49:33.360> to<22:49:33.480> have 22:49:33.590 --> 22:49:33.600 align:start position:0% then you're obviously going to have 22:49:33.600 --> 22:49:35.206 align:start position:0% then you're obviously going to have issues<22:49:33.960> you<22:49:34.256> could<22:49:34.376> have<22:49:34.552> one<22:49:34.920> person 22:49:35.206 --> 22:49:35.216 align:start position:0% issues you could have one person 22:49:35.216 --> 22:49:37.366 align:start position:0% issues you could have one person affected<22:49:35.872> or<22:49:36.120> the<22:49:36.296> entire 22:49:37.366 --> 22:49:37.376 align:start position:0% affected or the entire 22:49:37.376 --> 22:49:40.246 align:start position:0% affected or the entire um<22:49:37.440> organization<22:49:38.424> you<22:49:39.424> could<22:49:39.480> exhaust<22:49:39.896> all<22:49:40.144> of 22:49:40.246 --> 22:49:40.256 align:start position:0% um organization you could exhaust all of 22:49:40.256 --> 22:49:43.790 align:start position:0% um organization you could exhaust all of the<22:49:40.376> IP<22:49:40.680> addresses<22:49:41.160> on<22:49:41.464> your<22:49:41.576> DHCP<22:49:42.424> pool<22:49:42.800> you 22:49:43.790 --> 22:49:43.800 align:start position:0% the IP addresses on your DHCP pool you 22:49:43.800 --> 22:49:45.774 align:start position:0% the IP addresses on your DHCP pool you could<22:49:43.920> also<22:49:44.280> indicate<22:49:45.120> that<22:49:45.240> you've<22:49:45.480> got<22:49:45.600> some 22:49:45.774 --> 22:49:45.784 align:start position:0% could also indicate that you've got some 22:49:45.784 --> 22:49:48.822 align:start position:0% could also indicate that you've got some sort<22:49:45.960> of<22:49:46.080> attack<22:49:46.320> going<22:49:46.920> on<22:49:47.216> some<22:49:47.824> Rogue<22:49:48.176> DHCP 22:49:48.822 --> 22:49:48.832 align:start position:0% sort of attack going on some Rogue DHCP 22:49:48.832 --> 22:49:52.486 align:start position:0% sort of attack going on some Rogue DHCP server<22:49:49.376> or<22:49:50.280> the<22:49:50.576> devices<22:49:50.872> causing<22:49:51.480> issues 22:49:52.486 --> 22:49:52.496 align:start position:0% server or the devices causing issues 22:49:52.496 --> 22:49:55.966 align:start position:0% server or the devices causing issues we've<22:49:53.160> addressed<22:49:53.336> that<22:49:53.576> elsewhere 22:49:55.966 --> 22:49:55.976 align:start position:0% we've addressed that elsewhere 22:49:55.976 --> 22:49:59.094 align:start position:0% we've addressed that elsewhere DNS<22:49:56.824> obviously<22:49:57.296> for<22:49:57.832> DNS<22:49:58.256> lookups<22:49:58.800> you<22:49:58.920> need 22:49:59.094 --> 22:49:59.104 align:start position:0% DNS obviously for DNS lookups you need 22:49:59.104 --> 22:50:01.846 align:start position:0% DNS obviously for DNS lookups you need to<22:49:59.216> have<22:49:59.336> the<22:49:59.576> correct<22:49:59.872> device<22:50:00.480> configured 22:50:01.846 --> 22:50:01.856 align:start position:0% to have the correct device configured 22:50:01.856 --> 22:50:03.526 align:start position:0% to have the correct device configured a<22:50:02.336> host<22:50:02.512> can<22:50:02.760> be<22:50:02.872> configured<22:50:03.176> with<22:50:03.296> the<22:50:03.480> wrong 22:50:03.526 --> 22:50:03.536 align:start position:0% a host can be configured with the wrong 22:50:03.536 --> 22:50:05.814 align:start position:0% a host can be configured with the wrong DNS<22:50:04.016> server<22:50:04.440> either<22:50:04.976> because<22:50:05.280> you've 22:50:05.814 --> 22:50:05.824 align:start position:0% DNS server either because you've 22:50:05.824 --> 22:50:08.454 align:start position:0% DNS server either because you've misconfigured<22:50:06.536> the<22:50:06.656> DHCP<22:50:07.376> server<22:50:07.920> or 22:50:08.454 --> 22:50:08.464 align:start position:0% misconfigured the DHCP server or 22:50:08.464 --> 22:50:10.246 align:start position:0% misconfigured the DHCP server or somebody's<22:50:08.936> hard<22:50:09.176> set<22:50:09.424> it 22:50:10.246 --> 22:50:10.256 align:start position:0% somebody's hard set it 22:50:10.256 --> 22:50:12.414 align:start position:0% somebody's hard set it so<22:50:10.856> ensure<22:50:11.280> the<22:50:11.464> host<22:50:11.640> is<22:50:11.872> configured<22:50:12.296> with 22:50:12.414 --> 22:50:12.424 align:start position:0% so ensure the host is configured with 22:50:12.424 --> 22:50:15.166 align:start position:0% so ensure the host is configured with the<22:50:12.600> correct<22:50:12.784> IP<22:50:13.144> address<22:50:13.320> of<22:50:13.616> the<22:50:13.800> DNS<22:50:14.216> server 22:50:15.166 --> 22:50:15.176 align:start position:0% the correct IP address of the DNS server 22:50:15.176 --> 22:50:17.566 align:start position:0% the correct IP address of the DNS server on<22:50:15.656> Windows<22:50:16.016> you<22:50:16.256> could<22:50:16.376> issue<22:50:16.680> ipconfig 22:50:17.566 --> 22:50:17.576 align:start position:0% on Windows you could issue ipconfig 22:50:17.576 --> 22:50:20.150 align:start position:0% on Windows you could issue ipconfig space<22:50:17.872> forward<22:50:18.240> slash<22:50:18.720> all<22:50:19.016> and<22:50:19.680> it<22:50:19.800> will<22:50:19.976> show 22:50:20.150 --> 22:50:20.160 align:start position:0% space forward slash all and it will show 22:50:20.160 --> 22:50:22.734 align:start position:0% space forward slash all and it will show you<22:50:20.280> your<22:50:20.400> DHCP<22:50:21.240> server<22:50:21.656> address<22:50:21.832> your<22:50:22.320> DNS 22:50:22.734 --> 22:50:22.744 align:start position:0% you your DHCP server address your DNS 22:50:22.744 --> 22:50:24.046 align:start position:0% you your DHCP server address your DNS server<22:50:23.104> address 22:50:24.046 --> 22:50:24.056 align:start position:0% server address 22:50:24.056 --> 22:50:26.630 align:start position:0% server address IP<22:50:24.832> address<22:50:25.016> and<22:50:25.440> a<22:50:25.680> few<22:50:25.800> other 22:50:26.630 --> 22:50:26.640 align:start position:0% IP address and a few other 22:50:26.640 --> 22:50:27.950 align:start position:0% IP address and a few other um settings<22:50:26.872> that<22:50:27.296> you<22:50:27.424> may<22:50:27.600> find 22:50:27.950 --> 22:50:27.960 align:start position:0% um settings that you may find 22:50:27.960 --> 22:50:29.814 align:start position:0% um settings that you may find interesting 22:50:29.814 --> 22:50:29.824 align:start position:0% interesting 22:50:29.824 --> 22:50:31.966 align:start position:0% interesting if<22:50:30.424> your<22:50:30.656> interface<22:50:31.080> is<22:50:31.320> incorrectly 22:50:31.966 --> 22:50:31.976 align:start position:0% if your interface is incorrectly 22:50:31.976 --> 22:50:34.366 align:start position:0% if your interface is incorrectly configured<22:50:32.576> you'll<22:50:33.000> have<22:50:33.176> no<22:50:33.784> connectivity 22:50:34.366 --> 22:50:34.376 align:start position:0% configured you'll have no connectivity 22:50:34.376 --> 22:50:35.990 align:start position:0% configured you'll have no connectivity or<22:50:34.800> intermittent 22:50:35.990 --> 22:50:36.000 align:start position:0% or intermittent 22:50:36.000 --> 22:50:37.846 align:start position:0% or intermittent you<22:50:36.296> could<22:50:36.360> have<22:50:36.480> the<22:50:36.720> source<22:50:37.504> um<22:50:37.552> or 22:50:37.846 --> 22:50:37.856 align:start position:0% you could have the source um or 22:50:37.856 --> 22:50:39.950 align:start position:0% you could have the source um or destination<22:50:38.280> device<22:50:38.696> may<22:50:39.120> have<22:50:39.296> an<22:50:39.480> incorrect 22:50:39.950 --> 22:50:39.960 align:start position:0% destination device may have an incorrect 22:50:39.960 --> 22:50:43.366 align:start position:0% destination device may have an incorrect IP<22:50:40.800> address<22:50:40.976> or<22:50:41.216> subnet<22:50:41.696> so<22:50:42.296> if<22:50:42.424> if<22:50:42.720> for<22:50:43.192> some 22:50:43.366 --> 22:50:43.376 align:start position:0% IP address or subnet so if if for some 22:50:43.376 --> 22:50:45.230 align:start position:0% IP address or subnet so if if for some reason<22:50:43.552> you'll 22:50:45.230 --> 22:50:45.240 align:start position:0% reason you'll 22:50:45.240 --> 22:50:47.150 align:start position:0% reason you'll um router<22:50:45.656> interfaces<22:50:46.256> on<22:50:46.496> either<22:50:46.680> end<22:50:46.976> have 22:50:47.150 --> 22:50:47.160 align:start position:0% um router interfaces on either end have 22:50:47.160 --> 22:50:48.886 align:start position:0% um router interfaces on either end have been<22:50:47.280> put<22:50:47.464> in<22:50:47.640> different<22:50:47.824> subnets<22:50:48.296> then 22:50:48.886 --> 22:50:48.896 align:start position:0% been put in different subnets then 22:50:48.896 --> 22:50:50.326 align:start position:0% been put in different subnets then you're<22:50:49.080> not<22:50:49.192> going<22:50:49.376> to<22:50:49.552> get<22:50:49.680> you're<22:50:50.040> not<22:50:50.160> going 22:50:50.326 --> 22:50:50.336 align:start position:0% you're not going to get you're not going 22:50:50.336 --> 22:50:52.670 align:start position:0% you're not going to get you're not going to<22:50:50.464> get<22:50:50.576> connectivity 22:50:52.670 --> 22:50:52.680 align:start position:0% to get connectivity 22:50:52.680 --> 22:50:56.150 align:start position:0% to get connectivity check<22:50:53.160> the<22:50:53.400> ipn<22:50:53.824> subnet<22:50:54.600> mask<22:50:54.784> of<22:50:55.192> both<22:50:55.504> source 22:50:56.150 --> 22:50:56.160 align:start position:0% check the ipn subnet mask of both source 22:50:56.160 --> 22:50:57.470 align:start position:0% check the ipn subnet mask of both source and<22:50:56.216> destination<22:50:56.640> and<22:50:56.936> check<22:50:57.120> it<22:50:57.296> against 22:50:57.470 --> 22:50:57.480 align:start position:0% and destination and check it against 22:50:57.480 --> 22:51:00.350 align:start position:0% and destination and check it against your<22:50:57.896> design<22:50:58.192> documents 22:51:00.350 --> 22:51:00.360 align:start position:0% your design documents 22:51:00.360 --> 22:51:02.862 align:start position:0% your design documents cable<22:51:01.016> placement<22:51:01.552> you<22:51:02.160> could<22:51:02.336> have<22:51:02.512> slow 22:51:02.862 --> 22:51:02.872 align:start position:0% cable placement you could have slow 22:51:02.872 --> 22:51:04.246 align:start position:0% cable placement you could have slow performance 22:51:04.246 --> 22:51:04.256 align:start position:0% performance 22:51:04.256 --> 22:51:06.950 align:start position:0% performance and<22:51:05.160> it<22:51:05.464> could<22:51:05.576> be<22:51:05.696> close<22:51:05.872> to<22:51:06.056> a<22:51:06.176> source<22:51:06.424> of<22:51:06.480> Emi 22:51:06.950 --> 22:51:06.960 align:start position:0% and it could be close to a source of Emi 22:51:06.960 --> 22:51:10.542 align:start position:0% and it could be close to a source of Emi which<22:51:07.320> we've<22:51:07.680> already<22:51:07.920> discussed 22:51:10.542 --> 22:51:10.552 align:start position:0% which we've already discussed 22:51:10.552 --> 22:51:12.590 align:start position:0% which we've already discussed power<22:51:11.040> failure<22:51:11.576> obviously<22:51:12.000> that's<22:51:12.240> going<22:51:12.480> to 22:51:12.590 --> 22:51:12.600 align:start position:0% power failure obviously that's going to 22:51:12.600 --> 22:51:15.110 align:start position:0% power failure obviously that's going to cause<22:51:12.784> issues<22:51:13.192> either<22:51:13.440> with<22:51:13.744> the<22:51:13.920> device<22:51:14.216> or 22:51:15.110 --> 22:51:15.120 align:start position:0% cause issues either with the device or 22:51:15.120 --> 22:51:16.606 align:start position:0% cause issues either with the device or part<22:51:15.296> of<22:51:15.480> the<22:51:15.600> network<22:51:15.784> or<22:51:16.192> the<22:51:16.376> entire 22:51:16.606 --> 22:51:16.616 align:start position:0% part of the network or the entire 22:51:16.616 --> 22:51:18.710 align:start position:0% part of the network or the entire network 22:51:18.710 --> 22:51:18.720 align:start position:0% network 22:51:18.720 --> 22:51:20.390 align:start position:0% network and<22:51:19.440> most 22:51:20.390 --> 22:51:20.400 align:start position:0% and most 22:51:20.400 --> 22:51:22.134 align:start position:0% and most um<22:51:20.512> the<22:51:20.696> higher<22:51:21.000> end<22:51:21.176> switches<22:51:21.600> and<22:51:21.784> routers 22:51:22.134 --> 22:51:22.144 align:start position:0% um the higher end switches and routers 22:51:22.144 --> 22:51:25.006 align:start position:0% um the higher end switches and routers have<22:51:22.440> redundant<22:51:22.920> power<22:51:23.160> supplies<22:51:23.760> so<22:51:24.656> that<22:51:24.832> if 22:51:25.006 --> 22:51:25.016 align:start position:0% have redundant power supplies so that if 22:51:25.016 --> 22:51:27.110 align:start position:0% have redundant power supplies so that if the<22:51:25.256> main<22:51:25.440> one<22:51:25.616> goes<22:51:25.920> down<22:51:26.040> the<22:51:26.336> second<22:51:26.696> does 22:51:27.110 --> 22:51:27.120 align:start position:0% the main one goes down the second does 22:51:27.120 --> 22:51:30.470 align:start position:0% the main one goes down the second does backup<22:51:27.536> one<22:51:27.784> takes<22:51:28.080> over 22:51:30.470 --> 22:51:30.480 align:start position:0% 22:51:30.480 --> 22:51:33.350 align:start position:0% MTU<22:51:31.320> backholes<22:51:31.920> this<22:51:32.280> is<22:51:32.464> a<22:51:32.760> maximum 22:51:33.350 --> 22:51:33.360 align:start position:0% MTU backholes this is a maximum 22:51:33.360 --> 22:51:36.710 align:start position:0% MTU backholes this is a maximum transmission<22:51:34.144> units<22:51:34.920> for<22:51:35.104> your<22:51:35.280> IP<22:51:35.512> packets 22:51:36.710 --> 22:51:36.720 align:start position:0% transmission units for your IP packets 22:51:36.720 --> 22:51:38.990 align:start position:0% transmission units for your IP packets and<22:51:37.320> it<22:51:37.440> depends<22:51:37.744> on<22:51:37.920> configurations<22:51:38.464> it<22:51:38.872> can 22:51:38.990 --> 22:51:39.000 align:start position:0% and it depends on configurations it can 22:51:39.000 --> 22:51:41.030 align:start position:0% and it depends on configurations it can also<22:51:39.296> happen<22:51:39.480> with<22:51:39.832> routing<22:51:40.256> protocols<22:51:40.800> such 22:51:41.030 --> 22:51:41.040 align:start position:0% also happen with routing protocols such 22:51:41.040 --> 22:51:43.366 align:start position:0% also happen with routing protocols such as<22:51:41.160> ospf 22:51:43.366 --> 22:51:43.376 align:start position:0% as ospf 22:51:43.376 --> 22:51:45.230 align:start position:0% as ospf um<22:51:43.504> which<22:51:43.856> is<22:51:43.976> outside<22:51:44.160> the<22:51:44.512> scope<22:51:44.696> of<22:51:44.872> this 22:51:45.230 --> 22:51:45.240 align:start position:0% um which is outside the scope of this 22:51:45.240 --> 22:51:47.390 align:start position:0% um which is outside the scope of this course 22:51:47.390 --> 22:51:47.400 align:start position:0% course 22:51:47.400 --> 22:51:49.246 align:start position:0% course if<22:51:47.824> the<22:51:47.936> packet's<22:51:48.360> been<22:51:48.480> flagged<22:51:48.832> as<22:51:48.896> do<22:51:49.144> not 22:51:49.246 --> 22:51:49.256 align:start position:0% if the packet's been flagged as do not 22:51:49.256 --> 22:51:51.950 align:start position:0% if the packet's been flagged as do not fragment<22:51:49.744> then<22:51:50.696> the<22:51:50.872> router<22:51:51.176> is<22:51:51.360> expected<22:51:51.784> to 22:51:51.950 --> 22:51:51.960 align:start position:0% fragment then the router is expected to 22:51:51.960 --> 22:51:54.046 align:start position:0% fragment then the router is expected to send<22:51:52.080> an<22:51:52.320> icmp<22:51:52.976> message<22:51:53.280> destination 22:51:54.046 --> 22:51:54.056 align:start position:0% send an icmp message destination 22:51:54.056 --> 22:51:56.630 align:start position:0% send an icmp message destination unreachable<22:51:54.832> back<22:51:55.744> to<22:51:55.920> the<22:51:56.040> host<22:51:56.160> that<22:51:56.400> sent 22:51:56.630 --> 22:51:56.640 align:start position:0% unreachable back to the host that sent 22:51:56.640 --> 22:51:58.910 align:start position:0% unreachable back to the host that sent the<22:51:56.824> packet 22:51:58.910 --> 22:51:58.920 align:start position:0% the packet 22:51:58.920 --> 22:52:00.526 align:start position:0% the packet and<22:51:59.280> the<22:51:59.512> router<22:51:59.760> drops<22:52:00.056> the<22:52:00.120> packet<22:52:00.424> and 22:52:00.526 --> 22:52:00.536 align:start position:0% and the router drops the packet and 22:52:00.536 --> 22:52:02.566 align:start position:0% and the router drops the packet and doesn't<22:52:00.656> send<22:52:00.896> the<22:52:01.016> icmp<22:52:01.680> message<22:52:01.976> then<22:52:02.336> the 22:52:02.566 --> 22:52:02.576 align:start position:0% doesn't send the icmp message then the 22:52:02.576 --> 22:52:04.310 align:start position:0% doesn't send the icmp message then the host<22:52:02.824> to<22:52:03.240> the<22:52:03.424> host<22:52:03.600> and<22:52:03.784> the<22:52:03.960> router<22:52:04.256> is 22:52:04.310 --> 22:52:04.320 align:start position:0% host to the host and the router is 22:52:04.320 --> 22:52:06.414 align:start position:0% host to the host and the router is referred<22:52:04.616> to<22:52:04.680> as<22:52:04.800> a<22:52:04.976> black<22:52:05.040> hole<22:52:05.464> router 22:52:06.414 --> 22:52:06.424 align:start position:0% referred to as a black hole router 22:52:06.424 --> 22:52:09.646 align:start position:0% referred to as a black hole router you<22:52:06.960> can<22:52:07.080> check<22:52:07.256> the<22:52:07.504> interface<22:52:08.120> MTU<22:52:09.120> on<22:52:09.480> your 22:52:09.646 --> 22:52:09.656 align:start position:0% you can check the interface MTU on your 22:52:09.656 --> 22:52:12.046 align:start position:0% you can check the interface MTU on your routers<22:52:10.192> when<22:52:10.856> you<22:52:10.976> do<22:52:11.160> the<22:52:11.280> show<22:52:11.464> interface 22:52:12.046 --> 22:52:12.056 align:start position:0% routers when you do the show interface 22:52:12.056 --> 22:52:15.110 align:start position:0% routers when you do the show interface or<22:52:12.960> you<22:52:13.192> can<22:52:13.320> add<22:52:14.040> um<22:52:14.040> some<22:52:14.336> troubleshooting 22:52:15.110 --> 22:52:15.120 align:start position:0% or you can add um some troubleshooting 22:52:15.120 --> 22:52:17.390 align:start position:0% or you can add um some troubleshooting software<22:52:15.656> if<22:52:16.376> it<22:52:16.552> if<22:52:16.800> you<22:52:16.920> don't<22:52:16.976> already<22:52:17.160> have 22:52:17.390 --> 22:52:17.400 align:start position:0% software if it if you don't already have 22:52:17.400 --> 22:52:20.566 align:start position:0% software if it if you don't already have it<22:52:18.056> you<22:52:18.600> can<22:52:18.720> use<22:52:18.832> a<22:52:19.016> ping<22:52:19.256> utility<22:52:19.616> or<22:52:20.280> you<22:52:20.464> can 22:52:20.566 --> 22:52:20.576 align:start position:0% it you can use a ping utility or you can 22:52:20.576 --> 22:52:22.910 align:start position:0% it you can use a ping utility or you can use<22:52:20.760> a<22:52:20.936> trace<22:52:21.176> route<22:52:21.480> you<22:52:22.256> can<22:52:22.320> send<22:52:22.552> different 22:52:22.910 --> 22:52:22.920 align:start position:0% use a trace route you can send different 22:52:22.920 --> 22:52:25.790 align:start position:0% use a trace route you can send different ping<22:52:23.336> sizes<22:52:23.960> and<22:52:24.960> certainly<22:52:25.320> on<22:52:25.440> Cisco 22:52:25.790 --> 22:52:25.800 align:start position:0% ping sizes and certainly on Cisco 22:52:25.800 --> 22:52:28.094 align:start position:0% ping sizes and certainly on Cisco routers<22:52:26.216> you<22:52:26.464> can<22:52:26.576> go<22:52:26.696> into<22:52:26.872> a<22:52:27.176> detailed<22:52:27.832> menu 22:52:28.094 --> 22:52:28.104 align:start position:0% routers you can go into a detailed menu 22:52:28.104 --> 22:52:30.822 align:start position:0% routers you can go into a detailed menu of<22:52:29.104> options<22:52:29.464> or<22:52:29.640> send<22:52:29.824> a<22:52:30.000> ping<22:52:30.176> packet<22:52:30.536> of<22:52:30.656> a 22:52:30.822 --> 22:52:30.832 align:start position:0% of options or send a ping packet of a 22:52:30.832 --> 22:52:32.566 align:start position:0% of options or send a ping packet of a certain<22:52:31.016> size<22:52:31.320> to<22:52:31.920> see<22:52:32.040> if<22:52:32.160> you're<22:52:32.280> losing 22:52:32.566 --> 22:52:32.576 align:start position:0% certain size to see if you're losing 22:52:32.576 --> 22:52:34.182 align:start position:0% certain size to see if you're losing packets 22:52:34.182 --> 22:52:34.192 align:start position:0% packets 22:52:34.192 --> 22:52:37.542 align:start position:0% packets Nick<22:52:34.744> teaming<22:52:35.280> for<22:52:36.176> user<22:52:36.600> experiences<22:52:37.080> a 22:52:37.542 --> 22:52:37.552 align:start position:0% Nick teaming for user experiences a 22:52:37.552 --> 22:52:40.366 align:start position:0% Nick teaming for user experiences a degradation<22:52:38.216> in<22:52:38.640> network<22:52:38.824> performance<22:52:39.536> it 22:52:40.366 --> 22:52:40.376 align:start position:0% degradation in network performance it 22:52:40.376 --> 22:52:42.230 align:start position:0% degradation in network performance it could<22:52:40.552> be<22:52:40.680> a<22:52:40.856> Nick<22:52:41.040> teaming<22:52:41.464> misconfiguration 22:52:42.230 --> 22:52:42.240 align:start position:0% could be a Nick teaming misconfiguration 22:52:42.240 --> 22:52:45.366 align:start position:0% could be a Nick teaming misconfiguration this<22:52:43.080> is<22:52:43.256> generally<22:52:43.616> done<22:52:43.920> a<22:52:44.216> lot<22:52:44.336> on<22:52:44.640> servers 22:52:45.366 --> 22:52:45.376 align:start position:0% this is generally done a lot on servers 22:52:45.376 --> 22:52:49.494 align:start position:0% this is generally done a lot on servers and<22:52:46.376> different<22:52:47.360> vendors<22:52:48.360> have<22:52:49.192> different 22:52:49.494 --> 22:52:49.504 align:start position:0% and different vendors have different 22:52:49.504 --> 22:52:52.966 align:start position:0% and different vendors have different terminology<22:52:50.464> for<22:52:50.936> Nick<22:52:51.176> teaming<22:52:51.784> so<22:52:52.192> again 22:52:52.966 --> 22:52:52.976 align:start position:0% terminology for Nick teaming so again 22:52:52.976 --> 22:52:55.134 align:start position:0% terminology for Nick teaming so again check<22:52:53.280> your<22:52:53.464> documentation 22:52:55.134 --> 22:52:55.144 align:start position:0% check your documentation 22:52:55.144 --> 22:52:58.134 align:start position:0% check your documentation uh<22:52:56.040> generally<22:52:56.464> you'll<22:52:56.824> you'll 22:52:58.134 --> 22:52:58.144 align:start position:0% uh generally you'll you'll 22:52:58.144 --> 22:53:02.390 align:start position:0% uh generally you'll you'll aggregate<22:52:59.104> various<22:52:59.872> Network<22:53:00.480> Cards<22:53:01.144> into<22:53:02.040> one 22:53:02.390 --> 22:53:02.400 align:start position:0% aggregate various Network Cards into one 22:53:02.400 --> 22:53:07.246 align:start position:0% aggregate various Network Cards into one logical<22:53:02.824> connection 22:53:07.246 --> 22:53:07.256 align:start position:0% 22:53:07.256 --> 22:53:10.366 align:start position:0% um<22:53:07.376> so<22:53:07.616> you<22:53:07.856> could<22:53:07.976> have<22:53:08.160> broadcast<22:53:08.464> uh<22:53:09.720> storms 22:53:10.366 --> 22:53:10.376 align:start position:0% um so you could have broadcast uh storms 22:53:10.376 --> 22:53:12.110 align:start position:0% um so you could have broadcast uh storms there'll<22:53:10.920> be<22:53:11.040> other<22:53:11.160> issues<22:53:11.512> as<22:53:11.696> well<22:53:11.872> with 22:53:12.110 --> 22:53:12.120 align:start position:0% there'll be other issues as well with 22:53:12.120 --> 22:53:15.526 align:start position:0% there'll be other issues as well with spanning<22:53:12.600> tree<22:53:12.784> and<22:53:13.616> um<22:53:13.680> other<22:53:14.216> things<22:53:14.576> to 22:53:15.526 --> 22:53:15.536 align:start position:0% spanning tree and um other things to 22:53:15.536 --> 22:53:17.502 align:start position:0% spanning tree and um other things to prevent<22:53:15.832> the<22:53:16.016> Nick<22:53:16.376> team<22:53:16.616> from<22:53:16.920> becoming 22:53:17.502 --> 22:53:17.512 align:start position:0% prevent the Nick team from becoming 22:53:17.512 --> 22:53:19.966 align:start position:0% prevent the Nick team from becoming multiple<22:53:17.936> links<22:53:18.360> you<22:53:19.144> can<22:53:19.256> use<22:53:19.680> Link 22:53:19.966 --> 22:53:19.976 align:start position:0% multiple links you can use Link 22:53:19.976 --> 22:53:23.094 align:start position:0% multiple links you can use Link aggregation<22:53:20.640> control<22:53:20.936> protocol<22:53:21.744> which<22:53:22.744> is 22:53:23.094 --> 22:53:23.104 align:start position:0% aggregation control protocol which is 22:53:23.104 --> 22:53:25.910 align:start position:0% aggregation control protocol which is used<22:53:23.280> on<22:53:23.512> routers<22:53:24.056> generally 22:53:25.910 --> 22:53:25.920 align:start position:0% used on routers generally 22:53:25.920 --> 22:53:28.246 align:start position:0% used on routers generally all<22:53:26.512> right<22:53:26.640> so<22:53:26.872> incorrect<22:53:27.480> develop<22:53:27.720> Gateway 22:53:28.246 --> 22:53:28.256 align:start position:0% all right so incorrect develop Gateway 22:53:28.256 --> 22:53:31.182 align:start position:0% all right so incorrect develop Gateway broadcast<22:53:28.744> storms<22:53:29.512> duplicate<22:53:30.296> IP<22:53:30.720> and<22:53:31.016> speed 22:53:31.182 --> 22:53:31.192 align:start position:0% broadcast storms duplicate IP and speed 22:53:31.192 --> 22:53:34.006 align:start position:0% broadcast storms duplicate IP and speed and<22:53:31.440> duplex<22:53:32.176> VLAN<22:53:33.176> assignments<22:53:33.720> on<22:53:33.832> your 22:53:34.006 --> 22:53:34.016 align:start position:0% and duplex VLAN assignments on your 22:53:34.016 --> 22:53:35.926 align:start position:0% and duplex VLAN assignments on your switches<22:53:34.496> check<22:53:34.856> your<22:53:35.104> documentation<22:53:35.640> for 22:53:35.926 --> 22:53:35.936 align:start position:0% switches check your documentation for 22:53:35.936 --> 22:53:38.150 align:start position:0% switches check your documentation for that<22:53:36.056> and<22:53:36.240> your<22:53:36.360> configurations 22:53:38.150 --> 22:53:38.160 align:start position:0% that and your configurations 22:53:38.160 --> 22:53:41.390 align:start position:0% that and your configurations should<22:53:38.512> say<22:53:38.760> Hardware<22:53:39.000> failure<22:53:39.656> sorry 22:53:41.390 --> 22:53:41.400 align:start position:0% should say Hardware failure sorry 22:53:41.400 --> 22:53:45.166 align:start position:0% should say Hardware failure sorry misconfigured<22:53:42.240> DHCP<22:53:43.192> and<22:53:43.800> DNS 22:53:45.166 --> 22:53:45.176 align:start position:0% misconfigured DHCP and DNS 22:53:45.176 --> 22:53:48.110 align:start position:0% misconfigured DHCP and DNS interface<22:53:45.832> misconfiguration<22:53:46.744> issues<22:53:47.576> cable 22:53:48.110 --> 22:53:48.120 align:start position:0% interface misconfiguration issues cable 22:53:48.120 --> 22:53:49.790 align:start position:0% interface misconfiguration issues cable placements 22:53:49.790 --> 22:53:49.800 align:start position:0% placements 22:53:49.800 --> 22:53:52.430 align:start position:0% placements power<22:53:50.216> failures<22:53:50.760> empty<22:53:51.480> black<22:53:51.720> holes<22:53:52.144> and 22:53:52.430 --> 22:53:52.440 align:start position:0% power failures empty black holes and 22:53:52.440 --> 22:53:54.710 align:start position:0% power failures empty black holes and Nick<22:53:52.616> teaming<22:53:53.160> that's<22:53:53.696> all<22:53:53.936> for<22:53:54.120> now<22:53:54.296> thanks 22:53:54.710 --> 22:53:54.720 align:start position:0% Nick teaming that's all for now thanks 22:53:54.720 --> 22:53:59.590 align:start position:0% Nick teaming that's all for now thanks for<22:53:54.896> watching 22:53:59.590 --> 22:53:59.600 align:start position:0% 22:53:59.600 --> 22:54:08.286 align:start position:0% [Music] 22:54:08.286 --> 22:54:08.296 align:start position:0% [Music] 22:54:08.296 --> 22:54:16.182 align:start position:0% [Music] thank<22:54:09.296> you 22:54:16.182 --> 22:54:16.192 align:start position:0% 22:54:16.192 --> 22:54:18.710 align:start position:0% welcome<22:54:16.552> to<22:54:16.856> module<22:54:17.160> 20<22:54:17.400> lesson<22:54:17.936> one<22:54:18.120> change 22:54:18.710 --> 22:54:18.720 align:start position:0% welcome to module 20 lesson one change 22:54:18.720 --> 22:54:21.822 align:start position:0% welcome to module 20 lesson one change management<22:54:19.144> basics 22:54:21.822 --> 22:54:21.832 align:start position:0% management basics 22:54:21.832 --> 22:54:23.566 align:start position:0% management basics we're<22:54:22.192> going<22:54:22.320> to<22:54:22.440> look<22:54:22.496> at<22:54:22.680> what<22:54:22.920> is<22:54:23.104> a<22:54:23.336> change 22:54:23.566 --> 22:54:23.576 align:start position:0% we're going to look at what is a change 22:54:23.576 --> 22:54:25.910 align:start position:0% we're going to look at what is a change what<22:54:23.936> is<22:54:24.176> change<22:54:24.360> management<22:54:24.856> types<22:54:25.856> of 22:54:25.910 --> 22:54:25.920 align:start position:0% what is change management types of 22:54:25.920 --> 22:54:28.606 align:start position:0% what is change management types of changes<22:54:26.464> and<22:54:26.640> approval<22:54:27.056> processes<22:54:27.784> what<22:54:28.440> is 22:54:28.606 --> 22:54:28.616 align:start position:0% changes and approval processes what is 22:54:28.616 --> 22:54:30.590 align:start position:0% changes and approval processes what is documentation<22:54:29.336> in<22:54:29.936> respect<22:54:30.176> of<22:54:30.360> change 22:54:30.590 --> 22:54:30.600 align:start position:0% documentation in respect of change 22:54:30.600 --> 22:54:31.910 align:start position:0% documentation in respect of change management 22:54:31.910 --> 22:54:31.920 align:start position:0% management 22:54:31.920 --> 22:54:34.670 align:start position:0% management what<22:54:32.400> is<22:54:32.576> a<22:54:32.696> maintenance<22:54:33.000> window 22:54:34.670 --> 22:54:34.680 align:start position:0% what is a maintenance window 22:54:34.680 --> 22:54:37.606 align:start position:0% what is a maintenance window what<22:54:35.464> is<22:54:35.696> configuration<22:54:36.360> procedures<22:54:37.192> or<22:54:37.440> what 22:54:37.606 --> 22:54:37.616 align:start position:0% what is configuration procedures or what 22:54:37.616 --> 22:54:38.686 align:start position:0% what is configuration procedures or what are 22:54:38.686 --> 22:54:38.696 align:start position:0% are 22:54:38.696 --> 22:54:41.326 align:start position:0% are what<22:54:39.056> is<22:54:39.296> a<22:54:39.424> rollback<22:54:39.832> what<22:54:40.744> is<22:54:40.856> the<22:54:41.040> potential 22:54:41.326 --> 22:54:41.336 align:start position:0% what is a rollback what is the potential 22:54:41.336 --> 22:54:42.350 align:start position:0% what is a rollback what is the potential impact 22:54:42.350 --> 22:54:42.360 align:start position:0% impact 22:54:42.360 --> 22:54:45.134 align:start position:0% impact what<22:54:42.784> is<22:54:42.960> the<22:54:43.080> notification<22:54:43.616> to<22:54:43.856> change 22:54:45.134 --> 22:54:45.144 align:start position:0% what is the notification to change 22:54:45.144 --> 22:54:49.182 align:start position:0% what is the notification to change now<22:54:46.144> change<22:54:46.376> management<22:54:46.744> is<22:54:47.336> a<22:54:47.784> new<22:54:48.784> addition 22:54:49.182 --> 22:54:49.192 align:start position:0% now change management is a new addition 22:54:49.192 --> 22:54:52.134 align:start position:0% now change management is a new addition to<22:54:49.616> the<22:54:49.920> network<22:54:50.104> plus<22:54:50.464> syllabus 22:54:52.134 --> 22:54:52.144 align:start position:0% to the network plus syllabus 22:54:52.144 --> 22:54:55.070 align:start position:0% to the network plus syllabus it<22:54:52.616> actually<22:54:52.744> dates<22:54:53.216> back<22:54:53.512> to<22:54:54.424> you<22:54:54.784> can<22:54:54.960> trace 22:54:55.070 --> 22:54:55.080 align:start position:0% it actually dates back to you can trace 22:54:55.080 --> 22:54:58.542 align:start position:0% it actually dates back to you can trace change<22:54:55.440> the<22:54:55.616> management<22:54:55.800> back<22:54:56.216> to<22:54:56.336> the<22:54:56.512> 1960s 22:54:58.542 --> 22:54:58.552 align:start position:0% change the management back to the 1960s 22:54:58.552 --> 22:55:01.966 align:start position:0% change the management back to the 1960s and<22:54:59.512> now<22:55:00.056> it's<22:55:00.360> a<22:55:00.536> recognized 22:55:01.966 --> 22:55:01.976 align:start position:0% and now it's a recognized 22:55:01.976 --> 22:55:02.710 align:start position:0% and now it's a recognized um 22:55:02.710 --> 22:55:02.720 align:start position:0% um 22:55:02.720 --> 22:55:06.710 align:start position:0% um qualification<22:55:03.720> and<22:55:04.616> a<22:55:04.856> whole<22:55:05.160> area<22:55:05.536> where<22:55:06.536> you 22:55:06.710 --> 22:55:06.720 align:start position:0% qualification and a whole area where you 22:55:06.720 --> 22:55:08.390 align:start position:0% qualification and a whole area where you can<22:55:06.832> gain<22:55:07.144> employment<22:55:07.616> as<22:55:08.040> a<22:55:08.216> change 22:55:08.390 --> 22:55:08.400 align:start position:0% can gain employment as a change 22:55:08.400 --> 22:55:10.966 align:start position:0% can gain employment as a change management<22:55:08.760> change<22:55:09.536> manager 22:55:10.966 --> 22:55:10.976 align:start position:0% management change manager 22:55:10.976 --> 22:55:14.206 align:start position:0% management change manager so<22:55:11.576> you<22:55:12.056> could<22:55:12.176> Google<22:55:12.480> change<22:55:13.192> manager<22:55:13.920> and 22:55:14.206 --> 22:55:14.216 align:start position:0% so you could Google change manager and 22:55:14.216 --> 22:55:16.134 align:start position:0% so you could Google change manager and ITIL<22:55:14.640> which<22:55:14.872> is<22:55:15.000> the<22:55:15.176> it<22:55:15.296> infrastructure 22:55:16.134 --> 22:55:16.144 align:start position:0% ITIL which is the it infrastructure 22:55:16.144 --> 22:55:17.150 align:start position:0% ITIL which is the it infrastructure Library 22:55:17.150 --> 22:55:17.160 align:start position:0% Library 22:55:17.160 --> 22:55:19.606 align:start position:0% Library but<22:55:17.464> this<22:55:17.640> is<22:55:17.760> bringing<22:55:18.120> it<22:55:18.480> into<22:55:19.016> alignment 22:55:19.606 --> 22:55:19.616 align:start position:0% but this is bringing it into alignment 22:55:19.616 --> 22:55:22.310 align:start position:0% but this is bringing it into alignment with<22:55:19.800> prisoners<22:55:20.400> practices<22:55:21.144> where<22:55:22.144> we're 22:55:22.310 --> 22:55:22.320 align:start position:0% with prisoners practices where we're 22:55:22.320 --> 22:55:23.750 align:start position:0% with prisoners practices where we're managing 22:55:23.750 --> 22:55:23.760 align:start position:0% managing 22:55:23.760 --> 22:55:27.886 align:start position:0% managing um<22:55:23.960> changes<22:55:25.216> and<22:55:26.216> problems<22:55:27.000> also<22:55:27.480> when<22:55:27.720> I 22:55:27.886 --> 22:55:27.896 align:start position:0% um changes and problems also when I 22:55:27.896 --> 22:55:31.246 align:start position:0% um changes and problems also when I worked<22:55:28.256> uh<22:55:28.736> Yellow<22:55:28.976> Pages<22:55:29.336> in<22:55:29.760> the<22:55:29.872> UK<22:55:30.256> there 22:55:31.246 --> 22:55:31.256 align:start position:0% worked uh Yellow Pages in the UK there 22:55:31.256 --> 22:55:33.222 align:start position:0% worked uh Yellow Pages in the UK there was<22:55:31.376> a<22:55:31.504> whole<22:55:31.616> Lotto<22:55:31.976> team<22:55:32.280> looking<22:55:32.640> at<22:55:33.232> um 22:55:33.222 --> 22:55:33.232 align:start position:0% was a whole Lotto team looking at um 22:55:33.232 --> 22:55:36.414 align:start position:0% was a whole Lotto team looking at um change<22:55:33.720> management<22:55:34.216> problem<22:55:35.216> management<22:55:35.576> so 22:55:36.414 --> 22:55:36.424 align:start position:0% change management problem management so 22:55:36.424 --> 22:55:38.094 align:start position:0% change management problem management so there's<22:55:36.656> systems<22:55:37.080> and<22:55:37.256> procedures<22:55:37.736> for 22:55:38.094 --> 22:55:38.104 align:start position:0% there's systems and procedures for 22:55:38.104 --> 22:55:40.070 align:start position:0% there's systems and procedures for everything<22:55:38.336> looking<22:55:39.176> at<22:55:39.480> what<22:55:39.784> we're<22:55:39.896> doing 22:55:40.070 --> 22:55:40.080 align:start position:0% everything looking at what we're doing 22:55:40.080 --> 22:55:43.846 align:start position:0% everything looking at what we're doing why<22:55:40.440> we're<22:55:40.680> doing<22:55:40.856> it<22:55:41.160> who<22:55:42.056> authorizes<22:55:42.784> it<22:55:42.960> if 22:55:43.846 --> 22:55:43.856 align:start position:0% why we're doing it who authorizes it if 22:55:43.856 --> 22:55:45.350 align:start position:0% why we're doing it who authorizes it if there's<22:55:43.976> a<22:55:44.216> problem<22:55:44.336> what<22:55:44.760> caused<22:55:45.296> the 22:55:45.350 --> 22:55:45.360 align:start position:0% there's a problem what caused the 22:55:45.360 --> 22:55:46.726 align:start position:0% there's a problem what caused the problem<22:55:45.536> how<22:55:45.960> do<22:55:46.080> we<22:55:46.192> stop<22:55:46.320> the<22:55:46.552> problem 22:55:46.726 --> 22:55:46.736 align:start position:0% problem how do we stop the problem 22:55:46.736 --> 22:55:48.414 align:start position:0% problem how do we stop the problem happening<22:55:47.216> again 22:55:48.414 --> 22:55:48.424 align:start position:0% happening again 22:55:48.424 --> 22:55:50.750 align:start position:0% happening again and<22:55:48.896> it<22:55:49.016> makes<22:55:49.192> the<22:55:49.440> entire<22:55:49.800> uh<22:55:50.512> business 22:55:50.750 --> 22:55:50.760 align:start position:0% and it makes the entire uh business 22:55:50.760 --> 22:55:52.542 align:start position:0% and it makes the entire uh business procedure<22:55:51.360> and<22:55:51.536> business<22:55:51.720> run<22:55:52.144> more 22:55:52.542 --> 22:55:52.552 align:start position:0% procedure and business run more 22:55:52.552 --> 22:55:55.134 align:start position:0% procedure and business run more professionally<22:55:53.120> and<22:55:54.120> it<22:55:54.296> cuts<22:55:54.600> down<22:55:54.656> a<22:55:54.960> lot<22:55:55.016> of 22:55:55.134 --> 22:55:55.144 align:start position:0% professionally and it cuts down a lot of 22:55:55.144 --> 22:55:56.822 align:start position:0% professionally and it cuts down a lot of unnecessary 22:55:56.822 --> 22:55:56.832 align:start position:0% unnecessary 22:55:56.832 --> 22:56:00.950 align:start position:0% unnecessary procedures<22:55:57.832> blaming<22:55:58.680> Communications<22:55:59.960> and 22:56:00.950 --> 22:56:00.960 align:start position:0% procedures blaming Communications and 22:56:00.960 --> 22:56:03.350 align:start position:0% procedures blaming Communications and debriefing<22:56:01.856> and<22:56:02.216> makes<22:56:02.400> the<22:56:02.696> organization 22:56:03.350 --> 22:56:03.360 align:start position:0% debriefing and makes the organization 22:56:03.360 --> 22:56:05.390 align:start position:0% debriefing and makes the organization work<22:56:03.720> more<22:56:03.896> efficiently 22:56:05.390 --> 22:56:05.400 align:start position:0% work more efficiently 22:56:05.400 --> 22:56:07.726 align:start position:0% work more efficiently changes<22:56:06.232> any<22:56:06.480> addition<22:56:06.896> removal<22:56:07.616> or 22:56:07.726 --> 22:56:07.736 align:start position:0% changes any addition removal or 22:56:07.736 --> 22:56:09.822 align:start position:0% changes any addition removal or modification<22:56:08.336> or<22:56:08.696> configuration<22:56:09.296> that<22:56:09.656> could 22:56:09.822 --> 22:56:09.832 align:start position:0% modification or configuration that could 22:56:09.832 --> 22:56:13.246 align:start position:0% modification or configuration that could have<22:56:10.144> an<22:56:10.680> effect<22:56:10.856> on<22:56:11.104> the<22:56:11.280> IT<22:56:11.400> service<22:56:12.080> so<22:56:13.080> this 22:56:13.246 --> 22:56:13.256 align:start position:0% have an effect on the IT service so this 22:56:13.256 --> 22:56:15.470 align:start position:0% have an effect on the IT service so this is<22:56:13.376> why<22:56:13.552> we<22:56:13.856> need<22:56:13.976> to<22:56:14.216> have<22:56:14.512> a<22:56:14.936> set<22:56:15.360> of 22:56:15.470 --> 22:56:15.480 align:start position:0% is why we need to have a set of 22:56:15.480 --> 22:56:19.134 align:start position:0% is why we need to have a set of procedures<22:56:16.080> in<22:56:17.040> order<22:56:17.160> to<22:56:17.640> plan<22:56:18.120> for<22:56:18.832> a<22:56:18.960> change 22:56:19.134 --> 22:56:19.144 align:start position:0% procedures in order to plan for a change 22:56:19.144 --> 22:56:22.070 align:start position:0% procedures in order to plan for a change rather<22:56:19.552> than<22:56:19.800> somebody<22:56:20.104> just<22:56:20.512> rebooting<22:56:21.176> one 22:56:22.070 --> 22:56:22.080 align:start position:0% rather than somebody just rebooting one 22:56:22.080 --> 22:56:24.526 align:start position:0% rather than somebody just rebooting one of<22:56:22.256> the<22:56:22.376> main<22:56:22.736> cool<22:56:23.040> routers<22:56:23.640> on<22:56:24.120> the<22:56:24.296> network 22:56:24.526 --> 22:56:24.536 align:start position:0% of the main cool routers on the network 22:56:24.536 --> 22:56:27.646 align:start position:0% of the main cool routers on the network at<22:56:25.440> the<22:56:25.552> busiest<22:56:25.856> time<22:56:26.160> of<22:56:26.400> day<22:56:26.576> we<22:56:27.360> need<22:56:27.536> to 22:56:27.646 --> 22:56:27.656 align:start position:0% at the busiest time of day we need to 22:56:27.656 --> 22:56:30.046 align:start position:0% at the busiest time of day we need to have<22:56:27.784> some<22:56:28.016> sort<22:56:28.144> of<22:56:28.256> procedure 22:56:30.046 --> 22:56:30.056 align:start position:0% have some sort of procedure 22:56:30.056 --> 22:56:32.270 align:start position:0% have some sort of procedure so<22:56:30.536> change<22:56:30.784> management<22:56:31.144> is<22:56:31.736> a<22:56:31.856> set<22:56:32.104> of 22:56:32.270 --> 22:56:32.280 align:start position:0% so change management is a set of 22:56:32.280 --> 22:56:34.246 align:start position:0% so change management is a set of processes<22:56:32.872> that<22:56:33.232> governs<22:56:33.656> and<22:56:33.784> controls<22:56:34.144> the 22:56:34.246 --> 22:56:34.256 align:start position:0% processes that governs and controls the 22:56:34.256 --> 22:56:36.710 align:start position:0% processes that governs and controls the aspects<22:56:34.680> from<22:56:34.800> start<22:56:35.040> to<22:56:35.280> finish<22:56:35.464> it<22:56:36.296> reduces 22:56:36.710 --> 22:56:36.720 align:start position:0% aspects from start to finish it reduces 22:56:36.720 --> 22:56:39.350 align:start position:0% aspects from start to finish it reduces the<22:56:36.960> risk<22:56:37.320> disruption<22:56:37.856> and<22:56:38.512> impact<22:56:39.000> on<22:56:39.176> the 22:56:39.350 --> 22:56:39.360 align:start position:0% the risk disruption and impact on the 22:56:39.360 --> 22:56:40.430 align:start position:0% the risk disruption and impact on the business 22:56:40.430 --> 22:56:40.440 align:start position:0% business 22:56:40.440 --> 22:56:44.030 align:start position:0% business we<22:56:41.040> could<22:56:41.216> refer<22:56:41.464> to<22:56:41.512> it<22:56:41.696> as<22:56:41.872> CM<22:56:42.232> for<22:56:42.536> short 22:56:44.030 --> 22:56:44.040 align:start position:0% we could refer to it as CM for short 22:56:44.040 --> 22:56:46.542 align:start position:0% we could refer to it as CM for short so<22:56:44.512> CM<22:56:44.936> aims<22:56:45.296> to<22:56:45.424> use<22:56:45.536> the<22:56:45.720> defined<22:56:46.080> standards 22:56:46.542 --> 22:56:46.552 align:start position:0% so CM aims to use the defined standards 22:56:46.552 --> 22:56:48.110 align:start position:0% so CM aims to use the defined standards and<22:56:46.736> methods<22:56:47.160> and<22:56:47.216> procedures<22:56:47.696> across 22:56:48.110 --> 22:56:48.120 align:start position:0% and methods and procedures across 22:56:48.120 --> 22:56:49.910 align:start position:0% and methods and procedures across various<22:56:48.480> teams<22:56:48.832> of<22:56:49.016> groups<22:56:49.320> so<22:56:49.440> we're<22:56:49.680> all 22:56:49.910 --> 22:56:49.920 align:start position:0% various teams of groups so we're all 22:56:49.920 --> 22:56:52.310 align:start position:0% various teams of groups so we're all basically<22:56:50.424> singing<22:56:51.424> off<22:56:51.536> the<22:56:51.720> same<22:56:51.832> hymn 22:56:52.310 --> 22:56:52.320 align:start position:0% basically singing off the same hymn 22:56:52.320 --> 22:56:55.606 align:start position:0% basically singing off the same hymn sheep<22:56:52.640> this<22:56:53.640> is<22:56:53.824> the<22:56:54.360> ITIL<22:56:55.256> the<22:56:55.440> it 22:56:55.606 --> 22:56:55.616 align:start position:0% sheep this is the ITIL the it 22:56:55.616 --> 22:56:57.710 align:start position:0% sheep this is the ITIL the it infrastructure<22:56:56.336> Library<22:56:56.640> which<22:56:57.120> we<22:56:57.424> actually 22:56:57.710 --> 22:56:57.720 align:start position:0% infrastructure Library which we actually 22:56:57.720 --> 22:57:00.526 align:start position:0% infrastructure Library which we actually host<22:56:58.280> and<22:56:59.280> some<22:56:59.576> of<22:56:59.696> the<22:56:59.872> one<22:57:00.360> of<22:57:00.480> the 22:57:00.526 --> 22:57:00.536 align:start position:0% host and some of the one of the 22:57:00.536 --> 22:57:03.414 align:start position:0% host and some of the one of the qualifications<22:57:01.016> on<22:57:01.376> howturnetwork.com<22:57:02.424> I 22:57:03.414 --> 22:57:03.424 align:start position:0% qualifications on howturnetwork.com I 22:57:03.424 --> 22:57:05.206 align:start position:0% qualifications on howturnetwork.com I highly<22:57:03.656> recommend<22:57:04.080> it<22:57:04.256> because 22:57:05.206 --> 22:57:05.216 align:start position:0% highly recommend it because 22:57:05.216 --> 22:57:07.494 align:start position:0% highly recommend it because um it<22:57:05.576> people<22:57:06.000> now<22:57:06.296> can't<22:57:06.600> just<22:57:06.832> rely<22:57:07.192> on 22:57:07.494 --> 22:57:07.504 align:start position:0% um it people now can't just rely on 22:57:07.504 --> 22:57:08.862 align:start position:0% um it people now can't just rely on being<22:57:07.800> technical 22:57:08.862 --> 22:57:08.872 align:start position:0% being technical 22:57:08.872 --> 22:57:10.790 align:start position:0% being technical they<22:57:09.424> need<22:57:09.600> to<22:57:09.720> have<22:57:09.896> an<22:57:10.144> understanding<22:57:10.616> of 22:57:10.790 --> 22:57:10.800 align:start position:0% they need to have an understanding of 22:57:10.800 --> 22:57:12.470 align:start position:0% they need to have an understanding of how<22:57:10.976> they<22:57:11.104> slot<22:57:11.400> into<22:57:11.512> the<22:57:11.760> business<22:57:11.872> and<22:57:12.296> how 22:57:12.470 --> 22:57:12.480 align:start position:0% how they slot into the business and how 22:57:12.480 --> 22:57:15.414 align:start position:0% how they slot into the business and how the<22:57:12.600> business<22:57:12.784> works<22:57:13.504> the<22:57:14.400> it<22:57:14.576> works<22:57:15.120> as<22:57:15.232> part 22:57:15.414 --> 22:57:15.424 align:start position:0% the business works the it works as part 22:57:15.424 --> 22:57:18.046 align:start position:0% the business works the it works as part of<22:57:15.480> the<22:57:15.600> overall<22:57:15.896> business<22:57:16.512> utility<22:57:17.512> breaks 22:57:18.046 --> 22:57:18.056 align:start position:0% of the overall business utility breaks 22:57:18.056 --> 22:57:20.030 align:start position:0% of the overall business utility breaks into<22:57:18.176> service<22:57:18.536> transition<22:57:19.144> service<22:57:19.616> design 22:57:20.030 --> 22:57:20.040 align:start position:0% into service transition service design 22:57:20.040 --> 22:57:22.134 align:start position:0% into service transition service design and<22:57:20.464> service<22:57:20.696> operations 22:57:22.134 --> 22:57:22.144 align:start position:0% and service operations 22:57:22.144 --> 22:57:24.710 align:start position:0% and service operations and<22:57:22.552> you<22:57:22.616> can<22:57:22.736> see<22:57:22.920> some<22:57:23.216> of<22:57:23.336> the<22:57:24.000> um<22:57:24.000> things<22:57:24.424> I 22:57:24.710 --> 22:57:24.720 align:start position:0% and you can see some of the um things I 22:57:24.720 --> 22:57:26.814 align:start position:0% and you can see some of the um things I mentioned<22:57:25.192> here<22:57:25.736> you<22:57:26.336> can<22:57:26.464> see<22:57:26.576> change 22:57:26.814 --> 22:57:26.824 align:start position:0% mentioned here you can see change 22:57:26.824 --> 22:57:29.030 align:start position:0% mentioned here you can see change management<22:57:27.176> is<22:57:27.656> highlighted<22:57:28.256> there's 22:57:29.030 --> 22:57:29.040 align:start position:0% management is highlighted there's 22:57:29.040 --> 22:57:30.822 align:start position:0% management is highlighted there's problem<22:57:29.280> management<22:57:29.640> Knowledge<22:57:30.536> Management 22:57:30.822 --> 22:57:30.832 align:start position:0% problem management Knowledge Management 22:57:30.832 --> 22:57:34.366 align:start position:0% problem management Knowledge Management Service<22:57:31.552> testing<22:57:32.216> and<22:57:32.400> validation 22:57:34.366 --> 22:57:34.376 align:start position:0% Service testing and validation 22:57:34.376 --> 22:57:37.366 align:start position:0% Service testing and validation and<22:57:35.160> you<22:57:35.336> slot<22:57:35.824> this<22:57:36.000> into<22:57:36.176> your<22:57:36.656> business<22:57:36.784> how 22:57:37.366 --> 22:57:37.376 align:start position:0% and you slot this into your business how 22:57:37.376 --> 22:57:38.926 align:start position:0% and you slot this into your business how your<22:57:37.616> business<22:57:37.800> works<22:57:38.280> and<22:57:38.464> how<22:57:38.640> it's<22:57:38.760> going 22:57:38.926 --> 22:57:38.936 align:start position:0% your business works and how it's going 22:57:38.936 --> 22:57:40.910 align:start position:0% your business works and how it's going to<22:57:39.056> benefit<22:57:39.176> it 22:57:40.910 --> 22:57:40.920 align:start position:0% to benefit it 22:57:40.920 --> 22:57:43.182 align:start position:0% to benefit it so<22:57:41.640> change<22:57:41.936> management<22:57:42.232> includes<22:57:42.784> a<22:57:42.960> risk 22:57:43.182 --> 22:57:43.192 align:start position:0% so change management includes a risk 22:57:43.192 --> 22:57:45.310 align:start position:0% so change management includes a risk assessment<22:57:43.616> reducing<22:57:44.336> change<22:57:44.640> failures 22:57:45.310 --> 22:57:45.320 align:start position:0% assessment reducing change failures 22:57:45.320 --> 22:57:47.750 align:start position:0% assessment reducing change failures properly<22:57:46.320> implementing<22:57:46.976> any<22:57:47.160> changes 22:57:47.750 --> 22:57:47.760 align:start position:0% properly implementing any changes 22:57:47.760 --> 22:57:50.150 align:start position:0% properly implementing any changes looking<22:57:48.536> at<22:57:48.784> business<22:57:49.016> timelines<22:57:49.736> and 22:57:50.150 --> 22:57:50.160 align:start position:0% looking at business timelines and 22:57:50.160 --> 22:57:52.182 align:start position:0% looking at business timelines and service<22:57:50.336> level<22:57:50.576> agreements 22:57:52.182 --> 22:57:52.192 align:start position:0% service level agreements 22:57:52.192 --> 22:57:55.094 align:start position:0% service level agreements it<22:57:52.552> gives<22:57:52.680> you<22:57:52.856> better<22:57:53.040> control<22:57:53.400> a<22:57:54.232> clear<22:57:54.424> plan 22:57:55.094 --> 22:57:55.104 align:start position:0% it gives you better control a clear plan 22:57:55.104 --> 22:58:00.046 align:start position:0% it gives you better control a clear plan for<22:57:56.104> reverting<22:57:56.760> if<22:57:57.232> there's<22:57:57.424> an<22:57:57.832> issue 22:58:00.046 --> 22:58:00.056 align:start position:0% for reverting if there's an issue 22:58:00.056 --> 22:58:02.750 align:start position:0% for reverting if there's an issue I've<22:58:00.720> actually<22:58:00.896> seen<22:58:01.144> this<22:58:01.376> when<22:58:01.552> I<22:58:01.800> had<22:58:02.512> my 22:58:02.750 --> 22:58:02.760 align:start position:0% I've actually seen this when I had my 22:58:02.760 --> 22:58:04.430 align:start position:0% I've actually seen this when I had my website<22:58:03.056> hosted<22:58:03.480> with<22:58:03.656> a<22:58:03.896> different<22:58:04.016> service 22:58:04.430 --> 22:58:04.440 align:start position:0% website hosted with a different service 22:58:04.440 --> 22:58:07.606 align:start position:0% website hosted with a different service provider<22:58:05.280> somebody<22:58:06.176> did<22:58:06.656> a<22:58:06.896> change<22:58:07.080> to<22:58:07.320> one<22:58:07.504> of 22:58:07.606 --> 22:58:07.616 align:start position:0% provider somebody did a change to one of 22:58:07.616 --> 22:58:10.310 align:start position:0% provider somebody did a change to one of the<22:58:07.736> tables<22:58:08.160> on<22:58:08.400> one<22:58:08.576> of<22:58:08.696> the<22:58:08.824> databases<22:58:09.480> and 22:58:10.310 --> 22:58:10.320 align:start position:0% the tables on one of the databases and 22:58:10.320 --> 22:58:12.710 align:start position:0% the tables on one of the databases and it<22:58:10.496> caused<22:58:10.856> outages<22:58:11.280> for<22:58:11.824> around<22:58:12.056> three<22:58:12.424> days 22:58:12.710 --> 22:58:12.720 align:start position:0% it caused outages for around three days 22:58:12.720 --> 22:58:14.630 align:start position:0% it caused outages for around three days and<22:58:13.080> I<22:58:13.192> know<22:58:13.376> some<22:58:13.856> people<22:58:14.040> went<22:58:14.336> out<22:58:14.512> of 22:58:14.630 --> 22:58:14.640 align:start position:0% and I know some people went out of 22:58:14.640 --> 22:58:16.070 align:start position:0% and I know some people went out of business<22:58:14.824> it<22:58:15.176> was<22:58:15.296> just<22:58:15.480> an<22:58:15.720> absolute 22:58:16.070 --> 22:58:16.080 align:start position:0% business it was just an absolute 22:58:16.080 --> 22:58:19.006 align:start position:0% business it was just an absolute catastrophe<22:58:16.824> and<22:58:17.824> they<22:58:18.000> didn't<22:58:18.176> I<22:58:18.832> don't 22:58:19.006 --> 22:58:19.016 align:start position:0% catastrophe and they didn't I don't 22:58:19.016 --> 22:58:20.862 align:start position:0% catastrophe and they didn't I don't think<22:58:19.192> they<22:58:19.440> had<22:58:19.680> a<22:58:20.040> change<22:58:20.512> management 22:58:20.862 --> 22:58:20.872 align:start position:0% think they had a change management 22:58:20.872 --> 22:58:22.606 align:start position:0% think they had a change management procedure<22:58:21.536> in<22:58:21.720> place<22:58:21.896> otherwise<22:58:22.320> they<22:58:22.440> could 22:58:22.606 --> 22:58:22.616 align:start position:0% procedure in place otherwise they could 22:58:22.616 --> 22:58:24.774 align:start position:0% procedure in place otherwise they could have<22:58:22.736> backed<22:58:23.040> out<22:58:23.104> quite<22:58:23.512> quickly 22:58:24.774 --> 22:58:24.784 align:start position:0% have backed out quite quickly 22:58:24.784 --> 22:58:27.046 align:start position:0% have backed out quite quickly I'm<22:58:25.552> managing<22:58:25.920> Communications<22:58:26.464> this<22:58:26.936> is 22:58:27.046 --> 22:58:27.056 align:start position:0% I'm managing Communications this is 22:58:27.056 --> 22:58:29.206 align:start position:0% I'm managing Communications this is important<22:58:27.536> where<22:58:27.832> there's<22:58:28.016> a<22:58:28.192> central<22:58:28.856> person 22:58:29.206 --> 22:58:29.216 align:start position:0% important where there's a central person 22:58:29.216 --> 22:58:32.030 align:start position:0% important where there's a central person is<22:58:29.640> responsible<22:58:30.120> for<22:58:30.896> from<22:58:31.256> communicating 22:58:32.030 --> 22:58:32.040 align:start position:0% is responsible for from communicating 22:58:32.040 --> 22:58:34.430 align:start position:0% is responsible for from communicating what's<22:58:32.512> going<22:58:32.760> to<22:58:32.872> happen<22:58:33.080> when<22:58:34.080> it's<22:58:34.256> going 22:58:34.430 --> 22:58:34.440 align:start position:0% what's going to happen when it's going 22:58:34.440 --> 22:58:37.494 align:start position:0% what's going to happen when it's going to<22:58:34.616> happen<22:58:34.800> and<22:58:35.760> then<22:58:35.872> they<22:58:36.360> communicate 22:58:37.494 --> 22:58:37.504 align:start position:0% to happen and then they communicate 22:58:37.504 --> 22:58:38.150 align:start position:0% to happen and then they communicate um 22:58:38.150 --> 22:58:38.160 align:start position:0% um 22:58:38.160 --> 22:58:40.966 align:start position:0% um just<22:58:38.576> before<22:58:38.696> it<22:58:39.000> happens<22:58:39.232> and<22:58:40.192> then<22:58:40.320> after<22:58:40.552> to 22:58:40.966 --> 22:58:40.976 align:start position:0% just before it happens and then after to 22:58:40.976 --> 22:58:43.790 align:start position:0% just before it happens and then after to say<22:58:41.104> the<22:58:41.336> changes<22:58:41.640> happened<22:58:41.936> and<22:58:42.296> it<22:58:43.016> was 22:58:43.790 --> 22:58:43.800 align:start position:0% say the changes happened and it was 22:58:43.800 --> 22:58:46.006 align:start position:0% say the changes happened and it was um<22:58:43.920> a<22:58:44.512> success<22:58:44.872> or<22:58:45.056> failure<22:58:45.600> on<22:58:45.784> what's 22:58:46.006 --> 22:58:46.016 align:start position:0% um a success or failure on what's 22:58:46.016 --> 22:58:47.094 align:start position:0% um a success or failure on what's actually 22:58:47.094 --> 22:58:47.104 align:start position:0% actually 22:58:47.104 --> 22:58:48.646 align:start position:0% actually um<22:58:47.160> the<22:58:47.512> procedure<22:58:47.936> afterwards<22:58:48.424> for 22:58:48.646 --> 22:58:48.656 align:start position:0% um the procedure afterwards for 22:58:48.656 --> 22:58:50.990 align:start position:0% um the procedure afterwards for following<22:58:49.016> up 22:58:50.990 --> 22:58:51.000 align:start position:0% following up 22:58:51.000 --> 22:58:53.030 align:start position:0% following up changes<22:58:51.720> can<22:58:51.960> be<22:58:52.080> performed<22:58:52.440> to<22:58:52.552> adapt<22:58:52.856> or 22:58:53.030 --> 22:58:53.040 align:start position:0% changes can be performed to adapt or 22:58:53.040 --> 22:58:55.310 align:start position:0% changes can be performed to adapt or change<22:58:53.216> business<22:58:53.576> needs<22:58:54.176> Hardware<22:58:54.536> software 22:58:55.310 --> 22:58:55.320 align:start position:0% change business needs Hardware software 22:58:55.320 --> 22:58:58.246 align:start position:0% change business needs Hardware software it<22:58:55.976> could<22:58:56.104> reactively<22:58:56.872> Implement<22:58:57.296> a<22:58:57.600> fix<22:58:57.896> if 22:58:58.246 --> 22:58:58.256 align:start position:0% it could reactively Implement a fix if 22:58:58.256 --> 22:59:00.710 align:start position:0% it could reactively Implement a fix if there's<22:58:58.440> some<22:58:58.680> sort<22:58:58.856> of<22:58:58.920> major<22:58:59.160> issue<22:59:00.120> or<22:59:00.480> bug 22:59:00.710 --> 22:59:00.720 align:start position:0% there's some sort of major issue or bug 22:59:00.720 --> 22:59:03.414 align:start position:0% there's some sort of major issue or bug or<22:59:01.440> attack<22:59:01.616> on<22:59:01.856> the<22:59:02.040> network 22:59:03.414 --> 22:59:03.424 align:start position:0% or attack on the network 22:59:03.424 --> 22:59:06.950 align:start position:0% or attack on the network normal<22:59:04.080> changes<22:59:04.680> for<22:59:04.920> example<22:59:05.280> a<22:59:06.000> a<22:59:06.232> normal 22:59:06.950 --> 22:59:06.960 align:start position:0% normal changes for example a a normal 22:59:06.960 --> 22:59:10.006 align:start position:0% normal changes for example a a normal configuration<22:59:07.736> or<22:59:08.160> server<22:59:08.512> maintenance 22:59:10.006 --> 22:59:10.016 align:start position:0% configuration or server maintenance 22:59:10.016 --> 22:59:11.566 align:start position:0% configuration or server maintenance and<22:59:10.496> something<22:59:10.800> that<22:59:11.040> it<22:59:11.160> was<22:59:11.336> generally 22:59:11.566 --> 22:59:11.576 align:start position:0% and something that it was generally 22:59:11.576 --> 22:59:12.774 align:start position:0% and something that it was generally expected 22:59:12.774 --> 22:59:12.784 align:start position:0% expected 22:59:12.784 --> 22:59:15.222 align:start position:0% expected standard<22:59:13.552> change<22:59:13.736> is<22:59:14.040> pre-approved<22:59:14.696> changes 22:59:15.222 --> 22:59:15.232 align:start position:0% standard change is pre-approved changes 22:59:15.232 --> 22:59:17.390 align:start position:0% standard change is pre-approved changes that<22:59:15.424> don't<22:59:15.600> require<22:59:15.784> approvals<22:59:16.616> these<22:59:17.336> are 22:59:17.390 --> 22:59:17.400 align:start position:0% that don't require approvals these are 22:59:17.400 --> 22:59:19.366 align:start position:0% that don't require approvals these are things<22:59:17.640> that<22:59:18.000> just<22:59:18.424> aren't<22:59:18.600> going<22:59:18.784> to<22:59:18.896> cause<22:59:19.080> a 22:59:19.366 --> 22:59:19.376 align:start position:0% things that just aren't going to cause a 22:59:19.376 --> 22:59:22.486 align:start position:0% things that just aren't going to cause a problem<22:59:19.824> usually<22:59:20.824> for<22:59:21.176> example 22:59:22.486 --> 22:59:22.496 align:start position:0% problem usually for example 22:59:22.496 --> 22:59:23.502 align:start position:0% problem usually for example um 22:59:23.502 --> 22:59:23.512 align:start position:0% um 22:59:23.512 --> 22:59:25.542 align:start position:0% um swapping<22:59:24.176> out<22:59:24.360> a<22:59:24.536> redundant<22:59:25.016> power<22:59:25.320> supply 22:59:25.542 --> 22:59:25.552 align:start position:0% swapping out a redundant power supply 22:59:25.552 --> 22:59:27.414 align:start position:0% swapping out a redundant power supply it's<22:59:25.976> just<22:59:26.160> not<22:59:26.280> going<22:59:26.464> to<22:59:26.576> have<22:59:26.696> any<22:59:26.872> impact 22:59:27.414 --> 22:59:27.424 align:start position:0% it's just not going to have any impact 22:59:27.424 --> 22:59:30.110 align:start position:0% it's just not going to have any impact and<22:59:28.376> it's<22:59:28.680> been<22:59:28.856> tested<22:59:29.216> for 22:59:30.110 --> 22:59:30.120 align:start position:0% and it's been tested for 22:59:30.120 --> 22:59:31.910 align:start position:0% and it's been tested for um in<22:59:30.480> the<22:59:30.600> past 22:59:31.910 --> 22:59:31.920 align:start position:0% um in the past 22:59:31.920 --> 22:59:34.134 align:start position:0% um in the past risk<22:59:32.640> associated<22:59:33.056> is<22:59:33.360> low<22:59:33.536> and<22:59:33.784> does<22:59:33.896> not<22:59:34.016> have 22:59:34.134 --> 22:59:34.144 align:start position:0% risk associated is low and does not have 22:59:34.144 --> 22:59:36.286 align:start position:0% risk associated is low and does not have enough<22:59:34.320> adverse<22:59:35.160> adverse<22:59:35.760> effect<22:59:35.872> on<22:59:36.120> the 22:59:36.286 --> 22:59:36.296 align:start position:0% enough adverse adverse effect on the 22:59:36.296 --> 22:59:37.366 align:start position:0% enough adverse adverse effect on the business 22:59:37.366 --> 22:59:37.376 align:start position:0% business 22:59:37.376 --> 22:59:40.006 align:start position:0% business emergency<22:59:38.360> these<22:59:39.360> are<22:59:39.480> changes<22:59:39.784> that<22:59:39.896> are 22:59:40.006 --> 22:59:40.016 align:start position:0% emergency these are changes that are 22:59:40.016 --> 22:59:42.110 align:start position:0% emergency these are changes that are implemented<22:59:40.496> on<22:59:40.800> an<22:59:41.104> urgent<22:59:41.336> basis<22:59:41.824> through 22:59:42.110 --> 22:59:42.120 align:start position:0% implemented on an urgent basis through 22:59:42.120 --> 22:59:44.502 align:start position:0% implemented on an urgent basis through and<22:59:42.536> remediate<22:59:43.144> a<22:59:43.320> problem<22:59:43.552> it's<22:59:44.216> normally 22:59:44.502 --> 22:59:44.512 align:start position:0% and remediate a problem it's normally 22:59:44.512 --> 22:59:47.030 align:start position:0% and remediate a problem it's normally Network<22:59:44.824> effect<22:59:45.176> in<22:59:45.600> business<22:59:45.896> affecting<22:59:46.552> and 22:59:47.030 --> 22:59:47.040 align:start position:0% Network effect in business affecting and 22:59:47.040 --> 22:59:49.670 align:start position:0% Network effect in business affecting and it<22:59:47.160> has<22:59:47.336> to<22:59:47.464> be<22:59:47.576> done<22:59:47.936> urgently<22:59:48.232> you<22:59:49.192> need<22:59:49.320> to 22:59:49.670 --> 22:59:49.680 align:start position:0% it has to be done urgently you need to 22:59:49.680 --> 22:59:51.710 align:start position:0% it has to be done urgently you need to have<22:59:49.976> approval<22:59:50.512> off<22:59:51.232> um<22:59:51.232> the<22:59:51.480> emergency 22:59:51.710 --> 22:59:51.720 align:start position:0% have approval off um the emergency 22:59:51.720 --> 22:59:54.414 align:start position:0% have approval off um the emergency change<22:59:52.496> Advisory<22:59:53.104> Board<22:59:53.336> and<22:59:54.176> they'll 22:59:54.414 --> 22:59:54.424 align:start position:0% change Advisory Board and they'll 22:59:54.424 --> 22:59:56.030 align:start position:0% change Advisory Board and they'll normally<22:59:54.656> have<22:59:54.896> either<22:59:55.080> a<22:59:55.376> video<22:59:55.504> conference 22:59:56.030 --> 22:59:56.040 align:start position:0% normally have either a video conference 22:59:56.040 --> 22:59:57.590 align:start position:0% normally have either a video conference or<22:59:56.280> a<22:59:56.400> quick<22:59:56.512> meeting 22:59:57.590 --> 22:59:57.600 align:start position:0% or a quick meeting 22:59:57.600 --> 23:00:00.350 align:start position:0% or a quick meeting in<22:59:58.144> order<22:59:58.320> to<22:59:58.440> talk<22:59:58.736> about<22:59:58.920> the<22:59:59.760> impact<23:00:00.000> on<23:00:00.176> the 23:00:00.350 --> 23:00:00.360 align:start position:0% in order to talk about the impact on the 23:00:00.360 --> 23:00:01.790 align:start position:0% in order to talk about the impact on the business<23:00:00.480> because<23:00:00.896> you<23:00:01.080> need<23:00:01.192> to<23:00:01.256> look<23:00:01.376> at<23:00:01.552> the 23:00:01.790 --> 23:00:01.800 align:start position:0% business because you need to look at the 23:00:01.800 --> 23:00:02.862 align:start position:0% business because you need to look at the entire 23:00:02.862 --> 23:00:02.872 align:start position:0% entire 23:00:02.872 --> 23:00:04.454 align:start position:0% entire um<23:00:03.000> structure 23:00:04.454 --> 23:00:04.464 align:start position:0% um structure 23:00:04.464 --> 23:00:07.006 align:start position:0% um structure documentation<23:00:05.464> a<23:00:06.000> change<23:00:06.176> request<23:00:06.656> is 23:00:07.006 --> 23:00:07.016 align:start position:0% documentation a change request is 23:00:07.016 --> 23:00:09.414 align:start position:0% documentation a change request is documented<23:00:07.616> using<23:00:07.976> applications 23:00:09.414 --> 23:00:09.424 align:start position:0% documented using applications 23:00:09.424 --> 23:00:11.814 align:start position:0% documented using applications there's<23:00:10.144> a<23:00:10.376> variety<23:00:10.976> of 23:00:11.814 --> 23:00:11.824 align:start position:0% there's a variety of 23:00:11.824 --> 23:00:14.150 align:start position:0% there's a variety of um applications<23:00:12.784> you<23:00:13.144> can<23:00:13.256> use 23:00:14.150 --> 23:00:14.160 align:start position:0% um applications you can use 23:00:14.160 --> 23:00:16.246 align:start position:0% um applications you can use the<23:00:14.576> documentary<23:00:15.056> change<23:00:15.232> request<23:00:15.600> is<23:00:15.896> caused 23:00:16.246 --> 23:00:16.256 align:start position:0% the documentary change request is caused 23:00:16.256 --> 23:00:18.046 align:start position:0% the documentary change request is caused a<23:00:16.376> change<23:00:16.496> record<23:00:16.800> it<23:00:17.104> could<23:00:17.216> be<23:00:17.336> online<23:00:17.640> or 23:00:18.046 --> 23:00:18.056 align:start position:0% a change record it could be online or 23:00:18.056 --> 23:00:20.326 align:start position:0% a change record it could be online or printed<23:00:18.536> issues<23:00:19.504> to<23:00:19.616> track<23:00:19.800> the<23:00:19.976> chains 23:00:20.326 --> 23:00:20.336 align:start position:0% printed issues to track the chains 23:00:20.336 --> 23:00:21.950 align:start position:0% printed issues to track the chains throughout<23:00:20.640> its<23:00:20.936> life<23:00:21.120> cycle<23:00:21.424> from<23:00:21.720> beginning 23:00:21.950 --> 23:00:21.960 align:start position:0% throughout its life cycle from beginning 23:00:21.960 --> 23:00:23.454 align:start position:0% throughout its life cycle from beginning to<23:00:22.320> end 23:00:23.454 --> 23:00:23.464 align:start position:0% to end 23:00:23.464 --> 23:00:25.430 align:start position:0% to end this<23:00:23.936> is<23:00:24.000> so<23:00:24.176> we've<23:00:24.360> got<23:00:24.480> an<23:00:24.600> audit<23:00:24.960> trail<23:00:25.144> of 23:00:25.430 --> 23:00:25.440 align:start position:0% this is so we've got an audit trail of 23:00:25.440 --> 23:00:27.166 align:start position:0% this is so we've got an audit trail of what<23:00:25.680> happened<23:00:25.920> and<23:00:26.160> who<23:00:26.400> did<23:00:26.576> what<23:00:26.760> and<23:00:26.936> who 23:00:27.166 --> 23:00:27.176 align:start position:0% what happened and who did what and who 23:00:27.176 --> 23:00:28.726 align:start position:0% what happened and who did what and who approved<23:00:27.600> it<23:00:27.784> and 23:00:28.726 --> 23:00:28.736 align:start position:0% approved it and 23:00:28.736 --> 23:00:31.366 align:start position:0% approved it and Etc<23:00:28.936> the<23:00:29.936> change<23:00:30.056> record<23:00:30.424> contains<23:00:31.144> key 23:00:31.366 --> 23:00:31.376 align:start position:0% Etc the change record contains key 23:00:31.376 --> 23:00:33.286 align:start position:0% Etc the change record contains key details<23:00:31.800> of<23:00:31.976> the<23:00:32.104> change<23:00:32.280> including<23:00:32.872> detail 23:00:33.286 --> 23:00:33.296 align:start position:0% details of the change including detail 23:00:33.296 --> 23:00:36.526 align:start position:0% details of the change including detail tech<23:00:33.736> technical<23:00:34.736> implementation 23:00:36.526 --> 23:00:36.536 align:start position:0% tech technical implementation 23:00:36.536 --> 23:00:38.686 align:start position:0% tech technical implementation the<23:00:37.080> the<23:00:37.080> technical<23:00:37.616> parts<23:00:37.856> will<23:00:38.160> probably<23:00:38.336> be 23:00:38.686 --> 23:00:38.696 align:start position:0% the the technical parts will probably be 23:00:38.696 --> 23:00:41.502 align:start position:0% the the technical parts will probably be read<23:00:39.120> by<23:00:39.536> the<23:00:40.080> um<23:00:40.080> the<23:00:40.440> it<23:00:40.552> managers<23:00:41.280> and 23:00:41.502 --> 23:00:41.512 align:start position:0% read by the um the it managers and 23:00:41.512 --> 23:00:44.390 align:start position:0% read by the um the it managers and Technical<23:00:41.872> team<23:00:42.296> but<23:00:42.960> they're<23:00:43.192> there<23:00:43.920> um<23:00:43.976> for 23:00:44.390 --> 23:00:44.400 align:start position:0% Technical team but they're there um for 23:00:44.400 --> 23:00:46.486 align:start position:0% Technical team but they're there um for the<23:00:44.576> record 23:00:46.486 --> 23:00:46.496 align:start position:0% the record 23:00:46.496 --> 23:00:49.310 align:start position:0% the record key<23:00:47.104> details<23:00:47.640> is<23:00:47.760> who<23:00:48.056> requested<23:00:48.536> it<23:00:48.720> why<23:00:49.144> did 23:00:49.310 --> 23:00:49.320 align:start position:0% key details is who requested it why did 23:00:49.320 --> 23:00:51.590 align:start position:0% key details is who requested it why did they<23:00:49.504> request<23:00:49.856> it<23:00:50.104> what's<23:00:51.000> the<23:00:51.232> outcome 23:00:51.590 --> 23:00:51.600 align:start position:0% they request it what's the outcome 23:00:51.600 --> 23:00:53.270 align:start position:0% they request it what's the outcome what's<23:00:51.896> the<23:00:52.144> point<23:00:52.320> of<23:00:52.440> doing<23:00:52.552> it<23:00:52.800> is<23:00:52.976> there<23:00:53.104> a 23:00:53.270 --> 23:00:53.280 align:start position:0% what's the point of doing it is there a 23:00:53.280 --> 23:00:54.774 align:start position:0% what's the point of doing it is there a business<23:00:53.400> benefit<23:00:53.760> or<23:00:54.296> is<23:00:54.424> it<23:00:54.600> going<23:00:54.656> to 23:00:54.774 --> 23:00:54.784 align:start position:0% business benefit or is it going to 23:00:54.784 --> 23:00:56.990 align:start position:0% business benefit or is it going to prevent<23:00:54.960> something<23:00:55.192> more<23:00:55.552> serious<23:00:55.920> happening 23:00:56.990 --> 23:00:57.000 align:start position:0% prevent something more serious happening 23:00:57.000 --> 23:00:59.926 align:start position:0% prevent something more serious happening what<23:00:57.480> are<23:00:57.600> the<23:00:57.720> risks<23:00:58.016> involved 23:00:59.926 --> 23:00:59.936 align:start position:0% what are the risks involved 23:00:59.936 --> 23:01:02.686 align:start position:0% what are the risks involved what<23:01:00.424> resources<23:01:00.896> that<23:01:01.552> includes<23:01:01.976> the<23:01:02.160> teams 23:01:02.686 --> 23:01:02.696 align:start position:0% what resources that includes the teams 23:01:02.696 --> 23:01:04.726 align:start position:0% what resources that includes the teams human<23:01:02.936> resources<23:01:03.600> and<23:01:03.960> physical<23:01:04.144> and 23:01:04.726 --> 23:01:04.736 align:start position:0% human resources and physical and 23:01:04.736 --> 23:01:06.646 align:start position:0% human resources and physical and software<23:01:05.040> resources 23:01:06.646 --> 23:01:06.656 align:start position:0% software resources 23:01:06.656 --> 23:01:08.814 align:start position:0% software resources for<23:01:07.144> example<23:01:07.376> a<23:01:07.856> network<23:01:08.160> card<23:01:08.464> needs 23:01:08.814 --> 23:01:08.824 align:start position:0% for example a network card needs 23:01:08.824 --> 23:01:11.454 align:start position:0% for example a network card needs replacing<23:01:09.360> or<23:01:10.192> an<23:01:10.496> update<23:01:10.736> required<23:01:11.160> for<23:01:11.280> the 23:01:11.454 --> 23:01:11.464 align:start position:0% replacing or an update required for the 23:01:11.464 --> 23:01:12.526 align:start position:0% replacing or an update required for the software 23:01:12.526 --> 23:01:12.536 align:start position:0% software 23:01:12.536 --> 23:01:14.686 align:start position:0% software who's<23:01:13.080> responsible<23:01:13.616> for<23:01:13.920> building<23:01:14.104> testing 23:01:14.686 --> 23:01:14.696 align:start position:0% who's responsible for building testing 23:01:14.696 --> 23:01:17.270 align:start position:0% who's responsible for building testing and<23:01:14.936> implementing<23:01:15.656> what's<23:01:16.616> the<23:01:16.856> relationship 23:01:17.270 --> 23:01:17.280 align:start position:0% and implementing what's the relationship 23:01:17.280 --> 23:01:19.430 align:start position:0% and implementing what's the relationship between<23:01:17.576> this<23:01:17.936> change<23:01:18.120> and<23:01:18.360> other<23:01:18.600> changes<23:01:19.144> is 23:01:19.430 --> 23:01:19.440 align:start position:0% between this change and other changes is 23:01:19.440 --> 23:01:22.726 align:start position:0% between this change and other changes is it<23:01:19.616> one<23:01:19.856> of<23:01:20.040> a<23:01:20.160> series 23:01:22.726 --> 23:01:22.736 align:start position:0% 23:01:22.736 --> 23:01:24.774 align:start position:0% so<23:01:23.400> the<23:01:23.512> effect<23:01:23.696> of<23:01:23.872> one<23:01:24.056> change<23:01:24.296> on<23:01:24.536> another 23:01:24.774 --> 23:01:24.784 align:start position:0% so the effect of one change on another 23:01:24.784 --> 23:01:27.710 align:start position:0% so the effect of one change on another for<23:01:25.144> example<23:01:25.376> if<23:01:25.552> you<23:01:25.736> update<23:01:26.216> a<23:01:26.760> VLAN<23:01:27.360> on<23:01:27.536> a 23:01:27.710 --> 23:01:27.720 align:start position:0% for example if you update a VLAN on a 23:01:27.720 --> 23:01:30.166 align:start position:0% for example if you update a VLAN on a certain<23:01:27.832> device<23:01:28.400> what<23:01:29.400> devices<23:01:29.760> what 23:01:30.166 --> 23:01:30.176 align:start position:0% certain device what devices what 23:01:30.176 --> 23:01:31.790 align:start position:0% certain device what devices what physical<23:01:30.360> ports<23:01:30.896> are<23:01:31.016> going<23:01:31.144> to<23:01:31.256> be<23:01:31.320> affected 23:01:31.790 --> 23:01:31.800 align:start position:0% physical ports are going to be affected 23:01:31.800 --> 23:01:34.182 align:start position:0% physical ports are going to be affected is<23:01:32.512> the<23:01:32.696> VLAN<23:01:33.056> going<23:01:33.232> to<23:01:33.296> be<23:01:33.424> propagated<23:01:33.896> on 23:01:34.182 --> 23:01:34.192 align:start position:0% is the VLAN going to be propagated on 23:01:34.192 --> 23:01:35.686 align:start position:0% is the VLAN going to be propagated on other<23:01:34.376> switches<23:01:34.920> or<23:01:35.104> does<23:01:35.216> it<23:01:35.336> need<23:01:35.464> to<23:01:35.512> be 23:01:35.686 --> 23:01:35.696 align:start position:0% other switches or does it need to be 23:01:35.696 --> 23:01:37.310 align:start position:0% other switches or does it need to be blocked 23:01:37.310 --> 23:01:37.320 align:start position:0% blocked 23:01:37.320 --> 23:01:38.926 align:start position:0% blocked maintenance<23:01:37.920> window<23:01:38.160> I'm<23:01:38.336> sure<23:01:38.512> you've<23:01:38.760> heard 23:01:38.926 --> 23:01:38.936 align:start position:0% maintenance window I'm sure you've heard 23:01:38.936 --> 23:01:41.270 align:start position:0% maintenance window I'm sure you've heard of<23:01:39.176> it's<23:01:39.480> an<23:01:39.656> agreed<23:01:40.144> period<23:01:40.552> of<23:01:40.736> time<23:01:40.920> in 23:01:41.270 --> 23:01:41.280 align:start position:0% of it's an agreed period of time in 23:01:41.280 --> 23:01:42.774 align:start position:0% of it's an agreed period of time in which<23:01:41.512> is<23:01:41.872> going<23:01:42.176> to<23:01:42.232> have<23:01:42.360> minimal 23:01:42.774 --> 23:01:42.784 align:start position:0% which is going to have minimal 23:01:42.784 --> 23:01:44.390 align:start position:0% which is going to have minimal disruption 23:01:44.390 --> 23:01:44.400 align:start position:0% disruption 23:01:44.400 --> 23:01:47.030 align:start position:0% disruption normally<23:01:45.232> done<23:01:45.480> on<23:01:45.720> the<23:01:45.832> weekends<23:01:46.376> or<23:01:46.616> out<23:01:46.856> of 23:01:47.030 --> 23:01:47.040 align:start position:0% normally done on the weekends or out of 23:01:47.040 --> 23:01:49.686 align:start position:0% normally done on the weekends or out of hours<23:01:47.216> just<23:01:48.120> depends<23:01:48.536> on<23:01:48.656> your<23:01:48.784> business<23:01:49.016> uh 23:01:49.686 --> 23:01:49.696 align:start position:0% hours just depends on your business uh 23:01:49.696 --> 23:01:52.606 align:start position:0% hours just depends on your business uh procedures<23:01:50.696> the<23:01:51.600> author<23:01:51.960> authorized 23:01:52.606 --> 23:01:52.616 align:start position:0% procedures the author authorized 23:01:52.616 --> 23:01:54.166 align:start position:0% procedures the author authorized maintenance<23:01:52.920> Windows<23:01:53.336> predetermined<23:01:54.056> and 23:01:54.166 --> 23:01:54.176 align:start position:0% maintenance Windows predetermined and 23:01:54.176 --> 23:01:56.326 align:start position:0% maintenance Windows predetermined and pre-approved<23:01:54.720> to<23:01:54.896> carry<23:01:55.144> out<23:01:55.256> the<23:01:55.504> change<23:01:55.680> a 23:01:56.326 --> 23:01:56.336 align:start position:0% pre-approved to carry out the change a 23:01:56.336 --> 23:01:57.470 align:start position:0% pre-approved to carry out the change a lot<23:01:56.512> of<23:01:56.576> the<23:01:56.696> time 23:01:57.470 --> 23:01:57.480 align:start position:0% lot of the time 23:01:57.480 --> 23:01:59.094 align:start position:0% lot of the time um an<23:01:57.832> alternative 23:01:59.094 --> 23:01:59.104 align:start position:0% um an alternative 23:01:59.104 --> 23:02:02.686 align:start position:0% um an alternative our<23:01:59.696> server<23:02:00.176> is<23:02:00.296> used<23:02:00.600> or<23:02:01.144> whatever 23:02:02.686 --> 23:02:02.696 align:start position:0% our server is used or whatever 23:02:02.696 --> 23:02:03.286 align:start position:0% our server is used or whatever um 23:02:03.286 --> 23:02:03.296 align:start position:0% um 23:02:03.296 --> 23:02:04.670 align:start position:0% um you<23:02:03.784> could<23:02:03.896> have<23:02:04.016> some<23:02:04.192> sort<23:02:04.320> of<23:02:04.440> load 23:02:04.670 --> 23:02:04.680 align:start position:0% you could have some sort of load 23:02:04.680 --> 23:02:06.950 align:start position:0% you could have some sort of load balancer<23:02:05.160> used<23:02:05.464> on<23:02:06.056> all<23:02:06.232> traffic<23:02:06.480> is<23:02:06.784> just 23:02:06.950 --> 23:02:06.960 align:start position:0% balancer used on all traffic is just 23:02:06.960 --> 23:02:09.950 align:start position:0% balancer used on all traffic is just sent<23:02:07.144> through<23:02:07.376> one<23:02:07.920> of<23:02:08.400> the<23:02:08.576> load<23:02:08.824> balances<23:02:09.360> so 23:02:09.950 --> 23:02:09.960 align:start position:0% sent through one of the load balances so 23:02:09.960 --> 23:02:11.862 align:start position:0% sent through one of the load balances so the<23:02:10.192> change<23:02:10.616> could<23:02:10.920> actually<23:02:11.040> be<23:02:11.280> transparent 23:02:11.862 --> 23:02:11.872 align:start position:0% the change could actually be transparent 23:02:11.872 --> 23:02:13.542 align:start position:0% the change could actually be transparent to<23:02:12.056> users 23:02:13.542 --> 23:02:13.552 align:start position:0% to users 23:02:13.552 --> 23:02:15.414 align:start position:0% to users generally<23:02:14.104> changes<23:02:14.512> during<23:02:14.696> weekdays<23:02:15.296> are 23:02:15.414 --> 23:02:15.424 align:start position:0% generally changes during weekdays are 23:02:15.424 --> 23:02:17.862 align:start position:0% generally changes during weekdays are scheduled<23:02:15.784> after<23:02:15.896> business<23:02:16.256> hours<23:02:16.872> critical 23:02:17.862 --> 23:02:17.872 align:start position:0% scheduled after business hours critical 23:02:17.872 --> 23:02:20.150 align:start position:0% scheduled after business hours critical changes<23:02:18.360> Friday<23:02:18.656> nights<23:02:19.256> and<23:02:19.680> they<23:02:19.856> can<23:02:19.976> run 23:02:20.150 --> 23:02:20.160 align:start position:0% changes Friday nights and they can run 23:02:20.160 --> 23:02:22.486 align:start position:0% changes Friday nights and they can run into<23:02:20.280> the<23:02:20.512> weekend<23:02:20.640> so<23:02:21.360> you<23:02:21.896> can<23:02:22.016> roll<23:02:22.256> back 23:02:22.486 --> 23:02:22.496 align:start position:0% into the weekend so you can roll back 23:02:22.496 --> 23:02:25.182 align:start position:0% into the weekend so you can roll back and<23:02:22.736> recover<23:02:23.040> if<23:02:23.280> there's<23:02:23.400> an<23:02:23.640> issue 23:02:25.182 --> 23:02:25.192 align:start position:0% and recover if there's an issue 23:02:25.192 --> 23:02:27.886 align:start position:0% and recover if there's an issue or<23:02:25.680> changes<23:02:26.160> to<23:02:26.336> service<23:02:26.576> assets<23:02:27.360> and<23:02:27.600> config 23:02:27.886 --> 23:02:27.896 align:start position:0% or changes to service assets and config 23:02:27.896 --> 23:02:31.006 align:start position:0% or changes to service assets and config configuration<23:02:28.936> items<23:02:29.936> are<23:02:30.120> recorded<23:02:30.536> in<23:02:30.784> the 23:02:31.006 --> 23:02:31.016 align:start position:0% configuration items are recorded in the 23:02:31.016 --> 23:02:34.246 align:start position:0% configuration items are recorded in the configuration<23:02:31.680> management<23:02:32.104> system 23:02:34.246 --> 23:02:34.256 align:start position:0% configuration management system 23:02:34.256 --> 23:02:36.526 align:start position:0% configuration management system uh<23:02:34.976> server<23:02:35.400> can<23:02:35.576> move<23:02:35.760> from<23:02:36.000> pre-production 23:02:36.526 --> 23:02:36.536 align:start position:0% uh server can move from pre-production 23:02:36.536 --> 23:02:38.326 align:start position:0% uh server can move from pre-production to<23:02:36.832> production<23:02:37.192> with<23:02:37.440> a<23:02:37.616> formal<23:02:37.920> sign<23:02:38.104> off 23:02:38.326 --> 23:02:38.336 align:start position:0% to production with a formal sign off 23:02:38.336 --> 23:02:41.030 align:start position:0% to production with a formal sign off before<23:02:38.760> it's<23:02:38.936> accepted<23:02:39.424> into<23:02:39.600> production 23:02:41.030 --> 23:02:41.040 align:start position:0% before it's accepted into production 23:02:41.040 --> 23:02:43.310 align:start position:0% before it's accepted into production such<23:02:41.464> changes<23:02:42.000> are<23:02:42.232> to<23:02:42.424> be<23:02:42.600> documented<23:02:43.080> for 23:02:43.310 --> 23:02:43.320 align:start position:0% such changes are to be documented for 23:02:43.320 --> 23:02:45.222 align:start position:0% such changes are to be documented for timely<23:02:43.680> support<23:02:43.976> so<23:02:44.280> everyone<23:02:44.512> needs<23:02:44.936> to<23:02:45.000> know 23:02:45.222 --> 23:02:45.232 align:start position:0% timely support so everyone needs to know 23:02:45.232 --> 23:02:47.206 align:start position:0% timely support so everyone needs to know about<23:02:45.832> the<23:02:46.080> fact<23:02:46.144> this<23:02:46.376> new<23:02:46.552> server<23:02:46.920> has<23:02:47.040> been 23:02:47.206 --> 23:02:47.216 align:start position:0% about the fact this new server has been 23:02:47.216 --> 23:02:49.246 align:start position:0% about the fact this new server has been introduced<23:02:47.760> the<23:02:48.360> configuration<23:02:48.896> settings 23:02:49.246 --> 23:02:49.256 align:start position:0% introduced the configuration settings 23:02:49.256 --> 23:02:51.950 align:start position:0% introduced the configuration settings and<23:02:49.976> what<23:02:50.160> the<23:02:50.336> possible<23:02:50.640> risks<23:02:51.176> are<23:02:51.360> and<23:02:51.832> what 23:02:51.950 --> 23:02:51.960 align:start position:0% and what the possible risks are and what 23:02:51.960 --> 23:02:55.430 align:start position:0% and what the possible risks are and what we<23:02:52.080> do<23:02:52.256> if<23:02:52.440> there<23:02:52.616> is<23:02:52.800> a<23:02:53.040> an<23:02:53.336> issue 23:02:55.430 --> 23:02:55.440 align:start position:0% we do if there is a an issue 23:02:55.440 --> 23:02:57.526 align:start position:0% we do if there is a an issue our<23:02:55.856> rollback<23:02:56.216> is<23:02:56.512> basically<23:02:56.824> going<23:02:57.120> back<23:02:57.296> to 23:02:57.526 --> 23:02:57.536 align:start position:0% our rollback is basically going back to 23:02:57.536 --> 23:02:59.862 align:start position:0% our rollback is basically going back to how<23:02:57.784> we<23:02:58.016> were<23:02:58.376> before<23:02:58.920> this<23:02:59.336> change<23:02:59.464> happened 23:02:59.862 --> 23:02:59.872 align:start position:0% how we were before this change happened 23:02:59.872 --> 23:03:03.110 align:start position:0% how we were before this change happened not<23:03:00.656> always<23:03:00.896> possible<23:03:01.376> obviously<23:03:02.120> especially 23:03:03.110 --> 23:03:03.120 align:start position:0% not always possible obviously especially 23:03:03.120 --> 23:03:05.030 align:start position:0% not always possible obviously especially if<23:03:03.424> something's<23:03:03.832> completely<23:03:04.192> broken<23:03:04.496> and<23:03:04.856> has 23:03:05.030 --> 23:03:05.040 align:start position:0% if something's completely broken and has 23:03:05.040 --> 23:03:07.006 align:start position:0% if something's completely broken and has to<23:03:05.160> be<23:03:05.280> replaced<23:03:05.936> and<23:03:06.480> then<23:03:06.600> the<23:03:06.832> replacement 23:03:07.006 --> 23:03:07.016 align:start position:0% to be replaced and then the replacement 23:03:07.016 --> 23:03:12.470 align:start position:0% to be replaced and then the replacement for<23:03:07.680> example<23:03:07.856> is<23:03:08.160> broken<23:03:08.400> also 23:03:12.470 --> 23:03:12.480 align:start position:0% 23:03:12.480 --> 23:03:14.566 align:start position:0% okay<23:03:13.192> so<23:03:13.504> worst<23:03:13.856> case<23:03:13.976> there's<23:03:14.216> a<23:03:14.464> site 23:03:14.566 --> 23:03:14.576 align:start position:0% okay so worst case there's a site 23:03:14.576 --> 23:03:16.910 align:start position:0% okay so worst case there's a site failover<23:03:15.056> or<23:03:15.360> business<23:03:15.536> continuity<23:03:16.376> plan<23:03:16.616> may 23:03:16.910 --> 23:03:16.920 align:start position:0% failover or business continuity plan may 23:03:16.920 --> 23:03:20.270 align:start position:0% failover or business continuity plan may be<23:03:17.104> invoked<23:03:17.576> this<23:03:18.000> is<23:03:18.120> if<23:03:18.424> the<23:03:18.832> entire<23:03:19.280> core 23:03:20.270 --> 23:03:20.280 align:start position:0% be invoked this is if the entire core 23:03:20.280 --> 23:03:22.846 align:start position:0% be invoked this is if the entire core system<23:03:20.872> goes<23:03:21.424> down<23:03:21.600> is<23:03:22.256> there<23:03:22.440> some<23:03:22.616> sort<23:03:22.736> of 23:03:22.846 --> 23:03:22.856 align:start position:0% system goes down is there some sort of 23:03:22.856 --> 23:03:25.006 align:start position:0% system goes down is there some sort of backup<23:03:23.104> in<23:03:23.280> place<23:03:23.464> or<23:03:23.640> what<23:03:23.824> do<23:03:23.936> we<23:03:24.056> do 23:03:25.006 --> 23:03:25.016 align:start position:0% backup in place or what do we do 23:03:25.016 --> 23:03:28.134 align:start position:0% backup in place or what do we do looking<23:03:25.376> at<23:03:25.552> the<23:03:25.800> impact 23:03:28.134 --> 23:03:28.144 align:start position:0% looking at the impact 23:03:28.144 --> 23:03:30.886 align:start position:0% looking at the impact there's<23:03:28.552> a<23:03:28.800> matrix<23:03:29.160> low<23:03:29.640> impact<23:03:30.056> and<23:03:30.296> low<23:03:30.480> risk 23:03:30.886 --> 23:03:30.896 align:start position:0% there's a matrix low impact and low risk 23:03:30.896 --> 23:03:33.166 align:start position:0% there's a matrix low impact and low risk category<23:03:31.376> for<23:03:31.680> going<23:03:32.336> all<23:03:32.696> the<23:03:32.872> way<23:03:32.936> to 23:03:33.166 --> 23:03:33.176 align:start position:0% category for going all the way to 23:03:33.176 --> 23:03:35.750 align:start position:0% category for going all the way to category<23:03:33.600> one<23:03:33.896> which<23:03:34.144> is<23:03:34.320> high<23:03:34.496> impact<23:03:34.920> high 23:03:35.750 --> 23:03:35.760 align:start position:0% category one which is high impact high 23:03:35.760 --> 23:03:37.846 align:start position:0% category one which is high impact high risk<23:03:36.056> and<23:03:36.176> it's<23:03:36.360> a<23:03:36.536> critical<23:03:36.832> category<23:03:37.376> low 23:03:37.846 --> 23:03:37.856 align:start position:0% risk and it's a critical category low 23:03:37.856 --> 23:03:40.430 align:start position:0% risk and it's a critical category low medium<23:03:38.280> high<23:03:38.512> and<23:03:38.696> critical 23:03:40.430 --> 23:03:40.440 align:start position:0% medium high and critical 23:03:40.440 --> 23:03:43.246 align:start position:0% medium high and critical the<23:03:41.400> notification<23:03:41.936> to<23:03:42.176> change<23:03:42.424> is<23:03:42.784> published 23:03:43.246 --> 23:03:43.256 align:start position:0% the notification to change is published 23:03:43.256 --> 23:03:44.990 align:start position:0% the notification to change is published with<23:03:43.504> the<23:03:43.680> details<23:03:43.976> of<23:03:44.040> the<23:03:44.160> change<23:03:44.400> activity 23:03:44.990 --> 23:03:45.000 align:start position:0% with the details of the change activity 23:03:45.000 --> 23:03:47.630 align:start position:0% with the details of the change activity the<23:03:45.720> window<23:03:45.832> of<23:03:46.192> the<23:03:46.320> change<23:03:46.552> obviously<23:03:47.464> it 23:03:47.630 --> 23:03:47.640 align:start position:0% the window of the change obviously it 23:03:47.640 --> 23:03:49.246 align:start position:0% the window of the change obviously it only<23:03:47.872> goes<23:03:48.176> out<23:03:48.232> to<23:03:48.424> the<23:03:48.600> people<23:03:48.784> that<23:03:49.080> are 23:03:49.246 --> 23:03:49.256 align:start position:0% only goes out to the people that are 23:03:49.256 --> 23:03:51.646 align:start position:0% only goes out to the people that are going<23:03:49.504> to<23:03:49.616> be<23:03:49.736> impacted 23:03:51.646 --> 23:03:51.656 align:start position:0% going to be impacted 23:03:51.656 --> 23:03:52.966 align:start position:0% going to be impacted all<23:03:52.016> right<23:03:52.144> so<23:03:52.256> we've<23:03:52.440> looked<23:03:52.680> at<23:03:52.736> change 23:03:52.966 --> 23:03:52.976 align:start position:0% all right so we've looked at change 23:03:52.976 --> 23:03:55.134 align:start position:0% all right so we've looked at change change<23:03:53.336> management<23:03:53.696> types<23:03:54.480> of<23:03:54.600> changes<23:03:54.960> and 23:03:55.134 --> 23:03:55.144 align:start position:0% change management types of changes and 23:03:55.144 --> 23:03:57.886 align:start position:0% change management types of changes and approvals<23:03:55.680> what<23:03:55.976> is<23:03:56.160> documentation 23:03:57.886 --> 23:03:57.896 align:start position:0% approvals what is documentation 23:03:57.896 --> 23:03:59.710 align:start position:0% approvals what is documentation what<23:03:58.256> is<23:03:58.376> a<23:03:58.552> maintenance<23:03:58.856> window 23:03:59.710 --> 23:03:59.720 align:start position:0% what is a maintenance window 23:03:59.720 --> 23:04:02.206 align:start position:0% what is a maintenance window configuration<23:04:00.720> procedures<23:04:01.320> and<23:04:01.504> rollbacks 23:04:02.206 --> 23:04:02.216 align:start position:0% configuration procedures and rollbacks 23:04:02.216 --> 23:04:04.966 align:start position:0% configuration procedures and rollbacks impact<23:04:03.000> and<23:04:03.720> the<23:04:03.896> notification<23:04:04.440> to<23:04:04.736> change 23:04:04.966 --> 23:04:04.976 align:start position:0% impact and the notification to change 23:04:04.976 --> 23:04:10.070 align:start position:0% impact and the notification to change that's<23:04:05.760> all<23:04:06.000> for<23:04:06.176> now<23:04:06.296> thanks<23:04:06.656> for<23:04:06.784> watching 23:04:10.070 --> 23:04:10.080 align:start position:0% 23:04:10.080 --> 23:04:19.750 align:start position:0% [Music] 23:04:19.750 --> 23:04:19.760 align:start position:0% 23:04:19.760 --> 23:04:27.470 align:start position:0% thank<23:04:20.760> you 23:04:27.470 --> 23:04:27.480 align:start position:0% 23:04:27.480 --> 23:04:30.590 align:start position:0% welcome<23:04:28.144> to<23:04:28.320> module<23:04:28.800> 21<23:04:28.920> lesson<23:04:29.576> one<23:04:29.760> Internet 23:04:30.590 --> 23:04:30.600 align:start position:0% welcome to module 21 lesson one Internet 23:04:30.600 --> 23:04:33.222 align:start position:0% welcome to module 21 lesson one Internet of<23:04:31.016> Things<23:04:31.256> Technologies<23:04:32.104> this<23:04:32.824> is<23:04:33.000> one<23:04:33.120> of 23:04:33.222 --> 23:04:33.232 align:start position:0% of Things Technologies this is one of 23:04:33.232 --> 23:04:35.630 align:start position:0% of Things Technologies this is one of the<23:04:33.296> new<23:04:33.424> subjects<23:04:33.896> has<23:04:34.016> been<23:04:34.256> added<23:04:34.552> to<23:04:35.336> the 23:04:35.630 --> 23:04:35.640 align:start position:0% the new subjects has been added to the 23:04:35.640 --> 23:04:38.326 align:start position:0% the new subjects has been added to the latest<23:04:35.960> uh<23:04:36.960> come<23:04:37.144> to<23:04:37.320> exam 23:04:38.326 --> 23:04:38.336 align:start position:0% latest uh come to exam 23:04:38.336 --> 23:04:40.366 align:start position:0% latest uh come to exam they<23:04:38.696> just<23:04:38.872> expected<23:04:39.360> to<23:04:39.424> have<23:04:39.536> an<23:04:40.144> overview 23:04:40.366 --> 23:04:40.376 align:start position:0% they just expected to have an overview 23:04:40.376 --> 23:04:42.414 align:start position:0% they just expected to have an overview of<23:04:40.616> what<23:04:40.856> these<23:04:41.104> things<23:04:41.216> do<23:04:41.512> rather<23:04:41.872> than<23:04:42.000> any 23:04:42.414 --> 23:04:42.424 align:start position:0% of what these things do rather than any 23:04:42.424 --> 23:04:44.686 align:start position:0% of what these things do rather than any detail<23:04:42.960> because<23:04:43.144> there's<23:04:43.376> quite<23:04:43.616> a<23:04:43.800> diverse 23:04:44.686 --> 23:04:44.696 align:start position:0% detail because there's quite a diverse 23:04:44.696 --> 23:04:48.286 align:start position:0% detail because there's quite a diverse array<23:04:45.056> of<23:04:45.176> protocols<23:04:46.080> here<23:04:46.280> said<23:04:47.280> wave<23:04:47.824> and 23:04:48.286 --> 23:04:48.296 align:start position:0% array of protocols here said wave and 23:04:48.296 --> 23:04:50.750 align:start position:0% array of protocols here said wave and plus<23:04:48.600> Bluetooth<23:04:49.320> which<23:04:49.976> I'm<23:04:50.160> sure<23:04:50.512> you've 23:04:50.750 --> 23:04:50.760 align:start position:0% plus Bluetooth which I'm sure you've 23:04:50.760 --> 23:04:53.094 align:start position:0% plus Bluetooth which I'm sure you've heard<23:04:50.872> of<23:04:51.120> NFC 23:04:53.094 --> 23:04:53.104 align:start position:0% heard of NFC 23:04:53.104 --> 23:04:54.822 align:start position:0% heard of NFC uh<23:04:53.640> infrared 23:04:54.822 --> 23:04:54.832 align:start position:0% uh infrared 23:04:54.832 --> 23:04:57.110 align:start position:0% uh infrared RFID 23:04:57.110 --> 23:04:57.120 align:start position:0% RFID 23:04:57.120 --> 23:04:59.094 align:start position:0% RFID so<23:04:57.656> Internet<23:04:57.832> of<23:04:58.256> Things 23:04:59.094 --> 23:04:59.104 align:start position:0% so Internet of Things 23:04:59.104 --> 23:05:01.910 align:start position:0% so Internet of Things it's<23:04:59.696> a<23:04:59.936> network<23:05:00.056> of<23:05:00.360> devices<23:05:00.920> appliances 23:05:01.910 --> 23:05:01.920 align:start position:0% it's a network of devices appliances 23:05:01.920 --> 23:05:05.030 align:start position:0% it's a network of devices appliances Vehicles<23:05:02.576> physical<23:05:03.056> devices<23:05:03.720> and<23:05:04.616> many<23:05:04.920> of 23:05:05.030 --> 23:05:05.040 align:start position:0% Vehicles physical devices and many of 23:05:05.040 --> 23:05:07.366 align:start position:0% Vehicles physical devices and many of them<23:05:05.160> work<23:05:05.280> with<23:05:05.464> sensors<23:05:05.936> or<23:05:06.120> softwares<23:05:06.720> so 23:05:07.366 --> 23:05:07.376 align:start position:0% them work with sensors or softwares so 23:05:07.376 --> 23:05:11.094 align:start position:0% them work with sensors or softwares so for<23:05:07.552> example<23:05:07.856> when<23:05:08.400> you're<23:05:08.760> uh<23:05:09.360> so<23:05:10.192> let<23:05:10.736> me<23:05:10.920> go 23:05:11.094 --> 23:05:11.104 align:start position:0% for example when you're uh so let me go 23:05:11.104 --> 23:05:13.790 align:start position:0% for example when you're uh so let me go down<23:05:11.400> there's<23:05:11.760> a<23:05:12.056> car<23:05:12.176> here<23:05:12.424> actually 23:05:13.790 --> 23:05:13.800 align:start position:0% down there's a car here actually 23:05:13.800 --> 23:05:18.222 align:start position:0% down there's a car here actually you'll<23:05:14.464> have<23:05:14.696> a<23:05:14.936> sensors<23:05:15.424> on<23:05:15.600> your<23:05:15.832> car 23:05:18.222 --> 23:05:18.232 align:start position:0% 23:05:18.232 --> 23:05:19.670 align:start position:0% I<23:05:18.536> know<23:05:18.656> I<23:05:18.784> didn't<23:05:18.832> want<23:05:19.016> any<23:05:19.144> awards<23:05:19.552> for 23:05:19.670 --> 23:05:19.680 align:start position:0% I know I didn't want any awards for 23:05:19.680 --> 23:05:23.926 align:start position:0% I know I didn't want any awards for drawing<23:05:20.104> centers<23:05:21.056> on<23:05:21.232> your<23:05:21.536> car<23:05:21.960> breaks 23:05:23.926 --> 23:05:23.936 align:start position:0% drawing centers on your car breaks 23:05:23.936 --> 23:05:27.470 align:start position:0% drawing centers on your car breaks uh<23:05:24.656> which<23:05:24.896> has<23:05:25.016> been<23:05:25.192> detected<23:05:25.920> by<23:05:26.400> a<23:05:27.232> gold 23:05:27.470 --> 23:05:27.480 align:start position:0% uh which has been detected by a gold 23:05:27.480 --> 23:05:30.350 align:start position:0% uh which has been detected by a gold goes<23:05:27.832> into<23:05:27.960> a<23:05:28.256> CPU<23:05:28.856> of<23:05:29.104> some<23:05:29.280> sort 23:05:30.350 --> 23:05:30.360 align:start position:0% goes into a CPU of some sort 23:05:30.360 --> 23:05:32.566 align:start position:0% goes into a CPU of some sort when<23:05:30.896> it<23:05:31.080> detects<23:05:31.504> it<23:05:31.616> the<23:05:31.800> wear<23:05:31.976> is<23:05:32.216> down<23:05:32.400> and 23:05:32.566 --> 23:05:32.576 align:start position:0% when it detects it the wear is down and 23:05:32.576 --> 23:05:35.286 align:start position:0% when it detects it the wear is down and say<23:05:32.696> you've<23:05:32.872> got<23:05:33.000> 30<23:05:33.232> left<23:05:33.960> then<23:05:34.616> it<23:05:35.040> will 23:05:35.286 --> 23:05:35.296 align:start position:0% say you've got 30 left then it will 23:05:35.296 --> 23:05:39.590 align:start position:0% say you've got 30 left then it will communicate<23:05:36.296> to<23:05:36.896> the<23:05:37.856> uh<23:05:38.104> garage 23:05:39.590 --> 23:05:39.600 align:start position:0% communicate to the uh garage 23:05:39.600 --> 23:05:41.814 align:start position:0% communicate to the uh garage a<23:05:39.960> computer<23:05:40.144> in<23:05:40.496> the<23:05:40.616> garage<23:05:40.800> that<23:05:41.576> will<23:05:41.696> all 23:05:41.814 --> 23:05:41.824 align:start position:0% a computer in the garage that will all 23:05:41.824 --> 23:05:43.606 align:start position:0% a computer in the garage that will all down<23:05:42.120> whatever<23:05:42.296> part<23:05:42.720> you<23:05:42.960> need<23:05:43.144> from<23:05:43.440> the 23:05:43.606 --> 23:05:43.616 align:start position:0% down whatever part you need from the 23:05:43.616 --> 23:05:45.950 align:start position:0% down whatever part you need from the manufacturer<23:05:44.400> that<23:05:45.120> will<23:05:45.296> go<23:05:45.424> to<23:05:45.536> the<23:05:45.720> garage 23:05:45.950 --> 23:05:45.960 align:start position:0% manufacturer that will go to the garage 23:05:45.960 --> 23:05:48.414 align:start position:0% manufacturer that will go to the garage and<23:05:46.552> then<23:05:46.680> you<23:05:47.216> probably<23:05:47.464> depending<23:05:48.000> on<23:05:48.176> how 23:05:48.414 --> 23:05:48.424 align:start position:0% and then you probably depending on how 23:05:48.424 --> 23:05:50.630 align:start position:0% and then you probably depending on how advanced<23:05:48.720> the<23:05:48.896> car<23:05:49.080> is<23:05:49.320> have<23:05:49.800> a<23:05:49.976> notification 23:05:50.630 --> 23:05:50.640 align:start position:0% advanced the car is have a notification 23:05:50.640 --> 23:05:53.926 align:start position:0% advanced the car is have a notification that<23:05:51.600> your<23:05:52.080> tires<23:05:52.440> are<23:05:52.552> worn<23:05:52.800> or<23:05:53.464> your<23:05:53.640> garage 23:05:53.926 --> 23:05:53.936 align:start position:0% that your tires are worn or your garage 23:05:53.936 --> 23:05:56.502 align:start position:0% that your tires are worn or your garage next<23:05:54.784> time<23:05:54.960> you<23:05:55.192> take<23:05:55.376> it<23:05:55.552> in<23:05:55.680> for<23:05:56.040> a<23:05:56.280> service 23:05:56.502 --> 23:05:56.512 align:start position:0% next time you take it in for a service 23:05:56.512 --> 23:05:58.726 align:start position:0% next time you take it in for a service we'll<23:05:56.824> have<23:05:57.000> the<23:05:57.120> part<23:05:57.296> in<23:05:57.536> stock 23:05:58.726 --> 23:05:58.736 align:start position:0% we'll have the part in stock 23:05:58.736 --> 23:06:01.494 align:start position:0% we'll have the part in stock and<23:05:59.936> um<23:05:59.936> we'll<23:06:00.536> be<23:06:00.720> able<23:06:00.832> to<23:06:00.896> replace<23:06:01.144> it 23:06:01.494 --> 23:06:01.504 align:start position:0% and um we'll be able to replace it 23:06:01.504 --> 23:06:03.046 align:start position:0% and um we'll be able to replace it that's<23:06:01.976> just<23:06:02.216> one<23:06:02.336> example<23:06:02.640> of<23:06:02.824> The<23:06:02.936> Internet 23:06:03.046 --> 23:06:03.056 align:start position:0% that's just one example of The Internet 23:06:03.056 --> 23:06:04.910 align:start position:0% that's just one example of The Internet of<23:06:03.360> Things<23:06:03.480> there's<23:06:03.656> many<23:06:03.896> of<23:06:04.144> many<23:06:04.680> of<23:06:04.856> those 23:06:04.910 --> 23:06:04.920 align:start position:0% of Things there's many of many of those 23:06:04.920 --> 23:06:07.006 align:start position:0% of Things there's many of many of those and<23:06:05.160> it's<23:06:05.280> just<23:06:05.464> a<23:06:05.576> phrase<23:06:05.824> that<23:06:06.000> was<23:06:06.176> coined 23:06:07.006 --> 23:06:07.016 align:start position:0% and it's just a phrase that was coined 23:06:07.016 --> 23:06:10.070 align:start position:0% and it's just a phrase that was coined several<23:06:07.800> years<23:06:07.976> ago<23:06:08.336> said<23:06:09.296> wave<23:06:09.656> is<23:06:09.896> a 23:06:10.070 --> 23:06:10.080 align:start position:0% several years ago said wave is a 23:06:10.080 --> 23:06:13.134 align:start position:0% several years ago said wave is a Wireless<23:06:10.280> Communications<23:06:11.280> protocol<23:06:12.144> used 23:06:13.134 --> 23:06:13.144 align:start position:0% Wireless Communications protocol used 23:06:13.144 --> 23:06:15.286 align:start position:0% Wireless Communications protocol used mainly<23:06:13.616> for<23:06:13.800> home<23:06:13.976> automation<23:06:14.576> for<23:06:15.000> example 23:06:15.286 --> 23:06:15.296 align:start position:0% mainly for home automation for example 23:06:15.296 --> 23:06:17.206 align:start position:0% mainly for home automation for example your<23:06:15.720> lighting<23:06:16.192> your<23:06:16.496> security<23:06:16.680> your 23:06:17.206 --> 23:06:17.216 align:start position:0% your lighting your security your 23:06:17.216 --> 23:06:19.182 align:start position:0% your lighting your security your thermostats<23:06:17.824> to<23:06:17.936> set<23:06:18.120> it<23:06:18.296> and<23:06:18.832> all<23:06:19.016> your 23:06:19.182 --> 23:06:19.192 align:start position:0% thermostats to set it and all your 23:06:19.192 --> 23:06:21.470 align:start position:0% thermostats to set it and all your favorite<23:06:19.440> settings<23:06:19.872> works<23:06:20.872> over<23:06:21.000> a<23:06:21.176> mesh 23:06:21.470 --> 23:06:21.480 align:start position:0% favorite settings works over a mesh 23:06:21.480 --> 23:06:23.990 align:start position:0% favorite settings works over a mesh networks<23:06:21.896> all<23:06:22.144> the<23:06:22.376> devices<23:06:22.680> are 23:06:23.990 --> 23:06:24.000 align:start position:0% networks all the devices are 23:06:24.000 --> 23:06:25.670 align:start position:0% networks all the devices are um<23:06:24.120> interconnected 23:06:25.670 --> 23:06:25.680 align:start position:0% um interconnected 23:06:25.680 --> 23:06:28.246 align:start position:0% um interconnected and<23:06:26.160> is<23:06:26.336> controlled<23:06:26.760> by<23:06:27.000> a<23:06:27.176> keypad<23:06:27.784> or<23:06:28.016> you<23:06:28.144> can 23:06:28.246 --> 23:06:28.256 align:start position:0% and is controlled by a keypad or you can 23:06:28.256 --> 23:06:30.350 align:start position:0% and is controlled by a keypad or you can have<23:06:28.376> a<23:06:28.552> key<23:06:28.616> fob<23:06:28.976> of<23:06:29.104> some<23:06:29.280> sort 23:06:30.350 --> 23:06:30.360 align:start position:0% have a key fob of some sort 23:06:30.360 --> 23:06:32.030 align:start position:0% have a key fob of some sort and<23:06:31.016> plus 23:06:32.030 --> 23:06:32.040 align:start position:0% and plus 23:06:32.040 --> 23:06:34.006 align:start position:0% and plus it's<23:06:32.576> a<23:06:32.696> wireless<23:06:32.824> communication<23:06:33.480> protocol 23:06:34.006 --> 23:06:34.016 align:start position:0% it's a wireless communication protocol 23:06:34.016 --> 23:06:37.670 align:start position:0% it's a wireless communication protocol again<23:06:34.512> monitor<23:06:35.512> sensor<23:06:36.000> data<23:06:36.424> this<23:06:37.376> could<23:06:37.504> be 23:06:37.670 --> 23:06:37.680 align:start position:0% again monitor sensor data this could be 23:06:37.680 --> 23:06:40.486 align:start position:0% again monitor sensor data this could be your<23:06:37.976> heart<23:06:38.160> rate<23:06:38.400> tire<23:06:38.936> pressure<23:06:39.496> television 23:06:40.486 --> 23:06:40.496 align:start position:0% your heart rate tire pressure television 23:06:40.496 --> 23:06:43.606 align:start position:0% your heart rate tire pressure television any<23:06:41.280> number<23:06:41.512> of<23:06:41.696> things<23:06:42.000> and<23:06:42.960> it's<23:06:43.144> created 23:06:43.606 --> 23:06:43.616 align:start position:0% any number of things and it's created 23:06:43.616 --> 23:06:45.350 align:start position:0% any number of things and it's created and<23:06:43.800> managed<23:06:44.104> by<23:06:44.280> the<23:06:44.464> ant<23:06:44.640> Alliance<23:06:45.120> it's 23:06:45.350 --> 23:06:45.360 align:start position:0% and managed by the ant Alliance it's 23:06:45.360 --> 23:06:47.926 align:start position:0% and managed by the ant Alliance it's actually<23:06:45.600> a<23:06:46.320> subsidiary<23:06:46.856> of<23:06:47.104> Garmin<23:06:47.576> who<23:06:47.824> do 23:06:47.926 --> 23:06:47.936 align:start position:0% actually a subsidiary of Garmin who do 23:06:47.936 --> 23:06:51.350 align:start position:0% actually a subsidiary of Garmin who do uh<23:06:48.232> the<23:06:48.480> satellite<23:06:48.832> technology 23:06:51.350 --> 23:06:51.360 align:start position:0% 23:06:51.360 --> 23:06:55.494 align:start position:0% a<23:06:51.832> Bluetooth<23:06:52.080> mesh<23:06:52.856> adopted<23:06:53.696> in<23:06:53.872> 2017<23:06:54.536> it's 23:06:55.494 --> 23:06:55.504 align:start position:0% a Bluetooth mesh adopted in 2017 it's 23:06:55.504 --> 23:06:58.726 align:start position:0% a Bluetooth mesh adopted in 2017 it's many<23:06:56.160> to<23:06:56.400> many<23:06:56.696> Communications 23:06:58.726 --> 23:06:58.736 align:start position:0% many to many Communications 23:06:58.736 --> 23:07:00.590 align:start position:0% many to many Communications so<23:06:59.160> the<23:06:59.280> receiver<23:06:59.576> can<23:06:59.872> be<23:07:00.000> a<23:07:00.120> thing<23:07:00.232> a<23:07:00.480> group 23:07:00.590 --> 23:07:00.600 align:start position:0% so the receiver can be a thing a group 23:07:00.600 --> 23:07:02.750 align:start position:0% so the receiver can be a thing a group of<23:07:00.784> things<23:07:01.080> or<23:07:01.552> many<23:07:01.736> things<23:07:02.104> for<23:07:02.512> example 23:07:02.750 --> 23:07:02.760 align:start position:0% of things or many things for example 23:07:02.760 --> 23:07:05.094 align:start position:0% of things or many things for example you'd<23:07:03.720> compare<23:07:03.960> that<23:07:04.144> to<23:07:04.320> the<23:07:04.680> unicast 23:07:05.094 --> 23:07:05.104 align:start position:0% you'd compare that to the unicast 23:07:05.104 --> 23:07:07.606 align:start position:0% you'd compare that to the unicast multicast<23:07:05.696> or<23:07:06.000> broadcast 23:07:07.606 --> 23:07:07.616 align:start position:0% multicast or broadcast 23:07:07.616 --> 23:07:09.414 align:start position:0% multicast or broadcast all<23:07:08.280> messages<23:07:08.512> are<23:07:08.872> encrypted<23:07:09.232> and 23:07:09.414 --> 23:07:09.424 align:start position:0% all messages are encrypted and 23:07:09.424 --> 23:07:13.310 align:start position:0% all messages are encrypted and authenticated<23:07:10.080> so<23:07:10.376> it's<23:07:10.552> pretty<23:07:10.800> secure 23:07:13.310 --> 23:07:13.320 align:start position:0% 23:07:13.320 --> 23:07:16.070 align:start position:0% are<23:07:13.800> you<23:07:13.920> sorry<23:07:14.040> you<23:07:14.216> can<23:07:14.280> ignore<23:07:14.512> that<23:07:14.696> one 23:07:16.070 --> 23:07:16.080 align:start position:0% are you sorry you can ignore that one 23:07:16.080 --> 23:07:19.790 align:start position:0% are you sorry you can ignore that one near<23:07:16.552> field<23:07:16.800> communications 23:07:19.790 --> 23:07:19.800 align:start position:0% 23:07:19.800 --> 23:07:22.070 align:start position:0% a<23:07:20.216> set<23:07:20.400> of<23:07:20.576> communication<23:07:21.000> protocols<23:07:21.832> you're 23:07:22.070 --> 23:07:22.080 align:start position:0% a set of communication protocols you're 23:07:22.080 --> 23:07:23.926 align:start position:0% a set of communication protocols you're probably<23:07:22.192> using<23:07:22.616> this<23:07:22.800> already<23:07:22.976> it<23:07:23.640> allows 23:07:23.926 --> 23:07:23.936 align:start position:0% probably using this already it allows 23:07:23.936 --> 23:07:25.966 align:start position:0% probably using this already it allows two<23:07:24.120> devices<23:07:24.480> one's<23:07:25.080> usually<23:07:25.320> a<23:07:25.552> smartphone 23:07:25.966 --> 23:07:25.976 align:start position:0% two devices one's usually a smartphone 23:07:25.976 --> 23:07:28.966 align:start position:0% two devices one's usually a smartphone to<23:07:26.824> communicate 23:07:28.966 --> 23:07:28.976 align:start position:0% to communicate 23:07:28.976 --> 23:07:30.286 align:start position:0% to communicate now<23:07:29.336> you<23:07:29.464> need<23:07:29.576> to<23:07:29.696> be<23:07:29.760> within<23:07:30.120> four 23:07:30.286 --> 23:07:30.296 align:start position:0% now you need to be within four 23:07:30.296 --> 23:07:31.790 align:start position:0% now you need to be within four centimeters<23:07:30.960> of<23:07:31.080> each<23:07:31.192> other<23:07:31.320> so<23:07:31.504> you<23:07:31.616> have<23:07:31.680> to 23:07:31.790 --> 23:07:31.800 align:start position:0% centimeters of each other so you have to 23:07:31.800 --> 23:07:34.134 align:start position:0% centimeters of each other so you have to be<23:07:31.856> pretty<23:07:32.104> close<23:07:32.400> use<23:07:33.360> for<23:07:33.656> contactless 23:07:34.134 --> 23:07:34.144 align:start position:0% be pretty close use for contactless 23:07:34.144 --> 23:07:36.414 align:start position:0% be pretty close use for contactless payments<23:07:34.680> I<23:07:34.856> know<23:07:35.040> on<23:07:35.216> my<23:07:35.400> phone<23:07:35.576> I<23:07:35.872> can<23:07:36.056> enable 23:07:36.414 --> 23:07:36.424 align:start position:0% payments I know on my phone I can enable 23:07:36.424 --> 23:07:40.542 align:start position:0% payments I know on my phone I can enable it<23:07:36.784> to<23:07:37.552> act<23:07:38.464> as<23:07:38.640> my<23:07:39.056> card<23:07:39.720> credit<23:07:40.080> card<23:07:40.320> or 23:07:40.542 --> 23:07:40.552 align:start position:0% it to act as my card credit card or 23:07:40.552 --> 23:07:42.710 align:start position:0% it to act as my card credit card or debit<23:07:40.920> card<23:07:41.040> and<23:07:41.696> swipe<23:07:42.056> for<23:07:42.232> my<23:07:42.536> phone 23:07:42.710 --> 23:07:42.720 align:start position:0% debit card and swipe for my phone 23:07:42.720 --> 23:07:45.286 align:start position:0% debit card and swipe for my phone instead<23:07:43.552> of<23:07:43.616> my<23:07:43.856> card<23:07:44.104> quite<23:07:44.760> handy<23:07:45.000> if<23:07:45.120> you've 23:07:45.286 --> 23:07:45.296 align:start position:0% instead of my card quite handy if you've 23:07:45.296 --> 23:07:46.606 align:start position:0% instead of my card quite handy if you've forgotten<23:07:45.656> your<23:07:45.784> wallet<23:07:46.080> somewhere<23:07:46.376> as<23:07:46.496> well 23:07:46.606 --> 23:07:46.616 align:start position:0% forgotten your wallet somewhere as well 23:07:46.616 --> 23:07:49.094 align:start position:0% forgotten your wallet somewhere as well and<23:07:46.736> you<23:07:47.104> need<23:07:47.216> to<23:07:47.336> pay<23:07:47.464> for<23:07:47.696> something 23:07:49.094 --> 23:07:49.104 align:start position:0% and you need to pay for something 23:07:49.104 --> 23:07:51.470 align:start position:0% and you need to pay for something infrared<23:07:50.104> I'll<23:07:50.696> go<23:07:50.936> I'm<23:07:51.056> sure<23:07:51.176> you've<23:07:51.296> heard 23:07:51.470 --> 23:07:51.480 align:start position:0% infrared I'll go I'm sure you've heard 23:07:51.480 --> 23:07:53.326 align:start position:0% infrared I'll go I'm sure you've heard of<23:07:51.600> that<23:07:51.720> we<23:07:51.832> used<23:07:52.016> to<23:07:52.192> have<23:07:52.680> um<23:07:52.680> this<23:07:53.040> used<23:07:53.160> to 23:07:53.326 --> 23:07:53.336 align:start position:0% of that we used to have um this used to 23:07:53.336 --> 23:07:55.670 align:start position:0% of that we used to have um this used to be<23:07:53.464> the<23:07:53.872> competitor<23:07:54.784> to<23:07:54.896> wireless<23:07:55.144> where 23:07:55.670 --> 23:07:55.680 align:start position:0% be the competitor to wireless where 23:07:55.680 --> 23:07:57.646 align:start position:0% be the competitor to wireless where companies<23:07:56.336> would<23:07:56.576> add<23:07:56.760> an<23:07:57.296> infrared 23:07:57.646 --> 23:07:57.656 align:start position:0% companies would add an infrared 23:07:57.656 --> 23:07:59.750 align:start position:0% companies would add an infrared communication<23:07:58.320> module<23:07:58.856> on<23:07:59.216> top<23:07:59.336> of<23:07:59.512> their 23:07:59.750 --> 23:07:59.760 align:start position:0% communication module on top of their 23:07:59.760 --> 23:08:01.006 align:start position:0% communication module on top of their building 23:08:01.006 --> 23:08:01.016 align:start position:0% building 23:08:01.016 --> 23:08:02.454 align:start position:0% building and<23:08:01.440> as<23:08:01.504> long<23:08:01.680> as<23:08:01.736> they<23:08:01.856> had<23:08:01.976> line<23:08:02.104> the<23:08:02.336> site 23:08:02.454 --> 23:08:02.464 align:start position:0% and as long as they had line the site 23:08:02.464 --> 23:08:03.950 align:start position:0% and as long as they had line the site they<23:08:02.640> could<23:08:02.760> get<23:08:02.936> high-speed<23:08:03.424> Communications 23:08:03.950 --> 23:08:03.960 align:start position:0% they could get high-speed Communications 23:08:03.960 --> 23:08:05.990 align:start position:0% they could get high-speed Communications with<23:08:04.376> another<23:08:04.616> building<23:08:05.040> then<23:08:05.640> I<23:08:05.872> can't 23:08:05.990 --> 23:08:06.000 align:start position:0% with another building then I can't 23:08:06.000 --> 23:08:08.270 align:start position:0% with another building then I can't remember<23:08:06.120> what<23:08:06.296> the<23:08:06.424> range<23:08:06.656> was<23:08:06.896> but<23:08:08.040> um<23:08:08.040> it 23:08:08.270 --> 23:08:08.280 align:start position:0% remember what the range was but um it 23:08:08.280 --> 23:08:10.310 align:start position:0% remember what the range was but um it fell<23:08:08.512> by<23:08:08.760> the<23:08:08.872> wayside<23:08:09.120> really 23:08:10.310 --> 23:08:10.320 align:start position:0% fell by the wayside really 23:08:10.320 --> 23:08:12.046 align:start position:0% fell by the wayside really it's<23:08:10.616> similar<23:08:10.976> to<23:08:11.160> visible<23:08:11.464> light<23:08:11.696> but 23:08:12.046 --> 23:08:12.056 align:start position:0% it's similar to visible light but 23:08:12.056 --> 23:08:14.390 align:start position:0% it's similar to visible light but slightly<23:08:12.656> longer<23:08:13.016> wavelength 23:08:14.390 --> 23:08:14.400 align:start position:0% slightly longer wavelength 23:08:14.400 --> 23:08:17.686 align:start position:0% slightly longer wavelength for<23:08:15.176> example<23:08:15.424> your<23:08:15.720> remote<23:08:16.016> control 23:08:17.686 --> 23:08:17.696 align:start position:0% for example your remote control 23:08:17.696 --> 23:08:20.206 align:start position:0% for example your remote control you<23:08:18.232> click<23:08:18.424> that<23:08:18.720> and<23:08:19.320> per<23:08:19.504> second<23:08:19.680> of<23:08:19.920> holding 23:08:20.206 --> 23:08:20.216 align:start position:0% you click that and per second of holding 23:08:20.216 --> 23:08:22.246 align:start position:0% you click that and per second of holding down<23:08:20.336> the<23:08:20.464> button<23:08:20.696> it<23:08:20.872> sends<23:08:21.176> out<23:08:21.296> 38<23:08:22.144> 000 23:08:22.246 --> 23:08:22.256 align:start position:0% down the button it sends out 38 000 23:08:22.256 --> 23:08:24.646 align:start position:0% down the button it sends out 38 000 signals 23:08:24.646 --> 23:08:24.656 align:start position:0% signals 23:08:24.656 --> 23:08:26.270 align:start position:0% signals used<23:08:25.192> in<23:08:25.440> Internet<23:08:25.552> things<23:08:25.920> for<23:08:26.104> medical 23:08:26.270 --> 23:08:26.280 align:start position:0% used in Internet things for medical 23:08:26.280 --> 23:08:29.750 align:start position:0% used in Internet things for medical Diagnostics<23:08:27.120> fire<23:08:27.600> detection<23:08:28.464> remote<23:08:29.464> gas 23:08:29.750 --> 23:08:29.760 align:start position:0% Diagnostics fire detection remote gas 23:08:29.760 --> 23:08:32.094 align:start position:0% Diagnostics fire detection remote gas leak<23:08:30.120> detention<23:08:30.480> air<23:08:30.832> detection 23:08:32.094 --> 23:08:32.104 align:start position:0% leak detention air detection 23:08:32.104 --> 23:08:34.726 align:start position:0% leak detention air detection RFID<23:08:33.000> you<23:08:33.600> probably<23:08:33.720> see<23:08:34.016> this<23:08:34.192> if<23:08:34.376> you<23:08:34.496> saw 23:08:34.726 --> 23:08:34.736 align:start position:0% RFID you probably see this if you saw 23:08:34.736 --> 23:08:36.822 align:start position:0% RFID you probably see this if you saw the<23:08:35.160> uh<23:08:35.400> the<23:08:35.696> newest<23:08:35.936> not<23:08:36.120> the<23:08:36.296> newest<23:08:36.600> porn 23:08:36.822 --> 23:08:36.832 align:start position:0% the uh the newest not the newest porn 23:08:36.832 --> 23:08:37.726 align:start position:0% the uh the newest not the newest porn film 23:08:37.726 --> 23:08:37.736 align:start position:0% film 23:08:37.736 --> 23:08:41.814 align:start position:0% film a<23:08:38.216> bone<23:08:38.696> film<23:08:39.296> um<23:08:39.296> with<23:08:39.656> Jeremy<23:08:40.144> uh<23:08:41.104> I<23:08:41.512> forgot 23:08:41.814 --> 23:08:41.824 align:start position:0% a bone film um with Jeremy uh I forgot 23:08:41.824 --> 23:08:43.542 align:start position:0% a bone film um with Jeremy uh I forgot his<23:08:42.000> name<23:08:42.232> now 23:08:43.542 --> 23:08:43.552 align:start position:0% his name now 23:08:43.552 --> 23:08:45.590 align:start position:0% his name now JB<23:08:44.160> right<23:08:44.336> now<23:08:44.576> we<23:08:45.000> had<23:08:45.176> one<23:08:45.360> of<23:08:45.480> these 23:08:45.590 --> 23:08:45.600 align:start position:0% JB right now we had one of these 23:08:45.600 --> 23:08:47.526 align:start position:0% JB right now we had one of these inserted<23:08:46.080> in<23:08:46.192> him<23:08:46.376> and<23:08:46.616> they<23:08:46.736> tried<23:08:46.920> to<23:08:47.104> uh 23:08:47.526 --> 23:08:47.536 align:start position:0% inserted in him and they tried to uh 23:08:47.536 --> 23:08:49.494 align:start position:0% inserted in him and they tried to uh unfortunately<23:08:48.536> tried<23:08:48.784> to<23:08:48.896> shoot<23:08:49.016> him<23:08:49.192> with<23:08:49.376> a 23:08:49.494 --> 23:08:49.504 align:start position:0% unfortunately tried to shoot him with a 23:08:49.504 --> 23:08:51.590 align:start position:0% unfortunately tried to shoot him with a missile<23:08:49.736> so<23:08:50.040> I<23:08:50.216> had<23:08:50.280> to<23:08:50.400> cut<23:08:50.512> it<23:08:50.640> out 23:08:51.590 --> 23:08:51.600 align:start position:0% missile so I had to cut it out 23:08:51.600 --> 23:08:54.166 align:start position:0% missile so I had to cut it out let's<23:08:52.616> um<23:08:52.616> yes<23:08:53.216> it's<23:08:53.400> essential<23:08:53.824> to<23:08:54.000> the 23:08:54.166 --> 23:08:54.176 align:start position:0% let's um yes it's essential to the 23:08:54.176 --> 23:08:55.542 align:start position:0% let's um yes it's essential to the operation<23:08:54.656> on<23:08:54.896> the<23:08:55.016> Internet<23:08:55.080> of<23:08:55.440> Things 23:08:55.542 --> 23:08:55.552 align:start position:0% operation on the Internet of Things 23:08:55.552 --> 23:08:57.222 align:start position:0% operation on the Internet of Things allows<23:08:56.040> computers<23:08:56.464> to<23:08:56.696> manage<23:08:56.936> all 23:08:57.222 --> 23:08:57.232 align:start position:0% allows computers to manage all 23:08:57.232 --> 23:08:59.270 align:start position:0% allows computers to manage all individual<23:08:57.784> things<23:08:58.016> this<23:08:58.616> is<23:08:58.736> compared<23:08:59.160> in 23:08:59.270 --> 23:08:59.280 align:start position:0% individual things this is compared in 23:08:59.280 --> 23:09:00.774 align:start position:0% individual things this is compared in the<23:08:59.400> picture<23:08:59.512> to<23:08:59.760> a<23:08:59.872> grain<23:09:00.120> of<23:09:00.232> rice<23:09:00.424> so<23:09:00.720> it's 23:09:00.774 --> 23:09:00.784 align:start position:0% the picture to a grain of rice so it's 23:09:00.784 --> 23:09:02.030 align:start position:0% the picture to a grain of rice so it's pretty<23:09:00.960> smart 23:09:02.030 --> 23:09:02.040 align:start position:0% pretty smart 23:09:02.040 --> 23:09:04.910 align:start position:0% pretty smart uses<23:09:02.936> Emi<23:09:03.536> fields<23:09:03.896> to<23:09:04.080> identify<23:09:04.440> and<23:09:04.680> track 23:09:04.910 --> 23:09:04.920 align:start position:0% uses Emi fields to identify and track 23:09:04.920 --> 23:09:08.206 align:start position:0% uses Emi fields to identify and track tags<23:09:05.464> it<23:09:05.640> up<23:09:05.824> and<23:09:06.232> attached<23:09:06.720> to<23:09:06.832> objects 23:09:08.206 --> 23:09:08.216 align:start position:0% tags it up and attached to objects 23:09:08.216 --> 23:09:09.710 align:start position:0% tags it up and attached to objects the<23:09:08.576> attack<23:09:08.696> can<23:09:09.056> actually<23:09:09.176> contain<23:09:09.600> the 23:09:09.710 --> 23:09:09.720 align:start position:0% the attack can actually contain the 23:09:09.720 --> 23:09:13.182 align:start position:0% the attack can actually contain the electronically<23:09:10.256> stored<23:09:10.616> information<23:09:10.800> so 23:09:13.182 --> 23:09:13.192 align:start position:0% electronically stored information so 23:09:13.192 --> 23:09:16.606 align:start position:0% electronically stored information so this<23:09:13.736> is<23:09:13.856> what's<23:09:13.976> used<23:09:14.280> to<23:09:14.512> Target<23:09:15.000> pets 23:09:16.606 --> 23:09:16.616 align:start position:0% this is what's used to Target pets 23:09:16.616 --> 23:09:19.606 align:start position:0% this is what's used to Target pets for<23:09:17.400> example<23:09:17.696> when<23:09:18.232> will<23:09:18.784> a<23:09:18.960> pet<23:09:19.144> gets<23:09:19.504> lost 23:09:19.606 --> 23:09:19.616 align:start position:0% for example when will a pet gets lost 23:09:19.616 --> 23:09:21.774 align:start position:0% for example when will a pet gets lost somewhere<23:09:20.040> it<23:09:20.160> can<23:09:20.280> be<23:09:20.400> tagged 23:09:21.774 --> 23:09:21.784 align:start position:0% somewhere it can be tagged 23:09:21.784 --> 23:09:24.110 align:start position:0% somewhere it can be tagged also<23:09:22.320> using<23:09:22.680> tracking<23:09:23.104> Vehicles<23:09:23.640> if<23:09:23.936> you've 23:09:24.110 --> 23:09:24.120 align:start position:0% also using tracking Vehicles if you've 23:09:24.120 --> 23:09:25.846 align:start position:0% also using tracking Vehicles if you've ever<23:09:24.232> seen<23:09:24.480> a<23:09:24.656> production<23:09:24.896> line<23:09:25.192> there's<23:09:25.504> tags 23:09:25.846 --> 23:09:25.856 align:start position:0% ever seen a production line there's tags 23:09:25.856 --> 23:09:27.950 align:start position:0% ever seen a production line there's tags inserted<23:09:26.336> on<23:09:26.512> the<23:09:26.640> vehicle<23:09:26.936> and<23:09:27.480> that<23:09:27.656> updates 23:09:27.950 --> 23:09:27.960 align:start position:0% inserted on the vehicle and that updates 23:09:27.960 --> 23:09:29.750 align:start position:0% inserted on the vehicle and that updates the<23:09:28.192> entire<23:09:28.440> production<23:09:28.856> system<23:09:29.104> as<23:09:29.400> to<23:09:29.576> if 23:09:29.750 --> 23:09:29.760 align:start position:0% the entire production system as to if 23:09:29.760 --> 23:09:32.502 align:start position:0% the entire production system as to if it's<23:09:29.872> going<23:09:30.056> too<23:09:30.360> fast<23:09:30.536> too<23:09:30.896> slow<23:09:31.144> and<23:09:32.040> when<23:09:32.400> to 23:09:32.502 --> 23:09:32.512 align:start position:0% it's going too fast too slow and when to 23:09:32.512 --> 23:09:35.862 align:start position:0% it's going too fast too slow and when to expect<23:09:32.696> the<23:09:32.936> next<23:09:33.056> vehicle<23:09:33.424> along 23:09:35.862 --> 23:09:35.872 align:start position:0% 23:09:35.872 --> 23:09:37.846 align:start position:0% all<23:09:36.360> right<23:09:36.536> so<23:09:36.656> we've<23:09:36.832> covered<23:09:37.144> just<23:09:37.376> in<23:09:37.504> brief 23:09:37.846 --> 23:09:37.856 align:start position:0% all right so we've covered just in brief 23:09:37.856 --> 23:09:40.966 align:start position:0% all right so we've covered just in brief the<23:09:38.040> Z<23:09:38.216> Wave<23:09:38.640> amp<23:09:39.120> plus<23:09:39.232> Bluetooth<23:09:39.720> NFC<23:09:40.552> IR 23:09:40.966 --> 23:09:40.976 align:start position:0% the Z Wave amp plus Bluetooth NFC IR 23:09:40.976 --> 23:09:44.150 align:start position:0% the Z Wave amp plus Bluetooth NFC IR RFID<23:09:41.832> just<23:09:42.832> you<23:09:43.080> need<23:09:43.256> to<23:09:43.376> be<23:09:43.504> aware<23:09:43.736> of<23:09:43.856> these 23:09:44.150 --> 23:09:44.160 align:start position:0% RFID just you need to be aware of these 23:09:44.160 --> 23:09:46.246 align:start position:0% RFID just you need to be aware of these in<23:09:44.576> case<23:09:44.760> one<23:09:45.176> of<23:09:45.296> the<23:09:45.360> questions<23:09:45.480> pops<23:09:46.016> up<23:09:46.144> in 23:09:46.246 --> 23:09:46.256 align:start position:0% in case one of the questions pops up in 23:09:46.256 --> 23:09:47.270 align:start position:0% in case one of the questions pops up in the<23:09:46.440> exam 23:09:47.270 --> 23:09:47.280 align:start position:0% the exam 23:09:47.280 --> 23:09:50.720 align:start position:0% the exam that's<23:09:47.760> all<23:09:47.872> thanks<23:09:48.176> for<23:09:48.360> watching 10455653

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.